Ability to make checks with lambda functions on nullable int columns (Pandas' Int64)

Suppose I have a dataframe with a nullable int column (Int64 in pandas instead of the non-nullable int64)
and a nullable float column:
import pandas
import numpy as np
from pandera import (
    DataFrameSchema,
    Column,
    Check,
    Index,
    PandasDtype,
)

df = pd.DataFrame({'x1': [2, 3, np.nan], 'x2': [1.0, np.nan, 2.1]})
df['x1'] = df['x1'].astype('Int64')

Which gives

x1
x2

0
2
1.0

1
3
NaN

2

2.1

If I try to use a lambda function to check the x1 column
test_schema = DataFrameSchema(
    columns={
        "x1": Column(
            pandas_dtype=PandasDtype.INT64,
            allow_duplicates=False,
            nullable=True,
            checks=Check(lambda x: 0 <= x <= 3, element_wise=True)
        ),
        "x2": Column(
    pandas_dtype=PandasDtype.Float64,
            nullable=True,
            checks=Check(lambda x: 0.0 <= x <= 3, element_wise=True)
)},
    coerce=False,
    strict=False,
    name="test_schema")

test_schema.validate(df)

then I get a not so informative error message. In particular, I don't get informed which column or row was the offender:
SchemaErrorTraceback (most recent call last)
<ipython-input-41-7dbd5edc716e> in <module>
     30     name="test_schema")
     31
---> 32 test_schema.validate(df)

/opt/conda/lib/python3.7/site-packages/pandera/schemas.py in validate(self, check_obj, head, tail, sample, random_state, lazy, inplace)
    590                 check_results.append(isinstance(result, pd.DataFrame))
    591             except errors.SchemaError as err:
--> 592                 error_handler.collect_error("schema_component_check", err)
    593             except errors.SchemaErrors as err:
    594                 for schema_error_dict in err.schema_errors:

/opt/conda/lib/python3.7/site-packages/pandera/error_handlers.py in collect_error(self, reason_code, schema_error, original_exc)
     30         """
     31         if not self._lazy:
---> 32             raise schema_error from original_exc
     33
     34         # delete data of validated object from SchemaError object to prevent

/opt/conda/lib/python3.7/site-packages/pandera/schemas.py in validate(self, check_obj, head, tail, sample, random_state, lazy, inplace)
    586                     lazy=lazy if schema_component.has_subcomponents else None,
    587                     # don't make a copy of the data
--> 588                     inplace=True,
    589                 )
    590                 check_results.append(isinstance(result, pd.DataFrame))

/opt/conda/lib/python3.7/site-packages/pandera/schemas.py in __call__(self, check_obj, head, tail, sample, random_state, lazy, inplace)
   1884         """Alias for ``validate`` method."""
   1885         return self.validate(
-> 1886             check_obj, head, tail, sample, random_state, lazy, inplace
   1887         )
   1888

/opt/conda/lib/python3.7/site-packages/pandera/schema_components.py in validate(self, check_obj, head, tail, sample, random_state, lazy, inplace)
    209                     )
    210             else:
--> 211                 validate_column(check_obj, column_name)
    212
    213         return check_obj

/opt/conda/lib/python3.7/site-packages/pandera/schema_components.py in validate_column(check_obj, column_name)
    189                 random_state,
    190                 lazy,
--> 191                 inplace=inplace,
    192             )
    193

/opt/conda/lib/python3.7/site-packages/pandera/schemas.py in validate(self, check_obj, head, tail, sample, random_state, lazy, inplace)
   1861                         check_index=check_index,
   1862                     ),
-> 1863                     original_exc=err,
   1864                 )
   1865

/opt/conda/lib/python3.7/site-packages/pandera/error_handlers.py in collect_error(self, reason_code, schema_error, original_exc)
     30         """
     31         if not self._lazy:
---> 32             raise schema_error from original_exc
     33
     34         # delete data of validated object from SchemaError object to prevent

SchemaError: Error while executing check function: TypeError("boolean value of NA is ambiguous")

Note that it DOES work if I check the Int64 column with the equivalentCheck.in_range(0, 3) instead
Describe the solution you'd like
The ability to check an Int64 (nullable integer column) with a lambda function, just like Float64 can be checked.
Describe alternatives you've considered
If this is not possible, then the error message could be improved, hopefully to include that Int64 can't be checked with lambda functions. Otherwise include this gotcha in the documentation (Maybe it's already there, but I couldn't find it  😬)

hey @cdagnino, I'd recommend using built-in checks or explicitly handle na case in lambda function element_wise=True. The issue you're coming up against is happening because the element-wise function doesn't know how to operate on null values.
Some solutions are:
Check(lambda x: pd.notna(x) and (0 <= x <= 3), element_wise=True)  # if you want to use element-wise
Check(lambda s: s.between(0, 3)  # vectorized check
Check.in_range(0, 3)  # built-in pandera check

hi @cosmicBboy , thanks for the solutions!
What do you think should be the result of this issue though?
Should the answer be that there won't be a change, but maybe the error message should be improved?

I have a similar problem. I am trying to check a float column. However, the column can have strings and null. But null are accepted, it shouldn't give an error. So, my question would be: how can I make a Check that accepts a column that has numbers between -90 and 90, it also accepts null (it is ok to have empty fields), but it can not have strings?
I tried doing a helper function, but the issue is that if the function fails, Pandera doesn't return any error. The clearer example is if I do float(x). If x is empty, the python error is "ValueError: could not convert string to float: ''". However, Pandera doesn't crash, it continues to run.

hi @parayamelo can you provide a minimally reproducible example of the behavior you're seeing?

@cdagnino yes I think a better error message would help here. The output of an element-wise Check function must always a boolean, so outputing an NA value should not be allowed.
Basically, right here there should only be False or True values, otherwise a SchemaDefinitionError should be raised.


Update pt.json

Updated pt.json from brazilian to portuguese and changed some fields from english to portuguese aswell.

I'm sorry, but long long time ago it was decided there would only be one pt translation file (after we tried having both pt-BR and pt-PT), and since Brazilians outnumber 21 to 1, we decided to keep it in Brazilian Portuguese.
Feel free to use this as a custom locale file as described in the docs.


Can machines communicate with each other via MAVSDK-Python? (not a drone)

Hi, I'd like to construct a bunch of hardware setup like:
Drone - Raspberry Pi (RPi) - Desktop (GCS)
I figured out how to receive drone status and inject some sort of commands between Drone and RPi via MAVSDK-Python.
https://github.com/mavlink/MAVSDK-Python/issues/430#issuecomment-1008593103 would be an example.
However, I'm struggling with how to send some data from RPi to GCS.
Is it possible to send data from RPi to GCS via MAVSDK-Python?

I close this issue as this issue is for finding an alternative way of #419.
See https://github.com/mavlink/MAVSDK-Python/issues/419#issuecomment-1008905339 for MAVSDK-Python and ROS2 integration.


Implement Project page sorting

For the new frontend add ability to sort projects by starts/contributors/forks/other metadata attributes.
Based on the user's feedback:

and also to sort by the number of contributors/stars

/assign

can you please elaborate on what needs to be done here?
I apologise if this seems like a menial task but since it's my first issue, I want to be sure that I know correctly what I'm working with here.

This one may be not that easy. It requires both backend and frontend logic implementation. It seems the backend part will require additional index setup:

https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/
https://www.algolia.com/doc/guides/managing-results/refine-results/sorting/how-to/sort-by-attribute/

I didn't add any details and was going to work on it myself. But if you feel it's something that you can handle let do that -- I'd be happy to guide you and help with any questions.
@tsu-ki let me know what you think and I'll try to come up w/ more detailed description.

sure, i'll quickly go through the code and the guide you've shared. thank you for helping me out

Hey @tsu-ki any progress on this? Feel free to reach out to me here or in our Slack channel (DMs work too) in case you need help with this one.

re-assigning after discussing it in Slack

@arkid15r , i can implement it in frontend.

@arkid15r , i can implement it in frontend.

Please read this comment. We use index engine to produce relevant search results so I doubt I can be done on the frontend.

@arkid15r , i can implement it in frontend.

Please read this comment. We use index engine to produce relevant search results so I doubt I can be done on the frontend.

Yes, after getting the results, we can sort them on the frontend. It's quite easy compared to making changes in the API call.

My point is that search/ranking/sorting can be done on the index engine side only so the frontend sorting would be limited to one page only that doesn't add a lot of value.
Let me know if I'm missing something

You're right. Frontend sorting is limited to one page and isn't good for large datasets. However, we could use frontend sorting for single pages to ensure better user experience and reduce API calls, while relying on backend sorting to handle larger datasets across pages. what're your thoughts on this approach!


Application looks it changes not accessed values in Profile

In Profile you should update most of values, but not all are written into db, and user is notified about success update.

I don't understand. Which values are not being written into the database?

OK, it looks that this problem is only with Rodne cislo.

I can't reproduce this behavior.


Add possibility to configure an animation delay

Description
Change
Adding the possibility to configure a delay for the marquee animation.  This value is passed to the Animation.delay(...) function when starting it.
Usage Example
Marquee {
    Text("Hello World!")
}.marqueeDelay(5.0)

This is merged and can be used using my fork.


Rename $module to $root across the codebase

Internal refactoring to rename $module to $root across the codebase: components, tests, helpers and documentation.
This change is not breaking and won't even affect the component behaviours as:

$module was the name of positional arguments which are in the same position
this.$module was @private, so not to be used by external code

The PR splits the renaming component by component for easier review.
Closes #5322

I can't find any mentions of $module in the code base now and as you mentioned above due to way $module was used this renaming doesn't cause any problems. Have approved!


Mark 0.16 and 0.17 as unsupported and 0.19 under development

Provide a banner that shows:

0.16, 0.17 are not supported, and
0.19 is under development.

Signed-off-by: Johannes Bräuer<EMAIL_ADDRESS>

Hello @StackScribe ,
can you please take a look? :)

So is 0.16.2-rcl going to be supported? Do we have Release Notes that explains the situation?

Good question for @johannes-b

Do we need an upgrade guide for people going from 0.15.x to 0.18.x?

Nope

@StackScribe and @oleg-nenashev , many thanks for raising concerns here!
This gave me a trigger to re-think the situation and we should not mark 0.16, and 0.17 as unsupported. Instead, I added the banner to 0.12 - 0.15 since deep links might still lead the user to these versions.


Predicate NodeAffinity failed

Question
I installed longhorn with Python and Pulumi,
The source code is available here:
https://github.com/omidraha/pulumi_example/blob/main/longhorn/longhorn.py
https://github.com/omidraha/pulumi_example/blob/main/longhorn/__main__.py
But I got the following error:
Predicate NodeAffinity failed

Environment

Longhorn version: 1.5.1
Kubernetes version: v1.28.1
Node config

OS type and version Ubuntu 20.04.6 LTS x86_64 x86_64 x86_64 GNU/Linux
Kernel version
CPU per node: 4
Memory per node:  8
Disk type: Amazon EC2 NVMe Instance Storage
Network bandwidth and latency between the nodes:

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal): EKS

Additional context
Info
curl -sSfL https://raw.githubusercontent.com/longhorn/longhorn/v1.5.1/scripts/environment_check.sh | bash

