Breakpoints disappear after debug starts, can be hit, but not highlighted

Issue Description
Breakpoints not sticking in editor or gutter after debug starts. Breakpoints are hit, but line is not highlighted in editor, and variables are not loaded. I can see variables loaded on sidebar, but not on editor on hover. I can add breakpoints after debug starts, but they don't show on gutter, though it shows as registered on sidebar. Please advise on what information is needed to identify the problem. It used to work fine.
Steps to Reproduce
Expected Behavior
Actual Behavior
Logs
OmniSharp log
Post the output from Output-->OmniSharp log here
C# log
Post the output from Output-->C# here
Environment information
VSCode version: 1.49.1
C# Extension: 1.23.2
Mono Information
        OmniSharp using built-in mono
Dotnet Information
.NET Core SDK (reflecting any global.json):
 Version:   3.1.102
 Commit:    573d158fea
Runtime Environment:
OS Name:     Mac OS X
OS Version:  10.15
OS Platform: Darwin
RID:         osx.10.15-x64
Base Path:   /usr/local/share/dotnet/sdk/3.1.102/
Host (useful for support):
Version: 3.1.2
Commit:  916b5cba26
.NET Core SDKs installed:
2.1.4 [/usr/local/share/dotnet/sdk]
2.1.302 [/usr/local/share/dotnet/sdk]
2.2.402 [/usr/local/share/dotnet/sdk]
3.1.102 [/usr/local/share/dotnet/sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.All 2.1.2 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.All]
Microsoft.AspNetCore.All 2.2.7 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.All]
Microsoft.AspNetCore.App 2.1.2 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 2.2.7 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.AspNetCore.App 3.1.2 [/usr/local/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 2.0.5 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.2 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 2.1.16 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.7 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 2.2.8 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
Microsoft.NETCore.App 3.1.2 [/usr/local/share/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download

Visual Studio Code Extensions

Extension
Author
Version

csharp
ms-dotnettools
1.23.2

csharp-to-typescript
adrianwilczynski
1.12.1

csharpextensions
jchannon
1.3.1

gitlens
eamodio
10.2.2

rest-client
humao
0.24.2

sftp
liximomo
1.12.9

todo-tree
Gruntfuggly
0.0.178

vscode-nuget-gallery
patcx
0.0.22

vscode-nuget-package-manager
jmrog
1.1.6

duplicate of https://github.com/OmniSharp/omnisharp-vscode/issues/3920


Java SDK : Account Transaction - Update Contract

Closed as of of https://github.com/Concordium/concordium-java-sdk/pull/146


Datasets modularization pt.5

Feature or Bugfix

Refactoring

Detail
Refactoring of the Dataset entity and related to it code.
Refactoring for Votes
Introduced DataPolicy (the same way as ServicePolicy was used used)
Extracted dataset related permissions.
Used new has_tenant_permission instead of has_tenant_perm that allows not to pass unused parameters
Relates
#412 and #295
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Added a new commits:
Most of them were review remarks, but I also returned triggering the alarms as we discussed (+ added a line to trigger alarm not only create a message) @dlpzx
Extracted DatasetRole (kudos to @dbalintx for noticing it)
Created a way to extend EnvironmentSetup (which is an environment stack) and extracted glue profiler since it looks related to datasets. I didn't do that for the others likelakeformationdefaultsettings and gluedatabasecustomresource since wasn't sure if there are only dataset-specific.


SPIKE: Technology upgrade to Angular 7

Child of #556
As part of this spike, we need to determine the overall Pros and Cons of upgrading to Angular 7, so that there are less challenges in the future.
Along with this, a thorough analysis on the peripheral technologies to be used with Angular 7 should be.
A decision log should be maintained for the same, so that it can be referenced in the future if needed.

Features of angular js:-
1).  CLI Prompts:- Added new feature for CLI will prompt users while typing common commands like ng-add or ng-new.
2). Performance:- Angular team discovered blemish that Angular developer were including the reflect-metadata polyfill in production, which is only needed in development, In order to fix this, part of the update to v7 will automatically remove it from your polyfills.ts file, and then include it as a build step when building your application in JIT mode, removing this polyfill from production builds by default.
3).To speed up the performance new applications will warn when the initial bundle is more than 2MB and will error at 5MB which user can modify it in angular.json file. These budgets align with warnings that can be shown to users taking advantage of Chrome’s Data Saver features.
4). New features:- Angular 7 features visual improvements in Material Design which received a major update in 2018, refresh as well as virtual scrolling, for dynamically loading and unloading parts of the DOM to build high-performing, large lists of data. Also, applications can be fitted with a drag-and-drop capability by importing the DragDropModule or the ScrollingModule
5). Angular Do-Bootstrap:- It's used for bootstrapping modules that need to bootstrap a component. Angular 7 added a new life-cycle hook (ngDoBootstrap) and interface (DoBootstrap).
6).New ng-compiler :- provides an accelerated eight-phase compilation and reduction of large app size approximately 2 times.
7).Splitting of @angular/core:- One of the disadvantages of Angular is its total multipurposeness. It’s a large framework itself automatically provides modules which you probably don’t need, thus team Angular has split @angular/core past the boundaries presented no less than 418 modules.
Source:- https://www.angularminds.com/blog/article/top-10-features-of-angular-7.html


error with Gemini::geminiProVision()

Gemini 1.0 Pro Vision has been deprecated on July 12, 2024. Consider switching to different model, for example gemini-1.5-flash.

After inspecting the code, you can use this method to select a specific model instead of using the others.
$model = Gemini::generativeModel('models/gemini-1.5-flash');
$response = $model->generate(...);

I just released a new version.
Pro vision usage marked as deprecated. Also added geminiFlash method.
You can also use any model you want without depending on enums with the following method.
$client->generativeModel(model: 'models/gemini-1.5-flash-001')


Add int and CSRMatrix support for the distributed runtime

In GitLab by @aristotelis96 on Feb 26, 2022, 12:44
Distributed runtime currently works only with DenseMatrix<double>. We need to add support for:

integers
CSRMatrix (both double and integers)

I am reopening this issue. PR #428 provided CSRMatrix (and other value types) support for the distributed gRPC worker, but the coordinator still only supports DenseMatrix<double>. It will probably be easier and more straightforward to address this once #103 is resolved.


Create const list of supported spirv ops, including glsl ops

Right now there are tests for ops, but no guarantee that all ops are tested. These const lists will serve as the source of truth for which ops are actually supported, and there should be a test that makes sure all of these ops are tested.

This is obsolete now as we've moved to precompiled shaders directly to a host language (SkSL, MSL for Impeller on iOS, et cetera).


Brigade integration tests

addresses #87
depends on #82

Update on running kind in a Brigade job - there is now a PR on Brigade that allows us to mount the volumes necessary for kind to run in a Kubernetes pod.
To enable it for this project, we need to:

set the custom worker tag for the project
make sure project allows privileged jobs and host mounts
actually update the integration test pipeline to first start the kind cluster.

I can update the last point, but I'll have to ping @vdice for the first two.

Removing the "Draft" status to trigger Azure Pipelines builds.


Create cli and samples package

Resolves #419
Quite a large change set this one:

introduces caliper-cli that can be used to run a benchmark, start/stop a zoo service, start a zoo client
renames caliper-application to caliper-samples
strips caliper-samples down to only containing sample networks and their configuration details
removes custom-domain networks from the samples
adds a /scripts folder for help scripts that don't yet have a home
introduces caliper-tests-integration that runs an integration test, which performs the following:

stand up verdaccio server (local npm proxy)
publish all packages to proxy
npm install from proxy
execute caliper run benchmark command using samples package

Modifies travis build to:

run npm test across all packages
run integration test for composer and fabric-ccp adaptors

Addition of Readme's

... I think that's it 😂
A separate issue should be raised for converting the benchmark runner to use config settings
Signed-off-by<EMAIL_ADDRESS><EMAIL_ADDRESS>

thanks for the review - changes made 👍


main package now requires skipLibCheck=true

Hi @CGNonofr
because the main because is now only dependent on monaco-editor the typescript compilation now only succeeds with skipLibCheck=true.
I have reproduced this on two branches with the Angular example repo:
With lib checking enabled:
https://github.com/TypeFox/monaco-languageclient-ng-example/actions/runs/6422702376/job/17439750585
With lib checking disabled:
https://github.com/TypeFox/monaco-languageclient-ng-example/actions/runs/6422712538/job/17439771153
It is the same behaviour with monaco-languageclient. With the latest commit on main I globally enabled lib checking, but disabled it where it is required (packages client, examples and verify/webpack).
The problematic code/definitions are terminal related things and xterm related dependencies. Do you have a good idea how to fix this?

Sorry, corrected the title. Why isn't it called enableLibCheck? 😅

I'm surprised, typescript also checks code that is not used at all?

I'm surprised, typescript also checks code that is not used at all?

It must end up in the code-graph somehow. There must be some erroneous import or so somewhere, because otherwise this problem would not be constraint to the terminal.

I'm surprised, typescript also checks code that is not used at all?

It must end up in the code-graph somehow. There must be some erroneous import or so somewhere, because otherwise this problem would not be constraint to the terminal.

indeed: services.d.ts => vscode/src/vs/workbench/contrib/terminal/browser/terminal.d.ts => vscode/src/vs/platform/terminal/common/capabilities/capabilities.d.ts => vscode/src/vs/platform/terminal/common/capabilities/commandDetectionCapability.d.ts => xterm-headless
Not sure how to handle it!
One way is to stop exporting all services identifiers from there but it will be a breaking change


Upgrade Rust Version

[ ] Update to the most recent Rust nightly
[ ] Set recurring task to do this every 3 months

Isn't that a duplicate of #19?

If that's what's supposed to happen there? The title says something else. In any case we are on a 6+ month old version now and have to update. Feel free to close this and change #19.


[Bug]: crash on start

zot version
v2.0.3-0-g819994c
Describe the bug
Crash on start with trivy scan enabled.
I've got about 14GB of publicly available images only from various mirrors.
To reproduce

Configuration
/etc/zot/config.json

