YAxis size calculations

I've noticed that the current master branch resizes the y axis when the axis labels change, for instance during scrolling.
That means, that when you manipulate the current x axis range, it can happen that the max width of the y labels change, resulting in a resize of the chart drawing panel.
Can be disable this feature and go back to truncating the y axis labels instead?
I couldn't find a property for that.

It was actually never truncated - just did not calculate when scrolling... This has changed many commits ago!
You can set a fixed width for the Y axis to disable the constant updates

Oh I see.
Didn't keep up the changes lately as I had to implement the Android version of the chart.
Ok then, fixed size it is. Thanks for your help, Daniel!

NP :-)

@danielgindi, is there a way to actually truncate the y-axis labels? Turns out that constantly re-adjusting my synchronised chart viewports (I've got several charts stacked vertically that need to have the same y-axis width), looks kinda wrong during manipulation of the chart's viewport. Instead, setting the y-axes widths to the maximum size after the initial draw and then leave it that way looks way better.
However, in order to not have the y-axis labels reach into the chart's viewport, I need them to be truncated.
This should be doable in the ChartYAxisRenderer (if _yAxis.maxWidth > 0...), and using a lineBreakMode, right?
This is probably a feature many require, so I'd like to give this a go in the foreseeable future.

Well I'm planning to do some work on the Y axis labels anyway, to support
wrapping, line break mode etc.
בתאריך יום שישי, 16 באוקטובר 2015, AlBirdie<EMAIL_ADDRESS>כתב:

@danielgindi https://github.com/danielgindi, is there a way to actually
truncate the y-axis labels? Turns out that constantly re-adjusting my
synchronised chart viewports (I've got several charts stacked vertically
that need to have the same y-axis width), looks kinda wrong during
manipulation of the chart's viewport. Instead, setting the y-axes widths to
the maximum size after the initial draw and then leave it that way looks
way better.
However, in order to not have the y-axis labels reach into the chart's
viewport, I need them to be truncated.
This should be doable in the ChartYAxisRenderer (if _yAxis.maxWidth >
0...), and using a lineBreakMode, right?
This is probably a feature many require, so I'd like to give this a go in
the foreseeable future.
—
Reply to this email directly or view it on GitHub
https://github.com/danielgindi/ios-charts/issues/480#issuecomment-148644153
.

Ok then. I'll leave it to you then. :)
Cheers mate!


Is there any way to schedule notifications on monthly based?

Really need this feature.  let know if any way to do...

@meypod Thanks for your valuable reply.
Even I thought the same if a notification gets fired then I can schedule new one from previous one but the problem here is like if user's phone is switched off in that case the notification will not get triggered and no way to schedule next notification.

from what I know that scheduled notifications are rescheduled if the app has permissions to auto start after reboot (this should be how notifee works)
But, I think you are right, as app can't reschedule in the past, the notification will be gone and never triggered (I suggest testing though)
but I saw that there's a TODO in the source code of notifee for this:
https://github.com/invertase/notifee/blob/235c3dca8198c570ac6a9b6ad081b2c43bf9b4cd/android/src/main/java/app/notifee/core/NotifeeAlarmManager.java#L233
so maybe this will be possible in a future release @helenaford ?

case "daily":
calendar.set(Calendar.HOUR_OF_DAY, notification.getInt("hour"));
calendar.set(Calendar.MINUTE, notification.getInt("minute"));
calendar.set(Calendar.SECOND, 0);
alarmManager.setRepeating(AlarmManager.RTC_WAKEUP, calendar.getTimeInMillis(), AlarmManager.INTERVAL_DAY, pendingIntent);
case "weekly":
calendar.set(Calendar.DAY_OF_WEEK, notification.getInt("weekday"));
calendar.set(Calendar.HOUR_OF_DAY, notification.getInt("hour"));
calendar.set(Calendar.MINUTE, notification.getInt("minute"));
calendar.set(Calendar.SECOND, 0);
alarmManager.setRepeating(AlarmManager.RTC_WAKEUP, calendar.getTimeInMillis(), AlarmManager.INTERVAL_DAY * 7, pendingIntent);
case "yearly":
calendar.set(Calendar.MONTH, notification.getInt("month"));
calendar.set(Calendar.DAY_OF_MONTH, notification.getInt("day"));
calendar.set(Calendar.HOUR_OF_DAY, notification.getInt("hour"));
calendar.set(Calendar.MINUTE, notification.getInt("minute"));
calendar.set(Calendar.SECOND, 0);
calendar.set(Calendar.YEAR,Calendar.getInstance().get(Calendar.YEAR));
alarmManager.setRepeating(AlarmManager.RTC_WAKEUP, calendar.getTimeInMillis(), AlarmManager.INTERVAL_DAY * 365, pendingIntent);
break;
case "every_n_days":
calendar.set(Calendar.HOUR_OF_DAY, notification.getInt("hour"));
calendar.set(Calendar.MINUTE, notification.getInt("minute"));
calendar.set(Calendar.SECOND, 0);
int n = notification.getInt("n");
alarmManager.setRepeating(AlarmManager.RTC_WAKEUP, calendar.getTimeInMillis(), AlarmManager.INTERVAL_DAY * n, pendingIntent);
break;
case "weekdays":
calendar.set(Calendar.DAY_OF_WEEK,Calendar.MONDAY);
calendar.set(Calendar.HOUR_OF_DAY, 8);
calendar.set(Calendar.MINUTE, 0);
calendar.set(Calendar.SECOND, 0);
alarmManager.setRepeating(AlarmManager.RTC_WAKEUP, calendar.getTimeInMillis(), AlarmManager.INTERVAL_DAY * 7, pendingIntent);
calendar.set(Calendar.DAY_OF_WEEK,Calendar.FRIDAY);
alarmManager.setRepeating(AlarmManager.RTC_WAKEUP, calendar.getTimeInMillis(), AlarmManager.INTERVAL_DAY * 7, pendingIntent);
break;
  I got above response from ChatGPT. @meypod @helenaford  Do you think above things can be integrated?

lol
Scary
Plus I have no idea

Ah yes, will mark this as an enhancement to be able to do interval notifications with alarm manager. But in terms of that chatGPT code, not sure!

any update


It is better to add the helpful error details in the activity log if running upload with invalid characters were filled in the 'Destination directory' field

Storage Explorer Version: 1.26.0-dev
Build Number: 20221012.4
Branch: main
Platform/OS: Windows 10/Linux Ubuntu 22.04/MacOS Monterey 12.6 (Apple M1 Pro)
Architecture: ia32/x64
How Found: AD-hoc testing
Regression From: Not a regression
Steps to Reproduce

Expand one storage account -> File Share.
Create a file share -> Click 'Upload -> Upload Files...'.
Select one file -> Type '?' to the Destination directory field.
Click 'Upload' -> There is a failed activity log.
Check whether we can directly get the error details from the activity log.

Expected Experience
We can directly get the error details from the activity log.
Actual Experience
Can't get the error details from the activity log.

Additional Context

It would be better to remove the 'Retry...' next to the activity log. Here is the screenshot when clicking 'Retry...':

This issue also reproduces when typing " \ / : | < > * ? to the Destination directory field.
Below is the screenshot when creating a new folder under one file share:

There isn't much we can do in the activity log since the error details aren't exposed to us (they are in the logs). However, we should be able to tighten the validation logic in the upload dialog to prevent people from entering invalid paths for the destination directory.

Verified this issue on the build main 20230127.10. Fixed. So, we are going to close it.


⚠ Bofrost.at has degraded performance

In 843f654, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2459 ms

Resolved: Bofrost.at performance has improved in f43b816 after 309 days, 10 hours, 35 minutes.


Only create an instance of Progress once

This is the strand I was originally pulling on in #3095.
We have a test somewhere that creates an instance of Progress, then asserts the created and modified dates are the same. Which is fine… until Instant.now is called over a millisecond boundary, and the test fails. Really hard to hit, but caused me a flaky failure on master. So this fixes that.

Closing due to inactivity.


Clarify 'MsgFailedToParseGenesis' with regards to which genesis file is expected.

Issue Number

#2296
Overview

21da8b6c0ce6e24648c0b32e2150de77a2a7705e
:round_pushpin: clarify 'MsgFailedToParseGenesis' with regards to which genesis file is expected
We wrote that message a while ago when there was only Byron and therefore a single genesis file. With Shelley (and later Goguen), there's now an ambiguity when speaking about 'a genesis file' so it is better called out explicitly.

Comments

bors merge


postgres - Out of Memory on Initialize

We're adding postgres monitoring to an exiting datadog agent and seeing an "Out of Memory" exception when trying to connect. We specifically get the error when the postgres agent checker tries to connect to our AWS RDS Postgres instance. I would appreciate any help troubleshooting this issue.
Output of the info page
===============
Agent (v7.49.0)
===============

  Status date: 2023-11-07 22:10:07.599 UTC<PHONE_NUMBER>599)
  Agent start: 2023-11-07 20:23:23.814 UTC<PHONE_NUMBER>814)
  Pid: 1
  Go Version: go1.20.10
  Python Version: 3.9.18
  Build arch: amd64
  Agent flavor: agent
  Check Runners: 4
  Log Level: info

  Paths
  =====
    Config File: /etc/datadog-agent/datadog.yaml
    conf.d: /etc/datadog-agent/conf.d
    checks.d: /etc/datadog-agent/checks.d

  Clocks
  ======
    NTP offset: 31µs
    System time: 2023-11-07 22:10:07.599 UTC<PHONE_NUMBER>599)

  Host Info
  =========
    bootTime: 2023-08-23 14:48:37 UTC<PHONE_NUMBER>000)
    hostId: ec2914bc-3c53-8c30-8208-c271a3a2d78a
    kernelArch: x86_64
    kernelVersion: 5.10.184-175.731.amzn2.x86_64
    os: linux
    platform: ubuntu
    platformFamily: debian
    platformVersion: 23.04
    procs: 151
    uptime: 1829h34m49s

  Hostnames
  =========
    cluster-name: dev-company
    ec2-hostname: ip-10-0-2-28.us-east-2.compute.internal
    host_aliases: [i-0b3db96a4153207be ip-10-0-2-28.us-east-2.compute.internal-dev-company]
    hostname: i-0b3db96a4153207be
    instance-id: i-0b3db96a4153207be
    socket-fqdn: datadog-agent-7x4bs
    socket-hostname: datadog-agent-7x4bs
    host tags:
      cluster_name:dev-company
      kube_cluster_name:dev-company
      kube_node:ip-10-0-2-28.us-east-2.compute.internal
    hostname provider: aws
    unused hostname providers:
      'hostname' configuration/environment: hostname is empty
      'hostname_file' configuration/environment: 'hostname_file' configuration is not enabled
      azure: azure_hostname_style is set to 'os'
      fargate: agent is not runnning on Fargate
      fqdn: FQDN hostname is not usable
      gce: unable to retrieve hostname from GCE: GCE metadata API error: status code 401 trying to GET http://<IP_ADDRESS>/computeMetadata/v1/instance/hostname
      os: OS hostname is not usable

  Metadata
  ========
    agent_version: 7.49.0
    cloud_provider: AWS
    config_apm_dd_url:
    config_dd_url:
    config_logs_dd_url:
    config_logs_socks5_proxy_address:
    config_no_proxy: [<IP_ADDRESS> <IP_ADDRESS>]
    config_process_dd_url:
    config_proxy_http:
    config_proxy_https:
    config_site:
    feature_apm_enabled: true
    feature_cspm_enabled: false
    feature_cws_enabled: false
    feature_cws_network_enabled: true
    feature_cws_remote_config_enabled: true
    feature_cws_security_profiles_enabled: false
    feature_dynamic_instrumentation_enabled: false
    feature_fips_enabled: false
    feature_imdsv2_enabled: true
    feature_logs_enabled: true
    feature_networks_enabled: false
    feature_networks_http_enabled: false
    feature_networks_https_enabled: false
    feature_oom_kill_enabled: false
    feature_otlp_enabled: false
    feature_process_enabled: false
    feature_process_language_detection_enabled: false
    feature_processes_container_enabled: true
    feature_remote_configuration_enabled: true
    feature_tcp_queue_length_enabled: false
    feature_usm_enabled: false
    feature_usm_go_tls_enabled: false
    feature_usm_http2_enabled: false
    feature_usm_http_by_status_code_enabled: false
    feature_usm_istio_enabled: false
    feature_usm_java_tls_enabled: false
    feature_usm_kafka_enabled: false
    feature_windows_crash_detection_enabled: false
    flavor: agent
    hostname_source: aws
    install_method_installer_version: v1.2.0
    install_method_tool: datadog-operator
    install_method_tool_version: datadog-operator
    logs_transport: HTTP
    system_probe_core_enabled: true
    system_probe_gateway_lookup_enabled: true
    system_probe_kernel_headers_download_enabled: false
    system_probe_max_connections_per_message: 600
    system_probe_prebuilt_fallback_enabled: true
    system_probe_protocol_classification_enabled: true
    system_probe_root_namespace_enabled: true
    system_probe_runtime_compilation_enabled: false
    system_probe_telemetry_enabled: true
    system_probe_track_tcp_4_connections: true
    system_probe_track_tcp_6_connections: true
    system_probe_track_udp_4_connections: true
    system_probe_track_udp_6_connections: true

