#expect(throws:) does not work with @MainActor

Description
#expect(throws:) with an async block seems to get confused when run in a @MainActor function:
import Testing

struct Test {
	@Test func works() async throws {
		await #expect(throws: TestError.self) {
			try await Task.sleep(nanoseconds: 1)
			throw TestError()
		}
	}

	@Test @MainActor func doesNotWork() async throws {
		await #expect(throws: TestError.self) {
			try await Task.sleep(nanoseconds: 1)
			throw TestError()
		}
	}
}

struct TestError: Error {}

Expected behavior
Both of these should compile and run fine.
Actual behavior
The second function causes mysterious errors inside the code generated by the macro.
Steps to reproduce
Compile the code above.
swift-testing version/commit hash
Whatever ships with Xcode 16.0
Swift & OS version (output of swift --version ; uname -a)
swift-driver version: 1.115 Apple Swift version 6.0 (swiftlang-<IP_ADDRESS>.10 clang-16<IP_ADDRESS>)
Target: arm64-apple-macosx15.0
Darwin Mac 24.0.0 Darwin Kernel Version 24.0.0: Tue Sep 24 23:38:45 PDT 2024; root:xnu-11215.1.12~1/RELEASE_ARM64_T8122 arm64

I am not able to reproduce any issue here using the 6.0.2 toolchain. I had to rename your test suite from Test as it conflicts with symbols exposed by Swift Testing.
There was an actor isolation fix implemented in 6.0.1. Please try updating your copy of Xcode to something newer than 16.0; if that doesn't help, we can reopen.

Can confirm that it does work on later Xcode! Thanks for pointing me at that.


Hmmm, good to know, thanks for filing the issue. Is this something you're interested in investigating?

Does anyone know if there is a way to exclude certain tests from being run with xdist?

I think the easiest is to add an @pytest.mark.single, and then use pytest -m 'not single' in CI.


Image issue with offer (JPG)

Issue with picture(JPG) only partially appearing
This one is a little different, a blue square appears but not the actual image
GUID:   00d0d174b27fe20f:
this is the link and it works fine in a browser.
Image included in text is the following:
http://i2.wp.com/syscoin.org/wp-content/uploads/2015/07/Navy-ShrtSlv-LogoOnly-Front.jpg?fit=300%2C250
I've also tried duplicating the issue via GUID: 17050c5a079f5a72, but removing the ?fit=300%2C250 end, but still same problem.
This is what appears:

@sidhujag this problem is still happening latest 3/7/2016 build.

@sidhujag this problem is still happening latest 3/12/2016 build.

@sidhujag Issue still happening on 3/17 build

@sidhujag issue remains in 6/18 2.1 alpha build.

@sidhujag this issue remains in 9/9 build, fyi same issue happens when you remove the resizing of the pic as link below:
http://i2.wp.com/syscoin.org/wp-content/uploads/2015/07/Navy-ShrtSlv-LogoOnly-Front.jpg

Closing this issue since offer features has been moved to Blockmarket


Instructions for setting up a dev environment and contribution standards

Is your feature request related to a problem? Please describe.
Contributing this this project is currently slowed down by not having instructions for a standardized dev environment set up. We also observed that PR contributions are not formatted consistently.
Describe the solution you'd like

Clear instructions and supporting file for setting up a standardized dev environment.
Instructions for setting up relevant pre-commit hooks

Describe alternatives you've considered
NA
Additional context
NA

@ShengpeiWang for 1. would a poetry setup and corresponding documentation address this?

@ShengpeiWang for 1. would a poetry setup and corresponding documentation address this?

Yes!


fix: add missing +1 for month

This is a fix to a missed +1 in PR #1884.  Month for date is 0-11, not 1-12 so this fixes that offset for the date string.

Warnings

:warning:

Please include an updated CHANGELOG.md file.This way we can keep track of all the contributions.

  Generated by :no_entry_sign: dangerJS


Failed to build (APK/Appbundle) on Android

Iam using package appwrite pub dev which depends on this package. when i build IOS working fine, but when i build APK/Appbundle Android it showing error that says:

What went wrong:
A problem occurred evaluating project ':flutter_web_auth_2'.

No signature of method: build_br839y3cjw240hfyqvnkgs25f.android() is applicable for argument types: (build_br839y3cjw240hfyqvnkgs25f$_run_closure2) values: [build_br839y3cjw240hfyqvnkgs25f$_run_closure2@54024517]

my flutter version: 3.3.8

This is because of the new AGP requirements of this package.
You need to update your android gradle plugin to at least 7.x.


Fix issue 63

https://github.com/Samsung/GearVRf/issues/63
GearVRf-DCO-1.0-Signed-off-by: Jon Shemitz
<EMAIL_ADDRESS>

This should fix the issue, but I don't have any code that exercises GVRFloatTexture - @thomasflynn or @ejsamsung, can you test this?

Tested by @ejsamsung


Zerg larva not spawning while hatchery is morphing

Updated buildingcount and addlarva function to continue larva generation for morphing lair and hive.


WIP: 1551 migration create a default group for each organisation

What problem does this pull request solve?
Trello card:

Things to consider when reviewing

Ensure that you consider the wider context.
Does it work when run on your machine?
Is it clear what the code is doing?
Do the commit messages explain why the changes were made?
Are there all the unit tests needed?
Has all relevant documentation been updated?

We have these changes on another branch so closing this PR


div wrapper in Hits [react-instantsearch]

Is there any way to remove the div wrapper in Hits?
It prevents me from using table rows with Hits.

Hi @l4u
You can have the full control of the rendering using the connectors. In this case, you can use the connectHits and go wild :) Let me know if that fits what you're looking for.

Thanks @bobylito. It works.


chore: add compiled lib folder, don't rely on package.json hooks

fix component test
related https://github.com/status-im/status-mobile/pull/15071

@Parveshdhull request review

@Parveshdhull request review

https://github.com/status-im/status-mobile/pull/15071#issuecomment-1433526073


What's a "keystroke"? Can you give an example?

What's a "keystroke"? Can you give an example?

Sorry for the late comment. A keystroke is what follows when you press any key on your keyboard. When simulating keystrokes, you make the computer believe someone has actually pressed a key without pressing it manually. Simulated keystrokes will be handled just like normal manual input.


turkic publish offline mode outputs some rubbish links

When there is more than 1 video in the vatic database (ascertained turkic list), the turkic publish --offline options spews out invalid URLs. For instance, in my case, I had 2 videos (2 separate identifiers) in the vatic database. The tool outputs:
http://localhost?id=1&hitId=offline
http://localhost?id=2&hitId=offline
http://localhost?id=3&hitId=offline
http://localhost?id=16&hitId=offline
http://localhost?id=17&hitId=offline
Of these, only the last 2 are valid. Trying to access the first 3 URLs in the browser just displays '"Downloading the video"
0%

I am also trying to figure out how to actually launch turkic for the first time, offline.
turkic find
returns a bunch of links like yours that lead to a "Server Error" page.
turkic publish --offline doesn't do anything as far as I can tell.

#24

The issue lies in the database structure. This happens when you had previously loaded videos and deleted them. The next uploaded video will not have in the url id=1 but the incremental number of the segments.
For example, id=1 stands for the first segment of the first video you upload. since id is key for the table "jobs" you cannot reset it but goes incrementally.
Try manually το change the id number. I found mine in id=51, and works.
I will also try to find a better solution, since in the current structure it is too difficult to work with many videos in offline mode.

I agree with the above. I believe the error occurs when a video is loaded without the 'offline' keyword but published with the 'offline' keyword. When that video is deleted the urlid counter is not properly adjusted and continues to include that deleted video. The accurate analogue in the database is groupid under vatic.turkic_hits Those id's should still correspond to the urlid's.

my problem is that it sends out many links. But none of them works.
I load the video only once.
And I use the option "--offline" for loading the publishing.
Do you have any suggestion?
http://localhost/?id=85&hitId=offline
http://localhost/?id=86&hitId=offline
http://localhost/?id=87&hitId=offline
http://localhost/?id=88&hitId=offline
http://localhost/?id=89&hitId=offline
http://localhost/?id=90&hitId=offline
http://localhost/?id=91&hitId=offline
http://localhost/?id=92&hitId=offline
http://localhost/?id=93&hitId=offline
http://localhost/?id=94&hitId=offline
http://localhost/?id=95&hitId=offline
http://localhost/?id=96&hitId=offline
http://localhost/?id=97&hitId=offline
http://localhost/?id=98&hitId=offline
http://localhost/?id=99&hitId=offline
http://localhost/?id=100&hitId=offline
http://localhost/?id=101&hitId=offline
http://localhost/?id=102&hitId=offline
@zesoft23 @aaman-ee


2023-04-06 (6 April 2023) - Morphir Project Meeting

Date
Thursday 6 April 2023 - 11am ET / 4pm UK
Untracked attendees

Name
Firm
Comment

Meeting notices

FINOS Project leads are responsible for observing the FINOS guidelines for running project meetings. Project maintainers can find additional resources in the FINOS Maintainers Cheatsheet.

All participants in FINOS project meetings are subject to the LF Antitrust Policy, the FINOS Community Code of Conduct and all other FINOS policies.

FINOS meetings involve participation by industry competitors, and it is the intention of FINOS and the Linux Foundation to conduct all of its activities in accordance with applicable antitrust and competition laws. It is therefore extremely important that attendees adhere to meeting agendas, and be aware of, and not participate in, any activities that are prohibited under applicable US state, federal or foreign antitrust and competition laws. Please contact<EMAIL_ADDRESS>with any questions.

FINOS project meetings may be recorded for use solely by the FINOS team for administration purposes. In very limited instances, and with explicit approval, recordings may be made more widely available.

Agenda

[ ] Convene, roll call, welcome new people (5mins)
[ ] Display FINOS Antitrust Policy summary slide
[ ] Review Meeting Notices (see above)
[ ] Approve previous meeting minutes - https://github.com/finos/morphir/issues?q=is%3Aissue+is%3Aclosed+label%3Ameeting
[ ] FINOS Hackathon LCR and Open RegTech Reporting Recruitment

https://github.com/finos/community/discussions/245
https://github.com/finos/community/discussions/252

[ ] AOB, Q&A & Adjourn (5mins)

Decisions Made

[ ] Decision 1
[ ] Decision 2
[ ] ...

Action Items

[ ] Action 1
[ ] Action 2
[ ] ...

Zoom info

