text:
Merges of PRs give errors in release-please: "commit could not be parsed"

TL;DR
Merges of PRs give error: "commit could not be parsed" . The commit messages are normal merge commits from GitHub that contain the text "feat: message"
Expected behavior
New release PR should be created.
Observed behavior
New release PR was not created.
Action YAML
# test-and-release.yml script version: 1.0.4
#
# Test that pull requests on core packages will install, compile and build on all target platforms.
# Then, execute the upm package release process using release-please.
#
# XXX
# XXX
# XXX
# XXX
# XXX
# XXX
# XXX
# XXX
# XXX
# XXX
# XXX
# XXX
# XXX
# XXX
#
# *** Clearing the cache ***
#
# To clear the cache, change the contents of the CACHE_VERSION secret.
#
# XXX
# XXX
# XXX
# XXX
# XXX
# XXX

name: release-please

on:
  push:
    branches:
      - main

env:
  UNITY_CORE_UPM_CI_REF: 'main'

jobs:
  # Perform a matrix build on all selected platforms.
  build:
    name: Build for ${{ matrix.targetPlatform }}
    runs-on: self-hosted
    strategy:
      fail-fast: false
      matrix:
        targetPlatform:
          - Android
          - iOS
          - StandaloneOSX
          - StandaloneWindows64
          - WebGL

    steps:
      # Get repository name without the organization prefix.
      - name: Get repository name
        run: |
          REPOSITORY_NAME=$(echo '${{ github.repository }}' | awk -F '/' '{print $2}')
          echo "REPOSITORY_NAME=$REPOSITORY_NAME"
          echo "REPOSITORY_NAME=$REPOSITORY_NAME" >> $GITHUB_ENV

      # Install this repository as an embedded Unity package.
      - name: Checkout repository to the Packages/${{ env.REPOSITORY_NAME }} folder.
        uses: actions/checkout@v3
        with:
          lfs: true
          path: Packages/${{ env.REPOSITORY_NAME }}

      # Read package.json and save it into env.PACKAGE_JSON.
      - name: Read package.json.
        run: |
          PACKAGE_JSON=$(cat Packages/${{ env.REPOSITORY_NAME }}/package.json)
          echo "PACKAGE_JSON=$PACKAGE_JSON"
          echo "PACKAGE_JSON<<EOF" >> $GITHUB_ENV
          echo "$PACKAGE_JSON" >> $GITHUB_ENV
          echo "EOF" >> $GITHUB_ENV

      # Read name field from package.json and save it into env.PACKAGE_NAME.
      - name: Get package name.
        run: |
          echo "PACKAGE_JSON=$PACKAGE_JSON"
          echo "PACKAGE_NAME=${{ fromJson(env.PACKAGE_JSON).name }}"
          echo "PACKAGE_NAME=${{ fromJson(env.PACKAGE_JSON).name }}" >> $GITHUB_ENV

      # The directory in Packages must be named after the package name, not the repository name.
      - name: Rename package directory from Packages/${{ env.REPOSITORY_NAME }} to Packages/${{ env.PACKAGE_NAME }}
        run: |
          mv Packages/${{ env.REPOSITORY_NAME }} Packages/${{ env.PACKAGE_NAME }}

      # Get build environment variables from .github/build.env in the package
      - name: Get repository environment
        run: |
          BUILD_ENV_FILE="Packages/${{ env.PACKAGE_NAME }}/.github/build.env"
          echo "BUILD_ENV_FILE=$BUILD_ENV_FILE"

          if test -f $BUILD_ENV_FILE; then
            echo "Package build environment file '$BUILD_ENV_FILE' exists"
            cat $BUILD_ENV_FILE
            cat $BUILD_ENV_FILE >> $GITHUB_ENV
          else
            echo "Package build environment file '$BUILD_ENV_FILE' does not exist"
          fi

      # Checkout test harness repository.
      # See https://github.com/actions/checkout#checkout-multiple-repos-private
      - name: Checkout test harness repository from Attensi/unity_core_upm_ci
        uses: actions/checkout@v3
        with:
          lfs: true
          repository: Attensi/unity_core_upm_ci
          ref: ${{ env.UNITY_CORE_UPM_CI_REF }}
          # `GH_PAT_TOKEN` is a secret that contains a PAT, so that we can check out the test harness.
          # We should use an organization secret for a PAT token created by a read-only user.
          # Currently we are using Christian Tellefsen's PAT.
          token: ${{ secrets.UNITY_BASE_GITHUB_TOKEN }}

      # HACK: Above checkout wipes the package, we check it out again

      # Install this repository as an embedded Unity package.
      - name: Checkout repository to the Packages/${{ env.REPOSITORY_NAME }} folder.
        uses: actions/checkout@v3
        with:
          lfs: true
          path: Packages/${{ env.REPOSITORY_NAME }}

      # The directory in Packages must be named after the package name, not the repository name.
      - name: Rename package directory from Packages/${{ env.REPOSITORY_NAME }} to Packages/${{ env.PACKAGE_NAME }}
        run: |
          mv Packages/${{ env.REPOSITORY_NAME }} Packages/${{ env.PACKAGE_NAME }}
          ls Packages

      # Create authentication file. Required to download packages from upm.attensi.com.
      # https://game.ci/docs/github/builder#upm-authentication-using-.upmconfig.toml
      - name: Create .upmconfig.toml UPM authentication file
        run: |
          mkdir -p ${{ runner.temp }}/_github_home
          cd ${{ runner.temp }}/_github_home
          echo "[npmAuth.\"https://upm.attensi.com\"]" >> .upmconfig.toml
          echo "alwaysAuth = true" >> .upmconfig.toml
          echo "token = \"${{ secrets.UNITY_BASE_UPM_TOKEN }}\"" >> .upmconfig.toml

      # Cache the Library folder.
      # Force clear the cache by changing the CACHE_VERSION secret in this repository.
      - name: Cache Library folder
        uses: actions/cache@v3
        with:
          path: Library
          key: Library-${{ matrix.targetPlatform }}-${{ secrets.CACHE_VERSION }}

      # Build the project using GameCI (https://game.ci/docs/github/builder)
      - name: Build Unity project
        uses: game-ci/unity-builder@v2
        env:
          UNITY_EMAIL: ${{ secrets.UNITY_BASE_EDITOR_EMAIL }}
          UNITY_PASSWORD: ${{ secrets.UNITY_BASE_EDITOR_PASSWORD }}
          UNITY_SERIAL: ${{ secrets.UNITY_BASE_EDITOR_SERIAL }}
        with:
          targetPlatform: ${{ matrix.targetPlatform }}
          versioning: None # Using the default Semantic versioning does not work with repository changes - and this build will not be distributed, so version does not matter.

        # TODO: Add and run automated tests.

  release-please:
    name: Release Please
    runs-on: self-hosted
    needs: build
    steps:
      - name: Execute the Release Please action.
        uses: google-github-actions/release-please-action@v3
        id: release
        with:
          token: ${{ secrets.UNITY_BASE_GITHUB_TOKEN }}
          release-type: node
          package-name: ${{ github.repository.name }}
          bump-minor-pre-major: true

      # Check out the repository.
      - name: Checkout repository.
        uses: actions/checkout@v3
        # these if statements ensure that a publication only occurs when
        # a new release is created:
        if: ${{ steps.release.outputs.release_created }}
        with:
          lfs: true

      # Install node.
      - name: Set up node.
        uses: actions/setup-node@v3
        with:
          node-version: 16
          # This is redundant if registry is specified in package.json. We keep it here to be on the safe side.
          registry-url: "https://upm.attensi.com"
        if: ${{ steps.release.outputs.release_created }}

      # Publish the package to our package registry.
      - name: Publish package to upm.attensi.com
        run: npm publish
        env:
          NODE_AUTH_TOKEN: ${{secrets.UNITY_BASE_UPM_TOKEN}}
        if: ${{ steps.release.outputs.release_created }}

