Large BQ only table compares incorrect

I have two equal tables in BQ that are in the same schema, loaded from CSV files, have different names, same unique rows in each table (verified by SQL queries in GCP BQ), all STRING columns, about 200,000 rows.  The column compares are failing with some interesting rows in the BQRH table where either the source or target tables is null.
I'm going to modify the test today and make several columns, including the PK and compare column, INTEGER and see if I get the same compare results.
The tables were loaded to BQ using Cloud tools for PowerShell on W10.  Cloud tools gets updated to current each day.

This seems to be a bug that limits the rows at 10k due to support for random row limits.

I added a trace and some other information.
err2_2022_4_1.txt

This seems to be the culprit - Ibis limits query results to 10k: ibis.options.sql.default_limit = 100

Can you explain how to build the development branch?  I can download the repo but when I do a “pip install google-pso-data-validator” does that build the development branch?
I haven’t gotten any action on the developers list manager at Mayo.  I’ll probably be a tester for now.  After I build and test the latest fixes I’ll report any bugs again.  Thank you for your help!
Brian Brownlow
Senior Analyst Programmer
Big Data services
Office<PHONE_NUMBER>
Mayo Clinic Rochester
From: Neha Nene @.>
Sent: Friday, April 01, 2022 4:39 PM
To: GoogleCloudPlatform/professional-services-data-validator @.>
Cc: Brownlow, Brian N. @.>; Author @.>
Subject: [EXTERNAL] Re: [GoogleCloudPlatform/professional-services-data-validator] Large BQ only table compares incorrect (Issue #415)
This seems to be the culprit - Ibis limits query results to 10k: ibis.options.sql.default_limit = 100https://github.com/ibis-project/ibis/blob/9bb6bc2816de2c5acc96f3073fa92a879536d42b/docs/user_guide/configuration.md#sql-query-execution
—
Reply to this email directly, view it on GitHubhttps://github.com/GoogleCloudPlatform/professional-services-data-validator/issues/415#issuecomment-1086349585, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AJGIKLHI3XWHZK5U43QOTFDVC5UI3ANCNFSM5SIYMMCQ.
You are receiving this because you authored the thread.Message ID<EMAIL_ADDRESS>


Run redis over ssl when password is present

PR Title :boom:
Forcing redis to run over SSL when password is present as in app-interface.
Suggested formats:

Fixes/Refs #RHIROS-XXX - Title
RHIROS-XXX Title

Feel free to remove this section from PR description once done.
Why do we need this change? :thought_balloon:
Updating all of the various apps that will be running in environments where SSL is enforced we need to toggle redis:// -> rediss:// when the password is present.
Documentation update? :memo:

[ ] Yes
[x] No

Security Checklist :lock:
Upon raising this PR please go through RedHatInsights/secure-coding-checklist
:guardsman: Checklist :dart:

[ ] Bugfix
[ ] New Feature
[x] Refactor
[ ] Unittests Added
[ ] DRY code
[ ] Dependency Added
[ ] DB Migration Added

Additional :mega:
Feel free to add any other relevant details such as links, notes, screenshots, here.

Codecov Report
Patch coverage: 100.00% and project coverage change: +0.02 :tada:

Comparison is base (9c2ee47) 72.52% compared to head (2b34907) 72.54%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #337      +/-   ##
==========================================
+ Coverage   72.52%   72.54%   +0.02%
==========================================
  Files          28       28
  Lines        1354     1355       +1
==========================================
+ Hits          982      983       +1
  Misses        372      372

Flag
Coverage Δ

unittests
72.54% <100.00%> (+0.02%)
:arrow_up:

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

Impacted Files
Coverage Δ

ros/lib/config.py
55.76% <100.00%> (+0.42%)
:arrow_up:

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

thanks @lindgrenj6 for changes! LGTM! Merging now!


pip install failing

There are multiples issues with installing the version of the packages

numpy~=1.18.4 : Throws error: subprocess-exited-with-error
torch, torchtext versions missing, or is it because of a different Python version. It throws this: ERROR: Ignored the following versions that require a different python version: 0.7 Requires-Python >=3.6, <3.7; 0.8 Requires-Python >=3.6, <3.7 ERROR: Could not find a version that satisfies the requirement torchtext~=0.7.0 (from versions: 0.1.1, 0.2.0, 0.2.1, 0.2.3, 0.3.1, 0.4.0, 0.5.0, 0.6.0, 0.8.1, 0.9.0, 0.9.1, 0.10.0, 0.10.1, 0.11.0, 0.11.1, 0.11.2, 0.12.0, 0.13.0, 0.13.1, 0.14.0, 0.14.1, 0.15.1, 0.15.2) ERROR: No matching distribution found for torchtext~=0.7.0
Is updating the functions according to the recent versions of the libraries/packages used the only way to go forward?

I have the same problem as you. Have you solved it？

Hi, I got the same issue and I managed to fix it.
Here are the steps:

Use Python 3.8 as there are already many pre-built packages available on pip. I recommend you to use pyenv to install it alongside your system Python so you won't break your system Python version. Using pyenv:

# Install Python 3.8
pyenv install 3.8

# Enable Python 3.8
pyenv shell 3.8

# Verify that the version is correct
pip --version

# Should outputs:
pip 23.0.1 from /home/michel/.pyenv/versions/3.8.19/lib/python3.8/site-packages/pip (python 3.8)

Then you can install dependencies (there are some extra steps to fix errors):

# Install dependencies
# Force install old version of sklearn and downgrade protobuf to avoid errors
SKLEARN_ALLOW_DEPRECATED_SKLEARN_PACKAGE_INSTALL=True venv/bin/pip install -r requirements.txt
venv/bin/pip install protobuf==3.19.0

Finally replace the dataset sources as they are either unavailable or too slow with this one:

# Replacing all occurence of the old source url by the new one
grep -rl 'http://yann.lecun.com/exdb/mnist/' . | xargs sed -i 's|http://yann.lecun.com/exdb/mnist/|https://github.com/golbin/TensorFlow-MNIST/raw/master/mnist/data/|g'

After that you can normally run it:
venv/bin/python training.py --name mnist --params configs/mnist_params.yaml --commit none
/home/michel/Downloads/backdoors101/venv/lib/python3.8/site-packages/torch/cuda/__init__.py:52: UserWarning: CUDA initialization: Found no NVIDIA driver on your system. Please check that you have an NVIDIA GPU and installed a driver from http://www.nvidia.com/Download/index.aspx (Triggered internally at  /pytorch/c10/cuda/CUDAFunctions.cpp:100.)
  return torch._C._cuda_getDeviceCount() > 0
Downloading https://github.com/golbin/TensorFlow-MNIST/raw/master/mnist/data/train-images-idx3-ubyte.gz to .data/MNIST/raw/train-images-idx3-ubyte.gz
9920512it [00:02, 3679627.46it/s]
Extracting .data/MNIST/raw/train-images-idx3-ubyte.gz to .data/MNIST/raw
Downloading https://github.com/golbin/TensorFlow-MNIST/raw/master/mnist/data/train-labels-idx1-ubyte.gz to .data/MNIST/raw/train-labels-idx1-ubyte.gz
32768it [00:00, 62339.13it/s]
Extracting .data/MNIST/raw/train-labels-idx1-ubyte.gz to .data/MNIST/raw
Downloading https://github.com/golbin/TensorFlow-MNIST/raw/master/mnist/data/t10k-images-idx3-ubyte.gz to .data/MNIST/raw/t10k-images-idx3-ubyte.gz
1654784it [00:01, 1595056.98it/s]
Extracting .data/MNIST/raw/t10k-images-idx3-ubyte.gz to .data/MNIST/raw
Downloading https://github.com/golbin/TensorFlow-MNIST/raw/master/mnist/data/t10k-labels-idx1-ubyte.gz to .data/MNIST/raw/t10k-labels-idx1-ubyte.gz
8192it [00:00, 13965.30it/s]
Extracting .data/MNIST/raw/t10k-labels-idx1-ubyte.gz to .data/MNIST/raw
Processing...
/home/michel/Downloads/backdoors101/venv/lib/python3.8/site-packages/torchvision/datasets/mnist.py:480: UserWarning: The given NumPy array is not writeable, and PyTorch does not support non-writeable tensors. This means you can write to the underlying (supposedly non-writeable) NumPy array using the tensor. You may want to copy the array to protect its data or make it writeable before converting it to a tensor. This type of warning will be suppressed for the rest of this program. (Triggered internally at  /pytorch/torch/csrc/utils/tensor_numpy.cpp:141.)
  return torch.from_numpy(parsed.astype(m[2], copy=False)).view(*s)
Done!
2024-04-24 21:34:04 - WARNING  - | name | value |
 |-----|-----|
| task | MNIST |
| synthesizer | Pattern |
| batch_size | 64 |
| test_batch_size | 100 |
| lr | 0.01 |
| momentum | 0.9 |
| decay | 0.0005 |
| epochs | 350 |
| save_on_epochs | [] |
| optimizer | SGD |
| log_interval | 100 |
| scheduler | False |
| poisoning_proportion | 1.0 |
| backdoor_label | 8 |
| backdoor | True |
| backdoor_dynamic_position | False |
| loss_balance | MGDA |
| mgda_normalize | loss |
| save_model | False |
| log | False |
| tb | False |
| transform_train | True |
| loss_tasks | ['backdoor', 'normal'] |
| current_time | Apr.24_21.33.58 |
| commit | none |
| name | mnist |
100it [00:03, 27.61it/s]
2024-04-24 21:34:07 - WARNING  - Backdoor False. Epoch:     0. Accuracy: Top-1: 9.15 | Loss: value: 2.31
0it [00:00, ?it/s]2024-04-24 21:34:07 - INFO     - Epoch:   1. Batch:     0/938.  Losses: ['backdoor: 2.33', 'normal: 2.29', 'total: 2.29']. Scales: ['backdoor: 0.01', 'normal: 0.99']
99it [00:10, 10.18it/s]2024-04-24 21:34:18 - INFO     - Epoch:   1. Batch:   100/938.  Losses: ['backdoor: 1.02', 'normal: 1.04', 'total: 1.03']. Scales: ['backdoor: 0.16', 'normal: 0.84']
200it [00:20, 10.09it/s]2024-04-24 21:34:28 - INFO     - Epoch:   1. Batch:   200/938.  Losses: ['backdoor: 0.10', 'normal: 0.22', 'total: 0.21']. Scales: ['backdoor: 0.09', 'normal: 0.91']
300it [00:31,  9.09it/s]2024-04-24 21:34:39 - INFO     - Epoch:   1. Batch:   300/938.  Losses: ['backdoor: 0.04', 'normal: 0.13', 'total: 0.13']. Scales: ['backdoor: 0.08', 'normal: 0.92']
400it [00:41,  8.77it/s]2024-04-24 21:34:49 - INFO     - Epoch:   1. Batch:   400/938.  Losses: ['backdoor: 0.03', 'normal: 0.11', 'total: 0.11']. Scales: ['backdoor: 0.07', 'normal: 0.93']
500it [00:51,  9.02it/s]2024-04-24 21:34:59 - INFO     - Epoch:   1. Batch:   500/938.  Losses: ['backdoor: 0.01', 'normal: 0.09', 'total: 0.09']. Scales: ['backdoor: 0.06', 'normal: 0.94']
600it [01:01,  9.06it/s]2024-04-24 21:35:09 - INFO     - Epoch:   1. Batch:   600/938.  Losses: ['backdoor: 0.02', 'normal: 0.10', 'total: 0.09']. Scales: ['backdoor: 0.07', 'normal: 0.93']
699it [01:12,  9.40it/s]2024-04-24 21:35:20 - INFO     - Epoch:   1. Batch:   700/938.  Losses: ['backdoor: 0.01', 'normal: 0.09', 'total: 0.09']. Scales: ['backdoor: 0.07', 'normal: 0.93']
799it [01:22, 10.43it/s]2024-04-24 21:35:30 - INFO     - Epoch:   1. Batch:   800/938.  Losses: ['backdoor: 0.01', 'normal: 0.06', 'total: 0.05']. Scales: ['backdoor: 0.09', 'normal: 0.91']
899it [01:33,  9.95it/s]2024-04-24 21:35:40 - INFO     - Epoch:   1. Batch:   900/938.  Losses: ['backdoor: 0.01', 'normal: 0.08', 'total: 0.07']. Scales: ['backdoor: 0.06', 'normal: 0.94']
...


Publish code coverage task fix

We were not pushing report directory when there is no code coverage data. But user might need it to check what is missing.
fixed it.
Unit test changes accordingly.
Manual verification

Approved


Magnolia interface unification for Scala 2 and Scala 3 versions

In a process of migrating the project to Scala 3, I created a cross build. In which, I separated code with magnolia, that differs. So the Scala 2. code uses 1.1.3 version, and Scala 3 uses 1.2.6. Also, there is common code, which I want to keep for both versions. But, I've stumbled upon a problem, that those 2 versions of magnolia have different interfaces. In particular, I have a problem with CaseClass 'params'. In 1.1.3 it's "parameters", but in 1.2.6 it's "params" :
https://github.com/softwaremill/magnolia/blob/27d0e677bc7e7e258d89afb5b34fd7f10c8cf07b/src/core/interface.scala#L109
https://github.com/softwaremill/magnolia/blob/2a2ecb8edb8f80b0bae49898962eac0d67dfbf78/core/src/main/scala/magnolia1/interface.scala#L546
So, is there any way to unify these interfaces, for such use cases like mine?

Yes, and I expect this might diverge further. For example, we'll be releasing magnolia 2 for scala 3 using a different package name (see https://github.com/softwaremill/magnolia/pull/457), and there might be more changes needed to support scala3-specific types. So I don't think having a unified interface will be possible in the long run.


Top of text is slightly clipped in ab-glyph 0.2.12 but not in ab-glyph 0.2.11

I've got a graphical program that transitively depends on ab-glyph (wgpu_glyph -> glyph-brush -> ab_glyph). I recently ran cargo update and noticed some text clipping I hadn't seen before. The change seems to be caused by upgrading ab-glyph 0.2.11 to ab-glyph 0.2.12.
The text clipping doesn't seem to happen with every font.
I've created a repository with scripts to run example code against the two versions. The example it runs is the hello example from wgpu_glyph, modified to use a font that clips in 0.2.12 but not 0.2.11. It also contains the glyph-brush crate modified to use a specific ab-glyph version (either 0.2.12 or 0.2.11, depending on which script is run). The code requires a unix-like environment with basic utilities (e.g., tar, mv, etc.).
https://github.com/MichaelMMacLeod/debugging-font-weirdness
Running the 0.2.11 example results in the following (which seems correctly displayed):

Running the 0.2.12 example results in the following (where the top of the text gets slightly clipped):

The text also appears a bit bigger in 0.2.12 than it did in 0.2.11 (which might be why it's clipping).

This is presumably due to ttf-parser changes affecting this particular font.
I'll investigate when I get a chance. In meantime do you have a link to the
font you're using?
On Sat, 11 Dec 2021, 23:03 MichaelMMacLeod, @.***>
wrote:

I've got a graphical program that transitively depends on ab-glyph (wgpu_glyph
-> glyph-brush -> ab_glyph). I recently ran cargo update and noticed some
text clipping I hadn't seen before. The change seems to be caused by
upgrading ab-glyph 0.2.11 to ab-glyph 0.2.12.
The text clipping doesn't seem to happen with every font.
I've created a repository with scripts to run example code against the two
versions. The example it runs is the hello example from wgpu_glyph,
modified to use a font that clips in 0.2.12 but not 0.2.11. It also
contains the glyph-brush crate modified to use a specific ab-glyph
version (either 0.2.12 or 0.2.11, depending on which script is run). The
code requires a unix-like environment with basic utilities (e.g., tar, mv,
etc.).
https://github.com/MichaelMMacLeod/debugging-font-weirdness
Running the 0.2.11 example results in the following (which seems correctly
displayed):
[image: Screenshot_20211211_145430]
https://user-images.githubusercontent.com/17838676/145694056-ec1ae22d-5e93-4663-8a98-3d5f05e42670.png
Running the 0.2.12 example results in the following (where the top of the
text gets slightly clipped):
[image: image]
https://user-images.githubusercontent.com/17838676/145694086-ad9c1e4a-883a-4052-92bf-1ded38c3b57d.png
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/alexheretic/ab-glyph/issues/50, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AARZHV75C2TEBINIYE366GDUQPKF5ANCNFSM5J3QT57Q
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I'm using CooperHewitt-OTF-public/CooperHewitt-Book.otf from https://uh8yh30l48rpize52xh0q1o6i-wpengine.netdna-ssl.com/wp-content/uploads/fonts/CooperHewitt-OTF-public.zip. (the download link comes from https://www.cooperhewitt.org/open-source-at-cooper-hewitt/cooper-hewitt-the-typeface-by-chester-jenkins/)
The font is also inside the tarball of crates in https://github.com/MichaelMMacLeod/debugging-font-weirdness. After running one of the scripts you can cd into the directory the script created and then cd wgpu_glyph/examples to find the font there as well.

Thanks for the investigation---I appreciate the work you've put in to address this issue. Unfortunately, I don't know much about the implementation of fonts, so I can't really comment about whether or not  overflowing of the ascender / descender bounds is a problem with this specific font or just a weird edge-case that font rasterizers aught to handle.


$state.go not Worked in resolve

$state.go is not working in resolve ????

Thats not really the place to use a $state.go. http://bit.ly/UIR-SOF


Implement specific get/set class_id services for Intersection and Distance Triggers

The current ODE Trigger (base class) level get/set client services do not work for the Intersection and Distance Triggers as both support Class A - Class B testing.  New AB Trigger specific get/set calls will need to be implemented to override the base class services.
/**
 * @brief Gets the current class_id_a and class_id_b filters for the ODE Trigger
 * @param[in] name unique name of the Intersection ODE Trigger to query
 * @param[out] class_id_a returns the current class_id for Class A
 * @param[out] class_id_b returns the current class_id for Class B
 * @return DSL_RESULT_SUCCESS on successful query, DSL_RESULT_ODE_TRIGGER_RESULT otherwise.
 */
DslReturnType dsl_ode_trigger_class_id_ab_get(const wchar_t* name,
    uint* class_id_a, uint* class_id_b);

/**
 * @brief Sets the class_id_a and class_id_b filters for the ODE Trigger to filter on
 * @param[in] name unique name of the ODE Trigger to update
 * @param[in] class_id_a returns the current class_id for Class A
 * @param[in] class_id_b returns the current class_id for Class B
 * @return DSL_RESULT_SUCCESS on successful update, DSL_RESULT_ODE_TRIGGER_RESULT otherwise.
 */
DslReturnType dsl_ode_trigger_class_id_ab_set(const wchar_t* name, uint class_id_a, uint class_id_b);

Done


这是否是一个 Bug？

[X] 我已经确认我要报告的是一个 Bug

这个问题是否已经存在？

[X] 我已经确认这个 Issue 没有被报告过

Alova 版本
3.0
前端框架
Vue
问题描述
X [ERROR] Could not resolve "@alova/shared/function"
node_modules/alova/dist/stateshook/vue.esm.js:8:37:
  8 │ import { createSyncOnceRunner } from '@alova/shared/function';
    ╵                                      ~~~~~~~~~~~~~~~~~~~~~~~~

You can mark the path "@alova/shared/function" as external to exclude it from the bundle, which
will remove this error and leave the unresolved path in the bundle.
X [ERROR] Could not resolve "@alova/shared/function"
node_modules/@alova/adapter-uniapp/dist/alova-adapter-uniapp.esm.js:8:36:
  8 │ import { isPlainObject, noop } from '@alova/shared/function';
    ╵                                     ~~~~~~~~~~~~~~~~~~~~~~~~

You can mark the path "@alova/shared/function" as external to exclude it from the bundle, which
will remove this error and leave the unresolved path in the bundle.
X [ERROR] Could not resolve "@alova/shared/function"
node_modules/alova/dist/alova.esm.js:8:274:
  8 │ ...etLocalCacheConfigParam, isFn, getConfig, getOptions, isPlainObject, sloughFunction, noop, $self, isSpecialRequestBody, getContextOptions, key, isString } from '@alova/shared/function';
    ╵                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~

