Suggestion: Use more flexbox and fewer hardcoded px measurements

This is partially design related.
The issue is that we have many hard coded measurements in the code, such as this:
margin-right: 149px;

Implementing alignments like that might be debilitating us long-term in terms of implementing design changes, especially when it comes to implementing responsive design. A lot of times it might mean having to implement the same thing for every breakpoint separately, while we might not need breakpoints at all in many cases if we use 'flexbox'.
My proposal is that we should:

Avoid hard coded measurements whenever possible
Implement alignment using flexbox, or more classical alternatives, so we can avoid manual alignment
Aim to use a "palette" or "inventory" of a few specific measurement values for font sizes and spacings. (i.e. sp-sm: 16px, sp-md: 24px etc..)

As an extra regarding the "inventory" or "palette": it might be a nice idea to aim for a consistent vertical rhythm. This is just a personal opinion, but I think it'd be nice if spacings, font sizing and vertical measurements (such as card height) should be integer multiples of the same number.
I know this is a huge ask and it probably cannot be part of our current scope, but better yet, we could do a baseline alignment, i. e. non-typographical elements and typographical elements with different typesetting would be aligned to the same baseline. Here's an article that explains what I mean: https://www.smashingmagazine.com/2012/12/css-baseline-the-good-the-bad-and-the-ugly/

Regarding the flexbox point and moving away from pixel-perfectness, I agree with you. I think we should consider this approach since we will need the app to be reliably well rendered across several devices(diff screen-sizes) and browsers. Not aiming for pixel-perfection but for a "consistent" design can ease this task.

it might be a nice idea to aim for a consistent vertical rhythm [...] should be integer multiples of the same number.

This is too philosophically deep, don't have a personal opinion yet :smile:  Interesting tho
cc @mjancik

Vertically the designs are based on our 4px grid which we are all following when creating the designs. There might be very specific exceptions but as for now our Orbit guidelines consist of these vertical spacings: Desktop: 4, 8, 12, 16, 24, 32, 40, 52 (in px) / Mobile: 4, 8, 12, 16, 20, 28, 36, 44 (in px).

since is a suggestion and we all agree we should use more flex-box and fewer hardcoded px measurements can we close the issue? @kantord

Yup!


Feature custom icons

Custom Icons
Possibility to customize the icons for the directories and for the fallback of files not yet supported by nvim web icons.

Ready

I've taken care of it. Thanks for the PR!


FRU-83 Create Bulk Mutation to for adding "Core Recipe" Preparation tags

Description
This features adds a bulk mutation function to the adds a "Core Recipe" Preparation tag to all BASE Recipe Items provided. The script requires as input, a set of recipe item IDs provided by the Culinary OPS, locates all recipe items in Galley, and for each the base recipe (Usage Recipe) and appends a "Core Recipe" tag to the Preparations field. The feature only appends this tag, if the tag is not previously there.
Test Plan
For the manual test plan, we want to use the feature to create a fresh new set of base recipe items that with the "Core Recipe" Preparations tag

Sign in to Galley here
Go to Preparation: Core Recipe of the Galley staging-app to view all recipes that contain a "Core Recipe" preparation

Testing a single recipe id:

Open terminal and run python from the galley-sdk root folder:

>>> from galley.queries import *; from galley.enums import *; from galley.mutations import *;

>>> get_untagged_core_recipe_item_ids(["cmVjaXBlOjIwMjI5NA=="])    # recipe id for Harissa Roasted Carrot Salad BASE

[ ]  Verify result: ['cmVjaXBlSXRlbToxMjkwMTgx', 'cmVjaXBlSXRlbToxMjkwMjAw']

Note: These two recipe item ids correspond to the Harissa Roasted Carrot Salad BASE / "cmVjaXBlOjIwMjI5NA==" as a unique component of its two parent recipes (scroll to bottom of the page under the "USAGES" section):

(1) Harissa Roasted Carrot Salad with Paprika Chicken
(2) Harissa Roasted Carrot Salad with Paprika Kidney Beans

Run the batch job for adding Core Recipe preparation to all the recipe items that require the Harissa Roasted Carrot Salad BASE recipe above:

>>> update_recipe_item_data({"ids": ["cmVjaXBlOjIwMjI5NA=="], "attrs": {"preparationIds": ["cHJlcGFyYXRpb246MzEzNjk="]}})

Note: update_recipe_item_data() automatically runs get_untagged_core_recipe_item_ids() when called.

Refresh page from Step 2 and verify that these recipes are shown to now contain a "Core Recipe" preparation:

[ ] (1) Harissa Roasted Carrot Salad with Paprika Chicken
[ ] (2) Harissa Roasted Carrot Salad with Paprika Kidney Beans

Testing multiple recipe ids:

Run method with three recipe ids passed in:

>>> get_untagged_core_recipe_item_ids(["cmVjaXBlOjIwMjI5NA==", "cmVjaXBlOjE3NjQxNA==", "cmVjaXBlOjE4MDAwMw=="])
# recipe ids for Harissa Roasted Carrot Salad BASE, Daikon Sunflower Salad BASE, & Roasted Apple & Squash Chipotle Chili BASE

[ ] Verify result: ['cmVjaXBlSXRlbToxMTUwNDY5', 'cmVjaXBlSXRlbToxMTUwNDE3', 'cmVjaXBlSXRlbToxMTY0Njg5', 'cmVjaXBlSXRlbToxMTY0NTgy', 'cmVjaXBlSXRlbToxMjkyNjU3', 'cmVjaXBlSXRlbToxMjkyNjYy']

Note: The ids from Step 3 should not be included in this return list since they've already had the "Core Recipe" preparation applied in Step 5

Run the batch job for adding "Core Recipe" preparation to all recipe items that require the Harissa Roasted Carrot Salad BASE,  Daikon Sunflower Salad BASE, & Roasted Apple & Squash Chipotle Chili BASE.

update_recipe_item_data({"ids": ["cmVjaXBlOjIwMjI5NA==", "cmVjaXBlOjE3NjQxNA==", "cmVjaXBlOjE4MDAwMw=="], "attrs": {"preparationIds": ["cHJlcGFyYXRpb246MzEzNjk="]}})

Refresh page from Step 2 and verify that these recipes are shown to now contain a "Core Recipe" preparation:

2 usage items for Harissa Roasted Carrot Salad BASE / cmVjaXBlOjIwMjI5NA==

[ ] (1) Harissa Roasted Carrot Salad with Paprika Chicken
[ ] (2) Harissa Roasted Carrot Salad with Paprika Kidney Beans

2 usage items for Daikon Sunflower Salad BASE / cmVjaXBlOjE3NjQxNA==

[ ] (1) Daikon Sunflower Salad with Ginger Maple Dressing and Garlic Chicken
[ ] (2) Daikon Sunflower Salad with Ginger Maple Dressing and Garlic Mung Beans

4 usage items for Roasted Apple & Squash Chipotle Chili BASE / cmVjaXBlOjE4MDAwMw==

[ ] (1) Roasted Apple & Squash Chipotle Chili with Herb Pinto Beans
[ ] (2) Roasted Apple & Squash Chipotle Chili with Paprika Chicken
[ ] (3) Roasted Apple & Squash Chipotle Chili with Savory Ground Turkey
[ ] (4) Roasted Apple & Squash Chipotle Chili with Savory Pinto Beans

Notice that we've now ran the command update_recipe_item_data() twice on Harissa Roasted Carrot Salad BASE / cmVjaXBlOjIwMjI5NA==. Go to parent recipe pages and verify that ONLY ONE "Core Recipe" preparation chip is present for the Harissa Roasted Carrot Salad BASE recipe under the "COMPONENTS" section:

[ ] (1) Harissa Roasted Carrot Salad with Paprika Chicken
[ ] (2) Harissa Roasted Carrot Salad with Paprika Kidney Beans

It came up in conversation with Ugo today that the desire for this is to have as a one off for ops to run to identify recipes that need updating, not for regular execution.
If this is the case it might be good to look at creating a separate place to keep logic such as this where it's clearly documented and understood that these methods were built for a very specific purpose.  Potentially something like a management.py file??


Make attribution getters public.

In some applications it is nice to have a custom attribution control that for example can merge attributions for multiple layers. With the current API this is quite cumbersome.
This PR makes the getAttributions and getAttributionsCollapsible methods of ol/source/Source public to enable a custom attribution handling.

This sounds ok to me, but I’m wondering if there is something that could be done to make the attribution control more flexible.  @simonseyock could the logic for your custom control be handled be a more flexible control in the library?

The control would need to have an aggregation function that ideally not only gets the attribution but also the layer passed.
Something like:
attributionReducer: (attributions: string[], attribution: string, layer: Layer) => string[]

I can add this if wanted, but I still think that the getAttribution function should be public.


Inlining Analyzer integration

hey,
would it be possible to integrate the Inlining Analyzer  into rider?
cheers,
Wojtek

@wklm From a brief look I don't think it'd be feasible without rewriting a part of the analyzer itself right now. If it was a ReSharper extension, it'd be relatively easy to make it work in Rider, but it is an extension for Visual Studio that relies on VS APIs that ReSharper (and, consequently, Rider) doesn't have.
Using custom Roslyn analyzers is planned for 2018.1 Rider release, so as soon as it's available adding such analyzer by a user should be possible.

Closing as the question was answered.

Roslyn analyzers are now part of Rider, but they do not seem to include the functionality provided by the Inlining Analyzer, at least not that I was able to find in the settings.
https://www.jetbrains.com/help/rider/Using_NET_Compiler_Analyzers.html
Are there any plans to make inlining analysis available in Rider? I have some hot paths in my code where it would be helpful if I could quickly check in Rider if there's anything preventing calls from being inlined as intended.

@pineapplemachine This is the F# plugin repo, and F# uses its own analysers SDK, not compatible with Roslyn. For questions about Roslyn integration in Rider please file an issue on YouTrack.

Ahhh, my mistake. I came here from a search result and didn't realize where I'd ended up. Sorry about that!

@pineapplemachine No problem, I'm happy to help!


Page is broken

On the VDJ_Analysis_fixed page, right after "head(s_balbc_pbmc[[]])" the entire remainder of the page is showing the rmarkdown code instead of the HTML rendition.

Thanks for the heads up! I will try to get this fixed. In the mean time, you might try the same page on this year's version of the course: https://ucdavis-bioinformatics-training.github.io/2022-March-Advanced-Topics-in-Single-Cell-RNA-Seq-VDJ/


Add nyc (Istanbul) -> coveralls coverage

Could not drill down into the file on coveralls website, but their design is on point.

Could not drill down into the file on coveralls website, but their design is on point.

Good catch, thanks!  Fixed that by pulling levers at random, PTAL.

Here's a sample result for your perusal.

Thanks!
Pulling in the hope that master is somehow magic and the UI will start working for everyone, not just me.

Pulling by force: those 3 remaining "build"s are just the old names for "test".  They should go away.


Add Makefile

Signed-off-by: Nicolas Lamirault<EMAIL_ADDRESS>

Can you change the .travis.yml to ensure the test and build are stable w/ Makefile?

Thanks a lot for this PR!


Compile failed in Qt Creator: cmake: No such file or directory