{
  "distSpecVersion": "1.1.0",
  "storage": {
    "dedupe": true,
    "gc": true,
    "gcDelay": "1h",
    "gcInterval": "2h",
    "rootDirectory": "/tank/zot"
  },
  "http": {
    "address": "<IP_ADDRESS>",
    "port": "5000"
  },
  "log": {
    "level": "debug",
    "output": "/var/log/zot/zot.log",
    "audit": "/var/log/zot/audit.log"
  },
  "extensions": {
    "ui": {
      "enable": true
    },
    "search": {
      "enable": true,
      "cve": {
        "updateInterval": "168h"
      }
    },
    "metrics": {
      "enable": true,
      "prometheus": {
        "path": "/metrics"
      }
    },
    "mgmt": {
      "enable": true
    },
    "scrub": {
      "enable": false,
      "interval": "24h"
    },
    "sync": {
      "enable": true,
      "registries": [
        {
          "urls": [
            "https://index.docker.io"
          ],
          "content": [
            {
              "prefix": "**",
              "destination": "/docker.io"
            }
          ],
          "onDemand": true,
          "tlsVerify": true,
          "maxRetries": 3,
          "retryDelay": "15m"
        },
        {
          "urls": [
            "https://gcr.io"
          ],
          "content": [
            {
              "prefix": "**",
              "destination": "/gcr.io"
            }
          ],
          "onDemand": true,
          "tlsVerify": true
        },
        {
          "urls": [
            "https://ghcr.io"
          ],
          "content": [
            {
              "prefix": "**",
              "destination": "/ghcr.io"
            }
          ],
          "onDemand": true,
          "tlsVerify": true
        },
        {
          "urls": [
            "https://k8s.gcr.io"
          ],
          "content": [
            {
              "prefix": "**",
              "destination": "/k8s.gcr.io"
            }
          ],
          "onDemand": true,
          "tlsVerify": true
        },
        {
          "urls": [
            "https://nvcr.io"
          ],
          "content": [
            {
              "prefix": "**",
              "destination": "/nvcr.io"
            }
          ],
          "onDemand": true,
          "tlsVerify": true
        },
        {
          "urls": [
            "https://quay.io"
          ],
          "content": [
            {
              "prefix": "**",
              "destination": "/quay.io"
            }
          ],
          "onDemand": true,
          "tlsVerify": true
        },
        {
          "urls": [
            "https://registry.gitlab.com"
          ],
          "content": [
            {
              "prefix": "**",
              "destination": "/registry.gitlab.com"
            }
          ],
          "onDemand": true,
          "tlsVerify": true
        },
        {
          "urls": [
            "https://registry.k8s.io"
          ],
          "content": [
            {
              "prefix": "**",
              "destination": "/registry.k8s.io"
            }
          ],
          "onDemand": true,
          "tlsVerify": true
        },
        {
          "urls": [
            "https://public.ecr.aws"
          ],
          "content": [
            {
              "prefix": "**",
              "destination": "/public.ecr.aws"
            }
          ],
          "onDemand": true,
          "tlsVerify": true
        }
      ]
    }
  }
}

Client tool used

Seen error
sudo -u zot zot serve /etc/zot/config.json

2024-04-22T23:02:27.143+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.145+0200	INFO	Number of language-specific files: 0
2024-04-22T23:02:27.186+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.186+0200	INFO	Number of language-specific files: 0
2024-04-22T23:02:27.196+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.197+0200	INFO	Number of language-specific files: 0
2024-04-22T23:02:27.206+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.207+0200	INFO	Number of language-specific files: 0
2024-04-22T23:02:27.228+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.229+0200	INFO	Number of language-specific files: 0
2024-04-22T23:02:27.248+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.249+0200	INFO	Number of language-specific files: 0
2024-04-22T23:02:27.257+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.258+0200	INFO	Number of language-specific files: 0
2024-04-22T23:02:27.266+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.273+0200	INFO	Detected OS: alpine
2024-04-22T23:02:27.273+0200	INFO	Detecting Alpine vulnerabilities...
2024-04-22T23:02:27.274+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:27.274+0200	INFO	Detecting node-pkg vulnerabilities...
2024-04-22T23:02:27.290+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.291+0200	INFO	Number of language-specific files: 0
2024-04-22T23:02:27.299+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.300+0200	INFO	Number of language-specific files: 0
2024-04-22T23:02:27.307+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.312+0200	INFO	Detected OS: alpine
2024-04-22T23:02:27.312+0200	INFO	Detecting Alpine vulnerabilities...
2024-04-22T23:02:27.313+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:27.313+0200	INFO	Detecting node-pkg vulnerabilities...
2024-04-22T23:02:27.328+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.334+0200	INFO	Detected OS: alpine
2024-04-22T23:02:27.334+0200	INFO	Detecting Alpine vulnerabilities...
2024-04-22T23:02:27.335+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:27.335+0200	INFO	Detecting node-pkg vulnerabilities...
2024-04-22T23:02:27.350+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.356+0200	INFO	Detected OS: alpine
2024-04-22T23:02:27.356+0200	INFO	Detecting Alpine vulnerabilities...
2024-04-22T23:02:27.359+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:27.359+0200	INFO	Detecting node-pkg vulnerabilities...
2024-04-22T23:02:27.376+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.383+0200	INFO	Detected OS: alpine
2024-04-22T23:02:27.383+0200	INFO	Detecting Alpine vulnerabilities...
2024-04-22T23:02:27.384+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:27.384+0200	INFO	Detecting node-pkg vulnerabilities...
2024-04-22T23:02:27.396+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.406+0200	INFO	Detected OS: alpine
2024-04-22T23:02:27.406+0200	INFO	Detecting Alpine vulnerabilities...
2024-04-22T23:02:27.407+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:27.407+0200	INFO	Detecting node-pkg vulnerabilities...
2024-04-22T23:02:27.448+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.449+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:27.449+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:27.460+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.461+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:27.461+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:27.474+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.475+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:27.475+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:27.491+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.493+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:27.493+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:27.513+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.514+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:27.514+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:27.547+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.564+0200	INFO	Detected OS: debian
2024-04-22T23:02:27.564+0200	INFO	Detecting Debian vulnerabilities...
2024-04-22T23:02:27.579+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:27.579+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:27.627+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.637+0200	INFO	Detected OS: alpine
2024-04-22T23:02:27.637+0200	INFO	Detecting Alpine vulnerabilities...
2024-04-22T23:02:27.642+0200	INFO	Number of language-specific files: 2
2024-04-22T23:02:27.642+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:27.652+0200	WARN	This OS version is no longer supported by the distribution: alpine 3.15.8
2024-04-22T23:02:27.652+0200	WARN	The vulnerability detection may be insufficient because security updates are not provided
2024-04-22T23:02:27.673+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.684+0200	INFO	Detected OS: alpine
2024-04-22T23:02:27.684+0200	INFO	Detecting Alpine vulnerabilities...
2024-04-22T23:02:27.688+0200	INFO	Number of language-specific files: 2
2024-04-22T23:02:27.688+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:27.698+0200	WARN	This OS version is no longer supported by the distribution: alpine 3.15.8
2024-04-22T23:02:27.698+0200	WARN	The vulnerability detection may be insufficient because security updates are not provided
2024-04-22T23:02:27.717+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.736+0200	INFO	Detected OS: debian
2024-04-22T23:02:27.736+0200	INFO	Detecting Debian vulnerabilities...
2024-04-22T23:02:27.750+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:27.750+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:27.773+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.777+0200	INFO	Detected OS: alpine
2024-04-22T23:02:27.777+0200	INFO	Detecting Alpine vulnerabilities...
2024-04-22T23:02:27.778+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:27.778+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:27.801+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.813+0200	INFO	Detected OS: alpine
2024-04-22T23:02:27.813+0200	INFO	Detecting Alpine vulnerabilities...
2024-04-22T23:02:27.815+0200	INFO	Number of language-specific files: 2
2024-04-22T23:02:27.815+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:27.827+0200	WARN	This OS version is no longer supported by the distribution: alpine 3.15.8
2024-04-22T23:02:27.827+0200	WARN	The vulnerability detection may be insufficient because security updates are not provided
2024-04-22T23:02:27.842+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.868+0200	INFO	Detected OS: debian
2024-04-22T23:02:27.868+0200	INFO	Detecting Debian vulnerabilities...
2024-04-22T23:02:27.889+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:27.889+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:27.915+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.920+0200	INFO	Detected OS: alpine
2024-04-22T23:02:27.920+0200	INFO	Detecting Alpine vulnerabilities...
2024-04-22T23:02:27.922+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:27.922+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:27.937+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.940+0200	INFO	Detected OS: alpine
2024-04-22T23:02:27.940+0200	INFO	Detecting Alpine vulnerabilities...
2024-04-22T23:02:27.941+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:27.941+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:27.958+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:27.975+0200	INFO	Detected OS: debian
2024-04-22T23:02:27.976+0200	INFO	Detecting Debian vulnerabilities...
2024-04-22T23:02:27.991+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:27.991+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:28.023+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:28.040+0200	INFO	Detected OS: debian
2024-04-22T23:02:28.040+0200	INFO	Detecting Debian vulnerabilities...
2024-04-22T23:02:28.056+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:28.057+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:28.076+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:28.081+0200	INFO	Detected OS: alpine
2024-04-22T23:02:28.081+0200	INFO	Detecting Alpine vulnerabilities...
2024-04-22T23:02:28.082+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:28.082+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:28.097+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:28.103+0200	INFO	Detected OS: alpine
2024-04-22T23:02:28.103+0200	INFO	Detecting Alpine vulnerabilities...
2024-04-22T23:02:28.104+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:28.104+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:28.118+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:28.130+0200	INFO	Detected OS: debian
2024-04-22T23:02:28.130+0200	INFO	Detecting Debian vulnerabilities...
2024-04-22T23:02:28.137+0200	INFO	Number of language-specific files: 0
2024-04-22T23:02:28.175+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:28.193+0200	INFO	Detected OS: debian
2024-04-22T23:02:28.193+0200	INFO	Detecting Debian vulnerabilities...
2024-04-22T23:02:28.210+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:28.210+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:28.233+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:28.234+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:28.234+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:28.248+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:28.266+0200	INFO	Detected OS: debian
2024-04-22T23:02:28.266+0200	INFO	Detecting Debian vulnerabilities...
2024-04-22T23:02:28.283+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:28.283+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:28.302+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:28.304+0200	INFO	Detected OS: alpine
2024-04-22T23:02:28.304+0200	INFO	Detecting Alpine vulnerabilities...
2024-04-22T23:02:28.305+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:28.305+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:28.320+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:28.324+0200	INFO	Detected OS: alpine
2024-04-22T23:02:28.324+0200	INFO	Detecting Alpine vulnerabilities...
2024-04-22T23:02:28.326+0200	INFO	Number of language-specific files: 0
2024-04-22T23:02:28.333+0200	WARN	This OS version is no longer supported by the distribution: alpine 3.13.5
2024-04-22T23:02:28.333+0200	WARN	The vulnerability detection may be insufficient because security updates are not provided
2024-04-22T23:02:28.341+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:28.342+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:28.342+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:28.351+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:28.374+0200	INFO	Detected OS: debian
2024-04-22T23:02:28.374+0200	INFO	Detecting Debian vulnerabilities...
2024-04-22T23:02:28.389+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:28.389+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:28.411+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:28.412+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:28.412+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:28.422+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:28.448+0200	INFO	Detected OS: ubuntu
2024-04-22T23:02:28.448+0200	INFO	Detecting Ubuntu vulnerabilities...
2024-04-22T23:02:28.456+0200	INFO	Number of language-specific files: 0
2024-04-22T23:02:28.490+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:28.497+0200	INFO	Detected OS: alpine
2024-04-22T23:02:28.497+0200	INFO	Detecting Alpine vulnerabilities...
2024-04-22T23:02:28.501+0200	INFO	Number of language-specific files: 0
2024-04-22T23:02:28.507+0200	WARN	This OS version is no longer supported by the distribution: alpine 3.13.5
2024-04-22T23:02:28.507+0200	WARN	The vulnerability detection may be insufficient because security updates are not provided
2024-04-22T23:02:28.518+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:28.520+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:28.520+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:28.531+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:28.533+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:28.533+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:28.545+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:28.547+0200	INFO	Detected OS: alpine
2024-04-22T23:02:28.547+0200	INFO	Detecting Alpine vulnerabilities...
2024-04-22T23:02:28.548+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:28.548+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:28.570+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:28.596+0200	INFO	Detected OS: ubuntu
2024-04-22T23:02:28.596+0200	INFO	Detecting Ubuntu vulnerabilities...
2024-04-22T23:02:28.607+0200	INFO	Number of language-specific files: 0
2024-04-22T23:02:28.631+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:28.632+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:28.632+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:28.649+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:28.654+0200	INFO	Detected OS: alpine
2024-04-22T23:02:28.654+0200	INFO	Detecting Alpine vulnerabilities...
2024-04-22T23:02:28.657+0200	INFO	Number of language-specific files: 0
2024-04-22T23:02:28.664+0200	WARN	This OS version is no longer supported by the distribution: alpine 3.13.5
2024-04-22T23:02:28.664+0200	WARN	The vulnerability detection may be insufficient because security updates are not provided
2024-04-22T23:02:28.675+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:28.676+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:28.677+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:28.691+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:28.694+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:28.694+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:28.712+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:28.715+0200	INFO	Detected OS: alpine
2024-04-22T23:02:28.715+0200	INFO	Detecting Alpine vulnerabilities...
2024-04-22T23:02:28.716+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:28.717+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:28.737+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:28.771+0200	INFO	Detected OS: debian
2024-04-22T23:02:28.771+0200	INFO	Detecting Debian vulnerabilities...
2024-04-22T23:02:28.855+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:28.855+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:28.896+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:28.901+0200	INFO	Detected OS: alpine
2024-04-22T23:02:28.901+0200	INFO	Detecting Alpine vulnerabilities...
2024-04-22T23:02:28.902+0200	INFO	Number of language-specific files: 0
2024-04-22T23:02:28.913+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:28.915+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:28.915+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:28.929+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:28.933+0200	INFO	Detected OS: alpine
2024-04-22T23:02:28.933+0200	INFO	Detecting Alpine vulnerabilities...
2024-04-22T23:02:28.938+0200	INFO	Number of language-specific files: 0
2024-04-22T23:02:28.944+0200	WARN	This OS version is no longer supported by the distribution: alpine 3.13.5
2024-04-22T23:02:28.944+0200	WARN	The vulnerability detection may be insufficient because security updates are not provided
2024-04-22T23:02:28.954+0200	INFO	Vulnerability scanning is enabled
2024-04-22T23:02:28.956+0200	INFO	Number of language-specific files: 1
2024-04-22T23:02:28.956+0200	INFO	Detecting gobinary vulnerabilities...
2024-04-22T23:02:28.980+0200	INFO	Vulnerability scanning is enabled
panic: runtime error: invalid memory address or nil pointer dereference
[signal SIGSEGV: segmentation violation code=0x1 addr=0x10 pc=0x5b0262091c46]

