Feature request: allow to connect to wallets with Bluetooth API

Hi,
Anton, the developer of https://lightning-wallet.com/ said he is interested in implement bluetooth API.
If he really add it, I think Lightningjoule could allow to comunicate with it.
Interesting article about Bluetooth API: https://medium.com/@urish/start-building-with-web-bluetooth-and-progressive-web-apps-6534835959a6

This too: https://developers.google.com/web/updates/2015/07/interact-with-ble-devices-on-the-web?hl=en

More interesting links: https://plus.google.com/u/0/communities/108953318610326025178

I'm not sure there's much I can do on this front until one of the apps adds this functionality. Is there any form of standard around this?

BLW wallet is starting the work to enable bluetooth: https://github.com/btcontract/lnwallet/commit/de6417bc7247f4425810e49d6c4709d27a722995

Hey there, yeah I think this is an interesting idea and currently I work on implementing Bluetooth basics on BLW side.
How I imagine this would work so far:

User enables "Bluetooth payments" option in BLW settings and chooses a device in a list of paired devices (optionally choosing will happen later if needed device is not yet paired).
BLW warns user that chosen device will be able to issue automatic payments and remembers it if user proceeds. From now on BLW will only be trying to establish a Bluetooth connection with an approved device. This removes the need for macaroon authorization since network communication is local and also BLW is not password protected so paying can be very straightforward.
Once connection is established BLW will be sending stats to Joule (channel details, balance, etc) and listening for deposit/withdraw messages from Joule. I guess the messaging format can be copied from what is currently used to communicate with LND.

Does this look fine so far?

That all makes sense, and I think sticking as closely to LND as possible will make for the best developer experience. However, I'm still a little unsure as to how an app on the phone communicates over the device's bluetooth connection. The phone can only connect as one bluetooth "device", so how would I go about specifically communicating with your app on the device? It looks like there're GATT services that provide characteristics to read and write to, but it looks like a typical request -> response architecture is going to be a little tricky.
I have no experience with the Web Bluetooth API so I can't provide a ton of input on how this would look.

However, I'm still a little unsure as to how an app on the phone communicates over the device's bluetooth connection.

Same here. My plan is, once mobile side is done, to fork Joule and try things out until messaging works. I assume browser extension should at least be able to access Web Bluetooth API (https://developer.mozilla.org/en-US/docs/Web/API/Web_Bluetooth_API) like websites do?

Yep, they most certainly can! That sounds like a good path forward. Don't hesitate to hit me up with any questions you have during that process.


scdoc text files are incorrectly rendered as SuperCollider instead of Markdown

Preliminary Steps
Please confirm you have...

[x] reviewed How Linguist Works,
[x] reviewed the Troubleshooting docs,
[x] considered implementing an override,
[x] verified an issue has not already been logged for your issue (linguist issues).

Problem Description
scdoc is a project very similar to ronn, with the main difference being that it's written as a small C program instead of Ruby. They both use slight variants of Markdown to write man pages, allowing them to be easy to read and write directly.
Since Ronn is already detected as Markdown by linguist, those files render well. For example, see ronn.1.ronn rendered nicely.
Unfortunately, this is not the case for scdoc files, which have the extension .scd, already taken by SuperCollider. As such, they render very poorly; for example, see sway.5.scd.
I realise that the .scd extension is already taken or at best ambiguous, so I'm not asking to break that.
I also realise that projects could use gitattributes overrides, and that's better than nothing as a temporary workaround, but I still think it would be nice to support scdoc nicely given that it's extremely similar to ronn.
So here's my suggestion: since scdoc man pages always match the regular expression [a-z]+\.[0-9]\.scd, we could simply add the extensions .1.scd through .9.scd to the list of extensions matching Markdown. This should be doable as long as linguist is smart enough to attempt to match longer extensions before shorter ones, so that foo.1.scd matches Markdown and foo.scd matches SuperCollider.
URL of the affected repository:
https://github.com/swaywm/sway/blob/master/sway/sway.5.scd
Last modified on:
2020-08-03
Expected language:
Markdown
Detected language:
SuperCollider

I tried *.*.scd linguist-language=Markdown and it kind of works as a temporary workaround, since the syntax highlighting now follows Markdown. But my file is still not being rendered like .md and .ronn files: https://github.com/mvdan/sh/blob/f1d7185c4d02528db7c2f0290e9356a1c5503683/cmd/shfmt/shfmt.1.scd

The rendering of .md and .ronn files isn't done by Linguist and Linguist doesn't have much influence over that beyond identifying the language. The actual rendering is done by the code in https://github.com/github/markup/.
If you want syntax highlighting, support would need to be added to Linguist - please feel free to submit a PR.
If you want actual rendering, then you'll need to add support to or open an issue in https://github.com/github/markup/, though keep in mind, development in that library has slowed quite considerably over the years.

Thank you, I wasn't aware that language detection and language rendering were separate. Proper rendering is less important than fixing the highlighting I think, so we could fix linguist first and that would already be a big win.
Does my idea above about adding the extensions .1.scd through .9.scd sound good? Will linguist's extension matcher work with such extensions which should be checked before .scd?

I had a quick look at this but I'm afraid that Ruby and the Bayesian classifier steps in CONTRIBUTING.md make this look like a few hours of work rather than a simple PR.

SCDoc and SuperCollider have very different syntax so Linguist should be able to differentiate them without a heuristic. I'll issue a PR to see if it works properly.

Added in #5198, can be closed.

"this week" #5197

(Requesting closure of this issue)

I'll close this issue when the file above renders properly, if that's okay. If it's been two weeks and the rendering is still wrong, I'll assume that the issue should remain open.

That file now renders properly with the release of 7.13

It does, thank you!


Resolve #95 - Update Oghliner app content

This is just a start, will be building upon this.

This is ready for preliminary review.  I need to figure out a way to get rid of the buttons though.

I like the idea of reusing the README (idea that made me remember that we need to keep the README updated, filed #153).
I also like the result. I'd only add a bit more space between the sections (e.g. before "Using The Template").

I also think the information could be reorganized a little in the README, to make it simpler to read.

Updates made to separate sections and update code style.

Last remaining issue:

I tried white-space: pre-line but we were still getting overflow so the best solution is hiding overflow so code/commands look the same and we never see screen stretching.

Can we use overflow: auto so the scrollbars are only shown if needed?

/me facepalms
Of course, sorry.  No more early morning PRs from me

:smile:


What is the license of this repository?

What is the license of this repository, please?
Thank you.

What is the license of this repository, please?
Thank you.

MIT + Apache-2.0 — I just added the license text, thanks for pointing out they were missing!


Raise max TCP segment queue length

Out-of-order TCP segments are queued in the reassembly queue until the missing in-sequence segments arrive.  As a DoS mitigation, the length of this queue is limited, with a default of 100.  Since TCP allows a whole window to be in-flight at once, there can be up to 1448 to 11586 segments arriving before the sender expects an ACK, depending on the configured max receive buffer size and negotiated window size.  The limit of 100 is not usually an issue in wired networks, because segments seldom arrive out of order.  However, reordering and/or losses are more frequent with wireless networks and more complex networks, so the low default limit can cause a lot of segments to be discarded.
Raise the limit to 1448, which allows a full window to be queued in the default configuration.
See following ticket: https://redmine.ixsystems.com/issues/43558

Thanks for sending that in!


Remove babel-eslint from .eslintrc for yeoman

A leftover

Good catch! Thanks for the PR. Restarting Travis now cuz it failed. Will merge once that passes.


[Test] Remove junit

Signed-off-by: Zixuan Liu<EMAIL_ADDRESS>Motivation
The codebase has two unit test frameworks: JUnit and TestNG, which always make us confused about which one to use. I check the git commits and found that #1032 does this thing, but still has some tests using JUnit. We need to remove the JUnit, use the TestNG as the unit test framework in the codebase.
Modifications

Remove JUnit dependency
Clean the JUnit test in codebase

Documentation

[x] no-need-doc

/pulsarbot rerun-failure-checks

/pulsarbot rerun-failure-checks

/pulsarbot rerun-failure-checks

/pulsarbot rerun-failure-checks

@lhotari Please help review again, thanks.

@lhotari Please help review again.

/pulsarbot rerun-failure-checks

@lhotari Please help review the PR again.

Please verify the correct parameter order for TestNG Assert.assertEquals as explained in the comment above. Perhaps you already were aware of this since I see some changes in parameter order.

This request has been updated, could you continue to review?

@lhotari @nicoloboschi Could you please help review the PR again?


feat(wit): add definitions for a more general couchbase

Hey all thanks for this awesome project -- excited to see Couchbase integrated with wasmCloud!
This commit adds a more general WIT interface to a Couchbase cluster, including both basic and more advanced operations that users can perform.
I'm adding this PR to serve as a place to discuss the proposed API, receive feedback, etc, excited to hear what the team at couchbase thinks about this WIT as a part of their provider!

Hey @JesusTheHun Thanks for the detailed feedback -- I'll get to churning on these and make some updates!

Hey @JesusTheHun would love to get your feedback on https://github.com/couchbaselabs/wasmcloud-provider-couchbase/pull/2/commits/fc42fa2ee7946fcf40836e187148d93b34654bb0
I've kept it separate for now to make it easier to review (hopefully)

Hey @JesusTheHun would love to get your feedback on https://github.com/couchbaselabs/wasmcloud-provider-couchbase/pull/2/commits/fc42fa2ee7946fcf40836e187148d93b34654bb0
I've kept it separate for now to make it easier to review (hopefully)


fix:reduces the no. of setters

Reduced the no. of setters by:

Assuming a few defaults
Using the cluster name in conjunction with prefixes for deriving membership, feature and featuremembership names

@kaariger - PTAL


Fix homepage link

Apparently, this was copy-pasted from another composer.json file ;-).

i can even guess which one :-)


[ImageCache] cachedImages had no property sharedCacheKey

I don't use imageCache and so didn't really looked at how it works. But I'm transcoding cornerstone into typescript (preparation phase for an angular 2 version) and it's complaining about cachedImages not having a sharedCacheKey property.
It's inside removeImagePromise() and I think it's right since cacheImages is an Array and even if we can add custom properties to an Array I didn't find such assignation. Also there is a local var named cacheImage so I guess it's meant to be cacheImage.sharedCacheKey instead of cacheImages.sharedCacheKey

Thanks for reporting this - will be fixed in version 0.10.0


add bahrain country

Thanks for the contribution, @FnrDev!

It's live at https://committers.top/bahrain :+1:


ARROW-10951: [Python][CI] Fix nightly pandas builds (pytest monkeypatch issue)

This is rather ugly and brittle (since it relies on the exact place where this method is defined in pandas).
E   AssertionError: DataFrame.columns are different
E
E   DataFrame.columns values are different (50.0 %)
E   [left]:  Index(['あ', 'a'], dtype='object')
E   [right]: Index(['あ', 'b'a''], dtype='object')

pandas/_libs/testing.pyx:161: AssertionError

@github-actions crossbow submit test-conda-python-3.7-pandas-master test-conda-python-3.8-pandas-nightly

OK, all green, so merging this to get the nightly builds passing.


cpu 占用过高

VSCode Version: Code 1.15.1 (41abd21afdf7424c89319ee7cb0445cc6f376959, 2017-08-16T18:07:25.676Z)

OS Version: Windows_NT x64 10.0.15063
Extensions:

Extension
Author (truncated)
Version

typescript-react-snippets
abo
0.2.0

html-snippets
abu
0.1.0

vscode-javascript-snippet-pack
aka
0.1.5

path-intellisense
chr
1.4.2

jquerysnippets
don
0.0.1

vscode-html-css
ecm
0.1.8

vscode-great-icons
emm
2.1.14

react-native-react-redux
EQu
1.1.0

auto-close-tag
for
0.4.3

auto-rename-tag
for
0.0.14

canvas-snippets
hol
0.3.2

beautify
Hoo
1.1.1

path-autocomplete
ion
1.6.1

docthis
joe
0.4.8

node-module-intellisense
lei
1.4.0

debugger-for-chrome
msj
3.1.8

