powershellgallery: returns Invalid Response Data when package with highest version is unlisted

Are you experiencing an issue with...

[X] shields.io
[ ] My own instance
[ ] gh-badges NPM package

:beetle: Description
The version and download count badge shows invalid response data for package PoShGroupPolicy.
The latest version (1.0) status is Unlisted, while the current version (0.3) is Listed. I actually published the 1.0 first and was not able to delete it.

curl -H "Accept: application/atom+xml,application/xml" "https://www.powershellgallery.com/api/v2/Packages()?%24filter=Id%20eq%20'PoShGroupPolicy'%20and%20IsLatestVersion%20eq%20true"

I suspect this to be a limited, perhaps even rare, scenario. I'm only raising the issue for general awareness and do not expect any work to be done, unless the maintainers feels it's warranted.

Also, thank you for closing #2078.

:link: Link to the badge
https://img.shields.io/powershellgallery/dt/PoShGroupPolicy.svg?style=for-the-badge
https://img.shields.io/powershellgallery/v/PoShGroupPolicy.svg?style=for-the-badge

Hi, thanks for the detailed report!
Here's the output of that request (which is still failing):
{
  "feed": {
    "id": "http://schemas.datacontract.org/2004/07/",
    "title": "",
    "updated": "2018-11-17T02:31:51Z",
    "link": "",
    "entry": {
      "id": "https://www.powershellgallery.com/api/v2/Packages(Id='PoShGroupPolicy',Version='0.3.0')",
      "category": "",
      "link": [
        "",
        ""
      ],
      "title": "PoShGroupPolicy",
      "updated": "2018-11-12T12:00:39Z",
      "author": {
        "name": "Dave Carroll"
      },
      "content": "",
      "properties": {
        "Id": "PoShGroupPolicy",
        "Version": 0.3,
        "NormalizedVersion": "0.3.0",
        "Authors": "Dave Carroll",
        "Copyright": "(c) 2018 Dave Carroll. All rights reserved.",
        "Created": "2018-03-24T04:18:50.567",
        "Dependencies": "",
        "Description": "PowerShell module to assist with Group Policy",
        "DownloadCount": 136,
        "GalleryDetailsUrl": "https://www.powershellgallery.com/packages/PoShGroupPolicy/0.3.0",
        "IconUrl": "",
        "IsLatestVersion": true,
        "IsAbsoluteLatestVersion": true,
        "IsPrerelease": false,
        "Language": "",
        "LastUpdated": "2018-11-12T12:00:39.567",
        "Published": "2018-03-24T04:18:50.567",
        "PackageHash": "g2SYyk4/wfa3v0M4fyloM8Vi+lB2Awe5+bfzMGYjH4GCoNmn1VggyiW+CNbKkyHkCBcpKhMWjpelQpHEPzhUYw==",
        "PackageHashAlgorithm": "SHA512",
        "PackageSize": 11761,
        "ProjectUrl": "https://github.com/thedavecarroll/PoShGroupPolicy",
        "ReportAbuseUrl": "https://www.powershellgallery.com/packages/PoShGroupPolicy/0.3.0/ReportAbuse",
        "ReleaseNotes": "https://github.com/thedavecarroll/PoShGroupPolicy/blob/master/RelaseNotes.md",
        "RequireLicenseAcceptance": true,
        "Summary": "",
        "Tags": "PoshGroupPolicy GroupPolicy Group-Policy PowerShell GPO PSModule PSFunction_Get-GPSetting PSCommand_Get-GPSetting PSIncludes_Function",
        "Title": "",
        "VersionDownloadCount": 129,
        "MinClientVersion": "",
        "LastEdited": "",
        "LicenseUrl": "https://github.com/thedavecarroll/PoShGroupPolicy/blob/master/LICENSE",
        "LicenseNames": "",
        "LicenseReportUrl": "",
        "ItemType": "Module",
        "FileList": "PoShGroupPolicy.nuspec|LICENSE|PoShGroupPolicy.Format.ps1xml|PoShGroupPolicy.psd1|PoShGroupPolicy.psm1|README.md|ReleaseNotes.md|en-US\\about_PoShGroupPolicy.help.txt|Private\\Get-GPKnownFolderId.ps1|Public\\Get-GPSetting.ps1",
        "GUID": "fa6fcad4-9c3f-4258-8475-bbf11060b779",
        "PowerShellVersion": 3,
        "PowerShellHostVersion": "",
        "DotNetFrameworkVersion": "",
        "CLRVersion": "",
        "ProcessorArchitecture": "",
        "CompanyName": "Unknown",
        "Owners": "thedavecarroll"
      }
    }
  }
}

Having a similar issue for one of my projects:
https://github.com/EvotecIT/Statusimo
https://www.powershellgallery.com/packages/Statusimo
Any way to get this fixed?

Just wanted to put out there that Shields is a community project, and that means if you're reading this, you can can help make this happen! 👐 We'd welcome anyone who would like to dig into this! Our maintainer team is happy to review code and answer questions (feel free to post in Discord, or right in this thread). We've worked hard to create a good developer experience for first-time contributors, and gotten many positive reports, including from some first-time JavaScript developers.

@paulmelnikow I understand but without pointers I can't really help ;-) And even with pointers it seems to be JS mostly which I don't know :-) like at all.


Remotely Accessible Home Automation Dashboard

To remotely access the Dashboard, there should be REMOTE URL option in "Browser" along with DASHBOARD ADDRESS.
In Dashboard Address, we can enter local IP address to access dashboard when in local WiFi while in remote URL, we can enter cloud URL
so that if local IP is not reachable then it should redirect to remote URL.
This feature would be beneficial for openHAB users where they can use remote cloud URL like https://demo.openhab.org:8443/start/index  to access remotely.
For HA users, they can use local IP as well as DynamicDNS host name.
WHAT CHANGE NEEDS TO BE DONE:
When user access their Dashboard activity, first ping to local IP, if not reachable/error then redirect to remote URL.

Interesting, not sure when we might have time to complete this, but we can mark it as a feature request.


feat: Lydia/backport min commish onelasttime

Cosmos-sdk v0.45.4 is necessary for Chihuahua, but minimum commission is not built in until v0.46 of the sdk.
Backport the minimum commission from #10529 into v0.45.4

The two tests that failed here "Tests/Code Coverage/test-rosetta" and "Protobuf/breakage" were also broken in #2 , so we should still be good to merge.


Interface not working correctly when NanoDLP password is set.

Interface stops working if you set up a password on NanoDLP. Plates do not show up ("Undefined") and commands do not work (Z-axis, etc).
Looks like authentication needs be implemented. This should mean adding user/pass parameters to the HTTP request or using a cookie.
I'm new to node.js, but I could try to help adding it. I guess it should be in the "_request" function.

Hello, never tested the authentication on NanoDLP. It could be a problem indeed. Don't have time now so feel free to add it and make a pull request ;D

Working on it, I already figured out part of the process. Just a question, what is the difference between src and bin folders? Should I change files in /bin?

/bin folder are build from /src with gulp so you need to install node, gulp in global and run gulp work and every file in /src folder will be build in /bin when you edit a file.

Thanks.
A question: which version of nodejs have you been using? I get a compile error when I run gulp, both in Windows and in Ubuntu.
In both cases I did the same: first I installed nodejs and then gulp with needed dependencies:
npm install --global gulp-cli
Then inside the cloned project dir:
npm install --save-dev gulp
npm install gulp-plumber gulp-babel babel-core del array-includes
When I try to run gulp work I get the following output:

Using gulpfile ~/Sources/PHD/TouchScreen-For-NanoDLP/gulpfile.js
[13:47:03] Starting 'build-compile'...
[13:47:03] Finished 'build-compile' after 10 ms
[13:47:03] Starting 'build-copy'...
[13:47:03] Finished 'build-copy' after 1.92 ms
[13:47:03] Starting 'build'...
[13:47:03] Finished 'build' after 14 μs
[13:47:03] Starting 'watch'...
[13:47:03] Finished 'watch' after 33 ms
[13:47:03] Starting 'work'...
[13:47:03] Finished 'work' after 1.68 μs
[13:47:03] [Compilation Error]
[13:47:03] Plugin 0 specified in "base" was expected to return an object when invoked but returned "boolean"base0
[13:47:03] [Compilation Error]
[13:47:03] Plugin 0 specified in "base" was expected to return an object when invoked but returned "boolean"base0

Same compilation error is repeated about 20 times, I cut the output. Possibly a nodejs version incompatibility? Any other hints?
PS: module array-includes is not set as required in gulpfile.js, but if missing throws a compile error; I will also add the requirement in the pull request.

I merged it today. Will make a new realease with other bug fix asap


Added status badges to README

Issue
This repo's status is not displayed in the Charm Engineering Releases overview.
Solution
Added workflow badges for

Publish ROCK
Operator Tests

@a-velasco duplicate of https://github.com/canonical/mysql-router-container/pull/17 ?
Resolved to archive the repo (no longer in use).