goroutine 429 [running]:
github.com/aquasecurity/trivy/pkg/sbom/spdx.(*SPDX).isTrivySBOM(...)
	github.com/aquasecurity/trivy@v0.50.0/pkg/sbom/spdx/unmarshal.go:258
github.com/aquasecurity/trivy/pkg/sbom/spdx.(*SPDX).unmarshal(0xc001b5a288, 0xc00076e780)
	github.com/aquasecurity/trivy@v0.50.0/pkg/sbom/spdx/unmarshal.go:72 +0x26
github.com/aquasecurity/trivy/pkg/sbom/spdx.(*SPDX).UnmarshalJSON(0xc001b5a288, {0xc000b91800, 0x17b, 0x200})
	github.com/aquasecurity/trivy@v0.50.0/pkg/sbom/spdx/unmarshal.go:65 +0x20e
encoding/json.(*decodeState).object(0xc00076e668, {0x5b02659a8860?, 0xc001b5a288?, 0xc00137f1d0?})
	encoding/json/decode.go:604 +0x6d0
encoding/json.(*decodeState).value(0xc00076e668, {0x5b02659a8860?, 0xc001b5a288?, 0xc00137f220?})
	encoding/json/decode.go:374 +0x3e
encoding/json.(*decodeState).unmarshal(0xc00076e668, {0x5b02659a8860?, 0xc001b5a288?})
	encoding/json/decode.go:181 +0x11e
encoding/json.(*Decoder).Decode(0xc00076e640, {0x5b02659a8860, 0xc001b5a288})
	encoding/json/stream.go:73 +0x15a
github.com/aquasecurity/trivy/pkg/sbom.Decode({_, _}, {_, _})
	github.com/aquasecurity/trivy@v0.50.0/pkg/sbom/sbom.go:225 +0x6c2
github.com/aquasecurity/trivy/pkg/fanal/analyzer/sbom.sbomAnalyzer.Analyze({}, {0xc001e84cf0?, 0xc001e84cf0?}, {{0x0, 0x0}, {0xc0036960a0, 0x19}, {0x5b0265b41158, 0xc0015d35e0}, {0x7d27c0b38520, ...}, ...})
	github.com/aquasecurity/trivy@v0.50.0/pkg/fanal/analyzer/sbom/sbom.go:39 +0x105
github.com/aquasecurity/trivy/pkg/fanal/analyzer.AnalyzerGroup.AnalyzeFile.func1({0x5b0265b35c00?, 0x5b02683dd340}, {0x5b0265b33af0?, 0xc002024030?})
	github.com/aquasecurity/trivy@v0.50.0/pkg/fanal/analyzer/analyzer.go:430 +0x23a
created by github.com/aquasecurity/trivy/pkg/fanal/analyzer.AnalyzerGroup.AnalyzeFile in goroutine 578
	github.com/aquasecurity/trivy@v0.50.0/pkg/fanal/analyzer/analyzer.go:425 +0x4ab

Expected behavior
not crashing :)
Screenshots
No response
Additional context
No response

remvoving "cve" key and its content solves crashing, but of course disables cve scans.

@nvtkaszpir is this reproducible for you? it is coming up fine without crashing.

It may be related to the existing metadata or data of the images, I can provide you with the data if you want (form a snapshot):
/tank/zot # du -sh *
411K	cache.db
2.3G	docker.io
70M	gcr.io
475M	ghcr.io
304M	k8s.gcr.io
923K	meta.db
319M	nvcr.io
8.7G	quay.io
626M	registry.k8s.io
758M	_trivy

16GB in total

Hi @nvtkaszpir,
Can you also send us the last entries of the zot logs (/var/log/zot/zot.log)? From what I see it scanned successfully several images, and at some point, probably on a very specific image, it errored. That image could theoretically be identified based on the logs generating when scanning.
Also did you encounter this error while triggering a CVE scan yourself (using the zli or ui), or has it happened while it was scanning images in the background? That may also help in identifying what images were scanned.

I'll have to check the logs, I guess it started to happen on its own, because the scan was running on its own every 168h.
Now it started to happen instantly on start because scan time expired and thus it ends in crash loop under systemd service auto restart.

It's probably a newer image which was pushed to the upstream recently and was pulled by zot sync.

Oh nice.
Will try to do it in the evening, something 12h from now.

bin/zot-linux-amd64 --version
{"level":"info","distribution-spec":"1.1.0","commit":"v2.0.3-10-g7b1fc04","binary-type":"-imagetrust-lint-metrics-mgmt-profile-scrub-search-sync-ui-userprefs","go version":"go1.22.1","time":"2024-04-23T20:36:05+02:00","message":"version"}

It works, no crashes, after service restart it rescanned all images it could.

@nvtkaszpir thanks for confirming, we will cut a maintenance release for this.
Close this issue?

fixed in #2399


Need better output for unit-tests in case of RHost start failure

Currently it isn't visible in test output and require debugging

We believe that this no longer adds value.


Document how hot reload can be triggered from inside IntelliJ

Currently the Run your Flutter app section of the Getting Started guide does not provide any information on how to trigger hot reload from within IntelliJ.
https://flutter.io/getting-started/#run-your-flutter-app
IntelliJ Debug Panel Buttons

The documentation should contain information on the following buttons in the debug panel of IntelliJ:

Hot Reload
Full Application Restart
Open Observatory
Mention 'Rerun main.dart' button on the left, and how it differs from 'Full Application Restart'

Document Keyboard shortcuts

Document current keyboard shortcuts for both Mac and Linux for Hot Reload and Full Application Restart.
Link to IntelliJ documentation for how to change keyboard mappings.
Document Find action command (⇧⌘A on OS X, using settings or menu on Linux) to look for current Flutter keyboard shortcuts.

Agreed, thanks for pointing this out. I think our Getting Started guide should take you through a single change, thus showing you Hot Reload.
I don't think I'd include "Open Observatory", though, in the Getting Started guide.

cc @Sfshaza this one might be a good starter issue?

Yes, you are right. "Open Observatory" is probably not useful for beginners.

Created pull request: https://github.com/flutter/website/pull/326

PR was landed, closing bug


Upgrade to JMeter 5.4.1

This PR updates to latest available JMeter (5.4.1). It also upgrades the Java Runtime Environment (to 11).
I also took the liberty to change how the JMeter install location is referenced to make future upgrades easier.

This pull request will be very useful.

