Commit title does not update when switching base branch

Repro:

Make a branch on vscode-docs forked from vnext
Make a commit with a description
Push
Create a new PR
Change base branch from main to vnext, 🐛 The description is valid but the title remains incorrect and should be updated to the single commit message

Change base branch from main to vnext

It should already be set to vnext if you created the branch from vnext with GHPRI installed for the last couple months.
What title did you actually see?

@alexr00 does the branch need to be checked out via the git or ghrpi extension? I think I used the terminal.

Terminal should be fine (I almost always use the terminal). If you remember the name of your branch and haven't deleted it locally, can you checkout the ./.git/config file and share the entry for your branch?

Was trying to repro this but it's stuck on loading:

GHPR trace log:
2023-09-21 06:12:02.821 [info] Review> Queuing additional validate state
2023-09-21 06:12:02.821 [debug] GitHubRepository> Fetch metadata - enter
2023-09-21 06:12:02.821 [debug] RateLimit> Extension rate limit remaining: 138, /repos/{owner}/{repo}
2023-09-21 06:12:18.939 [info] Review> Queuing additional validate state
2023-09-21 06:12:25.878 [info] Review> Queuing additional validate state
2023-09-21 06:12:37.589 [info] Review> Queuing additional validate state
2023-09-21 06:12:44.197 [info] Review> Queuing additional validate state
2023-09-21 06:12:57.210 [debug] GitHubRepository> Fetch metadata - enter
2023-09-21 06:12:57.210 [debug] RateLimit> Extension rate limit remaining: 137, /repos/{owner}/{repo}
2023-09-21 06:13:12.618 [warning] C:\Users\Daniel\.ssh\config: ENOENT: no such file or directory, open 'C:\Users\Daniel\.ssh\config'
2023-09-21 06:13:12.642 [debug] Activation> Creating API implementation.
2023-09-21 06:13:12.643 [debug] Activation> Initializing state.
2023-09-21 06:13:12.643 [debug] Activation> Creating credential store.
2023-09-21 06:13:12.647 [debug] Authentication> Initializing GitHub authentication provider.
2023-09-21 06:13:12.701 [debug] RateLimit> Extension rate limit remaining: 140, /user
2023-09-21 06:13:12.779 [debug] Activation> Registering built in git provider.
2023-09-21 06:13:12.779 [debug] Activation> Registering live share git provider.
2023-09-21 06:13:12.779 [debug] Activation> Creating tree view.
2023-09-21 06:13:12.779 [info] Looking for git repository
2023-09-21 06:13:12.779 [info] Found 0 repositories during activation
2023-09-21 06:13:12.779 [info] Git repository found, initializing review manager and pr tree view.
2023-09-21 06:13:12.822 [debug] GitPostCommitCommands> Trying to register post commit commands.
2023-09-21 06:13:13.142 [info] Registering git provider
2023-09-21 06:13:14.054 [info] Repository file:///c%3A/Github/microsoft/vscode-docs has been opened
2023-09-21 06:13:14.281 [info] Review> Validate state in progress
2023-09-21 06:13:14.281 [info] Review> Validating state...
2023-09-21 06:13:14.281 [info] Cannot updates repositories as git is uninitialized
2023-09-21 06:13:14.281 [info] Repo state for file:///c%3A/Github/microsoft/vscode-docs changed.
2023-09-21 06:13:14.281 [info] Repo file:///c%3A/Github/microsoft/vscode-docs has already been setup.
2023-09-21 06:13:14.500 [info] Review> No matching pull request metadata found locally for current branch tyriar/test_branch
2023-09-21 06:13:14.500 [info] Review> no matching pull request metadata found for current branch tyriar/test_branch
2023-09-21 06:13:14.501 [info] Review> No matching pull request metadata found on GitHub for current branch tyriar/test_branch
2023-09-21 06:13:14.928 [info] Git initialization state changed: state=initialized
2023-09-21 06:13:14.928 [info] Review> Validate state in progress
2023-09-21 06:13:14.928 [info] Review> Validating state...
2023-09-21 06:13:14.936 [debug] FolderRepositoryManager> Not all remotes found. The following remotes are missing: ups, upstream
2023-09-21 06:13:14.936 [debug] FolderRepositoryManager> Displaying configured remotes: origin, ups, upstream
2023-09-21 06:13:14.938 [info] Found GitHub remote for folder c:\Github\microsoft\vscode-docs
2023-09-21 06:13:14.939 [debug] GitHubRepository> Fetch metadata - enter
2023-09-21 06:13:14.939 [debug] RateLimit> Extension rate limit remaining: 139, /repos/{owner}/{repo}

Restart + update fixed it, maybe backwards compat broke in the latest ext version or something?

It's not set to vnext automatically:

Proof I was on vnext just before this:

@Tyriar did you have VS Code open when you created the new branch? The way we figure out the base branch is by just watching when you change branches and saving that in you ./.git/config file.


Make thema CLI dynamically support github.com/grafana/thema imports

Currently, running thema outside of either the thema repo itself, or outside of a cue.mod module context that does not have the github.com/grafana/thema codebase within its cue.mod/pkg dir, will result in
Error: import failed: cannot find package "github.com/grafana/thema"

This is clearly a big problem, as it means the thema CLI only works when the user has already set up their fs "correctly"...in a way that is difficult to even explain how to do correctly.

#79 was a dupe of this, but this is now fixed! 🎉


Port Whitebox Watershed.java?

I'm interested in having access to the watershed tool from Whitebox GAT. The algorithm doesn't look too complilcated, but I have not written Go before. I wouldn't mind taking the time to learn, but may need some pointers.
Would a port be possible? Are there any obvious hurdles?

While I do not currently have any plans to add the Watershed tool to GoSpatial, I am currently re-writing all of Whitebox GAT's tools in Rust. In this way, people will be able to access the tools from outside of the Whitebox GAT user interface. In fact, while this is a long-term project, I have already ported the Watershed tool over (see WhiteboxTools. If this is your primary interest in porting the tool over to GoSpatial, I suggest that you take a look at WhiteboxTools instead.


Support

Hi,
This looks like a great project, thanks! - is it still being supported?
I downloaded the zip file, changed the config.php values (I'm on an XAMPP setup), however I am seeing the following error messages;
Notice: Undefined variable: host in C:\xampp\htdocs\helpdesk2\init.php on line 8

Notice: Undefined variable: port in C:\xampp\htdocs\helpdesk2\init.php on line 9

Notice: Undefined variable: username in C:\xampp\htdocs\helpdesk2\init.php on line 10

Notice: Undefined variable: password in C:\xampp\htdocs\helpdesk2\init.php on line 11

It also seems that the css styling is missing.
My config.php contains the following as my URL;
$website_url = "localhost/helpdesk2/";
How do install the database tables and data, is this supposed to be automatic?

Make sure you used write information and also you enable write permission for files and directory while installing the scripts. I just tried in my side(xaamp) and its working as expected.
I will be happy, if you can let me know about the css. Or may be you can contribute. :)
Thanks


Cannot Detect Device Change

The claimed feature is not working.

If an endpoint device is connected or disconnected to PC, liter should detect the change and allow manipulating the new default endpoint device.

Fixed by 8685e5241b82282da32087f5436b15024a1621d2.


Docs: Change Member Table to MudToggleGroup

Description
This update makes minor changes suggested in #10145 where the API Docs ApiMemberTable should use a MudToggleGroup to control the grouping of members.  This also slightly adjusts the appearance of the table in md, sm, and xs breakpoints for mobile devices.
Breakpoint: md

Breakpoint: sm

Breakpoint: xs

How Has This Been Tested?
This was tested visually by using F12 Developer Tools to view the site in Responsive mode as well as for mobile devices.
Type of Changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[X] Documentation (fix or improvement to the website or code docs)

Checklist

[X] The PR is submitted to the correct branch (dev).
[X] My code follows the code style of this project.
[ ] I've added relevant tests.

I think you're being constrained by the MudGrid. If you did the layout purely in CSS it would be more fluid. If you want I can make that change in a new PR or edit this one, or if you prefer how it is now that's fine too.

Thanks, Daniel!  Admittedly, I don't know how to do this cleanly in pure CSS, so you're welcome to show me how it's done!

Made some changes, let me know what you think. Happy to keep working with you on it!

Made some changes, let me know what you think. Happy to keep working with you on it!

Thanks, man!  I'll take a look tomorrow (Sunday), and I'm happy to fix up the tests.

Made some changes, let me know what you think. Happy to keep working with you on it!

Looks beautiful to me, on all devices!   I made a small whitespace commit to get tests working.

Looks beautiful to me, on all devices! I made a small whitespace commit to get tests working.

Can we see the new screen-shoots?

Can we see the new screen-shoots?

You bet; I updated the PR description with Daniel's changes in md/sm/xs modes.

You bet; I updated the PR description with Daniel's changes in md/sm/xs modes.

Thanks, it looks really good, got my insta approval

Thanks @jperson2000


AWS Docker Image Pulling: avoid using public internet

AWS Docker Image Pulling costs are very high because we go outside the internal network and it costs a lot. We should stay within private internet while docker image pulling.
:warning: we need to have an opportunity to push images to registry from the outside (registry-syncer)

To the best of our knowledge this was fixed with the S3 VPC Endpoint, but this needs to be validated

I have checked all non-nih deployments and it indeed looks like the cost for "NAT gateway Bytes" are drastically reduced, to a very tolerable average of 5$ per day

re-opening, not sure if fixed on nih-prod and nih-stag


A link in the checkbox label can't be clicked

The link is clickable with the default theme (Lumo)

I don’t really understand what the difference is here between Lumo and Material. Tried debugging, but can’t figure it out (I even removed the pointer-events: none; from the theme).

Seems to work for me after removing pointer-events: none; from the [part="label"]