=========
Collector
=========

  Running Checks
  ==============

    cert_manager (3.1.1)
    --------------------
      Instance ID: cert_manager:2b1f188aabed9bba [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/cert_manager.d/auto_conf.yaml
      Total Runs: 427
      Metric Samples: Last Run: 2, Total: 854
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 1, Total: 427
      Average Execution Time : 3ms
      Last Execution Date : 2023-11-07 22:09:56 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-11-07 22:09:56 UTC<PHONE_NUMBER>000)

    container
    ---------
      Instance ID: container [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/container.d/conf.yaml.default
      Total Runs: 426
      Metric Samples: Last Run: 760, Total: 323,760
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 14ms
      Last Execution Date : 2023-11-07 22:09:55 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-11-07 22:09:55 UTC<PHONE_NUMBER>000)

    containerd
    ----------
      Instance ID: containerd [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/containerd.d/conf.yaml.default
      Total Runs: 427
      Metric Samples: Last Run: 150, Total: 64,050
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 156ms
      Last Execution Date : 2023-11-07 22:10:02 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-11-07 22:10:02 UTC<PHONE_NUMBER>000)

    coredns (3.0.0)
    ---------------
      Instance ID: coredns:9089a795cd6c958f [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/coredns.d/auto_conf.yaml
      Total Runs: 427
      Metric Samples: Last Run: 161, Total: 68,747
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 1, Total: 427
      Average Execution Time : 15ms
      Last Execution Date : 2023-11-07 22:10:03 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-11-07 22:10:03 UTC<PHONE_NUMBER>000)

    cpu
    ---
      Instance ID: cpu [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/cpu.d/conf.yaml.default
      Total Runs: 426
      Metric Samples: Last Run: 9, Total: 3,827
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2023-11-07 22:09:54 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-11-07 22:09:54 UTC<PHONE_NUMBER>000)

    cri
    ---
      Instance ID: cri [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/cri.d/conf.yaml.default
      Total Runs: 427
      Metric Samples: Last Run: 0, Total: 0
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 13ms
      Last Execution Date : 2023-11-07 22:10:01 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-11-07 22:10:01 UTC<PHONE_NUMBER>000)

    disk (5.0.0)
    ------------
      Instance ID: disk:67cc0574430a16ba [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/disk.d/conf.yaml.default
      Total Runs: 426
      Metric Samples: Last Run: 902, Total: 384,252
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 47ms
      Last Execution Date : 2023-11-07 22:09:53 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-11-07 22:09:53 UTC<PHONE_NUMBER>000)

    file_handle
    -----------
      Instance ID: file_handle [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/file_handle.d/conf.yaml.default
      Total Runs: 427
      Metric Samples: Last Run: 5, Total: 2,135
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2023-11-07 22:10:00 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-11-07 22:10:00 UTC<PHONE_NUMBER>000)

    io
    --
      Instance ID: io [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/io.d/conf.yaml.default
      Total Runs: 427
      Metric Samples: Last Run: 41, Total: 17,480
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2023-11-07 22:10:07 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-11-07 22:10:07 UTC<PHONE_NUMBER>000)

    kubelet (7.9.2)
    ---------------
      Instance ID: kubelet:2b9bec749170d31d [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/kubelet.d/conf.yaml.default
      Total Runs: 321
      Metric Samples: Last Run: 1,083, Total: 347,607
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 5, Total: 1,604
      Average Execution Time : 287ms
      Last Execution Date : 2023-11-07 22:10:06 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-11-07 22:10:06 UTC<PHONE_NUMBER>000)

    kubernetes_apiserver
    --------------------
      Instance ID: kubernetes_apiserver [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/kubernetes_apiserver.d/conf.yaml.default
      Total Runs: 427
      Metric Samples: Last Run: 0, Total: 0
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2023-11-07 22:09:59 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-11-07 22:09:59 UTC<PHONE_NUMBER>000)

    load
    ----
      Instance ID: load [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/load.d/conf.yaml.default
      Total Runs: 427
      Metric Samples: Last Run: 6, Total: 2,562
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2023-11-07 22:10:06 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-11-07 22:10:06 UTC<PHONE_NUMBER>000)

    memory
    ------
      Instance ID: memory [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/memory.d/conf.yaml.default
      Total Runs: 427
      Metric Samples: Last Run: 20, Total: 8,540
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2023-11-07 22:09:58 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-11-07 22:09:58 UTC<PHONE_NUMBER>000)

    network (3.0.0)
    ---------------
      Instance ID: network:4b0649b7e11f0772 [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/network.d/conf.yaml.default
      Total Runs: 427
      Metric Samples: Last Run: 214, Total: 91,378
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 3ms
      Last Execution Date : 2023-11-07 22:10:05 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-11-07 22:10:05 UTC<PHONE_NUMBER>000)

    ntp
    ---
      Instance ID: ntp:3c427a42a70bbf8 [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/ntp.d/conf.yaml.default
      Total Runs: 8
      Metric Samples: Last Run: 1, Total: 8
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 1, Total: 8
      Average Execution Time : 0s
      Last Execution Date : 2023-11-07 22:08:26 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-11-07 22:08:26 UTC<PHONE_NUMBER>000)

    postgres (15.1.1)
    -----------------
      Instance ID: postgres:941660ed43814218 [ERROR]
      Configuration Source: kube_services:kube_service://my-system/postgres
      Total Runs: 312
      Metric Samples: Last Run: 0, Total: 0
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 66ms
      Last Execution Date : 2023-11-07 22:10:04 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : Never
      metadata:
        resolved_hostname: devdb-postgres.redacted.us-east-2.rds.amazonaws.com
      Error: out of memory

      Traceback (most recent call last):
        File "/opt/datadog-agent/embedded/lib/python3.9/site-packages/datadog_checks/base/checks/base.py", line 1210, in run
          initialization()
        File "/opt/datadog-agent/embedded/lib/python3.9/site-packages/datadog_checks/postgres/postgres.py", line 714, in _connect
          with self.db():
        File "/opt/datadog-agent/embedded/lib/python3.9/contextlib.py", line 119, in __enter__
          return next(self.gen)
        File "/opt/datadog-agent/embedded/lib/python3.9/site-packages/datadog_checks/postgres/postgres.py", line 197, in db
          self._db = self._new_connection(self._config.dbname)
        File "/opt/datadog-agent/embedded/lib/python3.9/site-packages/datadog_checks/postgres/postgres.py", line 703, in _new_connection
          conn = psycopg2.connect(**args)
        File "/opt/datadog-agent/embedded/lib/python3.9/site-packages/psycopg2/__init__.py", line 127, in connect
          conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
      psycopg2.OperationalError: out of memory

    uptime
    ------
      Instance ID: uptime [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/uptime.d/conf.yaml.default
      Total Runs: 427
      Metric Samples: Last Run: 1, Total: 427
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2023-11-07 22:09:57 UTC<PHONE_NUMBER>000)
      Last Successful Execution Date : 2023-11-07 22:09:57 UTC<PHONE_NUMBER>000)

========
JMXFetch
========

  Information
  ==================
  Initialized checks
  ==================
    no checks

  Failed checks
  =============
    no checks

=========
Forwarder
=========

  Transactions
  ============
    Cluster: 0
    ClusterRole: 0
    ClusterRoleBinding: 0
    CronJob: 0
    CustomResource: 0
    CustomResourceDefinition: 0
    DaemonSet: 0
    Deployment: 0
    Dropped: 0
    HighPriorityQueueFull: 0
    HorizontalPodAutoscaler: 0
    Ingress: 0
    Job: 0
    Namespace: 0
    Node: 0
    OrchestratorManifest: 0
    PersistentVolume: 0
    PersistentVolumeClaim: 0
    Pod: 0
    ReplicaSet: 0
    Requeued: 0
    Retried: 0
    RetryQueueSize: 0
    Role: 0
    RoleBinding: 0
    Service: 0
    ServiceAccount: 0
    StatefulSet: 0
    VerticalPodAutoscaler: 0

  Transaction Successes
  =====================
    Total number: 901
    Successes By Endpoint:
      check_run_v1: 426
      intake: 38
      metadata_v1: 11
      series_v2: 426

  On-disk storage
  ===============
    On-disk storage is disabled. Configure `forwarder_storage_max_size_in_bytes` to enable it.

  API Keys status
  ===============
    API key ending with 10ac1: API Key valid

==========
Endpoints
==========
  https://app.datadoghq.com - API Key ending with:
      - 10ac1

==========
Logs Agent
==========
    Reliable: Sending compressed logs in HTTPS to agent-http-intake.logs.datadoghq.com on port 443
    BytesSent: 9.964603e+06
    EncodedBytesSent: 1.80612e+06
    LogsProcessed: 6929
    LogsSent: 6928
    CoreAgentProcessOpenFiles: 49
    OSFileLimit: 1048576

  ============
  Integrations
  ============

 ....Redacted

=============
Process Agent
=============

  Version: 7.49.0
  Status date: 2023-11-07 22:10:07.614 UTC<PHONE_NUMBER>614)
  Process Agent Start: 2023-11-07 20:23:25.293 UTC<PHONE_NUMBER>293)
  Pid: 1
  Go Version: go1.20.10
  Build arch: amd64
  Log Level: info
  Enabled Checks: [pod process rtprocess]
  Allocated Memory: 21,643,080 bytes
  Hostname: i-0b3db96a4153207be
  System Probe Process Module Status: Not running
  Process Language Detection Enabled: False

  =================
  Process Endpoints
  =================
    https://process.datadoghq.com - API Key ending with:
        - 10ac1

  =========
  Collector
  =========
    Last collection time: 2023-11-07 22:10:06
    Docker socket:
    Number of processes: 79
    Number of containers: 23
    Process Queue length: 0
    RTProcess Queue length: 0
    Connections Queue length: 0
    Event Queue length: 0
    Pod Queue length: 0
    Process Bytes enqueued: 0
    RTProcess Bytes enqueued: 0
    Connections Bytes enqueued: 0
    Event Bytes enqueued: 0
    Pod Bytes enqueued: 0
    Drop Check Payloads: []

  ==========
  Extractors
  ==========

    Workloadmeta
    ============
      Cache size: 0
      Stale diffs discarded: 0
      Diffs dropped: 0