hey @thiagoarrais, thanks for the contribution, we will review it internally.
maybe would be better to add version tags before merging this
wdyt @s-radyuk @s4nji ?

hey @ldeitos, as you request some changes on this PR we need your approval here to be able to merge

Thank you!


Update to 1.18.2

I dont know the mod is breaking in 1.18.2 , it shouldnt do that since the versio is supposed to only change technical stuffs related to worldgen . still Can u pls find the issue and fix it ?
( note the error log that pops up into my server log , is very very similar to Nullscape 1.1 error when i tried to run it on 1.18.2 )

thx alot


Add missing export section to KR, ID, TR translations

In the README files for ID, KR, and TR, the "📤 Export Multiple Conversations" section was missing. I translated and added it to these different README (I didn’t touch the code 😄).

Nice catch. Thank you!


nixos-install: fix flake command

Motivation for this change
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[ ] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I wish nixos-install's Flake support had an installer test...

I wish nixos-install's Flake support had an installer test...

Even if something like this will be added: I'd be pretty much against on blocking a channel on a broken installer test using unstable features.

The nix package manager does not had a great testing culture. This is now improving a bit since more contributors are getting involved into development.


🐞 - Padding 0 Issues

Which @codeimage/* package(s) are the source of the bug?
codeimage
Please provide a screenshot or a video to a minimal reproduction of the bug
No response
Description
When padding is set to zero, we lose the radius on the code image. But once we click download it give us the rounded form, however it is cut on corners
Which browsers have you used?

[X] Chrome
[ ] Firefox
[ ] Safari
[ ] Edge

Which operating systems have you used?

[ ] macOS
[X] Windows
[ ] Linux
[ ] iOS
[ ] Android

I forked the repository to try to fix this bug

@saiidhanna21 I forked the repository to try to fix this bug

@saiidhanna21 In which file can I find the sidebar code ? Thanks

Hi @AlLubila, all sidebar code is here
https://github.com/riccardoperra/codeimage/tree/main/apps/codeimage/src/components/PropertyEditor
the border radius control is present in this file: https://github.com/riccardoperra/codeimage/blob/main/apps/codeimage/src/components/PropertyEditor/FrameStyleForm.tsx
However, I think this could be a frame styling issue
https://github.com/riccardoperra/codeimage/tree/main/apps/codeimage/src/components/Terminal

@riccardoperra I see, I will do my best to help you then. I will check each link and see how I can fix it(●'◡'●)

@riccardoperra  @saiidhanna21
My summary while I was debugging:
THE PROBLEM
When the padding is set to 0 the terminal loose its border-radius
OBSERVATION IN THE CONSOLE
When the padding is set to 0:
The class .terminal_wrapper is overlapping by the element.style(The highest container div of terminal) where the custom Radius(var--) is set to 0
SOLUTION
Find a way to disable the custom Radius of the element.style(The highest container div of terminal)
BUT,  BUT
After writting code to remove the custom radius style in the highest div of terminal you must set the value of radius in the sidebar to 16 to avoid that background behind the terminal be seen.
VIDEO TO ILLUSTRATE WHAT I WROTE ⬇ I hope it will help you to fix this issue 👌
https://github.com/riccardoperra/codeimage/assets/127430514/bc447bd1-e0ef-412e-af6f-0c8bd1b2a629

Hey @AlLubila, thanks for your explanation. I can investigate on this this weekend and give you more information on how to handle this.
Currently I think that the image backdrop should change his radius according to what the user choose.
However, if the user has set padding to 0, I think that we should disable the border type option (set to none/null) and the shadows (these could already be hidden since we are using overflow auto

@riccardoperra  Got it, If I find a way to contibute again I will share with you


[READY] Adds no-cache headers for non 200 responses

Problem
When the broker returns a non 200 response (Not one specified in the metadata Status header), no headers are sent to indicate the response shouldn't be cached upstream.
Solution
For any non 200 response, send back the following headers:
{
"Cache-Control" => "no-cache, must-revalidate",
"Pragma"        => "no-cache",
"Expires"       => "{Date in the past}"
}

:cake:


UI broken on Gnome 40.1 when using with two monitors (100%, 125% zoom)

System information:

Operating system (distribution) and version: Arch Linux (latest)
DBeaver version <IP_ADDRESS>105081620
Additional extensions none

Connection specification:
UI only issue
Describe the problem you're observing:
I am running gnome-shell 40.1 with two monitors, the external one on 125% zoom.
Steps to reproduce, if exist:
Open dbeaver (usually opens on large external screen), looks like this:

Resize dbeaver window:

Move to laptop screen (100% zoom) and move back to external monitor:

After Restart Now the process starts again, if I answer "no" I can use dbeaver, but with very small icons.

Only on the native screen it looks OK.

I'm afraid, it is a third party issue and we have to wait for a fix. Closed as a duplicate https://github.com/dbeaver/dbeaver/issues/6581


ell: 0.42 -> 0.43, iwd: 1.16 -> 1.17

Motivation for this change
iwd
ver 1.17:
	Fix issue with sending additional and vendor IEs.
	Fix issue with IE ordering for 802.11-2020 support.
	Fix issue with frequency update on channel switch events.
	Fix issue with drivers and handling of IF_OPER_UP setting.

ell
ver 0.43:
	Add support for DHCP Rapid Commit feature.
	Add support for DHCP authoritative mode feature.

ofono and bluez still build and seem to work. I had to include one post-1.17 commit to fix a test failure.
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 136284 at 306f04e4 run on x86_64-linux 1

5 packages marked as broken and skipped:

googleearth-pro
linuxKernel.packages.hardkernel_4_14.xpadneo
linuxPackages_hardkernel_latest.xpadneo
odpdown
termplay

795 packages skipped due to time constraints:

adapta-gtk-theme
adoptopenjdk-icedtea-web
alfis
almanah
anydesk
apostrophe
appgate-sdp
aravis
arc-theme
areca
...

12 packages built successfully:

bluez (bluez5)
ell
iwd
obexfs
obexftp
openobex
python38Packages.pybluez
python39Packages.bleak
python39Packages.pybluez
redfang
urserver
wiiuse


Tabs only 1 Tabs active

Is there a Problem with the Tab toggle attr. ? i have a Setup like this

    <button type="button"
	data-toggle-class
	data-toggle-target="#tabContainer1"
	data-toggle-radio-group="tabsGroup"
	data-toggle-is-active
	role="tab"
	aria-selected="true"
	aria-controls="tabContainer1">
          button1
     </button>
    <button type="button"
	data-toggle-class
	data-toggle-target="#tabContainer2"
	data-toggle-radio-group="tabsGroup"
	data-toggle-is-active
	role="tab"
	aria-selected="true"
	aria-controls="tabContainer2">
          button1
     </button>

He renders the is-active class into the div container but i can always activate both tabs at the same time. So in this example both image are among themselves. I want that they replace each other.
The CodePen example doesn't work good as well.
Thanks for some feedback
Chris

👍


Login page with redirect

Implement login page using redirect instead of popup as current.

Google authenticator doesn't respond to our webpage, replies to the Firebase host instead.


Couldn't load tag gravitychanger:forbidden_entities as it is missing following references: create:contraption (from GravityChanger), create:stationary_contraption (from GravityChanger), create:gantry_contraption (from GravityChanger), create:super_glue (from GravityChanger), create:crafting_blueprint (from GravityChanger), create:seat (from GravityChanger)

When you load a world, this is in the logs: (1.18.2)
Couldn't load tag gravitychanger:forbidden_entities as it is missing following references: create:contraption (from GravityChanger), create:stationary_contraption (from GravityChanger), create:gantry_contraption (from GravityChanger), create:super_glue (from GravityChanger), create:crafting_blueprint (from GravityChanger), create:seat (from GravityChanger)

I think this only happens on the curseforge versions, modrinth has more versions


hidden emails

Hi,
Sometimes emails are hidden<EMAIL_ADDRESS>This crash the program in the next step:
Traceback (most recent call last):
  File "domLink.py", line 176, in <module>
    expand()
  File "domLink.py", line 150, in expand
    pages = content["total_pages"]
KeyError: 'total_pages'

I think you should add a test to check the presence of total_pages but for now I added a very small function to test the email (a regexp would be much better but Python is not my cup of tea):
def append_email(email):
        if email.find('*') == -1:
	        company_emails.append(email)

Then replace:
company_emails.append(...)

By:
append_email(...)

Best regards,
Gwen

I'll add a try except to it just to catch it. You're supposed to type "n" when it prompts for such an email. But hmm... yeah.

Thanks! I'll take a look when I have a moment.


Network usage is prohibited for themes

It appears that your theme uses network connections to load assets (e.g. fonts, icons, or images). This is prohibited by the official Obsidian developer policies because themes should function completely locally.
You can bundle an asset for local use by using data URLs. See this guide.
Please let us know if you have any questions. Any themes that use network connections will be removed from the official directory in the first week of January 2024.

The Obsidian team.

Hi @Bluemoondragon07
We have noticed that you have not fixed this issue yet.
We have extended the deadline up to the 30th of february.
After that point, we will remove the theme from the community themes, if this issue is not fixed by then.

I have removed the assets from the network. The user can now optionally choose to load them with a snippet.


added note about digitally sighned PDF

#738

@nenonix @JohanFreelancer9 - kindly do the copy editor review for this PR. Thanks.

@MaratMussabekov - please merge the commit on the copy/edit review done by JohanFreelancer9 or make the necessary changes on the PR following the suggestions made. Thank you.

@KCCross - PR has been copy edited and is ready for final review. This is based on issue #738
Thank you.
cc: @kenwith

@KCCross - We would like to follow up. Any updates on this?
Thank you.

Kaarin, requesting assistance on finalizing information for SharePoint and PDF


MA-348 some video as not displayable

@aleffert @rohan-dhamal-clarice  @BenjiLee
please review.

Commit message could be clearer.

@BenjiLee @aleffert
Please review.

:+1:


Commits from Github Desktop occur errors

hello, first of all, great package ! & everything works just fine when trying to commit through my cli, but when using Github Desktop 3.1.1-linux1 (x64)  i get this error
><EMAIL_ADDRESS>pre-commit
> lint-staged

file:///home/xornei/xxxx/codes/xxxx/node_modules/lint-staged/bin/lint-staged.js:21
const packageJson = JSON.parse(await fs.readFile(new URL('../package.json', import.meta.url)))
                               ^^^^^

SyntaxError: Unexpected reserved word
    at Loader.moduleStrategy (internal/modules/esm/translators.js:133:18)
    at async link (internal/modules/esm/module_job.js:42:21)
husky - pre-commit hook exited with code 1 (error)

"husky": "^8.0.0",
"lint-staged": "^14.0.1",
"node": v16.20.2
Github Desktop 3.1.1-linux1 (x64)

thanks for helping, much appreciated.

Oh, I see you're running Node.js 14. You need to upgrade to at least 18.12.0 which is the minimim supported version.

@iiroj thanks for quick response, i'll give it a try and keep you updated !

@iiroj i installed the 18.19.0 version of node and made it default with this two commands
nvm install 18
nvm alias default 18

and then i retested a simple commit but the issue persisted
but since i'm using the version 14 of lint-staged isn't compatible with 16th version of node ?
v14
Since v14.0.0 lint-staged no longer supports Node.js 14. Please upgrade your Node.js version to at least 16.14.0.


Error Config flow could not be loaded: 500 Internal Server Error Server got itself in trouble

I have just installed 1.0.0-beta6 and appear to be having an issue with the setup.
When I select Configure I get this error dialog:

Debug log reports the following:
This error originated from a custom integration.

Logger: aiohttp.server
Source: custom_components/powercalc/config_flow.py:593
Integration: Powercalc (documentation, issues)
First occurred: 11:23:55 AM (1 occurrences)
Last logged: 11:23:55 AM

Error handling request
Traceback (most recent call last):
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_protocol.py", line 435, in _handle_request
    resp = await request_handler(request)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_app.py", line 504, in _handle
    resp = await handler(request)
  File "/usr/local/lib/python3.10/site-packages/aiohttp/web_middlewares.py", line 117, in impl
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/security_filter.py", line 60, in security_filter_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/forwarded.py", line 100, in forwarded_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/request_context.py", line 28, in request_context_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/ban.py", line 82, in ban_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/auth.py", line 236, in auth_middleware
    return await handler(request)
  File "/usr/src/homeassistant/homeassistant/components/http/view.py", line 136, in handle
    result = await result
  File "/usr/src/homeassistant/homeassistant/components/config/config_entries.py", line 218, in post
    return await super().post(request)
  File "/usr/src/homeassistant/homeassistant/components/http/data_validator.py", line 73, in wrapper
    result = await method(view, request, data, *args, **kwargs)
  File "/usr/src/homeassistant/homeassistant/helpers/data_entry_flow.py", line 71, in post
    result = await self._flow_mgr.async_init(
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 225, in async_init
    flow, result = await task
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 252, in _async_init
    result = await self._async_handle_step(flow, flow.init_step, data, init_done)
  File "/usr/src/homeassistant/homeassistant/data_entry_flow.py", line 367, in _async_handle_step
    result: FlowResult = await getattr(flow, method)(user_input)
  File "/config/custom_components/powercalc/config_flow.py", line 537, in async_step_init
    data_schema=self.build_options_schema(),
  File "/config/custom_components/powercalc/config_flow.py", line 593, in build_options_schema
    data_schema = SCHEMA_POWER_OPTIONS.extend(strategy_schema.schema).extend(
AttributeError: 'NoneType' object has no attribute 'schema'

Could you please check config/.storage/core.config_entries file, and search for the relevant configuration entry. Could you share that JSON please?

This was my first time with the new GUI interface so I wasn't quite sure how it was working.
It appears to of been an auto discovered Google Home device, which is good that it is auto discover, but doesn't seem to like the device entry:
      {
        "entry_id": "ea50ce89ab0518a476047c97af18fa07",
        "version": 1,
        "domain": "powercalc",
        "title": null,
        "data": {
          "unique_id": "264c2b14-24f7-dfae-12bb-67246f00a7a8",
          "name": null,
          "entity_id": "media_player.dining_room_speaker",
          "manufacturer": "google",
          "model": "Home Mini (HOA)",
          "sensor_type": "virtual_power"
        },
        "options": {},
        "pref_disable_new_entities": false,
        "pref_disable_polling": false,
        "source": "integration_discovery",
        "unique_id": "264c2b14-24f7-dfae-12bb-67246f00a7a8",
        "disabled_by": null
      }

I now also have some athom bulbs which have auto discovered and are working correctly, just the google device which is causing this issue.

Issue confirmed. I had the same bug (also on my production instance).
Should be fixed with #1177 which will be included in next beta I'll release shortly.
I also notice your entry is called "Unnamed entry". name and title is null in the config entry data. This should be taken over from the source entity name. Not sure why this is empty in your case. Could you have a look into config/.storage/core.entity_registry and search for media_player.dining_room_speaker?
The reason your other google home mini's are not autodiscovered is because they are not part of the entity registry in HA, I can see that by looking at the icon in the last column of the entity listing. These entities do not have a unique_id which is also why you cannot edit any properties of these entities via the GUI. And this is the reason they are not in the entity registry.
Powercalc looks at all the entities in the entity and device registries, but when your entities are not in it powercalc will not find them.
How did you create these Google Cast entities? Because for me they all have a unique id. When you do that with the GUI "Add integration" or it was auto discovered it should get a unique id automatically. So I'm not sure why you have this issue. I suggest to ask on HA community forum or create an issue on github home assistant core.
It's not possible to create a powercalc sensor yourself via the GUI and selecting the manufacturer and model from the library. That's only possible for the LUT mode yet, but the google home uses the linear mode.
I will add that in the future.
You can set it up with YAML however:
sensor:
  - platform: powercalc
    entity_id: media_player.fergus_speaker
    manufacturer: google
    model: Home Mini (HOA)

Here is dining_room_speaker
      {
        "area_id": null,
        "capabilities": {},
        "config_entry_id": "bce72d57a174cf37bec5783968262301",
        "device_class": null,
        "device_id": "516051413c31db89a5df4535d9a02cb6",
        "disabled_by": null,
        "entity_category": null,
        "entity_id": "media_player.dining_room_speaker",
        "hidden_by": null,
        "icon": null,
        "id": "b5833b6234f2573991aacd4062e58344",
        "has_entity_name": true,
        "name": null,
        "options": {},
        "original_device_class": "speaker",
        "original_icon": null,
        "original_name": null,
        "platform": "cast",
        "supported_features": 131968,
        "unique_id": "264c2b14-24f7-dfae-12bb-67246f00a7a8",
        "unit_of_measurement": null
      },

How did you create these Google Cast entities?

They would of been autodiscoved by the Google Cast integration a long time ago as I don't use them and it wasn't until powercalc started autodiscovery that I remembered I had them.
I shall delete and reload the Google Cast integration to see what happens.
Great Google Cast has been autodiscovered.

New devices entry from entity_registry:
      {
        "area_id": null,
        "capabilities": {},
        "config_entry_id": "46e191515852dffb405bfc29eba73d19",
        "device_class": null,
        "device_id": "516051413c31db89a5df4535d9a02cb6",
        "disabled_by": null,
        "entity_category": null,
        "entity_id": "media_player.lounge_speaker",
        "hidden_by": null,
        "icon": null,
        "id": "0744ea5f4557e1d4591ba04a43fa851d",
        "has_entity_name": true,
        "name": null,
        "options": {},
        "original_device_class": "speaker",
        "original_icon": null,
        "original_name": null,
        "platform": "cast",
        "supported_features": 131968,
        "unique_id": "264c2b14-24f7-dfae-12bb-67246f00a7a8",
        "unit_of_measurement": null
      },

Couldn't see how to retrigger auto discovery for powercalc and nothing as appeared after 30 minutes.

You can trigger auto discovery for powercalc by restarting HA.

You can trigger auto discovery for powercalc by restarting HA.

restarted a few times, but my rediscovered cast devices haven't been identified by powercalc.
I then deleted two unknown powercalc devices, rebooted and got the following.

Another unnamed entity (which is the lounge_speaker from https://github.com/bramstroker/homeassistant-powercalc/issues/1171#issuecomment-1290063914

Which seems to be working correctly as power/ energy sensor.

Second device, I unchecked 'Confirm Model' and was given a list of Google options, but was unable to proceed with setup.

From you devices only "Lounge speaker" and "Fergus speaker" are supported yet. Others are not the google home or mini and are not in the library yet. Maybe someone else will add.
Though there are some strange things with these two devices.

There are extra parenthesis around the manufacturer and model name in the message.
No name can be extracted from the source entity, which is why the config entry will be "Unnamed entry". The reason for that would be that both name and original_name are empty in the entity registry which is very strange. How does these google homes show in GUI entities tab under "Devices & Entities"? Could you check that please

It would also help if you can share entries from the core.device_registry for these 2 devices, which contains the device information.
One last thing I notice is the naming in the config flow about LUT and lights, and the error you have when selecting a manufacturer/model yourself. I need to have a look into this. Originally this was designed for lights, but other devices (smart plugs, media players) have been added very recently. So the config flow needs to be adapted / refactored a bit to facilitate this correctly. I will have a look into that soon.

Second device, I unchecked 'Confirm Model' and was given a list of Google options, but was unable to proceed with setup.

Could you have a look into the error log what the exact error was. It should be there.

@purcell-lab I did a lot of fixes and improvements for the discovery flow, which may also solve all your issues.
Are you able to verify by upgrading to the latest powercalc version?

Thanks this has resolved my issue.
Awesome development work and engagement!


MPI: Handle sanity checks during initialization of unstructured boundary conditions differently

Fix issue #1047:

During initialization of the boundary conditions for unstructured meshes (UnstructuredMesh and P4estMesh), there is a check if the boundary names given by the user via a dictionary are valid. This check compares the names given by the user in the dictionary to the names found in the boundary container. While this works fine for serial runs, this check can't be done in parallel runs because the local domain might not contain all boundaries and thus not all valid boundary names are present in the boundary container. In that case the check would fail even if all boundary names given by the user are valid.

I cannot see the reasons for checks crashing. Github seem to not work correctly now.


[Hidden] Reduce component size

[x] I have followed (at least) the PR section of the contributing guide.

Reduced the size of the Hidden component by not setting a default value for all the props and avoid repeating the same code for HiddenCss and HiddenJs. The implementation checks for a truthy value so having the value be undefined instead of false makes no difference.
generateMarkdown.js was updated to support getting the default value from the JSDoc comment so that the documentation stays the same

With this new doc gen capability, we could potentially apply the jsdoc default props pattern, at scale, to all the components. The Hidden component might be a special case, I'm not sure we should allow it to all the other components. From what I understand, the issue is with the ES5 transpilation. In a distant future, when we will publish ES6 code by default on npm, the overhead will be much significantly reduced: https://unpkg.com/<EMAIL_ADDRESS>+1 for checking the existence of inconsistency.

@eps1lon - but we should not allow creating mismatched API documentations
@oliviertassinari - +1 for checking the existence of inconsistency.

Do you mean if @default and defaultValue are set, make sure they're identical?
Because currently, if defaultvalue is set @default is ignored

Could we throw if both are defined?

Could we throw if both are defined?

That would limit in-editor documentation

That would limit in-editor documentation

What do you mean? I think that the idea is encourage people to use the destructuring default prop when possible and to avoid discrepancy in the information.

What do you mean?

I was thinking about future changes, unrelated to the goal of this PR. I've made it throw if both are provided

That's still incorrect documentation. HiddenJs nor HiddenCss have default values.

I don't understand, the default values are equivalent to false. What's wrong with that?

I don't understand, the default values are equivalent to false. What's wrong with that?

undefined and false are not equivalent. This is a slippery slop. You don't even believe that otherwise you wouldn't want to document false as the default value.

@eps1lon I still don't understand. I believe that the equivalence property is: provide false to the value, observe the same behavior. Doesn't this property hold? What's the issue with this slippery slope?

Can we just remove the default value in this case?

The default value is only here for the documentation.

The default value was only added for the documentation generation

I would add that we will also depend on this for Framer component generation. It uses react-docgen, and needs sane defaults for the Framer UI to display correctly. I have been adding missing defaults to the components as I go. (PR to follow.)

I would add that we will also depend on this for Framer component generation. It uses react-docgen, and needs sane defaults for the Framer UI to display correctly

@mbrookes This pull request shouldn't cause an issue, right? You could leverage the same logic?

I have been adding missing defaults to the components as I go.

Sweet! I thought we already had them all, guess not 🙃.

This pull request shouldn't cause an issue, right? You could leverage the same logic?

Yes, in theory; and since Hidden isn't a very interesting component, it's no issue.
Fundamentally though, I agree with @eps1lon that the docs should be generated from code where possible, not annotation that can drift from the truth.

To summarize one last time: Don't try to outsmart the compiler. If we can generate from docs from code don't overwrite the generated code. You think you know better than the compiler but that's just not how software works. There will be edge cases you don't consider and in a few weeks you see another location were you think you should document another type and another and another and at one point the first assumption isn't correct anymore and now your type system collapses.
And again the question @oliviertassinari:
If you think undefined and false are equivalent here why do you need to overwrite the documentation? Just document it as undefined and we're fine.

I resorted to just removing the default value.

@eps1lon From my perspective, this is a developer experience concern. I believe users will prefer seeing false than undefined documented.

Should we give up on the changes then?

Should we give up on the changes then?

It's still possible to reduce the size while keeping the default value, just doesn't save as much

@merceyz I think that we should focus on a systematic solution to the problem. The Hidden component could be great to explore the generic concern and solution, but I don't think that we should optimize for it. I don't see how a -0.11% bundle size reduction is significative.


Client JSON message has wrong structure

the correct structure is as follows:
{"method": "register","args": {"name": "Jan Novak","nick": "Jak"}}
thats why we have test, to show the correct behavior

also, no such method as register/call exists - we either have register OR call

http://erickveil.github.io/2016/04/06/How-To-Manipulate-JSON-With-C++-and-Qt.html

Structure of JSON messages for registration and login was repaired and improved.


Fix arm architecture translation issue

Description
Found when attempting to build on an arm64 machine when I recieved an error message below.  Root cause is that string equality in java cannot be done with the == sign.
unknown architecture [arm64] for jdk [provisioned_runtime], must be one of [aarch64, x64]

Issues Resolved
Fixes arm64 build issue
Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

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

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

start gradle chekc


Add new demo file

Updated the demo GIF file that shows how to run the Generator.
Checklist:

[X] Have you followed the guidelines in our Contributing document?
[X] Have you checked to ensure there aren't other open Pull Requests for the same update/change?
[X] Have you successfully ran tests with your changes locally?
[X] Have you added an explanation of what your changes do and why you'd like us to include them?

View rendered README.md

Hi! Thanks for PR.
Make sure you have checked points in PR Template correctly.
(Powered by GitMate.io)

Can you update dev branch as well?

Sure


Flow support

Describe the bug
I'm trying to write vite-plugin for removing Flow.js types and i'm getting the error below
Reproduction

yarn create @vitejs/app template - vanilla
(inside generated folder)

yarn install
yarn add -D flow-remove-types

Set main.js content:

/* @flow */

