[Snyk] Fix for 2 vulnerabilities

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `pip` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

requirements.txt

⚠ Warning
tensorflow 2.11.0 requires tensorflow-io-gcs-filesystem, which is not installed.
tensorboard 2.11.2 has requirement setuptools>=41.0.0, but you have setuptools 40.5.0.
cirq-core 0.13.1 requires scipy, which is not installed.

Vulnerabilities that will be fixed
By pinning:

Severity
Priority Score (*)
Issue
Upgrade
Breaking Change
Exploit Maturity

651/1000  Why? Recently disclosed, Has a fix available, CVSS 7.3
Buffer Overflow SNYK-PYTHON-PILLOW-6514866
pillow:  9.5.0 -> 10.3.0
No
No Known Exploit

551/1000  Why? Recently disclosed, Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS) SNYK-PYTHON-PYLINT-6514864
pylint:  2.4.4 -> 2.6.1
No
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Some vulnerabilities couldn't be fully fixed and so Snyk will still find them when the project is tested again. This may be because the vulnerability existed within more than one direct dependency, but not all of the affected dependencies could be upgraded.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Regular Expression Denial of Service (ReDoS)

Summary by CodeRabbit

Chores

Updated dependencies to enhance application performance and security:

pylint version updated from 2.4.4 to 2.6.1.
pillow version requirement updated to >=10.3.0.

@dependabot rebase


"Move" button does not seem to exist anymore.

It seems that this page is outdated I can't find the "Move" button.

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

ID: 76c1c185-685f-27e0-e634-844b510b1834
Version Independent ID: 09375778-5354-ab44-c5c6-94c2aebe34bc
Content: Move resources to a new subscription or resource group - Azure Resource Manager
Content Source: articles/azure-resource-manager/resource-group-move-resources.md
Service: azure-resource-manager
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

@treisska Perhaps I am missing something but based on given information, my understanding and as shown in below screenshot, I could see 'Move' button. It will be available inside a resource group. Can you confirm if you are checking inside a resource group or not ? If yes, can you please provide a screenshot.

Oh, you're right, I wasn't really awake yesterday I guess. I wasn't looking in a resource group. I'm closing the issue, thank you :)


Flaky test: Dask worker paused, causing race condition

Describe the problem
In this CI run, Dask crashed with ValueError("Sample larger than population or is negative"). This is likely due to a race condition in Dask itself; we've filed an issue on their end: https://github.com/dask/distributed/issues/6713
Stack trace
============================= test session starts ==============================
platform linux -- Python 3.8.13, pytest-7.1.2, pluggy-1.0.0
benchmark: 3.4.1 (defaults: timer=time.perf_counter disable_gc=False min_rounds=5 min_time=0.000005 max_time=1.0 calibration_precision=10 warmup=False warmup_iterations=100000)
rootdir: /home/runner/work/modin/modin, configfile: setup.cfg
plugins: cov-2.11.0, benchmark-3.4.1, forked-1.4.0, xdist-2.5.0, Faker-13.15.0
gw0 I / gw1 I
gw0 [488] / gw1 [488]
........................................................................ [ 14%]
........................................................................ [ 29%]
........................................................................ [ 44%]
........................F............................................... [ 59%]
........................................................................ [ 73%]
........................................................................ [ 88%]
........................................................                 [100%]
=================================== FAILURES ===================================
________________ test_pivot[None-<lambda>-None-float_nan_data] _________________
[gw1] linux -- Python 3.8.13 /usr/share/miniconda3/envs/modin/bin/python
data = {'col1': [nan, 15.495823294762069, 54.18965011208873, 84.29175834609546, 52.475393862603724, 3.5983596208683966, ...],...': [nan, nan, nan, nan, 25.291907676386415, nan, ...], 'col12': [nan, nan, nan, nan, 4.509197191137804, nan, ...], ...}
 This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 312.40 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 314.01 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Worker is at 85% memory usage. Pausing worker.  Process memory: 407.79 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 382.26 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Worker is at 79% memory usage. Resuming worker. Process memory: 378.01 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 378.01 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 378.01 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 319.11 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Worker is at 80% memory usage. Pausing worker.  Process memory: 382.70 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 382.70 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.core - ERROR - Exception while handling op scatter
Traceback (most recent call last):
  File "/usr/share/miniconda3/envs/modin/lib/python3.8/site-packages/distributed/core.py", line 520, in handle_comm
    result = await result
  File "/usr/share/miniconda3/envs/modin/lib/python3.8/site-packages/distributed/scheduler.py", line 5847, in scatter
    await self.replicate(keys=keys, workers=workers, n=n)
  File "/usr/share/miniconda3/envs/modin/lib/python3.8/site-packages/distributed/scheduler.py", line 6644, in replicate
    for ws in random.sample(tuple(workers - ts._who_has), count):
  File "/usr/share/miniconda3/envs/modin/lib/python3.8/random.py", line 363, in sample
    raise ValueError("Sample larger than population or is negative")
ValueError: Sample larger than population or is negative
distributed.worker - WARNING - Worker is at 78% memory usage. Resuming worker. Process memory: 376.08 MiB -- Worker memory limit: 476.84 MiB
--------------------------- Captured stderr teardown ---------------------------
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 376.08 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
distributed.worker - WARNING - Unmanaged memory use is high. This may indicate a memory leak or the memory may not be released to the OS; see https://distributed.dask.org/en/latest/worker.html#memtrim for more information. -- Unmanaged memory: 377.76 MiB -- Worker memory limit: 476.84 MiB
---------- coverage: platform linux, python 3.8.13-final-0 -----------
Coverage XML written to file coverage.xml
=========================== short test summary info ============================
FAILED modin/pandas/test/dataframe/test_default.py::test_pivot[None-<lambda>-None-float_nan_data]
=========== 1 failed, 487 passed, 1361 warnings in 380.33s (0:06:20) ===========
Error: Process completed with exit code 1.

Another failure: https://github.com/modin-project/modin/runs/7636442346?check_suite_focus=true


Added handling POSIXct and POSIXT datetypes to prep_match_datatypes

Noticed my code was breaking because of this line of code that was removed.
else if (col_type == 'c("POSIXct", "POSIXt")') {
target_dataframe <- target_dataframe |>
dplyr::mutate(!!col == as.POSIXct(!!rlang::sym(col),
format = "YYYY-MM-DD"
))
Just added it back. The AFP database dates evaluates to 'c("POSIXct", "POSIXt")' instead and not Date, so in so doing it was not able to match the datatypes.

closing this request for now. Still working on it.


docs: update docs about "--show-drafts" option of "gas log" command

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 86.468%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
7642

Relevant Lines:
8838

💛  - Coveralls


The program has encountered an error. If the problem persists, please reach support with the logs found in C:\Users\ALT-PC-1\Desktop\VALORANT-rank-yoinker-2.0\build\exe.win-amd64-3.10\logs press enter to exit...

[2022.06.30-12.46.22] got region from logs '['na', ['na-1', 'na']]'
[2022.06.30-12.46.22] Api urls: pd_url: 'https://pd.na.a.pvp.net', glz_url: 'https://glz-na-1.na.a.pvp.net'
[2022.06.30-12.46.22] opened lockfile
[2022.06.30-12.46.22] got version from logs 'release-05.00-shipping-6-725355'
[2022.06.30-12.46.22] Traceback (most recent call last):
File "main.py", line 49, in
File "C:\Users\ALT-PC-1\Desktop\VALORANT-rank-yoinker-2.0\src\requests.py", line 33, in check_version
if not rStatus["status_ok"] or rStatus["print_message"]:
KeyError: 'status_ok'

please update to the latest version 2.0


Sorting arrows (asc desc) not showiing

Hi @hsduiii, this addon indeed doesn't have arrows for sorting. It just shows 'asc' en 'desc' in front of the column names. You have the options to add styling in your host app (using CSS or by overwriting the addons template file) or to use a styled extension of this addon (e.g. https://github.com/mu-semtech/ember-paper-data-table)

Hi @hsduiii, this addon indeed doesn't have arrows for sorting. It just shows 'asc' en 'desc' in front of the column names. You have the options to add styling in your host app (using CSS or by overwriting the addons template file) or to use a styled extension of this addon (e.g. https://github.com/mu-semtech/ember-paper-data-table)

Oh, i see, thanks!


hooks/hooks-intro

@markus-willems Please check all suggestions, so we can merge your translation ;)

@ph1p didn't have much time lately. I haven't forgotten though! Will review this weekend :)

@ph1p didn't have much time lately. I haven't forgotten though! Will review this weekend :)

All good :) I can understand that. I think we all have a lot to do every day. I just wanted to write if you didn't see it. Have a nice day ;)


Folders (containing source code files) that are imported into Grey Hack are not deleted after auto compilation process has been completed [Potential Bug]

In one of my Greyscript projects, I have a folder/file structure that looks like so:
my-greyscript-project
- src
  - main.src
  - helpers
    - enum-helpers.src

It should be noted that in this case, the main.src file imports the enum-helpers.src file (which is located in the helpers folder).
The issue is that when enabling auto compilation using the --auto-compile option, although the main.src and enum-helpers.src files are deleted after the auto-compilation process has been completed, the helpers folder is not deleted from the specified in-game output folder.
However, I was anticipating that the helpers folder would also be deleted from the specified in-game output folder (just like the main.src and enum-helpers.src files had been deleted after the auto-compilation process had been completed).
If necessary, I can provide further elaborations and details regarding this issue.