Log output
2022-11-02T09:18:02.5627712Z Requested labels: self-hosted
2022-11-02T09:18:02.5627780Z Job defined at: Attensi/unity_core_cheats/.github/workflows/test-and-release.yml@refs/heads/main
2022-11-02T09:18:02.5627801Z Waiting for a runner to pick up this job...
2022-11-02T09:18:02.7057810Z Job is about to start running on the runner: unity-runner-529tm-pznfc (organization)
2022-11-02T09:18:07.6856436Z Current runner version: '2.298.2'
2022-11-02T09:18:07.6861001Z Runner name: 'unity-runner-529tm-pznfc'
2022-11-02T09:18:07.6861362Z Runner group name: 'Default'
2022-11-02T09:18:07.6861974Z Machine name: 'unity-runner-529tm-pznfc'
2022-11-02T09:18:07.6863385Z ##[group]GITHUB_TOKEN Permissions
2022-11-02T09:18:07.6863847Z Actions: write
2022-11-02T09:18:07.6864062Z Checks: write
2022-11-02T09:18:07.6864223Z Contents: write
2022-11-02T09:18:07.6864431Z Deployments: write
2022-11-02T09:18:07.6864642Z Discussions: write
2022-11-02T09:18:07.6864844Z Issues: write
2022-11-02T09:18:07.6865032Z Metadata: read
2022-11-02T09:18:07.6865192Z Packages: write
2022-11-02T09:18:07.6865379Z Pages: write
2022-11-02T09:18:07.6865592Z PullRequests: write
2022-11-02T09:18:07.6865822Z RepositoryProjects: write
2022-11-02T09:18:07.6866029Z SecurityEvents: write
2022-11-02T09:18:07.6866198Z Statuses: write
2022-11-02T09:18:07.6866407Z ##[endgroup]
2022-11-02T09:18:07.6869552Z Secret source: Actions
2022-11-02T09:18:07.6870010Z Prepare workflow directory
2022-11-02T09:18:07.7581069Z Prepare all required actions
2022-11-02T09:18:07.7718694Z Getting action download info
2022-11-02T09:18:08.3417355Z Download action repository 'google-github-actions/release-please-action@v3' (SHA:2a4590f9c1d322790253d997de5cad7f7ad4bc1b)
2022-11-02T09:18:08.8409008Z Download action repository 'actions/checkout@v3' (SHA:93ea575cb5d8a053eaa0ac8fa3b40d7e05a33cc8)
2022-11-02T09:18:09.2127711Z Download action repository 'actions/setup-node@v3' (SHA:8c91899e586c5b171469028077307d293428b516)
2022-11-02T09:18:09.7515634Z A job started hook has been configured by the self-hosted runner administrator
2022-11-02T09:18:09.7640941Z ##[group]Run '/etc/arc/hooks/job-started.sh'
2022-11-02T09:18:09.7655709Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
2022-11-02T09:18:09.7655981Z ##[endgroup]
2022-11-02T09:18:09.7861710Z 2022-11-02 09:18:09.782  DEBUG --- Running ARC Job Started Hooks
2022-11-02T09:18:09.7862214Z 2022-11-02 09:18:09.783  DEBUG --- Running hook: /etc/arc/hooks/job-started.d/update-status
2022-11-02T09:18:09.8170962Z ##[group]Run google-github-actions/release-please-action@v3
2022-11-02T09:18:09.8171266Z with:
2022-11-02T09:18:09.8171671Z   token: ***
2022-11-02T09:18:09.8171852Z   release-type: node
2022-11-02T09:18:09.8172095Z   bump-minor-pre-major: true
2022-11-02T09:18:09.8172323Z   fork: false
2022-11-02T09:18:09.8172525Z   clean: true
2022-11-02T09:18:09.8172746Z   bump-patch-for-minor-pre-major: false
2022-11-02T09:18:09.8173007Z   changelog-host: https://github.com
2022-11-02T09:18:09.8173284Z   github-api-url: https://api.github.com
2022-11-02T09:18:09.8173561Z   github-graphql-url: https://api.github.com/graphql
2022-11-02T09:18:09.8173938Z   monorepo-tags: false
2022-11-02T09:18:09.8174140Z env:
2022-11-02T09:18:09.8174343Z   UNITY_CORE_UPM_CI_REF: main
2022-11-02T09:18:09.8174520Z ##[endgroup]
2022-11-02T09:18:10.3276528Z ❯ Fetching package.json from branch main
2022-11-02T09:18:10.7764312Z ✔ Looking for latest release on branch: main with prefix: com.attensi.core.cheats
2022-11-02T09:18:10.7765261Z ❯ Fetching merge commits on branch main with cursor: undefined
2022-11-02T09:18:12.1673327Z ❯ Found latest release pull request: 31 version: 1.4.1
2022-11-02T09:18:12.1674213Z ❯ Fetching releases with cursor undefined
2022-11-02T09:18:12.6024094Z ❯ found release for com.attensi.core.cheats Version {
2022-11-02T09:18:12.6024536Z   major: 1,
2022-11-02T09:18:12.6024775Z   minor: 4,
2022-11-02T09:18:12.6025016Z   patch: 1,
2022-11-02T09:18:12.6025305Z   preRelease: undefined,
2022-11-02T09:18:12.6025559Z   build: undefined
2022-11-02T09:18:12.6025782Z }
2022-11-02T09:18:12.6026232Z ❯ found release for com.attensi.core.cheats Version {
2022-11-02T09:18:12.6026554Z   major: 1,
2022-11-02T09:18:12.6026775Z   minor: 4,
2022-11-02T09:18:12.6027017Z   patch: 0,
2022-11-02T09:18:12.6027265Z   preRelease: undefined,
2022-11-02T09:18:12.6027516Z   build: undefined
2022-11-02T09:18:12.6027749Z }
2022-11-02T09:18:12.6028175Z ❯ SHA not found in recent commits to branch main, skipping
2022-11-02T09:18:12.6029268Z ❯ found release for com.attensi.core.cheats Version {
2022-11-02T09:18:12.6029565Z   major: 1,
2022-11-02T09:18:12.6029778Z   minor: 3,
2022-11-02T09:18:12.6029990Z   patch: 0,
2022-11-02T09:18:12.6030244Z   preRelease: undefined,
2022-11-02T09:18:12.6030487Z   build: undefined
2022-11-02T09:18:12.6030697Z }
2022-11-02T09:18:12.6031102Z ❯ SHA not found in recent commits to branch main, skipping
2022-11-02T09:18:12.6031582Z ❯ found release for com.attensi.core.cheats Version {
2022-11-02T09:18:12.6031889Z   major: 1,
2022-11-02T09:18:12.6032132Z   minor: 2,
2022-11-02T09:18:12.6032357Z   patch: 3,
2022-11-02T09:18:12.6032608Z   preRelease: undefined,
2022-11-02T09:18:12.6032872Z   build: undefined
2022-11-02T09:18:12.6033095Z }
2022-11-02T09:18:12.6033483Z ❯ SHA not found in recent commits to branch main, skipping
2022-11-02T09:18:12.6033973Z ❯ found release for com.attensi.core.cheats Version {
2022-11-02T09:18:12.6034269Z   major: 1,
2022-11-02T09:18:12.6034667Z   minor: 2,
2022-11-02T09:18:12.6034913Z   patch: 2,
2022-11-02T09:18:12.6035172Z   preRelease: undefined,
2022-11-02T09:18:12.6035422Z   build: undefined
2022-11-02T09:18:12.6035651Z }
2022-11-02T09:18:12.6036040Z ❯ SHA not found in recent commits to branch main, skipping
2022-11-02T09:18:12.6036615Z ❯ found release for com.attensi.core.cheats Version {
2022-11-02T09:18:12.6036931Z   major: 1,
2022-11-02T09:18:12.6037160Z   minor: 2,
2022-11-02T09:18:12.6037381Z   patch: 1,
2022-11-02T09:18:12.6037601Z   preRelease: undefined,
2022-11-02T09:18:12.6037850Z   build: undefined
2022-11-02T09:18:12.6038075Z }
2022-11-02T09:18:12.6038503Z ❯ SHA not found in recent commits to branch main, skipping
2022-11-02T09:18:12.6038979Z ❯ found release for com.attensi.core.cheats Version {
2022-11-02T09:18:12.6039301Z   major: 1,
2022-11-02T09:18:12.6039530Z   minor: 2,
2022-11-02T09:18:12.6039735Z   patch: 0,
2022-11-02T09:18:12.6040006Z   preRelease: undefined,
2022-11-02T09:18:12.6040275Z   build: undefined
2022-11-02T09:18:12.6040527Z }
2022-11-02T09:18:12.6041133Z ❯ SHA not found in recent commits to branch main, skipping
2022-11-02T09:18:12.6041618Z ❯ found release for com.attensi.core.cheats Version {
2022-11-02T09:18:12.6041955Z   major: 1,
2022-11-02T09:18:12.6042175Z   minor: 1,
2022-11-02T09:18:12.6042402Z   patch: 0,
2022-11-02T09:18:12.6042661Z   preRelease: undefined,
2022-11-02T09:18:12.6042921Z   build: undefined
2022-11-02T09:18:12.6043149Z }
2022-11-02T09:18:12.6043544Z ❯ SHA not found in recent commits to branch main, skipping
2022-11-02T09:18:12.6044032Z ❯ found release for com.attensi.core.cheats Version {
2022-11-02T09:18:12.6044338Z   major: 1,
2022-11-02T09:18:12.6044580Z   minor: 0,
2022-11-02T09:18:12.6044802Z   patch: 0,
2022-11-02T09:18:12.6045043Z   preRelease: undefined,
2022-11-02T09:18:12.6045274Z   build: undefined
2022-11-02T09:18:12.6045506Z }
2022-11-02T09:18:12.6045919Z ❯ SHA not found in recent commits to branch main, skipping
2022-11-02T09:18:12.6046354Z ❯ found release for com.attensi.core.cheats Version {
2022-11-02T09:18:12.6046750Z   major: 0,
2022-11-02T09:18:12.6046984Z   minor: 0,
2022-11-02T09:18:12.6047210Z   patch: 1,
2022-11-02T09:18:12.6047457Z   preRelease: undefined,
2022-11-02T09:18:12.6047707Z   build: undefined
2022-11-02T09:18:12.6047946Z }
2022-11-02T09:18:12.6048349Z ❯ SHA not found in recent commits to branch main, skipping
2022-11-02T09:18:12.6048818Z ❯ found 2 possible releases. [
2022-11-02T09:18:12.6049099Z   Version {
2022-11-02T09:18:12.6049329Z     major: 1,
2022-11-02T09:18:12.6049573Z     minor: 4,
2022-11-02T09:18:12.6049806Z     patch: 1,
2022-11-02T09:18:12.6050068Z     preRelease: undefined,
2022-11-02T09:18:12.6050329Z     build: undefined
2022-11-02T09:18:12.6050553Z   },
2022-11-02T09:18:12.6050766Z   Version {
2022-11-02T09:18:12.6050979Z     major: 1,
2022-11-02T09:18:12.6051194Z     minor: 4,
2022-11-02T09:18:12.6051419Z     patch: 1,
2022-11-02T09:18:12.6051640Z     preRelease: undefined,
2022-11-02T09:18:12.6051876Z     build: undefined
2022-11-02T09:18:12.6052233Z   }
2022-11-02T09:18:12.6052448Z ]
2022-11-02T09:18:12.6052799Z ✔ Building releases
2022-11-02T09:18:12.6053144Z ✔ Building strategies by path
2022-11-02T09:18:12.6053494Z ❯ .: node
2022-11-02T09:18:13.6172587Z ❯ Fetching package.json from branch main
2022-11-02T09:18:13.6173355Z ✔ Looking for latest release on branch: main with prefix: com.attensi.core.cheats
2022-11-02T09:18:13.6173996Z ❯ Fetching merge commits on branch main with cursor: undefined
2022-11-02T09:18:14.5738026Z ❯ Found latest release pull request: 31 version: 1.4.1
2022-11-02T09:18:14.5738409Z ❯ Fetching releases with cursor undefined
2022-11-02T09:18:14.9298818Z ❯ found release for com.attensi.core.cheats Version {
2022-11-02T09:18:14.9299152Z   major: 1,
2022-11-02T09:18:14.9299390Z   minor: 4,
2022-11-02T09:18:14.9299626Z   patch: 1,
2022-11-02T09:18:14.9299903Z   preRelease: undefined,
2022-11-02T09:18:14.9300163Z   build: undefined
2022-11-02T09:18:14.9300406Z }
2022-11-02T09:18:14.9300826Z ❯ found release for com.attensi.core.cheats Version {
2022-11-02T09:18:14.9301165Z   major: 1,
2022-11-02T09:18:14.9301380Z   minor: 4,
2022-11-02T09:18:14.9301586Z   patch: 0,
2022-11-02T09:18:14.9301840Z   preRelease: undefined,
2022-11-02T09:18:14.9302104Z   build: undefined
2022-11-02T09:18:14.9302341Z }
2022-11-02T09:18:14.9302762Z ❯ SHA not found in recent commits to branch main, skipping
2022-11-02T09:18:14.9303262Z ❯ found release for com.attensi.core.cheats Version {
2022-11-02T09:18:14.9303564Z   major: 1,
2022-11-02T09:18:14.9303795Z   minor: 3,
2022-11-02T09:18:14.9304077Z   patch: 0,
2022-11-02T09:18:14.9304344Z   preRelease: undefined,
2022-11-02T09:18:14.9304594Z   build: undefined
2022-11-02T09:18:14.9304809Z }
2022-11-02T09:18:14.9305233Z ❯ SHA not found in recent commits to branch main, skipping
2022-11-02T09:18:14.9305699Z ❯ found release for com.attensi.core.cheats Version {
2022-11-02T09:18:14.9306014Z   major: 1,
2022-11-02T09:18:14.9306252Z   minor: 2,
2022-11-02T09:18:14.9306461Z   patch: 3,
2022-11-02T09:18:14.9306723Z   preRelease: undefined,
2022-11-02T09:18:14.9307173Z   build: undefined
2022-11-02T09:18:14.9307401Z }
2022-11-02T09:18:14.9307797Z ❯ SHA not found in recent commits to branch main, skipping
2022-11-02T09:18:14.9308181Z ❯ found release for com.attensi.core.cheats Version {
2022-11-02T09:18:14.9308681Z   major: 1,
2022-11-02T09:18:14.9308879Z   minor: 2,
2022-11-02T09:18:14.9309058Z   patch: 2,
2022-11-02T09:18:14.9309270Z   preRelease: undefined,
2022-11-02T09:18:14.9309549Z   build: undefined
2022-11-02T09:18:14.9309764Z }
2022-11-02T09:18:14.9310139Z ❯ SHA not found in recent commits to branch main, skipping
2022-11-02T09:18:14.9310661Z ❯ found release for com.attensi.core.cheats Version {
2022-11-02T09:18:14.9310987Z   major: 1,
2022-11-02T09:18:14.9311234Z   minor: 2,
2022-11-02T09:18:14.9311472Z   patch: 1,
2022-11-02T09:18:14.9311728Z   preRelease: undefined,
2022-11-02T09:18:14.9311987Z   build: undefined
2022-11-02T09:18:14.9312169Z }
2022-11-02T09:18:14.9312539Z ❯ SHA not found in recent commits to branch main, skipping
2022-11-02T09:18:14.9313038Z ❯ found release for com.attensi.core.cheats Version {
2022-11-02T09:18:14.9313355Z   major: 1,
2022-11-02T09:18:14.9313588Z   minor: 2,
2022-11-02T09:18:14.9313823Z   patch: 0,
2022-11-02T09:18:14.9314101Z   preRelease: undefined,
2022-11-02T09:18:14.9314383Z   build: undefined
2022-11-02T09:18:14.9314638Z }
2022-11-02T09:18:14.9314987Z ❯ SHA not found in recent commits to branch main, skipping
2022-11-02T09:18:14.9315402Z ❯ found release for com.attensi.core.cheats Version {
2022-11-02T09:18:14.9315700Z   major: 1,
2022-11-02T09:18:14.9315929Z   minor: 1,
2022-11-02T09:18:14.9316133Z   patch: 0,
2022-11-02T09:18:14.9316349Z   preRelease: undefined,
2022-11-02T09:18:14.9316597Z   build: undefined
2022-11-02T09:18:14.9316807Z }
2022-11-02T09:18:14.9317203Z ❯ SHA not found in recent commits to branch main, skipping
2022-11-02T09:18:14.9317659Z ❯ found release for com.attensi.core.cheats Version {
2022-11-02T09:18:14.9317966Z   major: 1,
2022-11-02T09:18:14.9318338Z   minor: 0,
2022-11-02T09:18:14.9318568Z   patch: 0,
2022-11-02T09:18:14.9318788Z   preRelease: undefined,
2022-11-02T09:18:14.9319029Z   build: undefined
2022-11-02T09:18:14.9319253Z }
2022-11-02T09:18:14.9319605Z ❯ SHA not found in recent commits to branch main, skipping
2022-11-02T09:18:14.9320076Z ❯ found release for com.attensi.core.cheats Version {
2022-11-02T09:18:14.9320368Z   major: 0,
2022-11-02T09:18:14.9320573Z   minor: 0,
2022-11-02T09:18:14.9320782Z   patch: 1,
2022-11-02T09:18:14.9321018Z   preRelease: undefined,
2022-11-02T09:18:14.9321283Z   build: undefined
2022-11-02T09:18:14.9321498Z }
2022-11-02T09:18:14.9321892Z ❯ SHA not found in recent commits to branch main, skipping
2022-11-02T09:18:14.9322285Z ❯ found 2 possible releases. [
2022-11-02T09:18:14.9322550Z   Version {
2022-11-02T09:18:14.9322766Z     major: 1,
2022-11-02T09:18:14.9322983Z     minor: 4,
2022-11-02T09:18:14.9323199Z     patch: 1,
2022-11-02T09:18:14.9323472Z     preRelease: undefined,
2022-11-02T09:18:14.9323717Z     build: undefined
2022-11-02T09:18:14.9323931Z   },
2022-11-02T09:18:14.9324148Z   Version {
2022-11-02T09:18:14.9324396Z     major: 1,
2022-11-02T09:18:14.9324641Z     minor: 4,
2022-11-02T09:18:14.9324887Z     patch: 1,
2022-11-02T09:18:14.9325134Z     preRelease: undefined,
2022-11-02T09:18:14.9325365Z     build: undefined
2022-11-02T09:18:14.9325576Z   }
2022-11-02T09:18:14.9325766Z ]
2022-11-02T09:18:14.9326106Z ✔ Building pull requests
2022-11-02T09:18:14.9326448Z ✔ Building strategies by path
2022-11-02T09:18:14.9326724Z ❯ .: node
2022-11-02T09:18:14.9327048Z ✔ Collecting release commit SHAs
2022-11-02T09:18:14.9327398Z ❯ release search depth: 400
2022-11-02T09:18:14.9327754Z ❯ Fetching releases with cursor undefined
2022-11-02T09:18:15.3622848Z ❯ Found release for path ., v1.4.1
2022-11-02T09:18:15.3623435Z ❯ release for path: ., version: 1.4.1, sha: 7a3ced2cd4be0a09a2dd93c6b7009ed8a10b467b
2022-11-02T09:18:15.3623938Z ✔ Collecting commits since all latest releases
2022-11-02T09:18:15.3624331Z ❯ commit search depth: 500
2022-11-02T09:18:15.3626359Z ❯ Set(1) { '7a3ced2cd4be0a09a2dd93c6b7009ed8a10b467b' }
2022-11-02T09:18:15.3626833Z ❯ Fetching merge commits on branch main with cursor: undefined
2022-11-02T09:18:16.3246461Z ❯ Backfilling file list for commit: eac148064a82c323193b2a081cacae3a468dd2b3
2022-11-02T09:18:16.5806934Z ❯ Found 2 files
2022-11-02T09:18:16.5807306Z ❯ Backfilling file list for commit: 7ba24fd265d1b7a67551fab3b49d0db48e7e812c
2022-11-02T09:18:16.8528537Z ❯ Found 1 files
2022-11-02T09:18:16.8528870Z ❯ Backfilling file list for commit: 8ddbaac01c7aaca30065822678c7cd6115d446fc
2022-11-02T09:18:17.1186651Z ❯ Found 2 files
2022-11-02T09:18:17.3579762Z ❯ Backfilling file list for commit: 64f2c9addc8da97ecf63a2bb9348dad8887f758b
2022-11-02T09:18:17.3580062Z ❯ Found 3 files
2022-11-02T09:18:17.3580339Z ❯ Backfilling file list for commit: 72cb2dd01f72e8f01f73956ecd1718ab93437249
2022-11-02T09:18:17.6246001Z ❯ Found 3 files
2022-11-02T09:18:17.6246397Z ❯ Backfilling file list for commit: 29eab324d5b82ae20f0259c61104993cd4d2a66e
2022-11-02T09:18:17.8815569Z ❯ Found 3 files
2022-11-02T09:18:17.8816059Z ❯ Backfilling file list for commit: 9b6da60adbb9420dd4fd226250ac7e57a9049f24
2022-11-02T09:18:18.1655841Z ❯ Found 2 files
2022-11-02T09:18:18.1656177Z ❯ Backfilling file list for commit: 2cb5e9a9129e1d3b6619bdb4955369a3619a1970
2022-11-02T09:18:18.4227331Z ❯ Found 9 files
2022-11-02T09:18:18.4227688Z ❯ Backfilling file list for commit: 3c67462eed816f5be2ffb85cf26a0b92e73f9714
2022-11-02T09:18:18.6780692Z ❯ Found 4 files
2022-11-02T09:18:18.6781073Z ❯ Backfilling file list for commit: 90aeaf76d96c38d2ee1cf54127e59b0025d70dac
2022-11-02T09:18:19.0330427Z ❯ Found 3 files
2022-11-02T09:18:19.0330908Z ❯ Backfilling file list for commit: c7bbafeeeb13827ca0bbe15edd35970a7e7b046f
2022-11-02T09:18:19.2881651Z ❯ Found 1 files
2022-11-02T09:18:19.2881997Z ❯ Backfilling file list for commit: da67f7496ac91e97d4bc1879944861ca7873eb6d
2022-11-02T09:18:19.5727145Z ❯ Found 2 files
2022-11-02T09:18:19.5728148Z ❯ Backfilling file list for commit: 7eee4402840a3092156ea5995293f1cfb987795f
2022-11-02T09:18:19.8518088Z ❯ Found 5 files
2022-11-02T09:18:19.8518334Z ✔ Splitting 3 commits by path
2022-11-02T09:18:19.8521451Z ✔ Building candidate release pull request for path: .
2022-11-02T09:18:19.8521668Z ❯ type: node
2022-11-02T09:18:19.8521842Z ❯ targetBranch: main
2022-11-02T09:18:19.8522028Z ❯ commits: 3
2022-11-02T09:18:19.8529348Z ❯ commit could not be parsed: baa8cf5b3838e1489b967a24ca073846777c2280 Merge pull request #28 from Attensi/feat/playerprefscheat
2022-11-02T09:18:19.8531002Z ❯ commit could not be parsed: 4ea1dc62d25702aef4100405363039989ae943fb Merge pull request #30 from Attensi/feat/timescalecheat
2022-11-02T09:18:19.8532225Z ❯ commit could not be parsed: 5b282942ad98578d2ea18c95977e4254db568464 Merge pull request #29 from Attensi/feat/fpscheat
2022-11-02T09:18:19.8532498Z ✔ Considering: 0 commits
2022-11-02T09:18:19.8532706Z ✔ No commits for path: ., skipping
2022-11-02T09:18:19.8652263Z A job completed hook has been configured by the self-hosted runner administrator
2022-11-02T09:18:19.8680605Z ##[group]Run '/etc/arc/hooks/job-completed.sh'
2022-11-02T09:18:19.8693908Z shell: /usr/bin/bash --noprofile --norc -e -o pipefail {0}
2022-11-02T09:18:19.8694130Z ##[endgroup]
2022-11-02T09:18:19.8742663Z 2022-11-02 09:18:19.873  DEBUG --- Running ARC Job Completed Hooks
2022-11-02T09:18:19.8754042Z 2022-11-02 09:18:19.875  DEBUG --- Running hook: /etc/arc/hooks/job-completed.d/update-status
2022-11-02T09:18:19.8879730Z Cleaning up orphan processes

