Append phishfort blocklist

PhishFort phishing blacklist
Included PhishFort blacklist in the default blacklist used to perform phishing detection.
Description

ADDED:

Fetch of public PhishFort blacklist via cdnjs / GitHub.
Inclusion of entries in the PhishFort blacklist into the one used by default (published as part of MetaMask/eth-phishing-detect)
Some tests to check for successful detection of entries from the PhishFort blacklist.

Checklist

[x] Tests are included if applicable
[x] Any added code is fully documented

Submitted w/ explanation to @sethkfman via email.

I have updated the PR with the following:

Removal of duplicates before appending the PhishFort hotlist.
Graceful failure if only one list is accessible.
Updated queryConfig to make the above possible (it no longer throws errors for certain HTTP codes and not for others).

The only thing discussed above but not yet catered for is tying back a specific blocklist entry to a list. The Detector from eth-phishing-detect would likely also need to change to do this, or alternatively the architecture of the PhishingController would need a revamp to allow for multiple PhishingDetector instances.
I would like to get this merged for the sake of getting users protected sooner rather than later, while we work out list separation separately, preferably in its own PR.

@Gudahtt Noted. My understanding is that you intend to make the required changes to eth-phishing-detect to allow for multiple list inputs. What are you envisioning in terms of input to the PhishingController? I could suggest the following:
{
    version: number;
    tolerance: number;
    blacklist: string[];
    fuzzylist: string[];
    whitelist: string[];
    provider: string; // eg. MetaMask, PhishFort, Umbrella Corporation, etc.
    disputeUrl: string; // Or reportingUrl if that does not cause ambiguity
}[]

Thanks @Gudahtt. I'll keep an eye on #7079. Once merged, I intend to update the version of eth-phishing-detect used in our fork, and then integrate both configurations.

v1.2.0 of eth-phishing-detect was just published with support for multiple phishing configurations. Let me know how it works out!

Updated implementation of PhishingController to make use of the new input type of PhishingDetector as per v1.2 of eth-phishing-detect. The new version worked without any issues. State typing and state-checking test also updated to accommodate this.
Please let me know if any other changes are desired, otherwise I think this is ready to be merged.

Could you update the test method to return the entire result object, instead of just the result boolean? We need the config name in order to tell the UI where to direct the user.

Response of test(...) updated with newly-defined interface that describes response from the check(...) function from eth-phishing-detect. All tests that check for boolean results are updated. @Gudahtt, is it necessary to alter the tests to check against the whole response object and not only the boolean property?

That would be ideal, yeah. We do want to have all properties tested. Though it seems there aren't any fuzzylist tests right now, so those would need to be added. We could use tests for the multi-config setup as well.

Not sure how much of the test improvements to ask you to complete here. I try to ensure that all new changes are fully tested but not to require adding tests that were already missing in the first place, as a general rule. So if you wanted to add fuzzylist tests, that would be great, but I would accept this with just additional assertions for the type property on the current test(...) tests, plus a few more tests to ensure that the "allow" and "block" cases work properly with multiple configs, with assertions for the config name.

Done. A sequence of fuzzylist tests added as well. @Gudahtt, once you have taken a look, please confirm that everything you expect to see is there.

Other minor changes:

EthPhishingDetectResult was missing match?: string, fixed.
Tests intended to verify behaviour for inaccessible configs changed to HTTP 500 instead of 304.

Sorry I'm only just now realizing that the legacy config remains in use until the first update. Could you update the constructor to use the new format as well, passing in the config as an array? I think this would be simpler if we moved directly to the new format, so we wouldn't have to anticipate the two different return types.

Done. Testing references to legacy config have been replaced with default config.

Looks like I don't have permission to make commits on this branch. I can merge this after my suggestion is addressed or merged, and the lint errors are fixed.

More lint errors. Please run yarn lint:fix locally, and double check that the build and tests pass as well.

@Gudahtt Linting done, build and test complete successfully. Please note that I am only running the PhishingController.test.ts tests.

@Gudahtt Any update on this?


StartGame autoaction

Auto clicks "Start Game" when visible in character screen.

Nice contribution!
Thanks alot!


Fill in with Emoji test

DO NOT MERGE
This reproduces the issue in #346. I'm not sure exactly how we should fix this yet and wanted to get some insight. Gitlab experienced this same issue and worked around it by filling in the field with js. Should we consider going that same route?

Well, we have to actual do the annoying fun work of fixing it 😝.

easy peasy... ;P

This appears to be a chromedriver problem and not a Wallaby problem.
I propose that the solution should be to document the behavior and potential workarounds, but not implement any special cases.
@michallepicki What do you think?

@mhanberg It's awesome that you found the issue tracked in chromedriver!
I agree with @keathley 's comment from here: https://github.com/keathley/wallaby/issues/346#issuecomment-404176302
I think we should document this behavior, link to the chromedriver issue and close this PR. But I think this should be documented here instead of the README, we should clean up the README instead of adding things to it: https://hexdocs.pm/wallaby/Wallaby.Browser.html#fill_in/3


Change mesos-server POM to inherit from Spring Boot parent

As a developer, I'd like to change the mesos-server pom.xml to inherit the foundation bits from Spring Boot parent itself.

I think this has become irrelevant and something similar to https://github.com/spring-cloud/spring-cloud-dataflow-server-cloudfoundry/pull/219 should be done instead. Correct?

Yes, will change this issue to reflect that.


Add an interactive mode.

An interactive mode will walk the users through the action they want to achieve.
Two options:

Do it globally

Eg: pb -i or pb --interactive

Do it for every command individually.

Eg: pb add -i, pb find -i, etc.

Every command will have instructions and prompts to walk the user through the action.
On getting and validating data from the interactive command, it can be handed off to existing commands to do the work.
Eg:$ pb find -i
Find record(s) based on e-mail or first name? (e/n): e
Enter the e-mail ID<EMAIL_ADDRESS>
# Internally give the command `pb find -e<EMAIL_ADDRESS>

Credits: @KartikSoneji

Have a global interactive mode, you don't need separate behaviour for each command.

you don't need separate behaviour for each command.

Even if I did have to implement something very different for every command, I could still use a global interactive mode and hand off the handling to different functions. I'm not understanding your argument for a global interactive mode versus a per-command interactive mode.
Thinking more makes me realise that something like Git doesn't have a global interactive mode, but only has it for commands that need it, like git rebase. I think the same logic can apply here. For the command pb display, no input is required, so it doesn't really require an interactive mode. All the other commands (pb add, etc.) have a user input, so an interactive mode might be specifically required for them. This can be an argument in favour of a per-command interactive mode.
What do you think @KartikSoneji?

When I say interactive mode, I mean something like diskpart.

Can you please elaborate more? I looked up diskpart and ran a few listing commands.


Add social image to GitHub repo

I whipped one up recently.
https://github.com/oktadeveloper/okta-blog/blob/main/_source/_assets/img/cli/okta-cli.png

Done!


Allow testing of children using 'caller' in review application and tests

Some of our components allow nesting using https://mozilla.github.io/nunjucks/templating.html#call.
We currently can't show this in the guide or tests, so this functionality could break.
For example https://github.com/alphagov/govuk-frontend/pull/509 we do not have coverage for 'caller'
We would need to

Allow the review application to show 'caller' examples
Allow the tests to test 'caller' examples

I've spiked this out: https://github.com/alphagov/govuk-frontend/compare/spike-expose-caller-in-review?expand=1
You can see in the current way our application is structure it results in duplication of logic in three places. I'd recommend we refactor app.js to have a unidirectional data flow.
Then share the rendering of components between the HTML Code examples, the iFrame preview and the test render helper.

As long as we have test coverage, I don't think we need to have examples in the review app, as neither the generated HTML nor the styling should differ from any other example.
So I'd suggest scoping this to just making sure we have tests that cover the {% call %} use case.

This has been implemented


Changing the DMatrix based on some column

Is there any way so that we can change the DMatrix content after loading them using xgboost?

no, dmatrix is made minimum for speedup the training, but not for data manipulation. Try to use other data processing tools like dataframe, numpy, before converting the final results to dmatrix

@tqchen: are there any current design restrictions that could prevent implementing the functionality to change a single feature in a DMatrix, in a manner that would be faster than recreating the whole thing (at least in a non-distributed case)?
There are quite a few potential applications for which being able to quickly change the values of a single feature would be very beneficial, e.g., computing partial dependencies, or various permutation-based approaches to feature importance.

@khotilov It is possible, with a bit deeper integration.

It is hard with current DMatrix memory layout.
It is possible by subclassing the https://github.com/dmlc/xgboost/blob/master/include/xgboost/data.h#L178 and change the certain column on the fly.
We can even directly expose say dataframe as a datasource, which re-uses the memory layout in dataframe and allow manipulations

@tqchen Thanks for the hints. Which one is the both convenient and fast to modify? Any instructions on the modification are highly appreciated.


[BUG] Creating a new item with Enter makes change in indent of the existing item

Describe the bug
When creating a new item with Enter key at the beginning of a line, indent of the existing item seems to be changed according to indent of the next line.
To Reproduce
Steps to reproduce the behavior:
1.

item 1        ← hit Enter key at the beginning of the line

item 2

(New item)

item 1
item 2
indent of item 1 changes.
(Then, reverse indenting item1 changes the order of items.)

Expected behavior
The state of indent of newly generated line by hitting Enter should be the same as the existing line.
Desktop (please complete the following information):

OS: windows 10
Obsidian Version: 0.11.9

Additional context
Sorry for my poor English,
and thank you for your wonderful plugin!

@iiz00 Thank you for your contribution!
Fixed in https://github.com/vslinko/obsidian-outliner/releases/tag/1.0.7


Framework Init - Logging

Based on template in #78, add support to initialize the logging.

Part of epic #74


Dynamic Inventory

Note: This is for the vagrant provisioner.
Support dynamic inventory, similar to /contrib/ansible/vagrant

This must differ because they use vagrant to bring up managed nodes, where we use Virtual Box's CLI.

Will have to update the create_cluster/cluster.sh script to create the proper inventory file that one could have to copy into the gem_master. The cluster script is who is creating the managed nodes for us and they would be the one's who know what names / IPs should be included in the inventory file

