Forking Mainnet With Upgrades Package

Hello all,
I am attempting to test a set of upgradeable contracts using the mainnet forking abilities on Hardhat.  Unfortunately, whenever I attempt to run my tests I receive this error message:
Error: Invalid deployment with address 0x09635F643e140090A9A8Dcd712eD6285858ceBef and txHash 0xd9e10e22b3ac93529b4563a615cb341a2f11832eef7df79d22c8e090b1e60a9a

With this stack trace:
at Object.resumeOrDeploy (node_modules/@openzeppelin/upgrades-core/src/deployment.ts:35:13)
      at processTicksAndRejections (internal/process/task_queues.js:97:5)
      at /Users/jacobsanjuan/Desktop/Tokemak/fractal-smart-contracts/node_modules/@openzeppelin/upgrades-core/src/impl-store.ts:33:23
      at Manifest.lockedRun (node_modules/@openzeppelin/upgrades-core/src/manifest.ts:90:14)
      at fetchOrDeployGeneric (node_modules/@openzeppelin/upgrades-core/src/impl-store.ts:25:24)
      at Proxy.deployProxy (node_modules/@openzeppelin/hardhat-upgrades/src/deploy-proxy.ts:45:18)
      at Context.<anonymous> (test-unit/Manager.test.js:27:15)

At this line of code in my test file:
manager = await upgrades.deployProxy(managerFactory, [CYCLE_DURATION], { unsafeAllow: ['delegatecall'] });

I have done a lot of research on this issue and am aware that this issue is very similar to the one resolved in issue #282, but I am still having problems.  I am using the latest version of OpenZeppelin Hardhat Upgrades (^1.6.0) and have tried both Infura and Alchemy on both the mainnet and testnets, and am still having issues.  Please let me know what further information is needed.

Hi @jake-sanjuan!
I’m sorry that you had this issue.
Unfortunately, I wasn’t able to reproduce this issue. I tried the following:

Box.sol contract, Box.js, Box.proxy.js from: https://forum.openzeppelin.com/t/openzeppelin-upgrades-step-by-step-tutorial-for-hardhat/3580

hardhat.config.js
Configure Hardhat fork
// hardhat.config.js
const { alchemyApiKey, mnemonic, etherscanApiKey } = require('./secrets.json');

require("@nomiclabs/hardhat-ethers");
require('@openzeppelin/hardhat-upgrades');

/**
 * @type import('hardhat/config').HardhatUserConfig
 */
module.exports = {
  solidity: "0.7.3",
  networks: {
    hardhat: {
      forking: {
        url: `https://eth-mainnet.alchemyapi.io/v2/${alchemyApiKey}`
      }
    }
  }
};

Test runs using mainnet fork
$ npx hardhat test --network hardhat

  Box
    ✓ retrieve returns a value previously stored

  Box (proxy)
    ✓ retrieve returns a value previously initialized

  2 passing (13s)

Can you try creating a simple example (such as using Box.sol) to illustrate the issue?

Hi @abcoathup
Thanks for getting back to me quickly.  I recreated using Box.sol, Box.js and Box.proxy.js.  The problems seems to be in my hardhat.config.js file, specifically with chainId.  Here is where it is the config file:
require("dotenv").config();
require("solidity-coverage");
require("@nomiclabs/hardhat-ethers");
require("@nomiclabs/hardhat-waffle");
require("@nomiclabs/hardhat-truffle5");
require("@nomiclabs/hardhat-etherscan");
require("@openzeppelin/hardhat-upgrades");

module.exports = {
  networks: {
    hardhat: {
      chainId: 1, // This seems to be the problem
      forking: {
        url: "https://eth-mainnet.alchemyapi.io/v2/" + process.env.ALCHEMY_API_KEY,
      },
    },
    localhost: {
      url: "http://<IP_ADDRESS>:8545",
      timeout: 1000000,
    },
    coverage: {
      url: "http://localhost:8555",
    },
    mainnet: {
      url: "https://eth-mainnet.alchemyapi.io/v2/" + process.env.ALCHEMY_API_LEY,
      gasPrice: 72e9,
      accounts: {
        mnemonic: process.env.MNEMONIC || "",
      },
      timeout: 1000000,
    },
  },
  solidity: {
    version: "0.6.11",
    settings: {
      optimizer: {
        enabled: true,
        runs: 999999,
      },
    },
  },
  mocha: {
    timeout: 1000000,
  },
  etherscan: {
    apiKey: process.env.ETHERSCAN_API_KEY,
  },
};

When adding the chainId to the config file for the Box project and running the tests twice, I get the same error:
Box (proxy)
       "before each" hook for "retrieve returns a value previously initialized":
     Error: Invalid deployment with address 0xE6E340D132b5f46d1e472DebcD681B2aBc16e57E and txHash 0x0c7fb14c79fa57fe32d0a4261e0aaedfa6bb7a7fd2937ce90bf9adf97c58222f

The tests work as expected the first time they are run.  After that, the Box.proxy.js test fails every time with the above error.
Config that recreates error for Box project:
require("@nomiclabs/hardhat-waffle");
const { alchemyApiKey } = require('./secrets.json');

require("@nomiclabs/hardhat-ethers");
require('@openzeppelin/hardhat-upgrades');

/**
 * @type import('hardhat/config').HardhatUserConfig
 */
module.exports = {
  solidity: "0.6.11",
  networks: {
    hardhat: {
      chainId: 1,
      forking: {
        url: `https://eth-mainnet.alchemyapi.io/v2/${alchemyApiKey}`
      }
    }
  }
};

Hi @jake-sanjuan,
Running the tests twice reproduced the issue:
I had to modify the tests to add   this.timeout(0); so they didn't timeout.  Running twice gave the error:
$ npx hardhat test --network hardhat
Compiling 1 file with 0.7.3
Compilation finished successfully

  Box
    ✓ retrieve returns a value previously stored

  Box (proxy)
    ✓ retrieve returns a value previously initialized

  2 passing (1m)

$ npx hardhat test --network hardhat

  Box
    1) "before each" hook for "retrieve returns a value previously stored"

  Box (proxy)
    ✓ retrieve returns a value previously initialized

  1 passing (4m)
  1 failing

  1) Box
       "before each" hook for "retrieve returns a value previously stored":
     FetchError: request to https://eth-mainnet.alchemyapi.io/v2/JPV2MMxt6g3rmMY_8b8u3dMOh1gr2VV5 failed, reason: connect ETIMEDOUT <IP_ADDRESS>:443
      at ClientRequest.<anonymous> (node_modules/node-fetch/lib/index.js:1461:11)
      at TLSSocket.socketErrorListener (_http_client.js:401:9)
      at emitErrorNT (internal/streams/destroy.js:91:8)
      at emitErrorAndCloseNT (internal/streams/destroy.js:59:3)
      at process._tickCallback (internal/process/next_tick.js:63:19)

Thanks so much for reporting it! The project owner will review and triage this issue as soon as they can.

The tests work as expected the first time they are run. After that, the Box.proxy.js test fails every time with the above error.

This makes sense. What's happening is that when you run the first test, it stores the deployment in your network file, and in the second run it sees that the deployment for this particular implementation contract has already been made, but the network was reset, so when it tries to reuse it it actually sees that there is no code in it, and that's when the error you're seeing gets triggered.
The reason setting the chain id causes this problem is that the usual Hardhat Network chain id gets special treatment: we know it's an ephemeral network so when we see an invalid deployment we ignore it. For mainnet, we consider this situation unexpected and bubble the error up for the user to handle it.
But I can see a couple of reasons why you'd need to set chain id to 1. On one hand, the metadata for your current implementation version may not be stored in the network file for another chan id (we can solve this with https://github.com/OpenZeppelin/openzeppelin-upgrades/issues/175), but the proxy admin contract also won't be in the network file, and this may be an error though I think we can also fix it.
Are there other reasons why you need chain id set to 1?

Thank you for the explanation this makes a lot of sense.  What I am writing is part of a larger project, which has been using the chainId to check a signer against a particular id in the test cases of another contract.

Got it. We'll change this so a deployment with a tx that can't be found in the network is always ignored, not only on Hardhat Network. May be on Monday, sorry about the delay.

@jake-sanjuan This should be fixed on the latest release of @openzeppelin/upgrades-core.
In the end we fixed it by using web3_clientVersion to check if the node is Hardhat Network or Ganache, regardless of its chain id. But this should fix it for you.

Solved, thank you for doing that, you guys rock!


do not fail or error on absence of 'loca', 'gasp', and 'glyf' tables if font contains a 'CFF' or 'CFF2' table

Observed behaviour
Currently, with a font that contains a CFF table, we get failures or errors like:
com.google.fonts/check/062 Is 'gasp' table set to optimize rendering?
FAIL  Font is missing the 'gasp' table. Try exporting the font with autohinting enabled.

and
com.google.fonts/check/153 Check if each glyph has the recommended amount of contours.
ERROR  Failed with KeyError: 'glyf'

and
com.google.fonts/check/180 Does the number of glyphs in the loca table match the maxp table?
ERROR  Failed with KeyError: 'loca'

Expected behaviour
Don't expect loca, gasp, and glyf tables in a font that contains a CFF or CFF2 table.

This is not fixed as of version 0.5.1, e.g.:
$ fontbakery check-opentype AcuminPro-Semibold.otf
...
>> com.google.fonts/check/046 with (('font[0]', 'AcuminPro-Semibold.otf'),)
   Font contains .notdef as first glyph?
 * ERROR: Failed with KeyError: 'glyf'
           File "/usr/local/lib/python3.7/site-packages/fontbakery/checkrunner.py", line 350, in _exec_check
             for sub_result in result:  # Might raise.
           File "/usr/local/lib/python3.7/site-packages/fontbakery/specifications/general.py", line 417, in com_google_fonts_check_046
             and glyph_has_ink(ttFont, ".notdef")
           File "/usr/local/lib/python3.7/site-packages/fontbakery/utils.py", line 178, in glyph_has_ink
             glyph = font['glyf'].glyphs[name]
           File "/usr/local/lib/python3.7/site-packages/fontTools/ttLib/ttFont.py", line 382, in __getitem__
             data = self.reader[tag]
           File "/usr/local/lib/python3.7/site-packages/fontTools/ttLib/sfnt.py", line 104, in __getitem__
             entry = self.tables[Tag(tag)]

   Result: ERROR

I think the problem here is that the helper method from fontbakery.utils import glyph_has_ink directly references glyf.


Failed to establish a new connection: [WinError 10061] No connection could be made because the target machine actively refused it',))

