🐛 Bug Report: Getting "Error: could not fetch catalog entities." error on browser

📜 Description
I've setup backstage on my linux server environement. I've installed all prerequisites like node, yarn and postgresql before setting up backstage. Was following this 'getting started' official doc from backstage. Here is my app-config.yaml file looks like:
app:
  title: Scaffolded Backstage App
  baseUrl: http://localhost:3000

organization:
  name: Clouddrove

backend:
  # Used for enabling authentication, secret is shared by all backend plugins
  # See https://backstage.io/docs/auth/service-to-service-auth for
  # information on the format
  # auth:
  #   keys:
  #     - secret: ${BACKEND_SECRET}
  baseUrl: http://localhost:7007
  listen:
    port: 7007
    # Uncomment the following host directive to bind to specific interfaces
    # host: <IP_ADDRESS>
  csp:
    connect-src: ["'self'", 'http:', 'https:']
    # Content-Security-Policy directives follow the Helmet format: https://helmetjs.github.io/#reference
    # Default Helmet Content-Security-Policy values can be removed by setting the key to false
  cors:
    origin: http://localhost:3000
    methods: [GET, HEAD, PATCH, POST, PUT, DELETE]
    credentials: true
  # This is for local development only, it is not recommended to use this in production
  # The production database configuration is stored in app-config.production.yaml
  database:
    client: pg
    connection:
      host: localhost
      port: 5432
      user: postgres
      password: postgres
  # workingDirectory: /tmp # Use this to configure a working directory for the scaffolder, defaults to the OS temp-dir

integrations:
  github:
    - host: github.com
      # This is a Personal Access Token or PAT from GitHub. You can find out how to generate this token, and more information
      # about setting up the GitHub integration here: https://backstage.io/docs/getting-started/configuration#setting-up-a-github-integration
      token: ${GITHUB_TOKEN}
    ### Example for how to add your GitHub Enterprise instance using the API:
    # - host: ghe.example.net
    #   apiBaseUrl: https://ghe.example.net/api/v3
    #   token: ${GHE_TOKEN}

proxy:
  ### Example for how to add a proxy endpoint for the frontend.
  ### A typical reason to do this is to handle HTTPS and CORS for internal services.
  # endpoints:
  #   '/test':
  #     target: 'https://example.com'
  #     changeOrigin: true

# Reference documentation http://backstage.io/docs/features/techdocs/configuration
# Note: After experimenting with basic setup, use CI/CD to generate docs
# and an external cloud storage when deploying TechDocs for production use-case.
# https://backstage.io/docs/features/techdocs/how-to-guides#how-to-migrate-from-techdocs-basic-to-recommended-deployment-approach
techdocs:
  builder: 'local' # Alternatives - 'external'
  generator:
    runIn: 'docker' # Alternatives - 'local'
  publisher:
    type: 'local' # Alternatives - 'googleGcs' or 'awsS3'. Read documentation for using alternatives.

auth:
  # see https://backstage.io/docs/auth/ to learn about auth providers
  environment: development
  providers: {}

scaffolder:
  # see https://backstage.io/docs/features/software-templates/configuration for software template options

catalog:
  import:
    entityFilename: catalog-info.yaml
    pullRequestBranchName: backstage-integration
  rules:
    - allow: [Component, System, API, Resource, Location]
  locations:
    # Local example data, file locations are relative to the backend process, typically `packages/backend`
    - type: file
      target: ../../examples/entities.yaml

    # Local example template
    - type: file
      target: ../../examples/template/template.yaml
      rules:
        - allow: [Template]

    # Local example organizational data
    - type: file
      target: ../../examples/org.yaml
      rules:
        - allow: [User, Group]

    ## Uncomment these lines to add more example data
    # - type: url
    #   target: https://github.com/backstage/backstage/blob/master/packages/catalog-model/examples/all.yaml

    ## Uncomment these lines to add an example org
    # - type: url
    #   target: https://github.com/backstage/backstage/blob/master/packages/catalog-model/examples/acme-corp.yaml
    #   rules:
    #     - allow: [User, Group]