Additional information
The merge commit messages that don't work are:
Merge pull request #29 from Attensi/feat/fpscheat

feat: Added FPS widget cheat

Merge pull request #30 from Attensi/feat/timescalecheat

feat: Added timescale cheat

Merge pull request #28 from Attensi/feat/playerprefscheat

feat: Added remove player prefs cheat

All the PR's and branches that were merged were created before the previous release, and merged afterwards - perhaps this is relevant?
The errors are probably generated here. https://github.com/googleapis/release-please/blob/21ed59a1db32c6b9593931519bfa3b1eb456a4a7/src/commit.ts#L396

We have also been experiencing this error, we are using squash and merge.

release-please cares about the commit message and the above examples are not valid conventional commits. Maintainers should be aware of the exact messages that make it into the release branch.

These messages are the default merge messages generated by GitHub when merging a PR. We see this button:

The merge page then shows this:

Is it intended behaviour that hitting Confirm Merge, using the default values provided by GitHub, does not create a commit that can be parsed by release-please-action? Typing in new information in this page is prone to human error.
Or am I missing something obvious here?

release-please cares about the commit message and the above examples are not valid conventional commits. Maintainers should be aware of the exact messages that make it into the release branch.

I don't understand how these are not conventional commits. This one was accepted:
Merge pull request #27 from Attensi/feat/changeloglevelscheat