Hello,
Thanks for writing nice wrapper. I am unable to establish a new connection.
Traceback (most recent call last):
File "C:\Users\HP PC\pycoreNLP\NLTK_Examples\nltk_examples\dbpedia_Spotter.py", line 9, in
annotations = spotlight.annotate('http://localhost/rest/annotate','Your test text', confidence=0.4, support=20)
File "C:\Users\HP PC\AppData\Local\Programs\Python\Python35\lib\site-packages\spotlight_init_.py", line 189, in annotate
pydict = post_request(address, payload, filters, headers)
File "C:\Users\HP PC\AppData\Local\Programs\Python\Python35\lib\site-packages\spotlight_init.py", line 48, in _post_request
response = requests.post(address, data=payload, headers=reqheaders)
File "C:\Users\HP PC\AppData\Local\Programs\Python\Python35\lib\site-packages\requests\api.py", line 112, in post
return request('post', url, data=data, json=json, **kwargs)
File "C:\Users\HP PC\AppData\Local\Programs\Python\Python35\lib\site-packages\requests\api.py", line 58, in request
return session.request(method=method, url=url, **kwargs)
File "C:\Users\HP PC\AppData\Local\Programs\Python\Python35\lib\site-packages\requests\sessions.py", line 513, in request
resp = self.send(prep, **send_kwargs)
File "C:\Users\HP PC\AppData\Local\Programs\Python\Python35\lib\site-packages\requests\sessions.py", line 623, in send
r = adapter.send(request, **kwargs)
File "C:\Users\HP PC\AppData\Local\Programs\Python\Python35\lib\site-packages\requests\adapters.py", line 504, in send
raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPConnectionPool(host='localhost', port=80): Max retries exceeded with url: /rest/annotate (Caused by NewConnectionError('<urllib3.connection.HTTPConnection object at 0x000002917F6D2668>: Failed to establish a new connection: [WinError 10061] No connection could be made because the target machine actively refused it',))

Closing this because it seems to be server side issue i am facing server side issue.
Exception in thread "main" java.lang.OutOfMemoryError: Java heap space

Yes, I'm pretty sure this is the problem.
Remember to raise the allowed memory that java may allocate. Maybe this helps: https://github.com/dbpedia-spotlight/dbpedia-spotlight/wiki/Troubleshooting#memory-error


Spinning forever

Since version 14.0 in Virtualmil Pro, when selecting System Statistics, the red bar goes rapidly to the right and the circles remains spinning forever. Framed Theme presents System Statistics as usual with no problems at all

You most likely need to clear browsers cache and restart Webmin. It was tested with Virtualmin Pro and it was working on my machine.
In case it still doesn't work, please go to theme settings and disable right content page loader and try again to see the actual error message. Also, I would need to know what is the script name that runs ib content page, by clicking right mouse button and opening frame source, there will be a script name. Is it history.cgi?

No success by clearing caches.
Opening the frame in a new windows I get the url https://mydomain.com:10000/virtual-server/history.cgi and the system statistics frame with no graph at all and CPU Load checked. Y I check other links in the frame I get  a blank graph. "Download raw data" link works and displays a list of   numerical data

What browser/OS your using?

Mac OS X Safari, Chrome & Firefox . All three same problem.

Disabling spinning in Theme settings I get this (no graphs at all):

And switching to Virtualmin Framed Theme everything is OK:

Yes, confirmed.

Version 14 looks OK to me, on all Internet Browsers apart from the latest Firefox. I can noticed a crash sometimes

I will fix this issue with Statistics a bit later. Sorry for that. Probably this is what's causing it in Firefox.

It will be fixed in version 14.01.

TKS!


Docs for removePage() on zend-navigation does not mention recursive delete.

Looking through the source code there is a second parameter for removePage() but the docs don't mention it.

@srayner
Please move your request to the issue tracker of the navigation component.
Thanks!


MTSRE-489 Bundles use digest format

py-mtcli
Description
Short description of the change:
Changed the tag format used by bundles to digest format.

/hold

/ok-to-test

/retest

/re-test


Add example or explanation on how to interconnect ns endpoints (nse)

Good afternoon:
With this new approach for NSM, I have noticed that you have uploaded several cases of connectivity between NSC and NSE. However, there is no example on how to interconnect different NSEs in order to perform a bigger/more complex service with NSM in this case.
If possible, do you consider adding an example of such characteristics to this repository? In my humble opinion, I think it could be a very positive addition to the examples that are already present.
Thanks!

@lewisfelix Good point... which would be the most interesting first example of that in your opinion?

@edwarnicke are you referring to those already implemented in the other NSM "examples" repository or in general? :)
In my opinion, one "simple" example (quoted because this is just simple in my mind now, I might be wrong in this one) could be using two "simple-clients" and two "simple-endpoints", interconnecting these later ones to allow both clients to be pinged though the endpoints (i.e. forcing the traffic to traverse the endpoints from one client to another).
If it is the case of those already developed for NSM, perhaps the VPN one seems to the most representative one of all, as it is the one presented in both the main repository and the website, clearly showing how multiple endpoints can cooperate to build a complex service using NSM.
Again Im just theorising here so what I am saying, or considering, now might be wrong or not the best approach for this, but I think an example of such characteristics can be potentially interesting for these new approach to NSM.
Thanks!

Waiting for moving this from Backlog into To do by @edwarnicke


Replace REPO_MIRROR_URLS with REPO_MIRROR_GRDEV_URLS

Fixes #?
Context

Contributor Checklist
Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation
[ ] Recognize contributor in release notes

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.

@bot-gradle test again please

Sorry I don't understand what you said.
Currently I support the following commands:

@bot-gradle test {BuildStage} to trigger a build

e.g. @bot-gradle test SanityCheck plz
SanityCheck/CompileAll/QuickFeedbackLinux/QuickFeedback/ReadyForMerge/ReadyForNightly/ReadyForRelease are supported
test this means test ReadyForMerge
test and merge to trigger a pre-tested commit build
cancel to cancel a running pre-tested commit build or remove it from queue
SanityCheck can be abbreviated as SC, ReadyForMerge as RFM, etc.
Specific builds:

AST: AllSmokeTestsReadyForMerge
AFT: AllFunctionalTestsReadyForMerge
ASB: AllSpecificBuildsReadyForMerge
ACC: AllConfigCacheTestsReadyForMerge
ACT: AllCrossVersionTestsReadyForNightly
APTN: AllPerformanceTestsReadyForNightly
AFTN: AllFunctionalTestsReadyForNightly
ACTR: AllCrossVersionTestsReadyForRelease
AFTR: AllFunctionalTestsReadyForRelease

@bot-gradle help to display this message
@bot-gradle clean to clear the conversation history

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.

@bot-gradle test this

OK, I've already triggered ReadyForMerge build for you.


Feature/host feature

Changes proposed in this Pull Request:

Hosting POC using firebase
Firebase console: https://console.firebase.google.com/u/3/project/pxb-storybook-ng-feature/overview
Hosted here: https://pxb-storybook-ng-feature.web.app/index.html?path=/story/intro-overview--px-blue-angular-components

Normally the URL ends with .web.app but firebase is taking its time hosting the app there correctly; I'll check tomorrow to make sure the app is actually hosted correctly, without required index.html at the end of it.

Here's what I did:

I went into<EMAIL_ADDRESS>firebase console.
Initialized a new project
Generated an access token
Put token into circleci env vars
Deploy from CI/CD

For some unknown reason, the cache is not being restored correctly during the deploy step.  Since there's only 1 dependency required & this dependency is only added for feature-branch workflows, I think it makes sense to leave the deploy command as yarn add firebase-tools && [publish].


Issue installing az cli extension

az feedback auto-generates most of the information requested below, as of CLI version 2.0.81

Describe the bug
Error when installing az extensions on Windows
To Reproduce

Download and Install az cli using Windows MSI installer on Windows 10.
Try installing an extension
Get the error: "Could not install packages due to an EnvironmentError."

Expected behavior

Extension should install successfully.

Environment summary
Windows 10 install with MSI
Manual Workaround

Update pip on the system environment
Install the extension manually by using pip outside of the az cli environment

Additional context
See details and workaround reported in this issue: https://github.com/MicrosoftDocs/azure-docs/issues/47465

Hi @jsntcy , could you please help with this ?

add to S166.

@bigdatamoore, what was the version of pip that caused the installation error?
I cannot reproduce the error on my machine with latest Azure CLI (2.5.1) and pip version on my machine is pip 20.0.2 from c:\code\azure-cli-extensions-jsntcy\env\lib\site-packages\pip (python 3.7)
I can install storage-preview successfully on my machine,

Executing pip with args: ['install', '--target', 'C:\Users\ychenu\.azure\cliextensions\storage-preview', 'C:\Users\ychenu\AppData\Local\Temp\tmpl7xxuf6f\storage_preview-0.2.10-py2.py3-none-any.whl']
Running: ['C:\Code\azure-cli-extensions-jsntcy\env\Scripts\python.exe', '-m', 'pip', 'install', '--target', 'C:\Users\ychenu\.azure\cliextensions\storage-preview', 'C:\Users\ychenu\AppData\Local\Temp\tmpl7xxuf6f\storage_preview-0.2.10-py2.py3-none-any.whl', '-vv', '--disable-pip-version-check', '--no-cache-dir']
Non-user install due to --prefix or --target option
Created temporary directory: C:\Users\ychenu\AppData\Local\Temp\pip-target-xh3x99nz
Created temporary directory: C:\Users\ychenu\AppData\Local\Temp\pip-ephem-wheel-cache-hz9s31_j
Created temporary directory: C:\Users\ychenu\AppData\Local\Temp\pip-req-tracker-ohxc4yf7
Initialized build tracking at C:\Users\ychenu\AppData\Local\Temp\pip-req-tracker-ohxc4yf7
Created build tracker: C:\Users\ychenu\AppData\Local\Temp\pip-req-tracker-ohxc4yf7
Entered build tracker: C:\Users\ychenu\AppData\Local\Temp\pip-req-tracker-ohxc4yf7
Processing c:\users\ychenu\appdata\local\temp\tmpl7xxuf6f\storage_preview-0.2.10-py2.py3-none-any.whl
Added storage-preview==0.2.10 from file:///C:/Users/ychenu/AppData/Local/Temp/tmpl7xxuf6f/storage_preview-0.2.10-py2.py3-none-any.whl to build tracker 'C:\Users\ychenu\AppData\Local\Temp\pip-req-tracker-ohxc4yf7'
Removed storage-preview==0.2.10 from file:///C:/Users/ychenu/AppData/Local/Temp/tmpl7xxuf6f/storage_preview-0.2.10-py2.py3-none-any.whl from build tracker 'C:\Users\ychenu\AppData\Local\Temp\pip-req-tracker-ohxc4yf7'
Installing collected packages: storage-preview
Created temporary directory: C:\Users\ychenu\AppData\Local\Temp\pip-unpacked-wheel-f8ogws_m
Successfully installed storage-preview-0.2.10
Cleaning up...
Removed build tracker: C:\Users\ychenu\AppData\Local\Temp\pip-req-tracker-ohxc4yf7

you can see it in the issue that I listed above that the problem was with the version of pip that was bundled with the AZ CLI.  When I tried installing the extension manually with my own local version of pip, it worked.
The version of pip that came with AZ CLI is pip 10.0.1
PS> . "C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\python.exe" -m pip --version
pip 10.0.1 from C:\Program Files (x86)\Microsoft SDKs\Azure\CLI2\lib\site-packages\pip (python 3.6)

Note, I haven't upgraded my CLI in a while, so this may be out of date now.  I will try updating later and see if it is still the case.

