Properly deprecate default implementation of `MacroExpansionContext.l…

Explanation: Now that we have rdar://123403268, we can change the default implementation of MacroExpansionContext.lexicalContext to return an empty array and be deprecated, making not implementing lexicalContext a compile-time warning instead of a runtime error.
Scope: Very narrow, only types conforming to MacroExpansionContext, which clients of the library generally shouldn’t be doing
Risk: Low, the scope is very narrow and shouldn’t affect anyone in practice. This  is just clean-up
Testing: Manually tested that the deprecation message shows up if a user conforms a type to MacroExpansionContext without adding a lexicalContext member
Issue: rdar://123410459
Reviewer:  @rintaro on https://github.com/swiftlang/swift-syntax/pull/2695

@swift-ci Please test

@swift-ci Please test


Change link address to market wiki

Hi @alexsuter,
When a user clicks on the "how to" hyperlink "https://dev.axonivy.com/link/market-contribute", they are redirected to "https://github.com/axonivy-market/market/wiki/c0-Contribute" instead of "https://github.com/axonivy-market/market/wiki/". This issue occurs only when the user is logged into GitHub; for anonymous users, the link works correctly. Is it ok if I proceed with changing it to the direct link as proposed in the PR, or if not, could you advise me on the redirect logic?

This link https://dev.axonivy.com/link/market-contribute is used in a lot of places. So now only this link here will be fixed. I need to analyze this issue further.

I've fixed the link redirection. You can close this PR and delete the branch.


WSL - suddenly all distro give error "The network does not have a subnet for this endpoint" when launching

Windows Build Number
10.0.18363 Build 18363
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
No response
Distro Version
Ubuntu 20.04
Other Software
Also Docker Desktop is not working anymore on WSL
Repro Steps

At windows startup wsl distro were usually running (eg docker desktop or Ubuntu)
Now, after months of straightforward usage, suddenly Docker Desktop at win startup gives exception with message "The network does not have a subnet for this endpoint."
I open cmd as Admin
I type wsl -l -v --> i detect both Ubuntu and Docker are "stopped"
I try to type wsl -d Ubuntu-20.04 --> get error "The network does not have a subnet for this endpoint."
I try to type wsl -d docker-destkop-data -> get error "The network does not have a subnet for this endpoint."
Restarting or any other command dont fix it

Expected Behavior
WSL distro launched and working as previous
Actual Behavior
WSL distro not launching

Diagnostic Logs
No response

Please collect networking logs and post (or link) the etl here.

Hi, thanks for the support. WSL started working again suddenly, without me doing any action.
So i think it probably broke cause of a central company windows update / pc config, that got fixed in a following update.
Closing the issue.


Improvement in Results Section in Exerciser Activity

The three icons on the left doesn't seem very intuitive to first time users. Neither there is a description of what they do nor their description pops when we hover over them.  Adding tooltips would help.

@llaske I would like to work on this.

@llaske, where the PR's of exerciser app, should be made?

PR for Exerciser should be made directly on Exerciser repo https://github.com/llaske/ExerciserReact


scroll.on does not work

My NextJS app uses react-locomotive-scroll in the _app.tsx which works well:
import { LocomotiveScrollProvider as RLSProvider } from "react-locomotive-scroll";
import { useRef } from "react";
import { LocomotiveScrollProvider as RLSProvider } from "react-locomotive-scroll";
import "locomotive-scroll/dist/locomotive-scroll.css";
import "../styles/index.css";

function MyApp({ Component, pageProps }: AppProps) {
  const { asPath } = useRouter();
  const containerRef = useRef(null);
  return (
    <RLSProvider
      options={{
        smooth: true,
        smartphone: {
          smooth: true,
        },
        tablet: {
          smooth: true,
        },
      }}
      watch={[]}
      location={asPath}
      onLocationChange={(scroll: any) =>
        scroll.scrollTo(0, { duration: 0, disableLerp: true })
      }
      containerRef={containerRef}
    >
      <div data-scroll-container ref={containerRef}>
        <Component {...pageProps} />
      </div>
    </RLSProvider>
  );
}

However, in my index.tsx which looks like the following, I cannot get the scroll.on function to work to report back the scroll position.
import { useLocomotiveScroll } from "react-locomotive-scroll";
const Index = () => {
const { scroll } = useLocomotiveScroll();

useEffect(() => {
        scroll.on("scroll", function (instance) {
      console.log(instance.scroll.y);
    });
  });
  return (
    <>
      <div className="flex flex-col">
        <HeaderMenu {...headerMenu} />
        <main data-scroll-container className="grow pt-24 pb-32 md:pb-48">
          {some content here}
        </main>
        <FooterMenu />
      </div>
    </>
  );
};

This always returns the error that data-scroll-container has not been defined.

Hi, did you figure this out eventually?

@Hasan-aga try following this example: https://github.com/brunos3d/nextjs-with-locomotive-scroll-example – worked for me!

Hey @opr-inzn, in your example, you define : const { scroll } = useLocomotiveScroll(); but you never use scroll anywhere. I need to access scroll.on, so how did you manage to access the scroll object? It is null for me.


Problem running mist on own Apache Spark Cluster

Hi,
I am trying to run a Mist Job on a custom Apache Spark cluster and I am getting the following error:
17/01/31 00:52:38 ERROR SparkUncaughtExceptionHandler: Uncaught exception in thread Thread[appclient-registration-retry-thread,5,main] java.util.concurrent.RejectedExecutionException: Task java.util.concurrent.FutureTask@6b9689d rejected from java.util.concurrent.ThreadPoolExecutor@38f018f4[Running, pool size = 1, active threads = 0, queued tasks = 0, completed tasks = 1] 	at java.util.concurrent.ThreadPoolExecutor$AbortPolicy.rejectedExecution(ThreadPoolExecutor.java:2047) 	at java.util.concurrent.ThreadPoolExecutor.reject(ThreadPoolExecutor.java:823) 	at java.util.concurrent.ThreadPoolExecutor.execute(ThreadPoolExecutor.java:1369) 	at java.util.concurrent.AbstractExecutorService.submit(AbstractExecutorService.java:112) 	at org.apache.spark.deploy.client.AppClient$ClientEndpoint$$anonfun$tryRegisterAllMasters$1.apply(AppClient.scala:96) 	at org.apache.spark.deploy.client.AppClient$ClientEndpoint$$anonfun$tryRegisterAllMasters$1.apply(AppClient.scala:95) 	at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244) 	at scala.collection.TraversableLike$$anonfun$map$1.apply(TraversableLike.scala:244) 	at scala.collection.IndexedSeqOptimized$class.foreach(IndexedSeqOptimized.scala:33) 	at scala.collection.mutable.ArrayOps$ofRef.foreach(ArrayOps.scala:108) 	at scala.collection.TraversableLike$class.map(TraversableLike.scala:244) 	at scala.collection.mutable.ArrayOps$ofRef.map(ArrayOps.scala:108) 	at org.apache.spark.deploy.client.AppClient$ClientEndpoint.tryRegisterAllMasters(AppClient.scala:95) 	at org.apache.spark.deploy.client.AppClient$ClientEndpoint.org$apache$spark$deploy$client$AppClient$ClientEndpoint$$registerWithMaster(AppClient.scala:121) 	at org.apache.spark.deploy.client.AppClient$ClientEndpoint$$anon$2$$anonfun$run$1.apply$mcV$sp(AppClient.scala:132) 	at org.apache.spark.util.Utils$.tryOrExit(Utils.scala:1119) 	at org.apache.spark.deploy.client.AppClient$ClientEndpoint$$anon$2.run(AppClient.scala:124) 	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 	at java.util.concurrent.FutureTask.runAndReset(FutureTask.java:308) 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.access$301(ScheduledThreadPoolExecutor.java:180) 	at java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:294) 	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
These are the steps I followed:

Set up a small Apache cluster of 3 machines using Apache Spark version 2.1.0.
Created an image using the Dockerfile after compiling Mist and specifying the Spark Version 2.1.0
Set the master URL in docker.conf to the IP and port of my apache spark cluster master.
Created a sample application using the examples given in the MIST directory and created an endpoint using router.conf.
Did the following POST request: curl --header "Content-Type: application/json" -X POST http://<IP:PORT>/api/log-search --data '{"digits":5}'

I would appreciate any help on this as I am trying to test whether Mist provides Driver fault tolerance for Spark Batch Processing jobs.
Please let me know if I can provide any more information.
Thank you

Hi @akshungupta, thanks for the issue. Could you please share settings for your Apache Spark cluster and docker.conf?

Hi,
Thank you for getting back to me.
The settings for Apache Spark are as follows:

I have 1 master and 2 worker nodes each on different machines. All of the machines can talk to each other.
I have used sbin/start-master.sh and sbin/start-slave.sh scripts to start the masters and slaves (workers).
There are no other custom settings that I have configured to create my Apache Spark cluster. It is a very simple cluster that I have brought up consisting of three machines.

I have attached my docker.conf, router.conf and the application simple_streaming.py in configs_job.zip to this post. simple_streaming.py is a very simple application and we wanted to get a feel of deploying mist on Apache Spark cluster.
configs_job.zip
One thing to note is the following:
We had downloaded the source code of Apache Spark and had used the binary from the project to launch the Apache Spark cluster and tell mist the IP and port of the master. We could not find a way to use mist's apache spark binary to set up a custom cluster. Please also let us know if this is possible.

Hi @akshungupta
You can start workers and connect them to the master via:
./sbin/start-slave.sh <master-spark-URL>

If you used spark-defaults.conf show me content please.
Generally it is better to use the IP address of Master node instead of the alphabetic hostname that is provided by spark master.
spark://<master-machine-IP>:7077

Once you have started a worker, look at the master’s web UI (port 8080 or 4040 by default). You should see all your nodes listed there.

Hi @leonid133
You are right. I had started my workers and master using sbin/start-mater.sh and sbin/start-slave.sh scrips available as part of the Spark code base. I did see all my worker nodes on the master's web UI.
I did not use spark-defaults.conf. I just started 2 slaves 2 machines and provided the master spark url to each slave when running the script /sbin/start-slave.sh
I tried using the IP address instead of the DNS name but I am getting the same error.

Hi @akshungupta
Try to check the connection from docker container to spark master node and SPARK_VERSION
docker exec -it <mist_docker_name> bash
telnet <master_host> <master_port>
echo $SPARK_VERSION

Now for Spark version 2.1.0 we have a specific docker
docker run -p 2003: 2003 -v /var/run/docker.sock:/var/run/docker.sock -d hydrosphere / mist: master-2.1.0 Mist

Hi @leonid133, using master-2.1.0 fixed the issue!
Thank you!


bumps golangci linter version to 1.46.2

Codecov Report

Merging #9 (d5bd10e) into main (c9b15e5) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main       #9   +/-   ##
=======================================
  Coverage   93.70%   93.70%
=======================================
  Files           3        3
  Lines         127      127
=======================================
  Hits          119      119
  Misses          4        4
  Partials        4        4

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 c9b15e5...d5bd10e. Read the comment docs.


Error with error.identity.user.primaryEmailNotSpecified

Hello there!
I followed the steps for arm branch but get stuck on this error. Is there any other action I should do? Thanks in advance!
Error: 400-IdcsConversionError, Post request failed{"schemas":["urn:ietf:params:scim:api:messages:2.0:Error","urn:ietf:params:scim:api:oracle:idcs:extension:messages:Error"],"detail":"The primary email must be specified.","status":"400","urn:ietf:params:scim:api:oracle:idcs:extension:messages:Error":{"messageId":"error.identity.user.primaryEmailNotSpecified"}}
Suggestion: Please retry or contact support for help with service: Identity User
Documentation: https://registry.terraform.io/providers/oracle/oci/latest/docs/resources/identity_user
API Reference: https://docs.oracle.com/iaas/api/#/en/identity/20160918/User/CreateUser
Request Target: POST https://identity.eu-milan-1.oci.oraclecloud.com/20160918/users
Provider version: 4.79.0, released on 2022-06-08.
Service: Identity User
Operation Name: CreateUser
OPC request ID: acd65a0eefe91be179364b94d85d92bc/EEC547AAD76A4045009ABF519620EFD3/6FA975E7A516F41B9CEA2A06E6B80DB7
  on users.tf line 5, in resource "oci_identity_user" "oci_user"
   5: resource "oci_identity_user" "oci_user" {

Thank you! I can confirm that you need to add user_email as variable. It can also be worthy notice that the configuration fails if the target compartment is not the root one.
The deployment is now successful for me, but how can I update docker- compose in order to apply DNS records?

Thanks a lot Enrico for your feedback.
Once the cluster is deployed and you want to update docker-compose.yml, just logged on node1 and perform:
$ ssh -i ssh_priv.key opc@oci-swarm-ID-0
$ sudo -i
# vi docker-compose.yml
# source /root/swarm.env
# export $(cut -d= -f1 /root/swarm.env)
# docker stack deploy -c docker-compose.yml swarm

Once you have a DNS configured to your Load Balancer IP, Traefik will register LetsEncrypt certs for Portainer, when this is ready you will be able to log into Portainer and start administering other stacks using the browser.
Best regards, Marcelo.

Thanks. I am experienced with Portainer but unfortunately I am not with Oracle cloud and Terraform. I am having troubles understanding how to connect. I cannot understand which private key is attached to the nodes. I did provide one for DB, not for nodes. (Cluster started via terraform apply since stacks didn't worked well)

Fixed in commit.


Just download the Layer. (No developer build required.)

I guess a GitHub Action should be build that automatically checks, if there is a new Swift version. If a new version is available, a new commit should be made in a separate repository that also gets a git tag. Then we can upload the Layer binary to the release tag. That way we always have the newest version. No manual work required.

Full layers can be downloaded or used here:
https://fabianfett.de/amazonlinux-swift


firefox-portable: Add scripts to set as default browser

fix #4090 .

/unsubscribe
I do not think more scripts like this should be introduced in official buckets.

/unsubscribe
I do not think more scripts like this should be introduced in official buckets.

sorry for the mistake!


[NFC] Move getRootOperation utility from CPUUtils -> Utils

-- getRootOperation utility had no CPU specific construct and is
being used by other backends : CPU, VMVX and a downstream project concerning AIE backend.
-- Therefore to disambiguate the header file's inclusion, this utility
has been moved to a common space instead.
Signed-off-by: Abhishek Varma<EMAIL_ADDRESS>

This is intended because different backends have different definition about "rootOp". The method is expected to be used by CPU and VMVX backends for now.

You're correct - but we also have AIE backend trying to use this now. Perhaps then we should have a better name than "CPUUtils" now that three different backends use this. Let me know your thoughts.

Okay, thanks for the information! So this is for downstream projects. Could you add it to PR description as well?

Hi Hanhan.
Thanks for approving. I've updated the PR's description now.
The PR seems to be blocked on the CLA (it's going on since 4 hours with no Pass/Fail response) although I've contributed to IREE a few times.
I tried checking the CLA doc, just in case to check if I still have the CLA signed and see one section where it mentions the following :-
Your contribution (commit) must be associated with at least one of:

1. The primary email on your Google Account associated with the signed CLA.
2. An Alternate email on your Google Account associated with the signed CLA. See and modify your aternate emails at https://myaccount.google.com/alternateemail.
3. The GitHub username associated with the signed CLA.

And I confirm that point number 3 satisfies the "at least" criteria above.
Maybe a server error because the "Manage account" gives 502 error.
Can you please help me out here with any actionable step that I may take to get this merged?

I'm no longer a Googler, so I don't have any access to related things. This is also new to me, so I don't know how to handle this. Maybe @jpienaar or others can help this.

You're correct - but we also have AIE backend trying to use this now. Perhaps then we should have a better name than "CPUUtils" now that three different backends use this. Let me know your thoughts.

Okay, thanks for the information! So this is for downstream projects. Could you add it to PR description as well?

Hi Hanhan.
Thanks for approving. I've updated the PR's description now. The PR seems to be blocked on the CLA (it's going on since 4 hours with no Pass/Fail response) although I've contributed to IREE a few times.
I tried checking the CLA doc, just in case to check if I still have the CLA signed and see one section where it mentions the following :-
Your contribution (commit) must be associated with at least one of:

1. The primary email on your Google Account associated with the signed CLA.
2. An Alternate email on your Google Account associated with the signed CLA. See and modify your aternate emails at https://myaccount.google.com/alternateemail.
3. The GitHub username associated with the signed CLA.

And I confirm that point number 3 satisfies the "at least" criteria above.
Maybe a server error because the "Manage account" gives 502 error. Can you please help me out here with any actionable step that I may take to get this merged?

Hi @jpienaar
Can you or someone you can me point to please help me getting this PR merged?

(note that I'd strongly advise against trying to common this utility - what a "root op" is - or even that one exists at all - will change over time and as a downstream repo you're likely to run into issue as it does if you tie yourself to it - it's almost always better to start with a soft fork of implementation details that haven't been approved as part of the public API of the compiler than it is to reuse them)

I want to signal that I'm considering to update the method with CPU specific logics. I found that we would want pack op to be root op for some cases. I will likely discuss it in tile size infra improvement, but we're stilling working on a draft doc..

Also fly by comment since we're talking about what a root op is, I would be +1 on finding a different term for "root op" here, as the way that "Kernel Dispatch"/"Config" uses it is unrelated to how most of the rest of codegen uses it (as the root of an operation DAG). The notion of "root" in KernelConfig is closer to an anchor for a code generation strategy rather than anything specific about the surrounding IR structure. I know that reuse of terminology has caused confusion in the past, so could be worth changing if we're poking around here already.

Ok, lets hold off on this PR... I think fundamentally all backends should be doing something similar (and I agree the different uses of the term "root op" has been confusing). I will be soon changing the first level tile and distribute to use some of the upstream work I am doing. I'll take that as an opportunity to rethink the terminology here.

Closing stale PR.


[Do not commit] Exclude JSON files from RAT check

Need to exclude the JSON files from
RAT check since we can't add ASF
license header as a comment.

It is duplicate of HADOOP-17750 (#3083). Thanks.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
14m 22s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+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.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
33m 34s

trunk passed

+1 :green_heart:
compile
23m 41s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
20m 15s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
mvnsite
27m  1s

trunk passed

+1 :green_heart:
javadoc
8m 50s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
9m 21s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
shadedclient
137m 18s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
23m  8s

the patch passed

+1 :green_heart:
compile
29m  0s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
29m  0s

the patch passed

+1 :green_heart:
compile
25m 15s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
javac
25m 15s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
22m 22s

the patch passed

+1 :green_heart:
xml
0m  2s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
8m 19s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
8m 14s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
shadedclient
31m 31s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

-1 :x:
unit
808m 45s
/patch-unit-root.txt
root in the patch passed.

+1 :green_heart:
asflicense
1m 41s

The patch does not generate ASF License warnings.

1095m 42s

Reason
Tests

Failed junit tests
hadoop.yarn.server.timelineservice.storage.common.TestHBaseTimelineStorageUtils

hadoop.yarn.server.router.clientrm.TestFederationClientInterceptor

hadoop.fs.http.client.TestHttpFSWithHttpFSFileSystem

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3082/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3082

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell xml

uname
Linux 6d57cd7dabf0 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-support/bin/hadoop.sh

git revision
trunk / da43ad3182d5b3da9d3d05ede6762d84656bbfe8

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3082/1/testReport/

Max. process+thread count
2884 (vs. ulimit of 5500)

modules
C: . U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3082/1/console

versions
git=2.25.1 maven=3.6.3

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Logfile
Comment

+0 :ok:
reexec
0m 40s

Docker mode activated.

_ Prechecks _

+1 :green_heart:
dupname
0m  0s

No case conflicting files found.

+0 :ok:
codespell
0m  1s

codespell was not available.

+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.

_ trunk Compile Tests _

+1 :green_heart:
mvninstall
32m 41s

trunk passed

+1 :green_heart:
compile
23m 47s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
compile
20m 28s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
mvnsite
27m 15s

trunk passed

+1 :green_heart:
javadoc
8m 20s

trunk passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
8m 20s

trunk passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
shadedclient
134m 51s

branch has no errors when building and testing our client artifacts.

_ Patch Compile Tests _

+1 :green_heart:
mvninstall
21m  6s

the patch passed

+1 :green_heart:
compile
23m 17s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javac
23m 17s

the patch passed

+1 :green_heart:
compile
20m 13s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
javac
20m 13s

the patch passed

+1 :green_heart:
blanks
0m  0s

The patch has no blanks issues.

+1 :green_heart:
mvnsite
22m 27s

the patch passed

+1 :green_heart:
xml
0m  2s

The patch has no ill-formed XML file.

+1 :green_heart:
javadoc
8m 21s

the patch passed with JDK Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04

+1 :green_heart:
javadoc
8m 22s

the patch passed with JDK Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

+1 :green_heart:
shadedclient
31m 40s

patch has no errors when building and testing our client artifacts.

_ Other Tests _

+1 :green_heart:
unit
797m 35s

root in the patch passed.

+1 :green_heart:
asflicense
1m 41s

The patch does not generate ASF License warnings.

1055m 45s

Subsystem
Report/Notes

Docker
ClientAPI=1.41 ServerAPI=1.41 base: https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3082/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hadoop/pull/3082

Optional Tests
dupname asflicense compile javac javadoc mvninstall mvnsite unit shadedclient codespell xml

uname
Linux b7675f5d1a6f 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-support/bin/hadoop.sh

git revision
trunk / c5deb75b07ff37eb38bbe7a608d7dd1369d2624a

Default Java
Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Multi-JDK versions
/usr/lib/jvm/java-11-openjdk-amd64:Ubuntu-11.0.11+9-Ubuntu-0ubuntu2.20.04 /usr/lib/jvm/java-8-openjdk-amd64:Private Build-1.8.0_292-8u292-b10-0ubuntu1~20.04-b10

Test Results
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3082/2/testReport/

Max. process+thread count
3128 (vs. ulimit of 5500)

modules
C: . U: .

Console output
https://ci-hadoop.apache.org/job/hadoop-multibranch/job/PR-3082/2/console

versions
git=2.25.1 maven=3.6.3

Powered by
Apache Yetus 0.14.0-SNAPSHOT https://yetus.apache.org

This message was automatically generated.


Grammar

Grammatical fixes

Thanks! Can you make the commit message title a little clearer, per the contributor guidelines? It should be clear to people just from the "title" line that this doesn't affect any behavior or even the meaning of the comment.

Thanks @jrose-apple -- updated the commit


[WIP] Domain-invariant partial least squares regression

Summary
I added the DIPLS class along with the dipals function to skada/_dipls.py and created an example in examples/methods/plot_dipls.py to showcase its usage. In the example, I apply di-PLS to a typical regression task in my domain (analytical chemistry) and tried to highlight the features that make it particularly useful for us (interpretability, flexibility). I also included a comparison with JDOT on the same task. The branch passed all tests (related to the new class and functions) and I updated the documentation accordingly.

Thanks for the PR! It seems your linter changed .circleci/config.yml and .pre-commit-config.yaml which shouldn't be modified. Can you revert these changes?

Hi Antoine
I have reverted the changes as you suggested but it seems that the tests are still not successful...

Hello @B-Analytics ,
You need to merge the README.md file because the current merge conflit prevent te doc and the test from running.

Got it!

 However, this time the problem is associated with the docs. Following files seem to cause the problem:
../../examples/deep/plot_adversarial.py
../../examples/deep/plot_divergence.py
../../examples/deep/plot_optimal_transport.py
Can you give please give me a hand?

You can generate and open the doc locally with
make clean && make html && open build/html/index.html
in the docs folder. Tell me if it helps you or not.

I can build the documentation locally

but it fails on circleci for some reason:

Which version of scikit-learn are you using?
I think I found the problem:
skorch is not compatible with version 1.6.0 of scikit-learn yet (https://github.com/skorch-dev/skorch/pull/1076). circle-ci pulls 1.6.0 and thus the documentation cannot be build... So I think your problem is independent from your PR.

Yes, I am using scikit-learn v1.5.2 on my local machine. Let me know if I can do something to move this forward.


Cannot build a target for linux arm64

Hello there,
First of all, thanks for the great work.
Using the following rule, I am trying to integrate a CPP library into a Go package.
# This rule is defined for each architecture in each directory.
cc_import(
    name = "banana_lib",
    static_library = "libbanana_static.a",
)

go_library(
    name = "banana",
    srcs = glob(["include/**/*.h"]) + [
        "cfunc.go",
        "banana.go",
    ],  # keep
    cdeps = select({
        "@io_bazel_rules_go//go/platform:linux_arm64": [
            "//test/banana/linux_arm64:banana_lib",
        ],
        "@io_bazel_rules_go//go/platform:linux_amd64": [
            "//test/banana/linux_amd64:banana_lib",
        ],
        "@io_bazel_rules_go//go/platform:darwin_amd64": [
            "//test/banana/darwin_x86_64:banana_lib",
        ],
        "@io_bazel_rules_go//go/platform:darwin_arm64": [
            "//test/banana/darwin_arm64:banana_lib",
        ],
        "//conditions:default": [],
    }),
    cgo = True,
    clinkopts = ["-lpthread -lstdc++"],
    data = [":banana_dict"],
    importpath = "seungduk.kim/test/banana",
)

It requires a toolchain, so I imported bazel-zig-cc in WORKSPACE.
BAZEL_ZIG_CC_VERSION = "v1.0.1"

http_archive(
    name = "bazel-zig-cc",
    sha256 = "e9f82bfb74b3df5ca0e67f4d4989e7f1f7ce3386c295fd7fda881ab91f83e509",
    strip_prefix = "bazel-zig-cc-{}".format(BAZEL_ZIG_CC_VERSION),
    urls = ["https://git.sr.ht/~motiejus/bazel-zig-cc/archive/{}.tar.gz".format(BAZEL_ZIG_CC_VERSION)],
)

load("@bazel-zig-cc//toolchain:defs.bzl", zig_toolchains = "toolchains")

zig_toolchains()

And I ran the following command.
 bazel build --platforms @zig_sdk//platform:linux_arm64 --extra_toolchains @zig_sdk//toolchain:linux_arm64_gnu.2.28  --incompatible_enable_cc_toolchain_resolution  //test/banana

Running the command above resulted the following.
ld.lld: error: undefined symbol: std::string::compare(char const*) const
>>> referenced by ArchUtils.cpp
>>>               ArchUtils.cpp.o:(parseArchType(char const*)) in archive experimental/seungduk.kim/test/banana/linux_arm64/libbanana_static.a

ld.lld: error: undefined symbol: std::_Rb_tree_increment(std::_Rb_tree_node_base const*)
>>> referenced by ModelDetector.cpp
>>>               ModelDetector.cpp.o:(banana::ModelDetector::saveModel(std::string const&) const) in archive experimental/seungduk.kim/test/banana/linux_arm64/libbanana_static.a
>>> referenced by ModelDetector.cpp
>>>               ModelDetector.cpp.o:(banana::ModelDetector::saveModel(std::string const&) const) in archive experimental/seungduk.kim/test/banana/linux_arm64/libbanana_static.a
>>> referenced by ModelDetector.cpp
>>>               ModelDetector.cpp.o:(banana::ModelDetector::saveModel(std::string const&) const) in archive experimental/seungduk.kim/test/banana/linux_arm64/libbanana_static.a
>>> referenced 8 more times

ld.lld: error: undefined symbol: std::_Rb_tree_rebalance_for_erase(std::_Rb_tree_node_base*, std::_Rb_tree_node_base&)
>>> referenced by ModelDetector.cpp
>>>               ModelDetector.cpp.o:(banana::ModelDetector::countNgram(banana::ModelDetector::Counter&, std::function<std::basic_string<char16_t, std::char_traits<char16_t>, std::allocator<char16_t>> ()> const&, unsigned long, unsigned long) const) in archive experimental/seungduk.kim/test/banana/linux_arm64/libbanana_static.a
>>> referenced by ModelDetector.cpp
>>>               ModelDetector.cpp.o:(banana::ModelDetector::countNgram(banana::ModelDetector::Counter&, std::function<std::basic_string<char16_t, std::char_traits<char16_t>, std::allocator<char16_t>> ()> const&, unsigned long, unsigned long) const) in archive experimental/seungduk.kim/test/banana/linux_arm64/libbanana_static.a
compilepkg: error running subcommand external/zig_sdk/tools/aarch64-linux-gnu.2.28/c++: exit status 1
Target //experimental/seungduk.kim/test:test failed to build
Use --verbose_failures to see the command lines of failed build steps.
INFO: Elapsed time: 32.203s, Critical Path: 31.75s
INFO: 5 processes: 2 internal, 3 darwin-sandbox.
FAILED: Build did NOT complete successfully

I also tried @zig_sdk//toolchain:linux_arm64_musl but nothing worked. I am using a darwin_arm64 machine and every targets of darwin (darwin_arm64, darwin_amd64) works well.
The error messages seem like all standard libraries failed to be linked. Any thoughts?
Thank you!

Here is the crux of the problem: https://github.com/ziglang/zig/issues/9832#issuecomment-926832810
TLDR: compile your dependencies with zig c++ too.

No easy job there... Thanks a lot!


refactor browser storage to allow component connection [SATURN-1286]

Evolves syncAtomToSessionStorage into a more general 'static' storage mechanism.
It can purge dynamic storage entries as needed to make space, but is not itself a candidate for automatic deletion. As such, it can serve as a more resilient storage area for 'important' data.
It also listens to the storage event, so will automatically sync across browser tabs in real-time.
It no longer maintains state in an atom, but instead provides an atom-compatible interface that can be used interchangably via connectAtom.
Tested existing usages by clicking through. Tested cross-tab communication with some temporary example code.

TOL, and I've only just skimmed the code... you say, "It no longer maintains state in an atom, but instead provides an atom-compatible interface that can be used interchangably via connectAtom." This feels misleading to me. Is there a higher-level concept than connectAtom that we should introduce to avoid confusion about what is actually being passed to it?

@breilly2 Agreed, we could definitely do some renaming to better incorporate these ideas. I was thinking along the lines of 'Store' as the common interface name, e.g. connectStore. And atom could be memoryStore, to communicate its lifespan.
In any case, I think we can do that in a separate PR to keep things small.


Specify version of spark to install

Unable to specify version of spark when running spark new, so I get error because have not upgraded to 6.  The only problem with this pr is that the version resource is not found.
I.e.
The current version is URL is
https://spark.laravel.com/api/releases/6.0.3/download?api_token=...
and the expected endpoint
https://spark.laravel.com/api/releases/5.0.3/download?api_token=....
returns 404.
Is there an api endpoint available for other versions?  I tried using the resource ID (v5.0.3 => 68), but to no avail.
Only worth merging this if I can find out what the correct endpoint is.

Please ignore the comment about the 404 on the resource.  There is no 5.0.3.  facepalm
Corrected to 5.0.1 and all is golden

There are other things that are different about the installation process. Use the 5.0 branch of the installer.


Added the option of a dilated convolution to parallel_conv and some

tests for it

Will likely move this into v1 since we are close to release there


Drop Python 3.9

close https://github.com/scverse/scvi-tools/issues/2966

integration (ubuntu-latest, 3.9)  is the legacy before the change and did not run; we expect this test to not appear once we merge this PR to main


OpenGL not working

Hello,
I am trying to run my C++ 3D game in Unity using native plugin. The game is 32-bit and uses OpenGL. I commented out directX defines in PlatformBase.h. And the plugin doesn't work (no triangle drawn). My OS is Windows 7, Unity version - 5.6.7f1.

I forgot to change API in Player Settings


Handler resolution context

I would like Sebastien and others to have a look, as this related to a problem that Sebastien encountered.
When resolving a handler, provide a context so that different handlers can be resolved in different contexts if needed. The problem that we are addressing is that when we have two queues on the same topic, we want a different handler for each queue and this doesn't work well with the IHandlerResolver.
e.g.
_fluentNotificationStack
    .WithSqsTopicSubscriber()
        .IntoQueue("QueueA")
        .WithMessageHandler<OrderPlaced>(_resolver)

    .WithSqsTopicSubscriber()
        .IntoQueue("QueueB")
        .WithMessageHandler<OrderPlaced>(_resolver)

Then we would like the resolver to resolve an instance of OrderPlacedHandlerA in the first case and an instance of OrderPlacedHandlerB in the second case.
This change will give the handler resolver information that can be used to do this using IoC container mechanisms such as named bindings
I'm not thrilled by the class name HandlerResolutionContext - it's long and the word "Context" is general enough to mean anything. But it is best to have a separate object for this task as it can be extended as been be without breaking anything else. Right now it looks like we only need the (short) queue name.
If the design is good, it probably needs a test demonstrating how to hook this into an IoC container and resolve different handlers?

👍 @AnthonySteele this is what I had in mind while we were discussing this. @serialseb what are your thoughts?

I am reasonably happy with this PR. Any thoughts on a better name than HandlerResolutionContext?


Receiving error "{error: file is invalid}" when importing

Hello,
I seem to be having issues implementing the import function, have I implemented this correctly? The following fails when trying to import with the error {error: file is invalid} - uploading the same file with CURL or manually works without any problems. I was getting the same error in postman until I switched the form data from text to "file" and selected the file manually.
var fi =<EMAIL_ADDRESS>var pa = `api-server`

func main() {
	git, err := gitlab.NewClient(t, gitlab.WithBaseURL(u))
	if err != nil {
		log.Fatal(err)
	}

	opt := &gitlab.ImportFileOptions{
		Path: &pa,
		File: &fi,
	}

	stat, resp, err := git.ProjectImportExport.ImportFile(opt)
	fmt.Println("Error:", err)
	if err != nil {
		log.Fatal(err)
	}

	body, err := ioutil.ReadAll(resp.Body)

	fmt.Println("Status:", stat)
	fmt.Println("Response:", body)

}

I came across #636 and can see the problem. Import takes a multipart writer and this hasn't been implemented, so no file was actually being sent, I've worked around this the same way using the standard library instead.


DL-45: DL should allow ByteBuffer based API and should avoid copying of arrays

This needs the bookkeeper pull request https://github.com/twitter/bookkeeper/pull/4 to be integrated first. Let's review both and then plan a commit plan.

the overall change looks good. Let me take a look at the bk change and plan how to merge this. @arvindkandhare

@arvindkandhare is the twitter/bookkeeper#4 change finalized?

@sijie The BK changes are final and ready to be checked in once you are satisfied with them. This particular pull request still needs a couple of changes.

@arvindkandhare @jiazhai I will merge the bk change and produce a new version this week.

@arvindkandhare @jiazhai I was experimenting using netty-buffer for memory allocation and management. I got pretty good performance results on it. I will try to share more details with numbers in a few days. /cc @leighst

in bookkeeper 4.5, the netty bytebuf is introduced, we might consider using bytebuf there to better integrate with the new bytebuf api.

closed this pull request since DL is using BK 4.5 now. we will pick up the ByteBuf API rather than ByteBuffer API here.


Global search field

There should be a way to find another compendium from any other page, a global search field or something like that.

Closing due to inactivity.


chore: syncRef watch options docs

As discussed in https://github.com/antfu/vueuse/issues/189

Thanks!


Customer Create functionality

While creating a customer couldn’t upload profile image

Hi @spurtcmsdeveloper-73 ,we will fix the issues shortly.

Now Implemented customer profile upload.

Great to hear that the customer profile upload feature has been implemented! I look forward to trying it out. Thank you for the update!


REST steps - consider option to specify query string in examples table

We should consider some option to send query string parameters in examples table, ie to simplify following use case:
/openapi/v2/transaction/{CP:ACCOUNT_NUMBER}/transactions/instalmentPlanOffers?demandedAmount=15000&transactionType=RTL&currency={CURRENCY}&transactionDate={CURRENT_DATE:{CP:TIMESHIFT_DAYS}}&iptype=EPP

There are 2 ways I see to solve this:

something like @query-parameter, @path-parameter (@query/@path, or @queryParameter/@pathParameter)? similar approach as for headers and body
new column that would say what type is the parameter - similar aproach as for jaxb and abstract type implementations

So far I am in favor of the first option with something like:
When [GET] request to [TEST]/[/openapi/v2/transaction/] is sent with data:
| name                       | data                               |
| @query.transaction         |                                    |
| @query.{CP:ACCOUNT_NUMBER} |                                    |
| @query.transactions        |                                    |
| @query.instalmentPlanOffers|                                    |
| @path.demandedAmount       | 15000                              |
| @path.transactionType      | RTL                                |
| @path.currency             | {CURRENCY}                         |
| @path.transactionDate      | {CURRENT_DATE:{CP:TIMESHIFT_DAYS}} |
| @path.iptype               | EPP                                |

Thoughts? Or any other ideas?

There are 2 ways I see to solve this:

something like @query-parameter, @path-parameter (@query/@path, or @queryParameter/@pathParameter)? similar approach as for headers and body
new column that would say what type is the parameter - similar aproach as for jaxb and abstract type implementations

So far I am in favor of the first option with something like:
When [GET] request to [TEST]/[/openapi/v2/transaction/] is sent with data:
| name                       | data                               |
| @query.transaction         |                                    |
| @query.{CP:ACCOUNT_NUMBER} |                                    |
| @query.transactions        |                                    |
| @query.instalmentPlanOffers|                                    |
| @path.demandedAmount       | 15000                              |
| @path.transactionType      | RTL                                |
| @path.currency             | {CURRENCY}                         |
| @path.transactionDate      | {CURRENT_DATE:{CP:TIMESHIFT_DAYS}} |
| @path.iptype               | EPP                                |

Thoughts? Or any other ideas?


sys/linux: various descriptions fixes

Codecov Report

Merging #1551 into master will decrease coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1551      +/-   ##
==========================================
- Coverage   56.08%   56.04%   -0.04%
==========================================
  Files         142      142
  Lines       26584    26584
==========================================
- Hits        14909    14899      -10
- Misses      10956    10966      +10
  Partials      719      719

Impacted Files
Coverage Δ

prog/checksum.go
76.92% <0%> (-13.19%)
:arrow_down:

prog/any.go
89.39% <0%> (+0.7%)
:arrow_up:

Continue to review full report at Codecov.

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

Nice!


ADD grid_color option

Thanks for providing this great repository!
I want to change the GridMap color after initialization.
This PR:

Added option to update grid map colors

I couldn't think of an best example, so I didn't add one.
I used this code to check the operation.

Thank your for your a lot of advise !
I have made changes to the code and conducted testing using same code

Thanks a lot! The PR looks good to me now.


Bug when trying to upload image using FileUpload with two different storages

Package
filament/filament
Package Version
v3.0.51
Laravel Version
v10.23.1
Livewire Version
v3.0.4
PHP Version
PHP 8.2.10
Problem description
When trying to upload an image file with FILESYSTEM_DISK to s3 and FILAMENT_FILESYSTEM_DISK set anything else. The Filament will try to first upload to the s3 and then to the desired disk.
However, my S3 disk does not have the CORS setup since it has nothing related to my filament panel.
Expected behavior
The file upload should fully use the FILAMENT_FILESYSTEM_DISK.
Steps to reproduce

Clone example repo
php artisan migrate
php artisan make:filament-user
Enter admin panel
Try to create a post

Reproduction repository
https://github.com/miguilimzero/filament-file-upload-bug-example
Relevant log output
No response

Following the livewire documentation, it seems that the Temporary preview URL is trying to use the default disk and not the filament disk.
https://livewire.laravel.com/docs/uploads#temporary-preview-urls.

You should also set the disk in the Livewire config, we can't do that for you unfortunately.


Windows: fix the exclusion of _DECC*.H in install

Correct the checked for directory delimiter

Ref: #6303

Applied efc7fb2eaee31f179fe1f965dd896e4a2c484418 and run build using MSVC, but still it didn't work:
	"C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.14.26428\bin\HostX64\x64\nmake.exe" /                   depend && "C:\Program Files (x86)\Microsoft Visual Studio\2017\Community\VC\Tools\MSVC\14.14.26428\bin\HostX64\x64\nmake.exe" /                   _all
*** Installing development files
created directory `C:/libOPENSSL-1.1.1-dev/MSVC64RH'
created directory `C:/libOPENSSL-1.1.1-dev/MSVC64RH/include'
created directory `C:/libOPENSSL-1.1.1-dev/MSVC64RH/include/openssl'
Copying: ./include/openssl/__DECC_INCLUDE_EPILOGUE.H to C:/libOPENSSL-1.1.1-dev/MSVC64RH/include/openssl/__DECC_INCLUDE_EPILOGUE.H
Copying: ./include/openssl/__DECC_INCLUDE_PROLOGUE.H to C:/libOPENSSL-1.1.1-dev/MSVC64RH/include/openssl/__DECC_INCLUDE_PROLOGUE.H
Copying: ./include/openssl/aes.h to C:/libOPENSSL-1.1.1-dev/MSVC64RH/include/openssl/aes.h