=========
APM Agent
=========
  Status: Running
  Pid: 1
  Uptime: 6403 seconds
  Mem alloc: 12,086,152 bytes
  Hostname: i-0b3db96a4153207be
  Receiver: <IP_ADDRESS>:8126
  Endpoints:
    https://trace.agent.datadoghq.com

  Receiver (previous minute)
  ==========================
    From nodejs v20.8.1 (v8), client 4.16.0
      Traces received: 128 (117,448 bytes)
      Spans received: 128

    Priority sampling rate for 'service:company-api-redis,env:dev': 100.0%

  Writer (previous minute)
  ========================
    Traces: 0 payloads, 0 traces, 0 events, 0 bytes
    Stats: 0 payloads, 0 stats buckets, 0 bytes

==========
Aggregator
==========
  Checks Metric Sample: 1,556,448
  Dogstatsd Metric Sample: 134,326
  Event: 1
  Events Flushed: 1
  Number Of Flushes: 426
  Series Flushed: 1,263,844
  Service Check: 2,893
  Service Checks Flushed: 3,311

=========
DogStatsD
=========
  Event Packets: 0
  Event Parse Errors: 0
  Metric Packets: 134,325
  Metric Parse Errors: 0
  Service Check Packets: 0
  Service Check Parse Errors: 0
  Udp Bytes: 23,390,557
  Udp Packet Reading Errors: 0
  Udp Packets: 62,996
  Uds Bytes: 0
  Uds Origin Detection Errors: 0
  Uds Packet Reading Errors: 0
  Uds Packets: 1
  Unterminated Metric Errors: 0

=====================
Datadog Cluster Agent
=====================

  - Datadog Cluster Agent endpoint detected: https://<IP_ADDRESS>:5005
  Successfully connected to the Datadog Cluster Agent.
  - Running: 7.49.0+commit.9cb8e9c

=============
Autodiscovery
=============
  Enabled Features
  ================
    containerd
    cri
    kubernetes
    orchestratorexplorer

====================
Remote Configuration
====================

    Organization enabled: False
    API Key: Not authorized, add the Remote Configuration Read permission to enable it for this agent.
    Last error: None

====
OTLP
====

  Status: Not enabled
  Collector status: Not running

Postgres check configured via Service definition
apiVersion: v1
kind: Service
metadata:
  name: postgres
  namespace: my-system
  labels:
    tags.datadoghq.com/env: dev
  annotations:
    ad.datadoghq.com/service.check_names: '["postgres"]'
    ad.datadoghq.com/service.init_configs: '[{}]'
    ad.datadoghq.com/service.instances: |
      [
        {
          "dbm": true,
          "host": "devdb-postgres.redacted.us-east-2.rds.amazonaws.com",
          "port": 5432,
          "username": "datadog",
          "dbname": "api",
          "tags": [
            "dbinstanceidentifier:devdb-postgres"
          ],
          "aws": {
            "instance_endpoint": "devdb-postgres.redacted.us-east-2.rds.amazonaws.com",
            "region": "us-east-2"
          }
        }
      ]
spec:
  ports:
    - port: 5432
      protocol: TCP
      targetPort: 5432
      name: postgres

Agent Configuration
apiVersion: datadoghq.com/v2alpha1
kind: DatadogAgent
metadata:
  name: datadog
  namespace: my-system
spec:
  features:
    apm:
      enabled: true
      hostPortConfig:
        enabled: true
    eventCollection:
      collectKubernetesEvents: true
    liveProcessCollection:
      enabled: true
    logCollection:
      enabled: true
      containerCollectAll: true
    liveContainerCollection:
      enabled: true
    orchestratorExplorer:
      enabled: true
  global:
    credentials:
      apiSecret:
        secretName: datadog-secret
        keyName: api-key
      appSecret:
        secretName: datadog-secret
        keyName: app-key
    site: datadoghq.com
  override:
    clusterAgent:
      image:
        name: gcr.io/datadoghq/cluster-agent:latest
    nodeAgent:
      image:
        name: gcr.io/datadoghq/agent:latest
      env:
      - name: "DD_EC2_PREFER_IMDSV2"
        value: "true"

IAM Role Configuration
data "aws_iam_policy_document" "db_monitor" {
  statement {
    effect = "Allow"
    actions = [
      "rds-db:connect"
    ]
    resources = [
      "arn:aws:rds-db:${data.aws_region.current.name}:${data.aws_caller_identity.current.account_id}:dbuser:${module.db.db_instance_resource_id}/${local.db_monitor_role_name}"
    ]
  }
}

data "aws_iam_policy_document" "db_assume_role" {
  statement {
    actions = ["sts:AssumeRole"]
    principals {
      type        = "Service"
      identifiers = ["rds.amazonaws.com"]
    }
  }
}

resource "aws_iam_role" "db_monitor" {
  name = local.db_monitor_role_name

  assume_role_policy = data.aws_iam_policy_document.db_assume_role.json

  inline_policy {
    name   = "DatadogRDSMonitoringPolicy"
    policy = data.aws_iam_policy_document.db_monitor.json
  }
}

Additional environment details (Operating System, Cloud provider, etc):

Kubernetes 1.27 via AWS EKS
AWS RDS Postgres 14.7 db.m6g.2xlarge
IAM Authentication
Datadog Operator 1.2.1 (managed via Helm/Terraform)

Steps to reproduce the issue:

Grant Agent Access Basic docs and use IAM permissions managed authentication

This includes creating the new  parameter groups, attaching, and rebooting the db, as well as the SQL commands ran

Apply postgres service resource definition to kubernetes
Allow agents to attempt to connect to database

Describe the results you received:

Once provided with the postgres config, we can see that it attempts to make a connection to the correct service, but immediately returns an "out of memory" error.
Attempted rebooting operator, cluster-agents, and agents just to be sure
It does appear to be attempting the IAM workflow, as I saw the errors when we didn't provide aws.region

Describe the results you expected:

Agent postgres check to connect to database and start monitoring

Additional information you deem important (e.g. issue happens only occasionally):

What else can we do to troubleshoot this?
Are there checks or databases we can exclude to reduce the scope?
Does the postgres check version need to match our implementation? I noticed the agent status showed postgres (15.1.1) but our RDS instance is on 14.7. Is this something that we can/should set? Or, is this backwards compatible?
Did open case with Datadog support 1427239

Hi @ashleywxwx, I was looking into this briefly & have some reason to believe that there may be a memory leak in the version of the boto library that is shipped in 7.49 of the agent. As a quick test, could you downgrade to 7.46, the first agent version that contained this feature to see if you still see the issue?
We have other customers using this feature without any issues on earlier versions of the agent, so I am trying to rule out the boto API library version bump.

@jmeunier28
I have updated to gcr.io/datadoghq/agent:7.46.0-rc.2 and still receiving the same issue. Let me know if there's a different tag I should use. I'll also go ahead and try a 7.45 version here for kicks.

Weird that rc refers to "release candidate", which isn't an official DD release. It should be this one docker pull datadog/agent:7.46.0

Oh, my mistake, that explains why I couldn't find a tag under 7.46, I'll give 7.46.0 a try