See this issue for more details:  https://github.com/MicrosoftDocs/azure-docs/issues/47465

so the root cause was that the version of pip bundled with the AZ CLI was out of date.

@bigdatamoore, I saw there are many very old CLI packages (acr, acs, appservice and etc.) along with azure-cli 2.0.80 on your machine, and they may cause dependency conflict. (the version of pip bundled with the AZ CLI was out of date may not be the root cause and upgrading pip version may happen to fix the error.)
azure-cli                         2.0.80 *
acr                                2.2.1 *
acs                               2.3.18 *
appservice                        0.2.14 *
botservice                         0.1.7 *
command-modules-nspkg              2.0.3
container                         0.3.14 *
core                              2.0.80 *
eventhubs                          0.3.3 *
find                              0.2.13 *
hdinsight                          0.3.1 *
network                            2.3.3 *
nspkg                              3.0.4
rdbms                              0.3.7 *
role                               2.4.1 *
servicefabric                     0.1.13 *
telemetry                          1.0.4

Before Mid of 2019, Az CLI is installed with many separated packages (acr, acs, appservice and ect.), but after that, Az CLI changed its installation mode and it is installed with only one pacakge (azure-cli).
Could you uninstall Az CLI to see if those separated packages (acr, acs, appservice and etc.) still exist? If still exist, please delete them manually, then install latest Az CLI to check if this issue is resolved or not.

Ok, I removed and re-installed AZ CLI.  I then removed and re-installed the storage-preview extension.  It installed this time without error.    So I think we can close this issue now.  Thanks!


Recursive call from typeof in output bundle

Version
3.5.4
Environment info
System:
    OS: macOS 10.14.3
    CPU: (4) x64 Intel(R) Core(TM) i7-7567U CPU @ 3.50GHz
  Binaries:
    Node: 10.15.1 - /usr/local/bin/node
    Yarn: 1.13.0 - /usr/local/bin/yarn
    npm: 6.9.0 - /usr/local/bin/npm
  Browsers:
    Chrome: 73.0.3683.86
    Firefox: Not Found
    Safari: 12.0.3
  npmPackages:
    @vue/babel-helper-vue-jsx-merge-props:  1.0.0-beta.3
    @vue/babel-plugin-transform-vue-jsx:  1.0.0-beta.3
    @vue/babel-preset-app:  3.5.4
    @vue/babel-preset-jsx:  1.0.0-beta.3
    @vue/babel-sugar-functional-vue:  1.0.0-beta.3
    @vue/babel-sugar-inject-h:  1.0.0-beta.3
    @vue/babel-sugar-v-model:  1.0.0-beta.3
    @vue/babel-sugar-v-on:  1.0.0-beta.3
    @vue/cli-overlay:  3.5.1
    @vue/cli-plugin-babel: ^3.2.0 => 3.5.4
    @vue/cli-plugin-eslint: ^3.2.1 => 3.5.1
    @vue/cli-service: ^3.3.0 => 3.5.3
    @vue/cli-shared-utils:  3.5.1
    @vue/component-compiler-utils: ^2.5.0 => 2.6.0
    @vue/eslint-config-standard: ^4.0.0 => 4.0.0
    @vue/preload-webpack-plugin:  1.1.0
    @vue/web-component-wrapper:  1.2.0
    babel-helper-vue-jsx-merge-props:  2.0.3
    eslint-plugin-vue: ^5.0.0-0 => 5.2.2
    vue: ^2.5.17 => 2.6.10
    vue-echarts-v3: ^1.0.19 => 1.0.19
    vue-eslint-parser:  5.0.0
    vue-hot-reload-api:  2.3.3
    vue-loader: ^15.4.2 => 15.7.0
    vue-router: ^3.0.1 => 3.0.2
    vue-style-loader:  4.1.2
    vue-template-compiler: ^2.5.17 => 2.6.10
    vue-template-es2015-compiler:  1.9.1
    vuex: ^3.0.1 => 3.1.0
  npmGlobalPackages:
    @vue/cli: Not Found

Steps to reproduce
when you use js typeof keyword, you will get this
What is expected?
no error!
What is actually happening?
RangeError: Maximum call stack size exceeded
    at _typeof2 (typeof.js?53ca:1)
    at _typeof (typeof.js?53ca:4)
    at _typeof2 (typeof.js?53ca:1)
    at _typeof (typeof.js?53ca:4)
    at _typeof2 (typeof.js?53ca:1)
    at _typeof (typeof.js?53ca:4)
    at _typeof2 (typeof.js?53ca:1)
    at _typeof (typeof.js?53ca:4)
    at _typeof2 (typeof.js?53ca:1)
    at _typeof (typeof.js?53ca:4)

Can you provide a reproduction? I can suspect some scenarios where typeof may be troublesome but right now I can't reproduce it on my machine.

Ah I got it.

any updates ?

The same issue here.
It doesn't work on V3.5.4.
But it works with 3.5.3.

Just conformed @lizux's suggestion to use 3.5.3, and this worked for me

https://github.com/savoygu/test-typeof
the project is generated using the version @vue/cli3.5.4, when you run, just open browser developer tools will see the error

I tried<EMAIL_ADDRESS>but still not work. So, I am trying to using<EMAIL_ADDRESS>to create a new project. However, it seems
vue create app

is always using the latest @vue/cli, So how can i create with<EMAIL_ADDRESS>@sodatea


Added autoclose exempt label for GitHub Bot

Checklist
(Check off all the items before submitting)

[x] Build process is done without errors. All tests pass in the /lib directory.
[x] Self-reviewed the code before submitting.
[x] Meets accessibility standards.
[x] Added/updated documentation to /website as needed.
[x] Added/updated tests as needed.

Description
Now, issues labeled with "non-closable" are not marked as stale or get automatically closed.

It is still pending to decide if it the tag will be called 'non-closable', 'non closable' or another.


UnoformGridLayout uses assignment instead of comparison

Describe the bug
On this line: https://github.com/microsoft/microsoft-ui-xaml/blob/61ea8fb19e84504a909cbe7bfa40202d2dc09090/dev/Repeater/UniformGridLayout.cpp#L270
That should be a comparison, not an assignment,
Version Info
Current master
Additional context
Apologies for not filling in more of the sections, but I think this describes the issue sufficiently.

Yikes! Great catch @grokys. @Ranjeshj, good opportunity to switch Repeater over to the per-property codegen callbacks.

In case you're wondering how I noticed this, I'm porting ItemsRepeater to Avalonia: https://github.com/AvaloniaUI/Avalonia/pull/2603 -- just in case you're interested!


pre-commit: integrate with cndp

Install pre-commit for CNDP + its configuration.
Remove old githook.

Sorry for the noise - it took a while to find the right recipe of clang versions between pre-commit hooks and the github action

:) Markdown linter disconnect now :(

Should this get merged now or will you be fixing the Lint Code Base issues?

I will fix them :)