live-server-preview
neg
0.0.4

vscode-icons
rob
7.12.0

sass-indented
rob
1.4.1

code-settings-sync
Sha
2.8.3

stylelint
shi
0.28.0

guides
spy
0.8.4

open-in-browser
tec
1.1.0

JavaScriptSnippets
xab
1.4.1

vscode-preview-server
yui
0.7.0

(10 theme extensions excluded)

Steps to Reproduce:

Reproduces without extensions: Yes/No

TO help investigate:

Try disabling all extensions by starting code with the --disable-extensions flag. One of them could be causing this
Right click for more details  on the process. What are the full command line arguments of the process with the high CPU usage?

/Applications/Visual\ Studio\ Code.app/Contents/MacOS/Electron  --disable-extensions
It works.

Ok, since this issue does not occur when extensions are disabled, please try tracking down which extension causes the high CPU usage and reporting the issue against them. The process more details information may help with this


[BUG] Early game soft lock

Aged Version: 2.2.2

In the early game when just starting out. It is possible to soft lock yourself and not be able to attack or do anything. This is due to a permanent weakness effect not allowing me to attack mobs so it is practically impossible to earn xp to level up. I have tried everything to earn xp and or un-soft lock myself. This occurred in hardcore mode. I think this started when i upgraded my Aged Version from 2.2 to 2.1.2

This could be the negative effect from NutritionZ (mining fatique)...
Will change this to another effect in a new version

Fixed in newer versions of Aged.


Resizing window should resize tiles

Resizing the window should resize the tiles together with the tile number. The aspect ratio should stay the same.

Also working on it :)

Regression?

Working on it


ScalarMul on Bandersnatch

ScalarMul on Bandersnatch now uses the D=-8 endomorphism with a hinted scalar decomposition.
Groth16 bench:

variable-base ScalarMul 2436 constraints
fixed-base ScalarMul 1914 constraints
variable-double-base ScalarMul 4844 constraints

For Jubjub, it costs:

variable-base ScalarMul 3060 constraints
fixed-base ScalarMul 2538 constraints
variable-double-base ScalarMul 4844 constraints

Note that the variable-double-base ScalarMul algortihm is the same for both curves. It uses an interleaved simultaneous scanning of two scalars and a window table of 4 (Lookup2).  It is better constraint-wise to do so than using the endomorphism separately on two ScalarMul. Therefore, EdDSA verification cost is (almost) the same on both curve (Bandersnatch has 4C less as the cofactor clearing costs one doubling less), but the ScalarMul independently costs 624C less.

converting the PR to draft until we make sure of the hinted scalar decomposition.

@yelhousni when is is going to be mergeable? I want to fix the weird apis in twistededwards / eddsa (see #262 ) and you may get quite a lot of conflicts if I do so before this PR :)

@yelhousni ⬆  ?

@yelhousni ⬆ ?

I'll take care of that tomorrow. The GLV decomposition is correct (and scalar size bound is increased) but we may need to constrain few more things.


[release-1.20] Bump grpc-go and x/net

@jwendell: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-ambient_istio_release-1.20
88605ed9d5d95826264ff047f1d41d94beb4b310
link
true
/test integ-ambient

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

/retest


Update github.com/openstack-k8s-operators/glance-operator/api digest to c4e2e43

This PR contains the following updates:

Package
Type
Update
Change

github.com/openstack-k8s-operators/glance-operator/api
require
digest
4983070 -> c4e2e43

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[x] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

Closing this as I manually rebased it here: https://github.com/openstack-k8s-operators/openstack-operator/pull/66


[trel] align trel_interface and platform layer with the initialized state

Currently Trel::Interface has a mInitialized state that is set to true after the ot instance is initialized. The platform layer trel can be initiated and deinitiated at runtimes now after https://github.com/openthread/openthread/pull/10872. This means the Trel::Interface can have a different init state than the platform layer.
This PR adds a otPlatTrelIsInitialized() method for the Trel::Interface to get the platform's status, this is used instead of the Trel::Interface::mInitialized to avoid out of sync. Also changed the check of (mInitialized && mEnabled) to only (mEnabled) because the trel interface can't be enabled unless it's initiated.

Thanks @sunytt  for adding this. The mInitialized variable in Trel::Interface tracks whether the Trel::Interface class itself is initialized (it is not currently related to platform status).
I am not sure that adding otPlatTrelIsInitialized() and having the TREL core module check with the platform is a good approach. We define otPlat APIs for core modules to interact with the platform layer. These APIs are often commands that instruct the platform to perform certain actions.
If the platform is not yet ready (e.g., it is waiting to be initialized or requires some initial startup time), this should be handled by the platform implementation itself.
For example, for TREL, we have otPlatTrelEnable(), which OT core modules can call to enable TREL on the platform at any point. If the platform is ready (initialized), it can enable TREL when this API is called. If not, it should remember what it is asked to do and wait until it is ready (e.g., wait until it is initialized and then enable and start TREL-related functions, open the UDP socket, start the DNS-SD browse).

Similarly, for otPlatTrelRegisterService(), when it is called, if the platform is ready, it should register the service. If not, it should remember the information and perform the registration when it can.
If otPlatTrelSend() is called when the platform is not ready, it can drop the message (or it can consider more complex logic where the platform places the packet in a queue for later transmission when it becomes ready).

This is a simpler model than adding an API and requiring the core module to check and synchronize the status (readiness) of the platform modules. It aligns with existing behavior for interaction between core and other platform modules. For example, otPlatAlarm, otPlatRadio, and otPlatUart follow a similar model.
Thoughts?

@abtink Thanks for the details of the intended design. If Trel::Interface and the platform code are intended to maintain different states, now since they can have different initiated states, a couple of fixes are needed in the platform code, to not crash when called in uninitiated state in non-prod builds. See https://github.com/openthread/openthread/pull/10894. This PR is not needed, closed.


fix(patch): typo in --help example

extra comma in json snippet

Codecov Report
Patch and project coverage have no change.

Comparison is base (1f7641b) 69.46% compared to head (8dd1400) 69.46%.

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #50   +/-   ##
=======================================
  Coverage   69.46%   69.46%
=======================================
  Files          11       11
  Lines        1562     1562
=======================================
  Hits         1085     1085
  Misses        416      416
  Partials       61       61

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

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


Create a readme for the api reposity

TBD - Content

Estimate (hours): 3
Uncertainty factor: 2

Estimate (hours): 3
Uncertainty factor: 2


Jumpy behavior when dragging with mouse after scrolling with touchpad

I've a horizontal scroll view that can be scrolled my touch, touchpad or by dragging with scrollbooster.
When the scroll view is scrolled using the touchpad and afterwards dragged by scrollbooster, I get jumpy behavior :/
Currently I've worked around it by updating the scrollbooster offset in the shouldScroll method:
//Jumpy behavior workaround
shouldScroll: () => {
        sb.setPosition({x: scrollView.scrollLeft});
        return true
}

I have the same isse, where I should add that? scrollbooster.js? Can you give me more details/line number
thx

@byman64
mybe
sb.setPosition({x: viewport.scrollLeft});

Not sure I understand correctly. Is this issue still relevant on version 2.0?
Some online sandbox with example would be very useful

I think this may be due to an open devtools
I'm closing this for now, please let me know if this issue still remains


How do I programmatically change the currently selected annotation?

The JSON state for my Viewer contains this:
"selection": {
    "layers": {
      "my-line-annotations": {
        "annotationId": "123456789",
        "annotationSource": 0,
        "annotationSubsource": "default"
      }
    }
  }

But I can't figure out how to change it via the Python API.  For example, I tried this:
with viewer.txn() as s:
    s.selection = {
      "layers": {
        "my-line-annotations": {
          "annotationId": "123456789",
          "annotationSource": 0,
          "annotationSubsource": "default"
        }
      }
    }

But that yields:
AttributeError: 'ViewerState' object has no attribute 'selection'

Also, is it possible to get a callback when the user changes the currently selected annotation?

I tried to figure it out by looking into the TypeScript code (not my forte).  I see that the relevant variable is of type TrackableDataSelectionState, but I don't know how to proceed from there.

I guess there's no harm in just using JSON.  This seems to work, for my purposes at least...
state = copy.deepcopy(viewer.state.to_json())
state['selection'] =  {
    "layers": {
        "focused-edges": {
            "annotationId": "123456789",
            "annotationSource": 0,
            "annotationSubsource": "default"
        }
    }
}
viewer.set_state(state)

Would be nice to have a cleaner way to do this. Also, setting the selected annotation like this makes the annotation list scroll to bottom. This is very inconvenient when there are a lot of annotations in the list.


WIP : Invoices modal back

I let comments on what I tried so far
Need to ask stripe the best way to achieve what we want to do :
use the .pay() when doing a one time payment so the payment is attached to the invoice

today it sounds like it works with normal card number NOT with 3DS card !! // please retry normal card payment
didn't find a way to attach payment even with payment intent (.pay() wait for a payment_method ID OR a source)
when doing a stripe payment directly, looking at the logs it looks like they use 'source' stuff but they also say it's deprecated in the doc...

code moved to another branch


[Question] Support for Custom Attention Mask

❓ General Questions
Many thanks for your effort to develop such a great library. I want to add support for the ChatGLM (not the 3rd generation) model in mlc-llm, however, it seems to me that currently attention mask is not supported as documented in the following file:
# 3rdparty/tvm/python/tvm/relax/frontend/nn/modules.py:924

assert attention_mask is None, "Attention mask not yet supported."

How can I resolve this issue, sincerely wish to hear from you.

https://github.com/flashinfer-ai/flashinfer/pull/266
FlashInfer has supported custom mask, any plan to support custom attention mask ?


ec - University of Auckland

University of Auckland - Electronic Campus

@dg-spark Please rename lib/domains/nz/ac/auckland/ec to lib/domains/nz/ac/auckland/ec.txt
The .txt extension is mandatory. Thank you!

@philipto Apologies for using the wrong filename. I have committed ec.txt now. Thanks

@dg-spark Pull request merged. Thank you!


fix ctypes for zbar qrcode scanner

Fixes #205
How to reproduce: run python lib/qrscanner.py

This seems to be done on master and python3 branches.


Fix Wikipedia version and re-add tests

To keep backward compatibility when loading using "wikipedia" dataset ID (https://huggingface.co/datasets/wikipedia), we have created the pre-processed data for the same languages we were offering before, but with updated date "20220301":

de
en
fr
frr
it
simple

These pre-processed data can be accessed, e.g.:
ds = load_dataset("wikipedia", "20220301.frr", split="train")

The next step will be to offer the pre-processed data for many other languages, but when loading using "wikimedia/wikipedia": https://huggingface.co/datasets/wikimedia/wikipedia

The docs for this PR live here. All of your documentation changes will be reflected on that endpoint.


Fix install-python on Python <3.4

The venv module was introduced in Python 3.3, but the deadsnakes PPA doesn't include a python3.3-venv package.
Here is an example where this breaks.
I guess per #6 there are no tests, so it's hard to know if this will work I guess.

I tested a this job and it doesn't actually work, because it cannot find venv. I tried digging into the deadsnakes PPA to see about adding an option to just disable venv creation (we are already executing this in some ephemeral VM or container, after all), but when I did that I found that, weirdly, it seems that the python3.3 package already distributes a binary called pyvenv.
I tried using this pyvenv, though, and though it seemed to work, that's just because Python 3.6 also distributes a pyvenv, and the current version of the code picks that up.
@asottile Not sure where to go from here. One option is to change this over to not require a virtual environment, or to not use a virtual environment unless you are on Python 3.4+.

is..... is someone seriously trying to use 3.3 in 2020? lol

is..... is someone seriously trying to use 3.3 in 2020? lol

The only thing that's difficult about it is actually running the tests. Pretty much all backwards compatibility measures to support Python 2.7 will also make your software compatible with 3.3.
I test against all versions of Python that I know the software works in, so that I can label the point at which the code actually stops working in an "unsupported" version of Python. If I made any changes to dateutil now that broke on Python 3.3, I'd simply update python_requires and the trove classifiers.
Unfortunately, we (as an ecosystem) are pretty bad about using lockfiles and reproducible tests, so the test rigs themselves bit-rot annoyingly quickly.

just a heads up as well after focal there won't be builds for <python3.5 because of the libssl changes so there will be some dead dead 🐍s :)

just a heads up as well after focal there won't be builds for <python3.5 because of the libssl changes so there will be some dead dead s :)

If I ever get to work on dateutil again rather than just trying to get the CI system back into shape, I plan to finish up the changes to the way time zones work and then drop support for Python 2 (if I get out a version with support for changing the zoneinfo location and using the tzdata repo for non-system time zones instead of an embedded tarball, the python-dateutil package on 2.7 should hopefully be good enough without patches for something on the order of years rather than months).
Once that happens, I'll likely want to drop support for everything before 3.6 anyway.

You may want to add a note about which versions of Python are supported by this on the README.


WorkflowTemplate reports invalid spec:  template '' undefined

Checklist:

[x] I've included the version.
[x] I've included reproduction steps.
[x] I've included the workflow YAML.
[x] I've included the logs.

What happened:
Attempted to simplify single-file Workflow by using WorkflowTemplates, and although the tasks completes successfully, it reports as failed every time, with the following value occupying Message:
invalid spec: templates.testing-relative-calls.steps[0].git-initial-status.template '' undefined

What you expected to happen:
The separated workflow just works.
How to reproduce it (as minimally and precisely as possible):
Run argo submit <filename> on the yaml, and watch it hang.
Anything else we need to know?:

testing-relative-calls.yaml

apiVersion: argoproj.io/v1alpha1
kind: Workflow
metadata:
  name: testing-relative-calls
  namespace: argo-events
spec:
  entrypoint: github-pending
  onExit: exit-handler
  arguments: []
    # <<REMOVED FOR SANITY>>
  volumes: []
  templates:
  - name: github-pending
    steps:
    - - name: git-initial-status
        templateRef:
          name: github
          template: report-github-status
        arguments:
          parameters:
          - name: state
            value: "pending"
  - name: exit-handler
    steps:
    - - name: successful
        templateRef:
          name: github
          template: report-github-status
        arguments:
          parameters:
          - name: state
            value: "success"
        when: "{{workflow.status}} == Succeeded"
      - name: failure
        templateRef:
          name: github
          template: report-github-status
        arguments:
          parameters:
          - name: state
            value: "failure"
        when: "{{workflow.status}} != Succeeded"

report-github-status.yaml

apiVersion: argoproj.io/v1alpha1
kind: WorkflowTemplate
metadata:
  name: github
  namespace: argo-events
spec:
  templates:
  - name: report-github-status
    inputs:
      parameters:
      - name: state
      - name: build-base-uri
        value: "{{workflow.parameters.build-base-uri}}"
      - name: git-commit-sha
        value: "{{workflow.parameters.git-commit-sha}}"
      - name: workflow-name
        value: "{{workflow.name}}"
      - name: github-repo-statuses-base-uri
        value: "{{workflow.parameters.github-repo-statuses-base-uri}}"
      - name: github-token-secret-name
        value: "{{workflow.parameters.github-token-secret-name}}"
      - name: github-token-secret-key
        value: "{{workflow.parameters.github-token-secret-key}}"
    script:
      image: ellerbrock/alpine-bash-curl-ssl:latest
      command: [bash]
      env:
      - name: GITHUB_TOKEN
        valueFrom:
          secretKeyRef:
            name: "{{inputs.parameters.github-token-secret-name}}"
            key: "{{inputs.parameters.github-token-secret-key}}"
      source: |
        case {{inputs.parameters.state}} in
          success)
            description="The build was successful!"
            ;;
          failed)
            description="The build failed"
            ;;
          *)
            description="The build is running"
            ;;
        esac
        read -r -d '' curl_data << EOM
        {
            "state": "{{inputs.parameters.state}}",
            "target_url": "{{inputs.parameters.build-base-uri}}/{{inputs.parameters.workflow-name}}",
            "description": "$description",
            "context": "ci-cd/argo-workflows"
        }
        EOM
        set -x
        curl \
          -H "Authorization: Bearer $GITHUB_TOKEN" \
          -H "Content-Type: application/json" \
          {{inputs.parameters.github-repo-statuses-base-uri}}/{{inputs.parameters.git-commit-sha}} \
          -d "$curl_data"

