Improve hashtag regex

Match all non space and punctuation characters
Require a space character before the hashtag to avoid matching URL fragments, see https://github.com/verbiricha/habla.news/issues/163

Wouldn't forcing a space before the hashtag mean that notes with just a hashtag will fail to be recognized?
I also tested, using regex101 and couldn't get any special characters to be recognized.

Maybe I misunderstood your original message. I thought you were trying to match those characters. I think I agree though that hashtags should not have special chars so it's better that they're filtered out here.


Is there a fix for 19401.508?

Hello,
I've been successful before with RDPWrap on a lower build, recently my computer went for a windows update without my permission :) and RDPWrap does not work anymore, I am now on:
Windows 10 Home
Version 2004
OS Build 19401.508
Is there a solution for this build?
Thanks!!

I seem to be having the same problem on build 19401.450

@GWAM does the fix in https://github.com/stascorp/rdpwrap/issues/1142 work for you?

No, it doesn't, I even tried uninstalling and re-installing RDPWrap, no luck, the INI does not have an entry for 19401, not sure if anyone else if facing the same issue?

try this
https://github.com/stascorp/rdpwrap/issues/1163

#1163

works for me

I can confirm [#1163 ] resolved my issue


fix: *golang: Set GOROOT_FINAL to use libdir

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[ ] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[ ] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[ ] Ready to merge

Summary

What does the PR accomplish, why was it needed?
Fix golang packages to set the compiled-in GOROOT correctly.
This is not causing problems under normal circumstances because shells are loading /etc/profile which has the correct GOROOT set.
However the go binary itself has an invalid GOROOT.
GOROOT_FINAL sets the compiled-in default GOROOT for the final go binary.
This was set to /usr/bin/go which causes the go command to error out (when /etc/profile is not loaded) because that is the binary path not the path of the final GOROOT.
Change Log

Update GOROOT_FINAL in golang and msft-golang to have the correct final value

Does this affect the toolchain?

NO
Associated issues

Fixes #6363

Test Methodology

Pipeline build id: xxxx

@mfrw done

Any updates on this one?

Any updates on this one?

Apologies, this got drowned in the numerous notifications from github :(


Sticky side menu

I believe I have followed the guides correctly and my semantics make sense, at least to me - however I can't seem to get the sticky header & sticky side menu (will be an accordion) to work correctly. (see test case)
What should happen?
My "menu placeholder" should stay in place at all times
What happens instead?
My "menu placeholder" scrolls into the header area and sticks in there
Possible Solution

I cannot suggest a solution.
Test Case and/or Steps to Reproduce (for bugs)

Test Case: https://codepen.io/anon/pen/xBKaLq
Context

I think this is a very common layout requirement
Your Environment

Foundation version(s) used: 6.5.1
Browser(s) name and version(s): chrome (latest) and firefox (latest)
Device, Operating System and version: windows 10
Link to your project: na

Checklist

[x] I have read and follow the CONTRIBUTING.md document.
[x] There are no other issues similar to this one.
[x] The issue title and template are correctly filled.

Further testing reveals that this is a problem with having a sticky component anchoring to another sticky component. ie if I remove the sticky-ness from the header, the menu placeholder sticks nicely - although my header disappears which is not what I want.


Digest authentitaction for a camera?

Hi,
I have an IP camera which supports digest authentication.
Does anyone have an idea of how to login using digest authentication and then display the stream url?
The camera has a standard mjpg stream url:
http://<server_ip>/cgi-bin/mjpg/video.cgi?channel=1&subtype=1
... but if I directly show the url in a flx.IFrame, the standard username/password box pops up in the browser.
Can I somehow use digest authentication on the current session, so that the browser won't ask me for credentials?
I am not knowledgable in sessions, cookies, ... so if I'm misunderstanding something or am picturing something completely wrong, please tell me.
Thanks,
Matic

I think that normally the browser will remember the credentials while the browser is open (and maybe for a certain period of time?). So you should be able to login once, and then watch the stream while the browser is open.
But maybe I am misunderstanding the question? :)

Hey @almarklein,
You are right, I had to wrap the JS code into a flx.Widget, and then it works.
But now the problem is that this library: https://github.com/inorganik/digest-auth-request
doesn't work with a DAHUA camera. I get an Access-Control-Expose-Headers error.
I'll leave this open for a few day, so that if anyone knows how to do digest authentication with a DAHUA camera, can let me know.
Thanks


Cross-OS caching: Cache in Ubuntu + OS matrix = no hit in Windows

Hi. This issue is manually copied from https://github.com/actions/virtual-environments/issues/3424 .
Could be related to https://github.com/actions/cache/issues/144 .
This comment by @maxim-lobanov is very interesting, and might explain why I'm having problems.

Original issue text
Description
Trying to pass data between jobs using cache.
I'm currently using artifacts, but I don't need these files to be available for download, and it seems artifacts are slower (more upload/download), so I would like to use cache instead.
I use multiple OSes, but Windows does not seem to be able to see caches from Ubuntu.
The other way around is also true, Ubuntu can't see caches from Windows.
MacOS can see both.
Area for Triage:
Scripting and command line
Question, Bug, or Feature?:
Bug
Virtual environments affected

[ ] Ubuntu 16.04
[ ] Ubuntu 18.04
[x] Ubuntu 20.04
[ ] macOS 10.15
[ ] macOS 11
[ ] Windows Server 2016 R2
[x] Windows Server 2019

Image version
2.278.0
Expected behavior
Cache hit in Windows
Actual behavior
No cache hit in Windows
Repro steps
Cache from Ubuntu, can not be read by Windows:
https://github.com/eirikb/gradlex-test/runs/2623752327?check_suite_focus=true

Cache from Windows can not be read by Ubuntu:
https://github.com/eirikb/gradlex-test/runs/2623807942?check_suite_focus=true

I could understand if this had something to do with runners in different environments or something, but isn't caches stored elsewhere, and why can MacOS see both?

@eirikb @j-boivie Yes, this is due to a bug using zstd and BSD tar on Windows.  You can fix this by adding GNU tar to the system path before running the cache step - see https://github.com/actions/cache/issues/576#issuecomment-830796954 for an example.
We plan to make GNU tar the default on Windows, but in the meantime I would recommend the workaround above.  This fix is being tracked by https://github.com/actions/toolkit/issues/552.

@dhadka Thank you. I've verified the workaround works. I'll close this issue since this is already being tracked.
For anyone stumbling over this issue, the workaround including OS matrix. looks like this:
    steps:
      - name: "Use GNU tar instead BSD tar"
        if: matrix.os == 'windows-latest'
        shell: cmd
        run: echo C:\Program Files\Git\usr\bin>>"%GITHUB_PATH%"
      - uses: actions/cache@v2
        with:
          path: hello
          key: hello


Doesn't work on Pixel 7

So I tried to use this app because it claims that it can access Android/data contents but in my Pixel 7 it is unable to. I can "see" the contents but I am not able to write to them which is the whole point. Also my phone has android 13. Can provide additional details if needed.

https://www.youtube.com/watch?v=-4H0K70WhDg
https://www.youtube.com/watch?v=XbeSkrdzsus&t=89s
you can watch the video first. thanks.
Debesh Mishra @.***> 于 2022年11月15日周二 09:11写道：

So I tried to use this app because it claims that it can access
Android/data contents but in my Pixel 7 it is unable to. I can "see" the
contents but I am not able to write to them which is the whole point. Also
my phone has android 13. Can provide additional details if needed.
—
Reply to this email directly, view it on GitHub
https://github.com/folderv/androidDataWithoutRootAPI33/issues/5, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ALTSMGII3KEEJBIX5RZE7W3WILPLVANCNFSM6AAAAAASAM32GY
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>

I have watched that video and also left a comment roughly a month ago refarding the same issue. If you want I can record the video from my phone and show it to you. It doesn't work.

please send me your video.thanks.
Debesh Mishra @.***> 于 2022年11月15日周二 09:45写道：

I have watched that video and also left a comment roughly a month ago
refarding the same issue. If you want I can record the video from my phone
and show it to you. It doesn't work.
—
Reply to this email directly, view it on GitHub
https://github.com/folderv/androidDataWithoutRootAPI33/issues/5#issuecomment-1314643549,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALTSMGO6RHNCUF7BDNQXTQLWILTNNANCNFSM6AAAAAASAM32GY
.
You are receiving this because you commented.Message ID:
@.***>

Here you go:
https://youtu.be/Seyci9S00pE

install the latest version to check.
https://play.google.com/store/apps/details?id=com.folderv.file
Debesh Mishra @.***> 于2022年11月15日周二 09:59写道：

Here you go:
https://youtu.be/Seyci9S00pE
—
Reply to this email directly, view it on GitHub
https://github.com/folderv/androidDataWithoutRootAPI33/issues/5#issuecomment-1314652260,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALTSMGKJ6ZXMXNFGYMYSISDWILVAZANCNFSM6AAAAAASAM32GY
.
You are receiving this because you commented.Message ID:
@.***>

Tried it, has the same issue. Nothing happens when trying to paste or trying to create a new folder.

Please install the latest version to check again，thank you for
your feedback .
https://play.google.com/store/apps/details?id=com.folderv.file
Debesh Mishra @.***> 于2022年11月16日周三 02:40写道：

Tried it, has the same issue. Nothing happens when trying to paste or
trying to create a new folder.
—
Reply to this email directly, view it on GitHub
https://github.com/folderv/androidDataWithoutRootAPI33/issues/5#issuecomment-1315718941,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALTSMGIH3QRBQ7CMLCJO3L3WIPKIZANCNFSM6AAAAAASAM32GY
.
You are receiving this because you commented.Message ID:
@.***>

No worries. I tried the latest update as well but the issue is still same.

new method here http://folderv.com/2023/11/24/access-Android-data-and-Android-obb-on-Android-14/


dogsatsd: add AF_UNIX+SOCK_STREAM listener

What does this PR do?

Add a new uds stream listener that shares code and pool managers with the datagram listener
Update unit tests and integration tests to leverage this listener
Mark it as experimental until at least one of our client lib has support for it

Motivation
Eventually provide more fairness in multi-tenant environment
Additional Notes
It can be enabled with:
dogstatsd_stream_socket: "/path/to/dogstatsd.stream.sock"
dogstatsd_experimental_and_not_yet_supported: true

The framing protocol is simply a big-endian int32 length prefix.
Possible Drawbacks / Trade-offs
Describe how to test/QA your changes
Can be tested with a simple python client:
    s = socket.socket(socket.AF_UNIX, socket.SOCK_STREAM)
    s.connect(SOCKET_PATH)

    msg = b"custom_counter1:1|c"
    s.send(len(msg).to_bytes(4, byteorder='big'))
    s.send(msg)

Reviewer's Checklist

[x] If known, an appropriate milestone has been selected; otherwise the Triage milestone is set.
[x] Use the major_change label if your change either has a major impact on the code base, is impacting multiple teams or is changing important well-established internals of the Agent. This label will be use during QA to make sure each team pay extra attention to the changed behavior. For any customer facing change use a releasenote.
[x] A release note has been added or the changelog/no-changelog label has been applied.
[x] Changed code has automated tests for its functionality.
[x] Adequate QA/testing plan information is provided if the qa/skip-qa label is not applied.
[x] At least one team/.. label has been applied, indicating the team(s) that should QA this change.
[x] If applicable, docs team has been notified or an issue has been opened on the documentation repo.
[x] If applicable, the need-change/operator and need-change/helm labels have been applied.
[x] If applicable, the k8s/<min-version> label, indicating the lowest Kubernetes version compatible with this feature.
[x] If applicable, the config template has been updated.

PR description to update following changes (endianness), also explanation on what it changes and why you expect more fairness with SOCK_STREAM (basically, TCP).
This is to help future Agent developers to understand context and history.

PR description to update following changes (endianness), also explanation on what it changes and why you expect more fairness with SOCK_STREAM (basically, TCP). This is to help future Agent developers to understand context and history.

done

dogstatsd.stream.sock

is the performance lower than unixgram?


Are there any plans to implement a ZigBee stack on top of the esp-ieee802154 crate?

Are there any plans to implement a ZigBee stack on top of the esp-ieee802154 crate, perhaps porting this repository, zigpy, to rust?

Until there is an open-source ZigBee stack I can't imagine any of us will have the time for something as complex like this.

There is some effort: https://github.com/blueluna/psila
Another alternative would be to use or port https://github.com/niclash/zboss

I took over the existing zigbee crate and started to re-implement the stack from scratch based on the latest ZigBee specification 22 1.0
If there are any volunteers, we could speed up the development.


Inflector helper doc specifications

The doc  should explicitly mention that this Helper is for English language only and there is no supported way of directly extending it to other languages.
Perhaps future plans might include this as part of the language Library instead in order to help profit from localization?

The current user guide could mention your suggestion, but it is not inconsistent with the other frameworks. Cake & Yii, for instance, have inflector helpers that are English only, without expressly stating that.
As for future plans, this sounds like a can of worms :(
I did not find any frameworks that deal elegantly with multiple languages, hmmm.
The closest was https://github.com/ICanBoogie/Inflector, which handles a handful of languages.
In other words, something easier said than done!

Yup you are right, I suppose for multilingual cases one could simply add a few extra language lines, it's not a huge deal anyway, thanks!

Nitpicking level: infinity.


Broken Manifest and Project

Manifest and Project cause the Julia kernel to crash in Jupyter Notebooks.
Here is the error:
ERROR: LoadError: ArgumentError: Package ZeroMQ_jll does not have JLLWrappers in its dependencies:
- If you have ZeroMQ_jll checked out for development and have
  added JLLWrappers as a dependency but haven't updated your primary
  environment's manifest file, try Pkg.resolve().
- Otherwise you may need to report an issue with ZeroMQ_jll

This isn't me but I had the same problem (I had this problem with the 1.4.2 and 1.0.4 kernels and this person had this error with the 1.5.2 kernel):
https://discourse.julialang.org/t/package-zeromq-jll-does-not-have-jllwrappers-in-its-dependencies/48807
EDIT: Problem fixed by deleting the files Manifest and Project.

Same. Should Manifest.toml and Project.toml be removed or modified? I'm not enough of a Julia person to know.

Updated both of them!


chore: Use python 3.11 in GH actions

Using latest python will help us to identify
latest changes and regressions early in upstream PRs. Bumped repo versions in .pre-commit-config.yaml
to point to latest stable releases per available check.
Signed-off-by: Tibor Dudlák<EMAIL_ADDRESS>

marking as draft unless pre-commit hook erros are adressed

Seems like pylint does not support 3.11 yet.
https://github.com/PyCQA/pylint/issues/6535

Decided to move to py3.10 unless 3.11 is usable for us without hax. Renaming the PR to reflect the changes here.


Upgraded greenlight core lightning version to 24.02.1.

Rebased and made this branch into a draft pull request so it's ready to merge when we've upgraded the cln version on our servers

[ ] Requires core lightning v24.02.1 to be pushed to cloud storage as a greenlight artifact. Otherwise check-self will fail with make: *** [Makefile:148: cln-versions/lightningd-v24.02.1gl1.tar.bz2] Error 8

Also, an update of the signer version is needed to upgrade the node to v24.02. Can be found in signer/mod.rs : VERSION. This is called on maybe_upgrade.

Rebased on top of master

libs/gl-testing/node.py class NodeProcess is missing the --developer flag on versions >= 24.02. Adding the following snippets fixes this for the time being until pyln-testing supports multiple versions.
#libs/gl-testing/gltesting/utils.py

def version_to_int(nv: NodeVersion):
        # Remove the initial 'v'
        version_string = nv.name.lstrip('v')

        # Split the version string into parts by '.' and strip any non-numeric suffix
        parts = version_string.split('.')
        numeric_parts = []

        for part in parts:
            numeric_part = ''.join(filter(str.isdigit, part))
            numeric_parts.append(numeric_part.zfill(2))  # Zero-fill to ensure 2 digits per part

        # Ensure there are exactly 4 parts, padding with '00' if necessary
        while len(numeric_parts) < 3:
            numeric_parts.append('00')

        # Join the parts into a single string
        parsed_version = ''.join(numeric_parts[:3])  # Take only the first 4 parts

        return int(parsed_version)

#libs/gl-testing/gltesting/utils.py

class NodeVersion(TailableProcess):
...

   self.cmd_line = [
            str(self.executable),
            f'--lightning-dir={self.directory}',
            f'--network={network}',
            '--log-level=debug',
            '--bitcoin-rpcuser=rpcuser',
            '--bitcoin-rpcpassword=rpcpass',
            f'--bitcoin-rpcconnect=<IP_ADDRESS>:{self.bitcoind.rpcport}',
            "--disable-plugin=commando",
            '--rescan=1',
            "--log-timestamps=false",
            "--cltv-final=6",
            f"--addr=<IP_ADDRESS>:{self.p2p_port}",
            # Stock `cln-grpc` disabled in favor of `gl-plugin`
            '--disable-plugin=cln-grpc',
            f'--subdaemon=hsmd:{signerproxy_path}',
            f'--important-plugin={plugin_path}',
            '--dev-bitcoind-poll=5',
            '--dev-fast-gossip',
            '--offline',
            '--experimental-anchors',
        ]

        if version_to_int(self.version) >= 240200:
            self.cmd_line.append('--developer');

...

This reduces the checks that fail to
sendcustommsg changed on pyln-client (no keyword args):

test_node.py::test_custommsg
test_lsps.py::test_lsps_list_protocol

some signer errors: - ValueError: Some signer reported an error: [msg: "resolver error:

libs/gl-testing/tests/test_gl_node.py::test_configure_close_to_addr
libs/gl-testing/tests/test_node.py::test_node_invoice_amountless
libs/gl-testing/tests/test_node.py::test_lsp_jit_fee
libs/gl-testing/tests/test_node.py::test_vls_crash_repro
libs/gl-testing/tests/test_node.py::test_sendpay_signer
libs/gl-testing/tests/test_node.py::test_node_listpays_preimage

Other tests are good!


VM memory tests and swap prevention

Set memoryBacking/locked for domains
Make examples/virsh.sh accept @pod[:namespace] notation
Refactor tests/e2e/e2e.sh
Add memory tests

This change is

Reviewed 6 of 6 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Reviewed 6 of 6 files at r1.
Review status: all files reviewed at latest revision, 2 unresolved discussions.

examples/virsh.sh, line 26 at r1 (raw file):

  local namespace_opts=""
  if [[ ${namespace} ]]; then
      namespace_opts="-o ${namespace}"

should be "-n" option here, no?

tests/e2e/e2e.sh, line 43 at r1 (raw file):

    fi
    if ((--n == 0)); then
      echo "Timed out waiting for pod ${pod}" >&2

"exit 1" missed?

Comments from Reviewable

Review status: 4 of 6 files reviewed at latest revision, 2 unresolved discussions.

examples/virsh.sh, line 26 at r1 (raw file):
Previously, vefimova (Victoria Efimova) wrote…
should be "-n" option here, no?

Thanks for spotting this, fixed.

tests/e2e/e2e.sh, line 43 at r1 (raw file):
Previously, vefimova (Victoria Efimova) wrote…
"exit 1" missed?

Fixed, thanks!

Comments from Reviewable

Reviewed 2 of 2 files at r2.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable

Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Tag CSS height fails with long tag names

This is what you get....

The fix I believe is to alter
.a17 .vselect--small.vselect--multiple .selected-tag {}  setting its height from 21px to auto
I would have made a pull request but not 100% sure where to modify your css as I found multiple references to this.

Thanks for reporting and providing a potential solution @arkid, much appreciated!
We'll look into this.


Renaming of GET reduction-cards to reduction-card-types

Two changes:

The masterdata endpoint GET reduction-cards should be renamed to GET reduction-card-types (since the semantics of reductionCard has changed to an instance of an reductionCardType.
Addionally the mandatory attribute reductionCardTypes[]/name{}/id should be removed (since it is no longer used).

Split of https://github.com/UnionInternationalCheminsdeFer/OSDM/issues/583


Fix logger bug on Windows: path contains ''.

Description:
system_log not successfully initialized.
Windows using \ to separate folders, combining it directly without escape will create illegal Regex.
re.escape must be called before combine it to regex string.
Checklist:

[x] The code change is tested and works locally.

If the code does not interact with devices:

[x] Local tests with tox run successfully. Your PR cannot be merged unless tests pass
[ ] Tests have been added to verify that the new code works.

fixed


vela traits --sync does not sync traitdefinitions from the cluster to .vela locally

Describe the bug
vela traits --sync does not sync traitdefinitions from the cluster to .vela locally.
Expected behavior
Traits that are defined in the targeted cluster should be synced to the .vela/capabilities/traits folder. This does not happen.
Cluster information
Describe your kubernetes cluster information.

Kubernetes Version 1.19.7-GKE.800

Ah we've found that we needed to do -r to force a sync. What is the -s useful for?

Yes, it seems it's a bug and the --sync was not needed.

By reading the source code, I found the following logical
// NewTraitsCommand creates `traits` command
func NewTraitsCommand(c types.Args, ioStreams cmdutil.IOStreams) *cobra.Command {
	var workloadName string
	var syncCluster, enforceRefresh bool
	...
		RunE: func(cmd *cobra.Command, args []string) error {
			if syncCluster {
				if err := RefreshDefinitions(ctx, c, ioStreams, true, enforceRefresh); err != nil {
					return err
				}
			}
	...
	}

	cmd.SetOut(ioStreams.Out)
	cmd.Flags().StringVar(&workloadName, "apply-to", "", "Workload name")
	cmd.Flags().BoolVarP(&syncCluster, "sync", "s", true, "Synchronize capabilities from cluster into local")
	cmd.Flags().BoolVarP(&enforceRefresh, "", "r", false, "Enforce refresh from cluster even if cache is not expired")
	return cmd
}

--sync means whether the traits information will be synchronized ； refreshInterval = 5 * time.Minute
-r  represents forced synchronization and does not need to wait for the synchronization cycle to arrive
If --sync is false, the information is never synchronized.

Yes, it seems it's a bug and the --sync was not needed.

Do you mean to remove the logic of --sync and sync directly from the cluster each time with parameter -r?

@just-do1  Hi, may I assign this issue to you?

Do you mean to remove the logic of --sync and sync directly from the cluster each time with parameter -r?

Yes, by default the --sync is true, we can just remove this parameter and leave it as the default behavior

Ok, I'll finish it as soon as possible

This is the same for vela workloads by the way.

This is the same for vela workloads by the way.

yes, ping @just-do1  please fix together，thanks

ok


Hexagons and their symbols often far apart when dragging

This is to document an issue which has been orally raised already.  Hopefully made self-explanatory by the screenshot.  I'm using Firefox 46.0.1 but the issue has been observed in Chrome too.

This was fixed in https://github.com/ucam-cl-dtg/isaac-app/commit/a3f09f24bcf1848a6d1bbd7610442b0e3dd5d7c6

@jsharkey13 I notice that the commit you mention was made 10 days ago, but the screenshot I took is from 5 days ago. If the issue was fixed then how can this be?

The version on staging is (was) the same as the live version, it will never be the (unstable) up-to-date version seen on dev. But since dev goes up and down like a yo-yo, you should always use staging and just trust us when we say it's fixed!
(Though do test it once we do a release to test/staging before a release to live!)


[webview_flutter]Support UserAgent setting for webview_flutter

It possible to get and set custom user agent to webview.

@amirh Thanks for the review.
I fixed the issues, and added new commit to fix the accessor name like currentUrl.

Sorry for the delay getting to review this, we were trying to minimize adding new features before we had e2e tests.
The code has changed a bit since this PR was sent, this PR needs to be rebased, and add e2e tests should be added(see https://github.com/flutter/plugins/blob/master/packages/webview_flutter/example/test_driver/webview.dart).

Hi, @amirh
Thank you for reply.
This PR is rebased, and added e2e tests.

What needs to be done to get this merged?

@YukiOya any change you can get the last remarks fixed so this can be merged?

This PR needs more work before it can be merged, a rebase/merge of master is needed(a recent refactoring that was done requires moving some stuff around, and following up on the review comments is still needed).
I'm marking this PR as "needs love" and closing it, feel free to re-open or file a new PR.
Note that the priority of the feature(and of reviewing non trivial PRs) is determined by the number thumbs up on the issue(https://github.com/flutter/flutter/issues/28256 in this case). See the review process section in the contributing guide.


Posters / Poster "UI card" images

Poster and demo presenters should be able to upload an image that will serve as the background of a UI "card" for each of them

Being implemented as part of the new UI's Exhibition Hall feature. Closing in favour of tracking in our internal SPLASH issues.


KAFKA-14702: Extend server side assignor to support rack aware replica placement

This patch introduces the SubscribedTopicDescriber interface to the group-coordinator module and changes the necessary files to facilitate the assignors in being rack aware. Existing range assignor now has facilities to test for rack awareness in the future, whenever that is implemented.
In order to obtain and provide the rack information from the topic and cluster metadata to the assignors the following  modifications were made:-

SubcribedTopicDescribor - Interface passed to the assignor to obtain topic and partition metadata.
- Assign function in PartitionAssignor interface now has two arguments, Assignment Spec and
SubscribedTopicDescriber.
- Removed the AssignmentTopicMetadata class and removed the topics attribute from the AssignmentSpec, all topic
metadata will now be provided by the SubscribedTopicDescriber.
SubcribedTopicMetadata - Implementation of the interface above.
Add partitionMetadata field to the ConsumerGroupPartitionMetadataValue.json, this will be empty if rack info doesn't exist.
TopicMetadata has a new attribute Map<Integer, Set> partitionRackInfo - Map of partition Id to a set of its racks.

New PR with all the previous commits squashed -
Link to Old PR = https://github.com/apache/kafka/pull/13998

@rreddy-22 The build does not look good. Could you check it?

The build for JDK 17 is stuck... The three others look good. I have seen a few build stuck this week in other PRs so this is clearly not related to changes made in this one. Moreover, we had successful builds previously and we addressed nits in the mean time. Therefore, I will merge this PR.


Feature Request: Menu

It'd be nice if someone pressed something like ESC (or something else), it'd pop-up some kind of menu. We all know it; it asks us if we want to continue, change settings, exit, save, load, etc.
But it also stops everything else in the game -- depending on which game you're playing.
Proposition:
width := 600
height := 800
pauseWorld := true

menuEntity := engi.CreateMenu(width, height, pauseWorld)

And this Entity, would then contain a SpaceComponent of given size, and one could add some additional components (i.e. RenderComponent) to do the markup themselves. The pauseWorld part is why I'd love to see this implemented (by me or someone else).
Additional proposition (which you don't have to like):
pauseWorld := true
items := map[string]func() {
    "Continue" : func() { /* do nothing */},
    "Save" : func() { /* save the game */},
    "Exit" : func() { /* exit the game */},
}

menuEntity := engi.CreateMenu(pauseWorld, items)

Then engi would just create a menu with these options, possibly with some styling options for the user.
Not sure how this fits in the whole ECS-paradigm, but it'd be a nice feature to have. And this issue would be a great place to discuss (or summarize discussions).

Awesome. We definitely need some sort of pause/menu feature. My only concern would be making the menu too specific and not flexible enough for general use. IMO we should view the pause menu as a group of Entitys which represent a UI + pause logic.
Regarding your second proposal, I don't quite understand why you wouldnt just use an interface?
type XYZ interface {
   Continue()
   Save()
   Exit()
}

Also, perhaps implementing Save logic into the engine is going a bit too far. I'm happy for a discussion on this though.

So it should have some kind of PauseSystem, which some Entity would require?
w.r.t. the second proposal:
The idea was the map, not those specific entries of the map. It would create a menu with the strings as buttons (or w/e), and execute the function on select.

Yes. A PauseSystem would be good. We could make use of the Message-ing features, to summon the PauseSystem.
@EtienneBruines I think it would be best to allow each Entity to handle its own behaviours.

A PauseSystem with the Message-ing features would work.
Thinking about what might be the best idea on how to stop "everything" - since we still want the menu to work. We still need (most of) the systems: RenderSystem, AnimationSystem, and possibly some other systems as well. We could use the PriorityLevel for this; the downside is that it's only attached to RenderComponents, and not to everything existing.
What if we used some UnpauseComponent or something? One could add those components to stuff that shouldn't be affected by the system-wide pause.
The current World-loop, is this:
for _, system := range w.Systems() {
		system.Pre()
		for _, entity := range system.Entities() {
			if entity.Exists {
				system.Update(entity, dt)
			}
		}
		system.Post()
	}

And it needs to be modified in such a way, that it skips everything that doesn't have an UnpauseComponent - if the system is paused.
I'll make a PR so you can see it in action.

Is there anything else we want to implement from this Issue?

Would this be pluggable by a developer or would this be core engine feature like CameraSystem?

Well, the PauseSystem has been implemented, and is completely pluggable.
I'm not sure what else we want to implement, because the other stuff probably is up to the developer, and it wouldn't be anything useful if we did it. We are busy with building-blocks though, such as #59.

hey @EtienneBruines and @paked
I do not know what happened to this issue.
I did not find this feature in any Golang game engine. And it is very difficult to create this alone.

Don't you want the engine to do this?

I think you support this right now.
Can you add a little example?

@SeanTolstoyevski I think it was decided that we did as much as we could as a game engine, because every main menu is different.
There's an example here:
https://github.com/EngoEngine/engo/tree/a8276ad380704822182b58ec79f3618c751a2d93/demos/adventure#a-pause-menu
Basically upon entering the main menu (can be a keypress, like ESC), you remove all Entitys from all System to prevent them from being rendered. That is, if you want to remove sight of the game. It's also become quite common to keep the game rendered in the background. If that is what you want, you'll need to figure out something to make it "pause aware", meaning that you don't move your character by pressing WASD while in the main menu -- nor should the time keep ticking.
But because every menu is different (some want buttons, some want text, some want animations), it's difficult to create a one-size-fits-all feature.
============
Even though I haven't been active on this project for years, I think I can go ahead and reopen this issue for further discussion (if you have any additional thoughts on the matter or ideas that the game engine could/should offer).

Hi, thank you very much for your attention and thinks. This community is active. It's beautiful.
It's hard to design a menu in general. Because it is necessary to establish an event-based system.

I think handling a main menu is out of scope for a game engine to handle. There's too many variances and possible combinations and some projects that might not even use one.
I think what we can do is show a good example of a menu in one of the demos (maybe improve the one in adventure) or it's own separate demo depending on how important it is.
Thoughts?

If you'd like an example of a main menu, including a start menu, you can check out my game hypnic. That scene is the main menu, and it even has an options menu with sliders to control things like volume and input. I'm actually participating in the Game-Off 2020 and I'm planning on attempting a pause menu type system for that as well.

That said, I don't think something like that would work as part of the systems in common. Common should be more general-purpose, so maybe a system for gui tools and buttons that you can use in a menu, but the menu itself should be up to the end user

I added a system to the adventure demo that can pause all the entities it tracks by removing them from the systems and re-adding them when it's unpaused. Another way of handling this would be to turn off the system's update when the system is paused. This is now part of the adventure demo.


Page 71. Is StandardScaler the default scaling for ColumnTransformer?

I noticed on page 71 that when the ColumnTransformer is used the StandardScaler method was not specified.
from sklearn.compose import ColumnTransformer

num_attribs = list(housing_num)
cat_attribs = ["ocean_proximity"]

full_pipeline = ColumnTransformer([
        ("num", num_pipeline, num_attribs),
        ("cat", OneHotEncoder(), cat_attribs),
    ])

housing_prepared = full_pipeline.fit_transform(housing)

Whereas, on the previous page, without using ColumnTransformer:
from sklearn.pipeline import Pipeline
from sklearn.preprocessing import StandardScaler

num_pipeline = Pipeline([
        ('imputer', SimpleImputer(strategy="median")),
        ('attribs_adder', CombinedAttributesAdder()),
        ('std_scaler', StandardScaler()), # <==
    ])

housing_num_tr = num_pipeline.fit_transform(housing_num)

Checking the Sklearn documentation I was not able to clarify this.
Thank You
Tom

Hi Tom, thanks for your question. The ColumnTransformer says that all the numerical features must be preprocessed using the num_pipeline:
full_pipeline = ColumnTransformer([
        ("num", num_pipeline, num_attribs), # <=== This is what this line says
        ("cat", OneHotEncoder(), cat_attribs),
    ])

And since the num_pipeline includes the StandardScaler, this is why the ColumnTransformer applies the StandardScaler to the numerical features.
Does this answer your question?


feat: restrict the assign_birt_traits_and_name  and change_character_trait

Only allow the overlore backend's address to use the functions. (use get_caller_address() and store the overlore in a config in the smart contract)

Depnds on #23

Change of design


Lab cannot be finished

Add a Power Apps Trial / Create a Production environment for Instructor
Description of issue
Lab is unable to be completed as the trial apps cannot be obtained due to the tenants assigned by the ALH.

You should raise this with the ALH in question, this is not an issue with the lab steps

Closing in response to Julian's comment above.


It throws exception when Ldap Server returns 9 error code (LDAP_PARTIAL_RESULTS)

Our LDAP server returns error code is 9 and I looked at the codebase. I don't know why it is not in codes.js and it will cause an error here
module.exports.getError = function (res) {
assert.ok(res instanceof LDAPResult, 'res (LDAPResult) required');
var errObj = ERRORS[res.status];
==> var E = module.exports[errObj.err];
return new E(res.errorMessage || errObj.message,
res.matchedDN || null,
module.exports.getError);
};
because errObj is undefined. Should we add LDAP_PARTIAL_RESULTS: 9 in codes.js?

👋
On February 22, 2023, we released version 3 of this library. As a result, we are closing this issue/pull request.
Please see issue #839 for more information, including how to proceed if you feel this closure is in error.


fix!: return external representation of ontology IRIs in admin routes

Pull Request Checklist
Task Description/Number
Issue Number: DEV-974
Basic Requirements
Please check if your PR fulfills the following requirements:

[x] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)

PR Type
What kind of change does this PR introduce?

[x] Bugfix: represents bug fixes
[x] Refactor: represents production code refactoring
[ ] Feature: represents a new feature
[x] Documentation: documentation changes (no production code change)
[ ] Chore: maintenance tasks (no production code change)
[ ] Style: styles updates (no production code change)
[ ] Test: all about tests: adding, refactoring tests (no production code change)
[ ] Other... Please describe:

Does this PR introduce a breaking change?

[x] Yes
[ ] No

Does this PR change client-test-data?

[ ] Yes (don't forget to update the JS-LIB team about the change)
[x] No

PR Progress / TODO

[ ] projects endpoint
[ ] user endpoint
[ ] groups endpoint
[ ] list endpoint
[ ] permissions endpoint

IMHO this is not a "refactor" but rather a breaking change as the nature of the identifier which are returned changes and old and new identifiers are incompatible.

I totally agree that it is a breaking change. I will adjust the PR title accordingly.

IMHO this is not a "refactor" but rather a breaking change as the nature of the identifier which are returned changes and old and new identifiers are incompatible.

I totally agree that it is a breaking change. I will adjust the PR title accordingly.

LGTM, just some minor coding style comments. Feel free to ignore them.


chore: drop byteorder dependency

Feature or Problem
Drop the byteorder dependency, which could easily be replaced with functions from std and easier to read logic.
Related Issues
None
Release Information
next
Consumer Impact
One less dependency, and less unsafe code in the build
Testing
Read below
Unit Test(s)
None
Acceptance or Integration
None
Manual Verification
While manually verifying that the code is correct I've gotten even more confused at how this code works. Looking at the Go library the CRC is put at the end and read from the end, while here the CRC is written to the end and read from the start :man_shrugging:. Are the tests wrong???
I've tried doing this and this seems to confirm my assumption:
diff --git a/src/crc.rs b/src/crc.rs
index 228880d..5dc5981 100644
--- a/src/crc.rs
+++ b/src/crc.rs
@@ -58,3 +58,23 @@ pub(crate) fn extract_crc(data: &mut Vec<u8>) -> Result<u16> {
     data.truncate(data.len() - 2);
     Ok(crc)
 }
+
+#[cfg(test)]
+mod tests {
+    use crate::crc::crc16;
+
+    use super::{extract_crc, push_crc};
+
+    #[test]
+    fn im_confused() {
+        let raw_data = rand::random::<[u8; 32]>();
+        let crc = crc16(&raw_data);
+
+        let mut data = raw_data.to_vec();
+        push_crc(&mut data);
+
+        let crc2 = extract_crc(&mut data).unwrap();
+        assert_eq!(raw_data, data.as_slice());
+        assert_eq!(crc, crc2);
+    }
+}

Thank you for filing this @paolobarbolini ! I'll take a look at this shortly to verify the behavior... seems weird.

@paolobarbolini do you a need for this to be released? It's small enough I think it could be a patch.

Thanks for the merge. I'll see if I can send the second PR with the CRC moved to the end.


Eliah Kagan: Watch chipgadgets.com

Eliah Kagan requests the watch of the watch_keyword chipgadgets\.com. See the MS search here and the Stack Exchange search here.

chipgadgets\.com has been seen in 2 true positives, 0 false positives, and 0 NAAs.

Approved by tripleee in Charcoal HQ


Can't connect to online node, channels down (LND <-> LND)

Background
I´ve opened channel with my friend, but the peer is connected, but channel is down. This report is related to https://github.com/getumbrel/umbrel/issues/598
Your environment
Mine:

lncm/lnd:v0.12.1
Linux umbrel 5.4.79-v8+ #1373 SMP PREEMPT Mon Nov 23 13:32:41 GMT 2020 aarch64 GNU/Linux
lncm/bitcoind:v0.21.0

The other side:

LND Version 	v0.12.1
Linux myNode 5.10.17-v7l+ #1403 SMP Mon Feb 22 11:33:35 GMT 2021 armv7l GNU/Linux
bitcoind Version 	v0.21.0

Steps to reproduce
Mine:
Open the channel, after opening I am getting following errors:
2021-03-06 17:50:36.935 [INF] PEER: unable to read message from 02e12a35304184cc4c6b9d3a85f3c5d9262403c335e2b01c4b6ed18cd838709c46@rbrg5j6zslb42n4xgkwh3gb2h2thzsw2xt77alh5mvosbysdvqbcivad.onion:9735: EOF
2021-03-06 17:50:36.935 [INF] PEER: disconnecting 02e12a35304184cc4c6b9d3a85f3c5d9262403c335e2b01c4b6ed18cd838709c46@rbrg5j6zslb42n4xgkwh3gb2h2thzsw2xt77alh5mvosbysdvqbcivad.onion:9735, reason: read handler closed
2021-03-06 17:50:37.035 [INF] DISC: Removing GossipSyncer for peer=02e12a35304184cc4c6b9d3a85f3c5d9262403c335e2b01c4b6ed18cd838709c46

The other side (log from first connection):
2021-02-16 21:01:50.692 [INF] CRTR: Processed channels=0 updates=20 nodes=5 in last 59.995472569s
2021-02-16 21:02:37.174 [INF] DISC: Broadcasting 27 new announcements in 3 sub batches
2021-02-16 21:02:50.692 [INF] CRTR: Processed channels=0 updates=19 nodes=1 in last 59.999253488s
2021-02-16 21:03:16.863 [INF] SRVR: New inbound connection from <IP_ADDRESS>:36714
2021-02-16 21:03:16.864 [INF] SRVR: Finalizing connection to 028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7@<IP_ADDRESS>:36714, inbound=true
2021-02-16 21:03:16.866 [INF] SRVR: New inbound connection from <IP_ADDRESS>:36708
2021-02-16 21:03:16.866 [INF] PEER: disconnecting 028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7@<IP_ADDRESS>:36714, reason: server: disconnecting peer 028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7@<IP_ADDRESS>:36714
2021-02-16 21:03:16.867 [INF] SRVR: Finalizing connection to 028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7@<IP_ADDRESS>:36708, inbound=true
2021-02-16 21:03:16.867 [INF] SRVR: New inbound connection from <IP_ADDRESS>:36712
2021-02-16 21:03:16.867 [INF] PEER: disconnecting 028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7@<IP_ADDRESS>:36708, reason: server: disconnecting peer 028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7@<IP_ADDRESS>:36708
2021-02-16 21:03:16.868 [INF] SRVR: Finalizing connection to 028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7@<IP_ADDRESS>:36712, inbound=true
2021-02-16 21:03:16.868 [INF] PEER: disconnecting 028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7@<IP_ADDRESS>:36712, reason: unable to start peer: unable to send init msg: write tcp <IP_ADDRESS>:9735-><IP_ADDRESS>:36712: write: broken pipe
2021-02-16 21:03:16.893 [INF] SRVR: New inbound connection from <IP_ADDRESS>:36706
2021-02-16 21:03:16.893 [INF] SRVR: Finalizing connection to 028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7@<IP_ADDRESS>:36706, inbound=true
2021-02-16 21:03:16.894 [INF] PEER: disconnecting 028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7@<IP_ADDRESS>:36706, reason: unable to start peer: unable to send init msg: write tcp <IP_ADDRESS>:9735-><IP_ADDRESS>:36706: write: broken pipe
2021-02-16 21:03:21.571 [INF] PEER: disconnecting 034bc0055092237b7a3e6fa2bf59ada3e355e2c18a0504a49c28125f675bbf2275@<IP_ADDRESS>:36070, reason: peer 034bc0055092237b7a3e6fa2bf59ada3e355e2c18a0504a49c28125f675bbf2275@<IP_ADDRESS>:36070 no answer for 5m0s -- disconnecting
2021-02-16 21:03:21.573 [INF] PEER: unable to read message from 034bc0055092237b7a3e6fa2bf59ada3e355e2c18a0504a49c28125f675bbf2275@<IP_ADDRESS>:36070: read tcp <IP_ADDRESS>:9735-><IP_ADDRESS>:36070: use of closed network connection
2021-02-16 21:03:21.608 [INF] SRVR: New inbound connection from <IP_ADDRESS>:36732
2021-02-16 21:03:21.608 [INF] SRVR: Finalizing connection to 028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7@<IP_ADDRESS>:36732, inbound=true
2021-02-16 21:03:21.611 [INF] PEER: Negotiated chan series queries with 028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7
2021-02-16 21:03:21.611 [INF] DISC: Creating new GossipSyncer for peer=028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7

Log from today:
2021-03-16 02:14:01.184 [INF] PEER: unable to read message from 028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7@<IP_ADDRESS>:35228: read tcp <IP_ADDRESS>:9735-><IP_ADDRESS>:35228: i/o timeout
2021-03-16 02:14:01.192 [INF] PEER: disconnecting 028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7@<IP_ADDRESS>:35228, reason: read handler closed
2021-03-16 02:14:01.294 [INF] DISC: Removing GossipSyncer for peer=028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7
2021-03-16 02:14:10.342 [INF] SRVR: Finalizing connection to 028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7@<IP_ADDRESS>:58492, inbound=true
2021-03-16 02:14:10.439 [INF] PEER: Negotiated chan series queries with 028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7
2021-03-16 02:14:10.439 [INF] DISC: Creating new GossipSyncer for peer=028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7
2021-03-16 02:18:17.529 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): applying gossipFilter(start=2021-03-16 02:18:17.529893541 +0100 CET m=+925011.536091081, end=2157-04-22 09:46:32.529893541 +0200 CEST)
2021-03-16 02:23:04.732 [INF] PEER: unable to read message from 028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7@<IP_ADDRESS>:58492: read tcp <IP_ADDRESS>:9735-><IP_ADDRESS>:58492: i/o timeout
2021-03-16 02:23:04.732 [INF] PEER: disconnecting 028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7@<IP_ADDRESS>:58492, reason: read handler closed
2021-03-16 02:23:04.833 [INF] DISC: Removing GossipSyncer for peer=028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7
2021-03-16 02:24:38.546 [INF] SRVR: Finalizing connection to 028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7@<IP_ADDRESS>:58858, inbound=true
2021-03-16 02:24:38.548 [INF] PEER: Negotiated chan series queries with 028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7
2021-03-16 02:24:38.548 [INF] DISC: Creating new GossipSyncer for peer=028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7
2021-03-16 02:35:11.122 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): requesting new chans from height=0 and 674812 blocks after
2021-03-16 02:35:11.785 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): buffering chan range reply of size=8000
2021-03-16 02:35:11.867 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): buffering chan range reply of size=8000
2021-03-16 02:35:11.924 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): buffering chan range reply of size=7993
2021-03-16 02:35:12.051 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): buffering chan range reply of size=7999
2021-03-16 02:35:12.407 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): buffering chan range reply of size=8000
2021-03-16 02:35:12.439 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): buffering chan range reply of size=743
2021-03-16 02:35:12.439 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): filtering through 40735 chans
2021-03-16 02:35:12.613 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): starting query for 1 new chans
2021-03-16 02:35:12.613 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): querying for 1 new channels
2021-03-16 02:35:13.175 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): no more chans to query
2021-03-16 02:36:33.522 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): filtering chan range: start_height=0, num_blocks=674812
2021-03-16 02:36:33.595 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): sending range chunk of size=7999
2021-03-16 02:36:33.605 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): sending range chunk of size=7995
2021-03-16 02:36:33.615 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): sending range chunk of size=7997
2021-03-16 02:36:33.624 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): sending range chunk of size=7998
2021-03-16 02:36:33.634 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): sending final chan range chunk, size=7925
2021-03-16 02:43:06.486 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): applying gossipFilter(start=2021-03-16 02:43:06.486833231 +0100 CET m=+926500.493030049, end=2157-04-22 10:11:21.486833231 +0200 CEST)
2021-03-16 03:03:06.486 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): applying gossipFilter(start=0001-01-01 00:00:00 +0000 UTC, end=0001-01-01 00:00:00 +0000 UTC)
2021-03-16 05:00:36.463 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): applying gossipFilter(start=2021-03-16 05:00:36.463325036 +0100 CET m=+934750.469522633, end=2157-04-22 12:28:51.463325036 +0200 CEST)
2021-03-16 06:36:33.520 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): filtering chan range: start_height=0, num_blocks=674843
2021-03-16 06:36:33.601 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): sending range chunk of size=8000
2021-03-16 06:36:33.618 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): sending range chunk of size=7992
2021-03-16 06:36:33.634 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): sending range chunk of size=7998
2021-03-16 06:36:33.649 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): sending range chunk of size=8000
2021-03-16 06:36:33.662 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): sending final chan range chunk, size=7962
2021-03-16 10:36:33.606 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): filtering chan range: start_height=0, num_blocks=674860
2021-03-16 10:36:33.653 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): sending range chunk of size=8000
2021-03-16 10:36:33.662 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): sending range chunk of size=7991
2021-03-16 10:36:33.672 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): sending range chunk of size=7998
2021-03-16 10:36:33.682 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): sending range chunk of size=7999
2021-03-16 10:36:33.693 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): sending final chan range chunk, size=7975
2021-03-16 12:35:11.123 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): requesting new chans from height=0 and 674870 blocks after
2021-03-16 12:35:11.943 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): buffering chan range reply of size=8000
2021-03-16 12:35:11.989 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): buffering chan range reply of size=8000
2021-03-16 12:35:12.062 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): buffering chan range reply of size=8000
2021-03-16 12:35:12.230 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): buffering chan range reply of size=7999
2021-03-16 12:35:12.571 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): buffering chan range reply of size=7998
2021-03-16 12:35:12.634 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): buffering chan range reply of size=811
2021-03-16 12:35:12.634 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): filtering through 40808 chans
2021-03-16 12:35:12.810 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): starting query for 1 new chans
2021-03-16 12:35:12.810 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): querying for 1 new channels
2021-03-16 12:35:13.449 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): no more chans to query
2021-03-16 14:03:06.486 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): applying gossipFilter(start=0001-01-01 00:00:00 +0000 UTC, end=0001-01-01 00:00:00 +0000 UTC)
2021-03-16 14:35:11.123 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): requesting new chans from height=0 and 674886 blocks after
2021-03-16 14:35:12.490 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): buffering chan range reply of size=8000
2021-03-16 14:35:12.912 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): buffering chan range reply of size=7999
2021-03-16 14:35:13.232 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): buffering chan range reply of size=8000
2021-03-16 14:35:13.479 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): buffering chan range reply of size=8000
2021-03-16 14:35:14.986 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): buffering chan range reply of size=7999
2021-03-16 14:35:14.989 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): buffering chan range reply of size=795
2021-03-16 14:35:14.989 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): filtering through 40793 chans
2021-03-16 14:35:15.182 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): starting query for 1 new chans
2021-03-16 14:35:15.182 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): querying for 1 new channels
2021-03-16 14:35:15.947 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): no more chans to query
2021-03-16 15:23:06.487 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): applying gossipFilter(start=2021-03-16 15:23:06.487081502 +0100 CET m=+972100.493278876, end=2157-04-22 22:51:21.487081502 +0200 CEST)
2021-03-16 15:35:11.123 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): requesting new chans from height=0 and 674891 blocks after
2021-03-16 15:35:12.549 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): buffering chan range reply of size=8000
2021-03-16 15:35:12.760 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): buffering chan range reply of size=7999
2021-03-16 15:35:12.824 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): buffering chan range reply of size=7999
2021-03-16 15:35:12.900 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): buffering chan range reply of size=7997
2021-03-16 15:35:13.202 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): buffering chan range reply of size=8000
2021-03-16 15:35:13.360 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): buffering chan range reply of size=805
2021-03-16 15:35:13.360 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): filtering through 40800 chans
2021-03-16 15:35:13.487 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): starting query for 1 new chans
2021-03-16 15:35:13.487 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): querying for 1 new channels
2021-03-16 15:35:14.145 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): no more chans to query
2021-03-16 15:43:06.486 [INF] DISC: GossipSyncer(028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7): applying gossipFilter(start=0001-01-01 00:00:00 +0000 UTC, end=0001-01-01 00:00:00 +0000 UTC)