Linting issues are now fixed. I just rebased there and kicked off the github actions again. As soon as they complete we should be good.
Sorry again for all the noise :( I couldn't reproduce the issues locally

No problem it is a lot of work, Thanks


Revert "Revert "Fix JLD2 julia compat" (#93526)"

Since this: https://github.com/JuliaLang/Pkg.jl/pull/3666
is merged, I think this compat bound change can be reapplied.
This reverts commit 3ede379e7b7040a1a0a8e1bae911afa08d9169b8.
Referencing https://github.com/JuliaIO/JLD2.jl/issues/490
Pinging @IanButterworth, since you did the other PRs.

Agreed. Thanks for tracking that


Removing a folder from multi-root workspace does not remove repo

Version: 1.50.1 (user setup)
Commit: d2e414d9e4239a252d1ab117bd7067f125afd80a
Date: 2020-10-13T15:06:15.712Z
Electron: 9.2.1
Chrome: 83.0.4103.122
Node.js: 12.14.1
V8: <IP_ADDRESS>-electron.0
OS: Windows_NT x64 10.0.19041
Steps to Reproduce:

Create a multi-root workspace:

folder_A contains git-repo A
folder_B contains git-repo B

SCM pane shows repo A and repo B

Remove folder_B from workspace
SCM pane still shows repo B (expected: repo B is automatically closed/removed)

Select "close repo" on repo B
repo B vanishes from SCM pane

reopen workspace
SCM pane again shows repo B (expected: repo B does no longer show up)

Workaround: Delete workspace settings under C:\Users\<username>\AppData\Roaming\Code\User\workspaceStorage.

Does this issue occur when all extensions are disabled?: Yes/No

I would like to try to help with this, but I can't reproduce the issue. In step 2 of "Steps to Reproduce", you state "Remove folder_B". I am assuming this means the "Remove Folder from Workspace" option in the VS Code Explorer. Is this correct?

...you state "Remove folder_B". I am assuming this means
the "Remove Folder from Workspace" option in the VS Code Explorer. Is this correct?

Thats correct.

Okay, I think I've reproduced the issue. The key is to have a file from "folder_B" open in the editor before you remove that folder from the workspace. I've been able to reliably reproduce the issue this way. I think this would explain why your workaround resolves it since deleting the workspaceStorage would essentially mean that the file would no longer be open in the editor. Note that you can also work around this by just closing the file in the editor, then next time you open the workspace, "git-repo B" will not show in the SCM window (you don't even have to "Close Repository" manually as you do in step 3).
I'm also curious if this would happen with any SCM plug-in, not just Git. My guess is that it would, but I have not tested this.

I am experiencing this bug; I'm not quite sure what sequence of actions got me here.
Even after right clicking the repo in source control and clicking "Close Repository", the repository is reopened the next time I open the workspace.

Can I work on this issue? I am participant of opensourceday2021.

Thx gustavo-reyes for the workaround => close files, exit workspace, re-open workspace. Worked!

@lszomoru Should removing a folder from multi root workspace remove it from the git extension?

SCM pane still shows repo B (expected: repo B is automatically closed/removed)

When closing a folder in multi-root workspace, the folder is removed only if there are no open files in editor. Is this expected behaviour?

On both a Mac and Win environment I notice that adding a folder to the workspace correctly adds the associated Git repos in SCM, but removing the folder never removes the repos from SCM. Closing & re-opening the workspace resolves this, as long as you don't have a file open from that added folder.
So I would say there is 1 bug and 1 potential bug:

Bug: When removing a folder with Git repos from the workspace, SCM will not (automatically) reflect this removal.
Questionable behaviour: When a file of a removed folder (from a workspace) is open, the SCM will keep the Git repo the open file is residing in. (At least with resolution of the bug, the repo(s) should be removed from SCM after the files are closed.)

Is someone here who can guide me on how to contribute in the issues. I am completely new in open source contribution and want to contribute but I can not understand from where and how to start ?

In (Model.ts) private async onDidChangeWorkspaceFolders:
This function checks for active repositories (i.e. repositories associated with visible open file tabs)
Then the openRepositoriesToDispose is set to check if any of the repositories to remove are not included in the active repository list.
The repository should only be removed from the workspace with a folder removal if it doesn’t have an active open file associated with the repository.
The behavior of removing a second folder from the workspace operates (I believe)  correctly in the following circumstances:

Add folder to workspace that already contains a folder, open file in new folder, remove new folder from workspace: i.e. the repository is not removed from the open git repositories.
Add folder to workspace that already contains a folder, remove new folder from workspace: i.e. the repository is removed from the open git repositories.
Add folder to workspace that already contains a folder, open file in new folder, close vscode, open vscode again (with automatic restoration of open files in workspace), remove new folder from workspace: i.e. the repository for the new folder is not removed from the git repository list.

Different behavior occurs with the following actions:

Add folder to a workspace that already contains a folder, open file in existing folder, remove existing workspace: i.e. the repository for the existing folder is removed from the git repository list. The whole repository list seems to be cleared and then reloaded with just the remaining open folder’s repository (before/outside the call to this method)

So I would probably modify or close this ticket to the unexpected repository removal behavior on the removal of the second folder from the workspace if it is indeed behaving as expected, and then ask the following question:
Is the behavior of removing the first folder in the workspace incorrect when a file from that folder is open in the visible tabs? And if so, then that should be investigated and fixed (which I am happy to continue investigating).


(WIP)ci: m1 support

Description

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] The commit message(s) follow conventional commits
[ ] Documentation has been added / updated (for bug fixes / features)
[ ] Changes follow the contributing document.

Motivation and Context

Does this PR introduce a breaking change?

[ ] Yes
[x] No

Which merge strategy will you use?

[x] Squash
[ ] Rebase (REVIEW COMMITS)

public repo don't have access to self-hosted runner by default


how do you control MA on iPhone?

since there isn't IOS app available for MA.
owntone server + rigelian ios app is nice
but owntone isn't as strong as MA.

Until the official Music Assistant mobile app gets released, you can probably install the webapp as a PWA

Edit: To clarify that will only allow you to control MA, not stream music to the phone

Yeah I would also like to stream music to our iPhones and Android mobile phones

How much effort would it take to bundle a Squeezebox and/or Snapcast client in the mobile app?

Until the official Music Assistant mobile app gets released …

How much effort would it take to bundle a Squeezebox and/or Snapcast client in the mobile app?

I have no idea how much ”effort” it would be to add local playback to mobile companion apps but read a recent comment from this companion app’s lead developer that he is away from this project for the next year or so, meaning its not something that he would have time to work on, but that other contributors are more than welcome to work on this. So seems like ”someone else” needs to take on coding tasks like those and contribute that code to this project.
I did not either see anything related to companion app listed on the MA developers backlog, however guess that list is more like MA servers and add-on developers own wishlist if time permits:
https://github.com/orgs/music-assistant/projects/2/views/1
Regardless, you still have to remember that this is a free and open-source hobby project that is only developed in developers spare time for fun or as a challange to themselves, as such they are not getting paid to work on anything related to Music Assassint. What drives development is the personal interest and pride of developers, and only as time permits as most probably also have full-timw school and/or jobs outside working on these hobby projects.

How much effort would it take to bundle a Squeezebox and/or Snapcast client in the mobile app? As a temporary solution, I use Snapdroid combined with the Home Assistant app. If you install MA as an add-on, you can add the webapp to the sidebar in Home Assistant.

Android probably wouldn't be that much work. Don't know about IOS.

Until the official Music Assistant mobile app gets released …

How much effort would it take to bundle a Squeezebox and/or Snapcast client in the mobile app?

I have no idea how much ”effort” it would be to add local playback to mobile companion apps but read a recent comment from this companion app’s lead developer that he is away from this project for the next year or so, meaning its not something that he would have time to work on, but that other contributors are more than welcome to work on this. So seems like ”someone else” needs to take on coding tasks like those and contribute that code to this project.
I did not either see anything related to companion app listed on the MA developers backlog, however guess that list is more like MA servers and add-on developers own wishlist if time permits:
https://github.com/orgs/music-assistant/projects/2/views/1
Regardless, you still have to remember that this is a free and open-source hobby project that is only developed in developers spare time for fun or as a challange to themselves, as such they are not getting paid to work on anything related to Music Assassint. What drives development is the personal interest and pride of developers, and only as time permits as most probably also have full-timw school and/or jobs outside working on these hobby projects.

Yes, that is all exactly correct! Thank you 🙏


Files show as absolute file path instead of relative file path in toml

I created a new quarto deployment in Positron. The following toml was auto-generated for me:
'$schema' = 'https://cdn.posit.co/publisher/schemas/posit-publishing-schema-v3.json'
type = 'quarto'
entrypoint = 'slides.qmd'
validate = true
files = [
  '/slides.qmd',
]

The above deployment works. But, I think that the files section should use relative paths, as opposed to absolute paths:
files = [
  './slides.qmd',
]

or
files = [
  'slides.qmd',
]

/slides.qmd should actually fail because this path points to a file at the root of my computer that does not exist.
System info
Posit Publisher:
v1.1.6 (pre-release)

Positron:
Positron Version: 2024.09.0 (Universal) build 45
Code - OSS Version: 1.92.0
Commit: b0ec249b20455499f9e79ffe0bec35a5ff602ea4
Date: 2024-09-16T02:45:13.900Z
Electron: 30.1.2
Chromium: 124.0.6367.243
Node.js: 20.14.0
V8: <IP_ADDRESS>-electron.0
OS: Darwin arm64 23.6.0

Thanks for submitting the issue!
The files inclusions use gitignore syntax so the leading / is not an absolute file path, rather is specifying that only slides.qmd at the root directory should be included rather than all files named slides.qmd which what would occur with slides.qmd on its own.
./slides.qmd works similarly to /slides.qmd
Does this clarity help or do you think a change should still be made?

Thanks for the reply. That makes sense. I did not know that about gitignore syntax.
I do wonder if gitignore is the best syntax to use? My assumption (I didn't read the docs), was that it would be "file system syntax". My hunch is that this is what most people would expect. Especially when coming from the mindset of application deployment. For example how you copy files from your machine to an image when building docker files.

I do wonder if gitignore is the best syntax to use? My assumption (I didn't read the docs), was that it would be "file system syntax". My hunch is that this is what most people would expect. Especially when coming from the mindset of application deployment. For example how you copy files from your machine to an image when building docker files.

Yeah, I'm not sure that leaning heavily on the gitignore syntax is the most friendly here. Some people might be familiar with it, but it's not as common as Docker or the more general (ba|z)sh approaches that I think more data scientists will be more familiar with.
What would it take for us to transition (or support both?)?

What would it take for us to transition

We would have to re-write our matcher go package that we introduced in #1192 based on the new spec we choose / create(?)

(or support both?)

When you ask if we can support both are you thinking being able to specify which format or match both? If matching both I think we'd have to outline both specs and how they overlap.
It seems like the glob syntax is the most applicable to docker / bash / zsh approaches? Does that seem right?

It seems like the glob syntax is the most applicable to docker / bash / zsh approaches? Does that seem right?

Yeah, this is much more common in my experience, but would love other opinions.

When you ask if we can support both are you thinking being able to specify which format or match both? If matching both I think we'd have to outline both specs and how they overlap.

Yeah, honestly supporting both sounds like it would be problematic. We likely could do it given that we are always starting at the parent of the (parent of) the config file directory — we treat that as the root. True full-root-specified paths would be problematic (since you can't include files outside of the directory you're publishing from). But just writing that out + imagining how we would document it and explain what's up sounds like a lot (and honestly would make the whole thing more complicated sounding than it actually is).

We would have to re-write our matcher go package that we introduced in https://github.com/posit-dev/publisher/pull/1192 based on the new spec we choose / create(?)

If this is too hard to unwind now, that's fine. The UI for doing this makes it so that someone isn't required to know about it. But is a little unfortunate (a good reminder to us about being vigelent in our user-focus in our decision making for things like this).


How to handle layout modifiers attached to struct fields?

There is a general problem that has bit me a few times in adding features to Slang, and I want to document it here so that we can iterate on a proposed solution.
Type layout information is computed from types, rather than being inherent to them; this is pretty much required by the semantics of HLSL, and to target GLSL, because the same type can be laid out differently in different contexts. E.g., if I have a struct Foo, then a row_major Foo is different than a column_major Foo, which is different from a centroid Foo, etc.
Because a TypeLayout is distinct from a Type in Slang, we have a TypeLayout when we go to output a variable or cbuffer declaration, but we do not have that layout information when we go to output struct Foo.
For layout information that applies strictly to a variable of type Foo, that is fine, but in many cases a particular layout will require something to be declared on the fields of Foo. This comes up for:

Interpolation mode qualifiers
Matrix layout mode qualifiers
Semantics

In each of these cases, in order to emit a struct declaration correctly, we need to have a representation of these features at the level of the IR type, so that we can spit a suitable declaration back out.
However, such a representation would be redundant with the information in a TypeLayout when we are emitting the body of a cbuffer, or when we are emitting a top-level varying paramter, so in those cases we use the TypeLayout information instead. This causes duplication of code, where anything we need to support for ordinary shader parameters also needs a second mechanism that applies to struct fields.
The duplication can lead to a variety of bugs, when we forget to add support for a feature on struct fields and only implement it for true shader parameters, or when the logic isn't quite the same between the two cases. There is also a concern that when we apply modifiers to fields in output HLSL/GLSL, we are ultimately trying to drive the downstream compiler's behavior to reproduce layout work we already did, and this seems risky.
What are the options for eliminating this kind of duplication?

For varying input/output we can potentially try to scalarize everything so that the actual interface doesn't use any struct types, so there are no fields to worry about. This raises questions about AOS->SOA conversion, and also has challenges for stages where the input/output must always be specified as a struct for HLSL.

Similarly and more generally, we could decide that in these cases a TypeLayout should give rise to its own custom type (a distinct struct declaration per unique layout...), and then we can/should copy from the type-with-layout to values with the ordinary undecorated type as needed.

On the flip side, we could decide that a struct declaration should be output using some kind of "default" layout, which can then be used to attach all the additional modifiers and such to its fields. The challenge there is that such a layout would need to combine aspects of uniform and varying layout, to be able to handle a struct that might be used in both contexts.

This is a messy issue, and I'm not entirely happy with any of the options.

Closing due to inactivity --- can reopen if we find a need.


Add support for add_theme_support( 'genesis-footer-widgets', num_cols );

where num_cols is an integer like (2, 3, or 4)
http://my.studiopress.com/tutorials/add-footer-widgets/ (Requires Studiopress Membership)

hi @salcode I tried to add widgets on Genesis-Bootstrap but it is using Genesis markup, I added some mark up at bsg_add_markup_class() function.
I want to change the footer-widgets-# to col-sm-3. How I am going to add it?
Regards,

Hi @unwiredtech,
It looks like we need to add the class to these divs (.footer-widgets-1, .footer-widgets-2, .footer-widgets-3, .footer-widgets-4) and unfortunately there is not a filter for that (see lib/structure/footer.php in the Studiopress Genesis theme).

If you need this functionality, I would add CSS to the project to .footer-widgets .widget-area to get it to behave the way you want.
Best of luck and I'd love to hear about the solution you find.

@salcode Hello, thank you for the fast response.
You are right, I tried to inject the class for the footer-widgets-x but it did not work. As you said I added the CSS the way you describe.
Great framework!
Cheers!

Glad to hear you got it working and that you find Bootstrap Genesis useful in general.
Thanks for the kind words. :+1:

See https://github.com/JiveDig/baseline/blob/master/includes/layout.php#L39 by @JiveDig for a solution using the current version of Genesis.


Go back from font section with back button/esc

Atm the only way is pressing the X

Good one! Will look into this for the next update. :)

Added by @yaichenbaum! 😎


Possibility for place text in the same way as we place polyline, circle etc

When importing a DXF to Leaflet, the polygons are appearing just fine, that is so amazing.
But this DXF also includes a lot of text both aligned with polylines, but also "floating" as description for various things.
I've tried using bindToolTip, and styling it. But it does not behave correctly since it does not scale on zoom like polylines etc.
So in general. A place text functionality would be amazing

I don't know if this addresses your issue in regard to DXF but have you looked at Leaflet.Illustrate by Justin Manley? It's kind of rough but there's potential there for placing text.

Thank. No I've not used it, and I don't think I dare.
It has not been updated for years, so the project looks kinda dead!?
And I cannot use thing that might be buggy :-)
But again, thanks


Added redux to disclaimer modal

fixes #200
Still need to add some CSS styling to make it look nice and fix the mobile view.

Looks great @Tanvez - super clean! Would you want me to leave this open/marked as WIP until you get the styling done?

Yea sounds good! Will let you know when the styling is done.

Updated the CSS for the Disclaimer modal. Let me know if i should change anything.

Awesome!


Update Github pull request template to have a task for inspecting failing checks

Description
Update Github pull request template to have a task for inspecting failing checks. Since we have not got the consensus on https://github.com/opensearch-project/OpenSearch/issues/10371, and this issue does not only persist but gets worst with mostly every new feature integrated, there is an alternative path to tackle the problem making it a part of the process.
The idea is to at least ask every contributor to inspect the failing checks (we are talking about Gradle checks primarily) and make a reference (by commenting) to:

an existing known issue
or, create and attach a new issue

It won't solve the problem of flaky tests going away but at least we may get attention (hopefully engaging more engineers into fixing flaky tests) and we should at least spot a new flaky tests proactively (since right now most people just push or retrigger the checks).
Related Issues

Relates to https://github.com/opensearch-project/OpenSearch/issues/10371

Check List

[ ] New functionality includes testing.

[ ] All tests pass

[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[x] Failing checks are inspected and point to the corresponding known issue(s)
[x] Commits are signed per the DCO using --signoff
[ ] Commit changes are listed out in CHANGELOG.md file (See: Changelog)
[ ] Public documentation issue/PR created

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.

I suspect most people ignore these check boxes, and we already have text that says the same thing. We can highlight that, or maybe find a way to block PRs where the failures haven't been examined?

URL: https://build.ci.opensearch.org/job/gradle-check/28462/

Should be fixed by https://github.com/opensearch-project/OpenSearch/pull/10754

Thanks @reta I like documenting expectations for contributors; however, this might be easy to forget for them to do and for maintainers to forget to follow up on - I am only human.
Borrowing from the security repo [link], we have a process of publicly documenting practices to inform intentions.  I'm curious what you think of this approach - maybe you'd want to add a first practice to OpenSearch for this scenario?

URL: https://build.ci.opensearch.org/job/gradle-check/28485/

https://github.com/opensearch-project/OpenSearch/issues/10749

@dblock are you good with that? :-)


Minor: Integration into conda environment

Describe The Bug
We have a conda-forge recipe for cargo-make: https://github.com/conda-forge/cargo-make-feedstock
The latest update broke one of the simplistic tests we performed on the built package: cargo-make --help (makers --help sitll works) for every releases. For now we have commentted out the test to continue provide the up-to-date package. It would be great if you could confirm that the behavior is discontinued, or could suggest a simple test to validate the correct behavior of cargo-make within the conda environment
To Reproduce
cargo-make --help
Error Stack
+ cargo-make -h
`cliparser::types::ParserError` error. InvalidCommandLine("Command does not match spec, command line: [\"cargo-make\", \"-h\"]")
exit code 731

If you wish to be added to the list of maintainer, please submit an issue:
https://github.com/conda-forge/cargo-make-feedstock/issues/new?assignees=&labels=&projects=&template=2-bot-commands.yml
with:
@conda-forge-admin, please add user @

thanks for reporting. my guess its related to #1112 by @SamuelMarks
if he can solve it, amazing. if not, unfortunately I won't have availability for coming 2 weeks :( and than I'll be able to check it out.

Yes I'll take a look at the --version and --help flags when I get back (getting ☕ now)

Update: it breaks here https://github.com/sagiegurari/cliparser/blob/e8f2bfb/src/parser.rs#L169
Might need to send that project of yours a PR

Sent through this simple change, tell me if it resolves your issue @MementoRC  https://github.com/sagiegurari/cliparser/pull/3

Thanks for the updates. conda-forge recipe builds on top of official releases or tags and we allowed the latest version to go live based upon your initial response. We will revisit at the next release

@MementoRC sorry didn't have a computer available for a while. going back to this it seems odd it ever worked for you. probably some bug.
there are 3 ways to run cargo make

makers
cargo make
cargo-make make # this one basically because how 'cargo' works

its strange it worked differently. 2 and 3 are for cargo integration so its always a sub command while the first is standalone so it doesn't need the 'extra' make sub command.
can you change the test to: cargo-make make -h instead?

Ok, I will try it with the new release

All good. Released. Thank you


RWA-958: Add missing permissions

JIRA link (if applicable)
https://tools.hmcts.net/jira/browse/RWA-958
Change description
Add missing scenarios
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x ] No

