Tagging the published ontology version

To make things easier for readers of the FLOPO manuscript it would be convenient if there were a tagged release that uses semantic versioning (e.g. v0.1.0). Barring that and/or for the time being, it is worth noting that the version in the manuscript corresponds with revision e0e1450b91d12a9990338c1030d0cb190cc6ef9e

In the interest of completeness: this can be done like so:
$ git tag -a v0.1.0 e0e1450 -m "Manuscript version"
$ git push --tags origin master
I notice that the repository is now also linked to Zenodo so if that is configured correctly this tagging will also trigger the minting of a DOI.


Catch invalid conversion of k8s 1.7 policies

Description
We're not handling policies received from k8s 1.7 properly at the moment.  Namely, those policies don't have a polciyTypes field which means libcalico defaults them to Ingress/Egress.
The k8s backend really should be catching this and including Ingress since k8s 1.7 networkpolicies only affect ingress.
This is just a UT, the fix is in libcalico I think.
This PR also includes some cleaning up of the Context/It/By decorator usage.
CC @tmjd I think this is the failure you're hitting and what's causing the e2e failures.
Todos

[x] Tests
[x] Documentation
[x] Release note

Release Note

None required

This should be the correct fix: https://github.com/projectcalico/libcalico-go/pull/531

Ok, updated to latest libcalico and tests appear to be passing


[core] error: invalid method declaration; return type required