Hey thanks for reporting. This is a known issue which I don't really plan to fix for now since it kinda means unnecessary added complexity.
Let's take your example for instance. So let's say the helpers folder already existed on the machine then you probably don't want it to be actually removed. Therefore this means I would need to keep track if a folder already exists ahead of time or not. Generally it's not a real issue to add this whole logic but it would add further latency on the whole transaction process between greybel and game since for each folder I would need to check if it existed pre import. Thus I am not sure if it is worth the effort since it may increase latency too much just for the sake of deleting left over folders.
Overall I don't think that the left over folders cause such a headache. I think for most users of this feature it's more about not leaving any source files on the in-game computer.
Anyway I can take a look into how much the check would add on top of the current latency and maybe give a bit more feedback in this thread. But saying that I would keep it rather low prio for now.

I get your point but what you may forget is that users may do not think about the fact that their already existing folders may get deleted by using greybel for importing and auto-compiling files which may result in frustration since their files get deleted. Therefore I think it is better to be safe than sorry.

However, I am not sure about why you made the assumption that if the helpers folder already existed on my GH (Grey Hack) machine then I would not want it to be removed. Shouldn't files and folders be treated the same by the tool instead of being treated differently?

I don't think that the assumption that if a folder already exists on an in-game computer, it should remain is, in any sense, far-fetched. Also, there is certainly a difference between a file and a folder. If you override a file, you already take that into account; therefore, deleting it after the fact is obviously inevitable. On the other hand, a folder is not like a file. You do not override the folder. You merely add or remove files to or from it.

Example 1: Let's say that I have a helpers.src file which already exists on my GH machine, when the auto-compilation process is completed, the helpers.src file will be removed regardless of whether it existed on my GH machine before the auto-compilation process was started or not.
In Example 1, the implicit assumption made (i.e. by you or by the tool) was that the user would be alright with the helpers.src file being removed after the auto-compilation process was completed.

I think you should be aware that you are essentially overriding a file. Therefore it is save to assume that it gets lost regardless since there is no way that the original file will be recovered.

Example 2: Let's say that I have a helpers folder which already exists on my GH machine, when the auto-compilation process is completed, unlike the aforementioned helpers.src file, the helpers folder will not be removed because as you mentioned, you are not sure if the folder should actually be removed or not, so you instead assume that the user does not want the folder removed, however, this assumption is not made for files which I find quite inconsistent and strange.
In Example 2, the implicit assumption made (i.e. by you or by the tool) was that the user would not be alright with the helpers folder being removed after the auto-compilation process was completed.

A folder cannot be compared to a file. In my opinion if a folder already exists and there are files in the folder which are unrelated to the compilation process that folder should remain.Therefore, I don't really share the opinion that this is inconsistent or strange.
Also please keep in mind the main reason why the folders currently remain is mainly for the sake of simplicity. But in a perfect implementation I would check if there are still files remaining in the folder and depending on that would remove related folders.

As you can hopefully see from the 2 aforementioned examples, the assumption made (i.e. by you or by this tool) for files and folders is different, which leads to unnecessary inconsistency (and perhaps even confusion on the part of the user), ideally, the assumptions made for files and folders should be the same (at least as much as possible) so as to increase consistency and minimize the chances of users running into unexpected behaviors when using this tool (which might also improve their perception of the reliability of this tool).
This tool does not seem to take responsibility for preserving files that the user might or might not want to keep on their GH machine (when auto-compiling), so why should it suddenly take responsibility for preserving folders that the user might or might not want to keep on their GH machine (when auto-compiling)?

I think we have a general disagreement when it comes to the perception of how a folder and file should be treated since from your definition it should be clearly treated the same. But I think there should be certainly a difference between treating these two things.
Also again, and I may repeat myself, I don't think that remaining folders will lead to huge problems nor any major confusion.

Anyway I've gonna ask in the discord for more opinions on this.

I get your point but what you may forget is that users may do not think about the fact that their already existing folders may get deleted by using greybel for importing and auto-compiling files which may result in frustration since their files get deleted. Therefore I think it is better to be safe than sorry.

However, I am not sure about why you made the assumption that if the helpers folder already existed on my GH (Grey Hack) machine then I would not want it to be removed. Shouldn't files and folders be treated the same by the tool instead of being treated differently?

I don't think that the assumption that if a folder already exists on an in-game computer, it should remain is, in any sense, far-fetched. Also, there is certainly a difference between a file and a folder. If you override a file, you already take that into account; therefore, deleting it after the fact is obviously inevitable. On the other hand, a folder is not like a file. You do not override the folder. You merely add or remove files to or from it.

Example 1: Let's say that I have a helpers.src file which already exists on my GH machine, when the auto-compilation process is completed, the helpers.src file will be removed regardless of whether it existed on my GH machine before the auto-compilation process was started or not.
In Example 1, the implicit assumption made (i.e. by you or by the tool) was that the user would be alright with the helpers.src file being removed after the auto-compilation process was completed.

I think you should be aware that you are essentially overriding a file. Therefore it is save to assume that it gets lost regardless since there is no way that the original file will be recovered.

Example 2: Let's say that I have a helpers folder which already exists on my GH machine, when the auto-compilation process is completed, unlike the aforementioned helpers.src file, the helpers folder will not be removed because as you mentioned, you are not sure if the folder should actually be removed or not, so you instead assume that the user does not want the folder removed, however, this assumption is not made for files which I find quite inconsistent and strange.
In Example 2, the implicit assumption made (i.e. by you or by the tool) was that the user would not be alright with the helpers folder being removed after the auto-compilation process was completed.

A folder cannot be compared to a file. In my opinion if a folder already exists and there are files in the folder which are unrelated to the compilation process that folder should remain.Therefore, I don't really share the opinion that this is inconsistent or strange.
Also please keep in mind the main reason why the folders currently remain is mainly for the sake of simplicity. But in a perfect implementation I would check if there are still files remaining in the folder and depending on that would remove related folders.

As you can hopefully see from the 2 aforementioned examples, the assumption made (i.e. by you or by this tool) for files and folders is different, which leads to unnecessary inconsistency (and perhaps even confusion on the part of the user), ideally, the assumptions made for files and folders should be the same (at least as much as possible) so as to increase consistency and minimize the chances of users running into unexpected behaviors when using this tool (which might also improve their perception of the reliability of this tool).
This tool does not seem to take responsibility for preserving files that the user might or might not want to keep on their GH machine (when auto-compiling), so why should it suddenly take responsibility for preserving folders that the user might or might not want to keep on their GH machine (when auto-compiling)?

I think we have a general disagreement when it comes to the understanding of how a folder and file should be treated since from your definition it should be clearly treated the same. But I think there should be a difference between treating these two things.
Also again, and I may repeat myself, I don't think that remaining folders will lead to huge problems nor any major confusion.

I see, thank you for your response and for getting the opinions of other users on the Discord server with regards to this issue.

I get your point but what you may forget is that users may do not think about the fact that their already existing folders may get
deleted by using greybel for importing and auto-compiling files which may result in frustration since their files get deleted.
Therefore I think it is better to be safe than sorry.

With regards to the following statement that you made in your response, one suggestion comes to mind, with the said suggestion being that a CLI option (named something like preserve-folders-after-auto-compile, or it could be given a shorter or more concise name) could be added so that users could specify whether they want the affected folders on their GH machine preserved or removed after the auto-compilation process has been completed. This way, no assumptions would have to be made by you regarding the ambiguous matter of whether a user is alright or not alright with the affected folders being deleted from their GH machine after the auto-compilation process has been completed.
Due to certain external matters, I might not have as much time to provide an in-depth response to what you have mentioned in your previous messages, however, I will try to do so when time permits me to once again.

If you think it is alright to implement the suggestion I mentioned in my previous message, I would be willing to help out with implementing it.

Generally I agree with adding an option but I think the default behaviour should be that folders will get preserved especially keeping in mind being backwards compatible.
Therefore I would suggest to add a option such as --auto-compile-purge or maybe just --purge to just forcefully remove every folder regardless of if there are remaining files/folders or not.

If you are alright with the suggestion that I mentioned in my previous message, I would be willing to help out with implementing it.

I've already started working on implementing the deletion + preservation logic. I can push that branch in a bit and then you could implement the --auto-compile-purge option if you want.

Alright I just pushed 3.2.16. Feel free to implement the flag by basing of that branch. It should be a lot easier to implement via that branch since I've extended the agent to allow code execution.

Alright I just pushed 3.2.16. Feel free to implement the flag by basing off that branch. It should be a lot easier to implement via that branch since I've extended the agent to allow code execution.

I see, thank you, and sure.

I have finished implementing the flag as well as the functionality backing it up.

I have finished implementing the said flag as well as the functionality backing it up.

Thanks. I've reviewed your PR and left one comment regarding the logic of deleting the folders. Once you've resolved that I am happy to merge the PR.

I have finished implementing the said flag as well as the functionality backing it up.

Thanks. I've reviewed your PR and left one comment regarding the logic of deleting the folders. Once you've resolved that I am happy to merge the PR.

Thank you for reviewing my PR, with regards to the change that you proposed, I might have certain questions about it which I have posted in my responses to your comment on my PR, I would appreciate it if you could take a look at them and answer them as soon as possible, thank you in advance.