Here is my complete log while running yarn dev command in root of backstage app dir:
yarn run v1.22.21
$ concurrently "yarn start" "yarn start-backend"
$ yarn workspace app start
$ yarn workspace backend start
$ backstage-cli package start
$ backstage-cli package start
[0] Loaded config from app-config.yaml
[0] fatal: not a git repository (or any of the parent directories): .git
[0] fatal: not a git repository (or any of the parent directories): .git
[0] NOTE: Did not compute git version or commit hash, could not execute the git command line utility
[0] <i> [webpack-dev-server] Project is running at:
[0] <i> [webpack-dev-server] Loopback: http://localhost:3000/, http://[::1]:3000/
[0] <i> [webpack-dev-server] Content not from webpack is served from '/root/backstage/backstage-demo/packages/app/public' directory
[0] <i> [webpack-dev-server] 404s will fallback to '/index.html'
[0] <i> [webpack-dev-middleware] wait until bundle finished: /
[1] Loaded config from app-config.yaml
[1] 2024-01-11T16:58:06.591Z backstage info Found 2 new secrets in config that will be redacted
[1] 2024-01-11T16:58:06.630Z backstage info Created UrlReader predicateMux{readers=azure{host=dev.azure.com,authed=false},bitbucketCloud{host=bitbucket.org,authed=false},github{host=github.com,authed=false},gitlab{host=gitlab.com,authed=false},awsS3{host=amazonaws.com,authed=false},fetch{}
[1] 2024-01-11T16:58:06.821Z catalog info Performing database migration type=plugin
[1] 2024-01-11T16:58:09.174Z auth info Configuring "database" as KeyStore provider type=plugin
[1] 2024-01-11T16:58:09.307Z techdocs info Creating Local publisher for TechDocs type=plugin
[1] 2024-01-11T16:58:09.360Z search info Added DefaultCatalogCollatorFactory collator factory for type software-catalog type=plugin
[1] 2024-01-11T16:58:09.361Z search info Added DefaultTechDocsCollatorFactory collator factory for type techdocs type=plugin
[1] 2024-01-11T16:58:09.374Z search info Starting all scheduled search tasks. type=plugin
[1] 2024-01-11T16:58:10.118Z backstage info Listening on :7007
[1] 2024-01-11T16:58:10.415Z backstage info Task worker starting: search_index_software_catalog, {"version":2,"cadence":"PT10M","initialDelayDuration":"PT3S","timeoutAfterDuration":"PT15M"} type=taskManager task=search_index_software_catalog
[1] 2024-01-11T16:58:10.418Z backstage info Task worker starting: search_index_techdocs, {"version":2,"cadence":"PT10M","initialDelayDuration":"PT3S","timeoutAfterDuration":"PT15M"} type=taskManager task=search_index_techdocs
[1] Connection Error: Connection ended unexpectedly
[1] Connection Error: Connection ended unexpectedly
[1] Connection Error: Connection ended unexpectedly
[1] Connection Error: Connection ended unexpectedly
[1] Connection Error: Connection ended unexpectedly
[1] Connection Error: Connection ended unexpectedly
[1] Connection Error: Connection ended unexpectedly
[1] Connection Error: Connection ended unexpectedly
[1] Connection Error: Connection ended unexpectedly
[1] Connection Error: Connection ended unexpectedly
[1] Connection Error: Connection ended unexpectedly
[1] Connection Error: Connection ended unexpectedly
[0] <i> [webpack-dev-middleware] wait until bundle finished: /ws
[0] ERROR in ../../node_modules/swagger-ui-react/node_modules/react-redux/dist/react-redux.mjs 1097:18-45
[0] export 'useSyncExternalStore' (imported as 'React2') was not found in 'react' (possible exports: Children, Component, Fragment, Profiler, PureComponent, StrictMode, Suspense, __SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED, cloneElement, createContext, createElement, createFactory, createRef, forwardRef, isValidElement, lazy, memo, useCallback, useContext, useDebugValue, useEffect, useImperativeHandle, useLayoutEffect, useMemo, useReducer, useRef, useState, version)
[0]
[0] webpack compiled with 1 error
[1] Connection Error: Connection ended unexpectedly
[1] Connection Error: Connection ended unexpectedly
[1] 2024-01-11T17:00:08.539Z search info Collating documents for techdocs via DefaultTechDocsCollatorFactory type=plugin documentType=techdocs
[1] 2024-01-11T17:00:08.558Z search info Collating documents for software-catalog via DefaultCatalogCollatorFactory type=plugin documentType=software-catalog
[1] 2024-01-11T17:00:08.629Z backstage info ::1 - - [11/Jan/2024:17:00:08 +0000] "GET /api/catalog/entities?limit=500&filter=metadata.annotations.backstage.io%2Ftechdocs-ref&offset=0 HTTP/1.1" 200 2 "-" "node-fetch/1.0 (+https://github.com/bitinn/node-fetch)" type=incomingRequest
[1] 2024-01-11T17:00:08.641Z search warn Index for techdocs was not created: indexer received 0 documents type=plugin documentType=techdocs
[1] 2024-01-11T17:00:08.643Z search info Collating documents for techdocs succeeded type=plugin documentType=techdocs
[1] 2024-01-11T17:00:08.650Z backstage info ::1 - - [11/Jan/2024:17:00:08 +0000] "GET /api/catalog/entities?limit=500&offset=0 HTTP/1.1" 200 - "-" "node-fetch/1.0 (+https://github.com/bitinn/node-fetch)" type=incomingRequest
[1] 2024-01-11T17:00:08.667Z search info Collating documents for software-catalog succeeded type=plugin documentType=software-catalog
[0] Killed
error Command failed with exit code 137.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
error Command failed.
[0] Exit code: 137
[0] Command: /usr/bin/node
[0] Arguments: /usr/local/lib/node_modules/yarn/lib/cli.js start
[0] Directory: /root/backstage/backstage-demo/packages/app
[0] Output:
[0]
info Visit https://yarnpkg.com/en/docs/cli/workspace for documentation about this command.
error Command failed with exit code 137.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
[0] yarn start exited with code 137
[1] Connection Error: Connection ended unexpectedly
[1] Connection Error: Connection ended unexpectedly
[1] Connection Error: Connection ended unexpectedly
[1] Connection Error: Connection ended unexpectedly
[1] 2024-01-11T17:01:48.827Z backstage info ::1 - - [11/Jan/2024:17:01:48 +0000] "GET / HTTP/1.1" 404 - "-" "curl/8.2.1" type=incomingRequest
[1] Connection Error: Connection ended unexpectedly
[1] Connection Error: Connection ended unexpectedly
[1] Connection Error: Connection ended unexpectedly
[1] Connection Error: Connection ended unexpectedly
[1] Connection Error: Connection ended unexpectedly
[1] Connection Error: Connection ended unexpectedly
[1] 2024-01-11T17:04:48.849Z backstage warn Task worker failed unexpectedly, attempt number 2, error: the database system is in recovery mode type=taskManager task=search_index_techdocs
[1] 2024-01-11T17:04:48.850Z backstage warn Task worker failed unexpectedly, attempt number 2, error: the database system is in recovery mode type=taskManager task=search_index_software_catalog
[1] 2024-01-11T17:04:48.875Z catalog warn Failed to load processing items the database system is in recovery mode type=plugin length=109 name=error severity=FATAL code=57P03 detail=undefined hint=undefined position=undefined internalPosition=undefined internalQuery=undefined where=undefined schema=undefined table=undefined column=undefined dataType=undefined constraint=undefined file=postmaster.c line=2361 routine=ProcessStartupPacket stack=error: the database system is in recovery mode
[1]     at Parser.parseErrorMessage (/root/backstage/backstage-demo/node_modules/pg-protocol/src/parser.ts:369:69)
[1]     at Parser.handlePacket (/root/backstage/backstage-demo/node_modules/pg-protocol/src/parser.ts:188:21)
[1]     at Parser.parse (/root/backstage/backstage-demo/node_modules/pg-protocol/src/parser.ts:103:30)
[1]     at Socket.<anonymous> (/root/backstage/backstage-demo/node_modules/pg-protocol/src/index.ts:7:48)
[1]     at Socket.emit (node:events:513:28)
[1]     at Socket.emit (node:domain:489:12)
[1]     at addChunk (node:internal/streams/readable:324:12)
[1]     at readableAddChunk (node:internal/streams/readable:297:9)
[1]     at Readable.push (node:internal/streams/readable:234:10)
[1]     at TCP.onStreamRead (node:internal/stream_base_commons:190:23)
[1] Connection Error: Connection ended unexpectedly
[1] Connection Error: Connection ended unexpectedly
[1] Connection Error: Connection ended unexpectedly
[1] Connection Error: Connection ended unexpectedly
[1] Connection Error: Connection ended unexpectedly
[1] Connection Error: Connection ended unexpectedly
[1] Connection Error: Connection ended unexpectedly
[1] Connection Error: Connection ended unexpectedly
[1] 2024-01-11T17:10:08.081Z search info Collating documents for techdocs via DefaultTechDocsCollatorFactory type=plugin documentType=techdocs
[1] 2024-01-11T17:10:08.087Z search info Collating documents for software-catalog via DefaultCatalogCollatorFactory type=plugin documentType=software-catalog
[1] 2024-01-11T17:10:08.107Z backstage info ::1 - - [11/Jan/2024:17:10:08 +0000] "GET /api/catalog/entities?limit=500&filter=metadata.annotations.backstage.io%2Ftechdocs-ref&offset=0 HTTP/1.1" 200 2 "-" "node-fetch/1.0 (+https://github.com/bitinn/node-fetch)" type=incomingRequest
[1] 2024-01-11T17:10:08.109Z backstage info ::1 - - [11/Jan/2024:17:10:08 +0000] "GET /api/catalog/entities?limit=500&offset=0 HTTP/1.1" 200 - "-" "node-fetch/1.0 (+https://github.com/bitinn/node-fetch)" type=incomingRequest
[1] 2024-01-11T17:10:08.111Z search warn Index for techdocs was not created: indexer received 0 documents type=plugin documentType=techdocs
[1] 2024-01-11T17:10:08.112Z search info Collating documents for techdocs succeeded type=plugin documentType=techdocs
[1] 2024-01-11T17:10:08.123Z search info Collating documents for software-catalog succeeded type=plugin documentType=software-catalog

👍 Expected behavior
I should get a browser responce like this

👎 Actual Behavior with Screenshots

👟 Reproduction steps
By running backstage app in dev env using this command: yarn dev
📃 Provide the context for the Bug.
I'm trying to setup backstage tool in my linux server.
🖥 Your Environment
yarn run v1.22.21
$ /root/backstage/backstage-demo/node_modules/.bin/backstage-cli info
OS:   Linux 6.5.0-14-generic - linux/x64
node: v18.13.0
yarn: 1.22.21
cli:  0.25.0 (installed)
backstage:  1.21.0

Dependencies:
  @backstage/app-defaults                                          1.4.6
  @backstage/backend-app-api                                       0.5.9
  @backstage/backend-common                                        0.20.0
  @backstage/backend-dev-utils                                     0.1.2
  @backstage/backend-openapi-utils                                 0.1.1
  @backstage/backend-plugin-api                                    0.6.8
  @backstage/backend-tasks                                         0.5.13
  @backstage/catalog-client                                        1.5.1
  @backstage/catalog-model                                         1.4.3
  @backstage/cli-common                                            0.1.13
  @backstage/cli-node                                              0.2.1
  @backstage/cli                                                   0.25.0
  @backstage/config-loader                                         1.6.0
  @backstage/config                                                1.1.1
  @backstage/core-app-api                                          1.11.2
  @backstage/core-compat-api                                       0.1.0
  @backstage/core-components                                       0.13.9
  @backstage/core-plugin-api                                       1.8.1
  @backstage/e2e-test-utils                                        0.1.0
  @backstage/errors                                                1.2.3
  @backstage/eslint-plugin                                         0.1.4
  @backstage/frontend-plugin-api                                   0.4.0
  @backstage/integration-aws-node                                  0.1.8
  @backstage/integration-react                                     1.1.22
  @backstage/integration                                           1.8.0
  @backstage/plugin-api-docs                                       0.10.2
  @backstage/plugin-app-backend                                    0.3.56
  @backstage/plugin-app-node                                       0.1.8
  @backstage/plugin-auth-backend-module-atlassian-provider         0.1.0
  @backstage/plugin-auth-backend-module-gcp-iap-provider           0.2.2
  @backstage/plugin-auth-backend-module-github-provider            0.1.5
  @backstage/plugin-auth-backend-module-gitlab-provider            0.1.5
  @backstage/plugin-auth-backend-module-google-provider            0.1.5
  @backstage/plugin-auth-backend-module-oauth2-provider            0.1.5
  @backstage/plugin-auth-backend-module-oauth2-proxy-provider      0.1.0
  @backstage/plugin-auth-backend-module-okta-provider              0.0.1
  @backstage/plugin-auth-backend                                   0.20.2
  @backstage/plugin-auth-node                                      0.4.2
  @backstage/plugin-catalog-backend-module-scaffolder-entity-model 0.1.5
  @backstage/plugin-catalog-backend                                1.16.0
  @backstage/plugin-catalog-common                                 1.0.19
  @backstage/plugin-catalog-graph                                  0.3.2
  @backstage/plugin-catalog-import                                 0.10.4
  @backstage/plugin-catalog-node                                   1.6.0
  @backstage/plugin-catalog-react                                  1.9.2
  @backstage/plugin-catalog                                        1.16.0
  @backstage/plugin-events-node                                    0.2.17
  @backstage/plugin-github-actions                                 0.6.9
  @backstage/plugin-org                                            0.6.18
  @backstage/plugin-permission-common                              0.7.11
  @backstage/plugin-permission-node                                0.7.19
  @backstage/plugin-permission-react                               0.4.18
  @backstage/plugin-proxy-backend                                  0.4.6
  @backstage/plugin-scaffolder-backend-module-azure                0.1.0
  @backstage/plugin-scaffolder-backend-module-bitbucket            0.1.0
  @backstage/plugin-scaffolder-backend-module-gerrit               0.1.0
  @backstage/plugin-scaffolder-backend-module-github               0.1.0
  @backstage/plugin-scaffolder-backend-module-gitlab               0.2.11
  @backstage/plugin-scaffolder-backend                             1.19.2
  @backstage/plugin-scaffolder-common                              1.4.4
  @backstage/plugin-scaffolder-node                                0.2.9
  @backstage/plugin-scaffolder-react                               1.7.0
  @backstage/plugin-scaffolder                                     1.17.0
  @backstage/plugin-search-backend-module-catalog                  0.1.12
  @backstage/plugin-search-backend-module-pg                       0.5.17
  @backstage/plugin-search-backend-module-techdocs                 0.1.12
  @backstage/plugin-search-backend-node                            1.2.12
  @backstage/plugin-search-backend                                 1.4.8
  @backstage/plugin-search-common                                  1.2.9
  @backstage/plugin-search-react                                   1.7.4
  @backstage/plugin-search                                         1.4.4
  @backstage/plugin-tech-radar                                     0.6.11
  @backstage/plugin-techdocs-backend                               1.9.1
  @backstage/plugin-techdocs-module-addons-contrib                 1.1.3
  @backstage/plugin-techdocs-node                                  1.11.0
  @backstage/plugin-techdocs-react                                 1.1.14
  @backstage/plugin-techdocs                                       1.9.2
  @backstage/plugin-user-settings                                  0.7.14
  @backstage/release-manifests                                     0.0.11
  @backstage/test-utils                                            1.4.6
  @backstage/theme                                                 0.5.0
  @backstage/types                                                 1.1.1
  @backstage/version-bridge                                        1.0.7
Done in 1.40s.

👀 Have you spent some time to check if this bug has been raised before?

[ ] I checked and didn't find similar issue

🏢 Have you read the Code of Conduct?

[X] I have read the Code of Conduct

Are you willing to submit PR?
Yes I am willing to submit a PR!

backend.baseUrl should be the address that the browser needs to make requests to, to reach the backend. It's often the address of a reverse proxy, an ingress web gateway, etc - depending on your deployment topology

@freben I'm only using my server where backstage is deployed. I've just created one server where I want to setup backstage. I've gone through getting started instruction, but not worked for me.

Do you get the page loading? What does the location bar of your browser say then?

Hi @freben ,
Yes, I get initial page loading that throwing error like this

While checking log it says listening to 7007 and resolving request fine:
yarn run v1.22.21
$ concurrently "yarn start" "yarn start-backend"
$ yarn workspace backend start
$ yarn workspace app start
$ backstage-cli package start
$ backstage-cli package start
[0] Loaded config from app-config.yaml
[0] fatal: not a git repository (or any of the parent directories): .git
[0] fatal: not a git repository (or any of the parent directories): .git
[0] NOTE: Did not compute git version or commit hash, could not execute the git command line utility
[0] <i> [webpack-dev-server] Project is running at:
[0] <i> [webpack-dev-server] Loopback: http://localhost:3000/, http://[::1]:3000/
[0] <i> [webpack-dev-server] Content not from webpack is served from '/root/backstage/backstage-demo1/packages/app/public' directory
[0] <i> [webpack-dev-server] 404s will fallback to '/index.html'
[1] Loaded config from app-config.yaml
[1] 2024-01-16T18:21:10.868Z backstage info Found 2 new secrets in config that will be redacted
[1] 2024-01-16T18:21:10.891Z backstage info Created UrlReader predicateMux{readers=azure{host=dev.azure.com,authed=false},bitbucketCloud{host=bitbucket.org,authed=false},github{host=github.com,authed=false},gitlab{host=gitlab.com,authed=false},awsS3{host=amazonaws.com,authed=false},fetch{}
[1] 2024-01-16T18:21:10.927Z catalog info Performing database migration type=plugin
[1] 2024-01-16T18:21:12.282Z auth info Configuring "database" as KeyStore provider type=plugin
[1] 2024-01-16T18:21:12.387Z techdocs info Creating Local publisher for TechDocs type=plugin
[1] 2024-01-16T18:21:12.395Z search info Added DefaultCatalogCollatorFactory collator factory for type software-catalog type=plugin
[1] 2024-01-16T18:21:12.403Z search info Added DefaultTechDocsCollatorFactory collator factory for type techdocs type=plugin
[1] 2024-01-16T18:21:12.405Z search info Starting all scheduled search tasks. type=plugin
[1] 2024-01-16T18:21:12.890Z backstage info Listening on :7007
[1] 2024-01-16T18:21:12.953Z backstage info Task worker starting: search_index_software_catalog, {"version":2,"cadence":"PT10M","initialDelayDuration":"PT3S","timeoutAfterDuration":"PT15M"} type=taskManager task=search_index_software_catalog
[1] 2024-01-16T18:21:12.955Z backstage info Task worker starting: search_index_techdocs, {"version":2,"cadence":"PT10M","initialDelayDuration":"PT3S","timeoutAfterDuration":"PT15M"} type=taskManager task=search_index_techdocs
[1] 2024-01-16T18:21:15.961Z search info Collating documents for software-catalog via DefaultCatalogCollatorFactory type=plugin documentType=software-catalog
[1] 2024-01-16T18:21:16.016Z search info Collating documents for techdocs via DefaultTechDocsCollatorFactory type=plugin documentType=techdocs
[1] 2024-01-16T18:21:16.199Z backstage info ::1 - - [16/Jan/2024:18:21:16 +0000] "GET /api/catalog/entities?limit=500&filter=metadata.annotations.backstage.io%2Ftechdocs-ref&offset=0 HTTP/1.1" 200 2 "-" "node-fetch/1.0 (+https://github.com/bitinn/node-fetch)" type=incomingRequest
[1] 2024-01-16T18:21:16.218Z search warn Index for techdocs was not created: indexer received 0 documents type=plugin documentType=techdocs
[1] 2024-01-16T18:21:16.220Z search info Collating documents for techdocs succeeded type=plugin documentType=techdocs
[1] 2024-01-16T18:21:16.227Z backstage info ::1 - - [16/Jan/2024:18:21:16 +0000] "GET /api/catalog/entities?limit=500&offset=0 HTTP/1.1" 200 - "-" "node-fetch/1.0 (+https://github.com/bitinn/node-fetch)" type=incomingRequest
[1] 2024-01-16T18:21:16.248Z search info Collating documents for software-catalog succeeded type=plugin documentType=software-catalog
[0] webpack compiled successfully
[1] 2024-01-16T18:24:08.270Z backstage info ::1 - - [16/Jan/2024:18:24:08 +0000] "GET / HTTP/1.1" 404 - "-" "curl/8.2.1" type=incomingRequest
[1] 2024-01-16T18:31:16.403Z search info Collating documents for techdocs via DefaultTechDocsCollatorFactory type=plugin documentType=techdocs
[1] 2024-01-16T18:31:16.426Z search info Collating documents for software-catalog via DefaultCatalogCollatorFactory type=plugin documentType=software-catalog
[1] 2024-01-16T18:31:16.453Z backstage info ::1 - - [16/Jan/2024:18:31:16 +0000] "GET /api/catalog/entities?limit=500&filter=metadata.annotations.backstage.io%2Ftechdocs-ref&offset=0 HTTP/1.1" 200 2 "-" "node-fetch/1.0 (+https://github.com/bitinn/node-fetch)" type=incomingRequest
[1] 2024-01-16T18:31:16.463Z search warn Index for techdocs was not created: indexer received 0 documents type=plugin documentType=techdocs
[1] 2024-01-16T18:31:16.465Z search info Collating documents for techdocs succeeded type=plugin documentType=techdocs
[1] 2024-01-16T18:31:16.474Z backstage info ::1 - - [16/Jan/2024:18:31:16 +0000] "GET /api/catalog/entities?limit=500&offset=0 HTTP/1.1" 200 - "-" "node-fetch/1.0 (+https://github.com/bitinn/node-fetch)" type=incomingRequest
[1] 2024-01-16T18:31:16.488Z search info Collating documents for software-catalog succeeded type=plugin documentType=software-catalog
[1] 2024-01-16T18:41:16.649Z search info Collating documents for techdocs via DefaultTechDocsCollatorFactory type=plugin documentType=techdocs
[1] 2024-01-16T18:41:16.657Z search info Collating documents for software-catalog via DefaultCatalogCollatorFactory type=plugin documentType=software-catalog
[1] 2024-01-16T18:41:16.668Z backstage info ::1 - - [16/Jan/2024:18:41:16 +0000] "GET /api/catalog/entities?limit=500&filter=metadata.annotations.backstage.io%2Ftechdocs-ref&offset=0 HTTP/1.1" 200 2 "-" "node-fetch/1.0 (+https://github.com/bitinn/node-fetch)" type=incomingRequest
[1] 2024-01-16T18:41:16.673Z search warn Index for techdocs was not created: indexer received 0 documents type=plugin documentType=techdocs
[1] 2024-01-16T18:41:16.674Z search info Collating documents for techdocs succeeded type=plugin documentType=techdocs
[1] 2024-01-16T18:41:16.677Z backstage info ::1 - - [16/Jan/2024:18:41:16 +0000] "GET /api/catalog/entities?limit=500&offset=0 HTTP/1.1" 200 - "-" "node-fetch/1.0 (+https://github.com/bitinn/node-fetch)" type=incomingRequest
[1] 2024-01-16T18:41:16.689Z search info Collating documents for software-catalog succeeded type=plugin documentType=software-catalog

I am getting a similar error following the getting started docs:
export 'useSyncExternalStore' (imported as 'React2') was not found in 'react' (possible exports: Children, Component, Fragment, Profiler, PureComponent, StrictMode, Suspense, __SECRET_INTERNALS_DO_NOT_USE_OR_YOU_WILL_BE_FIRED, cloneElement, createContext, createElement, createFactory, createRef, forwardRef, isValidElement, lazy, memo, useCallback, useContext, useDebugValue, useEffect, useImperativeHandle, useLayoutEffect, useMemo, useReducer, useRef, useState, version)
node_modules/swagger-ui-react/node_modules/react-redux/dist/react-redux.mjs

Looks like this is a duplicate of https://github.com/backstage/backstage/issues/22142 and https://github.com/swagger-api/swagger-ui/issues/9495

To fix this issue you can do this and run yarn install command. now the error should be gone.

The backstage getting started doc contains many bugs that still should be fixed. 😞

@nileshgadgi What I'm saying is that your browser will be trying to connect to http://localhost:7007. Is that really correct? Is that where Backstage is deployed, or is it on a different machine?

Failed to load processing items the database system is in recovery mode
What could that be? Could your local postgres be having problems somehow?


Doubt on training

Is a training on LLM done for OptiMUS or was gpt-4 equipped to give such outputs?
Is the dataset created used to evaluate the performance of LLM or used to train the LLM?
Can you give some insight into this?

Hi
It uses gpt-4 and no training/fine-tuning is done for this version. The dataset was used for evaluation, but could be used for training too.

So for all the steps that happen in the UI (OptiMUS website) is all by prompts to the gpt-4?

in the version that is currently up yes. We're working on tuning, and will share the results in our next paper.


Github Actions: Missing github Context Property (Documentation)

What article on docs.github.com is affected?
Context and expression syntax for GitHub Actions
What part(s) of the article would you like to see updated?
The "github context" table, which seems to be missing the github.repository.name property that is valid, but is not listed.

Researching how to gain a repositories name, without the owner / organisation within it, lead me to the github.repository.name property, through various Stack-overflow posts like the following. https://stackoverflow.com/questions/62803531/repository-name-as-a-github-action-environment-variable

Thanks so much for opening an issue @Sean12697! I'll triage this for the team to take a look 👀

# # # # # #7688

Thanks for opening this issue. A GitHub docs team member should be by to give feedback soon. In the meantime, please check out the contributing guidelines.

Ok
On Tue, Jun 29, 2021, 9:17 PM zaid1122 @.***> wrote:

Thanks for opening this issue. A GitHub docs team member should be by to
give feedback soon. In the meantime, please check out the contributing
guidelines https://github.com/github/docs/blob/main/CONTRIBUTING.md.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/github/docs/issues/7691#issuecomment-871025091, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AT5TPGQI3DSOSOKGBJYFADLTVJWCJANCNFSM47J6MUDQ
.

@Sean12697 Thanks for opening this issue! This context returns empty for me. Can you share an example workflow and workflow log where you use the github.repository.name context?


A bunch of bugs with specific syntax raising errors during dts generation (Though they don't fail the build 🤷♂ )

Describe the bug
The following trigger errors during dts generation:
1.
defineProps<{
    query: string | undefined;
}>()

Using v-bind in CSS.
Compiling a plain JS Vue SFC using script setup and defineProps

The errors:
vite v4.1.1 building for production...
✓ 11 modules transformed.
dist/style.css                        0.09 kB │ gzip:  0.10 kB
dist/vite-vue-typescript-starter.js  50.36 kB │ gzip: 16.25 kB │ map: 519.07 kB

[vite:dts] Start generate declaration files...
src/components/Foo.vue.js:12:40 - error TS8016: Type assertion expressions can only be used in TypeScript files.

12 const __returned__ = { props: props as any }
                                          ~~~
src/components/HelloWorld.vue.ts:7:5 - error TS2769: No overload matches this call.
  The last overload gave the following error.
    Type '{ type: (StringConstructor | null)[]; required: true; }' is not assignable to type 'Prop<unknown, unknown> | null'.
      Types of property 'type' are incompatible.
        Type '(StringConstructor | null)[]' is not assignable to type 'true | PropType<unknown> | null | undefined'.
          Type '(StringConstructor | null)[]' is not assignable to type 'PropConstructor<unknown>[]'.
            Type 'StringConstructor | null' is not assignable to type 'PropConstructor<unknown>'.
              Type 'null' is not assignable to type 'PropConstructor<unknown>'.

7     msg: { type: [String, null], required: true }
      ~~~

  node_modules/@vue/runtime-core/dist/runtime-core.d.ts:666:25
    666 export declare function defineComponent<PropsOptions extends Readonly<ComponentPropsOptions>, RawBindings, D, C extends ComputedOptions = {}, M extends MethodOptions = {}, Mixin extends ComponentOptionsMixin = ComponentOptionsMixin, Extends extends ComponentOptionsMixin = ComponentOptionsMixin, E extends EmitsOptions = {}, EE extends string = string, I extends ComponentInjectOptions = {}, II extends string = string>(options: ComponentOptionsWithObjectProps<PropsOptions, RawBindings, D, C, M, Mixin, Extends, E, EE, I, II>): DefineComponent<PropsOptions, RawBindings, D, C, M, Mixin, Extends, E, EE>;
                                ~~~~~~~~~~~~~~~
    The last overload is declared here.
src/components/HelloWorld.vue.ts:13:3 - error TS2322: Type 'number' is not assignable to type 'string'.

13   "1-FOO": (FOO)
     ~~~~~~~

[vite:dts] Declaration files built in 624ms.

Reproduction
https://stackblitz.com/edit/vitejs-vite-6b698p?file=src/components/HelloWorld.vue
Steps to reproduce

Run npm run build

System Info
System:
    OS: macOS 13.2
    CPU: (10) arm64 Apple M1 Pro
    Memory: 59.66 MB / 16.00 GB
    Shell: 5.8.1 - /bin/zsh
  Binaries:
    Node: 16.19.0 - ~/.nvm/versions/node/v16.19.0/bin/node
    npm: 9.4.1 - ~/.nvm/versions/node/v16.19.0/bin/npm
  npmPackages:
    @vitejs/plugin-vue: ^4.0.0 => 4.0.0
    vite: ^4.0.0 => 4.0.4
    vite-plugin-dts: 1.7.2 => 1.7.2

Validations

[X] Read the FAQ.
[X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
[X] The provided reproduction is a minimal reproducible example of the bug.

@qmhc Did you fix all the issues or only the CSS vars one? It might have auto closed this issue by accident.

@segevfiner Yes, the two others fixed in #173.


Readme for the test

Hi,
Thank you for sharing your great code. I want to run the test code of your model, However, I do not find the Readme file for the test.
Do you plan to release the Readme file for running the testing code?

Thank you for your question. For testing the code for video deblurring, it can be realized by setting
para.test_only = True

in main.py under MMP-RNN folder.
We will later upload the pretrained weights.

Thank you for your quick reply.
Another question is where should I put the dataset like GoPro?
Because I want to reproduce your GoPro results, what should I run for reproducing the results?
Could you give me the full instruction or do I just need to change the line para.test_only = True?
Thank you very much!

The gopro_lmdb folder should be under para.data_root (check parameter.py). Also, para.dataset in main.py should be gopro_lmdb. The lmdb version of gopro can be downloaded here.

Hello,
The checkpoints seem not correct,  I can not load the checkpoints from the download file 'model_best.pth.tar'.
Could you update the pre-trained weights? Thank you very much!

Hello, the download file 'model_best.pth.tar' is the pre-trained weight for MMP estimation network, the weight for the final MMP-RNN has not been uploaded yet.

Got it! Thank you for your quick reply. I am looking forward to testing the final MMP-RNN models.

Hello,
Thank you for your update on the GoPro results. Could you please also update the BSD results or the pre-trained weights?


[TASK] Fix keyboard navigation for connection window

Estimated story points: 3
Description

If you use tab navigation the connection window doesn't close any more

Acceptance criteria

time: 6h


Improving documentation (missing dependencies were not mentioned)

Dear @dr-mod,
thank you for publishing your program!
I really do like it as an example for using a Pi Zero W with a waveshare screen.
Unfortunately, I wasn't able to get your program to work following your documentation.
Hardware: Pi Zero W
OS: 2020-12-02-raspios-buster-armhf-lite
I'm always using the lite version of the OS since I don't need the graphical environment anyway.
I do think, that it would be beneficial for your program, to work properly on such minimal installs. It seemed, like you already had those packages installed. I decided, to improve the documentation by myself. I hope you like it.
I tested everything against multiple fresh installs of RaspiOS.
Problems that appeared:

APT packages being needed for waveshare library to work properly were missing: libopenjp2-7 libopenjp2-7 libatlas-base-dev
pip3 packages being needed for waveshare library to work properly were missing: image numpy
cd e-Paper-master/RaspberryPi_JetsonNano/python/ did not work: the repo is called e-Paper without the master

Other improvements:

removed redundant cd commands: we can clone repository's by adding a relative path into the command -> saving a few commands is especially useful when being executed in a script
we also can install packages via pip without using cd to go into the directory: pip3 install ~/e-Paper/RaspberryPi_JetsonNano/python/
we can do the same for executing the final python program
using pip3 install instead of pip3 install -e -> this way, the program still works in case we would remove the library's repository

You also could take a look at my commit messages, explaining what I'm doing.
I hope that my suggested changes for your documentation are wanted! In case you don't like something: tell me! I'm going to improve.
You could, if you really want to, add sudo apt-get install -y python3-pip git into your README. python3, git & pip aren't preinstalled on RaspiOS.
Thanks again for sharing your code!
Kind regards,
Niki from Germany

Hi Niki,
It's great that you found this script useful and went though with testing the installation process.
And of course, every bit of help or improvement is welcome, feel free to suggest things or add a pull request.
I've left a couple of comments that need to be taken care of with regards to your pull request.
Cheers,
Dmytro

Hi Niki,
It's great that you found this script useful and went though with testing the installation process.
And of course, every bit of help or improvement is welcome, feel free to suggest things or add a pull request.
I've left a couple of comments that need to be taken care of with regards to your pull request.
Cheers,
Dmytro

Hi @dr-mod,
thank you for taking yourself some time, reviewing my pull request!
I saw your comments. They were really helpful! I'm going to implement the suggested changes in the evening. You are 100% correct!
I have chosen a complicated way of solving dependency problems.
Have a nice day,
Niki

Hi @dr-mod,
thank you for taking yourself some time, reviewing my pull request!
I saw your comments. They were really helpful! I'm going to implement the suggested changes in the evening. You are 100% correct!
I have chosen a complicated way of solving dependency problems.
Have a nice day,
Niki

As discussed earlier, I've implemented the changes. I also did a test install on a fresh pi zero.

As discussed earlier, I've implemented the changes. I also did a test install on a fresh pi zero.

Hey Niki, I am going to merge the changes and fix that little typo. Thanks for the PR!

Hey Niki, I am going to merge the changes and fix that little typo. Thanks for the PR!


next_nth_usable filter requires python's netaddr be installed on the ansible controller

I'm getting this error during the "Configure NetworkManager for libvirt network" task.  I've installed python3_netaddr on the base server, but this still comes up.  Full -vvv output from the relevant section of the playbook:
TASK [Configure NetworkManager for libvirt network] ***************************************************************************************************************************************************************** task path: /images/libvirt-ocp4-provisioner-master/70_setup_sno_cluster.yml:80 <localhost> ESTABLISH LOCAL CONNECTION FOR USER: root <localhost> EXEC /bin/sh -c 'echo ~root && sleep 0' <localhost> EXEC /bin/sh -c '( umask 77 && mkdir -p " echo /root/.ansible/tmp "&& mkdir " echo /root/.ansible/tmp/ansible-tmp-1636499160.5299973-58778-194397503289046 " && echo ansible-tmp-1636499160.5299973-58778-194397503289046=" echo /root/.ansible/tmp/ansible-tmp-1636499160.5299973-58778-194397503289046 " ) && sleep 0' redirecting filter ansible.builtin.next_nth_usable to ansible.netcommon.next_nth_usable redirecting filter ansible.builtin.next_nth_usable to ansible.netcommon.next_nth_usable redirecting filter ansible.builtin.next_nth_usable to ansible.netcommon.next_nth_usable redirecting filter ansible.builtin.next_nth_usable to ansible.netcommon.next_nth_usable redirecting filter ansible.builtin.next_nth_usable to ansible.netcommon.next_nth_usable redirecting filter ansible.builtin.next_nth_usable to ansible.netcommon.next_nth_usable redirecting filter ansible.builtin.next_nth_usable to ansible.netcommon.next_nth_usable <localhost> EXEC /bin/sh -c 'rm -f -r /root/.ansible/tmp/ansible-tmp-1636499160.5299973-58778-194397503289046/ > /dev/null 2>&1 && sleep 0' The full traceback is: Traceback (most recent call last):   File "/usr/lib/python3.8/site-packages/ansible/plugins/action/template.py", line 146, in run     resultant = templar.do_template(template_data, preserve_trailing_newlines=True, escape_backslashes=False)   File "/usr/lib/python3.8/site-packages/ansible/template/__init__.py", line 1100, in do_template     res = j2_concat(rf)   File "<template>", line 16, in root   File "/usr/lib/python3.8/site-packages/ansible/template/__init__.py", line 265, in wrapper     ret = func(*args, **kwargs)   File "/root/.ansible/collections/ansible_collections/ansible/netcommon/plugins/filter/ipaddr.py", line 1125, in _need_netaddr     raise errors.AnsibleFilterError( ansible.errors.AnsibleFilterError: The next_nth_usable filter requires python's netaddr be installed on the ansible controller fatal: [localhost]: FAILED! => {     "changed": false,     "msg": "AnsibleFilterError: The next_nth_usable filter requires python's netaddr be installed on the ansible controller" }

Hey, thx for raising this up.
what OS are you using?

Sorry, forgot to say.  I'm running this on RHEL8.4

Can you please post the output for
ansible --version
I just tried to run it on my rhel84 and rhel85 and no error is happening, I was able to install it.

[root@lab1 openshift-baremetal-install]# ansible --version
ansible 2.9.27
config file = /etc/ansible/ansible.cfg
configured module search path = ['/root/.ansible/plugins/modules', '/usr/share/ansible/plugins/modules']
ansible python module location = /usr/lib/python3.6/site-packages/ansible
executable location = /usr/bin/ansible
python version = 3.6.8 (default, Mar 18 2021, 08:58:41) [GCC 8.4.1 20200928 (Red Hat 8.4.1-1)]

FYI: I have successfully gotten it all to work...rather I should say the TAM at RedHat I've been working with got it to work in his lab, and I ran his version.  There's something I want to suggest adding to his fork before he submits it back to you.

Please retry pulling new modifications on master!

This issue seems to have resurfaced with the latest version of RHEL 8.6 and ansible 2.12.2 (ansible-core-2.12.2-3.1.el8.x86_64)


CLI Feature Tracker

Docker build wrapper
Handler file checker, aserts that serverless.start is called.

Moved to internal project tracker


Multipile folder debugging

Environment data
VS Code version:  1.18.1
Python Extension version: 0.80.0
Python Version: 3.6
OS and version: Windows 10
Actual behavior
I opened a second folder in the workspace using File > Add Folder to Workspace
I managed to debug the second workspace (including creating lounch.jason etc.)
I changed the active folder using the button in the status line
I started debugging the second folder but:
Step into(F11) does not work (works like continue (F5))
Step over (F10) does not work (works like continue(F5))
I changed the project in the status line and in the second project the step into and step over works
(Not: the project that does not work properly is the first project)
Expected  behavior
The step into and step over should work in both projects
Steps to reproduce:

Logs
Output from Python output panel

Output from Console window (Help->Developer Tools menu)

Is there a by - pass to this problem so I can work in the mean time ?
I removed the second project but it still does not work.
Ilan

@DonJayamanne any ideas on what might be causing this?

@IlanHindy
Please confirm this are the steps used to reproduce the steps:

Open folder A in VS COde
I managed to debug this first workspace (including creating launch.json etc.)
Open a second folder "B" in the workspace using File > Add Folder to Workspace
I managed to debug the second workspace B (including creating launch.json etc.)
I changed the active folder to B using the button in the status line
I started debugging the second folder B but:
Step into(F11) does not work (works like continue (F5))
Step over (F10) does not work (works like continue(F5))
I changed the project in the status line back to A and in the second project the step into and step over works

Not Exactly

Open folder A in VS COde
I managed to debug this first project "A" (including creating launch.json etc.)
Open a second folder "B" in the workspace using File > Add Folder to Workspace
I managed to debug the second workspace B (including creating launch.json etc.)
5. I changed the active folder to A using the button in the status line
6. I started debugging the first folder A but:
Step into(F11) does not work (works like continue (F5))
Step over (F10) does not work (works like continue(F5))
9. I changed the project in the status line back to B and in the second project the step into and step over works

Summary:
The first folder ("A") does not work properly
The second project ("B") works properly
Additional information
I started a fresh workspace (with only code files) that include only project ("A") and the problem persists
Ilan

I started a fresh workspace (with only code files) that include only project ("A") and the problem persists
Ilan

Ok, this means debugging just doesn't work for folder A, and this had nothing to do with multiple workspace. Please confirm.
Please could you upload the code used in folder A.

The problem started when I started the second folder
The starting file to activate the program is ArtificialIntelligence_\ArtificialInteligence\main.py
ArtificialIntelligence_.zip

I found what caused the problem
The program starts from a file main.py
import Project.ArtificialIntelligence
This command caused the debugger not to work properly.
When I replaced it with a command of the sort:
from ... import
It worked OK
Ilan

I'm closing the issue as you have managed to fix it.
Thanks for getting back.


DATAJDBC-256 - Run integration tests with Oracle.

Started to work on the above issue. Please note that there is a huge obstacle (for my at least) to continue work:

https://blogs.oracle.com/oraclemagazine/deliver-oracle-database-18c-express-edition-in-containers there is stated that one needs some binary files from oracle
this requires an oracle account
i don´t know if there are any legal problems or how to deal with these binaries when downloaded

Regardless of the database edition and version, you must first obtain a copy of the software binaries through Oracle’s technical resources web page.

This PR was incorporated and replaced by #232


examples of Bundeled scripts

I can not get most of the bundled scripts to work. Even some who have instructions like "FollowCamera" don't work. Please help, would be specially interested in "FirstPersonController".

The FirstPersonController trait is used in first person template, but it has no exposed props yet so it's not very usable without modifying the script directly I guess..
 And I need to clean them up and expose props for configuring them from Blender.

Will move this issue to the repository at https://github.com/armory3d/armory_examples, marking this one as deprecated and intended for b27 usage.


Add version: Baidu.SwanIDE version 3.60.1

[X] Have you signed the Contributor License Agreement?
[X] Have you checked that there aren't other open pull requests for the same manifest update/change?

[ ] Have you tested your manifest locally with winget install --manifest <path>?
[X] Does your manifest conform to the 1.4 schema?

/azp run

/azp run

/azp run


Fix code scanning alert - Pinned-Dependencies package.yaml

Tracking issue for:

[ ] https://github.com/rtsoft-gmbh/up2date-win/security/code-scanning/18

Duplicate Of #144


ci: add directory of cookie to renovate ignorePaths

Closes #70
should work as https://github.com/JonasPammer/cookiecutter-pypackage/pull/100 also worked

pre-commit passed, lgtm


Make it easy for multiple tables

I add database package to make it usable for multiple tables.

Hi Mohammad, thanks for the PR! I'm not sure this is necessary, as I want this repository to remain as simple as possible. I'm sure this worked well for your use case, but I don't think I want to change this right now.


replace algo name by task name in plots

will solve #243

Codecov Report

Merging #246 (29fed7d) into master (403f591) will not change coverage.
The diff coverage is 100.00%.

:exclamation: Current head 29fed7d differs from pull request most recent head 3593f13. Consider uploading reports for the commit 3593f13 to get more accurate results

@@           Coverage Diff           @@
##           master     #246   +/-   ##
=======================================
  Coverage   95.26%   95.26%
=======================================
  Files         127      127
  Lines        4326     4326
=======================================
  Hits         4121     4121
  Misses        205      205

Flag
Coverage Δ

unittests
95.26% <100.00%> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

domainlab/utils/generate_benchmark_plots.py
92.55% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Writing of PNG images.

This writes both raw pixels and compressed jpeg as png in the same output directory as the csvs using the pattern nanoseconds.png.

Fixes so the RID/SID of continuation and stop packages are discarded in the aggregator
Uses the PacketLength in the innosat reader.

In general nice and clean. I have some minor suggestions...


GraphQL Error Unknown field allMarkdownRemark on type Query

I have created a new project, fresh from the repository without any changes and when I try to run it I get the error:
GraphQL Error Unknown field `allMarkdownRemark` on type `Query`

  file: /Users/kobit/tigase-net-gastby/src/pages/index.js

   1 |
   2 |   query {
>  3 |     allMarkdownRemark(
     |     ^
   4 |       filter: { fileAbsolutePath: { regex: "/services/" } }
   5 |       sort: { fields: [frontmatter___date], order: DESC }
   6 |     ) {
   7 |       edges {
   8 |         node {
   9 |           id
  10 |           frontmatter {
  11 |             path
  12 |             title
  13 |             date(formatString: "DD MMMM YYYY")

Do you have any suggestions?

There is one more error in the console output that I missed. Maybe these both errors are related? Here is a full console output:
 $ gatsby develop
success open and validate gatsby-configs — 0.008 s
error
Your plugins must export known APIs from their gatsby-node.js.
The following exports aren't APIs. Perhaps you made a typo or your plugin is outdated?

See https://www.gatsbyjs.org/docs/node-apis/ for the list of Gatsby Node APIs

- The plugin<EMAIL_ADDRESS>is exporting a variable named "createSchemaCustomization" which isn't an API.

- The plugin<EMAIL_ADDRESS>is exporting a variable named "createSchemaCustomization" which isn't an API.

- The plugin<EMAIL_ADDRESS>is exporting a variable named "createSchemaCustomization" which isn't an API.
success load plugins — 0.281 s
success onPreInit — 0.200 s
success delete html and css files from previous builds — 0.013 s
success initialize cache — 0.008 s
success copy gatsby files — 0.057 s
success onPreBootstrap — 0.007 s
success source and transform nodes — 0.095 s
success building schema — 0.207 s
error gatsby-node.js returned an error

  TypeError: Cannot read property 'services' of undefined

success createPages — 0.045 s
success createPagesStatefully — 0.048 s
success onPreExtractQueries — 0.001 s
success update schema — 0.100 s
error GraphQL Error Unknown field `allMarkdownRemark` on type `Query`

  file: /Users/kobit/Dropbox (Tigase)/projects/tigase/tigase-net-gastby/src/pages/index.js

   1 |
   2 |   query {
>  3 |     allMarkdownRemark(
     |     ^
   4 |       filter: { fileAbsolutePath: { regex: "/services/" } }
   5 |       sort: { fields: [frontmatter___date], order: DESC }
   6 |     ) {
   7 |       edges {
   8 |         node {
   9 |           id
  10 |           frontmatter {
  11 |             path
  12 |             title
  13 |             date(formatString: "DD MMMM YYYY")

(node:7797) DeprecationWarning: Passing lineNumber and colNumber is deprecated to @babel/code-frame. Please use

success run graphql queries — 0.022 s — 8/8 468.66 queries/second
success write out page data — 0.006 s
success write out redirect data — 0.004 s
success onPostBootstrap — 0.001 s

info bootstrap finished - 3.943 s
 DONE  Compiled successfully in 2559ms                                                                              8:12:55 PM

You can now view gatsby-serif-theme in the browser.

  http://localhost:8000/

View GraphiQL, an in-browser IDE, to explore your site's data and schema

  http://localhost:8000/___graphql

Note that the development build is not optimized.
To create a production build, use gatsby build

ℹ ｢wdm｣:
ℹ ｢wdm｣: Compiled successfully.
 WAIT  Compiling...                                                                                8:12:55 PM

ℹ ｢wdm｣: Compiling...
 DONE  Compiled successfully in 35ms                                                                                8:12:55 PM

ℹ ｢wdm｣:
ℹ ｢wdm｣: Compiled successfully.

I have the same problem. Did you find the solution?

No solution for this unfortunately. Ended up, implementing own theme from scratch.


Adding the ability to specify replacements from the command line.

There are cases where the values to be replaced are known, and so the user doesn't need to be asked.
I've added a step where it looks for command line arguments that are named the same thing as the variables. If any cannot be satisfied, then the user is asked to provide values.
For example:
meta template apply templates/test-template --VAR1=12345 --FULL_NAME="Allain Lalonde"

hey - no issue with this change, however, in order to trigger the release process properly, you need to commit using a certain format. There is a wizard to lead you through this process. Instead of running git commit, run npm run commit
A combination of commitizen and semantic-release will update the release notes on github, and publish the new version to npm


View/download Riak logs for each node

Add ability to view/download relevant logs for each node. (Error log, crash log, console log, etc).
Link to this from the Node Detail page (#96)

Comment for Jira.


User file upload dropdown list design

Users should be allowed to choose uploaded files inside the file upload operator. The dropdown window should be added to allow users to select files in a pop-up window instead of just entering a path.

required change of environment variables in the environment.default.ts:

sourceTableEnabled: true
userSystemEnabled: true

why is this not closed automatically?

closed by #867


Not Found: ./dist/render_conf.json

This issue is reporting a bug in the code of Perseus. Details of the scope will be available in issue labels.
The author described their issue as follows:

$~/Rustjr/myblog$ perseus snoop serve
Compiling myblog v0.1.0 ~/Rustjr/myblog)
Compiling perseus-engine v0.3.5 (/home/base/Rustjr/myblog/.perseus)
Compiling perseus-engine-server v0.3.5 (/home/base/Rustjr/myblog/.perseus/server)
Finished dev [unoptimized + debuginfo] target(s) in 54.63s
Running target/debug/perseus-engine-server
thread 'main' panicked at 'Couldn't get render configuration!: StoreError(ReadFailed { name: "./dist/render_conf.json", source: Os { code: 2, kind: NotFound, message: "No such file or directory" } })', /home/base/.cargo/registry/src/github.com-1ecc6299db9ec823/perseus-0.3.5/src/init.rs:360:18
note: run with RUST_BACKTRACE=1 environment variable to display a backtrace

The steps to reproduce this issue are as follows:

perseus snoop serve

A minimum reproducible example is available at <>.

Hydration-related: false
The author is willing to attempt a fix: false

Tribble internal data
dHJpYmJsZS1yZXBvcnRlZCxDLWJ1ZyxBLWNsaQ==

The problem happens when called perseus serve with the snoop argument. otherwise normal serve works correctly

Does this persist after perseus clean?

Ah, yes you do! perseus snoop serve must be preceded by perseus build if you haven't already run it.

Ok, Thanks,


Contextual Configuration File Loading (rework)

Description
This PR is a re-work of the following PR. The predominant  reason for iterating on the previous solution was to solve 2 main issues:

To avoid using webpack magic aka externals to dictate which bundles have the cosmiconfig library included.
Come up with an API that can be implemented in the upcoming version 2.

Summary
The problem with the previous solution was that to used a single isomorphic function using a combination of webpack externals and evaluated require statements to prevent cosmiconfig from being bundled in client code and ensuring it's available for server code.
Because V2 does not use externals, this solution wouldn't be easily implemented. Resulting in this solution where cosmiconfig is only used on the server via the express app is made available to the rest of the application in a module context that can be accessed in both server and browser contexts.
Testing
A deployed version of this code can be seen here. In this deployment the javascript configuration is requiring 'site.json' information and exposing it at __CONFIG__.app.sites. This isn't in this PR and was only used as a POC that you can use JS configuration files to their fullest.

I want to open a discussion around the following topic --> Asynchronous Configuration Loading
Why did this topic come up?
The question about async configuration loading most recently came up as feedback from a partner developer, although its been mentioned in the past on how we'd keep the sites in our configuration in sync with those in the back-end (business manager), the  feedback we received was more targeted at how we have a single point of truth for configuration, and how to prevent the need to re-deploy our code when configuration changes. Examples of these changes would be any kinds of changes to site, locale and currency.
Why would be want such a thing?
The answer on why we think it's valuable to have this support for async configuration loading is to solve the problem mentioned above. So we don't have to redeploy code to see effects that have happen on the backend (business manager).
**What risks might this impose? **
In the real world when we talk about async configuration loading we are talking about making a fetch request to the back end in order to get the latest site, locale, currency settings before accepting requests via the dev server or lambda function. This means that there will be potentially a small price to pay to get that information from the remote server before the server is ready to accept connections, but this will only happen once during "cold boots". So in my eyes it's not a a huge issue.
What can we do about this?
I'm not super familiar with this part of the SDK, but at the core of our app we export a get function, I'm not sure this can change, but what might be able to change is the support a new overloaded mobify option. Right now it's an object, maybe we can support async function that returns a config object and make all the change upwards to support that. I'm a little less informed how this might work for the lambda start up, but I can see how it might work for the dev server.
Are there any alternatives?
Possibly. If there was a way to store configurations in MRT we could potentially use MRT as a source of the configuration, meaning no need to re-deploy, but we'd still have to solve not having a single source of truth. This solution would use kinda of a copy of the configuration.
What effects does it have on this PR?
The main purpose of this PR is to have different configurations for different environments, but if you look closely at what is in that configuration there isn't much that really benefits from this functionality besides different site/locale/currency settings (e.g. proxy information is only useful for dev servers, remotes use what it in MRT anyway). Furthermore if we where to get site information adhoc from BM there is really no reason to have any configuration differences between one production environment and another as connections to remote servers/apis are directed by the proxies for that environment.

I want to open a discussion around the following topic --> Asynchronous Configuration Loading
Why did this topic come up?
The question about async configuration loading most recently came up as feedback from a partner developer, although its been mentioned in the past on how we'd keep the sites in our configuration in sync with those in the back-end (business manager), the feedback we received was more targeted at how we have a single point of truth for configuration, and how to prevent the need to re-deploy our code when configuration changes. Examples of these changes would be any kinds of changes to site, locale and currency.
Why would be want such a thing?
The answer on why we think it's valuable to have this support for async configuration loading is to solve the problem mentioned above. So we don't have to redeploy code to see effects that have happen on the backend (business manager).
**What risks might this impose? **
In the real world when we talk about async configuration loading we are talking about making a fetch request to the back end in order to get the latest site, locale, currency settings before accepting requests via the dev server or lambda function. This means that there will be potentially a small price to pay to get that information from the remote server before the server is ready to accept connections, but this will only happen once during "cold boots". So in my eyes it's not a a huge issue.
What can we do about this?
I'm not super familiar with this part of the SDK, but at the core of our app we export a get function, I'm not sure this can change, but what might be able to change is the support a new overloaded mobify option. Right now it's an object, maybe we can support async function that returns a config object and make all the change upwards to support that. I'm a little less informed how this might work for the lambda start up, but I can see how it might work for the dev server.
Are there any alternatives?
Possibly. If there was a way to store configurations in MRT we could potentially use MRT as a source of the configuration, meaning no need to re-deploy, but we'd still have to solve not having a single source of truth. This solution would use kinda of a copy of the configuration.
What effects does it have on this PR?
The main purpose of this PR is to have different configurations for different environments, but if you look closely at what is in that configuration there isn't much that really benefits from this functionality besides different site/locale/currency settings (e.g. proxy information is only useful for dev servers, remotes use what it in MRT anyway). Furthermore if we where to get site information adhoc from BM there is really no reason to have any configuration differences between one production environment and another as connections to remote servers/apis are directed by the proxies for that environment.

Documentation on this conversation has been moved here --> https://salesforce.quip.com/6JykAlnb2rCK

Found and commented on a few bits of what I assume are debugging code. Overall, looks great.  To verify for 100% certain, for instance, that cosmiconfig doesn't get bundled for the client? Would be good to see that!

setConfig(options.mobify)

Good call. Looking at the output of analyzing the build the sum of the front end bundle are as follow:
packages/pwa % npm run analyze-build

Before (origin/develop): 448.93 KB
After: (origin/sdk-config) 449.13 KB
The small increase is probably the result the changes (additions of getters/setters) and their usage. So nothing surprising there. Also there is no occurrences of cosmiconfig when searching those reports.


Fix: Decode Webpage Id to fix 404 on Webpages with nonsafe ids

What/Why?
Pages with non url safe ids causes to 404 response.
Page Data and PageMetadata request sends the urlencoded id strings. this cause no response. I checked the  Contact page but it already been fix
Example id: Tm9ybWFsUGFnZToxMA== and graphgl has the variable {id:"Tm9ybWFsUGFnZToxMA%3D%3D"}

Testing
Go to a page with nonurlsafe id

Thanks for your contribution!


Is it possible to replace Google Maps with another Map Engine?

Due to GFW it's hard to access google services in the  mainland of china, so if provide an extra options to replace Google Map with other Engine? For example:
  <MapView
    provider="Google"   // Some others map engine ....
    initialRegion={{
      latitude: 37.78825,
      longitude: -122.4324,
      latitudeDelta: 0.0922,
      longitudeDelta: 0.0421,
    }}
  />

While technically feasible it would be a substantial effort to provide alternate provider such as mapbox for example.

I would suggest you look into mapbox as a complete alternative

One possible solution would be have this library use AirMapView under the hood, since it provides options for google web maps and mapbox and the external api is similar to the google one

It will be nice to have MapBox as a provider.

Similar to #773

Any provider would be great as long as it works. Maybe if there was a way to switch the base map provider would satisfy the ones who wish to keep Google and the ones who prefer other solutions.

I get started the project to use OpenStreetMaps or GoogleMaps to Android.  https://github.com/enieber/react-native-open-street-map

See #2348

@rborn The reason why #2348 has been closed are clear.
But why is this issue closed?

I just cleanup the repo for very old issues and yours was a victim of this.
If you think is important please open a new one following the new template.
Thanks and sorry for any annoyance 😻


feat: Add some conversion methods to AccountIdentifier in ic-ledger-types

Description
Add some conversion methods to AccountIdentifier for better conversion between types
Fixes # (issue)
How Has This Been Tested?
Code from the already tested ic repository
Checklist:

[x] The title of this PR complies with Conventional Commits.
[x] I have edited the CHANGELOG accordingly.
[x] I have made corresponding changes to the documentation.

If we're copying some code, it would be great to copy the test suite for it as well :)

Good idea

If we're copying some code, it would be great to copy the test suite for it as well :)


s

Version 4.4.0 breaks expectation to be able to include <iframe> declarations anywhere in a markdown document. This should be a task for a sanitizer such as https://github.com/bevacqua/insane, not the markdown parser

http://spec.commonmark.org/
Are you vamiliar with 0.21 spec changes? Is this report related to this pachage or to spec?

That's gibberish to me, I can't make sense of the spec, I just see that it doesn't reference <iframe> elements anymore. Markdown historically allowed to mix-in HTML. Removing support for that seems like a major change (and even with a major version change I would be strongly against it)

@bevacqua , both this project and reference implementation have demos, allowing to create examples.

https://markdown-it.github.io/
http://spec.commonmark.org/dingus/

Please, create examples what is wrong and give links to those.

example
I see no problem with iframe, except the fact it's been wrapped with paragraph.

If I upgrade to 4.4.0 in this library the <iframe> test fails

I can't test your library. If you need help here - please, prepare examples.

Nevermind, it was an issue in my end (didn't realize that it got wrapped in a paragraph now.)

Wrapping to paragraph seems to be a bug.
Reported here https://github.com/jgm/CommonMark/issues/352

Yeah I agree, I was just content to be able to upgrade to @latest with tests passing


ValueError: Expected 2D array, got 1D array instead

Using continuous variables. Took a simple input matrix X and target variable y. It seems to run in a problem using sklearn's preprocessing even though the matrix dimensions are correctly set:
  File "run.py", line 29, in <module>
    feat_selector.fit(X, y)
  File "/home/charles/corex/lib/python2.7/site-packages/mifs-0.0.1.dev0-py2.7.egg/mifs/mifs.py", line 149, in fit
    return self._fit(X, y)
  File "/home/charles/corex/lib/python2.7/site-packages/mifs-0.0.1.dev0-py2.7.egg/mifs/mifs.py", line 193, in _fit
    self.X, y = self._check_params(X, y)
  File "/home/charles/corex/lib/python2.7/site-packages/mifs-0.0.1.dev0-py2.7.egg/mifs/mifs.py", line 296, in _check_params
    y = ss.fit_transform(y)
  File "/home/charles/corex/lib/python2.7/site-packages/sklearn/base.py", line 518, in fit_transform
    return self.fit(X, **fit_params).transform(X)
  File "/home/charles/corex/lib/python2.7/site-packages/sklearn/preprocessing/data.py", line 590, in fit
    return self.partial_fit(X, y)
  File "/home/charles/corex/lib/python2.7/site-packages/sklearn/preprocessing/data.py", line 612, in partial_fit
    warn_on_dtype=True, estimator=self, dtype=FLOAT_DTYPES)
  File "/home/charles/corex/lib/python2.7/site-packages/sklearn/utils/validation.py", line 410, in check_array
    "if it contains a single sample.".format(array))
ValueError: Expected 2D array, got 1D array instead:
array=[ 1.  1.  1. ...,  0.  0.  0.].
Reshape your data either using array.reshape(-1, 1) if your data has a single feature or array.reshape(1, -1) if it contains a single sample.```

Can you please try the latest version of the code and report back if you still encounter the bug? Thanks!


Fix nukies not getting station codes

About the PR

This "fixes" #31216 but needs to be mapped onto the nukies shuttle (I have no idea how to do this so someone else needs to!). The issue is that the paper is spawned in before the station nuke is spawned leading to the only available nuke being the nukies one. Now, the paper is inside a folder which means that when its opened both nukes should be loaded.
Whoever makes the mapping change should explain that the bug is fixed in their CL. In this PR the bug still exists because the paper isn't replaced yet!
Media

https://github.com/user-attachments/assets/72b54747-2413-4eb1-b4e1-4cdc60b06a82
Breaking changes

Changelog

:cl: Beck Thompson

add: Nuclear authentication code folder that spawns the nuclear authentication codes when opened.

Oh also if anyone has better sprites for the folder I'm all ears! I really had trouble with it...


Support remote storage in modelcardgenerator

Fixes #261
I updated the MCT generator to create a temp dir for all cases since I don't think that's a big operation.

[x] Tests pass
[ ] Appropriate changes to README are included in PR

Hi @rcrowe-google or @casassg, would you please take a look at this PR since Hannes is currently unavailable. 🙏

Thank you, Robert! My apologies; I think I blanked and forgot about the bot. I'll be more mindful about this next time. 😅

btw just a heads up. The bot adds and removes labels in the PR as needed. if it has lgtm, then only is missing / merge command

/merge


Building React Native 0.73.1 causes Android app to crash with ProGuard enabled

Describe the bug
I recently upgraded my React Native app to 0.73.1. I have always built with ProGuard enabled for release versions without issues, but since upgrading to 0.73.1 from 0.72.7, I now get a crash:
Nothing has changed with my config; I simply followed the React Native upgrade helper. Disabling ProGuard fixes the crashes, although I'd like to get this resolved so that I can re-enable it, as my app download size has gone up almost 40% with ProGuard disabled.
Steps to reproduce
No idea if there's a simple repro for this. I don't actually have an Android device to test on, so I found out about the crash from one of my testers, and from the Bugsnag report. I guess this means it's still reporting to Bugsnag in some cases, so I'm not sure exactly what's broken...
Environment

Bugsnag version: 7.22.2
React Native 0.73.1
Device: Pixel 6 Pro, Android 12

Error messages:
com.facebook.react.common.JavascriptException: Error: No Bugsnag API Key set, js engine: hermes, stack:
_configure@1:684887
Client@1:684148
_createClient@1:661352
createClient@1:661182
start@1:661944
anonymous@1:82247
loadModuleImplementation@1:75876
guardedLoadModule@1:75375
metroRequire@1:75040
global@1:74592

        at com.facebook.react.modules.core.ExceptionsManagerModule.reportException(SourceFile:76)
        at java.lang.reflect.Method.invoke(Method.java:-2)
        at com.facebook.react.bridge.JavaMethodWrapper.invoke(SourceFile:147)
        at com.facebook.react.bridge.JavaModuleWrapper.invoke(SourceFile:22)
        at com.facebook.jni.NativeRunnable.run(SourceFile:-2)
        at android.os.Handler.handleCallback(Handler.java:938)
        at android.os.Handler.dispatchMessage(Handler.java:99)
        at com.facebook.react.bridge.queue.MessageQueueThreadHandler.dispatchMessage(SourceFile:1)
        at android.os.Looper.loop(Looper.java:246)
        at com.facebook.react.bridge.queue.MessageQueueThreadImpl$4.run(SourceFile:38)
        at java.lang.Thread.run(Thread.java:923)

Hi @swrobel
I have created a reproduction application using the environment information you have provided and have been able to implement BugSnag with minifyEnabled true. As such I do not believe that this is due to an incompatibility error.
Rather, based off of the error message you are receiving, it would appear that the BugSnag API key has not been correctly set. You can configure this API key in your AndroidManifest.xml in the application tag. i.e.
<application ...>
  <meta-data android:name="com.bugsnag.android.API_KEY"
             android:value="your-api-key-here"/>
</application>

You can read more about setting this api key here in our documentation.
If after configuring the API key and your application is still producing the same error then please let us know and we can investigate this issue further.

If after configuring the API key and your application is still producing the same error then please let us know and we can investigate this issue further.

I have this key in my AndroidManifest.xml and have had it there for years, and it was working fine until upgrading, as I mentioned:
<meta-data android:name="com.bugsnag.android.API_KEY" android:value="my-key" />

Did you install & launch the app on a real device to test for the crash? When you generated a RN 0.73 project, did you get Kotlin files instead of Java, ex: MainApplication.kt?

Same here

Hi @swrobel
Would you mind sharing your build.gradle files so we may better understand the configuration of your application?
I you would prefer to not share these publicly then please feel free to open a support ticket with us by reaching out to us at<EMAIL_ADDRESS>quoting this github issue (#2060) and attaching the files to the message.

@clr182 I just submitted them via email, ticket #66817. It's worth noting that my release config previously had minifyEnabled true, before I had to change it due to the crash.

Hi @swrobel
Thank you for sharing these files via zendesk.
To update you, we have been able to reproduce this issue and we are investigating this further. We will be sure to let you know once we have more information to share.

Hi @swrobel, thanks for reporting this.
React Native 0.73 bumps AGP to 8+ and it looks like this has changed some of the R8 optimisations, meaning the native plugin class used by the SDK is now being obfuscated.
We'll look to get this fixed in an upcoming release, but in the meantime you can add the following rule to android/app/proguard-rules.pro as a workaround:
-keep class com.bugsnag.android.BugsnagReactNativePlugin { *; }

Hi :wave:
A fix for this issue has been released in version 7.22.4 of the BugSnag JS notifier.
After updating, please let us know whether you are seeing any further issues.


minor: Fix proxyStrictSSL check

bors r+

CC @tumluliu

Huh, why is the windows-latest link missing?


Failure to compile on PPC due to Eigen incompatibility

Issue Type
Build/Install
Have you reproduced the bug with TF nightly?
Yes
Source
source
Tensorflow Version
2.9.1
Current Behaviour?
Compiling TensorFlow from source yields:
external/eigen_archive/unsupported/Eigen/CXX11/../../../Eigen/src/Core/arch/AltiVec/MatrixVectorProduct.h: In instantiation of 'void EigenForTFLite::internal::gemv_row(Index, Index, const LhsMapper&, const RhsMapper&, ResScalar*, Index, ResScalar) [with Index = long int; LhsScalar = float; LhsMapper = EigenForTFLite::internal::TensorContractionInputMapper<float, long int, 1, EigenForTFLite::TensorEvaluator<const EigenForTFLite::TensorReshapingOp<const EigenForTFLite::DSizes<long int, 2>, const EigenForTFLite::TensorMap<EigenForTFLite::Tensor<const float, 4, 1, long int>, 16> >, EigenForTFLite::ThreadPoolDevice>, std::array<long int, 1>, std::array<long int, 1>, 4, true, false, 16, EigenForTFLite::MakePointer>; RhsScalar = float; RhsMapper = EigenForTFLite::internal::TensorContractionInputMapper<float, long int, 0, EigenForTFLite::TensorEvaluator<const EigenForTFLite::TensorReshapingOp<const EigenForTFLite::DSizes<long int, 2>, const EigenForTFLite::TensorImagePatchOp<-1, -1, const EigenForTFLite::TensorMap<EigenForTFLite::Tensor<const float, 4, 1, long int>, 16> > >, EigenForTFLite::ThreadPoolDevice>, std::array<long int, 1>, std::array<long int, 1>, 4, true, false, 0, EigenForTFLite::MakePointer>; ResScalar = float]':
external/eigen_archive/unsupported/Eigen/CXX11/../../../Eigen/src/Core/arch/AltiVec/MatrixVectorProduct.h:2019:1:   required from 'static void EigenForTFLite::internal::general_matrix_vector_product<Index, float, LhsMapper, 0, ConjugateLhs, float, RhsMapper, ConjugateRhs, Version>::run(Index, Index, const LhsMapper&, const RhsMapper&, EigenForTFLite::internal::general_matrix_vector_product<Index, float, LhsMapper, 0, ConjugateLhs, float, RhsMapper, ConjugateRhs, Version>::ResScalar*, Index, EigenForTFLite::internal::general_matrix_vector_product<Index, float, LhsMapper, 0, ConjugateLhs, float, RhsMapper, ConjugateRhs, Version>::ResScalar) [with Index = long int; LhsMapper = EigenForTFLite::internal::TensorContractionInputMapper<float, long int, 1, EigenForTFLite::TensorEvaluator<const EigenForTFLite::TensorReshapingOp<const EigenForTFLite::DSizes<long int, 2>, const EigenForTFLite::TensorMap<EigenForTFLite::Tensor<const float, 4, 1, long int>, 16> >, EigenForTFLite::ThreadPoolDevice>, std::array<long int, 1>, std::array<long int, 1>, 4, true, false, 16, EigenForTFLite::MakePointer>; bool ConjugateLhs = false; RhsMapper = EigenForTFLite::internal::TensorContractionInputMapper<float, long int, 0, EigenForTFLite::TensorEvaluator<const EigenForTFLite::TensorReshapingOp<const EigenForTFLite::DSizes<long int, 2>, const EigenForTFLite::TensorImagePatchOp<-1, -1, const EigenForTFLite::TensorMap<EigenForTFLite::Tensor<const float, 4, 1, long int>, 16> > >, EigenForTFLite::ThreadPoolDevice>, std::array<long int, 1>, std::array<long int, 1>, 4, true, false, 0, EigenForTFLite::MakePointer>; bool ConjugateRhs = false; int Version = 0; EigenForTFLite::internal::general_matrix_vector_product<Index, float, LhsMapper, 0, ConjugateLhs, float, RhsMapper, ConjugateRhs, Version>::ResScalar = float]'

<snip>

external/eigen_archive/unsupported/Eigen/CXX11/../../../Eigen/src/Core/arch/AltiVec/MatrixVectorProduct.h:1976:5: error: 'class EigenForTFLite::internal::TensorContractionInputMapper<float, long int, 0, EigenForTFLite::TensorEvaluator<const EigenForTFLite::TensorReshapingOp<const EigenForTFLite::DSizes<long int, 2>, const EigenForTFLite::TensorImagePatchOp<-1, -1, const EigenForTFLite::TensorMap<EigenForTFLite::Tensor<const float, 4, 1, long int>, 16> > >, EigenForTFLite::ThreadPoolDevice>, std::array<long int, 1>, std::array<long int, 1>, 4, true, false, 0, EigenForTFLite::MakePointer>' has no member named 'load'

See my issue in Eigen: https://gitlab.com/libeigen/eigen/-/merge_requests/764#note_1231907378
Standalone code to reproduce the issue
Compile TensorFlow on PPC/POWER9
The issue is that the specialized TensorContractionInputMapper in eigen_spatial_convolutions-inl.h (at master at https://github.com/tensorflow/tensorflow/blob/master/tensorflow/tsl/framework/convolution/eigen_spatial_convolutions-inl.h) is missing the new load functions as required by Eigen

Seems to be fixed in 2.10.1 either by a change in TensorFlow or the updated Eigen


Allow to display meteorological radar data

Linked to https://github.com/kalisio/kMap/issues/31 & https://github.com/kalisio/kargo/issues/11.

Here is an example of a GDAL script to apply on the source raster to simplify the visualization process:
for %%f in (*.tif) do (
  # Transform the dataset in GEO WGS84
  gdalwarp -t_srs EPSG:4326 %%f output/WGS84_%%f
  # Extract the 2nd band
  gdal_translate -b 2 -co COMPRESS=LZW output/WGS84_%%f output/b2_%%f
  # Extract the 3th band
  gdal_translate -b 3 -co COMPRESS=LZW output/WGS84_%%f output/b3_%%f
)

LZW compression ensure to have an optimized raster that could be exposed using thredds


Diff the files

has anyone tried branching then cloning and then updating your local with the 2.1 files available to then view the diffs?
another great way to do this locally is with something like WinMerge, you can make 2 local copies, update the files in one and then compare the folders.
if we could do the updates individually it will make much more sense in the long run, and using diff tools gives you a panoptic view of the source. Also compare the different versions, it is enlightening....

vasm noticed a few problems when trying to assemble everything, these are highlighted in: https://github.com/AmosFactory/AmosProfessional/commit/b66669a98e91f655cdafe058c80e7dd8e8f22fdf
I'm maintaining the integrity of the files so that the differences in the commits are easy to follow - if you review the commit the changes made are typo's that genam didn't find - like cmp.s, there is no such op-code, it is cmp.b - very interesting.


[Feature][CDC][Postgres] Support PostgreSQL CDC

Search before asking

[X] I had searched in the feature and found no similar feature requirement.

Description
add PostgreSQL CDC
Usage Scenario
No response
Related issues
No response
Are you willing to submit a PR?

[X] Yes I am willing to submit a PR!

Code of Conduct

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

Excuse me, is there any code development for this problem。

Reopen this issue ？

Hi, Do we have news about this? :(👍

Hi, Do we have news about this? :(👍


"ErrorException: Trying to get property of non-object"  while trying to access nonexisting field in BSONArray

If i have a valid BSON Array Object named $data i would access the fields in it via $data->id or $data->name for example.
How do i properly catch following the case:
using
$data->description

where "description" may or may not exist in the $data fields.
Currently calling this would lead to an ErrorException: Trying to get property of non-object
How would i f.e. just return "null" or "false" if the description field doesn't exist in my data.
I thought one big plus of using mongoDB would be the possibility for different structured data in one collection?
MongoDB\Model\BSONArray Object
(
    [storage:ArrayObject:private] => Array
        (
            [0] => MongoDB\Model\BSONDocument Object
                (
                    [storage:ArrayObject:private] => Array
                        (
                            [id] => 84
                            [enumber] => E 472 b
                            [name] => Milchsäureester von Mono- und Diglyceriden von Speisefettsäuren
                        )

                )

            [1] => MongoDB\Model\BSONDocument Object
                (
                    [storage:ArrayObject:private] => Array
                        (
                            [id] => 198
                            [enumber] => E 407
                            [name] => Carrageen
                            [description]=>TestText
                        )

                )

            [2] => MongoDB\Model\BSONDocument Object
                (
                    [storage:ArrayObject:private] => Array
                        (
                            [id] => 293
                            [enumber] => E 941
                            [name] => Stickstoff
                        )

                )

        )

)

Currently calling this would lead to an ErrorException: Trying to get property of non-object
How would i f.e. just return "null" or "false" if the description field doesn't exist in my data.
I thought one big plus of using mongoDB would be the possibility for different structured data in one collection?

To be fair, this issue is pertaining to PHP raising an exception for accessing an unknown field on an object. That's unrelated to MongoDB permitting you to have diverse document schemas within the same collection, which it does.
By default, the library converts BSON arrays and objects to MongoDB\Model\BSONArray and MongoDB\Model\BSONDocument classes, respectively. These both extend PHP's ArrayObject, which provides a relatively user-friendly API somewhere between stdClass objects (not very convenient) and PHP arrays (very convenient). As an aside, this is a compromise since we need to use some class to ensure that we preserve the BSON types when shuffling data to/from the database.
For BSONDocument, we take an extra step and enable ArrayObject's ARRAY_AS_PROPS flag by default, which allows you to use the property accessor (i.e. ->) in addition to the always-on array accessor (i.e. []). We also do this because the the underlying mongodb extension returns documents as stdClass objects, where users would already need to use -> to access things. Keeping this behavior in the library makes for a more consistent experience.
All that said, PHP still requires you to check that a property or offset exists before accessing it. ArrayObject supports such checking via its offsetExists() method (part of the ArrayAccess interface).
For your example, the following should work:
$description = isset($data->description) ? $data->description : null;

If you're using PHP 7, you might prefer to use the null coalesce operator (i.e. ??) for brevity.

I found my mistake - i used a foreach to go through the $data variable as $value and there tried to access $value->description - here the isset function would just cause the script to abort with the above result .i should have used $data->description - isset() works here as indented.
Thank you for your eyeopening answer - i'm a bit stressed because my cs thesis is due ;)

As already mentioned, this is a general PHP "issue" and not specific to either MongoDB or this PHP library.
Don't be afraid to use the error control operator when accessing fields that may or may not exist. If you expect the result to be of a specific type whether or not the field exists, just cast the result to the specific type and you will get the standard value for that type if the field does not exist.
$varOne = @$result->field; // returns the field value, or null if it doesn't exist
$varTwo = (int) @$result->field; // returns the field value as int, or 0 if it doesn't exist


Global kanban with filters

Feature Description
I think it would be great if gitea had a "org level kanban" - that could list issues from ANY project within the org - with issue filtering on so one could f.ex. "list issues from 1 particular project".. OR from a "parent project" - which has subprojects (f.ex. view all 'internal tasks - no matter which subproject they were in) - or filter on "assignee" - so one can see all ones tasks and their "status in kanban flow" across any project..
This is actually our main hiindrance from using only gitea for tasks and planning
Screenshots
No response

Org-level kanban boards are already possible with Gitea, but not the filter options and similar. Could you please rephrase your feature proposal accordingly?

How can I do an Org level kanban board? Only thing I've been able to do, is to make a project directly under org - and then a kanban board for that. Then I can have ONLY ONE project and assign all issues to that project - for it to show up on that kanban board.
Thats NOT the same at all.
Point is that you should be able to have projects.. and issues assigned to those projects show up on the project kanban board..
BUT - then a global view kanban board with filtering - should be possible (as an alternative to having kanban board per project).
This way, you can have your per project kanban board (and some users may only have access to that) - but managers f.ex. - can use the org-level board with filtering - and view f.ex. one users tasks status - across all projects.
The filtering is the same as "the existing swimlanes" feature request - which is useful both for "per project" kanban boards and for a org level/global project-wide kanban board.

such a kanban view - would have to pull "all possible columns" - from all projects - to show their state in a global kanban view.. and that might just make it fairly useless.. especially as gitea does not seem to map "columns" - to a seperate "issue flow" structure.. which it really should to clean this up.

a usecase we would like to support is this:
We have about 15 projects.. we have a kanban/project for each of them - so the project owner(s) can plan and show their progress for each project..
Along side that we have standups - and our teammembers work on multiple projects.. so we'd like at standup to show a single kanban - that shows issues assigned to user X (the swimlanes/filter need for kanban - ticket exists with PR) - across all projects.
alternatively one COULD add "user" filter to the org level users view (its missing that) - to atleast be able to see all issues - but then its not aligned with the feature sorting that kanban does so well.

So you mean that you have sort of an issue dashboard for the whole organisation, which by default displays issues from every project, and then can be filtered to display e. g. issues by assignee?

This sounds like that what is implemented in GitLab. In parent group you can see all the issues from nested repositories and subgroups with their repositories in a form of the list or the kanboard.
And you can filter the issues by assignee, label, author, milestone, and so forth.
But gitlab is very heavy and complicated to setup 😅.
It will be great pleasure once to see this feature in Gitea ❤


Shrink action Fix

Issue #, if available:
https://github.com/opensearch-project/index-management/issues/709
Description of changes:

If the index already has target number of shards, skip the shrink action. This guarantees indices not being shrunk unnecessarily. CHANGE
Use the correct id to release node lock. CHANGE
Only exclude Decision.Type.NO during shard moving dry-run. CHANGE
Set index write block again before sending shrink request, in case of write block flipped by other processes in previous steps. CHANGE
Rename methods below to reflect logic clearly.
getNodeFreeMemoryAfterShrink -> getNodeFreeDiskSpaceAfterShrink
fail -> setStepFailed
updateAndGetShrinkActionProperties -> checkShrinkActionPropertiesAndRenewLock
Update content of related loggers and comments.

CheckList:

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #718 (0e7f320) into 2.x (d357c10) will decrease coverage by 0.19%.
The diff coverage is 43.28%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff              @@
##                2.x     #718      +/-   ##
============================================
- Coverage     75.44%   75.26%   -0.19%
+ Complexity     2642     2641       -1
============================================
  Files           333      333
  Lines         15398    15421      +23
  Branches       2386     2394       +8
============================================
- Hits          11617    11606      -11
- Misses         2417     2440      +23
- Partials       1364     1375      +11

Impacted Files
Coverage Δ

...gement/indexstatemanagement/action/ShrinkAction.kt
67.64% <ø> (-1.48%)
:arrow_down:

...atemanagement/step/shrink/WaitForMoveShardsStep.kt
49.23% <0.00%> (ø)

...exstatemanagement/step/shrink/WaitForShrinkStep.kt
42.00% <0.00%> (ø)

...atemanagement/step/shrink/AttemptMoveShardsStep.kt
57.36% <40.47%> (-3.07%)
:arrow_down:

...exstatemanagement/step/shrink/AttemptShrinkStep.kt
59.42% <53.33%> (-1.30%)
:arrow_down:

...ent/indexstatemanagement/step/shrink/ShrinkStep.kt
35.55% <60.00%> (-0.71%)
:arrow_down:

...xmanagement/indexstatemanagement/util/StepUtils.kt
85.55% <100.00%> (-2.09%)
:arrow_down:

... and 11 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

Question: this is raised against 2.x, but we would also need this on main branch, right?

Question: this is raised against 2.x, but we would also need this on main branch, right?

Added backport to main label

Please add a github issue for ITs around the shrink action fixes if they wont be a part of this PR.

Created issue: https://github.com/opensearch-project/index-management/issues/730


Add support for keycloak compatible plugin

Created an example plugin useful for importing users from keycloak.
Here's the code that keycloak uses to hash passwords by default: https://github.com/keycloak/keycloak/blob/master/server-spi-private/src/main/java/org/keycloak/credential/hash/Pbkdf2PasswordHashProvider.java

We should maybe copy this into core at some point.

@voidmain @robotdan suggested doing that, I wanted to ship it and thought it'd be too much hassle. If we do ship this in core, we should update https://fusionauth.io/docs/v1/tech/migration-guide/keycloak/#install-the-hashing-plugin section of the keycloak doc.


SHI3 - Diffs

After deserializing there are a lot of diffs for SHI3 objects.
looks like everything gets a new NODE_ID, plus some fields contain release information FRELEASE + LRELEASE

merged


Update 'ros_genmsg' to 0.5.12-p0

I've followed this guide
step by step carefully. [Yes]

I've tested this package remotely and have excluded all broken builds.
Here is the links to the Travis/AppVeyor with status "All passed":

https://ci.appveyor.com/project/kgeorgiev93/hunter/builds/24938094
https://travis-ci.com/kgeorgiev93/hunter/builds/113819876

Testing:

https://ci.appveyor.com/project/ingenue/hunter/builds/24945545
https://travis-ci.org/ingenue/hunter/builds/539607958?utm_source=github_status&utm_medium=notification

Released: https://github.com/ruslo/hunter/releases/tag/v0.23.184


Make methods virtual

Make methods of FixpositionDriver virtual so the class is extendable

@floriansegginger Thanks for the PR, we merged it.


Error on Instance Log

I get this error, on a Sinusbot docker
2020/03/19 15:05:56 6b4a3482 9ce69f0d PLUGIN [     lol-rankify:288:48] Error: 403 Forbidden
2020/03/19 15:05:56 6b4a3482 9ce69f0d PLUGIN Unhandled rejected promise: An Unknown Error Occurred. var level is not a number.
2020/03/19 15:05:56 6b4a3482 9ce69f0d PLUGIN Unhandled rejected promise: undefined
2020/03/19 15:05:56 6b4a3482 9ce69f0d PLUGIN Unhandled rejected promise:
2020/03/19 15:05:56 6b4a3482 9ce69f0d PLUGIN [     lol-rankify:292:48] Error: An Unknown Error Occurred. var level is not a number.
2020/03/19 15:05:57 6b4a3482 9ce69f0d PLUGIN Unhandled rejected promise: [object Object]
2020/03/19 15:05:57 6b4a3482 9ce69f0d PLUGIN [     lol-rankify:268:48] Error: 403 Forbidden
2020/03/19 15:05:57 6b4a3482 9ce69f0d PLUGIN Unhandled rejected promise: TypeError: Cannot read property '0' of undefined
2020/03/19 15:05:57 6b4a3482 9ce69f0d PLUGIN Unhandled rejected promise:
2020/03/19 15:05:57 6b4a3482 9ce69f0d PLUGIN [     lol-rankify:286:48] Error: TypeError: Cannot read property '0' of undefined
2020/03/19 15:05:57 6b4a3482 9ce69f0d PLUGIN Unhandled rejected promise: [object Object]
2020/03/19 15:05:57 6b4a3482 9ce69f0d PLUGIN [     lol-rankify:288:48] Error: 403 Forbidden
2020/03/19 15:05:57 6b4a3482 9ce69f0d PLUGIN Unhandled rejected promise: An Unknown Error Occurred. var level is not a number.
2020/03/19 15:05:57 6b4a3482 9ce69f0d PLUGIN Unhandled rejected promise: undefined
2020/03/19 15:05:57 6b4a3482 9ce69f0d PLUGIN Unhandled rejected promise:
2020/03/19 15:05:57 6b4a3482 9ce69f0d PLUGIN [     lol-rankify:292:48] Error: An Unknown Error Occurred. var level is not a number.

TY After all
And sorry if the problem its maded by me
anyhelp

#2 seams to be similar

Correct. Thanks for all the info.
All others reported that the bug disappeared - So I am confused.
I will have to dig into that.

If you leave me your server ip so i can come online and check that would be nice.
You can do it private/ or via sinusbot forums if you want to.

ok, i will create i will taltk to u to private

sinusbot better

You can do it private/ or via sinusbot forums if you want to.

Pm on Sinusbot forum

403 (Forbidden) This error indicates that the server understood the request but refuses to authorize it. There is no distinction made between an invalid path or invalid authorization credentials (e.g., an API key). The client should not continue to make similar requests.
Common Reasons
An invalid API key was provided with the API request.
A blacklisted API key was provided with the API request.
The API request was for an incorrect or unsupported path.
Can you please confirm this?