text:
Add operation for withdrawal_credentials change operation

What?
New operation and signed message is proposed for Eth2, BLSSetWithdrawal, which could permanently change withdrawal_credentials:
BLSSetWithdrawal
class BLSSetWithdrawal(Container):
    bls_withdrawal_pubkey: Bytes32   # Reveal of withdrawal public key
    withdrawal_credentials: Bytes32  # New withdrawal credentials, shouldn't start with BLS_WITHDRAWAL_PREFIX (0x00)
    validator_index: ValidatorIndex

And SignedBLSSetWithdrawal message:
SignedBLSSetWithdrawal
class SignedBLSSetWithdrawal(Container):
    message: BLSSetWithdrawal
    signature: BLSSignature  # Signed by withdrawal BLS key

Why?
It's already confirmed that at least one extra withdrawal target option will be supported with merge of PR #2149. While new validators could submit deposits using this option, there were already tons of deposits before this PR was merged and some of their owners could be interested in Eth1 withdrawal. Moreover, for some parties it could be a best flow of withdrawal control during validator lifecycle to start with BLS key 0x00 withdrawal credentials and change it's target to Eth1 address later with 0x01 or another options introduced in future.
How?

we verify that current validator’s withdrawal_credentials is started with BLS_WITHDRAWAL_PREFIX (0x00)
we verify that new credentials are  not started with BLS_WITHDRAWAL_PREFIX (0x00)

There are several assessments when choosing such behavior of this operation:

Why don’t allow change to another BLS public key? There are 2 most obvious usages for 0x00 to another 0x00 swaps:

Validator's withdrawal key was compromised. For some validators it would mean the validator signing key could be under attack too and the safest way is to withdraw now. Changing credentials to explicit target works in the safest way in this case
Validators could be traded on some market by withdrawal pubkey change. Currently there is no mechanism to change validator's signing key and it's not known whether it will be introduced in future. Also it provides additional load on beacon chain network and block size making this type of message to fight for its place under the sun with Deposit, Attestation and other more important network message types.

Whether to check that withdrawal_credentials is in the currently supported range. The answer should be “no”, as the deposit contract already doesn’t check it. It’s a kind of risk for the minutest number of user errors, but by changing this we could open a way to a number of bugs that could affect all users.

Draft implementation:
def process_bls_set_withdrawal(state: BeaconState, signed_bls_set_withdrawal: SignedBLSSetWithdrawal) -> None:
    set_withdrawal = signed_bls_set_withdrawal.message
    validator = state.validators[set_withdrawal.validator_index]
    # Verify the validator has BLS pubkey commitment
    assert validator.withdrawal_credentials[:1] == BLS_WITHDRAWAL_PREFIX
    # Verify the validator is active
    assert is_active_validator(validator, get_current_epoch(state))
    # Verify exit has not been initiated
    assert validator.exit_epoch == FAR_FUTURE_EPOCH
    # Verify new withdrawal credentials doesn't start with BLS_WITHDRAWAL_PREFIX
    assert set_withdrawal.withdrawal_credentials[:1] != BLS_WITHDRAWAL_PREFIX
    # Verify BLS pubkey reveal is correct
    assert hash(set_withdrawal.withdrawal_pubkey)[1:] == validator.withdrawal_credentials[1:]
    # Verify signature
    domain = get_domain(state, DOMAIN_BLS_SET_WITHDRAWAL, get_current_epoch(state))
    signing_root = compute_signing_root(set_withdrawal, domain)
    assert bls.Verify(set_withdrawal.withdrawal_pubkey, signing_root, signed_bls_set_withdrawal.signature)
    # Update withdrawal credentials
    validator.withdrawal_credentials = set_withdrawal.withdrawal_credentials

Some concerns
We have two options here, and I'm not sure, which way should we go:

allow change of credentials only for validators that doesn't initiate the exit
allow change of credentials for exited validators

Second option requires extra processing of withdrawals after withdrawal_credentials are changed for already exited validators. It’s not straightforward and requires thoughtful implementation to avoid bugs. For example, when we have 2 active withdrawal options, we should verify that one was not processed before withdrawal_credentials change, though Eth1 withdrawal is planned to be automatically on validator exit without extra messages on Beacon Chain, while BLS key withdrawal will require new message with processing.
Some important notes

this approach means once withdrawal_credentials are changed from BLS_WITHDRAWAL_PREFIX (0x00) to any other, withdrawal target could not be changed anymore. But this is already concreted by PR #2149
BLSSetWithdrawal could be added already, as nothing prevents to submit withdrawal_credentials to Deposit Contract today with a prefix other than BLS_WITHDRAWAL_PREFIX (0x00)

Links
Simple eth1 withdrawals (beacon-chain centric) with BLSSetWithdrawalAddress proposal by @djrtwo inspiring this issue
Eth1 withdrawal credentials (0x01) #2149 by @djrtwo - PR merged in specs
Withdrawal credential rotation from BLS to Eth1 - some alternative approaches of withdrawal credentials change
Allow withdrawal_credentials to point to an eth1 address #2040 by @dapplion - Issue to add eth1 withdrawal prefix

Regarding your points about not allowing a different set of withdrawal credentials with BLS:

Validator's withdrawal key was compromised. For some validators it would mean the validator signing key could be under attack too and the safest way is to withdraw now. Changing credentials to explicit target works in the safest way in this case

If the withdrawal key is compromised I think we have to accept that the funds protected by that withdrawal key are likely to be lost.  This is especially the case given that in the vast majority of cases compromise of the withdrawal key implies compromise of the validator key as well.

Validators could be traded on some market by withdrawal pubkey change. Currently there is no mechanism to change validator's signing key and it's not known whether it will be introduced in future.

As soon as we have the ability to assign an Ethereum 1 address to a validator it creates a market, as it is trivial to target a smart contract that can disburse funds as it sees fit.

Also it provides additional load on beacon chain network and block size making this type of message to fight for its place

I think that this is the critical item, and the reason why changing withdrawal credentials should be a one-time operation.
Regarding the state of the validator to allow this operation, I think that it should only apply while the validator is active.  Otherwise we move in to areas of race conditions / potential impact of censorship of the operation and the like.  And, as you mention, it potentially restricts the exit process with this additional complexity.

Thanks for the comment

If the withdrawal key is compromised I think we have to accept that the funds protected by that withdrawal key are likely to be lost. This is especially the case given that in the vast majority of cases compromise of the withdrawal key implies compromise of the validator key as well.

I mean the case when it was probably compromised, or some hackable keystore gone, and your validator is still under control, but it's under the risk in the near future.

+1 on designing withdrawal-credential changes as a one-time operation scoped only to those with 0x00 creds. There aren't obvious use cases for this beyond allowing staking pools that launched prior to 0x01 to switch over so the generality doesn't seem worth the congestion/avenue for DoS vectors.

That's a great way to introduce key rotation for staking pools that want to reduce their reliance on custodial or semi-custodial solutions.
I think that withdrawal credential compromise scenario shouldn't be a factor when evaluating the proposed solution. If it helps, it's a good side effect, but the setting where it matters is pretty convoluted IMO.
Re: allow change of credentials for exited validators, I think that if it's not too much work it should be implemented (mainly to the benefit of slashed validators owners), but it's a low-value feature. Only working with active validators is good enough.

That's a great way to introduce key rotation for staking pools that want to reduce their reliance on custodial or semi-custodial solutions.

Note that this proposal does not allow a change of validator key, so wouldn't help much in this situation.

That's a great way to introduce key rotation for staking pools that want to reduce their reliance on custodial or semi-custodial solutions.

Validators are not custodians though.

Hello guys, is this proposal still being discussed currently ? How likely is it to be implemented ?


text:
Why are validator balances no longer part of ValidatorRecord?

Validator_balances was separated into its own UInt64 array, rather than being part of ValidatorRecord. What was the thought process behind this decision?
'validator_registry': [ValidatorRecord],
'validator_balances': ['uint64']

It's an optimisation to minimise the amount of hashing when computing the beacon state root. The validator_registry (which contains most of the state) changes slowly and requires little hashing effort to maintain. The validator_balances is a smaller part of the state with much higher churn, hence why it is segregated.

Thank you!

source: gharchive/issue

authors: JustinDrake akhila-raju

license_type: permissive

license_source: github-api


text:
MAX_PERSISTENT_COMMITTEE_SIZE -> TARGET_PERSISTENT_COMMITTEE_SIZE

replace #1325

close in favor of #1358

source: gharchive/pull-request


text:
fix a typo: use TIMELY_HEAD_WEIGHT instead of _INDEX

Seems to be a typo in PARTICIPATION_FLAG_WEIGHTS: TIMELY_HEAD_FLAG_INDEX used, while other elements are of _WEIGHT kind

a duplicate of #2419


text:
POC for issue 1035 - better correlation between requests and responses.

Fixes https://github.com/ethereum/py-evm/issues/1035
What was wrong?
STUB:
How was it fixed?
Cute Animal Picture

replaced by #1063 and #1089

repo: ethereum/py-evm

license: MIT


text:
Added the host address parameter to the JSONRPCClient.init

for #117

Coverage remained the same at 50.473% when pulling f74524e7ec13c3c80956c6ca1056e4c4499404c1 on RomanZacharia:rpc_client into 2f086d2634595cf081c00c9794553027de272e99 on ethereum:develop.

see #118

authors: RomanZacharia coveralls konradkonrad

repo: ethereum/pyethapp

license: mit

license_source: bigquery


text:
Remove unused cargo dependencies

What was wrong?
Unused dependencies in some workspace crates.
How was it fixed?
Ran cargo-udeps to remove unused dependencies.
To-Do

[ ] Add entry to the release notes (may forgo for trivial changes)
[ ] Clean up commit history

partying_face is there any way to leverage cargo-udeps in our ci pipeline?

It requires rust nightly, not sure if we want to add a nightly pipeline only for cargo udeps, shall we?

@ogenev Nah, i don't think it's worth it for now. periodically running cargo udeps locally seems sufficient

authors: njgheorghita ogenev

repo: ethereum/trin


text:
Beta 2 release

Goal of the milestone: code cleanup and bugfix release. Release before end of August
Bugs
New features

[ ] delete account #302
[x] import raw pk

Refactoring

[ ] use stateless redux, extends of classes extends React.Component
[ ] refactor state zones - #234
[ ] check syntax with eslint

Other

[x] introduce unit tests for ui
[ ] builds scripts with grunt - #228
[ ] make builds only when deploying
[ ] use prebuilds Emerald Vault binaries, instead of compilation

next #326

repo: ethereumproject/emerald-wallet


text:
batchstore, kademlia: add radius as depth upper bound

This PR wires in the postage radius of responsibility into kademlia as an upper bound of the neighborhood depth, paving the way for agreement between connected neighborhoods and data persistence responsibility.

deepsource complaints addressed in a different PR

repo: ethersphere/bee


text:
Fix horizontal scrollbar not appearing for code editor in scratch view

We have word wrap on now, but we should figure this out anyway and maybe make word wrap a user option instead

The scrollbar exists..not sure why I thought it didn't


text:
Configurable psc executables

I'd like to be able to use psa with this. Could we maybe allow for a configurable executable, with additional args?

Good call. I think this would be handy.

Supported in: purs-loader@0.6.0-beta.4 and purescript-webpack-plugin@0.2.0-beta.5

authors: ethul natefaubion

repo: ethul/purescript-webpack-plugin


text:
Remove "Reset suggestions" option from dictionary toggle

Also remove the accompanying code that makes it work.

moving to done

authors: Roger-Ethyca TheAndrewJackson

repo: ethyca/fides


text:
language/resources/.md

Still have to do Qualifier and Policy, but might as well get a PR going.

@iamkelllly there were wild conflicts here, i did my best!

authors: ThomasLaPiana dougfulton


text:
Initial Fidesops Merge

Closes #995
Dealing with two repos
There are two pieces here, the first is the initial merge, and the second is the ongoing merging of those remote repositories into this one to continue keeping compatibilty.
Commands used to execute the merge:

git remote add fidesops https://github.com/ethyca/fidesops.git
git fetch fidesops --tags
git merge --allow-unrelated-histories fidesops/main

Commands used to keep parity with remote repos:

git pull --all (you should see it pull from both origin as well as fidesops
git merge origin/main & git merge fidesops/main

Once the final merge is deemed complete, we'll need to run git remote remove fidesops

Code Changes

[x] do the git merge and clean up any conflicts
[x] copy/pasta the frontend_test workflow
[x] fix/consolidate docker builds
[x] merge the alembic migration histories
[x] consolidate nox commands
[x] consolidate pr_checks
[x] add the fides worker command to run a worker

Steps to Confirm

[x] all workflows pass except for the fidesops tests

Pre-Merge Checklist

[ ] All CI Pipelines Succeeded
Documentation Updated:

[ ] documentation complete, or draft/outline provided (tag docs-team to complete/review on this branch)
[ ] documentation issue created (tag docs-team to complete issue separately)

[ ] Issue Requirements are Met
[ ] Relevant Follow-Up Issues Created
[ ] Update CHANGELOG.md

Description Of Changes
The goal of this PR is two-fold:

Prove that the merger can be done in an elegant way
Merge the code (not necessarily the products) and get all tests passing

Once those two goals are completed, there will be a slew of follow-up tasks to properly unify the products, with generally one issue per update
Things to do after this issue:

Docs Merger
Frontend Merger
Server Merger (a single main.py)
Config Merger (combine the logic for loading in the config values)
Re-implement optional dependencies

working on getting the conflicts fixed (29), going well so far, will push up when finished

it looks like using docker-compose up --wait wasn't working with the compose version in the workflow runners so I converted all of them to docker compose up --wait in the hopes that the version would support it

got tests passing, now going to do the heavy lift of merging the servers....

ok with the current state of the tests, going to go ahead and merge and then pop open all of the follow-up issues


text:
Failing unit tests under ROS Jade.

[----------] 2 tests from checkGetCentroid
[ RUN      ] checkGetCentroid.triangle
/home/peter/jade_ws/src/grid_map/grid_map_core/test/PolygonTest.cpp:33: Failure
Value of: centroid.x()
  Actual: 0.83333333333333326
Expected: expectedCentroid.x()
Which is: 0.5
[  FAILED  ] checkGetCentroid.triangle (0 ms)
[ RUN      ] checkGetCentroid.rectangle
/home/peter/jade_ws/src/grid_map/grid_map_core/test/PolygonTest.cpp:47: Failure
Value of: centroid.x()
  Actual: -0.4907407407407407
Expected: expectedCentroid.x()
Which is: -0.5
[  FAILED  ] checkGetCentroid.rectangle (0 ms)

Fixed with 60ecceebe49ecd032ff9368eea492caa971ec064.


text:
Vision related UDFs

Provide UDFs for easy operations on image and box2d

This is supporting the image notebook demo

This is supporting the image notebook demo

Thanks @changhiskhan . added docstring for (0, 0)

Thanks @changhiskhan . added docstring for (0, 0)

repo: eto-ai/rikai


text:
Explicitly type-casting minimum-severity parameter to integer

Possible fix for #121

Thanks @michielrensen!

authors: michielrensen morria

repo: etsy/phan


text:
Optimize graphics

This also strips metadata from the images. Similar effort has been made before in #26, so this time overall package size didn't change that much, though it's still a bit smaller. Packaged with zstd the difference is about 200KB (18.9 -> 18.7 MB).
Tool used: optipng.
Flags: -o7 -zm 1-9 -strip all.

I'm still in the process of finishing up a PR that does touch some of these files. For the sake of avoiding having to deal with another merge conflict, it would be better to hold off on this. More so since I'm adding new images that could probably stand to be optimized themselves.

that is why i did not merge this

repo: etternagame/etterna


text:
serialstream reade/write implementation must comply in raised effects…

… to StreamObj
fixing error of readDataImpl: spReadData:
Error: type mismatch: got <proc (s: Stream, buffer: pointer, bufLen: int): int{.gcsafe, locks: .}> but expected 'proc (s: Stream, buffer: pointer, bufLen: int): int{.gcsafe.}'
.raise effects differ

Well that was an easy fix 👍 Thanks very much!

On 24 Jul 2019, at 09:53, LucaWolf notifications@github.com wrote:
… to StreamObj
fixing error of readDataImpl: spReadData:
Error: type mismatch: got <proc (s: Stream, buffer: pointer, bufLen: int): int{.gcsafe, locks: .}> but expected 'proc (s: Stream, buffer: pointer, bufLen: int): int{.gcsafe.}'
.raise effects differ
You can view, comment on, or merge this pull request online at:
https://github.com/euantorano/serial.nim/pull/21
Commit Summary
serialstream reade/write implementation must comply in raised effects to StreamObj
File Changes
M src/serial/private/serialport/serialport_common.nim (2)
Patch Links:
https://github.com/euantorano/serial.nim/pull/21.patch
https://github.com/euantorano/serial.nim/pull/21.diff
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

I’m at work right now, but I’ll create a new version release when I get home.

authors: LucaWolf euantorano


text:
mUU rev14

macOS Updater Utility revision 14:

Added support for macOS Sequoia
Fix for users not being prompted on major upgrades
Enhanced logic to reset counters (deferrals or deadline timer) on mUU profile reinstallation

Signed-off-by: Matt Zaske <mzaske@omnissa.com>

closing - need to fix commit DCO

repo: euc-oss/euc-samples


text:
3Dサウンド使用時にエラーが出る

[x]  環境によって出力、入力チャンネルが変わるので対応
[x]  いくつかのチャンネルで試す

とりあえず解決した

repo: eugene-hanada/EugeneLib


text:
Warn user on a dirty commit

Is your feature request related to a problem? Please describe.
The commit in the job description may not be accurate, for example, if there are uncommited changes.
Describe the solution you'd like
When submitting the job, if the commit is dirty warn the user. If they are aware and wish to continue, slutil should allow it but mark the commit as dirty, maybe like:  COMMIT: abc123[d] where [d] shows it dirty.
Describe alternatives you've considered
Ignoring this and making the user take responsibility.

This should be as unintrusive as possible, adding [d] to the commit tag is sufficient. For now, append to string. maybe consider a smarter implementation in a future release

repo: eugene-prout/slutil


text:
New code changes for BAEL-698

New code changes for BAEL-698

Closing this PR as it is no longer relevant.

repo: eugenp/tutorials


text:
Add method signature code

Code sample to illustrate what is a method signature.

No relevant.

I please stop sending me information.
On Tue, Aug 11, 2020 at 3:52 PM Jonathan Cook notifications@github.com
wrote:

Not relevant.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/eugenp/tutorials/pull/9617#issuecomment-671927371,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJLG7DYIO57N3WEKJH2NEGTSAE5IVANCNFSM4OLZ3GVA
.

authors: JonCook corlaez sergioKon


text:
Účto Predvolené texty - počet

Dá sa v programe - užívateľsky - zvýšiť počet predvolených textov, ktoré sa zobrazia na výdavkom pokladničnom doklad - cez šedú ikonu? Aspoň na 20.

je to neobmedzene, skusal som 21, nie je problem ale...
po 20 polozke uz musi odskrolovat lebo na mojom displayi ta 21. polozka je uz pod spodnou hranou obrazovky
uzivatelovi sa moze zdat ze max 20


text:
Rename to scipy_doctest

Also,

run ruff, fix violations
update pyproject.toml: trove classifiers etc
bump version: 0.1 is prehistory (before pytest layer); 1.0 was tagged a while ago; what is now is working towards 1.1

Something fishy is going on with local files under pytest, xfail for now (https://github.com/ev-br/scpdt/pull/153/commits/902e2e824b9fe41e6a6a0d995ee22b39192006b9) to keep the ball rolling.

repo: ev-br/scpdt


text:
add unified jna test + add nio filechannel test

This PR adds unified JNA solution + an alternative NIO solution. The NIO solution is basically the JNA solution with the JNA system calls replaced by NIO FileChannel operations.

Sysfs2 is currently broken + there's the bug in the benchmark code itself. I can fix this too, if necessary.

I forgot -- both JNA and NIO solutions now use UTF-8, the encoding choice might not matter much.

rationale for that opinion: if the non-cached JNA to cached JNA time ratio is about 3, the majority of the time is probably spend doing the native call and not the encoding operation itself.

hmmm, also: SysfsNIO2 is not using the API called NIO2, it's just a way of differentiating from Sysfs2 (I would call that "SysfsNIO1").

I replaced the obsolete JNA implementations with a single NIO-based one presented in https://github.com/ev3dev-lang-java/ev3dev-lang-java/issues/748#issuecomment-743859055.

After few days with no changes in the NIO solution, I am going to close the PR.
I will clean manually the JNA files and associated changes in branch sysfs_perf
I will add the .py script to review with current NIO solution.

I don't understand, the NIO alternative is a replacement for the JNA1/2/3 proposals.

authors: JakubVanek jabrena


text:
Randomness and Cmd interaction

Hi! First of all, I love the idea of this repo, and I am using to learn elm :D
I am having problems getting randomness into my "game". I think that the problem is that game function doesn't allow me to modify the returned Cmd of the update function (this line), required in order to generate a random value.
Am I getting something wrong? Is there any workaround to getting access to the Cmd?
Thank you!

That is exciting to hear! 😊
What are you wanting to use randomness for specifically? That can help a lot in designing features in the future.
For now, there is not a way to add randomness with the Random module. I wanted to keep it really minimal, and that API is pretty fancy for what I was going for here.
If I wanted to spawn spaceships at some unknown x coordinates, I would probably do something like cos (spin 0.1 time) whenever I wanted a new ship. It is "very predictable" and "not random at all" but it could seem unpredictable if it is happening on some user input.

Hi @evancz,
I am using the randomness for initializing a population of entities randomly in the map (their positions) and move them along their lives randomly, so I need for each frame some kind of randomness.  Currently, I am using the Random.step (that does not need the interaction of the Cmd) and passing the generated seed to the next Random.step.
I like the idea you said of using the time for getting the first random seed in order to generate different populations each time you run the "game".
Thanks! :D

authors: evancz lemunozm

repo: evancz/elm-playground


text:
🛑 www.actionherojs.com is down

In e0c2812, www.actionherojs.com (https://www.actionherojs.com) was down:

HTTP code: 0
Response time: 0 ms

Resolved: www.actionherojs.com is back up in 5ea60ce.

repo: evantahler/upptime


text:
Threshold for Standby Power in Visualisation.

Mir gefällt das Design immer noch hervorragend - selbst nach einer Woche! 😁
In meinem Fall (bin da vielleicht auch eine Ausnahme) zieht die WB im Standby auch etwas Strom und das erscheint dann in der UI als kleiner Punkt. Ich verstehe die Idee des Punktes, aber evtl. macht es Sinn, unterhalb bestimmter Leistungen den jeweiligen Verbraucher in der Grafik vielleicht ganz zu unterschlagen?

Originally posted by @Alestrix in https://github.com/evcc-io/evcc/issues/2889#issuecomment-1120478942

@premultiply Bei den Smarthome Steckdosen ignorieren wir schon über den standbypower Parameter niedrige Ströme.
Siehe bspw: https://github.com/evcc-io/evcc/blob/a7f9f8bfda45f9da97bd480ff2edcdecb7e38365/charger/fritzdect.go#L145

Ist das jetzt im Code geändert? Ich hab das bei mir zwischenzeitlich durch ne jquery in der evcc Config gelöst.

authors: Alestrix naltatis thierolm

repo: evcc-io/evcc


text:
Fix eslint packages to have correct peerDeps/deps

Some packages that should have been hard dependencies were in peer, and packages that were extending from other packages were requesting the sub-dependencies as its own peer, so this diff is correcting that.

@BenAtEventbrite @gagoar I'm rethinking this approach and this might need more discussion.
The original issue came from core:
warning "eslint-config-eventbrite@4.1.0" has unmet peer dependency "babel-eslint@^7.0.0".
warning "eslint-config-eventbrite@4.1.0" has incorrect peer dependency "eslint@^3.0.0".
warning "eslint-config-eventbrite@4.1.0" has unmet peer dependency "eslint-plugin-import@^2.0.0".
warning "eslint-config-eventbrite-legacy@3.0.0" has incorrect peer dependency "eslint@^3.0.0".

The issue with these packages being peerDeps, as plugins generally are, is that we want a single copy at top level. But with yarn's flat structure, dependencies are already deduped at the root level, avoiding the need to define these, and some package seem to adopt this model. This also solves the issue if we down the road we end up adding a conflicting eslint config/plugin (although that's less likely). But alternatively, we can just add all the peers to core as a dev dependency, or to loosen the requirements to be >=, example.

the only thing that might need to change is babel-eslint, i.e., should the configuration dictate which parser to use?

The configuration does depend on a certain parser to work, but it can likely be more relaxed than what the current peer dependency setting is. Generally peer dependencies can use >= vs. ^ because they only depend on little bits

per offline convo, closing this and moving this to core.

authors: benmvp kaylieEB

repo: eventbrite/javascript


text:
chore: bump version of node bot in release workflow

Why
Semantic release bot only runs on node >= 18 and we were using node 14.
How
Bumped the version of node in the workflow
Checklist

[x] Commit messages are formatted as per the convention, and breaking changes are marked

:tada: This PR is included in version 3.6.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

authors: e-moran shanecurran

repo: evervault/evervault-node


text:
feat(Volume Servicebroker) Added Framework Capability for Volume Serv…

…icebroker and made several bugfixes

I changed the base to develop.

authors: jheyl yremmet

repo: evoila/cf-service-broker-core


text:
Unsubscribed user still receives notifications (topics)

Hi
I'm using:
"react-native": "0.53.3",
"react-native-fcm": "^14.1.3",
"react": "16.2.0",
When a user logs out the app also does an unsubscribe from topics. But user still receives the notifications. How come?
thanks!

perhaps firebase has a delay? does it persist after a while

hmm I don't know. but will add this to my tests. send notif, unsubscribe, send again. thanks!

authors: dhcmega evollu

repo: evollu/react-native-fcm


text:
No annotation processors set if task configuration evaluated early

I checked this new plugin with latest Gradle 6. It is almost working :) I like how simple it is now, but there is one issue: no annotation processor is set if task configuration is evaluated (too) early.
You can test that using your QuerydslPluginTest class, just add:
project.tasks.getByName("compileQuerydsl")

before
extension.jpa = true
extension.jdo = true

in setup(). Then check content of project.tasks.getByName("compileQuerydsl").options.compilerArgs

Can you please provide some more information. Is this causing issues within your builds or is it just a specific issue with the unit tests. Can you provide a simple example project that showcases the problem?

It was causing issues in my build. I can't provide simple example, my project is big and complex. I was able to pinpoint the root cause, it can be simulated in the unit test.
Task should read parameters as late a possible. Now it is configured fully when plugin is applied. Just put break point somewhere in:
https://github.com/ewerk/querydsl-plugin/blob/d5b53e8ab02c90d56d4f7ed0c4e103c9680ef63c/src/main/groovy/com/ewerk/gradle/plugins/querydsl/QuerydslPlugin.groovy#L84-L114
You will notice that it is run earlier in the lifecycle if you add something like project.tasks.getByName("compileQuerydsl") in the build script.
Unfortunately I can't test help you, I'm not using your plugin anymore. With latest Gradle annotationProcessor "com.querydsl:querydsl-apt:${querydslVersion}:jpa" is enough for me. Thank you for great work, this plugin server me well for years! :)

