[Bug]: Unkown Exception was hit

What happened?
I'm working on a test repo in my company's org (hid the name in all the screenshots that I'm going to attach. We have a policy which keeps us from interacting with outside repos using our corporate account).
This repo has several open security vulnerabilities and has had them for a long time. Was originally used as a test repo for comparing Veracode to GHAS (honestly a pointless comparison, GHAS is better by miles).

When I run the action though, with v2.7.3 I get errors that cause the action to fail, as one would expect given these security alerts on that repo, but no information about which alert caused the issue. I also get at least one of this error each run: Unknown Exception was hit, please repo this to https://github.com/advanced-security/policy-as-code
This is the included ID that comes up in logs: 'A4D3:360A1:447E699:78AAC10:666203F8'
Workflow File:
name: Policy Testing - No General Workflow

on:
    pull_request:
        branches: main
    push:
        branches: main

# workflow or job level
permissions:
    contents: read
    security-events: read
    # pull request summaries
    pull-requests: write

jobs:
    policy-check:
        runs-on: ubuntu-latest
        name: Policy Testing

        steps:
            # Compliance
            - name: Advance Security Policy as Code
              uses<EMAIL_ADDRESS>              with:
                  # The owner/repo of where the policy is stored
                  policy: dat-freight-and-analytics/ghas-policy-as-code
                  # The local (within the workspace) or repository
                  policy-path: policies/default.yml
                  # The branch you want to target
                  policy-branch: main
                  policy-repo-token: ${{ secrets.GHAS_COMPLIANCE_PAT }}
                  argvs: '--display --pr-comment'

Policy Doc (which excludes licensing check):
# # Level Hierarchy
# - critical
# - high
# - error
# - medium
# - moderate
# - low
# - warning
# - notes

# default remediation policy
general:
  # All other blocks will be inheriting the remediate section if they don't have
  #  their own defined.
  remediate:
    # Only `errors` and above have got 7 days to remediate according to the
    #  policy
    errors: 90
    # Same here for anything regarding warnings but for 30 days
    warnings: 90

    # Any / All issues that haven't been defined by other catagories will have
    #  the following remediation policy applied.
    all: 90

# ------------ #

# the `codescanning` block will inherit the `general` block
codescanning:
  # If `level` is also set with `remediate` turned on then both the level check
  #  and time to remediate time frame checks are done.
  # In this example, if `level: error` is set and a warning is reported and
  #  violated the time to remediate check (has exceeded the time to fix the
  #  issue) then it will NOT be reported.
  level: error

  # Conditions will only trigger and raise an error when an exact match is hit
  # conditions:
  #   ids:
  #     # Code Scanning Rule identifier
  #     - js/sql-injection
  # # Ignores are run next so if an ignored rule is hit that matches the level, it will be skipped
  ignores:
    ids:
      - js/log-injection
    names:
      # Code Scanning Rule name
      - "Missing rate limiting"

# ------------ #

dependabot:
  # This block will not inherit the `general` remediate block
  remediate:
    # The team have 7 days before this starts crashing workflows / builds
    high: 7

  # Conditions will only trigger and raise an error when an exact match is hit
  # conditions:
  #   ids:
  #     # GitHub Security Advisory ID
  #     - GHSA-446m-mv8f-q348
  #     # CWE data from GitHub Advisory Database
  #     - CWE-89
  # # Ignores are run next so if an ignored rule is hit that matches the level, it will be skipped
  # ignores:
  #   ids:
  #     - GHSA-mh5c-679w-hh4r

# ------------ #

# licensing:
  # Licensing does not have `remediate` block as there are no dates associated
  #  with the discovery of a dependency with licensing issues. This may change
  #  in the future but currently isn't available.

  # # Conditions will only trigger and raise an error when an exact match is hit
  # conditions:
  #   ids:
  #     # License identifiers
  #     - GPL-2.0
  #     - GPL-3.0
  #   names:
  #     # Dependency Name (manager + name), best to use as this makes sure that
  #     #  the right package manager is used
  #     - maven://org.apache.struts
  #     # Dependency Short Name (just name)
  #     - org.apache.struts
  #     # Dependency Full Name (manager + name + version)
  #     - maven://org.apache.struts#2.0.5
  # warnings:
  #   ids:
  #     # Other is the 'Known Licensing' in GitHub Dependency Graph
  #     - Other
  #     # NA or Not Available is where the GitHub Dependency Graph has no data
  #     #  on the repository
  #     - NA
  # # Ignores are run next so if an ignored rule is hit that matches the level, it will be skipped
  # ignores:
  #   ids:
  #     - MIT License

# ------------ #

secretscanning:
  level: all
  remediate:
    # All secrets by default are set to 'critical' severity so only `critical`
    #  or `all` will work
    critical: 3

Version
v2 (current major version)
Where are you experiencing the issue?
GitHub Actions
Relevant log output
2024-06-06T18:45:53.3906058Z Current runner version: '2.317.0'
2024-06-06T18:45:53.3929208Z ##[group]Operating System
2024-06-06T18:45:53.3929815Z Ubuntu
2024-06-06T18:45:53.3930275Z 22.04.4
2024-06-06T18:45:53.3930597Z LTS
2024-06-06T18:45:53.3930908Z ##[endgroup]
2024-06-06T18:45:53.3931356Z ##[group]Runner Image
2024-06-06T18:45:53.3931788Z Image: ubuntu-22.04
2024-06-06T18:45:53.3932205Z Version: 20240603.1.0
2024-06-06T18:45:53.3933229Z Included Software: https://github.com/actions/runner-images/blob/ubuntu22/20240603.1/images/ubuntu/Ubuntu2204-Readme.md
2024-06-06T18:45:53.3934670Z Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20240603.1
2024-06-06T18:45:53.3935526Z ##[endgroup]
2024-06-06T18:45:53.3936007Z ##[group]Runner Image Provisioner
2024-06-06T18:45:53.3936468Z 2.0.370.1
2024-06-06T18:45:53.3936797Z ##[endgroup]
2024-06-06T18:45:53.3937984Z ##[group]GITHUB_TOKEN Permissions
2024-06-06T18:45:53.3939518Z Contents: read
2024-06-06T18:45:53.3940053Z Metadata: read
2024-06-06T18:45:53.3940635Z PullRequests: write
2024-06-06T18:45:53.3941214Z SecurityEvents: read
2024-06-06T18:45:53.3941621Z ##[endgroup]
2024-06-06T18:45:53.3943737Z Secret source: Actions
2024-06-06T18:45:53.3944470Z Prepare workflow directory
2024-06-06T18:45:53.4657177Z Prepare all required actions
2024-06-06T18:45:53.4814468Z Getting action download info
2024-06-06T18:45:53.6694692Z Download action repository<EMAIL_ADDRESS>(SHA:70331f3a4dd481cefa98f5341250ac3dea2a8d5f)
2024-06-06T18:45:54.2543433Z Complete job name: Policy Testing
2024-06-06T18:45:54.3710095Z ##[group]Run<EMAIL_ADDRESS>2024-06-06T18:45:54.3711195Z with:
2024-06-06T18:45:54.3712044Z   policy: ********/ghas-policy-as-code
2024-06-06T18:45:54.3713239Z   policy-path: policies/default.yml
2024-06-06T18:45:54.3714127Z   policy-branch: main
2024-06-06T18:45:54.3715927Z   policy-repo-token: ***
2024-06-06T18:45:54.3716910Z   argvs: --display --pr-comment
2024-06-06T18:45:54.3717640Z   severity: error
2024-06-06T18:45:54.3718482Z   repository: ********/vera-busted-01
2024-06-06T18:45:54.3719921Z   token: ***
2024-06-06T18:45:54.3720555Z   ref: refs/heads/main
2024-06-06T18:45:54.3721188Z   action: break
2024-06-06T18:45:54.3722072Z ##[endgroup]
2024-06-06T18:45:54.4118916Z ##[group]Run echo "Running Policy as Code..."
2024-06-06T18:45:54.4120122Z echo "Running Policy as Code..." This may be the result of a timeout, or it could be a GitHub bug. Please include `A4D3:360A1:447E699:78AAC10:666203F8` when reporting this issue."\n      }\n   ]\n}\n'
2024-06-06T18:46:26.5974152Z ERROR:root:Unknown Exception was hit, please repo this to https://github.com/advanced-security/policy-as-code
2024-06-06T18:46:26.5975415Z ERROR:root:Failed to get data from GraphQL API
2024-06-06T18:46:26.5977438Z Code Scanning violations :: 1
2024-06-06T18:46:26.5978802Z ##[endgroup]
2024-06-06T18:46:26.5979760Z ##[group]Dependabot Results
2024-06-06T18:46:26.5984124Z ##[warning] Unable to get Dependabot alerts :: REST Request failed :: Resource not accessible by integration
2024-06-06T18:46:26.5986508Z ##[warning] Trying GraphQL API
2024-06-06T18:46:26.5987140Z Total Dependabot Alerts :: 0
2024-06-06T18:46:26.5988066Z Dependabot violations :: 0
2024-06-06T18:46:26.5989130Z ##[endgroup]
2024-06-06T18:46:26.5990122Z ##[group]Dependency Graph
2024-06-06T18:46:26.5990728Z Total Dependency Graph :: 828
2024-06-06T18:46:26.5991304Z Dependency Graph violations :: 0
2024-06-06T18:46:26.5992350Z ##[endgroup]
2024-06-06T18:46:26.5993401Z ##[group]Dependency Graph Results - Licensing
2024-06-06T18:46:26.5996462Z ##[error]Unknown Exception was hit, please repo this to https://github.com/advanced-security/policy-as-code
2024-06-06T18:46:26.5998992Z ##[error]Failed to get data from GraphQL API
2024-06-06T18:46:26.8157408Z INFO:root:Total unacceptable alerts :: 3
2024-06-06T18:46:26.8158672Z ERROR:root:Unacceptable Threshold of Risk has been hit!
2024-06-06T18:46:26.8160247Z ##[group]Secret Scanning Results
2024-06-06T18:46:26.8161370Z ##[endgroup]
2024-06-06T18:46:26.8162138Z ##[group]Summary
2024-06-06T18:46:26.8162751Z Total unacceptable alerts :: 3
2024-06-06T18:46:26.8164446Z ##[error]Unacceptable Threshold of Risk has been hit!
2024-06-06T18:46:26.8343905Z ##[error]Process completed with exit code 1.
2024-06-06T18:46:26.8644825Z Cleaning up orphan processes

Code of Conduct

[X] I agree to follow this project's Code of Conduct

Also worth calling out, the above was from running directly against a Push to main. Here's a PR to main:

And the logs which did show errors, though they didn't show up in the PR comment:
2024-06-06T21:01:18.0645933Z ##[group]Operating System
2024-06-06T21:01:18.0646731Z Ubuntu
2024-06-06T21:01:18.0647121Z 22.04.4
2024-06-06T21:01:18.0647524Z LTS
2024-06-06T21:01:18.0647833Z ##[endgroup]
2024-06-06T21:01:18.0648436Z ##[group]Runner Image
2024-06-06T21:01:18.0649008Z Image: ubuntu-22.04
2024-06-06T21:01:18.0649392Z Version: 20240603.1.0
2024-06-06T21:01:18.0650431Z Included Software: https://github.com/actions/runner-images/blob/ubuntu22/20240603.1/images/ubuntu/Ubuntu2204-Readme.md
2024-06-06T21:01:18.0651984Z Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20240603.1
2024-06-06T21:01:18.0652892Z ##[endgroup]
2024-06-06T21:01:18.0653255Z ##[group]Runner Image Provisioner
2024-06-06T21:01:18.0653819Z 2.0.370.1
2024-06-06T21:01:18.0654206Z ##[endgroup]
2024-06-06T21:01:18.0655381Z ##[group]GITHUB_TOKEN Permissions
2024-06-06T21:01:18.0657160Z Contents: read
2024-06-06T21:01:18.0657605Z Metadata: read
2024-06-06T21:01:18.0658332Z PullRequests: write
2024-06-06T21:01:18.0658838Z SecurityEvents: read
2024-06-06T21:01:18.0659400Z ##[endgroup]
2024-06-06T21:01:18.0661505Z Secret source: Actions
2024-06-06T21:01:18.0662116Z Prepare workflow directory
2024-06-06T21:01:18.1286311Z Prepare all required actions
2024-06-06T21:01:18.1442730Z Getting action download info
2024-06-06T21:01:18.2818246Z Download action repository<EMAIL_ADDRESS>(SHA:70331f3a4dd481cefa98f5341250ac3dea2a8d5f)
2024-06-06T21:01:18.9050398Z Complete job name: Policy Testing
2024-06-06T21:01:19.0228835Z ##[group]Run<EMAIL_ADDRESS>2024-06-06T21:01:19.0229957Z with:
2024-06-06T21:01:19.0231023Z   policy: ********/ghas-policy-as-code
2024-06-06T21:01:19.0232164Z   policy-path: policies/default.yml
2024-06-06T21:01:19.0233125Z   policy-branch: main
2024-06-06T21:01:19.0235254Z   policy-repo-token: ***
2024-06-06T21:01:19.0236135Z   argvs: --display --pr-comment
2024-06-06T21:01:19.0237201Z   severity: error
2024-06-06T21:01:19.0238174Z   repository: ********/vera-busted-01
2024-06-06T21:01:19.0239564Z   token: ***
2024-06-06T21:01:19.0240394Z   ref: refs/pull/100/merge
2024-06-06T21:01:19.0241112Z   action: break
2024-06-06T21:01:19.0241837Z ##[endgroup]
2024-06-06T21:01:19.0635665Z ##[group]Run echo "Running Policy as Code..."
2024-06-06T21:01:19.0636895Z echo "Running Policy as Code..."
2024-06-06T21:01:19.0639879Z export PYTHONPATH=/home/runner/work/_actions/advanced-security/policy-as-code/v2.7.3:/home/runner/work/_actions/advanced-security/policy-as-code/v2.7.3/vendor
2024-06-06T21:01:19.0642429Z python3 -m ghascompliance \
2024-06-06T21:01:19.0643598Z   --severity "error" \
2024-06-06T21:01:19.0644556Z   --action "break" \
2024-06-06T21:01:19.0645991Z   --github-token "***" \
2024-06-06T21:01:19.0648725Z   --policy-repo-token "***" \
2024-06-06T21:01:19.0650121Z   --github-repository "********/vera-busted-01" \
2024-06-06T21:01:19.0651577Z   --github-ref "refs/pull/100/merge" \
2024-06-06T21:01:19.0653208Z   --github-policy "********/ghas-policy-as-code" \
2024-06-06T21:01:19.0654803Z   --github-policy-path "policies/default.yml" \
2024-06-06T21:01:19.0656049Z   --github-policy-branch "main" \
2024-06-06T21:01:19.0657254Z   --display --pr-comment
2024-06-06T21:01:19.0769040Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
2024-06-06T21:01:19.0770447Z ##[endgroup]
2024-06-06T21:01:19.1132318Z Running Policy as Code...
2024-06-06T21:01:19.4175147Z INFO:root:GitHub Repository :: ********/vera-busted-01
2024-06-06T21:01:19.4176495Z INFO:root:GitHub Instance :: https://github.com
2024-06-06T21:01:19.4177739Z INFO:root:GitHub Reference (branch/pr) :: refs/pull/100/merge
2024-06-06T21:01:19.4179324Z INFO:root:Loading Policy as Code from Repository - https://github.com/********/ghas-policy-as-code/policies/default.yml
2024-06-06T21:01:19.4181754Z INFO:root:Cloning policy repo - ********/ghas-policy-as-code@main
2024-06-06T21:01:19.9127643Z INFO:root:Loading policy file - /tmp/repo/policies/default.yml
2024-06-06T21:01:19.9129738Z INFO:root:Enabling Time to Remediate (global) :: codescanning
2024-06-06T21:01:19.9131277Z INFO:root:Policy loaded successfully
2024-06-06T21:01:19.9132528Z INFO:root:Saving Policy...
2024-06-06T21:01:19.9133502Z INFO:root:Policy saved
2024-06-06T21:01:19.9134598Z INFO:root:Finished loading policy
2024-06-06T21:01:19.9135585Z INFO:root:Policy as Code Summary:
2024-06-06T21:01:19.9136795Z INFO:root:```
2024-06-06T21:01:19.9137779Z INFO:root:general: 'error'
2024-06-06T21:01:19.9138862Z INFO:root:codescanning: 'error'
2024-06-06T21:01:19.9140063Z INFO:root:dependabot: 'None'
2024-06-06T21:01:19.9141367Z INFO:root:secretscanning: 'all'
2024-06-06T21:01:19.9142505Z INFO:root:licensing: 'error'
2024-06-06T21:01:19.9143765Z INFO:root:dependencies: 'error'
2024-06-06T21:01:19.9144568Z INFO:root:```
2024-06-06T21:01:19.9145463Z INFO:root:Code Scanning Alerts from Pull Request (alert diff)
2024-06-06T21:01:20.5919271Z INFO:root:Total Code Scanning Alerts :: 0
2024-06-06T21:01:20.5920165Z INFO:root:Code Scanning violations :: 0
2024-06-06T21:01:20.5921141Z INFO:root:Dependabot Alerts from Pull Request
2024-06-06T21:01:20.8783609Z WARNING:ghastoolkit.octokit.dependencygraph:Failed to get dependencies from Pull Request
2024-06-06T21:01:20.8785808Z WARNING:ghastoolkit.octokit.dependencygraph:Make sure Advanced Security is enabled and token permissions are correct
2024-06-06T21:01:20.8787227Z INFO:root:Total Dependabot Alerts :: 0
2024-06-06T21:01:20.8788023Z INFO:root:Dependabot violations :: 0
2024-06-06T21:01:20.8794187Z INFO:root:Dependencies from Pull Request
2024-06-06T21:01:21.0944357Z WARNING:ghastoolkit.octokit.dependencygraph:Failed to get dependencies from Pull Request
2024-06-06T21:01:21.0946912Z WARNING:ghastoolkit.octokit.dependencygraph:Make sure Advanced Security is enabled and token permissions are correct
2024-06-06T21:01:21.0949051Z INFO:root:Total Dependency Graph :: 0
2024-06-06T21:01:21.0950268Z INFO:root:Dependency Graph violations :: 0
2024-06-06T21:01:21.0956104Z INFO:root:Dependencies from Pull Request
2024-06-06T21:01:21.2505744Z WARNING:ghastoolkit.octokit.dependencygraph:Failed to get dependencies from Pull Request
2024-06-06T21:01:21.2513117Z WARNING:ghastoolkit.octokit.dependencygraph:Make sure Advanced Security is enabled and token permissions are correct
2024-06-06T21:01:21.2562379Z INFO:root:Loaded extra licensing information :: 9459
2024-06-06T21:01:21.2563969Z INFO:root:Total Dependencies in Graph :: 0
2024-06-06T21:01:21.2565366Z INFO:root:Dependency Graph violations :: 0
2024-06-06T21:01:21.6930414Z INFO:root:No exisiting comment from PaC, adding a new comment...
2024-06-06T21:01:22.2136460Z INFO:root:Total unacceptable alerts :: 1
2024-06-06T21:01:22.2143174Z ERROR:root:Unacceptable Threshold of Risk has been hit!
2024-06-06T21:01:22.2144088Z  _____  _   _   ___   _____ _____                       _ _
2024-06-06T21:01:22.2145485Z |  __ \| | | | / _ \ /  ___/  __ \                     | (_)
2024-06-06T21:01:22.2147355Z | |  \/| |_| |/ /_\ \\ `--.| /  \/ ___  _ __ ___  _ __ | |_  __ _ _ __   ___ ___
2024-06-06T21:01:22.2148596Z | | __ |  _  ||  _  | `--. \ |    / _ \| '_ ` _ \| '_ \| | |/ _` | '_ \ / __/ _ \
2024-06-06T21:01:22.2150108Z | |_\ \| | | || | | |/\__/ / \__/\ (_) | | | | | | |_) | | | (_| | | | | (_|  __/
2024-06-06T21:01:22.2151402Z  \____/\_| |_/\_| |_/\____/ \____/\___/|_| |_| |_| .__/|_|_|\__,_|_| |_|\___\___|
2024-06-06T21:01:22.2152832Z                                                  | |
2024-06-06T21:01:22.2154973Z                                                  |_|         v2.7.3
2024-06-06T21:01:22.2155838Z     GitHub Advanced Security Policy as Code by GeekMasher
2024-06-06T21:01:22.2156365Z
2024-06-06T21:01:22.2157046Z GitHub Repository :: ********/vera-busted-01
2024-06-06T21:01:22.2158277Z GitHub Instance :: https://github.com
2024-06-06T21:01:22.2159056Z GitHub Reference (branch/pr) :: refs/pull/100/merge
2024-06-06T21:01:22.2172540Z ##[group]Policy as Code
2024-06-06T21:01:22.2174004Z Loading Policy as Code from Repository - https://github.com/********/ghas-policy-as-code/policies/default.yml
2024-06-06T21:01:22.2175821Z Cloning policy repo - ********/ghas-policy-as-code@main
2024-06-06T21:01:22.2176995Z Loading policy file - /tmp/repo/policies/default.yml
2024-06-06T21:01:22.2177846Z Enabling Time to Remediate (global) :: codescanning
2024-06-06T21:01:22.2178719Z Policy loaded successfully
2024-06-06T21:01:22.2179294Z Saving Policy...
2024-06-06T21:01:22.2179749Z Policy saved
2024-06-06T21:01:22.2180375Z Finished loading policy
2024-06-06T21:01:22.2180946Z Policy as Code Summary:
2024-06-06T21:01:22.2181460Z ```
2024-06-06T21:01:22.2182067Z general: 'error'
2024-06-06T21:01:22.2182645Z codescanning: 'error'
2024-06-06T21:01:22.2183262Z dependabot: 'None'
2024-06-06T21:01:22.2183951Z secretscanning: 'all'
2024-06-06T21:01:22.2184549Z licensing: 'error'
2024-06-06T21:01:22.2185162Z dependencies: 'error'
2024-06-06T21:01:22.2185890Z ```
2024-06-06T21:01:22.2186877Z ##[endgroup]
2024-06-06T21:01:22.2188019Z ##[group]Code Scanning Results
2024-06-06T21:01:22.2188808Z Code Scanning Alerts from Pull Request (alert diff)
2024-06-06T21:01:22.2189602Z Total Code Scanning Alerts :: 0
2024-06-06T21:01:22.2190673Z Code Scanning violations :: 0
2024-06-06T21:01:22.2191562Z ##[endgroup]
2024-06-06T21:01:22.2192392Z ##[group]Dependabot Results
2024-06-06T21:01:22.2192994Z Dependabot Alerts from Pull Request
2024-06-06T21:01:22.2193639Z Total Dependabot Alerts :: 0
2024-06-06T21:01:22.2194323Z Dependabot violations :: 0
2024-06-06T21:01:22.2195278Z ##[endgroup]
2024-06-06T21:01:22.2196202Z ##[group]Dependency Graph
2024-06-06T21:01:22.2196999Z Dependencies from Pull Request
2024-06-06T21:01:22.2197668Z Total Dependency Graph :: 0
2024-06-06T21:01:22.2198476Z Dependency Graph violations :: 0
2024-06-06T21:01:22.2199501Z ##[endgroup]
2024-06-06T21:01:22.2200703Z ##[group]Dependency Graph Results - Licensing
2024-06-06T21:01:22.2201494Z Dependencies from Pull Request
2024-06-06T21:01:22.2202176Z Loaded extra licensing information :: 9459
2024-06-06T21:01:22.2203103Z Total Dependencies in Graph :: 0
2024-06-06T21:01:22.2203814Z Dependency Graph violations :: 0
2024-06-06T21:01:22.2204967Z ##[endgroup]
2024-06-06T21:01:22.2205878Z ##[group]Secret Scanning Results
2024-06-06T21:01:22.2206987Z ##[endgroup]
2024-06-06T21:01:22.2207797Z ##[group]Summary
2024-06-06T21:01:22.2209308Z ##[group]Pull Request comment
2024-06-06T21:01:22.2210024Z No exisiting comment from PaC, adding a new comment...
2024-06-06T21:01:22.2211325Z ##[endgroup]
2024-06-06T21:01:22.2211882Z Total unacceptable alerts :: 1
2024-06-06T21:01:22.2242834Z ##[error]Unacceptable Threshold of Risk has been hit!
2024-06-06T21:01:22.2333189Z ##[error]Process completed with exit code 1.
2024-06-06T21:01:22.2623830Z Cleaning up orphan processes

This one is really difficult to figure out for me. The individual log lines show no issues, but then the action fails saying 'Total unacceptable alerts :: 1`. So the action fails, blocking the merge, but no info given in the comment as to why. And of course not consistent with the results originally added to this Issue

I mean it obviously says it failed its API calls, but this is the same workflow that ran on the push to main, so it's not clear why that was the case

@Brutalbeard this might be an issue with the token permissions. Secret Scanning API might not be accessible via the normal Actions tokens.
You can fix this by using and setting up a GitHub App + using this action from one of my colleagues:
https://github.com/peter-murray/workflow-application-token-action
You'll have to set the policy-as-code token to the output of the application token action
A similar example can be found here
https://github.com/advanced-security/policy-as-code/blob/main/examples/workflows/appAuth.yml

Testing complete, but still not happy. Not seeing any issue pulling info, and in logs it seems to be finding some issues, but nothing in the comments on PRs. Would think there'd be a link directly to the violating alert of each type? At least a count?
I created an app with the following permissions:

Actions - Read Only
Code scanning alerts - Read Only
Contents - Read Only
Custom properties - Read Only (may be using this at some point)
Dependabot alerts - Read Only
Metadata - Read Only
Pull requests - Read/Write
Repository security advisories - Read Only
Secret scanning alerts - Read Only

Updated workflow file:
name: Policy Testing - No General Workflow

on:
    pull_request:
        branches: main
    push:
        branches: main

jobs:
    policy-check:
        runs-on: ubuntu-latest
        name: Policy Testing

        steps:
            - name: Get Token
              id: get_workflow_token
              uses: peter-murray/workflow-application-token-action@v3
              with:
                  application_id: ${{ secrets.GHAS_APPLICATION_ID }}
                  application_private_key: ${{ secrets.GHAS_APPLICATION_PRIVATE_KEY }}

            # Compliance
            - name: Advance Security Policy as Code
              uses<EMAIL_ADDRESS>              with:
                  token: ${{ steps.get_workflow_token.outputs.token }}
                  # The owner/repo of where the policy is stored
                  policy: dat-freight-and-analytics/ghas-policy-as-code
                  # The local (within the workspace) or repository
                  policy-path: policies/default.yml
                  # The branch you want to target
                  policy-branch: main
                  policy-repo-token: ${{ secrets.GHAS_COMPLIANCE_PAT }}
                  argvs: "--display --pr-comment --is-github-app-token"

Results:
PR Logs:
2024-06-07T19:17:48.7373199Z Current runner version: '2.317.0'
2024-06-07T19:17:48.7397894Z ##[group]Operating System
2024-06-07T19:17:48.7398775Z Ubuntu
2024-06-07T19:17:48.7399427Z 22.04.4
2024-06-07T19:17:48.7400017Z LTS
2024-06-07T19:17:48.7400571Z ##[endgroup]
2024-06-07T19:17:48.7401229Z ##[group]Runner Image
2024-06-07T19:17:48.7401965Z Image: ubuntu-22.04
2024-06-07T19:17:48.7402567Z Version: 20240603.1.0
2024-06-07T19:17:48.7404074Z Included Software: https://github.com/actions/runner-images/blob/ubuntu22/20240603.1/images/ubuntu/Ubuntu2204-Readme.md
2024-06-07T19:17:48.7406073Z Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20240603.1
2024-06-07T19:17:48.7407359Z ##[endgroup]
2024-06-07T19:17:48.7408039Z ##[group]Runner Image Provisioner
2024-06-07T19:17:48.7408771Z 2.0.370.1
2024-06-07T19:17:48.7409415Z ##[endgroup]
2024-06-07T19:17:48.7412956Z ##[group]GITHUB_TOKEN Permissions
2024-06-07T19:17:48.7414886Z Actions: write
2024-06-07T19:17:48.7415851Z Attestations: write
2024-06-07T19:17:48.7416602Z Checks: write
2024-06-07T19:17:48.7417286Z Contents: write
2024-06-07T19:17:48.7417901Z Deployments: write
2024-06-07T19:17:48.7418593Z Discussions: write
2024-06-07T19:17:48.7419270Z Issues: write
2024-06-07T19:17:48.7419854Z Metadata: read
2024-06-07T19:17:48.7420515Z Packages: write
2024-06-07T19:17:48.7421137Z Pages: write
2024-06-07T19:17:48.7421795Z PullRequests: write
2024-06-07T19:17:48.7422493Z RepositoryProjects: write
2024-06-07T19:17:48.7423523Z SecurityEvents: write
2024-06-07T19:17:48.7424297Z Statuses: write
2024-06-07T19:17:48.7424960Z ##[endgroup]
2024-06-07T19:17:48.7427479Z Secret source: Actions
2024-06-07T19:17:48.7428455Z Prepare workflow directory
2024-06-07T19:17:48.8049498Z Prepare all required actions
2024-06-07T19:17:48.8206468Z Getting action download info
2024-06-07T19:17:48.9492177Z Download action repository 'peter-murray/workflow-application-token-action@v3' (SHA:dc0413987a085fa17d19df9e47d4677cf81ffef3)
2024-06-07T19:17:49.3092927Z Download action repository<EMAIL_ADDRESS>(SHA:70331f3a4dd481cefa98f5341250ac3dea2a8d5f)
2024-06-07T19:17:49.7811062Z Complete job name: Policy Testing
2024-06-07T19:17:49.8809345Z ##[group]Run peter-murray/workflow-application-token-action@v3
2024-06-07T19:17:49.8810242Z with:
2024-06-07T19:17:49.8810759Z   application_id: ***
2024-06-07T19:17:49.8826764Z   application_private_key: ***
2024-06-07T19:17:49.8827371Z   revoke_token: false
2024-06-07T19:17:49.8827842Z ##[endgroup]
2024-06-07T19:17:50.1691350Z Found GitHub Application: GHAS-Policy-as-Code
2024-06-07T19:17:50.1694658Z Obtaining application installation for repository: ********/vera-busted-01
2024-06-07T19:17:50.3214813Z {"token":"***","expires_at":"2024-06-07T20:17:50Z","permissions":{"actions":"read","contents":"read","metadata":"read","pull_requests":"write","repository_advisories":"read","repository_custom_properties":"read","secret_scanning_alerts":"read","security_events":"read","vulnerability_alerts":"read"},"repository_selection":"selected"}
2024-06-07T19:17:50.3218774Z Successfully generated an access token for application.
2024-06-07T19:17:50.3492894Z ##[group]Run<EMAIL_ADDRESS>2024-06-07T19:17:50.3493670Z with:
2024-06-07T19:17:50.3494300Z   token: ***
2024-06-07T19:17:50.3494903Z   policy: ********/ghas-policy-as-code
2024-06-07T19:17:50.3495689Z   policy-path: policies/default.yml
2024-06-07T19:17:50.3496288Z   policy-branch: main
2024-06-07T19:17:50.3497497Z   policy-repo-token: ***
2024-06-07T19:17:50.3498135Z   argvs: --display --pr-comment --is-github-app-token
2024-06-07T19:17:50.3498862Z   severity: error
2024-06-07T19:17:50.3499440Z   repository: ********/vera-busted-01
2024-06-07T19:17:50.3500192Z   ref: refs/pull/100/merge
2024-06-07T19:17:50.3500701Z   action: break
2024-06-07T19:17:50.3501135Z ##[endgroup]
2024-06-07T19:17:50.3761337Z ##[group]Run echo "Running Policy as Code..."
2024-06-07T19:17:50.3762156Z echo "Running Policy as Code..."
2024-06-07T19:17:50.3764233Z export PYTHONPATH=/home/runner/work/_actions/advanced-security/policy-as-code/v2.7.3:/home/runner/work/_actions/advanced-security/policy-as-code/v2.7.3/vendor
2024-06-07T19:17:50.3765938Z python3 -m ghascompliance \
2024-06-07T19:17:50.3766581Z   --severity "error" \
2024-06-07T19:17:50.3767144Z   --action "break" \
2024-06-07T19:17:50.3768089Z   --github-token "***" \
2024-06-07T19:17:50.3769516Z   --policy-repo-token "***" \
2024-06-07T19:17:50.3770437Z   --github-repository "********/vera-busted-01" \
2024-06-07T19:17:50.3771432Z   --github-ref "refs/pull/100/merge" \
2024-06-07T19:17:50.3772393Z   --github-policy "********/ghas-policy-as-code" \
2024-06-07T19:17:50.3773446Z   --github-policy-path "policies/default.yml" \
2024-06-07T19:17:50.3774262Z   --github-policy-branch "main" \
2024-06-07T19:17:50.3775052Z   --display --pr-comment --is-github-app-token
2024-06-07T19:17:50.3850083Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
2024-06-07T19:17:50.3850907Z ##[endgroup]
2024-06-07T19:17:50.4008351Z Running Policy as Code...
2024-06-07T19:17:50.6520806Z INFO:root:GitHub Repository :: ********/vera-busted-01
2024-06-07T19:17:50.6535755Z INFO:root:GitHub Instance :: https://github.com
2024-06-07T19:17:50.6537557Z INFO:root:GitHub Reference (branch/pr) :: refs/pull/100/merge
2024-06-07T19:17:50.6540799Z INFO:root:Loading Policy as Code from Repository - https://github.com/********/ghas-policy-as-code/policies/default.yml
2024-06-07T19:17:50.6544182Z INFO:root:Cloning policy repo - ********/ghas-policy-as-code@main
2024-06-07T19:17:51.0965400Z INFO:root:Loading policy file - /tmp/repo/policies/default.yml
2024-06-07T19:17:51.0967174Z INFO:root:Enabling Time to Remediate (global) :: codescanning
2024-06-07T19:17:51.0968624Z INFO:root:Policy loaded successfully
2024-06-07T19:17:51.0969816Z INFO:root:Saving Policy...
2024-06-07T19:17:51.0970844Z INFO:root:Policy saved
2024-06-07T19:17:51.0971846Z INFO:root:Finished loading policy
2024-06-07T19:17:51.0972960Z INFO:root:Policy as Code Summary:
2024-06-07T19:17:51.0974294Z INFO:root:```
2024-06-07T19:17:51.0975284Z INFO:root:general: 'error'
2024-06-07T19:17:51.0976435Z INFO:root:codescanning: 'error'
2024-06-07T19:17:51.0977638Z INFO:root:dependabot: 'None'
2024-06-07T19:17:51.0978776Z INFO:root:secretscanning: 'all'
2024-06-07T19:17:51.0979897Z INFO:root:licensing: 'error'
2024-06-07T19:17:51.0981036Z INFO:root:dependencies: 'error'
2024-06-07T19:17:51.0982102Z INFO:root:```
2024-06-07T19:17:51.0984510Z INFO:root:Code Scanning Alerts from Pull Request (alert diff)
2024-06-07T19:17:51.6913342Z INFO:root:Total Code Scanning Alerts :: 0
2024-06-07T19:17:51.6914378Z INFO:root:Code Scanning violations :: 0
2024-06-07T19:17:51.6915336Z INFO:root:Dependabot Alerts from Pull Request
2024-06-07T19:17:52.0051375Z INFO:root:Total Dependabot Alerts :: 0
2024-06-07T19:17:52.0052640Z INFO:root:Dependabot violations :: 0
2024-06-07T19:17:52.0054064Z INFO:root:Dependencies from Pull Request
2024-06-07T19:17:52.1224153Z INFO:root:Total Dependency Graph :: 1
2024-06-07T19:17:52.1225197Z INFO:root:Dependency Graph violations :: 0
2024-06-07T19:17:52.1226115Z INFO:root:Dependencies from Pull Request
2024-06-07T19:17:52.2890834Z INFO:root:Loaded extra licensing information :: 9459
2024-06-07T19:17:52.2892473Z INFO:root:Total Dependencies in Graph :: 1
2024-06-07T19:17:52.2893975Z INFO:root:Dependency Graph violations :: 0
2024-06-07T19:17:52.6505311Z INFO:root:No exisiting comment from PaC, adding a new comment...
2024-06-07T19:17:53.0645769Z INFO:root:Total unacceptable alerts :: 1
2024-06-07T19:17:53.0647791Z ERROR:root:Unacceptable Threshold of Risk has been hit!
2024-06-07T19:17:53.0649619Z  _____  _   _   ___   _____ _____                       _ _
2024-06-07T19:17:53.0651180Z |  __ \| | | | / _ \ /  ___/  __ \                     | (_)
2024-06-07T19:17:53.0653444Z | |  \/| |_| |/ /_\ \\ `--.| /  \/ ___  _ __ ___  _ __ | |_  __ _ _ __   ___ ___
2024-06-07T19:17:53.0655181Z | | __ |  _  ||  _  | `--. \ |    / _ \| '_ ` _ \| '_ \| | |/ _` | '_ \ / __/ _ \
2024-06-07T19:17:53.0656532Z | |_\ \| | | || | | |/\__/ / \__/\ (_) | | | | | | |_) | | | (_| | | | | (_|  __/
2024-06-07T19:17:53.0657786Z  \____/\_| |_/\_| |_/\____/ \____/\___/|_| |_| |_| .__/|_|_|\__,_|_| |_|\___\___|
2024-06-07T19:17:53.0659027Z                                                  | |
2024-06-07T19:17:53.0660175Z                                                  |_|         v2.7.3
2024-06-07T19:17:53.0661287Z     GitHub Advanced Security Policy as Code by GeekMasher
2024-06-07T19:17:53.0662007Z
2024-06-07T19:17:53.0662732Z GitHub Repository :: ********/vera-busted-01
2024-06-07T19:17:53.0664290Z GitHub Instance :: https://github.com
2024-06-07T19:17:53.0665394Z GitHub Reference (branch/pr) :: refs/pull/100/merge
2024-06-07T19:17:53.0669074Z ##[group]Policy as Code
2024-06-07T19:17:53.0670993Z Loading Policy as Code from Repository - https://github.com/********/ghas-policy-as-code/policies/default.yml
2024-06-07T19:17:53.0673053Z Cloning policy repo - ********/ghas-policy-as-code@main
2024-06-07T19:17:53.0674591Z Loading policy file - /tmp/repo/policies/default.yml
2024-06-07T19:17:53.0675715Z Enabling Time to Remediate (global) :: codescanning
2024-06-07T19:17:53.0676853Z Policy loaded successfully
2024-06-07T19:17:53.0677780Z Saving Policy...
2024-06-07T19:17:53.0678518Z Policy saved
2024-06-07T19:17:53.0679441Z Finished loading policy
2024-06-07T19:17:53.0680363Z Policy as Code Summary:
2024-06-07T19:17:53.0681118Z ```
2024-06-07T19:17:53.0681959Z general: 'error'
2024-06-07T19:17:53.0682781Z codescanning: 'error'
2024-06-07T19:17:53.0683716Z dependabot: 'None'
2024-06-07T19:17:53.0684646Z secretscanning: 'all'
2024-06-07T19:17:53.0685492Z licensing: 'error'
2024-06-07T19:17:53.0686406Z dependencies: 'error'
2024-06-07T19:17:53.0687293Z ```
2024-06-07T19:17:53.0688766Z ##[endgroup]
2024-06-07T19:17:53.0690096Z ##[group]Code Scanning Results
2024-06-07T19:17:53.0691303Z Code Scanning Alerts from Pull Request (alert diff)
2024-06-07T19:17:53.0692494Z Total Code Scanning Alerts :: 0
2024-06-07T19:17:53.0693429Z Code Scanning violations :: 0
2024-06-07T19:17:53.0694933Z ##[endgroup]
2024-06-07T19:17:53.0696343Z ##[group]Dependabot Results
2024-06-07T19:17:53.0697394Z Dependabot Alerts from Pull Request
2024-06-07T19:17:53.0698369Z Total Dependabot Alerts :: 0
2024-06-07T19:17:53.0699390Z Dependabot violations :: 0
2024-06-07T19:17:53.0700878Z ##[endgroup]
2024-06-07T19:17:53.0702252Z ##[group]Dependency Graph
2024-06-07T19:17:53.0703766Z Dependencies from Pull Request
2024-06-07T19:17:53.0704699Z Total Dependency Graph :: 1
2024-06-07T19:17:53.0705748Z Dependency Graph violations :: 0
2024-06-07T19:17:53.0707364Z ##[endgroup]
2024-06-07T19:17:53.0708872Z ##[group]Dependency Graph Results - Licensing
2024-06-07T19:17:53.0709819Z Dependencies from Pull Request
2024-06-07T19:17:53.0711098Z Loaded extra licensing information :: 9459
2024-06-07T19:17:53.0712308Z Total Dependencies in Graph :: 1
2024-06-07T19:17:53.0713274Z Dependency Graph violations :: 0
2024-06-07T19:17:53.0714788Z ##[endgroup]
2024-06-07T19:17:53.0716154Z ##[group]Secret Scanning Results
2024-06-07T19:17:53.0717773Z ##[endgroup]
2024-06-07T19:17:53.0719208Z ##[group]Summary
2024-06-07T19:17:53.0720804Z ##[group]Pull Request comment
2024-06-07T19:17:53.0722015Z No exisiting comment from PaC, adding a new comment...
2024-06-07T19:17:53.0723708Z ##[endgroup]
2024-06-07T19:17:53.0724658Z Total unacceptable alerts :: 1
2024-06-07T19:17:53.0757327Z ##[error]Unacceptable Threshold of Risk has been hit!
2024-06-07T19:17:53.0847880Z ##[error]Process completed with exit code 1.
2024-06-07T19:17:53.0955322Z Post job cleanup.
2024-06-07T19:17:53.1836295Z There is no valid token stored in the action state, nothing to revoke.
2024-06-07T19:17:53.2039461Z Cleaning up orphan processes

Push to Main:
2024-06-07T19:14:41.1670384Z Current runner version: '2.317.0'
2024-06-07T19:14:41.1695789Z ##[group]Operating System
2024-06-07T19:14:41.1697329Z Ubuntu
2024-06-07T19:14:41.1697905Z 22.04.4
2024-06-07T19:14:41.1698519Z LTS
2024-06-07T19:14:41.1699087Z ##[endgroup]
2024-06-07T19:14:41.1699723Z ##[group]Runner Image
2024-06-07T19:14:41.1700425Z Image: ubuntu-22.04
2024-06-07T19:14:41.1701030Z Version: 20240603.1.0
2024-06-07T19:14:41.1702340Z Included Software: https://github.com/actions/runner-images/blob/ubuntu22/20240603.1/images/ubuntu/Ubuntu2204-Readme.md
2024-06-07T19:14:41.1704134Z Image Release: https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20240603.1
2024-06-07T19:14:41.1705271Z ##[endgroup]
2024-06-07T19:14:41.1705942Z ##[group]Runner Image Provisioner
2024-06-07T19:14:41.1706636Z 2.0.370.1
2024-06-07T19:14:41.1707239Z ##[endgroup]
2024-06-07T19:14:41.1710012Z ##[group]GITHUB_TOKEN Permissions
2024-06-07T19:14:41.1712019Z Actions: write
2024-06-07T19:14:41.1712806Z Attestations: write
2024-06-07T19:14:41.1713609Z Checks: write
2024-06-07T19:14:41.1714234Z Contents: write
2024-06-07T19:14:41.1714885Z Deployments: write
2024-06-07T19:14:41.1715480Z Discussions: write
2024-06-07T19:14:41.1716134Z Issues: write
2024-06-07T19:14:41.1716715Z Metadata: read
2024-06-07T19:14:41.1717351Z Packages: write
2024-06-07T19:14:41.1717998Z Pages: write
2024-06-07T19:14:41.1718519Z PullRequests: write
2024-06-07T19:14:41.1719218Z RepositoryProjects: write
2024-06-07T19:14:41.1719876Z SecurityEvents: write
2024-06-07T19:14:41.1720549Z Statuses: write
2024-06-07T19:14:41.1721214Z ##[endgroup]
2024-06-07T19:14:41.1723439Z Secret source: Actions
2024-06-07T19:14:41.1724337Z Prepare workflow directory
2024-06-07T19:14:41.2341945Z Prepare all required actions
2024-06-07T19:14:41.2497343Z Getting action download info
2024-06-07T19:14:41.3898704Z Download action repository 'peter-murray/workflow-application-token-action@v3' (SHA:dc0413987a085fa17d19df9e47d4677cf81ffef3)
2024-06-07T19:14:41.7180029Z Download action repository<EMAIL_ADDRESS>(SHA:70331f3a4dd481cefa98f5341250ac3dea2a8d5f)
2024-06-07T19:14:42.1740331Z Complete job name: Policy Testing
2024-06-07T19:14:42.2638384Z ##[group]Run peter-murray/workflow-application-token-action@v3
2024-06-07T19:14:42.2639444Z with:
2024-06-07T19:14:42.2640202Z   application_id: ***
2024-06-07T19:14:42.2655476Z   application_private_key: ***
2024-06-07T19:14:42.2656234Z   revoke_token: false
2024-06-07T19:14:42.2657283Z ##[endgroup]
2024-06-07T19:14:42.6243769Z Found GitHub Application: GHAS-Policy-as-Code
2024-06-07T19:14:42.6246268Z Obtaining application installation for repository: ********/vera-busted-01
2024-06-07T19:14:42.7553984Z {"token":"***","expires_at":"2024-06-07T20:14:42Z","permissions":{"actions":"read","contents":"read","metadata":"read","pull_requests":"write","repository_advisories":"read","repository_custom_properties":"read","secret_scanning_alerts":"read","security_events":"read","vulnerability_alerts":"read"},"repository_selection":"selected"}
2024-06-07T19:14:42.7558603Z Successfully generated an access token for application.
2024-06-07T19:14:42.7851607Z ##[group]Run<EMAIL_ADDRESS>2024-06-07T19:14:42.7852582Z with:
2024-06-07T19:14:42.7853586Z   token: ***
2024-06-07T19:14:42.7854744Z   policy: ********/ghas-policy-as-code
2024-06-07T19:14:42.7855833Z   policy-path: policies/default.yml
2024-06-07T19:14:42.7856998Z   policy-branch: main
2024-06-07T19:14:42.7858541Z   policy-repo-token: ***
2024-06-07T19:14:42.7859473Z   argvs: --display --pr-comment --is-github-app-token
2024-06-07T19:14:42.7860470Z   severity: error
2024-06-07T19:14:42.7861261Z   repository: ********/vera-busted-01
2024-06-07T19:14:42.7862250Z   ref: refs/heads/main
2024-06-07T19:14:42.7862974Z   action: break
2024-06-07T19:14:42.7863602Z ##[endgroup]
2024-06-07T19:14:42.8130917Z ##[group]Run echo "Running Policy as Code..."
2024-06-07T19:14:42.8132066Z echo "Running Policy as Code..."
2024-06-07T19:14:42.8134623Z export PYTHONPATH=/home/runner/work/_actions/advanced-security/policy-as-code/v2.7.3:/home/runner/work/_actions/advanced-security/policy-as-code/v2.7.3/vendor
2024-06-07T19:14:42.8136916Z python3 -m ghascompliance \
2024-06-07T19:14:42.8137913Z   --severity "error" \
2024-06-07T19:14:42.8138751Z   --action "break" \
2024-06-07T19:14:42.8139893Z   --github-token "***" \
2024-06-07T19:14:42.8141659Z   --policy-repo-token "***" \
2024-06-07T19:14:42.8142801Z   --github-repository "********/vera-busted-01" \
2024-06-07T19:14:42.8144078Z   --github-ref "refs/heads/main" \
2024-06-07T19:14:42.8145311Z   --github-policy "********/ghas-policy-as-code" \
2024-06-07T19:14:42.8146564Z   --github-policy-path "policies/default.yml" \
2024-06-07T19:14:42.8147668Z   --github-policy-branch "main" \
2024-06-07T19:14:42.8148767Z   --display --pr-comment --is-github-app-token
2024-06-07T19:14:42.8231249Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
2024-06-07T19:14:42.8232361Z ##[endgroup]
2024-06-07T19:14:42.8390457Z Running Policy as Code...
2024-06-07T19:14:43.1341572Z INFO:root:GitHub Repository :: ********/vera-busted-01
2024-06-07T19:14:43.1344139Z INFO:root:GitHub Instance :: https://github.com
2024-06-07T19:14:43.1345537Z INFO:root:GitHub Reference (branch/pr) :: refs/heads/main
2024-06-07T19:14:43.1347284Z INFO:root:Loading Policy as Code from Repository - https://github.com/********/ghas-policy-as-code/policies/default.yml
2024-06-07T19:14:43.1348725Z INFO:root:Cloning policy repo - ********/ghas-policy-as-code@main
2024-06-07T19:14:43.6258061Z INFO:root:Loading policy file - /tmp/repo/policies/default.yml
2024-06-07T19:14:43.6399641Z INFO:root:Enabling Time to Remediate (global) :: codescanning
2024-06-07T19:14:43.6401089Z INFO:root:Policy loaded successfully
2024-06-07T19:14:43.6402144Z INFO:root:Saving Policy...
2024-06-07T19:14:43.6403144Z INFO:root:Policy saved
2024-06-07T19:14:43.6404090Z INFO:root:Finished loading policy
2024-06-07T19:14:43.6405205Z INFO:root:Policy as Code Summary:
2024-06-07T19:14:43.6406277Z INFO:root:```
2024-06-07T19:14:43.6407251Z INFO:root:general: 'error'
2024-06-07T19:14:43.6408364Z INFO:root:codescanning: 'error'
2024-06-07T19:14:43.6409464Z INFO:root:dependabot: 'None'
2024-06-07T19:14:43.6410491Z INFO:root:secretscanning: 'all'
2024-06-07T19:14:43.6411640Z INFO:root:licensing: 'error'
2024-06-07T19:14:43.6412591Z INFO:root:dependencies: 'error'
2024-06-07T19:14:43.6413647Z INFO:root:```
2024-06-07T19:14:43.8118361Z INFO:root:Total Code Scanning Alerts :: 1
2024-06-07T19:14:43.8142207Z ERROR:root:CodeQL - 2023-10-30 20:34:07 - Inefficient regular expression
2024-06-07T19:14:43.8143887Z  _____  _   _   ___   _____ _____                       _ _
2024-06-07T19:14:43.8145272Z |  __ \| | | | / _ \ /  ___/  __ \                     | (_)
2024-06-07T19:14:43.8147428Z | |  \/| |_| |/ /_\ \\ `--.| /  \/ ___  _ __ ___  _ __ | |_  __ _ _ __   ___ ___
2024-06-07T19:14:43.8149015Z | | __ |  _  ||  _  | `--. \ |    / _ \| '_ ` _ \| '_ \| | |/ _` | '_ \ / __/ _ \
2024-06-07T19:14:43.8150518Z | |_\ \| | | || | | |/\__/ / \__/\ (_) | | | | | | |_) | | | (_| | | | | (_|  __/
2024-06-07T19:14:43.8151957Z  \____/\_| |_/\_| |_/\____/ \____/\___/|_| |_| |_| .__/|_|_|\__,_|_| |_|\___\___|
2024-06-07T19:14:43.8153214Z                                                  | |
2024-06-07T19:14:43.8154467Z                                                  |_|         v2.7.3
2024-06-07T19:14:43.8155766Z     GitHub Advanced Security Policy as Code by GeekMasher
2024-06-07T19:14:43.8156504Z
2024-06-07T19:14:43.8157209Z GitHub Repository :: ********/vera-busted-01
2024-06-07T19:14:43.8158721Z GitHub Instance :: https://github.com
2024-06-07T19:14:43.8160098Z GitHub Reference (branch/pr) :: refs/heads/main
2024-06-07T19:14:43.8164001Z ##[group]Policy as Code
2024-06-07T19:14:43.8166209Z Loading Policy as Code from Repository - https://github.com/********/ghas-policy-as-code/policies/default.yml
2024-06-07T19:14:43.8168755Z Cloning policy repo - ********/ghas-policy-as-code@main
2024-06-07T19:14:43.8170457Z Loading policy file - /tmp/repo/policies/default.yml
2024-06-07T19:14:43.8177133Z Enabling Time to Remediate (global) :: codescanning
2024-06-07T19:14:43.8178815Z Policy loaded successfully
2024-06-07T19:14:43.8179888Z Saving Policy...
2024-06-07T19:14:43.8180860Z Policy saved
2024-06-07T19:14:43.8181867Z Finished loading policy
2024-06-07T19:14:43.8183183Z Policy as Code Summary:
2024-06-07T19:14:43.8184051Z ```
2024-06-07T19:14:43.8185129Z general: 'error'
2024-06-07T19:14:43.8186284Z codescanning: 'error'
2024-06-07T19:14:43.8187429Z dependabot: 'None'
2024-06-07T19:14:43.8188592Z secretscanning: 'all'
2024-06-07T19:14:43.8189546Z licensing: 'error'
2024-06-07T19:14:43.8190623Z dependencies: 'error'
2024-06-07T19:14:43.8191555Z ```
2024-06-07T19:14:43.8194174Z ##[endgroup]
2024-06-07T19:14:43.8195817Z ##[group]Code Scanning Results
2024-06-07T19:14:43.8196780Z Total Code Scanning Alerts :: 1
2024-06-07T19:14:43.8221016Z ##[error]CodeQL - 2023-10-30 20:34:07 - Inefficient regular expression
2024-06-07T19:14:43.8222133Z INFO:root:Code Scanning violations :: 1
2024-06-07T19:14:54.3289319Z INFO:root:Total Dependabot Alerts :: 26
2024-06-07T19:14:54.3357725Z INFO:root:Dependabot violations :: 0
2024-06-07T19:15:02.5778440Z INFO:root:Total Dependency Graph :: 829
2024-06-07T19:15:02.5838228Z INFO:root:Dependency Graph violations :: 0
2024-06-07T19:15:11.0285467Z INFO:root:Loaded extra licensing information :: 9459
2024-06-07T19:15:11.0287671Z INFO:root:Total Dependencies in Graph :: 829
2024-06-07T19:15:11.0300390Z INFO:root:Dependency Graph violations :: 0
2024-06-07T19:15:11.2337908Z INFO:root:Total unacceptable alerts :: 2
2024-06-07T19:15:11.2339061Z Code Scanning violations :: 1
2024-06-07T19:15:11.2340268Z ERROR:root:Unacceptable Threshold of Risk has been hit!
2024-06-07T19:15:11.2342037Z ##[endgroup]
2024-06-07T19:15:11.2343420Z ##[group]Dependabot Results
2024-06-07T19:15:11.2390111Z Total Dependabot Alerts :: 26
2024-06-07T19:15:11.2391286Z Dependabot violations :: 0
2024-06-07T19:15:11.2392859Z ##[endgroup]
2024-06-07T19:15:11.2394306Z ##[group]Dependency Graph
2024-06-07T19:15:11.2395312Z Total Dependency Graph :: 829
2024-06-07T19:15:11.2396204Z Dependency Graph violations :: 0
2024-06-07T19:15:11.2397671Z ##[endgroup]
2024-06-07T19:15:11.2399363Z ##[group]Dependency Graph Results - Licensing
2024-06-07T19:15:11.2400562Z Loaded extra licensing information :: 9459
2024-06-07T19:15:11.2401603Z Total Dependencies in Graph :: 829
2024-06-07T19:15:11.2402675Z Dependency Graph violations :: 0
2024-06-07T19:15:11.2404177Z ##[endgroup]
2024-06-07T19:15:11.2405594Z ##[group]Secret Scanning Results
2024-06-07T19:15:11.2407038Z ##[endgroup]
2024-06-07T19:15:11.2408377Z ##[group]Summary
2024-06-07T19:15:11.2409269Z Total unacceptable alerts :: 2
2024-06-07T19:15:11.2412644Z ##[error]Unacceptable Threshold of Risk has been hit!
2024-06-07T19:15:11.2541570Z ##[error]Process completed with exit code 1.
2024-06-07T19:15:11.2634411Z Post job cleanup.
2024-06-07T19:15:11.3530451Z There is no valid token stored in the action state, nothing to revoke.
2024-06-07T19:15:11.3752208Z Cleaning up orphan processes

Any thoughts on how I can troubleshoot?

@GeekMasher pinging you now so I don't forget post holiday. Very much hoping to look at this still

Hey @Brutalbeard sorry for the delay, let me check over this today and get back to you shortly

Morning! Get a chance to find anything?

Checking in again! Hoping to hear something before weekend

Good morning! Checking in again this week. Is there anything I can do to help with troubleshooting>

Hey @Brutalbeard I have been working with this composite for a while in a large FinSer company and have seen issues similar to this. I’m recently retired so I will be happy to have a look at this to see if I can reproduce. IME the main reason for this is permissions. When you access open secrets alerts in particular you need a LOT of perms (more than you showed above). I used a GitHub app and, because of the perms, restricted access to the cert and app id to a very limited scope secrets manager policy (in Hashicorp Vault) bound to the reusable workflow in which this action was used (via the job_workflow_ref).
I assume you have tried disabling secrets scanning (--disable-secret-scanning) and each of the other capabilities per the docs, e.g.
parser.add_argument("--disable-caching", action="store_false")
parser.add_argument("--disable-code-scanning", action="store_true")
parser.add_argument("--disable-dependabot", action="store_true")
parser.add_argument("--disable-dependency-licensing", action="store_true")
parser.add_argument("--disable-dependencies", action="store_true")
parser.add_argument("--disable-secret-scanning", action="store_true")
parser.add_argument("--is-github-app-token", action="store_true", default=False)
parser.add_argument("--is-policy-github-app-token", action="store_true", default=False)
parser.add_argument("--pr-comment", action="store_true", default=False)

Morning @goffinf, if you have them open still, could you toss me a link to the docs you're referencing? Happy to try whatever

Hey John, it’s evening here in the UK (6p.m). The code snippet above was from the implementation. I note Mathew has recently improved the docs but when I started using this (about a year ago) they were somewhat incomplete so looking at the source was informative. The link in this case is :
https://github.com/advanced-security/policy-as-code/blob/main/ghascompliance/__main__.py
HtHs
Fraser

I'm Denver US, so I'll have the day to go through and check out what you've noted here. Will have some comments on here to see tomorrow

Hey all! Appreciate your collaboration and patience here.  Discussing with @GeekMasher - he was able to reproduce the issue on a test repo and has uncovered a couple of bugs that need resolved.  Let's look toward next week to get something patched here.  While we do maintain this project as OSS, this issue has hit during a perfect storm of travel, sickness, and OOO for the summertime for our team - apologies for the delays in comms.

Hey @Brutalbeard, sorry for the delay. Turns out there was a few different issues here but they should all be fixed in v2.8.0. Please can you confirm if this issue is fixed

Howdy! I think we're chatting about it a bit in slack, but can confirm we're getting an issue with permissions at the moment. Just dropping that note here for anyone who may be keeping an eye on this issue


Describe Kamelet properties

Changes

Print Kamelet provider information
Print Kamelet properties
Use more detailed output based on --verbose option

Sample output:
Name:         k1
Namespace:    default
Labels:       camel.apache.org/kamelet.provider=Community, camel.apache.org/kamelet.type=source
Age:          0s
Description:  Kamelet k1 - Sample Kamelet source
Provider:     Community
Phase:        Ready

Properties:  k1_prop, k1_optional

Conditions:
  OK TYPE     AGE REASON
  ++ Ready

Sample output --verbose:
Name:         k1
Namespace:    default
Labels:       camel.apache.org/kamelet.provider=Community
              camel.apache.org/kamelet.type=source
Age:          0s
Description:  Kamelet k1 - Sample Kamelet source
Provider:     Community
Phase:        Ready

Properties:
  Name        Required Type     Description
  k1_prop     true     string   The k1 required property
  k1_optional false    boolean  The k1 optional property

Conditions:
  OK TYPE     AGE REASON
  ++ Ready

/kind enhancement

Fixes #19

Release Note

Docs

@christophd sorry for the delay, this week was kind of crazy. I will jump on a review early next week.

/remove-lifecycle stale

@dsimansk @vyasgun @rhuss would you mind having a look?

@rhuss have pushed the review changes. workflow fails with weird error. could you please have a look and see what's wrong here?

@rhuss have pushed the review changes. workflow fails with weird error. could you please have a look and see what's wrong here?

That's really strange error, I wonder it it isn't caused by the degraded performance all over the GH services. https://www.githubstatus.com/

And sorry for being late to the review. The changes look good to me. :)

Thanks!
/approve
/lgtm


Slow on Llama_cpp_python

This seems to work nicely for my use case, but using the llama_cpp_python backend with a long prompt and a dozen completions takes about 1 minute. Any tips on improving speed?

Hi @dnhkng,
Unfortunately cappr.llama_cpp can be slow. This is partly b/c there currently isn't a way to batch over completions like we can in cappr.huggingface. The CAPPr algorithm also doesn't scale well, as discussed here.
2 different routes to improve performance:

Shorten the prompt. Perhaps if you post the prompt and completions we can figure out ways to make it shorter.

Don't use CAPPr. There are other LLM structuring tools which provide a "just pick" functionality. I'm most familiar with the algorithm for guidance.select, and it's quite efficient.

Apologies for the slowness, and thanks for raising the issue

I do want to use CAPPr.
I need the probabilities (yes I know that we can't use these as confidence values), but I think I have found something useful.
I need to run a few thousand inference over a long prompt, with a large number of categories to test this though.
Any other tips would be welcome.

Are you using a GPU? If not (and assuming it's ok to use a cloud GPU for security/compliance), can you point to the GGUF model you're using? Maybe the model and task will fit on a free or cheap GPU

Can you use a smaller version of the model? Also, if there's a PyTorch/AutoGPTQ version of the model, cappr.huggingface may be faster. Lmk which model you're using

Can you post the prompt and completions (or something similar-enough to work with)? In case you're doing in-context learning / few-shot prompting, consider reducing or eliminating the examples / do a zero-shot prompt. Sometimes, the lift from in-context learning is marginal

Another tip: if all of the prompts start with the same long substring, e.g., system instructions and few-shot examples, use cappr.llama_cpp.cache

Thanks for the tips!

yes, using a beefy GPU
A big model is required, unfortunately.
the prompt is necessarily long, no way around that.

I'm currently using Outlines for category selection, but I want to try a new approach that requires probabilities. It initially, I planned on doing the naive 'tokenise the categories', and collect the probabilities for each token, and do the whole thing in a batch the size of the categories.
But I assume that sometimes the same category wording can be achieved via multiple token combinations... So I found your library to use instead.

Makes sense. How long are the completions? Despite the long prompt, it's still surprising to me that 12 completions takes a minute. Maybe the prompt can be refactored a bit to work with cappr.llama_cpp.cache_model.  And is there an AutoGPTQ version of the big model?
Also, I found this point from your previous comment interesting:

I need the probabilities (yes I know that we can't use these as confidence values), but I think I have found something useful.

Can you elaborate on this / point to a reference? I've barely studied this

I just mean the fact that LLMs are trained on cross entropy loss on next tokens. This leads to overconfidence, as the loss does not penalise miscalibration.  But maybe that's not a huge issue?

This leads to overconfidence, as the loss does not penalise miscalibration.

I believe that research is about neural networks leading to overconfidence. Cross entropy (CE) / negative log-likelihood (NLL) is also used to fit logistic regression, for example. A short mathematical argument will make it clear that CE/NLL is great for calibration: the loss is $-\log \hat{y}$, where $\hat{y}$ is the predicted probability of the given class. As $\hat{y}$ gets closer to 0 / further from 1, the loss goes up. In fact, it's unbounded. So CE/NLL penalizes miscalibrated models much more than other losses like mean squared error.
That aside, I take your point. LLMs are NNs, and they shouldn't be expected to be calibrated. Though I think it's worth researching how calibrated CAPPr's probabilities are. Hopefully they turn out to be helpful for your task

Exactly.  The tests I'm planning are to see how it works in practice.

As far as the algorithm works, does it sum the probabilities of all paths?

No. It tokenizes end_of_prompt + completion and calculates the log-probability of each token given prompt. See my post about it here and this page of the documentation


Error: Could not find or load main class Files/Java/openjfx-13.0.2_windows-x64_bin-sdk\javafx-sdk-13.02\lib

Error: Could not find or load main class Files\Java\openjfx-13.0.2_windows-x64_bin-sdk\javafx-sdk-13.0.2\lib
Caused by: java.lang.ClassNotFoundException: Files\Java\openjfx-13.0.2_windows-x64_bin-sdk\javafx-sdk-13.0.2\lib
Hi. See above for the error that I get when I try to run the program from the tutorial. I am having the same issue whether I use the community or the ultimate version of Intellij IDEA. I have followed the tutorial to a T as well as followed along with a YouTube video by Kody Simpson that basically followed the tutorial as well. Everything for me goes exactly as the video until I get to the part where I select:
Run - Edit Configuration - Copy/Paste  --module-path "\path\to\javafx-sdk-13\lib" --add-modules javafx.controls,javafx.fxml
.... but with the path to my JavaFX library between the double quotes. When I try to run the program after the above step is when I get the error.

Your issue is with the "path" of the JavaFX SDK. Instead of C:\Program Files\Java..., the IDE is reading Files\Java\....


System.Configuration.ConfigurationManager not avaliable in .Net Core 3.0 and above

NLog version: 4.6.8
I've been trying to port a desktop app to .Net Core 3.1, but any reference to LogManager.Configuration produces a message that the ConfigurationManager assembly cannot be loaded. Is there a work-around for this?
Note, this is currently a multi-targetted library project, the .Net 4.7.2 target works just fine.

I never have seen this error.
What platform build do you use? Please share the properties of the NLog.dll  - go to the NLog.dll in your bin folder in explorer. Go to properties and please share a screenshot of the details tab.

Properties as requested.

Curiously, the installed version reports 4.6.8

Sounds like you have multiple projects:

trying to port a desktop app to .Net Core 3.1
This is currently a multi-targeted library project,

Make sure to change all libraries to use Net Core 3.1 and not just some of them. And ensure that their dependencies are also supporting Net Core 3.1
Make sure that none of the libraries in this chain suddenly have a direct reference (or hintpath) to the NLog.dll, but all of them are using nuget-packages (Change projects to newstyle using <packagereferences>)
NetCore31 will try to be optimistic, so if it meets a library that only supports NetFramework, then it will load it anyway. If that library references NLog.dll for Net45 then you will get an error.
Anyway have no issue with using NLog with multitarget applications, so I think the problem is in your application.

I assume your question has been answered, if not, please let us know!


Local register index and state re-execution

Problem definition
Right now Flow execution node is responsible for executing all the transactions including EVM transactions. More specifically EVM became part of FVM where transactions are executed. While the EVM Gateway indexes transactions and blocks emitted via events.
The problem with this approach is while the EVM Gateway has transactions and blocks indexed it doesn't keep an EVM state, which is required for some of the JSON RPC APIs. How we currently implemented ability to also inspect the state is that we exposed some of the APIs through the EVM Core contract, methods like getBalance or getCode, which we were then able to call using a Cadence script. There are issues with the current approach (albeit being the simplest):

all the requests require the execution of Cadence scripts which brings resource penalty as well as time penalty
new future APIs will require for EVM Core contract to be updated, which is not ideal since it's deployed on the network and potentially introduces breaking changes which we want to avoid
but most importantly, it prevents us from inspecting historic state defined by the EVM block height, how we currently handled this issue was, we executed Cadence scripts calling EVM Core contract API to inspect the state at previous Cadence heights, but since the Cadence height to EVM height is not always 1:1 mapping we are facing issues where that isn't the case

The following APIs require inspection of the state and allow for providing historic block heights:

eth_getBalance loads the account balance
eth_getStorageAt value from a storage position at a given address
eth_getTransactionCount the number of transactions sent from an address
eth_getCode code at a given address

Besides the getStorageAt which is not supported, we implemented the rest relying on the EVM Core contract API calls, which like explained fails with certain historic EVM heights as well as introduce other issues explained.
Proposal
The EVM Gateway was built to implement JSON RPC API specification, which is usually implemented by an "archive node" on the EVM networks. Such a node has a local state of the blockchain available to query and inspect.
We initially avoided doing this because it requires quite a bit of work to achieve but we have come at a point where this became unavoidable, specifically because of the EVM height problem, as well as the requirement to support getStorageAt API.
Because this is a specific problem to the EVM we would want to isolate the solution to the EVM Gateway itself. We could take an alternative approach of extending Flow archive node to index registers at EVM height resolution but that would leak complexity from EVM into Flow and is not a good idea.
The proposal is to extend EVM Gateway so it can operate in the archive mode, which besides indexing transactions and blocks as it already does, it also builds and indexes the state. It does so by re-executing all the transactions it indexes locally using an emulator.
Requirements
In order to achieve rebuilding the state on EVM Gateway we need a complete history of changes applied to the state (transactions), which we already have, but there is one caveat. Flow EVM exposes Cadence arch precompiles, which have the ability to read into the Cadence state, and that would not be available on EVM Gateway by simply executing EVM transactions. So we need to somehow have access to the Cadence state on EVM Gateway. The easiest solution for that is to include results (outputs) from the Cadence arch calls in the EVM transaction receipts, this way we can locally build and mock access to the Cadence state for already known calls, then when we re-execute the transaction we can provide the results from Cadence state it read while executing on the execution node.
Implementation
Emulator
We will have to create an emulator that will be able to execute EVM. There are two options here, either use existing Flow emulator, which in turn already integrates EVM, but this has some overhead of also containing complete FVM execution which is not really needed, the alternative solution would be to implement a simpler emulator only hosting EVM.
Event ingestion
We must improve event ingestion to build and index of all the Cadence values read through the Cadence arch, which would then be read with mocked precompiles provided to the above emulator EVM.
Ledger
EVM emulator would use the Flow EVM wrapper, which uses the stateDB wrapper and the stateDB wrapper relies on a ledger that stores key-values. We should investigate whether we write our own simple Pebble-backed ledger implementation.
Traces
Trace production would be done on the EVM Gateway since the execution will be done locally and can be used to produce the traces.
### Tasks
- [ ] https://github.com/onflow/flow-evm-gateway/issues/449
- [ ] https://github.com/onflow/flow-evm-gateway/issues/450
- [ ] https://github.com/onflow/flow-evm-gateway/issues/451
- [ ] https://github.com/onflow/flow-evm-gateway/issues/452
- [ ] https://github.com/onflow/flow-evm-gateway/issues/458
- [ ] https://github.com/onflow/flow-evm-gateway/issues/572
- [ ] https://github.com/onflow/flow-evm-gateway/issues/573
- [ ] https://github.com/onflow/flow-evm-gateway/issues/587

We have started implementation of improved solution in dry-run (https://github.com/onflow/flow-go/issues/6539)The , so this issue is no longer needed.


websockets.server:connection rejected

I'm running on Manjaro Linux. Have the cpu Docker for the server running, and the chrome plugin. Transcription from the extension doesn't work with the Collabora server or my local docker server. Only message I get is:
INFO:websockets.server:connection rejected (426 Upgrade Required)

@luandro Can you try upgrading the websockets package?


Query builder UI + field validation

Summary of changes 🔍
Initial PR for the UI of the query builder in Advanced Search modal. This new component will allow users to build queries based on properties, operators and values. This can be achieved by adding/removing query rows and updating the inputs in the respective fields. The scope of this PR includes property combo-box, operators changing based on property type and basic value field validation and row to string query creation.
This does not accomplish the following tasks for advanced search:

Value auto-complete
Query search and results integration
SQL display of query

Testing 🧪

Open Advanced search base story
Click on Add/Remove query row buttons

Validate limit of 10 rows
Validate first row not removable

Select properties in property dropdown to see how operators change

Validate string/numeric/boolean types to have different operators

Add values in the respective input field to see how validation works:

Validate empty string
Validate no string values in numeric types

Checklist ✔

[ ] Linked associated issue (if present)
[ ] Added relevant labels
[ ] Requested developer reviews
[ ] Request UI review from design / PM
[ ] Verify all code checks are passing

left couple of small comments, nice job! :)


Button: wired spacing when line breaks

[x] The issue is present in the latest release.
[x] I have searched the issues of this repository and believe that this is not a duplicate.

Current Behavior 😯
There is additional space on the button left and right (see screenshot)

Expected Behavior 🤔
The button should shrink as without line breaks

Steps to Reproduce 🕹

Steps:

Please note the maxWidth on the surrounding div.
https://codesandbox.io/s/material-demo-3do1p?file=/demo.js

<div style={{ maxWidth: 170 }}>
    <Button variant="contained" color="primary">
        Send to somewhere
    </Button>
    <Button variant="contained" color="primary">
        Send to some
    </Button>
</div>

Context 🔦

THis issue might be related: https://github.com/mui-org/material-ui/issues/17494
Your Environment 🌎

Tech
Version

Material-UI
v4.9.9

React
16.13.1

Browser
Linux Chrome Version 80.0.3987.162 (Official Build) (64-bit)

TypeScript

etc.

Tip, check the full-width option

The issue is not about making the smaller one full-width but the additional space WITHIN the first button is unexpected and too much. The first button should shrink to the same width as the 2nd example.Am 08.04.2020 01:29 schrieb Olivier Tassinari<EMAIL_ADDRESS>Tip, check the full-width option
—You are receiving this because you authored the thread.Reply to this email directly, view it on GitHub, or unsubscribe.

@oliviertassinari can you please check the issue description more closely, I think it is a bug and it is not about the full-width but the first button is too wide. I Think my first screenshot was not marked very wisely.

The button stops shrinking.


syncthing: hardcoded gui settings in unit file

Issue description
I'm trying to set access to syncthing wui to listen to all ips and not just localhost. So I edite the syncthing config.xml. However, no matter what I do, nothing worked. It would always use <IP_ADDRESS>:8384.
The problem is that this seems hardcoded in the provided systemd unit file.
ExecStart=/nix/store/zyz36q4vv9jhdm2l3qxcg9q3c9rz4srr-syncthing-0.14.51/bin/syncthing \
  -no-browser \
  -gui-address=<IP_ADDRESS>:8384 \
  -home=/home/hyper/Syncthing/.config/syncthing

So this is new, because before I upgraded my system it used to work just fine.
Technical details
Please run nix-shell -p nix-info --run "nix-info -m" and paste the
results.

system: "x86_64-linux"
host os: Linux 4.14.78, NixOS, 19.03pre157893.1fe3328593e (Koi)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.1.3
channels(hyper): ""
channels(root): "nixos-19.03pre157893.1fe3328593e"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

It's not hardcoded though, that's just how systemd units work in NixOS.
You shouldn't be editing the XML. You need to be setting the module's guiAddress: https://github.com/NixOS/nixpkgs/blob/master/nixos/modules/services/networking/syncthing.nix#L158

Well, it breaks how it worked so far. Also wtf is this with the change of config file? And each syncthing has an xml file and that should be respected.

If I were to guess, I guess that the command line flags take precedence over the config file, as is common for CLI tools.
It looks like this was a recent change, as part of https://github.com/NixOS/nixpkgs/pull/48119.

It is set to the default syncthing uses anyway : https://www.mankier.com/1/syncthing#-home

https://docs.syncthing.net/intro/getting-started.html#configuring the gui-address is set to the default syncthing.

One problem that remains is the configuration for the listen address for data transfers. The choice of the port there is rather important (because it needs to interact with the firewall) yet this setting cannot be changed through the command line.
As far as I can tell, the only viable solution to make this stuff configurable via Nix is to manipulate the appropriate settings into the config file every time syncthing starts, which is easy enough considering it's a simple XML file.


How to use Layoutlm in receipt understanding case?

Hi there,
Thanks for the repo and help! I was wondering how to use layoulm in receipt understanding? I don't find python script about it.
Thanks much in advance!

@ranpox @wolfshow

Hi @hee0624 ,
Currently, the preprocessing script only supports the FUNSD dataset. But you can convert your receipt dataset into BIO format in a similar way.
FYI: #81
Thanks.


Support for dual logos in presentation theme

It is common within academia to have some kind of dual affiliation requiring a logo for USYD and some other group whether that be something like the HRI, ACFR, BMRI.
This would add a new command like \affiliationlogo which adds the image to the titlepage.

@chinitaberrio I would gladly accept a PR for this if you would like to contribute.

fixed in #13


Unity Editor Colors messy after run

System information

OS Platform and Distribution (e.g., Linux Ubuntu 20.04): ArchLinux
Target Platform: Desktop
Mobile Device (if the target is Android or iOS):
MediaPipeUnityPlugin version or commit id: 333279e132c9601b1809260732804eaede989d2a
Bazel version: 4.2.2
GCC/G++ version: 11.1.0
Android NDK version (if the target platform is Android):
Xcode version (if the target platform is iOS):

Describe the current behavior
After run in Unity Editor the colors of the interfaz get messy. For be able to work need to close and start again. Like that problem related to have another scene in hierarchy like Pose Tracking
Describe the expected behavior
Unity Editor keep its colors after run the start scene
Steps to reproduce the issue
Open project with Unity Editor and play start scene
Full logs
Can not read then because of the problem
Additional context
Happens in several unity versions like 2021.2.5f1, 2020.3.4f1

Can you post a screenshot?
It looks to me like a problem with your Linux or UnityEditor in your environment, doesn't it happen in other projects?

Never notice in other projects

Can not read then because of the problem

OK, please share Editor.log.
Two things:

Please use version 2020.3.*, since it's not tested using 2021.2.x.
It's known that this plugin doesn't work with OpenGL, so please use Vulkan as the graphic API.

Never notice in other projects

With Vulcan worked without problems. Thanks so much for all your work


add userSharingScope field when exporting to Synapse table

test done:

all unit tests in package;
manual test: upload test data through Bridge Server and send SQS msg to exporter; then verify if new column was added;

Looks good. We just need to resolve conflicts before we can merge.


ENH: Handle minimum / maximum zoom limit for known providers

using automatic zoom in bounds2img for a small area results in high zoom level values that exceeds the available zoom levels of the provider, and rises HTTPError:
import contextily as ctx
img, ext = ctx.bounds2img(1231934.7608171296, 5785711.490238651, 1232411.1480162584, 5785880.3953617485)

It would be great to clip the zoom level to a max_zoom property for the known providers (18 for stamen, 19 for OSM).

I think this is related to https://github.com/darribas/contextily/issues/10. We want to have more complete list of providers, but also objects that contain more information than only the url (so eg also the attribution, max zoom level etc). Once we have that, we should indeed use that here to prevent this from happening.
See also https://github.com/darribas/contextily/pull/66 for an initial to start to get this information from leaflet-providers.js.

With #66 in, this should now be an straightforward enhancement, as the provider dicts have an optional min_zoom and max_zoom keys which can be checked.

Just to mention that I could run the tests with pytest.
I will look around the issues to see where I could help.
best


Update quick start docs to reflect that instance is not optional

The quick start guide provides a minimal example of instantiating a VmaAllocator. Unfortunately the example is incorrect, as the instance field (type VkInstance) in the VmaAllocatorCreateInfo struct is not optional anymore.
Without providing a value for this field the user hits the assert on line 15503:
VmaAllocator_T::VmaAllocator_T(const VmaAllocatorCreateInfo*): Assertion pCreateInfo->physicalDevice && pCreateInfo->device && pCreateInfo->instance' failed.
This small PR updates the quick start docs to reflect this.

Thank you for this contribution!


Things I miss from v0.10.7

Description
Hello
Thanks a lot for the big update on v0.11 but I had to role back to v0.10.7, cause of this things that I hope you would add or bring back later to homarr.
These are some of those and other things that I would like to see:

being able to change between small - medium - large screen size manually so I would have a lot of small icons on my big screen.
being able to make tiles even smaller in edit mode.
being able to adjust the size of the sidebars.
being able to collapse a category so in that way you can have a lot of categories with a lot of tiles in each exactly like v0.10.7.
add a shortcut for entering and exiting the edit mode.

Priority
Medium (Would be very useful)

Thank you for your issue.

being able to collapse a category so in that way you can have a lot of categories with a lot of tiles in each exactly like v0.10.7.

This has just been re-introduced in 0.11.3. Please check it out.

add a shortcut for entering and exiting the edit mode.

Do you mean a keyboard shortcut with that?

add a shortcut for entering and exiting the edit mode.

Do you mean a keyboard shortcut with that?

Yes I meant a keyboard shortcut.

add a shortcut for entering and exiting the edit mode.

Done in f28f0b9

being able to collapse a category so in that way you can have a lot of categories with a lot of tiles in each exactly like v0.10.7.

Has been implemented in 0.11.3

being able to adjust the size of the sidebars.

Can you open a separate issue for that?

being able to change between small - medium - large screen size manually so I would have a lot of small icons on my big screen.

being able to make tiles even smaller in edit mode.

Already requested in #613
After creating the issue for the size of the sidebar, can we close this?

After creating the issue for the size of the sidebar, can we close this?

Sure, Thanks a lot.


Feature/fix issue 7

The changes in this PR add some sanity checks before modifying the XML3D scene when a node comes in via REST. Most noticably, changes triggered by STOMP shouldn't lead to erroneous additions to the scene any more.
Especially, it should fix #7.

Ready to merge.


Invalid character in vcard results in undhandled exception

A vcard on my DAViCal server contains a character that is apparently not legal for vdirsyncer: It causes an InvalidXMLResponse error and vdirsyncer closes itself. It would be nicer if an error could be generated, but all other contacts would be synced. Or alternatively, if the user is given the option to replace this character, abort, or ignore it. Evolution ignores such characters and just shows an equals sign.
The character that causes this is shown as ^P in vim and is part of the NOTE section. Pressing ga to get the ASCII representation gives <^P>  16,  Hex 10,  Octal 020. The encoding of the XML document is UTF-8.
I get the following strack trace in this situation:
Unhandled exception occured for my_contacts.
Traceback (most recent call last):
  File "/usr/lib/python2.7/site-packages/vdirsyncer/cli/tasks.py", line 70, in sync_collection
    force_delete=force_delete
  File "/usr/lib/python2.7/site-packages/vdirsyncer/sync.py", line 159, in sync
    b_info.prepare_idents(storage_a.read_only)
  File "/usr/lib/python2.7/site-packages/vdirsyncer/sync.py", line 114, in prepare_idents
    hrefs_to_download else ()):
  File "/usr/lib/python2.7/site-packages/vdirsyncer/storage/dav.py", line 384, in get_multi
    root = _parse_xml(response.content)  # etree only can handle bytes
  File "/usr/lib/python2.7/site-packages/vdirsyncer/storage/dav.py", line 50, in _parse_xml
    .format(e))
InvalidXMLResponse: Invalid XML encountered: PCDATA invalid Char value 16, line 5512, column 30
Double-check the URLs in your config.

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/15343766-invalid-character-in-vcard-results-in-undhandled-exception?utm_campaign=plugin&utm_content=tracker%2F574345&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F574345&utm_medium=issues&utm_source=github).

Could you give me the Content-Type header of the response? It also might be a different encoding than expected.

I've got a PR prepared for this (it skips the broken character) but I'd like to still know what the encoding was. This might be the wrong fix for your issue.

Hi, the Content-Type header is text/xml charset="utf-8". And  the encoding of the XML data sent is UTF-8.

Ok great, so #208 should be appropriate.
Could you try:
pip install --user --force-reinstall -U git+https://github.com/untitaker/vdirsyncer@tolerant-xml-parser

?

Thanks, I installed vdirsyncer in a virtualenv and started it from there, this should work the same. After I managed to insert this character again (by copying it directly into the VCF file, vdirsyncer sent the odd character without problems), I was able to try again. This time the invalid character is handled gracefully:
warning: Partially invalid XML response: <string>:20:32:FATAL:PARSER:ERR_INVALID_CHAR: PCDATA invalid Char value 16

Very nice, thanks for looking into this so quickly!  It would be even more helpful, if the item ID would be part if the warning so that one can manually investigate the situation.
And as it seems to me you just skip this character and thereby changing the item, correct? At least I can't see the invalid character in the produced VCF file anymore. Is this change uploaded (or copied to the other storage) as well?

Very nice, thanks for looking into this so quickly!  It would be even more helpful, if the item ID would be part if the warning so that one can manually investigate the situation.

I don't think that's possible.

And as it seems to me you just skip this character and thereby changing the item, correct?

Yup.

At least I can't see the invalid character in the produced VCF file anymore. Is this change uploaded (or copied to the other storage) as well?

That depends on the local storage.

On singlefile-storage, yes, a second sync will upload the new item
immediately.

On filesystem-storage, the item with the skipped chars will be uploaded once
you make explicit changes to it.


Error when shutting down server

[2019-09-05 17:48:59,507] [] ERROR {org.apache.catalina.loader.WebappClassLoaderBase} - The web application [shindig] created a ThreadLocal with key of type [org.apache.shindig.common.xml.XmlUtil$2] (value [org.apache.shindig.common.xml.XmlUtil$2@7dcd2859]) and a value of type [org.apache.xerces.jaxp.DocumentBuilderImpl] (value [org.apache.xerces.jaxp.DocumentBuilderImpl@7062131e]) but failed to remove it when the web application was stopped. Threads are going to be renewed over time to try and avoid a probable memory leak.

The above error when shutting down the IS server

Tested the alpha4 pack and the issue is not reproducible. Hence closing the issue.


Support to input wide characters

Currently, spanner-mycli doesn't support to input wide characters.
It is a reeflective/readline issue, so hard to fix.
https://github.com/reeflective/readline/issues/73

Fixed by #35


Added the social media handles

I have added the social media links/handles to the footer section of the website. Check if it is fine or do I need to add anything else.

can you add that color functionality on hovering @vivek-singh-13

Sure

Added the color functionality on hover.


JBDS-4520 Use credential manager API to store username/login

This PR is to address issues in https://github.com/redhat-developer-tooling/developer-platform-install/pull/890:

Remember me checkbox location
Unit tests errors
settings.json location

Codecov Report

Merging #893 into master will decrease coverage by 0.55%.
The diff coverage is 83.07%.

@@            Coverage Diff             @@
##           master     #893      +/-   ##
==========================================
- Coverage   97.71%   97.16%   -0.56%
==========================================
  Files          36       37       +1
  Lines        3241     3491     +250
  Branches      274      504     +230
==========================================
+ Hits         3167     3392     +225
- Misses         74       88      +14
- Partials        0       11      +11

Impacted Files
Coverage Δ

browser/services/platform.js
99.11% <100%> (+0.17%)
:arrow_up:

browser/services/credentialManager.js
65.62% <71.42%> (ø)

browser/pages/account/controller.js
88.88% <78.57%> (-1.64%)
:arrow_down:

browser/services/data.js
97.06% <87.5%> (-1.34%)
:arrow_down:

browser/main.js
98.41% <0%> (-1.59%)
:arrow_down:

browser/model/helpers/downloader.js
96.24% <0%> (-1.51%)
:arrow_down:

browser/pages/confirm/controller.js
94.92% <0%> (-1.47%)
:arrow_down:

browser/model/devstudio.js
96.8% <0%> (-0.97%)
:arrow_down:

browser/model/cdk.js
99.21% <0%> (-0.79%)
:arrow_down:

... and 27 more

Continue to review full report at Codecov.

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

Got tests for the new code? ಠ‿ಠ

I'll forward that question to @sudhirverma ;)


Most buffers not loading

The plugin seems to only load the buffer with the focus when the session was saved, no matter the number of existing buffers.  recession is latest, nvim is 0.9.0, NvChad is latest.  Saving seems to indicate success via screen output.  To the extent that buf_filter might affect this, I defined it as a function that always returns true, but no change.
Thanks.

Grrr . . .  So, this is working just fine in isolation.  Something about the interaction with NvChad is causing the problem.  I will close for now.  Thanks for the help.


Bring xgql code to this repo

Now that xgql is written in Go and agent was already in Go, all parts of Universal Crossplane are written in Go. As mentioned in design doc, I think it makes sense for us to move both xgql and agent to this repo and produce their images from here.
For versioning, @turkenh suggested using v1.2.0-up.1 where v1.2.0 is Crossplane version and up.1 is distro version, similar to GKE using 1.18-gke.156. All images (bootstrapper, agent and xgql) would use the same version tag.

@negz should we close this issue?

Closing as xgql was removed in https://github.com/upbound/universal-crossplane/pull/327.


Expose queue/topic creator

This PR ensures compatibility with JustSayingStack by providing queue/topic creation/loading by interface, instead of the raw SnsTopicByName et al.

Thanks so much for the reviews and comments @maurofranchi, @martincostello and @slang25. We had a discussion on Wednesday and came to the conclusion that this isn't the best way to support JustSayingStack moving forward.
Our options were to do this as a temporary workaround until we can deprecate JSS, or re-expose the internal types and mark them as obsolete for removal/internalisation in a future version that supports the scenarios that JSS enables. Given that the latter option is less risky, less code, and easier, we went with it.
I'll open another PR that re-exposes those types so we can move forward with V7.


Multiple instances for repeater fields

Hi, found this plugin very easy to setup and nicely ready for production. We've made a form for our client with a single attachment block with multiple attachments facilities.
But now client wants to bind Some text/select choice with each of the files individually so that they provide title for each of the file or they can group files etc. So I choose repeater fields with using jQuery Dynamic Form and Plupload for each of the row. The thing should be something like this:

I found a solution, I think, not yet tried.
But your plugin might not ready for such things:

It's generating UI widget by default and I cannot trigger a Core view for each of the fields
You are using id for plupload selector and id selector for iterating fields failed me to select files in newly generated plupload instances

So what I got is:

And plupload simply isn't working for multiple instances where it's triggered on an ID.

Maybe you can inject the request like this:

Route::post('/upload', function(\Illuminate\Http\Request $request)
{
    return Plupload::receive('file', function ($file) use ($request)
    {
        $file->move(storage_path() . '/test/', $file->getClientOriginalName());
        $info = $request->get('info');

        //do something with $info

        return 'ready';
    });
});


Update Hungarian translation for 1.93–94

I have updated the Hungarian localisation for 1.93.
I also have some feedback:
I would like to reiterate my question from the original PR: Is there a way to be notified when modifications are made to the strings? Since my last update, 113 strings were modified or added, none of which I was able to translate in time before the build was published. With all due respect, I would like to avoid making a habit of having to check for new strings each and every day, lest a new version be made public with an unfinished translation.
I wonder if moving the translation efforts to a service like Crowdin could be done? That way, the system itself would be able to send out notifications about newly-added strings. I believe they have a free tier for open-source projects.

I absolutely agree, this is an issue that needs to be addressed...

First: I'll get an issue started when I get some free time to discuss the best way to coordinate translations for yall.
Second: Thank you @smileyhead for an amazing PR.
Third: @smileyhead can you tag another hungarian speaker to give this translation a review? It doesn't have to be super thorough for one this big -- we just have a policy that another native speaker takes a look, just to be safe!

Sure thing, and thanks for the work on making the localisation process better.
I will tag @SonoSooS to proofread, but let me just ask: Does every update need to be reviewed by someone else? I am the same person who translated the rest of the app as well, which has been checked and approved, and it's not like the quality of my translations is going to change (or at the very least, it will not worsen).
The localisation updating process already seems rather slow as it is. Based on the current timing, this PR would not have made it into the final build even if I translated every new string as soon as possible.

I would proofread the changes, but judging by the changed line numbers, and the messages in this comment chain, the lines in the translation file got scramled around in order, which means that I'd have to do redundant checking of translations that were not actually changed. I waited 5 minutes at 100% CPU use to try to load the diff, but I have a feeling, that even if it loaded, I'd have to sift through unchanged strings, just because the line order got scrambled around in the file.
It took a lot of time to do the initial checking, checking translations in context, interacting with every possible situation to see if everything matches the context, etc., I don't think it's very productive to have to do that every time new strings are added, especially if most changes don't affect unchanged translations, to see if the context of any unchanged translations could be affected or not. So yeah, we definitely need a better method to diff translations, so they could be edited (and checked) easier.
Don't get me wrong, even if only one string changes in a group of strings, I'd still have to check it for contextual consistency, but it's still much less work than having to redundantly check every little option again where nothing has changed.
I'm not whinging, I'm more than happy to proof-read the translations, but the lost hours do add up.

can you tag another hungarian speaker to give this translation a review? It doesn't have to be super thorough for one this big

I don't think we should let verifiers compromise the translation. If it's mandatory for verifiers to proofread the translation, then I'd expect them to check it with the same vigor the translator used to make the translation.

we just have a policy that another native speaker takes a look, just to be safe!

In my opinion, there needs to be a trusted/verified translator program, or a trusted hiearchy system of translation writers and verifiers, or something else akin to these.
With the trusted/verified translator program, trusted/verified translators would have their translations merged as soon as they are done, so users will get the new features seamlessly translated by the time they are pushed to prod.
As for the hierarchy system, there could be a "language manager" (project manager for the given language) possibly doing translation work, and also verifying, and there could be higher level verifiers who could possibly overwrite the decisions of lower-level translators and verifiers (as long as it's not too contended).
As the project grows, it will be just more and more difficult and tedious to get the "supply chain" of the translations rolling smooth, so it's probably better to get good systems in place as soon as we can.

I think there’s no need to close this PR, as it includes additional discussions on improving the translation environment. Opening a new PR might make it harder to track these discussions.
It would be simpler to merge the latest main branch into this one and continue building on it. Although it might make the original focus of this PR (Hungarian translation updates) a bit more complex.

I have reopened the PR already. I only temporarily closed it because GitHub wouldn't let me update my branch without discarding the previous commits first.

It’s possible that upstream updates to Hungarian translations (executing intl:extract for all languages in preparation for a release) caused conflicts with your existing translation branch.
The GitHub web interface’s suggested approach of discarding changes isn’t ideal—it would be better if it guided users to resolve merge conflicts first, similar to how GitHub Desktop handles it.
Discarding the previous translation work might slow down progress, especially since the earlier version contained over a hundred translated strings...
You might consider rolling back the merge to recover the original translation progress, then resolving the merge conflicts and syncing with the latest main branch. This approach should help reduce the current translation workload.

The GitHub web interface’s suggested approach of discarding changes isn’t ideal—it would be better if it guided users to resolve merge conflicts first, similar to how GitHub Desktop handles it.

This is a good point; before I discovered how to resolve conflicts from a PR I was confused by this and followed what GitHub was telling me to do when I tried to sync the branch and discard the commits, which isn't necessary. GitHub could definitely improve this.

The GitHub web interface’s suggested approach of discarding changes isn’t ideal—it would be better if it guided users to resolve merge conflicts first, similar to how GitHub Desktop handles it.

This is a good point; before I discovered how to resolve conflicts from a PR I was confused by this and followed what GitHub was telling me to do when I tried to sync the branch and discard the commits, which isn't necessary. GitHub could definitely improve this.

Same here. Before I figured out how to properly handle merge conflicts, I saw that “discard changes” was the only option available. I assumed I had to discard them to sync with the latest changes, so I chose to discard…
This shows how important it is to have a translation platform. Many translators are great at translating, but handling GitHub errors can be difficult for them. It would be better if they could focus on what they’re good at part.

You might consider rolling back the merge to recover the original translation progress

No progress has been lost. I've made a copy of the Hungarian .po file from the original PR beforehand and applied the 1.94 changes to it. From GitHub's perspective, nothing should be different than if it just let me sync without losing changes to the .po file.

And you can choose to keep all my changes, which will reduce the number of missing translation strings to just 15.

So…will this get merged before the release of 1.94? If not, the localisation will be two updates behind.

So…will this get merged before the release of 1.94? If not, the localisation will be two updates behind.

I'm sorry, no. I merge translations right before cutting a release. I know there's some frustration about the coordination here. It's probably time to formalize this process and get better contact with our translators!

In my opinion, there needs to be a trusted/verified translator program, or a trusted hiearchy system of translation writers and verifiers, or something else akin to these.

I think we do need to get crowdin going so that we can formalize this. I'm sorry this won't be as fast as yall deserve. We're putting out a lot of fires! But I've got this high on my task list.
FWIW this is informally how it's done. I have a document where I track this, but I also do it by memory. Somebody like quiple has no-verification approval, after a long contribution history. @smileyhead since this is your second contribution I would still normally still want review, but I also don't want to slow you down more so I'm going to go ahead and merge.
I'm sorry about frustrations with this; I don't want yall to ever feel undervalued. Our somewhat informal translations process was adequate until things popped off this past week, which of course meant that lots of things needed attention all at once.