<snip>

Copying: ./include/openssl/x509v3err.h to C:/libOPENSSL-1.1.1-dev/MSVC64RH/include/openssl/x509v3err.h
Copying: ./include/openssl/__DECC_INCLUDE_EPILOGUE.H to C:/libOPENSSL-1.1.1-dev/MSVC64RH/include/openssl/__DECC_INCLUDE_EPILOGUE.H
Copying: ./include/openssl/__DECC_INCLUDE_PROLOGUE.H to C:/libOPENSSL-1.1.1-dev/MSVC64RH/include/openssl/__DECC_INCLUDE_PROLOGUE.H
Copying: ./include/openssl/aes.h to C:/libOPENSSL-1.1.1-dev/MSVC64RH/include/openssl/aes.h

Damnit...  didn't think this one through.  Closing.


ts: Migrate compose_fade_helper.js and compose_fade_users.js to TypeScript.

This PR consists of 4 commits:

sub_store: Move PartialBy to util.
This aids reusability of this utility type in the codebase.

util: Redefine Recipient type.
Redefined Recipient type by spliting it into DirectRecipient
and StreamRecipient. Splitting makes each of sub-type reusable.
This is a prep-commit for migrating compose_fade_helpers.

ts: Migrate compose_fade_helper.js to TypeScript.

