How to make use of the json bot instructions?

I'm looking to get a bot that can follow a specific build order. Is there an existing bot that can import the json generated by "Copy SC2 Bot Instructions"? Or are we suppose to build a custom bot using https://github.com/BurnySc2/python-sc2 with the json as input, and run each action based on the frame index?

One such parser was created to cover a number of edge cases: https://github.com/DrInfy/sharpy-sc2/blob/47c157ac6724603ef5a5028b9d00eba28817350a/tools/json_build.py
But so far I don't know of any bot that implements it, as I suppose it is a bad strategy to hardcode build orders like that, because then the bot might get stuck. E.g. your bot gets cannon rushed and want to expand, it keeps sending down workers to try to expand.


HDDS-3667. If we gracefully stop datanode it would be better to notify scm and r…

What changes were proposed in this pull request?
The datanode handles the signal and sends the stop dn request to scm, then scm update datanode state to dead.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-3667.
How was this patch tested?
manual tests.
1、When the command bin/ozone --daemon stop datanode is executed, datanode can immediately become dead in scm.
2、when scm is down，datanode can be stopped by the command.

the failed pre-check is unrelated to this patch.

Codecov Report

Merging #1033 into master will decrease coverage by 0.06%.
The diff coverage is 28.33%.

@@             Coverage Diff              @@
##             master    #1033      +/-   ##
============================================
- Coverage     69.36%   69.29%   -0.07%
- Complexity     9103     9112       +9
============================================
  Files           961      963       +2
  Lines         48127    48244     +117
  Branches       4676     4687      +11
============================================
+ Hits          33381    33430      +49
- Misses        12530    12594      +64
- Partials       2216     2220       +4

Impacted Files
Coverage Δ
Complexity Δ

...ne/container/common/statemachine/StateContext.java
85.02% <ø> (-0.09%)
52.00 <0.00> (-1.00)

...p/ozone/protocol/commands/UnRegisteredCommand.java
0.00% <0.00%> (ø)
0.00 <0.00> (?)

...ntainerDatanodeProtocolClientSideTranslatorPB.java
85.71% <0.00%> (-11.06%)
10.00 <0.00> (ø)

...rg/apache/hadoop/hdds/scm/node/SCMNodeManager.java
84.29% <0.00%> (-2.89%)
55.00 <0.00> (ø)

...oop/hdds/scm/server/SCMDatanodeProtocolServer.java
67.97% <0.00%> (-7.18%)
24.00 <0.00> (ø)

.../apache/hadoop/hdds/scm/node/NodeStateManager.java
73.37% <33.33%> (-1.63%)
42.00 <0.00> (ø)

...common/states/endpoint/UnRegisterEndpointTask.java
44.23% <44.23%> (ø)
4.00 <4.00> (?)

.../java/org/apache/hadoop/ozone/audit/SCMAction.java
100.00% <100.00%> (ø)
2.00 <0.00> (ø)

...r/common/states/datanode/RunningDatanodeState.java
78.57% <100.00%> (-3.25%)
17.00 <0.00> (-2.00)

...otocol/commands/RetriableDatanodeEventWatcher.java
55.55% <0.00%> (-44.45%)
3.00% <0.00%> (-1.00%)

... and 17 more

Continue to review full report at Codecov.

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

/pending See questions from @maobaolong

@leosunli After you are ready for review, please use /ready to restore this PR.

/ready

hi @elek Could you help review this patch？Thank you.

@elek Would you like to take a look at this PR, that's a interesting feature, and it would be a useful feature.

/pending
What advantage do we get by sending a stop signal from the datanode to SCM? This will require additional logic in Node Management code of SCM. If there is not much of value addition, we don't have to add additional complexity in SCM Node Management.
This change will introduce a new path from HEALTHY to DEAD directly (skipping STALE) adding complexity and maintenance overhead.
FYI: @leosunli, State change is not properly handled.

/pending @nandakumar131: "State change is not properly handled"


Add a GetWithTTL method to know the remaining TTL for an item

Fixes #49

I messed the PR after pushing some commits that were intended only for my forked version. I can reopen it with the GetWithTTL stuff if that is something you will be interested on add to your lib.

Yeah, i'm interested. I did see the data calculation inside the 'hot' path, ie. for all users. It might be better to only explicitly caluclate the TTL in the GetWithTTL call or return the expiration time as parameter.

Hi @ReneKroon , I opened the PR. Please take a look at it and let me know your comments #51


(PYL-W0621) Re-defined variable from outer scope

Description
Local variable name hides the variable defined in the outer space, making it inaccesible. It may cause confusion.
Occurrences
There are 3 occurrences of this issue in the repository.
See all occurrences on DeepSource → deepsource.io/gh/BAN-AI-Communications/rfc2217-gateway/issue/PYL-W0621/occurrences/

3rd party / won't fix


Cookbook

Summary
Writing a cookbook style guides for Vue Storefront in ./docs folder
Motivation
This helps a lot for new comers to wrap their heads around how to use Vue Storefront to their advantage.
Guide-level explanation
It explains the step-by-step guides with respect to how to start Vue Storefront from scratch.
It deals with common issues frequently faced by new comers.

Data Imports
Setup Elastic Search
Starting from scratch
Integration with 3rd party
Extend a module
Theming
Dealing with common mistakes and pitfalls
and so on...

Reference-level explanation
This guide follows the proven design for general cookbook which is easy to understand, easy to follow the steps and help users to stay on track with clear solution for certain type of problems.
It contains 4 ~ 5 sections for each recipe (solution), and a handful recipes comprise a chapter.
Sections include :

Preparation
Recipe
Peep into the kitchen (how it works internally)
Chef's secret (protips)

Drawbacks
It takes a lot of time to build a cookbook that is relevant.
Rationale and alternatives

Cookbook is generally known as the best way for helping newbies and new comers get started at all.
Tutorial is good for helping new comers too but cookbook has a variety of helps in a more structured way.

Unresolved questions

You may add/remove topics

Future possibilities
We can build a lot more stuff to help new comers and users who lost in the middle.

I am currently working on Data imports.
Data imports consists of a few recipes including :

Introduction (done)
Data Migration for Elasticsearch (done)
Data pump (doing)
Data imports and tools (not done)

I really love this idea. The first cook book also looks great. Would awesome to have at least first one ready for the 1.10 release (19.06.2019) to show the direction.
Data imports consists of a few recipes including :
Introduction (done)
Data Migration for Elasticsearch (done)
Data pump (done)
--Data imports and tools (canceled)--
You can watch it while it is in progress at here : https://vuepress.andflyaway.now.sh/guide/cookbook/data-import.html

Ch. 3 includes following topics :

Introduction (done)
Install with Docker (doing)
Using Installer
Manual Installation
Storefront CLI at your service
How to debug anything
Install Tool Chains

You can watch it while it is in progress at here : https://vuepress.andflyaway.now.sh/guide/cookbook/data-import.html

Cool!

Opened up a trello board for WIPs
https://trello.com/b/f4URVw5e/vuestorefront

Updated contents of cookbook :
Chapter 1. Data Imports
Chapter 2. Elasticsearch in the context of VS
Chapter 3. Starter pack for new comers (Install)
Chapter 4. Integration with 3rd Party
Chapter 5. Building a Module from scratch
Chapter 6. Theming in depth
Chapter 7. Anti-Patterns & Common Pitfalls
Chapter 8. On DevOps
Chapter 9. Test Driven Development for VS
Chapter 10. Internals internally
Chapter 11. Vue Basics by example of VS


Prometheus ServiceMonitor failing to scrape operator metrics served though kube-proxy HTTPS 8443 port

Bug Report
I'm using operator-sdk 1.5.0 and I'm trying to gather operator metrics without success.
What did you do?
Deployed default operator-sdk v1.5.0 with prometheus metrics enabled at kustomize config level (config/default/kustomization.yaml). I'm using kube-rbac-proxy:v0.5.0 because of issue https://github.com/operator-framework/operator-sdk/issues/4684, but I don't think it affects.

It is being created the expected controller-manager deployment with kube-proxy metrics enabled at port 8443 (I just copy/paste the relevant parts of the deployed yaml):

kind: Deployment
apiVersion: apps/v1
metadata:
  name: prometheus-exporter-operator-controller-manager
  namespace: prometheus-exporter
   spec:
      containers:
        - name: kube-rbac-proxy
          image: 'gcr.io/kubebuilder/kube-rbac-proxy:v0.5.0'
          args:
            - '--secure-listen-address=<IP_ADDRESS>:8443'
            - '--upstream=http://<IP_ADDRESS>:8080/'
            - '--logtostderr=true'
            - '--v=10'
          ports:
            - name: https
              containerPort: 8443
              protocol: TCP
          resources: {}
          terminationMessagePath: /dev/termination-log
          terminationMessagePolicy: File
          imagePullPolicy: IfNotPresent
        - name: manager
...
          env:
            - name: ANSIBLE_GATHERING
              value: explicit
            - name: WATCH_NAMESPACE
              valueFrom:
                fieldRef:
                  apiVersion: v1
                  fieldPath: 'metadata.annotations[''olm.targetNamespaces'']'
          imagePullPolicy: IfNotPresent
          terminationMessagePolicy: File
          image: 'quay.io/3scale/prometheus-exporter-operator:v0.3.0'
          args:
            - '--metrics-addr=<IP_ADDRESS>:8080'
            - '--enable-leader-election'
            - '--leader-election-id=prometheus-exporter-operator'
...