@kmaterka As you have narrowed down the issue so close, would it be possible the provide an PR with the fix?

As I wrote, I no longer use this plugin as it is an overkill for me, I need only one annotation processor and Gradle 6 serves me well.
The issue is that you can't assume that plugin configuration is fully setup during evaluation phase. You need to post-pone configuration as late as possible, for example in QuerydslPlugin::configureTasks use:
task.doFirst {
  task.options.compilerArgs += [
    "-proc:only",
    "-processor", querydslPlugin.processors()
  ]
  if (querydslPlugin.aptOptions.size() > 0) {
    for (aptOption in querydslPlugin.aptOptions) {
      task.options.compilerArgs << "-A" + aptOption
    }
  }
}

It should help, but I'm not 100% - unfortunately I have no time to write proper test, QuerydslCompileTest looks unfinished.
Alternatively create setters for each parameter in QuerydslPluginExtension and update task configuration on each update.
Alternatively override doFirst in QuerydslCompile:
class QuerydslCompile extends JavaCompile {
  @Override
  Task doFirst(Action<? super Task> action) {
    def querydslPlugin = getProject().extensions.findByType(QuerydslPluginExtension)

    options.compilerArgs += [
      "-proc:only",
      "-processor", querydslPlugin.processors()
    ]
    if (querydslPlugin.aptOptions.size() > 0) {
      for (aptOption in querydslPlugin.aptOptions) {
        options.compilerArgs << "-A" + aptOption
      }
    }

    return super.doFirst(action)
  }
}

You can also override configure, which seems a better place for task configuration than QuerydslPlugin (or not, iterating source sets is probably better in the plugin).
BTW, you can add distributionType to build.gradle.kts, it will help you with code completion:
  wrapper {
    gradleVersion = "5.0"
    distributionType = Wrapper.DistributionType.ALL
  }

Hi,
I am interested in using the new version. Is there anything I can do to close this? Seems like this is the only issue blocking a v2 release.

Closing issue as repository is going to archived mode.

repo: ewerk/querydsl-plugin


text:
Model Performance Tracking: MLFlow

Consider using another tool (e.g., MLFlow) to track the performance of models during a run

On further thought, this is something outside of the scope of colmena for now. We want to keep it agnostic to specific ML tools to simplify the codebase and limit dependencies.

repo: exalearn/colmena


text:
Close menu when deselecting

Steps:

select shape and open properties menu
click away to deselect (which closes the menu)
select some element, which opens the menu again

IMO this is non-intuitive (and it tends to use the same tap you used to select an element for clicking a button in the menu if it happens to be under pointer --- I tested this on devTools emulation only, so it may not be what's happening on real device).

This could be fixed by setting the current menu to null when deselecting objects.

Seems like this is not relevant anymore

authors: alex-kim-dev dwelle j-f1

repo: excalidraw/excalidraw


text:
fix: don't bind text to container if already present

fixes https://github.com/excalidraw/excalidraw/issues/4895
https://user-images.githubusercontent.com/11256141/159300607-57c97096-a576-4658-bcc8-3744d46cea37.mp4

Cool. Let's add a test for this in src/element/textWysiwyg.test.tsx?


text:
[BUG] Add image in streaming mode with exceljs

I'm developing a reporting system. In study the exceljs library I verified that the streaming mode due to the volume of data, and in the tests it would suit me and it really suited me perfectly.
However, I have a problem, it does not let you add an image to the worksheet. returning the worksheet.addImage error is not function. Does anyone know how I can get around this?

I too encounter this limitation.  It works great in Document mode, but I am trying to switch to exceljs for building excel files explicitly for the streaming mode due to massive spreadsheets; but the workbooks I need to generate require a logo in a cell range of each worksheet.  Is this on anyone's radar to add?

we've just added in umongous/exceljs, not sure about pull requesting though, i was unable to get through pre-commit hooks

Is there any update or alternative solution to resolve this issue?

repo: exceljs/exceljs


text:
System.Web.HttpException: The client disconnected.

This error seems to be thrown by the api end points that are hit the most /api/v2/error and has been thrown thousands of times. I've been able to reproduce this error by posting something and then redirecting or navigating away from the page. The post content seems to be posted without issue.
I'm not sure if this is a client issue or what we can do about this but it would be good to get to the bottom of this and see what the best practice is. I do know that some users pass a cancellation token through the controllers or what. But we do want the request to succeed but we don't really care if they are still connected for the response..
During my initial research I came across this:
http://weblogs.asp.net/fredriknormen/asp-net-web-api-exception-handling
http://forums.asp.net/t/1863442.aspx?HttpClient+Error+A+Task+was+canceled+
System.Web.HttpException: The client disconnected.
at System.Web.Hosting.IIS7WorkerRequest.EndRead(System.IAsyncResult asyncResult) at offset 78
at System.Web.HttpBufferlessInputStream.EndRead(System.IAsyncResult asyncResult) at offset 95
at Microsoft.Owin.Host.SystemWeb.CallStreams.DelegatingStream.EndRead(System.IAsyncResult asyncResult) at offset 0
at System.Web.Http.NonOwnedStream.EndRead(System.IAsyncResult asyncResult) at offset 0
at System.Net.Http.StreamToStreamCopy.BufferReadCallback(System.IAsyncResult ar) at offset 8
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task task) at offset 11
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task task) at offset 40
at Exceptionless.Api.Utility.NakedBodyParameterBinding.<ExecuteBindingAsync>d__1.MoveNext() at offset 428 in C:\projects\exceptionless\Source\Api\Utility\Bindings\NakedParameterBinding.cs:line 29:col 17
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task task) at offset 11
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task task) at offset 40
at System.Web.Http.Controllers.HttpActionBinding.<ExecuteBindingAsyncCore>d__0.MoveNext() at offset 160
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task task) at offset 11
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task task) at offset 40
at System.Web.Http.Controllers.ActionFilterResult.<ExecuteAsync>d__2.MoveNext() at offset 143
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task task) at offset 11
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task task) at offset 40
at System.Web.Http.Filters.AuthorizationFilterAttribute.<ExecuteAuthorizationFilterAsyncCore>d__2.MoveNext() at offset 265
at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(System.Threading.Tasks.Task task) at offset 11
at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(System.Threading.Tasks.Task task) at offset 40
at System.Web.Http.Controllers.ExceptionFilterResult.<ExecuteAsync>d__0.MoveNext() at offset 151

This might just be a bot or something trying to hit this endpoint and then disconnecting before sending something.  Or maybe just a normal client aborting a request in the middle.  Or maybe someone trying to send a large post and getting cut off.

from the user agents it's submission clients.

http://aspnetwebstack.codeplex.com/workitem/1797

But how can I handle it? I tried if (exception is OperationCanceledException || exception is HttpException && exception.Message.Contains("The client disconnected"))

You mean in client code or in your own code base? @Marusyk I haven't found a good way to. I think some people pass through the cancelation token to the controller action and pass it through.. But that isn't very pretty.

authors: Marusyk ejsmith niemyjski

repo: exceptionless/Exceptionless


text:
More configuration options for notifications

Time when the daily project summary should be send
Quiet hours
Quiet days (weekend)

It should also be possible to configure the above on organization level, with option to overwrite on selected projects.
Option to get a daily summary on organization level instead for one mail per project.

Currently emails are sent out at 8/9am in your local time zone. The issue is everyones timezone is different on a project and as such you could get them at different times.
How do you see quiet hours working? What should happen to the notifications if you are in quiet time? Most phones / inboxes already keep quiet when receiving email.

You're right. Quiet hours is probably most a luxury that can be handled in other ways.
One way of handelig it could be to send an email with a summary of the events that occurred during the quiet hours. Kind of like the daily summart, but just for that period.

Merging into https://github.com/exceptionless/Exceptionless/issues/69

authors: KasperLK niemyjski


text:
Suppress svg.path element if no children

I need to control the color of the svg collapse indicator using css as I switch between different themes in my app. I can target the color using css like:
svg path {
        stroke: green;
    }

This works, but a side effect is the indicator is visible for nodes with no children.  The no-children <path> is generated with stroke="transparent" but is overridden by the css stroke.
A proposed solution is to not generate the <path> element if there are no children. Change to ListItem.razor:
@if (HasChildren) {
    <path d="M 4 2 l 7 6 l -7 6" class="@(TreeView.Disabled ? "tree-view-disabled" : "")" stroke="@(TreeView.Disabled ? "gray" : "black")" fill="transparent" stroke-width="2" />
}

https://github.com/RobWunderlich/Blazor.TreeViews/commit/6cadd87dec6e4547de7e9fb76a0fc7ef3f972c47
I also added class="tree-view-disabled" for disabled nodes to allow css targeting.

Hi @RobWunderlich,
Thanks for uncovering this. Wouldn't it be easier if we also defined a treeview css class that controls the stroke & fill? I didn't try this out, but something like the following should work:
@{
   var classes = string.Join(";",
      "excubo-blazor-treeview",
      (TreeView.Disabled ? "excubo-blazor-treeview-disabled" : ""),
      (HasChildren ? "" : "excubo-blazor-treeview-nochildren")
   );
}
<path d="M 4 2 l 7 6 l -7 6" class="@classes" />

Default CSS would then be something like
svg path .excubo-blazor-treeview {
   stroke: black;
   fill: transparent;
   stroke-width: 2;
}
svg path .excubo-blazor-treeview-disabled {
   stroke: gray;
}
svg path .excubo-blazor-treeview-nochildren {
   stroke: transparent;
}

Would that enable you to customize the path element correctly?
Thanks,
Stefan

Hi @stefanloerwald,
That would work as well and has the advantage of allowing nochildren to be targeted. I tested the code and made a couple of tweaks. Use " " as the Join separator.
@{
    var classes = string.Join(" ",
    "excubo-blazor-treeview",
    (TreeView.Disabled ? "excubo-blazor-treeview-disabled" : ""),
    (HasChildren ? "" : "excubo-blazor-treeview-nochildren")
    );
}
<path d="M 4 2 l 7 6 l -7 6" class="@classes" />

And the css:
.excubo-blazor-treeview {
  stroke: black;
  fill: transparent;
  stroke-width: 2;
}

.excubo-blazor-treeview-disabled {
    stroke: gray;
    fill: gray;
}

.excubo-blazor-treeview-nochildren {
    visibility: hidden;
}

I prefer visibility: hidden; over transparent color. I think it makes more sense semantically.
Thanks,
Rob

While we're adding classes, can we also add an expanded/collapsed class? It makes sense to me to move the classes up to the <li> like this:
@{
    var classes = string.Join(" ",
    "excubo-blazor-treeview",
    (TreeView.Disabled ? "excubo-blazor-treeview-disabled" : ""),
    (HasChildren ? "" : "excubo-blazor-treeview-nochildren"),
    ($"excubo-blazor-treeview-{(Collapsed ? "collapsed" : "expanded")}")
    );
}
<li class="@Class @classes">

And then the css like this:
.excubo-blazor-treeview svg path {
        stroke: black;
        fill: transparent;
        stroke-width: 2;
}

.excubo-blazor-treeview-disabled svg path {
    stroke: gray;
}

.excubo-blazor-treeview-nochildren svg path {
    visibility: hidden;
}

.excubo-blazor-treeview-expanded {
}

.excubo-blazor-treeview-collapsed {
}

Thanks,
Rob

Hi Rob,
That all looks very good. Would you mind creating a PR for this?
Thanks
Stefan

