Deploy UCSD Scan 1.0.2

ITS-Pro time tracking: https://its-pro.ucsd.edu/projects/MA/issues/MA-31?filter=allopenissues
This is complete when:

[x] v1.0.2 has gone through regression testing
[x] v1.0.2 is awaiting App Store review
[ ] v1.0.2 has been approved by Apple for store release
[ ] v1.0.2 has been deployed to the App Store

Update
1.0.2 rejected by Apple Review citing the need for a SSO account login to fully review the app.
Next Steps

[ ] Update demo video showing barcode submission success, failure, duplicate
[ ] Appeal the decision using verbiage from Campus Mobile app submissions and updated demo video

Holding off on this enhancement update. Native scanner on the campus mobile app has reduced the need of the iPads.


style(prettier integrasion): added prettier and import plugin to eslint and applied code style

In starters, the base app added a prettier integration. This is huge development satisfaction if the fix is
applied on  IDE save
What is it?

[x] Feature / enhancement
[ ] Bug
[ ] Docs / tests

Description
These are opinionated changes.
Use cases and why

As a developer, I would like to have consistency regarding code style

It is not easy to properly setup eslint with code style to work together

Checklist:

[ ] My code follows the developer guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have made corresponding changes to the documentation
[ ] Added new tests to cover the fix / functionality

@FDiskas Thanks for your great help. This PR has few conflicts and it's old, the best way to proceed is to open a new fresh PR so I close this one. feel free to open a new one if you would like to work on it.


Statistics tables look empty

Since a while we're using django-trackstats for collecting metrics
without using a third-party service like Google. However, this is no longer working with version 0.92.0,
the metric tables are empty .. don't know why yet. The tests concerning the metrics have passed.
Maybe this is related to the high age of django-trackstats?!

However, I have just tested the statistics export and it is working,
also the old data is still there. When looking into the PG tables, they look empty, not sure why.

The statistics table hasn't been mailed out in a long time and appears broken.

I've disabled trackstats entirely as the module appears to be a major source of delays in delivering response. Essentially, every request to deliver data from the database also entails a write which appears to make things slow.


Fix incorrect stream/5 typespec

Hello!
I was using stream/5 in a project today and noticed that the typespec appears to be incorrect. Currently stream/5's spec says it's return type is acc. However, when using stream/5 it returned {:ok, acc} instead. This appears to be confirmed in existing Finch tests for stream/5.
This PR updates the stream/5 typespec to be {:ok, acc}. If I've missed something, please feel free to decline this PR and let me know!

Thanks @Jwsonic! This looks good to me. I'll work on getting this merged soon.

Thanks @Jwsonic! This looks good to me. I'll work on getting this merged soon.


Watchlist-CloseIncidentKnownIPs  Playbook - bug & guidance needed

Line 194 of the Watchlist-CloseIncidentKnownIPs playbook has a hardcoded 'safeips'  - this needs to be the alias of the imported Watchlist.
Adding guidance for the permissions required by the Logic App steps would be beneficial:
The permissions required in 'For Each' of the logic app need to be Log Analytics Reader at a minimum.
The permissions required in the 'Add comment to incident' of the log app, well its unclear - Log Analytics Contributor was insufficient, when provided with  Subscription Contributor it works.
Same is true for the "Update incident" under the  Condition step.
Hope this helps
Mark
<EMAIL_ADDRESS>

The issue in the arm template and the readme are now updated in #3215 to address this issue.
Thanks for sharing!


Support design metadata emitting for new ES decorators

Acknowledgement

[X] I acknowledge that issues using this template may be closed without further explanation at the maintainer's discretion.

Comment
This can be probably classified as bug, but also partially as new feauture.
With legacy typescript decorators "design" metadata (e.g. design:returntype, design:paramtypes) were added to the emitted Javascript, when options experimentalDecorators and emitDecoratorMetadata were enabled. With the recent support of ES-style decorators (see tc39 proposal) the same metadata are missing.
Option emitDecoratorMetadata cannot be enabled, when experimentalDecorators are disabled, but experimentalDecorators supress the behaviour of ES decorators and thus not allowing for metadata to be created for them (see example in playground).
Possible solutions

add design metadata to DecoratorContext.metadata object
allow emitting of metadata without experimentalDecorators option

Duplicate of #57533 and #55788. Used search terms: metadata in:title


Add missing Python 3.11 dependencies.

Add two dependencies that were previously excluded for Python 3.11.
Modify the scripts to install python-snappy linux headers so that dependencies can be regenerated.

fixes: https://github.com/apache/beam/issues/25985

let's decouple snappy upgrade from googlecloudprofiler, sending: https://github.com/apache/beam/pull/29651


[New Feature ]l oad_image_file - Expected new feature to load_image_base64

face_recognition version: latest
Python version: 3.8
Operating System: MACOS

Description
Thanks to developer effort, this lib lot more easy compre to other lib.
I expected additional feature like load_image_base64. so we can load image from base64 data.

Hi there, alternatively you can convert the base64 image to a binary format which you can save to a file and read from that file using the standard load_image_file method provided in face_recognition.
Hope this helps.

code?


Error running check disk: No such file or directory: '/host/proc/self

Running the datadog agent container on Docker for Windows with the WSL2 backend, I get an error that /host/proc/self is not found.
I am using docker-compose, with the following config:
  datadog:
    image: datadog/agent:7
    hostname: ${HOSTNAME}
    network_mode: "host"
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock:ro
      - /proc/:/host/proc/:ro
      - /etc/passwd:/etc/passwd:ro
      - /sys/fs/cgroup/:/host/sys/fs/cgroup:ro
    environment:
      - DD_API_KEY=${DATADOG_KEY}
      - DD_SITE=datadoghq.com
      - DD_PROCESS_AGENT_ENABLED=true

Describe what happened:
Error running check disk: [{"message": "[Errno 2] No such file or directory: '/host/proc/self'", "traceback": "Traceback (most recent call last):\n  File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/checks/base.py\", line 863, in run\n    self.check(instance)\n  File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/disk/disk.py\", line 109, in check\n    for part in psutil.disk_partitions(all=self._include_all_devices):\n  File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/psutil/__init__.py\", line 2027, in disk_partitions\n    return _psplatform.disk_partitions(all)\n  File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/psutil/_pslinux.py\", line 1167, in disk_partitions\n    mounts_path = os.path.realpath(\"%s/self/mounts\" % procfs_path)\n  File \"/opt/datadog-agent/embedded/lib/python3.8/posixpath.py\", line 391, in realpath\n    path, ok = _joinrealpath(filename[:0], filename, {})\n  File \"/opt/datadog-agent/embedded/lib/python3.8/posixpath.py\", line 439, in _joinrealpath\n    path, ok = _joinrealpath(path, os.readlink(newpath), seen)\nFileNotFoundError: [Errno 2] No such file or directory: '/host/proc/self'\n"}]

