Beautify and adapt SailfishOS:Chum OBS-repository's description

At https://build.sailfishos.org/project/meta/sailfishos:chum
please change
<project name="sailfishos:chum">
  <title>SailfishOS Community repos</title>
  <description>SailfishOS Community repos

See https://github.com/sailfishos-chum/main for documentation and issues.

Ping piggz or rinigus at #sailfishos for help</description>

to
<project name="sailfishos:chum">
  <title>SailfishOS:Chum</title>
  <description>SailfishOS:Chum community repository

A GUI-client for SailfishOS:Chum is available for easy installation at https://chumrpm.netlify.app/ and its individual RPMs are also provided at https://build.sailfishos.org/package/show/sailfishos:chum/sailfishos-chum-gui
A helper RPM, which solely provides an appropriate local repository configuration for utilising SailfishOS:Chum with command line tools as pkcon or zypper, is available at https://build.sailfishos.org/package/show/sailfishos:chum/sailfishos-chum

See https://github.com/sailfishos-chum/main for documentation, guidance, rules and the issue tracker.
You may also ping piggz or rinigus at the IRC channel #sailfishos for help.
</description>

This aligns this description and its wording with PR #44 and https://github.com/sailfishos-chum/sailfishos-chum-gui/pull/85
P.S.: I hope that my guess that #sailfishos denotes an IRC channel (and not some Telegram group etc.) is correct.

Done. Similar notation has been used for chum:testing repo as well

https://build.sailfishos.org/project/show/sailfishos:chum
https://build.sailfishos.org/project/show/sailfishos:chum:testing

Please check and close the issue if it is fixed

Thank you, we are almost there, but not fully yet:

You already had Copy&Paste'd my suggestion, when I did my final edit; sorry, I tend to have after-thoughts.

The appearance differs, when rendered by the OBS web-GUI: The central text block is too long and clumsy.
I forgot a final line break.

Hence another try, this time separately for both pages:

https://build.sailfishos.org/project/show/sailfishos:chum<project name="sailfishos:chum">
  <title>SailfishOS:Chum</title>
  <description>SailfishOS:Chum community repository

A full-featured GUI-client and a minimalistic helper RPM (which solely provides a local repository configuration) for utilising the SailfishOS:Chum repository are available for easy installation at https://chumrpm.netlify.app/

For SailfishOS:Chum's documentation, guidance, rules and issue tracker, see https://github.com/sailfishos-   chum/main

You may also ping piggz or rinigus at the IRC channel #sailfishos for help.

</description>

https://build.sailfishos.org/project/show/sailfishos:chum:testing<project name="sailfishos:chum:testing">
  <title>SailfishOS:Chum:Testing</title>
  <description>SailfishOS:Chum testing repository

This repository is used for evaluating packages before they are promoted to the main repository.
To submit a new or updated package, create it under your own account and submit it per OBS' "Submit package" action.

For SailfishOS:Chum's documentation, guidance, rules and issue tracker, see https://github.com/sailfishos-chum/main

You may also ping piggz or rinigus at the IRC channel #sailfishos for help.

</description>

HTH & hope that looks better than v1.

Updated. Had to add one more linebreak in :testing to split the paragraphs. Hopefully, its OK now :)

For the main repository:
For some reason the double line break after the subtitle has been reduced to a single one.  But the double line break after the subtitle is looking good at the testing repository, IMO.
For the testing repository:
Actually my intention was to deliberately avoid inserting a paragraph split there, just a simple line break.  Before you had both sentences directly appended to each other, hence I considered a line break to increase readability, but also to be sufficient.  IMO paragraph breaks (u.e., empty lines) are only helpful, if either a line ends with a web-link to Copy&Paste or a paragraph ends.
I also thought of inserting the preposition "staging", so this is the / my chance.

v3:

https://build.sailfishos.org/project/show/sailfishos:chum (identical to v2!)<project name="sailfishos:chum">
  <title>SailfishOS:Chum</title>
  <description>SailfishOS:Chum community repository

A full-featured GUI-client and a minimalistic helper RPM (which solely provides a local repository configuration) for utilising the SailfishOS:Chum repository are available for easy installation at https://chumrpm.netlify.app/

For SailfishOS:Chum's documentation, guidance, rules and issue tracker, see https://github.com/sailfishos-   chum/main

You may also ping piggz or rinigus at the IRC channel #sailfishos for help.

</description>

https://build.sailfishos.org/project/show/sailfishos:chum:testing (solely the word "staging" added)<project name="sailfishos:chum:testing">
  <title>SailfishOS:Chum:Testing</title>
  <description>SailfishOS:Chum testing repository

This staging repository is used for evaluating packages before they are promoted to the main repository.
To submit a new or updated package, create it under your own account and submit it per OBS' "Submit package" action.

For SailfishOS:Chum's documentation, guidance, rules and issue tracker, see https://github.com/sailfishos-chum/main

You may also ping piggz or rinigus at the IRC channel #sailfishos for help.

</description>

If you are tired of these nitpicking changes, never mind.  But they make these two texts more consistent (both with two line breaks after the subtitle) and the two sentences IMO logically form a paragraph together, so they shall not be split.

Taking into account that these texts are mostly for developers and not of interest for users, I suggest to stop fine tuning them. I think they are good enough and its better to focus on more important issues

when we talk about the readme.md i am to stupid to understand the simplified process of check-in.  and as a consequence i bother you guys on each update with submit package requests as i just found out. can you please improve that or give me a hint ?
thanks !

@PawelSpoon: yes, it is manual at this stage when we accept in sailfishos:chum. But don't worry about bothering, it is a part of the design. So, you are expected to make it ready in sailfishos:chum:testing and then make submit request
sailfishos:chum:testing -> sailfishos:chum
We try to process ASAP, but it may take few hours depending on our timezone, work engagement.

@PawelSpoon,

ok i did accept my own request and version now ended in :testing

Do you feel that is some information missing in the README.md?
I.e., do you think that a (half-) sentence denoting this should be added to README.md#how-to-use-the-sailfishoschum-repository-developers-guide?
If so, can you please make a suggestion in a new issue or a PR (because the last three messages already have been off-topic for this issue).

@rinigus,

Taking into account that these texts are mostly for developers and not of interest for users, …

I would like to agree, but multiple user-guides direct users to these pages, e.g. Announcing sailfishos:chum.

I suggest to stop fine tuning them. I think they are good enough and its better to focus on more important issues

Which in this context is to enhance the alternatives to …

browsing RPMs there to install them at the command line.
download SailfishOS:Chum repo config RPM from there to perform 1.
download the SailfishOS:Chum GUI app RPM from there.

Well, I tried to address point 3 per sailfishos-chum-web PR 4, but sailfishos-chum-web seems to be unmaintained currently.  Can you trigger a review and maybe a subsequent merging and publishing (or just do that)?
But this is still an awkward workaround, and a severe obstacle to "become the principal software distribution platform for Sailfish OS".  The real solution might be to implement sailfishos-chum-gui issue 96.

@Olf0: I have been thinking if we could push GUI into the official store. Not sure whether communication with SSU or PackageKit is allowed there. Haven't look into it yet, unfortunately.

@Olf0: I have been thinking if we could push GUI into the official store.

That would be a really easy and nice way out, but …

Not sure whether communication with SSU or PackageKit is allowed there.

I doubt that.

Haven't look into it yet, unfortunately.

Me, too.

… furthermore I do not remember that the Jolla Store does support deploying different RPMs depending on the installed SailfishOS release.  If so, this approach has massive drawbacks.
IMO the only viable way is a noarch installer RPM, this is way I pointed to sailfishos-chum-gui issue 96 for a potential long-term solution.
Until then, merging sailfishos-chum-web PR 4 would bring an enhancement ("quick win") for the current workaround.

I am not currently aware of the code that would require different versions on the same arch for different SFOS releases. As we fixed the issues encountered by you on older SFOS, it could work via Jolla Store. Just (most probably) we will hit some policy prohibiting it

I am not currently aware of the code that would require different versions on the same arch for different SFOS releases.

So the necessity to select an SFOS release at https://chumrpm.netlify.app/ is just a superfluous complication?!?
Then this webpage and its source repository also are good for nothing, because the SailfishOS:Chum GUI app could be easily deployed via OpenRepos?

As we fixed the issues encountered by you on older SFOS, it could work via Jolla Store.

O.K.; that would be really nice.  If only we both would not hesitate out of experience that …

Just (most probably) we will hit some policy prohibiting it.

So the necessity to select an SFOS release at https://chumrpm.netlify.app/ is just a superfluous complication?!?

Yes, pretty much, I believe.

Then this webpage and its source repository also are good for nothing, because the SailfishOS:Chum GUI app could be easily deployed via OpenRepos?

yes, in principle. Although, it is a bit bizarre when you have to hop through OpenRepos to end up in Chum. So, we better either make it possible to install via Store or have an easier online download.

So the necessity to select an SFOS release at https://chumrpm.netlify.app/ is just a superfluous complication?!?

Yes, pretty much, I believe.

For sure, and for both RPMs.  One is also a noarch RPM, thus both enforced choices are completely unnecessary for it.

Then this webpage and its source repository also are good for nothing, because the SailfishOS:Chum GUI app could be easily deployed via OpenRepos?

yes, in principle. Although, it is a bit bizarre when you have to hop through OpenRepos to end up in Chum.

This would be far less bizarre than either to go to an awkwardly looking web-page at an unknown hoster, to perform two manual choices there to ultimately download an RPM, which has to be manually installed or to perform the same actions fully manually at the SailfishOS:Chum OBS (which you defined as "for developers").
Especially for everybody already using Storeman, but even if one manually downloads this RPM, because OpenRepos is a well known location.

So, we better either make it possible to install via Store or have an easier online download.

Via Jolla Store or OpenRepos does not make any difference for many, likely most SailfishOS users willing to use SailfishOS:Chum.
Though I sure support to "have an easier online download", this is exactly why I created sailfishos-chum-web PR 4 and contributed to bug reports, only to see that no one seems to care.
But it always will be an awkward workaround, much more tedious, inconvenient and questionable (in terms of trustworthyness) than using Storeman (or the Jolla Store app).

Re unknown hoster: good point. Maybe we should add those RPMs into this repo releases. We could make some version that would later be just updated at OBS. That way RPMs will be coming from a repo that is associated with the project. Although, that "unknown hoster" should be actually providing links to OBS
I am not maintainer of -chum-web and I don't know how that web app gets enrolled.
As for OpenRepos, yes, maybe we should put it there as well.
Now in terms of making it happen - I'd love to spend a bit of time on other projects. Just few days or a week :)