It is being created the expected metrics Service:

kind: Service
apiVersion: v1
metadata:
  name: prometheus-exporter-operator-controller-manager-metrics-service
  namespace: prometheus-exporter
  labels:
    control-plane: controller-manager
    operators.coreos.com/prometheus-exporter-operator.prometheus-exporter: ''
spec:
  ports:
    - name: https
      protocol: TCP
      port: 8443
      targetPort: https
  selector:
    control-plane: controller-manager
  clusterIP: <IP_ADDRESS>
  type: ClusterIP
  sessionAffinity: None

It is being created the expected ServiceMonitor:

apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
  name: prometheus-exporter-operator-controller-manager-metrics-monitor
  namespace: prometheus-exporter
  labels:
    control-plane: controller-manager
spec:
  endpoints:
    - path: /metrics
      port: https
  selector:
    matchLabels:
      control-plane: controller-manager

What did you expect to see?
ServiceMonitor achieves to scrape operator metrics (an so, metric up=1).
What did you see instead? Under which circumstances?
Service monitor failing (metric up=0):
up{container="kube-rbac-proxy",endpoint="https",instance="<IP_ADDRESS>:8443",job="prometheus-exporter-operator-controller-manager-metrics-service",namespace="prometheus-exporter",pod="prometheus-exporter-operator-controller-manager-669f6fbdcc2jbm7",prometheus="openshift-user-workload-monitoring/user-workload",service="prometheus-exporter-operator-controller-manager-metrics-service"} | 0

Environment
Operator type:

/language ansible

Kubernetes cluster type: Openshift v4.6
$ operator-sdk version
operator-sdk version: "v1.5.0", commit: "98f30d59ade2d911a7a8c76f0169a7de0dec37a0", kubernetes version: "1.19.4", go version: "go1.15.5", GOOS: "linux", GOARCH: "amd64"

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"16+", GitVersion:"v1.16.13-dispatcher", GitCommit:"fd22db44e150011eccc8729db223945384460143", GitTreeState:"clean", BuildDate:"2020-07-24T07:27:52Z", GoVersion:"go1.13.9", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"20", GitVersion:"v1.20.0+bd9e442", GitCommit:"bd9e4421804c212e6ac7ee074050096f08dda543", GitTreeState:"clean", BuildDate:"2021-02-11T23:05:38Z", GoVersion:"go1.15.5", Compiler:"gc", Platform:"linux/amd64"}

Possible Solution
N/A
Additional context
If I connect to the controller-manager, manager container, I can check the metrics served through manager protected port 8080 (only available at <IP_ADDRESS>):
$ kubectl exec -it prometheus-exporter-operator-controller-manager-669f6fbdcc2jbm7 -c manager -- /bin/bash

bash-4.4$ curl <IP_ADDRESS>:8080/metrics
# HELP ansible_operator_build_info Build information for the ansible-operator binary
# TYPE ansible_operator_build_info gauge
ansible_operator_build_info{commit="98f30d59ade2d911a7a8c76f0169a7de0dec37a0",version="v1.4.0+git"} 1
# HELP ansible_operator_reconcile_result Gauge of reconciles and their results.
# TYPE ansible_operator_reconcile_result gauge
ansible_operator_reconcile_result{GVK="monitoring.3scale.net/v1alpha1, Kind=PrometheusExporter",result="succeeded"} 6
# HELP ansible_operator_reconciles How long in seconds a reconcile takes.
# TYPE ansible_operator_reconciles histogram
ansible_operator_reconciles_bucket{GVK="monitoring.3scale.net/v1alpha1, Kind=PrometheusExporter",le="0.005"} 6
...

However, if I try to access to the port published through the kube-proxy port, it fails (both http/https schema), which I guess is what prometheus is trying to do with the deployed ServiceMonitor, so failing):
bash-4.4$ curl <IP_ADDRESS>:8443/metrics
Client sent an HTTP request to an HTTPS server.

bash-4.4$ curl https://<IP_ADDRESS>:8443/metrics
curl: (60) SSL certificate problem: self signed certificate in certificate chain
More details here: https://curl.haxx.se/docs/sslcerts.html

curl failed to verify the legitimacy of the server and therefore could not
establish a secure connection to it. To learn more about this situation and
how to fix it, please visit the web page mentioned above.

Maybe there are 2 problems?

Current ServiceMonitor tries to scrape using HTTP schema, but the port is offering HTTPS?
In addition, although ServiceMonitor uses HTTPS schema (not the case), the certificate is selfsigned, and maybe prometheus would refuse it anyway?

Hello, I had the exact same problem and it brought me a lot of headache. Try the following:
apiVersion: monitoring.coreos.com/v1
kind: ServiceMonitor
metadata:
  name: prometheus-exporter-operator-controller-manager-metrics-monitor
  namespace: prometheus-exporter
  labels:
    control-plane: controller-manager
spec:
  endpoints:
    - path: /metrics
      port: https
      bearerTokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token
      tlsConfig:
        insecureSkipVerify: true
  selector:
    matchLabels:
      control-plane: controller-manager

Thanks for posting that solution @criscola, actually your suggestion makes total sense.
I have applied that change and deploy it:
$ git diff
diff --git a/config/prometheus/monitor.yaml b/config/prometheus/monitor.yaml
index 1b44d4f..a5bd8b1 100644
--- a/config/prometheus/monitor.yaml
+++ b/config/prometheus/monitor.yaml
@@ -11,6 +11,10 @@ spec:
   endpoints:
     - path: /metrics
       port: https
+      scheme: https
+      bearerTokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token
+      tlsConfig:
+        insecureSkipVerify: true
   selector:
     matchLabels:
       control-plane: controller-manager

$ make deploy
cd config/manager && /home/slopez/bin/kustomize edit set image controller=quay.io/3scale/prometheus-exporter-operator:v0.3.0
/home/slopez/bin/kustomize build config/manual | kubectl apply -f -
namespace/prometheus-exporter-operator-system created
customresourcedefinition.apiextensions.k8s.io/prometheusexporters.monitoring.3scale.net created
serviceaccount/prometheus-exporter-operator-controller-manager created
role.rbac.authorization.k8s.io/prometheus-exporter-operator-leader-election-role created
role.rbac.authorization.k8s.io/prometheus-exporter-operator-manager-role created
clusterrole.rbac.authorization.k8s.io/prometheus-exporter-operator-metrics-reader created
clusterrole.rbac.authorization.k8s.io/prometheus-exporter-operator-proxy-role created
rolebinding.rbac.authorization.k8s.io/prometheus-exporter-operator-leader-election-rolebinding created
rolebinding.rbac.authorization.k8s.io/prometheus-exporter-operator-manager-rolebinding created
clusterrolebinding.rbac.authorization.k8s.io/prometheus-exporter-operator-proxy-rolebinding created
service/prometheus-exporter-operator-controller-manager-metrics-service created
deployment.apps/prometheus-exporter-operator-controller-manager created
servicemonitor.monitoring.coreos.com/prometheus-exporter-operator-controller-manager-metrics-monitor created