type Type = {};

Create vite.config.js:

import removeTypes from "flow-remove-types";

export default {
  plugins: [
    {
      name: "vite-plugin-flow",
      enforce: "pre",
      transform(code) {
        const output = removeTypes(code);

        return {
          code: output.toString(),
          map: null,
        };
      },
    },
  ],
};

yarn dev // error

But it starts working if:

Remove types from main.js
yarn dev
Add types to main.js

Sorry if i missed something in the docs.
System Info

vite version: 2.0.3
Operating System: Ubuntu 18.04
Node version: 14.15.4
Package manager (npm/yarn/pnpm) and version<EMAIL_ADDRESS>
Logs (Optional if provided reproduction)

Run vite or vite build with the --debug flag.

  vite:config bundled config file loaded in 122ms +0ms
  vite:config using resolved config: {
  vite:config   plugins: [
  vite:config     'vite:pre-alias',
  vite:config     'alias',
  vite:config     'vite-plugin-flow',
  vite:config     'vite:dynamic-import-polyfill',
  vite:config     'vite:resolve',
  vite:config     'vite:html',
  vite:config     'vite:css',
  vite:config     'vite:esbuild',
  vite:config     'vite:json',
  vite:config     'vite:wasm',
  vite:config     'vite:worker',
  vite:config     'vite:asset',
  vite:config     'vite:define',
  vite:config     'vite:css-post',
  vite:config     'vite:client-inject',
  vite:config     'vite:import-analysis'
  vite:config   ],
  vite:config   server: {},
  vite:config   configFile: '/home/eazymov/Documents/projects/test/vite.config.js',
  vite:config   inlineConfig: {
  vite:config     root: undefined,
  vite:config     base: undefined,
  vite:config     mode: undefined,
  vite:config     configFile: undefined,
  vite:config     logLevel: undefined,
  vite:config     clearScreen: undefined,
  vite:config     server: {}
  vite:config   },
  vite:config   root: '/home/eazymov/Documents/projects/test',
  vite:config   base: '/',
  vite:config   resolve: { dedupe: undefined, alias: [ [Object] ] },
  vite:config   publicDir: '/home/eazymov/Documents/projects/test/public',
  vite:config   command: 'serve',
  vite:config   mode: 'development',
  vite:config   isProduction: false,
  vite:config   optimizeCacheDir: '/home/eazymov/Documents/projects/test/node_modules/.vite',
  vite:config   build: {
  vite:config     target: [ 'es2019', 'edge16', 'firefox60', 'chrome61', 'safari11' ],
  vite:config     polyfillDynamicImport: true,
  vite:config     outDir: 'dist',
  vite:config     assetsDir: 'assets',
  vite:config     assetsInlineLimit: 4096,
  vite:config     cssCodeSplit: true,
  vite:config     sourcemap: false,
  vite:config     rollupOptions: {},
  vite:config     commonjsOptions: { include: [Array], extensions: [Array] },
  vite:config     minify: 'terser',
  vite:config     terserOptions: {},
  vite:config     cleanCssOptions: {},
  vite:config     write: true,
  vite:config     emptyOutDir: null,
  vite:config     manifest: false,
  vite:config     lib: false,
  vite:config     ssr: false,
  vite:config     ssrManifest: false,
  vite:config     brotliSize: true,
  vite:config     chunkSizeWarningLimit: 500
  vite:config   },
  vite:config   env: { BASE_URL: '/', MODE: 'development', DEV: true, PROD: false },
  vite:config   assetsInclude: [Function: assetsInclude],
  vite:config   logger: {
  vite:config     hasWarned: false,
  vite:config     info: [Function: info],
  vite:config     warn: [Function: warn],
  vite:config     error: [Function: error],
  vite:config     clearScreen: [Function: clearScreen]
  vite:config   },
  vite:config   createResolver: [Function: createResolver]
  vite:config } +2ms
  vite:deps Crawling dependencies using entries:
  vite:deps   /home/eazymov/Documents/projects/test/index.html +0ms
  vite:resolve 1ms   /main.js -> /home/eazymov/Documents/projects/test/main.js +0ms
 > main.js:3:5: error: Expected ";" but found "Type"
    3 │ type Type = {};
      ╵      ~~~~