You can mark the path "@alova/shared/function" as external to exclude it from the bundle, which
will remove this error and leave the unresolved path in the bundle.
X [ERROR] Could not resolve "@alova/shared/function"
node_modules/alova/dist/clienthook/index.esm.js:8:402:
  8 │ ...t, walkObject, uuid as uuid$1, globalToString, delayWithBackoff, isString, getConfig, createAsyncQueue, getLocalCacheConfigParam, usePromise, getOptions } from '@alova/shared/function';
    ╵                                                                                ~~~~~~~~~~~~~~~~~~~~~~~~

You can mark the path "@alova/shared/function" as external to exclude it from the bundle, which
will remove this error and leave the unresolved path in the bundle.
X [ERROR] Could not resolve "@alova/shared/vars"
node_modules/alova/dist/stateshook/vue.esm.js:9:49:
  9 │ import { setTimeoutFn, forEach, trueValue } from '@alova/shared/vars';
    ╵                                                  ~~~~~~~~~~~~~~~~~~~~

You can mark the path "@alova/shared/vars" as external to exclude it from the bundle, which will
remove this error and leave the unresolved path in the bundle.
X [ERROR] Could not resolve "@alova/shared/vars"
node_modules/@alova/adapter-uniapp/dist/alova-adapter-uniapp.esm.js:9:20:
  9 │ import { len } from '@alova/shared/vars';
    ╵                     ~~~~~~~~~~~~~~~~~~~~