Okay, good. I messed something up then.
There’s a comment in Lumo about the active style not working in IE11 without that, though. Need to check if that’s still the case.


[INFO] eforsyning.dk SSL certificate expired (external problem)

Describe the bug
I'm creating this issue, so you won't get multiple bug reports for an external error. The SSL certificate has expired on https://eforsyning.dk/. Which causes this integration to fail (as it should).

Is there anything we can do about it?

Is there anything we can do about it?

They (www.dff-edb.dk) will probably see it tomorrow. The SSL certificate expired the 30th. So it happened on a day off (weekend).

Thanks for the info, much appreciated.


Longer inter-character timeout for connect

GPRS::connect() often failed for me. I found that the SIM900 responds to the AT+CIPSTART command immediately with OK, but then takes a couple of seconds to follow up with CONNECT OK. This delay was more than the default inter-character timeout, so sim900_read_buffer() would return before it read the CONNECT OK, and GPRS::connect() would return false.
Making the inter-character timeout the same as the other timeout parameter fixes this for me.

Hi,
Thanks a lot for your contribution, but it's better to do it more open for everybody, so we prefer to make the connect function declaration better.
What do you think about:
bool connect(Protocol ptl, const char * host, int port, int timeout = 2 * DEFAULT_TIMEOUT, int chartimeout = 2 * DEFAULT_INTERCHAR_TIMEOUT);
bool connect(Protocol ptl, const __FlashStringHelper *host, const __FlashStringHelper *port, int timeout = 2 * DEFAULT_TIMEOUT, int chartimeout = 2 * DEFAULT_INTERCHAR_TIMEOUT);
And then, change all sim900_read_buffer() calls inside CONNECT functions with "chartimeout" function.
In your sketch you will call like: sim900.connect( XXX, XXX, XXX, 5, 5) or whatever you like.
We prefer that, than putting inside the function this kind of call: "timeout * 1000"
What do you think ?
Best regards

Yes - that makes complete sense - I'll refactor my code as you suggest, test it, and commit the changes if all is good.

@juan3211 Reworked my code as you suggested. Works great for me - in fact, even just using the default value you suggested for chartimeout (doubling the previous value) works much better.

Thanks. Merged :)

Awesome - thanks!


Dynamic neo4j queries

Hi,
Is it possible to create and run dynamic queries in neo4j using EntityManager or some other combination provided by Spring data?

Hey @sanyalpp
In the case of these kinds of technical, code-focused and very specific questions, we need to go through StackOverflow.
They have very clear (and strict) guidelines on everything from how to structure the question, how much (or little) detail to provide, how to structure code, etc.
And these help with how easy it is for me (and anyone else) to go through that and actually help.
Hope that makes sense.
So, after you structure your question / code and post it there, feel free to follow up here with the link. I get a lot of these questions, so I can't promise an answer, but I do try to get to them as much as I can.
I actually recently wrote a short piece about that here: https://www.baeldung.com/how-can-i-help
Cheers,
Eugen.


Validate native tracers with reth

Check if native tracers work with reth or not

Error:
arpit.temani@Polygon-V0VXP5G0XK:~/Workspace/Polygon/zk_evm|arpit/704⚡ ⇒  RUST_LOG=debug OUTPUT_TO_TERMINAL=true ./scripts/prove_rpc.sh 1 1 http://localhost:8545/ native 0 3000 100 test_only
Block batch size: 8
Proving blocks from (1) to (1)
   Compiling zero v0.1.0 (/Users/arpit.temani/Workspace/Polygon/zk_evm/zero)
    Finished `release` profile [optimized] target(s) in 31.65s
     Running `target/release/leader --test-only --runtime in-memory --load-strategy on-demand --proof-output-dir /Users/arpit.temani/Workspace/Polygon/zk_evm/proofs --block-batch-size 8 rpc --rpc-type native --rpc-url 'http://localhost:8545/' --start-block 1 --end-block 1 --backoff 3000 --max-retries 100 --checkpoint-block 0`
2024-11-11T12:16:25.564682Z  INFO leader: Proving interval 1
process_block_trace
process_block_trace
process_transactions
process_transaction
fetch_tx_data
fetch_tx_data - 1
fetch_tx_data - 2
fetch_tx_data - 3
fetch_tx_data - 4
process_transaction - 1
process_transaction - 2
process_transaction - 3
process_block_trace
Error: Failed to get proof for account

Caused by:
    server returned an error response: error code -32602: distance to target block exceeds maximum proof window

Stack backtrace:
   0: std::backtrace::Backtrace::create
   1: <futures_util::future::try_maybe_done::TryMaybeDone<Fut> as core::future::future::Future>::poll
   2: <futures_util::future::maybe_done::MaybeDone<Fut> as core::future::future::Future>::poll
   3: <futures_util::future::poll_fn::PollFn<F> as core::future::future::Future>::poll
   4: leader::main::{{closure}}
   5: tokio::runtime::park::CachedParkThread::block_on
   6: leader::main
   7: std::sys::backtrace::__rust_begin_short_backtrace
   8: std::rt::lang_start::{{closure}}
   9: std::rt::lang_start_internal
  10: _main
Proof witness generation finished with result: 1

Closing this for now


Add Services class

Codecov Report

Merging #4 (ebe5bc0) into master (fdbfb3b) will decrease coverage by 0.70%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##            master       #4      +/-   ##
===========================================
- Coverage   100.00%   99.29%   -0.71%
===========================================
  Files            2        2
  Lines          142      284     +142
  Branches        18       34      +16
===========================================
+ Hits           142      282     +140
- Misses           0        2       +2

Flag
Coverage Δ

unittests
99.29% <100.00%> (-0.71%)
:arrow_down:

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

Impacted Files
Coverage Δ

lib/node_service.js
99.29% <100.00%> (-0.71%)
:arrow_down:

Continue to review full report at Codecov.

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


Zee5 Extractor Error

[x] I've verified that I'm running yt-dlp version 2021.09.02
[x] I've checked that all provided URLs are alive and playable in a browser
[x] The provided URLs do not contain any DRM to the best of my knowledge
[x] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[x] I've searched the bugtracker for similar bug reports including closed ones
[x] I've read bugs section in FAQ

Verbose log
yt-dlp -F -v https://www.zee5.com/global/tvshows/details/apna-time-bhi-aayega/0-6-3008/apna-time-bhi-aayega-august-26-2021/0-1-manual-5uhb68jgqvg0
[debug] Command-line config: ['-F', '-v', 'https://www.zee5.com/global/tvshows/details/apna-time-bhi-aayega/0-6-3008/apna-time-bhi-aayega-august-26-2021/0-1-manual-5uhb68jgqvg0']
[debug] Encodings: locale cp1252, fs utf-8, out utf-8, pref cp1252
[debug] yt-dlp version 2021.08.10 (exe)
[debug] Python version 3.8.10 (CPython 64bit) - Windows-10-10.0.17763-SP0
[debug] exe versions: ffmpeg 4.4-full_build-www.gyan.dev, ffprobe 4.4-full_build-www.gyan.dev
[debug] Optional libraries: mutagen, pycryptodome, sqlite, websockets
[debug] Proxy map: {}
[debug] [Zee5] Extracting URL: https://www.zee5.com/global/tvshows/details/apna-time-bhi-aayega/0-6-3008/apna-time-bhi-aayega-august-26-2021/0-1-manual-5uhb68jgqvg0
[Zee5] 0-1-manual-5uhb68jgqvg0: Downloading access token
[Zee5] 0-1-manual-5uhb68jgqvg0: Downloading video token
ERROR: Unable to download JSON metadata: HTTP Error 404: Not Found (caused by <HTTPError 404: 'Not Found'>); please report this issue on  https://github.com/yt-dlp/yt-dlp . Make sure you are using the latest version; see  https://github.com/yt-dlp/yt-dlp  on how to update. Be sure to call yt-dlp with the --verbose flag and include its complete output.
  File "yt_dlp\extractor\common.py", line 682, in _request_webpage
  File "yt_dlp\YoutubeDL.py", line 3190, in urlopen
  File "urllib\request.py", line 531, in open
  File "urllib\request.py", line 640, in http_response
  File "urllib\request.py", line 563, in error
  File "urllib\request.py", line 502, in _call_chain
  File "urllib\request.py", line 755, in http_error_302
  File "urllib\request.py", line 531, in open
  File "urllib\request.py", line 640, in http_response
  File "urllib\request.py", line 569, in error
  File "urllib\request.py", line 502, in _call_chain
  File "urllib\request.py", line 649, in http_error_default

Description
Its look like token endpoint issue

don't click checkboxes blindly.
Already fixed, update ur exe


fix changes_display_dict to display added/deleted objects for m2m updates

In one of my projects I needed to use the changes_display_dict function in a Django template to display changes of a m2m field.
Apparently for such field the changes_display_dict function is not storing the added/deleted object while the changes_dict function does. The changes_display_dict function just store a list like this: ['type', 'operation', 'objects'] .
See screenshots attached.

I slightly modified the changes_display_dict function to also store the list of added/removed objects. The result is the following:

I hope you could consider merging this if appropriate. Happy to implement any changes/improvements you might suggest on my current proposal.

@a-cesari, thanks for your patch! I indeed missed changes_display_dict logic when implementing m2m tracking because it's a feature which I don't use myself.
Could you please cover the added logic with a test?


Remove CSS and JS fields for new installs and ones an without existing value

Changes

New installs will not see the Custom CSS and Custom JS fields, only a message and link to upcoming documentation.
Installs without a value saved to these fields will see the same.
Installs with a value in either field will see a deprecation message.

Testing

[x] This change adds unit test coverage
[x] This change has been tested on WP 5.1.1

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@a78b427). Click here to learn what that means.
The diff coverage is 94.11%.