feat: Add Hono utilization documentation

This commit introduces documentation for the Hono web framework. It includes a new file hono.mdx which provides an example of how to use Hono with typia. Additionally, it updates the _meta.json file to include Hono in the list of technologies.
Before submitting a Pull Request, please test your code.
If you created a new feature, then create the unit test function, too.
# COMPILE
npm run build

# RE-WRITE TEST PROGRAMS IF REQUIRED
npm run test:template

# BUILD TEST PROGRAM
npm run build:test

# DO TEST
npm run test

Learn more about the CONTRIBUTING

Hono is really popular right now!
Try it!


feat(core-api): read-only and distortion proxies of plugins

Description
As a Cactus operator I want to have safety measures in place when importing a plugin, ensuring that if said plugin turns out to be malicious it will not be able to steal sensitive information from other plugins such as private keys used by a validator plugin for example so that I can have peace of mind (or at least a little less anxiety) about installing new plugins to my Cactus deployment.
https://github.com/salesforce/observable-membrane
Acceptance Criteria

A test case showing two plugins having only read-only access to each other's read-only properties
Test case for distortion where dummy malicious plugin tries to access the privateKeyHex property of some other plugin instnace that it acquired through the plugin registry and failing (e.g. distortion ensures real private key is hidden and the proxy accessor returned some garbage instead).

cc: @cliveb @jonathan-m-hamilton @takeutak  @sfuji822

Added a test case on the PoC branch that can be executed like this:
npx tap packages/cactus-core-api/src/test/typescript/unit/plugin-registry/plugin-proxies-security.test.ts

Currently it fails, so it's a work in progress for now.

Found the root cause: All the plugins are instances of ES6 classes and those are not supported [1] by the membrane implementation.
Potential solution is to just bite the bullet and use raw JS objects instead of ES6 classes for plugins, but that would not be my first choice because then we lose the upside of having ES6 classes to begin with: for example ability to identify instances of a certain class without arbitrary discriminator properties on objects, identify inheritance chains, etc.
[1] https://github.com/salesforce/observable-membrane/issues/42

This restriction is on purpose. The main issue with observing objects that don't inherit from the Object.constructor or null is that it introduces unexpected behaviors related to the this value.

I gathered there may be an ES6 shim available pending ratification of Dr. SES and Frozen Realms or its successors SES and Realms et al. Perhaps @erights could point Cactus Dev to a shim to secure keys in plugins, and we can help by ratifying the shim for TC39, with the DLT integration use case?

For reference v2 presentation on ES membranes. I recall v1 was presented to TC39 quarterly meeting by @ajvincent invited talk by Mark S. Miller. In retrospect, I need to read-up and look around before asking for help.
https://docs.google.com/presentation/d/1r0e_jPnGqPyT_q07p7jtHnD-dMV2ONN68Jc9FVze-XY/edit#slide=id.g3e0e1ea5fb_0_106

Need to re-evaluate if the observable-membrane package has added support for ES6 classes in the meantime. If yes, this task is in a good shape to get some work done on it, otherwise the complexity is still undetermined (as in unbounded) because we don't yet have the tooling (e.g. library support) for accomplishing what we are trying to do.

Apparently, Metamask has implemented SES shim to contain ES6 classes. While TC39 continues to consider proposals to implement. Given the SolarWinds reckoning with NPM supply-chain hacks, it looks like tooling or standards changes are unavoidable. More a question of when they arrive and what are the risks of waiting vs shimming. That Catus is targeted at enterprise permissioned blockchain integration, perhaps risks are limited to the NPM chain used in plugins. I wonder if we should roll the concern over to the academic Cactus paper under the topic of "Robust Composition" and close this PR. IDK.
Video on Metamask securing NPM for web3 graphs the risks at 15:23 mins.
https://www.youtube.com/watch?v=vPGnJf3e9DA

Apparently, Metamask has implemented SES shim to contain ES6 classes. While TC39 continues to consider proposals to implement. Given the SolarWinds reckoning with NPM supply-chain hacks, it looks like tooling or standards changes are unavoidable. More a question of when they arrive and what are the risks of waiting vs shimming. That Catus is targeted at enterprise permissioned blockchain integration, perhaps risks are limited to the NPM chain used in plugins. I wonder if we should roll the concern over to the academic Cactus paper under the topic of "Robust Composition" and close this PR. IDK.
Video on Metamask securing NPM for web3 graphs the risks at 15:23 mins.
https://www.youtube.com/watch?v=vPGnJf3e9DA

@cliveb Thank you for that treasure trove of information of a comment! I see that SES is a stage 1 TC39 proposal (early days) but I think even with that, as long as there's a working implementation we have no excuse but to try and work on this, knowing full well that in the future we might need to re-work it if the stable version of the proposal will end up with a different API. So as far as my own time/opinion goes, I'll just keep this open and slowly but surely chip away at the problem, even if it's an uphill battle right now. Thanks again for the support/ideas/info, I wouldn't even know about membranes/SES' existence if it wasn't for you!
Note to self: invest some time into triaging the SES-shim: https://github.com/Agoric/SES-shim and take it from there.

Realms currently at stage 2. https://github.com/tc39/proposal-realms
Unsure details of SES and Realms are equivalent.

Hi @cliveb !
The original SES proposal has split into Realms, Compartments, and SES. Historically, SES and Frozen Realms were coupled. The Realms portion of Frozen Realms split into the modern Realms and Compartments.
They are closely related and the people involved have a heavy overlap. However, we've managed to minimize dependencies so these can proceed in standardization mostly independently.

The "Frozen" aspect of "Frozen" realms remains in SES as lockdown and harden, and does not appear in Realms or Compartments.

@erights clears up. Nice work.
cc @petermetz LavaMoat uses SES https://github.com/LavaMoat/

Hello/
author of LavaMoat here
I think the observable-membrane package is not built to be secure. I looked at it when building my membrane implementation Cytoplasm https://github.com/LavaMoat/cytoplasm
However I ultimately abandoned it due to severe performance impact (I've seen 300x slowdown) and some other design issues
Membranes are really neat but I've lost some hope on their practicality.
That said, I think you can get a lot of security without them by using SES. Welcome to your new favorite rabbit hole 🐇

@erights @cliveb @kumavis Thank you all, it's starting to make a lot more sense now big-picture wise. This will help me a lot once I get started up on this task again (currently neck deep in another one).

Welcome to your new favorite rabbit hole rabbit2

Definitely made me chuckle. :-) Can't go back up now... gotta go deeper! :-)

https://github.com/petermetz/cactus/tree/feat/core-api%2Fin-process-plugin-isolation-253


[Bug]: IPX fails with type: module in package.json

Summary
This bug has been filed as a response to the ticket: https://netlify.zendesk.com/agent/tickets/82173 (internal only).
The user has a monorepo with the following package.json:

Monorepo package.json
{
  "name": "5starz",
  "version": "1.0.0",
  "license": "MIT",
  "type": "module",
  "engines": {
    "node": ">=16.0.0"
  },
  "dependencies": {
    "prettier": "^2.4.1",
    "ts-node": "^10.4.0",
    "typescript": "^4.5.2"
  },
  "devDependencies": {
    "@netlify/plugin-nextjs": "^4.2.2",
    "@types/lodash": "^4.14.177",
    "@types/node": "^16.11.9",
    "cross-env": "^7.0.3",
    "env-cmd": "^10.1.0",
    "tsc-watch": "^4.6.0"
  },
  "scripts": {
    "restart:backend": "docker build -f backend2/Dockerfile -t the5starz-backend:0.2.2 . && (cd deploy/compose/ && docker-compose down && docker-compose up -d)",
    "staging:check": "docker build -f backend2/Dockerfile -t the5starz-backend-staging:0.2.4 . && (cd deploy/staging/ && docker-compose down && docker-compose up)",
    "logs:backend": "cd ~/the5starz/deploy/compose && docker-compose logs",
    "build:front": "yarn workspace @the5starz/common build && yarn workspace front build",
    "build:website": "yarn workspace @the5starz/common build && yarn workspace website build",
    "build:backend": "yarn workspace @the5starz/common build && yarn workspace @the5starz/db generate && yarn workspace @the5starz/db build && yarn workspace backend2 build",
    "clean-npm": "yarn cache clean && rm -rf ./*/yarn.lock && rm -rf */package-lock.json && rm -rf yarn.lock && rm -rf package-lock.json && rm -rf ./*/node_modules/ && rm -rf node_modules",
    "test": "./node_modules/.bin/ts-node --transpile-only scripts/old/json-transform-test.ts",
    "get-s3-files": ""
  },
  "private": true,
  "workspaces": {
    "packages": [
      "db",
      "backend2",
      "front",
      "scripts",
      "common",
      "website",
      "apify"
    ]
  },
  "volta": {
    "node": "16.13.1",
    "yarn": "1.22.17",
    "npm": "8.2.0"
  }
}

Their Next.js website has the following package.json:

