An error occurred during the fetch of repository 'rules_python'

System information

OS Platform and Distribution (e.g., Linux Ubuntu 20.04, WSL2):window10
Target (e.g. desktop cpu, android arm64):desktop cpu
Bazel version:3.7.2
Python version:3.9.7
Unity version:2020.3.16

Describe the problem
When I run the command:python build.py build --desktop cpu --include_opencv_libs -v,it can not build successfully
Steps to reproduce the issue
python build.py build --desktop cpu --include_opencv_libs -v
Full logs
E:\UnityProJects\MediaPipeUnityPlugin-master>python build.py build --desktop cpu --include_opencv_libs -v
INFO (build.py): Building protobuf sources...
DEBUG (build.py): Running bazel --host_jvm_args "-DsocksProxyHost=<IP_ADDRESS>" --host_jvm_args "-DsocksProxyPort=7890" --output_user_root C:/_bzl build -c opt --action_env PYTHON_BIN_PATH="C://Users//shengyilai//AppData//Local//Programs//Python//Python39//python.exe" --action_env ProgramData --action_env PROCESSOR_ARCHITECTURE --action_env PROCESSOR_IDENTIFIER --action_env PROCESSOR_LEVEL --action_env PROCESSOR_REVISION //mediapipe_api:mediapipe_proto_srcs
WARNING: Running Bazel server needs to be killed, because the startup options are different.
Starting local Bazel server and connecting to it...
DEBUG: C:/_bzl/sqzb2w22/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'com_google_absl' because it already exists.
DEBUG: C:/_bzl/sqzb2w22/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'com_google_protobuf' because it already exists.
DEBUG: C:/_bzl/sqzb2w22/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'com_google_googletest' because it already exists.
DEBUG: C:/_bzl/sqzb2w22/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'com_github_gflags_gflags' because it already exists.
DEBUG: C:/_bzl/sqzb2w22/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'rules_python' because it already exists.
DEBUG: C:/_bzl/sqzb2w22/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'build_bazel_rules_apple' because it already exists.
DEBUG: C:/_bzl/sqzb2w22/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'build_bazel_rules_swift' because it already exists.
DEBUG: C:/_bzl/sqzb2w22/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'build_bazel_apple_support' because it already exists.
DEBUG: C:/_bzl/sqzb2w22/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'bazel_skylib' because it already exists.
DEBUG: C:/_bzl/sqzb2w22/external/org_tensorflow/third_party/repo.bzl:108:14:
Warning: skipping import of repository 'pybind11' because it already exists.
DEBUG: C:/_bzl/sqzb2w22/external/tf_runtime/third_party/cuda/dependencies.bzl:51:10: The following command will download NVIDIA proprietary software. By using the software you agree to comply with the terms of the license agreement that accompanies the software. If you do not agree to the terms of the license agreement, do not use the software.
INFO: Repository rules_python instantiated at:
E:/unityprojects/mediapipeunityplugin-master/WORKSPACE:41:23: in
C:/_bzl/sqzb2w22/external/rules_pkg/deps.bzl:33:10: in rules_pkg_dependencies
C:/_bzl/sqzb2w22/external/bazel_tools/tools/build_defs/repo/utils.bzl:201:18: in maybe
Repository rule git_repository defined at:
C:/_bzl/sqzb2w22/external/bazel_tools/tools/build_defs/repo/git.bzl:199:33: in
ERROR: An error occurred during the fetch of repository 'rules_python':
Traceback (most recent call last):
File "C:/_bzl/sqzb2w22/external/bazel_tools/tools/build_defs/repo/git.bzl", line 181, column 30, in _git_repository_implementation
update = _clone_or_update(ctx)
File "C:/_bzl/sqzb2w22/external/bazel_tools/tools/build_defs/repo/git.bzl", line 36, column 20, in clone_or_update
git = git_repo(ctx, directory)
File "C:/_bzl/sqzb2w22/external/bazel_tools/tools/build_defs/repo/git_worker.bzl", line 91, column 12, in git_repo
_update(ctx, git_repo)
File "C:/_bzl/sqzb2w22/external/bazel_tools/tools/build_defs/repo/git_worker.bzl", line 103, column 10, in _update
fetch(ctx, git_repo)
File "C:/_bzl/sqzb2w22/external/bazel_tools/tools/build_defs/repo/git_worker.bzl", line 136, column 13, in fetch
_git(
File "C:/_bzl/sqzb2w22/external/bazel_tools/tools/build_defs/repo/git_worker.bzl", line 169, column 15, in _git
_error(ctx.name, start + list(args), st.stderr)
File "C:/_bzl/sqzb2w22/external/bazel_tools/tools/build_defs/repo/git_worker.bzl", line 190, column 9, in _error
fail("error running '%s' while working with @%s:\n%s" % (command_text, name, stderr))
Error in fail: error running 'git fetch origin refs/heads/:refs/remotes/origin/ refs/tags/:refs/tags/' while working with @rules_python:
fatal: unable to access 'https://github.com/bazelbuild/rules_python.git/': Failed to connect to github.com port 443: Timed out
ERROR: E:/unityprojects/mediapipeunityplugin-master/mediapipe_api/BUILD:175:8: //mediapipe_api:mediapipe_proto_srcs depends on @rules_pkg//:build_zip in repository @rules_pkg which failed to fetch. no such package '@rules_python//python': error running 'git fetch origin refs/heads/:refs/remotes/origin/ refs/tags/:refs/tags/' while working with @rules_python:
fatal: unable to access 'https://github.com/bazelbuild/rules_python.git/': Failed to connect to github.com port 443: Timed out
ERROR: Analysis of target '//mediapipe_api:mediapipe_proto_srcs' failed; build aborted: Analysis failed
INFO: Elapsed time: 268.110s
INFO: 0 processes.
FAILED: Build did NOT complete successfully (12 packages loaded, 10 targets configured)
currently loading: @rules_pkg//
Traceback (most recent call last):
File "E:\UnityProJects\MediaPipeUnityPlugin-master\build.py", line 445, in
Argument().command().run()
File "E:\UnityProJects\MediaPipeUnityPlugin-master\build.py", line 112, in run
self._run_command(self._build_proto_srcs_commands())
File "E:\UnityProJects\MediaPipeUnityPlugin-master\build.py", line 52, in _run_command
return subprocess.run(' '.join(command_list), check=True, shell=shell)
File "C:\Users\shengyilai\AppData\Local\Programs\Python\Python39\lib\subprocess.py", line 528, in run
raise CalledProcessError(retcode, process.args,
subprocess.CalledProcessError: Command 'bazel --host_jvm_args "-DsocksProxyHost=<IP_ADDRESS>" --host_jvm_args "-DsocksProxyPort=7890" --output_user_root C:/_bzl build -c opt --action_env PYTHON_BIN_PATH="C://Users//shengyilai//AppData//Local//Programs//Python//Python39//python.exe" --action_env ProgramData --action_env PROCESSOR_ARCHITECTURE --action_env PROCESSOR_IDENTIFIER --action_env PROCESSOR_LEVEL --action_env PROCESSOR_REVISION //mediapipe_api:mediapipe_proto_srcs' returned non-zero exit status 1.
Additional context
I have followed mediapipe's installation guide and install MSYS2, Python, Visual C++ Build Tools 2019, WinSDK and Bazel(step1 ~ step6) and build the example successfully,and i update the commands ['bazel'] with ["bazel", "--host_jvm_args", ""-DsocksProxyHost=<IP_ADDRESS>"", "--host_jvm_args", ""-DsocksProxyPort=7890""] so that it is not a proxy problem,please help,thanks.

Is there any way I can get the face rotation angles?

Basically, I don't want you to ask me how to use MediaPipe itself here (ask it in MediaPipe community instead), but I think you can get these values by examining the slope of the line segment connecting two specific landmarks (e.g. Left ear to Right ear, Top of the head to the tip of the chin, etc...).

Ok, thanks. I will figure it out.


sap.m.Popover header border misaligned in light themes

OpenUI5 version: 1.124, but older versions are also affected
Browser/version (+device/version): latest firefox, chrome
Any other tested browsers/devices(OK/FAIL): -
URL (minimal example if possible): sample
User/password (if required and possible - do not post any confidential information here): -
Steps to reproduce the problem:

Open the sample for edit
Replace the content of view/Popover.fragment.xml with the following code:

<core:FragmentDefinition
	xmlns="sap.m"
	xmlns:core="sap.ui.core"
	xmlns:l="sap.ui.layout">
	<Popover>
	    <customHeader>
			<l:VerticalLayout
			    width="10rem"
			>
			</l:VerticalLayout>
		</customHeader>
	</Popover>
</core:FragmentDefinition>

Click on the Show Popover button

What is the expected result?
It should display a popover with the gray line inside the popover.
What happens instead?
The gray line is rendered outside of the popover.
Any other information? (attach screenshot if possible)

Affects both Quartz Light and Morning Horizon themes.

Hello @bfopta,
Thank you for sharing this finding. I've created an internal incident DINC0173393. The status of the issue will be updated here in GitHub.
Regards,
Niya

Hi,
Instead of Horizontal/VerticalLayout, you can use HBox/VBox like here:
<core:FragmentDefinition
	xmlns="sap.m"
	xmlns:core="sap.ui.core"
	xmlns:l="sap.ui.layout">
	<Popover>
	    <customHeader>
			<VBox
			    width="10rem"
			>
			   <Text text="text" />
			</VBox>
		</customHeader>
	</Popover>
</core:FragmentDefinition>

Best,
Teo


Extending the Ingredient class

in order to be able to implement add/remove/replace functionality in vr.cli.

Looks great. In the future, consider including an entry in CHANGES.rst.

Sure, I didn't want to bump the version number or amend a changelist as I wasn't sure if this should be done by the maintainer after accepting PR or by me. Will do next time!


Add PowerOutput Component

We need a component to represent the power outputs on the power board.
Another nice things would be a neat way to group them together.

Required features:

Set on/off state
Get current measurement


B15.0 dLDD Integration & Test

[x] Generate and Deliver Discipline LDDs for I&T
[x] Discipline LDD Review (dLDD Stewards Teams)
[ ] Discipline LDD Freeze

📆 10/2024 status: delayed a couple weeks, but no impact on build expected.

All LDDs built and delivered to DD Stewards for review. End date pushed back to 12/4 to give sufficient time to review

Done. dLDD review and merge phase complete.


feature request: render output in Rust

Thanks for the awesome crate. A feature request that I think would be a great addition to this API:
The current output format (text lines) work well for simple diffs, but as APIs get bigger/more complicated, it is much harder to follow/navigate. See an example here: https://github.com/NomicFoundation/slang/pull/1081/
I suggest supporting a Rust format for the output? Using the same Rust syntax, omitting function bodies, and nesting items inside their respective modules recursively?
This would have the following benefits:

Allow syntax highlighting in editors and in GitHub during code review.
Have folding/collapse, outline view, and many more editor features.
Support formatting using rustfmt.
Output would be much more concise, as we don't have to use FQNs everywhere.
The recursive structure makes it much easier to read/reason about large APIs, or ignore irrelevant parts.
We can also add the documentation markdown above each item as /// comments, so that doc changes are reflected in the diff.

Example, replacing the existing one in: https://github.com/cargo-public-api/cargo-public-api/blob/main/public-api/tests/expected-output/example_api-v0.2.0-omit_blanket_impls.txt
pub mod example_api {
    #[non_exhaustive]
    pub struct Struct {
        pub v1_field: usize,
        pub v2_field: usize,
    }

    impl Struct {
        pub fn fmt(&self, f: &mut core::fmt::Formatter<'_>) -> core::fmt::Result {}
    }

    impl core::fmt::Debug for Struct {}
    impl core::marker::Freeze for Struct {}
    impl core::marker::Send for Struct {}
    impl core::marker::Sync for Struct {}
    impl core::marker::Unpin for Struct {}
    impl core::panic::unwind_safe::RefUnwindSafe for Struct {}
    impl core::panic::unwind_safe::UnwindSafe for Struct {}

    pub struct StructV2 {
        pub field: usize,
    }

    impl core::marker::Freeze for StructV2 {}
    impl core::marker::Send for StructV2 {}
    impl core::marker::Sync for StructV2 {}
    impl core::marker::Unpin for StructV2 {}
    impl core::panic::unwind_safe::RefUnwindSafe for StructV2 {}
    impl core::panic::unwind_safe::UnwindSafe for StructV2 {}

    pub fn function(v1_param: Struct, v2_param: usize) {}
}

How would this show removed fields/imports/impls?

How would this show removed fields/imports/impls?

@Emilgardis do you mean for the output of cargo public-api diff?
I don't mind its current "individual lines" display is great for showing added/removed items. It doesn't necessarily have to support the new format, if you think the current one is better. Otherwise, I can suggest looking at delta or difftastic, as both render beautiful diffs for code with syntax highlighting in the terminal, including added/removed ranges. And IIRC, they are both written in Rust.
Btw, for our own use cases, we don't use the diff command, and instead use the editor diff viewer itself when the snapshot changes, or we use the tools above for diffing in the CLI. That works well with both formats.


Even more error handling with new error types

What type of PR is this?
/kind feature
What this PR does / why we need it:
Finalizing error handling refactoring
Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #1869
Does this PR introduce a user-facing change?:

NONE

/assign @xmudrii


Create testSimulationsWorking

What new features does this PR implement?
Please summarize the features that this PR implements. As relevant, please indicate the issues that the PR closes.

Adds ABC (closes #X)
Adds XYZ (closes #X)

What bugs does this PR fix?
Please summarize the bugs that this PR fixes. As relevant, please indicate the issues that the PR closes.

Fixes ABC (closes #X)
Fixes XYZ (closes #X)

Does this PR introduce any additional changes?
Please summarize any additional changes that this PR introduces.

Corrects typos in documentation
Changes theme of documentation

How have you tested this PR?
Please summarize the tests that you implemented to test this PR.

Added test for ABC
Added test for XYZ

Additional information
Please describe any information needed to review this PR.

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


Support GHC 8.2

I haven't tested yet, but I'm almost certain things will break a little in 8.2.
The codebase should be structured defensively, because this is going to happen over and over again:

Opaque GHC-derived datatypes like ParsedSource should live in GHC-specific modules, like HGrep.Internal.Data.GHC_8_0
Lenses should be generated in GHC-specific modules, like HGrep.Internal.Lens.GHC_8_0
Queries too
Use CPP to hide old versions
Ensure future GHC releases will attempt to use the most recent version, hope for forward-compatibility

I tried building it with 8.2 and it compiled and seemed to run without issues.

 We can probably put this stuff on ice until the GHC syntax tree actually changes.
(ExactPrint is destined to be brittle, I'm quite surprised it worked!)


Fix broken CI due to stale TODO notes on dropAllUsersFromDatabase tests

Description
Fixing CI linting errors caused after closing #1492 issue.
Readiness checklist

[ ] I added/updated unit tests (and they pass).
[ ] I added/updated integration/compatibility tests (and they pass).
[ ] I added/updated comments and checked rendering.
[x] I made spot refactorings.
[ ] I updated user documentation.
[x] I ran task all, and it passed.
[x] I ensured that PR title is good enough for the changelog.
[x] (for maintainers only) I set Reviewers (@FerretDB/core), Milestone (Next), Labels, Project and project's Sprint fields.
[x] I marked all done items in this checklist.

The next time just reopen the issue :)


Only create a new observable query if options have changed

Breaking changes
n/a
Fixes / Enhancements

Only create a new observable query if options have changed. @HofmannZ

Docs
n/a

:tada: This PR is included in version 1.0.0-beta.1 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:

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


Added confidence score with region and made changes in the unit_test.py

Issue number #643
Made following changes:

verify(), find(), represent() and extract_faces() in DeepFace.py

extract_faces() in function.py()

replaced assert "confidence" in img_obj.keys() in unit_tests.py with assert "confidence" in img_obj["facial_area"].keys()

[x] Passed 108 test cases out of 110

@serengil please review this and drop the changes in DockerFile as it looks like I didn't pulled the latest changes to the master branch before committing. Thanks


Incorrect numbered list ordering

Which doc needs an update?
https://planetscale.com/docs/concepts/nonblocking-schema-changes#planetscale-workflow
What needs to be updated?
The numbered lists for the PlanetScale Workflow section are incorrectly numbered on the rendered documentation page at https://planetscale.com/docs/concepts/nonblocking-schema-changes#planetscale-workflow

@ayrton this issue seems to be happening on many pages. Here are a few examples:

https://planetscale.com/docs/concepts/regions#changing-branch-and-database-regions
https://planetscale.com/docs/concepts/connection-strings#creating-a-password
https://planetscale.com/docs/concepts/deploy-requests#review-and-deploy-a-deploy-request


Ubuntu 20.04

I have install galgebra on Ubuntu 22.04 using github -
git clone https://github.com/pygae/galgebra.git
cd galgebra
pip install -e .
When I try to run terminal examples from the geany editor I get -
Traceback (most recent call last):
File "/home/brombo/galgebra/examples/Terminal/terminal_check.py", line 4, in
from galgebra.printer import Eprint
ModuleNotFoundError: No module named 'galgebra'
When I run a ipynb file (in Google-Chrome) all the packages are found and the code runs and when I run from the terminal command line, "python3 some_galgebra_code.py" the galgebra modules are found.  Note that when I run python code from the geany editor with sympy imports it works.
Any idea what is going on here.  It started when I upgraded to Ubuntu 22.04.

My guess would be that geany is using an old version of python on your system; if you run a program that prints sys.executable, you can compare which versions are being used in the different environments.


download action dont work

action response with
{
"download": "/nova-api/messages/261/download/store_filename",
"name": "message-0001-99dfb9f0-4961-47d8-a62c-7a6daa964330.eml"
}

@sitnikov you've got to provide more info then just this. what did you make for a button? what do you expect it todo?

try use button with this
https://nova.laravel.com/docs/4.0/actions/defining-actions.html#download-responses

@sitnikov  this is not helpful, what are you trying todo, show some code? How is the problem related to this package? The Button::action method is limited to 1 resource only at a time, without supporting fields.

@sitnikov  if you have issues with Laravel Nova you can submit a bug here:
https://github.com/laravel/nova-issues

this is ok without button action

@sitnikov  if you mean to download a file with the button you can use the Route method for it

Action::download() - default feature

but action must generate this file before download ...


Unable to delete uneditable elements using backspace or delete key

I am using 0.5.0
I am dynamically inserting few uneditable elements using insertNode(). I am not able to delete them using backspace or delete key. When i try to do that browser back button action is invoked, then page submits for previously visited URL. This happens only i have some uneditable elements together with some space and custom text.
This used to work very well in 0.4 versions.. I recently upgraded to 0.5.0.

I got a workaround for chrome on this.
For the span node that I am trying to add, I removed style dipslay:inline-block. After this, I was able to delete the nodes
I didn't dive deeper but the delete happens based on a regex check of /block/ on display property
inside the method fixDeleteInTheBeginnigOfHeading


[Debug info] Dump macro expansion buffers to disk for debug info to reference

When emitting debug info that references into a macro expansion, dump
the macro expansion buffer into a file on disk (in the temporary
directory) so that one can see the macro expansion buffers in the
source files themselves.
And thanks to the @adrian-prantl, emit "inline call" debug scopes for macro expansion expressions. The end result of this is that LLDB can "step into" a macro expansion expression to walk through the expanded code.
Implements a big chunk of rdar://102916513.

@swift-ci please smoke test

@swift-ci please smoke test

Note that the actual debug-info scope code is from https://github.com/apple/swift/pull/63144.

@swift-ci please smoke test


Problem starting systemd after upgrade

Failed to reload daemon: Process org.freedesktop.systemd1 exited with status 1
pi@raspberrypi:~ $ systemctl --user start raspisump
Failed to start raspisump.service: Process org.freedesktop.systemd1 exited with status 1
See user logs and 'systemctl --user status raspisump.service' for details.
pi@raspberrypi:~ $ systemctl --user restart raspisump
Failed to restart raspisump.service: Process org.freedesktop.systemd1 exited with status 1
See user logs and 'systemctl --user status raspisump.service' for details.

I get the above errors when trying to start the upgraded raspi-sump. Any help gratefully received

did a reboot and it now seems to be working ok

except the chart is not working! here's the status message I am getting
pi@raspberrypi:~ $ systemctl --user status rsumpwebchart.timer
● rsumpwebchart.timer - RaspiSump Webchart Timer
Loaded: loaded (/home/pi/.config/systemd/user/rsumpwebchart.timer; enabled; vendor preset: enabled
Active: inactive (dead)
Trigger: n/a

are you able to run rsumpwebchart.py manually? Do you get errors?
Just type rsumpwebchart.py then check /home/pi/raspi-sump/charts for today.png
Also check /home/pi/raspi-sump/charts/2023/07 to see if it has charts in it.

Several reboots later the chart is now working but there's another problem.  The measurement interval is set in the conf file to 300 seconds (5 mins) but what I am seeing in the CSV file does not reflect this: the interval seems to vary between a few seconds up to a few minutes
20:56:45,5.9
20:56:54,5.6
20:57:01,6.2
20:57:08,6.2
20:57:16,6.3
20:57:24,6.1
20:57:32,6.7
20:57:40,6.7
20:57:47,6.8
20:57:55,6.5
20:58:02,6.8
20:58:09,7.1
20:58:16,7.2
20:58:23,7.1
20:58:30,6.9
20:58:36,7.1
20:58:44,7.4
20:58:51,7.6
20:58:58,7.4
20:59:05,7.6

Hi Al, I am running 1.9.2 on Bullseye. I got the chart working last night but nothing was running this morning.  Does raspisump start automatically on a re-boot ? If not how can I make this happen? Also still having a problem with erratic measurement intervals.

Are your crontab entries still active?
what does crontab -l return?
Also please provide the output of
systemctl --user status raspisump
and
systemctl --user status rsumpwebchart.timer

it still sounds to me like you have remnants of your old install in crontab mixed in with systemd.
Can you post the output of the commands I gave you in the previous message?

When it generates a reading every few seconds it indicates that rsump.py is starting, stopping and then systemd tries to restart the service.  (over and over)
Are issues still present?
You wouldnt happen to have an old entry on /etc/rc.local that initiates rsump.py on startup of the pi would you?
Also the commands to make sure raspisump and rsumpwebchart.timer work on reboot are the following
systemctl --user enable raspisump
systemctl --user enable rsumpwebchart.timer
But it looks to me like they are already enabled from your output.

Hi Al,
Nothing in rc.local - see below
rc.local

This script is executed at the end of each multiuser runlevel.
Make sure that the script will "exit 0" on success or any other
value on error.

In order to enable or disable this script just change the execution
bits.

By default this script does nothing.
Print the IP address
_IP=$(hostname -I) || true
if [ "$_IP" ]; then
printf "My IP address is %s\n" "$_IP"
Its been running fine all day, but problem is that rusump.py is running 4 or 5 times a minute when in the config file its set to runn every 300 secs - not a huge issue but a bit puzzling.  Also noticed that I have raspisump.conf and a raspisump.conf.save file - is this intentional? I assume I could delete the .save version?

ok
can we just recap quickly
What is working?
What is not working?

Hi Al
Sump and chart.timer are both working fine. The remaining issue is the
measurement interval. That is set to 300 secs in config but actually
running every 15 seconds or so.
Thanks for your help
Best regards
Nick
m: 07771 994175
On Mon, 31 Jul 2023 at 20:05, Al Audet @.***> wrote:

ok
can we just recap quickly
What is working?
What is not working?
—
Reply to this email directly, view it on GitHub
https://github.com/alaudet/raspi-sump/issues/81#issuecomment-1658977911,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJBUUJOK7MRXLFR4232DQHTXS76ZPANCNFSM6AAAAAA25KXKFM
.
You are receiving this because you authored the thread.Message ID:
@.***>

ok let me test this on my end.

In the meantime, can you upgrade to my latest development snapshot?  I have included a troublshooting utility to better help me analyse the environment.
This will upgrade you to version 1.9.3rc1
To upgrade run the following
sudo pip3 install -U --no-binary :all: https://github.com/alaudet/raspi-sump/archive/refs/heads/devel.zip

Then run the following command
rsumpsupport

This will create a file called support.txt in the /home/pi/raspi-sump/support folder.
Email me that file at<EMAIL_ADDRESS>You can actually view the contents of that file, there is  no personal info in it.  It's currently a work in progress for my next release but could be helpful here.

OK I will do that upgrade and send you the file should I shut down
raspisump and the chart timer first?
Best regards
Nick
m: 07771 994175
On Mon, 31 Jul 2023 at 20:28, Al Audet @.***> wrote:

In the meantime, can you upgrade to my latest development snapshot? I have
included a troublshooting utility to better help me analyse the environment.
This will upgrade you to version 1.9.3rc1
To upgrade run the following
sudo pip3 install -U --no-binary :all: https://github.com/alaudet/raspi-sump/archive/refs/heads/devel.zip
Then run the following command
rsumpsupport
This will create a file called support.txt in the
/home/pi/raspi-sump/support folder.
Email me that file at @.***
You can actually view the contents of that file, there is no personal info
in it. It's currently a work in progress for my next release but could be
helpful here.
—
Reply to this email directly, view it on GitHub
https://github.com/alaudet/raspi-sump/issues/81#issuecomment-1659005581,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJBUUJLRL3QHZMVOWCCVQJDXTABMTANCNFSM6AAAAAA25KXKFM
.
You are receiving this because you authored the thread.Message ID:
@.***>

yes please shutdown the raspisump and rsumpwebchart.timer, upgrade then start again.

Hi Al
Upgrade done.Here's the content of the support.txt file.
Date file generated: 2023-07-31 21:18:55
os version: 10
raspi-sump version: Version 1.9.3rc1
python version on system: Python 3.7.3
Systemctl status for raspisump:
● raspisump.service - RaspiSump Service
Loaded: loaded (/home/pi/.config/systemd/user/raspisump.service;
enabled; vendor preset: enabled)
Active: active (running) since Mon 2023-07-31 21:18:50 BST; 5s ago
Main PID: 24720 (rsump.py)
CGroup: @.***/raspisump.service
└─24720 /usr/bin/python3 /usr/local/bin/rsump.py
Jul 31 21:18:50 raspberrypi systemd[692]: Started RaspiSump Service.
Systemctl status for rsumpwebchart.timer:
● rsumpwebchart.timer - RaspiSump Webchart Timer
Loaded: loaded (/home/pi/.config/systemd/user/rsumpwebchart.timer;
enabled; vendor preset: enabled)
Active: active (waiting) since Mon 2023-07-31 21:17:47 BST; 1min 8s ago
Trigger: Mon 2023-07-31 21:30:00 BST; 11min left
Jul 31 21:17:47 raspberrypi systemd[692]: Started RaspiSump Webchart Timer.
Raspi-Sump Variables:
critical_water_level: 10
pit_depth: 35
reading_interval: 300
temperature: 15
trig_pin: 17
echo_pin: 27
unit: metric
smtp_tls: 1
smtp_ssl: 0
alert_when: high
alert_interval: 5
heartbeat: 1
heartbeat_interval: 10080
line_color: FB921D
User Crontab:
Edit this file to introduce tasks to be run by cron.

Each task to run has to be defined through a single line
indicating with different fields when the task will be run
and what command to run for the task

To define the time you can provide concrete values for
minute (m), hour (h), day of month (dom), month (mon),
and day of week (dow) or use '*' in these fields (for 'any').

Notice that tasks will be started based on the cron's system
daemon's notion of time and timezones.

Output of the crontab jobs (including errors) is sent through
email to the user the crontab file belongs to (unless redirected).

For example, you can run a backup of all your user accounts
at 5 a.m every week with:
0 5 * * 1 tar -zcf /var/backups/home.tgz /home/

For more information see the manual pages of crontab(5) and cron(8)

m h  dom mon dow   command
#*/5 * * * * /usr/local/bin/rsump.py
#59 * * * * /usr/local/bin/rsumpwebchart.py
Logs/error_log content:
2021-03-14 21:25:03,**ERROR - Signal not received. Possible cable or sensor
problem.
2021-03-16 00:50:04,**ERROR - Signal not received. Possible cable or sensor
problem.
2021-04-02 20:35:06,**ERROR - Signal not received. Possible cable or sensor
problem.
2021-04-02 23:20:04,**ERROR - Signal not received. Possible cable or sensor
problem.
2021-04-06 14:55:03,**ERROR - Signal not received. Possible cable or sensor
problem.
2021-05-03 09:10:05,**ERROR - Signal not received. Possible cable or sensor
problem.
2021-06-03 03:10:04,**ERROR - Signal not received. Possible cable or sensor
problem.
2021-06-08 22:05:04,**ERROR - Signal not received. Possible cable or sensor
problem.
2021-06-17 01:20:03,**ERROR - Signal not received. Possible cable or sensor
problem.
2021-07-03 20:20:04,**ERROR - Signal not received. Possible cable or sensor
problem.
2021-07-11 15:15:04,**ERROR - Signal not received. Possible cable or sensor
problem.
2021-07-12 13:00:03,**ERROR - Signal not received. Possible cable or sensor
problem.
2021-07-13 21:35:05,**ERROR - Signal not received. Possible cable or sensor
problem.
2021-07-30 03:30:03,**ERROR - Signal not received. Possible cable or sensor
problem.
2021-08-15 04:40:03,**ERROR - Signal not received. Possible cable or sensor
problem.
2021-08-15 11:50:06,**ERROR - Signal not received. Possible cable or sensor
problem.
2021-08-17 12:40:04,**ERROR - Signal not received. Possible cable or sensor
problem.
2021-10-18 21:50:04,**ERROR - Signal not received. Possible cable or sensor
problem.
2021-11-08 08:25:04,**ERROR - Signal not received. Possible cable or sensor
problem.
2021-11-18 01:10:04,**ERROR - Signal not received. Possible cable or sensor
problem.
2021-11-27 00:15:04,**ERROR - Signal not received. Possible cable or sensor
problem.
2022-01-19 06:55:04,**ERROR - Signal not received. Possible cable or sensor
problem.
2022-01-25 15:00:04,**ERROR - Signal not received. Possible cable or sensor
problem.
2022-02-10 20:15:05,**ERROR - Signal not received. Possible cable or sensor
problem.
2022-02-14 00:35:03,**ERROR - Signal not received. Possible cable or sensor
problem.
2022-04-05 16:40:06,**ERROR - Signal not received. Possible cable or sensor
problem.
2022-09-02 22:15:03,**ERROR - Signal not received. Possible cable or sensor
problem.
2022-09-07 10:15:04,**ERROR - Signal not received. Possible cable or sensor
problem.
2022-10-06 18:05:04,**ERROR - Signal not received. Possible cable or sensor
problem.
2022-12-05 09:25:04,**ERROR - Signal not received. Possible cable or sensor
problem.
2022-12-15 07:00:06,**ERROR - Signal not received. Possible cable or sensor
problem.
2023-01-23 04:25:04,**ERROR - Signal not received. Possible cable or sensor
problem.
2023-04-02 13:00:04,**ERROR - Signal not received. Possible cable or sensor
problem.
2023-07-01 11:30:05,**ERROR - Signal not received. Possible cable or sensor
problem.
2023-07-05 11:55:07,**ERROR - Signal not received. Possible cable or sensor
problem.
2023-07-30 19:13:52,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-30 19:23:32,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-30 19:23:39,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-30 19:33:04,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-30 19:33:11,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-30 19:42:39,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-30 19:42:46,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-30 19:52:11,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-30 19:52:18,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-30 19:52:25,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-30 20:02:14,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-30 20:02:21,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-30 20:12:16,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-30 20:12:22,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-30 20:22:02,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-30 20:31:44,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-30 20:41:18,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-30 20:50:59,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 13:09:28,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 13:09:35,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 13:18:24,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 13:18:31,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 13:18:38,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 13:27:33,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 13:27:40,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 14:02:57,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 14:03:04,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 14:11:59,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 14:20:51,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 14:20:58,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 14:29:52,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 14:29:58,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 14:38:21,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 14:38:28,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 14:38:34,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 14:47:55,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 14:48:02,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 14:48:08,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 14:57:21,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 14:57:27,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 15:05:57,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 15:06:04,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 15:06:10,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 15:15:03,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 15:15:11,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 15:23:46,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 15:23:52,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 15:23:59,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 15:33:08,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 15:33:14,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 15:33:21,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 15:42:21,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 15:42:28,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 15:48:11,ERROR - Signal not received. Possible cable or sensor
problem.
2023-07-31 15:50:53,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 15:50:59,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 16:00:01,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 16:09:02,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 16:09:09,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 16:17:59,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 16:18:06,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 16:26:53,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 16:27:00,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 16:35:37,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 16:35:43,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 16:44:34,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 16:44:41,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 16:53:17,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 16:53:24,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 17:02:05,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 17:02:12,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 17:10:54,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 17:19:09,ERROR - Signal not received. Possible cable or sensor
problem.
2023-07-31 17:28:44,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 17:37:47,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 17:46:42,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 17:46:50,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 18:04:39,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 18:04:46,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 18:10:27,ERROR - Signal not received. Possible cable or sensor
problem.
2023-07-31 18:22:20,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 18:22:27,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 18:31:23,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 18:31:30,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 18:40:27,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 18:49:54,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 18:50:01,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 18:50:08,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 18:59:13,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 18:59:19,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 19:08:14,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 19:08:21,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 19:08:27,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 19:17:33,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 19:26:15,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 19:26:21,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 19:35:18,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 19:35:24,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 19:35:31,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 19:44:50,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 19:44:56,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 19:45:03,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 19:54:56,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 19:55:03,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 19:55:09,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 20:04:36,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 20:04:42,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 20:13:46,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 20:13:53,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 20:23:18,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 20:23:25,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 20:23:31,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 20:32:35,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 20:32:42,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 20:41:53,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 20:42:00,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 20:42:06,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 20:51:16,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 20:54:08,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 20:54:15,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 20:57:07,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 20:57:14,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 20:57:20,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 21:00:17,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 21:00:26,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 21:00:36,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 21:03:38,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 21:03:45,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 21:03:51,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 21:06:41,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 21:06:48,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 21:09:39,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 21:09:46,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
2023-07-31 21:09:53,ERROR - Negative reading adjusted to 0.0. Possible
degrading sensor.
Logs/info_log content:
Error executing command: ['cat', '/home/pi/raspi-sump/logs/info_log'].
Return code: 1. Output:
Last 10 lines of logs/heartbeat.log:
2022-04-02 01:15:08,Heartbeat Email Sent
2022-04-09 01:20:09,Heartbeat Email Sent
2022-04-16 01:25:08,Heartbeat Email Sent
2022-04-23 01:30:09,Heartbeat Email Sent
2022-04-30 01:35:08,Heartbeat Email Sent
2022-05-07 01:40:09,Heartbeat Email Sent
2022-05-14 01:45:08,Heartbeat Email Sent
2022-05-21 01:50:09,Heartbeat Email Sent
2022-05-28 01:55:09,Heartbeat Email Sent
2022-06-04 02:00:09,Heartbeat Email Sent
Last 10 lines of logs/alert.log:
Best regards
Nick
m: 07771 994175
On Mon, 31 Jul 2023 at 20:28, Al Audet @.***> wrote:

In the meantime, can you upgrade to my latest development snapshot? I have
included a troublshooting utility to better help me analyse the environment.
This will upgrade you to version 1.9.3rc1
To upgrade run the following
sudo pip3 install -U --no-binary :all: https://github.com/alaudet/raspi-sump/archive/refs/heads/devel.zip
Then run the following command
rsumpsupport
This will create a file called support.txt in the
/home/pi/raspi-sump/support folder.
Email me that file at @.***
You can actually view the contents of that file, there is no personal info
in it. It's currently a work in progress for my next release but could be
helpful here.
—
Reply to this email directly, view it on GitHub
https://github.com/alaudet/raspi-sump/issues/81#issuecomment-1659005581,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJBUUJLRL3QHZMVOWCCVQJDXTABMTANCNFSM6AAAAAA25KXKFM
.
You are receiving this because you authored the thread.Message ID:
@.***>

Well for one thing you definitely seem to have a degrading sensor as you have multiple 0.0 readings in your error_log.  I am starting to expect that the program is exiting sometimes due to the sensor and systemd tries to restart it right away.  But that doesnt make sense for negative values which are adjusted to 0.0.   You wouldnt happen to have a new sensor laying around?  This one is definitely looking like it is starting to fail.
If that is the issue then I have an issue in the code as well that is not handling this right.

Hi AlI will order a new sensor and try that but I doubt that’s the problem as it’s been working ok until now. In the meantime, thanks for all your excellent support.Best RegardsNickOn 31 Jul 2023, at 22:13, Al Audet @.***> wrote:
Well for one thing you definitely seem to have a degrading sensor as you have multiple 0.0 readings in your error_log.  I am starting to expect that the program is exiting sometimes due to the sensor and systemd tries to restart it right away.  But that doesnt make sense for negative values which are adjusted to 0.0.   You wouldnt happen to have a new sensor laying around?  This one is definitely looking like it is starting to fail.
If that is the issue then I have an issue in the code as well that is not handling this right.
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

ok Nick, I will leave the issue open until then.  In the meantime you could revert to crontab for handling the readings
Just stop and disable the services and change your crontab back.  As well change your reading_interval back to 0 in your raspisump.conf  file.
Al

Hi Nick checking in.  We're you ever able to get it going properly?

Hi Al, I reverted to running both processes using a cron task and it seems fine.  I think I have a water leak somewhere in or near my property as the sump pump is currently going 5 or 6 times per hour meaning that I am pumping out about 60 - 75 litres per hour and have been for many weeks.  So I am not going to do any more tinkering with the monitoring system until I find the source. The guys at the utility company were impressed when I told them about raspi-sump.Best RegardsNickOn 24 Aug 2023, at 14:01, Al Audet @.***> wrote:
Hi Nick checking in.  We're you ever able to get it going properly?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>

Thats probably a good idea. I will close this issue and if you need help at some later time we can revisit.
thanks.


Support save request/response body in self defined nginx variables

Summary
Support save request/response body in self defined nginx variables, then the request/response body content can be saved in access log.
If you think it is a good feature. Let me have a try.

There are two options:

you grap the body in context variable with body_filter phase (that can be called multiple times)
implement response phase with plugin and use kong.service.request_get_raw_body(), but this only works when client connection is http 1.1 due to OpenResty limitation with subrequests.


saving in qdrant

Describe the bug
While using huge data we need to save or store the embeddings while trying to store the embedding in qdrant and using it for llm it did not save the embeddings in qdrant itself.
To Reproduce
Steps to reproduce the behavior. Ideally with a code example.
Expected behavior
I want you to give me code integrated with llm of storing in qdrant db.
System (fill in)

Version: [e.g. 0.0.1]

Additional context
Add any other context about the problem here.

@sushmar07 can you share details of what didn't work?

just in the rag hr example which you gave or similarity search example
which you gave in colab instead of saving it in memory can you implement by
saving it in qdrant and  use it for query. the integration of the
qdrant part is not working .
On Wed, 4 Dec 2024 at 11:44, svonava @.***> wrote:

@sushmar07 https://github.com/sushmar07 can you share details of what
didn't work?
—
Reply to this email directly, view it on GitHub
https://github.com/superlinked/superlinked/issues/88#issuecomment-2516290520,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BDLXBLKKPNUF4CQNXSNOKVL2D2MTHAVCNFSM6AAAAABS7JI2ISVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJWGI4TANJSGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

I see - can you share your code and the error you are getting?
On Tue, 3 Dec 2024 at 22:29, sushmar07 @.***> wrote:

just in the rag hr example which you gave or similarity search example
which you gave in colab instead of saving it in memory can you implement
by
saving it in qdrant and use it for query. the integration of the
qdrant part is not working .
On Wed, 4 Dec 2024 at 11:44, svonava @.***> wrote:

@sushmar07 https://github.com/sushmar07 can you share details of what
didn't work?
—
Reply to this email directly, view it on GitHub
<
https://github.com/superlinked/superlinked/issues/88#issuecomment-2516290520>,

or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/BDLXBLKKPNUF4CQNXSNOKVL2D2MTHAVCNFSM6AAAAABS7JI2ISVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJWGI4TANJSGA>

.
You are receiving this because you were mentioned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/superlinked/superlinked/issues/88#issuecomment-2516308987,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AALMSVKLZX6ZHJ3LONHOSOL2D2OL3AVCNFSM6AAAAABS7JI2ISVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJWGMYDQOJYG4
.
You are receiving this because you commented.Message ID:
@.***>

i have attached a sample file. the code is running but it is not storing in
qdrant db. i have tried everything and i dont know in which collection it
is stored.the embeddings is not being stored at all. please can you
change this.
On Wed, 4 Dec 2024 at 14:10, svonava @.***> wrote:

I see - can you share your code and the error you are getting?
On Tue, 3 Dec 2024 at 22:29, sushmar07 @.***> wrote:

just in the rag hr example which you gave or similarity search example
which you gave in colab instead of saving it in memory can you implement
by
saving it in qdrant and use it for query. the integration of the
qdrant part is not working .
On Wed, 4 Dec 2024 at 11:44, svonava @.***> wrote:

@sushmar07 https://github.com/sushmar07 can you share details of
what
didn't work?
—
Reply to this email directly, view it on GitHub
<

https://github.com/superlinked/superlinked/issues/88#issuecomment-2516290520>,

or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/BDLXBLKKPNUF4CQNXSNOKVL2D2MTHAVCNFSM6AAAAABS7JI2ISVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJWGI4TANJSGA>

.
You are receiving this because you were mentioned.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
<
https://github.com/superlinked/superlinked/issues/88#issuecomment-2516308987>,

or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AALMSVKLZX6ZHJ3LONHOSOL2D2OL3AVCNFSM6AAAAABS7JI2ISVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJWGMYDQOJYG4>

.
You are receiving this because you commented.Message ID:
@.***>

—
Reply to this email directly, view it on GitHub
https://github.com/superlinked/superlinked/issues/88#issuecomment-2516560020,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BDLXBLJPADLIQW7BKNVKY3D2D25XFAVCNFSM6AAAAABS7JI2ISVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJWGU3DAMBSGA
.
You are receiving this because you were mentioned.Message ID:
@.***>

@sushmar07 I believe that attaching a file to the email that you use to respond to this thread doesn't actually add that file here on github. Can you upload here directly?

Since it is not completed I can't attach it on github that's y I attached
it here.please can u give solution for it.
On Thu, 5 Dec 2024, 2:50 am svonava, @.***> wrote:

@sushmar07 https://github.com/sushmar07 I believe that attaching a file
to the email that you use to respond to this thread doesn't actually add
that file here on github. Can you upload here directly?
—
Reply to this email directly, view it on GitHub
https://github.com/superlinked/superlinked/issues/88#issuecomment-2518583585,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BDLXBLIAHRTPBTC47VYAO7T2D5WZBAVCNFSM6AAAAABS7JI2ISVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMJYGU4DGNJYGU
.
You are receiving this because you were mentioned.Message ID:
@.***>

Sorry but I can not see the file when you just attach it to your email response - instead, you have to:

Navigate to: https://github.com/superlinked/superlinked/issues/88#issuecomment-2522031259
Comment on the thread and upload the file in your web browser.

superlinked_new (1).zip
i have uploaded the file here please resolve the issue of saving the embeddings into qdrant and then using that embeddings in my llm.

i have attached the file like you have mentioned please can you resolve the
issue.
On Fri, 6 Dec 2024 at 09:46, svonava @.***> wrote:

Sorry but I can not see the file when you just attach it to your email
response - instead, you have to:

Navigate to: #88 (comment)
https://github.com/superlinked/superlinked/issues/88#issuecomment-2522031259
Comment on the thread and upload the file in your web browser.

—
Reply to this email directly, view it on GitHub
https://github.com/superlinked/superlinked/issues/88#issuecomment-2522086206,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BDLXBLLQVMSBXLYNV2UDOIL2EEQINAVCNFSM6AAAAABS7JI2ISVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKMRSGA4DMMRQGY
.
You are receiving this because you were mentioned.Message ID:
@.***>

Hey @sushmar07! Thank you for sending us the code. You run this as is? Meaning, this is the exact code you're trying to use in a notebook? Because I see 2 problems:

QdrantVectorDatabase needs a valid host and api key. I'm quite sure you're using proper args and only added placeholders for us, but if that's not the case and you accidentally left them as they were after copying it from the example, make sure you replace them.
The code you sent is intended to be used as a REST application. If you'd like to run an experiment in a notebook, you need to use an interactive application. An example can be found here. For setting up a local REST application you can find instructions here.

I have used my host and api key
can you validate my second problem more clearly if i use rest
application will i be able to save it in qdrant.

On Tue, 17 Dec 2024 at 15:35, Edward Grosz @.***> wrote:

Hey @sushmar07 https://github.com/sushmar07! Thank you for sending us
the code. You run this as is? Meaning, this is the exact code you're trying
to use in a notebook? Because I see 2 problems:

QdrantVectorDatabase needs a valid host and api key. I'm quite sure
you're using proper args and only added placeholders for us, but if that's
not the case and you accidentally left them as they were after copying it
from the example, make sure you replace them.
The code you sent is intended to be used as a REST application. If
you'd like to run an experiment in a notebook, you need to use an
interactive application. An example can be found here
https://colab.research.google.com/github/superlinked/superlinked/blob/main/notebook/rag_hr_knowledgebase.ipynb.
For setting up a local REST application you can find instructions here
https://docs.superlinked.com/run-in-production/index#how-to-start-the-application
.

—
Reply to this email directly, view it on GitHub
https://github.com/superlinked/superlinked/issues/88#issuecomment-2548015068,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BDLXBLOFEPE6AI4DV6VE5DT2F7ZNVAVCNFSM6AAAAABS7JI2ISVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBYGAYTKMBWHA
.
You are receiving this because you were mentioned.Message ID:
@.***>

Sure, you're gonna be able to store the results in Qdrant if you either:

configure your application to use sl.InMemorySource and sl.InMemoryExecutor or
use our superlinked-server package and run a REST application

but while storing inMemory it is temporary right? i want to store  the
embeddings permanently
thats why i had used rest
On Tue, 17 Dec 2024 at 15:49, Edward Grosz @.***> wrote:

Sure, you're gonna be able to store the results in Qdrant if you either:

configure your application to use sl.InMemorySource and
sl.InMemoryExecutor or
use our superlinked-server
https://pypi.org/project/superlinked-server/ package and run a REST
application

—
Reply to this email directly, view it on GitHub
https://github.com/superlinked/superlinked/issues/88#issuecomment-2548062653,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BDLXBLPXTZUZLHMOTKVJ7L32F73ETAVCNFSM6AAAAABS7JI2ISVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBYGA3DENRVGM
.
You are receiving this because you were mentioned.Message ID:
@.***>

InMemoryExecutor doesn't mean the underlying vector database will only store data in-memory, it indicates how it can be interacted with and where is it run. If a a proper QdrantVectorDatabase is configured, InMemoryExecutor will store the results in it.

Ok thank you
On Tue, 17 Dec 2024, 4:33 pm Edward Grosz, @.***> wrote:

InMemoryExecutor doesn't mean the underlying vector database will only
store data in-memory, it indicates how it can be interacted with and where
is it run. If a a proper QdrantVectorDatabase is configured,
InMemoryExecutor will store the results in it.
—
Reply to this email directly, view it on GitHub
https://github.com/superlinked/superlinked/issues/88#issuecomment-2548157186,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/BDLXBLNCLUF6QTFLIZR2HJT2GAAJHAVCNFSM6AAAAABS7JI2ISVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDKNBYGE2TOMJYGY
.
You are receiving this because you were mentioned.Message ID:
@.***>


RFE: Support Artifact deployment from Azure Storage + Artifact Management solution

Is your feature request related to a problem? Please describe.
Today the options to deploy an App are to ASA are:

Azure CLI - non suitable for production
IDE / VSCode extension - non suitable for production
IaC / ARM / Bicep  'Microsoft.AppPlatform/Spring/apps/deployments@2022-09-01-preview' not documented
GitHub Action

There is no option neither to deploy an App from the Azure portal:
see also https://github.com/Azure/Azure-Spring-Apps/issues/5
Describe the solution you'd like
In the Java space and specifically in the Enterprise Corp. environment, customers use mainly those 2 Artifact Management solutions:
JFrog Artifactory
SonaType Nexus
Priority to JFrog who is already available on the Azure marketplace
Please add in the roadmap the ability to deploy Artifcats from Azure BLOB storage or an Artifact Management solution with this priority order :

JFrog Artifactory
SonaType Nexus
Azure BLOB storage
GitHub Packages

see also https://github.com/Azure/spring-apps-deploy/issues/17
The experience should be consistent for the developpers when deploying an App whatever the way used :

Azure Portal
GitHub Action
JFrog Artifactory
SonaType Nexus
Azure CLI
IaC / ARM / Bicep
IDE / VSCode extension

Describe alternatives you've considered
None
Additional context

@yangtony90 could you please study this RFE ?

@yangtony90 could you please study this RFE ?

Thanks for the input, Steve. @hangwan97 is considering more deployment options as part of the effort to improve the developer experience. This list will be very helpful for him.

Portal experience is under consideration.
For deploying from other repository stores, we would like to discuss and get more customer evidence before prioritizing it.


Setup an SQL Database for the Practice App

[ ] Find a suitable SQL DB service
[ ] Create the DB
[ ] Create tables required for the Practice App
[ ] Create some mock data in the Practice App for the team to use during the development of the Practice App

We dumped our initial design because of the practice-app requirements so we won't have tables from our initial design. Our base Spring project has its own local DB that will be running on the EC2 machine. In case somebody needs to use a database in the project, they can still use this local DB that will be running by default.


Unable to specify precompiled HMR dependencies in a plugin

I'm working on the plugin at https://github.com/ccapndave/fuse-box-elm-plugin/blob/master/src/index.ts
Let's assume that the entry point to my application is app.ts.
fuse.ts
fuse.bundle("app")
  .watch()
  .instructions("> js/app.ts")
  .hmr();

app.ts
import * as Elm from "../elm/src/Main.elm"

Main.elm
import Model exposing (Model)
import Update exposing (update, subscriptions, Msg(..))
import View exposing (view)

So elm-make will compile Model.elm, Update.elm and View.elm into its output automatically.  I can get a list of the absolute
paths of all dependencies using a find-elm-dependencies npm module.
The goal is to make HMR work, so that if I edit View.elm, elm-make will run on Main.elm, and then inject the code into the browser.
Here is my (failed) attempt.  This does actually make HMR work (I think), but it runs elm-make for Main.elm, Model.elm, Update.elm
and View.elm instead of just running it for Main.elm.  I sort of copied the relevant parts from BabelPlugin.ts without properly
understanding them.
//import { File, WorkFlowContext, Plugin } from "fuse-box";
import { File, WorkFlowContext, Plugin } from "../../fuse-box/.dev";
import { ChildProcess } from "child_process";
import { resolve } from "path";
import { readFile } from "fs";
import { tmpName } from "tmp";
import * as spawn from "cross-spawn";
import { findAllDependencies } from "find-elm-dependencies"

const tmp = () =>
  new Promise((resolve, reject) =>
    tmpName((err, path) => (err ? reject(err) : resolve(path)))
  );

export interface ElmPluginOptions {
  warn?: boolean;
  debug?: boolean;
}

export class ElmPluginClass implements Plugin {
  // Match Elm files
  public test: RegExp = /\.elm$/;

  public context: WorkFlowContext;

  public options: ElmPluginOptions;

  constructor(options: ElmPluginOptions = {}) {
    this.options = { ...options };
  }

  public init(context: WorkFlowContext): void {
    this.context = context;
    context.allowExtension(".elm");
  }

  public getElmMakePath(): string {
    try {
      return resolve("node_modules/.bin/elm-make");
    } catch (_) {}

    return "elm-make";
  }

  public async transform(file: File): Promise<any> {
    if (this.context.useCache) {
      if (file.loadFromCache()) {
          return;
      }
    }

    file.loadContents();

    // Get the path to elm-make
    const elmMakePath: string = this.getElmMakePath();

    // Create temporary JS file
    const tmpFilename: string = `${await tmp()}.js`;

    return new Promise((resolve, reject) => {
      // Construct the arguments for elm-make
      const args = [
        "--yes",
        "--output",
        tmpFilename,
        this.options.warn ? "--warn" : null,
        this.options.debug ? "--debug" : null,
        file.absPath
      ].filter(x => x !== null);

      const proc: ChildProcess = spawn(elmMakePath, args, { stdio: "inherit" });

      proc.on("error", (err: NodeJS.ErrnoException) => {
        if (err.code === "ENOENT") {
          reject(
            `Could not find Elm compiler @ "${elmMakePath}"
             \nHave you installed elm yet? If not, please install "elm" via npm`
          );
        } else if (err.code === "EACCES") {
          reject(
            `Elm compiler @ "${elmMakePath}" did not have permission to run
            \nYou may need give it executable permissions`
          );
        } else {
          reject(
            `Error attempting to run Elm compiler @ "${elmMakePath}" \n ${err}`
          );
        }
      });

      proc.on("close", (code: Number) => {
        if (code === 0) {
          readFile(tmpFilename, (err: NodeJS.ErrnoException, data: Buffer) => {
            if (err) {
              reject(err);
            } else {
              file.contents = data.toString();

              findAllDependencies(file.absPath)
                .then((paths: string[]) => {
                  file.analysis.dependencies = paths;

                  if (this.context.useCache) {
                    this.context.emitJavascriptHotReload(file);
                    this.context.cache.writeStaticCache(file, file.sourceMap);
                  }

                  resolve(file);
                })
                .catch((err: string) => {
                  reject(err);
                });

              resolve(file);
            }
          });
        } else {
          reject("Failed to compile Elm.");
        }
      });
    });
  }
}

export const ElmPlugin = (options?: ElmPluginOptions) =>
  new ElmPluginClass(options);

Note that paths in
findAllDependencies(file.absPath)
  .then((paths: string[]) => {
    file.analysis.dependencies = paths;

is an array of absolute paths to all imported Elm files:
[ '/Users/dave/Projects/Couloir/ctp/title-sss/app/packages/couloir-core/src/Util/MaybeExtra.elm',
  '/Users/dave/Projects/Couloir/ctp/title-sss/app/elm/src/Model.elm',
  '/Users/dave/Projects/Couloir/ctp/title-sss/app/elm/src/Update.elm',
  '/Users/dave/Projects/Couloir/ctp/title-sss/app/elm/src/View.elm',
  '/Users/dave/Projects/Couloir/ctp/title-sss/app/elm/src/Persister.elm',
  ... lots and lots more
]

Unfortunately elm-make can only take a file as input, not a string or things on stdin (hopefully this will be coming in a future version).

I think that the other files are simply not cached (for some reason). Could you investigate what is actually written to the file system

Clear .fusebox folder
Run the project, check the cache.

If it's in the cache then
if (this.context.useCache) {
      if (file.loadFromCache()) {
          return;
      }
    }

This condition should work just fine. If it's not there we should start investigating why it's not there. The other thing that comes to my mind is that it takes a long time to compile the files, and you hit HMR before the previous compilation is completed.

Fixed with https://github.com/ccapndave/fuse-box-elm-plugin/commit/30fd879285431708978a67242853ee0cdc85bcd6


Build Gadgetron with GPU support fails

It fails because it doesn't find one header hdf5_hl.h.
Looking at the hdf5 build we disable BUILD_HDF5_HL_LIB

Additionally there is a fix in Gadgetron https://github.com/CCPPETMR/gadgetron/tree/fix_gpu_link

My PR on Gadgetron repo has been merged https://github.com/gadgetron/gadgetron/pull/638


Root should not be inside location block

Bad practice is currently enforced:  fail('Cannot create a location reference without a www_root [...]).
Instead option to add www_root should be removed and error raised if user tries to add root inside location block.
Nginx Pitfalls: Root inside location block
BAD:
server {
    server_name www.domain.com;
    location / {
      root /var/www/nginx-default/;
      [...]
    }
}

GOOD:
server {
  server_name www.domain.com;
  root /var/www/nginx-default/;
  location / {
    [...]
  }

Root moved to vhost_header

solution #576

:thumbsup:
but I think #576 is a workaround. the module should do it correctly by default, to avoid the wrong behavior, if the DevOP is careless / inexperienced

I agree. However see @jfryman comment. I do understand his noble democratic desire to allow people doing stupidity but I still think that by default root should be in server block. Case that user from whatever reasons still wants to place root in location block give her/him option to do it.

@schkovich I totally agree.

@schkovich I think in that comment I said...

I'd rather provide sane defaults and let a user make silly decisions on their own.

I do think this falls under a sane default. Throw up a PR, I'll review/merge.

I have included a way to suppress logs in #888
We do have some use cases that require setting different roots per location, but agree that the default behavior could be improved.
I'm going to close this one, just because it hasn't had any activity in ages, but, as they say, pull requests (with tests) will be reviewed and gratefully accepted if this is still an issue.


Shiny Leaderboard

Is your feature request related to a problem? Please describe.
Several Discord guilds are using other bots for shinies and gyms
Describe the solution you'd like
Add a leaderboard for shinies
Describe alternatives you've considered
Not dealing with shinies
Additional context
We run a poll:

POLL ENDED

What is your opinion on us having a Shiny Leaderboard based on the honour system?

Results

I wouldn't use it but I'm not against it: 23
Yes: 10
NO NO NO: 1

Okay, to make this happen we need to do a few things:

[ ] Discuss and decide on the rules for these shiny stats.

[ ] Add fields for shiny stats to the database

[ ] Update TrainerDex/TrainerDex.py to support these new fields

[ ] Enable the bot to post to and read from these new fields

@SenorKarlos I know you're very focal for the shiny leaderboards. So I would appreciate your feedback.

I think at the bare minimum, we need to match what PoGo Leaderboard has since, given Chucks unfortunate news, it might be a possibilty that that bot will be going down and it would be smart to fill that gap. They have: Shiny, UniqueShinies, ShinyDex (they have the same for Lucky too)
Quote from Sellyme#1963 explaining their stats:

UniqueShiny is what you have right now, ShinyDex is what you've had ever.
If you catch a shiny Charmander and evolve it to Charizard that's 1 UniqueShiny and 3 ShinyDex

Also from PoGo Leaderboard's rules command:

Unique 100% and Shinies are 1 per Pokedex number in your inventory, this means that while 2 perfect Tyranitars will count twice for Total 100%, they only count once for Unique 100%, same goes for Shiny

Costume variations DO NOT count as an extra unique, so a shiny party hat Pikachu and a shiny non hat Pikachu is worth 1 unique shiny

Personally, I know the people in my local discord count a costumed unique shiny leaderboard which uses Leek Duck's Shiny Checklist to determine total count. We could parse the share link from that to generate a count for all of the shiny stats in one shot.

Personally, I know the people in my local discord count a costumed unique shiny leaderboard which uses Leek Duck's Shiny Checklist to determine total count. We could parse the share link from that to generate a count for all of the shiny stats in one shot.

This this is the output URL from Leek Duck's Checklist for myself.
https://leekduck.com/shiny/?nickname=TurnrDev&show=all&lang=en&dex=31-125-240-126-175-176-180-190-198-256-271-296-315-403-404-412_11-572&own=1-2-3-4-6-7-8-9-7_05-8_05-9_05-15-19-20-19_61-20_61-172-26-25_01-172_07-35-37-39-40-43-50-53_61-54-60-63-77-78-83-89_61-91-93-95-103_61-105-124-466-467-130-131-134-135-196-233-474-139-147-148-153-154-156-157-159-160-161-468-179-181-424-430-202-205-215-221-473-227-234_08-244-245-247-249-250-253-254-255-257-261-262-267-270-272-273-279-280-281-475-287-288-291-297-307-308-407-321-325-333-334-348-349-350-367-368-371-372-373-375-376-380-383-386_11-388-389-401-405-413_11-427-436-573-632-809&offer=5-13-14-25-92-94-127-129-133-136-197-137-142-145-146-149-152-155-158-209-210-220-243-246-248-311-312-351-366-374-382-387
So we only care about the dex, own and offer parameters.

dex: Shiny Pokemon they once had, but no longer do.
own: Shiny Pokemon they have
offer: Shiny Pokemon they have spares off, whilst we don't care about spares, any pokemon appearing here should be treated as if they're in own

These are the rough, untested formulas for the following boards (assuming query is a dict of the parameters from the url)
UniqueShinies
own = set([x.split('_')[0] for x in query.get('own').split('-')])
offer = set([x.split('_')[0] for x in query.get('offer').split('-')])
return len(own+offer)

ShinyDex
dex = set([x.split('_')[0] for x in query.get('dex').split('-')])
own = set([x.split('_')[0] for x in query.get('own').split('-')])
offer = set([x.split('_')[0] for x in query.get('offer').split('-')])
return len(dex+own+offer)

CostumedShinies
own = set(query.get('own').split('-'))
offer = set(query.get('offer').split('-'))
return len(own+offer)


Incorrect comparisson of parquet binary statistics for accented characters

Original Issue from the old repo: https://github.com/prestodb/presto/issues/12338 by @igorcalabria

On version 0.216 presto incorrectly assumes that a binary column statistic is corrupt due to wrong ordering of accented values. The root cause is probably the naive comparison made by the slice library here:
https://github.com/prestodb/presto/blob/master/presto-parquet/src/main/java/com/facebook/presto/parquet/predicate/TupleDomainParquetPredicate.java#L201
I have added a simple test case on TupleDomainParquetPredicateTest that should not fail
   @Test
   public void testAccentedString() throws ParquetCorruptionException {
       String column = "StringColumn";

       assertEquals(getDomain(createUnboundedVarcharType(), 10, stringColumnStats("Áncash", "china"), ID, column,
               true), create(ValueSet.ofRanges(range(createUnboundedVarcharType(), > utf8Slice("Áncash"), true, utf8Slice("china"), true)), false));
   }

but it fails with
com.facebook.presto.parquet.ParquetCorruptionException: Corrupted statistics for column "StringColumn" in Parquet file "testFile": [min: Áncash, max: china, num_nulls: 0]

Áncash comes before China, but presto flags the statistics as corrupt since it does not use natural ordering to sort binary statistics.
As additional information, the files that led me to this error were generated by spark

It seems ordering can be different between different systems and this leads to one system encoding certain statistics (min/max) with an ordering that is different from Presto's.
In the best case, Presto notices that something is wrong with statistics and throws an exception (this is what happened to @igorcalabria) but in the worst case Presto does not notice the problem and can serve incorrect results. See my last comment:

Say we have strings A, B, C. If the order for Parquet is A, B, C but for Presto is A, C, B.
(I don't mean to imply that Parquet's order is correct, while Presto's isn't -- this is just an example)
In the best case, say we have a Parquet page of Bs and Cs, the stats will show min=B and max=C and Presto will raise the corrupt stats exception.
In the worst case, say we have a Parquet page of As, Bs, and Cs, the stats will show min=A, max=C. Presto will not raise an exception as it also finds that A < C. But if Presto is looking for Bs, it will completely skip the page because it believes that B > C. No exception will be raised and Presto will return the wrong result.

We are discussing this issue in the Presto Community Slack (https://prestosql.io/community.html), #parquet-stats

This hasn't been updated for a while and i suspect one of the upgrades (Hive 3 or Parquet lib update) could have solved the problem.
There may be no point in keeping the issue open, so let me close this. We can continue conversation here, or on #troubleshooting channel on our slack.

so hive 2 isn't supported by presto anymore? its still an issue

Can confirm, we are still having this issue. In particular, it's corrupting when trying to generate a Parquet table where a column has currency symbols ($, €, etc.). We are using 0.232, and patch notes from last year suggest that the hive.parquet.fail-on-corrupted-statistics configuration is being deprecated. I would have thought this implied that this issue was fixed.

We are using 0.232

@ConnorJBeck can you please try again with the latest release (currently 348, https://prestosql.io/download.html)?
if you have any questions, you can always ping me on our slack


TODO

update GAP
test different version SOAPs
add CACE to potential bank
add CN in CV

implement of generalised MACE also with fine-tunning


Update bot.php

This was wrong. You need to divide your balance from the current purchase price to get the buy amount.

@codeandbattle thanks for pointing all those bugs out! Unfortunately I didn't have the time to properly test the code and make it prettier. Now would be a good time for using this bot since the market has had the perfect conditions lately


add Screenplay#exit

This should fix #76.

Add a Screenplay#exit method to be called in Activity#onDestroy
Call tearDownComponents/teardownScene in Screenplay#exit so that components receive a callback even when attached to the last scene on the stack

LGTM


It has to have an ability to compile a module with aspects without a transformation of the module's code

implemented in 3.1.0 — already available in maven :)


Adds stuff needed to compute lognormal shift parameters

This small PR ports the code that @dlanzieri developed back into this repo, and also makes use of python multiprocessing for quickly computing all the lognormal params we need on a single machine without headaches

Note that it uses the redshift file from you PR #31 , which I copied over on my local machine but didnt include in this PR since you are going to add it


Remove eRegulations

This PR removes the eRegulations dependencies and related configuration. This should enable us to proceed with the Django 1.11 upgrade.
I'm putting a hold label on this for right now until the launch dust clears for Regs3k.
Removals

eRegulations

Checklist

[x] PR has an informative and human-readable title
[x] Changes are limited to a single goal (no scope creep)
[x] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the development playbook
[x] Passes all existing automated tests
[ ] Any change in functionality is tested
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged / future todos are captured in comments
[ ] Visually tested in supported browsers and devices (see checklist below :point_down:)
[ ] Project documentation has been updated
[x] Reviewers requested with the Reviewers tool :arrow_right:


💡 [FEAT] Query TODOs from the commandline

I think it would be great if there was a commandline interface to dooit, with which the todos could be printed to stdout.
My use case would be that I would like to display the todo that is due next in my global system status bar along with some other todo metadata.
Something like dooit --list all --sort due --format "%n %d %t" would be a great addition. The command should then only output the relevant todos to stdout in the specified format (e.g. %n would be the format sequence for the title of the todo, %d would be the due date and %t would be the tags of the todo item etc.) and sorted by the flag supplied in --sort.

Hey!

My use case would be that I would like to display the todo that is due next in my global system status bar along with some other todo metadata.

Maybe you can currently use python scripts for that?
This is a great idea tho. Altho I am a bit confused about the implementation part since it has a pretty complex structure :(

@kraanzu thanks for making this app. Any way you can show an example of a Python script that can query data?
Thanks!

Hi @maulik13 , You can check out Backend API from the docs.
If you need any assistance, feel free to open a discussion :)
As for the initial idea of this issue thread, maybe I can create a separate parser just for this and integrate it with dooit. For now, I'll close this issue.
Note: You still can run custom python scripts for regularly used queries :D


Regarding removal of buffers and directly using the nets

Feature Description
Hi ,
I have buffers in my netlist , any way not to use the buffers and use the input nets of the buffer directly downstream ?
If i put dont use on the buffers , i am getting Error that buffers are not there in the library.
sky130_fd_sc_hd__buf_1 _43_ (
    .A(_17_),
    .X(_13_)
  );
  sky130_fd_sc_hd__buf_1 _44_ (
    .A(_14_),
    .X(_10_)
  );
  sky130_fd_sc_hd__buf_1 _45_ (
    .A(_11_),
    .X(_07_)
  );

Thanks

What Yosys script are you using?

The recommended solution here would be to use techmap followed by opt_clean.
Given a Verilog file like this one called buffer_map.v:
module sky130_fd_sc_hd__buf_1(input A, output X)
\$_BUF_ _TECHMAP_REPLACE_ (.A(A), .Y(X));
endmodule

techmap -map buffer_map.v will replace the sky130 buffer cells with the Yosys-internal $_BUF_ cell, and then opt_clean will directly connect the input and output of the $_BUF_ cell, which achieves what you want.


Fix typo for Gemspec/DateAssignment examples

This PR fixes typo for Gemspec/DateAssignment examples.

Variable names are corrected from s to spec.

Before submitting the PR make sure the following are checked:

[x] The PR relates to only one subject with a clear title and description in grammatically correct, complete sentences.
[x] Wrote good commit messages.
[ ] Commit message starts with [Fix #issue-number] (if the related issue exists).
[x] Feature branch is up-to-date with master (if not - rebase it).
[x] Squashed related commits together.
[ ] Added tests.
[x] Ran bundle exec rake default. It executes all tests and runs RuboCop on its own code.
[ ] Added an entry (file) to the changelog folder named {change_type}_{change_description}.md if the new code introduces user-observable changes. See changelog entry format for details.

Thanks!


successful on mac and win10

Hey, guys. I have been successful on mac and win10. You can see my blog
https://blog.csdn.net/qq_39567427/article/details/111390051 for more information. I think it's not easy to be successful  on both mac and win10.

Thanks for your effort!

博主,您好,我vs也安装了,环境变量都设置了,可是编译总是出现:error: command 'cl.exe' failed: No such file or directory
. 在其他程序的编译也出现这个问题,我百度这个解决方案就是不行.你懂怎么弄么?

博主,您好,我vs也安装了,环境变量都设置了,可是编译总是出现:error: command 'cl.exe' failed: No such file or directory . 在其他程序的编译也出现这个问题,我百度这个解决方案就是不行.你懂怎么弄么?

应该就是没有cl.exe 或许可以尝试下载vs studio 带的编译器或者看是否配好环境变量。


fixed mgw2 stats with ethernet connection

Thanks!

this MR has been conflicted with #885, @AlexxIT may need to use only one of these two MRs.
2022-12-23 19:12:45.616 WARNING (MainThread) [custom_components.xiaomi_gateway3.core.gateway] <IP_ADDRESS> | Can't update gateway stats
Traceback (most recent call last):
File "/config/custom_components/xiaomi_gateway3/core/gateway/gate_mgw2.py", line 82, in mgw2_update_stats
"rssi": int(rssi) + 100 if len(rssi) >=1 else 0
TypeError: object of type 'int' has no len()


Run yarn install before tests

Ensures that tests will work when switching branches.

IMO yarn install adds a lot to the runtime of testing. Should be a manually 1-off rather than part of the test command.


Blacklist doesn't work with 'ember-cli-babel' options key

Was scratching my head why this wasn't working. Blacklisting doesn't seem to work with 5.2.3/4 and the options key 'ember-cli-build'.
Example repo demonstrating: https://github.com/Soliah/es6-test

blacklist was part of the babel config option (only compileModules and includePolyfill were moved to 'ember-cli-babel' config key). I submitted https://github.com/Soliah/es6-test/pull/1 to show what I mean.
Closing this for now (assuming I was correct above).  Happy to reopen if that doesn't solve the issue...


data: add device Logitech G Pro (X) keyboard

Device file for Logitech G Pro and Logitech G Pro X keyboards
Known issues:

not possible to change LED color of Caps lock indicator, Scroll lock indicator and Game Mode button.

Thank you!


Settings - users

Settings - List of users isn't responsive

That's true. Making tables responsive is tricky, probably not something I'll work on myself at this time.

Hey, @Kak3n! Telescope has changed a lot in the past months, and there is a new React-based version, Telescope Nova (intro video). If you know Crater, it runs on the latest version.
The Legacy version is no longer supported. I'm closing this issue.
I invite you to check the new version, it's awesome!
Happy hacking! 🚀
Ps: by the way, don't hesitate to join the Slack to ask any question, you are welcome! 👍


Error with copy-as-markdown on individual records  on debian after results are re-ordered

Description
I have first noticed this on the results of a describe mysql statement, I have not tested it on other types of queries (I am not sure if that would make any difference or not).
DBeaver Version
Community Ediotion, Version <IP_ADDRESS>112130652
Operating System
Debian 11
Database and driver

Database: 10.2.32-MariaDB-log
Driver: org.mariadb.jdbc:mariadb-java-client:RELEASE 2.7.1

Steps to reproduce
Given a test table with 2 columns:

Field
Type
Null
Key
Default
Extra

column_1
varchar(100)
YES

column_2
varchar(100)
YES

run an sql statement like

describe test

right click on the row 2, Advanced Copy -> copy as markdown. The clipboard will contain the markdown for the second row
|Field|Type|Null|Key|Default|Extra|
|-----|----|----|---|-------|-----|
|column_2|varchar(100)|YES||||

reorder the results based on the column name

again, right click on the row 2, Advanced Copy -> copy as markdown. The clipboard should contain the markdown for the (new) second row but it contains the markdown for the current first row
|Field|Type|Null|Key|Default|Extra|
|-----|----|----|---|-------|-----|
|column_2|varchar(100)|YES||||

Additional context
Not sure if this was intended behavior or not.
OS version
$ cat /etc/os-release
PRETTY_NAME="Debian GNU/Linux 11 (bullseye)"
NAME="Debian GNU/Linux"
VERSION_ID="11"
VERSION="11 (bullseye)"
VERSION_CODENAME=bullseye
ID=debian
HOME_URL="https://www.debian.org/"
SUPPORT_URL="https://www.debian.org/support"
BUG_REPORT_URL="https://bugs.debian.org/"

Dbeaver version

Thank you for bug report. It should be fixed for the DBeaver 22.1.4. Could you, please, check if your issue is still actual for the latest DBeaver version?

Hi @E1izabeth, thanks for your quick reply. Indeed I've updated my dbeaver to 22.1.4 and the issue is fixed.
I will close this then as it is not actual for the latest dbeaver version


Enable Break Between Pages

Hello, Is there a way I can enable it to show a break between each page in the pdf?

I have this done in my fork, user selectable for the size of the page marker also enable option.

So there is no way to currently do it. When will that be put in? Or can you give me a code snippet of how to do it?

I custom added the code and create a fork, codes on there

Not had time to update the fork but the basics are there.... i will have to update and merge
@barteksc

+1

@Papabrose Try 2.7.0-beta version, it has possibility to add spacing between pages

@barteksc is there anyway to make it look like a page break like this? This is really what I meant by break between pages.

Set spacing and PdfView's background in desired color

Thanks you rock!


Parallelization of Jordan-Wigner transformation

For systems of >10 orbitals, I noticed that a jordan wigner transformation on the fermionic hamiltonian is quite expensive, probably because it is pure python code so it runs on just 1 core. Is there any way of improving the speed of the get_jordan_wigner() function and/or parallelize it?

Probably. It would be nice to have faster code for this. The runtime should be roughly linear in the number of terms in the Hamiltonian. Of course, for large chemistry Hamiltonians with O(N^4) terms, that's not very good. But for the case of molecules there is a special routine that maps the InteractionOperators directly to qubits without going through the fermion Hamiltonian as an intermediate, and that is faster. Feel free to suggest a better implementation for the jordan wigner transform applied to the FermionOperator data structure.

I think at some point we might want to implement the basic transforms in Cython.


Letters tabs refactor

Bar tests seeming to hang, this branch has all features and refactors that i wanted to add.  So over to you @rjmk
Ivan and I can go over and fix hanging tests tomorrow.

Are they still hanging locally, @JMurphyWeb? Try npm prune


Fixed media queries, (kind of), lots of linting, got the pages to reload, (kind of)

Hey @StephanieEA @bekahlundy , changed BrowserHistory to HashHistory, its kind of hacky  I think but allows us to reload page and hit back and forth. Also we got mr burns centered on the mobile app, has to use the !important in css to make that happen. I deleted footer and a bunch of other junk and did a lot of linting.
Also fixed a few other errors in consoel. CSS needs some more polishing, and we need to deploy to firebase. Let me know if everything looks alright!
Dylan

🔥


Runner[810:141577] [VERBOSE-3:shell.cc(212)] Check failed: vm. Must be able to initialize the VM.

Hi,
I'm developing an app using latest Flutter version, Due to some reason app is getting crash on startup white screen, I'm providing u logs as below, Any thoughts ? :) thanks
2019-09-30 22:59:37.791687+0500 Runner[810:141577] [VERBOSE-2:dart_vm_data.cc(19)] VM snapshot invalid and could not be inferred from settings.
2019-09-30 22:59:37.793008+0500 Runner[810:141577] [VERBOSE-2:dart_vm.cc(245)] Could not setup VM data to bootstrap the VM from.
2019-09-30 22:59:37.793537+0500 Runner[810:141577] [VERBOSE-2:dart_vm_lifecycle.cc(89)] Could not create Dart VM instance.
2019-09-30 22:59:37.795949+0500 Runner[810:141577] [VERBOSE-3:shell.cc(212)] Check failed: vm. Must be able to initialize the VM.
(lldb)

Hello @AteqEjaz !
Thank you for posting an issue.
This problem has been raised and discussed already in these threads: #41081, #40770, #41636.
Can you please try Flutter version from the beta / master channels? Also, can you please add the flutter doctor -v command output?
Thank you.

Hello, you this problem solved？

我也遇到了这个问题信息如下
2019-11-07 19:21:03.141894+0800 Runner[2280:469656] [VERBOSE-2:dart_vm_data.cc(19)] VM snapshot invalid and could not be inferred from settings.
2019-11-07 19:21:03.141966+0800 Runner[2280:469656] [VERBOSE-2:dart_vm.cc(245)] Could not setup VM data to bootstrap the VM from.
2019-11-07 19:21:03.141998+0800 Runner[2280:469656] [VERBOSE-2:dart_vm_lifecycle.cc(89)] Could not create Dart VM instance.
2019-11-07 19:21:03.142079+0800 Runner[2280:469656] [VERBOSE-3:shell.cc(212)] Check failed: vm. Must be able to initialize the VM.
[✓] Flutter (Channel stable, v1.9.1+hotfix.6, on Mac OS X 10.15 19A582a, locale zh-Hans-CN)
• Flutter version 1.9.1+hotfix.6 at /Users/xhp281/flutter
• Framework revision 68587a0916 (8 weeks ago), 2019-09-13 19:46:58 -0700
• Engine revision b863200c37
• Dart version 2.5.0
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.0)
• Android SDK at /Users/xhp281/Library/Android/sdk
• Android NDK location not configured (optional; useful for native profiling support)
• Platform android-29, build-tools 29.0.0
• ANDROID_HOME = /Users/xhp281/Library/Android/sdk
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 11.0)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 11.0, Build version 11A420a
• CocoaPods version 1.8.4
[✓] Android Studio (version 3.5)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin version 41.0.2
• Dart plugin version 191.8593
• Java version OpenJDK Runtime Environment (build 1.8.0_202-release-1483-b49-5587405)
[✓] IntelliJ IDEA Ultimate Edition (version 2019.2)
• IntelliJ at /Applications/IntelliJ IDEA.app
• Flutter plugin version 38.1.4
• Dart plugin version 192.6262.13
[✓] VS Code (version 1.39.2)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.6.0
Thread 1: signal SIGABRT
import UIKit
import Flutter
@UIApplicationMain
@objc class AppDelegate: FlutterAppDelegate {
override func application(
_ application: UIApplication,
didFinishLaunchingWithOptions launchOptions: [UIApplication.LaunchOptionsKey: Any]?
) -> Bool {
GeneratedPluginRegistrant.register(with: self)
return super.application(application, didFinishLaunchingWithOptions: launchOptions)
}
}

See https://github.com/flutter/flutter/issues/27835
"Please try deleting /Users/owner/Documents/Flutter/flutter/bin/cache and run flutter doctor then try again."

I've tried the Flutter cache, re-running doctor, as well as running flutter upgrade to advance to 68587a0916, but when trying to launch on a physical iPhone after flutter build, I get the following, and a white screen:
2019-11-25 20:08:08.361862+0100 Runner[732:33380] [VERBOSE-2:dart_vm_data.cc(19)] VM snapshot invalid and could not be inferred from settings.
2019-11-25 20:08:08.362089+0100 Runner[732:33380] [VERBOSE-2:dart_vm.cc(245)] Could not setup VM data to bootstrap the VM from.
2019-11-25 20:08:08.362183+0100 Runner[732:33380] [VERBOSE-2:dart_vm_lifecycle.cc(89)] Could not create Dart VM instance.
2019-11-25 20:08:08.362871+0100 Runner[732:33380] [VERBOSE-3:shell.cc(212)] Check failed: vm. Must be able to initialize the VM.

The upgrade command produced, eventually:
Flutter 1.9.1+hotfix.6 • channel stable • https://github.com/flutter/flutter.git
Framework • revision 68587a0916 (2 months ago) • 2019-09-13 19:46:58 -0700
Engine • revision b863200c37
Tools • Dart 2.5.0

Output from Flutter Doctor:
👻 20:05:46 zmeggyesi@ShinyPlatform:[~/projects/site-overwatch/frontend]:
$ flutter doctor
Doctor summary (to see all details, run flutter doctor -v):
[✓] Flutter (Channel stable, v1.9.1+hotfix.6, on Mac OS X 10.14.6 18G1012, locale en-GB)
[✗] Android toolchain - develop for Android devices
    ✗ Unable to locate Android SDK.
      Install Android Studio from: https://developer.android.com/studio/index.html
      On first launch it will assist you in installing the Android SDK components.
      (or visit https://flutter.dev/setup/#android-setup for detailed instructions).
      If the Android SDK has been installed to a custom location, set ANDROID_HOME to that location.
      You may also want to add it to your PATH environment variable.

[✓] Xcode - develop for iOS and macOS (Xcode 11.2.1)
[!] Android Studio (not installed)
[!] VS Code
    ✗ Flutter extension not installed; install from
      https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter
[✓] Connected device (1 available)

! Doctor found issues in 3 categories.


Handle nested :undef in consul_sorted_json

Currently consul_sorted_json only handles top level :undef values,
leaving nested :undef values to slip through and eventually raise an
exception. Instead of trying to handle all :undefs upfront in the
function, handle them in the recursion and treat them as what they
actually are, nulls.
I've also been encountering the Exception("") vs Exception.new("")
problem detailed in #245, as Exception("") is not valid syntax in
newer versions of Ruby. That fix is included here as well

Nice. Thanks!


Make withCredential optional in oauth2.exchangeForToken

I'm working on login form a fully decoupled Angular app.
Currently it's not possible to call a server that has CORS set to *, since oauth2.exchangeForToken has return $http.post(defaults.url, data, { withCredentials: true }); (and passing credentials when CORS is * is illegal).
Also looking at instagram-hackhands as an example, I see that the code there has return $http.post(defaults.url, data);
The solution should be making the withCredentials optional.

(PR will follow)

Actually, why do we even need withCredentials at all? I think that part can be removed.