Expected behaviour
Channel should be online.
Actual behaviour
Channel is offline

Seems there's some connectivity issue, possibly related to Tor:

2021-02-16 21:03:16.894 [INF] PEER: disconnecting 028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7@<IP_ADDRESS>:36706, reason: unable to start peer: unable to send init msg: write tcp <IP_ADDRESS>:9735-><IP_ADDRESS>:36706: write: broken pipe

2021-02-16 21:03:21.571 [INF] PEER: disconnecting 034bc0055092237b7a3e6fa2bf59ada3e355e2c18a0504a49c28125f675bbf2275@<IP_ADDRESS>:36070, reason: peer 034bc0055092237b7a3e6fa2bf59ada3e355e2c18a0504a49c28125f675bbf2275@<IP_ADDRESS>:36070 no answer for 5m0s -- disconnecting

The channel will only show as "active" after both sides have sent a handshake message. Before that it's possible for gossip traffic to flow between them.

It can't seem to read any thing the other peer writes due to an I/O timeout:

2021-03-16 02:23:04.732 [INF] PEER: unable to read message from 028d829e9254bf0a816983fb79c61d1aefcdc210a3c6f37177d62db98e3ea3a8f7@<IP_ADDRESS>:58492: read tcp <IP_ADDRESS>:9735-><IP_ADDRESS>:58492: i/o timeout