ts: Migrate compose_fade_users.js to TypeScript.
Created a type Configuration in compose_fade_users.ts that very likely will be re-used in compose_fade.js, buddy_data.js,  buddy_list.js, etc.

Fixes:

Screenshots and screen captures:

Self-review checklist

[ ] Self-reviewed the changes for clarity and maintainability
(variable names, code reuse, readability, etc.).

Communicate decisions, questions, and potential concerns.

[ ] Explains differences from previous plans (e.g., issue description).
[ ] Highlights technical choices and bugs encountered.
[ ] Calls out remaining decisions and concerns.
[ ] Automated tests verify logic where appropriate.

Individual commits are ready for review (see commit discipline).

[ ] Each commit is a coherent idea.
[ ] Commit message(s) explain reasoning and motivation for changes.

Completed manual review and testing of the following:

[ ] Visual appearance of the changes.
[ ] Responsiveness and internationalization.
[ ] Strings and tooltips.
[ ] End-to-end functionality of buttons, interactions and flows.
[ ] Corner cases, error conditions, and easily imagined bugs.

@zulipbot add "area: typescript migration"

@zulipbot add "mentor review"

Status update: Currently slowly fixing Puppeteer's errors as I'm not able to test with Puppeteer on my local machine. Trying to solve my local problem first.
CZO discussion