@@            Coverage Diff            @@
##             master     #634   +/-   ##
=========================================
  Coverage          ?   38.88%
  Complexity        ?     1241
=========================================
  Files             ?       51
  Lines             ?     3811
  Branches          ?        0
=========================================
  Hits              ?     1482
  Misses            ?     2329
  Partials          ?        0

Impacted Files
Coverage Δ
Complexity Δ

lib/WP_Auth0_Options.php
72.72% <ø> (ø)
28 <0> (?)

lib/admin/WP_Auth0_Admin_Appearance.php
14.75% <94.11%> (ø)
19 <0> (?)

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 a78b427...b4cd688. Read the comment docs.


emscripten: 1.37.16 -> 1.37.34

Semi-automatic update. These checks were performed:

built on NixOS
found 1.37.34 with grep in /nix/store/mdr47v3wdjmzic5c2nvdx5krdwl6bcxf-emscripten-1.37.34

@GrahamcOfBorg build emscripten

Success on x86_64-darwin (full log)
Partial log (click to expand)
trying https://github.com/kripken/emscripten/archive/1.37.34.tar.gz
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   127    0   127    0     0    211      0 --:--:-- --:--:-- --:--:--   212
100 32.1M    0 32.1M    0     0  1776k      0 --:--:--  0:00:18 --:--:-- 2095k
unpacking source archive /private/tmp/nix-build-source.drv-0/1.37.34.tar.gz
copying path '/nix/store/fvw6b4kzw10hyfj4njwfxpxbldln171p-emscripten-fastcomp-wrapper-1.37.16' from 'https://cache.nixos.org'...
copying path '/nix/store/qjx6hyzg2fmn2psnjnpjxmw4zyy71izz-emscriptenfastcomp' from 'https://cache.nixos.org'...
building '/nix/store/29g20qrk06wr2zxwycv6z66lc8k3x8i2-emscripten-1.37.34.drv'...
/nix/store/1030pf5aly11mvq117jicnvxajgzi550-emscripten-1.37.34

Failure on aarch64-linux (full log)
Partial log (click to expand)
Package ‘oraclejre-8u161’ in /var/lib/gc-of-borg/nix-test-rs-2/repo/38dca4e3aa6bca43ea96d2fcc04e8229/builder/grahamc-aarch64-community-2/pkgs/development/compilers/oraclejdk/jdk-linux-base.nix:71 has an unfree license (‘unfree’), refusing to evaluate.

a) For `nixos-rebuild` you can set
  { nixpkgs.config.allowUnfree = true; }
in configuration.nix to override this.

b) For `nix-env`, `nix-build`, `nix-shell` or any other Nix command you can add
  { allowUnfree = true; }
to ~/.config/nixpkgs/config.nix.

Success on x86_64-linux (full log)
Partial log (click to expand)

*** Downloading ‘https://cache.nixos.org/nar/0qgd98xmqf322i945vzxf3xg8086x6451hf4vmc5ri8mrnlrs6s7.nar.xz’ (signed by ‘cache.nixos.org-1’) to ‘/nix/store/fky9air5q4ji9whdyribbpwj6drgiz4q-emscriptenfastcomp’...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed

  0     0    0     0    0     0      0      0 --:--:-- --:--:-- --:--:--     0
100 27996  100 27996    0     0  84325      0 --:--:-- --:--:-- --:--:-- 84325

100 6535k  100 6535k    0     0  7005k      0 --:--:-- --:--:-- --:--:-- 6997k

building path(s) ‘/nix/store/mdr47v3wdjmzic5c2nvdx5krdwl6bcxf-emscripten-1.37.34’
/nix/store/mdr47v3wdjmzic5c2nvdx5krdwl6bcxf-emscripten-1.37.34

Is the compiler tested as part of building itself, or should that be done as well? Never poked at the emscripten bits...

cc @qknight @matthiasbeyer

You meant @matthewbauer

@matthiasbeyer it worked out in the end :)

While debugging my follow-up PR, I found that this breaks emscriptenPackages?
Not familiar enough to say why, but it worked previously:
@GrahamcOfBorg build emscriptenPackages.zlib
Like I said before, does the resulting compiler still work? Apparently not... (at least not the way we used it) :(.

No attempt on aarch64-linux
The following builds were skipped because they don't evaluate on aarch64-linux: emscriptenPackages.zlib
No log is available.

Failure on x86_64-darwin (full log)
Attempted: emscriptenPackages.zlib
Partial log (click to expand)
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file zlib-1.2.11/zutil.c
patching sources
configuring
INFO:root:generating system asset: is_vanilla.txt... (this will be cached in "/private/tmp/nix-build-emscripten-zlib-1.2.11.drv-0/.emscripten_cache/is_vanilla.txt" for subsequent builds)
INFO:root: - ok
Compiler error reporting is too harsh for ./configure (perhaps remove -Werror).
** ./configure aborting.
ERROR:root:Configure step failed with non-zero return code 1! Command line: ['./configure', '--prefix=/nix/store/xvv659ix482wjz6jm4ff91dg2mm76lmj-emscripten-zlib-1.2.11'] at /private/tmp/nix-build-emscripten-zlib-1.2.11.drv-0/zlib-1.2.11
builder for '/nix/store/g7dmgqidgs837nz65d0yb76p0an71f0m-emscripten-zlib-1.2.11.drv' failed with exit code 1
error: build of '/nix/store/g7dmgqidgs837nz65d0yb76p0an71f0m-emscripten-zlib-1.2.11.drv' failed

@joachifm based on @dtzWill's cpmment seems like we should revert.

Success on x86_64-linux (full log)
Attempted: emscriptenPackages.zlib
Partial log (click to expand)
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/9rlgsjbf2hp35f29wi2z17vvz12qmmfk-emscripten-zlib-1.2.11-dev/lib
patching script interpreter paths in /nix/store/9rlgsjbf2hp35f29wi2z17vvz12qmmfk-emscripten-zlib-1.2.11-dev
checking for references to /tmp/nix-build-emscripten-zlib-1.2.11.drv-0 in /nix/store/9rlgsjbf2hp35f29wi2z17vvz12qmmfk-emscripten-zlib-1.2.11-dev...
shrinking RPATHs of ELF executables and libraries in /nix/store/n7skclzybwm6c35yqb9b4h4myj06h7vx-emscripten-zlib-1.2.11-static
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/n7skclzybwm6c35yqb9b4h4myj06h7vx-emscripten-zlib-1.2.11-static/lib
patching script interpreter paths in /nix/store/n7skclzybwm6c35yqb9b4h4myj06h7vx-emscripten-zlib-1.2.11-static
checking for references to /tmp/nix-build-emscripten-zlib-1.2.11.drv-0 in /nix/store/n7skclzybwm6c35yqb9b4h4myj06h7vx-emscripten-zlib-1.2.11-static...
/nix/store/4vjwq8rnqxz0dx34j8rcwcg3zdnxj4by-emscripten-zlib-1.2.11

@ryantm @dtzWill i've been playing with this for a while now but it seems that those packages didn't build before either. no clue why yet.
i'll look into this. don't revert for the moment.

@qknight It was already reverted.

@ryantm thanks for your effort!
see this: https://github.com/kripken/emscripten-fastcomp/issues/224

... you should use the same emscripten version in all 3 repos (emcc should warn if you do not).

well, it didn't warn IIRC

You must also use the same version of LLVM and clang (unrelated to emscripten - if those repos don't match, LLVM won't be able to use clang properly). The same emscripten version in those repos will take care of that for you. Likewise the same emscripten version will ensure you are on the right LLVM version.

i found that out the hard way.
in general we should change nixpkgs expressions so that one defines the version number as 1.37.36 and all the 3 expressions download the same version.
our roadmap should be:

get emscriptenPackages to comiple with 1.37.36

emcc main.c -> produces something working
emconfigure seems to fail

get a meaningful set of tests in the emscripten package working
refactor the 3 expressions to use the same target version (only set once)

@everyone
i've been playing with 1.37.36 and implemented the unit testing:

source: https://github.com/qknight/nixpkgs/tree/emscripten-1.37.16-to-1.37.36

result : https://gist.github.com/qknight/fd7027a70830b4080e3b4352476e8009

altough there are lots of errors, this is not looking so bad. i'd love to select some meaningful tests and get these into nixpkgs. we can't do all, this requires at least 4220.752s to complete, which is too long!
building emscriptenPackage.zlib
still this won't compile with the new toolchain. no clue why, anyone?
joachim@lenovo-t530 ~/D/p/n/nixpkgs> nix-env -f default.nix -I nixpkgs=. -iA emscriptenPackages.zlib
installing ‘emscripten-zlib-1.2.11’
these derivations will be built:
  /nix/store/8xlwzkd9lsziq188fyznsdmyqgmg7w5f-emscripten-zlib-1.2.11.drv
building path(s) ‘/nix/store/1az5xq03k6qjms3mdvaiix25fk51whv4-emscripten-zlib-1.2.11-static’, ‘/nix/store/ak7rqj9bdhdf0ll4idr6sb06jzrcb6s3-emscripten-zlib-1.2.11-dev’, ‘/nix/store/qi1k9vbp9jzavx44n96zv2ihz96c16af-emscripten-zlib-1.2.11’
unpacking sources
unpacking source archive /nix/store/rrzja19jbqxbfryp2zchb2ma5h041rxh-zlib-1.2.11.tar.gz
source root is zlib-1.2.11
setting SOURCE_DATE_EPOCH to timestamp<PHONE_NUMBER> of file zlib-1.2.11/zutil.c
patching sources
configuring
INFO:root:generating system asset: is_vanilla.txt... (this will be cached in "/tmp/nix-build-emscripten-zlib-1.2.11.drv-0/.emscripten_cache/is_vanilla.txt" for subsequent builds)
INFO:root: - ok
Compiler error reporting is too harsh for ./configure (perhaps remove -Werror).
** ./configure aborting.
ERROR:root:Configure step failed with non-zero return code 1! Command line: ['./configure', '--prefix=/nix/store/qi1k9vbp9jzavx44n96zv2ihz96c16af-emscripten-zlib-1.2.11'] at /tmp/nix-build-emscripten-zlib-1.2.11.drv-0/zlib-1.2.11
builder for ‘/nix/store/8xlwzkd9lsziq188fyznsdmyqgmg7w5f-emscripten-zlib-1.2.11.drv’ failed with exit code 1
error: build of ‘/nix/store/8xlwzkd9lsziq188fyznsdmyqgmg7w5f-emscripten-zlib-1.2.11.drv’ failed

Just a guess but maybe try setting 'hardeningDisable = [ "format" ]'

seems the python executable was missing and therefore emconfigure's internals fail. i might have json_c and zlib working

LONG_BIT is no longer a problem, i've added this:
emconfigure ./configure --prefix=$out --without-python
to libxml2

@matthewbauer maybe you could check https://github.com/kripken/emscripten/issues/6341 for an obvious error i've made.

@qknight That was just a guess based on the "Compiler error reporting is too harsh" line. But it sounds like python was the real culprit.

@qknight Looks like this might be the culprit:
https://github.com/NixOS/nixpkgs/blob/5f020d5627789ce77b2997e360ece984c261bce7/pkgs/development/libraries/zlib/default.nix#L53
This was introduced in @Ericson2314's cross compiling patches.

@matthewbauer you are amazing!
setting: NIX_CFLAGS_COMPILE=""; leads to a libz shared library!

status update:

[x] the emscriptenVersion is a global attribute which is used for emscripten and emscripten-fastcomp
[x] added a test to check if emscripten is working
[x] updated to 1.37.28 (because i needed to test something)
[x] fix emscriptenPackages.libxml2
[x] fix emscriptenPackages.zlib
[] fix emscriptenPackages.xmlmirror
[] updated to 1.37.36

will upload my branch in a few secs...

@ryantm  @matthewbauer
if you want to test my changes:

source: https://github.com/qknight/nixpkgs/tree/emscripten-1.37.16-to-1.37.36
command: nix-env -f default.nix -I nixpkgs=. -iA emscriptenPackages

so everything from my perspective is now working. someone interested in helping me to write the documentation?

\o/  done!

@matthewbauer please have a look at https://github.com/NixOS/nixpkgs/pull/37291


Introduce the search icon (magnifying glass) in the search field which acts as a filter

Hey Jacob,
it's a common pattern for search when it functions like a filter, to have the magnifying glass icon at the start of the box..
can we place one there and then have the text 'Search projects' after.. hope this is not too much
Gabs

this is done.


words hidden by the edge

parts of the text are being hidden by the edge nd there is no way to read them besides the parts that are visible
Additional Details
Share Link :
or
Brew code to reproduce : Click to expand
PASTE BREW CODE HERE

It's hard to help without seeing what's going on. Mind posting the "share" link to your brew as the above form asked you to?

Closing for now because of no further response from the user, and the issue does not have enough information to fix.
Feel free to reopen this issue if this is still a problem for you and you can provide more information. @wspr119


Strip whitespaces from names before saving organisation, scheme or a user

Saving it with a space was erroring out when trying to select them from an accessible select.
It also makes sense not to store the leading/trailing spaces in the names

We probably want this on location name as well?


Add Todo flag

Adds a boolean flag called todo  which defaults to true. If it's set to true // TODO: flags will be included in the generated code. Otherwise they will not.
Resolves https://github.com/matryer/moq/issues/56

There's no need for a flag here. Let's just remove TODO from the template?

@pdrum great job though :) Well executed.