possibly scp it into the master or some other protocol (cannot used sync'd folders since CoreOS does not support it

Since they don't have any master and are creating those machines in vagrant they can.
Upstream's Steps

Bring up cluster
Run setup.sh

Here are our steps:

For this virtualenv, the master must be provisioned first (it makes the ssh key, and gets PXE boot in place).
Then we need to start up blank machines, wait for them all to PXE boot.
Ensure the inventory file reflects our cluster
Then we can run the setup.sh script

We could modify the cluster.sh script to start machines. Log into the master, set up the inventory file and wait for all to PXE boot, then run setup.sh

This issue will be addressed by Collins when gemini is merged into Contiv Cluster Manager

@stephenrlouie is this still an issue?

I think its something that we need to do, but not high priority. We can keep it open for tracking purposes


Query generation not generating nullable types

go version go1.8 linux/amd64
psql (PostgreSQL) 9.6.2
Ubuntu 14.04.5 LTS

We're having trouble generating the go code for queries that select from multiple tables and/or views. Sample code and schema are below.
SQL
BEGIN;
CREATE TABLE "occurence_date" (
        occurence_date_id SERIAL PRIMARY KEY,
        occurence_date DATE UNIQUE
);

CREATE TABLE "note" (
        note_id SERIAL PRIMARY KEY,
        note TEXT
);

CREATE TABLE "user_case" (
        user_case_id SERIAL PRIMARY KEY,
        occurence_date_id INTEGER NOT NULL REFERENCES occurence_date("occurence_date_id"),
        note_id INTEGER REFERENCES note("note_id")
);
COMMIT;

CLI

xo<EMAIL_ADDRESS>-N -M -B -T SampleDateID -o $GOPATH/src/nycds-database/pddb/models/ << ENDSQL
SELECT occurence_date, note
FROM user_case
LEFT JOIN note USING (note_id)
LEFT JOIN occurence_date USING (occurence_date_id)
ENDSQL

The created go file sampledateid.xo.go generates string as a type for the note field although in the database the type allows for NULLs. We expected it would generate a sql.NullString, but weren't able to find a way to set the type.

I'll take a look and see what the issue is.

Any luck? Thanks!

Sorry, finally got around to this. This is an issue that actually I was aware of before, and I had added the --query-fields command line option so that one could manually override the types used. I know this is not ideal, but at least it can work temporarily. I'm trying to figure out where if I can fix the logic associated with this.

Not sure if I can fix this or not. I know where in the code this happens, but I'm doing regression tests now on a bunch of different projects where this tool is used to see what the "effect" of fixing this is, if any.

This has been fixed by adding a --query-allow-nulls command-line option. Please note that not all databases will end up respecting this properly, primarily due to the "clever hack" xo uses to extract information about a query. I would highly recommend forcing the specific types via the --query-fields option, however, as it makes it more explicit about what is intended, and a developer will more readily be able to understand the discrepancy/relationship between the schema design and the code.
Note: this is not enabled by default, as I want to maintain backwards compatibility with the existing tool. The reason I had originally designed / done it like this, is for a variety of philosophical reasons when it comes down to database design (which don't need to be discussed here).
The xo code is really due for an overhaul ... !


Initial RDKE release for devicesettings

Compatible with devicesettings hal interface header 2.0.0

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.deepthi-ps seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


useRouter.hash isnt in SSR side

Environment
Working directory: /home/projects/nuxt-starter-3zqnfv                                                              9:10:18
Nuxt project info:                                                                                9:10:18

Operating System: Linux
Node Version:     v18.18.0
Nuxt Version:     3.8.0
CLI Version:      3.9.1
Nitro Version:    2.7.0
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      devtools
Runtime Modules:  -
Build Modules:    -

👉 Report an issue: https://github.com/nuxt/nuxt/issues/new                                                        9:10:18
👉 Suggest an improvement: https://github.com/nuxt/nuxt/discussions/new
👉 Read documentation: https://nuxt.com
Reproduction
https://stackblitz.com/edit/nuxt-starter-3zqnfv
Describe the bug
If i open this reproduction, the variable isHash is correct.
If i added "#description" the variable isHash is false, but there is a hash!!!

If i clicked the button works ok!
Additional context
No response
Logs
No response

Hey there! I have a suggestion that could help. Try adding "immediate: true" to the watch function like this:
watch(
  () => route.hash,
  () => {
    if (route.hash == `#description`) isHash.value = true;
  }, {immediate: true}
);

This adjustment will enable to execute your watcher on initial load which will check for the presence of "description" in the hash. Additionally, your button will continue to function properly when clicked. Hope this helps!
If you need more informations: https://vuejs.org/guide/essentials/watchers.html#eager-watchers

But route.hash in SSR mode is empty ¿really?
Why all parameters of route (useRouter()) are filled but hash is empty in SSR mode?

The reason for this behavior is related to the functioning of SSR. When a page is rendered on the server side, the fragment identifiers (the part that comes after the hash symbol) are not sent to the server. These identifiers are used to identify specific sections within a page and scroll to it for example. Since this information is handled on the client side, the server doesn't need to be aware of it. As a result, when you use SSR, the initial page load will display everything including the full page, queries, etc., but the fragment identifier (hash) won't be visible.


Tutorials for Pod Security Admission

Creates a two part tutorial for Pod Security Admission with KinD:

Applying Pod Security Standards at Cluster level
Applying Pod Security Standards at Namespace level

/kind documentation
Notes for reviewers:

kind node image for v1.23 is not yet available here: https://hub.docker.com/r/kindest/node/tags
So the steps here are documented by building a kind Node image from source
We could hold this PR until v1.23 tag lands for kind or I can add a step / link on how to build Node image from source
Once v1.23 lands, can update the tutorial to reflect the correct version instead of latest tag

(open to feedback on other ways to tackle this of course :) )
Initial slack discussion: https://kubernetes.slack.com/archives/C1J0BPD2M/p1636152420159200

/cc @reylejano @shannonxtreme @savitharaghunathan

/sig security

Previews of updated pages:
https://deploy-preview-30422--kubernetes-io-main-staging.netlify.app/docs/tutorials/
https://deploy-preview-30422--kubernetes-io-main-staging.netlify.app/docs/tutorials/pod-security/
https://deploy-preview-30422--kubernetes-io-main-staging.netlify.app/docs/tutorials/pod-security/cluster-level-pss/
https://deploy-preview-30422--kubernetes-io-main-staging.netlify.app/docs/tutorials/pod-security/ns-level-pss/

/hold
Until merge timelines are aligned as per this comment: https://github.com/kubernetes/website/pull/30502#issuecomment-973301421

/sig auth

Thank you so much for the thoughtful feedback on the PR @shannonxtreme . All the feedback should be resolved with recent changes. It also refers to the link of blog post from #30502 right at the top of both tutorials (cc @jimangel @lachie83).
Only pending item I can think of is using busybox instead of nginx pod container image. I am happy to switch it post publication in Jan (since I am on PTO rest of December), if there are no concerns.
PR is currently on /hold for work on Blog PR to wrap up. Once that PR is merged, we can /unhold this assuming no more work or feedback is needed here :) Excited to se this all come together !!!

Mostly inline feedback. Things I marked as a nit wouldn't block a merge.
overall nit: I'd put these tutorials in the clusters directory, and then raise an issue (post-merge) to rename clusters to security. The AppArmor and seccomp tutorials are just as much about security as the PSA one.

Thank you @sftim for helping me discover the examples directory under docs :) I did not know it existed before. Removed the references to gists and moved them to examples. Also accepted vast majority of the nits.
Issue for merging clusters tutorials with security is also here: https://github.com/kubernetes/website/issues/30778

/label tide/merge-method-squash

/approve
The intent of this PR is right on target.

Thank you Jim, Tim and Shannon. Accepted all inline changes from phone app. Will do some final clean up today/tomorrow when I get on Wi-Fi. After that we should be in good shape to publish this together with the blog!

Alright, just pushed the final changes that takes care of all the pending actionable feedback.
Now that blog post PR is merged, just need someone to /hold remove and /lgtm on or before publish date for the blog (Dec 09)

/check-cla
/easycla

Hold from https://github.com/kubernetes/website/pull/30422#issuecomment-973654356 should stand until the blog article publishes.
Any time after 16:05 Pacific time on the 8th of December should be good to go, as the related blog article goes live at UTC midnight on the 9th.
It's also OK to PR an update to the publication time of that article if that makes the sync easier.

This is ready for a technical signoff from SIG Auth. It's already been through quite a few checks, including by me, so what I'm looking for is a final read-through and a formal /lgtm providing no concerns spotted.
In other words, there is no need to go through each step to verify.
Page previews:

Apply Pod Security Standards at Cluster level
Apply Pod Security Standards at Namespace level

LGTM for SIG Docs, and https://github.com/kubernetes/website/pull/30422#pullrequestreview-815339185 implies it also looks good to @shannonxtreme

/remove-label tide/merge-method-squash
Commits are already squashed

Technical content lgtm, had a non-blocking question about use of tmp and suggestion about calling out use of dry-run

Thanks @liggitt
Taking https://github.com/kubernetes/website/pull/30422#issuecomment-988840804 as
/lgtm
We can do a follow-up PR. I agree about taking care about using /tmp. There might be a way to improve on this.

LGTM too PJ, wonderful work here ❤
On Wed., Dec. 8, 2021, 18:09 Kubernetes Prow Robot, <
@.***> wrote:

LGTM label has been added.
Git tree hash: 377841f45aca39355245243a3391e41bda229ba5
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/kubernetes/website/pull/30422#issuecomment-988846119,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AHH4EFXXTM47JCWCLNJRBZDUP5RJLANCNFSM5HV7LZTQ
.

Blog is now published https://kubernetes.io/blog/2021/12/09/pod-security-admission-beta/
/hold remove

/hold cancel


Added support for using ROS parameters to spawn entities in Gazebo using ros_gz_sim::create

🎉 New feature
Closes #459
Summary
Added ROS parameters support in ros_gz_sim::create node, while preserving the existing behavior. ROS parameters will be checked first, if not found then will revert back to Gflags arguments.
Test it
Launch the demo launch file from the ros_gz_sim_demos package.
ros2 launch ros_gz_sim_demos robot_description_publisher.launch.py
Checklist

[x] Signed all commits for DCO
[ ] Added tests
[x] Added example and/or tutorial
[ ] Updated documentation (as needed)
[ ] Updated migration guide (as needed)
[ ] Consider updating Python bindings (if the library has them)
[x] codecheck passed (See contributing)
[x] All tests passed (See test coverage)
[x] While waiting for a review on your PR, please help review another open pull request to support the maintainers

Note to maintainers: Remember to use Squash-Merge and edit the commit message to match the pull request summary while retaining Signed-off-by messages.

@ahcorde can you please review it for approval?

@ahcorde approval required for the workflow, can you please look into it?

Thanks for the contribution, @Ayush1285! Is this a duplicate of #463?

Thanks for the contribution, @Ayush1285! Is this a duplicate of #463?
Just checked the other PR. I guess we both created PRs parallelly for the same issue.

@Ayush1285 , I've closed the other PR. Let's iterate on this one and get it merged.

Remove gflags on rolling too

Why are we removing gflags? Wouldn't this break a lot of launch files already out there?

maybe add a warning

do you mind to target rolling ? then we can backport the changes to humble and iron.

Yes, I've created a new PR #475 for rolling.

I will close this PR in favour of this PR on rolling


Update zio-schema, zio-schema-derivation to 1.0.1

About this PR
📦 Updates

dev.zio:zio-schema
dev.zio:zio-schema-derivation

from 0.4.17 to 1.0.1 ⚠
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "dev.zio" }
}]

labels: library-update, early-semver-major, semver-spec-major, commit-count:1

Superseded by #410.


Cinnamon v4.8

Motivation for this change
Technical progress

Finally, Cinnamon v4.8 is WIP
Things to figure out:

[ ] figure out dbus-glib removal
[x] solve startup issue
[ ] check if we should use cjs or pinned gjs with a symlink to cjs (there was discussion in cjs repo, seems to be mostly compatible)
[ ] test everything thoroughly

Bugs:
Feb 06 15:05:33 nixos pulseaudio[1135]: GetManagedObjects() failed: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

gkr-pam: couldn't unlock the login keyring.

Things done

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

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

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

I have a nightmarish review request :frowning_face: it involves the hashes in the updates.
It seems you're using a newer nix version, and its changed the hashes to
 sha256 = "sha256-4DMXQYH1/RjLhgrn55I7Vkk6+gGsR+OVmiwxVHUIyro=";

with the hash being in SRI format.
We should probably change this to
hash = "sha256-4DMXQYH1/RjLhgrn55I7Vkk6+gGsR+OVmiwxVHUIyro=";

instead.
And I say this with full knowing that I did this to the pantheon tree (a while ago) and now need to fix it :grin:

About the patch in cinnamon-session that you asked about, I think before it maybe required us to use elogind and not all the dbus-glib references were cleaned up. If I look at the buildsystem now https://github.com/linuxmint/cinnamon-session/search?q=elogind&type=code it's now optional and I think should work as intended.

@worldofpeace
The sha256 -> hash thing as a script:
find -iname "*.nix" -type f -exec sed 's|sha256 = "sha256|hash = "sha256|g' -i {} +

Other packages could benefit from this fix aswell, should I make a PR to run this over the whole tree?