Closing in favor of https://github.com/zulip/zulip/pull/26812, thanks @jychen630!


require node 16 due to adapter-core 3.x.x

Adapter requires node 16 as adapter-core 3.x.x is known to fail at node 14 or older

Please merge this PR and create a new release so that the check is active when requesting as stable update.


quic: report stream reset direction in reset callback failure string

Commit Message: add FROM_PEER/FROM_SELF to the transport_failure_reason string when a QUIC stream gets reset.
Risk Level: low, error reporting format change
Testing: existing tests
Docs Changes: N/A
Release Notes: N/A
Platform Specific Features: N/A

/retest

/retest

@RyanTheOptimist Mind helping merging it?


orbis.zone not accessible

The website is not longer accessible at https://orbis.zone since it returns a 404 Error.

Any updates on this? Am i missing an changed sign up process or so?

I was asked whether I could make clarifications on this project. Orbis is the work of willy, so I unfortunately can't personally. I will relay the issue to him to ask for an update.


feat: adds readme content

Resolves #898

adds readme
gets formatters working and tweaks typedefs

Hmm, I think that would be a different ticket to resolve the front-end issue.
I'm not sure if there is a way to set the width and height for the images inside the README, but I wouldn't be surprised.
I believe the current issue could be due to the containers not setting a specific width and height themselves, so the images don't respect their container size.


