should_not_be for element in collection wait all timeout even in success case

    from selene.support.jquery_style_selectors import ss
    from selene.conditions import in_dom
    from selene import config

    config.timeout = 100500
    browser.open_url('https://google.com')
    elem = ss('[name=q]').first()
    elem.should_be(in_dom)
    browser.open_url('https://ya.ru')
    elem.should_not_be(in_dom)

last string will wait all timeout and finished with success, but should check element state once.

Still seems to be a problem even in 2.0.0a22 ver. and not only should_not_be, but should_not too.  But in 2.0.0a22 these methods are marked as deprecated and it's recommended to use
should(be.not_.in_dom)
or
should(not_(be.in_dom))
    def should_not_be(self, condition: ElementCondition, timeout=None) -> Element:
        warnings.warn(
            "deprecated; use `should` method with `be.not.*` or `have.no.*` style conditions instead: "
            "`browser.element('#foo').should(be.not.enabled).should(have.no.css_class('bar')`, "
            "you also can build your own inverted conditions by: `not_ok = Condition.as_not(have.text('Ok'))`",
            DeprecationWarning)
        return self.should(inver, timeout)

Then @ibalagurov's example in ver 2.0.0a22 will look like:
from selene import be
from selene import config
from selene.core.condition import not_
from selene.support.jquery_style_selectors import ss
from selene.support.shared import browser

def test_should_not():
    config.timeout = 100500
    browser.open_url('https://google.com')
    elem = ss('[name=q]').first
    elem.should_be(be.in_dom)
    browser.open_url('https://ya.ru')
    elem.should(be.not_.in_dom)

@yashaka will should_not_be and should_not be fixed, or it will be deleted soon?

Still seems to be a problem even in 2.0.0a22 ver. and not only should_not_be, but should_not too.  But in 2.0.0a22 these methods are marked as deprecated and it's recommended to use
should(be.not_.in_dom)
or
should(not_(be.in_dom))
    def should_not_be(self, condition: ElementCondition, timeout=None) -> Element:
        warnings.warn(
            "deprecated; use `should` method with `be.not.*` or `have.no.*` style conditions instead: "
            "`browser.element('#foo').should(be.not.enabled).should(have.no.css_class('bar')`, "
            "you also can build your own inverted conditions by: `not_ok = Condition.as_not(have.text('Ok'))`",
            DeprecationWarning)
        return self.should(inver, timeout)

Then @ibalagurov's example in ver 2.0.0a22 will look like:
from selene import be
from selene import config
from selene.core.condition import not_
from selene.support.jquery_style_selectors import ss
from selene.support.shared import browser

def test_should_not():
    config.timeout = 100500
    browser.open_url('https://google.com')
    elem = ss('[name=q]').first
    elem.should_be(be.in_dom)
    browser.open_url('https://ya.ru')
    elem.should(be.not_.in_dom)

@yashaka will methods should_not_be and should_not be fixed, or it will be deleted soon?

Will be deleted soon...

@aleksandr-kotlyar and with should(...) it works, doesn't it?

Yeah, it works, sorry, forgot to mention it. I have updated my previous reply. :)

fixed in 2.*


Beckn-Onix spec version 1.0 Document Review & Rework

Back Story
@rajaneeshk90 has sent this for review to Ravi and Binu & Tanya from ONDC (Binu has added some comments and those have been resolved). The review request has been sent on Sep 6.
The deliverable for this is part of the document here: https://docs.google.com/document/d/1JlE-JTgQCPVPtFUqs3dIfBma3Koi_pVsO4LwB4hGcM8/edit#heading=h.m1mzlygez2v3
Reference Card
#99

@vbabuEM - This card is a duplicate of #226 hance closing this card.
@viraj89 @emmayank @faizmagic


MF-314 - Investigate MQTT clustering

MQTT adapter wasn't scalable because mq emitter wasn't setup. Now
it's working as intended. You can create two different instances
and exchange messages between their clients.
This PR resolves #314.
Signed-off-by: Aleksandar Novakovic<EMAIL_ADDRESS>

Codecov Report

Merging #526 into master will decrease coverage by 0.08%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master     #526      +/-   ##
==========================================
- Coverage   87.07%   86.99%   -0.09%
==========================================
  Files          53       53
  Lines        2399     2399
==========================================
- Hits         2089     2087       -2
- Misses        213      215       +2
  Partials       97       97

Impacted Files
Coverage Δ

things/service.go
92.14% <0%> (-1.43%)
:arrow_down:

Continue to review full report at Codecov.

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

@anovakovic01 fantastic!

@anovakovic01 cool, nice and clean solution :)

Merged!


handle failures more gracefully when extracting metadata from setup.py

@aspiers can you rebase please if you still think this is needed? I think I fixed the underlying problem...