Next.js `package.json`
{
  "name": "website",
  "version": "0.1.0",
  "private": true,
  "scripts": {
    "dev": "next dev",
    "build": "next build",
    "start": "next start",
    "lint": "next lint",
    "storybook": "start-storybook -p 6006 -s ./public",
    "build-storybook": "build-storybook -s public"
  },
  "dependencies": {
    "@headlessui/react": "^1.4.2",
    "@heroicons/react": "^1.0.5",
    "@mdx-js/loader": "^1.6.22",
    "@next/mdx": "^12.0.10",
    "axios": "^0.25.0",
    "next": "12.0.7",
    "react": "17.0.2",
    "react-countup": "^6.1.0",
    "react-dom": "17.0.2",
    "react-grid-gallery": "^0.5.5",
    "react-hook-form": "^7.25.0",
    "react-icons": "^4.3.1",
    "react-player": "^2.9.0",
    "react-slick": "^0.28.1",
    "react-visibility-sensor": "^5.1.1",
    "slick-carousel": "^1.8.1"
  },
  "devDependencies": {
    "@babel/core": "^7.16.12",
    "@storybook/addon-actions": "^6.4.14",
    "@storybook/addon-essentials": "^6.4.14",
    "@storybook/addon-links": "^6.4.14",
    "@storybook/react": "^6.4.14",
    "autoprefixer": "^10.4.2",
    "babel-loader": "^8.2.3",
    "eslint": "8.6.0",
    "eslint-config-next": "12.0.7",
    "eslint-plugin-storybook": "^0.5.6",
    "postcss": "^8.4.5",
    "tailwindcss": "^3.0.13"
  }
}

The generated _ipx.zip is attached: _ipx.zip
Steps to reproduce
N/A
A link to a reproduction repository
N/A
Plugin version
4.2.2
More information about your build

[ ] I am building using the CLI
[X] I am building using file-based configuration (netlify.toml)

What OS are you using?
No response
Your netlify.toml file
N/A
Your public/_redirects file
N/A
Your next.config.js file
N/A
Builds logs (or link to your logs)
https://app.netlify.com/sites/the5starz-website/deploys/61fa7a6e5c4d41000836be19
Function logs

Function logs (_ipx)
{
  "errorType": "ReferenceError",
  "errorMessage": "module is not defined in ES module scope\nThis file is being treated as an ES module because it has a '.js' file extension and '/var/task/package.json' contains \"type\": \"module\". To treat it as a CommonJS script, rename it to use the '.cjs' file extension.",
  "trace": [
    "ReferenceError: module is not defined in ES module scope",
    "This file is being treated as an ES module because it has a '.js' file extension and '/var/task/package.json' contains \"type\": \"module\". To treat it as a CommonJS script, rename it to use the '.cjs' file extension.",
    "    at file:///var/task/_ipx.js:1:1",
    "    at ModuleJob.run (internal/modules/esm/module_job.js:183:25)",
    "    at process.runNextTicks [as _tickCallback] (internal/process/task_queues.js:60:5)",
    "    at /var/runtime/deasync.js:23:15",
    "    at _tryAwaitImport (/var/runtime/UserFunction.js:74:12)",
    "    at _tryRequire (/var/runtime/UserFunction.js:162:21)",
    "    at _loadUserApp (/var/runtime/UserFunction.js:197:12)",
    "    at Object.module.exports.load (/var/runtime/UserFunction.js:242:17)",
    "    at Object.<anonymous> (/var/runtime/index.js:43:30)",
    "    at Module._compile (internal/modules/cjs/loader.js:1085:14)"
  ]
}

.next JSON files
N/A

I'm having the same issue with images not loading using the Next/Image component. Are there any updates or fixes for this? It's also referenced in another thread: https://github.com/netlify/next-runtime/issues/1456#issuecomment-1199149379

@orinokai mentioned in the closed PR that Netlify is currently testing an update to the Next.js Runtime that will address this issue and will have some information to share soon 🎉

https://github.com/netlify/next-runtime/pull/1886#issuecomment-1903573857

The team at Netlify have now released the new v5 Next.js runtime which has support for both pages and app router, on-demand and time-based revalidation, automatic fine-grained cache control, and automatic image optimization using Netlify's image CDN. Please try your Next sites with this as it removes the need for ipx.
You can find the documentation and additional information here: Next.js on Netlify
The v4 runtime is now in the maintenance support phase with no new features being added. Occasional bug fixes and security patches will be applied when needed.
Thanks!


bump shellcheck to v0.10.0

Shellcheck had its first release since 2022, so bump it.

/hold
needs project-infra change as well.

/approve

/unhold
Project-infra has gone in.
/test shellcheck

/cc @mboukhalfa @Rozzii


Lua syntax highlighting for GitHub.

Now that the python build script is merged GitHub seems to think this is a Python repository. By including a .gitattributes file we can make all the .p8 files show up as Lua (and we get syntax highlighting).

That sounds great - but b4 I merge, I'm not seeing the syntax highlighting in your branch, e.g.
https://github.com/benwiley4000/scumm-8/blob/lua-linguist/src/scumm-8.p8

...shouldn't I see the highlighting here?


XUID

Hi!
Is it possible to use this plugin without connection to XUID? When I try to connect to the server without XboxAuth, it crashes.

Also have a question, how to connect balance and ScoreHud plugin?

https://github.com/cooldogepm/BedrockEconomy/issues/127


Shape of the detections

https://github.com/rwightman/efficientdet-pytorch/blob/52279b43acfa1b2a653ad74c9dc8bf8ee991cbcf/effdet/anchors.py#L127
I guess the generate_detections function in anchors.py returns the shape [Max_DET_PER_IMAGE, 6] and not [MAX_DETECTION_POINTS, 6]

Also, I am training, validating and testing (evaluating) my dataset having 1 class. In the detections, generated by the model I always see the classes == 1 in the output [x, y, x2, y2, score, class].
Can anyone throw a light if it is wrong?


cannot define PROLEPTIC_GREGORIAN calendar with T0 on Feb 29th

Reading FERRET documentation, proleptic_gregorian calendar accounts for leap years.
However, basing a new axis with this calendar on Feb 29th does not work:
yes? de ax/t0="29-FEB-2000"/units=seconds/cal=proleptic_gregorian pgtest = l[l=1:100]
 **TMAP ERR: error in time line definition
             29-FEB-2000 is not valid in this calendar
 **ERROR: improper grid or axis definition: /T0=29-FEB-2000

Is this by design or a bug?

With current versions of PyFerret, this command works.  It may have been a bug in some Ferret versions.


Copy & paste mistake in README

You can find implementations of the specification by looking for packages providing the psr/simple-cache-implementation virtual package.

This should be adjusted to the right package name.

Thanks


BugFix fix DataTypeArray to_string use after free

ColumnArray::convert_to_full_column_if_const override the base function
and ColumnArray::create generate a temporary variable
Proposed changes
Issue Number: close #10638
Problem Summary:
Describe the overview of changes.
Checklist(Required)

Does it affect the original behavior: (Yes/No/I Don't know)
Has unit tests been added: (Yes/No/No Need)
Has document been added or modified: (Yes/No/No Need)
Does it need to update dependencies: (Yes/No)
Are there any changes that cannot be rolled back: (Yes/No)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

LGTM


Use mocha instead of jest in markdown-docx

Feature Request 🛍

Use mocha to execute tests in markdown-docx instead of jest .
Use Case

Mocha gives a clearer output of what tests passed. Eg.
Mocha

Jest

Possible Solution

Put all the tests in test directory.
Change npm test script to mocha instead of jest.

@algomaster99
I was able to convert all but one test file to run with mocha. It is primarily due to the fact that it uses a snapshot test.

Mocha does not support snapshot testing itself so I am using this package
The snapshots are created already. I have not touched it.
I tried moving snapshots outside of src(in the root) and running but got the same error.

Don't add this package. Instead, skip that test. I am quite sure that the DocxTransformer will be deleted in the future.


Add howtos for connecting statsig wn to bigquery/snowflake

🚀 Deployed on https://645c407f9b7ec831b1717512--cozy-fox-0defec.netlify.app


[fix] Fix for dlwp_healpix dataloader not subsetting channels correctly

Modulus Pull Request
Description
Fixes a bug where the dlwp_healpix dataloader uses a prebuilt dataset with more channels than used by the model. This fix adds channel selection so only the necessary channels are loaded.
Checklist

[x] I am familiar with the Contributing Guidelines.
[x] New or existing tests cover these changes.
[x] The documentation is up to date with these changes.
[x] The CHANGELOG.md is up to date with these changes.
[x] An issue is linked to this pull request.

/blossom-ci

/blossom-ci

/blossom-ci

/blossom-ci

/blossom-ci

@daviddpruitt is this ready to be merged?

/blossom-ci

@daviddpruitt is this ready to be merged?

@mnabian Should be good to go.

/blossom-ci


NPM support

Please add package to NPM repository.
Than the DIST folder should contains only the 2 output files picker.js/picker.css without the demo site sources.
Thanks in advance!

I will add it npm however instead of dist folder those two files are in src folder .

added to npm. check and confirm

It works well, thanks.
It would be also nice to have a feature of setting time seconds.
It is quite easy to implement, one just need to clone all minutes relevant code parts.

Create issue for seconds selection, I will add in version 2.0.0


How to disable Analytics in Images URL

Where do I place this code to disable Analytics; basically I do not want to have ?= at the end of my Image URL
url: {
    secure: true,
    analytics: false,
  }

configuration parameters
const cloudinaryMedia = new Cloudinary({
  cloud: {
    cloudName: "cloud",
  },
  url: {
    secure: true,
    analytics: false,
  },
});

hey @mohdlatif i dont believe this currently isn't supported, but we can work on adding this as an option

hey @mohdlatif i dont believe this currently isn't supported, but we can work on adding this as an option

Thank you

Hey, @mohdlatif @colbyfayock
Yes, I can work on adding that optional cloudinary analytics :)