Hi Stefan,
Created https://github.com/excubo-ag/Blazor.TreeViews/pull/43#issue-1515671561.
I added the string "-item" into the css classes for more clarity.
Thanks,
Rob

Thanks Rob!
I've merged the PR and a new version is now in deployment.
Thanks
Stefan

authors: RobWunderlich stefanloerwald


text:
Incorrecly reformats python code

Describe the bug
context
When I pass in a code block such as below. (notice the indented inner class)

click to expand
1. Add a serializer class

    ```python
    class RecurringEventSerializer(serializers.ModelSerializer):  # (1)!
        """Used to retrieve recurring_event info"""

        class Meta:
            model = RecurringEvent  # (2)!
            fields = (
                "uuid",
                "name",
                "start_time",
                "duration_in_min",
                "video_conference_url",
                "additional_info",
                "project",
            )
            read_only_fields = (
                "uuid",  # (3)!
                "created_at",
                "updated_at",
            )
    ```

expectation
I expected mdformat to either:

ignore the block
leave it alone because it knows that python inner classes are indented from the outer class

bug
But instead it re-indents the inner class to the same level as the outer class.
Here's the output... (where the error is the un-indented inner class code)

click to expand
1. Add a serializer class

    ```python
    class RecurringEventSerializer(serializers.ModelSerializer):  # (1)!
        """Used to retrieve recurring_event info"""

    class Meta:
        model = RecurringEvent  # (2)!
        fields = (
            "uuid",
            "name",
            "start_time",
            "duration_in_min",
            "video_conference_url",
            "additional_info",
            "project",
        )
        read_only_fields = (
            "uuid",  # (3)!
            "created_at",
            "updated_at",
        )
    ```

problem
This is a problem for people creating programming guides because readers can't run the code they copy/pasted from the documentation.
Reproduce the bug

I uninstalled mdformat from my system to to eliminate possiblities.

I have the original text in a file called test.md

click to expand
1. Add a serializer class

    ```python
    class RecurringEventSerializer(serializers.ModelSerializer):  # (1)!
        """Used to retrieve recurring_event info"""

        class Meta:
            model = RecurringEvent  # (2)!
            fields = (
                "uuid",
                "name",
                "start_time",
                "duration_in_min",
                "video_conference_url",
                "additional_info",
                "project",
            )
            read_only_fields = (
                "uuid",  # (3)!
                "created_at",
                "updated_at",
            )
    ```

My pre-commit config for mdformat:

click to expand
  - repo: https://github.com/executablebooks/mdformat
    rev: 0.7.17
    hooks:
      - id: mdformat

There's no plugin being used.

I call the mdformat pre-commit hook on this file
pre-commit run mdformat --files docs/how-to/test.md

List your environment
mdformat revision (from pre-commit config)
0.7.17
❯ python --version
Python 3.11.4
❯ pre-commit --version
pre-commit 3.0.4
OS: Linux Mint 21.1 Vera. Based on Ubuntu Xenial I think.

I'm closing the issue. I ran mdformat without pre-commit and it's doing the correct thing.

repo: executablebooks/mdformat


text:
Minor correction to instruction text for animal-magic instructions.md

The following text instruction does not match the comment after the function, as the text says between and the comment says the value can be equal to zero. Please change the text to "... number equal or greater than 0.0 and less than 12.0".
Implement a GenerateWandEnergy function. The wand energy should be a random floating point number between 0.0 and 12.0.
f := GenerateWandEnergy()  // f will be assigned a random float64, 0.0 <= f < 12.0

This is being discussed in the forum: https://forum.exercism.org/t/minor-correction-to-instruction-text-for-animal-magic-instructions-md/10963

authors: Kristianwhittick andrerfcsantos

repo: exercism/go


text:
Add comparison concept

Part of #1611

Thanks for the review!
Suggestions applied to both files.


text:
Fixed Typo

Replaced "for .. of" with "for...of"

Done!

repo: exercism/javascript


text:
[v3] New concept exercise: lucas-numbers (Enumerators)

This builds on the idea of Enumerables, allows student to learn about creating a generator method that allows infinite enumeration.
Lots of todos left here.

@ErikSchierboom Could you take a review of this at some point pls? I'd entirely forgotten these existed, Tim - sorry!

I'm pretty disconnected from these draft concept exercises — I'm not sure how much value there is in them now, and I don't think I can commit the time at the moment to bring them up to the current standard.
I am very willing to turn them over to someone interested. It might be that they should just get closed if they don't fit the current state of the track.

I am going to leave this as draft, I might be able to look at this later.  (I will put it on my "tickler" list, so if it happens to effect my fancy in that way…)

I am very willing to turn them over to someone interested. It might be that they should just get closed if they don't fit the current state of the track.

I think it would make for a nice exercise, so hopefully someone else will find the time to complete it.

authors: ErikSchierboom iHiD kotp neenjaw

repo: exercism/ruby


text:
Add new exercise: Robot name

We're going to need lots of them :smile_cat:

w00t!

btw -- if there are people who are being helpful in the javascript/ecmascript tracks and you want them to have commit, let me know. You're in a better position to evaluate contributions here than I am :)

authors: kytrinyx rchavarria

repo: exercism/xecmascript


text:
Add HINTS to wordy exercise

As specified in #234.

Thanks again @ErikSchierboom!

authors: ErikSchierboom robkeim

repo: exercism/xfsharp


text:
New tests for the Pangram problem

We have found that the Pangram tests miss edge cases allowing students to pass all of the current tests with an incorrect implementation.
To cover these cases we have added new tests to the Pangram test set. Those new tests were added in this commit
Since this track implements Pangram, please take a look at the new pangram.json file and see if your track should update its tests.
If you do need to update your tests, please refer to this issue in your PR. That helps us see which tracks still need to update their tests.
If your track is already up to date, go ahead and close this issue.
More details on this change are available in x-common issue 222.
Thank you for your help!

The tests are already implemented in the xPHP track, closing.

authors: IanWhitney petemcfarlane

repo: exercism/xphp


text:
Implement basic exercise: averager

[x] Write test cases
[x] Write example solution file
[x] Write empty file for user
[x] Write instructions for exercise

Merged


text:
JsonInput width should shrink beyond minimum content size

Fixes #1083

Thanks!

authors: TomTirapani amcclain

repo: exhi/hoist-react


text:
Minting failed! Please try again!

When trying to mint I am getting the following error:
Minting failed! Please try again!
What can be causing this?
I don't seems to find log to investigate. Where can I find the console log so I could probably share more information.
I was able to setup a different candy matching yesterday and I was able to mint...

Closing this as my issue is gone.

How did you solve it? Im having the same problem

I am also having this problem, but I am unsure of the solution

authors: WildCroc cdric sswils211

repo: exiled-apes/candy-machine-mint


text:
Setting the system status (unscanned, hostile, etc) no longer works

I'm seeing this behaviour after c9a792083d74ad346593637ba10f4e4d882ecc03 -- if you set the system status and then refresh, it's no longer set.

Scratch that -- was just some weirdness I was having after doing the upgrade, a full php/nginx service restart resolved it.


text:
fix: AVAudioPlayer cannot play on background when Youtube playing

AVAudioPlayer cannot play on background when Youtube playing

will be merged from 0.7.3-dev-1.2 branch


text:
get my own anchors

h run get_anchors and I have this error :
runfile('D:/My Data/My Work/GP/code/CodeFinalFinal/gen_anchors.py', wdir='D:/My Data/My Work/GP/code/CodeFinalFinal')
Reloaded modules: preprocessing, utilss
Taher1 0
(0,)
Traceback (most recent call last):
File "", line 1, in
runfile('D:/My Data/My Work/GP/code/CodeFinalFinal/gen_anchors.py', wdir='D:/My Data/My Work/GP/code/CodeFinalFinal')
File "C:\ProgramData\Anaconda3\lib\site-packages\spyder\utils\site\sitecustomize.py", line 710, in runfile
execfile(filename, namespace)
File "C:\ProgramData\Anaconda3\lib\site-packages\spyder\utils\site\sitecustomize.py", line 101, in execfile
exec(compile(f.read(), filename, 'exec'), namespace)
File "D:/My Data/My Work/GP/code/CodeFinalFinal/gen_anchors.py", line 143, in
main(args)
File "D:/My Data/My Work/GP/code/CodeFinalFinal/gen_anchors.py", line 135, in main
centroids = run_kmeans(annotation_dims, num_anchors)
File "D:/My Data/My Work/GP/code/CodeFinalFinal/gen_anchors.py", line 73, in run_kmeans
indices = [random.randrange(ann_dims.shape[0]) for i in range(anchor_num)]
File "D:/My Data/My Work/GP/code/CodeFinalFinal/gen_anchors.py", line 73, in
indices = [random.randrange(ann_dims.shape[0]) for i in range(anchor_num)]
File "C:\ProgramData\Anaconda3\lib\random.py", line 188, in randrange
raise ValueError("empty range for randrange()")
ValueError: empty range for randrange()
runfile('D:/My Data/My Work/GP/code/CodeFinalFinal/gen_anchors.py', wdir='D:/My Data/My Work/GP/code/CodeFinalFinal')
Reloaded modules: preprocessing, utilss
Taher1 0
(0,)
Traceback (most recent call last):
File "", line 1, in
runfile('D:/My Data/My Work/GP/code/CodeFinalFinal/gen_anchors.py', wdir='D:/My Data/My Work/GP/code/CodeFinalFinal')
File "C:\ProgramData\Anaconda3\lib\site-packages\spyder\utils\site\sitecustomize.py", line 710, in runfile
execfile(filename, namespace)
File "C:\ProgramData\Anaconda3\lib\site-packages\spyder\utils\site\sitecustomize.py", line 101, in execfile
exec(compile(f.read(), filename, 'exec'), namespace)
File "D:/My Data/My Work/GP/code/CodeFinalFinal/gen_anchors.py", line 143, in
main(args)
File "D:/My Data/My Work/GP/code/CodeFinalFinal/gen_anchors.py", line 135, in main
centroids = run_kmeans(annotation_dims, num_anchors)
File "D:/My Data/My Work/GP/code/CodeFinalFinal/gen_anchors.py", line 73, in run_kmeans
indices = [random.randrange(ann_dims.shape[0]) for i in range(anchor_num)]
File "D:/My Data/My Work/GP/code/CodeFinalFinal/gen_anchors.py", line 73, in
indices = [random.randrange(ann_dims.shape[0]) for i in range(anchor_num)]
File "C:\ProgramData\Anaconda3\lib\random.py", line 188, in randrange
raise ValueError("empty range for randrange()")
ValueError: empty range for randrange()
how i can fix it  ?

when i use the -a option and pass an integer like this
-a 10
i get
File "gen_anchors.py", line 71, in run_kmeans
old_distances = np.zeros((ann_num, anchor_num))
TypeError: 'str' object cannot be interpreted as an integer
Any help?
@RichardSieg @Spider95

change this
argparser.add_argument(
    '-a',
    '--anchors',
    default=5,
    help='number of anchors to use')

to this:
argparser.add_argument(
    '-a',
    '--anchors',
    default=5,
    help='number of anchors to use',
    type=int)

Tried that and now i'm getting this:
Traceback (most recent call last):
File "gen_anchors.py", line 138, in
main(args)
File "gen_anchors.py", line 130, in main
centroids = run_kmeans(annotation_dims, num_anchors)
File "gen_anchors.py", line 74, in run_kmeans
indices = [random.randrange(ann_dims.shape[0]) for i in range(anchor_num)]
File "gen_anchors.py", line 74, in
indices = [random.randrange(ann_dims.shape[0]) for i in range(anchor_num)]
File "/home/ugot/anaconda3/lib/python3.6/random.py", line 189, in randrange
raise ValueError("empty range for randrange()")
ValueError: empty range for randrange()

Sorry, I couldn't replicate your error

@ogbanugot I had a similar error and it was because I was not able to extract any annotations from the .xml files due to the fact the classes I put in my config.json file didn't correspond to the ones in the .xml files. I hope this can help you.

Thanks, you are right. The classes in my xml file didn't match the ones in my config.json file. but i'd point out that it was when i attempted to train, that the class mismatch error was highlighted. So now that i fixed the classes in my .xml file, the get_anchors works now.


text:
feat: Update redux UI, add action update UI, add state,diff and actio…

Update UI for redux, added selection of history in state, diff, state and action tabs added, readme updated

Hi! @Kudo just merged the commit for the suggestion.

repo: expo/dev-plugins


text:
eas build showing some errors

Build/Submit details page URL
No response
Summary

I am getting this error every time while building the app using eas build command.
Managed or bare?
Android
Environment
expo-env-info 1.0.5 environment info:
System:
OS: Windows 10 10.0.22621
Binaries:
Node: 16.13.0 - C:\Program Files\nodejs\node.EXE
Yarn: 1.22.19 - ~\AppData\Roaming\npm\yarn.CMD
npm: 8.1.0 - C:\Program Files\nodejs\npm.CMD
npmPackages:
expo: ~47.0.12 => 47.0.12
react: 18.1.0 => 18.1.0
react-native: 0.70.5 => 0.70.5
Expo Workflow: managed
Error output
No response
Reproducible demo or steps to reproduce from a blank project
{
"cli": {
"version": ">= 3.1.1"
},
"build": {
"development": {
"developmentClient": true,
"distribution": "internal"
},
"preview": {
"distribution": "internal"
},
"production": {}
},
"submit": {
"production": {}
}
}