@toabctl Argh, you changed everything! This is not a trivial rebase :-( What do you mean by "fixed the underlying problem"? Can you summarise what you did, other than moving the parsing to a separate file?

@aspiers the fix is https://github.com/saschpe/py2pack/commit/b1d14894a7b340d0d52bf54d54aefc5bf56f979f .

@aspiers btw. I'm working on a fpm inspired solution for the dependency detection. Thanks for that pointer!

Oh, but that only improves the case where the user is assume that the Python code is parseable as a trivial data structure.  IIRC that has nothing to do with --run, so it doesn't fix many of the cases where it references other variables / functions etc.  The sandbox case still needs to fail gracefully - or did you change that too?

@aspiers not yet. But I'm doing that currently...

OK, well hopefully you can reuse some of my work in this PR rather than doing it from scratch. It would be shame if my efforts were totally wasted ...

@aspiers I added the first commit (https://github.com/saschpe/py2pack/pull/42/commits/e7a3abd3a35d9e577c9daf001cf1c71346a5abec ) to https://github.com/saschpe/py2pack/pull/45 . The second commit (https://github.com/saschpe/py2pack/pull/42/commits/6a3620450153a936105d836d672689951650cc03 ) is no longer useful I think. I fixed the setup run (using the same approach the fpm project uses)

See https://github.com/saschpe/py2pack/pull/42#issuecomment-229292028


Add M1 Support

This adds Mac M1 Support by passing the flag -DCPU=M1 to cmake.
Tested on Mac Mini with M1 CPU.
README updated accordingly.

Thanks! It's really helpful.


The binary operator Equal is not defined for the types 'System.Nullable`1[System.Guid]' and 'System.Guid'.

Hi,
I have come across a problem running a query to get the count(s) of child collections, the exact same code is OK with EF6:
            IQueryable<IRClaim> dbQuery = _context.Set<IRClaim>().AsNoTracking();

            var counts = (from c in dbQuery
                          select new
                          {
                              CountA = c.Collection1.Count,
                              CountB = c.Collection2.Count,
                              CountC = c.Collection3.Count
                          }).FirstOrDefault();

The error is:
"The binary operator Equal is not defined for the types 'System.Nullable`1[System.Guid]' and 'System.Guid'."
I have just updated the model in my EF7 solution to use the Fluent API for configuration and I haven't reflected these changes in my EF6 solution yet, but I didn't think this would be related(?). Despite the different configuration (Annotations vs Fluent API) the models produce the same database structure.

Can you include code for your DbContext and the entities used in the query?

Hi, I have some issues with sharing this publicly, but I can share it privately if that is OK.
From: Maurycy Markowski<EMAIL_ADDRESS>Sent: 18 November 2015 17:49
To: aspnet/EntityFramework<EMAIL_ADDRESS>Cc: ChangedHourly<EMAIL_ADDRESS>Subject: Re: [EntityFramework] The binary operator Equal is not defined for the types 'System.Nullable`1[System.Guid]' and 'System.Guid'. (#3782)
Can you include code for your DbContext and the entities used in the query?
—
Reply to this email directly or view it on GitHub https://github.com/aspnet/EntityFramework/issues/3782#issuecomment-157797659 .  https://github.com/notifications/beacon/ALMjKWsn6VTeQELNVdYK9bhW-TNLLQKeks5pHLF0gaJpZM4Gk0MJ.gif

@ChangedHourly  I sent you an email to which you can reply with the repro code

This issue has been fixed in the current bits, probably by the following commit:
https://github.com/aspnet/EntityFramework/commit/41ad57ad2f3755c5e35b51d939fab52b489ce738
However, the repro uncovers a different issue, most likely a duplicate of #3616
Will keep it open, just in case, until we are sure that those two issues have the same root cause.

repro for the second issue:
classes:
    public class Foo
    {
        public int Id { get; set; }
        public string Name { get; set; }

        public ICollection<Bar> Bars { get; set; }
        public ICollection<Baz> Bazs { get; set; }
    }

    public class Bar
    {
        public int Id { get; set; }
        public string Name { get; set; }
    }

    public class Baz
    {
        public int Id { get; set; }
        public string Name { get; set; }
    }

query:
ctx.Foos.Select(f => new { c1 = f.Bars.Count, c2 = f.Bazs.Count }).ToList();

sql we produce is the following:
SELECT (
    SELECT COUNT(*)
    FROM [Baz] AS [b]
    WHERE [f].[Id] = [b].[FooId]
)
FROM [Foo] AS [f]

Fixed in e697bd49359b50e4a385f199c0e4aabff769aca2


System.Random isnt always very random

https://github.com/amido/NAuto/blob/a2928c4ee349d9a2613234c5cf47a13576060d24/Amido.NAuto/Randomizers/RandomNumberGenerator.cs
There are examples of System.Random throughout the codebase.  There is a lot of evidence backing up that System.Random isnt truely random, thereby impacting test results in some cases.

@td444 do you have any articles regarding this?
I think adding a cryptographic randomiser would be beneficial instead of replacing the existing one.
What do you think?


Go to Definition sample

Hi,
Could you please publish an example for implementing the 'Go to Definition' feature?
I am planning to implement this feature for a proprietary programming language. I have checked how this is done in Python/Go, however, they are really not newbie friendly, especially I am still new to TypeScript.
If such a sample is available that will do great help to those having the same needs!
Thanks!

Closing this due to lack of further feedback.
In general though, implementing go to definition is quite similar to many other language features, such as completions

Closing this due to lack of further feedback.
In general though, implementing go to definition is quite similar to many other language features, such as completions


How to I check whether a certain key can be found in the settings heirarchy?

I'd like to check if my session .json contains a certain key (e.g. objectRotationSpeed) and use that value if it exists and assign a default value if it doesn't.  For that I have to check whether the key objectRotationSpeed exists in the settings heirarchy but I don't know how to do this.
Something like:
if(session.settings.GetFloat("objectRotationSpeed") == null){
\\\\ Assigning default value
}

But if I do this I get the following error:
KeyNotFoundException: The key "objectRotationSpeed" was not found in the settings heirarchy. Use UXF Session Debugger (UXF menu at top of unity editor) to check your settings are being applied correctly.

I've tried to use this https://learn.microsoft.com/en-us/dotnet/api/system.collections.generic.dictionary-2.keycollection?view=net-8.0 by accessing session.settings.Keys.Contains(key) because session.settings.Keys seem to be a 'Dictionary<string, object>.KeyCollection' , however I still get
error CS1061: 'Dictionary<string, object>.KeyCollection' does not contain a definition for 'Contains' and no accessible extension method 'Contains' accepting a first argument of type 'Dictionary<string, object>.KeyCollection' could be found (are you missing a using directive or an assembly reference?)

This works
        foreach(var key in session.settings.Keys){
            Debug.Log(key);
        }


srht.el package: *.el files stored in ./lisp subdir

Hi,
I just installed the srht package, which is on ELPA, with straight.el. I cannot require the srht feature, presumably because the package stores its .el files in the upstream repo's lisp subdir. However, in the tar archive available from ELPA, they are stored in the content directory; see http://elpa.gnu.org/packages/srht-0.1.tar.
I don't really understand how all this works - should this be reported upstream?
Meanwhile, I have managed to get it to work with a custom recipe, but I presume it should actually work out of the box.
Thank you very much for your astonishing work,
EV

Alrighty, I know I'm quite late on the response here, but let's have a look. First things first, I can definitely repro the issue. I'm guessing somebody on the GNU ELPA side changed the archive format out from under me, or I just made a mistake when setting it up originally. Investigating...

Sigh.

Another special case to add, I guess.

Of course there had to be a special feature that's only used by 4 packages in the whole archive.

PR in progress at https://github.com/radian-software/gnu-elpa-mirror/pull/8, will work on it more later.

Thanks a lot for having a look at this! I'm sorry you have to go through all this trouble just for four packages...

Okay cool, this should work. I've updated the 4 relevant packages, and any new ones that show up should be taken care of by the new code that I've deployed.

That's brilliant! Thanks a lot @raxod502!


Can't use any sub command in brew services

Try use any command but get an error.Can't search any releated question about it.
Error:
[root@StarSky /usr/local/nginx]$:brew services list
Error: private method `named' called for ["list"]:Array
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-services/cmd/brew-services.rb:103:in `run!'
/usr/local/Homebrew/Library/Taps/homebrew/homebrew-services/cmd/brew-services.rb:539:in `<top (required)>'
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
/System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/lib/ruby/2.6.0/rubygems/core_ext/kernel_require.rb:54:in `require'
/usr/local/Homebrew/Library/Homebrew/utils.rb:81:in `require?'
/usr/local/Homebrew/Library/Homebrew/brew.rb:112:in `<main>'

brew update --force and try again. If that doesn't work: brew update-reset and try again.


Clarify dtype type in ColumnBuffers  elements

Thanks for this team's efforts in implementing the dataframe interchange protocol.
While experimenting on an implementation for StaticFrame (https://github.com/InvestmentSystems/static-frame/pull/621), I found one aspect of the ABC and associated types unclear.
The ColumnBuffers TypedDict defines its elements as pairs of Buffer and a dtype, but only types the dtype as Any. I assume that the dtype should be provided as the same tuple returned from Column.dtype. This PR makes this explicit by defining a Dtype type alias and using it for the return value of Column.dtype as well as the elements in ColumnBuffers.
If my assumption is incorrect, it would be helpful to specify the type of the dtype values returned from ColumnBuffers.

If my assumption is incorrect

Just as a sanity check I checked and pandas/vaex/cuDF/modin all return the type described in Column.dtype for the get_buffers() values. A. TODO I realize for dataframe-interchange-tests is generalise test_dtype and use it in test_get_buffers.

Note that this is actually not correct, depending on how you interpret it. Yes, the buffers' dtype returns a similar type of DType tuple, but it should not necessarily return the same dtype tuple as its Column.dtype does, as the buffer can have a different dtype than the column.
It seems that we all interpreted this wrongly and all implementations got this wrong (or the text about "the data buffer's associated dtype" is wrong), see https://github.com/apache/arrow/issues/37598, https://github.com/pandas-dev/pandas/issues/54781, https://github.com/pola-rs/polars/pull/10787 (and the same for StaticFrame mentioned above, from a quick look).


Can you provide better API docs and a Forum for questions and help

Because starting with GTK is difficult.

For the API, we can provide an autogenerated list of proc headers, we plan to do that soon.
But note that the gtk.nim module has about 3000 different procs, and the related modules may provide some thousand more procs, so that we have about 10000 procs total, supported by maybe 1000 data types.
So we would split the API docs for the various modules, the gtk one would list 3000 procs, maybe sorted alphabetically.
That may be not that helpful, and we still have no documentation for each proc. Just copying the C docs is not a perfect fit.
What we may additional provide is tools which list all proc parameters when we type in a proc name. maybe only part of proc name.
For now you may install the gtk devhelp tool, which allows easy C API access.
But the fact is, that learning GTK is not very easy, and that there are currently not many good learning resources. But if you know GTK already, maybe because you have used C, Python or Java-Script API, then using it with Nim is easy.

For the forum, there is
https://discourse.gnome.org/
for general GTK discussion. Feel free to ask Nim related questions there.

If an API reference is provided, I can try porting pygtk tutorial (https://python-gtk-3-tutorial.readthedocs.io/en/latest/) to gintro, this should get a newbie started with gitnro/gtk3.
But I don't know how stable gintro is. My experience with Gtk-rs has shown that documenting GTK binding is not a trivial task.

Regarding Forums, most of the questions might be related to gintro itself, not Gtk. A matrix channel could be set up for this but I understand that nobody has time to moderate a platform. Hence opening up an issue labelled question is probably a better choice.

Providing an autogenerated list of proc headers is easy, as I already said. But the headers are not well sorted and contain no comment. For gtk module itself we have about 3000 procs to list. We can try to add the C comments, but that is not too helpful and is some effort, as comments are not supported by introspection.
How stable gintro is? The API is very stable, as it is basically the C api, with identifiers and data types tuned to Nim world (string or int vs cstring/uint32 or newButton() vs gtk_button_new(), and GC support.) Some stuff is missing, like procs with varargs or procs with GSList parameter. How stable the executable works? Well, we have to check for small memory leaks, for example recently I found that creating GValues from strings may not automatically free the memory of the string, I have to investigate.
As you said, documenting GTK binding is not a trivial task, when people are not already familiar with GTK. In principle we would have to write a textbook explaining GTK3 and GTK4, resulting in a book like the one from A.Krause for GTK2.
For porting Python tutorials: Of course we have to ask for permission first. Porting Python is not that easy as porting C, because Python code has most often OOP design.
For your other post: https://discourse.gnome.org/ should be really fine for now. That forum exists since a few months and has not much traffic. People discuss different languages like C, Python, D, JavaScript already. Of course there are questions to gintro itself, as recently https://forum.nim-lang.org/t/3136. Most often only Nim core devs can answer these, but I hesitate to ask them, as they are busy with more important tasks.
The fact is, that GTK and Nim community are both small, so number of people using GTK with Nim is very small. So a dedicated forum or IRC channel or  matrix channel would have one user in average if I subscribe myself.
Note, the most daunting task is newruntime for gintro, see https://github.com/StefanSalewski/gintro/issues/55

For gtk module itself we have about 3000 procs to list.

That could be a start.

My start is generally grep and ~/.nimble/pkgs/gintro-0.5.5/gintro/gtk.nim when I am unsure.
I can not imagine that I ever will open a html page listing 3k procs. But I think I will create that page, but seems to be not that urgent, I can see not many gtk users currently.


CLA

The contributing guidelines mention signing the Dropbox CLA in order to make contributions. Is this still relevant given that the project is now under the Mobile Native Foundation?

Nope need to update that


Fix e-manual link in readme

Hey, stumbled upon the e-manual link 404-ing on me. Fixed it.

Thank you for your contribution.


External_labels not being honoured

Hi,
I tried out 0.17.0rc2 and discovered that our external_labels settings were no longer appearing in our metrics.
Top of prometheus.yml:
global:
  scrape_interval: 60s
  evaluation_interval: 60s
  scrape_timeout: 30s
  external_labels:
    env: "dev"
    region: "eu-west-1"

We've been on an old version for a while so I had to update "labels" to external_labels above and I've tried 17.0rc1 and 16.2 and my custom labels don't seem to appear anywhere. Is there something else I need to do to get my labels back?
Thanks
John

I've been looking in the graph console expecting to see my above external_labels. In prod, running our old version, I see:
prometheus_local_storage_memory_chunks{env="production",instance="localhost:3000",job="prometheus",region="eu-west-1"}
While on my upgraded version I see:
prometheus_local_storage_memory_chunks{instance="localhost:3000",job="prometheus"}

This was an intentional change in behavior – to make that clear the option was named to external_labels.
The labels will be applied to time series that are leaving the scope of your Prometheus server. This means specifically alerts and federation.
One of the motivations was that when attaching labels when storing ingested time series, a change to those labels would break all time series unnecessarily.

Thanks for the information.
John


pitch black unrealarena maps (nolightmap issue)

reported by @maek on #unrealarena channel on QuakeNet, their campgrounds map is displayed pitch black when loaded by master or for-0.51.0 channel.
Must display:

Display instead:

@gimhael has a work in progress fix there: https://github.com/gimhael/Daemon/compare/fixnolightmap
But that “fix” also introduces bugs, it breaks models:

That “fix” also mess with nolightmapped models (I really don't know how are usually lightmapped nolightmapped model but…):
before:

after:

For testing purpose a build of unrealarena's campgrounds map can be found in their latest pre-prelease zip:
https://github.com/unrealarena/unrealarena/releases/download/v0.1-4/unrealarena-0.1-4.zip
The pk3 must be renamed to dpk to be loaded by a for-0.51.0 engine.
For testing purpose a snapshot of for-0.51.0 assets (including station15 map and unvanquished models) can be fetched this way:
wget -O- http://gg.illwieckz.net/dl/unvanquished/dev/UnvanquishedAssets.get | xargs wget

@gimhael I tested your newer commits and now I can say your changes fixes that bug without adding any regression.

@gimhael do you think your fixnolightmap is ready for a PR? :smiley:


Integration with Telescope TODO finder

Does this feature exist in Emacs orgmode core?
N/A
Orgmode link
No response
Feature value
Would make easier search TODOs even being in other files
Additional context
No response

https://github.com/nvim-orgmode/telescope-orgmode.nvim


Allow debouncing of ng model updates

Hey, If you like feel free to merge this.
This: https://medium.com/@jasperkuperus/angularjs-custom-debounce-events-5a4f5c597b2
pointed me in the right direction; ie calling $setViewValue as this respects the $$debounceViewValueCommit whenever necessary.


Table documentation: Wrong create table example

The create table if not exists is in the wrong order
Documentation URL: https://docs.delta.io/latest/delta-batch.html#create-a-table

It should be CREATE TABLE IF NOT EXISTS

Thanks for pointing this out @alexandreio. We will take a look.

The doc has been fixed


Fix panics and docs when using World schedules

Objective
The method World::try_run_schedule currently panics if the Schedules resource does not exist, but it should just return an Err. Similarly, World::add_schedule panics unnecessarily if the resource does not exist.
Also, the documentation for World::add_schedule is completely wrong.
Solution
When the Schedules resource does not exist, we now treat it the same as if it did exist but was empty. When calling add_schedule, we initialize it if it does not exist.

I fixed a couple more related issues that I noticed.


kv(ticdc): reduce eventfeed rate limited log

What is changed and how it works?
Issue Number: close #4006
Check List
Tests

Unit test

Related changes

Need to cherry-pick to the release branch

Release note
Reduce "EventFeed retry rate limited" logs

Codecov Report

Merging #4072 (57e28e3) into master (3873d39) will decrease coverage by 1.8869%.
The diff coverage is 67.3333%.

Flag
Coverage Δ

cdc
58.7294% <67.3333%> (+0.4928%)
:arrow_up:

dm
52.1814% <ø> (-3.8532%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
@@               Coverage Diff                @@
##             master      #4072        +/-   ##
================================================
- Coverage   57.0741%   55.1871%   -1.8870%
================================================
  Files           478        486         +8
  Lines         56551      60081      +3530
================================================
+ Hits          32276      33157       +881
- Misses        20978      23558      +2580
- Partials       3297       3366        +69

/merge

/run-kafka-integration-test
/run-verify

/run-kafka-integration-test
/run-dm-integration-test


Fix to retrieve modal presentation attributes

Hi, here's a change to retrieve the view controller modal attributes.
I've not found a way to set the presentation style and I think the attributes were not set.

+1


ktlint doens't make noise on missing trailing comma

Sorry for raising this
Expected Behavior
Ktlint failed
Observed Behavior
Ktlint passed
Steps to Reproduce
    override fun onCreateViewHolder(
        parent: ViewGroup,
        viewType: Int //<---- this should fail?
    ): ItemViewHolder {
        val binding = ItemAbFeatureBinding.inflate(
            LayoutInflater.from(parent.context), parent, false,
        )
        return ItemViewHolder(binding)
    }

Your Environment

Version of ktlint used: 0.43.0
Name and version (or code for custom task) of integration used (Gradle plugin, Maven plugin, command line, custom Gradle task): ./gradlew spotlessCheck on version 5.17.1
Version of Gradle used (if applicable): 7.1.1
Operating System and version: Windows 11

Are you using the experimental ruleset? the trailing comma rule is available there at the moment

Also note that you need to set the editorconfig properties below:
ij_kotlin_allow_trailing_comma_on_call_site=true
ij_kotlin_allow_trailing_comma=true

Are you using the experimental ruleset? the trailing comma rule is available there at the moment

What do you means by experimental ruleset?

Also note that you need to set the editorconfig properties below:
ij_kotlin_allow_trailing_comma_on_call_site=true
ij_kotlin_allow_trailing_comma=true

hrm, I do have them set
// .editorconfig

[*.{kt,kts}]
ij_kotlin_allow_trailing_comma = true
ij_kotlin_allow_trailing_comma_on_call_site = true

// build.gradle for spotless

            ktlint(ktlintVersion).userData(
                /**
                 * spotless not yet support .editorconfig, see below,
                 * so we have to provide our rules via user data
                 * https://github.com/diffplug/spotless/tree/main/plugin-gradle#ktlint
                 * https://github.com/diffplug/spotless/issues/142
                 */
                [
                    "charset"                                    : "utf-8",
                    "end_of_line"                                : "lf",
                    "indent_size"                                : "4",
                    "indent_style"                               : "space",
                    "insert_final_newline"                       : "true",
                    "max_line_length"                            : "100",
                    "ij_kotlin_allow_trailing_comma"             : "true",
                    "ij_kotlin_allow_trailing_comma_on_call_site": "true",
                ]
            )

FYI, I tried with the JAR file as well

FYI, I tried with the JAR file as well, but still doesn't work, is this working on your side?

Yes it works for me.

ok, my bad, is it still under experimental, I think we should mention in the release note to reduce confusions 😄

Indeed, it is missing in theist of experimental rules. Tnx for noting that.


Update the Readme

The $message variable is undefined.
And call to undefined method bgColor() . Its defined as bg(). Either update the readme or change the method name

Fixed my pull request #9

Cool. Thanks


Cut a release?

Hey @JakeWharton,
Could we respectfully request a release? We're on 1.9.0 now (thank you), but we have to use a custom version of the Compose compiler in order to ship for WASM. That's waiting on #206 which is done but not released.

Obviously this next release should preclude this from ever being an issue again, so thank you on that front as well 🚀

I tried to yesterday, in fact, but ran out of time. I'm on vacation this week. Maybe it gets done, but maybe it doesn't. At worst: next week!
For now, you can use Gradle dependency substitution to redirect the coordinates we add with your own.

thanks for the WA 👍🏻 have a great vacation

(i'll keep this open so i remember to drop the substitution, if that's okay)

Nevermind they're there now! I literally got the popup notification as I hit the "comment" button.


[T4PUB-666] wait reboot sub to support multiple ecu

What is this PR?
This PR supports multiple ECU update/status requests.
issue
~~https://tier4.atlassian.net/browse/T4PB-13539~~
https://tier4.atlassian.net/browse/T4PUB-666
test
I confirm that update and status request for the two VirtualBox machines works properly.

Please let me confirm the scenario:

mainECU dispatches ota-update request to all subECU, and subECU dispatches ota-update request to subsub...ECU, recursively, in a top-down fashion;
Only when all the child ECUs are updated, the parent ECU can update itself, recursively in bottom-up fashion.

Is that right?

Actually I think the implementation of the logic should be restricted in the grpc-server, not stepped into the ota-client(I can see that a closure function can_reboot is passed deep into the ota-client).
More specifically speaking, I think the status pulling should be implemented in the grpc-server side(in ota-client-service), the scenarios may as follow:
(in ota_client_stub)

mainECU dispatches the ota-update requests to all subECU,
wait for the immediately responses from all subECUs non-blocking, confirm that all subECUs receive the request,
mainECU responses to the IoT agent non-blocking,
mainECU lauches a background tasks to pulling all subECUs and wait for updating itself.

mainECU dispatches ota-update request to all subECU, and subECU dispatches ota-update request to subsub...ECU, recursively, in a top-down fashion;
Only when all the child ECUs are updated, the parent ECU can update itself, recursively in bottom-up fashion.

Right.
the parent ECU start updating itself, and wait reboot until all the child has been finished.

It is better to start updating for main ecu if update is requested, but the reboot should be waited until all children are finished.

I'd like to close this PR since #97 was merged.


CI fails randomly with version info not found error

Sample error log as follows:
================================= log start ===================================
ERROR: Exception:
Traceback (most recent call last):
File "/home/vsts/work/1/s/sdk/textanalytics/azure-ai-nspkg/.tox/sdist/lib/python3.6/site-packages/pip/_vendor/pkg_resources/init.py", line 2681, in version
return self._version
File "/home/vsts/work/1/s/sdk/textanalytics/azure-ai-nspkg/.tox/sdist/lib/python3.6/site-packages/pip/_vendor/pkg_resources/init.py", line 2815, in getattr
raise AttributeError(attr)
AttributeError: _version
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "/home/vsts/work/1/s/sdk/textanalytics/azure-ai-nspkg/.tox/sdist/lib/python3.6/site-packages/pip/_internal/cli/base_command.py", line 186, in _main
status = self.run(options, args)
File "/home/vsts/work/1/s/sdk/textanalytics/azure-ai-nspkg/.tox/sdist/lib/python3.6/site-packages/pip/_internal/commands/freeze.py", line 100, in run
for line in freeze(**freeze_kwargs):
File "/home/vsts/work/1/s/sdk/textanalytics/azure-ai-nspkg/.tox/sdist/lib/python3.6/site-packages/pip/_internal/operations/freeze.py", line 70, in freeze
req = FrozenRequirement.from_dist(dist)
File "/home/vsts/work/1/s/sdk/textanalytics/azure-ai-nspkg/.tox/sdist/lib/python3.6/site-packages/pip/_internal/operations/freeze.py", line 257, in from_dist
req = dist.as_requirement()
File "/home/vsts/work/1/s/sdk/textanalytics/azure-ai-nspkg/.tox/sdist/lib/python3.6/site-packages/pip/_vendor/pkg_resources/init.py", line 2840, in as_requirement
if isinstance(self.parsed_version, packaging.version.Version):
File "/home/vsts/work/1/s/sdk/textanalytics/azure-ai-nspkg/.tox/sdist/lib/python3.6/site-packages/pip/_vendor/pkg_resources/init.py", line 2648, in parsed_version
self._parsed_version = parse_version(self.version)
File "/home/vsts/work/1/s/sdk/textanalytics/azure-ai-nspkg/.tox/sdist/lib/python3.6/site-packages/pip/_vendor/pkg_resources/init.py", line 2689, in version
raise ValueError(msg, self)
ValueError: ("Missing 'Version:' header and/or PKG-INFO file at path: /home/vsts/work/1/s/sdk/textanalytics/azure-ai-nspkg/azure_ai_nspkg.egg-info/PKG-INFO", azure-ai-nspkg [unknown version] (/home/vsts/work/1/s/sdk/textanalytics/azure-ai-nspkg))

PR to fix this issue: https://github.com/Azure/azure-sdk-for-python/pull/9951


Couple of questions

1: how do create a table more than 12 columns wide? Currently only the first 12 columns are shown, with no scroll for further columns :-(
2: is it possible to enable / disable / activate a tab

Hi @bentwonk,

Our grid system has 12 columns by default. Can you do a codepen do explain what you want to do? http://www.codepen.io

Humm, by the material design specs, tabs do not have a disable state https://material.io/components/tabs#states and https://material.io/design/interaction/states.html#disabled

But for me, it's nice to have a disabled state on tabs. I think we can work on it 🙂

Thanks fro the quick response: Table: I have a table for results being generated dynamically, the number of columns is determined by the input data and can exceed 12. In data dashboard applications a 12 column table is pretty limiting.  simplified example https://codepen.io/bentwonk/pen/PoEZRzv
I agree disabled tabs is a good way to show future workflow.

Sorry I did not understant yet, I'll try help. If you use the row element you have 12 columns (is a responsive way to do the things). If you use the
 element you do not have column limit. By default, row and
 elements will have the width of parent element.
Horizontal scroll is disabled by default. So, if you want horizontal scroll on
 element you need to set a scroll helper on parent element, like this:

...

Go to this codepen and resize the window to show the scroll.
https://codepen.io/leo-bnu/pen/WNdxaPa
Is this that you want to do @bentwonk ?

Sorry I did not understant yet, I'll try help. If you use the row element you have 12 columns (is a responsive way to do the things). If you use the
 element you do not have column limit. By default, row and
 elements will have the width of parent element.
Horizontal scroll is disabled by default. So, if you want horizontal scroll on
 element you need to set a scroll helper on parent element, like this:

...

Go to this codepen and resize the window to show the scroll.
https://codepen.io/leo-bnu/pen/WNdxaPa
Is this that you want to do @bentwonk ?

I will close this issue by inactivity, ok?


Fix DOMNode & DOMElement property types

Due to false positive errors from PHPStan I found out that the stubs from this repo have incorrect types for DOMNode & DOMElement properties. All of these are actually correctly noted in the docs: DOMNode, DOMElement and I have also verified all of these in runtime:

DomNode::$nodeValue - example: https://3v4l.org/qa86V
DomNode::$localName - example: https://3v4l.org/5613l
DomElement::$parentNode - example: https://3v4l.org/Dv8CN
DomElement::$firstChild - example: https://3v4l.org/FcLun
DomElement::$lastChild - example: https://3v4l.org/TifIr
DomElement::$previousSibling - example: https://3v4l.org/t3rAL
DomElement::$nextSibling - example: https://3v4l.org/H77QM

I am not sure why the properties on DomElement which are inherited from DomNode are "redeclared", maybe they should not? Also generally does it make any sense since properties should be invariant?

@DmitryTronin Qodana finally came through, could you please allow to run again the other workflows?

Thanks for merging :)

As for re-declared properties: they are there because of https://youtrack.jetbrains.com/issue/WI-6760. You can also find them documented at https://www.php.net/manual/en/class.domelement.php.
Currently they are required for a correct code completion in cases described in WI-6760. Removing those declaration would break code completion & I don't see a quick & efficient way of removing them currently.

You can also find them documented at https://www.php.net/manual/en/class.domelement.php.

Yea, but they are documented only as inherited, I think PHP documentation shows these for all classes. See for example https://www.php.net/manual/en/class.typeerror.php and https://www.php.net/manual/en/class.exception.php .

they are there because of https://youtrack.jetbrains.com/issue/WI-6760
Removing those declaration would break code completion

Unfortunately I think that this PR has the same effect - but only because the original usecase in the issue is "wrong".
/* @var \DOMElement $node */
$node->parentNode->removeAttributeNS

The fact that $node->parentNode does not have removeAttributeNS is correct, precisely because it can not have it - as seen in the example above and if I add accessing this attribute, it obviously results in an error: https://3v4l.org/2JMN3 .
So the only correct way in such a case is either handle all the cases, or if the parent can only indeed be a DOMElement, than code should look something like this (which would be obviously fine in PHPStorm and with code completion):
/* @var \DOMElement $node */
$parentElement = $node->parentNode;
assert($parentElement instanceof DOMElement);
$parentElement->removeAttributeNS;

Thanks for the comments. I'll review the info & update you in the nearest future.

@VasekPurchart Yeah, that looks valid. You can give it a go & create a new PR addressing this, or let me know - I'll report this to our tracker to address in the future.


Support Symfony 5

I think it's worth supporting Symfony 5, even if you need to bump this to a new version.
Fortunately, going from 4.4 to 5 is simply a matter of removing deprecations.
I know you just pushed the tag for Symfony 4, thanks!

It's been a while
Now the bundle supports Symfony 6 and 7.


🥅 Makes ErrorEvent contains the optional exception stack trace

Description
The ErrorEvent for the relay client error channel does not contain enough info to extract where the exception is thrown. Adding the ErrorEvent.stackTrace will help the developer determine the root cause of the exceptions.

Hello @AlexV525! I will discuss this with the team as I'm quite sure we don't want to throw stack traces to the user/developer in these scenarios... These should be all user facing events so stack traces are meaningless here. If you could provide a useful scenario for doing this it would help me a lot!

The reason is similar to #25, once you've swallowed the stack trace, developers will never know where goes wrong, especially when you report those errors to analysis platforms.

We can add logger methods for sure, like on line 217 or 222
core.logger.e('[$runtimeType]: Connect timeout: $e');
onRelayClientError.broadcast(ErrorEvent('Connection to relay timeout'));

But the main idea of onRelayClientError (or any other event subscription fwiw) is to allow the developer to subscribe to meaningful events and inform the user when they happen. Stack trace is not meaningful to the users.
I will add for sure logs in the next version but still kipping this PR opened to discuss it.
Thanks!

What is the definition of "users" here? Is it "end users" or "developers"? For end users they surely don't need to care about anything with stack traces, but they are helpful for developers.

Exactly, users are end users. And for developers I will add a logging system there like in other places. If that is not helpful we can discuss this PR further/

Logging requires extra efforts for developers to track as they need to filtering from logs and make connections between business and errors.
 How would you determine if an error is occurred from RelayA not RelayB, and how do you manage error reporting?

This is still worth updating.

I will reconsider this again this week as we are in the middle of tech debt week and I will either close it or merge it. Thanks!


Amendment to dot_etl project proposal timelines

Add update / amendment to M1 and total timelines.  Have been working on other projects, but we are still committed to delivery of this grant proposal.
Project Abstract
This is an amendment (request for extension) of an earlier accepted grant proposal.  All of the details of the original proposal are still valid and are availabled in the original PR.  Thank you.
Grant level

[ ] Level 1:  Up to $10,000, 2 approvals
[x] Level 2:  Up to $30,000, 3 approvals
[ ] Level 3:  Unlimited, 5 approvals (for >$100k: Web3 Foundation Council approval)

Application Checklist

[x] The application template has been copied and aptly renamed (project_name.md).
[x] I have read the application guidelines.
[x] Payment details have been provided (bank details via email or Polkadot (USDC & USDT) address in the application).
[x] I am aware that, in order to receive a grant, I (and the entity I represent) have to successfully complete a KYC/KYB check.
[x] The software delivered for this grant will be released under an open-source license specified in the application.
[x] The initial PR contains only one commit (squash and force-push if needed).
[x] The grant will only be announced once the first milestone has been accepted (see the announcement guidelines).
[ ] I prefer the discussion of this application to take place in a private Element/Matrix channel. My username is: @_______:matrix.org (change the homeserver if you use a different one)

@keeganquigley thanks for reaching out on an extension / amendment to our original proposal.  Adding an amendment for an extension on this.  We've been working on other things but are still committed to get to this proposal.  thanks.  (+ @johncandido )

I have read and hereby sign the Contributor License Agreement.

pinging @liangjh

all - thanks for the feedback.  i will add a start date on this -

Thanks again for creating the PR. The committee decided to go ahead and close it. We will also terminate the current grant, but you are more than welcome to apply again, once you want to work on the project.

Hi all, just got to the recent feedback this morning.  Thank you for the feedback, and the comments in the initial review rounds for this proposal back last year.
I do have a question on this though, do you have a sense of what the review rounds will look like if we re-apply for this grant?  Given that this propose (dot_etl) was already approved by the committee, would an enhanced or updated proposal pass through fairly quickly?   We are still committed to the original thesis of extracting actionable and economically viable data from DOT / substrate.

@liangjh As you know, we've signed multiple grants related to the Analytics Website/Data Platform RFP. So whether I'd add my approval at the time you'd re-apply also depends on the maturity of similar tools and the additional value your solution would bring. However, that's just my opinion and doesn't necessarily reflect the opinion of other w3f grants committee members.


15min and daily meter data does not match

I'm getting this error. I think the problem is rounding.
15min and daily meter data does not match: 25.32 (15min) vs 25.33 (daily)
mojelektro20240219_error.txt

Sometimes Moj elektro might send wrong meter data. Mainly between 0 and 6 am, but sometimes it can last the entire day. This is just a failsafe. It just means that will keep refreshing internal cache with online data until conditions are fulfilled.
Tnx for posting.


Rcmdcheck fix

Some issues with the timezone database for arrow in Windows... let's merge for now and raise an  new issue...


Provide documentation for swagger x-ms-format of id, resource type and location

Provide documentation describing the three new values and when they should be used
https://github.com/Azure/autorest.csharp/pull/2051
azure-location and etag were added after that PR as well which should be documented.

https://github.com/Azure/autorest.csharp/blob/feature/v3/docs/mgmt/polishing.md#change-format-by-name-rules


adding Zeroconf / Avahi Publish to main.py

Hi,
do you thought about adding Zeroconf / the avahi publish into the main.py maybe trigger by and option "--avahi true" that would be nice for households with more than one Spotify Account
Cheers and also thanks for the great Work

I do plan on adding this, but it won't be for a while (a few months)


Influxdb is not supported null value for fields

see https://github.com/influxdata/influxdb/pull/2429

Thanks


[BUG]:Workflow failed for get latest template

Discussed in https://github.com/ObsidianPublisher/obsidian-github-publisher/discussions/88

Originally posted by clutterwhy January 24, 2023
Get lastest release from template workflow run failed.

Please check the #90 !
Repost of the announce :
Hello!
I updated the workflows to auto_update and the workflows that clean unused medias and update the requirements. You need the 0.0.4 version!
You must do :

Create a  .env file in .github folder.
With the following value. You need to edit the the WORKFLOW_TYPE to corresponding to your methods (netlify or gh-pages') :

WORKFLOW_TYPE='netlify' or 'gh-pages' (or leave blank : '')
CLEAN=true
IMG_DIR='assets/img'
AUTO_MERGE=false

Create the GH_TOKEN secrets.
Register it as a secrets. As I said, the secret must be named GH_TOKEN.

Obviously, you can change any option, I present here only the default.


More tolerance for path to room id

Some scripts e.g. hubot-rss-reader are using different paths to define room. This adds support for envelope.room.

Hi @jbick,
Thanks for that PR.
Although I see no harm on that code change it doesn't look like hubot-rss-reader works properly though. I initially got issues with promises (line 74) https://github.com/shokai/hubot-rss-reader/blame/master/scripts/hubot-rss-reader.coffee#L75
While trying to delete a RSS as a test for rooms I also got the following error:
[Thu Dec 03 2015 15:09:23 GMT+0000 (GMT)] ERROR TypeError: undefined is not a function
  at TextListener.callback (/Users/lessa/OSS/hubot-test/node_modules/hubot-rss-reader/scripts/hubot-rss-reader.coffee:156:5, <js>:211:38)
  at executeListener (/Users/lessa/OSS/hubot-test/node_modules/hubot/src/listener.coffee:65:11, <js>:53:19)
  at allDone (/Users/lessa/OSS/hubot-test/node_modules/hubot/src/middleware.coffee:41:37, <js>:32:16)
  at /Users/lessa/OSS/hubot-test/node_modules/hubot/node_modules/async/lib/async.js:274:13
  at Object.async.eachSeries (/Users/lessa/OSS/hubot-test/node_modules/hubot/node_modules/async/lib/async.js:142:20)
  at Object.async.reduce (/Users/lessa/OSS/hubot-test/node_modules/hubot/node_modules/async/lib/async.js:268:15)
  at /Users/lessa/OSS/hubot-test/node_modules/hubot/src/middleware.coffee:46:7, <js>:35:22
  at process._tickCallback (node.js:355:11)

I've already checked bluebird library and it's all there so it might be something on my dev environment, so if you have any other package that I can test that against that would be perfect.
Tks

Hi @heitorlessa,
I do not have these problems, sorry. The only other problem I had with hubot-rss-reader was a missing proxy env.

I scheduled to test this weekend as soon as I come back from a trip, so I will clean up my environment and try that with 2 other scripts I identified the same pattern.

Hey @jbick,
Just tested on a new environment (docker) and it works perfectly.
Thanks for yet another nice PR.


Add metrics for failed topic load operation

Search before asking

[X] I searched in the issues and found nothing similar.

Motivation
Currently, we have topic load-related metrics like the followings:
topic_load_times{cluster="standalone",quantile="0.5"} 140.0
topic_load_times{cluster="standalone",quantile="0.75"} 183.0
topic_load_times{cluster="standalone",quantile="0.95"} 249.0
topic_load_times{cluster="standalone",quantile="0.99"} 249.0
topic_load_times{cluster="standalone",quantile="0.999"} 249.0
topic_load_times{cluster="standalone",quantile="0.9999"} 249.0
topic_load_times_count{cluster="standalone"} 6.0
topic_load_times_sum{cluster="standalone"} 955.0
topic_load_times_created{cluster="standalone"} 1.671240308864E9

But we are not able to detect if there are topics that failed to load due to
zookeeper/bookkeeper problems.
It's better to add new metrics for the topic load failed operation so that users
can add alerts based on the metrics.
Solution
Add topic_load_failed_count metrics
Alternatives
No response
Anything else?
The metrics changes requires a proposal
Are you willing to submit a PR?

[ ] I'm willing to submit a PR!

@codelipenghui Please assign to me

what a coincidence, I was considering add the metric when I was dealing a ticket

@tjiuming you can directly submit a pr

@shy-share https://github.com/apache/pulsar/pull/19236 The PR is pending reivew


Example

Hii can you create a demo example folder using http and websocket with ping/pong for both thanks.

Hey @LeulAria,
Here's a demo example folder using both HTTP and WebSocket functionality: example.


Option to switch between digital/analog

As the title says, it would be great if we had the option to display only the digital clock (with custom format)

@panosru What do you mean? If you don't want the time-string to get shown, just disable 'Show Title' from the little dropdown menu in the property inspector. This gives you just the analog clock...

@tiptronic I mean a toggle between only analog or only digital. I know the plugin is called "Analog" clock, but if would be great if we could just use digital.
For example I currently have the following setup which I accomplish by using the world clock (modified to remove the annoying globe background) or the left, and only analog clock on the right.
I would be best to have this available in one plugin so I could just duplicate it and have it either analog or digital.

Thanks!

@panosru OK - understood... Good idea, although the AnalogClock is a sample to show how to draw from canvas to a key... but we'll see ;)

@tiptronic  I'm just throwing an idea :) feel free to close this issue ;)

@panosru I added a digital option (see PI)... (no date, however ;))


Maintainer wanted

Hey, just wanted to say I was interested in possibly becoming a maintainer!
What all would that involved I'd like to get started right away!

🎉  In the "Contribute" section https://github.com/simurai/tone-syntax#contribute are steps how to get started. Is that enough clear.

Yeah it's clear enough thanks

Apologies for butting in, but as I'm unfamiliar with syntax support styles in Atom, would if be possible for you to add a link here to give me a heads up Simurai? I'd be keen to give it a go... thanks

@objectkit Here some more infos, but it might not go into details.
What language are you familiar with? Here an example for "Go".

Doublicate styles/languages/javascript.less so you have a starting point and rename the file to go.less.
Add the file to styles/languages/_index.less with @import 'go';.
In go.less replace the styles with

// Go

.@{s}go {

  &.@{s}string {
    .uno-1();
  }

  &.@{s}keyword {
    .duo-1();
  }

}

Open a .go file that has some sample code. You should already see that strings and keywords have a different color.
Now place the cursor somewhere in the Go sample code that you want to highlight and press cmd-alt-p. This should open a popup like

In this example variable.other.assignment.go it's a variable. We could be more specific with .other.assignment, but maybe ok to highlight all variables the same. So in go.less add the following.

// Go

.@{s}go {

  &.@{s}string {
    .uno-1();
  }

  &.@{s}keyword {
    .duo-1();
  }

  &.@{s}variable {
    .tri-1();
  }

}

This should make variables have a tri-1 color. Here the whole color palette to choose from.
Once you're happy, commit and send a PR. 🙇

Thinking about it, I might can add a few more languages. So it's easier to get started if there is already some syntax highlighting.


mountpoint for  not found

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description

I have an image that builds find for a non-root user. When I try to build it as root (sudo podman build -t test .), I get the following error:
STEP 1: FROM alpine:3.11
STEP 2: RUN apk add --update python3 py3-libvirt py3-lxml
WARN[0000] signal: killed
ERRO[0000] container_linux.go:346: starting container process caused "process_linux.go:297: applying cgroup configuration for process caused \"mountpoint for  not found\""
container_linux.go:346: starting container process caused "process_linux.go:297: applying cgroup configuration for process caused \"mountpoint for  not found\""
error running container: error creating container for [/bin/sh -c apk add --update python3 py3-libvirt py3-lxml]: : exit status 1
Error: error building at STEP "RUN apk add --update python3 py3-libvirt py3-lxml": error while running runtime: exit status 1

Steps to reproduce the issue:

build an image as `root

Additional information you deem important (e.g. issue happens only occasionally):
This is on Fedora 31, previously running the stock 1.8.0 package.
Output of podman version:
Version:            1.8.1-dev
RemoteAPI Version:  1
Go Version:         go1.13.6
Git Commit:         1a18a50acd9ea51158ab908e1f32d6fb2372869e-dirty
Built:              Fri Aug  3 20:00:00 2018
OS/Arch:            linux/amd64

This is from @baude's COPR repository. I'm pretty sure that "Built" date is erroneous.
Output of podman info --debug:
(paste your output here)

Package info (e.g. output of rpm -q podman or apt list podman):
podman-1.8.1-1582918459.git275e9b85.fc31.x86_64

Additional environment details (AWS, VirtualBox, physical, etc.):

You can infer this from the error message, but this is failing on a Dockerfile that looks like:
FROM alpine:3.11

RUN apk add --update python3 py3-libvirt py3-lxml

it is something related to the copr build. i dont have the problem with master.  i also cannot replciate this exatly but i get a different error.

I can no longer reproduce this behavior.


Investigate ways to improve mapping of benefits to job quality categories

[ ] Literature review
[ ] Test most promising avenues


[#157737869] Create an Aiven service broker and implement provision/deprovision

What
We gone done a broker.
The last operation endpoint was implemented implicitly in this as it is hard to properly integration test the whole lifecycle without it.
This was forked from https://github.com/henrytk/universal-service-broker. The fork should be broken, but I don't know how to do that. Please help.
How to review

Code review
See the README for instructions on how to run tests.

Who
Anyone but me or @samcrang

I think we should avoid this repo being a fork (as far as Github is concerned). If it is a fork, that has implications - Searching is more limited, also PRs get targeted against the upstream repo by default.

@alext seems reasonable. Are you happy with retaining the history though?

Are you happy with retaining the history though?

Yeah, no problem with retaining the history. Otherwise we end up with a massive 'initial commit', which isn't great.
ISTR that it's possible to break a fork in github by contacting their support. (found the reference to it on this page: https://help.github.com/articles/why-are-my-contributions-not-showing-up-on-my-profile/#commit-was-made-in-a-fork)

I've hassled GitHub support about detaching the fork.

@chrisfarms, @henrytk and myself discussed the config layout offline. We think the current layout is fine for now.
There may be scope for refactoring in future so that we're not using the upstream catalog types anywhere except in the broker.Catalog method, which would decouple our config from the upstream layout. We don't need to look at this now though.


Add Layer.Stack cons method

I'm unclear what the issue is here. Should have written a description at the time. 🤦
Needs investigation or closing.


Add optional border for weather bar

Is your feature request related to a problem? Please describe.
When a weather type's background color matches the card background color, the weather bar looks a little odd:

Describe the solution you'd like
An option to add a simple 1 pixel border to the bar
Thanks for making this card, it works great!

Just in case anyone runs into this in the future, this is what I ended up doing for now, via card-mod:
    card_mod:
      style:
        weather-bar$: |
          .snowy {
            outline-style: solid;
            outline-width: 1px;
            outline-offset: -1px;
            outline-color: #E5E5E5;
          }

I opted to outline the Snowy sections, since snow is rather rare and this way I am not modifying the look of the bar when there is no snow in the forecast. If you wanted to outline the whole bar, something like this works:
    card_mod:
      style:
        weather-bar$: |
          .bar {
            outline-style: solid;
            outline-width: 1px;
            outline-color: #E5E5E5;
            border-radius: 10px;
          }

I appreciate the request. I'm concerned that changing this would open a can of worms for existing users, and would be quite complex when we account for custom colors and themes. Thus, I'm inclined to leave this as-is and, instead, suggest that folks use card-mod when they want this sort of customization. Thanks for posting the card-mod YAML that worked for you!


chore(deps): update common-dev-assets digest to 65fb570

This PR contains the following updates:

Package
Update
Change

common-dev-assets
digest
5cf7d9c -> 65fb570

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

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

This PR has been generated by Renovate Bot.

/run pipeline

/run pipeline

:tada: This PR is included in version 2.6.14 :tada:
The release is available on:

GitHub release
v2.6.14

Your semantic-release bot :package::rocket:


JupyterView Roadpath

@trungleduc Thanks for jupyterview, it's pretty darn awesome 😍
Just thought I'd share with you jupyterview visualising some AWI-CM FESOM climate data, where each vtk mesh consists of 126,859 cells and 2,283,462 points 👍
Also, I have a couple of questions:

I was just wondering what the roadpath is for jupyterview? Do you have any plans that you're able to share?
Are there plans to extend jupyterview to allow more than one VTK object to be added to the scene? Or, if that's already possible, how do you do it?
Is it easy for you to share instructions on how to publish jupyterview and run with jupyterlite?

Ping @koldunovn (yeah, I know it's not the triangulated version of the mesh, but still very cool!)
https://user-images.githubusercontent.com/2051656/168305776-cb6b389b-c375-412b-b516-6f96c3ea04c8.mp4

@trungleduc Fancy enabling GH Discussions for your repo?

Hi @bjlittle, thank you for sharing your use case. It looks awesome!

I was just wondering what the roadpath is for jupyterview? Do you have any plans that you're able to share?

I'm working in #34 to support more file types  by using the meshio package. With this update, jupyterview can read a lot more mesh file type, for example : Abaqus (.inp), ANSYS msh (.msh),  CGNS (.cgns), DOLFIN XML (.xml)...
I would love to hear about your suggestions to improve jupyterview.

Are there plans to extend jupyterview to allow more than one VTK object to be added to the scene? Or, if that's already possible, how do you do it?

Technically it's possible, but since I started jupyterview as a single document viewer, it needs a lot of changes in the UI.

Is it easy for you to share instructions on how to publish jupyterview and run with jupyterlite?

You can take a look at https://github.com/trungleduc/jupyterview/blob/master/.github/workflows/deploy.yml .  I used this workflow to deploy jupyterview with jupyterlite to Github page.

@trungleduc As suggestions for improvements, having a "follow-mode" to focus and zoom the camera through a scene would be fantastic e.g., by double clicking to fly to the location of the mouse in the scene. For example, exploring this relatively complex river basin with tributaries is possible with jupyterview, but a little difficult:
https://user-images.githubusercontent.com/2051656/168390294-1f2cec27-4947-4ebb-b32c-7837bc64a55c.mp4
This is the same scene, but using pyvista with focus and zoom to make the interaction more natural and intuitive:
https://user-images.githubusercontent.com/2051656/168390777-e9897289-ff61-4ef1-8e52-92c80a6c397d.mp4

@trungleduc If you could offer more colormaps out-the-box, such as the perceptually accurate colormaps from colorcet or indeed cmocean, then that would be marvellous and make a huge difference.
For example, it would really enhance visualizations of salinity changing with the tide:
https://user-images.githubusercontent.com/2051656/168392784-8e8fcd3f-dedb-48b2-8a1d-d0862e55b1bf.mp4
Awesome, thanks! 👍

You can take a look at https://github.com/trungleduc/jupyterview/blob/master/.github/workflows/deploy.yml .  I used this workflow to deploy jupyterview with jupyterlite to Github page.

Brilliant, thanks... I take a look at that 👍

Also, being able to simply change the background colour and add a title to the scene would be useful 👍

@trungleduc Did you have a specific use case for adding the warping to the UI?
Personally, I'd tend to pre-warp and save the mesh rather than do it interactively. Also, warping by a fixed normal is limiting, but being able to compute the normals of the faces (and flip) and then warp by those could potentially be more useful... but I guess it depends on what the user is trying to achieve.

@trungleduc Just to clarify, for the pvd file format, is the timestep the intended delay between rendered frames?
i.e., so here it's 100ms, right? (given that each frame in reality can be rendered that quickly)
<?xml version="1.0"?>
<VTKFile type="Collection" version="0.1">
    <Collection>
        <DataSet timestep="0.000000E+00" file="tamar_salinity_000.vtk"/>
        <DataSet timestep="0.100000E+00" file="tamar_salinity_001.vtk"/>
        <DataSet timestep="0.200000E+00" file="tamar_salinity_002.vtk"/>
        <DataSet timestep="0.300000E+00" file="tamar_salinity_003.vtk"/>
    </Collection>
</VTKFile>

@bjlittle just to say the AWI-CM example (as well as others :)) looks great! :)

Sorry for my late reply

Also, some minor requests:

being able to simply change the background colour

add a title to the scene
control the title of the colorbar/scalarbar (rather than default to the name of the scalar)
the Color by drop-down also indicates for each scalar it's location i.e., points or cells, which will help differentiate to the user between two scalar arrays attached to the mesh with the same name but on different mesh locations.

Would all be really useful 😃

Thank you for your very helpful suggestions. I created the 0.5.0 release plan #36. It would be great if you could put your suggestion into independent issues, I will tag them with the 0.5.0 milestone

@trungleduc Did you have a specific use case for adding the warping to the UI?
Personally, I'd tend to pre-warp and save the mesh rather than do it interactively.
That said, warping by a fixed normal is limiting, but jupyterview being able to compute the normals of the points/faces (and option to flip them) and then warp by those could potentially be more useful?... but I guess it depends on what the user is trying to achieve.
Anyways, if you supported this then I could easily load the flattened bathymetry mesh and warp the points by scalar depth to dynamically create the scene shown above. That would help to easily determine the warp factor that suits the users needs... now that would be pretty cool 😉
Or are you assuming/preferring that the user pre-computes and attaches the normals to the mesh? If so, then being able to select the existing normals on the mesh from the UI and warp by those might be an easier option to support from the perspective of jupyterview

From my experience in solid mechanics, we want to plot different stress fields on a deformed mesh, so having interactive wrapping is quite useful.
What I want to do is a "wrap by vector", just like in ParaView but this feature is not available yet on vtk.js, the base library that i used in jupyterview

@trungleduc Just to clarify, for the pvd XML file format, is the timestep the intended delay between rendered frames?
i.e., so here it's 100ms, right? (given that each frame in reality can be rendered that quickly)
<?xml version="1.0"?>
<VTKFile type="Collection" version="0.1">
    <Collection>
        <DataSet timestep="0.000000E+00" file="tamar_salinity_000.vtk"/>
        <DataSet timestep="0.100000E+00" file="tamar_salinity_001.vtk"/>
        <DataSet timestep="0.200000E+00" file="tamar_salinity_002.vtk"/>
        <DataSet timestep="0.300000E+00" file="tamar_salinity_003.vtk"/>
    </Collection>
</VTKFile>

Also, is there a limit to the number of frames that can be in a collection? i.e., do you load all the frame meshes into memory before rendering or do you have a lazy loading/render scheme?

I fixed the framerate at 24fps, the timestep is used just for labeling the frame. And yes, all the meshes are loaded into memory before rendering, and the frames are cached so I only need to render once for each mesh.


fix(toml)!: Disallow [lints] in virtual workspaces

This was missed with the initial [lints] implementation.
While this is a breaking change, this is aligned with ones we've done in the past.  A lot of times, we warn first.  My hope is that isn't needed this time because

It only exists virtual workspaces so they aren't published
It is a nop to have this which is likely to be caught
This is so new that the number of people using it, and likely running into this case, is quite low.

What does ! mean in fix(toml)!:?

@bors r+

:pushpin: Commit 48c72b9aa7967fc635826fdc4cda2bb177a3153e has been approved by weihanglo
It is now in the queue for this repository.

:hourglass: Testing commit 48c72b9aa7967fc635826fdc4cda2bb177a3153e with merge a0339b0ae34a147279df33d1aed12054b89c00ce...

:sunny: Test successful - checks-actions
Approved by: weihanglo
Pushing a0339b0ae34a147279df33d1aed12054b89c00ce to master...

What does ! mean in fix(toml)!:?

Breaking change

I'm probably missing something, but what's the rationale for this? Surely it may be useful to also harmonize lints in a virtual workspace?

I'm probably missing something, but what's the rationale for this? Surely it may be useful to also harmonize lints in a virtual workspace?

Then one should use [workspace.lints] instead of [lints]. This PR prohibits the latter.

Ah, that distinction also confused me. I think it might be worth emphasizing it in the release notes if they're not immutable :)

I posted #13425


Object model => mapper => ui model => render

What is this PR trying to achieve?
As the title says it's moving towards the model we chatted about.
The image below is a poor representation of that - the title a better one.
This way API models are decoupled from UI component models.
What we have now is:
Wordpress /posts endpoint => ArticleStubsResponse => Series => PromoList => Rendered.
What does it look like?

The dream would be to get closer to a UI component being a function.

TODO

[ ] Typechecking
[ ] Forward fill of electricity series


MAIN B-18411-UI-shipment-address-update-review-screen-updates

INTEGRATION BRANCH PR
Agility ticket
Summary
In order to get the full functionality, please run git merge origin/B-18475-INT to merge the backend portion of this feature into the branch.
B-18475 PR
When you're finished run git reset --hard HEAD~1 to undo the commit of the above branch.
When the TOO reviews a shipment destination address update request - there's a reason for it. It means that there was a check done in the backend that changed the status of the request in the shipment_address_updates table to REQUESTED instead of automatically changing it to APPROVED.
When a shipment contains destination SIT service items, the above mentioned backend branch does logic checks that populates the table with SIT data.
This PR does the following:

takes that SIT data sent to the UI and returns an info banner if the new mileage change for a shipment containing SIT is changed to greater than 50 miles

How to test

Access MM as prime
Request a shipment destination address update to a ZIP that is > 50 miles of what the current destination address is
Log in as the TOO & navigate to that shipment
Follow the red prompts until you get to the address update modal that shows the changes
You should see an info banner that shows the updated mileage and a general statement to the TOO letting them know what's up

Screenshots

WHY WONT YOU COMPILE


testfix fe ut,  now create cluster be node is not required

Proposed changes
fix pipeline fe ut problem, create cluster repeatedly

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

https://github.com/apache/doris/pull/28722  have fixed


Extended spacing systems with fallback

Proposal to change spacing classes to a singular class .marX with modifier isSpace allowing for a more memorable spacing utility. Early explorations ran into limitations with destructiveness in children which required swapping css variables & resetting children.
:root {
  --gap-1: 2rem;
  --gap-2: 4rem;
}

.isSpace {
  --space-1: 4rem;
  --space-2: 6rem;
}

.isSpace * {
  --space-1: initial;
  --space-2: initial;
}

.mar1 {
  margin: var(--space-1, var(--gap-1));
}

.mar2 {
  margin: var(--space-2, var(--gap-2));
}

Fixed with #51

Seemingly an issue with isSpace being used much more frequently, is a fallback needed?

There are maybe three approaches.

Remove gap entirely by adding 01-05, which adds five classes instead a switch?

  --space-01: 0.0625rem; /* 1px */
  --space-02: 0.125rem; /* 2px */
  --space-03: 0.25rem; /* 4px */
  --space-04: 0.5rem; /* 8px */
  --space-05: 0.75rem; /* 12px */

Change .isSpace to .isGap but have it only operate from 0 to 5, default all component spacing to initial instead of gap,

Keep only spaceX but add arithmetic classes like plushalf which would add 0.5rem for example


Include output of failed exec in graphql errors

Right now if an exec fails the graphql error just says that it exited non-zero. This makes it hard to debug unless you go look at the buildkit progress output.
We should instead include the output of the execop in the graphql error to help debugging. The implementation is not incredibly straightforward. Buildkit has the ability to obtain the FS of a failed exec op (including changes made during the command): https://github.com/moby/buildkit/blob/c9a0f4d2de095591e742d7f411d9ed36a03a1c4e/client/build_test.go#L1278-L1310
We will probably need to use that to obtain the output as written to the output files by the shim.
We should also make sure to limit the size of the output included so if there's a failure during a command with many megabytes of output (e.g. compiling a large project) we don't try to transfer all of that in the error. Instead, we can just return the last N bytes.

I helped somebody that got hit by that today.
They used container.Stderr(ctx) and got nothing in it, even though they saw the build failed.
The only way to diagnose was to set the LogOutput to something they could see after the fact. Not great.

Buildkit v0.11 is adding a way of retrieving execution logs after a build finishes, so hopefully that will make it somewhat easier to implement this relative to the huge song+dance required to get the FS of a failed exec op.

@sipsma I'm talking to a developer that is hitting this issue, which is confusing because the issue seems fixed? Do you know which release this fix was part of? Perhaps they just need to upgrade.

@shykes it has not been released yet, there's a few more issues that we need to close before we do the next release: https://github.com/dagger/dagger/milestone/16
Most of those PRs have approval as of this morning, so we can do the release perhaps as early as tomorrow (or monday if we want to avoid the dreaded friday release)


Split API docs

Type of Change

Routes/Pages: /api & new /api/* routes
Components: New API sidebar, modified existing API docs components
Styling: Updated API styling

What issue does this relate to?
Fixes #21
What should this PR do?
TBD.
What are the acceptance criteria?
TBD.
Remaining tasks

[ ] Sidebar responsiveness
[ ] Mobile compatability

Hey @MattIPv4,
Can I do some help for this?

👋 @thetejasmagade Sorry for the delayed reply -- sure thing, you're welcome to work on this. The best bet at this point might be to take the changes from here and open a new PR with further work, rather than trying to contribute into this existing PR as it's so old.


Error messages are difficult to read because of weak of contrast in Slang console

Error messages in the Slang console are difficult to read because they are colored dark red on a black background, having a weak contrast. We have found this during the Hackaton pretty annoying when doing pair programming, sitting in the front of laptop screens.

I would suggest using a brighter color for error messages.

like which color?
usually red is the context of error...

A brighter red. I have checked with a color picker, and you are using the RGB color (128, 0, 0). I would suggest using (192, 0, 0) or (224, 0, 0).

The contrast is quite nice here, although it looks more like purple than red.

The contrast seems to be much better on this screenshot.

It's a different color in the screenshot.
You can see here the 2 colors

red for the slang errors
purple for spring shell errors

seems like Ansi.Color does not support light/bright RED...
only : BLACK, RED, GREEN, YELLOW, BLUE, MAGENTA, CYAN, WHITE
Either we use another library for colors, or change to a diff color from the list...

Or just have all errors be the same colour, and use the content to distinguish between the types of error ...

pending #120 -replacing CLI FW


Getting errors in the log - Template variable warning: 'dict object' has no attribute

Since uninstalling and re-installing the add on today I am seeing errors in the log every minute .. for example:
2022-12-26 23:59:50.730 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'gas_mtr' when rendering '{{ value_json.gas_mtr}}'
2022-12-26 23:59:50.735 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'watt_now' when rendering '{{ value_json.watt_now}}'
2022-12-26 23:59:50.736 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'elec_imp' when rendering '{{ value_json.elec_imp}}'
2022-12-26 23:59:50.738 WARNING (MainThread) [homeassistant.helpers.template] Template variable warning: 'dict object' has no attribute 'elec_exp' when rendering '{{ value_json.elec_exp}}'
My guess is I have done something when I uninstalled and re-installed but don't know what ...
As far as I can see my energy data is going to the dashboard - Smart Meter Electricity: Power seems correct and the HA energy dashboard appears to be showing the correct data ...
Any help would be appreciated.

Hi @snigehere ,
This isn't generally anything to worry about if data is flowing as expected despite being a bit annoying spamming the logs. It happens when data is received without any relevant data or missing data. I've recently worked around an issue where data packets are sent which don't contain any relevant fields, particularly with older meters. I'm assuming this is some sort of heartbeat type packet but I can't be sure. Previously it was causing the plugin to crash but now we simply get a log message stating that expected data was missing from the payload which is a Home Assistant MQTT expectation more so than a plugin issue.
The plugin still sends data regardless of whether all fields are present because it's not uncommon to get data packets which only include gas readings or only import and not export electricity readings for example. In this instance Home Assistant will warn that some expected fields are missing.

Thanks for the explanation Scott ... but I am not sure that's what's happening here
Was this a recent change to push the record to the log?
For me its a bit more than spam ... between 2022-12-27 13:21:18.181 and 2022-12-28 13:21:10.976 .. so just on one day .... I have 34,574 of these messages in the log ... 4 records every 10 seconds .... I hope I am not getting that number of empty records ....
I am using local mqtt connection to my glow IHD

I wonder if the mqtt definitions are messed up

A bit more .. when I look at the detail of the energy dashboard I see an error message in the configuration but its not stopping the data from being displayed in the dashboard .... most odd

Was this a recent change to push the record to the log?

This is a Home Assistant MQTT integration warning in the log, not something I have control over.

Should I see a comma in the json data?

The actual data looks OK to me but it does appear that the local MQTT publishing is doing something weird when you have both gas and electric meters. I can see the timestamps for each meter are different so it must be publishing each meters data separately and I assume every 10 seconds (maybe more). I believe that is different to the behaviour with non-local MQTT.

A bit more .. when I look at the detail of the energy dashboard I see an error message in the configuration but its not stopping the data from being displayed in the dashboard .... most odd

This is weird... I'd assume when Home Assistant starts the entity isn't initialised with it's last known state from history or MQTT retained data but the energy dashboard requires the entity to be in the recorder list so there should be history which can be loaded on startup... very strange.
I can only think of 2 workarounds to avoid the log messages.

Create different sensors for electric and gas meters. Currently the plugin creates a sensor per Glow Device ID and then entities for relevant data fields. This would be significant breaking change.
Data caching in the plugin... Store the last value for each entity so we can send the last value if data is missing. This will result in one or two log messages when the plugin first starts and no value is cached but it should minimise log warnings thereafter. There are of course some risks with this method as it adds some additional complexity to the plugin which could make debugging data issues more tricky but it would be less of a breaking change in theory.

thanks - I will leave you to consider if its worth making changes or not ... I guess it will only impact local mqtt users.  I don't recall seeing all these errors in the log in the past but maybe I was focused on them when I was looking at why it didn't work for me after the last update.
Thanks for your continued support.

Just to add an observation ... One result is that the values for the electricity sensors show zero apart from a very tiny bit of time (eg they flash a value then go to zero again) .. I guess that's because of this issue ... but the gas sensor persists the value

One result is that the values for the electricity sensors show zero apart from a very tiny bit of time (eg they flash a value then go to zero again)

Hmm, this isn't ideal... I would guess this is the default behaviour of the MQTT integration if it receives a payload which is missing entity data, it just sets them to zero although I would find that an odd implementation decision... The plugin code already rejects any readings which are NOT greater than 0 so it can't be the plugin sending zero values. The only thing puzzling me is that I would also expect you to get gas meter readings of zero when electricity data is published but you say these are persisting? Or maybe it's timing and the gas readings are always coming in a few ms after the electricity readings?
Either way I would hope that local caching in the plugin will help this situation for want of a better solution so I will explore this route and see where I end up...
Thanks for your continued debug.

One result is that the values for the electricity sensors show zero apart from a very tiny bit of time (eg they flash a value then go to zero again)

Hmm, this isn't ideal... I would guess this is the default behaviour of the MQTT integration if it receives a payload which is missing entity data, it just sets them to zero although I would find that an odd implementation decision... The plugin code already rejects any readings which are NOT greater than 0 so it can't be the plugin sending zero values. The only thing puzzling me is that I would also expect you to get gas meter readings of zero when electricity data is published but you say these are persisting? Or maybe it's timing and the gas readings are always coming in a few ms after the electricity readings?
Either way I would hope that local caching in the plugin will help this situation for want of a better solution so I will explore this route and see where I end up...
Thanks for your continued debug.

Hi @snigehere , I'm trying to understand a bit more about the data coming in when there are multiple meters in play (gas + electric). I only have electric here so I'm blind in this regard.
Are you able to share some representative MQTT payloads? The main thing I want to understand is whether "gasmeter" is completely omitted from the payload when "electricitymeter" values get updated and vice-versa. I'm concerned this may cause issues with my current dynamic sensor discovery mechanism. It will also help me better decide how to implement caching.
Many thanks.

Let me try
So in MQTT explorer I see this hierarchy:
glow
glow/441793525F6C
glow/441793525F6C/SENSOR
glow/441793525F6C/SENSOR/electricitymeter
glow/441793525F6C/SENSOR/gasmeter
glow/441793525F6C/STATE
For the entity glow/441793525F6C I see the electric values followed a fraction of a second later by gas data then a pause for 10 seconds then electric and a fraction later gas etc etc ...
I took a short video which I hope shows the behaviour
I have also dumped the history from MQTT explorer entities to a text file and also the data from the integration log .. the log mirrors the behaviour I see so a set of electric values then the gas value then just under 10 seconds later it loops again.  The various elements will not quite cover the same time frame as it was running still as I cycled round copying the data but there is a big chunk that will match
I don't know if glow can give any guidance on the expected behaviour - maybe its changed since I started using it ...
I hope this helps - let me know if you need further data .....
https://user-images.githubusercontent.com/104912027/210284528-90ce8865-8a16-4811-b470-0c7d0e0dad4b.mp4
glow mqtt data.txt

Thanks @snigehere , that's definitely helpful.
I would guess in your case the data for both meters is coming in fast enough that the discovery is working OK but I will work on a more robust implementation anyway. It's a bit frustrating that the local MQTT behaviour doesn't more closely mimic what already existed in terms of payload and data publishing but that's life I suppose.
I will keep you posted with progress.

Many thanks Scott

Hi Scott
Many thanks for your work on this .. I installed the update soon after it was released.
The log entries are gone, I see the value in my dashboard and have a solid line for the graphs again

Everything else seems to be working OK so I am closing this bug report

@snigehere pleased to hear everything is working well for you now. It was quite a big overhaul so hopefully there haven't been any additional bugs introduced.
I appreciate the help debugging this one.


near help has typos

near state repeats twice in near-shell help
[WARNING] Didn't find config at /Users/zaver/Projects/nearcore/core/store/src/config, using default shell config
near <command>

Commands:
  near create_account <accountId>           create a developer account
  near state <accountId>                    view account
  near delete_account <accountId>           delete an account and transfer funds
  <beneficiaryId>                           to beneficiary account.
  near keys <accountId>                     view account public keys
  near tx-status <hash>                     lookup transaction status by hash
  near build                                build your smart contract
  near deploy                               deploy your smart contract
  near call <contractName> <methodName>     schedule smart contract call which
  [args]                                    can modify state
  near view <contractName> <methodName>     make smart contract call which can
  [args]                                    view state
  near state <accountId>                    view account
  near send <sender> <receiver> <amount>    send tokens to given receiver
  near clean                                clean the build environment
  near new_project [projectDir]             create a new blank project
  near stake [accountId] [publicKey]        create staking transaction
  [amount]
  near login                                create a developer account

Options:
  --help                     Show help                                 [boolean]
  --version                  Show version number                       [boolean]
  --nodeUrl, --node_url      NEAR node URL
                                     [string] [default: "http://localhost:3030"]
  --networkId, --network_id  NEAR network ID, allows using different keys based
                             on network            [string] [default: "default"]
  --helperUrl                NEAR contract helper URL                   [string]
  --keyPath                  Path to master account key                 [string]
  --homeDir                  Where to look for master account, default is
                             ~/.near    [string] [default: "/Users/zaver/.near"]
  --accountId, --account_id  Unique identifier for the account          [string]

Please enter a command

Can't reproduce.


CMake 3.20.1 problems when install

brew config output
brew config
HOMEBREW_VERSION: 3.1.2
ORIGIN: https://github.com/Homebrew/brew
HEAD: bc9b98aa0ba777889218ac51f67ccc76b0be6a28
Last commit: 27 hours ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: 42e0cb4fe341dd63f0418b8e41ce50e4c6413189
Core tap last commit: 2 hours ago
Core tap branch: master
HOMEBREW_PREFIX: /usr/local
HOMEBREW_CASK_OPTS: []
HOMEBREW_MAKE_JOBS: 12
Homebrew Ruby: 2.6.3 => /usr/local/Homebrew/Library/Homebrew/vendor/portable-ruby/2.6.3_2/bin/ruby
CPU: dodeca-core 64-bit kabylake
Clang: 12.0 build 1200
Git: 2.24.3 => /Applications/Xcode.app/Contents/Developer/usr/bin/git
Curl: 7.64.1 => /usr/bin/curl
macOS: 10.15.7-x86_64
CLT: <IP_ADDRESS>.17
Xcode: 12.4

brew doctor output
brew doctor
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry or file an issue; just ignore this. Thanks!

Warning: A newer Command Line Tools release is available.
Update them from Software Update in System Preferences or run:
  softwareupdate --all --install --force

If that doesn't show you any updates, run:
  sudo rm -rf /Library/Developer/CommandLineTools
  sudo xcode-select --install

Alternatively, manually download them from:
  https://developer.apple.com/download/more/.

Warning: Some installed formulae are deprecated or disabled.
You should find replacements for the following formulae:
<EMAIL_ADDRESS>

I ran brew update and am still able to reproduce my issue.
I have resolved all warnings from brew doctor and that did not fix my problem.
What were you trying to do (and why)?
Install latest cmake 3.20.1
What happened (include all command output)?
#!/bin/bash --login -eo pipefail
brew install cmake
Updating Homebrew...
==> Auto-updated Homebrew!
Updated 3 taps (homebrew/cask-versions, homebrew/core and adoptopenjdk/openjdk).
==> New Formulae
as-tree                    latino                     python-tabulate
bas55                      leaf-proxy<EMAIL_ADDRESS>brook                      libmd                      qt-libiodbc
cadence-workflow           libpipeline                qt-mariadb
cherrytree                 libprelude                 qt-mysql
clusterctl                 libunwind                  qt-percona-server
coin3d                     linux-pam                  qt-postgresql
crackpkcs                  lttng-ust                  qt-unixodbc
crispy-doom                mapcidr                    rdkit
curlie                     minisat                    rosa-cli
dasel                      moto                       rtl_433
datalad                    multitime                  saml2aws
delve                      mx                         six
djl-serving                name-that-hash             smu
dua-cli                    net-tools                  snowpack
enkits                     numactl                    spaceship
enzyme                     obfs4proxy                 sqlancer
epr                        open-adventure             systemd
geph4                      openmama                   threemux
ghc@9                      openmodelica               timg
glibc                      oras                       tomcat@9
go-boring                  orgalorg                   truffle
<EMAIL_ADDRESS>                  organize-tool              tz
gopass-jsonapi             pandoc-plot                virtualenv
haruhi-dl                  pcalc                      waffle
haskell-language-server    pcp                        wllvm
iconsur                    phpbrew                    xcprojectlint
influxdb@1                 projectm                   xplr
kertish-dfs                pure                       xray
kickstart                  pyqt-3d                    yubikey-agent
klee                       pyqt-builder               zinit
kotlin-language-server     pyqt-networkauth           zlib-ng
kubergrunt                 pyside@2                   zsh-vi-mode
==> Updated Formulae
Updated 5107 formulae.
==> Renamed Formulae
fcct -> butane
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>ht-rust -> xh
kde-extra-cmake-modules -> extra-cmake-modules
kde-karchive -> karchive
kde-kdoctools -> kdoctools
kde-ki18n -> ki18n
kde-threadweaver -> threadweaver
libsasl2 -> cyrus-sasl
minizip2 -> minizip-ng
<EMAIL_ADDRESS>-><EMAIL_ADDRESS>pyqt5 -> pyqt@5
qt5 -> qt@5
==> Deleted Formulae
atlassian-cli              avian                      geant4
==> New Casks
ableton-live-intro10       adoptopenjdk16-openj9      dnagedcom-beta
ableton-live-lite10        adoptopenjdk16-openj9-jre  local-beta
ableton-live-standard10    arduino-beta               netnewswire-beta
ableton-live-suite10       clashx-pro                 olympus
adoptopenjdk16             dash5                      qq-beta
adoptopenjdk16-jre         deadbeef-nightly           zulu15
==> Updated Casks
Updated 75 casks.
==> Deleted Casks
hex-fiend-beta

==> Downloading https://homebrew.bintray.com/cmake-3.20.1.catalina.bottle.tar.gz
##O#- #
curl: (22) The requested URL returned error: 404 Not Found
Trying a mirror...
==> Downloading https://ghcr.io/v2/homebrew/core/cmake-3.20.1.catalina.bottle.ta
==> Downloading from https://github.com/-/v2/packages/container/package/homebrew
#=#=#
curl: (22) The requested URL returned error: 404
Error: Failed to download resource "cmake"
Download failed: https://ghcr.io/v2/homebrew/core/cmake-3.20.1.catalina.bottle.tar.gz

Exited with code exit status 1

What did you expect to happen?
Install cmake 3.20.1
Step-by-step reproduction instructions (by running brew commands)
brew install cmake

Please do brew update and try again. See also https://github.com/Homebrew/homebrew-core/issues/75243.


include: dfu: mcuboot: Fix header information for MCUBoot

Add updated version of MCUBoot header and additional header information.
Signed-off-by: Sigvart Hovland<EMAIL_ADDRESS>

Shouldn't this also include updates to boot_read_bank_header()?
I would have expected an addition of a boot_read_v2_header() function that filled this in properly, and also changes to boot_read_bank_header() to check the magic numbers to decide whether to call that or boot_read_v1_header().

https://github.com/zephyrproject-rtos/zephyr/blob/1ef9b20f6119b1884ebb1d4cd2823a866b92a1ab/subsys/dfu/boot/mcuboot.c#L30-L57
Peeked into the mcuboot file and the header is already implemented there. It's weird that we have this here and not in the header file. Do you know why?

Peeked into the mcuboot file and the header is already implemented there. It's weird that we have this here and not in the header file. Do you know why? The V1 header described here is the V2 header described in the PR AFIK.

v1 here means "the one used in mcuboot versions 1.x.y". Is there an upcoming mcuboot version 2 that is changing the header version? If not, I'm not sure there's anything wrong with this code as-is -- am I missing something?

@mbolivar Change the PR to reflect the changes I wanted to see/do. For me it is weird that the header information found in the header file is not reflecting the real layout of the mcuboot header. By moving it out of the mcuboot.c file protocols and other files which want to use some information from the mcuboot header can easily use it by including the header for mcuboot instead of having to define the layout again in a struct by themselves.

I think the raw header can be removed from mcuboot.c

I think exposing the magic would be helpful at least but that maybe just me as it can tell something about which version of MCUBoot the image belongs too as they have had two. However I'll change the PR to move the raw header out into the header so that it can be used by other files which needs this information.

I think exposing the magic would be helpful at least but that maybe just me as it can tell something about which version of MCUBoot the image belongs too as they have had two.

That's what the mcuboot_version field should be capturing. Upstream mcuboot promised that incompatible changes to the header would be accompanied by major version bumps, so a single int should be enough to tell what version of the bootloader the image was built for.

However  I'll change the PR to move the raw header out into the header so that  it can be used by other files which needs this information. Or expose an  additional API which can be called to check if it is an mcuboot header

Sure, adding "raw" routines if they are useful to someone could be reasonable -- I don't know your use case. But the point of designing this API in this way was to hide the user from these details when possible.

I don't see the abstraction to be all that useful to be honest but it is fine to keep it simple.  It's used 2 places in conjecture with boot_img_read_bank_header. This means you can't detect the image type in transit you actually have to store it before you can start guessing if it is an MCUBoot image or garbage.
I can just store the raw_header layout in the file I'm working in but would it make sense to also expose the actual raw_header in the header dfu/mcuboot.h? For use-cases such as this or do you actually want to hide it behind something like bool boot_is_header(u8_t *buf, size_t len, struct mcuboot_header) Which populates the structure if true?

I assume the functionality is not needed by anyone else I'll just close this

I assume the functionality is not needed by anyone else I'll just close this

Like I said if it's useful to expose the raw header then that makes sense to do via additional API.
BTW, do you know what's going on with the new MCUboot version keeping the magic number but having incompatible changes to the header? That seems inconsistent with the previous guarantees about versioning.


Subject filtering according to entity

Getting all the users and their permissions to a specific resource?
Example:
in organization:1
user:1 is owner
user:2 is member
user:3 is member
I would like something like this:
Request: which users have access to organization:1
Response: [ "user:1#owner", "user:2#member", "user:3#member" ]

This would be beneficial both ways -
"What are all the relationships to Organization:1" -> user:1#owner, user:2#member...
"What are all the relationships for User:1 " -> organization:1#owner, repository:3#maintainer