Environment:

Argo version:

argo: vv2.7.4+50b209c.dirty
  BuildDate: 2020-04-16T16:28:14Z
  GitCommit: 50b209ca14c056fb470ebb8329e255304dd5be90
  GitTreeState: dirty
  GitTag: v2.7.4
  GoVersion: go1.13
  Compiler: gc
  Platform: darwin/amd64

Kubernetes version :

clientVersion:
  buildDate: "2019-12-11T12:42:56Z"
  compiler: gc
  gitCommit: 6c143d35bb11d74970e7bc0b6c45b6bfdffc0bd4
  gitTreeState: clean
  gitVersion: v1.15.7
  goVersion: go1.12.12
  major: "1"
  minor: "15"
  platform: darwin/amd64
serverVersion:
  buildDate: "2020-03-18T22:49:35Z"
  compiler: gc
  gitCommit: aa93664bafe74f3c051e021b27a64e28ac34ab40
  gitTreeState: clean
  gitVersion: v1.15.11-gke.1
  goVersion: go1.12.17b4
  major: "1"
  minor: 15+
  platform: linux/amd64

Other debugging information (if applicable):

workflow result:

Name:                testing-relative-calls
Namespace:           argo-events
ServiceAccount:      SANITIZED
Status:              Running
Message:             invalid spec: templates.testing-relative-calls.steps[0].git-initial-status.template '' undefined
Created:             Thu Apr 16 16:31:23 -0400 (13 minutes ago)
Started:             Thu Apr 16 16:31:23 -0400 (13 minutes ago)
Finished:            Thu Apr 16 16:31:23 -0400 (13 minutes ago)
Duration:            0 seconds
Parameters:       [] # SANITIZED

STEP                                                      TEMPLATE                             PODNAME                                                           DURATION  MESSAGE
 ● testing-relative-calls                                 git-initial-status
 └---◷ git-initial-status                                 github/report-github-status          testing-relative-calls-3382379192  13m

executor logs:

Completed pods, not failed!

workflow-controller logs:

W0416 20:51:57.549050       1 reflector.go:302] pkg/mod/k8s.io/client-go@v0.0.0-20191225075139-73fd2ddc9180/tools/cache/reflector.go:98: watch of *v1.ConfigMap ended with: too old resource version: 16172178 (16175377)
time="2020-04-16T20:52:09Z" level=info msg="Alloc=6574 TotalAlloc=111353 Sys=71360 NumGC=85 Goroutines=101"
time="2020-04-16T20:53:17Z" level=info msg="Processing workflow" namespace=argo-events workflow=testing-relative-calls
time="2020-04-16T20:53:17Z" level=info msg="Updated phase  -> Running" namespace=argo-events workflow=testing-relative-calls
time="2020-04-16T20:53:17Z" level=info msg="Steps node {testing-relative-calls testing-relative-calls testing-relative-calls Steps github-pending nil    Running   2020-04-16 20:53:17.28125219 +0000 UTC 0001-01-01 00:00:00 +0000 UTC   <nil> nil nil [] []} initialized Running" namespace=argo-events workflow=testing-relative-calls
time="2020-04-16T20:53:17Z" level=info msg="StepGroup node {testing-relative-calls-4000565252 testing-relative-calls[0] [0] StepGroup github-pending nil    Running testing-relative-calls  2020-04-16 20:53:17.281321122 +0000 UTC 0001-01-01 00:00:00 +0000 UTC   <nil> nil nil [] []} initialized Running" namespace=argo-events workflow=testing-relative-calls
time="2020-04-16T20:53:17Z" level=info msg="Pod node {testing-relative-calls-3382379192 testing-relative-calls[0].git-initial-status git-initial-status Pod  &TemplateRef{Name:github,Template:report-github-status,RuntimeResolution:false,}    Pending testing-relative-calls  2020-04-16 20:53:17.281776102 +0000 UTC 0001-01-01 00:00:00 +0000 UTC   <nil> nil nil [] []} initialized Pending" namespace=argo-events workflow=testing-relative-calls
time="2020-04-16T20:53:17Z" level=info msg="Created pod: testing-relative-calls[0].git-initial-status (testing-relative-calls-3382379192)" namespace=argo-events workflow=testing-relative-calls
time="2020-04-16T20:53:17Z" level=info msg="Workflow step group node &NodeStatus{ID:testing-relative-calls-4000565252,Name:testing-relative-calls[0],DisplayName:[0],Type:StepGroup,TemplateName:github-pending,TemplateRef:nil,Phase:Running,BoundaryID:testing-relative-calls,Message:,StartedAt:2020-04-16 20:53:17.281321122 +0000 UTC,FinishedAt:0001-01-01 00:00:00 +0000 UTC,PodIP:,Daemoned:nil,Inputs:nil,Outputs:nil,Children:[testing-relative-calls-3382379192],OutboundNodes:[],StoredTemplateID:,WorkflowTemplateName:,TemplateScope:,ResourcesDuration:ResourcesDuration{},} not yet completed" namespace=argo-events workflow=testing-relative-calls
time="2020-04-16T20:53:17Z" level=warning msg="Error updating workflow: Operation cannot be fulfilled on workflows.argoproj.io \"testing-relative-calls\": the object has been modified; please apply your changes to the latest version and try again Conflict" namespace=argo-events workflow=testing-relative-calls
time="2020-04-16T20:53:17Z" level=info msg="Re-applying updates on latest version and retrying update" namespace=argo-events workflow=testing-relative-calls
time="2020-04-16T20:53:17Z" level=info msg="Update retry attempt 1 successful" namespace=argo-events workflow=testing-relative-calls
time="2020-04-16T20:53:17Z" level=info msg="Workflow update successful" namespace=argo-events phase=Running resourceVersion=16176791 workflow=testing-relative-calls

Logs
argo get
Name:                testing-relative-calls
Namespace:           argo-events
ServiceAccount:      SANITIZED
Status:              Running
Message:             invalid spec: templates.github-pending.steps[0].git-initial-status.template '' undefined
Created:             Thu Apr 16 16:53:17 -0400 (3 minutes ago)
Started:             Thu Apr 16 16:53:17 -0400 (3 minutes ago)
Finished:            Thu Apr 16 16:53:17 -0400 (3 minutes ago)
Duration:            0 seconds
Parameters:          SANITIZED

STEP                                                      TEMPLATE                             PODNAME                            DURATION  MESSAGE
 ● testing-relative-calls                                 github-pending
 └---◷ github-pending                                     github/report-github-status          testing-relative-calls-3382379192  3m

NO FAILED PODS

Message from the maintainers:
If you are impacted by this bug please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.

Hi @ericmeadows. A couple of things:

I tried my best to reproduce this behavior with no success. The sample workflow and workflowtempalte you provide it also make it difficult since it has a lot of specific parameters and code. Is it possible for you to try to reduce its complexity in a way that still causes the issue on your end?

I searched the entire codebase and it seems that getting an error with the exact structure of
invalid spec: templates.github-pending.steps[0].git-initial-status.template '' undefined

is impossible. The closest is https://github.com/argoproj/argo/blob/06c4bd60cf2dc85362b3370acd44e4bc3977dcbc/workflow/validate/validate.go#L390 but that error contains the string name and yours does not.

In the workflow-controller logs that you posted, the error is
level=warning msg="Error updating workflow: Operation cannot be fulfilled on workflows.argoproj.io \"testing-relative-calls\": the object has been modified; please apply your changes to the latest version and try again Conflict" namespace=argo-events workflow=testing-relative-calls

That seems to be fairly unrelated to validation. Could you look into this? Perhaps you have multiple controllers in your namespace?

Chatted with @ericmeadows offline about this bug.
For posterity: the issue was that there were multiple controllers of Argo with different versions acting on the same resources. In this case it was Argo 2.7.4 and Kubeflow Pipelines running Argo 2.3.0.
The solution to this is to set different Instance IDs to each controller so that they don't step on each other's tracks.