This is a semi-automatic executed nixpkgs-review with nixpkgs-review-checks extension. It is checked by a human on a best effort basis and does not build all packages (e.g. lumo, tensorflow or pytorch).
If you have any questions or problems please reach out to SuperSandro2000 on IRC.
Result of nixpkgs-review pr 112147 run on x86_64-linux 1

14 packages built:

arc-theme
cinnamon.cinnamon-common
cinnamon.cinnamon-control-center
cinnamon.cinnamon-desktop
cinnamon.cinnamon-gsettings-overrides
cinnamon.cinnamon-menus
cinnamon.cinnamon-screensaver
cinnamon.cinnamon-session
cinnamon.cinnamon-settings-daemon
cinnamon.cinnamon-translations
cinnamon.cjs
cinnamon.muffin
cinnamon.nemo
cinnamon.xviewer

@ryantm Could you enable updates for cinnamon packages on the bot again, please?


Error while generating signed APK: "Error:(5) Error: "forecast_api_key" is not translated in "nl" (Dutch) [MissingTranslation]"

Error:(5) Error: "forecast_api_key" is not translated in "nl" (Dutch) [MissingTranslation]
Error:(7) Error: "static_maps_api_key" is not translated in "nl" (Dutch) [MissingTranslation]

The error doesn't happen when creating a non signed APK.
I did this:
<string name="forecast_api_key" translatable="false">myKey</string>
<string name="static_maps_api_key" translatable="false"></string>

This way it doesn't complain and the app works.

Ah, thanks for the headsup! To be honest I never built a signed apk for
speculum 😁
Op 8 apr. 2017 12:36 schreef "ordago"<EMAIL_ADDRESS>
Error:(5) Error: "forecast_api_key" is not translated in "nl" (Dutch) [MissingTranslation]
Error:(7) Error: "static_maps_api_key" is not translated in "nl" (Dutch) [MissingTranslation]
The error doesn't happen when creating a non signed APK.
I did this:
myKey

This way it doesn't complain and the app works.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/NielsMasdorp/Speculum-Android/issues/38, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AFsS1-21_ZiWFG-V94zgL9Eu-dPA8S22ks5rt2MSgaJpZM4M3qjq
.

Fixed in PR #40


init duplicate

We should support initialization with [Int] instead of only array literals.

Let me try to fix this up.


Fix buglet in script to test if port 445 is open

Fixes #42831

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

Fixes the first part of https://github.com/MicrosoftDocs/azure-docs/issues/42008

I also fixed the second part of #42008


the FSA autogenerated GitRepository can't pull private git repo

Hi,
When using FSA, a GitRepository resource with same ArgoCd application name will be created, while can't find a way to include GitRepository private ssh credential reference to Argo Kind Application.
May I know is there a way to setup global sourceref for all GitRepository resources in a specific namespace?
Thanks.

You would create Flux GitRepository with the credentials you'd like. Then you would go creating the applications inside Flamingo normally.
  brew install<EMAIL_ADDRESS>
  flux create source git <app-name> -n <namespace> \
<EMAIL_ADDRESS>\
    --branch=master \
    --private-key-file=./private.key

Please note that we haven't supported Flux v2.0.0-rc.1 yet.


ICNS integration

Add ICNS integration for cosmos-kit. This PR contains

@cosmos-kit/icns as a separated package
icns hooks in react package, let me know if it makes more sense to separate the hook logic out as it's own package (eg. @cosmos-kit/icns-react) or moved to @cosmos-kit/icns

The goal is to make it modular and not imposed itself as a default name service so developer can choose what they want.

Fixed according to the feedback, lmk if there is anything else to update @pyramation


Feiv: 2-Step IV Estimation procedure instead of 1-Step Estimator

Context
Currently, the Feiv class implements a "one-step" 2SLS estimator for instrumental variable estimation. For multiple first stage IV diagnostics of interest, this needs to be changed to a 2-Step estimator.
To do:

Update Fepois.get_fit() and Fepois.vcov() to be based on a 2-Step estimator.
This could be achieved by calling feols() twice or by implementing the 2-Step estimator by hand.

I will take this issue. Thanks.

We can close this =)


Fix that allows replays from custom maps to be viewed

I'll leave this here in case I die. The issue that discusses this PR is #309.

@googlebot I signed it!

Good feature. There are many PRs to be processed by the owner of PySC2, it seems the owner is not active recently.


Speed Up of spotdl objects gathering

Speed up gathering large quantities of spotdl Objects. Specifically for gathering artist tracks. Implementation was created in #935 and the issue was also addressed in #935

Use multiprocessing when SongObj.from_url()

Also add flag preliminary: bool to SongObj.from_url() for quick Spotify-only metadata gathering

Serialize masterClient into file for access outside main process.
Allow calling initialize() multiple times from different "processes" by serializing instance into file.

Results are approximately +4x faster.
Although there is still a blank wait for large collections, in the future this can utilize progressHandler to show messages and progress bars for collection status.

Closing in favor of asyncio over multiprocessing. I hope to recreate this fix/improvement with asyncio in the future


Refactor SPSA

Summary
Refactor the SPSA optimizer to allow more flexible options and prepare the structure for extensions such as 2-SPSA and QN-SPSA.
Details and comments
Most existing code--and all code in the tests--still works exactly as before.
Changes to before:

Instead of assuming powerlaws for the perturbation and learning rate, arbitrary sequences are now supported (e.g. constant)
The coefficients for the powerlaws cannot be passed in anymore, instead a generic iterator must be passed (a convience function is provided for that)

New options:

A blocking condition: only accept a new step if it improves the loss (modulo some allowed increase)
Using multiple gradient samples in each step instead of just one
Perturbing only a few dimensions instead of all
Setting a final tolerance and if the update step is smaller than the tolerance, stop
A callback function
Setting a trust region (update step is confined to the learning rate)

The particular structure of the code allows a straightforward extension to 2-SPSA and QN-SPSA, not included in this PR to keep it small.

Hi, I am migrating old code from qiskit-aqua.
With this refactoring, I am not sure how I should adapt the code below:
SPSA(maxiter=1000, c0=0.1, c1 = 0.01)
Could you help me?
Thanks!


Not able to add dropdown to Spreadsheet Cell using dataValidation property

Hi Folks,
I'm trying to display dropdown for a cell in Google Sheet using Nodejs code. I have added the DataValidationRule as mentioned in https://developers.google.com/sheets/api/reference/rest/v4/spreadsheets/cells#DataValidationRule as below. But this is not throwing any exception nor working as expected.
let cell = sheet.getCell(rowNumber, cellIndex)
cell.dataValidation = {
condition: {
type: 'ONE_OF_LIST',
values: [
{
userEnteredValue: 'DropdownValue1'
},
{
userEnteredValue: 'DropdownValue2'
}
]
},
inputMessage: "Choose any one from the list",
showCustomUi: true
}
await sheet.saveUpdatedCells();
Any insights on this would be much helpful!

Sorry but this is not yet supported in this module. Just setting it on the cell object like that won't actually do anything at the moment. Open to pull requests!

combined into #566


Collab window data looks pretty bad

This data suggests that

Client consume a lot of memory to track data about clients
Any kind of proposal may take forever
Summaries are larges (catchUp blob in sequence)
Search is not accurate for FFX / Sequences

In other words, a lot of things behave really badly, if these numbers actually represent the truth
Distance, number of ops
Office_Fluid_FluidRuntime_Performance
| where Event_Time > ago(5d)
| where Data_eventName contains "MsnStatistics"
| where Data_clientType == "interactive"
| summarize count(), percentile(Data_msnDistance, 25), percentile(Data_msnDistance, 50), percentile(Data_msnDistance, 90), percentile(Data_msnDistance, 95), percentile(Data_msnDistance, 99)

count_
percentile_25
percentile_50
percentile_90
percentile_95
percentile_99

60801
8
24
1094
2590
8411

Distribution graph (msnDistance) looks like proper hockey stick, but the tail is just enormously long.
Distance, duration
Office_Fluid_FluidRuntime_Performance
| where Event_Time > ago(5d)
| where Data_eventName contains "MsnStatistics"
| where Data_clientType == "interactive"
| summarize count(), percentile(Data_duration, 25), percentile(Data_duration, 50), percentile(Data_duration, 90), percentile(Data_duration, 95), percentile(Data_duration, 99)

count_
percentile_25
percentile_50
percentile_90
percentile_95
percentile_99

60782
41,321
176,843
1,929,970
6,202,287
66,444,955

Distribution graph (duration) does not look like proper hockey stick.
Office_Fluid_FluidRuntime_Performance
| where Event_Time > ago(5d)
| where Data_eventName contains "MsnStatistics"
| where Data_clientType == "interactive"
| where Data_duration < 1000000
| summarize count() by bin(Data_duration, 10)
| render linechart

First 100 second look even worse (bin size = 1):

Ok, from quick code inspection, it's clear that opSendTimeForLatencyStatisticsForMsnStatistics is not reset on disconnect, similar to how other things are reset in this file and tracked only for same connection. Something similar should happen
@markfields, can you please follow with a fix here? Should be simple one

Actually, assigning to Si :)


fixed issue no 2 and 10

fixed the newsletter section and also made navbar responsive and fixed the ui of navbar of small screen

Read #90
Please follow the guidelines.


Binary search algorithm

Hi @Tezze2001 ,
I have added binary search algorithm to the code base and I want add other different algorithms and data structures too in various programming languages.
I hope this PR is merged

Hi @Udbhav-regadamilli, we are happy to receive your pull request and we are happy to combine your work with ours.  We will accept your pull request as soon as we have set up the entire development environment. Also we are still define how to organize the code.
Our idea is to separate the implementation from the signature of the methods, so that we can create a common interface for each operation, for example: create a list of "abstract" classes and the various implementations in other classes.
Also we are intrested in which programming languages you want to implement other things.
Now we are working on a GitHub action that compiles, executes tests, creates a package and the end update the doc.

If you want continue to contribute, we can talk together on Discord, in this way we can easily explain our goals!
Thank you for your work 🥇 !

I can see only test file but not the other changes

Now I have committed the changes, please verify them.


Update docs for AB3 traces.

Codecov Report

Merging #67 (c711686) into master (492e7ba) will not change coverage.
The diff coverage is n/a.

@@            Coverage Diff            @@
##             master      #67   +/-   ##
=========================================
  Coverage     72.15%   72.15%
  Complexity      399      399
=========================================
  Files            70       70
  Lines          1232     1232
  Branches        125      125
=========================================
  Hits            889      889
  Misses          311      311
  Partials         32       32

Continue to review full report at Codecov.

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


Fix timestamp_nanos_opt to default

Codecov Report
Patch coverage is 66.66% of modified lines.
:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.

Files Changed
Coverage

src/storage.rs
66.66%

:loudspeaker: Thoughts on this report? Let us know!.


Visualize results

Hi,
Have you added a script to visualize the results ?

Hi @naufil601,
Have you reproduced the results? If yes, how dis you managed?
thanks in advance.


DEV:FsR:GetFromStore  can come from a 2.0 Client

The GET code cannot assume only <IP_ADDRESS> or <IP_ADDRESS> now; there can also be a 2.0 client.

2.0 is no longer in scope


Race condition: "Taking longer than usual to connect"

Version
NPM: "botframework-webchat": "^4.6.0"

botframework-webchat:bundle:variant = full
botframework-webchat:bundle:version = 4.6.0
botframework-webchat:core:version = 4.6.0
botframework-webchat:ui:version = 4.6.0

Describe the bug
When Web-chat loses connection to the server but connection is reestablished within 15 seconds (before the "Taking longer than usual to connect" message is shown) then the message will appear after the chat is connected again and never disappear.
The error appears to originate from a call to "sleep" within detectSlowConnectionSaga.js, where the RECONNECT_FULFILLED status in connectivitystatus.js is overwritten by CONNECT_STILL_PENDING, hence showing the message.