Issue details
Windows JADX 1.5.1, JAVA version 23.0.1
When I decompile jar I got :
      this.someVar = Platform.xxxxx(new xxxxx(new xxxxx.Provider() {
            AnonymousClass1() {
            }

So when I want to compile that java file :
javac -cp ../some.jar:. myJava.java -g
I got:
error: invalid method declaration; return type required
AnonymousClass1() {

Jadx version
1.5.1

Can't fix without sample


[SPARK-14085] [SQL] Star Expansion for Hash and Concat

What changes were proposed in this pull request?
This PR is to support star expansion in hash and concat. For example,
val structDf = testData2.select("a", "b").as("record")
structDf.select(hash($"*")
structDf.select(concat($"*"))

In addition, it refactors the codes for the rule ResolveStar and fixes a regression for star expansion in group by when using SQL API. For example,
SELECT * FROM testData2 group by a, b

cc @cloud-fan Now, the code for star resolution is much cleaner. The coverage is better. Could you check if this refactoring is good? Thanks!
How was this patch tested?
Added a few test cases to cover it.

Test build #53840 has started for PR 11904 at commit c0551aa.

Test build #53840 has finished for PR 11904 at commit c0551aa.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53840/
Test PASSed.

It's pretty strange to do this -- who's actually doing it for concat?

ok. How about the other three? hash, greatest and least? Should we support them for star expansion?

hash makes a lot of sense. greatest and least are kind of funny since i'd imagine columns are of different types...

Maybe we can restrict it to hash only with less code changes. Thanks!

that sounds reasonable

Test build #53892 has started for PR 11904 at commit 4368a6c.

Test build #53892 has finished for PR 11904 at commit 4368a6c.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53892/
Test FAILed.

Test build #53935 has started for PR 11904 at commit 73160a3.

Test build #53935 has finished for PR 11904 at commit 73160a3.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53935/
Test PASSed.

Test build #53942 has started for PR 11904 at commit 4c8d24a.

Test build #53942 has finished for PR 11904 at commit 4c8d24a.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53942/
Test PASSed.

LGTM pending tests

Test build #53987 has started for PR 11904 at commit 7af4eee.

Test build #53987 has finished for PR 11904 at commit 7af4eee.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/53987/
Test PASSed.

thanks, merging to master!

Thank you!


Option to populate a cache directory

Some consumers of Tarmac, like Roblox, want to have local copies of each uploaded asset, indexed by asset ID.
Tarmac should support an additional flag or separate command to create an output cache out of whatever the current state is by downloading images from Roblox:
# As a flag
tarmac sync --target roblox --cache-dir my-cache/

# As a separate command
tarmac sync --target roblox
tarmac make-cache my-cache/

Currently implemented as a property on the project file, but possible it should be turned into a flag for practical usage.

Done as the create-cache-map command, which rolled up two commands into one.


"Getting started" link broken

Link to →GETTING STARTED (http://trailblazer.to/gems/operation/2.0/guides/getting_started_with_trailblazer_2.html) from http://trailblazer.to/gems/operation/2.0/index.html#learn-more gives 404.

Thanks, the guides are not written, yet, but the first few will come this weekend. :beer:


Update 2023.12.11~ynh1 to 2024.01.05~ynh1 fail

Describe the bug
Updating Jellyfin-vueto 2024.01.05~ynh1 does not work.
Context

Hardware: OVH Kimsufi KS-5 (Intel Xeon E5-1620v2 - 4c/8t - 3.7 GHz/3.9 GHz, 32go RAM)
YunoHost version: <IP_ADDRESS> (stable)
I have access to my server: not at the moment.
Using, or trying to install package version/branch: 2024.01.05~ynh1
If upgrading, current package version: 2023.12.11~ynh1

Logs
https://paste.yunohost.org/raw/azorisabif

Solved with the last update.

Oh 😅 sorry about that...


create Travis CI build definitions

travis can build using .NET Core natively on Linux (and OSX if i can get it working)
Note that @NaamloosDT still has to manually set up a free account on travis-ci.org and mark it as enabled for builds to trigger

Travis failed because random ancient commit failed to build. 10/10 would drop again.

yeah this fucked


PHOENIX-6164 Rename phoenix4-compat and phoenix5-compat maven artifacts

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

+0 :ok:
reexec
4m 54s
Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  1s
No case conflicting files found.

+1 :green_heart:
hbaseanti
0m  0s
Patch does not have any anti-patterns.

+1 :green_heart:
@author
0m  0s
The patch does not contain any @author tags.

-1 :x:
test4tests
0m  0s
The patch doesn't appear to include any new or modified tests. Please justify why no new tests are needed for this patch. Also please list what manual steps were performed to verify this patch.

_ master Compile Tests _

+0 :ok:
mvndep
8m 43s
Maven dependency ordering for branch

+1 :green_heart:
mvninstall
7m 13s
master passed

+1 :green_heart:
compile
2m 22s
master passed

+1 :green_heart:
checkstyle
0m 20s
master passed

+1 :green_heart:
javadoc
2m 45s
master passed

+0 :ok:
spotbugs
4m 23s
root in master has 111 extant spotbugs warnings.

+0 :ok:
spotbugs
0m 51s
phoenix-hive-base/phoenix4-hive in master has 47 extant spotbugs warnings.

+0 :ok:
spotbugs
0m 56s
phoenix-hive-base/phoenix5-hive in master has 46 extant spotbugs warnings.

_ Patch Compile Tests _

-1 :x:
mvninstall
0m  6s
root in master failed.

+0 :ok:
mvndep
0m 13s
Maven dependency ordering for patch

-1 :x:
mvninstall
0m  6s
root in the patch failed.

-1 :x:
compile
0m  6s
root in the patch failed.

-1 :x:
javac
0m  6s
root in the patch failed.

-1 :x:
checkstyle
0m  4s
The patch fails to run checkstyle in root

-1 :x:
whitespace
0m  0s
The patch has 1 line(s) that end in whitespace. Use git apply --whitespace=fix <<patch_file>>. Refer https://git-scm.com/docs/git-apply

+1 :green_heart:
xml
0m 12s
The patch has no ill-formed XML file.

-1 :x:
javadoc
0m  6s
root in the patch failed.

-1 :x:
javadoc
0m 10s
phoenix4-flume in the patch failed.

-1 :x:
javadoc
0m 12s
phoenix5-flume in the patch failed.

-1 :x:
javadoc
0m  8s
phoenix4-hive in the patch failed.

-1 :x:
javadoc
0m  9s
phoenix5-hive in the patch failed.

-1 :x:
javadoc
0m  8s
phoenix4-spark in the patch failed.

-1 :x:
javadoc
0m  9s
phoenix5-spark in the patch failed.

-1 :x:
spotbugs
0m  6s
root in the patch failed.

-1 :x:
spotbugs
0m  8s
phoenix4-hive in the patch failed.

-1 :x:
spotbugs
0m  9s
phoenix5-hive in the patch failed.

_ Other Tests _

-1 :x:
unit
0m  6s
root in the patch failed.

+1 :green_heart:
asflicense
1m  2s
The patch does not generate ASF License warnings.

39m 53s

Subsystem
Report/Notes

Docker
ClientAPI=1.40 ServerAPI=1.40 base: https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-37/1/artifact/yetus-general-check/output/Dockerfile

GITHUB PR
https://github.com/apache/phoenix-connectors/pull/37

Optional Tests
dupname asflicense javac javadoc unit xml compile spotbugs hbaseanti checkstyle

uname
Linux f3f78b4ad34a 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux

Build tool
maven

Personality
dev/phoenix-connectors-personality.sh

git revision
master / 8c02df3

Default Java
Private Build-1.8.0_242-8u242-b08-0ubuntu3~16.04-b08

mvninstall
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-37/1/artifact/yetus-general-check/output/branch-mvninstall-root.txt

mvninstall
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-37/1/artifact/yetus-general-check/output/patch-mvninstall-root.txt

compile
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-37/1/artifact/yetus-general-check/output/patch-compile-root.txt

javac
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-37/1/artifact/yetus-general-check/output/patch-compile-root.txt

checkstyle
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-37/1/artifact/yetus-general-check/output/buildtool-patch-checkstyle-root.txt

whitespace
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-37/1/artifact/yetus-general-check/output/whitespace-eol.txt

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-37/1/artifact/yetus-general-check/output/patch-javadoc-root.txt

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-37/1/artifact/yetus-general-check/output/patch-javadoc-phoenix-flume-base_phoenix4-flume.txt

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-37/1/artifact/yetus-general-check/output/patch-javadoc-phoenix-flume-base_phoenix5-flume.txt

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-37/1/artifact/yetus-general-check/output/patch-javadoc-phoenix-hive-base_phoenix4-hive.txt

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-37/1/artifact/yetus-general-check/output/patch-javadoc-phoenix-hive-base_phoenix5-hive.txt

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-37/1/artifact/yetus-general-check/output/patch-javadoc-phoenix-spark-base_phoenix4-spark.txt

javadoc
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-37/1/artifact/yetus-general-check/output/patch-javadoc-phoenix-spark-base_phoenix5-spark.txt

spotbugs
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-37/1/artifact/yetus-general-check/output/patch-spotbugs-root.txt

spotbugs
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-37/1/artifact/yetus-general-check/output/patch-spotbugs-phoenix-hive-base_phoenix4-hive.txt

spotbugs
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-37/1/artifact/yetus-general-check/output/patch-spotbugs-phoenix-hive-base_phoenix5-hive.txt

unit
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-37/1/artifact/yetus-general-check/output/patch-unit-root.txt

Test Results
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-37/1/testReport/

Max. process+thread count
94 (vs. ulimit of 30000)

modules
C: . phoenix-connectors-phoenix4-compat phoenix-connectors-phoenix5-compat phoenix-flume-base/phoenix4-flume phoenix-flume-base/phoenix5-flume phoenix-hive-base/phoenix4-hive phoenix-hive-base/phoenix5-hive phoenix-spark-base/phoenix4-spark phoenix-spark-base/phoenix5-spark U: .

Console output
https://ci-hadoop.apache.org/job/Phoenix/job/Phoenix-Connectors-PreCommit-GitHub-PR/job/PR-37/1/console

versions
git=2.7.4 maven=3.3.9 spotbugs=4.1.3

Powered by
Apache Yetus 0.12.0 https://yetus.apache.org

This message was automatically generated.


Add Templatized Helm Charts

Deploying old Nodejs microservices in the interim
update apps/k8s/app/values.yml when containers are built

This change addresses the need by:

closes #7

Signed-off-by: Christopher Hein<EMAIL_ADDRESS>By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Can you exclude .DS_Store from the PR? Added to .gitignore as well?

@arun-gupta check out the latest and let me know if it works for you. Use the same command as before
helm install --name foo myapp


[FEATURE] Acknowledge alerts generated by rule detector

This will be a part of [FEATURE] Alert Orchestration Framework #37

Alerting plugin requires that we pass a monitor id and a list of alerting ids containing that monitor id to acknowledge them
In order to implement an Acknowledge Alerts API in SAP, we would need to do the following -

accept a request with alert ids, detector id
fetch list of monitor ids associated with detector
try to find which monitor is associated with each alert and then call Alerting

but for achieving the 3rd step, we would need to be able to fetch alerts by their id’s
so we would need to add support in Get Alerts API to fetch alerts by Id.
@sbcd90 @lezzago


Formatting Email to use data from other columns

#2813 ## Category

[x] Question

I have a JSON script working with an email address to open Outlook and fill in the subject and some text in the body of the email. My question, how do I incorporate data from other columns into the body of the email?  For example, I have columns named: Name1, Email1, Name2, Email2, Topic1, and Topic2. What I would like to do is have the body of the text show something like this:
Dear [Name1],
We have found [Name2] is also interested in [Topic2]. If you would like to reach out to them you may contact them by email at [Email2].
If Name1 = Tom and Name2 = David and Email2 =<EMAIL_ADDRESS>and Topic2 = Nature Photography, the email would look something like this:
Dear Tom,
We have found David is also interested in Nature Photography. If you would like to reach out to them you may contact them by email at<EMAIL_ADDRESS>I have tried using [$Name1], [$Name2], and [$Topic2] without any success. I don't know if this is possible to accomplish or not.  If it is possible, what am I missing?
Regards,
John

In order to reference the other columns, I believe they need to also be visible in the view.

Hello bcameron1231, they are visible in the view.

Here is the JSON that I am currently using.  Where the underscores are is where I want to fill in with information from other columns.
{
"$schema": "https://developer.microsoft.com/json-schemas/sp/column-formatting.schema.json",
"elmType": "div",
"children": [
{
"elmType": "span",
"style": {
"padding-right": "8px"
},
"txtContent": "@currentField"
},
{
"elmType": "a",
"attributes": {
"iconName": "Mail",
"class": "sp-field-quickActions",
"href": {
"operator": "+",
"operands": [
"mailto:",
"@currentField",
"?subject=We have a match","\r\n\r\n",
"Dear __________________.\r\n",
"We have a match for _______________________.\r\n\r\n",
"Here is the contact email: _______________\r\n",
"Happy corresponding!\r\n\r\n",
"Kind regards,\r\n\r\n",
"John"
]
}
}
}
]
}

Thanks for the comment. Are these columns visible in your view? As mentioned, if you want to reference them via [$column] they need to be visible in the view.

Yes, they are visible in the view.

If I add [$NameOne] to the JSON script nothing shows up in the field to open up an email.  The column is blank.
{
"$schema": "https://developer.microsoft.com/json-schemas/sp/column-formatting.schema.json",
"elmType": "div",
"children": [
{
"elmType": "span",
"style": {
"padding-right": "8px"
},
"txtContent": "@currentField"
},
{
"elmType": "a",
"attributes": {
"iconName": "Mail",
"class": "sp-field-quickActions",
"href": {
"operator": "+",
"operands": [
"mailto:",
"@currentField",
"?subject=We have a match","\r\n\r\n",
"Dear ", "[$NameOne]","\r\n",
"We have a match for _______________________.\r\n\r\n",
"Here is the contact email: _______________\r\n",
"Happy corresponding!\r\n\r\n",
"Kind regards,\r\n\r\n",
"John"
]
}
}
}
]
}

A couple things.

The URL you are building is incorrect, to specify the body you need to pass in the Body parameter
You'll need to concatenate your values on separate lines to get the values.

Try this JSON
{
  "$schema": "https://developer.microsoft.com/json-schemas/sp/column-formatting.schema.json",
  "debugMode": "true",
  "elmType": "div",
  "children": [
    {
      "elmType": "span",
      "style": {
        "padding-right": "8px"
      },
      "txtContent": "@currentField"
    },
    {
      "elmType": "a",
      "attributes": {
        "iconName": "Mail",
        "class": "sp-field-quickActions",
        "href": {
          "operator": "+",
          "operands": [
            "mailto:",
            "@currentField",
            "?subject=We have a match",
            "\r\n\r\n",
            "&body=Dear ",
            "=[$Test2]",
            ",\r\n",
            "We have a match for ",
            "=[$Test3]",
            "\r\n\r\n",
            "Here is the contact email: ",
            "=[$Test4]",
            "\r\n",
            "Happy corresponding!\r\n\r\n",
            "Kind regards,\r\n\r\n",
            "John"
          ]
        }
      }
    }
  ]
}

Replace the Test values with your internal column values.

Thanks for the catch on the &body=Dear, I missed that.  I did substitute the internal column values for the $Test2 (with $NameOne), $Test3 (with $Name2), and $Test4 (with $Email2).  the Column Email1, where this JSON is being placed, displays the following.
Failure: NameOne was not found on the data object.  It is in the list and on the list view being displayed.

It appears to be having trouble referencing that column. Can you send me a screen grab of your internal column name?
Also, why type of column is this?

It works perfect now.  It was my mistake.  When you asked for the internal column name that triggered it for me.  I changed the name of the columns that were being displayed for the user and that is the name I was using for the column and not the internal column name that is shown in the URL when I selected the column while editing the list.
Now I have something I can expand upon and understand it.
Thank you so much for helping me with this bcameron1231!  Really appreciate it!

bcameron1231, thanks for the help.  Also, for showing me how to break up the JSON so it does work.  I really appreciate it.

Absolutely! I appreciate the clear and concise issue descriptions and json. Very helpful to figuring out the problem!

Question for you.  Are there any good reference material to be found where there are more examples of using JSON with SharePoint other than a couple of the standard web sites that are found when do a search on this topic?  For example, a reference that would have shown how to format an email correctly so that it works the way you help me to get mine to work?

So your issue with two-fold. The missing body parameter is just an HTML requirement, not unrelated to JSON column formatting.
It's defined in RFC2368 https://www.ietf.org/rfc/rfc2368.txt , but there are likely tons of blogs out there talking on this.
In terms of JSON formatting for SharePoint, a couple great resources:
GitHub Repo With Samples
Chris Kent's Blog
Chris is the resident expert on JSON formatting and has provided many of those samples in the GitHub. His blog and this repo is a great resource to see more in depth examples of JSON formatting in SharePoint.


[POC] Remove restoreLocals flag

I don't have an intention to merge this PR, it's more to start a discussion because I feel like we can get rid of TaskRestartCallback#WithLocals because most of the heavy lifting is done by Local after @oleg-py changes.
Only two tests started failing - TaskLocals get restored in Task.create on error and locals get transported with executeOn and shift - I had to use TracingRunnable in cases with manual execution to the ExecutionContext. It might be cool to not require TracingRunnable so we probably can't just remove everything like in this PR but it seems to be possible to cut 90% of TaskLocal special cases
restoreLocals flag was introduced in https://github.com/monix/monix/pull/647
We should keep in mind https://github.com/monix/monix/issues/856 which is about issues with TaskLocal + memoize (we probably have to disable ability to modify Local from memoize)

Huh, interesting.
So we no longer need to do Local.getContext and Local.setContext on async boundaries?

I have a haunting suspicion that it might introduce undesired sharing on Tasks running in parallel, that should be isolated. I don't think our test suite could detect that, since it mostly even doesn't use real parallelism.

I have a haunting suspicion that it might introduce undesired sharing on Tasks running in parallel, that should be isolated. I don't think our test suite could detect that, since it mostly even doesn't use real parallelism.

As a user, I would like something that works like this:
for {
f1 <- task.start // copy "main" local but isolate for its own duration
f2 <- task.start // copy "main" local but isolate for its own duration
_  <- Task.parZip2(f1.join, f2.join) // nondeterministic local value from either f1 or f2
} yield ()

for {
 // task1 and 2 copy "main" local but their own changes are isolated until entire Task returns
_ <- Task.parZip2(task1, task2)
_ <- ... // nondeterministic value from either task1 or 2
} yield ()

But I'm not sure how to achieve it and I can probably live with what we have right now as second best. :D Though I plan to play a bit in following days to make sure I can use it the way I would like to

// nondeterministic local value from either f1 or f2

I think that's problematic if your main fiber also interacts with locals before joining. You would lose all writes between start-join and would be forced to isolate join explicitly to avoid this.
In my (very small, mind you) experience with TaskLocal, it's best to write locals at the top level and only read or, worst case, bind them in layers below. I also think "stuff is shared unless said otherwise" is an okay model for reasoning about fibers and parXXX methods.
And with typelevel mouse and/or scala 2.13 you can use some chaining syntax to make it both more visible and convenient:
import TaskLocal.isolate
for {
f1 <- task.start |> isolate
f2 <- task.start |> isolate
_  <- Task.parZip2(f1.join, f2.join)
} yield ()

We can also have a helper like .startIsolated as a shorthand for that if we want to.

@Avasil is this PR still relevant?

@Avasil is this PR still relevant?

I think we actually had a use case for a flag in memoize and evalAsync so might be not relevant.


Update 3.1 Interop - IS-04

Add more detail on the equivalence between Connection API /active parameters and Node API subscription attributes

Is it worth tweaking the page title and filename so it isn't called "NMOS IS-04" as well? 😬


Fabric CA with postgres DB:  register new user fails with Authorization failure

We have TLS CA and Organization CA(Root CA).
Configuration of TLS CA with postgres DB instance went fine. We are able to bootstrap admin and register our identities.
When configuring Organization CA, we are connecting to the same Postgres DB instance which is used by TLS CA.
We are able to bootstrap admin.
When registering a new user, it fails with "Authorization failure".
If we configure Org CA with a different postgres DB instance then register/enroll of new user goes fine.
Is there any restriction on having dedicated postgres DB for TLS CA and Org CA servers ?

I see an opportunity here for adding points in Fabric CA documentation. Based on our community review, I will take required inputs and push appropriate changes in Fabric CA guides.


Embed executable code inside of exercise solutions

In #18 @jstac brought up a good point that it is quite common to want executable code in the solutions to your exercises. Right now this isn't possible with {code-cell} because this breaks the flat cell structure that Jupyter Notebooks enforce.
This is an issue to brainstorm how to get this working!
Some options
Use start/stop directives for solutions
As @chrisjsewell suggests, we could provide another directive here that would mark the start/stop of a solution. Something like:
```{solution-start}
```
Intro to solution

```{code-cell}
print(2+2)
```

```{solution-stop}
```

Improve cell copy/pasting functionality to make this easier
If we improved the cell copy/pasting functionality we could do something like:
% This code cell would be executed
```{code-cell}
:tags: remove-cell
:name: solution1
print(2+2)
```

% And here it'd be placed inside the solution block
````{solution}
```{ipynb:cell} solution1
```
````

Recommend jupyter-sphinx for solutions/exercises
As long as the code in the solution doesn't require the state of the kernel that came from running any previous code, then jupyter-sphinx should work just fine here. What won't work is if we define variables earlier in the page and then want to reference those variables in the solution.
What other ideas are out there?

Thanks for opening @choldgraf .
I would find option 1 easier to remember.
One related alternative would be to replace solution-start with solution-header and drop solution-stop.
Then the only think that's being inserted is a heading that tells us what exercise is being solved, while the contents of the solution is just ordinary notebook content.
I suppose the exercise could be symmetric, with exercise-header inserting "Exercise x", typeset nicely as determined by the extension, and the content of the exercise again being ordinary notebook content underneath the header.

These are great suggestions @choldgraf @jstac.
Just to double check, it wouldn't be possible to automate the "gluing" functionality so that whenever a code-cell is introduced in the content of the directive, it is replaced with a code block and the output of the code-cell - which can be added at the bottom of the document with a remove-cell tag - is glued in the directive?
The only issue I have with @jstac's solution-header suggestion is that we wouldn't be able to duplicate/copy solutions to another location as suggested in issue #11.

One related alternative would be to replace solution-start with solution-header and drop solution-stop.

One downside here would be if you wanted to apply styling to the solution text (i.e. in similar fashion to an admonition). I think it would be useful to have a end demarcation so that the solution block is identified in the ast.
This is actually similar to the root issue behind https://github.com/executablebooks/MyST-NB/issues/274. The motivation behind this request is to be able to bring in code from a file (as used to be done with literalinclude) but jupytext (rightly) has no knowledge of anything outside of code-cell breaks.
I am in favour of option1 style approach to this -- mainly because the content stays ordered. If we introduce jupytext filters as a way to update content such as links to a website (instead of to other notebooks) to support download notebooks for websites then having notebooks with content in the correct order will make this work easier.

Could we simplify the solution directive to be:
```{solution} <name>
```

<Content of Solution>

```{solution} <name>
```

which would require named boundaries. Would be a bit harder to code -- but would be easier to write at the user level.

Thanks for your thoughts @mmcky .
As a user, I would be happy enough with the original option 1, although I do see your point about other nested code cells and the need for a consistent approach.  Option 1 doesn't feel consistent with the rest of myst.

Hi guys, tossing out an alternative option: How about we use tabs?  (as in https://jupyterbook.org/content/content-blocks.html#tabbed-content)
One tab is "Exercise X" and the other tab, with content initially hidden, is "Solution".

hey @jstac this is a nice format option -- I like it. I think we will still get issues with executing the nested code-blocks (cc: @chrisjsewell) as it breaks the linear document jupyter notebook rule for the code-blocks though.

I wonder if we could have tabbed code blocks in jupyter notebooks which had an execution rule of left to right. This would then directly translate to the notebooks format but this would essentially require a jupyter extension I think to change the base jupyter notebook format.

Just a note as well that we can always use jupyter-sphinx to execute and embed outputs in the built docs, and we can embed jupyter-sphinx execution inside of admonitions, tabs, etc. The only challenge is that jupyter-sphinx won't have access to the same kernel that jupyter-cache uses when it executes the notebook. But this might still work for certain kinds of exercises.

thanks @choldgraf -- that is a thought I had as well and might be the best we can do (unless jupyter-cache implements something like pre-execution filters/transforms). My concern though is the document will necessarily need more imports and it "looks" like it would flow through the document linearly -- when in fact execution is not. It also complicates the production of support download notebooks.
In sphinxcontrib-jupyter the code-block (nestedness) was ignored and a code-cell block would just be written following the exercise but we can't do that here as the action takes place in jupyter-cache first.
What do you think about a jupyter-cache  transform that could look for any nested code-cells and promote them to be code-cells where they occur:

If the the {code-cell} occurs in a markdown block it would (a) split the markdown block, (b) copy the contents of code-cell to a code-cell in the notebook json, (b) remove the {code-cell} from the text.

Given there is no real translation just a simple parse task -- this may have some merit.

@choldgraf just to clarify one point on your suggestion. Would all the jupyter-sphinx directives be executed by the same independent kernel (at the file level)?
Perhaps we can introduce an {exercise-code} node that uses jupyter-sphinx under the hood
Then we can add support for hidden etc. so that you could have a preamble / import blocks for all exercises that doesn't show in outputs. We could also support future features like exercise/solution notebooks. From a user perspective I think it would be really confusing to be able to use jupyter-sphinx but not code-cell so perhaps exercise-code would make that relationship clearer at the expense of being a lightweight wrapper.
One con however is that these nodes require sphinx to be interpreted / executed -- so if we are to support download notebooks for websites (or binder / runnable notebooks) it will be difficult to have these nested items supported in any way in the notebook format.

I think exercise-code could be a good way to make it explicit. Your point about not having the same structure when you export to ipynb is precisely the challenge here, I think. Jupyter cache wants to have the exact same notebook in the cached and “source” version, which is why I believe @chrisjsewell has pushed back on requests to transform the content of a source file (like by in-nesting) in order to be executable as a notebook.
Longer term, I feel like we’re really going to need to come up with some kind of story for the non-linear (eg nested) execution workflow. It’s common and popular in R, and many services nowadays are supporting this kind of thing. I still wonder if we can accomplish this with improving the UX around glue-like functionality 🤔🤔🤔

@choldgraf @chrisjsewell I am going to dive into this issue. I think using this as a prototype to figure out the best way to setup nested code will be useful case study to discuss the broader issue of nested code-cells in jupyterbook. Perhaps once a prototype is up and running we can all catchup on a technical workshop style meeting to see if we like it or can think of a better solution.
I will work with @chrisjsewell suggestion of using directives to indicate a start and stop while keeping code-cell at the root level for compatibility with myst and jupytext etc.
Such as:

```{solution} start
```

Content

```{solution} end
```

I plan to try using arguments to the solution directive as that might be more robust for adding other options down the track.

@AakashGfude thanks for the brainstorming today. It looks like we could support styling only through the use of visit_solution_start and visit_solution_end nodes injecting updates to html and latex but it will be difficult to support features like hidden.
I think we will need to some parsing of the doctree to support a full suite of features.
Perhaps we should use a transform to alter the tree (early on in the parsing) to build a child relationship with nodes that are contained between solution-start and solution-end. But this transform would have to occur after md -> ipynb to be fully compliant with jupytext etc.

I have now setup an working prototype of this idea for sphinx-exercise
https://github.com/executablebooks/sphinx-exercise/pull/45
I quite like the gated directive approach as it tends to simplify the syntax (when compared with nested structures) at the cost of searching from -start and -end components.


Add Android APK for Silero VAD

https://github.com/k2-fsa/sherpa-onnx/releases/download/v1.7.18/sherpa-onnx-1.7.18-arm64-v8a-silero-vad.apk

Here are some screenshots:

Home page
Speech detected state
Idle state

Analysis of the generated APK:


add justitia nsdi22

Where is the PDF?

Are you referring to the camera-ready pdf? I thought we should wait until NSDI posts it first.

Why? It's already on my website and Brent's website. We want to people to read it, not wonder what it might be.

Got it. Submitted another request to add the pdf and code link in.


Avoid using lookupByKey to check if an Instrument version exists

Consider to remove or replace it with Daml 3.


move: versioned toolchain compilation to verify source

Description
Implements versioned toolchain builds to verify bytecode when publishing packages. That is, on publish, verifies package dependencies and compiles modules with prior compiler versions if needed.
Currently guarded by VERIFIED_SOURCE_BUILD, see inline comments for discussion.
This PR maybe looks more intimidating than it really is 🙂 All changes are confined to lib.rs in the sui-source-validation crate and basically only additive changes.
Here's what it looks like when publishing a package that requires downloading a prior sui binary:

The same as above, but when the binary is already downloaded:

Test Plan
Added a test that requires a dep to compile with the current compiler by reading from Move.lock. Supporting a prior compiler is TBD. All new functionality gated for now by VERIFIED_SOURCE_BUILD

If your changes are not user-facing and do not break anything, you can skip the following section. Otherwise, please briefly describe what has changed under the Release Notes section.
Type of Change (Check all that apply)

[ ] protocol change
[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes

Okay
On Thu, Jan 18, 2024, 4:36 AM Rijnard van Tonder @.***>
wrote:

@.**** commented on this pull request.
In crates/sui-source-validation/src/lib.rs
https://github.com/MystenLabs/sui/pull/15731#discussion_r1456807815:

@@ -58,6 +86,9 @@ pub enum SourceVerificationError {
module: Symbol,
},

#[error("Cannot check local module for {module}: {message}")]

2240ef2
https://github.com/MystenLabs/sui/commit/2240ef2ca2dd5eb87fc9a7e9103e421427e07390
—
Reply to this email directly, view it on GitHub
https://github.com/MystenLabs/sui/pull/15731#discussion_r1456807815, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/A66IW4Y7RLFH6NSWRUZEMQLYPCKFJAVCNFSM6AAAAABB5VK4SCVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMYTQMRYGY4DMMBZGE
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

Thanks for the detailed review @amnn 🙏 ! Busy checking off remaining items and will then re-request review

[ ] sandbox dependency builds
[ ] auto-downloader escape hatch / messaging

I may bundle or put up separate PRs for:

[ ] lock file hygiene and checks
[ ] optimize caching current compiler binary

The current approach is accidentally quadratic in how it handles dependencies. This may also be an acceptable trade-off to begin with?.

Not sure we have an out-of-box solution to work around this one (I will leave this to @tnowacki  / @cgswords to comment on). Tradeoff seems reasonable to me.


feat: adapt active learning with small-text example to recent argilla version

Description
This PR solves #3442 in which two notebooks should be updated. In the respective issue I just wanted to raise the small-text version since there have been new features, and more importantly, some bug fixes in small-text.
In the course of updating this, I noticed that the notebooks seemed to have issues when used with a recent argilla version:

a legacy warning regarding rg.configure_dataset()
an error regarding TextClassificationRecord which was passed ids of type np.int64, which seems to have become stricter and now requires int.

This could have been done in two three PRs but since it needs manual testing afterwards I decided to count it as "one update".  I hope you are okay with this ;). Edit: I made separate entries in CHANGELOG.md. Feel free to rewrite/change it back.
The following two notebooks were updated:

tutorials/notebooks/training-textclassification-smalltext-activelearning.ipynb
tutorials/notebooks/deploying-textclassification-colab-activelearning.ipynb

Changes:

Raised small-text version
Replaced the call to rg.configure_dataset() with rg.configure_dataset_settings()
Changed ids to be of type int
Dataset name (i.e. the "project" in argilla) now uses hyphens instead of underscores to keep it consistent with the default project in hugging spaces' argilla template.

Closes #3442
Type of change

[x] Improvement (change adding some improvement to an existing functionality)

How Has This Been Tested

training-textclassification-smalltext-activelearning.ipynb has been tested with a local Jupyterlab against a Hugging Face Spaces argilla instance.
deploying-textclassification-colab-activelearning.ipynp has been testen in Google Colab (as it is required).

Checklist

[ ] I added relevant documentation
[ ] I followed the style guidelines of this project (<-- where?)
[x] I did a self-review of my code
[ ] I made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I filled out the contributor form (see text above)
[x] I have added relevant notes to the CHANGELOG.md file (See https://keepachangelog.com/)

I forgot:
For deploying-textclassification-colab-activelearning.ipynp the required command argilla server start did not seem to be enough. I had to run two commands before that: argilla server database migrate and argilla server database users create_default to get it working.
Not sure if this was my fault or if is it missing in the notebook description.


Validation of project information not implemented in ProjectInformationView

Describe the bug
The user input of the project title and description validation are not properly implemented although it is indicated that there is a validation (reset of component error is done but it is never created). Furthermore, the button activation/deactivation logic is not properly implemented
To Reproduce
Steps to reproduce the behavior:

Enter a project title or project description
Click somewhere in the view
Observe the "next" button is activated
Delete the text again
Observe that there is no component error and the button is still activated

Expected behavior
The next button should only be activated if the project description and the project title (both are required) are entered by the user (valid text inputs). If the user e.g. deletes the input of one of the fields also the next button should be disabled

 Validation of project information not implemented in ProjectInformationView #488


Update Styles as per basic preview

Tried to understand few things,

We now load the preview after the images are loaded.
Change top scroll position
If it has been tested already, then it looks good to me.

@LokeshNSF

No, Instead of loading preview with LWC styling, now we load basic VS Code default style. I have added a few custom CSS for custom plugins components.
Initially when we were typing something in the editor people were experiencing some odd flickering. This was fixed in this PR.

All the changes are verified by Prabhav.


[IMPORTANT/bp/1.29] Multiple CVEs

CVE-2024-45808: Malicious log injection via access logs
CVE-2024-45806: Potential manipulate x-envoy headers from external sources
CVE-2024-45809: Jwt filter crash in the clear route cache with remote JWKs
CVE-2024-45810: Envoy crashes for LocalReply in http async client

closing in favour of https://github.com/envoyproxy/envoy/pull/36214
it was taking too long - so probs better to just land with the release


Add configurable proxy IP and port to realize the linkage between IAST and DAST

Preflight Checklist

[X] I agree to follow the Code of Conduct that this project adheres to.
[X] I have searched the issue tracker for an issue that matches the one I want to file, without success.

Problem Description
Add configurable proxy IP and port to realize the linkage between IAST and DAST
新增对agent可配置的代理ip和端口，实现IAST 和DAST的联动。
Proposed Solution
Realize the outgoing traffic and hit the self-realized DAST within the enterprise
实现流量的外发，打到企业内部自实现的DAST
Alternatives Considered
No response
Additional Information
No response

We have successfully integrated DongTai IAST and X-Ray, for further information please refer to the following two articles:

https://i0x0fy4ibf.feishu.cn/docx/X51kdnWmRoVbu8xPNtWcsNAynTg
https://i0x0fy4ibf.feishu.cn/wiki/wikcn9hKakyNnTOaul4E89vMblh

As for other DAST tools, they can be adapted by referencing the project https://github.com/HXSecurity/Dongtai_USB.


Fix: bugs

09/06/23

Show no results found for stock images
show default stock images when no keyword is in search bar
fix loader to have a better scrolling ux
fix duplicate of grouped images
add sample images api

12/06/23

Image fits in canvas when adding from add dropdown
New fix for multiple bg on adding stock images as bg
New fix for duplicate of grouped images

Multiple layer on quick click on stock images or category images in remove background panel issue still not fixed. Will be fixed in another PR


Run npm start with error

Important：Please file the issue follow the template, or we won't help you to solve the problem.

0. Report Issue Guide

Please run the following command and check whether the problem has been fixed：

rm -rf package-lock.json
rm -rf node_modules
npm install

Please search in FAQ List first, and make sure your problem has not been solved before.

Please search in the issue first, and make sure your problem had not been reported before

1. Versions

What is your wechaty version?
Answer: 1.13.7

Which puppet are you using for wechaty? (padchat/puppeteer/padpro/...)
Answer: padchat

What is your wechaty-puppet-XXX（padchat/puppeteer/） version?
Answer: padlocal

What is your node version? (run node --version)
Answer: v16.14.0

What os are you using
Answer: macos

2. Describe the bug
surprisedly, I can't run the npm start successfully after struggling several hours.
3. To Reproduce
This part is very important: if you can not provide any reproduce steps, then the problem will be very hard to be recognized.
Steps to reproduce the behavior:

git clone https://github.com/wechaty/getting-started.git
cd getting-started
npm install
export WECHATY_LOG=verbose
export WECHATY_PUPPET=wechaty-puppet-wechat
npm start

4. Expected behavior
Of course,I expect the qrcode
5. Actual behavior
(base) bogon:getting-started sunny$ npm start

><EMAIL_ADDRESS>start
> cross-env NODE_OPTIONS="--no-warnings --loader=ts-node/esm" node examples/ding-dong-bot.ts

node:internal/errors:464
    ErrorCaptureStackTrace(err);
    ^

Error [ERR_UNSUPPORTED_DIR_IMPORT]: Directory import '/Users/sunny/Javascript/getting-started/node_modules/ts-node/esm' is not supported resolving ES modules imported from /Users/sunny/Javascript/getting-started/
    at new NodeError (node:internal/errors:371:5)
    at finalizeResolution (node:internal/modules/esm/resolve:414:17)
    at moduleResolve (node:internal/modules/esm/resolve:981:10)
    at defaultResolve (node:internal/modules/esm/resolve:1078:11)
    at ESMLoader.resolve (node:internal/modules/esm/loader:530:30)
    at ESMLoader.getModuleJob (node:internal/modules/esm/loader:251:18)
    at ESMLoader.import (node:internal/modules/esm/loader:332:22)
    at initializeLoader (node:internal/process/esm_loader:74:49)
    at loadESM (node:internal/process/esm_loader:87:11)
    at runMainESM (node:internal/modules/run_main:51:21) {
  code: 'ERR_UNSUPPORTED_DIR_IMPORT',
  url: 'file:///Users/sunny/Javascript/getting-started/node_modules/ts-node/esm'
}

6. Full Output Logs
Set env WECHATY_LOG=silly in order to set log level to silly, then we can get the full log (If you dosen't set log env, log level is info as default, we cannot get the full log)
We need full log instead of log screenshot or log fragments!

Show Logs

$ WECHATY_LOG=silly node yourbot.js

Question: Paste your FULL(DO NOT ONLY PROVIDE FRAGMENTS) log messages
Answer:

7. Additional context
Add any other context about the problem here.
太难了，一万多star的项目，为何跑不起来，我太难了
[bug]

我也跑不起来，去他说那个平台也打不开，demo 扔到编辑器上就爆红不知道他怎们写的

npm i 出现错误我也服了不能排除下代码吗我们也没白嫖

哈哈，似乎已经没人维护了，，别打微信的注意了，

npm i 出现错误我也服了不能排除下代码吗我们也没白嫖

Close this issue because it's off topic.


Standardise draw/modify descriptions

Modify at the moment might mislead, as it implies that it can also modify feature attributes. I was going to change select interaction as well ('Interaction for selecting vector features'), but that would conflict with #3758, so I'll leave that for the moment.

Thanks @probins!


Fixing empty sentence handling for chunk-based translation

Empty sentences were getting ids relative to the position in the current chunk, instead of absolute sentences ids. This could sometimes (more probable for inputs with many empty lines) result in an incorrect ordering during later collection of translated chunks into outputs that is based on sentence- and chunk-ids.
Fixes #477
Pull Request Checklist

[x] Changes are complete (if posting work-in-progress code, prefix your pull request title with '[WIP]'
until you can check this box.
[x] Unit tests pass (pytest)
[x] System tests pass (pytest test/system)
[x] Passed code style checking (./style-check.sh)
[x] You have considered writing a test
[x] Updated major/minor version in sockeye/__init__.py. Major version bump if this is a backwards incompatible change.
[x] Updated CHANGELOG.md

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

let's fix Travis and then merge.


Development

@rielas Can you please help with resolving the charts conflicts here?

@rielas Can you please help with resolving the charts conflicts here?

Resolved

@tamirGer When are you going to merge development into master? It has a lot of helm-related changes


Docker Quickstart - Pulling datahub-actions in error

Hi!
I have this error message when I launch quickstart command.
datahub docker quickstart
(I launched it yesterday without any problem)
It seems related to the image pull of datahub-actions:
ERROR: for datahub-actions  failed to register layer: error creating overlay mount to /var/lib/docker/overlay2/8e4a978b78ea7e210f5feb6cc5d864ca03ed1cc652bde6a0a6e0772fb1ab71b2/merged: too many levels of symbolic links ERROR: failed to register layer: error creating overlay mount to /var/lib/docker/overlay2/8e4a978b78ea7e210f5feb6cc5d864ca03ed1cc652bde6a0a6e0772fb1ab71b2/merged: too many levels of symbolic links Error while pulling images. Going to attempt to move on to docker-compose up assuming the images have been built locally

Thank you for your help!

If I try to change in the docker-compose quickstart file, the tag of datahub-actions image (acryldata/datahub-actions:v.0.0.5). It works, so maybe there's a problem with the new version of the image.

@matwalk

Can you please confirm if this is working for you now with latest CLI versions?
If not working even now, can you please share the environment details? Which OS? What version?
Can you provide output of these commands

python -c "import platform; print(platform.platform())"
python -c "import sys; print(sys.version); print(sys.executable); import datahub; print(datahub.__file__); print(datahub.__version__);"

Can you provide the output of

docker ps -a


Nested views ad infinitum

Hello,
Hope you're well! This is a great library! I was wondering if it was possible to use it to create nested views continuously without predefining the layout. So given an initial view, the user clicks a button to split it in half. Given the two new views, the user can click a same button to split it etc.
Thanks!

It's an interesting problem! Without reviewing the more specific issue you raised later, I put this together as an attempt to capture what you specified. If you use a DynamicSplit(), it shows a "Split" button that increments the nSplits state to redraw the view. The starting NestedHSplit recursively creates alternating NestedVSplits and NestedHSplits until the passed-in nSplits is 0. If you need to retain the split state, I would use a property based on the value of nSplits at each instantiation.
struct DynamicSplit: View {
    @State var nSplits: Int = 0
    var body: some View {
        VStack {
            let primordialView = Color.red
            let newView = Color.green
            Button("Split") { nSplits += 1 }
            if nSplits > 0 {
                NestedHSplit(nSplits: nSplits, primary: { primordialView }, secondary: { newView })
            } else {
                primordialView
            }
        }
    }

}

struct NestedHSplit<P: View, S : View>: View {
    let nSplits: Int
    var primary: P
    var secondary: S

    var body: some View {
        if nSplits == 0 {
            primary
        } else {
            primary.hSplit { NestedVSplit(nSplits: nSplits - 1, primary: { secondary }, secondary: { primary } ) }
        }
    }

    init(nSplits: Int, @ViewBuilder primary: @escaping ()->P, @ViewBuilder secondary: @escaping ()->S ) {
        self.nSplits = nSplits
        self.primary = primary()
        self.secondary = secondary()
    }
}

struct NestedVSplit<P: View, S : View>: View {
    let nSplits: Int
    var primary: P
    var secondary: S

    var body: some View {
        if nSplits == 0 {
            primary
        } else {
            primary.vSplit { NestedHSplit(nSplits: nSplits - 1, primary: { secondary }, secondary: { primary } ) }
        }
    }

    init(nSplits: Int, @ViewBuilder primary: @escaping ()->P, @ViewBuilder secondary: @escaping ()->S ) {
        self.nSplits = nSplits
        self.primary = primary()
        self.secondary = secondary()
    }
}

That works perfectly, thank you! Will modify it to behavior closer to Xcode's split pane behavior. Also greetings from Palo Alto!

Feel free to re-open if needed.


Spring Framework / Spring Boot supports

What is the purpose of the change

Bugfix : Legacy Spring annotation-driven issues on placeholder.
Refactor: The binder for Dubbo's config beans in order to adapter for Spring Framework and Spring Boot 1.x/2.0
Enhancement : Extraction of the Ops methods for Spring Boot Acutator

Brief changelog

[Enhancement] placeholder supports on Dubbo Annotation #1317
[Enhancement] Add configuration properties of binder for Dubbo's config beans #1464
[Enhancement] Dubbo Config Bindings supports customized DataBinder #1278
[Refactor] ReferenceAnnotationBeanPostProcessor add Ops methods #1277

Verifying this change
Run test-cases
Follow this checklist to help us incorporate your contribution quickly and easily:

[x] Make sure there is a GITHUB_issue filed for the change (usually before you start working on it). Trivial changes like typos do not require a GITHUB issue. Your pull request should address just this issue, without pulling in other changes - one PR resolves one issue.
[ ] Format the pull request title like [Dubbo-XXX] Fix UnknownException when host config not exist. Each commit in the pull request should have a meaningful subject line and body.
[ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why.
[ ] Write necessary unit-test to verify your logic correction, more mock a little better when cross module dependency exist. If the new feature or significant change is committed, please remember to add integration-test in test module.
[ ] Run mvn clean install -DskipITs to make sure unit-test pass. Run mvn clean test-compile failsafe:integration-test  to make sure integration-test pass.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

Codecov Report

Merging #1534 into 2.5.x will decrease coverage by 1.86%.
The diff coverage is 83.53%.

@@            Coverage Diff             @@
##            2.5.x    #1534      +/-   ##
==========================================
- Coverage   30.39%   28.52%   -1.87%
==========================================
  Files         879      798      -81
  Lines       45519    41851    -3668
  Branches     9451     8542     -909
==========================================
- Hits        13834    11940    -1894
+ Misses      29399    27832    -1567
+ Partials     2286     2079     -207

Impacted Files
Coverage Δ

...g/convert/converter/StringArrayToMapConverter.java
100% <100%> (ø)

...beans/factory/annotation/ReferenceBeanBuilder.java
87.5% <100%> (+3.12%)
:arrow_up:

...onvert/converter/StringArrayToStringConverter.java
100% <100%> (ø)

...ontext/annotation/DubboConfigBindingRegistrar.java
92.72% <100%> (-0.03%)
:arrow_down:

...dubbo/config/spring/util/PropertySourcesUtils.java
84.61% <100%> (+1.28%)
:arrow_up:

...annotation/ServiceAnnotationBeanPostProcessor.java
85.18% <100%> (+0.33%)
:arrow_up:

...g/context/properties/DefaultDubboConfigBinder.java
100% <100%> (ø)

.../alibaba/dubbo/config/spring/util/ObjectUtils.java
50% <50%> (ø)

...ry/annotation/AnnotationPropertyValuesAdapter.java
62.5% <62.5%> (ø)

...nnotation/DubboConfigBindingBeanPostProcessor.java
67.5% <63.63%> (-26.25%)
:arrow_down:

... and 139 more

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 4f34540...1e5b28f. Read the comment docs.


[test] Disable parse_stdlib tests on Mac too

We're running out of memory there as well. Fixing this is tracked by rdar://problem/34771322.

@swift-ci Please smoke test and merge


Meet 429 error when using chat

I can use chatgpt in the webpage. But when using it in obsidian. A 429 error returns

Strange 429 usually means too many requests, which is unlikely that you would achieve that on your own.
Does the error still happen? Is the api key configured correctly?
Otherwise try to install chatgpt-md in a sandbox vault and compare if it works there.

Hi @WystanW,
@lukemt is correct. 429 is an OpenAI error b/w them and client (you). Try through the UI (platform.openai.com) and see if you get a 429 there too.


Can't expand all groups

How can I expand all groups?

Go through this https://github.com/thoughtbot/expandable-recycler-view/issues/54#issuecomment-284171806


[Bug]: Structure comparison will only display the first task when opening details

ODC version
odc424
OB version

What happened?
https://github.com/oceanbase/odc/assets/143492234/399bc4aa-c732-4b1b-8af1-55c384b47c08
https://github.com/oceanbase/odc/assets/143492234/fcf9944d-ecd4-4268-ab7f-2a9c84b30e56
What did you expect to happen?
Normal display task
How can we reproduce it (as minimally and precisely as possible)?
View details of structural comparison task
Anything else we need to know?
No response
Cloud
No response

Fixed In Commit 017dccc99e78bc533f08e6786864e4dad6088ad4
------
陈朝俊
Mon Mar 25 17:22:08 2024 +0800

pass


Parsing devices fails on Xcode 15.3

When parsing the device list the parsing fails because the dataPathSize field seems to be missing when running a simulator from Xcode 15.3.

Awesome! Thanks @aegzorz
I'm going to tag it later this week.

Awesome! Thanks @aegzorz I'm going to tag it later this week.

Nice! 🙌

This has been included in #16 use tag 1.1.0-beta.2 to try it out


Backmerge release 2.16.0

Release: https://github.com/safe-global/safe-config-service/releases/tag/v2.16.0

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 99.207%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
876

Relevant Lines:
883

💛  - Coveralls


Don't detect trait "use ..." statements in filtered-out classes

Closes #204

:+1:

Thank you @aik099.


Torch not compiled with CUDA enabled

I am trying to test the tool but after running the installation process it does not work when I click on generate.
In the console an exception is raised on cuda initialization (Torch not compiled with CUDA enabled)
My card is a 3080 with 10GB.
Below I attach the full log after running gradio app
(tooncrafter) C:\Users\user\dev\ToonCrafter>python gradio_app.py
WARNING[XFORMERS]: xFormers can't load C++/CUDA extensions. xFormers was built for:
    PyTorch 2.0.0+cu118 with CUDA 1108 (you have 2.0.0+cpu)
    Python  3.8.10 (you have 3.8.5)
  Please reinstall xformers (see https://github.com/facebookresearch/xformers#installing-xformers)
  Memory-efficient attention, SwiGLU, sparse and more won't be available.
  Set XFORMERS_MORE_DETAILS=1 for more details
AE working on z of shape (1, 4, 32, 32) = 4096 dimensions.
checkpoints/tooncrafter_512_interp_v1/model.ckpt
>>> model checkpoint loaded.
Running on local URL:  http://<IP_ADDRESS>:7860

To create a public link, set `share=True` in `launch()`.
Global seed set to 123
start: talking man 2024-06-07 23:46:38
Traceback (most recent call last):
  File "C:\Users\user\miniconda3\envs\tooncrafter\lib\site-packages\gradio\queueing.py", line 532, in process_events
    response = await route_utils.call_process_api(
  File "C:\Users\user\miniconda3\envs\tooncrafter\lib\site-packages\gradio\route_utils.py", line 276, in call_process_api
    output = await app.get_blocks().process_api(
  File "C:\Users\user\miniconda3\envs\tooncrafter\lib\site-packages\gradio\blocks.py", line 1923, in process_api
    result = await self.call_function(
  File "C:\Users\user\miniconda3\envs\tooncrafter\lib\site-packages\gradio\blocks.py", line 1509, in call_function
    prediction = await anyio.to_thread.run_sync(
  File "C:\Users\user\miniconda3\envs\tooncrafter\lib\site-packages\anyio\to_thread.py", line 56, in run_sync
    return await get_async_backend().run_sync_in_worker_thread(
  File "C:\Users\user\miniconda3\envs\tooncrafter\lib\site-packages\anyio\_backends\_asyncio.py", line 2177, in run_sync_in_worker_thread
    return await future
  File "C:\Users\user\miniconda3\envs\tooncrafter\lib\site-packages\anyio\_backends\_asyncio.py", line 859, in run
    result = context.run(func, *args)
  File "C:\Users\user\miniconda3\envs\tooncrafter\lib\site-packages\gradio\utils.py", line 832, in wrapper
    response = f(*args, **kwargs)
  File "C:\Users\user\dev\ToonCrafter\scripts\gradio\i2v_test_application.py", line 51, in get_image
    model = model.cuda()
  File "C:\Users\user\miniconda3\envs\tooncrafter\lib\site-packages\lightning_fabric\utilities\device_dtype_mixin.py", line 69, in cuda
    device = torch.device("cuda", torch.cuda.current_device())
  File "C:\Users\user\miniconda3\envs\tooncrafter\lib\site-packages\torch\cuda\__init__.py", line 674, in current_device
    _lazy_init()
  File "C:\Users\user\miniconda3\envs\tooncrafter\lib\site-packages\torch\cuda\__init__.py", line 239, in _lazy_init
    raise AssertionError("Torch not compiled with CUDA enabled")
AssertionError: Torch not compiled with CUDA enabled

I am trying on the same... but something doesn't add up for me.
this will give you the torch with cuda
pip install torch==2.0.0+cu117 torchvision==0.15.0+cu117 torchaudio==2.0.0+cu117 -f https://download.pytorch.org/whl/cu117/torch_stable.html
pip install transformers==4.25.1
AND
pip install -U xformers --index-url https://download.pytorch.org/whl/cu20
That completes the setup BUT every time I run the generate my PC freezes and I need to hard reboot.
I suspect 2 reasons, but can't confirm yet: Nvidia driver 555.85 and potentially Windows (because Triton, which is another GPU optimizer, that doesn't support Windows )
I will try on WSL.

wget https://repo.anaconda.com/miniconda/Miniconda3-latest-Linux-x86_64.sh && bash Miniconda3-latest-Linux-x86_64.sh
eval "$(/home/YOUR-USERNAME/miniconda3/bin/conda shell.bash hook)" && conda init && source ~/.bashrc
conda create -n tooncrafter python=3.8.5 && conda activate tooncrafter
sudo apt update && sudo apt install nvidia-cuda-toolkit
git clone https://github.com/ToonCrafter/ToonCrafter.git && cd ToonCrafter
pip install -r requirements.txt
python gradio_app.py

Also ...
Keep in mind, I just saw - A100 is required with the default model...
https://github.com/ToonCrafter/ToonCrafter/issues/28

I dont know why but xformers, so i kill it and use standard vae decode, i use this command F:\AI\Comfy2\ComfyUI_windows_portable\python_embeded\python.exe -m pip uninstall xformers

You need to install pytorch with your GPU. This is a common issue with pytorch, and reinstalling pytorch on the gpu instead of the cpu will likely resolve this specific issue.
Reading from https://pytorch.org/, you are on windows, so you can probably run (not tested):
python -m pip install torch=2.0.0 torchvision --index-url https://download.pytorch.org/whl/cu118

You might need to find the version for torchvision as well, I don't remember which version was compatible with torch==2.0.0 on python 3.8.

I encountered the same bug while reinstalling xformers, which consistently conflicted with torch, torchaudio, and torchvision. To resolve this, I used the following command:
pip install xformers==0.0.22.post2 --index-url https://download.pytorch.org/whl/cu118
I also reinstalled torch, torchaudio, and torchvision, or they might have been installed during the xformers installation. I can't recall precisely. For reference, here is the final combination that worked for me (though it still has errors while generating videos, but at least it runs):

torch: 2.1.0+cu118i
torchaudio: 2.0.2+cu118
torchvision: 0.15.2+cu118
xformers: 0.0.22.post2+cu118


System crash with CPU error after plug in the realsense sr300 camera

Required Info

Camera Model
SR300

Firmware Version
<IP_ADDRESS>

Operating System & Version
16.04.02

Kernel Version (Linux Only)
<IP_ADDRESS>-generic

Build System
Makefile

My camera works well on 14.04, I meet this problem after I switch to 16.04.
Before I insert the patched uvcvideo module I meet the problem described in issue  #175, but except the depth information everything else works fine.
So I patched the module using the "patch-realsense-ubuntu-xenial.sh" script file.
The patching process ends with no error, and run sudo modprobe uvcvideo returns
[ 2007.069046] media: Linux media interface: v0.10
[ 2007.092882] Linux video capture interface: v2.00
[ 2007.142988] usbcore: registered new interface driver uvcvideo
[ 2007.142991] USB Video Class driver (1.1.1-3-realsense)

at dmesg. Util now every thing seems great. But when plug in the SR300, the system crashed. I checked the kern.log file and it looks like some CPU relevant error occur. I attach the kern.log file to help debug, and I plug in the camera at line 3769.
kern.txt
Sometime, when I reboot the computer after plug in the sr300 camera I got this messge
"Overclocking failed! Please enter Setip to re-configure your system."
I can't reproduce this error, but it happens sometime.

We never observed this behavior on any of our setups. It might be related to the specific setup. Do you have another Linux machine to test on?


correct db added

Coverage remained the same at 99.749% when pulling 95c27eebd5af87db2fba92c3cdd5c941237463e5 on hsim13372:update_files into 789da8181d44a7bcab6fa0d60f7a1c3d40cee8ac on cs207-group11:master.

Coverage remained the same at 99.749% when pulling a1c3423039ebf20a7b4818f9e06c3aa4f7cf0a92 on hsim13372:update_files into 789da8181d44a7bcab6fa0d60f7a1c3d40cee8ac on cs207-group11:master.


Oungeuaol

Oungeuaol created by<EMAIL_ADDRESS>on 2017-01-10 11:44:56

<EMAIL_ADDRESS>replied, Tekinged has "ngeuaol", also spelled "ngoaol" as a noun to mean the open ocean (more or less). Â I've come across the word "oungeuaol" which literally would mean "go to the open ocean" but appears to also have the meaning "go looking for new love somewhere else" or "stray". Â This appears to be a variation on the spelling of "ongoaol", which is in tekinged. Â I guess it would be useful to put in the variation of spelling for the verb as is done with the noun.

<EMAIL_ADDRESS>replied, that would be helpful eh Kitalong as for a non Belauan speaker, they are not acquainted with various spelling like a native tongue speaking person that would do a search typing different entries. :-) My Beliasang imol sens.


8bitify

name: 8bitify my avatar
about: A command that turns an avatar 8bit
Closes #239
Adds the cog and command

Maybe it's something for a later enhancement/refinement, but I was thinking about the possibility of adding a feature that accepts an image URL as well. That way, we could have it 8-bitify non-avatar images as well.
Not sure about the risks involved of having it access image files provided with a link, though.


Add fix_data.yaml with  first 7 fixes

Description
Replace this paragraph with a description of what this PR is doing. If you're modifying existing behavior, describe the existing behavior, how this PR is changing it, and what motivated the change. If you're changing visual properties, consider including before/after screenshots (and runnable code snippets to reproduce them).
Related Issues
Replace this paragraph with a list of issues related to this PR from our issue database. Indicate, which of these issues are resolved or fixed by this PR. There should be at least one issue listed here.
Tests
I added the following tests:
Replace this with a list of the tests that you added as part of this PR. A change in behavior with no test covering it
will likely get reverted accidentally sooner or later. PRs must include tests for all changed/updated/fixed behaviors. See Test Coverage.
Checklist
Before you create this PR, confirm that it meets all requirements listed below by checking the relevant checkboxes ([x]). This will ensure a smooth and quick review process.

[ ] I read the Contributor Guide and followed the process outlined there for submitting PRs.
[ ] I signed the CLA.
[ ] I read and followed the Flutter Style Guide, including Features we expect every widget to implement.
[ ] I read the Tree Hygiene wiki page, which explains my responsibilities.
[ ] I updated/added relevant documentation (doc comments with ///).
[ ] All existing and new tests are passing.
[ ] The analyzer (flutter analyze --flutter-repo) does not report any problems on my PR.
[ ] I am willing to follow-up on review comments in a timely manner.

Breaking Change
Did any tests fail when you ran them? Please read Handling breaking changes.

[ ] No, no existing tests failed, so this is not a breaking change.
[ ] Yes, this is a breaking change. If not, delete the remainder of this section.

[ ] I wrote a design doc: https://flutter.dev/go/template Replace this with a link to your design doc's short link
[ ] I got input from the developer relations team, specifically from: Replace with the names of who gave advice
[ ] I wrote a migration guide: https://flutter.dev/go/breaking-changes-template Replace this with a link to a pull request that adds the migration guide to https://flutter.dev/docs/release/breaking-changes

/cc @Piinks

We have to come up with a way to test these fixes. @bwilkerson Have you already given testing these definitions some thoughts?

@goderbauer do you want to move forward with this change?

The tests that need to be added here are almost the same as https://github.com/flutter/flutter/pull/72903
This change will need to land before that one.

@goderbauer do you want to move forward with this change?

Yes, I'll update this PR.

@goderbauer do you want to move forward with this change?

Yes, I'll update this PR.

Google tests have been fixed, this has a merge conflict now though. Strange Resolve conflicts is disabled here.

Google tests have been fixed, this has a merge conflict now though. Strange Resolve conflicts is disabled here.

Merge conflict is resolved.

Merge conflict is resolved.


switch to new elasticsearch-js for users things

Clearly describe the problem and solution
Relevant issue number(s) if applicable
Did you run npm run lint from the viewer or parliament directory (whichever you are making changes to) and correct any errors
Did you Ensure that all tests still pass by navigating to the tests directory and running ./tests.pl --viewer
License
I confirm that this contribution is made under an Apache 2.0 license and that I have the authority necessary to make this contribution on behalf of its copyright owner.

maybe when those apis are being moved? :) i just wanted to convert something and see about gotchas :)


Bump version

Could you bump up the package version so the mailchimp command from #4 gets published?
Also you could tag these version bump commits using the releases tag as well.
Thanks!

I don't have push access to the npm package, but I think @m-baumgartner does. fyi, I use grunt-release to make proper releases dead simple, so it takes all of 1 second to pull one with tags, version bumps, npmjs push, etc
https://github.com/geddski/grunt-release
Also, using this hubotscript generator gives you that for free when creating future scripts:
https://github.com/desmondmorris/generator-hubot-script
Cheers! :)

Or you could use Travis deployments which could automatically publish to npm on tagged commits. http://docs.travis-ci.com/user/deployment/npm/

Done.
Manually for now but that travis automation is sexy though, i'll take a look.

Alright Travis should now build and publish future versions of this package on it's own.
Plus, I added travis build status and npm version badges.


Allow viewing the source code of blocks

Description
Features
This PR adds an experimental view command that lets you view the source code of:

a block
a module
a custom command

Caveats

Currently, viewing individual blocks of export env is not possible -- you need to view the whole module. However, viewing export def and export def-env is possible (e.g., using `view "module-name def-name").
It shows only the block part. E.g., the def name [args...] parts will be lost.

Tests
Make sure you've run and fixed any issues with these commands:

[x] cargo fmt --all -- --check to check standard code formatting (cargo fmt --all applies these changes)
[x] cargo clippy --all --all-features -- -D warnings -D clippy::unwrap_used -A clippy::needless_collect to check that you're using the standard code style
[x] cargo build; cargo test --all --all-features to check that all the tests pass

“View” seems very generic choice for internal source code and might conflict in the future with some actual viewing functionality. Maybe a more explicit name like “View-source” would be better?

Ahh, I like view-source, too. Reminds me of viewing source on a webpage :grinning:


thread 'main' panicked when using optional on build

Bug Report
Version
tonic-build = "0.4"
prost-build = "0.7"

Platform
Darwin MacBook-Pro.home 20.3.0 Darwin Kernel Version 20.3.0: Thu Jan 21 00:07:06 PST 2021; root:xnu-7195.81.3~1/RELEASE_X86_64 x86_64

Description
I'm trying to add optional to a field in a message.
I looked online to see how to do so and I added the following to my build.rs thanks to https://github.com/akiradeveloper/lol/blob/master/lol-core/build.rs from https://github.com/hyperium/tonic/issues/627
fn main() -> Result<(), Box<dyn std::error::Error>> {
    let mut config = prost_build::Config::new();
    config.bytes(&[".rooms.AppendStreamEntry.command"]);
    config.protoc_arg("--experimental_allow_proto3_optional");
    tonic_build::configure().compile_with_config(config, &["proto/rooms.proto"], &["proto"])?;
    Ok(())
}

But I get the following error on cargo build
error: failed to run custom build command for `media-server v0.1.0 (/Users/...)`

Caused by:
  process didn't exit successfully: `/Users/.../target/debug/build/...-04f97c8a3b581fe0/build-script-build` (exit code: 101)
  --- stderr
  thread 'main' panicked at 'called `Option::unwrap()` on a `None` value', /Users/remikalbe/.cargo/registry/src/github.com-1ecc6299db9ec823/prost-build-0.7.0/src/code_generator.rs:259:47
  note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

Here is my proto file in proto/rooms.proto
syntax = "proto3";
package rooms;

service Rooms {
  rpc Create (Void) returns (CreateReply);
  rpc Join (JoinRequest) returns (JoinReply);
}

message Void {}

message CreateReply {
  string roomId = 1;
}

message JoinRequest {
  string roomId = 1;
  string peerId = 2;
}

message RouterRtpCapabilities {
  string kind = 1;
  string mimeType = 2;
  uint32 clockRate = 3;
  optional uint32 channels = 4;     <==========   Here is my optional field
  map<string, string> parameters = 5;
  enum RtcpFeedback {
    NACK = 0;
    NACKPLI = 1;
    CCMFIR = 2;
    GOOGREMB = 3;
    TRANSPORTCC = 4;
    UNSUPPORTED = 5;
  }
  repeated RtcpFeedback rtcpFeedback = 6;
}

message JoinReply {
  repeated RouterRtpCapabilities routerRtpCapabilities = 1;
}

If I remove the optional from my field but I keep the same build.rs I don't get any error.

Probably a bug in prost-build and not tonic https://docs.rs/prost-build/0.7.0/prost_build/
Are you able to reproduce it without tonic?

I think so as this produce the same error.
//tonic_build::configure().compile_with_config(config, &["proto/rooms.proto"], &["proto"])?;
config.compile_protos(&["proto/rooms.proto"], &["proto/"])?;

This seems to have already been reported https://github.com/danburkert/prost/issues/457, I'll close the issue.

This seems to have already been reported https://github.com/danburkert/prost/issues/457, I'll close the issue.

this link lead to 404.
https://github.com/tokio-rs/prost/issues/457


Cannot interpret 'datetime64[ns, UTC]' as a data type

Any idea when support for datetime64[ns, UTC] will be implemented ?
I get this error Cannot interpret 'datetime64[ns, UTC]' as a data type when using compare function

Happy to accept a PR for this from the community. I’ll add this to the backlog now 👍

Hi @Rstar1998, can you provide an example?
numpy had this problem in the past, but it's fixed now. see https://github.com/numpy/numpy/pull/19269
Thanks!


chore(dal): Adding integration tests for creating attribute funcs for props and sockets

@nickgerace this is the code we were just working on!

bors try

bors merge


use 2 images

can we use 2 images ? one before selection animation other after selection animation completes ??

+1

+1

+1

1

+1

+1

+1


e621 self-uploads from artists not properly parsed

When I click on the image to preview it in a larger resolution for the first time, I see the artist tag. But when the full-resolution image begins to load, it disappears. The artist tag is also not saved in the separate log file. There is no issue in saving the artist tag to the separate log file with other posts.
I am using Grabber 7.10.1 (x64) on Windows 10 Home. Not running on a virtual machine.
I am browsing through e621.net.
I notice this usually occurs with posts with the 'conditional_dnp' tag.
See the following image

These are the tags when I first open the image:

The artist tag disappears a few seconds later:

main.log attached:
main.log
settings.ini (renamed file ext with .txt because github doesn't support .ini)
settings.txt

Indeed, seems to come from this new checkmark here:

Pushing a fix now.


capnp: zero out memory of cleared pointer fields

@kentonv mentioned this to me at the 0.6 release party, and addresses an issue @abraithwaite raised to me a while back.  In read-modify-write scenarios where you are changing a pointer field, it is desirable to recursively zero out the objects formerly pointed to.  @kentonv says that it's not necessary to have the region reclaimed by the arena.  This is what the C++ implementation does.
I have two small concerns about this feature.  First, I don't see a good way of allowing a struct to be moved to a different pointer field without introducing more API (at the very least to make an explicit copy).  I don't think this is a common use case, so I don't see this as a huge deal.  Second, this is a behavior change in existing API that can only be caught at runtime.  I'm not sure whether to fix this in v2 or v3.

FWIW in C++ the way you move pointers is through the "orphan" API.
auto orphan = someStruct.disownSomeField();
someOtherStruct.adoptSomeField(kj::mv(orphan));

If an orphan goes out-of-scope without being adopted, then that's when the zeroing happens (the destructor calls a method which I named... uh... euthanize()...). So, if you just do:
someStruct.disownSomeField();

ignoring the return value, then the zeroing kicks in.
I guess in Go you don't have RAII or move semantics so you can't really copy this API directly.

Correct.  The Go API basically acts like the Orphan API in C++ at all times.  There could be a new "clear field shallowly" method and that would allow moves.  How about this set of changes:

A new DisownPtr method on Struct.  It would zero out the pointer field and return the old pointer.
A new generated struct method for each pointer field that calls DisownPtr.
Change the existing SetPtr method to do recursive clearing if a non-null value is present (breaking behavior change, but I'm unclear on how much code would be impacted).

Would SetPtr accept null as an argument, in order to recursively zero a field without setting a new value?

Yes.

Sounds reasonable.
In C++, calling disownFoo() and then ignoring the return value would end up deep-zeroing it. In Go I assume you don't have a way to detect if the return value was unused, so people will need to make some explicit call to deep-zero a pointer after it is returned.

@kentonv, how does the C++ implementation deal with clearing pointers when capabilities are involved?  Specifically, do you remove the capability from the capability table?  Seems like you can't know whether a capability index is used elsewhere without walking the whole message.

@zombiezen

For readers, the message is immutable, so there's no need to support dropping individual pointers.
For builders (which always start from scratch), the C++ implementation never uses the same index twice. This means that if a message contains two copies of the same capability (which is unusual), the cap table may have duplicate entries, but that's not a big deal.
When copying from a reader into a builder, the table indexes are re-assigned as each pointer is copied.

Acknowledged, but the crucial question in there is still: do you remove the capability from the capability table?

Yes.

Just to be clear: It would be a security problem is removing a capability from a message before sending did not actually prevent the receiver from receiving that capability.

Okay, yes, I understand now.  I'm not sure how or where to document this, but I think we need to document that Cap'n Proto read-modify-write scenarios must have a copy step for security purposes.  IIUC this is true for both C++ and Go.
If that's the case, how much do we care about the recursive zeroing?

In C++, it is not possible to read-modify-write without a copy step because you can only read into a Reader, which is immutable.
Well, OK, that's not quite true: there is an obscure API by which you can create a Builder backed by already-initialized memory. But the API is documented as being unsafe unless you trust the input, and there's no particular support for using it with messages that have capabilities (although you could build such support, but then it's up to you to get it right).

 I would open another issue for that then. This would be reasonably efficient due to the "no two pointers pointing to the same object" limitation - what I just yesterday considered a limitation seems to be a very wise decision indeed.

@KubaO A "compacting garbage collection" can already be achieved in O(n) time by making a copy of the message. Only reachable objects will be copied.


Additional checklist

https://github.com/Mic92/nixpkgs-review/blob/2661aaa1fbee70e5c3258ee9daf73bd40c9eba9b/nixpkgs_review/report.py#L124
Since this is posted on github, It would make sense to provide a default checklist of additional checks performed.
Although, arguably, if it's checklistable, it's also scriptable.
Hence, maybe provide a section for manual checks provided?
Additional manual checks completed:
- [ ] Tested all binaries in `./results/bin`
- [ ] `grep WARN ./logs/*` empty
- [ ] `grep ERR ./logs/*` empty

The intent being the reviewer could either:

complete the list locally editor result.md
or tick the boxes on github

Result could be something like: https://github.com/NixOS/nixpkgs/pull/78451#issuecomment-655088862

Superseded by #115


'dlib/opencv.h' file not found

Although I have added libdlib.a  to frameworks, the xcode still doesn't build successfully and I get a error: 'dlib/opencv.h' file not found in the FaceSwap_iOS-master/FaceSwap/FSImageUtils.mm. It is the line I include <dlib/opencv>.
I have tried put the dlib library in the same folder with the FSImageUtils.mm and it works. But when I want to build it in my iPad, it generates the new error:
Apple Mach-O Linker (ld) Error Group
1."_USER_ERROR__missing_dlib_all_source_cpp_file__OR__inconsistent_use_of_DEBUG_or_ENABLE_ASSERTS_preprocessor_directives", referenced from:
2.clang: error: linker command failed with exit code 1 (use -v to see invocation)
Any help will be appreciated!

Hmm, I've seen that somewhere else. Are you sure you have added OpenCv to it? I think it should be enough to add the unziped version of opencv2.framework.zip to frameworks.

Yes, I unzip the opencv framework and add it to the framework but the error is about the libdlib.a. It seems xcode does not correctly recognize the dlib because the error is can't find the file "dlib/opencv"

When I added the dlib framework I just dropped it manually in the root. An I think I chose "copy ... if needed" (I don't remember clearly).
I also think you might have to change some setting from debug to run for successfully running it on a device.


Sync with cloud feature hardening - 1

Issue1:
Sync content member compare(includes NetworkInterface) always fails.
Fix:
Name field in CloudResourceID holds the VM ID(resource ID), hence
use the indexer meant for matching VM ID fix in VM CRs.
While creating network interface CloudResource object, use
the right id in CloudResourceID.
Issue2:
Synchronization content is never received for AT SG.
Fix:
An example of NSG in Azure is nephe-at-per-vnet-default-archana-test-vnet-1.
Fix is related to string comaprision of SG name with "per-vnet-default".
As this is not a direct comparison, use "Contains" instead of "Compare".
Issue3:
Sync content is not received for AG SG when AT SG with same name exists.
Fix:
Irrespective of AT group names, fix creates sync content for AG.
Name collision between AG and AT group can arise when two ANP's
vm1 AT -> vm2 AG and vm2 AT -> vm1 AG exist.
Issue4:
Stale sync content received for AG SG which belong to unmanaged VPCs.
Fix:
While building CloudResource Map for ASG, it is built only for managed VPC,
however after cloud API call for getting all ASGs is made,
while processing the result, all nephe created ASGs are taken into
account even if they do not have any CloudResource member/vpc association.
Add a check to make sure ASG is associated with managed VPC and
skip ASGs associated with unmanaged VPCs.
Signed-off-by: Archana Holla<EMAIL_ADDRESS>

/nephe-test-e2e-kind, /nephe-test-e2e-aks, /nephe-test-e2e-eks

/nephe-test-e2e-kind

/nephe-test-e2e-kind


[css-paint-api] Example of passing images to the paint worklet doesn't work in Chrome

This example does not work for me in the latest Chrome.  The image stays in the 'unloaded' state indefinitely.
I'm not sure if this is a Chromium bug or  if the example is outdated.

I don’t think Properties & Values API is implemented to that extend in Chrome yet.

Oh man, too bad :(

Sooooon!


Test packaging

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 67.127%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
3466

Relevant Lines:
5026

💛  - Coveralls


Bug: backticks inside link title prevent Markdown rendering

- [relative/path/to/hello](relative/path/to/hello) : works
- [`relative/path/to/hello`](relative/path/to/hello) : does not render link

In GitHub both ways work:

relative/path/to/hello
relative/path/to/hello

It appears a Markdown parsing issue where the backticks-inside-link variant simply does not get parsed as a link

Maybe the problem is in how https://github.com/facebook/lexical/blob/d13e5b893a2113d2df08c4d69e32cb8a355a8a23/packages/lexical-markdown/src/MarkdownTransformers.ts#L357 is implemented as a text match. Within the caption, some markdown should be parsed too or at least it should still get parsed as a link (even if some formatting from the caption is discarded).

Duplicate of #5148


publish number of downloads

thses are the stats for the website visits

but the number of downloads would have to be published

turns out we would have to get the downloads from the htaccess file.


1st version

1st version

@huan Please review this PR and change commit title/content if needed, then the repo can be moved under Wechaty org.


When will the next release avaliable?

I noticeed that the lasted version 3.2.3, which was released on Apr 9, 2015. There are so many bug s fixed from that time.
I will appreciate it so much if there is a new stable release available.
@mloskot

The C++ code is ready as you have noticed.
I just have no time to get the CMake stuff updated in order to provide fully-featured CMake Config-modules for SOCI and its dependencies.
A solution could be to release CMake as it is now, but packagers may come back with lots of complains  :)

Agree with that.
Is there any plan/schedule available now?

Is there any plan/schedule available now?

No, not yet as above I've just started thinking about that idea to cut some corners. I'll see what I can achieve this week/weekend for the release.

Hi, @mloskot
Did you have an evaluation about the plan of 4.0.0?
Thanks

No, I have not managed to do anything for this yet

What's a pity.
And how about 3.2.4?

3.x line is not maintained

@mloskot
How can i help u to bring forward the progress for releasing 4.0.0. It seems there are 10 issues need to be fixed in 4.0.0.

@yxdming
I don't have time to work on any outstanding issues marked for the 4.0.0 milestone.
I can only merge PRs already submitted, but there are none waiting https://github.com/SOCI/soci/pulls?q=is%3Aopen+is%3Apr+milestone%3A4.0.0
The preparation to new release takes:

Collect release notes and update CHANGES file.
Bump versions in build scripts, documentation, etc.
Update website
Prepare source archive RC1, 2, ... and call for testing for a a week or two
Test archive locally on at least one environment.
Publish final release

Currently, the most time consuming part is the collection of CHANGES update:

Generate log of changes in Markdown. You fan find command in https://github.com/SOCI/soci/issues/93#issuecomment-15434667 which I used to generate this early list https://gist.github.com/mloskot/86df093cfc456c137c008bb18574dc93
Extract major and important changes
Copy them into CHANGES file

I contemplated and proposed automated creation of ChangeLog in https://github.com/SOCI/soci/commit/2ab0fb90120440243e0e1528bb1d16dbe71928ba  but I don't think there is general agreement about it as some folks prefer the distilled CHANGES file.
However, there is nothing wrong with including the CHANGELOG.md as raw extract from GitHub generated by the commands pointed above.
If you'd like to give the CHANGES preparation a try, you are welcome.
Otherwise, I will try to book some time in next 2-3 days to get it done.
Then, we should be pretty much ready for release.

I'll be taking care of these in my free time. I just hope that you would be merging the PR'S :)

FYI, I have just completed collecting the list of CHANGES up to now.

Closing this as duplicate of #616

I have just published SOCI 4.0.0 RC1 calling for tests
https://sourceforge.net/p/soci/mailman/message/36793193/
I'm expecting final release in a week or so, depending on stream of RC issues reported back.

SOCI 4.0.0 has been released
Please, prefer to use the mailing lists for questions.


Make sure all data is processed when there is mixed techniques

If there is Spectroscopic and Imaging data the redccd will only process imaging and if anything fails it will stop working. Either improve exit message or make sure the Spectroscopic data is processed

It is a tricky problem to do this automatically and of little value, it is recommended that user organized their files. Improving exit value would be good though.


Update hello-world.ts

Hello world in finnish
c21b5dc8b158914c340bac83ff236e557f6020fd40b3c1f02117eb44a6d5b0b9

@odetolataiwo I have paid this earlier. Don't send coins. Can you make sure this is logged into the system?

@odetolataiwo I have paid this earlier. Don't send coins. Can you make sure this is logged into the system?

done