⚠ Jenkins Plugins Artifactory has degraded performance

In 21eff72, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1363 ms

Resolved: Jenkins Plugins Artifactory performance has improved in da14229 after 12 minutes.


Mega remote releases

Hurray for BOSH being able to fetch releases for itself!!

Nice feature  !!
Well, hope we will have http proxy support for poor corporate bosh ops ;-)

Updated. Tests should pass again. Fixed a bug where run_nested_command would not exit if the nested command failed.

Updated. Tests should pass. Added ability to create/upload release from local release folder.

This PR covers multiple stories in OSS Release Integration team's backlog:
https://www.pivotaltracker.com/n/projects/1382120
Some of the stories have been rejected, and others are still in flight, so this PR is not ready to merge.  I will close this PR, and we will resubmit after stories have been accepted on the fork.

Hey @cppforlife @Amit-PivotalLabs, is there any update on this functionality being merged? Thanks!

@mavenraven It looks like they have been merged as part of #969. They were rebased so the PR doesn't have the merge in it.
I think the head of the code pull is here 6d2fb2bba0d6bb022ce6207cfc211a14e4e2456f

Got it, thanks @jpalermo!


toASCII returns incorrect result

While converting various emojis, I've found that very often it is not converting them correctly.
What I'd expect:
1. punycode.toASCII( "❄🙊" ) should equal "xn--tdix719m" where instead it equals "xn--tdiy444e5vxg" (invalid punycode)
2. punycode.toASCII( "👰✉" ) should equal "xn--4bi6168m" where instead it equals "xn--4biw254ehqwg" (invalid punycode)
I could give many more examples, but I haven't found a pattern in the mistake.

What makes you say that’s the expected output, and that the current output is “invalid Punycode”? Could you elaborate please?

Yes, sorry. I've been converting many emojis and because the punycode isn't correct many of them haven't been appearing correctly, which is what pushed me to investigate further. I tested on many conversion sites to test that out. The main one I trust most is Punycoder. If you try converting those strings above, you will find the results I was describing.

Cluster-Nobes has given a networking drive & wifi-drive. Having first error on Nobe-3

This is not really a bug. It's a limitation.
> [...'❄🙊']
[ '❄', '', '🙊' ]
>

The second character is U+FE0F. If you drop it from the input, you get the correct result. Take a look at idna-uts46 for a more detailed explanation.
Here's a quick alternative that works in the browser as well as Node.js:
let toASCII = d => d.split('.').map(l => new URL(`ws://${l}`).hostname).join('.');


upgrade to play25

The main change is requiring an ActorMaterializer and an ActorSystem. Anyone using newer version of Akka and Play are used to dealing with these.
I'm not yet shutting the systems down in tests. I'll update with a specs scope for that.

you probably need to change here as well.
As discuss in gitter, we should make examples modules sub projects of asobu in another PR.

👍
Thanks a lot


[Voice] Blade by Sergeant Todd

The author of this VP is Sergeant Todd.

URL: https://unrealarchive.org/voices/unreal-tournament/B/blade-by-sergeant-todd_0c9767ea.html
Hash: 0c9767eadf0b4f09e58dd01ef8ef3e4171b3d869
Current name: Blade by Sergeant Todd

Fixed


Add a test using cross-model relations

Issue
Validate that cross-model relations with grafana-agent are usable.
Closes #174
Solution
pytest-operator gets confused on some of the cross-model operations (create_offer, list_offers), since libjuju uses a ContextManager which subsequently closes the connection to the controller, but it's a small thing to work around.
Testing Instructions
Run the integration test.
Release Notes
Add a test using cross-model relations

Note: this PR is only a single file, and looks huge because it's based on #276.

Note: this PR is only a single file, and looks huge because it's based on #276.

Which file is the new one?

mypy on tests is completely unnecessary

Ouch. Separate issue/PR so we can discuss?

I mean, tests are just internal, but fighting mypy fighting itself between parts of stdlib and mypy's own typeshed is a waste of time, at best:
.tox/static-unit/lib/python3.8/site-packages/mypy/typeshed/stdlib/unittest/mock.pyi: error: Source file found twice under different module names: "unittest.mock" and "mypy.typeshed.stdlib.unittest.mock"
Found 1 error in 1 file (errors prevented further checking)
ERROR: InvocationError for command /home/rbarry/charms/prometheus-k8s-operator/.tox/static-unit/bin/mypy tests/unit (exited with code 2)

mypy on tests is completely unnecessary

Ouch. Separate issue/PR so we can discuss?

I mean, tests are just internal, but fighting mypy fighting itself between parts of stdlib and mypy's own typeshed is a waste of time, at best:
.tox/static-unit/lib/python3.8/site-packages/mypy/typeshed/stdlib/unittest/mock.pyi: error: Source file found twice under different module names: "unittest.mock" and "mypy.typeshed.stdlib.unittest.mock"
Found 1 error in 1 file (errors prevented further checking)
ERROR: InvocationError for command /home/rbarry/charms/prometheus-k8s-operator/.tox/static-unit/bin/mypy tests/unit (exited with code 2)

Version pinning "fixed" it:
httpcore==0.14.7
mypy==0.950
responses==0.20.0

Removing mypy from tests also fixed it :+1:
We shouldn't have to pin mypy or other packages because mypy cannot sort out things from stubgen and the standard library.
The complete lack of useful help if you search "Source file found twice under different module names" is a negative. How do you fix this? Uh... anybody's guess. It's not like they document it.


Elevation output

https://github.com/graphhopper/map-matching/pull/187

@michaz should we use a ConfiguredCommand instead to read the configuration from the config file?

My workflow for map-matching was basically over cli, but originally you can only add elevation if you use the web interface, so; this add add elevation on cli.
I didn't add cli for importing; i haven't figure it out yet

@karussell Yeah, if anything. I don't really feel like maintaining this, it's just been there forever and at one point I ported it to a Dropwizard Command.

@karussell Yeah, if anything. I don't really feel like maintaining this, it's just been there forever and at one point I ported it to a Dropwizard Command.

MatchCommand now requires a config file and a profile name. If elevation can go in the config file, it can now go into map-matching.

MatchCommand now requires a config file and a profile name. If elevation can go in the config file, it can now go into map-matching.


[retrofit_generator] Error: Property 'path' cannot be accessed on 'File?' because it is potentially null.

Describe the bug
If we want to use an @MultiPart() API for sending Files where some of them are optional, retrofit generator ignores the fact that File can be null which leads to the compile error described in the title.
To Reproduce
Steps to reproduce the behavior:
For example, declare an API call like this:
@MultiPart()
@POST("upload")
Future<String> uploadSelfExamRecordings(
    @Part(name: "user") String user,
    @Part(name: "firstFile", contentType: "text/plain") File? firstFile,
    @Part(name: "secondFile", contentType: "text/plain") File? secondFile);

Retrofit generator will generate .g.dart file that will look like this:
_data.files.add(MapEntry(
      'firstFile',
      MultipartFile.fromFileSync(
       firstFile.path,
        filename: firstFile.path.split(Platform.pathSeparator).last,
        contentType: MediaType.parse('text/plain'),
      ),
    ));

During compile, you will be able to see the above error since firstFile can be null.
Expected behavior
Introduce null check when adding MultipartFile to the list.
if (firstFile != null) {
      _data.files.add(MapEntry(
          'firstFile',
          MultipartFile.fromFileSync(
           firstFile.path,
            filename: firstFile.path.split(Platform.pathSeparator).last,
            contentType: MediaType.parse('text/plain'),
          ),
        ));
}

Screenshots
Not applicable
Desktop (please complete the following information):
Doesn't matter, this is compile issue.
Smartphone (please complete the following information):
Doesn't matter, this is compile issue.
Additional context
Retrofit generator version used is 9.1.3
The workaround for the issue is to mark nullable File objects as optional.

@nebojsa-licina , I also facing this issue. So, I forked the repo and edit some code lines. Now, I request to merge this pull request https://github.com/trevorwang/retrofit.dart/pull/720. This request can help your issue.


Request: Control allowComments Page Option

Hellow,
We noticed here that the pages database contains a allowComments variable / option, which cannot be changed on the new-content.php nor the edit-content.php bludit administration pages. However, such an option would be really really helpful for custom comment plugins.
A simple implementation like the following one (which works at least on the latest version) would be perfect. (Example code for edit-content.php)
// Page Comments
echo Bootstrap::formSelectBlock(array(
    'name'      => 'allowComments',
    'label'     => $L->g('Page Comments'),
    'selected'  => $page->allowComments()? "1": "0",
    'class'     => '',
    'options'   => array(
        "1"     => $L->g('Allow Comments'),
        "0"     => $L->g('Disallow Comments')
    )
));

Thanks.
Sincerely,
Sam.

Hi,
yes I need to check this, the problem is provided this button to change this field when the user don't have enabled a comment system, is going to be wired.
I was thinking to add to the plugins a field type, so if the plugin is related to a comment system has the type=comments, if the plugin is an HTML Editor the type is editor, so is possible to check if there are some plugin enabled with the type comments so appear this checkbox.

Related topic: https://github.com/bludit/bludit/issues/996

So you plan to conditionally show the allowComments checkbox if a comment-type plugin is enabled? I think that could work, but I'm not sure if a strict taxonomy like #996 proposes is useful in the long run. Why not add additional hooks, so that plugins can e.g. in the constructor tell the system which capabilities they require/want to enable?


⚠ Bofrost.si has degraded performance