But now prometheus cannot scrape the operator, before I had prometheus up=0 because the target was down, but now nothing, like if prometheus is ignoring that ServiceMonitor after applying that 3 changes.
It might be caused by a total unrelated problem regarding the monitoring stack I'm using, which is the openshift user-workload-monitoring stack (let's say, the official way of monitoring user workloads on openshift).
If I get into a prometheus pod from openshift user-workload-monitoring stack (for example container config-reloaded), and I execute the curl that prometheus should use with configured the Servicemonitor`,  it works fine and I can get the metrics:
$ oc project openshift-user-workload-monitoring
Now using project "openshift-user-workload-monitoring" on server "https://api.....net:6443".

$ oc get pods
NAME                                   READY   STATUS    RESTARTS   AGE
prometheus-operator-849fdfdcb5-ktqjd   2/2     Running   0          29d
prometheus-user-workload-0             4/4     Running   1          29d
prometheus-user-workload-1             4/4     Running   1          2d22h
thanos-ruler-user-workload-0           3/3     Running   3          29d
thanos-ruler-user-workload-1           3/3     Running   3          29d

$ kubectl exec -it prometheus-user-workload-1 -c config-reloader -- /bin/bash

bash-4.4$ cat /var/run/secrets/kubernetes.io/serviceaccount/token
qy......xAba

bash-4.4$ curl --insecure https://prometheus-exporter-operator-controller-manager-metrics-service.prometheus-exporter-operator-system.svc.cluster.local:8443/metrics -H "Authorization: Bearer qy......xAba"
# HELP ansible_operator_build_info Build information for the ansible-operator binary
# TYPE ansible_operator_build_info gauge
ansible_operator_build_info{commit="98f30d59ade2d911a7a8c76f0169a7de0dec37a0",version="v1.4.0+git"} 1
# HELP controller_runtime_active_workers Number of currently used workers per controller
# TYPE controller_runtime_active_workers gauge
controller_runtime_active_workers{controller="prometheusexporter-controller"} 0
....

However it seems that the prometheus is ignoring the ServiceMonitor because of having the bearerTokenFile field defined. If I remove that field from the ServiceMonitor, prometheus scrape fails (normal), but a least I can see hat prometheus is trying to scrape it with giving up=0, but once I add the bearerTokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token there is nothing.

I have checked that new operator-sdk:v1.6.1 (from yesterday) already implements the suggested ServiceMonitor modifications at https://github.com/operator-framework/operator-sdk/pull/4680:
+      scheme: https
+      bearerTokenFile: /var/run/secrets/kubernetes.io/serviceaccount/token
+      tlsConfig:
+        insecureSkipVerify: true

And I have found that my particular problem is caused because using Openshift User Workload Monitoring stack, Iif I get into on prometheus-operator pod logs, I can see the following warning:
level=warn ts=2021-04-15T14:55:59.541363474Z caller=operator.go:1636 component=prometheusoperator msg="skipping servicemonitor" error="it accesses file system via bearer token file which Prometheus specification prohibits" servicemonitor=prometheus-exporter-operator-system/prometheus-exporter-operator-controller-manager-metrics-monitor namespace=openshift-user-workload-monitoring prometheus=user-workload

So the ServiceMonitor with the bearerTokeFile field is ignored (skipped), because of prometheus configuration, it is prohibited.
After commenting it with Openshift monitoring team, it is skiped because of arbitraryFSAccessThroughSMs, which it is set   to false to limit potential security issues (to not let scraped targets to get access to the prometheus service account's token).
They suggested me to maybe use bearerTokeSecret instead of bearerTokeFile, but after doing myself a couple of tests (and without being an expert on the matter), I see a couple of issues:

From one side, bearerTokenSecret requires the name of a secret, and secrets holding the tokens from ServiceAccounts have random objects names (so there is no way to know the name of the secret before creating the ServiceAccount, and operator-sdk requires predictability of object names for the scaffolding)
In addition, normally operator use Roles (not ClusterRoles), and it seems that the permission required can only be added to ClusterRoles (- nonResourceURLs:  - /metrics / verbs: - get)

In addition, Openshift monitoring team told me that we should  bear in mind that using bearer tokens for metrics authn puts additional load on the API server and they are looking at replacing this by client TLS auth in the future (it's being discussed here: https://github.com/openshift/enhancements/pull/701)
For the moment I will just remove the proxy in front the operator (to be able to access operator metrics without any problem using the Openshift UWM).
So from my point of view issue can be closed now (there is no problem with operator-sdk), but I will let operator-sdk team to decide what to do, because current ServiceMonitor definition won't work on Openshift User Workload Monitoring (the official monitoring stack from Openshift), and maybe I'm missing something, can you think in a way to authenticate to the metrics endpoint that not requires a cluster role or accessing a generated secret?

just to share for who will be able to check out and help here. The PR change the related scaffolds so might be valid to check
https://github.com/kubernetes-sigs/kubebuilder/pull/2065 this with the latest scaffold as well.


Add unsubscribe logic

Just to clarify things a bit: what the stop logic means in this context? Is it unsubscribe?

Yep, naming's hard :D


[public link]File converted into folder when copying folder into file

Description
When we copy a folder (e.g testFolder) within a public link folder to a folder which has same name as an already existing file (e.g copy1.txt), then the new copied folder overwrites the previously existing file of same name. Something similar happens in https://github.com/owncloud/core/issues/37683, but here the difference is that even though the HTTP status code is 204 when we check fort the content for copy1.txt it is same as the original which means it was not overwritten and there is no file copy1.txt/testfile.txt.
Steps to reproduce

Create a user Alice
User Alice creates a folder PARENT1
User Alice creates another folder PARENT1/testFolder
User Alice uploads a file with content some data to PARENT1/testFolder/testfile.txt
User Alice uploads a file with content some data 1 to PARENT1/copy1.txt
User Alice creates a public link share with path PARENT1 and permissions read,update,create,delete
[User gets a token in the response eg:YZgUPJKKDhbi]
The public copies folder testFolder to copy1.txt using new public webdav api:

curl -X COPY -H "Destination: https://localhost:9200/remote.php/dav/public-files/YZgUPJKKDhbi/copy1.txt" 'https://localhost:9200/remote.php/dav/public-files/YZgUPJKKDhbi/testFolder' -k -v

Expected behaviour
A 403 Forbidden error
Actual behaviour
 HTTP/1.1 204 No Content
 Access-Control-Allow-Origin: *
 Content-Security-Policy: default-src 'none';
 Date: Mon, 13 Jul 2020 09:22:09 GMT
 Vary: Origin
 X-Content-Type-Options: nosniff
 X-Download-Options: noopen
 X-Frame-Options: SAMEORIGIN
 X-Permitted-Cross-Domain-Policies: none
 X-Robots-Tag: none
 X-Xss-Protection: 1; mode=block

Checking Content
To make sure if the file has been overwritten:
curl -X GET http://localhost:9140/remote.php/webdav/PARENT1/copy1.txt -u alice:1234 -k
some data 1%

curl -X GET http://localhost/core/remote.php/webdav/PARENT1/copy1.txt/testfile.txt -u alice:1234 -k -v

HTTP/1.1 500 Internal Server Error
 Access-Control-Allow-Origin: *
 Content-Security-Policy: default-src 'none';
 Vary: Origin
 X-Access-Token: eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJhdWQiOiJyZXZhIiwiZXhwIjoxNTk0NjQyMTc2LCJpYXQiOjE1OTQ2Mzg1NzYsImlzcyI6Imh0dHBzOi8vbG9jYWxob3N0OjkyMDAiLCJ1c2VyIjp7ImlkIjp7ImlkcCI6Imh0dHBzOi8vbG9jYWxob3N0OjkyMDAiLCJvcGFxdWVfaWQiOiJBbGljZSJ9LCJ1c2VybmFtZSI6IkFsaWNlIiwibWFpbCI6ImFsaWNlQGV4YW1wbGUub3JnIiwiZGlzcGxheV9uYW1lIjoiQWxpY2UifX0.B2JIkA1JPoZmIi-4aOics2WzTa8weco_H3YLr0LUb_M
 X-Content-Type-Options: nosniff
 X-Download-Options: noopen
 X-Frame-Options: SAMEORIGIN
 X-Permitted-Cross-Domain-Policies: none
 X-Robots-Tag: none
 X-Xss-Protection: 1; mode=block
 Date: Mon, 13 Jul 2020 11:09:36 GMT
 Content-Length: 0

At step 7 I see an error in the description or something I do not understand. We cannot copy a folder to a file
If there is an error in the description here and you copy copy1.txt to testFolder then the case works, we get
Request Method: COPY
Status Code: 201 Created

If so, please close it

At step 7 I see an error in the description or something I do not understand. We cannot copy a folder to a file If there is an error in the description here and you copy copy1.txt to testFolder then the case works, we get
Request Method: COPY
Status Code: 201 Created

If so, please close it

@ScharfViktor actually copying folder into file should be forbidden but we get 204 http status code which is odd behaviour

Current behavior
Checking context
curl -X GET http://localhost:9140/remote.php/webdav/PARENT1/copy1.txt -u alice:1234 -k
>
* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK

<
* Connection #0 to host localhost left intact

curl -X GET http://localhost/core/remote.php/webdav/PARENT1/copy1.txt/testfile.txt -u alice:1234 -k -v

* Mark bundle as not supporting multiuse
< HTTP/1.1 200 OK
<
* Connection #0 to host localhost left intact
some data%

I believe these are the expected behaviors:

COPY myfile.txt -> myFolder

folder myFolder is moved to trashbin
file myFolder is created

COPY myFolder -> myfile.txt

file myfile.txt is moved to trashbin
folder myfile.txt is created

@ScharfViktor Please, confirm the behavior then maybe we can close this one
CC @amrita-shrestha

@ScharfViktor, please see the comment above, i assign the ticket to you

@ScharfViktor Please, confirm the behavior then maybe we can close this one

re-tested also for public link case. Works fine


Ranked Voting Computation

Write the algorithm to evaluate the winner in a ranked voting.
https://en.m.wikipedia.org/wiki/Instant-runoff_voting

I had a pdf excellent which explain about (voting systems)[https://drive.google.com/file/d/1bOGS0jkPyMP1Cx_-Vr7kI12-MwG4C-rS/view?usp=sharing] I'll leave here to consult

how would work this algorithm?

As we're changing the project scope, this issue is no longer necessary.


getServerSideProps makes next-i18next load empty namespaces

I probably did something incredibly wrong but I cant figure it out. I followed the docs and re-read them multiple times + tried all the issues I could find related to the topic.
Basically, if you go to https://capp.floffah.dev/ you will see that translations load fine. that site uses getStaticProps. however if you go to https://master.capp.floffah.dev it loads none and when looking at next's data it loads the namespaces but they are just empty objects.
The repository is https://github.com/floffah/collaborated with the project in the packages/web folder.
I am passing the config to the serversidetranslations method (which is used in the same function shared by a util function i made to build almost identical (with the obvious changes) functions for getServerSideProps and getStaticProps) and also to the _app hoc.
Everything works fine in a development environment but if you build it and run the serverless functions, it refuses. The namespace files are definitely on vercel as i can see them but it just doesnt seem to load them.
If you need to build the web run yarn build build --exclude docs,old-server,app in the root of the project
Any ideas? Am I being incredibly stupid?

Please post on StackOverflow for help requests. Good luck!


gRPC on FreeBSD 10.1

Had a chance to port gRPC on FreeBSD 10.1. Basically created a FreeBSD 10.1 VM, cloned the gRPC git and with some changes in header file, makefiles & downloading few tools, was able to compile and run the sample app from the git.
Pasted below are the changes done. Please do have a look and let know your feedback. Also let know if gRPC can start supporting freeBSD.
I. grpc compilation for FreeBSD 10.1:
a) Add support for FreeBSD platform in include/grpc/support/port_platform.h.
The following changes required to have support for FreeBSD platform.
+++ include/grpc/support/port_platform.h
@@ -75,6 +75,28 @@
#define GPR_POSIX_SYNC 1
#define GPR_POSIX_TIME 1
#define GPR_GETPID_IN_UNISTD_H 1
+/**************************************/
+#elif defined(FreeBSD)
+#define GPR_GCC_ATOMIC 1
+#define GPR_CPU_POSIX 1
+#define GPR_POSIX_LOG 1
+#define GPR_POSIX_MULTIPOLL_WITH_POLL 1
+#define GPR_POSIX_WAKEUP_FD 1
+#define GPR_POSIX_NO_SPECIAL_WAKEUP_FD 1
+#define GPR_POSIX_SOCKET 1
+#define GPR_POSIX_SOCKETADDR 1
+#define GPR_POSIX_SOCKETUTILS 1
+#define GPR_POSIX_ENV 1
+#define GPR_POSIX_FILE 1
+#define GPR_POSIX_SYNC 1
+#define GPR_POSIX_STRING 1
+#define GPR_POSIX_TIME 1
+#ifdef _LP64
+#define GPR_ARCH_64 1
+#else
+#define GPR_ARCH_32 1
+#endif
+/****************************************/
#elif defined(linux)
#ifndef _BSD_SOURCE
#define _BSD_SOURCE
b) The tools automake, autoconf and libtool needs to installed to compile thirdparty/protobuf for protobuf 3.0.
c) A change is need to the Makefile under thirdparty/openssl/ to set C/C++ compilers appropriately.
The FreeBSD 10.x comes with clang and will not have gcc by default.
The Makefile under thirdparty/openssl/ sets C/C++ compilers to gcc and g++ which should be cc(clang) and c++(clang++) for FreeBSD 10.x.
d) A change is needed to the Makefile under thirdparty/zlib/ to set C/C++ compilers appropriately (same reason mentioned above).
II. grpc-common compilation for FreeBSD 10.1
The following changes needed for Services (or Applications) Makefiles.
a) Need to set C/C++ compilers appropriately fro FreeBSD 10.x.
b) Need to link with the library libc.so (-lc) instead of the library libdl (-ldl) for FreeBSD 10.x for calls to deal with a shared library (eg, dlopen, dlsym etc.).
III. The environment and tools used for compilations as follows.
OS: FreeBSD 10.0-RELEASE FreeBSD 10.0-RELEASE #0 r260789: Thu Jan 16 22:34:59 UTC 2014 root@snap.freebsd.org:/usr/obj/usr/src/sys/GENERIC amd64
compiler: FreeBSD clang version 3.3 (tags/RELEASE_33/final 183502) 20130610
libtool: libtool (GNU libtool) 2.4.5
automake: automake (GNU automake) 1.15
autoconf: autoconf (GNU Autoconf) 2.69
host-triplet: amd64-portbld-freebsd10.1
shell: GNU bash, version 4.3.33(0)-release (amd64-portbld-freebsd10.1)
<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<<

Excellent, thanks for the report and contribution. You mentioned that you can build under FreeBSD - are you able to run the tests also, using the commands specified in the contributions guide? Were any changes needed on the C++ side? We currently do not have FreeBSD as a supported platform, but there is potentially interest and some experience on this platform from the group. We're very glad to accept external contributions, of course!

Did you have a chance to look at #1047 ? :-)

Nico, I knew about #1047; sorry for not mentioning it in my response. I would actually encourage @M-Vivek to submit a PR anyway in order to see if there's anything further required in that environment to make things work than what you had to do. I particularly want to know if M was able to run the tests successfully and if the work needed any changes on the C++ side.

hi vjpai, thanks for being glad to accept this contribution. By contribution guide, i assume you are mentioning about c++ sample app under grpc-common and yes i was able to run the app successfully. The changes mentioned in the report are the only changes that were done.
I have submitted a pull request, https://github.com/grpc/grpc/pull/1252.
nico, i wasnt aware of #1047.


App is crashing on Android 11

What is the bug?
In Unstoppable Wallet, which is using you SDK, app is crashing on Android 11. One of our users has reported this issue, and directed to solution to increase OkHttp version.
Crash log
grpc-okhttp-0
   Process: io.horizontalsystems.bankwallet.dev, PID: 7840
   java.lang.AssertionError: Method getAlpnSelectedProtocol not supported for object SSL socket over Socket[address=zcash.horizontalsystems.xyz/<IP_ADDRESS>,port=9067,localPort=39814]
       at io.grpc.okhttp.internal.OptionalMethod.invoke(OptionalMethod.java:114)
       at io.grpc.okhttp.internal.OptionalMethod.invokeWithoutCheckedException(OptionalMethod.java:135)
       at io.grpc.okhttp.OkHttpProtocolNegotiator$AndroidNegotiator.getSelectedProtocol(OkHttpProtocolNegotiator.java:183)
       at io.grpc.okhttp.OkHttpProtocolNegotiator$AndroidNegotiator.negotiate(OkHttpProtocolNegotiator.java:145)
       at io.grpc.okhttp.OkHttpTlsUpgrader.upgrade(OkHttpTlsUpgrader.java:63)
       at io.grpc.okhttp.OkHttpClientTransport$4.run(OkHttpClientTransport.java:568)
       at io.grpc.internal.SerializingExecutor.run(SerializingExecutor.java:123)
       at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
       at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
       at java.lang.Thread.run(Thread.java:923)

Sorry for delay. Just noticed this issue, due to the holiday break. It seems that the root issue is pretty straight-forward:
the underlying library (OkHttp) was making calls to hidden methods through reflection and the use of getAlpnSelectedProtocol just needs to be replaced with  javax.net.ssl.SSLSocket#getApplicationProtocol() and that change was made and merged back in February.
However, as noted here this library has been stuck on an older version of the grpc library (1.25.0) due to compatibility issues that would cause breaking changes in multiple places (all consumers of the protobufs: iOS, Android and GoLang). Consequently, gRPC is pulling in the older version of okhttp.
I'll dig into this and get a better idea of exactly how painful it is to clear this tech debt and I'll also investigate whether we can reduce the pain by switching over to wire for gRPC.

Sorry for delay. Just noticed this issue, due to the holiday break. It seems that the root issue is pretty straight-forward:
the underlying library (OkHttp) was making calls to hidden methods through reflection and the use of getAlpnSelectedProtocol just needs to be replaced with  javax.net.ssl.SSLSocket#getApplicationProtocol() and that change was made and merged back in February.
However, as noted here this library has been stuck on an older version of the grpc library (1.25.0) due to compatibility issues that would cause breaking changes in multiple places (all consumers of the protobufs: iOS, Android and GoLang). Consequently, gRPC is pulling in the older version of okhttp.
I'll dig into this and get a better idea of exactly how painful it is to clear this tech debt and I'll also investigate whether we can reduce the pain by switching over to wire for gRPC.

If the root issue was not fixed by these changes, we can re-open this issue.

If the root issue was not fixed by these changes, we can re-open this issue.


Negative outdoor temperatures do not fit into database column structure

Note that this fix requires altering the database.


Incremental annotation processing for Kotlin

Depends on #625, https://github.com/permissions-dispatcher/kompile-testing/pull/13
Will add some tests later.

👀


beforeRouteEnter next callback is not called (in this very specific async situation)

Version
3.0.1
Reproduction link
http://jsfiddle.net/df4Lnuw6/271/
Steps to reproduce

Have a <router-view v-if="ready"> in the root component's template with ready initially false.
Have a single route for path / whose component has a beforeRouteEnter hook.
Perform the following in the root component's created hook:

Replace the route with /?x=1 (this causes the same component to be reused).
After a timeout, set ready to true.

What is expected?
The callback function passed to next in the beforeRouteEnter hook should be called.
What is actually happening?
The callback function passed to next in the beforeRouteEnter is not called.

A temporary fix is to use history.replaceState directly instead of router.replace.

hmm. Since the router-view is not is toggled off with a v-if, there's no component to pass to the next callback. Using a v-show would also let you have the callback.
What do you do in the actual callback that needs to be in the callback?

Since the router-view is not is toggled off with a v-if, there's no component to pass to the next callback.

The issue isn't solely the v-if, if you comment out the router.replace('/?x=1') it will work.
Since this issue requires a very specific setup, I doubt it would affect many people, so it might not be worth fixing, but I thought I'd mention it for what it's worth. Also the workaround works fine for me.

Not sure should i create new ticket or not... Its about a component beforeRouteEnter guard
I'm using same component for different routes with different meta.content(if its important)
lets say it is category  and item
If I initially load page from item, callback for item works
if I initially load from category - it do not works

@enomado
I just found the issue that seems to have the same problem

Closingn in favour of #2255 / #2188


Make tests more robust

This PR makes our integration tests work with recent docker and SSH versions. It doesn't affect the binaries we ship.

@fejnartal You've already reviewed and approved the commits in this PR when they were part of #426, so I'm not marking this one as "draft". Please let me know if this is a mistake!


unicode vs. string comparison in scipy.stats.binned_statistic_dd

I'm getting an error where scipy.stats.binned_statistic_dd isn't recognizing that the statistic parameter I'm passing is 'count' when it does the string comparison.
I'm assuming this has something to do with a unicode vs. str type issue --- I'm using python2.7 with from __future__ import unicode_literals.  Should this be changed to an equality comparison?  i.e.
if(statistic != 'count' and Vlen != Dlen):

instead of
if(statistic is not 'count' and Vlen != Dlen):

My understanding is that you shouldn't use "is" but "==" for string
comparisons for this sort of thing, yeah.

@lzkelley, this is addressed in #5935. Do you have a test for this?


Time Section Aligned correctly

closes #2279
The issue was in the Time.tsx section mainly with the timeline graph, below I have attached the before and after images
Before

After

Before

After

Before

After

@RavindraP04 Please review this PR

Can you shift the image a little bit downwards @Mehaksharma6 , it looking cluttered near about 768px

Sure, I can do that

How is this ?

This one looks better @Mehaksharma6

Pushed the changed, Please check @RavindraP04

Looks Good, Merging it
Thanks for your valuable contribution @Mehaksharma6


tinydtls: Update to most recent version, simplify usage

While (again) not an official release, this will advance us by 274 commits:
$ git rev-list --count 178b945e5497b813b1239e2fbf57e34b7488745f..HEAD
274

Smoke tested like this (after registering here and here):

$ examples/client/lwm2mclient_tinydtls -h leshan.eclipseprojects.io -4 -p 5784 -n wakaama-560-with-dtls -i wakaama-560-with-dtls -s 5cdafa07cf5d7e0e65b8e504bc0dc9 -b
Trying to bind LWM2M Client to port 56830
LWM2M Client "wakaama-560-with-dtls" started on port 56830
>  -> State: STATE_BOOTSTRAPPING
 -> State: STATE_BOOTSTRAPPING
60 bytes received from [<IP_ADDRESS>]:5784
16 FE FD 00  00 00 00 00  00 00 00 00  2F 03 00 00   ............/...
23 00 00 00  00 00 00 00  23 FE FD 20  B8 4A 5F 7E   #.......#.. .J_~
96 8B F1 EF  0B ED 54 EA  06 01 7F C8  37 D2 69 D0   ......T.....7.i.
B5 BD 79 08  35 9D E9 4D  30 43 B2 9C                ..y.5..M0C..
 -> State: STATE_BOOTSTRAPPING
126 bytes received from [<IP_ADDRESS>]:5784
16 FE FD 00  00 00 00 00  00 00 01 00  58 02 00 00   ............X...
4C 00 01 00  00 00 00 00  4C FE FD 63  F8 D9 59 81   L.......L..c..Y.
2A 68 7F EC  D6 89 73 E2  42 CE D0 0C  E5 84 D1 F0   *h....s.B.......
64 A8 17 01  30 8D 51 F1  FD F4 42 20  01 FD 3D 8F   d...0.Q...B ..=.
A0 18 3F 15  78 D0 8C 2D  37 8F 2E 20  63 30 A3 68   ..?.x..-7.. c0.h
C7 B1 6B 89  24 6E DE 5B  FA 8D 08 EC  C0 A8 00 00   ..k.$n.[........
04 00 17 00  00 16 FE FD  00 00 00 00  00 00 00 02   ................
00 0C 0E 00  00 00 00 02  00 00 00 00  00 00         ..............
 -> State: STATE_BOOTSTRAPPING
67 bytes received from [<IP_ADDRESS>]:5784
14 FE FD 00  00 00 00 00  00 00 03 00  01 01 16 FE   ................
FD 00 01 00  00 00 00 00  00 00 28 00  01 00 00 00   ..........(.....
00 00 00 22  D4 1E D9 06  A6 F9 00 B5  72 A1 85 E1   ..."........r...
77 16 5D 56  CA F3 09 3F  21 48 BC E0  B4 11 C9 FF   w.]V...?!H......
71 19 B3                                             q..
 -> State: STATE_BOOTSTRAPPING
 -> State: STATE_BOOTSTRAPPING
37 bytes received from [<IP_ADDRESS>]:5784
17 FE FD 00  01 00 00 00  00 00 01 00  18 00 01 00   ................
00 00 00 00  01 61 68 16  BC B7 55 C0  16 C9 19 D4   .....ah...U.....

 -> State: STATE_BOOTSTRAPPING
380 bytes received from [<IP_ADDRESS>]:5784
17 FE FD 00  01 00 00 00  00 00 05 01  6F 00 01 00   ............o...
00 00 00 00  05 8A 55 89  00 03 1B 4B  24 8C 94 15   ......U....K$...
AF FC BD EC  81 73 A0 89  EC 55 E3 05  03 EF BC D0   .....s...U......
E8 2F ED A6  30 41 76 E4  59 84 AF A9  38 67 3A 71   ./..0Av.Y...8g:q
0F 89 57 1A  6B 3A 22 73  C3 A2 FC 4F  6A DD D4 21   ..W.k:"s...Oj..!
D4 3A E6 2C  EC 4B EA D3  5F 2C EC 2A  E9 2A 80 93   .:.,.K.._,.*.*..
CD 9D 0B 6E  47 FE 01 12  F9 BC CE A4  88 49 40 AB<EMAIL_ADDRESS>D5 BF 6D 80  E7 D4 0A 0D  C0 1B 6C 5E  57 29 69 AC   ..m.......l^W)i.
04 5F 36 D0  F9 91 4A 5B  4E F2 13 E1  4A 85 62 76   ._6...J[N...J.bv
5E 46 21 FE  3D 1C 00 56  DB 1F BA C4  23 D9 3B 0E   ^F!.=..V....#.;.
41 41 A2 3D  46 00 78 70  EE 87 33 83  24 9C EA 51   AA.=F.xp..3.$..Q
E0 A9 36 AE  42 15 37 66  50 92 79 76  E0 AD B2 96   ..6.B.7fP.yv....
ED 83 3E D5  6D E7 BB 1F  30 CF C0 AB  92 E5 AA 98   ..>.m...0.......
17 2B 67 88  F9 9F EB E8  16 90 86 78  75 57 3E C9   .+g........xuW>.
2D 8E 6D 7B  30 5F 11 C5  7F EF 97 7B  C2 87 0C 46   -.m{0_.....{...F
83 38 FA 1F  3F 5A B6 2A  3B 49 05 64  06 65 09 63   .8..?Z.*;I.d.e.c
34 28 0C D9  37 22 DC 85  BB A4 A5 D2  2A DE 7D 11   4(..7"......*.}.
D0 1A 08 F2  F3 97 8F 2C  E0 DF 27 E1  AC 11 C4 C5   .......,..'.....
06 1F 8F C4  A7 34 D7 37  D8 C8 2D 98  E1 F4 09 E0   .....4.7..-.....
A4 81 6A C3  F3 09 07 72  4F 5A D9 76  98 07 42 B5   ..j....rOZ.v..B.
05 F6 FF 62  6C 0E FF 67  52 2E 76 62  E3 15 AC 5B   ...bl..gR.vb...[
AC 2A 19 1E  73 71 94 5C  80 AF 03 C3  23 FE 11 26   .*..sq.\....#..&
DA 08 A5 38  E1 F9 DD 1B  50 0B 41 0E  1B 28 B2 3D   ...8....P.A..(.=
63 06 E0 6C  A2 B5 4A A0  93 6A C6 FD                c..l..J..j..
 -> State: STATE_BOOTSTRAPPING
153 bytes received from [<IP_ADDRESS>]:5784
17 FE FD 00  01 00 00 00  00 00 06 00  8C 00 01 00   ................
00 00 00 00  06 CB 16 9E  6A 1C AB D0  5C 52 F1 8C   ........j...\R..
8A 23 06 FF  67 04 61 2C  1A B2 56 3D  CE 56 D2 41   .#..g.a,..V=.V.A
27 22 86 DB  69 6F A2 5C  1F 71 CC 30  C0 C4 C4 8F   '"..io.\.q.0....
E9 E1 55 1C  C9 4E 28 F6  09 59 85 6E  4C BE 0E 8C   ..U..N(..Y.nL...
96 1A B1 A6  19 01 DE 6A  82 71 C0 86  9D D0 DD 55   .......j.q.....U
71 58 2B 78  C9 3C 3E 10  82 EA BC F3  99 C0 E0 FE   qX+x.<>.........
7B AF 01 68  05 F3 12 16  D6 5A 7F A1  63 47 5E 5C   {..h.....Z..cG^\
05 D6 BF 95  32 48 B9 F9  32 8A E7 EE  00 E2 CE 03   ....2H..2.......
29 17 D4 A9  15 07 7D 02  F9                         ).....}..
 -> State: STATE_BOOTSTRAPPING
44 bytes received from [<IP_ADDRESS>]:5784
17 FE FD 00  01 00 00 00  00 00 07 00  1F 00 01 00   ................
00 00 00 00  07 26 A3 E5  DD 5B 47 E6  E9 44 92 D4   .....&...[G..D..
3B 2C EA 2A  DC D0 18 02  EE 2F 2D C9                ;,.*...../-.
 -> State: STATE_BOOTSTRAPPING
 -> State: STATE_REGISTERING
60 bytes received from [<IP_ADDRESS>]:5684
16 FE FD 00  00 00 00 00  00 00 00 00  2F 03 00 00   ............/...
23 00 00 00  00 00 00 00  23 FE FD 20  E9 19 40 0E   #.......#<EMAIL_ADDRESS>
B9 CB 3C EE  66 D9 1E 3E  C0 2E 0F 20  BF F2 43 B2   ..<.f..>... ..C.
CE BA 28 27  17 2E 0D C3  D2 3D AB A9  1E 96 8F 8C   ..('.....=......
82 2B A6 A3  5B 51 40 C1  78 39 92 6F  C0 A8 00 00<EMAIL_ADDRESS>04 00 17 00  00 16 FE FD  00 00 00 00  00 00 00 02   ................
00 0C 0E 00  00 00 00 02  00 00 00 00  00 00         ..............
 -> State: STATE_REGISTERING
67 bytes received from [<IP_ADDRESS>]:5684
14 FE FD 00  00 00 00 00  00 00 03 00  01 01 16 FE   ................
FD 00 01 00  00 00 00 00  00 00 28 00  01 00 00 00   ..........(.....
00 00 00 23  75 19 AF A5  11 93 A2 EB  6B DB CC E6   ...#u.......k...
B6 B0 4E 10  83 BA 0C 46  B3 48 8C 7A  32 F0 D9 AA   ..N....F.H.z2...
2A B1 34                                             *.4
 -> State: STATE_REGISTERING
 -> State: STATE_REGISTERING
51 bytes received from [<IP_ADDRESS>]:5684
17 FE FD 00  01 00 00 00  00 00 01 00  26 00 01 00   ............&...
00 00 00 00  01 47 5C D6  1B 6F 16 55  0A 93 9C F6   .....G\..o.U....
4E 00 A9 BE  8F CC 62 B6  64 15 C4 28  63 47 49 B1   N.....b.d..(cGI.
2A BC CD                                             *..
 -> State: STATE_READY
quit

non IPV4 or IPV6 address
non IPV4 or IPV6 address
non IPV4 or IPV6 address
non IPV4 or IPV6 address

Do we need a new CQ for this, the existing one is for version 0.8.2

Do we need a new CQ for this, the existing one is for version 0.8.2

You are talking about tinydtls dependency right ?
As now tinydtls is an eclipse project, AFAIK no CQ is needed.
You could ask why does it exist a CQ for the version 0.8.2 ?
Good question, I guess probably before tinydtls become an eclipse project :thinking:

Just to mention:
tinyDtls made a lot of progress and is still making progress.
If you're interested, for testing the "develop" branch contains many bugfixes of the last months and there are still improvement and bugfixes pending. So I would recommend, to check frequently, if that works for you.

@boaks do you know the idea behind master and develop branch ? I'm not sure to get the development process ?
(or maybe @obgm could answer about it ?)
Let me know if I should rather ask this at https://github.com/eclipse/tinydtls/issues)

I don't know. So asking @obgm is the best.

The reason for these branches is that it follows the usual best practices for git workflows with a stable main branch, and a develop branch where the next stable version is being prepared.
The odd thing for tinydtls is that there is not really a stable version as it has never been released while under the hood of Eclipse Foundation; The current main branch reflects the initial contribution and will be updated once the 1.0 release process has finished.

Thanks to @boaks I think we are getting closer to this initial release within the next weeks.

Thanks to @boaks I think we are getting closer to this initial release within the next weeks.

Would you (tinydtls) prefer Wakaama to update now (and again in a few weeks) or wait for the final release?

+1 for the final release

Would you (tinydtls) prefer Wakaama to update now (and again in a few weeks) or wait for the final release?

That depends on what you want. I usually try the "newest", but with care, mainly in order to find left or new bugs.
FMPOV, the current "develop" is worth to be used, even if some issues are open.
I guess, in some weeks, it will be worth again to update.
Don't forget to report issues, if you get faced ones.

I suppose updating now is a good idea, especially as the release process will take some time. We could provide a new release candidate soon if you prefer to have some synchronization point.

@obgm, I think I get it, you're master branch is a kind of maintenance branch.
Currently tinydtls is just used for example / demo, right ?
IMHO a Wakaama release should ideally use a released version of tinydtls but during development phase, this could OK to use a development branch. (especially if this is just for demo)
E.g. Leshan (LWM2M in java) development branch (master) frequently depends on development version of Scandium (DTLS in java). It allows to provide feedback or detect bugs sooner. The only constraint is that you need to ensure that the library you depend on will release in an acceptable time for you.

Currently tinydtls is just used for example / demo, right ?

Yes, its works-with.
side note: I intend to include the DTLS enabled client binary in the integration testing, but even then, it will not be a dependency of the Wakaama library itself.

Just updated this PR on the most recent Wakaama master and with the most recent commit of tindydtls (there is no release yet). Suggesting to merge this PR in this current state.

I consider, that when the  PR for RFC5746 is merged into tinydtls/main, a update would make again sense.
I will ping, when we merged it.

Just realized the thumbs up from @boaks. I consider this an approval and therefore merge this PR. :dancers:


Fix the back button in Chrome iOS

When pressing the back button in Chrome iOS after the first pushState, the popstate event contains an undefined state (Chrome desktop's state value is null). This is indistinguishable from an extraneous WebKit popstate event, which means that handlePop and the history listener never get called.
This adds a UA check for CriOS to distinguish between bogus WebKit popstate events and real Chrome iOS ones.
I didn't add a test for this, as it appears that the DOM/UA-specific stuff isn't unit tested. Happy to add one if you like!
BrowserStack now supports Chrome iOS, so it might be worth adding it to the testing matrix.
If you'd like to replicate this yourself, you'll have to use weinre to debug against Chrome iOS. Not the best situation there 😄

@tptee Any chance you can update this PR? I'd like to get this merged ASAP :) Thanks!

Oh definitely! I'll make it happen tonight.
Unfortunately, it looks like Browserstack only supports Chrome iOS for manual testing :(

Extraneous date is no more!
Confirmed through the BrowserStack API that Chrome iOS isn't available for automated testing :( :( :( https://www.browserstack.com/automate/rest-api#rest-api=browsers

Thanks, @tptee!


CSS classes from own SCSS files will be overwritten.

I try to to build Bootstrap 4 according to this description: https://v4-alpha.getbootstrap.com/getting-started/build-tools/#tooling-setup
I've found the _custom.scss where variables can be overwritten.
But it seems that the _custom.scss is the wrong place for an import of '_myOwn.scss' because it's one of the first SCSS files called by 'bootstrap.scss'.
So if "_myOwn.scss" contain the lines
.btn {
	// great stuff
}

it will be overwritten by the .btn class from '_buttons.scss'.
Is there a propper way to import your own SCSS files?
If not, I suggest a '_customImports.scss' called last by 'bootstrap.scss'.

if .btn {} is defined more than once, the last one defined is the one used.
if you're overriding rules, create a separate _myOwnRules.css and include it last.

Yup, what @bkdotcom said.


Add observations' taxon threatened status and establishment means to ES index

We want to be able to query for observations that are threatened in their location context, as well as introduced, native, and endemic. Use the centroid of the observations uncertainty region as a starting point.
Related discussion in https://github.com/inaturalist/design/issues/20

I found an interesting case in http://www.inaturalist.org/observations/1000148 , which is introduced to its region and endemic to its country. Looking at https://github.com/inaturalist/inaturalist/blob/master/app/models/listed_taxon.rb#L378 I wonder if what we want to record is

introduced = true if the observation is introduced in ANY place it exists, otherwise native = true if it is set as native or endemic in any place (otherwise introduced and native are false) (i.e. introduced trumps all), OR
grab the first establishment means if the place with the highest admin_level or lowest place_type and is that most specific value only, OR
have it returned in searches for both observations of endemic and introduced taxa?

In the first two options introduced and native can never both be true, whereas they can in the 3rd.
Finally - any need to distinguish native and endemic, or do we just need introduced? and native??

I think introduced and native should never both be true. On observations/show we choose the listed taxon with the smallest bbox_area that has establishment_means set to endemic or introduced, and I think that's the strategy we should use here.
Regarding endemism, this is a situation in which we overloaded the establishment_means field when we probably shouldn't have. I think ideally the ES index should have have a separate field for endemic: true | false, since a taxon can be native AND endemic, but also native and NOT endemic.

So we'll grab the first listed_taxon sorted by bbox area with an establishment_means. If the means is introduced then obs.taxon.introduced = true, of the means is native or endemic we'll set obs.taxon.native = true
Additionally we'll set obs.taxon.endemic = true if it has an establishment_means of exactly endemic. One last weird case - in the example I gave it is technically endemic to New Zealand, but I suspect if obs.taxon.introduced = true then endemic should never be true, but endemic can be true if obs.taxon.native = true

I think that's right. There are always going to be some weird edge cases like that, I'm afraid, since so much of this depends on the context of the search. So with the current strategy, people searching for observations of endemic species in New Zealand are not going to see http://www.inaturalist.org/observations/1000148, even though it's an observation of a species that's endemic to New Zealand (sort of, at least for wild populations).


IMPROVE EXPLORE TOP HACKTHON SECTION

As there links that are are appearing over the images which is making them look jumbled .
I would like to add hover effect on those links so that they only appear when cursor is moved over them .
Please assign this issue to me.
https://github.com/anmode/grabtern-frontend/assets/129520458/9162823c-345f-45e1-99b3-c0b4e2d28c17
leftmost is the earlier , and the other three are the one I changed

Hey, Thanks for raising the issue. sorry, but we won't need...there are many improvements. Please look at those!!. I will be creating issues. please comment on that


Jesse strategy break point debugging in vscode.

As a developer I'd be nowhere without breakpoint debugging, and I wanted to bring the other people I'm collaborating with up to speed on developing software so they needed this capability to learn how to write python. I'm using vscode to develop with Jesse. So I've forked the project-template and updated it to work automatically with vscode which means it will provide the user prompts to install docker, open in a container, etc. It also gives them a single button press to start debugging the code. It will work for both docker (in linux and windows) and with the jesse app natively in windows and linux.
Note: https://code.visualstudio.com/docs/containers/docker-compose
"In Python projects, you have the Dockerfile, .dockerignore, docker-compose*.yml files all in the root folder of the workspace. When you add another app or service, move the Dockerfile into the app's folder."

The workflow is:

(OPTIONAL) follow the desired setup instructions for your jesse environment (you can skip this if you just want to use docker as vscode will prompt you through all the setup)
install vscode
Create a new strategy project from this template
open this new project in vscode as a folder
vscode will then prompt you through the remaining steps (eg opening the project in the dev-container, installing python, etc)

Once you're ready to debug a strategy:

open the file of the strategy in vscode
insert a break point by clicking in the left margin (near the line numbers)
navigate to the debugging tab as shown in the image (1)
choose your debugging environment as shown in the image (2) eg jesse docker debug
then just click play to start debugging as showing in the image (3)

you can inspect the program flow, variable values, and start experimenting with your strategy in the debug console against the candle data. oh and poke around at the internals of jesse if that's what you're into.

Worth noting for this one, it's really useful to edit the break point for a specific candle you're debugging eg:
datetime.utcfromtimestamp(self.time/1000).strftime('%Y-%m-%d %H:%M:%S') == '2021-07-20 02:47:00'


Variable x-axis domain in 2D plots

As discussed in #188, x-axis domain in 2D plots should be variable to account for different number of nodes in each TRACULA bundle.

Resolved by #209.


Demonstrate pluggable storage back-ends

@keller-mark I've extracted this to respond in a separate ticket because I want to keep the javascript one focused on that use case, but I think you bring up an important point.

I also understand that the initial goal is to focus on the TileDB backend for the API. It would also be important to demonstrate (perhaps in the secondary draft if not the initial draft) that the initial API is flexible enough to be integrated with more than one backend, for instance with "dumber" backends like HDF5 files and Zarr stores.

You've correctly identified our focus. We believe that establishing pluggable storage back-ends is a key requirement for this project to be successful.
We will be eager to collaborate with other storage back-ends. However, we anticipate that there will be a significant number of issues to resolve before we align on an API that effectively serves the R and python single cell toolchains. We felt it would be best to work out those details before approaching storage providers. It's our intuition that when we have a stable draft of the API, it will be relatively simple to plug in different storage back-ends, and we like the idea of demonstrating value before asking help on implementation.

Circling back -- a central part of the last many months' work has centered on the separate of the abstract spec at https://github.com/single-cell-data/SOMA, and the particular implementation https://github.com/single-cell-data/TileDB-SOMA.


greater-than/less-than/equal-to havingSpec to call AggregatorFactory.finalizeComputation(..)

Fixes #4859

its failing tests in GroupByQueryRunnerTest which expect exceptions with having clause on complex metrics, will fix those once the solution proposed here is in agreement.

just noticed #2507 , that should be fixed with this patch.

@himanshug could you please fix the conflict, and then feel free to merge yourself.


VisualFSharp project --- is super slow to display Cyan Type info

When loading a large solution, time to get to full build is desperately slow.

The title and body of this issue differ.  Are you referring to semantic colorization being slow on VF#, or the time to build the solution?

Repro steps would be helpful :)
However I believe Kevin is referring to the fact that when in-memory cross-project references are enabled (the default) and you're working in FSharp.Editor, then it takes ages to show Cyan because it goes and does a full typecheck on all dependent projects first.
If in-memory cross-project references are disabled, and a build has been done, then it is faster.

@dsyme, I think that is exactly what @KevinRansom means. Though I think it is also related to editing a large project and finding that it gets annoyingly slow very quickly (to the point where even typing a simple comment ends up at about a character a second!). It often takes less than a half hour of editing for this to happen. Waiting it out and continuing does not give back performance (once slow, it stays slow until restart).
I have been trying to find the culprit by attaching a profiler when this happens and I have seen a lot of thread-wait cycles, but I have yet to manage to find the actual thread I should be monitoring for this, I mean, I am not sure the thread-waits are the culprit (or how to effectively profile to begin with). I'm willing to do more research, but may need some help. I can also give a datadump of the profile session if that helps anyone with more knowledge of the processes involved.
I also noticed that it seems to be a single thread spinning, it is not that multiple threads end up using all available processing power.

There are two things at work here:

Semantic classification basically requires typechecking the world for large solutions in files where many types from many places are used (e.g., FSharp.Editor).
The workspace event which tells us to invoke semantic classification isn't instantaneous, so there is a delay before our chunky operation can happen.

@KevinRansom was looking into the idea of immediately kicking off semantic classification upon file open against a known TFM and the default set of references for that type. This will still result in things like types from P2P references not being colored until the workspace computes projects and fires off the event, but it should make the editor "feel" faster for numerous cases.

Closing this old issue


(6410) SQLITE_IOERR_GETTEMPPATH thrown on first write on Android

For reference: The SQLITE_IOERR_GETTEMPPATH error code is an extended error code for SQLITE_IOERR indicating that the VFS is unable to determine a suitable directory in which to place temporary files.
This implies that SQLite being used is compiled with SQLITE_TEMP_STORE=1 build flag, and somehow in this particular environment it's failing to determine a suitable location on disk for temp files.
From Firefox's build config, on Android SQLite is forced to use memory for temp store: https://dxr.mozilla.org/mozilla-central/source/db/sqlite3/src/moz.build#90
"On Android there's no tmp partition, so always use a MEMORY temp store" - via SQLITE_TEMP_STORE=3 flag.
We can force temp files to be stored in memory via PRAGMA temp_store=2.

Following Firefox's config, it's using memory store on Android (no other choice) and on 64bit platforms.

Try to use a MEMORY temp store when possible. That allows for better
performance and doesn't suffer from a full separate tmp partition.
Exclude 32bit platforms due to address space fragmentation issues.

Proposed patch in #506 forces memory storage indiscriminately. Ideally I'd like to follow what Firefox is doing and exclude 32bit platforms, but I'm not sure how to actually achieve that.
@ncalexan , thoughts?

The linked code isn't testing for 32-bit on Android at all. For reference, from https://sqlite.org/tempfiles.html:

The SQLITE_TEMP_STORE compile-time parameter is a #define whose value is an integer between 0 and 3, inclusive. The meaning of the SQLITE_TEMP_STORE compile-time parameter is as follows:
0. Temporary files are always stored on disk regardless of the setting of the temp_store pragma.
1. Temporary files are stored on disk by default but this can be overridden by the temp_store pragma.
2. Temporary files are stored in memory by default but this can be overridden by the temp_store pragma.
3. Temporary files are always stored in memory regardless of the setting of the temp_store pragma.

I think we should go with 2 everywhere for Mentat: default to memory, let consumers override.

I'm happy defaulting to memory storage for now (#506), but keeping this issue open to alter our SQLite build options or provide a configuration parameter: when used with Firefox's SQLite we'll get the former for free, and #506 doesn't allow consumers to override.


Update README.md

Added the build badge per the new Chef Partner cookbook guide guidelines.

@jjasghar can you please check the failure logs? Seems like builds are breaking on your end.

Yep, got em fixed.
Can you take care of: https://jenkins-01.eastus.cloudapp.azure.com/job/dynatrace-cookbook/93/console for me? Thanks! 🤘

@jjasghar some of the error message are a little picky. We'll see what we can do. How can we replicate the output locally? We should make this part of our upstream process then. Cheers!

Yep, we have all our jobs posted here: https://github.com/chef-partners/chef-partner-cookbook-program-jjb your specifically: https://github.com/chef-partners/chef-partner-cookbook-program-jjb/blob/master/jobs/dynatrace-cookbook.yml
PR's are more then welcome, and we'd like to have a more visible continual validation/certification :)

I'll have a closer look into this soon! Will chef-exec-rspec-spec execute our kitchen tests? By the way, a fix from our dev team is already underway.

I fixed issues reported by chef-exec-rubocop on master branch. The remaining validation tasks (chef-exec-foodcritic and chef-exec-rspec-spec) also pass with status 0 (OK). It seems that the  chef-exec-rspec-spec is a noop for now.

@pozieblo looks like you missed one thing :(
[dynatrace-cookbook] $ /bin/bash /tmp/hudson7364832001878912519.sh
Inspecting 84 files
...............C....................................................................

Offenses:

attributes/server_update.rb:1:1: C: Carriage return character detected.
# ...
^

84 files inspected, 1 offense detected
Build step 'Execute shell' marked build as failure
Finished: FAILURE

https://github.com/Dynatrace/Dynatrace-Chef/pull/22

I fixed the issue on master. For some reason CRLF characters were injected into the attributes/server_update.rb file (instead of LF) maybe because I have started playing with the autocrlf git config attribute...

Wonderful! It's green now, thank you so much for the help :)


Is mj_jac implemented in mujoco-mjx

Hi,
It is great to see that mujoco supports GPU with MJX, I would like to ask that if mj_jac function is implemented in JAX, I need to obtain Jacobian matrix for the end-effector of robots. If not, is there a way to compute it from current version 3.1.2. Thank you.

I see, that a function jac() is implemented in support.py, which I think is the same as mj_jac(). But it is not imported in init.py, so cannot be imported from outside.

Hi @gautica - perhaps this should be public, I'll look into this.  Thanks for pointing it out.


Configuration option to not have import React on component snippet (as per react v17)?

Hi!
Would it be possible to add a configuration option to the extension so when we use any snippets to create a component it doesn't automatically add the import React from 'react';, as this is no longer mandatory for components?
Great extension, I tested many and yours is basically the best, specially to proper parse the component name to CamelCase regardless of the component file name.
Thanks!

Thank you. I am currently working on it and will inform you once it's released.

Hi, this feature has been launched as a pre-release version v11.1.2.

Hi, this feature has been launched as a pre-release version v11.1.2.

how to config? There are no vscode settings.


HTML Proofer retry?

Sometimes the build fails due to (randomly) failing external links.
It would be nice if we could configure HTML Proofer to (for instance) retry 2-3 times if a check on a particular links fails

Had a look at https://github.com/gjtorikian/html-proofer
Didn't see an immediate option to retry failed external links, but it is possible to "enable caching for your external links. Caching simply means to skip links that are valid for a certain period of time." (See: Configuring caching)
This would be really useful imho, as atm deploy fails on random external links...

Sounds good. We'd have to check the implications of running on Travis CI though, as by default they recreate the environment every build - so we'd need to tweak cache settings.
48 hours should weed out the ones failing sporadically?

48 hours sounds great!
I'm not so familiar with Travis CI or Ruby / config. Who could do it?

I'll take a look next week.

External links are only checked on Netlify - it's too slow and annoying to do locally.
It occasionally fails because of timeouts, but a rerun usually fixes it. I think that's good enough for now.
I haven't figured out what directory Netlify uses for caching, so I'm not sure how to take advantage of HTMLProofer's cache option. I suggest we close this issue and revisit it if it becomes too much of a nuisance.

Agreed. Won't fix (at least for now)


Changed ControlRunbookDocument names to reduce code smells

Description of changes:
Changed ControlRunbookDocument names to their remediations + document in order to meet SonarQube requirements.
This change will remove 43 minor bugs and code smells.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

To be fair, I don't know if a lot of these changes for SonarQube will be "improvements" per say. I've been trying to resolve the rules (without fixes) that do not apply to what we're doing, but if I'm resolving most of the changes are we really hitting that quality bar? That's been my thought process trying to slowly get us green here. That being said, I am open to other naming convention because I also liked the older format.


Cloud.code version vs JS SDK version

Hi
There seems to be something at odds with two systems.
It appears that only 1.6.7 (at the time of writing) (cli 3.0.2) that works and allows for deployment
"parse": {
"jssdk": "1.6.7"
}
I have tried 1.6.12 which is a current JS SDK and an error happens with no message.
thanks

Looks like we had an issue that was deploying new SDKs to invalid version strings. Should be resolved now.


In .csproj Link to wwwroot folder can not be open by https.

  <ItemGroup>
    <Content Include="..\Base\wwwroot\css\**\*.css" LinkBase="wwwroot\css">
      <CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
    </Content>
    <Content Include="..\Base\wwwroot\css\**\*.map" LinkBase="wwwroot\css">
      <CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
    </Content>
    <Content Include="..\Base\wwwroot\css\**\fonts\**" LinkBase="wwwroot\css">
      <CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
    </Content>
    <Content Include="..\Base\wwwroot\js\**\*.js" LinkBase="wwwroot\js">
      <CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
    </Content>
    <Content Include="..\Base\wwwroot\js\**\*.map" LinkBase="wwwroot\js">
      <CopyToOutputDirectory>PreserveNewest</CopyToOutputDirectory>
    </Content>
  </ItemGroup>

I have file but https://localhost:5001/css/bootstrap/bootstrap.min.css report status 404

/cc @Tratcher @javiercn
Would static web assets help in this case?

@pranavkm No, and this is unsupported by design. When doing dotnet run no files get copied around. Using LinkBase won't work here. StaticWebAssets would work if they created an RCL for the assets, but that's kind of a hack. Static web assets doesn't support linked content for the same reason.
@Honjoy  what are you trying to achieve?
Closing this as by design. We can reopen if we determine we are missing a feature.

I reorganize library include .js and .css and have some files write by myself.
I hope in my case always link they files just like a template.


After JanusGraph 0.1.1 release, update docs to override ID store name

@amcp need to ask for 0.1.1 release

Asked
https://groups.google.com/forum/#!topic/janusgraph-dev/H9feDHMJahA

However mitigated meanwhile by #165


Improve etcd error reporting and move etcd session startup to background

Description of change
Before actually creating an etcd session, we first try to quickly obtain
a lease using short timeout, so we can print error if it fails.
Also, etcd session creation and leadership election was moved to
background. Note that this doesn't mean that agent can start without
etcd, because:

Peers need etcd in OnStart,
Every watcher tries to bootstrap in OnStart.

Example log with error:
12:02PM WRN<EMAIL_ADDRESS>> retrying of unary invoker failed error="rpc error: code = DeadlineExceeded desc = latest balancer error: last connection error: connection error: desc = \"transport: Error while dialing: dial tcp: lookup controller-etcd.aperture-controller.svc.cluster.local: no such host\"" attempt=0 component=etcd-client target=etcd-endpoints://0xc004432000/controller-etcd.aperture-controller.svc.cluster.local:2379
12:02PM ERR etcd/client/session.go118 > Initial attempt to establish etcd session failed, retrying error="context deadline exceeded" service=aperture-agent

Example (filtered) log when etcd becomes available during startup.
12:13PM INF etcd/client/client.go129 > Initializing etcd client service=aperture-agent
...
12:13PM INF<EMAIL_ADDRESS>> OnStart hook executing callee=github.com/fluxninja/aperture/v2/pkg/etcd/client.ProvideSession.func2() component=fx
12:13PM WRN etcd/client/session.go95 > Establishing etcd session takes long time, putting in background service=aperture-agent
12:13PM INF<EMAIL_ADDRESS>> OnStart hook executed callee=github.com/fluxninja/aperture/v2/pkg/etcd/client.ProvideSession.func2() component=fx runtime=600.2952ms
...
12:13PM WRN<EMAIL_ADDRESS>> retrying of unary invoker failed error="rpc error: code = DeadlineExceeded desc = latest balancer error: last connection error: connection error: desc = \"transport: Error while dialing: dial tcp <IP_ADDRESS>:2379: connect: connection refused\"" attempt=0 component=etcd-client target=etcd-endpoints://0xc000c46540/controller-etcd.aperture-controller.svc.cluster.local:2379
12:13PM ERR etcd/client/session.go119 > Initial attempt to establish etcd session failed, retrying error="context deadline exceeded" service=aperture-agent
12:13PM INF etcd/client/session.go70 > etcd session established service=aperture-agent
...
12:13PM INF etcd/election/election.go82 > Node is now a leader service=aperture-agent

Checklist

[x] Tested in playground or other setup
[ ] Screenshot (Grafana) from playground added to PR for 15+ minute run


autoconf: Depends on m4

I tryed to install ruby-build, and the installation of the dependence autoconf fail.
 GNU Autoconf
configure: autobuild revision... 2.69
configure: autobuild hostname... dcardosods-Ubuntu-13
configure: autobuild timestamp... 20130912T153411Z
checking whether /bin/sh -n is known to work... no
checking for characters that cannot appear in file names... none
checking whether directories can have trailing spaces... yes
checking for expr... /usr/bin/expr
checking for GNU M4 that supports accurate traces... configure: error: no acceptable m4 could be found in $PATH.
GNU M4 1.4.6 or later is required; 1.4.16 or newer is recommended.
GNU M4 1.4.15 uses a buggy replacement strstr on some systems.
Glibc 2.9 - 2.12 and GNU M4 1.4.11 - 1.4.15 have another strstr bug.
==> Configuration
HOMEBREW_VERSION: 0.9.4
HEAD: 39785c8b04e46bae09f70da26d8f8697a666f5d4
HOMEBREW_PREFIX: /usr/local/dcardosods/linuxbrew
CPU: quad-core 64-bit dunno
OS X: 0-x86_64
/usr/bin/ruby1.9.1:
  1.9.3-194
X11: N/A
==> ENV
CC: /usr/bin/gcc => /usr/bin/gcc-4.7
CXX: /usr/bin/g++ => /usr/bin/g++-4.7
CFLAGS: -Os -w -pipe -march=core2 -msse4
CXXFLAGS: -Os -w -pipe -march=core2 -msse4
CPPFLAGS: -isystem /usr/local/dcardosods/linuxbrew/include
LDFLAGS: -L/usr/local/dcardosods/linuxbrew/lib -Wl,-headerpad_max_install_names
MAKEFLAGS: -j4
CMAKE_PREFIX_PATH: /usr/local/dcardosods/linuxbrew
PKG_CONFIG_LIBDIR: /usr/lib/pkgconfig
ACLOCAL_PATH: /usr/local/dcardosods/linuxbrew/share/aclocal
OBJC: /usr/bin/gcc
PATH: /home/dcardosods/bin:/usr/local/dcardosods/linuxbrew/bin:/usr/local/dcardosods/linuxbrew/share/npm/bin:/home/dcardosods/bin:/usr/lib/lightdm/lightdm:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/usr/local/dcardosods/linuxbrew/Library/Contributions/cmd

Error: autoconf did not build
Logs:       /home/dcardosods/Library/Logs/Homebrew/autoconf/config.log

The config.log content.

I just tried to install ruby-build and the m4 dependency is still missing. Any plan to specify these system dependencies as @sjackman or @mistydemeo were proposing?

Fixed. Thanks, Alejandro.

Thanks for the quick fix! Linuxbrew is getting really stable. :smiley:

Thanks! It has come a long way.