Outlook email requires type in username every day.

Avoid duplicates

[X] I have searched the issues tracker for a bug report similar to mine, in vain

Steps to reproduce

wake up in a new day.
open my windows PC
open Ferdi
switch to my outlook tab
5. requires me to login
type in the mail address(username)
no need for the password, goes straight in.

Debug link
Debug link failed to produce, stuck at this page
Screenshots

Additional information
No response

Update to the issue:
I have confirmed that not just every day, but every time I open the Ferdi software it asks me to login.

I can confirm this but it only happens when accessing Outlook personal (i.e. live.com) and not when using outlook business (i.e. Office 365). As a workaround, edit the service, click on "Self hosted" and specify "https://outlook.live.com/mail/0/" as URL. Tnhis will keep you logged in.
I assume that the problem is related to some type of redirect always leading to the login form.

Thank you for the reply!
Yes it indeed works.


aurutils.t: failed to lock database

==> Finished making: aurutils-git 1.3.6.r44.g1b17bf7-1 (Tue Nov  1 13:59:52 CET 2016)
adding aurutils-git 1.3.6.r44.g1b17bf7-1
writing aurutils-test.db...
writing aurutils-test.files...
+ aurbuild -cd aurutils-test -a argfile
:: Synchronizing package databases...
error: failed to update core (unable to lock database)
error: failed to update extra (unable to lock database)
error: failed to update community (unable to lock database)
error: failed to update custom (unable to lock database)
error: failed to synchronize any databases
error: failed to init transaction (unable to lock database)
error: could not lock database: File exists
  if you're sure a package manager is not already
  running, you can remove /var/lib/pacman/db.lck
+ rm -rf /tmp/tmp.Z8zd1siF4M

Looks like it was just a stale lock file.


安装问题

Mac 上安装时，最后一条命令   make -j出错，如下所示。请问各位老师这个怎么解决呢？多谢

Hi @relinda2019 ,
You can pull the latest version and try again. In the new version, we require gRPC as a prerequisite and you can follow here to install gRPC before installation of FedTree.


Movie folder is empty

First folder, movies, has only two dots that return to top level
Second folder, serials, contains many subfolders like trends, top, popular, favorite
Your Environment

Version used: 0.0.43

Environment name and version: LibreELEC 8.2.4

Operating System and version: Linux x86_64

Link to Kodi debug log:

Can;t reproduce it.


📝 create_default_mappings -> add_default_mappings

Change from create_default_mappings to add_default_mappings, because calling create_default_mappings() resulted in an error.
I did not investigate why, but I found that the h pages of leap do in fact state that you should use add_default_mappings, so I tried that out and it worked.

nvm 🙈 , i was stuck on an old commit 😊


Deprecate -f flag from docker tag

Closes #9798
@maintainers please note that this is a change to the UX. We no longer
require the -f flag on docker tag to move a tag name from an existing image.
However, this does make us more consistent across our commands,
see https://github.com/docker/docker/issues/9798 for the history.
Signed-off-by: Doug Davis<EMAIL_ADDRESS>

I like consistency. Design LGTM.

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "Issue9798a" git@github.com:duglin/docker.git somewhere
$ cd somewhere
$ git rebase -i HEAD~2
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

Yup, I like consistency as well, design LGTM
also /cc @tianon, who opened the issue that this resolves :heart:

Is there still a way not to move the tag of an image if the tag exists?
I liked the -f behavior very much, since I usually don't want to move a tag, same as with git.

@schmunk42 no, if we do this then we'll move it every time.  Can you explain your scenario a bit? It sounds like you count on getting an error as part of your normal work flow - is that true? What do you do when you get the error to recover - just generate a new tag and try again?

LGTM+++

@schmunk42 Have you consider changing it so that you use docker images [tag] first to see if the name exists and then picking a new one if it does

@duglin Our workflow in some projects is to tag docker images on a release branch from a version-file.
Now, if someone accidentally pushes another commit with the same version on the release branch ... nothing happens, simply because the tag is already there.
I have something like this in our CI scripts:
VERSION=4.1.1
VERSION_MINOR=4.1
VERSION_MAJOR=4

docker tag ....:$VERSION
docker tag -f ....:$VERSION_MINOR
docker tag -f ....:$VERSION_MAJOR

btw: About consistency, I had opened a ticket to introduce -f here https://github.com/docker/machine/issues/2349
I don't really rely on the error, but I also like to be asked, before I change crucial things.
What's about tagging an image during local development, then later I move the tag accidentally - how do I get back the original version?

LGTM

The docker tag -f behavior already changed in 1.4.0 (the flag semantics were not honored), which forced us to add this flag in our 150+ repositories build scripts to keep the builds idempotent.
Seeing that this flag will be removed in 1.12 makes me very sad since we will have to revert this changes across all our repositories... I am OK with deprecation for consistency, but can't the actual removal happen in a major release (2.x)?

@bjaglin it will be removed in docker-1.12 so ppl should have time to update their stuff. For now you just get a warning

@bjaglin You're 100% on spot.
@runcom We will run into this issue, since we're using CI runners on different hosts, probably dozens at 1.12, we will need to detect the docker version an act accordingly.

We also use -f to overwrite a tag in our build environment when generating images.@bjaglin's problem case is bang-on to our problem case as well.
I understand why -f is getting deprecated since docker tag is reverting to its old behaviour (yay!), but at the same time this is a major UX change which should not be rolled into a minor release IMO as it breaks the semver contract. Looking at the history of previous UX changes like the very change that introduced this behaviour, third party projects like Drone, Packer, Mesos and Deis have had to tweak things in the past because client UX changed.
I guess that also brings me to my question... What can we consider covered by a semver contract in docker if existing client features keep being broken in minor releases? A few examples of breaking changes in the client that have occurred would be when docker inspect output changed and the all-too-familiar --insecure-registry flag change. Is it safe to say that the client is to be considered semver-incompatible and the only thing covered by Docker's semver contract would be the remote API?

Given we haven't moved from "1.x" ever I don't think waiting for a major release version is much of an option.  The best Docker has is the "give 'em 2 release warning": https://github.com/docker/docker/blob/master/docs/misc/index.md#feature-deprecation-policy

Yeah, the flag isn't gone yet (your scripts should still work as-is),
it's just turned into a warning now (and doesn't have any effect).

docs team please be more specific about the deprecation, right now when you use -f flag it says
Warning: '-f' is deprecated, it will be removed soon. See usage.

Ok, let's take a look on usage https://docs.docker.com/engine/reference/commandline/tag/, what it says about -f? Right, nothing.
So what is current behavior is? Does it force or not? Do I need to manually delete tag before using it? The only one way to find out is to actually find this deprecation commit.
It is always good to tell users, who used this before - what is the "migration" plan is.

@outcoldman the deprecation is explained here; https://docs.docker.com/engine/deprecated/. The reason the flag is no longer mentioned on https://docs.docker.com/engine/reference/commandline/tag/ is because it's been deprecated; see this PR, which removes it from the docs

@thaJeztah great, but how I can get to this page? I'm not trying to argue about this deprecation, I am trying to point on the luck of documentation in usage/help, when the deprecation message says Warning: '-f' is deprecated, it will be removed soon. See usage..

@outcoldman that message is automatically generated for flags that are marked deprecated; usually, a flag is deprecated in favor of another flag, and is a bit more informative;
https://github.com/docker/docker/blob/34a83f9f2c0516b3c5e7024393487eee54309401/pkg/mflag/flag.go#L25
If you're have a suggestion on how to improve that message, feel free to add.

@thaJeztah for example standard library always require you to specify a deprecation message, see https://godoc.org/github.com/spf13/pflag#FlagSet.MarkDeprecated (and https://github.com/spf13/pflag/blob/master/flag.go#L311) not something auto-generated, but informative for user.
This is just a suggestion.

That's not the standards library; the standards library (https://golang.org/pkg/flag/) doesn't have a way to deprecate flags, hence the (slightly hacky) mflags package was created. I agree that a custom deprecation message could be nice, possibly replacing mflags with pflags could be an option, however, with the deprecation page, and a mention in the change logs, it's not our top priority; PRs welcome though

IMO it'd definitely be neat to adjust our flags package to allow for the deprecation message to be generally customized so we could add a link to our deprecation page :innocent:


Web - Thread reply with concierge gets automatically pinned even if the original chat is not pinned

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open a new account
Unpin the concierge
Hover over the first message from concierge and reply in thread
Go back and open the thread again by clicking on the "1 Reply" button

Expected Result:
The thread should not be automatically pinned
Actual Result:
Thread replies from concierge gets pinned
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android / native
[ ] Android / Chrome
[ ] iOS / native
[ ] iOS / Safari
[x] MacOS / Chrome / Safari
[ ] MacOS / Desktop

Version Number: 1.3.35-5
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/93399543/8added2d-710f-4a96-aa48-20fbb7dd09b9
https://github.com/Expensify/App/assets/93399543/6d46f532-b0e4-4e12-8ed1-d62e32594abe
Expensify/Expensify Issue URL:
Issue reported by: React JS development and Quality Assurance (GH @Nathan-Mulugeta)
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1688209194465719
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01edf19e94d20b64a5
Upwork Job ID:<PHONE_NUMBER>803575808
Last Price Increase: 2023-07-04

This seems BE issue.
After reply in thread, BE first responds report with isPinned: false, and if reopen the thread again, BE responds report with isPinned: true.

Yup, I can reproduce this one. I don't think a thread in the Concierge DM should be automatically pinned in the same way that a thread in any other chat (pinned or not) doesn't assume the parent chat's pinned status.

Based on this comment, adding internal as a backend issue.

It seems unlikely that this is only occurring on web, did we not test the other platforms?

Ah yes, I forgot to remove the web specific piece from the OP. It's reproducible on on all.

I ran out of time to triage this today, it's top of the list for tomorrow

I had another insane day. Will get to this soon for triage

Finally done with deploy dyte and found time. Agree it's likely backend and will investigate further when I have a moment.

Investigating this today

I fixed this with a backend PR, which can't be tested by C+ team.

Has been deployed to prod, closing

Wait, we need to pay reporting bonus to @Nathan-Mulugeta in two days time.

Hey @Julesssss payment has not been processed yet.

Bump to remind about payment @Julesssss

Ah woof, the header didn't update and I missed it on the 27th. Apols! @Nathan-Mulugeta I've sent you an offer on this job here.

Just accepted offer @trjExpensify


osu-lazer-bin won't build

Pinned version (2023.510.0) seems to be absent on Github which is causing the update.sh script to not work either.

It was probably deleted in favor of 2023.511.0. Will update.