In 72deb62, Bofrost.si (https://www.bofrost.si) experienced degraded performance:

HTTP code: 200
Response time: 1823 ms

Resolved: Bofrost.si performance has improved in c6fb753.


Console "complete withrawal" doesn't ask to connect an ethereum wallet

May be fixed by: https://github.com/vegaprotocol/frontend-monorepo/issues/3364
Description
If the ethereum wallet has disconnected from the console webapp for whatever reason (maybe frame.sh I am using is more prone to disconnect) then "complete withdrawal" tells me I am on the wrong network in console.

If I then go to do a fresh withdrawal it would ask for destination and then connect to the wallet. Afterwards "complete withdrawal" works.
Device details
Mac OS (latest) M1, Firefox browser, frame.sh

Already resolved


Add some utils functions to ChemReactions and RDKFingerprints

Chem Reactions

provide function to re/move agents
add utils function to remove atom-mapping numbers
allow sanitization of reactions, necessary for improving drawing

RDKFingerprints

add an unfolded count-based version of this FP
add a bitinfo map to allow mapping bits back to atoms like the one used in MorganFPs
refactor some code to largely avoid code duplicates

@NadineSchneider,  A request for the future: Please try and avoid doing PRs with multiple different pieces of functionality in them.
Now that we've gotten more serious about reviews, having multiple topics in one PR makes things more confusing.

Please add a test for the new bitInfo argument to the bit vector version of the RDKit fingerprinter to both the C++ and Python test suites.


Add a Monoid instance for Parser

What does this pull request do?
Fixes #33
Note: this doesn't implement Foldable for Parser, which is the other part of that issue.

Thanks! I'm not sure a Foldable instance makes much sense for Parser; this PR at least does enable the use case of calling fold on an a array of parsers, though, which is nice.


new-issues-fixed

@origranot
#88 was my PR
https://user-images.githubusercontent.com/97425135/194712031-c2e02bc9-e1f1-45a5-b962-bf70c568dab7.mov

@Dev-Code24 It looks great! I really want to merge it alreadt.
Just one more fix, we need to indicate the users that it's a dark mode toggle..
Something like this:
https://codepen.io/grapdroad/pen/gOzaXQg

@origranot
I've done the needed changes
https://user-images.githubusercontent.com/97425135/194715834-1e556d03-7d64-40fa-90e1-4b9c249f271b.mov

@Dev-Code24 Hey!
Do you mind fix the issues?
And maybe put the dark mode icons inside the toggle button.
examples:
https://codepen.io/sophiekoonin/details/jOWKvOr
https://codepen.io/gvissing/details/OJvxoJq

@Dev-Code24 can you pull from dev and merge?

@origranot
who is dev?


panic on subgraph query

Subgraph queries panic early when attempting to use the QUERY_DURATION metric.
thread 'tokio-runtime-worker' panicked at 'called `Result::unwrap()` on an `Err` value: InconsistentCardinality { expect: 2, got: 1 }', /home/theodus/.cargo/registry/src/index.crates.io-6f17d22bba15001f/prometheus-0.13.3/src/vec.rs:258:49
...
at /home/theodus/src/edgeandnode/local-network/build/graphops/indexer-service-rs/service/src/server/routes/subgraphs.rs:40:32

QUERY_DURATION is declared with the expectation of 2 labels, deployment & name, here. But only deployment is set here. I would have just fixed this, but I'm not sure what the name label is supposed to be populated with.

This is weird, ts impl here has the 2 labels but only uses deployment.
I would just remove name from the metrics declaration


[Addition]: Multiple Hummingbird selfwitnessing clusters

Hotspot b58 Addresses
112a3vwbkQsCnSo6Ex5hYZxYuLMcCggAbTRjEcnsBUitz99v4DrV
112Y72DrmhMSM7dGwaFzwHwB881PXRiUfjpU2u9BzUnkx2h4bM2T
11zKP5Fkc51W3JD1hYR8hqiPiaGwrmbvsJt2SRrxum8Ub2JzHeH
112cTsEMBHXZVJNj9gdrrKXRQPNP3c3c3Fnb4JEVXQJHF5AGcJYQ
112TUV8hj5uZFZGixG75oKETffXWoa3aC9gQgJaYdBkTXiB6ssRW
11FTuh35P7tCLiM6jtVXfA8CMMvXrRJqTB8gu53QX7Mqgccy36C
11HLKU1kEqc7u7hW8vaYAgkRFzW8rZ581TniskRtysTLEkmWBMk
11q3v1UyC7S1J3KUTgnkPNG95JVP4LGkeHuE9birZAj1xZWHCdA
1127pVLQfsVdHfyVWmVNgDq7xNd7ou5d7wpp1Rt9cBbtkCtcT6sm
1128YKAWVA2eCuYUH3j3Xy4X8yfHPBtfRCGbXeVpcyhGRhibkcPX
112CiACph7M7RqURep6MTa99sA6yhWetPr86c5BfR3sUZ7xc9q6T
112W9Ys3nJ2GDGBM9sPgN9gZyY9hhrxY9cn2R8zoLzzsxyTDtbWt
11cEm3fsnAbZ8EVHHW6ix4KcGFpNTeWNWZo1Uuqm5ZrLJ85ntdX
1123Xr9XXk31oM6E7Co1R7DECA493NqiMCM8UGRwQxNqCEJJcEzV
112VaHeqTbj2sXCa3QTEfmKihwqGQHjL3txxL7RLGDkUkhjsdgsn
112cf8QwVTt9HycznEmnpczkm812WbKXTz3hbLVmJgyuwM3pBbmr
11Pwtnt4LGdg7ogQfz6V1zH1zrU4iJTDRimuN62knG6w7s2zasL
11wyGNLRLMW3jX7Pm834F289WBZnNyLykqgGea9VnQrTc3JL7eX
112eqQZArZM6zb4FYNBMWPnbUPgNUKac2E5TGv7gfgcxpgLbrHnQ
112gVy4daSSUec49oJyBAv2r9qcktJmM8kBq9B3GtJ7ns5uzFJoj
11kgwvLpFyNZ5jbCWdBVPPf9xCNZkZzN9CKpVg4DSisMF6NqUgq
112emVrNMGeNZKPxC33nNpDNVNdAJ22hM1G8cerhu67tCBLUEhss
11sjqKRo2RNzUfPnLAhfDCMh7kEXoNmYsB3WhATXmRLB5WpsNdF
11vkopyqFE1j7d2CGGonj95mMM6pgeYoucFojmCwbtGXMhrEbmN
112bej4M4PnfNCiRRXABW2jb5RhDKqgwRXyqEWXDhZHgKbsR9gtb
112Ds1drJFkYS4o5yjQmJmdJmrMjUPRferavzSYu8gK1qCfmbM48
112eFWYefe8N6HTHxvGF8thsmSdWKC5LuXcL56e51ZwpdaUyqSy3
112N31TzBeSv71iQ5L18BJ83XrkNmrC4SeAAC9XnbeEpyFg2gkKD
112qoAu5Sk8anzNXqi4bVR1Gm9nPT6bhqcXyCjAXuBUwJSoZnEbS
112vBe564ZpBVVg22QdDNRzMmp34zYtwJ4gXftJ6Bg5fWjHK6Gad
112WmVHodM1h6V9dM3wfQ9ZTvmR4iGNwPYHQ7UCWaLxnDp1QHU2k
11dnyEF3bJbNZ5T1E1U66XCoE4q1qDLTpXupASvy3dvBD69UWEj
11xfjQ4nKTs7LHrSJeXsSxKsWGaXNhFKYHJRrcvrdC3n115ZHpw
11ZX4JEDz7KQTQkoFbBqjbSs9aikzLyazuyGSwtWodBygBcvsDt
112BjfPajJG52tqyjmZoyuZTiuMbHxgf56gFHTQ1MgCTmX2j1ZUF
112jEUTutR1xn5LiWQLTqJgioGkNyPRhoRr9BszFkUuK5JwFwytz
11Dajd65KD5pqimd94LbVgvFxouQ7nDrhdi89j1krLieMAeJLvx
11dBb68kSmBkaU6rgfFNUEaS4V3yL5JfmZfriv4qfYBa3eG1qj7
11DHqVT2N5j3jszoUbRzwaf3BeVMq8yU5fucjpRnHhQv4FFqVsN
11vLhVHeo3cgoXJSUNokvUcFCUiZMCqZaPfeTH7V4BswSAoVDMu
1121wro5ogQEP6D2c3yVr2ZychMpqGbkRw5xpAi9FKkHAodkAZLX
112dphoe51aquQYbUZSiwXRWvEKeR1i6tuWTsDpMqTE6m8nXukm5
112DUJGRSALPHjAwdZYVpqqCfLevkYELHkfU4A4v8hVuYpRT818S
112EuvLsYGMFCEgPmKpuwJJkmKbpgFY6p78NHC4BEBGxu4bJwmDe
112kBo42uJYsbuFB51EvTd6Z2UZse6n2f5NJ6hBkgvyqDyGFVgBy
112Qu1yHZQku6sF5xtSfD6399mSEJQCFU2K2hjj8ZsC2PyttcKHq
112WU5SoZ6vUM2kZdYhzPWUKzAdsZPDwbjPCK8mAAcM3dKds7VnG
114kez9VZeHHDVz2gvWqb8Poa2ptzeDprCNQ8gWdRFScWmZJAez
119nkAay3Fdmr8DbMPhSfAcTTXFNBmN7qXCHmcjEJErj6DF3SRW
1127gr69k1qSGuXMEX8hxDEX2zAfHQpSKEnfSbQfPFMN4Eq1dDEx
11CsP1UXLKmyGc98ZjQT879dUSYR9FpMvbvPihavDvnmG6wzW8N
112Bu529mpqVLHvNDSqVLcw5mTvjr4nv8zxVeVphY29zqoQEWig5
112FWdrcKE9Xc2JGt8BdC7vSDqPWUbaU2VJkDwvJsNiSerjmhTQG
11283YEUmJtttXtiqSoQKvw4U4Cz2YfpASYb4FowxKUmnnDw3VTu
112eyZ8D635KHghTA1cJxLWNg3M8Z7nTDsd1HLLjernrqo7oXQaf
112juHHaEDM9QT1pGp2AjiGNNtQufox351iG54vvCAsZxBHg6Aq4
112SEnMhSngVBpkWPnvog4gLe3bZxx8WfL2Lt8gCFX2c2fjekarE
112XeJG9JfSaYpJuLWnU9VkEmemS2iGHb6ebsznYc8s2tRJ8HuQA
112YLRy6WnWTQbZwk1Kf6zDJr4Sn7KazxfDutAWReFXM1nTLkmwX
11DqF1YY7yj5DLYHzu25MSTcdLN9GJuq38eCotdqgBbjz1mcVJP
11RLB2RcCNbPuu6f1rGodVvVBTd7aTWXWCEhR4mAUPKBEiPBBCH
11uT5WjDRrkBwK2hW6kvaTAnqy1BXkPVUSf4ynH1s2bw4LJcSWc
11xnjR3h2fcakhedSHusAdxXD5AfBYgzJNiEz9FL7SJMfWXS1wu
112fodoKAJoV4zq5EvcBsNfejJ3RapMi8wi6Kbo8kKf5totngkqS
11LVdbLhC15aoXaojEcmg4QGwtPB5u5Ny4BnvPi6niPEPWjdm2x
11Xwu5tvCqgpLsLJPkxVRcAuYzAoTszVv6seDsxS3YZ3LndzMNT
112dE8Chk5eBCLj2j9tzjBRt6swUbSs6H51HhQDB8k6ZSuhiBFfb
112KWCx5tVwieweyZXE8PGoxQCHRTjGcB9SBF8bSuvtjjZTfFeyN
112r4y8iSYiM1BM1KBH28xdwvpzivzQd1pEv32u8bwEqBuxjzcJe
11a7h9hYz9Aps3X8zx24gqeW61JKGLo4cxkroGLtCFaZaXUnP8R
11euuV9G64Qp1VsZpoSCQMaBNt3MPfa5esNrcgtfSdeAy98KW29
112ETbBn1qELhWGtk8wRLCQDk3NBZM2SMuWTd9wsgAfz4TAzQSjZ
112UNBjgi6Mh6E5A15brnXrzbnaXnwZMTznHV9muwtMjZr8GgNmo
11qzHFNjq5eEZe7yVfuZYy2B4YmwhoMXe7KxUGFioaHj1xQrBFK
1126EcHrzkkchv47ejBfrtCUGt3vfN7LfbVMMmJLJkxWoEfZKv2k
112cS5zwP69etCX7ZzoAexeeTPj6AN71VkgjRHsjWQPsRHMnHQqZ
112Y7MeFhfU9GL2HAFatjuQDp8og1TgrXaF6TKvLRQ2uivSBb6s7
112Zrt1GQDeorXnjxF7sU4wN7dhE46j9zzQroTmTpKicuWTHV7zA
11jmHbFYVCKKvx8fXmbKXsDHwCU7VkNC7YKN8vLZZmvoSr6Ea6y
11mfxL1KEE4kTsP5StMPLze1YMQR1FpxQvdZGCTLEsWn1pnd7bn
11MnEyC5bQhFBCd5zDr5Tg6eM1Wuz1ddWN4o4yW2nUrNU1ZVpjp
11zat1jR7QP7Pq17sauoBsqUXQG4mTxiw9aaqDbngdqhnrAC6CX
112jYuDR7SkoJpegcBKevJzB3qZdaeuvvKFhrkKtD9SkDfA2vrT6
11r6w7746ffLMYkVQbLbV96GZ2sdN1QAsQKhmtb8xR3HCx4bFbd
11vi2vsrGfz9jALR9oja1jQMZey9UznXko5AgJQjtCozxtEwWGT
11213mF2Ut9M9WqgwZnHBe84GHQbhrnFbJfuJnudige5eTkstbsr
112sUWEWxQAPEKwBhzay2jbWsyCpDpMqDgKctYyvWnHcYfS2i5bq
11k5je9FTsi7iZx5J64RMv5y9YJRU7m9NXwprjwcf935N4N5Jof
11Ke6f8NPFKehrEZuZYEf1wtPB2uzuH9o2ZhkmB52Q4c3Nr7XBQ
11UvGPCaCtfFBpqcpewKHxueXyfaaXnQE3AHbMoqdhBvmzZnVZW
112pKtboiEZpxxUfYFwQkemm4Kp1GxQrQ29L6P7EY9q7S9jbKP6X
112SdELT36gV4yFJDGEvCVSNdDDtwutWMwQQBNMBZBrBHpFKYevB
117JZoYEdTiPmws7CgLZhnKAWW7VpW858wyj2eXpoRHMyk99Zbi
11Uqj5GGWKAGLaFXzUamv6xj34zH3PvHGv3EZspghXnSncVeeuY
11ZbFnr1J43f8f1EhhCyVmRixJeRyEfbeCbLRSs41BrxfzSVZTW
1124R6kp74bno2XNhPZFFSJyERFF7Gf8ZuYTvpWGGSPoWnYKLyXN
1128DPLB5dLic4NaN27HbUMhokANr7QeUPmjt3Yhufmwgdg9svAK
1128MqV24Yra79C6UYL8JPdYZRMKxden6abBqUMfr8oSqubJFT2K
112fDJ9zGs74f8qsXF2S6BzN7rQkHSSycYG2PX2pZM8MP7gHD6JS
112nYcCpFzc4zrMQ1origMsV5tQ6jYyXTmRGnjoX2kiENuJDZfEB
11Aa4nkfQGNC8oZnNHEn1WvTePsYqK9zJmYa7nVjNaFEzhZk6xq
11fC14hc7kfMfySD2aQ6zz9jarRDSN5aavqPUqmaYHxiP9VLbYt
11fxGwq8C7LWtaJvnsUdwqis3RJ2hhvr4759HFK68oumuZPK71b
11wcw42xXMVNEKsJ3kgsp6z1hYpPTbaeSfktNmxyr6kuzy7tciH
11AkQy9yi3yTLD5Vzqos6XgA99iSbWXYFvh5t46BqGTGn1oxWsK
11jYJ8MuHmMrj6RaJn323ENLiHPexa2df7PcdmJcRsbHTAofS4Z
11uHruaaqniRGvc7UXSXd5T81v3iVWHE8vAAuZkKX6DR8XbfW7C
1121NvZvqiyMrj168vJ7EGHH2Lj8Me5r7wYBMcQVppyRwP28g18r
11ApYznVZe2PxR4gvHN253SvCqdeW2mgQ2arNtSkbW7PDf52EbQ
11JiZSvStzbSYaL6qSgVHRBytBEFzg67TNtEBCEwqa1dCwCFUm6
11XuC8fWetRsgWC9ySxjvdPB2qC6KutnifgSg7Q1UJf92Xa7HjY
112jKC92WcR5PZDfNYYnDPEG9vTkMQ9kBucV7wo2ogWgk32D5c58
112mwQz37CPTm8ikho7jPCkHdjNW1kghYatHeEht9nJpek74begP
112VKQBurF72r9tg7nNFM3ZQHdf7J5cjfuAv8cwtSPBHs39i5zeD
115avhE6WnLKP9jie5nkewJ1A1TiccWWCtsr4HWasjL6hDKKc3b
11BquFajeM91UVE8nSBMFpp6FhdGNWeJMbxwTk8M26w5Ciosx3G
11DabpgjvaHSCN9EFgYiyUnMaxJwc6FENeChofWKGCN1P82DXc6
11GMVa9ccPqF1McC5LzgveCGenhfkysD2UWMUZU6GN1hHHHRj9h
11syR45CiHiZ4aQeW3RWpyUzdmWjmJFTTED9hqM3bKMY22ihTBx
112WXRwFCdF17bap4thAUSo6QXH9PdRSyENRcbsiuycN4iyZqD2g
11AjLQaBWVu1Rx829ZtEzQiioU3LCiLJZiDNSNYrWyFFG5K2V1b
11LmvBSCEr8Y5wPVxtkhoirrR2E9VAv8gex45hngBDR2PE1ASRq
11M341xhxs3vPZZqbC7YqXTEh6uWMSBEdNdygCd5yHUdUnGDnB7
112rsN9t1Hpoiq6DN93x3tkfZAZHobXQ5cwYKdWkuXcvBaerS2CL
113sy9rGK51ZzXwUL2ZWGPeQTUvfcDn58UbjjWfpC6DbXSjsZWa
11kNE7xjAK6gckbPkg7SWFS2N6scgwsYhSKwim2qDJam6vL7VfF
11qHtqPDoLDSavasAVGJ5duQbXC9JEXC34xgwgKdimoq9Qvvb1Q
11Y3dR4o9grc6Yt7vhwEdJAk93S5ync59MMYnii9NQrMcWWr3Mj
11ZkHgNXLYdxYVSSVYsPUCk4vWK6VfdYY221gGvsSGHFKnNsa8F
1127iTVGcK6amrucCPyWng19t1dNdUCpEytW6EntR3bGSXhwLVwt
112ige5bHPqd1Pty8exE2KZrZFXN1FtZ645a6FwXHVoB5pi1iUVh
112m2chKUaM43GzZ7Jj7aycGeBoXX3pdQC3gXnRybfgfAciDJ9JM
112UnRej4kCbvz1VHKKEFw5NCsZzfQkGam2ZQqTYnH7yUsqXrNLj
115jkYmHAtfTn8D7vgwahPPUmhB7kMLJ8tcus4opMwGy1xQWh8V
11CgfzTYCSpMfx7G1fJJ2dSip8W1mmDDQA1buoYj85CiRmkdcG2
11eLCMpE9evCcRHht9JcoaTWoKhLBcHhXGRiZMP8ZC4VBqrDA4f
11jmS7uxDUTzKrZVKXiHUqGZBwKvmQyuq38RXZQDgFcso3tDDG9
11joYm8pdSq8B6obfmeHaCL2GCAWDDsuBA3kQ3xLsdFcgqFzWhL
112fYnHSqZxHWYuNXkiypZRsdw63sTDVjGXZUP9MCS4Bj5VRUDBJ
112nmzE1aLbCFx4TPq1uD8AaE91EPfM1j8ZoB2CoTTpkKLvenhYi
112ZCdJCsAaSwTKcPyKRHs8nCDpqokh9tDhXwDTb4CfmgZh2DisR
113rXwneyb5ts9LZ87gMUZnugz62KCAJuaDZWRwYnzN7ey7dUMa
11iDrM62wY22d9eQ2EQAAJWvSm2nFhWApx8qNC4XVas1QYE741T
1129gAArZQMwSj4Utkucyyhku5a4p1SvSw1Q9WACNJf9AgFP79Gg
112MydJiYpp4sqhcWFu1MkwifWP5WYFu1Tn4S5DMbysg9c8e4wgS
112omxxwWt35HtzdfnegbUgGySGD6gCCFt5zZGuA8xJp9QV9GHvt
112SjxxiwpYAD8Rn8yPcsNZgohEhSgeJbeA571hHCd8ps63GTae1
112UKig4H6vPN9uymQnD6isSqmfHDCPsfHNHTpQwVHV4trfUUuXf
117S4aHF26WKsXtALBTWdGKwsEM4MGED8s72GDzzFNLrbpMRdKh
119Hx7ZMDs4DfaKzF1DDUpeuNL4Zvciqgsdm2T9GfFe8x8kCjDb
11KGY9sQ5ZTnTi99i79eASjdRtwdt19rjtn1Eb2MC93K6jtB11f
11rZyZhwG7u1FETVHEo7gkKGCxTGLY8vWuhkqL4ft7MHbbASgH9
11WmiY6FTDUWwEpjmC64nZtcDUSu6b78dcdSznrrBUec1PK7CWZ
Discord Handle
No response
Reason(s)

All but 1 account for all Hummingbird gateway's didn't show any data transfers.
So data transfer is possible! only 109 out of 3853 showed packet transfer data, all these 109 are in same account.
the gateway's in that account are part of a selfwitnessing cluster so they probably all heared the same
signal.

Most of all Hummingbird gateway's witness only Hummingbird gateway's.

We iterated the witnesses of the witnesses to find the clusters.
We used the node-red server we setup for this to get the results out of api.

All HNT stolen with the total amount of 21067 HNT as by todays date/time.

We conclude that out of the 3852 gateway's we inspected only 109 gateway's in 1 account showed accidental
data transfer. so data transfer for gateway's Hummingbird is possible.

We conclude that out of the 3852 gateway's we inspected only a couple of accounts showed communication with other makers. so communication with other makers for Hummingbird gateway's is possible.

Rssi/ distance / SNR calculations are to perfect, we have found some invalids -59 dbm but we suspect they are from cables touching eachother.

We haven't targetted any maker, it was the result of a count WHERE actors1.actor_role = 'witness'
AND actors2.actor_role = 'challengee' are in same account.

 Nebra or bobcat? How about ban whole Helium.

You killed a lot of innocent nodes, garbage，Fuck you

It would help if you listed several of these hotspots here, then perhaps people could check them and provide evidence to support you showing their innocence? These issues do not automatically mean hotspots will be denylisted, if you can provide evidence showing your hotspots have been unfairly flagged then this can be acted on. If you offer no defense, then no-one can support you?

https://github.com/helium/denylist/issues/2914
https://github.com/helium/denylist/issues/3079
https://github.com/helium/denylist/issues/3414
And if you take a look what he included on denylist for deeper, a lot are not yet asserted location or simply only submitting challenge.

#2914 #3079 #3414 And if you take a look what he included on denylist for deeper, a lot are not yet asserted location or simply only submitting challenge. My friend also has a few deepers in SF just onboarded got banned.

#3414 and #3079 are deeper miners, and I would assume have been affected by the MOC action in some way. I don't understand the technical details, but it's possible they were not denylisted because of specific inclusion in any list flagged by CTH, but just because they are new Deeper HS which have their onboarding keys blocked? As such, it is probably the wrong place to aim criticism. It seems Deeper has refunded your HS and presumably your friends also?
#2914 is odd since the author mentions

a bobcat
itchy-mint-horse
112VCyMBLHyvNTcFvFUpaF4zsLiKd3nDX9bs7c1jFqmn8iHEBE9o
But this b58 address is for a different PantherX HS in the same town?
The b58 address mentioned does not appear in the CTH list https://github.com/helium/denylist/issues/2868
The name for the b58 address given by the author is:
Creamy Pewter Gibbon - which is not denied and seems to behave normally

itchy mint horse's actual b58 address is
11gMKzytezXwQfQPudyJdx75gnE6bK4SyNexEnv7GFJSs9oe718
which DOES appear on the CTH list
Checking this it does appear to have normal behaviour and it witnesses all kinds of brands, so it doesn't seem like this should have been in the CTH 2868 list - which was Deeper and PantherX self-witnessing. But there may be something I've not understood.
So it looks like it could be a mistake and should be checked.


Webhook running since 2h but stream online since seconds.

Sorry for opening so many Issues, my offer still stands ;)
Now to the bug:
tested with my own stream, but also there with other streamer.
After Stream went live the webhook says its been there since 2h or smth.

