Update deps

Not updating any K8s/OpenShift API as that will need to wait for an Operator-SDK release, but otherwise updating:

aws-sdk-go-v2
ginkgo/gomega
prometheus/client_golang
zap

/lgtm

Codecov Report

Merging #99 (0ff7d40) into main (3d43a0a) will decrease coverage by 1.30%.
The diff coverage is n/a.

Additional details and impacted files

@@            Coverage Diff             @@
##             main      #99      +/-   ##
==========================================
- Coverage   58.33%   57.04%   -1.30%
==========================================
  Files          26       26
  Lines        1265     1299      +34
==========================================
+ Hits          738      741       +3
- Misses        442      470      +28
- Partials       85       88       +3

Impacted Files
Coverage Δ

pkg/aws_client/security_group.go
71.79% <0.00%> (-9.75%)
:arrow_down:

main.go
5.81% <0.00%> (-1.88%)
:arrow_down:


Docker Images are not getting build

Hi,
besides that the release label "python3" is not nice, the docker images are not getting build. Maybe because of  errors in travis https://travis-ci.org/DefectDojo/django-DefectDojo/builds/576885586 .
Cheers,
Timo

update: apt-get update causes the problem,see https://travis-ci.org/DefectDojo/django-DefectDojo/jobs/576880722

I do not replicate
if you're still seeing it, does this fix it?
apt -o Acquire::https::No-Cache=True -o Acquire::http::No-Cache=True update
ref: https://github.com/nodesource/distributions/issues/500, https://askubuntu.com/questions/751801/apt-update-fails-writing-more-data-than-expected

works for locally, also. But on travis it might still be an issue.


Feature: prime k-tuplets interface

Good day , Kim.
I think it would be nice feature if you implement something like this
primesieve_generate_twins(start, stop)
primesieve_generate_triplets(start, stop)
...
primesieve_generate_sextuplets(start, stop)
( or may be k-tuplet iterator ? )
where each function returns array of (first element of the k-tuplet and pattern if needed).
IMO primesieve_print_*()  are not very useful for prime tuplet processing / analyzing.
Best Regards
Julian.

Hi Julian,
I agree that the primesieve_print_*() functions are useless. However I won't remove them because that would break backwards compatibility. Since the beginning, my goal for primesieve and primecount was to write libraries that are extremely specialized i.e. primesieve should generate primes as quickly as possible and primecount should count primes as quickly as possible. So unlike many other libraries my goal was never to create a library for doing number theory with lots of number theoretic functions.
After more than a decade of hard work, I am both happy and relieved that I have finally achieved my goals. This means that for me personally, both primesieve and primecount are now feature complete. My new goals for the future are:  to maintain primesieve and primecount with hopefully as little effort as possible and to use my free time for my other hobbies.
I guess it is a good idea, for me to open a new issue  "No new feature requests" so that other users can read about the status of my libraries and what they can expect of my libraries.
Best regards,
Kim

Hi Julian,
I agree that the primesieve_print_*() functions are useless. However I won't remove them because that would break backwards compatibility. Since the beginning, my goal for primesieve and primecount was to write libraries that are extremely specialized i.e. primesieve should generate primes as quickly as possible and primecount should count primes as quickly as possible. So unlike many other libraries my goal was never to create a library for doing number theory with lots of number theoretic functions.
After more than a decade of hard work, I am both happy and relieved that I have finally achieved my goals. This means that for me personally, both primesieve and primecount are now feature complete. My new goals for the future are:  to maintain primesieve and primecount with hopefully as little effort as possible and to use my free time for my other hobbies.
I guess it is a good idea, for me to open a new issue  "No new feature requests" so that other users can read about the status of my libraries and what they can expect of my libraries.
Best regards,
Kim

It's clear. Thank you.
I will do it myself  :-) .
Regards and productive New Year!
Julian.

It's clear. Thank you.
I will do it myself  :-) .
Regards and productive New Year!
Julian.


Updated presence_ref.md formatting

Updated markdown to correctly show tables and json examples

 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.:x: trir262 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

OPS Build status updates of commit 0d3dc6e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Skype/UCWA/presence_ref.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 36494d7:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Skype/UCWA/presence_ref.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 8eb49b5:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Skype/UCWA/presence_ref.md
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


Use NCRegressionTests package

This PR removes the NCRegressionTests and uses the NCRegressionTests package. Cleaning things up from #312.

bors r+


Hotkey to yank command / snippet to clipboard

i have an alias for navi --print | xclip -sel clip but just wanted to suggest adding a hotkey like ctrl-y for this

This is pretty easy to do it. Hopefully by the end of this week I'll release a new version with it :)

The hardest thing is to generalize clipboard actions (xclip vs pbcopy vs ...)

Would be very nice is if configurable, I personally use gpaste to manage the clipboard that has a very nice cli.

Could anyone give a feedback to https://github.com/denisidoro/navi/pull/155?


How to send decimal target temperatures?

The target temperature is a string, yet any decimal value specified gets truncated to the nearest integer.  Is this the expected behaviour of the Energenie TRV?  A whole degree is a lot of heat.

I did have it on my list to handle decimal places, or at least half degree values. But with use I found that the temperature reported was not stable when set - it can vary up to 1.5 degrees, so setting the target any more accurately was not of much use.
If you your trvs are more stable than mine, I am willing to accept patches, but I won't be able to test them until next October when my heating comes back on.


Add the score of manga when one tries to add an entry for the tracker

Describe your suggested feature

add here the average score of Anilist. i am proposing this because when I want to start a new hentai i would like to see the score of the said hentai (see the image) there( if it exist) so that we are not obliged to open in the browser (entries in anilist) and check the score, so of course this is a QoL suggestion.
i proposed only anilist because:

Mal doesn't accept entries of any hentai easly specially pornhwas (manhwa hentai), so their archive is poor on this category
i didn't try myself other webisites avaiable on tachi, so maybe, if they are fine too like anilist, add the score thing there too

Other details
No response
Acknowledgements

[X] I have searched the existing issues and this is a new ticket, NOT a duplicate or related to another open or closed issue.
[X] I have written a short but informative title.
[X] If this is an issue with an extension, I should be opening an issue in the extensions repository.
[X] I have updated the app to version 1.8.5.
[X] I will fill out all of the requested information in this form.

I personally am not interested in this, you could open a issue in the main Tachi repo and SY would would get it if main Tachi does.


Update README with information on apiserver

Added @munnerz 's architecture documentation in #273.
See https://navigator-dbaas.readthedocs.io/


Circle CI update with readme fix.

@mb64
#226 did not publish the docker image as hoped. The error messages and warnings produced are below. This pull requests reverts the README to reference my docker image until the automated build is fixed. It should also fix the security warning. However, the warning appears to be just a warning and the real error is the username or password is incorrect. I do not expect this to fix the publishing issue.
I recommend pushing so that the README will point to the newer docker image until we can workout the authentication issues with publishing. I don't have access to the Circle CI control panel so someone else will need to fix that part or grant me access.

#!/bin/sh -eo pipefail
docker login -u $DOCKERHUB_LOGIN -p $DOCKERHUB_PASSWORD
docker push IMAGE_NAME
WARNING! Using --password via the CLI is insecure. Use --password-stdin.
Error response from daemon: Get https://registry-1.docker.io/v2/: unauthorized: incorrect username or password
Exited with code 1

I'll merge for now, and cc @tomaka to fix updating the Docker image.


How does BM3D denoise color pictures?

http://www.ipol.im/pub/art/2012/l-bm3d/
Adapting the algorithm to color images is easy and can be done in the following steps:

First a transformation to a luminance-chrominance space from the RGB noisy image is applied. Y denotes the luminance channel and by U and V the chrominance channels;

For each step:

Grouping is only performed with the Y channel;
The 3D block built on Y is used for all three channels;
Collaborative filtering is applied to each channel separately as well as the weighted aggregation.

Return to the RGB space by applying the inverse transformation.


copernicus parser first draft

Codecov Report
Patch coverage: 90.20% and project coverage change: +0.11% :tada:

Comparison is base (2da7ab6) 88.31% compared to head (0622263) 88.43%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #62      +/-   ##
==========================================
+ Coverage   88.31%   88.43%   +0.11%
==========================================
  Files          20       22       +2
  Lines        2183     2326     +143
==========================================
+ Hits         1928     2057     +129
- Misses        255      269      +14

Files Changed
Coverage Δ

adsingestp/parsers/copernicus.py
89.81% <89.81%> (ø)

tests/test_copernicus.py
91.42% <91.42%> (ø)

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


Typo: "evetything" on /docs/getting-started/adding-interactivity/

https://github.com/wbkd/react-flow-docs/blame/fe57d8b54a21d8b1da0f0ba3c03b380f792ce758/docs/getting-started/adding-interactivity.md#L41C187-L41C197

Thanks @artimath


[DealabsBridge] Add new bridge

This is a new Bridge for the Deal search function of dealabs.com
The html content is a little bit crappy, but it works !

Getting all the categories together was not the toughest in this Bridge, the HTML was a little bit harder  :sunglasses:
I followed your advices and updated the code.
There actually one line longer than 80 chars, but splitting this line would IMHO make it less readable.
I hope I did not forgot anything !

Thanks for updating.

There actually one line longer than 80 chars, but splitting this line would IMHO make it less readable.

That's fine. 80 characters are a rule of thumb. The checks will definitely fail if a line exceeds 120 characters.
I did an offline check on your last commit and there are still some errors:
FILE: /var/www/html/rss-bridge/bridges/DealabsBridge.php
----------------------------------------------------------------------
FOUND 6 ERRORS AFFECTING 6 LINES
----------------------------------------------------------------------
   6 | ERROR | [ ] String concat is not required here; use a single
     |       |     string instead
     |       |     (Generic.Strings.UnnecessaryStringConcat.Found)
   7 | ERROR | [ ] String concat is not required here; use a single
     |       |     string instead
     |       |     (Generic.Strings.UnnecessaryStringConcat.Found)
  89 | ERROR | [x] Whitespace found at end of line
     |       |     (Squiz.WhiteSpace.SuperfluousWhitespace.EndLine)
 157 | ERROR | [x] Expected 1 space after ">="; 0 found
     |       |     (Squiz.WhiteSpace.OperatorSpacing.NoSpaceAfter)
 160 | ERROR | [x] Expected 1 space after closing brace; newline
     |       |     found
     |       |     (Squiz.ControlStructures.ControlSignature.SpaceAfterCloseBrace)
 166 | ERROR | [x] Expected 1 space after closing brace; newline
     |       |     found
     |       |     (Squiz.ControlStructures.ControlSignature.SpaceAfterCloseBrace)