[INFO]  Required dependencies 'kubectl jq mktemp' are installed.
[INFO]  All nodes have unique hostnames.
[INFO]  Waiting for longhorn-environment-check pods to become ready (1/3)...
[INFO]  All longhorn-environment-check pods are ready (3/3).
[INFO]  MountPropagation is enabled
[INFO]  Checking iscsid...
[INFO]  Checking multipathd...
[INFO]  Checking packages...
[INFO]  Cleaning up longhorn-environment-check pods...
[INFO]  Cleanup completed.

Info
kubectl get events --sort-by=.metadata.creationTimestamp -A

longhorn-system   4s          Warning   NodeAffinity                   pod/instance-manager-d55627fd28d244702258ead89ebd57ab                 Predicate NodeAffinity failed
longhorn-system   3s          Warning   NodeAffinity                   pod/instance-manager-1408df7deb7f56638ec33cdf5dd8f2f7                 Predicate NodeAffinity failed
longhorn-system   4s          Warning   NodeAffinity                   pod/instance-manager-d55627fd28d244702258ead89ebd57ab                 Predicate NodeAffinity failed
longhorn-system   4s          Warning   NodeAffinity                   pod/instance-manager-d55627fd28d244702258ead89ebd57ab

Info
kubectl logs -n longhorn-system longhorn-manager-8nr2m

time="2023-10-19T22:13:26Z" level=info msg="Deleting instance manager pod instance-manager-94b22cd47f77eef52e310ed86c1eb73b for instance manager instance-manager-94b22cd47f77eef52e310ed86c1eb73b"
time="2023-10-19T22:13:26Z" level=info msg="Creating instance manager pod" controller=longhorn-instance-manager instanceManager=instance-manager-94b22cd47f77eef52e310ed86c1eb73b node=ip-172-16-23-174.us-east-2.compute.internal nodeID=ip-172-16-23-174.us-east-2.compute.internal
time="2023-10-19T22:13:26Z" level=info msg="Instance manager state is updated from error to starting after syncing with the pod" controller=longhorn-instance-manager instanceManager=instance-manager-94b22cd47f77eef52e310ed86c1eb73b node=ip-172-16-23-174.us-east-2.compute.internal nodeID=ip-172-16-23-174.us-east-2.compute.internal

Info
kubectl describe pod  -n longhorn-system instance-manager-1408df7deb7f56638ec33cdf5dd8f2f7

Name:             instance-manager-1408df7deb7f56638ec33cdf5dd8f2f7
Namespace:        longhorn-system
Priority:         0
Service Account:  longhorn-service-account
Node:             ip-172-16-138-34.us-east-2.compute.internal/
Start Time:       Thu, 19 Oct 2023 15:14:50 -0700
Labels:           longhorn.io/component=instance-manager
                  longhorn.io/instance-manager-image=imi-a21ea71c
                  longhorn.io/instance-manager-type=aio
                  longhorn.io/managed-by=longhorn-manager
                  longhorn.io/node=ip-172-16-138-34.us-east-2.compute.internal
Annotations:      longhorn.io/last-applied-tolerations:
                    [{"key":"key1","operator":"Equal","value":"value1","effect":"NoSchedule"},{"key":"key2","operator":"Exists","effect":"NoExecute"}]
                  longhorn.io/v2-data-engine: false
