NPM pulls corrupted packages from Verdaccio instance (its back)

Same behavior as reported in ticket #756 but those fixes dont fix the issue.  I am doing this with a fairly generic Angular 6 cli built project.  Error output from a manually issued npm install --verbose:
npm timing audit body Completed in 94ms
npm WARN tarball tarball data for<EMAIL_ADDRESS><2.8 (sha512-p5TCYZDAO0m4G344hD+wx/LATebLWZNkkh2asWUFqSsD2OrDNhbAHuSjobrmsUmdzjJjEeZVU9g1h3O6vpstnw==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-Gr4p6nFNaoufRIY4NMdpQRNmgxVIGMs4Fcu/ujdYk3nAZqk7supzBE9idmvfZIlH/Cuj//dvi+019qEue9lV0w==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-IIU5cN1mR5J3z9jjdESJbnxikTrEz3lzAw/D0Tf45jHpBp55nY31UkUvmVHoffCfKHTqJs3fCLPDxknQTTFegQ==) seems to be corrupted. Trying one more time.
npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-FPIb2j3zfoBwb6vo/u0gQeu70h8InGlSisBr3xMACs/35/pwB6kbQR+JQiUr0D7k6QApg7AuMkvq8aFNelg0aw==) seems to be corrupted. Trying one more time.

Note I had this behavior with Verdaccio 3, did one of the recommendations in the #756 ticket and restarted my Docker Verdaccio container which upgraded it to Verdaccio 4 (thanks for all of the help you provided in #1324 to get that working) and I now have the exact same behavior with Verdaccio 4.01.
I have purged the node_modules and package-lock.json (and as I just rebuilt my packages tree in the new Docker instance I know those are clean).  I have done the npm cache purge commands listed in 756 and I still get the same behavior.
Odd notes - this only happens on my build server, even when it is setup to wipe the directory and clean build - on my development vm the npm install works fine, so it seems to be something related to that machine but I am not sure what it could be.  In both cases I am currently manually running the commands under my user account, so it is not like they are running under different security.
On machine that works
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>on machine with issue
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>Any ideas/suggestions on where to look for this?  I guess I can try updating the working machine to npm 6.8 to see if it then stops working.......
Update - well, going to 6.8.0 on the working machine didnt break it, and going to 6.9.0 on the broken machine didnt fix it so I am open to suggestions on things to try.
Update 2 - well, I did a npm cache verify and then an npm update still without success, but the end of the log from the Verdaccio server is interesting:
http <-- 200, user: null(<IP_ADDRESS>), req: 'GET /has-values', bytes: 0/4129
http --> 304, req: 'GET https://registry.npmjs.org/copy-descriptor' (streaming)
http --> 304, req: 'GET https://registry.npmjs.org/copy-descriptor', bytes: 0/0
http <-- 200, user: null(<IP_ADDRESS>), req: 'GET /copy-descriptor', bytes: 0/2400
http <-- 200, user: null(<IP_ADDRESS>), req: 'POST /-/npm/v1/security/audits/quick', bytes: 74646/1172
http <-- 200, user: null(<IP_ADDRESS>), req: 'GET /typescript/-/typescript-2.7.2.tgz', bytes: 0/6076378
http <-- 200, user: null(<IP_ADDRESS>), req: 'GET /typescript/-/typescript-2.9.2.tgz', bytes: 0/6372426
http <-- 200, user: null(<IP_ADDRESS>), req: 'GET /typescript/-/typescript-2.8.4.tgz', bytes: 0/6034070
http <-- 200, user: null(<IP_ADDRESS>), req: 'GET<EMAIL_ADDRESS>bytes: 0/5429592
http <-- 200, user: null(<IP_ADDRESS>), req: 'GET<EMAIL_ADDRESS>bytes: 0/5429592
http <-- 200, user: null(<IP_ADDRESS>), req: 'GET /typescript/-/typescript-2.9.2.tgz', bytes: 0/6372426
http <-- 200, user: null(<IP_ADDRESS>), req: 'GET /typescript/-/typescript-2.7.2.tgz', bytes: 0/6076378
http <-- 200, user: null(<IP_ADDRESS>), req: 'GET /performance-now/-/performance-now-2.1.0.tgz', bytes: 0/4564
http <-- 200, user: null(<IP_ADDRESS>), req: 'GET /postcss/-/postcss-6.0.23.tgz', bytes: 0/183627
http <-- 200, user: null(<IP_ADDRESS>), req: 'GET /uri-js/-/uri-js-3.0.2.tgz', bytes: 0/107604
http <-- 200, user: null(<IP_ADDRESS>), req: 'GET /selenium-webdriver/-/selenium-webdriver-3.6.0.tgz', bytes: 0/776120
http <-- 200, user: null(<IP_ADDRESS>), req: 'GET /resolve/-/resolve-1.11.0.tgz', bytes: 0/33459
http <-- 200, user: null(<IP_ADDRESS>), req: 'GET /less/-/less-3.9.0.tgz', bytes: 0/671112
http <-- 200, user: null(<IP_ADDRESS>), req: 'GET /typescript/-/typescript-2.8.4.tgz', bytes: 0/6034070
http <-- 200, user: null(<IP_ADDRESS>), req: 'GET /less/-/less-3.9.0.tgz', bytes: 0/671112
as mentioned in the other ticket, the problem file seem to be larger ones.
Update 3 - I tried to disable to the caching of npmjs packages to no effect (even after doing a npm cache verify on the machine in question before redoing the npm install).  Is this the right spot to put in the cache false setting?
`# a list of other known repositories we can talk to
uplinks:
  npmjs:
    url: https://registry.npmjs.org/
    cache: false

`

hi @johnruck ,

Is this the right spot to put in the cache false setting?

cache: false is optional, but you pay the penalty to do not have tarballs cached.
I wonder which value do you have for max_body_size https://verdaccio.org/docs/en/configuration#max-body-size.
⚠  Furthermore, share the config file also helps to give us more context.

well, going to 6.8.0 on the working machine didnt break it, and going to 6.9.0 on the broken machine didnt fix it so I am open to suggestions on things to try.

Sometimes try with either yarn or pnpm helps to spot the issue is on the client side.

I am doing this with a fairly generic Angular 6 cli built project. Error output from a manually issued npm install --verbose:

Could you describe the steps? I'd like to try locally.

@juanpicado - I am willing to try the max_body_size option (where does it go in the configuration file - the web page you referenced doesnt really say or show it in context in a configuration), although if I am interpreting the output from the verdaccio properly the files seem to be within that constraint (6M in size)
For reference,. my current config.yaml was posted in #1324 earlier today, just missing the cache: false that I have since re-added that I referenced above.
I would love to be able to explain how to reproduce it, but the exact same code is working on one machine and not on another with no obvious differences between the two machines.  The machine that is failing happens to be a TeamCity agent machine, but the failures happen even when I manually invoke npm in the same directory (it is how I am debugging this issue now without involving TC).

pnpm output -
H:\TC1-DataDirectory\ff1c88d354221106\SystemManagementServer\ClientApp>pnpm install
 WARN  deprecated<EMAIL_ADDRESS>Switch to @angular/common/http - see https://angular.io/guide/http
Downloading<EMAIL_ADDRESS>5.43 MB/5.43 MB, done
Downloading tohsaka.silverblazegaming.com+4873/typescript/2.8.4: 6.03 MB/6.03 MB, done
Downloading tohsaka.silverblazegaming.com+4873/typescript/2.9.2: 6.37 MB/6.37 MB, done
 WARN  @angular-devkit/build-angular<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ~2.5.0 || ~2.6.0 || ~2.7.0 but version 2.8.4 was installed.m+4873/typescript/2.7.2: 6.05 MB/6.08 MB