We currently use a read timeout of 5 seconds before giving up on a connection: https://github.com/lightningnetwork/lnd/blob/b4aa661d165601b8fb3df32d2cd5e0b28696e41c/peer/brontide.go#L56

We both restarted the nodes.. and also we have other channels which we have online.. any ideas what to try?

I'd recommend trying a clearnet connection to see if that resolves things. Alternatively if you can recompile, then increase this value: https://github.com/lightningnetwork/lnd/blob/b4aa661d165601b8fb3df32d2cd5e0b28696e41c/peer/brontide.go#L58 and the write one above it to a higher value to see if that resolves things.

Hmm.. nobody from us have public IP, so we can't do the first thing.. and dont know if I want to go by way recompiling the LND, pretty scared that I can mess things up..

Increasing those values is relatively low risk. From the logs, each time we go to read/write to socket, we timeout as nothing is able to be sent/read.

So I tried to increase it to 10 (https://github.com/downet/lnd/commit/2827dce01d1e46b410578253f2357b49f91cc0b6) in v0.12.1-beta-branch and recompile it.. but I see still the same in log:
lnd                  | 2021-03-22 16:03:55.882 [INF] PEER: unable to read message from 02e12a35304184cc4c6b9d3a85f3c5d9262403c335e2b01c4b6ed18cd838709c46@rbrg5j6zslb42n4xgkwh3gb2h2thzsw2xt77alh5mvosbysdvqbcivad.onion:9735: EOF
lnd                  | 2021-03-22 16:03:55.882 [INF] PEER: disconnecting 02e12a35304184cc4c6b9d3a85f3c5d9262403c335e2b01c4b6ed18cd838709c46@rbrg5j6zslb42n4xgkwh3gb2h2thzsw2xt77alh5mvosbysdvqbcivad.onion:9735, reason: read handler closed

Which time do you advise to try?
Btw. I am not able to deliver this to secondary side.. so it's only on my side.

Try a much larger jump maybe? You should also try to increase both of them, there's a variable called writeMessageTimeout right above it.

So I tried 100 on both.. channel is still down, but nothing special in LND log..
2021-03-22 20:36:08.015 [INF] SRVR: Established connection to: 02e12a35304184cc4c6b9d3a85f3c5d9262403c335e2b01c4b6ed18cd838709c46@rbrg5j6zslb42n4xgkwh3gb2h2thzsw2xt77alh5mvosbysdvqbcivad.onion:9735
2021-03-22 20:36:08.016 [INF] SRVR: Finalizing connection to 02e12a35304184cc4c6b9d3a85f3c5d9262403c335e2b01c4b6ed18cd838709c46@rbrg5j6zslb42n4xgkwh3gb2h2thzsw2xt77alh5mvosbysdvqbcivad.onion:9735, inbound=false
2021-03-22 20:36:08.509 [INF] PEER: NodeKey(02e12a35304184cc4c6b9d3a85f3c5d9262403c335e2b01c4b6ed18cd838709c46) loading ChannelPoint(43ef22e1272a80c94f0670a723470fc60b27700f66cb56bab0056ca1275f935c:1)
2021-03-22 20:36:08.513 [INF] PEER: Negotiated chan series queries with 02e12a35304184cc4c6b9d3a85f3c5d9262403c335e2b01c4b6ed18cd838709c46
2021-03-22 20:36:08.517 [INF] DISC: Creating new GossipSyncer for peer=02e12a35304184cc4c6b9d3a85f3c5d9262403c335e2b01c4b6ed18cd838709c46
2021-03-22 20:36:12.407 [INF] DISC: GossipSyncer(02e12a35304184cc4c6b9d3a85f3c5d9262403c335e2b01c4b6ed18cd838709c46): applying gossipFilter(start=2021-03-22 20:36:12.407613183 +0000 UTC m=+261.328724287, end=2157-04-29 03:04:27.407613183 +0000 UTC)
2021-03-22 20:43:06.678 [INF] DISC: GossipSyncer(02e12a35304184cc4c6b9d3a85f3c5d9262403c335e2b01c4b6ed18cd838709c46): applying new update horizon: start=2021-03-22 20:43:06 +0000 UTC, end=2157-04-29 03:11:21 +0000 UTC, backlog_size=1

If the other side still hangs up early, then it may still happen. As far as I can tell, it's some sort of networking issue related to the higher latency of Tor. Recently the tor network has been under various DoS attacks, which may manifest to the end user as a degradation of network quality.
Way may want to consider using higher values for the read/write time outs, but 5 seconds is already an eternity in the time frame of computers.

Strange is, that is only this node, where I have a problems, all others are ok (they are also thru Tor). And we both did multiple restarts..

Here are logs.. even I go thru them, it looks like totally different problem then we have here, but adding in case I overlooked something.
I just restarted LND and everything was OK after that.
LND version: btcpayserver/lnd:v0.13.1-beta-withloop-fix (lncli version 0.13.1-beta commit=basedon-v0.13.1-beta-withloop-fix-fresh-btcpay)
Logs: https://pastebin.com/q1hnM0tT

Another logs here: https://pastebin.com/eZhLA7M3
Logs from my node which lost connection:
2021-12-23 05:03:12.893 [INF] PEER: unable to read message from 021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a@<IP_ADDRESS>:9735: EOF
2021-12-23 05:03:12.893 [INF] PEER: disconnecting 021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a@<IP_ADDRESS>:9735, reason: read handler closed
2021-12-23 05:03:13.096 [INF] DISC: Removing GossipSyncer for peer=021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a
2021-12-23 05:04:54.092 [INF] SRVR: Established connection to: 021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a@hmgnavz6eccfnug5tpjxsgl3wlm5dimbe547mjv6utdy6xtcobovxmad.onion:9735
2021-12-23 05:04:54.093 [INF] SRVR: Finalizing connection to 021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a@hmgnavz6eccfnug5tpjxsgl3wlm5dimbe547mjv6utdy6xtcobovxmad.onion:9735, inbound=false
2021-12-23 05:05:09.102 [INF] PEER: disconnecting 021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a@hmgnavz6eccfnug5tpjxsgl3wlm5dimbe547mjv6utdy6xtcobovxmad.onion:9735, reason: unable to start peer: peer did not complete handshake within 15s
2021-12-23 05:05:11.677 [INF] SRVR: Established connection to: 021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a@<IP_ADDRESS>:9735
2021-12-23 05:05:11.678 [INF] SRVR: Finalizing connection to 021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a@<IP_ADDRESS>:9735, inbound=false
2021-12-23 05:05:18.623 [INF] PEER: NodeKey(021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a) loading ChannelPoint(4c9328787b34e28d1bcab7bad6c9396fc7aed823f2d43c70cbcfa2bc42c8a319:1)
2021-12-23 05:05:18.624 [INF] PEER: Negotiated chan series queries with 021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a
2021-12-23 05:05:18.625 [INF] DISC: Creating new GossipSyncer for peer=021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a
2021-12-23 05:05:18.780 [INF] PEER: unable to read message from 021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a@<IP_ADDRESS>:9735: EOF
2021-12-23 05:05:18.781 [INF] PEER: disconnecting 021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a@<IP_ADDRESS>:9735, reason: read handler closed
2021-12-23 05:05:18.882 [INF] DISC: Removing GossipSyncer for peer=021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a
2021-12-23 05:05:21.813 [INF] SRVR: Finalizing connection to 021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a@<IP_ADDRESS>:39056, inbound=true
2021-12-23 05:05:21.825 [INF] PEER: disconnecting 021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a@<IP_ADDRESS>:39056, reason: unable to start peer: unable to send init msg: write tcp <IP_ADDRESS>:9735-><IP_ADDRESS>:39056: write: broken pipe
2021-12-23 05:05:21.913 [INF] SRVR: Finalizing connection to 021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a@<IP_ADDRESS>:39058, inbound=true
2021-12-23 05:05:22.080 [INF] PEER: NodeKey(021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a) loading ChannelPoint(4c9328787b34e28d1bcab7bad6c9396fc7aed823f2d43c70cbcfa2bc42c8a319:1)
2021-12-23 05:05:22.081 [INF] PEER: Negotiated chan series queries with 021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a
2021-12-23 05:05:22.081 [INF] DISC: Creating new GossipSyncer for peer=021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a
2021-12-23 05:05:22.703 [INF] DISC: GossipSyncer(021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a): filtering chan range: start_height=0, num_blocks=715350
2021-12-23 05:05:22.812 [INF] DISC: GossipSyncer(021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a): sending range chunk of size=8000
2021-12-23 05:05:22.817 [INF] DISC: GossipSyncer(021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a): sending range chunk of size=8000
2021-12-23 05:05:22.822 [INF] DISC: GossipSyncer(021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a): sending range chunk of size=8000
2021-12-23 05:05:22.828 [INF] DISC: GossipSyncer(021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a): sending range chunk of size=7994
2021-12-23 05:05:22.833 [INF] DISC: GossipSyncer(021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a): sending range chunk of size=7988
2021-12-23 05:05:22.838 [INF] DISC: GossipSyncer(021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a): sending range chunk of size=8000
2021-12-23 05:05:22.903 [INF] DISC: GossipSyncer(021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a): sending range chunk of size=8000
2021-12-23 05:05:22.907 [INF] DISC: GossipSyncer(021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a): sending range chunk of size=8000
2021-12-23 05:05:22.912 [INF] DISC: GossipSyncer(021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a): sending range chunk of size=7974
2021-12-23 05:05:22.919 [INF] DISC: GossipSyncer(021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a): sending range chunk of size=8000
2021-12-23 05:05:22.925 [INF] DISC: GossipSyncer(021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a): sending final chan range chunk, size=2631
2021-12-23 05:05:24.381 [INF] DISC: GossipSyncer(021d925f1fae7e7756149be421079141af62d77b1f8626b29ab60f15b14645635a): fetching chan anns for 500 chans

After LND restart on BTCPay, it´s up again.

Found this old issue while looking through the open ones. I assume this was eventually resolved?
There were a number of bugs fixed around connection establishment since 0.13.1 as well.


Display last seen date on each chart

At the moment if the system updating the chart goes down, there's no easy way of seeing it.
We should have a date string for 'last update seen' which is normally formatted small and black - and becomes large and red if the value is more than 20 minutes old.

@lukechurch should we close this?

@lukechurch should we close this?

This isn't working very well for me:

This is showing as being scary and red but it's been less than ten minutes since the last update so that doesn't make sense...


Some complex query expressions don't map correctly to sort keys

Failing test provided here: https://github.com/jyelewis/DynamoFlow/blob/main/src/tests/issues.ts#L13

Fix here: https://github.com/jyelewis/DynamoFlow/pull/15

Fix released in 1.3.1


Implement endroid/qr-code support

I have left out readme changes as it needs updating further, default provider still listed as ImageChartsQRCodeProvider for example.
Usage
$qrProvider = new RobThree\Auth\Providers\Qr\EndroidQrCodeProvider('ffffff', '0000000', 0, 'H');
$tfa = new RobThree\Auth\TwoFactorAuth('My Company', 6, 30, 'sha1', $qrProvider);

I am really not very much familiar with the whole composer thing; shouldn't this require a reference in the composer.json file as it's a dependency?

Anything that can be helped with to see this merged and incorporated into a new release? Similar to the suggestion in #39, composer.json can be modified to use the suggest block to propose dependencies that will enhance the package, but are not strictly necessary:
"suggest": {
  "endroid/qr-code": "Needed for EndroidQrCodeProvider"
}

Then optionally install it to require-dev to be used for writing a test case with it.

I have merged this one, as wel as #39. If someone would like to update the README and make a PR that would be appreciated!

sure, I can do that.

thanks @MasterOdin


Fix crash when duplicating Light3D inherited nodes

Same issue as https://github.com/godotengine/godot/pull/100632, just with nodes that inherit Light3D.

Superseded by #100632, it makes sense to merge both related fixes as part of the same commit.


Unable to run cloudfront demo url in Iframe

I want to run this demo url in Iframe and facing some issue.It is not running in iframe.although it is running fine when used externally.Attached screenshot for this too-

The demo does not support rendering within an iframe. You would likely need to play around with the CSP policies to get it to work.
I believe this would be a good place to look

Thanks @p-foucht
Thanks for the solution. It worked for me


Group related changes in RELEASE_NOTES

Trying to make the bigger picture a bit easier to grok...
Question - should we get rid of the emoji hammer for build until we have other ones we use for other areas? So its not all on its own? (or add ones for the other things now)

I don't mind the hammer emoji. I think its useful to call out somehow that something is build-only breaking change.

I've removed this for now, and added https://github.com/OpenAssetIO/OpenAssetIO/issues/1160 - so we can make the most of it for the b1 release notes.


[8.x] Typo fixes

Got bored tonight and went on a typo hunt

Sweet, thanks!

Sweet, thanks!

@driesvints I also wanted to confirm - for the changelog, there were a few, but I figured those were being pulled directly from the PR titles, so I wasn't sure if I should fix them or not.  Can you let me know if those should be fixed or not?  I can see arguments both for and against updating it so I'll leave it up to you and your team to decide.

@driesvints I also wanted to confirm - for the changelog, there were a few, but I figured those were being pulled directly from the PR titles, so I wasn't sure if I should fix them or not.  Can you let me know if those should be fixed or not?  I can see arguments both for and against updating it so I'll leave it up to you and your team to decide.

Nah, it's okay to leave those.

Nah, it's okay to leave those.

Sounds good.  Thanks for confirming!

Sounds good.  Thanks for confirming!


profiling: True

Setting profiling: True in the cabal.project file causes the hashes to change

(I just opened this PR to see how it works on CI, will close it later)

Fails on CI (https://hydra.iohk.io/build/1481342/nixlog/1) on the changes I made to get it to pass
For example, the expected hash for the TokenAccount contract on CI is add3a37fb97b24d6f36572498273c066168b2c5929400dee829dec4c390d07a0, which this PR changes to 496ff7cca4e2b3e758e15e3199b5c50ef2da37caa6e3206db2a8a78e963ceea3.

Yeah, I think this is somewhat expected, see https://github.com/input-output-hk/plutus/issues/1085#issuecomment-564493782. I observed differences in specialized functions in the PIR, so thanks GHC.


Use usePocketbase on server API route

Thanks for the project. Very useful.
I'm new to Nuxt 3, and assessing its server api capacity.
I'm trying to consume the usePocketbase composable in a server api route.
// /server/api/auth/login.post.ts
export default defineEventHandler(async (event) => {
  const pocketbase = usePocketbase();

  ...
});

I'm basically getting a 500 usePocketbase is not defined error. How can I make it so this can be used on the server api route?
Thanks!

@charbs-io You probably need to explicitly import the usePocketbase composable, as I don't think auto-imports works the same in the server directory.
// /server/api/auth/login.post.ts
import { usePocketbase } from '~/composables/pocketbase.ts'

export default defineEventHandler(async (event) => {
  const pocketbase = usePocketbase();
  ...
});

@charbs-io was sifferhans able to answer your question?
If not I can dig in further


imgpkg fails if location image pull is denied instead of not found

What steps did you take:
I ran ./imgpkg-darwin-amd64 copy -b "registry.pivotal.io/build-service/bundle:1.2.0" --to-repo gcr.io/cf-build-service-dev-219913/tom/tbs on imgpkg 0.9.0 and 0.10.0
What happened:
I got this error
Error: Reading Images from Bundle: fetching location image: GET https://registry.pivotal.io/v2/build-service/bundle/manifests/sha256-8ab4c32699209412c3f58b4a910aaefc3ace3d1e99b5770dffa20bebda5184fa.image-locations.imgpkg: DENIED: denied; denied

What did you expect:
I expected it to succeed like it used to on 0.8.0
Anything else you would like to add:
it appears the the location image fetcher only checks for not found errors and doesn't handle denied (which is what registry.pivotal.io) responds with
Environment:

imgpkg version (use imgpkg --version): 0.10.0
Docker registry used (e.g. Docker HUB):  regsitry.pivotal.io (harbor), trying to copy to gcr
OS (e.g. from /etc/os-release): os x

Vote on this request
This is an invitation to the community to vote on issues, to help us prioritize our backlog. Use the "smiley face" up to the right of this comment to vote.
👍 "I would like to see this addressed as soon as possible"
👎 "There are other more important things to focus on right now"
We are also happy to receive and review Pull Requests if you want to help working on this issue.

Looks like a regression introduced in 0.9.0. Prioritizing...


Use rem units for size to improve visibility on pages with a larger font

The rem units I used were calculated such that the calendar would appear the same on a page with html, body { font-size: 14px; } as it does currently on a page with any font size.

Thanks for changing this. Going to double check this to make sure it doesn't break our existing font sizes


Undefined index installation-source

Probably caused by #18, 'installation-source' field can be missing in package cache. Just add test and return default

Thanks :)


Expected an unbounded problem, but this problem has lower and/or upper bounds.

I have a bounded problem, I tried both PGPE and CMAES but I get the error:
Expected an unbounded problem, but this problem has lower and/or upper bounds.

Is there any solver for bounded problems?

Hello turian,
Thank you for your question, and for trying out EvoTorch!
These algorithms support bounded problems:

GeneticAlgorithm (see: https://docs.evotorch.ai/v0.5.1/reference/evotorch/algorithms/ga/#evotorch.algorithms.ga.GeneticAlgorithm)
Cosyne (see: https://docs.evotorch.ai/v0.5.1/reference/evotorch/algorithms/ga/#evotorch.algorithms.ga.Cosyne)
PyCMAES (which is an interface for the CMAEvolutionStrategy solver provided by the cma library; see: https://docs.evotorch.ai/v0.5.1/reference/evotorch/algorithms/pycmaes/#evotorch.algorithms.pycmaes.PyCMAES)

Distribution-based search algorithm implementations of EvoTorch such as PGPE and CMAES do not support strictly bounded problems. Still, you could define initial_bounds, and then augment your fitness function by adding penalty terms to discourage the exploration of the infeasible regions.
I think such an augmented problem definition could look like this (I hope it works and/or helps, feel free to let me know):
import torch
from evotorch import Problem, SolutionBatch

class MyBoundedProblem(Problem):
    ...

    def _evaluate_batch(self, batch: SolutionBatch):
        # Take the decision values from the solution batch
        values = batch.values

        # identify where the lower and upper bounds are violated within the batch
        lb_violated = values < self.lower_bounds
        ub_violated = values > self.upper_bounds

        # for each solution within the batch, compute the total amount of violation
        violation_amounts = (
            torch.where(lb_violated, self.lower_bounds - values, 0.0)
            + torch.where(ub_violated, values - self.upper_bounds, 0.0)
        ).sum(dim=-1)

        # get the clipped counterpart of the values, such that the boundaries are not
        # violated anymore
        clipped_values = torch.where(lb_violated, self.lower_bounds, values)
        clipped_values = torch.where(ub_violated, self.upper_bounds, clipped_values)

        # compute the fitnesses (or solution costs) using the clipped decision values
        fitnesses = SomehowComputeTheFitnesses(clipped_values)

        penalty_sign = 1.0 if self.objective_sense == "min" else -1.0

        # the magnitude of the penalty is 100 times the violation squared
        # (needs tuning according to the fitness scale of the problem at hand)
        penalties = penalty_sign * 100.0 * (violation_amounts ** 2)

        # Evaluations take into account fitnesses and the penalties
        batch.set_evals(fitnesses + penalties)

EvoTorch also introduced helper functions for detecting the amount of violations for constraints, and for penalizing them (using exponential penalization or using log barriers), but they have not been included in a release yet: https://github.com/nnaisense/evotorch/blob/master/src/evotorch/tools/constraints.py.
If you are okay with installing EvoTorch directly from its master branch on GitHub, you could also use these helper functions, if you prefer.
Feel free to let us know if you have further questions, or if something is not clear.


geoQuery.query() returns all the documents

Following code returns all the documents
const db = admin.firestore();
const collectionRef = db.collection('documents');
const geoFirestore = new GeoFirestore(collectionRef);

const geoQuery = geoFirestore.query({
    center: new admin.firestore.GeoPoint(52.1989266, 0.0499472),
    radius: 1,
});
const query = geoQuery.query();
query.get().then((querySnapshot) => {
    querySnapshot.forEach(function (doc) {
        console.log(doc.id, " => ", doc.data());
    });
});

Since the radius has been set to 1 km, it should only return the documents within that range. But this is not working as expected. Can you please let me know if the above code is correct?

Duplicate of #43 the docs should have been updated to explain this, I'd advise looking at my answer
https://github.com/geofirestore/geofirestore-js/issues/43#issuecomment-428469214

Thanks mate.  It would have been better if docs have clearly stated it.

#43 (comment)
Hi MichaelSolati,
In react native on listner not working...

@KSRajkumar45 I'd need to see some code as an example as well as your package.json. hopefully I can help from there

Hi Micheal,
I have tested this and i am also seeing the same behaviour in which the code is returning all documents, how is i use the following code below i get the correct results.
         const collectionRef = firebase.firestore().collection('Consents').orderBy('g').startAt(2)

         const geoFirestore = new
        GeoFirestore(collectionRef.where('d.details.ConsentType',"==",consentType))

         const geoQuery = geoFirestore.query({
         center: new firebase.firestore.GeoPoint(lat, long),
         radius: val,
         });

        geoQuery.on("key_entered",function($key, result) {
     console.log(key+result)

        }

      });

On a second note are we able to use firestore pagination as mention in the doc here
https://firebase.google.com/docs/firestore/query-data/query-cursors with
the library and if so can you point me to any working example ?

Pagination is not available. The library effectively does a form of pagination based on the geohash in order to do the query, and since we can not stack startAt (or other similar orderBy modifiers). We also can't do a limit because of how this is an aggregation of queries.
This part of the docs explains in detail why we can't do those two things. However in v3.1.0 you will have limit. I do first need to get through v3.0.0 as it's a massive rewrite, and I'm going through writing tests for it now.
While limit isn't in my current codebase for v3.0.0, you can test it via:
npm install geofirestore/geofirestore-js#v3.0.0
This is very much not guaranteed to be solid, but I do think it works well for what it is, and most kinks have been ironed out.

Paging does not remain possible even if you have a limit?


Who can decrypt the text?

I used ciphey to decrypt ''MS4wLjNb8Fnjj9gir_zccRZhnUuDvV8IryK41K8rkx9PLyvzlMMVzHGaemFu752w-VDQHVE"
But after 57 minutes, it still thinking.

Please in need help to decipher this phrase but I don't know the key
DBLZPB VNST SPWBM RKWULO MYZFF WNWSF FPPTWHJ GIPU QVTHTEB AFDCNCSK WDLMPEZ

And this too please
dblzpb vnst spwbm rkwulo myzff wnwsf fpptwhj gipu qvthteb afdcncsk wdlmpez icfa

can anyone decrypt this shit
8761bf

Hi. did you decipher the phrase?
dblzpb vnst spwbm rkwulo myzff wnwsf fpptwhj gipu qvthteb afdcncsk wdlmpez icfa

dblzpb


Build on ubuntu18.04

Unable to build due to:
CMake Error at CMakeLists.txt:57 (find_package):   Could not find a package configuration file provided by "unofficial-curlpp"
Cannot find package on linux

Use vcpkg to install @cumafo read the build instructions.

OK
I was following instructions as per
https://bestofcpp.com/repo/minio-minio-cpp-cpp-miscellaneous#releases
/C
From: Harshavardhana @.>
Reply to: minio/minio-cpp @.>
Date: Tuesday, 11 January 2022 at 08:31
To: minio/minio-cpp @.>
Cc: Curt Lestrup @.>, Mention @.***>
Subject: Re: [minio/minio-cpp] Build on ubuntu18.04 (Issue #10)
Use vcpkg to install @cumafohttps://github.com/cumafo read the build instructions.
—
Reply to this email directly, view it on GitHubhttps://github.com/minio/minio-cpp/issues/10#issuecomment-1009668828, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ACXETTVLVHLU4IOLN7HFXQDUVPMDTANCNFSM5LVRRUIQ.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.
You are receiving this because you were mentioned.Message ID: @.***>

OK I was following instructions as per https://bestofcpp.com/repo/minio-minio-cpp-cpp-miscellaneous#releases /C

That's not our doc read here https://github.com/minio/minio-cpp#install-from-vcpkg


Escape Inside for HTML

(Original issue 1388 created by None on 2017-10-28T15:59:34.305793+00:00)
I would like to be able to put LaTeX math in HTML output,
so it is formatted by MathJax. This can be done for LaTeX with
minted package using Pygments, with escapeinside feature.
There may be another way to do this, if there is a class of output
which Pygments emits raw "as is", then I could get my language
lexer to do the job.
[Trying to sign up with Atlassian at the moment]

(Original comment by skaller on 2017-10-30T23:49:49.211831+00:00)
Ok, finally got registered. Anyone here?

(Original comment by skaller on 2017-11-01T02:40:37.309977+00:00)
This issue should be replaced by another one I think. I have looked at this problem and I think what needs to happen is more fundamental, as follows:

First, we need a Math token standard in Pygments.

The formatters have to be upgraded so Math tokens are output raw.

For HTML this means wrapping the raw text of the Math token inside \( and \) delimiters, and also fixing Pygments to use these and not $ which is considered deprecated notation.
For LaTex, it would be the same. In both case we're primarily interested in inline math.
Then the various lexers have to be upgraded. This means at least my system felix, but also Ocaml. Ocaml uses 'a, 'b etc which should be typeset as the Greek letters alpha, beta, etc.
For HTML, the user, such as sphinx or whatever, will have to load mathJax. For LaTeX, it can already do math, provided it can see the math delimiters.
For lexers supporting inline math we will also usually want TWO lexers, one which actually formats the maths as maths, and one which formats the language encoding as written. Perhaps this can be handled with an option to a single lexer, I don't know, but typically an author will require both in a document so that they can explain that typing certain ASCII characters in program text is intended when mathematics is seen in the document. Alternatively this could be done by using a "text" lexer.


Support for HDFS HA

While fetching spark event logs in HDFS, dr. elephant just get the namenode address by dfs.namenode.http-address in startup. This property may be empty when using HDFS HA.
Anyone have time to add this feature?

Just in case you are not aware, there is a mailing list  for Dr. Elephant. I think it is worth adding it there.

Thanks, I will add it there or do it myself later :)

Hi @akshayrai , I'm confused why SparkFSFetcher use WebHdfsFileSystem to connect to HDFS.
Instead, use FileSystem.get(conf) can utilize the namenode HA automatically.
I just send a simple PR
It works fine in my cluster :)
By the way, the event_log_dir of spark fetcher should be set to [nameservice ID]/path...

@stiga-huang, thanks for this patch. I'll review it later today.

Closing this as it has been fixed in https://github.com/linkedin/dr-elephant/commit/2364c2627c0c0291a374067db454084be60a2be9.


Consuming Application crashes when consuming nLog.dll with another .dll in the same directory that "StartsWith" 'nLog'

I had an application which at one point we had a wrapper class for logging, after switching to nLog we just used nLog inside that wrapper class and left a lot of the calling code the same.
Everything worked fine until I upgraded to nLog 4.
As it turns out, becuase of the fact that there is another dll in the same directory that starts with 'nLog' (NLogLogger.dll) the TypeInitializer throws an exception and the application crashes.
This is easily reproduced by creating any file in the same directory as your nLog.dll and nLog.config files and call that file NLogLogger.dll. When the app starts it will throw a TypeInitializerException.
I have easily worked around this by changing the name of that assembly, but I thought it would be good to post in case anyone else is having a similar issue :)
Happy Coding!
Matt

Thanks for the report. This has to due with the auto loading feature added in NLog 4.
We will think for a solution. I'm not sure if a try-catch when loading the DLL is a good solution.


Custom build - macOS without FORTRAN?

Note: This is specific to macOS. Linux platforms don't run into this issue, and Windows isn't among our needs here.
Wild idea, but how much of AmberTools depends on compiling FORTRAN code? For context, our OpenFF stack and Psi4 have conflicts that seem to relate to libgfortran, and I'm not sure if the parts of AmberTools we need (primarily antechamber) depend on it. This has me wondering how feasible a stripped-down build would be, one without compiled FORTRAN code, and only for macOS.
This comment provides the most succinct context I can point to: https://github.com/psi4/psi4/issues/2024#issuecomment-722811014

I'm no longer in need of this - others may be and should raise a new issue if they are.


Fix placeholder

Closes https://github.com/holoviz-topics/panel-chat-examples/issues/35

Codecov Report
All modified lines are covered by tests :white_check_mark:

Comparison is base (bb337db) 93.65% compared to head (93aac31) 98.41%.
Report is 22 commits behind head on main.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##             main      #36      +/-   ##
==========================================
+ Coverage   93.65%   98.41%   +4.76%
==========================================
  Files           2        2
  Lines          63       63
==========================================
+ Hits           59       62       +3
+ Misses          4        1       -3

see 1 file with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Viewer triggeredoscilloscope

Added QTriggeredOscilloscope to default imports
Added triggered oscilloscope example (broken)
Spelling correction

The example is broken because BaseOscilloscope requires self.max_xsize, which is defined in QOscilloscope.

Thanks.


Allow resource to be specified as a metadata field per record

Context: Spark Streaming (Scala) to Elasticsearch
Use case:
Millions of json documents are sent to ES on an index based on a 'creationtimestamp' field.
The index pattern name is: transactions-{yyyy}-{MM}-{dd}
Issue is: when the record is already a json document, there is no way to define the target index name using a complex expression or technical fields that will not be indexed.

technical fields: not supported as es.mapping.exclude cannot be used for json documents (rationale??)
(workaround: json -> rdd(Map[String,Any]) -> json!!)
write pattern: mixes the target format and field format and crashes if different. Example:

es.resource.write =<EMAIL_ADDRESS>
Crashes if timestamp is a valid UTC timestamp ('2018-06-21 15:45:00.53') as I want the output pattern to be yyyy.MM.dd regardless of the actual timestamp format!!
Proposal: allow the target resource (e.g. index) to be provided as metadata (same as version)
Ex:
val airportsRDD = sc.makeRDD(Seq((Map(ID -> 1, RESOURCE-> "transactions-2018-06-02/tickets") , otp), ...))
airportsRDD.saveToEsWithMeta()

This has been discussed before (#991). The big problem here is that the connector is built in a way that expects a resource to be provided up front, either a simple index/type name or one with patterns. When performing a write operation with a simple index name, the connector is able to determine the locations of primary shards and pin to those primaries. If indices were able to be specified via the metadata map, then every user who uses the metadata map for indexing will lose this optimization, whether they use indices or not. This was a big enough change that we decided to not move forward with it at this time.
Now, there is some work that I would like to get to in the near future that would allow us to make best effort routing decisions for data in the connector instead of relying on knowing all primary locations apriori. That's tied to #1130, which if we can get that right, we might be able to move forward with features like this that take greater liberties with when an index name is known.


Ban crawlers from following target-redirect urls

If we update the "Platform" drop-down on the crate page to link directly (since the root page is guaranteed to exist on all targets and doesn't need checking) then we could probably ban crawlers from the target-redirect urls since they create a very dense, uninteresting, mesh of interlinking redirects.

@Nemo157 I guess this issue can be closed, right?

@Nemo157 I guess this issue can be closed, right?

👍

👍