Hi, does this issue still occur for you? It seems like it's old and stale. I can't reproduce it so far 🤔 Feel free to reopen if you still think it's broken.

repo: expo/eas-cli


text:
fromPairs(toPairs({a: 1})) doesn't work

json: unsupported type: map[interface {}]interface {}

This is just a playground problem. Go's json package does not support marshaling map[any]any to json (only map[string]any). I have plans to refactor playground and get way from json as output.
You still can get results in playground by wrapping in string() func:
string(fromPairs(toPairs({a: 1})))

[!tip]
Use a pipe operator for better readability:
toPairs({a: 1}) | fromPairs() | string()

repo: expr-lang/expr


text:
Error: stream ended unexpectedly

I am getting this error i don't know from where i am getting this error  and why

Hm, weird. I would love to take a look and figure it out. Can you help provide instruction on how to reproduce so I can take a look? Provide the following, for example:

Version of Node.js
Version of this and all other used modules
Complete server code I can copy and paste and run to see the issue
Instructions on what request (include a copy of the request or code that creates the request) to make to produce the given error.

Thanks!

Same here:
pakages.json
"connect-multiparty": "^2.1.0",
    "express": "^4.16.3",

app.js
const express = require('express')
const app = express()
const multipart = require('connect-multiparty')
const multipartMiddleware = multipart()

app.post('/', multipartMiddleware, (req, res) => {
  console.debug(req.body, req.files)
})

raises the following:
Listening on port 3000

Error: stream ended unexpectedly
    at Form.<anonymous> (/Users/vinyll/Projects/eurordis/receipt-sender/node_modules/multiparty/index.js:754:24)
    at Form.emit (events.js:165:20)
    at finishMaybe (_stream_writable.js:633:14)
    at endWritable (_stream_writable.js:641:3)
    at Form.Writable.end (_stream_writable.js:583:5)
    at IncomingMessage.onend (_stream_readable.js:602:10)
    at Object.onceWrapper (events.js:255:19)
    at IncomingMessage.emit (events.js:165:20)
    at endReadableNT (_stream_readable.js:1101:12)
    at process._tickCallback (internal/process/next_tick.js:152:19)

Seems like it is when re-submitting the _post_ed form refreshing the page.
Works fine when browsing back and reclicking on the submit button.

Hi @vinyll I can definitely take a look. I ran your app, and that error doesn't actually appear. After I copy the app and run it, what are the steps to see the error?

I did try that in Chrome and there wasn't an error. I'm hoping that you can possible some more specific instructions if possible. Maybe the code for how to do the post is different between us? Or the web browser?

Good point. I tried with Chromium and Firefox 56 and I had no error risen; it occurs on Firefox 60.
What I do more precisely to reproduce:

run
submit a file
the server loops as there's no response. Ctrl+C to stop the server
restart the server
refresh the page accepting to post again

At this stage I'm wondering if it isn't a bug with FF… :/

Ah, gotcha. I will work to get Firefox installed soon and try it out 👍

Hi @Akash0333 so I downloaded & installed Firefox 30 and setup my form to do the same thing you described: I have a <form> that makes a POST and then displays "success". I then click on the Reload button and Firefox asks if I want to send the data again. I accept and "success" is displayed again and the form uploaded without an error. Not sure what the difference is between our setups are, though.
Is it possible you can update your above app.js to send an HTML page with a <form> that represents your form? Ideally the less I have to try and make up on the fly, the closer our implementations will get to each other to reproduce the issue.
Also, you're always welcome to submit a fix as a PR as well 👍I want to get this fixed, but I don't (yet) have a way to see the issue to understand what to change.

Hey @dougwilson! Why are you talking about Firefox 30?
I can't see a reference from @Akash0333 about it, but maybe I'm missing some message here.

Sorry that was a typo. I meant Firefox 60 (the current version).

I have the same issue if I don't send any body from post man to any service. What is the wrong ?? and how to fix it ??

Open a new issue with complete code and steps to reproduce the issue so we can figure it out.

repo: expressjs/connect-multiparty


text:
Can't install express