Steps to reproduce

Establish a connection
Go offline
Reconnect within 15 seconds

Expected behavior
The slow-connection-warning-message should not appear after 15 seconds if connection is already reestablished.

Hi @Curiousite. Thank you for the issue and the contribution! We'll review the pull request soon. See #2656 for updates.

I have repro-ed the issue in test and found the main cause in this code instead, detectSlowConnectionSaga.js.
The code did not take account into RECONNECT_FULFILLED or RECONNECT_REJECTED.
I am working on a proper fix and test case.
export default function* detectSlowConnectionSaga() {
  for (;;) {
    yield take([CONNECT_PENDING, RECONNECT_PENDING]);

    const connectivityRace = yield race({
-     fulfilled: take(CONNECT_FULFILLED),
+     fulfilled: take([CONNECT_FULFILLED, RECONNECT_FULFILLED]),
-     rejected: take(CONNECT_REJECTED),
+     rejected: take([CONNECT_REJECTED, RECONNECT_REJECTED]),
      slow: call(() => sleep(SLOW_CONNECTION_AFTER))
    });

    if ('slow' in connectivityRace) {
      yield put({ type: CONNECT_STILL_PENDING });
    }
  }
}


Error handling

Addressing this issue:
https://github.com/Activiti/Activiti/issues/1847
Depending on:
https://github.com/Activiti/activiti-cloud-service-common/pull/165

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.5 out of 6 committers have signed the CLA.:white_check_mark: erdemedeiros:white_check_mark: jx-activiti-cloud:white_check_mark: CTI777:white_check_mark: miguelruizdev:white_check_mark: salaboy:x: mergify[bot]You have signed the CLA already but the status is still pending? Let us recheck it.


readme中未找到启动训练的shell脚本和json文件

涉及的URL：https://github.com/mindspore-lab/mindcv/tree/main/configs/mobilenetv3
readme中未找到生成run_distribute_train_ascend.sh 和hccl_8p_01234567_<IP_ADDRESS>.json文件的说明，请补充。

please use python train.py as example. no json file

duplicate issue of #329  , we need to review the "distributed training command" part of README file for all models.

A recommended solution is to change all distributed training commands to mpirun mode. As follows:
mpirun -n 8 python train.py -c /path/to/config.yaml --data_dir=/path/to/data

All subsequent new models' PR should follow this rule.

fixed in #362 #367 #368  #369 #370


Date and Date32 type normalization with user's timezone

This resolves #295.

Hi @asimpson
PR is ready for review 🚀

@jkaflik this is looking great, coming together nicely 🏆 ! I left one comment re: testing.

@asimpson thanks! pushed changes for backend tests


Getting "Too Many Requests (HTTP error 429)" Error

I am getting this "Too Many Requests (HTTP error 429)" Error in my Link Checker when calling to external sites as shown below.

Is there a way to get this resolved or to skip displaying these in the output file using Liche arguments?

Did you activate 429 retry in your configuration?
See https://github.com/tcort/markdown-link-check#markdownlinkcheckmarkdown-opts-callback retryOn429 option

@NicolasMassart - I am using the Link Checker written by Peter Evans and unfortunately the -a and -r arguments don't seem to work in it.
Do I have another workaround?

Well it has nothing to do with our project then...or I misunderstood... Can you explain how your issue is related to tcort/markdown-link-checkbif you don't use it?

I am sorry, my bad. I opened this issue thinking this project can help me in case if it is also using Liche.
Will close it.


Adding responsiveness to the Blog Page

Under the issue i would like to set the responsiveness of the youtube videos post in the blog page .

Does this issue has been resolved @Mansi168 @MonalikaPatnaik ?


Wallet Contract: Token Recovery; Set forwarding operations; Auto update backlinks; Recovery address to authorize forwarding remaining funds; Wallet interfaces; Size reduction;

Note: https://github.com/polymorpher/one-wallet/issues/83


Prevent the build status from being "stuck" for pull requests

This reverts commit 315291911a55e528a9046ca321bbfd6bf67ddafb.
The current criteria for building pull requests prevents them from being rebuilt when the author pushes updates to their branch. I think this is the issue as seen in #78.
The issue is that it's waiting for a build related to new commits pushed by the author, but no build is being scheduled because the current criteria prevents it. The current criteria will only schedule builds when pull requests are opened or re-opened by external contributors. This reverts it back to the old criteria which will rebuild whenever authors push new commits to pull requests.
This does mean that pull requests created from branches local to the current repo will build twice which is what I think #58 tried to prevent. I'm not sure what the best way to fix that is.
CC: @ILiedAboutCake, since they tried to fix the original issue in #58.
Feel free to close if this is the behavior you want. But hopefully now at least you know why it is what it is!

i think you can remove the pull_request and only leave push
because it will result in running the build twice because both actions got triggered

i think you can remove the pull_request and only leave push
because it will result in running the build twice because both actions got triggered

So this is my understanding of it (and what I do for all of my repos):

push - pushes directly to the repo, which can only be done by the owner or administrator of the repo.
pull_request (without any types) - opening a pull request or pushes to it, which can be done by external contributors.

At the very least it should be evident that just having push doesn't seem to work to enable external contributors, since that is currently a criteria and it doesn't work.
This does mean that we'd get two builds when for example the owner (Destiny) pushes directly to a branch of the repo and then sets up a pull request based on this branch. This is usually acceptable.
See the documentation for more info on available events.

Don’t write a book about it I’m falling asleep

@udoprog thank you for explaining this <3


Report is creating errors when run with non ASCII characters

Hello
when I run script runscuba.ps1 report is empty
I have an error inputobject is value null ?
see extract powershell command
unable to parse input: yaml: invalid trailing UTF-8 octet
ConvertTo-Csv : Impossible de lier l'argument au paramètre « InputObject », car il a la valeur Null.                    Au caractère C:\scubaO365\ScubaGear-main\PowerShell\ScubaGear\Modules\Orchestrator.psm1:272 : 46                        + ...     $TestResultsCsv = $TestResults | ConvertTo-Csv -NoTypeInformation                                             +                                          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~                                                 + CategoryInfo          : InvalidData : (:) [ConvertTo-Csv], ParameterBindingValidationException                        + FullyQualifiedErrorId : ParameterArgumentValidationErrorNullNotAllowed,Microsoft.PowerShell.Commands.ConvertToCs     vCommand                                                                                ConvertTo-Csv : Impossible de lier l'argument au paramètre « InputObject », car il a la valeur Null.                    Au caractère C:\scubaO365\ScubaGear-main\PowerShell\ScubaGear\Modules\Orchestrator.psm1:272 : 46                        + ...     $TestResultsCsv = $TestResults | ConvertTo-Csv -NoTypeInformation                                             +                                          ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
if you have a solution ?
thanks

@hervecinetic was this fixed by the v0.2.0 release?

Took a quick look at this while I was renaming it.  I think the problem is that rego expects utf8 (per its error) but PowerShell ConvertTo-Json generates a .NET String, which is apparently a utf-16 based construct (and thus serializes as utf-16 bytes):
https://learn.microsoft.com/en-us/powershell/module/microsoft.powershell.utility/convertto-json?view=powershell-7.3
https://learn.microsoft.com/en-us/dotnet/api/system.string?view=net-7.0
Crutch, you may have already come to the same conclusion but in the event you haven't looked yet hopefully this is helpful.  This seems to be a candidate solution, but I don't have time to test it:
https://stackoverflow.com/questions/23256911/encode-a-string-in-utf-8

One more note on this one.  Orchestrator.psm1 is responsible for writing the unified string of provider data (from the various ConvertTo-Json calls) to a file using Set-Content
Set-Content by default encodes using "utf8NoBom", per documentation
So that explains why we weren't seeing utf-16 providersettingsexport.json, but not quite why rego can't parse the non-ascii characters.  So likely will need to reproduce this and then analyze the json encoding more carefully.  I'll leave it there, but wanted to post this update since this was nagging at me from earlier today.

Nice find.  Yes, I agree.  That seems the likely cause.  A fix may just be to change to UTF8 for encoding since that is what rego is expecting.

Changed all Set-Content to encode using utf8 or utf8NoBom if available.


Concurrent requests problem

Hi,
I confused some thing about using http proxy.
For example:
I use 2  proxy servers  access example.com at the same time.
<IP_ADDRESS>:1080 -> example.com
<IP_ADDRESS>:1080 -> example.com
If the first request(<IP_ADDRESS>:1080) finished loading resource of example.com, the second request(<IP_ADDRESS>:1080) will auto stop the work?  or just independent of each request.
I think it should not interfere with each other.
UPDATE: Seems splash will cancel to handle the same url if one of the thread has finished this work.

I also have this problem .  Is there any options in splash to disable  this ? @kmike


Electrs won't start after udpate

