[Poll]: Configuration of corobo

Since corobo lives inside a Docker container and is deployed after every commit.
To use the configuration templates, we'll need a way to pre-configure the plugins so that bot admins don't have to configure them after every deployment.
In the comment section, are the different proposed option than can be implemented to auto-configure the plugins at the time of deployment.
Please use a ' :+1:  ' to vote for the best-suited implementation.
cc @meetmangukiya @gbin @jayvdb

Option 1
Simple use of environment variables in the configuration templates. Eg:
    def get_configuration_template(self):
        config = {
           'CROSSLINK_GITHUB_TOKEN': os.getenv('GITHUB_TOKEN'),
           'CROSSLINK_GITLAB_TOKEN': os.getenv('GITLAB_TOKEN'),
           'CROSSLINK_OPENHUB_TOKEN': os.getenv('OPENHUB_TOKEN'),
        }
        return config

Downside: Environment variables on windows are hard to set & change.

Option 3
@jayvdb 's workaround https://github.com/coala/corobo/issues/380#issuecomment-391575383
    def get_configuration_template(self):
        config = {
           'CROSSLINK_GITHUB_TOKEN': '',
           'CROSSLINK_GITLAB_TOKEN': '',
           'CROSSLINK_OPENHUB_TOKEN': '',
        }

        for key in config:
            if hasattr(self.bot_config, key):
                config[key] = getattr(self.bot_config, key)

        return config

    def _get_config(self, key):
        if self.config and key in self.config:
            return self.config[key]
        return getattr(self.bot_config, key, None)

We could put something similar into a super class for all our plugins.

Option 4
We can store the configuration dictionary in a seperate file default_configs.py which can be mounted to the docker container using docker volumes. The content of the file would be the configurations for the plugins. Eg:
CONFIG = {'configs': {'LabHub': {'TOKEN': 'abc123'}, 'WolframAlpha': {'TOKEN2': 'abc123'}}}

Using a pythin script from inside the container we can import CONFIG from default_configs.py and configure the bot before it is deployed by executing  Errbot's Provisioning command
errbot --storage-set core <CONFIG>
and then deploy the bot after it is configured.

Option 5
By keeping the data/ dir outside the docker container and mounting it instead, we can take advantage of Errbot's storage.
We'd have to set BOT_DATA_DIR in config.py to the path of the mounted data dir.
Currently BOT_DATA_DIR = os.path.join(BOT_ROOT, 'data') where BOT_ROOT is the absolute path of the project root.

data/ directory is just errbot's shelf storage, it can not even be existing if we use another database, redis, postgres, etc.

Do not consider / assume that this thing will be running inside Docker. If the goal is to have the project reusable outside of coala, don't make decision that could make it unusable for people outside of coala (exp. Not using Docker, Not using Linux, etc).
I believe using environment variables to configure should be considered a cheap hack in comparison to a proper setup. I would prefer if it uses something like Python's built-in ConfigParser and just read it from there. Environment variables can be used to generate the file at the start or have an option to always update it.
I suggest adding command line arguments for --config-file and --data-dir to make it easier to declare where those directories are located.
If it isn't declared try the following in order:

For the config file:

$(pwd)/corobo.ini
$XDG_CONFIG_HOME/corobo/config.ini
$HOME/.corobo/config.ini
/etc/corobo/config.ini
/etc/corobo.ini

For the data directory:

$(pwd)/data
$XDG_DATA_HOME/corobo
3 $HOME/.corobo/data

First, check if there's an exisiting config file and data directory
Second, if they don't exist, use the first one on the list
Third, if it fails (because of permission issue, etc), Fail and print config file and data directory does not exist and corobo cannot make them. Please declare --config-file and --data-dir if you're planning to use a different location. See --help for more details

fwiw, the runtime config was finished in https://github.com/coala/corobo/pull/597


PR to add a message if user attempts an unsupported search

Display a message if a user attempts to make a search for "wikidata.org" as the project.
Phabricator task: T207367

Thanks, I have made the suggested changes.

Looks good - thanks!


Error with staticfiles collection and missing source map files

What happened?
When I ran collectstatic on my production server, I get this error:
Traceback (most recent call last):
  File "/tmp/8daedd4f753e458/manage.py", line 31, in <module>
    execute_from_command_line(sys.argv)
  File "/tmp/8daedd4f753e458/antenv/lib/python3.10/site-packages/django/core/management/__init__.py", line 446, in execute_from_command_line
    utility.execute()
  File "/tmp/8daedd4f753e458/antenv/lib/python3.10/site-packages/django/core/management/__init__.py", line 440, in execute
    self.fetch_command(subcommand).run_from_argv(self.argv)
  File "/tmp/8daedd4f753e458/antenv/lib/python3.10/site-packages/django/core/management/base.py", line 414, in run_from_argv
    self.execute(*args, **cmd_options)
  File "/tmp/8daedd4f753e458/antenv/lib/python3.10/site-packages/django/core/management/base.py", line 460, in execute
    output = self.handle(*args, **options)
  File "/tmp/8daedd4f753e458/antenv/lib/python3.10/site-packages/django/contrib/staticfiles/management/commands/collectstatic.py", line 209, in handle
    collected = self.collect()
  File "/tmp/8daedd4f753e458/antenv/lib/python3.10/site-packages/django/contrib/staticfiles/management/commands/collectstatic.py", line 154, in collect
    raise processed
whitenoise.storage.MissingFileError: The file 'js/popper.js.map' could not be found with <whitenoise.storage.CompressedManifestStaticFilesStorage object at 0x7851a54578b0>.

The JS file 'js/vendors.js' references a file which could not be found:

  js/popper.js.map

Please check the URL references in this JS file, particularly any
relative paths which might be pointing to the wrong location.

The error comes because popper.js has this comment:
//# sourceMappingURL=popper.min.js.map

But popper.min.js.map is not copied into the static files directory.
This general issue is reported as an issue in Django 4.1:
https://code.djangoproject.com/ticket/33353#comment:15
And there was a fix to django-rest-framework to add source map files:
https://github.com/encode/django-rest-framework/pull/8591
I am not sure why I am seeing this in Django 4.0.8, since it's supposedly a 4.1 issue, but perhaps 4.0.8 manifests an earlier version of the issue.
Proposed fix
This is the change I made to my repo:
https://github.com/pamelafox/cookiecutter-django-output/commit/c5e8166e40fb8c87f1ce11849ef246f98a52b6f5
I modified the gulpfile to copy over the *.map files for the vendor files, and add *.map to the gitignore file.
I can submit that as a pull request to this repository if it seems like a helpful change.
Additional details
This is the repository I deployed:
https://github.com/pamelafox/cookiecutter-django-output/tree/961a1ebfd226ec1aa0726760e4c2fd46b7bc0840
I deployed using the 'azd up' command to Azure App Service (using infrastructure files I wrote myself), and I found the error in the deployment center logs.
I do not seem to get the error when I run manage.py collectstatic locally.

Thanks for the detailed bug report and suggested fix. That's a bit weird, I don't remember seeing an error like this before...
Do you remember which options you have selected when generating? I see frontend_pipeline=Gulp, docker=n, whitenoise=y and Cloud provider=Azure. I think the error is specific to Gulp + Whitenoise?

Here's my configuration - it does use Gulp + Whitenoise, yep. I would think it would happen without Gulp too, if Whitenoise tries to server popper.js, but maybe not, still a little fuzzy on static asset compilation.
The strange thing is how it happens in my prod environment and not locally. I'd expect it to always happen in Django 4.1 (based on the django ticket), so if I have time today I'll see if I can upgrade and replicate it locally.
project_name [My Awesome Project]:
project_slug [my_awesome_project]:
description [Behold My Awesome Project!]:
author_name [Daniel Roy Greenfeld]: pamela fox
domain_name [example.com]: pamelafox.org
email<EMAIL_ADDRESS><EMAIL_ADDRESS>version [0.1.0]:
Select open_source_license:
1 - MIT
2 - BSD
3 - GPLv3
4 - Apache Software License 2.0
5 - Not open source
Choose from 1, 2, 3, 4, 5 [1]: 1
timezone [UTC]:
windows [n]: n
use_pycharm [n]: n
use_docker [n]: n
Select postgresql_version:
1 - 14
2 - 13
3 - 12
4 - 11
5 - 10
Choose from 1, 2, 3, 4, 5 [1]: 2
Select cloud_provider:
1 - AWS
2 - GCP
3 - Azure
4 - None
Choose from 1, 2, 3, 4 [1]: 3
Select mail_service:
1 - Mailgun
2 - Amazon SES
3 - Mailjet
4 - Mandrill
5 - Postmark
6 - Sendgrid
7 - SendinBlue
8 - SparkPost
9 - Other SMTP
Choose from 1, 2, 3, 4, 5, 6, 7, 8, 9 [1]: 9
use_async [n]: n
use_drf [n]: n
Select frontend_pipeline:
1 - None
2 - Django Compressor
3 - Gulp
Choose from 1, 2, 3 [1]: 3
use_celery [n]: n
use_mailhog [n]: n
use_sentry [n]: n
use_whitenoise [n]: y
use_heroku [n]: n
Select ci_tool:
1 - None
2 - Travis
3 - Gitlab
4 - Github
Choose from 1, 2, 3, 4 [1]: 4
keep_local_envs_in_vcs [y]: y
debug [n]: y
 [INFO]: .env(s) are only utilized when Docker Compose and/or Heroku support is enabled so keeping them does not make sense given your current setup.
 [SUCCESS]: Project initialized, keep up the good work!

In production, the file popper.js.map isn't needed right? In my case it is referenced from vendors.js and not vendors.min.js.
My workaround was by adding --ignore=js/vendors.js to collectstatic so it isn't processed anyway.

I don't believe the default UI uses it, but it would be needed if the website actually utilized one of the Bootstrap JS widgets that rely on popper, so it would become an issue at that point.

Update: I was able to replicate this on my local server (keeping Django 4.0.8) by copying the production setting to settings/local:
STATICFILES_STORAGE = "whitenoise.storage.CompressedManifestStaticFilesStorage"


[Feature Request]: ${selectedPath} predefined variable

I use the ${file} variable for tasks to launch tests on specific files.  But sometimes I'd like to launch tests on a directory.  It would be nice if there were a ${selectedPath} predefined variable that would resolve to the file or folder I've selected in the explorer.
I guess it would have to produce an error if multiple paths are selected.  It would be cool if there's somehow a way to pass multiple selected paths to tasks, but I'm not sure how that would work, VSCode would have to magically explode "args": ["${selectedPaths}"] into multiple array elements or something.

This feature request is now a candidate for our backlog. The community has 60 days to upvote the issue. If it receives 20 upvotes we will move it to our backlog. If not, we will close it. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

This feature request has not yet received the 20 community upvotes it takes to make to our backlog. 10 days to go. To learn more about how we handle feature requests, please see our documentation.
Happy Coding!

:slightly_frowning_face: In the last 60 days, this feature request has received less than 20 community upvotes and we closed it. Still a big Thank You to you for taking the time to create this issue! To learn more about how we handle feature requests, please see our documentation.
Happy Coding!


Wrap bare URIs

Description / Summary
mdformatted output can violate Markdownlint rule MD034 - Bare URL used. I know that the CommonMark Spec section 6.5 Autolinks allows bare URIs and specifies that they not be treated as autolinks, but that's not relevant — I agree with MD034 and I want & need my formatter to wrap bare URIs with angled brackets — otherwise, I will have to do it by hand.
Value / benefit
The value of this is automating a time-consuming and error-prone manual process, i.e. fulfilling the purpose of a formatter.
Implementation details
I guess that maybe_add_link_brackets() or its calling function link() will have to be modified to take bad guess. Still, a configurable option will be required like wrap_bare_URIs which defaults to False (current behaviour) but always wraps bare URIs with < and > when True.
Tasks to complete

[ ] find out where bare URIs are to be found and work out how to detect them for wrapping.

Thanks for the issue, but this isn't something that mdformat can or should make. Adding angle brackets will change rendered HTML so is not a matter of style but content. You'll have to add the brackets manually unfortunately.

How do you imagine manual changes will be made when mdl runs automatically in a CI pipeline?

I don't think this is something that can safely be automated. There's no way for mdformat to tell which whether you want the angle brackets or not, and as I mentioned, it isn't a matter of style, Markdown AST and rendered HTML is different.

I'm suggesting that this be a configurable option with the status quo remaining as the default. It's obvioulsy safe to apply configured behaviours automatically.
This is a matter of style, as fully described in MD034. The point of style rule MD034 is to achieve consistent HTML output no matter which renderer was used; the point is to change the Markdown source to achieve that. I happen to agree with that style rule, and I think it's fair to say that it's highly likely that many other people do also.
I'd prefer to not discuss the merits of this suggestion in a closed bug, I trust you appreciate that I have no choice or power in that respect.