Although, that "unknown hoster" should be actually providing links to OBS

Well, if I ever get stuff merged there, I have https://github.com/Olf0/sailfishos-chum-web/pull/1/commits/72d82a08395bc31f9bbb361b6f18b985b735d849 in store.

I am not maintainer of -chum-web and I don't know how that web app gets enrolled.

Right now I would be glad to see any reaction from @mentaljam.  Piling up more issues, changes, commits and PRs does not make sense without maintainer's feedback (even silently merging would do).

As for OpenRepos, yes, maybe we should put it there as well.

Well, I avoided to address the consistent use of "we", but here I do have to ask who "we" is?
I could, but I would be awkward to distribute somebody else's work, and I hardly can be the maintainer at OpenRepos without being involved (at least "in the loop" / notified) of maintenance work at GitHub.  You may be better suited, but ultimately @mentaljam seems to be the "natural candidate".

We would be me, @piggz, @mentaljam. I wouldn't mind you to take GUI RPMs and set them up at OpenRepos. You seem to be very well in the loop already :)

I wouldn't mind you to take GUI RPMs and set them up at OpenRepos.

Done: https://openrepos.net/content/olf/sailfishoschum-gui-client-app & https://openrepos.net/content/olf/sailfishoschum-repo-config-rpm

You seem to be very well in the loop already :)

I am merely a contributor, who tried to enhance the visual appeal and usability of the SailfishOS:Chum infrastructure (software, documentation etc.) to a point where it looses the look & feel of being "done by students in their spare time" (a phrase a colleague of mine at work coined, which fits well to many FLOSS projects, even some "big" ones); IMO this was (and still is: a couple of PRs are not merged yet) just a first step towards a more professional appearance for many infrastructure components of SailfishOS:Chum with the long-term goal in mind of "The ambition is to become the principal software distribution platform for Sailfish OS".
As mentioned before, most techies vastly underestimate the impact of appearance on non-techies: Because they have nothing else to base their judgement upon, the "look & feel" is what they evaluate, while all the things techies are proud of (quality of the source code etc.) are (rsp., "must implicitly be") meaningless to them.
As said and now also stated in the README, I did appreciate the concept of F-Droid (a repo with semi-automatic builds from contributed sources) much for long and love to see it applied to the SailfishOS ecosystem.  This is why I supported SailfishOS:Chum by roughly enhancing an aspect which did not seem to be much in your focus yet: a proper "look & feel" (appearance and usability).

This is an excellent example where we can very well contribute bits to build something bigger. I am happy that you took this part of the project and work on the design and overall appearance. It will surely translate into more users and developers working via SailfishOS:Chum :)

While Chum GUI got just released (minor version bump), we can keep older GUI binaries at OpenRepos as GUI gets updated by itself through Chum anyway. So, in this respect, we need to update OpenRepos release only occasionally.

While Chum GUI got just released (minor version bump), we can keep older GUI binaries at OpenRepos as GUI gets updated by itself through Chum anyway. So, in this respect, we need to update OpenRepos release only occasionally.

Well, now "we" is me. :wink:
More seriously: Yes, I already considered that, too.
But specifically for the last upload of the sailfishos-chum-gui RPM v0.4.0, I have to redo it any way, because I did not think enough before acting: I picked the variant compiled for SailfishOS 4.3.0, which failed to install later when testing on my<EMAIL_ADDRESS> That "C++ ABI mismatch" error was to be expected, in hindsight. :frowning_face:
Thus I plan to upload the sailfishos-chum-gui RPM v0.4.1 compiled for SFOS 3.1.0 at OpenRepos, next.  Do you expect any issues when installing this on recent SailfishOS releases?

