Where am I getting instant leech from?

I've been looking for a while, but I don't know where I'm getting the instant leech from. I have no Vall Pact, no Acuity, no Legacy Vinktars: https://pastebin.com/f51ppRw1

The program cannot calculate the hit rate for spells triggered by CoC yet, so they are displayed in Average Damage mode. Since the hit rate is required to calculate your leech rate, when in Average Damage mode the program instead shows the average life leeched from each hit. In your case that number is quite big, so you'd presumably be at your leech cap (1218 per second) at all times, but the program can't know that.


Extracting crop coordinates rather than encoding output in AutoFlip

Hi, I was hoping to re-utilise/re-adapt AutoFlip so to obtain coordinates of the resulting crops, rather than the actual cropped video output. I've had a look at #454 but it seems like the solution is specific to Android and hand tracking where different calculators are used.
By inspecting the AutoFlip graph on the mediapipe visualizer (amazing tool btw, thank you for this), what this basically means is that I'm not interested in running OpenCvVideoEncoderCalculator and am instead interested in the output from SceneCroppingCalculator. This however simply outputs a set of frames, a list of image matrices (vectorcv::Mat), which are meant for encoding by OpenCV if I understand correctly.

I was hoping to go one step earlier, i.e., simply get the actual coordinates of the crop regions. What I'm ideally hoping to output is a file listing the coordinates of the crop frames and their relevant timestamps, something like [[x, y, w, h, timestamp]].
I'm having trouble determining exactly how to do this. I'm unsure where exactly the transformation from crop coordinates to cropped images (i.e. the cropping) occurs. I believe it occurs here.
I imagine this means the data I'm actually interested in is contained in the SceneKeyFrameCropSummary scene_summary, but since this does not contain FocusPoint information, this will leave me with the jittery output if I'm not mistaken.
It seems therefore that I need to edit/replace scene_cropper.cc with something that takes into account FocusPointFrames too.
It also seems like there are additional operations performed on the cv::Mat images before returning such as an affine retarget.
In general, it is unclear to me how to readapt AutoFlip for my needs described above.
Is what I'm seeking feasible? Perhaps a user with more experience in mediapipe can shine a light
Thank you very much, apologies if this sort of question is inappropriate for the issues page

is it the all_xforms vector returned by PolynomialRegressionPathSolver::ComputeCameraPath that I am essentially after? From the docstring in polynomial_regression_solver.h :

The returned |all_xforms| hold the camera location at each timestamp corresponding to each input frame.

width and height I realize is trivial. So in fact what I am after is [[x, y, timestamp]] which this seems to provide.
That being said I notice in scene_cropper.cc that as mentioned above, it seems like there are further operations performed on the image frames themselves, particularly here with AffineRetarget. I'm unsure what is happening with AffineRetarget, is this simply preparing the frames for OpenCV video encoding in the next calculator or is it part of the AutoFlip cropping process?
Thank you in advance

The |all_xforms| vector, particularly elements (0,2) and (1,2) corresponding to the (x, y) position of the camera was indeed what I was after. I'm still not sure what AffineRetarget does afterwards, but I guess it is not relevant to what I'm seeking.
Anyone interested in my (shoddy) readaptation, come have a look at my fork and/or feel free to ask


Python-Markdown 3.4 has been released and makes resume.md buggy

Python-Markdown 3.4 has been released and makes the build fails.
It works well if I set the dependency back to version 3.3.7: pip install markdown==3.3.7.

I'm not sure this is a bug in python-markdown. If you have a look at the release note, you can see that:

Previously deprecated objects have been removed
Various objects were deprecated in version 3.0 and began raising deprecation warnings (see the version 3.0 release notes for details). Any of those objects which remained in version 3.3 have been removed from the code base in version 3.4 and will now raise errors. The relevant objects are listed below.

resume.py does not reference any of those deprecated objects.
If the problem you're reporting is not https://github.com/Python-Markdown/markdown/issues/1274 then please write a meaningful description of the problem so I have some idea what you're talking about. "buggy" and "build fails" are not meaningful descriptions.