I tried to import mapd-core into Qt Creator 4.3.1 and compiled, came out with the following error.
It is probably caused by miss configurations in the IDE, but would be greatly helpful if you can give me a hint.
00:16:58: Running steps for project mapd...
00:16:58: Starting: "/usr/local/bin/cmake" --build . --target all
[  2%] Built target calciteserver_thrift
[  3%] Built target sqlite3
[  4%] Built target SqliteConnector
[  6%] Built target Utils
[  8%] Built target StringDictionary
[  9%] Built target Fragmenter
[ 10%] Built target Calcite
[ 11%] Built target Catalog
[ 12%] Built target CudaMgr
[ 19%] Built target DataMgr
[ 20%] Built target Chunk
[ 23%] Built target Shared
[ 24%] Built target initdb
make[2]: cmake: No such file or directory
make[2]: *** [CMakeFiles/rerun_cmake] Error 1
make[1]: *** [CMakeFiles/rerun_cmake.dir/all] Error 2
make: *** [all] Error 2
00:17:00: The process "/usr/local/bin/cmake" exited with code 2.
Error while building/deploying project mapd (kit: mapd-kit)
When executing step "CMake Build"
00:17:00: Elapsed time: 00:01.

Node that by checking the log, Qt Creator use server mode with cmake, to generate targets, e.g:
Running "/usr/local/bin/cmake -E server --pipe=/tmp/cmake-1SZfel/socket --experimental" in /Users/flow/workspace/github/mapd-core/build.qt.
The C compiler identification is AppleClang <IP_ADDRESS>00042
The CXX compiler identification is AppleClang <IP_ADDRESS>00042
Check for working C compiler: /usr/bin/gcc
Check for working C compiler: /usr/bin/gcc -- works
Detecting C compiler ABI info
Detecting C compiler ABI info - done
Detecting C compile features
Detecting C compile features - done
Check for working CXX compiler: /usr/bin/clang++
Check for working CXX compiler: /usr/bin/clang++ -- works
Detecting CXX compiler ABI info
Detecting CXX compiler ABI info - done
Detecting CXX compile features
Detecting CXX compile features - done
Looking for pthread.h
Looking for pthread.h - found
Looking for pthread_create
Looking for pthread_create - found
Found Threads: TRUE
Found CUDA: /usr/local/cuda (found version "8.0")
Found Git: /usr/bin/git (found version "2.10.1 (Apple Git-78)")
Found Gflags: /usr/local/lib/libgflags.dylib
Found Glog: /usr/local/lib/libglog.dylib
Found Thrift: /usr/local/lib/libthrift.dylib
Found ZLIB: /usr/lib/libz.dylib (found version "1.2.5")
Found PNG: /usr/local/lib/libpng.dylib (found version "1.6.29")
Found GDAL: /usr/local/Cellar/gdal/1.11.5_2/lib/libgdal.dylib
Found Folly: /usr/local/lib/libfolly.dylib
Found Curses: /usr/lib/libcurses.dylib
Found JNI: /System/Library/Frameworks/JavaVM.framework
Looking for bison++
Looking for bison++ -- /usr/local/bin/bison++
Looking for flex++
Looking for flex++ -- /usr/bin/flex++
Configuring done
Generating done
CMake Warning:
  Manually-specified variables were not used by the project:

    QT_QMAKE_EXECUTABLE

Got fix by setting environment vars like PATH to IDE.


Issue with k8s.io/docs/tasks/administer-cluster/kubeadm/kubeadm-certs/

This is a Bug Report

Problem:
A cluster set-up using kubeadm needs a yearly certificate renewal procedure. This procedure consists of renewal of server certificates as well as client certificates. The client certificates renewal procedure is missing.
IMO after kubeadm alpha certs renew all either the client certificates in :
/etc/kubernetes/kubelet.conf, /etc/kubernetes/controller-manager.conf, /etc/kubernetes/scheduler.conf, /etc/kubernetes/admin.conf
should be renewed as well or the documentation should clearly suggest to renew clients certificates by doing:
cd /etc/kubernetes/
mv {admin.conf,controller-manager.conf,mv kubelet.conf,scheduler.conf} ~/
kubeadm init phase kubeconfig all

Proposed Solution:
I think that kubeadm alpha certs renew all should also update the client certificates.
Page to Update:
k8s.io/docs/tasks/administer-cluster/kubeadm/kubeadm-certs/

v1.13.10

/sig cluster-lifecycle
Looks valid, I'll let someone from SIG Cluster Lifecycle make a call on this.

1.13 is out if support. Please try 1.15 at minimum. I am pretty sure
'renew' updates .conf files in later versions.
On Mon, Dec 16, 2019, 14:08 Tim Bannister<EMAIL_ADDRESS>wrote:

/sig cluster-lifecycle
Looks valid, I'll let someone from SIG Cluster Lifecycle make a call on
this.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/website/issues/18169?email_source=notifications&email_token=AACRATFNEGJ2YFK6WBEII63QY5VSZA5CNFSM4J3HYWGKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOEG6P6CY#issuecomment-566034187,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AACRATBUIJ3GV5J2W54OYILQY5VSZANCNFSM4J3HYWGA
.

Upgraded step-by-step to v1.16.4. The client certificates seem all updated except /etc/kubernetes/kubelet.conf, which seems consistent with https://kubernetes.io/docs/tasks/administer-cluster/kubeadm/kubeadm-certs/
So I changed /etc/kubernetes/kubelet.conf:
KUBECONFIG=/etc/kubernetes/kubelet.conf kubectl config set-cluster kubernetes --certificate-authority=/etc/kubernetes/pki/ca.crt
KUBECONFIG=/etc/kubernetes/kubelet.conf kubectl config set-credentials system:node:$HOSTNAME \
  --client-certificate=/var/lib/kubelet/pki/kubelet-client-current.pem \
  --client-key=/var/lib/kubelet/pki/kubelet-client-current.pem

So, this issue can be closed. Thanks.

/close


POST method not allowed

I get "405 Method Not Allowed" only for POST methods

I'm facing with same kind of issue. when we checked with api:routes it shows POST request. but when i tested using postman it give 405 error.

Same here

I found the solution for this problem. The problem was post request rejected by the middleware. when the request is coming from api then we can ignore csrf token.using this way i fixed the issue.

How do you do that? I have the same issue...


Plan posts

The program is able to post. Is it possible to increase functionality, plan posts, like in "planoly" or in "buffer". So that you can plan your posts and sort not yet published.

What do you mean by that?

@bil-elmoussaoui I think he's talking about scheduling posts' date and time.
@vladcraft No, this is not possible since this is a web wrapper and we're not using any private API integration to post.


Remove AbstractSwaggerUIAPI class

This PR removes the AbstractSwaggerUIAPI class, which was a temporary base class used to support the swagger UI both in the Flask App & Middleware. Since the swagger UI has been moved completely into the middleware, we don't need it anymore.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

9 of 9 (100.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage decreased (-0.01%) to 94.726%

Totals

Change from base Build<PHONE_NUMBER>:
-0.01%

Covered Lines:
2712

Relevant Lines:
2863

💛  - Coveralls


production option for the build command not working?

Do you want to request a feature or report a bug?
Bug
What is the current behavior?
The --production option to the build command doesn't seem to work. It creates a minified build even if I pass false as a value for it.
If the current behavior is a bug, please provide the steps to reproduce.

Create a new project with empty template - preact create my-app --type empty
Build the application with production option turned off - preact build --production false

What is the expected behavior?
It should create non-minified files in the build folder.
If this is a feature request, what is motivation or use case for changing the behavior?
Please mention other relevant information.

node version - v8.4.0
npm version - v5.4.0
Operating system - macOS Sierra 10.12.6
Preact-cli version - v1.4.1

You would have to do --no-production because yargs isn't smart enough to infer boolean types.


Stop playing automatically in the background

hello, I play audio in background ,but play next music about 2-3 songs, it stop automatically, however,when the screen on, it played.A very strange strange phenomenon.My English is pool,I'm not sure if you understand what I mean，Could you please help me fix this issue.Thanks

Closing in lieu of https://github.com/luanpotter/audioplayers/issues/788


more safe and easily readable use to get raw pointer of shared-pointer

Signed-off-by: Yonghye Kwon<EMAIL_ADDRESS>Description
before
  auto g = std::make_shared<torch::jit::Graph>();
  torch::jit::parseIR(graph, &*g);

after
  auto g = std::make_shared<torch::jit::Graph>();
  torch::jit::parseIR(graph, g.get());

Refer to this thread uploaded on Stack Overflow.
Type of change

Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

[x] My code follows the style guidelines of this project (You can use the linters)
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas and hacks
[x] I have made corresponding changes to the documentation
[x] I have added tests to verify my fix or my feature
[x] New and existing unit tests pass locally with my changes

@narendasan Is there any reason using '&*' instead  of '.get())?

The structure of tests has its roots in how PyTorch does JIT tests, likely they did the same thing and we copied it. Places like this https://github.com/pytorch/pytorch/blob/c7a70eec1b1a8aaac1f5659f688cd625c4a67831/test/cpp/tensorexpr/test_kernel.cpp#L42. Though I now see both in the PyTorch codebase. Im not highly opinionated on what way we get the raw pointer and seems reasonable if its safer

Is this really a breaking change?

@narendasan
I was not thinking straight.
I was not familiar with shared pointer. I studied this recently.
It's not a breaking change.


Check or GitHub discussions rather than Slack?

This is a followup to

#129

I'm a bit surprised by the check for Slack channels because @caniszczyk and I had been discussing (maybe some time last fall) about a preference to move to, say, GitHub discussions instead. Maybe I misunderstood.
Comments?
/cc @nate-double-u

We should do both!
Some projects won't get away from Slack and we generally create folks a
slack channel in the CNCF Slack when they join
On Tue, Jun 28, 2022 at 8:53 AM Patrice Chalin @.***>
wrote:

This is a followup to

#129 https://github.com/cncf/clomonitor/issues/129

I'm a bit surprised by the check for Slack channels because @caniszczyk
https://github.com/caniszczyk and I had been discussing (maybe some
time last fall) about a preference to move to, say, GitHub discussions
instead. Maybe I misunderstood.
Comments?
/cc @nate-double-u https://github.com/nate-double-u
—
Reply to this email directly, view it on GitHub
https://github.com/cncf/clomonitor/issues/418, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAPSINQNQZFJBNQXGXHN23VRL7WXANCNFSM52CIQSBQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

--
Cheers,
Chris Aniszczyk
https://aniszczyk.org

We should do both!

Sounds good. @tegioz - can we generalize the check?

In terms of how checking for slack or GitHub discussions would affect the project's score, I think a fail would be having neither, and a pass would be having either


LINK type constraints on lightweight edges

Is it possible to create LINK type constraints on a lightweight edge? I am running OrientDB 2.1.11, and I set my edges to be lightweight using the command
ALTER DATABASE CUSTOM useLightWeightEdges = TRUE
The following is an example of what I would like to be able to do.
I first ran the following SQL commands
CREATE CLASS C1 EXTENDS V
CREATE CLASS C2 EXTENDS V
CREATE CLASS E1 EXTENDS E
CREATE PROPERTY E1.out LINK C1
CREATE PROPERTY E1.in LINK C1
CREATE VERTEX C1 set id="c11"
CREATE VERTEX C1 set id="c12
CREATE VERTEX C2 set id="c2
After all that, now running
CREATE EDGE E1 FROM (SELECT FROM C1 WHERE "id" = "c11") TO (SELECT FROM C2 WHERE "id" = "c2")
does not throw any exceptions, and creates the edge as requested. Is there any reason why a lightweight edge cannot enforce LINK type constraints? If I make E1 a "normal" edge then the constraint is enforced and I get thrown an OValidationException as I expected. Is creating a normal edge the only solution to my problem? Can lightweight edges also be configured to enforce such constraints?
I should mention, when I type
INFO CLASS E1
the LINK type constraint does show up on the output, which suggests to me that the constraint information for the lightweight edge is maintained by the database, even if not ultimately enforced. Thanks for any comments.

