Parallel tests execution in a collection

I have a very common case of testing. I have a collection fixture:
[CollectionDefinition(nameof(SomeCollection))]
public class SomeCollection : ICollectionFixture<ImmutableClass>
{
}

with some test classes:
[Collection(nameof(SomeCollection))]
public class TestClass1
{
    [Fact]
    public async Task Test1() => await Task.Delay(3000);

    [Fact]
    public async Task Test2() => await Task.Delay(3000);
}

[Collection(nameof(SomeCollection))]
public class TestClass2
{
    [Fact]
    public async Task Test3() => await Task.Delay(3000);

    [Fact]
    public async Task Test4() => await Task.Delay(3000);
}

This fixture is immutable, so I want to run each test method in the collection parallel. It should be 4 times faster. Is there any way to achieve this?

@iikuzmychov the feature that you are looking for is now available. you will have to add "EnableParallelization" attribute to the collection tests classes.
[Collection(nameof(SomeCollection))]
[EnableParallelization]
public class TestClass1
{
    [Fact]
    public async Task Test1() => await Task.Delay(3000);

    [Fact]
    public async Task Test2() => await Task.Delay(3000);
}

[Collection(nameof(SomeCollection))]
[EnableParallelization]
public class TestClass2
{
    [Fact]
    public async Task Test3() => await Task.Delay(3000);

    [Fact]
    public async Task Test4() => await Task.Delay(3000);
}

Awesome, thanks! Will try it today and then close the issue

Hmm, it seems like tests from TestClass1 and TestClass2 still executing sequentially 🤔 However, the tests within the same test class are running in parallel

Would be much appreciated if we could run the tests in parallel for a whole collection

@meziantou Could you review the PR?

@meziantou can you release the nuget package and close this ticket?

I just published the package on nuget. It should be available in a few minutes.

@meziantou @pregress Thanks you both!
Note for everyone who will found this issue in the future: now you also need to add [EnableParallelization] attribute to the fixture. So the final sample will looks like this:
public class ImmutableClass
{
}

[CollectionDefinition(nameof(SomeCollection))]
[EnableParallelization] // <------------------------------------------------  here is it
public class SomeCollection : ICollectionFixture<ImmutableClass>
{
}

[Collection(nameof(SomeCollection))]
[EnableParallelization]
public class TestClass1
{
    [Fact]
    public async Task Test1() => await Task.Delay(3000);

    [Fact]
    public async Task Test2() => await Task.Delay(3000);
}

[Collection(nameof(SomeCollection))]
[EnableParallelization]
public class TestClass2
{
    [Fact]
    public async Task Test3() => await Task.Delay(3000);

    [Fact]
    public async Task Test4() => await Task.Delay(3000);
}


error when runntin marble

info: [EventHub.js]: _connect - options {"grpc.http2.keepalive_time":300,"grpc.keepalive_time_ms":300000,"grpc.http2.keepalive_timeout":35,"grpc.keepalive_timeout_ms":3500,"grpc.max_receive_message_length":-1,"grpc.max_send_message_length":-1}
error: [client-utils.js]: sendPeersProposal - Promise is rejected: Error: 2 UNKNOWN: error executing chaincode: premature execution - chaincode (marbles:v4) is being launched
at new createStatusError (/home/daily/Desktop/hyper/marbles/node_modules/grpc/src/client.js:64:15)
at /home/daily/Desktop/hyper/marbles/node_modules/grpc/src/client.js:583:15
error: [fcw] Failed to obtain endorsement for transaction. code=2, , details=error executing chaincode: premature execution - chaincode (marbles:v4) is being launched
error: [fcw] Error in invoke catch block object code=2, , details=error executing chaincode: premature execution - chaincode (marbles:v4) is being launched
debug: [fcw] transaction event is disconnected
error: Exhausted all peers. There are no more peers to try.
error: error creating the marble owner { parsed: 'Blockchain network error - 4) is being launched',
raw:
[ { Error: 2 UNKNOWN: error executing chaincode: premature execution - chaincode (marbles:v4) is being launched
at new createStatusError (/home/daily/Desktop/hyper/marbles/node_modules/grpc/src/client.js:64:15)
at /home/daily/Desktop/hyper/marbles/node_modules/grpc/src/client.js:583:15
code: 2,
metadata: [Object],
details: 'error executing chaincode: premature execution - chaincode (marbles:v4) is being launched' } ] } id=o01552996702741bbX2S
error: [client-utils.js]: sendPeersProposal - Promise is rejected: Error: 2 UNKNOWN: error executing chaincode: premature execution - chaincode (marbles:v4) is being launched
at new createStatusError (/home/daily/Desktop/hyper/marbles/node_modules/grpc/src/client.js:64:15)
at /home/daily/Desktop/hyper/marbles/node_modules/grpc/src/client.js:583:15
error: [fcw] Failed to obtain endorsement for transaction. code=2, , details=error executing chaincode: premature execution - chaincode (marbles:v4) is being launched
error: [fcw] Error in invoke catch block object code=2, , details=error executing chaincode: premature execution - chaincode (marbles:v4) is being launched
debug: [fcw] transaction event is disconnected
error: Exhausted all peers. There are no more peers to try.
error: error creating the marble owner { parsed: 'Blockchain network error - 4) is being launched',
raw:
[ { Error: 2 UNKNOWN: error executing chaincode: premature execution - chaincode (marbles:v4) is being launched
at new createStatusError (/home/daily/Desktop/hyper/marbles/node_modules/grpc/src/client.js:64:15)
at /home/daily/Desktop/hyper/marbles/node_modules/grpc/src/client.js:583:15
code: 2,
metadata: [Object],
details: 'error executing chaincode: premature execution - chaincode (marbles:v4) is being launched' } ] } id=o01552996702749VW11M
I did "install_chaincode", and "instantiate_chaincode", but there is no error.
But when i running "gulp marbles_local" and do guide step4(maybe register 3 users), this error is occur..
Need help ..

so error executing chaincode: premature execution is the Fabric error saying you have to wait a bit more for you chaincode to start.  it can take awhile depending on your environment and internet speed (2-10minutes). the peer needs to download some dependency images which take time.

Thanks, all problem is solved :)


Add tracker for non-js users, fixes #383

Coverage remained the same at 100.0% when pulling f756aa857d9725679fa72e36ea1002c0ddfe0777 on issue/383-image-tracker into 6c32413baae0569389284185f0c64f22bb4096ba on master.


Prepare changelog for 1.1.2

Coverage remained the same at 97.526% when pulling ce9f5490926473884552d914ad64c06b6d3a27f7 on roman/1.1.1 into 40c3d2bd149621169a5bf2f31fc9176f89ccd94c on devel.

Coverage remained the same at 97.526% when pulling c14fac9e4cc0521dca9412fa3b2708ae804be430 on roman/1.1.1 into 40c3d2bd149621169a5bf2f31fc9176f89ccd94c on devel.


Index outside of table length

The offset input box warns of numbers larger than a limit (like 2000) but then the errors start at a smaller value than that limit (like 1955).

ValueError: Index (2000) outside of table length (2000).
Traceback:
File "/home/sasha/.local/lib/python3.7/site-packages/streamlit/ScriptRunner.py", line 322, in _run_script
exec(code, module.dict)
File "/home/sasha/nlp_viewer/run.py", line 116, in
v = d[item][k]
File "/home/sasha/.local/lib/python3.7/site-packages/nlp/arrow_dataset.py", line 338, in getitem
output_all_columns=self._output_all_columns,
File "/home/sasha/.local/lib/python3.7/site-packages/nlp/arrow_dataset.py", line 290, in _getitem
raise ValueError(f"Index ({key}) outside of table length ({self._data.num_rows}).")

Interesting. Could you provide a snippet of code to reproduce this error ?

Sounds like something related to the nlp viewer @srush

Fixed.


alter data field and the form of password encryption

I have altered the date filed to data layer and changed the form of password encryption.
In this change, I will not insert a new field into the database。

No necessary.The sql file hava realized the date of update.
I will delete the relevant code.

No necessary.The sql file hava realized the date of update.
I will delete the relevant code.


Cannot use DotNet on Extension

Hello
When i try to use XMLdocument from DotNet y get the error "The type or method 'DotNet' cannot be used for 'Extension' development.AL(AL0296)" is there a way to achieve this