Describe what you expected:
No error
Steps to reproduce the issue:
setup docker agent as above
Additional environment details (Operating System, Cloud provider, etc):
This is Windows 10 (Home, if that matters), WSL2, Docker for Desktop and Ubuntu 20.04
I belief the issue appears similar to this bug but I don't think they are related.
The agent status report is:
===============
Agent (v7.24.0)
===============

  Status date: 2020-12-16 22:22:38.284207 UTC
  Agent start: 2020-12-16 21:53:14.244158 UTC
  Pid: 388
  Go Version: go1.14.7
  Python Version: 3.8.5
  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: 3.604616s
    System UTC time: 2020-12-16 22:22:38.284207 UTC

  Host Info
  =========
    bootTime: 2020-12-12 18:15:40.000000 UTC
    kernelArch: x86_64
    kernelVersion: 4.19.128-microsoft-standard
    os: linux
    platform: debian
    platformFamily: debian
    platformVersion: bullseye/sid
    procs: 23
    uptime: 99h37m39s

  Hostnames
  =========
    hostname: docker-desktop
    socket-fqdn: docker-desktop
    socket-hostname: docker-desktop
    hostname provider: container
    unused hostname providers:
      aws: not retrieving hostname from AWS: the host is not an ECS instance and other providers already retrieve non-default hostnames
      configuration/environment: hostname is empty
      gce: unable to retrieve hostname from GCE: Get "http://<IP_ADDRESS>/computeMetadata/v1/instance/hostname": dial tcp <IP_ADDRESS>:80: connect: connection refused

  Metadata
  ========
    hostname_source: container

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

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

    cpu
    ---
      Instance ID: cpu [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/cpu.d/conf.yaml.default
      Total Runs: 118
      Metric Samples: Last Run: 7, Total: 820
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2020-12-16 22:22:33.000000 UTC
      Last Successful Execution Date : 2020-12-16 22:22:33.000000 UTC

    disk (4.0.0)
    ------------
      Instance ID: disk:e5dffb8bef24336f [ERROR]
      Configuration Source: file:/etc/datadog-agent/conf.d/disk.d/conf.yaml.default
      Total Runs: 117
      Metric Samples: Last Run: 0, Total: 0
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 3ms
      Last Execution Date : 2020-12-16 22:22:25.000000 UTC
      Last Successful Execution Date : Never
      Error: [Errno 2] No such file or directory: '/host/proc/self'
      Traceback (most recent call last):
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/checks/base.py", line 863, in run
          self.check(instance)
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/disk/disk.py", line 109, in check
          for part in psutil.disk_partitions(all=self._include_all_devices):
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/psutil/__init__.py", line 2027, in disk_partitions
          return _psplatform.disk_partitions(all)
        File "/opt/datadog-agent/embedded/lib/python3.8/site-packages/psutil/_pslinux.py", line 1167, in disk_partitions
          mounts_path = os.path.realpath("%s/self/mounts" % procfs_path)
        File "/opt/datadog-agent/embedded/lib/python3.8/posixpath.py", line 391, in realpath
          path, ok = _joinrealpath(filename[:0], filename, {})
        File "/opt/datadog-agent/embedded/lib/python3.8/posixpath.py", line 439, in _joinrealpath
          path, ok = _joinrealpath(path, os.readlink(newpath), seen)
      FileNotFoundError: [Errno 2] No such file or directory: '/host/proc/self'

    docker
    ------
      Instance ID: docker [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/docker.d/conf.yaml.default
      Total Runs: 117
      Metric Samples: Last Run: 10, Total: 1,170
      Events: Last Run: 0, Total: 5
      Service Checks: Last Run: 1, Total: 117
      Average Execution Time : 4ms
      Last Execution Date : 2020-12-16 22:22:32.000000 UTC
      Last Successful Execution Date : 2020-12-16 22:22:32.000000 UTC

    file_handle
    -----------
      Instance ID: file_handle [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/file_handle.d/conf.yaml.default
      Total Runs: 117
      Metric Samples: Last Run: 5, Total: 585
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2020-12-16 22:22:24.000000 UTC
      Last Successful Execution Date : 2020-12-16 22:22:24.000000 UTC

    io
    --
      Instance ID: io [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/io.d/conf.yaml.default
      Total Runs: 117
      Metric Samples: Last Run: 78, Total: 9,072
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2020-12-16 22:22:31.000000 UTC
      Last Successful Execution Date : 2020-12-16 22:22:31.000000 UTC

    load
    ----
      Instance ID: load [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/load.d/conf.yaml.default
      Total Runs: 117
      Metric Samples: Last Run: 6, Total: 702
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2020-12-16 22:22:23.000000 UTC
      Last Successful Execution Date : 2020-12-16 22:22:23.000000 UTC

    memory
    ------
      Instance ID: memory [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/memory.d/conf.yaml.default
      Total Runs: 117
      Metric Samples: Last Run: 18, Total: 2,106
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2020-12-16 22:22:30.000000 UTC
      Last Successful Execution Date : 2020-12-16 22:22:30.000000 UTC

    network (1.19.0)
    ----------------
      Instance ID: network:5c571333f400457d [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/network.d/conf.yaml.default
      Total Runs: 118
      Metric Samples: Last Run: 31, Total: 3,658
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 1ms
      Last Execution Date : 2020-12-16 22:22:37.000000 UTC
      Last Successful Execution Date : 2020-12-16 22:22:37.000000 UTC

    ntp
    ---
      Instance ID: ntp:d884b5186b651429 [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/ntp.d/conf.yaml.default
      Total Runs: 2
      Metric Samples: Last Run: 1, Total: 2
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 1, Total: 2
      Average Execution Time : 275ms
      Last Execution Date : 2020-12-16 22:08:19.000000 UTC
      Last Successful Execution Date : 2020-12-16 22:08:19.000000 UTC

    uptime
    ------
      Instance ID: uptime [OK]
      Configuration Source: file:/etc/datadog-agent/conf.d/uptime.d/conf.yaml.default
      Total Runs: 117
      Metric Samples: Last Run: 1, Total: 117
      Events: Last Run: 0, Total: 0
      Service Checks: Last Run: 0, Total: 0
      Average Execution Time : 0s
      Last Execution Date : 2020-12-16 22:22:29.000000 UTC
      Last Successful Execution Date : 2020-12-16 22:22:29.000000 UTC

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

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

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

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

  Transactions
  ============
    Deployments: 0
    Dropped: 0
    DroppedOnInput: 0
    Nodes: 0
    Pods: 0
    ReplicaSets: 0
    Requeued: 0
    Retried: 0
    RetryQueueSize: 0
    Services: 0

  Transaction Successes
  =====================
    Total number: 248
    Successes By Endpoint:
      check_run_v1: 117
      intake: 14
      series_v1: 117

  API Keys status
  ===============
    API key ending with b65ec: API Key valid

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

==========
Logs Agent
==========

  Logs Agent is not running

=========
APM Agent
=========
  Status: Running
  Pid: 393
  Uptime: 1764 seconds
  Mem alloc: 32,904,032 bytes
  Hostname: docker-desktop
  Receiver: <IP_ADDRESS>:8126
  Endpoints:
    https://trace.agent.datadoghq.com

  Receiver (previous minute)
  ==========================
    No traces received in the previous minute.
    Default priority sampling rate: 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: 20,346
  Dogstatsd Metric Sample: 12,244
  Event: 6
  Events Flushed: 6
  Number Of Flushes: 117
  Series Flushed: 23,534
  Service Check: 1,176
  Service Checks Flushed: 1,287

=========
DogStatsD
=========
  Event Packets: 0
  Event Parse Errors: 0
  Metric Packets: 12,243
  Metric Parse Errors: 0
  Service Check Packets: 0
  Service Check Parse Errors: 0
  Udp Bytes: 892,508
  Udp Packet Reading Errors: 0
  Udp Packets: 1,180
  Uds Bytes: 0
  Uds Origin Detection Errors: 0
  Uds Packet Reading Errors: 0
  Uds Packets: 0```

I am also facing the same issue with the same exact setup, running docker on Windoes with WSL2 enabled. Any suggestion to fix the issue.
ddagent_1    | 2021-03-08 22:14:53 UTC | CORE | ERROR | (pkg/collector/runner/runner.go:292 in work) | Error running check disk: [{"message": "[Errno 2] No such file or directory: '/host/proc/self'", "traceback": "Traceback (most recent call last):\n  File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/base/checks/base.py\", line 901, in run\n    self.check(instance)\n  File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/datadog_checks/disk/disk.py\", line 115, in check\n    for part in psutil.disk_partitions(all=self._include_all_devices):\n  File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/psutil/__init__.py\", line 2027, in disk_partitions\n    return _psplatform.disk_partitions(all)\n  File \"/opt/datadog-agent/embedded/lib/python3.8/site-packages/psutil/_pslinux.py\", line 1167, in disk_partitions\n    mounts_path = os.path.realpath(\"%s/self/mounts\" % procfs_path)\n  File \"/opt/datadog-agent/embedded/lib/python3.8/posixpath.py\", line 391, in realpath\n    path, ok = _joinrealpath(filename[:0], filename, {})\n  File \"/opt/datadog-agent/embedded/lib/python3.8/posixpath.py\", line 439, in _joinrealpath\n    path, ok = _joinrealpath(path, os.readlink(newpath), seen)\nFileNotFoundError: [Errno 2] No such file or directory: '/host/proc/self'\n"}]


Cordova 6.1.0 version, ios build failed.

Hello, google-maps-plugin on Cordova 6.1.0 with iOS platform not working, i can't build app, see errors:
.../GoogleMaps.m:176:59: error: no known instance method for selector
'initWithWebView:'
.../GoogleMaps.m:245:68: error: no known instance method for selector
'initWithWebView:'
pluginClass = [[NSClassFromString(className)alloc] initWithWebView:self.webView];
.../GoogleMaps.m:321:19: error: no visible @interface for 'UIView' declares
the selector 'stringByEvaluatingJavaScriptFromString:'
[self.webView stringByEvaluatingJavaScriptFromString:jsString];
.../GoogleMapsViewController.m:10:9: fatal error: 'Cordova/CDVJSON.h' file
not found
P.S Adding "$(OBJROOT)/UninstalledProducts/$(PLATFORM_NAME)/include" in X-Code "Header search paths" not resolve problem.

Sorry, on the latest version of plugin, Cordova build is successful. Solution: You need use "cordova plugin add https://github.com/phonegap-googlemaps-plugin/cordova-plugin-googlemaps" instead of "cordova plugin add cordova-plugin-googlemaps".

@LucasNova It'd be great if this information was available a bit more front and center in the documentation. None of the samples currently work without adding the plugin in this manner on ios.


bug: Crash when reading an NFC Tag goes wrong on Android device

Plugin version:
"@capawesome-team/capacitor-nfc": "5.0.1"
Platform(s):
Android
Current behavior:
When reading an NFC tag by "brushing" the phone on the tag, sometimes the app fully crashes on Android
Expected behavior:
App should not crash when a tag reading goes wrong
Steps to reproduce:
Pass the phone on the NFC tag so the vibration of the "read" goes off when the phone isn't on the tag anymore
Related code:
Exception goes off on line 789 of "Bridge.java" file.
It is then caught on line 186 of "NfcPlugin.java", but in my case, on line 188 of "NfcPlugin.java", the "Log.e(TAG, message);" throws a NullPointerException, which isn't caught and makes the app crash.
I tested on my side, and just adding a null check on the message and sending a generic message instead resolves the issue
Other information:
Tested on a Samsung Galaxy A32 5G
Capacitor doctor:
Latest Dependencies:

  @capacitor/cli: 5.0.5
  @capacitor/core: 5.0.5
  @capacitor/android: 5.0.5
  @capacitor/ios: 5.0.5

Installed Dependencies:

  @capacitor/cli: 5.0.5
  @capacitor/android: 5.0.0
  @capacitor/core: 5.0.0
  @capacitor/ios: 5.0.0

Thank you for reporting this. I will publish a new version.

Unfortunately, I could not reproduce the issue. However, I have still added a null check. Please let me know if the problem persists.

I just tested the version and it doesn't crash anymore in this case, thank you !
This does seem device related and I wouldn't be surprised if Samsung's software layer changed the way Exceptions are built.


[Azure Stack] Updates to Azs.Update.Admin spec

Latest improvements:
MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Contribution checklist:

[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and have all been fixed in this PR.
[ ] The OpenAPI Hub was used for checking validation status and next steps.

ARM API Review Checklist

[ ] Service team MUST add the "WaitForARMFeedback" label if the management plane API changes fall into one of the below categories.
adding/removing APIs.
adding/removing properties.
adding/removing API-version.
adding a new service in Azure.

Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs.

[ ] If you are blocked on ARM review and want to get the PR merged urgently, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.
Please follow the link to find more details on API review process.

/azp run automation - sdk

Can one of the admins verify this patch?

/azp run

/azp run automation - sdk

@akning-ms, please force merge this PR since the case change on path is not a real breaking change. Add @jianyexi , we need to compare path case-insensitively in OAD tool.


[ISSUES-3063][Improve] Improve ImplicitsUtilsTest test code coverage

What changes were proposed in this pull request
Improve streampark-common module unit test

Brief change log

Verifying this change

This change added tests and can be verified as follows:

Does this pull request potentially affect one of the following parts

Dependencies (does it add or upgrade a dependency): (no)

@zzzk1 @wolfboys Hello, I think some negative tests should be added here, and I will submit a PR to improve it.


[CSPM] Cross-container scanning by detecting container root mountpoint

What does this PR do?
Executes cross-container scanning by detecting the root mountpoint of a namespaced process. To do so it find the mountpoint of the interested namespaced process by matching its overlay options with the mount entry in /proc/1/mountinfo.
Motivation
We could get rid of our system-probe module that executes our cross-container checks today.

Additional Notes

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge


Add multiple chat template

This PR adds support for models with multiple chat templates, such as Cohere Command R+, addressing issue https://github.com/EleutherAI/lm-evaluation-harness/issues/1962.
The command line API has been updated to reuse an existing flag to specify the template name, while preserving backward compatibility:
--apply_chat_template {template_name}

@haileyschoelkopf Let me know if anything needs updating! :)
cc @clefourrier @NathanHB

Thanks for the review @haileyschoelkopf! Let me know if anything else needs reworking!


Install Node.js

WHY
Sometimes Rails tests require Node.js environment
WHAT
Install Node.js in this box

LTGM!


Allow the filtering of cost reports by service

What
This allows you to go to /reports/cost/2019-03-01?service=blah and see
only the bills for that particular service.
The particular use case for this is to see how much we've billed for
elasticsearch.
It works in a pretty hacky way, using the query param as a substring to
search through all the plan names.
How to review

Code review
Run with stub api and visit localhost:3000/reports/cost/2019-03-01?service=wizarding-plan (or one of the other magical plans) and confirm that the bills change as expected

Who can review
Not @richardTowers

All working correctly locally


add 2 features: "ctrl+u" and "asynchronous completion"

add 2 features: "ctrl+u" and "asynchronous completion".
the former one is a convinience, while the latter is needed when completion is retrieved from the server asynchronously using ajax or websocket.

Cool!


Data API equivalent for HoloMaps

We've had the recent Data API PR merged for Chart elements and this issue suggests a similar thing could be implemented for HoloMaps and NdMappings.
The API is not quite the same as for charts as HoloMap is designed to be dictionary like. However, instead of always using ordered dictionaries as .data, you can imagine using pandas DataFrames instead. This could greatly improve the speed of certain operations (such as groupby) involving holomaps.

Note that the slow speed of groupby is the major driver here. I've just come up with an alternative implementation for the NdMapping groupby that temporarily converts to a DataFrame. Here's the performance profiling for a three-dimensional HoloMap grouped by two of the dimensions with both implementations:

I think until we find a way around this we should allow HoloMap to use this implementation when pandas is available.

Just some quick thoughts on this. Fundamentally the distinction between NdMapping and Columns types is in the way the data is indexed. NdMapping types are good for providing multi-dimensional indexing for dense chunks of data, e.g. Elements. Elements on the other hand hold dense chunks of data. Implementing a separate API for NdMapping types that can work using either the current OrderedDict based implementation or using pandas MultiIndexes therefore would make sense.
This second index based baseclass would also be useful for more powerful composite Element types, i.e. you could have a new Element baseclass where the data maps between multi dimensional keys and values that match the Columns data format, e.g. for a list of polygons for each country the data format would be {'Australia': {'x': xs, 'y': ys}, 'Austria': ...}. This would be very similar to what NdOverlay provides but without the need to nest the data and provide a much more optimized alternative for storing and plotting collections of artists.
This example from the pandas docs should make it clear what the data format is:
                     A         B         C
first second
bar   one     0.895717  0.410835 -1.413681
      two     0.805244  0.813850  1.607920
baz   one    -1.206412  0.132003  1.024180
      two     2.565646 -0.827317  0.569605
foo   one     1.431256 -0.076467  0.875906
      two     1.340309 -1.187678 -2.211372
qux   one    -1.170299  1.130127  0.974466
      two    -0.226169 -1.436737 -2.006747

Here first and second would be the dimensions mapping to the NdMapping style n-dimensional key and A, B and C the dimensions of the columns based format of the values in this new Element type. If we added support for this then we could leverage the general work to improve NdMapping proposed as part of this issue with the work on the data API to get a high-performance Element type for collections of data without some of the hacky workarounds (e.g. padding with delimiters) we discussed to improve the Paths and Polygons types.

I no longer think this is required now that I've optimized groupby with pandas and we are building out DynamicMap support, so I'm going to close this issue.


[BEAM-13159] Add Redis Stream (XADD) Write Support

This change adds support for writing PCollections of KV<String, Map<String,String>> to Redis Streams

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[X] Choose reviewer(s) and mention them in a comment (R: @username).
[X] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[X] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R:@jbonofre this is my first attempt and Java is definitely not my lingua franca, so any and all feedback would be appreciated. :)

fry_squint.jpg at the java precommit test failure -- I don't think that's related to my change?

10:37:44       > Could not resolve org.pentaho:pentaho-aggdesigner-algorithm:5.1.5-jhyde.
10:37:44          > Could not get resource 'https://public.nexus.pentaho.org/repository/proxy-public-3rd-party-release/org/pentaho/pentaho-aggdesigner-algorithm/5.1.5-jhyde/pentaho-aggdesigner-algorithm-5.1.5-jhyde.pom'.
10:37:44             > Could not HEAD 'https://public.nexus.pentaho.org/repository/proxy-public-3rd-party-release/org/pentaho/pentaho-aggdesigner-algorithm/5.1.5-jhyde/pentaho-aggdesigner-algorithm-5.1.5-jhyde.pom'.
10:37:44                > Read timed out

It looks like a request timed out, you can rerun the failing test by commenting what is between the quotes like

Run Java PreCommit

Run Java PreCommit

Run Java PreCommit

Run Java PreCommit

Run Java PreCommit

Run Java PreCommit

Run Java_Examples_Dataflow PreCommit
Run Java_Examples_Dataflow_Java11 PreCommit
Run Whitespace PreCommit

@lukecwik I'm not sure what's going on here: jenkins reports that all of the builds have succeeded (e.g. the whitespace precommit) but github still thinks a bunch of them are pending.  In any case I believe I am passing all builds here.

@lukecwik I'm not sure what's going on here: jenkins reports that all of the builds have succeeded (e.g. the whitespace precommit) but github still thinks a bunch of them are pending. In any case I believe I am passing all builds here.

That looks like a glitch between Jenkins and Github. The 3 pending runs say that they are passing and this should be good to review.

Run Whitespace PreCommit

Run Java_Examples_Dataflow PreCommit Run Java_Examples_Dataflow_Java11 PreCommit Run Whitespace PreCommit

I believe you need to make a separate comment for each one you want to run.

Run Java_Examples_Dataflow_Java11 PreCommit

Run Java_Examples_Dataflow PreCommit

R: @jbonofre

I think @aromanenko-dev has been reviewing some similar changes. We could also start to ask the people who wrote them to do the review of this?

Thanks! I'll take a look

@aromanenko-dev thoughts? :)

@kennknowles @lukecwik @aromanenko-dev gentle ping?

@n-oden Sorry, I was off in the last 3 weeks. I'll try to take a look asap

@mosche Could you take a look on this, please?

@mosche thanks for the thorough review!  I'll try to get all comments addressed in the next few days.

@mosche I think I've addressed most/all of your comments.

Sigh, looks like the precommit failed because google throttled an unrelated test:
{
  "code" : 403,
  "errors" : [ {
    "domain" : "global",
    "reason" : "rateLimitExceeded"
  } ],
  "message" : "rateLimitExceeded"
}

Run Java PreCommit


vt-uploader: Add version 0.1.9

Closes #9349

[x] I have read the Contributing Guide.

/verify

/verify

/verify

/verify

@HUMORCE could you please test the manifest in my personal bucket? I need to know why the context menu I created for this manifest is not functioning properly?
scoop bucket add MyScoop 'https://github.com/Zliced13/MyScoop'; scoop install MyScoop/vt-uploader

why the context menu I created for this manifest is not functioning properly?

check the generated registry file finally.
btw:
1.why not use the package of portable one.
2.you should let the user choose whether to install the context menu or not, rather than forcing users to elevate privileges to do it, context menu is not a mandatory part.

If I get rid of the elevated privileges and forced context menu (make it optional). Would you help me figure out my context menu problem?

Then would you help me figure out my context menu problem?

I have already told you for this...

If I get rid of the elevated privileges and forced context menu (make it optional).

context menu without require elevated privileges is OK.

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\*\shell\Upload to VirusTotal\command]
@="\"$dir\\uploader.exe\" \"%1\""

Windows Registry Editor Version 5.00

[HKEY_CLASSES_ROOT\*\shell\Upload to VirusTotal\command]
@="\"$diruploader.exe\" \"%1\""

/verify

Thank you, @HUMORCE, the context menu now works perfectly.

I used the setup package, because that one contains language files that could be helpful for non-English speakers. The portable version does not.

you might need to recreate a plain text format of install-context.reg replace current one, it's content cannot be tracked in the file changes.

/verify

context menu without elevated privileges, and consider of global installation.
install-context.reg needs to changed to:
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Classes\*\shell\Upload to VirusTotal\command]
@="\"$dir\\uploader.exe\" \"%1\""

I am not sure if this works with developer mode disabled. (Windows Settings > Privacy & security > For developer > Developer Mode )

Done, I changed it.

fix it please

fix it please
suggestion:
create uninstall-context.reg when you do this.
sorry for I did not list all at once. thanks

@HUMORCE download the file and you can see for yourself that I did change it.
https://github.com/ScoopInstaller/Extras/blob/174fb74f2ebd2374e0b8f8ffcfce43b34ad754ea/scripts/vt-uploader/install-context.reg

yes, but it is identified as a binary file, so we cannot viewing its changes.
when correct:
https://github.com/ScoopInstaller/Main/pull/4106/files#diff-8fee256e0fd73758f66ee53fa4ddaff6d04e97bfcd861204f61aaf53a9284312

Done, @HUMORCE, The reg file is fixed now.

thanks for your work, I will refine this manifest when i am free.


Will IPAdapterFull support sdxl in the future?

Will IPAdapterFull support sdxl in the future?

257 tokens is too heavy, I will look more efficient method


Is there a demo or example for force layout?

To expand on that, what would need to be done to build a force directed layout demo if I was going to try?


Bad value for restricted picklist field when picklist value has a single quote

Trying to update an SObject picklist field that has defined answers with single quotes and I am getting an error.
client.update!('Contact', Id: '0035500000EoVgKAAV', Highest_Degree_of_Education__c: "Bachelor's Degree")
Faraday::ClientError: INVALID_OR_NULL_FOR_RESTRICTED_PICKLIST: Highest Degree: bad value for restricted picklist field: Bachelor's Degree

It looks like something weird is going on with encoding the single quote, not 100% sure this is an issue with this gem or maybe with the SalesForce API in general.
Here's the output of with debug turned on, some of the information is anonymized.
D, [2016-08-05T21:34:44.814402 #3311] DEBUG -- request:
  url: "https://xxx.salesforce.com/services/data/v37.0/sobjects/Contact/0035500000EoVgKAAV"
  method: :patch
  headers: {"User-Agent"=>"Faraday v0.9.2", "Content-Type"=>"application/json", "Authorization"=>"OAuth XXXXXXX"}
  body: "{\"Highest_Degree_of_Education__c\":\"Bachelor's Degree\"}"
D, [2016-08-05T21:34:45.082223 #3311] DEBUG -- response:
  status: "400"
  headers: {"date"=>"Fri, 05 Aug 2016 21:34:45 GMT", "set-cookie"=>"BrowserId=xxx;Path=/;Domain=.salesforce.com;Expires=Tue, 04-Oct-2016 21:34:45 GMT", "expires"=>"Thu, 01 Jan 1970 00:00:00 GMT", "sforce-limit-info"=>"api-usage=384/5000000", "content-type"=>"application/json;charset=UTF-8", "transfer-encoding"=>"chunked", "connection"=>"close"}
  body: "[{\"message\":\"Highest Degree: bad value for restricted picklist field: Bachelor's Degree\",\"errorCode\":\"INVALID_OR_NULL_FOR_RESTRICTED_PICKLIST\",\"fields\":[\"Highest_Degree_of_Education__c\"]}]"

Never mind, this was related to configuration. Not a real issue.


⚠ HDArea has degraded performance

In 71c173c, HDArea ($HDAREA) experienced degraded performance:

HTTP code: 200
Response time: 2793 ms

Resolved: HDArea performance has improved in e0953e5 after 20 minutes.


OS customizations missing

I think there are still some customizations missing (unfortunately, I never really made a list of changes I made, so this is from my memory):

Systemd: Disable logging daemon and periodic compression of logs
Systemd: Disable everything else it might do
Clean-Up crontabs (we don't want cron to run any tasks at all)
Make sure no other service/daemon is running other than "our" programs (i.e. wbc related stuff)
Remove  packages that interfere with wifibroadcast function (wireless-regdb, crda, wpa_supplicant, and probably others I forgot right now)
Remove packages that don't interfere with wifibroadcast function but are otherwise not necessary (for example spelling dictionary packages, popularity contest, etc. etc.)

Very true,
There are also a lot of kernel options being compiled now that are unnecessary.
If possible we need to make an inventory of everything that can be safely removed and i will add this to the scripts.
Perhaps you could provide some of the commands to achieve this.
I'll leave this issue open to aggregate such a list when we come upon them.
It's hard to find all modifications to the RC6 script...

I have removed two packages in the package script.
Every removal i do needs separate testing to see if i broke the image, so it will take some time, but work on this has started.

@rodizio1

Systemd: Disable logging daemon and periodic compression of logs
Systemd: Disable everything else it might do
Clean-Up crontabs (we don't want cron to run any tasks at all)

Do you have the commands available for this? I'm not sure about the best way to approach this. (Not a long time Linux user, so some things still elude me).

Did you figure this out? If not I can look into it

Ive been working on it. The services mentioned are pretty easy to disable and I believe that disabling cron.service will kill all of its tasks.
Just want to do some testing and also compare what is running on the beta image vs 1.6.
While making that comparison I can see what packages are installed on 1.6 so that should give us a pretty good idea of what to eliminate off the beta image on the first go without too much tedious code changes/rebuild cycles.

running systemctl status between 1.6 and 2.0beta so feel pretty good about killing these
#disable unneeded services
sudo systemctl disable cron.service
sudo systemctl disable syslog.service
sudo systemctl disable journald.service
sudo systemctl disable logind.service
sudo systemctl disable triggerhappy.service
sudo systemctl disable avahi-daemon.service
sudo systemctl disable ser2net.service
sudo systemctl disable dbus.service
sudo systemctl disable systemd-timesyncd.service
one reveal running sstemctl status is that the new image is running in a degraded mode which I think means some things failed to load. Upon investigation they are
hciuart.service (feel pretty good about killing this as it is for bluetooth support and currently wbc does not offer any- maybe in future)
AND
run.rpc_pipes.mount
The last does not mean anything to me- you guys? One way or another it should be addressed

That's some good investigative work, the hciuart could be because of the config.txt in boot not enabling bluetooth.
The other one is unkown to me, we could disable it since it isn't starting anyway, but i'd feel better if i knew what it did. Google only gives me some hits about NFS mounts etc...
Since we have a mounted FS i don't think it is completely broken, but if somebody knows what this actually does, please chime in.
I'll add the other commands to a chroot script in the 04 WFB stage.

For what its worth: I was adding them in stage 4, 03-run-chroot.sh after the #disable sync option for usbmount. I did not test it yet with disabling hciuart.service but should will.
BTW
On 1.6 the only 2 services running not directly related to WBC (as far as I can tell) is:
udevd.service (might be a slight name change on 3b+ not totally sure)
ssh.service
If we continue to have weird issues I may take a closer look at the timing order of how everything is started between 1.6 and 2.0. At a glance the order in which some of the WBC stuff start looks different but I cant say with certainty yet.

Once you are satisfied, make a pull request, i'll happily approve it.

Got side tracked by that run.rpc_pipes.mount error. Dug a bit in the boot logs and there is a failure to load module autofs4 . I believe this auto mounts partitions. This also explains some errors related to ext4 file system during boot.
Going to compare all of this to the boot logs of 1.6 ANNNDD then finally get to the packages lol

Journald is still running.
I seem to vaguely remember this issue back in the day.. @rodizio1 any input?

 I don't remember what I did back then, but I remember at some point I started deleting stuff because I couldn't find another way to cleanly disable this systemd crap.
One option would be using the tool "meld" to compare directories and files of my image with the new image (thing is just, since the image-builder uses a newer Raspbian based on a newer Debian version, things could have changed significantly).

yes I am seeing that.. It is whack a mole with systemd. When I delete packages to kill one service sometimes it comes back in another form. This is going to take more work. I am still plugging away

Closing in on some solutions.
The workflow is time consuming, especially when modifying the build early on.
I have been creating an image then running it and making mods to the live image at command line. Finally going back and implementing this changes in the build script and testing. It can be slow.. as you know. It’s also tempting to try and make too many changes in one build run and thus complicating debugging lol
So I should have a pull for purges packages, stopped services, and later v4l2loopback support although having more issues than expected getting it to make

I know, the power of the image builder is more apparent when changing in the later steps. The kernel build for instance took a good long while to get right.
Making modifications in the image, writing them down and then doing several at once is how i do it myself.
Should the original pull request still be done? Or are you going to replace it? v4l would be great to get working!

No please wait on the pull, the original pull needs to be modified. I am waiting for an entire build to cook and then test.
I think solution for for that journald is using a mask command. Essentially break it buy sending it’s output to the infamous null file. This may be the solution for some other service along with purging of packages. @rodizio1 does this sound familiar
My understanding of systemd is it is more powerful than init.d in that if a new service has a service dependency it will start new services. Everything tries to write to journald thus systemd is restarting it constantly.

I know, the power of the image builder is more apparent when changing in the later steps. The kernel build for instance took a good long while to get right.

One other big benefit of the building script is that every one can see and reproduce how the image has been built.
That's not the case for all others image (except DroneBridge) where there's no documentation about their building process.
So @RespawnDespair, I say you again many thanks for this great tool :-)

Yes +1 @Yes21 !
The pull request for the services killer commit is ready to go.
Their is a new pull request for package deletion.
Both were briefly tested on pi 3b and 3b+ acting as groundpi. Video and telemetry OK. They need more testing as AirPi and the RC part.

So far these are the packages I removed and tested in my pull request
Remove packages that conflict with the workings of EZ-Wifibroadcast
DEBIAN_FRONTEND=noninteractive sudo apt-get -yq purge wireless-regdb
DEBIAN_FRONTEND=noninteractive sudo apt-get -yq purge wpasupplicant
DEBIAN_FRONTEND=noninteractive sudo apt-get -yq purge crda
DEBIAN_FRONTEND=noninteractive sudo apt-get -yq purge cron
#Untested Packages for possible removal
#DEBIAN_FRONTEND=noninteractive sudo apt-get -yq purge dbus
#DEBIAN_FRONTEND=noninteractive sudo apt-get -yq purge dhcpcd5
#DEBIAN_FRONTEND=noninteractive sudo apt-get -yq purge isc-dhcp-client
#DEBIAN_FRONTEND=noninteractive sudo apt-get -yq purge isc-dhcp-common
Remove packages for space savings
DEBIAN_FRONTEND=noninteractive sudo apt-get -yq purge apt-transport-https
DEBIAN_FRONTEND=noninteractive sudo apt-get -yq purge aptitude
DEBIAN_FRONTEND=noninteractive sudo apt-get -yq purge aptitude-common
DEBIAN_FRONTEND=noninteractive sudo apt-get -yq purge apt-listchanges
DEBIAN_FRONTEND=noninteractive sudo apt-get -yq purge avahi-daemon
DEBIAN_FRONTEND=noninteractive sudo apt-get -yq purge bzip2
DEBIAN_FRONTEND=noninteractive sudo apt-get -yq purge cifs_utils
DEBIAN_FRONTEND=noninteractive sudo apt-get -yq purge curl
DEBIAN_FRONTEND=noninteractive sudo apt-get -yq purge iptables
DEBIAN_FRONTEND=noninteractive sudo apt-get -yq purge triggerhappy
Does anything jump out that might need to stay? I have come to the conclusion that I could spend hours and hours just getting rid of unneeded packages... The 4 commented packages are ones that might be purged as well that involve networking. Thoughts?
Rodizio had a good idea with using meld and doing a comparison. Might look into that later but I kind of see the space savings stuff as something we could get to later (lower priority). Additionally there are other space saving that could be implimented such as removing all info files and more...

@pilotnbr1 Many thanks for all thi great job :-)
I will test it as far as your PRs will be merged.

@Yes21 if you want to test you should remove the skip files from stage 3 and stage 4

Thanks, I know it. I've already rerun stages 3 and 4 many times today !!

Could we close this issue now ?

@pilotnbr1 are you happy with your changes? Any loose ends?
I'm confident the kernel config part is okay now.
If you are happy we'll close this issue as well...

Its looking good!

I agree, great work!


modifying elastalert* index contents

I need some more fields in addition to the fields that are added to the elastalert index of my elasticsearch for creating visualisation in which i can filter out the server with the other fields- like server group etc. I can see them in the kibana search

but can't use them in visualisation. shows "no catched mapping for the field. Refresh the fields mapping from management page" but even that doesn't help.
How can I get all required fields that match the alert situation in the elasticsearch. any help would be great.

changing the code in create_index.py with 'match_body' : {'enabled': True.... creates the respective mapping in the elasticsearch elastalert_status index.


Inline service registries into ManualDocumentsController

This is similar to #865, but for the ManualDocumentsController instead of the ManualDocumentAttachmentsController. The overall aim is to reduce the levels of indirection in the code to make it easier to follow. In some cases, this means temporarily introducing duplication, but we're confident that in the long run this will make it easier to identify better abstractions to remove that duplication.
The net effect is to inline most of the methods from AbstractManualDocumentServiceRegistry and its two sub-classes, ManualDocumentServiceRegistry & OrganisationalManualDocumentServiceRegistry into ManualDocumentsController. I've also extracted three anonymous procs returned by methods in AbstractManualDocumentServiceRegistry into new named classes to avoid excessive duplication:

PublishingApiDraftManualExporter
PublishingApiDraftManualDocumentExporter
PublishingApiDraftManualDocumentDiscarder

I've tried hard to break the overall refactoring down into small steps to give as much confidence as possible that I haven't broken anything; the tests all pass after every commit.
Although I've applied the refactorings to the TidyUpRemovedDocuments migration, I haven't tested these changes. However, since we're hoping to remove the commits in #868, I think this is OK.
Although I've applied the refactorings to ManualSectionReslugger, this class is not tested. However, since the script which uses this class is already broken (see #851), I think this is OK.

Rebasing against master and force-pushing to keep the branch up-to-date.

Rebasing against master and force-pushing in preparation for merging.

Note that rebasing against master was a bit painful due to the renaming of ManualDocument to Section in #887. However, I think I've caught everything - including editing the commit notes!


Update links for model repositories

Remove dead links and update links (redirections, https, etc).

Cool, thanks! 😊


Convert buttons to list

As of now buttons are a map, but they should be list so that users can decide the order in which these appear.

We can probably silently transform the old format when saving to make this is a non breaking change.


GDAX brokerage only supports 3-character currencies

Expected Behavior

GDAX brokerage should support all available symbols

Actual Behavior

GDAX brokerage only supports 3-character currencies

Potential Solution

Add new GDAX symbol mapper
Update brokerage to use the symbol mapper

Reproducing the Problem
Code review:

https://github.com/QuantConnect/Lean/blob/master/Brokerages/GDAX/GDAXBrokerage.Messaging.cs#L48
https://github.com/QuantConnect/Lean/blob/master/Brokerages/GDAX/GDAXBrokerage.Messaging.cs#L405
https://github.com/QuantConnect/Lean/blob/master/Brokerages/GDAX/GDAXBrokerage.Messaging.cs#L502

System Information
n/a
Checklist

[x] I have completely filled out this template
[x] I have confirmed that this issue exists on the current master branch
[x] I have confirmed that this is not a duplicate issue by searching issues
[x] I have provided detailed steps to reproduce the issue

Closed by #4888


Fix #35 - disable debug mode by default.

Also made debug pins configurable.

Interested in the PR. I'll review and test out.

Please verify missing ( and resolve. Thanks.

Forgot to test with debug turned on :/
Merged with master and fixed missing '('.

LGTM.


Color switcher - content switcher is broken

Switcher throws an error on this page
https://carbondesignsystem.now.sh/guidelines/color/usage

related https://github.com/carbon-design-system/carbon/pull/3302


Minimum votes required to implement accessibility  issue should be far less than normal issues.

There are  a lot fewer number of assistive technology users  compared to normal users. So we should try to give level playing feild to assistive technology users by reducing the number of votes required to move it to implementation.There are less than 5% people only use assistive technologies.

Thanks for the issue - we already do this, pls provide an example if you feel that's not the case

I have seen the issue triaging docs but there is mention of upvoting policy link is no mention of numberof votes required specifically for accessibility issues.
Please treat Accessibility issue  as important  as UI issue so that accessibility users also can benifit.
Please treat accessibility issue as a bug so that community can implement quicker.thanks.

Yes, though it's not documented those are already our current practice.


[json-schema-validator] Update to 2.2.0

Updates json-schema-validator to 2.2.0

[x]  Changes comply with the maintainer guide
[x]  SHA512s are updated for each updated download
[x]  The "supports" clause reflects platforms that may be fixed by this new version
[x]  Any fixed CI baseline entries are removed from that file.
[x]  Any patches that are no longer applied are deleted from the port's directory.
[x]  The version database is fixed by rerunning ./vcpkg x-add-version --all and committing the result.
[x]  Only one version is added to each modified port's versions file.

Thanks for the update!


Add method to add padding to video

Lekker. This is not needed for ios?

@FrikkieSnyman Instagram does have capable iOS developers 🤷  - it scales okay there by default

👍

@jaspermeijaard thanks for the extensive review! I'll check these changes with the new version as well. The PR I added above should answer your other question!


Cannot read property 'addClass' of undefined

This is a (multiple allowed):

[x] bug

[ ] enhancement

[ ] feature-discussion (RFC)

Swiper Version: EXACT RELEASE VERSION OR COMMIT HASH, HERE.

Live Link or JSFiddle/Codepen or website with isssue: PREFERABLY (IF YOU WANT YOUR ISSUE TO BE RESOLVED ASAP).

Expected Behavior
EXPLAIN WHAT IS TO BE EXPECTED, HERE.
Actual Behavior
EXPLAIN WHAT IS ACTUALLY HAPPENING, HERE.
P.S. Remember, an issue is not the place to ask questions. You can use Stack Overflow
for that.
Before you open an issue, please check if a similar issue already exists or has been closed before.

Uncaught TypeError: Cannot read property 'addClass' of undefined
at h.init (swiper.min.js?v=:12)
at h.beforeInit (swiper.min.js?v=:12)
at swiper.min.js?v=:12
at Array.forEach ()
at swiper.min.js?v=:12
at Array.forEach ()
at h.n.emit (swiper.min.js?v=:12)
at h.init (swiper.min.js?v=:12)
at new h (swiper.min.js?v=:12)
at video:1532

Check your classes. If you have multiple swiper inits and they will catch elements with same class (for example thumbs slider) it could fails like that.

Add a JSFiddle or CodePen for better help

Closing due to inactivity and/or no responses from issue author

hello,
same issue here... i cant understand why it has been so complicated... the docs has a lots of typo errors or missunderstandable contents, the Swiper.use() doesn't load moduls... etc.
I built a gallery Swiper (in next.js) with thumbs and when I click on the second image in the galleries list (not on Swiper's thumbnail) the Swiper runs on error:
Unhandled Runtime Error
TypeError: Cannot read property 'addClass' of undefined
Call Stack
Swiper.init
node_modules/swiper/esm/components/thumbs/thumbs.js (32:0)

There's my code:
import React, { useState } from "react";
import { Container, Row, Col, Modal, ModalBody } from "reactstrap";
import SwiperCore, { Navigation, Thumbs } from "swiper";
import { Swiper, SwiperSlide } from "swiper/react";

SwiperCore.use([Navigation, Thumbs]); // docs says Swiper.use() but that's wrong... Navigation doesn't load here, but Thumbs module works

const GalleryModal = ({ images, isModalOpen, toggle, className }) => {
  const [thumbnailSwiper, setThumbnailSwiper] = useState(null);

  const gallerySwiperConfig = {
    grabCursor: true,
    spaceBetween: 10,
    thumbs: {
      swiper: thumbnailSwiper,
    },
  };

  const thumbnailSwiperConfig = {
    slidesPerView: 4,
    spaceBetween: 30,
  };

  const toggleWindowScrollbar = (overflowState) => {
    const html = document && document.querySelector("html");
    if (html) {
      html.style.overflowY = overflowState;
    }
  };

  return (
    <Modal
      isOpen={isModalOpen}
      toggle={toggle}
      className={className}
      centered
      autoFocus
      onOpened={() => toggleWindowScrollbar("hidden")}
      onClosed={() => toggleWindowScrollbar("auto")}
    >
      <ModalBody>
        <Swiper
          id="gallery-swiper"
          {...gallerySwiperConfig}
        >
          {images && images.length
            ? images.map((image, index) => (
                <SwiperSlide
                  key={`image-slide-${index}`}
                  virtualindex={`thumb-${index}`}
                >
                  <div
                    style={{
                      width: "100%",
                      height: 400,
                      backgroundSize: "cover",
                      backgroundImage: `url(${image})`,
                    }}
                  />
                </SwiperSlide>
              ))
            : null}
        </Swiper>

        <Swiper
          id="thumbnail-swiper"
          onSwiper={setThumbnailSwiper}
          {...thumbnailSwiperConfig}
          className="mt-4"
        >
          {images
            ? images.map((image, index) => (
                <SwiperSlide
                  key={`thumbnail-slide-${index}`}
                  virtualindex={`thumb-${index}`}
                >
                  <div
                    style={{
                      width: "100%",
                      height: 100,
                      backgroundSize: "cover",
                      backgroundImage: `url(${image})`,
                      cursor: "pointer",
                    }}
                  />
                </SwiperSlide>
              ))
            : null}
        </Swiper>

      </ModalBody>
    </Modal>
  );
};

export default GalleryModal;

Thank you.

Same error after todays update – strange.

Same error after todays update – strange.

been using swiper cdn for around a year just fine this error come out today out of nowhere had to roll back to older version
this version works fine:
<EMAIL_ADDRESS>

been using swiper cdn for around a year just fine this error come out today out of nowhere had to roll back to older version
this version works fine:
<EMAIL_ADDRESS>

@SarkarKurdish #4157

@SarkarKurdish #4157

Same issue today

Same issue today

I have the same error with NextJS + Swiper (6.7.0)
When a page is re-rendered with the slider, it breaks and gives the following message above.
I have downgraded to older versions, no luck..

i have same error in next js .please help


Spacing before and after content being removed on save

When in edit mode you can use line breaks, and empty elements, to create additional spacing between paragraphs or content. As soon as edit mode exits, this space is removed. Is this by design? If so, is there a suggested way for users to create space between their content?

HI @shawnlehner - there's a stackoverflow post which includes a description on why this is the default behaviour and instructions on patching the editor to modify this behaviour if you need to (http://stackoverflow.com/questions/36883079/how-to-preserve-multiple-br-when-no-content-before-or-after-with-contenttools/36954440#36954440)
My recommendation however would be to use CSS and not additional line-breaks or paragraphs to add extra space between elements in scenarios where the default spacing for an element needs to be overwritten. For example:
.mind-the-gap {
    margin-bottom: 40px;
}

ContentTools.StylePalette.add([new ContentTools.Style('Mind the gap', '.mind-the-gap')]);

You'll then be able to apply the .mind-the-gap class to any editable element (other than static elements) within a region (e.g via the inspector bar > properties dialog > style tab).


Don't save passwords, addresses etc by default

Should be easy...

Using the browser password manager is a good idea in general.


Profile Screen not updating on Box change

The profile screen does not update when we change to a box where we haven't uploaded anything. Also causes crash on MIUI devices

Closed


sky_tool start fails to start sky_server if sky_tools isn't a dependency

It should at least fail hard.  Right now it just logs and continues:
Package "sky_tools" is not an immediate dependency.
Cannot run executables in transitive dependencies.

I believe I created this project using sky_tools init, so presumably that template should be updated to include this direct dependency.

I can't repro this.  Removing sky_tools from the Stocks example pubspec.yaml seems to work fine for me.  Please reopen if this is still an issue.


Add CI workflow

Can you clarify exactly what else I should do to finalize the ci/cd with publish to the stores? (chrome + firefox)

Follow the steps here: https://docs.plasmo.com/framework/workflows/submit

Can you clarify exactly what else I should do to finalize the ci/cd with publish to the stores? (chrome + firefox)

Follow the steps here: https://docs.plasmo.com/framework/workflows/submit

What about FireFox? Can't see that you mention it in the submit.yml.

Maybe here?
https://docs.plasmo.com/itero/publisher
https://docs.plasmo.com/itero/publisher#firefox-add-ons-store


update kernel in release-16.03

Currently the kernel in branch release-16.03 is not up to date. Could the following commits be cherry-picked from master into release-16.03?
commit 4489454b83ccf519f516dcfcc073a450a4fa8ac7
Author: Tim Steinbach<EMAIL_ADDRESS>Date:   Sat Oct 22 12:10:34 2016 -0400
linux: 4.4.26 -> 4.4.27

commit 1af5b2a80c48d3536585a784baf8b7d73c70868d
Author: Tim Steinbach<EMAIL_ADDRESS>Date:   Sun Oct 30 10:29:37 2016 -0400
linux: 4.4.27 -> 4.4.28

commit ef1a188e079d6ae2a68d400eefc2104b159548e7
Author: Eelco Dolstra<EMAIL_ADDRESS>Date:   Tue Nov 1 11:31:00 2016 +0100
linux: 4.4.28 -> 4.4.30

My understanding is that 16.03 is no longer maintained (and is likely to contain multiple vulnerabilities).

Unfortunately I can not update to release-16.09 because of #18995 (see my comment https://github.com/NixOS/nixpkgs/issues/7220#issuecomment-252297993). Until it is fixed I have to keep some commits cherry-picked on top of release-16.03. It would be great if some of them are applied upstream too.
BTW where can I find EOL dates for nixos releases? I tried to do this before submitting this bug report, but I didn't find it on neither the official site nor github.

I think there's no real official announcement about EOL, but it's really lots of work to keep up with all those CVEs, and AFAIK contributors generally didn't want to do the work longer than a few weeks after a new stable release.
I picked linux-4.4.30. Just git cherry-pick -x suitable patches, and submit PR against release-16.03 (you can repeat once a while). Perhaps ping me, if noone merges it. The Hydra job should not be a problem, if given a lower priority; it's the manpower/motivation that is/was missing.

I announce EOL with new stable release, for example http://lists.science.uu.nl/pipermail/nix-dev/2016-October/021882.html

Ah, thanks for correcting that.

@domenkozar Thank you. I see now. I assumed this policy, but as some commits got into 16.03 after 16.09 was announced, I thought that probably this is not the case.
@vcunat Thank you. I will make a PR if I have any appropriate patches.


[feat-4496][server]  Add to! {} is used to mark the custom parameters to be output as-is in sql

What is the purpose of the pull request’
Before pre-compiling sql, replace the custom parameters marked with !{}
to prevent the parameters in the hive plus partition path from being
replaced with single quotes
Closes This closes #4496
Brief change log

Add a method to replace custom parameters before pre-compiled SQL
增加一个方法在预编译sql之前替换自定义参数

Verify this pull request

Manually verified the change by testing locally.

Codecov Report

Merging #4497 (9324a3c) into dev (690e4ea) will decrease coverage by 0.05%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##                dev    #4497      +/-   ##
============================================
- Coverage     43.58%   43.53%   -0.06%
+ Complexity     3202     3198       -4
============================================
  Files           471      471
  Lines         21765    21778      +13
  Branches       2640     2641       +1
============================================
- Hits           9487     9480       -7
- Misses        11376    11393      +17
- Partials        902      905       +3

Impacted Files
Coverage Δ
Complexity Δ

...lphinscheduler/server/worker/task/sql/SqlTask.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

...er/master/dispatch/host/assign/RandomSelector.java
77.77% <0.00%> (-5.56%)
3.00% <0.00%> (-1.00%)

...inscheduler/service/zk/CuratorZookeeperClient.java
60.97% <0.00%> (-4.88%)
7.00% <0.00%> (-1.00%)

...e/dolphinscheduler/remote/NettyRemotingClient.java
50.00% <0.00%> (-2.78%)
9.00% <0.00%> (-2.00%)

Continue to review full report at Codecov.

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

Codecov Report

Merging #4497 (9324a3c) into dev (690e4ea) will decrease coverage by 0.05%.
The diff coverage is 0.00%.

@@             Coverage Diff              @@
##                dev    #4497      +/-   ##
============================================
- Coverage     43.58%   43.53%   -0.06%
+ Complexity     3202     3198       -4
============================================
  Files           471      471
  Lines         21765    21778      +13
  Branches       2640     2641       +1
============================================
- Hits           9487     9480       -7
- Misses        11376    11393      +17
- Partials        902      905       +3

Impacted Files
Coverage Δ
Complexity Δ

...lphinscheduler/server/worker/task/sql/SqlTask.java
0.00% <0.00%> (ø)
0.00 <0.00> (ø)

...er/master/dispatch/host/assign/RandomSelector.java
77.77% <0.00%> (-5.56%)
3.00% <0.00%> (-1.00%)

...inscheduler/service/zk/CuratorZookeeperClient.java
60.97% <0.00%> (-4.88%)
7.00% <0.00%> (-1.00%)

...e/dolphinscheduler/remote/NettyRemotingClient.java
50.00% <0.00%> (-2.78%)
9.00% <0.00%> (-2.00%)

Continue to review full report at Codecov.

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

@liuxuedongcn Maybe you should pass the Unit Test / Check code style and SonarCloud Code Analysis at first

@liuxuedongcn Maybe you should pass the Unit Test / Check code style and SonarCloud Code Analysis at first


gloves dont connect

I use esp32 , with a ch340c converter. The firmware was successful, changed to bluetooth connection, but when I try to connect the gloves writes that there is no response from the device. Tried to connect by wire , also nothing works. I think the problem is in the ch340c.

If the firmware was successfully flashed, then that means the CH340C worked without any issue. Bluetooth is completely independent of the hardware serial interface so it has nothing to do with the CH340C either...
Is Bluetooth dongle is version 4.0? Newer versions are known to cause issues with the ESP32

Dongle version is 5.0

That is a probably cause for the Bluetooth issue, however you should still be able to test it in serial mode (via USB cable)


Multiple domains

It would be useful to be able to specify multiple domains for a service. There are cases where it might be useful to set some context for an application based on the domain used to access it. Like, I can imagine a dashboard that uses the same app, but modifies some language or visibility of menu items based on the domain:
teacher.app.com

student.app.com

Similar but different to #246

Related to #174

This also blocks Nounly.

Blocked by #523

Duplicate of https://github.com/orgs/DefangLabs/projects/4/views/20?pane=issue&itemId=67388462 ?

Duplicate of https://github.com/orgs/DefangLabs/projects/4/views/20?pane=issue&itemId=67388462 ?

Duplicate of https://github.com/orgs/DefangLabs/projects/4/views/20?pane=issue&itemId=67388462 ?

My understanding of the spec is that that issue would address internal hostname aliases, not public facing? But @lionello can correct me if I'm wrong.

Duplicate of https://github.com/DefangLabs/defang-mvp/issues/1108


Proposal: Add etcd plugin to detect the mesos master.

Currently, the etcd-based master contender/detector module is developing in Mesos community, refer to MESOS-1806 for the details. So in the near future，when we deploy the kubernetes cluster on a high-availability model Mesos cluster, it does not need to run another zookeeper cluster just for Mesos. So I create this ticket to enhance mesos-go to have the ability to detect the Mesos master from etcd cluster. I will submit a pull request for this ticket later,

Related PR #256


Tag a release (v0.0.2?)

At the time of writing, there is only a single tag (release) of play-with-docker:
cd $(mktemp -d)
go mod init mod.com
go list -m -versions github.com/play-with-docker/play-with-docker

gives:
github.com/play-with-docker/play-with-docker v0.0.1

Indeed this tag was created as far back as Dec 2016:
https://github.com/play-with-docker/play-with-docker/releases/tag/v0.0.1
This tag does not, therefore, include https://github.com/play-with-docker/play-with-docker/commit/f1183076e553f3b4ffff868e253ec12c5b197812. Hence someone doing go get github.com/play-with-docker/play-with-docker@latest (which is the default behaviour) will get the non-module version of this project.
At the least, therefore, we should tag v0.0.2 to include https://github.com/play-with-docker/play-with-docker/commit/f1183076e553f3b4ffff868e253ec12c5b197812

Tag v0.0.2 pushed.
@myitcv check it out and LMK if anything's missing

All looks good, thanks.


Fix Magnifying glass in page builder

Changelog
Summary of the issue: The magnify icon in the page builder has styles that make it look like a link, when you hover over the icon. Since it is just an icon, these styles has to be removed for better ui.
What was changed: Link styles are stripped off from the magnify icon in compose page builder.

Closing this one, as requirements have changed in the meantime.


Convert v1 model file to current version

We have an older Neon v1 model which we'd like to use with the latest Neon version. However, the model loading fails due to this assert:
File "neon/neon/layers/container.py", line 200, in load_weight
assert len(pdict['config']['layers']) == len(self.layers)
This same issue has been reported with the pre-trained deep speech model: https://github.com/NervanaSystems/deepspeech/issues/63
Is there a way to convert the old v1 model to work with the latest Neon?

What do you mean by "v1 model" ? Which model is that.
Is that DeepSpeech model and was it used to work with an older neon version?

It is based on the DeepSpeech model, and it has been trained with Neon 1.8. It appears that the models serialized with the old 1.* versions are no longer compatible with the latest Neon. Is there some way to convert those models such that they can be used with version 2.6?

neon 2.3+ versions should be able to load the model trained in neon 1.8, and re-save it in neon 2.3+ format.
Please see this issue: https://github.com/NervanaSystems/neon/issues/415
and please pay attention to the comment that "i was able to load and save the new model by printing out the model architecture and verifying that the structure of the layers where equal".


Upgrade build tools to fix deployment on new builds

On newer builds of VS, our repo is failing to deploy to VS with:
VSSDK1043: There was a problem finding the extension with a VSIX identifier of "F6B5EACA-7FA1-4591-8D40-A38234763621". Value does not fall within the expected range.
Upgrading our build tools version to a build that contains this fix.

tag @dotnet/project-system


Update to build API

Updates Capistrano, Rake & Heroku to use the new build api endpoint.

Uses local deploy command for delivery instead of Bugsnag::Delivery
Acquires builderName from %x(whoami) if not provided

Closing in favour of #13


Vulnerability roundup 102: gradle-5.6.4: 3 advisories [7.8]

search, files

[ ] CVE-2021-29428 CVSSv3=7.8 (nixos-20.09, nixos-unstable)
[ ] CVE-2021-29427 CVSSv3=7.2 (nixos-20.09, nixos-unstable)
[ ] CVE-2021-29429 CVSSv3=5.5 (nixos-20.09, nixos-unstable)

Scanned versions: nixos-20.09: 76ed24ceab9; nixos-unstable: ea7d4aa9b82.

See also: #116879

Gradle 5 was dropped in #205388


Remove kyverno support

Breaking Change
Removes kyverno support. All references to command line options and action options related to kyverno have been removed and you need to remove them when upgrading.
Details
Kyverno support has been removed since we no longer wish to maintain this feature.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 93.55%. Comparing base (903e860) to head (333df45).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #818      +/-   ##
==========================================
+ Coverage   93.53%   93.55%   +0.01%
==========================================
  Files          20       20
  Lines        2306     2250      -56
==========================================
- Hits         2157     2105      -52
+ Misses        149      145       -4

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Removed like arg in dpnp zeros and ones overload.

[x] Have you provided a meaningful PR description?
[ ] Have you added a test, reproducer or referred to an issue with a reproducer?
[ ] Have you tested your changes locally for CPU and GPU devices?
[ ] Have you made sure that new changes do not introduce compiler warnings?
[ ] If this PR is a work in progress, are you filing the PR as a draft?

Can you remove the like keyword for dpnp.empty as well?

Done, force pushed.


YETUS-494. smart-apply-patch fails if there is the corresponding PR but the patch URL is not written

Test JIRA integration


Basic documentation around grafana, dashboards and datasources

Crap this shouldn't trigger the e2e test. We should fix that to speed this up

Some of the things that I have mentioned as TODO I have now mentioned in https://github.com/grafana-operator/grafana-operator/issues/957 to help to keep track of it.

@elamaran11 so I want this PR merged as quickly as possible so My thinking is that we will add the examples that you talk about in a separate PR.
@HubertStefanski since I did the original PR I can't approve it but if you think it looks okay please approve and we can get this merged :)

Sounds good @NissesSenap LGTM


Adding a delegate to get current video playback progress

Replaced typeof(self) by PBJVideoPlayerController * for travis validation

Hi @piemonte , do you plan to merge this ? I'd rather use your pod instead of my fork.
Thanks !

hey @Tibabal :v:
yes, changes look good, will get it merged. thanks for the contribution!


[Suggestion]: Ignore version data inside filenames

Currently, luarocks embeds versioning information in the rock filename itself (rockname-0.0.1-1.rockspec). We should still allow files like this, but we should ideally completely the version that's presented there. Instead we should parse the contents of the file to extract the actual version - this is slightly slower but at greatly increased developer ergonomics.

Already implemented as part of projects. When parsing rockspecs we ignore any sort of filename data.


feat(keybindings): generic way of adding keybindings

New hooks to make adding keybindings a breeze.
We use activity symbols to decouple the key combo from the key combo handler. Components define various activities and the app decides which keys trigger which activities.
Obligatory ASCII Venn diagram:
[ app         {          ] component }
[ key combo   { activity ]   handler }

Re AB#14428
Credit goes to @megheaiulian for figuring out how to generalize https://github.com/Neovici/cosmoz-bottom-bar/pull/163

Noticed there is no export of keybindings in package.json, don’t we need that? :)

Thank you @micaelagoffe. I would have missed that for sure!

Thank you! :pray:


${__org.name} does not work

SCENES
Question 1
I tried it in a simple application and the global variable ${__org.name} does not work. The code:
const getOrganizationScene = () => {
  return new EmbeddedScene({
    body: new SceneFlexLayout({
      children: [
        new SceneFlexItem({
          body: PanelBuilders.text().setTitle("Title: ${__org.name}").build(),
        }),
      ],
    }),
  });
};

Result:

Interestingly, and definitely worth noting, it works on the dashboard. Why not in the app? Have I implemented something incorrectly? I know, it's hard to debug remotely, maybe I missed some important step.
Dahboard:

Question 2
Is it possible to use these global variables in a SceneApp title (like in my example)? Maybe in the future, or somehow already now?
const getScene = () =>
  new SceneApp({
    pages: [
      new SceneAppPage({
        title: 'Organization ${__org.name}',
        url: prefixRoute(`${ROUTES.Organization}`),
        hideFromBreadcrumbs: true,
        getScene: getOrganizationScene,
      }),
    ],
  });

Just a guess but I think you might need a custom macro? ihttps://grafana.com/developers/scenes/advanced-variables#custom-variable-macros


Make the example alt text useful

Thanks for the contribution!  Before we can merge this, we need  @avh4 to sign the Salesforce Contributor License Agreement.

Closing this as it now has conflicts - feel free to reopen if you feel strongly about it!


Improve the dashboard buffer name and make it customizable

Dashboard creates a scratch buffer, named 'Scratch' by default. Not very intuitive.
This does not matter much if status/window/tab lines are hidden, the default behaviour. But may not look nice otherwise.

sorry i don't get the point.

In my environment, I prefer the tabline to be visible, and dashboard to appear every time I open a new tab. Config like this:
 db.setup( {
   theme = 'hyper',
   hide = {
     tabline = false
   },
   config = {
     -- disable_move = true,
   }
 } )

 vim.api.nvim_create_autocmd('TabNewEntered', {
   desc = "Open dashboard-nvim on new tab",
   callback = function() require('dashboard'):instance()
 })

This causes the dashboard on a new tab to look like this:

Note that the name of the new tab where the dashboard is opened is shown as Scratch. Dashboard creates a temporary buffer, and it is called "Scratch" by default. So wherever the current buffer name can be displayed, this word "Scratch" appears. This is not a big deal, just a cosmetic issue, but it does not look nice, IMO.
With my fix, it looks like this:

I have opened several new tabs in parallel to show how the fix behaves when multiple dashboards are opened


FOLBCAsk to implement InferenceProcedure

As of now, FOLBCAsk is an independent class. However, a few demo applications require it to be an implementation of the InferenceProcedure interface. The algorithm should be modified for the same.

This issue was resolved in #425.


[8.x] Add model factory trait to disable model events

Benefits to end users
For users who make use of model events, especially the creating/created or saving/saved events, it is often desirable to skip those events for the sake of narrowing the scope of test in factories for tests or preventing incidental processing during seeders, etc. This PR adds a trait which allows for a fluent interface to skip model events during the factory creation of the model.
Intended usage
After adding the DisablesEvents trait onto a model factory, a user can skip model events during the creation process by calling ModelFactory::new()->withoutEvents()->create(). Or, with the model trait: Model::factory()->withoutEvents()->create()
Relationships
The scope of the withoutEvents() method only applies to the factory it is directly called on. To apply this to related models as well, one can do so in the definition by applying the method to the related model factory. It could also be applied to any other situation (states, etc) where a model factory could be present.
Non-breaking feature
This addition is encapsulated in a trait which users can choose to add to their model factories if they wish. There are no impacts to any users who do not apply the trait.
Makes readability better
This addition is primarily an ease-of-testing situation. There is nothing that it does that cannot currently be done using Model::withoutEvents(...) but it allows for better readability by doing so via the factory's fluent interface.

Why an entirely separate trait. Seems like you could just build this feature into the Factory class.

Why an entirely separate trait. Seems like you could just build this feature into the Factory class.

I agree, the initial idea was to keep this as hands-off as possible, and the trait from a project standpoint didn't need to interact with the underlying factory class at all. If you think it would fit better as part of the factory, I'd be happy to move it in there.


sensible way to flag model instability?

Does the team have a sensible way to detect and flag unstable simulations?
Context: I finished some AMIP runs forced by modified boundary conditions. For each start date, I have twenty ensemble members generated with different random seeding. While simulations are stable for most start dates, a few combinations of initial conditions and boundary forcings are so unstable that most runs fail.

The plot compares the standard deviations along the longitude dimension at the start and the end dates. The ratios are in the [latitude, ensemble member] space. Any ratios beyond 5.0 are likely beyond the normal range of seasonality and indicate some model instability. Conventional physical models usually flag instability and terminate simulations early.
The plot is generated using the following code:
    ds_test = xr.open_mfdataset(filelist, preprocess=add_ens_dim)
    (ds_test['geopotential'].isel(time=-1).sel(level=500).std('longitude').compute()/ \
     ds_test['geopotential'].isel(time= 0).sel(level=500).std('longitude').compute()).T \
        .plot(cmap='PiYG_r', levels=[0.5, 0.75, 1, 1.25, 1.5, 2.5, 5, 10, 20])
    plt.title('Ratio of Std.Dev. by Latitude \n' + \
              pd.to_datetime(ds_test.time[-1].values).strftime('%Y-%m-%d') + ' vs ' + \
              pd.to_datetime(ds_test.time[0].values).strftime('%Y-%m-%d'))

For reference, the same analysis of a good date looks like this:

Like Stephan wrote, we are still working on instability issues.
In some simulations I found that there is an early drift of the global mean pressure surface (which happens a lot before the actual instability). This drift might be related to the sharp topography we are using (as we have not smoothed the orography). We are currently working on a fix to this issue, but even after this fix it won't solve all instabilities.

Interesting. Thanks for your quick replies. I looked at your paper figures and some of my cases. I agree that the instability often appears to originate from the near-surface. The most common mode of failure appears to be:

Near-surface (gravity?) waves develop, propagate, and amplify in the tropics.
Upward propagation deposits momentum in the upper troposphere and stratosphere.
The waves extend poleward and gradually contaminate the whole atmosphere.

The good side of the story is that such propagating behaviors are consistent with physics. It also indicates the model may capture processes related to the stratosphere-troposphere coupling, which is a weakness for many physical models and is useful for long-range predictions. Whether NeuralGCM does better remains to be determined.
For the instability, my guesses are: 1) smoothing the topography and tweaking the settings of lower boundaries probably can help; 2) if the dynamical core model has hyperdiffusion parameters, tuning it may help dampen some initial fine-scale noises.


[CI/CD] Write Github actions to build precompiled plugins

Write Github actions to automate building and optionally releasing web3.unreal for different engine versions so that a working precompiled plugin is always available and the build steps are transparent and through a trusted third party.
Engine versions that should be supported are 4.27, 5.0, 5.1 although it may not be necessary to build 3 separate times for full compatibility.

use this command to build the plugin Engine\Build\BatchFiles\RunUAT.bat BuildPlugin -Plugin=[Path to .uplugin file, must be outside engine directory] -Package=[Output directory] -Rocket
as mentioned on https://www.unrealengine.com/en-US/marketplace-guidelines#263b


fix access HMS need ugiDoAs

Proposed changes
introduced from  https://github.com/apache/doris/pull/30595

这是来自QQ邮箱的假期自动回复邮件。


investigate checking for and showing captured outputs in panos skillets

Currently, displaying outputs requires a workflow and template. However, we can check if there is no workflow, but we do find captured outputs, then possibly show the results screen

also, possibly have a custom label to point to an appropriate template skillet to use to display the results.
This would be ignored in a workflow, but for a simple panos type skillet, just look for a label called 'output_template' then attempt to find and load that template skillet and display the rendered output in the results screen (or possibly a special template output page)


Graphs with no data

for example
Average price by buyer status in United Kingdom
currently we just have an empty graph - is there a better response we can provide for the user to indicate no data presennt?

Annotate the graph with 'no data for these dates/region'

Fix deployed.

'Sorry, there is no buyer status data available for United Kingdom. Please select a different location.' is now visible on the graph in place of no data - happy to close


Minor typo

heck -> check

@fonio Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

@fonio Thank you for signing the Contributor License Agreement!


Allow user to force the export of a box file.

Finished up the wiring for --force on vagrant basebox export boxname.

this functionality is implemented in the new branch veewee03 in commit - e0145afafb7a0976f61ef660933c32950d90736a


Plus login UI

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

36 of 38 (94.74%)  changed or added relevant lines in 3 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.001%) to 99.571%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/modules/menu/components/mainMenu/content/misc/BvvMiscContentPanel.js
13
15
86.67%

Totals

Change from base Build<PHONE_NUMBER>:
0.001%

Covered Lines:
12082

Relevant Lines:
12088

💛  - Coveralls


chore(master): release 1.1.72

:robot: I have created a release beep boop
1.1.72 (2023-09-04)
Miscellaneous

deps: update dependency ergebnis/composer-normalize to v2.36.0 (80fa484)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wayofdev/laravel-stripe-webhooks/releases/tag/v1.1.72 :sunflower:


Linearity check

Problem
This picture compares a sampled posterior (blue) with the VB posterior (red) and I assume the sampled results to be correct. E_beam and E_conn are MVN model parameters, Lambda is the Gamma noise precision.

The individual parameters are not normally distributed.
By definition, the MVN posterior cannot capture the curved covariance.

This boils down to the fact that a for a nonlinear model the prior and the posterior are not conjugate anymore (right?!). But even though our model is indeed nonlinear, the linearization around a narrow posterior distribution may still by quite linear. So I would like to provide some (optional) linearity checks that warn the user if the linearization assumption is bad at the posterior mean. This matters, if you want to evaluate the model at the tails of the posterior distribution, as the posterior MVN may significantly differ from the true posterior (see figure).
Goal

Define and quantify good and bad in the paragraph above.
Very optional: Derive suggestions for parameter transformations like The linearization of 'E_beam' of has a linearity of 0.2 (bad!), the parametrization '1/E_beam' would have a linearity of 0.96 (good).

Possible solutions
The basis could be a comparison of our model error function M at some point with the posterior-linearized M_lin. For a scalar model error with one parameter theta, we could take a set of points (e.g. theta_i = mean + i * sd for i [-4, -3, ..., 4]) and compare M(theta_i) [as a data set] and M_lin(theta_i) [as our prediction] using R².

How do deal with multiple parameters?

Doing it for each parameter individually could be sufficient.

The model error is vector valued. How do deal with that?

We could compute R² for entry individually. If each entry has a meaning (e.g. sensor 4 at time step 17) that could be indeed interesting to see. Or we return some mean(R²).
Is there something like R² for higher dimensional data. Maybe this?

Bonus: The possible transformations could be explored by a least square fit of M(theat_i) to a set of predefined nonlinear models (log(theta), exp(theta), 1/theta, ...).
Discussion
Would you find that useful?
Any ideas on how to define the linearity?

You could try to compute the diagonal entries of the second derivates (so for a single parameter) at the MAP and try to estimate the error resulting from that onto the posterior (sum_i dTheta_post_mean/dH2 * dH2) und analog dTheta_post_std/dH2 * dH2.

#90 Tries to provide a solution.


Obsoletion notice: GO:0033561 regulation of water loss via skin

Dear all,
The proposal has been made to obsolete GO:0033561 regulation of water loss via skin. The reason for obsoletion is that water loss from the skin is a readout, not a specific process, either for 'GO:0043589 skin morphogenesis' or 'GO:0098773 skin epidermis development'. There are 6 EXP annotations to this term, by MGI, RGD and UniProt, see https://github.com/geneontology/go-annotation/issues/4345.
There are no mappings to these terms, these terms are not present in any subsets.
You can comment on the ticket: https://github.com/geneontology/go-ontology/issues/24298
Thanks, Pascale

Child GO:0061436 establishment of skin barrier: move under GO:0098773 ! skin epidermis development


WIP - log4j config update

The current LoggingUtils class only logs stack traces if debug level is turned on for the particular logger logging the exception.
I like to see stack traces if errors are happening and not have to wait to hear about a problem, turn on debug and then recreate the problem to see the stack trace.
Stack traces do make a mess of the logs so this config puts them in their own log file where they can be matched up via timestamp to messages from console or from regular log file where stack traces are turned off by default.
The old behavior (stack traces in console or file and no separate stack trace file) can be achieved via system properties or updating the log4j2 properties.
Old/Current behavior could be achieved via:
-Dlog.console.stacktraces=true
-Dlog.file.stacktraces=true
-Dlog.stacktraceappender=null
-Dlog.include.location=true

This also changes the way Async logging is turned on and there are fairly significant performance benefits to doing it this way according to this document: ("all async" method vs. using AsyncLogger or AsyncAppender)
Log4j "all async" Logging
Turning on AsyncLogging would be done via:
-Dlog4j2.contextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector

I have seen cases in the past during development where CAS dies on startup and async logging is not flushed. With this config as the default, most users would have regular logging during development and could turn on async logging when their server is in production and performance matters.
I also disabled location info (includeLocation) by default and made it configurable b/c the log4j2 docs say it is 30-100 times slower when doing async logging and I don't see where the location info is being used in the pattern layouts.
The benefit of LoggingUtils is that it replaces null messages with the classname of the exception so logger.error(e.getMessage()); is more useful if the message is null.
Another benefit is that it replaces the following with a one liner:
catch (Exception e) {
  if (logger.isDebugEnable()) {
    logger.error(msg, e);
  } else {
    logger.error(msg);
  }

I would rather go ahead and log the exceptions to their own log file and not have to turn on debug to get the stack traces but I suppose it could be made configurable.
If there is a NPE or some other runtime exception, the stack trace can tell you where and the code can be updated to avoid that error. If there are expected types of exceptions and a desire to catch them and continue, I would rather catch those specific exceptions and log them at an appropriate level with no stack trace (if they are expected you already know where they came from), and still catch Exception if there is a desire to continue regardless but log the unexpected exception with a stack trace so it can be avoided or added to the expected exception list.
This is WIP pending feedback and because there is documentation to update (AsyncLogger -> Logger), other log4j2.xml files to update and I should probably test it.

This all looks great to me.
I'd only add that it would be best if org.apache.logging.log4j.core.async.AsyncLoggerContextSelector could in fact be the default, where folks could then turn this off via a setting. Are there any downsides to making the system be prod-ready by default besides the possible albeit rare flushing issues? My concern is that if we are asking folks to set -Dlog4j2.contextSelector=org.apache.logging.log4j.core.async.AsyncLoggerContextSelector, that's just one extra thing to set, to remember, to document, etc in scenarios where performance might be an issue and it would waste time and resources to figure out if perf is in fact hit by less-than-ideal logging config vs actually presenting the best possible config by default. Letting the system run at peak performance seems to come at no significant cost, and "It should just work" without extra magic settings....unless log4j sort of makes that difficult to configure as the default option?

The documentation doesn't mention a way to turn it on programmatically (that I saw), but I will look into whether the switch can be done after some classes have been loaded. The fact that they don't have a way to turn it on in log42.xml config makes me suspect that it is a decision that is made early on by one of the first classes loaded in log4j2.

If there is no option to make this be the default, then let's not add code to make it so since I imagine it would be difficult to write tests for this sort of thing. Rather, we could build support for the option in the overlay where the build script could auto-set the system property before launching the war, etc. Same goes for Docker builds too in the same overlay. I think that should be enough as a default option.

I have been trying to add a custom filter that would only log messages with a stack trace in a dedicated stack trace log file. I think I was probably having difficulties due to the way the CasAppender wraps the regular appender but it seems to work when I add the filter to the CasAppender. It might be better to make it so CasAppender just supports adding any filter rather than having it only accept this one type of filter. I will try that when I get a chance.
I added the shadowJar plugin which makes a file core/cas-server-core-logging-api/out/production/classes/META-INF/org/apache/logging/log4j/core/config/plugins/Log4j2Plugins.dat that helps Log4j2 find custom plugins, although it probably isn't necessary if the log4j2.xml file has packages="org.apereo.cas.logging". One or the other is probably sufficient.
This filter should allow for exceptions to be logged at higher levels (WARN/ERROR) without a stack trace and they will show up as one liners in the main logfile and the console but their stack trace will show up in the cas_stacktrace.log that someone can consult for the details. Alternatively, someone could get rid of that appender and just turn on stack traces for the main log file and/or the console appender.

Now async is on by default using log4j2.component.properties. This could be overridden in an overlay (or on command line) if someone didn't want async logging.

This may need some more documentation but at this point I am ready for feedback. Async is now on by default but someone in an overlay can turn it off by using system property or putting log4j2.component.properties in their WEB-INF/classes to override the one in in logging-api module that turns on async. My hope is that more bad things with exceptions can be logged at ERROR or WARN and not clutter up the main log files b/c exceptions will go to their own logfile (or be logged as DEBUG and force adjusting log level and re-creating error to get stack trace). I also would need to update log4j2.xml in the cas-overlay.
Log4j2 supports a programmatic property source interface that one can implement and it would use that to get properties instead of or in addition to log42.component.properties and I briefly went down road of letting async be turned on by a regular spring boot property, but all of that happens too late, long after log4j would have been initialized, although I think CAS may re-initialize log4j so maybe it would be there in time for that. It probably is simpler the way it is since most people won't adjust async.

This should be good to go. Would you mind updating logging/Logging.md with a few details on how one could tweak the async behavior? Just a few references to current behavior and why should be enough, as I don't expect many to go down this path, tweaking internals.

I updated logging.md.


Reduce dependency to jQuery only where really necessary

Not to load floatz.js or use ua-parser.js. Provide dependency matrix when it is necessary.

to

Also added log error messages if jQuery or ua-parser are not loaded (where necessary)