if you expand the advanced stuff with the + button, what does the "went live" say?
it's a bit odd considering the webhook duration is calculated with the start and end capture time

thats what I thought and thats also why I created that issue. almost like its running in the background or smth:

ok maybe you are right:

and as usual, working with dates and especially timezones in js is a nightmare


Support fetch tensor/dataframe using only the tileable keys

Is your feature request related to a problem? Please describe.
After #605, we can support the web session and local cluster session to fetch tensor/dataframe directly using the tileable keys.
Describe the solution you'd like

We first check if there are any GraphActor that contains in tileable, (the SessionActor already has such mapping)
When the key does not exist, raise an Exception.
For web session, return 404

Describe alternatives you've considered
Additional context
PR is coming.

TileableData.key is for private usage, at least for now. How about add the name property to TileableData just like MutableTensorData, so that we can get a tensor or DataFrame by giving a name.
Difference is that the name for tensor and DataFrame is optional, and we should ignore name when calculating key.

Thus mt.tensor(name='a') and md.DataFrame(name='a') can be used to get a tensor and DataFrame.

I don't think that adding .name to Tensor and DataFrame will benefit mars and potential users of mars. I think adding .name is bad, and makes things be in a mess. It will make things become more complicated and I think the .name property will cause a lot of confusion to users.
At the mars side, we might need to keep things as simple as possible, here the simple means consistent with numpy and pandas. That would make mars easier to be accepted by board users.
As for the feature requested in this proposal, I think we could just add some "hacks" to the fetch code path, like adding a debugging api. And we might even don't need to advertise this feature in the documentation.