You can use DotNet types only if you are developing for on-premise only. For this you will need to set the target property to "Internal" in the app.json file of your project.
Please see:  https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/devenv-get-started-call-dotnet-from-al
If your solution is supposed to be for on-premise only, then you should look into using built-in types and objects.
For your case, you might also want to look into the new AL type "XmlDocument" (see: https://docs.microsoft.com/en-us/dynamics365/business-central/dev-itpro/developer/methods-auto/xmldocument/xmldocument-data-type)

Thanks for the reply this help me so much

Thanks @adrianordonez for filing this issue. As @rvanbekkum correctly points out, you can't invoke dotnet code directly on BC servers. Thanks


Install python libraries through requirements

This will help push snafu to become a python library, and also
as we try to migrate other benchmarks to run_snafu and because of
imports each Dockerfile for the benchmark would be requiring more
libaries that aren't tracked in requirements.txt

/rerun all

Results for SNAFU CI Test

Test
Result
Runtime

fio_wrapper
PASS
00:16:20

fs_drift_wrapper
PASS
00:10:19

hammerdb
FAIL
00:15:58

pgbench-wrapper
FAIL
00:00:02

requirements.txt
FAIL
00:00:00

smallfile_wrapper
FAIL
00:00:01

uperf-wrapper
FAIL
00:00:02

ycsb-wrapper
FAIL
00:00:01

The ci system ran out of space in /. Re-running this test now.

/rerun all

Results for SNAFU CI Test

Test
Result
Runtime

fio_wrapper
FAIL
00:02:43

fs_drift_wrapper
FAIL
00:02:19

hammerdb
FAIL
00:03:23

pgbench-wrapper
FAIL
00:02:05

requirements.txt
FAIL
00:00:00

smallfile_wrapper
FAIL
00:02:12

uperf-wrapper
FAIL
00:01:51

ycsb-wrapper
FAIL
00:05:51

/rerun all

Results for SNAFU CI Test

Test
Result
Runtime

fio_wrapper
PASS
00:15:32

fs_drift_wrapper
PASS
00:09:11

hammerdb
PASS
00:11:19

pgbench-wrapper
PASS
00:07:14

requirements.txt
FAIL
00:00:00

smallfile_wrapper
PASS
00:10:22

uperf-wrapper
PASS
00:23:37

ycsb-wrapper
PASS
00:13:45

Looks good however needs a doc update to point out that we want to use that requirements file now.

Looks good however needs a doc update to point out that we want to use that requirements file now.

updated

!!! Couldn't read commit file !!!

@aakarshg With this change we are installing some modules twice. :(

configparser => included by default in python3.7
statistics => included by default in python3.7
numpy => Installed via DNF
requests => Installed via DNF


LLVM-3.7 MCJIT

In theory if 3.6 is supported, 3.7 should work also since the ORCJIT does no come at the expense of the MCJIT, but is intended to complement it.
However, currnet HEAD is failing. (Specifically with LLVM-3.7.1)
./OpenShadingLanguage-Release/src/liboslexec/llvm_util.cpp: In member function ‘void OSL::pvt::LLVM_Util::SetupLLVM()’:
./OpenShadingLanguage-Release/src/liboslexec/llvm_util.cpp:347:49: error: ‘begin’ is not a member of ‘llvm::TargetRegistry’
         for (llvm::TargetRegistry::iterator t = llvm::TargetRegistry::begin();

./OpenShadingLanguage-Release/src/liboslexec/llvm_util.cpp:348:19: error: ‘end’ is not a member of ‘llvm::TargetRegistry’
              t != llvm::TargetRegistry::end();  ++t) {

./OpenShadingLanguage-Release/src/liboslexec/llvm_util.cpp: In member function ‘llvm::Module* OSL::pvt::LLVM_Util::module_from_bitcode(const char*, size_t, const string&, std::__cxx11::string*)’:
./OpenShadingLanguage-Release/src/liboslexec/llvm_util.cpp:392:72: error: conversion from ‘llvm::ErrorOr<std::unique_ptr<llvm::Module> >’ to non-scalar type ‘llvm::ErrorOr<llvm::Module*>’ requested
     llvm::ErrorOr<llvm::Module *> ModuleOrErr = llvm::parseBitcodeFile (buf, context());

./OpenShadingLanguage-Release/src/liboslexec/llvm_util.cpp: In member function ‘void OSL::pvt::LLVM_Util::setup_optimization_passes(int)’:
./OpenShadingLanguage-Release/src/liboslexec/llvm_util.cpp:524:18: error: expected type-specifier
     fpm.add (new llvm::DataLayoutPass());

./OpenShadingLanguage-Release/src/liboslexec/llvm_util.cpp:528:18: error: expected type-specifier

./OpenShadingLanguage-Release/src/liboslexec/llvm_util.cpp: In member function ‘void OSL::pvt::LLVM_Util::op_memset(llvm::Value*, int, llvm::Value*, int)’:
./OpenShadingLanguage-Release/src/liboslexec/llvm_util.cpp:1182:15: error: ‘OSL::pvt::LLVM_Util::IRBuilder {aka class llvm::IRBuilder<true, llvm::ConstantFolder, llvm::IRBuilderDefaultInserter<true> >}’ has no member named ‘CreateCall5’
     builder().CreateCall5 (func, ptr, fill_val, len, constant(align),

./OpenShadingLanguage-Release/src/liboslexec/llvm_util.cpp: In member function ‘void OSL::pvt::LLVM_Util::op_memcpy(llvm::Value*, llvm::Value*, int, int)’:
.OpenShadingLanguage-Release/src/liboslexec/llvm_util.cpp:1205:15: error: ‘OSL::pvt::LLVM_Util::IRBuilder {aka class llvm::IRBuilder<true, llvm::ConstantFolder, llvm::IRBuilderDefaultInserter<true> >}’ has no member named ‘CreateCall5’
     builder().CreateCall5 (func, dst, src,

./OpenShadingLanguage-Release/src/liboslexec/llvm_util.cpp: In member function ‘llvm::Value* OSL::pvt::LLVM_Util::GEP(llvm::Value*, int, int)’:
./OpenShadingLanguage-Release/src/liboslexec/llvm_util.cpp:1246:59: error: no matching function for call to ‘llvm::IRBuilder<true, llvm::ConstantFolder, llvm::IRBuilderDefaultInserter<true> >::CreateConstGEP2_32(llvm::Value*&, int&, int&)’
     return builder().CreateConstGEP2_32 (ptr, elem1, elem2);

In file included from ./OpenShadingLanguage-Release/src/liboslexec/llvm_util.cpp:54:0:
/usr/include/llvm/IR/IRBuilder.h:1104:10: note: candidate: llvm::Value* llvm::IRBuilder<preserveNames, T, Inserter>::CreateConstGEP2_32(llvm::Type*, llvm::Value*, unsigned int, unsigned int, const llvm::Twine&) [with bool preserveNames = true; T = llvm::ConstantFolder; Inserter = llvm::IRBuilderDefaultInserter<true>]
   Value *CreateConstGEP2_32(Type *Ty, Value *Ptr, unsigned Idx0, unsigned Idx1,

/usr/include/llvm/IR/IRBuilder.h:1104:10: note:   candidate expects 5 arguments, 3 provided
src/liboslexec/CMakeFiles/oslexec.dir/build.make:857: recipe for target 'src/liboslexec/CMakeFiles/oslexec.dir/llvm_util.cpp.o' failed

Everything else seems to build though...

OSL is known not to work with LLVM > 3.5.
I'm working on this. Closing.

I was just assuming from your latest commits that you were able to get it to build with 3.6.

Current status: It compiles against 3.6, and llvmutil_test (unit tests) works, but full-blown OSL compilation results in shaders that crash. But even if that was fixed, my implementation for llvm 3.6 has unacceptably bad memory bloat, because the trick I used with the old JIT to aggressively free LLVM memory (other than the resulting binary JIT code) doesn't work with 3.6 due to changed APIs and the way that MCJIT works, so I wouldn't consider it production-worthy solution.
I'm actually trying to push to LLVM 3.7 and beyond with ORC JIT, which as I understand it recaptures some of the memory reclamation that we desperately need. I'm working on this right now. If it works well, it may be that we skip LLVM 3.6 entirely and jump straight to only versions of ORC JIT (3.7+). But the production viability of this still is awaiting my finding out how the time and memory performance compare to the system we have built around LLVM 3.4/3.5.

@lgritz Can't post this on your Github as you don't allow issues, so I hope you get this. I was trying your Orc Jit patches from here: https://github.com/lgritz/OpenShadingLanguage/tree/lg-orcjit
I applied them to the latest master code. I compiled with LLVM 3.8.1 and trying to use with Blender 2.78. I followed the script from here: http://elbrujodelatribu.blogspot.co.uk/2013/04/blender-cycles-osl-mandelbrot-fractal.html
To create my test script with something known to work.
However, Blender crashes with this:
src/liboslexec/llvm_instance.cpp:1097: failed assertion 'll.get_compiled_function(name)'
Aborted (core dumped)
That function was added with your code. I was wondering if you might be able to help me figure this out.
Again, sorry for posting here, but it's kinda relevant to this bug and the only way I can get a hold of @lgritz
Cheers.

The "lgritz" account is my private work area / boneyard, so of course it does not allow issues to file against it. You will find trees there in various states of disrepair, abandonment, and half-assedness. Never assume anything there works, it's not intended to ever be pulled by anybody.
The official OSL area is the imageworks/OpenShadingLanguage account. The currently supported LLVM versions are 3.4 and 3.5.


[Migration] What's missing

[ ] update FranklinTemplates (minor release)
[x] literate files
[x] tags

[ ] docs?

[x] RSS

[ ] docs

[ ] sitemap, robots + robots disallow
[x] pagination

[ ] docs?

[x] * environments (equations)
[ ] lunr path
[x] slug
[x] keep path (avoid /.../) e.g. google analytics + add some docs about this (https://support.google.com/webmasters/answer/9008080?hl=en#html_verification)
[ ] bib ref + docs
[x] add a function hfun_last_modified see #114 ; bring fd_date from Franklin to do this with locales

Maybe

[ ] something interactive when calling newsite that indicates a message about setting prepath (this should ultimately be in FranklinTemplates and should be done afterwards, pointing to the docs)
[ ] prerendering pass (probably not baked in, better to have either a demo of how to do it for KaTeX / HL + maybe done in CI)

Later

date stuff (locales, months etc) (gv date_format, date_days, etc)

Notes

div_content -> content_class
fd_tag -> tag_name (btw maybe that tag_str should be an allowed alias)


Add resource compare option to CRD

Hello,
ArgoCD supports capability to ignore aggregated ClusterRoles by adding following to Argo's ConfigMap:
  resource.compareoptions: |
    # if ignoreAggregatedRoles set to true then differences caused by aggregated roles in RBAC resources are ignored.
    ignoreAggregatedRoles: true

It would be great if this could be configured using ArgoCD CRD.
Best regards,
Bostjan

Was this eve implemented?

I played around with it and saw that this can be sorted with spec.extraConfig.resources.compareoptions.ignoreAggregatedRoles: true


Does clientv3 support 32-bit system?

According to the op-guide on supported systems, etcd server has known issues on 32-bit systems due to a bug in the Go runtime.
The issues are mainly caused by the usage of package sync/atomics. And the clientv3 package doesn't import the sync/atomics, does it mean that clientv3 can be used stably in 32-bit system?

does it mean that clientv3 can be used stably in 32-bit system?

Hi @Pc6 on the client level this should be OK as your calls to the server are presumably over TCP thus archtecture agnostic . So as long as the binary compiles I believe this should be stable. Think of a 32bit browser connecting to a 64bit web server.
Would you mind testing and reporting back your results? If all is well maybe you could append the docs? Thanks!

Sure, I'm glad to : )

@hexfusion as for the test result, I have been tested the clientv3 in 32-bit system with the test cases presented in the package. The client performs well. My testing platform is Ubuntu Server 16.04.1 LTS 32-bit, and go version is go1.10.1 linux/386. Should I offer more test cases so that I can append the docs?

@Pc6 If you use 64-bit for server, 32-bit client should just work. But make sure to test it. We don't say it's stable in the doc, because we don't run all integration tests for 32-bit. You might try run

GOARCH=386 CPU=4 PASSES='integration' ./test

And report to us if you find any bugs.


MAYBE NO BUG I always get green candles from historic_prices

I am getting a bit mad.
When I call historic prices, 'close' is always higher or same as 'open'
 data = pd.DataFrame(client.get_product_historic_rates(product, None, None, 300), columns=('time', 'open', 'high', 'low', 'close', 'volume'))
(Pdb) data
           time      open      high       low     close    volume
0<PHONE_NUMBER>  43277.04  43381.28  43328.53  43295.79  0.895786
1<PHONE_NUMBER>  43245.81  43376.39  43289.20  43337.49  2.657281
2<PHONE_NUMBER>  43215.02  43289.48  43282.52  43270.07  3.115343
3<PHONE_NUMBER>  43241.98  43355.00  43306.87  43280.41  9.459572
4<PHONE_NUMBER>  43281.95  43360.71  43360.58  43295.80  2.105679
..          ...       ...       ...       ...       ...       ...
295<PHONE_NUMBER>  40675.47  40805.46  40801.05  40740.01  2.508802
296<PHONE_NUMBER>  40796.18  40835.05  40819.96  40801.80  1.037107
297<PHONE_NUMBER>  40802.84  40877.22  40820.00  40842.17  1.680386
298<PHONE_NUMBER>  40781.36  40809.03  40801.66  40805.00  2.128685
299<PHONE_NUMBER>  40768.70  40843.26  40802.43  40809.03  2.047796

Pdb) data.loc[data.close < data.open]
Empty DataFrame
Columns: [time, open, high, low, close, volume]

Any help appreciated

The order of data values is time, low, high, open, close, volume.

@robertbasham you have no idea how much you made my day. thanks!


Collective Close Operational

This PR creates an explicit close_operational transaction that can only be called by collective members in order to close a vote with Operational priority. The original close extrinsic now has Normal priority and can be called by anyone.
This is just a little bit safer against spam attacks from irrational users who may want to waste their money in order to fill a block. In this case, the average user does not have access to generate arbitrary Operational transactions.

Needs a signed extension

We are done with our review for this PR - please refer to issue #7 in the internal tracker.

Needs a signed extension

I guess this PR is not ready for review anymore ?

So, anyone working on this?

closing due to a lack of progress.


added finalized assets from teams, finished el joaquin articles, adde…

…d drawn portraits to bios, adjusted title screen

god I hate fixing merge conflicts, requires maximum percolation from me


Build for step builder failed due to dial unix /var/run/docker.sock: connect: connection refused

I'm trying to build a dev container on my OSX machine for an existing Rails app, which uses some private gems so needs my ssh key passed in (which is what brought me to this project!). I can't get past the part where it's trying to connect to a Docker socket.
This is the command I'm running:
sudo habitus_darwin_amd64 -f ./config/containers/build.yml --build host=$(ipconfig getifaddr en0) --host unix:///var/run/docker.sock --binding=$(ipconfig getifaddr en0) --secrets=true
Which returns
2017/05/29 13:27:20 ▶ Using './config/containers/build.yml' as build file
2017/05/29 13:27:20 ▶ Collecting artifact information
2017/05/29 13:27:20 ▶ Building 1 steps
2017/05/29 13:27:20 ▶ Step 0 - builder: builder
2017/05/29 13:27:20 ▶ Parallel build for builder
2017/05/29 13:27:20 ▶ Building builder
2017/05/29 13:27:20 ▶ Parsing and converting 'Dockerfile'
2017/05/29 13:27:20 ▶ Starting API on 8080
2017/05/29 13:27:20 ▶ Writing the new Dockerfile into Dockerfile.generated
2017/05/29 13:27:20 ▶ Building the builder image from Dockerfile.generated
2017/05/29 13:27:28 ▶ Build for step builder failed due to dial unix /var/run/docker.sock: connect: connection refused

build.yml just contains:
build:
  version: 2016-03-14
  steps:
    builder:
      name: builder
      dockerfile: Dockerfile
      secrets:
        id_rsa:
          type: file
          value: _env(HOME)/.ssh/id_rsa
      cleanup:
        commands:
          - rm -rf /root/.ssh/

docker info returns:
Containers: 0
 Running: 0
 Paused: 0
 Stopped: 0
Images: 0
Server Version: 17.05.0-ce
Storage Driver: aufs
 Root Dir: /mnt/sda1/var/lib/docker/aufs
 Backing Filesystem: extfs
 Dirs: 0
 Dirperm1 Supported: true
Logging Driver: json-file
Cgroup Driver: cgroupfs
Plugins:
 Volume: local
 Network: bridge host macvlan null overlay
Swarm: inactive
Runtimes: runc
Default Runtime: runc
Init Binary: docker-init
containerd version: 9048e5e50717ea4497b757314bad98ea3763c145
runc version: 9c2d8d184e5da67c95d601382adf14862e4f2228
init version: 949e6fa
Security Options:
 seccomp
  Profile: default
Kernel Version: 4.4.66-boot2docker
Operating System: Boot2Docker 17.05.0-ce (TCL 7.2); HEAD : 5ed2840 - Fri May  5 21:04:09 UTC 2017
OSType: linux
Architecture: x86_64
CPUs: 1
Total Memory: 1.955GiB
Name: default
ID: D7ID:PG7A:X2I2:L2VD:FXSP:7VXH:YYPN:T25R:VNMS:ZHYJ:5BAV:RC7Z
Docker Root Dir: /mnt/sda1/var/lib/docker
Debug Mode (client): false
Debug Mode (server): true
 File Descriptors: 16
 Goroutines: 24
 System Time: 2017-05-29T19:22:35.212446204Z
 EventsListeners: 1
Registry: https://index.docker.io/v1/
Labels:
 provider=virtualbox
Experimental: false
Insecure Registries:
 <IP_ADDRESS>/8
Live Restore Enabled: false

What am I missing?

Hi @MathieuGilbert this happening when you miss an extra '/' in your --host setting.
--host=unix:///var/run/docker.sock will work of mac.
--host=unix://var/run/docker.sock gives you the error.
can you check you use the right name of the sock?

Thanks @kamerblauwlicht. If I use unix:// (or a different path), it gives a different error:
Build for step builder failed due to dial unix /run/docker.sock: connect: no such file or directory
"No such file or directory" vs "connection refused", so it seems like the command is correct, just some config isn't allowing a connection to the VM's docker process.
Does this depend on my local machine's Docker or Virtualbox config?

hi @MathieuGilbert
it does depend how you install your docker engine. if you use the Docker runtime on Mac you use unix:///var/run/docker.sock but if you run inside a VM using Linux you use unix://var/run/docker.sock

Ok, I guess I'll try reinstalling all the Docker and Habitus components and starting from scratch with a simple app. I just thought it might be a Habitus issue since I'm able to build the Docker container on its own (just without the SSH key). Thanks anyways!


[2.10.5] 'Multiple widgets used the same GlobalKey' (however global key only used by one widget)

The code below has been working without issues for all the devices previously tested on, both iOS and Android. However, recently on Flutter v.2.10.5 on an physical iPhone 13 iOS 15.4 I get a 'Multiple widgets used the same GlobalKey' error with the code shown below. For other iOS and Android devices the code continues to work fine.
From the error it looks like two versions of the same widget exists causing the error, but I am not quite sure why that would happen?
Flutter code:
final PageStorageBucket _bucket = PageStorageBucket();
final GlobalKey bottomNavigationBarKey = GlobalKey(debugLabel: 'barKey');
double? _navigationBarHeight;

@override
Widget build(BuildContext context) {
  return Scaffold(
    body: PageStorage(
      child: pages[_selectedIndex],
      bucket: _bucket,
    ),
    bottomNavigationBar: AnimatedContainer(
      duration: const Duration(milliseconds: 300),
      height: _navigationBarHeight
      child: SingleChildScrollView(
        child: SafeArea(
          child: SizedBox(
            height: 55.0,
            child: BottomNavigationBar(
              // Global key added here
              key: bottomNavigationBarKey,
              items: ...
            ),
          ),
        ),
      ),
    ),
  ),
}

Error message:
════════ Exception caught by widgets library ═══════════════════════════════════
The following assertion was thrown while finalizing the widget tree:
Multiple widgets used the same GlobalKey.

The key [GlobalKey#9e720 barKey] was used by multiple widgets. The parents of those widgets were:
- SizedBox(height: 55.0, renderObject: RenderConstrainedBox#9f47f relayoutBoundary=up3)
- SizedBox(height: 55.0, renderObject: RenderConstrainedBox#25bf8 relayoutBoundary=up3 NEEDS-PAINT)
A GlobalKey can only be specified on one widget at a time in the widget tree.
When the exception was thrown, this was the stack
#0      BuildOwner._debugVerifyGlobalKeyReservation.<anonymous closure>.<anonymous closure>.<anonymous closure>
package:flutter/…/widgets/framework.dart:2868
#1      _LinkedHashMapMixin.forEach (dart:collection-patch/compact_hash.dart:539:8)
#2      BuildOwner._debugVerifyGlobalKeyReservation.<anonymous closure>.<anonymous closure>
package:flutter/…/widgets/framework.dart:2815
#3      _LinkedHashMapMixin.forEach (dart:collection-patch/compact_hash.dart:539:8)
#4      BuildOwner._debugVerifyGlobalKeyReservation.<anonymous closure>
package:flutter/…/widgets/framework.dart:2811
#5      BuildOwner._debugVerifyGlobalKeyReservation
package:flutter/…/widgets/framework.dart:2876
#6      BuildOwner.finalizeTree.<anonymous closure>
package:flutter/…/widgets/framework.dart:2935
#7      BuildOwner.finalizeTree
package:flutter/…/widgets/framework.dart:3016
#8      WidgetsBinding.drawFrame
package:flutter/…/widgets/binding.dart:884
#9      RendererBinding._handlePersistentFrameCallback
package:flutter/…/rendering/binding.dart:363
#10     SchedulerBinding._invokeFrameCallback
package:flutter/…/scheduler/binding.dart:1144
#11     SchedulerBinding.handleDrawFrame
package:flutter/…/scheduler/binding.dart:1081
#12     SchedulerBinding._handleDrawFrame
package:flutter/…/scheduler/binding.dart:995
#16     _invoke (dart:ui/hooks.dart:151:10)
#17     PlatformDispatcher._drawFrame (dart:ui/platform_dispatcher.dart:308:5)
#18     _drawFrame (dart:ui/hooks.dart:115:31)
(elided 3 frames from dart:async)
════════════════════════════════════════════════════════════════════════════════

Flutter doctor -v
[✓] Flutter (Channel stable, 2.10.5, on macOS 12.3.1 21E258 darwin-arm)
    • Flutter version 2.10.5
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 5464c5bac7 (7 days ago), 2022-04-18 09:55:37 -0700
    • Engine revision 57d3bac3dd
    • Dart version 2.16.2
    • DevTools version 2.9.2

[✓] Xcode - develop for iOS and macOS (Xcode 13.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • CocoaPods version 1.11.3

[✓] VS Code (version 1.66.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.38.1

Hi @mzkai, please provide a complete minimal reproducible code sample so that we can investigate this.
Thank you


footer doesn't stick to bottom on smaller screens

need that sticky footer tho

yeah if you feel like trying to fix that, be my guest. That's like... kinda a tough thing

if @j6k4m8 says its hard, then its not worth anybody doing.


Winget Repair - Eliminate installer type mapping for MSI/WIX and MSIX NonStore ,code refactoring & E2E Test Coverage

Repair Command updates:

Code changes eliminate installer type mapping for MSI/WIX and MSIX NonStore, leveraging native platform support for repairs.
Refactored code for better readability and maintainability.

AppInstallerTestExeInstaller - Repair support

Refactored AppInstallerTestExeInstaller to support repair operations. The code now accommodates Modify Repair, Uninstaller Repair, and Installer Repair.
Minor refactoring is also part of this update

E2E Test Coverage:

Added E2E tests for winget, targeting installer types such as

MSI,
NonStore MSIX,
Burn, Nullsoft, Inno, and Exe.

These tests aim to ensure reliability across Modify Repair, Uninstaller Repair, and Installer Repair scenarios.

How Validated:

Configured LocalhostWebServer for local execution.
Executed WingetRepair Tests via Visual Studio TestExplorer, confirming all tests passed on the local machine

[x] I have signed the Contributor License Agreement.
[ ] This pull request is related to an issue.

Microsoft Reviewers: Open in CodeFlow

/azp run


Merge into base?

Hey everyone. Looks like this fork has gotten quite ahead, and it has many features I need in a module I'm working on (particularly a lot of the trouble and other events).
Any thoughts on getting this fork merged into the base? I took a quick glance and it would definitely be a breaking change as-is, mainly due to a different structure in the event data that is emitted. So if it is kept as-is, it will need to me a major sem-ver change.
@kbin76 What are your thoughts? Are your modifications finished/stable?

Hi,
yes, I think i'm quite finished with what i wanted to do. However, I have no idea on what this module was used for originally. And due to that, I assumed that my changes was going to break something for someone else, so I never bothered submitting a pull request. But if you want to merge it with the master, please do, but I can't answer for the consequences... :-)...

Note that i have modified package.json, changes which you shouldn't merge into the master.
--Kalle

@kbin76 I'd be interested in the changes you made to evl-mqtt-bridge

@mhdawson I don't think i've ruined any of the original functionality in evl-mqtt-bridge :-), so it should be possible to merge with your original code without too much hassle, if you want to... I've added two additional output formats, one that is based on a variety of mqtt topics and boolean values (on/off) and another format that spits out json events (as received from nodealarmproxy) to one mqtt topic... the only problem is that it's sort of dependant on my changes to NodeAlarmProxy to work ok...
Unfortunately, I don't have too much time to spend on this at the moment (hobby stuff that competes with work, family, etc)... :-/

@dstapleton92 @kbin76  @mhdawson  Hey, so I don't really use / need nodealarm proxy anymore.  It was originally used to proxy envisalink to smartthings for home automation (but I no longer have an envisalink OR smarthings).  @kbin76 since you have a number of improvements and seem to be actively developing it I could either transfer ownership to you or create an organization for it (which is apparently free to do?)  I can then figure out figure out how to transfer npm publishing rights.
I'm leaning towards an organization so it's easier for others to contribute
What do you all think?

@martzcodes sounds good.  In terms of transferring npm publishing rights, I think all you need to do is add new people as collaborators who can publish.  You can then either stay in the list of collaborators who can publish or drop off if for some reason you don't want to remain.

@mhdawson @kbin76 ok, transfered the repo to an organization, made you guys owners and added @mhdawson as a npm publisher (ran into an error when trying to add @kbin76 )  I'll stay on board but likely won't do anything

Oh, and I updated the package.json with the actual repo.  If anyone else on this thread wants access, let those guys know


.Net: Add Kernel.CreateBuilder()

This item is to allow a user to use the KernelBuilder in DI.

If we want to do this, I expect it would look like this:
https://github.com/microsoft/semantic-kernel/compare/main...stephentoub:semantic-kernel:createbuilder


Commander : Effectively track failure reporting and handle hotplug sensors

Now commander will report all issues when a new link is connected. So no messages are lost.
:) Also, with my changes, it will now wait in ARMING_STATE_INIT till all primary sensors come online.
This will need some careful review, but I'm confident this works 100% as tested. Please let me know what else is needed.
New output when link first connects (hotplug sensor not up yet though) :
[20:14:12.645 - COMP:1] Info: new data link connected #0
[20:14:12.861 - COMP:1] Critical: warning: primary compass not operational
[20:14:12.964 - COMP:1] Critical: Not ready to fly: Flying with USB connected prohibited
[20:14:13.068 - COMP:1] Critical: Not ready to fly: Sensors need inspection

Note to self : Figure out a way to flag external/hotplug sensors during calibration, and not play annoying error tune right at boot before it has come up.
Suggestions, Lorenz?

I would propose to not warn for the first two seconds. After that it's unlikely a sensor will still show up without user intervention. So the first two seconds after boot it should just flag the system as by ready, but not warn via MAVLink or buzzer.

Implemented. Works perfectly. We don't warn the user for upto 4 seconds after booting (this value was the minimum required one, tested with UAVCAN mag)

Awesome work! Just going through it now.

OK, I just added some user experience tweaks to warn the user later if sensors fail, etc. This feels very polished now.
Timeout is set to 5 seconds, which works fine with USB, but on battery, with the faster boot, and UAVCAN sensors ridiculously taking around 8-9 seconds (after commander starts) to come up, the system starts warnings, before the sensors come up.
Now the weird thing is, if I set the timeout to > 5s commander never goes into a proper failure state if nothing is connected. Tracking it down now. If you find anything please let me know.

Hard to tell why it's different on battery without sitting in front of the system. Have you pinged @pavel-kirienko to see why it takes so long to enumerate?

Ok, so I fixed the remaining small user-experience issues, other than the long enumeration times. The system works exactly as expected now, and warns perfectly in every condition. I check with all sorts of combinations - bad calibrations, mag unplugged, plugged, uavcan enabled/disabled etc. and it works great!
Timeout is set to 8 seconds till Pavel can provide us with faster enumeration times. System won't warn till 8 seconds are over -- but it will still refuse to go to STANDBY silently.
I also added a small differentiation between pre-arm and pre-flight. USB power is only checked if we are doing a pre-arm check, not for pre-flight (as in bench tests or otherwise) This can be expanded later to encompass more system checks.

@LorenzMeier Could you please give a high-level review of this meanwhile ? Does everything look OK, or does anything need more re-factoring/optimization?

This looks really good. I will cross-test and get this in tomorrow.


@react-stately/checkbox is not resolved error while using useTheme()

install adaptui in a fresh expo app.
yarn add<EMAIL_ADDRESS>

use the useTheme() hook in the app
const tailwind = useTheme()

Temporary fix
yarn add  @react-stately/checkbox


Informative message for old commands

This version uses new slash commands, but a lot of users wouldn't be aware of this change and thus expect old commands (with ? prefix) to work properly. We should respond to these commands with a message that asks to use the new slash command instead.

Can I do this one?

Thanks for contributing, I've assigned you the issue.


StateKeeper fails to persist state on Android

Hello,
Now I'm not entirely sure if this is due to me not knowing what I'm doing (quite probable) or a bug with persistence, but StateKeeper fails to actually save the state when the application is terminated on Android. I am unable to reproduce this on Desktop.
I've gone ahead and stripped down my project to the bare minimum for an easier repro, which you can find here.
The relevant parts of that (as far as I can tell) are the following:
My root model:
interface RootComponent : BackHandlerOwner {
    val data: Value<Model>
    fun input(token: String)

    data class Model(
        val token: String? = null,
    )
}

class DefaultRootComponent(
    val ctx: ComponentContext,
) : RootComponent, ComponentContext by ctx {

    override val data = MutableValue(
        RootComponent.Model(
            token = stateKeeper.consume(key = "TOKEN", strategy = serializer<String>())
        )
    )

    init {
        stateKeeper.register(key = "TOKEN", strategy = serializer<String>()) {
            // This always gets printed, and yet, on Android, the token is not persisted.
            // On Desktop (JVM) the persistence works fine though.
            println("Looks like it is time to save the token, which is: ${data.value.token}")
            data.value.token
        }
    }

    override fun input(token: String) {
        data.value = data.value.copy(token = token)
    }
}

and my main activity:
class MainActivity : ComponentActivity() {
    override fun onCreate(savedInstanceState: Bundle?) {
        super.onCreate(savedInstanceState)
        enableEdgeToEdge()
        val root = DefaultRootComponent(defaultComponentContext())

        setContent {
            AppTheme {
                App(root)
            }
        }
    }
}

Reproduction steps:

Clone repo, open in Android Studio
Launch the project with the "Android App" preset (I've tested this on my personal API33 device and an emulator running API35)
Type anything into the textfield for the token
Exit the app & close it fully so it is not running in the background
Reopen the app

Expected Result:
The text field's value is populated by the text from persistence by the statekeeper
Actual Result:
The text field is empty
Trying the same thing with the "Desktop" launch preset works correctly.

Thanks in advance, and let me know if I should provide any additional info!

Hmm, upon some further testing, the wasmJS target also doesn't seem to work, but that is likely due to me not knowing how to configure the statekeeper for that platform.

On Android, StateKeeper works similarly to SavedStateHandle, i.e. the state is only saved if the process is killed by the system due to memory pressure. The state is discarded if you kill the app manually. You can try the following to simulate process death: minimize the app and run adb shell am kill <package_name>, then the state should be restored if you open the app again via the shortcut.
As of wasmJs, StateKeeper requires some manual setup. You can hook it either to sessionStorage (persistent over page refreshes) or localStorage (persistent even if you close the tab and open the app again). I've got an example here: https://github.com/arkivanov/Minesweeper/blob/master/composeApp/src/wasmJsMain/kotlin/Main.kt#L23.

On Android, StateKeeper works similarly to SavedStateHandle, i.e. the state is only saved if the process is killed by the system due to memory pressure. The state is discarded if you kill the app manually. You can try the following to simulate process death: minimize the app and run adb shell am kill <package_name>, then the state should be restored if you open the app again via the shortcut.
As of wasmJs, StateKeeper requires some manual setup. You can hook it either to sessionStorage (persistent over page refreshes) or localStorage (persistent even if you close the tab and open the app again). I've got an example here: https://github.com/arkivanov/Minesweeper/blob/master/composeApp/src/wasmJsMain/kotlin/Main.kt#L23.

Thanks for the quick reply! So I assume I shouldn't use StateKeeper to store client state/settings then, given this limitation of Android. Do you have any suggestions on what I should use instead?
P.S. Got WASM to work, thanks!

Yeah! For settings, you can try using multiplatform-settings library. You can also check SQLDelight for database.

Looks promising, thanks for the very quick & concise replies! Closing now.


Color legend for plate maps

Plate map cells change color after an entry has been added. Sometimes, it's not clear to the wetlab what the colors represent.

Either Amanda or myself would be the best people to handle this; it doesn't need to be both people.

@fedarko This would be a nice to have for the full launch, but it's just not as high a priority as the other issues. This would be a good thing for George to dig through the code and document, and if he needs help you might be able to provide it, since you're also working in the plate-mapper area.

@charles-cowart Got it! Between George and I, I think this issue should be handleable.
FYI to @gwarmstrong: from what I can tell, the code that handles the individual well styles does this via CSS classes (which seem to all be defined here). I would imagine that we could solve this fairly simply by just applying each of these classes to a <div> or something, and then wrapping all of that off to the side of the big plate div. (Charlie, feel free to yell at me if this is summary is lacking :)

@fedarko there will be no yelling. :)

I currently have a mock up going for this here
Before:

After:

@charles-cowart  @fedarko Thoughts on the initial layout? I can move this over to a PR if more appropriate

@gwarmstrong Looks great, thanks! I think moving two of them to the right to make it a 2x2 square rather than a 1x4 is a better use of space; it'll prevent people from having to scroll down more to view the entire legend.

@charles-cowart
How about now?

Also, is there any way to get feedback from the lab on whether the legend descriptions are reasonable?

Amanda and I looked them over and we have a few comments I'll pass on later
this afternoon.
On Thu, Aug 15, 2019 at 11:39 AM George Armstrong<EMAIL_ADDRESS>wrote:

Also, is there any way to get feedback from the lab on whether the legend
descriptions are reasonable?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jdereus/LabControl/issues/432?email_source=notifications&email_token=AKFU7E6KEN7WZGWCEHBEQPLQEWPEPA5CNFSM4HDPABJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4MULDQ#issuecomment-521749902,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKFU7EZWVJLV3EGQ5PRAYALQEWPEPANCNFSM4HDPABJA
.

Great, should I go ahead and submit a PR, and we can handle the commenting there?

sure! I'll add them as part of a review
On Thu, Aug 15, 2019 at 1:16 PM George Armstrong<EMAIL_ADDRESS>wrote:

Great, should I go ahead and submit a PR, and we can handle the commenting
there?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/jdereus/LabControl/issues/432?email_source=notifications&email_token=AKFU7E67HSXOROONV57UCXDQEW2QVA5CNFSM4HDPABJKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD4M4COA#issuecomment-521781560,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AKFU7EYVJJUTRSHKDZJTUO3QEW2QVANCNFSM4HDPABJA
.


skip_covered and skip_empty for HTML. #1090

The skip_covered and skip_empty settings in the configuration file
can now be specified in the [html] section, so that text reports and HTML
reports can use separate settings.  The HTML report will still use the
[report] settings if there isn't a value in the [html] section.

Looking forward to this release 🙇🏻

Looking forward to this release 🙇🏻


[UNDERTOW-1834] Fix for IBM JDK and HTTP2/ALPN.

https://issues.redhat.com/browse/UNDERTOW-1834
There is a difference in IBM JDK TLS ciphersuite names versus their
Oracle JDK counterparts, see e.g. [1].
This discrepancy causes issue in usage of HTTP2 with IBM JDK since
we check enabled ciphersuite based on the name in Oracle JDK variant
only. So if there is an incomming connection from client that offers
IBM names of the ciphersuite, we simply fail to use ALPN and HTTP2
with it consequently.
This change should fix such issue.
[1] https://www.ibm.com/support/knowledgecenter/SSFKSJ_9.0.0/com.ibm.mq.dev.doc/q113210_.htm

Thanks @jstourac !


glib/BindingBuilder: add concrete type based transform setters

Not sure about the naming though :)
Fixes https://github.com/gtk-rs/gtk-rs-core/issues/382

Should be good now! :)

@bilelmoussaoui What do you think?


[release/0.8] Support specifying a specific logrus log level for shim log output

Sometimes debug is a bit too noisy and can cause log rotation at a higher than
ideal rate.
This will be accompanied by an audit of our use of log levels throughout to make sure
they actually fit what level they're under.
Signed-off-by: Daniel Canter<EMAIL_ADDRESS>(cherry picked from commit a2d897c201cc1178f6e3ee5b1df26c13fe760893)
Signed-off-by: Daniel Canter<EMAIL_ADDRESS>

Realized this was never pulled into the release/0.8 branches. Would be nice to have for a new ctrd 1.5 release, and helps with the merge conflicts from just trying to cherry-pick https://github.com/microsoft/hcsshim/pull/1197


Always use node-fetch and stop polyfilling

Due to a bug in undici (https://github.com/nodejs/undici/issues/1776)
that is affecting many versions of Node and Next.js,
we want a workaround to ensure our users don't see this.
Therefore, we're forking isomorphic-unfetch to always use node-fetch
on Node to avoid falling back to global.fetch (undici).
Also, isomorphic-unfetch was polyfilling, which we want to avoid.

It will be easier to review this PR commit-by-commit, since in the first commit I refactored the tests a bit.


Double definition of ray in requirements-optional.txt

🐛🐛 Bug Report
⚗ Current Behavior
A double definition of ray in the requirements-optional.txt is not needed.
Input Code
https://github.com/activeloopai/Hub/blob/5f1ab722667552a3ae049b4f465b3d140f70487d/requirements-optional.txt#L4
https://github.com/activeloopai/Hub/blob/5f1ab722667552a3ae049b4f465b3d140f70487d/requirements-optional.txt#L8
🧰 Possible Solution  (optional)
Remove ray>=1.0

@Anselmoo good catch! Mind submitting a PR and I'll merge?

@mynameisvinn, thx for the feedback. PR is already submitted #798


Uncaught TypeError: Cannot read property 'clientWidth' of null

I get "Uncaught TypeError: Cannot read property 'clientWidth' of null" when running the sample code: https://jsfiddle.net/6rqxusw5/6/.
Tested with chrome and safari but always get same error.
Also, for some reason, the jsfiddle code doesn't render the chart.
Thanks in advance.

Nevermind, the code I was using is for v < 1.0...


Add legacy objects to apache

@gingerwizard Keeping two different version of the kibana dashboard/objects for this.  I am updating the corresponding blog post to reference the -4 version, and we will make a new, updated blog post for kibana-5

or @hstephenson


generate-cask-ci-matrix: fix incorrect error being raised

[ ] Have you followed the guidelines in our Contributing document?
[ ] Have you checked to ensure there aren't other open Pull Requests for the same change?
[ ] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.
[ ] Have you successfully run brew style with your changes locally?
[ ] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

The comparison between the working directory and tap path did not function correctly on GitHub actions, because we don't checkout the tap to a standard location when using Setup Homebrew.
The command must be run from within the tap directory, which is the default path in GitHub actions, so this should not be an issue.

Thanks @bevanjkay!


[YUNIKORN-2340] Upgrade actions versions in Github Action workflow

What is this PR for?
Bump below actions verions to surpress the "Node.js 16 actions are deprecated." warning message:

actions/checkout (v3 -> v4)
actions/setup-node (v3 -> v4)
actions/setup-go (v3 -> v5)   (Only support node js 20 in v5)

What type of PR is it?

[ ] - Bug Fix
[x] - Improvement
[ ] - Feature
[ ] - Documentation
[ ] - Hot Fix
[ ] - Refactoring

Todos
Update below repo's actions version:

yunikorn-k8shim
yunikorn-core
yunikorn-scheduler-interface

What is the Jira issue?
https://issues.apache.org/jira/browse/YUNIKORN-2340
How should this be tested?
Tested in Github action.  Create a pull request to master branch and check the Actions result.
ex: https://github.com/chenyulin0719/yunikorn-web/actions/runs/7694231502
Screenshots (if appropriate)
After:

Before:

Questions:
NA

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

Comparison is base (e307b08) 66.66% compared to head (a9fc03f) 66.66%.

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #161   +/-   ##
=======================================
  Coverage   66.66%   66.66%
=======================================
  Files           1        1
  Lines          30       30
=======================================
  Hits           20       20
  Misses          7        7
  Partials        3        3

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


remove the library including its functionality to utki library

added utf8 stuff to utki. Need to delete the unikod from all depending projects now.

dependency on unikod removed from all my libs. Done.


Indefinite resubmission of jobs.

I ran across a problem today where jade continued to submit jobs even after the job had completed.
This resulted in an explosion of HPC submissions which may be a very large problem for users who encounter this bug.
This may have coincided with exceeding my HPC time allocation limit.
A snippet from one of the job .e files looks like this:
2021-06-19 07:28:54,995 - INFO [jade.jobs.cluster cluster.py:488] : Wrote config version 151 reason=promote_to_submitter hostname=r7i3n16
2021-06-19 07:28:55,056 - INFO [jade.hpc.hpc_submitter hpc_submitter.py:78] : Created split config file jade_output_missing/config_batch_1.json with 20 jobs
2021-06-19 07:28:55,058 - INFO [jade.utils.utils utils.py:64] : Writing jade_output_missing/run_batch_1.sh
2021-06-19 07:28:55,061 - INFO [jade.utils.utils utils.py:64] : Writing jade_output_missing/medium_batch_1.sh
2021-06-19 07:28:55,062 - INFO [jade.hpc.hpc_manager hpc_manager.py:203] : Created submission script jade_output_missing/medium_batch_1.sh
2021-06-19 07:28:55,092 - INFO [jade.hpc.hpc_manager hpc_manager.py:212] : job 'medium_batch_1' with ID=7017599 submitted successfully
2021-06-19 07:28:55,093 - INFO [jade.hpc.hpc_submitter hpc_submitter.py:458] : Assigned job_ID=7017599 name=medium_batch_1
2021-06-19 07:28:55,097 - INFO [jade.hpc.hpc_submitter hpc_submitter.py:78] : Created split config file jade_output_missing/config_batch_2.json with 20 jobs
2021-06-19 07:28:55,098 - INFO [jade.utils.utils utils.py:64] : Writing jade_output_missing/run_batch_2.sh
2021-06-19 07:28:55,101 - INFO [jade.utils.utils utils.py:64] : Writing jade_output_missing/medium_batch_2.sh
2021-06-19 07:28:55,103 - INFO [jade.hpc.hpc_manager hpc_manager.py:203] : Created submission script jade_output_missing/medium_batch_2.sh
2021-06-19 07:28:55,131 - INFO [jade.hpc.hpc_manager hpc_manager.py:212] : job 'medium_batch_2' with ID=7017600 submitted successfully
2021-06-19 07:28:55,131 - INFO [jade.hpc.hpc_submitter hpc_submitter.py:458] : Assigned job_ID=7017600 name=medium_batch_2
2021-06-19 07:28:55,135 - INFO [jade.hpc.hpc_submitter hpc_submitter.py:78] : Created split config file jade_output_missing/config_batch_3.json with 20 jobs
2021-06-19 07:28:55,136 - INFO [jade.utils.utils utils.py:64] : Writing jade_output_missing/run_batch_3.sh
2021-06-19 07:28:55,139 - INFO [jade.utils.utils utils.py:64] : Writing jade_output_missing/medium_batch_3.sh

...

2021-06-19 09:59:08,595 - INFO [jade.hpc.hpc_manager hpc_manager.py:212] : job 'large_batch_81' with ID=7023774 submitted successfully
2021-06-19 09:59:08,595 - INFO [jade.hpc.hpc_submitter hpc_submitter.py:458] : Assigned job_ID=7023774 name=large_batch_81
2021-06-19 09:59:08,597 - INFO [jade.hpc.hpc_submitter hpc_submitter.py:78] : Created split config file jade_output_missing/config_batch_82.json with 14 jobs
2021-06-19 09:59:08,598 - INFO [jade.utils.utils utils.py:64] : Writing jade_output_missing/run_batch_82.sh
2021-06-19 09:59:08,600 - INFO [jade.utils.utils utils.py:64] : Writing jade_output_missing/bigmem_batch_82.sh
2021-06-19 09:59:08,600 - INFO [jade.hpc.hpc_manager hpc_manager.py:203] : Created submission script jade_output_missing/bigmem_batch_82.sh
2021-06-19 09:59:08,611 - ERROR [jade.hpc.hpc_manager hpc_manager.py:216] : Failed to submit job 'bigmem_batch_82': result=Status.ERROR: sbatch: error: Batch job submission failed: Invalid qos specification

2021-06-19 09:59:08,615 - INFO [jade.jobs.cluster cluster.py:488] : Wrote config version 302 reason=demote_from_submitter hostname=r7i3n16
Traceback (most recent call last):
  File "/home/telgindy/miniconda3/bin/jade", line 10, in <module>
    sys.exit(cli())
  File "/home/telgindy/miniconda3/lib/python3.7/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/home/telgindy/miniconda3/lib/python3.7/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/home/telgindy/miniconda3/lib/python3.7/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/telgindy/miniconda3/lib/python3.7/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/telgindy/miniconda3/lib/python3.7/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/home/telgindy/miniconda3/lib/python3.7/site-packages/jade/cli/try_submit_jobs.py", line 55, in try_submit_jobs
    status = mgr.submit_jobs(cluster)
  File "/home/telgindy/miniconda3/lib/python3.7/site-packages/jade/jobs/job_submitter.py", line 155, in submit_jobs
    is_complete = self._submit_to_hpc(cluster)
  File "/home/telgindy/miniconda3/lib/python3.7/site-packages/jade/jobs/job_submitter.py", line 385, in _submit_to_hpc
    if hpc_submitter.run():
  File "/home/telgindy/miniconda3/lib/python3.7/site-packages/jade/utils/timing_utils.py", line 26, in timed_
    return _timed(func, logger.debug, *args, **kwargs)
  File "/home/telgindy/miniconda3/lib/python3.7/site-packages/jade/utils/timing_utils.py", line 33, in _timed
    result = func(*args, **kwargs)
  File "/home/telgindy/miniconda3/lib/python3.7/site-packages/jade/hpc/hpc_submitter.py", line 125, in run
    self._submit_batches(queue, group, blocked_jobs, submitted_jobs)
  File "/home/telgindy/miniconda3/lib/python3.7/site-packages/jade/hpc/hpc_submitter.py", line 180, in _submit_batches
    self._submit_batch(queue, submission_group, batch)
  File "/home/telgindy/miniconda3/lib/python3.7/site-packages/jade/hpc/hpc_submitter.py", line 200, in _submit_batch
    queue.submit(async_submitter)
  File "/home/telgindy/miniconda3/lib/python3.7/site-packages/jade/jobs/job_queue.py", line 231, in submit
    self._run_job(job)
  File "/home/telgindy/miniconda3/lib/python3.7/site-packages/jade/jobs/job_queue.py", line 121, in _run_job
    job.run()
  File "/home/telgindy/miniconda3/lib/python3.7/site-packages/jade/hpc/hpc_submitter.py", line 447, in run
    raise ExecutionError("Failed to submit name={self._name}")
jade.exceptions.ExecutionError: Failed to submit name={self._name}
2021-06-19 09:59:08,711 - ERROR [jade.cli.run_jobs run_jobs.py:89] : Failed to run 'jade try-submit-jobs jade_output_missing' ret=1

Happy to provide more error outputs if it helps

This is a JADE bug. It was triggered by the fact that qos value was set to high for one submission group and the allocation had consumed all of its allotted hours. This caused the SLURM submission to fail. Then JADE raised a generic exception without updating the jobs that had been submitted. This caused future submitters to resubmit the same jobs over and over again.
This would have only happened in configurations with multiple submission groups where one invalid submission group follows  valid submission groups. It could not happen in configurations with one submission group (default).
Fixed in v0.4.3.

A variation of this could have occurred with only one submission group. If there were network problems in the HPC where one or more sbatch commands in a batch and then one failed, the successfully submitted jobs would have been resubmitted. Unlike this case, the jobs would likely only have been resubmitted one extra time assume the transient errors did not occur the next time. This is still obviously very problematic.
The users would hopefully have detected this when it happened. If it occurred when the user ran jade submit-jobs then it would have dumped a big stacktrace to the console. If it occurred in a deferred submission that part wouldn't have been as obvious. However, jade show-results and jade show-status would have displayed errors.
I have a script that can detect whether this error occurred on a past job submission and can make it available.
Version v0.4.4 adds handling of transient errors.


Run this script to discord bot?

Please include the script to run on discord

I won't be implementing such a function. However, you/someone else can feel free to do so. There are forks of this project that add Discord bot functionality.


Model Parameters Size?

Hi,
Congratulations on your great work!
May I know they model size of SSAN? I feel that substantial amount of additional parameters are added to the backbone (BERT/RoBerta) due to the Transformation Module. Is this true?
Thank you!

The additional paramters of SSAN mainly come from transformation matrix A, and its bias b (see eq. 6).
For Biaffine Transformation, A is of dim_per_head * dim_per_head, and the new paramters in total are caculated as:
N = (dim_per_head * dim_per_head + 1) * n_head * n_layer * n_structure
in the original paper, n_structure=5, so for BERT / RoBERTa Base, N=(64 * 64 + 1) * 12 * 12 * 5=2.9M, comparing to BERT's original parameter of 110M, so SSAN adds approximately 2.6% new parameters.
For Decomposed Linear Transformation, similarly we get N=(2 * dim_per_head + 1) * n_head * n_layer * n_structure=0.09M, which is much smaller, so SSAN_Decomposed adds approximately 0.08% new paramters.
Actually, we can still share the transformation module across different heads, or even different layers, reduce X12 its parameters, but I can only guss this will not significant affect its performance.
Hope this helps, if the above calculation went wrong or you have further regarding questions, let me know.


add GitHub workflow example in readme

Thanks for the suggestion. However, I want to limit the scope of this repository to getting core Python working on Windows 7. In a GitHub Actions workflow, the way to install Python from an installer is no different whether the installer comes from this repository or whether it comes from the official Python website.

That's not really true. You can install official Python versions with actions/setup-python without having to setup path variables and stuff like that.


[Sonic] Update HLD for ACL tagging and metering

Clarify metering precedence
Change ACL tag bitmap to list

Use a list instead of a bitmap for ACL tagging
Metering - resolve / clarify priority across policy routing and mapping


Fixes to sigproc.Window

Note - this is based off #62 and requires #62 to be valid. Of the 4 commits (so far), only the 2nd and 3rd are in question, as the first is from the other PR and the 4th is a cherry-pick from another PR that was already merged into main, but not dev (and I need it in dev).
In this PR, I...

The expansion to the tests look at the time (or newaxis) .offset values, and the data assuming Counter is correct.

Refactored sigproc.Window to satisfy the tests.

I also noticed that the initialization of the buffer creates a window-length buffer that's all zeros. Then, when new data comes in, the first window out comes only from the initialized zeros! I highly doubt that we want a completely fabricated window as the first window through the pipeline.
I added a new zero_pad_until setting.

"full" (default), maintains the current behaviour, though maybe that shouldn't be the default.
"shift" fills the buffer with zeros except for the space required for a single shift, meaning that the first window out will have exactly a single window-shift's worth of real data.
"input" fills the buffer with zeros but leaves room for the input. In this mode, the first yielded window will have as much of the input data as possible. IMO this should be the default because it provides minimal latency.
"none" does not use zero-padding in the buffer. There will not be any windows yielded until we have received enough messages to fill at least 1 windows.

Agreed the zero padding is suboptimal...  I really need one-to-one behavior in some of my pipelines (one input results in one output) in order to track completion of processing, so this was the necessary evil.  Nans would have been a better choice for padding here, but would likely break the existing filter implementation.
I'm happy to accept this so long as it maintains current behavior as the default.  We can deprecate this as a default with a warning.

I've completely rewritten this, using the generator pattern and adding way more unit tests.
I'll make this a draft for now while I prepare another PR that my new version depends on, then I'll update this PR.

Note that a457108 is the same commit as in  #79 and it might make sense to look at that one first.


Update model_id for Cartesia plugin

This PR makes the following changes:

Changes the default model_id from upbeat-moon (deprecated) to sonic-english. This is a time-sensitive change since upbeat-moon will soon stop being supported by the Cartesia API.
Adds sonic-multilingual to the type for model_id
Changes the default voice embedding to a better default voice

Next steps: update the plugin to support new Cartesia API functionality (including continuations, speed & emotion control, timestamps, more)

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

Awesome, closing this one.


lib: os: spsc_pbuf: Add support for full capacity packets

Currently, a largest packet that can be stored in an empty packet buffer was approx. half of the capacity. That is because of a rule that producer modifies only the write index and consumer only the read index. There are cases when user expects that a buffer will be able to hold packets of size much closer to the buffer full capacity.
Adding such feature requires producer to modify the read index (but only when the buffer is empty). With certain limitations that still can perform reliably but because of limitations this mode of operation is optional, enabled by the configuration flag.
To support this option spsc_pbuf_free had to be changed to return an information if freed packet is the last one. Same with spsc_pbuf_read where additional parameter was added (set to null for backward compatibility).
Commit updates test and ipc_service to the modified API.

@emob-nordic @nordic-krch you folks should take ownership of this part in the CODEOWNERS file.

If you could leave only the part fixing #59443 i would be grateful.

Violating the assumption that reader is only modifying read index and writer the write index may end up with hard to spot race conditions.

Now, I'm not very into the technical details of this patch but this statement from @emob-nordic is very true, and especially so when you have caches in the picture.


Adding some testnet link for bridging on the website will be useful

Describe the feature request
A more user-friendly interface will be welcome and some testnet link for bridging will be useful

I agree

Hi @entrepreneurlibre, could you provide more details on how to improve the current user interface?

Since you are in testnet, it would be better to add a testnet menu which will redirect users to the link for the distribution of eth sopolia in testnet. This keeps users on the page and it makes the interface less difficult to understand. You will see a menu like this:
Bridge
Faucet
Transactions
Explore
Get testnet tokens (new)
Guide
This remains exhaustive but the idea is to have everything in one without going to do research elsewhere

Good


convert github pages to jekyll to support blogging

Our github pages should support blogging. use jekyll not static HTML

adding @davide and @nllz
the website will be a lot easier to edit if we make full use of the Jekyll support in GitHub Pages and make a proper distinction between the content (in Markdown) and the layout/styling. That will also allow us to do more with blog posts, etc.

Here's an example of a website that uses Jekyll with GitHub Pages:
http://bead.glass/
is backed by:
https://github.com/glass-bead-labs/bead.glass
What you can see is that it makes it easier to separate content from layout, which makes development easier.
Here's a markdown file which is the content for a single blog post, for example:
https://github.com/glass-bead-labs/bead.glass/blob/gh-pages/_posts/2015-12-22-top-100.md


The Question About the Usage of Source Domain Data

According to my understanding, in the Statistics Alignment step, this method still utilizes the source domain data and its labels.
So, it's not entirely source-free, is it?

Thanks for this concern.
In the inference phase, we introduce the source statistics by using the running_mean and running_var stored within the BN layers.
Therefore,  there is no need to utilize source domain data or its labels during inference.
The related code can be found in utils/convert.py.


Looking for information on keys that drive TLS/SSL renegotiation behavior in Schannel

In troubleshooting some schannel issues with channel renegotiation, I've come across a few registry keys:
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurityProviders\SCHANNEL]
"AllowInsecureRenegoClients"=dword
"AllowInsecureRenegoServers"=dword
"DisableRenegoOnServer"=dword
The first two only seem to be documented in MS10-049, and only there, but I can't find any information on DisableRenegoOnServer. Searches for this information point to the MS10-049 advisory containing this registry value as well as "DisableRenegoOnServer" in 2010.
Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: dd180142-4c19-8abc-ecce-e4c7e5ac8951
Version Independent ID: fc5bba87-afad-1729-8f7e-333c73188b73
Content: Transport Layer Security (TLS) registry settings
Content Source: WindowsServerDocs/security/tls/tls-registry-settings.md
Product: windows-server
Technology: security
GitHub Login: @PatAltimore
Microsoft Alias: patricka

Hey mscottmueller,
Thanks again for contacting Microsoft. We value your feedback.
Conversing with the TLS team on this, I was given the following response:

"There are several registry values that can be used to change schannel behavior and a lot of settings are implemented internally. Authors/Contributors are under no obligation to document every single setting. Configuring them without deep understanding will generate more support cases. We actively discourage customers from using some of schannel settings for this reason."

I did go into our tech community and did find some links that may potentially assist you:

https://social.msdn.microsoft.com/Forums/en-US/8f5907de-0458-4740-8d8a-fd74042aeb8e/how-do-you-enable-quotsecure-renegotiationquot-in-iis-on-windows-2012-r2?forum=iissecurity
https://social.msdn.microsoft.com/Forums/en-US/d80517da-ab45-40d3-b9b6-6b275dd01b7a/disable-renegotiation?forum=iissecurity
https://social.msdn.microsoft.com/Forums/en-US/3f69a42b-b62d-4a4a-81aa-f93d6d4883de/client-certificate-selection?forum=iissecurity

Here are our additional support forums:

TechNet: https://social.technet.microsoft.com/Forums/en-US/home
MSDN: https://social.msdn.microsoft.com/Forums/en-US/home
Microsoft Community: https://answers.microsoft.com/

Hopefully one of our community experts can assist you better. We will now be closing this thread.
Thank you and have a most pleasant day.
#please-close


WDDM graphics driver causing RDP mouse jitter

Any plans to address the WDDM graphics driver causing RDP mouse jitter?  See https://answers.microsoft.com/en-us/windows/forum/all/windows-10-1903-remote-desktop-cursor-stutters/dc1f77db-0f35-4954-8084-937edc192558 for details.

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

ID: 2e05c0fc-2bb3-964a-01e8-0e9b2f7557de
Version Independent ID: 65380793-9c19-edbb-3879-f3dcbb8e15d4
Content: Migrating to the Windows Display Driver Model (WDDM) - Windows drivers
Content Source: windows-driver-docs-pr/display/migrating-to-the-windows-vista-and-later-display-driver-model.md
Product: windows-hardware
Technology: windows-devices
GitHub Login: @lorihollasch
Microsoft Alias: loriwhip

@jantonacci , thanks for your feedback - I've passed it along to the development team. The best way to report issues is through the Feedback Hub, which I encourage you to do. Closing this issue since it isn't doc-related, thanks.

Just heard back from the dev team, @jantonacci. Turns out that they were aware and issued a servicing fix in Win 10 v2004. (They are not going to fix in 1903.) I also just realized that your issue was filed in August, so perhaps you're already aware of this. Apologies for my slow response!

Hey great, ty. I am on Win10 build 1909 now.  I will roll back the workarounds and report back here.

RDP is DOA, will have to travel to the remote site and revert RDP session changes via gpedit.msc as remote shutdown (restart) failed.  Sadness abounds.

Good luck, @jantonacci - hope you get resolution on your issues soon.


Thanks

I implement this timeline in angular4.
Thank you very much for your work (jQuery to Angular).


Python SDK

Is the opening "Before you start" section intentionally not displaying the Python option?
https://github.com/Microsoft/ApplicationInsights-Python

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

ID: 401d2997-0fbd-7966-8996-edbaab1819ff
Version Independent ID: c3ee3318-4c69-8ded-a8d5-5059d699351b
Content: Application Insights API for custom events and metrics
Content Source: articles/application-insights/app-insights-api-custom-events-metrics.md
Service: application-insights
GitHub Login: @mrbullwinkle
Microsoft Alias: mbullwin

@tiny-dancer Thank you for bringing this to our attention.  I'll assign this to the document author so they can add this update request to their queue.

@tiny-dancer Even though the Python SDK is originally Microsoft authored and we still have engineers making contributions to it we currently consider it community supported so it doesn't get the same level of coverage in the official docs as the SDKs that are officially supported. The list of officially supported SDKs are: Java, Node.JS, JavaScript, .NET, and .NET Core.
We have made some recent investments in Python and Go in the area of distributed tracing that we announced last month as part of our participation in the OpenCensus project. These new capabilities do not require the SDK and the documentation for Python can be found here.

thanks for the info! it would be help to call the community vs officially supported options, similar to the hashi vault docs.  we had written off using Azure Monitor app insights in favor of another vendor as it wasn't listed as supported in the docs.

We do that in this doc here. But I agree the discoverability is not great and the doc itself could use some improvement. I will update the doc and see if we can find a more prominent location for it to live in the table of contents/make sure it is linked to from enough other docs to make it clear to the community what is supported and what is community supported. Thanks again for the question, and the feedback!

We have moved the supported platform doc to the Reference section to increase discoverability and renamed it's TOC entry to make discovery easier. This change is merged and will go-live between 10 AM - 11 AM UTC -8.

@MicrosoftDocs/azure-cxp-triage #please-close


investigate pinned dependencies

Is your enhancement request related to a problem? Please describe
the conda install for rubicon-ml is super slow and takes a few solves to install into a fresh environment. this is almost certainly due to issues with our pinned dependencies
Describe the solution you'd like

investigate why our pinned dependencies are pinned (pyarrow, pyyaml, fsspec)
investigate the dependencies called out by the conda forge bot in the dependency analysis here (UI libraries, pyarrow, s3fs)
update and unpin any upper limits we can

at a first glance before digging into it, here are a few things I think we'll have to do

add the relevant UI libs to the conda recipe (since conda doesn't do extras)
unpin pyyaml and fsspec - I don't think theres any legit reason they're pinned
determine if we even need pyarrow and s3fs - they're optional dependencies of our dependencies


Latest Atom 1.60 on Linux suddenly freezes GNOME when requiring file open popup

Not sure if it was due to recent 5.17 kernel update or some other recent update on Fedora 35. But as of a few days ago I could get a GNOME file open popup from Atom. Now if you do anything in Atom that requires a file open popup it dims like it is going to display it but then nothing comes up and the entire GNOME desktop is frozen. Sad.

I have other strange things with KDE. When I launch Atom, the window of keepaxc, which is hidden, appears. I dont think that the problem is linked with the kernel, but more with the window manager, and more globally, with the desktop management.

On Fedora 35 GNOME now when you do something within Atom that triggers a file open popup, the Atom window dims slightly (which is normal and expected) because it's going to be in the background and getting ready to show the GNOME file open popup in the foreground, but instead of showing the popup GNOME freezes with Atom dimmed.

I have other strange things with KDE. When I launch Atom, the window of keepaxc, which is hidden, appears. I dont think that the problem is linked with the kernel, but more with the window manager, and more globally, with the desktop management.

Did this just start happening to you recently? I haven't been coding for a couple weeks but a couple weeks my Atom 1.60 was working perfectly fine on Fedora 35. Some Fedora update since then triggered this sudden problem. Might rollback my dnf history to see where, but either way still not good because then I cannot update Fedora anymore for fear of breaking Atom again, not a long-term solution.

No, I installed Atom a week ago.
Seems that atom uses dbus. I would look into that direction.
Le 03/05/2022 à 23:14, Leandro Hermida a écrit :

I have other strange things with KDE. When I launch Atom, the
window of keepaxc, which is hidden, appears. I dont think that the
problem is linked with the kernel, but more with the window
manager, and more globally, with the desktop management.

Did this just start happening to you recently? I haven't been coding
for a couple weeks but a couple weeks my Atom 1.60 was working
perfectly fine on Fedora 35. Some Fedora update since then triggered
this sudden problem. Might rollback my dnf history to see where, but
either way still not good because then I cannot update Fedora anymore
for fear of breaking Atom again, not a long-term solution.
—
Reply to this email directly, view it on GitHub
https://github.com/atom/atom/issues/25437#issuecomment-1116664586,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKKQX6QXUAEEY6ULD6BGTLTVIGJMPANCNFSM5U5FCULQ.
You are receiving this because you commented.Message ID:
@.***>

Another update to Fedora 35 packages now fixed the problem, so must've been a temporary issue or regression caused by a GNOME or Fedora package Atom uses.


309 get latest ni stops data

Closes #309 .
This has had to be reworked just to get the data from the URL. I have taken this approach so that the data does not need to be stored in Sync. The read_ni_stops function has been updated now so that it reads the data in locally and, if it doesn't exist, it saves the data locally and reads it in.  Any comments are welcome!

I've addressed @Antonio-John comments so I will merge :)


Added two fancy badges from shields.io

Coverage remained the same at 65.093% when pulling 4cad28a8963a4ee6ac7d90faefd4b8cca1a18086 on iBug:patch-1 into d383bfc8f14c1e7f4717fc808c8983404ca6c91e on Charcoal-SE:master.

!!/approve


confusion about the final chamfer distance for LDIF result

Hi, chengzhag.
Thanks for you excellent work.
I tried to reproduce the mesh generation part of your work, exactly the LDIF network, and I train this part followed the parameters mentioned in the paper, the best result I got from my reproduction was wicp_avg_chamfer=7.25, which remain a certain gap with the results shown in the paper(6.72). I am not sure if i missed some thing.
Another question. I used the checkpoint file provided in the readme file to get 6.72.  However, the final statistical results of various categories are not quite consistent with those shown in the paper, so I would like to ask if there is any difference between the statistical results in the paper and the statistical methods in the code?

Hi, @Harvey-Mei,
Thanks for your interest in our work!
I think that the training process might introduce some randomness to the results. Maybe try again to see if there is any change to the results? For your reference, here is the wandb report of experiment<PHONE_NUMBER>0518, including the LR/training/testing curves. The report also includes another experiment<PHONE_NUMBER>3369 (grey), which is almost identical with<PHONE_NUMBER>0518 (orange) in terms of settings. However, the results differ a lot since the learning rate in grey drops early than orange.

The report also includes an experiment<PHONE_NUMBER>0721 which tests the weight trained on watertight meshes in<PHONE_NUMBER>0518 on non-watertight meshes. It is where we got the results in the paper.
The reason for your second question might be that the ICP algorithm provided by gaps can introduce some randomness in the process of optimizing to align the meshes. For your reference, chamfer_woICP of each category is:
{'bed': 4.3483425925046015, 'wardrobe': 5.368200843907593, 'bookcase': 4.65738395402351, 'chair': 6.334140533872199, 'sofa': 5.99414974168976, 'table': 15.723936902234081, 'desk': 10.808811716871475, 'misc': 29.429790655298163, 'tool': 4.530272881545347}.
Hope this can help solve your problem.

Hi, @chengzhag ,
Very grateful for your quick reply!
I'll study the information you gave me. Good luck with your research.

PS: The watertight process we use introduces thicker object meshes thus can lead to drop on chamfer distance when evaluating on non-watertight meshes.Although this is what we report in the paper, I personally think it would be fair to use our test results on watertight meshes for comparison.


Create OpenD executable

This is a very brief draft of what I expect it to be, more stuff to be added later on

Added running single .d file, next stop is getting dependencies in

Added add-local-pacakge command, usage as follows:
opend please add-local-package /path/to/package

Writes stuff to .opend/settings.json
Next on my list is adding git dependencies and dependencies from some kind of server

Even if this isn't quite done, as long as the basics work i wanna merge to have something in the release.

Even if this isn't quite done, as long as the basics work i wanna merge to have something in the release.

Currently, the Linux support is missing entirely. Give me a deadline so I can adhoc some linux support before you package this ～


feat(volume): Add tooltip message on failure of volume expansion

image: wangsiye/longhorn-ui:0e1ba41
Signed-off-by: Siye Wang<EMAIL_ADDRESS>

@smallteeths Please help backport to 1.3.x and 1.2.x. Thanks.


FacebookClientWrapper should not silently fail on SendMessageAsync

#Describe the bug
If the result of the response is NOT IsSuccessStatusCode, the sdk should presumably throw an exception and not just return an empty string.  The current code makes debugging difficult, and seems to ignore errors.
                using (var client = new HttpClient())
                {
                    var res = await client.SendAsync(request, cancellationToken).ConfigureAwait(false);

                    if (res.IsSuccessStatusCode)
                    {
                        var responseBody = await res.Content.ReadAsStringAsync().ConfigureAwait(false);
                        var stringResponse = JsonConvert.DeserializeObject<FacebookResponseOk>(responseBody);
                        return stringResponse.MessageId;
                    }

                    return string.Empty;
                }

Expected behavior
An exception indicating the send operation failed.

@garypretty , please take a look at this and let us know if and how we should take this.

@mrivera-ms yes, I think we should take this.  We should throw the error instead of returning an empty string (providing we check that no other code is relying on that return of an empty).

@BruceHaley @EricDahlvang Did this get fixed in this PR?

@mdrichardson it looks like it has been addressed.


Fix some abnormally high-capacity boxes

About the PR

Fixed some abnormally high-capacity boxes to be more inline with existing expectations around box capacity.

Dart boxes now have a normal storage capacity and 1 less dart of each colour.
Candle boxes are now whitelisted to candles only (akin to replacement light boxes), and have a smaller capacity (6x4, the same as light boxes) with slightly less coloured candles.
Replacement light boxes have had duplicated yaml removed through parenting.
Deathrattle implant box, a nukeops only item, has been moved to the syndicate.yml box fills and given a new sprite. It retains its abnormally high capacity.

Fixes #28271
Media

[X] I have added screenshots/videos to this PR showcasing its changes ingame, or this PR does not require an ingame showcase

Breaking changes

Changelog

:cl:

tweak: Candle boxes can now only hold candles.

good pr
i was about to fix it in #25458 , but got some tests failing

good pr i was about to fix some of it in #25458 , but got some tests failing you can check which was done in my pr to make sure not to dupe work

From what you've done there, this PR covers:

Replacement light box parenting
Changes to candle boxes (I've also changed their capacity and added a whitelist)
Changes to dart boxes (I've also changed their capacity in this)
I'd just resolve those conflicts when your PR gets unfrozen (not sure why it got caught by the feature freeze)


Not working on React 17

Description
When I try to render any React Pixi component using React 17, I get the following error:
react-pixi.es-dev.js?e177:2960 Uncaught TypeError: Cannot read property 'alternate' of undefined

If I use React 16 then I don't get this error, that's why I know it's related to the new React's version.
Steps to reproduce

Install and use React 17
Render any React Pixi Component

Additional info

@inlet/react-pixi version:  5.2.0
React version: 17
ReactDOM version: 17
PIXI version: 5.3.3

Thanks for letting me know, we need to update the lib to make it compatible with the newest React version.
I'll look into this later today.

That was fast! Thank you so much for maintaining this library, I love it.


adds seal/unseal to Aead, Daead, Signer

fixes #45

Codecov Report
Patch coverage: 4.83% and project coverage change: -0.79 :warning:

Comparison is base (c569ff6) 59.34% compared to head (846389c) 58.56%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #47      +/-   ##
==========================================
- Coverage   59.34%   58.56%   -0.79%
==========================================
  Files          88       88
  Lines        9188     9302     +114
==========================================
- Hits         5453     5448       -5
- Misses       3735     3854     +119

Impacted Files
Coverage Δ

navajo/src/aead.rs
35.46% <0.00%> (-4.80%)
:arrow_down:

navajo/src/aead/key_info.rs
45.83% <0.00%> (-6.55%)
:arrow_down:

navajo/src/daead.rs
61.05% <0.00%> (-14.10%)
:arrow_down:

navajo/src/dsa/key_info.rs
91.66% <0.00%> (ø)

navajo/src/dsa/signer.rs
44.53% <0.00%> (-17.43%)
:arrow_down:

navajo/src/dsa/signing_key.rs
76.33% <0.00%> (ø)

navajo/src/primitive.rs
62.98% <0.00%> (ø)

navajo/src/envelope.rs
75.16% <100.00%> (ø)

navajo/src/hkdf/salt.rs
44.31% <100.00%> (ø)

navajo/src/mac.rs
55.55% <100.00%> (ø)

... and 2 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Add background fetch to the library

Once we have a PWA (#876), we should look into the use of background sync and/or background fetch to fetch segments for offline storage.  This also depends on Fetch support (#829).
With this, one could begin storing content for offline consumption, then close the app and let the segments be fetched and stored in the background, as connectivity is available.

Updated to include both background sync and background fetch as tools we may want to use for this, and closing #881 as a duplicate.

Issues implementing background fetch & sync so far:

BG fetch is behind a flag in Chrome 61, experimental web platform features must be enabled explicitly.  Expected at this stage, but worth noting.
navigator.serviceWorker provides no consistent indication of service worker existence.  Sometimes, controller is null even when a SW is registered.  Sometimes, controller becomes non-null after reloading the page.  This means that we will need an app-level configuration to instruct us to try BG fetch in the first place, since we can't detect the SW.
navigator.serviceWorker.ready never resolves on localhost over http.  It does on appspot over https.  This means we can't reliably grab a reference to the SW registration, even asynchronously.  Saving the reference in the app level after initial registration allows me to work around this for development purposes, but this is going to complicate library APIs for BG fetch.  If this is consistently the case, we will have to have applications pass in a reference to the SW registration before we can use BG fetch.
At least on desktop Chrome 61 on Linux, the BG fetch API does not result in a network request.  Nothing shows up in the Network debug panel in Chrome.
At least on desktop Chrome 61 on Linux, the BG fetch API does not provide any way to access the fetch.  (May be related to the point immediately above.)  The BackgroundFetchRegistration object contains icons, tag, title, and totalDownloadSize.  The spec'd activeFetches does not appear.  There is no clear way to access the results of the fetch.

Given all of the above, I am moving this issue to the backlog for now.

According to Chrome team, background fetch is not ready for production yet.  Leaving this issue on the backlog until that changes.

It would have been grate if the Native File System could be used somehow.

@theodab I have seen that with the latest changes all the initialization segments will be downloaded, even of qualities that are not going to be downloaded, is it intentionally?

@avelad What assets are you seeing that happen on?
I tried downloading Angel One (multicodec, multilingual, Widevine) on both nightly and v3.2.0, and they seem to be downloading the same set of segments.
137 network requests, 35 items stored in the segment DB, manifest size reported as 8224778 in the DB... it all matches up.

@theodab I have recorded a video, but it is too big to attach here, I have mailed it to you.

We load the init segments so that we can create the segment index for those variants; that asset uses SegmentBase, so we need to see the sidx box from the init segment. It's part of the initial process of loading the manifest, so it happens before we choose which video stream we want to store.
It's not a new behavior. For example, I loaded that same asset you showed in v3.1.3 and the same number of network requests are made in that version.
We have been working on a variety of performance enhancements recently (see, for example, #1936). I believe one of the planned enhancements is to lazy-load the segment index, which should fix this problem.

This may be blocked on changes in Chrome for now: https://bugs.chromium.org/p/chromium/issues/detail?id=1256838

@joeyparrish  I have seen that of the two issues that block the implementation, one is closed and the other has a commit, but it is not closed. Do you know if this is already working in the latest versions of Chrome?

We are waiting for the changes to become on-by-default and in the stable branch of Chrome.  AFAIK that has not happened yet.


DOM checker

This is a (multiple allowed):

[ ] bug
[x] enhancement
[x] feature-discussion (RFC)

Even if Framework7 is well-documented, there are several ways to make mistakes in the HTML code (e.g. missing id attributes for tabs). What do you think about a DOM checker, to be enabled in the Framework7 init, which checks all pages according required structure and logs errors to the console.

It could be good to throw warnings in the console for these things

A html code checker would be very much work

Issue is closed because of outdated/irrelevant/not actual
If this issue is still actual and reproducible for latest version of Framework7, please create new issue and fill the issue template correctly:

Clearly describe the issue including steps to reproduce when it is a bug.
Make sure you fill in the earliest version that you know has the issue.
Provide live link or JSFiddle/Codepen or website with issue


Setting eshop on AKS with Internet access?

Other than creating an Ingress resource (which is not part of the repo), are there simple steps to expose the blazorclient to the internet (just like in eshopOnContainers)? I see that all services are nodeports and need some plumbing to expose to the internet. Same goes to web status and auth.

The Kubernetes instructions (https://github.com/dotnet-architecture/eShopOnDapr/blob/main/docs/run-eshop.md) now include an NGINX ingress controller. Instructions do not include setting up DNS though, that's still something you'd have to do yourself and dependent on type of K8s cluster.


(fix): get_variation input validation fixes.

Summary

Fixed issue for experimentKey and user_id validation for get_variation.

Coverage increased (+29.7%) to 98.112% when pulling 4593161f29de882d8d669d8c745118a3b55edbd8 on yasir/get-variation-fix into 138fff50735c390779654e45cb72d438b7e4fb08 on master.


Aggressive cows

🚀 Feature
Farmer John has built a new long barn, with N (2 <= N <= 100,000) stalls. The stalls are located along a straight line at positions x1,...,xN (0 <= xi <= 1,000,000,000).
His C (2 <= C <= N) cows don't like this barn layout and become aggressive towards each other once put into a stall. To prevent the cows from hurting each other, FJ wants to assign the cows to the stalls, such that the minimum distance between any two of them is as large as possible. What is the largest minimum distance?
Example :
1)Input :
5 3
1 2 4 8 9
Output : 3
2) Input :
6 4
1 3 5 7 8 10
Output : 2
Have you read the Contributing Guidelines on Pull Requests?
Yes
Motivation
Enhances problem solving ability and practical application of concepts.
Pitch
It is a competitive programming question with applied knowledge of Binary search.

I want to work on this issue in C++ as a participant of GSSOC'21

/assign


[DO NOT MERGE] Investigating actor id stress tests possibly regressions

Reverts dapr/dapr#5729

/ok-to-perf


Adds methods to remove a user from a group

Hello, is there any chance this will released soon ?

bump :)

Thank you for your PR and sorry it took so long to get back to it. We have recently released a 1.x version of this SDK which completely updates the structure and build process for our SDK.
I believe our changes no longer require this PR to be included so we are going to close it. If you feel the new version does not resolve the issues you were seeing, prompting this PR, please let us know and we will be happy to re-investigate.