I updated to v1.8.0c but electrs isn't running. I've restarted the node and I've run sudo systemctl restart electrs to no effect. Can't exactly figure out what I should be doing from the logs
Nov 21 01:05:45 raspberrypi systemd[1]: Started Electrs.
Nov 21 01:05:45 raspberrypi electrs[50449]: Starting electrs 0.9.9 on aarch64 linux with Config { network: Bitcoin, db_path: "/mnt/hdd/app-storage/electrs/db/bitcoin", daemon_dir: "/home/electrs/.bitcoin", daemon_auth: UserPass("raspibolt", ""), daemon_rpc_ad>
Nov 21 01:05:45 raspberrypi electrs[50449]: [2022-11-21T01:05:45.286Z INFO  electrs::metrics::metrics_impl] serving Prometheus metrics on <IP_ADDRESS>:4224
Nov 21 01:05:45 raspberrypi electrs[50449]: [2022-11-21T01:05:45.286Z INFO  electrs::server] serving Electrum RPC on <IP_ADDRESS>:50001
Nov 21 01:05:45 raspberrypi electrs[50449]: [2022-11-21T01:05:45.373Z INFO  electrs::db] "/mnt/hdd/app-storage/electrs/db/bitcoin": 157 SST files, 37.605140975 GB, 4.69618748 Grows
Nov 21 01:05:51 raspberrypi electrs[50449]: [2022-11-21T01:05:51.693Z INFO  electrs::chain] loading 761248 headers, tip=0000000000000000000640e114b9e6272b9688178273e193ef957e02fad1069f
Nov 21 01:05:57 raspberrypi electrs[50449]: [2022-11-21T01:05:57.645Z INFO  electrs::chain] chain updated: tip=0000000000000000000640e114b9e6272b9688178273e193ef957e02fad1069f, height=761248
Nov 21 01:05:57 raspberrypi electrs[50449]: [2022-11-21T01:05:57.777Z INFO  electrs::db] closing DB at /mnt/hdd/app-storage/electrs/db/bitcoin
Nov 21 01:05:57 raspberrypi electrs[50449]: Error: electrs failed
Nov 21 01:05:57 raspberrypi electrs[50449]: Caused by:
Nov 21 01:05:57 raspberrypi electrs[50449]:     0: bitcoin p2p failed to connect: <IP_ADDRESS>:8333
Nov 21 01:05:57 raspberrypi electrs[50449]:     1: Connection refused (os error 111)
Nov 21 01:05:57 raspberrypi systemd[1]: electrs.service: Main process exited, code=exited, status=1/FAILURE
Nov 21 01:05:57 raspberrypi systemd[1]: electrs.service: Failed with result 'exit-code'.
Nov 21 01:05:57 raspberrypi systemd[1]: electrs.service: Consumed 19.409s CPU time.
Nov 21 01:06:57 raspberrypi systemd[1]: electrs.service: Scheduled restart job, restart counter is at 3.
Nov 21 01:06:57 raspberrypi systemd[1]: Stopped Electrs.
Nov 21 01:06:57 raspberrypi systemd[1]: electrs.service: Consumed 19.409s CPU time.
Nov 21 01:06:57 raspberrypi systemd[1]: Started Electrs.
Nov 21 01:06:58 raspberrypi electrs[57473]: Starting electrs 0.9.9 on aarch64 linux with Config { network: Bitcoin, db_path: "/mnt/hdd/app-storage/electrs/db/bitcoin", daemon_dir: "/home/electrs/.bitcoin", daemon_auth: UserPass("raspibolt", ""), daemon_rpc_ad>
Nov 21 01:06:58 raspberrypi electrs[57473]: [2022-11-21T01:06:58.022Z INFO  electrs::metrics::metrics_impl] serving Prometheus metrics on <IP_ADDRESS>:4224
Nov 21 01:06:58 raspberrypi electrs[57473]: [2022-11-21T01:06:58.022Z INFO  electrs::server] serving Electrum RPC on <IP_ADDRESS>:50001
Nov 21 01:06:59 raspberrypi electrs[57473]: [2022-11-21T01:06:59.601Z INFO  electrs::db] "/mnt/hdd/app-storage/electrs/db/bitcoin": 158 SST files, 37.605141779 GB, 4.696187481 Grows
Nov 21 01:07:05 raspberrypi electrs[57473]: [2022-11-21T01:07:05.701Z INFO  electrs::chain] loading 761248 headers, tip=0000000000000000000640e114b9e6272b9688178273e193ef957e02fad1069f
Nov 21 01:07:10 raspberrypi electrs[57473]: [2022-11-21T01:07:10.260Z INFO  electrs::chain] chain updated: tip=0000000000000000000640e114b9e6272b9688178273e193ef957e02fad1069f, height=761248
Nov 21 01:07:47 raspberrypi electrs[57473]: [2022-11-21T01:07:47.743Z INFO  electrs::db] closing DB at /mnt/hdd/app-storage/electrs/db/bitcoin
Nov 21 01:07:47 raspberrypi electrs[57473]: Error: electrs failed
Nov 21 01:07:47 raspberrypi electrs[57473]: Caused by:
Nov 21 01:07:47 raspberrypi electrs[57473]:     0: bitcoind RPC polling failed
Nov 21 01:07:47 raspberrypi electrs[57473]:     1: daemon not available
Nov 21 01:07:47 raspberrypi electrs[57473]:     2: JSON-RPC error: transport error: Didn't receive response data in time, timed out.
Nov 21 01:07:47 raspberrypi systemd[1]: electrs.service: Main process exited, code=exited, status=1/FAILURE
Nov 21 01:07:47 raspberrypi systemd[1]: electrs.service: Failed with result 'exit-code'.
 Maybe wrong Password B in the electrs config?
you can check your electrs config file here
sudo cat /home/electrs/.electrs/config.toml
Maybe check your bitcoind logs
sudo journalctl -fu bitcoind -n 200
or check your open ports for 8333
netstat -tupl | grep 8333

i think your bitcoind is not running. Check again with
sudo systemctl status bitcoind
If your bitcoind is not running, you should reflash your sd card

Looks like it's running:
bitcoind.service - Bitcoin daemon
Loaded: loaded (/etc/systemd/system/bitcoind.service; enabled; vendor preset: enabled)
Active: active (running) since Mon 2022-11-21 05:37:00 GMT; 12h ago
Process: 5924 ExecStartPre=/home/admin/config.scripts/blitz.systemd.sh log blockchain STARTED (code=exited, status=0/SUCCESS)
Process: 5941 ExecStartPre=/bin/chgrp bitcoin /mnt/hdd/bitcoin (code=exited, status=0/SUCCESS)
Process: 5945 ExecStart=/usr/local/bin/bitcoind -daemonwait -conf=/mnt/hdd/bitcoin/bitcoin.conf -datadir=/mnt/hdd/bitcoin -debuglogfile=/mnt/hdd/bitcoin/debug.log (code=exited, status=0/SUCCESS)
Main PID: 6017 (bitcoind)
Tasks: 17 (limit: 4531)
CPU: 55min 18.630s
CGroup: /system.slice/bitcoind.service
└─6017 /usr/local/bin/bitcoind -daemonwait -conf=/mnt/hdd/bitcoin/bitcoin.conf -datadir=/mnt/hdd/bitcoin -debuglogfile=/mnt/hdd/bitcoin/debug.log
Nov 21 05:33:48 raspberrypi systemd[1]: Starting Bitcoin daemon...
Nov 21 05:33:48 raspberrypi bitcoind[5945]: Warning: /mnt/hdd/bitcoin/bitcoin.conf:31 Section [main.main] is not recognized.
Nov 21 05:33:48 raspberrypi bitcoind[5945]: /mnt/hdd/bitcoin/bitcoin.conf:32 Section [main.main] is not recognized.
Nov 21 05:33:48 raspberrypi bitcoind[5945]: /mnt/hdd/bitcoin/bitcoin.conf:38 Section [main.main] is not recognized.
Nov 21 05:33:48 raspberrypi bitcoind[5945]: /mnt/hdd/bitcoin/bitcoin.conf:39 Section [main.test] is not recognized.
Nov 21 05:37:00 raspberrypi systemd[1]: Started Bitcoin daemon.

Looks like it's running:
bitcoind.service - Bitcoin daemon Loaded: loaded (/etc/systemd/system/bitcoind.service; enabled; vendor preset: enabled) Active: active (running) since Mon 2022-11-21 05:37:00 GMT; 12h ago Process: 5924 ExecStartPre=/home/admin/config.scripts/blitz.systemd.sh log blockchain STARTED (code=exited, status=0/SUCCESS) Process: 5941 ExecStartPre=/bin/chgrp bitcoin /mnt/hdd/bitcoin (code=exited, status=0/SUCCESS) Process: 5945 ExecStart=/usr/local/bin/bitcoind -daemonwait -conf=/mnt/hdd/bitcoin/bitcoin.conf -datadir=/mnt/hdd/bitcoin -debuglogfile=/mnt/hdd/bitcoin/debug.log (code=exited, status=0/SUCCESS) Main PID: 6017 (bitcoind) Tasks: 17 (limit: 4531) CPU: 55min 18.630s CGroup: /system.slice/bitcoind.service └─6017 /usr/local/bin/bitcoind -daemonwait -conf=/mnt/hdd/bitcoin/bitcoin.conf -datadir=/mnt/hdd/bitcoin -debuglogfile=/mnt/hdd/bitcoin/debug.log
Nov 21 05:33:48 raspberrypi systemd[1]: Starting Bitcoin daemon... Nov 21 05:33:48 raspberrypi bitcoind[5945]: Warning: /mnt/hdd/bitcoin/bitcoin.conf:31 Section [main.main] is not recognized. Nov 21 05:33:48 raspberrypi bitcoind[5945]: /mnt/hdd/bitcoin/bitcoin.conf:32 Section [main.main] is not recognized. Nov 21 05:33:48 raspberrypi bitcoind[5945]: /mnt/hdd/bitcoin/bitcoin.conf:38 Section [main.main] is not recognized. Nov 21 05:33:48 raspberrypi bitcoind[5945]: /mnt/hdd/bitcoin/bitcoin.conf:39 Section [main.test] is not recognized. Nov 21 05:37:00 raspberrypi systemd[1]: Started Bitcoin daemon.

think something is wrong with the config file... you should reflash your sd card or take a look into the bitcoind config file

Alright. This will be the third reflash but I'll do it and update here. First I'll check the config file though.

Re-flash didn't work. Electrs is still not running. Any other ideas? Where is the config file and what should I be looking for?

Ok, so its definitely an error on your existent ssd installation of electrs. Remove and install again should fix it. Maybe switch to the raspiblitz dev branch and update electrs to v0.9.10.

So I flashed the dev branch and ran commands from other tickets to update lnd and electrs. No change. I then deleted electrs (but kept the index) and re-installed. Still not running. I don't know what to do from here other than abandon my node and install from scratch, no recovery. Any other ideas?
For what it's worth, here's the output from sudo journalctl -u electrs
-- Journal begins at Wed 2022-07-20 12:10:51 BST, ends at Sat 2022-11-26 18:18:10 GMT. --
Nov 26 04:58:41 raspberrypi systemd[1]: Started Electrs.
Nov 26 04:58:41 raspberrypi electrs[28236]: Starting electrs 0.9.7 on aarch64 linux with Config { network: Bitcoin, db_>Nov 26 04:58:41 raspberrypi electrs[28236]: [2022-11-26T04:58:41.845Z INFO  electrs::metrics::metrics_impl] serving Pro>Nov 26 04:58:41 raspberrypi electrs[28236]: [2022-11-26T04:58:41.845Z INFO  electrs::server] serving Electrum RPC on 0.>Nov 26 04:58:46 raspberrypi electrs[28236]: [2022-11-26T04:58:46.865Z INFO  electrs::db] "/mnt/hdd/app-storage/electrs/>Nov 26 04:58:55 raspberrypi electrs[28236]: [2022-11-26T04:58:55.205Z INFO  electrs::chain] loading 761248 headers, tip>Nov 26 04:59:00 raspberrypi electrs[28236]: [2022-11-26T04:59:00.064Z INFO  electrs::chain] chain updated: tip=00000000>Nov 26 04:59:04 raspberrypi electrs[28236]: [2022-11-26T04:59:04.620Z INFO  electrs::db] closing DB at /mnt/hdd/app-sto>Nov 26 04:59:04 raspberrypi electrs[28236]: Error: electrs failed
Nov 26 04:59:04 raspberrypi electrs[28236]: Caused by:
Nov 26 04:59:04 raspberrypi electrs[28236]:     0: bitcoin p2p failed to connect: <IP_ADDRESS>:8333
Nov 26 04:59:04 raspberrypi electrs[28236]:     1: Connection refused (os error 111)
Nov 26 04:59:04 raspberrypi systemd[1]: electrs.service: Main process exited, code=exited, status=1/FAILURE
Nov 26 04:59:04 raspberrypi systemd[1]: electrs.service: Failed with result 'exit-code'.
Nov 26 04:59:04 raspberrypi systemd[1]: electrs.service: Consumed 23.242s CPU time.
Nov 26 05:00:04 raspberrypi systemd[1]: electrs.service: Scheduled restart job, restart counter is at 1.
Nov 26 05:00:04 raspberrypi systemd[1]: Stopped Electrs.
Nov 26 05:00:04 raspberrypi systemd[1]: electrs.service: Consumed 23.242s CPU time.
Nov 26 05:00:04 raspberrypi systemd[1]: Started Electrs.
Nov 26 05:00:04 raspberrypi electrs[36810]: Starting electrs 0.9.7 on aarch64 linux with Config { network: Bitcoin, db_>Nov 26 05:00:04 raspberrypi electrs[36810]: [2022-11-26T05:00:04.949Z INFO  electrs::metrics::metrics_impl] serving Pro>Nov 26 05:00:04 raspberrypi electrs[36810]: [2022-11-26T05:00:04.950Z INFO  electrs::server] serving Electrum RPC on 0.>Nov 26 05:00:06 raspberrypi electrs[36810]: [2022-11-26T05:00:06.804Z INFO  electrs::db] "/mnt/hdd/app-storage/electrs/>Nov 26 05:00:14 raspberrypi electrs[36810]: [2022-11-26T05:00:14.837Z INFO  electrs::chain] loading 761248 headers, tip>Nov 26 05:00:20 raspberrypi electrs[36810]: [2022-11-26T05:00:20.237Z INFO  electrs::chain] chain updated: tip=00000000>Nov 26 05:00:21 raspberrypi electrs[36810]: [2022-11-26T05:00:21.021Z INFO  electrs::db] closing DB at /mnt/hdd/app-sto>Nov 26 05:00:21 raspberrypi electrs[36810]: Error: electrs failed
Nov 26 05:00:21 raspberrypi electrs[36810]: Caused by:
Nov 26 05:00:21 raspberrypi electrs[36810]:     0: bitcoin p2p failed to connect: <IP_ADDRESS>:8333
Nov 26 05:00:21 raspberrypi electrs[36810]:     1: Connection refused (os error 111)
Nov 26 05:00:21 raspberrypi systemd[1]: electrs.service: Main process exited, code=exited, status=1/FAILURE
Nov 26 05:00:21 raspberrypi systemd[1]: electrs.service: Failed with result 'exit-code'.
Nov 26 05:00:21 raspberrypi systemd[1]: electrs.service: Consumed 20.721s CPU time.
Nov 26 05:01:21 raspberrypi systemd[1]: electrs.service: Scheduled restart job, restart counter is at 2.
Nov 26 05:01:21 raspberrypi systemd[1]: Stopped Electrs.
Nov 26 05:01:21 raspberrypi systemd[1]: electrs.service: Consumed 20.721s CPU time.
Nov 26 05:01:21 raspberrypi systemd[1]: Started Electrs.
Nov 26 05:01:21 raspberrypi electrs[44576]: Starting electrs 0.9.7 on aarch64 linux with Config { network: Bitcoin, db_>Nov 26 05:01:21 raspberrypi electrs[44576]: [2022-11-26T05:01:21.273Z INFO  electrs::metrics::metrics_impl] serving Pro>Nov 26 05:01:21 raspberrypi electrs[44576]: [2022-11-26T05:01:21.273Z INFO  electrs::server] serving Electrum RPC on 0.>Nov 26 05:01:21 raspberrypi electrs[44576]: [2022-11-26T05:01:21.351Z INFO  electrs::db] "/mnt/hdd/app-storage/electrs/>Nov 26 05:01:26 raspberrypi electrs[44576]: [2022-11-26T05:01:26.425Z INFO  electrs::chain] loading 761248 headers, tip>Nov 26 05:01:31 raspberrypi electrs[44576]: [2022-11-26T05:01:31.052Z INFO  electrs::chain] chain updated: tip=00000000>Nov 26 05:01:31 raspberrypi electrs[44576]: [2022-11-26T05:01:31.099Z INFO  electrs::db] closing DB at /mnt/hdd/app-sto>Nov 26 05:01:31 raspberrypi electrs[44576]: Error: electrs failed
Nov 26 05:01:31 raspberrypi electrs[44576]: Caused by:
Nov 26 05:01:31 raspberrypi electrs[44576]:     0: bitcoin p2p failed to connect: <IP_ADDRESS>:8333
Nov 26 05:01:31 raspberrypi electrs[44576]:     1: Connection refused (os error 111)
lines 1-49...skipping...
-- Journal begins at Wed 2022-07-20 12:10:51 BST, ends at Sat 2022-11-26 18:18:10 GMT. --
Nov 26 04:58:41 raspberrypi systemd[1]: Started Electrs.
Nov 26 04:58:41 raspberrypi electrs[28236]: Starting electrs 0.9.7 on aarch64 linux with Config { network: Bitcoin, db_path: "/mnt/hdd/app-storage/electrs/db/bitcoin", daemon_dir: "/home/electrs/.bitcoin", daemon_auth: UserPass("raspibolt", ""), daemon_rpc_ad>
Nov 26 04:58:41 raspberrypi electrs[28236]: [2022-11-26T04:58:41.845Z INFO  electrs::metrics::metrics_impl] serving Prometheus metrics on <IP_ADDRESS>:4224
Nov 26 04:58:41 raspberrypi electrs[28236]: [2022-11-26T04:58:41.845Z INFO  electrs::server] serving Electrum RPC on <IP_ADDRESS>:50001
Nov 26 04:58:46 raspberrypi electrs[28236]: [2022-11-26T04:58:46.865Z INFO  electrs::db] "/mnt/hdd/app-storage/electrs/db/bitcoin": 159 SST files, 37.605142583 GB, 4.696187482 Grows
Nov 26 04:58:55 raspberrypi electrs[28236]: [2022-11-26T04:58:55.205Z INFO  electrs::chain] loading 761248 headers, tip=0000000000000000000640e114b9e6272b9688178273e193ef957e02fad1069f
Nov 26 04:59:00 raspberrypi electrs[28236]: [2022-11-26T04:59:00.064Z INFO  electrs::chain] chain updated: tip=0000000000000000000640e114b9e6272b9688178273e193ef957e02fad1069f, height=761248
Nov 26 04:59:04 raspberrypi electrs[28236]: [2022-11-26T04:59:04.620Z INFO  electrs::db] closing DB at /mnt/hdd/app-storage/electrs/db/bitcoin
Nov 26 04:59:04 raspberrypi electrs[28236]: Error: electrs failed
Nov 26 04:59:04 raspberrypi electrs[28236]: Caused by:
Nov 26 04:59:04 raspberrypi electrs[28236]:     0: bitcoin p2p failed to connect: <IP_ADDRESS>:8333
Nov 26 04:59:04 raspberrypi electrs[28236]:     1: Connection refused (os error 111)
Nov 26 04:59:04 raspberrypi systemd[1]: electrs.service: Main process exited, code=exited, status=1/FAILURE
Nov 26 04:59:04 raspberrypi systemd[1]: electrs.service: Failed with result 'exit-code'.
Nov 26 04:59:04 raspberrypi systemd[1]: electrs.service: Consumed 23.242s CPU time.
Nov 26 05:00:04 raspberrypi systemd[1]: electrs.service: Scheduled restart job, restart counter is at 1.
Nov 26 05:00:04 raspberrypi systemd[1]: Stopped Electrs.
Nov 26 05:00:04 raspberrypi systemd[1]: electrs.service: Consumed 23.242s CPU time.
Nov 26 05:00:04 raspberrypi systemd[1]: Started Electrs.
Nov 26 05:00:04 raspberrypi electrs[36810]: Starting electrs 0.9.7 on aarch64 linux with Config { network: Bitcoin, db_path: "/mnt/hdd/app-storage/electrs/db/bitcoin", daemon_dir: "/home/electrs/.bitcoin", daemon_auth: UserPass("raspibolt", ""), daemon_rpc_ad>
Nov 26 05:00:04 raspberrypi electrs[36810]: [2022-11-26T05:00:04.949Z INFO  electrs::metrics::metrics_impl] serving Prometheus metrics on <IP_ADDRESS>:4224
Nov 26 05:00:04 raspberrypi electrs[36810]: [2022-11-26T05:00:04.950Z INFO  electrs::server] serving Electrum RPC on <IP_ADDRESS>:50001
Nov 26 05:00:06 raspberrypi electrs[36810]: [2022-11-26T05:00:06.804Z INFO  electrs::db] "/mnt/hdd/app-storage/electrs/db/bitcoin": 160 SST files, 37.605143387 GB, 4.696187483 Grows
Nov 26 05:00:14 raspberrypi electrs[36810]: [2022-11-26T05:00:14.837Z INFO  electrs::chain] loading 761248 headers, tip=0000000000000000000640e114b9e6272b9688178273e193ef957e02fad1069f
Nov 26 05:00:20 raspberrypi electrs[36810]: [2022-11-26T05:00:20.237Z INFO  electrs::chain] chain updated: tip=0000000000000000000640e114b9e6272b9688178273e193ef957e02fad1069f, height=761248
Nov 26 05:00:21 raspberrypi electrs[36810]: [2022-11-26T05:00:21.021Z INFO  electrs::db] closing DB at /mnt/hdd/app-storage/electrs/db/bitcoin
Nov 26 05:00:21 raspberrypi electrs[36810]: Error: electrs failed
Nov 26 05:00:21 raspberrypi electrs[36810]: Caused by:
Nov 26 05:00:21 raspberrypi electrs[36810]:     0: bitcoin p2p failed to connect: <IP_ADDRESS>:8333
Nov 26 05:00:21 raspberrypi electrs[36810]:     1: Connection refused (os error 111)
Nov 26 05:00:21 raspberrypi systemd[1]: electrs.service: Main process exited, code=exited, status=1/FAILURE
Nov 26 05:00:21 raspberrypi systemd[1]: electrs.service: Failed with result 'exit-code'.
Nov 26 05:00:21 raspberrypi systemd[1]: electrs.service: Consumed 20.721s CPU time.
Nov 26 05:01:21 raspberrypi systemd[1]: electrs.service: Scheduled restart job, restart counter is at 2.
Nov 26 05:01:21 raspberrypi systemd[1]: Stopped Electrs.
Nov 26 05:01:21 raspberrypi systemd[1]: electrs.service: Consumed 20.721s CPU time.
Nov 26 05:01:21 raspberrypi systemd[1]: Started Electrs.
Nov 26 05:01:21 raspberrypi electrs[44576]: Starting electrs 0.9.7 on aarch64 linux with Config { network: Bitcoin, db_path: "/mnt/hdd/app-storage/electrs/db/bitcoin", daemon_dir: "/home/electrs/.bitcoin", daemon_auth: UserPass("raspibolt", ""), daemon_rpc_ad>
Nov 26 05:01:21 raspberrypi electrs[44576]: [2022-11-26T05:01:21.273Z INFO  electrs::metrics::metrics_impl] serving Prometheus metrics on <IP_ADDRESS>:4224
Nov 26 05:01:21 raspberrypi electrs[44576]: [2022-11-26T05:01:21.273Z INFO  electrs::server] serving Electrum RPC on <IP_ADDRESS>:50001
Nov 26 05:01:21 raspberrypi electrs[44576]: [2022-11-26T05:01:21.351Z INFO  electrs::db] "/mnt/hdd/app-storage/electrs/db/bitcoin": 157 SST files, 37.605140975 GB, 4.69618748 Grows
Nov 26 05:01:26 raspberrypi electrs[44576]: [2022-11-26T05:01:26.425Z INFO  electrs::chain] loading 761248 headers, tip=0000000000000000000640e114b9e6272b9688178273e193ef957e02fad1069f
Nov 26 05:01:31 raspberrypi electrs[44576]: [2022-11-26T05:01:31.052Z INFO  electrs::chain] chain updated: tip=0000000000000000000640e114b9e6272b9688178273e193ef957e02fad1069f, height=761248
Nov 26 05:01:31 raspberrypi electrs[44576]: [2022-11-26T05:01:31.099Z INFO  electrs::db] closing DB at /mnt/hdd/app-storage/electrs/db/bitcoin
Nov 26 05:01:31 raspberrypi electrs[44576]: Error: electrs failed
Nov 26 05:01:31 raspberrypi electrs[44576]: Caused by:
Nov 26 05:01:31 raspberrypi electrs[44576]:     0: bitcoin p2p failed to connect: <IP_ADDRESS>:8333
Nov 26 05:01:31 raspberrypi electrs[44576]:     1: Connection refused (os error 111)
Nov 26 05:01:31 raspberrypi systemd[1]: electrs.service: Main process exited, code=exited, status=1/FAILURE
Nov 26 05:01:31 raspberrypi systemd[1]: electrs.service: Failed with result 'exit-code'.
Nov 26 05:01:31 raspberrypi systemd[1]: electrs.service: Consumed 18.463s CPU time.
Nov 26 05:02:31 raspberrypi systemd[1]: electrs.service: Scheduled restart job, restart counter is at 3.
Nov 26 05:02:31 raspberrypi systemd[1]: Stopped Electrs.
Nov 26 05:02:31 raspberrypi systemd[1]: electrs.service: Consumed 18.463s CPU time.
Nov 26 05:02:31 raspberrypi systemd[1]: Started Electrs.
Nov 26 05:02:31 raspberrypi electrs[53005]: Starting electrs 0.9.7 on aarch64 linux with Config { network: Bitcoin, db_path: "/mnt/hdd/app-storage/electrs/db/bitcoin", daemon_dir: "/home/electrs/.bitcoin", daemon_auth: UserPass("raspibolt", ""), daemon_rpc_ad>
Nov 26 05:02:31 raspberrypi electrs[53005]: [2022-11-26T05:02:31.277Z INFO  electrs::metrics::metrics_impl] serving Prometheus metrics on <IP_ADDRESS>:4224
Nov 26 05:02:31 raspberrypi electrs[53005]: [2022-11-26T05:02:31.277Z INFO  electrs::server] serving Electrum RPC on <IP_ADDRESS>:50001
Nov 26 05:02:31 raspberrypi electrs[53005]: [2022-11-26T05:02:31.383Z INFO  electrs::db] "/mnt/hdd/app-storage/electrs/db/bitcoin": 158 SST files, 37.605141779 GB, 4.696187481 Grows
Nov 26 05:02:36 raspberrypi electrs[53005]: [2022-11-26T05:02:36.195Z INFO  electrs::chain] loading 761248 headers, tip=0000000000000000000640e114b9e6272b9688178273e193ef957e02fad1069f
Nov 26 05:02:40 raspberrypi electrs[53005]: [2022-11-26T05:02:40.919Z INFO  electrs::chain] chain updated: tip=0000000000000000000640e114b9e6272b9688178273e193ef957e02fad1069f, height=761248
Nov 26 05:02:40 raspberrypi electrs[53005]: [2022-11-26T05:02:40.965Z INFO  electrs::db] closing DB at /mnt/hdd/app-storage/electrs/db/bitcoin
Nov 26 05:02:41 raspberrypi electrs[53005]: Error: electrs failed
Nov 26 05:02:41 raspberrypi electrs[53005]: Caused by:
Nov 26 05:02:41 raspberrypi electrs[53005]:     0: bitcoin p2p failed to connect: <IP_ADDRESS>:8333
Nov 26 05:02:41 raspberrypi electrs[53005]:     1: Connection refused (os error 111)
Nov 26 05:02:41 raspberrypi systemd[1]: electrs.service: Main process exited, code=exited, status=1/FAILURE
Nov 26 05:02:41 raspberrypi systemd[1]: electrs.service: Failed with result 'exit-code'.
Nov 26 05:02:41 raspberrypi systemd[1]: electrs.service: Consumed 18.523s CPU time.
Nov 26 05:03:41 raspberrypi systemd[1]: electrs.service: Scheduled restart job, restart counter is at 4.

Update: I just deleted the config files from my ssd and flashed anew and built from scratch. No recovery, new everything. Installed electrs and indexed, it's now running and can be connected to. Not sure what went wrong with my node above, but if all else fails, starting from the beginning (but keeping the blockchain on ssd) is a not too long way of getting past it.


Prediction result recovery

Hi,
I downloaded your prediction result mat, but I can not recover it correctly. I got a 142x697 image from predictions in mat. I plot it our but it's quite weird. All the images look like this example:

Is there anything I have to do before I save the data to png?

It seems that you need a matrix transpose.
The issue seems to be the row major/column major conventions used in different languages.


Add KeepRewardUnlocked Option in APuzzleImplementation

If the option is set to true, the reward should be permanently unlocked, even if one of the conditions' state turns to false.

Done!


default to localhost instead of rinkeby

@MicahZoltu @pgebheim

:thumbsup: aside from CI failures.

CI failures resolved in #127


Create get_gpos module, implement get-folder command, and add some module helper functions

I was initially going to have the get_gpos module have the ability to download all of them, hence the helper functions, but LDAP can only query certain GPO information, so it'd have to be another SMB module to download them all; however, the user can just take the GUID output from the module and pass it to --get-folder
get_gpos module:

--get-folder feature:

Would it be possible to detect a folder on a remote system? Than we could just integrate it into the existing get commands

Would it be possible to detect a folder on a remote system? Than we could just integrate it into the existing get commands

Well the current get-file command references a file, so what would we change it to? I think having them separate makes more sense.

Would it be possible to detect a folder on a remote system? Than we could just integrate it into the existing get commands

Well the current get-file command references a file, so what would we change it to? I think having them separate makes more sense.

Hmm yeah i was thinking about moving --get-file/--put-file maybe to --get/--put anyway and add some sort of deprecation warning for the old function. But of course that would only make sense if it is possible to do a smart download/upload.  But if it cant be changed by a fairly simple check or try&except call its fine i guess. I just try to limit the amount of options the smb protocol has, there are already a lot (too much imo)

I mean we are on SMB, imo its pretty clear what you are trying to achieve

Well I disagree with that... we have numerous options to get things such as users, groups, disks, computers, etc all under the SMB protocol.

I mean we are on SMB, imo its pretty clear what you are trying to achieve

Well I disagree with that... we have numerous options to get things such as users, groups, disks, computers, etc all under the SMB protocol.

That is true but it is still listed in the Options for put and get remote files. Also the options have descriptions & we have a wiki. Imo that should be enough, but if its not

why the heck did i/it close it lol


Target class does not exist (Controller not found)

Q
A

Bug?
yes

New Feature?
no

Framework
Laravel

Framework version
7.x

Package version
3.x.y

PHP version
7.3.18

Actual Behaviour
Whenever I try to load a class it will always display an error that Target Class is not found even I have specified the exact location of the file.
$api = app('Dingo\Api\Routing\Router');
$api->version('v1', function ($api) {

    // This Will Work
    // $api->get('hello', function() {
    //     return "hi";
    // });

    //Will not work
    $api->get('hello', 'app\Http\Controllers\TestController@index');
    // $api->get('hi','app\Api\Controllers\TestController@index');
});

Error Message:
message: "Target class [app\Http\Controllers\TestController] does not exist.", status_code: 500,
Screenshot of the File location

Expected Behaviour
In the TestController it should only display a "hi" text. However I can only display the "hi" text if I write in on the route api.php
Steps to Reproduce
Possible Solutions
Not sure

Found the Issue
On my route 'hello' the name of path Should have a capitalized first letter. App\Http\Controller\.. instead of app\Http\Controller\..

Glad you solved it!


Add meta block extraction functionality

Add option extractMetas, working just like extractScripts and extractStyles but for meta tags :smile:

Thank you!


Add informative comment delineating class purpose

Changes in this PR
Added an informative comment delineating the purpose of the Agent class and what it means in Business terms to minimise confusion.

You don't have to worry about adding this so I have removed it from your PR description. The template includes reminders of our definition of done btw.
## Screenshots of UI changes

`N/A` Nothing visual

## Next steps

`N/A` Merge PR


Search Consortia feature does not work in COINSTAC production

Self explanatory

@spanta28 Please attach the screenshot or video.

https://user-images.githubusercontent.com/5415931/210621577-e7d06bff-cdab-4ccc-9f27-e494be7e184a.mov


doc: shared IP inconsistency

Description
This PR fixes shared IP inconsistency in the documentation.
Fixes # (issue)
Type of change
Please delete options that are not relevant.

[x] Bug fix
[ ] New feature
[ ] Refactor/improvement
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[x] This change requires a documentation update

How Has This Been Tested?
N/A
Checklist

[x] My commit message is conventional
[x] I have run pre-commit on all files before creating the PR
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[x] I have checked my code and corrected any misspellings

Codecov Report

Merging #404 (91c6351) into develop (fe3c7db) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff            @@
##           develop     #404   +/-   ##
========================================
  Coverage    86.92%   86.92%
========================================
  Files           23       23
  Lines         1400     1400
========================================
  Hits          1217     1217
  Misses         183      183

Continue to review full report at Codecov.

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


(sourcetree) Update the package to latest

Description
This will self update from the package nuspec file for minimal net traffic.

Motivation and Context

If it fixes an open issue, please link to the issue here. #1641

How Has this Been Tested?

Locally in a Intranet and appveyor
Screenshot (if appropriate, usually isn't needed):
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Migrated package (a package has been migrated from another repository)

Checklist:

[x] My code follows the code style of this repository.
[ ] My change requires a change to documentation (this usually means the notes in the description of a package).
[ ] I have updated the documentation accordingly (this usually means the notes in the description of a package).
[ ] I have updated the package description and it is less than 4000 characters.
[x] All files are up to date with the latest Contributing Guidelines
[x] The added/modified package passed install/uninstall in the chocolatey test environment.
[x] The changes only affect a single package (not including meta package).

Original Location

Original Repository
Open Issues Add the different issues underneath, and tick those that are fixed in this PR

[x] Issue 1 #1641
[ ] Issue 2 Link

[ ] Include the link to the opened PR that removes the package from the original location
[ ] The migration guidelines have been followed

:white_check_mark: Package verification completed without issues. PR is now pending human review

@wget do you have a minute to look over the changes here, as you are the one that has mostly been working on this package?

@wget do you have a minute to look over the changes here, as you are the one that has mostly been working on this package?

@AdmiringWorm
Are you sure about wget being the one that has mostly been working on this package? The history for the package doesn't list them at all. It does list @pascalberger as a contributor.
(FYI: wget hasn't been seen on github for over 2 weeks)

@RedBaron2 yeah, you are right. I mixed up the packages. Somehow I thought it was the LibreOffice packages, sorry about that.
@pascalberger do you have the time to look over the changes?

@TheCakeIsNaOH
https://github.com/chocolatey-community/chocolatey-packages/issues/1641#issuecomment-1089114023

@RedBaron2 this is working for me: (Invoke-WebRequest -UseBasicParsing -Uri "https://www.sourcetreeapp.com/").links | ? href -match "exe" | select -First 1 -ExpandProperty href and spits out https://product-downloads.atlassian.com/software/sourcetree/windows/ga/SourceTreeSetup-3.4.9.exe.
With -UseBasicParsing, powershell does not use IE.
Then version can be gotten out of that URL, and the enterprise package URL contructed.

@TheCakeIsNaOH
Their website has been known to have things work, and then other times have the website be sourced as JavaScript. Please test again in a few days.

@TheCakeIsNaOH @pauby
The package installs the msi file and not the exe
FYI: The current version of the package updated on 2 June 2022 to the 3.4.9 version
This PR can be put on hold for now since the sourcetree website seems to be working as of now.

This PR can be put on hold for now since the sourcetree website seems to be working as of now.

I'll move it to draft in the meantime.

Sourcetree looks to not updating anymore (CCR version is 3.4.9 and the latest available is 3.4.10). Taking this out of draft.

This update updated my version of this package without any errors.

I'm going to close this PR due to IRL responsibilities that are more urgent. I'll probably not be returning to this PR. I make the suggestion for putting it "up for grabs".


Specify MultiQC modules to run

We can speed up the MultiQC execution a little by specifying which modules to run in the config file.

Good idea!
The command in question:
--tag RNA


Category selection screen disappears after accepting permission

Install the app
Push Gallery button, choose pic to upload
Enter description, save
Categories selection screen is empty, with a bottom thing asking for a permission (location I think?), press it
Accept the permission
The screen disappear, back to the gallery, no way to enter categories

I guess this only happens once, but it probably confuses everyone trying the app for the first time.
It might also give the impression that not filling categories is OK.

Should have been fixed, please let me know if anyone is still experiencing this.


Listing large amount of metadata is slow

Purpose
Feature request
Description
Listing metadata of 3k files with pydtk db list files is very slow though pydtk db list files --parsable finishes within a reasonable time.
It seems that creating DataFrame in DBHandler is a bottleneck.
Symtem info [Optional]

Commit: f8e5d33ccf4839f96c59e40bf202d0a5a9d475cc
Ubuntu 18
DB: MongoDB

/meow

@d-hayashi:

In response to this:

/meow

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

/woof

/woof

@d-hayashi:

In response to this:

/woof

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

This function is taking a long time to return DataFrame.
https://github.com/dataware-tools/pydtk/blob/5a639aae3aa07d65ed6a27f578e8736effc133be/pydtk/db/v4/handlers/meta.py#L277

The default value is--limit=20, which is a reasonable time if not specified.


Update hyperparameter.md

Related Issue

Supports #ISSUE_NUMBER
Related PRs

This PR is not dependent on any other PR
What does this PR do?

Description of Changes

What gif most accurately describes how I feel towards this PR?

Changes read fine.


Add possibility to query for job results

The startCommand() methods return opaque job ids. These commits introduce a new client methods queryJobResult(), which enable querying for the results of those jobs.
The Connection class was extended by one method, enabling the creation of GET requests.

Hello and thanks for contributing! It is very much appreciated that you are proposing a patch to actually extend the functionality of the library. It would be very nice though if you could fix the formatting of your patch according to our project guidelines as well as regarding the inline comments. The most important formatting rules can be found in the [README] (https://github.com/SUSE/saltstack-netapi-client-java/blob/master/README.md), let me know if you have any questions.
Please note further that we agreed on a [convention about naming the library methods] (https://github.com/SUSE/saltstack-netapi-client-java/pull/15#issuecomment-74485966). While the currently proposed method name queryJobResult() is quite OK, I would propose to change it to getJobResult().

Hey @sschober, thanks for this PR!
We like the content and could find no obvious problem with it, so we will gladly merge your contribution.
There are still some smaller style issues here and there though, so I will add inline comments - in general my recommendation (even in other OSS projects) is to copy whatever style you see in surrounding code.
Thanks in advance!

@moio
I've tried to address all your concerns, rebased and pushed a new version.

@sschober: thanks for this PR! Merged manually.
Please note I added two further nitpicks with b34c9d8 :-)


Sitemap

Created sitemap based on @navigation with depth 4.
Browse the /sitemap to see result.

Works like a charm!


Update ds4drv & deps

Extracted from https://github.com/NixOS/nixpkgs/pull/16313

(Note that I don't use these packages myself ...)

@Mic92 I've moved the expressions. Does it look okay to you? If so I'll squash this up and integrate it.


there is a problem with loading our login plage.

When the exception was thrown, this was the stack:
#2      Element.markNeedsBuild (package:flutter/src/widgets/framework.dart:3867:12)
#3      State.setState (package:flutter/src/widgets/framework.dart:1168:14)
#4      _SpinKitPouringHourglassState._repaint (package:flutter_spinkit/src/pouring_hour_glass.dart:76:27)
#5      AnimationLocalListenersMixin.notifyListeners (package:flutter/src/animation/listener_helpers.dart:124:19)
#6      AnimationController._tick (package:flutter/src/animation/animation_controller.dart:788:5)
...
The AnimationController notifying listeners was: AnimationController#d0999(▶ 0.420)
════════════════════════════════════════════════════════════════════════════════════════════════════
════════ Exception caught by animation library ═════════════════════════════════════════════════════
'package:flutter/src/widgets/framework.dart': Failed assertion: line 3867 pos 12: '_debugLifecycleState != _ElementLifecycle.defunct': is not true.
this is happened after loading UI. but UI is perfectly loading.

A TextField widget or the Animation Controller might cause that problem. Have you disposed all controllers in dispose?

Hi @prabuddhafernando
can you please provide your flutter doctor -v and flutter run --verbose?
Also, to better address the issue, would be helpful if you could post a minimal code sample to reproduce the problem
Thank you

Hi @prabuddhafernando
Without additional information, we are unfortunately not sure how to resolve this issue. We are
therefore reluctantly going to close this bug for now. Please don't hesitate to comment on the
bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.


feat: add argc plugin to registry

Adds an asdf plugin for Argc, an open-source Bash CLI framework: https://github.com/sigoden/argc
Also PR'd to asdf-plugins: https://github.com/asdf-vm/asdf-plugins/pull/1061

Does it work with ubi?

yes, it works with ubi. But to use it with ubi I have to add extra tools to install ubi itself
[tools]
rust = "1.82.0"
ubi = "0.1.2"
"ubi:sigoden/argc" = "v1.20"

Also, I can just use rust to install argc without ubi
[tools]
rust = "1.82"
"cargo:argc" = "v1.20"

But I think a much simpler way to install argc is to use asdf backend
[tools]
argc = "1.20"
[plugins]
argc = "https://github.com/rgeraskin/asdf-argc"

This PR is aimed to drop the need of [plugins] section in .mise.toml

ubi is built into mise itself so it does not need to be separately installed

thanks, I've used an outdated mise. Works great with ubi!

You can still add it to the registry with ubi


Japanese translation

Japanese translation with test case.

Looks great! Merging this in and we'll have it live sometime during the day today.

FYI, the ISO 639-1 code for Japanese is ja (oddly), so we'll be renaming these files for the release.


About custom training and inference

感谢作者的优秀工作，并且在这分享实现给大家！
我刚刚看了你的视频演讲回放，讲得很棒！
我正在做3D pose的应用，有一些问题想请教一下：

因为是做应用，所以比较关注estimator。我们在推理的时候，能不能只用estimator？是否还得配合着imitator来用使得这个动作序列更逼真一些？用和不用imitator做推理（不是训练）在性能上差多少呢？
关于整个framework，我自己理解是这三个模块结构上是可拆解替换的是吗？也就是我可以自定义修改estimator的实现，然后用pretrained的imitator和hallucinator来单独训练estimator的是吗？

当然了，我做的应用是自用小工具，非商业项目。

Hi, thank you for the interest.

我们在推理的时候，能不能只用estimator？是否还得配合着imitator来用使得这个动作序列更逼真一些？用和不用imitator做推理（不是训练）在性能上差多少呢？

Yes, the estimator_inference folder is estimator only.
Indeed, the RL based imitator can perform physical correction as suggested in PPT: imitator page.
However, the imitor in my work is offline setting, if you want real-time, you need to check the previous work SimPoE.
The performance difference, in my case, with imitator the artifacts is better, but the p2 is worse as physical constrain is involved, you may check other related physical aware works mentioned in  the PPT.

关于整个framework，我自己理解是这三个模块结构上是可拆解替换的是吗？也就是我可以自定义修改estimator的实现，然后用pretrained的imitator和hallucinator来单独训练estimator的是吗？

Yes, the framework is new, but the three modules are flexible, as long as you can link them together.
The goal of imitator and hallucinator is for plausibility and diversity, so use the pretrain or train from scratch both are okay.
One more suggestion: this work is under self-supervised setting (only use 2D data), if you want to use it for application, involve more GT 2D-3D data would be better.

One more suggestion: this work is under self-supervised setting (only use 2D data), if you want to use it for application, involve more GT 2D-3D data would be better.
为什么呢？按我的理解，imitator+hallucinator增广出来的3D数据投影成2D的数据之后，这个2D-3D pair对于estimator来说就已经是GT了呀，它甚至要比真实传感器采集的数据要更准（系统误差等）。是因为hallucinator生成的序列也是基于初始的序列，所以需要更多的初始动作增加多样性吗？

The projected 2D-3D pose pair can be considered as GT pairs. However, its quality is still somehow not as good as the real GT (e.g., H36M GT data), which can be seen from the performance table. 1.
so involve them will be better.

了解啦，谢谢！


Use composite action

https://github.blog/changelog/2020-08-07-github-actions-composite-run-steps/
https://docs.github.com/en/actions/creating-actions/creating-a-composite-run-steps-action

error msg:
##[error]CyberAgent/cmaes/composite-action/benchmark/action/action.yml (Line: 13, Col: 5): Unexpected value 'uses'
##[error]CyberAgent/cmaes/composite-action/benchmark/action/action.yml (Line: 14, Col: 5): Unexpected value 'with'
##[error]CyberAgent/cmaes/composite-action/benchmark/action/action.yml (Line: 11, Col: 5): Required property is missing: run
##[error]CyberAgent/cmaes/composite-action/benchmark/action/action.yml (Line: 11, Col: 5): Required property is missing: shell
##[error]CyberAgent/cmaes/composite-action/benchmark/action/action.yml (Line: 18, Col: 5): Unexpected value 'if'
##[error]CyberAgent/cmaes/composite-action/benchmark/action/action.yml (Line: 17, Col: 5): Required property is missing: shell
##[error]CyberAgent/cmaes/composite-action/benchmark/action/action.yml (Line: 24, Col: 5): Required property is missing: shell
...


Filesystem messed up after creating a res directory

Operating system or device - Godot version:
OS: Windows 10 x64
Godot commit c83aa5f86383bf89871f0a41752f5c6eeb148950
Issue description (what happened, and what was expected):
I created a directory under res:// and named that directory to 'res' then the filesystem tree messed up and displayed tons of repeating res:// copies.

Steps to reproduce:
Create a directory named res under res:// and include/import a resource from there into your project. I don't know if the same thing might happen if you create a res directory under another directory

Yet another duplicate of #3662....


Fixed a typo and two broken links on the Documents/README.md file.

Description in the title.

@drphilmarshall, any chance you can review and merge? It's very minor.

Nice work, Yao! :-)

And thanks for fixing the bugs, Tom - much appreciated.


pdf-tales

-- create pdf for tales

@KlYana Thank you, I am trying to discuss it more with our UX people here: https://cesko-digital.slack.com/archives/C03C9M0QPA9/p1679252244602969

@met @KlYana  I think it would be good to have a tale title included in pdf.

as well @met @jejdacz please check if it is possible to import images for stories that way?? when I was trying to import like this: src={/kids/${story.slug}.jpg}, pdf could not find the image

@jejdacz please check in [storyId].tsx, when trying to export pdf with image src={/kids/${story.slug}.jpg} I've got no image found. So for now I'm using it like src={https://www.movapp.cz/_next/image?url=%2Fkids%2F${story.slug}.jpg&w=640&q=75} which does not seem correctly for me but it works. I need some confirmation if it can be like this, or if not, how can I add src correctly

@jejdacz please check in [storyId].tsx, when trying to export pdf with image src={/kids/${story.slug}.jpg} I've got no image found. So for now I'm using it like src={https://www.movapp.cz/_next/image?url=%2Fkids%2F${story.slug}.jpg&w=640&q=75} which does not seem correctly for me but it works. I need some confirmation if it can be like this, or if not, how can I add src correctly

I have it same. I didn't find any other solution than src={https://www.movapp.cz/_next/image?url=%2Fkids%2F${story.slug}.jpg&w=640&q=75}.
I did it wrong before. I forgot to rebuild. Sorry for wrong info.

Another approach could be to provide content styled with css for print and let the user print it to pdf file. Then we need no pdf generation.

@met I've corrected text color and space.
@jejdacz please approve if it's ok, I then can merge changes

Since the stories section code was and is UK/CS version only it's ok to merge. There's lot of conditions made on "cs" "uk". Not good.

I agree with finishing this soon in this way.
During next weeks there will be Slovak fairytales ready soon (but not Polish yet).
There will be time to think about language conditions (or improve them).
And there is also this (stories of fairytales will be in central data repostitory in similar way like the data for dictionary is), see https://trello.com/c/dn0tMBGd
So some things will need to be rewritten. But that could take time. Better finish this one now so PDF can work now and there is not such press for rewrite.

So I think it's ready to merge.


Jump between previous and next version in git

GitLens supports (under the alternate keychord) to press alt+, or alt+. to jump between versions of a file. I use this a lot to see what happened recently quickly, when I e.g. see an error log from a file and I need to see what recent changes happened.
Unfortunately GitLens has become too bloated, and that is the only feature I need.
I think this should be fairly easy to implement, and they keyboard shortcuts are not used by VS Code by default at this moment writing this feature request.

@lszomoru if I implement this PR myself, am I free to do so even if it has not reached backlog status yet?

@thernstig, I would suggest that we wait for the issue to make it to the backlog.