For what it's worth, using version 7.45.1 I now see a different error, but haven't dug in much further. Configuration is the same (e.g. aws.region is provided) , so maybe a difference there?
2023-11-10 20:17:43 UTC | CORE | ERROR | (pkg/collector/worker/check_logger.go:69 in Error) | check:postgres | Error running check: [{"message": "fe_sendauth: no password supplied
", "traceback": "Traceback (most recent call last):
  File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/checks/base.py\", line 1135, in run
    self.check(instance)
  File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/postgres/postgres.py\", line 725, in check
    raise e
  File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/postgres/postgres.py\", line 693, in check
    self._connect()
  File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/postgres/postgres.py\", line 522, in _connect
    self.db = self._new_connection(self._config.dbname)
  File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/postgres/postgres.py\", line 506, in _new_connection
    conn = psycopg2.connect(**args)
  File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/psycopg2/__init__.py\", line 127, in connect
    conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
psycopg2.OperationalError: fe_sendauth: no password supplied

"}]

IAM is only supported starting in version 7.46 of the postgres agent

Okay, I have pinned to tag 7.46.0, but am still seeing the error.
2023-11-10 20:40:29 UTC | CORE | ERROR | (pkg/collector/worker/check_logger.go:69 in Error) | check:postgres | Error running check: [{"message": "out of memory
", "traceback": "Traceback (most recent call last):
  File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/checks/base.py\", line 1142, in run
    self.check(instance)
  File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/postgres/postgres.py\", line 750, in check
    raise e
  File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/postgres/postgres.py\", line 717, in check
    self._connect()
  File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/postgres/postgres.py\", line 546, in _connect
    self.db = self._new_connection(self._config.dbname)
  File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/postgres/postgres.py\", line 530, in _new_connection
    conn = psycopg2.connect(**args)
  File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/psycopg2/__init__.py\", line 127, in connect
    conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
psycopg2.OperationalError: out of memory

"}]

@ashleywxwx can you tell me more about your setup? How much memory are you giving the agent container? Do you see this only when configuring the agent with IAM authentication or do you also see it when trying to connect via username/password?

The same apply here using datadog-agent version:
Agent 7.47.1 - Commit: 24dcc70 - Serialization version: v5.0.90 - Go version: go1.20.6

@ashleywxwx and @OmriBenShoham we were able to reproduce this internally by removing the permissions that need to be granted for the IAM user. So, we ran REVOKE rds_iam from datadog; & then saw the same error on agent startup
          conn = _connect(dsn, connection_factory=connection_factory, **kwasync)
      psycopg2.OperationalError: out of memory

This permission is mentioned here & is necessary to make the feature work. To do this log in to your database instance as the root user, and grant the rds_iam role to the new user:
GRANT rds_iam TO <YOUR_IAM_ROLE>;

Once the role is all set up and attached to your instance, you can configure your instance config like this:
instances:
- dbm: true
 host: example-endpoint.us-east-2.rds.amazonaws.com
 port: 5432
 username: <YOUR IAM ROLE NAME>
 aws:
   region: <YOUR DB HOST'S REGION>

Can you double check that you performed all of these steps correctly in accordance with these docs https://docs.datadoghq.com/database_monitoring/guide/managed_authentication/#configure-iam-authentication?
As a side note the out of memory error is very misleading. I would expect error would raise here.  We are investigating this more internally, but hopefully this unblocks you.

I was able to connect with a standard user & password, which should unblock me. If there is additional troubleshooting I can help with around this error, please let me know. Otherwise, we can close this issue.
Thank you for the help @jmeunier28

@ashleywxwx FWIW we had a few other people report this as well. Our docs were not very clear initially & told people to set the region in the aws block, which is required for IAM. What was not made clear is the fact that setting region means we will attempt IAM authentication and ignore the password set by the user. We have since updated our docs to make this distinction more clear here.
We also have some updates to make the instance configuration for IAM more clear, which will come out in a future release of the agent. Thanks for pointing out the issue to us!


Some setCookie directives are missing in karate 1+ versions

Same context than #1708 , after an HTTP call, server answers (in HTTP headers) :
SetCookie CookieValue; Secure;HttpOnly;SameSite=None;Expires=....
But Karate (versions 1+, 0.9.6 was fine) doesn't "see" all of those directives :
Secure, Expires are visible by Karate, while HttpOnly and SameSite are not.
Reason is that we create cookies from a map, where we didn't put all the attributes from the incoming serverResponse :
https://github.com/intuit/karate/blob/3a9d5148c3e0ae167736174527040abb8d7fc536/karate-core/src/main/java/com/intuit/karate/http/ApacheHttpClient.java#L297,L303
Thing is the com.intuit.karate.http.Cookies class already knows those fields (public static final attributes exist for Secure and SameSite), but the org.apache.http.cookie.Cookie doesn't seem to know them...
I don't know what the solution is, relying on another interface could do the trick, but I don't see how far it will impact the rest of the code.
Also, I have been unsuccessful in finding information on how people use those directives with this apache lib.
But since those directives are quite widespread, I would find it hard to believe that no one has encountered and fixed the problem already...

@zgael I also don't understand all of this. I'll treat this as duplicate of the other issue. maybe others will come back with the same issue and more ideas. there was some cookie related discussions for 1+ and it would have been nice to get this feedback earlier. so I don't consider this a priority - yet.

@zgael I can re-open if you find a way to get the missing properties from apache + a PR, in case apache gives you the "raw" cookie header, we could parse that with netty etc.

@zgael I also don't understand all of this. I'll treat this as duplicate of the other issue. maybe others will come back with the same issue and more ideas. there was some cookie related discussions for 1+ and it would have been nice to get this feedback earlier. so I don't consider this a priority - yet.

Yeah, I actually don't understand HOW I didn't see that earlier, I am pretty confident my test suite was OK with at least 1.1.0.RC4... But it looks like it didn't (some dependency cache issue, entirely by my fault maybe...)
I'll try to see what can be done with the apache lib, but can't be sure it's gonna be successful.

@zgael no worries. just curious, does this "block" some use-cases you have now ?
so that you have the context:
I started out bypassing apache completely for cookie handling, but then we ran into this: https://github.com/intuit/karate/issues/1526
and that ticket has a commit where you can see we went back to apache for cookies. if not for the re-direct problem we would be okay. so one option is to add our intelligence into a re-direct (and maybe also re-tries) to handle cookies, but it seemed to be complex

Yeah that "blocks" some of my use-cases :
I use karate to test a web-based application, especially its security.
One important point of web-app security is to protect the authentication cookie, so there are plenty of directives a server can use to instruct the client's browser to protect it.
Secure, HttpOnly, SameSite are examples of such directives.
My test is simple : make a request, check that the response contains Secure, HttpOnly and SameSite (among others).
And currently, our test crashes because of the missing fields.

@zgael question, by any chance is the information present in the response headers sufficient for your use-case ?
example:
* url 'https://postman-echo.com/cookies/set?foo1=bar1&foo2=bar2'
* method get
* def first = responseHeaders['Set-Cookie'][0]
* match first == 'foo1=bar1; Domain=postman-echo.com'

That's almost exactly what I have :
And match responseHeaders["Set-Cookie"][0] contains "SameSite=None"
But Karate doesn't even know those directives are presents, even loglevel DEBUG (the curl-like request/response display - which is awesome btw) sees the truncated output :
Actual :
Set-Cookie: CookieName=CookieValue; Max-Age=1628523155000; Expires=Mon, 14 Jun 53627 06:26:42 GMT; Domain=...; Secure
Expected :
Set-Cookie: CookieName=CookieValue; path=/; Expires=Mon, 09 Aug 2021 15:32:35 GMT; Secure; HttpOnly; SameSite=None;
Also, there's the domain directive instead of the path, I didn't notice it until now.
But it seems to me that the apache cookie interface is not enough when it comes to security :(

@zgael to be honest this is not something I would consider a high-priority test. so I'll wait for a contribution and move this to the project board after a while.
just a thought, see if cURL works for this: https://stackoverflow.com/a/64352676/143475

Yes curl works for this indeed!
That could be a workaround for people in dire need, but not all environments have a working curl, so I would not rely on it too much.

closing as duplicate of #1708 which will attempt to refactor cookie handling


[HTTP] Update the transport API

At the moment we have following too,
HttpContent getHttpContent()
MessageFuture getHttpContentAsync()
But we ideally want is,
MessageFuture getHttpContentAsync()
MessageFuture getHttpContentAsync().sync()
Need to improve the code to support this.

Closing this as this is no longer a high priority.


type convert

I have a property like this:
@property (nonatomic, strong) NSArray *thumb;
if server return the property like this:
{
thumb="";
}
then,the app is crashed.I think it can return an error not crashed. for this,Jsonmodel is strong.
Do you think so?

Make sure that the server always sends thumb as an array. Here in sample response
{
thumb="";
}

thumb is just the NSString. That's why you are getting the crash.

Sorry, I don't describe clearly.This question is:
when the server return correct, the [thumb] is an array, like this:
{
thumb=("aaa","bbb");
}
but, if the array is empty, it will return:
{
thumb="";
}
I know, I can tell the server to modify the field.but server maybe change,
so,I wanna, in this case , It's not crashed.

You can handle this by having custom setters:
- (void)setThumbWithNSArray:(NSArray *)array
{
  _thumb = array;
}

- (void)setThumbWithNSString:(NSString *)string
{
  if (string.length == 0)
    _thumb = nil;

  // undefined behavior
}


feat: Add support for Document Picture-in-Picture

This PR adds experimental support for the Document Picture-in-Picture API in the Shaka Player.
I'm making some assumptions about how Shaka Player works and I'd love your review on this. Thank you!
Closes https://github.com/shaka-project/shaka-player/issues/4964

@beaufortfrancois Please, fix the build errors. Thanks!

The dimensions that the player occupies in the window becomes 0, this can cause problems in some websites.

I agree and that's something I'd like to discuss. Adding a container may be enough. I'm not sure though.

@joeyparrish , what is your opinion about that?

Looks like the externs for documentPictureInPicture need to be updated to make that an implementation of EventTarget.  I'll make the revision.

Some other type information is missing, too, so I'm adding all of it.

@joeyparrish Thanks for fixing externs!

Do you folks know when this feature will be available in next shaka player release?

@joeyparrish @avelad
Do you know which release will have Document Picture-in-Picture support? Any rough ETA?


Introduce detekt for all subprojects

Solves #32

For now, I intentionally didn't set up detekt autoformatting because we use KtLint for that
The build is configured to succeed up to a maximum of 36 issues (= our current number of issues)

@IanArb / @MrIceman: I can't seem to set reviewers here, but this PR is ready for review.

@Niekon01 If I'm not mistaken, this wasn't paid yet. I'd appreciate it if you could take a look :)
2c9a538d3952a780ba65ee5a672e9ae4b415f542ab265e9517687b25ae4897aa

Hey @petersommerhoff there is no PR reward on the issue that this PR closes. This is why I did not pay any amount.

@IanArb: Could you attach an amount of coins that you think would fit? Thanks!


analyzer: Disable dependency resolution in MavenSupport.parsePackage()

The function only determines information about the package itself, not
about the dependencies, so it makes no sense to resolve the dependencies.

This change is

Maybe a little bit, but not much because the full dependency tree should already be resolved at this point. Probably in situations where the full tree contains a different version of a dependency due to version conflict resolution.


test: please ignore

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

AWS CodeBuild CI Report

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

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

AWS CodeBuild CI Report

CodeBuild project: AutoBuildProject89A8053A-yXMHf40Kl6rH
Commit ID: 4d55022ba6ee0eb2b1f24bfdcd87936597809d24
Result: SUCCEEDED
Build Logs (available for 30 days)

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


myapp download script updated

There seem to be conflicts with the DownloadMyApps file.
Please move app_list.txt to config/myapps.txt

There are still conflicts

check and pull now


Add a top level Google and a child App Engine Deployment property page

The Google property page is visible always (should it be restricted to JavaProjects?), the deploy page is only visible for projects having the App Engine Standard facet.
Implements the first task in #492

LGTM.  It may make sense to implement the contents of the DeployPropertyPage as a standalone widget that could also be hosted in a dialog.


feat: document hooks server architecture + protocol

Motivation and Context
This PR documents the current hooks server architecture. It documents the hooks protocol between the Hooks server and the wunderNode.

Marketing Changelog

Checklist

[ ] run make test
[ ] PR title must follow conventional-commit-standard
[ ] tests and/or benchmarks are included
[ ] documentation is changed or added
[ ] commit message and code follows the Code of conduct

Thank you @StarpTech!


Water Leak Sensor H5054 - Not reporting leaks or correct battery status

What issue do you have? Please be as thorough and explicit as possible.
The H5054 Leak sensors do not send leak status to HomeKit, therefore no Critical Alert is generated
The native Govee app has the correct leak info and sends proper push notifications (and email) from Govee. Also battery info from the plug-in is incorrect at 0%
Details of your setup.

Do you use (1) Homebridge UI-X (2) Homebridge CLI or (3) HOOBS?

Homebridge

Which version of Homebridge/HOOBS do you have?

1.7.0

Which platform do you run Homebridge/HOOBS on (e.g. Raspberry Pi/Windows/HOOBS Box)? Please also mention your version of Node.js/NPM if known.

MacOS Monterey 12.7.2

Node 20.11.0

Which version of this plugin (homebridge-govee) do you have? Has the issue started since upgrading from a previous version?

10.3.0

Unknown when problem started

Which Govee devices do you have that are causing issues? Please include product models if applicable.

H5054 Water Leak Sensors

Please paste any relevant logs below.

No errors in the logs. Note I have 16 leak sensor devices but edited the log to only show one of them
[1/21/2024, 8:25:51 PM] [Govee] Launched child bridge with PID 48901
[1/21/2024, 8:25:51 PM] Registering platform 'homebridge-govee.Govee'
[1/21/2024, 8:25:51 PM] [Govee] Loaded homebridge-govee v10.3.0 child bridge successfully
[1/21/2024, 8:25:51 PM] Loaded 16 cached accessories from cachedAccessories.0E65E4382F51.
[1/21/2024, 8:25:51 PM] [Govee] Initialising plugin v10.3.0 | System darwin | Node v20.11.0 | HB v1.7.0 | HAPNodeJS v0.11.1...
[1/21/2024, 8:25:51 PM] [Govee] Plugin initialised. Setting up accessories....
[1/21/2024, 8:25:51 PM] Homebridge v1.7.0 (HAP v0.11.1) (Govee) is running on port 48354.
[1/21/2024, 8:25:53 PM] [Govee] [LAN] client enabled and found 0 device(s).
[1/21/2024, 8:25:54 PM] [Govee] [HTTP] client enabled and found 16 device(s).
[1/21/2024, 8:25:54 PM] [Govee] [AWS] disabling client as disabled in config.
[1/21/2024, 8:25:54 PM] [Govee] [BLE] disabling client as disabled in config.
[1/21/2024, 8:25:54 PM] [Govee] [Guest Toilet] initialising with options {}.
[1/21/2024, 8:25:54 PM] [Govee] [Guest Toilet] initialised with id [42:F5:20:38:CB:F6:00:18:C3] [H5054].
[1/21/2024, 8:25:54 PM] [Govee] ✓ Setup complete. This plugin has been made with ♥ by bwp91, please consider a ☆ on GitHub if you are finding it useful!

Thanks for the plugin Ben!
Same issue is happening with mine. I only installed the plugin recently and was just testing today. Leak event not detected.
I uninstalled the latest plugin (v10.3.0) and installed last version v10.2.0. That gets me the leak alerts to activate. But they never deactivate. I guess it's having trouble polling via HTTP.
v10.2.0 occasionally throws a refresh error in the log: "[Water Heater] could not be refreshed as Request failed with status code 502 at settle (file:///homebridge/node_modules/homebridge-govee/node_modules/axios/lib/core/settle.js:19:12)"
v10.3.0 throws no errors I can see.
Unfortunately LAN detection isn't working I think because my devices are on a separate VLAN than the homebridge hub.
-D

That gets me the leak alerts to activate. But they never deactivate.

I could be wrong, but I think to get the leak detection to "reset" you must physically do it from the native Govee app. And it's not clear what to do there, either. Pressing "Got It" is not enough, you must go in to settings for the individual sensor and Delete Data for that particular unit.

I also had to revert to v10.2.0 to make it work.

@bwp91 - unresolved in 10.4 will you please re-open this issue?
Non-collaborators cannot re-open if they were closed by you.
Thanks!


Bug when trying to put "01" in birth date

Hi there,
I just tried to update the birth date in my profile to the most common one on the internet (01/01) but when I put the first 0, the form immediately crashes (see the attached gif)

@switowski thanks for the report!
The new repo is here: I made a PR: https://github.com/pythonitalia/pycon/pull/1390 😊

@switowski merged! I'll close this. I think in future we'll make the birth date optional, I need to check with the other organisers :)


Feature : team management

Hello,
Is it planned in future versions to support team management?
Thank you in advance for your response.

hi @bynicodevelop , not on the roadmap, the https://docs.npmjs.com/cli/v7/commands/npm-team is so deeply integrated into npmjs business logic and completely closed that unique alternative would be "made up" something based on what you see on the npm CLI. They can change easily the logic in future major releases and break the registry, it is hard to follow up if is a closed source. I haven't pursued personally this command for that and other lack of time reasons.


unused lil bf sprites?

What is your question?
im just curious about something

how exactly are these miss and hey! sprites used for lil bf in the chart editor?

they're unused lol
i can't really remove them from the xml because that would break it

ohhh ok yea that makes sense-

im reopening this just to ask another question
how was the unused sprites meant to be used?
liek was the lil bf sprite meant to be a playable thing in the chart editor (yk like when you playtest the chart in the chart editor with esc) or was it smth else?

who knows

im reopening this just to ask another question
how were the unused sprites meant to be used? liek was the lil bf sprite meant to be a playable thing in the chart editor (yk like when you playtest the chart in the chart editor with esc) or was it smth else?

go ask rozebud cuz idk


Lidl Smart Plug nkcobies and RGB bulb q50zhdsc

#Added Lidl Smart Plug and RGB bulb sold in Denmark.
Closes #397, closes #529.

Added to next release


Check a variety of base classes in the NotAuthorizedNodeType check

Closes #142
If I add Types::BaseUserType to SafeBaseClasses I'd expect all of following to pass the cop:

Absolute reference

module Types
  class UserType < ::Types::BaseUserType
    implements GraphQL::Types::Relay::Node

    field :uuid, ID, null: false
  end
end

Relative reference to the "root" namespace

module Types
  class UserType < Types::BaseUserType
    implements GraphQL::Types::Relay::Node

    field :uuid, ID, null: false
  end
end

Relative reference within the module

module Types
  class UserType < BaseUserType
    implements GraphQL::Types::Relay::Node

    field :uuid, ID, null: false
  end
end

The only one that currently passes the cop is case 2.
These are all valid ruby, but could lead to confusion/frustration when trying to sort out GraphQL authorization. I'd propose checking a list of possible parent classes in this instance.
In case 1 we can just check Types::BaseUserType is our SafeBaseClasses list.
In case 2 we need to check if either Types::BaseUserType or Types::Types::BaseUserType is in our list.
Finally in case 3 we need to check if either BaseUserType or Types::BaseUserType is in our list.
I don't think we can see from the AST which other classes have been defined in the code, so checking for the two possible permutations is required for this cop to be robust.

Hey hey, makes a lot of sense, thank you! Could you please at these rubocop offences and I'll merge it?

Hey hey, makes a lot of sense, thank you! Could you please at these rubocop offences and I'll merge it?

Thanks! All done :)


docs: add gif of example images, small explanation

docs: add gif of example images, small explanation
What does this PR do?

Adds gif on how to pull our test image
Adds link to our VM guide on how to test it after building

Screenshot / video of UI

N/A, see doc
What issues does this PR fix or reference?

Closes https://github.com/containers/podman-desktop-extension-bootc/issues/342
How to test this PR?

N/A, doc
Signed-off-by: Charlie Drage<EMAIL_ADDRESS>

FYI I see 10 links starting in the markdown with (/(relative links that will fail)

I have updated this PR to add the absolute links. The rest of the absolute links will be added with #411


Fix OGV/Theora playback

I've done some looking into #10031. Replacing the Vorbis module with a stub like the Ogg module (since vorbis is now replaced with STB_Vorbis anyhow, this shouldn't be a huge loss) and writing a quick OGV/OGM ResourceLoader, I have video playback working without audio playback

Thanks for fixing this! I have one small question : could you squash those two commits please? 'Merging changes into my local fork' doesn't make much sense as a commit for the master branch.

Just in case you're interested in this docs page:
https://godot.readthedocs.io/en/stable/community/contributing/pr_workflow.html#mastering-the-pr-workflow-the-rebase

I've hacked away at the webm module and gotten the webm video importer working, though it suffers the same fate as the theora module in that audio is not working for me.

The diff includes recent commits by others?

It shouldn't have included those, darn, I'm definitely not used to rebasing yet.

@akien-mga recently wrote a nice guide about it here


eat: astro-font - optimize fonts & prevent CLS

Astro Font: https://www.launchfa.st/blog/building-astro-font
Changes
This PR integrates astro-font which automatically generates the fallback font and pass it as CSS variables.

Hey @rishi-raj-jain, thanks for the contribution!
I would like to keep this template as dependency-free as possible, though.
However, feel free to add anything you want when working with it. 🤗


Required to include routes in web.php / require_once channels.php?

Hello,
Thanks for this! It made my live much easier! I've got the websockets configured and working as expected.
But the routes didn't work in routes/channels.php. Instead I've I had to add  them to routes/web.php (or include a require_once channels.php in the web routes).
I'm wondering if this is expected and I just missed it or did I do something wrong? I can provide further details or answer question, if that helps.
Cheers!

You should use channels.php and uncomment the BroadcastingServiceProvider from config/app.php

Awesome, thank you!


Testing page on dev server

Just did a commit to test build server: https://github.com/tdwg/website/commit/5fb7b037511687e27cb772a5574cba93407ba6fd and the build server indicates a successful build, but the site indicates a test page: http://dev.tdwg.org/
PS: can the URL of the build server be public (as in: part of the documentation)?

The build log says ERROR: Unknown status 'draft' for file pages/home.md, skipping it.
index.html wasn't generated, so you're seeing the default Apache page.
The build system is already public for other GBIF projects, so it can be public for this.

I don't think settings-dev.py is working as intended.
$ pelican -s settings.py
WARNING: Feeds generated without SITEURL set properly may not be valid
Done: Processed 1 article, 0 drafts, 4 pages and 0 hidden pages in 0.23 seconds.

$ pelican -s settings-dev.py
WARNING: Feeds generated without SITEURL set properly may not be valid
ERROR: Unknown status 'draft' for file pages/home.md, skipping it.
Done: Processed 1 article, 0 drafts, 3 pages and 0 hidden pages in 0.20 seconds.

Ok, thanks. Will look into this on Monday.

You now have SSH access, using the SSH key you provided to GitHub, as<EMAIL_ADDRESS>sudo should be used if you need to do something as root. Other than looking at log files or restarting HTTPD, I'd prefer to know when anything needs to be changed.

Thanks, noticed console output is public at https://builds.gbif.org/job/tdwg-dev-prod/16/console. Will let you know when I'll need to use ssh.


update from 0.9.7 to 1.0.5 broke project completely without warning

it's not immediately clear to me what to do so that I don't wreck my project and metadata.
the config no longer works:
main.go:59: failed to parse config: failed to open file: open nhost/nhost.toml: no such file or directory

nhost up doesn't run:
main.go:59: no nhost project found, please run nhost init or nhost config pull
And I looked a lot but couldn't find any specific migrations steps.

Ok, just found this and tried to follow it:
https://docs.nhost.io/cli/migrate-config
➜  hasura git:(main) nhost config pull
main.go:59: failed to get app info: failed to find app with subdomain: local
➜  hasura git:(main) nhost up
main.go:59: no nhost project found, please run `nhost init` or `nhost config pull`

Doesn't work.

Ok, struggling slowly to move. Apparently I had to run:
nhost config pull --subdomain MY_LINKED_SUBDOMAIN
It should have been the default, but that didn't work I guess? ... moving on. Now running nhost up gives me this error:
failed to generate docker-compose.yaml: hasura version must be at least v2.18.0
- Do you want to stop Nhost's development environment? [y/N]

So, in the end things worked out but I can't say it was easy. At all.
As feedback: It would be nice if much clearer migration guides were accompanying major changes.

hey @israelidanny  can you please describe how did you make it work? I'm going through the same issue right now.

hey @israelidanny  can you please describe how did you make it work? I'm going through the same issue right now.

The no project found goes away if your force a specific subdomain.


fix: Remove Module type from package.json

What kind of change does this PR introduce?
Remove Module type from package.json. Also adds arethetypeswrong/cli to avoid future regressions regarding this type of issues

https://github.com/supabase/realtime-js/issues/424


[de] Fix typos in README

I fixed some crucial typos and errors in the README-de.md!

/language de
/retitle [de] Fix typos in README

/kind cleanup

Ping de localization team for review
/cc @kubernetes/sig-docs-de-reviews

/lgtm

/cc https://github.com/orgs/kubernetes/teams/sig-docs-de-reviews

I'm afraid I won't be able to help with reviewing PRs on the German language side as I can't read German.

/label tide/merge-method-squash

/approve


How to get started

Please only ask one question per issue!
Describe what it is that you want to accomplish
How to start using picamera2?
Describe alternatives you've considered
From documentation I tried the following:
$ sudo apt install -y python3-pyqt5 python3-opengl
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
python3-opengl is already the newest version (3.1.5+dfsg-1).
python3-opengl set to manually installed.
python3-pyqt5 is already the newest version (5.15.2+dfsg-3).
python3-pyqt5 set to manually installed.
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
$ sudo apt install -y python3-picamera2
Reading package lists... Done
Building dependency tree... Done
Reading state information... Done
**python3-picamera2 is already the newest version (0.3.8-1).**
0 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
$ python
Python 3.9.2 (default, Feb 28 2021, 17:03:44)
[GCC 10.2.1 20210110] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import time
>>> from picamera2 import PiCamera2, Preview
Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
ImportError: cannot import name 'PiCamera2' from 'picamera2' (/usr/lib/python3/dist-packages/picamera2/__init__.py)
>>>

Additional context
OS: Debian GNU/Linux 11 (bullseye) aarch64
Host: Raspberry Pi 3 Model B Rev 1.2
As a complete newbie, how do I get started with picamera2 self-paced exercises?
Thanks.

It looks like you've used the wrong capitalisation in the import statement.
Which should be -
from picamera2 import Picamera2

https://datasheets.raspberrypi.com/camera/picamera2-manual.pdf is very useful.
Along with the examples in this repository.

 Sorry to waste your time on something like this. I feel terrible because I can't even cut-and-paste correctly.


schema() returns a model, not a schema

I'm wondering why it works in this manner.  In order to get the schema and attach plugins to it, I have to do this sort of devilry:
var data = fs.readFileSync('public/models/user.json');
var User = new Schema(generator._convert(JSON.parse(data)));
User.plugin(somePlugin, {});
module.exports = mongoose.model('User', User);

I'm using a private method I shouldn't be using.  If I get the model via schema() then modifing the model's schema property directly doesn't seem to work because the model is already created.

@boneskull Yes, that was stupid! I upgraded this module, so that you would now do:
var UserSchema = generator.getSchema(JSON.parse(data));
var UserModel = mongoose.model('User', UserSchema);

@boneskull it would be lovely to get some feedback from you for the latest version ;)

Hehe, forgot about this one.  I haven't had occasion to use mongoose in awhile, so I will reserve comment until I do.  Thanks though!

Cool. 10x


[WorksForYou] Fix sizing issue for embedded models vc on iPad Pro

On iPad Pro, the embedded models view controller doesn't size properly:

On a happier note, single artworks are :+1:

Does it resize properly in other parts of the app? And by resize, do you mean that this is only an issue after rotation?

Ah I meant size instead of resize.

I think elsewhere in the app, it's similar. I don't know that it's necessarily wrong but it doesn't stretch to the sides the way it does on smaller iPads.

Closing this


Update FAKE to 4.1 and all build dependencies

This one uses the latest FCS to allow F# 4.0 in build scripts. Also dogfood

While you're at it, could you help renovate the Release target?
Right now, NuGet push is not automatic; git tags and release notes may be out of sync with actual releases.

Yep will do

@forki - do you want to do that in a separate commit or as part of this one?

I think I do a second one


Common Lisp implementation logotypes

I have made a collection of high-res logotypes (originally 4000x4000px) in Photoshop. The upside is that I still have the original PSD files, the downside is that they are pretty huge and the logos are raster rather than vector.
You can see the smaller transparent PNGs at https://imgur.com/a/QEd1p

I was really amazed, actually I want to make another logo other than the lizard, but my designer friend want to take a rest for while, I love JSCL logo that you made so I ask my friend to adapt that and change here and there.
fortunately you come up with so many beautiful logo, I often look for lisp logo but never find yours in that list, sometimes I find but it's just a thumbnail.
why don't you put it in blog so people can easily find it :)

Is this good enough?

Thank you so much Phone.
Thank you.  :)


Minor fixes

This is a couple of minor fixes:

Remove the unused denseLimit and fix the theoretical problem with sparse limit handling if sparse limit - primorial number wasn't even.
Fix bug where a block height change could trigger log about not enough work.  This should let you reinstate the warning message, but I'll leave it to you to decide if that should be shown in non-debug.
Improve the accuracy of the memory estimate.

Added an additional fix:

Don't turn on verification checks with the debug flag, as these are slow (and one had a bug in it where it could trigger if sieve max was > 2^32).  Instead add a debug level 2 which turns on verify checks.

Merged, thank you.


Exam Mode: Make storing of any data for exam sessions configurable for administrators

Checklist
General

[x] I tested all changes and their related features with all corresponding user types on a test server.
[x] Language: I followed the guidelines for inclusive, diversity-sensitive, and appreciative language.
[x] I chose a title conforming to the naming conventions for pull requests.

Motivation and Context / Description

Since our department for privacy/law said we can only store information for the feature described in here: https://github.com/ls1intum/Artemis/issues/5058#issuecomment-1133114391
I've created a property to disable any storing of data to the exam session: info.student-exam-store-session-data.
Note: The new property replaces "info.browser-fingerprints-enabled"
Steps for Testing

Prerequisites:

1 Admin

Set the flag to false
Create an exam and participate as student
Verify in the DB that no data (IP, UserAgent, Fingerprint, Client Instance) has been stored (all shall be NULL)

Review Progress

Code Review

[x] Review 1
[x] Review 2

Manual Tests

[x] Test 1
[x] Test 2

Tested on our test systems. Works as expected :)
mysql> select * from exam_session where student_exam_id=30 limit 10;
+-----+-----------------+------------------+------------+--------------------------+--------------+------------------+-------------+------------+---------------------+---------------------+
| id  | student_exam_id | session_token    | user_agent | browser_fingerprint_hash | created_by   | last_modified_by | instance_id | ip_address | last_modified_date  | created_date        |
+-----+-----------------+------------------+------------+--------------------------+--------------+------------------+-------------+------------+---------------------+---------------------+
| 101 |              30 | qgGwIjMBUKRCG_L7 | NULL       | NULL                     | test-student | test-student     | NULL        | NULL       | 2022-06-27 09:20:15 | 2022-06-27 09:20:15 |
+-----+-----------------+------------------+------------+--------------------------+--------------+------------------+-------------+------------+---------------------+---------------------+