feat: Add storeToRefs to the auto imports in @pinia/nuxt #1876

fix #1876
Testing changes in Nuxt playground testStore.ts.

Codecov Report

Merging #2427 (04e14d1) into v2 (b1704d0) will increase coverage by 0.03%.
Report is 21 commits behind head on v2.
The diff coverage is 60.00%.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
@@            Coverage Diff             @@
##               v2    #2427      +/-   ##
==========================================
+ Coverage   93.80%   93.83%   +0.03%
==========================================
  Files          11       11
  Lines        2858     2856       -2
  Branches      182      182
==========================================
- Hits         2681     2680       -1
+ Misses        175      174       -1
  Partials        2        2

Files
Coverage Δ

packages/pinia/src/store.ts
84.16% <60.00%> (+0.07%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[?] Unable to install qcodes after uninstalling it

The issue is in [?] state because it is being checked on whether it is reproducible.
(qcodes3) C:\Users\Administrator>pip list -e
Package             Version Location
------------------- ------- ------------------------------------------------------------
plottr              0.0.1   c:\users\administrator\onedrive\bf4\code\plottr
pytopo              0.0.1   c:\users\administrator\onedrive\bf4\code\pytopo
qcodes              0.1.11  c:\users\administrator\onedrive\bf4\code\qcodes
qdev-wrappers       0.1     c:\users\administrator\onedrive\bf4\code\qdev-wrappers
StationQ            0.1     c:\users\administrator\onedrive\bf4\code\stationq
v0-characterization 0.0.1   c:\users\administrator\onedrive\bf4\code\v0_characterization
You are using pip version 10.0.1, however version 18.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.

(qcodes3) C:\Users\Administrator>pip uninstall qcodes
Uninstalling qcodes-0.1.11:
  Would remove:
    c:\programdata\anaconda3\envs\qcodes3\lib\site-packages\qcodes.egg-link
Proceed (y/n)? y
  Successfully uninstalled qcodes-0.1.11
You are using pip version 10.0.1, however version 18.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.

(qcodes3) C:\Users\Administrator>cd OneDrive\BF4\Code\Qcodes

(qcodes3) C:\Users\Administrator\OneDrive\BF4\Code\Qcodes>pip install -e .
Obtaining file:///C:/Users/Administrator/OneDrive/BF4/Code/Qcodes
    Complete output from command python setup.py egg_info:
    get_version: 0.1.11
    running egg_info
    writing qcodes.egg-info\PKG-INFO
    writing dependency_links to qcodes.egg-info\dependency_links.txt
    writing requirements to qcodes.egg-info\requires.txt
    writing top-level names to qcodes.egg-info\top_level.txt
    reading manifest file 'qcodes.egg-info\SOURCES.txt'
    writing manifest file 'qcodes.egg-info\SOURCES.txt'
    Traceback (most recent call last):
      File "<string>", line 1, in <module>
      File "C:\Users\Administrator\OneDrive\BF4\Code\Qcodes\setup.py", line 109, in <module>
        module = import_module(module_name)
      File "C:\ProgramData\Anaconda3\envs\qcodes3\lib\importlib\__init__.py", line 126, in import_module
        return _bootstrap._gcd_import(name[level:], package, level)
      File "<frozen importlib._bootstrap>", line 994, in _gcd_import
      File "<frozen importlib._bootstrap>", line 971, in _find_and_load
      File "<frozen importlib._bootstrap>", line 955, in _find_and_load_unlocked
      File "<frozen importlib._bootstrap>", line 665, in _load_unlocked
      File "<frozen importlib._bootstrap_external>", line 678, in exec_module
      File "<frozen importlib._bootstrap>", line 219, in _call_with_frames_removed
      File "C:\ProgramData\Anaconda3\envs\qcodes3\lib\site-packages\pyqtgraph\__init__.py", line 13, in <module>
        from .Qt import QtGui
      File "C:\ProgramData\Anaconda3\envs\qcodes3\lib\site-packages\pyqtgraph\Qt.py", line 44, in <module>
        raise Exception("PyQtGraph requires one of PyQt4, PyQt5 or PySide; none of these packages could be imported.")
    Exception: PyQtGraph requires one of PyQt4, PyQt5 or PySide; none of these packages could be imported.

    *****
    ***** package matplotlib must be at least version 2.2.3.
    ***** Please upgrade it (pip install -U matplotlib or conda install matplotlib)
    ***** in order to use MatPlot
    *****

    ----------------------------------------
Command "python setup.py egg_info" failed with error code 1 in C:\Users\Administrator\OneDrive\BF4\Code\Qcodes\
You are using pip version 10.0.1, however version 18.1 is available.
You should consider upgrading via the 'python -m pip install --upgrade pip' command.

It looks like this issue is caused by having pyqtgraph installed but not pyqt5. This should normally not happen as the pyqtgraph package depends on pyqt5. In #1316 I changed this check so that it cannot break the install


Ensure meta.yaml and setup.py have consistent requirements

This ensures meta.yaml and setup.py have consistent requirements, which hopefully fixes the travis issue.

huh, looks like theres still an issue with the license? are we sure that this one is the current license?

Nope, the problem is still getting my decryption logic to work correctly:
$encrypted_514505261e50_iv -in oe_license.txt.enc -out oe_license.txt -d; fi
/home/travis/build.sh: line 45: [: choderalab/perses: integer expression expected

OK, tests are working properly now, though @pgrinaway needs to fix a couple of them.


Inconsistent serde implementations

CertificateChain can only be serialized via serde
PrivateKey can't be serialized via serde

I was trying to store the private key and the chain in Bonsai, and I only then discovered PrivateKey doesn't implement serde through that action.
Is there a good reason to not implement it for PrivateKey?

It does over the Dangerous trait, as we discussed before it's probably a terrible solution. So I will change that soon to something simpler.

It does over the Dangerous trait

So it does. I missed that. This does make it significantly easier to provide a wrapper. I close this request :)


Add heartbeat for our (monitoring) runners

Our search service monitor was dying. We didn't know. 😢

done!


Show warning if user has selected public repository instead private for storing notes

There is no restriction on using a public repository for storing notes. But user should be prompted with a warning saying the repository is public and their notes could be accessible publicly when they choose to use a public repo for storing notes.
This is is requires only frontend changes.

@vivekweb2013
Take a look at GitHub's Rest API to obtain the JSON codec list of public repositories.

@omegaui the type of repository is already there in gitnoter repositories response payload. This ticket is about showing the warning on UI if the user selects public repository.

@omegaui the type of repository is already there in gitnoter repositories response payload. This ticket is about showing the warning on UI if the user selects public repository.

I noticed that already,
I don't know go that much to contribute code,
Just wanted to tell the starting point.
Anyways awesome project.

Done


Ensure kcmfonts file is not required to exist.

So I found this by accident: https://aur.archlinux.org/packages/contour-git#comment-850893
I'm not sure what the original problem was, but we should make sure contour works even if that file is not available.

I dont have this file and everything is alright, will close it


CRITICAL FileNotFoundError

Trying to run Astrolauncher on my WindowsServer2016:
AstroLauncher Version 1.8.1
05:34:13 - INFO   'AstroLauncher - Unofficial Dedicated Server Launcher v1.8.1'
05:34:13 - INFO   'If you encounter any bugs please open a new issue at:'
05:34:13 - INFO   'https://github.com/ricky-davis/AstroLauncher/issues'
05:34:13 - INFO   'To safely stop the launcher and server press CTRL+C'
05:34:14 - INFO   'Starting a new session'
05:34:14 - INFO   'Attempting to validate Playfab Certs'
05:34:14 - CRITICAL FileNotFoundError(2, 'Das System kann die angegebene Datei nicht finden', None, 2, None)
But what file can't be find?

Update: On my Windows10 own Build ServerImage (Without Store Apps and DataTools etc.) its working fine!

Can you send the debug.log file?

debug.log
server.log
No better information in the logs :/

Unsure what the issue is, next version of AstroLauncher should be able to provide more error information. Closing for now

Idem
Environment : Win10 ,1607
The AstroServer.exe description


fix: Add Siswati News Classification

Checklist for adding MMTEB dataset

Reason for dataset addition: Cover Siswati in Classification

[x] I have tested that the dataset runs with the mteb package.
[x] I have run the following models on the task (adding the results to the pr). These can be run using the mteb run -m {model_name} -t {task_name} command.

[x] sentence-transformers/paraphrase-multilingual-MiniLM-L12-v2
[x] intfloat/multilingual-e5-small

[x] I have checked that the performance is neither trivial (both models gain close to perfect scores) nor random (both models gain close to random scores).
[x] I have considered the size of the dataset and reduced it if it is too big (2048 examples is typically large enough for most tasks)
[x] I have filled out the metadata object in the dataset file (find documentation on it here).
[x] Run tests locally to make sure nothing is broken using make test.
[x] Run the formatter to format the code using make lint.
[x] I have added points for my submission to the points folder using the PR number as the filename (e.g. 438.jsonl).

Same origin/paper but different csv file.


in semantic segmentation, new brush strokes cover old ones

Describe the bug
When annotating using the semantic segmentation module and choosing a different label, when you choose the previous label again and add to an existing area the brush appears on top of the old one (like in a painting app).
To Reproduce
Steps to reproduce the behavior:
Annotate an area using a label -> annotate a different region using a different label -> annotate the first region again/add to it
Expected behavior
Seems like a bug rather than a feature. I'd expect there to be only one layer of "paint".
Screenshots
If applicable, add screenshots to help explain your problem.
Environment (please complete the following information):

OS: MacOS 11
Label Studio Version 1.1

Additional context
Add any other context about the problem here.

Isn't this what the maxUsages feature is for? I tried testing this out by setting maxUsages="1" and it didn't seem to do anything.


Orchard can't handle placement of the same field name within a single type

I've created a type which has 3 parts. In each of these parts, contains 4 fields with the same technical name which are FirstName, LastName, EmailAddress, and PhoneNumber. I've tried arranging it in placement.info, it doesn't rearrange fields at all. It seems to take all FirstName and group them together, all LastName and group them together, etc. It would be nice if we can separate the placement by content type or part.
This is the config I used in placement.info. I've also attach the content type definition with this issue.
export.xml.txt
Please rename it to export.xml (github doesn't allow attachment of xml extension.)
    <Place Fields_Common_Text__DetailContact__AdditionalApplicationsContactPart__FirstName="Content:1" />
    <Place Fields_Common_Text__DetailContact__AdditionalApplicationsContactPart__LastName="Content:2" />
    <Place Fields_Common_Text__DetailContact__AdditionalApplicationsContactPart__EmailAddress="Content:3" />
    <Place Fields_Numeric__DetailContact__AdditionalApplicationsContactPart__PhoneNumber="Content:4" />
    <Place Fields_Numeric__DetailContact__AdditionalApprenticeshipProgramContactPart__PhoneNumber="Content:5" />
    <Place Fields_Common_Text__DetailContact__AdditionalApprenticeshipProgramContactPart__FirstName="Content:6" />
    <Place Fields_Common_Text__DetailContact__AdditionalApprenticeshipProgramContactPart__LastName="Content:7" />
    <Place Fields_Common_Text__DetailContact__AdditionalApprenticeshipProgramContactPart__EmailAddress="Content:8" />
    <Place Fields_Numeric__DetailContact__AdditionalBidsContactPart__PhoneNumber="Content:9" />
    <Place Fields_Common_Text__DetailContact__AdditionalBidsContactPart__FirstName="Content:10" />
    <Place Fields_Common_Text__DetailContact__AdditionalBidsContactPart__LastName="Content:11" />
    <Place Fields_Common_Text__DetailContact__AdditionalBidsContactPart__EmailAddress="Content:12" />

I tried to reproduce this by importing only export.xml.txt to a vanilla dotnest site. Only the PhoneNumber fields get sorted together: https://testingpartplacement.dotnest.com/test-detail

After some more investigation:
Without any placement.info for these parts, the fields are rendered sanely:

[FieldA from PartAA]
[FieldB from PartAA]
[FieldA from PartBB]
[FieldB from PartBB]

As soon as we add any placement that touches these fields, things go haywire.
With this placement:
<Place Fields_Common_Text__MyContentType__PartAA__FieldA="Content:1" />
<Place Fields_Common_Text__MyContentType__PartAA__FieldB="Content:2" />
<Place Fields_Common_Text__MyContentType__PartBB__FieldA="Content:3" />
<Place Fields_Common_Text__MyContentType__PartBB__FieldB="Content:4" />

instead of the above layout, we get:

[FieldA from PartAA]
[FieldA from PartBB]
[FieldB from PartAA]
[FieldB from PartBB]

@chanond-w please correct me if I'm wrong.

Yes that is correct. Any placements specification that works will group the fields by Field type/name which will render out as you've mentioned

[FieldA from PartAA]
[FieldA from PartBB]
[FieldB from PartAA]
[FieldB from PartBB]

I haven't been able to figure out whether Fields_Common_Text__MyContentType__PartAA__FieldA are valid shapes in this context.


Security CVE-2022-3874

https://scout.docker.com/vulnerabilities/id/CVE-2022-3874?utm_source=desktop&utm_medium=ExternalLink

A command injection flaw was found in foreman. This flaw allows an authenticated user with admin privileges on the foreman instance to transpile commands through CoreOS and Fedora CoreOS configurations in templates, possibly resulting in arbitrary command execution on the underlying operating system.
--
CVSS Score: | 9.1
CVSS Vector: | CVSS:3.1/AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:H
Affected range: | <=3.8.0
Fix version: | Not yet available
Publish date: | 2023-09-22

Saw this come through as well, but it looks like this is being falsely attributed to this gem.
The "foreman" referenced in the CVE is part of Red Hat Satellite.
References:

https://bugzilla.redhat.com/show_bug.cgi?id=2140577
https://theforeman.org/

So weird yeah. How can we dismiss this false tagging of CVE?  :cry:

It looks like it has been withdrawn: https://github.com/advisories/GHSA-9jfq-54vc-9rr2

all good now! it's not showing anymore from the scans! closing this issue.


feat: Port/Data.Seq.Seq

Port of data.seq.seq
A bit of a mess due to the name conflict with Seq (was has_seq
Will delete this and re-do when upstream mathlib#18284 is merged.

leanprover-community/mathlib#18284 is now merged

Closed to re-port after updates on mathlib3 side


Tag Docker images

I see you're tagging releases with git, could you also create Docker tags when you push the image to Docker Hub?

This should now be happening for new tags - @frankh if you bump the minor version tag we should trigger a new build.
I do notice that the Docker Hub build appears to be having issues at the moment: https://hub.docker.com/r/cabotapp/cabot/builds/
Please let's close this when we confirm that tagged builds are going up successfully.

@dbuxton it seems it's trying to run "sut" from docker-compose-test.yml and failing (see: https://docs.docker.com/docker-cloud/builds/automated-testing/). I'll try and fix that
Also, I noticed the docker hub login details aren't in 1password - could you send them to me? (although you really shouldn't be working!)

We've switched to using github.com/cabotapp/docker-cabot to build docker images. It's not automatic yet but docker images are tagged at https://hub.docker.com/r/cabotapp/cabot/


Fix indentation and custom dns names

fix indentation of egressgateway env
fix custom dns name

We had some breakages and circle won't automatically rebase. Can you rebase this?

/test integration-presubmit-isolated-namespaces-kind

/test integration-presubmit-isolated-namespaces-kind


[yocto] update

kirkstone was released today, update other latest releases, fix codename spelling to version used in official docs

@captn3m0  In yocto projects website all codenames are lowercased , maybe we also mimic their system ?

This is the reference table for us now, which uses capitals. I think only the branch names are lowercase, which makes sense.
I think either is fine in this case, and matching the reference table (which we link to) seems fair.


modern client mode behaves differently for including async chunks on initial page load

Version
v2.12.2
Reproduction link
https://github.com/simllll/vue-lazy-hydration/tree/fix/lazy-imports
Steps to reproduce
I just stumbled onto something that looks like a bug, but which is actually kind of a feature request which is possible with this "bug" ;). Sounds weird? Yes, let me explain:
When including async components on a page, they are included in the page assets via script tag immedeitaly on page load. This is actually a problem for things like "lazy-hydration" (https://github.com/maoberlehner/vue-lazy-hydration#advanced) and there is a open PR to solve this (https://github.com/vuejs/vue/issues/9847). While I was looking into this issue, I found out that nuxt does this somehow differently. Even though the VueSSRClientPlugin is used (but some own version of VueSSRServerPLugin..)..I could make the assets load async (and only when needed) in my nuxt project, but as I tried to reproduce this with a little test I came up to the conclusion this is actually a side effect of "modern: client" mode.
When I build my demo app with modern: true:
<script>window.__NUXT__={layout:"default",data:[{}],fetch:[],error:null,serverRendered:true,routePath:"\u002Fintegration"};</script>
<script src="/_nuxt/runtime.js" defer></script>
<script src="/_nuxt/pages/integration.js" defer>
</script><script src="/_nuxt/1.js" defer></script>
<script src="/_nuxt/2.js" defer></script>
<script src="/_nuxt/3.js" defer></script>
<script src="/_nuxt/0.js" defer></script>
<script src="/_nuxt/commons.app.js" defer></script>
<script src="/_nuxt/app.js" defer></script>

The script src includes all my async chunks <script src="/_nuxt/0.js" defer></script>. Similar for modern: false of course, but now with modern: 'client', it produces following code:
<script>window.__NUXT__={layout:"default",data:[{}],fetch:[],error:null,serverRendered:true,routePath:"\u002Fintegration"};</script>
<script>!function(){var e=document,t=e.createElement("script");if(!("noModule"in t)&&"onbeforeload"in t){var n=!1;e.addEventListener("beforeload",function(e){if(e.target===t)n=!0;else if(!e.target.hasAttribute("nomodule")||!n)return;e.preventDefault()},!0),t.type="module",t.src=".",e.head.appendChild(t),t.remove()}}();</script>
<script nomodule src="/_nuxt/legacy-runtime.js" defer></script>
<script type="module" src="/_nuxt/runtime.js" defer></script>
<script nomodule src="/_nuxt/legacy-pages/integration.js" defer></script>
<script type="module" src="/_nuxt/pages/integration.js" defer></script>
<script nomodule src="/_nuxt/legacy-1.js" defer></script>
<script type="module" src="/_nuxt/3.js" defer></script>
<script nomodule src="/_nuxt/legacy-2.js" defer></script>
<script type="module" src="/_nuxt/3.js" defer></script>
<script nomodule src="/_nuxt/legacy-3.js" defer></script>
<script type="module" src="/_nuxt/3.js" defer></script>
<script nomodule src="/_nuxt/legacy-0.js" defer></script>
<script type="module" src="/_nuxt/3.js" defer></script>
<script nomodule src="/_nuxt/legacy-commons.app.js" defer></script>
<script type="module" src="/_nuxt/commons.app.js" defer></script>
<script nomodule src="/_nuxt/legacy-app.js" defer></script>
<script type="module" src="/_nuxt/app.js" defer></script>
  </body>
</html>

Now the html includes some script tags for the chunks, but with a "nomodule" attribute <script nomodule src="/_nuxt/legacy-0.js" defer>. The chunks are not loaded therefore in a "module" supported browser. This is actually what I want to have, therefore super great (y). But unfortunately it still looks kind of a bug, because changing e.g. max chunk size to split up other common chunks, is then broken as the "other" chunks are not loaded in this case.
I also think it should not include "_nuxt/3.js" several times, probably here is the root cause of this bug.
<script type="module" src="/_nuxt/3.js" defer></script>

(is included several times instead of the right asset)
To reproduce this issue, you can check out the git branch https://github.com/simllll/vue-lazy-hydration/tree/fix/lazy-imports (lazy-imports), run npm install in the root and switch to the directory "test/nuxt-integration". Run "nuxt build" and "nuxt start". In this setup, the modern mode is set to client and it actually lazy loads the component when they are needed (just scroll down on the demo page and watch the network tab).
What is expected ?
The behavior should be somehow either be

documented
controllable (which would be GREAT also for the non-modern mode)
work the same way as in the modern: true or modern: false way.

I would vote for number 2, or number 1.. number 3 would break my lovely workaround ;)
What is actually happening?
The async chunks are not loaded when modern is set to "client" mode.

This bug report is available on Nuxt community (#c10607)

@simllll Thank you so much for the detailed issue description.
You're right, the issue is because of modern and legacy bundle files don't map very well because code split on asyn components, I'll try to look into this this weekend, I hope I can figure out a proper way to fix it.
Thanks for the reporting again.

Thanks, let me know if I can help somehow. I guess the root cause is somewhere in the manifest file of the modern build or in the code part where the manifest file is applied in modern client mode. As it seems everything works fine in "modern: true" and "modern: false" mode.


Readme update

Hi! I think we've moved enought in the documentation process to update our beautiful README. In my opinion, two main tasks have to be adressed:

Decide if we change the actual content of the readme (many of this things are now on separate documentation section).
Complete what's left (some code blocks are placeholders, for example)

So we can discuss here how to approach this. My proposal:

First paragraph and quick links stays, but quick links could maybe be at the bottom of the readme.
Use cases look cool there, but I think design principles is info overloading. We can either move it to an existing doc page (Introduction feels right to me).
Main concepts have their own place now to be. We could maintain a copy here too, I'm down to anything here.
Get started coul be a little bit reduced, and placed before main concepts. We would reference the full instructions doc page. I see this get started as a I want to test Rubrix in less than a minute to test something out, and the docs get started as a that was cool! something cool enough for me I even made it to the documentation.
Supported and planned tasks feels right to me here, we give a glance at we have done and what are we working on from the readme.

Tell me what do you think 🤠

My 22 cents:

First paragraph and quick links stays, but quick links could maybe be at the bottom of the readme.
Not sure if Quick links is necessary here, i would put a link to the docs in the first paragraph at the end and remove this section.
Use cases look cool there, but I think design principles is info overloading. We can either move it to an existing doc page (Introduction feels right to me).
I agree, the first paragraph already outlines some use cases. I think in the docs we can elaborate more on use cases.
Main concepts have their own place now to be. We could maintain a copy here too, I'm down to anything here.
+1 for removing this section
Get started coul be a little bit reduced, and placed before main concepts. We would reference the full instructions doc page. I see this get started as a I want to test Rubrix in less than a minute to test something out, and the docs get started as a that was cool! something cool enough for me I even made it to the documentation.
I think the Get started section is fine, not sure if it can be reduced further without missing its purpose. However, i would switch number 1 and 2, that is first install the client, then run docker compose or install the client with the server deps.
Supported and planned tasks feels right to me here, we give a glance at we have done and what are we working on from the readme.
I would substitute this section with something like Next steps, where we put more specific links to our documentation, like to the tutorials, main concepts, supported tasks ...  If we leave development stuff here, i'm afraid they get outdated rapidly. Maybe we can open a thread in Discussions about planned/requested tasks, and leave a link in the readme.

I agree with your proposal and @dcfidalgo suggestions. Please go ahead. My only suggestion would be to add the rubrix_intro.svg diagram close to the top part of the readme as I think it helps to get a kick idea.

Just one more thing not to forget, if we remove Supported tasks please move them into the Get started docs module as a new section and we will improve them over time.

Just one more thing not to forget, if we remove Supported tasks please move them into the Get started docs module as a new section and we will improve them over time.

Yeah, I think Supported task can be moved to Get Started, even as a final destination.

I think the Get started section is fine, not sure if it can be reduced further without missing its purpose. However, i would switch number 1 and 2, that is first install the client, then run docker compose or install the client with the server deps.

@dcfidalgo , I think dani or paco put it in this order because install the client can be skipable if you follow what is now 1b.

@dcfidalgo , I think dani or paco put it in this order because install the client can be skipable if you follow what is now 1b.
You are right, let's just leave it as is.


Problem to use it (CORS)

I'm realy confused about CORS, so, I'm developing front-end with vuejs in localhost:8080 and json-server is runing in another port (9000)
When I do request with axios and add some header I got this:

So I also created a middleware
server.use((req, res, next) => {
  res.header('Access-Control-Allow-Origin', '*');
  res.header('Access-Control-Allow-Headers', 'authorization');
  res.header('Access-Control-Request-Headers', 'authorization');
  res.header('Access-Control-Allow-Methods', 'GET');
  res.header('Access-Control-Request-Methods', 'GET');
  if (req.path == '/api/auth/login') {
    next();
  } else {
    if (isAuthorized(req)) { // add your authorization logic here
      next() // continue to JSON Server router
    } else {
      res.sendStatus(401)
    }
  }
})

I have added this lines trying to allow the request
  res.header('Access-Control-Allow-Origin', '*');
  res.header('Access-Control-Allow-Headers', 'authorization');
  res.header('Access-Control-Request-Headers', 'authorization');
  res.header('Access-Control-Allow-Methods', 'GET');
  res.header('Access-Control-Request-Methods', 'GET');

and just simple function to compare and authorize
const isAuthorized = (req) => {
  // console.log(req.headers)
  return (req.headers.authorization == 'Bearer: ' + token);
}

can you help me please? I don't know if I need to add 'Access-Control-Allow-Origin' in json-server response or in axios, one more detail, is I'm using with default options const server = jsonServer.create()

@hjJunior I know you closed this. Did you find a solution? I'm running into this as well.

@hjJunior I know you closed this. Did you find a solution? I'm running into this as well.

did you find anything? We found out that we have same issue (and with a tiomcat server).

@hjJunior : hello, I'm running into the same problem, did you find a solution ? Or any other workaround ? The point is, we need to access our app from the outside and not from localhost.

I'm having the same problem

I managed to get this to work
i have this in index.js on my server
const jsonServer = require('json-server');
const server = jsonServer.create();
const router = jsonServer.router('db.json');
const middlewares = jsonServer.defaults();
const cors = require('cors');

server.use(
    cors({
        origin: true,
        credentials: true,
        preflightContinue: false,
        methods: 'GET,HEAD,PUT,PATCH,POST,DELETE',
    })
);
server.options('*', cors());

server.use(middlewares);
server.use(router);
server.listen(3000, () => {
    console.log('JSON Server is running');
});

and in my client (I'm using Vue and axios) `./src/api/axios.js'
import axios from 'axios'

axios.defaults.withCredentials = true

const instance = axios.create({
    baseURL: 'http://<IP_ADDRESS>:3000',
    // withCredentials: true,
})
export default instance

and then in Vue: main.js I have
// [...]
import axios from '@/api/axios'
import VueAxios from 'vue-axios'
// [...]
Vue.prototype.$axios = axios
Vue.use(VueAxios, axios)
// [...]

and then in my vue component
                results = await this.$axios.request({
                    method: 'get',
                    url: this.axios.url + `/${id}`,
                })

@hafdon hi but my
app.use(auth); is not alone it has const auth = require("json-server-auth");

Make the course settings according to the following example:
// server.js
const jsonServer = require("json-server");
const server = jsonServer.create();
const router = jsonServer.router("db.json");
const middlewares = jsonServer.defaults();
const cors = require("cors");

server.use(middlewares);
server.use(router);
server.use(
  cors({
    origin: true,
    credentials: true,
    preflightContinue: false,
    methods: "GET,HEAD,PUT,PATCH,POST,DELETE",
  })
);
server.options("*", cors());
server.listen(3001, () => {
  console.log("JSON Server is running");
});

Terminate the server through the terminal and then clear your browser cache and cookies and run the server again.

I know this is closed but if it helps someone - I was able to resolve this on macOS without creating a dedicated server.js. By turning off AirPlay receiver. I was using json-server on port 5000 and it turned out the AirPlay receiver also listens on this port somehow causing the CORS errors.


remove package-lock.json in packages

The Root package-lock.json is still in the repository. Is that intentional?

Yes, other lerna managed repos I looked at retain the root lock file. Babel, for example.


Fee selection UI

-> time estimates
-> CAD fee estimates
-> Clarify that the fee is in sats/vbyte

For reference the fiat amount is based on a default config of 140 vbytes, as it is the standard for Mempool
Calculation for fiat:
[(feerate * 140)/100000000] * fiat price
example:

Assuming 10 sat/vbyte rate
140 constant
1 BTC = 100 000 000 sats
Bitcoin price of $30,000

[(10 sat/vbyte * 140 vbytes )/10000000] * 30000 =  0.42$

Fixed in 0.1.89-02


add layout component @xelaok/svelte-media-query

https://github.com/xelaok/svelte-media-query

That's a great little component, thank you!


EF remove entity when use automapper to update entity properties

Describe what is not working as expected.
I use following code to update an entity in the database
var currentMed = await context.Media.FindAsync(srcMed.Id);
mapper.Map(srcMed, currentMed);
await context.SaveChangesAsync();

This approach works in one context but not another. I think it was the AutoMapper mapping cause this. What condition make EF to delete an entity except call delete method.
Funny thing is when I get
var entry = await context.Entry(currentMed);

the state of entry is actually Modified not Deleted.
Further technical details
EF Core version: 1.1.2
Database Provider: Microsoft.EntityFrameworkCore.SqlServer
Operating system: Windows 10
IDE: Visual Studio 2017

EF Team Triage: This issue is lacking enough information for us to be able to effectively investigate it. In particular, it is missing the following information requested in the new issue template. Can you please provide this information?

Steps to reproduce

Ideally include a complete code listing that we can run to reproduce the issue.
Alternatively, you can provide a project/solution that we can run.
Note that this does not have to be your actual production code--in fact the more it can be simplified the better--but it must demonstrate the issue you are seeing.

BTW we're not just doing this to be mean :smile:... we get a lot traffic on this project and it takes time to attempt to reproduce an issue based on fragments of information. In addition, our attempt is often unsuccessful as the exact conditions required to hit the issue are often not explicitly included in the code provided. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we ask that folks give us a self-contained way to reproduce an issue.
For a guide on submitting good bug reports, read Painless Bug Tracking.
BTW this is a canned response and may have info or details that do not directly apply to this particular issue. While we'd like to spend the time to uniquely address every incoming issue, we get a lot traffic on the EF projects and that is not practical. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we use canned responses for common triage decisions.

Hi @ajcvickers, thank you for your reply. I think I figured out what is the issue. It was my fault.
I have a foreign key [ForeignId] and also [ForeignObject] in this class. When I map the object. I only map the [ForeignId] and leave the [ForeignObject] null which cause the object to be removed from database.


[master]fix custom brand when subscription enabled

#3861 - the head function setting the title wasn't using getVendor with the SUSE brand enabled so I rectified that here. I thought that getVendor returned 'SUSE Rancher' or something similar with the subscription key provided, but I don't see any code for that hanging around... @nwmac do you know if that was intentionally removed?

@mantis-toboggan-md don't know if this was intentionally removed.


How to Get dalle 2 big image ai cookies

???

it's by default have Dalle 2 with /img command btw you also can use Bing Dalle with /art if you want to setup Read This

i hope you fix :)


All config variables are shown to user when server raise 500 and DEBUG=True

When DEBUG=True and server raise 500 , all config variables and their values are shown to user. How to fix that?

I guess you can set DEBUG to False. The objective of DEBUG is to show the variables and values so you can debug them.

I guess you can set DEBUG to False. The objective of DEBUG is to show the variables and values so you can debug them.

I need config variables mustn't be shown to other users at any time and any case even when DEBUG=True
Is it possible


start provider failed

following this guide  ,I try to start the HTTP server capability provider,but it nothing happens, and the actor’s status is null.
What could be the reason?

One of the first places we want to look, if something doesn't work as expected, is in the host logs. Did you see any errors there? Were there any errors from the wash commands?
If the logs aren't clear, you can paste them here and we can help decode them.

I solved this problem by changed the version to wasmcloud.azurecr.io/httpserver:0.13.1

@shikingram did you find a solution for this issue? Just want to make sure you got it working 😄


Make STATIC=true part of nuxtent generate

Is there any documentation on what this does? When I run 'yarn generate' after putting 'STATIC=true' in my nuxtent.config.js, the blog portion of the site fails. Is 'nuxtent generate' and upcoming command to still allow the site to be exported statically? Thanks for the clarification!

For now instead of nuxt generate you can run STATIC=true nuxtent generate

Next version only requires nuxtent generate as the command.  Static=true is set automatically.

When I run STATIC=true yarn nuxtent generate, I get a type error. I'm using the template linked in the ReadMe and I have updated. Works perfectly when running in dev. Maybe I'm still misunderstanding the command?
node_modules/nuxtent/bin/nuxtent-generate:57

const nuxt = new Nuxt(options)
             ^

No you're using it correctly now. Sorry for the complications, Nuxt is in a transitionary phase so you have to be mindful of versions you're using. Make sure you're using the lastest nuxt version if you want to to generate static version of site via nuxtent command (however, you won't be able to use markdown components yet with this version).

run npm install<EMAIL_ADDRESS>

Hm. Just updated to the beta and it built fine, but I then got a network error when I navigated to the markdown blogs when running in Dev, and also the same thing when testing the generated version on a webserver. I'm going to assume I messed up the template at some point and try again tomorrow from scratch.
Thank you for the guidance on this issue and all the work you've put into this module! I love the concept as an alternative to static site generators.

Feel free to open up a new issue with the error information otherwise.
There is a 404 error caused by hot module reloading that I was getting as well, so it might be the same issue. I intend to fix it since it's annoying to see on the terminal but it shouldn't prevent the content from beign fetched and rendered.


feat: add initial support for FUSE

This PR adds:

CLI flags for fuse and fuse-temp-dir
A check if the OS supports FUSE
a FUSE server that serves a README
Support for closing the FUSE server

The next PR(s) will include:

returning a symlink to a Unix domain socket that is connected to the Cloud SQL instance
(maybe) support for "warming up" instance connection names in FUSE mode

Woops wrong branch, recreating this.


Remove unused/unsupported code now that the Central Repository feature is released

Bug description
After introducing the Central Repository feature, there is a lot of code paths that are no longer supported.
That code was kept as the Central Repository feature evolved, but now that it has been released, those code paths just complicate the code base for nothing.
Things that can be removed:

usage of  context-target-v2 and no-central-repo-test-only feature flags, and all associated and unused code.  The CLI does not support changing the default value of either of these feature flags.
unused GCP discovery source

Expected behavior
Unused/unsupported code paths are removed to simplify the code base.

A bunch of cleanup was done for v1.1.0 but there is still a bit more than can be done.
I'll keep this open for v1.2.0


Op-pocalypse now

Implement remaining binary ops. Fixes #59.

I endorse both the new operators and the pun.


With 'smudge --skip', if the file exists in cache use it?

TLDR: I like running with --skip by default to prevent the slow serial downloads, but it's inconvenient to have to always run 'git lfs pull' even when the objects are already cached locally. Please consider either changing the behavior of --skip or adding another flag that avoids downloads during smudge (outputting the placeholder in this case), but still smudges if the object is available in cache.
Long version:
Currently, with smudge --skip, you'll still get the lfs placeholder file even if you already had the file in your .git/lfs/objects cache.
It's mainly the download that hurts me in terms of wait time, so I'd prefer if there were a way to skip just downloading during smudge, but go ahead and do the smudge if the file already exists in the .git/lfs/objects cache. This way, if i do a 'git checkout tree-ish' and the lfs objects are already cached locally, they'll be smudged in. For files that aren't available in cache, I should still get a placeholder.
As far as I'm concerned the behavior of smudge --skip could just be changed to work this way, but if there's some reason for having a way to totally disable smudging (even when the file is cached), another flag such as --skip-downloads could be added.

I opened a pull request for this, #831

Merged a fix, closing this.


folders creation nautilus

I am using rmfuse 0.2.3 on arch linux with gnome. rmfuse works fautless in the terminal, but using nautilus strange things are occurring. for example folders with more than one character can not be created. also the created folders with one character are not synced correctly. most probably this is not a direct rmfuse issue, but more a fuse mount option issue. other fuse file systems are working as expected (sshfs, gocryptfs, ...).
thanks for any help!

This can be fixed with #38


[Easy] Make path_graph_structure the default output_structure in approx_itensornetwork

Codecov Report

Merging #82 (64916f6) into main (0673f07) will decrease coverage by 1.31%.
The diff coverage is n/a.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main      #82      +/-   ##
==========================================
- Coverage   77.61%   76.30%   -1.31%
==========================================
  Files          61       61
  Lines        3243     3056     -187
==========================================
- Hits         2517     2332     -185
+ Misses        726      724       -2

Impacted Files
Coverage Δ

src/approx_itensornetwork.jl
97.81% <ø> (-0.11%)
:arrow_down:

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

Thanks!


Introduce more tmux options

This introduces more options for spotify status display in tmux:

#{spotify_song} -> #{spotify_status}
#{spotify_song}
#{spotify_artist}
#{spotify_album}
#{spotify_playback}

This builds on top of pwittchen/spotify-cli-linux#26

Thanks for this PR! It may be useful. We can merge it once we deal with the PR in spotifycli project. In this case, it also would be nice if you could squash your commits into one.

Thanks for the quick response! I'll test and review it soon.


Add Redirection and AutoProgressBar components

EX-4297

I found a problem:

Search from black friday
Before the  UserClickedARedirection will be emitted, type a new query.
The event of the redirection will be launched anyways.

Maybe we can listen the event UserAcceptedAQuery and clear the setInterval? What do you think?


Change misleading claims description

This sentence is highly misleading.  Claims can contain "permission" information, there is no issue with this, and this article even goes on to talk about "role claims" which are permission information.

It doesn't say what they can do tho ... it only provides information to the system that will authorize them for what they can do. If a role claim says that the user is in the "admin" role, it really doesn't say anything about what an "admin" can do after being authenticated, and it certainly can be different app-to-app for exactly the same claim.

OK, but that's still a misleading sentence.  It makes it sound like the information in a claim isn't related to determining what a user can do.  Saying a user is in an "admin" role, or even that they have "edit X permission" is clearly related to determining what they can do, and a system may even not need to go to a database to determine what they can do based on this information.


How can this problem be solved?

File "train.py", line 198, in
main()
File "train.py", line 114, in main
model = build_network(model_cfg=cfg.MODEL, num_class=len(cfg.CLASS_NAMES), dataset=train_set)
File "/home/abc/下载/VFF-main/pcdet/models/init.py", line 18, in build_network
model_cfg=model_cfg, num_class=num_class, dataset=dataset
File "/home/abc/下载/VFF-main/pcdet/models/detectors/init.py", line 30, in build_detector
model_cfg=model_cfg, num_class=num_class, dataset=dataset
File "/home/abc/下载/VFF-main/pcdet/models/detectors/voxel_rcnn_fusion.py", line 7, in init
self.module_list = self.build_networks()
File "/home/abc/下载/VFF-main/pcdet/models/detectors/detector3d_template.py", line 49, in build_networks
model_info_dict=model_info_dict
File "/home/abc/下载/VFF-main/pcdet/models/detectors/detector3d_template.py", line 64, in build_vfe
depth_downsample_factor=model_info_dict['depth_downsample_factor']
File "/home/abc/下载/VFF-main/pcdet/models/backbones_3d/vfe/image_point_vfe.py", line 18, in init
self.build_modules()
File "/home/abc/下载/VFF-main/pcdet/models/backbones_3d/vfe/image_point_vfe.py", line 25, in build_modules
module = getattr(self, 'build_%s' % module_name)()
File "/home/abc/下载/VFF-main/pcdet/models/backbones_3d/vfe/image_point_vfe.py", line 64, in build_f2v
disc_cfg=self.disc_cfg
File "/home/abc/下载/VFF-main/pcdet/models/backbones_3d/vfe/image_vfe_modules/f2v/voxel_field_fusion.py", line 34, in init
fuse_layer=model_cfg.LAYER_CHANNEL.keys())
File "/home/abc/下载/VFF-main/pcdet/models/backbones_3d/vfe/image_vfe_modules/f2v/point_to_image_projection.py", line 45, in init
device=device,dtype=torch.float32)
TypeError: create_meshgrid3d() got an unexpected keyword argument 'dtype'

Hi @463727502,
I am also getting same error. Did you found any fix for this error?
Thank you so much!
Regards,
Saket

Please try avoding Chinese letter in you path!


iOS: App stops updating after backgrounding

Steps to reproduce:

Launch Zen Tuner
Notice the current note, marker and pitch all update in real time
Switch to another app, might require an app playing video (e.g. Twitter)
Switch back to Zen Tuner
Notice the current note, marker and pitch are all frozen at the previous values before backgrounding the app

Of course, this happened when removing AudioKit somewhere in https://github.com/jpsim/ZenTuner/compare/36046b6...43038e2


Russian Peasant Algorithm

Have you read the Contributing Guidelines on Pull Requests?
Yes
Description
Russian Peasant algorithm to multiply two long numbers.
Checklist

[Y ] I've read the contribution guidelines.
[Y] I've checked the issue list before deciding what to submit.
[Y] I've edited the README.md and link to my code.

Related Issues or Pull Requests
#978

Kindly review this PR @iamrajiv @plazzy99 @Kajol-Kumari @atarax665 @SKAUL05

kindly review this PR @iamrajiv

kindly merge this PR it has 3 reviews @iamrajiv