Successfully logged into Azure! – Failed to setup project: EPERM: operation not permitted (Visual Studio Publishing)

Please can anyone help me out this stated after upgrading visual studio
Authenticating with Static Web Apps...
swa.cmd login --subscription-id 05684fd7-3bfe-4cc1-b4ad-ca41bcc98de1 --tenant-id a32d1fb1-51f6-435a-88f3-e44052f3e884 --app-name Pinkinetics --resource-group Pinkinetics --no-use-keychain
Welcome to Azure Static Web Apps CLI (1.1.8)
Checking Azure session...
✔ Successfully logged into Azure!
âœ– Failed to setup project: EPERM: operation not permitted, open 'C:\Program Files\Microsoft Visual Studio\2022\Enterprise\Common7\IDE.env'
âœ– If you believe this behavior is unexpected, please raise a GitHub issue at:
https://github.com/Azure/static-web-apps-cli/issues/new/choose

Windows 11
Blazor  wasm app

Additional context
Add any other context about the problem here.

The workaround was to use the cli (swa)  hope it helps

Dupe of #836


Using ifUserInGroup directive with no group: this.groups.filter is not a function

When logged in with a user not in any group.
Using ifUserInGroup like this:

...

I get this in the console:
TypeError: this.groups.filter is not a function
    at User.inGroup (stormpath-sdk-angularjs.js:2002)
    at User.groupTest (stormpath-sdk-angularjs.js:2022)
    at evalElement (stormpath-sdk-angularjs.js:611)
...

My bower.json:
{
  "name": "app",
  "dependencies": {
    "angular": "~1.4.5",
    "angular-ui-router": "ui-router#~0.2.15",
    "bootstrap": "~3.3.5",
    "font-awesome": "~4.4.0",
    "stormpath-sdk-angularjs": "~0.7.0"
  }
}

Hello Pierre, this problem is now fixed in version 0.7.1
If you are using express-stormpath in your server, please make sure to update that module to 2.0.10 because it has the server-side fix as well :)


Easy to use from CLI and npm run-script

before:
./node_modules/touch/bin/touch.js FILE
after:
$(npm bin)/touch FILE

Ah, strange, I thought that the bin was already listed.  Thanks.
Btw, in npm run-script commands, you can just do touch and it'll find the one in node_modules/.bin, because of PATH environment magic.

Travis failure is unrelated.

Landed on master and published.  thanks!

@isaacs Thanks! :smile:


Fixes to ch11 notebook for DeepChem HEAD

This PR fixes some issues in the Chapter 11 notebooks that break them on DeepChem HEAD. However, I think these fixes would break the notebooks on DeepChem 2.3
@peastman Should we go ahead and merge in these fixes or should we try to maintain a DeepChem 2.3 version of the notebooks before we merge in?

It looks like we never made a release for the DeepChem 2.3 versions.  We should first make that release, and then we can start updating them for 2.4.


New features and fixes

Request Dummy to Jump
Request Dummy to Enter/Exit Vehicle
Fix problem that causess not giving /admin to dummy

Requesting jump is possible with command /dummy jump <id> or from code:

Dummyuser.Jump();

Requesting enter/exit is also possible with command /dummy ride <id> [--exit].
Will look into later.

I'm planning to rewrite this project to make it modular for my future projects, but no time at all

Fix problem that causess not giving /admin to dummy

Do /unadmin on the dummy then do /admin, that seems to work


Include zooming options in View menu

As a followup to #38: the View menu should include:
Zoom In Ctrl++
Zoom Out Ctrl+-
Original magnification Ctrl+0

Will it be useful? We have already implemented keyboard shortcuts for zooming feature. We can document it somewhere.

@akashnimare Yes, it's useful. Accessibility best practices in browsers and in desktop applications in general say that if something's possible to do via a keyboard shortcut, it should also be discoverable via the dropdown menus. And I myself am much more likely to first look at the options available to me via the dropdown menus, and to expect that zooming options would be listed there under View.