Not sure if this is intentional or not, but the title is self explanatory. Doesn't really matter that much, but I thought it'd be nice to let you know.

i think its funny


Cold Email Generator Using LLM

Problem Statement
In the competitive world of software services, companies like TCS, Infosys, and Attic Technologies compete to acquire new clients by providing high-quality software solutions. Their clients—large corporations such as Nike, JP Morgan, and Kroger—often post job openings indicating specific technology needs. These job posts provide insight into client requirements for software engineering, especially in AI/ML and DevOps, which these service providers can leverage to offer contract-based solutions.
Solution Overview
The Cold Email Generator tool will take a job posting as input, extract required skills, and automatically craft a customized cold email that highlights the service provider’s expertise in the relevant domains. The generated email will focus on how the service provider's team can meet the client’s requirements on a contract basis, showcasing previous project experience and relevant skills to make the outreach compelling.
Approach to be followed are here -
Data Extraction
Skill Matching and Email Generation
Components and Technology- LLM (Lama 3.1), Chroma ADB (Vector Store) , LangChain
Objective: Sales teams at these software service companies frequently use cold emailing as a technique to approach potential clients. However, crafting personalized, skill-relevant cold emails can be time-consuming. This project aims to automate the process of generating highly relevant cold emails by analyzing job postings and matching them with the service provider's expertise. The goal is to save time and improve the effectiveness of these outreach efforts by using an LLM (Large Language Model) to generate context-specific cold emails.
@UTSAVS26  liked my project idea assign me task i will on it !

@SimranShaikh20 please read this #1073


Fixed field local cache warm up in case of nested calls

It seems like nested metadata load happens under certain conditions.
1.	IndexMetadataBuilder tries to get field config
2.	\Oro\Bundle\EntityConfigBundle\Config\ConfigModelManager::findFieldModel are called and it calls \Oro\Bundle\EntityConfigBundle\Config\ConfigModelManager::ensureFieldLocalCacheWarmed
3.	ensureFieldLocalCacheWarmed calls \Oro\Bundle\EntityConfigBundle\Entity\EntityConfigModel::getFields
4.	fields are loaded from DB
5.	Doctrine unserializes field data and calls autoloader
6.	autoloader calls getAllMetadata
7.	that eventually lead to IndexMetadataBuilder tries to get config of the same field
8.	findFieldModel are called again and it calls ensureFieldLocalCacheWarmed
9.	BUT we are still in previous ensureFieldLocalCacheWarmed call!

In the second pass in ensureFieldLocalCacheWarmed $this->fieldLocalCache[$className] is already set. But it is an empty array because the previous call of ensureFieldLocalCacheWarmed not finished yet.
So findFieldModel returns nothing and the exception are thrown.
This pull request does not fixes nested calls. But it prevents incorrect local field cache warm up.

Hi @turboezh,
Could you please provide us with STR.
Thanks.

Excuse my unawareness. What is STR?

STR - Steps to Reproduce.

@hurricane-voronin, hi.
Unfortunately I can't continue to work on this. This PR may be closed.
I can't easily provide STR. Most likely described situation is very specific and associated with inconsistent database of custom fields (with indexes). It may be not relevant with consistent DB.

Thank you for your pull request.
It looks like this may be your first contribution to an Oro, Inc. open source project, in which case you'll need to sign a Contributor License Agreement (CLA) at http://www.orocrm.com/contributor-license-agreement/
If you've already signed the CLA, it's possible we don't have your GitHub username or you're using a different email address. GitHub uses the email address you set in your local Git configuration to associate commits with your GitHub account. Please sign the CLA again using the correct GitHub username and email address or see this help article on setting the email on your git commits.
Once you've signed the CLA, please allow for about an hour for the submission to be processed.

Closing this PR based on @turboezh feedback.


How to test a function that returns a Promise

I want to test a function that returns a Promise
I expect this test case to fail, but it passed. Do I miss anything here?
// > resolve(2)
// Promise.resolve(3);
function resolve(x) {
  return Promise.resolve(x);
}

Thank you for the bug report, @zhangchiqing. The problem lies with R.equals. I just opened ramda/ramda#1616 for discussion.

I think that promises here should be considered as generic objects. Note that even in Python, doctests were never meant to compare two objects, since the semantic of such a comparison would be ambiguous. Something loosely related here, from the Python doc.
Interestingly enough, trying to work around this constraints would lead you to test with doctests just purely functional code, and push the use of promises elsewhere, at the boundaries of your computation logic. Promises are asynchronous because they usually involve side effects, which are out of the range of doctests anyway.
If you really need to test a function returning an object, you will need to provide equality methods for your object, like showed in comparisons for Python dictionaries, in the doc linked above

I agree. If we need to doctest a function that returns a generic Object (e.g. MyObject in your case), we could provide its own equality method. But that equality method would have to return a Bool value synchronously for doctest to check the result.
Since Promises are asynchronous, I don't think doctest is able to wait for the asynchronous operation to finish then check. (Please correct me if I'm wrong here)
I tried, this would fail.
// > resolve(2).then(function(x) { return x; })
// 2
function resolve(x) {
  return Promise.resolve(x);
}

// => || FAIL: expected 2 on line 32 (got {})

Then it would mean that a function returns a Promise, which is asynchronous, would be untestable for doctest. no?

Then it would mean that a function returns a Promise, which is asynchronous, would be untestable for doctest. no?

Correct. Testing asynchronous functions is out of scope for this project.
Thanks for finding and reporting a bug in Ramda, though! I've opened a pull request to fix it.


changed error message

Ticket: #15
Describe The Problem Being Solved:
changed error message
Checklist For Submitter

[x] I have documented all new functionality
[-] I have screenshotted new UI changes and attached them to this PR

Reminder list For Reviewers

Code formatting/static analysis: is the code formatted properly? Does a linter/other form of static analysis reveal any issues? Does the code have appropriately low cyclomatic complexity?
Code architecture: concerns are separated, code follows single-responsibility principle, code utilizes OOP, DRY code.
Coding best practices: code avoids hard-coded variables, inefficient computations, reinventing the wheel when using frameworks. Code is well-commented and generally readable.
Non-functional requirements: Code has accompanying tests. Programmer can easily explain decisions to reviewers.