LGTM


Black is not working

Python 3.11.3, VSCode  1.77.3, Black v2023.2.0, or v2023.3.10961008 (doesn't matter, both are not working).
Black works only in the terminal.
Output:
2023-04-24 03:47:34.217 [info] Name: Black Formatter
2023-04-24 03:47:34.217 [info] Module: black
2023-04-24 03:47:36.666 [error] Python version undefined.undefined is not supported.
2023-04-24 03:47:36.666 [error] Selected python path: undefined
2023-04-24 03:47:36.666 [error] Supported versions are 3.7 and above.
2023-04-24 03:47:36.669 [info] Server run command: /Users/hipertracker/.asdf/shims/black /Users/hipertracker/.vscode/extensions/ms-python.black-formatter-2023.3.10961008/bundled/tool/lsp_server.py
2023-04-24 03:47:36.669 [info] Server: Start requested.
2023-04-24 03:47:36.837 [info] All done! ✨ 🍰 ✨
1 file left unchanged.

2023-04-24 03:47:36.846 [info] [Error - 03:47:36] Server initialization failed.
2023-04-24 03:47:36.847 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-04-24 03:47:36.847 [info] [Info  - 03:47:36] Connection to server got closed. Server will restart.
2023-04-24 03:47:36.847 [info] true
2023-04-24 03:47:36.847 [info] [Error - 03:47:36] Black Formatter client: couldn't create connection to server.
2023-04-24 03:47:36.847 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-04-24 03:47:37.021 [info] All done! ✨ 🍰 ✨
1 file left unchanged.

2023-04-24 03:47:37.031 [info] [Error - 03:47:37] Server initialization failed.
2023-04-24 03:47:37.031 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-04-24 03:47:37.031 [info] [Info  - 03:47:37] Connection to server got closed. Server will restart.
2023-04-24 03:47:37.031 [info] true
2023-04-24 03:47:37.031 [info] [Error - 03:47:37] Black Formatter client: couldn't create connection to server.
2023-04-24 03:47:37.031 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-04-24 03:47:37.031 [error] Server: Start failed: Error: Pending response rejected since connection got disposed
2023-04-24 03:47:37.204 [info] All done! ✨ 🍰 ✨
1 file left unchanged.

2023-04-24 03:47:37.213 [info] [Error - 03:47:37] Server initialization failed.
2023-04-24 03:47:37.213 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-04-24 03:47:37.213 [info] [Info  - 03:47:37] Connection to server got closed. Server will restart.
2023-04-24 03:47:37.213 [info] true
2023-04-24 03:47:37.213 [info] [Error - 03:47:37] Black Formatter client: couldn't create connection to server.
2023-04-24 03:47:37.213 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-04-24 03:47:37.213 [info] [Error - 03:47:37] Restarting server failed
2023-04-24 03:47:37.213 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-04-24 03:47:37.373 [info] All done! ✨ 🍰 ✨
1 file left unchanged.

2023-04-24 03:47:37.382 [info] [Error - 03:47:37] Server initialization failed.
2023-04-24 03:47:37.382 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-04-24 03:47:37.382 [info] [Info  - 03:47:37] Connection to server got closed. Server will restart.
2023-04-24 03:47:37.382 [info] true
2023-04-24 03:47:37.382 [info] [Error - 03:47:37] Black Formatter client: couldn't create connection to server.
2023-04-24 03:47:37.382 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-04-24 03:47:37.382 [info] [Error - 03:47:37] Restarting server failed
2023-04-24 03:47:37.382 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-04-24 03:47:37.550 [info] All done! ✨ 🍰 ✨
1 file left unchanged.

2023-04-24 03:47:37.559 [info] [Error - 03:47:37] Server initialization failed.
2023-04-24 03:47:37.559 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-04-24 03:47:37.559 [info] [Error - 03:47:37] The Black Formatter server crashed 5 times in the last 3 minutes. The server will not be restarted. See the output for more information.
2023-04-24 03:47:37.559 [info] [Error - 03:47:37] Black Formatter client: couldn't create connection to server.
2023-04-24 03:47:37.559 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-04-24 03:47:37.559 [info] [Error - 03:47:37] Restarting server failed
2023-04-24 03:47:37.559 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097

I've had this same issue crop up in that last week or two.  I haven't changed any settings, and uninstalling and re-installing the extension didn't fix it.
Python:Report Issue Output
Type: Bug

Behaviour
Expected vs. Actual
Expected: Black formatter formats code
Actual: Black formatter crashes on start
Steps to reproduce:

Install black formatter
Restart VS Code

Diagnostic data

Python version (& distribution if applicable, e.g. Anaconda): 3.10.6
Type of virtual environment used (e.g. conda, venv, virtualenv, etc.): Global
Value of the python.languageServer setting: Default

Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)

XXX

User Settings

languageServer: "Pylance"

formatting
• provider: "none"

Extension version: 2023.2.0
VS Code version: Code 1.77.3 (704ed70d4fd1c6bd6342c436f1ede30d1cff4710, 2023-04-12T09:16:52.732Z)
OS version: Linux x64 5.15.0-60-generic
Modes:
Sandboxed: No

System Info

Item
Value

CPUs
Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz (16 x 2300)

GPU Status
2d_canvas: enabledcanvas_oop_rasterization: disabled_offdirect_rendering_display_compositor: disabled_off_okgpu_compositing: enabledmultiple_raster_threads: enabled_onopengl: enabled_onrasterization: enabledraw_draw: disabled_off_okskia_renderer: enabled_onvideo_decode: disabled_softwarevideo_encode: disabled_softwarevulkan: disabled_offwebgl: enabledwebgl2: enabledwebgpu: disabled_off