If there's a specific reason to avoid adding this to the View menu, I'm open to hearing it. But desktop applications that support zooming (browsers, LibreOffice, Thunderbird, etc.) usually include a Zoom item in their View menu or someplace similar (for instance, it's an expected option in the Window menu for Apple applications), even when they also support a keyboard shortcut for it. In general, if a user has to go read documentation in order to use a feature, that's much less optimal than if we could have provided them with an easy discovery through the user interface.

Cool then let's add it 👍 .

@brainwane Added zooming options in Menu.


Pytorch Lightning 2.0.8 cannot find neptune.new.utils with Neptune-client 0.16.3

Bug description
Bug:
import pytorch_lightning as pl fails with error message No module named 'neptune.new.utils', but I have Neptune-client 0.16.3. More interestingly, the code runs perfectly on an env that does not even have neptune-client installed.
I have reproduced on a clean environment (see steps below), and I was able to import Lightning up until the point where I installed Neptune-client. Then, the import fails with the error message presented here.
My problem is that I need to use Lightning in an env a customer provided us, which uses Neptune-client as indicated, and I am therefore unsure on whether we can remove/change that package.
This is on Python 3.10.12.
Error traceback:
ModuleNotFoundError                       Traceback (most recent call last)
File [main.py] in line 7
      1 #%%
      2 # basic libraries
      3 #import  os
      4 #import  yaml
      5
      6 # pytorch lightning
----> 7 import  pytorch_lightning           as      pl
      8 from    lightning.pytorch           import  Trainer
      9 from    lightning.pytorch.loggers   import  TensorBoardLogger

File [~/miniforge3/envs/test_env/lib/python3.10/site-packages/pytorch_lightning/__init__.py:26]
     23     _logger.propagate = False
     25 from lightning_fabric.utilities.seed import seed_everything  # noqa: E402
---> 26 from pytorch_lightning.callbacks import Callback  # noqa: E402
     27 from pytorch_lightning.core import LightningDataModule, LightningModule  # noqa: E402
     28 from pytorch_lightning.trainer import Trainer  # noqa: E402

File [~/miniforge3/envs/test_env/lib/python3.10/site-packages/pytorch_lightning/callbacks/__init__.py:29]
     27 from pytorch_lightning.callbacks.prediction_writer import BasePredictionWriter
     28 from pytorch_lightning.callbacks.progress import ProgressBar, RichProgressBar, TQDMProgressBar
---> 29 from pytorch_lightning.callbacks.pruning import ModelPruning
     30 from pytorch_lightning.callbacks.rich_model_summary import RichModelSummary
...
     56 else:
     57     # needed for tests, mocks and function signatures
     58     neptune, Run, Handler, File, stringify_unsupported = None, None, None, None, None

ModuleNotFoundError: No module named 'neptune.new.utils'

What version are you seeing the problem on?
v2.0
How to reproduce the bug
Create new environment
conda create -n test_env

Install Pytorch 1.11.0
conda install pytorch==1.11.0 torchvision==0.12.0 torchaudio==0.11.0 -c pytorch

Install Pytorch Geometric (the one for Pytorch 1.11)
pip install torch-scatter torch-sparse torch-cluster torch-spline-conv torch-geometric -f https://data.pyg.org/whl/torch-1.11.0+cpu.html

Install Pytorch Lightning (note that lightning 2.0 is compatible with Pytorch 1.11, see compatibility matrix https://lightning.ai/docs/pytorch/stable/versioning.html)
python -m pip install lightning

Install neptune-client 0.16.3
pip install neptune-client==0.16.3

Try importing Pytorch Lightning
import pytorch_lightning as pl

Obtain error message above.

### Environment

<details>
  <summary>Current environment</summary>

#- Lightning Component (e.g. Trainer, LightningModule, LightningApp, LightningWork, LightningFlow):
#- PyTorch Lightning Version: 2.0.8
#- PyTorch Version: 1.11.0
#- Python version: 3.10.12
#- OS: McOS Ventura 13.4.1

</details>

cc @Blaizzy

@filipporemonato It looks like the neptune.new module was removed at some point. You can work around the issue for now by uninstalling neptune-client (legacy) and installing pip install neptune instead.

Thanks Adrian! Yes that's what I thought too. It may work as a workaround for now, but as said Neptune-client comes from the customer's env, so I am not sure if it will be possible to change it and go over to Neptune. But it should be (bar some backward-compatibility issues).
I guess my post here was more about the strange fact that all goes smoothly as long as Neptune-client is not installed. It seems a bit weird that installing a package "breaks" the usage of Lightning, especially if Lightning can well be used without that package at all.
Thanks for the suggestion about Neptune though.
From: Adrian Wälchli @.>
Sent: torsdag 14. september 2023 18:51
To: Lightning-AI/lightning @.>
Cc: Filippo Remonato @.>; Mention @.>
Subject: Re: [Lightning-AI/lightning] Pytorch Lightning 2.0.8 cannot find neptune.new.utils with Neptune-client 0.16.3 (Issue #18555)
@filipporemonatohttps://github.com/filipporemonato It looks like the neptune.new module was removed at some point. You can work around the issue for now by uninstalling neptune-client (legacy) and installing pip install neptune instead.

Reply to this email directly, view it on GitHubhttps://github.com/Lightning-AI/lightning/issues/18555#issuecomment-1719804260, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABPSTZTS2RMAO2DYITIP7ALX2MYYTANCNFSM6AAAAAA4X7ZDKU.
You are receiving this because you were mentioned.Message ID<EMAIL_ADDRESS>

@filipporemonato , @awaelchli
utils was introduced in neptune.new only in version 0.16.16. Since you are using neptune-client==0.16.4, this import will fail.
I will push a change to fix this in the Lightning repo.
For now, you can either update to neptune as suggested above (preferred), or comment out line 55 of pytorch_lightning/loggers/neptune.py:
elif _NEPTUNE_CLIENT_AVAILABLE:
    # <1.0 package structure
    import neptune.new as neptune
    from neptune.new import Run
    from neptune.new.handler import Handler
    from neptune.new.types import File
    # from neptune.new.utils import stringify_unsupported

Here's an upgrade guide to Neptune 1.0+: https://docs.neptune.ai/setup/neptune-client_1-0_release_changes/

@SiddhantSadangi What should be done here? Options:

Set 0.16.16 as the minimum supported version
Change the import (to what?)
Copy the implementation of stringify_unsupported to support it in older versions.

@awaelchli - 1 would be the most viable option until we submit a fix to pytorch_lightning

No @SiddhantSadangi I'm talking about the fix. These are the three options I see to fix it in the NeptuneLogger implementation in Lightning. So of these 3 options, which one do you want me to do? Or do you see another one?

@awaelchli Hello! Let me share my experience. I met the same issue. The easiest solution is to do pip uninstall neptune-client then pip install neptune, but make sure that everything of neptune-client was replaced. After this my pipeline started to work without any problems.
current versions in pip are:
neptune                     1.6.3
neptune-contrib       0.28.1

@ArtemSivtsov - that's the recommended solution, however sometimes users are constrained with the packages they can install, and that might prevent them from upgrading to neptune>=1.0

@awaelchli - for the fix, I was thinking of introducing a _STRINGIFY_UNSUPPORTED_AVAILABLE  flag and updating the import to the below:
_STRINGIFY_UNSUPPORTED_AVAILABLE = True
...
elif _NEPTUNE_CLIENT_AVAILABLE:
  ...
  # Needed for neptune-client<0.16.16
  try:
      from neptune.new.utils import stringify_unsupported
  except ModuleNotFoundError:
      _STRINGIFY_UNSUPPORTED_AVAILABLE = False
...
def log_hyperparams(self, params: Union[Dict[str, Any], Namespace]) -> None:  # type: ignore[override]
  ...
  if _STRINGIFY_UNSUPPORTED_AVAILABLE:
      self.run[parameters_key] = stringify_unsupported(params)
  else:
      self.run[parameters_key] = params

neptune-client<0.16.16 doesn't need stringify_unsupported, so the logging should be fine.
Full file attached as .txt below:
neptune.txt
I can push a PR if this works for you.

@Raalsky does #19265 close this issue?

@awaelchli Yes. It closes in with a meaning that it won't be supported anymore.


feat: add aperture on azure marketplace

Description of change
Checklist

[ ] Tested in playground or other setup
[ ] Screenshot (Grafana) from playground added to PR for 15+ minute run
[ ] Documentation is changed or added
[ ] Tests and/or benchmarks are included
[ ] Breaking changes

Summary by CodeRabbit

New Feature: Added support for Azure-specific configurations in the Aperture Agent and Controller Helm charts. This includes conditional logic for image tag retrieval and endpoint creation, as well as additional pod labels.
New Feature: Introduced a new job in the CI/CD pipeline to publish the application on Azure Marketplace. This includes setup for remote Docker, installation of necessary dependencies, modification of values.yaml file, and pushing bundles to Azure registry.
Chore: Updated the circleci package version from 0.1.26343 to 0.1.27054 for improved tooling.

Closing to reduce clutter


Remove unnecessary string concatenation in plugin path configuration

Description
Please describe your pull request:

Why is it necessary?
Cleaner code and less string operations
What does it improve?
See above
Does it have side effects?
No

I also fixed the coding style although this is already done in the 5.3 branch, but the merge will be less painful

Questions
Answers

BC breaks?
no

Tests pass?
yes

Related tickets?
-

How to test?
Apply patch, nothing should change.

Hello,
thank you for creating this pull request.
I have opened an issue on our Issue Tracker for you. See the issue link: https://issues.shopware.com/issues/SW-18148.
Please use this issue to track the state of your pull request.

thanks for your contribution @aragon999 :+1: your PR will be merged soon


Working with Langchain I get nlkt errors telling me: Package "tokenizers" not found in index and Packaage "taggers" not found in index

Issue you'd like to raise.
I'm trying to load some documents, powerpoints and text to train my custom LLm using Langchain.
When I run it I come to a weird error message where it tells I don't have "tokenizers" and "taggers" packages (folders).
I've read the docs, asked Langchain chatbot, pip install nltk, uninstall, pip install nltk without dependencies, added them with nltk.download(), nltk.download("punkt"), nltk.download("all"),... Did also manually put on the path: nltk.data.path = ['C:\Users\zaesa\AppData\Roaming\nltk_data'] and added all the folders. Added the tokenizers folder and taggers folder from the github repo: . Everything. Also asked on the Github repo. Nothing, no success.
Here the code of the file I try to run:
`
from nltk.tokenize import sent_tokenize
from langchain.document_loaders import UnstructuredPowerPointLoader, TextLoader, UnstructuredWordDocumentLoader
from dotenv import load_dotenv, find_dotenv
import os
import openai
import sys
import nltk
nltk.data.path = ['C:\Users\zaesa\AppData\Roaming\nltk_data']
nltk.download(
'punkt', download_dir='C:\Users\zaesa\AppData\Roaming\nltk_data')
sys.path.append('../..')
_ = load_dotenv(find_dotenv())  # read local .env file
openai.api_key = os.environ['OPENAI_API_KEY']
folder_path_docx = "DB\ DB VARIADO\DOCS"
folder_path_txt = "DB\BLOG-POSTS"
folder_path_pptx_1 = "DB\PPT DAY JUNIO"
folder_path_pptx_2 = "DB\DB VARIADO\PPTX"
loaded_content = []
for file in os.listdir(folder_path_docx):
if file.endswith(".docx"):
file_path = os.path.join(folder_path_docx, file)
loader = UnstructuredWordDocumentLoader(file_path)
docx = loader.load()
loaded_content.extend(docx)
for file in os.listdir(folder_path_txt):
if file.endswith(".txt"):
file_path = os.path.join(folder_path_txt, file)
loader = TextLoader(file_path, encoding='utf-8')
text = loader.load()
loaded_content.extend(text)
for file in os.listdir(folder_path_pptx_1):
if file.endswith(".pptx"):
file_path = os.path.join(folder_path_pptx_1, file)
loader = UnstructuredPowerPointLoader(file_path)
slides_1 = loader.load()
loaded_content.extend(slides_1)
for file in os.listdir(folder_path_pptx_2):
if file.endswith(".pptx"):
file_path = os.path.join(folder_path_pptx_2, file)
loader = UnstructuredPowerPointLoader(file_path)
slides_2 = loader.load()
loaded_content.extend(slides_2)
print(loaded_content[0].page_content)
print(nltk.data.path)
installed_packages = nltk.downloader.Downloader(
download_dir='C:\Users\zaesa\AppData\Roaming\nltk_data').packages()
print(installed_packages)
sent_tokenize("Hello. How are you? I'm well.")
`
When running the file I get:
`
[nltk_data]     in index
[nltk_data] Error loading tokenizers: Package 'tokenizers' not found
[nltk_data]     in index
[nltk_data] Error loading taggers: Package 'taggers' not found in
[nltk_data]     index
[nltk_data] Error loading tokenizers: Package 'tokenizers' not found
[nltk_data]     in index
[nltk_data] Error loading tokenizers: Package 'tokenizers' not found
[nltk_data]     in index
[nltk_data] Error loading tokenizers: Package 'tokenizers' not found
[nltk_data]     in index
[nltk_data] Error loading taggers: Package 'taggers' not found in
[nltk_data]     index
[nltk_data] Error loading tokenizers: Package 'tokenizers' not found
[nltk_data]     in index
[nltk_data] Error loading tokenizers: Package 'tokenizers' not found
[nltk_data]     in index
[nltk_data] Error loading tokenizers: Package 'tokenizers' not found
[nltk_data]     in index
[nltk_data] Error loading tokenizers: Package 'tokenizers' not found
[nltk_data]     in index
[nltk_data] Error loading taggers: Package 'taggers' not found in
[nltk_data]     index
[nltk_data] Error loading tokenizers: Package 'tokenizers' not found
[nltk_data]     in index
[nltk_data] Error loading tokenizers: Package 'tokenizers' not found
[nltk_data]     in index
[nltk_data] Error loading tokenizers: Package 'tokenizers' not found
[nltk_data]     in index
[nltk_data] Error loading tokenizers: Package 'tokenizers' not found
[nltk_data]     in index
[nltk_data] Error loading taggers: Package 'taggers' not found in
[nltk_data]     index
[nltk_data] Error loading tokenizers: Package 'tokenizers' not found
[nltk_data]     in index
[nltk_data] Error loading tokenizers: Package 'tokenizers' not found
[nltk_data]     in index
[nltk_data] Error loading tokenizers: Package 'tokenizers' not found
[nltk_data]     in index
[nltk_data] Error loading tokenizers: Package 'tokenizers' not found
[nltk_data]     in index
[nltk_data] Error loading taggers: Package 'taggers' not found in
[nltk_data]     index

HERE SOME TEXT -

['C:\Users\zaesa\AppData\Roaming\nltk_data']
dict_values([, , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , , ])
`
And here is how my folders structure from nltk_data looks like:

Suggestion:
I have fresh installed nltk with no dependencies. The version is the latest. The support team from NLTK doesn't know what is wrong. It seems everything is fine. So, it has to be a bug or something coming from Langchain that I'm not able to see. Really appreciate any help. Need to make this work! Thank you.

I encounter a similar issue. I am using the qachain and running code I have run a lot of times before, but now getting this:
[nltk_data] Error loading tokenizers: Package 'tokenizers' not found
[nltk_data]     in index
[nltk_data] Error loading tokenizers: Package 'tokenizers' not found
[nltk_data]     in index
[nltk_data] Error loading tokenizers: Package 'tokenizers' not found
[nltk_data]     in index
[nltk_data] Error loading tokenizers: Package 'tokenizers' not found
[nltk_data]     in index
[nltk_data] Error loading tokenizers: Package 'tokenizers' not found
[nltk_data]     in index
[nltk_data] Error loading tokenizers: Package 'tokenizers' not found
[nltk_data]     in index
[nltk_data] Error loading tokenizers: Package 'tokenizers' not found
[nltk_data]     in index
[nltk_data] Error loading tokenizers: Package 'tokenizers' not found
[nltk_data]     in index
[nltk_data] Error loading taggers: Package 'taggers' not found in
[nltk_data]     index
LookupError                               Traceback (most recent call last)
 in <cell line: 10>()
8
9 # get the langchain qa chain for the given company
---> 10 qa = get_company_qa_chain(text_dir_path)
17 frames
/usr/local/lib/python3.10/dist-packages/nltk/data.py in find(resource_name, paths)
581     sep = "*" * 70
582     resource_not_found = f"\n{sep}\n{msg}\n{sep}\n"
--> 583     raise LookupError(resource_not_found)
584
585
LookupError:

Resource averaged_perceptron_tagger not found.
Please use the NLTK Downloader to obtain the resource:

import nltk
nltk.download('averaged_perceptron_tagger')

For more information see: https://www.nltk.org/data.html
Attempted to load taggers/averaged_perceptron_tagger/averaged_perceptron_tagger.pickle
Searched in:
- '/root/nltk_data'
- '/usr/nltk_data'
- '/usr/share/nltk_data'
- '/usr/lib/nltk_data'
- '/usr/share/nltk_data'
- '/usr/local/share/nltk_data'
- '/usr/lib/nltk_data'
- '/usr/local/lib/nltk_data'

Thanks for sharing.
So have you come to a solution or are you facing the same problem.
Appreciate

Sadly, I am facing the same problem and still trying to find the solution. I was just adding some further context in the hope that it could help us. If I find a solution, I will definitely share it here!

I found a workaround, for my situation anyway. The problem seems to be with the Directory loader. I went from:
loader = DirectoryLoader(text_dir, glob="*.txt", recursive=True, silent_errors=True)
to
loader = DirectoryLoader(text_dir, glob="*.txt", recursive=True, silent_errors=True, loader_cls=TextLoader)
You will also need:
from langchain.document_loaders import DirectoryLoader, TextLoader
Hopefully that works for you too.

Upgrading to the latest unstructured fixed for me pip install -U unstructured.  See https://github.com/Unstructured-IO/unstructured/commit/e017e99b5ba3226249b34d6c0920bd7c4301da4e

Oh sorry I didn't notice you're the same one that posted on the nltk issue.


Picamera install in virtual environment

I already installed virtual environment.
When I was working on it, I installed picamera by using command:
pip-3.2 install "picamera[array]"
after that, I tried:
python (still in virtualenv)
and then:
import picamera
but at this time, I got an error saying that: "ImportError: No module named "picamera"
And then I tried:
pip freeze
it gave me:
appdirs==1.4.3
numpy==1.12.1
packaging==16.8
pyparsing==2.2.0
six==1.10.0
There is not picamera there!!!
When I log out the virtual environment, and retry python and import picamera, it worked!
But I need to work on the virtual environment, anyone can help me please??

Have you managed to solve this problem? I am running into the same issue.

You might not be using the pip from the virtualenv (typically the pip native to a venv is just called "pip" so there's no need for a version suffix). After activating the venv, ask bash which pip it's using. If it's the one in /usr/bin run hash -r to clear out bash's cache of pathnames then try again:
$ source myvenv/bin/activate
(myvenv) $ which pip
/usr/bin/pip
(myvenv) $ hash -r
(myvenv) $ which pip
/home/pi/myvenv/bin/pip

I think modern versions of virtualenv clear the hash table automatically as I haven't seen this in a while, but it's possible you've got an old version if you're still on wheezy.

copy module 'Picamera' (2 folder) from local installation as 'usr/local/lib/python3.5/distr-package' to virtualenv installation '.virtualenvs/py3_for_all/lib/python3.5/site-package'


[Question]: Abnormal use of agent

Describe your problem

The display output is truncated, and the content is incorrect when it continues, and it does not connect to the previous

Disable or enlarge 'Max  token' in settnig of '生成回答'.

I need to generate an article that may have 10,000 tokens in length, and many models cannot reach this maximum output requirement.


[Bug]: Python39 on scoop is on 3.9.13, official release is on 3.9.18

Prerequisites

[X] I have written a descriptive issue title.
[X] I have searched all issues/PRs to ensure it has not already been reported or fixed.
[X] I have verified that I am using the latest version of Scoop and corresponding bucket.

Package Name
python39
Expected/Current Behaviour
Current:
scoop install versions/python39 installs Python 3.9.13
Expected:
scoop install versions/python39 installs Python 3.9.18
Steps to Reproduce
1. Run `scoop install versions/python39`
2. Check the installed version

Possible Solution
Update bucket with 3.9.18
Scoop and Buckets Version
PS> scoop --version
Current Scoop version:
v0.3.1 - Released at 2022-11-15

'extras' bucket:
c57864a86 (HEAD -> master, origin/master, origin/HEAD) saber: Update to version 0.18.6

'main' bucket:
003af7e55 (HEAD -> master, origin/master, origin/HEAD) rdiff-backup: Update to version 2.2.5

'nonportable' bucket:
8d658ac (HEAD -> master, origin/master, origin/HEAD) anki-np: Update to version 23.12

'versions' bucket:
89c87b9e8 (HEAD -> master, origin/master, origin/HEAD) vlc-nightly: Update to version 20231225

Scoop Config
PS> scoop config

last_update            scoop_repo                              scoop_branch
-----------            ----------                              ------------
25-12-2023 01:44:28 PM https://github.com/ScoopInstaller/Scoop master

PowerShell Version
PS> $PSVersionTable

Name                           Value
----                           -----
PSVersion                      7.4.0
PSEdition                      Core
GitCommitId                    7.4.0
OS                             Microsoft Windows 10.0.22631
Platform                       Win32NT
PSCompatibleVersions           {1.0, 2.0, 3.0, 4.0…}
PSRemotingProtocolVersion      2.3
SerializationVersion           <IP_ADDRESS>
WSManStackVersion              3.0

Additional Softwares
No response

security:
only security fixes are accepted and no more binaries are released, but new source-only versions can be released
https://devguide.python.org/versions/#status-key

PSF does not provides binary installer for security updates versions.
Built from source or use unofficial build instead, Scoop will not switch to unofficial builds.


Question 2 should be under findable

code state: 390fb39dd3ac909ed699a12ef9d01b2d5a75a65a
Q 2 "Are the software's identifiers globally unique?" should be under "findable", and it's currently under accessible. The corresponding FAIR4RS guiding principle is "F1. Software is assigned a globally unique and persistent identifier."

I realize it's perhaps not the most widely shared view, but in my opinion having a globally unique identifier does not help another person find (as in "discover") the software. It does however help them unambigously resolve the identifier (uniqueness), in a way that will work for the foreseeable future (persistence), but importantly note this happens after they found the identifier.
I think your question was also discussed in the Google Doc, where we talked about whether metadata that is "indexable" is helping discoverability. Something along the lines of:

In my opinion, the answer is "no", instead what you're looking for as a desirable property is "indexed", not "indexable". Hence the phrasing of question 1.

A resolver is an augmentation to the identifier. The "identifier" is only the string that differentiates it from others. And, you're right, it doesn't help discover the software. And you'd be correct that indexed would capture this. I don't solidly recall the discussion around F4 ("indexable") but I suspect the argument ran was that this was about the software curation/preparation by the software owner/author, rather than the properties of the infrastructure which it was captured in. This is something worth taking back to the group at the 2 year anniversary which is coming up in March 2025.
As I understand it, the mindset comes from printed scholarly works. The identifier helps "find" the software based on a reference to it. i.e., if one stumbles across a reference to the software in a scholarly article, they could locate it using the identifier. The name of the project, or the name of the software wouldn't be sufficient in every instance. Especially if that name had already been used elsewhere.
That was the intent of the principle, and that's why this question belongs under findable. The way you're interpreting the principle is outside the intent with which it was written. So, I still think this belongs under F.

PR #90 moved question 2 from Accessibility to Findability. Closing this issue.


Removed for Runner dependency

As the deployment method for this offering was only published via Runner, which was deprecated in 2020, this article should be removed.

Is there anywhere that the URL for this article to be redirected?


Fix PartitionKey.None.toString() throws an exception

#8499
PartitionKey.None.toString() throws an exception:
Java: 11
Jackson: 2.10.1
azure-cosmos 3.6.0
    @Test
    void testPartitionKeyNoneToString() {
        com.azure.data.cosmos.PartitionKey.None.toString();
    }

The exception happened in the following code:
https://github.com/Azure/azure-sdk-for-java/blob/660bc29a3a268988e515a3889dec7c2b7c3a2e86/sdk/cosmos/azure-cosmos/src/main/java/com/azure/cosmos/implementation/routing/PartitionKeyInternal.java#L246
partitionKey.getComponents() return null in the "for" loop.
Is it ok to add a null check for partitionKey.getComponents before the for loop?
@jongio

@mbhaskar - Please take a look at this.

This has been fixed on v4 SDK.

@tzhanl - Please verify fixed.

Verified fixed in azure.cosmos 4.1.0. Close issue.


Allow it to use npm installed clang-format

If I install clang-format from npm globally, I am unable to use it as it is looking for the .exe it seems. Could you allow it to use either windows or npm installed versions?
Thanks.

Duplicate of #19


Design general library for actions to devices

Create a python library which transforms general inputs to specific device control

Library is implemented with control actions for Windows and Linux computers + Kissbox devices.


apply_complex_function HELP

I wanted to turn the circle into an irregular shape by random scaling, as shown in Figure 1, but it didn't turn out what I wanted. Anyone can help me？
from manim import *
import random

class Test(Scene):

    def construct(self):
        circle = Circle()

        # circle.apply_complex_function(
        #     lambda z: z*2
        # )

        circle.apply_complex_function(
            lambda z: z*2*random.uniform(0.75, 1.25)
        )

        self.add(circle)

Figure 1

Result

I don't completely understand what happens here, but if you scale down the amplitude of your randomness it gets better. Also a parametric curve for your circle seems to be a better choice, since a circle object in Manim does not contain many points.
class Test(Scene):

    def construct(self):
        #circle = Circle()
        circle = ParametricFunction(
            lambda t: np.array([np.cos(t),np.sin(t),0]),
            t_range=[0,2*PI,0.2]
        )
        # circle.apply_complex_function(
        #     lambda z: z*2
        # )

        circle.apply_complex_function(
            lambda z: z*np.random.uniform(1.975, 2.025)
        )

        self.add(circle)

Thanks @uwezi ，My purpose is to generate an irregular shape, and now I've found a way.
from manim import *
import random

class IrregularShapeDemo(Scene):
    stroke_color = TEAL
    fill_color = BLUE_E
    fill_opacity = 1
    height = 2

    def construct(self):
        plane = NumberPlane()

        blob = VMobject()
        blob.set_points_as_corners([
            (1 + 0.3 * random.random()) * p
            for p in compass_directions(12)
        ])
        blob.close_path()
        blob.set_fill(self.fill_color, self.fill_opacity)
        blob.set_stroke(self.stroke_color)
        blob.set(height=self.height)
        blob.make_smooth()
        blob.center().shift(UP+RIGHT)

        self.add(plane, blob)

looks nice!
I didn't know that already VMobject()  had the method .make_smooth()


pkgsStatic.linux-pam: Remove no longer necessary musl patches.

Motivation for this change
See https://github.com/NixOS/nixpkgs/pull/109906#issuecomment-775630916.
These Alpine patches:
libpam-fix-build-with-eglibc-2.16.patch
fix-compat.patch

were removed in https://git.alpinelinux.org/aports/commit/main/linux-pam?id=9ba93cf3f515b4f0b9b3802b84d42c4e436afe8b
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I tested with:
nix-build -E '(import <nixpkgs> {}).pkgsStatic.parted.override { lvm2 = null; }'

which uses this.


Random parse errors

Hey,
I am seeing these sometimes:
GenServer #PID<0.10459.0> terminating
  ** (exit) an exception was raised:
  ** (Redix.Protocol.ParseError) not a valid integer: "343\r"
  lib/redix/protocol.ex:135: Redix.Protocol.parse_integer/1
  lib/redix/protocol.ex:142: Redix.Protocol.parse_bulk_string/1
  lib/redix/protocol.ex:183: Redix.Protocol.take_n_elems/3
  lib/redix/protocol.ex:105: Redix.Protocol.parse_multi/2

It seems to happen especially often when fetching a MGET like query but not all of the time. :(
Let me know if I can help further...

Hey @mschae, thanks for the report! I'll try to reproduce this, in the meantime could you tell me what the values of the keys you're fetching are?

Sure! Thanks for looking into this!
They are binary encoded erlang terms. Example:
RedixPool.command ["MGET", "395b8b1b-2343-45f8-a006-d1fb2ef6aadc", "3bc82e6c-1aee-4a78-86c5-4627220eaa6d"]
[<<131, 116, 0, 0, 0, 10, 100, 0, 10, 95, 95, 115, 116, 114, 117, 99, 116, 95, 95, 100, 0, 21, 69, 108, 105, 120, 105, 114, 46, 83, 111, 109, 109, 101, 108, 105, 101, 114, 46, 66, 111, 100, 121, 100, 0, 15, 97, 118, 103, ...>>,
 <<131, 116, 0, 0, 0, 10, 100, 0, 10, 95, 95, 115, 116, 114, 117, 99, 116, 95, 95, 100, 0, 21, 69, 108, 105, 120, 105, 114, 46, 83, 111, 109, 109, 101, 108, 105, 101, 114, 46, 66, 111, 100, 121, 100, 0, 15, 97, 118, 103, ...>>]

My best guess is that incomplete packages are not properly detected.

@mschae yeah that's probably it. Let me look into this :)

@mschae could you give master a spin? It should work now, the bug was actually pretty silly. Let me know!

Thanks for the super quick resolution!
I'll give it a spin and let you know.

Looks a lot better, thanks!

:+1: releasing v0.3.2 :)

...and published!

Ugh... Sorry to bother you again: Close but no cigar.
** (exit) exited in: :gen_server.call(#PID<0.6044.0>, {:commands, [["MGET", "e7f145f9-79dc-4a37-a707-5b549369e8d3", "c60d6573-db7d-4da8-ad5f-b7e8547ce168", "389a2400-0ad9-4881-9f6d-010652005257", "62efc575-a94b-4a50-9903-9d9445a78262", "1862acc3-aab1-45e0-bb42-53ace95c4caa", "1ae3302a-3fee-4ff8-a9c8-19b1e73094e1", "1ae5f990-e8a8-487b-8839-f492927b5a41", "f95f8291-9d56-407d-af65-ae97e643234a", "137fd2c1-689a-4f78-97a2-7acf33ca5c95", "8cc709cf-1bc8-46f3-9f49-1f040e79763b", "de0da939-43ee-4a4c-9cc8-5294e32463c1", "89139cd5-7ad6-4a30-ac2a-ee95aa0a31af", "5b1548f1-ec55-465b-9ea6-1805122265dd"]]}, 5000)
  ** (EXIT) an exception was raised:
  ** (Redix.Protocol.ParseError) not a valid integer: ""
  lib/redix/protocol.ex:137: Redix.Protocol.parse_integer/1
  lib/redix/protocol.ex:142: Redix.Protocol.parse_bulk_string/1
  lib/redix/protocol.ex:183: Redix.Protocol.take_n_elems/3
  lib/redix/protocol.ex:105: Redix.Protocol.parse_multi/2

Tried to solve it myself...


I have two questions.

Can block the right-click menu in the Preview pane?
Can add  custom CSS to the preview pane?

There are no configuration options for either of these features... actually there are no options, period. But If you are willing to compile, this should be very easy!

Sure, the control being used to display is a regular WebBrowser control, you can set IsWebBrowserContextMenuEnabled to false. Depending on your motives, you may want to set other properties too, like AllowWebBrowserDrop
Sure, the CSS loaded is from the embedded resource obtained in MarkdownPreview.Core/Engine.cs > GetCSS. This embedded resource is from the CSS from https://github.com/nicolashery/markdownpad-github, loaded as a submodule. Depending of what you want to achieve, you can do all kinds of things here:
2.1. Embed an additional or other CSS styleheet
2.2. Pre- or post-fix your own CSS

That being said, I could think of trying to make this configurable once I have the time if you could tell me why you would want this.

Context Menu, which blocks webbrowse, wants the plugin to have a separate Context Menu (for example, select All, copy, and so on).
The custom CSS is loaded to accommodate the dark mode of Windows 10.

I don't understand yet. What is context menu. Would it suffice if the menu was disabled?
I agree, it would be nice of the plugin could detect if dark mode is used and switch to a compatible scheme itself. See #8


find n-th root, 'n' is hidden.

Issue Summary
When I want to show find cubic root or n-th root, I find the number ( or the mo n) is hidden. Like this:

Then, when I try more mathml, I found when I use some n-th root mathml as adjacent sibling, the n in first mathml will be hidden, others will show.

Technical details:

MathJax Version: 3.1.4, 3.2.0
Client OS: Windows10
Browser: Chrome 91.0.4472.114

Supporting information:

Example MathML: <math xmlns="http://www.w3.org/1998/Math/MathML"><mroot><msup><mn>6</mn><mn>3</mn></msup><mn>4</mn></mroot></math>
Example link: https://jsbin.com/xemewowujo/1/edit?html,output

It will hidden if the mathml is the first element of a new line(block).

Add custom style: m-root { width: 1px} will fix this, but I don't know if this will bring other render bug...

Yes, I was looking at it and came to the same conclusion.  It also only occurs at some zoom levels, so if you zoom in or out, it sometimes appears again.
This seems to be a bug in Chrome, related to the fact that the root is placed in a box with width 0 (Chrome seems to clip those out when they appear at the beginning of a line).
A work-around for now is to add the CSS
mix-root {
  min-width: .05px;
}

Looks like you've been thinking along the same lines.  Setting the min-width for mjx-root  is better, since the width can be larger than 0 in some cases (i.e., if the root is wide, say "1000").

Yes, min-width is better. It's true that chrome has this problem, but firebox doesn't. I'll try to find the reason. It's so confusing.

I'm no longer able to reproduce this, so I suspect it has been fixed in current versions of Chrome.


Type definitions

Could we include a typing declaration for use with TypeScript?

Coming soon. Check out our road map here #39

Seems we already have a pr #37 here. I'm new to TS, anyone could give it a review? THX

Plus, @varHarrie what's this file index.d.test.ts used for?

@ryanoshea @varHarrie Type definitions comes in release 1.5.23 thanks.😁

released , close


Deprecation warnings with usage of std::binder1st and std::binder2nd

Just tried a build with the latest development snapshot and the following deprecation warnings gets thrown:
In file included from /home/ghislain/workspace/MIRTK/ThirdParty/Eigen/Eigen/Core:276:0,
                 from /home/ghislain/workspace/MIRTK/Modules/Numerics/include/mirtk/Eigen.h:34,
                 from /home/ghislain/workspace/MIRTK/Modules/Numerics/src/Matrix.cc:39:
/home/ghislain/workspace/MIRTK/ThirdParty/Eigen/Eigen/src/Core/Functors.h:973:28: warning: ‘template<class _Operation> class std::binder2nd’ is deprecated [-Wdeprecated-declarations]
 struct functor_traits<std::binder2nd<T> >
                            ^
In file included from /usr/include/c++/5/bits/stl_function.h:1128:0,
                 from /usr/include/c++/5/string:48,
                 from /home/ghislain/workspace/MIRTK/Modules/Common/include/mirtk/String.h:27,
                 from /home/ghislain/workspace/MIRTK/Modules/Common/include/mirtk/Object.h:23,
                 from /home/ghislain/workspace/MIRTK/Modules/Numerics/include/mirtk/Matrix.h:24,
                 from /home/ghislain/workspace/MIRTK/Modules/Numerics/src/Matrix.cc:21:
/usr/include/c++/5/backward/binders.h:143:11: note: declared here
     class binder2nd
           ^
In file included from /home/ghislain/workspace/MIRTK/ThirdParty/Eigen/Eigen/Core:276:0,
                 from /home/ghislain/workspace/MIRTK/Modules/Numerics/include/mirtk/Eigen.h:34,
                 from /home/ghislain/workspace/MIRTK/Modules/Numerics/src/Matrix.cc:39:
/home/ghislain/workspace/MIRTK/ThirdParty/Eigen/Eigen/src/Core/Functors.h:977:28: warning: ‘template<class _Operation> class std::binder1st’ is deprecated [-Wdeprecated-declarations]
 struct functor_traits<std::binder1st<T> >
                            ^
In file included from /usr/include/c++/5/bits/stl_function.h:1128:0,
                 from /usr/include/c++/5/string:48,
                 from /home/ghislain/workspace/MIRTK/Modules/Common/include/mirtk/String.h:27,
                 from /home/ghislain/workspace/MIRTK/Modules/Common/include/mirtk/Object.h:23,
                 from /home/ghislain/workspace/MIRTK/Modules/Numerics/include/mirtk/Matrix.h:24,
                 from /home/ghislain/workspace/MIRTK/Modules/Numerics/src/Matrix.cc:21:
/usr/include/c++/5/backward/binders.h:108:11: note: declared here
     class binder1st

and
In file included from /home/ghislain/workspace/MIRTK/ThirdParty/Eigen/Eigen/Core:276:0,
                 from /home/ghislain/workspace/MIRTK/Modules/Numerics/include/mirtk/Eigen.h:34,
                 from /home/ghislain/workspace/MIRTK/Modules/Numerics/src/Polynomial.cc:24:
/home/ghislain/workspace/MIRTK/ThirdParty/Eigen/Eigen/src/Core/Functors.h:973:28: warning: ‘template<class _Operation> class std::binder2nd’ is deprecated [-Wdeprecated-declarations]
 struct functor_traits<std::binder2nd<T> >
                            ^
In file included from /usr/include/c++/5/bits/stl_function.h:1128:0,
                 from /usr/include/c++/5/string:48,
                 from /home/ghislain/workspace/MIRTK/Modules/Common/include/mirtk/String.h:27,
                 from /home/ghislain/workspace/MIRTK/Modules/Common/include/mirtk/Object.h:23,
                 from /home/ghislain/workspace/MIRTK/Modules/Numerics/include/mirtk/Polynomial.h:23,
                 from /home/ghislain/workspace/MIRTK/Modules/Numerics/src/Polynomial.cc:20:
/usr/include/c++/5/backward/binders.h:143:11: note: declared here
     class binder2nd
           ^
In file included from /home/ghislain/workspace/MIRTK/ThirdParty/Eigen/Eigen/Core:276:0,
                 from /home/ghislain/workspace/MIRTK/Modules/Numerics/include/mirtk/Eigen.h:34,
                 from /home/ghislain/workspace/MIRTK/Modules/Numerics/src/Polynomial.cc:24:
/home/ghislain/workspace/MIRTK/ThirdParty/Eigen/Eigen/src/Core/Functors.h:977:28: warning: ‘template<class _Operation> class std::binder1st’ is deprecated [-Wdeprecated-declarations]
 struct functor_traits<std::binder1st<T> >
                            ^
In file included from /usr/include/c++/5/bits/stl_function.h:1128:0,
                 from /usr/include/c++/5/string:48,
                 from /home/ghislain/workspace/MIRTK/Modules/Common/include/mirtk/String.h:27,
                 from /home/ghislain/workspace/MIRTK/Modules/Common/include/mirtk/Object.h:23,
                 from /home/ghislain/workspace/MIRTK/Modules/Numerics/include/mirtk/Polynomial.h:23,
                 from /home/ghislain/workspace/MIRTK/Modules/Numerics/src/Polynomial.cc:20:
/usr/include/c++/5/backward/binders.h:108:11: note: declared here
     class binder1st

This problem is likely to go away with Eigen 3.3 which is currently in beta stage as this header file no longer exists then. Instead, there is a src/Core/functors subdirectory. When Eigen 3.3 is released, we can update ThirdParty/Eigen.

Eigen3 source files are no longer included in MIRTK, not even as Git submodule. As this deprecation warning relates to the third-party library Eigen3 only (and has been addressed there), this issue can be closed/ignored.


zhimi.airp.va2 pm2.5 entity no longer updates

Device model / 设备型号
zhimi.airp.va2
Component version / 插件版本
0.7.18
HA core version / HA版本
2024.6.2
Integrated mode / 集成方式
Automatic (自动模式)
The problem / 问题详情
the zhimi.airp.va2 "air filter pro 4" air purifier usually reports a pm2.5 value. it seems to have stopped. power cycling the air filter will update the number to whatever it's first read is, but then it never updates again. I noticed when the value hadnt changed at all in a few days. having a look at the history:

i can see that on approx 1am may 4th the integration just stopped updating and seemed to only update when home assistant was restarted.
Entity attributes / 实体属性
preset_modes: Auto, Sleep, Favorite, Manual
percentage: 33
percentage_step: 33
preset_mode: Auto
model: zhimi.airp.va2
lan_ip: <IP_ADDRESS>
mac_address: CC:B5:D1:1A:30:6F
entity_class: MiotFanEntity
miot_type: urn:miot-spec-v2:device:air-purifier:0000A007:zhimi-va2:1
air_purifier.on: true
air_purifier.fault: 0
air_purifier.mode: 0
air_purifier.fan_level: 1
air_purifier.anion: false
rfid.rfid_tag: 90:f:a3:aa:f1:ce:4
aqi.purify_volume: 1666887
custom_service.favorite_level: 3
custom_service.manual_level: 2
custom_service.iic_error_count: 23
screen.brightness: 2
physical_controls_locked: false
alarm: false
filter.filter_life_level: 0
filter.filter_used_time: 8709
filter.filter_left_time: 0
environment.relative_humidity: 56
environment.pm2_5_density: 5
environment.temperature: 25.3
state_updater: cloud
rfid.rfid_factory_id: 0:0:41:50
rfid.rfid_product_id: 0:0:31:35
rfid.rfid_time: 0:22:10:21
rfid.rfid_serial_num: 0:19:57:34
aqi.average_aqi: 3
aqi.aqi_state: 0
aqi.aqi_updata_heartbeat: 0
custom_service.moto_speed_rpm: 488
custom_service.favorite_speed: 900
custom_service.motor_set_speed: 490
custom_service.buttom_door: false
custom_service.reboot_cause: 0
sub_entities: environment-3.relative_humidity-1, environment-3.pm2_5_density-4, environment-3.temperature-7, filter-4.filter_life_level-1, air_purifier-2.on-1, air_purifier-2.anion-6, alarm-6.alarm-1, filter-4.filter_used_time-3, filter-4.filter_left_time-4, physical_controls_locked-8.physical_controls_locked-1
friendly_name: Xiaomi Smart Air Purifier 4 Pro Air Purifier
supported_features: 9
Home Assistant Logs / 系统日志

Try reloading the integration and/or restarting the purifier. fixed it for me.

it seems that the integration forgets to refresh the status for the sensor. I can see that the attribute for pm2.5 in the main fan entity was updated, but not the dedicated sensor.
It seems that this issue affects xiaomi.airp.mp4 as well.
@al-one 帮忙看一下为什么净化器的代码里面，就算pm2.5的attribute更新了，也没有更新 pm2.5 实体。就是从开发者工具里面看到environment.pm2_5_density 更新了，但是sensor.xiaomi_mp4_pm25_density 还是没有更新。

Temporary mitigated by using a template sensor to read the attribute from the main fan entity.
state_attr('fan.purifier', 'environment.pm2_5_density')

zhimi.airp.meb1 is also affected; I see the correct temperature in the fan entity attribute, but the temperature sensor is stuck on the first value it was initialized with.

Hi all,
zhimi.airp.mb3a is also affected by this bug even with the latest 0.7.22 version.
The sensors (temp, humidity, pm2.5, filter life) are not updating but the filter used time sensor and the switches seem to be working great. Doesn't matter which way I set up the integration (auto, local or cloud), they only update once.
Tried what @al-matic suggested in the latest comment but it didn't work for me (with my model of course).
Any update on this fairly old bug maybe?
The last properly working version was 0.7.17

Try beta version.

https://github.com/al-one/hass-xiaomi-miot/releases/tag/v1.0.0b3

Had the same issue but it works again with the linked beta release.

despite all of these updates since June - none of them have resolved the issue. My air filter says its 'zhimi.airp.va2', and the only time any of the numbers update themselves is when i reload the integration. it gets the first value, then i guess it just 'quits checking'.

Try beta version.

https://github.com/al-one/hass-xiaomi-miot/releases/tag/v1.0.0b3

Hi al-one,
Yes, this beta version seems to be working great, all of my devices are working and updating as they should.
Thank you for your work!

why is this closed?
i opened the ticket, my issue is still not resolved!


Refactor test cases

Fix #62

Coverage increased (+0.1%) to 80.934% when pulling 9d8d88f2f0e0f3111a074b0658f0979c5cb2c00b on refactor_test_cases into 2a231773a0f205ba2da7d5d3d4eb6822403bc4e1 on master.


React-Native-Swipeable-Cards, Forked & Updated

I had a lot of issues with gettings this to work, so I forked and credited meteor-factory but will be maintaining it at react-native-swipeable-cards. If you have requests or need help post there unless meteor wants to continue maintaining this

can you post a link to you repo please ?
thanks

https://github.com/jonathanRinciari/React-Native-Swipeable-Cards
but it is also not maintained, I have my own fork at https://github.com/eyalyoli/react-native-swipe-cards-deck


Local install doesn't start

(Thanks for reporting an issue! Please make sure you click the link above to view the issue guidelines, then fill out the blanks below.)
What are the steps to reproduce this issue?

git clone https://github.com/hashicorp/faas-nomad.git
cd faas-nomad
./startNomad.sh (after adding a further grep to the script to ensure my RFC1918 interface is chosen) (OK)
vagrant up

What happens?
$ consul version
Consul v1.4.4
Protocol 2 spoken by default, understands 2 to 3 (agent will automatically use protocol >2 when speaking to compatible agents)
$ nomad version
Nomad v0.9.0 (18dd59056ee1d7b2df51256fe900a98460d3d6b9)
$ vagrant version
Installed Version: 2.2.4
Latest Version: 2.2.4
$ VBoxManage --version
5.2.26r128414
$ uname -a
Darwin myMac.my.net 17.7.0 Darwin Kernel Version 17.7.0: Wed Feb 27 00:43:23 PST 2019; root:xnu-4570.71.35~1/RELEASE_X86_64 x86_64
$ vagrant up
<errors - see below>
What were you expecting to happen?
Vagrant to deliver 1+ docker hosts with the stack running
Any logs, error output, etc?
All went OK until:
# Enabling the service here to ensure each state is independent.
nomad-service:
  service.running:
    - name: nomad
    # Restart service if config changes
    - restart: True
    - enable: True
[DEBUG   ] Results of YAML rendering:
OrderedDict([(u'nomad-config', OrderedDict([(u'file.serialize', [OrderedDict([(u'name', u'/etc/nomad/nomad.hcl')]), OrderedDict([(u'formatter', u'json')]), OrderedDict([(u'dataset_pillar', u'nomad:config')]), OrderedDict([(u'mode', 640)]), OrderedDict([(u'user', u'root')]), OrderedDict([(u'group', u'root')]), OrderedDict([(u'watch_in', [OrderedDict([(u'service', u'nomad-service')])])])])])), (u'nomad-service', OrderedDict([(u'service.running', [OrderedDict([(u'name', u'nomad')]), OrderedDict([(u'restart', True)]), OrderedDict([(u'enable', True)])])]))])
[PROFILE ] Time (in seconds) to render '/var/cache/salt/minion/files/dev/nomad/config.sls' using 'yaml' renderer: 0.00392889976501
[DEBUG   ] LazyLoaded highstate.output
local:
    Data failed to compile:
----------
    Rendering SLS 'dev:nomad.install' failed: Jinja variable 'salt.utils.odict.OrderedDict object' has no attribute 'data_dir'
The SSH command responded with a non-zero exit status. Vagrant
assumes that this means the command failed. The output for this command
should be in the log above. Please read the output to determine what
went wrong.

Any other comments?
What versions of software are you using?
Operating System: macOS 10.13.6 (17G6030)
OpenFaaS Version: 0.8.4 cli
Nomad Version: 0.9.0

I have same issue

I'll ping the maintainer.
@acornies
Alex

Thanks for the report. Unfortunately Nomad 0.9 isn't officially supported yet, although it's definitely on my priority list.
The defined vagrant up flow in this repo technically doesn't use the startNomad.sh script, but the salt directory in provisioning/saltstack/... which provisions Nomad 0.8.6, Consul and Vault w/ Docker.

I should also mention that vagrant flow is designed to locally develop/debug faas-nomad itself, so it assumes you're running vagrant but also running faas-nomad on your local system. I use these settings in vscode + installed Go in conjunction with the vagrant setup:
{
  "version": "0.2.0",
  "configurations": [
    {
      "name": "faas-nomad",
      "type": "go",
      "request": "launch",
      "mode": "auto",
      "remotePath": "",
      "host": "<IP_ADDRESS>",
      "port": 8081,
      "program": "${workspaceFolder}",
      "env": {},
      "args": [
        "-nomad_region", "global",
        "-nomad_addr", "<IP_ADDRESS>:4646",
        "-enable_consul_dns=true",
        "-consul_addr", "http://<IP_ADDRESS>:8500",
        "-statsd_addr", "<IP_ADDRESS>:9125",
        "-basic_auth_secret_path", "provisioning/secrets",
        "-enable_basic_auth=false",
        "-vault_default_policy", "openfaas",
        "-vault_addr", "http://<IP_ADDRESS>:8200",
        "-vault_app_role_id", "2c5b9c12-e27a-f9ef-a64a-f032cb3f6fa0",
        "-vault_app_secret_id", "5618056c-e638-de3f-8e46-4fd2eb434318",
        "-port=8081"
      ],
      "showLog": true
    }
  ]
}

If you're just interested in running not developing, using the docker image from quay.io/nicholasjackson/faas-nomad:v0.4.1 along with he files in nomad_job_files should be sufficient.

@acornies I run vagrant up on Windows 10 without local Nomad, have same problem, how can I fix the problem? Thanks!

@nwong4932 can you try pulling latest master? I believe the config data needed to be updated for local vagrant flow to work.

@acornies, I read the README, but figured it would install openfaas as well as the local hashicorp stack in VMs which was a mistake.  Closing, as I was just gonna look around. In the innarests of dev, I'll downgrade nomad, and install openfaas first, then retry and report back.

BTW,  the link on the README to the aws setup is a 404.

@phosphre Let me know how it goes. This repo is a bit of a mess right now and my full-time work is consuming all my energy atm. The plan is to revamp this provider using Nomad 0.9 deps, increase test coverage and make provider configuration simpler.

I don't want to install docker for mac but never used faas so I was relying on the guides over there to get faas working first. How is your setup setup?

I use the Vagrantfile + supporting files in provisioning/... and simply run vagrant up in a portable VM (both virtualbox and vmware fusion supported) which installs Nomad, Consul and Vault and deploys the OpenFaaS components on Nomad. However, if you want to run this provider in the VM as well, just add this example block to this file: provisioning/saltstack/salt/nomad/files/faas.hcl
task "nomadd" {
      driver = "docker"
      config {
        image = "quay.io/nicholasjackson/faas-nomad:v0.4.1"
        args = [
          "-nomad_region", "${NOMAD_REGION}",
          "-nomad_addr", "${NOMAD_IP_http}:4646",
          "-consul_addr", "http://${NOMAD_IP_http}:8500",
          "-statsd_addr", "${NOMAD_ADDR_statsd_statsd}",
          "-node_addr", "${NOMAD_IP_http}",
          "-basic_auth_secret_path", "/secrets",
          "-enable_basic_auth=false",
          "more..."
        ]
        port_map {
          http = 8080
        }
      }
      resources {
        cpu    = 500 # 500 MHz
        memory = 128 # 128MB
        network {
          port "http" {
            static = 8081
          }
        }
      }

      service {
        port = "http"
        name = "faasd-nomad"
        tags = ["faas"]
      }
    }


ci: add verifier e2e presubmit that runs CLI at main

Signed-off-by: Asra Ali<EMAIL_ADDRESS>Adds a verifier e2e presubmit that mimics the example-package test with go/workflow dispatch. This should catch regressions early that show up in the e2e tests.
Related https://github.com/slsa-framework/slsa-verifier/issues/382

@asraa I think you checked in a slsa-verifier binary into the repo on this PR. Could you remove it?


Remove this use of "stopForeground"; it is deprecated.

Describe the technical debt
A clear and concise description of what the technical debt is.
Location: services/TrackRecordingService.java
Proposed solution
If applicable:

add logcat output

Technical information

Device: [e.g. Nexus 7 (2013)]
OS: [e.g. LineageOS 15.1]
OpenTracks version: [e.g. v3.2.4]
OpenTracks commit id (only for nightly builds): [e.g. 4b333bb]

Proposed Solution:
updated the code to use the stopForeground(int flags) method with the Service class.


cardinal: add aarch64-darwin support

Added aarch64-darwin support for Cardinal
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

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

[x] Fits CONTRIBUTING.md.

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

Could you please move the reformatting into a separated commit?

Thank you for the pointer @xanderio. Is this better?

That looks better, thanks! Could you resolve the merge conflict and take a look at the failing CI jobs


makefile: build: allow include recursively

Motivation: build.service.mk uses build.tool.mk. Now, this relation is implicit and resolved on the top level: Go Service.mk.

I have to avoid recursive including and deep-nesting cases.


fix: proper handling of LV and MV loads

Fixes #7

further requested improvements

round cosphi in topology and steadystate (expoter.py --> COSPHI_DECIMAL_DIGITS)
round power in topology and steadystate (exporter.py --> no decimal digits)
define separate names for parts of mv loads (e.g. MV_Load_5_CONSUMER and MV_Load_5_PROSUMER; otherwise in steadystate no unique assignment is possible (there exists then 2 entries with the same name))

I implemented the requested improvements and changed the 7 bus network to the 8 bus network.


Black Box

This is a black box for client feedback.

Some questions only showing their answers on question selection page when in regions mode
Survey notification bar should be the same red as used in the rest of the site

Some questions only showing their answers on question selection page when in regions mode
Survey notification bar should be the same red as used in the rest of the site


Attempt to get tests passing with updated deps

This probably needs work still but I needed to open a PR to run on AppVeyor.

Coverage decreased (-0.0008%) to 98.47% when pulling 6ff94cbd68b5cf2c11ba83ba4d06d7d847b52eef on phated:replace-syspath into cbdf25563cfff7f526e16ab4732b236e94be8f42 on paulmillr:master.

Coverage decreased (-0.0008%) to 98.47% when pulling 6ff94cbd68b5cf2c11ba83ba4d06d7d847b52eef on phated:replace-syspath into cbdf25563cfff7f526e16ab4732b236e94be8f42 on paulmillr:master.

@es128 any idea why this didn't run on AppVeyor?

Webhook config might be messed up. I'm not able to look at it.
@paulmillr can you check? The webhook url is
https://ci.appveyor.com/api/github/webhook?id=jvv568xm6xsow034

Alright, I'll set up a temp hook on my appveyor account.

Coverage decreased (-0.0008%) to 98.47% when pulling 1a4ba3d5b251bf1072c192c3cb535fdae06fb939 on phated:replace-syspath into cbdf25563cfff7f526e16ab4732b236e94be8f42 on paulmillr:master.

just resubmitted to appveyor

Please push a new commit @phated

@es128 @paulmillr I'm noticing some fundamental problems with the tests for the major bump - mainly that getFixturesPath needs to be modified to always return a posix-style path but it's also used to generate expected paths in many tests.  Do you think chokidar should emit posix-style paths in the same fashion as the globs it takes or should the tests be re-written to separate the expectations from the glob paths?

Don't think we should break any backwards compatibility.

The purpose of the major bump is to break compat with Windows style paths because they aren't valid globs. All dependencies have been upgraded for that behavior

Should we do a 2.0 release then?

@paulmillr yeah, I believe @es128 suggested the dependency updates to land in 2.0 in his #632 PR - I was just trying to get the tests to pass when I noticed https://github.com/paulmillr/chokidar/pull/658#issuecomment-354025519

I'm happy to make the changes but I need the direction to take 😄

should the tests be re-written to separate the expectations from the glob paths?

That would be my vote. I don’t think forcing posix-style paths in the events makes sense.
Maybe leave getFixturesPath as it was and a new method for generating the absolute-path globs for watch input?

@es128 sure, I can look into that.  I'm having a hard time understanding the core impl so it's taking me awhile.

@es128 I believe I have all the tests passing now (except maybe 1 flakey Windows polling test). However, I don't know if this is the proper amount of changes for this bump.  I had to do some really weird things (that you'll see in the diff) to get these to pass).
cc @doowb

Not sure why node 4 failed on AppVeyor - it's passing on mine: https://ci.appveyor.com/project/phated/chokidar/history

Coverage increased (+0.007%) to 98.477% when pulling a92f089f05978f242e0ca72f29cc627659dd977d on phated:replace-syspath into cbdf25563cfff7f526e16ab4732b236e94be8f42 on paulmillr:master.

I have no idea what's going on with the Travis runs :(

It's not unusual to have flaky failures because of how the test suite thrashes the filesystem, especially on weak CI VMs... especially especially the OS X ones.
This all looks pretty good to me. Can you point out what part of the patch seems weird/objectionable to you? I just took a quick look, but don't have concerns with anything I saw.

@es128 I'm specifically concerned with the changes I had to make to .add that does normalization to joined cwd and potentially a glob path.  I'm also not comfortable with the codebase but noticed a lot of sysPath usage - which would cause issues if a glob was passed to any of those.

The changes to .add make sense to me for the specific reason you described - we'll no longer be able to use isGlob on anything that's been sysPath'd.
If there are any other bad combinations of sysPath + the newly stricter globbing deps I'd expect the tests to tell us.
I'd be comfortable letting this out with a major bump. We could start with a prerelease tag also to try to get early feedback before it goes wide.

I'm good with that if you are comfortable with it.

Crud, I need to update anymatch too.

Coverage increased (+0.007%) to 98.477% when pulling 2f3112a834ef27cd03320c6caba4f57548505f9e on phated:replace-syspath into cbdf25563cfff7f526e16ab4732b236e94be8f42 on paulmillr:master.

@es128 can you rerun the CI?

@es128 looks like just 1 OSX failure now.

woohoo!  @es128 do you want appveyor to be green too?  I think @paulmillr would have to restart it.

No, there’s no point in trying to get the 0.10 one green in appveyor. It fails on something random more often than it succeeds.

@paulmillr the appveyor webhook still doesn't seem to be working. After merging I just had to kick it off manually, and the only option exposed to me in their UI is to do that for the latest commit in the master branch.

@es128 did you have to manually kick it off at https://ci.appveyor.com/project/es128/chokidar and https://ci.appveyor.com/project/paulmillr/chokidar?  It seems the location changed when he re-enabled it
Also, thanks for getting this merged!  Excited to see 2.0 so I can get it updated in glob-watcher 😸

Oh I hadn't even noticed the divergence. So yeah, I guess the new one at https://ci.appveyor.com/project/paulmillr/chokidar should be good to go.

Do you need anything else from me before it gets released?  Where do you want to mention the breaking glob changes?

@paulmillr do you have any housekeeping items you'd like to see prior to publishing 2.0?
I've been mulling over the idea of opening a PR and a discussion about dropping 0.10 and 0.12 from the CI configs... and maybe announcing an end of active support for them with the major bump, without doing anything to deliberately break compatibility.

@es128 What about deprecating them in the major and moving them to allow_failures in the CI configs?

Outside observer dropping in: IMHO either you drop a version or you don't. Soft-deprecations inevitably turn into hard failures when a regression isn't noticed (because they're dropped from CI). That's a major pain for downstream packages who don't expect node version to be (effectively) dropped in a minor release.

Hmm, I hadn't really considered the allow_failures option. If I can turn that on in appveyor for node v0.10 that may be good enough. Don't even really need to deprecate compatibility with the old versions, they should just keep working as well as they already do.


KeyError: unet

After updating ComfyUI this module generates an import error because ComfyUI changed the folders structure.
On the screenshot below you can see the commented original line of code and next to it it is the fix.

This has already been fixed to support both names, it looks like you're on an older version.

Hmmm strange. I tried to update many times using the Manager in ComfyUI. Let me check in CLI via direct git command.
Sorry for dup.


chore: add default value for registry

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


chore(master): release 1.1.51

:robot: I have created a release beep boop
1.1.51 (2023-08-25)
Miscellaneous

deps: update dependency phpstan/phpstan-phpunit to v1.3.14 (3d3b4ff)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/wayofdev/laravel-stripe-webhooks/releases/tag/v1.1.51 :sunflower:


Fix viddy tool

Expected Behaviour

E2e tests should pass, but the viddy tool has had a breaking change and is causing a failure.
Possible Solution

Investigate what changed and update templates
Steps to Reproduce (for bugs)

make e2e

https://github.com/alexellis/arkade/actions/runs/4194318807/jobs/7272319718

Error is HTTP/403
The paths looks the same and there hasn't been a Viddy release since June 2022.
A subsequent run https://github.com/alexellis/arkade/actions/runs/4199349285/jobs/7284102754 completed successfully.
Could this have been a transient issue?

Works to me as well:
PASS
coverage: 54.4% of statements
ok      github.com/alexellis/arkade/pkg/get     17.942s coverage: 54.4% of statements

Thanks both for looking.


Fix minimum swift-nio version to use async/await FileIO APIs.

2.0.0-beta.2 uses async/await FileIO APIs in NIO.
Package.swift points to 2.62.0 as the minimum version, but this API was introduced in 2.63.0.
INFO: https://github.com/apple/swift-nio/releases/tag/2.63.0

Thank you


project settings type does not match what is added

Godot version:
Godot_v3.3-rc9_win64
Tested on Godot_v3.2.3-stable_win64 without issue.
Issue description:
When adding new project setting, type name does not always match what is added. For example, adding an array will add a dictionary.
Steps to reproduce:

That's very likely a regression from #42616, which removes two entries from the list but doesn't handle the code which then actually creates those Variant types (most likely by assuming that their OptionButton index matches their Variant index).

I think there are many such assumptions throughout Godot editor. A warning in the project settings should suffice I think.


spinner.fail is not a function! error when trying to install missing package(new rule created)

I ran yarn new:rule from the root directory to create a new rule and it gave me the interactive wizard to specify the meta information about the rule. After creating the rule, I ran  the command the wizard gave me to init the rule. As per the documentation, i should be able to start using the rule. So i updated the config json to include this rule and when i ran sonarwhal command, it gave me a message saying 1 package is missing and i want to install it . I opted "Yes" and i got an error message spinner.fail  is not a function!

Environment

sonarwhal version:  1.6.1
Node.js version: 8.11.1
npm version: 5.8.0

sonarwhal configuration

sonarwhal’s configuration
{
    "connector": {
        "name": "chrome",
        "options": {
            "waitFor": 1000
        }
    },
    "formatters": ["summary", "excel"],
    "parsers": [],
    "rulesTimeout": 120000,
    "rules": {
        "content-type": "warning",
        "my-new-rule-name": "warning",
        "http-cache": "warning"

    }
}

URL for which sonarwhal failed

URL:

Output
Please include the raw output generated by sonarwhal, or if possible,
the raw output from running sonarwhal in debug mode: sonarwhal --debug <URL>.

sonarwhal’s raw output

A couple of things we need to do:

Update the docs to execute yarn after creating the rule to get all the dependencies
Investigate why spinner.fail doesn't exist

I am not able to reproduce the spinner error :(

The spinner dependency will be removed once https://github.com/sonarwhal/sonarwhal/pull/1113 is merged. So we should be able to close this issue after the merge.


Bot is not playing track

📝 Description
Even though not displaying any error and fetching the query results correctly, the bot is not playing any kind of track.
🪜 Reproduction Steps

Use /play command
Bot is summoned, but no track is played (as stated by /np command as well)

ℹ Environment / Computer Info

Parrot version:  1.6.0
Operating System:  Windows 10

Using the Docker image doesn't seem to have any problems, this happened while testing the bot locally.
📸 Screenshots

Using the Docker image doesn't seem to have any problems, this happened while testing the bot locally.

Having this in mind, my guess is that it is either yt-dlp or ffmpeg interfering in some way. As those are the things that sort of work outside our dependencies.

Did you managed to fix it ?

@lucawen I had the same issue, upgrading yt-dlp version fixed it. (I had a ~4 month old yt-dlp)

I tested in Linux afterwards and it also worked, so it might just have been the yt-dlp version
As such, I will close this issue for the moment

Edit: Actually...
I looked at the error log, I see the following error when attempting to download the metadata:
Application error: WARNING: [youtube] Failed to download m3u8 information: HTTP Error 429: Too Many Requests

Which is an issue reported on yt-dlp: https://github.com/yt-dlp/yt-dlp/issues/7143
However, strangely if I run yt-dlp manually, it successfully downloads the file.
And right after, it seems to get the correct metadata.
My guess is that somehow this error is intercepted by parrot, and song in the stdout is ignored.
And since all metadata is fetched from Youtube, nothing gets played.
I tried disabling the metadata entirely, however still nothing gets played.
Unfortunately, I don't know the project well enough to debug further.
@afonsojramos Any ideas?

I'm getting this as well and updating to a new yt-dlp was the fix. I logged into the container console and ran pip install -U yt-dlp

I'm getting this as well and updating to a new yt-dlp was the fix. I logged into the container console and ran pip install -U yt-dlp

We already do that in the container, did it find a new version? Did it really updated?
https://github.com/aquelemiguel/parrot/blob/main/Dockerfile#L25

Yeah my container was on 2023.03.06 of the yt-dlp and now it's on 2023.11.16

If you remove cache and rebuild the container with this same docker image, is it still the case?

Yessir. I already tried that. Did it on multiple machines as well. I'm using the official docker install.


[Hub Generated] Publish private branch 'voiceservices/api-release'

This is a PR generated at OpenAPI Hub. You can view your work branch via this link.
ARM API Information (Control Plane)
Azure 1st Party Service can try out the Shift Left experience to initiate API design review from ADO code repo.  If you are interested, may request engineering support by filling in with the form https://aka.ms/ShiftLeftSupportForm.
Changelog
Add a changelog entry for this PR by answering the following questions:

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[ ] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[x] Other, please clarify
Updates to the SDK generation markdown files for the GA release of the Java and Python SDKs

When are you targeting to deploy the new service/feature to public regions? Please provide the date or, if the date is not yet available, the month.
When do you expect to publish the swagger? Please provide date or, the the date is not yet available, the month.
By default, Azure SDKs of all languages (.NET/Python/Java/JavaScript for both management-plane SDK and data-plane SDK, Go for management-plane SDK only ) MUST be refreshed with/after swagger of new version is published. If you prefer NOT to refresh any specific SDK language upon swagger updates in the current PR, please leave details with justification here.

Contribution checklist (MS Employees Only):

[ ] I commit to follow the Breaking Change Policy of "no breaking changes"
[ ] I have reviewed the documentation for the workflow.
[ ] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

Applicability: :warning:
If your changes encompass only the following scenarios, you should SKIP this section, as these scenarios do not require ARM review.

Change to data plane APIs
Adding new properties
All removals

Otherwise your PR may be subject to ARM review requirements. Complete the following:

[ ] Check this box if any of the following apply to the PR so that the label "ARMReview" and "WaitForARMFeedback" will be added by bot to kick off ARM API Review.  Missing to check this box in the following scenario may result in delays to the ARM manifest review and deployment.

Adding a new service
Adding new API(s)
Adding a new API version
-[ ] To review changes efficiently, ensure you copy the existing version into the new directory structure for first commit and then push new changes, including version updates, in separate commits. You can use OpenAPIHub to initialize the PR for adding a new version. For more details refer to the wiki.

[ ] Ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If you have any breaking changes as defined in the Breaking Change Policy, request approval from the Breaking Change Review Board.
Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Additional details on the process and office hours are on the Breaking Change Wiki.
NOTE: To update API(s) in public preview for over 1 year (refer to Retirement of Previews)
Please follow the link to find more details on PR review process.

The PR is created based on the updates in the private branch. The updates in the PR has already been reviewed and approved with this PR Azure/azure-rest-api-specs-pr/12174

@live1206 - Generated ApiView link for .Net is not displayed, please take a look, thanks!
@raych1  - Generated ApiView link for Go is not displayed, please take a look, thanks!

/azp run

@live1206 - Generated ApiView link for .Net is not displayed, please take a look, thanks!

@zedy-wj I saw your service configured both .Net track 1 and track 2. Track 2 SDK automation succeeded, track 1 threw error while parsing swagger, track 1 is deprecated please remove it from readme.md.

@sebastianrex - Please remove .Net track1 from readme.md because it has been deprecated.

@live1206 - Generated ApiView link for .Net is not displayed, please take a look, thanks! @raych1 - Generated ApiView link for Go is not displayed, please take a look, thanks!

@zedy-wj , no change for API view for both dotnet and go are expected as this PR only changes the java/python readme.

@live1206 - Approved as changes have already reviewed and approved in https://github.com/Azure/azure-rest-api-specs-pr/pull/12174. .Net track1 has been removed from readme.md. Please take a look and merge it.


{Compute} az snapshot create: import_enum of DiskCreateOption is changed to import

Related command

az snapshot create
Description

IMPORT_ENUM keyError
close https://github.com/Azure/azure-cli/issues/24263
Testing Guide

History Notes

{Compute} az snapshot create: import_enum of DiskCreateOption is changed to import

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Compute

/azp run


(PDB-1300) Update acceptance suite for Puppet 4.0

This pull request updates the PuppetDB acceptance test suite to be able to run against Puppet 4.0 using the puppet-agent and puppetserver packages. Specifically, this pull request focuses on enabling the testing of this platform on RHEL 7 using the embedded database.

Pin to beaker 7d0cccf
Add options file for puppetserver and embedded database
Add nightly repos for puppet-agent and puppetserver on RHEL 7
Modify use of global manifest value to use a constructed environmentpath instead
Quote all uses of file mode values
Update use of beaker puppetpath value to use host.puppet method instead

Can one of the admins verify this patch?

@pljenkinsro test this please

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/948/

@pljenkinsro test this please

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/958/

@pljenkinsro retest this please

@pljenkinsro retest this please

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/959/

@pljenkinsro retest this please

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/992/

@pljenkinsro retest this please

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1023/

@pljenkinsro retest this please

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1028/

@pljenkinsro retest this please

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1029/

@pljenkinsro retest this please

@johnduarte is this still a WIP?

@wkalt I am still fighting through this on the AIO side. Currently, it looks like there is a bug in the Centos 7 package of iptables-services that causes the puppetlabs-firewall module to fail when installing puppetdb.

got it, thanks for the update @johnduarte

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1073/

Looks like @johnduarte's patch to puppetlabs-firewall has been merged now: https://github.com/puppetlabs/puppetlabs-firewall/pull/518 just waiting for a release I guess.

This PR is related to the problem also: https://github.com/puppetlabs/puppetlabs-firewall/pull/520

@pljenkinsro retest this please

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://jenkins.puppetlabs.com/job/platform_puppetdb_intn-sys_pr/1320/

Merged manually with the small manage_firewall fix here: https://github.com/puppetlabs/puppetdb/commit/7e14b1be4dff865723879c15606c8c5d1f5dc8c6


Move Count Tracker

Can we please add a capability of how many moves has passed for all 4 games(Olympiad)? This will help us understand how much time a player has until 40th move. This is the main thing in which most players make mistakes

this is not the repository for the eval bars


Implement Dark Theme Feature ✨

Pull Request Title
Issue Reference:
#259
Description:
I added a dark theme feature to the HireHub project. This provides users with an alternative viewing option, improving accessibility and user experience, especially in low-light environments.
Screenshots:

Type of change:

[x] Bug fix
[x] New feature
[ ] Breaking change
[x] Enhancement

Checklist:

[x] I have tested my changes and verified that they work
[x] My code follows the style guidelines of this project
[x] I have commented on my code, particularly in hard-to-understand areas
[x] My changes generate no new warnings
[x] New and existing unit tests pass locally with my changes

Additional Information:

@AnushkaChouhan25 it is not looking good make proper black theme

@Yashgabani845 Is it fine ?

or this one

or this one

@Yashgabani845 can you please review it

@Yashgabani845 Can you please respond?


path/filepath: Glob fails if it has a wildcard and ends with /

The function Glob tries to get the parent directory of the given path.
When a trailing slash is present, filepath.Split returns the path as it is as it can not split it further.
This fix cleans the path first by removing any trailing slash before getting the parent directory.
Fixes #33617

HI @jamdagni86 , May need to make judgments about directories and files
https://github.com/golang/go/issues/33617#issuecomment-557382741


Disable suggestions

please complete the following information:

OS version: Pop!_OS
Editor: Intellij]
Editor version: latest
Programming language: Markdown
TabNine extension version: Latest
Engine version (could be located within Tabnine Hub): Latest

Issue Details:
Markdown and Text (or similar extensions) file suggestions should be ignored by default. Disable suggestions should not be a pro config option.
gz#1687

For now, the option to disable Tabnine in specific extensions, etc. is a pro feature.
But I appreciate your feedback and will pass it on.


Incorrect types for rules, minimizer and plugins

Bug report

What is the current behavior?
In file: declarations\WebpackOptions.d.ts you can see types:
/**
 * A list of rules.
 */
export type RuleSetRules = ("..." | RuleSetRule)[];

/**
 * Plugins for the resolver.
 */
plugins?: ("..." | ResolvePluginInstance)[];

/**
 * Minimizer(s) to use for minimizing the output.
 */
minimizer?: ("..." | WebpackPluginInstance | WebpackPluginFunction)[];

If the current behavior is a bug, please provide the steps to reproduce.
N/A

What is the expected behavior?
"..."  should be removed from the types for these properties.

Other relevant information:
webpack version:  5.73.0
Node.js version: N/A
Operating System: All
Additional tools: N/A

"..." is valid, you can use ... to merge with default minimizer and options


Use the real error messages from node-webid

Half the error codes in the switch() did not even exist anymore and/or were very cryptic. The new version of node-webid sends more verbose error codes, and we can just forward those directly to the debugger/printer.

Good, will merge once I release the new node-webid


Issue on page /S46_logistics_learning.html

The expectation-maximization or EM algorithm is an algorithm that allows us to estimate measurement and motion models even when the state is only observed from measurements.

Maybe it should be 'estimate states' rather than 'estimate measurement'?

Oops, did not see this issue until now. No, it's supposed to be "measurement [models] and motion models".


add: CI workflows and issue templates

Fixes #1

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Comparison is base (0a013a3) 61.91% compared to head (fa6c155) 61.91%.

:exclamation: Current head fa6c155 differs from pull request most recent head 880e65f. Consider uploading reports for the commit 880e65f to get more accurate results

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main      #21   +/-   ##
=======================================
  Coverage   61.91%   61.91%
=======================================
  Files          28       28
  Lines         751      751
=======================================
  Hits          465      465
  Misses        286      286

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Fix fonts

Features

Game uses sans-serif
REPL output has same font as ace editor

Issues fixed

Fixes #247
Fixes #242

Pull Request Test Coverage Report for Build 495

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 24.611%

Totals

Change from base Build 493:
0.0%

Covered Lines:
769

Relevant Lines:
2639

💛  - Coveralls


feat(handlers): add getMembers and stronger typing for requestAllMembers()

Please describe the changes this PR makes and why it should be merged:
Status

[x] Code changes have been tested against the Discord API, or there are no code changes

Semantic versioning classification:

[x] This PR changes the library's interface (methods or parameters added)

[x] This PR includes breaking changes (methods removed or renamed, parameters moved or removed)

[ ] This PR only includes non-code changes, like changes to documentation, README, etc.

Could you separate this PR into two? Thanks.

Could you separate this PR into two? Thanks.


Initial implementation of #662

Implement mapping of naturalId and sourceFileId for FOLIO MARC-to-FOLIO authorities mapping according to MODDICORE-283

@banerjek Could you please take a look at this and let me know if my logic looks sound here?

Also fixes #663


Issues with form after submitting and then using the back button

As you can see the File radio button is selected, but it hasn't got the browse button.
Also "Add a data schema" is selected, but the UI to select a schema is not showing. If you unselect and reselect it does show up. If you had previously selected a file, it is showing the same issue as above, that it is missing the browse button.

In case you need it for debugging these issues were seen with Firefox 36.0.1 on Ubuntu Linux.

Thanks @morty, this is a great catch, and should be an easy fix.

Had another bug report for this. Working on it now.


Failed to request both edges events for lines: 13, 6

Hey, thanks for sharing this project.
When i built and ran it, the move_robot_task failed, and all other tasks worked well. The failure info is Failed to request both edges events for lines: 13, 6, any idea for this?

Sure, here is the updated response with the additional information:

Hi there,
The error message you encountered is related to testing the motor encoder data for the DOLY robot. The failure occurs because the interrupt pins are already occupied by the official kernel module doly_drive. To resolve this issue, you can temporarily unload this module by entering the command rmmod doly_drive in the command line. Alternatively, you can comment out the encoder-related functions in the move_task function, specifically EtrLeft.startEncoder(13,6);.
It is worth noting that the current method of reading the encoder is only suitable for testing the encoder. In actual multi-task operations, it may cause the move_task thread to block, and this needs further improvement.

Tried rmmod doly_drive and it worked. Really appreciate your quick reply.


Provide missing tests for the watcher

There are tests already provided by @jonaslagoni in this PR #191, we just need to make them end up in master and work with jest:

const { describe, before, it , afterEach} = require('mocha');
const chai = require('chai');
const sinonChai = require('sinon-chai');
const sinon = require('sinon');
chai.use(sinonChai);
const expect = chai.expect;
const Watcher = require('../../../../lib/watcher');
const fs = require('fs');
const nodePath = require('path');
describe('Watcher class', () => {
  before(() => {
  });

  it('should not be able to create empty path watcher', () => {

  });
  it('should be create watcher if path and not array are supplied', () => {
  });

  describe('fileChanged function', () => {

  });
  describe('getAllNonExistingPaths function', () => {

  });
  describe('closeWatcher function', () => {

  });
  describe('closeWatchers function', () => {

  });
  describe('convertEventType function', () => {

  });
  describe('isWatching function', () => {

  });
  describe('watch function', () => {
    it('should not keep notifying when no data was change in the file.', () => {

    });
    it('should handle the deletion of a watched file path correctly, when more paths can be watched', () => {
    });
    it('should handle the deletion of a watched file path correctly, when there are no more paths to watch', () => {
    });
    it('should handle the deletion of a watched directory path correctly, when there are no more paths to be watched', () => {
    });
    it('should handle the deletion of a watched directory path correctly, when more paths can be watched', () => {
    });
    describe('should be able to watch a single file path', () => {
      let watcher;
      const filePath = 'testfile.temp';
      before(() => {
        const stream = fs.createWriteStream(filePath, { flags: 'a' });
        stream.write('Text');
        stream.end();
        watcher = new Watcher(filePath);
      });
      afterEach(() => {
        watcher.closeWatchers();
        try{
          fs.unlinkSync(filePath);
        }catch(e){}
      });
      it('and give correct notice when the watched file are changed', () => {
        let expectedChangeObj;
        return new Promise((resolve, reject) => {
          watcher.watch((filechanges) => {
            try {
              expect(filechanges).to.not.be.null;
              expect(filechanges[filePath]).to.deep.equal(expectedChangeObj);
              resolve();
            } catch (e) {
              reject(e);
            }
          }, () => {
            reject('Should not have failed.');
          });
          expectedChangeObj = createFile(filePath);
        });
      });
      it('and give correct notice when the watched file are renamed', () => {
        let expectedChangeObj;
        const newPath = './testfile2.temp';
        createFile(filePath);
        return new Promise((resolve, reject) => {
          watcher.watch((filechanges) => {
            try {
              expect(filechanges).to.not.be.null;
              expect(filechanges[filePath]).to.deep.equal(expectedChangeObj);
              resolve();
            } catch (e) {
              reject(e);
            }
          }, () => {
            reject('Should not have failed.');
          });
          expectedChangeObj = renamePath(filePath, newPath);
        });
      });
    });

    function updateFile(path) {
      const stream = fs.createWriteStream(nodePath.resolve(path), { flags: 'a' });
      stream.write('append');
      stream.end();
    }
    function createFile(path) {
      const stream = fs.createWriteStream(nodePath.resolve(path));
      stream.write('created', (error) => {
        if (error) {
          console.error(`Something went wrong when creating file with path: ${path}, error was ${error}`);
        }
      });
      stream.end();
      return {
        eventType: 'changed',
        path
      };
    }
    function renamePath(oldPath, newPath) {
      fs.renameSync(nodePath.resolve(oldPath), nodePath.resolve(newPath));
      return {
        eventType: 'changed',
        path: newPath
      };
    }
    describe('should be able to watch multiple file paths', () => {
      it('and give correct notice when 1 watched file are changed', () => {
      });
      it('and give correct notice when multiple watched files are changed', () => {
      });
      it('and give correct notice when 1 watched file are renamed', () => {
      });
      it('and give correct notice when multiple watched files are renamed', () => {
      });
    });
    describe('should be able to watch both file paths and directory paths', () => {
      it('and give correct notice when 1 file are changed', () => {
      });
      it('and give correct notice when multiple watched files are changed', () => {
      });
      it('and give correct notice when 1 watched file are renamed', () => {
      });
      it('and give correct notice when multiple watched files are renamed', () => {
      });

      it('and give correct notice when 1 file are changed in 1 watched directory', () => {
      });
      it('and give correct notice when multiple files are changed in 1 watched directory', () => {
      });
      it('and give correct notice when 1 file are created in 1 watched directory', () => {
      });
      it('and give correct notice when multiple files are created in 1 watched directory', () => {
      });
      it('and give correct notice when 1 file are deleted from 1 watched directory', () => {
      });
      it('and give correct notice when multiple files are deleted from 1 watched directory', () => {
      });
      it('and give correct notice when 1 directory are deleted from 1 watched directory', () => {
      });
      it('and give correct notice when multiple directories are deleted from 1 watched directory', () => {
      });

      it('and give correct notice when 1 file are changed in each watched directory', () => {
      });
      it('and give correct notice when multiple files are changed in each watched directory', () => {
      });
      it('and give correct notice when 1 file are created in each watched directory', () => {
      });
      it('and give correct notice when multiple files are created in each watched directory', () => {
      });
      it('and give correct notice when 1 file are deleted from each watched directory', () => {
      });
      it('and give correct notice when multiple files are deleted from each watched directory', () => {
      });
      it('and give correct notice when 1 directory are deleted from each watched directory', () => {
      });
      it('and give correct notice when multiple directories are deleted from each watched directory', () => {
      });
    });
    describe('should be able to watch directory path', () => {
      it('and give correct notice when 1 file are changed in the watched directory', () => {
      });
      it('and give correct notice when multiple files are changed in the watched directory', () => {
      });
      it('and give correct notice when 1 file are created in the watched directory', () => {
      });
      it('and give correct notice when multiple files are created in the watched directory', () => {
      });
      it('and give correct notice when 1 file are deleted from the watched directory', () => {
      });
      it('and give correct notice when multiple files are deleted from the watched directory', () => {
      });
      it('and give correct notice when 1 directory are deleted from the watched directory', () => {
      });
      it('and give correct notice when multiple directories are deleted from the watched directory', () => {
      });
    });
    describe('should be able to watch multiple directory paths', () => {
      it('and give correct notice when 1 file are changed in 1 watched directory', () => {
      });
      it('and give correct notice when multiple files are changed in 1 watched directory', () => {
      });
      it('and give correct notice when 1 file are created in 1 watched directory', () => {
      });
      it('and give correct notice when multiple files are created in 1 watched directory', () => {
      });
      it('and give correct notice when 1 file are deleted from 1 watched directory', () => {
      });
      it('and give correct notice when multiple files are deleted from 1 watched directory', () => {
      });
      it('and give correct notice when 1 directory are deleted from 1 watched directory', () => {
      });
      it('and give correct notice when multiple directories are deleted from 1 watched directory', () => {
      });

      it('and give correct notice when 1 file are changed in each watched directory', () => {
      });
      it('and give correct notice when multiple files are changed in each watched directory', () => {
      });
      it('and give correct notice when 1 file are created in each watched directory', () => {
      });
      it('and give correct notice when multiple files are created in each watched directory', () => {
      });
      it('and give correct notice when 1 file are deleted from each watched directory', () => {
      });
      it('and give correct notice when multiple files are deleted from each watched directory', () => {
      });
      it('and give correct notice when 1 directory are deleted from each watched directory', () => {
      });
      it('and give correct notice when multiple directories are deleted from each watched directory', () => {
      });
    });
  });
});

I don't think it makes sense to keep it open, we have ongoing efforts for new CLI with completely new code and nobody will work on watcher here in the generator anytime soon

if somebody experience similar issue, please instead use https://github.com/asyncapi/cli and any CLI issues report there 🙏🏼