It is now pushed. Can you check whether it works?

It works! Thank you for taking the time to solve this issue.


Finish notification system

Implement the notification drawer in the header. See http://www.patternfly.org/pattern-library/communication/notification-drawer/ for a reference.

Now part of #61


Closes #282: Test Data Guidance vignette

Thank you for your Pull Request! We have developed this task checklist from the Development Process Guide to help with the final steps of the process. Completing the below tasks helps to ensure our reviewers can maximize their time on your code as well as making sure the admiral codebase remains robust and consistent.
Please check off each taskbox as an acknowledgment that you completed the task or check off that it is not relevant to your Pull Request. This checklist is part of the Github Action workflows and the Pull Request will not be merged into the devel branch until you have checked off each task.

[x] Place Closes #<insert_issue_number> into the beginning of your Pull Request Title (Use Edit button in top-right if you need to update)
[x] Code is formatted according to the tidyverse style guide. Run styler::style_file() to style R and Rmd files
[x] Updated relevant unit tests or have written new unit tests, which should consider realistic data scenarios and edge cases, e.g. empty datasets, errors, boundary cases etc. - See Unit Test Guide
[x] If you removed/replaced any function and/or function parameters, did you fully follow the deprecation guidance?
[x] Update to all relevant roxygen headers and examples, including keywords and families. Refer to the categorization of functions to tag appropriate keyword/family.
[x] Run devtools::document() so all .Rd files in the man folder and the NAMESPACE file in the project root are updated appropriately
[x] Address any updates needed for vignettes and/or templates
[x] Update NEWS.md if the changes pertain to a user-facing function (i.e. it has an @export tag) or documentation aimed at users (rather than developers)
[x] Build admiral site pkgdown::build_site() and check that all affected examples are displayed correctly and that all new functions occur on the "Reference" page.
[x] Address or fix all lintr warnings and errors - lintr::lint_package()
[x] Run R CMD check locally and address all errors and warnings - devtools::check()
[x] Link the issue in the Development Section on the right hand side.
[x] Address all merge conflicts and resolve appropriately
[x] Pat yourself on the back for a job well done! Much love to your accomplishment!

While not involved - I am excited that there is going to be a vignette around this!!

Is admiraldev the right place for this information? The text is quite admiraldata-specific.
The first three section could be the README of admiraldata and the other sections a developer vignette for admiraldata.
Maybe we should just refer to the admiraldata pages. Then we do not need to maintain this information in two places.
What do you think?

Maybe you're right. If so I still think we should have a page in {admiraldev}, with reduced info, and point to this page in {admiraldata}. @kaz462 what do you think?

Is admiraldev the right place for this information? The text is quite admiraldata-specific.
The first three section could be the README of admiraldata and the other sections a developer vignette for admiraldata.
Maybe we should just refer to the admiraldata pages. Then we do not need to maintain this information in two places.
What do you think?

Maybe you're right. If so I still think we should have a page in {admiraldev}, with reduced info, and point to this page in {admiraldata}. @kaz462 what do you think?

I would also add something (a short paragraph and/or a link) to the "Writing Vignettes" vignette.
In principle, we should also add something to the templates guidance but we do not have any. Should we add one?

In principle, we should also add something to the templates guidance but we do not have any. Should we add one?

What do you mean by template guidance?

In principle, we should also add something to the templates guidance but we do not have any. Should we add one?

What do you mean by template guidance?

We provide several templates in inst/templates but we do not have a guidance for these files, e.g., we do not describe when templates should be created, how they should be structured, which data they should use, ...

Is admiraldev the right place for this information? The text is quite admiraldata-specific.
The first three section could be the README of admiraldata and the other sections a developer vignette for admiraldata.
Maybe we should just refer to the admiraldata pages. Then we do not need to maintain this information in two places.
What do you think?

Maybe you're right. If so I still think we should have a page in {admiraldev}, with reduced info, and point to this page in {admiraldata}. @kaz462 what do you think?

I would also add something (a short paragraph and/or a link) to the "Writing Vignettes" vignette.
In principle, we should also add something to the templates guidance but we do not have any. Should we add one?

Agree we should put most of the data strategy info at pharmaversesdtm README/website, and link it at admiraldev with a brief overview.


Add missing annotations to lax

@hawkinsp Would you mind looking over this again?  I've adjusted the code in response to your comments.

(Closing and reopening to force a CI rebuild.)

This PR appears to cause test failures under pytype, which we also check with (internally, although I would imagine you can reproduce by just running pytype on the PR). I found this patch fixes it:
--- a/google3/third_party/py/jax/_src/lax/lax.py
+++ b/google3/third_party/py/jax/_src/lax/lax.py
@@ -99,13 +99,14 @@ def _array_copy(arr):
     return bitwise_or(arr, _const(arr, False))
   return add(arr, _const(arr, 0))

-def _try_broadcast_shapes(shapes):
+def _try_broadcast_shapes(
+    shapes: Sequence[Tuple[int, ...]]) -> Optional[Tuple[int, ...]]:
   assert shapes
   if len(shapes) == 1: return shapes[0]
   rank, *others = {len(shape) for shape in shapes}
   if others: return None  # must have consistent rank
   if not rank: return ()  # scalar case
-  result_shape = [None] * rank
+  result_shape = [-1] * rank
   for i, sizes in enumerate(zip(*shapes)):
     non_1s = set([d for d in sizes if not core.symbolic_equal_dim(d, 1)])
     if len(non_1s) > 1:
@@ -125,7 +126,8 @@ def broadcast_shapes(*shapes: Tuple[int,
   if result_shape is None:
     raise ValueError("Incompatible shapes for broadcasting: {}"
                      .format(tuple(shape_list)))
-  return result_shape
+  else:
+    return result_shape

 def _identity(x): return x

Mind making those changes?
(Sorry for the slow review, I was out for the holidays.)

No problem, and done.

return result_shape

else:
return result_shape

I didn't make this change though since I don't understand how it would change anything?  Most linters complain about the unnecessary else.

pytype passes on my machine

$ pytype jax/_src/lax/
Computing dependencies
Analyzing 13 sources with 138 local dependencies
ninja: Entering directory `.pytype'
[118/238] check jax._src.lax.lax
[231/238] check jax._src.lax.polar
FAILED: /Users/neil/src/jax/.pytype/pyi/jax/_src/lax/polar.pyi
/Users/neil/.pyenv/versions/3.7.12/bin/python3.7 -m pytype.single --imports_info /Users/neil/src/jax/.pytype/imports/jax._src.lax.polar.imports --module-name jax._src.lax.polar -V 3.7 -o /Users/neil/src/jax/.pytype/pyi/jax/_src/lax/polar.pyi --analyze-annotated --nofail --quick /Users/neil/src/jax/jax/_src/lax/polar.py
File "/Users/neil/src/jax/jax/_src/lax/polar.py", line 27, in <module>: Couldn't import pyi for 'jax.scipy' [pyi-error]
  Unreplaced NamedType: 'jax.scipy.fft', referenced from 'jax.scipy'

For more details, see https://google.github.io/pytype/errors.html#pyi-error
ninja: build stopped: subcommand failed.
Leaving directory '.pytype'


fix: stoichiometric consistency

Description of the issue:
According to memote report, stoichiometric concistency is one of the lowest scores of the model, and thus one obvious task for further improvement. This inconcistency is probably caused by metabolites lacking chemical formula.
The memote output:

Stoichiometric inconsistency violates universal constraints: 1. Molecular masses are always positive, and 2. On each side of a reaction the mass is conserved. A single incorrectly defined reaction can lead to stoichiometric inconsistency in the model, and consequently to unconserved metabolites. Similar to insufficient constraints, this may give rise to cycles which either produce mass from nothing or consume mass from the model. Implementation: This test first uses an implementation of the algorithm presented in section 3.1 by Gevorgyan, A., M. G Poolman, and D. A Fell. "Detection of Stoichiometric Inconsistencies in Biomolecular Models." Bioinformatics 24, no. 19 (2008): 2245. doi: 10.1093/bioinformatics/btn425 Should the model be inconsistent, then the list of unconserved metabolites is computed using the algorithm described in section 3.2 of the same publication. This model contains 1288 (62.13%) unconserved metabolites.

Expected feature/value/output:
Improved model concistency with fewer unconserved metabolites
Reproducing these results:
Run memote report snapshot to recreate memote report.
To do:
If specific curations are proposed, generate a list of checkboxes of steps that should be followed to solve this issue:

[ ] Check the cause of these inconcistencies, i.e. find out which metabolites lacking chemical formula or unbaklanced reactions
[ ] Add chemical formula and balance reactions as far as possible. Extract knowledge from DBs either automatically or manually

I hereby confirm that:

[x] This problem persists in the master branch of the repository
[x] A similar issue does not already exist
[x] I've considered asking this first in the Gitter chat room

See issue #80 for more details


Add option to set time key for elasticsearch

Signed-off-by: Thomas Draebing<EMAIL_ADDRESS>
What this PR does / why we need it:
The PR adds an option to change the time key for the elasticsearch backend in the fluent-bit helm chart. This allows to set a time_key other than the default (@timestamp), which could lead to errors, when merging JSON logs into the log structure, if the logs also contained a @timestamp-key (e.g. kibana).
Which issue this PR fixes
When using filter.mergeJSONLog: true, while some other application also used the default time key @timestamp, JSON logs could not be merged correctly, resulting in errors.
Special notes for your reviewer:

/lgtm

/ok-to-test

/assign @mattfarina

/approve


Update build-store-front-backend.md

Fix REQUIREMENTS URL ,
Thanks, Mr. Mohamed For You Effort

thanks for the pull request @EGYWEB-Mohamed  but you redirect people to my solution :D


Impls BigRat pow for negative powers

This also changes the behavior of 0^0 to be 1
as opposed to undefined

Hi Eli! Been a while since we last spoke. When I went to use pow for BigRat, I noticed that these features were missing. Also, I changed the behavior of 0^0 to being 1 from being undefined which may be controversial 🤷. Would love any guidance on how to add proper test cases any other egglog-dev conventions as this is my first PR. Happy Holidays!

Thanks for the PR! I think for tests the easiest way to add them for this kind of change is to add to an existing .egg test file or create a new one that runs some check commands to verify that the output of the primitives matches what you expect.


Document pmpu APIs as stabilised

Following up on #8103, and the subsequent discussion in #8108 - it appears that the pmpu APIs are already stable, but still tagged as "experimental".
Yhe correct way to resolve this is by removing the experimental tag and documenting them properly (in docs/).
cc @talSofer

@yonipeleg33, it's not experimental - the tag was left there and should have been removed earlier.
Can you please specify what stabilizing means? Is the API flaky? Do we have a bug? I think you might be using the wrong terminology

You're probably right, I meant only in the documentation level - removing the "experimental" tag, and adding proper documentation, following up on @arielshaqed's comment: https://github.com/treeverse/lakeFS/pull/8108#discussion_r1734261646
My intent with the original PR was fixing a technical "bug" in the documentation, but as it turned out, it is more big of a deal than I originally thought, so after discussing privately with @talSofer I decided to open a new issue for it and triage-ing it properly...

@N-o-Z I have updated the title and description, lmk if that's any better

@N-o-Z I have updated the title and description, lmk if that's any better

Great! Thank you for clarifying

@N-o-Z why was this experimental in the first place? What changed since then? Is there full support for all Cloud vendors?
@arielshaqed - maybe you can shed more context on why was this experimental?

@N-o-Z why was this experimental in the first place? What changed since then? Is there full support for all Cloud vendors? @arielshaqed - maybe you can shed more context on why was this experimental?

This is one method of development we practice. We release something as experimental and if useful and works well we remove the experimental tag.
This was done a long time ago, and the decision to make it a "formal" API was taken a long time ago but was not executed.
This set of APIs is designed to work ONLY with S3. Enabling it for other block stores will require research into each storage we want to implement it for and might not be possible for some block stores


Problems with uploads

Hello -- I'm running a script to upload a TGZ image for Juniper EX3400 devices, the script runs and it says that it uploaded files but when I log into the device the files are missing from /var/tmp
Please, confirm the upload of junos-arm-32-20.4R3-S3.4.tgz on:
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
<IP_ADDRESS>
Proceed? [n]|y: y
--------------------------------------------------------------------------------
Please insert your username: root
And your password
Password:
--------------------------------------------------------------------------------
Upload on: <IP_ADDRESS>
Upload on: <IP_ADDRESS>
Upload on: <IP_ADDRESS>
Upload on: <IP_ADDRESS>
Upload on: <IP_ADDRESS>
Upload on: <IP_ADDRESS>
Upload on: <IP_ADDRESS>
Upload on: <IP_ADDRESS>
Upload on: <IP_ADDRESS>
Upload on: <IP_ADDRESS>
Upload on: <IP_ADDRESS>
Upload on: <IP_ADDRESS>
================================================================================
Uploads completed in 7.7323243618011475 seconds.

Hi,
Unfortunately, I have no Juniper device to test it. But, this script use mostly the SCP function of Netmiko described here:
https://pynet.twb-tech.com/blog/expanding-netmiko-secure-copy-support.html
Maybe you can try it with a single device, using this snippet of code below, to see if it works:
https://github.com/twin-bridges/pynet_articles/blob/main/netmiko_scp/test_file_transfer.py
If you have the same problem with a single device and the above script, it's probably an issue with your device/credentials/permissions, or anything similar. Or eventually with the Netmiko code itself. I'm not the author.
I let you check that first. Thank you.
Jerome

Hi @jerome-t, just reporting that it worked with a single device using test code linked.

Closing as I went another way for transfers. Thanks.


Issue 3975

Proposed changes:

fix rasa interactive part #3975
rename sender-id to conversation -id

Status (please check what you already did):

[x] added some tests for the functionality
[ ] updated the documentation
[x] updated the changelog (please check changelog for instructions)
[x] reformat files using black (please check Readme for instructions)

Tom said in the issue that we should expose sender-id, you used conversation-id because that's what the contributor for rasa shell did?

Yep, there was a slack conversation where we decided to go for conversation-id

Btw, in the future it'd be helpful if the name of the PR referenced the changes themselves instead of the issue -- i had trouble finding it in the PR list


Add email-validator into install requires

WTForms introduce a breaking change in 2.3.1, it replaces regex implementation with third party library email-validator (https://github.com/wtforms/wtforms/pull/429) for Email validator. When people use the Email validator without email-validator installed, it will throw out an exception. This PR adds email-validator into install requires since it's a common need when developing web applications with Flask-WTF.

Codecov Report

Merging #421 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #421   +/-   ##
=======================================
  Coverage   97.97%   97.97%
=======================================
  Files          18       18
  Lines         936      936
  Branches       73       73
=======================================
  Hits          917      917
  Misses         17       17
  Partials        2        2

Continue to review full report at Codecov.

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

The core functionally of (Flask-)WTForms is not to provide email validation, and while it's useful it's not universal, so I don't think it should be required.

Maybe we can make an email flask-wtf extra requirement that would install wtforms[email], so in the end, the user can chose whatever option fits the most.

@azmeuk Sounds reasonable,  I will do it.


undefined method `autocomplete_field' for #ActionView::Helpers::FormBuilder:0x007fce8ce7b730

undefined method `autocomplete_field' for #ActionView::Helpers::FormBuilder:0x007fce8ce7b730
why?

MicropostController
autocomplete x x
but  view
my micro post form in users/show.html.erb
and has this error

it's OK after restart the web server!


expm2 => expm

Deprecated in SciPy expm2 function changed to expm

This seemed to solve this error: https://github.com/pybrain/pybrain/issues/228
Thanks!

Can this be merged and released in a new bugfix version ?
The conda-forge package for pybrain is blocked due to this issue - https://github.com/conda-forge/staged-recipes/pull/4653


Attempt to improve messaging for keg-only formulae that are installed…

Attempt to improve messaging for keg-only formulae that are installed as dependencies.  https://github.com/Homebrew/discussions/discussions/1415#discussioncomment-700699

[x ] Have you followed the guidelines in our Contributing document?
[x ] Have you checked to ensure there aren't other open Pull Requests for the same change?
[ x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ x] Have you written new tests for your changes? Here's an example.
[ x] Have you successfully run brew style with your changes locally?
[ x] Have you successfully run brew typecheck with your changes locally?
[ ] Have you successfully run brew tests with your changes locally?

Perfect, thank you so much.
On Thu, May 20, 2021 at 6:04 AM Mike McQuaid @.***>
wrote:

Closed #11367 https://github.com/Homebrew/brew/pull/11367 via #11413
https://github.com/Homebrew/brew/pull/11413.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Homebrew/brew/pull/11367#event-4772813688, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAADBUE3FYEHGWS5OZQQ5DTTOT3GFANCNFSM44WXQ6WQ
.


tests: net: tcp2: llegal use of the EPSR

Describe the bug
tests/net/tcp2/ is failed on nucleo_f429zi, nucleo_f746zg (all boards running this test on STMicroelectronics test bench)
This is a regression introduced by #28302 Misc TCP2 fixes
and more specifically
SHA1: 80d04616de61f6f2601d7a3ea7ff09bf7506af74 net: tcp2: Honor TCP retry count limit from Kconfig file  (git bisect)
To Reproduce
Steps to reproduce the behavior:

west build -p auto -b nucleo_f429zi tests/net/tcp2/
west flash
See error

Expected behavior
Test passed
Logs and console output
*** Booting Zephyr OS build v2.4.0-rc1-280-gb5c2ff93974f  ***
Running test suite test_tcp_fn
===================================================================
START - test_presetup
 PASS - test_presetup
===================================================================
START - test_client_ipv4
 PASS - test_client_ipv4
===================================================================
START - test_client_ipv6
 PASS - test_client_ipv6
===================================================================
START - test_server_ipv4
 PASS - test_server_ipv4
===================================================================
START - test_server_with_options_ipv4
 PASS - test_server_with_options_ipv4
===================================================================
START - test_server_ipv6
 PASS - test_server_ipv6
===================================================================
START - test_client_syn_resend
 PASSE: ***** USAGE FAULT *****
E:   Illegal use of the EPSR
E: r0/a1:  0x2000c6d8  r1/a2:  0x20000fa0  r2/a3:  0x20000fa0
E: r3/a4:  0x00000000 r12/ip:  0x00000004 r14/lr:  0x0800c39b
E:  xpsr:  0x6000000f
E: Faulting instruction address (r15/pc): 0x00000000
E: >>> ZEPHYR FATAL ERROR 0: CPU exception on CPU 0
E: Fault during interrupt handling

E: Current thread: 0x20000fa0 (main)
E: Halting system

Environment (please complete the following information):

OS:  Linux and Windows
Toolchain:Zephyr SDK
Commit SHA :0e49f5570ce5d0434d45f115c7391dd95be81b07

Can you try #28624 if it helps for stm32? I just fixed similar issue for frdm_k64f.

@jukkar , yes #28624 solves this this on both boards nucleo_f429zi, nucleo_f746zg

Duplicate of #28602


Fix broken headings in Markdown files

GitHub changed the way Markdown headings are parsed, so this change fixes it.
See bryant1410/readmesfix for more information.
Tackles bryant1410/readmesfix#1

Hi, thanks for patch!


Did you forgot to publish @pezzo/common package? Getting error "Cannot find module @pezzo/common"

Report
Updated to from previous releases
"@pezzo/client": "^0.2.0",
"@pezzo/integrations": "^0.1.8"
and when run build, getting an error
node_modules/@pezzo/client/src/client/Pezzo.d.ts:2:47 - error TS2307: Cannot find module '@pezzo/common' or its corresponding type declarations.

2 import type { CreatePromptExecutionDto } from "@pezzo/common";

Expected behavior
Expect not to get such a build issue
Steps to reproduce the problem

pull the latest version of client / integration packages and try to use it :)

Logs (if applicable)
node_modules/@pezzo/client/src/client/Pezzo.d.ts:2:47 - error TS2307: Cannot find module '@pezzo/common' or its corresponding type declarations.

2 import type { CreatePromptExecutionDto } from "@pezzo/common";

Pezzo version
client version 0.2.0
How do you use Pezzo?
Kubernetes Deployment

@arielweinberger @ItayElgazar and the worse part is that we already updated our server and so all migrations are run and old client packages do not work anymore with the new version of the server:
[ExceptionsHandler] Unknown type "FindPromptByNameInput". Did you mean "PromptWhereInput"?: {"response":{"errors":[{"message":"Unknown type \"FindPromptByNameInput\". Did you mean \"PromptWhereInput\"?","locations":[{"line":1,"column":44}],"extensions":{"code":"GRAPHQL_VALIDATION_FAILED","stacktrace":["GraphQLError: Unknown type \"FindPromptByNameInput\". Did you mean \"PromptWhereInput\"?","
...
at makeRequest (/srv/xxxxxxxx/node_modules/@pezzo/client/node_modules/graphql-request/build/cjs/index.js:310:15)
at process.processTicksAndRejections (node:internal/process/task_queues:95:5)


Forked jsLDA and am refactoring the JS/HTML/CSS

Hi David,
I will let you know when phase 1 is complete to see if you are interested in using any of it.  Using a responsive layout and perhaps will migrate to React.js. in Phase 2.
Thanks so much for sharing this!  Please advise if you have suggested modifications to any of the algorithms.
Owen Dall

I see you already split into JS/HTML/CSS.


Search Editor: number input box & Toggle Context Lines button suggestions

Several related suggestions for Search Editor:

add tooltip for the number of context lines input box;
swap position of the number input box and the Toggle Context Lines button;
change tooltip text for that button to "Context Lines";
disable the number input box when the Context Lines button is switched off;
add border line around the Context Lines button when it is switched on, use the same line as it is around Match Case / Match Whole Word / RegEx buttons when they are switched on.

Currently, it is not always clear enough if the context lines option is switched on or off just by looking at the displayed resulting lines. If you see just one line with the search result: it could be that the button is switched off, or in some rare cases, it could be that the file with the matched line has just single line of text and no surrounding lines.

They're reasonable suggestions but I do not have capacity to take this on at the moment. Thus moving to backlog and marking as help wanted.

I'd like to take this

@quanzhuo thanks! Let me know if you need any pointers.

@quanzhuo If you are going to implement these suggestions, maybe you could also take a look at this related bug: #140612.

@Z-E-D OK. Got it

Thank you for submitting your feature request and everyone who considered it! Unfortunately, this issue did not receive enough votes over the allotted time, and so we are closing the issue. PRs are welcome so you can create a PR that fixes this if you are passionate about getting this feature across the finish line. Thanks!


scraping errors will show in the log when debug mode is enabled

closes #2820
@beorn7
Signed-off-by: Krasi Georgiev<EMAIL_ADDRESS>

Thanks!


Support hyper parameter for activation layer

Our framework currently does not receive hyperparameters when implementing the activation layer. Because of this, layers that require separate hyperparameter settings such as Leaky ReLU are always implemented to operate with a fixed constant value for now. If technically possible but not applied, we need to update existing activation layers(leaky, selu, and so on).

:octocat: cibot: Thank you for posting issue #2614. The person in charge will reply soon.


[Bilinear] Allow non-uniform angles

Allow the camera angle index to be a float and use the same strategy as batch 1 to interpolate the camera angles.

Punting this until I have a reason to use it.


Non-Deterministic Unit Test Fail

Tests in Karma run in parallel in many different iframes, which means there can be non-deterministic fails if two tests write/read from persistent storage (local storage) at the same time. The Options test suite periodically fails, but is fixed if you re-run it enough times.

I believe I solved this... only time will tell with probabilistic certainty. Yay non-determinism!


Add "color" option type

Is your feature request related to a problem? Please describe.
See https://github.com/f3d-app/f3d/issues/1570
F3D support many option with different option types, it would be beneficial to support a new "color" option type instead of relying on double vector. A color should obviously be stored in a double_vector of size 3.
Describe the solution you'd like

Add it to types.h with the correct API
Add a naive parse/format methods to options_tools.h.in
Use it for at least one option in options.json
Add testing in TestSDKOptions*

Thanks for creating this issue


Kali Linux does not want run

Environment
Windows build number: [run `cmd.exe /c ver`]
Your Distribution version: [On Debian or Ubuntu run `lsb_release -r` in WSL]
Whether the issue is on WSL 2 and/or WSL 1: [run `cat /proc/version` in WSL]

Steps to reproduce

WSL logs:
Expected behavior

Actual behavior

Installing, this may take a few minutes...
WslRegisterDistribution failed with error: 0x8000000d
Error: 0x8000000d An illegal state change was requested.

/dupe #4084


Introduce cleaner to clean AllocMemory and MemoryMappedFile

Introduce cleaner for AllocMemory and MemoryMappedFile
Get Rid of requireFree method
Fix constructors in AllocMemory
Remove unsafe.reallocateMemoryCalls
AllocMemory is now extends NativeMemory
Deprecate NativeMemory(ByteBuf) and instead use NativeMemory.wrap(ByteBuf)
Documentation Fix

Coverage increased (+0.02%) to 98.67% when pulling 0b63dd76d248dca02f32ae73f45d2865ff87aa33 on niketh:master into 8632249b7f95d1a0a60da10a72102eb10b581c8c on DataSketches:master.


 should probably have a :host display style of block

This risks dipping into Spring '83 spec territory, but in my limited experience I've yet to find a reason for <spring-board> to not default to display: block. 🤔 Setting width, height and background-color on the element doesn't really work out the box otherwise.

This ought to be in the specification -- I will add it to the client section of the new draft. (Honestly, I always forget that custom elements don't have display: block set; and this has caused me problems in the past!)

Ooh, okay! This this should most certainly happen. 🙌


Move demo into a separate repo

Conceptually, the bookstore demo should be completely decoupled from OSM implementation details. Separating the OSM and demo source code will help enforce this distinction.
The most sensitive areas of OSM to this change are demo documentation and CI tests. The core of OSM shouldn't need any modification that would adversely affect stability.

The demo manifests have been moved to the osm-docs repo.

This issue is to track all of the demo, including source code for the book* services and scripts. The manifests referenced in the docs are just one piece.

This issue is to track all of the demo, including source code for the book* services and scripts. The manifests referenced in the docs are just one piece.

I don't think we should be increasing the maintenance overhead by moving the automated demo manifests outside the osm repo. It is being used by the CI and developers and seems well suited to be within the osm repo. Sometimes it's also helpful to evolve the demo with new features (e.g. mySQL integration) so having the automated demo within the osm repo makes a lot more sense to me.

I think i agree with @shashankram here, we are not yet ready to move all the demo related code to a separate repo. As of today, having it as a part of osm will help with faster turnaround, be it testing one's changes locally or extending out the demo to cover newly developed scenarios/ integrations

Closing since we're not planning to do this anytime soon.


Finish coordinate suite

Finish the coordinate parser regex and edge case detection

This is definitely the most complex part of the suite. The general ethos around the parsing is that we try and make our capture groups as deterministic as humanly possible. Less tricks in the regex the better for simplification sake. E.g. for a coordinate passed to us in DD form we will always capture the following groups, regardless if there is a value there or not:
[dir][sign][degrees][decimals][dir][sign]

With this, we can capture either lon or lat independently, or combined by simply concating the regex's. Additionally, we now have more deterministic inputs for our value normalization described further below.
The current Regex partials can be found here:
packages/geo/src/coordinates/regex.ts
packages/geo/src/coordinates/match.ts

We currently are testing against a number of variations for each coordinate format as seen here:
packages/geo/src/coordinates/__fixtures__/index.ts

This covers the bulk of the edge cases and or use cases that you would see in the wild. We will want to slightly adjust these fixtures potentially just so that the snapshot output is a tad more consistent and or our expect() calls can be simplified a bit or in a more generic way.

Finish the coordinate normalization

Given that we now have the input, either from a machine or a user, deterministic split into N number of capture groups, we can normalize this input into a common form. Notably, regardless of the input format, we want the normalized format to be a simple float value that can then be used as the input for external formatting outwards. E.g. N 87.2123 would become 87.2123 , 87.2123 S would become -87.2123 etc.
We have some initial work started for this for specifically the DD format capture groups here:
packages/geo/src/coordinates/normalize.ts

Create coordinate formatting

Given our normalized float value for both lon and lat we can take that and format it into the common standards of DD, DMS, DDM. We might be able to actually reuse the regex segments to assist with this but this area is largely tbd. Additionally, we will potentially need to support MGRS, CGRS, and other standard military coordinate formats.

Create coordinate component

... some interesting interplay with #24. @brandonjpierce

Thinking about edge cases:

User input: "22 33" - should we allow this as valid input and assume "22 / 33" and if LATLON "22 N / 33 E"?
User input: "11 22 33 66 55 44" - becomes "11 22 33 / 66 55 44" and if LAT LON "11 22 33 N / 66 55 44 E"?
User input "44 55" - is this valid for any system - Decimal Degrees, Degrees Decimal Minutes, or Degrees Minutes Seconds - if we allow omitted values to default to "0"?

DD = "44 / 55" and if LATLON "44 N / 55 E"
DDM = "44 0 / 55 0" and if LATLON "44 0 N / 55 0 E"
DMS = "44 0 0 / 55 0 0" and if LATLON "44 0 0 N / 55 0 0 E"

User input "N 1 2 3 4 5"

DD = invalid because too many numbers
DDM = invalid because too many number
DMS - invalid because too few numbers: options are "1 2 3 N / 4 5 0 E" or "1 2 N / 3 4 5 E"

User input "1 2 3 N 4 5"

DD = invalid
DDM = invalid
DMS = invalid: options are "1 2 3 N / 4 5 0 E" or "1 2 3 E / 4 5 0 N"

There is a difference between the user having missed a keystroke and not being done entering a value. Either way, do we want to return a positive result when there is ambiguity in the input?


feat: create new test acc

Try out this version of the Leather — download extension builds.

See title

Going to link a Code Health issue I made for this awhile ago, thx!


Crashes after C-c on stagnated ros::roseus

Describe the bug
Emacs crashes
To Reproduce
without a proper master:

(robot-init)
C-c C-c

Log *slime-events*
(:emacs-rex
 (swank-repl:listener-eval "(baxter-init)\n")
 "USER" :repl-thread 44)
(:write-string "^[[31m[ERROR] [1650021924.495021658]: [registerPublisher] Failed to contact master at [localhost:11311].  Retrying...^[[\
0m\n")
(:emacs-interrupt :repl-thread)
(:emacs-rex
 (swank:set-package "")
 "USER" :repl-thread 45)

Log *inferior-lisp*
[DEBUG - protocol:L69] Processing id: 44 ...
[INFO - protocol:L71] func: swank_repl_listener_eval
[INFO - protocol:L72] args: [u'(baxter-init)\n']
[DEBUG - handler:L216] Acquiring lock: <thread.lock object at 0x7f996c698590>
[INFO - bridge:L371] eval: (baxter-init)

[DEBUG - server:L45] output: [ERROR] [1650021924.495021658]: [registerPublisher] Failed to contact master at [localhost:11311].  Retrying...

[DEBUG - server:L80] raw header: 000020
[DEBUG - server:L87] raw data: (:emacs-interrupt :repl-thread)

[INFO - protocol:L71] func: _emacs_interrupt
[INFO - protocol:L72] args: [Symbol(u':repl-thread')]
[DEBUG - server:L80] raw header: 00003b
[DEBUG - server:L87] raw data: (:emacs-rex (swank:set-package "") "USER" :repl-thread 45)

[DEBUG - protocol:L69] Processing id: 45 ...
[INFO - protocol:L71] func: swank_set_package
[INFO - protocol:L72] args: [u'']
[DEBUG - handler:L611] Acquiring lock: <thread.lock object at 0x7f996c698590>

Process inferior-lisp terminated

Why it crashes:

While ros::roseus is trying to connect with the master, the eus node is not responsive to C-c interruptions. This is because the eus sigint handler will only set a flag on C-c, and then activate the new prompt on calls to breakck. In time-extensive operations we would usually set a smaller timeout, and loop for trials and breakcks. However, ros::init doesn't appear to have a timeout option. A solution for this would be to register separate sigint handlers during and after the master connection, but I am not sure if the ability to interrupt a ros::roseus call is worth the changes.
https://github.com/jsk-ros-pkg/jsk_roseus/blob/master/roseus/roseus.cpp#L655
http://wiki.ros.org/roscpp/Overview/Initialization and Shutdown

Meanwhile, the emacs client in euslime sends an sigint to the euslisp process and assumes that the process is responsive. Trying to evaluate another request during this time will force the emacs buffer into waiting a response from the euslisp process, which in this case won't come until successfully connected to the master. Thus, leading to a crash.

I'll take a look if there is a way for the emacs client to assert if the console is responsive or not before sending requests.

I have added a 0.5s timeout to interruption requests in https://github.com/jsk-ros-pkg/euslime/commit/8098612ad8ed8e7abca4375a247f1b4de88fa357
This way the emacs window will not crash even if the emacs process is not responsive.


Issue292 pjg addzonalmean

work in progress but currently functional

@gleckler1 great this is looking ALOT cleaner..

@doutriaux1 This pull request - maybe after major repair - needs to be merged in time for V1.1

@gleckler1 tiny tweaks please review and let me know if that's ok with you.

@doutriaux1 I'll give it a test run and get back to you shortly.

@doutriaux1 I went to branch did a pull, so some changes come down... when I ran a test I don't see the zonal mean (and departure results) and more but the following was inadvertently appended to the json:
"METRICS": {
"rms_xyt": {
"Abstract": "Compute Spatial and Temporal Root Mean Square",
"Contact": "Peter Gleckler<EMAIL_ADDRESS>"Name": "Spatio-Temporal Root Mean Square",
"URI": "http://uvcdat.llnl.gov/documentation/utilities/utilities-2.html"
},
"rms_xy": {
"Abstract": "Compute Spatial Root Mean Square",
"Contact": "Peter Gleckler<EMAIL_ADDRESS>"Name": "Spatial Root Mean Square",
"URI": "http://uvcdat.llnl.gov/documentation/utilities/utilities-2.html"
},
"bias_xy": {
"Abstract": "Compute Full Average of Model - Observation",
"Contact": "Peter Gleckler<EMAIL_ADDRESS>"Name": "Bias"
},
"mae_xy": {
"Abstract": "Compute Full Average of Absolute Difference Between Model And Observation",
"Contact": "Peter Gleckler<EMAIL_ADDRESS>"Name": "Mean Absolute Error"
},
"cor_xyt": {
"Abstract": "Compute Spatio-Temporal Correlation",
"Contact": "Peter Gleckler<EMAIL_ADDRESS>"Name": "Spatial and Temporal Correlation",
"URI": "http://uvcdat.llnl.gov/documentation/utilities/utilities-2.html"
},
"cor_xy": {
"Abstract": "Compute Spatial Correlation",
"Contact": "Peter Gleckler<EMAIL_ADDRESS>"Name": "Spatial Correlation",
"URI": "http://uvcdat.llnl.gov/documentation/utilities/utilities-2.html"
},
"seasonal_mean": {
"Abstract": "Compute Seasonal Mean",
"Contact": "Peter Gleckler<EMAIL_ADDRESS>"Name": "Seasonal Mean",
"Comments": "Assumes input are 12 months climatology"
},
"annual_mean": {
"Abstract": "Compute Annual Mean",
"Contact": "Peter Gleckler<EMAIL_ADDRESS>"Name": "Annual Mean",
"Comments": "Assumes input are 12 months climatology",
"URI": "http://uvcdat.llnl.gov/documentation/utilities/utilities-2.html"
}

@doutriaux1 my bad... its working

@gleckler1 I did run locally here's my diff and it shows only the new stuff that this branch adds.
Remember @jservonnat asked for the metrics description to be always added so your extra bits are normal.


Replace parallelization_level with more structured options of what to run

Just a dump of the meeting notes, for now:
Tasks which produce metadata will write a more structured list, e.g.
B03/cycle1, well=B03, image_name=cycle1, *
B03/cycle2, well=B03, image_name=cycle2, *

Or
B03/cycle1/{relative_path_to_MIP}, well=B03, image_name=cycle1, relative_path_to_MIP

This gives access to the following component lists

All current raw data
A subset of them, e.g.
A single well
A single cycle for all wells
A single cycle for a given well
All 2D projections
A subset of them, like above

NOTE: how to handle registration? The input would be the cycle that you want to register, and the task would take a reference_cycle parameter (which will be searched for in a standard path, i.e. “../reference_cycle”).

image_name

Is this the name of the folder in the well? e.g. 0 for plate_name.zarr/B/03/0?

reference_cycle parameter (which will be searched for in a standard path, i.e. “../reference_cycle”)

To give an example here:
We have a task with 3 cycles:
B03/cycle1,
B03/cycle2,
B03/cycle3,
The task would run separately for cycle 2 & cycle 3 (cycle 1 is a trivial registration to itself):
To run cycle 2, it gets the parameters to run on B03/cycle2 and the reference cycle B03/cycle1.
Path-wise, it could look like this:
Current component: plate_name.zarr/B/03/1
reference_cycle component: plate_name.zarr/B/03/0
Or maybe it's always relative to the well folder, i.e. the info is just 0? Not sure. That would enable i.e. just saying the reference cycle is 0, then it works for 2D and 3D data, because it's relative to the component that the tasks gets (i.e. path for cycle2)

My core idea is to split the selection of what is run into 3 categories:

“Parallelization level”: Selection of whole plate vs. individual images at a time. Or new also selection for Dimensionality, registered vs. raw, Illumination corrected vs raw => different representations of the data that never need to be processed together. Typically, the new representation is the result of processing the raw data
Component lists: A list for each parallelization level. Used for collection of OME-Zarrs, e.g. acquisitions, wells => different subsets of the dataset.
Subset of Zarrs: Subset selection of Zarrs are defined as task parameters. E.g. which ROI to loop over, which time point to process, which channel to load

TBD to specify this in more details (nested component list vs. arbitrary names of component lists, how tasks know when to switch to a different parallelization level / subset thereof.
See here for long-form brainstorming on the relevant component structure: https://docs.google.com/document/d/1J4-_HYbbaUdk6Wop0J7_hpGPX_QV4I8odzQeJfUNmuk/edit#heading=h.ji31nheqz584


Overfitting when training on Cityscapes

I wonder about the overfitting problem when training on Cityscapes and why it happened. How can I solve this problem? Thanks!

I met the same problem! Did you fix it?

Same problem here, anybody figure out why?

I met the same problem! Does anybody figure out why?


Ideal short read coverage to use for correction of Nanopore

I am wondering what would be the recommended coverage of illumina paired-end short read to use for correction. In my case I have ~270x short read coverage of the genome I am intending to assemble de novo. I would guess that this is too high cov to use, so I can split it into smaller cov values, but:

I am not sure what cov value would be the best for fmlrc2
And what parameter optimization would be needed for the chosen cov value (if other than default), specially on the -m and -f parameters.
I would be grateful to have your suggestions. Thanks.

This is a complicated question that doesn't have an exact answer.  For the first bullet, there is no theoretical limit on the coverage, but it can influence how you decide -m and -f (see below).  When we were working with E. coli, the coverage was quite high (~1000x IIRC) and it was not an issue.  We've also done some limited testing with lower coverage human data (~30x) and it was working fine there also.
For the second bullet, I can think of a handful of things that will influence the answer:

The error rates of your short reads (probably ~1%)
The ploidy (or mixture, if multi-organism like microbiome) of your data
How sensitive you want to be to low-frequency variant
The coverage of the short read dataset

Given answers to those questions, you have two levers to pull in fmlrc2 (which you already pointed out):

-m - this will change the absolute minimum count that is considered "solid" or real (default: 5)
-f - this will change the dynamic fraction minimum count that is considered "solid" or real (default: 0.1, i.e. 10%)

So for example, if you have 270x coverage short reads with a 1% error rate, a diploid organism, and you are planning to ignore low-frequency variation (i.e. de novo/mosaic variants); then on average, you're going to have 2.7x error bases per variant.  This is below the absolute default of -m=5x, and well below the expected fractional of -f = 270*0.1 = 27x, so you likely would not need to change any of the default parameters.
If you know the error rate is higher OR there is some contaminant in your data you want to ignore OR you don't care about the diploid nature of your data, then you might consider raising those criteria to higher levels.  This will basically create a stricter correction, and some may even call this an "overcorrection" in some ways.  However, it will likely run faster (i.e. less CPU time due to fewer paths to explore) and be easier to assemble downstream due to higher consistency.
On the other hand, if you want to be very sensitive to low level variation OR if you're working with microbiome data, you might consider lowering the criteria so you don't accidentally correct true variant.  I would not recommend going below -m 3 though or lowering -f to be too close to your short-read error rate as this may lead to underperformance both in the result and in run-time.
Does that help?  Sorry for the wall of text, but it's all very data and use-case dependent.

This is a complicated question that doesn't have an exact answer.  For the first bullet, there is no theoretical limit on the coverage, but it can influence how you decide -m and -f (see below).  When we were working with E. coli, the coverage was quite high (~1000x IIRC) and it was not an issue.  We've also done some limited testing with lower coverage human data (~30x) and it was working fine there also.
For the second bullet, I can think of a handful of things that will influence the answer:

The error rates of your short reads (probably ~1%)
The ploidy (or mixture, if multi-organism like microbiome) of your data
How sensitive you want to be to low-frequency variant
The coverage of the short read dataset

Given answers to those questions, you have two levers to pull in fmlrc2 (which you already pointed out):

-m - this will change the absolute minimum count that is considered "solid" or real (default: 5)
-f - this will change the dynamic fraction minimum count that is considered "solid" or real (default: 0.1, i.e. 10%)

So for example, if you have 270x coverage short reads with a 1% error rate, a diploid organism, and you are planning to ignore low-frequency variation (i.e. de novo/mosaic variants); then on average, you're going to have 2.7x error bases per variant.  This is below the absolute default of -m=5x, and well below the expected fractional of -f = 270*0.1 = 27x, so you likely would not need to change any of the default parameters.
If you know the error rate is higher OR there is some contaminant in your data you want to ignore OR you don't care about the diploid nature of your data, then you might consider raising those criteria to higher levels.  This will basically create a stricter correction, and some may even call this an "overcorrection" in some ways.  However, it will likely run faster (i.e. less CPU time due to fewer paths to explore) and be easier to assemble downstream due to higher consistency.
On the other hand, if you want to be very sensitive to low level variation OR if you're working with microbiome data, you might consider lowering the criteria so you don't accidentally correct true variant.  I would not recommend going below -m 3 though or lowering -f to be too close to your short-read error rate as this may lead to underperformance both in the result and in run-time.
Does that help?  Sorry for the wall of text, but it's all very data and use-case dependent.

It definitely helps! Thanks for the detailed explanation. It is clear.
One other detail is if it is possible to use only the R2 of a paired-end short read data for correction? My R2 sequence I believe is reverse complemented. Would this create a problem for the fmlrc2 process?
I'd like to use only R2 reads because in my case R2 is 150 bp long, whereas my R1 is 125 bp long, and since I have plenty of coverage I'd like to use only the longest short reads for correction (R2) in the hope that this would benefit the correction process, but I am not sure if this is actually true. So if I use R2 only I would end up with 135x coverage and likely default parameters would still be safe (my genome is diploid and planning to ignore low-frequency variation) Thanks!

It definitely helps! Thanks for the detailed explanation. It is clear.
One other detail is if it is possible to use only the R2 of a paired-end short read data for correction? My R2 sequence I believe is reverse complemented. Would this create a problem for the fmlrc2 process?
I'd like to use only R2 reads because in my case R2 is 150 bp long, whereas my R1 is 125 bp long, and since I have plenty of coverage I'd like to use only the longest short reads for correction (R2) in the hope that this would benefit the correction process, but I am not sure if this is actually true. So if I use R2 only I would end up with 135x coverage and likely default parameters would still be safe (my genome is diploid and planning to ignore low-frequency variation) Thanks!

So the entire reads are loaded into the BWT, and assuming they are in separate files (i.e. r1 and r2 files), you could just create a BWT with one end of the pair instead of both.
However, fmlrc only performs queries on k-mers (i.e. substrings) of the reads at lengths 21 and 59 by default, and it is smart enough to look for the k-mer and it's reverse complement when performing the query.  Since those k-mer lengths are quite a bit smaller than your 125 r1 reads, you will likely only hurt the performance by removing them.  Not only would you be losing information from your sequencing, but it's possible you may be injecting a strand bias by removing one end of the reads.
Of course, if compute isn't a major issue, you could always just try it both ways and see how it works out.

So the entire reads are loaded into the BWT, and assuming they are in separate files (i.e. r1 and r2 files), you could just create a BWT with one end of the pair instead of both.
However, fmlrc only performs queries on k-mers (i.e. substrings) of the reads at lengths 21 and 59 by default, and it is smart enough to look for the k-mer and it's reverse complement when performing the query.  Since those k-mer lengths are quite a bit smaller than your 125 r1 reads, you will likely only hurt the performance by removing them.  Not only would you be losing information from your sequencing, but it's possible you may be injecting a strand bias by removing one end of the reads.
Of course, if compute isn't a major issue, you could always just try it both ways and see how it works out.

I'm glad to know this. I will definitely use both pairs of my reads, I would not like any possibility of strand bias on my long reads. There seems to be no reason to use fewer reads and miss sequence information.
I noticed that Fmlrc2 allows 3-pass correction (e.g. k-mers 21, 59, 79), do you think it would be a good idea to add 79 to the default 21 and 59 k-mers to my correction job? What is the argument to add '21,59,79'? I tried various argument combinations by it did not work, either the job stops as 'argument wasn't expected' or only the default (21,59) was recognized. Thanks.

I'm glad to know this. I will definitely use both pairs of my reads, I would not like any possibility of strand bias on my long reads. There seems to be no reason to use fewer reads and miss sequence information.
I noticed that Fmlrc2 allows 3-pass correction (e.g. k-mers 21, 59, 79), do you think it would be a good idea to add 79 to the default 21 and 59 k-mers to my correction job? What is the argument to add '21,59,79'? I tried various argument combinations by it did not work, either the job stops as 'argument wasn't expected' or only the default (21,59) was recognized. Thanks.

To do the multiple k-mer sizes, you just include each one with a space in between like this:
fmlrc2 -k 21 59 79 ...

As for the practicality of a third pass, we don't really know.  That's also something that may be worth testing, but that I don't have any evidence for or against.
Theoretically, longer k-mers will increase the accuracy of the correction by allowing you to find more unique anchors (this was shown with the second pass at 59).  However, as your k-mer gets longer, you will lose evidence because either the k-mer is only partially in a read or you have a sequencing error, and at a certain point there will be no benefit to larger k-mers because of that loss.

To do the multiple k-mer sizes, you just include each one with a space in between like this:
fmlrc2 -k 21 59 79 ...

As for the practicality of a third pass, we don't really know.  That's also something that may be worth testing, but that I don't have any evidence for or against.
Theoretically, longer k-mers will increase the accuracy of the correction by allowing you to find more unique anchors (this was shown with the second pass at 59).  However, as your k-mer gets longer, you will lose evidence because either the k-mer is only partially in a read or you have a sequencing error, and at a certain point there will be no benefit to larger k-mers because of that loss.

It is very useful to know this information. Since various topics were covered in this issue I edited its title to reflect more accurately the Q/A addressed here, so that other users can see it too.
Finally and as a general outline about correction of Nanopore data, in the fmlrc paper it was mentioned that "Our method is applicable to both Pacbio SMRT sequencing and nanopore sequencing datasets, however further parameter optimization may improve its accuracy and efficiency for nanopore sequences, which exhibit a slightly different error profile than Pacbio." So I am wondering what would be those parameters/optimization that may improve Nanopore accuracy? and how accurate/efficient is fmlrc2 at correcting Nanopore vs PacBio data? Thanks so much for your help! Every answer was very valuable.

It is very useful to know this information. Since various topics were covered in this issue I edited its title to reflect more accurately the Q/A addressed here, so that other users can see it too.
Finally and as a general outline about correction of Nanopore data, in the fmlrc paper it was mentioned that "Our method is applicable to both Pacbio SMRT sequencing and nanopore sequencing datasets, however further parameter optimization may improve its accuracy and efficiency for nanopore sequences, which exhibit a slightly different error profile than Pacbio." So I am wondering what would be those parameters/optimization that may improve Nanopore accuracy? and how accurate/efficient is fmlrc2 at correcting Nanopore vs PacBio data? Thanks so much for your help! Every answer was very valuable.

We have done some limited testing on Nanopore data, mostly for the purpose of verifying that there wasn't some strange compatibility issue and that we were getting results that made sense.  IIRC, all of the paper analysis was PacBio.
As far as CLI parameters, the main things are based on the error rates.  The PacBio CLR we originally tested with had ~10-15% error rate I believe, but I'm not sure what it is for recent Nanopore sequencing.  If your error rate was higher, you would want to use smaller k-mers, especially for the first pass so you can actually get some anchors to the sequence.  Whereas with a lower error rate, you can make your k-mers larger because there's a higher chance of hitting them.  I believe in recent benchmarks (such as this one or this other one), they just used the default settings of fmlrc without any specific tuning.
Most of the tuning that I think would be most relevant are really new features that aren't even implemented in either fmlrc or fmlrc2.  This would include things like a custom error model (i.e. PacBio has higher indel than mismatch rate), a different anchoring strategy depending on the inputs, etc.

We have done some limited testing on Nanopore data, mostly for the purpose of verifying that there wasn't some strange compatibility issue and that we were getting results that made sense.  IIRC, all of the paper analysis was PacBio.
As far as CLI parameters, the main things are based on the error rates.  The PacBio CLR we originally tested with had ~10-15% error rate I believe, but I'm not sure what it is for recent Nanopore sequencing.  If your error rate was higher, you would want to use smaller k-mers, especially for the first pass so you can actually get some anchors to the sequence.  Whereas with a lower error rate, you can make your k-mers larger because there's a higher chance of hitting them.  I believe in recent benchmarks (such as this one or this other one), they just used the default settings of fmlrc without any specific tuning.
Most of the tuning that I think would be most relevant are really new features that aren't even implemented in either fmlrc or fmlrc2.  This would include things like a custom error model (i.e. PacBio has higher indel than mismatch rate), a different anchoring strategy depending on the inputs, etc.

Great! In the benchmark papers Fmlrc2 performs very well for correction of Nanopore data with short reads.
With the new improvements introduced to the Nanopore basecaller starting in Guppy 3.6.0, the accuracy increased between 1 - 2% over previous versions. So I don't think the error rate of my Nanopore data is higher than ~10-15% and probably just the default settings are very suitable in my case. Thanks.

Great! In the benchmark papers Fmlrc2 performs very well for correction of Nanopore data with short reads.
With the new improvements introduced to the Nanopore basecaller starting in Guppy 3.6.0, the accuracy increased between 1 - 2% over previous versions. So I don't think the error rate of my Nanopore data is higher than ~10-15% and probably just the default settings are very suitable in my case. Thanks.

Yep, I'm going to close this for now, but if you have other questions, feel free to re-open it.  Thanks for using fmlrc!

Yep, I'm going to close this for now, but if you have other questions, feel free to re-open it.  Thanks for using fmlrc!


test - error on some systems with test import

the following error occurs reproducibly on test system, not on prod system:
TASK [test : make test import] *******************************************************************************************************************************************************
fatal: [fworch-srv]: FAILED! => changed=true
  cmd:
  - ./fworch-importer-single.pl
  - mgm_name=fortigate_test_khwkWdjlejojoRFRvlHYfKeCMRHRXXFn
  delta: '0:00:00.185500'
  end: '2022-02-08 08:45:54.705122'
  msg: non-zero return code
  rc: 2
  start: '2022-02-08 08:45:54.519622'
  stderr: |-
    DBD::Pg::st execute failed: ERROR:  duplicate key value violates unique constraint "import_control_only_one_null_stop_time_per_mgm_when_null"
    DETAIL:  Key (mgm_id)=(70) already exists. at CACTUS/FWORCH/import.pm line 342.
    DBD::Pg::st execute failed: ERROR:  current transaction is aborted, commands ignored until end of transaction block at CACTUS/FWORCH/import.pm line 345.
    DBD::Pg::st fetchrow failed: no statement executing at CACTUS/FWORCH/import.pm line 346.
    Use of uninitialized value $current_import_id in concatenation (.) or string at ./fworch-importer-single.pl line 100.
  stderr_lines: <omitted>
  stdout: |-
    version: 5ff, manufacturer: fortinet, current_import_id=ERR-set-import-lock-failed
    WARN-import-already-running: fortigate_test_khwkWdjlejojoRFRvlHYfKeCMRHRXXFn (ID: 70)
  stdout_lines: <omitted>

both systems at a customer's are now affected

fixed by #1620

unfortunately the "TimeoutStopSec=300min" setting did not fix this error, we still get the same error message.
The wait for import to stop works though.

Closed with #1628


MH-12868: Make frame-by-frame skipping function in the editor use the "actual" framerate

This makes the admin UI tools endpoint return the framerate of the preview videos used for editing and previewing. This is then in turn used by the frontend to make the left and right key actually skip the correct amount of time (= 1 / framerate).
The assumption here is, of course, that the preview video has the same framerate as the end product. Otherwise, a skip of 1 / preview_fps is meaningless.
Note also that seeking 1 / fps seconds is kind of a hack, but there is currently no standard (also also not really any non-standard, barring this) way of controlling a video element in a frame-precise manner.

A patch like this shouldn't go into 3.x anymore, should it?

I could see the argument that the scrubber is inaccurate, therefore this is a bug fix.  But I'd feel more comfortable punting this into 5.x or develop so that more eyes see it.  4.x if we have to, but 5.x is where QA is going to be focused.

@lkiesow I wasn't sure, but my thinking was along the lines of what @gregorydlogan said. I have no strong opinion on this, though; will retarget today. :smiley:

Done, btw. Just in case GitHub does not notify in the case of a redirect and/or push.
I can never remember what GitHub sends notifications for. :sweat_smile:

As is this dumps files in admin-ui/.tmp and admin-ui/coverage.  I also can't see to get the admin UI to work right, but then that's true regardless of whether this patch is included or not.

Fair enough, double checked and no longer see the issue.  Merged!


can't personal sign with v2, because the rpc request parameters has a nil & the index is not last

Describe the bug
can't personal sign with v2, because the rpc request parameters has a nil, and  AnyCodable will throw the error

I have 4 parameters
AnyCodable will throw when the 3rd parameter decode
I need the 4th parameter to sign

https://github.com/WalletConnect/WalletConnectSwiftV2/blob/9e4e61095ee028d4d329803d6206380dc5f77d74/Sources/Commons/AnyCodable.swift#L160
SDK Version

Client: WalletConnectSwiftV2
Version 1.6.11

To Reproduce
Steps to reproduce the behavior:

open https://app.rhino.fi/portfolio
Click on 'Connect Wallet'
Click on 'Wallet Connect'
use WalletConnectSwiftV2 scan the qr code

Expected behavior
person sign success
Screenshots

Device (please complete the following information):

Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]

Additional context
Add any other context about the problem here.

@JustLee-me sorry for long response, could you please check does issue still reproducing?


Support ignoreMethods

I want to be able to block certain request methods from being traced. For example to prevent option requests:
app.register(fastifyOpentelemetry, {
   serviceName: 'my-app',
   wrapRoutes: true,
   ignoreMethods: ['options']
})

Is something like this possible? If not could it be implemented?

That makes sense to me, thanks @JosephScript 👍
I think a little more flexibility with our ignoreRoutes option should do the trick.
I've just opened a PR(#39) which updates the ignoreRoutes option to also accept a function that receives the path and method, then returns a boolean.
So to ignore all OPTIONS routes:
app.register(fastifyOpentelemetry, {
   serviceName: 'my-app',
   wrapRoutes: true,
   ignoreRoutes: (path, method) => method === 'OPTIONS'
})


Email notifications (async microservice)

Use RabbitMQ or Azure Queue Storage to queue a message send.

A few thoughts:

notifications should be logged
create a good template system or way to plugin different providers (SendGrid, etc)
could be done in a generic way as it's own project that could be used for other systems
eventually may want to support other types of messages (SMS, FB messenger, Slack, Skype)
eventually may want to lookup user notification preferences (via User microservice?)


[Content sync]: carbon-website PR 3225

The following pull request on carbon-website has been merged. It contains .mdx content changes that may need synced to platform.

https://github.com/carbon-design-system/carbon-website/pull/3225

verfied this new content is already on PROD: https://next.carbondesignsystem.com/contributing/bugs-and-requests
no further action needed


Validation errors are returned with http status code 400 instead of 422

Technically it is not wrong to use status code 400 for validations but more specific code would be 422. At least that should be in the options. Broken syntax should return 400, invalid data 422.
"The 422 (Unprocessable Entity) status code means the server understands the content type of the request entity (hence a  415 (Unsupported Media Type) status code is inappropriate), and the syntax of the request entity is correct (thus a 400 (Bad Request) status code is inappropriate) but was unable to process the contained instructions."
https://datatracker.ietf.org/doc/html/rfc4918#section-11.2
"Sending invalid fields will result in a 422 Unprocessable Entity response."
https://docs.github.com/en/rest/overview/resources-in-the-rest-api?apiVersion=2022-11-28#client-errors

I agree on that. I often use it.
I think I should an option to let the user choose whether it was 400 or 422 for validation error.
Will take care of this next week.

Absolutely brilliant!

Sorry for the delay. Released in v4.2.0


feat: set up contributions

What type of PR is this? (check all applicable)

[x] 🍕 Feature
[ ] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Description

This PR [adds/removes/fixes/replaces] the [feature/bug/etc].
Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings

Added tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[ ] 📕 storybook
[ ] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

I integrated the code from this PR into my incoming database improvement refactor, we can close this pretty soon 🍕

Think #36 superseded this as well 🚀


How to make the translucent property on the navigationbar and segmented pager to false in swit

Hi,
I am facing the following problem while using the library.
Throughout my app i have made the translucent property of the navigation bar to 'false' so that i dont get the blur effect on the navigation bar.
After integrating the library on a viewcontroller, that viewcontroller's navigationbar's translucent property is automatically set to 'true'

I am trying to make the nav bar and segment bar the same color as my header view but it seems there is a translucent property added to the MXSegmentedPagerController
Please let me know how can i change the translucent property to false

I met with same kind of problem, a translucent layer above segmented control. Solved it by changing selection indicating box's opacity to 1.0 . MXSegmentedPager.segmentedControl.selectionIndicatorBoxOpacity = 1.0;


Add the supply chain smart contract example

Adds the supply chain smart contract example (gear-tech/apps#45).

@fluiderson please run the text through Google docs to highlight grammar issues and fix it.


Add support for clipping (and EO clipping); add support for non-EO fill.

This change is

These will be tested by #1348.

:shipit:

@rajsesh-msft Addressed your feedback! I added a comment on the geometry cloning and simplified Clip() a little.


Plugin for IntelliJ IDEA

Hi, will be excellent to have a plugin for IntelliJ IDEA that will show issues in editor itself

Do you mean somehow like Python issues in Pycharm? Some of the syntax errors are detected in real time for Python. We plan something similiar - to integrate with one of the existing Robot Framework plugins for intellij.
For now you can define Robocop as external tool in Pycharm/intellij and assign shortcut for it. I have it configured with macros (like pass currently open file as argument to Robocop) if press shortcuts it will run tests on file open in the screen. I can share screenshots of configuration if you want

Hi @bhirsz
Yes, with syntax highlighting. Could you share the screenshots, thank you!

Go to File -> Settings -> Tools -> External Tools. Click + button to add new tool. Fill it out:

You can also add your own arguments (like excluding/including rules, configuring).
Advanced option and output filters are required to get clickable links in issues list.
After saving and closing settings window you can go back to settings and add new shortcut under Keymap -> External Tools
This is of course "poor man's integration with Intellij" but better than nothing ;). I'm already working on integrating with plugins that have syntax highlighting.

On side note external tools are really handy with small automation tasks in Pycharm/Intellij - I often have some python scripts that autoformat files for me or do different tasks. This is example of such tool https://github.com/bhirsz/robotframework-clean - but I did not have time to add better documentation for it. I usually have shortcut for things like 'split currently selected keyword in multilines' or 'align selected lines in column like view' to make working with RF code easier.

Hi @bhirsz
Thank you for the detailed instruction, I tried it and the second plugin, these tools are great and it will be really cool to have them integrated into IntelliJ IDEA.
With regards,
Yosef

Only one question, is there any objectives to be compatible with robot 3.0.2?

Robocop needs 3.2.1 because it is introducing new robot api - with new parsing api which we're using when analysing Robot Framework code. But you can use Robocop to analyse code code written to be compatible with previous versions (although there could be some problems).
I will keep issue open until we get better integration with Intellij IDEA

As a note, Robocop is being integrated with the Robot Framework Language Server (i.e.: https://github.com/robocorp/robotframework-lsp/issues/271), which has an integration with Intellij (https://plugins.jetbrains.com/plugin/16086-robot-framework-language-server), so, keep an eye on it (it should be integrated in the next release: 0.11.0).

Closing this issue because Robocop is already integrated to LSP through https://github.com/robocorp/robotframework-lsp and should be available in PyCharm and Visual Studio Code. Note that it's best to install most recent version of Robocop globally (and update it frequently) because LSP is shipped with old version of Robocop that don't have recent fixes.


spam

I wish to report a malfunctioning developer.
While I have full respect for the hard work that the developers put in, and I know I'm not paying for a service, but a bit of respect in communicating with users is in order. When we put in the time and effort to follow to the letter the bureaucracy required for making a bug request (and yes I understand why you want it) it is not good behaviour to dismiss us out of hand.
In this respect I wish to report a malfunctioning dirkf. Please can you see what can be done to fix the bugs in this developer. Thank you.

No sense of humour!
I see you are digging your heels in and not listening to fair feedback.  Listen to your users!

Somewhat amusing but still spam. Try this https://github.com/ytdl-org/youtube-dl/issues/31931#issuecomment-1483886289 for a laugh.


add cross-env package to avoid Node errors

Windows users can now just npm start instead of
$env:NODE_ENV="development"
npm run build
node dist/src/main.js

I added the cross-env package to package-lock and start:dev, start:cli scripts to avoid Node errors with the NODE_ENV variable.

great idea, thanks @lelemathrin !


Document how to wildcard labels in identity logic

Add documentation with the specific steps / syntax for how the --labels option can be configured.

Isn't this covered by https://docs.cilium.io/en/latest/operations/performance/scalability/identity-relevant-labels/ already?

Thanks, yes, looks like it was addressed now. The docs there look pretty clear to me about how the configuration should look in the actual config. Let's close this out :tada:


[WIP] Creates datadog manifests to replace helm chart sub chart dependency

Removes Datadog from chart.yaml
Resolves merge conflicts that previously existed in this branch which is why there are other files pushed
Creates datadog manifests for datadog agents
Packaged to semver 5.5.0

New Keys added:
datadog:
  enabled: true
  apiKey: ""
  clusterAgentToken: ""

NOTE: Extra files are included due to merge conflicts that need to be fixed. Datadog manifests are append with datadog keyword
Closes: #47

@Abhi94N let's determine first how we could remove the cluster level dependencies from our helm chart and then remove this DatadogHQ dependency altogether.


Orbot doesn’t connect - shows connecting and then back to disconnected

As per title, Orbot suddenly stopped working on my iPhone. When I press the connect button, the app shows that it is connecting for about fifteen seconds before changing back to the “disconnected” button.
Here is the log:
Jun 01 09:21:05.000 [notice] Tor <IP_ADDRESS> opening new log file.
Jun 01 09:21:05.274 [notice] We compiled with OpenSSL 101010df: OpenSSL 1.1.1m  14 Dec 2021 and we are running with OpenSSL 101010df: 1.1.1m. These two versions should be binary compatible.
Jun 01 09:21:05.284 [notice] Tor <IP_ADDRESS> running on Darwin with Libevent 2.1.12-stable, OpenSSL 1.1.1m, Zlib 1.2.11, Liblzma 5.2.5, Libzstd N/A and Unknown N/A as libc.
Jun 01 09:21:05.284 [notice] Tor can't help you if you use it wrong! Learn how to be safe at https://support.torproject.org/faq/staying-anonymous/
Jun 01 09:21:05.284 [notice] Configuration file "/private/var/mobile/Containers/Data/PluginKitPlugin/6DD9EC68-75BF-4411-B0F1-4C14AC096B88/.torrc" not present, using reasonable defaults.
Jun 01 09:21:05.288 [warn] MaxMemInQueues is set to a low value; if your client doesn't work, this may be the reason why.
Jun 01 09:21:05.292 [notice] Opening Socks listener on <IP_ADDRESS>:0
Jun 01 09:21:05.292 [notice] Socks listener listening on port 56782.
Jun 01 09:21:05.293 [notice] Opened Socks listener connection (ready) on <IP_ADDRESS>:56782
Jun 01 09:21:05.293 [notice] Opening DNS listener on <IP_ADDRESS>:0
Jun 01 09:21:05.293 [notice] DNS listener listening on port 63092.
Jun 01 09:21:05.293 [notice] Opened DNS listener connection (ready) on <IP_ADDRESS>:63092
Jun 01 09:21:05.293 [notice] Opening Control listener on <IP_ADDRESS>:0
Jun 01 09:21:05.293 [notice] Control listener listening on port 56783.
Jun 01 09:21:05.293 [notice] Opened Control listener connection (ready) on <IP_ADDRESS>:56783
Jun 01 09:21:05.000 [notice] {GENERAL} Parsing GEOIP IPv4 file /var/containers/Bundle/Application/5D84940D-1C99-4E40-9639-2FD6E4A06AF7/Orbot.app/Frameworks/Tor.framework/GeoIP.bundle/geoip.
Jun 01 09:21:05.000 [notice] {GENERAL} Parsing GEOIP IPv6 file /var/containers/Bundle/Application/5D84940D-1C99-4E40-9639-2FD6E4A06AF7/Orbot.app/Frameworks/Tor.framework/GeoIP.bundle/geoip6.
Jun 01 09:21:05.000 [notice] {CONTROL} Bootstrapped 0% (starting): Starting

It worked fine a couple weeks back when the app was initially out but since then I’ve been unable to get it working. I’m unsure whether this was before or after the update to iOS 15.5.
Currently using an iPhone XS Max running iOS 15.5 (19F77). Orbot is on version 1.2.0 build 10.
None of the settings have been changed on Orbot. I’ve tried force-closing and restarting the app. I’ve also tried deleting the VPN configuration in iOS settings and re-installing the VPN configuration.
I don’t use bridges. (But I have tried connecting with all the bridge types, which didn’t help fix the issue.)

@tladesignz thanks for the reply.

Can you tell where you're situated? Usually, I see this kind of behaviour when Tor has trouble connecting because it gets blocked, resp. parts of the Internet get blocked so it cannot find servers.

I'm currently situated in South Korea. There are no problems with Tor connectivity here.

Did you play with the node settings? That could be another reason. You might have set something which limited you to e.g. one entry node, which now is gone.

No settings have been modified. The fields for the node settings are all blank.

If nothing helps, you could try remove the app and reinstall.

That worked for some reason, thanks!

Could you share the log when trying bridges? Or does that look exactly the same?

Pretty much the same if I remember correctly; it also stops with the following line at the end:
{CONTROL} Bootstrapped 0% (starting): Starting

Since I cannot reproduce the issue anymore after re-installing, I'll close the issue now. Will re-open in the future if it happens again. Thanks!

Thank you for the feedback. I have to say: I'm stumped. No idea what could cause this. Maybe Tor can manoeuvre itself in a situation where it breaks its cached circuit "microdescriptors" configuration in a way, that it can't start again or something similar?
I'll keep an eye out for it. Maybe this happens to me sometimes. Or maybe it is gone with the new version.
However, on a quick scan since version <IP_ADDRESS>, I couldn't find anything related:
https://gitlab.torproject.org/tpo/core/tor/-/raw/release-0.4.7/ReleaseNotes

I’ve tried all the bridge options (including requesting one from Tor Project), quit and restarted the app, removed and re-added the VPN configuration from iOS settings, and tried starting the VPN with the switch in iOS settings rather than using the Orbot on button. All of them fail with the logs matching above.
The only thing I haven’t tried is reinstall the app, because I’m pretty sure that will fix it, but then I won’t be able to reproduce the issue until it occurs again and it’s rather cumbersome to reinstall every time this problem occurs.

On Android there seems to be a similar thing.
Orbot is connected but has no data exchange or the viewer does not correctly display the amount of transmissions. There also seems to be Snowflake routing disabling on its own sometimes.
Suggestion: also send logs manually, as in Waze and Netmonster and that the exchange of data is also accounted for when we help another user on Snowflake.

@tladesignz is that what the problem is, the Orbot app (or some sort of extension within it) running out of memory and quitting early?
Two things I can think of: maybe a memory “usage” screen that shows currently used memory so that users can tell why the problem is occurring, as well as an entry in the log if the app (and/or the extension) was killed by the iOS system because it hit against the memory limit? Also the reset cache button you mentioned sounds great as well. But the first two will at least let users figure out what is going wrong instead of just silently dying.
I’ve had the app kill the connection in the background – I noticed the VPN indicator did not show anymore and when I came back to the app it was disabled. Could be very dangerous for some users where Tor needs to stay on for privacy reasons.

@tladesignz is that what the problem is, the Orbot app (or some sort of extension within it) running out of memory and quitting early?

The "Network Extension", which contains Tor running in the background.
It's just a shot in the dark.

Two things I can think of: maybe a memory “usage” screen that shows currently used memory so that users can tell why the problem is occurring, as well as an entry in the log if the app (and/or the extension) was killed by the iOS system because it hit against the memory limit? Also the reset cache button you mentioned sounds great as well. But the first two will at least let users figure out what is going wrong instead of just silently dying.

Yeah, would be nice to have, but we can't measure that. iOS security restrictions.

I’ve had the app kill the connection in the background – I noticed the VPN indicator did not show anymore and when I came back to the app it was disabled. Could be very dangerous for some users where Tor needs to stay on for privacy reasons.

Yes, unfortunately Network Extensions fail open and we can't do much about it automatically.
There is a flag in Settings -> VPN -> Orbot -> Connect on demand
Check that, on the Extension will be restarted automatically.
Not found a way to provide that from within the app and/or automatically set it. 🤷 Sorry.

I added that "clear cache" button I was thinking about, and I also revisited the whole "connect on demand" thing. I actually recognized, that thinking this would be beyond our control was actually an old memory which wasn't completely informed.
I was able to leverage it and create a "reconnect on error" feature. Which uses the "connect on demand" feature of the system but disables that again automatically, after the user purposefully stopped Tor again. Seems way more useful this way, and definitely easier to discover for unwitting users.
I hope this will help your situation. I'll close this for now. Please join the TestFlight, if you need this soon: https://orbot.app/download

Fails to connect.
Bridges I’m using are the ones from the telegeam bot.
Connect on Demand is ON.
The connection percentage goes up to ~60-70% and  then stops and disconnects. So at the end of the day I have made zero successful connections.
nothing helps. Please advise.
location: Australia


Documentation pleassssse

### Documentation pleassssse

@mbaumgartenbr  is there any documentation provided please ? I like the package but It lack s the doc it'd be helpful if you provided us wit some simple concrete code on how to use the package with a list of data

Hey @talbiislam96! Sorry for the inconvenience.
I'm actively working on version 1.0 of the package and the API changed drastically. Due to this change I decided to not write documentation for the current version and instead focus on a rich documentation for the next one.
The plan is to have a nice and easy to follow guide in README. And I'm also working on simpler examples instead of relying on the demo.
The new API is very close to done and the only thing left after that is the readme and then the release of a dev version.
Since there's many different ways of representing a tree, I won't be able to cover everything, therefore, once the new version is out, I'd be open to answering the "How to use the package with foo data model?" question, feel free to open question issues then.


v0.3.4

requesting bond angle for nonexistent bond(s) raises error instead of NaN
bond angle calculation no longer uses rounding to avoid numerical precision errors
symmetry rules bug fix
primitive cell temporary file bug fix

closes #93
closes #94
closes #95

Codecov Report

Merging #96 (61b14bb) into master (dbb688e) will increase coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #96      +/-   ##
==========================================
+ Coverage   95.92%   95.94%   +0.02%
==========================================
  Files           9        9
  Lines         981      987       +6
==========================================
+ Hits          941      947       +6
  Misses         40       40

Impacted Files
Coverage Δ

src/bonds.jl
96.71% <100.00%> (+0.06%)
:arrow_up:

src/crystal.jl
95.11% <100.00%> (+0.02%)
:arrow_up:

Continue to review full report at Codecov.

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