I don't think that adding .name to Tensor and DataFrame will benefit mars and potential users of mars. I think adding .name is bad, and makes things be in a mess. It will make things become more complicated and I think the .name property will cause a lot of confusion to users.
At the mars side, we might need to keep things as simple as possible, here the simple means consistent with numpy and pandas. That would make mars easier to be accepted by board users.

Fair enough, I agree with this point, we should keep consistent as much as we can.

As for the feature requested in this proposal, I think we could just add some "hacks" to the fetch code path, like adding a debugging api. And we might even don't need to advertise this feature in the documentation.

OK, if users call execute or fetch, we can do the check if it's executed before, it's transparent to users that they need not sense about what key is, if we can do that, I think it's workable.

Close with #693 .


Update static code analysis tool to ktlint instead of lint

Why
Ktlint will improve our Kotlin code quality with lint checks
Once approved we can drop this issue: #182
Acceptance Criteria

Add ktlint configurations
Remove lint configurations
Update workflows
Update Dangerfile
Update README.md

Who Benefits?
This is essential because it will improve the experience of developers

@Tuubz looks like we'll need to update our .gitignore files too since ktlint wants us to update .idea/codeStyles/codeStyleConfig.xml and .idea/codeStyles/Project.xml as well 🤔 ref


[Embeddingapi] Add release mode pack

It's fine to pack release and debug mode pkg for embeddingapi cases

BUG=https://crosswalk-project.org/jira/browse/XWALK-5114

LGTM


uglify is not working

Passing the uglify: true or uglify: false or not passing the uglify flag at all has no effect on the output. The modernizr build is always output as unminified, with the following header:
/* Build http://modernizr.com/download/#-shiv-dontmin */

It's been removed.
Per the Gulp guidelines, the option to uglify the build goes against guidelines #1 and #3. Thus, this setting has been removed from this plugin. You may use gulp-uglify to achieve this functionality in Gulp:


Barriers

This PR resolves #33 by

adding barriers on all qubits with only_visual set to true

Hello @stroblme! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file tests/test_model.py:

Line 473:89: E501 line too long (96 > 88 characters)

test locally passing, not sure what's wrong here


Option to select month and year - Feature request

You can change datePickerMode.
let popupDatePickerView = AYPopupDatePickerView()
popupDatePickerView.datePickerView.datePickerMode = .date

This option gives days also. The feature that I requested is  to see the months and years in a picker and select it.


release 2.17.0-rc.3

We need a 2.17.0-rc.3 because the docker images of 2.17.0-rc.2 were not published correctly. And relaunching the job creates new tarballs that them have different checksums so it is better to simply release a new RC.
Signed-off-by: Julien Pivotto<EMAIL_ADDRESS>

And relaunching the job creates new tarballs that them have different checksums so it is better to simply release a new RC.

You should have been able to delete the tarballs from the release page. Or am I missing something? Anyway that's not a big deal, I agree.

And relaunching the job creates new tarballs that them have different checksums so it is better to simply release a new RC.

You should have been able to delete the tarballs from the release page and relaunch the CI workflow. Or am I missing something? Anyway that's not a big deal, I agree.

I sent the announcement and published the github release already. I did not want two releases with different sha1 but same version to be published.


[5.0.0-alpha.2] Typo in the release note

In the code snippet, it should be
import {NavigationRoute} from 'workbox-routing/NavigationRoute.mjs'

Updated—thank you!


Gas probleme

Hi,
I am getting this error when trying to buy an order . It seems to struggle with gas:
cannot estimate gas; transaction may fail or may require manual gas limit [ See: https://links.ethers.org/v5-errors-UNPREDICTABLE_GAS_LIMIT ] (reason="execution reverted", method="estimateGas", transaction={"from":"0x9f3752cd801fD513dAD4200aD08EA6b9d149C6Cd","to":"0x00000000006c3852cbEf3e08E8dF289169EdE581","value":{"type":"BigNumber","hex":"0x12795f58d50000"},"data":"0xfb0f3ee1000000000000000000000000000000000000000000000000000000000000002000000000000000000000000000000000000000000000000000
. I am using truffle/hd wallet. Any idea where it could come from?

Getting the same error using ethers, following the exact code in the documentation. Apparently the error can mask another, underlying error: since the gas estimation simulates the transaction, it will fail if the transaction fails.
The code below replicates the error (wallet address, api key, and private key are hidden here). Filename is *.mjs
`
import { Seaport } from "@opensea/seaport-js";
import { ethers } from "ethers";
// Provider must be provided to the signer when supplying a custom signer
const provider = new ethers.providers.JsonRpcProvider(
"https://eth-mainnet.g.alchemy.com/v2/ALCHEMY_API_KEY"
);
const signer = new ethers.Wallet("WALLET_PRIVATE_KEY", provider);
const seaport = new Seaport(signer);
const offerer = "WALLET_ADDRESS";
const { executeAllActions } = await seaport.createOrder(
{
offer: [
{
amount: ethers.utils.parseEther("0.001").toString(),
// WETH
token: "0xc02aaa39b223fe8d0a0e5c4f27ead9083c756cc2",
},
],
consideration: [
{
itemType: 2,
token: "0x8a90cab2b38dba80c64b7734e58ee1db38b8992e",
identifier: "1",
recipient: offerer,
},
],
},
offerer,
);
const order = await executeAllActions();
`

I am also getting same error of
 reason: 'cannot estimate gas; transaction may fail or may require manual gas limit',   code: 'UNPREDICTABLE_GAS_LIMIT',
I don't know what is an error here
`const { Seaport } = require("@opensea/seaport-js");
const { ethers } = require("ethers");
const { data } = require("./details.json");
// Provider must be provided to the signer when supplying a custom signer
const provider = new ethers.providers.JsonRpcProvider(
data.apiKey.goerli.infura.url
);
const signer = new ethers.Wallet(data.accounts.acc1["private-key"], provider);
const seaport = new Seaport(signer);
/// offering nad fullfillin it
const offerer = data.accounts.acc1.address;
const fulfiller = data.accounts.acc2.address;
async function main() {
console.log("creating order !");
const { executeAllActions } = await seaport.createOrder(
{
offer: [
{
itemType: 2,
token: data.contract.goerli.nft,
identifier: "0",
},
],
consideration: [
{
amount: ethers.utils.parseEther("0.1").toString(),
recipient: offerer,
},
],
},
offerer
);
console.log("created order success");
const order = await executeAllActions();
console.log("order : ", order)

const { executeAllActions: executeAllFulfillActions } =
    await seaport.fulfillOrder({
        order,
        accountAddress: fulfiller,
    });

const transaction = await executeAllFulfillActions();

console.log("transaction success");
console.log(transaction);

}
main();`

I have solved that problem by changing the provider and sometimes it runs but sometime it doesn't.


Fix Confluent Schema Registry client

As per @jonarcher:

Original implementation was getting the schema id and using it as the
version. This made deserialization fail since it would endeavor to
retrieve the schema by version using the id value.

This fix (maybe accidentally) broke the registration of a new schema. See https://github.com/spring-cloud/spring-cloud-stream/commit/b1285c3d4aa994ae65094c5dac1aca894d7438a5#commitcomment-22493861


Added note about process interaction with container in detached mode

Fixes #13595
@moxiegirl pls take a look when you have time and let me know if it looks good or I need to make any changes.

@moxiegirl I've submitted the PR again with the changes discussed above.

@dharmit Thank you! LGTM @thaJeztah @docker/docs-owners

LGTM thanks @dharmit !


Consistent assertion formatting

Doing so wraps the error message in the color format string for the
error title, so that if the error message title were set to another
color code, e.g. '31;1' (bright red), that would leak into the error
message.
Also there was an extra newline before the error message when showing a
diff that wouldn't appear when there is no diff.
Before:

After:

@avdd Thanks!  Can you please sign the CLA?


Digging deeper i found that sendFileImpl(...) (in Socket+File.swift) returns -1 after calling write(...) and the posix ERRNO is set to "Broken Pipe".
When trying to read the same file directly from Swift using the FileManager everything is ok, so no missing file or permission should be the cause.
Work perfectly on:
iPhone X @ iOS 12.1.4
iPhone XS @ iOS 12.1.1
Always returns error on:
iPad Mini 2 @ iOS 10.0.1
iPad Mini 2 @ iOS 11.0
iPad Mini 4 @ iOS 12.2

Hey, @megakode Thanks for reporting this. Can you please run the SwifterSampleiOS in your iPad Mini x @ iOS x.x to see the result there when the route/files/:path is requested? Unfortunately, I don't have that specific device to run it myself.

@Vkt0r you don't need Ipad Mini  just send large file i.e 30MB or 100MB

I got this error too and use Google to read something about "broken pipe" issue.
Even IBM-Swift/Kitura got this issue as is sock
https://github.com/IBM-Swift/Kitura/issues/594
This issue are also replicated on simulator

just try to delay request and disable keepalive on my client maybe that solve this issue
similar on swift python https://stackoverflow.com/questions/24327239/python-swiftclient-broken-pipe-in-requests

maybe that help add to signal(SIGPIPE, SIG_IGN);
https://github.com/httpswift/swifter/blob/f043c24abc6df1f834731b1a9081c6901b59870c/XCode/Sources/Socket.swift#L225
https://stackoverflow.com/questions/30799296/what-does-signalsigpipe-sig-ign-do


Make room for the word username on the onboarding screen

Interesting. What device (or simulated device) is your screenshot on?
I'll try it again with the latest version of develop.

Yep, it's working now!


Not able to run multi-agent demo(e.g. two diggers or MultiMaze) on one machine

I tried to run the multi-agent demo with following steps.

Launch 2 Minecraft clients with port 10000 and 10001
Run MultiMaze.py with role 0 and role 1

However, once I run the role 1 the role 0 seems just halt, and when role1 was shut down the role0 came back. It looks like the running mission never begins.
log of role 0:
python MultiMaze.py
Will run as role 0
Mission 0 --- starting at 0, 200, 0
Waiting for the mission to start....................................................................................................................................................
TimestampedString: 2017-Apr-04 19:07:59.612649, Mission ended abnormally: From Gertrude: Lost contact with the agent
Mission was aborted by server: From Gertrude: Lost contact with the agent
Mission has stopped.
Sleeping to give the clients a chance to reset... done.
Mission 1 --- starting at 32, 200, 0
Waiting for the mission to start...........................................^CTraceback (most recent call last):
File "MultiMaze.py", line 165, in
time.sleep(0.1)
KeyboardInterrupt
log of role 1:
python MultiMaze.py --role 1
Will run as role 1
Mission 0 --- starting at 0, 200, 0
Waiting for the mission to start.............................................................................................................................................................^CTraceback (most recent call last):
File "MultiMaze.py", line 165, in
time.sleep(0.1)
KeyboardInterrupt

Am closing this as I believe it's a dupe of #420.


add stable error messages to html5lib

The errors are there already, we just need to convert them to code_transformers's style error messages, so we can post more details in the error/warning page.

This issue has been moved to dart-lang/polymer-dart#467.


A question about the dataset

Thank you for your excellent work!
When I create the dataset following the instructions, I met some problems. Therefore I want to konw could you share the final file data?
Thank you very much!

Have you solved your problems?
I also met problems about the dataset,
the comvert_mvsec file import the pakages: bag_indexer，calibration and downloader, do you know where can i find the three pakages.
Thank you very much!

These three files are in MVSEC files, maybe because you didnot create soft link or you can add sys.path.append()to import them

These three files are in MVSEC files, maybe because you didnot create soft link or you can add sys.path.append()to import them

I have already created the soft link, ln -s /event_stereo_ICCV2019/tools/convert_mvsec.py conert_mvsec.py, but I still met some problems, how can I solve it? Thanks!
Traceback (most recent call last):
  File "tools/convert_mvsec.py", line 51, in <module>
    import bag_indexer
ImportError: No module named bag_indexer

Have you solved your problems?
I also met problems about the dataset,
the comvert_mvsec file import the pakages: bag_indexer，calibration and downloader, do you know where can i find the three pakages.
Thank you very much!

Hello, Do u have the final dataset, I am converting the MVSEC but it takes really long time, I don't know why

Have you solved your problems?
I also met problems about the dataset,
the comvert_mvsec file import the pakages: bag_indexer，calibration and downloader, do you know where can i find the three pakages.
Thank you very much!

Hello, Do u have the final dataset, I am converting the MVSEC but it takes really long time, I don't know why

Hi @AllenZyy821 , have you convert the MVSEC sucessfully? Due to the virtual linux system limitation, it seemed a lit bit difficult to create the virtual ROS env. Can you share the processed MVSEC dataset? Thx a lot!


Help

Hi, any idea why it keeps restarting? Great product btw, thanks mate!

Seems like the format of Go boolean flags changed sometime in the last few years, and instead of —nohttp in the Dockerfile, it should be —http=false.
Do you mind trying that and telling me if it works?

5cc5ebaefaedd2f754c1c6780350b5f0abbeedc9

Should work now. :) Thanks for the report.