You can mark the path "@alova/shared/vars" as external to exclude it from the bundle, which will
remove this error and leave the unresolved path in the bundle.
X [ERROR] Could not resolve "@alova/shared/vars"
node_modules/alova/dist/alova.esm.js:9:321:
  9 │ ...jectKeys, PromiseCls, deleteAttr, isArray, MEMORY, promiseThen, trueValue, falseValue, promiseFinally, promiseReject, promiseCatch, JSONStringify, JSONParse } from '@alova/shared/vars';
    ╵                                                                                ~~~~~~~~~~~~~~~~~~~~

You can mark the path "@alova/shared/vars" as external to exclude it from the bundle, which will
remove this error and leave the unresolved path in the bundle.
X [ERROR] Could not resolve "@alova/shared/vars"
node_modules/alova/dist/clienthook/index.esm.js:9:415:
  9 │ ...s, ObjectCls, valueObject, defineProperty, includes, RegExpCls, regexpTest, shift, mapItem as mapItem$1, MEMORY, objectValues, promiseReject, promiseFinally } from '@alova/shared/vars';
    ╵                                                                                ~~~~~~~~~~~~~~~~~~~~

You can mark the path "@alova/shared/vars" as external to exclude it from the bundle, which will
remove this error and leave the unresolved path in the bundle.
X [ERROR] Could not resolve "@alova/shared/assert"
node_modules/alova/dist/alova.esm.js:10:29:
  10 │ import { createAssert } from '@alova/shared/assert';
     ╵                              ~~~~~~~~~~~~~~~~~~~~~~

You can mark the path "@alova/shared/assert" as external to exclude it from the bundle, which will
remove this error and leave the unresolved path in the bundle.
X [ERROR] Could not resolve "@alova/shared/assert"
node_modules/alova/dist/clienthook/index.esm.js:10:41:
  10 │ import { createAssert, AlovaError } from '@alova/shared/assert';
     ╵                                          ~~~~~~~~~~~~~~~~~~~~~~

You can mark the path "@alova/shared/assert" as external to exclude it from the bundle, which will
remove this error and leave the unresolved path in the bundle.
10:42:04 [vite] Build failed with 10 errors:
node_modules/@alova/adapter-uniapp/dist/alova-adapter-uniapp.esm.js:8:36: ERROR: Could not resolve "@alova/shared/function"
node_modules/@alova/adapter-uniapp/dist/alova-adapter-uniapp.esm.js:9:20: ERROR: Could not resolve "@alova/shared/vars"
node_modules/alova/dist/alova.esm.js:8:274: ERROR: Could not resolve "@alova/shared/function"
node_modules/alova/dist/alova.esm.js:9:321: ERROR: Could not resolve "@alova/shared/vars"
node_modules/alova/dist/alova.esm.js:10:29: ERROR: Could not resolve "@alova/shared/assert"
期望的表现
No response
复现链接
No response
复现步骤
createAlova({   ...AdapterUniapp() })
系统信息
No response
补充说明
No response

pnpm下使用uniapp，需要额外安装@alova/shared

已经安装了的

<EMAIL_ADDRESS>

<EMAIL_ADDRESS>


Installing Kali via PowerShell installs an outdated version.