Should be available now with 3.2.16 released.

I see, thank you.

Since this issue has been resolved, I will close it. Thanks again for helping to resolve it.


Can't deploy Azure Vm with ARM Template, error with "patchSettings"

Hello,
I try to deploy an Azure VM with windows with ARM Template with this configuration :
"osProfile": {
                    "computerName": "[parameters('virtualMachineName')]",
                    "adminUsername": "[parameters('adminUsername')]",
                    "adminPassword": "[parameters('adminPassword')]",
                    "windowsConfiguration": {
                        "ProvisionVMAgent": true,
                        "EnableAutomaticUpdates": true,
                        "PatchSettings": {
                            "patchMode": "AutomaticByPlatform",
                            "automaticByPlatformSettings": {
                                "bypassPlatformSafetyChecksOnUserSchedule": true
                            },
                            "assessmentMode": "AutomaticByPlatform"
                        },
                        "enableVMAgentPlatformUpdates": false
                    },
                    "secrets": []
                },

but i have this error in powerhsell and also on Azure portal
Message : Could not find member 'patchSettings' on object of type 'WindowsConfiguration'. Path 'properties.osProfile.windowsConfiguration.patchSettings', line 1, position 355.
Error Code : BadRequest
I searched for a lot of time, but i didn't find the solution.
Thanks in advance.

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

ID: ea17fd8b-0187-1723-b1df-0ab1e73c059f
Version Independent ID: 9dc81c82-6fb7-e8b3-2760-a1b54122fe9e
Content: WindowsConfiguration Class (Microsoft.Azure.Management.Compute.Models) - Azure for .NET Developers
Content Source: xml/Microsoft.Azure.Management.Compute.Models/WindowsConfiguration.xml
Service: multiple
GitHub Login: @rloutlaw
Microsoft Alias: routlaw

Hi @AKowsigan.  Thank you for reaching out and we regret that you're experiencing difficulties.  Can you please help us understand which Azure SDK package you're using so that we can loop in the right folks to assist?

Hi @AKowsigan.  If I understand what you're looking for, it would be the schema for VMs, which appears to be here.
Unfortunately, there's no further help that we can provide.  This repository is focused on the Azure SDK for .NET - we're unable to assist with other Azure issues.   If further help is needed, your best path forward would be to open an Azure support request.
I'm going to close this out;  if I've misunderstood what you're describing, please let us know in a comment and we'd be happy to assist as we're able.


last version 2222 not working on Mac OS High Sierra

It is not even starting.

i'm sorry, my mistake, am uploading a working version now.


check 'name' field is a string type for about msgs

addresses https://github.com/ssbc/scuttlebot/issues/472

Also: any objections to moving this repo to the ssbc org so we can push emergency fixes?

no objections. Thanks for figuring this one out @noffle !

ah yeah, people started using about messages for everything... merging. will shift to ssbc too

note, this changes the code for the index, so requires the index to rebuild, but it doesn't change the api, so it's just a patch version.

merged into 3.0.2


Library allows add_peer() when connection_state is not WebRTCPeerConnection.STATE_NEW.

Godot version
3.3.3.stable
Plugin version
0.5
System information
Linux
Issue description
According to the documentation for add_peer, the following should not have worked:
if v["subject"] == "offer":
	var peer = WebRTCPeerConnection.new()
	peer.initialize({"iceServers": [ { "urls": ["stun:stun.l.google.com:19302"] } ] })
	peer.connect("session_description_created", self, "client_session_description_created")
	peer.connect("ice_candidate_created", self, "client_ice_candidate_created")

	var networkedmultiplayerclient = WebRTCMultiplayer.new()
	peer.set_remote_description("offer", v["data"])
	networkedmultiplayerclient.add_peer(peer, 1)

However, it does in the webrtc-native library.  But it doesn't in the HTML5 implementation.  This difference made my bug quite hard to find.
Basically my last two lines needed to be swapped around for it to be right.
Steps to reproduce
The code above is an excerpt of the client_packet_received from here:
https://github.com/goatchurchprime/godot_multiplayer_networking_workbench/blob/main/networking/WebRTCmultiplayerclient.gd#L29
It would take a bit of work to thin it down to just that WebRTCmultiplayerclient example.  It would be easy to show if there was a minimal WebRTC multiplayer example in the networking demo projects, and to keep it self-contained it could use WebSockets as the signalling system
Minimal reproduction project
See above

I've finally got the example derived from the signalling demo with an ugly toggle button "Addpeerbeforesetdescription" to swap the order of the function calls.
webrtc_signaling (copy).zip
I've used a peerslist = {} to keep track of the peers created, instead of fetching them back using the WebRTCMultiplayer.get_peer(id).connection function.
It's necessary to call WebRTCPeerConnection.add_peer(peer) before peer.create_offer()
However on the receiving end of the Offer your library lets me get away with add_peer() after set_remote_description():
  var rtc_mp = WebRTCMultiplayer.new()
  peer.set_remote_description("offer", offer)
  rtc_mp.add_peer(peer, id)

I have confirmed that the HTML5 implementation does not work for this, but your library does.
To run the HTML5 version:

Run a copy of WebRTC_signalling_demo on the command line and click on the Signalling server: Listen button.
Run the exported HTML5
Hit Start on the top left panel
Paste the string after Joined lobby into the Room Secret line edit box
Hit Start on the top right panel
... then some stuff happens (or doesn't) to indicate a WebRTC connection has been established.

This is now running on Godot version 3.4.
The reason this issue matters is it's easier to develop WebRTC code against this plugin than on the HTML5 platform, so this is where people are going to be looking for their bugs.


missing labs

20, 21, 22  7 and 9 , 54, 46, 57 are missing from the lab export.

We are still missing labs for BRICK_09, 20,21,22,7, 46 and 57 @AidaasinAyda

requested an export for these labs. the data stewards will contact me about it


🐛 [Firebase-Core] Upgrade Android SDK version to pull in upstream bugfix

In light of firebase/firebase-android-sdk#3757, the Android SDK dependency should be upgraded to the latest version (30.3.0 as of writing), in order to pull in the fix released in that version.
I see the change itself is already done, but is awaiting release, I guess? When is the next scheduled (or unscheduled) release due?

https://github.com/firebase/flutterfire/pull/9161
This should be released I think per this comment.
Closing, as above links should address your question.


'rasa.model.unpack_model ' Triggered 4 times and did not clean up when the program was closed.

Rasa version: 1.8
Rasa SDK version (if used & relevant):
Rasa X version (if used & relevant):
Python version:3.7.1
Operating system (windows, osx, ...):windows
Issue:
'rasa.model.unpack_model ' Triggered 4 times and did not clean up when the program was closed.
4 folders are generated in the directory 'CreatorTemp' after 'rasa shell -vv'.
Only the last two directories are deleted when the program exits.
After several starts, I got a lot of useless cache directories
Error (including full traceback):
PS E:\GitHub\bot\test_app> rasa shell -vv
2020-03-18 15:13:43 DEBUG    rasa.model  - Extracted model to 'C:\Users\Public\Documents\Wondershare\CreatorTemp\tmpvcevdagm'.
2020-03-18 15:13:43 DEBUG    rasa.cli.utils  - Parameter 'endpoints' not set. Using default location 'endpoints.yml' instead.
2020-03-18 15:13:43 DEBUG    rasa.cli.utils  - Parameter 'credentials' not set. Using default location 'credentials.yml' instead.
2020-03-18 15:13:43 DEBUG    rasa.model  - Extracted model to 'C:\Users\Public\Documents\Wondershare\CreatorTemp\tmph5zxtwp4'.
2020-03-18 15:13:44 INFO     root  - Connecting to channel 'cmdline' which was specified by the '--connector' argument. Any other channels will be i
gnored. To connect to all given channels, omit the '--connector' argument.
2020-03-18 15:13:44 DEBUG    sanic.root  - CORS: Configuring CORS with resources: {'/*': {'origins': [''], 'methods': 'DELETE, GET, HEAD, OPTIONS, P
ATCH, POST, PUT', 'allow_headers': ['.*'], 'expose_headers': None, 'supports_credentials': True, 'max_age': None, 'send_wildcard': False, 'automatic
_options': True, 'vary_header': True, 'resources': {'/*': {'origins': ''}}, 'intercept_exceptions': True, 'always_send': True}}
2020-03-18 15:13:44 DEBUG    rasa.core.utils  - Available web server routes:
/webhooks/rest                                     GET                            custom_webhook_CmdlineInput.health
/webhooks/rest/webhook                             POST                           custom_webhook_CmdlineInput.receive
/                                                  GET                            hello
2020-03-18 15:13:44 INFO     root  - Starting Sophi server on http://localhost:5005
2020-03-18 15:13:44 DEBUG    rasa.core.utils  - Using the default number of Sanic workers (1).
2020-03-18 15:13:44 INFO     root  - Enabling coroutine debugging. Loop id<PHONE_NUMBER>664.
2020-03-18 15:13:44 DEBUG    rasa.model  - Extracted model to 'C:\Users\Public\Documents\Wondershare\CreatorTemp\tmpep4di4kg'.
2020-03-18 15:13:44 INFO     rasa.nlu.isi.ISISemanticDependency  - load()...
...
2020-03-18 15:13:45 DEBUG    rasa.core.tracker_store  - Connected to InMemoryTrackerStore.
2020-03-18 15:13:45 DEBUG    rasa.core.lock_store  - Connected to lock store 'InMemoryLockStore'.
2020-03-18 15:13:45 DEBUG    rasa.model  - Extracted model to 'C:\Users\Public\Documents\Wondershare\CreatorTemp\tmpnujnm5cy'.
2020-03-18 15:13:45 DEBUG    pykwalify.compat  - Using yaml library: f:\virtualenvs\rasa-wr2c3hgm-py3.7\lib\site-packages\ruamel\yaml\__init__.py
2020-03-18 15:13:45 DEBUG    rasa.core.nlg.generator  - Instantiated NLG to 'TemplatedNaturalLanguageGenerator'.
Bot loaded. Type a message and press enter (use '/stop' to exit):
Your input ->

Cancelled by user

2020-03-18 15:15:33 INFO     root  - Killing Sanic server now.

Command or request that led to error:
rasa shell -vv
ctrl + c

Content of configuration file (config.yml) (if relevant):

Content of domain file (domain.yml) (if relevant):

Thanks for the issue, @erohmensing will get back to you about it soon!
You may find help in the docs and the forum, too 🤗

I've fixed the bug about the undeleted temporary files.
But I still don't understand why rasa has to decompress it many times.When I execute 'rasa shell'.
First decompression :
···
rasa.cli.shell.shell
···
Second decompression
···
rasa.cli.run.run
···
I think these two places are more about checking the validity of the model structure than using it.
I modified them according to this idea

Sorry, I'm confused. With I've fixed the bug and I modified them according to this idea, where are you fixing things? Was it an issue with the code or your setup?

The main causes of useless cache directories are code issues.

Hey @glacierck! Would you mind opening a PR with your proposed changes? That way we can review and test them easily.


.net core 2.0 project 107 ENOTCONN socket is not connected at

I am deployoing .net core 2.0 project on Linux UbuntuI have used Supervisor And Nginx, however I get the following output
exception.Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Networking.UvException: Error -107 ENOTCONN socket is not connected at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Networking.LibuvFunctions.ThrowError(Int32 statusCode) at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Networking.LibuvFunctions.tcp_getpeername(UvTcpHandle handle, SockAddr& addr, Int32& namelen) at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Networking.UvTcpHandle.GetPeerIPEndPoint() at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.LibuvConnection..ctor(ListenerContext context, UvStreamHandle socket) at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Listener.DispatchConnection(UvStreamHandle socket) at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Listener.OnConnection(UvStreamHandle listenSocket, Int32 status)

@shaddockblack Could you share more details, or ideally an app that reproduces your issue?

Not enough details, so closing this one.

I have got a lot of same exception, but I didn't knew where the exception happened.
2017-12-07 16:34:42.758 +08:00 [Error] Listener.OnConnection
Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Networking.UvException: Error -107 ENOTCONN socket is not connected
   at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Networking.LibuvFunctions.ThrowError(Int32 statusCode)
   at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Networking.UvTcpHandle.GetPeerIPEndPoint()
   at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.LibuvConnection..ctor(ListenerContext context, UvStreamHandle socket)
   at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Listener.DispatchConnection(UvStreamHandle socket)
   at Microsoft.AspNetCore.Server.Kestrel.Transport.Libuv.Internal.Listener.OnConnection(UvStreamHandle listenSocket, Int32 status)

@kexxxfeng Are you able to share a small repro app on GitHub?

@kexxxfeng What OS is the app running on? Did you notice any failed requests or any other issue other than the error log?
My theory is that this is caused by a client disconnecting almost immediately after connecting.

Recently, I upgraded Microsoft.AspNetCore.All to 2.0.3，then the exception was logged on running.
 Error:
   An assembly specified in the application dependencies manifest (Cnblogs.UCenter.WebAPI.deps.json) was not found:
     package: 'Microsoft.AspNetCore.Antiforgery', version: '2.0.1'
     path: 'lib/netstandard2.0/Microsoft.AspNetCore.Antiforgery.dll'
   This assembly was expected to be in the local runtime store as the application was published usingthe following target manifest files:
     aspnetcore-store-2.0.3.xml
 Error:
   An assembly specified in the application dependencies manifest (Cnblogs.UCenter.WebAPI.deps.json) was not found:
     package: 'Microsoft.AspNetCore.Antiforgery', version: '2.0.1'
     path: 'lib/netstandard2.0/Microsoft.AspNetCore.Antiforgery.dll'
   This assembly was expected to be in the local runtime store as the application was published usingthe following target manifest files:
     aspnetcore-store-2.0.3.xml

Then, I found an issue about that on github.
According the comment, I disable PublishWithAspNetCoreTargetManifest.
<PropertyGroup>
  <PublishWithAspNetCoreTargetManifest>false</PublishWithAspNetCoreTargetManifest>
</PropertyGroup>

The app ran successfully. But after a few days, I found the error reported before in the log.txt.
Now, I have already downgrade Microsoft.AspNetCore.All to 2.0.0. the error was not appeared any more.
The error was threw occasionally, in my opinion,  it must be about Microsoft.AspNetCore.All 2.0.3.
I've tried to new a demo to reproduce the exception, however, it didn't appear again.


How to force rye to use gh matrix's python version?

Hey,
I'm running to an issue that rye is using python 3.8, disrespecting matrix's python version.
For detailed insight:
https://github.com/pydantic/FastUI/pull/287#discussion_r1582518466
Any idea how can i match these two? perhaps something to be mentioned in readme?

Hi, rye will look for the pinned version in .python_version to have to set it as the very first rye command. Here is an example how I use it in one of my repos: https://github.com/eifinger/hass-fressnapf-tracker/blob/a3852211708debea35e385f0b9553ba6cb42c607/.github/workflows/ci.yaml#L23-L33
The clear drawback here is, that it is not using the lock files you have on your local setup since it runs sync again.
You can try to change that to sync --no-lock but I had a few problems with that approach. Some dependencies have transitive dependencies depending on the current python version. If you create the lock files with one python version but run it with another this might cause problems. Try it out, depending on your dependencies it might work.
This is an open issue with rye itself I have not found a way yet to work around that.
See: https://github.com/astral-sh/rye/discussions/438 https://github.com/astral-sh/rye/discussions/411

As FastUI (big fan btw) itself is a library I would argue that its not that big a deal. The final dependency versions which get resolved are defined by the project using it as a dependency. Only pyproject.toml contents will count.
It might cause flaky and hard to debug CI pipelines still...

Hi thanks for the quick answer!

Hi, rye will look for the pinned version in .python_version to have to set it as the very first rye command. Here is an example how I use it in one of my repos: https://github.com/eifinger/pywaze/blob/main/.github/workflows/ci.yml

Yes but I didn't push it, because i didn't want it to run only one version.

You can try to change that to sync --no-lock but I had a few problems with that approach. Some dependencies have transitive dependencies depending on the current python version. If you create the lock files with one python version but run it with another this might cause problems. Try it out, depending on your dependencies it might work.

Oh didn't know that! Hmm that makes it even harder to use it on ci with multiple version pythons
Thanks for the example, it was very useful. so rye pin does the job! 👍 I'm still newbie in rye, never used it in any actual project.


Bootstrap pagination does not work with angular-ui-bootstrap/2.5.0/ui-bootstrap-tpls.js

Because of this thread, I need to use a high version of ui-bootstrap-tpls.js. However, I realise that this disabled bootstrap pagination, which works with a lower version of ui-bootstrap-tpls.js.
For example, this pagination works with https://cdnjs.cloudflare.com/ajax/libs/angular-ui-bootstrap/0.11.0/ui-bootstrap-tpls.js, whereas https://cdnjs.cloudflare.com/ajax/libs/angular-ui-bootstrap/2.5.0/ui-bootstrap-tpls.js does not work.
Does anyone know what I could do?

See the docs at https://angular-ui.github.io/bootstrap/, the tag changed since 0.11. You need to replace  with .

It works, thank you...


Bump prowjobs to Go 1.18.2

What this PR does / why we need it:
What it says at the top. Bumps Go in prow jobs to 1.18.2 and respectively updated kubermatic/build images.
Which issue(s) this PR fixes (optional, in fixes #<issue number> format, will close the issue(s) when PR gets merged):
Fixes #
Special notes for your reviewer:
Optional Release Note:

Update Go to 1.18.2

Signed-off-by: Marvin Beckers<EMAIL_ADDRESS>

/hold

/lgtm cancel

/retest


config consistency

Fixes #194  .
Motivation
The bool config in rosetta-cli conf has variables with both *enabled and *disabled suffixes which is inconsistent and creates confusion.
Solution
Making all the config *disabled
Open questions

Pull Request Test Coverage Report for Build 7396

0 of 2 (0.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 41.983%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

pkg/results/construction_results.go
0
1
0.0%

pkg/results/data_results.go
0
1
0.0%

Totals

Change from base Build 7372:
0.0%

Covered Lines:
707

Relevant Lines:
1684

💛  - Coveralls


An --ignores argument?

It's possible there is a use case for an --ignore-packages argument. The user can ignore certain packages and creosote would simply ignore reporting them as unused. The ignores already exists internally here so all that is needed to enable this is to pass an argument to the CLI and pass it onto that function.
The use case could be e.g. using SQLAlchemy with a database driver. You wouldn't import the database driver in your own source code. Instead you would tell SQLAlchemy to use it via e.g. connection or engine creation string. This would be too tricky to support for Creosote, I think.
To avoid forgetting about the ignores (if e.g. discontinuing the use of said database driver above), Creosote could complain if an ignored package is no longer found in the dependency file (pyproject.toml, requirements.txt, ...), prompting the user to also remove the ignore.
🤔 Would it also be useful to ignore certain files/folders from the source code scan?
Anyhow, this would in that case be a different CLI argument, like --ignore-paths.
I'm just leaving this thought here for now to simmer. Please upvote if you think this would be a good addition to Creosote. 😄

Would it also be useful to ignore certain files/folders from the source code scan?

It's actually even possible there is a need for ignoring venvs, if creosote ends up supporting multiple venvs. Use case example: pip install --user.

It seems what we need here is an --ignore-packages argument but maybe also a good time to introduce the option to configure via pyproject.toml itself? 🤔
Maybe add add a [tool.creosote] section where all config can be stored...?

Isn't it more of an --additional-packages? And yes. definitely a good idea to off-load it into a configuration file.

@grofte haha, yeah - much better 😄
I would be super happy if anyone in need of this feature would like to give this a try:
$ pipx install --suffix=@130 --force git+https://github.com/fredrikaverpil/creosote.git@extend-with-packages
$ creosote@main ... --extend-with-packages <PKG1>..<PKG2>
$ pipx uninstall creosote@130


RingBuf constructor contains UB

https://github.com/carllerche/mio/issues/119

RingBuf is removed.


Fix heartbeat returning too fast

Description
Fix issue where heartbeat doesn't sleep
I did not look through all other uses of .time()
Self Check:
Strike through any lines that are not applicable (~~line~~) then check the box

[ ] Attached issue to pull request
[x] Changelog entry
[ ] Type annotations are present
[ ] Code is clear and sufficiently documented
[ ] No (preventable) type errors (check using make mypy or make mypy-diff)
[ ] Sufficient test cases (reproduces the bug/tests the requested feature)
[ ] Correct, in line with design
[ ] End user documentation is included or an issue is created for end-user documentation (add ref to issue here: )
[ ] If this PR fixes a race condition in the test suite, also push the fix to the relevant stable branche(s) (see test-fixes for more info)

Processing this pull request

Merged into branches master in c88e7895ee18e2621b5ab23a94fb5aa4c6076ce9


Readme example uses shorthand with full word

Both POSIX and Windows prefix conventions are supported. When manually setting a name (overriding decorated property's name), you should specify the option name including the prefix (e.g. --option, -option or /option)

Should read

Both POSIX and Windows prefix conventions are supported. When manually setting a name (overriding decorated property's name), you should specify the option name including the prefix (e.g. --option, -o or /option)

As - is shorthand and -- is longhand.
So -o is correct and -option means -o -p -t -i -o -n, which is not what you meant.

Ok updated docs:

Both POSIX and Windows prefix conventions are supported. When manually setting a name (overriding decorated property's name), you should specify the option name including the prefix (e.g. --option, -o, -option or /option).
Bundling of single-character options are supported, also known as stacking. Bundled options are single-character option aliases specified together after a single hyphen prefix. For example if you have options "-a", "-b" and "-c", you can bundle them like "-abc". Only the last option can specify an argument. Note that if you have an explicit option named "-abc" then it will win over bundled options.


ReferenceError: Cannot access 'isBrowser' before initialization

What is the current behavior?
I am trying to use the JS sdk in a Next.js 15 App Router api route. So executed on the server.
I am instantiating Deepgram as per instructions here with
const deepgram = createClient(process.env.DEEPGRAM_API_KEY);

but I get the following error:
⨯ ReferenceError: Cannot access 'isBrowser' before initialization
    at Module.isBrowser
    ...
  page: '/api/audio/text-to-speech'
}
 POST /api/audio/text-to-speech 500 in 50ms

Steps to reproduce

Create a Next.js 15 App router codebase
create an api route
in the same file add const deepgram = createClient(process.env.DEEPGRAM_API_KEY);
call the route
error will be thrown in the app console

Expected behavior
To just be able to use the sdk in an api route
Please tell us about your environment

We want to make sure the problem isn't specific to your operating system or programming language.

Operating System/Version: macOS
Language: TypeScript
Browser: Chrome
Next.js: 15.0.1
@deepgram/sdk: 3.9.0

Other information
This is the stack trace:
⨯ ReferenceError: Cannot access 'isBrowser' before initialization
    at Module.isBrowser (/Users/claudio/Dev/web/cuecard/.next/server/chunks/node_modules_@deepgram_sdk_dist_module_6533bc._.js:147:23)
    at<EMAIL_ADDRESS>[app-route] (ecmascript) (/Users/claudio/Dev/web/cuecard/.next/server/chunks/node_modules_@deepgram_sdk_dist_module_6533bc._.js:99:211)
    at instantiateModule (/Users/claudio/Dev/web/cuecard/.next/server/chunks/[turbopack]_runtime.js:589:23)
    at getOrInstantiateModuleFromParent (/Users/claudio/Dev/web/cuecard/.next/server/chunks/[turbopack]_runtime.js:644:12)
    at esmImport (/Users/claudio/Dev/web/cuecard/.next/server/chunks/[turbopack]_runtime.js:132:20)
    at<EMAIL_ADDRESS>[app-route] (ecmascript) (/Users/claudio/Dev/web/cuecard/.next/server/chunks/node_modules_@deepgram_sdk_dist_module_6533bc._.js:160:177)
    at instantiateModule (/Users/claudio/Dev/web/cuecard/.next/server/chunks/[turbopack]_runtime.js:589:23)
    at getOrInstantiateModuleFromParent (/Users/claudio/Dev/web/cuecard/.next/server/chunks/[turbopack]_runtime.js:644:12)
    at esmImport (/Users/claudio/Dev/web/cuecard/.next/server/chunks/[turbopack]_runtime.js:132:20)
    at<EMAIL_ADDRESS>[app-route] (ecmascript) (/Users/claudio/Dev/web/cuecard/.next/server/chunks/node_modules_@deepgram_sdk_dist_module_6533bc._.js:676:175)
    at instantiateModule (/Users/claudio/Dev/web/cuecard/.next/server/chunks/[turbopack]_runtime.js:589:23)
    at getOrInstantiateModuleFromParent (/Users/claudio/Dev/web/cuecard/.next/server/chunks/[turbopack]_runtime.js:644:12)
    at esmImport (/Users/claudio/Dev/web/cuecard/.next/server/chunks/[turbopack]_runtime.js:132:20)
    at<EMAIL_ADDRESS>[app-route] (ecmascript) (/Users/claudio/Dev/web/cuecard/.next/server/chunks/node_modules_@deepgram_sdk_dist_module_6533bc._.js:1269:189)
    at instantiateModule (/Users/claudio/Dev/web/cuecard/.next/server/chunks/[turbopack]_runtime.js:589:23)
    at getOrInstantiateModuleFromParent (/Users/claudio/Dev/web/cuecard/.next/server/chunks/[turbopack]_runtime.js:644:12)
    at esmImport (/Users/claudio/Dev/web/cuecard/.next/server/chunks/[turbopack]_runtime.js:132:20)
    at<EMAIL_ADDRESS>[app-route] (ecmascript) (/Users/claudio/Dev/web/cuecard/.next/server/chunks/node_modules_@deepgram_sdk_dist_module_6533bc._.js:2909:185)
    at instantiateModule (/Users/claudio/Dev/web/cuecard/.next/server/chunks/[turbopack]_runtime.js:589:23)
    at getOrInstantiateModuleFromParent (/Users/claudio/Dev/web/cuecard/.next/server/chunks/[turbopack]_runtime.js:644:12)
    at esmImport (/Users/claudio/Dev/web/cuecard/.next/server/chunks/[turbopack]_runtime.js:132:20)
    at<EMAIL_ADDRESS>[app-route] (ecmascript) <locals> (/Users/claudio/Dev/web/cuecard/.next/server/chunks/node_modules_@deepgram_sdk_dist_module_6533bc._.js:3030:175)
    at instantiateModule (/Users/claudio/Dev/web/cuecard/.next/server/chunks/[turbopack]_runtime.js:589:23)
    at getOrInstantiateModuleFromParent (/Users/claudio/Dev/web/cuecard/.next/server/chunks/[turbopack]_runtime.js:644:12)
    at esmImport (/Users/claudio/Dev/web/cuecard/.next/server/chunks/[turbopack]_runtime.js:132:20)
    at [project]/libs/deepgram/speech.ts [app-route] (ecmascript) (/Users/claudio/Dev/web/cuecard/.next/server/chunks/[root of the server]__c97bc6._.js:107:182)
    at instantiateModule (/Users/claudio/Dev/web/cuecard/.next/server/chunks/[turbopack]_runtime.js:589:23)
    at getOrInstantiateModuleFromParent (/Users/claudio/Dev/web/cuecard/.next/server/chunks/[turbopack]_runtime.js:644:12)
    at esmImport (/Users/claudio/Dev/web/cuecard/.next/server/chunks/[turbopack]_runtime.js:132:20)
    at [project]/app/api/audio/text-to-speech/route.ts [app-route] (ecmascript) (/Users/claudio/Dev/web/cuecard/.next/server/chunks/[root of the server]__c97bc6._.js:490:132)
    at instantiateModule (/Users/claudio/Dev/web/cuecard/.next/server/chunks/[turbopack]_runtime.js:589:23)
    at getOrInstantiateModuleFromParent (/Users/claudio/Dev/web/cuecard/.next/server/chunks/[turbopack]_runtime.js:644:12)
    at esmImport (/Users/claudio/Dev/web/cuecard/.next/server/chunks/[turbopack]_runtime.js:132:20)
    at [project]/node_modules/next/dist/esm/build/templates/app-route.js { INNER_APP_ROUTE => "[project]/app/api/audio/text-to-speech/route.ts [app-route] (ecmascript)" } [app-route] (ecmascript) (/Users/claudio/Dev/web/cuecard/.next/server/chunks/_5829b8._.js:47:158)
    at instantiateModule (/Users/claudio/Dev/web/cuecard/.next/server/chunks/[turbopack]_runtime.js:589:23)
    at instantiateRuntimeModule (/Users/claudio/Dev/web/cuecard/.next/server/chunks/[turbopack]_runtime.js:652:12)
    at Object.getOrInstantiateRuntimeModule (/Users/claudio/Dev/web/cuecard/.next/server/chunks/[turbopack]_runtime.js:668:12)
    at Object.<anonymous> (/Users/claudio/Dev/web/cuecard/.next/server/app/api/audio/text-to-speech/route.js:13:26)
    at Module._compile (node:internal/modules/cjs/loader:1469:14)
    at Module._extensions..js (node:internal/modules/cjs/loader:1548:10)
    at Module.load (node:internal/modules/cjs/loader:1288:32)
    at Module._load (node:internal/modules/cjs/loader:1104:12)
    at Module.require (node:internal/modules/cjs/loader:1311:19)
    at mod.require (/Users/claudio/Dev/web/cuecard/node_modules/next/dist/server/require-hook.js:65:28)
    at require (node:internal/modules/helpers:179:18)
    at requirePage (/Users/claudio/Dev/web/cuecard/node_modules/next/dist/server/require.js:103:84)
    at loadComponentsImpl (/Users/claudio/Dev/web/cuecard/node_modules/next/dist/server/load-components.js:99:57)
    at async DevServer.findPageComponentsImpl (/Users/claudio/Dev/web/cuecard/node_modules/next/dist/server/next-server.js:732:36)
    at async DevServer.findPageComponents (/Users/claudio/Dev/web/cuecard/node_modules/next/dist/server/dev/next-dev-server.js:611:20)
    at async DevServer.renderPageComponent (/Users/claudio/Dev/web/cuecard/node_modules/next/dist/server/base-server.js:2279:24) {
  page: '/api/audio/text-to-speech'
}
 POST /api/audio/text-to-speech 500 in 50ms

Having the same issue using Next 15.1.2

The SDK remains untested and (it looks) incompatible with some new features of Next.js 15. For now, you can downgrade to Next.js 14, or you can connect to Deepgram via a pages/api express-like proxy instead of using the SDK in Next.js specifically

thanks, how do you "connect to Deepgram via a pages/api express-like proxy instead of using the SDK in Next.js specifically" ? is there an example of that?


Appropriate way/configuration to use recaptcha.net instead of google.com with this library

Issue description
As described in https://developers.google.com/recaptcha/docs/faq#can-i-use-recaptcha-globally , the recommended way of making ReCAPTCHA accessible for Chinese users is to replace all calls to google.com to point to recaptcha.net instead.
I realize this may be a long-solved issue for some, but I could not find good documentation on how to best achieve this. On the javascript side, this is trivial. However, the PHP library here also includes a call to the siteverify API that is hard-coded as a constant in the library to point to google.com .
While we could make a local, modified copy of the library, I feel that this is not the right and re-usable way to go about this. But I am unsure how to achieve this best. So it's maybe less a bug report and more of a question?
Environment

google/recaptcha version: 1.2.4

If I'm not misunderstanding, recaptcha.net is just a bypass so it should be fine as far as your frontend can post the g-recaptcha-response to your backend.


Reapply "Let vespa own the /conf/vespa dir."

Reverts vespa-engine/vespa#25437

I think we want to leave the conf/vespa directory as "configuration from outside", so no vespa processes should need to write to it, and it should not be owned by the vespa user.

Sounds good. I seem to have forgotten the reasoning behind this change.


Facing python script deploy issue with a normal user

Hi Team,
I am trying to test the python client script using a normal user credentials (Not an admin user)
The user has required access to view and modify the required folder that I am testing.
But when am trying to deploy the script, its not working properly.

In Control-M EM , I can see after doing a deploy the folder is going to "Not Synchronized" state.

Please help me in fixing this issue.

That looks like a separate issue.  Not synchronized is a problem between Enterprise Manager and Control-M Server.  That would explain why the run isn't working.  This likely has nothing to do with the Python Client.

Python client behaves like Automation API, you have to use a user who has the ability to execute and browse folders and jobs.
What  permissions and privileges are needed to be defined in user security authorizations in order for a user to be able to consume all of the endpoints in Control-M Automation API?


Supported CUDA Version Issue

Hi Zhaofeng, thanks for such great repo! I am just wondering if it possible for the code to support CUDA>11.0? Thanks!

We have that restriction mostly due to DGL. We worked with DGL version 0.4.3.post2 which did not support CUDA 11. You are welcome to try more recent versions of DGL. From their release notes, it seems that there shouldn't be any major backward-incompatible changes.  Feel free to comment here if you run into any issue and I'd be happy to help out. PRs are welcome, of course.

Thank you!!

Closing for lack of activity. Feel free to reopen if you have more questions.


Reinstate armhf which was removed I don't know why

Problem

Cannot upgrade to last version on my Raspberry Pi 3 as armhf/armv7 was removed from the package without warning

Solution

re-add armhf architecture into manifest.toml

PR Status

[ ] Code finished and ready to be reviewed/tested
[ ] The fix/enhancement were manually tested (if applicable)

Automatic tests
Automatic tests can be triggered on https://ci-apps-dev.yunohost.org/ after creating the PR, by commenting "!testme", "!gogogadgetoci" or "By the power of systemd, I invoke The Great App CI to test this Pull Request!". (N.B. : for this to work you need to be a member of the Yunohost-Apps organization)

!testme


Question, How can I add the Widget in Azure DevOps

Where do I find the widget, to add it at the dashboard? Is there a install.md for Azure DevOps?

It's correct installed:

@megel This extension isn't a widget for the dashboard.  It rolls-up under Azure Boards (Boards hub)... This screen capture should help.

Thx!


fix(dom-slider): check if slide methods exist on Node.prototype befor…

…e defining them
This is causing issues with Jest/JSDOM otherwise

Much appreciated 🙏


fix: return error when the datamover exits early

:tada: This PR is included in version 1.1.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


feat: Add a step to validate the filename

check if the filename follow the convention (kebab-case)

Tested with https://github.com/bonitasoft/bonita-documentation-site/pull/791 PR.
Publish a comment on PR with this display when the page filename step is on error.

LGTM, great work! 🎉
I haven't approved the PR yet, because I'd first like to talk about the current situation:
* the warning message about eventual alias creation

* if we do a manual rename operations in all repositories prior merging/releasing this new feature. This is what was planned in [Tool: enforce file name to use kebab-case in documentation content bonita-documentation-site#589](https://github.com/bonitasoft/bonita-documentation-site/issues/589)

Answering to my own questions:

warning message: I am going to propose an alternative
the actions provides a way to skip the step. It is used with a reusable workflow in the documentation content repositories, so by adding a new input to the reusable workflow, it will be possible to disable the step.


android ndk build support

thank you for your effort.
I want to use libquic in android.
Does it currently support android ndk build?
if not,  Is there any plan to support android ndk build ?

It does not support NDK build. Any contributions welcome. :)
Writing Android.mk file is not that hard. If you need any guidelines, I'd be happy to help.

ok. ~ I like to . It seems grateful if you provide a guideline.

See android.mk documentation and samples from https://android.googlesource.com/platform/development/+/7bc5bfc65c1f73f474b45b02d92d01032b79df3c/ndk/samples/
Add source files defined in https://github.com/devsisters/libquic/blob/master/CMakeLists.txt and create a Android.mk file.
See also: https://github.com/bagder/curl/blob/master/packages/Android/Android.mk

@gagoongx2 Hi! Have you any progress with this task? I want to build library on android to, but I try to build it using android studio experimental plugin. If you have any progress, can you describe it?

need this +

there is a quic  android client here
https://github.com/GoogleChrome/cronet-sample


Read the combat log

Hello, I would like to know if with this lib I can read the combat_log in real time.
I intend to create a dataset, with the arena fights.

Hey, no this is intended for 3D formats and data tables. Supported formats are in the readme.


Update people.json

Let me know if I did this correctly or change need to be made :)

Awesome, thanks for doing the first PR! I didn't create the GitHub Action to regenerate the README automatically yet, but I just did, so you are in the repository list now 🎉


Reevaluating a module fails with "is already defined"

Environment

Livebook version: Nerves Livebook 0.8.0

Current behavior
Setting up a livebook based on: https://github.com/wojtekmach/mix_install_examples/blob/main/phoenix_live_view.exs
I'm assuming there are some macro-related problems but I cannot re-evaluate any of the modules without getting the already defined error.
I think Brooklyn and DockYard Academy are hitting something similar: https://github.com/DockYard-Academy/beta_curriculum/issues/622
I imagine it has to do with this:
https://github.com/livebook-dev/livebook/pull/1518
If this is works as intended, good to know, no worries. But it was not expected compared to repasting a module in iex.
Expected behavior
It would be nice if I could refresh that code to update the LiveView for example :)

Hey @lawik, do you have a notebook that reproduces this?

Works for me, both on Livebook v0.8.0 and main. What Elixir version do you use?

Ah, I can reproduce it on v0.8.0 by reevaluating start_link so the notebook crashes, then evaluating everything again. This is #1576 and is fixed on main :)

I really appreciate this fixing-the-bug-before-I-report them approach. Thanks Jonatan :)


Managed identity as a group member?

Can I place a managed identity into an Azure AD group?
Context: we're currently using a managed identity with the Azure service operator for Kubernetes (https://github.com/Azure/azure-service-operator) to provision Azure SQL Managed Users on our databases for applications running on a Kubernetes cluster. After adding the service operator's managed identity to a group and setting the group as the server's AAD admin, the service operator seems unable to authenticate with the server. Is this a known limitation, or am I doing something wrong?

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

ID: 07551795-7de9-95d5-486c-579b8332e054
Version Independent ID: 925ae422-7975-4ecb-eded-4c36a29a95a3
Content: FAQs and known issues with managed identities - Azure AD
Content Source: articles/active-directory/managed-identities-azure-resources/known-issues.md
Service: active-directory
Sub-service: msi
GitHub Login: @barclayn
Microsoft Alias: barclayn

@LukeCarrier Thanks for reaching out. We will investigate and update the thread accordingly.

Hello @LukeCarrier, I apologize for the delayed response on this. I did review your query and had some queries around this. As you mentioned that you were already able to add the managed identity to an AAD group. It would be great if you can share the details as which type of managed identity you are using in this case as for every managed identity a service principal object gets created in the backend that you can add to certain applications or resources as required.
So, I am trying to understand this as I fail to add a service principal object to an AAD group. Hence some more information on this would really help.

Hello @LukeCarrier, it would be great if you can share some more light on this so that we can take this up further.

Hi @souravmishra-msft, apologies for the delay in responding.
After creating a managed identity, we can identify the Azure AD Service Principal created for it in the portal:

We can then make this a member of a group:
$ az ad group member list -g sec_az_alp_data_dev_helm_admin --query "[?servicePrincipalType=='ManagedIdentity'].[displayName,objectId]"
[
  [
    "service-operator",
    "7d0499dd-2c72-496a-98f4-01fc27f99390"
  ]
]

We then configured this group to be the Azure AD admin group of a SQL Server and verified that an ordinary (human) user was able to authenticate with the server, but apparently the machine using the managed identity could not.

Hello @LukeCarrier, thanks a lot for sharing the details about the implementation. I would like to connect with you offline to discuss this further and hence it would be great if you can drop an email with the following details to azcommunity[at]microsoft[dot]com:

Tenant ID:
Azure Subscription ID:
Mentioned this Github Post URL in the email for us to identify it.

Do share the following details and I would like to connect with you to have a look into the issue and help you fix this as soon as possible.

Hello @LukeCarrier, trust you are doing great. I wanted to follow up with you regarding this thread. This issue would need some in-depth look around and for that, a screen sharing session would be best for us to analyze the issue and device the next set of actions on it. Please do drop us an email on azcommunity[at]microsoft[dot]com or reply to my earlier followup email that I had sent with the email subject as "ATTN: soumi" and a suitable time to schedule the call so that we can take this forward.
We are closing this thread for now. Do get connected with us on the email so that we can drive this further and help you fix the issue as soon as possible.

Hi @souravmishra-msft, apologies for the delay in responding.
After creating a managed identity, we can identify the Azure AD Service Principal created for it in the portal:

We can then make this a member of a group:
$ az ad group member list -g sec_az_alp_data_dev_helm_admin --query "[?servicePrincipalType=='ManagedIdentity'].[displayName,objectId]"
[
  [
    "service-operator",
    "7d0499dd-2c72-496a-98f4-01fc27f99390"
  ]
]

We then configured this group to be the Azure AD admin group of a SQL Server and verified that an ordinary (human) user was able to authenticate with the server, but apparently the machine using the managed identity could not.

@LukeCarrier, do you mind sharing how did you add managed identity to aad group? I got this error:
az ad group member add --group mygroup --member-id xxxxx-xxxx-...
Directory object type: ServicePrincipal cannot be added to Unified Groups. paramName: Members, paramValue: , objectType: Microsoft.Online.DirectoryServices.Group


Threading

Fixes: #18

@vgel Hey there! I think I merged it correctly now. Your drop tests pass :). I Added the same MaybeUninit code to the AllocRingbuffer because when the buffer gets full it may need to replace items with uninitialized items. Thanks again for the help!

It's now possible to pre-initialize the AllocRingbuffer with Maybeuninit items. That might make the AllocRingBuffer a little faster.


twister: tests: Refactor and expand testing scopes

Minor changes to the test_config.yaml. Switch to inheritance instead of repeating the scope and extend the scope with some generic driver tests

The driver tests to add where consulted with @anangl. Those are probably generic enough to be able to run on all referece (tier 1) boards.

related to https://github.com/zephyrproject-rtos/zephyr/issues/64087


Image-stack 2 is missing :)

Tried to find it in the project history and couldn't.

Hi @neoswf!
Thanks for noticing, added it for gbi's issue #93 and forgot to remove it again % ).
Just pushed the fix for it.
But should you'd rather want the file to exist, here are the contents of pages/image-stack-2.js:
import React from 'react'
import styled from 'styled-components'

import Layout from '../components/Layout'
import SEO from '../components/SEO'
import {
  StyledContentCenterWrapper,
  StyledImageWrapper,
} from '../components/SharedStyledComponents'
import GbiStacked from '../components/GbiStacked'
import StyledFullBackground from '../components/FullBackground'

const StyledCenterWrapper = styled(StyledContentCenterWrapper)`
  max-width: 800px;
  margin-top: 5rem;
`

const StyledOutsideLink = styled.a`
  margin-left: 0.32rem;
`

const MultipleStackedBackgroundImages = () => (
  <Layout>
    <SEO title="Multiple Stacked Background Images" />

          .

 All attribution goes to them : )!

      </StyledCenterWrapper>
    </StyledFullBackground>
  </Layout>
)

export default MultipleStackedBackgroundImages

Thanks again - and the honor of closing this issue is all yours : )!
Best,
Tim.

Thank you @timhagn !!!!!

Great, happy to have been of help : ).


Provide a "temporary download folder" option

The user should be able to specify, where the video parts get stored while being downloaded.

Fixed!


ENH add some options for a smaller image

This PR slims down the docker image a bit.

Approximately, yes.


Can it support for Hbase Hlive clickhouse  database ?

Can it support for Hbase Hlive clickhouse  database ?

Unfortunately those are not supported databases at this time. Pull requests would be gladly accepted if someone would like to work on them :)

ClickHouse is added in master/ latest on Docker Hub, and Hbase and Hive are supported via the ODBC integration.
Open to accepting PRs if anyone wants to work on adding Hbase/Hive specific drivers, but going to close this issue for now.

@zhaodagang you can use presto connection instead. presto can support hive connector  and hbase connector


read time out

Search before asking

[X] I had searched in the issues and found no similar issues.

What happened
in process,the http reponse will take place 500
java sockeTimeoutException: read time out
What you expected to happen
wait the result
How to reproduce
in process,the http task will request a test task  that need time
but read time out
Anything else
no
Are you willing to submit PR?

[ ] Yes I am willing to submit a PR!

Code of Conduct

[X] I agree to follow this project's Code of Conduct

another same issue exists, so i close this one.


feat: wat compiler

Pull Request Test Coverage Report for Build 164146044

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 78.488%

Totals

Change from base Build 164084640:
0.0%

Covered Lines:
581

Relevant Lines:
688

💛  - Coveralls


Clean up test_views.py

This PR makes two improvements to our test_views test suite:

We had two similar test_chant_with_volpiano_with_no_incipits defined within ChantDetailViewTest. The second of these has been removed
AjaxSearchBarTest.test_cantus_id_search has been refactored to be deterministic (we had been creating two chants, and only the first had a cantus_id specified. When the other chant's cantus_id began with a 1 (P=0.1), the test would fail. Now, both chants' Cantus IDs are specified). This fixes #1244.

#1244 has a pending draft PR in #1245, but this should be a quicker and better way of getting the issue fixed!


[Feature] Add call_with_overrides method on CallBuilder returning decoded output, not raw

Component
contract, provider, pubsub
Describe the feature you would like
In order to make calling with state overrides from contract instances easier I propose we add a new method call_with_overrides. This would have the same behavior as call_raw with a state override and then decoding the output.
https://github.com/alloy-rs/alloy/blob/25916cd88c153d0546afc8730530ee7cc30d665f/crates/contract/src/call.rs#L349-L370
Additional context
No response

PR is redundant, resolved by better documenting how state overrides are applied


Enhancement: Homestatus widget

ToDo: make it compatible to RESIDENTS and  ROOMMATE
Status: unassigned

done: http://forum.fhem.de/index.php/topic,34233.msg280885/topicseen.html#msg280885


File dependency

Add dependencies capabilities.

List of dependencies name for python,
Paste package.json for node
Paste Gemfile for ruby.

@andresmgot can you review ?

@andresmgot yes we can edit the dependencies, in the Edit modal


fix: Window now closes when 'x' is clicked

The commit 30a251c has made the biscuit window to not close when 'x' is clicked. This is probably due to the "WM_DELETE_WINDOW" protocol only calling the on_close_app function, which does not destroy() the tkinter window.
I checked the previous commit c9dd044 and this does close the window, so i guess the addition of the "WM_DELETE_WINDOW" protocol might have introduced the bug

@vyshnav-vinod thanks for opening a pr on this! apparently the window is closable with the window close button currently on windows, but technically the problem is existing. Unsure of what is causing the behavior difference.


Fuzzing

It'd be great if we could do some amount of fuzz testing with AFL or another tool. Due to the nature of Diesel I'm not sure how that would even work, but it's something I'm interested in having done.

Hey ! Any particular areas you would like to see fuzzed first ? data coming from the database connection ? user-supplied queries ? something entirely different ? I can try taking a look into hooking up cargo-fuzz in some nearish future I think.

I would expect parsing the data coming out of the database would be the most interesting.
Be warned, though. You'll probably have to do a whole bunch of freaky things to get access to these function in a way you can fuzz them. I was originally thinking stuff like #[path="../../diesel/pg/lorem/ipsum.rs"] mod ipsum; in the fuzzer script but I'm not sure if that'd work well.

Am 23.05.2017 um 20:57 schrieb Cyryl Płotnicki<EMAIL_ADDRESS>Hey ! Any particular areas you would like to see fuzzed first ? data coming from the database connection ? user-supplied queries ? something entirely different ? I can try taking a look into hooking up cargo-fuzz in some nearish future I think.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

No worries, I consider myself warned now :) If I get to work on this in some time and get stuck - will definitely describe what I did and what worked and what not. thanks a lot !

We already have tests for that @killercup (types_roundtrips)

Thank you for giving it a try :) Feel free to drop into gitter if you get stuck, I'm sure we can figure out how to get this working.
@Eijebong, sure, but types roundtrips usually only test valid data. Fuzzing makes sure we don't explode when we get invalid data :)

Am 23.05.2017 um 21:05 schrieb Cyryl Płotnicki<EMAIL_ADDRESS>No worries, I consider myself warned now :) If I get to work on this in some time and get stuck - will definitely describe what I did and what worked and what not. thanks a lot !
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Oh, ok :)

Hey, haven't had much luck/time to really take this on so far, feel free to pick it up if someone else is interested. Would love to pair on this one if you want btw. I will take a second look when I'll have some more time. Thank you !


Support remote Chrome

Hi,
is it possible to add support for remote Chrome? (ex: running in Docker)
I'm running cloudflare-scraper on headless machine (no X, no Chrome installed) and I'd like to solve Cloudflare puzzle, retrieve cookie and continue my scrapping using different tool.
I was able to do it, but I needed to do some dirty code patching first.

Can you tell me more ? What did you have to patch ? If you can override puppeteer options, is it enough ?

Hi,
sorry I could be more specific.
This what I'm doing:
I have running chrome with remote debugger in docker (I'm using selenium-standalone-chromium-debug). Then I can discover websocker URL from:
http://<IP_ADDRESS>:21222/json/version (21222 is mapped from container)
Next (I was still using 42308d8f2d180eaff86d5798d6f8faf756d68371) by changing puppeteer.launch(puppeteerOptions) to puppeteer.connect({browserWSEndpoint: 'ws://<IP_ADDRESS>:21222/devtools/browser/...'}) in fillCookiesJar.js
I was able to connect to chrome and play with website I want.
Then after solving Cloudflare puzzle I can retrieve cookie and user-agent.
I didn't play with puppeteer alot so I don't know if there any options than be exported here.
But creating cloudflareScraper with url paramater to remote dbg could be nice thing.

I made the changes, you should be able to connect to your remote chrome in the last version (1.0.5).
let response = await cloudscraper.get('https://your-url.com', { browserWSEndpoint: 'http://<IP_ADDRESS>:21222/json/version'});


Cross Highlighting Support

Fantastic visual.
It seems Deneb can cross filter and cross highlight other visuals (where other visuals support cross highlighting like the bar chart below).

However, the inverse seems to be that other visuals can only cross filter Deneb but not cross highlight as per the image below when clicking on France in the table.

Is this correct? Is it possible to cross highlight Deneb charts instead of cross filtering them?

Thanks for taking the time to provide feedback! I appreciate it :)
Cross-highlighting is quite complicated to handle generically in a visual and will require more thought (and will more investment from you as a creator to manage how your design should work visually). This has already been raised in #134 with current thoughts documented so I'd suggest continuing any discussions in there.


Tool to validate customer environment prior to installing hybrid cloud

@bashofmann might there be value in a tool to validate the customer environment before they install hybrid cloud?

the tool could interrogate the local system to check for the prerequisites and generate appropriate warnings before the customer commences an install that may result in an unusable &/or unhealthy cluster
the tool could be updated as and when we validate (or contraindicate) environments to host the remote clusters

Added in https://github.com/qdrant/qdrant-cloud-support-tools/tree/main/hybrid-cloud-prerequisites


3.x release or SSL in 2.x?

The Heroku Kafka CLI has been running with this patched 2.x branch (patch adds SSL support):

https://github.com/hunterloftis/kafka

We would love to get the CLI pointed back at this official lib, but can't without either SSL in 2.x or with the SSL in the unreleased 3.x branch.
Are there features slowing down the 3.x release? If so, and you can describe them, we may be able to help expedite that branch. Alternatively, what do you think of merging SSL into the next 2.x release? Currently, with neither of those complete, no version of no-kafka supports secure connections.

@hunterloftis I was wondering the same thing in #110.
I've been porting some of the SSL changes from the 3.0 branch into my fork if you wanted to take a look.
I was also aiming to add SASL PLAIN which would require 10.0, but maybe they could be delivered separately.

Hi @oleksiyk. Any chance of releasing SSL in 2.X? I have been using branch 3.X without problems, but we would like to use the latest NPM release to keep up to date with bug fixes.

I think I'll just release 3.0. Without full support for Kafka 10.0

Hi @oleksiyk, are you still planning to release 3.0 without full 0.10 support? Thanks.

Is there anything we can do to help get a release out with SSL support? Would just like to know what barriers exist so we can support you however possible and expedite things.

I've published version 3.0.0. Sorry everyone for the huge delay.


Add rpc methods to serialise the world state

It can be useful to be able to serialize the accounts & their states post deployment.
To allow external tools to interact with ganache and get this information there would need to be two additional rpc calls:
evm_getAccountState() -> to return a tuple (address, balance, nonce, code, storage)
evm_getAccounts() -> to return a list [address, address, ...]

Context
These two methods have single responsibilities, so there can be several applications.
I'm looking to construct a json object that looks like:
{
    evmState: {
        0xa03.....: {
            balance: 100,
            nonce: 0,
            code: "0x6064....",
            storage: {0: "0x00000000000001202030...", 1: "0x10"}
        }
    }
}

What's the proposed method of formulating the interface & return data structure for new custom rpc calls?
ps. I'm 100% down to contribute the code for these rpc calls 👍.

Closing this for issue maintenance. @JoranHonig let us know if you'd like to continue the conversation here and we can re-open. Thanks!


fix glow layer kernel set

related to https://forum.babylonjs.com/t/glowlayers-kernelblursize-is-reset-on-canvas-resize/34495
superseeds https://github.com/BabylonJS/Babylon.js/pull/13063

@sebavan did you mean for this to be a breaking change? Because before the value passed to the kernel setter was the actual value used by the Blur PPs but now that value is halved. The test PG below shows the issue if you compare it before and after the PR is merged.
https://playground.babylonjs.com/#RPA5G8
https://playground.babylonjs.com/?snapshot=refs/pull/13068/merge#RPA5G8


Create freeze/tag for the version on crates.io?

Might be a good idea to make a tag for the current version released on crates.io. I think this commit is the point-in-time. a0200a2

I was wrong about the commit. This one is a little "later" than what is on crates.io, but it seems to be the last one before major rework (which broke the esp haha) so maybe a minor version bump on crates.io with this commit and we can continue troubleshooting main?


Add unpublishing dev mgmt command

Goes along with the documentation for unpublishing.
Ticket
https://trello.com/c/7IkxeDcb

latest boolean includes drafts - it literally just means, "Is this the latest record existing for a measure version?"
So I think it can stay set to whatever it is at the moment.

@samuelhwilliams ah yeah. I always forget that... Doh.


Wrong Creds

I am trying to check if your script works. I have followed the instructions. Wen i run the script it's showing me ERROR Wrong credentials specified!.  Can you help me with this why i am getting this error?

Hi,
Just to be sure, are you able to login into the web application with the same credentials? Does your password contain a backslash \? That could escape the JSON double-quotes and might be the issue here.

HI,
I am able to login into the web application with the same credentials. No, Password doesn't contain any backslash.
Instead, I am logging in by using log in with Google. Is there any chance using the different login mechanism the script is not recognizing the credentials?

Sorry, the script won't work with those credentials.
I've seen the option for signing in with Google and other OAuth providers but since I can't publicly signup with them, I can't write a module for it in the script.
If you want to, I can take a look at how the authentication is happening using your credentials. Let me know if you're up for it.

Closing due to no response