----------------------------------------------------------------------
PHPCBF CAN FIX THE 4 MARKED SNIFF VIOLATIONS AUTOMATICALLY
----------------------------------------------------------------------

Time: 944ms; Memory: 18Mb

Regarding lines 6 and 7 you can do this:
const DESCRIPTION = 'Return the Dealabs search result using keywords,
 with/without expired deals, with/without shop deals and by category';

Notice that there is a space at the beginning of the second line. The output is the same.

Travis is fixed in master. Unfortunately this PR cannot pass builds unless you rebase on master.

I'm pretty new to teamwork with git, therefore it took so long ...
TIL to rebase from a fork :satisfied:
Now it's all fixed, and checked !

Merged, thanks for your work !


BEN conformity

In the progress indicator module, I think this;

Should be

Because it’s the progress-indicator__link element that’s being modified not the progress-indicator block.

That is very true :) and on me!
I shall fix soon. Will be a breaking change though.

fixed via #234


Fix travis and build errors under python 3.

PR #71 introduced a bug, where the python version that was used by travis did not match the version intended.
Also fix the problems plaguing current master builds failing under python 3, with tests! :)
@amjith

Thank you for fixing Travis as well as the breaking tests.
Cheers! :gem:


tipPosition is not defined

row 155: ["set" + m.camel.pos.c1](balloon.inner[m.size.c] / tipPosition - len)
i think it should be:
["set" + m.camel.pos.c1](balloon.inner[m.size.c] / options.tipPosition - len)
tipPosition was never defined before, it come out in an error.
At least on Chrome/Linux

Thank you so much!


Links from /tiddlers should link to the short-url of the tiddler