@JohannesStoehr @b-fein merged develop :)

Would be great to get a couple more approvals for this PR before we can merge it

Also tested it now in the testing session, worked as expected!

Tested in the testing session - works as expected 👍


[New RISC-V Tutorial Resource] - NEORV32, an open-source RISC-V microcontroller

Resource Title
NEORV32
Resource Description
A tiny, customizable and highly extensible MCU-class 32-bit RISC-V soft-core CPU and microcontroller-like SoC written in platform-independent VHDL. The project is highly documented, powered by a nice community, includes software examples, demo FPGA setups and targets FPGA/RISC-V starters as well as advanced users.
Resource Link
https://github.com/stnolting/neorv32
Required Background (Optional)
If further information is required I'm happy to provide it :wink:
Additional Details (Optional)
RISC-V enthusiast and community member having +4 years of hobby and professional RISC-V experience in academia and research. The NEORV32 processor has already been incorporated into commercial products as well as several research projects (see Google scholar). The project is listed in the RISC-V architecture ID list, the RISC-V Exchange data base and also in RISC-V Landscape.

Thank you for your contribution. This is now added to the repository as an open source implementation.

Thank you very much! :)


No error or info message where it should be

I'm trying to connect to Dropbox (probably doesn't actually matters to what), but after couple of seconds the same login form is displayed again. It seems like there are some network restrictions, which don't allow me to connect to Dropbox, but the plugin doesn't give any information about that. It appears the same no matter if the credentials are valid or not. It would be nice to be more informative and show an error or info message.