error when starting dev server:
Error: Build failed with 1 error:
main.js:3:5: error: Expected ";" but found "Type"
    at failureErrorWithLog (/home/eazymov/Documents/projects/test/node_modules/esbuild/lib/main.js:1171:15)
    at buildResponseToResult (/home/eazymov/Documents/projects/test/node_modules/esbuild/lib/main.js:907:32)
    at /home/eazymov/Documents/projects/test/node_modules/esbuild/lib/main.js:1002:20
    at /home/eazymov/Documents/projects/test/node_modules/esbuild/lib/main.js:553:9
    at handleIncomingPacket (/home/eazymov/Documents/projects/test/node_modules/esbuild/lib/main.js:642:9)
    at Socket.readFromStdout (/home/eazymov/Documents/projects/test/node_modules/esbuild/lib/main.js:520:7)
    at Socket.emit (events.js:315:20)
    at addChunk (internal/streams/readable.js:309:12)
    at readableAddChunk (internal/streams/readable.js:284:9)
    at Socket.Readable.push (internal/streams/readable.js:223:10)
error Command failed with exit code 1.

Provide the error log here.

$ vite
 > main.js:3:5: error: Expected ";" but found "Type"
    3 │ type Type = {};
      ╵      ~~~~

error when starting dev server:
Error: Build failed with 1 error:
main.js:3:5: error: Expected ";" but found "Type"
    at failureErrorWithLog (/home/eazymov/Documents/projects/test/node_modules/esbuild/lib/main.js:1171:15)
    at buildResponseToResult (/home/eazymov/Documents/projects/test/node_modules/esbuild/lib/main.js:907:32)
    at /home/eazymov/Documents/projects/test/node_modules/esbuild/lib/main.js:1002:20
    at /home/eazymov/Documents/projects/test/node_modules/esbuild/lib/main.js:553:9
    at handleIncomingPacket (/home/eazymov/Documents/projects/test/node_modules/esbuild/lib/main.js:642:9)
    at Socket.readFromStdout (/home/eazymov/Documents/projects/test/node_modules/esbuild/lib/main.js:520:7)
    at Socket.emit (events.js:315:20)
    at addChunk (internal/streams/readable.js:309:12)
    at readableAddChunk (internal/streams/readable.js:284:9)
    at Socket.Readable.push (internal/streams/readable.js:223:10)