https://zoom.us/j/95452540437?pwd=TEk0bitJcVFsK3lrWVZCYmxyTm5LZz09
Meeting ID: 954 5254 0437
Passcode: 778814

Dial-in

Find your local number: https://zoom.us/u/aFGSSGV9x

Github Repo: https://github.com/finos/morphir/
Mailing List: Email<EMAIL_ADDRESS>to subscribe to our mailing list

Attila Mihaly @ Morgan Stanley

Ronald Ssebalamu / FINOS


Is the Chinese language code currently using cmn or zh_cN?

Is the Chinese language code currently using cmn or zh_cN?

You can see here they're all 2 letter ISO 639-1 codes https://huggingface.co/rhasspy/piper-voices/tree/v1.0.0
And please ask questions in the Discussions section instead

I want to train a new single speaker model on aishell dataset , but when I set the language to zh, the preprocess script gets the following err, but when I set cmn, the proprocess script works. Is it wrong or right?
ERROR:preprocess:Failed to process utterance: Utterance(text='培训费每人一千二百元', audio_path=PosixPath('/workspace/dataset/wavs/BAC009S0174W0461.wav'), speaker=None, speaker_id=None, phonemes=None, phoneme_ids=None, audio_norm_path=None, audio_spec_path=None, missing_phonemes=Counter())
Traceback (most recent call last):
File "/workspace/piper/src/python/piper_train/preprocess.py", line 302, in phonemize_batch_espeak
all_phonemes = phonemize_espeak(casing(utt.text), args.language)
File "/opt/conda/lib/python3.10/site-packages/piper_phonemize/init.py", line 38, in phonemize_espeak
return _phonemize_espeak(text, voice, str(data_path))
RuntimeError: Failed to set eSpeak-ng voice


Use the Alpine image to reduce size and fix security

The current high and critical image OS vulnerabilities are:
$ trivy image --severity HIGH,CRITICAL quay.io/hmpps/hmpps-delius-interventions-event-listener
{snip}
quay.io/hmpps/hmpps-delius-interventions-event-listener (debian 11.1)
=====================================================================
Total: 6 (HIGH: 2, CRITICAL: 4)
{snip}

❗ This is not reported however, as our nightly trivy scan implement --ignore-unfixed, which is basically hiding all of these, which to me feels wrong
This image has no OS vulnerabilities and about half the size:
$ docker build . --tag=local.event-listener
{snip}

$ trivy image --severity HIGH,CRITICAL local.event-listener
local.event-listener (alpine 3.14.2)
====================================
Total: 0 (HIGH: 0, CRITICAL: 0)

It does not fix the Java vulnerabilities flagged up by Trivy though

🙋 Branch builds should build the docker image and scan it, right?


Qwen-72B合并LoRA权重自动被killed

Reminder

[X] I have read the README and searched the existing issues.

System Info
peft                              0.11.1
torch                             2.3.0
llamafactory                      0.8.3.dev0

model_name_or_path: /data/zhaopengfeng/models/Qwen2-72B-Instruct
adapter_name_or_path: /data/zhaopengfeng/kddcup_repo/ckpt_output/fsdp_qlora/alpaca_0704_all/checkpoint-124
template: qwen
finetuning_type: lora

### export
export_dir: /data/zhaopengfeng/kddcup_repo/ckpt_output/fsdp_qlora/alpaca_0704_all/checkpoint-124/merge
export_size: 2
export_device: cpu
export_legacy_format: false

cuda driver version 12.4
服务器 RAM 252GB
权重是通过fsdp+qlora训练得到的
Reproduction
(vllm) zhaopengfeng@zju:/data/zhaopengfeng/LLaMA-Factory$ llamafactory-cli export examples/merge_lora/llama3_lora_sft.yaml

[2024-07-07 17:51:35,065] [INFO] [real_accelerator.py:203:get_accelerator] Setting ds_accelerator to cuda (auto detect)
 [WARNING]  async_io requires the dev libaio .so object and headers but these were not found.
 [WARNING]  async_io: please install the libaio-dev package with apt
 [WARNING]  If libaio is already installed (perhaps from source), try setting the CFLAGS and LDFLAGS environment variables to where it can be found.
 [WARNING]  Please specify the CUTLASS repo directory as environment variable $CUTLASS_PATH
 [WARNING]  sparse_attn requires a torch version >= 1.5 and < 2.0 but detected 2.3
 [WARNING]  using untested triton version (2.3.0), only 1.0.0 is known to be compatible
[INFO|tokenization_utils_base.py:2159] 2024-07-07 17:51:38,884 >> loading file vocab.json
[INFO|tokenization_utils_base.py:2159] 2024-07-07 17:51:38,884 >> loading file merges.txt
[INFO|tokenization_utils_base.py:2159] 2024-07-07 17:51:38,884 >> loading file tokenizer.json
[INFO|tokenization_utils_base.py:2159] 2024-07-07 17:51:38,885 >> loading file added_tokens.json
[INFO|tokenization_utils_base.py:2159] 2024-07-07 17:51:38,885 >> loading file special_tokens_map.json
[INFO|tokenization_utils_base.py:2159] 2024-07-07 17:51:38,885 >> loading file tokenizer_config.json
[WARNING|logging.py:313] 2024-07-07 17:51:39,164 >> Special tokens have been added in the vocabulary, make sure the associated word embeddings are fine-t
uned or trained.
07/07/2024 17:51:39 - INFO - llamafactory.data.template - Replace eos token: <|im_end|>
[INFO|configuration_utils.py:731] 2024-07-07 17:51:39,174 >> loading configuration file /data/zhaopengfeng/models/Qwen2-72B-Instruct/config.json
[INFO|configuration_utils.py:800] 2024-07-07 17:51:39,176 >> Model config Qwen2Config {
  "_name_or_path": "/data/zhaopengfeng/models/Qwen2-72B-Instruct",
  "architectures": [
    "Qwen2ForCausalLM"
  ],
  "attention_dropout": 0.0,
  "bos_token_id": 151643,
  "eos_token_id": 151645,                                                                                "hidden_act": "silu",                                                                                "hidden_size": 8192,                                                                                "initializer_range": 0.02,
  "intermediate_size": 29568,
  "max_position_embeddings": 32768,
  "max_window_layers": 80,
  "model_type": "qwen2",
  "num_attention_heads": 64,
  "num_hidden_layers": 80,
  "num_key_value_heads": 8,
  "rms_norm_eps": 1e-06,
  "rope_theta": 1000000.0,
  "sliding_window": 131072,
  "tie_word_embeddings": false,
  "torch_dtype": "bfloat16",
  "transformers_version": "4.42.2",
  "use_cache": true,
  "use_sliding_window": false,
  "vocab_size": 152064
}

07/07/2024 17:51:39 - INFO - llamafactory.model.patcher - Using KV cache for faster generation.

[INFO|modeling_utils.py:3553] 2024-07-07 17:51:39,226 >> loading weights file /data/zhaopengfeng/models/Qwen2-72B-Instruct/model.safetensors.index.json
[INFO|modeling_utils.py:1531] 2024-07-07 17:51:39,243 >> Instantiating Qwen2ForCausalLM model under default dtype torch.bfloat16.
[INFO|configuration_utils.py:1000] 2024-07-07 17:51:39,244 >> Generate config GenerationConfig {
  "bos_token_id": 151643,
  "eos_token_id": 151645
}

Loading checkpoint shards: 100%|█████████████████████████████████████████████████████████████████████████████████████████| 37/37 [00:16<00:00,  2.20it/s]
[INFO|modeling_utils.py:4364] 2024-07-07 17:51:57,116 >> All model checkpoint weights were used when initializing Qwen2ForCausalLM.

[INFO|modeling_utils.py:4372] 2024-07-07 17:51:57,116 >> All the weights of Qwen2ForCausalLM were initialized from the model checkpoint at /data/zhaopeng
feng/models/Qwen2-72B-Instruct.
If your task is similar to the task the model of the checkpoint was trained on, you can already use Qwen2ForCausalLM for predictions without further trai
ning.
[INFO|configuration_utils.py:953] 2024-07-07 17:51:57,130 >> loading configuration file /data/zhaopengfeng/models/Qwen2-72B-Instruct/generation_config.js
on
[INFO|configuration_utils.py:1000] 2024-07-07 17:51:57,130 >> Generate config GenerationConfig {
  "bos_token_id": 151643,
  "do_sample": true,
  "eos_token_id": [
    151645,
    151643
  ],
  "pad_token_id": 151643,
  "repetition_penalty": 1.05,
  "temperature": 0.7,
  "top_k": 20,
  "top_p": 0.8
}

07/07/2024 17:51:57 - INFO - llamafactory.model.model_utils.attention - Using torch SDPA for faster training and inference.
Killed

Expected behavior
No response
Others
No response

export_device: auto


Fix: remove legacy API versions

Thanks @bacht-fidi !
I added a note about the cert-manager prerequisite in the README and I will merge this.
FYI @klopfenstein-puzzle @madchr1st

That's great news! Thanks @Pidu2 , appreciated


local images load failed

For example
![](image/微生物学笔记/1641386328583.png)

![](image/微生物学笔记/1641386612027.png)

Above is grammar about local images in markdown. In marktext and vscode, load image success. However, it is fail to load images in milkdown.
VS Code

Milkdown

Same here。

Same here

Resolved by https://github.com/Saul-Mirone/milkdown-vscode/commit/577e5734fba9ca3616452d3fd0adfdb7a9896ce4

Released with 0.0.13.

Thanks for help, I will try it if I have time.👍


High CPU usage and Low GPU

I'm running this code
python inference_realesrgan.py -n RealESRGAN_x4plus_anime_6B -i inputs --output "results/output_test" --fp32 --outscale 2
My input images is 576x1024
And my Graphic Card is RTX 3060 12GB
Is that normal?

@DenisKen not sure if it is intended, but when follow instructions from the readme it installs PyTorch without CUDA support.
So I had to manually reinstall PyTorch like
pip install torch==2.0.0+cu118 -f https://download.pytorch.org/whl/torch_stable.html
pip install torchvision==0.15.1+cu118 -f https://download.pytorch.org/whl/torch_stable.html

then it works. You can check manually after installation
$ python
>>> import torch
>>> torch.zeros(1).cuda()
tensor([0.], device='cuda:0')
>>> torch.cuda.get_arch_list()
['sm_37', 'sm_50', 'sm_60', 'sm_61', 'sm_70', 'sm_75', 'sm_80', 'sm_86', 'sm_90', 'compute_37']
>>> torch.cuda.is_available()
True

