ButtonBarPagerTabStripViewController crash

ButtonBarPagerTabStripViewController crashes sometimes when I click on buttonBarView.
It crashes in ButtonBarPagerTabStripViewController at
let oldCell = buttonBarView.cellForItemAtIndexPath(NSIndexPath(forItem: currentIndex, inSection: 0)) as! ButtonBarViewCell

with Optional null exception.
I fixed that by replacing as! ButtonBarViewCell with as? ButtonBarViewCell but I'm not sure if it's not affecting something else.

@tailec Can you show me step by step how you are setting up the buttonBarView?

@mtnbarreto I created sample project here: https://github.com/tailec/XLPagerTabStripTestProject
If you're on the first tab, try to tap on the last one. It crashes :)

@tailec Thanks for the sample project, it was very useful. As you said there is a bug when the oldCell is no longer visible in the buttonBarView collectionView,  in this particular case buttonBarView.cellForItemAtIndexPath(NSIndexPath(forItem: currentIndex, inSection: 0)) returns nil and as! makes the app crash.
Do you want to fix it with the change you proposed initially?

Yeah sure, I'll make PR this evening as soon as I get back home

:+1:  thanks!


Typo in README

Hi, I think this command in your testing example
python tools/test.py --config-file configs/scannet/semseg-pt-v2m2-0-base.py --options save_path=exp/scannet/semseg-pt-v2m2-0-base weight=exp/scannet/semseg-pt-v2m2-0-base/models/model_best.pth

should be
python tools/test.py --config-file configs/scannet/semseg-pt-v2m2-0-base.py --options save_path=exp/scannet/semseg-pt-v2m2-0-base weight=exp/scannet/semseg-pt-v2m2-0-base/model/model_best.pth

model_best.pth is under model/ not models/.

Yes, thanks for pointing out this issue, and I have already fixed the bug in README.


Feature/civ 322 uptade lint

JIRA link
CIV-322
Change description
Updated lint version
Does this PR introduce a breaking change? (check one with "x")
[ ] Yes
[x] No

The templates/NOTES.txt file should be reinstated and the linting issue fixed. Note that the templates folder is not causing the linting issue.

Closing this pr as this is not relevant


release: v0.7.2

Description: 概要

Changes: 変更内容

Changes

fix: after reserved error (cf5e9b6aa20cab5a99b164c698ee9bf164371f10)
chore: add license file (06a6d13905286be73f506615e6d6bbe842b95fca)
chore: consider responsive (eaaa958dd92025fae9b80c624273994a838afc08)
chore: update lp (2a6111c33cb5f60a82dd686e8de7efc1864f3dc2)

Expected Impact: 影響範囲

Operating Requirements: 動作要件

Additional context: 補足

Command results

Details:

add path
/home/runner/work/_actions/technote-space/create-pr-action/v2/node_modules/npm-check-updates/bin

yarn update
yarn run v1.22.5
$ yarn update:core && yarn workspaces run update && yarn install && yarn upgrade && yarn audit
$ npx npm-check-updates -u --timeout 100000
Upgrading /home/runner/work/frourio-demo/frourio-demo/package.json

All dependencies match the latest package versions :)

> @frourio-demo/types
$ npx npm-check-updates -u --timeout 100000
Upgrading /home/runner/work/frourio-demo/frourio-demo/shared/types/package.json

 @types/react  ^17.0.0  →  ^17.0.1

Run npm install to install new versions.

> @frourio-demo/utils
$ npx npm-check-updates -u --timeout 100000
Upgrading /home/runner/work/frourio-demo/frourio-demo/shared/utils/package.json

 @types/react  ^17.0.0  →  ^17.0.1

Run npm install to install new versions.

> @frourio-demo/admin
$ npx npm-check-updates -u --timeout 100000 -x @date-io/date-fns,next-transpile-modules
Upgrading /home/runner/work/frourio-demo/frourio-demo/apps/admin/package.json

 @types/react  ^17.0.0  →  ^17.0.1

Run npm install to install new versions.

> @frourio-demo/front
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.
info Visit https://yarnpkg.com/en/docs/cli/workspaces for documentation about this command.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

stderr:
npx: installed 318 in 13.296s

npx: installed 318 in 7.801s

npx: installed 318 in 7.868s

npx: installed 318 in 8.475s

error<EMAIL_ADDRESS>The platform "linux" is incompatible with this module.
error Commands cannot run with an incompatible environment.
error Command failed.
Exit code: 1
Command: /usr/local/bin/node
Arguments: /usr/share/yarn/lib/cli.js run update
Directory: /home/runner/work/frourio-demo/frourio-demo/apps/front
Output:

error Command failed with exit code 1.

Changed files

Changed 3 files:

apps/admin/package.json
shared/types/package.json
shared/utils/package.json

:octocat: Repo | :memo: Issues | :department_store: Marketplace


Modify FunctionApp.bicep and BuildParams.ps1 file to allow using existing Storage Account.