Very old issue - closed for cleanup-reason. Feel free to reopen, if it is still valid in latest version 2.1.0


Max height bug in Chrome v43

http://stackoverflow.com/questions/30369222/flex-box-bug-with-max-height-in-chrome-v43

I only looked at this briefly, but the demo works fine in Chrome Canary (45), so it's most likely just Flexbug 1. If you think there's more to it than just that, feel free to reopen, but please provide a more simplified demo.


Evaluate exwlshelleventloop migration

Remove https://github.com/MalpenZibo/iced_sctk in favor of https://github.com/waycrate/exwlshelleventloop

The exwlshelleventloop it's promising. Currently, there are some issues: blurry text on HiDPI monitor, and the layer is created on every available monitor.
With these two bugs fixed, I will be able to remove my custom fork of pop_os iced layershell "wrapper", resolve the packaging problem #25, update to iced 13 and add #4 feature

In the end, I decided to move to the pop-os fork of iced. But in the future maybe I can reconsider this decision to be able to use the official iced version.


STAR test cases

I started writing a STAR implementation but got slowed down by the tie-breaking complexity.  Here are my work in progress implementation and unit tests in case they're useful.  (Some of the WDS examples are not correct, and he never responded to my emails.)

https://github.com/endolith/elsim/blob/master/elsim/methods/star.py
https://github.com/endolith/elsim/blob/master/tests/test_star.py

I'd like more examples of corner cases if you know of a list.  Real-world election ballot lists would be good, too.

Thanks for the link, I think this will be very useful. I just added a PR with the basic unittest framework. Our STAR implementation is pretty basic at the moment, no ties or anything, so I'm interested in reading through what you've done. There's some tie breaker documentation here and we have some javascript implementations here

These tiebreakers get confusing fast.  If you try to write out tests for every possible scenario, the scenarios keep branching off with ties within ties within ties.  For example:

A=2, B=1, C=0
A=1, B=0, C=1

Totals are A=3, B=1, C=1, so A is a finalist, but B and C are tied.
So find pairwise winner between B and C.  1 voter prefers B>C, one prefers C>B, so they're tied, no pairwise winner.
"If needed you can also compare them each head-to-head against the highest scoring candidate."  So if 2 voters prefer A>B, while 1 prefers A>C, then C goes to the runoff?  (And then A wins.)

A=2, B=1, C=0, D=0
A=1, B=0, C=1, D=0
A=1, B=0, C=0, D=1

Totals are A=4, B=1, C=1, D=1, so A is a finalist, but B, C, D are tied.
So try to find pairwise winner between B, C, and D.  There is none, it's a tie.
So compare with highest scoring candidate.
3 A>B
2 A>C
2 A>D
So C and D are tied?  Pick one randomly for the runoff?  (Then A wins regardless.)

The link above should cover these scenarios. In your second case with a multi candidate tie, A is the Condorcet winner and C and D tie for runner up. I don't think there's a need to break the tie further. In other cases with true ties it's ok to just report that the result is a tie.

But the instructions say "Take each candidate and compare them head-to-head with the others in the tie."  So it doesn't matter that A is Condorcet winner for deciding the 2nd candidate who goes to the runoff.  It needs to select one of them, if only to display who it was.

OK I made a big table and found there are 12 possible scenarios with the "minimum tiebreaker" method, and made a test case for each (rows are voters, columns are candidates A B C, numbers are scores)

One highest-scoring, one 2nd-highest. B preferred in runoff:

0	5
2	4

One highest-scoring, one 2nd-highest. Both tied in runoff, break tie using scores, B wins:

0	5
3	2

Two tied for highest-scoring, B wins in runoff:

0	2
1	2
4	1

Two tied for highest-scoring, tied in runoff, decide A or B randomly:

1	3
4	2

One highest-scoring, two or more tied for second-highest. One Condorcet winner among tied (C). One is preferred in runoff (A):

5	2	3
5	2	3
5	2	0

One highest-scoring, two or more tied for second-highest. One Condorcet winner among tied (C). Runoff is tied, highest-scoring A wins:

5	2	3
5	2	3
1	2	2
1	4	2

One highest-scoring, two or more tied for second-highest. No Condorcet winner among tied, break 2nd place randomly (B or C). One is preferred in runoff (A):

5	2	3
5	2	3
4	3	2
1	4	3

One highest-scoring, two or more tied for second-highest. No Condorcet winner among tied, break 2nd place randomly (B or C). Both are tied in runoff, highest-scoring wins (A).

5	2	3
5	2	3
1	3	2
1	4	3

Three or more tied for highest-scoring. One Condorcet winner and one 2nd-place Condorcet winner go to runoff. Condorcet winner wins (A):

2	1	0
2	1	0
2	1	0
2	1	0
1	0	0
0	0	4
0	5	5