feat: Added change log levels cheat

This one was not accepted:
Merge pull request #29 from Attensi/feat/fpscheat

feat: Added FPS widget cheat

Would you be so kind as to tell me why PR #27 is a convetional commit, and PR #29 is not a conventional commit?

I don't understand why this issue is labeled 'type:question'. release-please seems to be treating identically structured commit messages in different ways, I think that has to be a bug.

In my instance I don't believe that my commit messages are incorrect. We're using squash merge and husky to automate/control the commit messages and ensure that they DO follow the conventional commit messages so I don't see how that would be an issue.
I'm not sure if I'm using this GitHub Action improperly with squash commits but I've tried various types of commit messages and it still seems to skip over them all.
Can this is actually be confirmed to be working with squash merging? I know the previous automatic releases we used was handled with TriPSs/conventional-changelog-action@v3.15.0 and it was working but does not work with squash merging, so could this be case here as well?

I've tried again today to get squash merging to work with release-please although still with no luck. I got the still get the commit could not be parsed error. please see the following log:

I'm not sure why since this is the PR / commit that it's trying to parse

I tried a previous squash merge PR and used the conventional commit message as the PR title and it did work although it doesn't seem to work when the commit messages are in the description.

Sorry for the delay in getting to this.
@Mexmorize Even if you are squash merging, the commit message of https://github.com/google-github-actions/release-please-action/issues/651#issuecomment-1307474280 does not follow the https://conventionalcommits.org spec. The secondary commit messages do match the extended commit format, but the main message needs to look like a convetional commit.
A few options that could have worked:
meta: fixed AB#0011 lets go (#25)

fix(docs): updated README with TODO
feat(docs): added uninstalled husky info in README