FunctionApp.bicep
//Storage Account
@description('Required: Yes | Name of the storage account used by the Function App. This name must be unique across all existing storage account names in Azure. It must be 3 to 24 characters in length and use numbers and lower-case letters only.')
param StorageAccountName string
@description('Required: Yes | Name of the resource group where the existing storage account was created.')
param StorageAccountResourceGroup string
// Reference existing Storage Account
resource storageAccount 'Microsoft.Storage/storageAccounts@2022-09-01' existing = {
name: StorageAccountName
scope: resourceGroup(StorageAccountResourceGroup)
}
BuildParams.ps1
BicepParams       = @{
#Storage Account
StorageAccountResourceGroup                = 'RG-SA'
StorageAccountName                        = 'SA-name'

Hi Kyle,
If you are interested, I have an example forked here where I needed to deploy multiple function apps that use the same app service plan, log analytics and storage account.
https://github.com/Thomas-Butterfield/AVDReplacementPlans/tree/public-sample-use-case/Build/Bicep


[mem] Implement HW support of ECC protection on main memory with byte access

ECC is preferred on main memory, but we also want to have byte-access. Options

ECC on main memory, software does RMW to avoid byte accesses
ECC on main memory, hardware does RMW on byte accesses
parity on main memory, byte accesses are easy

Need software input on the cost of lowRISC/stwg-base#1

@tjaychen @msfschaffner I think there has been some thinking on this issue recently, can you update this issue with the current status?
In terms of implementation, we now have prim_ram_1p_adv as a wrapper available for such functionality, and prim_ram_2p_adv as an example how to implement some of the ECC/Parity functionality, not yet considering write masks.

@imphil
thanks Phil will do. Sorry I need to document the memory scrambling / ecc / parity discussion we did a couple of months ago.
I just have not gotten to it.  It is in a way..somewhat on-hold because I am hoping to get some security lab guidance to make sure it is okay.

assign to myself to documentation purposes

@tjaychen no worries, we just got reminded of this one today when talking about the icache, but there's nothing blocked at the moment by this issue.

Not the solution, but an implementation step towards it, is in https://github.com/lowRISC/opentitan/pull/2418

this issue is quite stale now.
Just for the sake of closure, we opted for scrambling + parity on the main sram.
This is because we determined that it was important for have a fast (single cycle) working memory for the processor, and the potential latency of ECC piling up, in the absence of something like a dcache (other security holes) just was not worth it.
I'm closing this now, if anyone objects, please feel free to re-open.


Adjusted the ALM examples and operator capabilities in CSV

Signed-off-by: Juraci Paixão Kröhling<EMAIL_ADDRESS>

The examples list has now three examples:

Simplest
Simple prod (with external Elasticsearch)
Badger with volumes

Let me know if you agree with the choice of examples.

How about jaeger-all-in-one-in-memory (for simplest), jaeger-prod-elasticsearch (simple-prod) and jaeger-all-in-one-local-storage (badger) ?


AZURE_CLIENT_CERTIFICATE_LOCATION environment variable for Azure.Identity is not working

Referring to https://docs.microsoft.com/en-us/dotnet/api/azure.identity?view=azure-dotnet and https://docs.microsoft.com/en-us/dotnet/api/azure.identity.environmentcredential?view=azure-dotnet, it is stated:

AZURE_CLIENT_CERTIFICATE_LOCATION
A path to the certificate that was generate for the App Registration.

I tested a simple application, providing environment variables AZURE_TENANT_ID, AZURE_CLIENT_ID and AZURE_CLIENT_CERTIFICATE_LOCATION, but does not seem to work.
Directly using ClientCertificateCredential using the same values works fine.

That is because the documentation in some places is incorrect as of this posting. I had to check the code directly to get my bearings.
Make sure you have updated Azure.Identity ≥ 1.2.0. Use AZURE_CLIENT_CERTIFICATE_PATH instead of AZURE_CLIENT_CERTIFICATE_LOCATION. This setting accepts the location of either a .pem or .pfx. You need to make sure the certificate is accessible by the application. There isn't a password. Since there isn't a password, you need to assign your service account access to the certificate. ericmbowden submitted a comment on another issue that may provide additional help.

@ShamsulAmry closing this issue for now -- please let me know if you are still running into this.


SimpleCopy Paste Augmentation Implementation

Simple Copy Paste is a data augmentation technique which is extremely useful for generating data for training and testing.
Motivation
There is a recent paper https://arxiv.org/abs/2012.07177,  which is very helpful for improving scores in instance segmentation and classification.
Related resources
https://github.com/tensorflow/tpu/tree/master/models/official/detection/projects/copy_paste
Additional context
Hi, we have implemented this feature already in mmdet for the LVIS 2021 challenge and we have made our submission. We want to add our code to the official repository and hence submit a PR. We feel this would be a great addition to the repository.
If we get the go ahead, me, along with @GrantorShadow and @akki2503 will work on formatting our code, adding tests and so on, so that we can cleanly add it to the repo.

@sudz123 thank you very much. If you have any questions, please feel free to contact us.

Hi @sudz123 ,
PRs are definitely welcomed! We will also organize the PR review as soon as the PRs are created.
To make the progress more smooth, it is also preferred if you could briefly describe your plan, e.g., the module you want to add and the related potential modification. You can also describe that following the PR template when creating the PR.

Hi @ZwwWayne Can you point out where we can find the PR template?
To summarise the plan:

We will add one new Class to mmdet.datasets.pipelines.transforms called SimpleCopyPaste. The code will exactly match the official implementation.
This class will take in two images at random and hence use the class MultiImageMixDataset from mmdet.datasets.dataset_wrappers.py
We will provide one simple config which uses mask rcnn with SimpleCopyPaste.
We can also provide trained model results for a small backbone like ResNet18, ResNet50 and put this in the ReadMe in the configs.

We, however, cannot give the exact backbone implementation given in the original paper and the corresponding model since it was trained using a large batch size for very long and we do not have the compute power to replicate it. I hope that is okay?
We will submit the PR within this week and based on comments, we will modify and then close it as soon as possible.

Hi @ZwwWayne Can you point out where we can find the PR template?
To summarise the plan:

We will add one new Class to mmdet.datasets.pipelines.transforms called SimpleCopyPaste. The code will exactly match the official implementation.
This class will take in two images at random and hence use the class MultiImageMixDataset from mmdet.datasets.dataset_wrappers.py
We will provide one simple config which uses mask rcnn with SimpleCopyPaste.
We can also provide trained model results for a small backbone like ResNet18, ResNet50 and put this in the ReadMe in the configs.

We, however, cannot give the exact backbone implementation given in the original paper and the corresponding model since it was trained using a large batch size for very long and we do not have the compute power to replicate it. I hope that is okay?
We will submit the PR within this week and based on comments, we will modify and then close it as soon as possible.

When you creating a PR, the template will be shown on the web page.

Hello, I am interested in your inplementation and I wonder if SimpleCopy Paste is available. Also, how can I add this one to my project (for example, configs and the place of the [SimpleCopy Paste] original code). Thank you~~

Already in https://github.com/open-mmlab/mmdetection/tree/master/configs/simple_copy_paste through https://github.com/open-mmlab/mmdetection/pull/7501


RFC: CDC Source Node (MySQL)

Migrated from Notion.

will we have another discussion or merge directly?

will we have another discussion or merge directly?

It is just a migration of the previous RFC. The conclusion is below.

To make the source node pure stateless, its lifecycle should align with compute node (source executors). When the CN crashed the source node will experience a grpc connection error, then corresponding CDC engines should exit.
Based on above conclusion, we can use only one rpc interface to create and consume CDC events
The source (connector) node will deploy as a sidecar with compute node
To verify the database connector properties we may need to deploy source node as sidecar with Meta node and verify in the process of create source.


Invalid pool management

As per comments here: https://github.com/One-com/node-postgres-migrate/commit/69644cf492f08229359e22f75d565b14cc4b343b

Quote from the above mentioned commit - wan't to continue the discussion here and keep the context :-)

This doesn't really do anything. There is no such option in pg-promise as poolSize.
If you really want to achieve such effect, you need to do the following:

pgp.pg.defaults.poolSize = 0;

I'm not sure what it will do exactly, so I can't advise for or against this. This is not a common practice.

Thanks for reaching out @vitaly-t. I did that change in a hurry, while debugging connection pool exhaustion and obviously didn't test it thoroughly enough. Thanks for bringing it to my attention.
I was trying to read through some of your code, and I must have misread something, but I thought that you passed unknown options through to the vanilla pg module.
Setting the poolSize to 0 disables connection pooling in the pg module (which is enabled by default). I wanted to do that, as the migration stuff is something that you run as a one-off thing before bootstrapping an application - or before running it at all. Doing it this way, allows me to ignore connection pooling entirely, which was not really called for in the situation any way.
The specific problem that I thought I was solving was with a test suite that opened multiple connections to multiple different databases within the same postgres instance. Some of them through pg-promise, and some of them through knex which carries its own connection pool implementation. I wanted to simplify things, by only having one kind of pools in play, instead of having the default one from the postgres module on top.

I believe you will get far better results by reducing the pool size. The default is 10. And if you set it to 2, it will be far better than disabling it.
That option belongs to node-postgres settings, it is part of pg-promise. And the node-posgres instance is available from pg-promise via property pg as shown in the example.
See also: FAQ: How to access the instance of node-postgres that's used?

I know that it's not common practice, but it's documented in the node-postgres module, and it is exactly what I think this situation call for. What do you think?
I know that the code I'm executing need to run in sequence, thus I have no need to fan out over multiple connections. One is enough, and no connection pooling behavior simplifies stuff a lot.

Just keep in mind that the moment you try to execute something at the same time, you will run out of connections, which in turn may result in some queries fail, if something else is taking too long to execute.
People who use full potential of the connection pool often have to implement an additional layer of a re-try when the connection pool is exhausted.

@vitaly-t Given my rather limited use case here, I am very sure, that I'll never need to execute anything in parallel. In order to give the guarantees about the migrations that I need, I must execute sequentially anyway, so this is not a problem for my particular use case :-)

Properly fixed in https://github.com/One-com/node-postgres-migrate/commit/61885a3c70b627db9b93a1038f5a4e339ea8dcb4 and released with v1.1.1


feat: updated packages

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Feature/1648 remove the old voluntary conversion locales

Changes
Add a summary of the changes in this pull request
Checklist

[x] Attach this pull request to the appropriate card in Trello.
[ ] Update the CHANGELOG.md if needed.

 Remove the old voluntary conversion locales


Issues with SSL cert

export DOCKER_HOST=tcp://<IP_ADDRESS>:2376
export DOCKER_CERT_PATH='C:\Users\nolan\.boot2docker\certs\boot2docker-vm'
export DOCKER_TLS_VERIFY=1

bash-3.1$ boot2docker up
Waiting for VM and Docker daemon to start...
............o
Started.
Writing C:\Users\nolan.boot2docker\certs\boot2docker-vm\ca.pem
Writing C:\Users\nolan.boot2docker\certs\boot2docker-vm\cert.pem
Writing C:\Users\nolan.boot2docker\certs\boot2docker-vm\key.pem
Your environment variables are already set correctly.
bash-3.1$ docker version
Client version: 1.7.0
Client API version: 1.19
Go version (client): go1.4.2
Git commit (client): 0baf609
OS/Arch (client): windows/amd64
An error occurred trying to connect: Get https://<IP_ADDRESS>:2376/v1.19/versi
on: x509: certificate is valid for <IP_ADDRESS>, <IP_ADDRESS>, not <IP_ADDRESS>
The ISO is at version 1.7.0 as well.

Sorry, this repository is long-since deprecated in favor of Docker Toolbox (whose usage is now also discouraged in favor of Docker for Windows and Docker for Mac).


pyarrow data type error cause lot of dependent project crash

Describe the bug, including details regarding any error messages, version, and platform.
several project depends on pyarrow crash on type conversation

Data Wrangler
Polars

df = pl.DataFrame(pd)
ArrowInvalid: Could not convert '230' with type str: tried to convert to double
Component(s)
Python

Could you share a concrete reproducible example so we can see where the issue might be?

I have this dataset, when the string is mixed with float datatype, pandas will read as mixed datatype but not pyarrow,
therefore it breaks Data wrangler, and ability convert pd to polars, or export as parquet
https://drive.google.com/file/d/1uxKSIqZ7IUEQ1Qp_LgB2qSAZDQEKteJl/view?usp=sharing

Yes, Arrow array (or column) has one data type by definition. Defining the column (with mixed float and string) as a string should solve the problem?

thanks,

In case you have any follow-up questions, do not hesitate to re-open the issue.


Opt-out Google Analytics in future settings

I have assigned @monstermunchkin to this, please include an opt-out in the wizard and also check if we receive data at all (see https://www.google.com/analytics/)


Test: Validate domain config test for attrValidator

Description: This PR introduces enhanced unit tests for attrValidator.go in the uber/cadence/common/domain package, focusing on increasing test coverage through comprehensive, table-driven tests. It covers a range of scenarios including edge cases and error conditions for domain attribute validation functions.

Why?: To improve code quality and reliability by ensuring all logical paths are tested, which helps in early detection of potential bugs and maintains high standards for the Cadence codebase.

How did you test it?: Tests were added and executed locally to verify their effectiveness. The coverage tool was used to ensure that the new tests significantly increase coverage for attrValidator.go.

Potential risks: Minimal to none, as the changes are confined to unit tests which do not affect production code directly.

Release notes: Not applicable as the changes do not impact the functionality or schema.

Pull Request Test Coverage Report for Build 018dfcae-abec-49ca-b600-251b173f58ea
Details

0 of 0   changed or added relevant lines in 0 files are covered.
43 unchanged lines in 9 files lost coverage.
Overall coverage increased (+0.03%) to 62.917%

Files with Coverage Reduction
New Missed Lines
%

common/task/weighted_round_robin_task_scheduler.go
1
89.05%

common/task/fifo_task_scheduler.go
2
84.54%

service/history/task/transfer_active_task_executor.go
2
72.38%

service/history/task/transfer_standby_task_executor.go
2
87.42%

service/matching/taskListManager.go
2
79.7%

service/history/task/task_util.go
4
75.14%

service/history/task/fetcher.go
6
85.05%

service/history/task/cross_cluster_task_processor.go
8
80.79%

service/history/execution/mutable_state_task_refresher.go
16
59.81%

Totals

Change from base Build 018dfbb1-48ef-4faa-92f4-b269d8ca713f:
0.03%

Covered Lines:
92998

Relevant Lines:
147811

💛  - Coveralls


Box value encoded in a variant to reduce enum stack space

before
print-type-size type: `util::psbt::error::Error`: 120 bytes, alignment: 8 bytes
print-type-size     discriminant: 1 bytes
print-type-size     variant `CombineInconsistentKeySources`: 115 bytes
print-type-size         padding: 3 bytes
print-type-size         field `.0`: 112 bytes, alignment: 4 bytes
print-type-size     variant `InvalidKey`: 39 bytes
print-type-size         padding: 7 bytes
print-type-size         field `.0`: 32 bytes, alignment: 8 bytes

after
print-type-size type: `util::psbt::error::Error`: 40 bytes, alignment: 8 bytes
print-type-size     discriminant: 1 bytes
print-type-size     variant `InvalidKey`: 39 bytes
print-type-size         padding: 7 bytes
print-type-size         field `.0`: 32 bytes, alignment: 8 bytes
print-type-size     variant `DuplicateKey`: 39 bytes
print-type-size         padding: 7 bytes
print-type-size         field `.0`: 32 bytes, alignment: 8 bytes

util::psbt::error::Error is wrapped also in consensus::encode::Error and stack savings are gained there also

Interesting PR, I rarely think about the stack space of error enums. To educate me, can you please explain a few things if/when you have the time:

What led you to do this?
Why stop at the 115 byte variant, why not box all variants below X bytes?
What made you do this enum in particular? Should we be doing this by convention for all the error enums codebase wide?

No rush, just if you have time. Thanks

I see, paraphrasing to make sure I get you, the Result<T, E> has the same size as the biggest of T and E so even in the success path the size of the error effects stack usage.
So if we want to be particularly careful with stack usage we'd have to check the relation between T and E everywhere - sounds like hard work. Assuming the error path is infrequent then it would seem like good practice to box all error variants above some reasonable threshold,  just to be proactive?
And we may want to be careful with stack usage as we endevour to support smaller devices (WASM, no-std, ect.)?

Cool, so any error path that can be hit from PSBT code, that's a non-trivial amount of work to find out, right? Follow every type used in the psbt module and check its implementations. How serious are we about folk writing embedded signing devices in Rust? Is anyone doing this now that we know of?

@RCasatta, I am curious how do you print byte alignments?

@RCasatta, I am curious how do you print byte alignments?

RUSTFLAGS=-Zprint-type-sizes cargo +nightly build --release

Yea, actually no idea - is there a concrete use-case where this is important @RCasatta?

No concrete use-case in this case, I just spotted this big variant by looking at the aforementioned program. There are some example linked from this page https://nnethercote.github.io/perf-book/type-sizes.html?highlight=print#measuring-type-sizes where changes like this make performance impact

Specter Wallet has indicated a desire to use rust-miniscript (and therefore rust-bitcoin) in embedded contexts. I take this pretty seriously. Maybe we have no actual users, but I think that's probably because rust-bitcoin can't be used rather than that it isn't used. So anything that improves the viability of rust-bitcoin-on-embedded is good by me.
Regarding the reasoning for this, Matt's summary sounds great to me. (a) generally we should try not to have big error enums, (b) PSBT is both non-speed-critical and likely to be used on a hardware wallet, so let's try to be nice with stack space.


Add link to official images by python upstream

I'm OK with linking to these, but IMO the description on https://hub.docker.com/_/python is probably a more appropriate place (esp. since this README file is autogenerated from a boilerplate template for all the repositories in https://github.com/docker-library).
In linking to them, I think we also need to describe the caveats of what they are (multiple versions of Python in a single image), so users don't think they're general purpose replacements for what we maintain here. :sweat_smile:
(See also https://github.com/docker-library/python/issues/373#issuecomment-461116541 for where these have been discussed previously.)


Set data validation of a partial column/row cells 设置列校验时，如何设置从某一列的第几行到这一列结尾都需要校验？

目前的场景类似于：对于A列，从他的第6行开始，到最后一行需要设置校验；如果直接validation.SetSqref("A:A")，那么前五行的单元格也会被设置校验，这是不需要看到的，请问可以如何处理呢

This issue was similar with #1576. As the documentation says, you can set the data validation range by the Sqref field. You can set data validation of a partial column/row cells in column A with maximum rows constants (excelize.TotalRows) referenceA6:A1048576 (columns A and B A1:B1048576).

This issue was similar with #1576. As the documentation says, you can set the data validation range by the Sqref field. You can set data validation of a partial column/row cells in column A with maximum rows constants (excelize.TotalRows) referenceA6:A1048576.

I've closed this issue, if you have any questions, please let me know to reopen this anytime.


Version check fails for Node.js v6.10.0

Issue Summary
Ghost pre-install version check fails for Node.js v6.10.0.
Steps to Reproduce

Install Node.js v6.10.0.
Install Ghost.

As Node.js v6.10.0 is the latest LTS release, Ghost should accept it.
Technical details:

Ghost Version: 0.11.3
Node Version: 6.10.0
Browser/OS: Debian 8.7 (jessie)
Database: SQLite 3.10.10

FYI, anyone looking to pick this up I believe the offending code is here https://github.com/TryGhost/Ghost/blob/lts/core/server/utils/npm/preinstall.js#L34. My guess is that string sorting is failing us here because "10" comes before "9"

checking versions using string comparison? oo-er.

Found this today, how can I bypass this error?

http://support.ghost.org/supported-node-versions/

To disable the startup check in Ghost, set the environment variable GHOST_NODE_VERSION_CHECK to be false.
E.g. GHOST_NODE_VERSION_CHECK=false npm install --production.
E.g. GHOST_NODE_VERSION_CHECK=false npm start --production.

http://www.nodenica.com/error-al-instalar-ghostjs-version-0-11-5-en-heroku/ #spanish

closes via https://github.com/TryGhost/Ghost/pull/8046


Fatal error:  Uncaught exception 'Cmfcmf\OpenWeatherMap\Exception' with message 'Unknown fatal  error: OpenWeatherMap returned the following json object: ' Line 173

Hi,  when i want request a response of plugin i get this message sometimes, not always
error: OpenWeatherMap returned the following json object: ' in D:\xampp\htdocs\sfinal\plugins\Cmfcmf
\vendor\cmfcmf\openweathermap-php-api\Cmfcmf\OpenWeatherMap.php:173
what is the reason about that? .. thanks for your answer...

Hi, this means that the Open Weather Map API didn't return valid data. This library therefore couldn't decode it as XML nor as JSON. You could try to debug what the answer contains here before json_decoding it. https://github.com/cmfcmf/OpenWeatherMap-PHP-Api/blob/master/Cmfcmf/OpenWeatherMap.php#L169-L173


Support for geojson >= 3

Currently geojson has a constraint. geojson 3.0.1 was released a while back. It would be nice to get support for later geojson releases.
Thanks

Fixed in v0.5


#114 RemoveEdge

As per #114
RemoveEdge introduced.

@rultor merge

@rultor merge

@vssekorin OK, I'll try to merge now. You can check the progress of the merge here

@rultor merge

@vssekorin Done! FYI, the full log is here (took me 9min)


Add topic: terminal-share

Thanks for publishing this! How about adding it to GitHub.com/topics/terminal-share alongside similar tools by adding that topic to this repo? Thank you :-)

Topic terminal-share has been added.

Awesome, thank you :-)


New EF Hub and TOC update

Add new EF hub page design - index.yml
Update TOC to point to new index.yml
Remove old hub index.md

Unable to delete index.md and add index.yml at the same time without errors.  Closing and will try just adding the index.yml, publish that that in a separate pr, remove index.md


Add fake provider and building classes to allow better work on the UI.

This is still imperfect as I'm not well aware of the various states the
Pods can be in. One thing we could do is actually capture a couple of
build cases and provide them for replay at different speeds.

The main benefit of this over the current UI is that it lets you go through the full process yeah?

It does not change current UI, but fake the GitHub fetching and building
which should make working on the UI locally (when you do not have minikube)
easier. In the long term this should also allow you when working on the UI
to decide whether it should fail or succeed.
One thing I'd like to do for example is intercept the 'Step 13/39' do
display a more informative progress bar.
On Oct 29, 2017 11:03, "Chris Holdgraf"<EMAIL_ADDRESS>wrote:

The main benefit of this over the current UI is that it lets you go
through the full process yeah?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jupyterhub/binderhub/pull/230#issuecomment-340281470,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAUez848qFdYQNK4umv4iUp6xZsLUmweks5sxL3VgaJpZM4QJuYz
.

Thank you very much, @Carreau!

will this "just work" if we're running the localonly .py script? Or should we write docs to explain how to use this?

will this "just work" if we're running the localonly .py script? Or should we write docs to explain how to use this?

Will this "just work" if we're running the localonly .py script?

Yes.


Set download link from Mega to Github releases page

Hi Joel,
currently my intention is to rework the download link to point to a download webpage then:

download.html

Link to last stable download build (0.2.5b) -> main link point out to build hosted in webserver
Alternative link to last stable download build (0.2.5b) -> link point out to build hosted in github release page
Link to old builds -> link point out to build hosted in github release page
Link to 0.3 alpha builds -> link point out to builds hosted in MEGA or webserver build (I haven't decided yet because I don't know if the web server will support around 1TB/month transfer.)

Hi!
I can make this download.html page if you don't mind, probably with the same grid layout I did in the following community.html page:


debug tool bar not showing up in Production

I have a setup in public cloud, NGINX + GUNICORN + Django, I have followed all steps in official documents to install django-debug-toolbar, and have below configs in settings.py:
DEBUG = True

def show_toolbar(request):
    return True

DEBUG_TOOLBAR_CONFIG = {
    'SHOW_TOOLBAR_CALLBACK': 'project_name.settings.show_toolbar',
}

I also tried to set INTERNAL_IPS to public accessible address of my django server.
django-debug-toolbar never shows up. anything I missed out ?

This looks like it should do it. Does it work locally?

I do not have a local setup with NGINX and GUNICORN unfortunately. Hence, I did not try. And I did not want to try either as that was quite a lot efforts from me.

Oh sure, maybe not a local setup with nginx and gunicorn; just with the Django runserver (python manage.py runserver) to ensure that it really is a problem with the production environment.

Try passing the function itself rather than a path to the function as a
string.
Also you shouldn't use the toolbar in production as it exposes sensitive
information.
On Mon, Mar 7, 2022, 1:56 AM Matthias Kestenholz @.***>
wrote:

Oh sure, maybe not a local setup with nginx and gunicorn; just with the
Django runserver (python manage.py runserver) to ensure that it really is
a problem with the production environment.
—
Reply to this email directly, view it on GitHub
https://github.com/jazzband/django-debug-toolbar/issues/1591#issuecomment-1060287084,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAJYZP46BIWLRE6LR3B22QTU6WZBPANCNFSM5QCJR6QQ
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I found the debug_toolbar did show up in some specific URLs of my web sever.  When customized HTML template is applied, then debug_toolbar disappears. It seems related with HTML template. But I did not know how to troubleshoot ? any HTML template related configs required for debug_toolbar which I missed out ?

Maybe your customized HTML template does not contain a </body> string? This string is used to find the insertion point for the toolbar, see https://github.com/jazzband/django-debug-toolbar/blob/bf785130d5c60e4c269be154d231775d02008801/debug_toolbar/settings.py#L13

I have </body> and did see the <div> for debug_toolbar while inspecting HTML elements for that webpage. Most likely, I need to tweak my CSS to bring up the <div> for debug_toolbar.  thank you all for the help.

I finally figured out and now debug_toolbar is showing up and working properly. Let me summarize key troubleshooting steps here for anyone confronting same issue in the future.

Use Inspect Element in browser, I confirmed that debug_toolbar related HTML elements did exist.
Then I realized that browser failed to download debug_toolbar related CSS/JS files, I upload them to my NGINX static file serving server. After this, debug_toolbar showed up charmingly and worked perfectly.

Ah of course. We discussed if we should add the collectstatic step to the installation documentation in the past but opted not to because we really want to discourage people from running with the debug toolbar in production environments. It isn't hardened for production use, that's why.
(It may be fine but please add another layer of defense, e.g. HTTP basic authorization or an IP range block.)

strongly agree and completely understandable.  my website is deployed with Production setup but not officially released yet, so I can still play with it.

i get same trouble, it never show once ! i really don't know, even i follow official documents steps and steps!

Try passing the function itself rather than a path to the function as a string. Also you shouldn't use the toolbar in production as it exposes sensitive information.
…
On Mon, Mar 7, 2022, 1:56 AM Matthias Kestenholz @.> wrote: Oh sure, maybe not a local setup with nginx and gunicorn; just with the Django runserver (python manage.py runserver) to ensure that it really is a problem with the production environment. — Reply to this email directly, view it on GitHub <#1591 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJYZP46BIWLRE6LR3B22QTU6WZBPANCNFSM5QCJR6QQ . You are receiving this because you are subscribed to this thread.Message ID: @.>

Try passing the function itself rather than a path to the function as a string. Also you shouldn't use the toolbar in production as it exposes sensitive information.
…
On Mon, Mar 7, 2022, 1:56 AM Matthias Kestenholz @.> wrote: Oh sure, maybe not a local setup with nginx and gunicorn; just with the Django runserver (python manage.py runserver) to ensure that it really is a problem with the production environment. — Reply to this email directly, view it on GitHub <#1591 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/AAJYZP46BIWLRE6LR3B22QTU6WZBPANCNFSM5QCJR6QQ . You are receiving this because you are subscribed to this thread.Message ID: @.>

i get same trouble, it never show once ! i really don't know, even i follow official documents steps by steps!


Update contracts max size in genesis to 900K

Increased MaxWasmSize to 1000 * 1024 = 1MB. It is checked when uploading wasm byte code on genesis.
When we start using wasmd v0.30.0, this variable will also be taken into account when uploading wasm byte code via governance.


SCM view shows a shadow

todays insiders<PHONE_NUMBER>4e4c0fddbc1b3b728013744ae90840)
the SCM view shows a shadow above the input box