I was mistaken - cannot use GUI for SFOS 4.0.1 (oldest version for aarch64) on 4.3. At least not as it is now. There is something preventing it from starting when using app grid. I guess related to the bug you had with the invoker :( .
Cannot test very old SFOS releases, unfortunately.

I was mistaken - cannot use GUI for SFOS 4.0.1 (oldest version for aarch64) on 4.3. At least not as it is now. There is something preventing it from starting when using app grid. I guess related to the bug you had with the invoker :( .

:frowning:
O.K., I deleted my recent uploads of the sailfishos-chum-gui RPM v0.4.1 compiled for SFOS 3.1.0 (rsp. SFOS 4.0.1 for aarch64) at OpenRepos, and uploaded the variants compiled for SFOS 4.3.0.
So currently it makes only sense to offer the sailfishos-chm-gui variants compiled for the current SFOS release at OpenRepos, but this is probably only useful for users of exactly this SFOS release.
Maybe Slava Monich's harbour-lib is helpful here for implementing a proper solution.
Until then my one-man-show at sailfishos-chum-web PR 4 would still provide a quick improvement (though only visually and WRT clarity of the text), if it is ever reviewed, maybe merged and even uploaded to chumrpm.netlify.app.

Cannot test very old SFOS releases, unfortunately.

Well, I can, did and do (at least ARMv7A@SFOS3.2.1): Variants compiled for SFOS ≥ 3.4.0 fail, as mentioned}.

Makes sense to have latest GUI version on OpenRepos. We will have to revise options for GUI installer and then look what to do about it. I can look into it, hopefully tonight after work

This deviated far enough from the original issue topic (which is basically resolved) to be closed.
The remaining issues should be discussed elsewhere, the most prominent (and last discussed here) at [SailfishOS:Chum GUI issue 96](https://github.com/sailfishos-chum/sailfishos-chum-gui/issues/96].


Integrate volsync in test environment

Add volsync addon and test environment using minikube volumesnapshots and
csi-hostpath-driver storage.
The addon includes a self test deploying a busybox application on one cluster and
replicating it to the second cluster.
With this change we can add a basic test using volsync instead of rbd mirroring.
We will add later CephFS so we can test also volsync with CephFS.
Fixes: #661

Example deploy:
$ test/basic-test/deploy dr1
2023-06-16 00:56:40,257 INFO    [deploy] Creating temporary directory /tmp/ramen-test/basic-test
2023-06-16 00:56:40,257 INFO    [deploy] Cloning ocm-ramen-samples
2023-06-16 00:56:40,257 INFO    [deploy] Creating kustomization for using cluster 'dr1'
2023-06-16 00:56:40,257 INFO    [deploy] Deploying busybox example application
2023-06-16 00:56:40,639 INFO    [deploy] waiting for namespace busybox-sample
2023-06-16 00:56:40,697 INFO    [deploy] Waiting until busybox drpc reports phase
2023-06-16 00:56:41,816 INFO    [deploy] Waiting until busybox drpc is deployed
2023-06-16 00:56:41,970 INFO    [deploy] Waiting until application is replicated
2023-06-16 00:58:40,927 INFO    [deploy] Application was deployed successfully

The app is replicated successfully with volsync and submariner.
Failover - app moves to second cluster, but get stuck in clean up.
$ test/basic-test/failover dr2
2023-06-16 01:00:39,448 INFO    [failover] Waiting until application is replicated
2023-06-16 01:00:39,501 INFO    [failover] Starting failover
2023-06-16 01:00:39,569 INFO    [failover] Waiting until application is failed over...
2023-06-16 01:01:10,224 INFO    [failover] Waiting until application is replicated
2023-06-16 01:06:10,450 ERROR   [failover] test failed
Traceback (most recent call last):
  File "/home/nsoffer/src/ramen/test/basic-test/failover", line 50, in <module>
    drenv.wait_for(
  File "/home/nsoffer/src/ramen/test/drenv/__init__.py", line 50, in wait_for
    raise RuntimeError(f"Timeout waiting for {resource}")
RuntimeError: Timeout waiting for drpc/busybox-drpc

drpc changes:
$ kubectl get drpc -A --context hub -o wide -w
NAMESPACE        NAME           AGE   PREFERREDCLUSTER   FAILOVERCLUSTER   DESIREDSTATE   CURRENTSTATE   PROGRESSION   START TIME   DURATION   PEER READY
busybox-sample   busybox-drpc   0s    dr1
busybox-sample   busybox-drpc   0s    dr1
busybox-sample   busybox-drpc   0s    dr1                                                 Deployed       UpdatingPlRule   2023-06-15T21:56:40Z              True
busybox-sample   busybox-drpc   1s    dr1                                                 Deployed       UpdatingPlRule   2023-06-15T21:56:41Z              True
busybox-sample   busybox-drpc   3s    dr1                                                 Deployed       UpdatingPlRule   2023-06-15T21:56:43Z              True
busybox-sample   busybox-drpc   5s    dr1                                                 Deployed       UpdatingPlRule   2023-06-15T21:56:45Z              True
busybox-sample   busybox-drpc   16s   dr1                                                 Deployed       UpdatingPlRule   2023-06-15T21:56:56Z              True
busybox-sample   busybox-drpc   30s   dr1                                                 Deployed       EnsuringVolSyncSetup   2023-06-15T21:56:56Z              True
busybox-sample   busybox-drpc   60s   dr1                                                 Deployed       Completed              2023-06-15T21:56:56Z   44.090243322s   True
busybox-sample   busybox-drpc   60s   dr1                                                 Deployed       EnsuringVolSyncSetup   2023-06-15T21:56:56Z   44.090243322s   True
busybox-sample   busybox-drpc   60s   dr1                                                 Deployed       Completed              2023-06-15T21:56:56Z   44.090243322s   True
busybox-sample   busybox-drpc   90s   dr1                                                 Deployed       Completed              2023-06-15T21:56:56Z   44.090243322s   True
busybox-sample   busybox-drpc   2m    dr1                                                 Deployed       Completed              2023-06-15T21:56:56Z   44.090243322s   True
busybox-sample   busybox-drpc   3m    dr1                                                 Deployed       Completed              2023-06-15T21:56:56Z   44.090243322s   True
busybox-sample   busybox-drpc   3m59s   dr1                dr2               Failover       Deployed       Completed              2023-06-15T21:56:56Z   44.090243322s   True
busybox-sample   busybox-drpc   3m59s   dr1                dr2               Failover       FailingOver    WaitingForResourceRestore   2023-06-15T22:00:39Z                   False
busybox-sample   busybox-drpc   4m      dr1                dr2               Failover       FailingOver    WaitingForResourceRestore   2023-06-15T22:00:39Z                   False
busybox-sample   busybox-drpc   4m30s   dr1                dr2               Failover       FailedOver     UpdatedPlacement            2023-06-15T22:00:39Z                   True
busybox-sample   busybox-drpc   4m30s   dr1                dr2               Failover       FailedOver     Cleaning Up                 2023-06-15T22:00:39Z                   True

Rebased on main, one commit already merged via another pr.


Silently take blob data over HTTP as base64

@christophermancini identified a key issue: JSON does not like binary data. Since JSON is our sole interface for inserting and retrieving records via HTTP, that's a bit of a problem.
This set of changes allows HTTP clients such as our PHP library to use the industry-standard base64 encoding to upload and retrieve blob data for insert, query, get, and list_keys.
Must consider branching the logic to allow 0x-prefaced strings to be sent instead of base64 to maintain consistency with the SQL command line. (This will be the only way to do SQL queries with blob as key values). Outstanding question: which format should we use for output?
And need tests, badly.

The key riak_test test for HTTP has been updated to use a blob as a primary key element (something which isn't actually tested elsewhere, I don't believe, oops) and all tests pass. See linked PR.
I'm inclined to not worry about supporting 0x-prefaced values via the HTTP interface other than requiring them for select statements. We can add that later if it seems useful, but base64 is the vital standard to support.
Removing "WIP" from this PR, it's ready for review.

+1 - lovely piece of work produced under pressure...

Great work John!

:+1:


Error when a comment is added above a piped statement

Get an error when a comment is added between any statement while using the Pipe(|>) operator.
use core {*}

main :: () {
    iter.counter()
    // Comment
    |> iter.take(4)
}

Trying to run this code in the playground produces an error

Thanks for reporting this! This is definitely an oversight and should be fixed.


Allow custom action to have transformed values

:tada: This PR is included in version 2.2.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Summary Endpoint missing total "applied" and "failed" user commands

Blocks https://github.com/Granola-Team/mina-block-explorer/issues/898

Blocked by #1587


GC stats not being collected

Cassandra 2.0.14 + 2.1.4 changed bind address of JMX from <IP_ADDRESS> (any addr) to localhost only.
cassandra-stress tries to collect GC stats via JMX, which does not work since JMX is not reachable.
Let C* bind JMX to any-address so that GC stats can be collected (again).

I thought I fixed this here: https://github.com/datastax/cstar_perf/commit/0a745f2e61d6f89f8e625942b1bc998817e57ca5
What stats specifically are missing?
Here's a recent run from you that looks like its picking it up:
http://cstar.datastax.com/graph?stats=7de68872-1c0c-11e5-9038-42010af0688f&metric=gc_mb&operation=1_write

Ah - yes. Partially :)
See http://cstar.datastax.com/tests/artifacts/e703f7cc-1c39-11e5-a699-42010af0688f/console
The first two revisions are off 2.1 commits - the last is a 2.0 commit. And the last misses the GC stats.

AFAIK stress can't pick up gc stats prior to 2.1. I'll try and confirm that though

Would it be possible to get the GC stats in the graph, too?

They are?
http://cstar.datastax.com/graph?stats=ae729c84-2656-11e5-ba8a-42010af0688f&metric=gc_count&operation=1_write&smoothing=1&show_aggregates=true&xmin=0&xmax=136.07&ymin=0&ymax=4.4

oops - strike my question (seems, i really need glasses)


Update README.md

This ReadMe text is corrected using the latest Qiskit version.

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


dotnet tools like "ef" not working.

Issue Title
When using the "dotnet ef" command or any other dotnet tool command the following error is diaplayed
(https://user-images.githubusercontent.com/57043614/80925402-e12bfd00-8da8-11ea-8031-509888f5df6a.png)
Note:
Downloaded the dotnet core package from snap.
Ubuntu 20.04

@dagood

It looks like you'll want to use this workaround due to this open issue with Snaps: https://github.com/dotnet/runtime/issues/3203#issuecomment-398841315

It looks like you'll want to use this workaround due to this open issue with our Snaps: dotnet/runtime#3203 (comment)

Sir, first of all thank you for replying. Look the thing is "dotnet" and every other thing is working just fine only when I try to tools like "ef" or "codegenerator" the above given error shows up.
Thank you.


Links from within grid Blocks do not appear in links and relations view

Describe the bug
Internal links and references within grid Blocks (Teaser,  Image, Inline Link) are not registered as relations in the links and references View of the linked page.
To Reproduce
Steps to reproduce the behavior:

create 2 pages: page-a and page-b
add a Grid Block to page-b
add a teaser block within that grid block and link page-a there
got to /page-a/links-to-item

Expected behavior
page-b should appear as an item that references page-a in the links and references panel.
Screenshots

Software (please complete the following information):

OS: any
Browser: any
Volto Version: 17.0.0-alpha.24
Plone Version: 6.0.5
Plone REST API Version: 8.39.1

Additional context
For Blocks outside the grid all works fine. I already created cypress tests for these cases here https://github.com/plone/volto/blob/27a8419529231ec855cbc11a1fe6c9ee8be4b11f/cypress/tests/core/basic/linkIntegrityView.js
For Links from within a grid I created a failing test here: https://github.com/plone/volto/blob/27a8419529231ec855cbc11a1fe6c9ee8be4b11f/cypress/tests/core/basic/linkIntegrityView.js#L397

@davisagli I assume this needs to be fixed in p.restapi, right?

@davisagli enhanced the handling of subblocks in https://github.com/plone/plone.restapi/pull/1648 which is part of plone.restapi 8.41.0. An upgrade should fix your issue.

@davisagli thank you will try that out and close the issue.

Confirmed working with latest rest api. Closing


Error when building Pt_Ios example

Dear Team,
I cannot run the example for the IOS, and this error appears to me

@MuhamedAdly @mustafaanan

pt_ios branch was in the development phase,
you can checkout to pt2 branch now


Update the Postgres documentation

User Story
As a reportstream engineer I want documentation on Postgres that is up to date.
Description/Use Case
Read through the Postgres docs and make any changes necessary to the document to get it up to date with the latest information.
Docs:

Data restore - already exists
DB Failover restore - already exists
DB Flyaway repair - already exists
How to debug database queries (already exists)
SimpleReport data dictionary (already exists)
Include content for the environment RS is running i.e local, staging, and prod

Risks/Impacts/Considerations
Dev Notes
Acceptance Criteria

[ ] Postgres doc has been read through and updated
[ ] Look for additional documentation on this topic and consolidate if it exists.
[ ] Put this document in the file structure, if already updated. Otherwise put it in docs/features

Hey team! Please add your planning poker estimate with Zenhub @arnejduranovic @jack-h-wang @JessicaWNava @JFU-NAVA-PBC @luis-pabon-tf @mkalish @thetaurean


Pull Request information

Some good advice on here, is it worth including the important parts & then referencing the rest? https://github.com/blog/1943-how-to-write-the-perfect-pull-request

I like it (apart from the overuse of emoji in the "Use emoji to clarify tone" comment). I think you are right - it can be summarised into key points then referenced.

Yes, a lot of emoji over use (I would usually put a smily face here)


Review

In this milestone of the final capstone the following partners will work together.
girma336
odaialazzeh
Tamunokuro
Falis
Below is our kanban
Kanban

Hi Team,
While you made a great effort in this project, unfortunately, I cannot proceed to review your board.
Invalid Code Review Request
You have submitted a project, that does not contain a screenshot of the current state of the Kanban Board at the time of review request which is seen as a requirement here
Your Code Review Request will be marked as invalid in your Dashboard, so please submit a new one once you are ready 🙏
Cheers and Happy coding!👏👏👏
Feel free to leave any questions or comments in the Issue thread if something is not 100% clear.
Please, do not open a new Issue for re-reviews. You should use the same Issue submitted for the first review, either valid or invalid unless it is requested otherwise.

Hi Team,
In my opinion, you are ready to move on to the next step! ⏭
Good luck! 🎉
Highlights

met basic requirements

Optional suggestions

maybe you can divide and conquer tasks better, instead of having everyone work on same tasks
Consider using labels to better filter tasks by type etc

Feel free to leave any questions or comments in the Issue thread if something is not 100% clear.
Cheers and Happy coding!👏👏👏

As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


docs: add interop docs to mdbook

Ah, @kaymomin I see that lints are failing. I guess you need to run zkstack dev fmt to fix CI.

Ah, @kaymomin I see that lints are failing. I guess you need to run zkstack dev fmt to fix CI.

on it!!


Update Email in Code of Conduct

At some point, I'd like to change The Renegade Coder email address since I'm changing my last name. With the new email address, I'll need to update the Code of Conduct.
As an additional safety measure, I'll also forward all emails from the old email address to the new one until I'm certain everything is properly updated.

Changed the email from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>


Take into account httpRoot.

The NodeRed contrib plugin doesn't take into account httpRoot. This breaks routing if you're trying to view some of the endpoints.
Steps to reproduce the behavior:

Configure httpRoot in NodeRed settings.js
Try to enter in an entity in NodeRed
You'll get a 404.

Expected behavior
Shouldn't receive a 404.

Node Red Version: Latest
NR Home Assistant Plugin Version: Latest
Is Node Red running in Docker: Yes

Other (please complete the following information):
https://github.com/AYapejian/node-red-contrib-home-assistant/issues/86

Thanks - following!

What does the httpRoot function do?
I'll try to look into this this afternoon

I don't think it's a function, it's a variable that gets stored in nodered's settings.js.
This is an issue for users that have custom routing (ex: nginx reverse proxy). The plugin doesn't handle these routes correctly.
The URLs would also need to be updated in the .html files. The httpRoot setting should be taken into account here.
Example:
If you look in server-events-state-changed.html:
Line47: $.get('/homeassistant/entities').done((entities)
Maybe the httpRoot setting needs to be concatenated to that?

This may be a bug in AYapejian/node-home-assistant.
I'll look into it further

Going off the .html stuff I mentioned in my previous comment, a good temporary workaround is to go through all of the .html files under each folder under the nodes directory and add your directory to the URL.
So I basically just did a CTRL + F on "homeassistant" and concatenated my route to the URL it's trying to get.
Restart nodered, then you'll see your entity IDs populating.
Let me know if you'd like any help or a test environment. I could probably throw one up.

Here's another workaround for those using an nginx reverse proxy like I am
https://github.com/AYapejian/node-red-contrib-home-assistant/issues/41

https://github.com/AYapejian/node-red-contrib-home-assistant/issues/76#issuecomment-408111524
This comment has more details about the issue.

@kevinduong  is there a variable (I presume httproot) that could/should be aded to the beginning of the html strings? if so could you submit a PR with an example?

I have a fix for this on my WebSocket fork feel free to cherry-pick it if you would like.
These are the two commits:
https://github.com/zachowj/node-red-contrib-home-assistant-websocket/commit/04ad3984b326ea239de26eb4ffa8a168ad5b8d02
https://github.com/zachowj/node-red-contrib-home-assistant-websocket/commit/cf2a4ad5df8772a0fb508debe946ce39bccd9141

Has this arrived in an actual release? I am currently postponing all my HA-nodered stuff until this is fixed.

I think it's fixed in this fork
https://github.com/zachowj/node-red-contrib-home-assistant-websocket
On Wed, Oct 17, 2018, 4:06 PM Simon Szustkowski<EMAIL_ADDRESS>wrote:

Has this arrived in an actual release? I am currently postponing all my
HA-nodered stuff until this is fixed.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Spartan-II-117/node-red-contrib-home-assistant-llat/issues/25#issuecomment-430789080,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACqSwM-RqpuG1vP6NqlIUok2vIN_uNnvks5ul5vQgaJpZM4Vh53p
.

I pushed the changes to NPM, so it should be fixed

I'm sorry, but it doesn't work for me. Maybe i've configured it the wrong way? Here's what i did:

Deploy HA and node-red via docker
Making sure that this module is installed in version 3.10
Configured a reverse proxy, so that node-red is reachable via node-red.mydomain.tld and HA via assistant.mydomain.tld
Both containers are in the same docker network, HA is reachable via internal hostname homeassistant_app_1
Did not configure a legacy API password in HA, created a LLAT
Configured node-red's httpRoot to "/"
Added a HA element to the flow, configured it with the server "http://homeassistant_app_1:8123" and the LLAT. API password field is empty.

Result: Error "Cannot get /homeassistant/entities", however, when i deploy the flow, the node says "Connected". The element list stays empty.


Disable client deps until  #6730 is done

Hey @silasary,
Your changes look good to me!
View build log
TravisBuddy Request Identifier: d17fac80-00fe-11ea-82f1-cf3ba55cf6d0


Fix issue with long Certificate names being used as labels

Signed-off-by: Michael Tsang<EMAIL_ADDRESS>
What this PR does / why we need it:
Currently, a label is set on Orders and Secrets with the full name of the owning Certificate.
This causes problems since a label is limited to 63 characters whereas names can be much longer.
Instead, we now do not set such a label on Orders, anything using it has been changed to use OwnerReferences instead.
For Secrets, we do not set OwnerReferences with the Certificate to avoid garbage collection - instead we continue using labels, but instead of the full name, we use the hash of the full name (up to 10 characters) to ensure that it fits on the label.
There is also a new flag SetTruncatedLabelOrderSecret to add the old label as well for any user tools which may have relied on it, but truncated to 63 characters.
Which issue this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close that issue when PR gets merged): fixes #1460
Release note:

Fix issue with Certificate names being too long to use as labels, by using the hashed name on Secrets and OwnerReferences on Orders

I have updated the description to match the new implementation, still unsure if this is the best way to do this though.

Hi @cheukwing thanks for this PR, we're hitting some problems derived from this so we'd be super interested in getting it upstream.  Is there anything we can do to help you move it forward?

Hey @srvaroa, with the review from @munnerz talking about using annotations instead I don't think this PR is ready for merging. I don't currently have time to fix this issue so please feel free to create your own PR and I will close this in favour of that :smile:

Thanks @cheukwing, we'll take a stab at it soon.

Closing in favour of #2042


chore: npm-check-updates && yarn upgrade

Ran npm-check-updates and yarn upgrade to keep the yarn.lock file up-to-date.

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject6AEA49D1-5lHf64IXfvmr
Commit ID: 4b901b00bc124aeea220a3a667e0aa609864ce70
Result: SUCCEEDED
Build Logs (available for 30 days)

Powered by github-codebuild-logs, available on the AWS Serverless Application Repository


Wheelchairs need fixing

Sprite netsync needs removing we just purged them all.
Don't Ensure on comp init.
Don't RemComp in a component's startup eventbus.
WheelChairBound should be MapInit not startup.

Also the localisation needs fixing.

to add to this, layering on east and west directions needs implementation

Every time I go FTL with a wheelchair, it would turn the camera oblique.
This can resolve itself by unbuckling and rebuckling.

wheelchair really exposing the silly vehicle buckling parenting pulling code

There's also this weird issue of whenever I was trying to link the two machines (cloning console - Genetic scanner) while on top of a puddle of reagents, I won't be able to move my own wheelchair, nor unbuckle myself from it.
Someone has to drag to move me, and unbuckle me from the wheelchair to fix the issue.

the tilt thing happens on any vehicle


Enable fmi4cpp as subproject

here is yet another fix for enabling fmi4cpp as a cmake subproject
also fix a minor override warning

Thanks


Can I use those codes under the MIT license?

I am building deno website for Japanese
I don't find any licenses for this repository (except deno image)
Can I use those codes under the MIT license?

There is a header on all files specifying that the code is MIT licensed so feel free to fork / copy or do whatever you want with it. The licences for all of the artwork can be found at https://deno.land/artwork.
@ry We seem to be missing a LICENCE file in this repo.

@tokiedokie This code is MIT, you may use it for a Japanese language website.  I will add a LICENSE file to the project.

@lucacasonato @ry Thank you


Update LayoutExample.js

Added UIManager.setLayoutAnimationEnabledExperimental(true) if the user is on Android.
Motivation
Just for the sake of clarity: the code I've added is already written atop this official doc page. However, it wasn't reported in the example code. Now it is.

Thanks! Although there is a PR for removing the need to call this, so it won't be needed in the docs anymore.

Lol, ok


[cleanup][misc] Add annotation

Motivation
Some implementation classes are missing annotations.
Modifications
Add @Override annotation.
Verifying this change

[x] Make sure that the change passes the CI checks.

This change is a trivial rework / code cleanup without any test coverage.
Does this pull request potentially affect one of the following parts:
If the box was checked, please highlight the changes

[ ] Dependencies (add or upgrade a dependency)
[ ] The public API
[ ] The schema
[ ] The default values of configurations
[ ] The threading model
[ ] The binary protocol
[ ] The REST endpoints
[ ] The admin CLI options
[ ] Anything that affects deployment

Documentation

[ ] doc
[ ] doc-required
[x] doc-not-needed
[ ] doc-complete

Looks reasonable. Triggering tests.

Codecov Report

Merging #18397 (a8b1249) into master (27186a1) will decrease coverage by 0.40%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master   #18397      +/-   ##
============================================
- Coverage     45.61%   45.21%   -0.41%
+ Complexity    10728     8579    -2149
============================================
  Files           752      587     -165
  Lines         72521    56147   -16374
  Branches       7791     5842    -1949
============================================
- Hits          33083    25386    -7697
+ Misses        35769    27925    -7844
+ Partials       3669     2836     -833

Flag
Coverage Δ

unittests
45.21% <ø> (-0.41%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

...va/org/apache/pulsar/broker/service/ServerCnx.java
43.66% <ø> (-6.06%)
:arrow_down:

.../java/org/apache/pulsar/client/impl/ClientCnx.java
30.16% <ø> (ø)

...g/apache/pulsar/client/impl/RawBatchConverter.java
3.12% <0.00%> (-89.07%)
:arrow_down:

.../pulsar/broker/service/SharedConsumerAssignor.java
3.70% <0.00%> (-74.08%)
:arrow_down:

.../transaction/buffer/metadata/AbortTxnMetadata.java
28.57% <0.00%> (-57.15%)
:arrow_down:

...lsar/broker/service/StickyKeyConsumerSelector.java
50.00% <0.00%> (-50.00%)
:arrow_down:

...apache/pulsar/broker/service/TopicListService.java
10.65% <0.00%> (-44.27%)
:arrow_down:

...ion/buffer/metadata/TransactionBufferSnapshot.java
42.85% <0.00%> (-42.86%)
:arrow_down:

...apache/pulsar/broker/service/EntryAndMetadata.java
0.00% <0.00%> (-40.75%)
:arrow_down:

...e/HashRangeExclusiveStickyKeyConsumerSelector.java
0.00% <0.00%> (-36.93%)
:arrow_down:

... and 233 more


Permutation_test fails stochastically

I had cirq/contrib/acquaintance/permutation_test/test_linear_permutation_gate_equality fail. When rerunning the test, it suddenly passed.  Maybe some RNG problem in the parametrization? Below is the raised error message:
AssertionError: cirq.contrib.acquaintance.LinearPermutationGate({2: 2, 3: 3}, cirq.SWAP) and cirq.contrib.acquaintance.LinearPermutationGate({1: 1, 2: 2, 3: 3, 5: 5, 6: 6, 7: 7, 9: 9}, cirq.SWAP) can't be in different equality groups. They're equal.

This has been fixed in #1331

Not the same test though?

Oh oops.  Reopened!

#1338


support R, G, B

	for (int r = 0; r < fpip->h; r++)
	{
		for (int c = 0; c < fpip->w; c++)
		{
			PIXEL_YC* px = fpip->ycp_edit + r* fpip->max_w + c;
			try
			{
				short new_y = static_cast<short>(ST->lookup(px->y));
				px->y = new_y;
			}
			catch (std::exception e)
			{
				continue;
			}
		}
	}

this code support Y only.

implemented in v0.0.2
Very slow however...


Refactor Project Structure to be RetroQuest

Feature Request
This feature is to realign the project structor to the branding of RetroQuest.  The packages should be renamed from FordFacto to RetroQuest.

After talking with Chris, he mentioned that we should name the package either com.ford.retroquest or com.fordlabs.retroquest. Are there any opinions on this matter?

Lee Alpha gave us a good suggestion of naming the package scheme to com.ford.labs.retroquest so we did.

LGTM


Rate limit and throttle: Last item throttled

Thanks for this code!
const lim = RateLimit(2, {
  timeUnit: (5000),
});

await Promise.all(
  images.map(async (image, index) => {

    await lim();

    const parsed = await _prepImage.call(this, image);

    await util.downloadImage(parsed.url, parsed.target);

  })
);

From what I can tell, the above code downloads two images at a time and pauses 5 seconds between concurrent downloads.
I am noticing though, the last image download waits when I would like it to exit as soon as it's resolved.
In other words, since there are no more images to download (as it it the last promise to resolve) I don't want it to wait.
Questions:

Considering the above code snippet, am I using  RateLimit properly (or, is this a good use case for RateLimit)?
How can I exit out of the last promise to resolve without pausing?

Many thanks in advance for the help and for sharing this code!

I believe that's correct behavior, at least it's something that we wanted for the applications where we use the rate limiter, that are usually very long running tasks.
For downloading/uploading files I would recommend to use the semaphore primitive directly because what you usually want to do is to download/upload n files concurrently all the time, without pauses or gaps.
const s = new Sema(2);
await Promise.all(
  images.map(async (image, index) => {
    await s.acquire();
    const parsed = await _prepImage.call(this, image);
    await util.downloadImage(parsed.url, parsed.target);
    s.release();
  })
);

or more correctly if you want to keep s global and never leak the tokens, then you should use
try {
  await s.acquire();
  ...
} catch (err)
  ...
} finally {
  s.release();
}

Awesome! Thank you so much @OlliV, that should do the trick for me.
I really appreciate your help!


Update ns-schannel-sch_credentials.md

changed a typo in SCH_CRED_DISABLE_RECONNECTS

@jess-krynitsky : Thanks for your contribution! The author(s) have been notified to review your proposed change.


LOOP-1313 Add phone details to dosing decision

https://tidepool.atlassian.net/browse/LOOP-1313
Add device settings to stored dosing decision

Looking for one reviewer.

LoopWorkspace PR confirming build: https://github.com/tidepool-org/LoopWorkspace/pull/105


Drawer seems missing in the last release dist file

Describe the bug
After updating to 1.5.0, I was not able to use the new Drawer component.
While it is present in node_modules/flowbite/src/components/drawer.js, it does not seems to be included in node_modules/flowbite/dist/flowbite.js.
Desktop (please complete the following information):

OS: Linux Manjaro
Browser N/A
Version 1.5.0

Additional context
I use pnpm as package installer, not sure if the same issue appear with npm our yarn

Hey @alorence,
Thanks for letting me know.
Big "whoopsie" from my part :)
You can get the Drawer JS starting from v1.5.1.
If something seems off, please let me know!


mime: ParseMediaType drops value with trailing semicolon

What version of Go are you using (go version)?

// up to go current playground version
package main

import (
	"fmt"
	"runtime"
)

func main() {
	fmt.Println(runtime.Version())
}

go1.16.4
Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (go env)?
go playground env
What did you do?

https://play.golang.org/p/kIcw1CfXcUq
package main

import (
	"fmt"
	"mime"
)

func main() {
	// example from rfc2231 (p.3)

	const (
		contentTypeSucc = `message/external-body; access-type=URL;
         URL*0="ftp://";
         URL*1="cs.utk.edu/pub/moore/bulk-mailer/bulk-mailer.tar"`
		contentTypeFail = `message/external-body; access-type=URL;
         URL*0="ftp://";
         URL*1="cs.utk.edu/pub/moore/bulk-mailer/bulk-mailer.tar";`	// <-- !!!
	)

	r1, p1, err1 := mime.ParseMediaType(contentTypeSucc)
	r2, p2, err2 := mime.ParseMediaType(contentTypeFail)

	fmt.Println(r1, p1, err1)
	fmt.Println(r2, p2, err2)
}

What did you expect to see?
message/external-body map[access-type:URL url:ftp://cs.utk.edu/pub/moore/bulk-mailer/bulk-mailer.tar] <nil>
message/external-body map[access-type:URL url:ftp://cs.utk.edu/pub/moore/bulk-mailer/bulk-mailer.tar] <nil>

What did you see instead?
message/external-body map[access-type:URL url:ftp://cs.utk.edu/pub/moore/bulk-mailer/bulk-mailer.tar] <nil>
message/external-body map[access-type:URL] <nil>

Analysis
this https://github.com/golang/go/blob/go1.16.4/src/mime/mediatype.go#L170 (https://golang.org/src/mime/mediatype.go?#L170) should be break instead of return
Question
Should I next time push fix commit instead of writing issue if I  found both a bug and a fix to it at once?

If you are sure that it is a bug, it's OK to send a patch instead of filing an issue.  See https://golang.org/doc/contribute.html.  Thanks.


Setup CI

Inspired by druid repository's GitHub actions setup.
Adds a GitHub actions pipeline that will run on every commits to main and all pull requests.
It contain two jobs:

a cargo fmt on the whole workspace,
a cargo clippy and cargo test that will also run on the entire workspace but on Ubuntu, MacOS and Windows 10 environments.

I also added a badge displaying the status of this pipeline in the README to bring credibility in the project.
Hopefully I got it right because I couldn't find a simple way to "dry run" it.

It looks like the CI badge in the README is just an image, not a full link.
Also, can you do a dry run in your own fork of the repo, on your own main branch?

You're right about the badge, I fixed it.
However with the current configuration of clippy, the job fail due to two errors. You can consult the reports here.
Let me know if this sounds OK to you. But don't merge yet, I'll have to revert some URLs.

I just pushed a fix for the clippy warning. Looks like that warning was recently added to clippy; I had to update my local toolchain to get it.

Merging your fix into my main, everything is green.
Do we need something else for now?


Adjust job configuration for MiModd suite at ORG

Likely similar to this, which was addressed but maybe not at all clusters? https://github.com/galaxyproject/galaxy/issues/16435
Error

mimodd: command not found

Details

history https://usegalaxy.org/u/jen-at-org/h/imported-from-archive-test-mimoddvarcall
successful job (roundup) https://usegalaxy.org/datasets/f9cad7b01a472135edf421f23730d460/details
failed job (jetstream2) https://usegalaxy.org/datasets/f9cad7b01a472135d0f1308f1fa41254/details

I've removed the special casing for conda and that should be it


Use atproto and bluesky to access to pds

See #9

atproto and bluesky (Dart)

After resolving below problem reopen.
https://github.com/tacsotai/flutter_bluesky/issues/9#issuecomment-1513945699


fix:1674

improve comment
fix https://github.com/gogf/gf/issues/1674

Codecov Report

Merging #1686 (9e34085) into master (d1f76f3) will decrease coverage by 0.05%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##           master    #1686      +/-   ##
==========================================
- Coverage   71.45%   71.39%   -0.06%
==========================================
  Files         445      445
  Lines       42754    42765      +11
==========================================
- Hits        30549    30532      -17
- Misses      10291    10313      +22
- Partials     1914     1920       +6

Flag
Coverage Δ

go-1.15
71.39% <50.00%> (-0.02%)
:arrow_down:

go-1.16
?

go-1.17
?

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

database/gdb/gdb_func.go
86.10% <ø> (ø)

database/gdb/gdb.go
71.77% <50.00%> (-1.47%)
:arrow_down:

net/gtcp/gtcp_pool.go
28.40% <0.00%> (-10.23%)
:arrow_down:

os/gmutex/gmutex.go
94.73% <0.00%> (-2.64%)
:arrow_down:

net/gtcp/gtcp_conn.go
29.64% <0.00%> (-2.02%)
:arrow_down:

container/gtree/gtree_avltree.go
95.95% <0.00%> (-0.58%)
:arrow_down:

container/gtree/gtree_redblacktree.go
92.30% <0.00%> (-0.46%)
:arrow_down:

Continue to review full report at Codecov.

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


store+querier: QueryPushdown PoC using StoreAPI and nested PromQL.

This yolo query pushdown implementation is semi-hardcorded for instant query sum(count_over_time(<>[2w])) by (cluster, replica), but can be extended to any associative query. It allows Querier to detect detailed query hints (function, range step etc in nested fashion)  and pushdown them to proxy and underlying leafs. Leaf (in this case store) gets hints in request, fetches matched series from each block concurrently AND before giving to merge sort it aggregates using AggregatedSeriesSet wrapped with promQL engine. This needs a bit of work ofc to optimize PromQL engine for such usage. Hacked it for demo purposes for now.
Pros of this approach:

Ultra-simple
Should be quicker (benchmarks in progress)

Cons:

Does not work (YET!) (:
Still if the block is too large (too many series) we cannot shard query by series - this can be solved by series ID sharding on top of it.

Signed-off-by: Bartlomiej Plotka<EMAIL_ADDRESS>

Tests will not work because I hijacked dedup option to control QP

I have some nice panic to fix, and it should work then ;p
11:33:57 store1: pushed query on block
11:33:57 store1: : sum(count_over_time(name{}[1209600000ms])) by ( cluster, replica )
11:33:57 store1: panic: runtime error: invalid memory address or nil pointer dereference
11:33:57 store1: [signal SIGSEGV: segmentation violation code=0x1 addr=0x18 pc=0x1193449]
11:33:57 store1: goroutine 1655 [running]:
11:33:57 store1: github.com/thanos-io/thanos/pkg/store/promqlaggr.(*seriesQueryable).Close(0xc020b90160)
11:33:57 store1: <autogenerated>:1 +0x29
11:33:57 store1: github.com/prometheus/prometheus/promql.(*Engine).execEvalStmt(0xc020b422a0, {0x1ff7c30, 0xc020b48ab0}, 0xc000899020, 0xc01b3ba2d0)
11:33:57 store1: /home/bwplotka/Repos/thanosgopath/pkg/mod/github.com/prometheus/prometheus@v1.8.2-0.20211119115433-692a54649ed7/promql/engine.go:647 +0xe4d
11:33:57 store1: github.com/prometheus/prometheus/promql.(*Engine).exec(0xc020b422a0, {0x1ff7c30, 0xc020b48ab0}, 0xc000899020)
11:33:57 store1: /home/bwplotka/Repos/thanosgopath/pkg/mod/github.com/prometheus/prometheus@v1.8.2-0.20211119115433-692a54649ed7/promql/engine.go:548 +0x7eb
11:33:57 store1: github.com/prometheus/prometheus/promql.(*query).Exec(0xc000899020, {0x1ff7c30, 0xc01b1eefc0})
11:33:57 store1: /home/bwplotka/Repos/thanosgopath/pkg/mod/github.com/prometheus/prometheus@v1.8.2-0.20211119115433-692a54649ed7/promql/engine.go:186 +0xb4
11:33:57 store1: github.com/thanos-io/thanos/pkg/store/promqlaggr.AggregatedSeriesSet({0x1ff7c30, 0xc01b1eefc0}, {0x1fdea00, 0xc01a4fbef0}, 0xc01b1eeba0, 0x0, {0xc00b97d900, 0x2, 0xc01b123fd0})
11:33:57 store1: /home/bwplotka/Repos/thanos/pkg/store/promqlaggr/aggregator.go:77 +0x342
11:33:57 store1: github.com/thanos-io/thanos/pkg/store.(*BucketStore).Series.func2()
11:33:57 store1: /home/bwplotka/Repos/thanos/pkg/store/bucket.go:1082 +0x4fa
11:33:57 store1: golang.org/x/sync/errgroup.(*Group).Go.func1()
11:33:57 store1: /home/bwplotka/Repos/thanosgopath/pkg/mod/golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c/errgroup/errgroup.go:57 +0x67
11:33:57 store1: created by golang.org/x/sync/errgroup.(*Group).Go
11:33:57 store1: /home/bwplotka/Repos/thanosgopath/pkg/mod/golang.org/x/sync@v0.0.0-20210220032951-036812b2e83c/errgroup/errgroup.go:54 +0x92
11:33:57 store-prom2: pushed query on block
11:33:57 store-prom2: : sum(count_over_time(name{}[1209600000ms])) by ( cluster, replica )
11:33:57 store-prom2: panic:
11:33:57 store-prom2: runtime error: invalid memory address or nil pointer dereference
11:33:57 store-prom2: [signal SIGSEGV: segmentation violation code=
11:33:57 store-prom2: 0x1
11:33:57 store-prom2: addr=0x18 pc=0x1193449]
11:33:57 store-prom2: goroutine 4570 [running]:
11:33:57 store-prom2: github.com/thanos-io/thanos/pkg/store/promqlaggr.(*seriesQueryable).Close
11:33:57 store-prom2: (0xc0456f6dc0)

Current status:
Without pushdown the query sum(count_over_time(continuous_app_metric0[2w])) by (cluster, replica) on my data (20k series full of samples for 2w = 1.6 billions of samples) .. [after 2.7m timeout] (no dedup).
With QP enabled, same query on same setup takes only ~20s! (no dedup). Previously my runs of no pushdown were returning within 1.7m (my laptop doing more work now?), but in this case the QP case would be probably faster too. We can assume more than ~6x time improvement with this very naive implementation.

Resource usage is better too. Total CPU time is only slightly bigger, within 2 CPU (more concurrency), memory is enormously better. Not much of CPU increase which indicates more concurreny is possible. Total memory 2x less, BUT distributed across nodes (QP, nonQP, nonQP, QP runs):

Do you want to do this in a feature branch? Is it ready for a review? :p

I think not as it is now. It's a demo what can be done. If we want this even in this naitve form we need to explore:

Adding button for turning this off and on
Passing more hints to PromQL
Creating extensive unit tests
Making sure this WON'T be used with duplicated or overlapped data

So - lots of work still.

I am convinced that wrapping everything into the current SeriesResponse is the way to go because with pushdown, we will probably never have "100% correct responses" either way. For example, when executing rate(foo[5m]) you won't know whether there was any missing data in foo[5m] because rate extrapolates. So, we will lose some accuracy either way. But, I think that's a reasonable trade-off to make. I would vote to make this feature opt-out, not opt-in.

I disagree with that. I would aim with 100% correctness. We can totally work with rate boundaries by returning raw samples near the boundaries of shared time range, plus we can shard and query pushdown to disjoint series (!) where no rate can extrapolate outside of matched time range (:

Good job! The PoC makes sense to me. I have few very high level comments:

At the current stage, it requires a guarantee that a series is only within a single block for the given time range, so we can't enable it if compactor is lagging behind (or enable it for series queried from receiver).
I think you may have problems (in terms of correctness) with NaN and StaleNaN and the PromQL lookback period when they are around the block range period boundaries.
Design wise, I'm not super convinced about running PromQL engine in the store. My concern is just a architectural thing.
Have you considered pushing down the partial query instead of hints?

Thanks for the comments @pracucci!

At the current stage, it requires a guarantee that a series is only within a single block for the given time range, so we can't enable it if compactor is lagging behind (or enable it for series queried from receiver). Looks quite a strong guarantee to me. Most queries hit most recent data (and can be slow because querying hundred thousands of series).

Correct, see an initial version that in theory does not need dedup/non-overlapped series: https://github.com/thanos-io/thanos/pull/4917 This is for trivial stuff like min/max etc.
In terms of correctness around edges and duplication for other functions, we have to find some solutions indeed. In Thanos world, it might be safe to pushdown to Prometheus and make sure data not overlaps e.g time-wise with stores. For HA this get's tricker, but maybe there is a way to do deduplication in some dynamic fashion - instead of doing this per series, assume full time range from one Prometheus is not queryable during downtime period.
For Receivers and Cortex ingesters, it's might be tricker indeed because we shard and replicate by individual series. We could still try to group receivers/ingesters in some way or pushdown the calculation while keeping replica label. Something to think about.

I think you may have problems (in terms of correctness) with NaN and StaleNaN and the PromQL lookback period when they are around the block range period boundaries.

True, this has to be handled correctly, similar to rate algorithm discussed in https://github.com/thanos-io/thanos/pull/4901#issuecomment-981835385 (:

Design wise, I'm not super convinced about running PromQL engine in the store. My concern is just a architectural thing.

Could you elaborate? Do you think it would need to be too generic? I like the idea of reusing same, tricky piece, but I might be wrong.

Have you considered pushing down the partial query instead of hints?

Yes and I don't see a difference. You can construct query from hints and vice versa. So is it worth to keep preparing? hints does not require that parsing 🤔 But I don't think it makes any difference if we choose partial PromQL string vs hints. Do you have any benefit I might have missed?

NOTE: https://github.com/thanos-io/thanos/pull/4917 Filips started version which could be merged.
This PR is only for overview and will be closed as soon as discussion die out and PoC will be finished (:


Triangular Convex Region with Polytope

Hey Everyone,
I am very new to TULIP and polytope. For my problem I want to define a triangular region instead of a rectangular region as you guys have explained in the tutorials and examples. What I wanna do is described in this image

I want green to be given proposition (let's say A) and blue part to B. But as in the tutorial we can only define rectangular regions or as half planes but I am not what I am doing is right or not. This is what I am doing
Continuous state space
cont_state_space = box2poly([[0., 5.], [0., 5.]])
#This is how I am defining the lower part of the region i.e. the blue part
cont_props = {}
A = np.array([[1.0, -1.0],
[-1.0, -0.0],
[-0.0, -1.0]])
b = np.array([0.0, 0.0, 0.0, 0.0])
p = pc.Polytope(A, b)
But when I print p, it gives
Single polytope
[[ 0.70711 -0.70711] |    [[0.]
[-1.      -0.     ]         x <=  [0.]
[-0.      -1.     ]]          |     [0.]]
P.S. This diagonal line line is x1 = x2. So this gives me x1 - x2 = 0. Converting to matrix form gives the above form.
Thanks in advance

What is your question?
Are you asking why the first row of the matrix is 0.70711 -0.70711 instead of 1 -1 ?

Thank you for your response.
Actually, I am not sure whether I am doing it right or not. and yes why does it change to 0.70711 -0.70711 instead of 1 -1 in the first row of the matrix?


Use local path for custom HTML5 shell export

Fixes #17286
Only changes the property hint, so this is backwards compatible

Now that Godot 3.1 has been released, we don't plan to cherry-pick new features and enhancements to the 3.0 branch, unless there is very strong support in favor of it. Removing cherrypick label for 3.0.


electron-forge package not respecting .compilerc

I have a .compilerc that looks like:
{
  "env": {
    "development": {
      "application/javascript": {
        "presets": [
          [
            "env",
            {
              "targets": {
                "chrome": 56
              }
            }
          ]
        ],
        "plugins": [],
        "sourceMaps": "inline"
      }
    },
    "production": {
      "application/javascript": {
        "presets": [
          [
            "env",
            {
              "targets": {
                "chrome": 56
              }
            }
          ]
        ],
        "plugins": [],
        "sourceMaps": "none"
      }
    }
  }
}

With electron-forge start I seem to be having no trouble and .compilerc is being respected.
With electron-forge package. The packaged application gives me an error which I can trace back to this babel bug: https://github.com/babel/babel/issues/3930 . However, this babel plugin shouldn't even be used considering the above .compilerc.
When I look in the packaged application /resouces/app/.cache/compiler-info.json.gz I see these lines:
"text/jsx":{"name":"BabelCompiler","inputMimeTypes":["text/jsx","application/javascript"],"compilerOptions":{"presets":["es2016-node5","react"],"sourceMaps":"inline"},"compilerVersion":"6.23.1"},

"application/javascript":{"name":"BabelCompiler","inputMimeTypes":["text/jsx","application/javascript"],"compilerOptions":{"presets":["es2016-node5","react"],"sourceMaps":"inline"},"compilerVersion":"6.23.1"},

So I have no idea why it is using those compiler options instead of the ones in my .compilerc

/cc @paulcbetts I'll look into this but do you have any idea why this could happen, never seen it before?

After looking into it more, what happens is that while packaging the app, it tries to look in the temporary packaging folder for the .compilerc file.
So for example: /tmp/electron-packager/linux-x64/my_app-linux-x64/resources/app/.compilerc
However, while the package.json is copied over, the .compilerc is not and therefore it falls back to the default config...
I have no idea who should be responsible for that...

@sebakerckhof Possibly your ignore config for electron-forge?

Aah, of course, way back I put in a regex ignoring all files starting with a . at the root location. My bad, sorry.


KTOR-6409 and KTOR-5839 document staticZip and using Path as resources

KTOR-6409
KTOR-5839

Show how to serve a single file as resource using Path.
Document  the staticZip() function.
Rewrite the Serving Static Content topic to include existing and new code samples, improve structure, and fix grammar mistakes and formatting.

LGTM


Bug when using conda-lock within environment deployment

There is currently this issue in the conda github repo related to a bug with conda-lock when a package in the environment yaml file contains a hash (#) in the package specification.
This happens to be the case for this repo's env.yml file in the mule installation through pip (note the #subdirectory=mule at the end of the line).
This, as reported in the conda GitHub repo issue above, causes the current deployment action to fail with the same error.
I also tested the deployment when commenting the "hashy" line in the env.yml file, and in that case conda-lock runs without problems, meaning the hash (#) is effectively the problem here.
Currently, mule needs to be installed through pip as specified in this repo's env.yml (containing a hash (#) within the pip package installation line).
Is there any way to solve this for the time being?
Do we have any alternatives to using conda-lock?
@CodeGat

Seems like this PR might be relevant: https://github.com/ACCESS-NRI/payu-condaenv/pull/37#issuecomment-2287665832 in which I was talking about the #subdirectory=mule bit. @jo-basevi might be able to help as well.

In the PR you linked, only the env-dev.yml environment is deployed, so the deploy-dev.yml is run for the action.
But in the deploy-dev.yml file there is no conda-lock run in the Create Pack step:
https://github.com/ACCESS-NRI/payu-condaenv/blob/485b4d9dd02a46c070a603b837c9b7880f214cf2/.github/workflows/deploy-dev.yml#L88-L90
whereas in the deploy.yml there is:
https://github.com/ACCESS-NRI/payu-condaenv/blob/485b4d9dd02a46c070a603b837c9b7880f214cf2/.github/workflows/deploy.yml#L46-L50
The conda-lock run is what causes issues.
Whenever the env.yml file is going to be depoyed, it might trigger this bug also in the payu-condaenv case.

Yeah we are going to run into issues with payu-condaenv too once pip install mule is added to env.yaml.. I think conda-lock is not essential for the deployment as it was a reference of what dependencies were installed. I don't have any great ideas on alternatives. Could use micromamba list to obtain the micromamba dependencies and a pip list to get list of pip dependencies and adding those to a file.

As we are using conda-pack, the environment is already fixed and the environment can be reproduced by downloading the packed environment file so maybe using conda-lock file is not as necessary?

As we are using conda-pack, the environment is already fixed and the environment can be reproduced by downloading the packed environment file so maybe using conda-lock file is not as necessary?

The conda-lock is for "external usage" to be placed in the release files.
I commented it out for now so it won't be produced.
I would say it's not a must-have, but definitely a good thing to have if the issue gets solved!

Fixed by replacing mule installation through pip with mule from coecms conda channel!
Thank you @jo!

@atteggiani I think you meant @jo-basevi  :laughing:

Oopssss 🤣


[Bug] Misuse of Docker API and misunderstanding of Ray HA cause test_ray_serve flaky

Search before asking

[X] I searched the issues and found no similar issues.

KubeRay Component
ci
What happened + What you expected to happen
See #620.
Reproduction script
See #620.
Anything else
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

cc @jasoonn
The following links may be useful.

#619
#620

How does the docker container communicate with the k8s cluster?

NodePort Service: head pod <--> local
Docker (network_mode: host): container <--> local

You can try curl <IP_ADDRESS>:10001 (valid port) in both your local laptop and the container. You will get curl: (56) Recv failure: Connection reset by peer. You can also run curl <IP_ADDRESS>:10002 (invalid port), and you will get curl: (7) Failed to connect to <IP_ADDRESS> port 10002: Connection refused.

@kevin85421
Thanks a lot for the information. I will work on it!


Worker stop handle jobs if redis is disconnected

Hello in some case as follow a worker may stop listening for new tasks, this happens when the connection between the worker & redis  is interrupted.
Start a worker :
pub async fn send_email(job: Email, _ctx: JobContext) -> impl IntoJobResponse {
    println!("sleeping");
    let dur = time::Duration::from_millis(5_000);
    thread::sleep(dur);
    println!("job number {}", job.text);
}

#[tokio::main]
async fn main() -> Result<()> {
    let storage = RedisStorage::connect("redis://<IP_ADDRESS>/").await.expect("");
    Monitor::new()
        .register(
            WorkerBuilder::new(storage.clone())
                .build_fn(send_email),
        )
        .run()
        .await
}

Then with a client send 20 tasks for example.
Once some job are processed, restart redis, under macOS: brew service restart redis.
If the worker was already processing a job (eg in our example sleeping ...)
then the worker will finish this task and will NOT handle the rest of 20 initial tasks.
But you can start another worker in parallel and it will handle the reste of the task without any issue.
If this issue can be fixed this will allow enable the Try Reconnect feature in the middle of application and also at startup (celery style)

Hello @geofmureithi
Did you get time to investigate this issue ?
Since this could be really problematic ^^

Hey @AzHicham This can be fixed by using https://docs.rs/redis/latest/redis/aio/struct.ConnectionManager.html in Redis storage. It will be fixed in the next release.

Ok nice to know !!! Thank you

Hi @geofmureithi, Thanks for providing this amazing repo. This one really suits our need. We are currently trying it out. We are on 0.3.6 and considering moving to 0.4.1. We had this issue hit us couple of times and we need to restart our services to start processing the jobs.
Is this issue still open? would be great to know what version we can expect this fix?

Hey. Am aware of this issue. The goal was to move from a concrete connection manager to using the generic one provided by the redis crate.
Unfortunately I was not able to do that in 0.4. I don't want to change the API with a new version release. For now I will do a hotfix and do a release that will sort this issue then tackle the API issue later.

@AzHicham @shan-pandian Please verify this is fixed in v0.4.2 if possible.


About the accuracy mismatch using the example code

Hi,
I ran the code (main.py) using the default settings, but only get ~53% accuracy on the target set (80% on the source set), is anything not set appropriately?
Thanks.
Sam

how many epochs you ran?

100 epochs

Thank you, I really make a mistake, you can fix the error by replace transform.RandomSizedCrop with transfrom.Resize, and I will upload the fixed version later.

Thanks,  now the test accuracy on the target domain achieves amazing 90%, far more better than the paper. What about your own experiment?

@fungtion
Hi, can you tell me what is the difference?

@omg777  comparing with the original paper, I set $\lambda$ in domain classifier as 1, and use Adam instead of SGD optimizer

@fungtion What is $\lambda$ ?
and when I run main.py ,
in this line class_output, domain_output = my_net(input_data=inputv_img, alpha=alpha)
ValueError: expected 4D input (got 2D input)
error occurs. How can I fix this?
(my settings: python2.7 , pytorch0.4.1)

@omg777 $\lambda$ means alpha in the main.py, inputv_img must be 4D (n, c, w, h), you'd better check the shape of your inputv_img

@omg777 @fungtion I also have the same problem. We didn't change your code, it runs and it get the results. Could you please check the code? The error is class_output = self.class_classifier(feature) of the model file.

@jindongwang the same error ValueError: expected 4D input (got 2D input)?

@fungtion Try my code: https://github.com/jindongwang/transferlearning/tree/master/code/deep/DANN(RevGrad)

@jindongwang I mean you got the same error ValueError: expected 4D input (got 2D input) ?

@fungtion Yes, but I fixed that in my code...

@jindongwang Can you show me why you got the error when running my code, since I didn't meet the error before, thank you.

@fungtion I think it's the pytorch version. We are using 0.4.0, while you are using 0.3...

@jindongwang Ok

@fungtion The problem is BatchNorm2d function. I change it to BatchNorm1d and it's fine. https://github.com/jindongwang/transferlearning/blob/master/code/deep/DANN(RevGrad)/main/model.py

@jindongwang I see, I'll fix it, thank you.


autoplay mp4

I'd like to play time-killer videos while AI is thinking.
I'm using animated GIFs, however, their file size is 10 times larger than mp4.
I'd like to have:
video = cl.Video(......, autoplay=True)
or
await video.play().
Thanks.

did you solved this problem? :(


How to Deploy and Run Ballerina Programs

Adding content for "How to Deploy and Run Ballerina Programs"

Do not merge until Tyler and Kasun review.


Correct time to update checking in SAC/TD3

Description
Corrected minor bug in sac where train_freq was compared to local variable step instead of agent.num_timesteps in order to check if it was time to update.
Motivation and Context
Running agent.learn with total_timesteps less than the update frequency resulted in no policy updates.

[x]  I have raised an issue to propose this change (required for new features and bug fixes)
Closes #754 .

Types of changes

[x]  Bug fix (non-breaking change which fixes an issue)
[ ]  New feature (non-breaking change which adds functionality)
[ ]  Breaking change (fix or feature that would cause existing functionality to change)
[ ]  Documentation (update in the documentation)

Checklist:

[x] I've read the CONTRIBUTION guide (required)
[x] I have updated the changelog accordingly (required).
[ ] My change requires a change to the documentation.
[ ] I have updated the tests accordingly (required for a bug fix or a new feature).
[ ]  I have updated the documentation accordingly.
[ ] I have ensured pytest and pytype both pass (by running make pytest and make type).

I did it for TD3 as well.


Feature/garbage data range

Adds the ability to limit the garbage data range.  Useful if input data is an index into another buffer or memory.

Looks good to me!


Update uninstall-az-ps.md

Update command to uninstall PowerShell AzureRm Module

Docs Build status updates of commit 7964d4e:
:clock10: Full build: the average full build time is 22 min(s) 34 sec(s), this is based on the last 265 build(s) for this repository.

Docs Build status updates of commit 7964d4e:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

docs-conceptual/azps-3.1.0/uninstall-az-ps.md
:white_check_mark:Succeeded
View (azps-3.1.0)

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


Make the output of diff and push the same when no changes

Coverage decreased (-0.02%) to 85.441% when pulling cdc430fedf1c30f8ee3c3552b166fe15a78e99f7 on msgs into 21f66fd7ff0e1f3cc077fa6054d4cbc09af8b4dc on master.

LGTM


Add remapping to coupler puts & gets

Purpose and Content
Adds remapping to the coupler put! and get calls. Implements these calls in the sea breeze simulation
Benefits and Risks
Hides explicitly calling remapping operations from the user.
Next steps
The initialization phase needs reworking and reordering in order to facilitate the auto-construction of the remap operators.
Linked Issues
#44
PR Checklist

[x] This PR has a corresponding issue OR is linked to an SDI.
[x] I have followed CliMA's codebase contribution and style guidelines OR N/A.
[x] I have followed CliMA's documentation policy.
[x] I have checked all issues and PRs and I certify that this PR does not duplicate an open PR.
[x] I linted my code on my local machine prior to submission OR N/A.
[x] Unit tests are included OR N/A.
[x] Code used in an integration test OR N/A.
[x] All tests ran successfully on my local machine OR N/A.
[x] All classes, modules, and function contain docstrings OR N/A.
[x] Documentation has been added/updated OR N/A.

Currently it is not possible to map to an exchange or intermediary grid -- any field put! in the coupler lives on the space of the simulation that puts it there.

Currently it is not possible to map to an exchange or intermediary grid -- any field put! in the coupler lives on the space of the simulation that puts it there.

Currently it is not possible to map to an exchange or intermediary grid -- any field put! in the coupler lives on the space of the simulation that puts it there.

This is because of the current way the mapping is set up which uses a tag (write_sim) to specify the source space/sim when remapping. This tag also (as the name suggests) indicates which simulation has write permissions to that coupled field.
Perhaps the right solution is to remove the double usage of write_sim and add another tag like "space_name" which would be part of the remap operator name.

This PR sets up several follow up PRs:

Documentation updates:
i. Change example used to the sea breeze as this is checked by buildkite and now a cleaner example
ii. Add DocStringExtensions to improve doc quality
Add a coupler_get! method that accepts a field that will be modified/filled by the coupler_get call
ClimaCore: introduce AbstractRemap abstract type, with concrete subtypes including LinearRemap, IdentityRemap, RLLRemap, etc.
Update coupler_put! to include a remap operation. This creates symmetry and more flexibility for what grid the coupling takes place on.
Auto-build remap operators during init phase

bors r+


Instructions reference old cli & asm mode

This document shows examples which use 1) the 1.0 xplat cli ("azure"), and 2) asm mode.  Both of these are deprecated.  Document should be updated to reflect newer cli and arm mode.

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

ID: 34c16b61-15ac-f9ad-f001-ecf223074dea
Version Independent ID: 6cef5cf6-b524-e70f-5882-f5304a6d6f26
Content: Join a RedHat Linux VM to an Azure Active Directory DS
Content Source: articles/virtual-machines/linux/join-redhat-linux-vm-to-azure-active-directory-domain-service.md
Service: virtual-machines-linux
GitHub Login: @vlivech
Microsoft Alias: v-livech

@larryms Thanks for the feedback! I have assigned the issue to the content author to investigate further and update the document as appropriate.
@timlt I have assigned this to you as it seems I am not able to assign to @vlivech

Thanks, @larryms . This is a known area that we need to address, and have a backlog work item to update this for Resource Manager. At the time, even though CLI 2.0 and Resource Manager was the preferred approach, AAD DS only supported ASM. As we have a backlog work item for this already, I'm going to close out this issue.
#please-close

@iainfoulds, can you pls update metadata in this article to current manager?

@iainfoulds Closing issue with an understanding that metadata will be updated.

@Mike-Ubezzi-MSFT Yes, @jpconnock is working on updating metadata


Adding matrix to travis

R: @jeffposnick @addyosmani
This is the first step in fixing the remaining issues on: #48

I believe we currently only display a single build status for our CI for the overall repo. I'd like to suggest we also include badges for individual projects in the README so folks can instantly tell what is green and what is not.

This PR doesn't include the individual shields, but I will do that tomorrow in a follow up PR once I get the server accessible somewhere.

@jeffposnick happy for this to land?

I just took a look at the Travis runs and it seems like we're spending ~1 minute per project on the npm install step, even though the same package.json is used for each of the runs. How about configuring:
cache:
  directories:
    - node_modules

as per https://blog.travis-ci.com/2013-12-05-speed-up-your-builds-cache-your-dependencies?

Just added this in. Will look at doing the same for the selenium browsers later today as well (once this + shields is in).

So something weird is occuring with Travis since switching on node module caching (although I think that's just a coincidence. Node failed to install Node 7 (i.e. stable) and now it's failing to find modules that were originally installed.
Hopefully a new build soon will pass without these errors.

Hmm, each of the projects are still taking ~1 minute on npm install and installing their own copies of everything.
Maybe the next full build will actually take advantage of the cache?

Yeah I cleared the cache to get the tests to pass (I think the first attempt was broken and continued breaking.

Well the caches page on travis is showing '309.03MB' begin cached for the branch and PR, so I think it's working.
@jeffposnick are you happy to take this PR or do you want me to push some "fake changes" to see if the caching is working?


Add release notes and version bump for the 0.6.2 security fix release.

Once https://github.com/theupdateframework/notary/pull/1420 gets merged, we can merge this, tag the branch, build, and put the released binaries up.
cc @eiais @justincormack.
Will update the date as needed post LGTM.
As a note, this PR isn't based on https://github.com/theupdateframework/notary/pull/1420 and won't have those fixes, including the Circle CI fix, so likely CI will fail for this PR.

Can one of the admins verify this patch?

Thanks for getting to this :smiley:


Windows 11 22H2 Adding rule crash

[ ] This is not about other apps being displayed weird or etc.
[ ] This is not about rendering issues that caused by a bug in the Windows.
[ ] I've read FAQ.
[ ] I've checked other issues and this is not a duplicate.
Describe the bug
A clear and concise description of what the bug is.
To Reproduce
Steps to reproduce the behavior:

Go to 'Mica For Everyone'
Click on 'Plus Icon, then create rule or for class or process'
Scroll down to '....'
See error

Expected behavior
Program will simply crash without any error
Screenshots
If applicable, add screenshots to help explain your problem.
Windows Version
Windows 11 22H2 22621.1848
Additional context
I saw in FAQ that crash exists on older versions of Windows 11, but I have 22H2 which is way newer and says it's supported

同样的问题

same here. i'm in canary insider build 25393.1

#307

saaaame

Seems to be fixed for me in the latest commits.

updated today, have tried just now and the problem still presents

Well did you clone the source code from GitHub/using Action builds or did you use Releases?

Well did you clone the source code from GitHub/using Action builds or did you use Releases?

I just used Releases. Don't quite understand how to build from source code, but I'll try and check now, thanks

well, nope.
as I understand, it should load from Installer.iss through InnoSetup, but I just keep getting different errors  when I try to make an installer through it.
and while I managed to resolve a few, they keep spawning

You can try downloading through Actions: https://github.com/MicaForEveryone/MicaForEveryone/actions/runs/5533151624

thank you, it fixed everything

You can try downloading through Actions: https://github.com/MicaForEveryone/MicaForEveryone/actions/runs/5533151624

虽然添加规则不崩溃了，但是添加的规则设置的效果不能自动加载了，需要手动切换选择后才有效果
Although adding rules does not crash, the effect of the added rule settings cannot be automatically loaded and needs to be manually switched to have an effect

You mean that the rule does not apply to new windows?
Message ID: @.***>

You mean that the rule does not apply to new windows? Message ID: @.***>

是的，比如，添加一个应用程序名的规则，将这个规则的模糊类型设置为 亚克力 ，并把模糊特效打开；此时打开规则的应用程序，窗口并不会加载设置的效果，需要去手动选择切换 模糊类型或模糊特效，应用程序效果才生效
Yes, for example, add a rule for the application name, set the fuzzy type of this rule to Acrylic, and turn on the fuzzy special effects; At this point, open the rule application, and the window will not load the set effect. You need to manually choose to switch the blur type or blur special effect for the application effect to take effect

@simear2004 A bug report has already been opened for it: #315.

Fixed in <IP_ADDRESS> on GitHub.


Moment is now a legacy project

Hello,
The Moment.js team has announced here that the project is now considered as legacy.
Now, Chart.js is using Moment 2.27.0.
I would like to know what is the Chart.js development team's reaction about this news.
Do you still consider using Moment or will you use an other library ?
Thank you

@sylvain-pointud moment will no longer be a dependency when v3 (currently in beta) ships. In the meantime, you can use either date-fns or luxon via different adapters. https://www.chartjs.org/docs/latest/axes/cartesian/time.html#date-adapters

Thank you for your quick reply.


Problem with updating logo

I'm submitting a ...
[ ] bug report
[ ] feature request
[ ] question about the decisions made in the repository
[x ] question about how to use this project

Summary
@keone One of our developers have uploaded our tokendetails including the logo, however he does not have acces to his github account anymore. We would like to change our current logo to https://github.com/Solviewapp/solviewlogo/blob/main/Solviewlogo copy.png?raw=true

Other information (e.g. detailed explanation, stack traces, related issues, suggestions how to fix, links for us to have context, eg. StackOverflow, personal fork, etc.)

#18733 That is for updating SOLV token LOGO PR

Thanks

that PR is closed and I can't reopen it bc the branch was deleted

Okay I will try again

#18843

merged

Thanks


perf(app): #33 optimize all images in what we do section

This includes a refactor to astro for the component.
This is important because these are all very high-res images (8MB+) and therefore load slowly on end-user devices and also eat up all our Vercel bandwidth:

Related to #33

@Han2-Ro There is an issue I just noticed: Expanding the exercises does not work anymore. This is not covered by our tests yet!

I'm really confused. It does not work in dev but with pnpm run build && pnpm run preview it works like a charm.
In dev mode I get this error:
Error hydrating /src/components/about-us/Exercises.svelte SyntaxError: The requested module '/node_modules/.pnpm/cssesc@3.0.0/node_modules/cssesc/cssesc.js?v=38871376' does not provide an export named 'default' (at transition.js?v=38871376:3:8)
start @ about-us:2408
await in start (async)
childrenConnectedCallback @ about-us:2408
await in childrenConnectedCallback (async)
connectedCallback @ about-us:2408
m @ @astrojs_svelte_client__js.js?v=38871376:43
mount @ MeltPortalled.svelte:11
mount_component @ chunk-6C6FYBOG.js?v=38871376:2134
init @ chunk-6C6FYBOG.js?v=38871376:2215
MeltPortalled @ MeltPortalled.svelte:6
createProxiedComponent @ svelte-hooks.js?v=38871376:341
ProxyComponent @ proxy.js?v=38871376:242
Proxy<MeltPortalled> @ proxy.js?v=38871376:349
(anonymous) @ @astrojs_svelte_client__js.js?v=38871376:19
(anonymous) @ about-us:2408
e @ about-us:2408
await in e (async)
start @ about-us:2408
childrenConnectedCallback @ about-us:2408
await in childrenConnectedCallback (async)
e @ about-us:2408
(anonymous) @ about-us:2408
Show 7 more frames
Show less

What's so weird about it is that the supporting member component in /support-us works fine and does the same thing. Both use melt-ui and a transition:slide ...

Very very weird: It suddenly stopped happening and now works reliably??


Remove semicolons from end of TPMA_* macro definitions.

The semicolon prevents us from using these macros like so:
TPMA_ALGORITHM algorithm_attrs =
TPMA_ALGORITHM_ASYMMETRIC + TPMA_ALGORITHM_SYMMETRIC;
This resolves #272
Signed-off-by: Philip Tricca<EMAIL_ADDRESS>

Looks like a bug in the autogeneration code.  Should be fixed there.


ApplicationPrincipals. Error:ApplicationPrincipalAbortableError on working cluster

I have a cluster where applications are deployed and works.
Then once a while I do see the following error:
Error event: SourceId='System.Hosting', Property='Activation:1.0'. There was an error during activation.Failed to setup ApplicationPrincipals. Error:ApplicationPrincipalAbortableError

in the explorer.  Restarting the node in explorer do not resolve it, when the application comes up again then it reports the error again.
Reimaging the node from azure portal works. But as i am evaluating SF for this project, i dont want to manually have to fix these things. But i dont get why the error can come after the application have been running fine. If there is principal errors or certs errors, i would expect them to be there in the beginning.
What can I do to provide more information/ logs/traces/dumps to help find out why it happens?

any updates on this?
I'm experiencing the same issue on a Ubuntu 16.04 cluster.


Add configure PS1 to load on windows logon

On first login, run powershell to configure setup.

Want to back this issue? Post a bounty on it! We accept bounties via Bountysource.

Implemented as First-Login.ps1