Load (avg)
2, 2, 2

Memory (System)
30.99GB (26.88GB free)

Process Argv
--unity-launch --crash-reporter-id f0bf3635-4727-4c1a-b142-92f1c6e8b1e8

Screen Reader
yes

VM
0%

DESKTOP_SESSION
ubuntu

XDG_CURRENT_DESKTOP
Unity

XDG_SESSION_DESKTOP
ubuntu

XDG_SESSION_TYPE
x11

A/B Experiments
vsliv368:30146709
vsreu685:30147344
python383cf:30185419
vspor879:30202332
vspor708:30202333
vspor363:30204092
vstes627:30244334
vslsvsres303:30308271
vserr242:30382549
pythontb:30283811
vsjup518:30340749
pythonptprofiler:30281270
vshan820:30294714
vstes263:30335439
pythondataviewer:30285071
vscod805:30301674
binariesv615:30325510
bridge0708:30335490
bridge0723:30353136
cmake_vspar411:30581797
vsaa593:30376534
pythonvs932:30410667
cppdebug:30492333
vscaat:30438848
vsclangdc:30486549
c4g48928:30535728
dsvsc012:30540252
pynewext54:30695312
azure-dev_surveyone:30548225
nodejswelcome1cf:30587006
3biah626:30602489
pyind779:30671433
89544117:30613380
pythonsymbol12:30671437
a9j8j154:30646983
azdwalk:30721579
pythonms35:30701012
pythonfmttext:30716742
pythonclientmvcf:30725893