DOM hints towards tree sticky scroll

@benibenj, could you please take a look? Thanks!

The sticky scroll shadow was not being removed anymore since my latest changes, fixed it here: https://github.com/microsoft/vscode/pull/202490


feat(ui): Adjust the long title of challenge on challenge card

closes #1948

Changelog

truncate long string > 60 chars with ellipsis

Note
According to the current schemas, the title of challenge should not have more than 60 chars. The challenge title (challengeName) should be enforced when seeding data via SQL to match the maximum chars defined in schemas. The truncation in this pr is still useful to prevent from this situation and retain the styling of the challenge card.

Preview

I kind of remember a discussion with Verena about 60 char being too short for titles. Even if we end up accepting longer titles, displaying max 60 chars with an ellipse on the card should be a future-proof solution.

This is kind of a weird case. Maybe we should avoid breaking words with the ellipse?

Updated
If the last word exceeds the maximum limit, remove the entire word as well as special characters.

Converting this PR to draft the time to implement the changes discussed this morning.

@tschaffter it seems data response by sorting relevance is returned in the same order now 😮

@rrchai Are you referring to #1651?

@rrchai Are you referring to https://github.com/Sage-Bionetworks/sage-monorepo/issues/1651?

Yeah, I tried to refresh multiple times, I got the same order of challenges, at least the first couple lines.


Revise etcd task prerequisites to remove playground envs

The etcd operation and maintenance job is not supposed to run on the playground environments.
closes: #4479

remove the hold label, as the above comment is addressed.
/unhold

Preview looks good: https://deploy-preview-43277--kubernetes-io-main-staging.netlify.app/docs/tasks/administer-cluster/configure-upgrade-etcd/#before-you-begin
/lgtm


