NeoFSBlockFetcher may seem hanging

with NeoFSBlockFetcher address set to ssl neogo silentlty doesn't work
steps to reproduce:
NeoFSBlockFetcher:
  Addresses:
    - st1.storage.fs.neo.org:443
    - st2.storage.fs.neo.org:443
    - st3.storage.fs.neo.org:443
    - st4.storage.fs.neo.org:443

log:
INFO        starting NeoFS BlockFetcher service

neogo silentlty doesn't work

It works. BlockFetcher is trying to deal, and we have a relatively large deal timeout, so the error will be returned after timeout.

deal timeout is not an answer, as reply happens instantly:
% curl -v http://st1.storage.fs.neo.org:443
* Host st1.storage.fs.neo.org:443 was resolved.
* IPv6: (none)
* IPv4: <IP_ADDRESS>
*   Trying <IP_ADDRESS>:443...
* Connected to st1.storage.fs.neo.org (<IP_ADDRESS>) port 443
* using HTTP/1.x
> GET / HTTP/1.1
> Host: st1.storage.fs.neo.org:443
> User-Agent: curl/8.11.0
> Accept: */*
>
* Request completely sent off
< HTTP/1.1 400 Bad Request
< Server: nginx
< Date: Wed, 04 Dec 2024 14:50:10 GMT
< Content-Type: text/html
< Content-Length: 248
< Connection: close
< Strict-Transport-Security: max-age=63072000; includeSubDomains
< X-Content-Type-Options: nosniff
< X-Frame-Options: SAMEORIGIN
<

<title>400 The plain HTTP request was sent to HTTPS port</title>

400 Bad Request

The plain HTTP request was sent to HTTPS port

nginx

* shutting down connection #0

@cthulhu-rider probably knows something about it, I don't think it can be fixed with current SDK.

The problem is not on the NeoGo side. pool.Dial returns only after n*DealTimeout seconds where n is the number of nodes in the pool, so the problem is related to the pool itself.  The following code is responsible for initial pool dealing on the NeoGo side:
https://github.com/nspcc-dev/neo-go/blob/8952922c4d4f4474e390cf3afa4abcdf20c7960d/pkg/services/blockfetcher/blockfetcher.go#L202-L204
The result is (with smaller dial timeout):
2024-12-04T16:22:52.244+0300	INFO	starting NeoFS BlockFetcher service
2024-12-04T16:22:53.255+0300	INFO	persisted to disk	{"blocks": 0, "keys": 116, "headerHeight": 0, "blockHeight": 0, "took": "12.85244ms"}
2024-12-04T16:25:52.248+0300	ERROR	skipping NeoFS BlockFetcher	{"error": "failed to dial NeoFS pool: at least one node must be healthy"}

So @532910 you may submit an issue to the NeoFS SDK repo.

@cthulhu-rider probably knows something about it, I don't think it can be fixed with current (as in version used by NeoGo) SDK.

the behavior is the same in the latest SDK. The error we receive from gRPC layer is
open gRPC connection: gRPC dial: context deadline exceeded: connection error: desc = "error reading server preface: http2: frame too large"

and gRPC dialer considers reading server preface as a temporary error: it tries again until the deadline arrives
in opposite, NeoFS connection fails immediately on non-temporary failures. For example, both single client and pool return immediately if we set ports to 444:
gRPC dial: connection error: desc = "transport: error while dialing: dial tcp <IP_ADDRESS>:444: connect: connection refused"

@AnnaShaleva is right that pool's dial timeout sums all the client ones. And yeah, everything that can be improved in this area is located in the NeoFS SDK

% journalctl -n1 -u neogo-morph-rpc
Dec 06 14:36:14 tenes4 neogo-morph-rpc[446809]: INFO        starting NeoFS BlockFetcher service
% date
Fri  6 Dec 17:09:18 UTC 2024


Fatal error Uncaught Exception

[ ] I've read the guidelines for Contributing to Roots Projects
[ ] This request isn't a duplicate of an existing issue
[ ] I've read the docs and followed them (if applicable)
[ ] This is not a personal support request that should be posted on the Roots Discourse community

Description
[Description of the issue]
Fatal error: Uncaught Exception: The /current/web/app/themes/sage-10/public directory must be present. in /current/web/app/themes/sage-10/vendor/roots/acorn/src/Roots/Acorn/Application.php:124 Stack trace:
#0 /current/web/app/themes/sage-10/vendor/roots/acorn/src/Roots/Acorn/Bootloader.php(206): Roots\Acorn\Application->usePaths(Array)
#1 /current/web/app/themes/sage-10/vendor/roots/acorn/src/Roots/Acorn/Bootloader.php(181): Roots\Acorn\Bootloader->app()
#2 /current/web/wp/wp-includes/class-wp-hook.php(303): Roots\Acorn\Bootloader->__invoke('') #3 /current/web/wp/wp-includes/class-wp-hook.php(327): WP_Hook->apply_filters(NULL, Array)
#4 /current/web/wp/wp-includes/plugin.php(470): WP_Hook->do_action(Array)
#5 /current/web/wp/wp-settings.php(556): do_action('after_setup_the...')
#6 /current/web/wp-config.php(9): require_once('/srv/www/re in /current/web/app/themes/sage-10/vendor/roots/acorn/src/Roots/Acorn/Application.php on line 124
Steps to reproduce

[First step]
[Second step]
[and so on...]

Expected behavior: [What you expect to happen]
Actual behavior: [What actually happens]
Reproduces how often: [What percentage of the time does it reproduce?]
Versions
You can get this information from referencing CHANGELOG.md. Also, please include the OS and what version of the OS you're running.
Additional information
Any additional information, configuration or data that might be necessary to reproduce the issue.

instead of deciding to not read or fill out the issue template, please use it next time, since you would have already seen this.
dupe #2852


2.0.0-rc0 cherry-pick request: Only add ModuleWrapper when lazy loading is requested or when using TF 1.x (to print deprecation warnings).

That is, don't use TFModuleWrapper in r2.0 builds. We don't need to print deprecation warnings since deprecated 1.x symbols are already removed and we don't use lazy loading by default.

Windows build is breaking with this change. I will update this PR with a few more changes before merging.

I included changes from these other commits to get it to build:
https://github.com/tensorflow/tensorflow/commit/d82a2bbf8a0ead6d7298e652f7d4e057ca8fd83d#diff-62ec18ff8bdd93adaff55160f27a7e09
https://github.com/tensorflow/tensorflow/commit/b7db3f4ae43f5228952f3a1bb480a3e52a2006ed#diff-15bdff9a63024759f88313469be4b11f
https://github.com/tensorflow/tensorflow/commit/18c2cf989a2263ee212fbd5ac0b3085d9450b80a#diff-15bdff9a63024759f88313469be4b11f
Please take another look.


Support rust_decimal

Re: https://github.com/SoftbearStudios/bitcode/issues/37#issuecomment-2362255748
@l-7-l opening this dedicated issue!


Selective Time of Day

Is it possible to use groups to add Time of Day to one Group but not another

Sorry, but there is no possibility right now.

That's a bummer. But not a big deal. Just was thinking how cool it would be to have different formats for different groups.


luci-base: fix regression add by button-row class

This should fix the regression that was introduced by https://github.com/openwrt/luci/pull/7153

[x] Each commit has a valid :black_nib: Signed-off-by<EMAIL_ADDRESS>row (via git commit --signoff)
[x] Each commit and PR title has a valid :memo: <package name>: title first line subject for packages
[x] ( Preferred ) Mention: @jow-
[x] Description: (describe the changes proposed in this PR)

@systemcrash @dannil @zdz2019  All the problems mentioned should be solved with this PR.

Problem resolved, hope to merge soon.
By the way, would it be better if these two buttons were swapped?


[FLINK-24351][docs] Translate "JSON Function" pages into Chinese

What is the purpose of the change
(For example: This pull request makes task deployment go through the blob server, rather than through RPC. That way we avoid re-transferring them on each deployment (during recovery).)
Brief change log
(for example:)

The TaskInfo is stored in the blob store on job creation time as a persistent artifact
Deployments RPC transmits only the blob storage reference
TaskManagers retrieve the TaskInfo from the blob cache

Verifying this change
(Please pick either of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added integration tests for end-to-end deployment with large payloads (100MB)
Extended integration test for recovery after master (JobManager) failure
Added test that validates that TaskInfo is transferred only once across recoveries
Manually verified the change by running a 4 node cluser with 2 JobManagers and 4 TaskManagers, a stateful streaming program, and killing one JobManager and two TaskManagers during the execution, verifying that recovery happens correctly.

Does this pull request potentially affect one of the following parts:

Dependencies (does it add or upgrade a dependency): (yes / no)
The public API, i.e., is any changed class annotated with @Public(Evolving): (yes / no)
The serializers: (yes / no / don't know)
The runtime per-record code paths (performance sensitive): (yes / no / don't know)
Anything that affects deployment or recovery: JobManager (and its components), Checkpointing, Kubernetes/Yarn, ZooKeeper: (yes / no / don't know)
The S3 file system connector: (yes / no / don't know)

Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)

@MonsterChenzhuo Maybe you should rebase from latest master branch for your branch and resolve the conflicting file before next review .

@MonsterChenzhuo 感谢您的更新。 也许你应该从最新的 master 分支为你的分支 rebase 并在下次审查之前解决冲突的文件。
@RocMarshal  I'm really sorry for the recent delay. I will deal with it as soon as possible tomorrow

@RocMarshal https://github.com/apache/flink/pull/17789   Please check it again. I was delayed by something at home

@RocMarshal #17789 Please check it again. I was delayed by something at home

Excuse me, please let me know why did you switch the pr to #17789 instead of keeping it currently?

@RocMarshal Sorry for the trouble,I'm new to Github and it's not very clear how it works, which led to a previous shutdown and the creation of a new PR.Now I know I can submit multiple times on a PR.

@RocMarshal Sorry for the trouble,I'm new to Github and it's not very clear how it works, which led to a previous shutdown and the creation of a new PR.Now I know I can submit multiple times on a PR.

Take it easy. If you have any questions, you could discuss its on the email or in the pr.
So, if you are willing to advance the jira in the new pr,  I'll do the review based on the new one.
If you still use this pr page, may be you could rebase the latest master branch in your pr-branch and push it forced to your remote pr-branch.

@RocMarshal Please go to #17789 to review


add a send stream test that randomly acknowledges and loses data

In an attempt to find the race condition of #2533 I wrote this test. Turns out that the race condition is not caused by handling of lost frames in the stream.

Codecov Report

Merging #2535 into master will increase coverage by 0.03%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #2535      +/-   ##
==========================================
+ Coverage   86.12%   86.16%   +0.03%
==========================================
  Files         122      122
  Lines        9542     9542
==========================================
+ Hits         8218     8221       +3
+ Misses        985      983       -2
+ Partials      339      338       -1

Impacted Files
Coverage Δ

send_stream.go
93.36% <0.00%> (+0.37%)
:arrow_up:

server.go
83.59% <0.00%> (+0.61%)
:arrow_up:

Continue to review full report at Codecov.

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


Allow for Django user attribute validation.

PasswordSerializer is sending AnonymousUser to the validate_password function because it first grabs the user from the self.context["request"] and this will always be populated with at least AnonymousUser.  In a password reset situation we want to validate the password against the user from the token or self.user of the serializer.  This is specifically important when using django.contrib.auth.password_validation.UserAttributeSimilarityValidator.
Fix is in pull request #434

Any updates regarding this? Will this be fixed?


This error drive me crazy I just use a uploader as middleware and keep getting this error please help

CLI options definitions were upgraded with "type" property (which could be one of "string", "boolean", "multiple"). Below listed plugins do not predefine type for introduced options:

ServerlessDynamodbLocal for "seed"

By the way, I don't use any seed option even I set seed to false this error is still showing
serverless-dynamodb:
port: 8000
docker: false
start:
migrate: true
seed: false

Duplicate of #24


uniq with an iteratee is uniqBy

The wrong version of the function was being used which was resulting in flow errors.
See https://lodash.com/docs/4.17.4#uniqBy for reference.
Test Plan
There should probably be a test for this. According to the lodash source, calling uniq with a second argument is not supported.
Flow correctly picks up on this, and is causing errors in my project.

I believe we merged similar PR a couple of weeks ago 🤔

Just found it. Seems we already have a PR that has been opened for a while (26 days). I don't want to discourage you, but I would prefer merging it that PR as far as it was the first one and we already reviewed it. Thanks for pointing out that we didn't merge it yet (in my mind we did haha)!
Hope to see more contributions from you in the future!

That's all good, just want to get it merged :)


[Dropbox] ERROR: unable to download video data: HTTP Error 403: Forbidden

I'm not sure if this situation goes in this area, as this is my first time using this platform. I'm not tech savvy at all. This is a challenge for those who are. Whoever can find a way to download a Dropbox video when the download button is disabled, you are a genius. Please find a way to bypass the disabled download button so people can download the original videos.

I'm having the same issue :(


GH-4968: server-spring - Close query result on pre-render exception

GitHub issue resolved: #4968
Briefly describe the changes proposed in this PR:

Introduce explicit result closing (in addition to existing repo close) when an exception occurs between the evaluation & rendering stages.
:information_source: I have not added any tests yet since I'd like to get feedback on whether this is the right approach (and there weren't any other pre-existing tests for the AbstractQueryRequestHandler class.

PR Author Checklist (see the contributor guidelines for more details):

[x] my pull request is self-contained
[ ] I've added tests for the changes I made
[x] I've applied code formatting (you can use mvn process-resources to format from the command line)
[x] I've squashed my commits where necessary
[x] every commit message starts with the issue number (GH-xxxx) followed by a meaningful description of the change

It looks like the integration test failure is unrelated (in that this from my understanding doesn't use server-spring):
testsuites/repository/src/main/java/org/eclipse/rdf4j/testsuite/repository/optimistic/ModificationTest.java:180 | Malformed query result from server

I'm rerunning that GitHub action to see if it is just temperamental. I haven't seen it being flaky before though.

Test is still failing. I suspect it's related to the Boolean query changes you've introduced. I added a proposal to your code for a simple instanceOf AutoCloseable check instead.

I just realised that I'm probably doing the whole "add more commits during review" thing wrong: Internally we use !fixup commits and once the review is complete - we do a git rebase --auto-squash to push everything together.
What's your preference?

Add extra commits (but history looks strange like e.g. here where I e.g undid some changes)
Force-push to replace the existing commit(s) with updated versions
Something else?

Squashed

Ah wait - should the target branch also be develop instead of main? (like with the other PR I submitted)


[FEATURE REQUEST] GUI improvements

Run SELECT * FROM Table LIMIT 1000 on table click
Show/Hide SQL query field
Inline table editor
Sort tables on header click

@a2nt would you like to contribute for those improvements?

@krolow

I think is not the best default as some tables might contain a lot of rows, and react is not good in render a lot of items
Well, I mean run select query on click

Inline table editor
It will be nice to edit data fields on double-click. The same way as PhpMyAdmin and Sequel Pro does.
So after editing UPDATE + SELECT query will be made.

You mean sort only the elements that are visible in the current query, or actually change the query when click in one row?
Query needs to be changed


CircularMemoryLogger start -- might freeze

Due to some technical difficulties I cannot provide a screen shot.
Can someone confirm that
CircularMemoryLogger start

when inspected in a playground does not freeze after say about 10 seconds? It is easier to observe using the Grouped tab on the inspector.
I am observing that it seems to freeze after about ten seconds.
v0.8.487
18.04 in cloud with newer libstdc++ that satisfies libSkia.so

@girba has confirmed this, and suspects a refresh issue, as discussed in discord. I trust that the GT team will repair this following their customary work processes. Feel free to close this issue or use it for tracking, as you see fit.


gyp ERR! configure error

Possible install-time or require-time problem

[x] I have read the documentation relating to installation.
[x] I have ensured that the architecture and platform of Node.js used for npm install is the same as the architecture and platform of Node.js used at runtime.

Are you using the latest version of sharp?

[ x] I am using the latest version of sharp as reported by npm view sharp dist-tags.latest.

If you cannot confirm this, please upgrade to the latest version and try again before opening an issue.
If you are using another package which depends on a version of sharp that is not the latest, please open an issue against that package instead.
Is this a problem with filesystem permissions?
If you are using npm v6 or earlier and installing as a root or sudo user, have you tried with the npm install --unsafe-perm flag?
If you are using npm v7 or later, does the user running npm install own the directory it is run in?
If you are using the ignore-scripts feature of npm, have you tried with the npm install --ignore-scripts=false flag?
What is the complete output of running npm install --verbose --foreground-scripts sharp in an empty directory?

npm verb cli [
npm verb cli   '/Users/kareljanvanhaute/.nvm/versions/node/v16.15.0/bin/node',
npm verb cli   '/Users/kareljanvanhaute/.nvm/versions/node/v16.15.0/bin/npm',
npm verb cli   'install',
npm verb cli   '--verbose',
npm verb cli   '--foreground-scripts',
npm verb cli   'sharp'
npm verb cli ]
npm info using<EMAIL_ADDRESS>npm info using<EMAIL_ADDRESS>npm timing npm:load:whichnode Completed in 0ms
npm timing config:load:defaults Completed in 1ms
npm timing config:load:file:/Users/kareljanvanhaute/.nvm/versions/node/v16.15.0/lib/node_modules/npm/npmrc Completed in 0ms
npm timing config:load:builtin Completed in 0ms
npm timing config:load:cli Completed in 1ms
npm timing config:load:env Completed in 0ms
npm timing config:load:file:/Volumes/External/TMP/BASWEB/.npmrc Completed in 0ms
npm timing config:load:project Completed in 1ms
npm timing config:load:file:/Users/kareljanvanhaute/.npmrc Completed in 1ms
npm timing config:load:user Completed in 1ms
npm timing config:load:file:/Users/kareljanvanhaute/.nvm/versions/node/v16.15.0/etc/npmrc Completed in 0ms
npm timing config:load:global Completed in 0ms
npm timing config:load:validate Completed in 0ms
npm timing config:load:credentials Completed in 0ms
npm timing config:load:setEnvs Completed in 1ms
npm timing config:load Completed in 5ms
npm timing npm:load:configload Completed in 5ms
npm timing npm:load:setTitle Completed in 5ms
npm timing config:load:flatten Completed in 1ms
npm timing npm:load:display Completed in 3ms
npm verb logfile /Users/kareljanvanhaute/.npm/_logs/2022-05-10T14_03_06_651Z-debug-0.log
npm timing npm:load:logFile Completed in 2ms
npm timing npm:load:timers Completed in 0ms
npm timing npm:load:configScope Completed in 0ms
npm timing npm:load Completed in 15ms
npm timing arborist:ctor Completed in 0ms
npm timing arborist:ctor Completed in 0ms
npm timing idealTree:init Completed in 4ms
npm timing idealTree:userRequests Completed in 1ms
npm http fetch GET 200 https://registry.npmjs.org/sharp 148ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/color 58ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/tar-fs 90ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/simple-get 108ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/node-addon-api 109ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/prebuild-install 112ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/tunnel-agent 118ms (cache updated)
npm http fetch GET 200 https://registry.npmjs.org/semver 119ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/detect-libc 167ms (cache revalidated)
npm timing idealTree:#root Completed in 321ms
npm http fetch GET 200 https://registry.npmjs.org/minimist 53ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/simple-concat 52ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/mkdirp-classic 60ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/github-from-package 62ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/color-convert 67ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/rc 66ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/decompress-response 67ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/node-abi 71ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/tar-stream 81ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/chownr 101ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/safe-buffer 100ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/pump 108ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/once 113ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/color-string 117ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/lru-cache 116ms (cache updated)
npm http fetch GET 200 https://registry.npmjs.org/napi-build-utils 120ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/expand-template 121ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/npmlog 120ms (cache updated)
npm timing idealTree:node_modules/sharp Completed in 133ms
npm http fetch GET 200 https://registry.npmjs.org/simple-swizzle 40ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/color-name 51ms (cache revalidated)
npm timing idealTree:node_modules/color Completed in 52ms
npm timing idealTree:node_modules/color-convert Completed in 1ms
npm timing idealTree:node_modules/color-name Completed in 0ms
npm http fetch GET 200 https://registry.npmjs.org/is-arrayish 38ms (cache revalidated)
npm timing idealTree:node_modules/color-string Completed in 39ms
npm timing idealTree:node_modules/detect-libc Completed in 0ms
npm timing idealTree:node_modules/node-addon-api Completed in 0ms
npm http fetch GET 200 https://registry.npmjs.org/console-control-strings 39ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/deep-extend 39ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/strip-json-comments 44ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/are-we-there-yet 47ms (cache updated)
npm http fetch GET 200 https://registry.npmjs.org/set-blocking 53ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/end-of-stream 54ms (cache updated)
npm http fetch GET 200 https://registry.npmjs.org/ini 54ms (cache updated)
npm http fetch GET 200 https://registry.npmjs.org/gauge 75ms (cache updated)
npm timing idealTree:node_modules/prebuild-install Completed in 81ms
npm timing idealTree:node_modules/expand-template Completed in 0ms
npm timing idealTree:node_modules/github-from-package Completed in 0ms
npm timing idealTree:node_modules/minimist Completed in 0ms
npm timing idealTree:node_modules/mkdirp-classic Completed in 0ms
npm timing idealTree:node_modules/napi-build-utils Completed in 0ms
npm timing idealTree:node_modules/node-abi Completed in 0ms
npm http fetch GET 200 https://registry.npmjs.org/signal-exit 44ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/aproba 45ms (cache updated)
npm http fetch GET 200 https://registry.npmjs.org/readable-stream 47ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/delegates 50ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/strip-ansi 49ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/object-assign 53ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/string-width 53ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/has-unicode 58ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/wide-align 58ms (cache revalidated)
npm timing idealTree:node_modules/npmlog Completed in 63ms
npm http fetch GET 200 https://registry.npmjs.org/process-nextick-args 47ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/core-util-is 48ms (cache updated)
npm http fetch GET 200 https://registry.npmjs.org/isarray 59ms (cache updated)
npm http fetch GET 200 https://registry.npmjs.org/inherits 61ms (cache updated)
npm http fetch GET 200 https://registry.npmjs.org/util-deprecate 63ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/string_decoder 85ms (cache revalidated)
npm timing idealTree:node_modules/are-we-there-yet Completed in 87ms
npm timing idealTree:node_modules/console-control-strings Completed in 0ms
npm timing idealTree:node_modules/delegates Completed in 0ms
npm http fetch GET 200 https://registry.npmjs.org/ansi-regex 57ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/is-fullwidth-code-point 61ms (cache updated)
npm http fetch GET 200 https://registry.npmjs.org/code-point-at 61ms (cache updated)
npm timing idealTree:node_modules/gauge Completed in 65ms
npm timing idealTree:node_modules/aproba Completed in 0ms
npm timing idealTree:node_modules/has-unicode Completed in 0ms
npm timing idealTree:node_modules/object-assign Completed in 0ms
npm http fetch GET 200 https://registry.npmjs.org/wrappy 62ms (cache revalidated)
npm timing idealTree:node_modules/pump Completed in 64ms
npm timing idealTree:node_modules/end-of-stream Completed in 0ms
npm timing idealTree:node_modules/once Completed in 1ms
npm timing idealTree:node_modules/rc Completed in 1ms
npm timing idealTree:node_modules/deep-extend Completed in 0ms
npm timing idealTree:node_modules/ini Completed in 0ms
npm timing idealTree:node_modules/readable-stream Completed in 3ms
npm timing idealTree:node_modules/core-util-is Completed in 0ms
npm timing idealTree:node_modules/inherits Completed in 0ms
npm timing idealTree:node_modules/isarray Completed in 0ms
npm timing idealTree:node_modules/process-nextick-args Completed in 0ms
npm timing idealTree:node_modules/safe-buffer Completed in 0ms
npm http fetch GET 200 https://registry.npmjs.org/yallist 53ms (cache revalidated)
npm timing idealTree:node_modules/semver Completed in 55ms
npm timing idealTree:node_modules/lru-cache Completed in 1ms
npm timing idealTree:node_modules/set-blocking Completed in 0ms
npm timing idealTree:node_modules/signal-exit Completed in 0ms
npm http fetch GET 200 https://registry.npmjs.org/mimic-response 65ms (cache revalidated)
npm timing idealTree:node_modules/simple-get Completed in 66ms
npm timing idealTree:node_modules/decompress-response Completed in 1ms
npm timing idealTree:node_modules/mimic-response Completed in 0ms
npm timing idealTree:node_modules/simple-concat Completed in 0ms
npm timing idealTree:node_modules/simple-swizzle Completed in 1ms
npm timing idealTree:node_modules/is-arrayish Completed in 0ms
npm timing idealTree:node_modules/string_decoder Completed in 0ms
npm http fetch GET 200 https://registry.npmjs.org/number-is-nan 48ms (cache revalidated)
npm timing idealTree:node_modules/string-width Completed in 52ms
npm timing idealTree:node_modules/code-point-at Completed in 0ms
npm timing idealTree:node_modules/is-fullwidth-code-point Completed in 2ms
npm timing idealTree:node_modules/number-is-nan Completed in 0ms
npm timing idealTree:node_modules/strip-ansi Completed in 0ms
npm timing idealTree:node_modules/ansi-regex Completed in 0ms
npm timing idealTree:node_modules/strip-json-comments Completed in 0ms
npm http fetch GET 200 https://registry.npmjs.org/bl 49ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/fs-constants 60ms (cache miss)
npm timing idealTree:node_modules/tar-fs Completed in 63ms
npm timing idealTree:node_modules/chownr Completed in 0ms
npm http fetch GET 200 https://registry.npmjs.org/buffer 57ms (cache revalidated)
npm timing idealTree:node_modules/tar-stream Completed in 62ms
npm http fetch GET 200 https://registry.npmjs.org/base64-js 38ms (cache revalidated)
npm http fetch GET 200 https://registry.npmjs.org/ieee754 54ms (cache updated)
npm timing idealTree:node_modules/bl Completed in 57ms
npm timing idealTree:node_modules/buffer Completed in 1ms
npm timing idealTree:node_modules/base64-js Completed in 0ms
npm timing idealTree:node_modules/fs-constants Completed in 0ms
npm timing idealTree:node_modules/ieee754 Completed in 0ms
npm timing idealTree:node_modules/tunnel-agent Completed in 0ms
npm timing idealTree:node_modules/util-deprecate Completed in 0ms
npm timing idealTree:node_modules/wide-align Completed in 0ms
npm timing idealTree:node_modules/wrappy Completed in 0ms
npm timing idealTree:node_modules/yallist Completed in 0ms
npm timing idealTree:node_modules/bl/node_modules/readable-stream Completed in 0ms
npm timing idealTree:node_modules/tar-stream/node_modules/readable-stream Completed in 0ms
npm timing idealTree:buildDeps Completed in 1280ms
npm timing idealTree:fixDepFlags Completed in 1ms
npm timing idealTree Completed in 1287ms
npm timing reify:loadTrees Completed in 1288ms
npm timing reify:diffTrees Completed in 1ms
npm timing reify:retireShallow Completed in 0ms
npm timing reify:createSparse Completed in 5ms
npm timing reify:loadBundles Completed in 0ms
npm timing reifyNode:node_modules/is-fullwidth-code-point Completed in 73ms
npm timing reifyNode:node_modules/ansi-regex Completed in 73ms
npm timing reifyNode:node_modules/chownr Completed in 74ms
npm timing reifyNode:node_modules/code-point-at Completed in 74ms
npm timing reifyNode:node_modules/process-nextick-args Completed in 73ms
npm timing reifyNode:node_modules/strip-json-comments Completed in 73ms
npm timing reifyNode:node_modules/once Completed in 73ms
npm timing reifyNode:node_modules/strip-ansi Completed in 73ms
npm timing reifyNode:node_modules/wrappy Completed in 73ms
npm timing reifyNode:node_modules/string-width Completed in 74ms
npm timing reifyNode:node_modules/ini Completed in 74ms
npm timing reifyNode:node_modules/object-assign Completed in 74ms
npm timing reifyNode:node_modules/aproba Completed in 74ms
npm timing reifyNode:node_modules/wide-align Completed in 74ms
npm timing reifyNode:node_modules/has-unicode Completed in 74ms
npm timing reifyNode:node_modules/end-of-stream Completed in 74ms
npm timing reifyNode:node_modules/color-name Completed in 73ms
npm timing reifyNode:node_modules/color-string Completed in 73ms
npm timing reifyNode:node_modules/simple-swizzle Completed in 74ms
npm timing reifyNode:node_modules/fs-constants Completed in 77ms
npm timing reifyNode:node_modules/ieee754 Completed in 77ms
npm timing reifyNode:node_modules/mimic-response Completed in 77ms
npm timing reifyNode:node_modules/number-is-nan Completed in 77ms
npm timing reifyNode:node_modules/decompress-response Completed in 76ms
npm timing reifyNode:node_modules/core-util-is Completed in 76ms
npm timing reifyNode:node_modules/inherits Completed in 77ms
npm timing reifyNode:node_modules/lru-cache Completed in 77ms
npm timing reifyNode:node_modules/signal-exit Completed in 77ms
npm timing reifyNode:node_modules/set-blocking Completed in 77ms
npm timing reifyNode:node_modules/console-control-strings Completed in 77ms
npm timing reifyNode:node_modules/tunnel-agent Completed in 76ms
npm timing reifyNode:node_modules/color Completed in 77ms
npm timing reifyNode:node_modules/base64-js Completed in 79ms
npm timing reifyNode:node_modules/util-deprecate Completed in 78ms
npm timing reifyNode:node_modules/yallist Completed in 78ms
npm timing reifyNode:node_modules/safe-buffer Completed in 81ms
npm timing reifyNode:node_modules/deep-extend Completed in 81ms
npm timing reifyNode:node_modules/pump Completed in 81ms
npm timing reifyNode:node_modules/npmlog Completed in 81ms
npm timing reifyNode:node_modules/string_decoder Completed in 82ms
npm timing reifyNode:node_modules/is-arrayish Completed in 83ms
npm timing reifyNode:node_modules/isarray Completed in 82ms
npm timing reifyNode:node_modules/delegates Completed in 83ms
npm timing reifyNode:node_modules/color-convert Completed in 82ms
npm timing reifyNode:node_modules/detect-libc Completed in 82ms
npm timing reifyNode:node_modules/are-we-there-yet Completed in 83ms
npm timing reifyNode:node_modules/simple-get Completed in 84ms
npm timing reifyNode:node_modules/buffer Completed in 86ms
npm timing reifyNode:node_modules/rc Completed in 86ms
npm timing reifyNode:node_modules/bl Completed in 87ms
npm timing reifyNode:node_modules/prebuild-install Completed in 86ms
npm timing reifyNode:node_modules/node-abi Completed in 88ms
npm timing reifyNode:node_modules/gauge Completed in 90ms
npm timing reifyNode:node_modules/minimist Completed in 90ms
npm http fetch GET 200 https://registry.npmjs.org/mkdirp-classic/-/mkdirp-classic-0.5.3.tgz 73ms (cache miss)
npm timing reifyNode:node_modules/mkdirp-classic Completed in 92ms
npm http fetch GET 200 https://registry.npmjs.org/simple-concat/-/simple-concat-1.0.1.tgz 78ms (cache miss)
npm timing reifyNode:node_modules/simple-concat Completed in 96ms
npm http fetch GET 200 https://registry.npmjs.org/tar-stream/-/tar-stream-2.2.0.tgz 82ms (cache miss)
npm timing reifyNode:node_modules/tar-stream Completed in 98ms
npm timing reifyNode:node_modules/readable-stream Completed in 100ms
npm http fetch GET 200 https://registry.npmjs.org/github-from-package/-/github-from-package-0.0.0.tgz 77ms (cache miss)
npm timing reifyNode:node_modules/github-from-package Completed in 101ms
npm timing reifyNode:node_modules/tar-stream/node_modules/readable-stream Completed in 103ms
npm timing reifyNode:node_modules/bl/node_modules/readable-stream Completed in 103ms
npm http fetch GET 200 https://registry.npmjs.org/napi-build-utils/-/napi-build-utils-1.0.2.tgz 85ms (cache miss)
npm timing reifyNode:node_modules/napi-build-utils Completed in 104ms
npm timing reifyNode:node_modules/node-addon-api Completed in 103ms
npm timing reifyNode:node_modules/semver Completed in 104ms
npm timing reifyNode:node_modules/sharp Completed in 106ms
npm http fetch GET 200 https://registry.npmjs.org/tar-fs/-/tar-fs-2.1.1.tgz 82ms (cache miss)
npm timing reifyNode:node_modules/tar-fs Completed in 109ms
npm http fetch GET 200 https://registry.npmjs.org/expand-template/-/expand-template-2.0.3.tgz 97ms (cache miss)
npm timing reifyNode:node_modules/expand-template Completed in 118ms
npm timing reify:unpack Completed in 120ms
npm timing reify:unretire Completed in 0ms
npm timing build:queue Completed in 1ms
npm timing build:link:node_modules/prebuild-install Completed in 1ms
npm timing build:link:node_modules/rc Completed in 1ms
npm timing build:link:node_modules/semver Completed in 1ms
npm timing build:link Completed in 1ms
npm info run<EMAIL_ADDRESS>install node_modules/sharp (node install/libvips && node install/dll-copy && prebuild-install) || (node install/can-compile && node-gyp rebuild && node install/dll-copy)

<EMAIL_ADDRESS>install
(node install/libvips && node install/dll-copy && prebuild-install) || (node install/can-compile && node-gyp rebuild && node install/dll-copy)

npm http fetch POST 200 https://registry.npmjs.org/-/npm/v1/security/advisories/bulk 243ms
npm timing auditReport:getReport Completed in 247ms
npm timing auditReport:init Completed in 0ms
npm timing reify:audit Completed in 247ms
sharp: Detected globally-installed libvips v8.12.2ng reify:audit Completed in 247ms
sharp: Building from source via node-gyp
gyp info it worked if it ends with okemplate: timing reify:audit Completed in 247ms
gyp verb cli [
gyp verb cli   '/Users/kareljanvanhaute/.nvm/versions/node/v16.15.0/bin/node',
gyp verb cli   '/Users/kareljanvanhaute/.nvm/versions/node/v16.15.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js',
gyp verb cli   'rebuild'
gyp verb cli ]
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| darwin | arm64
gyp verb command rebuild []
gyp verb command clean []
gyp verb clean removing "build" directory
gyp verb command configure []
gyp verb find Python Python is not set from command line or npm configuration
gyp verb find Python Python is not set from environment variable PYTHON
gyp verb find Python checking if "python3" can be used
gyp verb find Python - executing "python3" to get executable path
gyp verb find Python - executable path is<EMAIL_ADDRESS>gyp verb find Python - executing<EMAIL_ADDRESS>to get version
gyp verb find Python - version is "3.9.12"te: timing reify:audit Completed in 247ms
gyp info find Python using Python version 3.9.12 found at<EMAIL_ADDRESS>gyp verb get node dir no --target version specified, falling back to host node version: 16.15.0
gyp verb command install [ '16.15.0' ]
gyp verb install input version string "16.15.0"iming reify:audit Completed in 247ms
gyp verb install installing version: 16.15.0
gyp verb install --ensure was passed, so won't reinstall if already installed
gyp verb install version is already installed, need to check "installVersion"
gyp verb got "installVersion" 9
gyp verb needs "installVersion" 9
gyp verb install version is good
gyp verb get node dir target node version installed: 16.15.0
gyp verb build dir attempting to create "build" dir: /Volumes/External/TMP/BASWEB/node_modules/sharp/build
gyp verb build dir "build" dir needed to be created? Yes
gyp verb build/config.gypi creating config file
gyp verb build/config.gypi writing out config file: /Volumes/External/TMP/BASWEB/node_modules/sharp/build/config.gypi
gyp verb config.gypi checking for gypi file: /Volumes/External/TMP/BASWEB/node_modules/sharp/config.gypi
gyp verb common.gypi checking for gypi file: /Volumes/External/TMP/BASWEB/node_modules/sharp/common.gypi
gyp verb gyp gyp format was not specified; forcing "make"
gyp info spawn<EMAIL_ADDRESS>gyp info spawn args [
gyp info spawn args   '/Users/kareljanvanhaute/.nvm/versions/node/v16.15.0/lib/node_modules/npm/node_modules/node-gyp/gyp/gyp_main.py',
gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args   '/Volumes/External/TMP/BASWEB/node_modules/sharp/build/config.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/Users/kareljanvanhaute/.nvm/versions/node/v16.15.0/lib/node_modules/npm/node_modules/node-gyp/addon.gypi',
gyp info spawn args   '-I',
gyp info spawn args   '/Users/kareljanvanhaute/Library/Caches/node-gyp/16.15.0/include/node/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/Users/kareljanvanhaute/Library/Caches/node-gyp/16.15.0',
gyp info spawn args   '-Dnode_gyp_dir=/Users/kareljanvanhaute/.nvm/versions/node/v16.15.0/lib/node_modules/npm/node_modules/node-gyp',
gyp info spawn args   '-Dnode_lib_file=/Users/kareljanvanhaute/Library/Caches/node-gyp/16.15.0/<(target_arch)/node.lib',
gyp info spawn args   '-Dmodule_root_dir=/Volumes/External/TMP/BASWEB/node_modules/sharp',
gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.'
gyp info spawn args ]
Package xproto was not found in the pkg-config search path.audit Completed in 247ms
Perhaps you should add the directory containing xproto.pc' to the PKG_CONFIG_PATH environment variable Package 'xproto', required by 'xau', not found gyp: Call to 'PKG_CONFIG_PATH="/usr/lib/pkgconfig:/usr/local/Homebrew/Library/Homebrew/os/mac/pkgconfig/12:/usr/local/lib/pkgconfig:/usr/lib/pkgconfig:/usr/local/libdata/pkgconfig:/usr/libdata/pkgconfig" pkg-config --cflags-only-I vips-cpp vips glib-2.0 | sed s\/-I//g' returned exit status 0 while in binding.gyp. while trying to load binding.gyp gyp ERR! configure error  gyp ERR! stack Error: gyp` failed with exit code: 1
gyp ERR! stack     at ChildProcess.onCpExit (/Users/kareljanvanhaute/.nvm/versions/node/v16.15.0/lib/node_modules/npm/node_modules/node-gyp/lib/configure.js:261:16)
gyp ERR! stack     at ChildProcess.emit (node:events:527:28)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
gyp ERR! System Darwin 21.4.0
gyp ERR! command "/Users/kareljanvanhaute/.nvm/versions/node/v16.15.0/bin/node" "/Users/kareljanvanhaute/.nvm/versions/node/v16.15.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Volumes/External/TMP/BASWEB/node_modules/sharp
gyp ERR! node -v v16.15.0
gyp ERR! node-gyp -v v9.0.0
gyp ERR! not ok
npm info run<EMAIL_ADDRESS>install { code: 1, signal: null }
npm timing reify:rollback:createSparse Completed in 19ms
npm timing reify:rollback:retireShallow Completed in 0ms
npm timing command:install Completed in 7578ms
npm verb stack Error: command failed
npm verb stack     at ChildProcess. (/Users/kareljanvanhaute/.nvm/versions/node/v16.15.0/lib/node_modules/npm/node_modules/@npmcli/promise-spawn/index.js:64:27)
npm verb stack     at ChildProcess.emit (node:events:527:28)
npm verb stack     at maybeClose (node:internal/child_process:1092:16)
npm verb stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)
npm verb pkgid<EMAIL_ADDRESS>npm verb cwd /Volumes/External/TMP/BASWEB
npm verb Darwin 21.4.0
npm verb argv "/Users/kareljanvanhaute/.nvm/versions/node/v16.15.0/bin/node" "/Users/kareljanvanhaute/.nvm/versions/node/v16.15.0/bin/npm" "install" "--verbose" "--foreground-scripts" "sharp"
npm verb node v16.15.0
npm verb npm  v8.5.5
npm ERR! code 1
npm ERR! path /Volumes/External/TMP/BASWEB/node_modules/sharp
npm ERR! command failed
npm ERR! command sh -c (node install/libvips && node install/dll-copy && prebuild-install) || (node install/can-compile && node-gyp rebuild && node install/dll-copy)
npm verb exit 1
npm timing npm Completed in 7683ms
npm verb unfinished npm timer reify<PHONE_NUMBER>755
npm verb unfinished npm timer reify:build<PHONE_NUMBER>178
npm verb unfinished npm timer build<PHONE_NUMBER>179
npm verb unfinished npm timer build:deps<PHONE_NUMBER>179
npm verb unfinished npm timer build:run:install<PHONE_NUMBER>181
npm verb unfinished npm timer build:run:install:node_modules/sharp<PHONE_NUMBER>181
npm verb code 1
npm ERR!      /Users/kareljanvanhaute/.npm/_logs/2022-05-10T14_03_06_651Z-debug-0.log

What is the output of running npx envinfo --binaries --system --npmPackages=sharp --npmGlobalPackages=sharp?
System:
OS: macOS 12.3.1
CPU: (8) arm64 Apple M1
Memory: 178.61 MB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.15.0 - ~/.nvm/versions/node/v16.15.0/bin/node
Yarn: 1.22.17 - /usr/local/bin/yarn
npm: 8.5.5 - ~/.nvm/versions/node/v16.15.0/bin/npm

I did a  brew update && brew upgrade and I reinstalled pkg-config and the vips. But to no avail. Still getting the same error.

When I remove the vips in brew. I get the following error.
error /Volumes/External/GIT/BASWEB/node_modules/sharp: Command failed.
 [MODE-ARG]...
Try 'libtool --help' for more information.
libtool:   error: unrecognised option: '-static'
make: *** [Release/nothing.a] Error 1
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/Users/kareljanvanhaute/.nvm/versions/node/v16.15.0/lib/node_modules/npm/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack     at ChildProcess.emit (node:events:527:28)
gyp ERR! stack     at Process.ChildProcess._handle.onexit (node:internal/child_process:291:12)
gyp ERR! System Darwin 21.4.0
gyp ERR! command "/Users/kareljanvanhaute/.nvm/versions/node/v16.15.0/bin/node" "/Users/kareljanvanhaute/.nvm/versions/node/v16.15.0/lib/node_modules/npm/node_modules/node-gyp/bin/node-gyp.js" "rebuild"
gyp ERR! cwd /Volumes/External/GIT/BASWEB/node_modules/sharp

https://sharp.pixelplumbing.com/install#apple-m1 says

Prebuilt sharp and libvips binaries have been provided for macOS on ARM64 since sharp v0.29.0.

The log you've provided looks like it's an attempt to install sharp v0.28.x - please upgrade.

@lovell thank you very much for your time. I used sharp in another plugin which used indeed 0.28.0. I now forced it to use the latest version. Now it works again.
For future reference, my steps:

yarn cache clean (don't know if this was necessary)
changed the yarn.lock file, so it points to v0.30.4 instead of v0.28.0.
And then runned  the installation again. And now it works.

The code I changed in the yarn.lock file:
<EMAIL_ADDRESS>  version "6.2.2"
  resolved "https://registry.npmjs.org/favicons/-/favicons-6.2.2.tgz"
  integrity sha512-qhvFqbhlXA/JYIDYuxTrE4uT9rcpTCrWvF3UG0GxBoLl/XgFBBTrZkQvASrkMebSwDCJ9kKGypRWIbvoRZLBsw==
  dependencies:
    clone "^2.1.2"
    colors "^1.4.0"
    image-size "^0.8.3"
    jimp "^0.16.1"
    jsontoxml "^1.0.1"
    lodash.defaultsdeep "^4.6.1"
    require-directory "^2.1.1"
    sharp "^0.30.4"
    through2 "^4.0.2"
    tinycolor2 "^1.4.2"
    to-ico "^1.1.5"
    vinyl "^2.2.1"
    xml2js "^0.4.23"

It's a bit weird it crashes because it had sharp "^0.28.0" so shouldn't it use 0.30.4 in that case on install?

Alternatively, if you don't need to use the brew-installed libvips, run brew remove vips then re-install sharp and it will use its own prebuilt binaries.

Removing vips worked! Wow!

Worked for me too! Thanks

Alternatively, if you don't need to use the brew-installed libvips, run brew remove vips then re-install sharp and it will use its own prebuilt binaries.

Removing vips worked! Wow!

This solved the issue for me on Mac Sequoia 15.0.1.


Added more test cases for ARIMA

ARIMA implementation is now tested for all possible combinations of
arguments. However, each argument (e.g. p,d,q,...) has final amount of
possible values.

Can an Admin verify this patch?

Welcome and thanks for catching these issues @TobiasSchmidtDE. Unfortunately, SYSTEMML-2340 did not resolve all issues yet. I'll work on a fix and merge this PR afterwards. In the meantime, it would be great if you could replace the introduced guava dependency with an alternative if possible. In the past, we faced version conflicts with Spark/Hadoop (pulling in different guava versions) and thus, decided to remove this unnecessary dependency.

LGTM - thanks again @TobiasSchmidtDE - instead of creating all combinations (some of which are invalid), I included a subset of problematic cases. These cases are currently failing due to incorrect loop range handling (i.e., missing increment). Once the ARIMA scripts are fixed, we can enable these tests. Thanks.


Cannot render static files in gofiber after build

Whenever I try to move the build (.exe) to another folder the http://<IP_ADDRESS>:3000/sample.txt will throw an error Cannot GET /sample.txt however if I run the build in the same project folder the static file sample.txt will load without problem.
project
├── static
  └── sample.txt
├── templates
  └── index.html
├── go.mod
├── go.sum
└── main.go

package main

import (
	"github.com/gofiber/fiber/v2"
	"github.com/gofiber/template/html"
	"github.com/markbates/pkger"
)

func main() {
	pkger.Include("/static")

	views := html.NewFileSystem(pkger.Dir("/templates"), ".html")

	app := fiber.New(fiber.Config{
		Views: views,
	})

	app.Static("/", "./static")

	app.Get("/", func(c *fiber.Ctx) error {
		return c.Render("index", fiber.Map{
			"Title": "Hello, World!",
		})
	})

	app.Listen(":3000")
}

I'm having the same issue on linux using go version go1.14.10 linux/amd64, and github.com/markbates/pkger v0.17.1

Have you run pkger to generate the pkged.go file?
Pkger is failing back to using the local disk. You need to run pkger to generate the go code that will get built into your binary, if that is present, Pkger will use THAT instead

I encounter the same issue, and turn out it seem to be the way go list unable to run.
Turn out my source folder is named in kebab case my-project, and due to package name convention in golang, pkger.go package was name my-project which is invalid.
After rename the project source, change the module name in go.mod and run the app again, I was able to add the pkger by using `import _ "rootPackage".


Implement run bundle subcommand to improve OLM integration

The Operator SDK maintainers are hard at work to implement run bundle to improve integration with the Operator Lifecycle Manager.
The purpose of this issue is to communicate with the community what will be in run bundle.
TODO

[x] create registry image pod (#3337 , #3665 )
[x] rebase / update operator-group-install-mode branch
[x] scaffold out structs from diagram to start (#3636)
[x] implement Config struct, refer to kubectl operator plugin and cobra "prerun" (#3636)
[x] implement RunBundle and tie CLI to call OperatorInstaller (#3636)
[x] connect run bundle to the Operator SDK CLI (#3636)
[x] create grpc catalogsource (#3467, #3832 )
[x] implement OperatorInstaller (#3764, #3838)
[x] implement IndexImageCatalogCreator (create CatalogCreator interface) (#3467)
[x] implement PackageManifestCatalogCreator (maybe) (#3764)
[x] update OperatorGroup logic to handle install mode for run bundle (#3861)
[x] create Subscription logic (#3764, #3838)
[x] verify operator is installed/upgraded (#3766 #3819)
[ ] write e2e test for run bundle and enable run bundle CLI (#3844 #3831)

Reference information

run bundle enhancement which describes the CLI to be implemented
run bundle upgrade enhancement
kubectl operator plugin

Proposed design:

run bundle is now in the operator-sdk.


Refactor code, update dependencies and version in girolle and girolle_macro

Type
Enhancement

Description

The PR mainly focuses on refactoring the code and updating dependencies.
The import statements in simple_macro.rs and lib.rs have been simplified by using a single import from girolle::prelude::*.
A new prelude module has been added to lib.rs.
The example in the documentation of lib.rs in girolle_macro has been removed.
The version in Cargo.toml for both girolle and girolle_macro has been updated from 1.0.1 to 1.1.0.
girolle_macro has been added to the dependencies in girolle/Cargo.toml, and girolle has been removed from the dependencies in girolle_macro/Cargo.toml.

Changes walkthrough
Relevant filesCode simplification

simple_macro.rsSimplify imports in simple_macro.rs

examples/simple_macro.rs

Replaced specific imports from girolle and girolle_macro with a   single import from girolle::prelude::*

+1/-2

Code refactoring

lib.rsRefactor imports and add prelude module in lib.rs

girolle/src/lib.rs

Removed the import of serde_json::Value

Added the import of JsonValue::{json, Value}

Added prelude to the module

+2/-2

Code addition

prelude.rsAdd imports to prelude.rs

girolle/src/prelude.rs

Added the import of girolle_macro::girolle

Added the import of JsonValue::{json, Value}

+3/-0

Documentation

lib.rsRemove example from lib.rs documentation

girolle_macro/src/lib.rs

Removed the example in the documentation

+0/-17

Dependencies

Cargo.tomlUpdate version and dependencies in Cargo.toml

girolle/Cargo.toml

Updated the version from 1.0.1 to 1.1.0

Added girolle_macro to the dependencies

+2/-1

Cargo.tomlUpdate version and remove girolle dependency in Cargo.toml

girolle_macro/Cargo.toml

Updated the version from 1.0.1 to 1.1.0

Removed girolle from the dependencies

+1/-2

 ✨ Usage guide:
Overview:
The describe tool scans the PR code changes, and generates a description for the PR - title, type, summary, walkthrough and labels. The tool can be triggered automatically every time a new PR is opened, or can be invoked manually by commenting on a PR.
When commenting, to edit configurations related to the describe tool (pr_description section), use the following template:
/describe --pr_description.some_config1=... --pr_description.some_config2=...

With a configuration file, use the following template:
[pr_description]
some_config1=...
some_config2=...

  Enabling\disabling automation

When you first install the app, the default mode for the describe tool is:

pr_commands = ["/describe --pr_description.add_original_user_description=true"
                         "--pr_description.keep_original_user_title=true", ...]

meaning the describe tool will run automatically on every PR, will keep the original title, and will add the original user description above the generated description.

Markers are an alternative way to control the generated description, to give maximal control to the user. If you set:

pr_commands = ["/describe --pr_description.use_description_markers=true", ...]

the tool will replace every marker of the form pr_agent:marker_name in the PR description with the relevant content, where marker_name is one of the following:

type: the PR type.
summary: the PR summary.
walkthrough: the PR walkthrough.

Note that when markers are enabled, if the original PR description does not contain any markers, the tool will not alter the description at all.

  Custom labels
The default labels of the describe tool are quite generic: [Bug fix, Tests, Enhancement, Documentation, Other].
If you specify custom labels in the repo's labels page or via configuration file, you can get tailored labels for your use cases.
Examples for custom labels:

Main topic:performance - pr_agent:The main topic of this PR is performance
New endpoint - pr_agent:A new endpoint was added in this PR
SQL query - pr_agent:A new SQL query was added in this PR
Dockerfile changes - pr_agent:The PR contains changes in the Dockerfile
...

The list above is eclectic, and aims to give an idea of different possibilities. Define custom labels that are relevant for your repo and use cases.
Note that Labels are not mutually exclusive, so you can add multiple label categories.
Make sure to provide proper title, and a detailed and well-phrased description for each label, so the tool will know when to suggest it.

  Utilizing extra instructions
The describe tool can be configured with extra instructions, to guide the model to a feedback tailored to the needs of your project.
Be specific, clear, and concise in the instructions. With extra instructions, you are the prompter. Notice that the general structure of the description is fixed, and cannot be changed. Extra instructions can change the content or style of each sub-section of the PR description.
Examples for extra instructions:
[pr_description]
extra_instructions="""
- The PR title should be in the format: '<PR type>: <title>'
- The title should be short and concise (up to 10 words)
- ...
"""

Use triple quotes to write multi-line instructions. Use bullet points to make the instructions more readable.

  More PR-Agent commands

To invoke the PR-Agent, add a comment using one of the following commands:

/review: Request a review of your Pull Request.
/describe: Update the PR title and description based on the contents of the PR.
/improve [--extended]: Suggest code improvements. Extended mode provides a higher quality feedback.
/ask <QUESTION>: Ask a question about the PR.
/update_changelog: Update the changelog based on the PR's contents.
/add_docs 💎: Generate docstring for new components introduced in the PR.
/generate_labels 💎: Generate labels for the PR based on the PR's contents.
/analyze 💎: Automatically analyzes the PR, and presents changes walkthrough for each component.

See the tools guide for more details.
To list the possible configuration parameters, add a /config comment.

See the describe usage page for a comprehensive guide on using this tool.

/describe

/review

/review

/improve


Feature/#209 improve redesign

Changes Unknown when pulling 5ea5e1271e04d372cc66391b28ba8bd6e20e1fba on feature/#209-improve-redesign into ** on develop**.


Add functionality to load a parquet file

Addresses part of #1538
Dependent on #1572. Please note that this currently contains the same commit as in #1572 to facilitate GitHub Actions.
Description
This PR adds a function with unit tests to load a parquet file using pandas.
Testing:

[x] Ran tests and they passed OK
[x] Added new tests for the new feature(s)

I'm not that this wrapper is needed, does it give us anything over using pd.read_parquet() directly?

I think that we will be interested in reading in parquet files, outside of the parquet to cube CLI. This will be needed for rain calibration.
cc @benowen-bom


Bludit v3.9.2 Code Execution Vulnerability in "Upload function"

A Code Execution Vulnerability in Bludit v3.9.2
Hi,
For CVE ID,so I open a new issue,sorry about that.And I  think you haven't completely fixed the bug.
There is a new Code Execution Vulnerability which allow to get server permissions,the path is /bl-kernel/admin/ajax/upload-images.php
1, login with any account which allows you to edit conten

2.upload the evil jpg
We can specify the location of the uploaded file by changing the value of the uuid,then upload the evil picture to tmp folder

3.upload both the.htaccess file and the access target jpg

Successfully reverted to the target file
4. Access the evil file that are written through jpg

So I recommend checking the file before uploading it to temporary directory

I uploaded a fix, checking if the uuid variable has a directory separator character.
Any other recommendation to prevent this ?

It can also to code execution by both accounts upload file at the same time,one of account to upload the .htaccess file,and the other upload the evil file.

My personal opinion is rename the file to random number before upload to temporary directory.

I added check the extension file, if you can try to do the exploit with the version from Github. I will release a new version in a few days.

OK,glad to help you

Fixed in Bludit v3.10.0.

its too late but you dont even need to upload .htaccess or jpg
you can upload php file into server and may get some error that you cant upload such format but btw it will be upload to server and you can use that php file

i need help exploit it


Badge request: ProGet NuGet feeds

:clipboard: Description

Service: Inedo ProGet
Latest Version (), Latest Prerelease (), Download Count ()

Specifically, we're looking for support for the nuget feeds, but there are a lot of other feed types that others could find useful.
:link: Data

ProGet supports many types of artifact feeds. This issue is specifically looking to add support for the nuget feeds. other feeds supported by ProGet:

NuGet
PowerShell Packages / Modules
Ruby Gems
Visual Studio Extensions
Maven
npm
Bower
Chocolatey
Docker

I'd be willing to contribute support for the nuget feed, although I'm not sure if this would be better off as a generic addition to the existing nuget service that supports arbitrary feed URL's or as it's own service so support for other feed types can be added later.

IMO this should be implemented as a separate family of services under services/proget/.. directory. I look at proget as being very functionally similar to other services we support (nexus, bintray, etc.) for binary/artifact storage and distribution.
I'd hope that the proget APIs will return the info we'll need (version, download counts, etc.) in a standard/homogenized response regardless of the format of the target feeds/repositories but if not we can break out more granular services
i.e. I hope we can have services like proget-downloads.service.js, proget-version.service.js, etc. otherwise maybe we could do proget-nuget-downloads.service.js, etc.

For nuget feeds specifically, they're just standard nuget v2/v3 feeds (depending on the version of proget) available at <proto>://<hostAndPath>/nuget/<feedName>. The other feed types are similarly routed.

I assume that's for consumption right? As in that's the type of path I would use to add a nuget feed from proget as a nuget package store for my app vs. that's where I'd get the total/interval download counts from proget

Was there any progress in regards to proget badges ?


Reorder and add section headings to README

@blink1073 @jasongrout One more pass on the docs. Focusing on user understanding and comprehension through breaking up the larger sections of text with headings.

Thanks so much!


SWP-95814 Add 10 and 20 second rates

Allow rate limits to be specified in 10/20 second increments

I feel like most services either do rate limit of per second or per minute. Even on Kong, we only have the ability to limit per second/minute.
Approving assuming an investigation has been done and it is determined that 1 second / 1 minute is not enough granularity.

@Timothylock: The ticket description points out two examples of existing integrations that use these intervals:

Hubspot: 100 requests/10 seconds
Marketo: 100 requests/20 seconds

It was possible to convert the rate limit to use a smaller unit (e.g. 100 req/20s -> 5 req/s) ... Unfortunately, that would unnecessarily rate limit any temporary burst of 6-100 requests in an otherwise quiet period.  I know, for example, that accessing the integration settings for Marketo results in a large number of requests, and that would have led to worse UX.

This PR has been merged to an incorrect branch. Opening #3 to merge the PR to main.


[Event Request]Application “Tests-Workflow”, 134307 "Workflow Cond. Eval. Tests"

[Event Request]Application “Tests-Workflow”, 134307 "Workflow Cond. Eval. Tests"
Could you please insert the OnTestInitialize Event at the beginning of each test procedure:

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability.


GPS toggle not working

I've set Toggle settings -> GPS sources to "GPS & network" and "Network", so it should toggle between "High accuracy" and "Battery saving" location setting in Android.
My device is a BQ Aquaris X5 Plus.
The toggle used to work in Firmware 1.5.1, but stopped working after the update to Firmware 1.6. (Both firmware versions use Android 6.0.1).
A command is executed with root access, but results in an error:

Please let me know whether this is an issue with Power Toggles or a Firmware issue.

Works again after upgrading my phone to Android 7. Probably an issue with the device firmware.


How do you handle pluralisation in Handlebars?

Is it possible to write a helper for pluralizing words that can be used like this?
{{dog_count}} {{pluralize dog_count "dog" "dogs"}} {{pluralize dog_count "has" "have"}} gone for a walk.

I made my own Handlebars helper for this. It's pretty versatile. For example, all of these compile to "bagel" when numVar === 1 and to "bagels" for everything else:
{{plural numVar 'bagel'}}
{{plural numVar 'bagel(s)'}}
{{plural numVar 'bagel/bagels'}}
bagel{{plural numVar}}

It can also be used for switching between singular and plural grammar as appropriate:
{{numVar}} bagel{{plural numVar ' was/s were'}} eaten.

Here's the source: https://gist.github.com/drmercer/c3e0b2e174718787dac5a181b2be83f6

Also consider using grunt-locales to manage your translations.


Add comments to WSX

WSX right now is pretty hard to tweak since it lacks comments for way finding.
In addition, some have manual lines for inserting files where others do a for loop.  This causes confusion as well.

This is currently done


Can  be used to complete all common characters within the completion menu?

meta: I did not think the Bug Report issue template was relevant here, since this is more of a question / feature request and isn't specific to my config. I have not found this feature discussed in issues or the wiki, and the FAQ link in the README is broken. Apologies if I have missed something, I am a little surprised to have not found this because it seems like it would be common.
The use-case here is for expediting completion when there are a large number of possible results remaining but they share a long common stem. For instance, we might have my-very-long-prefix which is shared by a number of symbols my-very-long-prefix.foo, my-very-long-prefix.bar, etc. Typing out my-v brings up a window where each possible result begins with my-very-long-prefix, and it can save a lot of typing if one could simply hit <tab> to autocomplete to the shared prefix, at which point one could continue typing to narrow down the possibilities. This is not dissimilar to bash terminal completion, where pressing tab will complete the common prefix of all remaining valid completions.
Is this feature possible right now, and if so can I find instructions on how to set it up? (I thought this feature was present in nvim-compe but perhaps I am wrong)

Hm...interesting.
I'll try to implement it.

BTW, You can type mybar for such situation.


chore(deps): upgrade dependencies

Upgrades project dependencies. See details in workflow run.

Automatically created by projen via the "upgrade-k8s-24-main" workflow

⚪ Backport skipped
The pull request was not backported as there were no branches to backport to. If this is a mistake, please apply the desired version labels or run the backport tool manually.
Manual backport
To create the backport manually run:
backport --pr 2254

Questions ?
Please refer to the Backport tool documentation


Evaluation order for function calls undefined

Fix this too in cppCodegen

Yes this will lead to source code size blowup but this is an acceptable risk to take

There will be modification later


feat: Detect undefined variations

Description
In this PR we had a new check when validating a feature flag to check if we reference an undefined variation in one of the rule configuration.
The effect of this PR is double, it will allow the linter to detect those issues and it will discard this flag (and log an error)  for misconfigured flags.
Closes issue(s)
Resolve #2562
Checklist

[x] I have tested this code
[x] I have added unit test to cover this code
[x] I have followed the contributing guide

Thanks!


feat: generate blocks if no matured cellbase

:cry:  Sadly, I ran tps-bench at night before I fell asleep, it just finished the turn for tps 1 when I woke up at next afternoon (a bit hyperbole).
I have spent 60 minutes to run tps-bench for one time with dev spec: 5 min for build ckb and tps-bench, 1800 secs for tps 1.
In benchmark CI, another 30 minutes is required to build two ckb and tps-bench, it's 90 minutes in total, current is 40 minutes.
I hope this issue could be fixed a.s.a.p. :smile:


Jav 438 work for integration

1.调整Web为Spring Boot启动（便于打包）
2.ServiceComb暂时不支持@CrossOrigin，所以改为Zuul做网关
3.修改Docker Compose

Coverage increased (+0.004%) to 95.444% when pulling 250ca98520f5ca19a25460b75fd1568024322222 on JAV-438_work_for_Integration into fec3189df345e363c33c32c6ba2c78c5370122c8 on master.

Coverage increased (+0.004%) to 95.444% when pulling 72328a40b05b5a9f37cb67b58f3fcf01ef52030b on JAV-438_work_for_Integration into fec3189df345e363c33c32c6ba2c78c5370122c8 on master.

Coverage increased (+0.004%) to 95.444% when pulling 8519cffce0f9f6d40cd6ac97273d43e36343b753 on JAV-438_work_for_Integration into fec3189df345e363c33c32c6ba2c78c5370122c8 on master.


--terragrunt-modules-that-include does not work

Everytime I try to use --terragrunt-modules-that-include, terragrunt simply returns this and nothing is executed:
  [yyyy@XXXX:~/tg]$ terragrunt run-all plan --terragrunt-modules-that-include incl.hcl
  INFO[0000] The stack at /home/yyyy/tg will be processed in the following order for command plan:
  [yyyy@XXXX:~/tg]$

I can reproduce this with a very simple project:
.
├── first
│   ├── main.tf
│   └── terragrunt.hcl
└── incl.hcl
Where the terragrunt.hcl file does nothing but include the incl.hcl (all other files are empty):
  include "incl" {
      path = "../incl.hcl"
  }

Even after turning on debug logging, I have no glue why terragrunt is constantly refusing to run my stack:
  yyyy@XXXX:~/tg]$ terragrunt run-all plan --terragrunt-modules-that-include incl.hcl --terragrunt-log-level debug
  DEBU[0000] Did not find any locals block: skipping evaluation.  prefix=[/home/yyyy/tg/first]
  DEBU[0000] Did not find any locals block: skipping evaluation.  prefix=[/home/yyyy/tg/first]
  DEBU[0000] [Partial] Included config ../incl.hcl has strategy shallow merge: merging config in (shallow).  prefix=[/home/yyyy/tg/first]
  DEBU[0000] Setting download directory for module /home/yyyy/tg/first to /home/yyyy/tg/first/.terragrunt-cache
  DEBU[0000] Stack at /home/yyyy/tg:
    => Module /home/yyyy/tg/first (excluded: true, assume applied: false, dependencies: [])
  INFO[0000] The stack at /home/yyyy/tg will be processed in the following order for command plan:
  [yyyy@XXXX:~/tg]$

It says the module /home/yyyy/tg/first was excluded but when I simply remove the --terragrunt-modules-that-include attribute from the command line, my stack is executed.
terragrunt version v0.35.14

I will take a look at this one, looks like an issue with the detection of included files in
https://github.com/gruntwork-io/terragrunt/blob/master/configstack/module.go#L258

Will close this when the release is cut.

Fixed in https://github.com/gruntwork-io/terragrunt/releases/tag/v0.35.16

Works now even in the big Terragrunt setup for me. Thanks a lot!

Hi @denis256, unfortunately I have to revert my statement from yesterday. It doesn't work 100%. It is difficult to track down but I think the bug is here: https://github.com/gruntwork-io/terragrunt/blob/5cf44f6ef421f35c8e16623fdf6f3695f3021bc0/configstack/module.go#L276-L280
Looks like the canonical path fix hasn't been applied to the transitive dependencies' includes. That's why I have now the situation that a module is included through its include blocks but later excluded because it is mentioned as a dependency somewhere.

@denis256, can you please reopen this issue?


Get both ingress and egress queue length in bytes

How do i get queue size in bytes? I tried some approaches, one of which was that i stored a 32 bit field in metadata. And as we know that in v1model switch each packet has to pass through parser, ingress pipeline,traffic manager, egress pipeline and deparser. I updated it with the packet_length field in ingress and egress block, but it always gave output as zero. Code is as follows:
meta.que_len=meta.que_len+standard_metadata.packet_length; meta.que_len=meta.que_len-standard_metadata.packet_length;
when queue is build up (i generated UDP traffic using iperf), then shouldn't it give the queue length in bytes?
And can someone please explain how do we calculate queue size in v1model switch.
Thank you

In the open source v1model architecture, there is no built-in mechanism to get queue sizes in bytes.
There are built-in mechanisms where during egress processing, you can read the depth of the queue a packet went through after ingress, and before egress, both at the time it was enqueued (standard_metdata.enq_qdepth) and at the time it was dequeued (standard_metadata.deq_qdepth).  The units of these queue depths are in number of packets, though, not in number of bytes.  Search for occurrences of qdepth on this page: https://github.com/p4lang/behavioral-model/blob/master/docs/simple_switch.md#queueing_metadata-header
There are other proprietary architectures that enable reading similar values in egress, in units that are either bytes, or more closely related to bytes, e.g. some architectures use "cells" as something approximately like "ceiling(packet_length_in_bytes / cell_size_in_bytes)", where cell_size_in_bytes might be a number like 60 bytes.  You would need to consult the documentation of the particular architecture to find out what they provide.
It is certainly possible using a fairly decent amount of P4 code, and packet recirculation, and P4 registers, to maintain a queue depth in any units you wish, readable from ingress.  Such a value would not be the most up-to-the-nanosecond correct value.  For example, it could be something like "exact total number of bytes ever enqueued in queue number X, minus a the number of bytes ever dequeued from queue number X as of between T1 and T2 microseconds ago", where T1 and T2 would depend upon details of the implementation, but could probably be made on the order of T1 approximately 1 microsecond, and T2 approximately 2 microseconds, on some high speed targets.

Here is an issue on the behavioral-model repository suggesting the idea of adding variants of enq_qdepth and deq_qdepth to the open source BMv2 simple_switch implementation, which would not be a lot of work to implement, but it isn't necessarily an urgent thing to implement, either.  https://github.com/p4lang/behavioral-model/issues/841
Note that this repository where you have created this issue is intended for issues about the P4 language itself.  Up to this point, the kinds of features you are asking about have not been considered part of the P4_16 language specification, but are instead delegated to P4_16 architectures, and each such P4_16 architecture makes its own independent decisions what kinds of features like this that they provide.


doc: flatpak hub missing update command

On this page: https://flathub.org/apps/details/io.dbeaver.DBeaverCommunity
At the bottom, add missing "upgrade" command:
Update:
flatpak update io.dbeaver.DBeaverCommunity

Unfortunately we cannot influence this. It's flathub issue.

Unfortunately we cannot influence this. It's flathub issue.

Actually you can and should, by opening a bug with them to correct the information. I only brought this to your attention to help your users. This is how improvements are done, when people take initiative.

Actually you can and should, by opening a bug with them to correct the information. I only brought this to your attention to help your users. This is how improvements are done, when people take initiative.


@1aurabrown => [ARTiledImageView] Add more breadcrumbs for a crash we're experiencing.

Related to #686

whoa sorry i totally didn't see this @alloy

No problemo for sigñor :+1:


build fails

ubuntu subsystem or on windows build fails with:
error: failed to run custom build command for glfw-sys v3.3.0
Caused by:
process didn't exit successfully: G:\rust\flutter-rs\target\debug\build\glfw-sys-14aa8bdb431de969\build-script-build (exit code: 101)
--- stdout
running: "cmake" "C:\Users\fox21\.cargo\registry\src\github.com-1ecc6299db9ec823\glfw-sys-3.3.0\." "-G" "Visual Studio 16 2019" "-Thost=x64" "-Ax64" "-DGLFW_BUILD_EXAMPLES=OFF" "-DGLFW_BUILD_TESTS=OFF" "-DGLFW_BUILD_DOCS=OFF" "-DCMAKE_INSTALL_LIBDIR=lib" "-DCMAKE_INSTALL_PREFIX=G:\rust\flutter-rs\target\debug\build\glfw-sys-dfa596fa242f662f\out" "-DCMAKE_C_FLAGS= /nologo /MD" "-DCMAKE_C_FLAGS_DEBUG= /nologo /MD" "-DCMAKE_CXX_FLAGS= /nologo /MD" "-DCMAKE_CXX_FLAGS_DEBUG= /nologo /MD" "-DCMAKE_BUILD_TYPE=Debug"
--- stderr
thread 'main' panicked at '
failed to execute command: The system cannot find the file specified. (os error 2)
is cmake not installed?
build script failed, must exit now', C:\Users\fox21.cargo\registry\src\github.com-1ecc6299db9ec823\cmake-0.1.39\src\lib.rs:829:5
note: Run with RUST_BACKTRACE=1 environment variable to display a backtrace.
warning: build failed, waiting for other jobs to finish...
error: build failed

cmake is needed for glfw-sys compilation on linux. Take a look here: https://github.com/PistonDevelopers/glfw-rs
But even if this succeeds, does WSL support linux GUI application?


Docker Remote API v1.24 "Tag an image into a repository" description could be clearer

The the Docker Remote API v1.24 (https://github.com/docker/docker/blob/master/docs/reference/api/docker_remote_api_v1.24.md), the REST function,
Tag an image into a repository
does not really explain what the function does.

ping @thaJeztah
can you check pls?

yup, I can try making it more clear


eslint and webstorm complain about get-schema output

This happens 😿
Given I have a graphql endpoint
And it serves a schema with comments/docs/descriptions
When I use graphql-cli to generate the schema (graphql get-schema -e default)
Then the output schema.graphql cannot be be parsed by eslint plugin and webstorm plugin

This should be happening: 🙏
Given I have a graphql endpoint
And it serves a schema with comments/docs/descriptions
When I use graphql-cli to generate the schema (graphql get-schema -e default)
Then the output schema.graphql can be parsed by eslint plugin and webstorm plugin

From a type:
# It's some sort of pet
type Pet {
  name: String
}

When generated by get-schema it generates this invalid syntax:
"""It's some sort of pet"""
type Pet {
  name: String
}

Plugin versions:
ESLINT "eslint-plugin-graphql": "^1.4.1"
WEBSTORM ``JS GraphQL: 1.6.2`

This schema is valid according to the most recent graphql spec: https://github.com/graphql/graphql-js/releases/tag/v0.12.0.

Updated ticket title and provided plugin versions.

As @kbrandwijk mentioned, this is according to the current official GraphQL spec. The right way forward is to help eslint + webstorm to support the newest GraphQL version. Until then I recommend to use a previous version of the graphql-cli.

@schickling I tried reverting graphql-cli all the way to version 1.1.0 (npm install -g<EMAIL_ADDRESS>and graphql-cli was still generating the new schema type.
I was wondering if the graphql version defined in the graphql-cli package.json was not locked, and it always installing the newest, but I navigated to the location where graphql-cli is installed and checked the version of graphql, and it is indeed 0.11.6.  Maybe somewhere in the modules the version is not locked?


When I try to import this file I get a database error "ERROR: Geometry SRID (0) does not match column SRID (25833)" which I believe should indicate that the gml file doesn't have a specified coordinate system, but as far as I can see it has. I've also tried to import the Railway Scene example from the distribution, but with the same error.
ksu_test.txt

Strange... I believe I have an older postgis than you, may be an issue there... I'll take it up with my systems people.

Ok, closing then. Feel free to reopen if you have more information.


Security Measures

Description:
• Implementation of security best practices, including SSL/TLS encryption for secure HTTP connections.
• Regular updates and security patches applied to the server and software to protect against known vulnerabilities.

The issue appears to be well defined. Requires a "definition of done" to clarify completion criteria.

Server environment is setup with OU firewall so incoming traffic can happen only within OU network. Secure ports are open for the server


Support standalone Var throughout transpiler

Summary
This adds the missing pieces to fully support standalone Var nodes through every part of the transpiler (that I could detect).  It's quite possible there's some problem in a more esoteric non-preset pass somewhere, but I couldn't spot them.
For the most part there were very few changes needed to the actual passes, and only one place in QuantumCircuit that had previously been missed.  Most of the commit is updating passes to correctly pass inline_captures=True when appropriate for dealing with DAGCircuit.compose, and making sure that any place that needed to build a raw DAGCircuit for a rebuild without using DAGCircuit.copy_empty_like made sure to correctly add in the variables.
This commit adds specific tests for every pass that I touched, plus the general integration tests that we have for the transpiler to make sure that OQ3 and QPY serialisation work afterwards.
Details and comments
Close #10931.
This is the top of the stack and depends on #12215 and #12308 (the latter of which depends on #12307, though those could be merged together).
I'll write the full release note as a full PR after the tagging of rc1.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

277 of 309 (89.64%)  changed or added relevant lines in 19 files are covered.
15 unchanged lines in 5 files lost coverage.
Overall coverage increased (+0.05%) to 89.591%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit/transpiler/passes/layout/apply_layout.py
5
6
83.33%

qiskit/transpiler/passes/layout/sabre_layout.py
5
6
83.33%

qiskit/transpiler/passes/routing/stochastic_swap.py
8
9
88.89%

qiskit/visualization/circuit/text.py
19
22
86.36%

qiskit/qasm3/exporter.py
73
77
94.81%

qiskit/dagcircuit/dagcircuit.py
54
60
90.0%

qiskit/visualization/circuit/matplotlib.py
3
19
15.79%

Files with Coverage Reduction
New Missed Lines
%

qiskit/qasm3/exporter.py
1
95.87%

qiskit/visualization/circuit/matplotlib.py
1
49.33%

qiskit/dagcircuit/dagcircuit.py
1
91.81%

crates/qasm2/src/lex.rs
6
91.6%

crates/qasm2/src/parse.rs
6
97.61%

Totals

Change from base Build<PHONE_NUMBER>:
0.05%

Covered Lines:
61655

Relevant Lines:
68818

💛  - Coveralls

Now rebased over #12308 (speculatively assuming the merge-queue commit passes CI).

I'll try closing and re-opening this to see if that triggers GH to recalculate the merge base.


Fix for Vagrantfile merging security.json

Invert merge so settings in security.json are not overridden by static settings.

Steve and I discussed extending auth-setup to prompt the user for an admin account password.  This should make the situation less confusing the for the user since they pick the password themselves. Once we the change to auth-setup is committed that I'll close this PR (vs. merging it) and validate that the Vagrantfile no longer passes in any override credentials.  Cool?


infrastructure: set comment on head ref pr

hey @jarrvis  I've added a step for referring to PR head ref as it's nicer to see already the tests result in the same PR context and not having to jump to actions  section - unfortunately there is no other way to test it than merge it to main branch


Define an object for doctests?

Is it possible to globally define an object for doctest?
And how to run the command with this object?
example command: doctest.testmod(extraglobs={'t': MdFile(PDF_FILE_TEST)})

I'd be curious to know more about what you have in mind. Where would you be defining the object and executing the command? This extension doesn't modify the way doctests work within python, it only runs the command in the terminal.

I am testing a class (see attached file) and I therefore need an object of
this class without having to define it on each test!
To do this, I pass this object as a parameter to the command which launches
the tests:
doctest.testmod(extraglobs={'t': MdFile('/Users/pco/boulanger_2023_balance_minuteur.pdf')})
And when I run the tests with your extension, it doesn't know this object...
  File "<doctest md_file.MdFile.gen_tags[0]>", line 1, in <module>
    t.gen_tags()
    ^
NameError: name 't' is not defined

Le mer. 12 juin 2024 à 17:00, Noah Synowiec @.***> a
écrit :

I'd be curious to know more about what you have in mind. Where would you
be defining the object and executing the command? This extension doesn't
modify the way doctests work within python, it only runs the command in the
terminal.
—
Reply to this email directly, view it on GitHub
https://github.com/NoahSyn10/VSCode-PyDoctestBtn/issues/8#issuecomment-2163264290,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ASJFGAAIOTM23DEUTPAHVWLZHBO7JAVCNFSM6AAAAABIIXBY56VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRTGI3DIMRZGA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Warning : "Unable to set utime on symlink {}. Your Python build does not support it"

When I run the file "run_prepare_data_locally.sh", it gives a warning "Unable to set utime on symlink {}. Your Python build does not support it" for the rule "Fastqs".

@AkankshaFarswan
We fixed the problem according to http://snakemake.readthedocs.io/en/stable/project_info/faq.html?highlight=symlink#can-the-output-of-a-rule-be-a-symlink. Please do not hesitate to ask again if the problem remains.
Best,
Jochen

I used the updated code this time and it is again giving the error. I am
attaching the screenshot of the error.[image: Inline image 1]
Please help.
On Sat, Sep 30, 2017 at 10:34 PM, singerj<EMAIL_ADDRESS>wrote:

Closed #3 https://github.com/cbg-ethz/NGS-pipe/issues/3.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cbg-ethz/NGS-pipe/issues/3#event-1272809728, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AbvoR43Tc_fvQDwBaTGozuA8XrO11aLNks5snnSDgaJpZM4PpfXA
.

@AkankshaFarswan
Hi,
unfortunately I cannot see the screenshot you created. However, I downloaded the latest version and ran the script. During the last commit I accidentally introduced an error which I have now corrected. However, the linking issues is not resolved yet. As this is a know problem (http://snakemake.readthedocs.io/en/stable/project_info/faq.html?highlight=symlink#can-the-output-of-a-rule-be-a-symlink) and "only" a warning you can ignore the issue for the time being. I hope I can fix this problem soon.
Best,
Jochen

Hi,
Thank you for the help.
On Mon, Oct 2, 2017 at 3:08 PM, singerj<EMAIL_ADDRESS>wrote:

@AkankshaFarswan https://github.com/akankshafarswan
Hi,
unfortunately I cannot see the screenshot you created. However, I
downloaded the latest version and ran the script. During the last commit I
accidentally introduced an error which I have now corrected. However, the
linking issues is not resolved yet. As this is a know problem (
http://snakemake.readthedocs.io/en/stable/project_info/faq.
html?highlight=symlink#can-the-output-of-a-rule-be-a-symlink) and "only"
a warning you can ignore the issue for the time being. I hope I can fix
this problem soon.
Best,
Jochen
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/cbg-ethz/NGS-pipe/issues/3#issuecomment-333486726,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AbvoR6Ln5u3o9mEuIuqhpLzDiv4SSe22ks5soK8qgaJpZM4PpfXA
.


Proposal for type namespaces

I'm working on PR for active_model_serializers gem:
https://github.com/rails-api/active_model_serializers/pull/1216
Right now standard doesn't say anything about namespace declaration in type field, and current behavior of ams is just to glue namespace segments by the same separator that is used for class name processing. So Namespaced::SuperModel becomes namespaced_super_model, which doesn't allow for distinguishing between this one and NamespacedSuperModel.
Current proposal from ams team is to use double dash for this purpose and formally it complies standard, however I think something like / or : or . would serve better. So here are variants of proposals:

Can we let member names contain any of these symbols to reflect namespace of the model? Probably a period as it's url-safe?

Or can we create namespace attribute next to type and pass the namespace there?

Or can we recommend passing namespace in meta?

Is this a dup of https://github.com/json-api/json-api/issues/850 ?

Seems like. Sorry. ;) Should I just close this one?

Yeah, let's consolidate discussion over there :+1:


Sluggish Performance when using External Display

VSCode Version: 1.46.0-insider
OS Version: macOS 10.15.5 (19F101)
Extensions Installed: none

Steps to Reproduce:

Quit VSCode before attaching the external monitor
Sleep your mac
Hook up your Macbook to an external display (as described here)
Launch VSCode. You'll start to notice that VSCode now performs really slowly.

Workaround

Do not quit VSCode when you're on your macbook without the external monitor attached
Sleep
Hook up your Macbook to an external display
No performance hit.

Does this issue occur when all extensions are disabled?: Yes
Strangely, when I attempted to profile performance, this problem would go away.
The typing speed goes back to normal, and VSCode behaves normally.
https://www.icloud.com/iclouddrive/0DJATm0_JKYV8SVv7HFAtUOGA#vscode_performance

Just solved this by changing the calibrated color profile I had. I put it back to the default and now vscode and all the other apps are running great

Can you check if the issue happens with our latest insiders and exploration builds ?

Just solved this by changing the calibrated color profile I had. I put it back to the default and now vscode and all the other apps are running great

@nidty719 is correct. Removing my calibrated color profile completely resolves this issue for me.

Both builds are still facing the same issue when you have a calibrated color profile.
Version: 1.52.0-insider Commit: 40558fc8e13dbdceee5f4a9ad3fc661b9f8dae15 Date: 2020-11-11T16:49:20.394Z Electron: 9.3.3 Chrome: 83.0.4103.122 Node.js: 12.14.1 V8: <IP_ADDRESS>-electron.0 OS: Darwin x64 19.6.0
Version: 1.52.0-exploration Commit: 3c1b4bacbef4ab788f72059f56ef53e9aa7923bc Date: 2020-11-04T06:53:16.102Z (1 wk ago) Electron: 11.0.0-beta.17 Chrome: 87.0.4280.27 Node.js: 12.18.3 V8: <IP_ADDRESS>-electron.0 OS: Darwin x64 19.6.0


Fix setbfree UI

Description of changes
The package was being built without UI because it was applying to the wrong file. Changing the file to be patched to common.mak fixes that.

Thank you for the fix!
I'd suggest using substituteInPlace instead of sed because it warns when substitution does not happen; and I'd like to add an installCheckPhase that checks that setBfree was built with UI: #223707


atrium_xrpc_server isn't compatible with tokio::spawn

atrium_xrpc_server::stream::frames::Frame::try_from returns Result<Self, Box<dyn std::error::Error>>. The problem is that dyn std::error::Error is not Send, which means that if the result of Frame::try_from is potentially used across an await, the entire future is not Send.
To reproduce this, modify the firehose example to spawn the firehose running method instead of running it directly with #[tokio::main]. I tested this at commit 7d99ccd36c8bb562276732d1b9bb888f42530151.
It would be helpful if the error type was Send + Sync + 'static, to also make it compatible with the anyhow crate. But that can be handled by rewriting the error as a string, whereas the future not being Send is more problematic for usage.

Thank you for your report! I modified atrium-xrcp-server to use anyhow::Error and confirmed that it works with the following change in firehose example.
    tokio::spawn(async move {
        let _ = process_message(&message).await;
    });


generatemakefile.sh j2 dependency

When I try and run the  generatemakefile.sh script, I get an error stating the the "j2 command is not available".
I ended up changing the pyproject.toml file to include the following line j2cli = ">=0.3.11"
This is the package this will download https://github.com/kolypto/j2cli
This seemed to resolve the issue once I reran the poetry install/lock commands

Hi Aaron! @souzadevinicius will be able to advise better once he returns to office, but it seems from the docs that J2 is installed prior to running the makefile.sh:


[BUG] Star count is always zero

Describe the bug
Star count is always zero. GitHub must've changed their HTML in a way that broke this extension. There is already a PR open to fix this: #26.
To Reproduce
Check any repo.
Expected behavior
Accurate star count is retrieved and used in grading.
Screenshots

Extension Version
0.3.1
Desktop (please complete the following information):

OS: MacOS
Browser: Chrome
Version: 105

I have merged the PR related to this.


Missing $DESTDIR in the install statements

https://github.com/uNetworking/uWebSockets/blob/master/Makefile#L37

You can set prefix to /use/local or /usr

Makefile should contain $(DESTDIR)$(PREFIX)

Destdir and prefix are virtually identical - do you have a problem using the prefix? I prefer a small minimal Makefile

Destdir and prefix are virtually identical

No. They are different.
DESTDIR is the stage directory where the project is being temporarily installed, ex. /tmp/my-build-dir/uNetworking
PREFIX is intstallation prefix, ex. /usr/local

Other than die hard fanatism, do you have any problem achieving your desired goal with the current Makefile?

Other than die hard fanatism, do you have any problem achieving your desired goal with the current Makefile?

$(DESTDIR)$(PREFIX) is what makes all GNU make projects install properly on all systems when stage directory is used. Stage directories are always used when packages are built. The the problem from my OP breaks packageability.

Since this is a simple header-only project with a Makefile that literally just cp a folder to a particular directory, you can use prefix to specify exactly where things should go.
I get that more complex projects that want to be GNU-compatible and all that Stallman crap could have DESTDIR but this project really is nothing but one folder of headers - you don't even need a Makefile at all, it's standard C++ files in a folder even for non-Stallman Micro$oft Windows.
The point of the Makefile is basically to have a simple way of building example apps, if I add more GNU features soon we'll have autoconf and all kinds of shit.
Sure, we could add DESTDIR, but I have a real hard time understanding how this really affects your package building - you still need some kind of script calling make, so just put CP in that script and bypass the Makefile entirely. That's why I call this fanatism - because I know for a fact its very possible to do without.

Alright I added it

Thank you,


Error message not clear when files are missing - Cannot read property 'success' of undefined

Summary
This may be a duplicate although I didn't specifically see this case. Running this command fails:
Using specified username myusername

ERROR running force:source:deploy:  Cannot read property 'success' of undefined

I checked sfdx.log, although even at trace level it is unfortunately useless.
After scratching my head for a while, I decided to try this:
sfdx force:source:convert -r force-app/main/default
ERROR running force:source:convert:  Expected file at path: /Users/mrossner/Dev/systemu/deploy/digital-platform-sfcore/force-app/main/default/translations/fr.translation-meta.xml.xml-meta.xml

And sure enough I got a more coherent error message. I'm not sure exactly what's missing but I deleted that file just to see if that would fix the issue and it does. Although force:source:deploy should be capable of giving the same error message.
"Cannot read property 'success' of undefined" is a useless generic message, it's the equivalent of someone telling me they got a NullPointerException with no stack trace, I'm completely lost.
Steps To Reproduce:
If I have some time I can try to make this reproducible with Dreamhouse, although I assume just create an xml file in that location and deploy does not like it.
Expected result
I should get an error message that actually tells me what went wrong.
Actual result
I get a useless generic message: ERROR running force:source:deploy:  Cannot read property 'success' of undefined
Additional information
sfdx-cli/7.75.1-5585088c75 darwin-x64 node-v12.18.3```

```sfdx plugins --core
@oclif/plugin-autocomplete 0.1.5 (core)
@oclif/plugin-commands 1.3.0 (core)
@oclif/plugin-help 3.2.0 (core)
@oclif/plugin-not-found 1.2.4 (core)
@oclif/plugin-plugins 1.9.0 (core)
@oclif/plugin-update 1.3.10 (core)
@oclif/plugin-warn-if-update-available 1.7.0 (core)
@oclif/plugin-which 1.0.3 (core)
@salesforce/sfdx-trust 3.4.3 (core)
alias 1.1.2 (core)
analytics 1.12.1 (core)
b2bcc-sfdx-plugin 0.0.1 (link) /Users/mrossner/Dev/ccrz/B2BCC-SFDX-Plugin
config 1.1.8 (core)
generator 1.1.3 (core)
salesforcedx 49.13.1
├─ templates 49.10.0
├─ custom-metadata 1.0.10
├─ @salesforce/sfdx-plugin-lwc-test 0.1.7
├─ apex 0.1.1
└─ salesforce-alm 49.12.2
sfdx-cli 7.75.1 (core)
sfdx-wry-plugin 0.0.11 (link) /Users/mrossner/Dev/sfdx-stuff/sfdx-wry-plugin

OS is OSX 10.15.7

This is fixed with the most recent CLI (7.76.1) and salesforcedx plugin (v50.1.1)

run sfdx plugins:uninstall salesforcedx then sfdx update

thanks for the quick response. I thought I had already updated, will try that again.


GROOVY-8858: Refine GCL to avoid occupying Permanent Area/Metaspace repeatedly for same source code

Yay!


GPU support for OD metrics

Added device support for calculating Model Overview metrics for OD
Description

Checklist

[ ] I have added screenshots above for all UI changes.
[ ] I have added e2e tests for all UI changes.
[ ] Documentation was updated if it was needed.

Codecov Report

Merging #2266 (b906ae2) into main (f6091d3) will decrease coverage by 13.39%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##             main    #2266       +/-   ##
===========================================
- Coverage   89.06%   75.68%   -13.39%
===========================================
  Files         129       14      -115
  Lines        7363     1242     -6121
===========================================
- Hits         6558      940     -5618
+ Misses        805      302      -503

Flag
Coverage Δ

unittests
75.68% <100.00%> (-13.39%)
:arrow_down:

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

Files Changed
Coverage Δ

..._vision/rai_vision_insights/rai_vision_insights.py
78.65% <100.00%> (+0.04%)
:arrow_up:

... and 115 files with indirect coverage changes


Chores/bump version

Use ActiveRecord::LockWaitTimeout
Change the mysql connection name check
Revert the logging stuff - it was fine.

Sorry!


Font used in UI

I am curious which font is used in the screenshots for the UI. Sadly the dropdown overlaps the font name but it ends with "Text".

Does someone knows / remembers its name?

Hi @marcorieser, it is detected by most applications as .SF NS Text which stands for Apple‘s main system font family called San Francisco. Unfortunately it is closed source, but you can simply create an Apple account and download it from their developer resource page.
I try to take screenshots like this on my macOS system to achieve the most “crisp“ font and UI rendering. Their rendering engine is (unfortunately) still unbeaten compared to most open source implementations and results in beautiful screenshots in combination with this typeface.
My other systems are running Arch Linux (server & desktop) with GNOME and AwesomeWM (desktop only) and if you're looking for an fantastic UI font family I can absolutely recommend Inter UI that is open source.

@arcticicestudio Thank you very much.