Packages: +997
++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++
 WARN  Fetching tohsaka.silverblazegaming.com+4873/typescript/2.7.2 failed!
 ERROR  Actual size (6052937) of tarball (http://tohsaka.silverblazegaming.com:4873/typescript/-/typescript-2.7.2.tgz) did not match the one specified in 'Content-Length' header (6076378)99 MB/6.08 MB

Seems like you have internet connection issues.
Try running the same command again.
If that doesn't help, try one of the following:

- Set a bigger value for the `fetch-retries` config.
    To check the current value of `fetch-retries`, run `pnpm get fetch-retries`.
    To set a new value, run `pnpm set fetch-retries <number>`.

- Set `network-concurrency` to 1.
    This change will slow down installation times, so it is recommended to
    delete the config once the internet connection is good again: `pnpm config delete network-concurrency`

NOTE: You may also override configs via flags.
For instance, `pnpm install --fetch-retries 5 --network-concurrency 1`
Resolving: total 999, reused 0, downloaded 996
Downloading tohsaka.silverblazegaming.com+4873/typescript/2.7.2: 5.99 MB/6.08 MB
Error: Actual size (6052937) of tarball (http://tohsaka.silverblazegaming.com:4873/typescript/-/typescript-2.7.2.tgz) did not match the one specified in 'Content-Length' header (6076378)
    at WriteStream.opts.stream.on (C:\Users\john\AppData\Roaming\npm\node_modules\pnpm\lib\node_modules\@pnpm\tarball-fetcher\lib\createDownloader.js:162:29)
    at WriteStream.emit (events.js:182:13)
    at lazyFs.close (internal/fs/streams.js:208:14)
    at C:\Users\john\AppData\Roaming\npm\node_modules\pnpm\lib\node_modules\graceful-fs\graceful-fs.js:45:10
    at FSReqWrap.oncomplete (fs.js:141:20)
Error: Actual size (6052937) of tarball (http://tohsaka.silverblazegaming.com:4873/typescript/-/typescript-2.7.2.tgz) did not match the one specified in 'Content-Length' header (6076378)
    at WriteStream.opts.stream.on (C:\Users\john\AppData\Roaming\npm\node_modules\pnpm\lib\node_modules\@pnpm\tarball-fetcher\lib\createDownloader.js:162:29)
    at WriteStream.emit (events.js:182:13)
    at lazyFs.close (internal/fs/streams.js:208:14)
    at C:\Users\john\AppData\Roaming\npm\node_modules\pnpm\lib\node_modules\graceful-fs\graceful-fs.js:45:10
    at FSReqWrap.oncomplete (fs.js:141:20)
Error: Actual size (6052937) of tarball (http://tohsaka.silverblazegaming.com:4873/typescript/-/typescript-2.7.2.tgz) did not match the one specified in 'Content-Length' header (6076378)
    at WriteStream.opts.stream.on (C:\Users\john\AppData\Roaming\npm\node_modules\pnpm\lib\node_modules\@pnpm\tarball-fetcher\lib\createDownloader.js:162:29)
    at WriteStream.emit (events.js:182:13)
    at lazyFs.close (internal/fs/streams.js:208:14)
    at C:\Users\john\AppData\Roaming\npm\node_modules\pnpm\lib\node_modules\graceful-fs\graceful-fs.js:45:10
    at FSReqWrap.oncomplete (fs.js:141:20)
Error: Actual size (6052937) of tarball (http://tohsaka.silverblazegaming.com:4873/typescript/-/typescript-2.7.2.tgz) did not match the one specified in 'Content-Length' header (6076378)
    at WriteStream.opts.stream.on (C:\Users\john\AppData\Roaming\npm\node_modules\pnpm\lib\node_modules\@pnpm\tarball-fetcher\lib\createDownloader.js:162:29)
    at WriteStream.emit (events.js:182:13)
    at lazyFs.close (internal/fs/streams.js:208:14)
    at C:\Users\john\AppData\Roaming\npm\node_modules\pnpm\lib\node_modules\graceful-fs\graceful-fs.js:45:10
    at FSReqWrap.oncomplete (fs.js:141:20)

Make any sense to you?

ok, I managed to do some more testing in a separate new directory and I was able to get it to work with the cache turned off with both pnpm and npm.  I then turned on caching to see if it would break again (and I got the 4.02 docker image) - it broke again once I re-enabled the caching.

Canyou check the size of the actual tarball on disk? Maybe it is an issue with some compression or additional metadata in it.

Sorry for taking this long to respond, I am not entirely sure how to interpret these results - in looking at the file in the docker storage zone (for typescript 2.9.2.tgz)
john@tohsaka:~$ docker run -it --rm -v verdaccio-storage:/verdaccio/storage -v /home/john/verdaccio/storage:/backup ubuntu bash -c "ls -al /verdaccio/storage/typescript/typescript-2.9.2.tgz"
-rw-r--r-- 1 10001 65533 6372426 Jun 12 18:22 /verdaccio/storage/typescript/typescript-2.9.2.tgz
john@tohsaka:~$ docker run -it --rm -v verdaccio-storage:/verdaccio/storage -v /home/john/verdaccio/storage:/backup ubuntu bash -c "sha512sum /verdaccio/storage/typescript/typescript-2.9.2.tgz"
1abe29ea714d6a8b9f44863834c76941136683154818cb3815cbbfba37589379c066a93bb2ea73044f62766bdf648947fc2ba3fff76f8bed35f6a12e7bd955d3  /verdaccio/storage/typescript/typescript-2.9.2.tgz

while on the machine where it is failing to download -
npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-Gr4p6nFNaoufRIY4NMdpQRNmgxVIGMs4Fcu/ujdYk3nAZqk7supzBE9idmvfZIlH/Cuj//dvi+019qEue9lV0w==) seems to be corrupted. Trying one more time.
I am not sure if those two checksums should match (ie - whether the npm checksum reported should be for the whole file or a segment of it)
The file size does match what verdaccio is reporting the filesize to be (if am reading the diagnostics right):
 http <-- 200, user: null(<IP_ADDRESS>), req: 'GET /typescript/-/typescript-2.7.2.tgz', bytes: 0/6076378
 http <-- 200, user: null(<IP_ADDRESS>), req: 'GET /typescript/-/typescript-2.9.2.tgz', bytes: 0/6372426
 http <-- 200, user: null(<IP_ADDRESS>), req: 'POST /-/npm/v1/security/audits/quick', bytes: 70063/820
 http <-- 200, user: null(<IP_ADDRESS>), req: 'GET /typescript/-/typescript-2.9.2.tgz', bytes: 0/6372426
 http <-- 200, user: null(<IP_ADDRESS>), req: 'GET /typescript/-/typescript-2.7.2.tgz', bytes: 0/6076378

Were you wanting me to check the tarball size on the npm side? If so can you tell me where it is getting stored as when I look in %appdata%/npm-cache-typescript all I see is the 2.4.2 version.

Here is a piece of useful info - I have managed to isolate down the package.json to a point where I can trigger the failure:

{
  "name": "SystemManagementServer",
  "version": "0.0.0",
  "scripts": {
    "ng": "ng",
    "start": "ng serve",
    "build": "ng build",
    "build:ssr": "ng run SystemManagementServer:server:dev",
    "test": "ng test",
    "lint": "ng lint",
    "e2e": "ng e2e"
  },
  "private": true,
  "dependencies": {
    "@angular/common": "6.1.10",
    "@angular/compiler": "6.1.10",
    "@angular/core": "6.1.10"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "~0.6.0",
    "@angular/cli": "~6.0.0",
    "@angular/compiler-cli": "6.1.10",
    "typescript": "~2.8.0"
  },
  "optionalDependencies": {}
}

As the file is configured above, I can consistently get it to say the typescript 2.9.2 is corrupt.  If I remove the @angular-devkit/build-angular line, then typescript 2.9.2 is not flagged as being corrupt.  I dont know enough about npm to try to figure out from this what is happening, but maybe this file might be able to trigger it for you as well.  I was testing by just putting this file in a new subdirectory and running npm install off of it.

btw - today's replies from me were against the Verdaccio 4.0.3 docker image updated today.

Err dang, I just realized, my package.json was pulling 2.8* so the package I removed was the one pulling the 2.9.* in, let me see if it flags it as corrupt if I bump it to 2.9.*

hmm, ok, I think I have stumbled upon the cause/effect, but I need an explanation because npm is not behaving as I thought it did.  If I switch the typescript my original package.json file was referencing from ~2.8.0 to ~2.9.0 npm no longer reports corrupted packages.
My understanding was that any packages referenced by other packages were installed in the node_modules directory under the referencing package (so that version mismatches between referenced tools would not interact with each other), so I am at a loss for explaining how a mismatch between a top level referenced package and a dependency of a another package could interfere with each other.  Can one of you explain this to me?

Ok, I am still at this (switching my teamcity build agent to run under user account instead of system to see if I can get it working that way - good news is Verdaccio now reports my user account, bad news is still corrupted packages).  Right now I have a question on interpreting the diagnostics that come out of Verdaccio.  In these lines it says "Streaming"
 http --> 304, req: 'GET https://registry.npmjs.org/es5-ext' (streaming)
 http --> 304, req: 'GET https://registry.npmjs.org/es5-ext', bytes: 0/0
 http --> 304, req: 'GET https://registry.npmjs.org/typescript' (streaming)
 http --> 304, req: 'GET https://registry.npmjs.org/typescript', bytes: 0/0
 http --> 304, req: 'GET https://registry.npmjs.org/@angular%2Fcore' (streaming)
 http --> 304, req: 'GET https://registry.npmjs.org/@angular%2Fcore', bytes: 0/0

Does this indicate where Verdaccio is actually pulling a new file as opposed to just returning a file from its cache?  I am just trying to see some indicator of where it redownloads the file from the npmjs.org servers.

Well, I have manually pulled the typescript-2.9.2.tgz on another machine (via straight http) and its sha512sum matches the one in the Verdaccio storage volume, so where does npm pull down its files these days when it repulls and fails them so that I can see what is different in the file it is getting.

If I pull the typescript-2.9.2.tgz via browser on the machine in question from the Verdaccio server, it also seems to match the SHA512 I am getting from the other machines, so this appears to be some sort of npm interaction issue or something with how npm is getting the data feed.

On a whim I tried to limit npm to just one download at a time (using --maxsockets=1, it didnt seem to resolve the problem but I was able to see the downloads happening much slower so I think the option did work from that standpoint.  It might be important that I see npm complain about the 2.9 and 2.7 typescripts, but it always redownloads those two and the 2.8 one as well, like they are somehow stepping on each other.

http <-- 200, user: null(<IP_ADDRESS>), req: 'POST /-/npm/v1/security/audits/quick', bytes: 61732/818
http <-- 200, user: jruck(<IP_ADDRESS>), req: 'GET /typescript/-/typescript-2.9.2.tgz', bytes: 0/6372426
http <-- 200, user: jruck(<IP_ADDRESS>), req: 'GET /typescript/-/typescript-2.7.2.tgz', bytes: 0/6076378
http <-- 200, user: jruck(<IP_ADDRESS>), req: 'GET /typescript/-/typescript-2.8.4.tgz', bytes: 0/6034070

Here is the teamcity build log output, I wonder if the .staging\typescript-#### are all stepping on each other......

Checkout directory: H:\TC1-DataDirectory\c617351503b7bc54
[12:13:47]Step 1/1: test (Command Line) (3m:25s)
[12:13:52][Step 1/1] Starting: C:\TeamcityTC1\temp\agentTmp\custom_script8243164111786357582.cmd
[12:13:52][Step 1/1] in directory: H:\TC1-DataDirectory\c617351503b7bc54
[12:13:52][Step 1/1]         1 file(s) copied.
[12:13:52][Step 1/1] C:\Program Files\nodejs\node.exe
[12:13:52][Step 1/1] C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js
[12:13:53][Step 1/1] C:\Users\tcba\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js
[12:13:53][Step 1/1] 6.9.0
[12:13:53][Step 1/1] C:\Program Files\nodejs\node.exe
[12:13:53][Step 1/1] C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js
[12:13:55][Step 1/1] C:\Users\tcba\AppData\Roaming\npm\node_modules\npm\bin\npm-cli.js
[12:14:07][Step 1/1] npm WARN deprecated<EMAIL_ADDRESS>This module is no longer maintained, try this instead:
[12:14:07][Step 1/1] npm WARN deprecated   npm i nyc
[12:14:07][Step 1/1] npm WARN deprecated Visit https://istanbul.js.org/integrations for other alternatives.
[12:16:32][Step 1/1] npm WARN tarball tarball data for<EMAIL_ADDRESS>(sha512-Gr4p6nFNaoufRIY4NMdpQRNmgxVIGMs4Fcu/ujdYk3nAZqk7supzBE9idmvfZIlH/Cuj//dvi+019qEue9lV0w==) seems to be corrupted. Trying one more time.
[12:16:55][Step 1/1] npm WARN tarball tarball data for<EMAIL_ADDRESS><2.8 (sha512-p5TCYZDAO0m4G344hD+wx/LATebLWZNkkh2asWUFqSsD2OrDNhbAHuSjobrmsUmdzjJjEeZVU9g1h3O6vpstnw==) seems to be corrupted. Trying one more time.
[12:17:12][Step 1/1] npm WARN optional SKIPPING OPTIONAL DEPENDENCY<EMAIL_ADDRESS>(node_modules\chokidar\node_modules\fsevents):
[12:17:12][Step 1/1] npm WARN notsup SKIPPING OPTIONAL DEPENDENCY: Unsupported platform for<EMAIL_ADDRESS>wanted {"os":"darwin","arch":"any"} (current: {"os":"win32","arch":"x64"})
[12:17:12][Step 1/1] npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
[12:17:12][Step 1/1] npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>|| ~2.5.0 || ~2.6.0 || ~2.7.0 but none is installed. You must install peer dependencies yourself.
[12:17:12][Step 1/1] npm WARN<EMAIL_ADDRESS>requires a peer of<EMAIL_ADDRESS>but none is installed. You must install peer dependencies yourself.
[12:17:12][Step 1/1]
[12:17:12][Step 1/1] npm ERR! path H:\TC1-DataDirectory\c617351503b7bc54\node_modules.staging\typescript-1171c6e3\lib\tsserverlibrary.js
[12:17:12][Step 1/1] npm ERR! code EPERM
[12:17:12][Step 1/1] npm ERR! errno -4048
[12:17:12][Step 1/1] npm ERR! syscall unlink
[12:17:13][Step 1/1] npm ERR! Error: EPERM: operation not permitted, unlink 'H:\TC1-DataDirectory\c617351503b7bc54\node_modules.staging\typescript-1171c6e3\lib\tsserverlibrary.js'
[12:17:13][Step 1/1] npm ERR!  { [Error: EPERM: operation not permitted, unlink 'H:\TC1-DataDirectory\c617351503b7bc54\node_modules.staging\typescript-1171c6e3\lib\tsserverlibrary.js']
[12:17:13][Step 1/1] npm ERR!   cause:
[12:17:13][Step 1/1] npm ERR!    { Error: EPERM: operation not permitted, unlink 'H:\TC1-DataDirectory\c617351503b7bc54\node_modules.staging\typescript-1171c6e3\lib\tsserverlibrary.js'
[12:17:13][Step 1/1] npm ERR!      errno: -4048,
[12:17:13][Step 1/1] npm ERR!      code: 'EPERM',
[12:17:13][Step 1/1] npm ERR!      syscall: 'unlink',
[12:17:13][Step 1/1] npm ERR!      path:
[12:17:13][Step 1/1] npm ERR!       'H:\TC1-DataDirectory\c617351503b7bc54\node_modules\.staging\typescript-1171c6e3\lib\tsserverlibrary.js' },
[12:17:13][Step 1/1] npm ERR!   stack:
[12:17:13][Step 1/1] npm ERR!    'Error: EPERM: operation not permitted, unlink 'H:\TC1-DataDirectory\c617351503b7bc54\node_modules\.staging\typescript-1171c6e3\lib\tsserverlibrary.js'',
[12:17:13][Step 1/1] npm ERR!   errno: -4048,
[12:17:13][Step 1/1] npm ERR!   code: 'EPERM',
[12:17:13][Step 1/1] npm ERR!   syscall: 'unlink',
[12:17:13][Step 1/1] npm ERR!   path:
[12:17:13][Step 1/1] npm ERR!    'H:\TC1-DataDirectory\c617351503b7bc54\node_modules\.staging\typescript-1171c6e3\lib\tsserverlibrary.js',
[12:17:13][Step 1/1] npm ERR!   parent: '@angular-devkit/build-optimizer' }
[12:17:13][Step 1/1] npm ERR!
[12:17:13][Step 1/1] npm ERR! The operation was rejected by your operating system.
[12:17:13][Step 1/1] npm ERR! It's possible that the file was already in use (by a text editor or antivirus),
[12:17:13][Step 1/1] npm ERR! or that you lack permissions to access it.
[12:17:13][Step 1/1] npm ERR!
[12:17:13][Step 1/1] npm ERR! If you believe this might be a permissions issue, please double-check the
[12:17:13][Step 1/1] npm ERR! permissions of the file and its containing directories, or try running
[12:17:13][Step 1/1] npm ERR! the command again as root/Administrator (though this is not recommended).
[12:17:13][Step 1/1]
[12:17:13][Step 1/1] npm ERR!      C:\Users\tcba\AppData\Roaming\npm-cache_logs\2019-06-19T17_17_12_773Z-debug.log
[12:17:13][Step 1/1] Process exited with code -4048
[12:17:13][Step 1/1] Process exited with code -4048 (Step: test (Command Line))
[12:17:13][Step 1/1] Step test (Command Line) failed

the teamcity build step being referenced (command line runner):

copy h:\test3\package.json
call npm -v
call npm install --maxsockets=1
and that package.json

{
"name": "SystemManagementServer",
"version": "0.0.0",
"scripts": {},
"private": true,
"dependencies": {
"@angular/common": "6.1.10",
"@angular/compiler": "6.1.10",
"@angular/core": "6.1.10"
},
"devDependencies": {
"@angular-devkit/build-angular": "~0.6.0",
"@angular/cli": "~6.0.0",
"@angular/compiler-cli": "6.1.10",
"typescript": "~2.8.0"
},
"optionalDependencies": {}
}

One other datapoint, I went and deleted the node_modules and package-lock.json files, after this (when doing it myself from a command prompt and not using teamcity) for the first run I got the corrupted files message but a re-run had no corrupted files.  I notice that the corrupted file messages are saying the checksum for a different version of the package -<EMAIL_ADDRESS>when the actual package returned was 2.9.2, so is this maybe a problem where the checksums are being reported for the wrong file which is why they fail and why redownloading the file doesnt resolve the issue?
I dont know where to look to see what checksums are being returned each time.

Set server.keepAliveTimeout in config to a large value works for me (or with the new version 4.0.4, set it to zero also works)

I'm having the same issue with other packages when I try to use create-react-app to initialize a new react project using the default react template. I'm not exactly sure how to approach a fix on this.

Upgrading from Ubuntu 18 LTS to Ubuntu 20 LTS seems to have fixed the issue for me.

If you have issues downloading larger files, then https://github.com/verdaccio/verdaccio/pull/1207 fix the issue.
Add a custom value in the config.yaml file. A reminder this is supported Node 8 an higher,
server:
  keepAliveTimeout: 60
```

https://verdaccio.org/docs/en/configuration#server

I'm closing this one, feel free to share more feedback.


#1615 fix

#1615
I also turned requires_grad off on some of them
also for sparse_categorical_crossentropy and argmax, should the arange be int32?

Changes made in tinygrad/:
------------------------------------------------------------
files                             insertions       deletions
------------------------------------------------------------
tinygrad/tensor.py                         6               6
------------------------------------------------------------
lines added in the tinygrad folder: 0

yea, the dtypes should be fine for crossentropy and argmax, both are indexes

@ZenginU also found that ones_like and zeros_like from torch
"Returns a tensor filled with the scalar value 1/0, with the same size as input. torch.ones_like(input) is equivalent to torch.ones(input.size(), dtype=input.dtype, layout=input.layout, device=input.device)"
So I suppose having full_like take the device=tensor.device is gooooooooooooood?

yea thats fine

merge conflict


chore: jsonfmt devtestlabls

Ran jsonfmt -w "specification/devtestlabs/**/*.json"

Can one of the admins verify this patch?

Automation for azure-sdk-for-ruby

Automation for azure-sdk-for-python

Automation for azure-sdk-for-js

Automation for azure-sdk-for-go

Automation for azure-sdk-for-java


Use path-browserify for web environments.

This PR adds support for using path-browserify for environments where native path is not present (i.e. on web environments)

Sorry for the mistake, meant to do this on my forked repo.


Improve retry docs

Addresses https://github.com/Azure/azure-sdk-for-net/issues/27989

API change check for Azure.Messaging.EventHubs
API changes are not detected in this pull request for Azure.Messaging.EventHubs

API change check for Azure.Messaging.ServiceBus
API changes are not detected in this pull request for Azure.Messaging.ServiceBus


Missing requirement of typing-extensions on python <= 3.10

On python versions that do not provide typing.Self (i.e., python <= 3.10), schwifty falls back to using typing_extensions. However, it does not specify typing-extensions as a requirement, and consequently user installing schwifty in a clean virtual environment will end up with defunct version. For example, on linux:
python3.10 -m venv venv
. venv/bin/activate
pip install schwifty
python -c "import schwifty"

Traceback (most recent call last):
  File "[...]/venv/lib64/python3.10/site-packages/schwifty/common.py", line 9, in <module>
    from typing import Self
ImportError: cannot import name 'Self' from 'typing' (/usr/lib64/python3.10/typing.py)

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "[...]/venv/lib64/python3.10/site-packages/schwifty/__init__.py", line 6, in <module>
    from schwifty.bban import BBAN
  File "[...]/venv/lib64/python3.10/site-packages/schwifty/bban.py", line 5, in <module>
    from schwifty import common
  File "[...]/lib64/python3.10/site-packages/schwifty/common.py", line 11, in <module>
    from typing_extensions import Self
ModuleNotFoundError: No module named 'typing_extensions'

Looks like https://github.com/mdomke/schwifty/commit/aa251c25c3439d5c2de476f444f5be7467ea866b accidentally removed ˙"typing_extensions>=4.0; python_version <= '3.11'"` requirement that was added in #201.

I published a new release 2024.05.2 to address the issue.


Add option similar to maxdepth, but only track nested if's

Thanks for your interest in JSHint! This feature request is missing some important information. Check out the project's contribution guide for tips on how to start a discussion about new functionality.


JavaScript Best Practices

[ ] Keep all the JavaScript code in JS files, not in the script tag.
- No issue found

[ ] type checks
- No issue found

[ ] naming
- No issue found

[ ] simplicity
- No issue found

[ ] DRY
- No issue found

Assign me to this


Split service workers helpers

We need to move service workers helpers to a dedicated repository and just add integration in this one.

Use https://github.com/Chialab/sw-helpers-js


⚠ Secret Website 2 has degraded performance

In 423e11e, Secret Website 2 ($SECRET_WEBSITE_2) experienced degraded performance:

HTTP code: 200
Response time: 14637 ms

Resolved: Secret Website 2 performance has improved in b2c05a2.


Add description into .pre-commit-hooks.yaml

So, https://pre-commit.com/hooks.html page will indicate this description.

The official mirrors don't do this e.g. https://github.com/pre-commit/mirrors-prettier , https://github.com/pre-commit/mirrors-mypy - maybe submit PR's there.


Setup email campain

[x] Install nodemailer
[ ] Make email campain html
[ ] Create email script that can be reused by any components
story point: 5
-Time estimation 10 hr

Emails can now be sent using jnodeMailer


Forms: Finalize Terrestrial Plant Observation API

Describe the Task
Follow up form edits after consulting with the business area (first ticket was #207). This ticket is to deal with changes within the code tables/API.
See attached spreadsheet for field specific details:
https://app.zenhub.com/files/296689811/0a3c4e95-8944-49f4-ae2a-04f188f642a5/download

UI for Terrestrial Plant Observation Form

UI for Terrestrial Plant Observation Form


The scrollbar for the terminal window does not work

The scrollbar for the terminal window (linux1, vqfx1, vqfx2, ...) does not work
I see the slider on the right-hand side, but I cannot drag it.
I could not discover any way to scroll back beyond the currently visible screen.
This is a major issue because most of the output is larger than one screen's worth of data.

PS: This is running Chrome on a macOS

@brunorijsman Hi! This is a known issue with the way the mouse mapping is currently being done. You can get around this for now by using Shift+PgUp / Shift+PgDown (on mac you'll have to use fn+up/down in lieu of a dedicated page button).


What's the difference between two "Office 365 Education for Faculty" SKUs?

The table on https://docs.microsoft.com/en-us/MicrosoftTeams/sku-reference-edu lists:
Plan name 	SkuPartNumber 	SkuID
Office 365 Education for Faculty 	STANDARDWOFFPACK_FACULTY 	94763226-9b3c-4e75-a931-5c89701abe66
Office 365 Education for Faculty 	STANDARDWOFFPACK_IW_FACULTY 	78e66a63-337a-4a9a-8959-41c6654dfb56
SKU 94763226-9b3c-4e75-a931-5c89701abe66 appears as "Office 365 A1 for faculty" in the admin center.
SKU 78e66a63-337a-4a9a-8959-41c6654dfb56 appears as "Office 365 A1 Plus for faculty" in the admin center.
What's the difference between these two SKUs?  Both seem to be free but how can you check eligibility?

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

ID: ae22e4df-3f88-8c54-c55e-a3cd4f720cbc
Version Independent ID: 3be05aac-9860-e78c-aca7-c62de044c48b
Content: Education SKU reference - Microsoft Teams
Content Source: Teams/sku-reference-edu.md
Service: msteams
GitHub Login: @LanaChin
Microsoft Alias: v-lanac

@rsoakford thank you for submitting feedback.
I think the best way forward is if you open a service ticket in your tenant so this can get resolved ASAP. Based on the outcome let me know if it is something that can be called out in the docs.
Please follow this link to contact support for business products:https://docs.microsoft.com/office365/admin/contact-support-for-business-products
Please keep us posted here on the resolution so we can feed whatever information you discover into the content.


beta version has been marked as latest

@fabian-hiller I've noticed that the latest beta version, 1.0.0-beta.0, has been marked as latest on npm.
This has led to some unexpected behavior in our project.
It might be helpful to consider tagging the beta version as 'beta' on npm, while restoring the 'latest' tag to the previous stable release (v0.42.1).
This could help prevent potential issues for other users.

Thanks for the tip! I thought npm would automatically detect prereleases. This is now fixed.

Hey, if you freshly install Valibot, you get version 1.0.0-beta from npm, which is quite unexpected because the documentation isn't up to date (which is, in turn expected for beta stuff). Also, this release is marked as a pre-release on GitHub. Is this intentional? It certainly threw me off.

Our documentation should be up to date. Only some internal APIs may be missing or out of date. There are no changes to our external API between the latest v0 and v1 beta. I decided to mark it as latest on npm to get more feedback and get a better and more stable v1 release faster. I know this is a bad DX at the moment and I am very sorry for that. But this will be fixed soon when we release our stable v1.


how do i update react table after i added or removed rows?

Problem Description
I am trying to update react table programatically to refresh itself when i add or remove new data to the table. Is there a way to refresh the table without refreshing the whole page?
I bind data using {this.state.myData}
Code Snippet(s) or Codepen (http://codepen.io/tannerlinsley/pen/QpeZBa?editors=0010)
Steps to Reproduce

list the steps
to reproduce the issue

System Information

Browser & Browser Version: Chrome, latest version
Node Version: 6.10.3
OS Version:
NPM Version:
Yarn Version:

Data should be automatically refreshed when you change the reference to data. Make sure you're not mutating the original reference but creating a new copy (e.g data = [...data])
If you need more help with implementation please join the slack channel.
Slack Signup: https://react-chat-signup.herokuapp.com/


deserializeJson() failed: NoMemory

Sometimes serial is running this error --

seems like there is enough memory- still trying to find a work around

found a typing error - Last JSON_OBJECT_SIZE(14)+280 - change to JSON_OBJECT_SIZE(13)+270 and that solved it


New release?

There have been some new capabilities added to the project since the November 2017 release. Are there any plans to cut a new release that is more recent?

Wish granted! I think you happened to file this just before I noticed the same thing and did a release. v1.3.0 is now on PyPI.

Awesome, thank you!
Regards,
Tobias Macey
https://linkedin.com/in/tmacey
On Sat, Aug 3, 2019 at 6:39 AM Luke Plant<EMAIL_ADDRESS>wrote:

Closed #32 https://github.com/python-parsy/parsy/issues/32.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/python-parsy/parsy/issues/32?email_source=notifications&email_token=AADU64ERMFGF4UZSM7XF5ODQCVN7DA5CNFSM4IJA7TL2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOS3P6PGI#event-2531256217,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AADU64BL7VAZXQBE7MX6H6LQCVN7DANCNFSM4IJA7TLQ
.


chore(package): update tap to version 10.2.0

Closes #31
https://greenkeeper.io/

Coverage remained the same at 93.75% when pulling 4308042b5d10380f926bae808f5e560a9296c2cd on greenkeeper/tap-10.2.0 into d9c4d54b1cee75839ac477ea2fa789065a4d3a65 on master.


Episodes above 30

It seems that the episodes list is capped at the number 30. Why is that and how can it be solved?

Fixed, please give a try.


GHA setup to automate release changelog creation

We should have some setup like this:
https://github.com/MylesBorins/node-osc/blob/main/.github/workflows/create-release.yml
This does several things, when a new tag is created and pushed:

publish to npm
create GH release
generate changelog for the GH release

This may be useful for us. What do you think @materializecss/members?

This is very nice, but I think we will need to review / rework manually the automated change log if it's based on the commits.
I take for examples some of my PR that haves a bunch of commits for a single bug fix. It's better to have one change log entry instead of five

The Changelog is generated automatically by GitHub.
I think this is solved. Feel free to reopen.


Should inline source in haddock files use syntax highlighting?

It was suggested on a reddit UX thread. Interesting question, not sure if I'd want it...

Also, potentially, e.g. typeclass constraints, instance heads, etc?

The title of the issue is not a good idea. I frequently use inline code for stuff that is not Haskell.
If anything, we might want to add support for describing which language is used in a code block (and having some flag that, when enabled, packages in some JS library to highlight accordingly).

Also, potentially, e.g. typeclass constraints, instance heads, etc?

I'm not sure what is meant here, but it sounds interesting. Care to elaborate?

What I meant was not just inline code, but the code in haddocks themselves -- type signatures, etc.
Also note that we have a "semi" highlighting that comes from the hyperlinks and i don't know how a typical highlighting lib would interact with that.

I think syntax highlighting for example code would be a great idea (trying to figure out if it were possible is how I came upon this ticket).

The title of the issue is not a good idea. I frequently use inline code for stuff that is not Haskell.

I agree that forcing a particular highlight would be bad. I think a correct implementation would have the capability to highlight haskell (or maybe even non-haskell) code, but not necessarily require such highlighting. Something like github's ```<language> syntax highlighting format. (see also: https://help.github.com/articles/creating-and-highlighting-code-blocks/)

I don't know if I already wrote this down into an issue describing the idea, but for code blocks in haddock markup I had planned to do something like
> -- haddock-highlight: c --
>
> size_t mystrlen (const char x[])
> {
>   return x ? strlen(x) : 0;
> }

And default to haddock-highlight: plain (i.e. no highlighting at all) and give a way via a {-# HADDOCK_OPTIONS #-}` setting to set a default highlighting mode for the current module.
We need some way to switch on syntax highlighting which gracefully degrades with older Haddock versions, as we don't have a good version gating story for Haddock yet.

Being able to specify the language would be quite nice. With the language specified something like highlightjs could be easily used HTML side at least. OOC if -- haddock-highlight: language-name -- is used in old versions, would it just display this verbatim rather than use highlighting? So no breakages, but noise in output (or folks would employ a a post-processing script so that it is nop).

It would be great to get this! Then code examples on Haddock would be able to get nice syntax highlighting, right? Probably not old ones due to backward compatibility, but at least we would be able to specify the syntax for the new releases, right?
General idea sounds good to me, of by default not having any highlighting, in order to stay backward compatible, but then one could set a default highlighting to be Haskell + one could choose language per code block/snippet that would override the default setting.
What are the needed steps to get this going? I am proficient with Haskell, but have never contributed to Haddock -> is this something a new contributor would be able to tackle? Could you maybe provide some higher-level steps on how to approach this, some pointers on the best way to attack this?


how to handle "workbench" composer updates?

I'm putting some of my app logic inside a package so I can use those for other applications. Since the app is still in development the package itself is still in the workbench folder of my main app. Can you give me some pointers how I would define this in Rocketeer that he has to run composer update first for the workbench and then for the main folder?
thx!

You could do:
Rocketeer::before('dependencies', function (AbstractTask $task) {
   $workbench = $task->releasesManager->getCurrentReleasePath('workbench');

   $task->runInFolder($workbench, [
      'composer install',
   ]);
});

Or something of that effect

Thx! this did the trick :)


Add $like documentation for knex

See also https://github.com/feathersjs/feathers-knex/pull/79

Perfect, thanks again!


Link API Docs directly to Path class doc in README

I suggest linking the API Docs directly to the Path class doc, since it's the only one as of now.
Easier to find for people, and the only useful API doc page.

Good idea! :) Thanks!


Better documentation - here's how you REALLY install [iOS]

This should be added to the documentation. It's much more clear and will save headaches in debugging issues.

Enable cloud capabilities

If you have automatic code signing, this will be created and handled for you. It's important to check the boxes exactly as shown in the picture.

Run
npm install git://github.com/Elyx0/react-native-document-picker.git#v3 --save
This installs the latest updates in the document picker.

Run
react-native link
Links android modules, I honestly don't think it does anything for iOS but may as well run it anyway.

Open your project in XCode, right click on Libraries and click Add Files to "Your Project Name"

Add libRNDocumentPicker.a to Build Phases -> Link Binary With Libraries

Now, restart your entire simulator, packager, debugger etc (quit out of running stuff and rerun it)

Should be done and working now.

For testing purposes, if you want to see if it is working, try the following react-native code:
console.log(DocumentPicker)
try {
    const res = DocumentPicker.pick({
        type: [DocumentPicker.types.images],
    });
    console.log(
        res.uri,
        res.type, // mime type
        res.name,
        res.size
    );
} catch ( err ) {
    if ( DocumentPicker.isCancel(err) ) {
        // User cancelled the picker, exit any dialogs or menus and move on
    } else {
        throw err;
    }
}

Thanks for this help!
I'll add you need to enroll the paid Apple developer program to activate the iCloud entitlement...

this picker is not display , why?

@agates4 followed all the steps u specified but facing the below issues while IOS build
duplicate symbol OBJC_IVAR$_RNDocumentPicker.composeViews
duplicate symbol OBJC_IVAR$_RNDocumentPicker.composeCallbacks
duplicate symbol OBJC_CLASS$_RNDocumentPicker
duplicate symbol OBJC_METACLASS$_RNDocumentPicker
duplicate symbol OBJC_IVAR$_RNDocumentPicker._bridge
ld: 5 duplicate symbols for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)
any solution?

@GrishmaM if you're getting that error, add this to your Podfile (in the iOS folder). This should be added to your target scheme
target 'MyApp' do
    # Uncomment the next line if you're using Swift or would like to use dynamic frameworks
    # use_frameworks!

    # Pods for MyApp
    rn_path = '../node_modules/react-native'
    pod 'yoga', path: "#{rn_path}/ReactCommon/yoga/yoga.podspec"
    pod 'React', path: rn_path, subspecs: [
        'Core',
        'RCTActionSheet',
        'RCTAnimation',
        'RCTGeolocation',
        'RCTImage',
        'RCTLinkingIOS',
        'RCTNetwork',
        'RCTSettings',
        'RCTText',
        'RCTVibration',
        'RCTWebSocket',
        'DevSupport'
    ]

    pod 'react-native-document-picker', :path => '../node_modules/react-native-document-picker`

end

# very important to have the below added to the very end of the Podfile
post_install do |installer|
    installer.pods_project.targets.each do |target|
        if target.name == "React"
            target.remove_from_project
        end
    end
end

Then, in the command prompt use the command pod deintegrate and after it is completed, do pod install
That should solve it!

@agates4 Thanks for your great and simple explanation. Just one single note: since in your used version DocumentPicker is exported as default, then we should use the following import:
import DocumentPicker from "react-native-document-picker"

I followed these directions exactly and rebuilt my app, but I'm getting this warning: RNDocumentPicker: Native module is not available, make sure you have finished the installation process and rebuilt your app

I followed these directions exactly and rebuilt my app, but I'm getting this warning: RNDocumentPicker: Native module is not available, make sure you have finished the installation process and rebuilt your app. Does anyone know how I can fix this?

My gut tells me this is a caching issue
Maybe try
delete package.lock and node_modules/
npm install
delete Podfile.lock and Pods/
clear Xcode build with Command + Shift + K
quit Xcode
Pod install in the ios/ folder
If it still doesn't work, then there's something else going on

I'm getting this error:
RNDocumentPicker: Native module is not available, make sure you have finished the installation process and rebuilt your app
But I followed the directions above exactly. I can't figure out what I'm doing wrong :(

I don't have pods installed in my react native app. Would this affect anything? It's still not working.

It didn't work when I did that, so I tried installing again with cocoa pods. It doesn't throw an error or warning anymore when I have import { DocumentPicker, DocumentPickerUtil } from 'react-native-document-picker'; at the top of my file, but when I try to run the sample code above, it says that DocumentPicker is undefined. I got this error before as well, but I also had the warning that rnDocumentPicker wasn't fully installed. Now that it is, I don't know what's going on :(

What finally worked for me was installing with cocoa pods and then changing my code to:
var DocumentPicker = require('react-native-document-picker');
DocumentPicker.default.pick({
                            type: [DocumentPicker.default.types.allFiles],
                          },(error,res) => {
                            // Android
                            console.log(
                              "Okay Bhai error paichi Document Picker e: ",
                              res.uri,
                              res.type,
                              res.fileName,
                              res.fileSize
                            );
                          })

Is it posible to add an option of file size limit?

I tried these steps (and that on docs) but it gives RTCDefines.h error. I opened a issue about it
https://github.com/Elyx0/react-native-document-picker/issues/249

Having similar issue when building for IOS,
"react-native": "0.59.10"
"react-native-document-picker": "^3.2.2"
ld: warning: directory not found for option '-L/Users/{user}/Library/Developer/Xcode/DerivedData/app-cdhuqaxbqwujfufogqftsrampkmb/Build/Products/Debug-iphonesimulator/React'

duplicate symbol '_OBJC_IVAR_$_RNDocumentPicker.composeViews' in:
    /Users/{user}/Library/Developer/Xcode/DerivedData/app-cdhuqaxbqwujfufogqftsrampkmb/Build/Products/Debug-iphonesimulator/react-native-document-picker/libreact-native-document-picker.a(RNDocumentPicker.o)
    /Users/{user}/Library/Developer/Xcode/DerivedData/app-cdhuqaxbqwujfufogqftsrampkmb/Build/Products/Debug-iphonesimulator/libRNDocumentPicker.a(RNDocumentPicker.o)

duplicate symbol '_OBJC_IVAR_$_RNDocumentPicker.composeResolvers' in:
    /Users/{user}/Library/Developer/Xcode/DerivedData/app-cdhuqaxbqwujfufogqftsrampkmb/Build/Products/Debug-iphonesimulator/react-native-document-picker/libreact-native-document-picker.a(RNDocumentPicker.o)
    /Users/{user}/Library/Developer/Xcode/DerivedData/app-cdhuqaxbqwujfufogqftsrampkmb/Build/Products/Debug-iphonesimulator/libRNDocumentPicker.a(RNDocumentPicker.o)
... etc...
ld: 6 duplicate symbols for architecture x86_64
clang: error: linker command failed with exit code 1 (use -v to see invocation)

React Native 0.50.10
"react-native-document-picker": "^3.2.4"
Got this to work by removing
LibRNDocumentPicker.a from Link Binary with Libraries in xcode.

closing as resolved, the image is in the readme and autolinking makes the install process easier


FOV Support

Would it be possible to support different FOV values?
From a cursory search around it seems like Flawless Widescreen supports changing the FOV.
It would be really nice to have an option like --fov value if doable.
Thank you for the great tool!

Hi, I had a look how the FOV patch works in Flawless Widescreen and unfortunately the method they use is not straight forward to implement in er-patcher. They patch the game memory at runtime and essentially inject additional code whereas er-patcher in its current state can only modiify existing code. So unless someone figures out to adjust the fov without having to inject additional code/instructions, you have to make do without or just use FWS.

Ah, I didn't realise it injected additional code.
No problem, thank you for looking into it! I'll close this issue for now.


Unable to run ElectronTestApp (msal-node-samples) with Azure B2C

Library

[ ]<EMAIL_ADDRESS>
Description

I am trying to run a sample project here https://github.com/AzureAD/microsoft-authentication-library-for-js/tree/dev/samples/msal-node-samples/standalone-samples/ElectronTestApp
I set up my MSAL_CONFIG configuration but when I click log in, the page fails to load and I receive a blank page. Going to the source code of the page I was able to get this code from HTML page

We can't sign you in

Your browser is currently set to block JavaScript. You need to allow JavaScript to use this service.

To learn how to allow JavaScript or to find out whether your browser supports JavaScript, check the online help in your web browser.

We can't sign you in

Your browser is currently set to block cookies. You need to allow cookies to use this service.

Cookies are small text files stored on your computer that tell us when you're signed in. To learn how to allow cookies, check the online help in your web browser.

Source

[ ] Internal (Microsoft)
[ ] Customer request

Hi @ammritt! Could you please provide your MSAL configuration so we can have a little more information and try to help you debug this?

Hi @ammritt! Could you please provide your MSAL configuration so we can have a little more information and try to help you debug this?

Hi @hectormmg This is a production B2C account
I am sending you an email with my MSAL Configuration

Hi @hectormmg This is a production B2C account
I am sending you an email with my MSAL Configuration

Hi @hectormmg just following up to see if you have been able to reproduce my issue.

Hey @ammritt ! I haven't been able to reproduce it yet, but I'll let you know when I have more information!

@ammritt I'm able to reproduce your issue now. It seems the B2C login page requires cookies and javascript to be enabled wherever they are rendered. I've tested enabling javascript on the BrowserWindow object and registering the custom protocol as privileged so cookies are enabled, but no success yet. I'm investigating what other configuration changes need to be made on the sample to support that. I'll update this issue when I figure it out.

hi @hectormmg
Do you have any updates? Do you think it's an issue with the Azure B2C service or an issue with the sample app?

@ammritt apologies for the delay. I'm updating the sample to use a Popup to load the B2C login screen, given that the main window shouldn't allow the execution of external scripts. It seems for now doing auth in a second window (instead of the main application window through redirects as the sample does now) is going to be the recommended usage pattern for B2C. I'll keep investigating to make sure that's the right approach.


For each of the dependencies files, create a workflow to extract the dependencies and check for the latest version...

if the latest version is not present, generate a text file containing the dependency and the version available

@Riyu44 -

Python requirements.txt
Python pyproject.toml
Ruby Gemfile
GO go.sum

@Tushar-2510

Ruby Gemfile.lock
Java Maven pom.xml
Java Gradle build.gradle

@CodePrakhar

C# packages.config
Go go.mod
Haskell stack.yaml

@Suvarchala-30

Rust Cargo.lock
Rust Cargo.toml
PHP composer.json

@navvay

Swift packages.swift
C CMakeLists.txt
C++ CMakeLists.txt

I think this issue can now be closed.


error after accepting pop up.

i'm using linux mint.  when running gimme-aws-creds, i get this traceback.  not quite sure how to resolve. any help is most certainly appreciated.  this was working a few days back until maybe updates.  i tried uninstalling gimme-aws-creds and re-installing using pip3 install/uninstall gimme-aws-creds.
Multi-factor Authentication required.
Okta Verify App: SmartPhone_Android: SM-N960U selected
Okta Verify push sent...
Traceback (most recent call last):
File "/home/mark/.local/bin/gimme-aws-creds", line 17, in
GimmeAWSCreds().run()
File "/home/mark/.local/lib/python3.8/site-packages/gimme_aws_creds/main.py", line 469, in run
self._run()
File "/home/mark/.local/lib/python3.8/site-packages/gimme_aws_creds/main.py", line 802, in _run
for data in self.iter_selected_aws_credentials():
File "/home/mark/.local/lib/python3.8/site-packages/gimme_aws_creds/main.py", line 773, in iter_selected_aws_credentials
for role in self.aws_selected_roles:
File "/home/mark/.local/lib/python3.8/site-packages/gimme_aws_creds/main.py", line 672, in aws_selected_roles
selected_roles = self._get_selected_roles(self.requested_roles, self.aws_roles)
File "/home/mark/.local/lib/python3.8/site-packages/gimme_aws_creds/main.py", line 663, in aws_roles
self.saml_data['SAMLResponse'],
File "/home/mark/.local/lib/python3.8/site-packages/gimme_aws_creds/main.py", line 654, in saml_data
self._cache['saml_data'] = saml_data = self.okta.get_saml_response(self.aws_app['links']['appLink'])
File "/home/mark/.local/lib/python3.8/site-packages/gimme_aws_creds/main.py", line 647, in aws_app
self._cache['aws_app'] = aws_app = self._get_selected_app(self.conf_dict.get('aws_appname'), self.aws_results)
File "/home/mark/.local/lib/python3.8/site-packages/gimme_aws_creds/main.py", line 600, in aws_results
self.auth_session
File "/home/mark/.local/lib/python3.8/site-packages/gimme_aws_creds/main.py", line 582, in auth_session
auth_result = self.okta.auth_session()
File "/home/mark/.local/lib/python3.8/site-packages/gimme_aws_creds/okta.py", line 183, in auth_session
"session": response.cookies['sid'],
File "/usr/lib/python3/dist-packages/requests/cookies.py", line 328, in getitem
return self._find_no_duplicates(name)
File "/usr/lib/python3/dist-packages/requests/cookies.py", line 399, in _find_no_duplicates
raise KeyError('name=%r, domain=%r, path=%r' % (name, domain, path))
KeyError: "name='sid', domain=None, path=None"
... update. i'm getting the same error on windows as well.

Seeing same issue on macos. This started happening after I updated my okta password.

found a fix which required modifying main.py as:
@property
def auth_session(self):
    if 'auth_session' in self._cache:
        return self._cache['auth_session']
    auth_result = self.okta.auth_session(redirect_uri=self.conf_dict.get('app_url'))
    self.set_auth_session(auth_result)
    return auth_result

this fixed the issue for me.  maybe i can see about a pull request.

Also, it's a duplicate of https://github.com/Nike-Inc/gimme-aws-creds/issues/302


bubble:0.2.2

I am submitting

[ ] a new package
[x] an update for a package

Description: Fix hardcoded language in the template and add some minor features (new other field)

[x] ensured that my package is licensed such that users can use and distribute the contents of its template directory without restriction, after modifying them through normal use.

It would be nice if you could fix the error reported in CI. You can ignore the warnings.


chore: Activity screen refactoring & code decoupling

Follows up on https://github.com/artsy/eigen/pull/10988
Description
This is an attempt to refactor and decouple the Activity screen code to avoid bugs like the one fixed in https://github.com/artsy/eigen/pull/10988. I noticed that the artwork list component, which is used for many activity types, contains some type-specific elements and optimizations and tried to move them out of the component.

PR Checklist

[ ] I have tested my changes on iOS and Android.
[ ] I hid my changes behind a feature flag, or they don't need one.
[ ] I have included screenshots or videos, or I have not changed the UI.
[ ] I have added tests, or my changes don't require any.
[ ] I added an app state migration, or my changes do not require one.
[ ] I have documented any follow-up work that this PR will require, or it does not require any.
[ ] I have added a changelog entry below, or my changes do not require one.

To the reviewers 👀

[ ] I would like at least one of the reviewers to run this PR on the simulator or device.

Changelog updates
Changelog updates

Cross-platform user-facing changes

iOS user-facing changes

Android user-facing changes

Dev changes

Activity item screen code refactoring & decoupling (test setup: https://www.notion.so/artsy/Activity-Panel-cd0a9668895848a484b51bebb9723a8f?pvs=4#1faeb480c6d3432fa866718aa446ef5d) - ole

Need help with something? Have a look at our docs, or get in touch with us.

This PR contains the following changes:

Dev changes (Activity item screen code refactoring & decoupling (test setup: https://www.notion.so/artsy/Activity-Panel-cd0a9668895848a484b51bebb9723a8f?pvs=4#1faeb480c6d3432fa866718aa446ef5d) - ole - olerichter00)

  Generated by :no_entry_sign: dangerJS against 6c6e0f7c06c5ba8c4b2c2aa4114f25970c2c7264

But I can see that there are changes in the rendered elements code, maybe we should test it and take screenshots before and after to make sure that this changes doesn't introduce a visual bug?

That's a very good idea 👍 I've tested the changes with all notification types but haven't taken screenshots. I'll add them to the PR.


Add safe mode reconfig recovery test

Description
This PR tests our safe mode reconfiguration, checking that:

we enter the safe mode after an abort in advance_epoch
framework upgrade can happen even when regular advance_epoch fails
after upgrading to a good framework we exit the safe mode

I wanted to make the safe mode code smaller since all it needs to do is to abort during reconfig but it's pretty hard - genesis needs to create the expected objects so genesis code needs to be there and genesis code depends on everything.
Test Plan
added a test

If your changes are not user-facing and not a breaking change, you can skip the following section. Otherwise, please indicate what changed, and then add to the Release Notes section as highlighted during the release process.
Type of Change (Check all that apply)

[ ] user-visible impact
[ ] breaking change for a client SDKs
[ ] breaking change for FNs (FN binary must upgrade)
[ ] breaking change for validators or node operators (must upgrade binaries)
[ ] breaking change for on-chain data layout
[ ] necessitate either a data wipe or data migration

Release notes

I have rebased after the framework separation PR landed. And now the added Move code for testing should be much smaller. Let me know how it looks now and if you think we still need to have the flow that does the module substitution @amnn

Yeah i agree with @amnn , adding ~10k lines of code (much of it duplicate) seems like an easy way to make our lives a bit challenging going forward.

I am looking at a simple mock governance contract, maybe we can share that

As @lxfind mentioned, for his system state upgrade test, he's working on a condensed test version of sui-system package containing only the necessary functions / structs for the system to operate, that is decoupled from the actual package and has its own test system state type that impls the SuiSystemStateTrait. This way when the actual package in the framework changes, there's no need to change the test package, with the exception of changes to signatures of genesis and epoch change functions. Does that sound better? @amnn @bmwill

Updated the PR based on @lxfind 's mock sui system package with a minimal safe_mode version that's even smaller than the base mock package. @amnn


./configure: line 8363: .: filename argument required

When resolv.h is not found or found to be unusable, these lines error out on Mac OS X 10.4.11:
https://github.com/OpenPrinting/cups/blob/7a7ef6b180a35f64eee12db982a245da69e17574/configure#L8363-L8368
I'm not sure what those lines are supposed to be doing. Any tips appreciated!

Hi @evanmiller ,
thank you for reporting the issue!
IIUC those lines include the header files which would be included by resolv.h if it was present.
It would be great if you attached your config.log (with .txt suffix) here for examination what exactly went wrong.
Thank you in advance!

Found the bug (or a bug):
https://github.com/OpenPrinting/cups/blob/7a7ef6b180a35f64eee12db982a245da69e17574/config-scripts/cups-network.m4#L15
Should be a comma, not a period.


Add a start time counter for helping monitoring

As descrived in mef_eline#341, we lack a mechanism to identify when some services are actually down or they are just booting up. My suggestion is, as a workaround, we add the start time counter to kytos_stats, and then we can leverage this counter on zabbix_wrapper (or any other monitoring tool) to identity those booting moments.

@italovalcy @gretelliz
I'll add some comments to mef_eline#341 shortly.
Regarding the workaround, maybe we could instead augment this core endpoint GET localhost:8181/api/kytos/core/status to include when the APIServer started? In fact, we already have a self.started_at keeping track right after the Controller instance is started and dispatched the tasks:
diff --git a/kytos/core/api_server.py b/kytos/core/api_server.py
index 8d9d788..8cc7819 100644
--- a/kytos/core/api_server.py
+++ b/kytos/core/api_server.py
@@ -146,7 +146,14 @@ class APIServer:

     def status_api(self, _request: Request):
         """Display kytos status using the route ``/kytos/status/``."""
-        return JSONResponse({"response": "running"})
+        uptime = self.napps_manager._controller.uptime()
+        return JSONResponse(
+            {
+                "response": "running",
+                "uptime_seconds": uptime.seconds if uptime else 0,
+                "started_at": self.napps_manager._controller.started_at,
+            }
+        )

❯ http localhost:8181/api/kytos/core/status
HTTP/1.1 200 OK
content-length: 90
content-type: application/json
date: Mon, 26 Jun 2023 19:33:30 GMT
server: uvicorn

{
    "response": "running",
    "started_at": "2023-06-26T19:31:53.776338+00:00",
    "uptime_seconds": 97
}

and then on zabbix_wrapper, depending on the endpoint, it could send a pre-request and check either uptime_seconds or started_at` and depending on the value returning a value that's considered unknown until we augment mef_eline? wdyt?


[CARBONDATA-1111]Improve No dictionary column Include And Exclude filter And Fixed Data Mismatch Issue In case of range Filter

Improve No dictionary column Include And Exclude filter
Fixed Data mismatch issue
Fixed Alter with Caps Decimal issue

Build Failed  with Spark 1.6.2, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2122/

retest this please

add to whitelist

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2123/

retest this please

Build Failed  with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2132/

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/carbondata-pr-spark-1.6/19/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/carbondata-pr-spark-2.1/48/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2154/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2275/

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder/2276/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/carbondata-pr-spark-1.6/148/

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/carbondata-pr-spark-1.6/149/

LGTM


Value for memory in "Custom GPU and RAM Tweaks" is confusing

Hi, I just ran the script and I'm not sure what to choose at "[2] Custom GPU and RAM Tweaks' dialogue.
`What size of RAM do you have?

[1] 4GB
[2] 6GB
[3] 8GB
[4] 16GB
[5] 32GB
[6] 64GB
[7] Skip if Unsure
>`

I have 4GB of ram, so I typed 1. But the feedback is confusing:
`What size of RAM do you have?

[1] 4GB
[2] 6GB
[3] 8GB
[4] 16GB
[5] 32GB
[6] 64GB
[7] Skip if Unsure
> 1
The operation completed successfully.
Successfully applied tweak for 1GB RAM.
Press any key to continue . . .`

If I type 4, corresponding to 16 GB I get this:
What size of RAM do you have?

[1] 4GB
[2] 6GB
[3] 8GB
[4] 16GB
[5] 32GB
[6] 64GB
[7] Skip if Unsure
> 4
The operation completed successfully.
Successfully applied tweak for 4GB RAM.
Press any key to continue . . .

I'm not sure what should I choose.

The tweak was applied correctly based on your selection. However, there was a mistake in the feedback message, which displayed the option number instead of the actual RAM size. This issue has been fixed in the latest commit. Very grateful for the feedback


a field with empty Vector value gets omitted

steps
Make an object with a Vector field, serialize it to JSON.
problem
The field is omitted. For example, in the following example, "diagnostics": [] is missing.
JsonRpcNotificationMessage(2.0, textDocument/publishDiagnostics, {"uri":"file:/xxx/Hello.scala"})

The receiver of the message is not happy.
expectation
Empty fields are not omitted.
notes
This was an intentional design added in #6.
I think Option[A] can continue to elide.

https://github.com/eed3si9n/sjson-new/pull/72

Yea, I was wrong on this design decision. I still do think we need some way of evolving the JSON schema while remaining bincompat on Scala side. I'll go back to the drawing board.


Clean up ci and remove unnecessary examples

Purpose

To-do

Content

[ ] I have read and checked the items on the review checklist.

bors r+


Add attachments for Mouse Embryo wiki

@mkcor I am using the attachments folder under embryo to upload all attachments that we use in the Wiki. This makes it easier to link to images.

Good idea, @ana42742! Since the wiki pertains to the entire repo (as opposed to just the embryo project), I would actually have this attachment folder at the root (feel free to name it "fig" or "figs," but I don't mind "attachments").


articles crop before the end

I'm requesting articles over 800 words long, but the articles are cropping before the end.  I have a paying account in credit at openai so don't think that's the issue.  can provide creds privately if that helps.

A pull request has been created - https://github.com/wp-innovator/innovator-ai/pull/4
After merge the issue will be resolved.


feat: significantly improve root signature

Changes

...

Checklist

[x] Read the contribution guide and accept the code of conduct
[ ] Readme (updated or not needed)
[ ] Tests (added, updated or not needed)

Codecov Report

Merging #19 (ae5979f) into main (b20fb0e) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##              main       #19   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            1         1
  Lines            5         5
=========================================
  Hits             5         5


security-group.json file not getting created when we create a space using new cf-mgmt-config CLI

Describe the bug
A clear and concise description of what the bug is.
Failed to create security-group.json file when we try to create a space using new version of cf-mgmt.
cf-mgmt-config_latest_16_sep.exe space /config-dir:chdnp /org:nagaraju_test_org /space:test-space2 /enable-security-group:true /allow-ssh:true /enable-unassign-security-group:true
To Reproduce
Steps to reproduce the behavior:

Go to ' ..'
Click on '....'
Scroll down to '....'
See error

Try running the following command using latest CF-MGMT:
cf-mgmt-config.exe space /config-dir:cf-mgmt /org:nagaraju_test_org /space:test-space2 /enable-security-group:true /allow-ssh:true /enable-unassign-security-group:true
Expected behavior
A clear and concise description of what you expected to happen.
It should create space and create security-group.json file under the space along with the spaceConfig.yml file.
Screenshots
If applicable, add screenshots to help explain your problem.
Desktop (please complete the following information):

OS: Windows
Browser [e.g. chrome, safari] N/A
Version [Version: [1.0.34], Commit: [1516bac9999d68c8434a2cf5413098e35f4fd036]]

Smartphone (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

Released in https://github.com/pivotalservices/cf-mgmt/releases/tag/v1.0.37


Add BULL token

Official announcement:
BULL is the integration of decentralized finance and e-commerce, a symbiotic Internet for freedom and wealth
BULL echoes, circulates and balances existing mainstream Internet applications (such as Facebook, YouTube and WeChat), thus forming a strong internal structure at the early stage. Its internal financial balance, community promotion, business connection, value accumulation and network expansion will further improve the shortcomings of the centralized business model
BULL will be a symbiotic Internet for everybody. It supports the development of separate Web browsers, where each BULL address can be used as an anonymous IP address. In this open symbiotic network, all applications of the centralized Internet can be migrated. To create a new, decentralized ecosystem of Internet freedom through community efforts
Link: http://bulldex.org/
Project team background:
Bull team works in the world's top Internet companies, with rich experience and great influence. Own blockchain, good at e-commerce, online games, blockchain
Project basic information:
Bull combines Internet decentralized Finance
And decentralized e-commerce, symbiosis with internet giants. Bull will become the universal "symbiotic token" in the future decentralized Global Finance
Bull volume:
Total, 21 million bull.
21 million obtained by mining
1 million bull usage allocation table
51% Community feedback and construction
bull community promotion, ecological construction,
user reward and pass replacement
19% of the bull fund is invested in relevant digital ecosystems, philanthropy, and rewarding outstanding contributors.
The locking period was 12 months.
15% of the founding team,
the lock-in period is one year.
8% Strategic partner lock period 12 months
7% Private  lock for 6 months.
Media publications:
https://twitter.com/bulldextoken
https://www.facebook.com/dex.bull.33
https://t.me/bulldexofficialgroup
https://t.me/bulldextoken
Tradeable exchanges:
BIKI
UNISWAP
Recommended Gas Limit (For ERC-20 project teams) for transaction:
60000

为确保资料提交的真实性，请在贵方官网或其他经过认证的社交媒体渠道发布公告，并将此公告链接附于「官方公告」。推荐文案：
#imToken# #1636# 我们正在完善 XXX 在 imToken 中的代币相关资料。完成后，大家可以在 imToken 里看到 logo，更方便地管理 XXX，同时能看到更多代币信息。
注：

1636 为 pr 序号，如 https://github.com/consenlabs/token-profile/pull/1636 的序号为 1636，这是帮助 imToken 判断 pr 真实性的关键。
#imToken #1636 标签及其展示形式可自行调整。
若未提供「官方公告」，则无法显示代币信息。

「官方公告」

「官方公告」
http://bulldex.org/

We have published an announcement on the official website channel to help IMToken judge the authenticity of PR, our official website: http://bulldex.org

欢迎在社区中推荐用户使用 imToken 2.0 ，imToken 支持比特币, 以太坊, Comos, EOS, 波场, Nervos, 比特币现金, 莱特币，波卡等资产管理；同时支持去中心化币币兑换功能 Tokenlon；转账页面支持 ETH, USDT, EOS, BTC OTC 功能；另外对于没有 ETH 矿工费的用户，也提供 ETH 手续费充值功能。


Autofix heuristics for NoUnused.Parameters

Currently NoUnused.Parameters doesn't auto fix issues in named functions. The docs say:

We're only offering fixes for lambdas here because we believe unused parameters in functions are a code smell that should be refactored.

Unfortunately, neither the docs nor the error message really expand on the rationale here. So let me take a stab:
I think the idea here is that a better fix for this is not passing in the unused variable at call sites.
I'll proceed with the rest of this issue with this assumption.
Now whether this is true depends on a few situations. The first classification I think is to figure out if the callsite is a direct or indirect callsite.
A direct callsite is one where the function is called directly, typically in a fully applied fashion.
target a = 3

myFun a b =
  let

     foo = target a

  in
  doSomething foo b

An indirect callsite is one where the function is stored in a datastructure:

type alias Process =
   { start : Int
   , next : Int -> Int
   }

process1 : Process
process1 =
   { start = 0, next = target }

eval : Process -> Int
eval {start, next }
  next start

results = List.map eval [process1]

I think if we found all the callsites to be direct, then it would make sense to suggest an auto fix to remove the arguments at all of the callsites (and then other rules might cleanup those callsites, etc).
Indirect callsites complicate the picture, as we often need to evaluate all the possible arguments for each potential callsite can only really remove the argument iff all potential arguments for each potential callsite ignore that argument.
Now I'm not sure how feasible that analysis actually is. Finding direct callsites is straightforward, and I suppose it could be relatively straightforward to find clear cut cases (i.e. when a function is only ever referred to when being fully evaluated, that it is only called via direct callsites). The dificulty of finding all the indirect callsites would probably involve some flow analysis, which may well be untractable or even just impractical.

To summarise though, I think the most actionable idea here is to just add more auto fixes for named functions that only ever have direct callsites by eliminating the variable from both the signature and from all of the callsites.

Hey
I think this is a good idea :+1:
It's a lot of additional analysis but I think it's worth having.
There's currently a limitation in elm-review that fixes are for a single file only, meaning that we wouldn't be able to apply a fix to functions that are exposed.
I think we can and should focus on direct call sites, because indirect call sites seem a lot more complex to fix. So what I'm thinking is that we find that argument n°2 of a function is unused, then we look for all the places where we find that function. And if in all those places at least 2 arguments (including <| and |>), and remove that additional parameter (and eventual pipe).
But this would be quite a bit of work, especially considering that this rule IIRC does not currently do any work of that kind.

Additional thought: if the unused parameter is for a non-exposed function, then it makes sense to report the issue when analyzing the module, and trying to remove the argument in all the other call sites.
When the function is exposed however, it could make sense to delay the report until we've analyzed the rest of the project, to see whether we can automate removing the argument from all other call sites.
That said, this last piece doesn't make much sense until we have multi-file fixes.


records don't work for shit

the service class is awful, it does almost the exact same thing in each case but each of the cases is written out. i do not get this

will fix this later


Fix weird rotation when strapped to a bed

About the PR

Stops people being placed at a funny rotation when strapped to a bed.
Fixes #24563
Why / Balance

Bug fix.
Technical details

StrapComponent specifies an angle as an int in degrees, and RotationVisualizerSystem takes an Angle in radians. Now StrapComponent uses Angle too.
I know this will get stomped by the eventual buckle/vehicle refactor, but at least it'll be fixed for now.


module named ecto

Hi, im recently installed the software, when im tried to run it i got this error.
ImportError: No module named ecto
Ubuntu trusty 64bits.

Can you give more information? What commands did you run? Did you run into any installation errors?

Sorry, my mistake.

No worries, glad you got it fixed


[Diagnostics] Update existential type error message for clarity

Updating the redundant_any_in_existential error message by making it more explicit that the issue is the redundant any keyword.
Note: This is my first pull request as part of the Swift Mentorship.
@hborla I guess it's ready for review :)

@swift-ci please smoke test

@mazevedofs CI failure is because tests have to be updated in type/explicit_existential_swift6.swift as well =]

@mazevedofs CI failure is because tests have to be updated in type/explicit_existential_swift6.swift as well =]

@LucianoPAlmeida That's right! Is there a way to run this test locally so I can properly test it?

@LucianoPAlmeida That's right! Is there a way to run this test locally so I can properly test it?

Yes, we can use lit to run then locally against our ninja build. The exact commands are here in Running Tests section =]

@swift-ci Please test

Given that @hborla approved already, let's land it


Add-DbaAgDatabase Method Invocation Failure

Verified issue does not already exist?
Yes
What error did you receive?
PSMessageDetails      :
Exception             : System.Management.Automation.RuntimeException: Method invocation failed because [System.Object[]] does not contain a method
named 'op_Division'.
at System.Management.Automation.ParserOps.CallMethod(IScriptExtent errorPosition, Object target, String methodName,
PSMethodInvocationConstraints invocationConstraints, Object[] paramArray, Boolean callStatic, Object valueToSet)
at System.Management.Automation.ParserOps.ImplicitOp(Object lval, Object rval, String op, IScriptExtent errorPosition, String
errorOp)
at lambda_method(Closure , Object[] , StrongBox`1[] , InterpretedFrame )
TargetObject          : op_Division
CategoryInfo          : InvalidOperation: (op_Division:String) [], RuntimeException
FullyQualifiedErrorId : MethodNotFound
ErrorDetails          :
InvocationInfo        : System.Management.Automation.InvocationInfo
ScriptStackTrace      : at Add-DbaAgDatabase, C:\Program Files\WindowsPowerShell\Modules\dbatools\1.1.22\allcommands.ps1: line 350
at , : line 1
PipelineIterationInfo : {}
Steps to Reproduce
Ran the following:
Add-DbaAgDatabase -SqlInstance Instance1 -Secondary Instance2 -AvailabilityGroup AGName -Database DBName
-SeedingMode Automatic
Are you running the latest release?
Yes
Other details or mentions
No response
What PowerShell host was used when producing this error
Windows PowerShell ISE (powershell_ise.exe)
PowerShell Host Version
5.1.14393.4583
SQL Server Edition and Build number
Microsoft SQL Server 2019 (RTM-CU12) (KB5004524) - 15.0.4153.1 (X64)   Jul 19 2021 15:37:34   Copyright (C) 2019 Microsoft Corporation  Enterprise Edition: Core-based Licensing (64-bit) on Windows Server 2019 Datacenter 10.0  (Build 17763: ) (Hypervisor)
.NET Framework Version
.NET Framework 4.8.03761

Thanks for reporting, will have a look.

For a workaround, you can disable the reporting of the seeding operation with:
Set-DbatoolsConfig -FullName commands.add-dbaagdatabase.report.seeding -Value $false


TST: Add coverage to testing pipeline

Change Summary
This adds code coverage checks to our testing pipeline. I'm not sure if codecov is currently running on the org, or if we need to add it to this repo explicitly. We'll see once the PR is opened.
New Dependencies
pytest-cov to run code coverage through pytest

Does this only run code coverage in the testing pipeline? I don't generally love code coverage as any kind of commit blocker, but just having a report and a percentage goal to aim for is alright with me. Is there some easier way to view the report than that link in the testing details page?

Does this only run code coverage in the testing pipeline?

Yes, it only runs it in CI. We could add it locally as well by setting default options for when we invoke pytest, but I generally invoke it manually if I'm curious: pytest --cov

I don't generally love code coverage as any kind of commit blocker, but just having a report and a percentage goal to aim for is alright with me.

I agree that it being a blocker is generally not good. However, I think it is quite valuable for reviewers to know whether the PR has added the proper tests for their portion of the code. I like the idea of adding a percentage target to your PR review guidelines and leaving these as "status" but not blockers for merging. (I do think we should strive for 100% coverage on our algorithms if possible though...)

Is there some easier way to view the report than that link in the testing details page?

We have it on our sds-data-manager repo, see for example this PR: https://github.com/IMAP-Science-Operations-Center/sds-data-manager/pull/151 If you click on the show checks, then you'll see the codecov information that you can click and link out to.

Ok, that all sounds good!


mwc-top-app-bar-fixed ??

Hi,
why this component ? instead of an attribute on mwc-top-app-bar. Any technical reason ?
Thanks in advance for explanation

The reason is mostly around the idea that anything attribute based must be dynamic, and the "scrolling" and "fixed" top app bar variants require switching out Foundation controllers: https://github.com/material-components/material-components-web-components/blob/bb1ad7f281bc10b2820b71b20a7c09707037c266/packages/top-app-bar/src/mwc-top-app-bar-base.ts#L31-L37
https://github.com/material-components/material-components-web-components/blob/bb1ad7f281bc10b2820b71b20a7c09707037c266/packages/top-app-bar/src/mwc-top-app-bar-base.ts#L129-L135
It seemed more likely that the top app bar behavior is going to remain the same for an individual bar, rather than switching back and forth.
If you have use cases where you need to be able to switch between a "scrolling" and "fixed" top app bar, I'd be open to merging them back together.

Hi @azakus , thanks for explanation.
I understand the fact an attribute should be dynamic but it looks like a technical constraint create this component. I'm not a fan at first glance and still not.
Is this use case are matching the fact fixed could be an attribute:
https://codepen.io/JGallardo/pen/lJoyk
Regards,

If you have use cases where you need to be able to switch between a "scrolling" and "fixed" top app bar, I'd be open to merging them back together.

This would come in handy for extra screen real-estate according to the user's device size.
For example, switching to "scrolled" for mobile (where screen real-estate is limited), then back to "fixed" for desktop.

@taylor-vann please reopen the issue. I have same use case as @Sebastianhex


updates for file handler docs

Updates to the documentation for file handlers with updated registration instructions, index wording changes, and updates on resetting the cache.

Docs Build status updates of commit c647094:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/file-handlers/index.md
:warning:Warning
View (>= odsp-graph-online)
Details

docs/file-handlers/register-manually.md
:warning:Warning
View (>= odsp-graph-online)
Details

docs/file-handlers/reset-cache.md
:warning:Warning
View (>= odsp-graph-online)
Details

docs/file-handlers/index.md

Line 3, Column 12: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'rgregg' is not a valid Microsoft alias.
Line 149, Column 1: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-authentication-scenarios' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 150, Column 1: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-v2-protocols-oidc' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs/file-handlers/register-manually.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 3, Column 12: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'rgregg' is not a valid Microsoft alias.
Line 42, Column 1: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/active-directory/develop/reference-app-manifest' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 92, Column 1: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/databricks/dev-tools/api/latest/aad/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs/file-handlers/reset-cache.md

Line 3, Column 12: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'rgregg' is not a valid Microsoft alias.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 4f0c7d3:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/file-handlers/index.md
:warning:Warning
View (>= odsp-graph-online)
Details

docs/file-handlers/register-manually.md
:warning:Warning
View (>= odsp-graph-online)
Details

docs/file-handlers/reset-cache.md
:warning:Warning
View (>= odsp-graph-online)
Details

docs/file-handlers/index.md

Line 3, Column 12: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'rgregg' is not a valid Microsoft alias.
Line 149, Column 1: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-authentication-scenarios' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 150, Column 1: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-v2-protocols-oidc' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs/file-handlers/register-manually.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 3, Column 12: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'rgregg' is not a valid Microsoft alias.
Line 42, Column 1: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/active-directory/develop/reference-app-manifest' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 92, Column 1: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/databricks/dev-tools/api/latest/aad/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs/file-handlers/reset-cache.md

Line 3, Column 12: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'rgregg' is not a valid Microsoft alias.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 6fdf366:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/file-handlers/index.md
:warning:Warning
View (>= odsp-graph-online)
Details

docs/file-handlers/register-manually.md
:warning:Warning
View (>= odsp-graph-online)
Details

docs/file-handlers/reset-cache.md
:warning:Warning
View (>= odsp-graph-online)
Details

docs/file-handlers/index.md

Line 3, Column 12: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'rgregg' is not a valid Microsoft alias.
Line 149, Column 1: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-authentication-scenarios' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 150, Column 1: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-v2-protocols-oidc' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs/file-handlers/register-manually.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 3, Column 12: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'rgregg' is not a valid Microsoft alias.
Line 42, Column 1: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/active-directory/develop/reference-app-manifest' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 92, Column 1: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/databricks/dev-tools/api/latest/aad/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs/file-handlers/reset-cache.md

Line 3, Column 12: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'rgregg' is not a valid Microsoft alias.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit 425ffae:
:warning: Validation status: warnings

File
Status
Preview URL
Details

docs/file-handlers/index.md
:warning:Warning
View (>= odsp-graph-online)
Details

docs/file-handlers/register-manually.md
:warning:Warning
View (>= odsp-graph-online)
Details

docs/file-handlers/reset-cache.md
:warning:Warning
View (>= odsp-graph-online)
Details

docs/file-handlers/index.md

Line 3, Column 12: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'rgregg' is not a valid Microsoft alias.
Line 149, Column 1: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-authentication-scenarios' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 150, Column 1: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/active-directory/develop/active-directory-v2-protocols-oidc' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs/file-handlers/register-manually.md

Line 2, Column 1: [Warning-title-missing] Missing required attribute: 'title'. Add a title string to show in search engine results.
Line 3, Column 12: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'rgregg' is not a valid Microsoft alias.
Line 42, Column 1: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/active-directory/develop/reference-app-manifest' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 92, Column 1: [Warning-hard-coded-locale] Link 'https://docs.microsoft.com/en-us/azure/databricks/dev-tools/api/latest/aad/' contains locale code 'en-us'. For localizability, remove 'en-us' from links to most Microsoft sites.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

docs/file-handlers/reset-cache.md

Line 3, Column 12: [Warning-ms-author-invalid] Invalid value for 'ms.author', 'rgregg' is not a valid Microsoft alias.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


Releases/v0.3.0

Updates

update: Improve example app appearance + misc updates (#14)

Breaking

breaking: Rename enum values of PlaybackMaxResolution to UP_TO_720p, UP_TO_1080p, etc

Co-authored-by: Emily Dixon<EMAIL_ADDRESS>Co-authored-by: GitHub<EMAIL_ADDRESS>

API changes are still incoming based on our other work. This can be reopened when we're really ready to ship