Metrics not returned via custom.metrics.k8s.io

Hi,
I’m using prometheus adapter, and I’m trying to get the K8S HPA do its job based on the metric I’ve set prometheus to scrape via the config rules-
data:
config.yaml: |
rules:
- metricsQuery: sum by (kubernetes_pod_name) (hydra_ws_active_conn)
name:
as: hydra_ws_active_conn
matches: ^.*
resources:
overrides:
kubernetes_namespace:
resource: namespace
kubernetes_pod_name:
resource: pod
seriesQuery: hydra_ws_active_conn{kubernetes_namespace!="",kubernetes_pod_name!=""}
- metricsQuery: sum by (app) (hydra_server_semaphore_latency_second_sum{app="agent-gateway-api", kubernetes_namespace="agent-gateway-api"})
name:
as: hydra_api_latency
matches: ^.*
resources:
overrides:
kubernetes_namespace:
resource: namespace
kubernetes_pod_name:
resource: pod
seriesQuery: hydra_server_semaphore_latency_second_sum{app="agent-gateway-api", kubernetes_namespace="agent-gateway-api"}
I’m trying to figure out what’s not right with the second query.
The first query is working and I get data-
$ kubectl get --raw "/apis/custom.metrics.k8s.io/v1beta1/namespaces/agent-gateway-api/pods/*/hydra_ws_active_conn" | jq .
{
"kind": "MetricValueList",
"apiVersion": "custom.metrics.k8s.io/v1beta1",
"metadata": {
"selfLink": "/apis/custom.metrics.k8s.io/v1beta1/namespaces/agent-gateway-api/pods/%2A/hydra_ws_active_conn"
},
"items": [
{
"describedObject": {
"kind": "Pod",
"namespace": "agent-gateway-api",
"name": "agent-gateway-api-ws-868f454554-cbs65",
"apiVersion": "/v1"
},
"metricName": "hydra_ws_active_conn",
"timestamp": "2020-08-04T11:24:52Z",
"value": "1273",
"selector": null
},
....
When I try the second metric, an empty array is displayed-
$ kubectl get --raw "/apis/custom.metrics.k8s.io/v1beta1/namespaces/agent-gateway-api/pods/*/hydra_api_latency" | jq .
{
"kind": "MetricValueList",
"apiVersion": "custom.metrics.k8s.io/v1beta1",
"metadata": {
"selfLink": "/apis/custom.metrics.k8s.io/v1beta1/namespaces/agent-gateway-api/pods/%2A/hydra_api_latency"
},
"items": []
}
From the metrics point, they both get reported, tried to attach images to prove but can't upload images here for some reason. The images show the Grafana explore querying the above metricsQuery queries and shows the same results structure.
Any idea why do I get an empty array for the second query?

I am facing the same issue
$ kubectl get --raw  /apis/custom.metrics.k8s.io/v1beta1/namespaces/<>/pods/*/Test_ReadyPool_Total_Num_Messages | jq
{
"kind": "MetricValueList",
"apiVersion": "custom.metrics.k8s.io/v1beta1",
"metadata": {
"selfLink": "/apis/custom.metrics.k8s.io/v1beta1/namespaces/<>/pods/%2A/Test_ReadyPool_Total_Num_Messages"
},
"items": [
{
"describedObject": {
"kind": "Pod",
"namespace": "<>",
"name": "autoscaling-7c7b45c7c-t7sh9",
"apiVersion": "/v1"
},
"metricName": "Test_ReadyPool_Total_Num_Messages",
"timestamp": "2020-08-06T09:44:32Z",
"value": "0",
"selector": null
}
]
}
Charless-MacBook-Pro:autoscaling charlesparasa$ kubectl describe hpa test-consumer-hpa
Error from server (NotFound): horizontalpodautoscalers.autoscaling "test-consumer-hpa" not found
Charless-MacBook-Pro:autoscaling charlesparasa$ kubectl describe hpa test-consumer-hpa  -n <>
Name:                                           test-consumer-hpa
Namespace:                                      dragonfruit
Labels:
Annotations:                                    kubectl.kubernetes.io/last-applied-configuration:
{"apiVersion":"autoscaling/v2beta1","kind":"HorizontalPodAutoscaler","metadata":{"annotations":{},"name":"test-consumer-hpa","namespace":"...
CreationTimestamp:                              Thu, 06 Aug 2020 15:12:29 +0530
Reference:                                      Deployment/test-consumer
Metrics:                                        ( current / target )
"Test_ReadyPool_Total_Num_Messages" on pods:   / 1
Min replicas:                                   2
Max replicas:                                   15
Deployment pods:                                2 current / 0 desired
Conditions:
Type           Status  Reason               Message

AbleToScale    True    SucceededGetScale    the HPA controller was able to get the target's current scale
ScalingActive  False   FailedGetPodsMetric  the HPA was unable to compute the replica count: unable to get metric Test_ReadyPool_Total_Num_Messages: no metrics returned from custom metrics API
Events:
Type     Reason                        Age   From                       Message

Warning  FailedGetPodsMetric           10s   horizontal-pod-autoscaler  unable to get metric Test_ReadyPool_Total_Num_Messages: no metrics returned from custom metrics API
Warning  FailedComputeMetricsReplicas  10s   horizontal-pod-autoscaler  invalid metrics (1 invalid out of 1), first error is: failed to get pods metric value: unable to get metric Test_ReadyPool_Total_Num_Messages: no metrics returned from custom metrics API
Any quick Help would be appreciated

FYI, This got fixed using this config-
    - metricsQuery: sum by (kubernetes_pod_name) (hydra:api_latency_seconds:avg)       name:         as: hydra_server_api_latency         matches: ^.*       resources:         overrides:           kubernetes_namespace:             resource: namespace           kubernetes_pod_name:             resource: pod       seriesQuery: hydra:api_latency_seconds:avg{kubernetes_pod_name!=""}
hydra:api_latency_seconds:avg is a recording for-
(avg by (kubernetes_pod_name) (hydra_server_semaphore_latency_second_sum{app="agent-gateway-api"})) / (avg by (kubernetes_pod_name) (hydra_server_semaphore_latency_second_count{app="agent-gateway-api"}))


How to paste specified data in element?

For now I have to deal with the real clipboard, and focus on it and execCommand('paste')
Here is my weird code: https://github.com/fritx/wxbot/blob/dev/preload.js#L233-L254
Is there any way to paste data directly? Thanks!

You can probably call webContents.paste, or send a fake paste event to the DOM element directly.

webContents.paste still has to work with the real clipboard
I've also tried dispatch a fake paste event but it wouldn't truly paste things accroding to http://www.w3.org/TR/clipboard-apis/#clipboard-event-interfaces

What I need is to emulate a user paste behavior, is it possible?

I'm afraid the only way to do that is to access the real clipboard, even Chromium's tests also do so:
https://code.google.com/p/chromium/codesearch#chromium/src/third_party/WebKit/LayoutTests/editing/pasteboard/data-transfer-items.html

Oh I see! What a pity.. Thanks for your time!
I should probably keep that code...


It cannot parse files where we have parenthesis in the imports

Example from one of my projects:
from nes_ai.ai.genome import (
    Activation,
    ConnectionGene,
    InnovationCollection,
    NodeGene,
    TypeNodeGene,
)

I am getting:

Parenthesis is not closed.
Error while parsing the file!

That's because of the limitation of Regex (The project based on regex), this issue will be solved after using the Python AST approach.
I'll work on it as soon as possible, Thank you for the feedback.

Nice, thanks for the module. :)


shaderObject: Disable GPL on some drivers

Some drivers fail a lot of CTS tests with GPL enabled, disable using it until it is resolved

CI Vulkan-ExtensionLayer build queued with queue ID 7031.

CI Vulkan-ExtensionLayer build # 510 passed.


Upgraded Dagger from 2.9 to 2.11 to fix Glide/javapoet issue

Upgraded Dagger from 2.9 to 2.11 to fix Glide/javapoet issue that was discussed in #155

Is that better? or do you want me to do another PR? I apologize, this is my first PR :sweat_smile:

Nope, looks all good to me, thanks for the PR! 🚀


Cannot build harmoni_w2l

When I tried to build the docker-compose-harmoni (not dev), I got the following error:
ImportError: No module named 'setuptools'
Command "python setup.py egg_info" failed with error code 1 in /tmp/pip-build-hvmdev3f/numpy/
You are using pip version 8.1.1, however version 20.1.1 is available.
You should consider upgrading via the 'pip install --upgrade pip' command.
ERROR: Service 'harmoni_w2l' failed to build

Fixed in #14


Error with endpoints with Brother QL-700 usb printer

Hi,
I added the source from this project to my device, made sure the PID was correct, and plugged in the printer. I get the following error when trying to print the test page. Any ideas on how to troubleshoot. (I am a newbie as far as the Imp05 USB device goes).
thanks.

2018-02-12 16:23:39 -08:00
[Device]
USB Connect

2018-02-12 16:23:39 -08:00
[Device]
QL720NWUartUsbDriver was connected!

2018-02-12 16:24:37 -08:00
[Device]
QL720NWUartUsbDriver disconnected

2018-02-12 16:24:37 -08:00
[Device]
ERROR: endpoint must have been opened in usb.generaltransfer(address, endpoint, type, data)

2018-02-12 16:24:37 -08:00
[Device]
ERROR:   in unknown :4294967295

2018-02-12 16:24:37 -08:00
[Device]
ERROR:   from _popBulkTransferQueue ...icimp#usb.device.lib.nut#0.1.0:408

2018-02-12 16:24:37 -08:00
[Device]
ERROR:   from _onTransferCompleted ...icimp#usb.device.lib.nut#0.1.0:377

2018-02-12 16:24:37 -08:00
[Device]
ERROR:   from _onEvent ...icimp#usb.device.lib.nut#0.1.0:422

2018-02-12 16:24:37 -08:00
[Device]
ERROR: endpoint must have been opened in usb.generaltransfer(address, endpoint, type, data)

2018-02-12 16:24:37 -08:00
[Device]
ERROR:   in _popBulkTransferQueue ...icimp#usb.device.lib.nut#0.1.0:408

2018-02-12 16:24:37 -08:00
[Device]
ERROR:   from _onTransferCompleted ...icimp#usb.device.lib.nut#0.1.0:377

2018-02-12 16:24:37 -08:00
[Device]
ERROR:   from _onEvent ...icimp#usb.device.lib.nut#0.1.0:422

Moved on some - enabled _DEBUG on UsbHost
Endpoints are not opened (was using wrong PID). Nothing is printed though.

OK. It is now running thought the print code but nothing comes out on the printer. No apparent errors.

Code:
switch (typeof device) {
case "QL720NWUartUsbDriver":
// Initialize Printer Driver with USB UART device
printer <- QL720NW(device);
        // Print a text label
        printer
            .setOrientation(QL720NW.LANDSCAPE)
            .setFont(QL720NW.FONT_SAN_DIEGO)
            .setFontSize(QL720NW.FONT_SIZE_48)
            .write("San Diego 48 ")
            .print();

        // Configure Barcode
        barcodeConfig <- {
            "type": QL720NW.BARCODE_CODE39,
            "charsBelowBarcode": true,
            "width": QL720NW.BARCODE_WIDTH_M,
            "height": 1,
            "ratio": QL720NW.BARCODE_RATIO_3_1
        }

        // Print bacode of the imp's mac address
        printer.writeBarcode(imp.getmacaddress(), barcodeConfig).print();


Dry run - missing semicolons in some some cases

IMO I'd be useful if --dry-run option generated working SQL script. I does not for now - I've noticed missing semicolons after:

START TRANSACTION
COMMIT
ALTER TABLE

Are you able to make a PR with the suggested changes?

I'm not sure, but I'll try to figure out the solution when I'll have some free time. :)

PR open


Lack of code style convention

Currently, the DepClean codebase lacks proper code style conventions. This makes the codebase messy and is overall bad for maintainability. The best way to mitigate this is by enforcing the use of strict code style rules.
Checkstyle is currently one of the best tools for this purpose. Configuring Checkstyle in DepClean will help newcomers to have a more clean codebase to work with.

Hey... @cesarsotovalero,
I would like to work on this enhancement, may I?
And if yes then please also suggest to me some documentation of this repo, because if we use checkstyle for code style conventions then we have to also write incode short documentation of every method, class, and interface. So the documentation will help me a lot in understanding the codebase and also in writing short but effective incode documentation.

Hi @ABHAY0O7, Welcome!

I would like to work on this enhancement, may I?

I've already done it. But you can add documentation and fix Checkstyle warnings.

Ya sure, I am on it.


MAHOUT-1752: Implement CbindScalar operator on H2O

Closes apache/mahout#144
Signed-off-by: Anand Avati<EMAIL_ADDRESS>

Looks good to me.


[ISV-2734] Build tekton bundle out of signing tasks

Here's a successful action triggered from this PR: https://github.com/redhat-openshift-ecosystem/operator-pipelines/actions/runs/3385327380/jobs/5623342543
As per JIRA AC, this should run on merge, so for the actual trigger, I've re-used the one from build-image.yml action.

Switched target to tkn-signing-bundle  and deleted the old repository


Build error: Identifier 'clampValue' has already been declared

Hello @nicolas-cusan,
Nice plugin! I'd like to use it but I encountered a few problems...

Since v2.1.0, there's an error: Identifier 'clampValue' has already been declared, which seems to be caused by this line: https://github.com/nicolas-cusan/tailwind-clamp/blob/v2.2.1/src/index.js#L12
If I rename the export, it works but the values of the clamp are always in px when I was expecting them to be rem (I tried different unit options and nothing seems to change).
Lastly, this might be more of an issue with my build system but I also get errors about tailwindcss/plugin not being found and I have to change it to import plugin from 'tailwindcss/plugin.js';

Thanks for your time!

Hello @hybridvision
Thank you for using the plugin, glad it is useful to you. Regarding your issues:

I pushed a fix in v2.2.2.
This is odd, can you send some code examples of your setup or a codesandox? If you use clampValue in your tailwind.config.js values are converted from px to rem. To use a different unit, you have to pass a unit in the options. If you use a class in your CSS e.g. clamp-[p,4,8] the values 4 and 8 will be looked up in your config, if they are present whatever value and unit they have will be used 1rem and 2rem in this case. If they do not exist in your config, they and the values are just numbers, they will be interpreted as px (as it is the case by default for plain numbers in tailwind.config.js) if you want a different unit you need to pass it in the class e.g: clamp-[p,1.5rem,2.6rem].
Don't know why that could be, I do not have a problem with that, maybe a workaround is to add the unit in the import...

Best regards

Hi Nicolas,
Thank you for the quick fix :)
In reply to your points:

Your fix resolved that particular error, thanks!
I made a little sandbox to test out the plugin and what I was expecting was the generated clamp(...) values to be in rem not px when I use arbitrary values like clamp-[w,150,400] – I mean these as 100px and 400px but I would like the resulting clamp to use rem. Changing the unit in options doesn't seem to do anything.
I don't know why either but there must be some obscure reason in the build configuration (for reference this is in a WordPress environment with the Roots stack and Bud as the build tool via Sage. This is where the JS ecosystem is frustrating because there are so many layers with little bits of magic added but also weird inconsistencies where simple things like imports don't always work. The actual error I get is Cannot find module '/xxxxx/node_modules/tailwindcss/plugin' imported from /xxxxx/node_modules/tailwind-clamp/src/index.js Did you mean to import tailwindcss/plugin.js? – it knows the file is there but for some reason won't work unless the .js extension is added to the import path. 🤯 The problem is that this is within your package, so I can't really fix it without forking your code. At the same time, I'm not sure if this is a problem you should need to fix... Argh!

By the way, I wanted to add some extra thoughts about your plugin:
It's neat that you've given the ability to reference a key in the config but I think this makes it more confusing (at least for me!) and inconsistent because that connection isn't always obvious and there are plenty of properties where the keys won't exist in the config. In other words, I think having 2 = 0.5rem, 4 = 1rem, etc is only really useful when you are using the simple utility classes (eg. p-2, mt-4 etc). In the arbitrary values of clamp-[...], it seems like an unnecessary layer and it would be simpler to assume that unitless numbers are always in pixels. What do you think?
I should also add that I'm using Utopia for font sizing and spacing, so my need for these other clamps is possibly different to yours. I was actually going to make my own simple plugin using utopia-core when I came across yours.
Anyway, thanks for reading!

Hi @hybridvision
To address 2.:
Changing the unit option is only possible when using the clampValue function in your config, see here.
To give you some context: The plugin started out just as you describe, with px to rem conversion and not reading values from the config. But as I developed this for my own needs, I found a lot of value in being able to define regular font sizes with line-height and letter-spacing in my tailwind.config.js and just being able to clamp between two fontSize definitions. Which seems to be something you are not doing, as you use Utopia for that.
By referencing values from the config you also do not have to parallel systems of measurement for spacing p-4 will be more relatable to clamp-[p,4,8] then needing to mentally shift between the regulars spacing scale and pixels when using clamp-[...].
So to answer your question I rather have it this way, which also helps a little with staying consistent
To make my own life easier, I usually customize my config to include all values from 0.5 to 96 in 2px increments:
// tailwind.config.js

const space = () => {
  const s = {};
  for (let idx = 0; idx < 96; idx += 0.5) {
    s[idx] = idx === 0 ? `0` : `${idx * 0.25}rem`;
  }
  return s;
};

// ...

export default {
  // ...
  theme: {
    extend: {
      spacing: {...space()},
  }
  // ...
}

If I need something larger, I will just include the value with the unit.
To address 3.:
I am not familiar with the tools you are using. In any case, importing without the extension seems to be the "official way to do it", see here. Maybe I need to bundle the code for it to work. Maybe I will look into it at some later point.


Roblox Ramdomly Closing

it started to happening in build a boat for a treasure i dont have soo many details sorry

Can I see the list of flags you have configured in the menu?

I can confirm the same happens, Roblox freezes and then a "Roblox has just crashed. We're sorry!" dialog appeared

those are the only default FFlags I modified, I added no custom fflag

This isn't the same issue though, you're being shown a crash dialog. Open a separate issue for this.

Issue has been awaiting clarification for over a month, closing as stale. If you have anything further to add, just respond and I'll reopen.


[Bug] Error: Command failed: cat /sys/class/net/ppp0/speed

Description of the bug
I am running dashdot from source.
After installing, I type in sudo -E yarn start to start it, it show the error
How to reproduce
sudo -E yarn start
Relevant log output
Version file not found. This is normal on from-source builds.
listening on *:3001
Multiple default network interfaces found [ppp0, eth0], using "ppp0"
Using default network interface "ppp0"
Using host os version from "/etc/os-release"
(node:1114655) UnhandledPromiseRejectionWarning: Error: Command failed: cat /sys/class/net/ppp0/speed
cat: /sys/class/net/ppp0/speed: Invalid argument
    at ChildProcess.exithandler (child_process.js:308:12)
    at ChildProcess.emit (events.js:314:20)
    at maybeClose (internal/child_process.js:1022:16)
    at Socket.<anonymous> (internal/child_process.js:444:11)
    at Socket.emit (events.js:314:20)
    at Pipe.<anonymous> (net.js:676:12)
(node:1114655) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1)
(node:1114655) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate
the Node.js process with a non-zero exit code.

Info output of dashdot cli
INFO
=========
Yarn: 3.5.0
Node: v18.15.0
Dash: unknown
Cwd: /home/yanyixuan/dashdot
Hash: c6cb25447599a94fc7955b5ccb680a61d0c97d5e
In Docker: false
In Podman: false
In Docker (env):

What browsers are you seeing the problem on?
Chrome
Where is your instance running?
Raspberry Pi
Additional context
In my browsers it shows

Hi there, can you by any chance post the output of this command:
route | grep '^default' | grep -o '[^ ]*$'

or
ip route get <IP_ADDRESS> | sed -n 's/.*dev \([^\ ]*\).*/\1/p'

If that doesn't work, please have a look at this StackExchange post for another method of finding out your main network interface.
What I suspect is that ppp0 is not your actual network interface and there is some weirdness happening.

yanyixuan@raspberrypi:~ $ route | grep '^default' | grep -o '[^ ]*$'
ppp0
eth0
yanyixuan@raspberrypi:~ $ ip route get <IP_ADDRESS> | sed -n 's/.*dev \([^\ ]*\).*/\1/p'
ppp0

So I just pushed a new version on the dev branch, could you please try that out?
docker image pull mauricenino/dashdot:dev
docker container run -it --rm --privileged -v /:/mnt/host:ro -p 3002:3001 mauricenino/dashdot:dev

@SuimgPhilip You are having similar issues, so could you please also try out that solution?

Thank you!
It can run now.

@SuimgPhilip You are having similar issues, so could you please also try out that solution?

The problem is solved


pkg/obfuscate: set an error in the tokenizer when we fail to parse a number

scanNumber failed to set an error in the tokenizer when it returned
LexError, resulting in nil error messages. This commit causes scanNumber
to set an error message in the tokenizer as soon as it encounters an error
rather than relying on the caller to do so.
Describe how to test/QA your changes
Manually tested

I'll add a regression testcase for this.


How to unzip your training pairs?

How to unzip your training pairs?

How to unzip your training pairs?

If you download from GoogleDrive, you can directly 'unzip' it. The zip files in BaiduDrive is seperated to several smaller zip files since uploading size limit.
1） for GoogleDrive: unzip xxx.zip
2)  for BaiduDrive:  cat SiamDW_DATA.zip* > SiamDW_DATA.zip && unzip SiamDW_DATA.zip

This issue will be closed since long-term no reply.


help(dev-app): yarn dev-app gives SASSCompiler error on windows

What are you trying to do?
I am trying to run dev-app on latest version of master branch
What troubleshooting steps have you tried?
I am trying to run dev-app application,by using yarn dev-app and it gives me the following errror
ERROR: C:/projects/components/src/dev-app/BUILD.bazel:162:1 SassCompiler src/material/grid-list/grid-list.css failed: Worker process did not return a WorkResponse:

---8<---8<--- Start of log, file at C:/users/onika/_bazel_onika/mitqcfzm/bazel-workers/worker-29-SassCompiler.log ---8<---8<---
'""' is not recognized as an internal or external command,
operable program or batch file.
---8<---8<--- End of log ---8<---8<---
INFO: Elapsed time: 8.108s, Critical Path: 0.53s
INFO: 0 processes.
FAILED: Build did NOT complete successfully
ERROR: Build failed. Not running target
FAILED: Build did NOT complete successfully
iBazel [6:42PM]: Error starting process: fork/exec C:\Users\onika\AppData\Local\Temp\bazel_script_path345870083.bat: %1 is not a valid Win32 application.
iBazel [6:42PM]: Run start failed fork/exec C:\Users\onika\AppData\Local\Temp\bazel_script_path345870083.bat: %1 is not a valid Win32 application.
iBazel [6:42PM]: Error reading config: open .bazel_fix_commands.json: The system cannot find the file specified.

Reproduction
there is no way I can reproduce it either stackblitz,or anywhere else, because it's framework issue
Steps to reproduce:

yarn
yarn dev-app

Environment

Angular: ^9.1.0-next.4
CDK/Material: 9.2.0-next.0
Browser(s): none
Operating System (e.g. Windows, macOS, Ubuntu):  Windows 10 Enterprise

I've been running master all day without any issues on Windows, but I have seen that error before. I've had it happen when Bazel didn't like some characters in the output path (in my case it was some whitespace).

Hello! I'm running Bazel on Windows too, but haven't seen that in a while. This usually happens when the cloned project path contains spaces (which isn't the case here as it looks), or if the BAZEL_SH environment variable is explicitly set (this variable is not needed anymore).
I'm happy to help. Is this is still an issue for you? Closing in the meanwhile as I don't believe this is an upstream issue on our end. This seems like a client issue with how Bazel launches arbitrary binaries.


Incompatibilidad con bacon/bacon-qr-code versión 3.0.0

Please check these requirements

[X] This feature helps everyone using this package
[X] It's feasible and maintainable
[X] It's non breaking
[ ] I issued a PR with the implementation (optional)

Description
Podrían considerar actualizar el paquete laragear/two-factor para ser compatible con la versión 3.0.0 de bacon/bacon-qr-code. Actualmente, laragear/two-factor requiere la versión 2.x de bacon/bacon-qr-code, lo cual genera incompatibilidades con otras dependencias en proyectos que ya utilizan la versión 3.0.0.
Esta actualización ayudaría a evitar conflictos y permitiría una mayor flexibilidad al integrarlo en proyectos existentes.
Code sample
./composer.json has been updated
Running composer update laragear/two-factor
Loading composer repositories with package information
Updating dependencies
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - laragear/two-factor[v1.0.0, ..., v1.2.0] require bacon/bacon-qr-code ^2.0 -> found bacon/bacon-qr-code[2.0.0, ..., 2.0.8] but the package is fixed to v3.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - laragear/two-factor[v1.2.1, ..., v1.3.0, v2.0.0, ..., v2.0.1] require bacon/bacon-qr-code 2.* -> found bacon/bacon-qr-code[2.0.0, ..., 2.0.8] but the package is fixed to v3.0.0 (lock file version) by a partial update and that version does not match. Make sure you list it as an argument for the update command.
    - Root composer.json requires laragear/two-factor * -> satisfiable by laragear/two-factor[v1.0.0, ..., v1.3.0, v2.0.0, v2.0.1].

Use the option --with-all-dependencies (-W) to allow upgrades, downgrades and removals for packages currently locked to specific versions.
You can also try re-running composer require with an explicit version constraint, e.g. "composer require laragear/two-factor:*" to figure out if any version is installable, or "composer require laragear/two-factor:^2.1" if you know which you need.

Installation failed, reverting ./composer.json and ./composer.lock to their original content.
PS /home/carlos-daniel/Herd/laravel/test-jetstream>

#85


method might not refer to a location within buffer

Our app parses a request but doesn't need to do anything with it until the body is also received. In order to allow the underlying buffer to be used for reading the body, and also to avoid parsing the request twice, the app converts the various slices (method, path, headers) into integer indexes within the underlying buffer and then drops the Request in order to unborrow the buffer. Later on, the slices can be reestablished using the indexes.
As of httparse 1.8, our app started failing due to slice locations potentially existing outside of the buffer, likely due to "GET" and "POST" now being returned as static strings.
In hindsight I suppose we were abusing the API. httparse never guaranteed the slices would always point within the buffer. It was just an easy assumption to make since httparse is known to do in-place parsing without copying. I'm not sure if anything should be changed in httparse and we will look at reworking our code. Posting this in case anyone else ran into the same issue.

Following up on this. I came up with three possible solutions:

Parse the request twice, once before reading the body and once after. This is likely the simplest approach.

Keep doing the slice->index conversion thing we were doing, but take into account that a slice might not be in the buffer. Each tracked field could be an enum, something like enum FieldRef { RangeInBuf(u32, u32), Slice(&'static str) }. This is likely the closest solution to what we were already doing.

Use a different buffer for subsequent reads. After parsing the request, copy any remaining bytes into a second buffer, and then start using that second buffer for reading the body. The original buffer stays borrowed by the Request. Further, when it's time to read the next request, read it from the second buffer. This is likely the most optimal solution, if there happens to be an unused buffer lying around. In our case we did have this: an idle write buffer.

I ended up going with the last approach. For each connection we were allocating two Vec<u8> buffers, one for reading and one for writing, but the write buffer was not used at all during the reading process and so it was available. The implementation was a bit tricky, with the buffers switching places for each request, but it seems to work.

@jkarneges I'll fix this for the next release, my fault, it makes sense to return buffer pointers instead of static strings.


Migration doesn't properly handle calls from one extension to another via implicit this

As of 5569f10236f522e62adea480c1de4de244074359, the following code is handled improperly by null safety migration:
extension on int {
  foo() => bar();
}
extension on num {
  bar() => 0;
}
f(int i, bool b) {
  if (b) {
    print(i.foo());
  }
}
g() => f(null, false);

It should be migrated to:
extension on int? {
  foo() => bar();
}
extension on num? {
  bar() => 0;
}
f(int? i, bool b) {
  if (b) {
    print(i.foo());
  }
}
g() => f(null, false);

But instead it is migrated to:
extension on int? {
  foo() => bar();
}
extension on num {
  bar() => 0;
}
f(int? i, bool b) {
  if (b) {
    print(i.foo());
  }
}
g() => f(null, false);

(It's missing the ? on extension on num).
The reason this is happening is that when analyzing foo() => bar();, the migration engine's edge builder fails to understand that bar is referring to an extension method, so it fails to introduce a dependency between the nullability of the two extensions' extended typs.
If the reference from foo to bar is via explicit this (i.e. foo() => this.bar();) the problem does not occur.
There are similar problems when invoking property getters and setters rather than methods.
I suspect this kind of code is really rare, and it hasn't cropped up for any users that I know of, so I'm initially classifying this as a P3.

As of 1c7fe7196dd7a542f7f91cd6ea2ac81e1a13146c, the null safety migration tool has been removed from active development and retired. No further work on the tool is planned.
If you still need help, or you believe this issue has been closed in error, please feel free to reopen.


Gauntlet toolbar zooms in

Gauntlet toolbar removes options when I zoom the editor view. I want to control which options are removed or (preferably) keep the toolbar from zooming at all.

I think the is actually an issue for the gauntlet team either:

a feature request
looking at a new way to layout/offer up the controls.

I can connect you with that team via email.
Sean


Outline - Ability to hide inner content of functions (variables and etc.)

Did it already plan to add flag in settings for showing just one level of nesting in outline?

yes

/duplicate of #53034


Not able to build lodestar on contabo vpss

Describe the bug
Got this error when building lodestar from source
yarn install v1.22.19
[1/5] Validating package.json...
[2/5] Resolving packages...
[3/5] Fetching packages...
[4/5] Linking dependencies...
warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning " ><EMAIL_ADDRESS>has unmet peer dependency<EMAIL_ADDRESS>warning "workspace-aggregator-a358551c-f04b-4ee5-a2f7-b59dd384aef0 > @lodestar/beacon-node ><EMAIL_ADDRESS>has unmet peer dependency "<EMAIL_ADDRESS>warning "workspace-aggregator-a358551c-f04b-4ee5-a2f7-b59dd384aef0 > @lodestar/beacon-node ><EMAIL_ADDRESS>has incorrect peer dependency "prom-client@>= 10 <= 12".
warning "workspace-aggregator-a358551c-f04b-4ee5-a2f7-b59dd384aef0 > @lodestar/beacon-node > @multiformats/multiaddr > dns-over-http-resolver ><EMAIL_ADDRESS>has unmet peer dependency "undici@*".
[5/5] Building fresh packages...
[11/18] ⠄ @chainsafe/blst
[2/18] ⠄ electron
[7/18] ⠄ bcrypto
[9/18] ⠄ snappy
error /usr/src/lodestar/node_modules/@chainsafe/blst: Command failed.
Exit code: 1
Command: node dist/scripts/install.js
Arguments:
Directory: /usr/src/lodestar/node_modules/@chainsafe/blst
Output:
node:internal/modules/cjs/loader:1243
  return process.dlopen(module, path.toNamespacedPath(filename));
                 ^

Error: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by<EMAIL_ADDRESS>    at Module._extensions..node (node:internal/modules/cjs/loader:1243:18)
    at Module.load (node:internal/modules/cjs/loader:1037:32)
    at Module._load (node:internal/modules/cjs/loader:878:12)
    at Module.require (node:internal/modules/cjs/loader:1061:19)
    at require (node:internal/modules/cjs/helpers:103:18)
    at [eval]:1:1
    at Script.runInThisContext (node:vm:129:12)
    at Object.runInThisContext (node:vm:313:38)
    at node:internal/process/execution:79:19
    at [eval]-wrapper:6:22 {
  code: 'ERR_DLOPEN_FAILED'
}

Node.js v18.12.1
Cached BLST native bindings not OK
Retrieving BLST native bindings<EMAIL_ADDRESS>...
node:internal/modules/cjs/loader:1243
  return process.dlopen(module, path.toNamespacedPath(filename));
                 ^

Error: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by<EMAIL_ADDRESS>    at Module._extensions..node (node:internal/modules/cjs/loader:1243:18)
    at Module.load (node:internal/modules/cjs/loader:1037:32)
    at Module._load (node:internal/modules/cjs/loader:878:12)
    at Module.require (node:internal/modules/cjs/loader:1061:19)
    at require (node:internal/modules/cjs/helpers:103:18)
    at [eval]:1:1
    at Script.runInThisContext (node:vm:129:12)
    at Object.runInThisContext (node:vm:313:38)
    at node:internal/process/execution:79:19
    at [eval]-wrapper:6:22 {
  code: 'ERR_DLOPEN_FAILED'
}

Node.js v18.12.1
Error: Error importing BLST native bindings: Command failed: node -e 'require("/usr/src/lodestar/node_modules/@chainsafe/blst/prebuild/linux-x64-108-binding.node")'
node:internal/modules/cjs/loader:1243
  return process.dlopen(module, path.toNamespacedPath(filename));
                 ^

Error: /lib/x86_64-linux-gnu/libc.so.6: version `GLIBC_2.32' not found (required by<EMAIL_ADDRESS>    at Module._extensions..node (node:internal/modules/cjs/loader:1243:18)
    at Module.load (node:internal/modules/cjs/loader:1037:32)
    at Module._load (node:internal/modules/cjs/loader:878:12)
    at Module.require (node:internal/modules/cjs/loader:1061:19)
    at require (node:internal/modules/cjs/helpers:103:18)
    at [eval]:1:1
    at Script.runInThisContext (node:vm:129:12)
    at Object.runInThisContext (node:vm:313:38)
    at node:internal/process/execution:79:19
    at [eval]-wrapper:6:22 {
  code: 'ERR_DLOPEN_FAILED'
}

Node.js v18.12.1

    at checkExecSyncError (node:child_process:871:11)
    at Object.execSync (node:child_process:943:15)
    at Object.testBindings (/usr/src/lodestar/node_modules/@chainsafe/blst/dist/scripts/testBindings.js:8:21)
    at Object.downloadBindings (/usr/src/lodestar/node_modules/@chainsafe/blst/dist/scripts/downloadBindings.js:11:26)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async install (/usr/src/lodestar/node_modules/@chainsafe/blst/dist/scripts/install.js:34:9) {
  status: 1,
  signal: null,
  output: [
    null,
    <Buffer >,
    <Buffer 6e 6f 64 65 3a 69 6e 74 65 72 6e 61 6c 2f 6d 6f 64 75 6c 65 73 2f 63 6a 73 2f 6c 6f 61 64 65 72 3a 31 32 34 33 0a 20 20 72 65 74 75 72 6e 20 70 72 6f ... 800 more bytes>
  ],
  pid: 2164487,
  stdout: <Buffer >,
  stderr: <Buffer 6e 6f 64 65 3a 69 6e 74 65 72 6e 61 6c 2f 6d 6f 64 75 6c 65 73 2f 63 6a 73 2f 6c 6f 61 64 65 72 3a 31 32 34 33 0a 20 20 72 65 74 75 72 6e 20 70 72 6f ... 800 more bytes>
}
Building BLST native bindings<EMAIL_ADDRESS>from source...
BLST_WRAP_CPP_PREBUILD<EMAIL_ADDRESS>exists, SWIG will be skipped
Launching node-gyp {
  nodeJsExec: '/home/devops/.nvm/versions/node/v18.12.1/bin/node',
  nodeGypExec<EMAIL_ADDRESS>  cwd<EMAIL_ADDRESS>  BLST_WRAP_CPP_PREBUILD<EMAIL_ADDRESS>}
gyp info it worked if it ends with ok
gyp info using<EMAIL_ADDRESS>gyp info using<EMAIL_ADDRESS>| linux | x64
gyp info find Python using Python version 3.8.10 found at "/usr/bin/python3"
gyp info spawn /usr/bin/python3
gyp info spawn args [
gyp info spawn args<EMAIL_ADDRESS>gyp info spawn args   'binding.gyp',
gyp info spawn args   '-f',
gyp info spawn args   'make',
gyp info spawn args   '-I',
gyp info spawn args<EMAIL_ADDRESS>gyp info spawn args   '-I',
gyp info spawn args<EMAIL_ADDRESS>gyp info spawn args   '-I',
gyp info spawn args   '/home/devops/.cache/node-gyp/18.12.1/include/node/common.gypi',
gyp info spawn args   '-Dlibrary=shared_library',
gyp info spawn args   '-Dvisibility=default',
gyp info spawn args   '-Dnode_root_dir=/home/devops/.cache/node-gyp/18.12.1',
gyp info spawn args   '-Dnode_gyp_dir=/usr/src/lodestar/node_modules/@chainsafe/blst/node_modules/node-gyp',
gyp info spawn args   '-Dnode_lib_file=/home/devops/.cache/node-gyp/18.12.1/<(target_arch)/node.lib',
gyp info spawn args<EMAIL_ADDRESS>gyp info spawn args   '-Dnode_engine=v8',
gyp info spawn args   '--depth=.',
gyp info spawn args   '--no-parallel',
gyp info spawn args   '--generator-output',
gyp info spawn args   'build',
gyp info spawn args   '-Goutput_dir=.'
gyp info spawn args ]
gyp info spawn make
gyp info spawn args [ 'BUILDTYPE=Release', '-C', 'build' ]
make: Entering directory<EMAIL_ADDRESS>  ACTION binding_gyp_blst_target_blst_wrap Release/obj.target/blst/geni/blst_wrap.cpp
/bin/sh: 1: python: not found
make: *** [blst.target.mk:13: Release/obj.target/blst/geni/blst_wrap.cpp] Error 127
gyp ERR! build error
gyp ERR! stack Error: `make` failed with exit code: 2
gyp ERR! stack     at ChildProcess.onExit (/usr/src/lodestar/node_modules/@chainsafe/blst/node_modules/node-gyp/lib/build.js:194:23)
gyp ERR! stack     at ChildProcess.emit (node:events:513:28)
gyp ERR! stack     at ChildProcess._handle.onexit (node:internal/child_process:291:12)
gyp ERR!  System Linux 5.4.0-62-generic
gyp ERR! command "/home/devops/.nvm/versions/node/v18.12.1/bin/node"<EMAIL_ADDRESS>"rebuild"
gyp ERR! cwd<EMAIL_ADDRESS>gyp ERR! node -v v18.12.1
gyp ERR! node-gyp -v v8.4.1
gyp ERR! not ok

    at ChildProcess.exithandler (node:child_process:412:12)
    at ChildProcess.emit (node:events:513:28)
    at maybeClose (node:internal/child_process:1091:16)
    at ChildProcess._handle.onexit (node:internal/child_process:302:5) {
  code: 1,
  killed: false,
  signal: null,
  cmd: '/home/devops/.nvm/versions/node/v18.12.1/bin/node<EMAIL_ADDRESS>rebuild'
}
Error: Error downloading and building BLST native bindings /usr/src/lodestar/node_modules/@chainsafe/blst/prebuild/lin

Expected behavior
No error

OS: Ubuntu 20.04.3 LTS
Branch: unstable
Commit hash: c274d22

This issue does not always happen on contabo vpss machines.
The error is version GLIBC_2.32' not found`:
ldd --version
ldd (Ubuntu GLIBC 2.31-0ubuntu9.2) 2.31
Copyright (C) 2020 Free Software Foundation, Inc.
This is free software; see the source for copying conditions.  There is NO
warranty; not even for MERCHANTABILITY or FITNESS FOR A PARTICULAR PURPOSE.
Written by Roland McGrath and Ulrich Drepper.

but other success nodes have same GLIBC (2.31) version

Maybe those contabo VPSS are running an old version of linux?

Maybe those contabo VPSS are running an old version of linux?

@dapplion  no, it's ubuntu 20.04.3, some other nodes with same OS worked

there's an issue with @chainsafe/blst 0.2.7

lodestar v1.2.x uses @chainsafe/blst 0.2.4 and it works fine
lodestar v1.3.x uses @chainsafe/blst 0.2.7 and it has build error

it works well if I use v1.3.x with @chainsafe/blst 0.2.6, it seems that when releasing blst we always go with latest ubuntu and it make it incompatible for not-upgraded machines
see https://github.com/ChainSafe/blst-ts/actions/runs/3706833809/jobs/6285801787
Ubuntu
  22.0[4](https://github.com/ChainSafe/blst-ts/actions/runs/3706833809/jobs/6285801787#step:1:4).1
  LTS

not able to get github action log of v0.2.6 https://github.com/ChainSafe/blst-ts/actions/runs/3001398317/jobs/4817458661 since it's expired

Then the pre-built files should be tagged better to ensure are built for the correct environment

found the difference between v20 ubuntu nodes

Nodes work with blst v0.2.7 has Intel cpu (this does not require any blst installations)

Vendor ID:                       GenuineIntel
CPU family:                      6
Model:                           79
Model name:                      Intel(R) Xeon(R) CPU E5-2640 v4 @ 2.40GHz

Nodes does not work with blst v0.2.7 and require some failed blst installations has AMD cpu

Vendor ID:                       AuthenticAMD
CPU family:                      23
Model:                           49
Model name:                      AMD EPYC 7282 16-Core Processor

also not sure if it's related to https://github.com/ChainSafe/blst-ts/issues/77

blst-ts v0.2.7 has prebuilds up to modules version 108 = linux-x64-108-binding.node, while v0.2.4 has up to modules version 102
linux-x64-102-binding.node. That means that using v0.2.4 with an older NodeJS version will always trigger a new build.
You can check which modules version is used by each node version with
$ node -e "console.log(process.version, process.versions.modules)"
v18.12.1 108

@dapplion v0.2.6 has prebuilds up to modules version 108 too and it works fine

on the error node, it failed to testBinding (with child process execSync, the difference between v0.2.6 and v0.2.7), that's why it did an installation
Node.js v18.12.1
Cached BLST native bindings not OK
Retrieving BLST native bindings<EMAIL_ADDRESS>...
node:internal/modules/cjs/loader:1243
  return process.dlopen(module, path.toNamespacedPath(filename));
                 ^

on the successfully node, if I run the install script, it's a success so no need to do the installation
node scripts/install.js
Using existing BLST native bindings from<EMAIL_ADDRESS>
this really links to the child process invocation we added to v0.2.7 https://github.com/ChainSafe/blst-ts/pull/76

could be fixed by https://github.com/ChainSafe/blst-ts/pull/79

@dapplion v0.2.6 has prebuilds up to modules version 108 too and it works fine

Does this include arm64 devices? I remember trying to build v0.2.6 on an arm64 device and was still getting the SIGSEGV exit signal, which is why https://github.com/ChainSafe/blst-ts/pull/76 was made.

@philknows v0.2.8 is same to v0.2.7 but we use ubuntu 20.04 instead of ubuntu 22.04 to generate binding files


Recommendation 3.9: enum values are separated by comma and a line break. ';' is put on the new line

Recommendation 3.9: enum values are separated by comma and a line break. ';' is put on the new line

Enum values are separated by comma and a line break. ';' is put on the new line:

   enum class Warnings {
       A,
       B,
       C
       ;
   }

This will help to resolve conflicts and reduce it's number during merging pull requests.

In case enum is simple (it has no properties, no methods and no comments inside) - it can be declared in a single line:

enum class Suit { CLUBS, HEARTS, SPADES, DIAMONDS }

Prefer enum classes if it is possible, for example instead of 2 Boolean properties like: val isCelsius = true | val isFahrenheit = false use enum class:

enum class TemperatureScale { CELSIUS, FAHRENHEIT }

The variable value only changes within a fixed range and is defined with the enum type. For example, Recommend 8.6.3 Keyboard example
Avoid comparison with magic constant numbers of -1, 0, and 1, instead of this use enums:
  enum class ComparisonResult {
      ORDERED_ASCENDING,
      ORDERED_SAME,
      ORDERED_DESCENDING
      ;
  }

Duplicate of #153


UniswapV2Factory full test

Time spent on this PR: 0.5
Pull request type
Please check the type of change your PR introduces:

[ ] Bugfix
[x] Feature
[ ] Code style update (formatting, renaming)
[ ] Refactoring (no functional changes, no api changes)
[ ] Build related changes
[ ] Documentation content changes
[ ] Other (please describe):

What is the current behavior?
Token addresses are random instead the same one as in the original test.
Test using createPair is skipped
Resolves #467
What is the new behavior?
All tests pass as in the original file

Nvm I didn't notice tests were failing

It took me quite a lot of time to understand what was the issue. Actually the ExecutionContext.is_root and ExecutionContext.is_leaf (note: I wrote them myself two months ago) were not checking that a given true context was root or leaf ; it was working only on the dummy empty_ctx.
These methods are not tested (!) and actually is_root was used only once with
is_parent_root = ExecutionContext.is_root(ctx.calling_context);

which was quite misleading imao against past me. Consequently I've updated these helpers to be usable on the actual current execution context. For now, I've just considered that checking against an empty evm_contract_address was enough, wdyt?

Are we still maintaining kakarot.execute?
It looked to me as though we were slowly deprecating kakarot.execute in favor of kakarot.execute_at_address


Error in installation docs

Hi Everybody,
just a brief issue descritpion.
The readme explains that Flet-Box can be installed with:
>>> source .venv/bin/activate
>>> pip install flet
>>> pip install https://github.com/xavier53348/Flet-Box.git

Unfortunately this will fail due to an error inside the pip install command.
It will work if you use the follwing commands instead:
>>> source .venv/bin/activate
>>> pip install flet
>>> pip install git+https://github.com/xavier53348/Flet-Box.git

...but this isn't however installing flex-box properly I guess because I was still not able to start it with flet ./src/flet_box.py as there was no folder src in my working folder. I had to download (or clone) the repo and copy the complete src folder to my working folder. After doing this flet-box was starting up. Please consider to update/correct your installation instructions.
HTH
regards
Chris

Hello dev I have some errors in my computer creating pip package download manually now with git clone I have to resolve that situation today I upgrade I on beta yet but I'm adding new this


Evolution of registries

New Infographic is required.

Arka has shared the infographics but that needs some changes..

Pending for Review


OAK-4101 Consider separate external (group) principal management

I created this pull request in order to be able to discuss the proposed patch in https://issues.apache.org/jira/browse/OAK-4101. I'm not the original author.

closing due to inactivity.


DO NOT MERGE: Working branch for SDM/CDK consolidation

Replaced by:

https://github.com/airbytehq/airbyte-python-cdk/pull/58

Closing as replaced by https://github.com/airbytehq/airbyte-python-cdk/pull/58


Track spring-boot compatible versions about azure-sdk-for-java and spring-cloud-azure.

Version mapping between spring-boot and azure-sdk-for-java

Now there is a wiki page to track version mapping between spring-boot and spring-cloud-azure:
https://github.com/Azure/azure-sdk-for-java/wiki/Spring-Versions-Mapping
But there isn't a wiki page to track version mapping between spring-boot and azure-sdk-for-java.
We should maintain that mapping.

Single truth of version mapping.
We should put the mapping in one place(for example, github wiki), and add link in MS docs and reference doc.

Hi, @JonathanGiles ,
How about using same version for all azure-sdk-for-java libraries? Just Like Spring-Cloud-Azure:4.0.0.
If it's OK to use same versioon, the azure-sdk-bom should use that version, too. (cc: @pallavit FYI)
Furthermore, how about using same version for all azure-sdk-for-java libraries and Spring-Cloud-Azure libraries.
Just like some spring projects(spring-framework, spring-security), all artifacts in one repository share the same version.
It will be convenient for our customer if we do like this.

There are too many libraries that have existed for years to find any suitable way to align versions. Storage is at version 12 and application config is at version 1. Should we move everything to major version 13? Probably not. What about when releases happen out of band due to critical issues, etc? Does everything need to do a revision release? What if we need to do a major release of a certain library - do we do major releases of all libraries even if they have no major changes?
There are a bunch of issues with aligning versions, so for that reason our preferred strategy is to have our BOM be responsible for handling the matching of compatible versions of each library, and have our users simply defer to the BOM for choosing the relevant version for each dependency they require.

@JonathanGiles Thank you for your detailed explanation.
But similar issues also exist in spring-framework repository.
Since spring-framework can use the uniform version, we can accept the same solution.
About the issues you metioned:

Storage is at version 12 and application config is at version 1. Should we move everything to major version 13?

Version 13 is OK.

What about when releases happen out of band due to critical issues, etc? Does everything need to do a revision release?

Yes, release for every artifact in this repo. I think for spring-framework, not every library has updates in every patch release.

What if we need to do a major release of a certain library - do we do major releases of all libraries even if they have no major changes?

Yes, do major release for all libraries, just like spring-framework did. For every major release, not every spring-framework library have major changes, I think.

have our BOM be responsible for handling the matching of compatible versions of each library

Yes, use BOM is one solution. But use uniform version is a better solution. So the customer can use the concept of the version of azure-sdk-for-java. When customer use artifact like azure-security-keyvault-secrets and azure-data-appconfiguration, if they use the same version, our customer can know that the 2 artifacts can work together without any problem.
This problem not only exist in our repo, a lot of other repos have similar problem. Most of them choose the uniform version. Like spring-framework, spring-security. These repositories also have a lot of libraries.

@JonathanGiles . Got it. Thank you.

@chenrujun  - I don't think should be closed. The document created does not do a sufficient job of providing a mapping of versions that should be used. https://start.spring.io/actuator/info should be used for inspiration as to what is sufficient. I am specifically talking about how the Spring team provides version mapping for things like Spring Cloud:
"spring-cloud": {
"Hoxton.SR12": "Spring Boot >=2.2.0.RELEASE and <2.4.0.M1",
"2020.0.5": "Spring Boot >=2.4.0.M1 and <2.6.0-M1",
"2021.0.0-M1": "Spring Boot >=2.6.0-M1 and <2.6.0-M3",
"2021.0.0-M3": "Spring Boot >=2.6.0-M3 and <2.6.0-RC1",
"2021.0.0-RC1": "Spring Boot >=2.6.0-RC1 and <2.6.1",
"2021.0.1": "Spring Boot >=2.6.1 and <2.6.5-SNAPSHOT",
"2021.0.2-SNAPSHOT": "Spring Boot >=2.6.5-SNAPSHOT and <3.0.0-M1",
"2022.0.0-M1": "Spring Boot >=3.0.0-M1 and <3.1.0-M1"
},

That provides a crystal clear definition of what versions map to what.

@azizabah
Your comment make sense.
I'll reopen this issue and improve the document.

Hi, @azizabah .
I update the wiki page. Please help to check:
https://github.com/Azure/azure-sdk-for-java/wiki/Spring-Versions-Mapping

@chenrujun - That looks great. Thanks for the update and feel free to close now.

Closing this issue, because related wiki page has been updated.


[MM-37978] - Start Trial CTA in Main Menu

Summary
This PR adds a new CTA for users on E0 to start the Trial license
Ticket Link
MM-37978
Screenshots

Release Note
NONE

Should this have a release note? It adds new UI.

Should we add a space for the mobile view?

Mattermost test server created! 🎉
Access here: mattermost-webapp-pr-8684.test.mattermost.cloud
Account Type	Username	Password
Admin	sysadmin	Sys@dmin123
User	user-1	User-1@123

@annelieseklein this test server is new with the trial options available for your review.

@annelieseklein gentle ping on this

@amyblais we would like to include this to v6.0

/cherry-pick release-6.0

Cherry pick is scheduled.


Adding code review commits I missed pushing in #1

Dunno how I didn't include them in #1, but I seem to have missed them ALL.

Pulling because it was just missed in #1, no re-review.


Doesn't work

When I try listen along with someone else it still tells me I need to buy premium...

Is the plugin enabled in the BD plugin settings?

yes it is, and doesn't work

Do you have any other plugins which are related to Spotify? Do you have ZeresPluginLibrary installed? If yes, then play any song in spotify, press ctrl+shift+i and go to console and paste:
BdApi.findModuleByProps("isSpotifyPremium").isSpotifyPremium()
and press enter, then send a screenshot here.

wait, I just saw that you are not issue author, @marcpinet , are you having the same issue as the author ?

wait, I just saw that you are not issue author, @marcpinet , are you having the same issue as the author ?

yes

can you also type this in console and tell me the output ?
ZeresPluginLibrary.DiscordModules.DeviceStore.getProfile(123)

->ZeresPluginLibrary.DiscordModules.DeviceStore.getProfile(123)
->undefined

Multiple people replying on troubleshooting steps don't help the problem. Well, the plugin seems to be working fine. It is patching the functions needed to be patched. Try reconnecting your Spotify account with discord.

Do you have any other plugins which are related to Spotify? Do you have ZeresPluginLibrary installed? If yes, then play any song in spotify, press ctrl+shift+i and go to console and paste:
BdApi.findModuleByProps("isSpotifyPremium").isSpotifyPremium()
and press enter, then send a screenshot here.

can you also type this in console and tell me the output ?
ZeresPluginLibrary.DiscordModules.DeviceStore.getProfile(123)

@ModkaVartini The plugin doesn't seem to be enabled. Double-check that you have the plugin enabled.

@ModkaVartini The plugin doesn't seem to be enabled. Double-check that you have the plugin enabled.

It is enabled, ZeresPluginLibrary is installed as well, don't see what I could be doing wrong.

Update: I opened discord today and gave it another go when @ordinall reached out to me in my dms (props to him for actually caring) and now it works like a charm! I haven't the slightest idea as to how it did, but I like to think a restart is what fixed it.

Since the original issue creator has been inactive for really long, i am gonna close this issue, if someone gets a similar problem, they can make a new issue.


New version: KRTirtho.Spotube version 3.0.1

Pull request has been created with WinGet Releaser v2 :rocket:
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/115317&drop=dogfoodAlpha

@wingetbot run


New Misc Marker:  [firebaseZ_spawn]

Name
OMEGA RADIO
Type of Misc Marker
Omega Radio
Description
On top of a table, across from the bunk beds in the upper floor of the aromory. Have to turn on power first
Map
firebaseZ_spawn
Location Coordinates
[300.9558734823382,<PHONE_NUMBER>503805]
Any Other Info
No response

Thanks for the input @NamelesZombie, this has been added!


Delete documents

Anyone using the web link can view the documents from Document Viewer.
Is it possible to hide/remove the documents from portal itself? (instead of deleting from Blob Storage). It would be super if you can implement that. Pls let me know. Thanks.

implemented


Sample iSCSI yaml files?

Did anyone get the iSCSI driver to work? If so can you provide some sample yaml files?

@j-griffith have you had any success modifying the current driver to run on kubernetes? Any ideas what requirements the spec would have, e.g. is it needed/sufficient to mount /dev? Thanks!

I started this last week but I've shifted gears a bit and am working on the iscsi connector libs (will need/want that for this driver) first.  I may be able to get back to this at the end of the week or early next week and get something posted.  I'll update here.
BTW, the approach I've taken is to just focus on the CSI driver itself, and not the deployment and ansible playbooks.  You'll need more than just /dev I think though; in particular /lib/modules and likely /run and /etc/localtime to keep lvm happy but I haven't dug into things to be sure yet.


Ubuntu / Debian / Fedora Support

This patch provides support for the following Linux Distros

Ubuntu 12.04, 14.04, 15.04, 15.10
Debian Jessie
Fedora 23, 22

Signed-off-by: Rian Quinn<EMAIL_ADDRESS>

General +1, though the switch from non-typedef structs to typedef structs in the elf loader would've been more appropriate as a separate PR. Closing this PR. as the merge conflict is resolved on a PR that has this commit stacked in it (PR #95)


Stuck waiting for StS to generate log file

I've followed the readme instructions and find myself stuck at waiting for StS to generate log file.

I haven't checked the game in a while, it is possible that they changed the way they manage logs.
If that's not the case though, make sure to close your game after going past Neoh and the open it back after a couple of seconds. It should work if you recreate that.

Ah, it seems that the log folder has changed for me in the beta. I dont know about core game, but if you are in beta look for
[  In your root folder of the game SendToDevs > logs > SlayTheSpire.log  ]
Not only that, the log issue has been fixed apparently so you will not have to wait for the log, it will be instant no restarts needed :) I'll update the repository in the weekend !
Make sure to delete your log.txt so that you can re select the .log and you are golden! Have fun, and let me know how it went.

This is great, I really like it.
Is there a way I can use custom weights? It would be cool to be able to
just enter the weights I wanted the algorithm to use.
On 23 March 2018 at 01:13, rainy<EMAIL_ADDRESS>wrote:

Ah, it seems that the log folder has changed for me in the beta. I dont
know about core game, but if you are in beta look for
[ In your root folder of the game SendToDevs > logs > SlayTheSpire.log ]
Not only that, the log issue has been fixed apparently so you will not
have to wait for the log, it will be instant no restarts needed :) I'll
update the repository in the weekend !
Make sure to delete your log.txt so that you can re select the .log and
you are golden! Have fun, and let me know how it went.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/karakasis/STS_AutoRoute/issues/1#issuecomment-375498616,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aj5T_-Asjt9zDCj5wSZsP-GozTBv-T88ks5thD5HgaJpZM4S2JtX
.

Yeah i can add this functionality. Just didnt want to make it too complicated to use.

That would be really cool.
On 24 March 2018 at 15:56, rainy<EMAIL_ADDRESS>wrote:

Yeah i can add this functionality. Just didnt want to make it too
complicated to use.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/karakasis/STS_AutoRoute/issues/1#issuecomment-375895139,
or mute the thread
https://github.com/notifications/unsubscribe-auth/Aj5T_3BnkqWUAkWau0evYhSAM83O6_5cks5thl6PgaJpZM4S2JtX
.