looks good to me


which use PEP 517 and cannot be installed directly

Collecting django-simple-history
Downloading django-simple-history-3.1.1.tar.gz (544 kB)
|████████████████████████████████| 544 kB 939 kB/s
Installing build dependencies ... done
Getting requirements to build wheel ... done
Installing backend dependencies ... done
Preparing wheel metadata ... done
Building wheels for collected packages: django-simple-history
Building wheel for django-simple-history (PEP 517) ... error
ERROR: Command errored out with exit status 1:
command: 'C:\Users\toqp.conda\envs\imitator_fedsfm\python.exe' 'C:\Users\toqp.conda\envs\imitator_fedsfm\lib\site-packages\pip_vendor\pe
p517\in_process_in_process.py' build_wheel 'C:\Users\toqp\AppData\Local\Temp\tmpdd8v77oh'
cwd: C:\Users\toqp\AppData\Local\Temp\pip-install-1hil4l1g\django-simple-history_d2e457f0360c497eb9f3145efd9004d2
Complete output (439 lines):
running bdist_wheel
running build
running build_py
creating build
creating build\lib
creating build\lib\simple_history
copying simple_history\admin.py -> build\lib\simple_history
copying simple_history\exceptions.py -> build\lib\simple_history
copying simple_history\manager.py -> build\lib\simple_history
copying simple_history\middleware.py -> build\lib\simple_history
copying simple_history\models.py -> build\lib\simple_history
copying simple_history\signals.py -> build\lib\simple_history
copying simple_history\utils.py -> build\lib\simple_history
copying simple_history_init_.py -> build\lib\simple_history
creating build\lib\simple_history\management
copying simple_history\management_init_.py -> build\lib\simple_history\management
creating build\lib\simple_history\management\commands
copying simple_history\management\commands\clean_duplicate_history.py -> build\lib\simple_history\management\commands
copying simple_history\management\commands\clean_old_history.py -> build\lib\simple_history\management\commands
copying simple_history\management\commands\populate_history.py -> build\lib\simple_history\management\commands
copying simple_history\management\commands_init_.py -> build\lib\simple_history\management\commands
creating build\lib\simple_history\templatetags
copying simple_history\templatetags\getattributes.py -> build\lib\simple_history\templatetags
copying simple_history\templatetags\simple_history_admin_list.py -> build\lib\simple_history\templatetags
copying simple_history\templatetags\simple_history_compat.py -> build\lib\simple_history\templatetags
copying simple_history\templatetags_init_.py -> build\lib\simple_history\templatetags
running egg_info
writing django_simple_history.egg-info\PKG-INFO
writing dependency_links to django_simple_history.egg-info\dependency_links.txt
writing top-level names to django_simple_history.egg-info\top_level.txt
listing git files failed - pretending there aren't any
reading manifest file 'django_simple_history.egg-info\SOURCES.txt'
reading manifest template 'MANIFEST.in'
adding license file 'LICENSE.txt'
adding license file 'AUTHORS.rst'
writing manifest file 'django_simple_history.egg-info\SOURCES.txt'
C:\Users\toqp\AppData\Local\Temp\pip-build-env-heka82r_\overlay\Lib\site-packages\setuptools\command\build_py.py:153: SetuptoolsDeprecationW
arning:     Installing 'simple_history.locale.cs_CZ.LC_MESSAGES' as data is deprecated, please list it in packages.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'simple_history.locale.cs_CZ.LC_MESSAGES' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'simple_history.locale.cs_CZ.LC_MESSAGES' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'simple_history.locale.cs_CZ.LC_MESSAGES' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

C:\Users\toqp\AppData\Local\Temp\pip-build-env-heka82r_\overlay\Lib\site-packages\setuptools\command\build_py.py:153: SetuptoolsDeprecationW
arning:     Installing 'simple_history.locale.de.LC_MESSAGES' as data is deprecated, please list it in packages.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'simple_history.locale.de.LC_MESSAGES' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'simple_history.locale.de.LC_MESSAGES' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'simple_history.locale.de.LC_MESSAGES' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

C:\Users\toqp\AppData\Local\Temp\pip-build-env-heka82r_\overlay\Lib\site-packages\setuptools\command\build_py.py:153: SetuptoolsDeprecationW
arning:     Installing 'simple_history.locale.fr.LC_MESSAGES' as data is deprecated, please list it in packages.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'simple_history.locale.fr.LC_MESSAGES' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'simple_history.locale.fr.LC_MESSAGES' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'simple_history.locale.fr.LC_MESSAGES' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

C:\Users\toqp\AppData\Local\Temp\pip-build-env-heka82r_\overlay\Lib\site-packages\setuptools\command\build_py.py:153: SetuptoolsDeprecationW
arning:     Installing 'simple_history.locale.pl.LC_MESSAGES' as data is deprecated, please list it in packages.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'simple_history.locale.pl.LC_MESSAGES' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'simple_history.locale.pl.LC_MESSAGES' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'simple_history.locale.pl.LC_MESSAGES' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

C:\Users\toqp\AppData\Local\Temp\pip-build-env-heka82r_\overlay\Lib\site-packages\setuptools\command\build_py.py:153: SetuptoolsDeprecationW
arning:     Installing 'simple_history.locale.pt_BR.LC_MESSAGES' as data is deprecated, please list it in packages.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'simple_history.locale.pt_BR.LC_MESSAGES' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'simple_history.locale.pt_BR.LC_MESSAGES' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'simple_history.locale.pt_BR.LC_MESSAGES' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

C:\Users\toqp\AppData\Local\Temp\pip-build-env-heka82r_\overlay\Lib\site-packages\setuptools\command\build_py.py:153: SetuptoolsDeprecationW
arning:     Installing 'simple_history.locale.ru_RU.LC_MESSAGES' as data is deprecated, please list it in packages.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'simple_history.locale.ru_RU.LC_MESSAGES' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'simple_history.locale.ru_RU.LC_MESSAGES' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'simple_history.locale.ru_RU.LC_MESSAGES' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

C:\Users\toqp\AppData\Local\Temp\pip-build-env-heka82r_\overlay\Lib\site-packages\setuptools\command\build_py.py:153: SetuptoolsDeprecationW
arning:     Installing 'simple_history.registry_tests' as data is deprecated, please list it in packages.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'simple_history.registry_tests' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'simple_history.registry_tests' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'simple_history.registry_tests' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

C:\Users\toqp\AppData\Local\Temp\pip-build-env-heka82r_\overlay\Lib\site-packages\setuptools\command\build_py.py:153: SetuptoolsDeprecationW
arning:     Installing 'simple_history.registry_tests.migration_test_app' as data is deprecated, please list it in packages.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'simple_history.registry_tests.migration_test_app' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'simple_history.registry_tests.migration_test_app' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'simple_history.registry_tests.migration_test_app' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

C:\Users\toqp\AppData\Local\Temp\pip-build-env-heka82r_\overlay\Lib\site-packages\setuptools\command\build_py.py:153: SetuptoolsDeprecationW
arning:     Installing 'simple_history.registry_tests.migration_test_app.migrations' as data is deprecated, please list it in packages.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'simple_history.registry_tests.migration_test_app.migrations' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'simple_history.registry_tests.migration_test_app.migrations' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'simple_history.registry_tests.migration_test_app.migrations' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

C:\Users\toqp\AppData\Local\Temp\pip-build-env-heka82r_\overlay\Lib\site-packages\setuptools\command\build_py.py:153: SetuptoolsDeprecationW
arning:     Installing 'simple_history.templates.simple_history' as data is deprecated, please list it in packages.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'simple_history.templates.simple_history' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'simple_history.templates.simple_history' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'simple_history.templates.simple_history' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

C:\Users\toqp\AppData\Local\Temp\pip-build-env-heka82r_\overlay\Lib\site-packages\setuptools\command\build_py.py:153: SetuptoolsDeprecationW
arning:     Installing 'simple_history.tests' as data is deprecated, please list it in packages.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'simple_history.tests' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'simple_history.tests' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'simple_history.tests' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

C:\Users\toqp\AppData\Local\Temp\pip-build-env-heka82r_\overlay\Lib\site-packages\setuptools\command\build_py.py:153: SetuptoolsDeprecationW
arning:     Installing 'simple_history.tests.custom_user' as data is deprecated, please list it in packages.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'simple_history.tests.custom_user' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'simple_history.tests.custom_user' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'simple_history.tests.custom_user' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

C:\Users\toqp\AppData\Local\Temp\pip-build-env-heka82r_\overlay\Lib\site-packages\setuptools\command\build_py.py:153: SetuptoolsDeprecationW
arning:     Installing 'simple_history.tests.external' as data is deprecated, please list it in packages.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'simple_history.tests.external' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'simple_history.tests.external' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'simple_history.tests.external' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

C:\Users\toqp\AppData\Local\Temp\pip-build-env-heka82r_\overlay\Lib\site-packages\setuptools\command\build_py.py:153: SetuptoolsDeprecationW
arning:     Installing 'simple_history.tests.tests' as data is deprecated, please list it in packages.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'simple_history.tests.tests' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'simple_history.tests.tests' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'simple_history.tests.tests' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