Issue seems to be fixed with markdown-3.4.1:
> # pip install markdown
Collecting markdown
  Downloading Markdown-3.4.1-py3-none-any.whl (93 kB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 93.3/93.3 KB 1.1 MB/s eta 0:00:00
Installing collected packages: markdown
Successfully installed markdown-3.4.1
WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv
WARNING: You are using pip version 22.0.4; however, version 22.1.2 is available.
You should consider upgrading via the '/usr/local/bin/python -m pip install --upgrade pip' command.
root@8d15f5222285:/# cd lab/
root@8d15f5222285:/lab# python3 resume.py
Wrote /lab/resume.html
Found Chrome or Chromium at /usr/bin/google-chrome
[0715/192003.607145:ERROR:bus.cc(398)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
[0715/192003.607248:ERROR:bus.cc(398)] Failed to connect to the bus: Failed to connect to socket /run/dbus/system_bus_socket: No such file or directory
Wrote /lab/resume.pdf


how to use the new models in huggingface

i cannot use the new model in huggingface ,because i pip the newest docling version, and i found that we can only use

You should rely on the tagged releases of the models in HuggingFace. See here https://github.com/DS4SD/docling/issues/567#issuecomment-2535365591


Yolo integration QAT compatibility fixes

PyTorch does not support QAT pickling or half precision. These fixes address those issues

@markurtz agreed. The minimal integration for pruning is still a few lines. A lot of the changes introduced here are due to unsupported features in QAT that could be simplified based on how future pytorch releases look.


Visual rust crashes msbuild while building in VS 2017

Downloaded latest VS 2017 related build from Appveyor, from here:
https://ci.appveyor.com/project/vosen/visualrust/build/artifacts
(built from master, f005c247)

Installed it on Visual Studio 2017 Community.
It is a clean installation (installed it just yesterday) , and the only Visual Studio installed on my OS.

I have both stable and beta rust installed, both of them build the project from step (4) correctly.
The default one is beta (but I also tried changing the default to stable and it happened).

Opened a toml file for a small project which it opened correctly.

When pressing build project, msbuild.exe crashed.

Attaching to it from another instance of VS 2017, I saw the following exception:

Exception

System.NullReferenceException.

Local variables in the crash point
(LogRustcMessage method, see stack trace below), as seen in the attached VS 2017 "locals" window:

  msg	         null	                                               VisualRust.Shared.Message.RustcMessageJson
  rootPath	"C:\\Users\\orvly\\rust\\blogposts"	      string
  log	        {Microsoft.Build.Utilities.TaskLoggingHelper}	Microsoft.Build.Utilities.TaskLoggingHelper

I looked at the source code for ExecuteCargo, and tried looking at the locals in the anonymous closure from ExecuteCargo but they were optimized and VS 2017 won't let me see them.  My dotnet debugging foo isn't that strong :-)   So I can't tell you why the message is null.
Stack trace :

VisualRust.Build.dll!VisualRust.Build.Rustc.LogRustcMessage(VisualRust.Shared.Message.RustcMessageJson msg, string rootPath, Microsoft.Build.Utilities.TaskLoggingHelper log)	Unknown
VisualRust.Build.dll!VisualRust.Build.CargoBuild.ExecuteCargo.AnonymousMethod__4_1(object sender, System.Diagnostics.DataReceivedEventArgs e)	Unknown
System.dll!System.Diagnostics.Process.OutputReadNotifyUser(string data)	Unknown
System.dll!System.Diagnostics.AsyncStreamReader.FlushMessageQueue()	Unknown
System.dll!System.Diagnostics.AsyncStreamReader.GetLinesFromStringBuilder()	Unknown
System.dll!System.Diagnostics.AsyncStreamReader.ReadBuffer(System.IAsyncResult ar)	Unknown
mscorlib.dll!System.IO.Stream.ReadWriteTask.InvokeAsyncCallback(object completedTask)	Unknown
mscorlib.dll!System.Threading.ExecutionContext.RunInternal(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state, bool preserveSyncCtx)	Unknown
mscorlib.dll!System.Threading.ExecutionContext.Run(System.Threading.ExecutionContext executionContext, System.Threading.ContextCallback callback, object state, bool preserveSyncCtx)	Unknown
mscorlib.dll!System.IO.Stream.ReadWriteTask.System.Threading.Tasks.ITaskCompletionAction.Invoke(System.Threading.Tasks.Task completingTask)	Unknown
mscorlib.dll!System.Threading.Tasks.Task.FinishContinuations()	Unknown
mscorlib.dll!System.Threading.Tasks.Task.FinishStageThree()	Unknown
mscorlib.dll!System.Threading.Tasks.Task.FinishStageTwo()	Unknown
mscorlib.dll!System.Threading.Tasks.Task.Finish(bool bUserDelegateExecuted)	Unknown
mscorlib.dll!System.Threading.Tasks.Task.ExecuteWithThreadLocal(ref System.Threading.Tasks.Task currentTaskSlot)	Unknown
mscorlib.dll!System.Threading.Tasks.Task.ExecuteEntry(bool bPreventDoubleExecution)	Unknown
mscorlib.dll!System.Threading.Tasks.Task.System.Threading.IThreadPoolWorkItem.ExecuteWorkItem()	Unknown

This looks like the same crash that I've fixed in https://github.com/PistonDevelopers/VisualRust/pull/286/commits/6323a84b3f329a131dabac36547acdc0315913f1 - that pull request hasn't been reviewed yet unfortunately.
If you're feeling particularly brave, I've got appveyor running against my (hopefully temporary) fork too.  Not only has nobody from the project has reviewed my changes - I haven't even tested the appveyor produced binaries - only my own locally built VS2015 ones!  But hey, they might work?
https://ci.appveyor.com/project/MaulingMonkey/visualrust/build/job/bgfigmcko2211nin/artifacts
If you do want to try it out, you'll want to uninstall the previous version (twice! via Visual Studio's "Extensions and Updates", and then via Windows's "Programs and Features") before installing mine.

Thanks, that did it, it works perfectly now in VS2017!  Including compiling, running and debugging.
I'll close this issue I guess, even though this isn't yet part of the official build.  But then again neither is the VS2017 build I downloaded in the first place.
There was one more problem though - all the files in the project initially appeared, but then disappeared after saving the sln file which VS generated for me.  I had to enable "Show All Files" in the solution in order to see them.  I'm not sure if that's a bug or a feature though, and I haven't read through the other issues to see if that's a known one.
Also, racer doesn't quite work for autocomplete - it always gives me the same generic completions regardless of context.  But again I'm not sure if it's supposed to work or not since this build doesn't seem to be official and all...  I'll try to dig into it later if I'll have time.

There was one more problem though - all the files in the project initially appeared, but then disappeared after saving the sln file which VS generated for me. I had to enable "Show All Files" in the solution in order to see them. I'm not sure if that's a bug or a feature though, and I haven't read through the other issues to see if that's a known one.

That's a bug.  One I haven't encountered so far - my Cargo.lock/toml shows up fine, as do my files in src/.  It's only if I want to see target/ as well, that I need to enable Show All Files.  Might see if the "Visual Rust" dropdown category in your Output tab shows anything interesting, since some of the project stuff is logged to there.

Also, racer doesn't quite work for autocomplete - it always gives me the same generic completions regardless of context. But again I'm not sure if it's supposed to work or not since this build doesn't seem to be official and all... I'll try to dig into it later if I'll have time.

I've been working to improve intellisense results in that branch, but I've been using a cargo-supplied racer instead of the Visual Rust bundled one, even since before I began my work IIRC.  The bundled racer might just be in need of an update?  Keywords will generally always show up in all contexts, even where they don't make sense, as well.

The link (https://ci.appveyor.com/project/MaulingMonkey/visualrust/build/job/bgfigmcko2211nin/artifacts) doesn't have any artifacts. Should I just use the latest succeeding build?


Update DatasetCoreFactory to match Dataset Factory

DatasetFactory accepts both a DataSet and an array of Quads, while DatasetCoreFactory only has an array of Quads. Note that this is correct according to the spec (https://rdf.js.org/dataset-spec/#datasetcorefactory-interface), but I would argue that consistency is better.

I'm not sure. I think we should try to be true to the spec. I see that Dataset#addAll indeed accepts an array as well as another dataset instance so we might align the two first.
On the other hand changing the constructor could be a potential breaking change for implementations which strictly accept only arrays


minor fixes

pretty self explanatory, found both because console were pointing the errors.

the fix for the "bug" on navbar (pushed quite after my last comment) I found when trying to add a bigger image to it

@paolotripodi - Can you pull this when you get a chance?

@cauerego sorry for delayed answer, so much work :) thanks for your fixes!

I'm really glad they helped! :)


Entity List View-select dropdown display name/translations not working

I'n been working with ADX/MicrosoftCRMPortals for a long time already and this is been an issue for quite some time.
When configuring the Entity List you add on or more predefined views to be available in the portal. In doing you, when you choose 'advanced' it will allow for a 'Display Name' for each pre-configured portal language to mask the default 'View' name from CRM. I'd like to give these CRM Views dedicated for the portal a name that will allow the  CRM users and system admins to easily recognize the purpose of that specific view, like 'PORTAL: My open ...; . This advanced but readily available configuration feature would allow me to do so without the Portal users being able to see this Portal-prefix.
But for this feature is not working at this time (and as long as I can remember)

What is it I am missing about this feature?

Hi @Edwin-VC, please reach out to support team with a service request for investigation on this issue.


[DO NOT MERGE] LLM-based crash triaging

Experiment based on the idea from #221 and more.

/gcbrun exp -n dg

/gcbrun exp -n dg

@fdt622 the experiment is running at here.
Do you have access to the report, btw?

@fdt622 the experiment is running at here. Do you have access to the report, btw?

No, I do not have the access.

/gcbrun exp -n dg -f

Not sure why the previous exp did not launch successfully, retrying ...

/gcbrun exp -n dg -f

/gcbrun exp -n dg-bug -f -b bug

Incorrect triage:

rediscommand has incorrect triage:

The fuzz target did check 'the return value of redisFormatCommand', the triage says otherwise. We can try providing the erroneous line in the fixer prompt.

No triage:
https://llm-exp.oss-fuzz.com/Result-reports/ofg-pr/2024-06-13-252-dg-comparison/sample/output-libarchive-archive_entry_linkify/05
Correct triage:

archive_entry_linkify. LLM can probably even fix the error given the triage.

JOB: https://console.cloud.google.com/kubernetes/job/us-central1-c/llm-experiment/default/ofg-pr-252-dg-bug
REPORT: https://llm-exp.oss-fuzz.com/Result-reports/ofg-pr/2024-06-13-252-dg-bug-bug/index.html

Incorrect triage:

rediscommand has incorrect triage:

The fuzz target did check 'the return value of redisFormatCommand', the triage says otherwise. We can try providing the erroneous line in the fixer prompt.

No triage: https://llm-exp.oss-fuzz.com/Result-reports/ofg-pr/2024-06-13-252-dg-comparison/sample/output-libarchive-archive_entry_linkify/05
Correct triage:

archive_entry_linkify. LLM can probably even fix the error given the triage.

Hi, I have fixed the no triage problem in #374. Besides, I slice code and point out concrete code line in the prompt.

Thanks @fdt622 !
Could you please 1) resolve the merge conflict on this PR (#252), 2) rebase this PR on the main branch, and 3) rebase #374 on this PR?
Sorry that you have to go through this trouble but I noticed that #374 contains code changes from other PRs (e.g., modifying ci/k8s/pr-exp.yaml), which is caused by:

This PR (#252) is not up-to-date with main
The new PR (#374) is based on newer commits in main
Hence, Github misinterprets those new commits from main as part of #374, which makes it difficult to reviewing and will lead to confusing conflicts when merged into this PR.

If rebasing #374 is too complicated, this is probably simpler:

resolve the merge conflict on this PR (#252),
rebase this PR on the main branch,
Get the new commits in #374 with git reflog
Create a new branch and git cherry-pick those new commits.

I also created a clean branch/PR with the latest main in #375.
Feel free to use it (or test merging into it) if you like.

Thanks @fdt622 ! Could you please 1) resolve the merge conflict on this PR (#252), 2) rebase this PR on the main branch, and 3) rebase #374 on this PR?
Sorry that you have to go through this trouble but I noticed that #374 contains code changes from other PRs (e.g., modifying ci/k8s/pr-exp.yaml), which is caused by:

This PR ([DO NOT MERGE] LLM-based crash triaging #252) is not up-to-date with main
The new PR (Enhance LLM-based crash triaging with project function code #374) is based on newer commits in main
Hence, Github misinterprets those new commits from main as part of Enhance LLM-based crash triaging with project function code #374, which makes it difficult to reviewing and will lead to confusing conflicts when merged into this PR.

If rebasing #374 is too complicated, this is probably simpler:

resolve the merge conflict on this PR ([DO NOT MERGE] LLM-based crash triaging #252),
rebase this PR on the main branch,
Get the new commits in Enhance LLM-based crash triaging with project function code #374 with git reflog
Create a new branch and git cherry-pick those new commits.

Thank you for your explanation @DonggeLiu, I have resolve the conflict on #252 and rebase #252 on main branch, see #376

Thank you for your explanation @DonggeLiu, I have resolve the conflict on #252 and rebase #252 on main branch, see #376

Thanks for looking into this so quickly!
But it seems that #376 still has merge conflicts : )
BTW, seeing other people's commit in your PR is normally a bad sign for 'something went wrong':

Thank you for your explanation @DonggeLiu, I have resolve the conflict on #252 and rebase #252 on main branch, see #376

Thanks for looking into this so quickly! But it seems that #376 still has merge conflicts : )
BTW, seeing other people's commit in your PR is normally a bad sign for 'something went wrong':

Hi @DonggeLiu , I have closed #376 and #374, sorry for submitting other's commit in my PR. Based on #375, I have resolved the conflict on #252 and rebase #252 on main branch, see #379. After #379 is merged, I would rebase #374 on #379. Thanks!

Thank you for your explanation @DonggeLiu, I have resolve the conflict on #252 and rebase #252 on main branch, see #376

Thanks for looking into this so quickly! But it seems that #376 still has merge conflicts : )
BTW, seeing other people's commit in your PR is normally a bad sign for 'something went wrong':

Hi @DonggeLiu , I have closed #376 and #374, sorry for submitting other's commit in my PR. Based on #375, I have resolved the conflict on #252 and rebase #252 on main branch, see #379. After #379 is merged, I would rebase #374 on #379. Thanks!

clear other's commit in my pr, all rebase done, see #379.

Superseded by #375.


Bridge Effect Not Working for Tiles (Foundry v11)

Not sure the Elevation settings are working correctly for tiles on v11, since the bridge effect doesn't seem to be functioning as intended. It fades correctly, but doesn't maintain the token's height when walked on, no matter what elevation the token starts from. I'm including screenshots of the settings, but at this point I must have tested just about every possible permutation of relevant setting combinations, elevation ranges for the scene's Levels (with/without overlapping ranges), using walls, not using walls, walls with various combinations of heights, and even different image formats for the tile art. The video showing a bridge on the Elevated Vision page doesn't show what settings are used to make that one work, so I have no idea what I'm doing wrong, if anything.
Ground elevation itself seems to be working fine. It adjusts tokens as expected, but just doesn't seem to care that a tile with an elevation is present under a token, dropping it to the base elevation level.

Thanks for the screenshots! Very helpful. Should be fixed in v0.5.5. But please let me know if it is not.

Thanks, king

Works now, but with a couple minor issues:

A tile has to cover >50% of a grid square with opaque pixels in order to not drop a token.
The first time a token attempts to walk on a 'bridge', it will fall through, though subsequent tokens maintain their elevation just fine.

That second one may be fixed with some settings changes, as I'm sure it began after I changed a few things while experimenting to get the bridge working. Will update when I find out what caused it.


Separated folders

[ ] I think my problem is NOT with youtube-dl
[ x] I've verified and i assure that I'm running youtube-dl-gui 0.4
[ x] I assure that i am using the latest version of youtube-dl
[ x] Searched bugtracker
[ x] I've read the FAQs file

Hello
IFAIK it is not possible to separate videos to a different folders depending on the channel's name? Can I ask you to implement this feature in your GUI version of youtube-dl?
Thanks
Example: save folder/channel_name1, save folder/channel_name2, etc

You can use the %(chapter)s_%(chapter_number)s in the "filename format" field.

What do you mean? In output/custom template or commands? Its not working for me, still saves the video into 1 folder without separation

The %(chapter)s_%(chapter_number)s is wrong, excuse me.
You should use something like that %(uploader)s/%(title)s.%(ext)s
In order to use a custom template just go to "General" tab and select "Custom" under the "Filename format" field. Then you can paste you own output template in the box below.

Much obliged, you are my hero! :-)

Hello
One more question please: can I download 1080p video+best audio and then convert them to 720p with 2pass vbr and lets say 128 aac for better image quality/bitrate and less space (automatically) using ffmpeg? And how to limit the bitrate/framerate in that case?


Expected in: /usr/lib/libc++.1.dylib

When debug iOS11.3.1 and startup crash log:
dyld: Symbol not found: __ZTISt18bad_variant_access
Referenced from: /var/containers/Bundle/Application/3908D51F-C774-421C-93B9-A3502128F938/Runner.app/Runner
Expected in: /usr/lib/libc++.1.dylib
in /var/containers/Bundle/Application/3908D51F-C774-421C-93B9-A3502128F938/Runner.app/Runner
and flutter doctor -v：

reproduce:
Add mobile_scanner to pubspec.yaml
debug for iOS11.3.1 failed, and iOS14-iOS16 passed.

I can reproduce too on iOS 11.2.6

It work fine in version 2.1.0


Text numFmt

Is there a "Text" type for number format? I can't see it nowhere

Found the answer in this guide.
for text: numFmt: '@'

this is very helpful!


updated docker stuff, added vscode devcontainer

Idk if your secret key thing was working but it got commented out you should be able to do that through docker exec...

Having issues with using dev containers in vscode on arch linux:
[2023-02-28T08:14:48.873Z] Start: Run: docker version --format {{.Server.APIVersion}}
[2023-02-28T08:14:49.022Z] Stop (149 ms): Run: docker version --format {{.Server.APIVersion}}
[2023-02-28T08:14:49.023Z] 1.42
[2023-02-28T08:14:49.044Z] Start: Run: /opt/visual-studio-code/code --ms-enable-electron-run-as-node /home/mkapral/.vscode/extensions/ms-vscode-remote.remote-containers-0.275.1/dist/spec-node/devContainersSpecCLI.js read-configuration --workspace-folder /home/mkapral/GitHub/Shoe-Expert --log-level debug --log-format json --config /home/mkapral/GitHub/Shoe-Expert/.devcontainer/devcontainer.json --include-merged-configuration --mount-workspace-git-root true
[2023-02-28T08:14:49.290Z] (node:253658) [DEP0005] DeprecationWarning: Buffer() is deprecated due to security and usability issues. Please use the Buffer.alloc(), Buffer.allocUnsafe(), or Buffer.from() methods instead.
[2023-02-28T08:14:49.290Z] (Use `code --trace-deprecation ...` to show where the warning was created)
[2023-02-28T08:14:49.293Z] @devcontainers/cli 0.29.0. Node.js v16.14.2. linux 6.1.12-arch1-1 x64.
[2023-02-28T08:14:49.293Z] Start: Run: docker ps -q -a --filter label=devcontainer.local_folder=/home/mkapral/GitHub/Shoe-Expert
[2023-02-28T08:14:49.343Z] Stop (50 ms): Run: docker ps -q -a --filter label=devcontainer.local_folder=/home/mkapral/GitHub/Shoe-Expert
[2023-02-28T08:14:49.343Z] Command failed: docker ps -q -a --filter label=devcontainer.local_folder=/home/mkapral/GitHub/Shoe-Expert
[2023-02-28T08:14:49.348Z] Stop (304 ms): Run: /opt/visual-studio-code/code --ms-enable-electron-run-as-node /home/mkapral/.vscode/extensions/ms-vscode-remote.remote-containers-0.275.1/dist/spec-node/devContainersSpecCLI.js read-configuration --workspace-folder /home/mkapral/GitHub/Shoe-Expert --log-level debug --log-format json --config /home/mkapral/GitHub/Shoe-Expert/.devcontainer/devcontainer.json --include-merged-configuration --mount-workspace-git-root true
[2023-02-28T08:14:49.348Z] Exit code 1

Initially I thought it was a problem with the vscode docker extension, but I added the DOCKER_HOST env variable to the extension's settings pointing to unix:///run/user/1000/docker.sock as I use docker in rootless, and the container doesn't build still. The log shows that a docker ps ... command fails, but it executes code 0 when I run it manually. Not sure yet what the issue is, any suggestions?
It seems to build fine on my mac, but I haven't tried much else there.

The ways I would recommend interacting with the app IMO

Docker compose up (with or without a -d flag based on personal preference
Docker compose down ( must be in the folder with the compose.yml for this to work)
or use vscode to build and run a devcontainer with the command palette (need remote extension pack for this to work)

I'm thinking that using the command palette in vscode is going to be easiest for everyone. That requires the remote extension as well as dev-containers extension in vscode?

Is docker compose up/down similar to docker start and docker stop?

IF you have resolved this with a vscdoe settings I recommend adding it to the .devcontainer config

If you have resolved this with a vscode settings I recommend adding it to the .devcontainer config

I'm pretty sure it was an issue with my docker setup locally since I didn't have the issue on macOS

I'm thinking that using the command palette in vscode is going to be easiest for everyone. That requires the remote extension as well as dev-containers extension in vscode?

Yep. yeah it is the simplest way to interact...with it automatically stops it for you to...
Most of the time a popup will come up prompting to open it...just gotta teach users how to tell they are actually in the container....
a side note if you add docker as a plugin for oh-my-zsh  you get a bunch of docker aliases like dcup = docker compose up  dcdn = docker compose down`.

Oh that's neat. I use the plugin for systemd, but I'll have to add the docker one to my zshrc

Your cake just needed some icing. :P


Deploy Fuel Block Commiter Helm Chart

We need to helmify the fuel block commiter and deploy to DEV cluster

@Voxelot  - assigned to you


Lode center contribution and Madelung tests

Adding a center_atom_weight parameter similarly to SOAP.
With this we can also add the Madelung tests for LODE. However with the current set of SphericalExpansionParameters I ran into missing block panicks.
thread 'calculators::lode::spherical_expansion::tests::madelung' panicked at 'missing block', rascaline/src/calculators/lode/spherical_expansion.rs:580:28

This seems to related to the small atomic_gaussian_width and cutoff.

Right, this is wrong:
https://github.com/Luthaf/rascaline/blob/f389e9048f12e57981b266f826df45e8e537f40d/rascaline/src/calculators/lode/spherical_expansion.rs#L313-L317
CenterSingleNeighborsSpeciesKeys will only generate a key species_1, species_2 if there is a neighbors with species_2 around a center with species_1, which is not what we need for LODE. We will need to change this to use all the species pairs in the system instead.

Ohh yes I will take a look. Thanks!


Fast paths for strings, likely boolean and likely objects for opcodes CmEq_A, CmNeq_A, CmSrEq_A and CmSrNeq_A

We have fast paths for equivalent Br* opcodes so I refactored the code
and reused it for Cm* opcodes. Basically Cm* opcodes behave as branch
where we store success if equal otherwise false in destination.

@LouisLaf please take a look

:shipit:


⚠ Catalog API Endpoint has degraded performance

In 2d201f0, Catalog API Endpoint (https://catalog.roblox.com/v1/bundles/details?bundleIds=192) experienced degraded performance:

HTTP code: 200
Response time: 4485 ms

Resolved: Catalog API Endpoint performance has improved in 1fe0d5b.


Escape $(...) in cheatsheets

docker rm -f $(docker ps -aq) will execute docker ps -aq when selected in FZF ⚠

Escape backticks as well

Maybe replacing the escaped double quotes here by escaped single quotes will fix the issue: https://github.com/denisidoro/navi/blob/dev/src/ui.sh#L22.
I'm not sure about side-effects of this change, though.

Fixed in the dev branch already.
While there's no another release, please run navi from the dev branch or run brew install --HEAD denisidoro/tools/navi-nightly to see the changes.


Undefined variables in helpers/function.py and main.py files

Sure @ShamanthVallem , go ahead and make a PR :))

made a PR #89


功能挺好的, 就是代码需要精简一些...

例如:
cellForItemAtIndexPath方法里, 其实除了 monthInfo 不一样之外, 其余的处理都是一模一样的, 为什么不抽离出来成一个函数呢.
    if (collectionView == _collectionViewL) {

        [self configCell:cell withMonthInfo:self.monthArray[0] atIndexPath:indexPath];

    }
    else if (collectionView == _collectionViewM) {

        [self configCell:cell withMonthInfo:self.monthArray[1] atIndexPath:indexPath];

    }
    else if (collectionView == _collectionViewR) {
        [self configCell:cell withMonthInfo:self.monthArray[2] atIndexPath:indexPath];
    }

另外我觉得还有一个需要注意的是, 没有必要在 monthArray 里面增加一个 NSNumber, 如果只是为了标识出前一个月份的天数, 直接写一个属性会更安全一些, 也容易理解.
个人意见, :-)

嗯，我也一直想找时间优化一下代码，很多地方写的可能不是很好，谢谢反馈

AltLayer Airdrop Season One Announcement

Exciting news! AltLayer token (ALT) is set to launch on Binance on January 25, 2024. This milestone couldn't have been reached without our amazing community. Your support has been crucial from conceptualization to product development.
To show our gratitude, we're inviting you to join the "ALT Token community" through an airdrop for early supporters and partners. Below is a summary:

Total Allocated ALT Tokens: 300,000,000 (3% of total supply)
Distribution Categories:

NFT Holders
Altitude Campaign Participants
EigenLayer Restakers
EigenLayer Ecosystem Partners
Celestia Stakers and others

For detailed criteria and information, check the full announcement here.
Claim opens from January 25 to February 25, 2024. Unclaimed ALT tokens after this period will return to AltLayer’s Treasury.
Thank you for being part of AltLayer's success! More to come in Season One, stay tuned.
Note: Certain regions are restricted from the airdrop. Please review the disclaimer before participating.
Winners: @insane-dev, @czars, @ericwali, @p768lwy3, @kos9kus, @rengokantai, @pragkent, @chai2010, @NecatiAlperen, @Dannyzheng831, @thonglinhma, @zyrikin, @globalYK, @stelabouras, @JaredHalpern, @the-x-man, @itaa, @JedWatson, @devxsby, @hbzs


Branch1

Withdrawn

hi @mnemonic01, your keys are still visible. I'll strongly urge you to change those keys if you haven't done so already.

Hi, the branch doesn't exist anymore however I don't have permissionto remove the update historyin the pull request so could you please remove the entire pull request? Thanks


Units are now paused in post-game screen

Post game all units are paused and turned invulnerable.
In order to ensure that no units are trained - in case the game is reset - the ownership of all buildings are also temporarily changed to another player and back to the original owner. This resets the training queue.
Invulnerability is necessary to prevent neutral units and buildings from attacking paused players in the post game.
These are cleaned up in the reset procedure. All units are resumed and invulnerability is turned off.

@dtchitt that is of course one option. The problem I am trying to solve though is to stop everything in the game. This includes unit movements (visible movements in the corners and via the minimap), unit training and related noises, attack pings on the map, etc. It goes further than just removing sound.

Ah okay I thought you were just worried about sounds. Okay Ill need to get someone to help me test to make sure it doesnt lead to any issues in restarts

Actually I was able to test just now, one problem this causes barracks/ports to be vulnerable on restarts. I would suggest skipping over structures when setting them invulnerable and vulnerable. I believe the unit queue corruption is not going to be an issue with the way you did it. I was not able to produce the bug in my testing. Keep in mind, its been a long time since I dealt with this bug so I may be testing for it wrong. If it comes up we will know its from this.

Ah, I totally forgot about that. I can make a fix for that to tomorrow evening.
This PR can wait for another patch release, since it is a purely UX improvement.
But if you want this in now, you can adjust it yourself, by filtering away buildings in the unpausing all units function.

I might do it tonight if I have time to sit down and work on, I gotta do the unit count tracking still as well

Alright, I added a filter to ensuring only non-buildings are made vulnerable again.
I also rearranged the resume functionality to occur later in the process.


[BUG]

Compensate with donations ($5 and more) for the time I spent to fix problems or send  me your Pull Request with fixes

Bitcoin: 3KHgnvNNWio6wyQ71cgNeBQojXStxzkzfd
Ethereum: 0x6e644c6b975B47801072b07a9a57DDfEC10DE74F
https://paypal.me/adw0rd
https://www.patreon.com/adw0rd
https://www.buymeacoffee.com/adw0rd
For Russia: СБП, Qiwi и тп: +79118107609

Describe the bug
I ran the docker image and I only see 2 options in the API

To Reproduce
I ran the docker image by docker run -p 8000:8000 adw0rd/instagrapi-rest
Desktop (please complete the following information):

OS: Windows 10

Updated https://hub.docker.com/repository/docker/adw0rd/instagrapi-rest


perf(cli):perf log

Codecov Report
Patch coverage: 100.00% and no project coverage change.

Comparison is base (0c3e42f) 100.00% compared to head (d83e3b6) 100.00%.

Additional details and impacted files
@@            Coverage Diff            @@
##              main      #213   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files           35        35
  Lines         4761      4765    +4
=========================================
+ Hits          4761      4765    +4

Impacted Files
Coverage Δ

megfile/cli.py
100.00% <100.00%> (ø)

megfile/s3_path.py
100.00% <100.00%> (ø)

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


Beautify ckcp

Hey @Roming22, thanks for the PR.
I saw code duplication of gitops-operator subscription resource while having a look at Bharath's work yesterday. I was hoping to remove this from /ckcp once his PR is merged and then raise this PR. I'm ok with making these changes later too.

LGTM.


Issue with "Could not retrieve index file"

When running talon with the example data I received the following errors, is this a known issue?
(py3.10) patrickmacknight@MacBook-Pro example % talon
--f config.csv
--db example_talon.db
--build SIRV --o example
[ 2023-09-27 01:12:14 ] Started TALON run
[ 2023-09-27 01:12:15 ] Merged input SAM/BAM files
[ 2023-09-27 01:12:15 ] Split reads into 7 intervals
[ 2023-09-27 01:12:16 ] Launching parallel annotation jobs
[ 2023-09-27 01:12:16 ] Annotating reads in interval SIRV1:1000-11644...
[E::idx_find_and_load] Could not retrieve index file for 'talon_tmp/interval_files/SIRV1_1000_11644.bam'
[ 2023-09-27 01:12:16 ] Annotating reads in interval SIRV2:999-5911...
[E::idx_find_and_load] Could not retrieve index file for 'talon_tmp/interval_files/SIRV2_999_5911.bam'
[ 2023-09-27 01:12:16 ] Annotating reads in interval SIRV3:998-9943...
[E::idx_find_and_load] Could not retrieve index file for 'talon_tmp/interval_files/SIRV3_998_9943.bam'
[ 2023-09-27 01:12:16 ] Annotating reads in interval SIRV4:1000-15123...
[E::idx_find_and_load] Could not retrieve index file for 'talon_tmp/interval_files/SIRV4_1000_15123.bam'
[ 2023-09-27 01:12:16 ] Annotating reads in interval SIRV5:1001-13607...
[E::idx_find_and_load] Could not retrieve index file for 'talon_tmp/interval_files/SIRV5_1001_13607.bam'
[ 2023-09-27 01:12:16 ] Annotating reads in interval SIRV6:1000-11839...
[E::idx_find_and_load] Could not retrieve index file for 'talon_tmp/interval_files/SIRV6_1000_11839.bam'
[ 2023-09-27 01:12:16 ] Annotating reads in interval SIRV7:1000-147958...
[E::idx_find_and_load] Could not retrieve index file for 'talon_tmp/interval_files/SIRV7_1000_147958.bam'
multiprocessing.pool.RemoteTraceback:
"""
Traceback (most recent call last):
File "/Users/patrickmacknight/opt/miniconda3/envs/py3.10/lib/python3.10/multiprocessing/pool.py", line 125, in worker
result = (True, func(*args, **kwds))
File "/Users/patrickmacknight/opt/miniconda3/envs/py3.10/lib/python3.10/multiprocessing/pool.py", line 51, in starmapstar
return list(itertools.starmap(args[0], args[1]))
File "/Users/patrickmacknight/opt/miniconda3/envs/py3.10/lib/python3.10/site-packages/talon/talon.py", line 2137, in parallel_talon
unpack_observed(annotation_info, queue,
File "/Users/patrickmacknight/opt/miniconda3/envs/py3.10/lib/python3.10/site-packages/talon/talon.py", line 2335, in unpack_observed
obs_ID = observed_counter.increment()
NameError: name 'observed_counter' is not defined
"""
The above exception was the direct cause of the following exception:
Traceback (most recent call last):
File "/Users/patrickmacknight/opt/miniconda3/envs/py3.10/bin/talon", line 10, in
sys.exit(main())
File "/Users/patrickmacknight/opt/miniconda3/envs/py3.10/lib/python3.10/site-packages/talon/talon.py", line 2451, in main
pool.starmap(parallel_talon, jobs)
File "/Users/patrickmacknight/opt/miniconda3/envs/py3.10/lib/python3.10/multiprocessing/pool.py", line 375, in starmap
return self._map_async(func, iterable, starmapstar, chunksize).get()
File "/Users/patrickmacknight/opt/miniconda3/envs/py3.10/lib/python3.10/multiprocessing/pool.py", line 774, in get
raise self._value
NameError: name 'observed_counter' is not defined

Check out my answer to #137 here: https://github.com/mortazavilab/TALON/issues/137#issuecomment-1758290250
I'm hoping this solves the issue.

I tested this behavior and found that I was able to reproduce your issue with Python >= 3.8, as the Stackoverflow thread I found suggested. I have now included <3.8 as a Python dependency in the installation requirements in the latest release. Please try installing with this version and see if this fixes your issue!


docs: mkcloud: Start the virtlogd service on new installations

When using the mkcloud on a new host, starting the libvirt daemon alone
will not start the virtlogd service which leads to the following problem:
libvirt: QEMU Driver error : Domain not found: no domain with matching name 'cloud-admin'
libvirt: XML-RPC error : Failed to connect socket to '/var/run/libvirt/virtlogd-sock': No such file or directory
Traceback (most recent call last):
File "/root/mchandras/automation/scripts/lib/libvirt/vm-start", line 16, in
main()
File "/root/mchandras/automation/scripts/lib/libvirt/vm-start", line 12, in main
libvirt_setup.vm_start(args)
File "/root/mchandras/automation/scripts/lib/libvirt/libvirt_setup.py", line 377, in vm_start
dom.create()
File "/usr/lib64/python2.7/site-packages/libvirt.py", line 1035, in create
if ret == -1: raise libvirtError ('virDomainCreate() failed', dom=self)
libvirt.libvirtError: Failed to connect socket to '/var/run/libvirt/virtlogd-sock': No such file or directory
This is because the libvirtd service file does not start virtlogd but it
simply installs it so it can start automatically on the next reboot.
Signed-off-by: Markos Chandras<EMAIL_ADDRESS>

IMHO it would be nicer to have this (additionally) as code in the setuphost section of mkcloud, if this is needed. The goal is to make setting up a cloud as easy as possible.

@bmwiedemann I have updated the code as requested.

@hwoarang can you rebase?
After that feel free to merge: +1

I did a quick fixup in 58165d5e86617179e6b13734b53b77e7415b5a86
the return value of service virtlogd start became the return value of the libvirt_do_setuphost function which made the whole run fail on non-SP2 hosts.


feat: Add multiple missing spells

What does this do?
Add missing spells:
-Friends
-Toll the Dead
-Blade Ward
-Dissonant Whisper
-Cloud of Dagger
-Crown of Madness
Is there a Github issue this is resolving?
No
Did you update the docs in the API? Please link an associated PR if applicable.
No

Unfortunately, none of these spells are in the D&D 5e SRD, and therefore we can't legally distribute this content as part of the API.
You're of course welcome to maintain a private fork of the API for personal use containing any additional content that you own, but we won't be able to merge this PR, I'm afraid. Sorry to be the bearer of bad news!


Python: Value Error : Function with name '{func.name}' already exists in plugin '{plugin_name} for chat prompt with messages

Describe the bug
From 0.5.0dev, I received the error Value Error : Function with name '{func.name}' already exists in plugin '{plugin_name}. And it is from the duplication check when calling kernel.register_semantic_function().
I have a scenario where each request would pair with a historic messages, so I am using the code below for the registering the semantic chat function:
req_settings = AzureChatPromptExecutionSettings(
            max_tokens=2000,
            temperature=0,
            messages=messages,
            extension_data={"chat_system_prompt": self.system_message},
        )
        config = PromptTemplateConfig(
            execution_settings=req_settings,
            description="Pass in question and relevant context, you will get the answer relevant to the context",
            default_services=["azure_openai_chat4_service"],
        )
        template = ChatPromptTemplate(
            template=self.propmt_template,
            template_engine=kernel.prompt_template_engine,
            prompt_config=config,
            parse_chat_system_prompt=True,
            parse_messages=True,
        )
        function_config = SemanticFunctionConfig(config, template)
        return kernel.register_semantic_function(
            "rag", "qa_with_context", function_config
        )

Since each request has different messages, and the only way right now to construct the messages is through the setting configuration above. so each request will register the semantic function, which caused the duplication check error.
To Reproduce
Running the above code twice in a session would have the error
Expected behavior

Expose a remove plugin/function so that I could explicitly call it before register.
Pass the messages attributes when invoking the function, so that I could register the function once and just calling it with messages parameter

It seems now, none of the above is provided.
Screenshots
If applicable, add screenshots to help explain your problem.
Platform

OS: Windows
IDE:  VS Code
Language: Python
Source: 0.5.1dev

Additional context
Add any other context about the problem here.

I finally found there is a function called
kernel.plugins.remove_by_name() can remove it and prevent from having the exception. But posted here to see if messages could be passed as parameter when invoking the function and only register the function once.

Hi @HuskyDanny, in #5077, your life should be a lot easier given the scenario you're working with. We've introduced a chat history class, which you will be able to pass in to the kernel invoke and the first/subsequent runs of a function.


Height affecting ground primitive polygon rendering

What happened?
I'm currently creating a GroundPolylinePrimitive using GroundPolylineGeometry, as well as a GroundPrimitive that uses a PolygonGeometry to "fill" the polyline. I'm giving both the GroundPolylineGeometry and GroundPrimitive the same positions, however the polygon shape does not seem to match the polyline. See the attached screenshot:

I've previously worked from a fork of cesium at version 1.99.0 in which the positions of the polygon do correctly "fill" the polyline. For example here is a screenshot running locally of the same scenario as the linked sandbox but with cesium version 1.99:

Here's the code for this example running at cesium v1.99.0:
var Cesium = require('cesium/Cesium');
var viewer = new Cesium.Viewer('cesiumContainer');

const cartographics = [
    {
      "longitude": -1.8402495415863134,
      "latitude": 0.7033934337801941,
      "height": 2177.974000000284
    },
    {
      "longitude": -1.8402506824369915,
      "latitude": 0.7033901872332414,
      "height": 2177.9740000000156
    },
    {
      "longitude": -1.840249836934684,
      "latitude": 0.703388112597783,
      "height": 2177.9739999988838
    },
    {
      "longitude": -1.8402478059109948,
      "latitude": 0.7033903665805613,
      "height": 2177.9739999987028
    },
    {
      "longitude": -1.840246112964614,
      "latitude": 0.7033920799454119,
      "height": 2177.9739999996555
    },
    {
      "longitude": -1.8402467855800173,
      "latitude": 0.7033933442953648,
      "height": 2177.9740000006414
    },
    {
      "longitude": -1.8402495415863134,
      "latitude": 0.7033934337801941,
      "height": 2177.974000000284
    }
  ];

const { WGS84 } = Cesium.Ellipsoid;

const positions = WGS84.cartographicArrayToCartesianArray(cartographics);

const c = Cesium.Color.fromCssColorString('#ffe566');

const polygonGeometryInstance = new Cesium.GeometryInstance({
    geometry: new Cesium.PolygonGeometry({
        polygonHierarchy: {
            positions,
        },
    }),
    attributes: {
        color: new Cesium.ColorGeometryInstanceAttribute(
            c.red,
            c.green,
            c.blue,
        ),
    },
});

const polygonPrimitive = new Cesium.GroundPrimitive({
    geometryInstances: polygonGeometryInstance,
    appearance: new Cesium.PerInstanceColorAppearance({
        closed: true,
        translucent: true,
    }),
});

const lineGeometryInstance = new Cesium.GeometryInstance({
    geometry: new Cesium.GroundPolylineGeometry({
        positions,
        loop: false,
        width: 3.0,
    }),
});

const linePrimitive = new Cesium.GroundPolylinePrimitive({
    geometryInstances: [lineGeometryInstance],
    appearance: new Cesium.PolylineMaterialAppearance({
        material: Cesium.Material.fromType('Color', {
            color: c,
        }),
    }),
});

viewer.scene.primitives.add(polygonPrimitive);
viewer.scene.primitives.add(linePrimitive);

viewer.scene.camera.flyTo({destination: positions[0]});

Interestingly when using cartographics with zeroed height they seem to match up (note this sandbox).
How is height intended to affect a ground primitive? Is this a regression, or expected behaviour?
Reproduction steps

Create a ground primitive using polygon geometry, and a ground polyline primitive using ground polyline geometry using the same positions in example sandbox/code snippet
Note that they don't quite match up

...
Sandcastle example
https://sandcastle.cesium.com/#c=tVZbb5tIFP4ryPsQLLljYLgMrhNtZK26lbpqpVS7D3EeJjC2Rx0zaGZI5Eb+73vAYANx7FhqeYE55zuH71whkZk21hNnz0xZ11bGnq0Z07xYo38rmT0fJNV5JjNDecbUfDD8OM/mWVJZJlQZuVQ0X/FEg4P7eWbB9bK7WdZ8IGS25KZI2XwwsT64iPiO58eB7wYkxC72Ry0oNXukgyIH4xj7GEfEcWPfbQFXjC9XpoR5bhShOPKd6vKIvwNtR+/iETgh8XwcxrEbnObhuCTyMPZ8138HD8cNwouI+DEBFtgPyel8EOK6XhBHEcGnaOC4vAghmFxGA1IdxK4Txz45kw8chgGAQ/c9RCKozGVEQogzDuF2pj88JwKy0E1ufJ5HHAZBcCGPiAQQp+NG+EyjYt/34gCHncy91SAh9NGFDfK7J6a8PbQm+8X679Md8a0tTHW9Ev4Sguda8rQFy6XmhsMjwCoD1F4Jt0rRzXc5AxG4oFl1tjtL47BNpGBIyKW9d9lZNAcaMymkQgsl1zOtq8OdUTxb2ld/LBYsCMOrYYeg2Cxl9onJNTNq8xlkNEtYd9n1tXZdjmUtn7TB37oe7X3prOZlf3OmqEpWYNdS7gB1bKODvGmB7XBUFas6UAMxPRaQto6PpAy3w6ZKQJ//bWNtd1+fIMXSUV+2VIxlr6SPomAt4XB0aNjtkQR/U3wNoT31M6tkkaV7ZT+xDWGI8o1C1a+lec6oKgXdWjDVAKtE3O5h7bIkQmqWTiyjOiEZAGpRJCwzHd122I9RwJfvF3ZQnRQIuO2420iv+0RImU+sBRW6HcQzT81qYmHknGR/ujw1k/eU6f5YLh7OVKn2/w81THEqjldpXWsnjVkDr2b9+yZn9lVV5KtRf6zqsUjaUzU8ko/djw7SUHKG8iZajWia2v0+Li1O4TsJe73FOqYJXcNGOMJhp0ALAVvSfkmZNjyjZeEnhxa4dx5q+oPRYKrNRrCbJs4/+TqXyliFEjZCY8PWOXwTmB4/FskPZlCiqy1aQqfjtuk05U8WT6+P/N/BuFCtQbMohLjjP+HrcjMdA/6VqZA0hcX79YkpQTclbOXefNkJEULTMRyPWxopxSNVPc//Aw
Environment
Browser: Chrome 121.0.6167.160
CesiumJS Version: 1.115
Operating System: Mac OS 13.5

Hi @r-edwards, thanks for reporting this issue!
The 1.110 release included some significant changes to how we handle polygon rendering. This does appear to be a regression.

@r-edwards thanks for reporting, I can second the behaviour change as we are seeing the same regression when we tested upgrading from 1.105 to 1.113 recently. In our testing it seems at least until 1.116 polygons behave as reported.
@ggetz is there an update on if this will be addressed or a possible workaround in the meantime? Many thanks in advance.