Interesting. I'd say, you've found a bug, but I am also uncertain about how constraints are supposed to work.
Referencing this issue to my suggestion too, since there are similar concerns.
https://github.com/orientechnologies/orientdb/issues/5260
Scott

lightweight edges cannot have properties set on them, because no record is ever created for the edge itself. lightweight edges work by linking the vertices directly. so in this case, you should add the constraint on the property of C1 and C2 classes.

That is also what I thought at first, but you can create a lightweight edge and create the constraints on the edge (which seem like properties). If you follow what @codelimner explains, you will see no document is created under the E1 class.
Scott

@smolinari i just tried these commands on orientdb-2.2.0beta and the database does not seem to respect the "useLightweightEdges=TRUE" setting. an edge record is in fact getting created:
orientdb {db=testdb}> select from V

----+-----+------+----+-------+-------
#   |@RID |@CLASS|id  |out_E1 |in_E1
----+-----+------+----+-------+-------
0   |#17:0|C1    |c11 |[#25:0]|null
1   |#18:0|C1    |c12 |null   |null
2   |#21:0|C2    |c2  |null   |[#25:0]
----+-----+------+----+-------+-------

3 item(s) found. Query executed in 0.006 sec(s).
orientdb {db=testdb}> select from E

----+-----+------+-----+-----
#   |@RID |@CLASS|out  |in
----+-----+------+-----+-----
0   |#25:0|E1    |#17:0|#21:0
----+-----+------+-----+-----

1 item(s) found. Query executed in 0.006 sec(s).
orientdb {db=testdb}>

i tried in OrientDB 2.1.7 and it works differently - no record is created for the edge.
in both versions, "info" command does not display the "useLightweightEdges" setting.

That is interesting. And in 2.2 it seems you not only have an edge document, but the edge is created, despite the constraint, which is different behavior than with 2.1.X, which throws an error on standard edges. So, being it is called a constraint, I'd say that is another bug.
Scott

actually my comment on "info" command in the previous comment was not completely correct. if i create a database through the console, and then set the "useLightweightEdges=TRUE", the info command does not display the setting. however if i disconnect from the console and relogin, the info command displays the setting correctly.

Thanks @smolinari and @nagarajasr for the comments and additional information.
I did some investigation on this looking into the source code for version 2.1.14 during the past couple of days. Essentially, all schema constraints (including LINK type) are completely ignored when the lightweightedges option for the db is set to "true". This is what @nagarajasr was implying I suppose, and you can observe this in the code by looking at the implementation of getType() method of the OrientEdge class.
But you can't also set these constraints on the two endpoint vertex classes. I feel this is reasonable as it is an edge type constraint, and it would not make sense to set constraints on the vertex end points without the edge being involved in any way.
So if my understanding is correct, this is more of a "not implemented now" thing (if it will ever be) rather than a bug. Part of the problem with implementing this seems to be that the constraint validation checks are done at a document level, and of course lightweight edges have no document by themselves. Validating a lightweight edge is really validating a property of another document (link property of either the out or in vertex), and may need a special case handling.

@codelimner - cool that you are digging into the ODB code.
From what I understand, the lightweight edge is always only found within the vertex data (out, in), plus some meta data about the edge class itself. There is no class with document storage created with lightweight edges. So, the constraints do have to be added to something, which is to me, must be meta data within the edge class. Was there anything in the code about this?
According to the docs, the constraints are very much possible, and to me, they should work the same, no matter what kind of edge is being used. Maybe @luigidellaquila can shed some more light on this.
Scott

Hi guys,
This seems to be a missing control in the validation. As you pointed out, the root cause for this is that schema checks are performed at document level, and in this case the edge is not a document.
I'll check if we can enforce basic schema validations on edge type at least, but I'm afraid more complex constraint checks (eg. unique edge between two vertices) will be harder to manage.
In the meantime I'm flagging this as an enhancement, I'll give you a feedback as soon as I can
Thanks
Luigi