Issue:
If you go to ./tiddlers?sort=-modified to find a tiddler you want to share and then click on that tiddler, currently it will point you to the private recipe version of that tiddler (assuming it's your space that you are in).
This is an issue because everyone else (who isn't a member), should get the public recipe version and not the private one.
Fix:
The link should be to the short-url version of that tiddler, i.e. ./

I'd prefer it if we avoided a javascript solution here. Not because people won't have it often, but because it would be nice if curl and browsers were having similar experiences.

Well, it sounds to me like the problem is "I want to share this url but the urls wrong"
Javascript sounds perfect here, as all that would happen is the url will change.
I'm not sure how curl is relevant here.
http://http://htmljs.tiddlyspace.com/htmljs-friendlyuris
updates the uri in a way that makes refresh, back and forward buttons work as expected. The only difference is the url is arguably always the one you want to share...
Note http://jon.tiddlyspace.com/recipes/jon_public/tiddlers/Openid Magic in TiddlySpace Documented gets its uri updated
but http://jon.tiddlyspace.com/recipes/jon_public/tiddlers doesn't
(the condition being it must contain /tiddlers/)

Looks like we should close this due to lack of concrete solution/interest...?


Update arcTo() documentation

Description of change
The documentation for arcTo() is wrong. Also refer this thread
Pre-Merge Checklist

[x] Documentation is changed or added

Codecov Report

Merging #6005 into dev will increase coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##              dev    #6005      +/-   ##
==========================================
+ Coverage   70.54%   70.55%   +<.01%
==========================================
  Files         208      208
  Lines       10530    10530
==========================================
+ Hits         7428     7429       +1
+ Misses       3102     3101       -1

Impacted Files
Coverage Δ

packages/graphics/src/Graphics.js
69.1% <ø> (ø)
:arrow_up:

packages/ticker/src/Ticker.js
87.5% <0%> (+0.78%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update b47c4bb...ce18c61. Read the comment docs.


Use the non-blocking IO enabled http.rb instead of net/http in watchers

When using kubeclient in an actor based concurrent environment, such as Celuloid, we need a non blocking HTTP library to handle watching Kubernetes events. http.rb can be used with Celuloid::IO sockets, so that Celluloid actors remain responsive when awaiting cluster events.
I've tested with basic and ssl authentication options, both with and without the usage of Celluloid::IO. I've not tested thoroughly using bearer token, I only verified that the headers are set when making a request.
This resolves issue #140

Not sure how to handle the Avoid parameter lists longer than 5 parameters. rubocop restriction. Please let me know if you can live with it or how would you rather expose the socket options to the user.

Thanks @msufa! Don't mind the travis error for now. I expect this to be a PR with a long life-cycle as I want to be sure that everything works as expected. I'll start to test it now but I want to run with it for a week or more to check it thoroughly.

@msufa I see that you've done some generic refactoring (thanks!) to facilitate the introduction of non-blocking IO but that is good regardless, for example creating read_stream, etc.
If you split that out into its own patch (you can use this PR anyway) it would facilitate my work of reviewing (keeping refactoring and features separated).
Thanks!

@simon3z, I only extracted that part because I got a warning from Code Climate that the host method is too complex. I can stuff that code back in if it makes the PR clearer.

@simon3z, I only extracted that part because I got a warning from Code Climate that the host method is too complex. I can stuff that code back in if it makes the PR clearer.

@msufa no, on the contrary I am all in favor of that but in the scope of this PR it makes it harder to review for relevant changes. Just split it to another patch and we're good.

This is working for my use-cases, @abonas can you review?

Didn't see that this comment was addressed: https://github.com/abonas/kubeclient/pull/142#issuecomment-161709995
Did I miss it?

Didn't see that this comment was addressed: #142 (comment)
Did I miss it?

@abonas, indeed this comment was addressed, please have a look here https://github.com/zendesk/kubeclient/commit/ac7ac64c53710e9367ee9e6f09305d5e62be2c5c
I'll wait until this PR is merged and revert that commit to bring back the refactoring if that's ok.

@abonas, indeed this comment was addressed, please have a look here zendesk@ac7ac64
I'll wait until this PR is merged and revert that commit to bring back the refactoring if that's ok.

@simon3z was the one doing the more thorough review of this PR given that he implemented the watches area, I'll let him decide on the approach here.

@msufa please rebase and squash move parsing of the HTTP response back into the #each method in update readme to include info about non-blocking socket support

@simon3z PR rebased, commits squashed.

@msufa I think that to pass rubocop you have to add in .rubocop.yml:
Metrics/ParameterLists:
  Max: 8

8 seems a good compromise to me. Feel free to suggest another value, cc @abonas
Otherwise @msufa you'll have to comply to current metric which is 5 and refactor initialize_client (it would be too much confusing in this PR though).

@msufa I think that to pass rubocop you have to add in .rubocop.yml:
Metrics/ParameterLists:
Max: 8
8 seems a good compromise to me. Feel free to suggest another value, cc @abonas
Otherwise @msufa you'll have to comply to current metric which is 5 and refactor initialize_client (it would be too much confusing in this PR though).

no objections to change rubocop.yml threshold

I've relaxed the rubocop parameter list restriction to 8.
I've also fixed the http.rb dependency to version 0.9.8 for now, as the Celluloid::IO support was temporarily removed from 1.0, see here for details.
/cc @simon3z @abonas

thanks @msufa , @simon3z please review/merge

Bump...

@msufa I pinged @simon3z and asked him to confirm/merge the PR - given that he is more familiar with the modified area and led the review. sorry for the delays.

@msufa if you could clarify the following to me - as that wiki states, Celluloid is removed from 1.0 of http (it's not clear from the link why it was removed), and setting hardcoded http gem version dependency in kubeclient to have Celluloid support can create issues for some kubeclient users who require other versions of the http gem at the moment, and can prevent from upgrading the gem version to enjoy other bug fixes, etc. Your thoughts on the topic?

@abonas, please have a look here for more details on Celluloid::IO support in http.rb: https://github.com/httprb/http/issues/272
Although there are many other benefits from using http.rb, the most significant use case for us is to utilise the non-blocking IO in watchers, implemented as Celluloid Actors, which constantly observe the state of the cluster. We believe that this is something that other users of kubeclient could benefit from.
I don't see any crucial changes in http.rb when comparing v0.9.8 with v1.0.0. I've also asked for some more details about the future of Celluloid support. Ultimately, upgrading the dependency to a version other than v0.9.8 should not break any code, as the extra socket parameters should just be ignored by the http library. This would be totally transparent for kubeclient users which don't rely on Celluloid support.

@abonas, please have a look here for more details on Celluloid::IO support in http.rb: httprb/http#272
Although there are many other benefits from using http.rb, the most significant use case for us is to utilise the non-blocking IO in watchers, implemented as Celluloid Actors, which constantly observe the state of the cluster. We believe that this is something that other users of kubeclient could benefit from.
I don't see any crucial changes in http.rb when comparing v0.9.8 with v1.0.0. I've also asked for some more details about the future of Celluloid support. Ultimately, upgrading the dependency to a version other than v0.9.8 should not break any code, as the extra socket parameters should just be ignored by the http library. This would be totally transparent for kubeclient users which don't rely on Celluloid support.

ack. thanks!


Upgrade third_party/bazel tools [phab:D485]

Created by schroederc at 2015-09-01 19:33:32:

shahms accepted this revision at 2015-09-01 19:36:30

schroederc closed via commit ce1536bf5a6fa65ee41af8eae5552f1db8c4922e at 2015-09-01 19:37:38


Properly support URIs to GLB in Instanced 3D Models

The TileData payload field carries a note that it can either contain the GLB data or an URI.
Functions like glbToI3dm or the (internal) extractGlbBuffers always assume that the payload is an embedded GLB. But this should be generalized. This will include some minor implementations for on-the-fly resolving of the GLB data from the URI and the corresponding error handling. It may also involve extending the CLI. For example, one could consider to offer an option like
... glbToI3dm -i input.glb -o output.i3dm -useUriForGlb
                                           ^--- this

at the command line.

The PR https://github.com/CesiumGS/3d-tiles-tools/pull/83 covers most of this: The functions that deal with I3DMs now usually receive an externalGlbResolver, which is a function that takes a URI and returns the Buffer with the data. (There are some degrees of freedom for things like error handling, but the main point is that external GLBs should now be supported more consistently).
The idea of generalizing the glbToI3dm command is now tracked in https://github.com/CesiumGS/3d-tiles-tools/issues/84


Request to introduce string indexing

invalid operation: type 'string' does not support indexing
Since ballerina doesn't support string indexing we have to implement another function.  try to fix this issues

Can you provide a sample code which resulted in the above error?

int string a= "Apple";
if (a[0]=="a"){}

Well, at the moment, strings aren't implemented as an index-based access type, though I can see that this can simplify the access to characters. Can you raise this in the Ballerina Dev Group?

@Sathiyakugan, you can achieve your use-case by using the substring() function.
int string a= "Apple";
if (a.substring(0,1) =="a"){}

I don't think we need to have indexing as well. @Sathiyakugan, please close the issue if you are happy with above solurtion.

May be, we can have a member function, say string::charAt(int index) returns string for string type.


pixi: fix darwin build

Description of changes
It looks like darwin fails to build because of a couple of tests. I don't image there is a major problem with darwin so this PR just disables failing tests for darwin
I don't have a ton of time to investigate what is wrong so I hope this is good enough for now.
Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

@aaronjheng @edmundmiller if you have a moment
(I'm not sure why the github ui doesn't let me tag you as reviewers, so I'm just tagging you here).


Page and Saved Colors: only allow using/adding from Color Picker

Feature Description
Per Figma, Page should not have Saved Colors section in the design panel and should only allow adding and applying colors from the Color Picker.

Alternatives Considered

Additional Context

Do not alter or remove anything below. The following sections will be managed by moderators only.
Acceptance Criteria

Implementation Brief

@barklund FYI for prioritizing

@barklund FYI for prioritizing

Figma has "excerpt" instead of "story description" for Document panel:

Figma is incorrect here, it should be "Story description", merging since this was the only found issue.


Let's put kubectl in ~/bin.

This change is

Thanks @castrojo. lgtm.

@chenopis are you a maintainer of this repo? Could you help merge this PR?

@caesarxuchao Yup, will do!


Make DirectoryChooser and FileChooser compatible with SceneBuilder

As of now, one needs to call specific factory methods to create instances of DirectoryChooserView and FileChooserView.
Any attempt to use both controls within SceneBuilder fail. This is due to the missing default constructor.

Both controls are now compatible with Scene Builder. Unfortunately the CSS requires rework as it does not work properly. Closed with 4c5b2f60eb9b591765dcaef3434ecff25b86c780.


added settings to allow filter users by telegram ids

it's already merged https://github.com/karfly/chatgpt_telegram_bot/pull/116


Glob based model paths

Some projects keep models within modules right next to controllers. Current implementation of sequelize-typescript allows to specify only path to folder with models.
What do you think about adding support for the following configuration:
modelPaths: [__dirname + '/**/*.model.ts']

Sounds good. I think we should implement this next.

#24

Hey guys.
I made some simple changes and was about to make sure they worked, before I opened a PR, when I found this discussion.
So, what will be done? Add the include option in the sequelize constructor or implement glob in the modelPaths?

Using modelPaths for an additional globing functionality should be fine. So that using a path to a directory with modelPaths should continue working as well.
@victorivens05 What is you suggestion?

@RobinBuschmann in my tests I managed to use glob and folder together.
Using glob, if you pass a folder: c:\project\models it doesn't return anything, but there's a method called glob.hasMagic with which we can detect if the user passed a folder or a glob.
If the user passed a folder, we concatenate with \* and get every file in the folder.
It should work, unless some user has a folder called !(folder), @(folder) or [folder]
The problem right now is that I work alone, so I don't have much experience working with teams. The tests seems to not be working and I don't know if I should create a branch and submit a PR.

@victorivens05 Sounds good! Don't worry. Create your PR and we will have a look :) If there is something that need to be adjusted we can discuss that in the context of your PR. If you have any questions don't hesitate to ask.

I just submitted the PR. I already think some stuff should be done differently. I didn't create a test, I'd like to create one, but I would need some help to figure out where and how it should be done.

Worth mentioning from this other issue thread

I think it would be much clearer to use only paths for modelPaths option and no globs. Using globs in include, exclude with an absolute path should work.

It might be a good idea to leave modelPaths alone, and then add include and exclude options that do exactly what your PR is doing for modelPaths.
I'll defer to @RobinBuschmann - it will be super nice to have globs either which way imo. :D

@snewell92 ha, maybe I'm right with that one. We could use an option called models for passing either an array of paths, of globs or of model references to simplify and mark modelPaths as deprecated... or include as initially intended.
@victorivens05

In my opinion, a breaking change should only be made when there is a great benefit attached to it or there is no other way to solve a problem.
The way the PR was submitted, nothing will have to change and there will be a new (altough small) feature.

I think this PR #181 closes this issue.

Closed due to #181


Publish Phase 1 - Notebooks

Summary
What/Why
This PR publishes the Phase 1 - Notebooks for the Long Stay Baseline models, part of the NHS AI Lab Skunkworks team programme.
Phase 2 will include the conversion of the notebooks into a reproducible analytical pipeline, at a date TBD.
Your approach
A series of notebooks with documentation detailing a number of baseline models to predict both Length of Stay and a Risk Score (1-5) of becoming a long stayer.
There are several limitations and future extensions captured in the documentation and at the end of several notebooks. This work represents an MVP that can be shared with the stakeholders and form the basis of a written report to be shared at a date TBD.
main is a placeholder branch which will be replaced by develop when this PR is approved (ie. please ignore merge conflicts for now).
What to review

Documentation in repo: README.md and notebooks/README.md
Notebook coding style - all files in notebooks/ executed sequentially
With access to the underlying data in Azure, technical accuracy/approach of model training/plots. Please re-install python requirements via pip install -r requirements.txt

Checklists

This pull/merge request meets the following requirements:

[X] code runs
[X] developments are ethical
[X] developments are secure (no data or notebook output)
[X] you have made proportionate checks that the code works correctly
[X] minimum usable documentation written in the docs folder

Comments have been added below around the incomplete checks.

Updates are ~ready to review~ and include:

Defining population earlier in notebook flow
Removing blanket sparse row removal, and subsequent treatment of null values
Documentation improvements across the notebooks and README files
Creation of utils.py for helper functions
Moving from GridSearchCV for every model, to a GridSearchCV on the final models


Group 5 solution to week-1 project tasks

We have created a folder "solutions_pavy" within Project_1_RBM_and_Tomography that contains our Task1 and Task2 notebooks along with the relevant contribution.txt and  CohortProject_2020_week1_business application-Team PAVY.pdf files. The contributing team consists of Pooria Madani, Yogesh Riyat, Arthur Strauss, and Vesselin Gueorguiev (Group 5 for week 1).

Great work - thanks for the extensive results & discussion.  It was a pleasure to read your submission.  Good additional Challenge material and business application video - let's keep these focused on quantum chemistry for the future weeks' projects.


check: surprising temporal NoError result

System information

Apalache version: 0.45.4 | build: 99508e4 (latest release)
OS: Linux, Ubuntu 24.04 (latest release)
JDK version [e.g. OpenJDK 0.8.0]: openjdk 21.0.4

Description
This is a bug report forwarded from Quint: https://github.com/informalsystems/quint/issues/1501
The original Quint specification was:
module buggyTemporals {
    var myState: int
    action init = myState' = 0
    action step = { myState' = myState + 1 }
    temporal temporalProps = always(myState < 0)
}

quint verify (with Apalache) fails to find a counterexample for temporalProps.
I followed @bugarela's suggestions and translated the Quint file to TLA+ then directly checked with Apalache, below is the full ouput.
Details
TLA+ specification (autogenerated by quint compile):
---------------------------- MODULE buggyTemporals ----------------------------

EXTENDS Integers, Sequences, FiniteSets, TLC, Apalache, Variants

VARIABLE
  (*
    @type: Int;
  *)
  myState

(*
  @type: (() => Bool);
*)
step == myState' := (myState + 1)

(*
  @type: (() => Bool);
*)
temporalProps == [](myState < 0)

(*
  @type: (() => Bool);
*)
init == myState' := 0

(*
  @type: (() => Bool);
*)
q_init == init

(*
  @type: (() => Bool);
*)
q_step == step

(*
  @type: (() => Bool);
*)
q_temporalProps == temporalProps

================================================================================

Config:
PROPERTIES
q_temporalProps

INIT
q_init

NEXT
q_step

Command:
apalache-mc check --config=buggyTemporals.cfg buggyTemporals.tla

Output:
16:11:50.998 [main] INFO at.forsyte.apalache.tla.tooling.opt.CheckCmd -- Loading configuration
# Usage statistics is OFF. We care about your privacy.
# If you want to help our project, consider enabling statistics with config --enable-stats=true.

Output directory: /tmp/_apalache-out/buggyTemporals.tla/2024-09-09T16-11-51_11624426143651718720
# APALACHE version: 0.45.4 | build: 99508e4                       I@16:11:51.285
  > buggyTemporals.cfg: Loading TLC configuration                 I@16:11:51.306
  > Using init predicate(s) q_init from the TLC config            I@16:11:51.351
  > Using next predicate(s) q_step from the TLC config            I@16:11:51.351
  > Using temporal predicate(s) q_temporalProps from the TLC config I@16:11:51.351
Tuning: search.outputTraces=false                                 I@16:11:51.352
PASS #0: SanyParser                                               I@16:11:51.528
Parsing file /tmp/buggyTemporals.tla
Parsing file /tmp/Integers.tla
Parsing file /tmp/__rewire_sequences_in_apalache.tla
Parsing file /tmp/FiniteSets.tla
Parsing file /tmp/__rewire_tlc_in_apalache.tla
Parsing file /tmp/Apalache.tla
Parsing file /tmp/Variants.tla
Parsing file /tmp/Naturals.tla
Parsing file /tmp/__apalache_folds.tla
PASS #1: TypeCheckerSnowcat                                       I@16:11:51.783
 > Running Snowcat .::.                                           I@16:11:51.783
 > Your types are purrfect!                                       I@16:11:52.064
 > All expressions are typed                                      I@16:11:52.065
PASS #2: ConfigurationPass                                        I@16:11:52.065
  > buggyTemporals.cfg: found PROPERTIES: q_temporalProps         I@16:11:52.190
  > Set the initialization predicate to q_init                    I@16:11:52.191
  > Set the transition predicate to q_step                        I@16:11:52.191
  > Set a temporal property to q_temporalProps                    I@16:11:52.192
PASS #3: DesugarerPass                                            I@16:11:52.194
  > Desugaring...                                                 I@16:11:52.194
PASS #4: InlinePass                                               I@16:11:52.201
Leaving only relevant operators: CInitPrimed, q_init, q_initPrimed, q_step, q_temporalProps I@16:11:52.202
PASS #5: TemporalPass                                             I@16:11:52.223
  > Rewriting temporal operators...                               I@16:11:52.223
  > Found 1 temporal properties                                   I@16:11:52.227
  > Adding logic for loop finding                                 I@16:11:52.227
PASS #6: InlinePass                                               I@16:11:52.248
Leaving only relevant operators: CInitPrimed, q_init, q_initPrimed, q_step, q_temporalProps I@16:11:52.248
PASS #7: PrimingPass                                              I@16:11:52.250
  > Introducing q_initPrimed for q_init'                          I@16:11:52.251
PASS #8: VCGen                                                    I@16:11:52.252
  > Producing verification conditions from the invariant q_temporalProps I@16:11:52.252
  > VCGen produced 1 verification condition(s)                    I@16:11:52.253
PASS #9: PreprocessingPass                                        I@16:11:52.255
  > Before preprocessing: unique renaming                         I@16:11:52.255
 > Applying standard transformations:                             I@16:11:52.260
  > PrimePropagation                                              I@16:11:52.260
  > Desugarer                                                     I@16:11:52.261
  > UniqueRenamer                                                 I@16:11:52.263
  > Normalizer                                                    I@16:11:52.264
  > Keramelizer                                                   I@16:11:52.265
  > After preprocessing: UniqueRenamer                            I@16:11:52.268
PASS #10: TransitionFinderPass                                    I@16:11:52.270
  > Found 1 initializing transitions                              I@16:11:52.284
  > Found 2 transitions                                           I@16:11:52.288
  > No constant initializer                                       I@16:11:52.289
  > Applying unique renaming                                      I@16:11:52.289
PASS #11: OptimizationPass                                        I@16:11:52.291
 > Applying optimizations:                                        I@16:11:52.300
  > ConstSimplifier                                               I@16:11:52.300
  > ExprOptimizer                                                 I@16:11:52.302
  > SetMembershipSimplifier                                       I@16:11:52.303
  > ConstSimplifier                                               I@16:11:52.304
PASS #12: AnalysisPass                                            I@16:11:52.306
 > Marking skolemizable existentials and sets to be expanded...   I@16:11:52.307
  > Skolemization                                                 I@16:11:52.307
  > Expansion                                                     I@16:11:52.308
  > Remove unused let-in defs                                     I@16:11:52.308
 > Running analyzers...                                           I@16:11:52.309
  > Introduced expression grades                                  I@16:11:52.311
PASS #13: BoundedChecker                                          I@16:11:52.311
State 0: Checking 1 state invariants                              I@16:11:52.510
State 0: state invariant 0 holds.                                 I@16:11:52.511
Step 0: picking a transition out of 1 transition(s)               I@16:11:52.513
State 1: Checking 1 state invariants                              I@16:11:52.523
State 1: state invariant 0 holds.                                 I@16:11:52.524
Step 1: Transition #1 is disabled                                 I@16:11:52.532
Step 1: picking a transition out of 1 transition(s)               I@16:11:52.533
State 2: Checking 1 state invariants                              I@16:11:52.539
State 2: state invariant 0 holds.                                 I@16:11:52.540
State 2: Checking 1 state invariants                              I@16:11:52.548
State 2: state invariant 0 holds.                                 I@16:11:52.549
Step 2: picking a transition out of 2 transition(s)               I@16:11:52.551
State 3: Checking 1 state invariants                              I@16:11:52.563
State 3: state invariant 0 holds.                                 I@16:11:52.565
State 3: Checking 1 state invariants                              I@16:11:52.572
State 3: state invariant 0 holds.                                 I@16:11:52.573
Step 3: picking a transition out of 2 transition(s)               I@16:11:52.574
State 4: Checking 1 state invariants                              I@16:11:52.583
State 4: state invariant 0 holds.                                 I@16:11:52.584
State 4: Checking 1 state invariants                              I@16:11:52.590
State 4: state invariant 0 holds.                                 I@16:11:52.591
Step 4: picking a transition out of 2 transition(s)               I@16:11:52.592
State 5: Checking 1 state invariants                              I@16:11:52.600
State 5: state invariant 0 holds.                                 I@16:11:52.602
State 5: Checking 1 state invariants                              I@16:11:52.608
State 5: state invariant 0 holds.                                 I@16:11:52.609
Step 5: picking a transition out of 2 transition(s)               I@16:11:52.610
State 6: Checking 1 state invariants                              I@16:11:52.617
State 6: state invariant 0 holds.                                 I@16:11:52.618
State 6: Checking 1 state invariants                              I@16:11:52.623
State 6: state invariant 0 holds.                                 I@16:11:52.624
Step 6: picking a transition out of 2 transition(s)               I@16:11:52.624
State 7: Checking 1 state invariants                              I@16:11:52.630
State 7: state invariant 0 holds.                                 I@16:11:52.631
State 7: Checking 1 state invariants                              I@16:11:52.636
State 7: state invariant 0 holds.                                 I@16:11:52.637
Step 7: picking a transition out of 2 transition(s)               I@16:11:52.637
State 8: Checking 1 state invariants                              I@16:11:52.645
State 8: state invariant 0 holds.                                 I@16:11:52.648
State 8: Checking 1 state invariants                              I@16:11:52.655
State 8: state invariant 0 holds.                                 I@16:11:52.656
Step 8: picking a transition out of 2 transition(s)               I@16:11:52.657
State 9: Checking 1 state invariants                              I@16:11:52.665
State 9: state invariant 0 holds.                                 I@16:11:52.667
State 9: Checking 1 state invariants                              I@16:11:52.678
State 9: state invariant 0 holds.                                 I@16:11:52.679
Step 9: picking a transition out of 2 transition(s)               I@16:11:52.680
State 10: Checking 1 state invariants                             I@16:11:52.688
State 10: state invariant 0 holds.                                I@16:11:52.690
State 10: Checking 1 state invariants                             I@16:11:52.696
State 10: state invariant 0 holds.                                I@16:11:52.697
Step 10: picking a transition out of 2 transition(s)              I@16:11:52.698
The outcome is: NoError                                           I@16:11:52.704
Checker reports no error up to computation length 10              I@16:11:52.704
It took me 0 days  0 hours  0 min  1 sec                          I@16:11:52.704
Total time: 1.418 sec                                             I@16:11:52.705
EXITCODE: OK

I sanity-checked the TLA+ specification (after some minor fixes) with TLC and it correctly finds the counterexample:
Error: Invariant temporalProps is violated by the initial state:
myState = 0

Triage checklist (for maintainers)

[ ] Reproduce the bug on the main development branch.
[ ] Add the issue to the apalache GitHub project.
[ ] If the bug is high impact, ensure someone available is assigned to fix it.

Thanks for submitting the report @lucab! I have been starring at the spec for some time, before I realized that the counter keeps incrementing. Technically, the liveness-to-safety reduction works only on finite-state systems. This explains why you were able to find a counterexample when you bounded myState in https://github.com/informalsystems/quint/issues/1501.
However, there is another subtle issue at play here. It looks like the liveness reduction does not assume Next to be stuttering. If I change q_step as q_step == step \/ UNCHANGED myState instead of just step, Apalache finds a loop. It's a bit surprising though that it does not find a self-loop but finds a loop of length 2.
@p-offtermatt could you have a look? I am not really surprised about the behavior on an infinitely-increasing counter, though the example is quite simple. But I am surprised that the minimal counterexample is of length 2, when we add stuttering. Also, do you remember, why we decided not to add stuttering by default?

You are exactly right about the incrementing counter - it is a limitation of the current implementation that to decide liveness properties, we need an execution that has a loop (as in, coming back back to a state we have already visited and thus finding an execution that can loop infinitely).
For the counterexample, if I understand correctly, this is the answer:
Apalache first nondeterministically chooses for a state to be the start of the loop, and it then needs to find this same state again. Meaning, counterexamples for temporal properties need to have at least two states (state 0 starts the loop, and then state 1==state 0 ends the loop).
I am not sure why we did not add stuttering by default - probably just to not restrict the expressivity, although it does lead to weird situations like this.

I am not sure why we did not add stuttering by default - probably just to not restrict the expressivity, although it does lead to weird situations like this.

Right. Actually, TLC uses Spec as the input for checking temporal properties, which normally has stuttering Next. We did not need that for safety and now it bites us back. Perhaps, we should only allow non-stuttering steps in the expert mode (there is no expert mode though :)).

Thanks for the feedback. You touched quite a bit of topics, so I'll try to split them across different items:

The temporal property above is a plain always check, i.e. it is a state invariant in disguise. I probably should have written it has a plain invariant without any temporal specifier, but I'm a bit surprised Apalache does not do that lifting for me. In the end, this is a condition that must hold true in each single state separately, regardless of loop-finding.

I'm actually happy that Next has no stuttering, as my Quint spec does not actually have stuttering. Otherwise, it would break some other properties (e.g. that the counter is always strictly increasing by 1 per step) in a quite opaque way. I can manually encode stuttering in Quint in specific actions, where needed.

I understand much of the trouble here come from the infinite state change, and in this (and most other cases) I can bound the execution. However that brings the additional problem of now having two caps: my arbitrary one, and the checker max-steps. If arbitrary_cap > max_steps, we are back to the problem of a (seemingly) infinite change.
Ideally I'd need some way in Quint and Apalache to derive one value from the other, e.g. execLimit = (maxSteps / 2) +1 with maxSteps coming from somewhere outside of the spec and linked to Quint/Apalache --max-steps.

The temporal property above is a plain always check, i.e. it is a state invariant in disguise. I probably should have written it has a plain invariant without any temporal specifier, but I'm a bit surprised Apalache does not do that lifting for me. In the end, this is a condition that must hold true in each single state separately, regardless of loop-finding.

This is true. The preprocessor of temporal properties could probably do a better job. It just follows the general algorithm.

I understand much of the trouble here come from the infinite state change, and in this (and most other cases) I can bound the execution. However that brings the additional problem of now having two caps: my arbitrary one, and the checker max-steps. If arbitrary_cap > max_steps, we are back to the problem of a (seemingly) infinite change.
Ideally I'd need some way in Quint and Apalache to derive one value from the other, e.g. execLimit = (maxSteps / 2) + 1 with maxSteps coming from somewhere outside of the spec and linked to Quint/Apalache --max-steps.

Yeah. This is actually a very hard problem in bounded model checking. If you are curious about it, there is a paper on reoccurence diameters. In practice, this means though that you have to use something like a napkin computation to figure out the bounds.

@konnov thanks for the paper reference, it looks like an interesting topic, I've put that up in my reading queue!
For clarity, I'm totally fine deriving an approximate bound on my own through some napkin math.
The problem is that the input parameter for this (e.g. the maxSteps above) can dynamically change outside of the spec, depending on Quint/Apalache CLI argument. And that may turn a finite execution into an infinite one, and vice-versa.
I guess I'm effectively asking for a new(?) feature which somehow propagates Quint/Apalache --max-steps value to something usable in the spec formulas. That would allow deriving a bound in the spec to make the execution finite, regardless of being invoked with --max-steps 10 or max-steps 99999.


Overwrite objects when pulling - file extensions should be taken into account

[Reproduced in version 1.70]
I am talking about this popup:

Having the some object appear seemingly multiple times is slightly confusing already, however, I can also reproduce a dump because of this:
Minimal steps to reproduce:
Publish package with a single class.
Make changes to the class in git, commit.
Make changes to the class in SAP, also change class description (to change the xml file), activate.
Now you should the option to pull in abapgit. You will be asked which files to overwrite. Select nothing, submit.
Abapgit does not distinguish between file extensions in this case and shows two identically named files (one clas.abap, one .xml) to choose from.
This causes an assert to fail in this method:
" excerpt from ZCL_ABAPGIT_OBJECTS->warning_overwrite_adjust
  METHOD warning_overwrite_adjust.
....
    LOOP AT lt_overwrite ASSIGNING <ls_overwrite>.
      READ TABLE it_overwrite INTO ls_overwrite WITH KEY
        obj_type = <ls_overwrite>-obj_type
        obj_name = <ls_overwrite>-obj_name.
      IF sy-subrc <> 0 OR ls_overwrite-decision IS INITIAL.
        zcx_abapgit_exception=>raise( |Overwrite { <ls_overwrite>-obj_type } {
          <ls_overwrite>-obj_name } undecided| ).
      ENDIF.

      IF ls_overwrite-decision = 'N'.
        DELETE ct_results WHERE
          obj_type = <ls_overwrite>-obj_type AND
          obj_name = <ls_overwrite>-obj_name.
        ASSERT sy-subrc = 0.
      ENDIF.

    ENDLOOP.

  ENDMETHOD.

since the file is attempted to be deleted twice.

looks like https://github.com/larshp/abapGit/issues/1552 is a similar issue

@FreHu try again, latest version

closing


Images missing in Dockerhub

The latest build to Dockerhub is 5 months ago as of this post. Additionally, images are not tagged with their corresponding tag number.
Should we be looking in another place?

Ryan
Thanks for bringing this to our attention.  The images should be back on Dockerhub now.
-Dave Czulada

Thanks Dave!
On Thu, Dec 19, 2019 at 09:37 dczulada<EMAIL_ADDRESS>wrote:

Ryan
Thanks for bringing this to our attention. The images should be back on
Dockerhub now.
-Dave Czulada
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/projectcypress/cypress/issues/1257?email_source=notifications&email_token=AAD3DWIJDB7PGJYA3YKVEKTQZOWNZA5CNFSM4JNBFFTKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEHKLNFI#issuecomment-567588501,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAD3DWICOPBE3NYOKEK4CRDQZOWNZANCNFSM4JNBFFTA
.


HDDS-5602. always choose the nearest one as the target in the candidates according to networkTopology

What changes were proposed in this pull request?
always choose the nearest one as the target in the candidates according to networkTopology
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-5602
How was this patch tested?
ut

@lokeshj1703 @siddhantsangwan PTAL, thanks!

@lokeshj1703 @siddhantsangwan , i have refactored the code again in the latest commit , please take a look!
if it looks good to you , i will then add the network topology related logic to this patch.
when selecting a target for a source, i think it is better to make  network topology distance as the first criteria, and then the storage usage.

thanks @lokeshj1703 very much for the review!

I think it is better to have a separated ContainerBalancerSelectionCriteria as it gives flexibility later to account both source and target limitations in the criteria.
for now , the only role of ContainerBalancerSelectionCriteria is to get Candidate Containers. but i agree with you. may be later in the future, we need to do some flexible work in ContainerBalancerSelectionCriteria. so let us keep it for now and i will cancel this refactor.

so in this patch , i will only do the network topology related work. so i want to hear your opinion, should we sorting candidate targets by network first, or make it configurable?
if we sort candidate targets by network first, we will then use a common list instead of current Treeset to hold all the candidate targets, and we should sort all the candidate targets for each source datanode with a function , for example:
List<DatanodeUsageInfo> potentialTargets;
DatanodeUsageInfo source;
NetworkTopology nt = scm.getClusterMap();
//for each source, we should sort
potentialTargets.sort((a, b) -> {
    // sort by network topology first
     int ret = 0;
     int distancetoA = nt.getDistanceCost(source, a);
     int distancetoB =  nt.getDistanceCost(source, b);
     ret = distancetoA - distancetoB;
     if (ret != 0) {
             return ret;
     }
    // if network distance is equal, sort by usage
      double currentUsageOfA = a.calculateUtilization(
          sizeEnteringNode.get(a.getDatanodeDetails()));
      double currentUsageOfB = b.calculateUtilization(
          sizeEnteringNode.get(b.getDatanodeDetails()));
      ret = Double.compare(currentUsageOfA, currentUsageOfB);
      if (ret != 0) {
        return ret;
      }
      UUID uuidA = a.getDatanodeDetails().getUuid();
      UUID uuidB = b.getDatanodeDetails().getUuid();
      return uuidA.compareTo(uuidB);
    })

I think configurable is better. It would be preferable to choose most under utilised nodes first in cases like addition of new nodes or highly unbalanced cluster.

@lokeshj1703 i have updated this patch according to the comments , PTAL!

@lokeshj1703  thanks for the review!  i have update this patch according to you comments , PTAL!

@lokeshj1703 i have added test case. could you help reviewing this patch?

@JacksonYao287 Thanks for the contribution! @siddhantsangwan Thanks for review! I have committed the PR to master branch.

thanks @lokeshj1703 @siddhantsangwan for the review!


[embedded] Serialize+deserialize vtables, fix using non-generic classes from other modules in embedded Swift

See the attached testcase that demonstrates the problem: Currently, the test fails to link with a missing symbol referencing the other module's class vtable, because (1) CMO doesn't serialize vtables, (2) IRGen doesn't emit class metadata when there isn't a Decl for the class in the module.

@swift-ci

@swift-ci please test

@swift-ci please test


Mismarked Biker on Route 8

Biker Ricardo on Route 8 is listed as having 3x Level 33 mons
Actually has 2x Level 33 and 1x Level 35 mons

Fixed! Thanks for reporting


Remove Protection

Remove the Protection API, and replace it with more descriptive methods.  CC #33.

Just pinging @danburkert.

@danburkert is there any traction? I'd like to see those changes.


Why computing the width?

What's your intention here?
Is it necessary to compute a fixed width and set it with every resize call, or could using flexbox solve your issue? https://css-tricks.com/snippets/css/a-guide-to-flexbox/
https://github.com/msdlt/h5p.LinkedImageSwap/blob/89154dd522cd8726dba857e71e353a330a0e4b61/linked-image-swap.js#L209

I'm afraid this was again just adapting H5P demo code: https://h5p.org/documentation/for-developers/responsive-design without thinking too much. I'll have a go with Flexbox later.

@theotherdy I see :-) Nothing wrong with that, but I can really recommend using a flexbox approach if you want to create a responsive layout. It's easier to understand for other coders who want to use your code and it allows others to customize the design to their needs by just overriding the CSS.

Thanks @otacke - flexbox now applied.

@theotherdy Glad you figured it out. I'd have to check if you could streamline your code even more, but I'll wait until you cleaned it up a little :-)


Min/Max Distances Swapped in Inline Docs

Not sure if these are the only two that are swapped, but it looks like the descriptions for MinCameraDistance and MaxCameraDistance are swapped in ARTSPlayerController.

Thanks @GuyPaddock - well observed! Fixed in ea006f497eb0e9be4f0c92950d1cc53bd903b5cd.


debug: Rust backtraces in alvr_client_core show  unwind frames

Description
Rust backtraces in alvr_client_core show  unwind frames. Eg.
05:04:24.799  8514-8601  [ALVR NATIVE-RUST] pid-8514 E  What happened:
 panicked at 'called `Result::unwrap()` on an `Err` value: ErrorResult(ErrorUnknown)', alvr\client_core\src\platform\android.rs:465:18
 Backtrace:
	0: <unknown>
	1: <unknown>
	2: <unknown>
	3: <unknown>
	4: <unknown>
	5: <unknown>
	6: <unknown>
	7: <unknown>
	8: <unknown>
	9: <unknown>
	10: <unknown>
	11: <unknown>
	12: <unknown>

On latest master. With and without xtask --release flag.
General Troubleshooting

[x] I carefully followed the instructions in the README and successfully completed the setup wizard
[x] I read the ALVR Wikis here and here

Environment
Hardware
Tested on android api levels 27, 30, 32. Both with a real android device (Android level 12) and AVDs
Installation
ALVR Version: Master (20v-dev10)
Install Type:

[x] Packaged (exe, deb, rpm, etc)
[ ] Portable (zip)
[x] Source

OS Name and Version (winver on Windows or grep PRETTY_NAME /etc/os-release on most Linux distributions):

Windows - Visual Code + gitbash - alvr-carboard/prepare-deps.sh + cargo xtask build-client-lib [--release]

https://github.com/alvr-org/ALVR/issues/1610#issuecomment-1553741909


Reenable detect exception plugin and switch version to 0.0.5.

v0.0.5 of the plugin has removed the upper bound on the fluentd version and is compatible with every 0.1x version of fluentd.

LGTM


retrieve depthmap given relative ply and color image

Required Info

Camera Model
{  D400 }

Language
{python }

Issue Description
Hi everyone,
I'm using pyrealsense 2.
Is it possible to retrieve the depth map of a scene given the relative ply file and color image?
can you provide a script dealing with this problem?
Thank you so much, any help is appreciated

Hi Woodstock94 ,
This one seems to be a dup of the other you created: https://github.com/IntelRealSense/librealsense/issues/3913.
Let's close this one and work on #3913.
Thanks!


[12] proposed edits for day one f2f morning session

Updated nn-6 asciidoc with changes proposed in the morning session of the May 23 Face-to-Face meeting in Alexandria VA.

Resolves #12

@bilhar97 and @TomKowal. I applied, committed and pushed the recommended changes. Probably easiest to review by focusing in and clicking on the changes related to my morning commits. @reh-imt, thanks for this initial push, I think we are close to merging this in.

Reviewed latest changes to cp_nn6.adoc. I did not review HTML (except index.html) since it is generated from the adoc. Changes look good to me. Approved.

Thanks, updated html and pushed that commit.


Remove getval from vspace(getval(...)) pattern (depends on #260)

This is a code simplification.
Includes an edit to assert_vspace_match, which is part of our 'inner loop', however, this doesn't appear to produce any performance regressions.
Benchmarking this branch against master, the only timings to change significantly are those of flatten, as expected (this is because of the changes in https://github.com/HIPS/autograd/pull/260, which this branch is based on). There is a slight regression for vspace_flatten, which was discussed in https://github.com/HIPS/autograd/pull/260 and is acceptable IMO since this method is only used by the tests.
All benchmarks:

    before     after       ratio
  [723e6777] [823c048d]
     1.14μs     1.05μs      0.92  bench_core.time_exp_call
     3.88μs     4.00μs      1.03  bench_core.time_exp_primitive_call_boxed
     3.02μs     3.21μs      1.06  bench_core.time_exp_primitive_call_unboxed
   624.39ms   592.63ms      0.95  bench_core.time_fan_out_fan_in_backward_pass
   229.18ms   230.75ms      1.01  bench_core.time_fan_out_fan_in_forward_pass
   847.61ms   831.57ms      0.98  bench_core.time_fan_out_fan_in_grad
   838.28μs   827.38μs      0.99  bench_core.time_long_backward_pass
   413.39μs   428.94μs      1.04  bench_core.time_long_forward_pass
     1.31ms     1.29ms      0.98  bench_core.time_long_grad
     3.77μs     3.75μs      0.99  bench_core.time_new_node_array
     3.63μs     3.47μs      0.96  bench_core.time_new_node_float
    39.90μs    37.92μs      0.95  bench_core.time_short_backward_pass
    18.08μs    18.29μs      1.01  bench_core.time_short_forward_pass
    90.82μs    87.40μs      0.96  bench_core.time_short_grad
     2.59μs     2.56μs      0.99  bench_core.time_vspace_array
     2.56μs     2.58μs      1.01  bench_core.time_vspace_float
      1.97y      1.96y      1.00  bench_rnn.RNNSuite.peakmem_manual_rnn_grad
      2.09y      2.10y      1.00  bench_rnn.RNNSuite.peakmem_rnn_grad
   609.16ms   617.79ms      1.01  bench_rnn.RNNSuite.time_manual_rnn_grad
   664.51ms   667.79ms      1.00  bench_rnn.RNNSuite.time_rnn_grad
-  290.68μs   211.05μs      0.73  bench_util.time_flatten
-    1.51ms   645.68μs      0.43  bench_util.time_grad_flatten
+   78.13μs   106.64μs      1.36  bench_util.time_vspace_flatten

OK sorry for being a git noob, it seems this pr includes the commits from https://github.com/HIPS/autograd/pull/260 as well as the ones which I intended. If you first merge https://github.com/HIPS/autograd/pull/260 maybe github will be smart enough to only include the extra commits in this pr?

Looks great to me. Just rebased onto master and merged.


Fix/zarf agent flux mutation

Description
Properly handle flux/pod update mutations and add test for flux in the pipeline
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)

Checklist before merging

[ ] Tests have been added/updated as necessary (add the needs-tests label)

Verifying that this PR fixes the issue we were seeing with updating the helm-releases when deploying the packages/big-bang-core/zarf.yaml package.

Is there anything we can do to get this merged today? There's been quite a few issues raised in the last few days where people are running into this bug and don't know why.

Yeah I'm going to go over all this in a bit (post Dr-pepper). I also have a patch for zarf agent I want to test via sget for existing effected envs.

If someone wants to take a look at the failing kind test that would be great.

I'm looking at the kind test now, might have to turn tracing on but I'm running the tests locally on KinD at the moment.


Can not gradlew.bat

I double click on gradlew.bat. Always stop on >Building 14% > :sbe-tool:compileJava > 111 KB/259 KB downloaded.Why ? I am in shanghai china

This is the Gradle build system. Maven also downloads dependencies. I wish the community made more efficient build systems but it is the world we have to live with.
Please take this issue up with Gradle as the question is not appropriate here.


add back grpc_artifact_android_ndk image to unbreak C# artifact build

Fixup https://github.com/grpc/grpc/pull/31961/files in v1.46.x branch.
The backport PR has by mistake removed the docker image that's needed for building Grpc C# android artifacts.
Example failed build:
https://source.cloud.google.com/results/invocations/1a51e8f9-1595-4fc6-a118-cdff4dfdd2d6/targets/github%2Fgrpc/tests

@veblush  please merge this.


Update api-interfaces to pull in tensorizer

The SDK currently throws an error due to an unknown type, which is a bug. This fixes the issue temporarily by pulling in the latest types.
https://github.com/Stability-AI/api-gitops/actions/runs/3454560101/jobs/5765943857

The SDK currently throws an error due to an unknown type, which is a bug. This fixes the issue temporarily by pulling in the latest types.

@palp In what sense is this fix temporary? Is there a more-permanent fix that's planned for later (or any aspect of this that will be undone)?

the more permanent fix is what's live in anima_stable right now. I'm guilty of doing the same thing dango was doing with generator_server and pushing commits to a development branch that should be going to main. Specifically: #114
I think my motivation at the time was since it would break backwards compatibility it should be a major version update and so it made sense to lump it in with the animation updates, but we should just fix this now. The only real dangling issue was an upstream blocking PR on api-interfaces, but that's long since merged. see https://github.com/Stability-AI/api-interfaces/pull/34 <-- eliminates the need for the touch operation in #114 's CI.
closing this in favor of merging in the changes from #114, will cobble together a PR shortly


WSL install powershell stops working, and Chrome

Version
Version 10.0.19044.1706
WSL Version

[ ] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
no distro is install yet
Other Software
No response
Repro Steps
HI, I have a new reinstalled computer start to install all program i already install chrome and it working fin, when install WSL in windows and reboot it chrome not even staring and PowerShell is staring but with error code.

So i removed the WSL again and reboot the computer , and all it wokring fin so i resintall wsl again and chrome and PowerShell stops working , with same error 0xc0000142 if i check the log about crome.exe i get Exception code: 0xc0000409
Expected Behavior
Powershell and chrome to work
Actual Behavior
This is from the windows event log:
PowerShell:
Faulting application name: conhost.exe, version: 10.0.19041.1566, time stamp: 0x56b24be3 Faulting module name: conhost.exe, version: 10.0.19041.1566, time stamp: 0x56b24be3 Exception code: 0xc0000409 Fault offset: 0x000000000001e7ff Faulting process id: 0x5f00 Faulting application start time: 0x01d86c37d8ac6247 Faulting application path: C:\Windows\system32\conhost.exe Faulting module path: C:\Windows\system32\conhost.exe Report Id: ce411055-ad12-47ff-9c5a-cfe3a8a77d2f Faulting package full name:  Faulting package-relative application ID:
Chrome crash
Faulting application name: chrome.exe, version: 101.0.4951.67, time stamp: 0x627c071e Faulting module name: chrome.exe, version: 101.0.4951.67, time stamp: 0x627c071e Exception code: 0xc0000409 Fault offset: 0x000000000011b0df Faulting process id: 0x4c40 Faulting application start time: 0x01d86c370d82066d Faulting application path: C:\Program Files\Google\Chrome\Application\chrome.exe Faulting module path: C:\Program Files\Google\Chrome\Application\chrome.exe Report Id: 6674f9cd-a862-4275-979b-149c61b5a93c Faulting package full name:  Faulting package-relative application ID:
Diagnostic Logs
No response

/logs

Hi hers i the log
logs.zip

Hi i fund what cause this it what Cisco AMP for endpoints, and now is all working again :)


[BEAM-8365] Project push-down for test table provider

InMemoryTable should implement buildIOReader(   PBegin begin, BeamSqlTableFilter filters, List<String> fieldNames) method.

Based on top of #9731
Design doc link.

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Choose reviewer(s) and mention them in a comment (R: @username).
[x] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

R: @apilloud

@amaliujia You marked as changes required. Can you take another look?

You probably want a few more test cases here:

Empty list.
All the columns.
Duplicate columns.
Invalid columns.

Otherwise LGTM

Added tests for 1-3. Passing invalid columns beaks things and is hard to test. A list of selected columns should be generated by the rule and passed to the table provider via BeamIOSourceRel. It should never get into an invalid state, where false column names are being extracted.

Run Java PreCommit

I don't have further comment.


Start and select buttons don’t work?

I downloaded a couple gb gbc Pokémon roms (pokemon brown and prism) and the start and select button don’t work on either game. Any ideas on how to resolve?

Pokemon prism won't let you use the start or select buttons before a certain point in the story (don't worry, it's early on). It's the game, not the app.

Closing as invalid. Thanks @Mastercarp.


LS to HC and Latch problems

Replace the LS series digital gates with HC series. Look into reset for the nor gate SR Latch. If possible, replace SR latch with JK latch.

 No, it is not possible to replace the SR Latch with a JK latch. This is because a so called "JK Latch" depends on the CLK to rid itself of the Invalid/Illegal state for the SR latch's 1 1 o/p. Making it a flipflop. Dropping the idea, solution is to look into the RESET mechanism of a SR latch.

The higher voltage logic gates are added, this allows for us to directly use the GLV power supply. After  the changes, the entire logic of the board now runs on 12V.


By default, don't depend on mysql in ewok-env

Is your feature request related to a problem? Please describe.
At the moment, mysql is a hard dependency in ewok-env, and because it's tricky to install and comes with narrow version constraints on boost, we've either installed it manually and made it available as an external package, or we've come up with workarounds to build a canned/internal boost just for mysql. The reality, mysql is only needed in one special case, which is
running JEDI-Skylab in localhost mode. This only happens on macOS laptops at JCSDA, on the JEDI Singlenode AMI for AWS, and on AWS ParallelCluster. HPCs,  non-JCSDA user installations, and other cloud systems can be installed w/o mysql.
Describe the solution you'd like
As discussed in https://github.com/JCSDA/spack/pull/401, we are going to define a variant +mysql for ewok-env that by default is false. We will provide instructions for users to set that variant to true and install an external mysql server (same as they do now) if needed. JCSDA will also maintain external mysql installations on the two systems that need it, with the necessary site config/documentation.
Additional context
This issue is related to https://github.com/JCSDA/spack-stack/issues/705

Closed via https://github.com/JCSDA/spack-stack/pull/993


Feat: Add Google Translate

Describe the feature
I want to add google translate feature in the website,
Add ScreenShots

Record

[X] I agree to follow this project's Code of Conduct
[X] I'm a GSSOC'24 contributor
[X] I want to work on this issue

Go ahead !!


Number of bits not preserved in tk_to_qiskit conversion with RangePredicate

Whilst looking into https://github.com/CQCL/pytket-qiskit/issues/375 I found that the number of bits was not preserved in the tk_to_qiskit conversion. I think this may well be the cause of the KeyError issue.
from pytket import Circuit, OpType
from pytket.circuit.logic_exp import reg_eq
from pytket.extensions.qiskit import tk_to_qiskit

main_circ = Circuit(2, 2, "main_circ")

creg_0 = main_circ.add_c_register("creg_0", 2)

main_circ.add_gate(OpType.CH,[0, 1], condition = reg_eq(creg_0, 3))

main_circ.measure_all()
print(main_circ.n_bits) # gives 5

But if I convert to a qiskit QuantumCircuit...
qc = tk_to_qiskit(main_circ)
print(qc.num_clbits) # gives 4

We only get 4 bits in the converted qiskit circuit. it seems the tk_SCRATCH_BIT[0] bit is lost in the conversion.

I think this is expected. In pytket, a scratch bit is required to store the evaluation of a range predicate, for example, if c == 2 tk_scratch_bit[0] = 1, and then condition a gate on that scratch bit, i.e., if tk_scratch_bit[0]==1 H(1). When converting such a conditional gate to qiskit, we combine these two instructions into one and remove the separate evaluation, resulting in  if c == 2 H(1). Since tk_scratch_bit is no longer used, we don't add it to the qiskit circuit.
qc[0].condition

prints
(ClassicalRegister(2, 'creg_0'), 2)

suggests that the CH gate has the correct condition

Closing as I think this is expected behaviour.


What about the move-V-button-to-addressbar?

Hi @justdanpo,
glad that you restarted the project!
There was a move-V-button-to-addressbar.js that was doing a very useful thing, especially when you use the vertical tabs in full screen without full menu.
 I added a few CSS rules in the browser.html that remove it completely:
#browser #tabs-container.top{ padding-left: 0px }
#browser.native:not(.tabs-top):not(.horizontal-menu) #header { display: none }
#titlebar > .vivaldi { display: none }
#browser.horizontal-menu .vivaldi-addressbar {display: none }

However that is not optimal, since you have to rely to the Alt key to get the menus.
Having the icon baack in the addresbar would completely solve the problem.

I'm not sure I understand you. Do you mean empty title bar is displayed in maximized window? If so I need to know which settings lead to this.
In non-maximized windows we need to have something we can drag windows by.

Not the window title bar, I mean the bar usually used for tabs. When the tabs are vertical is totally useless and contains only the icon for the Vivaldi menu. The old move-V-button-to-addressbar hook was moving it in the address bar area an hiding the bar that contained it.

In April I added move-V-button-to-addressbar.js functionality to move-window-buttons-maximized.js. Check out this wiki page for hooks descrption, may be you'll find anything useful.

I saw that and I tried to activate it, but it doesn't do anything to the V-button. Did I miss anything?

I see... I am using the linux version and looking into the hook code it apply the display:none only to non native window. in my case the css should be:
#browser:not(.popup):not(.horizontal-menu):not(.tabs-top).maximized #header { display: none; }

Then the .MaximizedWindowButtons styles are only for windows, so no mac nor linux.
I think I can create a new hook for my need by just cherry-picking  and adapting what I need from your code. Thank you.

It moves V button to the address bar

It doesn't do it in 2 cases:

tabbar is placed at the top (as there is not separate titlebar in this setup)
Vivaldi window is not maximized: we need a place we can use to move window via drag'n'drop

Talking about the second one I could replace it with a narrow bar of the same color as the address bar.

Vivaldi window is not maximized: we need a place we can use to move window via drag'n'drop

If it is using a native window it has its own window title bar to drag it around, so it could be removed also in that case.

Please check the latest update

The last update fixed it! Than you!


Send CircleCI notifications to Zulip

We didn't get a notification but we also didn't get an error so I'm merging this in hopes that it is only sending notifications after master passes. Will find out. Probably not but ¯_(ツ)_/¯.


restructure and add spdy to browser tests

WIP

Going to merge this and update libp2p-ipfs-browser, so that then we can test js-ipfs with bitswap on top of it :)


[BugFix] Fix NPE when export job waiting coordinator profile finish

What type of PR is this：

[x] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #14709
Problem Summary(Required) ：

connectContext can be null for broker export task coordinator.
Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[ ] 2.5
[ ] 2.4
[ ] 2.3
[ ] 2.2

[FE PR Coverage Check]
:disappointed: fail : 0 / 3 (00.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/qe/Coordinator.java
0
3
00.00%
[1453, 1454, 1456]

run starrocks_admit_test

[FE PR Coverage Check]
:disappointed: fail : 1 / 2 (50.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/qe/Coordinator.java
1
2
50.00%
[1458]

run starrocks_admit_test

run starrocks_admit_test

[FE PR Coverage Check]
:disappointed: fail : 0 / 3 (00.00%)
file detail

path
covered_line
new_line
coverage
not_covered_line_detail

:large_blue_circle:
com/starrocks/qe/Coordinator.java
0
3
00.00%
[1445, 1446, 1448]

run starrocks_admit_test

@mergify backport branch-2.5 branch-2.4 branch-2.3


Annoying Package error

Hi. I have an annoying console error: Asset Packages/com.vertx.debugging/Editor/Assets has no meta file, but it's in an immutable folder. The asset will be ignored.
Unity 2021.3.15
com.vertx.debugging v2.0.4 OpenUPM
Please add .meta file for the Assets folder to fix it ;)

This is a bug because there previously was a meta file. There should not be a folder at all, or a meta file. The bug is transient and only based on the state of the package cache.
You can delete any Assets folder that hasn't been cleaned up in the package (it should be empty).

Actually, now I look at it further I was mistaking two issues; it's a discrepancy between how OpenUPM handles gitignores, and how git does. I have this meta file present in git, but OpenUPM does not publish it. I've changed some names in the gitignore and this seems to have fixed it (in version 2.0.6)

@vertxxyz I understand. Thanks for fix ^_^


[KARAF-6479] Add features json format support

I'm just happing a test on FeaturesService to make Sonar happy ;) Thanks for the update.


using schemathesis or similar tools for testing purposes

Description
I saw these two issues raised recently,

Sometimes our API specifications get outdated and out-of-sync with our implementation. we should always respect this contract, but how to make sure it is always respected and updated?
We need to test our API functionality regularly to ensure it is working properly, a PR was submitted to run basic tests in a GitHub action. it will add one more thing to the stack that is needed also to keep in sync with every change.

I want to point out that there are many tools that can generate and run tests from the API specification.
e.g, schemathesis is an API testing tool that could run thousands of generated test cases given just the API schema.
This could solve these two issues and provides added benefits:

The API specification is the source of truth, this will help us to improve the API and make sure that API specification remains in sync with the implementation. issue no1. solved.
No tests code to write or maintain, less work. issue no.2 solved.
Better coverage. the tool will run thousands of tests.
GitHub action is available out of the box (for the suggested tool).

It is expected to have many falling tests when we start to use this tool, but I see this as a pro and a way to improve and fix invisible issues.

What is the status here? please make sure it's updated and merged or let's close the PR

@ramezsaeed @A-Harby what are we going to do with this one?

I will update the old PR code and version at https://github.com/threefoldtecharchive/tfgridclient_proxy/pull/297, and create a new PR on this repo after.

wip:
Create a new PR with new versions, all the networks and locally, and some fixes: https://github.com/threefoldtech/tfgrid-sdk-go/pull/695, waiting for reviews.

Any progress or help needed for This one?

Any progress or help needed for This one?

I'll update the PR with some changes as requested here: https://github.com/threefoldtech/tfgrid-sdk-go/pull/695#issuecomment-1937556279 and will request a re-review.

Approved and done: https://github.com/threefoldtech/tfgrid-sdk-go/pull/695#pullrequestreview-2015909505.


Problem with credentials

When i add my live secret key i get exception : Problem with Paystack Credentials

Are you running the latest version of the plugin? Check your pubspec.yaml, should be version 1.0.1, Thank you!

Running into same issue

Its an issue from paystack. Try again later if youre sure your paystack secret key is correc

I have triple checked my credentials. I see you throw an exception of "problem with credentials" on any status code aside 200. How about the actual error code is returned for easy debugging?

Plugin works but i will output the error out as youve suggested, expect an update latest by noon 1200GMT

Okay. Still debugging. Thanks a tonne, Mann!

Mind you, reference number cannot be repeated

Yes I understand, it's not being repeated. Having the actual status code will provide some clarity and direction. Will be on standby for updated plugin

No worries, am on it

Done, expect an update anytime soon

Hope @Samson11 this update helps you fix your bugs now and in the future. Thank you.

v1.02 is ready!!  https://pub.dev/packages/pay_with_paystack/versions/1.0.2

🎊
Managed to debug to see API throwing errors as reference was longer than permitted length. v1.0.2 will really help with debugging. This can be closed now.


Support disk/embedded/remote store via libsql

Adding libsql as an optional backend, enabling embedded or disk-local caches
https://github.com/long2ice/fastapi-cache/issues/273

Can you add test cases for testing new features? thk.


Introduce rally-tracks compatibility testing

This PR adds the infrastructure necessary to run rally-tracks integration tests (see https://github.com/elastic/rally-tracks/pull/289) from within the Rally repository, both locally and--more importantly--as a PR check via CI.
We modify and extend the pytest-rally plugin so that its behavior and defaults make sense when run from within the Rally repo as opposed to a track repo. This enables Rally developers and CI jobs to test Rally changes against arbitrary revisions of local track repositories, using arbitrary versions of Elasticsearch.
In the default case, it simply ensures that changes being made to Rally do not break the master branch of rally-tracks. It does this by executing whatever tests are contained in the it subdirectory of ~/.rally/benchmarks/tracks/default. By default, it uses a build of the main branch of ES from source (i.e. --revision=current in Rally terms) as the benchmark candidate.
To run these tests, execute pytest it/track_repo_compatibility/ from the root of the Rally repo after running make install, or run make rally-tracks-compat to run them within a tox environment.
Default behavior
Here's an example of what happens by default, but we'll limit the example to just one test (for brevity of output) and add some extra logging to more clearly see what the pytest-rally plugin is doing:
pytest it/track_repo_compatibility --log-cli-level=INFO -k metricbeat
===================================================================================== test session starts ======================================================================================
platform linux -- Python 3.8.13, pytest-6.2.5, py-1.11.0, pluggy-1.0.0 -- /home/baamonde/code/elastic/rally/.venv/bin/python3
cachedir: .pytest_cache
benchmark: 3.2.2 (defaults: timer=time.perf_counter disable_gc=False min_rounds=5 min_time=0.000005 max_time=1.0 calibration_precision=10 warmup=False warmup_iterations=100000)
rally: track-repository=/home/baamonde/.rally/benchmarks/tracks/default, track-revision=master
rootdir: /home/baamonde/code/elastic/rally, configfile: pyproject.toml
plugins: benchmark-3.2.2, rally-0.0.1, asyncio-0.18.1, anyio-3.6.1, httpserver-1.0.4
asyncio: mode=strict
collecting ...
------------------------------------------------------------------------------------- live log collection --------------------------------------------------------------------------------------
INFO     pytest_rally.rally:rally.py:110 Running command: [esrally list tracks --track-repository="/home/baamonde/.rally/benchmarks/tracks/default" --track-revision="master" --configuration-name="pytest"]
collected 68 items / 67 deselected / 1 selected

test_all_tracks_and_challenges.py::TestTrackRepository::test_autogenerated[metricbeat-append-no-conflicts]
---------------------------------------------------------------------------------------- live log setup ----------------------------------------------------------------------------------------
INFO     pytest_rally.elasticsearch:elasticsearch.py:84 Installing Elasticsearch: [esrally install --quiet --http-port=19200 --node=rally-node --master-nodes=rally-node --car=4gheap,trial-license,x-pack-ml --seed-hosts="<IP_ADDRESS>:19300" --revision=current]
INFO     pytest_rally.elasticsearch:elasticsearch.py:93 Starting Elasticsearch: [esrally start --runtime-jdk=bundled --installation-id=a14708f6-d2c0-49e1-aaa2-dd60a2acaf9d --race-id=b50f7204-3f70-4724-bb91-3e0050d0e2e0]
---------------------------------------------------------------------------------------- live log call -----------------------------------------------------------------------------------------
INFO     pytest_rally.rally:rally.py:144 Running command: [esrally race --track="metricbeat" --challenge="append-no-conflicts" --track-repository="/home/baamonde/.rally/benchmarks/tracks/default" --track-revision="master" --configuration-name="pytest" --enable-assertions --kill-running-processes --on-error="abort" --pipeline="benchmark-only" --target-hosts="<IP_ADDRESS>:19200" --test-mode]
PASSED                                                                                [100%]
-------------------------------------------------------------------------------------- live log teardown ---------------------------------------------------------------------------------------
INFO     pytest_rally.rally:rally.py:91 Removing Rally config from [/home/baamonde/.rally/rally-pytest.ini]
INFO     pytest_rally.elasticsearch:elasticsearch.py:104 Stopping Elasticsearch: [esrally stop --installation-id=a14708f6-d2c0-49e1-aaa2-dd60a2acaf9d]

============================================================================== 1 passed, 67 deselected in 33.14s ===============================================================================

You can see that we've applied the defaults for the --track-repository and --track-revision options in the first few lines of the output:
rally: track-repository=/home/baamonde/.rally/benchmarks/tracks/default, track-revision=master
And that these make their way into the esrally commands that pytest-rally generates:
INFO     pytest_rally.rally:rally.py:144 Running command: [esrally race --track="metricbeat" --challenge="append-no-conflicts" --track-repository="/home/baamonde/.rally/benchmarks/tracks/default" --track-revision="master" --configuration-name="pytest" --enable-assertions --kill-running-processes --on-error="abort" --pipeline="benchmark-only" --target-hosts="<IP_ADDRESS>:19200" --test-mode]`

Overriding defaults
For local development, overriding these defaults could be useful. For example, if you're working on changes to both Rally and rally-tracks locally, and want to test with a released version of ES, you could do something like this:
pytest it/track_repo_compatibility/ \
    --log-cli-level=INFO \
    --track-repository=/home/baamonde/code/elastic/rally-tracks \
    --track-revision=ci \
    --distribution-version=8.3.2 \
    -k metricbeat

The pytest session header will reflect these changes:
rally: track-repository=/home/baamonde/code/elastic/rally-tracks, track-revision=ci

The plugin will pass along the --distribution-version to install the ES fixture:
INFO     pytest_rally.elasticsearch:elasticsearch.py:84 Installing Elasticsearch: [esrally install --quiet --http-port=19200 --node=rally-node --master-nodes=rally-node --car=4gheap,trial-license,x-pack-ml --seed-hosts="<IP_ADDRESS>:19300" --distribution-version=8.3.2]

And race commands will provide the correct --track-repository and --track-revision:
INFO     pytest_rally.rally:rally.py:144 Running command: [esrally race --track="metricbeat" --challenge="append-no-conflicts" --track-repository="/home/baamonde/code/elastic/rally-tracks" --track-revision="ci" --configuration-name="pytest" --enable-assertions --kill-running-processes --on-error="abort" --pipeline="benchmark-only" --target-hosts="<IP_ADDRESS>:19200" --test-mode]

Thanks for the review @pquentin! I believe I've addressed your comments, so this is ready for another look whenever you're free.

Haven't tested the CI configuration though

It's a little cumbersome (especially for jobs triggered by PRs) unless you're conversant in the local Jenkins workflow we use internally, which maybe you are already. We can sync on this if you'd like.


Disable users

Author Name: Ruben S. Montero (@rsmontero)
Original Redmine Issue: 2030, https://dev.opennebula.org/issues/2030
Original Date: 2013-05-13

Add disable/enable functions for users. A disable user will not:

be able to make any api call
log in sunstone interface

Original Redmine Comment
Author Name: Ruben S. Montero (@rsmontero)
Original Date: 2013-05-17T18:57:59Z

DON'T FORGET EC2 and OCCI

Original Redmine Comment
Author Name: John Noss (John Noss)
Original Date: 2017-01-25T20:33:25Z

This would be a great feature to have, +1 from me! Also, to confirm, will this revoke any existing sessions (sunstone or xmlrpc cli authenticated)? (And, will this work for ldap users, as well?)

PRs (merge to master):

src: https://github.com/OpenNebula/one-ee/pull/545
tests: https://github.com/OpenNebula/development/pull/1233
doc: https://github.com/OpenNebula/docs/pull/1381

Needs Sunstone to expose:

User state in the datatable
Add enable/disable button

This can be mimicked from the host tab.

@tinova PRs to be approved:

code
docs

@tinova PRs to be approved:

code
docs

needs testing

needs testing

@tinova PR to be approved:

Tests