error Command failed with exit code 1.

This is an error during Vite's pre-scanning that uses esbuild to look for dependencies. Esbuild cannot handle flow syntax because it assumes .js files only contain valid JS syntax.
Looks like the only way to solve this is to expose a way to add plugins to the pre-scanning phase as well :/

Many people use Flow, would be great if Vite could support it :)

Maybe it is possible to use this. https://www.npmjs.com/package/esbuild-plugin-flow Not sure if Vite allows passing additional plugins to esbuild directly.

@henrikbjorn @Eazymov were you able to try https://www.npmjs.com/package/esbuild-plugin-flow ? Vite does support passing options to esbuild https://vitejs.dev/config/#esbuild. I think that if this works, we could close this issue.

@henrikbjorn @Eazymov were you able to try https://www.npmjs.com/package/esbuild-plugin-flow ? Vite does support passing options to esbuild https://vitejs.dev/config/#esbuild. I think that if this works, we could close this issue.

As i can see passing plugins is not supported
https://github.com/vitejs/vite/blob/352cd397d8c9d2849690e3af0e84b00c6016b987/packages/vite/src/node/plugins/esbuild.ts#L20-L24

You are right, ESBuildOptions extends TransformOptions from esbuild, and I see that plugins are only supported during build and not for transform.
Evan Wallace explained the rationale here https://github.com/evanw/esbuild/issues/779#issuecomment-776540566

The reason why you can't use on-load plugins with the transform API is that it's pointless. The transform API takes the code as a string so if you want to transform the string before esbuild processes it, you can just transform the string yourself first before giving it to esbuild. You don't need the plugin API for that.

You are right, ESBuildOptions extends TransformOptions from esbuild, and I see that plugins are only supported during build and not for transform.
Evan Wallace explained the rationale here evanw/esbuild#779 (comment)

The reason why you can't use on-load plugins with the transform API is that it's pointless. The transform API takes the code as a string so if you want to transform the string before esbuild processes it, you can just transform the string yourself first before giving it to esbuild. You don't need the plugin API for that.

Is there a way to transform the code before it is given to esbuild? I seem to remember that was possible in Vite1.

@henrikbjorn You can add rollup/plugin-babel.

@henrikbjorn You can add rollup/plugin-babel.

If Rollup plugins are the same as vite plugins, how would that work any differently as it does now?

@henrikbjorn You are not constrained to .jsx and .tsx extensions with it. You can put any syntax there vite does not support.

@henrikbjorn You are not constrained to .jsx and .tsx extensions with it. You can put any syntax there vite does not support.

The problem here is that we can't change the code, before it is given to ESBuild. That constraint is the same for Rollup plugins, when using the server. In that case, I can't see how using a Rollup will work differently than a small plugin that tries and strip flow types.

See https://vitejs.dev/guide/api-plugin.html#plugin-ordering
You probably want to add enforce: 'pre' option

See https://vitejs.dev/guide/api-plugin.html#plugin-ordering
You probably want to add enforce: 'pre' option

Look at the bug report here. Does not work, this is exactly the plugin used by the author of this issue.

Disclaimer: the following is an ugly hack, but it got us moving. My first attempt used flow-remove-types, but we ended up needing to parse decorators for esbuild also, so I switched to Babel. I will happily tear this code out when there is official support in vite for this use-case!
const { createServer } = require('vite');
const fs = require('fs');
const babelCore = require('@babel/core');

const readFileSync = fs.readFileSync;

(async () => {
  intercept();
  const server = await createServer();
  await server.listen();
  unintercept();
})();

function intercept() {
  fs.readFileSync = (...params) => {  // 🤮
    const [path] = params;
    const src = readFileSync(...params);
    return babel(path, src);
  };
}

function unintercept() {
  fs.readFileSync = readFileSync;
}

function babel(path, src) {
  const extensions = ['.js', '.jsx'];
  if (typeof src !== 'string') return src;
  if (path.includes('/node_modules/')) return src;
  if (!extensions.some(ext => path.endsWith(ext))) return src;
  return babelCore.transformSync(src, {
    // Transform just enough to allow vite to get through the precompilation stage
    filename: path,
    presets: ['@babel/flow'],
    plugins: [
      '@babel/plugin-syntax-jsx',
      '@babel/plugin-syntax-class-properties',
      ['@babel/plugin-proposal-decorators', { legacy: true }],
    ],
  }).code;
}

See @bunchtogether/vite-plugin-flow for flow support.

@wehriam Hey, did you already created a PR in https://github.com/vitejs/awesome-vite ?


Window#maximize spec fails when running on Travis

The window#maximize spec has recently stopped passing on Travis runs

@abotalov You did a great job getting this passing originally with the awesome window manager.  Any chance you have time to look at it again and see if you can figure out what has changed that is causing it to fail with firefox every time (I believe it passes with chrome).  I have marked the test as pending for the firefox/travis combo currently.

I reproduced it on my machine. This test passes with FF + awesome + Xvfb + selenium 2.44.0 /  2.45.0.dev2 / 2.45.0.dev2 but fails with selenium 2.45.0.dev / 2.45.0
I don't yet what is the cause of it.

This could be caused by the significant performance degradation the firefox driver has in selenium 2.45.0  hopefully 2.45.1 or 2.46 will be released soon with the fix so we can confirm.   https://code.google.com/p/selenium/issues/detail?id=8551


[BUG] - Input and Select have different label colors

NextUI Version
2.1.13
Describe the bug
By default the components Input and Select have different text colors.
Input: foreground-600
Select: foreground-500
I noticed this when using both components next to another in a form, which would be a very common use case.
Further to that I had trouble easily changing the Select  color and needed to use CSS modules to do it.
Your Example Website or App
No response
Steps to Reproduce the Bug or Issue
Use default Input and default Select components.
Expected behavior
Use a consistent color shade across both components.
I would personally suggest foreground-600.
Screenshots or Videos

Operating System Version
MacOS
Browser
Chrome

@Innders which files to change? Also, please assign this issue to me!

Hey this should be fixed in the next release v2.2.0
https://github.com/nextui-org/nextui/pull/1797


Sysprepped boxstarter installation

Here at our school we are trying to use Boxstarter.
I installed Boxstarter as admin in our default Win7 installation.
After the installation we sysprep this Win7 to use it for cloning purpose.
When deploying the image to computers, Boxstarter does not work anymore.
This is the error we get:
C:\Users\Administrator>boxstartershell
C:\Users\Administrator>powershell.exe -ExecutionPolicy bypass -NoE
xit -Command "&'C:\Users\Administrator\AppData\Roaming\Boxstarter\BoxstarterShel
l.ps1'"
The term 'C:\Users\Administrator\AppData\Roaming\Boxstarter\BoxstarterShell.ps1
' is not recognized as the name of a cmdlet, function, script file, or operable
program. Check the spelling of the name, or if a path was included, verify tha
t the path is correct and try again.
At line:1 char:2

& <<<< 'C:\Users\Administrator\AppData\Roaming\Boxstarter\BoxstarterShell.ps1
'

CategoryInfo          : ObjectNotFound: (C:\Users\Admini...tarterShell.p
s1:String) [], CommandNotFoundException
FullyQualifiedErrorId : CommandNotFoundException

Thanks!

When you sysprep the machine it deletes user specific accounts and directories. Since that's where the boxstarter bits are they get removed.
I'd consider adding the boxstarter install to your answer file so that it gets installed as part of windows os setup.
There is also an issue to not keep the boxstarter bits in user directories but instead install to programdata which will retain it through sysprep.


Fix CRI logger max size behavior

What type of PR is this?
/kind bug
What this PR does / why we need it:
We should account the bytes written globally and not on a per write basis. Added a unit test for the erroneous behavior.
Which issue(s) this PR fixes:

None
Special notes for your reviewer:
None
Does this PR introduce a user-facing change?

Fixed CRI logger max size behavior.

Codecov Report

Merging #562 (b77b818) into main (eaf0268) will not change coverage.
The diff coverage is n/a.

@@          Coverage Diff          @@
##            main    #562   +/-   ##
=====================================
  Coverage   6.89%   6.89%
=====================================
  Files          2       2
  Lines         29      29
  Branches      17      17
=====================================
  Hits           2       2
  Misses        27      27

@rphillips @haircommander PTAL

/lgtm


Support for errors.Join

nilaway detects false positives when errors.Join is used together with errors that are guaranteed to not be nil, like errors.Join(errors.New("an error")).
nilaway could have the rule: if any of the argument to errors.Join are guaranteed to not be nil, the joined error is also guaranteed to not be nil.
The full working example:
package main

import "errors"

func main() {
	printFn(true)
	printFn(false)
}

func printFn(ferr bool) {
	i, err := fn(ferr)
	if err != nil {
		println(err.Error())
	} else {
		println(*i)
	}
}

func fn(err bool) (*int, error) {
	if err {
		return nil, errors.Join(errors.New("an error"), errors.New("another error"))
	} else {
		i := 42
		return &i, nil
	}
}

runs fine, but produces the nilaway error output
main.go:15:12: error: Potential nil panic detected. Observed nil flow from source to dereference point:
	-> nilaway-errors-join/main.go:21:10: literal `nil` returned from `fn()` in position 0 when the error return in position 1 is not guaranteed to be non-nil through all paths
	-> nilaway-errors-join/main.go:15:12: result 0 of `fn()` dereferenced

@sebastianst: ACK. Thanks for reporting this issue. We have implemented a trusted functions framework in NilAway, with which we treat functions, such as errors.New(), as "trusted", meaning we can safely encode only one return value (always nonnil or always nil). However, this errors.Join() case is more nuanced, where it may return nil, when all of the arguments are nil, else return nonnil. We'll investigate more into how to accommodate support for such cases and hopefully come up with a fix soon.


Any plans on open sourcing?

Dear authors,
@woxihuanjiangguo
I am wondering about your plan for open sourcing, as indicated in your arXiv paper.
Thanks!

Hi @jiaxiaosong1002 , sorry for the delayed response. We are in the process of cleaning codes and plan to release them by the end of this month.


Fix async/await support for latest nightly