This is a matter of style

It's not however. The renderings are visually different.

The point of style rule MD034 is to achieve consistent HTML output no matter which renderer was used

Mdformat is a CommonMark compatible formatter. It doesn't care non compliant renderers.

I happen to agree with that style rule, and I think it's fair to say that it's highly likely that many other people do also.

I also agree with it but only because it is the only way to make an autolink in CommonMark. Without the angle brackets it's not an autolink. Again this is not a matter of style. Mdformat has no way of knowing if someone actually doesn't want an autolink. So you'll need to add the brackets manually.

I'd prefer to not discuss the merits of this suggestion in a closed bug

I'm sorry you feel that way, but the suggestion goes around the documented fundamentals of mdformat, so it's a very clear case for me, whether configurable or not.

Oh and btw I do encourage making a plugin that does this, that's exactly what the plugin API is there for. I can also answer questions regarding plugin development. Essentially you'll need to override the renderer for text elements, use a link detection library (linkify-it-py) to detect links and add the brackets to convert to an autolink.

Thanks, that looks promising and I'll give it a try as soon as I can. Packaging this along with the other configuration options I've drafted would create a coherent plugin.


Add Kotlin coroutine support.

Similarly to lce-rxjava3, add lce-coroutines module.

+1

Added in https://github.com/Laimiux/lce/pull/43 (will be published as part of 0.4.0)


mgmt/mcumgr/lib: Remove flash_area_open_ex

The function is no longer neede with fix provided by commit
aa5d20aaef (storage/flash_map: Return -ENODEV from flash_area_open).
Signed-off-by: Dominik Ermel<EMAIL_ADDRESS>

Rebased to fix CI failure

Thanks.

Typo in commit message *needed

@lairdjm  Fixed typo.

Hmm seems the commit message hasn't been updated


Made minor corrections (screenshots, wordings, code snippets) to the …

…Micronaut OCI ATP lab.
Add here your WMS ID: 11217
General requirements

Information in the workshop is adequate and updated
Code is correct and working
Links are correct
Make sure you enter the help email link in your manifest.json
Please make sure WMS URLs are updated as needed after your PR is approved

Checklist - Refer to the QA document for the complete list
Please confirm that the following is completed before submitting your PR

[ ] All filenames are lower case (including folders, images, files, etc.)
[ ] Filenames are descriptive
[ ] Your workshop folder structure should be similar to the one used in the sample workshop (https://github.com/oracle-livelabs/common/tree/main/sample-livelabs-templates/sample-workshop)
[ ] Are you using multiple versions (desktop/, sandbox/, tenancy/)? Make sure that each of them contains a manifest.json and an index.html
[ ] Image references in markdown contain an alternate text

Hi @kamryn-v, I have updated the PR with the WMS ID.


Add reminder to install django-querysetsequence

This mirrors the reminder elsewhere in the documentation "# don't forget to pip install djhacker".  Several issues have been started in the past due to the error that's caused by forgetting (or not understanding) that this isn't installed by default.  e.g. #971.  Just happened to me now.

Thanks!

Also, note that if you pip install django-autocomplete-light[gfk] then it will pull django-querysetsequence


APIM-3989: Angular Migration: Settings > Portal > API Portal Information

Issue
https://gravitee.atlassian.net/browse/APIM-3989
Description
Page + Components + Services migration from Angular 1 to Angular 16
Improvements in UI
New Unit Tests to functionality
Additional context

📚  View the storybook of this branch here

🏗 Your changes can be tested here and will be available soon:
Console: https://pr.team-apim.gravitee.dev/6483/console
Portal: https://pr.team-apim.gravitee.dev/6483/portal
Management-api: https://pr.team-apim.gravitee.dev/6483/api/management
Gateway v4: https://pr.team-apim.gravitee.dev/6483
Gateway v3: https://pr.gateway-v3.team-apim.gravitee.dev/6483

In your commits, you specify "cockpit", but the changes are in the console project. You can change "cockpit" -> "console".


'Upload block blob' displays in the context menu of premium blob container

Repro Steps:

Expand one premium storage account.
Right click one blob container and check the context menu.

Expect:
It should display 'Upload page blob' in the context menu.
Actual:
It displays 'Upload block blob' in the  context menu.

We should probably disable the context menu in this scenario since we don't support page blobs.  I expect they'll get an Azure error here.

By design for now.  If users try it anyway they should get an error message indicating that block blobs aren't supported.


feature-request NPC Tagging

Plugin that can outline selected npcs, very useful for chin hunting

I've got a question about how you want to select the NPCs.
Are you wanting the ability to right-click -> 'tag' a specific NPC and it will only outline that single NPC?
Or, are you wanting something where you can enter an NPC name and all NPCs with that name will be outlined?

Done in #939


Bug Fixes

This is a paid opportunity through the BCDevExchange.To apply, visit the opportunity page and submit a proposal before Friday, June 29, 2018

Hello interested applicants,
I am the UX designer for the BCDevExchange application. If you have any questions about putting in a proposal on this opportunity, please drop a note here and I'll respond. Thanks!

Hi Mark,
I'm interested in this opportunity. Is there somewhere the bugs in question can be reviewed?
Many thanks,

Jonny Miller

Hello, Mark.
I'm also interested in this opportunity.
I will submit proposal before the due date.
Cheers,
Albert Lee

Hi guys - thanks for your interest!
@hitchless - sorry for the delay. Please see #399 and #400 I've just posted ... examples of the kinds of things we'd be wanting you to look at.

Thanks Mark, I'll have a look now.

Thanks everyone for your interest in helping us out. The opportunity is now closed for proposals, and we've received 8. Due to the 🇨🇦 Canada Day holiday this weekend, we will score on Tuesday morning and announce the assignee here by mid-day Tuesday.

Hi everyone -- thank you for the time you put in to send us your proposals. We have scored them and the highest scoring applicant was @ccoldwell.  If you were unsuccessful and would like feedback on your proposal, please contact me at the email address in my profile. Thanks again!


[Darwin] Question of commissioningComplete implementation

Reproduction steps
I found that only when commissioning is successful, the nodeID is set as shown in the code below.
https://github.com/project-chip/connectedhomeip/blob/a4561356623ba5a7281aaeb60696860fd594318b/src/darwin/Framework/CHIP/MTRDeviceControllerDelegateBridge.mm#L155
I would like to ask if there is a reason for implementing it this way.
Since each stage operates asynchronously, I think it is more appropriate to pass on the nodeID even in case of failure. Ask if you would like to make that change.
Bug prevalence
everytime
GitHub hash of the SDK that was being used
a4561356623ba5a7281aaeb60696860fd594318b
Platform
darwin
Platform Version(s)
No response
Anything else?
No response

Like the documentation says:
 * Exactly one of error and nodeID will be nil.

The node ID here is the node ID that was assigned to the commissioned node.  If the node was not commissioned, no node ID was assigned.


test socialify

Didn't work, reported to socialify team: https://github.com/wei/socialify/issues/123
Will keep this open tho incase it works within the next 1-2 hours

well it takes a few hours ig, it worked now.


Merge Jeff+Wayne action ideas

Description
Cleans up the code introduced in the docker-playground to work in more cases and stream logs correctly.
Related Issue
Fixes #N/A
Type of change

[X] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Other (security config, docs update, etc)

Checklist before merging

[ ] Test, docs, adr added or updated as needed
[X] Contributor Guide Steps followed

Screnshot:

Streaming logs while sleeping

No progress


Micromod - Abstract the MCU

Would your firmware run adequately on https://www.sparkfun.com/products/21326
If so would you consider moving to the MicroMod footprint rather than as a specific dev board footprint?

I was interested in the possibility of adapting some of your work for a low-voltage off-grid use case, using LoRa as the comms layer.


Align flush behaviour of builders

Extracted from https://github.com/crystal-lang/crystal/pull/8876#discussion_r387900139
Why does YAML::Builder flush but XML::Builder doesn't? Shouldn't we make this behave identical?
JSON::Builder#flush delegates to io.flush which is another different behaviour.
I didn't look into this any deeper, so I'm not sure what should be the best way. But every builder behaves a bit different. There are also a few more builders in stdlib which should be covered as well.

So there are a few angles to this:

Builders typically expose a .build method, either on the builder itself or the parent namespace. Such a build method generates a self-contained piece and it makes sense to flush there.
Most builders also have internal methods that mark the end of a self-contained piece, for example YAML::Builder#end_stream. That method seems like it would be a good idea to flush. But what about YAML::Builder#end_document? Should that flush? It's a self contained piece. But in most typical use cases, a stream only contains a single document, so it just duplicates the flush on end_document. Probably not going to make a noticable performance difference, though.

It's probably undisputed that .build methods should make sure to always flush.
But I'm not sure if any of the API methods should flush. Typical use cases should always use the .build helper. If you don't use that it's because you need some special behaviour and I think it makes sense to be responsible for flushing then.
It might still be a good idea for API methods that clearly mark the end of the building sequence (for example after YAML::Builder#end_sequence is called, you can't add anything to the builder).

Also it seems to make sense to always flush the underlying IO when flush is called on the builder. Some builders expose this method when the builder implementation provides it, but it does not (yet) call flush the underlying IO.


Bug with redundant position:relative on

For some reason, I'm using ResizeSensor to watch for changes in the <body> element's size and I get the following behavior in Chrome: when one sets position:relative on <body> and there is a bottom (horizontal) scrollbar, your appended sensor 100% height element will take <body>'s outer height (so, including scrollbar). When there's no position:relative, it will take the <body>'s client height. The second case is obviously desired for measurement (ResizeSensor will not trip when bottom scrollbar gets added). I fixed it by simply not adding position:relative on body, especially since every browser has it's own hack-ish method of performing <html> and <body> scrolling and 100% sizing. So would you please add an exclusion for trying to change position on the <body>.
Context: I'm watching <body>'s size precisely to detect when scrollbars are added on desktop, not in a window.resize context but in a DOM context (DOM is manipulated that results in scrollbars being added). While I could do this by replicating some of your code (watching for a hidden scrollable element), I find using your whole bunch of code very useful for other purposes as well, so I'd be happy if the npm package would have the <body> exception built in :)

It's not a bug when the use-case is not supported. I can't see a reason why monitoring the body for size changes would be useful, so that use-case will likely stays unsupported, sorry.


fix fix cannot cancel storage policy of partition

Issue:
execute a stmt to cancel a partition's storage policy execute returns ok, but it doesnot work:

run buildall

We should not cancel any storage migration policies to prevent from being unable to recover data if the policies are canceled after data migration.

run buildall

run buildall

run p0

run p0

run p0

run p0

run p0


Thermostat clarification

First, thanks for a great project, I was up and running in no time with a bunch of custom built accessories.
On Thermostats, is there any way to have the characteristic Ito only 0 and 1 (off and heat, no cool or auto) ?
Also as you move the slider to change the setpoint, a lot of messages get posted, is there a way to only post the last message?  Going over the code, it looks like there may be some similar functionality in the WindowCovering.js
The reason I ask, is I'm using this for a spa heater. Obviously no cool or auto mode, and changing the temperature set point is very slow since I need to re-program the thermostat over a RS485 interface. So rather than buffer all the temperature set point changes and wait for a period of time with no activity to action the last one, it would obviously be easier to only send setpoint once the user has clicked off the icon, but not sure if that's an event you can catch or not.
Thanks again for this project.

Hmm... I think this is due to how the App sends the Requests to the Bridge. I fear I can't do anything about that, only suggestion I have are workarounds: perhaps try another App (Elgato Eve e.g.) or use Homekit-Scenes to set specific Temperatures...

Thanks or taking a look at limiting the characteristic
On the multiple messages, I've tried a few apps, they all seem to act the same.  But the Hope app is the one I use the most.  On the Thermostat icon, do a long press, and a slider will come up to let you adjust the set point temp.  That's the one I mean.
But, I've coded round that in the server side now.  Simply wait for 2 seconds with no update messages then act on the last one sent.
I do like the HomeKit-scene idea, I'll give that a shot.

So I tried that, overwrote the Properties of TargetHeatingCoolingState and CurrentHeatingCoolingState like this:
"TargetHeatingCoolingState": {
        "minValue": 0,
        "maxValue": 1,
        "validValues": [0, 1]
      },
      "CurrentHeatingCoolingState": {
        "minValue": 0,
        "maxValue": 1,
        "validValues": [0, 1]
      }

but sadly it does not work. Tested with the Home App and Elgato Eve, both still show Cooling and Auto :-(
I fear I can't help you with that.

Oh. It works :-) I did smth wrong :D Give me some time ;)

So on v0.8.0 you can achieve that by configuring your Heater like that:
  "test/Heizung": {
    "service": "Thermostat",
    "name": "Heizung Test",
    "topic": {
      "setTargetTemperature": "test/set/TargetTemperature",
      "statusTargetTemperature": "test/status/TargetTemperature",
      "setTargetHeatingCoolingState": "test/set/TargetHeatingCoolingState",
      "statusCurrentHeatingCoolingState": "test/status/CurrentHeatingCoolingState",
      "statusCurrentTemperature": "test/status/CurrentTemperature",
      "statusCurrentRelativeHumidity": "test/status/CurrentRelativeHumidity"
    },
    "props": {
      "TargetTemperature": {
        "maxValue": 36,
        "minValue": 4
      },
      "TargetHeatingCoolingState": {
        "validValues": [0, 1]
      }
    }
  }

Until now it's not possible to set props via the UI, so you have to do it manually in the json file.

so, in v0.8.3 editing the props is possible via the web ui :-)