I've tried to install both recommended versions of express (4.4.7 and 6.3.1) and I keep getting errors saying these are the only valid install targets:
Am I doing something wrong?  I've attached my debug log.  It seems most of the responses to this error are not having the most recent npm version which i can't be it because i have the most recent version (3.10.6)
Thanks for any help!  Been at this for 4 hours.  I guess I could just install one of the other versions, but I just wanted to figure out what the rookie mistake I must be making.  : (
my echo $PATH
/usr/local/bin:/Users/cdixon/local/nodejs/bin:/Library/Frameworks/Python.framework/Versions/2.7/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin

Here is my debug log:
0 info it worked if it ends with ok
1 verbose cli [ '/usr/local/Cellar/node/6.3.1/bin/node',
1 verbose cli   '/usr/local/bin/npm',
1 verbose cli   'install',
1 verbose cli   'express' ]
2 info using npm@3.10.6
3 info using node@v6.3.1
4 silly loadCurrentTree Starting
5 silly install loadCurrentTree
6 silly install readLocalPackageData
7 silly fetchPackageMetaData express@4.4.7
8 silly fetchNamedPackageData express
9 silly mapToRegistry name express
10 silly mapToRegistry using default registry
11 silly mapToRegistry registry https://registry.npmjs.org/
12 silly mapToRegistry data Result {
12 silly mapToRegistry   raw: 'express',
12 silly mapToRegistry   scope: null,
12 silly mapToRegistry   escapedName: 'express',
12 silly mapToRegistry   name: 'express',
12 silly mapToRegistry   rawSpec: '',
12 silly mapToRegistry   spec: 'latest',
12 silly mapToRegistry   type: 'tag' }
13 silly mapToRegistry uri https://registry.npmjs.org/express
14 verbose get https://registry.npmjs.org/express not expired, no request
15 silly fetchNamedPackageData No valid target from cache, forcing network
16 verbose request uri https://registry.npmjs.org/express
17 verbose request no auth needed
18 info attempt registry request try #1 at 11:58:36 AM
19 verbose request id f9fc9701f99c5541
20 http request GET https://registry.npmjs.org/express
21 http 200 https://registry.npmjs.org/express
22 verbose headers { server: 'CouchDB/1.5.0 (Erlang OTP/R16B03)',
22 verbose headers   etag: '"EZ5LR5NXZWKZG9YS144R6HOO0"',
22 verbose headers   'content-type': 'application/json',
22 verbose headers   'content-encoding': 'gzip',
22 verbose headers   'cache-control': 'max-age=300',
22 verbose headers   'content-length': '55897',
22 verbose headers   'accept-ranges': 'bytes',
22 verbose headers   date: 'Mon, 15 Aug 2016 15:58:36 GMT',
22 verbose headers   via: '1.1 varnish',
22 verbose headers   age: '253',
22 verbose headers   connection: 'keep-alive',
22 verbose headers   'x-served-by': 'cache-atl6234-ATL',
22 verbose headers   'x-cache': 'HIT',
22 verbose headers   'x-cache-hits': '6',
22 verbose headers   'x-timer': 'S1471276716.229334,VS0,VE0',
22 verbose headers   vary: 'Accept-Encoding' }
23 silly get cb [ 200,
23 silly get   { server: 'CouchDB/1.5.0 (Erlang OTP/R16B03)',
23 silly get     etag: '"EZ5LR5NXZWKZG9YS144R6HOO0"',
23 silly get     'content-type': 'application/json',
23 silly get     'content-encoding': 'gzip',
23 silly get     'cache-control': 'max-age=300',
23 silly get     'content-length': '55897',
23 silly get     'accept-ranges': 'bytes',
23 silly get     date: 'Mon, 15 Aug 2016 15:58:36 GMT',
23 silly get     via: '1.1 varnish',
23 silly get     age: '253',
23 silly get     connection: 'keep-alive',
23 silly get     'x-served-by': 'cache-atl6234-ATL',
23 silly get     'x-cache': 'HIT',
23 silly get     'x-cache-hits': '6',
23 silly get     'x-timer': 'S1471276716.229334,VS0,VE0',
23 silly get     vary: 'Accept-Encoding' } ]
24 verbose get saving express to /Users/cdixon/.npm/registry.npmjs.org/express/.cache.json
25 verbose correctMkdir /Users/cdixon/.npm correctMkdir not in flight; initializing
26 silly fetchPackageMetaData Error: No compatible version found: express@4.4.7
26 silly fetchPackageMetaData Valid install targets:
26 silly fetchPackageMetaData 5.0.0-alpha.2, 5.0.0-alpha.1, 4.14.0, 4.13.4, 4.13.3, 4.13.2, 4.13.1, 4.13.0, 4.12.4, 4.12.3, 4.12.2, 4.12.1, 4.12.0, 4.11.2, 4.11.1, 4.11.0, 4.10.8, 4.10.7, 4.10.6, 4.10.5, 4.10.4, 4.10.3, 4.10.2, 4.10.1, 4.10.0, 4.9.8, 4.9.7, 4.9.6, 4.9.5, 4.9.4, 4.9.3, 4.9.2, 4.9.1, 4.9.0, 4.8.8, 4.8.7, 4.8.6, 4.8.5, 4.8.4, 4.8.3, 4.8.2, 4.8.1, 4.8.0, 4.7.4, 4.7.3, 4.7.2, 4.7.1, 4.7.0, 4.6.1, 4.6.0, 4.5.1, 4.5.0, 4.4.5, 4.4.4, 4.4.3, 4.4.2, 4.4.1, 4.4.0, 4.3.2, 4.3.1, 4.3.0, 4.2.0, 4.1.2, 4.1.1, 4.1.0, 4.0.0, 4.0.0-rc4, 4.0.0-rc3, 4.0.0-rc2, 4.0.0-rc1, 3.21.2, 3.21.1, 3.21.0, 3.20.3, 3.20.2, 3.20.1, 3.20.0, 3.19.2, 3.19.1, 3.19.0, 3.18.6, 3.18.5, 3.18.4, 3.18.3, 3.18.2, 3.18.1, 3.18.0, 3.17.8, 3.17.7, 3.17.6, 3.17.5, 3.17.4, 3.17.3, 3.17.2, 3.17.1, 3.17.0, 3.16.10, 3.16.9, 3.16.8, 3.16.7, 3.16.6, 3.16.5, 3.16.4, 3.16.3, 3.16.2, 3.16.1, 3.16.0, 3.15.3, 3.15.2, 3.15.1, 3.15.0, 3.14.0, 3.13.0, 3.12.1, 3.12.0, 3.11.0, 3.10.5, 3.10.4, 3.10.3, 3.10.2, 3.10.1, 3.10.0, 3.9.0, 3.8.1, 3.8.0, 3.7.0, 3.6.0, 3.5.3, 3.5.2, 3.5.1, 3.5.0, 3.4.8, 3.4.7, 3.4.6, 3.4.5, 3.4.4, 3.4.3, 3.4.2, 3.4.1, 3.4.0, 3.3.8, 3.3.7, 3.3.6, 3.3.5, 3.3.4, 3.3.3, 3.3.2, 3.3.1, 3.3.0, 3.2.6, 3.2.5, 3.2.4, 3.2.3, 3.2.2, 3.2.1, 3.2.0, 3.1.2, 3.1.1, 3.1.0, 3.0.6, 3.0.5, 3.0.4, 3.0.3, 3.0.2, 3.0.1, 3.0.0, 3.0.0-rc5, 3.0.0-rc4, 3.0.0-rc3, 3.0.0-rc2, 3.0.0-rc1, 3.0.0-beta7, 3.0.0-beta6, 3.0.0-beta4, 3.0.0-beta3, 3.0.0-beta2, 3.0.0-beta1, 3.0.0-alpha5, 3.0.0-alpha4, 3.0.0-alpha3, 3.0.0-alpha2, 3.0.0-alpha1, 2.5.11, 2.5.10, 2.5.9, 2.5.8, 2.5.7, 2.5.6, 2.5.5, 2.5.4, 2.5.3, 2.5.2, 2.5.1, 2.5.0, 2.4.7, 2.4.6, 2.4.5, 2.4.4, 2.4.3, 2.4.2, 2.4.1, 2.4.0, 2.3.12, 2.3.11, 2.3.10, 2.3.9, 2.3.8, 2.3.7, 2.3.6, 2.3.5, 2.3.4, 2.3.3, 2.3.2, 2.3.1, 2.3.0, 2.2.2, 2.2.1, 2.2.0, 2.1.1, 2.1.0, 2.0.0, 2.0.0-rc3, 2.0.0-rc2, 2.0.0-rc, 2.0.0-beta3, 2.0.0-beta2, 2.0.0-beta, 1.0.8, 1.0.7, 1.0.6, 1.0.5, 1.0.4, 1.0.3, 1.0.2, 1.0.1, 1.0.0, 1.0.0-rc4, 1.0.0-rc3, 1.0.0-rc2, 1.0.0-rc, 1.0.0-beta2, 1.0.0-beta, 0.14.1, 0.14.0
26 silly fetchPackageMetaData
26 silly fetchPackageMetaData     at pickVersionFromRegistryDocument (/usr/local/lib/node_modules/npm/lib/fetch-package-metadata.js:178:16)
26 silly fetchPackageMetaData     at /usr/local/lib/node_modules/npm/node_modules/iferr/index.js:13:50
26 silly fetchPackageMetaData     at /usr/local/lib/node_modules/npm/lib/utils/pulse-till-done.js:20:8
26 silly fetchPackageMetaData     at saved (/usr/local/lib/node_modules/npm/lib/cache/caching-client.js:174:7)
26 silly fetchPackageMetaData     at /usr/local/lib/node_modules/npm/node_modules/graceful-fs/polyfills.js:210:7
26 silly fetchPackageMetaData     at FSReqWrap.oncomplete (fs.js:123:15)
26 silly fetchPackageMetaData  error for express@4.4.7 Error: No compatible version found: express@4.4.7
26 silly fetchPackageMetaData Valid install targets:
26 silly fetchPackageMetaData 5.0.0-alpha.2, 5.0.0-alpha.1, 4.14.0, 4.13.4, 4.13.3, 4.13.2, 4.13.1, 4.13.0, 4.12.4, 4.12.3, 4.12.2, 4.12.1, 4.12.0, 4.11.2, 4.11.1, 4.11.0, 4.10.8, 4.10.7, 4.10.6, 4.10.5, 4.10.4, 4.10.3, 4.10.2, 4.10.1, 4.10.0, 4.9.8, 4.9.7, 4.9.6, 4.9.5, 4.9.4, 4.9.3, 4.9.2, 4.9.1, 4.9.0, 4.8.8, 4.8.7, 4.8.6, 4.8.5, 4.8.4, 4.8.3, 4.8.2, 4.8.1, 4.8.0, 4.7.4, 4.7.3, 4.7.2, 4.7.1, 4.7.0, 4.6.1, 4.6.0, 4.5.1, 4.5.0, 4.4.5, 4.4.4, 4.4.3, 4.4.2, 4.4.1, 4.4.0, 4.3.2, 4.3.1, 4.3.0, 4.2.0, 4.1.2, 4.1.1, 4.1.0, 4.0.0, 4.0.0-rc4, 4.0.0-rc3, 4.0.0-rc2, 4.0.0-rc1, 3.21.2, 3.21.1, 3.21.0, 3.20.3, 3.20.2, 3.20.1, 3.20.0, 3.19.2, 3.19.1, 3.19.0, 3.18.6, 3.18.5, 3.18.4, 3.18.3, 3.18.2, 3.18.1, 3.18.0, 3.17.8, 3.17.7, 3.17.6, 3.17.5, 3.17.4, 3.17.3, 3.17.2, 3.17.1, 3.17.0, 3.16.10, 3.16.9, 3.16.8, 3.16.7, 3.16.6, 3.16.5, 3.16.4, 3.16.3, 3.16.2, 3.16.1, 3.16.0, 3.15.3, 3.15.2, 3.15.1, 3.15.0, 3.14.0, 3.13.0, 3.12.1, 3.12.0, 3.11.0, 3.10.5, 3.10.4, 3.10.3, 3.10.2, 3.10.1, 3.10.0, 3.9.0, 3.8.1, 3.8.0, 3.7.0, 3.6.0, 3.5.3, 3.5.2, 3.5.1, 3.5.0, 3.4.8, 3.4.7, 3.4.6, 3.4.5, 3.4.4, 3.4.3, 3.4.2, 3.4.1, 3.4.0, 3.3.8, 3.3.7, 3.3.6, 3.3.5, 3.3.4, 3.3.3, 3.3.2, 3.3.1, 3.3.0, 3.2.6, 3.2.5, 3.2.4, 3.2.3, 3.2.2, 3.2.1, 3.2.0, 3.1.2, 3.1.1, 3.1.0, 3.0.6, 3.0.5, 3.0.4, 3.0.3, 3.0.2, 3.0.1, 3.0.0, 3.0.0-rc5, 3.0.0-rc4, 3.0.0-rc3, 3.0.0-rc2, 3.0.0-rc1, 3.0.0-beta7, 3.0.0-beta6, 3.0.0-beta4, 3.0.0-beta3, 3.0.0-beta2, 3.0.0-beta1, 3.0.0-alpha5, 3.0.0-alpha4, 3.0.0-alpha3, 3.0.0-alpha2, 3.0.0-alpha1, 2.5.11, 2.5.10, 2.5.9, 2.5.8, 2.5.7, 2.5.6, 2.5.5, 2.5.4, 2.5.3, 2.5.2, 2.5.1, 2.5.0, 2.4.7, 2.4.6, 2.4.5, 2.4.4, 2.4.3, 2.4.2, 2.4.1, 2.4.0, 2.3.12, 2.3.11, 2.3.10, 2.3.9, 2.3.8, 2.3.7, 2.3.6, 2.3.5, 2.3.4, 2.3.3, 2.3.2, 2.3.1, 2.3.0, 2.2.2, 2.2.1, 2.2.0, 2.1.1, 2.1.0, 2.0.0, 2.0.0-rc3, 2.0.0-rc2, 2.0.0-rc, 2.0.0-beta3, 2.0.0-beta2, 2.0.0-beta, 1.0.8, 1.0.7, 1.0.6, 1.0.5, 1.0.4, 1.0.3, 1.0.2, 1.0.1, 1.0.0, 1.0.0-rc4, 1.0.0-rc3, 1.0.0-rc2, 1.0.0-rc, 1.0.0-beta2, 1.0.0-beta, 0.14.1, 0.14.0
26 silly fetchPackageMetaData
26 silly fetchPackageMetaData     at pickVersionFromRegistryDocument (/usr/local/lib/node_modules/npm/lib/fetch-package-metadata.js:178:16)
26 silly fetchPackageMetaData     at /usr/local/lib/node_modules/npm/node_modules/iferr/index.js:13:50
26 silly fetchPackageMetaData     at /usr/local/lib/node_modules/npm/lib/utils/pulse-till-done.js:20:8
26 silly fetchPackageMetaData     at saved (/usr/local/lib/node_modules/npm/lib/cache/caching-client.js:174:7)
26 silly fetchPackageMetaData     at /usr/local/lib/node_modules/npm/node_modules/graceful-fs/polyfills.js:210:7
26 silly fetchPackageMetaData     at FSReqWrap.oncomplete (fs.js:123:15)
27 silly rollbackFailedOptional Starting
28 silly rollbackFailedOptional Finishing
29 silly runTopLevelLifecycles Starting
30 silly runTopLevelLifecycles Finishing
31 silly install printInstalled
32 verbose stack Error: No compatible version found: express@4.4.7
32 verbose stack Valid install targets:
32 verbose stack 5.0.0-alpha.2, 5.0.0-alpha.1, 4.14.0, 4.13.4, 4.13.3, 4.13.2, 4.13.1, 4.13.0, 4.12.4, 4.12.3, 4.12.2, 4.12.1, 4.12.0, 4.11.2, 4.11.1, 4.11.0, 4.10.8, 4.10.7, 4.10.6, 4.10.5, 4.10.4, 4.10.3, 4.10.2, 4.10.1, 4.10.0, 4.9.8, 4.9.7, 4.9.6, 4.9.5, 4.9.4, 4.9.3, 4.9.2, 4.9.1, 4.9.0, 4.8.8, 4.8.7, 4.8.6, 4.8.5, 4.8.4, 4.8.3, 4.8.2, 4.8.1, 4.8.0, 4.7.4, 4.7.3, 4.7.2, 4.7.1, 4.7.0, 4.6.1, 4.6.0, 4.5.1, 4.5.0, 4.4.5, 4.4.4, 4.4.3, 4.4.2, 4.4.1, 4.4.0, 4.3.2, 4.3.1, 4.3.0, 4.2.0, 4.1.2, 4.1.1, 4.1.0, 4.0.0, 4.0.0-rc4, 4.0.0-rc3, 4.0.0-rc2, 4.0.0-rc1, 3.21.2, 3.21.1, 3.21.0, 3.20.3, 3.20.2, 3.20.1, 3.20.0, 3.19.2, 3.19.1, 3.19.0, 3.18.6, 3.18.5, 3.18.4, 3.18.3, 3.18.2, 3.18.1, 3.18.0, 3.17.8, 3.17.7, 3.17.6, 3.17.5, 3.17.4, 3.17.3, 3.17.2, 3.17.1, 3.17.0, 3.16.10, 3.16.9, 3.16.8, 3.16.7, 3.16.6, 3.16.5, 3.16.4, 3.16.3, 3.16.2, 3.16.1, 3.16.0, 3.15.3, 3.15.2, 3.15.1, 3.15.0, 3.14.0, 3.13.0, 3.12.1, 3.12.0, 3.11.0, 3.10.5, 3.10.4, 3.10.3, 3.10.2, 3.10.1, 3.10.0, 3.9.0, 3.8.1, 3.8.0, 3.7.0, 3.6.0, 3.5.3, 3.5.2, 3.5.1, 3.5.0, 3.4.8, 3.4.7, 3.4.6, 3.4.5, 3.4.4, 3.4.3, 3.4.2, 3.4.1, 3.4.0, 3.3.8, 3.3.7, 3.3.6, 3.3.5, 3.3.4, 3.3.3, 3.3.2, 3.3.1, 3.3.0, 3.2.6, 3.2.5, 3.2.4, 3.2.3, 3.2.2, 3.2.1, 3.2.0, 3.1.2, 3.1.1, 3.1.0, 3.0.6, 3.0.5, 3.0.4, 3.0.3, 3.0.2, 3.0.1, 3.0.0, 3.0.0-rc5, 3.0.0-rc4, 3.0.0-rc3, 3.0.0-rc2, 3.0.0-rc1, 3.0.0-beta7, 3.0.0-beta6, 3.0.0-beta4, 3.0.0-beta3, 3.0.0-beta2, 3.0.0-beta1, 3.0.0-alpha5, 3.0.0-alpha4, 3.0.0-alpha3, 3.0.0-alpha2, 3.0.0-alpha1, 2.5.11, 2.5.10, 2.5.9, 2.5.8, 2.5.7, 2.5.6, 2.5.5, 2.5.4, 2.5.3, 2.5.2, 2.5.1, 2.5.0, 2.4.7, 2.4.6, 2.4.5, 2.4.4, 2.4.3, 2.4.2, 2.4.1, 2.4.0, 2.3.12, 2.3.11, 2.3.10, 2.3.9, 2.3.8, 2.3.7, 2.3.6, 2.3.5, 2.3.4, 2.3.3, 2.3.2, 2.3.1, 2.3.0, 2.2.2, 2.2.1, 2.2.0, 2.1.1, 2.1.0, 2.0.0, 2.0.0-rc3, 2.0.0-rc2, 2.0.0-rc, 2.0.0-beta3, 2.0.0-beta2, 2.0.0-beta, 1.0.8, 1.0.7, 1.0.6, 1.0.5, 1.0.4, 1.0.3, 1.0.2, 1.0.1, 1.0.0, 1.0.0-rc4, 1.0.0-rc3, 1.0.0-rc2, 1.0.0-rc, 1.0.0-beta2, 1.0.0-beta, 0.14.1, 0.14.0
32 verbose stack
32 verbose stack     at pickVersionFromRegistryDocument (/usr/local/lib/node_modules/npm/lib/fetch-package-metadata.js:178:16)
32 verbose stack     at /usr/local/lib/node_modules/npm/node_modules/iferr/index.js:13:50
32 verbose stack     at /usr/local/lib/node_modules/npm/lib/utils/pulse-till-done.js:20:8
32 verbose stack     at saved (/usr/local/lib/node_modules/npm/lib/cache/caching-client.js:174:7)
32 verbose stack     at /usr/local/lib/node_modules/npm/node_modules/graceful-fs/polyfills.js:210:7
32 verbose stack     at FSReqWrap.oncomplete (fs.js:123:15)
33 verbose cwd /Users/cdixon/Desktop/NodeProjects/feedbot
34 error Darwin 15.3.0
35 error argv "/usr/local/Cellar/node/6.3.1/bin/node" "/usr/local/bin/npm" "install" "express"
36 error node v6.3.1
37 error npm  v3.10.6
38 error No compatible version found: express@4.4.7
38 error Valid install targets:
38 error 5.0.0-alpha.2, 5.0.0-alpha.1, 4.14.0, 4.13.4, 4.13.3, 4.13.2, 4.13.1, 4.13.0, 4.12.4, 4.12.3, 4.12.2, 4.12.1, 4.12.0, 4.11.2, 4.11.1, 4.11.0, 4.10.8, 4.10.7, 4.10.6, 4.10.5, 4.10.4, 4.10.3, 4.10.2, 4.10.1, 4.10.0, 4.9.8, 4.9.7, 4.9.6, 4.9.5, 4.9.4, 4.9.3, 4.9.2, 4.9.1, 4.9.0, 4.8.8, 4.8.7, 4.8.6, 4.8.5, 4.8.4, 4.8.3, 4.8.2, 4.8.1, 4.8.0, 4.7.4, 4.7.3, 4.7.2, 4.7.1, 4.7.0, 4.6.1, 4.6.0, 4.5.1, 4.5.0, 4.4.5, 4.4.4, 4.4.3, 4.4.2, 4.4.1, 4.4.0, 4.3.2, 4.3.1, 4.3.0, 4.2.0, 4.1.2, 4.1.1, 4.1.0, 4.0.0, 4.0.0-rc4, 4.0.0-rc3, 4.0.0-rc2, 4.0.0-rc1, 3.21.2, 3.21.1, 3.21.0, 3.20.3, 3.20.2, 3.20.1, 3.20.0, 3.19.2, 3.19.1, 3.19.0, 3.18.6, 3.18.5, 3.18.4, 3.18.3, 3.18.2, 3.18.1, 3.18.0, 3.17.8, 3.17.7, 3.17.6, 3.17.5, 3.17.4, 3.17.3, 3.17.2, 3.17.1, 3.17.0, 3.16.10, 3.16.9, 3.16.8, 3.16.7, 3.16.6, 3.16.5, 3.16.4, 3.16.3, 3.16.2, 3.16.1, 3.16.0, 3.15.3, 3.15.2, 3.15.1, 3.15.0, 3.14.0, 3.13.0, 3.12.1, 3.12.0, 3.11.0, 3.10.5, 3.10.4, 3.10.3, 3.10.2, 3.10.1, 3.10.0, 3.9.0, 3.8.1, 3.8.0, 3.7.0, 3.6.0, 3.5.3, 3.5.2, 3.5.1, 3.5.0, 3.4.8, 3.4.7, 3.4.6, 3.4.5, 3.4.4, 3.4.3, 3.4.2, 3.4.1, 3.4.0, 3.3.8, 3.3.7, 3.3.6, 3.3.5, 3.3.4, 3.3.3, 3.3.2, 3.3.1, 3.3.0, 3.2.6, 3.2.5, 3.2.4, 3.2.3, 3.2.2, 3.2.1, 3.2.0, 3.1.2, 3.1.1, 3.1.0, 3.0.6, 3.0.5, 3.0.4, 3.0.3, 3.0.2, 3.0.1, 3.0.0, 3.0.0-rc5, 3.0.0-rc4, 3.0.0-rc3, 3.0.0-rc2, 3.0.0-rc1, 3.0.0-beta7, 3.0.0-beta6, 3.0.0-beta4, 3.0.0-beta3, 3.0.0-beta2, 3.0.0-beta1, 3.0.0-alpha5, 3.0.0-alpha4, 3.0.0-alpha3, 3.0.0-alpha2, 3.0.0-alpha1, 2.5.11, 2.5.10, 2.5.9, 2.5.8, 2.5.7, 2.5.6, 2.5.5, 2.5.4, 2.5.3, 2.5.2, 2.5.1, 2.5.0, 2.4.7, 2.4.6, 2.4.5, 2.4.4, 2.4.3, 2.4.2, 2.4.1, 2.4.0, 2.3.12, 2.3.11, 2.3.10, 2.3.9, 2.3.8, 2.3.7, 2.3.6, 2.3.5, 2.3.4, 2.3.3, 2.3.2, 2.3.1, 2.3.0, 2.2.2, 2.2.1, 2.2.0, 2.1.1, 2.1.0, 2.0.0, 2.0.0-rc3, 2.0.0-rc2, 2.0.0-rc, 2.0.0-beta3, 2.0.0-beta2, 2.0.0-beta, 1.0.8, 1.0.7, 1.0.6, 1.0.5, 1.0.4, 1.0.3, 1.0.2, 1.0.1, 1.0.0, 1.0.0-rc4, 1.0.0-rc3, 1.0.0-rc2, 1.0.0-rc, 1.0.0-beta2, 1.0.0-beta, 0.14.1, 0.14.0
39 error If you need help, you may report this error at:
39 error     <https://github.com/npm/npm/issues>
40 verbose exit [ 1, true ]

Where do the recommended versions of express (4.4.7 and 6.3.1) come from? Express.js has never been released as those version numbers.

4.4.7 and 6.3.1 is the current versions of Node.js, not versions of express. Can you try installing the latest express with the following command:
npm install express@latest

OMG, I'm an idiot.  lack of sleep.  Please close this.

authors: LinusU dougwilson meanlittlechimp

repo: expressjs/express


text:
route parametere issue solved. FIXED #2495

Fixed #2495
I have checked and it is working fine with both conditions now.

This will be upgraded in the 5.0 branch, and this module is no longer a dependency of the 5.0 branch.


text:
Fix regexp handing logic in router. Closes #4204

It closes #4204. When regexp matches path not from the beginning, trim_prefx validates if path breaks on a path separator in a wrong way.
Here is a small illustration of the problem:
path:       /test/api/123
layerPath:  /api/123
c:                  ^

after the fix:
path:       /test/api/123
startIndex:      ^
layerPath:       /api/123
c:                       ^

This PR fixes his behaviors by testing matched layerPath not from the begging of the path but from the start of the match.
I have also added a unit test to cover this case.
Existing logic should not be affected, because in case of a match from the beginning of the path, the startIndex variable will be 0 and we will end up an old logic.

Thank you for the pull request! I'm not sure if this is a valid use case for the prefix matching function of app.use, though, as it is only supposed to match based on prefix.
What your change here, what is the value of req.url within your app.use? I assume it is also a mangled value now?

Yes, req.url in mangled now. OK, if app.use should only match based on prefix, the proper fix would be to add ^ to the regexp if the user didn't specify it (I think the same logic is already implemented somewhere in the code, because if I specify app.use('/api'... internally it will be replaced with a regexp /^\/api\/?(?=\/|$)/i

To add a bit more content to it, we faced this bug in prod in our app. We have defined two layers:
app.use(/(\/foo|\/api)/, handlerA)
and
app.use(/\/proxy/, handlerB)
and when we were making a request to /proxy/api/12345 it was processed by handlerA instead of habdlerB but only in case we have 5 characters after the last / symbol. In all other cases, it was processed by hanlderB as expected.

I have updated this PR (reverted the change and added a unit test to showcase the problem)

Hi @drussilla , sorry for the delay due to current world events 😕 . I just committed a fix (https://github.com/pillarjs/router/commit/16ff25e050243477b44c0e54d01f839d6d018064) to the upstream router repo that should fix your issue. The fix will be ported here and does pass the test you provided, and adds the check that really should have always been there. LMK what you think.

@dougwilson Look good to me, thanks for the fix!

@dougwilson Looks good to me, thanks for the fix and I hope you stay safe and healthy in this crazy time!

Awesome, @drussilla thanks for confirming :) I'll port that change into your PR here (so don't close it unless you really want to) and then we'll get it merged into the upcoming 4.x release (4.18).