fix(docs): updated README with TODO (#25)

Fixed AB#0011 lets go
feat(docs): added uninstalled husky info in README

Additionally, if you are using pull requests (like you are), you can rewrite what release-please looks at for the commit if you make a mistake: https://github.com/googleapis/release-please#how-can-i-fix-release-notes

Also note that the failure to parse the message is just a warning and that it will ignore the commit message (rather than crash).

It's still an issue that automatically generated GitHub merge messages sometimes - but not always - fail to be picked up by release-please-action.
I do understand that a commit message with Merge is not a valid conventional commit, but it is the message that GitHub generates by default - so for ease of use it should be possible to allow the default GitHub commit messages in addition to conventional commits.

authors: ChristianTellefsen Mexmorize chingor13


text:
Fix README gzip description

Fix README issue in gzip input description

Hi @NickDub could you please sign the CLA?

source: gharchive/pull-request

authors: NickDub sethvargo

license_type: permissive

license_source: bigquery


text:
TypeError: init() should return None, not 'NoneType'

Error:
(football-env) ➜  football git:(master) python -m gfootball.play_game --action_set=full
Traceback (most recent call last):
File "/Users/xxx/.pyenv/versions/3.8.2/lib/python3.8/runpy.py", line 193, in _run_module_as_main
return _run_code(code, main_globals, None,
File "/Users/xxx/.pyenv/versions/3.8.2/lib/python3.8/runpy.py", line 86, in _run_code
exec(code, run_globals)
File "/Users/xxx/dev/football/gfootball/play_game.py", line 70, in
app.run(main)
File "/Users/xxx/dev/football/football-env/lib/python3.8/site-packages/absl/app.py", line 300, in run
_run_main(main, args)
File "/Users/xxx/dev/football/football-env/lib/python3.8/site-packages/absl/app.py", line 251, in _run_main
sys.exit(main(argv))
File "/Users/xxx/dev/football/gfootball/play_game.py", line 46, in main
cfg = config.Config({
File "/Users/xxx/dev/football/gfootball/env/config.py", line 98, in init
self.NewScenario()
File "/Users/xxx/dev/football/gfootball/env/config.py", line 153, in NewScenario
self._scenario_cfg = scenario_builder.Scenario(self).ScenarioConfig()
File "/Users/xxx/dev/football/gfootball/env/scenario_builder.py", line 62, in init
scenario.build_scenario(self)
File "/Users/xxx/dev/football/gfootball/scenarios/11_vs_11_stochastic.py", line 33, in build_scenario
builder.AddPlayer(-1.000000, 0.000000, e_PlayerRole_GK)
File "/Users/xxx/dev/football/gfootball/env/scenario_builder.py", line 108, in AddPlayer
player = Player(x, y, role, lazy, controllable)
TypeError: init() should return None, not 'NoneType'
Step to reproduce:
brew install git python3 cmake sdl2 sdl2_image sdl2_ttf sdl2_gfx boost boost-python3
brew install sdl sdl_image sdl_mixer sdl_ttf portmidi
cd dev
git clone https://github.com/google-research/football.git
cd football
python3 -m venv football-env
source football-env/bin/activate
pip3 install .
python3 -m gfootball.play_game --action_set=full
Env:
MacOs Catalina 10.15.7
Use of pyenv in place

Your error is very similar to one that other folks have when using Anaconda (e.g. #156). Did your try using brew's version of Python 3.8 instead of pyenv to create a virtual environment as I noted here:
$(brew --prefix python3)/bin/python3.8 -m venv football-env

Runnnig $(brew --prefix python3)/bin/python3.8 -m venv football-env gives "syntax error near unexpected token `/bin/python3.8"

What version of python do you have? What is the result of command python3 -V?

I have version 3.8.6.

I have deleted Anaconda, reinstalled everything with reboot and tried with python 3.7.5 too. Tried with and without the virtual environments. My error message is identical to the one "asappia" get

It's quite hard to give any advice without knowing the whole picture. If you uninstalled Anaconda, you should've installed python3 using brew? I'm wondering how you can get python 3.7.5 if the default major version in brew is 3.8. As I explained earlier, in my opinion, the error TypeError: __init__() should return None, not 'NoneType' happens when someone installs boost-python3 with brew, but for installing football uses python3 that doesn't come from brew.

Ah ok, that is probably the case then. Just thought the packages had to be installed with brew not Python it self. Thanks for your help, I really appreciate it.

I get the same error after following the instructions with Catalina 10.15.7 and python3 version 3.8.5. I have deleted and reinstalled all of the modules to create the environment but I still get the same errors as "asappia". Anaconda is not installed. I have used brew to install boost ( version 1.73.0 ) and boost-python3 ( version 1.73.0 ).  Do I need to install python3 using brew ?

@dtinblack Yes, as per instruction in readme.

It's been resolved for me now. Uninstalling the python3 versions that where installed from other sources did the trick.  Thank you so much @vi3itor

Thanks @vi3itor for your help. Like @audunae I deleted all of the packages that were installed from other sources and the package is now working.

Could you propose a note to the readme to address this problem (and make a pull request)?

Your error is very similar to one that other folks have when using Anaconda (e.g. #156). Did your try using brew's version of Python 3.8 instead of pyenv to create a virtual environment as I noted here:
$(brew --prefix python3)/bin/python3.8 -m venv football-env

@vi3itor Hi, I create a virtual env through $(brew --prefix python3)/bin/python3.8 -m venv football-env , and how can I list and revisit this env?

Hi @yanxue7, the command you executed created football-env directory inside the directory where you ran the command in the Terminal. To revisit (reactivate) the environment after you closed the Terminal window or rebooted Mac, open Terminal window again, navigate to the same directory (where football-env is located) and run source football-env\bin\activate to activate the environment.

Hi @yanxue7, the command you executed created football-env directory inside the directory where you ran the command in the Terminal. To revisit (reactivate) the environment after you closed the Terminal window or rebooted Mac, open Terminal window again, navigate to the same directory (where football-env is located) and run source football-env\bin\activate to activate the environment.

Thanks for your help, I learn it.

source: gharchive/issue

authors: asappia audunae dtinblack qstanczyk vi3itor yanxue7

repo: google-research/football


text:
Fix typo

What's changed, or what was fixed?

fix typo

Fixes: N/A
Target Live Date: N/A

[ ] This has been reviewed and approved by (NAME)
[X] I have run gulp test locally and all tests pass.
[ ] I have added the appropriate type-something label.
[ ] I've staged the site and manually verified that my content displays correctly.

CC: @petele

:tada: This has been pushed live to https://developers.google.com/web/

repo: google/WebFundamentals


text:
Small fixes to the Custom Easing article

What's changed, or what was fixed?
In the Custom Easing article,

Improved a sentence to say "coordinates of a point" instead of "coordinate of a point" and explicitly state that (1, 1) are the coordinates of the ending point of a Bézier curve.
Updated a link from being http to https.

CC: @petele

:tada: This has been pushed live to https://developers.google.com/web/

authors: WebFundBot kyarik


text:
Vision Bonnet board not working

My Vision Bonnet board is not working now. I try to figure out what is the problem
After booting up, I typed the following command and found not any aiy module being actually loaded
$ sudo systemctl stop joy_detection_demo.service
$ sudo rmmod aiy_vision
$ sudo rmmod aiy_adc
$ sudo rmmod pwm_aiy_io
$ sudo rmmod gpio_aiy_io
$ sudo rmmod aiy_io_i2c
then I typed the command and got the error like this
$ i2cdetect -y 1
Error: Could not open file /dev/i2c-1' or /dev/i2c/1': No such file or directory
Is it the problem of the short flexible ribbon cable? Or the entire Vision Bonnet it  broken?

@alpha-david Can you confirm if you have flashed your sdcard with the latest AIY image : https://github.com/google/aiyprojects-raspbian/releases/tag/v20201120 ?

I just flashed the latest image (aiyprojects-2020-11-20.img). I can't access the camera (Raspicam V2.1) when I connect it following the AIY website instructions (flat cable from RPI Zero W to AIY Bonnet and camera connected directly to the AIY Bonnet). Tried the simplest raspistill -o test.png and the output was Camera control callback  cmd=0x4f525245mmal: No data received from sensor. Check all connections, including the Sunny one on the camera board. I was hoping this problem was fixed in the latest image... :(

authors: alpha-david manoj7410 ricardodeazambuja

repo: google/aiyprojects-raspbian


text:
[R&D] Ability to update APK and or FHIR resources without internet

In the context of CHW program in Liberia, we may have users who work offline for months at a time.  In this context, the way they sync data is via P2P with a visiting supervisor who downloads new activity from their device which is then submitted to the server when the supervisor gains access to the Internet.
In this example, it would be ideal if we can do support 2 things.
1 - We would want to update the content of the app. Eg. Questionnaire changes.  We assume this can be just part of the modified resources that would be part of the P2P sync.
2 - Ability to upgrade the APK itself.  Hopefully, with the ability to modify content via FHIR this is not needed as often.  Since the SDK/APK will be rapidly evolving having the ability to do this though would be great.

thanks matt!

can you share the p2p library you'll be using?
i don't think we ever want to update the sdk without updating the apk. so this really is a question of how to update apps. play store does some clever stuff but i don't know they are applicable in the offline setting where you probably just want to adb install. i think this item is out-of-scope for this codebase.

This is the p2p library OpenSRP currently uses, https://github.com/OpenSRP/android-p2p-sync
On (2) agree, oos

I'll close this and mark as duplicate of https://github.com/google/android-fhir/issues/258 where we should continue the discussion.

authors: jingtang10 mberg pld

repo: google/android-fhir


text:
enableWhenExpression Support

IMPORTANT: All PRs must be linked to an issue (except for extremely trivial and straightforward changes).
Fixes #https://github.com/google/android-fhir/issues/819
Description
Clear and concise code change description.
Alternative(s) considered
Have you considered any alternatives? And if so, why have you chosen the approach in this PR?
Type
Choose one: (Bug fix | Feature | Documentation | Testing | Code health | Builds | Releases | Other)
Screenshots (if applicable)
Checklist

[x] I have read and acknowledged the Code of conduct.
[x] I have read the Contributing page.
[x] I have signed the Google Individual CLA, or I am covered by my company's Corporate CLA.
[ ] I have discussed my proposed solution with code owners in the linked issue(s) and we have agreed upon the general approach.
[x] I have run ./gradlew spotlessApply and ./gradlew spotlessCheck to check my code follows the style guide of this project.
[x] I have run ./gradlew check and ./gradlew connectedCheck to test my changes locally.
[x] I have built and run the demo app(s) to verify my change fixes the issue and/or does not break the demo app(s).

@jingtang10 can we arrange a meeting to discuss this PR?

@RaaziaTarique , has this PR been discussed with Jing?

authors: RaaziaTarique Tarun-Bhardwaj


text:
NearBy Message API not working with iBeacon uploaded on beacon platform

I have uploaded one iBeacon(Kontakt) in my Beacon Platform project . I used python sample to upload the same.  I used below call for this
pb-cli --service-account-creds creds.json register-beacon --beacon-json '{"advertisedId":{"type":"IBEACON","id":""},"status":"ACTIVE"}' --no-ibeacon-props
Here Encoded Id is generated by encoding iBeacon UDID + Major(Hex) + Minor(Hex)
My iBeacon is uploaded successfully and I can see it in my Beacon Platform dashboard, however I am not able to receive messages in my app which is developed using NearBy samples.
Please note it's working perfectly fine for beacons using eddystone protocol (Kontakt again) which I uploaded using Beacon Tools mobile app. I am using NearBy Message sample for both Foreground and Background mode, and I am getting messages only for eddystone beacon , not for iBeacon.
Are any additional steps needed for iBeacon ?

Any update on this issue ?

Guys,
Any update on this ? Please let me know if I need to provide any more details on this.
Thanks,
Ashutosh

Hey,
to use Nearby Messages you need to add some attachments to your beacon; the Android API fetches these attachments and delivers them as messages (not raw beacon IDs).
Take a look here: https://developers.google.com/beacons/proximity/attachments
HTH!
p

Thanks  for responding P.
Actually I am using attachments. Also everything works for me if I am using Beacon with Eddystone format, I am only seeing issue if I am using iBeacon instead.
Thanks,
Ashutosh

repo: google/beacon-platform


text:
Allow the lobby API to require a secret for all requests

If an environment variable LOBBY_SECRET is provided when the API server is started, then all API requests will require that secret in a header named lobby-secret. (Issue #198)
This check is provided as a middleware for the API koa server.
Checklist

[x] Use a separate branch in your local repo (not master).
[x] Test coverage is 100% (or you have a story for why it's ok).

This is branched from #189 , so will require a rebase when it lands.

Coverage remained the same at 100.0% when pulling 703b267757f6829f733049da6908be80e981faf2 on scally:lobby-protect into 479e7d93af8464f911a0fc5f82923eb91b3a0d27 on google:master.

authors: coveralls scally

license: MIT

license_source: github-api


text:
The js_module_root flag doesn't work as documented

Currently, the ES6 module loader interprets import paths that start with / as absolute filesystem paths.  e.g., you can have:
import { X } from '/home/hearnden/projects/myproj/app/x';

Surely it would be more useful, and probably closer in line with https://html.spec.whatwg.org/multipage/webappapis.html#integration-with-the-javascript-module-system, for the path to be interpreted with respect to (one of) the module root URIs.
e.g., with a module root URI of /home/hearnden/projects/myproj/app, you could have:
import { X } from '/x';

which would do the right thing, regardless of the path of the importing script.
This appears trivial to make happen:
diff --git a/src/com/google/javascript/jscomp/ES6ModuleLoader.java b/src/com/google/javascript/jscomp/ES6ModuleLoader.java
index a36ff64..83e423a 100644
--- a/src/com/google/javascript/jscomp/ES6ModuleLoader.java
+++ b/src/com/google/javascript/jscomp/ES6ModuleLoader.java
@@ -102,9 +102,11 @@ public final class ES6ModuleLoader {
     URI uri = createUri(name);
     if (isRelativeIdentifier(name)) {
       URI referrerUri = normalizeInputAddress(referrer);
-      uri = referrerUri.resolve(uri);
+      uri = normalizeAddress(referrerUri.resolve(uri));
+    } else if (isAbsoluteIdentifier(name)) {
+      // Strip leading slash, to match the normalized entries in moduleUris.
+      uri = createUri(name.substring(1));
     }
-    URI normalized = normalizeAddress(uri);
     if (moduleUris.contains(normalized)) {
       return normalized;
     }

However, that change isn't backwards compatible, because it would break the use of absolute filesystem paths.  But surely that would be a good thing?

The compiler is actually pretty agnostic when it comes to where the absolute root actually is. It's based off the file path provided to it by the source flags --js=/path/to/foo.js. For instance, the grunt/gulp plugins anchor the root to the current working directory of the compiler.
Also, make sure you look at the --js_module_root flag.
The change you suggest above would break active projects.
I'm closing this issue for now. If the --js_module_root flag doesn't do what you want, then we can re-open.

Bare import paths work fine with --js_module_root, and this issue report doesn't affect them. Please note I'm talking about absolute import paths, not bare import paths.  i.e.,
import { X } from '/x/x';

not
import { X } from 'x/x';

Absolute import paths only get interpreted as a path from the filesystem root.  They don't get interpreted as a path from a module root.
Failing example:
/tmp/x/x.js:
export const X = 1;

/tmp/y/y.js:
import { X } from '/x/x';

With --js_module_root /tmp --js /tmp/x/x.js /tmp/y/y.js, the import fails:
/tmp/y/y.js:1: ERROR - Failed to load module "/x/x"
import { X } from '/x/x';
^

1 error(s), 0 warning(s)

The import works fine with the bare path x/x, which is the --js_module_root behavior you're describing.
All these invocations fail with the same error when attempting to use an absolute import path.

--js_module_root /tmp --js /tmp/x/x.js /tmp/y/y.js
--js_module_root /tmp --js x/x.js y/y.js

Using --js /x/x.js fails with ERROR - Cannot read: /x/x.js.

Ah - I think I see what you meant.
--js_module_root / --js x/x.js y/y.js does the trick, allowing an import of '/x/x' to get resolved as x/x relative to the the compiler's working directory.
So --js_module_root isn't a module root in the normal sense (i.e., a location from which to resolve module paths, like a classpath or an include path).  Rather, it's an arbitrary string prefix to strip off import paths before resolving the remainder against the current working directory of the compiler.  i.e., more like a mount point.
Thanks for your help.

I'm not sure I fully understand why this doesn't work:
--js_module_root /tmp --js /tmp/x/x.js /tmp/y/y.js

From my understanding of the flag, it should have. I may need to look into that more.

Apologies if this is hijacking this issue but I can't find any other issue or wiki page more relevant.
I am struggling to figure out how to get node_modules and commonjs requires to work with Closure Compiler using --js_module_root.
It would be really helpful if there was a node_modules example added here, showing the command line, directory structure, working dir (if relevant) and require line:
https://github.com/google/closure-compiler/wiki/JS-Modules
Also the command line usage could be more verbose. "Path prefixes to be removed from ES6 & CommonJS modules." I'm struggling to see why you'd want to put long prefixes in your require statements.

@supersteves The reason there is no documentation is it doesn't really work. You have to pre-process node_modules files so that the imports are paths instead of named modules.
There are changes to the compiler I have planned to address this, but nothing has been actually started yet.

Thanks @ChadKillingsworth ... saw your response only now after posting https://github.com/google/closure-compiler/issues/1773

I believe this is working as documented/intended.

authors: ChadKillingsworth hearnden supersteves

repo: google/closure-compiler


text:
Multi-line comment before else-if throws Parse error

Tested with: closure compiler v20190929, also happens on closure-compiler.appspot.com
Came across this while running closure compiler on some generated code. The following results in a parser error:
    function getClassFacts(node, staticProperties) {
      if (ts.some(staticProperties)) facts |= 1
      /* HasStaticInitializedProperties */
      ;
      if (isExportOfNamespace(node)) facts |= 8
      /* IsExportOfNamespace */
      ;else if (isDefaultExternalModuleExport(node)) facts |= 32
      /* IsDefaultExternalExport */
      ;
      return facts;
    }

This produces the following error (java -jar closure-compiler-v20190929.jar --compilation_level SIMPLE --js input.js --js_output_file output.js):
JSC_PARSE_ERROR: Parse error. '}' expected at line 8 character 7
      ;else if (isDefaultExternalModuleExport(node)) facts |= 32
       ^

Browsers and almost all parsers on https://astexplorer.net seem accept this code. Also, it only seems to happen when there is an else if after the if.

I think it's due to the weird code-styling (i.e. too corner case for the parser), this is working fine:
// ==ClosureCompiler==
// @output_file_name default.js
// @compilation_level SIMPLE_OPTIMIZATIONS
// ==/ClosureCompiler==

function getClassFacts(node, staticProperties) {
      if (ts.some(staticProperties)) {
      	facts |= 1
        /* HasStaticInitializedProperties */
      }
      if (isExportOfNamespace(node)) {
        facts |= 8
        /* IsExportOfNamespace */
      }
      else if (isDefaultExternalModuleExport(node)) {
        facts |= 32
	      /* IsDefaultExternalExport */
      }
      return facts;
}

Created Google internal issue http://b/143470545

@munizart one quibble with your second comment -
if (a) {}; else {}

is invalid and doesn't parse in Chrome or https://astexplorer.net/. The semicolon creates an empty statement after the if block.
Replacing the block with an expression seems to repro this and works in browser.
if (true) 1
; else {}

authors: blutorange kjin lauraharker munizart


text:
Update File System and File System Access APIs to the latest spec

Originally there was only one specification - File System Access API. Later it
was divided into 2 separate APIs and that's why I divided it into 2 separate
files.
On top of that I've updated both APIs to the latest specifications.

I'm afraid this is a very risky change, but I'll import it and test it to see what happens.

My first attempt at testing failed miserably, because I forgot to add the new file into our internal build setup.
I'm trying again now.
There's also a list of externs somewhere hard-coded into the java code that is used to enforce the standard externs get read in the right order. I suspect it may need updating, but it seems the 2 files that already existed aren't listed in it (i.e. searching across the compiler code for their names didn't find that java file), so maybe the new one doesn't need to be listed either. We'll see.

Thank you for your time @brad4d

I think I've dealt with all the breakages.
I'm sending this for review and will hopefully submit it this week.

This was merged by 17a20f5 but it looks like the commit comment didn't contain what it was supposed to in order to close this issue.


text:
long vector alignment

Long vectors (vectors of 8 or 16 elements) are not natively supported in SPIRV. To support them, we have a pass in clspv lowering them into a different form supported in SPIRV.
At the beginning we used to lower them into a struct of 8 or 16 scalar elements. But this solution prevents llvm from being able to access an element at a dynamic index.
So we changed it to be an array of 8 or 16 scalar elements. It worked pretty well for the previous issue. But I recently realized that it does not keep the same alignment as the one of the long vectors, which is problematic.
A solution could be to lower long vectors into a struct of one array of 8 or 16 scalar elements. I think llvm should still be able to access a dynamic index, and it should keep the alignment of the original long vector.

Lowering long vectors to struct of one array does not work as the alignment of the structure is the alignment of its component having the bigger alignment.
It means that we need to do it "by hand". I have a mock up that is taking care of the structure in the long vectors pass.
I also need to modify the clusterconstant pass, as the long vectors does not appear there anymore, but still, we need to keep the right alignment (maybe other pass needs to rework for that as well, clusterpodargs?).
Finally I have an issue with the ArrayStride in the generated SPIRV code with packed structures.
Here is an example:
typedef struct __attribute__ ((packed)) myPackedStruct {
    char2 vec;
    char cPost;
} testStruct;

My only idea to support those at the moment, is to lower all vectors inside packed structures into arrays.

here is an even harder structure to have packed with correct stride and alignment:
typedef struct __attribute__ ((packed)) myPackedStruct {
    short2 vec;
char cPost;
} testStruct;

The alignment of long vectors should be fixed by #906 and #907.
For the packing issue, I will open a new issue

repo: google/clspv


text:
rename "/image_info" API to "/version"

The "/version" API is standard.

Closed by pull request https://github.com/google/cluster-insight/pull/26 .

repo: google/cluster-insight


text:
Missing Go package github.com/containers/storage

Go package github.com/containers/storage is missing:

The package now appears, closing the issue.


text:
HTMLElement.style.setAttribute throw style.setAttribute is not a function

GWT version : 2.8.2
elemental2 version : 1.0.0-RC1
using the setAttribute from elemental2 CSSStyleDeclaration gives is not a function, while using setProperty works.
to repeat the case add the following code snippet
HTMLElement element= (HTMLElement) DomGlobal.document.createElement("div");
element.style.setProperty("padding-left","10px");//works
element.style.setAttribute("padding-right","10px");//fail

DomGlobal.document.body.appendChild(element);

the exception
App.java:13 Uncaught TypeError: element_0_g$.style.setAttribute is not a function
    at wzd_g$.xzd_g$ [as onModuleLoad_0_g$] (App.java:13)
    at Array.crb_g$ (org_00046sample_0004…MethodHolder.java:3)
    at initializeModules_0_g$ (ModuleUtils.java:44)
    at Dp_g$ (Impl.java:309)
    at Gp_g$ (Impl.java:368)
    at Impl.java:78
    at wqb_g$ (ModuleUtils.java:55)
    at App.java:9

i noticed that in the MDN documentation there is no setAttribute method
https://developer.mozilla.org/en-US/docs/Web/API/CSSStyleDeclaration
if it is something need to be fixed and i can make a PR for, i will gladly do.
Thanks

Thanks for the report.
It seems like an old IE API. Probably it is old enough that nobody cares. Please send a patch to @google/closure-compiler to remove following line:
https://github.com/google/closure-compiler/blob/master/externs/browser/w3c_css.js#L528

It seems we cannot remove the method form the original extern file but we could potentially remove that api by patching the extern file.

If we cannot remove, what about adding @deprecated?

Ok that's actually what they did so I think we can close this.

This will be much easier to notice by elemental2 users if https://github.com/google/jsinterop-generator/pull/6 is accepted, so that the @Deprecated is on the java types as well.

authors: gkdn jDramaix niloc132 vegegoku


text:
Improve Travis CI build Performance

According to the official document Fast Finishing, if some rows in the build matrix are allowed to fail, we can add fast_finish: true to the .travis.yml to get faster feedbacks.
=====================
If there are any inappropriate modifications in this PR, please give me a reply and I will change them.

@googlebot I signed it!

authors: ChenZhangg YunLemon

repo: google/error-prone


text:
Fix max anisotropy in Vulkan backend

Noticed this when working on the Metal backend. Anisotropy is provided as a logarithmic value, so we should bit-shift to get the correct value, as the OpenGL driver does.

Good catch!!  I double-checked the spec and you are correct.

authors: bejado prideout

repo: google/filament


text:
WIP: extract calculating the flex lines from FlexboxLayout to FlexboxHelper

Still WIP

This change is

Oops screwed up the PR while rebasing the change...
Discarding this and will send another PR.

repo: google/flexbox-layout


text:
Add python 3.8 support.

Description of the change

Motivation

Type of change
Choose one: (Bug fix | Feature request | Documentation | Other)
Checklist

[ ] I have performed a self-review of my code.
[ ] I have added detailed comments to my code where applicable.
[ ] I have verified that my change does not break existing code.
[ ] My PR is based on the latest changes of the main branch (if unsure, please run git pull --rebase upstream main).
[ ] I am familiar with the Google Style Guide for the language I have coded in.
[ ] I have read through the Contributing Guide and signed the Contributor License Agreement.

We should decide if 3.8 is something we're doing.

Yeah, and for anyone watching, large changes should be proposed via an issue/FR where we can discuss it before writing any code.

authors: markmcd mvinoba

repo: google/generative-ai-python


text:
docs: Add a link to CMake doc which shows the usage of FetchContent and add_subdirectory

Change-Id: I2e77e155c134d36f36ff38f3d3bc396a48b07ff6

:closed_book: MEV SW OD Build #27839 result: FAILURE

Manifest Name
Build Status
Jenkins Link
Artifacts
Unsuccessful Stages
Description

mev-ts-trunk
FAILURE
59604
 Artifacts
IPU SDK Build

mev-trunk
FAILURE
56680
 Artifacts
Simics_C0_ACC

mev-release
NOT AFFECTED

mev-ts-release
NOT AFFECTED

mev-ts-release-1.6.1
NOT AFFECTED

mev-ts-release-bitbake
NOT AFFECTED

mev-ts-release-external
NOT AFFECTED

mev-ts-trunk-bitbake
NOT AFFECTED

mev-ts-trunk-bitbake-c1
NOT AFFECTED

mev-ts-trunk-external
NOT AFFECTED

mev-upstream-idpf
NOT AFFECTED

:closed_book: MEV SW OD Build #27894 result: FAILURE

Manifest Name
Build Status
Jenkins Link
Artifacts
Unsuccessful Stages
Description

mev-trunk
FAILURE
56702
 Artifacts
IPU_IMC_6_6_4

mev-ts-trunk
SUCCESS
59633
 Artifacts

mev-release
NOT AFFECTED

mev-ts-release
NOT AFFECTED

mev-ts-release-1.6.1
NOT AFFECTED

mev-ts-release-bitbake
NOT AFFECTED

mev-ts-release-external
NOT AFFECTED

mev-ts-trunk-bitbake
NOT AFFECTED

mev-ts-trunk-bitbake-c1
NOT AFFECTED

mev-ts-trunk-external
NOT AFFECTED

mev-upstream-idpf
NOT AFFECTED

mev-ts-trunk BAT tests: success - build 59633 - it is required if PR have BAT MEV status check as mandatory. If failed, please review Tasks in provided link to Berta. For questions please contact with ipu.ci.triage.team@intel.com

authors: sys-ptipu valaxkong

repo: google/glog


text:
Package Name Mismatches

I find this odd since it seems to have been this way for a while, but Go has issues fetching the package since the go.mod name go-cmp and the actual name cmp aren't the same, forcing you to probably need to fork.

I don't understand the report here. What names aren't the same? What do you mean by "need to fork"?

Thanks, it's the 1st time I've seen this, and I already made my version fixing it based on my experience. I will see if I can get it properly working and delete my fork if so.

Thanks. I don't believe there's any issue here. The package name is github.com/google/go-cmp/cmp.

repo: google/go-cmp


text:
add SignKey gpg entity param to allow easier pgp signing of commits

This PR creates a new param for the Commit struct called SignKey.
SignKey is an openpgp.Entity type which is the standard way of reading and validating pgp keys.
When specified the key will be used to sign the commit. This makes it so the user does not have to sign the key externally and duplicate some of the logic the CreateCommit function does.
To maintain backward compatibility, if the Verification.Signature is defined SignKey will have no effect.
This provides similar functionality that go-git has: https://github.com/src-d/go-git/commit/7b6c1266556f59ac436fada3fa6106d4a84f9b56
Note from the git docs: https://github.com/octokit/routes/blob/152c0b5d156844e17a1805d0509c9a0b7cfc848f/routes/api.github.com/git.json#L282
To pass a `signature` parameter, you need to first manually create a valid PGP signature, which can be complicated. You may find it easier to [use the command line]

So I wanted to make it less complicated 😄

Thank you, @anandkumarpatel.
In the past, when "helper" functions have been suggested for this repo, we have typically requested that they be put in their own separate repo for a few reasons: it keeps the API surface area of this repo smaller, reduces the maintenance burden on this repo, and keeps its list of external dependencies smaller.
However, I can see how this can be useful, and I'm game to include it in this repo.
I'd like @willnorris and @gauntface to weigh in on their thoughts for including something like this first.

Closing abandoned PR.

@gmlewis Sorry, forgot about this one.
I rebased and updated my branch based on @willnorris feedback. Is it possible to reopen? or should I make another PR?

Oh, sure... no problem!  I was just trying to do some Spring Cleaning in June.  :smile:

Whups, it's not allowing me to reopen because of a force push. Can you please open another PR with these changes and we can run with that one?

No problem: Continued here: https://github.com/google/go-github/pull/1198

authors: anandkumarpatel gmlewis

repo: google/go-github


text:
Resume upload after program restart

Provide the capability for the ResumableUpload class to resume the upload that was in-progress when an upload program has halted and is subsequently restarted.
Unless otherwise directed, I intend to work on this issue and contribute the results to the google-api-dotnet-client repository.

Sounds like a feature to add. A few quick questions:

I assume the underlying APIs support this capability? How do you know which "upload" the file is a part of? When you initiate the upload do you get some form of token?
Would being able to resume a partial upload require passing in that token/state when restarting the upload?
Are there any guarantees from the API producer that partial uploads won't lead to corrupted files? e.g. during upload chunk N only half the bytes get sent, will restarting chunk N do the right thing?

@jskeet , @chrisdunelm who might have some thoughts on the design/approach.

I'll have to look at the code/protocol again, but it certainly sounds like a useful feature if it all works out. It would be nice to support resuming downloads in the same way, of course.

@chrsmith Thanks for your quick response. I have responded to your questions in italics below.
•I assume the underlying APIs support this capability? How do you know which "upload" the file is a part of? When you initiate the upload do you get some form of token?
Yes, the underlying APIs can support this capability via an overload of the Resume() and ResumeAsync() methods.
In the example upload program that I am developing, the application saves the UploadUri value and the name of the current file being uploaded to disk. Upon initiation, my example program checks for their presence on disk. If these values are not found on disk or the current filename does not match the saved filename, the example program executes UploadAsync(). If found and the filename matches, the example program prompts for permission to resume the prior upload and, if granted,  executes ResumeAsync() with an additional parameter (the saved UploadUri). Of course, this means that the application developer is responsible for ensuring that the UploadUri passed to the API is the UploadUri that matches the file that is currently open and was passed to the VideosResource.InsertMediaUpload in the Insert() method.
•Would being able to resume a partial upload require passing in that token/state when restarting the upload?
The UploadUri value previously saved by the application program is the token that is passed in via an overload of Resume() or ResumeAsync().
•Are there any guarantees from the API producer that partial uploads won't lead to corrupted files? e.g. during upload chunk N only half the bytes get sent, will restarting chunk N do the right thing?
I downloaded the ZIP file containing the source and created my own copy of Google.Apis.dll. I have interrupted and restarted my example program multiple times during upload of a video to YouTube. Upon playback, the video plays perfectly. This solution uses the ResumeAsync() method so files should be uploaded correctly as they are in cases where ResumeAsync() is used today.
I am continuing to test. There are only a few lines of changes to the google-api-dotnet-client source code to provide this feature. Would you like me to post those changes in a message here, send them in a private message or do you want to wait until I create a Pull Request?

A pull request would be ideal, definitely.

OK, when I get a little further along in my work, I will do a Pull Request.

In the example upload program that I am developing, the application saves the UploadUri value and the name of the current file being uploaded to disk. ... checks for their presence on disk. If these values are not found on disk or the current filename does not match the saved filename, the example program executes UploadAsync(). ... If found ... prompts for permission to resume the prior upload and, if granted,  executes ResumeAsync() with an additional parameter (the saved UploadUri).

This sounds like a perfect solution for desktop .NET applications. But if running .NET on other platforms -- WinPhone, Silverlight, Unity -- the file I/O APIs might not be available. I'm not worried about WinPhone and Silverlight, but Unity is a pretty big deal.
Would it make sense to have this functionality be opt-in? e.g. you register an object that will store UploadUri values to disk and look for previous UploadUri values? Not having things "just work' isn't ideal, but it would avoid complications for platforms with extra constraints.

@chrsmith
My example application is Windows Desktop.
My proposed changes to the ResumeableUpload Class are minimal and do not access the file system. Doing so is left up to the application developer. A developer working on something other than Windows Desktop could use my example application program as a starting point and replace my examples of saving the UploadUri and FullPathFilename to disk with whatever solution was best for them.

I am curious as to why the ResumableUpload.cs ProgressChanged event handler and UploadSessionData event handler are called using the .Invoke method but the ResponseReceived event handler is called without using the .Invoke method.

@mikemeinz: The ResponseReceived invocation is actually unsafe at the moment - it could become null after the check. Before C# 6, the code would have been better as:
var handler = ResponseReceived;
if (handler != null)
{
    handler(...);
}

But in C# 6 with the null conditional operator, this is equivalent to:
ResponseReceived?.Invoke(...);

I'll create a small PR to fix this... (I may try to find any similar occurrences, too...)

Can you tell me when my Pull Request to update the two ResumableUpload samples in the google-api-dotnet-client-samples library will be merged?
Thanks

I'll look at it this week. Sorry for the delay.

@mikemeinz Can this issue now be closed? Thanks for all your work on this :)

@chrisdunelm
Yes, this issue can be closed.
I have been running the latest version of google-api-dotnet-client using the new restart after program interruption capability without any issues. Also, the ResumableUpload samples in google-api-dotnet-client-samples have been updated to demonstrate how to use the new capability.
Thank you very much for your support during this process.

authors: chrisdunelm chrsmith jskeet mikemeinz

repo: google/google-api-dotnet-client


text:
Any rest API'S or node modules available for Google Forms

I am trying to search for rest API'S or node modules for google forms , but i am not getting any google api's  ,neither i am able to find any node module for Google Forms.Please let me know if you have any information on the above concern.
Thanks,
Varun

Currently you must use App Scripts. That's all I know of.

Ya i know about the App Scripts, but it will take long time to get used to it.So is there any API's or node modules for google form that would make my work easy and fast.

repo: google/google-api-nodejs-client


text:
Fix version for composer.

I tryed to install this library by this follows.
composer require google/apiclient:^2.0

But I am not able to do.
After that I recognized the version is already updated to 2.2.

I signed it!

@masayuki14 the command composer require google/apiclient:^2.0 will in fact install version 2.2, according to semantic versioning rules:
composer require google/apiclient:^2.0
./composer.json has been created
Loading composer repositories with package information
Updating dependencies (including require-dev)
Package operations: 12 installs, 0 updates, 0 removals
  - Installing psr/http-message (1.0.1): Loading from cache
  - Installing guzzlehttp/psr7 (1.4.2): Loading from cache
  - Installing guzzlehttp/promises (v1.3.1): Loading from cache
  - Installing guzzlehttp/guzzle (6.3.0): Loading from cache
  - Installing phpseclib/phpseclib (2.0.7): Loading from cache
  - Installing psr/log (1.0.2): Loading from cache
  - Installing monolog/monolog (1.23.0): Loading from cache
  - Installing firebase/php-jwt (v5.0.0): Loading from cache
  - Installing google/apiclient-services (v0.32): Loading from cache
  - Installing psr/cache (1.0.1): Loading from cache
  - Installing google/auth (v1.1.0): Loading from cache
  - Installing google/apiclient (v2.2.0): Loading from cache

Thanks for the mentoring.

repo: google/google-api-php-client


text:
Google::APIClient::BatchRequest, broken pipe when performing Google Analytics call

copy from: https://code.google.com/p/google-api-ruby-client/issues/detail?id=87
What steps will reproduce the problem?

Create Google::APIClient.new (and perform auth...)
Create Google::APIClient::BatchRequest.new
Add a new valid Google Analytics API call to batch request object (i've verified that mine work by using client.execute as usual)
Perform the batch request client.execute(batch)
client.execeute(batch) returns !! #<Errno::EPIPE: Broken pipe>

What is the expected output? What do you see instead?
Expected; Google::APIClient::Result
Result: !! #<Errno::EPIPE: Broken pipe>
What version of the product are you using? On what operating system?
google-api-client v 0.6.2 (ruby gem)  (Macintosh; Intel Mac OS X 10_8_3)
Please provide any additional information below.
I've verified that the call im trying to perform is valid and functional using client.execute without batch requests.
STACKTRACE:
Errno::EPIPE - Broken pipe:
/Users/buren/.rvm/rubies/ruby-2.0.0-p0/lib/ruby/2.0.0/openssl/buffering.rb:318:in do_write'   /Users/buren/.rvm/rubies/ruby-2.0.0-p0/lib/ruby/2.0.0/openssl/buffering.rb:336:in write'
/Users/buren/.rvm/rubies/ruby-2.0.0-p0/lib/ruby/2.0.0/net/http/generic_request.rb:202:in send_request_with_body_stream'   /Users/buren/.rvm/rubies/ruby-2.0.0-p0/lib/ruby/2.0.0/net/http/generic_request.rb:132:in exec'
/Users/buren/.rvm/rubies/ruby-2.0.0-p0/lib/ruby/2.0.0/net/http.rb:1403:in block in transport_request'   /Users/buren/.rvm/rubies/ruby-2.0.0-p0/lib/ruby/2.0.0/net/http.rb:1402:in transport_request'
/Users/buren/.rvm/rubies/ruby-2.0.0-p0/lib/ruby/2.0.0/net/http.rb:1375:in request'   /Users/buren/.rvm/rubies/ruby-2.0.0-p0/lib/ruby/2.0.0/net/http.rb:1368:in block in request'
/Users/buren/.rvm/rubies/ruby-2.0.0-p0/lib/ruby/2.0.0/net/http.rb:851:in start'   /Users/buren/.rvm/rubies/ruby-2.0.0-p0/lib/ruby/2.0.0/net/http.rb:1366:in request'
(gem) faraday-0.8.5/lib/faraday/adapter/net_http.rb:75:in perform_request'   (gem) faraday-0.8.5/lib/faraday/adapter/net_http.rb:38:in call'
(gem) faraday-0.8.5/lib/faraday/request/url_encoded.rb:14:in call'   (gem) google-api-client-0.6.2/lib/google/api_client/request.rb:159:in send'
(gem) google-api-client-0.6.2/lib/google/api_client.rb:563:in execute'   lib/google/tb_analytics.rb:81:in execute_request'
app/controllers/participants_controller.rb:360:in google_analytics_data'   (gem) actionpack-3.2.13/lib/action_controller/metal/implicit_render.rb:4:in send_action'
(gem) actionpack-3.2.13/lib/abstract_controller/base.rb:167:in process_action'   (gem) actionpack-3.2.13/lib/action_controller/metal/rendering.rb:10:in process_action'
(gem) actionpack-3.2.13/lib/abstract_controller/callbacks.rb:18:in block in process_action'   (gem) activesupport-3.2.13/lib/active_support/callbacks.rb:469:in _run__4205675944270840246__process_action__3704399789718745000__callbacks'
(gem) activesupport-3.2.13/lib/active_support/callbacks.rb:405:in __run_callback'   (gem) activesupport-3.2.13/lib/active_support/callbacks.rb:385:in _run_process_action_callbacks'
(gem) activesupport-3.2.13/lib/active_support/callbacks.rb:81:in run_callbacks'   (gem) actionpack-3.2.13/lib/abstract_controller/callbacks.rb:17:in process_action'
(gem) actionpack-3.2.13/lib/action_controller/metal/rescue.rb:29:in process_action'   (gem) actionpack-3.2.13/lib/action_controller/metal/instrumentation.rb:30:in block in process_action'
(gem) activesupport-3.2.13/lib/active_support/notifications.rb:123:in block in instrument'   (gem) activesupport-3.2.13/lib/active_support/notifications/instrumenter.rb:20:in instrument'
(gem) activesupport-3.2.13/lib/active_support/notifications.rb:123:in instrument'   (gem) actionpack-3.2.13/lib/action_controller/metal/instrumentation.rb:29:in process_action'
(gem) actionpack-3.2.13/lib/action_controller/metal/params_wrapper.rb:207:in process_action'   (gem) activerecord-3.2.13/lib/active_record/railties/controller_runtime.rb:18:in process_action'
(gem) actionpack-3.2.13/lib/abstract_controller/base.rb:121:in process'   (gem) actionpack-3.2.13/lib/abstract_controller/rendering.rb:45:in process'
(gem) actionpack-3.2.13/lib/action_controller/metal.rb:203:in dispatch'   (gem) actionpack-3.2.13/lib/action_controller/metal/rack_delegation.rb:14:in dispatch'
(gem) actionpack-3.2.13/lib/action_controller/metal.rb:246:in block in action'   (gem) actionpack-3.2.13/lib/action_dispatch/routing/route_set.rb:73:in dispatch'
(gem) actionpack-3.2.13/lib/action_dispatch/routing/route_set.rb:36:in call'   (gem) journey-1.0.4/lib/journey/router.rb:68:in block in call'
(gem) journey-1.0.4/lib/journey/router.rb:56:in call'   (gem) actionpack-3.2.13/lib/action_dispatch/routing/route_set.rb:612:in call'
(gem) bullet-4.3.0/lib/bullet/rack.rb:11:in call'   (gem) actionpack-3.2.13/lib/action_dispatch/middleware/best_standards_support.rb:17:in call'
(gem) rack-1.4.5/lib/rack/etag.rb:23:in call'   (gem) rack-1.4.5/lib/rack/conditionalget.rb:25:in call'
(gem) actionpack-3.2.13/lib/action_dispatch/middleware/head.rb:14:in call'   (gem) actionpack-3.2.13/lib/action_dispatch/middleware/params_parser.rb:21:in call'
(gem) actionpack-3.2.13/lib/action_dispatch/middleware/flash.rb:242:in call'   (gem) rack-1.4.5/lib/rack/session/abstract/id.rb:210:in context'
(gem) rack-1.4.5/lib/rack/session/abstract/id.rb:205:in call'   (gem) actionpack-3.2.13/lib/action_dispatch/middleware/cookies.rb:341:in call'
(gem) activerecord-3.2.13/lib/active_record/query_cache.rb:64:in call'   (gem) activerecord-3.2.13/lib/active_record/connection_adapters/abstract/connection_pool.rb:479:in call'
(gem) actionpack-3.2.13/lib/action_dispatch/middleware/callbacks.rb:28:in block in call'   (gem) activesupport-3.2.13/lib/active_support/callbacks.rb:405:in _run__1148351990235291595__call__1004835448436417272__callbacks'
(gem) activesupport-3.2.13/lib/active_support/callbacks.rb:405:in __run_callback'   (gem) activesupport-3.2.13/lib/active_support/callbacks.rb:385:in _run_call_callbacks'
(gem) activesupport-3.2.13/lib/active_support/callbacks.rb:81:in run_callbacks'   (gem) actionpack-3.2.13/lib/action_dispatch/middleware/callbacks.rb:27:in call'
(gem) actionpack-3.2.13/lib/action_dispatch/middleware/remote_ip.rb:31:in call'   (gem) better_errors-0.8.0/lib/better_errors/middleware.rb:84:in protected_app_call'
(gem) better_errors-0.8.0/lib/better_errors/middleware.rb:79:in better_errors_call'   (gem) better_errors-0.8.0/lib/better_errors/middleware.rb:56:in call'
(gem) actionpack-3.2.13/lib/action_dispatch/middleware/debug_exceptions.rb:16:in call'   (gem) actionpack-3.2.13/lib/action_dispatch/middleware/show_exceptions.rb:56:in call'
(gem) railties-3.2.13/lib/rails/rack/logger.rb:32:in call_app'   (gem) railties-3.2.13/lib/rails/rack/logger.rb:16:in block in call'
(gem) activesupport-3.2.13/lib/active_support/tagged_logging.rb:22:in tagged'   (gem) railties-3.2.13/lib/rails/rack/logger.rb:16:in call'
(gem) actionpack-3.2.13/lib/action_dispatch/middleware/request_id.rb:22:in call'   (gem) rack-1.4.5/lib/rack/methodoverride.rb:21:in call'
(gem) rack-1.4.5/lib/rack/runtime.rb:17:in call'   (gem) activesupport-3.2.13/lib/active_support/cache/strategy/local_cache.rb:72:in call'
(gem) actionpack-3.2.13/lib/action_dispatch/middleware/static.rb:63:in call'   (gem) railties-3.2.13/lib/rails/engine.rb:479:in call'
(gem) railties-3.2.13/lib/rails/application.rb:223:in call'   (gem) rack-1.4.5/lib/rack/content_length.rb:14:in call'
(gem) railties-3.2.13/lib/rails/rack/log_tailer.rb:17:in call'   (gem) thin-1.5.0/lib/thin/connection.rb:81:in block in pre_process'
(gem) thin-1.5.0/lib/thin/connection.rb:79:in pre_process'   (gem) thin-1.5.0/lib/thin/connection.rb:54:in process'
(gem) thin-1.5.0/lib/thin/connection.rb:39:in receive_data'   (gem) eventmachine-1.0.0/lib/eventmachine.rb:187:in run'
(gem) thin-1.5.0/lib/thin/backends/base.rb:63:in start'   (gem) thin-1.5.0/lib/thin/server.rb:159:in start'
(gem) rack-1.4.5/lib/rack/handler/thin.rb:13:in run'   (gem) rack-1.4.5/lib/rack/server.rb:268:in start'
(gem) railties-3.2.13/lib/rails/commands/server.rb:70:in start'   (gem) railties-3.2.13/lib/rails/commands.rb:55:in block in <top (required)>'
(gem) railties-3.2.13/lib/rails/commands.rb:50:in <top (required)>'   script/rails:6:in '

I've seen the broken pipe issue before on other calls, and in those cases, switching Faraday to use the httpclient as the adapter has fixed it. It's something I found here: http://stackoverflow.com/questions/24201842/uploading-a-video-to-youtube-using-youtube-data-api-broken-pipe-errnoepipe

authors: KenBackupify buren

repo: google/google-api-ruby-client


text:
how to move or create spreadsheet in my specified folder

Hi~all
I have create a new spreadsheet file by "sheet_v4 API" successfully, but it's default create the file in the root path "/", how could I create spreadsheet in my specified folder or create spreadsheet then move the spreadsheet file in my specified folder.
I try to write some code in the below

drive.update_file(file_id,add_parents: folder_id,fields: 'id, parents')

but it show the error in the below

parseError: This API does not support parsing form-encoded input.

Anyone know any solution? Thanks for your help.

Can work around that by giving it a request body that is a no-op update (e.g. set the name to it's existing name)

I have solve this problem. @sqrrrl Thanks for help^^

authors: kaogaau sqrrrl


text:
Go 1.9: exporter: variable/function exported but not defined: _

Hello, I've got this error when trying the hello world test. Go 1.9 on Gentoo, tomorrow I'll try with 1.8.
<autogenerated>:1:0: cannot use _ as value
<autogenerated>:1:0: internal compiler error: exporter: variable/function exported but not defined: _

goroutine 1 [running]:
runtime/debug.Stack(0x0, 0x0, 0x0)
        /usr/lib/go/src/runtime/debug/stack.go:24 +0xa7
cmd/compile/internal/gc.Fatalf(0xb701bc, 0x38, 0xc423833490, 0x1, 0x1)
        /usr/lib/go/src/cmd/compile/internal/gc/subr.go:181 +0x230
cmd/compile/internal/gc.(*exporter).obj(0xc423833628, 0xc420065860)
        /usr/lib/go/src/cmd/compile/internal/gc/bexport.go:491 +0x70d
cmd/compile/internal/gc.export(0xc42516dd40, 0x0, 0x0)
        /usr/lib/go/src/cmd/compile/internal/gc/bexport.go:347 +0x723
cmd/compile/internal/gc.dumpexport()
        /usr/lib/go/src/cmd/compile/internal/gc/export.go:253 +0x8a
cmd/compile/internal/gc.dumpobj1(0x7ffe2d6a05fa, 0x1e, 0x3)
        /usr/lib/go/src/cmd/compile/internal/gc/obj.go:95 +0xa5d
cmd/compile/internal/gc.dumpobj()
        /usr/lib/go/src/cmd/compile/internal/gc/obj.go:51 +0x61
cmd/compile/internal/gc.Main(0xb73f90)
        /usr/lib/go/src/cmd/compile/internal/gc/main.go:631 +0x2652
main.main()
        /usr/lib/go/src/cmd/compile/main.go:49 +0x95

make: *** [Makefile:216: build/pkg/linux_amd64/grumpy.a] Error 1```

Just tested with 1.8.3, no problems!

This issue appears to be caused by the const _ = declarations. Replacing the underscores with a dummy name allows the compiler to succeed. However, probably need verification from library authors that the previous behavior is still preserved. https://github.com/google/grumpy/pull/381

Damnit Jim! We need to define the...(!)
On Friday, September 22, 2017, Eddie Scholtz notifications@github.com
wrote:

This issue appears to be caused by the const _ = declarations. Replacing
the underscores with a dummy name allows the compiler to succeed. However,
probably need verification from library authors that the previous behavior
is still preserved. #381 https://github.com/google/grumpy/pull/381
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/google/grumpy/issues/378#issuecomment-331482521, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AX0Wxd4miGRUtFqHQH0qqjnFwyqWWXPhks5sk9SHgaJpZM4PFNo5
.

--
Thank you for choosing MagiTek choose you!

---------- Forwarded message ----------
From: "Andrew M. Hill" crossonrose@gmail.com
Date: Sep 26, 2017 8:40 PM
Subject:
To: crossonrose@hotmail.coml
Cc:
by Lugshar:
http://lugshar.bandcamp.com/album/simulacrum

Thank you for choosing MagiTek choose you!

authors: erpalma escholtz receptpr9001

repo: google/grumpy


text:
Completely remove OSGi Import-Package 'javax.annotation'

As suggested (and I assume also intended) in https://github.com/google/guice/pull/1173 this PR changes the configuration of the maven-bundle-plugin to completely remove the import of the package javax.annotation, which seems not to be required at runtime.
With PR https://github.com/google/guice/pull/1173 respectively https://github.com/google/guice/pull/1697 the OSGi package import of javax.annotation;version="[3.0,4)" was only changed to javax.annotation, i.e. the version range was removed.
@mcculls do you want to have a look at this?
Additionally update to latest maven-bundle-plugin 5.1.8.

Thank you @sameb for the quick review and merge.
Can you tell when the next release of guice that contains this change will approximately be done?

Sure thing!  Thanks for the PR!
My hope is to finish merging outstanding pull requests this week and do a cursory sweep over open issues, fixing anything reasonable.
The biggest barrier to a release is a resolution to #1383.  At this point, I think we mostly need a Maven expert who can advise on how to structure the POMs to allow pushing an artifact with different deps and bytecode, so we can do a final 6.0 release as-is, and then a 7.0 release using the jakarta namespace as deps (despite the code still referencing javax).  As soon as that's settled, I can cut a new release.

Thanks for the elaboration.
Looks like you already found a solution/plan. Looking forward to the new release!

authors: HannesWell sameb

repo: google/guice


text:
Moved Unit dependency to DM

Created a new branch as the previous one was a mess.

@sameb I made a mess of the previous PR. Let's follow this one. thanks.

original PR: https://github.com/google/guice/pull/981