creating build\lib\simple_history\locale
creating build\lib\simple_history\locale\cs_CZ
creating build\lib\simple_history\locale\cs_CZ\LC_MESSAGES
copying simple_history\locale\cs_CZ\LC_MESSAGES\django.mo -> build\lib\simple_history\locale\cs_CZ\LC_MESSAGES
copying simple_history\locale\cs_CZ\LC_MESSAGES\django.po -> build\lib\simple_history\locale\cs_CZ\LC_MESSAGES
creating build\lib\simple_history\locale\de
creating build\lib\simple_history\locale\de\LC_MESSAGES
copying simple_history\locale\de\LC_MESSAGES\django.mo -> build\lib\simple_history\locale\de\LC_MESSAGES
copying simple_history\locale\de\LC_MESSAGES\django.po -> build\lib\simple_history\locale\de\LC_MESSAGES
creating build\lib\simple_history\locale\fr
creating build\lib\simple_history\locale\fr\LC_MESSAGES
copying simple_history\locale\fr\LC_MESSAGES\django.mo -> build\lib\simple_history\locale\fr\LC_MESSAGES
copying simple_history\locale\fr\LC_MESSAGES\django.po -> build\lib\simple_history\locale\fr\LC_MESSAGES
creating build\lib\simple_history\locale\pl
creating build\lib\simple_history\locale\pl\LC_MESSAGES
copying simple_history\locale\pl\LC_MESSAGES\django.mo -> build\lib\simple_history\locale\pl\LC_MESSAGES
copying simple_history\locale\pl\LC_MESSAGES\django.po -> build\lib\simple_history\locale\pl\LC_MESSAGES
creating build\lib\simple_history\locale\pt_BR
creating build\lib\simple_history\locale\pt_BR\LC_MESSAGES
copying simple_history\locale\pt_BR\LC_MESSAGES\django.mo -> build\lib\simple_history\locale\pt_BR\LC_MESSAGES
copying simple_history\locale\pt_BR\LC_MESSAGES\django.po -> build\lib\simple_history\locale\pt_BR\LC_MESSAGES
creating build\lib\simple_history\locale\ru_RU
creating build\lib\simple_history\locale\ru_RU\LC_MESSAGES
copying simple_history\locale\ru_RU\LC_MESSAGES\django.mo -> build\lib\simple_history\locale\ru_RU\LC_MESSAGES
copying simple_history\locale\ru_RU\LC_MESSAGES\django.po -> build\lib\simple_history\locale\ru_RU\LC_MESSAGES
creating build\lib\simple_history\registry_tests
copying simple_history\registry_tests_init_.py -> build\lib\simple_history\registry_tests
copying simple_history\registry_tests\models.py -> build\lib\simple_history\registry_tests
copying simple_history\registry_tests\tests.py -> build\lib\simple_history\registry_tests
creating build\lib\simple_history\registry_tests\migration_test_app
copying simple_history\registry_tests\migration_test_app_init_.py -> build\lib\simple_history\registry_tests\migration_test_app
copying simple_history\registry_tests\migration_test_app\models.py -> build\lib\simple_history\registry_tests\migration_test_app
creating build\lib\simple_history\registry_tests\migration_test_app\migrations
copying simple_history\registry_tests\migration_test_app\migrations\0001_initial.py -> build\lib\simple_history\registry_tests\migration_tes
t_app\migrations
copying simple_history\registry_tests\migration_test_app\migrations\0002_historicalmodelwithcustomattrforeignkey_modelwithcustomattrforeignk
ey.py -> build\lib\simple_history\registry_tests\migration_test_app\migrations
copying simple_history\registry_tests\migration_test_app\migrations\0003_alter_historicalmodelwithcustomattrforeignkey_options_and_more.py -

build\lib\simple_history\registry_tests\migration_test_app\migrations
copying simple_history\registry_tests\migration_test_app\migrations\0004_history_date_indexing.py -> build\lib\simple_history\registry_tests
\migration_test_app\migrations
copying simple_history\registry_tests\migration_test_app\migrations\0005_historicalmodelwithcustomattronetoonefield_modelwithcustomattroneto
onefield.py -> build\lib\simple_history\registry_tests\migration_test_app\migrations
error: could not create 'build\lib\simple_history\registry_tests\migration_test_app\migrations\0005_historicalmodelwithcustomattronetoonefie
ld_modelwithcustomattronetoonefield.py': No such file or directory

ERROR: Failed building wheel for django-simple-history
Failed to build django-simple-history
ERROR: Could not build wheels for django-simple-history which use PEP 517 and cannot be installed directly
C:\Users\toqp\PycharmProjects\imitator_fedsfm\imitator_fedsfm>C:\Users\toqp.conda\envs\imitator_fedsfm_2\python.exe -m pip install django-sim
ple-history
Collecting django-simple-history
Using cached django-simple-history-3.1.1.tar.gz (544 kB)
Installing build dependencies ... done
Getting requirements to build wheel ... done
Installing backend dependencies ... done
Preparing wheel metadata ... done
Building wheels for collected packages: django-simple-history
Building wheel for django-simple-history (PEP 517) ... error
ERROR: Command errored out with exit status 1:
command: 'C:\Users\toqp.conda\envs\imitator_fedsfm_2\python.exe' 'C:\Users\toqp.conda\envs\imitator_fedsfm_2\lib\site-packages\pip_vendo
r\pep517\in_process_in_process.py' build_wheel 'C:\Users\toqp\AppData\Local\Temp\tmpgh34532h'
cwd: C:\Users\toqp\AppData\Local\Temp\pip-install-yg546var\django-simple-history_59e47d9cffe44f30bea0921ed51d4aae
Complete output (439 lines):
running bdist_wheel
running build
running build_py
creating build
creating build\lib
creating build\lib\simple_history
copying simple_history\admin.py -> build\lib\simple_history
copying simple_history\exceptions.py -> build\lib\simple_history
copying simple_history\manager.py -> build\lib\simple_history
copying simple_history\middleware.py -> build\lib\simple_history
copying simple_history\models.py -> build\lib\simple_history
copying simple_history\signals.py -> build\lib\simple_history
copying simple_history\utils.py -> build\lib\simple_history
copying simple_history_init_.py -> build\lib\simple_history
creating build\lib\simple_history\management
copying simple_history\management_init_.py -> build\lib\simple_history\management
creating build\lib\simple_history\management\commands
copying simple_history\management\commands\clean_duplicate_history.py -> build\lib\simple_history\management\commands
copying simple_history\management\commands\clean_old_history.py -> build\lib\simple_history\management\commands
copying simple_history\management\commands\populate_history.py -> build\lib\simple_history\management\commands
copying simple_history\management\commands_init_.py -> build\lib\simple_history\management\commands
creating build\lib\simple_history\templatetags
copying simple_history\templatetags\getattributes.py -> build\lib\simple_history\templatetags
copying simple_history\templatetags\simple_history_admin_list.py -> build\lib\simple_history\templatetags
copying simple_history\templatetags\simple_history_compat.py -> build\lib\simple_history\templatetags
copying simple_history\templatetags_init_.py -> build\lib\simple_history\templatetags
running egg_info
writing django_simple_history.egg-info\PKG-INFO
writing dependency_links to django_simple_history.egg-info\dependency_links.txt
writing top-level names to django_simple_history.egg-info\top_level.txt
listing git files failed - pretending there aren't any
reading manifest file 'django_simple_history.egg-info\SOURCES.txt'
reading manifest template 'MANIFEST.in'
adding license file 'LICENSE.txt'
adding license file 'AUTHORS.rst'
writing manifest file 'django_simple_history.egg-info\SOURCES.txt'
C:\Users\toqp\AppData\Local\Temp\pip-build-env-bq_rns37\overlay\Lib\site-packages\setuptools\command\build_py.py:153: SetuptoolsDeprecationW
arning:     Installing 'simple_history.locale.cs_CZ.LC_MESSAGES' as data is deprecated, please list it in packages.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'simple_history.locale.cs_CZ.LC_MESSAGES' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'simple_history.locale.cs_CZ.LC_MESSAGES' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'simple_history.locale.cs_CZ.LC_MESSAGES' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

C:\Users\toqp\AppData\Local\Temp\pip-build-env-bq_rns37\overlay\Lib\site-packages\setuptools\command\build_py.py:153: SetuptoolsDeprecationW
arning:     Installing 'simple_history.locale.de.LC_MESSAGES' as data is deprecated, please list it in packages.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'simple_history.locale.de.LC_MESSAGES' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'simple_history.locale.de.LC_MESSAGES' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'simple_history.locale.de.LC_MESSAGES' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

C:\Users\toqp\AppData\Local\Temp\pip-build-env-bq_rns37\overlay\Lib\site-packages\setuptools\command\build_py.py:153: SetuptoolsDeprecationW
arning:     Installing 'simple_history.locale.fr.LC_MESSAGES' as data is deprecated, please list it in packages.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'simple_history.locale.fr.LC_MESSAGES' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'simple_history.locale.fr.LC_MESSAGES' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'simple_history.locale.fr.LC_MESSAGES' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

C:\Users\toqp\AppData\Local\Temp\pip-build-env-bq_rns37\overlay\Lib\site-packages\setuptools\command\build_py.py:153: SetuptoolsDeprecationW
arning:     Installing 'simple_history.locale.pl.LC_MESSAGES' as data is deprecated, please list it in packages.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'simple_history.locale.pl.LC_MESSAGES' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'simple_history.locale.pl.LC_MESSAGES' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'simple_history.locale.pl.LC_MESSAGES' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

C:\Users\toqp\AppData\Local\Temp\pip-build-env-bq_rns37\overlay\Lib\site-packages\setuptools\command\build_py.py:153: SetuptoolsDeprecationW
arning:     Installing 'simple_history.locale.pt_BR.LC_MESSAGES' as data is deprecated, please list it in packages.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'simple_history.locale.pt_BR.LC_MESSAGES' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'simple_history.locale.pt_BR.LC_MESSAGES' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'simple_history.locale.pt_BR.LC_MESSAGES' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