@DenisKen not sure if it is intended, but when follow instructions from the readme it installs PyTorch without CUDA support.
So I had to manually reinstall PyTorch like
pip install torch==2.0.0+cu118 -f https://download.pytorch.org/whl/torch_stable.html
pip install torchvision==0.15.1+cu118 -f https://download.pytorch.org/whl/torch_stable.html

then it works. You can check manually after installation
$ python
>>> import torch
>>> torch.zeros(1).cuda()
tensor([0.], device='cuda:0')
>>> torch.cuda.get_arch_list()
['sm_37', 'sm_50', 'sm_60', 'sm_61', 'sm_70', 'sm_75', 'sm_80', 'sm_86', 'sm_90', 'compute_37']
>>> torch.cuda.is_available()
True

I followed your instruction but however, it did not work.
Still using high CPU, RAM and Disk, only GPU was still stable and it did not even use GPU performance at all.

@Ryosama2 for me it worked. It looks like you installed the torch cuda version in the base env and then switched to RESRGAN env which might still have the wrong cuda version?

我也是这样请问解决了吗

@DenisKen not sure if it is intended, but when follow instructions from the readme it installs PyTorch without CUDA support.
So I had to manually reinstall PyTorch like
pip install torch==2.0.0+cu118 -f https://download.pytorch.org/whl/torch_stable.html
pip install torchvision==0.15.1+cu118 -f https://download.pytorch.org/whl/torch_stable.html

then it works. You can check manually after installation
$ python
>>> import torch
>>> torch.zeros(1).cuda()
tensor([0.], device='cuda:0')
>>> torch.cuda.get_arch_list()
['sm_37', 'sm_50', 'sm_60', 'sm_61', 'sm_70', 'sm_75', 'sm_80', 'sm_86', 'sm_90', 'compute_37']
>>> torch.cuda.is_available()
True

Coooool, I followed your steps and solved the problem very well.
A little bit different is the version I use:
pip install torch==1.13.1+cu117 torchvision==0.14.1+cu117 --extra-index-url https://download.pytorch.org/whl/cu117

The wrong Conda environment may be used，

@DenisKen not sure if it is intended, but when follow instructions from the readme it installs PyTorch without CUDA support.
So I had to manually reinstall PyTorch like
pip install torch==2.0.0+cu118 -f https://download.pytorch.org/whl/torch_stable.html
pip install torchvision==0.15.1+cu118 -f https://download.pytorch.org/whl/torch_stable.html

then it works. You can check manually after installation
$ python
>>> import torch
>>> torch.zeros(1).cuda()
tensor([0.], device='cuda:0')
>>> torch.cuda.get_arch_list()
['sm_37', 'sm_50', 'sm_60', 'sm_61', 'sm_70', 'sm_75', 'sm_80', 'sm_86', 'sm_90', 'compute_37']
>>> torch.cuda.is_available()
True

 I followed your instruction but however, it did not work. Still using high CPU, RAM and Disk, only GPU was still stable and it did not even use GPU performance at all.


[Feature Request] Optional Field for oauth_verifier in OAuth 1.0

Insomnia Version: 5.14.9
Operating System: macOS

Details
Adding an optional field for oauth_verifier as per the Token Exchange for OAuth 1.0a - https://oauth.net/core/1.0a/#rfc.section.6.3.1

@hubsta would this just need to be a static value in the OAuth 1.0 form?


[Feature Request] Eliminate encode_raw_bytes from canonical serialization

Right now there are two means to encode byte arrays in canonical serialization. This requires authors to specify their byte encoding format and can lead to confusion. To address that, let's simplify the specification and eliminate the optional encoding of the length and make it required.

We prepend 4 bytes. I completely agree that it improves readability but it also makes the canonical definition have non-trivial ambiguity. When reading a struct, when as a byte array require a prefix or not. To mitigate that, it was decided to accept the 4 byte prefix. The code was merged in https://github.com/libra/libra/commit/59d29647f8aac104c6552dff7dd292f6a3953f10

True, bincode serialization prepends 8 bytes, but ours 4, meaning the max payload is 2^32 bytes and incompatible with bincode, which I guess is ok.
We need to crosscheck this feature more carefully.


Need to wrap response

I'm using Ember and Ember Data both 2.15.0, and I needed to wrap the response of the FixtureAdapter methods in order for them to be recognised by the calling method (from the Ember Data Store?) and processed into real Ember.Models. Eg:
// app/adapters/post.js
import FixtureAdapter from 'ember-data-fixture-adapter';
export default FixtureAdapter.extend({
	simulateRemoteResponse: false,
	findAll: function(){
		return this._super.apply(this, arguments).then(function(response){
			return { posts: response };
		});
	}
});

I'm using a RESTSerializer, if that matters, but I can't see how.
Is this intentional? Or perhaps caused by changes to Ember Data?
I'm currently upgrading from Ember 1.13 to 2.15.
The exact same fixtures and models worked fine in 1.13 using the built-in DS.FixtureAdapter, without needing to wrap the responses.

Sorry that you are running into issues, this repo / project is essentially deprecated and unmaintained.
I'm closing this (so that I can archive the repo and make it clearer to folks that this shouldn't be used going forward)...


V0.6.3 staging

Codecov Report

Merging #89 into series/0.6.x will not change coverage.
The diff coverage is n/a.

@@              Coverage Diff              @@
##           series/0.6.x      #89   +/-   ##
=============================================
  Coverage         58.15%   58.15%
=============================================
  Files                10       10
  Lines               282      282
  Branches             21       21
=============================================
  Hits                164      164
  Misses              118      118

Continue to review full report at Codecov.

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


add custom config with option "additionalScrapeConfigs" but can't create pod whitout error

I add the option "additionalScrapeConfigs:" in manifests/prometheus-prometheus.yaml and apply -f it
and i can create prometheus/k8s   but no pods appear in ns/monitoring without error
It's normal after deleting the option "additionalScrapeConfigs:"
  replicas: 2
 additionalScrapeConfigs:
   name: additional-scrape-configs
    key: prometheus-additional.yaml

That most likely means your config in the secret is malformed.

That most likely means your config in the secret is malformed.

as you said, i rewrite the config file and the problem is solved. thank you for your helping~


Introduce RunCompiledScript

Based off https://github.com/Shopify/v8go/pull/11
Using the latest v8go master
Adds RunCompiledScript on a v8 context using the cached script from CompileScript on a v8 isolate
TODO:

How can we assert in a test that the compilation for the script is using the cached data on the source vs the actual source string itself?
There's duplication between RunScript and RunCompiledScript in v8go.cc - maybe a shared private function can be extracted that accepts the cached data arguments and if theyre empty, proceeds normally, otherwise, creates the cached data + source objects and uses them.

We will probably want to more closely follow the V8 API before upstreaming this work. E.g. we would want to expose the Script / UnboundScript types, so that we can later expose methods from them or allow them to be passed to functions that accept them as an argument, without the need for breaking changes.

v8go already has a RunScript function that is a helper and not aligned to the v8 api. The function is available on the context and it combines compiling the source code into a (bound) script and running it in that context without ever exposing the script resources for direct use.
I think the balance in question is knowing whether there are more usecases or a better user experience for having access to the unbound script object vs the compiled/cached data.
An unbound script as a type needs to be bound to a context before it can be run so we'd either have a helper function here anyway which accepts the unbound script and the context to bind it to as well as run it in, or we expose another cgo api call BindToCurrentContext that needs to be executed on the unbound script object, returning a script object that can then be called with script.Run(ctx).
If we pass around the []byte, then a user can compile the script in one isolate with a single command and then use that compiled script as an argument to the subsequent function to run it in a context belonging to a different isolate. Internally that helper function behaves similarly to our v8go helper function RunScript with the additional step of creating a Source object that accepts both the uncompiled sourced script and the compiled bits (as shown in this PR).
There may be more benefits to exposing the UnboundScript and Script types in v8go. An UnboundScript does have some useful information like GetScriptName, GetSourceURL, GetSourceMappingURL which could be useful.

A benefit of exposing and using an UnboundScript type from c++ to go and back would be avoiding the Source/Compile functions we need to use currently in RunCompiledScript which may not be working as I expect right now when you provide the uncompiled source code as well as the cached data and the option to kConsumeCodeCache. I can give it a try and measure it with the current tests I have.


nixos/plasma5: fix users tab in system settings + minor formatting