Update Develocity plugin to 3.17.3

@bot-gradle test this

I've triggered the following builds for you. Click here to see all build failures.

PullRequestFeedback build

I am off for the next week, so please merge when ready.


[Bug]  Order Button code Doesnt work

Describe the bug
When i go to settings and the press ORDER BUTTON

It doesnt generate any code for my site

This worked on BoxBilling
How to reproduce

Go to settings
Press Order Button
you wont see any code

Expected behavior
I need to set the code there for you
Screenshots
No response
FOSSBilling version
Latest Stable
Module version
No response
Device
No response
Information
No response
Additional context
No response

Spectrum *** that has been removed but not completely

Fixed


Changing Remove User By Email to Remove User By ID

Changed all occurances of remove user by email to remove user by ID.
Works from my testing, but would appreciate someone else also testing.
eggs

i will get this merged this weekend


typos

Removed stray characters from DNS heading.
Corrected mislabeling of Converged Network Interface Card (NIC) link as High-Performance networking and changed hr tags to br tags.
Removed extra line return in Windows Container Networking causing tags to be visible on page.

@itbland Please resolve the merge conflict before I merge.

Done


Configure nav and footer links

Point all the dummy links to current page (instead of 404ing).
Translate their texts.
Closes #30

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@3168138). Click here to learn what that means.
The diff coverage is 100%.

@@           Coverage Diff            @@
##             master     #32   +/-   ##
========================================
  Coverage          ?   62.5%
========================================
  Files             ?      20
  Lines             ?     240
  Branches          ?       0
========================================
  Hits              ?     150
  Misses            ?      90
  Partials          ?       0

Impacted Files
Coverage Δ

omahelsinki/context_processors.py
0% <ø> (ø)

omahelsinki/tests/test_dummy.py
100% <100%> (ø)

omahelsinki/settings.py
85.24% <100%> (ø)

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 3168138...2e67a6e. Read the comment docs.


Point Docs link to https://mockingbird-docs.tinybird.co/

The UI link is correct - there should be a rewrite of https://mockingbird-docs.tinybird.co/ to go to mockingbird.tinybird.co - the problem is the rewrite isn't working


Performance - Test with the usage of virtual memory

Overflow physical memory when there is a swap.

We should test various hardware configurations.


Middle mouse button click event does not always fire.

Steps to reproduce
@Override
public boolean onTouchEvent(@NonNull MotionEvent event) {
    if (event.getButtonState() == MotionEvent.BUTTON_TERTIARY) {
        Log.d("MOUSE", "BUTTON_TERTIARY");
    }

    return super.onTouchEvent(event);
}

✔ Expected Behavior
The event should always fire.
❌ Actual Behavior
The event does not fire often.
Other Software
No response
Please specify the version of Windows Subsystem for Android
2208.40000.5.0

I realized that my mouse is defective.


v6.2.0 installs files directly under site-packages

README.md and CHANGELOG.md should not be installed directly under site-packages.
This patch fixes the issue:
--- pyproject.toml.orig	2024-04-26 20:03:26.188129942 +0000
+++ pyproject.toml
@@ -4,7 +4,6 @@ version = "6.2.0"
 description = "Fixes mojibake and other problems with Unicode, after the fact"
 authors = ["Robyn Speer<EMAIL_ADDRESS> license = "Apache-2.0"
-include = ["README.md", "CHANGELOG.md", "tests"]
 readme = "README.md"

 [tool.poetry.dependencies]

Merged the fix, thanks.


Colon in end-time strings in PKD mth5

This likely will need to be addressed in mth5. This issue was encountered while working on issue #153.  Specifically, when migrating the Parkfield tests to use the new Processing config based on mt_metadata.
The flow is:
1 Start with the mth5
2 extract the channel summary
3. cast channel summary as a dataframe,
4. select runs and remote references
5. Generate Processing() config
6. Call processing
Step 3 is where I am getting an issue.  The extraction of channel summary works fine, but when trying to represent the channel summary as a dataframe the .to_dataframe() method loops over the columns, casting them to appropriate dtypes.  The start column is handled properly, casting strings of the form:
2004-09-28T00:00:00+00:00
to datetimes, using
pd.to_datetime(df.start.str.decode("utf-8"))
Out[16]:
0   2004-09-28 00:00:00+00:00
1   2004-09-28 00:00:00+00:00
2   2004-09-28 00:00:00+00:00
3   2004-09-28 00:00:00+00:00
4   2004-09-28 00:00:00+00:00

but the end column has strings of the form:
df.end.str.decode("utf-8")
Out[19]:
0    2004-09-28T01:59:59.950000+00:
1    2004-09-28T01:59:59.950000+00:
2    2004-09-28T01:59:59.950000+00:
3    2004-09-28T01:59:59.950000+00:
4    2004-09-28T01:59:59.950000+00:

N.B. The colons at the end of these strings
Initially I thought the issue was the milliseconds, but actually, it seems like its due to the colons at the end of the strings.  viz the following from the  command line:
pd.to_datetime(df.end.str.decode("utf-8")[0][:-1])
Out[5]: Timestamp('2004-09-28 01:59:59.950000+0000', tz='UTC')

i.e. If I pass the string in with all but the colon stripped off, things work fine ...
So, the questions are:

Where is the colon coming from?
Can we fix that in the ingest?
Should a try/except be added to see if the string has a colon at the end, and then strip it and try again ...

I will dig into question 1

To reproduce this, you need to have the parkfield data locally
(if you don't have it
python make_parkfield_mth5.py

from aurora/tests/parkfield/.
Once you have the mth5, then you can run:
python aurora/tests/parkfield/make_processing_configs_new.py

to reproduce the error

Here is the output from station_traces on line 79 of tests/parkfield/make_mth5_helpers
Everything looks healthy with the timestamps
[BK.PKD..BQ1 | 2004-09-28T00:00:00.000000Z - 2004-09-28T01:59:59.950000Z | 40.0 Hz, 287999 samples,
 BK.PKD..BQ2 | 2004-09-28T00:00:00.000000Z - 2004-09-28T01:59:59.950000Z | 40.0 Hz, 287999 samples,
 BK.PKD..BF1 | 2004-09-28T00:00:00.000000Z - 2004-09-28T01:59:59.950000Z | 40.0 Hz, 287999 samples,
 BK.PKD..BF2 | 2004-09-28T00:00:00.000000Z - 2004-09-28T01:59:59.950000Z | 40.0 Hz, 287999 samples,
 BK.PKD..BF3 | 2004-09-28T00:00:00.000000Z - 2004-09-28T01:59:59.950000Z | 40.0 Hz, 287999 samples]

but the mth5_obj is showing the colons in the end column
(scroll to the right in the blurb below to see the end column)
mth5_obj.channel_summary
Out[5]:
index | survey | station |  run   | latitude | longitude | elevation | component |            start             |                end                | n_samples | sample_rate | measurement_type | azimuth | tilt |       units       |     hdf5_reference      |   run_hdf5_reference    | station_hdf5_reference
-------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
  0   |  BK   |  PKD   |  001   | 35.94517 | -120.5416 | 583.0 |  ex   |  2004-09-28T00:00:00+00:00   |  2004-09-28T01:59:59.950000+00:   | 287999 | 40.0 |  electric   | 77.6  | 14.4 |  Digital Counts   | <HDF5 object reference> | <HDF5 object reference> | <HDF5 object reference>
  1   |  BK   |  PKD   |  001   | 35.94517 | -120.5416 | 583.0 |  ey   |  2004-09-28T00:00:00+00:00   |  2004-09-28T01:59:59.950000+00:   | 287999 | 40.0 |  electric   | 172.6 | -8.1 |  Digital Counts   | <HDF5 object reference> | <HDF5 object reference> | <HDF5 object reference>
  2   |  BK   |  PKD   |  001   | 35.94517 | -120.5416 | 583.0 |  hx   |  2004-09-28T00:00:00+00:00   |  2004-09-28T01:59:59.950000+00:   | 287999 | 40.0 |  magnetic   | 87.0  | 0.0  |  Digital Counts   | <HDF5 object reference> | <HDF5 object reference> | <HDF5 object reference>
  3   |  BK   |  PKD   |  001   | 35.94517 | -120.5416 | 583.0 |  hy   |  2004-09-28T00:00:00+00:00   |  2004-09-28T01:59:59.950000+00:   | 287999 | 40.0 |  magnetic   | 177.0 | 0.0  |  Digital Counts   | <HDF5 object reference> | <HDF5 object reference> | <HDF5 object reference>
  4   |  BK   |  PKD   |  001   | 35.94517 | -120.5416 | 583.0 |  hz   |  2004-09-28T00:00:00+00:00   |  2004-09-28T01:59:59.950000+00:   | 287999 | 40.0 |  magnetic   |  0.0  | 90.0 |  Digital Counts   | <HDF5 object reference> | <HDF5 object reference> | <HDF5 object reference>

and the colons are in the summary strings, so I think this is happening in mth5

So, Iterating through create_from_server_multistation, updating the channel summary and visualizing at each line, I find that the channel summary changes (to the offending form with : ) upon execution of:
run_group.from_runts(run_ts_obj)

And just got blocked in debugging by issue #159, will try again later, but the plan is to step though
the function from_run_ts() around line 88 of
create_from_server_multistation

This is fixed from Jared's update to mth5 - the trick was to change the length of the timestamp strings from 30 to 36.


Android - Devices getting disconnected while face auth

Describe the bug
Devices getting disconnected while face auth intermittently
To Reproduce
Prerequisite: have VC downloaded in the wallet

open the scanner on the wallet
open qr code in the verifier
Select a VC in your wallet and click on face auth
perform face auth

Expected behavior
The transfer should work properly without any interruption
Actual behavior
The devices go disconnected, this issue I faced intermittently for 3 times in 25 attempts
Screenshots

Add the screenshot of the profile page with commit id

Smartphone:
Wallet :
device : 7A
BLE version : 4.2
OS version : Android 10
Verifier :
device : Samsung A03
BLE version : 4.2
OS version : Android 11
MOSIP Version: <IP_ADDRESS>
MOSIP server: qa-1201-b2.net
APP link : https://github.com/mosip/inji/actions/runs/4555460456

verified as fixed in the build with commit id in the below screenshot.


Next.js 13.4.5 breaks getServerSideProps instrumentation

Description
#128 was opened to skip verisons > 13.4.5 of Next.js.  I can't seem to figure out why but the renderHTML instrumentation is no longer getting called when running getServerSideProps calls.
Steps to Reproduce

Undo #128
Run npm run versioned:major

Expected Results
All versioned tests pass
Actual Result
Failures exist in attributes.tap.js like this

Yet another Next.js refactor.  https://github.com/vercel/next.js/pull/50404/files#diff-6f4291cc2bfc5073fdca12a014011769e840ee68583db1468acef075f037015aR1773.  The function we need to instrument, render, isn't available at runtime as it's bundled with the app.  We've discussed as a team this might be the time to figure out how to properly inject our agent at build time so it can instrument functions during bundling.


Trinity oauth backend

 (4) Trinity: SSO - steps before go to production

@tkeemon Great catches, all requested changes addressed!