C:\Users\toqp\AppData\Local\Temp\pip-build-env-bq_rns37\overlay\Lib\site-packages\setuptools\command\build_py.py:153: SetuptoolsDeprecationW
arning:     Installing 'simple_history.locale.ru_RU.LC_MESSAGES' as data is deprecated, please list it in packages.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'simple_history.locale.ru_RU.LC_MESSAGES' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'simple_history.locale.ru_RU.LC_MESSAGES' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'simple_history.locale.ru_RU.LC_MESSAGES' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

C:\Users\toqp\AppData\Local\Temp\pip-build-env-bq_rns37\overlay\Lib\site-packages\setuptools\command\build_py.py:153: SetuptoolsDeprecationW
arning:     Installing 'simple_history.registry_tests' as data is deprecated, please list it in packages.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'simple_history.registry_tests' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'simple_history.registry_tests' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'simple_history.registry_tests' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

C:\Users\toqp\AppData\Local\Temp\pip-build-env-bq_rns37\overlay\Lib\site-packages\setuptools\command\build_py.py:153: SetuptoolsDeprecationW
arning:     Installing 'simple_history.registry_tests.migration_test_app' as data is deprecated, please list it in packages.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'simple_history.registry_tests.migration_test_app' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'simple_history.registry_tests.migration_test_app' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'simple_history.registry_tests.migration_test_app' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

C:\Users\toqp\AppData\Local\Temp\pip-build-env-bq_rns37\overlay\Lib\site-packages\setuptools\command\build_py.py:153: SetuptoolsDeprecationW
arning:     Installing 'simple_history.registry_tests.migration_test_app.migrations' as data is deprecated, please list it in packages.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'simple_history.registry_tests.migration_test_app.migrations' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'simple_history.registry_tests.migration_test_app.migrations' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'simple_history.registry_tests.migration_test_app.migrations' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

C:\Users\toqp\AppData\Local\Temp\pip-build-env-bq_rns37\overlay\Lib\site-packages\setuptools\command\build_py.py:153: SetuptoolsDeprecationW
arning:     Installing 'simple_history.templates.simple_history' as data is deprecated, please list it in packages.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'simple_history.templates.simple_history' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'simple_history.templates.simple_history' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'simple_history.templates.simple_history' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

C:\Users\toqp\AppData\Local\Temp\pip-build-env-bq_rns37\overlay\Lib\site-packages\setuptools\command\build_py.py:153: SetuptoolsDeprecationW
arning:     Installing 'simple_history.tests' as data is deprecated, please list it in packages.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'simple_history.tests' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'simple_history.tests' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'simple_history.tests' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

C:\Users\toqp\AppData\Local\Temp\pip-build-env-bq_rns37\overlay\Lib\site-packages\setuptools\command\build_py.py:153: SetuptoolsDeprecationW
arning:     Installing 'simple_history.tests.custom_user' as data is deprecated, please list it in packages.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'simple_history.tests.custom_user' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'simple_history.tests.custom_user' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'simple_history.tests.custom_user' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

C:\Users\toqp\AppData\Local\Temp\pip-build-env-bq_rns37\overlay\Lib\site-packages\setuptools\command\build_py.py:153: SetuptoolsDeprecationW
arning:     Installing 'simple_history.tests.external' as data is deprecated, please list it in packages.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'simple_history.tests.external' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'simple_history.tests.external' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'simple_history.tests.external' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

C:\Users\toqp\AppData\Local\Temp\pip-build-env-bq_rns37\overlay\Lib\site-packages\setuptools\command\build_py.py:153: SetuptoolsDeprecationW
arning:     Installing 'simple_history.tests.tests' as data is deprecated, please list it in packages.
!!
  ############################
  # Package would be ignored #
  ############################
  Python recognizes 'simple_history.tests.tests' as an importable package,
  but it is not listed in the `packages` configuration of setuptools.

  'simple_history.tests.tests' has been automatically added to the distribution only
  because it may contain data files, but this behavior is likely to change
  in future versions of setuptools (and therefore is considered deprecated).

  Please make sure that 'simple_history.tests.tests' is included as a package by using
  the `packages` configuration field or the proper discovery methods
  (for example by using `find_namespace_packages(...)`/`find_namespace:`
  instead of `find_packages(...)`/`find:`).

  You can read more about "package discovery" and "data files" on setuptools
  documentation page.

!!
check.warn(importable)

creating build\lib\simple_history\locale
creating build\lib\simple_history\locale\cs_CZ
creating build\lib\simple_history\locale\cs_CZ\LC_MESSAGES
copying simple_history\locale\cs_CZ\LC_MESSAGES\django.mo -> build\lib\simple_history\locale\cs_CZ\LC_MESSAGES
copying simple_history\locale\cs_CZ\LC_MESSAGES\django.po -> build\lib\simple_history\locale\cs_CZ\LC_MESSAGES
creating build\lib\simple_history\locale\de
creating build\lib\simple_history\locale\de\LC_MESSAGES
copying simple_history\locale\de\LC_MESSAGES\django.mo -> build\lib\simple_history\locale\de\LC_MESSAGES
copying simple_history\locale\de\LC_MESSAGES\django.po -> build\lib\simple_history\locale\de\LC_MESSAGES
creating build\lib\simple_history\locale\fr
creating build\lib\simple_history\locale\fr\LC_MESSAGES
copying simple_history\locale\fr\LC_MESSAGES\django.mo -> build\lib\simple_history\locale\fr\LC_MESSAGES
copying simple_history\locale\fr\LC_MESSAGES\django.po -> build\lib\simple_history\locale\fr\LC_MESSAGES
creating build\lib\simple_history\locale\pl
creating build\lib\simple_history\locale\pl\LC_MESSAGES
copying simple_history\locale\pl\LC_MESSAGES\django.mo -> build\lib\simple_history\locale\pl\LC_MESSAGES
copying simple_history\locale\pl\LC_MESSAGES\django.po -> build\lib\simple_history\locale\pl\LC_MESSAGES
creating build\lib\simple_history\locale\pt_BR
creating build\lib\simple_history\locale\pt_BR\LC_MESSAGES
copying simple_history\locale\pt_BR\LC_MESSAGES\django.mo -> build\lib\simple_history\locale\pt_BR\LC_MESSAGES
copying simple_history\locale\pt_BR\LC_MESSAGES\django.po -> build\lib\simple_history\locale\pt_BR\LC_MESSAGES
creating build\lib\simple_history\locale\ru_RU
creating build\lib\simple_history\locale\ru_RU\LC_MESSAGES
copying simple_history\locale\ru_RU\LC_MESSAGES\django.mo -> build\lib\simple_history\locale\ru_RU\LC_MESSAGES
copying simple_history\locale\ru_RU\LC_MESSAGES\django.po -> build\lib\simple_history\locale\ru_RU\LC_MESSAGES
creating build\lib\simple_history\registry_tests
copying simple_history\registry_tests_init_.py -> build\lib\simple_history\registry_tests
copying simple_history\registry_tests\models.py -> build\lib\simple_history\registry_tests
copying simple_history\registry_tests\tests.py -> build\lib\simple_history\registry_tests
creating build\lib\simple_history\registry_tests\migration_test_app
copying simple_history\registry_tests\migration_test_app_init_.py -> build\lib\simple_history\registry_tests\migration_test_app
copying simple_history\registry_tests\migration_test_app\models.py -> build\lib\simple_history\registry_tests\migration_test_app
creating build\lib\simple_history\registry_tests\migration_test_app\migrations
copying simple_history\registry_tests\migration_test_app\migrations\0001_initial.py -> build\lib\simple_history\registry_tests\migration_tes
t_app\migrations
copying simple_history\registry_tests\migration_test_app\migrations\0002_historicalmodelwithcustomattrforeignkey_modelwithcustomattrforeignk
ey.py -> build\lib\simple_history\registry_tests\migration_test_app\migrations
copying simple_history\registry_tests\migration_test_app\migrations\0003_alter_historicalmodelwithcustomattrforeignkey_options_and_more.py -

build\lib\simple_history\registry_tests\migration_test_app\migrations
copying simple_history\registry_tests\migration_test_app\migrations\0004_history_date_indexing.py -> build\lib\simple_history\registry_tests
\migration_test_app\migrations
copying simple_history\registry_tests\migration_test_app\migrations\0005_historicalmodelwithcustomattronetoonefield_modelwithcustomattroneto
onefield.py -> build\lib\simple_history\registry_tests\migration_test_app\migrations
error: could not create 'build\lib\simple_history\registry_tests\migration_test_app\migrations\0005_historicalmodelwithcustomattronetoonefie
ld_modelwithcustomattronetoonefield.py': No such file or directory

ERROR: Failed building wheel for django-simple-history
Failed to build django-simple-history
ERROR: Could not build wheels for django-simple-history which use PEP 517 and cannot be installed directly

Anyone that knows the source of this problem?

To add in a bit of info:

Pip failed building wheel for django-simple-history==3.1.1 on windows. The following is the the last output I also get:
error: could not create 'build\lib\simple_history\registry_tests\migration_test_app\migrations\0002_historicalmodelwithcustomattrforeignkey_modelwithcustomattrforeignkey.py': No such file or directory
Issue does not occur on 3.0.0 (installs without any issue, has wheel available).

Is it possible to add a wheel next to the source dist in PYPI?

This might be related to the max path length limitation in Windows, but I'm not entirely sure 🤔
Closing, as the error doesn't seem to happen anymore. Please reopen if it's still an issue 🙂


Make Kivy apps accessible, add kivy.core.accessibility abstraction for accessibility providers