Three or more tied for highest-scoring. Two tied for Condorcet winner (A and B), both go to runoff. True Tie, break randomly:

2	2	0
2	2	0
1	1	5

Three or more tied for highest-scoring. One Condorcet winner in tiebreaker and two or more tied for 2nd place CW. Break tie randomly (B or C).  Condorcet winner A wins runoff:

2	1	1
2	1	1
3	5	5

Three or more tied for highest-scoring. No Condorcet winner in tiebreaker, choose two randomly.  Neither wins runoff, choose winner randomly (A B or C):

5	5	5
2	2	2

This has been a rabbit hole that we've been working on for a while. There's a few people deep diving on different tie breaker protocol including the minimax algorithm specified in the site. We're currently looking into an even simpler protocol based on the Ranked Robin voting method. For this reason I'd caution against putting too much more work into this rabbit hole. In the meantime we've updated the instructions to just

Ties in the Runoff round should be broken in favor of the candidate who was scored higher if possible.
Ties in the Scoring round should be broken in favor of the candidate who was preferred head-to-head by more voters.
Ties which can not be broken as above are considered a "True Tie."

So in scenarios where there are multiple candidates who tie in the score round it will be labeled as a true tie and up to whoever is running the election to break it with their preferred tie breaking protocol. I'm hoping to get some of those protocols added to this repo so there are multiple options available.

Wrote this in the slack but I'll copy it here. The 'simple' scenarios (i.e. 1, 2, 3, 4, or the unlisted scenario of one highest score, exactly two tied for second, with one preferred over the other) are already going to be rare, and the resolutions @mikefranze put above work great.
Any of the other scenarios ("True Tie") would be so astronomically rare I don't think it's worth any of the added complexity to specify other protocols like Ranked Robin or 'Minimax' etc. etc. Even just introducing the concept of a Condorcet winner feels like an avoidable cognitive burden for voters. I agree that in general it is nice to elect a Condorcet winner, but in this kind of edge case I really don't think it matters.
If it is necessary to specify exactly what to do in the case of a "True Tie," I would strongly recommend something more straightforward. Here are some examples:

Break tie in favor of candidate with most scores of 5.
Break tie in favor of candidate with most scores of 3+
Break tie in favor of candidate with fewest scores of 0

And so on.

Wrote this in the slack but I'll copy it here. The 'simple' scenarios (i.e. 1, 2, 3, 4, or the unlisted scenario of one highest score, exactly two tied for second, with one preferred over the other) are already going to be rare, and the resolutions @mikefranze put above work great.
Any of the other scenarios ("True Tie") would be so astronomically rare I don't think it's worth any of the added complexity to specify other protocols like Ranked Robin or 'Minimax' etc. etc. Even just introducing the concept of a Condorcet winner feels like an avoidable cognitive burden for voters. I agree that in general it is nice to elect a Condorcet winner, but in this kind of edge case I really don't think it matters.
If it is necessary to specify exactly what to do in the case of a "True Tie," I would strongly recommend something more straightforward. Here are some examples:

Break tie in favor of candidate with most scores of 5.
Break tie in favor of candidate with most scores of 3+
Break tie in favor of candidate with fewest scores of 0

And so on.

For this reason I'd caution against putting too much more work into this rabbit hole. In the meantime we've updated the instructions to just
1. Ties in the Runoff round should be broken in favor of the candidate who was scored higher if possible.

2. Ties in the Scoring round should be broken in favor of the candidate who was preferred head-to-head by more voters.

3. Ties which can not be broken as above are considered a "True Tie."

This is still the same scenarios I've described above, no?  Or are three-way ties not included in "ties"?

one highest score, exactly two tied for second, with one preferred over the other

That's numbers 5 and 6
Simplicity is nice.  I still haven't finished my STAR implementation because of handling the "three or more tied for highest-scoring" cases.

Sorry for all the questions, I'm just trying to make sure my implementation is 100% correct.

Ties in the Scoring Round should be broken in favor of the candidate who was preferred head-to-head by more voters.

So in this 3-voter, 4-candidate scenario
 	A	B	C	D
1	5	2	4	4
2	4	5	2	2
3	2	4	5	5

What would the "minimal tiebreaker" do?  This is considered a "True Tie" because there is no Condorcet winner, so choose between A, B, C, D randomly?  (Even though A wins more matchups over the alternatives?)
And in this
    Allison, Bill, Carmen, Doug = 0, 1, 2, 3
    election = [[5, 4, 1, 4],
                [5, 4, 1, 4],
                [2, 4, 1, 2],
                [4, 3, 2, 1],
                [0, 5, 4, 4],
                [3, 2, 4, 2],
                [3, 1, 5, 3],
                [3, 1, 5, 3],
                [1, 3, 2, 2],
                [4, 3, 5, 5]]

All candidates get the same score, and there is no Condorcet winner, but you still need to identify the Smith Set(?) and choose randomly from within that set {A, B, C} because they all beat D pairwise?  (Which is non-trivial?)


No Internet Access

The script ran flawlessly on my Ubuntu-MATE Raspberry Pi 3 Model B.  I was able to copy over the configuration files and connect to the VPN from my home network.  I can access resources on the LAN through the VPN, SSH-ing into the Pi by IP and pinging my router by IP.  But I have no Internet access through the VPN at all.
The only problem I can see in startup logs is the following two lines:
2016-05-08 21:31:48 /sbin/route add -net <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>
route: writing to routing socket: File exists
add net <IP_ADDRESS>: gateway <IP_ADDRESS>: File exists
2016-05-08 21:31:48 /sbin/route add -net <IP_ADDRESS> <IP_ADDRESS> <IP_ADDRESS>
route: writing to routing socket: File exists
add net <IP_ADDRESS>: gateway <IP_ADDRESS>: File exists
<IP_ADDRESS>/24 is my LAN subnet.  Any ideas?

never tested on ubuntu mate.  did the installer think you were ubuntu or raspberry pi?
if you run these commands
#!/bin/bash
iptables -t filter -F
iptables -t nat -F
iptables -A FORWARD -m state –state RELATED,ESTABLISHED -j ACCEPT
iptables -A FORWARD -s “<IP_ADDRESS>/24” -j ACCEPT
iptables -A FORWARD -j REJECT
iptables -t nat -A POSTROUTING -s “<IP_ADDRESS>/24” -j MASQUERADE

or paste them into a script you run does it work?

Well, it's pretty much a standard Ubuntu 16.04 with the MATE desktop instead of Unity.
I tried running those commands, but they cause the Pi to lose all connectivity.  I have to unplug and replug to restart it.
Here are my routing tables (slightly obscured) as they stand:
Server:
Kernel IP routing table
Destination     Gateway         Genmask         Flags Metric Ref    Use Iface
default         router.mydomain <IP_ADDRESS>         UG    100    0        0 enxb827eb684aa8
<IP_ADDRESS>        <IP_ADDRESS>        <IP_ADDRESS>   UG    0      0        0 tun0
<IP_ADDRESS>        *               <IP_ADDRESS> UH    0      0        0 tun0
link-local      *               <IP_ADDRESS>     U     1000   0        0 tun0
<IP_ADDRESS>    *               <IP_ADDRESS>   U     100    0        0 enxb827eb684aa8

Client (without VPN)
Internet:
Destination        Gateway            Flags        Refs      Use   Netif Expire
default            openrg.home        UGSc          110        0     en1
127                localhost          UCS             0        0     lo0
localhost          localhost          UH              7    14717     lo0
169.254            link#4             UCS             0        0     en1
192.168.69         link#4             UCS             4        0     en1
openrg.home        90:72:82:43:63:e1  UHLWIi        119      365     en1   1193
iphone.home        50:7a:55:d3:1c:64  UHLWIi          0        0     en1    964
new-host.home      localhost          UHS             0        0     lo0
rpi.home           b8:27:eb:68:4a:a8  UHLWIi          1      351     en1    174

Client (with VPN):
Internet:
Destination        Gateway            Flags        Refs      Use   Netif Expire
0/1                <IP_ADDRESS>           UGSc            5        0   utun1
default            <IP_ADDRESS>       UGSc           18        0     en1
10.8/24            <IP_ADDRESS>           UGSc            0        0   utun1
<IP_ADDRESS>/32        <IP_ADDRESS>           UGSc            0        0   utun1
<IP_ADDRESS>           <IP_ADDRESS>           UH             14        0   utun1
24.188.abc.def/32  <IP_ADDRESS>       UGSc            1        0     en1
127                localhost          UCS             0        0     lo0
localhost          localhost          UH              9    15319     lo0
128.0/1            <IP_ADDRESS>           UGSc            5        0   utun1
169.254            link#4             UCS             0        0     en1
192.168.69         link#4             UCS             3        0     en1
<IP_ADDRESS>       90:72:82:43:63:e1  UHLWIi          2      390     en1    871
<IP_ADDRESS>       50:7a:55:d3:1c:64  UHLWIi          0        0     en1    468
<IP_ADDRESS>       localhost          UHS             1        0     lo0
<IP_ADDRESS>     b8:27:eb:68:4a:a8  UHLWIi          1      351     en1

Note that DNS is not working with the VPN connected.

you probably ran the first or second command and lost connectivity.  paste all that into a file like iptables.sh, make it executable, chmod +x iptables.sh then as root execute it with ./iptables.sh
or run them all locally with local keyboard and mouse.  it'll be something with iptables, not the routes, they get built by the tunnel.

Yeah, I ran it in a script.  Had to change -state to --state.  When I run the script I do lose my SSH connection...but I also can no longer connect the VPN (which connects fine before I run the script).  I'll try a couple of other things and report back.

Yeah, I ran it as a script. Had to correct -state to --state.  After running it, I not only lose my current SSH connection but can no longer connect the VPN or even ping the server either from the LAN or over the Internet.

Let me see the output of iptables -L and iptables -t nat -L
also is this ubuntu 16.04? which one?

oh and one more
ufw status
show me what that says.

I'll definitely report back with that info when I can.  I'm at work now, though, and since testing the script I can no longer SSH into the Pi, so it'll have to wait for this evening.   Custom
# rules should be added to one of these chains:
#   ufw-before-input
#   ufw-before-output
#   ufw-before-forward
#

# START OPENVPN RULES
# NAT table rules
*nat
:POSTROUTING ACCEPT [0:0]
# Allow traffic from OpenVPN client to eth0
-A POSTROUTING -s <IP_ADDRESS>/8 -o eth0 -j MASQUERADE
COMMIT
# END OPENVPN RULES

# Don't delete these required lines, otherwise there will be errors
*filter
. . .

Then edit this file: sudo nano /etc/default/ufw
Look for the DEFAULT_FORWARD_POLICY
and change it to:
DEFAULT_FORWARD_POLICY="ACCEPT"
it could be at DROP.
then do
ufw disable
ufw enable

to stop and start it to apply your changes above.  Try VPN again.

I had tried that exact section once before and it hadn't worked.  But while testing it again (it still didn't work) I realized something else: for some unknown reason, my ethernet interface is [i]not[/i] called eth0 but enxb827eb684aa8.  I replaced eth0 with enxb827eb684aa8 and it works flawlessly!  I'm posting this through my newly functional VPN!
So, for anyone else experiencing a problem with Ubuntu-MATE 16.04 LTS, please check your interface name with ifconfig.

oops, i saw your interface was named that but forgot to change when pasting in.  Once I support ubuntu 16.04 I suspect this will work the same.

if you see this and have a moment can you send me the output of:
lsb_release -a

