connect ETIMEDOUT - API's are not working

Describe the bug
Below attach code is working fine in curl, python but the same set of code is not working in Node JS (tried different versions) as well.
Below error -
Uncaught Error: connect ETIMEDOUT 64:ff9b::3498:60fc:443
at TCPConnectWrap.afterConnect [as oncomplete] (node:net:1494:16)
at TCPConnectWrap.callbackTrampoline (node:internal/async_hooks:130:17) {
errno: -4039,
code: 'ETIMEDOUT',
syscall: 'connect',
address: '64:ff9b::3498:60fc',
To Reproduce
Run the program in node shell and you will get the error
Code snippets
const { Configuration, OpenAIApi } = require("openai");

const configuration = new Configuration({
  apiKey: process.env.OPENAI_API_KEY,
});
const openai = new OpenAIApi(configuration);

const completion = await openai.createCompletion({
  model: "text-davinci-003",
  prompt: "Hello world",
});
console.log(completion.data.choices[0].text);

OS
macOS
Node version
Node v18.14.2
Library version
<EMAIL_ADDRESS>/<EMAIL_ADDRESS>/<EMAIL_ADDRESS>

I have the same issue and could not resolve it.

same issue

I also encountered the same problem, did you solve it?

Openai's API is blocked in China. If you want to continue using it, you can use a foreign node to build services。I do this now, and use it normally。

Modify Agent.
链接

In your code snippet, you're trying to use the text-davinci-003 model.
But looking at the code, it appears the currently only gpt-3.5-turbo and gpt-3.5-turbo-0301 models are supported.
https://github.com/openai/openai-node/blob/0363de20747e272a92e41da4a4c4293104aa9461/dist/api.d.ts#L261-L266
The solution would be to make requests directly yourself, instead of using the openai-node package - here's how.

修改代理。
链接

我的服务运行在腾讯云上，没有自带代理。但是对于本地调试来说，这可能是一个很好的解决方案

对服务器节点有要求吗？需要国外节点的服务器吗？

是的，需要国外的服务器的节点，我现在用的是 美国 加州的节点 ，正常使用。

You may encounter ETIMEDOUT if there is a problem connecting from your computer to OpenAI's servers, perhaps because it is blocked somewhere along the chain, or due to networking issues.
If you encounter this issue when using the SDK but not when making the request directly, please open a new issue on this repo.
Related: https://github.com/openai/openai-node/issues/148


Netherrack abuseable due to instamining and mass quantities available.

The value of netherrack needs to be adjusted to prevent exploitation due to easy of mining and availability.
current value = 5

proposing to adjust the value to 0.75 to reduce exploitation.
This would reduce the value of a stack of netherrack from 320 to 48.
I think this still works the current value of netherquartz (4)
I have also adjusted NetherGoldore from 34 to gold nugget * 4  (the average drop from mining)
This also prompted me to adjust gildedblackstone from nethergoldore * 2 and instead set it to blackstone + nethergoldore, this did increase the value by about 20% over what it was as nethergoldore * 2.  I understand there is a chance of gildedblackstone not dropping any gold nuggets; however, gildedblackstone is significantly more rare than either of these and I don't see anyway to exploit this value.


Ideas Box url link

Make link a link that either:

Opens a new tab with that url
On Hover: pops up a clickable thumbnail of the website in the current view

Currently, if a user enters a link with "https" in it, we try to renders https/https twice, so the link does not load.


Add missing API references for coordinator

Description
Based on
https://github.com/apache/druid/blob/753bce324bdf8c7c5b2b602f89c720749bfa6e22/server/src/main/java/org/apache/druid/server/http/MetadataResource.java#L134
And
https://github.com/apache/druid/blob/753bce324bdf8c7c5b2b602f89c720749bfa6e22/server/src/main/java/org/apache/druid/server/http/MetadataResource.java#L95
There are several missing API references for coordinator.
/druid/coordinator/v1/metadata/segments
/druid/coordinator/v1/metadata/segments?datasources={dataSourceName1}&datasources={dataSourceName2}
/druid/coordinator/v1/metadata/segments?includeOvershadowedStatus
/druid/coordinator/v1/metadata/segments?includeOvershadowedStatus&datasources={dataSourceName1}&datasources={dataSourceName2}
/druid/coordinator/v1/metadata/datasources?includeDisabled
This pr adds these missing api references into api-reference.md

Key changed/added classes in this PR

api-reference.md

This PR has:

[x] been self-reviewed.

[ ] using the concurrency checklist (Remove this item if the PR doesn't have any relation to concurrency.)

[ ] added documentation for new or modified features or behaviors.
[ ] added Javadocs for most classes and all non-trivial methods. Linked related entities via Javadoc links.
[ ] added or updated version, license, or notice information in licenses.yaml
[ ] added comments explaining the "why" and the intent of the code wherever would not be obvious for an unfamiliar reader.
[ ] added unit tests or modified existing tests to cover new code paths, ensuring the threshold for code coverage is met.
[ ] added integration tests.
[x] been tested in a test Druid cluster.

All the APIs are used by MetadataSegmentView internal. Maybe we can document these APIs for users who are interested.


#14: 'New sub-issue' button (closes #14)

Issue #14

Test plan
Install github-workflow-pal.crx.zip

Go to any issue
Click on add subissue
it should:

fetch the template
replace the correct parent issue number
copy labels from the parent issue, with the exception of the macro label
copy milestone from the parent issue

test comment

macro is being copied

nice catch, fixed.

Try this version github-workflow-pal.crx.zip


Fix most tests to work with sqlalchemy 2

Fixes for

engine.execute is now connection.execute
nested transaction management is different

Still one failing test

CI is passing. which test is failing for you locally?
The pre-commit CI check can be resolved with
pip install pre-commit
pre-commit install
pre-commit run --all

which will format the files

Great thanks @olirice. I pushed the formatting fixes.
I'm seeing a failure for the following
src/test/test_recreate_dropped.py::test_succeeds_when_defering - sqlalchemy.exc.ProgrammingError: (psycopg2.errors.DuplicateTable) relation "branch" already exists

Codecov Report

Merging #105 (9c68c6e) into master (aef523d) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

: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             @@
##           master     #105      +/-   ##
==========================================
- Coverage   99.88%   99.88%   -0.01%
==========================================
  Files          18       18
  Lines         863      862       -1
==========================================
- Hits          862      861       -1
  Misses          1        1

Flag
Coverage Δ

unittests
99.88% <100.00%> (-0.01%)
:arrow_down:

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

Impacted Files
Coverage Δ

src/alembic_utils/testbase.py
100.00% <ø> (ø)

src/alembic_utils/simulate.py
100.00% <100.00%> (ø)

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

Ah @olirice the test only fails with sqlalchemy 2+. I think ideally CI would run against 1.x and 2.x as part of this PR.

thanks for your work on this, I appreciate it!
the update is available on pypi alembic_utils==0.8.1


grunt task fails with: File not found: 'MyAtomShellApp.exe'

Why is the task not finding the exe file in the appDirectory?  The exe DOES exist in the appDirectory ../bin/app/win32/atom-shell/resources/app.
It fails with this message:
$ grunt
...
Running "create-windows-installer" task
>>File not found: 'MyAtomShellApp.exe'.
Warning: Command failed: File not found: 'MyAtomShellApp.exe'.
  ...
Aborted due to warnings

Here are my files:
package.json:
{
  "name": "MyAtomShellApp",
  "version": "1.0.0",
  "description": "...",
  "main": "index.js",
  "author": "...",
  "license": "ISC",
  "devDependencies": {
    "grunt": "^0.4.5",
    "grunt-atom-shell-app-builder": "0.0.7",
    "grunt-atom-shell-installer": "^0.13.1",
  }

Gruntfile.coffee:
module.exports = (grunt) ->
  grunt.initConfig
    'build-atom-shell-app':
      options:
        cache_dir: '../bin/atom'
        app_dir: './'
        build_dir: '../bin/app'
        platforms: ['linux64', 'win32']
    'create-windows-installer':
      appDirectory: '../bin/app/win32/atom-shell/resources/app'
      outputDirectory: '../bin/installer/'
      authors: '...'

  grunt.loadNpmTasks 'grunt-atom-shell-app-builder'
  grunt.loadNpmTasks 'grunt-atom-shell-installer'

  grunt.registerTask 'default', [
      'build-atom-shell-app',
      'create-windows-installer'
    ]

My app has this folder structure:
bin/
src/
  index.js
  package.json
  Gruntfile.coffee

Is the app that is failing to build in a public repository?

It is in a private repo.
I think the problem is that the task that builds the exe is actually not placing the exe in , but in /resources/app.
I think the create-windows-installer task is expecting the exe to be in  proper although I haven't found the code yet.

Yes, the exe is assumed to be in the app directory.

I think that is a better place for it than resources/app.  I think the other task (https://www.npmjs.com/package/grunt-atom-shell-app-builder) should follow suit.

I think the create-windows-installer task is expecting the exe to be in appDirectory proper

Yes


💬  RFC: Installation Path & Priority

What version of Wrangler are you using?
2.0.2
What operating system are you using?
Mac
Describe the Bug
The Angular CLI does this cool thing where they recommend you install the CLI globally but then when you run ng commands, they also check to see if you have it installed locally. The cases seem to be:

You only have it installed globally or locally, it uses the only one you have.
You have it installed globally and locally. If you are running the update command, it uses the newest version. Otherwise, it always uses local but warns you if your global installation is newer.

This would be great to do for Wrangler. We could tell people to install it globally (for when they want to init a new project) but also recommend they add it to their existing project's package.json's and it should just work.

We should totally do this.


[RFC] Provenance and Attestation in wasmCloud: Foundation and Future Direction

RFC Title
Provenance and Attestation in wasmCloud: Foundation and Future
Introduction
Software supply chain security has become increasingly critical as organizations face sophisticated attacks targeting development and distribution pipelines. Major incidents like the SolarWinds attack in 2020 and the Log4Shell vulnerability in 2021 have highlighted the urgent need for better supply chain security practices. The Log4j incident, in particular, demonstrated how Software Bills of Materials (SBOMs) can be crucial in rapidly identifying and remediation of vulnerabilities in the software supply chain.
The Linux Foundation, through initiatives like the Open Source Security Foundation (OpenSSF) and the SLSA (Supply chain Levels for Software Artifacts) framework, has been leading efforts to establish industry standards for supply chain security. These initiatives emphasize provenance and attestation as fundamental security mechanisms that help protect against supply chain threats. Provenance provides verifiable records of where and how software artifacts were produced, while attestation offers cryptographic proof of their integrity and characteristics.
These mechanisms are essential for:

Verifying the authenticity of software artifacts
Detecting tampering during build and distribution
Establishing chain of custody from source to deployment
Meeting compliance requirements for software delivery
Enabling users to make informed trust decisions

Motivation
For the wasmCloud platform, implementing provenance and attestation through signed Software Bills of Materials (SBOMs) provides several key benefits:

Enables users to verify the authenticity of wasmCloud binaries, built-in providers, and example components
Demonstrates supply chain security best practices for the wider WebAssembly ecosystem
Supports organizations with strict security requirements in adopting wasmCloud
Provides transparency into the platform's dependencies and build process
Facilitates automated security scanning and vulnerability management
Establishes foundation for enterprise-grade security integration through standardized identity and trust frameworks

Detailed Design
This RFC addresses both immediate supply chain security needs and future trust architecture considerations:

Immediate Implementation (Phase 1):

Generate and sign SBOMs and attestations for all wasmCloud artifacts:

Binary artifacts (wasmCloud runtime, wash CLI)
OCI images (including both Debian and Wolfi-based variants)

Make these verifiable artifacts available through:

GitHub releases (for binaries and their SBOMs)
Container registries (for OCI images with embedded SBOMs)

Future Integration Paths (Phase 2 & 3):

Optional tooling integration through wash plugins
Native verification capabilities in Rust
Integration possibilities with SPIFFE/SPIRE for:

External root of trust
Workload identity verification
Enterprise grade security integration

Phase 1: Generation of SBOMs and Attestations
To achieve SLSA v1 Build Level 3, using the in-toto format, two reusable GitHub workflows will be introduced:

A workflow for generating SBOMs and attestations for binary artifacts:

# Reusable workflow for generating SBOMs and attestations for binary artifacts
# This workflow is designed to be called from release jobs to create
# verifiable provenance for wasmCloud binaries
name: Create Binary SBOM and Provenance

on:
  workflow_call:
    inputs:
      artifact-path:
        description: "Path to the binary artifact"
        required: true
        type: string
      artifact-name:
        description: "Name of the artifact"
        required: true
        type: string

# Required permissions for SLSA attestation
permissions:
  contents: read
  id-token: write # Needed for Sigstore API to generate certificates
  attestations: write # Needed for pushing attestations

jobs:
  create-sboms-and-attestation:
    runs-on: ubuntu-22.04
    steps:
      # Generate Syft configuration dynamically to ensure proper version tagging
      - name: Setup Syft config
        run: |
          cat > .syft.yaml << EOF
          package:
            cataloger:
              enabled: true
              scope: "squashed"

          source:
            name: "wasmcloud"
            version: "${GITHUB_REF_NAME}"

          output:
            format: "spdx-json"
            file: "sbom.json"
          EOF

      # Generate SBOM in SPDX format using Syft
      - name: Create Binary SBOM
        uses: anchore/sbom-action@v0
        with:
          path: ${{ inputs.artifact-path }}
          artifact-name: sbom-${{ inputs.artifact-name }}-spdx.json
          format: spdx-json
          config: .syft.yaml

      # Create and sign attestation using Sigstore's API through GitHub OIDC token
      - name: Create Binary Provenance
        uses: actions/attest-sbom@v1 # Uses Sigstore API for certificate generation
        with:
          subject-path: ${{ inputs.artifact-path }}
          sbom-path: sbom-${{ inputs.artifact-name }}-spdx.json

A workflow for generating SBOMs and attestations for OCI images:

# Reusable workflow for generating SBOMs and attestations for OCI images
# This workflow handles container image specific requirements and attaches
# the SBOM directly to the image manifest
name: Create OCI SBOM and Provenance

on:
  workflow_call:
    inputs:
      image-ref:
        description: "Full reference to the OCI image"
        required: true
        type: string

# Required permissions for SLSA attestation
permissions:
  contents: read
  id-token: write # Needed for creating attestations
  attestations: write # Needed for pushing attestations

jobs:
  create-sboms-and-attestation:
    runs-on: ubuntu-22.04
    steps:
      # Generate Syft configuration with OCI-specific settings
      - name: Setup Syft config
        run: |
          cat > .syft.yaml << EOF
          package:
            cataloger:
              enabled: true
              scope: "squashed"  # Important for container images to handle layers correctly

          source:
            name: "wasmcloud"
            version: "${GITHUB_REF_NAME}"

          output:
            format: "spdx-json"
            file: "sbom.json"
          EOF

      # Generate SBOM for the container image
      - name: Create OCI SBOM
        uses: anchore/sbom-action@v0
        with:
          image: ${{ inputs.image-ref }}
          artifact-name: sbom-${{ inputs.image-ref }}-spdx.json
          format: spdx-json
          config: .syft.yaml

      # Attach SBOM to the image using Sigstore for signing
      - name: Attach SBOM to Image
        uses: anchore/sbom-action@v0 # Internally uses Sigstore API for signing
        with:
          image: ${{ inputs.image-ref }}
          artifact-name: sbom-${{ inputs.image-ref }}-spdx.json
          format: spdx-json
          config: .syft.yaml
          attach: true # Attaches signed SBOM to the image

The smart-releases job in wasmcloud.yml will be updated to use these workflows:
# .github/workflows/wasmcloud.yml
smart-release:
  permissions:
    contents: write
    pull-requests: write
    id-token: write # Added for attestation
    attestations: write # Added for attestation

  steps:
    # Generate SBOMs and attestations only during release
    - name: Download Release Artifacts
      if: ${{ inputs.do-release }}
      uses: actions/download-artifact@v3
      with:
        path: artifacts

    - name: Generate Binary SBOMs and Attestations
      if: ${{ inputs.do-release }}
      uses: ./.github/workflows/create-binary-attestation.yml
      with:
        artifact-path: ./artifacts/wasmcloud/bin
        artifact-name: ${{ inputs.crate }}

    - name: Generate OCI SBOMs and Attestations
      if: ${{ inputs.do-release }}
      uses: ./.github/workflows/create-oci-attestation.yml
      with:
        image-ref: ghcr.io/${{ github.repository_owner }}/wasmcloud:${{ inputs.crate }}

    # ... existing smart-release steps ...

    # Release with cargo smart-release and include SBOMs
    - name: release
      if: ${{ inputs.do-release }}
      env:
        GH_TOKEN: ${{ github.token }}
        CARGO_REGISTRY_TOKEN: ${{ secrets.CRATES_PUBLISH_TOKEN }}
      run: |
        # Add SBOMs to the release assets directory
        mkdir -p .release-assets
        cp ./sbom-${{ inputs.crate }}-spdx.json .release-assets/
        cp ./sbom-${{ inputs.crate }}-oci-spdx.json .release-assets/

        # Run smart-release with assets
        cargo smart-release \
          --update-crates-index \
          --execute \
          --no-changelog-preview \
          --no-changelog \
          --assets=".release-assets/*" \
          ${{ inputs.additional-args }} \
          ${{ inputs.crate }}

Collectively, the workflows will:

Generate SBOMs for both binaries and OCI images
Create attestations using GitHub's OIDC token
Attach SBOMs to OCI images
Include binary SBOMs in GitHub releases

Verifying Provenance and SBOMs
The easiest method for verifying provenance and SBOMs is using the GitHub CLI. This method provides the following advantages:

Simpler verification process
Direct integration with GitHub's API
Automatic handling of OIDC token verification
Built-in support for both binary and OCI image attestations
JSON output format for automated verification in CI/CD pipelines

For wasmCloud Binaries
# Install GitHub CLI if not already installed
brew install gh  # or your system's package manager

# Verify binary attestation directly
gh attestation verify wasmcloud-x86_64-unknown-linux-musl-v1.42.0 \
  --repo wasmCloud/wasmCloud \
  --predicate-type https://spdx.dev/Document

# For detailed verification results
gh attestation verify wash-x86_64-unknown-linux-musl-v0.37.0 \
  --repo wasmCloud/wasmCloud \
  --predicate-type https://spdx.dev/Document \
  --format json

For OCI Images
# Verify OCI image attestation
gh attestation verify oci://ghcr.io/wasmcloud/http-server:0.25.0 \
  --repo wasmCloud/wasmCloud \
  --predicate-type https://spdx.dev/Document \
  --bundle-from-oci

# View detailed verification results
gh attestation verify oci://ghcr.io/wasmcloud/keyvalue-redis:0.28.2 \
  --repo wasmCloud/wasmCloud \
  --predicate-type https://spdx.dev/Document \
  --bundle-from-oci \
  --format json

For automated verification in CI/CD pipelines, the GitHub CLI approach with --format json output can be easily integrated into deployment workflows.

The GitHub CLI verifies attestations stored in GitHub's attestation API that were signed using Sigstore through GitHub's OIDC integration during the build process. For additional SBOM analysis and verification, users can leverage other industry-standard tools:

SPDX Tools - For validating SPDX format and license compliance
Syft - For SBOM generation and verification
Grype - For vulnerability scanning based on Syft-generated SBOMs
SBOM Scorecard - For SBOM quality assessment

Phase 2: Integration with wasmCloud Tooling (Optional)
As a convenience method, a wash plugin could be developed as a shim to the GitHub CLI to verify SBOMs and attestations. It could install the GitHub CLI if it's not present.
Phase 3: Native Verification and Trust Architecture (Future Consideration)
As wasmCloud evolves, we need to consider both native verification capabilities, and how they integrate with broader trust architectures. While the Rust ecosystem for SLSA attestation is still maturing, we can explore:

Native Verification Capabilities:

Developing Rust bindings for existing verification tools
Contributing to emerging Rust attestation projects
Creating wasmCloud-specific verification tools

Trust Architecture Integration:

Defining trust boundaries and transitions
Supporting external root of trust systems
Enabling enterprise security integration patterns

While native verification capabilities are important, they alone cannot establish end-to-end trust for the wasmCloud platform. Even when wash and wasmCloud host binaries include SBOM and attestation verification capabilities, enterprise-grade security requires the root of trust to remain external to these binaries, as allowing them to self-verify would create a circular trust dependency that undermines the entire security model.
This consideration of trust architecture naturally leads us to explore integration with established cloud-native security frameworks.
External Trust and Platform Integration
The separation of verification tools from the root of trust opens interesting possibilities for integration with cloud-native security patterns, particularly CNCF's SPIFFE (Secure Production Identity Framework for Everyone). SPIFFE provides a standardized way to securely identify software systems in dynamic and heterogeneous environments through:

Cryptographically-verifiable identity documents (SVIDs)
Automated workload attestation
Dynamic identity provisioning
Platform-agnostic trust domains

Integration Approaches
Two approaches merit consideration for integrating external trust with wasmCloud's security model:

Boundary Integration:

SPIFFE/SPIRE integration at platform edges:

wash and wasmCloud host binaries receive SVIDs
External workload verification via SPIRE
Internal verification continues using NATS nkeys

Advantages:

Minimal changes to existing architecture
Clear separation of concerns
Immediate enterprise grade security integration
Preserves proven internal security model

Challenges:

Limited to platform boundaries
Two separate identity systems to maintain
Potential complexity in trust transition points

Deep Integration:

Replace or augment NATS nkeys system with SPIFFE SVIDs:

All workloads use SPIFFE identities
Unified identity model throughout
Native SPIRE attestation for all components

Advantages:

Consistent identity model
Enterprise grade security integration
Simplified trust architecture
Better alignment with cloud-native patterns

Challenges:

Major architectural changes required
Migration complexity for existing deployments
Performance implications to evaluate
NATS integration considerations

Both approaches merit consideration, and the choice depends on specific deployment needs and security requirements. If there's community interest in pursuing either approach, a future RFC could be put forward to detail the design and implementation strategy.
References

SLSA Provenance Specification
Sigstore
Syft
GitHub CLI
SPIFFE Concepts

Backwards Compatibility
The proposed changes maintain full backward compatibility:
Phase 1 (Current Scope):

SBOM generation and attestation are additive features
Existing build and release processes continue to function as before
Verification is optional and doesn't affect existing deployments
No changes to runtime behavior or APIs

Future Considerations:

Phase 2 (wash plugin) would be entirely optional
Phase 3 implications would be addressed in a separate RFC
Any future identity integration would be designed with compatibility in mind

Alternatives Considered

No Action:

Continue without formal supply chain security measures
Miss opportunities for enterprise adoption
Fall behind industry security practices

Bespoke Solution:

Develop custom SBOM and attestation tooling
Risk incompatibility with industry standards
Duplicate existing ecosystem solutions
Increase maintenance burden

The chosen approach leverages established tools and standards, ensuring compatibility with the broader security ecosystem while minimizing implementation complexity.
Unresolved Questions
While the implementation path for Phase 1 is clear, using well-established tools and standards (SLSA, in-toto, Sigstore, SPDX), future phases regarding trust architecture and identity integration would require separate RFCs with their own detailed design considerations.
Conclusion
This RFC proposes a pragmatic approach to enhancing wasmCloud's supply chain security through:

Immediate implementation of SBOM generation and attestation
Leveraging industry-standard tools and practices
Establishing a foundation for future security integration
Maintaining flexibility for enterprise deployment scenarios

The phased approach allows for immediate security improvements while keeping options open for deeper integration with cloud-native security frameworks.

Hello Joonas,
Thanks very much for taking time to read through the RFC, and raise some
excellent questions; so, let me address the suggestions and questions one
by one:

In respect to the scope of phase one, it only covers first-party
binaries, and capability providers, built by the wasmcloud
https://github.com/wasmCloud/wasmCloud/blob/main/.github/workflows/wasmcloud.yml
workflow,
either directly within it, or by calling the provider
https://github.com/wasmCloud/wasmCloud/blob/main/.github/workflows/provider.yml
workflow;
so, the scope is limited to the wasmCloud assets, which are expected to be
found in production environments.

It's worth noting that the SBOM generation and signing workflows,
as the RFC shows, are callable workflows, and we can decide to
utilize them
for more wasmCloud assets, if the need arises down the road.

In respect to the phases, phase 2 is for vanity, and that's why it's
marked as optional; so, it could be safely removed without missing a beat.
Phase 3, however, is clearly marked as subject of a different RFC, if
and when it might be needed. As to why I think it needs to be mentioned
is for awareness and educating those who are less security savy that what
is often dubbed as enterprise security necessitates integrating with
external trust and verification providers. In that respect, since wasmCloud
sometimes is compared to Kubernetes, then we can also draw a comparison
here, and consider how a k8s installation is verified on public cloud
platforms (i.e. kubelet binary integrity verification, controlplane
components verification, container runtime verification are all done by
cloud platform services external to the k8s installation). However, boiling
the ocean in one step was not the goal here, and the RFC attempts to raise
just enough points for one to contemplate, without committing to any
immediate actions, in depth analysis, or even upcoming solutions. Education
is the primary objective, not solutioning.
In regards to the choice of tools and formats, it will be extremely
difficult to cover them in depth either through emails or in the RFC text,
as there are many nuances to consider; so, I'd try to cover the most
important aspects, in, hopefully, a more digestible format:

The scope of the RFC is Provenance (where is this package coming
from?), Trust (says who?), and Transparency (where can I find the
proof?).
Barring proprietary solutions, the widely accepted and used tools
and frameworks include In-Toto
https://in-toto.io/docs/what-is-in-toto/, TUF
https://theupdateframework.io/docs/overview/, SLSA
https://slsa.dev/spec/v1.0/, Sigstore https://www.sigstore.dev,
and Notary v2
https://github.com/notaryproject/.github/blob/main/README.md, with
separate and overlapping scopes.
Sigstore is just focused on artifact signing and signature
verification, and while Notary v2 provides that too (through its Notation
CLI), by the time that the latter was ready, Sigstore and its tools
(Cosign, Fulcio, and Rekor) were widely accepted, supported and used, by
majority of the CNCF projects, including Kubernetes.
SLSA has its roots, via the Linux Foundation, in the executive
order 14028
https://www.nist.gov/itl/executive-order-14028-improving-nations-cybersecurity
.
Both In-Toto (as a framework) and SLSA target provenance; however,
In-Toto goes deeper, and consequently requires much more work to
define and
implement; but SLSA was created to offer a progressive approach
(please see security
levels https://slsa.dev/spec/v1.0/levels, where higher means better
and more stringent), while leaving room for future spec expansion
https://slsa.dev/spec/v1.0/threats.
TUF is more focused on software update (related to trust), and
Notary is focused on making it easier to use and more accessible. So, I
considered it not the best fit here.
By using the In-Toto format, which is widely adopted, we broaden
the choice of tooling for verification.
SBOM, however, is focused on revealing constituent components of
software packages and the chain of dependencies (i.e. focus is
supply chain
transparency), which is valuable in threat modeling and vulnerability
assessment.
The two leading SBOM formats are CycloneDX https://cyclonedx.org,
and SPDX https://spdx.dev. While both are excellent and have their
own fans, SPDX is officially adopted by the Linux Foundation and CNCF. In
addition, pretty much any SBOM generation tool I know supports either one
or both of these formats (the main difference is how far down the
rabbit hole they go).
Since wasmCloud is open-source, a CNCF project, and is on GitHub,
by using the GitHub's own Attest Build Provenance action
https://github.com/marketplace/actions/attest-build-provenance, we
readily achieve a number of goals:
We can leverage GitHub's attestation APIs, and its CLI to
verify the provenance records, and associated signatures.
We leverage Sigstore's keyless signing, and public-good
instance, which makes the signatures transparently available
anywhere Rekor
is accessible.
We also use the Ancore SBOM action
https://github.com/marketplace/actions/anchore-sbom-action, which
uses Syft, which supports both SBOM formats. This provides us
the SBOM and
their attestation records.
By using callable workflows, we achieve SLAL build level 3 (as
mentioned above higher is better; so, it's always desired).
And finally, not only the generation process (the scope of phase

is CI ready; but the verification on the end user side is
both CI and CD
ready.

In terms of verification in air-gapped environments, it must be done
in their CI pipelines (where packages and artifacts are sourced from
wasmCloud and prepared for the air-gapped environment), not the CD
pipeline; this isn't a miss or a mistake; the solution opts for the most
transparent and accessible provenance and attestation record keeping
systems available (which by GitHub is associated with the system of source
(i.e. wasmCloud repo)), which is the right choice for an open source
project, and uses the same approaches utilized in Kubernetes release.
The RFC already includes the verification steps using GitHub CLI and
names other tools, which could be used for verification of different
aspects of what's being generated and made available; user organizations,
depending on their use case or existing tooling in their environments, can
decide what to use to verify the wasmCloud artifacts. The RFC mentions some
of the common tools, as building blocks, not complete verification
solutions, which fall outside the scope of this RFC, and are more suitable
for wasmCloud documentation.
I already use these in our workflows and systems; so, the users can
easily utilize the callable workflows included in RFC in their own build
process, and then utilize the verification tooling of their choice to
verify the artifacts. I assumed that's clear; if it isn't, of course the
RFC could be augmented to, or commented on, to make that clear.

Cheers,
ossfellow
On Thu, Dec 12, 2024 at 1:33 PM Joonas Bergius @.***>
wrote:

Hey @ossfellow https://github.com/ossfellow,
First off, thank you for taking the time to write down all of your
thoughts on this proposal, it's very helpful to have this written down.
In the interest of making this bit more digestible as a whole, I propose
focusing the RFC on securing the supply chain for wasmCloud, which would
essentially boil down to doing Phase 1. In terms of scoping, I would
recommend scoping the efforts around either:

Core wasmCloud components - essentially wasmcloud-host, wash and
wadm.
First-party wasmCloud ecosystem - the core wasmCloud components,
the first-party providers, other first-party software (such as the NATS
KV-based secrets backend) and possibly even the example components. By
first-party I'm referring to software that is hosted in the
wasmCloud/wasmCloud repository.

Doing so in my mind would make the RFC tractable to complete as a whole,
and the follow-on work (phase 2 + phase 3) could be proposed in a separate
RFC that's focused on solving just those specific areas.
Assuming this makes sense, some questions I'd like to see covered around
the proposed work in Phase 1 are as follows:

Why specific tools, formats, frameworks (SLA Build L3) and standards
were chosen (technical reasons, industry adoption, other criteria)?
a. What alternatives were considered for each of these? What motivated
the choice of the proposed tool, format, framework or standard over the
alternatives?
2.
I'd like to see it holistically addressed how end-users can consume /
verify / validate the proposed supply chain information, specifically
something I'd like to see addressed is how end-users in a limited
connectivity environment (say, behind a DMZ or airgapped network) could
make use of this information?
a. How could this information be consumed programmatically outside of
a CI/CD use case, for example to gate whether a given artifact should be
allowed to be deployed? This should likely cover the major platforms we
support as deployment (or perhaps simply Kubernetes?)
3.
If there's desire to cover the broader ecosystem, it would be
interesting to address how this information could be used for policy
decisions within wasmCloud? For example, if a given provider does not come
from an attested source, how would you be able to prevent wasmCloud from
running it?
4.
If covering the broader ecosystem, it would be good to also include
some thought around providing guidance to the broader community on how
these same tools and techniques could be applied to your own components and
providers.
—
Reply to this email directly, view it on GitHub
https://github.com/wasmCloud/wasmCloud/issues/3787#issuecomment-2539741578,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AL6ZVV4VZERDYWT6JLTJH3D2FHJIJAVCNFSM6AAAAABTHJ2PCOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMZZG42DCNJXHA
.
You are receiving this because you were mentioned.Message ID:
@.***>


tower of hanoi in java for issue number #1962

tower of hanoi in java for issue number #1962
Please include a summary of the change and which issue is fixed. List any dependencies that are required for this change.
Fixes #1962
Replace #1962  with the issue number which is fixed in this PR
code change
Please delete options that are not relevant.

[x] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update
[ ] Documentation Update

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have created a helpful and easy to understand README.md
[ ] I have made corresponding changes to the documentation
[ ] My changes generate no new warnings
[ ] I have added tests/screenshots(if any) that prove my fix is effective or that my feature works

@Rounak-chauhan place it in proper folder

Algorithm/Dynamic

done sir please check

@Rounak-chauhan merged


Offer of dark theme preferences to use as defaults

System information:

Windows 10
DBeaver <IP_ADDRESS>901202008
Java that came with 5.3

Connection specification:

SQL Server latest driver

Describe the problem you're observing:
Offer my preferences file to improve colors for the dark theme.  Hoping it could become the shipped defaults.
Mainly just the SQL Server Editor and Data Grid were adjusted.
Colors are more muted, less contrasting.  Better for longer sessions.
The odd/even row is more subtle.
There are still problems as some areas are apparently are not settable but IMO is large improvement over the defaults.  Hope you consider trying it out.
Steps to reproduce, if exist:

Download the attached file, rename by trimming the ".txt"
File -> Export -> "Preferences" -> Save to file so you can go back.
File -> Import -> "Preferences" -> The attached file

There may be a few other settings in there besides colors that need to be pruned.
DBeaverPrefs.epf.txt

I would say that your settngs are better than the DBeaver default. But there are still some way left to go before the dark scheme are useful. The contrast in comboboxes, treeviews and still too low to be useful. Maybe a change in font could help it up some.
PS. Take a look at JetBrains DataGrip and the color scheme Darkula that is clear and comfortable to look at even for long working hours.

Thanks for proposal. We'll try to adapt it in the next version..

Also note that you can use Darkest Dark theme (can be optionally installed in DBeaver from Help->Install New Software, P2 repo is preconfigured in the dropdown list).
Darkest Dark is much-much better than standard Dark theme. We are thinking about shipping it along with DBeaver although it is not that easy.

fyi, i selected the "DBeaver CE Update site", then tried just "DBeaver Core" but it stopped with "Cannot complete the install because of a conflicting dependency".  Then I re-tried by selecting all of them (not just core) and got similar message.  No big deal, I can wait.

Hi all,
Even with this updated theme, there are still a few values that are simply illegible. Any chance the base navigation/helper text can be made to be configurable as well?

@DavidMCook can't reproduce this:
Did you restart DBeaver after applying darkest dark theme?
What is your OS?

I'm running on Mac OSX, and I did restart DBeaver after. But perhaps the
theme isn't truly available? Now that you mention, "darkest dark," should
that be the actual name of the theme in the dropdown menu?
Best,
*David Cook *
On Tue, Mar 5, 2019 at 8:50 AM Serge Rider<EMAIL_ADDRESS>wrote:

@DavidMCook https://github.com/DavidMCook can't reproduce this:
Did you restart DBeaver after applying darkest dark theme?
What is your OS?
[image: image]
https://user-images.githubusercontent.com/6398845/53813622-194e6a80-3f6f-11e9-96f4-438171a7b5b6.png
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/dbeaver/dbeaver/issues/5184#issuecomment-469708121,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABqYijQCKMDu-PjIfNDJyjDl0RqapJxCks5vToREgaJpZM4afR3W
.

Closing the loop on this - it looks like the "Darkest Dark" them failed to install when using the direct jar method. Pulling from "install new software" (as mentioned in the later post) worked perfectly. Granted, something still didn't get set quite right, but it's a world of difference.

Yeah, I'm sorry to keep asking questions here but I'm guessing this isn't what the Properties tab is supposed to look like:

It definitely shouldn't look like this.
Is this Darkest Dark?


Missed words?

I don't believe the below makes sense?
>>You also its features<< to monitor and control Azure spending and to optimize Azure resource use.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 2d5c4c89-1778-7b70-db0e-1425315d027b
Version Independent ID: 7502f1f9-0ab9-5596-1254-1912b655b5e9
Content: Overview of Azure Cost Management and Billing
Content Source: articles/cost-management-billing/cost-management-billing-overview.md
Service: cost-management-billing
GitHub Login: @bandersmsft
Microsoft Alias: banders

@Daniel-AFK12
Thanks for your feedback! We will investigate and update as appropriate.

@Daniel-AFK12 Thanks! I made a pull request to fix this. https://github.com/MicrosoftDocs/azure-docs-pr/pull/107019

@Daniel-AFK12 @MarileeTurscak-MSFT Thanks for catching this and for fixing.


Customs Builds

Hello, I want to build the dropdown module only.
I downloaded the code and ran node build.js --bs_version 4 --minify --only dropdown from root. I got the following error: Cannot find module 'C:\Users\...\bootstrap.native-master\build.js
What am I missing ?

I would do it the other way, if I already have a configured webpack then I would just import the module import Dropdown from './components/dropdown-native.js' or if I want to build a bundle, I would comment out all the other modules and run the npm run build command. And used the build result from the dist folder

@madeInLagny we replaced all build tools with rollup and the wiki is out of date.
Stick around, the current build tools will have a new update very soon.

@madeInLagny I have a new build script, currently working on it's logic to make it more flexible.
I'm now currently working on a way to include ONLY util functions that are used by requested components and not ALL by default.

@madeInLagny and @cvaize the new build script is now online, check it out.
I've updated the above guide accordingly and will link to it as a temporary guide for future queries.
Talk to you soon.

@thednp, thanks for the updated build script and explanation, it works great for me.


Implement starknet_call

Seems like all binary builds fail on this: see here

I guess we should also update our README file under Installation section, as it's now requires additional step like  git submodule update --init --recursive

The Build and Publish Docker Image pipeline took over an 2h(and still in progress...) on this branch which is definitely too long. It appears the simultaneous building for linux/amd64 and linux/arm64 architectures, particularly the emulation of ARM64 on AMD64 hardware, is slowing us down. We might consider building images for these architectures in separate jobs. Here is job.
@stdevMac do you think we could set this up?


Resetting tickets (and their children)

For our use case, it's useful to have resetTicket methode in the API.
To allow re-encode a video without re-creating the encoding ticket.
The reset should set a ticket back to its initial state.
So after that commenceState has to be called to get things happen again.
When resetting a meta ticket all encoding childs should also be reset.
When resetting a 'master' encoding ticket, all tickets of a depending profile should be reset too.
Do we implement this as a model function or stored procedure?

Are you aware of the the following feature – you might be able to reuse it for your goals

Do we implement this as a model function or stored procedure?

Currently we have Ticket::resetSource, which does some similar things, but is very specific.
For consistency and transactional reasons I think this should be moved to a stored procedure, which should also support a desired state for the recording ticket (exact state, first state before or first state after, if there are none before) and maybe even for the encoding tickets.

What did you mean with before and after? Before which thing or state?

As arbitrary states can be disabled per project the target (to reset to) state has to computed from a desired hardcoded state. Example: desired state for reset is ready to encode, if it is disabled, the next state after should probably be selected.
I first thought about resetting to the previous state for disabled states, but this wouldn't be helpful.

How would you provide these desired states for different ticket types to a stored procedure?
Having explicit parameters for each type? So we'd have to extend the API every time (although it didn't happen for a long time) we add a ticket type?


Faild sending email

Hi. I've got this error: "Postmark delivery failed: Invalid 'From' value." Where I should set option "From"?

Did you solve this issue?


feature: print runtime git commit

Pull Request Description
Describe what this PR does / why we need it
Print runtime commit id of Rama in rama-manager and rama-daemon logs. It helps us to find the correct commit id while debugging.
Does this pull request fix one issue?

NONE
Describe how you did it
Link a flag "main.gitVersion" while building binaries, and add logs in rama-daemon and rama-manager.
Describe how to verify it
Run rama-daemon and rama-manager pod, logs of "starting rama manager with git version: " will be printed at the first place.
Special notes for reviews

Codecov Report

Merging #19 (26c3499) into main (0633357) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main      #19   +/-   ##
=======================================
  Coverage   13.21%   13.21%
=======================================
  Files          22       22
  Lines        1907     1907
=======================================
  Hits          252      252
  Misses       1606     1606
  Partials       49       49

Flag
Coverage Δ

unittests
13.21% <ø> (ø)

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

Continue to review full report at Codecov.

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

IMO, I don't think this will help us a lot, because

log won't be kept for a long time, it rotates usually
commit id is not useful compared with tag, which could be found in image url

For the first problem, I add an /rama/VERSION file into the image for long time usage.
For the second problem, image tag sometimes is unreliable. This happens mostly in develop environment, developer sometime don't know the exact code version if they dose not use a official release or have changed the image's tag.


select  Datepicker wheel with appiumlibrary with robotframework.

hi all , I have issue for select value picker wheel with appiumlibrary with robotframework. I want to select value for picker wheel but I can't set value for picker wheel .

This does not seem related with Robot Framework.

This tracker is for bug reports and enhancement requests related to Robot Framework itself. Issues related to external libraries and tools should be submitted to their own trackers and questions are typically best sent to mailing list, Slack, or other such support forums.


parser for combined glyphs and long glyphs

combiners:

[x] headword-modifier
[x] preverb-ala verb
[x] preposition-ala object
[x] preverb-verb
[x] preposition-object
[ ] combined numbers

long glyph:

[x] long pi
[x] long a
[x] long n
[x] long X ala X
[ ] long anu

[ ] binary anu
[ ] multiple anu
[ ] anu seme

[x] long prepositions
[x] underline lon

This will be tracked on #35 and #36 instead


table_1_trans - check for case sensitivity in columns

check_same_id column values should not be case sensitive
Note - Main ticket #584

This problem will be addressed in cQube v5.0.

This is related to cQube v4.1 beta and not implemented in the current version


SYntax Highlighter

Hi,
On a clean install I can't use the syntax highlighter webpart, due to the following error:
"Can't find brush for: x"
Installed on clean site on O365-tenant.

I'm having the same issue

Same problem here.

We are experiencing the same issue. Has anyone found a fix or workaround?

Same for me. Please update

Same issue here unfortunately...


read_attrs only addresses keys which map cleanly to sub-devices

ex, for an AD object
sd.read_attrs = ['tiff1']
sd.tiff1.read_attrs = []

Is what is required to get just the image key out of sd.read() not everything AD knows about.

I think this would be clearer if we renamed read_attrs -> read_cmpts, that is the list of a Devices components that it will consult as part of the read process.
Tuning how a Devices or  Signal tunes what keys it includes in the read dict that it it's self produces is a different problem.

It's certainly too much information in the case of plugins, but isn't it useful to be able to say "I want subdevice.**" to be read? That's why it's implemented as-is.

read_cmpts then could potentially include components that aren't even part of the Device hierarchy. __getattr__ stuff probably could be removed in that case, though.

I am super confused

Am I misunderstanding your suggestion?
device.read_cmpts = [device.cpt1]

I am suggesting to leave the functionality identical, but to rename it because it confused me.
I was mapping attrs -> keys that will be in the dictionary returned by read, instead a list of the name of sub-components of the current device that will be consulted as part of the read.

It was originally signals then renamed to attrs because of the exact problem you're describing. attrs is at least what Python would call them.

To sum up:

"read_signals" is problematic because the names can refer to Signals or Devices.
"read_attrs" is problematic because not all objects attributes qualify (only those that support .get()).
"read_cmpts" is heavily abbreviated for my taste (I can hear myself spelling out: "No, C-M-P-T-S....")
All of these might suggest that their contents are objects, not their string names.

How about:

signal_names -> component_names
read_signals -> read_names and likewise for configuration_*

Better make these changes Monday if we make them at all. Sanjit and Milinda already took notes on the existing terminology.

@tacaswell  @danielballan  Are you ok with closing this? I think we agreed that all of the proposed names have their own issues, so we may as well stick with what we have (and it being somewhat late to rename things and all...)

Yeah, I came to the same conclusion. If @tacaswell is OK,  close it.


The distortion_corrector has no warning when a velocity_report topic isn't subscribed

Checklist

[X] I've read the contribution guidelines.
[X] I've searched other issues and no duplicate issues were found.
[X] I'm convinced that this is not my fault but a bug.

Description
The distortion_corrector runs successfully even if a velocity report topic isn't subscribed.
Expected behavior
If the distortion_corrector node cannot subscribe a velocity_report topic, there should be a warning or it should fail to run.
Actual behavior
same as the description
Steps to reproduce

filter the /vehicle/status/velocity_status topic from rosbag
run sensing module

Versions
No response
Possible causes
No response
Additional context
No response

@yukke42 any updates on this?

@yukke42 Since the input status of new distortion_correction has already checked and logged here.
IMO, we don't need to add additional diagnostics for that.
shall we close this issue? cc @miursh

@badai-nguyen Cloud you put the link to PR here? We can close this issue.

Resolved by https://github.com/autowarefoundation/autoware.universe/commit/6fbdce5513b8a3992531da2c0a70597b4e293f2a


Macy doesnt auto paste on the 2nd screen

When I try to paste using the option of "paste automatically" . It works properly on the first screen , but not on the extended display

Can you please provide the Maccy version you use? You can get it in the "About" window.
Can you please record a screen video showing the problem? You can do this using QuickTime.app.
Can you please share the output of running defaults read org.p0deje.Maccy in Terminal.app?

@p0deje maybe you should try to create some issue template 😃

@p0deje I've the same issue due to which I've had to disable the pasteByDefault option. It happens when the paste option is used on two windows of the same application - for example Chrome windows which are open on both the primary and secondary monitor. When I try to paste on secondary, it pastes on Chrome in primary window instead.
Please find the info you requested for me below:

Version 0.26.2 (17)
Please find here. It got pasted on the chrome open on the primary monitor while the recording is on the secondary monitor.
Please see below:

➜ defaults read org.p0deje.Maccy
{
    "KeyboardShortcuts_popup" = "{\\"carbonModifiers\\":2048,\\"carbonKeyCode\\":8}";
    "NSStatusItem Visible Item-0" = 1;
    "NSWindow Frame SUStatusFrame" = "664 709 400 134 0 0 1728 1079 ";
    "NSWindow Frame SUUpdateAlert" = "554 510 620 398 0 0 1728 1079 ";
    "NSWindow Frame com.sindresorhus.Preferences.FrameAutosaveName" = "-1313 396 542 440 -1920 37 1920 1055 ";
    SUEnableAutomaticChecks = 1;
    SUHasLaunchedBefore = 1;
    SULastCheckTime = "2023-06-23 15:54:16 +0000";
    SUUpdateGroupIdentifier =<PHONE_NUMBER>;
    WebKitDefaultFontSize = 13;
    WebKitJavaEnabled = 0;
    WebKitJavaScriptEnabled = 0;
    WebKitPluginsEnabled = 0;
    WebKitStandardFont = "-apple-system-font";
    WebKitUserStyleSheetEnabledPreferenceKey = 1;
    WebKitUserStyleSheetLocationPreferenceKey = "/Applications/Maccy.app/Contents/Frameworks/Sparkle.framework/Resources/ReleaseNotesColorStyle.css";
    enabledPasteboardTypes =     (
        "public.png",
        "public.rtf",
        "public.tiff",
        "public.html",
        "public.utf8-plain-text"
    );
    hideFooter = 0;
    hideTitle = 1;
    history = {length = 42, bytes = 0x62706c69 73743030 a0080000 00000000 ... 00000000 00000009 };
    historySize = 115;
    ignoredPasteboardTypes =     (
        "com.typeit4me.clipping",
        "net.antelle.keeweb",
        "de.petermaurer.TransientPasteboardType",
        "Pasteboard generator type",
        "com.agilebits.onepassword"
    );
    maxMenuItems = 10;
    migrations =     {
        "2020-02-22-history-item-add-copied-at" = 1;
        "2020-02-22-history-item-add-number-of-copies" = 1;
        "2020-04-18-switch-storage-to-core-data" = 1;
        "2020-04-25-allow-custom-ignored-types" = 1;
        "2020-06-19-use-keyboardshortcuts" = 1;
        "2020-09-01-ignore-keeweb" = 1;
        "2021-02-20-allow-to-customize-supported-types" = 1;
        "2021-06-28-add-title-to-history-item" = 1;
        "2021-10-16-remove-dynamic-pasteboard-types" = 1;
        "2022-08-01-rename-suppress-clear-alert" = 1;
        "2022-11-14-add-html-rtf-to-supported-types" = 1;
        "2023-01-22-add-regexp-search-mode" = 1;
    };
    pasteByDefault = 1;
    popupPosition = cursor;
    removeFormattingByDefault = 1;
    searchMode = fuzzy;
    showInStatusBar = 1;
    showRecentCopyInMenuBar = 0;
}

I have the same issue. Really appreciate it if this can be prioritised.

@harshavarma @ignorantshr Do you experience it in Chrome too or in other apps?

@harshavarma @ignorantshr Do you experience it in Chrome too or in other apps?

Yes, reproduced in VSCode

I am not able to reproduce the issue after upgrading the below:

MacOS Monterey v12.6.7 from v12.6.6
Maccy v0.26.2 to v0.26.5

I just upgraded Maccy to v0.26.5 and I can still reproduce. Trying to paste in the Chrome address bar on a secondary monitor simply changes the focus to the chrome window in the primary monitor without pasting.
MacOS 13.4.1

after I upgraded Maccy to v0.26.5, in runs well in vscode. MacOS 13.2.1

I've just tested on Maccy 0.26.5 and macOS 13.4.1 - both Chrome and VSCode work fine. If someone can provide a reliable way to reproduce the issue or at least record a video showing the problem - it would be a good start.

Going to close since no response for several months. Feel free to re-open with more details.


Backend Wiki to point to front-end wiki

Describe the task that needs to be done.
A wiki page needs to be created for the backend, explaining and linking towards the front-end repo wiki.
We are doing this to consolidate all our wiki documents in one place (one repo) rather than duplicating and doubling the work for any new wiki additions.
Describe how a solution to your proposed task might look like (and any alternatives considered).
A wiki page added to the backend
Notes

Added link to front end wiki in backend wiki


Updates

It would be particularly helpful to review the README and make sure it makes sense.

:thumbsup:

Huh, I'd completely forgotten about this PR :)

:rabbit: :rabbit2:


Fixing bug with retry, and tweaks to interface

This PR will address #18, specifically there was a bug in a missing parameter. However, I wound up doing several changes that I think overall improve the usage of the urlchecker greatly! I'll discuss them here.

default of false was a bug for whitelist parameters -the default needed to be an empty string, and then in the case of a list with an empty string [""] that would be parsed with split, we need to ensure that we remove it.
I'm not a heavy user of exit() but it was having weird functionality where the success loop would exit with an error code, and the error loop the other way around. I changed this to a clean sys.exit with an error code (0 for success, 1 for fail) so it's clear.
the check_repos function wasn't returning the list like it should - not sure how it was working before!
I added a clear printing of all params to the onset of the function so it's easier to debug when a user hits an issue (they can copy paste those lines so you can quickly debug)
I added a check so that we don't check the same urls twice for any given page.
I removed stream=True from requests.get. This is typically used for streaming large files to disk, and for checking urls in documentation it's more likely to lead to some error because it tries to hold on to the connection.
I also removed the param to follow redirects, as following redirects is the default for requests.
I was having a really hard time looking at how the results were printed - the spacing was a little strange. I found that when I removed the formatting and colored the entire URL, the interface is much more clear to visually parse! Here is the UI before the change:

and after

Notice how I can quickly see green (passing) and the parameters I've set at the top. I hope you like this better, I like it a lot better! It also simplifies the functions a lot by not needing to pass around a format string.
You can see the full successful run (with new syntax) here:
https://github.com/HPC-buildtest/buildtest-framework/pull/211/checks?check_run_id=498679759

This looks good! Great look on the colouring of links, that is definitely more user-friendly. I am working on setting up Travis and codecov again, to ease up testing, commits and also PRs.


runserver_plus --print-sql only prints first two queries

When running runserver_plus --print-sql, only the first two queries are printed.
Python version 3.9.1
Django version 3.1.5
django_extensions version 3.1.0
DEBUG is True
Log after startup:
python manage.py runserver_plus --print-sql
SELECT name,
       type
  FROM sqlite_master
 WHERE type in ('table', 'view')
   AND NOT name='sqlite_sequence'
 ORDER BY name

Execution time: 0.000529s [Database: default]
SELECT "django_migrations"."id",
       "django_migrations"."app",
       "django_migrations"."name",
       "django_migrations"."applied"
  FROM "django_migrations"

Execution time: 0.000485s [Database: default]
Performing system checks...

System check identified no issues (1 silenced).
SELECT name,
       type
  FROM sqlite_master
 WHERE type in ('table', 'view')
   AND NOT name='sqlite_sequence'
 ORDER BY name

Execution time: 0.000531s [Database: default]
SELECT "django_migrations"."id",
       "django_migrations"."app",
       "django_migrations"."name",
       "django_migrations"."applied"
  FROM "django_migrations"

Execution time: 0.000735s [Database: default]

Django version 3.1.5, using settings 'proj.settings'
Development server is running at http://[<IP_ADDRESS>]:8000/
Using the Werkzeug debugger (http://werkzeug.pocoo.org/)
Quit the server with CONTROL-C.

When i then make requests to the view (that does some DB stuff) via curl, i don't see any SQL queries being printed

This problem was also mentioned on this issue

After some further investigation i found the cause. I had disable_existing_loggers set to True in my settings.LOGGING dict. I didn't realize that the print-sql relied on the Python logging framework. (tagging @markusmo in case it is still relevant for him)
Maybe this should be mentioned somewhere in the docs or print a warning message on startup.
Will leave it to the maintainers to classify if this is considered a bug; feel free to close the issue otherwise.


The server still running after calling (.stop ...).

Not reproducible, works as expected in tests and other my projects.


:palm_tree: Log as object

:rocket: deployed to http://connecting-to-services-pr-277.dev.c2s.nhschoices.net


HTML

HTML
User Story
As a bootcamp student
I want the prework notes to be structured on a webpage
so that I can easily find and read information
Aceptance Criteria
GIVEN a Prework Study Guide Website
WHEN I visit the website in my browser
THEN I see four boxes titled HTML, CSS, Git, JavaScript with associated notes listed

I would like to engage for the above mentioned acceptance criteria as I have required knowledge to both css and js to full fledged your requirements, looking forward to work for the same.


Thread Commissioning App compatibility

Opening this issue as part of the Wiki deprecation.
Currently, the public release of the Thread Commissioning App cannot be used for testing with OTBR.
This will eventually be noted in a Thread Commissioning guide using the OTBR Web UI, tracked in #62 . At that time we can close, or leave it open until we get the public release of the Thread Commissioning App updated.

Per #62, this should be fixed

Thanks for letting me know, I'll download and verify.

Confirmed that the update fixed this problem, closing.

Why Thread Commissioning App takes more time to add the new devices into the Thread network after scanned the QR code


Quick out-of-core downsampling to provide an overview of large data

As suggested in https://github.com/bokeh/datashader/issues/553, we need to improve our raster support so that it can access large rasters chunk by chunk.  This will let us work with raster datasets larger than system memory, just as we can currently work with larger-than-memory columnar Dask dataframes, and should make it very practical to work with a small, zoomed-in region of a very large raster dataset.
However, even if full resolution is needed only on deep zooms, very often it is not clear which region of the large dataset should be viewed at full resolution, until a zoomed-out overview of the data has been provided to the user.  And unfortunately, constructing such an overview using datashader will currently require making a complete pass through the entire dataset, reading all of the data into Python in order to aggregate it into a coarse grid.
Even if the Python code were to explicitly downsample the data, accessing only a strided subset of the data from disk, with most file formats and storage technologies the entire dataset will still end up being accessed.
After the above issue is addressed, it would be great if we could work on some specific combinations of aggregations and file formats where constructing such an overview would be relatively cheap. We could also consider making examples of having some pre-processed overview of the data stored with it, and then using HoloViews to switch dynamically between the overview and the full data depending on zoom level.

Note that I'm discussing raster data above, but the same issues apply to timeseries data, where a very long timeseries needs a quick overview that can be zoomed in to show the full data.

I am currently implementing something similar for our data. I came along #553 and then started working on this myself. So far I didn't find a way to wrap xarrays apply_ufunc or dask.map_blocks even though the latter would support ghosting which, as mentioned by @philippjfr, will probably be of importance for the sampling. The problem is that one needs to know the size of the processed data chunks and these will be chunk-dependent for non-symmetrically chunked data sets (i.e. an array with size 2055 along one axis, chunked into 1000,1000,55).
However, for the sampling methods that I am currently interested in: nearest neighbor upsampling and area mean downsampling, it seems that there is a satisfactory solution by using dask.delayed and manual creation of chunks. I addressed the issue of variable chunk sizes in unsymmetric datasets by instead dividing the plot canvas in equal chunks and map( as good as possible ) equal data chunks on these tiles.
My algorithms looks like this:
-1. data = dask.array.from_array(hdf5 file, chunks=(1000,1000))
0. preprocess xrange and yrange to match with data extent and resolution
#estimate number of plot tiles

xtiles = max(xrange // 2000,1) # something that fits good in memory

ytiles = max(yrange // 2000,1)

dask_delayed = [dask.delayed(resampling_function)( data[ith chunk in dim 1 : jth chunk in dim 2], plotwidth,plotheight, indicator of which tile (where in canvas and extents of tile) this data should be mapped to as (a function of i,j) ) for i,j in meshgrid (range(xtiles),range(ytiles))]

agg = dask.delayed(numpy.sum)(dask_delayed)

agg.compute(num_workers=4)

Inside the resampling_function, I initialize an array of zeros with the size of the plot canvas and fill one tile with the sampled array from gridtools.resample_2d. In the end when I sum over dask_delayed I end up with the complete agg. I am still testing the equivalence but so far it seems to work very well. On my laptop I can downsample more than 7 GByte in a few seconds.
In addition I added a cache of the full downsampled dataset in my plot class so that resetting to the full data extent, by far the biggest computation, is only performed once.

Thinking a little bit more about it, above works well for me without any chunk overlap because of the data (a matrix of probabilities). The values are of the same magnitude in their respective neighborhood and will converge to an area mean regardless of where exactly the split occurs.
For more heterogeneous data, I definitely expect some problems in the down-sampling process, although one can alter above algo to data [(ith + 1/2) chunk:(jth +1/ 2) chunk] to have some overlap. In the upsampling process, we are only dealing with one data chunk in a canvas with a reasonable size of w,h < 1000 pixel anyway and no overlap is needed.

Now that  #553 is done, and I've been able to successfully use that, this one comes to light again.  I find when trying to do a downsample and zoom it ends up with the wrong range during zoom.  Is there any tricks to using resample_2d that would help?  It seems like the above was a mechanism to solve 553.  I want to solve not having to have it ultimately read all the data.  I just want a very partial read of the data for a fast overview, but still have the zooming ranges work correctly.
I've done it brute force, constantly rereading, but would prefer some sort of mixed datashader mechanism, or recommendations on how to get to that.


Add missing third arg to define-obsolete-function-alias

These aliases were defined in 3b7b9e69d96933992b8174f48d3893412ceca54a,
before the 2.1.0 tag.

Thanks! Merged!

Thanks! Merged!


Introduce Veraison High Level Architecture

Currently Veraison Documentation needs to highlight a top level architecture daigram.
This issue tracks the need for architecture.

We need a high level design description with pics of the major components and their relationships. Plus sufficient explanatory text.


How to upload a file

How to upload a file?
like a png image?

Hi, attaching file upload docs:
https://zsa.vercel.app/docs/forms#file-upload

Can you please provide a complete example? It doesnt seem working.
Code:
createServerAction()
  .input(
    z.object({
      image: z.instanceof(File),
    }),
    {
      type: 'formData',
    },
  )
  .handler(async ({
    input: {
      image,
    },
  }) => {
      console.log({ image });
      const buffer = Buffer.from(await image.arrayBuffer());
      // custom method throwing error because buffer is empty
  });

Output:
{
  image: File {
    size: 0,
    type: 'application/octet-stream',
    name: 'undefined',
    lastModified:<PHONE_NUMBER>029
  }
}
Error: Input Buffer is empty


Cannot use dev mode with Playwright against production container

Could be associated with #26 , underlying problem is not the same.
We use container promotion and environment variable injection. Our process looks like this :

build app
containerize
inject TEST .env properties in container & test with playwright
promote to dev -> inject DEV .env properties and run in the DEV cloud
promote to prod -> inject PROD .env properties and run in the PROD cloud

Needs:

Be able to choose between OIDC / mock in local, test and DEV cloud environment
Be able to set "NODE_ENV" to whatever value we need and still respect the point above
Be able to switch OIDC/mock at cold start / runtime (not build time)
Not have code suggesting an unexpected behavior (eg: "devMode.enabled: true" on prod environment with devMode disabled)

Problems:

nuxt.config.ts is executed at build time, and valid for all environment. Hence the flag "oidc.devMode.enabled=true" will be present everywhere (bad readability)
process.env.NODE_ENV has to be "TEST" for some plugins, "E2E" for others and "development" for this plugin (bad reuse of not-owned property)

Proposed solution:

Get rid of the "oidc.devMode.enabled=true" that MAY NOT activate devMode

activate devMode on an owned env property. eg : "process.env.NUXT_OIDC_DEVMODE=true" or "process.env.NUXT_OIDC_MODE=mock"

stop mixing "dev" with "mock" as the two concepts are differents, albeit often used together. this is confusing on edge cases

BONUS : export DevModeConfig type to be imported in out nuxt.config.ts

Thanks for the extensive feedback.
Dev mode by the name was introduced for local development and testing, not for automated testing or mocking. It is not possible to mock a oidc provider in a way that is sufficient for testing, as every IdP is different and no one confirms to the OIDC standard 100%.
We will adjust the config filter to
!process.env.NODE_ENV.toLowerCase().startsWith('prod') && options.devMode?.enabled
Removing even more limitations from dev mode would increase the chance for the user to accidentally introduce security issues.
I would recommend to try to either mock it (not a good solution) or better introduce a low overhead oidc server or better the one you will use in production into your testing environment. Especially for E2E tests, mocks should be avoided and from a DevSecOps perspective, I would recommend to always use the proper oidc identity provider starting in dev, which should be possible for self hosted IdPs like Keycloak as well as all public cloud IdPs.
I am open to proposals or PR for a setup that supports automatic testing.


Preferred method of handling server error

We are using Ember Infinity for our infinite scrolling feed (loving it btw). One case we want to handle, however, is when there is a server error, and it returns a 404 JSON (or 500). We would like to gracefully fail, and show a message. I added a catch
return this.infinityModel('activity', params)
.catch(() => {

});

Which kind of works... I still get the error Uncaught Error: Property set failed: object in path "controller.model" could not be found or was destroyed. And the Loading Infinite Model... text is still displayed. I could ignore the error and have a class get rid of the text in this case, but I was wondering if there's a best way to handle this case. Thanks!

I did a bit more researching, and discovered that Ember has some error handling options from the route's model hook. https://guides.emberjs.com/v2.3.0/routing/loading-and-error-substates/
I just defined an error template and went from there.

nice!


switch to v2 clusters (declarative)

It would help out the clusters team if you can use v2 clusters -- those are the clusters under active development, so it's better to be dogfooding that.
This removes the spot=False b/c (1) that's the default anyway, and (2) v2 clusters don't support that argument quite yet.

Thanks for pointing this out @dchudz we are planning on eventually switching.
Couple of things:

At the moment in coiled=0.0.71  I can't do locally from coiled.v2 import Cluster and as you can see the CI is throwing the same error.
You are opening a PR from a fork, secrets are not supported for PR from forks.

Is there anything stopping us from upgrading so that we can get the newer Coiled versions?  Hopefully we don't have any inertia yet, and can remain nimble.

You are opening a PR from a fork, secrets are not supported for PR from forks.

That's okay, I'm fine closing this MR and letting you all make the switch. 😄
Btw I don't have rights to push to branches in this repo. Probably I'd like that at some point.

We can switch to declarative w/o solving the version issue by doing from coiled._beta import ClusterBeta as Cluster

Also, is there value for the platform team in us testing both the declarative and non-declarative (legacy? Coiled classic?) clusters?

Also, is there value for the platform team in us testing both the declarative and non-declarative (legacy? Coiled classic?) clusters?

Declarative only.  Future-or-bust!

Closing in favor of https://github.com/coiled/coiled-runtime/issues/35

thanks for taking this over!


Update billing-subscription-transfer.md

Added new functionality

Hi @adpick, I'm your friendly neighborhood Azure Pull Request Bot (You can call me AZPRBOT). Thanks for your contribution!

It looks like you're working at Microsoft (adpick). If you're full-time, we DON'T require a contribution license agreement.

If you are a vendor, DO please sign the electronic contribution license agreement. It will take 2 minutes and there's no faxing! https://cla.azure.com.

TTYL, AZPRBOT;

@adpick - thanks very much for your contribution!
@genlin - FYI. @adpick is a MSFT employee.


bug(linter): missing arm64-gnu oxlint build?

This happened when I ran npx oxlint@latest in one of my GH actions CI pipelines.

Your company has a arm64-gnu CI machine 👀 ?

That was run on a hosted github actions runner

Weird, the binary is here https://www.npmjs.com/package/@oxlint/linux-arm64-gnu

If it happens again I'll re open this.


Improve event manager

We need to think about the event manager that handles all events (keys, mouse, ...).
Then there should be two types (I guess):

Player (can be added later, like playing the player)
Ghost (this is the mode we can play around freely)

Those types should be able to handle the inputs and change their internal camera (#14 is blocker for this)

Done in #42


[sk] Add missing translations noted in todo

update todo.md

Thank you

Hey no problem, do you have any guidance how to work with capital_letters branch?
Do I rebase or merge my work from todo-sk and continue in capital_letters?


findNode based on id?

Is there a way to find a node based upon an arbitrary attribute value set in the node like, for instance, id?  I can't seem to do it.  I'd like to programmatically select a node based on id.
I'm trying to use it to track a hierarchy of locations, like "Room A->Gray Cabinet->Shelf 2" etc., but many of them will have similar names, which the search method uses, with different ids.

You need to iterate through getNodes()

Thanks for the tip.  Will try that.


Reset $SAFE to 0 for ruby 2.6

Before ruby 2.6, $SAFE was global to a thread, so setting it in a
separate thread would not affect main thread.
Since ruby 2.6, $SAFE is global to the process:
https://bugs.ruby-lang.org/issues/14250. This leads to unexpected
SecurityError occuring with ruby 2.6. The recommended approach is to
restore $SAFE to 0.
This should fix #304

Coverage increased (+0.005%) to 88.543% when pulling 85f9d8d0ed2d4f9c309b009af1b431d29c1330fb on hiptest:support-ruby-2-6-0-global-safe into f1a62a72ca08a0f707a83541414ff9d36c875c90 on technicalpickles:master.

@flajann2 Any thoughts on this PR?

I accept this. Sorry for the delay.

Thanks! Better late than never.
In the meantime we switched to juwelier. I made the same PR for the same issue. Can you merge it and make a release of juwelier please?


InputText: Dead key support and before key added observable

See forum discussion for details.

Yes, of course. Just wanted to wait until the PR had been reviewed.


TorEngine.get_page_source sends a NEWNYM signal to the control port

The TorEngine.get_page_source function sends a NEWNYM signal to the control port on every call. This is great for our use case where we want our ip to change frequently, but there are many use cases in which it is not so great. This should be configurable. I'd suggest creating a signaler class that can be passed to the TorEngine constructor.
# Every other GET sends a signal to the control port
eng = TorEngine(..., signaler = rasp.TorController(control_port, signal, 2), ...)
# No signals are sent
eng = TorEngine(..., signaler = None, ...)

Maybe this doesn't need to be a separate class, but can be just a number of GETs that are run before the signal is sent again.

Signaling after n iterations/gets is probably the simplest implementation of this issue.
We could also signal after n seconds elapse, I think that might be a slightly more appropriate move.
What exactly is the motivation for signaling for a new endpoint?  Do we think we're getting rate limited by certain sites?  Are we trying to pretend we're part of the regular non-scraping behavior so as to avoid detection at all?

We could also signal after n seconds elapse

You bring up a good point here. This makes me disagree with the following comment I made in the PR.

Maybe this doesn't need to be a separate class, but can be just a number of GETs that are run before the signal is sent again.

I think there will be times when we want to send the signal after n requests and times when we may want it to be timed. We could get real complex and send the signal only if n requests have been made in x time. So this makes me think we need a configurable class.

What exactly is the motivation for signaling for a new endpoint? Do we think we're getting rate limited by certain sites? Are we trying to pretend we're part of regular traffic so as to avoid detection at all?

All of the above 😄 . I was getting blocked in our anti-HT project and used this to avoid being blocked.

It may be as simple as allowing a pre-request callback, which could be anything, but in this case would be sending the signal.  User could mod time.time() and end up with a signal every N seconds, or maintain an instance variable counter for every N requests, which wouldn't necessarily play nice with the functional representation, but would be fine as-is.  The same mechanism would also work for the now-deprecated TimedWait selenium engine.

We could modify the N requests attribute at class level across multiple instances of the engine.  Not saying that's a great way to do it, but it is a way to do it.

Assigned to @baronvonbadguy

Would it be ridiculous to simply factor out all of the controller code from the engine, and have the user be responsible for the "when to signal" logic?  It seems like creating a connection to the controller is not something we should have with a functional rep of an engine method.

I think at the end of the day, once an engine is instantiated, whether it be a TorEngine, SeleniumEngine or DefaultEngine, it should look pretty much the same and be able to be used interchangeably.   So if there is some configuration/state that needs to be maintained to make a TorEngine just work, then that should happen at instantiation, not at get_page_source time.

So if we load the function into 10 green threads, will they bind the same TorController instance?  Which one closes the connection?

One approach for actual parallelism in an engine (which I haven't experimented with yet), would be to set up the configuration information at instantiation, but in the get_page_source catch an exception raised by not having a connection yet, and set up the connection at that time.   That way the as_func thing still works, each one having its own curried instance, but you have to rely on the os to clean up your connections.
Alternatively, we can give each worker a deep copy and they can each use the context manager interface.
Regardless I'd say that the assumption ought to be that workers in the crawlers each have their own instance of an engine, whether that is a semi-functional thingy or a class, tbd.  Either way, the goal should be that the crawlers just get passed in an object (function or class) and treat it the same no matter what.  The differences between them should be upstream, at engine instantiation/configuration if at all possible, not at runtime.

Say we wanted to go with the "n requests in x seconds".  Is that n requests across all workers?  How are we keeping track of all the requests between each worker?


Docs crossterm 5.0 not working.

The rust docs are not working for version 5.0

This will be fixed soon. #53 had fixed it.

This is fixed in the 0.5.1 release.


c++ clangd crash

Hello,
clangd server crashes in parsing some file.
Logs
From IDE
Traceback (most recent call last):
  File "/projects/Thirdparty/ycmd/third_party/bottle/bottle.py", line 868, in _handle
    return route.call(**args)
  File "/projects/Thirdparty/ycmd/third_party/bottle/bottle.py", line 1748, in wrapper
    rv = callback(*a, **ka)
  File "/projects/Thirdparty/ycmd/ycmd/watchdog_plugin.py", line 97, in wrapper
    return callback( *args, **kwargs )
  File "/projects/Thirdparty/ycmd/ycmd/hmac_plugin.py", line 62, in wrapper
    body = callback( *args, **kwargs )
  File "/projects/Thirdparty/ycmd/ycmd/handlers.py", line 122, in GetCompletions
    completions = filetype_completer.ComputeCandidates( request_data )
  File "/projects/Thirdparty/ycmd/ycmd/completers/cpp/clangd_completer.py", line 335, in ComputeCandidates
    return super().ComputeCandidates( request_data )
  File "/projects/Thirdparty/ycmd/ycmd/completers/completer.py", line 286, in ComputeCandidates
    candidates = self._GetCandidatesFromSubclass( request_data )
  File "/projects/Thirdparty/ycmd/ycmd/completers/language_server/language_server_completer.py", line 1281, in _GetCandidatesFromSubclass
    codepoint )
  File "/projects/Thirdparty/ycmd/ycmd/completers/language_server/language_server_completer.py", line 1247, in ComputeCandidatesInner
    REQUEST_TIMEOUT_COMPLETION )
  File "/projects/Thirdparty/ycmd/ycmd/completers/language_server/language_server_completer.py", line 437, in GetResponse
    response = self.GetResponseAsync( request_id, message )
  File "/projects/Thirdparty/ycmd/ycmd/completers/language_server/language_server_completer.py", line 430, in GetResponseAsync
    self.WriteData( message )
  File "/projects/Thirdparty/ycmd/ycmd/completers/language_server/language_server_completer.py", line 725, in WriteData
    self._server_stdin.write( data )
ValueError: write to closed file

Stack trace:
[08:55:30.916] Code complete: sema context MacroNameUse, query scopes [] (AnyScope=true), expected type <none>
 #0 0x000000000053e0da llvm::sys::PrintStackTrace(llvm::raw_ostream&) (/projects/Thirdparty/ycmd/third_party/clangd/output/bin/clangd+0x53e0da)
 #1 0x000000000053be1c llvm::sys::RunSignalHandlers() (/projects/Thirdparty/ycmd/third_party/clangd/output/bin/clangd+0x53be1c)
 #2 0x000000000053bf83 SignalHandler(int) (/projects/Thirdparty/ycmd/third_party/clangd/output/bin/clangd+0x53bf83)
 #3 0x00007f469c35cb20 __restore_rt (/lib64/libpthread.so.0+0x14b20)
 #4 0x00000000006e9f50 clang::RawComment::RawComment(clang::SourceManager const&, clang::SourceRange, clang::CommentOptions const&, bool) (/projects/Thirdparty/ycmd/third_party/clangd/output/bin/clangd+0x6e9f50)
 #5 0x00000000012caf76 clang::Sema::ActOnComment(clang::SourceRange) (/projects/Thirdparty/ycmd/third_party/clangd/output/bin/clangd+0x12caf76)
 #6 0x00000000010bcf30 (anonymous namespace)::ActionCommentHandler::HandleComment(clang::Preprocessor&, clang::SourceRange) (/projects/Thirdparty/ycmd/third_party/clangd/output/bin/clangd+0x10bcf30)
 #7 0x00000000008faca7 clang::Preprocessor::HandleComment(clang::Token&, clang::SourceRange) (/projects/Thirdparty/ycmd/third_party/clangd/output/bin/clangd+0x8faca7)
 #8 0x00000000008ad127 clang::Lexer::SkipBlockComment(clang::Token&, char const*, bool&) (/projects/Thirdparty/ycmd/third_party/clangd/output/bin/clangd+0x8ad127)
 #9 0x00000000008b1ee6 clang::Lexer::LexTokenInternal(clang::Token&, bool) (/projects/Thirdparty/ycmd/third_party/clangd/output/bin/clangd+0x8b1ee6)
#10 0x00000000008f9cbf clang::Preprocessor::Lex(clang::Token&) (/projects/Thirdparty/ycmd/third_party/clangd/output/bin/clangd+0x8f9cbf)
#11 0x00000000008c0294 clang::Preprocessor::CheckEndOfDirective(char const*, bool) (/projects/Thirdparty/ycmd/third_party/clangd/output/bin/clangd+0x8c0294)
#12 0x00000000008c0956 clang::Preprocessor::SkipExcludedConditionalBlock(clang::SourceLocation, clang::SourceLocation, bool, bool, clang::SourceLocation) (/projects/Thirdparty/ycmd/third_party/clangd/output/bin/clangd+0x8c0956)
#13 0x00000000008cae21 clang::Preprocessor::HandleIfdefDirective(clang::Token&, clang::Token const&, bool, bool) (/projects/Thirdparty/ycmd/third_party/clangd/output/bin/clangd+0x8cae21)
#14 0x00000000008cc176 clang::Preprocessor::HandleDirective(clang::Token&) (/projects/Thirdparty/ycmd/third_party/clangd/output/bin/clangd+0x8cc176)
#15 0x00000000008b2208 clang::Lexer::LexTokenInternal(clang::Token&, bool) (/projects/Thirdparty/ycmd/third_party/clangd/output/bin/clangd+0x8b2208)
#16 0x00000000008f9cbf clang::Preprocessor::Lex(clang::Token&) (/projects/Thirdparty/ycmd/third_party/clangd/output/bin/clangd+0x8f9cbf)
#17 0x00000000010bccbb clang::ParseAST(clang::Sema&, bool, bool) (/projects/Thirdparty/ycmd/third_party/clangd/output/bin/clangd+0x10bccbb)
#18 0x0000000000f3cb31 clang::FrontendAction::Execute() (/projects/Thirdparty/ycmd/third_party/clangd/output/bin/clangd+0xf3cb31)
#19 0x00000000009a3252 clang::clangd::(anonymous namespace)::semaCodeComplete(std::unique_ptr<clang::CodeCompleteConsumer, std::default_delete<clang::CodeCompleteConsumer> >, clang::CodeCompleteOptions const&, clang::clangd::(anonymous namespace)::SemaCompleteInput const&, clang::clangd::IncludeStructure*) (/projects/Thirdparty/ycmd/third_party/clangd/output/bin/clangd+0x9a3252)
#20 0x00000000009af38e clang::clangd::codeComplete(llvm::StringRef, clang::tooling::CompileCommand const&, clang::clangd::PreambleData const*, llvm::StringRef, clang::clangd::Position, llvm::IntrusiveRefCntPtr<llvm::vfs::FileSystem>, clang::clangd::CodeCompleteOptions, clang::clangd::SpeculativeFuzzyFind*) (/projects/Thirdparty/ycmd/third_party/clangd/output/bin/clangd+0x9af38e)
#21 0x0000000000991d73 clang::clangd::ClangdServer::codeComplete(llvm::StringRef, clang::clangd::Position, clang::clangd::CodeCompleteOptions const&, llvm::unique_function<void (llvm::Expected<clang::clangd::CodeCompleteResult>)>)::'lambda'(llvm::Expected<clang::clangd::InputsAndPreamble>)::operator()(llvm::Expected<clang::clangd::InputsAndPreamble>) (/projects/Thirdparty/ycmd/third_party/clangd/output/bin/clangd+0x991d73)

System information
Output of clangd --version:
clangd version 10.0.0 (https://github.com/ycm-core/llvm 038587147cf2f97d1c3e677042f69560c65b5bea)

Editor/LSP plugin: emacs/ycmd-core
Operating system: fedora 31

I beleive this has been fixed in the meantime, could you try with release candidate 2 from https://prereleases.llvm.org/11.0.0/ ?
If the crash is still happening we'll need the code for the file you are working on (possibly a minimized version) to repro.

Ok, I will try to provide either the input file or try the clang 11

the crash stack looks like similar to #332

Ok, I will try to provide either the input file or try the clang 11

You know how it is, when you add debug symbols and increase the log severity the crash doesn't appear :-)

so are you saying that you were able to reproduce with clangd-11 in release configuration but cannot repro with a debug binary?
or have you just built a clangd from head and it doesn't repro ?

so are you saying that you were able to reproduce with clangd-11 in release configuration but cannot repro with a debug binary?
or have you just built a clangd from head and it doesn't repro ?

Sorry for the confusing message :-)
Rebuild with debug symbol  and increased the log severity but I can't reproduce the problem, so as to provide the input file the produces the problem.
No luck with the clangd-11 so far.


NODE-84, chore: web3_clientVersion response format

Description

Update web3_clientVersion's response format into geth style.
Before

After

Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] Something else (simple changes that are not related to existing functionality or others)

Checklist

[ ] I have selected the correct base branch.
[ ] I have performed a self-review of my own code.
[ ] I have made corresponding changes to the documentation.
[ ] I have made new test codes regarding to my changes.
[ ] I have no personal secrets or credentials described on my changes.
[ ] I have run cargo-clippy  and linted my code.
[ ] My changes generate no new warnings.
[ ] My changes passed the existing test codes.
[ ] My changes are able to compile.

bifrost-node 프로젝트 적용도 부탁드릴게요


sdk: add FilterOptions

Closes #119

I experimented with a different approach: https://github.com/rust-nostr/nostr/pull/129 . I tested all 3 branches and they work.
What do you think?

On second thought, your new version is actually simpler. I closed my PR.

I found a bug in your version:
timeout doesn't just mean "timeout to EOSE", it means "timeout until function returns".
So calling it with

timeout of Duration::from_secs(1) and
FilterOptions::WaitDurationAfterEOSE(Duration::from_secs(5))

will return after 1 second with a timeout (even though EOSE came on time).

Yes, the timeout should be intended as "timeout until function returns".
The WaitDurationAfterEOSE should be executed outside the timeout?

IMO the simpler approach is better:

timeout refers to "timeout until EOSE" (could be renamed to better indicate that)
WaitDurationAfterEOSE is completely separate and up to the caller

I see two big reasons for this:

It's backward compatible, so people who used timeout in the "timeout to EOSE" sense so far, will not be confused or surprised by a change in the meaning.
After EOSE, there's no way to tell when a query "times out" (resulting in Err), or when the WaitDurationAfterEOSE was waited as per the filter option (success case, resulting in Ok).

Tested all 3 versions, with different timeout combinations, all work :+1:


Kaggle Notebook?

Kaggle offers a free 16gb VRam GPU / TPU for 20-30 hours per week
It would be really nice to have a Metavoice notebook for it, I tried to import the Google Colab notebook into Kaggle but it kept throwing errors...
Can anyone make a notebook for it? thanks!

Hi

#Cloning the repo
!git clone -b vatsal/make_2_5x_faster https://github.com/metavoiceio/metavoice-src.git
%cd metavoice-src
Install dependencies
!pip install -r requirements.txt
!pip install --upgrade torch torchaudio
!pip install -e .
Loading Text-to-Speech model --Metavoice
from fam.llm.fast_inference import TTS
tts = TTS()
response = "This is the demo for Metavoice TTS with voice cloning"
wav_file = tts.synthesise(
text=response,
spk_ref_path="/kaggle/input/sample.mp3"
)
print(f"Response generated:/n{display(Audio(wav_file, autoplay=True))}")
The above code is working properly in Kaggle notebook


Fixed Example app on swift 3

Fixes #123

Codecov Report

Merging #124 into swift3 will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           swift3     #124   +/-   ##
=======================================
  Coverage   93.06%   93.06%
=======================================
  Files          38       38
  Lines        3043     3043
=======================================
  Hits         2832     2832
  Misses        211      211

Continue to review full report at Codecov.

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


How to add an existing AWS Lambda function to a amplify project?

Which Category is your question related to?
API
Amplify CLI Version
4.19.0
Is there a way to add an existing AWS Lambda function to a amplify project?

Hi @sakhmedbayev
Currently ampify cli doesnt support integration with  existing resources. There is RFC for this  : https://github.com/aws-amplify/amplify-cli/issues/3977. You can comment or update on this RFC to support your usecase and track the status.
If you use case is to add existing lambda function to you graphql api, you can check here
I am closing this issue for now, but feel free to comment and I can again reopen it.


TypeError: Cannot read property 'slice' of undefined: How to use it in browser (angular) ?

I am trying to use it in an angular app, but always got problems
core.js:4002 ERROR Error: Uncaught (in promise): TypeError: Cannot read property 'slice' of undefined
TypeError: Cannot read property 'slice' of undefined
    at Object../node_modules/readable-stream/lib/_stream_writable.js

I'm not familiar with angular and which bundler you are using. If you can share a reproducible example, you might get more help.

@maroodb  I have exactly the same problem

i have the same issue. Please advise


Updating Migration class code snippet

It's not clear in the example what the constructor needs to be or that super.onPreMigrate needs to be called in the code snippet
I ran into this issue while creating my first migration and saw several other people throughout the Issues page that had similar complaints.

@danielrees18 Thanks for the contribution. For the DBFlow 3.0 release we hope to improve not only the documentation, but many aspects of the library. It will be a huge release and hopefully will be out by mid October. If this PR is not address in 3.0, it will be a priority after release. More on that here. Please let me know if you have any questions Daniel.

no longer valid. onPreMigrate is no longer needed to be called by most Migration except IndexMigration where that has the support lib annotation @CallSuper in place.


More test coverage

If I'm not mistaken, there's three uncovered lines?
Forest of trees without persisting is not covered:
https://github.com/ESM-VFC/xoak/blob/3a188ad5bea877370b80f3fa4fb4545a321fafe9/src/xoak/accessor.py#L73
Query with pure numpy arrays not tested:
https://github.com/ESM-VFC/xoak/blob/3a188ad5bea877370b80f3fa4fb4545a321fafe9/src/xoak/accessor.py#L151
And query against a single index tree is not tested:
https://github.com/ESM-VFC/xoak/blob/3a188ad5bea877370b80f3fa4fb4545a321fafe9/src/xoak/accessor.py#L154

Yes those are important lines. A single array_lib fixture used for both the dataset and the indexer was not enough to test those cases, so I created two separate fixtures: one for the dataset and the other for the indexer. As a result, the number of parametrized tests is (unnecessarily) blowing up, but that's still fast so it's fine for now I think.


Fixes:#986-scholarship page enhancement.

Issues Identification
Closes: #986
Description
This PR make sure that this page Enhances the Scholarship page,
Types of Changes
Please check the boxes that apply

[ ] Bugfix (non-breaking change that fixes an issue)
[x] New feature (non-breaking change that adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation update (Documentation content changed)
[x] Other (please describe):

Checklist
Please check the boxes that apply

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] My changes do not break the current system and pass all existing test cases
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Screenshots

@aditya-bhaumik added correct path as well.

there is no navbar or footer in any of the pages

@aditya-bhaumik could u please merge and verify

read my message once

i have checked the deployment

Ok give me time I will create new pull request.


Implement API `api/envs/default/apps/

implement API `api/envs/default/apps/ and refactor code

Please ignore failure of build step Install OAM runtime and prepare WorkloadDefinitions/TraitDefinitions, I will fix it after https://github.com/cloud-native-application/RudrX/pull/132 is merged. Thanks.

@ryanzhang-oss I like your integration test framework very much. But it will take me some time to have it passed as some fundamental apis like env create, system init needed to be implemented first.
And will you consider move it to https://github.com/cloud-native-application/RudrX/tree/master/e2e and named a folder apiserver to cover all api server test cases?


fixing potential null issue with optional param being parsed as a script

Description:
set_level is optional but the code is passing a potential None object into the Script constructor causing issues.
Related issue (if applicable): fixes #7929

Fixed that for you ;-)