In the last few days, I had the chance to chat with one of the https://github.com/AccessKit/accesskit core developers, regarding accessibility in Kivy.
For the last decade, Kivy has evolved quite a lot but never officially supported accessibility features (even if users have succeded in adding such features by themself).
In our vision to make Kivy a solid platform to build Apps for everyone, introducing accessibility features and making Kivy apps accessible by default has become increasingly important.
Kivy 3.0.0 is the right moment to break things and make the appropriate changes to allow accessibility tools to do their job, when they need to.
Even if we will work closely with AccessKit team (as they already have a POC, and offered to write an implementation for their tool in Kivy), Kivy will have an abstraction that will make it possible for other accessibility tools to add their implementation in future.
The plan:
### Tasks
- [ ] https://github.com/kivy/kivy/issues/8597
- [ ] https://github.com/kivy/kivy/issues/8598
- [ ] https://github.com/kivy/kivy/issues/8599
- [ ] https://github.com/kivy/kivy/issues/8600
- [ ] https://github.com/kivy/kivy/issues/8601

Here's the proof of concept thanks to @DataTriny.

@DataTriny and @clayote :
I've just finished the first draft of all the tasks linked to this issue.
With no rush, when you have some time, can you please proofread it and share your thoughts?
(mainly https://github.com/kivy/kivy/issues/8599)


TypeError: Cannot read property 'errors' of undefined

I have used the<EMAIL_ADDRESS>without the package @openzeppelin/upgrades-core when I deploy an upgradable contract some weeks ago。I create a new project with my contracts code and take this errors：
TypeError: Cannot read property 'errors' of undefined
    at /Users/work/allan/node_modules/@openzeppelin/truffle-upgrades/node_modules/@openzeppelin/upgrades-core/src/validate/query.ts:109:58
    at Array.map (<anonymous>)
    at getErrors (/Users/work/allan/node_modules/@openzeppelin/truffle-upgrades/node_modules/@openzeppelin/upgrades-core/src/validate/query.ts:109:26)
    at Object.assertUpgradeSafe (/Users/work/allan/node_modules/@openzeppelin/truffle-upgrades/node_modules/@openzeppelin/upgrades-core/src/validate/query.ts:13:16)
    at deployProxy (/Users/work/allan/node_modules/@openzeppelin/truffle-upgrades/src/deploy-proxy.ts:49:3)
    at processTicksAndRejections (node:internal/process/task_queues:94:5)
    at module.exports (/Users/work/allan/migrations/10_mdxpool_deploy.js:8:24)
    at Migration._deploy (/usr/local/lib/node_modules/truffle/build/webpack:/packages/migrate/Migration.js:80:1)
    at Migration._load (/usr/local/lib/node_modules/truffle/build/webpack:/packages/migrate/Migration.js:61:1)
    at Migration.run (/usr/local/lib/node_modules/truffle/build/webpack:/packages/migrate/Migration.js:218:1)
    at Object.runMigrations (/usr/local/lib/node_modules/truffle/build/webpack:/packages/migrate/index.js:150:1)
    at Object.runFrom (/usr/local/lib/node_modules/truffle/build/webpack:/packages/migrate/index.js:110:1)
    at runMigrations (/usr/local/lib/node_modules/truffle/build/webpack:/packages/core/lib/commands/migrate.js:253:1)
    at Object.run (/usr/local/lib/node_modules/truffle/build/webpack:/packages/core/lib/commands/migrate.js:223:1)
    at Command.run (/usr/local/lib/node_modules/truffle/build/webpack:/packages/core/lib/command.js:147:1)

I have change all the packets to the same version with my old project ,but still occured the same error?
how Can I do not use this @openzeppelin/upgrades-core packages? OR fix this errors?
Thank you

my system options :
Truffle v5.3.8 (core: 5.3.8)
Solidity - 0.6.12 (solc-js)
Node v15.9.0
Web3.js v1.3.6

runable truffle packages:
{
  "name": "[hardhat-project](https://npmjs.com/package/hardhat-project)",
  "devDependencies": {
    "[@nomiclabs/hardhat-ethers](https://npmjs.com/package/@nomiclabs/hardhat-ethers)": "^2.0.1",
    "[@nomiclabs/hardhat-waffle](https://npmjs.com/package/@nomiclabs/hardhat-waffle)": "^2.0.1",
    "[@openzeppelin/hardhat-upgrades](https://npmjs.com/package/@openzeppelin/hardhat-upgrades)": "^1.6.0",
    "[@openzeppelin/truffle-upgrades](https://npmjs.com/package/@openzeppelin/truffle-upgrades)": "^1.5.0",
    "[chai](https://npmjs.com/package/chai)": "^4.3.0",
    "[ethereum-waffle](https://npmjs.com/package/ethereum-waffle)": "^3.2.2",
    "[ethers](https://npmjs.com/package/ethers)": "^5.0.31",
    "[hardhat](https://npmjs.com/package/hardhat)": "^2.0.10"
  },
  "dependencies": {
    "[@openzeppelin/contracts](https://npmjs.com/package/@openzeppelin/contracts)": "^3.4.0",
    "[@openzeppelin/contracts-upgradeable](https://npmjs.com/package/@openzeppelin/contracts-upgradeable)": "^3.4.0",
    "[@openzeppelin/upgrades-core](https://npmjs.com/package/@openzeppelin/upgrades-core)": "^1.5.0",
    "[@pancakeswap/pancake-swap-lib](https://npmjs.com/package/@pancakeswap/pancake-swap-lib)": "^0.0.4",
    "[@truffle/hdwallet-provider](https://npmjs.com/package/@truffle/hdwallet-provider)": "^1.4.0",
    "[truffle-hdwallet-provider](https://npmjs.com/package/truffle-hdwallet-provider)": "^1.0.17"
  }
}

Hello @zhangliang7190
@openzeppelin/upgrades-core is an internal "library" that is used by @openzeppelin/truffle-upgrades and @openzeppelin/hardhat-upgrades. You should not have to deal with it directly.
Can you share the line of script that, when called, triggers this error ?

Note that you are not using the latest version of the upgrades plugin.
I would encourage you to save a backup of your .openzeppelin folder, upgrade to the latest version of the plugin (@openzeppelin/truffle-upgrades:1.7.0) and see it that fixes anything.

Note that you are not using the latest version of the upgrades plugin.
I would encourage you to save a backup of your .openzeppelin folder, upgrade to the latest version of the plugin (@openzeppelin/truffle-upgrades:1.7.0) and see it that fixes anything.

I think that is my contracts's problem. I have to try it. tks


Delete AWS Lambda functions created by tests regularly

Our AWS Lambda test suite is creating real Lambda functions in AWS.
We need a Lambda function that runs every Sunday that will remove all Lambda functions named test_*.
Run Lambda function ever X days:
https://stackoverflow.com/questions/56979740/how-to-run-aws-lambda-every-6-hours
Delete Lambda function from Python SDK:
https://docs.aws.amazon.com/lambda/latest/dg/example_lambda_DeleteFunction_section.html

We have a bash script that does this: https://github.com/getsentry/sentry-python/blob/master/scripts/aws-cleanup.sh
So maybe we can just invoke this in an AWS Lambda function (or somewhere else)


android emulator is closed because of an internal error gpu found id 10de device id 0x1f99

Type: Bug
open gls emulation failed to initalize . please consider the following troubleshooting steps
VS Code version: Code 1.72.0 (64bbfbf67ada9953918d72e1df2f4d8e537d340e, 2022-10-04T23:20:39.912Z)
OS version: Windows_NT x64 10.0.22621
Modes:
Sandboxed: No

Please file the issue with reproducable steps. Until that is done I am going to go ahead and close this.


hashcat: 6.2.4 -> 6.2.5

Motivation for this change
Update to latest upstream release 6.2.5
Change log: https://github.com/hashcat/hashcat/releases/tag/v6.2.5
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality 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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 147701 run on x86_64-linux 1

2 packages built:

hashcat
wifite2

Result of nixpkgs-review pr 147701 run on x86_64-linux 1

2 packages built:

hashcat
wifite2


Replacedjquery

Coverage decreased (-2.4%) to 72.064% when pulling 8686495b14fc65b1d476fcbde18c7f3de2987fe8 on replacedjquery into 2de33135810143f28e3fc027c835fa5d97d959f4 on master.


FAILED TO CORRESPOND

Hello booth:
When I run "lsfm -i ./test  -o ./out", An error occurred: FAILED TO CORRESPOND: 'LandmarkGroup' object has no attribute 'from_mask'. What's wrong, Please give me some tips. Thanks.

+1 , facing the same issue. @anny0316  did you find any fix for this ?

@jabooth Hi Booth, I have the same issue.  Do you know why? Thanks.

@patricksnape +1. I face the same issue. Do you have some advices?

I fixed it by upgrading menpo to desired versions: menpo==0.8 menpo3d==0.6 menpofit==0.5 menpodetect==0.5


[UPDATE] update to minecraft 1.20.4

i have updated the mod to minecraft 1.20.4
i have no ideia how to create a pull request here (github.com) but i have a pull request ready-to-go on InteliJ
i am available anytime to do so
Regards

Sorry for my absence in this discussion. There is a 1.20.4 version available on CurseForge and Modrinth.


Last questions xD Sorry, I know I'm asking too much

Now I am able to see the icons on the website, but can I see the stats? If yes, tell me how to do it xD
And it would be also nice if u could finish the unique history because I need it ^^

history you can find @ https://github.com/PServerCMS/SROUnique but its in testing history works also, just  in ranking will be some changes.
about the stats its not added in default ranking, you have to add your own logic or ask other ppl to add these part


Gateset Decomposition by level

It would be nice to have the ability to specify different decomposition or different decomposition 'levels' (ie, we want to keep toffolis, or want to keep rotations, or want to keep something else).
We could imagine specifying a target gateset to decompose , which we can imagine being done by either by having multiple different decomposition methods, or via flags that are passed
Is this something that is already on the roadmap or could be added?

Bloq.flatten() is closest to what you want. It takes a max_depth argument as well as a pred (predicate) argument. The predicate takes a bloq instance and returns True if it should be decomposed and flattened or False if it should be left alone