No problem:
No LSB modules are available.
Distributor ID:	Ubuntu
Description:	Ubuntu 16.04 LTS
Release:	16.04
Codename:	xenial

You can get more info on the release here.  It works very smoothly at least on my 3B.  I chose it over Raspbian because I was more familiar with Ubuntu and Gnome.
By the way, everything's working fine on my VPN.  Took a little figuring to get dnsmasq working, but after that it's been smooth sailing.  Works perfectly on my iPhone, too.

so this isn't a 16.04 ubuntu thing.  normal ubuntu 16.04 doesn't come with ufw enabled and would use normal iptables.  This must be a MATE packaging statement for this ubuntu.  What i can maybe do is detect if ufw is enabled, if it is, i'll try to insert the commands here instead of the iptables.

Commit 5d9580fbdda9e1a3200bdddc1d3b484f19a76021


host fails on 18.03

Issue description
Since upgrading to 18.03, I get the following error when I try to use the host command:
host: parse of /etc/resolv.conf failed`

My /etc/resolv.conf is as follows:
# Generated by resolvconf
nameserver <IP_ADDRESS>
nameserver fe80::xxxx:xxff:feyy:yyyy%wlp4s0
options edns0

EDITED by vcunat hide the mac address (xxxxxxyyyyyy)
/etc/resolvconf.conf is:
# This is the default, but we must set it here to prevent
# a collision with an apparently unrelated environment
# variable with the same name exported by dhcpcd.
interface_order='lo lo[0-9]*'
# Invalidate the nscd cache whenever resolv.conf is
# regenerated.
libc_restart='/nix/store/46nrl6ycwc140iqjrmk09wbnanj59nh5-systemd-238/bin/systemctl try-restart --no-block nscd.service 2> /dev/null'
# Options as described in resolv.conf(5)
resolv_conf_options='edns0'

Relevant lines from my configuration.nix:
  networking.networkmanager.enable = true;
  networking.enableIPv6 = false;

(The issue is the same with networking.enableIPv6 set to false.) My full configuration is here.
Steps to reproduce
host -t a google.com
Technical details

system: "x86_64-linux"
host os: Linux 4.14.29, NixOS, 18.03pre131587.b6ddb9913f2 (Impala)
multi-user?: yes
sandbox: no
version: nix-env (Nix) 2.0
channels(shosti): ""
channels(root): "nixos-18.03pre131587.b6ddb9913f2"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos/nixpkgs

Hmm.  At first this looked like a format string leaked into the configure file, but looking into it I think this is "correct" and is used to indicate "zone"s.
Can you:

Post result of host -V and perhaps readlink -f $(which host)?
Confirm behavior using 18.03's "host" with nix run -f channel:nixos-18.03 host -c host -t a google.com?
See if the newer bind (which provides host) resolves the issue? Changelog looks promising, considering it's only a minor version bump: nix run -f channel:nixos-unstable host -c host -t a google.com

Same here on master
$ git rev-parse HEAD
0426d9001fbb1ecd7552aaaeebccb84ea8483fb9
$ nix run -f $HOME/nixpkgs host -c host -t a google.com
host: parse of /etc/resolv.conf failed
$ nix run -f $HOME/nixpkgs host -c host -V
host 9.12.1
$ more /etc/resolv.conf
# Generated by resolvconf [address details removed]
nameserver 192.168.x.x
nameserver fe80::xxxx:xxff:fexx:xxxx%enp1s0f0
options edns0

@dtzWill :
[shosti@drogo:~]$ host -V
host 9.12.0

[shosti@drogo:~]$ readlink -f $(which host)
/nix/store/4r5nqfpj0isp7g9f3dxz83kxn07485yy-bind-9.12.0-host/bin/host

[shosti@drogo:~]$ nix run -f channel:nixos-18.03 host -c host -t a google.com
[10.3 MiB DL]
host: parse of /etc/resolv.conf failed

[shosti@drogo:~]$ nix run -f channel:nixos-unstable host -c host -t a google.com
[6 copied (28.9 MiB), 18.6 MiB DL]
host: parse of /etc/resolv.conf failed

Thanks!
Looks like it's this: https://gitlab.isc.org/isc-projects/bind9/issues/187
Which has a few solid leads.. :)

I'm not sure what to make of this, but I'm.... having trouble convincing host to barf on /etc/resolv.conf -- even when I replace mind with yours and bounce nscd.  Worst that happens is it hangs  (when I remove the other, valid, nameserver entries).
Oh! "Hooray!" haha, I can trigger it if I use nameserver entries like yours (with "%interface" suffix) and remove "search lan".
Furthermore I'll add that using host from 17.09 and 17.03 does not have the same error.

FWIW the drill command from ldns seems to have no problem with these resolv.conf files, if you need something to use right now.  Arch apparently moved to using that for their dns CLI needs a while back: https://www.archlinux.org/todo/dnsutils-to-ldns-migration .

I use drill and it seems to work fine on 18.03 and master.
As for host, we could also try to apply the patch mentioned in the upstream bug: https://gitlab.isc.org/isc-projects/bind9/commit/e50849097a05ee3fc9e7357d4e238540cb076d22 .
Or use ldns ...

I don't think there's much to do except to apply upstream patches for host (when available).  Most software should handle link-local addresses correctly.

We should label such issues "waiting for upstream solution" to keep track of them but I don't think we currently have such a label.

Created the label.  We can easily delete/change it later in case there's such consensus.

host seems to work fine on 20.03, can we close this? Thanks!

Yes, it seems long fixed in versions we use.  Even our 19.09 is using bind 14.


Welcome to 2022

The same procedure as last year, Miss Sophie?
Same procedure as every year, James.

who is make
znc management script xD 2k22

who is make
znc management script xD 2k22


Adding MT903345 as mpx reference genome

Our lab has been using MT903345.1 as reference genome (https://www.medrxiv.org/content/10.1101/2<IP_ADDRESS>80783v1.full) using older version of Cecret (v.3.4.20221121). The mpx_primalseq config now uses NC_063383.1. Is it necessary to set up a new profile using  MT903345.1?

The bedfile coordinates have to match the reference sequence otherwise ivar trim or samtools ampliconclip can't figure out where the primers are.
Do you have a copy of the bedfile that you could share with me?

TX-DSHS_Mpx_bed.zip
I have attached the reference fasta and bed files we are using. Thank you!

I DID NOT forget about this.
It's just that testing this takes a really long time.
I have added in new primer schemes that I have labeled mpx_yale into the latest updates that are currently going through testing.
If all goes well, this should get released by the end of the day. /fingerscrossed
To use these primers, you would set the params.primer_set = "mpx_yale" and params.species = "mpx" OR add mpx_yale to your profiles.
What command do you normally use? I can convert that to use these new values.

Thank you so much for working on this! The command I normally used is:
nextflow run UPHL-BioNGS/Cecret --reads <input_path> --outdir <output_path> -profile singularity,mpx_primalseq

The new release is out!!!
I've named the profile that uses these primers the 'mpx_yale' profile. You should be able to run what you normally ran by updating the profile from mpx_primalseq to mpx_yale.
nextflow run UPHL-BioNGS/Cecret --reads <input_path> --outdir <output_path> -profile singularity,mpx_yale

Sweet! I'll test it on our dataset. Appreciate it!


How to translate into other languages?

May I know which file I should modify, please?

we dont have any localization support atm nor is it planned to be added anytime soon


Error when forking. release-please failed: Resource not accessible by integration

Run google-github-actions/release-please-action@v3
✔ Looking for latest release on branch: master with prefix:
❯ Fetching merge commits on branch master with cursor: undefined
❯ Fetching releases with cursor undefined
⚠ Could not find releases.
❯ found 0 possible releases. []
❯ found 0 possible tags. []
✔ Building releases
✔ Building strategies by path
❯ .: simple
✔ Looking for latest release on branch: master with prefix:
❯ Fetching merge commits on branch master with cursor: undefined
❯ Fetching releases with cursor undefined
⚠ Could not find releases.
❯ found 0 possible releases. []
❯ found 0 possible tags. []
✔ Building pull requests
✔ Building strategies by path
❯ .: simple
✔ Collecting release commit SHAs
❯ release search depth: 400
❯ Fetching releases with cursor undefined
⚠ Could not find releases.
⚠ Expected 1 releases, only found 0
⚠ Missing 1 paths: .
✔ Collecting commits since all latest releases
⚠ No version for path .
⚠ Expected 1 releases, only found 0
❯ commit search depth: 500
❯ Set(0) {}
❯ Fetching merge commits on branch master with cursor: undefined
❯ Backfilling file list for commit: ea72bb32463f443e9d3f5c377b471b5e8d2d9be1
❯ Found 1 files
❯ Backfilling file list for commit: 6bd745[16](https://github.com/remarkablemark/release-please-action-fork-demo/actions/runs/4846345396/jobs/8635830737#step:2:17)a97dc54cc4544e908397b5423ddd2cdd
❯ Found 1 files
❯ Backfilling file list for commit: 3032501dd82e4b0bcad6b6e9fb27cb2a0cc19967
❯ Found 1 files
❯ Backfilling file list for commit: 78e71192efaa447d27be82ebd56e2e[18](https://github.com/remarkablemark/release-please-action-fork-demo/actions/runs/4846345396/jobs/8635830737#step:2:19)f8ee0f90
❯ Found 1 files
❯ Backfilling file list for commit: 042[19](https://github.com/remarkablemark/release-please-action-fork-demo/actions/runs/4846345396/jobs/8635830737#step:2:20)c3d488aed030ba3fdc9[21](https://github.com/remarkablemark/release-please-action-fork-demo/actions/runs/4846345396/jobs/8635830737#step:2:22)d10dd391976079
❯ Found 2 files
✔ Splitting 5 commits by path
✔ Building candidate release pull request for path: .
❯ type: simple
⚠ No latest release pull request found.
❯ targetBranch: master
❯ commit could not be parsed: 04219c3d488aed0[30](https://github.com/remarkablemark/release-please-action-fork-demo/actions/runs/4846345396/jobs/8635830737#step:2:31)ba3fdc921d10dd[39](https://github.com/remarkablemark/release-please-action-fork-demo/actions/runs/4846345396/jobs/8635830737#step:2:40)1976079 Initial commit
❯ commits: 4
✔ Considering: 4 commits
❯ component:
❯ pull request title pattern: undefined
✔ Looking for open release pull requests
✔ found 0 open release pull requests.
✔ Looking for snoozed release pull requests
✔ found 0 snoozed release pull requests.
❯ Fetching CHANGELOG.md from branch master
❯ Fetching version.txt from branch master
❯ Fetching .release-please-manifest.json from branch master
⚠ file .release-please-manifest.json did not exist
✔ Starting GitHub PR workflow...
✖ Error when forking
Error: release-please failed: Resource not accessible by integration

See https://github.com/google-github-actions/release-please-action/issues/768


Add an integration workflow

Similar to tfe-run, we can set up an 'integration workflow'. This workflow should run regularly to verify the integration with the Terraform Cloud API.
We can refer to how this is set up in tfe-run:

.github/workflows/integration.yaml
Actions: Integration

Done. See:

https://github.com/kvrhdn/go-tfe-run/blob/main/integration_test.go
https://github.com/kvrhdn/go-tfe-run/blob/main/.github/workflows/integration.yaml


Update MD file on new branch 2017-11-09_15-26-48

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

split/content1.md
:white_check_mark:Succeeded

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


Update tests/test_examples.py for AWS team

As per title.

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.