Alright, apologies for the delay on that. I have ported the router change into the PR here.

authors: dougwilson drussilla tavotech


text:
How to disable range requests in Next.js ?

Seems like Next has the same behavior and it doesn't use Express

Sorry opened the issue in the wrong repo.

repo: expressjs/serve-static


text:
adding ARM release  as a workaround

Signed-off-by: Gustavo Carvalho gusfcarvalho@gmail.com

@moolen @knelasevero @IdanAdar This is a quick fix to allow using the current workflow to release boringssl images.
I guess a proper fix would involve changing tha Makefile jq syntax to something like [.manifests, .config] | select( . != null) | .[].digest but we would need to test how the promotion process would actually work.

/approve

nvm - I had to properly fix it anyways to allow the pipeline to pass :/

repo: external-secrets/external-secrets


text:
Question: How to get parent group of node?

At first, thanks you for your awesome library 🥰. I have tried to read your source code for self-answering but it take so much time.
Assumption I have a SVG file like below:
<g id="parent-group">
    <path id="path1">

    <path id="path2">

    <path id="path3">

</g>

If I have a node of path1, how can I retrieve the group it belongs to (parent-group)?

Hi Duy,
Unfortunately there is no API for that, because in Macaw node can have multiple parents. But here is implementation you can use:
private func findParent(of node: Node, in view: MacawView) -> Node? {
    return findParent(of: node, in: view.node)
}

private func findParent(of node: Node, in container: Node) -> Node? {
    if container == node {
        return container
    }
    if let group = container as? Group {
        for child in group.contents {
            if let result = findParent(of: node, in: child) {
                return result
            }
        }
    }
    return nil
}

authors: duytph ystrot

repo: exyte/Macaw


text:
🛑 AUR Repo is down

In 3910b1a, AUR Repo (https://aur.eyenx.ch/x86_64/eyenx.db.tar.gz) was down:

HTTP code: 404
Response time: 393 ms

Resolved: AUR Repo is back up in 5f99347.

repo: eyenx/upptime


text:
Website | Add new composite chart section and dual axis chart

Adding a new section for composite chart. (With more examples coming)
Add an example for dual axis chart.

I ported over the one example in dev. Used generated data. Since it's pretty controversial in terms of whether/when people should use it, I figure we simply demo the way to do it, so users know it's a possibility.

@lee00678 Great, thanks!
I think we should add to the description some brief text and references about pros and cons of using dual axis charts. Datawrapper has a great blog post on the subject: https://blog.datawrapper.de/dualaxis/

Also, I don't really like the style of the chart I created (I think there's too much red), but maybe it will help scare people away from using two-axis charts 😄

Also, I don't really like the style of the chart I created (I think there's too much red), but maybe it will help scare people away from using two-axis charts 😄

I'm happy to change it to bright orange 🔶 to make it more scary.

@lee00678 Yes, let's just flip them, thanks!

@lee00678 Great, thanks!
I think we should add to the description some brief text and references about pros and cons of using dual axis charts. Datawrapper has a great blog post on the subject: https://blog.datawrapper.de/dualaxis/

I added the following description, honestly I don't think there are much pros out there. Happy to edit.
This example shows how to create dual axis chart by overlapping two charts. Dual Axis chart maybe good at showing correlations, or compare two datasets with different measurement units. But we suggest using it with caution. Here are some good articles from [Datawrapper](https://blog.datawrapper.de/dualaxis/) and [Florish](https://flourish.studio/blog/dual-axis-charts/).

@lee00678 Nice, I like it, thanks!

Thanks for the reviews!


text:
Unable to drag driving scrollview to change notch level.

I discovered an interesting bug where if:

Sheet has a scrollable list with the list set as the driving scrollview.
Start from 0 rows.
Reload with rows greater than 0.

Result:
The sheet will no longer be draggable using the driving scrollview to change notch levels, only by using views that are not part of the list (ie. grabber). At this point, the only way to get the drag to update notch level functionality back is by having a button that programmatically set the notch to a different level at least once. Only then, will the drag to change notch level functionality will be restored.
I am running:

Xcode 14.3.1.
iOS 16.4.
DynamicOverlay 1.0.2.

Is this a quick fix or is it more involved? Thanks for the great library!

Hi @louwe could you provide a sample code? 🙏

authors: gaetanzanella louwe

repo: faberNovel/DynamicOverlay


text:
Avoid pinger to kill program

Hello,
When I order a larger number of instances, sometimes, the pinger throws this error: new Error('[ping] should have hostname and port'); making the overall program to restart.
Here is a suggestion for the pinger:
`
if (!options || !options.hostname || !options.port) {
    winston.debug('[Pinger] ping: null / null ');

	return new Promise((resolve, reject) => {
		return reject('[ping] should have hostname and port');
	});

}else{

	winston.debug('[Pinger] ping: hostname=%s / port=%d', options.hostname, options.port);

	const opts = {
		method: 'GET',
		url: `http://${options.hostname}:${options.port}/ping`,
		timeout: options.timeout || 5000, // Set default timeout to 5s
	};

	return new Promise((resolve, reject) => {
		request(opts, (err, res, body) => {
			if (err) {
				return reject(err);
			}

			if (res.statusCode !== 200) {
				return reject(body);
			}

			return resolve(body);
		});
	});
}