Output Log:
2023-05-01 11:29:52.975 [info] Name: Black Formatter
2023-05-01 11:29:52.975 [info] Module: black
2023-05-01 11:29:52.975 [info] Python extension loading
2023-05-01 11:29:52.975 [info] Waiting for interpreter from python extension.
2023-05-01 11:29:52.975 [info] Python extension loaded
2023-05-01 11:29:52.975 [info] Server run command: /bin/python /home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/tool/lsp_server.py
2023-05-01 11:29:52.975 [info] Server: Start requested.
2023-05-01 11:29:53.293 [info] Traceback (most recent call last):
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/tool/lsp_server.py", line 40, in <module>
    import lsprotocol.types as lsp
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/lsprotocol/types.py", line 14, in <module>
    import attrs
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/attrs/__init__.py", line 3, in <module>
    from attr import (
ImportError: cannot import name 'AttrsInstance' from 'attr' (/usr/lib/python3/dist-packages/attr/__init__.py)

2023-05-01 11:29:53.304 [info] [Error - 11:29:53 AM] Server initialization failed.
2023-05-01 11:29:53.304 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-05-01 11:29:53.304 [info] [Info  - 11:29:53 AM] Connection to server got closed. Server will restart.
2023-05-01 11:29:53.304 [info] true
2023-05-01 11:29:53.304 [info] [Error - 11:29:53 AM] Black Formatter client: couldn't create connection to server.
2023-05-01 11:29:53.304 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-05-01 11:29:53.640 [info] Traceback (most recent call last):
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/tool/lsp_server.py", line 40, in <module>
    import lsprotocol.types as lsp
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/lsprotocol/types.py", line 14, in <module>
    import attrs
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/attrs/__init__.py", line 3, in <module>
    from attr import (
ImportError: cannot import name 'AttrsInstance' from 'attr' (/usr/lib/python3/dist-packages/attr/__init__.py)

2023-05-01 11:29:53.643 [info] [Error - 11:29:53 AM] Server initialization failed.
2023-05-01 11:29:53.643 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-05-01 11:29:53.643 [info] [Info  - 11:29:53 AM] Connection to server got closed. Server will restart.
2023-05-01 11:29:53.643 [info] true
2023-05-01 11:29:53.643 [info] [Error - 11:29:53 AM] Black Formatter client: couldn't create connection to server.
2023-05-01 11:29:53.643 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-05-01 11:29:53.643 [error] Server: Start failed: Error: Pending response rejected since connection got disposed
2023-05-01 11:29:53.969 [info] Traceback (most recent call last):
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/tool/lsp_server.py", line 40, in <module>
    import lsprotocol.types as lsp
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/lsprotocol/types.py", line 14, in <module>
    import attrs
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/attrs/__init__.py", line 3, in <module>
    from attr import (
ImportError: cannot import name 'AttrsInstance' from 'attr' (/usr/lib/python3/dist-packages/attr/__init__.py)

2023-05-01 11:29:54.029 [info] [Error - 11:29:54 AM] Server initialization failed.
2023-05-01 11:29:54.029 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-05-01 11:29:54.029 [info] [Info  - 11:29:54 AM] Connection to server got closed. Server will restart.
2023-05-01 11:29:54.029 [info] true
2023-05-01 11:29:54.029 [info] [Error - 11:29:54 AM] Black Formatter client: couldn't create connection to server.
2023-05-01 11:29:54.029 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-05-01 11:29:54.029 [info] [Error - 11:29:54 AM] Restarting server failed
2023-05-01 11:29:54.029 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-05-01 11:29:54.294 [info] Traceback (most recent call last):
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/tool/lsp_server.py", line 40, in <module>
    import lsprotocol.types as lsp
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/lsprotocol/types.py", line 14, in <module>
    import attrs
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/attrs/__init__.py", line 3, in <module>
    from attr import (
ImportError: cannot import name 'AttrsInstance' from 'attr' (/usr/lib/python3/dist-packages/attr/__init__.py)

2023-05-01 11:29:54.502 [info] [Error - 11:29:54 AM] Server initialization failed.
2023-05-01 11:29:54.502 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-05-01 11:29:54.502 [info] [Info  - 11:29:54 AM] Connection to server got closed. Server will restart.
2023-05-01 11:29:54.502 [info] true
2023-05-01 11:29:54.502 [info] [Error - 11:29:54 AM] Black Formatter client: couldn't create connection to server.
2023-05-01 11:29:54.502 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-05-01 11:29:54.502 [info] [Error - 11:29:54 AM] Restarting server failed
2023-05-01 11:29:54.502 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-05-01 11:29:54.725 [info] Traceback (most recent call last):
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/tool/lsp_server.py", line 40, in <module>
    import lsprotocol.types as lsp
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/lsprotocol/types.py", line 14, in <module>
    import attrs
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/attrs/__init__.py", line 3, in <module>
    from attr import (
ImportError: cannot import name 'AttrsInstance' from 'attr' (/usr/lib/python3/dist-packages/attr/__init__.py)

2023-05-01 11:29:54.777 [info] [Error - 11:29:54 AM] Server initialization failed.
2023-05-01 11:29:54.777 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-05-01 11:29:54.777 [info] [Error - 11:29:54 AM] The Black Formatter server crashed 5 times in the last 3 minutes. The server will not be restarted. See the output for more information.
2023-05-01 11:29:54.777 [info] [Error - 11:29:54 AM] Black Formatter client: couldn't create connection to server.
2023-05-01 11:29:54.777 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-05-01 11:29:54.777 [info] [Error - 11:29:54 AM] Restarting server failed
2023-05-01 11:29:54.777 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-05-01 11:53:08.494 [info] Name: Black Formatter
2023-05-01 11:53:08.494 [info] Module: black
2023-05-01 11:53:08.494 [info] Python extension loading
2023-05-01 11:53:08.494 [info] Waiting for interpreter from python extension.
2023-05-01 11:53:08.494 [info] Python extension loaded
2023-05-01 11:53:08.494 [info] Server run command: /bin/python /home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/tool/lsp_server.py
2023-05-01 11:53:08.494 [info] Server: Start requested.
2023-05-01 11:53:08.573 [info] Traceback (most recent call last):
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/tool/lsp_server.py", line 40, in <module>
    import lsprotocol.types as lsp
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/lsprotocol/types.py", line 14, in <module>

2023-05-01 11:53:08.573 [info]     import attrs
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/attrs/__init__.py", line 3, in <module>
    from attr import (
ImportError: cannot import name 'AttrsInstance' from 'attr' (/usr/lib/python3/dist-packages/attr/__init__.py)

2023-05-01 11:53:08.584 [info] [Error - 11:53:08 AM] Server initialization failed.
2023-05-01 11:53:08.584 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-05-01 11:53:08.584 [info] [Info  - 11:53:08 AM] Connection to server got closed. Server will restart.
2023-05-01 11:53:08.584 [info] true
2023-05-01 11:53:08.584 [info] [Error - 11:53:08 AM] Black Formatter client: couldn't create connection to server.
2023-05-01 11:53:08.584 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-05-01 11:53:08.682 [info] Traceback (most recent call last):
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/tool/lsp_server.py", line 40, in <module>
    import lsprotocol.types as lsp
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/lsprotocol/types.py", line 14, in <module>
    import attrs
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/attrs/__init__.py", line 3, in <module>

2023-05-01 11:53:08.683 [info]     from attr import (
ImportError: cannot import name 'AttrsInstance' from 'attr' (/usr/lib/python3/dist-packages/attr/__init__.py)

2023-05-01 11:53:08.694 [info] [Error - 11:53:08 AM] Server initialization failed.
2023-05-01 11:53:08.694 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-05-01 11:53:08.694 [info] [Info  - 11:53:08 AM] Connection to server got closed. Server will restart.
2023-05-01 11:53:08.694 [info] true
2023-05-01 11:53:08.694 [info] [Error - 11:53:08 AM] Black Formatter client: couldn't create connection to server.
2023-05-01 11:53:08.694 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-05-01 11:53:08.695 [error] Server: Start failed: Error: Pending response rejected since connection got disposed
2023-05-01 11:53:08.786 [info] Traceback (most recent call last):
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/tool/lsp_server.py", line 40, in <module>
    import lsprotocol.types as lsp
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/lsprotocol/types.py", line 14, in <module>
    import attrs
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/attrs/__init__.py", line 3, in <module>
    from attr import (
ImportError: cannot import name 'AttrsInstance' from 'attr' (/usr/lib/python3/dist-packages/attr/__init__.py)

2023-05-01 11:53:08.796 [info] [Error - 11:53:08 AM] Server initialization failed.
2023-05-01 11:53:08.796 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-05-01 11:53:08.796 [info] [Info  - 11:53:08 AM] Connection to server got closed. Server will restart.
2023-05-01 11:53:08.796 [info] true
2023-05-01 11:53:08.797 [info] [Error - 11:53:08 AM] Black Formatter client: couldn't create connection to server.
2023-05-01 11:53:08.797 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-05-01 11:53:08.797 [info] [Error - 11:53:08 AM] Restarting server failed
2023-05-01 11:53:08.797 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-05-01 11:53:08.878 [info] Traceback (most recent call last):
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/tool/lsp_server.py", line 40, in <module>
    import lsprotocol.types as lsp
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/lsprotocol/types.py", line 14, in <module>
    import attrs
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/attrs/__init__.py", line 3, in <module>
    from attr import (

2023-05-01 11:53:08.878 [info] ImportError: cannot import name 'AttrsInstance' from 'attr' (/usr/lib/python3/dist-packages/attr/__init__.py)

2023-05-01 11:53:08.888 [info] [Error - 11:53:08 AM] Server initialization failed.
2023-05-01 11:53:08.888 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-05-01 11:53:08.888 [info] [Info  - 11:53:08 AM] Connection to server got closed. Server will restart.
2023-05-01 11:53:08.888 [info] true
2023-05-01 11:53:08.888 [info] [Error - 11:53:08 AM] Black Formatter client: couldn't create connection to server.
2023-05-01 11:53:08.888 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-05-01 11:53:08.888 [info] [Error - 11:53:08 AM] Restarting server failed
2023-05-01 11:53:08.888 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-05-01 11:53:08.971 [info] Traceback (most recent call last):
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/tool/lsp_server.py", line 40, in <module>
    import lsprotocol.types as lsp
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/lsprotocol/types.py", line 14, in <module>
    import attrs
  File "/home/milner/.vscode/extensions/ms-python.black-formatter-2023.2.0/bundled/libs/attrs/__init__.py", line 3, in <module>

2023-05-01 11:53:08.971 [info]     from attr import (
ImportError: cannot import name 'AttrsInstance' from 'attr' (/usr/lib/python3/dist-packages/attr/__init__.py)

2023-05-01 11:53:08.981 [info] [Error - 11:53:08 AM] Server initialization failed.
2023-05-01 11:53:08.981 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-05-01 11:53:08.981 [info] [Error - 11:53:08 AM] The Black Formatter server crashed 5 times in the last 3 minutes. The server will not be restarted. See the output for more information.
2023-05-01 11:53:08.982 [info] [Error - 11:53:08 AM] Black Formatter client: couldn't create connection to server.
2023-05-01 11:53:08.982 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097
2023-05-01 11:53:08.982 [info] [Error - 11:53:08 AM] Restarting server failed
2023-05-01 11:53:08.982 [info]   Message: Pending response rejected since connection got disposed
  Code: -32097

@carmiac Your issue is different from the one posted here. In your case it looks like the attrs version you have in the environment is not supported. Try setting black-formatter.importStrategy to useBundled.

Oh, that fixed it, thanks!

@karthiknadig what is the right way to pin a specific black version then?
is there a way around the attrs issue above, or can one pin the bundled black version?


is this package actively maintained?

Going through issues and PRs it seems that there is no one maintaining this package. Is it sill active?

@assistunion Any chance we can hand this off to a developer interested in maintaining the repo? It would be great to let the community to continue to benefit from this npm pacakge.

hey @Artazor - anything we can do to help?

If anyone wants to maintain this package - I’m open for discussion. Btw, looks like it should be rewritten using async-iterator style or at least to have async reactions to selectors

I'm interested in contributing as well @assistunion is this a possibility?

One of y'all short fork it 🙂

Hi, over many years I see that this functionality is still needed and interesting for developers. Actually I think that this  particular package will not be updated. However I'm considering creating a very similar project that will reuse the same CSS like selectors (and all the mechanics of NFA), yet it will be based on Asynchronous Generators so you can basically enumerate all nodes you need via for await. Probably it will be publisched under not under @assistunion, it will be published under @blockvis. Will post an update here when I'll have more info about the timeframe.
Meanwhile it would be great to hear any input ideas that I can incorporate in future design.


DESC Science Requirements Document: The Update

DESC Science Requirements Document: The Update

Decide what to include in the DESC Science Requirements Document (SRD) update and make a plan for execution.
Location and Zoom Links
Wednesday 11am
Physical room: 2246 Randall
Zoom room: DESC 5: 949 2579 9346
Wednesday afternoon and Thursday morning
Physical room: 3246 Randall
Zoom room: DESC 2: 973 3462 5376
Contacts: Heather Prince and Eric Gawiser
Day/Time: Mon, Tues at 1-4pm; Weds 11-12 and 1-3; Thursday 10am-12pm
Main communication channel: #desc-requirements
GitHub repo: https://github.com/LSSTDESC/Requirements
DESC SRD v1:  https://arxiv.org/abs/1809.01669
Schedule
Monday 1-4pm:
overview
Tuesday 1-4pm:
1-2 Supernovae & Strong Lensing
2-3 Augur
3-4 Firecrown & supernovae
Wednesday 11-12 and 1-3:
11am-12pm Firecrown
1-2pm: clusters and covariances
2-3 or 3:30pm: 3x2pt
Thursday 10am-12pm:
wrap up and make a plan
Goals and deliverable
Our goals are

to obtain input from across the collaboration on the DESC SRD update,
decide what should be included in version 2,
evaluate what systematics to prioritize for the updated forecasts and error budgeting for each dark energy probe, and
determine if further code development is needed to enable these forecasts.

Deliverables:

A list of prioritized updates to the DESC SRD, together with a plan and timeline for completing them.

Resources and skills needed
Please join us if you can offer any of the following:

interest in the cosmological constraints we will reach with DESC
understanding of the analysis methods and systematics for one of the dark energy probes: 3x2pt (weak lensing & galaxy clustering), galaxy clusters, supernovae, and strong lensing
interest in/familiarity with DESC codes for forecasting, covariances, likelihoods etc

Detailed description
In-progress sprint week notes: https://docs.google.com/presentation/d/1w_fl7FCipzrdbiJlQHrLpUF-1B3Lx8RAfjZhO_TCSas/edit?usp=sharing

times above are in (EST)

I'll be happy to join tomorrow morning's session via Zoom.


Cannot activate this extension

I had this extension working very nicely! Awesome extension, thank you. But after a recent update, it stopped working. I have removed it, uninstalled it, you name it.
So with it uninstalled, I go to the SCM page, and click the More button. It only gives me the option to install more SCM providers. I click that. It shows me several available extensions, including the vscode-perforce one. I click Install.  I click Reload. Now if I go to the SCM page and click the More button,  it again ONLY shows me the option to install additional SCM providers. And the list it gives me when I do that, again shows vscode/perforce, but shows it as being installed. It shows that it is up to date, as is my vscode.  If I click on its settings buttons, it seems to be enabled, as it only shows options to disable it.
I restart vscode, and go to the SCM page, and it says "There are no source controls active". If I go to the list of installed extensions, it shows vscode-perforce as isntalled and enabled. Nothing in the log or problems tab.
What gives? It seems to be installed, yet vscode acts as if it is not.
It was working fine on the folder in question, the same folder I have now, and I have not changed any settings since then.
Using vscode 1.16.1, 64 bit. on Windows.
Attempting to use version 2.2.1 of the extension.
Please help! Is there some sort of log file or troubleshooting guide to tell you why this extension is not working?

We are reworking the way the extension will activate, in order to support multiple workspaces.
Can you try to set the following in your global settings, reload your workspace, and see if you can activate the Perforce Log in the command palette ?
"perforce.activationMode": "always"

Hi, with that option added, your extension seems to load and work now.  Thanks. BTW: I did have a folder open, the same one that automatically reopens when I start vscode.

How is your p4 settings configured? Are you using global settings pointing to a default depot? Are you using env vars or .p4config files?

In the folder I opened, I have a .p4config file containing:
P4CLIENT=MCH3_Client3
(This is because the plugin picks the wrong client otherwise, the machine has many clients)
In my User settings I have:
"perforce.activationMode": "always"
There are no P4 relevant environment variables. It must be getting the rest of the settings from wherever P4V saves them.
I do not set P4CLIENT in the vscode user settings or environment, as there are may clients, and the right one depends on the folder. So it is convenient that a .P4CONFIG file in the work folder seems to work now.
Anything else I can do to help or test please let me know.
Thanks.

Ok, the problem may come from the fact that you have multiple .p4config files in the same workspace, even if they are in different sub-folders.
I'll investigate why it break the autodetect mode. Thanks for the info!

Nope, there is one and only one .P4CONFIG file in the workspace directory. and none in any sub directories.  The other client directories are elsewhere on the machine.

Hm, it's curious then...
If there is no sensitive information, could you copy in the output of
Perforce: Display client/server information
And maybe also, run p4.exe set from VSCode Terminal?

The funny thing is, now that I have .the .P4CONFIG and it has loaded, I can remove the perforce.activationMode from my workspace and user settings, and the extension still loads and works fine. (When it was not working I did not have a .P4CONFIG but rather set the client in the user preference settings). If I remove the .P4CONFIG file, then it reverts back to "There are no source controls active". If I bring it back, it starts to work again. If I remove the .P4CONFIG file and set the client in the workspace preference settings instead, then the extension stops working again.
So I am guessing the extension works if it can find valid settings, which may require a .P4CONFIG file. The settings in the workspace preference (perforce.client) does not seem to work anymore. But that is fine for me.
The client server information is (edited some names slightly to remove confidential info):
p4.exe -c BXXXXXXX_Client3 -d e:/Perforce/Client3/main/xxxx-sim/ info
User name: vxxxxxx
Client name: BXXXXXX_Client3
Client host: BXXXXX4
Client root: e:\Perforce\Client3
Current directory: e:/Perforce/Client3/main/xxxxx-sim/
Peer address: <IP_ADDRESS>:62292
Client address: <IP_ADDRESS>
Server address: Axxxxx1.xxxxx.com:1666
Server root: d:\Perforce
Server date: 2017/09/25 10:53:01 -0500 Central Daylight Time
Server uptime: 813:22:09
Server version: P4D/NTX64/2017.1/1545029 (2017/08/16)
Proxy address: Cxxxx1.xxxxx.com:1666
Proxy version: P4P/NTX64/2017.1/1545029 (2017/08/16)
Server license: xxxxxxx  xxx users (support ends 2018/09/13)
Server license-ip: <IP_ADDRESS>:1666
Case Handling: insensitive
From a command shell, p4.exe set reports:
P4EDITOR=xxxxxxx (Set)
P4PORT=Cxxxxx:16666 (set)
P4USER=vXXXXXX
P4_cxxxxxx:1666_CHARSET=none (set)

I am guessing that setting the perforce.client in the user settings, requires the activationMode always setting to work. But if you instead you set the client via .P4CLIENT, then the activationMode is not required.

Ok, then PR #99 is likely to fix this issue. Just a few more test and I'll push a new version of the extension.

Yes, it is just a typo. BTW: Thank you for this extension it is awesome, I appreciate how much work it is! You are doing it just for the love of it?

To be honest, maintaining the project is a bit more work than I initially thought.
But since some people are using it on a daily basis, it might just worth it :)

Sadly, if you exit vscode and wait some time before loading it, then the extension start using the wrong client, instead of the one set in .P4CONFIG. So I am back to having perforce.client in the user workspace settings.


Weave multicast

Is there a quick way to see if multicast works across (latest) weave?
I did use https://github.com/neilellis/weave_multicast_tutorial/blob/master/blog_post.md in the past, but couldn't get it to run anymore.

I think there is a problem with the run.sh shell script in that demo container.  If I bypass it, and start the mcsend and mcreceive programs directly, they work fine across the weave network.
E.g., on one host
docker $(weave config) run -it --rm neilellis/weave-multicast-tutorial /mcsend <IP_ADDRESS> 1234

and on the other
docker $(weave config) run -it --rm neilellis/weave-multicast-tutorial /mcreceive <IP_ADDRESS> 1234


cargo info doesn't allow to specify output-format

Problem
it'll be good to support output-format
Proposed Solution
No response
Notes
No response

What other output format would you want and what is the use care for it?

@epage output format allow us to integrate other tools. I always want to be productive so I have the following alias:
function cbrowse
  if test -n "$argv[1]"
    open -u (cargo info $argv[1] | grep repository | awk '{print $2}')
  end
end

function cclone
  if test -n "$argv[1]"
    git clone (cargo info $argv[1] | grep repository | awk '{print $2}')
  end
end

in the future I may come up with other scripts for handling things like features

Is there reason you want to use this over cargo metatdata? That is generally our answer for programmatic use. This is a UX focused command that we can change the output on as needed.

@epage cargo metadata is for local crates, cargo info is for crates on crates.io

Would your needs be covered by #11034?


SwitchBot Blind tilt

Hello,
does the new SwitchBot Blind tilt also work with this Project?

Not currently. I've tried to hack it in on this issue but got stuck and over my head with my programming abilities. If someone more capable were able to take my findings and go that last mile so to speak it would work. I feel like it's something simple I'm missing but have no idea what it could be but for the time being it's stalled.

Plus 1 for this!
I bought 3 blind tilts thinking they would work but now I need to return them. :-(

If you use Home Assistant the native integration works just fine over Bluetooth. It's actually one of the only reasons I now run HA along side OpenHAB to get that control. I've yet to figure out how to surface the blind controlled by HA into OH effectively though so that's annoying

Yea I use HA. My NUC is my office closet and I bought a Bluetooth adapter, a USB hub, and a 6ft extension cable to see if this will work.
I was SOOOO hoping to use your app. I even have the ESP32 setup…then I realized no blind tilt support.
What skill set would be required to add this functionality?

Really it's just the ability to understand the C (I think) this is written in and look at the python the HA integration uses for the blind Tilt and be able to translate it. You can probably get away with duplicating most of the code sections here for curtain, it's just the parts where the it decodes the bits for status and stuff that are different. I got part of the way there in the issue I linked above but couldn't quite get it to work. It's probably just a few lines of code that need to change but try as I might I just couldn't get it to work


Update linera project new so that the "Hello, Linera" page doesn't need the git repo

Using linera project new, it should be possible to run the entire "Hello, Linera" page without checking out the git repository.
https://linera.dev/getting_started/hello_linera.html

It works!


Update README.md

Add the extra step after installation via HACS to navigate to Devices & Services, and add the integration

Thanks!


Add CommonResourceHelper.psm1 module and update to use it

The xPSDesiredStateConfiguration includes a CommonResourceHelper.psm1 that includes several common functions.
xNetworking has quite a lot of replicated code that is contained in the CommonResourceHelper.psm1 file. So there would be some benefit to changing xNetworking to use these patterns (including making the move to HQRM easier).

To keep this issue updated the module was added but most resources do not use it at this time.

@tysonjhayes - I'm working on this one now.


First task-assignment  issue

Project link
https://github.com/John-Kibirige/tv-maze/projects/1
Team
We are two people on this team that is @melashu  and @John-Kibirige

Required Changes :recycle:

Hey @John-Kibirige :wave:
Highlights :1st_place_medal:
:heavy_check_mark: Documented work in a professional way
:heavy_check_mark: Using GitHub Issues
:heavy_check_mark: Descriptive Issue Title
Good job on implementing some of the requirements, there are some issues that you still need to work on to go to the next project but you are almost there! :blush:
Mandatory Changes

[ ] Please assign these cards as well to someone. You can assign these cards to more than one person :blush:

Optional Suggestions
Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you to take them into account as they can make your code better.
Cheers and Happy coding :clap: :clap: :clap:
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.
Please, remember to tag me @HAMMAS-SALEEM in your question so I can receive the notification. Otherwise reach out to me on slack which is more fast. You can reach out to me on slack by searching my name in full-time-students channel :+1:
Please, do not open a new Pull Request for re-reviews. You should use the same Pull Request submitted for the first review, either valid or invalid unless it is requested otherwise.

As described in the Code reviews limits policy you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.

Status: APPROVED 🟢
Hi @John-Kibirige & @melashu ✋
Your project is complete!  There is nothing else to say other than... it's time to merge it: ship it:
Congratulations! :tada: :clap: :clap: :100:
Highlights!

Descriptive Issue title ✔
Great use of Github features ✔

Optional suggestions
Every comment with the [OPTIONAL] prefix is not crucial enough to stop the approval of this PR. However, I strongly recommend you consider them as they can improve your code.
Cheers and Happy coding!:clap::clap::clap:
Feel free to leave any questions or comments in the PR thread if something is not 100% clear.

_As described in the Code reviews limits policy  you have a limited number of reviews per project (check the exact number in your Dashboard). If you think that the code review was not fair, you can request a second opinion using this form.


Trigger camera via software

Hello!
Is it possible to trigger the camera via software sing this library? I know it can be triggert with a digital signal, but my pc has no output to trigger it, and I would need the acquisition to start exactly when i tell it to.
Thank you!
best regards
Igor

I am at this point now:

from builtins import *
import o3d3xx
import sys
import time
import numpy as np
import cv2

imageWidth = 176
imageHeight = 132

#imageWidth = 352
#imageHeight = 264

class GrabO3D300():
	def __init__(self,data):
		self.data = data
		self.Distance = np.zeros((imageHeight,imageWidth))

	def readNextFrame(self):
		result = self.data.readNextFrame()
		self.Distance = np.frombuffer(result['distance_image'], dtype='uint16')
		self.Distance = self.Distance.reshape(imageHeight, imageWidth)
		self.illuTemp = 20.0

if len(sys.argv) > 1:
	address=sys.argv[1]
else:
	address='<IP_ADDRESS>'

camData = o3d3xx.FormatClient(address, 50010,
o3d3xx.PCICFormat.blobs("distance_image"))
pcic = o3d3xx.PCICV3Client(address, 50010)

grabber = GrabO3D300(camData)

imDistance = np.random.rand(imageHeight,imageWidth)

while True:
	result = camData.readNextFrame()
	pcic.sendCommand("t")
	grabber.readNextFrame()
	dist_max = float(max(np.max(grabber.Distance), 1))
	imDistance = grabber.Distance / 1000
	cv2.imshow('dist', imDistance)
	cv2.waitKey()

But it does not work. nothing happens. The trigger will later be sent on a specific event, for the time being i would be happy to send the trigger and retrieve the image. Could somebody please help me on this? any help is greatly appreciated...
best regards
Igor


Include doi as a query parameter in the Literature search

Hello!
I want to add specific DOIs to the literature search. I saw that doi is a query parameter for the Literature API. However, I cannot make it work.
As an example, here's a doi = https://doi.org/10.1038/s41598-020-79074-8.
When I explore the literature search in gbif.org, I can see that the call is:
https://www.gbif.org/resource/search?contentType=literature&doi=10.1038~2Fs41598-020-79074-8
It seems that the / is changed to ~2F Not sure if this is related. It could also be that I'm not coding it right :)
I tried including the plain text, and then here I was trying a scape character, but also didn't work:
https://github.com/gbif/hp-biodiversidata/blob/master/_includes/js/config.js#L68
Thanks!

It looks like you are trying to add 10.15468\\/dl.klwehw. But that looks to me like a gbif download doi.
The DOI filter as you see it on GBIF.org works on the doi's of the papers.
So it will not do anything.
Secondly I have to enable search by DOI, I haven't done so. But I will now.
Thanks

Sorry Morten, the doi "10.15468\/dl.klwehw" is not the one I was using. That was just a test after many other tests to make it work. I was trying 10.1038/s41598-020-79074-8 and failed. But it's probably related to the fact that the search by doi is not enabled.

I have changed the predicate to a nested type.
https://github.com/gbif/hp-biodiversidata/commit/5061c217aac12327b2f586774bbf27de514b9588
As that worked here and now
UPDATE: i have now updated the backend to allow for simpler querying on nested objects in ElasticSearch
in this commit https://github.com/gbif/gbif-web/commit/f2a64ab5db5b3f13978a0dabf5e87a0c4b4449f6
So I have changed your config back to
https://github.com/gbif/hp-biodiversidata/commit/b070d8ab190fdce9822522eb83b88f7acf6b8200

Dear Morten, any reason why this doesn't work:
https://api.gbif.org/v1/literature/search?doi=10.3897/BDJ.7.e36226
I'm trying to use this DOI in the literature search (and a bunch of others), but it's not retrieving the paper. Is it because it's a data paper?
Here's the code: https://github.com/gbif/hp-biodiversidata/blob/511cfdff5b90f1703277ff563727049c0d005b9e/_includes/js/config.js#L84
Thanks!

This looks like a mistake - it appears to be case sensitive.
I'll let @MortenHofft determine where this should be fixed but perhaps this is enough for you to work around this @bienflorencia.
https://api.gbif.org/v1/literature/search?doi=10.3897/bdj.7.e36226 works
https://api.gbif.org/v1/literature/search?doi=10.3897/BDJ.7.e36226 does not


Remove redundant project reference in Sdk.Generator.Tests

Sdk.Generator.Tests is referencing Microsoft.Azure.Functions.Worker.Extensions.Http twice, one as a package reference (which is a transitive depedency) and second as a project reference.

[x] My changes do not require documentation changes

[ ] Otherwise: Documentation issue linked to PR

[] My changes should not be added to the release notes for the next release

[ ] Otherwise: I've added my notes to release_notes.md

[x] My changes do not need to be backported to a previous version

[ ] Otherwise: Backport tracked by issue/PR #issue_or_pr

[ ] I have added all required tests (Unit tests, E2E tests)

But I am curious about the references to sample projects here and how this package + project reference was introduced.

Would also like to better understand what changed here, as this has been in place for a while.


[Docs] Add descriptions of load generators in Meshery Performance Management page

Current State:
The Performance Management page does not have a description of the three supported load generators:

fortio
wrk2
Nighthawk

Desired State:
This page should describe the fact that Meshery supports these load generators and have a short description of what each load generator is. See the service mesh landscape for some of these details and performance management design documents.

Contributor Resources

Meshery documentation site
Meshery documentation source
Instructions for contributing to documentation

I don't see where to get the details of the three supported load generators

I would love to work on this, I would need a community member guidance too.

Hi @Annysah sure you can go ahead with it, do go over to the #first-timers workspace and ask questions.😊

Hi @Annysah situation report please, still up for this?


test: fix upgrade suite

Fixes #N/A
Description
How was this change tested?
Does this change impact docs?

[ ] Yes, PR includes docs updates
[ ] Yes, issue opened: #
[x] No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

/karpenter snapshot

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.01%) to 78.765%

Totals

Change from base Build<PHONE_NUMBER>:
0.01%

Covered Lines:
5612

Relevant Lines:
7125

💛  - Coveralls

/karpenter snapshot