@colbyfayock
During the implementation I have discovered that even when I dont pass any analytics object, analytics ID is still being sent.
Analytics enabled
https://res.cloudinary.com/nuxt-cloudinary/image/upload/f_auto/q_auto/v1//cld-sample-5.jpg?_a=BATFIJa20

Analytics disabled
https://res.cloudinary.com/nuxt-cloudinary/image/upload/f_auto/q_auto/v1//cld-sample-5.jpg?_a=BBDAACAD0

You can check it in the code here https://github.com/nuxt-modules/cloudinary/pull/174
Do you think this could be something implemented in the cloudinary url loader or should I strip final url from this default analytics ID?

@Baroshem i believe the URL Gen SDK by default adds its own tracking parameters, much like any newer Cloudinary SDK, which is the point (just like the use here)
this is a separate point however from disabling analytics, as its intentional for it to be on by default, which is why by default you pass in the tracking parameters as you do
when disabling, there was an inconsistency where if you pass in the config.url.analytics value as false, the underlying SDK would respect that and turn it off, however passing in the 3rd option as false would not
here's a fix to address that, as you can also see the tests in teh behavior added: https://github.com/colbyfayock/cloudinary-util/pull/101
before merging that, am i missing anything?

@colbyfayock @mohdlatif
I just looked at your PR at Cloudinary Util and realised that it is actually possible to disable analytics in useCldImageUrl composable by passing props.config.url.analytics: false even without my PR like so:
const { url } = useCldImageUrl({
  options: { src: "/cld-sample-5.jpg" },
  config: { url: { analytics: false } },
});

And you can also pass it as a prop to the CldImage.vue component like so:
  <CldImage
    src="cld-sample-5"
    :config="{ url: { analytics: false } }"
  />

Which will result in creating following url:
https://res.cloudinary.com/nuxt-cloudinary/image/upload/c_fill,w_987,h_987,g_auto/f_auto/q_auto/cld-sample-5

So I am not sure if both yours and my PR's are needed

if im understanding the code right, one thing i like is having the option in a globally configurable way through nuxt.config, is that correct? id like to do that in nextjs but there isn't a reliable pattern that they promote, so itd be somewhat at my own risk to implement, still figuring that out (they recommend wrapper components :/)
this could be spun up in another ticket, but being able to provide global cloudinary configurations would be great, including anything you see in that config object, including cnames and such, where perhaps the API then would be:
cloudinary: {
  config
}

to be extra explicit about its intent
the other consideration is that using Object assign with a value of false wouldn't work as epxect in my proposed PR
analytics: Object.assign({
  sdkCode: 'D',
  sdkSemver: `${pkg.version.split('.')[0]}.0.0`,
  techVersion: `${nuxtPkg.version.split('.')[0]}.0.0`,
  product: 'B'
}, props.analytics)

so id expect this not to work:
const { url } = useCldImageUrl({
  options: { src: "/cld-sample-5.jpg" },
  analytics: false
});

FYI merged my PR in from Cloudinary Util https://github.com/colbyfayock/cloudinary-util/pull/101

Will be added as a part of 2.5.0 release with following commit :)
https://github.com/nuxt-modules/cloudinary/pull/173/commits/0f8df15ab84afc90b37f9e07660b79beaa7c5da2


Spuriously disappearing extension

Cf. #39262. The common front end seems to consider the existence of an extension as a conflict when it is both declared in the current library and also imported, and the extension is then considered as non-existing (not duplicated).

Duplicate of #39160. Fix in https://dart-review.googlesource.com/c/sdk/+/123523


services.nginx: Use $scheme for globalRedirect.

Issue description
Right now the nginx service does prepend http or https (depending on enableSSL) to the value of globalRedirect. Nginx supports the $scheme variable to automatically use whatever the current context uses. Is there any reason why we're not using it?

Probably because I didn't think of it :sweat_smile:

(triage) @globin fixed?

(triage) close?


SMT from conda-forge

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (2b9ff8d) 97.68% compared to head (be87c84) 97.68%.
Report is 1 commits behind head on main.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #66   +/-   ##
=======================================
  Coverage   97.68%   97.68%
=======================================
  Files          11       11
  Lines         949      949
=======================================
  Hits          927      927
  Misses         22       22

Flag
Coverage Δ

unittests
97.68% <ø> (ø)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

This PR

Installs smt from conda-forge
smt was somehow not recognized by the typical miniconda-setup action
so switched to micromamba, which is much faster anyway
Critically important for micromamba to work: for micromamba to use the right python install for the python -m pip install -e . --no-deps step, had to specify shell: micromamba-shell {0} but maybe another shell would work as well

Note that these are the backends and versions that work with PEP 660 (i.e. pyproject.toml)


"This pull request is broken due to missing fork information." after pushing

Description
I have been using Gitea 1.20.2 for over a year now and recently I started to get "This pull request is broken due to missing fork information" on my pull requests. I can still interact with my repositories in the normal way
I then updated Gitea to 1.21.11 and the issue persisted. I have tried going to the dashboard and:

Update the '.ssh/authorized_keys' file with Gitea SSH keys.
Update the '.ssh/authorized_principals' file with Gitea SSH principals.
Resynchronize pre-receive, update and post-receive hooks of all repositories.

Gitea Version
1.21.11
Can you reproduce the bug on the Gitea demo site?
No
Log Gist
No logs are generated for gitea/log and log in the gitea directory, so I'm not sure what log to include
Screenshots

Git Version
2.44.1
Operating System
NixOS 24.05.20240803.a633d89 (Uakari)
How are you running Gitea?
Using the gitea module from NixOS's configuration.nix
Database
PostgreSQL

Have you tried to refresh multiple times?

Have you tried to refresh multiple times?

Do you mean refreshing the browser? It didn't work

The problem is gone for now after I merged the branches into each other a bit. I don't know what caused it in the first place.


Fix doc problem about azure-spring-boot-starter-active-directory in samples

Purpose
Related issue: https://github.com/azure/azure-sdk-for-java/issues/23876
Does this introduce a breaking change?

[ ] Yes
[ x] No

Pull Request Type
What kind of change does this Pull Request introduce?

[ ] Bugfix
[ ] Feature
[ ] Code style update (formatting, local variables)
[ ] Refactoring (no functional changes, no api changes)
[x ] Documentation content changes
[ ] Other... Please describe:

How to Test

Get the code

git clone [repo-address]
cd [repo-name]
git checkout [branch-name]
npm install

Test the code

What to Check
Verify that the following are valid

...

Other Information

In Azure-SDK-for-java 4.0.0, we will remove the function about group. Should we deprecated the related content?
aad-resource-server-by-filter can't remove the admin consent because no consent can be presented via a UI and accepted to use the service app and which don't support the appRole.
For stateless, which just means SecurityContextHolder doesn't store the user info(compared the AADAppRoleStatelessAuthenticationFilter and AADAuthenticationFilter), and both of them have been deprecated and will be removed in 4.0.0.

Hi, @michaelqi793 , could you please help to review this PR?


Support xlsx upload for measurement metadata registration

Solves #677

Regarding measurement editing: I followed the steps detailled in the documentation. However when I
1. Download the measurement metadata
2. Clear rows at the end by selecting them and pressing backspace on my keyboard
3. Save the XLSX file
4. Upload the edited XLSX file

I was able to reproduce it and included another method for the Sanitizer to be able to filter out empty rows for both TSVParser and XLSXParser.


Confusing docs for EC2 Security Group self option

The docs for EC2 Security Group rules about the self option are a bit confusing.
File: themes/default/content/registry/packages/aws/api-docs/ec2/securitygroup/_index.md
It is currently the same (wrong for both versions) description:

Whether the security group itself will be added as a source to this egress rule.

For the egress it should be

Whether the security group itself will be added as a destination to this egress rule.

...and for the ingress it should be:

Whether the security group itself will be added as a source to this ingress rule.