Status:           Failed
Reason:           NodeAffinity
Message:          Pod was rejected: Predicate NodeAffinity failed
IP:
IPs:              <none>
Controlled By:    InstanceManager/instance-manager-1408df7deb7f56638ec33cdf5dd8f2f7
Containers:
  instance-manager:
    Image:      longhornio/longhorn-instance-manager:v1.5.1
    Port:       <none>
    Host Port:  <none>
    Args:
      instance-manager
      --debug
      daemon
      --listen
      <IP_ADDRESS>:8500
    Requests:
      cpu:     470m
    Liveness:  tcp-socket :8500 delay=3s timeout=4s period=5s #success=1 #failure=3
    Environment:
      TLS_DIR:  /tls-files/
      POD_IP:    (v1:status.podIP)
    Mounts:
      /engine-binaries/ from engine-binaries (rw)
      /host from host (rw)
      /host/var/lib/longhorn/unix-domain-socket/ from unix-domain-socket (rw)
      /tls-files/ from longhorn-grpc-tls (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-6brbj (ro)
Volumes:
  host:
    Type:          HostPath (bare host directory volume)
    Path:          /
    HostPathType:
  engine-binaries:
    Type:          HostPath (bare host directory volume)
    Path:          /var/lib/longhorn/engine-binaries/
    HostPathType:
  unix-domain-socket:
    Type:          HostPath (bare host directory volume)
    Path:          /var/lib/longhorn/unix-domain-socket/
    HostPathType:
  longhorn-grpc-tls:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  longhorn-grpc-tls
    Optional:    true
  kube-api-access-6brbj:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   Burstable
Node-Selectors:              label-key1=label-value1
Tolerations:                 key1=value1:NoSchedule
                             key2:NoExecute op=Exists
                             node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason        Age   From     Message
  ----     ------        ----  ----     -------
  Warning  NodeAffinity  3s    kubelet  Predicate NodeAffinity failed

Info
kubectl describe pod  -n longhorn-system longhorn-driver-deployer-c876d675f-dg25h

Name:             longhorn-driver-deployer-c876d675f-dg25h
Namespace:        longhorn-system
Priority:         0
Service Account:  longhorn-service-account
Node:             ip-172-16-138-34.us-east-2.compute.internal/<IP_ADDRESS>
Start Time:       Thu, 19 Oct 2023 14:31:21 -0700
Labels:           app=longhorn-driver-deployer
                  app.kubernetes.io/instance=longhorn-exp-dc451a94
                  app.kubernetes.io/managed-by=Helm
                  app.kubernetes.io/name=longhorn
                  app.kubernetes.io/version=v1.5.1
                  helm.sh/chart=longhorn-1.5.1
                  pod-template-hash=c876d675f
Annotations:      <none>
Status:           Running
IP:               <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  ReplicaSet/longhorn-driver-deployer-c876d675f
Init Containers:
  wait-longhorn-manager:
    Container ID:  containerd://61bceb61ec822b5dc6f99f81d0b8db4e48e84448dd9fb225b5dba22bbee6a6a1
    Image:         longhornio/longhorn-manager:v1.5.1
    Image ID:      docker.io/longhornio/longhorn-manager@sha256:f29f6b568bbb76a73569b73e00ff3ed4b42fc500a2863e0523aeb8313bf9495f
    Port:          <none>
    Host Port:     <none>
    Command:
      sh
      -c
      while [ $(curl -m 1 -s -o /dev/null -w "%{http_code}" http://longhorn-backend:9500/v1) != "200" ]; do echo waiting; sleep 2; done
    State:          Terminated
      Reason:       Completed
      Exit Code:    0
      Started:      Thu, 19 Oct 2023 14:31:22 -0700
      Finished:     Thu, 19 Oct 2023 14:31:22 -0700
    Ready:          True
    Restart Count:  0
    Environment:    <none>
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-ghcjz (ro)
Containers:
  longhorn-driver-deployer:
    Container ID:  containerd://05ea4bf354dd31a226edae3d727b98b4e09f4a6c24d86b4f9e420527968a6ac9
    Image:         longhornio/longhorn-manager:v1.5.1
    Image ID:      docker.io/longhornio/longhorn-manager@sha256:f29f6b568bbb76a73569b73e00ff3ed4b42fc500a2863e0523aeb8313bf9495f
    Port:          <none>
    Host Port:     <none>
    Command:
      longhorn-manager
      -d
      deploy-driver
      --manager-image
      longhornio/longhorn-manager:v1.5.1
      --manager-url
      http://longhorn-backend:9500/v1
    State:          Waiting
      Reason:       CrashLoopBackOff
    Last State:     Terminated
      Reason:       Error
      Exit Code:    1
      Started:      Thu, 19 Oct 2023 15:10:35 -0700
      Finished:     Thu, 19 Oct 2023 15:12:37 -0700
    Ready:          False
    Restart Count:  9
    Environment:
      POD_NAMESPACE:                    longhorn-system (v1:metadata.namespace)
      NODE_NAME:                         (v1:spec.nodeName)
      SERVICE_ACCOUNT:                   (v1:spec.serviceAccountName)
      CSI_ATTACHER_IMAGE:               longhornio/csi-attacher:v4.2.0
      CSI_PROVISIONER_IMAGE:            longhornio/csi-provisioner:v3.4.1
      CSI_NODE_DRIVER_REGISTRAR_IMAGE:  longhornio/csi-node-driver-registrar:v2.7.0
      CSI_RESIZER_IMAGE:                longhornio/csi-resizer:v1.7.0
      CSI_SNAPSHOTTER_IMAGE:            longhornio/csi-snapshotter:v6.2.1
      CSI_LIVENESS_PROBE_IMAGE:         longhornio/livenessprobe:v2.9.0
    Mounts:
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-ghcjz (ro)
Conditions:
  Type              Status
  Initialized       True
  Ready             False
  ContainersReady   False
  PodScheduled      True
Volumes:
  kube-api-access-ghcjz:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   BestEffort
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                 From               Message
  ----     ------     ----                ----               -------
  Normal   Scheduled  45m                 default-scheduler  Successfully assigned longhorn-system/longhorn-driver-deployer-c876d675f-dg25h to ip-172-16-138-34.us-east-2.compute.internal
  Normal   Pulled     45m                 kubelet            Container image "longhornio/longhorn-manager:v1.5.1" already present on machine
  Normal   Created    45m                 kubelet            Created container wait-longhorn-manager
  Normal   Started    45m                 kubelet            Started container wait-longhorn-manager
  Normal   Pulled     35m (x5 over 45m)   kubelet            Container image "longhornio/longhorn-manager:v1.5.1" already present on machine
  Normal   Created    35m (x5 over 45m)   kubelet            Created container longhorn-driver-deployer
  Normal   Started    35m (x5 over 45m)   kubelet            Started container longhorn-driver-deployer
  Warning  BackOff    9s (x113 over 41m)  kubelet            Back-off restarting failed container longhorn-driver-deployer in pod longhorn-driver-deployer-c876d675f-dg25h_longhorn-system(02d0f76c-9757-44de-b6f8-914e703705c1)

Info
kubectl get nodes  -A

NAME                                          STATUS   ROLES    AGE   VERSION
ip-172-16-138-34.us-east-2.compute.internal   Ready    <none>   34m   v1.28.1
ip-172-16-21-1.us-east-2.compute.internal     Ready    <none>   34m   v1.28.1
ip-172-16-23-174.us-east-2.compute.internal   Ready    <none>   34m   v1.28.1

Info
kubectl get pods -A

NAMESPACE         NAME                                                              READY   STATUS         RESTARTS        AGE
default           longhorn-iscsi-exp-d63231cc-jzws7                                 1/1     Running        0               34m
default           longhorn-iscsi-exp-d63231cc-wllp9                                 1/1     Running        0               34m
default           longhorn-iscsi-exp-d63231cc-wz8sn                                 1/1     Running        0               34m
default           longhorn-nfs-installation-95xr2                                   1/1     Running        0               34m
default           longhorn-nfs-installation-tdwd5                                   1/1     Running        0               34m
default           longhorn-nfs-installation-wmfmj                                   1/1     Running        0               34m
kube-system       aws-node-98btm                                                    1/1     Running        0               35m
kube-system       aws-node-k5gjf                                                    1/1     Running        0               34m
kube-system       aws-node-whctm                                                    1/1     Running        0               35m
kube-system       coredns-664b6f5f5c-2kp6j                                          1/1     Running        0               32m
kube-system       coredns-664b6f5f5c-lwmmk                                          1/1     Running        0               34m
kube-system       kube-proxy-5pgws                                                  1/1     Running        0               35m
kube-system       kube-proxy-gcnxj                                                  1/1     Running        0               34m
kube-system       kube-proxy-vbdw6                                                  1/1     Running        0               35m
longhorn-system   discover-proc-kubelet-cmdline                                     0/1     Pending        0               91s
longhorn-system   instance-manager-1408df7deb7f56638ec33cdf5dd8f2f7                 0/1     NodeAffinity   0               0s
longhorn-system   instance-manager-94b22cd47f77eef52e310ed86c1eb73b                 0/1     NodeAffinity   0               0s
longhorn-system   instance-manager-d55627fd28d244702258ead89ebd57ab                 0/1     NodeAffinity   0               0s
longhorn-system   longhorn-driver-deployer-c876d675f-dg25h                          1/1     Running        8 (6m42s ago)   33m
longhorn-system   longhorn-manager-8nr2m                                            1/1     Running        0               34m
longhorn-system   longhorn-manager-dwn9b                                            1/1     Running        0               34m
longhorn-system   longhorn-manager-vjvvn                                            1/1     Running        0               34m
longhorn-system   longhorn-ui-5f6dddf97f-dvn4c                                      1/1     Running        0               32m
longhorn-system   longhorn-ui-5f6dddf97f-sb5fb                                      1/1     Running        1 (34m ago)     34m

Is your case similar to this one https://forums.rancher.com/t/longhorn-in-gke-node-affinity/19814 ?

No, It was related to defaultSettings values.
And It works now.


Consider adding filetree icons

@flukeout I saw this extension and thought of you:
https://github.com/drewbkoch/Brackets-File-Icons

Do you like that, or are you happy with what we have now?

I like the concept of icons, but I feel like this set is too vast & varied. I'll borrow some of these to make a mockup though. I think at least we could distinguish between

folders
code
images

We could also check our DB to see what kinds of files people are using.

If you pick the font/images/icons to use, we can just fork this and do it.  Nothing special about the ones chosen here.

Interesting. I'm working on this issue.

Now, I added a gif icon beside the file name. I think I need to add a function to load different gif file base on the extension name.

Where can I get the icons? @humphd

Hey @peiying16 - can you open a pull request for this change? I'll provide an icon there. We might need two colors of icons, or one color that works on both the dark and light themes.

Yeah. Most of the codes are done. I'm testing.

@flukeout PR is here https://github.com/mozilla/brackets/pull/660


Html2Canvas repository

Is this repository still maintained? There have been like 3 months without an update, should we create another repo? The author did not have any contributions on github since the last update here :(

He's still active on github, but not necessarily on this project at the moment. I don't think there are any plans to stop work on this, though single-maintainer open source projects can be slow sometimes.

#1167


Import data from Anki

ankisrs.net
Download Mac App
Sign up on the web
Click on "get shared" on mac app
Choose decks to import by downloading files
import into the mac app once downloaded

https://quizlet.com/api/2.0/docs


Support ClonedPath field for RepositorySpec

If you have already cloned the test repository, you can skip the clone by specifying that directory.
spec:
  repos:
    - name: test-repo
      value:
        clonedPath: /path/to/repo

Codecov Report

Merging #56 (5bc3db0) into master (530e978) will increase coverage by 0.11%.
The diff coverage is 50.00%.

@@            Coverage Diff             @@
##           master      #56      +/-   ##
==========================================
+ Coverage   60.74%   60.86%   +0.11%
==========================================
  Files          15       15
  Lines        2606     2624      +18
==========================================
+ Hits         1583     1597      +14
  Misses        766      766
- Partials      257      261       +4


[Sprig App] Brix and Boxes

Author name
Author: amino47
About your game
What is your game about?
I created a puzzle game where you have to move the boxes out of the way, so you can reach the green flag. I included music and a win sound effect.
How do you play your game?
W Up
A Left
S Down
D Right

Nice game! It really reminds me of those old coolmathgames games I used to play, and I love the music. Thanks for the submission :)
If you're a teen, you can get your Sprig here! sprig-order.hackclub.dev
Hack Clubbers would love to see this! Just post a link and 1-2 sentences talking about your game to our #ship channel ;)


NSMenu issue

Did not use any code from this library, just linked to this library, and the rounded corners of the Menu disappeared.

This is example code
NSMenuIssue.zip

Yes I'm aware of this bug and it seems to be a bug on Apple's side. I'm using NSView's menu property, which somehow doesn't have the rounded corners.

@flocked After a series of investigations and checks, I found that the modifications in this  commit caused the disappearance of the Menu's rounded corners. It is speculated that there might be properties with similar names within Apple's internal classes, and exposing them to objc could have overridden the original implementation.

Thanks! This indeed fixed the error! I took a look at the underlying NSView code and Apple already is using the property _cornerRadius. So my code somehow overwrote their code (which should normally not be the case).


Upgrade OpenRA to 20150614

Updated cask OpenRA to version 20150614. Added required dependency for mono-mdk.

Thank you for the contribution. It was merged directly as 35fdb7512673b81c85dccc92709f065732eeee58 to keep commit history cleaner. Your contribution is still credited to you.


Rating calculator

Doc says :
"Instantiate a RatingCalculator object
at instantiation, you can set the default rating for a player's volatility and the system constant for your game ("τ", which constrains changes in volatility over time) or just accept the defaults"
if there are 3 players, then at first the rating calculator uses the default values.
But for the next time
'RatingCalculator' needs to be initialised with volatility of which player p1 or p2 or p3 ?
PS : For a game If p1 beats p2, p3 then does it means p1 beat p2 and p1 beat p3 ?

@goochjs

Hi,
To answer your first question, it doesn't matter how you initialise the RatingCalculator for the second rating period as your players will each have their own volatilities. I would suggest you use the same default setting each time, in case you introduce a new player.
The answer to your second question is "sort of" as each game can only have two competitors.
J.

Actually it I can see that if I use the default volatility then the deviation constantly increases for the player after subsequent games. This indeed will be a factor after which the new rating  is computed.


Move String matchers to common

This commit moves String and associated code to the common modules. An important point to notice is that this commit will introduce some breaking changes, as some files were moved together to the common modules.
It was assumed that this is OK, as perhaps KotlinTest these changes are for KotlinTest 4.0, in which some breaking changes are expected.

Are the breaking changes limited to changing the package names ?

Yes

No change to functionality was made (yet, at least)


Unable to view files in newest insiders build

VSCode Version: Code - Insiders 1.19.0-insider (432b53bc3a263fda8db6ecca83d1ce89ede04bf2, 2017-11-06T06:22:36.757Z)
OS Version: Linux x64 4.10.0-38-generic
Extensions:

Extension
Author (truncated)
Version

vscode-eslint
dba
1.4.2

python
don
0.7.0

gitlens
eam
5.7.1

cpptools
ms-
0.14.0

vetur
oct
0.11.0

vim
vsc
0.10.2

Steps to Reproduce:

Open any file
The text view is blank.

Reproduces without extensions: Yes
It also is a problem in both normal and multi-root workspaces.
The following shows up in the dev tools console:
shell.ts:459 charCode is not defined: ReferenceError: charCode is not defined
    at o (file:///usr/share/code-insiders/resources/app/out/vs/workbench/workbench.main.js:9:530695)
    at Object.s [as renderViewLine] (file:///usr/share/code-insiders/resources/app/out/vs/workbench/workbench.main.js:9:531359)
    at e.renderLine (file:///usr/share/code-insiders/resources/app/out/vs/workbench/workbench.main.js:9:1491408)
    at e._finishRendering (file:///usr/share/code-insiders/resources/app/out/vs/workbench/workbench.main.js:9:400302)
    at e.render (file:///usr/share/code-insiders/resources/app/out/vs/workbench/workbench.main.js:9:398052)
    at e.renderLines (file:///usr/share/code-insiders/resources/app/out/vs/workbench/workbench.main.js:9:397467)
    at t.renderText (file:///usr/share/code-insiders/resources/app/out/vs/workbench/workbench.main.js:9:1538123)
    at t._actualRender (file:///usr/share/code-insiders/resources/app/out/vs/workbench/workbench.main.js:9:1641210)
    at file:///usr/share/code-insiders/resources/app/out/vs/workbench/workbench.main.js:9:1640476
    at z (file:///usr/share/code-insiders/resources/app/out/vs/workbench/workbench.main.js:9:1633012)

Oops, looks like this is also a duplicate of #37703


the remainder of div result is zero

In UINT64 class,when div && other > this,why this.remainder = 0?
I think this is an error.
// other > this: 0
if ( other.gt(this) ) {
this.remainder = new UINT64(0)
this._a00 = 0
this._a16 = 0
this._a32 = 0
this._a48 = 0
return this
}

Yes you are right, it should be itself. Fixed in 0.2.1.
Thank you for spotting this!


Install Docs needs updated

https://docs.photonvision.org/en/latest/docs/getting-started/installation/limelight.html should not refer to gloworm image, since it's old.
Update install guide to point to images in the main photonvision release page. references to the pi image repo shouldn't' be needed anymore, that's no longer the "user-facing" way to get photon.

Bumping with some specifics, since folks are gonna want this earlier rather than later. I'll try to start tackling this tonight. Specifically -

Change "Installation" section to "Getting Started"
Split out to have one unique page per hardware. Hardware should include (in order) Pi 3, Pi 4, Limelight, Gloworm, SnakeEyes, Windows PC, Linux PC, Mac PC, Romi
Add new section for "Command Line Usage" for some background on how to use the command line portion.

Pi 3 can still reference the image. Pi 4 should make mention that the Pi 3 instructions might work, but otherwise provide a "download latest raspian and run the linux script" procedure.
Review the other hardware docs too - don't delete any info, just mark things that "are not yet tested for 2023"

@gerth2 Seems to be good to close? Clarify if there is something to be added here, your last PR seems to have taken care of most of this

yup I think we're done here.


Replace compose with quick-start standalone OpenWhisk.

We've discussed in the past using the standalone controller as the new quick start. This morning I was trying to help someone in the community slack and I had trouble bringing up the compose version of the quick start. Plus it took many minutes to pull all the docker images. By contrast standalone is much lighter weight.
This is an attempt to replace compose with standalone controller in the welcome docs.
cc @chetanmeh @sciabarra I know we can do even better with the docker self container version. If you can point me to those steps, I can include them.
Description

Related issue and scope

[ ] I opened an issue to propose and discuss this change (#????)

My changes affect the following components

[ ] API
[ ] Controller
[ ] Message Bus (e.g., Kafka)
[ ] Loadbalancer
[ ] Invoker
[ ] Intrinsic actions (e.g., sequences, conductors)
[ ] Data stores (e.g., CouchDB)
[ ] Tests
[ ] Deployment
[ ] CLI
[ ] General tooling
[x] Documentation

Types of changes

[ ] Bug fix (generally a non-breaking change which closes an issue).
[ ] Enhancement or new feature (adds new functionality).
[ ] Breaking change (a bug fix or enhancement which changes existing behavior).

Checklist:

[x] I signed an Apache CLA.
[x] I reviewed the style guides and followed the recommendations (Travis CI will check :).
[x] I added tests to cover my changes.
[x] My changes require further changes to the documentation.
[x] I updated the documentation where necessary.

Thanks Dave, Dominic and Chetan. Will incorporate the feedback today.

Thanks for all the feedback. Will merge when Travis approves.

Codecov Report

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

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


I get these errors, can someone help?

When using the program, i get these errors,

Could someone help me on fixing this problem?

If you're unable to understand the simple errors it's throwing, no offense but you really need to spend some time learning about the terminal...

Click me for solution
Install xterm. That's it. Please spend some of your time learning about how to use bash and the terminal so you can solve these issues on your own in the future.

I am indeed learning about the terminal more the last time :) but thanks

sudo apt-get install xterm


incorrect link in src

when save textarea content in database
url of src image is incorrect
i want to change it
How can i change link

Here, let me help you ask your question correctly:

What is "correct url"?
What is "incorrect url"?

Thank you all.
I'm going to close this issue since there is no further information.


HDDS-11601. Intermittent failure in acceptance balancer test.

What changes were proposed in this pull request?
Fixed LOWER_LIWIT in test-ec.sh of ozone-balancer.
What is the link to the Apache JIRA
https://issues.apache.org/jira/browse/HDDS-11601
How was this patch tested?
Build-branch workflow.

I'm sorry, I missed that. I'll take a look and get back with a fix

Seems to be working now, I ran the patch several times on the build-branch workflow, and there were no errors.

It failed again with 92291072 > 104857600 * 1.4should be true. I’ll try changing -i 1 to -i 2 in ozone admin containerbalancer start -t 0.1 -d 100 -i 1, I think this will solve the problem.

Thanks @Daniilchik for updating the patch.  I just launched a repeated run for balancer.  In the meantime, can you please resolve the conflict?

2/10 failures:
Verify Container Balancer for RATIS/EC containers                     | FAIL |
'97538048 > 104857600 * 1' should be true.

Verify Container Balancer for RATIS/EC containers                     | FAIL |
'103829504 > 104857600 * 1' should be true.

I've resolved the conflict and fixed LOWER_LIMIT in the test

I've resolved the conflict and fixed LOWER_LIMIT in the test

Thanks.
Reducing lower limit arbitrarily does not explain the difference in runs.  Let's keep this as draft until we can find the root cause of the problem.
Please check the difference between runs,
passing:
Number of Datanodes involved: 6. Size moved: 170 MB

failing:
Number of Datanodes involved: 5. Size moved: 96 MB

Maybe we need more iterations.  Maybe we need to close EC container after writing each 100MB key, to get more uniform container sizes.

Disabled the EC test in master temporarily: 72e56d7508faa1248a33dc0c109b0aac10547b84

Thanks @Daniilchik for the update.  I guess creating 3 keys instead of 5 is OK.
(FYI, when iterating on the fix and running repeat-acceptance-test manually, you can skip regular CI (build-branch) by including [skip ci] in the commit message.)

Fixed the test. Build-branch tests passed, and the repeat-acceptance-test passed as well.


Invalid visualization type "enhanced-table" with kibana 7.9.2

Hello and thank you for this very neat plugin.
I just updated our ELK stack to 7.9.2 and removed/installed enhanced-table 1.10.1, but now all visualizations using enhanced-table returns "Invalid visualization type "enhanced-table".
When creating a new vis' the enhanced-table is not listed.
Would you have any idea how to find what can be wrong ?
Thanks.
[root@es-node01 ~]# sudo -u kibana /usr/share/kibana/bin/kibana-plugin list
<EMAIL_ADDRESS>
[root@es-node01 ~]# rpm -qa | grep kibana
kibana-7.9.2-1.x86_64

Hi,
I just tested to install enhanced-table 1.10.1 on Kibana 7.9.2 and I don't reproduce this issue.
Just 2 simple questions:

it is quite obvious, but do you install this package: https://github.com/fbaligand/kibana-enhanced-table/releases/download/v1.10.1/enhanced-table-1.10.1_7.9.2.zip ?
do you install using "kibana-plugin install file:///path/to/enhanced-table-1.10.1_7.9.2.zip ?

If all answers are yes, I invite you to do these actions:

stop kibana
remove $KIBANA_HOME/optimize folder
start kibana
empty your browser cache
reload kibana

Hello,
Thanks a lot.
Yes I installed this package and like you said.
I followed the steps you suggested and it now works. Not sure if it was the browser cache or the optimize folders though :)
Thanks again,
Sébastien

Nice to see that it finally works!
Starting from Kibana 7.9, normally, optimize folder is not anymore an issue. So it's probably the browser cache.
That said, without an isolated test, you will never know :)


Ads Play Fast, But "No Adblockers Allowed" Screen Still Appears

Script version
5.3
Describe the bug
I read the new announcement, so I understand that for now, ads will still show, albeit played at a faster speed than usual. However, while this does happen, immediately after the ad ends, the "Ad blockers violate..." screen appears.
Expected behavior
I expected to either be able to skip the ads like normal, or in the case where you can't skip the ad(s), view the video.
Screenshots
Here is a video demonstrating the issue.
https://github.com/TheRealJoelmatic/RemoveAdblockThing/assets/156716272/1e9b08f7-461d-4acb-b6fe-c2a67cedc3f2
Desktop (please complete the following information):

OS: Windows
Chrome
Version 125.0.6422.142

getting the same issue

same issue too, why is YT so greedy geesh

This only became a problem when I updated, first it just fast forwarded instead of skipping completely with occasional freezing, now I have this issue. Really strange.

Same issue. Seem like the update doesn't do much.

I've updated the script were this on longer happens. Please let me know if it works for u now. v5.4
also this a duplicate issue.
(https://github.com/TheRealJoelmatic/RemoveAdblockThing/issues/439)


New Feature - Support Consul ACL token

consul server is enbled acl.
how did set consulclient configuration token field?

@toby2o12 Thanks for your interest in the project. I don't think this feature is supported at the moment.
This is something we can definitely add. If you would like to do it yourself and submit a PR let me know and I will give you advice on how to complete the feature.

+1，Need it too.

@JCelento awesome :)
I haven't looked at how to do this yet but my guess would be the following class needs to pass the key to Consul?
https://github.com/ThreeMammals/Ocelot/blob/develop/src/Ocelot/ServiceDiscovery/Providers/ConsulServiceDiscoveryProvider.cs
I would add the key to FileServiceDiscoveryProvider and call it Key so other things might be able to use the same property.
Map this onto ServiceProviderConfiguration internal object..
Then map that to ConsulRegistryConfiguration..
This would then be available to use in ConsulServiceDiscoveryProvider..
ConsulClient is from another lib and I guess it has functionality to handle the key in a nice way!
The other use case would be to add it to ConsulFileConfigurationRepository which might also need it when calling Consul.
Does this help you get started?

@JCelento I'm going to start working on this now, just wanted to let you know in case you started :)

will close after new package released

Can add ACL token in version 5.5.1 (just released). Please see docs here


Fix vertex color looks darker in gles2

Add auto convert to srgb code in material
related to https://github.com/godotengine/godot/issues/82994, https://github.com/godotengine/godot/issues/30701
GLES2 gltf before fix

GLES2 gltf after fix(looks same as GLES3)

fbx looks brighter cause blender export fbx vertex color in srgb space, check the is_srgb vertex color in material will fix this.
GLES3 fbx/gltf not changed(already correct).

How do you mean GLES2? There's no GLES2 in 4.x


Post params missing

I have the following
Rack::Attack.throttle('req/preview', limit: 3, period: 1.minute) do |req|
  puts "Rack::Attack> #{req.params.inspect}"
  req.params['item_id'] if "preview".in?(req.path) && req.post?
end

In my controller I have:
def preview
puts "Preview> #{params.inspect}"
...
end

When I run the following in my specs:
post items_preview_path(:item_id => @item.id, :preview_email =><EMAIL_ADDRESS>
Here the print in the terminal:
Rack::Attack><EMAIL_ADDRESS>Preview><EMAIL_ADDRESS>"action"=>"preview", "controller"=>"items", "item_id"=>"1"}

I cannot figure out why I don't have access to params[:item_id] in the throttle block.

@damienbrz Good question!
The item_id is actually in the request path (like, /item/1234/preview) from Rack's perspective (not a query or POST param like req.params returns). Rails router magic parses it out of the request path and sticks it in the params.
So your throttle should look for the item_id in the path. Here's a completely untested example:
Rack::Attack.throttle('req/preview', limit: 3, period: 1.minute) do |req|
  if req.post? && match = req.path.match(/^\/item\/(\w+)\/preview$/)
    match[1]
  end
end

Thanks @ktheory :)


Segfault when running tests after compiling 0.2.3 on OSX 10.8.2

I'm trying to get Julia compiled, and I've run into a snag with the OpenBLAS 0.2.3 compilation:
(build with make CC="clang -mmacosx-version-min=10.6" FC="gfortran" FFLAGS="-ff2c -O2 -fPIC" USE_THREAD=1)
OPENBLAS_NUM_THREADS=1 OMP_NUM_THREADS=1 ./dblat1
Real BLAS Test Program Results
Test of subprogram number  1             DDOT
----- PASS -----
Test of subprogram number  2            DAXPY
----- PASS -----
Test of subprogram number  3            DROTG
----- PASS -----
Test of subprogram number  4             DROT
----- PASS -----
Test of subprogram number  5            DCOPY
----- PASS -----
Test of subprogram number  6            DSWAP
----- PASS -----
Test of subprogram number  7            DNRM2
----- PASS -----
Test of subprogram number  8            DASUM
----- PASS -----
Test of subprogram number  9            DSCAL
----- PASS -----
Test of subprogram number 10            IDAMAX
----- PASS -----
OPENBLAS_NUM_THREADS=1 OMP_NUM_THREADS=1 ./cblat1
Complex BLAS Test Program Results
Test of subprogram number  1            CDOTC
Program received signal SIGSEGV: Segmentation fault - invalid memory reference.
Backtrace for this error:
#0  0x100019bbe
#1  0x10001a2d4
#2  0x7fff98d598e9
gfortran -ff2c -O2  -o cblat2 cblat2.o ../libopenblas_sandybridgep-r0.2.3.a -lpthread -lgfortran  -lpthread -lgfortran
gfortran -ff2c -O2  -o zblat2 zblat2.o ../libopenblas_sandybridgep-r0.2.3.a -lpthread -lgfortran  -lpthread -lgfortran
rm -f ?BLAT2.SUMM
OPENBLAS_NUM_THREADS=1 OMP_NUM_THREADS=1 ./sblat2 < ./sblat2.dat
make[1]: *** [level1] Segmentation fault: 11
make[1]: *** Waiting for unfinished jobs....
OPENBLAS_NUM_THREADS=1 OMP_NUM_THREADS=1 ./dblat2 < ./dblat2.dat
OPENBLAS_NUM_THREADS=1 OMP_NUM_THREADS=1 ./cblat2 < ./cblat2.dat
OPENBLAS_NUM_THREADS=1 OMP_NUM_THREADS=1 ./zblat2 < ./zblat2.dat
rm -f ?BLAT2.SUMM
OPENBLAS_NUM_THREADS=2 ./sblat2 < ./sblat2.dat
OPENBLAS_NUM_THREADS=2 ./dblat2 < ./dblat2.dat
OPENBLAS_NUM_THREADS=2 ./cblat2 < ./cblat2.dat
OPENBLAS_NUM_THREADS=2 ./zblat2 < ./zblat2.dat
make: *** [tests] Error 2
It looks like I have to use clang to compile (it fails compiling kernels with gcc), so I'm suspecting an incompatibility between the gfortran I have and clang:

fortran -v
Using built-in specs.
COLLECT_GCC=gfortran
COLLECT_LTO_WRAPPER=/usr/local/libexec/gcc/x86_64-apple-darwin11.4.0/4.7.1/lto-wrapper
Target: x86_64-apple-darwin11.4.0
Configured with: ../gcc-4.7.1/configure --enable-languages=fortran
Thread model: posix
gcc version 4.7.1 (GCC)
clang -v
Apple clang version 4.1 (tags/Apple/clang-421.11.66) (based on LLVM 3.1svn)
Target: x86_64-apple-darwin12.2.0
Thread model: posix

Any guidance would be appreciated!

Interesting compiling with just make CC=clang FC=gfortran seems to work fine. Optimization/other flags issue? Stay tuned.

I tried to compile with the command:
sudo make CC=clang FC=gfortran -j 8

the error didn't occur and finally successed

Well, that error report was nine years ago (and even back then there should have been no reason to tell the compiler to assume unusual calling conventions that make it compatible with the ancient f2c converter)


Typo "@immediate_sync"→"@immediate_sync"

bold with escape characters
https://docs.microsoft.com/en-us/sql/relational-databases/system-stored-procedures/sp-reinitpullsubscription-transact-sql?view=sql-server-ver15

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

Thanks.


OwnTracks (via HTTP)

Make sure you are running the latest version of Home Assistant before reporting an issue.
You should only file an issue if you found a bug. Feature and enhancement requests should go in the Feature Requests section of our community forum:
Home Assistant release (hass --version):
0.55
Python release (python3 --version):
3.6
Component/platform:
Description of problem:
OwnTracks via HTTP does not work. I set it up in configuration file:
device_tracker:
   - platform: owntracks_http
      max_gps_accuracy: 100

I configured phone:
Mode: HTTP
Identification: turned authentication on, username homeassistant and my API password that I use to login to Home Assistant.
URL: https://johns.duckdns.org/api/owntracks/johns/iphone
When I restarted my HA, I received message that my known_devices.yaml file was not found, so I added it and entered the following:
johns_iphone:
  name: John
  mac: xx:xx:xx:xx:xx:xx
  picture:
  gravatar:
  track: yes
  hide_if_away: no

After I restarted my HA, I have the following in log:
2017-10-08 01:10:17 ERROR (MainThread) [aiohttp.server]
 Error handling request Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.6/site-packages/aiohttp/web_protocol.py", line 278, in ``data_received messages, upgraded, tail = self._request_parser.feed_data(data)
  File "aiohttp/_http_parser.pyx", line 274, in aiohttp._http_parser.HttpParser.feed_data (aiohttp/_http_parser.c:4364) aiohttp.http_exceptions.BadStatusLine: invalid HTTP method
 2017-10-08 01:11:50 ERROR (MainThread) [aiohttp.server] Error handling request Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.6/site-packages/aiohttp/web_protocol.py", line 278, in data_received messages, upgraded, tail = self._request_parser.feed_data(data)
  File "aiohttp/_http_parser.pyx", line 274, in aiohttp._http_parser.HttpParser.feed_data (aiohttp/_http_parser.c:4364) aiohttp.http_exceptions.BadStatusLine: invalid HTTP method

Also, my iPhone cannot connect. It says connecting and follows with error message:
error The request timed out. {
    NSErrorFailingURLKey = "https://johns.duckdns.org:8123/api/owntracks/johns/iphone";
    NSErrorFailingURLStringKey = "https://johns.duckdns.org:8123/api/owntracks/johns/iphone";
    NSLocalizedDescription = "The request timed out.";
    NSUnderlyingError = "Error Domain=kCFErrorDomainCFNetwork Code=-1001 \"(null)\" UserInfo={_kCFStreamErrorCodeKey=-2102, _kCFStreamErrorDomainKey=4}";
    "_kCFStreamErrorCodeKey" = "-2102";
    "_kCFStreamErrorDomainKey" = 4;
}

Expected:
Problem-relevant configuration.yaml entries and steps to reproduce:

Traceback (if applicable):

Additional info:

I follow this issue. I am also trying to configure my hass.io build with the new owntracks (via http) component. I have configured everything as suggested in this page (https://home-assistant.io/components/device_tracker.owntracks_http/) but I can't make it work obtaining this (https://imgur.com/jgAMnbI) error inside the android application.

Just to add my 2 cents. The http owntracks work for me Hassbian 1.3 (stretch) and HA 0.55 BUT I'm not using https at the moment only http, looking at the above two issues both are using https so could be an issue with that part of the setup in owntracks (just thinking out load).

I forgot to say that I use Python Virtual Env.

@twit123 uhm I don't think I'm using https

@leobel96 I presumed from your error message (SSL exception) that you were using https.

Example shows https. I tried http and, it seems, the problem is fixed. Thank you.


Save host:port locally

I do not know do we save host:port in latest version but latest version in googleplay doesn't save it. @lidaamber maybe it's already implemented, so close this issue if so.

@tshemsedinov Implemented.

It's already implemented in 82e4413cc0cf9e4cba6f1d2e48312671674994df and caa19df75936dba7b0be61812864e0da5ca0a488

@lidaamber current implementation uses stored dictionary of all successfully used passwords, right? That's great and much better then I thought. But after exit and back to login screen again could we use last successfully used passwords already entered in input boxes? (no need to enter first letter and select from the list, just click connect button) ? Together with dictionary it will be best solution for user, I suppose.

@tshemsedinov do you mean storing last entered host/port pair during one session (until the application gets turned off) or during whole application usage?

@lidaamber whole usage, it should appear after restarting, by default, to minimize operations needed to start app and use. I think we can even automatically connect to latest server. We can showing connection screen with entered latest host:port just after manual "Leave server".

@tshemsedinov ok
@MariaKokshaikina could you store last entered host/port pair and connect to the last host/port automatically when application starts? And could you fill host and port fields with this pair values in ConnectionFragment, please?

@lidaamber ok


ja2-stracciatella: Revert from legacy backticks to using $(...)

Description
First PR among the set of five PRs aimed at fixing issue #517. This PR changes all the use of backticks for command substitution under the ja2-stracciatella engine.
Chose this engine to be part of the first PR because it has the least number of recurrences of backticks.
Common Code Submissions

[x] Have you verified that the changes are isolated to the features or fixes you are wanting to do?
[x] Have you tested at least one of the engines to ensure that your changes do not break existing workflow?
[x] Have you described what your changes are accomplishing?

@OBITORASU

Rename the pull request to describe the engine being changed. Such as "ja2-stracciatella - Revert from legacy backticks to using $(...)"
Provide a log showing it running twice, the first time you should see "No Version Found", then the second time a log showing "Found version: ". This is to show that the check is working properly.

This is the entire log of running start_build.sh and package.sh one after the other twice.
(steamrt soldier 0.20210906.1)root@47967305c220:/packages# ./common/start_build.sh ja2-stracciatella
++ set -e
++ export pstart=/packages
++ pstart=/packages
++ export diststart=/packages/dist
++ diststart=/packages/dist
+ pushd engines/ja2-stracciatella
/packages/engines/ja2-stracciatella /packages
+ source env.sh
++ export STEAM_APP_ID_LIST=215930
++ STEAM_APP_ID_LIST=215930
+ log_environment
+ pwd
/packages/engines/ja2-stracciatella
+ nproc
12
+ setup_dist_dirs 215930
+ '[' -z '' ']'
+ for app_id in $1
+ mkdir -p /packages/dist/215930/dist/
+ mkdir -p /packages/dist/ja2-stracciatella
+ echo APP_IDS=215930
+ git config --global user.email<EMAIL_ADDRESS>+ git config --global user.name 'GitHub Action'
+ install_latest_cmake
+ wget https://github.com/Kitware/CMake/releases/download/v3.21.2/cmake-3.21.2-linux-x86_64.sh
--2021-10-01 03:52:36--  https://github.com/Kitware/CMake/releases/download/v3.21.2/cmake-3.21.2-linux-x86_64.sh
Resolving github.com (github.com)... <IP_ADDRESS>
Connecting to github.com (github.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://github-releases.githubusercontent.com/537699/ea29d7f6-d0d3-4798-9160-d9d333e74f13?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20211001%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20211001T035506Z&X-Amz-Expires=300&X-Amz-Signature=484d96ad027fe568899a5b189b464c534c6c4cd5b58d18563e600b9cd21baf74&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=537699&response-content-disposition=attachment%3B%20filename%3Dcmake-3.21.2-linux-x86_64.sh&response-content-type=application%2Foctet-stream [following]
--2021-10-01 03:52:36--  https://github-releases.githubusercontent.com/537699/ea29d7f6-d0d3-4798-9160-d9d333e74f13?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20211001%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20211001T035506Z&X-Amz-Expires=300&X-Amz-Signature=484d96ad027fe568899a5b189b464c534c6c4cd5b58d18563e600b9cd21baf74&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=537699&response-content-disposition=attachment%3B%20filename%3Dcmake-3.21.2-linux-x86_64.sh&response-content-type=application%2Foctet-stream
Resolving github-releases.githubusercontent.com (github-releases.githubusercontent.com)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
Connecting to github-releases.githubusercontent.com (github-releases.githubusercontent.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 44382646 (42M) [application/octet-stream]
Saving to: 'cmake-3.21.2-linux-x86_64.sh'

cmake-3.21.2-linux-x86_64.sh  100%[=================================================>]  42.33M  16.8MB/s    in 2.5s

2021-10-01 03:52:39 (16.8 MB/s) - 'cmake-3.21.2-linux-x86_64.sh' saved [44382646/44382646]

+ chmod +x cmake-3.21.2-linux-x86_64.sh
+ ./cmake-3.21.2-linux-x86_64.sh --skip-license --prefix=/usr
CMake Installer Version: 3.21.2, Copyright (c) Kitware
This is a self-extracting archive.
The archive will be extracted to: /usr

Using target directory: /usr
Extracting, please wait...

Unpacking finished successfully
+ install_latest_meson
+ wget https://bootstrap.pypa.io/get-pip.py
--2021-10-01 03:52:40--  https://bootstrap.pypa.io/get-pip.py
Resolving bootstrap.pypa.io (bootstrap.pypa.io)... <IP_ADDRESS>, 2a04:4e42:59::175
Connecting to bootstrap.pypa.io (bootstrap.pypa.io)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1946810 (1.9M) [text/x-python]
Saving to: 'get-pip.py'

get-pip.py                    100%[=================================================>]   1.86M  8.73MB/s    in 0.2s

2021-10-01 03:52:41 (8.73 MB/s) - 'get-pip.py' saved [1946810/1946810]

+ python3 get-pip.py
Collecting pip
  Downloading pip-21.2.4-py3-none-any.whl (1.6 MB)
     |████████████████████████████████| 1.6 MB 1.8 MB/s
Collecting setuptools
  Downloading setuptools-58.1.0-py3-none-any.whl (816 kB)
     |████████████████████████████████| 816 kB 25.2 MB/s
Collecting wheel
  Downloading wheel-0.37.0-py2.py3-none-any.whl (35 kB)
Installing collected packages: wheel, setuptools, pip
Successfully installed pip-21.2.4 setuptools-58.1.0 wheel-0.37.0
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
+ pip3 install meson --upgrade
Requirement already satisfied: meson in /usr/lib/python3/dist-packages (0.49.2)
Collecting meson
  Downloading meson-0.59.2.tar.gz (2.0 MB)
     |████████████████████████████████| 2.0 MB 2.3 MB/s
  Installing build dependencies ... done
  Getting requirements to build wheel ... done
    Preparing wheel metadata ... done
Building wheels for collected packages: meson
  Building wheel for meson (PEP 517) ... done
  Created wheel for meson: filename=meson-0.59.2-py3-none-any.whl size=808742 sha256=c991f10ff9d58123c61accb57f5c7511e4d6d401db097ec0779bfd2fb20bad83
  Stored in directory: /root/.cache/pip/wheels/55/62/0f/419ed16dc705cbcd99e4e3adb7b9d5b36fd5c636fe57c2002a
Successfully built meson
Installing collected packages: meson
  Attempting uninstall: meson
    Found existing installation: meson 0.49.2
    Uninstalling meson-0.49.2:
      Successfully uninstalled meson-0.49.2
Successfully installed meson-0.59.2
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
+ '[' '!' -z '' ']'
+ '[' '!' -z '' ']'
+ '[' '!' -z '' ']'
+ gcc --version
gcc (Debian 8.3.0-6) 8.3.0
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

+ '[' '!' -z '' ']'
+ source ./build.sh
++ cp -rfv assets/run-ja2.sh /packages/dist/215930/dist/
'assets/run-ja2.sh' -> '/packages/dist/215930/dist/run-ja2.sh'
+ copy_license_file 215930
+ '[' -z '' ']'
+ echo 'Warning: license file path is not set.'
Warning: license file path is not set.
+ popd
/packages
(steamrt soldier 0.20210906.1)root@47967305c220:/packages# ./common/package.sh ja2-stracciatella
++ set -e
++ export pstart=/packages
++ pstart=/packages
++ export diststart=/packages/dist
++ diststart=/packages/dist
+ pushd engines/ja2-stracciatella
/packages/engines/ja2-stracciatella /packages
+ source env.sh
++ export STEAM_APP_ID_LIST=215930
++ STEAM_APP_ID_LIST=215930
+ log_environment
+ pwd
/packages/engines/ja2-stracciatella
+ nproc
12
+ popd
/packages
+ pushd dist
/packages/dist /packages
+ '[' -z '' ']'
+ create_archives
+ '[' -z '' ']'
+ for app_id in $STEAM_APP_ID_LIST
+ filename=ja2-stracciatella-215930
+ pushd 215930
/packages/dist/215930 /packages/dist /packages
+ tar --format=v7 --mode=a+rwX,o-w --owner=0 --group=0 --mtime=@1560859200 -cf ja2-stracciatella-215930.tar dist
+ xz ja2-stracciatella-215930.tar
+ sha1sum ja2-stracciatella-215930.tar.xz
3b7272a0ae337de7c9527a49d52cd7e7339adf99  ja2-stracciatella-215930.tar.xz
+ popd
/packages/dist /packages
+ mv 215930/ja2-stracciatella-215930.tar.xz /packages/dist/ja2-stracciatella/ja2-stracciatella-215930.tar.xz
+ rm -rf 215930
+ popd
/packages
(steamrt soldier 0.20210906.1)root@47967305c220:/packages# ./common/start_build.sh ja2-stracciatella
++ set -e
++ export pstart=/packages
++ pstart=/packages
++ export diststart=/packages/dist
++ diststart=/packages/dist
+ pushd engines/ja2-stracciatella
/packages/engines/ja2-stracciatella /packages
+ source env.sh
++ export STEAM_APP_ID_LIST=215930
++ STEAM_APP_ID_LIST=215930
+ log_environment
+ pwd
/packages/engines/ja2-stracciatella
+ nproc
12
+ setup_dist_dirs 215930
+ '[' -z '' ']'
+ for app_id in $1
+ mkdir -p /packages/dist/215930/dist/
+ mkdir -p /packages/dist/ja2-stracciatella
+ echo APP_IDS=215930
+ git config --global user.email<EMAIL_ADDRESS>+ git config --global user.name 'GitHub Action'
+ install_latest_cmake
+ wget https://github.com/Kitware/CMake/releases/download/v3.21.2/cmake-3.21.2-linux-x86_64.sh
--2021-10-01 03:53:17--  https://github.com/Kitware/CMake/releases/download/v3.21.2/cmake-3.21.2-linux-x86_64.sh
Resolving github.com (github.com)... <IP_ADDRESS>
Connecting to github.com (github.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 302 Found
Location: https://github-releases.githubusercontent.com/537699/ea29d7f6-d0d3-4798-9160-d9d333e74f13?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20211001%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20211001T035506Z&X-Amz-Expires=300&X-Amz-Signature=484d96ad027fe568899a5b189b464c534c6c4cd5b58d18563e600b9cd21baf74&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=537699&response-content-disposition=attachment%3B%20filename%3Dcmake-3.21.2-linux-x86_64.sh&response-content-type=application%2Foctet-stream [following]
--2021-10-01 03:53:17--  https://github-releases.githubusercontent.com/537699/ea29d7f6-d0d3-4798-9160-d9d333e74f13?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=AKIAIWNJYAX4CSVEH53A%2F20211001%2Fus-east-1%2Fs3%2Faws4_request&X-Amz-Date=20211001T035506Z&X-Amz-Expires=300&X-Amz-Signature=484d96ad027fe568899a5b189b464c534c6c4cd5b58d18563e600b9cd21baf74&X-Amz-SignedHeaders=host&actor_id=0&key_id=0&repo_id=537699&response-content-disposition=attachment%3B%20filename%3Dcmake-3.21.2-linux-x86_64.sh&response-content-type=application%2Foctet-stream
Resolving github-releases.githubusercontent.com (github-releases.githubusercontent.com)... <IP_ADDRESS>, <IP_ADDRESS>, <IP_ADDRESS>, ...
Connecting to github-releases.githubusercontent.com (github-releases.githubusercontent.com)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 44382646 (42M) [application/octet-stream]
Saving to: 'cmake-3.21.2-linux-x86_64.sh.1'

cmake-3.21.2-linux-x86_64.sh. 100%[=================================================>]  42.33M  23.5MB/s    in 1.8s

2021-10-01 03:53:19 (23.5 MB/s) - 'cmake-3.21.2-linux-x86_64.sh.1' saved [44382646/44382646]

+ chmod +x cmake-3.21.2-linux-x86_64.sh
+ ./cmake-3.21.2-linux-x86_64.sh --skip-license --prefix=/usr
CMake Installer Version: 3.21.2, Copyright (c) Kitware
This is a self-extracting archive.
The archive will be extracted to: /usr

Using target directory: /usr
Extracting, please wait...

Unpacking finished successfully
+ install_latest_meson
+ wget https://bootstrap.pypa.io/get-pip.py
--2021-10-01 03:53:20--  https://bootstrap.pypa.io/get-pip.py
Resolving bootstrap.pypa.io (bootstrap.pypa.io)... <IP_ADDRESS>, 2a04:4e42:24::175
Connecting to bootstrap.pypa.io (bootstrap.pypa.io)|<IP_ADDRESS>|:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 1946810 (1.9M) [text/x-python]
Saving to: 'get-pip.py.1'

get-pip.py.1                  100%[=================================================>]   1.86M  8.58MB/s    in 0.2s

2021-10-01 03:53:21 (8.58 MB/s) - 'get-pip.py.1' saved [1946810/1946810]

+ python3 get-pip.py
Collecting pip
  Using cached pip-21.2.4-py3-none-any.whl (1.6 MB)
Installing collected packages: pip
  Attempting uninstall: pip
    Found existing installation: pip 21.2.4
    Uninstalling pip-21.2.4:
      Successfully uninstalled pip-21.2.4
Successfully installed pip-21.2.4
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
+ pip3 install meson --upgrade
Requirement already satisfied: meson in /usr/local/lib/python3.7/dist-packages (0.59.2)
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
+ '[' '!' -z '' ']'
+ '[' '!' -z '' ']'
+ '[' '!' -z '' ']'
+ gcc --version
gcc (Debian 8.3.0-6) 8.3.0
Copyright (C) 2018 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.

+ '[' '!' -z '' ']'
+ source ./build.sh
++ cp -rfv assets/run-ja2.sh /packages/dist/215930/dist/
'assets/run-ja2.sh' -> '/packages/dist/215930/dist/run-ja2.sh'
+ copy_license_file 215930
+ '[' -z '' ']'
+ echo 'Warning: license file path is not set.'
Warning: license file path is not set.
+ popd
/packages
(steamrt soldier 0.20210906.1)root@47967305c220:/packages# ./common/package.sh ja2-stracciatella
++ set -e
++ export pstart=/packages
++ pstart=/packages
++ export diststart=/packages/dist
++ diststart=/packages/dist
+ pushd engines/ja2-stracciatella
/packages/engines/ja2-stracciatella /packages
+ source env.sh
++ export STEAM_APP_ID_LIST=215930
++ STEAM_APP_ID_LIST=215930
+ log_environment
+ pwd
/packages/engines/ja2-stracciatella
+ nproc
12
+ popd
/packages
+ pushd dist
/packages/dist /packages
+ '[' -z '' ']'
+ create_archives
+ '[' -z '' ']'
+ for app_id in $STEAM_APP_ID_LIST
+ filename=ja2-stracciatella-215930
+ pushd 215930
/packages/dist/215930 /packages/dist /packages
+ tar --format=v7 --mode=a+rwX,o-w --owner=0 --group=0 --mtime=@1560859200 -cf ja2-stracciatella-215930.tar dist
+ xz ja2-stracciatella-215930.tar
+ sha1sum ja2-stracciatella-215930.tar.xz
3b7272a0ae337de7c9527a49d52cd7e7339adf99  ja2-stracciatella-215930.tar.xz
+ popd
/packages/dist /packages
+ mv 215930/ja2-stracciatella-215930.tar.xz /packages/dist/ja2-stracciatella/ja2-stracciatella-215930.tar.xz
+ rm -rf 215930
+ popd
/packages%

Could not find "No Version Found" or the "Version Found" in the log by grepping. Could you please tell me what I am doing wrong?

@OBITORASU Ah I was referring to running this script locally to launch the game. The scripts you were running are what cause the build to occur but this script you are changing would run on the user's system to launch the game.

Ah gotcha, I think this is the log you were referring to:
(steamrt soldier 0.20210906.1)root@36929e377fed:/packages/engines/ja2-stracciatella/assets# ./run-ja2.sh
No Version Found
Running Setup
chmod: cannot access './ja2-stracciatella_0.18.0-git+ebc73ce_x86-64.AppImage': No such file or directory
./run-ja2.sh: line 17: ./ja2-stracciatella_0.18.0-git+ebc73ce_x86-64.AppImage: No such file or directory
./run-ja2.sh: line 20: /root/.ja2/ja2.json: No such file or directory
ln: failed to create symbolic link './Data/Tilesets': No such file or directory
tar: wildfire-maps_0.3.0-linux.tar.gz: Cannot open: No such file or directory
tar: Error is not recoverable: exiting now
./run-ja2.sh: line 25: ./squashfs-root/usr/share/ja2/mods/wildfire-maps/install_wildfire_maps: No such file or directory
./run-ja2.sh: line 32: ./squashfs-root/usr/bin/ja2-launcher: No such file or directory
(steamrt soldier 0.20210906.1)root@36929e377fed:/packages/engines/ja2-stracciatella/assets# ./run-ja2.sh
Found version: 0.18.0
Not Running Setup
./run-ja2.sh: line 32: ./squashfs-root/usr/bin/ja2-launcher: No such file or directory
(steamrt soldier 0.20210906.1)root@36929e377fed:/packages/engines/ja2-stracciatella/assets#

@OBITORASU For this one do you own this game? If not, you should be able to run this script locally and put the appimage file it's talking about in the same directory for the test. You can find where that comes from in the packagesruntime.json file.

I will setup a test vm and get back to you with the report.

@OBITORASU Looks good thanks.

I will start working on the other engines tomorrow when I get some time off to test :)


Atom 1.12.0: bad scrollbar behavior again !!

On windows, the scroll bar is still buggy in atom 1.12.0.

When I am editing a large file (nearly 4000+ lines), dragging the scrollbar to the bottom, I find the document has't reached the bottom.

When I open a large file and move the cursor to the bottom, and then click View->Panes->Split Right.
I found the scroll bar position of previous pane rewind to the top but the cursor is still on the last line.

They assume to be fixed in https://github.com/atom/atom/issues/11484, but actually not.
Prerequisites

[x] Are you running the latest version of Atom?
[x] Can you reproduce the problem in safe mode?
[x] Did you check the debugging guide?
[x] Did you check the FAQs on Discuss?
[x] Are you reporting to the correct repository?
[x] Did you perform a cursory search to see if your bug or enhancement is already reported?

For more information on how to write a good bug report or enhancement request, see the CONTRIBUTING guide.
Description
[Description of the bug or feature]
Steps to Reproduce with BUG1

Editing a large file (nearly 4000+ lines),
Dragging the scrollbar to the bottom and top repeatly,

Expected behavior: [What you expected to happen]
the document scroll to the same position.
Actual behavior: [What actually happened]
Sometimes dragging the scrollbar to the bottom, I find the document has't reached the last line.
Steps to Reproduce with BUG2

Open a large file which is almost 4000+ lines.
Move the cursor to the bottom by pressing "CTRL-END"
Click View->Panes->Split Right.

Expected behavior: [What you expected to happen]
scroll bar position should no change
Actual behavior: [What actually happened]
I found the scroll bar position of previous pane rewind to the top but the cursor is still on the last line.
Versions
Atom    : 1.12.0
Electron: 1.3.6
Chrome  : 52.0.2743.82
Node    : 6.3.0
BUG1:

BUG2:

https://github.com/atom/atom/issues/11484 has been closed
they are supposed to fixed in 1.12.0, but actually it wasn't or maybe new bug comes out

@skywind3000 I understand that you are upset with the apparent quality of Atom. However, posting repetitive comments across so many separate Issues is harassment under our Code of Conduct. This is an official warning. If you continue, you will be banned from participation in the Atom and Electron projects.
Additionally, comments like the following:

I wonder do you have a QA Team ?

are insulting, which is also a violation of the Code of Conduct.
We want to work with you on these things. We closed #11484 because we could no longer reproduce the problem. There are some bugs that only reproduce on certain configurations or in certain instances. No team can find all bugs in a software product, some bugs will have to be reported by people outside of our team. If people run into bugs and don't tell us about them, then we don't know about them and can't fix them.
We're going to take a look at this and see if we can reproduce it. Please report any other bugs you find with as much information as you can. Please also do so in a respectful and cooperative manner.

Apologize for my inappropriate words.
All I want is atom becomes better.

Hey, this is a different bug than the one you referenced. I can reproduce this on Atom 1.14.0-dev-9c73ae0 Electron 1.4 branch, Windows 10 anniversary x64.
This is with an 84 line file and one-dark-ui. So it doesn't require large files and is not limited to atom-light-ui.

Start Atom using atom --safe from cmd.exe
Open any file and resize the Atom window so you have a vertical scrollbar visible
Scroll to the middle of an opened file
Run pane:split-right-and-copy-active-item
Expected: The scrollbars to stay in the same position for both files. Actual: The scrollbars in both files moves to the top of the file
Close the right pane
Expected: The scrollbar position of the first file to not change. Actual: The scrollbar in the first file is displayed at the top of the file.

Apologize for my inappropriate words.
All I want is atom becomes better.

We want Atom to become better too. Thanks for helping us find this bug so we can fix it! 👍

What about the first bug ? Is it possible that it is caused by a float point calculation error ?

@skywind3000 I can't reproduce Bug 1 using Atom v1.12.4 on Mac OS X 10.12.1. Additionally, you should report only one bug per Issue. If you can supply more detailed steps to reproduce the problem, please open a new Issue. I'll be editing this bug to only track the pane splitting bug that @Ben3eeE confirmed.

I can't reproduce it on Mac OS X either, It's only on windows.

Please include that information when you open the new Issue.


ENH: implicit args in blackscholes

Currently, BlackScholes modules work like:
from pfhedge.instruments import BrownianStock
from pfhedge.instruments import EuropeanOption
from pfhedge.nn import BlackScholes

derivative = EuropeanOption(BrownianStock())
pricer = lambda derivative: BlackScholes(derivative).price(
             log_moneyness=derivative.log_moneyness(),
             time_to_maturity=derivative.time_to_maturity(),
             volatility=derivative.ul().volatility)
derivative = EuropeanOption(BrownianStock(), maturity=5/250)
derivative.list(pricer, cost=1e-4)
derivative.simulate(n_paths=2)
derivative.spot

However, the part,
pricer = lambda derivative: BlackScholes(derivative).price(
             log_moneyness=derivative.log_moneyness(),
             time_to_maturity=derivative.time_to_maturity(),
             volatility=derivative.ul().volatility)

seems a little bit redundant and not universal.
I think it comes from the following reasons:

it is obvious that each args are generated from derivatives.
required args (and the number of required args) depend on underliers

Thus, I suggest that all args are not required, and if the args are missing, these required args are calculated automatically based on registered derivatives.
Of course, in the case of derivative using autogreeks, these implicit args cannot be applied, but, I think my suggestion is worth being considere.
This suggestion is not limited to BlackScholes.price, but also to all other methods in greeks methods.

Note that the current best workaround for the universality problem is
pricer = lambda derivative: BlackScholes(derivative).price(
             *[get_feature(f).of(derivative=derivative) for f in BlackScholes(derivative).inputs()])

Sounds great 👍
Maybe I will make that enhancement when I find the time, while it is more than welcome if you kindly send a patch.
If you want to implement this let me know to prevent duplicate work.
One way is to register default arguments as attributes of a module in init and pass them in function calls as:
    def __init__(self, ..., log_moneyness=None):
        self.log_moneyness = log_moneyness

    def price(self, log_moneyness=None, ...):
        log_moneyness = self.log_moneyness or log_moneyness
        ...

I know it is not high priority problem for you and me. So, I wrote this as just a note.
I'll let you know here before I do this implementation.

I'll make a prototype

I made a prototype for this: #516
Currently, this is only implemented for European option.
If it looks good for you (@simaki ), I'll implement to the others.

Resolved by #516


App will sometimes crash near startup

The Issue
I think it's being caused when the background process is loading as I haven't experienced a crash after that has finished.
Error:
2020-12-12 20:23:20.628 24040-24190/io.lbry.browser E/AndroidRuntime: FATAL EXCEPTION: AsyncTask #3
    Process: io.lbry.browser, PID: 24040
    java.lang.RuntimeException: An error occurred while executing doInBackground()
        at android.os.AsyncTask$3.done(AsyncTask.java:353)
        at java.util.concurrent.FutureTask.finishCompletion(FutureTask.java:383)
        at java.util.concurrent.FutureTask.setException(FutureTask.java:252)
        at java.util.concurrent.FutureTask.run(FutureTask.java:271)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
        at java.lang.Thread.run(Thread.java:764)
     Caused by: java.lang.NullPointerException: Attempt to invoke virtual method 'int org.json.JSONArray.length()' on a null object reference
        at io.lbry.browser.tasks.wallet.LoadSharedUserStateTask.isNotificationsDisabledForSubUrl(LoadSharedUserStateTask.java:134)
        at io.lbry.browser.tasks.wallet.LoadSharedUserStateTask.doInBackground(LoadSharedUserStateTask.java:85)
        at io.lbry.browser.tasks.wallet.LoadSharedUserStateTask.doInBackground(LoadSharedUserStateTask.java:36)
        at android.os.AsyncTask$2.call(AsyncTask.java:333)
        at java.util.concurrent.FutureTask.run(FutureTask.java:266)
        at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1162)
        at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:636)
        at java.lang.Thread.run(Thread.java:764)

Steps to reproduce

Pull from the latest on master 0647deb06cb3bc3e8a87dfa6453efa6dc4411c58
Set up development environment
Build/run/install app
Wait for background task to load and it may crash during that time

Expected behaviour
Should not crash
Actual behaviour
Crashed
System Configuration

Device: Samsung Galaxy S7
Android version: 8.1

Some more testing, seems to not crash until I try to do anything on the app after wallet and stuff loads. Background process itself doesn't crash but the interface does.

Fixed in 0.16.11 which is now live.


Add data handling code with get none when get timeseries data

…#45)
Category

[ ] New feature
[ ] Bug fix
[x] Improvement
[ ] Refactor
[ ] etc

Description

Add data handling code with get none when get timeseries data

Known issue

#45

There is some case when data is 'None'


add issue and pullrequest templates based on xarray's

As suggested in #96, this adds issue and pullrequest templates (based on xarray's).

@shoyer I'm going to merge this in a few days. Feel free to merge as is, if it's looking good to you.


Cannot resolve module fs in

I get this error as soon as I try to import AsynchNewStorage:
How do I fix this?
ERROR in ./~/node-localstorage/LocalStorage.js
Module not found: Error: Cannot resolve module 'fs' in /home/simran/Desktop/frontend/node_modules/node-localstorage
 @ ./~/node-localstorage/LocalStorage.js 9:7-20
ERROR in ./~/graceful-fs/graceful-fs.js
Module not found: Error: Cannot resolve module 'fs' in /home/simran/Desktop/frontend/node_modules/graceful-fs
 @ ./~/graceful-fs/graceful-fs.js 1:9-22
ERROR in ./~/graceful-fs/fs.js
Module not found: Error: Cannot resolve module 'fs' in /home/simran/Desktop/frontend/node_modules/graceful-fs
 @ ./~/graceful-fs/fs.js 3:9-22

that looks like you are running webpack - is your project running in the browser or in node?

@rt2zz : I am using ssr with react so node for the initial render

Yeah, that's right. I am running webpack

Could you potentially post some more code? I can't manage to reproduce your issue now.

Let me know if you're still dealing with this issue, then we'll reopen it.


Created the functions with delay option for the UITextView+Emojis extensions

Transferring: https://github.com/GetStream/Streamoji/pull/6
Author: @mehmetdelikaya

Hi @cardoso,
Thanks for the merge. Is Swiftmoji the one will be maintained as I see the other repo is archived?


Move line up/down causes indentation to break

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.90.0
OS Version: Windows 10 Home 22H2 build 19045.4412 (+ WSL2 inside Win10)

Steps to Reproduce:
(similar to this issue: https://github.com/microsoft/vscode/issues/78788)

Sample code:

<?php
if (true) {
    $a = 1;
}
$lineTo = 'move';

Set cursor at line 5 and perform editor.action.moveLinesUp 3 times.
The moved line is misplaced:

<?php
    $lineTo = 'move';
if (true) {
    $a = 1;
}

In a vscode window opened in WSL this also happens:
1-WSL. Sample code:
<?php
$lineTo = 'move';
if (true) {
    $a = 1;
}

2-WSL. Set cursor at line 2 and perform editor.action.moveLinesDown 3 times.
3-WSL. The last bracked is misplaced:
<?php
if (true) {
    $a = 1;
    }
$lineTo = 'move';

should be fixed by https://github.com/microsoft/vscode/pull/214577


deps: bump to golang 1.20 and latest deps

This bumps the repository up to go 1.20. This requires bumping golangci-lint to a compatible version. The new version of golangci-lint requires dep guard config changes as well.
Took the opportunity to upgrade the other deps and their transitive deps, this will quiet down dependabot yelling in other repositories about github.com/cloudflare/circl not being updated to latest version.
Ex. https://github.com/datawire/apro/security/dependabot/134

I'm not sure of the release process or our API guarantees for this project but figured it would be good to get its deps updated to make sure we are not lagging behind.


Update dependencies

This updates all of Earl Grey's dependencies to the latest versions.
The only one requiring significant changes was Babel, since it has a new API.
Bootstrapping is successful, and all tests pass under both lib5 and lib6. Quaint's tests also pass.
The bootstrap files have been regenerated as well.

Thanks! You're more diligent than I am.


Swarm multiple dat's together

Dat server tools like: https://github.com/beakerbrowser/homebase and https://github.com/new-computers/seeder are a great use case for managing multiple dat-node instances in a single swarm. I imagine we could have an API like:
var swarm = Dat.createSwarm([opts])
Dat('/dir', function (err, dat) {
  var network = dat.joinNetwork(swarm)

  network.on('connection', () => {
     // TODO: how would we handle something like this?
     // want to make it easy to track only network things on this dat.
  })
})

That API design seems right. For the connection events, there's some code you can steal from beaker.
Most/all of the events needed have a peer object with the .channel attribute, which should be the dkey. I don't recall if that will give you coverage of feeds being synced in addition to the main feed of the connection, but it will at least give you the main one. If not, we can listen to stream.on('feed') and attach the additional feeds to the events.
You also have to deal with the truncated dkeys, but that'll be a temporary kludge since we're moving away from the bittorrent dht.

Seems to me like you might reverse the join swarm call, so that the swarm is the first class object. Otherwise you could have a couple swarm objects hanging around and it's unclear which swarm is which (or is it the same swarm?)
var swarm = Dat.createSwarm([opts])
Dat('/dir', function (err, dat) {
   swarm.join(dat)
})

So it would take extending the swarm.join function to accept also a dat object

hyperswarm does this automatically with the multiplex: true option


TextEngine using width and height before updating

TextField.__updateLayout calls TextEngine.update, which updates textWidth and textHeight, and use width and height to update scroll values, i.e.
Then TextField.__updateLayout use textWidth and textHeight to set width and height for autosize.
So values used for TextEngine.update is incorrect, and for simple one-line TextFields with autosize no text is shown (bottomScrollV remains 0, less that scrollV)
Possible workaround is to call __updateLayout twice:
	__layoutDirty = true;
	__updateLayout();
	__layoutDirty = true;
	__updateLayout()

Possible proper solution is to update textWidth/textHeight, then update width/height, then update scroll

Are you using autoSize when the text is smaller than the original width, or larger?
I think that if the text was smaller than the field width, the layout will not change. When wordWrap is true the width is not resized, so autoSize is really trimming the width and height values, and should not be changing the scrollV at all (though I suppose scrollH could be affected?)
Though I suppose if it is expanding the width, that's another issue. Do you have a small sample of code I could use to see what you're seeing?

It's expanding:
		var tf = new flash.text.TextField();
		trace(tf.height, tf.textHeight, tf.scrollV, tf.bottomScrollV);
		// flash: 100, 0, 1, 1
		// html5: 100, 0, 1, null
		tf.autoSize = flash.text.TextFieldAutoSize.CENTER;
		trace(tf.height, tf.textHeight, tf.scrollV, tf.bottomScrollV);
		// flash: 4, 0, 1, 1
		// html5: 4, 0, 1, null
		tf.text = "text";
		trace(tf.height, tf.textHeight, tf.scrollV, tf.bottomScrollV);
		// flash: 18, 14, 1, 1
		// html5: 18.22, 14.219999999999999, 1, 0

		untyped tf.__layoutDirty = true;
		untyped tf.__updateLayout();
		trace(tf.height, tf.textHeight, tf.scrollV, tf.bottomScrollV);
		// html5: 18.22,14.219999999999999,1,2

Notice that after setting text bottomScrollV is 0, which cause CanvasTextField.render to break on line 214: if (group.lineIndex > textField.scrollV + textEngine.bottomScrollV - 2) break; and not render any text at all.
But after second layout update bottomScrollV it's not breaking and rendering that line.

It looks like bottomScrollV has been fixed already. I'm testing now, and it looks consistent with Flash here. Please let me know if you see more issues, thanks! :smile:


Lohkdesgds lsw5 future test

im closing these as i needed to manually reimplement stuff on top of it from master. opened in error.


Updating default.tensor.tf

This PR brings the default.tensor.tf in line with recent upgrades to the parent devicedefaul.tensor.
To do:

[ ] Update default.tensor.tf to get test_default_tensor_tf.py tests passing
[x] Move core implementation of operations and expectations into separate tf_ops.py file
[x] Update default.tensor.tf to take into account new features of default.tensor
[x] Update any relevant docstrings

Nice to haves:

[ ] Make sure default.tensor.tf can pass all the tests in test_default_tensor.py?

Notes:
TensorFlow v2.1+ is needed in order to support gradients of complex-valued svd (needed for mps representation). We will have to determine if there are issues along the lines of those mentioned here: https://github.com/tensorflow/tensorflow/issues/37307

@josh146 I managed to port everything over and get all existing tests to pass, except for one: test_jacobian_agrees now fails when using the "finite-diff" grad method. I am unable to figure out why this test fails when it passed before

A couple of notes on the test failures:

On Python 3.5, it looks like TensorNetwork is not supported. Although, I had a feeling that we took this into account?

Could the failing jacobian test be because of the einsum issue? That's the only thing that makes sense to me, since the result of the simulator is correct, just not the Jacobian. My guess could be that the upgrades to default.tensor are resulting in tensornetwork using einsum behind the scenese where it previously wasn't?
Although, correct me if I'm wrong, but if that was the case, I would expect the exact test to pass, but the mps test to fail?

* Could the failing jacobian test be because of the einsum issue? That's the only thing that makes sense to me, since the result of the simulator is correct, just not the Jacobian. My guess could be that the upgrades to `default.tensor` are resulting in `tensornetwork` using `einsum` behind the scenese where it previously wasn't?
  Although, correct me if I'm wrong, but if that was the case, I would expect the `exact` test to pass, but the `mps` test to fail?

I believe I saw this test failing even with TF2.0

Fixed failing tests. Was due to that test comparing outputs between default.tensor.tf and default.qubit, but the two default step-sizes for finite-difference were not the same


Gitlab-CI integration example

Need sample Gitlab-CI pipeline with some screenshots and guidance.

Hi @abdelrahmanbadr
https://gitlab.com/prabhu3/NodeGoat/-/blob/master/.gitlab-ci.yml
sast:
  stage: test
  image:
    name: appthreat/sast-scan
  script:
    - scan --src ${CI_PROJECT_DIR} --type nodejs --out_dir ${CI_PROJECT_DIR}/reports
  artifacts:
    paths:
      - $CI_PROJECT_DIR/reports/

@prabhu Thank you so much for your quick response


Error in docs

const { monorepoRoot, monorepoRootSync } = require('@node-kit/monorepo-root');

doesn't work but
const { monorepoRoot, monorepoRootSync } = require('monorepo-root');

does.

Thank you very much
Documentation errors have been fixed
Have a nice day


How to specify a bucket at install time?

In the case where two buckets provide the same package (by name), how can I specify which one I'd like to get the package from?
To elaborate, on Gentoo, I'd have masks and I would typically mask everything not in the main source, and unmask from specific overlays as and when I want stuff, so that if repo A and B both provided package foo, I could mask A's and unmask B's so that emerge foo would get foo::A (and I think I could also specify the source like that, though I've never tried, ie emerge foo::A)
I ask because the aimp package from extras is broken (fails to d/l since the link it has 302's, which it apparently doesn't follow). I'm ok with that, and want to learn how to write my own scoop sources, so I tried adding an aimp manifest to a personal repo, which showed up in a scoop search aimp, but I couldn't see a way (via cli help or documentation) to specify that I wanted my aimp, so scoop install aimp tries the b0rked manifest, not mine.
For now, I've renamed mine to aimp-portable, but I'm sure this is a common enough scenario (or will become so) that there's probably a solution I'm just missing.

Fixed in https://github.com/ScoopInstaller/Main/blob/master/bucket/gh.json

Thanks! Appreciated.


Unexpected behavior from Discovery

With the Omni Simulator running on my dev machine, discovery.search_ipv4() returns one server with an address of <IP_ADDRESS>:32323, as expected.
Now if I start ASCOM Remote, hosting the COM Telescope Simulator on the same PC, in addition to the Omni simulator. I still get a single server response from search_ipv4(). This response is <IP_ADDRESS>:11111, which is correct for ASCOM Remote.
I expected to see both <IP_ADDRESS>:32323 and <IP_ADDRESS>:11111 in the servers list from the search_ipv4 call when both the Omni Simulator and ASCOM Remote are active and serving drivers.

Thanks for this, and in particular for the detailed repro scenario. I'll look at this ASAP this week.

Fixed. Needed to do multicast to <IP_ADDRESS> specifically (<IP_ADDRESS>). Tested on Windows and Linux. Thanks again for the good catch.