Thanks Luigi,
I believe we are only looking for the constraint between two vertex classes being upheld properly. In other words (using this section of the docs for an example).
http://orientdb.com/docs/2.1/Tutorial-Using-schema-with-graphs.html#using-in-and-out-constraints-on-edges
The control should not only be the direction of the edge (a car can't own a person), but the fact that an "owns" edge can only be used between the "person" and "car" classes. If I would want to have multiple "owns" edges to other classes, then I wouldn't add the "owns.in" property.
I hope that makes sense.
Scott


Is this project dead?

There hasn’t been any updates nor can the betas be accessed

You can pick it up if you want to. 😀
I think by now there are a lot of very nice Mastodon clients out there so I don't have the motivation to build another one.

That’s understandable but just because there are a lot doesn’t mean yours would be any less. I wish I got to experience it and your vision. What are you working on currently?


feat: support paraterName for class constructor

Same logic with CallExpression node

any update on this?

I'm very sorry for the late response, I've been really busy. I'll work on this more frequently now again.


This extension delays CSS

Example websites:

https://demo.sylius.com/admin/login
http://troskovi.com/
https://www.chess.com/

Screencast from 17-08-18 14:35:38.zip

Same as #30.


PHP7: Resource as classname is forbidden

ZF\Rest\Resource generates a soft warning (for now) referring to the classname. "Resource" is listed as restricted on php.net.
This is the list of reservered php7 keywords: http://php.net/manual/en/reserved.other-reserved-words.php
Is there a plan to rename this class in the foreseeable future?

This repository has been closed and moved to laminas-api-tools/api-tools-rest; a new issue has been opened at https://github.com/laminas-api-tools/api-tools-rest/issues/2.


Insert signed committee letter with color watermark into thesis.

Added to project, replaced blank approval page.


Typegen: The method names in OperationMethods are not escaped properly

Typegen output code breaks if an operationid contains a special character like .

Can be fixed by by making operationMethod be
var operationMethod =
        methodName.replace(/[\.,-\/#!$%\^&\*;:{}=\-_`~()\+\s]/g,'_') +
        '(\n' +
        operationArgs
            .map(function (arg) {
                return indent_string_1.default(arg, 2);
            })
            .join(',\n') +
        '  \n): ' +
        returnType;```

inside generateMethodForOperation

I would make a PR for it but it seems the repo went into oblivion

We should come up with a common way to sanitize operationIds. The code you suggested (replace all special characters with _) would be a major breaking change.

Fixed in 3.7.0


File Overwrite Possibility

Perhaps I am missing some logic, but it seems that by pulling the s3key directly from the event.file.name if I were to upload a file dog.jpg and then someone else were to do the same, it is a last write wins scenario. This is dangerous in all but a controlled write environment. A simple solution could be appending a random string / using a uuid or something similar.
https://github.com/binoculars/awsm-s3tokenvendor/blob/5f7875918cb9df3194e055065eb7dca3db97ac33/awsm/vendtoken/index.js#L41

I agree, but it's open to how whoever wants to implement it does it. I can create an example where it uses just UUID as the S3 key or appends a UUID. I'll keep this open as a TODO.

Sounds good, I just wanted to make sure people don't get burned by a default.


Please update Cocoapods with this version

As of this writing Cocoapods installs a version of UIDeviceComplete that lacks the iPhone XS, XS Max and XR. Please update Cocoapods with this version.

I will close this issue as it is actually a duplicate of issue #28. I am also waiting for an update from @Nirma
For updates, do take a look at issue #28. Maybe some day it will be updated?

Oh yes, meanwhile you can use pod 'UIDeviceComplete', :git => 'https://github.com/Nirma/UIDeviceComplete.git'
This should get you the latest pod version for the time being, while we wait for @Nirma.


Can't activate exposure logging after iCloud backup restore

Avoid duplicates

[X] Bug is not mentioned in the FAQ
[X] Bug is not already reported in another issue

Describe the bug
After restoring an iOS 13.6 Public Beta 2 iCloud backup to my iPhone X. I was no longer able to activate exposure logging within the app. Using the reset function of the app didn't help as well, but only reinstalling it.
Expected behaviour
I'm aware that the random IDs are not backed up, but the app should continue to work after an iCloud backup restore without the need of reinstalling it.
Steps to reproduce the issue
https://www.icloud.com/photos/#0rlNvI8yY61JImMFCrG8QvdDQ
Technical details

iOS Version: 13.6 Public Beta 2
Device: iPhone X

Internal Tracking ID: EXPOSUREAPP-1948

Hi @ferdinand
Could you please describe it more, like the following:

Upgrade the system.
Restore the backup.
re-run the app
Cannot activate the EN
is it correct?

@haosap The reason for the restore for the restore of the backup was not an upgrade, but a downgrade from iOS 14 Developer Beta 1 to iOS 13.6 Public Beta 2. Besides that it's correct.
What I've done is:

Installed the app on its release day (pretty sure I was already on iOS 13.5 Public Beta 2 back then)
Made sure that iOS did an automatic iCloud backup yesterday
Upgraded OTA to iOS 14 Developer Beta 1
Downgraded to iOS 13.5.1 today (I didn't know there is a restorable IPSW file available for iOS 13.6 Public Beta 2. Hence the little detour.)
Upgraded OTA to iOS 14.6 Public Beta 2
Erased all contents and settings
Restored the backup done in step 2
Re-run the app
As far as I remember the app asked me again if I want to activate the EN and if I want to allow notifications, I agreed to both but iOS didn't bring up the system's permission dialogs
The app returned that the EN is not activated
Tried unsuccessfully to activate it (see video)
Used the app's reset function
Same behaviour as in steps 10 and 11
Deleted the app
Reinstalled the app
Went through the onboarding process, gave the necessary permissions when the system asked me fo it, and everything works fine

Recently, there are also reports that backup/restores may as well lead to an endless loop, see #896.

Hey, any updates here? You have a workaround? Should we delete and reinstall the app?
I have the same problem?
Kind Regards

@BongoUser The only workaround seems to be to reinstall the app. Since iOS doesn't backup the keys they're lost anyway. Thus, it's safe to do so.

Yes, unfortunately, that's currently the way to go.

Same issue here.
Migration from iPhone 7 to 11 on iOS 13.6 via iCloud backup => CWA won't work, endless loop on the welcome page

I think it would be useful if we change this title to something like "App doesn't work after Backup restore" because not only people who restore from iCloud have this problem, people who restore from iTunes, etc. have this or other restore problems.

Is there any update on that? I can confirm that this issue happens all the time doesn't matter if iCloud or iTunes Restore.
Tested with an iPhone 6S Backup to iPhone 7 and an iPhone7 to iPhone 11.
It is easy to fix for someone with technical understanding, because you just need to redownload the app, but for example elderly people don't know this. I had one case in my family where the app was not working for a week due to this issue.

Confirming another case of the endless loop issue, after migrating phones through iCloud backup, no beta versions involved. Also fixed by reinstalling the app on the new phone,

I can also provide a video on that since we experienced the bug yesterday. iPhone 11 Pro

Related PR: https://github.com/corona-warn-app/cwa-app-ios/pull/1158

@whiskey and @svengabr
Can you confirm that this Issue will be solved with the 1.4.0 release?

@Ein-Tim I have updated the attached Jira Ticket EXPOSUREAPP-1948 and asked for feedback from the developers. I will keep you updated!

This fix is in release 1.4

With the release of the iPhone 12 more and more people will run into this issue, I'm afraid. As far as I understand, the behavior of the app in 1.4 was changed, so affected users no longer end up in the endless-loop but rather the app correctly handles the issue and resets the DB so the current workaround (of having to remove and reinstall the app, which practically only a subset of affected users will spend the time on to figure this out themselves) is no longer required.
With the fix being available for around 23 days meanwhile, it doesn't seem that the severity of the issue is taken into account. From the looks of it (through the eyes of a QA manager), this issue would deserve a hotfix release by itself already with a much shorter distribution delay than the 1 month which is approaching now.
Again: In light of more and more users going to run into the problem now with the new iPhone being released, I'd like to raise the point that maybe it's worth considering another 1.3.x hotfix release, if 1.4 is not already around the corner in the next week.

@Luke1410
1.5.0 will be released tomorrow, @thomasaugsten is this Fix included in 1.5.0?

Confirmed that the 1.5.0 release fixed the endless dialog loop in my case. App works again as expected.


ADF - SAP ODP connector - parallel extraction done sequential on SAP side

Hi,
According to this documentation page, it should be possible to parallelize the extraction from SAP to Azure using the SAP ODP connector in ADF and following the steps described in the docs.
However, when executing the pipeline, I indeed see multiple copy activities on ADF side, but the total throughput combined is almost the same (actually a bit lower) compared to just running a single copy activity. This means that it won't make the extraction any faster. On SAP side, using transaction code SM50, I see that there is only a single background job running and doing a sequential read of the DB. Also good to know is that the SHIR has still a lot more space for concurrent jobs and SAP shows that only a fraction of total batch jobs are in use.
More details:
Context: ABAP_CDS
Extraction mode: Full (also happens with Delta)
Average throughput per copy activity run in parallel (4 activities total): 350 KB/s
Average througput if I just run a single copy activity: 2 MB/s
As you can understand, this low throughput means that we'd have to wait days to finish initial extractions for our larger tables and there'd be zero benefit of partitioning and running the extraction in parallel.
Is this a known issue? And is there a way to solve this?

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

ID: 9742eb69-b1b3-4618-313a-47a36a3340f1
Version Independent ID: 81fddcf7-2958-3feb-9087-a1878dd21373
Content: SAP change data capture solution (Preview) - data partitioning template - Azure Data Factory
Content Source: articles/data-factory/sap-change-data-capture-data-partitioning-template.md
Service: data-factory
Sub-service: data-movement
GitHub Login: @ukchrist
Microsoft Alias: ulrichchrist

Thanks for the feedback! We have assigned the issue to the content author to further review this and provide an update as appropriate.
@jianleishen - Could you please review the above feedback from user and share your thoughts? - Thank you

#please-close

It could be user config issue because you are getting low thruput. The doc is right. Please open a support ticket if needed.


Have issue with future versions?

Tried to install but seems to be not compatible with newer packages?
sudo npm i -g homebridge-camera-ui@latest
npm WARN deprecated<EMAIL_ADDRESS>core-js@<3 is no longer maintained and not recommended for usage due to the number of issues. Please, upgrade your dependencies to the actual version of core-js@3.
npm WARN notsup Unsupported engine for<EMAIL_ADDRESS>wanted: {"node":"^8.9.1","homebridge":"^0.4.49"} (current: {"node":"12.16.2","npm":"6.14.5"})
npm WARN notsup Not compatible with your version of node/npm<EMAIL_ADDRESS>Any help appreciated.
Thank
Mic

have the same issue

v2.2 should fix this

Yes, it installed ok.
Any idea why I get “connection refused” issue?
2020-08-18T10:39:41.510Z CameraUI Splitting the commandline.
Reading option '-rtsp_transport' ...
2020-08-18T10:39:41.513Z CameraUI  matched as AVOption 'rtsp_transport' with argument 'tcp'.
Reading option '-re' ... matched as option 're' (read input at native frame rate) with argument '1'.
Reading option '-i' ... matched as input url with argument 'rtsp://<IP_ADDRESS>/ch0_0.h264'.
Reading option '-map' ...
2020-08-18T10:39:41.513Z CameraUI  matched as option 'map' (set input stream mapping) with argument '0:0'.
Reading option '-vcodec' ... matched as option 'vcodec' (force video codec ('copy' to copy stream)) with argument 'libx264'.
Reading option '-pix_fmt' ... matched as option 'pix_fmt' (set pixel format) with argument 'yuv420p'.
Reading option '-r' ... matched as option 'r' (set frame rate (Hz value, fraction or abbreviation)) with argument '30'.
Reading option '-f' ... matched as option 'f' (force format) with argument 'rawvideo'.
Reading option '-tune' ...
2020-08-18T10:39:41.516Z CameraUI  matched as AVOption 'tune' with argument 'zerolatency'.
Reading option '-vf' ... matched as option 'vf' (set video filters) with argument 'scale=1920:1080'.
Reading option '-b:v' ...
2020-08-18T10:39:41.516Z CameraUI  matched as option 'b' (video bitrate (please use -b:v)) with argument '300k'.
Reading option '-bufsize' ...
2020-08-18T10:39:41.520Z CameraUI  matched as AVOption 'bufsize' with argument '300k'.
Reading option '-maxrate' ...
2020-08-18T10:39:41.524Z CameraUI  matched as AVOption 'maxrate' with argument '300k'.
Reading option '-payload_type' ...
2020-08-18T10:39:41.527Z CameraUI  matched as AVOption 'payload_type' with argument '99'.
Reading option '-ssrc' ...
2020-08-18T10:39:41.530Z CameraUI  matched as AVOption 'ssrc' with argument '15652741'.
Reading option '-f' ... matched as option 'f' (force format) with argument 'rtp'.
Reading option '-srtp_out_suite' ...
2020-08-18T10:39:41.532Z CameraUI  matched as AVOption 'srtp_out_suite' with argument 'AES_CM_128_HMAC_SHA1_80'.
Reading option '-srtp_out_params' ...
2020-08-18T10:39:41.534Z CameraUI  matched as AVOption 'srtp_out_params' with argument 'IB/4uBUyZJNQqv9NlzwHJiSs+qRBySLQvRfq22pG'.
Reading option 'srtp://<IP_ADDRESS>:58176?rtcpport=58176&localrtcpport=58176&pkt_size=1316' ... matched as output url.
2020-08-18T10:39:41.534Z CameraUI Reading option '-loglevel' ... matched as option 'loglevel' (set logging level) with argument 'debug'.
Finished splitting the commandline.
Parsing a group of options: global .
Applying option loglevel (set logging level) with argument debug.
Successfully parsed a group of options.
Parsing a group of options: input url rtsp://<IP_ADDRESS>/ch0_0.h264.
Applying option re (read input at native frame rate) with argument 1.
Successfully parsed a group of options.
Opening an input file: rtsp://<IP_ADDRESS>/ch0_0.h264.
2020-08-18T10:39:41.535Z CameraUI [tcp @ 0x1415410] No default whitelist set
2020-08-18T10:39:41.536Z CameraUI [tcp @ 0x1415410] Original list of addresses:
[tcp @ 0x1415410] Address <IP_ADDRESS> port 554
[tcp @ 0x1415410] Interleaved list of addresses:
[tcp @ 0x1415410] Address <IP_ADDRESS> port 554
[tcp @ 0x1415410] Starting connection attempt to <IP_ADDRESS> port 554
2020-08-18T10:39:41.613Z CameraUI [tcp @ 0x1415410] Connection attempt to <IP_ADDRESS> port 554 failed: Connection refused
2020-08-18T10:39:41.613Z CameraUI [tcp @ 0x1415410] Connection to tcp://<IP_ADDRESS>:554?timeout=0 failed: Connection refused
rtsp://<IP_ADDRESS>/ch0_0.h264: Connection refused
[8/18/2020, 11:39:41] [CameraUI] [ERROR] Y1 Camera: FFmpeg exited with code 1
Sent from my iPad

On Aug 13, 2020, at 8:06 PM, Seyd<EMAIL_ADDRESS>wrote:

v2.2 should fix this
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

As far as I can tell there is no password on this camera.  Doing a direct command line grab I get connection refused.  Verified IP address.  Any idea why it would refuse connection?
thanks in advance!
Mic
ffmpeg -i rtsp://<IP_ADDRESS>/ch0_0.h264 -t 1 -s 480x270 -f image2 -
ffmpeg version 4.2.2-d1e8be3 Copyright (c) 2000-2019 the FFmpeg developers
built with gcc 6.3.0 (Raspbian 6.3.0-18+rpi1+deb9u1) 20170516
configuration: --pkgconfigdir=/build/workspace/lib/pkgconfig --prefix=/build/workspace --pkg-config-flags=--static --extra-cflags=-I/build/workspace/include --extra-ldflags=-L/build/workspace/lib --extra-libs='-lpthread -lm' --enable-static --disable-debug --disable-shared --disable-ffplay --disable-doc --enable-openssl --enable-gpl --enable-version3 --enable-nonfree --enable-pthreads --enable-libvpx --enable-libmp3lame --enable-libopus --enable-libtheora --enable-libvorbis --enable-libx264 --enable-runtime-cpudetect --enable-libfdk-aac --enable-avfilter --enable-libopencore_amrwb --enable-libopencore_amrnb --enable-filters --enable-decoder=h264 --enable-network --enable-protocol=tcp --enable-libspeex --enable-demuxer=rtsp --enable-omx-rpi --enable-mmal --enable-indev=alsa --enable-outdev=alsa
libavutil      56. 31.100 / 56. 31.100
libavcodec     58. 54.100 / 58. 54.100
libavformat    58. 29.100 / 58. 29.100
libavdevice    58.  8.100 / 58.  8.100
libavfilter     7. 57.100 /  7. 57.100
libswscale      5.  5.100 /  5.  5.100
libswresample   3.  5.100 /  3.  5.100
libpostproc    55.  5.100 / 55.  5.100
[tcp @ 0x3af2c10] Connection to tcp://<IP_ADDRESS>:554?timeout=0 failed: Connection refused
rtsp://<IP_ADDRESS>/ch0_0.h264: Connection refused

On Aug 13, 2020, at 8:06 PM, Seyd<EMAIL_ADDRESS>wrote:
v2.2 should fix this
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub https://github.com/SeydX/homebridge-camera-ui/issues/28#issuecomment-673768547, or unsubscribe https://github.com/notifications/unsubscribe-auth/APPLUSUPO7PDYVZ5ZQFAOYDSAR5YHANCNFSM4PQ25DNQ.


[DashboardLayout] Support route patterns in navigation

Closes https://github.com/mui/mui-toolpad/issues/3974 (partially, must create new issue for PageContainer)
Adds an optional pattern property to navigation page items so that these can be marked as selected according to that pattern (using path-to-regexp), instead of the default behavior that uses their segment property.

[x] Tests
[x] Documentation (no demo as this doesn't make a lot of sense to demo, just an explanation)

https://deploy-preview-3991--mui-toolpad-docs.netlify.app/toolpad/core/react-dashboard-layout
Also simplifies the logic for the console warning in DashboardLayout for duplicate navigation items.
No changes to PageContainer or any more complex behavior for now.
We can enable the PageContainer for this type of scenario as proposed in https://github.com/mui/mui-toolpad/issues/3974 in a separate issue/PR.
Other than that I feel like it's too early to add more complexity.

In a further PR, will add further refactoring to keep track of one only selected list item and share that logic between DashboardLayout and PageContainer components.


Is the reported result based on new setting or old setting?

Timesteps and blocks used have been adjusted. So which one gives the reported result?

If I remember correctly, I updated the reported results along with the configs. So, the current configs should reproduce the results in the paper.

If I remember correctly, I updated the reported results along with the configs. So, the current configs should reproduce the results in the paper.

Thanks. Then I will try the current configs.


CSS: Better @supports syntax highlighting support

CodeMirror should syntax highlight the "property: value" inside the @supports condition as well as "and", "or" and "not" keywords.
MDN: https://developer.mozilla.org/en-US/docs/Web/CSS/@supports
Spec: http://dev.w3.org/csswg/css-conditional-3/
Grammar: http://dev.w3.org/csswg/css-conditional-3/#at-supports
Example:
@supports ( (color: red) or (color: blue) ) {
    p { color: red; }
}

The @supports syntax is supported in Chrome, Firefox, and WebKit nightlies.

And it does. Did you try with a recent version?

Hmm, I was trying on:
http://codemirror.net/mode/css/index.html
And it doesn't look syntax highlighted as I would expect. Does that not use the most up to date version of the CSS mode?

To give an example of what I mean, pasting the snippet above into the editor I see "error" colors for property values inside the @supports conditional, I'd expect it to look more like the colors normally inside a rule.
For example, this line @supports ( (color: red) or (color: blue) ) { becomes:

    @supports ( (
    color:
    red)
    or (
    color:
    blue) ) {

But a normal rule, p { color: red; }, becomes:

    p {
    color:
    red; }

The color "red" was treated as an error in @supports, but keyword in a rule.

Oh interesting. This could just an issue with color keywords and works with everything else!
states.atBlock is doing a valuesKeywords check but not a colorKeywords. Maybe this could be using wordAsValue to get value/color/variable behavior or maybe it should just be checking value/color on its own.

This got me the syntax highlighting I expected, but you may find other changes that might be necessary:
diff --git a/mode/css/css.js b/mode/css/css.js
index 1e6d2dd..63698c1 100644
--- a/mode/css/css.js
+++ b/mode/css/css.js
@@ -273,6 +273,8 @@ CodeMirror.defineMode("css", function(config, parserConfig) {
         override = "string-2";
       else if (valueKeywords.hasOwnProperty(word))
         override = "atom";
+      else if (colorKeywords.hasOwnProperty(word))
+        override = "keyword";
       else
         override = "error";
     }

Okay, I see what you mean now. I do wonder why your initial description was...

CodeMirror should syntax highlight the "property: value" inside the @supports condition as well as "and", "or" and "not" keywords.

Your patch looks good. Shall I apply it or do you want to create a PR?

 Thanks and sorry for the initial confusion.


Test re_formula and allow_new_levels in GetLogitMCMCWeights

The test can be a variant of mcmc_runs in test_mcmc.R.  The test should make sure mrpaw does expected behavior in settings where these arguments are necessary.  The tests can also function as documentation for why we need these arguments in case we forget in the distant future!

@alicecima for some reason I can't assign an issue to you!


Datacenter filter in subscriptions

We have uchiwa connected to a bunch of different datacenters. If I select a datacenter in the client list, I still see all subscriptions which does not make sense.
The same item count is also wrong because it shows all instead of the amount of clients in the datacenter.

The Uchiwa /subscriptions endpoint should support a dc parameter in order to return specific subscriptions for a particular datacenter.


Abstract logging output over JSON

Given https://github.com/sbt/sbt/issues/2798
steps

Start sbt server on terminal1 where a build is located: sbt server
Start sbt client on terminal2 from anywhere like ~/temp/: sbt client localhost:5001
On terminal2 type assembly

expectation
The log output from sbt-assembly is displayed on terminal2.
See http://eed3si9n.com/sbt-server-reboot on more details.

Duplicate of #2800?


Tool interface

resolves #1
Adds processing of tool command line arguments, configuration files, and ability to write output to files.

Nice work.
Could you add this license to the top of all files?
/*
 * SPDX-License-Identifier: Apache-2.0
 *
 * The OpenSearch Contributors require contributions made to
 * this file be licensed under the Apache-2.0 license or a
 * compatible open source license.
 *
 * Modifications Copyright OpenSearch Contributors. See
 * GitHub history for details.
 */

License has been added to files.

I've added the requirements.txt with pip-compile here.


Updated script to change app name and package

@mariobehling With this PR, the apk generator has the ability to change the app name and package name.

Closes #402

Good job! Thank you.


[Add display name-Add authentication][Update TOC.yml][2607868]

Added display name

Acrolinx Scorecards
We currently enforce a minimum score of 80.
Click the scorecard links for each article to review the Acrolinx feedback on grammar, spelling, punctuation, writing style, and terminology:

Article
Score
Issues
Scorecard
Processed

msteams-platform/TOC.yml
98
6
link
:white_check_mark:

More info about Acrolinx
Use the Acrolinx extension, or sidebar, in Visual Studio Code to check spelling, grammar, style, tone, clarity, and key terminology when you're creating or updating content. For more information, see Use the Visual Studio Code extension to run Acrolinx locally.

Docs Build status updates of commit 40ef15a:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

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

Docs Build status updates of commit 3a0710c:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

msteams-platform/TOC.yml
:white_check_mark:Succeeded
View

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


[Accessibility] Revert recent change in Chat keybinding: ctrl+DownArrow should go back to Chat input

Type: Bug
I think there was a miscommunication between @meganrogge and I when referring to a better way to focus in the chat area. I will elaborate this when we meet again.
The current critical issue that introduced by the miscommunication is that ctrl+DownArrow does not work as expected in Chat. It used to work to go back to the input area from Chat response list. After last Friday's change made by @TylerLeonhardt, users now have to use the same shortcut key (ctrl+UpArrow) for two different purposes: going to Chat response list and going back to the input area. This is confusing. We need to revert this because ctrl+UpArrow is used to move focus from Chat input to the Chat response list, and ctrl+DownArrow is used for the return trip. ctrl+UpArrow and ctrl+DownARrow round-trip key concept is already established concept in other areas, such as terminal input and its accessible view, find input and result. This is an inadvertent regression that needs to be fixed to not confuse other users.
 It sounds like we broke your (and maybe others') muscle memory with this change, so will revert.

@TylerLeonhardt, WDYT about just reverting this as it seems we've changed the paradigm from a screen reader user's perspective?


refactor: Sort imports with eslint

I personally find imports sorted in a consistent order easier to approach, just like how prettier formats code in a consistent way. The rules here are totally flexible but would mean all packages follow the same structure.

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (ddf6986) 92.29% compared to head (1295dd8) 92.29%.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #5634   +/-   ##
=======================================
  Coverage   92.29%   92.29%
=======================================
  Files         112      112
  Lines        4283     4283
  Branches     1117     1117
=======================================
  Hits         3953     3953
  Misses        309      309
  Partials       21       21

Impacted Files
Coverage Δ

packages/eslint-plugin-query/src/configs/index.ts
100.00% <ø> (ø)

.../src/rules/exhaustive-deps/exhaustive-deps.rule.ts
100.00% <ø> (ø)

...src/rules/exhaustive-deps/exhaustive-deps.utils.ts
100.00% <ø> (ø)

...-query-object-syntax/prefer-query-object-syntax.ts
96.19% <ø> (ø)

...kages/eslint-plugin-query/src/utils/create-rule.ts
100.00% <ø> (ø)

packages/query-core/src/mutation.ts
94.17% <ø> (ø)

packages/query-core/src/queryCache.ts
100.00% <ø> (ø)

packages/query-core/src/tests/utils.ts
88.57% <ø> (ø)

...s/query-persist-client-core/src/__tests__/utils.ts
89.47% <ø> (ø)

packages/query-sync-storage-persister/src/index.ts
85.00% <ø> (ø)

... and 59 more

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

I agree, but it's gonna cause so many conflicts when merging back to alpha 😭
Maybe we should this once v5 is released and we have only one branch to maintain?

I agree, but it's gonna cause so many conflicts when merging back to alpha 😭
Maybe we should this once v5 is released and we have only one branch to maintain?

@TkDodo I was just going to merge main into alpha and only keep the changes to .eslintrc.cjs, then re-run eslint fix. I'm hoping this would actually mean there would be fewer conflicts between v4 and v5!

okay, let me just ship the fix for 5538 first. It has two PRs - one for main and one for alpha.


Fix verbose output

Why does uncover print two times the output when in verbose mode?
Example:
uncover v0.0.7
Before PR
[shodan] <IP_ADDRESS>:80
<IP_ADDRESS>:80
[shodan] <IP_ADDRESS>:8086
<IP_ADDRESS>:8086
[shodan] <IP_ADDRESS>:80
<IP_ADDRESS>:80
[shodan] <IP_ADDRESS>:8086
<IP_ADDRESS>:8086
[shodan] <IP_ADDRESS>:8081
<IP_ADDRESS>:8081
[shodan] <IP_ADDRESS>:80
<IP_ADDRESS>:80
[shodan] <IP_ADDRESS>:3000
<IP_ADDRESS>:3000
[shodan] <IP_ADDRESS>:3000
<IP_ADDRESS>:3000

After PR:
[shodan] <IP_ADDRESS>:80
[shodan] <IP_ADDRESS>:8086
[shodan] <IP_ADDRESS>:80
[shodan] <IP_ADDRESS>:8086
[shodan] <IP_ADDRESS>:8081
[shodan] <IP_ADDRESS>:80
[shodan] <IP_ADDRESS>:3000
[shodan] <IP_ADDRESS>:3000

Understood.
This is the least bulky code I can think of in order to preserve a good verbose output (kinda obsessed with that) and file output.
Just close the PR if it adds too much complexity


Document enabling forward host headers for NGINX 0.25.0

This PR addresses this issue https://github.com/rancher/docs/issues/1835

@superseb Does this only apply to Rancher installs or would we need this in the RKE docs as well for anyone using the nginx ingress controller?

The reason we add it here is because it applies to a setup of Rancher we describe and it doesn't work in this newer version. I dont think we used to describe all changes in components that are used when setting up a cluster (or basically any component version besides Kubernetes), and all components provide changelogs, maybe we should link those in the docs.


Demo issues and cards from GitHub and Trello

https://docs.github.com/en/rest/reference/issues
https://developer.atlassian.com/cloud/trello/rest/api-group-boards/

 Demo issues and cards from GitHub and Trello


class_attribute_names: add constants, add ignoreLocal

part of #716
add naming for constants
add option to ignore local classes
currently errors during schema generation ->caused by faulty import statement

have to consider what the default setting should be, in some other rule the "C_" is changing parameters

I suppose CO_ is the only viable alternative? Abapgit uses GC_ but that doesn't seem to make much sense

suggest easy solution is: allow everything in the default, let the users configure

thanks 👍


[FEATURE REQUEST] Story arc support for Mylar-organized library?

Hi,
First of all, great work on this nifty piece of code, it was the cog that made all my comic-enjoying system work ^.^
I use Mylar to manage and organize my comic collection, and they have recently adde the option to manage story arcs (Convergence, Identity Crisis, etc...), would it be possible to add a new categorization in the database sorting to recognize them?
That way, when accessing the comic collection from Chunky, i can dowload the whole story arc without the need to fetch individual comics.
Thanks in advance and keep being great!

I don't know enough Mylar. I took a quick look and it seems basically a download manager for comics. If downloaded comics contain tags (in ComicRack's format for example) then story arcs should be already supported, at least at database level.

Yes, the only addition needed is a "Story Arcs->" section in the interface presented when using the API. I'm talking about the database viewed from Chunky, for example.

I have the exact same setup, comics downloaded, organised and tagged by Mylar and then read through Chunky. If a Story Arcs section was exposed through the API, it really would make this the most amazing way of streaming and reading comics!

I'd be happy to add this feature, but I need some more detailed specification. Unfortunately I don't have Chunky for testing so I'm trying to guess.
The current api allows to filter per story arc with the comiclist endpoint, eg:
http://localhost:32500/comiclist?storyarc=test%

Storyarcs are also available from the entities endpoint, eg:
http://localhost:32500/entities/storyarcs/

So it seems the building blocks are already in place. Maybe is it possible that Chunky doesn't support it?

Just thought I'd toss my 2 cents in, for what it's worth. Chunky has a free version now, and, in my experience, the developer is fairly responsive. You'll need an iPad though, which might be an issue.

Yep, CS offers the APIs to do it, Chunky just doesn't support it right now. It's a super-easy addition, it just never occurred to me :-/
Should be in the next update.
PS: If there are any other requests for additions to the root menu, now's the time to ask!

Sorry if it's not the right place, but along with story arc, maybe being able to re-order the comics in a group w/o having to rename them.  Took me a long time to figure out I could rename them with a number to put them in the order I needed them in.  Love your comic reader, use it every day!


[Bug]: 调试UIE infer.py 运行到from paddlenlp.transformers import AutoTokenizer 出现段错误

软件环境
- paddlepaddle:
- paddlepaddle-gpu:              2.4.2.post116

- paddlenlp: 2.5.2

重复问题

[X] I have searched the existing issues

错误描述
调试UIE infer.py 运行到from paddlenlp.transformers import AutoTokenizer 出现段错误  evaluate,finetune都可以运行，就infer.py 导入就出错了

Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)

稳定复现步骤 & 代码
运行infer.py出现断错 然后
单步调试UIE infer.py  发现运行到from paddlenlp.transformers import AutoTokenizer 出现段错误
Traceback (most recent call last):
File "paddleprj/PaddleNLP/model_zoo/uie/deploy/python/infer.py", line 25, in
from paddlenlp.transformers import AutoTokenizer
File ".local/lib/python3.10/site-packages/paddlenlp/init.py", line 33, in
import paddle
File ".local/lib/python3.10/site-packages/paddle/init.py", line 25, in
from .framework import monkey_patch_variable
File ".local/lib/python3.10/site-packages/paddle/framework/init.py", line 17, in
from . import random  # noqa: F401
File ".local/lib/python3.10/site-packages/paddle/framework/random.py", line 16, in
import paddle.fluid as fluid
File ".local/lib/python3.10/site-packages/paddle/fluid/init.py", line 52, in
from . import io
File ".local/lib/python3.10/site-packages/paddle/fluid/io.py", line 31, in
from paddle.fluid import layers
File ".local/lib/python3.10/site-packages/paddle/fluid/layers/init.py", line 29, in
from . import math_op_patch
File ".local/lib/python3.10/site-packages/paddle/fluid/layers/math_op_patch.py", line 24, in
from paddle.fluid.dygraph.base import in_declarative_mode
File ".local/lib/python3.10/site-packages/paddle/fluid/dygraph/init.py", line 35, in
from . import checkpoint
File ".local/lib/python3.10/site-packages/paddle/fluid/dygraph/checkpoint.py", line 26, in
from paddle.fluid.dygraph.jit import _SaveLoadConfig
File ".local/lib/python3.10/site-packages/paddle/fluid/dygraph/jit.py", line 34, in
from paddle.fluid.dygraph.dygraph_to_static import logging_utils
File ".local/lib/python3.10/site-packages/paddle/fluid/dygraph/dygraph_to_static/init.py", line 29, in
from . import program_translator
File ".local/lib/python3.10/site-packages/paddle/fluid/dygraph/dygraph_to_static/program_translator.py", line 38, in
from paddle.fluid.dygraph.dygraph_to_static.partial_program import partial_program_from
File ".local/lib/python3.10/site-packages/paddle/fluid/dygraph/dygraph_to_static/partial_program.py", line 36, in
from paddle.fluid.contrib.mixed_precision.decorator import (
File ".local/lib/python3.10/site-packages/paddle/fluid/contrib/init.py", line 31, in
from . import mixed_precision
File ".local/lib/python3.10/site-packages/paddle/fluid/contrib/mixed_precision/init.py", line 17, in
from . import decorator
File ".local/lib/python3.10/site-packages/paddle/fluid/contrib/mixed_precision/decorator.py", line 22, in
from . import fp16_utils
File ".local/lib/python3.10/site-packages/paddle/fluid/contrib/mixed_precision/fp16_utils.py", line 23, in
from .fp16_lists import AutoMixedPrecisionLists
File ".local/lib/python3.10/site-packages/paddle/fluid/contrib/mixed_precision/fp16_lists.py", line 186, in
_, _, _sys_unsupported_fp16_list = core.op_supported_infos(
RuntimeError: Invalid enum data type 255.
[/paddle/paddle/phi/common/data_type.h:210]
Process finished with exit code 139 (interrupted by signal 11: SIGSEGV)
然而在终端pyhon 环境
执行from paddlenlp.transformers import AutoTokenizer
又没有错误只是警告
/python3.10/site-packages/_distutils_hack/init.py:33: UserWarning: Setuptools is replacing distutils.
warnings.warn("Setuptools is replacing distutils.")

@cqray1990 你好，请尝试下执行paddle.utils.run_check()，另外可以试下安装nightly build版本 https://www.paddlepaddle.org.cn/install/quick?docurl=/documentation/docs/zh/develop/install/pip/linux-pip.html


gRPC health check - AWS ECS

Requirement - what kind of business use case are you trying to solve?
AWS ECS installation for jaeger collector
Problem - what in Jaeger blocks you from solving the requirement?
The AWS ECS gRPC requires a health check path on port 14250, there is no gRPC health check path.
as a workaround, we can specify / and status code 0-99
As a consequence, the collector starts complaining - message logs
{"level":"info","ts":1647699502.6893282,"caller":"grpclog/component.go:71","msg":"[transport]transport: loopyWriter.run returning. connection error: desc = \"transport is closing\"","system":"grpc","grpc_log":true}
--

Proposal - what do you suggest to solve the problem or improve the existing situation?
Add a simple gRPC health check

@HaroonSaid did this latest release solve your issue?
I'm hitting the same error - Jaeger collector in AWS ECS, ALB hitting 14250 and showing healthy for the collector.
Yet:
{"level":"info","ts":1647699502.6893282,"caller":"grpclog/component.go:71","msg":"[transport]transport: loopyWriter.run returning. connection error: desc = \"transport is closing\"","system":"grpc","grpc_log":true}
--

still appearing

@christmoore - yeah still seeing the same logs  - I guess my analysis was incorrect.

Looks to originate from grpc dependency https://github.com/grpc/grpc-go#the-rpc-failed-with-error-code--unavailable-desc--transport-is-closing


⚠ ClamAV has degraded performance

In 87fe5d4, ClamAV (https://spamassassin.apache.org/) experienced degraded performance:

HTTP code: 200
Response time: 223 ms

Resolved: ClamAV performance has improved in 7947c70 after 5 minutes.


Pickling the itk module fails

Description
Pickling of the itk module fails.
Steps to Reproduce
import pickle
import itk

pickle.dumps(itk)

Expected behavior
Pickling succeeds.
Actual behavior

---------------------------------------------------------------------------
TypeError                                 Traceback (most recent call last)
<ipython-input-3-8fd95ab0c545> in <module>
----> 1 pickle.dumps(itk)

TypeError: can't pickle LazyITKModule objects

Reproducibility
Every time.
Versions
ITK 5.0.0 with some modules as 5.0.0.post1.
$ conda list itk
...
# Name                    Version                   Build  Channel
itk                       5.0.0                    py37_1    conda-forge
itk-core                  5.0.0.post1              pypi_0    pypi
itk-filtering             5.0.0.post1              pypi_0    pypi
itk-numerics              5.0.0.post1              pypi_0    pypi
itk-registration          5.0.0.post1              pypi_0    pypi
itk-segmentation          5.0.0.post1              pypi_0    pypi

Environment
Ubuntu 16.04.5 LTS (Xenial)
Python  3.7.3

xref #1051

Pickling via cloudpickle addressed in #1090 . We will not be able to pickle with the pickle module because it does not support pickling modules.


renderdoc_replay: Expose ShutdownOutput to Python API

Only one ReplayOutput is allowed for an underlying WindowingData, but the Python
API doesn't provide any means to shut down an existing one. Fix this, allowing
the user to create and destroy as many ReplayOutputs per window as they wish.

Description
Hopefully should be obvious, but I'm doing some fairly ugly Python API shenanigans, it's possible I missed a better way to do this.

... nevermind, I do not know how I missed IReplayOutput::Shutdown()


Buttons and List Buttons

Buttons and List Buttons not working :(

@saintclair this is unfortunately a restriction from WhatsApp itself – it has been 2 weeks already.
Only businesses can use this feature for the time being.


Does not build on Windows 10, lots of error

Hello can you please update the nugets and references and check in with more detail step.
For a benchmark & ;earning microsoft application, this has a lot of errors!

Hi I tried again, the build failed for me because of the (I think) Nuget version inconsistencies. When I update one the rest need to be updated and it does not build
Is there some steps to follow that specific to this, please let me know.
Thanks for your help.

Please, see #73


Adding/Replacing existing kcContext mock data

I tried to add required actions to the info.ftl mock but it throws an error when I try to get the mocked context as shown in the image below. Have I made a mistake or does the feature not work exactly as intended?
The field is supposed to be undefined and according to the code in deepassign it should just use the new provided property.
 "mockData": [
    {
      "pageId": "info.ftl",
      requiredActions : [
        "CONFIGURE_TOTP",
        "UPDATE_PASSWORD",
        "UPDATE_PROFILE",
        "VERIFY_EMAIL",
        "terms_and_conditions"
      ]
    }
]

Hi,
At first sight it looks like an error on my end.
I will look into it.

Confirmed error on my side... fixing

Should be fixed 2.0.9, let me know if you have any issues

Works perfectly! Thanks for the help 😄


Cannot parse hex values

The following:
sscanf "%x" "1234abc"
will give:
Unhandled Exception
format failure "1234abc"
at Microsoft.FSharp.Core.PrintfModule.PrintFormatToStringThenFail@1637.Invoke(String message) in F:\workspace.1_work\1\s\src\fsharp\FSharp.Core\printf.fs:line 1637
at FSharp.Scanf.value$cont@318[t](FSharpList1 matches, FSharpList1 formatters, Unit unitVar)
at FSharp.Scanf.ksscanf[a,b,c,d,t,u](PrintfFormat5 pf, FSharpFunc2 cont, String s)
at <StartupCode$FSI_0027>.$FSI_0027.main@()
it looks like %x gets mapped at as an int32 but there is no conversion happening.

This part seems to be broken: https://github.com/cannorin/FSharp.CommandLine/blob/master/src/FSharp.Scanf/scanf.fs#L49-L50. It should also check Char.IsDigit. I will try this tomorrow (I'm a bit busy right now), but if you have time you can freely send a PR.


add string utils

#639

Pull Request Test Coverage Report for Build 2097
Details

58 of 62 (93.55%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 91.404%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

string/string.mbt
58
62
93.55%

Totals

Change from base Build 2095:
0.01%

Covered Lines:
3626

Relevant Lines:
3967

💛  - Coveralls

Pull Request Test Coverage Report for Build 2102
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

55 of 59 (93.22%)  changed or added relevant lines in 1 file are covered.
1 unchanged line in 1 file lost coverage.
Overall coverage decreased (-0.02%) to 91.372%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

string/string.mbt
55
59
93.22%

Files with Coverage Reduction
New Missed Lines
%

builtin/buffer.mbt
1
72.22%

Totals

Change from base Build 2095:
-0.02%

Covered Lines:
3622

Relevant Lines:
3964

💛  - Coveralls

Pull Request Test Coverage Report for Build 2103
Details

55 of 59 (93.22%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.008%) to 91.372%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

string/string.mbt
55
59
93.22%

Totals

Change from base Build 2101:
0.008%

Covered Lines:
3622

Relevant Lines:
3964

💛  - Coveralls

I think it's better to use KMP search for index_of
I've implemented it myself and could you help verify it?
fn compute_prefix(pattern : String) -> Array[Int] {
  let m = pattern.length()
  let prefix = Array::make(m, 0)
  let mut k = 0
  for q = 1; q < m; q = q + 1 {
    while k > 0 && pattern[k] != pattern[q] {
      k = prefix[k - 1]
    }
    if pattern[k] == pattern[q] {
      k = k + 1
    }
    prefix[q] = k
  }
  return prefix
}

fn kmp_search(text : String, pattern : String) -> Int {
  let n = text.length()
  let m = pattern.length()
  if m == 0 {
    return 0
  } else if m > n {
    return -1
  }
  let prefix = compute_prefix(pattern)
  let mut q = 0
  for i = 0; i < n; i = i + 1 {
    while q > 0 && pattern[q] != text[i] {
      q = prefix[q - 1]
    }
    if pattern[q] == text[i] {
      q = q + 1
    }
    if q == m {
      return i - m + 1
    }
  }
  return -1
}

Thanks!

I have implemented a basic brute force matching algorithm, which should be fast when the length of strings and substrings does not exceed a threshold. When the string is longer, it can be switched to KMP or Rabin-Karp algorithm.
You can do an optimize in another PR.
FYR, Go's string index search:
https://github.com/golang/go/blob/master/src/internal/stringslite/strings.go#L24
@qazxcdswe123

Pull Request Test Coverage Report for Build 2127
Details

55 of 59 (93.22%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.008%) to 91.352%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

string/string.mbt
55
59
93.22%

Totals

Change from base Build 2126:
0.008%

Covered Lines:
3634

Relevant Lines:
3978

💛  - Coveralls

@qazxcdswe123 kmp could be provided via a new API

Pull Request Test Coverage Report for Build 2130
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

55 of 59 (93.22%)  changed or added relevant lines in 1 file are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.05%) to 91.295%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

string/string.mbt
55
59
93.22%

Files with Coverage Reduction
New Missed Lines
%

array/fixedarray.mbt
1
98.96%

builtin/array.mbt
3
98.19%

Totals

Change from base Build 2126:
-0.05%

Covered Lines:
3639

Relevant Lines:
3986

💛  - Coveralls

Pull Request Test Coverage Report for Build 2131
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

55 of 59 (93.22%)  changed or added relevant lines in 1 file are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.05%) to 91.295%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

string/string.mbt
55
59
93.22%

Files with Coverage Reduction
New Missed Lines
%

array/fixedarray.mbt
1
98.96%

builtin/array.mbt
3
98.19%

Totals

Change from base Build 2126:
-0.05%

Covered Lines:
3639

Relevant Lines:
3986

💛  - Coveralls

Pull Request Test Coverage Report for Build 2132
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

55 of 59 (93.22%)  changed or added relevant lines in 1 file are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage decreased (-0.05%) to 91.295%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

string/string.mbt
55
59
93.22%

Files with Coverage Reduction
New Missed Lines
%

array/fixedarray.mbt
1
98.96%

builtin/array.mbt
3
98.19%

Totals

Change from base Build 2126:
-0.05%

Covered Lines:
3639

Relevant Lines:
3986

💛  - Coveralls

Pull Request Test Coverage Report for Build 2133
Warning: This coverage report may be inaccurate.
This pull request's base commit is no longer the HEAD commit of its target branch. This means it includes changes from outside the original pull request, including, potentially, unrelated coverage changes.

For more information on this, see Tracking coverage changes with pull request builds.
To avoid this issue with future PRs, see these Recommended CI Configurations.
For a quick fix, rebase this PR at GitHub. Your next report should be accurate.

Details

71 of 74 (95.95%)  changed or added relevant lines in 1 file are covered.
4 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.008%) to 91.352%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

string/string.mbt
71
74
95.95%

Files with Coverage Reduction
New Missed Lines
%

array/fixedarray.mbt
1
98.96%

builtin/array.mbt
3
98.19%

Totals

Change from base Build 2126:
0.008%

Covered Lines:
3655

Relevant Lines:
4001

💛  - Coveralls

Pull Request Test Coverage Report for Build 2136
Details

71 of 74 (95.95%)  changed or added relevant lines in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.07%) to 91.352%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

string/string.mbt
71
74
95.95%

Totals

Change from base Build 2129:
0.07%

Covered Lines:
3655

Relevant Lines:
4001

💛  - Coveralls


Needs space between the buttons on Payment Details Page

Environment Details
Spartacus: http://dev-com-17.accdemo.b2c.ydev.hybris.com:4200/
Browser: Chrome
Steps to Reproduce
Sign in.
Have at least 2 payment cards saved in MyAccount (by going through checkout)
Go to MyAccount -> Payment Details
Actual Results
The 2 buttons "Set as default" and "Delete" are too close together.

Maybe also check for Address Book

fixed elsewhere


Add LiveOverflow

A little uncertain as to which category to put this in. It is an amalgamation of a tutorial, informational, programming, and entertainment.
The channel is geared towards finding and understanding exploits such as zero days, how they work, how they can be prevented, "info security" if you will, but also contains a lot of valuable low-level & general programming information.

This is good thank you!


Make wind at KSFO more realistic

Wind at KSFO pretty consistently comes from the northwest instead of from the southeast.

Thanks! It turns out I just got the angle wrong in the airport file.

Thank you for this repo!  I figured the angle was just flipped by 180 degrees.


Duplicated orders (after hanging).

Describe the bug
Using avellaneda_market_making strategy against kucoin paper trade. When sell order filled, the buy orders keep appending same orders as the first hang (buy) order. See screenshot below.

Steps To Reproduce
Here are the steps to reproduce the issue (see attachments in the section below):

Set up your configuration file with these parameters: avellaneda_market_making using kucoin paper trade, enable hanging order, filled order delay(120) > order refresh time (60)
Wait for sell orders filled.

Screenshots

Release version
1.4.0

Update: After the 1st hanging order is canceled (is it a bug?), it looks normal again.

Now restarting the bot to reproduce...

Reproduced. Sell side this time.

Multiple hangs

The duplicated non hanging orders should expire already..

Upon checking the reason of that issue that level_distances is set to 0.
Another value of level distance and orders will be different.
For expired orders it's not cancelled due to order refresh tolerance.
Here's the results for level_distances 100 and order_refresh_tolerance -1


Fix Typescript Date encoding to be 64-bit integer

Describe the bug
Right now Typescript is using an f64 which is causing a date value to get slightly changed when it is encoded through TS.

@lynn is this still true? also with 3.0 around the corner does it make sense of us to further optimize the date data to remove the locale bit C# was originally appending?


[Breaking] Support Feature Values

This creates a class called  that allows you
to have more than just  as a feature. This opens up the possibility
for strings and other types in the future. The UI just needs
to evolve to support those types.

Nice! Created a v2 branch and merging this into that for UI support to be added.


Bump kube-vip to v0.4.4

Bumping kube-vip to latest.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/approve


Share > Send Credential not working after PR 293

Updating the vc file serialization in PR #293 now results in an error. To replicate:
Check out main at tag v1.17.2-build51, build, go into credential view, 3-button menu, Share, press Send Credential button.
(Note - you can also experience this in TestFlight / build 51).
Console error:
2022-12-08 14:19:33.452017-0500 Learner Credential Wallet[8521:1265079] [ShareSheet] Failed to request default share mode for fileURL:file:///var/mobile/Containers/Data/Application/F3B5A5C1-EAAE-4B2F-9AD5-C831A8244E36/Documents/SharedCredential.txt error:Error Domain=NSOSStatusErrorDomain Code=-10814 "(null)" UserInfo={_LSLine=1538, _LSFunction=runEvaluator}
2022-12-08 14:19:33.456984-0500 Learner Credential Wallet[8521:1265079] [ShareSheet] Only support loading options for CKShare and SWY types.
2022-12-08 14:19:33.828348-0500 Learner Credential Wallet[8521:1265079] [ShareSheet] error fetching item for URL:file:///var/mobile/Containers/Data/Application/F3B5A5C1-EAAE-4B2F-9AD5-C831A8244E36/Documents/SharedCredential.txt : Error Domain=NSCocoaErrorDomain Code=256 "The file couldn’t be opened."
2022-12-08 14:19:34.018041-0500 Learner Credential Wallet[8521:1265079] [ShareSheet] error loading metadata for documentURL:file:///var/mobile/Containers/Data/Application/F3B5A5C1-EAAE-4B2F-9AD5-C831A8244E36/Documents/SharedCredential.txt error:Error Domain=NSFileProviderInternalErrorDomain Code=0 "No valid file provider found from URL file:///var/mobile/Containers/Data/Application/F3B5A5C1-EAAE-4B2F-9AD5-C831A8244E36/Documents/SharedCredential.txt." UserInfo={NSLocalizedDescription=No valid file provider found from URL file:///var/mobile/Containers/Data/Application/F3B5A5C1-EAAE-4B2F-9AD5-C831A8244E36/Documents/SharedCredential.txt.}
2022-12-08 14:19:34.099063-0500 Learner Credential Wallet[8521:1265322] [default] LaunchServices: store (null) or url (null) was nil: Error Domain=NSOSStatusErrorDomain Code=-54 "process may not map database" UserInfo={NSDebugDescription=process may not map database, _LSLine=66, _LSFunction=_LSServer_GetServerStoreForConnectionWithCompletionHandler}
2022-12-08 14:19:34.100026-0500 Learner Credential Wallet[8521:1265322] [default] Attempt to map database failed: permission was denied. This attempt will not be retried.
2022-12-08 14:19:34.100146-0500 Learner Credential Wallet[8521:1265322] [db] Failed to initialize client context with error Error Domain=NSOSStatusErrorDomain Code=-54 "process may not map database" UserInfo={NSDebugDescription=process may not map database, _LSLine=66, _LSFunction=_LSServer_GetServerStoreForConnectionWithCompletionHandler}
2022-12-08 14:19:34.220404-0500 Learner Credential Wallet[8521:1265322] [default] LaunchServices: store (null) or url (null) was nil: Error Domain=NSOSStatusErrorDomain Code=-54 "process may not map database" UserInfo={NSDebugDescription=process may not map database, _LSLine=66, _LSFunction=_LSServer_GetServerStoreForConnectionWithCompletionHandler}
2022-12-08 14:19:34.220475-0500 Learner Credential Wallet[8521:1265322] [default] Attempt to map database failed: permission was denied. This attempt will not be retried.

I will submit a PR with this code to try to reproduce the issue. If we're not able to reproduce, lets push the code out to TestFlight

Can confirm, works now after PR #343.

Also, FWIW can only share verified credentials (thus applies to Send Credential, Create Public Link, Add to LinkedIn Profile)


Zola Rewrite

The migration is complete! The only changes are the removal of comments, and the removal of the comments, the removal of the last_updated footer because zola doesn't provide a site.time variable, and the date format change. I'll see if I can get this deployed to a gh-pages site.

I got the github action going

@ibraheemdev thanks for your great work, that's a huge improvement! I'll try to find time to review it on the weekend. Meanwhile, are there any instructions to build the site locally?

You can just clone the repo and run zola serve. The zola installation guide is here

@ibaryshnikov Also, the web-presence-team said that a maintainer of the repo had to ask them for permission to add a new maintainer. Any chance you could do that for me?

Deployment will require generating a token with repo access and updating the gh-pages build branch. That will require someone with access to the repo settings, which might be an issue.

I got the github workflow going with the built in GITHUB_TOKEN and peaceiris/actions-gh-pages, and manually installing the zola binary. Should I fix the conflicts and merge this?


Error when drawing circuits generated by StandardRB

Informations

Qiskit Experiments version: 0.4.0
Python version: 3.10
Operating system: Windows

What is the current behavior?
Running this script:
import qiskit
from qiskit_experiments.library import StandardRB
import qiskit_experiments
import numpy as np
print(qiskit.version.QiskitVersion())
print(qiskit_experiments.version.get_version_info())

lengths = np.arange(1, 600, 200)
exp1 = StandardRB([0], lengths, num_samples=4, seed=1010)
circuits=exp1.circuits()
circuits[0].draw()

results in an exception
{'qiskit-terra': '0.22.2', 'qiskit-aer': '0.11.1', 'qiskit-ignis': None, 'qiskit-ibmq-provider': '0.19.2', 'qiskit': None, 'qiskit-nature': None, 'qiskit-finance': None, 'qiskit-optimization': None, 'qiskit-machine-learning': None}
0.4.0

  ...

  File "C:\develop\env310\lib\site-packages\qiskit\visualization\circuit\_utils.py", line 556, in slide_from_left
    if node.op.condition:

AttributeError: 'Clifford' object has no attribute 'condition'

Steps to reproduce the problem
See the minimal example above
What is the expected behavior?
The circuit should be plotted
Suggested solutions

This is related to #9159 as Clifford operations are not instructions.

Fixed by #8907


Change context root to use controller-runtime signal handler

Replace our signal handler with the fuller featured controller-runtime one.
/kind cleanup
/assign @irbekrm
NONE

/lgtm

/retest

/lgtm

/retest


Cache eviction on File System dirver

Great project!
I am going to leverage GCP Cloud Run container disk as a cache to decrease DB requests.
In theory, you will run out of disk space if you keep writing data back to disk without evicting the oldest one.
It would be a good idea to introduce some kind of data eviction policy like LRU?
Many thanks.

Hello!
So, to explain quickly: some drivers have a TTL driver. Typically Redis or DynamoDB. In this case: no problem, when the TTL expires, the entry is completely deleted.
Other drivers don't: filesystem or databases. In this case, it's more complicated.
I've tried a simple implementation with database drivers: just run a setInterval that will delete expired entries every X seconds/minutes/hours. See https://github.com/Julien-R44/bentocache/blob/main/packages/bentocache/src/drivers/sql.ts#L66
The implementation is rather naive but it seems to works fine for now. I was planning to use a worker Node for this, but it's still on standby
So, for the filesystem, I suppose we can start by having a fairly similar implementation. Just a setInterval. Having said that, the implementation is likely to be a little more costly than with the database. We have to scan and open all the files to check the TTLs. We will probably have to do some benchmarking to make sure it's not too performance-intensive. Or use a worker right now instead of a simple setInterval
Any thoughts ?

Was implemented with #13 and will be available in next release

Published with<EMAIL_ADDRESS>


added uuid-ossp and updated postgresql

Added UUID support via uuid-ossp and updated PostgreSQL to make it work.

Thanks for the contribution @justinkuepper ! Everything looks good to me. Binaries have been uploaded and will merge.


Move over to HTTP/2 to access V2 of the Alexa Voice Service

Follow https://developer.amazon.com/public/solutions/alexa/alexa-voice-service/docs/migration-guide

hey still need help on migrating?


The source map is unnecessary in the production

ref. #228

👍  Thanks

Thank you for merging this PR 👍


Screen resize not working in QEMU/KVM Plasma guest

Describe the bug
When running NixOS as a QEMU/KVM guest with KDE Plasma as the desktop environment, screen auto-resize does not work in virt-manager. This appears to be a Plasma-specific issue because the equivalent configuration works fine in GNOME.
Steps To Reproduce
Steps to reproduce the behavior:

Create new VM in virt-manager with default video configuration (i.e. Video -> Model -> Virtio and default Spice display options).
Install NixOS into the VM with KDE Plasma as the desktop environment.
Update configuration.nix to add spice-vdagent to environment.systemPackages.
Update configutation.nix  to include:

services.spice-vdagentd.enable = true;
services.qemuGuest.enable = true;

Rebuild config and reboot.

OBSERVE

In virt-manager, View -> Scale Display -> Auto resize VM with window is grayed out. It should not be.
Plasma desktop does not resize to fit display. It's a small box in the center of the VM wimdow.

Expected behavior

In virt-manager, View -> Scale Display -> Auto resize VM with window should not be grayed out.
When Auto resize VM with window is selected, Plasma desktop should resize to fit display.

Screenshots
N/A
Additional context
This appears to be a Plasma-specific problem. If you repeat the same steps but choose GNOME as the desktop environment instead of Plasma, screen resize works correctly.
Also tried plasmawayland session. Same problem.
Notify maintainers
N/A
Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.1.33, NixOS, 23.05 (Stoat), 23.05.997.ddf4688dc7a`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.13.3`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

This issue has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/screen-resize-not-working-in-qemu-kvm-plasma-guest/29489/3

Same issue for me, qemu-guest-agent.service and spice-vdagentd.service both seemed to be running, but clipboard sharing and auto resizing were all unavailable.

Any chance you are running the virtio video adapter? I have the same issue, although only with the virtio adapter, it appears to work fine with qxl.

For me auto-resize only starts working after I run spice-vdagent manually even thought the services are enabled and running.

services.spice-vdagentd.enable = true; only enables the spice-vdagentd service. An additional spice-vdagent (note the absence of "d" at the end) daemon must be started for resize to work. But when I tried this in KDE with the following configuration, resizing did not work:
  services.spice-vdagentd.enable = true;
  services.xserver.enable = true;
  services.xserver.displayManager.sddm.enable = true;
  services.xserver.desktopManager.plasma5.enable = true;

spice-vgagent is automatically started when https://search.nixos.org/options?channel=23.05&show=xdg.autostart.enable&from=0&size=50&sort=relevance&type=packages&query=xdg.autostart is set.

servises.qemuGuest.enable = true;
I have no video driver set explicitly in the VM
virtio as Video in virt-manager

  services.desktopManager.plasma6.enable = true;
  services.spice-vdagentd.enable = true;
  services.qemuGuest.enable = true;

This makes VM guest resize work for me, at least for Plasma 6 Wayland sessions.


Move phobos' std.compiler into core.compiler in druntime.

Moved all code from phobos to druntime.
Made all values 'enum' rather than simply 'immutable'.
Renamed version_major/minor to compilerMajor/Minor and D_major/minor to languageMajor/Minor.
Renamed vendor to compilerVendor.
Renamed name to compilerName.

Do we really need/want a compiler module at all?  If so, we should sort out some way to put compiler-specific code-level interfaces in here, like the ability to set a save path for the profiler, etc.

Sure, extending it to such things in the future does make sense. The usefulness of this module is mostly apparent when writing very low-level code that depends on compiler features. For example, GDC has GCC-style inline assembly, and so on.

But aren't those features generally indicated by compiler-defined version flags?  In fact, it seems more sensible to me for everything outside of API calls to be done as compiler-defined globals (version flags, constants, etc).  As for the API calls... I'm really not sure what the answer is.  Since each compiler tends to maintain its own runtime for sanity's sake, having a unified core.compiler seems impractical.

Don't GDC and LDC both use druntime? (Although I do think LDC provides a necessary patch, but that's all.)

Yes, but they maintain their own repositories.  This avoids forcing runtime changes on them that their compiler isn't ready for, allows them to swap out src/rt with their own code, and simplifies the workflow in general.
On Nov 1, 2011, at 2:37 PM, Alex Rønne Petersen wrote:

Don't GDC and LDC both use druntime? (Although I do think LDC provides a necessary patch, but that's all.)
--
Reply to this email directly or view it on GitHub:
https://github.com/D-Programming-Language/druntime/pull/81#issuecomment-2596379

I really cannot find any separate druntime repository for GDC nor LDC.
Looking back, in fact, GDC-specific patches are being provided to this very repository: https://github.com/D-Programming-Language/druntime/pull/54
Maybe I'm not following, though.

GDC's druntime: https://bitbucket.org/goshawk/gdc/src/d89c3b7d495a/d/druntime
I believe the process there is to merge in with each dmd release. The patches may as well go upstream as they aren't GDC specific and still get merged in.
LDC's druntime: https://github.com/ldc-developers/druntime

Ah, I had no idea. Thanks!
So, OK. Having compiler-specific things in here is probably a bad idea then. I still think the module in its current form could be useful, though.

Are there any outstanding issues preventing this from being merged? Note that it's more or less a copy/paste from Phobos, so there shouldn't be much to review.

I'm just wondering if it's needed at all.

The problem with that is it means requiring druntime to be current on all available compiler implementations or people will just fall back on using the version identifiers anyway.

The general consensus seems to be that this module wouldn't be too useful in practice, so I'm closing this. We may want to consider deprecating it from phobos too...


Remove calls to to.(device)

Given that Pytorch Lightning handles gpu training automatically via Trainer flags, the documentation indicates that in order to enable GPU training, all calls to to.device() should be cleaned from the Lightning module code.

Closing since no follow-ups


Update @nx/workspace to 19.6.0

Update Nx from 19.5.7 to 19.6.0

Auto-generated by create-pull-request

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

Project coverage is 97.63%. Comparing base (d65eb86) to head (482d494).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #155   +/-   ##
=======================================
  Coverage   97.63%   97.63%
=======================================
  Files          17       17
  Lines         211      211
  Branches       30       30
=======================================
  Hits          206      206
  Misses          5        5

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