Version
Microsoft Windows [Version 10.0.22000.493]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
2019.2 / 2021.4 / 2022.1
Other Software
No response
Repro Steps
wsl --install -d kali-linux
Expected Behavior
WSL installs the latest (or a recent) Kali build (Currently 2021.4 if installed via the Microsoft Store).
Actual Behavior
WSL installs Kali build 2019.2 when installed through PowerShell.
This build is not updatable as apt / apt-get throws an error due to expired key signatures. A workaround exists, but attempting to update this build then throws another error that breaks the OS (or at least sudo / su functionality as far as I've tested, but Google shows other folks have encountered deeper issues).
Diagnostic Logs
No response

The WSL distro images downloaded by wsl --install... are hosted by Microsoft and have to be manually updated. They can get a little behind. The Kali team will need to provide an updated .appx to Microsoft and Microsoft will need to update it on their side.


Week 2

Implement the portfolio web-page with:

Github link

Nice cat picture

Projects and descriptions

Random fact button

Technologies used: HTML, css, JavaScript

Consider separating the different bits of this into separate pull requests. A good rule of thumb for the size of a pull request is 1 logical unit. If the pull request description contains a bullet list of features that are not strictly interdependent, or if in doubt, I'd consider splitting it up. Smaller pull requests are easier to write, update, review and manage. Of course, initially this is a bit of an overkill, but eventually I hope this practice will become more and more useful as you start working on larger, more complicated pieces in a more collaborative environment.


Runbook standards

eg “Does this service have a runbook, and can it be accessed”, but also maybe mirror runbooks around the world.

It would be good to have a conversation with the modernisation platform team about their approach to making the platform introspectable, in the way that the cloud platform is.
How we do this for more "legacy" stuff, I'm not sure - how do we know what services exist, without a reliable register of tech.

Stale. We have repo standards that we are happy with for now.


[cpuinfo] Fix tool cpuid-dump not found

Describe the pull request

What does your PR fix?
Fixes #28271

Duplicate of #28409


Improve datamasking performance

Type of Change

[X] Bug fix (non-breaking change, fixes # )
[X] New feature (non-breaking change, adds functionality, fixes # )
[ ] Breaking change (effects multiple commands or functionality, fixes # )
[ ] Ran manual Pester test and has passed (`.\tests\manual.pester.ps1)
[ ] Adding code coverage to existing functionality
[ ] Pester test is included
[ ] If new file reference added for test, has is been added to github.com/sqlcollaborative/appveyor-lab ?
[ ] Nunit test is included
[ ] Documentation
[ ] Build system

Purpose
When dealing with larger data sets, the masking command would either use a lot of memory or crash.
Also the speed of the updates drastically decreases when dealing with more than a million rows.
Approach
The command now works in batches. The update statement will be separated in batches and executed on the destination database.
Prior to the masking the command check if the table contains an identity column.
If it has an identity column, it will create a nonclustered index on that column.
If it doesn't have an identity column, the table will be altered by adding a column called "MaskingID" containing an identity.
Afterwards the command will remove both the index and if needed change the table back by removing the identity column.


[FEATURE] Connecting backend auth controllers with the frontend

Description
As our backend auth controllers and routes are ready , we need to connect them with the frontend
Use Case
After this feature we will have a full functional authentication system
Proposed Solution
No response
Additional Information
No response
Attachments
No response

Hi @krishnaacharyaa is this issue is closed

No it is WIP, I have pinged you in the discord, check it out


Rust RFC

@steckes I just put up a new version attempting to address each of your comments, please give it another look when you get a chance. Thanks for the feedback so far


LilyGo T-display

Would appreciate getting this slightly older board added.
https://uelectronics.com/wp-content/uploads/2020/10/Esquematico-TTGO-T-Display-ESP32-scaled.jpg

The board is now available


Buffer overflow in package.c, function add_exec_dir

Hi,
Look at add_exec_dir function located in src/libponyc/pkg/package.c file. It allocates buffer:
char path[FILENAME_MAX];

then reads executable path to that buffer:
readlink("/proc/self/exe", path, FILENAME_MAX - 1);

then finds the last slash in the path:
char *p = strrchr(path, PATH_SLASH);

and chops it:
p++;
*p = '\0'

then appends a suffix tho the path:
strcpy(p, "../lib");

one more time:
strcpy(p, "../packages");

and one more time:
strcpy(p, "../../packages");

This will cause buffer overflow if:

executable path length is close to FILENAME_MAX,
the executable name is short.

For example: if executable name is ponyc, and path length is FILENAME_MAX (or so, e. g. FILENAME_MAX - 1) the function will chop 5 characters from path, but append 6 (../lib), 11 (../packages), and 14 (../../packages) characters which will be written behind the end of allocated buffer.

Hi.
Digging through the code, this issue made me curious. (Thanks for the detailed report.)
I can't seem to create a test case, though:
Running in docker run -v $(pwd):/ponyc -it ponylang/ponyc bash (where pwd is a recent checkout):
$ pwd
/ponyc/examples
$ which ponyc # this should be close enough
/ponyc/examples/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/bbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbbb/ccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccccc/ffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffffff/ponyc
$ ponyc helloworld
Error:
builtin: couldn't locate this path
$

So I haven't dug into this enough to find where it is caught, but I think this buffer overflow might not be a problem after all? There are checks for path length, however. @van-de-bugger: if you could dig up a test case, this would be very helpful in discussing this issue, I suppose :)

I think this buffer overflow might not be a problem after all?

That's up to you.

…if you could dig up a test case…

How are you going to test buffer overflow? Program behavior is undefined in such a case. Who knows what the memory will be overwritten and how it will affect the running program.

…discussing this issue…

Frankly, I do not see a discussion topic. IMHO, any buffer overflow (even potential and hardly reproducible) must be fixed. Period. (You may have opposite opinion, though.)
The only possible discussion topic is how to fix it. I would recommend to throw away fixed-length buffers in favor of dynamically allocated buffers. Just use function asprintf(and free of course), it will make code much simpler.

Hey @van-de-bugger, thanks for responding so quickly.
I probably just qualify as an interested bystander, trying to help with this project -- not an authority of any kind.
Sorry if I was unclear in my last post, I do agree 100% that there shouldn't be any buffer overflows, anywhere. That said, thinking about how to solve the problem, my preferred course of action is roughly like this:

gather inputs that trigger the problem
fix the problem
use inputs of 1. to prove that the problem is solved.

What I have tried and struggled with is 1. If you have succeeded with this, please share your data 😃
(You can see what I've tried before, have I hit that issue without noticing?)
I am also not trying to deter you from PRing a fix, please don't get me wrong here.

From my current (limited!) understanding, what I see is like this example:
#include <stdio.h>
#include <string.h>
#include <stdbool.h>

bool mysterious(char** argv) {
  // who knows?
}

int main(int argc, char** argv) {
  char foo[4];

  if(!mysterious(argv))
    return 1;

  strcpy(foo, argv[1]);
  printf("foo is '%s'\n", foo);
}

Looking at the allocation, the user-controlled input (argv), and the strcpy call in isolation, this looks like a buffer overflow. The ways of figuring out if this is one, however, either needs diving into what mysterious does -- does it check the condition and never return true if the argument isn't safe? -- or, come up with a test case. In this situation, this would be easy:
$ ./foo bar
foo is 'bar'
$ ./foo barbaaz
Abort trap: 6

Does this make sense?
Cheers! 😃

Update, I've been digging some more:

ponyc calls ponyc_init
ponyc_init calls package_init
package_init calls the offending add_exec_dir

And I've pushed a commit here that sets the scene like you described -- by messing with the source instead of producing the real situation with /proc/self/exe, but I think we can safely assume this could happen (under weird circumstances, but it's possible).
And 🎉 :
$ build/debug/ponyc examples/helloworld
0 exec_path is '/Users/stephan/Misc/pony/ponyc/build/debug/ponyc', len = 48
0 path is '/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/ponyc', len = 1023
add_path(/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/)
add_path(/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/../lib)
add_path(/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/../packages)
add_path(/aaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaaa/../../packages)
Abort trap: 6
$

@van-de-bugger we'd love a PR to fix this. Thanks!

Listening to the sync call, I think there was some confusion. The offer to make it PR-able came from @srenatus regarding the commit referenced above.

@Perelandric @SeanTAllen: yup, I'd be happy to contribute. If you glance at e20065259a8b3ded1311411091b91b6021727bc3, what would be missing to PR this? (Does anyone with a better understanding of the source code put this someplace else or reuse something existing I've overlooked?)

@srenatus - it looks good to me, other than needing an entry in the CHANGLOG.md, and possibly making the error message a bit more descriptive (though I'm at a loss for exactly what words to choose).


[MNOE-106] Admin Panel Improvments

@alexnoox Can you have a look at the Angular part?
I'm looking at the ruby and fixing the specs.

LGTM

@claire00 I've added the specs in 777dc88b and pushed to feature/admin_panel_improvement, update your local branch (git pull upstream feature/admin_panel_improvement) and have a look for your information.
Could you also add @alexnoox suggestion?
Thanks

Closing in favor of #54 to merge in 3.1 branch


Better resolution Mac OS X icon

This always looked so gross in my dock compared to the other icons so I had to do something!
There could still be a small visual improvement but I need someone to provide me with a 1024x1024 logo... my photoshop skills aren't good enough to render my own version.
You can figure out which is which in this image ;)

(30 minutes)

Okay I got a copy of the 1024x1024 logo and updated this pull to use that as my base.


Forms: Iterable collection of states

Summary of changes
Depends on #254 to be merged.

Provides a new collection type StateCollection that provides the FormElement and its State.
The new type is iterable and immutable. A MutableStateCollection is provided that allows insertion of new elements.

thanks @sorenoid, merging!


magic-vlsi: 8.3.454 -> 8.3.456

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/magic/versions.
meta.description for magic-vlsi is: VLSI layout tool written in Tcl
meta.homepage for magic-vlsi is: http://opencircuitdesign.com/magic/
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 8.3.456 with grep in /nix/store/ss8x1729hv6w4nrndj708f5di1vvkn7d-magic-vlsi-8.3.456
found 8.3.456 in filename of file in /nix/store/ss8x1729hv6w4nrndj708f5di1vvkn7d-magic-vlsi-8.3.456

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
magic-vlsi

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/ss8x1729hv6w4nrndj708f5di1vvkn7d-magic-vlsi-8.3.456 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A magic-vlsi https://github.com/r-ryantm/nixpkgs/archive/b6839c45e5fee0d9e480a29845f70dc11617156a.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/b6839c45e5fee0d9e480a29845f70dc11617156a#magic-vlsi

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/ss8x1729hv6w4nrndj708f5di1vvkn7d-magic-vlsi-8.3.456
ls -la /nix/store/ss8x1729hv6w4nrndj708f5di1vvkn7d-magic-vlsi-8.3.456/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

magic-vlsi

Maintainer pings
cc @anna328p @thoughtpolice @AndersonTorres for testing.

wait, what? why did i get readded to the maintainers? i removed myself in #279973

You weren't readded to the maintainers by this PR, you're just notified since this was created three days before #279973.

That makes sense, thank you.


App Service limits - Number of apps in table is misleading

Hi there,
In the table for App Service limits the first row contains the following information:

Resource
Free
Shared
Basic
Standard
Premium (v1-v3)
Isolated

Web, mobile, or API apps per Azure App Service plan1
10
100
Unlimited2
Unlimited2
Unlimited2
Unlimited2

1 Apps and storage quotas are per App Service plan unless noted otherwise.
2 The actual number of apps that you can host on these machines depends on the activity of the apps, the size of the machine instances, and the corresponding resource utilization.
The number of apps is misleading because it isn't specified how many you can deploy while still getting support. While there is the second remark that states that "the actual number of apps (...) depends on activity of the apps (...) resource utilization", you won't get any support if you are over a recommended max. number of apps. The recommendation is specified in Should I put an app in a new plan or an existing plan?
In my case the utilization of the App Service Plan was below 25% but I had more apps deployed than was specified in the recommendation table. Unless I was going to split the App Service Plan or scale up I wouldn't get any support on my errors (except that I should split). The support was sticking to the recommended numbers as a hard limit and not as a guidance (how I view it).
In the end I had contact with Craig M. (Technical Lead Azure App Services), he agreed with me that it is wrong that the specified table shows unlimited, but that there is actually a recommendation that is used as maximum. He asked me to provide feedback to the page.
He stated that "they should have put the actual recommended number of apps within that documentation as well."
I don't care how the numbers are put into the table, if it is put into the table, or with a footnote linking to the other page, but it should be there. Ideally it would specify that support is only there if your apps are below the number of recommended apps.
Thank you.

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

ID: 36f49a06-90b1-cbe1-3853-2c38277b79f8
Version Independent ID: 02ff6f6c-3ef6-b48f-060d-b290419e0aba
Content: Azure subscription limits and quotas - Azure Resource Manager
Content Source: articles/azure-resource-manager/management/azure-subscription-service-limits.md
Service: azure-resource-manager
Sub-service: management
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

@Jeej
Thanks for your feedback! We will investigate and update as appropriate.

@Jeej - Thanks for bringing this to our attention.
I'm going to assign this to the document author so they can review and update accordingly.

@msangapu-msft - can you look at this request related to the statement about unlimited apps per App Service plan?

We have a new feedback system in place, so we need to close the remaining GitHub issues. I have created an issue in our internal tracking system.
#please-close


Is there a backpropagation-method for all math-layers i.e. tf.fft2d?

When building a deep NN, where one of the layer is represented by a fouriertransform (i.e. tf.fft), does tensorflow provide a backpropagation method for it? In this case it could/would be complex I guess.
How does the optimizer work on that? Are there any documents which could explain this behavior?
In theory, I understand how the gradient of a multiplication is carried out, but doing this for a more complicated function makes things more difficult for me.
Thank you very much :)

From https://www.tensorflow.org/versions/r0.11/resources/index.html

For help and support, technical or algorithmic questions, please submit your questions to Stack Overflow: https://stackoverflow.com/questions/tagged/tensorflow. You may also find answers in our FAQ, our glossary, or in the shapes, sizes and types guide. Please do not use the mailing list or issue tracker for support.


Added Home Page with Tailwind CSS Styles

This pull request introduces a new home page to the project along with the integration of Tailwind CSS styles. The home page provides a basic structure with navigation links and buttons styled using Tailwind CSS.
Changes Made

Added a new home page file (pages/home.astro) with essential content.
Integrated Tailwind CSS to enhance styling and responsiveness.
Updated the navigation links and buttons for a cohesive design.

Screenshots

Checklist

[x] Home page added
[x] Tailwind CSS styles integrated
[x] Code reviewed and tested locally

i

add header and icons


open-webui: 0.3.20 -> 0.3.21

Diff: https://github.com/open-webui/open-webui/compare/refs/tags/v0.3.20...0.3.21
Changelog: https://github.com/open-webui/open-webui/blob/refs/tags/v0.3.21/CHANGELOG.md
Description of changes

Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

This is not working for me, have you tested it before merge ?


Confusing behavior of uvx and uv tool paths.

I'm trying to convert from pipx to uvx, but running into some confusion about how the commands should work.
% uv --version
uv 0.4.25 (Homebrew 2024-10-21)

I am using /bin/bash on macOS 14.7
I wrote a little script called world which looks up country codes.  If I install this with pipx, it gets put in my ~/.local/bin directory, which I can put on my $PATH and then can invoke directly instead of through pipx.  If I try to do something similar with uvx, I get some confusing behavior.  This might be intended behavior but for someone moving from pipx to uvx it feels like friction.
% uvx world it
Installed 2 packages in 3ms
it originates from Italy
% uvx world de
de originates from Germany

So far so good.  However, uv tool list doesn't show that world is installed:
% uv tool list
No tools installed

I'd also like to be able to invoke world directly, which I assumed would be possible if uvx's bin directory were on my $PATH, but this doesn't work:
% uv tool dir --bin
/Users/mylogin/.local/bin
% uv tool update-shell
Executable directory /Users/mylogin/.local/bin is already in PATH
% world fr
-bash: world: command not found
% ls -l $(uv tool dir --bin) | grep world
%

If I install the tool before trying to run it though, it works in the obvious ways:
% uv tool install world
Resolved 2 packages in 293ms
Installed 2 packages in 6ms
 + atpublic==5.0
 + world==5.1.1
Installed 1 executable: world
% world it
it originates from Italy
% uv tool list
world v5.1.1
- world
% ls -l $(uv tool dir --bin) | grep world
lrwxrwxr-x  1 mylogin  staff  50 Oct 22 09:49 world@ -> /Users/mylogin/.local/share/uv/tools/world/bin/world

It almost seems like the default behavior for uvx is to run with the --isolated flag enabled by default.

Yes, uvx does not install a tool by design — it uses an isolated environment.

(uvx is equivalent to uv tool run which is roughly equivalent to pipx run which also does not install the tool in your bin directory)

I had a feeling this was working by design, thank you for confirmation!
My only suggestion to resolve this ticket is to add some documentation to clarify that uvx/uv tool run uses isolated environments by default, and that if you want to put the tool in your uv tool dir --bin directory and have uv tool list show it is to uv tool install first.
This is especially useful for tools where you need the uvx --from flag, e.g. pepotron but don't if you uv tool install first, e.g. v tool run --from pepotron pep.
Thanks!

This is especially useful for tools where you need the uvx --from flag, e.g. pepotron but don't if you uv tool install first, e.g. v tool run --from pepotron pep.

Yeah this actually sort of incidental, in that we only check if the requested binary belongs to the package if it fails — so you can do things like uvx --from black bash -c "black".

My only suggestion to resolve this ticket is to add some documentation to clarify that uvx/uv tool run uses isolated environments by default, ...

I'm planning on doing some documentation work this week, I'll try to roll this into that.

I think it's consistently confusing that uvx doesn't just mean uv tool
It seems more intuitive than for it to only mean uv tool run, making it a niche shorthand.
I try to remember that uvx is not a thing as to not mess up my commands


#112 Adjust for new syntax

#112 Adjust for new syntax

@yegor256 please merge

@rultor merge

@rultor merge

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

@rultor merge

@yegor256 Done! FYI, the full log is here (took me 12min)


update echo to 3.2.1

hi!
Im adapted because the Echo version has gone up and the interface has changed.

Many thanks :)


[CC scenario] one of capture has not any table to sync

What did you do?

Testbed: 8 captures deployed in 4 physical servers; 1 changefeed; upstream TiDB cluster: 6 TiKV 2 TiDB, 3 PD; downstream cluster: 3 TiKV, 1 TiDB, 1 PD; CDC & TiKV numa_node binded; each physical server has: CPU 40-48C, 188GB memory, 2 NVME 3.6TB; 10GB/s NIC

Upstream and downstream cluster already have 5.6TB data size before the changefeed creating.

Run workload run phase: ./bin/go-ycsb run mysql -P workloads/betting -p operationcount=5000000000 -p mysql.host=<IP_ADDRESS> -p mysql.port=4000 --threads 200 -p dbnameprefix=betting_ -p databaseproportions=1.0 -p unitnameprefix=unit1_ -p unitscount=10 -p tablecount=20

Because there's not storage.tikv.cache setting (two TiKV deployed in one server), there's two TiKV  OOM which is expected.

What did you expect to see?
cdc works fine.
What did you see instead?

one of capture has not work for any table, and lasted for 10 hours after I reboot cluster.

Versions of the cluster
Upstream TiDB cluster version (execute SELECT tidb_version(); in a MySQL client):
v5.4.0-nightly-20211213

TiCDC version (execute cdc version):
cdc-cloud-cdc-b82eb4f05-2021-12-16-15-59.tar.gz

Fixed by https://github.com/pingcap/tiflow/pull/3916


Settings: Added descriptions for better clarity.

I have added descriptions to the addon settings for better clarity for the users.
This PR resolves this issue: https://github.com/ynput/ayon-blender/issues/55
Testing steps:

Build ayon-blender addon package and upload to AYON
Set it to bundle and go through the settings categories and check description additions

Thanks for your input guys, I have also another thing to discuss...
I was trying to incorporate "hoover over tips" mostly but due to my very limited python knowledge (basically non existing :D ) I wasnt able to produce those all the time so they got into those headers most of the time which makes the settings UI a bit busy for my taste...
It would be more than welcome to make a suggestion / example how to treat those as hoover over mostly and not been visible as this:

I think it could be much more prefered to see those just when hoovering by cursor over the actual settings knobs - but not been able to resolve it myself.
What u think? If agreed, any help much appreaciated!


Southern cross practice day changes

Codecov Report

Merging #68 into master will decrease coverage by 0.1%.
The diff coverage is 84.21%.

@@            Coverage Diff             @@
##           master      #68      +/-   ##
==========================================
- Coverage   85.93%   85.82%   -0.11%
==========================================
  Files          20       20
  Lines        1372     1376       +4
  Branches      128      129       +1
==========================================
+ Hits         1179     1181       +2
- Misses        160      162       +2
  Partials       33       33

Impacted Files
Coverage Δ

pyswervedrive/chassis.py
100% <ø> (ø)
:arrow_up:

components/climb.py
79.62% <0%> (ø)
:arrow_up:

utilities/pure_pursuit.py
86.98% <100%> (ø)
:arrow_up:

components/hatch.py
100% <100%> (ø)
:arrow_up:

pyswervedrive/module.py
91.08% <100%> (+0.05%)
:arrow_up:

automations/alignment.py
56.71% <100%> (ø)
:arrow_up:

autonomous/autonomous.py
64.7% <100%> (+0.7%)
:arrow_up:

robot.py
77.35% <66.66%> (-0.57%)
:arrow_down:

Continue to review full report at Codecov.

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


'graphcool deploy help' will deploy project

When entering 'graphcool deploy help' instead of 'graphcool help deploy' to get help on the command no error is given but the project is deployed. There should be an error thrown for wrong usage of the deploy command. For other extra arguments than help an error is produced.

Also the error message for other arguments after deploy says deploy is not a command.

This issue was moved to graphcool/graphcool-cli#238


Ambiguous error message when parsing JSON during eject

Description
When trying to eject app to "Native" syntax error is thrown and ejection process exits.
Expected Behavior
answer all questions in process, then native app is ejected properly.
Observed Behavior
After being asked what type of ejection I want to run (native vs expo), syntax error is thrown and process exits
If there's an error message, please paste the full terminal output and error message in this code block:
Error running eject: SyntaxError: Unexpected token } in JSON at position 487

Environment
Please run these commands in the project folder and fill in their results:

npm ls<EMAIL_ADDRESS>npm ls react-native<EMAIL_ADDRESS>npm ls expo<EMAIL_ADDRESS>node -v: 7.8.0
npm -v: 4.2.0
yarn --version: 0.19.1
watchman version: 4.7.0

Also specify:

Operating system: OSX 10.12.5
Phone/emulator/simulator & version: iOS iPhone 7 sim 10.3

new project works fine

Hi! Thanks for the report! Which option did you choose to eject?

I am trying to eject to a "raw" native app.  If I knew what JSON it was referring to I could look specifically to try an fix, but I couldn't find anything with a issue that I could see.  Thanks for the quick response!

Can you paste the contents of app.json and package.json?

app.json
{   "expo": {     "sdkVersion": "15.0.0",     "icon": "./img/logo.png",     "slug": "Logo",     "loading": {       "hideExponentText": true,       "icon": "./img/loading.png",       "backgroundImage": "./img/logo.png"     },     "orientation": "portrait",     "primaryColor": "#cccccc",     "packagerOpts": {       "assetExts": [         "ttf"       ]     },     "ios": {       "supportsTablet": true,       "bundleIdentifier": "com.onepxoff.test",     },     "android": {       "package": "com.onepxoff.test",     },     "androidStatusBarColor": "#EEE",     "androidStatusBar": {       "barStyle": "dark-content",       "backgroundColor": "#EEE",     }   }

I actually think I just figured it out, however I think this is a problem that could be more clear in the error.
I opened the json file in another editor and it showed me some "errors" with the json.  basically the trailing , on lines like "bundleIdentifier": "com.onepxoff.test" are causing technically invalid json

Ah, yeah, that'll do it. I don't think we're parsing using json5. I agree the error message could be much clearer, I've updated the issue title to reflect that.

thanks for the help. I was able to eject the app now. Not sure if you want to close this issue or keep it open to help clear up the error message.

Let's leave it open, I'd like to improve this!

I am getting this error while eject project with expo-sdk.

Error running eject: SyntaxError: Unexpected token } in JSON at position 805

hi, I just got the exact same error and removing a trailing comma, like @n8stowell82  suggested, fixed the issue.

also got this error, and fixed by removing trailing comma of app.json

@anp would you accept a PR using https://github.com/json5/json5 for safer parsing? Or wrapping the parse calls and throwing more contextual exceptions?

I don't really see a downside to that, cc @fson.

It would be enough to change the eject functionality to use XDL.ProjectUtils.readConfigJsonAsync instead of doing raw JSON.parse like it does now. This function in XDL uses this library https://github.com/expo/json-file for parsing JSON files. It uses the json5 parser and also throws contextual syntax errors.


Plotly download png does not work in interactive/notebook scenario

Used to be plotly gave us an href with the png in it, now they return this:
blob:null/5c84fc27-a2c2-4512-af71-d2cfb58cba1f

Not sure how this works in a notebook either, but we can't save the image anymore.

Cause:

Here elem.className is not a string.
if (!elem.className.includes('image-button')) {


CI fails for py33

I have Travis CI cron job set for my fork of swidGenerator repo. Lately, the tests fail for master (== 0d0941d261925cc01638e88df748c0f2c4395131) for the Python: 3.3: https://travis-ci.org/adelton/swidGenerator/builds/428317519 with error
$ tox
Traceback (most recent call last):
  File "/home/travis/virtualenv/python3.3.6/bin/tox", line 7, in <module>
    from tox import cmdline
  File "/home/travis/virtualenv/python3.3.6/lib/python3.3/site-packages/tox/__init__.py", line 10, in <module>
    from pkg_resources import DistributionNotFound, get_distribution
  File "/home/travis/virtualenv/python3.3.6/lib/python3.3/site-packages/pkg_resources/__init__.py", line 90, in <module>
    raise RuntimeError("Python 3.4 or later is required")
RuntimeError: Python 3.4 or later is required

Something has likely changed somewhere external to swidGenerator because the same commit passed a month ago, both in my clone https://travis-ci.org/adelton/swidGenerator/builds/413453444 and in upstream: https://travis-ci.org/strongswan/swidGenerator/builds/412677830

Probably related to 9da44c927cbe05bee032f5f9996288d12f3ce0c2 somehow.

I pushed a fix to the 50-hierarchic-root branch, which removes support for Python 3.3 (which was EOL for over a year) and adds testing with Python 3.7. The docker images used for the integration tests I've updated accordingly (see https://github.com/strongswan/swidGenerator-dockerimages).


i am getting this error plz fix it as sooon as possible

─(kali㉿windows)-[~/Desktop]
└─$ hashcat -m 22000 capture.hccapx pass
hashcat (v6.2.5) starting
OpenCL API (OpenCL 2.0 pocl 1.8  Linux, None+Asserts, RELOC, LLVM 11.1.0, SLEEF, DISTRO, POCL_DEBUG) - Platform #1 [The pocl project]

Device #1: pthread-Intel(R) Core(TM) i3-7020U CPU @ 2.30GHz, 708/1480 MB (256 MB allocatable), 4MCU

Minimum password length supported by kernel: 8
Maximum password length supported by kernel: 63
Hashfile 'capture.hccapx' on line 1 (HCPX): Separator unmatched
Hashfile 'capture.hccapx' on line 2 (): Separator unmatched
No hashes loaded.
Started: Thu Dec  7 08:20:45 2023
Stopped: Thu Dec  7 08:20:52 2023

Does the hccapx file contain any data?

hccapx (binary) is deprecated and has been replaced by the new format 22000 (ASCII).
Specification is here:
https://hashcat.net/wiki/doku.php?id=cracking_wpawpa2

Probably u will need to try 4 to 5 times after that u will be able to see hccapx that issue happened with me too also ensure the proximity of esp and the AP is less


Integrating Javascript business logic into Flutter App

Is it possible to integrate business logic written in Javascript, with a Flutter app?
We use a Redux style business logic layer in our enterprise web app; We cannot afford to write this logic in two separate languages.
Would it be possible to run a Javascript thread on the V8 engine, inside a Flutter app? Then, the flutter app would talk to the business logic via a simple interface, with flutter taking the responsibility of much of the UI / navigation, leaving the responsibility of the app logic to the shared business layer?
We are deciding whether or not to go with a React Native implementation. Right now, that's the only platform which can support this code sharing scenario. We'd be interested in Flutter if it were possible to share Javascript business logic.

At this point Flutter is only Dart; however one potential work around is that you could technically embed the Node engine into Flutter as a plugin.   This will give you an additional thread that runs JavaScript on iOS and Android, so you could basically do something like Node.Run("jscode()").
I haven't actually tried this with Flutter, but I did create a plugin to do it with NativeScript, so I do believe it should be very possible to do this in Flutter.    (NativeScript; is also a JavaScript based system that would also support code sharing JavaScript just like RN, so don't limit yourself to just RN.)

You could also run JavaScript in a WebView https://github.com/dart-flitter/flutter_webview_plugin
but Dart itself has no JavaScript capabilities, it can just be compiled to JavaScript to be run in the browser (or Nodejs).


Port candidate fix for https://github.com/microsoft/vscode-jupyter/issues/7031

Codecov Report

:exclamation: No coverage uploaded for pull request base (release-2021.08@63d2d4b). Click here to learn what that means.
The diff coverage is n/a.

@@                Coverage Diff                @@
##             release-2021.08   #7082   +/-   ##
=================================================
  Coverage                   ?     65%
=================================================
  Files                      ?     410
  Lines                      ?   28525
  Branches                   ?    4263
=================================================
  Hits                       ?   18553
  Misses                     ?    8336
  Partials                   ?    1636


import * as Contentful from "contentful"; produces error

This import is never used as a value and must use 'import type' because 'importsNotUsedAsValues' is set to 'error'.ts(1371)
In the generated files it should import contentful only as a type because if 'importsNotUsedAsValues' is set to error then it produces an error.
Should be: import type * as Contentful from "contentful";

Hi @AndrisBorbas,
thanks for the callout - would you be able to create a PR for that?

Hi, sorry for the late reply, just noticed it. I tried looking into the code, but I couldn't find where that line gets generated.

Hi @AndrisBorbas
I have re-worked they way imports are generated. The PR is currently in review, maybe we want to have a look. Any comments are welcome :)
#205


Replace "kale" with "skala" as an argument to --backend

@cos  can you make sure this is still correct and lets get it merged?

We can change it from skala to scala here, but this looks like just a comment. It's not clear exactly what we'd have to change in order to correctly rename it to scala. For example, are there other repositories like kale or kore that depend on the name skala? Feel free to open up another pull request and change it to scala everywhere needed, but if it's ok with you we'd like to just get this merged as is.

Merging, we can re-name it again later if needed. It looks like renaming it will require more work than just changing things in this repository.


[Accessibility] Multiple issues causing poor accessibility user experience.

My team’s application needs to be WCAG compliant and we are using the Plyr library to meet various accessibility requirements for our audio player. Since the adoption of Plyr in our app, there have been several reviews on it from accessibility experts and a few concerns have been raised. I’d like to give these concerns some visibility and provide suggestions to get them addressed. I apologize if there is some overlap here with other issues, I did look through the other accessibility related ones and was not able to find any others that have the same needs as us. Although there may be a few conflicts with: https://github.com/sampotts/plyr/issues/905
Some additional background info on our app:

It is expected to be accessible on Chrome and Firefox using the JAWS screen reader tool which is only available on Windows.
Our application has more fine-tuned accessibility requirements in the sense that our users are more sensitive to information overload, many of them are children.

Audio Player Progress Bar Slider
1 - The issue we are facing with the audio progress slider is: When the audio is playing and the progress slider is tab-focused or focused with the virtual cursor, the current time is being constantly announced to the screenreader user. This is a problem for us because it is overloading the user with information that they do not want to hear continuously.

Proposed Solutions:

Adding a single flag to make the aria-valuenow, aria-valuemax, aria-valuenow, and aria-valuetext conditional or a flag for each one?
Have the attributes get updated/announced in set intervals, the interval being passed in as a prop.

I understand that the default screenreader behavior for this scenario is to constantly announce the elapsed time and that this requirement is something that is specific to our needs, but would like to know whether you are open to these changes to avoid forking.
2 - The aria-valuemax attribute is being read out by the screenreader as a large number since this value is the total duration in seconds. If we can implement the conditional property defined in 1) then this would be resolved. Right now we are deleting this attribute on load, but this is not an ideal solution.
Audio Player Current Time
The Current Time text is being read as 3 o’clock for an innerText value of 3:00. In order to fix this, we would most likely need to add some visually hidden text with the numbers separated by commas then add an aria-hidden to the element, much like what is being done here https://github.com/bbc/simorgh/issues/2996

Following.

Just want to add that it's relatively to hack plyr 'from the outside' - I mean, you can, with a short, independent javascript, set an aria-label into plyr's timecode element, which may perform any clever string substitutions, and keep those substitutions in sync with plyr's on-screen timecode using (e.g.) timeout or setinterval, without plyr breaking down. One of the many reasons I like plyr is that it is so tolerant of hacks like these, and that's mainly because plyr
But again, please study the caveats in my previous post before you do this!


CLEANUP: Remove xml module usage in objectGetAcl api

Fix #285

Generate the XML DOM with a function instead of constructing
a JSON object with aclUtils.constructGetACLsJson and then
using the xml module

@ironman-machine go

Hello @bennettbuchanan
Starting end to end procedure using the following payload:
{"REPO_NAME": "S3", "SCALITY_S3_BRANCH": "dev/CLEANUP/remove_xml_module_objectGetAcl", "DEFAULT_BRANCH": "master"}
Please follow http://ci.ironmann.io/gh/scality/Integration/5469 for CI status.

This function can apply across both objectGetACL and bucketGetACL APIs. Thus it will be moved to aclUtils.js. The change will be opened in a new pull request.


Exception has occurred: IndentationError

This occurs after typing $settings, or well anything after starting the bot

to many spaces then so try to align the spaces
On Fri, Oct 14, 2022 at 8:26 AM XLThinOreos1 @.***>
wrote:

[image: bild]
https://user-images.githubusercontent.com/111511159/195846251-24dff546-8586-48ae-b068-98132e61ba0d.png
Line 407
m = resp.parsed.auto()
unexpected indent
How do I fix this?
—
Reply to this email directly, view it on GitHub
https://github.com/vivinano/MudaeAutoBot/issues/209, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AH32WDOMAARXC5RJCN4OR2LWDFGOTANCNFSM6AAAAAARFGFNSY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

to many spaces then so try to align the spaces

I have not modified your code whatsoever and I am not really sure why this is happening. Everything is aligned as it should without causing any errors

Based on what you provided to me that is the only answer I can provide

Based on what you provided to me that is the only answer I can provide

What can I show that could be helpful?

Well I would say just redownload the files and try again probably for the best to fix a indention error

Well I would say just redownload the files and try again probably for the best to fix a indention error

Reinstalling discum fixed the problem but then the notorious "KeyError 'user' " showed up.


[SPARK-39063][CORE]  Fix potential risk of JVM crash and RocksDBIterator resource leak

What changes were proposed in this pull request?
There is lock contention between RocksDBIterator.finalize() and RockDB.close() method. If RocksDB.close() method is executed first, the RocksDBIterators hold by Finalizer will not close before the RockDB close.
If user use a rocksdbjni compile with DEBUG_LEVEL=1 to enables all assertions of rocksdbjni(official rocksdbjni compile with DEBUG_LEVEL=0 and diabled all assertions), above issue will lead to JVM crash.
So this pr try to use a custom ReferenceQueue + cleanupThread instead of Finalization mechanism to automatically clean up RocksDBIterator resources that are not explicitly closed in Spark code and solve the issue mentioned above.
Why are the changes needed?
Fix potential risk of JVM crash and RocksDBIterator resource leaks caused by lock contention.
Does this PR introduce any user-facing change?
No
How was this patch tested?

Pass GA and add a new test to check all RocksDBIterator not explicit closed
Manual test：

Compile a rocksdbjni with DEBUG_LEVEL=1 ref to https://github.com/facebook/rocksdb/wiki/RocksJava-Basics and modify pom.xml as follows:

<dependency>
  <groupId>org.rocksdb</groupId>
  <artifactId>rocksdbjni</artifactId>
  <version>7.0.3</version>
  <scope>system</scope>
  <systemPath>/${basepath}/rocksdb/java/target/rocksdbjni-7.0.3-osx.jar</systemPath>
</dependency>

Run test cases testCloseRocksDBIterator and testAllRocksDBIteratorNotExplicitClosed in kvstore.RocksDBSuite:

mvn clean install -DskipTests -pl common/kvstore -am
mvn test  -pl common/kvstore -Dtest=org.apache.spark.util.kvstore.RocksDBSuite#testCloseRocksDBIterator
mvn test  -pl common/kvstore -Dtest=org.apache.spark.util.kvstore.RocksDBSuite#testAllRocksDBIteratorNotExplicitClosed

Before
All UTs lead JVM crash as follow:
[ERROR] Error occurred in starting fork, check output in log
[ERROR] Process Exit Code: 134
[ERROR] Crashed tests:
[ERROR] org.apache.spark.util.kvstore.RocksDBSuite

Key error message as follows:
Assertion failed: (last_ref), function ~ColumnFamilySet, file db/column_family.cc, line 1494.

After
All test passed

Just for test now

https://github.com/apache/spark/pull/36403#issuecomment-1114466277

@dongjoon-hyun
After SPARK-38896, I think all LevelDB/RocksDBIterator has been explicitly closed in Spark code, so I want to clean up the code related to finalize() in LevelDB/RocksDBIterator to avoid the negative impact of Finalization:

As described in https://github.com/apache/spark/pull/36403#issuecomment-1114466277,  there is lock contention between the code to be executed through Finalizer and the RocksDB.close() method. If the RocksDB.close() method is executed first, the RocksDBIterators hold by Finalizer  cannot be closed before the DB close. if use a rocksdbjni without link jemalloc(The official rocksdbjni will linked jemalloc),  the above issue will lead to vm crash and it can be reproduced by testCloseRocksDBIterator in RocksDBSuite.
Others: JEP 421: Deprecate Finalization for Removal

But it seems that we still need finalize() to ensure that RocksDBIterator has a chance to be closed which is not explicitly closed in Spark code at present, so in the current pr, I try to use a custom ReferenceQueue + cleanupThread instead of finalize()

The issue will not cause vm crash when using the official release rocksdbjni, so if it's not worth fixing, I can close this pr .

Description of DEBUG_LEVEL as follows:
https://github.com/facebook/rocksdb/blob/7b55b508390d792ff31a416b63d474a2a6780588/Makefile#L31-L42
# DEBUG_LEVEL can have three values:
# * DEBUG_LEVEL=2; this is the ultimate debug mode. It will compile rocksdb
# without any optimizations. To compile with level 2, issue `make dbg`
# * DEBUG_LEVEL=1; debug level 1 enables all assertions and debug code, but
# compiles rocksdb with -O2 optimizations. this is the default debug level.
# `make all` or `make <binary_target>` compile RocksDB with debug level 1.
# We use this debug level when developing RocksDB.
# * DEBUG_LEVEL=0; this is the debug level we use for release. If you're
# running rocksdb in production you most definitely want to compile RocksDB
# with debug level 0. To compile with level 0, run `make shared_lib`,
# `make install-shared`, `make static_lib`, `make install-static` or
# `make install`

If DEBUG_LEVEL=1
https://github.com/facebook/rocksdb/blob/b7119ff818f83b54a46602ac1f23d4fe2add1bfc/db/column_family.cc#L1488-L1495
ColumnFamilySet::~ColumnFamilySet() {
  while (column_family_data_.size() > 0) {
    // cfd destructor will delete itself from column_family_data_
    auto cfd = column_family_data_.begin()->second;
    bool last_ref __attribute__((__unused__));
    last_ref = cfd->UnrefAndTryDelete();
    assert(last_ref); // this assert will lead jvm crash
  }

Finally, is this ready for review, @LuciferYang ? :)

Yes, can you help to review this? @dongjoon-hyun

I want this pr to focus on RocksDB first, so LevelDB is not changed not in this pr

I want this pr to focus on RocksDB first, so LevelDB is not changed not in this pr

Can we proceed LevelDB first because it's enabled by default? RocksDB is not used by default and it's not tested widely.

I want this pr to focus on RocksDB first, so LevelDB is not changed not in this pr

Can we proceed LevelDB first because it's enabled by default? RocksDB is not used by default and it's not tested widely.

LevelDB can only be explained theoretically, but I can't reproduce it manually now. Is this acceptable ...

Let me give a LevelDB pr first

@dongjoon-hyun LevelDB one: https://github.com/apache/spark/pull/36484

This seems like a well thought-out change, though it's complex compared to the issue it's trying to solve - a setting of a non-default third party library. I'm neutral about bothering with it if 'normal' rocksdb does not have this issue.

I have not looked into this in great detail, but why not simply return a boolean from notifyIteratorClosed to indicate if the underlying db has been closed or not ?
This can be used to determine if the iterator needs to be closed ? This is similar to what closeIterator does in RocksDb (for example)

I have not looked into this in great detail, but why not simply return a boolean from notifyIteratorClosed to indicate if the underlying db has been closed or not ? This can be used to determine if the iterator needs to be closed ? This is similar to what closeIterator does in RocksDb (for example)

The issue to be solved is:
Ensure all RocksDBIterators are clsoed before the RocksDB is closed, otherwise the JVM will crash when use a rocksdb with debug mode enable

The issue to be solved is: Ensure all RocksDBIterators are clsoed before the RocksDB is closed, otherwise the JVM will crash when use a rocksdb with debug mode enabled.

This is already handled by iteratorTracker, right ?
RocksDB.close() already iterates over all RocksDBIterator and closes them before closing itself.

The issue to be solved is: Ensure all RocksDBIterators are clsoed before the RocksDB is closed, otherwise the JVM will crash when use a rocksdb with debug mode enabled.

This is already handled by iteratorTracker, right ? RocksDB.close() already iterates over all RocksDBIterator and closes them before closing itself. (This will also mean that it.close within db.close will need to handle the corner case - pass a forceClose even if notifyIteratorClosed returns false)

If the definition of iteratorTracker is changed from ConcurrentLinkedQueue<Reference<RocksDBIterator<?>>> to ConcurrentLinkedQueue<RocksDBIterator<?>> , then you are right.
However, iteratorTracker holds RocksDBIterator WeakReference now, so it doesn't hold all unclosed RocksDBIterator due to JVM GC, some RocksDBIterator will be held by the JVM Finalizer thread. We cannot interfere with the running state of Finalizer, so there is no guarantee that all not closed RocksDBIterator in Finalizer have been closed before RocksDB.close is executed. At the same time, The thread executing RocksDB.close() and Finalizer thread need the same lock, so if RocksDB.close() executes first, pending db.closeIterator(this) in Finalizer can only wait.

If the definition of iteratorTracker is changed from ConcurrentLinkedQueue<Reference<RocksDBIterator>> to ConcurrentLinkedQueue> , then you are right.

It should not need change types.
In the current code, ConcurrentLinkedQueue<Reference<RocksDBIterator<?>>> allows us to keep a reference to the RocksDBIterator, without holding a strong reference to it (so it can be gc'ed if there are no other references to it).
To sketch a possible solution:
RocksDBIterator:
public synchronized void close() throws IOException {
  close(false);
}

// accessible from RocksDB
void close(boolean forceClose) {
  if (db.notifyIteratorClosed(this) || forceClose) {
    if (!closed) {
      it.close();
      closed = true;
    }
  }
}

RocksDB:
In close() : call it.close(true), instead.

For notifyIteratorClosed:
// return true if DB is still open
boolean notifyIteratorClosed(RocksDBIterator<?> it) {
  iteratorTracker.removeIf(ref -> it.equals(ref.get()));
  return _db.get() != null;
}

@dongjoon-hyun @srowen @mridulm Thanks for your review. I will close this pr


Feat: Get codebase more inline with a flat layout

As recommended by @Digitalone1 instead of having endless nested functions, with error checking tailing success logic, place error logic at the lead, and get the codebase more flat. Similar to what's seen within package_handler.POSTPackages()

It looks like @Digitalone1 has done a fantastic job contributing to this goal. And while still some locations may be needlessly deep in indents, in general the codebase is significantly easier to read and maintain. As such, I will go ahead and close this issue.


feat: add restructuredtext support

I want to add support for reStructuredText (rst) files.
I have the basic query working, it recognizes the language and extracts the code.
But there is some trouble with the indents.
I'll need to strip the indent before going to the formatter (black seems to fail on this) and re-apply them on the result.
Currently a test rst file:
########
test
########
.. code:: lua

  local bar = require 'bar'
    bar.setup {
      foo = {},
      baz = { 'aa', 'bb' },
    }

results in:
########
test
########
.. code:: lua

local bar = require 'bar'
bar.setup {
  foo = {},
  baz = { 'aa', 'bb' },
}
    }

So, still some work to be done, but I already wanted to get some feedback or input before continuing.
This is also my first foray into rust.
I had to fork tree-sitter-rst to upstep tree-sitter to 0.20 and add the scanner.c code to the lib. I'll try to get that merged, but I can continue from the forked repo for now.

No worries, I have time.
Good luck with the new job.

The upstep PR was merged and I updated the url in cargo.
Would you prefer to pin the current revision (since there is no crate for it)?

since there is no crate for it

Sorry this is required now. I published cbfmt to crates.io, and they require all dependencies to be hosted there as well.
Can we ask @stsewd to publish tree-sitter-rst? :pray:

They will publish it. Once it's done I'll rebase and ping you again.

Updated and rebased.

I think something went wrong with the rebase :thinking: this is an old version of the PR

I used the wrong workspace to rebase in. Fixed now.


Navigation on content by links in PDF.

The Pdfium supported the the definition of links on a page that is very convenient to navigate through content.
I think it can be done by determining the list of rectangles of the links on the corresponding page.
I've written the following code that returns the associative array with areas (rectangles) on page and appropriate link address (page numbers):
        private Dictionary<Rectangle, int> GetLinks(IntPtr document, IntPtr page, double width, double height)
        {
            Dictionary<Rectangle, int> linckAreas = new Dictionary<Rectangle, int>();

            int startPos = 0;
            IntPtr linkAnnot;

            while (NativeMethods.FPDFLink_Enumerate(page, ref startPos, out linkAnnot))
            {
                IntPtr pdfDest = NativeMethods.FPDFLink_GetDest(document, linkAnnot);

                if (pdfDest == IntPtr.Zero)
                    continue;

                int index = (int)NativeMethods.FPDFDest_GetPageIndex(document, pdfDest);

                NativeMethods.FS_RECTF rect = new NativeMethods.FS_RECTF();
                _RectCallbacksHandle = GCHandle.Alloc(rect);

                if (NativeMethods.FPDFLink_GetAnnotRect(linkAnnot, out rect))
                {
                    int deviceX, deviceY;

                    NativeMethods.FPDF_PageToDevice(page, 0, 0, (int)width, (int)height,
                        0, rect.left, rect.top, out deviceX, out deviceY);
                    linckAreas.Add(
                        new Rectangle(deviceX, deviceY, (int)(rect.right - rect.left),
                        (int)(rect.top - rect.bottom)), index);
                }
            }

            return linckAreas;
        }

Could you help me embed this logic into your project?

This has been implemented. I've also added support for URI's.


[docs] Add more instructions on how to opt-in/out to stats usage.

The Problem/Issue/Bug:
Clarify the exact setting to use to opt-in/out to stats usage.
How this PR Solves The Problem:
Adds instructions.
Manual Testing Instructions:
Automated Testing Overview:

Related Issue Link(s):
Release/Deployment notes:

Thanks - looks good to me. I'd be interested to know what prompted you to explore this territory and whether it was hard to figure out.

I was helping configure ddev to run in codespaces and saw the prompt was hanging the script, and ended up following the link at the prompt and noticed that was confusing because it said where to set it but not what to set.

I hope you'll contribute back your codespaces work. I've spent some time with that and was successful, but didn't want to completely go down that rabbit-hole.
Note that if you don't want any interruptions of this type, use ddev start -y.

I hope you'll contribute back your codespaces work. I've spent some time with that and was successful, but didn't want to completely go down that rabbit-hole.
Note that if you don't want any interruptions of this type, use ddev start -y.

Thanks, I didn't think to try ddev start -y, maybe I'll do that instead.
Work will be public after this is merged https://github.com/department-of-veterans-affairs/va.gov-cms/pull/9401.


Not able to find Modules window in visual studio 2017

As per document in my visual studio Debug > Windows > Modules, this option is not available. Where can I find the Modules window.

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

ID: b7bd93e4-509f-6fb9-594e-820d62c03479
Version Independent ID: 2453d9ef-4bb3-91bc-820f-cd59d589ca0f
Content: View DLLs and executables - Visual Studio Modules window
Content Source: docs/debugger/how-to-use-the-modules-window.md
Product: visual-studio-windows
Technology: vs-ide-debug
GitHub Login: @Mikejo5000
Microsoft Alias: mikejo

I am able to see the Modules window now.


chore(package): update semantic-release to version 15.9.14

Fixes #76

Coverage remained the same at 100.0% when pulling cb5354aaddeff5285d4807daf7882f660baf394a on greenkeeper/semantic-release-15.9.14 into c98c539aca7094145961d1a6e128071bb31ea83a on master.

Coverage remained the same at 100.0% when pulling cb5354aaddeff5285d4807daf7882f660baf394a on greenkeeper/semantic-release-15.9.14 into c98c539aca7094145961d1a6e128071bb31ea83a on master.

Coverage remained the same at 100.0% when pulling cb5354aaddeff5285d4807daf7882f660baf394a on greenkeeper/semantic-release-15.9.14 into c98c539aca7094145961d1a6e128071bb31ea83a on master.

Coverage remained the same at 100.0% when pulling cb5354aaddeff5285d4807daf7882f660baf394a on greenkeeper/semantic-release-15.9.14 into c98c539aca7094145961d1a6e128071bb31ea83a on master.

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Feat] Support for binary and scalar embedding quantization

Limitations
Current supported types for HNSW are FLOAT32 and FLOAT64.
Feature Request
Support for binary and scalar embedding quantization(https://huggingface.co/blog/embedding-quantization) using HNSW.

Support for FP16 and BFLOAT16 is coming very very soon.


docs: update deployment guide

@pbabinca since you wrote the NFS part, I would like to author the commit on your behalf, would you mind that?

NFS part looks like my docs. Feel free to commit it in my name.

How does this PR relate to #157?

not at all actually, I just wanted to open source our internal docs; that's what this PR is about

Merging this into #158


Fixes #3059 - Reset task's delay only after viability threshold has been reached

@FlorentFlament  Thanks for the PR! I added a few comments, but in general it looks very good to me =).
@kolloch is much more familiar with this part of Marathon, so I would feel more confident if he would look over the PR before merging it.

Hi, any news on this PR ?

@aquamatthias and @meichstedt   This looks pretty good to me, I can handle getting it up to date. Any thoughts?

Can one of the admins verify this patch?

Can one of the admins verify this patch?

@jasongilanfarr I agree - please proceed.

Can one of the admins verify this patch?

Hi,
I just rebased this on master and (hopefully) solved the conflicts.
We use this patch since 0.13 (was cherry-picked on our side for 0.14.0, 0.15.0, 0.15.3, 1.1.1, 1.3.0)

Solved newly introduced conflicts.
Don't really know if this was addressed by another commit at some point.

ok to test

Thanks @FlorentFlament and sorry for the (too) long time to handle this PR!
Since this change did not compile any longer - I took the liberty to cherry pick your commit and put the necessary changes on top as a separate commit. See #4915


VSCode Plugin Not Detecting Home Directory

Description:
When there is a space in a user's home directory (for example, mine was "SamWeeras 1"), the VSCode plugin doesn't automatically detect Ballerina home. Output can be seen in the below image:

Steps to reproduce:
Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

As per the output log, this seems to be a CLI issue when executing ballerina home command.

Closing along with #27


az aks get-credentials: FAILURE

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az aks get-credentials
Errors:
Paste here the error message you have received. Make sure to remove all sensitive information,
such as user name, password, credential, subscription ID, etc.

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az aks get-credentials --resource-group {} --name {}

Expected Behavior
Environment Summary
Windows-10-10.0.17763-SP0
Python 3.10.10
Installer: MSI

azure-cli 2.46.0

Additional Context

Thank you for opening this issue, we will look into it.

@4021019 Can you please provide us the error message you are getting. Thanks

@4021019 Please let me know if you need any help on this one.  If yes, please provide us the debug log to investigate further.

@4021019 We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


Applescript "thumbs up" shouldn't be a toggle

The suggestion on issues like #159 is that the user map keys to Applescript, eg.
tell application "Hermes" to thumbs up

The only problem with this particular command is that it operates just like pressing the menu bar button, which is actually a toggle.  The toggle works on the menu bar because the user can see the current state, but an Applescript is much more likely to be run blindly; the result is that this often results in the current song being de-liked instead.
This is pretty easily fixable in Applescript like
tell application "Hermes"
    if the current song's rating is not 1 then thumbs up
end tell

but it's not obvious from the outset that this is necessary, and it seems like this check should really be in the application's Applescript handler anyway.

@corypina Your solution works like a charm. Maybe documenting this will help

Agreed — don't think that changing the semantics of the existing scripting command is a good idea, but both the rating and the “thumbs up” command are better documented now.


Fix issues with timeout

@braposo Greeting! let me know if you need any further description on this PR.

Hi @kenime! Thanks for creating the PR!
Could you please describe in more detail what kind of issues are you referring to? I think your changes look sensible, but just want to understand exactly what are you fixing with this.
Thanks!

@braposo I was trying to pause the text loop by updating the interval to 0, but then I found that the timeout cannot be cleared such that the text loop will still go to the next child and then stopped.
By including this PR, the timeout will be cleared as expected, such that the text loop will immediately stop when interval is changed to 0.
The reason is that with animationframe, the loop function will update the requestId value after it is returned to caller, hence we need to create an object to hold the requestId and return the reference to object instead of directly return as value.

bump

sorry for the delay @kenime! All sounds quite sensible, thanks for taking the time to explain and fix the issue! Going to merge and release it as a new version!

This is now included in https://github.com/braposo/react-text-loop/releases/tag/v2.3.0


ARTEMIS-1289 Fix: Unable to configure queues containing "/" in broker.xml

@michaelandrepearce Thanks for this.
Any chance you could make the queue ID unique.
e.g.
   <element name="addresses"...
        <xs:unique name="UniqueQueueName">
            <xs:selector xpath="address/*/queue/@name" />
            <xs:field xpath="@name" />
        </xs:unique>
    </element>

Actually, you could add this to the core element instead.  That means it would work for the 1.x way of defining queues.

@mtaylor as discussed in IRC, few comments i would have.

Address is currently xsd:string already (this is just following suit)

Duplicate declaration is checked anyhow on config load, do we really need a complex schema? as we don't do this on address and the same applies, that it must be unique.

Queues can be declared in two places it seems according to the xsd, either within an address, or within the queues section, as such an unique field within one element would not capture where it could be defined in two separate places.

@michaelandrepearce OK I think these are fair points.  I'll go ahead and merge this.


2.8.0-dev.20 – dart executed via symlink now fails (mac)!

Dart VM version: 2.8.0-dev.20.0 – SHA 803c0cd8da8125af1fe3a73970d66af892775fb7
brew installs dart in
$BREW/Cellar/dart/2.8.0-dev.20.0/libexec/bin
symlink is added to
$BREW/bin/dart -> ../Cellar/dart/2.8.0-dev.20.0/bin/dart
$BREW/bin is on path
> dart bin/some_exe.dart
Error: Error when reading 'bin/some_exe.dart': No such file or directory

> $BREW/bin/dart bin/some_exe.dart
Error: Error when reading 'bin/some_exe.dart': No such file or directory

This works fine
> $BREW/Cellar/dart/2.8.0-dev.20.0/libexec/bin/dart bin/some_exe.dart
All good!

Something with how the dart exe determines it's working directory seems very broken – at least on mac!

https://github.com/dart-lang/sdk/commit/99a5117411f9b9fae2866dee85573e9894db1f46 seems like it could be a culprit – CC @bkonyi

Should be fixed in https://dart-review.googlesource.com/c/sdk/+/142440

Instead of moving forward with another change I am wondering if it be more safe to do a cherry pick that reverts this change in 2.8, the change was made for dartdev which is not a feature for 2.8

Since we have a revert for this to be merged into the dev release bumping down priority from P0 to P2

Change to P1 to reflect priority for cherrypick, P2 will not meet the bar
Added merge-to-beta, merge-to-dev label for cherrypick process

Temporary workaround for homebrew until this goes out in the dev channel is to install the beta upcoming channel:
$ brew unlink dart
$ brew install dart-beta
$ dart --version
Dart VM version: 2.8.0-dev.20.7 (beta) (Tue Apr 14 08:59:52 2020 +0200) on "macos_x64"

It's a bit weird that there are fixes in beta not in dev... 🤷

@kevmoo I'm working on dev as well. We're in a bit of a weird state because of alignment with Flutter versioning.

Do we need some tweaking in the cherry pick process to ensure the merges flow first into dev and then into beta?

No, this is purely temporary and a technical rather than a process issue.

@bkonyi – this is back in the latest dev release - 2.9.0-1.0.dev

Verified fixed in 2.9.0-3.0.dev (dev) – thanks @bkonyi !

Thank you for verifying @kevmoo! May this issue remain closed for the rest of time...

I'm still see brew issues w/ the latest dev; is that expected? There's nothing left to merge?
dart analyze
Could not find DartDev snapshot and 'analyze' is not a valid script.

dart --version
Dart VM version: 2.9.0-7.0.dev (dev) (Thu May 7 09:17:54 2020 +0200) on "macos_x64"

Hm, not sure what the issue was, but it seems to disappear when I replace the last symlink in the brew install to point towards my locally built SDK. I've been fiddling with the options parsing quite a bit over the last week, so it could be that this was just a temporary failure that's been fixed in a follow up CL that came after we created the dev build.
Let's confirm whether or not this issue is still occurring once we create the next dev release.

Confirmed that we're seeing this again.

@devoncarew can you confirm this is resolved in 2.9.0-13.0.dev? It seems like it's working on my end now.

Yup! It started working as of the last time I checked, ~last week. Thanks!

Awesome! Thanks for confirming!