Thanks very much for this, exactly what I need, I’ll give it a try in a day or two.

Works like a charm.  thank you very much for this.


Allow multiple default cluster lists

Existing: A single cluster list (based on UN data) that can be added to
Target: Add a ClusterGroup layer on top of the existing list. This allows the site to have several standard lists of clusters available for selection, as well as starting a new cluster list as needed.
Needs both database migration and UI work

Working on this one


Webpack compatibility

Awesome stuff! Thanks!
Webpack doesn't like this line: https://github.com/epoberezkin/ajv/blob/master/lib/ajv.js#L294
Webpack can require() .json-files, but it needs an explicit https://github.com/webpack/json-loader, and a different syntax e.g. require('json!./refs/json-schema-draft-04.json');
I can't work around this issue by setting metaSchema explicitly, since Webpack simply will not parse and process ajv ....

Managed to get it working by configuring Webpack properly - Just add the following to your Webpack configuration:
	"module": {
		"loaders": [{
			"test": /\.json$/,
			"loader": "json"
		}]
	}

Thanks!


Add rector to CI

Codecov Report

Merging #70 (9c75ead) into main (5e26af9) will increase coverage by 1.37%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##               main      #70      +/-   ##
============================================
+ Coverage     98.10%   99.47%   +1.37%
+ Complexity      437      435       -2
============================================
  Files            30       30
  Lines          1159     1152       -7
============================================
+ Hits           1137     1146       +9
+ Misses           22        6      -16

Impacted Files
Coverage Δ

src/Cache/FileCacheManager.php
100.00% <100.00%> (+14.81%)
:arrow_up:

src/Cache/FileHandler.php
100.00% <100.00%> (+34.37%)
:arrow_up:

src/Runner/Linter.php
98.48% <100.00%> (+1.46%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Fixes issues with the intake API

Intake API created issues when the result had more than 150 results (fields were written as List of strings when they should be just String). This aims to fix this

@Karinon the build process did not complete : Can you check what's going on? https://github.com/FREVA-CLINT/databrowserAPI/actions/runs/7694596668/job/20965688706

@antarcticrainforest The issue came with python 3.12 and I am sure, that the previous build does not work anymore aswell.
The error message is
  frozenlist/_frozenlist.c:8088:45: error: ‘PyLongObject’ {aka ‘struct _longobject’} has no member named ‘ob_digit’
   8088 |     const digit* digits = ((PyLongObject*)b)->ob_digit;
        |                                             ^~
  error: command '/usr/bin/gcc' failed with exit code 1

  at /usr/local/lib/python3.12/site-packages/poetry/installation/chef.py:164 in _prepare
      160│
      161│                 error = ChefBuildError("\n\n".join(message_parts))
      162│
      163│             if error is not None:
    → 164│                 raise error from None
      165│
      166│             return path
      167│
      168│     def _prepare_sdist(self, archive: Path, destination: Path | None = None) -> Path:

Note: This error originates from the build backend, and is likely not a problem with poetry but with frozenlist (1.3.3) not supporting PEP 517 builds. You can verify this by running 'pip wheel --no-cache-dir --use-pep517 "frozenlist (==1.3.3)"'.

As of now I have no idea how to fix that except for setting the docker-container to python:3.11.
Is there any reason why you have set poetry install -q --only main --no-root --no-directory --no-interaction to quiet? It took me way too long to realize, that -q is the thing which eats the error message and it was quite frustrating. Can we get rid of it?
Btw: I still think that it makes sense to use actual version numbers instead of 'latest' if we really want to have a stable system :P

I'd say we get rid of poetry in favour for flit altogether. For my taste way too much boilerplate. Flit is simple and does the job how we need it. The project has been started by a former colleague of mine. I have already made a PR there as something didn't work as I wanted. Which was easy.


Update array_ops.py

Added couple of examples for tf.zeros_like

Closing this PR as this not against master, please open a new PR against master
CC @mihaimaruseac


add username as author of card

In GitLab by @lakhoune on May 8, 2020, 18:47
Put the username on the author field of the card, as these are unique for the site

In GitLab by @lakhoune on May 9, 2020, 22:33
assigned to @lakhoune

In GitLab by @lakhoune on May 9, 2020, 22:45
mentioned in commit 8f0a517e14ae5d079dc0de73d1805a830d2c0b8f

In GitLab by @lakhoune on May 9, 2020, 22:47
closed

In GitLab by @VerwaltungHilton on May 15, 2020, 22:57
Do not forget to mark the social service as verified                  here


Documentation is unclear about how to get data into a Dialog.

Bug, feature request, or proposal:
Documentation bug.
What is the expected behavior?
When I use the MdDialog service to open a dialog with some component, I'd love to be able to pass some configuration into that component.
What is the current behavior?
The dialogRef exposes componentInstance, which allows me to set properties / call functions on the component after construction, however I'm unsure if this is the recommended approach since it is not mentioned in the docs.
What are the steps to reproduce?
Read the docs at https://github.com/angular/material2/blob/master/src/lib/dialog/README.md, and notice the example uses a "static" dialog.
What is the use-case or motivation for changing an existing behavior?
It would improve the documentation and reduce the number of future issues.
Which versions of Angular, Material, OS, browsers are affected?
Latest /all
Is there anything else we should know?
I can submit a PR for improved documentation of an answer from this threads provides sufficient information!

https://github.com/angular/material2/issues/1377#issuecomment-250632661

The dialogRef exposes componentInstance, which allows me to set properties / call functions on the component after construction, however I'm unsure if this is the recommended approach since it is not mentioned in the docs.

https://github.com/angular/material2/issues/1377#issuecomment-250632661

@SamMousa, as I see it's actually the only way to do it directly. You can use an injected service for that, but, IMHO, it would be an overkill.

I've added this to my todo list.

Is there any timeframe of when this will be added? if not could a code snippet be created here to show how to do it?

@tmburnell I'm currently no longer working on an angular related project so it's low on the list.

I figured it out from another post:
use this when opening
let dialogRef = this.dialog.open(myModal);
dialogRef.componentInstance.data = myData;

use this in the modal
this.data = this.dialogRef.componentInstance.data;

@SamMousa
I know in general components should share data (typically modeled data) with a service. (depending on what you're doing)
https://angular.io/docs/ts/latest/cookbook/component-communication.html#!#bidirectional-service
If you're looking for something quick I don't think there is anything wrong with tmburnells example, it just depends on what you're trying to accomplish and how expandable or modular you want it to be.

I'm gonna close this since I no longer expect I'll be working on it in the foreseeable future.

@SamMousa I have a PR out for this, you were right about it being confusing.


⭐ Query - When is John Smith's next availability

Cc: @theixdev @AttackOnMorty

Pain

People want to know when is someone available
Tasks (only do the easy ones)

[ ] When is John Smith's next availability
[ ] When is John next available
[ ] When will John next be free
[ ] When is John next Free/Available
[ ] When will John finish his current booking
[ ] When is John's next bookable

Hard Tasks

[ ] When is John next free for 3 days?
Feedback from @theixdev

Thanks!

[ ] Have a test for all queries

Easy ones are implemented.

Figure: Command responses from the "easy ones"

As per conversation with Adam during Sprint Review, Add this new feature to the SophieBot Try out page.

[ ] Add it.

Done - Added to the SophieBot Try page

Figure: Added new query "When is Piers next free for 2 days?" to the Try Out Page


Error Adding Local Alias : SCID not found

Hi Team, We have recently tested Single Hop and Multi-Hop Payment Transfers via a Mock RFQ middleware in between.
So, the case was RFQ middleware node generated an invoice via this command
user@aw60:/src$ ./litcli-assetfunctions-testnet.sh ln addinvoice --asset_id d421c41e5cccc7a46853a67a77f9bfbff0e46b636be45080b70d6228430c2675 --asset_amount  10
Asking peer 0310fc0c9bec84463bfc7fc2c9c8de4ebb1a0417e89c4aaeb0be14ea80390959b3 for quote to buy assets to receive for invoice over 10 units; waiting up to 60s

Our Node used the conventional way via paying using GRPC of LND ( lncli payinvoice).
The taproot-Asset daemon of our node went down and the error noted in the console was
received a critical error from sub-server (taproot-assets), shutting down: failed to handle outgoing message: error adding local alias: base SCID not found for an asset: d421c41e5cccc7a46853a67a77f9bfbff0e46b636be45080b70d6228430c2675"

We restarted LITD and have been good to go since then, But I think the issue struck when trying to populate alias SCID for the first time.
The team is trying to catch up to the logs of the node, might update in the comment if we retrieve one, as it's been quite a few hours since we noticed the issue.
LITD version used
578f65f301b8:/# litcli -n testnet getinfo
{
    "version":  "0.13.99-alpharc3 commit=v0.13.99-alpha.rc3"
}

Hey @vanditshah99
Thank you for the early testing, and for opening this issue
Looks like this was expected behavior according to our codebase, as we would not be able to match a real channel with an empty asset id.
This was recently changed in #1011 and will no longer cause the daemon to terminate.

We restarted LITD and have been good to go since then, But I think the issue struck when trying to populate alias SCID for the first time.

After the restart, did you try to pay with the same command? (i.e lncli payinvoice)

Oh yes, we did. we checked the scenario, where in a taproot asset ln invoice is paid by lncli payinvoice, worked well :+1:

The scenario that failed, was that a multi-hop or single-hop (direct channel) payment?

It was a single hop payment.

And did you have other channels (non-asset channels) on either of the sender/receiver node?

Yes, The receiver had a lightning channel with another node as well

Okay, thanks. I'll try to reproduce this and let you know if I have more questions.

Hmm, I'm having trouble reproducing this... Do you still have the logs from when it happened (please always attach logs if possible)?
If no logs are available anymore, can you please try to reproduce with the latest RC4?

We were actively testing it with two other peer nodes, and didn't so until we completed testing and gathered info about the bugs, we found that server didn't persist the logs, let us try with latest rc4, and see if we can reproduce it. Thanks

@guggero we accidentally came across this issue again, what we did

Node 1 minted assets
Node 2 synced the universe
Node 1 connects to node 2 as peers

Now we directly try AddAssetBuyOrder
{
    "min_asset_amount":10,
    "timeout_seconds":15,
    "peer_pub_key":"A1a0YjGCFe2iTH1enk7eUXpyfJiZrGrL8nOjlqQhGjeS"
}

Node 2 which is the peer node logs are as follows
2024-07-31 06:11:17.659 [DBG] RFQS: Order handler is registering an asset sale policy given a buy accept message: BuyAccept(peer=0310fc0c9bec84463bfc7fc2c9c8de4ebb1a0417e89c4aaeb0be14ea80390959b3, id=d78f50f99909e66b9f7a8bb5256cd08e97669e2b83a507e23e5db68424382ee0, ask_price=158, expiry=1722409877, scid=4493948681845223136)
2024-07-31 06:11:17.659 [DBG] RPCS: [/lnrpc.Lightning/ListChannels] requested
2024-07-31 06:11:17.660 [DBG] RPCS: [listchannels] fetched 0 channels from DB
2024-07-31 06:11:17.660 [TRC] TSVR: InlineParseCustomData called with *lnrpc.ListChannelsResponse
2024-07-31 06:11:17.660 [ERR] RFQS: Error in RFQ manager: failed to handle outgoing message: error adding local alias: add alias: base SCID not found for asset: f8ffc554dad8a3780c408297a70b70af1c8d96cae3c167ff55cbd6308edb2a08
2024-07-31 06:11:19.209 [ERR] CMGR: Can't accept connection: unable to accept connection from <IP_ADDRESS>:37943: EOF
2024-07-31 06:11:19.501 [TRC] TCHN: Request to handle: *lnwire.GossipTimestampRange
2024-07-31 06:11:19.501 [TRC] TCHN: Request to handle: 265
2024-07-31 06:11:19.501 [DBG] TCHN: Failed to handle: *lnwire.GossipTimestampRange
2024-07-31 06:11:19.501 [DBG] PFSM: MsgRouter: unable to route msg protofsm.PeerMsg
2024-07-31 06:11:19.501 [DBG] CHDB: ChanUpdatesInHorizon hit percentage: NaN (0/0)
2024-07-31 06:11:19.501 [INF] DISC: GossipSyncer(0310fc0c9bec84463bfc7fc2c9c8de4ebb1a0417e89c4aaeb0be14ea80390959b3): applying new update horizon: start=2042-07-14 01:04:00 +0000 UTC, end=2042-07-14 01:04:00 +0000 UTC, backlog_size=0
2024-07-31 06:11:19.559 [DBG] HLCK: invoking success callback
2024-07-31 06:11:19.581 [DBG] SRVR: Sending 0 messages to peer 02e76d0188c85c4bc13939533f6c4f5f21768d3e0a86fc32552a37969be0c6abe0
2024-07-31 06:11:19.582 [DBG] SRVR: Sending 0 messages to peer 02db3ba0d5b512f58ee0833b40ea62c62e78c1d997457cc03caeb17d06ec12ab69
2024-07-31 06:11:19.582 [DBG] SRVR: Sending 0 messages to peer 031ba13b2a008cd5ed17bfc8df660210aa37fbac6ce5951fa1e01cdbc74059d92e
2024-07-31 06:11:19.582 [DBG] SRVR: Sending 0 messages to peer 0310fc0c9bec84463bfc7fc2c9c8de4ebb1a0417e89c4aaeb0be14ea80390959b3

Node 1 Logs which requests AddAssetBuyOrder
2024-07-31 06:11:00.359 [DBG] PFSM: MsgRouter: unable to route msg protofsm.PeerMsg
2024-07-31 06:11:00.359 [DBG] PEER: Peer(032ea4d24c807bfe6df899df04f2b562a646d7467b2ab3c97cffdc98e0d1a984e4): Received NodeAnnouncement(node=03423cb1bd00c92af9cf91ed64a454cc97362038d549e1297028cf83fd3ea1b6d5, update_time=2024-07-31 06:10:07 +0000 UTC) from 032ea4d24c807bfe6df899df04f2b562a646d7467b2ab3c97cffdc98e0d1a984e4@<IP_ADDRESS>:40576
2024-07-31 06:11:00.359 [DBG] TCHN: Failed to handle: *lnwire.NodeAnnouncement
2024-07-31 06:11:00.359 [DBG] PFSM: MsgRouter: unable to route msg protofsm.PeerMsg
2024-07-31 06:11:00.359 [DBG] DISC: Processing ChannelUpdate: peer=032ea4d24c807bfe6df899df04f2b562a646d7467b2ab3c97cffdc98e0d1a984e4@<IP_ADDRESS>:40576, short_chan_id=2615181809600299008,
2024-07-31 06:11:00.359 [DBG] DISC: Processing NodeAnnouncement: peer=032ea4d24c807bfe6df899df04f2b562a646d7467b2ab3c97cffdc98e0d1a984e4@<IP_ADDRESS>:40576, timestamp=2024-07-31 06:10:07 +0000 UTC, node=03423cb1bd00c92af9cf91ed64a454cc97362038d549e1297028cf83fd3ea1b6d5
2024-07-31 06:11:00.359 [DBG] DISC: Validating ChannelUpdate: channel=2615181809600299008, from node=02c6bb69fd7615c70ee271ed64d12a9f233da8836ac79b0a21a43d0149a246c0a7, has edge=true
2024-07-31 06:11:00.359 [DBG] PEER: Peer(032ea4d24c807bfe6df899df04f2b562a646d7467b2ab3c97cffdc98e0d1a984e4): Received NodeAnnouncement(node=02be8f360e57600486b93dd33ea0872a4e14a259924ba4084f27d693a77d151158, update_time=2024-07-31 06:09:22 +0000 UTC) from 032ea4d24c807bfe6df899df04f2b562a646d7467b2ab3c97cffdc98e0d1a984e4@<IP_ADDRESS>:40576
2024-07-31 06:11:00.359 [DBG] TCHN: Failed to handle: *lnwire.NodeAnnouncement
2024-07-31 06:11:00.359 [DBG] PFSM: MsgRouter: unable to route msg protofsm.PeerMsg
2024-07-31 06:11:00.360 [DBG] DISC: Processing NodeAnnouncement: peer=032ea4d24c807bfe6df899df04f2b562a646d7467b2ab3c97cffdc98e0d1a984e4@<IP_ADDRESS>:40576, timestamp=2024-07-31 06:09:22 +0000 UTC, node=02be8f360e57600486b93dd33ea0872a4e14a259924ba4084f27d693a77d151158
2024-07-31 06:11:00.360 [DBG] CRTR: Received ChannelEdgePolicy for channel<PHONE_NUMBER>600299008
2024-07-31 06:11:00.359 [DBG] CRTR: Checking stale node<PHONE_NUMBER>63623162643030633932616639636639316564363461343534636339373336323033386435343965313239373032386366383366643365613162366435 got Ignoring outdated announcement for 03423cb1bd00c92af9cf91ed64a454cc97362038d549e1297028cf83fd3ea1b6d5
2024-07-31 06:11:00.360 [DBG] DISC: Skipped processing stale node: 03423cb1bd00c92af9cf91ed64a454cc97362038d549e1297028cf83fd3ea1b6d5
2024-07-31 06:11:00.867 [DBG] DISC: Processed NodeAnnouncement: peer=032ea4d24c807bfe6df899df04f2b562a646d7467b2ab3c97cffdc98e0d1a984e4@<IP_ADDRESS>:40576, timestamp=2024-07-31 06:09:22 +0000 UTC, node=02be8f360e57600486b93dd33ea0872a4e14a259924ba4084f27d693a77d151158
2024-07-31 06:11:00.873 [DBG] DISC: Processed ChannelUpdate: peer=032ea4d24c807bfe6df899df04f2b562a646d7467b2ab3c97cffdc98e0d1a984e4@<IP_ADDRESS>:40576, short_chan_id=2615181809600299008, timestamp=2024-07-31 06:09:54 +0000 UTC
2024-07-31 06:11:07.419 [DBG] PEER: Peer(02eb311fca318454d00ed19fee12b5fe3bb6058034a1cb0f1e094d2c075ff93ee7): Received Ping(ping_bytes=0060e621661c7d61c0672d8816abc5deae5ebc6d7a2fda2fcaf0bebd09000000000000005f4df808c1c6368e3dcc39b9720959612162464e52adc1fb5771e06990f6e9efc6d4a966c9f21419b15c31b8) from 02eb311fca318454d00ed19fee12b5fe3bb6058034a1cb0f1e094d2c075ff93ee7@<IP_ADDRESS>:9735
2024-07-31 06:11:07.419 [DBG] TCHN: Failed to handle: *lnwire.Ping
2024-07-31 06:11:07.419 [DBG] PFSM: MsgRouter: unable to route msg protofsm.PeerMsg
2024-07-31 06:11:07.419 [DBG] PEER: Peer(02eb311fca318454d00ed19fee12b5fe3bb6058034a1cb0f1e094d2c075ff93ee7): Sending Pong(len(pong_bytes)=16) to 02eb311fca318454d00ed19fee12b5fe3bb6058034a1cb0f1e094d2c075ff93ee7@<IP_ADDRESS>:9735
2024-07-31 06:11:07.428 [DBG] PEER: Peer(02eb311fca318454d00ed19fee12b5fe3bb6058034a1cb0f1e094d2c075ff93ee7): Sending Ping(ping_bytes=0060e621661c7d61c0672d8816abc5deae5ebc6d7a2fda2fcaf0bebd09000000000000005f4df808c1c6368e3dcc39b9720959612162464e52adc1fb5771e06990f6e9efc6d4a966c9f21419b15c31b8) to 02eb311fca318454d00ed19fee12b5fe3bb6058034a1cb0f1e094d2c075ff93ee7@<IP_ADDRESS>:9735
2024-07-31 06:11:07.431 [DBG] PEER: Peer(02eb311fca318454d00ed19fee12b5fe3bb6058034a1cb0f1e094d2c075ff93ee7): Received Pong(len(pong_bytes)=3173) from 02eb311fca318454d00ed19fee12b5fe3bb6058034a1cb0f1e094d2c075ff93ee7@<IP_ADDRESS>:9735
2024-07-31 06:11:07.431 [DBG] TCHN: Failed to handle: *lnwire.Pong
2024-07-31 06:11:07.431 [DBG] PFSM: MsgRouter: unable to route msg protofsm.PeerMsg
2024-07-31 06:11:07.616 [DBG] PEER: Peer(0236e31dcc11311b09d1cfe54c82897fac4d8c3e28fcb7fb8744de385e0cf8ffb2): Sending Ping(ping_bytes=0060e621661c7d61c0672d8816abc5deae5ebc6d7a2fda2fcaf0bebd09000000000000005f4df808c1c6368e3dcc39b9720959612162464e52adc1fb5771e06990f6e9efc6d4a966c9f21419b15c31b8) to 0236e31dcc11311b09d1cfe54c82897fac4d8c3e28fcb7fb8744de385e0cf8ffb2@<IP_ADDRESS>:9735
2024-07-31 06:11:07.620 [DBG] PEER: Peer(0236e31dcc11311b09d1cfe54c82897fac4d8c3e28fcb7fb8744de385e0cf8ffb2): Received Ping(ping_bytes=0060e621661c7d61c0672d8816abc5deae5ebc6d7a2fda2fcaf0bebd09000000000000005f4df808c1c6368e3dcc39b9720959612162464e52adc1fb5771e06990f6e9efc6d4a966c9f21419b15c31b8) from 0236e31dcc11311b09d1cfe54c82897fac4d8c3e28fcb7fb8744de385e0cf8ffb2@<IP_ADDRESS>:9735
2024-07-31 06:11:07.621 [DBG] TCHN: Failed to handle: *lnwire.Ping
2024-07-31 06:11:07.621 [DBG] PFSM: MsgRouter: unable to route msg protofsm.PeerMsg
2024-07-31 06:11:07.621 [DBG] PEER: Peer(0236e31dcc11311b09d1cfe54c82897fac4d8c3e28fcb7fb8744de385e0cf8ffb2): Sending Pong(len(pong_bytes)=2918) to 0236e31dcc11311b09d1cfe54c82897fac4d8c3e28fcb7fb8744de385e0cf8ffb2@<IP_ADDRESS>:9735
2024-07-31 06:11:07.692 [DBG] PEER: Peer(0236e31dcc11311b09d1cfe54c82897fac4d8c3e28fcb7fb8744de385e0cf8ffb2): Received Pong(len(pong_bytes)=634) from 0236e31dcc11311b09d1cfe54c82897fac4d8c3e28fcb7fb8744de385e0cf8ffb2@<IP_ADDRESS>:9735
2024-07-31 06:11:07.692 [DBG] TCHN: Failed to handle: *lnwire.Pong
2024-07-31 06:11:07.692 [DBG] PFSM: MsgRouter: unable to route msg protofsm.PeerMsg
2024-07-31 06:11:09.185 [DBG] PEER: Peer(020c3b59b1854d31b94c0dd9df1019d251b4cd5565129f7ad16e3ec8c4671afd8c): Sending Ping(ping_bytes=0060e621661c7d61c0672d8816abc5deae5ebc6d7a2fda2fcaf0bebd09000000000000005f4df808c1c6368e3dcc39b9720959612162464e52adc1fb5771e06990f6e9efc6d4a966c9f21419b15c31b8) to 020c3b59b1854d31b94c0dd9df1019d251b4cd5565129f7ad16e3ec8c4671afd8c@<IP_ADDRESS>:41934
2024-07-31 06:11:09.270 [DBG] PEER: Peer(020c3b59b1854d31b94c0dd9df1019d251b4cd5565129f7ad16e3ec8c4671afd8c): Received Pong(len(pong_bytes)=2604) from 020c3b59b1854d31b94c0dd9df1019d251b4cd5565129f7ad16e3ec8c4671afd8c@<IP_ADDRESS>:41934
2024-07-31 06:11:09.271 [DBG] TCHN: Failed to handle: *lnwire.Pong
2024-07-31 06:11:09.271 [DBG] PFSM: MsgRouter: unable to route msg protofsm.PeerMsg
2024-07-31 06:11:09.276 [DBG] PEER: Peer(020c3b59b1854d31b94c0dd9df1019d251b4cd5565129f7ad16e3ec8c4671afd8c): Received Ping(ping_bytes=0060e621661c7d61c0672d8816abc5deae5ebc6d7a2fda2fcaf0bebd09000000000000005f4df808c1c6368e3dcc39b9720959612162464e52adc1fb5771e06990f6e9efc6d4a966c9f21419b15c31b8) from 020c3b59b1854d31b94c0dd9df1019d251b4cd5565129f7ad16e3ec8c4671afd8c@<IP_ADDRESS>:41934
2024-07-31 06:11:09.276 [DBG] TCHN: Failed to handle: *lnwire.Ping
2024-07-31 06:11:09.276 [DBG] PFSM: MsgRouter: unable to route msg protofsm.PeerMsg
2024-07-31 06:11:09.276 [DBG] PEER: Peer(020c3b59b1854d31b94c0dd9df1019d251b4cd5565129f7ad16e3ec8c4671afd8c): Sending Pong(len(pong_bytes)=3913) to 020c3b59b1854d31b94c0dd9df1019d251b4cd5565129f7ad16e3ec8c4671afd8c@<IP_ADDRESS>:41934
2024-07-31 06:11:09.766 [ERR] CMGR: Can't accept connection: unable to accept connection from <IP_ADDRESS>:57347: EOF
2024-07-31 06:11:16.086 [DBG] LNWL: filterManager updated moving median to: 1000 sat/kb
2024-07-31 06:11:17.234 [INF] WTCL: (taproot) Client stats: tasks(received=0 accepted=0 ineligible=0) sessions(acquired=0 exhausted=0)
2024-07-31 06:11:17.234 [INF] WTCL: (legacy) Client stats: tasks(received=0 accepted=0 ineligible=0) sessions(acquired=0 exhausted=0)
2024-07-31 06:11:17.234 [INF] WTCL: (anchor) Client stats: tasks(received=0 accepted=0 ineligible=0) sessions(acquired=0 exhausted=0)
2024-07-31 06:11:17.650 [INF] LITD: Handling REST request: /v1/taproot-assets/rfq/buyorder/asset-id/f8ffc554dad8a3780c408297a70b70af1c8d96cae3c167ff55cbd6308edb2a08
2024-07-31 06:11:17.650 [INF] LITD: Handling gRPC request: /rfqrpc.Rfq/AddAssetBuyOrder
2024-07-31 06:11:17.651 [DBG] RPCS: [/rfqrpc.Rfq/AddAssetBuyOrder] requested
2024-07-31 06:11:17.652 [DBG] RFQS: Manager handling outgoing message: BuyRequest(peer=0356b462318215eda24c7d5e9e4ede517a727c9899ac6acbf273a396a4211a3792, id=d78f50f99909e66b9f7a8bb5256cd08e97669e2b83a507e23e5db68424382ee0, asset_id=f8ffc554dad8a3780c408297a70b70af1c8d96cae3c167ff55cbd6308edb2a08, asset_group_key=, asset_amount=10, bid_price=158)
2024-07-31 06:11:17.652 [DBG] RFQS: Stream handling outgoing message: BuyRequest(peer=0356b462318215eda24c7d5e9e4ede517a727c9899ac6acbf273a396a4211a3792, id=d78f50f99909e66b9f7a8bb5256cd08e97669e2b83a507e23e5db68424382ee0, asset_id=f8ffc554dad8a3780c408297a70b70af1c8d96cae3c167ff55cbd6308edb2a08, asset_group_key=, asset_amount=10, bid_price=158)
2024-07-31 06:11:17.654 [DBG] RPCS: [/lnrpc.Lightning/SendCustomMessage] requested
2024-07-31 06:11:17.658 [DBG] PEER: Peer(0356b462318215eda24c7d5e9e4ede517a727c9899ac6acbf273a396a4211a3792): Sending custom(type=52884) to 0356b462318215eda24c7d5e9e4ede517a727c9899ac6acbf273a396a4211a3792@<IP_ADDRESS>:8735
2024-07-31 06:11:19.255 [DBG] NANN: HostAnnouncer checking for any IP changes...
2024-07-31 06:11:19.258 [DBG] NANN: No IP changes detected for hosts: [taplit.tryspeed.dev:9751]
2024-07-31 06:11:19.260 [DBG] HLCK: invoking success callback
2024-07-31 06:11:19.493 [DBG] DISC: Rotating active GossipSyncer(0356b462318215eda24c7d5e9e4ede517a727c9899ac6acbf273a396a4211a3792) with GossipSyncer(020c3b59b1854d31b94c0dd9df1019d251b4cd5565129f7ad16e3ec8c4671afd8c)
2024-07-31 06:11:19.493 [DBG] DISC: Transitioning active GossipSyncer(0356b462318215eda24c7d5e9e4ede517a727c9899ac6acbf273a396a4211a3792) to passive
2024-07-31 06:11:19.494 [DBG] DISC: GossipSyncer(0356b462318215eda24c7d5e9e4ede517a727c9899ac6acbf273a396a4211a3792): transitioning from ActiveSync to PassiveSync
2024-07-31 06:11:19.494 [INF] DISC: GossipSyncer(0356b462318215eda24c7d5e9e4ede517a727c9899ac6acbf273a396a4211a3792): applying gossipFilter(start=0001-01-01 00:00:00 +0000 UTC, end=0001-01-01 00:00:00 +0000 UTC)
2024-07-31 06:11:19.494 [DBG] DISC: GossipSyncer(0356b462318215eda24c7d5e9e4ede517a727c9899ac6acbf273a396a4211a3792): state=chansSynced, type=PassiveSync
2024-07-31 06:11:19.494 [DBG] DISC: Transitioning passive GossipSyncer(020c3b59b1854d31b94c0dd9df1019d251b4cd5565129f7ad16e3ec8c4671afd8c) to active
2024-07-31 06:11:19.494 [DBG] DISC: GossipSyncer(020c3b59b1854d31b94c0dd9df1019d251b4cd5565129f7ad16e3ec8c4671afd8c): transitioning from PassiveSync to ActiveSync
2024-07-31 06:11:19.494 [INF] DISC: GossipSyncer(020c3b59b1854d31b94c0dd9df1019d251b4cd5565129f7ad16e3ec8c4671afd8c): applying gossipFilter(start=2024-07-31 06:11:19.494398499 +0000 UTC m=+602405.086032608, end=2160-09-06 12:39:34.494398499 +0000 UTC)
2024-07-31 06:11:19.494 [DBG] DISC: GossipSyncer(020c3b59b1854d31b94c0dd9df1019d251b4cd5565129f7ad16e3ec8c4671afd8c): state=chansSynced, type=ActiveSync
2024-07-31 06:11:19.494 [DBG] PEER: Peer(0356b462318215eda24c7d5e9e4ede517a727c9899ac6acbf273a396a4211a3792): Sending GossipTimestampRange(chain_hash=000000000933ea01ad0ee984209779baaec3ced90fa3f408719526f8d77f4943, first_stamp=2042-07-14 01:04:00 +0000 UTC, stamp_range=0) to 0356b462318215eda24c7d5e9e4ede517a727c9899ac6acbf273a396a4211a3792@<IP_ADDRESS>:8735
2024-07-31 06:11:19.494 [DBG] PEER: Peer(020c3b59b1854d31b94c0dd9df1019d251b4cd5565129f7ad16e3ec8c4671afd8c): Sending GossipTimestampRange(chain_hash=000000000933ea01ad0ee984209779baaec3ced90fa3f408719526f8d77f4943, first_stamp=2024-07-31 06:11:19 +0000 UTC, stamp_range=4294967295) to 020c3b59b1854d31b94c0dd9df1019d251b4cd5565129f7ad16e3ec8c4671afd8c@<IP_ADDRESS>:41934
2024-07-31 06:11:19.766 [ERR] CMGR: Can't accept connection: unable to accept connection from <IP_ADDRESS>:55844: EOF
2024-07-31 06:11:22.457 [DBG] LQDY: no rules configured for autoloop
2024-07-31 06:11:22.998 [DBG] UNIV: Federation envoy handling new tick event
2024-07-31 06:11:22.999 [INF] UNIV: Synchronizing with 1 federation members
2024-07-31 06:11:22.999 [INF] UNIV: Syncing Universe state with server=(universe.ServerAddr) {
 ID: (int64) 1,
 addrStr: (string) (len=40) "testnet.universe.lightning.finance:10029",
 addr: (net.Addr) <nil>
}

2024-07-31 06:11:22.999 [INF] UNIV: Attempting to sync universe: host=testnet.universe.lightning.finance:10029, sync_type=full, ids=([]universe.Identifier) <nil>

2024-07-31 06:11:23.034 [DBG] GRPC: [core] [Channel #2334] Channel created
2024-07-31 06:11:23.034 [DBG] GRPC: [core] [Channel #2334] original dial target is: "<IP_ADDRESS>:10029"
2024-07-31 06:11:23.034 [DBG] GRPC: [core] [Channel #2334] dial target "<IP_ADDRESS>:10029" parse failed: parse "<IP_ADDRESS>:10029": first path segment in URL cannot contain colon
2024-07-31 06:11:23.034 [DBG] GRPC: [core] [Channel #2334] fallback to scheme "passthrough"
2024-07-31 06:11:23.034 [DBG] GRPC: [core] [Channel #2334] parsed dial target is: {URL:{Scheme:passthrough Opaque: User: Host: Path:/<IP_ADDRESS>:10029 RawPath: OmitHost:false ForceQuery:false RawQuery: Fragment: RawFragment:}}
2024-07-31 06:11:23.034 [DBG] GRPC: [core] [Channel #2334] Channel authority set to "<IP_ADDRESS>:10029"
2024-07-31 06:11:23.034 [DBG] GRPC: [core] [Channel #2334] Resolver state updated: {
  "Addresses": [
    {
      "Addr": "<IP_ADDRESS>:10029",
      "ServerName": "",
      "Attributes": null,
      "BalancerAttributes": null,
      "Metadata": null
    }
  ],
  "Endpoints": [
    {
      "Addresses": [
        {
          "Addr": "<IP_ADDRESS>:10029",
          "ServerName": "",
          "Attributes": null,
          "BalancerAttributes": null,
          "Metadata": null
        }
      ],
      "Attributes": null
    }
  ],
  "ServiceConfig": null,
  "Attributes": null
} (resolver returned new addresses)
2024-07-31 06:11:23.034 [DBG] GRPC: [core] [Channel #2334] Channel switches to new LB policy "pick_first"
2024-07-31 06:11:23.035 [DBG] GRPC: [core] [pick-first-lb 0xc006670930] Received new config {
  "shuffleAddressList": false
}, resolver state {
  "Addresses": [
    {
      "Addr": "<IP_ADDRESS>:10029",
      "ServerName": "",
      "Attributes": null,
      "BalancerAttributes": null,
      "Metadata": null
    }
  ],
  "Endpoints": [
    {
      "Addresses": [
        {
          "Addr": "<IP_ADDRESS>:10029",
          "ServerName": "",
          "Attributes": null,
          "BalancerAttributes": null,
          "Metadata": null
        }
      ],
      "Attributes": null
    }
  ],
  "ServiceConfig": null,
  "Attributes": null
}
2024-07-31 06:11:23.035 [DBG] GRPC: [core] [Channel #2334 SubChannel #2335] Subchannel created
2024-07-31 06:11:23.035 [DBG] GRPC: [core] [Channel #2334] Channel Connectivity change to CONNECTING
2024-07-31 06:11:23.035 [INF] UNIV: Fetching 0 roots
2024-07-31 06:11:23.035 [DBG] GRPC: [core] [Channel #2334 SubChannel #2335] Subchannel Connectivity change to CONNECTING
2024-07-31 06:11:23.035 [DBG] GRPC: [core] [Channel #2334 SubChannel #2335] Subchannel picks a new address "<IP_ADDRESS>:10029" to connect
2024-07-31 06:11:23.035 [INF] UNIV: Obtained 0 roots from remote Universe server
2024-07-31 06:11:23.035 [DBG] GRPC: [core] [Channel #2334] Channel Connectivity change to SHUTDOWN
2024-07-31 06:11:23.035 [DBG] GRPC: [core] [Channel #2334] ccBalancerWrapper: closing
2024-07-31 06:11:23.035 [DBG] GRPC: [core] [pick-first-lb 0xc006670930] Received SubConn state update: 0xc006670a50, {ConnectivityState:CONNECTING ConnectionError:<nil>}
2024-07-31 06:11:23.035 [DBG] GRPC: [core] [Channel #2334] Closing the name resolver
2024-07-31 06:11:23.035 [DBG] GRPC: [core] [Channel #2334 SubChannel #2335] Subchannel Connectivity change to SHUTDOWN
2024-07-31 06:11:23.035 [DBG] GRPC: [core] [Channel #2334 SubChannel #2335] Subchannel deleted
2024-07-31 06:11:23.035 [DBG] GRPC: [core] [Channel #2334] Channel deleted
2024-07-31 06:11:23.035 [DBG] GRPC: [core] Creating new client transport to "{Addr: \"<IP_ADDRESS>:10029\", ServerName: \"<IP_ADDRESS>:10029\", }": connection error: desc = "transport: Error while dialing: dial tcp <IP_ADDRESS>:10029: operation was canceled"
2024-07-31 06:11:23.035 [WRN] GRPC: [core] [Channel #2334 SubChannel #2335] grpc: addrConn.createTransport failed to connect to {Addr: "<IP_ADDRESS>:10029", ServerName: "<IP_ADDRESS>:10029", }. Err: connection error: desc = "transport: Error while dialing: dial tcp <IP_ADDRESS>:10029: operation was canceled"
2024-07-31 06:11:29.240 [DBG] PEER: Peer(02bf82e22f99dcd7ac1de4aad5152ce48f0694c46ec582567f379e0adbf81e2d0f): Sending Ping(ping_bytes=0060e621661c7d61c0672d8816abc5deae5ebc6d7a2fda2fcaf0bebd09000000000000005f4df808c1c6368e3dcc39b9720959612162464e52adc1fb5771e06990f6e9efc6d4a966c9f21419b15c31b8) to 02bf82e22f99dcd7ac1de4aad5152ce48f0694c46ec582567f379e0adbf81e2d0f@<IP_ADDRESS>:9739
2024-07-31 06:11:29.340 [DBG] PEER: Peer(02bf82e22f99dcd7ac1de4aad5152ce48f0694c46ec582567f379e0adbf81e2d0f): Received Pong(len(pong_bytes)=1373) from 02bf82e22f99dcd7ac1de4aad5152ce48f0694c46ec582567f379e0adbf81e2d0f@<IP_ADDRESS>:9739
2024-07-31 06:11:29.340 [DBG] TCHN: Failed to handle: *lnwire.Pong
2024-07-31 06:11:29.340 [DBG] PFSM: MsgRouter: unable to route msg protofsm.PeerMsg
2024-07-31 06:11:29.766 [ERR] CMGR: Can't accept connection: unable to accept connection from <IP_ADDRESS>:49427: EOF
2024-07-31 06:11:30.221 [DBG] PEER: Peer(0356b462318215eda24c7d5e9e4ede517a727c9899ac6acbf273a396a4211a3792): Received Ping(ping_bytes=0060e621661c7d61c0672d8816abc5deae5ebc6d7a2fda2fcaf0bebd09000000000000005f4df808c1c6368e3dcc39b9720959612162464e52adc1fb5771e06990f6e9efc6d4a966c9f21419b15c31b8) from 0356b462318215eda24c7d5e9e4ede517a727c9899ac6acbf273a396a4211a3792@<IP_ADDRESS>:8735
2024-07-31 06:11:30.221 [DBG] TCHN: Failed to handle: *lnwire.Ping
2024-07-31 06:11:30.221 [DBG] PFSM: MsgRouter: unable to route msg protofsm.PeerMsg
2024-07-31 06:11:30.222 [DBG] PEER: Peer(0356b462318215eda24c7d5e9e4ede517a727c9899ac6acbf273a396a4211a3792): Sending Pong(len(pong_bytes)=3429) to 0356b462318215eda24c7d5e9e4ede517a727c9899ac6acbf273a396a4211a3792@<IP_ADDRESS>:8735
2024-07-31 06:11:30.223 [DBG] PEER: Peer(0356b462318215eda24c7d5e9e4ede517a727c9899ac6acbf273a396a4211a3792): Sending Ping(ping_bytes=0060e621661c7d61c0672d8816abc5deae5ebc6d7a2fda2fcaf0bebd09000000000000005f4df808c1c6368e3dcc39b9720959612162464e52adc1fb5771e06990f6e9efc6d4a966c9f21419b15c31b8) to 0356b462318215eda24c7d5e9e4ede517a727c9899ac6acbf273a396a4211a3792@<IP_ADDRESS>:8735
2024-07-31 06:11:30.225 [DBG] PEER: Peer(0356b462318215eda24c7d5e9e4ede517a727c9899ac6acbf273a396a4211a3792): Received Pong(len(pong_bytes)=706) from 0356b462318215eda24c7d5e9e4ede517a727c9899ac6acbf273a396a4211a3792@<IP_ADDRESS>:8735
2024-07-31 06:11:30.225 [DBG] TCHN: Failed to handle: *lnwire.Pong
2024-07-31 06:11:30.225 [DBG] PFSM: MsgRouter: unable to route msg protofsm.PeerMsg
2024-07-31 06:11:30.670 [DBG] WTCL: (taproot) Unable to get new tower candidate, retrying after 5m0s -- reason: exhausted all tower candidates
2024-07-31 06:11:30.670 [DBG] WTCL: (anchor) Unable to get new tower candidate, retrying after 5m0s -- reason: exhausted all tower candidates
2024-07-31 06:11:30.670 [DBG] WTCL: (legacy) Unable to get new tower candidate, retrying after 5m0s -- reason: exhausted all tower candidates
2024-07-31 06:11:32.653 [ERR] RPCS: [/rfqrpc.Rfq/AddAssetBuyOrder]: timeout waiting for response from peer 0356b462318215eda24c7d5e9e4ede517a727c9899ac6acbf273a396a4211a3792
2024-07-31 06:11:32.653 [DBG] GRPC: [transport] [server-handler-transport 0xc001c64320] Closing: finished writing status
2024-07-31 06:11:33.246 [DBG] PEER: Peer(032ea4d24c807bfe6df899df04f2b562a646d7467b2ab3c97cffdc98e0d1a984e4): Sending Ping(ping_bytes=0060e621661c7d61c0672d8816abc5deae5ebc6d7a2fda2fcaf0bebd09000000000000005f4df808c1c6368e3dcc39b9720959612162464e52adc1fb5771e06990f6e9efc6d4a966c9f21419b15c31b8) to 032ea4d24c807bfe6df899df04f2b562a646d7467b2ab3c97cffdc98e0d1a984e4@<IP_ADDRESS>:40576
2024-07-31 06:11:33.337 [DBG] PEER: Peer(032ea4d24c807bfe6df899df04f2b562a646d7467b2ab3c97cffdc98e0d1a984e4): Received Ping(ping_bytes=0060e621661c7d61c0672d8816abc5deae5ebc6d7a2fda2fcaf0bebd09000000000000005f4df808c1c6368e3dcc39b9720959612162464e52adc1fb5771e06990f6e9efc6d4a966c9f21419b15c31b8) from 032ea4d24c807bfe6df899df04f2b562a646d7467b2ab3c97cffdc98e0d1a984e4@<IP_ADDRESS>:40576
2024-07-31 06:11:33.337 [DBG] TCHN: Failed to handle: *lnwire.Ping
2024-07-31 06:11:33.337 [DBG] PFSM: MsgRouter: unable to route msg protofsm.PeerMsg
2024-07-31 06:11:33.337 [DBG] PEER: Peer(032ea4d24c807bfe6df899df04f2b562a646d7467b2ab3c97cffdc98e0d1a984e4): Sending Pong(len(pong_bytes)=16) to 032ea4d24c807bfe6df899df04f2b562a646d7467b2ab3c97cffdc98e0d1a984e4@<IP_ADDRESS>:40576
2024-07-31 06:11:33.338 [DBG] PEER: Peer(032ea4d24c807bfe6df899df04f2b562a646d7467b2ab3c97cffdc98e0d1a984e4): Received Pong(len(pong_bytes)=1049) from 032ea4d24c807bfe6df899df04f2b562a646d7467b2ab3c97cffdc98e0d1a984e4@<IP_ADDRESS>:40576
2024-07-31 06:11:33.338 [DBG] TCHN: Failed to handle: *lnwire.Pong
2024-07-31 06:11:33.338 [DBG] PFSM: MsgRouter: unable to route msg protofsm.PeerMsg
2024-07-31 06:11:37.259 [DBG] PEER: Peer(02146e28a3d43205b99d93c758b18d302be0086655d5a23e9bea9a6509da907dbd): Received Ping(ping_bytes=0060e621661c7d61c0672d8816abc5deae5ebc6d7a2fda2fcaf0bebd09000000000000005f4df808c1c6368e3dcc39b9720959612162464e52adc1fb5771e06990f6e9efc6d4a966c9f21419b15c31b8) from 02146e28a3d43205b99d93c758b18d302be0086655d5a23e9bea9a6509da907dbd@<IP_ADDRESS>:9735
2024-07-31 06:11:37.259 [DBG] PEER: Peer(02146e28a3d43205b99d93c758b18d302be0086655d5a23e9bea9a6509da907dbd): Sending Ping(ping_bytes=0060e621661c7d61c0672d8816abc5deae5ebc6d7a2fda2fcaf0bebd09000000000000005f4df808c1c6368e3dcc39b9720959612162464e52adc1fb5771e06990f6e9efc6d4a966c9f21419b15c31b8) to 02146e28a3d43205b99d93c758b18d302be0086655d5a23e9bea9a6509da907dbd@<IP_ADDRESS>:9735
2024-07-31 06:11:37.260 [DBG] TCHN: Failed to handle: *lnwire.Ping
2024-07-31 06:11:37.260 [DBG] PFSM: MsgRouter: unable to route msg protofsm.PeerMsg
2024-07-31 06:11:37.260 [DBG] PEER: Peer(02146e28a3d43205b99d93c758b18d302be0086655d5a23e9bea9a6509da907dbd): Sending Pong(len(pong_bytes)=4059) to 02146e28a3d43205b99d93c758b18d302be0086655d5a23e9bea9a6509da907dbd@<IP_ADDRESS>:9735
2024-07-31 06:11:37.281 [DBG] PEER: Peer(02146e28a3d43205b99d93c758b18d302be0086655d5a23e9bea9a6509da907dbd): Received Pong(len(pong_bytes)=1924) from 02146e28a3d43205b99d93c758b18d302be0086655d5a23e9bea9a6509da907dbd@<IP_ADDRESS>:9735
2024-07-31 06:11:37.281 [DBG] TCHN: Failed to handle: *lnwire.Pong
2024-07-31 06:11:37.281 [DBG] PFSM: MsgRouter: unable to route msg protofsm.PeerMsg
2024-07-31 06:11:39.766 [ERR] CMGR: Can't accept connection: unable to accept connection from <IP_ADDRESS>:54520: EOF
2024-07-31 06:11:49.766 [ERR] CMGR: Can't accept connection: unable to accept connection from <IP_ADDRESS>:56258: EOF
2024-07-31 06:11:59.358 [DBG] PEER: Peer(02bf82e22f99dcd7ac1de4aad5152ce48f0694c46ec582567f379e0adbf81e2d0f): Received Ping(ping_bytes=00000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000) from 02bf82e22f99dcd7ac1de4aad5152ce48f0694c46ec582567f379e0adbf81e2d0f@<IP_ADDRESS>:9739
2024-07-31 06:11:59.358 [DBG] TCHN: Failed to handle: *lnwire.Ping
2024-07-31 06:11:59.358 [DBG] PFSM: MsgRouter: unable to route msg protofsm.PeerMsg
2024-07-31 06:11:59.358 [DBG] PEER: Peer(02bf82e22f99dcd7ac1de4aad5152ce48f0694c46ec582567f379e0adbf81e2d0f): Sending Pong(len(pong_bytes)=939) to 02bf82e22f99dcd7ac1de4aad5152ce48f0694c46ec582567f379e0adbf81e2d0f@<IP_ADDRESS>:9739
2024-07-31 06:11:59.766 [ERR] CMGR: Can't accept connection: unable to accept connection from <IP_ADDRESS>:52706: EOF

Thanks for the additional information. So that means you don't yet have an asset channel between node 1 and node 2?
RFQ quotes can only be requested once a channel with the given asset exists. But we should probably catch that earlier and return a more useful error message.

Yes we don't have a channel between node1 and node 2.

Created this issue to help users use the RPC endpoints correctly: https://github.com/lightninglabs/taproot-assets/issues/1053

Closing, as the shutdown problem was addressed with https://github.com/lightninglabs/taproot-assets/pull/1011 and the remaining problem is tracked in https://github.com/lightninglabs/taproot-assets/issues/1053.


templates_config_context not defined

Hey,
in the latest version "templates_config_context" (218) is not defined and there comes an error.

I might have pushed some code yesterday that was contaminated with code that was meant for a different branch. Will look at it ASAP.

Can you do a pull again on the main repo and check if the script works again?

Yes it works
This afternoon I already removed it manually for our production. Didn't want to create a pull request because I thought it was something for the future


Asciimatics doesn't print anything.

Describe the bug
If I run something, terminal screen just blink one time and script stop working.
To Reproduce
from asciimatics.widgets import Frame, Layout, Button
from asciimatics.screen import Screen

def main(screen):
    frame = Frame(screen, 80, 20, has_border=False)
    layout = Layout([1, 1, 1, 1])
    frame.add_layout(layout)

    layout.add_widget(Button("Button 1", lambda: print("Button 1 pressed")), 0)

Screen.wrapper(main)

Expected behavior
It must create button.
Screenshots

I wrote there "python main.py"
System details (please complete the following information):

OS and version: Windows 10
Python version: 3.9.13
Python distribution: Python 3.9.13 (python -V)
Asciimatics version: 1.14.0

Additional context
Please help!

You haven't created a Scene and then told the screen to play it.  Take a look at https://github.com/peterbrittain/asciimatics/blob/31b3fe579af6ef08bcd8e01e33aeaf8d46805353/samples/contact_list.py#L175-L180

how do i add to scenes my main function? i dont have any ListView, or ContactView..


Make a !suggest command

I'm not sure if it's possible - but a !suggest command that would connect to the GitHub API and make a new issue. The issue would be made by a bot account, but would mention the twitch user in the description

I think this is a not a good feature, but I'll let @pajlada weigh in first.

Not really an api I want to interact with from a Twitch bot, so the so the way its described in this issue is a no for me too.


Create a progress bar for downloading youtube

use tqdm for the progress bar

maybe it is not possible because all the process runs inside the pytubefix lib


Support for husky >=2

The current library has been tested with husky 1.x, update the library to support higher versions of husky.

You can currently make it work just fine if you do:
HUSKY_GIT_PARAMS="$1" npx --no -- git-commit-template .commit-msg

The prepare-commit-msg script I’m currently using is:
.husky/prepare-commit-msg
#!/bin/sh
. "$(dirname "$0")/_/husky.sh"

pwd

COMMIT_MSG_FILE=$1  # name of file that contains the commit log message
COMMIT_SOURCE=$2    # message, template, merge, squash, commit
COMMIT_SHA=$3       # exists if amending or reusing a commit

# If there is no commit source then we don't have a template and are just doing `git commit`
# Override any global git templates that are already set
if [ "$COMMIT_SOURCE" == "" -o "$COMMIT_SOURCE" == "template" ]; then
  echo "" > $COMMIT_MSG_FILE
  HUSKY_GIT_PARAMS="$COMMIT_MSG_FILE" npx --no -- git-commit-template .husky/.commit-template
fi

fwiw I also have
.husky/commit-msg
#!/bin/sh
. "$(dirname "$0")/_/husky.sh"

npx --no -- devmoji --edit "$1" && \
npx --no -- commitlint --edit "$1"

.husky/pre-commit
#!/bin/sh
. "$(dirname "$0")/_/husky.sh"

npx --no -- lint-staged


Glances sensor problems & suggestions

My network has three Raspberry Pis. All of them run glances, one is also the home-assistant server, monitoring various aspects of each of them.

Problem If one of the Pis is down at the time that home-assistant is started, it's sensors will never appear on the home-assistant web interface even if you reload the page. You have to restart hass.
It would clearly be better for system monitoring if the Pi automatically show up once it is running.

The entity names that hass generates from glances are (eg) sensor.cpu_load, sensor.cpu_load_2, sensor.cpu_load_3 etc.
It is quite hard to work out which of these relates to which Raspberry Pi.
Suggestion: I can make it a bit easier by adding a new sensor 'hostname' to glances.py
This addition (3 new lines of code) is probably worth retaining - assuming that glances returns the hostname for all platforms.

I have to define groups so that the display shows a card for each Pi:

group:
      RedPi (Server):
        - sensor.hostname
        - sensor.cpu_load
        - sensor.disk_use
        - sensor.ram_use
      RPiA:
        - sensor.hostname_2
        - sensor.cpu_load_2
        - sensor.disk_use_2
        - sensor.ram_use_2
      RPiB:
        - sensor.hostname_3
        - sensor.cpu_load_3
        - sensor.disk_use_3
        - sensor.ram_use_3

Problem:, the relationship between entity name and target machine can change and I end up with the sensor data from RPiA on my RPiB card.
Suggestion: One possible way to resolve this issue would be to include the name: attribute of the sensor: stanza in the entity name.
So my
    sensor 2:
      - platform: glances
        name: RedPi
        host: <IP_ADDRESS>
        resources:
          - 'hostname'
          - 'disk_use_percent'
          - 'memory_use_percent'
          - 'processor_load'

would generate entities
    - sensor.RedPi_hostname
    - sensor.RedPi_cpu_load
    - sensor.RedPi_disk_use
    - sensor.RedPi_ram_use

The Glances sensor doesn't do discovery. The issue is that an additional part on the device which you want to monitor is needed if you want it automatically discoverable. The work-around would be to disable the presence check while setting up the sensor and wait for the timeout. The downside is that as long as the device is down the frontend elements are just sitting around.

& 3.  Looks like both problems could be solved by adding an optional name configuration key.

@fabaff: About your last point 'Looks like both problems could be solved by adding an optional name configuration key'.
Is this something that is there already?  If so, can you point me in the right direction?
Thanks,
Frank

I may have mininterpreted fabaff's response...
I already have a name configuration key - name : "RedPi" in the above Sensor 2 stanza and it does nothing to help identify which entity applies to this machine.
Indeed my suggestion was that the entity name should include the optional name configuration key, if any.

Yes, the entity name should be changed.

"The example contains this key but not the code."
My python skills were not up to the task!

I will fix it.

This was merged and will be available with the next release.


be服务启动失败

版本[starrocks-3.3.3]be服务启动失败
运行./be/bin/start_be.sh --daemon后，
查看be.out文件:/media/hdd1/temp/database/starrocks/be/lib/starrocks_be: error while loading shared libraries: libbfd-2.38-system.so: cannot open shared object file: No such file or directory
系统ubuntu18.04
缺少这个“libbfd-2.38-system.so”链接库文件，需要怎么补？

@bayueqiankong please install libbinutils on your system

运行 sudo apt-get install binutils-dev
显示 binutils-dev is already the newest version (2.30-21ubuntu1~18.04.9).
libbinutils 已安装，但仍然不是目标版本，怎么更新到指定版本？

Basically you can't run the binary on ubuntu 18.04 where it was built from ubuntu 22.04.
You can try following ways:

upgrade your operating system to ubuntu 22.04,
or run the starrocks in docker env with host OS remaining in 18.04,
or rebuild from source code on ubuntu 18.04,
or give a try to run centos7 binary on ubuntu 18.04.


Adapt ros control api

There have been upstream changes regarding stopped controllers and querying the interface name inside controllers.

For reference, these are the ros2_control changes requiring this:

https://github.com/ros-controls/ros2_control/pull/737
https://github.com/ros-controls/ros2_control/pull/755


[$500] IOU-For User B, receipt removed is not updated in real time & receipt page loading infinitely

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

Version Number: 1.3.96-0
Reproducible in staging?: Y
Reproducible in production?:  N
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause-Internal Team
Slack conversation: @
Action Performed:
1.Launch app
2.Open a 1:1 report
2.Tap request money--- manual
3 Enter an amount, tap 3 dots on top and add a receipt, enter description& merchant
4.Tap request
5 Open User B iou detail page
6.In user A, Iou details page, tap receipt and replace receipt
7.Note changed receipt can be seen in user B iou details page
8.In user A, tap receipt and delete it
9.In user B's iou details page, the receipt deleted is not updated in real time.
10.Tap header "from"
11.Tap IOU
12.Tap the green label
Expected Result:
For User B, the receipt removed must be updated in real time & tapping green label, the receipt page must not load infinitely.
Actual Result:
For User B, the receipt removed is not updated in real time & tapping green label, the receipt page loads infinitely.
Workaround:
Unknown
Platforms:

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

[x] Android: Native
[x] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
Add any screenshot/video evidence
https://github.com/Expensify/App/assets/115492554/b59ea605-83d7-4d9f-b9e5-cfedc5d78591
https://github.com/Expensify/App/assets/115492554/abf162c2-8e48-44a0-b2ba-6bd779ff307a

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01057ef6486c923811
Upwork Job ID:<PHONE_NUMBER>537888768
Last Price Increase: 2023-11-08

Error page opens in production instead of loading spinner.
https://github.com/Expensify/App/assets/115492554/faece3f6-bc20-467e-bdc6-af7c790ed2f5

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.

This may be fixed here: https://github.com/Expensify/App/issues/29462
I think there is the same root cause of having the mergeCollection method instead of SET...

@luacmartins is this dupe or related to #29462?

I think it has the same root cause. We can close it in favor of https://github.com/Expensify/App/issues/29462

Demoting to NAB since it also happens in prod. Closing in favor of https://github.com/Expensify/App/issues/29462


Mistakes in Documentation

There are few grammatical errors in the contributing.md file and there can be some changes done in it to make it more friendly

@Abhishek-kumar09 i would like to solve this errors can you assign it to me ??

@Abhishek-kumar09  I will take care of this. No worries!


circleci: fix nightly job clobber of the build/test env settings

The yaml macros for the nightly job's env settings were getting clobbered by the subsequent use of the "environment:" key containing the TAG setting.  Yaml doesn't do an auto-merge of dicts/maps :-)
Changed to put the tag setting in each command-line for now to make it clear.
Troubleshooting note:  use the circleci "configuration" tab on the job view to see the resulting yaml that circleci sees--it has the result of using all those yaml inline macros (references/aliases).

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approver: tiswanso
If they are not already assigned, you can assign the PR to them by writing /assign @tiswanso in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


User should be asked to enter their full name in register step

Users should complete their profile (full_name) in order to be able to write stories and story parts. We need to ask for their full name when they're signing up to prevent extra steps in the future.
Criteria

[ ] In the register screen we should ask for three mandatory fields:

full name
email address (already exists)
password (already exists)

Reproducing Steps

Anonymous user tries to create a story [story part].
Novel will show an error that they need to be authenticated and redirect them to the login screen.
User register with their email address and password and after verifying their email address they get redirected to Novel.
They try to create a story [story part] again. They write their story [story part] and hit Enter to submit it.
Novel will show another error, saying that they need to complete their profile, and redirect them to the Profile screen.
User's story is gone as they got redirected without their story [story part] being saved.

Hi @thevahidal !
I would love to work on that. Could you assign it to me, please ?

Hi @mnosov622,
Thanks for coming forward to collaborate on Novel. I'd love to see you working on this task, too.
You can start I'll assign it to you, but I have to provide some information for you to run the project locally as right now we don't have anything on how to do it.
Also, I'll add some contribution guidelines and a code of conduct so everyone can follow the same rules.
Thanks again, and I assigned this to you. Good luck and can't wait to see your PR.

Hi @thevahidal !
Thank you so much !

For now, my suggestion is to have down-vote and up-vote icons in the bottom right corner

As well as in the top of the story. What do you think ?

@thevahidal and could you tell me who do I run this project locally, please ?

@thevahidal and could you tell me who do I run this project locally, please ?

I'm creating a development guide and will finish it asap. You can follow it in this issue #35 .

Got it !
Let me know when it's ready please :)
On Sat, Nov 26, 2022, 1:32 PM Vahid Al @.***> wrote:

@thevahidal https://github.com/thevahidal and could you tell me who do
I run this project locally, please ?
[image: image]
https://user-images.githubusercontent.com/73063742/204095590-7b8f0698-826a-4d38-9bb7-5f10d692e7cb.png
I'm creating a development guide and will finish it asap. You can follow
it in this issue #35 https://github.com/thevahidal/novel/issues/35 .
—
Reply to this email directly, view it on GitHub
https://github.com/thevahidal/novel/issues/17#issuecomment-1328094039,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARNN2PVCIY3OE5EVEEW3ZPDWKJJUVANCNFSM6AAAAAASLU6NBI
.
You are receiving this because you were assigned.Message ID:
@.***>

Hi @thevahidal !
Do you mind exchanging with discord or something like that, so we can talk more about the project ?
I would love to work with you on your project :) I like the idea.

Hey @mnosov622,
Please send me your email address so I can give you my contact info.

Hi !
Sure. @.***
On Mon, Nov 28, 2022, 1:18 AM Vahid Al @.***> wrote:

Hey @mnosov622 https://github.com/mnosov622,
Please send me your email address so I can give you my contact info.
—
Reply to this email directly, view it on GitHub
https://github.com/thevahidal/novel/issues/17#issuecomment-1328597938,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARNN2PX43Y236I25WPQHL5TWKRFBZANCNFSM6AAAAAASLU6NBI
.
You are receiving this because you were mentioned.Message ID:
@.***>

@mnosov622,
It doesn't show your email address, it's like this @.***

Oh, really.
Let's do it that way. My email is my login: mnosov622 + gmail.com


Could not run 'aten::index_select' on RX 6700

I'm getting an error on the embedding step when specifying the device as torch.device("dml"). I suspect this is related to a feature not yet supported in the preview but not sure. I have no issues running using cpu as a device, but when trying to use dml:[0,1] (trying to use my AMD RX 6700 GPU) I get the below error:
File "C:\Users\user-pc\miniconda3\envs\pytorch_env\lib\site-packages\torch\nn\modules\module.py", line 889, in _call_impl
    result = self.forward(*input, **kwargs)
File ".\test.py", line 110, in forward
  embeddings = self.embedding(inputs)
File "C:\Users\user-pc\miniconda3\envs\pytorch_env\lib\site-packages\torch\nn\modules\module.py", line 889, in _call_impl
  result = self.forward(*input, **kwargs)
File "C:\Users\user-pc\miniconda3\envs\pytorch_env\lib\site-packages\torch\nn\modules\sparse.py", line 145, in forward
  return F.embedding(
File "C:\Users\user-pc\miniconda3\envs\pytorch_env\lib\site-packages\torch\nn\functional.py", line 1913, in embedding
  return torch.embedding(weight, input, padding_idx, scale_grad_by_freq, sparse)
RuntimeError: Could not run 'aten::index_select' with arguments from the 'UNKNOWN_TENSOR_TYPE_ID' backend. This could be because the operator doesn't exist for this backend, or was omitted during the selective/custom build process (if using custom build). If you are a Facebook employee using PyTorch on mobile, please visit https://fburl.com/ptmfixes for possible resolutions. 'aten::index_select' is only available for these backends: [CPU, SparseCPU, BackendSelect, Named, AutogradOther, AutogradCPU, AutogradCUDA, AutogradXLA, AutogradNestedTensor, UNKNOWN_TENSOR_TYPE_ID, AutogradPrivateUse1, AutogradPrivateUse2, AutogradPrivateUse3, Tracer, Autocast, Batched, VmapMode].

CPU: registered at D:\a\_work\1\s\build\aten\src\ATen\RegisterCPU.cpp:5926 [kernel]
SparseCPU: registered at D:\a\_work\1\s\build\aten\src\ATen\RegisterSparseCPU.cpp:558 [kernel]
BackendSelect: fallthrough registered at D:\a\_work\1\s\aten\src\ATen\core\BackendSelectFallbackKernel.cpp:3 [backend fallback]
Named: registered at D:\a\_work\1\s\aten\src\ATen\core\NamedRegistrations.cpp:7 [backend fallback]
AutogradOther: registered at D:\a\_work\1\s\torch\csrc\autograd\generated\VariableType_1.cpp:9665 [autograd kernel]
AutogradCPU: registered at D:\a\_work\1\s\torch\csrc\autograd\generated\VariableType_1.cpp:9665 [autograd kernel]
AutogradCUDA: registered at D:\a\_work\1\s\torch\csrc\autograd\generated\VariableType_1.cpp:9665 [autograd kernel]
AutogradXLA: registered at D:\a\_work\1\s\torch\csrc\autograd\generated\VariableType_1.cpp:9665 [autograd kernel]
AutogradNestedTensor: registered at D:\a\_work\1\s\torch\csrc\autograd\generated\VariableType_1.cpp:9665 [autograd kernel]
UNKNOWN_TENSOR_TYPE_ID: registered at D:\a\_work\1\s\torch\csrc\autograd\generated\VariableType_1.cpp:9665 [autograd kernel]
AutogradPrivateUse1: registered at D:\a\_work\1\s\torch\csrc\autograd\generated\VariableType_1.cpp:9665 [autograd kernel]
AutogradPrivateUse2: registered at D:\a\_work\1\s\torch\csrc\autograd\generated\VariableType_1.cpp:9665 [autograd kernel]
AutogradPrivateUse3: registered at D:\a\_work\1\s\torch\csrc\autograd\generated\VariableType_1.cpp:9665 [autograd kernel]
Tracer: registered at D:\a\_work\1\s\torch\csrc\autograd\generated\TraceType_1.cpp:11324 [kernel]
Autocast: fallthrough registered at D:\a\_work\1\s\aten\src\ATen\autocast_mode.cpp:250 [backend fallback]
Batched: registered at D:\a\_work\1\s\aten\src\ATen\BatchingRegistrations.cpp:1016 [backend fallback]
VmapMode: fallthrough registered at D:\a\_work\1\s\aten\src\ATen\VmapModeRegistrations.cpp:33 [backend fallback]

Thanks for checking out PyTorch+DirectML!
You are correct.
The aten::index_select operator isn't implemented in the DirectML backend for PyTorch in the current prerelease.
We are working towards broadening our operator coverage and will update this thread when we have more details on our operator roadmap.

Didn't want to open a new issue but having aten::silu implemented would be great.

Thanks for your submission! We are actively adding new operator support to PyTorch-DML, so thank you for your patience and being one of our early users. Please visit the PyTorch-DirectML Operator Roadmap for guidance on current and future support.


Big latency

When I emit event event(new \App\Events\Ping()) and before the client received message there is a latency from 1 to 3 seconds. It is not like realtime. I want to user receive messages immediately as possible.
In logs of "laravel-echo-server" event is also appeared after 1-3 seconds.

// laravel-echo-server.json
{
  "authHost": "http://api.local",
  "authEndpoint": "/auth/broadcasting",
  "clients": [
    {
      "appId": "xxxxxxxxxxx",
      "key": "xxxxxxxxxxxxxxxxxxxxxxxxxx"
    }
  ],
  "database": "redis",
  "databaseConfig": {
    "redis": {},
    "sqlite": {
      "databasePath": "/database/laravel-echo-server.sqlite"
    }
  },
  "devMode": true,
  "host": null,
  "port": "8002",
  "protocol": "http",
  "socketio": {},
  "sslCertPath": "",
  "sslKeyPath": "",
  "sslCertChainPath": "",
  "sslPassphrase": "",
  "apiOriginAllow": {
    "allowCors": true,
    "allowOrigin": "http://localhost:80",
    "allowMethods": "GET, POST",
    "allowHeaders": "Origin, Content-Type, X-Auth-Token, X-Requested-With, Accept, Authorization, X-CSRF-TOKEN, X-Socket-Id"
  }
}

What is a problem can be here?

I've found the way to fix it.
To avoid latencies event class should implements ShouldBroadcastNow instead of ShouldBroadcast!

@JILeXanDR  thank you , i had a latency of 1-3 secondes with shouldbroadcast, but with shouldbroadcastnow there is no latency


Does scrcpy have some kind of api?

Hi, I want to write my application using scrcpy as a basis, is there an api through some protocol? For example a socket or other network protocol

There is no libscrcpy, but you can use the server only and write your own client. However, there is absolutely no guarantee of protocol stability (it is an internal protocol for scrcpy and may change at any time).
I have to document how to use the server somewhere, but you can get an example here (based on scrcpy v1.25).


Accessibility contrast tweaks

Make the light code theme have accessible contrast.
Docsearch placeholder contrast tweak

Also minor tweak to the prismjs tokenizer to fix optional property highlighting

All changed packages have been documented.

You can try these changes at https://cadlplayground.z22.web.core.windows.net/prs/3026/
Check the website changes at https://tspwebsitepr.z22.web.core.windows.net/prs/3026/


Refined storage pattern grid saying current workstation does not support recipe

refined storage pattern grid should be able to add recipe patterns no matter the workstation but it doesnt work with this mod please fix this.

Make sure JEI is installed to forward the support.

Make sure JEI is installed to forward the support.
still doesnt work?


EXPRMT: debug registry

Type of change

Bugfix
Enhancement / new feature
Refactoring
Documentation

Description

Checklist

[ ] Update/write design documentation in ./documentation/design
[ ] Write tests and make sure they pass
[ ] Update documentation
[ ] Check RBAC rights for Kubernetes / OpenShift roles
[ ] Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
[ ] Reference relevant issue(s) and close them after merging
[ ] Update CHANGELOG.md

@enmasse-ci run tests profile=smoke

@enmasse-ci run tests profile=smoke

:x: Test Summary :x:
TEST_PROFILE: smoke
TEST_CASE:
TOTAL: 14
PASS: 11
FAIL: 3
SKIP: 0
BUILD_NUMBER: 1361
BUILD_ENV: oc cluster up
:heavy_exclamation_mark: Test Failures :heavy_exclamation_mark:

smoketest in io.enmasse.systemtest.isolated.standard.SmokeTest
testCreateDeleteAddressSpace in io.enmasse.systemtest.isolated.brokered.SmokeTest
testAddressTypes in io.enmasse.systemtest.isolated.brokered.SmokeTest

:x: Test Summary :x:
TEST_PROFILE: smoke
TEST_CASE:
TOTAL: 14
PASS: 11
FAIL: 3
SKIP: 0
BUILD_NUMBER: 1361
BUILD_ENV: oc cluster up
:heavy_exclamation_mark: Test Failures :heavy_exclamation_mark:

smoketest in io.enmasse.systemtest.isolated.standard.SmokeTest
testCreateDeleteAddressSpace in io.enmasse.systemtest.isolated.brokered.SmokeTest
testAddressTypes in io.enmasse.systemtest.isolated.brokered.SmokeTest


Baklava: Discord-Like System Tray & Auto-Hide Default Menu

Updates to the Electron app.

Discord-like system tray (click to focus, right click to see context menu)
Auto-hide the default electron menu (can access with alt if you need to. seems useless though, until we make our own)

Sorry, wrong target


getting alert by email and other ways

Feature Request
Short Description
there should be the way to get alert by email and other way (slack,telegram etcd)
Is your feature request related to a problem? Please describe the use case.
How to know about suspicious behavior ?
Describe the solution you'd like
I want to get email after some actions blocked or been audited
Describe alternatives you've considered
falco has different ways to do alert like program output. which may run program send email or curl webhook for posting to slack.
Maybe i missed , How to send alert about kubearmor security event ?

One of example is falcosidekick, which forward falco events to different outputs and you can do everything with them. How can i operate with kubearmor events ?

Hey @cloud-66 thanks for raising this request. this is on our roadmap and we have already started working on sending events to falco sidekick.
this feature will be out soon

KubeArmor now support sidekick as well!


I installed a script on Windows 10 Home and lost access to my PC

Discussed in https://github.com/simeononsecurity/Windows-Optimize-Harden-Debloat/discussions/41

Originally posted by xFELAx September  1, 2022
Hi! I installed this script on my Windows 10 Home.  After rebooting I can't login into my microsoft account. When I try to login there is a message: "Something went wrong and your PIN isn't available (status: 0xc000015b, substatus:0x0 Restart your device to see if that fixes the problem". I searched for the fix online but nothing helped. When I try to do something in a safe mode I realized that there is only available a new X_Admin account but I don't know the password for this account. Could you help me to regain access to my PC? Sorry for a problem. :/

Microsoft account signins are not supported by this script or by DoD STIGs, which are documented in the readme of this repo. Additionally, you are to test this script on a VM or clean install before ever running in on any personal system.
The X_Admin account is to satisfy the hardening recommendations and requirements to lock down the local administrator account. This is not your account, it is a built in default account of windows installs. Unless you've previously configured it, it does not have a password and the account is disabled via GPO.
Unfortunately here, the best option you have is to reinstall windows.


fix(table viz): correctly sort by multiple columns in a table

Recent commit to sort alphanumeric columns via case insensitive
comparison broke the multi-column sort option. React-table only sorts
by the second (or third...) column if the first column matches.
Since the alphanumeric sort only returned -1 or 1, it never would move
to the subsequent columns when the earlier column values matched.
SUMMARY
prior commit only returned -1 or +1, resulting in a value of -1 when two rows had the same value for a given column.
BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF
Unsorted:

Sorted by Platform:

Sorted by Platform AND Global Sales (broken):

Sorted by Platform and Global Sales (fixed):

TESTING INSTRUCTIONS
I added a new test to check for properly sorting by multiple columns (using react-table's
ADDITIONAL INFORMATION

[X] Has associated issue: #19919
[ ] Required feature flags:
[X] Changes UI
[ ] Includes DB Migration (follow approval process in SIP-59)

[ ] Migration is atomic, supports rollback & is backwards-compatible
[ ] Confirm DB migration upgrade and downgrade tested
[ ] Runtime estimates and downtime expectations provided

[ ] Introduces new feature or API
[ ] Removes existing feature or API

For reference, there's something on the react-table repo about this too
https://github.com/TanStack/react-table/issues/3512

@stephenLYZ @kgabryje anything else you think this needs?