`
What do you think ?
Best,
Anis

Hello @anisgandoura ,
Nice idea :)
Will be in next release (https://github.com/fabienvauchelles/scrapoxy/commit/4b6c3a508863b54a4574390b8f1e2c603b431c22)
Are you still at Station F ?
Fabien.

authors: anisgandoura fabienvauchelles

repo: fabienvauchelles/scrapoxy


text:
Prevent / in filePath be encoded.

convert
https://github.com/fabiospampinato/vscode-open-in-github/blob/master/src%2Fcommands.ts/#L119
to
https://github.com/fabiospampinato/vscode-open-in-github/blob/master/src/commands.ts/#L119

Both urls seem to be working so I'm not sure why this should be changed 🤔

But %2F is not human friendly.

Are you considering merging this pr?

Are you considering merging the PR?

Yes otherwise I would have closed.
Available in v1.2.2.

authors: fabiospampinato ipcjs

repo: fabiospampinato/vscode-open-in-github


text:
Strange {% spaceless %} and {% collapse %} suggestion

Hallo Fabien,
sorry for my terrible english.
I'm not sure that it's issue, but it's a bit strange for me
code:
{% spaceless %}

  Hallo Fabien

{% endspaceless %}

expected:

Hallo Fabien

got:

HalloFabien

Of course I can use   instead of space between  and
But I belive {% spaceless %} tag should not remove spaces between inline HTML tags.
Also I suggest {% collapse %} tag:
{% collapse %}
{{ some_thing }}

  here is some content

div

    pre1

{% for i in arr %}...{% endfor %}
...
{% endcollapse %}

Above code should work like this:
{{ some_thing }}                  {{-''-}}

                             {{-''-}}
  here is some content            {{-''-}}

div
                  {{-''-}}

                           {{-''-}}
    pre1                          {{-''-}}

                          {{-''-}}

                            {{-''-}}
{% for i in arr %}...{% endfor %} {{-''-}}
...                               {{-''-}}

or that:
{{ some_thing }}
here is some content
div

pre1

{% for i in arr %}...{% endfor %}...

Or simply {% spaceless %} should not affects on any value that can be returned from {{ ... }}
Best regards,
Grigoriy

This is the expected behavior; spaceless removes all spaces between tags. We won't change the behavior for two reasons: first, it would break BC, then I don't see why you would want to keep some spaces and remove some others.

I agree with you that Twig could be made a bit smarter here and there, and respect the semantics of the HTML that it is generating, but it would be a general departure from the current "simple" approach.

"I don't see why you would want to keep some spaces and remove some others."
Why not just remove all the spaces, then? (Whynotjustremoveallthespaces,then?)
In HTML, spaces between block-level tags are discarded by the browser. They just waste space and bandwidth. Spaces between inline tags are rendered because they are actually spaces. Consider the example in the first post, it's the difference between "Hello Fabien" and "HelloFabien".
So I can easily see why you might want to discard the unrendered spaces and keep the rendered ones.

authors: fabpot mrxotey schmittjoh webarnes

repo: fabpot/Twig


text:
Fix select element background on iOS 15

As mentioned in #fabric-private - we need to explicitly set this for iOS 15 or it turns the background gray

Yeah, this is a new default in iOS 15 that is no bueno since it makes our select field look very much like our idea of a disabled field

repo: fabric-ds/css


text:
use appropriate sentry user id

Sentry uses token id as user id, but it needs to use subject.
fixes: https://github.com/fabric8-services/fabric8-wit/issues/1968

@surajssd snapshot fabric8-wit image is available for testing.  docker pull docker.io/fabric8/fabric8-wit:SNAPSHOT-PR-1970-7


text:
fix(test): add unit test for group type reducer

Note: If there are pending changes to the PR, prefix the PR title with "WIP" and add the label "DO NOT MERGE"
Mandatory

[ ] What does this PR do?
Added unit tests for group type reducer.
[ ] What issue/task does this PR references?
https://openshift.io/openshiftio/openshiftio/plan/detail/2282
[ ] Are the tests Included?
Yes

@vikram-raj Your image is available in the registry. Run docker pull registry.devshift.net/fabric8-ui/fabric8-planner:SNAPSHOT-PR-2705 && docker run -it -p 5000:8080 registry.devshift.net/fabric8-ui/fabric8-planner:SNAPSHOT-PR-2705 and visit http://localhost:5000 to access it.

authors: centos-ci vikram-raj


text:
Update prod-preview test branch

Note: If there are pending changes to the PR, prefix the PR title with "WIP" and add the label "DO NOT MERGE"
Mandatory

[ ] What does this PR do?

[ ] What issue/task does this PR references?

[ ] Are the tests Included?

Optional

[ ] Is the documentation Included?

[ ] Are the Release Notes included?

[ ] @mention(s) to expected reviewer(s) included

@divyanshiGupta Your image is available in the registry. Run docker pull quay.io/openshiftio/fabric8-ui-fabric8-planner:SNAPSHOT-PR-2808 && docker run -it -p 5000:8080 quay.io/openshiftio/fabric8-ui-fabric8-planner:SNAPSHOT-PR-2808 and visit http://localhost:5000 to access it.

authors: centos-ci divyanshiGupta


text:
Search for a space in list of spaces

As a viewer or collaborator in spaces, I'd like to search the entire list of spaces I'm currently collaborating in, so that I can pinpoint a specific space to navigate to.
The spaces should be listed and searchable at the route: /<username>/spaces
The spaces should be retrieved from the REST API from the Spaces resource at /api/spaces.
Functional Acceptance criteria:

Entering a search criteria in the search box should initiate a search.
The spaces listed below in the space list, should match the search criteria.
The search criteria should be executed against the name of the space and the description. The search results should highlight the matches in the name and/or description.

For now, typeahead is likely to be used for implementing the search functionality.

Fixed by #269 I think

authors: VineetReynolds pmuir


text:
Rethrow promise errors

Motivation
Currently any exceptions thrown during server startup cause the process to silently exit.  This makes tracking down bugs in config files super frustrating.
Test Plan
Add this, see an error with a stack trace for my broken config.

Probably fixes #238

repo: facebook/Docusaurus


text:
Update documentation screeenshots & output examples

Since it was written we have:

Better stack trace line removal (shorter output).
Better trimming of path prefixes.
Colored stack traces.

Let's make this visible both at README.md and Sphinx docs.

Could I work on this?

@aryasoni98  Yes. if you could, that would be lovely

authors: aryasoni98 deathowl fornellas

repo: facebook/TestSlide


text:
Is it normal to receive a DEPRECATION WARNING if using sass and not node-sass?

Hello,
I have updated my react-scripts to version 4.0.3, and I wanted to replace node-sass with sass as well since it's been deprecated for some time.
The thing now is that I receive a deprecation warning: "DEPRECATION WARNING: The legacy JS API is deprecated and will be removed in Dart Sass 2.0.0. More info: https://sass-lang.com/d/legacy-js-api".
As far I understand one needs to use the modern api with sass-loader which has to be set in the webpack's config, but we don't have access to that in create-react-app:
https://create-react-app.dev/docs/adding-a-sass-stylesheet
https://sass-lang.com/documentation/breaking-changes/legacy-js-api/
https://webpack.js.org/loaders/sass-loader/#api
So my question is how to use this modern api in order to let this deprecated staff go?
Thank you in advance.

You may need to look at your scss files. I had to convert mine from @import to @use and then some other minor issues with namespaces and variables, I just did @use 'path/to/file/' as *;
Hope this helps!

@mrandrewjbaker, thanks.
So in other words you mean that changing those should make the compiler not use the old JS API?

https://sass-lang.com/documentation/at-rules/import/

Yes, thank you very much, @mrandrewjbaker. :)

Closing since it's not directly relevant to CRA as @mrandrewjbaker mentioned.

authors: JumpForJoy mrandrewjbaker

repo: facebook/create-react-app


text:
react-dev-utils 10.2.1: events.js:291       throw er; // Unhandled 'error' event

After updating react-dev-utils from:
"react-dev-utils": "^6.1.1",
to:
"react-dev-utils": "^10.2.1",
An error occurs:
events.js:291
throw er; // Unhandled 'error' event
^
Error: read ECONNRESET
at TCP.onStreamRead (internal/stream_base_commons.js:209:20)
Emitted 'error' event on Socket instance at:
at emitErrorNT (internal/streams/destroy.js:106:8)
at emitErrorCloseNT (internal/streams/destroy.js:74:3)
at processTicksAndRejections (internal/process/task_queues.js:80:21) {
errno: -4077,
code: 'ECONNRESET',
syscall: 'read'

I'm seeing this issue as well

I just had a co-worker run into this issue. It seems to be on Windows only. Haven't seen it on MacOS or Linux.

Having the same issue; on Windows 10.
I have tried React 17.0.1, React, 16.14.0, 16.13.1
I have tried Nodejs 15.1.0, 15.0.1, 14.15.0

I have same issue.
Could it be because of this package?
"babel-core": "^7.0.0-bridge.0",

Same issue here

It appears to be present in v11 as well. Downgrading to 9.1.0 seems to be the only solution for now.

Is there any update on this ticket react-dev-utils 11 faces this issue as well?

I was using react-dev-utils 11 and facing this problem. Just dowbgraded to version 9 and it worked.
yarn add react-dev-utils@9

Any updates?

authors: Ericarthurc JakeLokkesmoe TaylorBriggs aShelist danielo515 marcofugaro srinaath tomaszs


text:
Fix eqeqeq lint rule to allow nulls

Fixes #4807
Replaced the deprecated option following https://eslint.org/docs/rules/eqeqeq

Please open this against the next branch; we're no longer accepting updates to master.
Also, it looks like we want to use the smart mode.

No, I don't think "smart" is the way to go. It goes against the whole idea of using != and == only when necessary, and otherwise sticking to !== and !=. Plus it gives you "two ways" of doing things, leading to inconsistent codebases.

authors: Timer xixixao


text:
fix: add react-refresh as a dependency for templates

This fixes #9446 - basically I've added react-refresh to the starting templates so that the peerDependency from react-refresh-webpack-plugin would properly resolve in stricter module systems (e.g. Yarn 2 and PnP). It is already a dependency of react-scripts but that does not suffice because imports to react-refresh/runtime will be injected to the users' bundle.

Thanks for this @pmmmwh!
We also have community templates, it might be better to add it here?
https://github.com/facebook/create-react-app/blob/master/packages/create-react-app/createReactApp.js#L434
Maybe @iansu and/or @ianschmitz have some thoughts too.

I've update the PR to install react-refresh within the CRA command instead - I've made the changes where I think is necessary, but please feel free to correct me cause I'm not very familiar with the CLI's structure!

This should be fixed in the plugin instead by having it resolve it before injecting the import - https://github.com/pmmmwh/react-refresh-webpack-plugin/pull/230

This should be fixed in the plugin instead by having it resolve it before injecting the import - pmmmwh/react-refresh-webpack-plugin#230

Do you think that this is still needed after the fix in the plugin?

Do you think that this is still needed after the fix in the plugin?

Nope, it's not needed anymore. The plugin is updated in https://github.com/facebook/create-react-app/pull/9872 together with other dependency issues

Superseded by #9872

authors: merceyz mrmckeb pmmmwh


text:
fix for #64

This is my attempt to implement the optimizations mentioned in the issue. I assumed it was also safe to remove the 'in' check from 'getPositiveSpacing' as well because if it is null then will not be >= 0 I would be happy to make any requested changes if this isn't quite right.
Thanks!

Hey,
I will gladly make this safer then time the tests and  give you the output. I should have thought out my changes a bit more thoroughly, sorry about that!

Also would making it  look like
return node.style['marginTop'] || node.style['margin'] || 0;
work if I excluded the return 0 on exiting the loop? Otherwise I can add check for being undefined.
Also for the tests do I use the RunLayoutRandomTests.html to do this?  Or the tests that are in the tests dir?

Also, opening RunLayoutRandomTests.html before my changes finishes in about 2.2 seconds on chrome and after it finishes in about 1 second

Hey so after working on this for a while yesterday I found that there wasn't much of a performance improvement on my machine, and that the changes caused a slight increase in the number of failures on the layout tests. Thanks for taking a look at what I had. I will close the PR.

repo: facebook/css-layout


text:
Only HTML is loaded using github pages

🐛 Bug Report
By following the documentation written in Docusaurus, I'm trying to deploy using the gh-pages branch.
Problem being that only the HTML is loaded, the whole javascript etc is not loaded throwing 404 or content security issues
Have you read the Contributing Guidelines on issues?
Yes
To Reproduce

Clone the repo https://github.com/Vident/vident and cd into the documentation folder
Yarn and yarn build
Open the index.html in the browser and only the html content will appear. It's doing the same on the gh-pages

You can find the whole configuration on the following repo: https://github.com/Vident/vident
And the result here: https://vident.github.io/vident/
Expected behavior

Render the styled page
Actual Behavior

Renders HTML only and cannot load other pages
Your Environment

Docusaurus version used: 2.0.0-alpha.58
Environment name and version (e.g. Chrome 78.0.3904.108, Node.js 10.17.0): Chrome Version 83, NodeJS version 12.18.1, yarn version 1.22.4
Operating system and version (desktop or mobile): Macos 11 beta 2

Reproducible Demo
Already described in the steps to reproduce. You can find how it renders to this link: https://vident.github.io/vident/
The whole configuration is in the repo which is public: https://github.com/Vident/vident

Hi,
You need to set a baseurl if you are not hosting the site at the root of your domain (/vident), like it is documented.
=> https://github.com/Vident/vident/pull/3

authors: psyycker slorber

repo: facebook/docusaurus