Update: After digging into this, I come to the conclusion that unless I am mistaken about this resource type the upstream docs are correct. I'll find out the correct place to address and fix this.
Thank you again for reporting.

Update update: After talking to the team, it turns out this is a known bug and we're tracking it in https://github.com/pulumi/docs/issues/6854.

Closing as a duplicate of https://github.com/pulumi/pulumi-terraform-bridge/issues/529
Once the core issue is solved this will be fixed on the next upgrade of the TF bridge.


Istio 1.16.4 returning GRPC Unavailable instead of deadline exceeded

Is this the right place to submit this?

[X] This is not a security vulnerability or a crashing bug
[X] This is not a question about how to use Istio

Bug Description
Context: We are upgrading from Istio 1.14.1 to 1.16.4 in all our k8s clusters. While this version is soon going to be out of scope for support (June 2023), we're working our way up the revisions. In the service mesh, we have a microservice that issues outbound GRPC requests to our monolith (outside EKS). There is a valid service entry for this monolith but no virtual service.
The microservice has historically managed its own GRPC backoff and retry behaviour and set deadlines without using any Istio config to do so. (Nothing configured explicitly in terms of CRDs / no config for Envoy Route objects). These outgoing requests contain a  grpc timeout header (set to 150ms)  and the service gracefully deals with deadline exceeded errors (GRPC status code 4).
Upon moving to Istio 1.16.4, we noticed a low volume of errors where when a deadline is reached, the Istio sidecar proxy reports: UT upstream request timeout  with a GRPC Unavailable (status code (14)) error.  This unexpected change correlates with the upgrade:
Digging further:

This commit moved away from using maxStreamDuration to maxGrpcTimeout exclusively and got picked up in our upgrade.
However, as a result of this move - there seems to be a side effect on how global timeouts are configured. If I'm reading this correctly, we're now going down this branch in envoy itself where the global timeout is being set to whatever is in the header (150ms). With Istio 1.14.1 (via maxStreamDuration and GrpcTimeoutHeaderMax set to 0) the global timeout would have been left as is (0ms) .
Consequently, this now non-zero global timeout is probably also surfacing the UT upstream request timeout here even in the case of some real spotty upstreams.

Perhaps this is more nuanced for our use case but by switching to maxGrpcTimeout - this seems to complicate how a microservice can be on the service mesh and manage its own GRPC timeouts.
As a workaround, we can use EnvoyFilters to keep maxStreamDuration, but just wondering if this is norm now.
Version
1.16.4

Additional Information
No response
Affected product area

[ ] Ambient
[ ] Docs
[ ] Installation
[X] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
[ ] Upgrade
[ ] Multi Cluster
[ ] Virtual Machine
[ ] Control Plane Revisions

cc @ramaraochavali


Use DIRECTORY_SEPARATOR constant instead of /

On Windows CheckNotTestsNamespaceOutsideTestsDirectoryRule wouldn't have worked as inteded.

Thank you :+1:


EB Web and Work - Sharing Database

I'm assuming they need to share a database, but didn't see this mentioned in the Readme. What are the recommended steps for sharing the RDS instance?

Simply use an environment variable to pass the database url and use that environment variable in both environments.
e.g.
DATABASE_URL="postgres://user:password@host:port/database_name"


[WIP] Use BreezSDK pod as iOS dependency of RN plugin

[WIP] This PR needs to be resolved first: https://github.com/breez/breez-sdk-swift/pull/9
To test this, I published a version of updated RN plugin under my personal npm namespace and integrated it in a fresh RN project. I then checked if I could successfully build and use the mnemonicToSeed interface. That worked. 🙌

@cnixbtc Thanks a lot!
One question: will we be able to build locally the plugin without publishing a swift package and use in the example app?
The reason is because during development we want to test the example app with a built version without publishing.

@cnixbtc Thanks a lot! One question: will we be able to build locally the plugin without publishing a swift package and use in the example app? The reason is because during development we want to test the example app with a built version without publishing.

Good question. The ask is to be able to develop the RN plugin / the RN example app with a local build of the BreezSDK without it needing to be published as a CocoaPod first right? I think that is a fair concern. I don't think this can be done comletely seemlessly, though. I guess that this would probably involve manually changing a line in the RN plugins podspec to change the source from where the BreezSDK is loaded (as a local, vendored framework as we had it until now or pulled remotely from the CocoaPods trunk).
I will look into this tonight.

@cnixbtc changing a line in the podspec or something similar sounds reasonable. Just wanted you to take that into consideration

I think I've found a way to make it work but I still need to test it. Will report back here.

Alright I think everything should work now. I've tested:

A fresh RN project as well as the example project when using a local build of the SDK via vendored_framework in the plugin's podspec
The "new" way of pulling in the BreezSDK pod instead of the locally built SDK.

I'd like to test this once more once we release a new version of the pod that has the latest change (lowering the deployment target https://github.com/breez/breez-sdk-swift/pull/9) in just to be sure. I'd also like to add a sentence or two to the plugins docs explaining the new setup. I'd be great to get some feedback on the approach already, though. I don't expect those things to change much.
I'll add CI changes to publish the plugin to npm in a separate PR!


LG Heat pump energy usage

Hello
I'm using HA with smarthinq-sensors for my heatpump, Seems it's fully working with LG Monoblock R32 (supersilent)  HM(XXX)MR U44 units. Didn't noticed any problems.
My feature request is to include energy usage meter. While we have energy current, we could have energy usage meter, this data is also stored in LG cloud and could be used in HA as component of energy tab.

This feature request is related to and/or a duplicate of https://github.com/ollo69/ha-smartthinq-sensors/issues/555


Register the "dns.weave.local" name in WeaveDNS

Fixes #984 by registering dns.weave.local. in a private ident that is not exported via mDNS, so containers can query about dns.weave.local. and get the IP of the local WeaveDNS instance.

Am ready to merge this once minor comment is addressed!

Is there a reason to pollute the user-owned namespace weave.local with this name? Why not use something else, e.g., .local (I know, the user is allowed to change the name of the domain, but that does not excuse the pollution).
Also: unless WeaveDNS is in the same subnet as the container asking, they will not be able to talk. This seems like a bit of a sticking point for the issue which motivated this change.

Also: unless WeaveDNS is in the same subnet as the container asking, they will not be able to talk. This seems like a bit of a sticking point for the issue which motivated this change.

Why not populate it with the docker bridge ip? As per https://github.com/weaveworks/weave/issues/984#issuecomment-114425450

Why not populate it with the docker bridge ip? As per #984 (comment)

And if you're doing that, why not put an entry in /etc/hosts while you're at it (e.g., with --add-host or --link).

@fintanr see above - could you give that a try?

i.e. docker run --add-host weavedns:$(weave docker-bridge-ip) ... should do the trick and allow the nginx to resolve weavedns.

@rade sure, starting a test/update for nginx guides now.

docker run --add-host weavedns:$(weave docker-bridge-ip) ...

or even
docker run --link weavedns ...

HOWEVER: linking also copies the environment variables from the source container over to the target container (!?). So perhaps not recommended.

What is the problem with polluting the weave.local. domain? We are not introducing a random name. We are setting the dns server of that domain. It is a common convention to have a dns.somedomain.com server for the somedomain.com domain. Registering dns in a different domain provides little benefit and much complexity.

What is the problem with polluting the weave.local. domain?

It's meant to be under control of the user -- withholding a name in it is a bad smell.
Sure, it may be a convention for DNS admins to put dns.example.com -- but it's not done automatically by the nameserver (is it?). In any case I don't think we need this for fixing #984.

@squaremo So you are suggesting to fix this with --add-host. Taking into account that nginx uses its own resolver, have we verified that it reads /etc/hosts?
So I guess I should close this PR.

@squaremo So you are suggesting to fix this with --add-host. Taking into account that nginx uses its own resolver, have we verified that it reads /etc/hosts?

According to the description in #984, nginx uses the system resolver first, to find the host you told it to use for its own resolver.

So I guess I should close this PR.

Only if there's otherwise no use for this feature -- i.e., is there another scenario in which it would be handy to be able to resolve the DNS server itself?

Only if there's otherwise no use for this feature -- i.e., is there another scenario in which it would be handy to be able to resolve the DNS server itself?

I think there isn't... I'm closing it.

Let's wait for @fintanr to confirm that the --add-host approach actually works.

Any news on this, @fintanr?

--add-host worked fine for me

For anyone who stumbles on this via google: IPv6 must be turned off for the resolver to work, at least as of Nginx 1.9.15.
https://trac.nginx.org/nginx/ticket/974
TL;DR: If the resolver setting is not working, try ipv6=off resolver flag.

@kpdecker I believe you are describing the same problem as #2244, which is fixed now and will be in the next release.  Sorry for the trouble.

@bboreham thanks for the update. I have a work around for now and will certainly give the next version a try!

@kpdecker we just released version 1.5.1 with the fix to #2244 included.

@bboreham thanks, will make some time to test it out.


tsc was not available or found in your node_modules or $PATH. Please run install and try again.