After https://github.com/rust-lang/rust/pull/50120 procedural macros do not receive the parentheses as part of their attributes TokenStream.
Also the proc_macro_non_items feature is necessary to use async_block.

Thanks!


Add Postman to Developer Tools

Highly recommended tool. Don't know why I left it earlier. Thanks anyway. Merged.


/* Program main Point which code for   ** You are working for a compa…

…ny that lays ceramic floor tile, and its employees need a program that estimates the number of boxes of tiles need for a job.** */
You are working for a company that lays ceramic floor tile, and its employees need a program that estimates the number of boxes
of tiles need for a job.
A job is estimated by taking the dimensions of each room in feet and inches, and converting those dimensions into a multiple of
the tile size (rounding up any partial multiple) before multiplying to get the number of tiles for the room.
A box contains 20 tiles, so the total number needed should be divided by 20 and rounded up to get the number of boxes. The tiles
are assumed to be square.
The program should initially prompt the user for the size of the tiles in inches and the number of rooms to be covered with tile. It
should then input the dimensions for each room in feet and inches.
After the dimensions for each room have been input then calculate and output the number of tiles needed for each room, the total
number of tiles needed for all rooms, the number of boxes of tiles needed, and how many extra tiles will be left over.
You should create a function called TilesInRoom that will take the size of one tile, and the width and length of a room and return
the number of tiles it will take to cover that room. The number of tiles should be rounded up to the nearest whole number.
Here is an example of how a run might appear:
Enter the number of rooms in the job: 2
Enter the size of each tile in inches: 12
Enter room 1 width (feet and inches, separated by a space): 17 4
Enter room 1 length (feet and inches, separated by a space): 9 3
Room 1 requires 161 tiles.
Enter room 2 width (feet and inches, separated by a space): 11 6
Enter room 2 length (feet and inches, separated by a space): 11 9
Room 2 requires 136 tiles.
The 2 rooms in this job will require 297 tiles.
The number of boxes of tiles needed is 15.
There will be 3 extra tiles left over.
Note: Do not assume that the instructor will enter only 2 rooms when testing your program.

For C language Program, contact with me


I can't find the equivelant of rowSums for spark dataframes

Hi everyone,
I am trying to create a new column that is the sum of different columns. This is possible using dplyr on an T data frame using rowSums(tbl[,n1:n2]).
When I tried it on a spark data frame, i got this error :
error in UseMethod("escape") :
no applicable method for 'escape' applied to an object of class "c('tbl_spark', 'tbl_sql', 'tbl_lazy', 'tbl')"
thank you so much for your help

@oghanmi Right, rowSums is currently not supported in sparkylr. Can you use mutate instead?
sc <- spark_connect(master = "local")
iris_tbl <- copy_to(sc, iris)
iris_tbl %>% mutate(y = Petal_Length + Petal_Width)

@javierluraschi Thank you for your answer. Actually we can sum differnt columns by indicating their names, i.e :iris_tbl %>% mutate(y = Petal_Length + Petal_Width)
It's only problematic when you have lots of columns  from n1 to n2 to sum.
Hope it will be available in the next release

It will be supported in the upcoming release of sparklyr 1.5.0.


clean install of conda python 3.7 rdkit rdkit for postgres on ubuntu 18.04 has boost version issues

demonstration of issue
psql --port=15432 my-rdkit-db
psql (11.2)
Type "help" for help.
my-rdkit-db=# create extension rdkit;
ERROR:  could not load library "/home/username/anaconda3/envs/my-rdkit/lib/rdkit.so": libboost_regex.so.1.65.1: cannot open shared object file: No such file or directory
versions of relevant things:
conda --version
conda 4.7.10
python --version
Python 3.7.3
uname -a
Linux iapetus 4.15.0-55-generic #60-Ubuntu SMP Tue Jul 2 18:22:20 UTC 2019 x86_64 x86_64 x86_64 GNU/Linux
boost is installed however a more recent version:
cd ~/anaconda3/envs/my-rdkit/lib
ls libboost_regex.so*
libboost_regex.so  libboost_regex.so.1.67.0
this workaround worked several weeks ago on another clean install.
try installing a prior version:
conda install -y boost=1.65.1 py-boost=1.65.1
Collecting package metadata (current_repodata.json): done
Solving environment: failed with current_repodata.json, will retry with next repodata source.
Collecting package metadata (repodata.json): done
Solving environment: failed
Initial quick solve with frozen env failed.  Unfreezing env and trying again.
Solving environment: failed
UnsatisfiableError: The following specifications were found
to be incompatible with the existing python installation in your environment:

boost=1.65.1 -> python[version='>=2.7,<2.8.0a0,>=3.6,<3.7.0a0']
py-boost=1.65.1 -> python[version='>=2.7,<2.8.0a0,>=3.6,<3.7.0a0']

If python is on the left-most side of the chain, that's the version you've asked for.
When python appears to the right, that indicates that the thing on the left is somehow
not available for the python version you are constrained to.  Your current python version
is (python=3.7).  Note that conda will not change your python version to a different minor version
unless you explicitly specify that.
The following specifications were found to be incompatible with each other:
Package setuptools conflicts for:
snip
a masive list of stuff **

This is a bug related to the rdkit-conda packaging, not the RDKit.
Please report future bugs of this type here:
https://github.com/rdkit/conda-rdkit


stuff despawn on a train and not keep rotation when disassembling a train.

bug report
list
all floodlight do not drop when mining with a pickaxe and can not be pick up with a wreach.
they do not keep the rotation when disassembling a train.
signs and letter sign despawn/remove when disassembling train even when the train is in the same position.
screws delete them self when a train disassemble in a different rotation.
cardboard, metal support, railings and diagonal girder does not keep it rotation when the train is disassemble in a different rotation

forgot to put the version of forge 1.20.1 and mod design_decor-0.4.0b


[translations] /rest_filters updates

Updates to rest_filters dir for translation. thanks to @AlanCoding for calling out during the work on this PR for making sure we don't translate when necessary (and also syntax checking me to make sure we are actually translating all that is needed).
Testing Steps

pull down PR branch and start dev virtual env
install django in virtenv if it is not already present (I believe it is but just in case)
pip freeze | grep Django
pip install Django
make a locale directory (makemessages looks for one and we don't have one configured yet so just create your own) mkdir locale
run the makemessages command check the output to see if strings were extracted correctly.
django-admin makemessages -l es
vim locale/es/LC_MESSAGES/django.po

Technically a WIP, spoke more @AlanCoding and need to change a few more things (but everything here is good for review)

Ignore the DAB Consumers failure, I've confirmed other PRs are seeing the same errors.


Iterators

I just tried array-from with the result of Map.prototype.keys(), and it does not seem to work (an empty list is returned). From a brief look at the source code, my guess is that it does not handle iterators, and as far as I understand it should.

Hi, we’ve actually just packaged code from the MDN, which was modelles after revision 22 – quite an old one. The spec for Array.from has changed once or twice since and we haven’t yet had the time to update.
Would you be willing to help? :) That’s the fastest way to push things forward.

I would be willing, but for now I have other things to do.

I think this can be closed as #3 has been merged

Wow, thanks for the cleaning up @JakeChampion!


ARIA Attributes Follow Best Practices

downshift version: 3.1.0
node version: 9.2
npm (or yarn) version: 5.6

Receiving the following errors while testing Downshift in Chromes Audit:

Elements with [role] that require specific children [role]s, are missing:

<button type="button" role="button" aria-label="open menu" aria-haspopup="true" data-toggle="true">nl</button>

[aria-*] attributes do not have valid values

<button type="button" role="button" aria-label="open menu" aria-haspopup="true" data-toggle="true">nl</button>

For error number 1, your failure comes from failing to supply an <input> element inside the
. A combobox needs a input to type into as its child. You may also be required to supply an aria-owns with the listbox ID if you plan to use the listbox outside the combobox div, but that is not the problem right now. Take a look at aria combobx to see how you should organize your HTML inside the downshift children function.
For error number 2, your failure comes from aria-labelledby="lang-switcher-label". The element with the ID you supplied as parameter does not exist probably.

@kentcdodds can we close this? unless you have something more to add.


Does not work without JavaScript

w3m https://logseq.com/ gets a user a blank page. Users with scripts disabled by default for security, also get nothing.
If the goal of a homepage is to be accessible and provide basic information to users, there shouldn't be a scripting requirement—nothing requires interactivity (use case tabbing, could just show all with scripts disabled). This tends to hurt SEO as well (only the Googlebot executes JavaScript).

Very good point to address

Is there any interest in migrating the code base to something like Next.js? I could try working on this.

We can go with astro + react for that astro for SSR or SSG + react for dynamic content also help in good SEO. I can help in that migration


docs: Fix typo

Fix a typographical error

thanks but I find the other version clearer: you can await anything


Sg/2024/04/15

Dataset Collections and "AggPlaces" (new approach)
#174

merged 23 Apr, 18:22

re: "Dataset contains features with null geometry, so cannot create ant-trails." Dataset collections should never have ant trails; they indicate motion and there is no motion involved. Datasets and Dataset Collection should have a single option (imho) time slider yes/no, which is stubbed in now on ds_status

when navigating to a dataset from a DC detail div, the detail div there shows 'Dataset" -- not necessary, as there is only one on that page

having the map zoom to views like this is not wonderful! zooming out some is better; not sure the rule to apply


Pin hatchling to 1.18

We eventually need to update build settings to adjust to https://github.com/pypa/hatch/issues/1113.

You need to provide something like this https://hatch.pypa.io/latest/config/build/#packages
Previously the wheel target had a fallback to include every Python file anywhere it could find that didn't look like a test file.

@ofek Looks like I needed both that and a force includes section to make sure that ./setup.py gets added as well.

I'll replace this PR with one that adds the newly required sections to the pyproject.toml.


is it Possible to fix location pin?

I need to fix location pin on a particular position and no one will able to change that if it is possible then let me know ASAP.

Well yes but this package is not built for that purpose. However, you can pass null or empty function () => {} to onChange prop so that the user won't be able to change the position given.


No current page on cursor based pagination

I am building an app with bi-directional infinite scrolling, where the user can scroll up through pages of old posts, and new posts occasionally appear on the opposite direction. There is currently no way to refetch the first page (as it was fetched without a cursor, to see if there are new pages added on the front. There is also the reverse use case which would be refetching the last page to see if new pages have been added on the end.
sqlakeyset supports this with:
page.paging.bookmark_current
page.paging.bookmark_current_backwards

Can this get added to the cursor paginated response?

I posted a PR- let me know its missing anything or needs adjustment. Thanks @uriyyo!