Motivation for this change
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages 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/)
21.11 Release Notes (or backporting 21.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

[ ] Fits CONTRIBUTING.md.

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
Result of nixpkgs-review pr 144024 run on x86_64-linux 1

1 package marked as broken and skipped:

xmonad_log_applet

56 packages built:

accountsservice
adapta-gtk-theme
chrome-gnome-shell
cinnamon.cinnamon-common
cinnamon.cinnamon-gsettings-overrides
cinnamon.cinnamon-screensaver
gnome.gdm
gnome.gnome-applets
gnome.gnome-control-center (gnome.gnome_control_center)
gnome.gnome-flashback
gnome.gnome-initial-setup
gnome.gnome-panel
gnome.gnome-session (gnome.gnome_session)
gnome.gnome-shell (gnome.gnome_shell)
gnome.gnome-terminal (gnome.gnome_terminal)
gnome.gnome-tweaks (gnome.gnome-tweak-tool)
gnomeExtensions.easyScreenCast
gnomeExtensions.gsconnect
gnomeExtensions.night-theme-switcher
lightdm
lightdm-enso-os-greeter
lightdm-mini-greeter
lightdm-tiny-greeter
lightdm_gtk_greeter
lightdm_qt
malcontent
malcontent-ui
monitor
pantheon.elementary-default-settings
pantheon.elementary-greeter
pantheon.elementary-gsettings-schemas
pantheon.elementary-session-settings
pantheon.elementary-settings-daemon
pantheon.gala
pantheon.switchboard-plug-a11y
pantheon.switchboard-plug-mouse-touchpad
pantheon.switchboard-plug-pantheon-shell
pantheon.switchboard-plug-power
pantheon.switchboard-plug-security-privacy
pantheon.switchboard-with-plugs
pantheon.wingpanel
pantheon.wingpanel-applications-menu
pantheon.wingpanel-indicator-a11y
pantheon.wingpanel-indicator-bluetooth
pantheon.wingpanel-indicator-datetime
pantheon.wingpanel-indicator-keyboard
pantheon.wingpanel-indicator-network
pantheon.wingpanel-indicator-nightlight
pantheon.wingpanel-indicator-notifications
pantheon.wingpanel-indicator-power
pantheon.wingpanel-indicator-session
pantheon.wingpanel-indicator-sound
pantheon.wingpanel-with-indicators
phosh
vimix-gtk-themes
whitesur-gtk-theme


Error in Suzuka + bridge setup since merge of 561

Describe the bug
Suzuka + bridge build, run with command
CELESTIA_LOG_LEVEL=FATAL CARGO_PROFILE=release CARGO_PROFILE_FLAGS=--release  nix develop --extra-experimental-features nix-command --extra-experimental-features flakes --command bash  -c "just bridge native build.setup.eth-local.celestia-local.bridge --keep-tui"

fails since the merge of 651 (commit 7aa85be210524d0b18c1f29299e4f3be8778d13b Merge pull request #561 from movementlabsxyz/primata/contract-pipeline)
See screenshot for error:

This highlights the need to utilize proper CI checks when merging PRs.
To Reproduce
At the movement project root:
git reset --hard 249228ad58f31bd9e0f492d83b9396baff72e77c

You should see
HEAD is now at 249228ad update: client calls with match arms

This is the commit prior to the merge of 651.
Expected behavior
This command should start the bridge without errors:
CELESTIA_LOG_LEVEL=FATAL CARGO_PROFILE=release CARGO_PROFILE_FLAGS=--release  nix develop --extra-experimental-features nix-command --extra-experimental-features flakes --command bash  -c "just bridge native build.setup.eth-local.celestia-local.bridge --keep-tui"

Screenshots
Expected behavior screenshot:

If we had our new e2e running on cicd:bridge job, this would have caught the issue before merging. This effectively stalls e2e testing on the bridge. What I would suggest is a dedicated PR just to add the bridge e2e test in CI (at the moment it's just integration tests).
Then revert this PR, and re-merge it with it having to pass that test.
@l-monninger @0xPrimata please chime in on what you think the appropriate approach is here.


Display emulator version

it would be nice to know the emulator version for debugging purposes - https://github.com/onflow/flip-fest/pull/89#issuecomment-958118594

[x] implement getVersion() function to FlowEmulatorService (should execute and parse flow version command)
[x] add /api/flow/version that retrieves emulator version
[ ] display emulator version in settings or navigation view
[x] add design

UI DESIGN:

Fixed in e6546b4de0aedd64e5d88df25995a2b41e531a8b and cc3ac71b3b607cbafd22e45af293c83a0c4b5d93.


Clear and Save As buttons should have a hover action

Current behavior
The Clear and Save As buttons on the Distance and Direction pane do not have a hover action to indicate to the user that those buttons will do something when clicked. They do have tooltips that appear.
Expected behavior
Requesting that they also have a hover action that occurs to help the user understand that the button does something when clicked. These buttons should behave the way the Add Favorite button behaves on the Military Symbol Editor pane.

This should exist on all four tabs of the Distance and Direction pane
Screenshot is of Dark theme, but the same example/expected behavior should apply to Light theme

Verified with #658 in ArcMap (10.6.1) and Pro (2.4.19921)

@lfunkhouser is this something you want to put in the doc? no sweat either way, just seems minor, and not previously listed as a known issue


[0.2] Combine sides and sizes for rounded utilities, like we do with border widths

This PR reverts an API design decision that was made just prior to 0.1.0 back to how it used to be in the secret days.
It combines rounded sides and sizes into one utility, like this:

Right now, to make only one side of an element round, you need to combine a size utility and a side utility:

This had the benefit of not repeating the size utilities for every side, which seemed like a win.
There's a few downsides that ultimately I don't think ended up being worth it though:

You have to combine two utilities for something that's actually done with one CSS property; that seems a bit weird.

The implementation is too "clever". The way it works is when you add rounded-t, it sets the bottom border radiuses back to 0. I don't like that a class designed to say "make the top corners round" actually just makes the bottom corners square. It should be simpler and more obvious.

You can't make 3 out of 4 corners rounded because of the implementation in point #2.

The implementation mentioned in point #2 leads to this annoying situation where if you want to change what side is rounded at a different breakpoint, you have to respecify the size.
For example, this won't work as you expect:

You'd think that would have top rounded corners by default, and left rounded corners on medium screens and up. But what actually happens, is that on medium screens and up, only the top left corner is rounded, because rounded-t sets bottom radiuses to 0 and rounded-l sets right radiuses to 0. Grim!
So currently you need to do this:

With the changes in this PR, sides and sizes are combined into the same utility like they are with border widths. So the example above would be written like this:

...which is a lot more like how you'd write similar border width code.
You can also now have two sides with different border radiuses if you really desire:

This approach comes with the downside that the filesize is now a bit bigger because there are more utilities, but I think the added flexibility, increased consistency, and more obvious implementation is worth it.
Breaking Changes
This is a breaking change so it wouldn't land until 0.2.0.
Breaks include:

Border radius size utilities now no longer affect the radius of individually specified sides, ie:

...would have normal sized rounded top corners, not large.
Instead, you'd write that like this now:

The borderRadius section of the default config file has changed slighty, moving none to the top of the modifiers list so you can more easily use it to reset border radius at a breakpoint while still overriding one of those corners with another size. End users would need to update their config files to match this for their experience to match what's in the documentation.

Questions
I have two things I'm still considering that I'd be interested in input on:

Right now we target sides like top, left, bottom, or right. That's not really how it works in CSS; instead in CSS you target top-left, top-right, bottom-right, or bottom-left.
Our current utilities try to serve as a useful abstraction on top of this but it can make it really tricky to get things right when you're trying to round 3 corners or 1 corner.
For example, this is the only way to round just the bottom right corner:

That seems pretty lame to me vs. something like this:

In general I think rounding a pair of corners is probably still the most common use case though, so I'm inclined to keep it the way it is. I don't think I'd like to add all 4 sides and all 4 corners, because the CSS bloat would be significant.
Would the developer experience be significantly worse if you had to write this to make the top of an element rounded?

I feel like it's probably worse, but it's definitely the most powerful approach :/ Open to discussion on that.

I think I hate our default none modifier, and I think I'd like to change it to 0 by default, even though we use a named scale for the other sizes.
Is this scale weird, or is it fine?
{
    // ...
    borderRadius: {
        '0': '0',
        default: '.25rem',
        'sm': '.125rem',
        'lg': '.5rem',
        'full': '9999px',
    }
}

To Do Before Merging

[ ] Update rounded documentation

I think I'd actually prefer this:

Yes, it's longer than just using rounded-t, but I've always felt like reference to corners at "top" only was kinda weird.
As for the rounded-none vs rounded-0, I'm kinda indifferent. Does seems kinda weird to use "0" when the rest of the scale is named. What about rounded-square? :feelsgood: Just kidding. Hard problem. I almost want rounded-disabled or rounded-off.

I almost want rounded-disabled or rounded-off. Kinda like rounded-off actually.

I like the rounded-disabled better. The class rounded-off sounds like you are rounding something, which is the opposite of what the class is trying to invoke. Kinda like rounding-off numbers.
Anyways, I love the fact that you guys are discussing ideas here between each other, feels more open to the community :smile:

Part of me wants to rename this utility altogether to just radius-{modifier}, but it sort of kills the nice "no modifier" variant we use a lot now, since I think

 is a bit weird. Feels like there needs to be a value there.
But I do really like radius-0 or radius-none compared to rounded-0, rounded-none, rounded-disabled, etc.
If we did switch that name, I'm not sure what I'd want the default scale to be either.
radius-0
radius-sm
radius-md
radius-lg

Or:
// This one sort of sucks because right now we have a 0.125rem value for smallest
// radius, and that's not consistent with our numeric scale elsewhere (which is
// increments of .25rem)
radius-0
radius-1
radius-2
radius-4

...or who knows what else. Tough.

If I may provide an outside opinion for consideration, perhaps it helps when thinking about naming css classes (and perhaps not). :)
When naming classes, I think it is important to keep the naming to convey meaning and describe what the element looks like after it is applied. Focussing on the specific CSS property the rule pertains to seems to steer the "discussion" back to the technical side of things.
The class names become adjectives of the element they are applied to. This is in-line with most of the other naming conventions in Tailwind, like the colors, etc.
Because of that, I think rounded is still the better way to go.


Replace deprecated ffmpeg functions:

avpicture_get_size -> av_image_get_buffer_size
avpicture_fill -> av_image_fill_arrays
av_picture_copy -> av_image_copy
Add missing includes.
This fixes build with ffmpeg-6.x.x

@jpulz thank you for the pull request, just note that this channel is unmaintained and disabled by default.

@freerdp-bot test please

@freerdp-bot test again please

@freerdp-bot test again

Can this pool be merged with the stable-2.0?

Can this pool be merged with the stable-2.0?

A lot of deprecated stuff has now been removed from ffmpeg git. https://bugs.gentoo.org/926787
Please backport this to stable-2.0!
krdc 24.02 depends on that branch.

@jospezial
I try backport this to stable-2.0
https://github.com/eegorov/FreeRDP/tree/stable-2.0
net-misc/freerdp-2.9999 build fine on my gentoo


Update columnstore-indexes-overview.md

Synapse Analytics also has a tuple mover. Customers are confused. (Although the doc https://docs.microsoft.com/en-us/azure/synapse-analytics/sql-data-warehouse/sql-data-warehouse-tables-index explains "Closed groups are automatically converted to columnstore row groups by the background "tuple mover" process.")

@MemiyazaMiyazaki : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#label:"aq-pr-triaged"

@WilliamDAssafMSFT : Thanks for your contribution! The author(s) have been notified to review your proposed change.

Hi @MemiyazaMiyazaki! Thanks for taking the time to create this PR. I've added a complimentary commit to this PR to clarify. Our commits will both be merged and this article update is in flight. After the updated article is published, GitHub will list you as an article contributor.
Thanks again for this feedback, your suggestions help improve our documentation.
#sign-off

@WilliamDAssafMSFT: I'm sorry - only the author of this article, @MikeRayMSFT, can sign off on your changes. But we do have an exception process - if you are on the Microsoft content or product team for this product area, you can ask the PR review team to review and merge it by sending mail to the techdocprs alias.

Thanks @ktoliver #sign-off


Suggestion

Maintain separate folders for different languages.

A really good suggestion indeed as we can clearly see the data in folders is not really in a proper manner.

@adityabisoi Please do consider.

@stormfireuttam @srinath1412001 Chat in gitter.


Module somehow enables Star Wars FFG System to use StarJedi font, system uses it wrong

After enabling this addon, suddendly the "Mandar" style of the Star Wars FFG System will be able to use the StarJedi font, and incorrect use of the font causes some strange text-artifacts where letters are switched.
https://github.com/StarWarsFoundryVTT/StarWarsFFG/issues/900
Changing the mandar.css of the system like in the above issue fixes the problem.
Although I am still not sure why this addon triggered this. Perhaps worth a look.

As discussed on Discord, this isn't actually an issue with this module - rather, we provide the font that the Mandar theme was trying to use and the artifacting is a result of the way in which the theme is trying to use it.
That being said, since our module exposes it, I'll override the CSS applied by the theme until the next system update comes out and fixes it, at which point I'll stop overriding it.

Will be released in 0.1.8.


Certificate for the DNS may have expired

I and many of my team members are getting these errors when we try to build sites.

@wilso929 we are not sure why you are getting this issue.
I wanted to suggest that you run the nslookup CLI command (https://en.wikipedia.org/wiki/Nslookup) a couple of times, to see if it gives us useful information to troubleshoot what is going on
After you run these 3 separate commands on your terminal, then send me the outputs through Slack (that way you don't share you internal name server IPs).
nslookup traefik.me
nslookup islandora.traefik.me
nslookup islandora.ca
Good luck,
Yamil Suarez (that is my name on the Islandora Slack)

This ticket was reviewed during today's weekly Islandora tech meeting. It was mentioned that traefik recently updated their cert, so this issue may have been resolved?
Let us know either way, so we can close this ticket by next week.

@wilso929 I will close this ticket because I did not hear back from you.
If you are still having issues please reach out to us on Slack or open up the ticket again.

Closing ticket.


Add field set support to GAU Allocations

https://powerofus.force.com/0D58000002CGoZp

Just ran into this issue today. It would be a lovely feature.
Thanks!

Is this in progress? We may be able to pick it up...

It's not in progress, but I'm happy to collaborate if you're interested in
contributing!
On Thu, Oct 1, 2015 at 2:07 PM, Brian Pickett<EMAIL_ADDRESS>wrote:

Is this in progress? We may be able to pick it up...
—
Reply to this email directly or view it on GitHub
https://github.com/SalesforceFoundation/Cumulus/issues/1655#issuecomment-144850149
.

Ok, thanks. We're poking around in the code over the next two weeks and will share some thoughts/examples afterwards as a basis for a discussion.

Sounds great. You could also participate in the NPSP sprint, in person or
remotely, which starts three weeks from today,
and do the work then!
On Thu, Oct 1, 2015 at 2:30 PM, Brian Pickett<EMAIL_ADDRESS>wrote:

Ok, thanks. We're poking around in the code over the next two weeks and
will share some thoughts/examples afterwards as a basis for a discussion.
—
Reply to this email directly or view it on GitHub
https://github.com/SalesforceFoundation/Cumulus/issues/1655#issuecomment-144855852
.

Thank you, Brian! Looking forward to seeing what you come up with.
Sent from my iPhone
On Oct 1, 2015, at 5:30 PM, Brian Pickett<EMAIL_ADDRESS>wrote:
Ok, thanks. We're poking around in the code over the next two weeks and
will share some thoughts/examples afterwards as a basis for a discussion.
—
Reply to this email directly or view it on GitHub
https://github.com/SalesforceFoundation/Cumulus/issues/1655#issuecomment-144855852
.

**lurch: add

Tracking W-008314

Yes, also just ran into this, mentioned to @kbromer. To add a few more fields to the Manage Allocations layout we had to duplicate the page, controller, and test code (which obviously isn't great practice) -- along with a couple associated UTIL classes -- so we could add a few fields to the SOQL query and table layout. Would be great to be able to use a field set instead.

I took a look at this since it came back up on the Hub, and I did the field set support for the Payments Wizard a while back. This is trickier, because there's JS attached to events on the Amount and Percent fields. The simplest way to implement this, I think, would be to leave the 3 fields there (GAU, %age, Amount) hardcoded into the VF and then have the fieldset be just for additional fields that would display to the right of Percent. Does that seem like it would meet users' needs and NPSP standards?
Possible alternatives:

include these three fields in the field set but document that all three are required, and error on the page if one of them is missing. (I'm pretty sure, but not certain, that the isRequired property  in displayedFields in the object metadata doesn't actually prevent subscribers from removing the field from the fieldset. I think it just provides an attribute that can be queried for and used to mark a field as required in the UI.)
Similar to the above, but only require one of Amount or Percentage to be present.

Either of these would give subscribers maximum flexibility in ordering the fields.  LMK if I should take this back to the Idea to get some Hubbers' input.
FYI @coriobriensfdo @mpusto (sorry - don't see a way to tag Alison Meyer here!)

@tet3 sounds good. I prefer the latter options that give increased flexibility for field order, including the option to remove Amount or Pct if appropriate. In our experience the teams who are doing allocation data entry have been understandably particular about optimizing their workflow, given the scale of records they have to maintain.

@tet3 it certainly wouldn't hurt posting this in the Idea and getting additional feedback :)
Any chance you can make it to one of our upcoming Open Source Community Sprint's (Detroit in July or Philly in Oct)?

Hi everyone.  I know this has been an older post and ongoing but wanted to see if anyone figured anything out here.  We're trying to do something with Manage Allocations, add two fields to it and when you start recreating your own page you run into other dependencies.  Thank you for any insight anyone may have.

@stephaniepck we don't provide support here in GitHub, so my recommendation would be to post in the Power of Us Hub and ask for advice.

@stephaniepck We did the same thing. We've rebuilt the page by cloning code from this repo, then added-in support for a Field Set. It did take a bit of effort to get all the dependencies worked out, but in the end is working.
@coriobriensfdo Would love to talk about getting this included in the base package so that others don't need to go through this headache. Let me know if you're interested.

Work Item to resolve (community contribution)


Update on stable 0.15.x tried to upgrade to 0.16.0RC0?

Please verify that this bug has NOT been raised before.

[X] I checked and didn't find a similar issue

Describe the bug*
I'm running 0.15.6 and tried to upgrade now to 0.15.7 but 0.16.0 RC0 tried to install (and failed)
Steps to Reproduce
Running 0.15.6:
sudo apt update
sudo apt dist-upgrade
Expected behaviour
Should have upgraded to 0.15.7
Deployment Method

[ ] Docker
[X] Package
[X] Bare metal
[ ] Other - added info in Steps to Reproduce

Version Information
Version Information:
InvenTree-Version: 0.15.6
Django Version: 4.2.14
Database: mysql
Debug-Mode: False
Deployed using Docker: False
Platform: Linux-5.4.0-182-generic-x86_64-with-glibc2.31
Installer: None
Active plugins: [{'name': 'InvenTreeBarcode', 'slug': 'inventreebarcode', 'version': '2.0.0'}, {'name': 'InvenTreeCoreNotificationsPlugin', 'slug': 'inventreecorenotificationsplugin', 'version': '1.0.0'}, {'name': 'InvenTreeCurrencyExchange', 'slug': 'inventreecurrencyexchange', 'version': '1.0.0'}, {'name': 'InvenTreeLabel', 'slug': 'inventreelabel', 'version': '1.0.0'}, {'name': 'InvenTreeLabelMachine', 'slug': 'inventreelabelmachine', 'version': '1.0.0'}, {'name': 'InvenTreeLabelSheet', 'slug': 'inventreelabelsheet', 'version': '1.0.0'}, {'name': 'DigiKeyPlugin', 'slug': 'digikeyplugin', 'version': '1.0.0'}, {'name': 'LCSCPlugin', 'slug': 'lcscplugin', 'version': '1.0.0'}, {'name': 'MouserPlugin', 'slug': 'mouserplugin', 'version': '1.0.0'}, {'name': 'TMEPlugin', 'slug': 'tmeplugin', 'version': '1.0.0'}, {'name': 'KiCadLibraryPlugin', 'slug': 'kicad-library-plugin', 'version': '1.4.2'}]
Please verify if you can reproduce this bug on the demo site.

[ ] I can reproduce this bug on the demo site.

Relevant log output
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
Get more security updates through Ubuntu Pro with 'esm-apps' enabled:
  libpython3.9-minimal libpython3.9-stdlib libpython3.9 python3.9
  python3.9-dev python3.9-minimal libpython3.9-dev python3.9-venv
Learn more about Ubuntu Pro at https://ubuntu.com/pro
The following packages will be upgraded:
  inventree
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 73.0 MB of archives.
After this operation, 17.9 MB of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 https://dl.packager.io/srv/deb/inventree/InvenTree/stable/ubuntu 20.04/main amd64 inventree amd64 0.16.0-rc0-1722935028.6937b3a2.focal [73.0 MB]
Fetched 73.0 MB in 7s (10.6 MB/s)
(Reading database ... 125521 files and directories currently installed.)
Preparing to unpack .../inventree_0.16.0-rc0-1722935028.6937b3a2.focal_amd64.deb ...
# Clearing precompiled files
No idea what 'clear-generated' is!
dpkg: error processing archive /var/cache/apt/archives/inventree_0.16.0-rc0-1722935028.6937b3a2.focal_amd64.deb (--unpack):
 new inventree package pre-installation script subprocess returned error exit status 1
# Setting base environment variables
# Using existing config file: /etc/inventree/config.yaml

[notice] A new release of pip is available: 24.1.2 -> 24.2
[notice] To update, run: pip install --upgrade pip
# Collected environment variables:
#    INVENTREE_MEDIA_ROOT=/opt/inventree/data/media
#    INVENTREE_STATIC_ROOT=/opt/inventree/data/static
#    INVENTREE_BACKUP_DIR=/opt/inventree/data/backup
#    INVENTREE_PLUGINS_ENABLED=true
#    INVENTREE_PLUGIN_FILE=/etc/inventree/plugins.txt
#    INVENTREE_SECRET_KEY_FILE=/etc/inventree/secret_key.txt
#    INVENTREE_DB_ENGINE=mysql
#    INVENTREE_DB_NAME=inventree
#    INVENTREE_DB_USER=inventree
#    INVENTREE_DB_HOST=localhost
#    INVENTREE_DB_PORT=3306
# Getting the IP address of the server via web service
IP address is x.x.x.x
# Python environment already present
# Found earlier used version: /opt/inventree/env/bin/python
# Setting up python environment
Requirement already satisfied: invoke in ./env/lib/python3.9/site-packages (2.2.0)
Requirement already satisfied: wheel in ./env/lib/python3.9/site-packages (0.43.0)

[notice] A new release of pip is available: 24.1.2 -> 24.2
[notice] To update, run: pip install --upgrade pip
# Stopping nginx
# Setting up nginx to /etc/nginx/sites-enabled/inventree.conf
# Starting nginx
# (Re)creating init scripts
Nothing to do.
Nothing to do.
# Enabling InvenTree on boot
# Admin data already exists - skipping
# Stopping InvenTree
# Updating InvenTree
Requirement already satisfied: wheel in ./env/lib/python3.9/site-packages (0.43.0)

[notice] A new release of pip is available: 24.1.2 -> 24.2
[notice] To update, run: pip install --upgrade pip
# inv update| Installing required python packages from 'src/backend/requirements.txt'
# inv update| Requirement already satisfied: pip in ./env/lib/python3.9/site-packages (24.1.2)
# inv update| Collecting pip
# inv update|   Downloading pip-24.2-py3-none-any.whl.metadata (3.6 kB)
# inv update| Requirement already satisfied: setuptools in ./env/lib/python3.9/site-packages (69.5.1)
# inv update| Collecting setuptools
# inv update|   Downloading setuptools-72.1.0-py3-none-any.whl.metadata (6.6 kB)
# inv update| Downloading pip-24.2-py3-none-any.whl (1.8 MB)
# inv update|    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 1.8/1.8 MB 11.2 MB/s eta 0:00:00
# inv update| Downloading setuptools-72.1.0-py3-none-any.whl (2.3 MB)
# inv update|    ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 2.3/2.3 MB 11.8 MB/s eta 0:00:00
# inv update| Installing collected packages: setuptools, pip
# inv update|   Attempting uninstall: setuptools
# inv update|     Found existing installation: setuptools 69.5.1
# inv update|     Uninstalling setuptools-69.5.1:
# inv update|       Successfully uninstalled setuptools-69.5.1
# inv update|   Attempting uninstall: pip
# inv update|     Found existing installation: pip 24.1.2
# inv update|     Uninstalling pip-24.1.2:
# inv update|       Successfully uninstalled pip-24.1.2
# inv update| Successfully installed pip-24.2 setuptools-72.1.0
# inv update| Requirement already satisfied: asgiref==3.8.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 3)) (3.8.1)
# inv update| Requirement already satisfied: async-timeout==4.0.3 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 9)) (4.0.3)
# inv update| Requirement already satisfied: attrs==23.2.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 13)) (23.2.0)
# inv update| Requirement already satisfied: babel==2.15.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 19)) (2.15.0)
# inv update| Requirement already satisfied: bleach==6.1.0 in ./env/lib/python3.9/site-packages (from bleach[css]==6.1.0->-r src/backend/requirements.txt (line 23)) (6.1.0)
# inv update| Requirement already satisfied: brotli==1.1.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 27)) (1.1.0)
# inv update| Requirement already satisfied: certifi==2024.2.2 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 112)) (2024.2.2)
# inv update| Requirement already satisfied: cffi==1.16.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 118)) (1.16.0)
# inv update| Requirement already satisfied: charset-normalizer==3.3.2 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 174)) (3.3.2)
# inv update| Requirement already satisfied: coreapi==2.3.3 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 266)) (2.3.3)
# inv update| Requirement already satisfied: coreschema==0.0.4 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 269)) (0.0.4)
# inv update| Requirement already satisfied: cryptography==42.0.7 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 273)) (42.0.7)
# inv update| Requirement already satisfied: cssselect2==0.7.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 309)) (0.7.0)
# inv update| Requirement already satisfied: defusedxml==0.7.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 313)) (0.7.1)
# inv update| Requirement already satisfied: deprecated==1.2.14 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 319)) (1.2.14)
# inv update| Requirement already satisfied: diff-match-patch==20230430 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 326)) (20230430)
# inv update| Requirement already satisfied: dj-rest-auth==6.0.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 330)) (6.0.0)
# inv update| Requirement already satisfied: django==4.2.14 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 332)) (4.2.14)
# inv update| Requirement already satisfied: django-allauth==0.61.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 366)) (0.61.1)
# inv update| Requirement already satisfied: django-allauth-2fa==0.11.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 369)) (0.11.1)
# inv update| Requirement already satisfied: django-cleanup==8.1.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 372)) (8.1.0)
# inv update| Requirement already satisfied: django-cors-headers==4.3.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 375)) (4.3.1)
# inv update| Requirement already satisfied: django-crispy-forms==1.14.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 378)) (1.14.0)
# inv update| Requirement already satisfied: django-dbbackup==4.1.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 381)) (4.1.0)
# inv update| Requirement already satisfied: django-error-report-2==0.4.2 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 384)) (0.4.2)
# inv update| Requirement already satisfied: django-filter==24.2 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 387)) (24.2)
# inv update| Requirement already satisfied: django-flags==5.0.13 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 390)) (5.0.13)
# inv update| Requirement already satisfied: django-formtools==2.5.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 393)) (2.5.1)
# inv update| Requirement already satisfied: django-ical==1.9.2 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 396)) (1.9.2)
# inv update| Requirement already satisfied: django-import-export==3.3.7 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 399)) (3.3.7)
# inv update| Requirement already satisfied: django-js-asset==2.2.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 402)) (2.2.0)
# inv update| Requirement already satisfied: django-maintenance-mode==0.21.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 406)) (0.21.1)
# inv update| Requirement already satisfied: django-markdownify==0.9.3 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 409)) (0.9.3)
# inv update| Requirement already satisfied: django-money==3.2.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 412)) (3.2.0)
# inv update| Requirement already satisfied: django-mptt==0.16.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 415)) (0.16.0)
# inv update| Requirement already satisfied: django-otp==1.5.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 418)) (1.5.0)
# inv update| Requirement already satisfied: django-picklefield==3.2 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 422)) (3.2)
# inv update| Requirement already satisfied: django-q-sentry==0.1.6 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 426)) (0.1.6)
# inv update| Requirement already satisfied: django-q2==1.6.2 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 428)) (1.6.2)
# inv update| Requirement already satisfied: django-recurrence==1.11.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 431)) (1.11.1)
# inv update| Requirement already satisfied: django-redis==5.4.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 435)) (5.4.0)
# inv update| Requirement already satisfied: django-sesame==3.2.2 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 438)) (3.2.2)
# inv update| Requirement already satisfied: django-sql-utils==0.7.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 441)) (0.7.0)
# inv update| Requirement already satisfied: django-sslserver==0.22 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 444)) (0.22)
# inv update| Requirement already satisfied: django-stdimage==6.0.2 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 446)) (6.0.2)
# inv update| Requirement already satisfied: django-taggit==5.0.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 449)) (5.0.1)
# inv update| Requirement already satisfied: django-user-sessions==2.0.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 452)) (2.0.0)
# inv update| Requirement already satisfied: django-weasyprint==2.3.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 455)) (2.3.0)
# inv update| Requirement already satisfied: django-xforwardedfor-middleware==2.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 458)) (2.0)
# inv update| Requirement already satisfied: djangorestframework==3.14.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 460)) (3.14.0)
# inv update| Requirement already satisfied: djangorestframework-simplejwt==5.3.1 in ./env/lib/python3.9/site-packages (from djangorestframework-simplejwt[crypto]==5.3.1->-r src/backend/requirements.txt (line 467)) (5.3.1)
# inv update| Requirement already satisfied: drf-spectacular==0.27.2 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 470)) (0.27.2)
# inv update| Requirement already satisfied: dulwich==0.22.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 473)) (0.22.1)
# inv update| Requirement already satisfied: et-xmlfile==1.1.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 521)) (1.1.0)
# inv update| Requirement already satisfied: feedparser==6.0.11 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 525)) (6.0.11)
# inv update| Requirement already satisfied: fonttools==4.51.0 in ./env/lib/python3.9/site-packages (from fonttools[woff]==4.51.0->-r src/backend/requirements.txt (line 528)) (4.51.0)
# inv update| Requirement already satisfied: googleapis-common-protos==1.63.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 572)) (1.63.0)
# inv update| Requirement already satisfied: grpcio==1.63.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 578)) (1.63.0)
# inv update| Requirement already satisfied: gunicorn==22.0.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 626)) (22.0.0)
# inv update| Requirement already satisfied: html5lib==1.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 629)) (1.1)
# inv update| Requirement already satisfied: icalendar==5.0.12 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 633)) (5.0.12)
# inv update| Requirement already satisfied: idna==3.7 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 637)) (3.7)
# inv update| Requirement already satisfied: importlib-metadata==7.0.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 641)) (7.0.0)
# inv update| Requirement already satisfied: inflection==0.5.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 648)) (0.5.1)
# inv update| Requirement already satisfied: itypes==1.2.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 652)) (1.2.0)
# inv update| Requirement already satisfied: jinja2==3.1.4 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 656)) (3.1.4)
# inv update| Requirement already satisfied: jsonschema==4.22.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 660)) (4.22.0)
# inv update| Requirement already satisfied: jsonschema-specifications==2023.12.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 664)) (2023.12.1)
# inv update| Requirement already satisfied: markdown==3.6 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 668)) (3.6)
# inv update| Requirement already satisfied: markuppy==1.14 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 672)) (1.14)
# inv update| Requirement already satisfied: markupsafe==2.1.5 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 675)) (2.1.5)
# inv update| Requirement already satisfied: oauthlib==3.2.2 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 737)) (3.2.2)
# inv update| Requirement already satisfied: odfpy==1.4.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 741)) (1.4.1)
# inv update| Requirement already satisfied: openpyxl==3.1.2 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 744)) (3.1.2)
# inv update| Requirement already satisfied: opentelemetry-api==1.24.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 748)) (1.24.0)
# inv update| Requirement already satisfied: opentelemetry-exporter-otlp==1.24.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 760)) (1.24.0)
# inv update| Requirement already satisfied: opentelemetry-exporter-otlp-proto-common==1.24.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 763)) (1.24.0)
# inv update| Requirement already satisfied: opentelemetry-exporter-otlp-proto-grpc==1.24.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 769)) (1.24.0)
# inv update| Requirement already satisfied: opentelemetry-exporter-otlp-proto-http==1.24.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 773)) (1.24.0)
# inv update| Requirement already satisfied: opentelemetry-instrumentation==0.45b0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 777)) (0.45b0)
# inv update| Requirement already satisfied: opentelemetry-instrumentation-django==0.45b0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 785)) (0.45b0)
# inv update| Requirement already satisfied: opentelemetry-instrumentation-redis==0.45b0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 788)) (0.45b0)
# inv update| Requirement already satisfied: opentelemetry-instrumentation-requests==0.45b0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 791)) (0.45b0)
# inv update| Requirement already satisfied: opentelemetry-instrumentation-wsgi==0.45b0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 794)) (0.45b0)
# inv update| Requirement already satisfied: opentelemetry-proto==1.24.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 798)) (1.24.0)
# inv update| Requirement already satisfied: opentelemetry-sdk==1.24.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 805)) (1.24.0)
# inv update| Requirement already satisfied: opentelemetry-semantic-conventions==0.45b0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 811)) (0.45b0)
# inv update| Requirement already satisfied: opentelemetry-util-http==0.45b0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 820)) (0.45b0)
# inv update| Requirement already satisfied: packaging==24.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 827)) (24.0)
# inv update| Requirement already satisfied: pdf2image==1.17.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 831)) (1.17.0)
# inv update| Requirement already satisfied: pillow==10.3.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 834)) (10.3.0)
# inv update| Requirement already satisfied: pint==0.21 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 910)) (0.21)
# inv update| Requirement already satisfied: pip-licenses==4.4.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 913)) (4.4.0)
# inv update| Requirement already satisfied: prettytable==3.10.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 916)) (3.10.0)
# inv update| Requirement already satisfied: protobuf==4.25.3 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 920)) (4.25.3)
# inv update| Requirement already satisfied: py-moneyed==3.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 935)) (3.0)
# inv update| Requirement already satisfied: pycparser==2.22 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 939)) (2.22)
# inv update| Requirement already satisfied: pydyf==0.10.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 943)) (0.10.0)
# inv update| Requirement already satisfied: pyjwt==2.8.0 in ./env/lib/python3.9/site-packages (from pyjwt[crypto]==2.8.0->-r src/backend/requirements.txt (line 947)) (2.8.0)
# inv update| Requirement already satisfied: pyphen==0.15.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 953)) (0.15.0)
# inv update| Requirement already satisfied: pypng==0.20220715.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 957)) (0.20220715.0)
# inv update| Requirement already satisfied: python-barcode==0.15.1 in ./env/lib/python3.9/site-packages (from python-barcode[images]==0.15.1->-r src/backend/requirements.txt (line 961)) (0.15.1)
# inv update| Requirement already satisfied: python-dateutil==2.9.0.post0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 964)) (2.9.0.post0)
# inv update| Requirement already satisfied: python-dotenv==1.0.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 970)) (1.0.1)
# inv update| Requirement already satisfied: python-fsutil==0.14.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 973)) (0.14.1)
# inv update| Requirement already satisfied: python3-openid==3.2.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 977)) (3.2.0)
# inv update| Requirement already satisfied: pytz==2024.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 981)) (2024.1)
# inv update| Requirement already satisfied: pyyaml==6.0.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 988)) (6.0.1)
# inv update| Requirement already satisfied: qrcode==7.4.2 in ./env/lib/python3.9/site-packages (from qrcode[pil]==7.4.2->-r src/backend/requirements.txt (line 1043)) (7.4.2)
# inv update| Requirement already satisfied: rapidfuzz==3.9.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1047)) (3.9.0)
# inv update| Requirement already satisfied: redis==5.0.4 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1138)) (5.0.4)
# inv update| Requirement already satisfied: referencing==0.35.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1142)) (0.35.1)
# inv update| Requirement already satisfied: regex==2024.4.28 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1148)) (2024.4.28)
# inv update| Requirement already satisfied: requests==2.31.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1228)) (2.31.0)
# inv update| Requirement already satisfied: requests-oauthlib==2.0.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1236)) (2.0.0)
# inv update| Requirement already satisfied: rpds-py==0.  Running command git clone --filter=blob:none --quiet https://github.com/afkiwers/inventree_kicad /tmp/pip-install-x2_il51b/inventree-kicad-plugin_3f90d549edce4889b4477d1343e17fc5
18.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1240)) (0.18.1)
# inv update| Requirement already satisfied: sentry-sdk==2.1.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1343)) (2.1.1)
# inv update| Collecting setuptools==69.5.1 (from -r src/backend/requirements.txt (line 1347))
# inv update|   Downloading setuptools-69.5.1-py3-none-any.whl (894 kB)
# inv update|      ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 894.6/894.6 kB 12.1 MB/s eta 0:00:00
# inv update| Requirement already satisfied: sgmllib3k==1.0.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1353)) (1.0.0)
# inv update| Requirement already satisfied: six==1.16.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1356)) (1.16.0)
# inv update| Requirement already satisfied: sqlparse==0.5.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1363)) (0.5.0)
# inv update| Requirement already satisfied: tablib==3.5.0 in ./env/lib/python3.9/site-packages (from tablib[html,ods,xls,xlsx,yaml]==3.5.0->-r src/backend/requirements.txt (line 1369)) (3.5.0)
# inv update| Requirement already satisfied: tinycss2==1.2.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1373)) (1.2.1)
# inv update| Requirement already satisfied: typing-extensions==4.11.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1380)) (4.11.0)
# inv update| Requirement already satisfied: uritemplate==4.1.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1389)) (4.1.1)
# inv update| Requirement already satisfied: urllib3==2.2.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1395)) (2.2.1)
# inv update| Requirement already satisfied: wcwidth==0.2.13 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1402)) (0.2.13)
# inv update| Requirement already satisfied: weasyprint==61.2 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1406)) (61.2)
# inv update| Requirement already satisfied: webencodings==0.5.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1410)) (0.5.1)
# inv update| Requirement already satisfied: whitenoise==6.6.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1418)) (6.6.0)
# inv update| Requirement already satisfied: wrapt==1.16.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1421)) (1.16.0)
# inv update| Requirement already satisfied: xlrd==2.0.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1496)) (2.0.1)
# inv update| Requirement already satisfied: xlwt==1.3.0 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1500)) (1.3.0)
# inv update| Requirement already satisfied: zipp==3.18.1 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1504)) (3.18.1)
# inv update| Requirement already satisfied: zopfli==0.2.3 in ./env/lib/python3.9/site-packages (from -r src/backend/requirements.txt (line 1508)) (0.2.3)
# inv update| Installing collected packages: setuptools
# inv update|   Attempting uninstall: setuptools
# inv update|     Found existing installation: setuptools 72.1.0
# inv update|     Uninstalling setuptools-72.1.0:
# inv update|       Successfully uninstalled setuptools-72.1.0
# inv update| Successfully installed setuptools-69.5.1
# inv update| Installing plugin packages from '/etc/inventree/plugins.txt'
# inv update| Collecting inventree-kicad-plugin@ git+https://github.com/afkiwers/inventree_kicad (from -r /etc/inventree/plugins.txt (line 3))
# inv update|   Cloning https://github.com/afkiwers/inventree_kicad to /tmp/pip-install-x2_il51b/inventree-kicad-plugin_3f90d549edce4889b4477d1343e17fc5
# inv update|   Resolved https://github.com/afkiwers/inventree_kicad to commi/opt/inventree/env/lib/python3.9/site-packages/allauth/exceptions.py:9: UserWarning: allauth.exceptions is deprecated, use allauth.core.exceptions
  warnings.warn("allauth.exceptions is deprecated, use allauth.core.exceptions")
Backing Up Database: inventree
 mysqldump inventree --quick --host=localhost --port=3306 --user=inventree --password='45ErW!rtyU55'
Backup size: 1.1 MiB
Writing file to default-inventree-server-2024-08-06-101205.dump.gz
/opt/inventree/env/lib/python3.9/site-packages/allauth/exceptions.py:9: UserWarning: allauth.exceptions is deprecated, use allauth.core.exceptions
  warnings.warn("allauth.exceptions is deprecated, use allauth.core.exceptions")
Backup size: 111.8 MiB
Writing file to inventree-server-2024-08-06-101210.tar.gz
/opt/inventree/env/lib/python3.9/site-packages/allauth/exceptions.py:9: UserWarning: allauth.exceptions is deprecated, use allauth.core.exceptions
  warnings.warn("allauth.exceptions is deprecated, use allauth.core.exceptions")
/opt/inventree/env/lib/python3.9/site-packages/allauth/exceptions.py:9: UserWarning: allauth.exceptions is deprecated, use allauth.core.exceptions
  warnings.warn("allauth.exceptions is deprecated, use allauth.core.exceptions")
System check identified some issues:

WARNINGS:
account.EmailAddress: (models.W036) MySQL does not support unique constraints with conditions.
	HINT: A constraint won't be created. Silence this warning if you don't care about it.
fatal: not a git repository (or any of the parent directories): .git
/opt/inventree/env/lib/python3.9/site-packages/allauth/exceptions.py:9: UserWarning: allauth.exceptions is deprecated, use allauth.core.exceptions
  warnings.warn("allauth.exceptions is deprecated, use allauth.core.exceptions")
/opt/inventree/env/lib/python3.9/site-packages/allauth/exceptions.py:9: UserWarning: allauth.exceptions is deprecated, use allauth.core.exceptions
  warnings.warn("allauth.exceptions is deprecated, use allauth.core.exceptions")
/opt/inventree/env/lib/python3.9/site-packages/allauth/exceptions.py:9: UserWarning: allauth.exceptions is deprecated, use allauth.core.exceptions
  warnings.warn("allauth.exceptions is deprecated, use allauth.core.exceptions")
t c99613592b9cf7265a8e20b5edcc1d83ba0c1c6e
# inv update|   Preparing metadata (setup.py): started
# inv update|   Preparing metadata (setup.py): finished with status 'done'
# inv update| Backing up InvenTree database...
# inv update| Python version 3.9.5 - /opt/inventree/env/bin/python3
# inv update| Backing up InvenTree media files...
# inv update| Python version 3.9.5 - /opt/inventree/env/bin/python3
# inv update| Running InvenTree database migrations...
# inv update| ========================================
# inv update| Python version 3.9.5 - /opt/inventree/env/bin/python3
# inv update| No changes detected
# inv update| Python version 3.9.5 - /opt/inventree/env/bin/python3
# inv update| /opt/inventree/env/lib/python3.9/site-packages/allauth/exceptions.py:9: UserWarning: allauth.exceptions is deprecated, use allauth.core.exceptions
# inv update|   warnings.warn("allauth.exceptions is deprecated, use allauth.core.exceptions")
# inv update| Python version 3.9.5 - /opt/inventree/env/bin/python3
# inv update| Operations to perform:
# inv update|   Synchronize unmigrated apps: allauth, allauth_2fa, corsheaders, crispy_forms, dbbackup, dj_rest_auth, django_cleanup, django_filters, django_ical, django_otp, djmoney, drf_spectacular, formtools, generic, import_export, maintenance_mode, m
arkdownify, messages, mptt, registration, rest_framework, runserver_nostatic, staticfiles, web
# inv update|   Apply all migrations: InvenTree, account, admin, auth, build, common, company, contenttypes, django_q, error_report, exchange, flags, inventree_kicad, label, machine, order, otp_static, otp_totp, part, plugin, report, socialaccount, stock,
 taggit, user_sessions, users
# inv update| Synchronizing apps without migrations:
# inv update|   Creating tables...
# inv update|     Running deferred SQL...
# inv update| Running migrations:
# inv update|   No migrations to apply.
# inv update| ========================================
# inv update| InvenTree database migrations completed!
# inv update| Updating frontend...
# inv update| Downloading frontend...
# inv update| [ERROR] Cannot get current ref via 'git rev-parse HEAD'
# inv update| Python version 3.9.5 - /opt/inventree/env/bin/python3
# inv update| Rendered all files in /opt/inventree/src/backend/InvenTree/templates/js/translated
# inv update| Collecting static files...
# inv update| Python version 3.9.5 - /opt/inventree/env/bin/python3
# inv update| Python version 3.9.5 - /opt/inventree/env/bin/python3
# inv update| Python version 3.9.5 - /opt/inventree/env/bin/python3
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/pl/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/id/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/vi/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/en/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/ja/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/zh_Hans/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/da/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/es_MX/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/bg/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/fr/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/es/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/nl/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/fa/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/sl/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/zh/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/el/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/zh_hant/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/fi/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/he/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/pt_br/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/tr/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/lv/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/sr/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/sk/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/hu/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/cs/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/pt/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/uk/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/it/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/hi/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/de/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/sv/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/ru/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/no/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/th/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| File “/opt/inventree/src/backend/InvenTree/locale/ko/LC_MESSAGES/django.po” is already compiled and up to date.
# inv update| InvenTree translation coverage: 19%
# Set permissions for data dir and media: /opt/inventree/data
# Starting InvenTree
####################################################################################
This InvenTree install uses nginx, the settings for the webserver can be found in
/etc/nginx/sites-enabled/inventree.conf
Try opening InvenTree with either
http://localhost/ or http://<IP_ADDRESS>/

Admin user data:
   Email:
   Username:
   Password:
####################################################################################
Errors were encountered while processing:
 /var/cache/apt/archives/inventree_0.16.0-rc0-1722935028.6937b3a2.focal_amd64.deb
E: Sub-process /usr/bin/dpkg returned an error code (1)

Tried another test upgrade after 0.15.8 release and it's still stuck trying to upgrade to 0.16.x
greg@inventree-server:~$ sudo apt dist-upgrade --dry-run
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
Get more security updates through Ubuntu Pro with 'esm-apps' enabled:
  libpython3.9-minimal libpython3.9-stdlib libpython3.9 python3.9
  python3.9-dev python3.9-minimal libpython3.9-dev python3.9-venv
Learn more about Ubuntu Pro at https://ubuntu.com/pro
The following packages will be upgraded:
  inventree
Inst inventree [0.15.6-1721711075.23a9485e.focal] (0.16.0-rc0-1722955471.6937b3a2.focal Ubuntu 20.04 packages for inventree/InvenTree:dl.packager.io [amd64])

@matmair any thoughts here? Is the installer building correctly at the moment?

I installed using the script in a debian VM and it installed 0.16.0 dev and I'm 99% I had manually changed the INVENTREE_TAG to stable because it installed using the latest tag.

I see two stable versions on the packager that 0.15.7, 0.16.0. while using installer script, default selection is 0.16.0 version and it does not install correctly.

@SchrodingersGat
greg@inventree-server:~$ apt policy inventree
inventree:
  Installed: 0.15.6-1721711075.23a9485e.focal
  Candidate: 0.16.0-rc0-1722955471.6937b3a2.focal
  Version table:
     0.16.0-rc0-1722955471.6937b3a2.focal 500
        500 https://dl.packager.io/srv/deb/inventree/InvenTree/stable/ubuntu 20.04/main amd64 Packages
     0.16.0-rc0-1722935028.6937b3a2.focal 500
        500 https://dl.packager.io/srv/deb/inventree/InvenTree/stable/ubuntu 20.04/main amd64 Packages
     0.15.7-1723011304.0d8eb2e0.focal 500
        500 https://dl.packager.io/srv/deb/inventree/InvenTree/stable/ubuntu 20.04/main amd64 Packages
     0.15.7-1722165410.0d8eb2e0.focal 500
        500 https://dl.packager.io/srv/deb/inventree/InvenTree/stable/ubuntu 20.04/main amd64 Packages

0.16.0-rc0 sitting under stable.

Thanks!
@matmair should we yank the build from packager.io? Or is there a better way to handle this

Hi , im using packager.io prepared builds adn ia have same issue.  As @MyRetroStore said : look slike 0.16.RC1 sitting as stable .
It is possible to update to last  stable version ( at this time 0.15.7 )    before  0.16.RC1.
I did it  in my case 0.15.4 ->0.15.7  just via apt upgrade command:
stockadmin@simstock:~$ sudo apt upgrade inventree=0.15.7-1723011304.0d8eb2e0.bullseye

``` I did it  and update 0.15.4 ->0.15.7  OK

Thanks, I was also able to upgrade by forcing the version number
sudo apt upgrade inventree=0.15.7-1723011304.0d8eb2e0.focal
2 wees ago 0.15.8 was released but is still not available on the packager.io


Pre-Training

Hello, I would like to know if it is possible to first train the networks (before learning with on-policy or off-policy methods) in some dataset of experience. I know that BCAgents allow one to load a supervised dataset (state,actions), but it is only for then. I would like to know if there is some way to train the networks before any method.

Hi Ivan,
In the learning_tutorials branch, we have two tutorials (1, 2) showcasing how to train a policy based on an existing dataset. These tutorials are very basic, but they convey the general idea of how this can be achieved. Is this what you were looking for?

Closing due to lack of activity.


feat: Migrate service to V2

closes  #48
Signed-off-by: Marc-philippe Fuller<EMAIL_ADDRESS>

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/device-rfid-llrp-go/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[x] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I am not introducing a new dependency (add notes below if you are)
[x] I have added unit tests for the new feature or bug fix (if not, why?)
[ ] I have fully tested (add details below) this the new feature or bug fix (if not, why?) minimal startup testing, full validation tbd
[ ] I have opened a PR for the related docs change (if not, why?) N/A for migration changes
Readme is updated

Testing Instructions

Run service to the point where it is waiting for devices to be added
New Dependency Instructions (If applicable)
N/A

@marcpfuller thanks for the changes, but you changed more than I suggested which has introduced new issues. Please see my inline comment: https://github.com/edgexfoundry/device-rfid-llrp-go/pull/52#discussion_r745380410

@farshidtz could you take a look at the snap. It looks to be failing. I am not sure what to do fix this

recheck

@farshidtz could you take a look at the snap. It looks to be failing. I am not sure what to do fix this

I had already explained why it's failing in my comment above.
Please merge this to fix it: https://github.com/marcpfuller/device-rfid-llrp-go/pull/1

Codecov Report

Merging #52 (2f01496) into main (73c0aef) will increase coverage by 0.12%.
The diff coverage is 16.21%.

@@            Coverage Diff             @@
##             main      #52      +/-   ##
==========================================
+ Coverage   40.99%   41.12%   +0.12%
==========================================
  Files          21       21
  Lines        9081     9019      -62
==========================================
- Hits         3723     3709      -14
+ Misses       4184     4141      -43
+ Partials     1174     1169       -5

Impacted Files
Coverage Δ

internal/driver/device.go
6.80% <0.00%> (-0.12%)
:arrow_down:

internal/driver/discover.go
65.61% <0.00%> (ø)

internal/driver/logging.go
60.86% <ø> (ø)

internal/driver/service.go
0.00% <ø> (ø)

internal/driver/driver.go
25.11% <10.90%> (+1.29%)
:arrow_up:

internal/driver/config.go
100.00% <100.00%> (+45.45%)
:arrow_up:

internal/llrp/reader.go
41.24% <0.00%> (+0.66%)
:arrow_up:

internal/retry/retry.go
93.12% <0.00%> (+1.52%)
:arrow_up:

Continue to review full report at Codecov.

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

However, I was not able to add a device, even though the device discovery found it.

@siggiskulason , this is awesome feedback. I didn't realize you have a Speedway RFID reader. I was worried about this cache issue once the discovery was triggered. The SDK cache issue was fix for profiles.... :-(

However, I was not able to add a device, even though the device discovery found it.

@siggiskulason, hey we were missing the provision watchers in the snap and I have updated the snap for this. Please test again

However, I was not able to add a device, even though the device discovery found it.

@siggiskulason, hey we were missing the provision watchers in the snap and I have updated the snap for this. Please test again

Yes, missing or invalid provision watchers will have the effect @siggiskulason has observed. This is one of the current shortcomings of the provision watcher approach. Because we are unable to get any feedback on if they worked or not, we just have to assume the device was added.

If it helps, you can skip the snap-related fixes and we'll address them once this PR is merged.

If it helps, you can skip the snap-related fixes and we'll address them once this PR is merged.

@farshidtz , Yes that is what we are planning. THX!

llrp.impinj.profile.yaml needs the following things set to RW:
  -
    name: config
    isHidden: false
    readWrite: "RW"
    resourceOperations:
      - { deviceResource: "ReaderConfig" }

  -
    name: "ReaderConfig"
    description: "A Reader's configuration"
    properties:
      valueType: "String"
      readWrite: "RW"

General comment, please avoid force-pushing  while still in review unless there is a good reason.

I have not reviewed the snap folder this iteration.

@ajcasagrande , please do not spend time on the snap folder. Canonical team now owns these for all Edgex Services and plans a rework once we complete the migration.