I get this error in my typescript vite project. It was working before for a long time until after I updated yesterday. Here is my package.json:
"packages": {
"": {
"dependencies": {
"@headlessui/react": "^1.7.14",
"@heroicons/react": "^2.0.17",
"@tailwindcss/forms": "^0.5.3",
"@tanstack/react-query": "^4.29.13",
"@tanstack/react-query-devtools": "^4.29.14",
"@tanstack/react-table": "^8.9.1",
"@types/crypto-js": "^4.1.1",
"@types/react-csv": "^1.1.3",
"axios": "^1.4.0",
"class-variance-authority": "^0.6.0",
"clsx": "^1.2.1",
"color": "^4.2.3",
"crypto-js": "^4.1.1",
"date-fns": "^2.30.0",
"framer-motion": "^10.12.16",
"jwt-decode": "^3.1.2",
"react": "^18.2.0",
"react-csv": "^2.2.2",
"react-day-picker": "^8.7.1",
"react-dom": "^18.2.0",
"react-hook-form": "^7.43.9",
"react-icons": "^4.8.0",
"react-router-dom": "^6.11.2",
"react-toastify": "^9.1.3",
"recharts": "^2.5.0",
"tailwind-merge": "^1.12.0",
"vite-plugin-svgr": "^3.2.0",
"zod": "^3.21.4"
},
"devDependencies": {
"@faker-js/faker": "^8.0.0",
"@types/react": "^18.0.28",
"@types/react-dom": "^18.0.11",
"@typescript-eslint/eslint-plugin": "^5.57.1",
"@typescript-eslint/parser": "^5.57.1",
"@vitejs/plugin-react-swc": "^3.0.0",
"autoprefixer": "^10.4.14",
"eslint": "^8.38.0",
"eslint-plugin-react-hooks": "^4.6.0",
"eslint-plugin-react-refresh": "^0.3.4",
"postcss": "^8.4.23",
"prettier": "^2.8.8",
"prettier-plugin-tailwindcss": "^0.3.0",
"tailwindcss": "^3.3.2",
"typescript": "^5.0.2",
"vite": "^4.3.2"
}
}

Can you share your tsconfig(s) and the project structure? In the mean time you can try setting the bin_path configuration option.

It's a company repository, so unfortunately, I am unable to provide detailed information about the project structure. However, I can tell you that the tsconfig file is generally the default configuration generated by Vite when initializing a new project.
Regarding your question about setting the bin_path configuration, could you please provide more context or specify how I could do that?

There is a bin_path config option that you can set to the path to your tsc binary. See #26 for more details.

I get the following error with the default configuration in the docs. Do I have to manually implement the utils function?
Error notify.error lazy.nvim Failed to run config for tsc.nvim
 /home/xxx/.config/LazyVim/lua/plugins/tsc-nvim.lua:7: attempt to index global 'utils' (a nil value)
Config:
return {
  "dmmulroy/tsc.nvim",
  config = function()
    require("tsc").setup({
      auto_open_qflist = true,
      auto_close_qflist = false,
      bin_path = utils.find_tsc_bin(),
      enable_progress_notifications = true,
      flags = {
        noEmit = true,
        project = function()
          return utils.find_nearest_tsconfig()
        end,
      },
      hide_progress_notifications_from_history = true,
      spinner = { "⣾", "⣽", "⣻", "⢿", "⡿", "⣟", "⣯", "⣷" },
    })
  end,
}

I also just installed a fresh project using npm create vite@latest my-vite-app -- --template vanilla-typescript and everything worked, so you may need to add some logging to the plugin or call utils.find_tsc_bin() from the status line cmdline (e.g. :lua print(vim.inspect(require('tsc.utils').find_tsc_bin())))

No, invoking which tsc returns ~/.local/bin/tsc, which is a symlink to /lib/node_modules/typescript/bin/tsc . Therefore, I opted to use that instead. In any case, I managed to get it working by utilizing the utility function you provided. I had ChatGPT to make any corrections if needed and it worked. Specifying the bin_path never worked, nor did requiring the tsc.utils.
Here's the working configuration:
local utils = {}

utils.find_tsc_bin = function()
  local node_modules_tsc_binary = vim.fn.findfile("node_modules/.bin/tsc", ".;")

  if node_modules_tsc_binary ~= "" then
    return node_modules_tsc_binary
  end

  return "tsc"
end

return {
  "dmmulroy/tsc.nvim",
  config = function()
    require("tsc").setup({
      bin_path = utils.find_tsc_bin(),
    })
  end
}

Ah, I wonder if the problem is the symlink. I'm betting that utils.is_executable(tsc) doesn't follow the symlink and returns false.

That's really bizarre. You should at least be able to simplify that to just:
return {
  "dmmulroy/tsc.nvim",
  config = function()
    require("tsc").setup({
      bin_path = require('tsc.utils').find_tsc_bin(),
    })
  end
}

I wonder if vim.fn.executable is doing something unexpected

executable({expr})					executable()
This function checks if an executable with the name {expr}
exists.  {expr} must be the name of the program without any
arguments.
executable() uses the value of $PATH and/or the normal
searchpath for programs.		PATHEXT
On MS-Windows the ".exe", ".bat", etc. can optionally be
included.  Then the extensions in $PATHEXT are tried.  Thus if
"foo.exe" does not exist, "foo.exe.bat" can be found.  If
$PATHEXT is not set then ".exe;.com;.bat;.cmd" is used.  A dot
by itself can be used in $PATHEXT to try using the name
without an extension.  When 'shell' looks like a Unix shell,
then the name is also tried without adding an extension.
On MS-Windows it only checks if the file exists and is not a
directory, not if it's really executable.
On Windows an executable in the same directory as Vim is
always found (it is added to $PATH at |startup|).
The result is a Number:
1	exists
0	does not exist
-1	not implemented on this system
|exepath()| can be used to get the full path of an executable.

I was also hitting this issue. For whatever reason running  :echo vim.fn.findfile("node_modules/.bin/tsc", ".;") gave me nothing, but running :echo vim.fn.findfile("node_modules/.bin/tsc") spit out the correct tsc path. I updated my config setup to look like this:
require("tsc").setup({
	auto_open_qflist = true,
	auto_close_qflist = false,
	bin_path = vim.fn.findfile("node_modules/.bin/tsc"),
	enable_progress_notifications = true,
	flags = {
		noEmit = true,
		project = function()
			return vim.fn.findfile("tsconfig.json")
		end,
	},
	hide_progress_notifications_from_history = true,
	spinner = { "⣾", "⣽", "⣻", "⢿", "⡿", "⣟", "⣯", "⣷" },
})

note that i hit the same issue in the project file flag config.
https://github.com/evanrichards/dotfiles/commit/08fe91648f6fdeff711e3bfc149eab035cf0dc0a

@evanrichards do you think you could replicate the issue in a small repo and post it?

Very strange this also seems to be an issue here, im working in a pnpm monorepo with build = true set.

@sami616 Could you create a small pnpm monorepo where this is reproducible? I've never used pnpm or it's monorepo capabilities before.

@sami616 could you try using this config
require("tsc").setup({
	flags = {
		noEmit = false,
		build = true,
		project = false,
	},
})

@dmmulroy fyi I just started using your awesome plugin and I ran into similar issues. I also use pnpm as someone above mentioned but I don't think that should be a problem. I think potentially the problem is due to windows and likely path issues (backslashes vs forward, escaping, spaces in paths etc.). This is the most common issue I have ran into with many plugins in the neovim community. Curious if you have had a chance to test on windows?
That all being said, my solution was that I could use the defaults as provided in the readme except I had to change it to use bin_path = "tsc". All is working nicely after making this change.

@GitMurf thanks for the details! Pnpm and workspaces have been a thorn in my side for this plugin haha. Is there any chance you could create a small repo where the bug is reproducible?

@GitMurf thanks for the details! Pnpm and workspaces have been a thorn in my side for this plugin haha. Is there any chance you could create a small repo where the bug is reproducible?

Yes but may take me a week or so. Swamped right now as I'm sure you understand ;)
Again, awesome work on this plugin! Absolute game changer for me for typescript development :)

I cannot run TSC as it complains tsc was not found.
Why can't we just used npx tsc to find where tsc is automatically, instead of providing it manually through bin_path?


Latest version triggers my virusscanner

03/11/2024 18:20
Application blocked
Path: C:\Users<myname>\Downloads
File: ObservatorySetup.exe
Reason: Suspicious:W32/Malware.a!fsmind
Anyone else seeing this, or is it a fluke?

Happens to me with almost every release, as its a new exe and likely not yet scanned by enough PC's to be generally considered safe in AV databases.

Was a first for me, but guess it's mostly the installer that causes it. Downloaded the zip, scanned the *.exe without issues so up and running again.


feat(mappings): check if desc key exists when parsing mappings

There are two patterns of adding a description, with a second string or with the desc key.
Legendary.nvim uses the parse function from which-key. This function does not check the desc key in the table, which should be supported.

Thanks!


goog.fx.AbstractDragDrop: issue with subtargets

This issue was imported from Closure Library's previous home at http://closure-library.googlecode.com
The link to the original issue is:
https://code.google.com/p/closure-library/issues/detail?id=461

This issue is being closed as a preparation step before archiving the repository.  See the README for more detail.


Switch to a tutorial-style GitBook

I'd love to have a GitBook similar to tutorials for React, MobX, Flux, and so on. I'm thinking it would be reasonable to have the topics be:

Introduction/README.md
Syntax

Comments
Variables
Math
Strings
Arrays and Lists
Dictionaries
Main/Functions
Classes

Member variables
Member functions
Interfaces
Statics

Files

Importing

Omissions
Internals

Status:

[x] Create separate Intro GitBook
[x] Copy & create content in temporary Intro book
[x] Remove unnecessary content from GLS; copy content into Docs folder
[x] Delete temporary Intro book
[x] Create new Intro book pointing at GLS itself
[x] Point glslang.org domain to the book

https://github.com/general-language-syntax/Intro

https://general-language-syntax.gitbooks.io/intro

https://www.glslang.org is up!


Feature/test

Codecov Report

Merging #29 into develop will increase coverage by 0.29%.
The diff coverage is 100%.

@@             Coverage Diff             @@
##           develop      #29      +/-   ##
===========================================
+ Coverage    53.91%   54.21%   +0.29%
===========================================
  Files          199      199
  Lines        10282    10308      +26
===========================================
+ Hits          5544     5588      +44
+ Misses        4738     4720      -18

Impacted Files
Coverage Δ

...er/tests/switch_stream/mediaPlayerSwitchStream.cpp
100% <100%> (ø)
:arrow_up:

framework/filter/ffmpegAudioFilter.cpp
80.9% <0%> (-1.01%)
:arrow_down:

mediaPlayer/media_packet_queue.cpp
69.59% <0%> (-0.81%)
:arrow_down:

framework/demuxer/play_list/HLSStream.cpp
68.38% <0%> (+0.33%)
:arrow_up:

framework/data_source/curl/curl_data_source.cpp
63.12% <0%> (+0.38%)
:arrow_up:

framework/codec/ActiveDecoder.cpp
63.44% <0%> (+0.53%)
:arrow_up:

mediaPlayer/player_notifier.cpp
78.65% <0%> (+0.56%)
:arrow_up:

mediaPlayer/SuperMediaPlayer.cpp
66% <0%> (+0.63%)
:arrow_up:

mediaPlayer/player_msg_control.cpp
70.58% <0%> (+1.68%)
:arrow_up:

Continue to review full report at Codecov.

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


PR: Pattern text copy edits and layout

Hi
Please see https://verify-local-patterns.herokuapp.com/service-patterns/concessionary-travel for the before version.
This is just for content style not fact check but have updated some bits I knew had irritatively changed.
After

Photo upload flow still to be updated

@sanjaypoyzer @lizziebruce so i remember on Wednesday, the only outstanding copy edits are in 7. the Verify common content on Parking

@petegale please see screenshots above as so far these changes are only on my local service. Specifically, the Access user research links that appear after each Explore prototype link.


CASHnet: uri encode the merchant gateway name

Not sure how to test this, so :+1:.

I felt the same way.


:art: Change format to use fmtlib compile-time formatting

Closes #257
Addresses #105

I'm going to need to take a close look at this on Monday. 🤩


Any plans to support Anthropic API as an option?

I've found myself recently switching from GPT-4 to Claude 3 for all the work I do, because the answers from their latest "Opus" model are outperforming anything I was previously getting from OpenAI using GPT-4.
Do you have any plans of supporting the Anthropic API in your plug-in for a future version? I would assume the same approach, with the user having to provide an API key to use the model...

Hi @afalk42,
Thanks for your interest, yes, I am working on Claude integration. Will release it soon.

That's awesome! If you need a beta tester, let me know!
Also, do you have a "Buy Me A Coffee" or similar link where I could send
you a little token of appreciation for this wonderful plugin?
Best Regards,
Alexander Falk
https://alexander.falk.us
https://xmlaficionado.com
Co-Founder, President, CEO - Altova https://www.altova.com/
WASH Major Gifts Initiative Adviser 2024-27 - Rotary Foundation
https://www.rotary.org/en/about-rotary/rotary-foundation
Past District Governor 2022-23,
District Rotary Foundation Chair 2024-27 - Rotary District 7930
https://rotary7930.org/
Past President 2018-19 - Marblehead Rotary Club
https://www.marbleheadrotary.com/

https://fa.lk/personalemailpolicy
On Thu, Mar 28, 2024 at 3:15 PM Quentin @.***> wrote:

Hi @afalk42 https://github.com/afalk42,
Thanks for your interest, yes, I am working on Claude integration. Will
release it soon.
—
Reply to this email directly, view it on GitHub
https://github.com/qgrail/obsidian-ai-assistant/issues/24#issuecomment-2025931258,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABUWDXBKXHAVKFRB5EOCIVDY2RM5BAVCNFSM6AAAAABFLMPLESVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDAMRVHEZTCMRVHA
.
You are receiving this because you were mentioned.Message ID:
@.***>


Inquiry about Shortcut Key Functionality

I would like to inquire if the functionality to disconnect connections is working properly. I am unable to disconnect any connections between nodes unless I delete the blueprint node itself.

You can double click on a arc to create a path node (don't remember the exact name) and delete that one. Is there a shortcut key in UE?

Yes, you can disconnect by pressing ALT + left mouse click.
---Original---
From: @.>
Date: Fri, Aug 4, 2023 16:59 PM
To: @.>;
Cc<EMAIL_ADDRESS>Subject: Re: [barsdeveloper/ueblueprint] Inquiry about Shortcut KeyFunctionality (Issue #10)
You can double click on a arc to create a path node (don't remember the exact name) and delete that one. Is there a shortcut key in UE?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you authored the thread.Message ID: @.***>

Will add it. Thanks


Function based endpoint URIs

Type of issue

[ ] Bug report
[X] Feature request

Uploader type

[X] Traditional
[X] S3
[X] Azure

Is there any way / upcoming support for the server-side endpoints to be functions / promises instead of hard-coded strings?
Our JS -> Server REST has a pretty robust API with real-time nonces and signature verifications built in, we'd like to generate the full endpoint URL at the time it is needed through our functions and return that back, rather than hard-coding a string in the qq object.
Is this possible today?
Again, we're talking about the communication between our JS (and your JS) to our back-end server for signature verification and other server-side endpoints.  We need these URLs to be more robust.

Please look at #1939. I've added support to accommodate a workflow where the endpoint for each upload/chunk is only known at runtime via some ajax call or other async process.


Feature: Custom Path for server

It would be nice to add a custom path for local server. Right now when you spin up the local server it builds out a dist directory to serve from. This creates a permissions conflict when using https with port 443 and when your builds export to dist as well.
paths: {
    src: 'src', // The source directory. Must include an index.js entry file.
    serve: 'local' // The directory local server runs from
    dist: 'dist', // The output directory.
    public: 'public' // The public directory (files copied to dist during build)
  },

Hi @poorpaddy!
Have you seen the Using Custom devServer properties part of the Webpack Config and Plugins section? You can customize the devServer however you like.

Hi @EmilTholin,
Yes, I'm currently using it but not sure how to stop it from generating dist everytime react-static runs.
devServer: {
    host: 'local.xxxx.com',
    historyApiFallback: true,
    https: (USE_HTTPS) ? {
      key: fs.readFileSync('./cert/local-xxxx-com.pem'),
      cert: fs.readFileSync('./cert/local-xxxx-com.pem'),
      ca: fs.readFileSync('./cert/local-xxxx-com.pem')
    } : false,
    disableHostCheck: true,
    port: USE_HTTPS ? 443 : 5000
  },

If you're using HTTPS, or any ports lower on the scale, you'll likely need to use sudo react-static start/build either way. Does that solve your problem?

@tannerlinsley not really. I need to to use https locally which sudo is fine for. But for the actual build for production output I do not want https or sudo because the server the static html gets deployed will handle that and sudo causes some challenges in that case since it is an automatic deployment based on our pom file.

So you want the dev server to be able to use a directory other than dist?
On Wed, Nov 15, 2017 at 2:27 PM Dave Bergschneider<EMAIL_ADDRESS>wrote:

@tannerlinsley https://github.com/tannerlinsley not really. I need to
to use https locally which sudo is fine for. But for the actual build for
production output I do not want https or sudo because the server the static
html gets deployed will handle that and sudo causes some challenges in that
case since it is an automatic deployment based on our pom file.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/nozzle/react-static/issues/174#issuecomment-344733960,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFUmCTa3n5Nl93tbGpBNiaG25dz0G9Ftks5s21dCgaJpZM4Qfdz7
.

That is is correct.

Should be available in the latest release as a new config option: config.paths.devDist :)


[TEVA-1757] Update sanitise script to sanitise new Feedbacks table

Jira ticket URL
https://dfedigital.atlassian.net/browse/TEVA-1757
Changes in this PR:

As per title.

Review app deployed to https://teaching-vacancies-review-pr-2846.london.cloudapps.digital


Feature Request: Total Blocks Broken

What does your feature do?
Instead of having to specify the exact types of blocks to be broken with corresponding values, we should be able to specify all blocks for one value.
How would people use it?
For the blocks mined requirement, specifying the type of block as ALL or ANY should be allowed.
This is particularly helpful for prison.

stages:
  ordered:
    '1':
      break-block-names:
      - ANY
      break-block-amounts:
      - 10000
      break-block-durability:
      - 0
      complete-message: You have successfully broken 10000 Blocks!

Thanks for the suggestion. This could already be made possible with a Custom Objective, but I'll consider adding the functionality to the plugin itself.

@PikaMug do you intend on adding this feature? I'm looking for any plugin that will allow this sort of quest without causing any bugs.

So I've looked into just incorporating this into the plugin and unfortunately it's not as simple as I'd hoped. Quests loads/saves blocks as an ItemStack, which has to be a specific item. In other words, you can't have an ItemStack with a name of "ANY" - it has to be something from the Materials list. Rewritting those parts of the plugin to work around that would constitute an overhaul of the player data files, which I'm not willing to do.
Furthermore, it's my opinion that what you've requested doesn't really constitute a quest. Google defines the word "quest" as follows:

What you've requested doesn't really require any thought to accomplish. Granted, mining 10000 blocks is long, but hardly arduous as there's no pressure to hunt for a specific object. Mining X amount of blocks would better be left to a more general plugin like Jobs Reborn... or a Quests module.
This is all it would take to make a custom module objective that counts ANY block:
package me.pikamug.Blocks;

import org.bukkit.Bukkit;
import org.bukkit.entity.Player;
import org.bukkit.event.EventHandler;
import org.bukkit.event.EventPriority;
import org.bukkit.event.block.BlockBreakEvent;

import me.blackvein.quests.CustomObjective;
import me.blackvein.quests.Quest;
import me.blackvein.quests.Quests;

public class AnyBreakBlockObjective extends CustomObjective {
	private static Quests quests = (Quests) Bukkit.getServer().getPluginManager().getPlugin("Quests");

	public AnyBreakBlockObjective() {
		setName("Break Blocks Objective");
		setAuthor("PikaMug");
		setShowCount(true);
		addStringPrompt("Obj Name", "Set a name for the objective", "Break ANY block");
		setCountPrompt("Set the amount of blocks to break");
		setDisplay("%Obj Name%: %count%");
	}

	@EventHandler(priority = EventPriority.LOW)
	public void onBlockBreak(BlockBreakEvent event) {
		Player player = event.getPlayer();
		for (Quest q : quests.getQuester(player.getUniqueId()).getCurrentQuests().keySet()) {
			incrementObjective(player, this, 1, q);
			return;
		}
	}
}

As you can see, this is very simple to do and would only require specifying the custom objective in the Quests Editor rather than using the built-in Break Block objective. However, as the existence of #803 implies, the module would likely want to support other Block events (Place, Use, et al.). From there, people are bound to want wildcards for Mob names, NPC IDs (see #807), delivery items, et al. and eventually for Bukkit Events which Quests doesn't inherently support (as of writing). It's a rabbit hole which would only widen with each Minecraft release - something I'm not willing to tackle myself.
TL;DR: Including this enhancement would be opening a can of worms. This is best left to a module, which I'm not willing to write. Feel free to use the code above, or enlist the help of a developer at https://www.spigotmc.org/forums/hiring-developers.55/ (which neither I nor the Quests project are associated with).

Update since I keep mentioning this: consider trying https://lectern.browsit.org/resources/resource/19/


Error handling for duplicate column header values is broken.

Hi there,
I receive the following error when performing .data() on a sheet which has 2 columns with the same value:
Traceback (most recent call last):
  File "read/read_data.py", line 15, in <module>
    key_column_headers=["AWS Account"])
  File "/Users/raid/Projects/sheetsync/venv/lib/python2.7/site-packages/sheetsync/__init__.py", line 413, in __init__
    self._get_or_create_headers()
  File "/Users/raid/Projects/sheetsync/venv/lib/python2.7/site-packages/sheetsync/__init__.py", line 706, in _get_or_create_headers
    self.header.set(cell.col, cell.value)
  File "/Users/raid/Projects/sheetsync/venv/lib/python2.7/site-packages/sheetsync/__init__.py", line 227, in set
    self.header_row_ix,  self.sheet_name))
AttributeError: 'Header' object has no attribute 'header_row_ix'

I guess this is because python dictionaries don't support duplicate keys, but is there any way duplicate column header values can be handled?
Cheers!

Right. There's no way to figure out which column to use (put data in, read data from) when you have duplicated column headers.
I can fix the error though, which is simple bug caused by the refactoring. Will roll that up with other fixes in the future.
Thanks!

Even something that returns a more accurate error message would be sufficient.


Version 1.2.4 not working anymore on browsers

I upgraded my code to use the latest version of this library and while it still work fine under node, it stops working (it does not complete the connection) while running in the browser.
I think it has something to do with the way you handle the supported protocols but I've not yet been able to pinpoint exactly.

I had no issue upgrading to latest but if you can provide more info I would look into it

That's because you are not respecting the websocket protocols property. Look at this issue and associated fix #66

If you give a specific list of protocol at your websocket here https://github.com/JSteunou/webstomp-client/blob/master/src/webstomp.js#L12 or let the default list, your server must accept / handle at least one protocol in the list.
example from a real app:
my request contains header Sec-WebSocket-Protocol: v10.stomp, v11.stomp, v12.stomp my response contains header sec-websocket-protocol: v12.stomp and my stomp CONNECT & CONNECTED frames contains accept-version:1.2 & version:1.2

I'm sorry, I'm not sure about where is the problem and what I've to do.
I've no control con the server, it's handled by https://docs.spring.io/spring-integration/reference/html/stomp.html and I suppose they follow specifications.
I was using default options and everything worked fine until 1.2.0, and stopped working in newer releases so I suppose some default is not correct.
That shouldn't happen, right?

So, to make it work, do I need to specify the exact protocol I want to use?

Could you show me how you initialize your webstomp client in JS and what are the headers you can see on the http request (the one upgraded as websocket) from your browser devtool for example.

I use a code like this:

const options = { debug: false, heartbeat: false }
stompClient = Stomp.client(stompEndpoint, options)

I'll look for the headers

ok that means that the client will send the default list of supported STOMP protocols 'v10.stomp', 'v11.stomp', 'v12.stomp' but maybe your server did not apply to this list and send another version back or worse, no version at all

I will let you open an issue at spring project if there is an issue on their side, I will not have the time to handle all possible server implementation. I follow the spec and handle this client, that's enough for the little time I have for side projects :)
You did not tell me yet what is the http response header you get from your server.

The connection works fine if I use those options:

const options = { debug: false, heartbeat: false, protocols: ['v12.stomp'] }

Debugging your code it seems like in this.ws.onpen() function _this.ws.protocol is empty, while it should not be.
Can this be the problem?

I will look into it when I will be back but this is weird. If you let default which is a list of v10.stomp, v11.stomp, v12.stomp, and get v10.stomp back then it should work and 1.0 should be used. On the contrary if you force v12.stomp and get v10.stomp back it should not work as they do not match.

The issue is still marked as "needs input", does it?

Yes. Could you give me a clear state of what works and what does not work (which options, which server, ...) and for each case what are the http response headers and ws.protocol because it's a bit hard to follow you, information is spread out.
And look here https://github.com/JSteunou/webstomp-client/blob/master/dist/webstomp.js#L98 When there are no protocols matching, the accept-version header is a simple list of all 3 possible versions to be not breaking that's why I'm surprised with this issue

Ok but I need more information to find the issue, and unless you do not provide it I cannot understand if and where there is an issue from this lib

ok, please tell me the specifis of what you need, I already sent you the snapshot of the capture of the stream

I just did

Could you give me a clear state of what works and what does not work (which options, which server, ...) and for each case what are the http response headers and ws.protocol value because it's a bit hard to follow you, information is spread out.

Hi there, I'm running into the same issue as @Polve.
Basically what's happening is if the server responds with a Sec-Websocket-Protocol: v10.stomp header, it doesn't work. So including v10.stomp in the protocols list (whether by using the default, or by specifying explicitly) breaks it. Specifying only v12.stomp or only v13.stomp or the list v12.stomp, v13.stomp works fine.

That's weird because again they are all in the list of handle protocols, and I cannot reproduce this issue (when WS instance correctly created with a matched list of expected protocols).
Have you try to add some breakpoints in the webstomp client to debug this issue and find what happen?

You might concern by https://github.com/JSteunou/webstomp-client/issues/75#issuecomment-426578411