[3.2.0] Cannot invoke Web Socket APIs when OAuth2 Opaque (Reference) Access Tokens are used

Description:
Invocation of Web Socket APIs is failing when using Opaque access tokens. This is due to the incorrect URI which contains multiple "/PRODUCTION" or "/SANDBOX" when initiating the Web Socket handshake.
Affected Product Version:
wso2am-3.2.0+1639932343262.full.staging.zip
Environment details (with versions):

OS: Ubuntu 20.04.4 LTS

This is fixed and released via U2 and WUM. Hence, closing the issue.


aws: route53, fix duplicate zone

https://github.com/GoogleCloudPlatform/terraformer/issues/66

@sergeylanzman I still get this error:
duplicate resource found: aws_route53_record_


License missing

Really cool project.
It would be nice to see some kind of license file or section of the README even if it stays proprietary.

Thank you very much. I added the licence as you requested.
Have a great day! :)


changelog-d: init / justStaticExecutables

Motivation
changelog-d had an unnecessarily large runtime closure.
Description of changes

Use justStaticExecutables

Make changelog-d a top level package

Refactor

The combined PR diff doesn't understand the file move, so it's easier to review individual commits.
Things done

Built on platform(s)

[ ] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes (or backporting 23.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[ ] Fits CONTRIBUTING.md.

Yeah, you'd have to use this git-only project as a library to find these changes. Basically you'd be asking for it.


Kafka Input Polling issue

Moved from https://github.com/elastic/logstash/issues/9421

Version: 6.2.4
Operating System: Ubuntu 16.04
Config File (if you have sensitive info, please remove it):

input {
  kafka {
    auto_offset_reset  => "earliest"
    bootstrap_servers  => "SERVERS"
    consumer_threads   => 4
    enable_auto_commit => "false"
    group_id           => "GROUP"
    client_id          => "CLIENT"
    topics_pattern     => "PATTERN"
    codec              => "json"
  }
}
filter {
[...]
}
output {
  elasticsearch {
    index =>              "INDEX"
    hosts =>              ["SERVER"]
    document_id =>        "%{[@metadata][fingerprint]}"
    template =>           "/etc/logstash/index_template.json"
    template_name =>      "logging"
    template_overwrite => true
  }
}

Steps to Reproduce:

take a config like the one above (filters are not required)
start logstash (with some continous input)
make ES unreachable somehow
make it reachable after some time

More Info:
With Kafka input and Elasticsearch output, logstash stops if elasticsearch is unreachable for a while.
The process is still running, but doesnt process new data.
The logstash is running in Kubernetes, so i have the problem that i need to manualy restart it each time ES was not reachable. IMHO it should end/stop the sevice or wait for the cluster to get up again.
Log output while ES is down (for some hours in my case):
2018-04-23T16:58:39.510378721Z [WARN ] 2018-04-23 16:58:39.510 [Ruby-0-Thread-11@[main]>worker1: /usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:385] elasticsearch - UNEXPECTED POOL ERROR {:e=>#}
2018-04-23T16:58:39.510487776Z [ERROR] 2018-04-23 16:58:39.510 [Ruby-0-Thread-11@[main]>worker1: /usr/share/logstash/logstash-core/lib/logstash/pipeline.rb:385] elasticsearch - Attempted to send a bulk request to elasticsearch, but no there are no living connections in the connection pool. Perhaps Elasticsearch is unreachable or down? {:error_message=>"No Available connections", :class=>"LogStash::Outputs::ElasticSearch::HttpClient::Pool::NoConnectionAvailableError", :will_retry_in_seconds=>64}
2018-04-23T16:58:42.951478403Z [WARN ] 2018-04-23 16:58:42.951 [Ruby-0-Thread-8: /usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-output-elasticsearch-9.1.1-java/lib/logstash/outputs/elasticsearch/http_client/pool.rb:232] elasticsearch - Attempted to resurrect connection to dead ES instance, but got an error. {:url=>"SERVER", :error_type=>LogStash::Outputs::ElasticSearch::HttpClient::Pool::HostUnreachableError, :error=>"Elasticsearch Unreachable: [SERVER][Manticore::SocketException] Connection refused (Connection refused)"}

Log output at the time es is up again:
2018-04-23T16:59:42.326249582Z Exception in thread "Ruby-0-Thread-23: /usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-input-kafka-8.0.6/lib/logstash/inputs/kafka.rb:241" Exception in thread "Ruby-0-Thread-22: /usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-input-kafka-8.0.6/lib/logstash/inputs/kafka.rb:241" org.apache.kafka.clients.consumer.CommitFailedException: Commit cannot be completed since the group has already rebalanced and assigned the partitions to another member. This means that the time between subsequent calls to poll() was longer than the configured max.poll.interval.ms, which typically implies that the poll loop is spending too much time message processing. You can address this either by increasing the session timeout or by reducing the maximum size of batches returned in poll() with max.poll.records.
2018-04-23T16:59:42.326318585Z 	at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.sendOffsetCommitRequest(org/apache/kafka/clients/consumer/internals/ConsumerCoordinator.java:721)
2018-04-23T16:59:42.326342549Z 	at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.commitOffsetsSync(org/apache/kafka/clients/consumer/internals/ConsumerCoordinator.java:599)
2018-04-23T16:59:42.326350452Z 	at org.apache.kafka.clients.consumer.KafkaConsumer.commitSync(org/apache/kafka/clients/consumer/KafkaConsumer.java:1203)
2018-04-23T16:59:42.326358068Z 	at java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498)
2018-04-23T16:59:42.326363546Z 	at org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:438)
2018-04-23T16:59:42.326455383Z 	at org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:302)
2018-04-23T16:59:42.32646587Z 	at RUBY.block in thread_runner(/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-input-kafka-8.0.6/lib/logstash/inputs/kafka.rb:269)
2018-04-23T16:59:42.326472091Z 	at org.jruby.RubyProc.call(org/jruby/RubyProc.java:289)
2018-04-23T16:59:42.326477217Z 	at org.jruby.RubyProc.call(org/jruby/RubyProc.java:246)
2018-04-23T16:59:42.326483081Z 	at java.lang.Thread.run(java/lang/Thread.java:748)
2018-04-23T16:59:42.326607591Z org.apache.kafka.clients.consumer.CommitFailedException: Commit cannot be completed since the group has already rebalanced and assigned the partitions to another member. This means that the time between subsequent calls to poll() was longer than the configured max.poll.interval.ms, which typically implies that the poll loop is spending too much time message processing. You can address this either by increasing the session timeout or by reducing the maximum size of batches returned in poll() with max.poll.records.
2018-04-23T16:59:42.326619456Z 	at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.sendOffsetCommitRequest(org/apache/kafka/clients/consumer/internals/ConsumerCoordinator.java:721)
2018-04-23T16:59:42.326680519Z 	at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.commitOffsetsSync(org/apache/kafka/clients/consumer/internals/ConsumerCoordinator.java:599)
2018-04-23T16:59:42.326690954Z 	at org.apache.kafka.clients.consumer.KafkaConsumer.commitSync(org/apache/kafka/clients/consumer/KafkaConsumer.java:1203)
2018-04-23T16:59:42.326696757Z 	at java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498)
2018-04-23T16:59:42.326703114Z 	at org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:438)
2018-04-23T16:59:42.326749471Z 	at org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:302)
2018-04-23T16:59:42.326760403Z 	at RUBY.block in thread_runner(/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-input-kafka-8.0.6/lib/logstash/inputs/kafka.rb:269)
2018-04-23T16:59:42.326801054Z 	at org.jruby.RubyProc.call(org/jruby/RubyProc.java:289)
2018-04-23T16:59:42.326889432Z 	at org.jruby.RubyProc.call(org/jruby/RubyProc.java:246)
2018-04-23T16:59:42.326901776Z 	at java.lang.Thread.run(java/lang/Thread.java:748)
2018-04-23T16:59:42.33038824Z Exception in thread "Ruby-0-Thread-20: /usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-input-kafka-8.0.6/lib/logstash/inputs/kafka.rb:241" Exception in thread "Ruby-0-Thread-21: /usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-input-kafka-8.0.6/lib/logstash/inputs/kafka.rb:241" org.apache.kafka.clients.consumer.CommitFailedException: Commit cannot be completed since the group has already rebalanced and assigned the partitions to another member. This means that the time between subsequent calls to poll() was longer than the configured max.poll.interval.ms, which typically implies that the poll loop is spending too much time message processing. You can address this either by increasing the session timeout or by reducing the maximum size of batches returned in poll() with max.poll.records.
2018-04-23T16:59:42.330428219Z 	at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.sendOffsetCommitRequest(org/apache/kafka/clients/consumer/internals/ConsumerCoordinator.java:721)
2018-04-23T16:59:42.330513757Z 	at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.commitOffsetsSync(org/apache/kafka/clients/consumer/internals/ConsumerCoordinator.java:599)
2018-04-23T16:59:42.33053427Z 	at org.apache.kafka.clients.consumer.KafkaConsumer.commitSync(org/apache/kafka/clients/consumer/KafkaConsumer.java:1203)
2018-04-23T16:59:42.330542261Z 	at java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498)
2018-04-23T16:59:42.330548441Z 	at org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:438)
2018-04-23T16:59:42.330554574Z 	at org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:302)
2018-04-23T16:59:42.33056064Z 	at RUBY.block in thread_runner(/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-input-kafka-8.0.6/lib/logstash/inputs/kafka.rb:269)
2018-04-23T16:59:42.330566733Z 	at org.jruby.RubyProc.call(org/jruby/RubyProc.java:289)
2018-04-23T16:59:42.330572125Z 	at org.jruby.RubyProc.call(org/jruby/RubyProc.java:246)
2018-04-23T16:59:42.330677833Z 	at java.lang.Thread.run(java/lang/Thread.java:748)
2018-04-23T16:59:42.330688725Z org.apache.kafka.clients.consumer.CommitFailedException: Commit cannot be completed since the group has already rebalanced and assigned the partitions to another member. This means that the time between subsequent calls to poll() was longer than the configured max.poll.interval.ms, which typically implies that the poll loop is spending too much time message processing. You can address this either by increasing the session timeout or by reducing the maximum size of batches returned in poll() with max.poll.records.
2018-04-23T16:59:42.330696963Z 	at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.sendOffsetCommitRequest(org/apache/kafka/clients/consumer/internals/ConsumerCoordinator.java:721)
2018-04-23T16:59:42.330702453Z 	at org.apache.kafka.clients.consumer.internals.ConsumerCoordinator.commitOffsetsSync(org/apache/kafka/clients/consumer/internals/ConsumerCoordinator.java:599)
2018-04-23T16:59:42.330713048Z 	at org.apache.kafka.clients.consumer.KafkaConsumer.commitSync(org/apache/kafka/clients/consumer/KafkaConsumer.java:1203)
2018-04-23T16:59:42.330718522Z 	at java.lang.reflect.Method.invoke(java/lang/reflect/Method.java:498)
2018-04-23T16:59:42.330724478Z 	at org.jruby.javasupport.JavaMethod.invokeDirectWithExceptionHandling(org/jruby/javasupport/JavaMethod.java:438)
2018-04-23T16:59:42.331021615Z 	at org.jruby.javasupport.JavaMethod.invokeDirect(org/jruby/javasupport/JavaMethod.java:302)
2018-04-23T16:59:42.331034813Z 	at RUBY.block in thread_runner(/usr/share/logstash/vendor/bundle/jruby/2.3.0/gems/logstash-input-kafka-8.0.6/lib/logstash/inputs/kafka.rb:269)
2018-04-23T16:59:42.331041498Z 	at org.jruby.RubyProc.call(org/jruby/RubyProc.java:289)
2018-04-23T16:59:42.331046719Z 	at org.jruby.RubyProc.call(org/jruby/RubyProc.java:246)
2018-04-23T16:59:42.331051815Z 	at java.lang.Thread.run(java/lang/Thread.java:748)```

Same problem here :(

Hi @andrewvc, thanks for sharing the detailed tuning steps. What changes you suggest in case of slower indexing rates than incoming messages ?
After making these changes and running pipeline for couple of days, I am encountering heap issues on logstash indexer. Error are something like this,

Auto offset commit failed for group logstash-indexer-onprem: Commit cannot be completed since the group has already rebalanced and assigned the partitions to another member. This means that the time between subsequent calls to poll() was longer than the configured session.timeout.ms, which typically implies that the poll loop is spending too much time message processing. You can address this either by increasing the session timeout or by reducing the maximum size of batches returned in poll() with max.poll.records.

Error while attempting to check/cancel excessively long grok patterns {:message=>"Java heap space", :class=>"Java::JavaLang::OutOfMemoryError", :backtrace=>[]}

@andrewvc any additional information on this? Also is there a way to have the plugin restart after it disconnects? (some sort of retry logic)


Move data into a json file

Moved data out. Should fit your requirements. Note the relative path.
It's also possible to abstract the path into an absolute path, and replace this with an environment variable declared at compile-time
Fixes #12 (Whoops got this number wrong)

Problem is prepublish doesn't move the .json file to the dist folder. That is the main issue actually...

Ah sorry that was quite silly of me. I've made the necessary fixes.

Some package missing on package.json?
ReferenceError: Unknown plugin "inline-json-import" specified in "/home/travis/build/gabidavila/react-usa-map/.babelrc" at 0, attempted to resolve relative to "/home/travis/build/gabidavila/react-usa-map"

My bad.  I had to change the dev branch and lost the merge. I want to keep the track of your contribution and not just copy and paste it. Thanks.


wagtail.core.models.Site is rejecting certain Page objects.

Found a bug? Please fill out the sections below. 👍
Issue Summary
A summary of the issue.
Internal Server Error is displayed while running tests even though the Site object saves.
Steps to Reproduce

Start a new project with wagtail start myproject
Edit models.py as follows...

• home / models.py
class HomePage(Page):
    content = StreamField([
        ('our_services_statement', StatementBlock()),
        ('the_technology_we_utilize', TechStatementBlock()),
        ('meet_codedan_developers', DeveloperBlock()),
        ('meet_codedan_analysts', AnalystsBlock()),
    ], null=True, blank=True)
    objects = models.PageManager()

    content_panels = Page.content_panels + [
        StreamFieldPanel('content'),
    ]
    template = 'home.html'

Edit home/tests.py as follows:

• home / tests.py
class HomePageTestCase(StaticLiveServerTestCase, TestCase):
    @classmethod
    def setUpClass(cls):
        if Page.objects.first():
            cls.root = Page.objects.create(title="Root", path='001', depth=1)
        else:
            cls.root = Page.objects.get(title="Root").specific

        # Index page is compulsory
        cls.codedan_index_page = HomePage(
            title="Home Page",
            content = [
                    ('our_services_statement', {'statement': 'Default statement'}),
                    ('the_technology_we_utilize', {'statement': 'Default technology'}),
                    ('meet_codedan_developers', {'statement': 'Default developers'}),
                    ('meet_codedan_analysts', {'statement': 'Default analysts'}),
            ]
        )
        cls.root.add_child(instance=cls.codedan_index_page)
        cls.saved_revision_codedan_index_page = cls.codedan_index_page.save_revision()
        cls.saved_revision_codedan_index_page.publish()
        cls.codedan_index_page.save()

        # Create site object if there isn't any

        if Site.objects.first():
            cls.site = Site.objects.first()
            cls.site.root_page = cls.codedan_index_page
            cls.site.save()

        else:
            cls.site = Site.objects.create(
                site_name="localhosted",
                is_default_site=True,
                root_page=cls.codedan_index_page
            )

        cls.codedan_index_page.content = [
            ('our_services_statement', {'statement': 'Default statement'}),
            ('the_technology_we_utilize', {'statement': 'Default technology'}),
            ('meet_codedan_developers', {'statement': 'Default developers'}),
            ('meet_codedan_analysts', {'statement': 'Default analysts'}),
        ]

        cls.codedan_index_page.save()
        super(HomePageTestCase, cls).setUpClass()
        cls.browser = selenium.webdriver.Chrome()

    def test_tech_we_utilize_gets_displayed(self):
        self.browser.get(self.live_server_url)
        technology_we_utilize = self.browser.find_element_by_id('tech-we-use-chunk')
        self.assertTrue(technology_we_utilize.text.is_displayed(), True)

Any other relevant information. For example, why do you consider this a bug and what did you expect to happen instead?
• I consider this a bug because if you set the root_page of the Site object to the root page (Page.objects.get(id=1)), there is no server error displayed. However, the root page isn't the desired Index Page. This means that calls to the index page self.get_live_server_url would load a web page that just displays the text "Root"  or the familiar "Welcome to your wagtail site" page. This is the code to explain what I am describing:
# in this case, there is no Internal Server Error Displayed
class HomePageTestCase(StaticLiveServerTestCase, TestCase):
        # ...
        if Site.objects.all():
            cls.site = Site.objects.first()
            cls.site.root_page = cls.root
            cls.site.save()

        else:
            cls.site = Site.objects.create(
                site_name="localhosted",
                is_default_site=True,
                root_page=cls.root
            )
        # ...

• I also consider this a bug because, if you don't add the stream field information, and set the desired index page as the root_page of the Site object, it loads with no problem. However, the HomePage object does not have any StreamField data saved (which defeats the aim of having a test suite in the first place). Below is the code describing what I have just described.
# this is another situation where there is no Internal Server Error displayed
class HomePageTestCase(StaticLiveServerTestCase, TestCase):
        # ...

        # Index page is compulsory
        cls.codedan_index_page = HomePage(  # notice that the StreamField data has been removed
            title="Home Page",
        )
        cls.root.add_child(instance=cls.codedan_index_page)
        cls.saved_revision_codedan_index_page = cls.codedan_index_page.save_revision()
        cls.saved_revision_codedan_index_page.publish()
        cls.codedan_index_page.save()

        # Create site object if there isn't any

        if Site.objects.all():
            cls.site = Site.objects.first()
            cls.site.root_page = cls.codedan_index_page
            cls.site.save()

        else:
            cls.site = Site.objects.create(
                site_name="localhosted",
                is_default_site=True,
                root_page=cls.codedan_index_page
            )
        # ...

SO FROM ALL INDICATIONS, THE SITE OBJECT IS FINE WITH HAVING root_page SET TO A ROOT PAGE OBJECT (e.g. Page.objects.get(id=1))  OR HAVING root_page SET TO ANOTHER PAGE OBJECT (IN THIS CASE THE INDEX OBJECT) AS LONG AS THAT PAGE OBJECT DOES NOT HAVE STREAMFIELD DATA SET UP
Please also note that in all these situations, the Site object still saves but the test case returns a browser window saying Internal Server Error

I have confirmed that this issue can be reproduced as described on a fresh Wagtail project: (no)

Technical details

Python version: Python 3.6.9
Django version: 3.1.2
Wagtail version: 2.10.2
Browser version: https://www.whatsmybrowser.org/b/Y8H8M

Hi @alvindera97, thanks for your detailed report.
Does your HomePage model work fine in the admin UI: can you create / preview / publish a page? Does home.html exist?
You haven't included the definition of your various Blocks here. Is {'statement': 'Default developers'} a workable value for all of them?
Have you configured logging so that you can get some more helpful error output from your tests?

Hi @alvindera97,
The steps you have provided are not sufficient to replicate the issue, as they do not include the template or StreamField block definitions. With some basic adjustments (such as adding
 to the home.html template) I was able to get the test to pass, which suggests that the problem is at least partly in the code we haven't seen here.
As I mentioned at https://github.com/wagtail/wagtail/issues/6455#issuecomment-707697173, the failure of this testing setup to provide a meaningful error message is a Selenium / Django configuration issue, not a Wagtail bug. If you were to rewrite the test using the Django test client to fetch the appropriate page and check for the ID in the HTML, I'm confident that it would give you a more useful error trace. That doesn't mean that Selenium is the wrong approach - just that there is more setup to be done that's out of scope for us to assist with. (Yes, it would indeed be nice if this all worked out of the box, but as I'm sure you understand, we have enough work to do in maintaining Wagtail itself - how other parts of the tech stack interoperate is really out of our hands.)

Hi @alvindera97, thanks for your detailed report.
Does your HomePage model work fine in the admin UI: can you create / preview / publish a page? Does home.html exist?
You haven't included the definition of your various Blocks here. Is {'statement': 'Default developers'} a workable value for all of them?
Have you configured logging so that you can get some more helpful error output from your tests?

Yeah, my HomePage model works fine in the admin UI. I wasn't able to notice anything amiss with the setUpClass until I tried running the test. I think this all boils down to the inability to get a proper glimpse of what's wrong during the test. The "Internal Server Error" page is not only annoying, It is extremely useless at anything other than claiming that there was a server error.
Thank you for the hard work and support that you have put into Wagtail and into Open Source Development. I am really proud to be working with Wagtail and Wagtail Developers (I also think you guys have a cooler "It worked" page counterpart compared to Django's" ... You've all been [unsurprisingly] right with your recommendations and it is now much clearer to me that this isn't a Wagtail specific problem. Unfortunately, I am at a dilemma on who exactly I should lay my complaint to —
"Selenium" or "Django" — in reference to the "Internal Server Error" page. If you have any suggestions, I would love to hear it. It would make the world a better place if a trace back or an error page was displayed.
To the solution of the problem, it was basically a syntax error on the template. I couldn't believe it but it turned out that everything worked apart from the section of my template that was dependent on the StreamField content. Another thing that made this issue look like a bug was that when I used @override_settings(DEBUG=True) on the test method, there was no TemplateSyntaxError page displayed. Still the same old "Internal Server Error".
Thanks again. If there's any idea as to who I can report the "Internal System Error" page to, or if you think it's worth reporting, I would really love to hear it. It's been a pleasure working with the community and Wagtail Developers.


GLES2 Unimplemented WorldEnvironment Properties

Godot version:
72db300
OS/device including version:
Windows 10 64 Bit
NVIDIA GTX 960M
Driver v416.16
Issue description:
WorldEnvironment has several properties that currently do not work in GLES2, but are present in-editor.

Tonemap
Auto Exposure
Screen Space Reflections
Screen Space Ambient Occlusion
Depth of Field Far Blur
Depth of Field Near Blur
Glow
Adjustments

Steps to reproduce:

Add a WorldEnvironment node and turn on any of the listed properties while in GLES2 mode.

Minimal reproduction project:
GLES2_WORLDENVIRONMENT.zip

https://github.com/godotengine/godot/issues/21809
Only works panorama/procedural sky, ambient light and fog.

Also worth noting, but might be worthy of a new issue: Ambient light is not affected by the color set in the picker.

Works for me. Add a mesh instance to the scene, decrease sky contribution and move the picker for appreciate the effect.

I'm not sure turning off the parameters if you're on GLES2 is a good idea. Obviously it would be good to communicate these properties aren't functional.
However for someone who is making a game supporting both GLES3 and GLES2 because they are targeting both desktop and mobile, they may not be too happy if their settings disappear just because they are running a test on GLES2.

I'm sure I'm not the only one trying to support GLES2/3 at the same time so something even as simple as "GLES3 ONLY" in the tooltip would be much appreciated, though obviously something a bit more visible would be much more effective.


Edge version doesn't launch anymore (fatal: can only run as pid 1)

Description of problem:
Edge version fails to launch
Zigbee2mqtt add-on version (if edge, please report commit hash):
Edge

Running platform (details from Suypervisor > System)
Core: core-2022.2.9
Supervisor: supervisor-2022.05.1
Operating System: Home Assistant OS 7.4

Your logs from Home Assistant Supervisor
s6-overlay-suexec: fatal: can only run as pid 1

Description of problem: Edge version fails to launch
Zigbee2mqtt add-on version (if edge, please report commit hash):
Edge

Running platform (details from Suypervisor > System)
Core: core-2022.2.9
Supervisor: supervisor-2022.05.1
Operating System: Home Assistant OS 7.4

Your logs from Home Assistant Supervisor
s6-overlay-suexec: fatal: can only run as pid 1

I have the exact same problem with Edge version,

Same here.
Seems to be caused by HA update to the last S6-overlay version, check here : https://developers.home-assistant.io/blog/2022/05/12/s6-overlay-base-images/

Adding init: false to the config.json (in correct json format) also leads to other subsequent failures. Even though it fixes the initial error, all the other shell scripts for startup don't work (Permission Denied). I tried changing them to +x in the git repo, and trying the recommended apparmor.txt but still get permission denied, so I gave up.

I have the same problem:
Zigbee2mqtt Edge  s6-overlay-suexec  fatal  can only run as pid 1

any news on that? having the same issue!

same here

Same

Same here

Figured it out. So the steps in the blog are still valid for fixing this addon, add init: false and modify files to be executable.
The extra problem is that this addon doesn't have a build.yaml file and isn't pinning the version of its base image. Latest for the alpine base image is now 3.15 and this addon doesn't work on 3.15. It needs a build.yaml pinning the version to 3.14 until the application an be updated to work on 3.15. This part isn't related to s6 v3 it just happened to bite at the same time. I'll put in a PR for all the above.

Figured it out. So the steps in the blog are still valid for fixing this addon, add init: false and modify files to be executable.
The extra problem is that this addon doesn't have a build.yaml file and isn't pinning the version of its base image. Latest for the alpine base image is now 3.15 and this addon doesn't work on 3.15. It needs a build.yaml pinning the version to 3.14 until the application an be updated to work on 3.15. This part isn't related to s6 v3 it just happened to bite at the same time. I'll put in a PR for all the above.

I pulled your PR into my repo (https://github.com/thardie/hassio-zigbee2mqtt) and it doesn't work for me. Did I mess something up? Here's my startup log:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/socat.sh
/package/admin/s6-overlay-<IP_ADDRESS>/etc/s6-rc/scripts/cont-init: line 14: /etc/cont-init.d/socat.sh: Permission denied
cont-init: info: /etc/cont-init.d/socat.sh exited 126
cont-init: info: running /etc/cont-init.d/zigbee2mqtt.sh
/package/admin/s6-overlay-<IP_ADDRESS>/etc/s6-rc/scripts/cont-init: line 14: /etc/cont-init.d/zigbee2mqtt.sh: Permission denied
cont-init: info: /etc/cont-init.d/zigbee2mqtt.sh exited 126
cont-init: warning: some scripts exited nonzero
s6-rc: warning: unable to start service legacy-cont-init: command exited 1
/run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.
/run/s6/basedir/scripts/rc.init: fatal: stopping the container.
s6-rc: info: service fix-attrs: stopping
s6-rc: info: service fix-attrs successfully stopped
s6-rc: info: service s6rc-oneshot-runner: stopping
s6-rc: info: service s6rc-oneshot-runner successfully stopped

@thardie in your fork you still list the same image as the one here.
To test the branch you would have to pull it into your /addons folder and merge the common folder and zigbee2mqtt or zigbee2mqtt-edge folders to make a normal addon that supervisor can build an image for. Or you'd have to adjust the CI in your fork so you can actually publish your own images to dockerhub and use them.

@thardie in your fork you still list the same image as the one here.
To test the branch you would have to pull it into your /addons folder and merge the common folder and zigbee2mqtt or zigbee2mqtt-edge folders to make a normal addon that supervisor can build an image for. Then remove image from the config.json so supervisor does build a new image and doesn't just use the one from dockerhub. Or you'd have to adjust the CI in your fork so you can actually publish your own images to dockerhub and then adjust the config.json to use them.

Sorry to be a PITA. I've updated my repo and built all the images and loaded them into my own docker registry (orcas.docker-public.orcas.net). I've verfied I can docker pull them anonymously, but my HA won't take the update:
22-05-17 00:24:58 WARNING (SyncWorker_7) [supervisor.store.data] Can't read /data/addons/git/3be6726f/zigbee2mqtt-edge/config.json: does not match regular expression ^([a-zA-Z\-\.:\d{}]+/)*?([\-\w{}]+)/([\-\w{}]+)$ for dictionary value @ data['image']. Got 'orcas.docker-public.orcas.net/zigbee2mqtt-edge-{arch}'

I also tried your other suggestion of loading it into my addons and merging the folders, but that fails when I try to add the addon with:
22-05-17 00:17:40 INFO (MainThread) [supervisor.addons] Creating Home Assistant add-on data folder /data/addons/data/local_zigbee2mqtt_edge
22-05-17 00:17:40 ERROR (SyncWorker_5) [supervisor.docker.addon] Invalid build environment, can't build this add-on!

@thardie So I'm not sure why exactly its coded this way but this is the regex for image from that error:
^([a-zA-Z\-\.:\d{}]+/)*?([\-\w{}]+)/([\-\w{}]+)$

orcas.docker-public.orcas.net/zigbee2mqtt-edge-{arch} doesn't pass that regex because it's only got one resource path part. For example if it was this orcas.docker-public.orcas.net/a/zigbee2mqtt-edge-{arch} then it would work. It just really wants a second path part.
I can't really explain why here, I was kind of cringing why I typed it to be honest. I guess I've got to look into that. For now, I can only tell you what the regex does lol.

I also tried your other suggestion of loading it into my addons and merging the folders, but that fails when I try to add the addon with:

I'm not sure how to explain this one. I tried it just now starting from a blank /addons folder on a dev system and had no issues. First I did this:
> git clone --depth 1 -b base-image-s6-v3-update https://github.com/mdegat01/hassio-zigbee2mqtt
> mv hassio-zigbee2mqtt/common/* hassio-zigbee2mqtt/zigbee2mqtt-edge

Then I removed image from config.json in the zigbee2mqtt-edge folder. Then I went to the addon store, clicked the 3 dots in the upper right and did "Check for updates" to make my new local addon appear. I installed the edge version (it built fine) and then ran it, got this in the log:
s6-rc: info: service s6rc-oneshot-runner: starting
s6-rc: info: service s6rc-oneshot-runner successfully started
s6-rc: info: service fix-attrs: starting
s6-rc: info: service fix-attrs successfully started
s6-rc: info: service legacy-cont-init: starting
cont-init: info: running /etc/cont-init.d/socat.sh
[16:44:24] INFO: Socat not enabled, marking service as down
cont-init: info: /etc/cont-init.d/socat.sh exited 0
cont-init: info: running /etc/cont-init.d/zigbee2mqtt.sh
cont-init: info: /etc/cont-init.d/zigbee2mqtt.sh exited 0
s6-rc: info: service legacy-cont-init successfully started
s6-rc: info: service legacy-services: starting
services-up: info: copying legacy longrun socat (no readiness notification)
services-up: info: copying legacy longrun zigbee2mqtt (no readiness notification)
[16:44:26] INFO: Handing over control to Zigbee2mqtt Core ...
><EMAIL_ADDRESS>start
> node index.js
Zigbee2MQTT:info  2022-05-17 16:44:29: Logging to console and directory: '/config/zigbee2mqtt/log/2022-05-17.16-44-28' filename: log.txt
Zigbee2MQTT:info  2022-05-17 16:44:29: Starting Zigbee2MQTT version 1.25.1-dev (commit #5ae8347)
Zigbee2MQTT:info  2022-05-17 16:44:29: Starting zigbee-herdsman (0.14.31)
Zigbee2MQTT:error 2022-05-17 16:44:29: Error while starting zigbee-herdsman
Zigbee2MQTT:error 2022-05-17 16:44:29: Failed to start zigbee
Zigbee2MQTT:error 2022-05-17 16:44:29: Check https://www.zigbee2mqtt.io/guide/installation/20_zigbee2mqtt-fails-to-start.html for possible solutions
Zigbee2MQTT:error 2022-05-17 16:44:29: Exiting...
Zigbee2MQTT:error 2022-05-17 16:44:30: Error: Error while opening serialport 'Error: Error: No such file or directory, cannot open /dev/ttyACM0'
    at SerialPort.<anonymous> (/app/node_modules/zigbee-herdsman/src/adapter/z-stack/znp/znp.ts:146:28)
    at SerialPort._error (/app/node_modules/@serialport/stream/lib/index.js:198:14)
    at /app/node_modules/@serialport/stream/lib/index.js:242:12

I mean to be clear the addon isn't working here because I don't actually have a zigbee coordinator plugged into my dev system right now and didn't configure the addon at all. But it is running all the start-up scripts successfully so it would work with a real config and a coordinator.

Thanks for the response, I really appreciate it. I couldn't understand why the regex wasn't matching, since I was barking up this tree:
Python 3.8.5 (default, Jul 28 2020, 12:59:40)
[GCC 9.3.0] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import re
>>> res = '^([a-zA-Z\-\.:\d{}]+/)*?([\-\w{}]+)/([\-\w{}]+)$'
>>> re.match(res, "foo/bar")
<re.Match object; span=(0, 7), match='foo/bar'>
>>> re.match(res, "foo.a/bar")
>>>

I was convinced it was in the first part (periods in the domain name) and couldn't understand why. Thanks for helping with that.
As for the addons folder, I'll work on that - I'll just assume something's gorked in my HAOS that can't build locally for some reason not related to this addon.
I'll re-organize my repo so there's an additional directory. Thanks again.

I've managed to get it running. All seems good (Zigbee is working), but the web frontend doesn't work. I see this error in the logs:
(node:166) UnhandledPromiseRejectionWarning: TypeError: name.orig.at is not a function
    at check (/app/node_modules/connect-gzip-static/lib/gzip-static.js:94:19)
    at Frontend.gzipStatic (/app/node_modules/connect-gzip-static/lib/gzip-static.js:54:16)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
(node:166) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 14)

Should I open a new issue?

@thardie I think that might just be a frontend bug in Z2M. I found this, looks the same. It is still the edge version so that can happen.

Problem localised, buggy dependency got downgraded
https://github.com/pirxpilot/connect-gzip-static/issues/16

Having the same issue, using edge c6840a9a435f9c2da1fd2fdc611249fb58b10d92
Description of problem:
Addon doesn't start, trying to open the UI gives 502 bad gateway
Tried restoring a backup but the error stays
Zigbee2mqtt logs show:
s6-overlay-suexec: fatal: can only run as pid 1

Zigbee2mqtt add-on version (if edge, please report commit hash):
edge c6840a9a435f9c2da1fd2fdc611249fb58b10d92
Your entire configuration from the frontend (with sensitive fields redacted):
data_path: /share/zigbee2mqtt
socat:
  enabled: false
  master: pty,raw,echo=0,link=/tmp/ttyZ2M,mode=777
  slave: tcp-listen:8485,keepalive,nodelay,reuseaddr,keepidle=1,keepintvl=1,keepcnt=5
  options: '-d -d'
  log: false
mqtt:
  server: mqtt://<IP_ADDRESS>:1883
  user: ****
  password: ****
serial:
  port: >-
    /dev/serial/by-id/usb-dresden_elektronik_ingenieurtechnik_GmbH_ConBee_II_DE2403707-if00
  adapter: deconz

Running platform (details from Suypervisor > System)
core-2022.5.4
Home Assistant OS 8.0
supervisor-2022.05.2

Your logs from Home Assistant Supervisor
22-05-18 15:39:11 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/home-assistant/addons repository
22-05-18 15:39:11 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/snowzach/hassio-addons repository
22-05-18 15:39:11 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/hassio-addons/repository repository
22-05-18 15:39:11 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/zigbee2mqtt/hassio-zigbee2mqtt repository
22-05-18 15:39:11 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/net-daemon/homeassistant-addon repository
22-05-18 15:39:11 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/thomasmauerer/hassio-addons repository
22-05-18 15:39:11 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/CoolKit-Technologies/ha-addon repository
22-05-18 15:39:11 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/alexbelgium/hassio-addons/ repository
22-05-18 15:39:11 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/Expaso/hassos-addons repository
22-05-18 15:39:11 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/sabeechen/hassio-google-drive-backup repository
22-05-18 15:39:11 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/esphome/home-assistant-addon repository
22-05-18 15:39:11 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/MaxWinterstein/homeassistant-addons repository
22-05-18 15:39:11 INFO (MainThread) [supervisor.store.git] Update add-on https://github.com/sanderdw/hassio-addons repository
22-05-18 15:39:14 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with 45df7312_zigbee2mqtt_edge!
22-05-18 15:39:15 INFO (MainThread) [supervisor.resolution.check] Starting system checks with state CoreState.RUNNING
22-05-18 15:39:15 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.DNS_SERVER_IPV6_ERROR/ContextType.DNS_SERVER
22-05-18 15:39:15 INFO (SyncWorker_5) [supervisor.docker.interface] Cleaning addon_45df7312_zigbee2mqtt_edge application
22-05-18 15:39:15 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.TRUST/ContextType.SUPERVISOR
22-05-18 15:39:15 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.DNS_SERVER_FAILED/ContextType.DNS_SERVER
22-05-18 15:39:15 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.PWNED/ContextType.ADDON
22-05-18 15:39:15 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.SECURITY/ContextType.CORE
22-05-18 15:39:15 INFO (MainThread) [supervisor.resolution.checks.base] Run check for IssueType.FREE_SPACE/ContextType.SYSTEM
22-05-18 15:39:15 INFO (MainThread) [supervisor.resolution.check] System checks complete
22-05-18 15:39:15 INFO (MainThread) [supervisor.resolution.evaluate] Starting system evaluation with state CoreState.RUNNING
22-05-18 15:39:16 INFO (MainThread) [supervisor.resolution.evaluate] System evaluation complete
22-05-18 15:39:16 INFO (MainThread) [supervisor.resolution.fixup] Starting system autofix at state CoreState.RUNNING
22-05-18 15:39:16 INFO (MainThread) [supervisor.resolution.fixup] System autofix complete
22-05-18 15:39:17 INFO (SyncWorker_5) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-edge-aarch64 with version edge
22-05-18 15:39:19 INFO (MainThread) [supervisor.store] Loading add-ons from store: 158 all - 0 new - 0 remove
22-05-18 15:39:19 INFO (MainThread) [supervisor.store] Loading add-ons from store: 158 all - 0 new - 0 remove
22-05-18 15:39:26 ERROR (SyncWorker_2) [supervisor.docker.interface] Container addon_45df7312_zigbee2mqtt_edge is not running
22-05-18 15:39:47 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with 45df7312_zigbee2mqtt_edge!
22-05-18 15:39:48 INFO (SyncWorker_7) [supervisor.docker.interface] Cleaning addon_45df7312_zigbee2mqtt_edge application
22-05-18 15:39:49 ERROR (MainThread) [supervisor.api.ingress] Ingress error: Cannot connect to host <IP_ADDRESS>:8099 ssl:default [Connect call failed ('<IP_ADDRESS>', 8099)]
22-05-18 15:39:50 INFO (SyncWorker_7) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-edge-aarch64 with version edge
22-05-18 15:40:04 ERROR (SyncWorker_3) [supervisor.docker.interface] Container addon_45df7312_zigbee2mqtt_edge is not running
22-05-18 15:40:20 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with 45df7312_zigbee2mqtt_edge!
22-05-18 15:40:20 INFO (SyncWorker_2) [supervisor.docker.interface] Cleaning addon_45df7312_zigbee2mqtt_edge application
22-05-18 15:40:22 INFO (SyncWorker_2) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-edge-aarch64 with version edge
22-05-18 15:40:31 ERROR (SyncWorker_5) [supervisor.docker.interface] Container addon_45df7312_zigbee2mqtt_edge is not running
22-05-18 15:40:52 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with 1e14b3fb_tgtg-ha-mqtt-bridge!
22-05-18 15:40:52 INFO (SyncWorker_2) [supervisor.docker.interface] Cleaning addon_1e14b3fb_tgtg-ha-mqtt-bridge application
22-05-18 15:40:52 ERROR (SyncWorker_3) [supervisor.docker.interface] Container addon_45df7312_zigbee2mqtt_edge is not running
22-05-18 15:40:53 INFO (SyncWorker_2) [supervisor.docker.addon] Starting Docker add-on maxwinterstein/homeassistant-addon-toogoodtogo-ha-mqtt-bridge-aarch64 with version 2.0.0
22-05-18 15:40:53 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with 45df7312_zigbee2mqtt_edge!
22-05-18 15:40:53 INFO (SyncWorker_6) [supervisor.docker.interface] Cleaning addon_45df7312_zigbee2mqtt_edge application
22-05-18 15:40:55 INFO (SyncWorker_6) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-edge-aarch64 with version edge
22-05-18 15:41:00 INFO (MainThread) [supervisor.auth] Auth request from 'core_mosquitto' for 'TestUser'
22-05-18 15:41:00 INFO (MainThread) [supervisor.auth] Home Assistant not running, checking cache
22-05-18 15:41:25 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with 45df7312_zigbee2mqtt_edge!
22-05-18 15:41:26 INFO (SyncWorker_1) [supervisor.docker.interface] Cleaning addon_45df7312_zigbee2mqtt_edge application
22-05-18 15:41:27 INFO (SyncWorker_1) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-edge-aarch64 with version edge
22-05-18 15:41:58 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with 45df7312_zigbee2mqtt_edge!
22-05-18 15:41:58 INFO (SyncWorker_0) [supervisor.docker.interface] Cleaning addon_45df7312_zigbee2mqtt_edge application
22-05-18 15:42:00 INFO (SyncWorker_0) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-edge-aarch64 with version edge
22-05-18 15:42:30 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with 45df7312_zigbee2mqtt_edge!
22-05-18 15:42:30 INFO (SyncWorker_3) [supervisor.docker.interface] Cleaning addon_45df7312_zigbee2mqtt_edge application
22-05-18 15:42:32 INFO (SyncWorker_3) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-edge-aarch64 with version edge
22-05-18 15:43:02 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with 45df7312_zigbee2mqtt_edge!
22-05-18 15:43:02 INFO (SyncWorker_7) [supervisor.docker.interface] Cleaning addon_45df7312_zigbee2mqtt_edge application
22-05-18 15:43:04 INFO (SyncWorker_7) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-edge-aarch64 with version edge
22-05-18 15:43:06 ERROR (SyncWorker_3) [supervisor.docker.interface] Container addon_45df7312_zigbee2mqtt_edge is not running
22-05-18 15:43:11 ERROR (SyncWorker_5) [supervisor.docker.interface] Container addon_45df7312_zigbee2mqtt_edge is not running
22-05-18 15:43:38 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with 45df7312_zigbee2mqtt_edge!
22-05-18 15:43:39 INFO (SyncWorker_3) [supervisor.docker.interface] Cleaning addon_45df7312_zigbee2mqtt_edge application
22-05-18 15:43:44 INFO (SyncWorker_3) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-edge-aarch64 with version edge
22-05-18 15:43:57 WARNING (SyncWorker_2) [supervisor.docker.interface] Can't grep logs from zigbee2mqtt/zigbee2mqtt-edge-aarch64: 404 Client Error for http+docker://localhost/v1.41/containers/ccd804f02ab52d82ffc5fc71d5b0be3861f16891b9c04ae2a6a58cb775d6f2ae/json: Not Found ("No such container: ccd804f02ab52d82ffc5fc71d5b0be3861f16891b9c04ae2a6a58cb775d6f2ae")
22-05-18 15:44:14 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with 45df7312_zigbee2mqtt_edge!
22-05-18 15:44:14 INFO (SyncWorker_5) [supervisor.docker.interface] Cleaning addon_45df7312_zigbee2mqtt_edge application
22-05-18 15:44:15 INFO (SyncWorker_5) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-edge-aarch64 with version edge
22-05-18 15:44:35 ERROR (SyncWorker_0) [supervisor.docker.interface] Container addon_45df7312_zigbee2mqtt_edge is not running
22-05-18 15:44:46 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with 45df7312_zigbee2mqtt_edge!
22-05-18 15:44:46 INFO (SyncWorker_0) [supervisor.docker.interface] Cleaning addon_45df7312_zigbee2mqtt_edge application
22-05-18 15:44:47 INFO (SyncWorker_0) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-edge-aarch64 with version edge
22-05-18 15:45:18 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with 45df7312_zigbee2mqtt_edge!
22-05-18 15:45:18 INFO (SyncWorker_5) [supervisor.docker.interface] Cleaning addon_45df7312_zigbee2mqtt_edge application
22-05-18 15:45:19 INFO (SyncWorker_5) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-edge-aarch64 with version edge
22-05-18 15:45:48 INFO (MainThread) [supervisor.updater] Fetching update data from https://version.home-assistant.io/stable.json
22-05-18 15:45:49 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with 45df7312_zigbee2mqtt_edge!
22-05-18 15:45:49 INFO (SyncWorker_7) [supervisor.docker.interface] Cleaning addon_45df7312_zigbee2mqtt_edge application
22-05-18 15:45:51 INFO (SyncWorker_7) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-edge-aarch64 with version edge
22-05-18 15:46:21 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with 45df7312_zigbee2mqtt_edge!
22-05-18 15:46:22 INFO (SyncWorker_5) [supervisor.docker.interface] Cleaning addon_45df7312_zigbee2mqtt_edge application
22-05-18 15:46:23 INFO (SyncWorker_5) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-edge-aarch64 with version edge
22-05-18 15:46:53 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with 45df7312_zigbee2mqtt_edge!
22-05-18 15:46:53 INFO (SyncWorker_4) [supervisor.docker.interface] Cleaning addon_45df7312_zigbee2mqtt_edge application
22-05-18 15:46:55 INFO (SyncWorker_4) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-edge-aarch64 with version edge
22-05-18 15:47:13 INFO (MainThread) [supervisor.homeassistant.core] Detect a running Home Assistant instance
22-05-18 15:47:13 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
22-05-18 15:47:13 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_nodered
22-05-18 15:47:13 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request initialize
22-05-18 15:47:13 INFO (MainThread) [supervisor.api.proxy] WebSocket access from a0d7b954_appdaemon
22-05-18 15:47:25 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with 45df7312_zigbee2mqtt_edge!
22-05-18 15:47:25 INFO (SyncWorker_5) [supervisor.docker.interface] Cleaning addon_45df7312_zigbee2mqtt_edge application
22-05-18 15:47:27 INFO (SyncWorker_5) [supervisor.docker.addon] Starting Docker add-on zigbee2mqtt/zigbee2mqtt-edge-aarch64 with version edge
22-05-18 15:47:32 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
22-05-18 15:47:32 INFO (MainThread) [supervisor.api.proxy] Home Assistant WebSocket API request running
22-05-18 15:47:58 WARNING (MainThread) [supervisor.misc.tasks] Watchdog found a problem with 45df7312_zigbee2mqtt_edge!
22-05-18 15:47:59 INFO (SyncWorker_7) [supervisor.docker.interface] Cleaning addon_45df7312_zigbee2mqtt_edge applica

Same here

Same here

I have the same problem too

Same here, cannot run the Edge version so I've switched to the main branch, but get some devices that aren't recognized.
Waiting for the fix, thank for your awesome work guys.

Same error for me as well, I updated to hass OS version 8 and then this error after reboot. Didn't update my hass version yet, still on 2022.4.2.

same thing .....
any solution please ?

I finally choosen to run Z2M in a LXC container, in my Proxmox : no imcompability, and I can now use newest devices that was not supported nattively.
Good luck all

Hyperion.NG
s6-overlay-suexec: fatal: can only run as pid 1

Same problem...

Likely enough ppl with same problem by now, but... here, too ^^ Went back to stable for now.

This is why I get off this add-on : Edge is not updated frequently, and Stable is outdated - out of the box - for some of my devices (Aqara WRS-R02 and Nous A1Z).

Having the same issue. has anyone managed to fix this, if so could they provide some simple steps, couldn't follow previous comments or blog post.
Any help greatly appreciated.

Having the same issue. has anyone managed to fix this, if so could they provide some simple steps, couldn't follow previous comments or blog post.
Any help greatly appreciated.

The fix is not simple, but if you want to use the edge version I fixed, point your HA repo to https://github.com/thardie/hassio-zigbee2mqtt and install the edge version. I will not be keeping this up to date, so as soon as this is fixed upstream, you will need to switch back.

Likely enough ppl with same problem by now, but... here, too ^^ Went back to stable for now.

This is why I get off this add-on : Edge is not updated frequently, and Stable is outdated - out of the box - for some of my devices (Aqara WRS-R02 and Nous A1Z).

Edge needs to be updated manually and is always recent. This is explained in the Addon information btw. Stable is... Stable

Edge needs to be updated manually and is always recent. This is explained in the Addon information btw. Stable is... Stable

For sure.
But as you saw, Edge add-on was updated 10 days after this issue (PR was merged 19h ago).
Stable version is 1.18.x, which is dated from 05/2021 : seems to be a little bit outdated to me.
But, be sure I don't denigrate the amazing work of Koenkk and others : without, no Z2M.

It doesn't work for me, same error. Am I alone in this case?

Works fine for me.

It doesn't work for me, same error. Am I alone in this case?

Works fine for me.

Did you do anything special?
I've switched back to stable for now and when I installed edge again it still failed with the same error.

Same issue with latest zigbee2mqtt edge digest 2b2120afbd9e

FYI edge should work now. There was an issue with the config.json since my PR targetted the dev branch but master wasn't changed. Koenkk fixed that with #344 . I just tried installing and running edge and it worked without issue after that.

You probably need to go to the go to the addon store and click "check for updates". Then follow the normal updating process for the edge addon (reinstalling it I believe).

You probably need to go to the go to the addon store and click "check for updates" in the menu in the top right. Then follow the normal updating process for the edge addon (reinstalling it I believe).

Yes I delete the zigbee2mqtt folder on my NUC and I reinstalled it. It works but my Danfoss devices are not supported...I don't understand why because it works perfectly before...

You probably need to go to the go to the addon store and click "check for updates" in the menu in the top right. Then follow the normal updating process for the edge addon (reinstalling it I believe).

Yes I delete the zigbee2mqtt folder on my NUC and I reinstalled it. It works but my Danfoss devices are not supported...I don't understand why because it works perfectly before...

Are you using my version? I'm not keeping it up to date with edge - I built it just after this problem started. When was support added to edge of Z2M for your Danfoss devices?

I just checked and getting from this official repo and installing the edge version now work (above commit fixed it for me)

no luck here.  still fatal error

Are you using my version? I'm not keeping it up to date with edge - I built it just after this problem started. When was support added to edge of Z2M for your Danfoss devices?

I installed the version fixed on the official repo. My devices are recognized before...but not now https://www.zigbee2mqtt.io/devices/014G2461.html

Are you installing edge from the official repo?

I had to uninstall, remove the repository, reboot the host the add repo and install.  Now it works.

Just tested, it's working (please follow the instructions when updating)

Thanks, last Z2M edge commit is working!

I know this topic is closed, but I am still having the exact same error. I have uninstalled both the normal AND the edge add-ons, removed the repository from HA (after a reboot), added the repo and installed z2m again. The normal version is still working. The edge version still gives me the above error?

I have the same error  for latest version of edge - s6-overlay-suexec: fatal: can only run as pid 1


When I have disabled title it still shows in some windows

Describe the bug
First, thank you for the amazing plugin I really love it.
I have in my config ui.title = false but it still shows in:

diagnostic_jump_next, diagnostic_jump_prev
show_diagnostic in all windows

Steps to reproduce
Call
:Lspsaga diagnostic_jump_next
:Lspsaga diagnostic_jump_prev
:Lspsaga show_diagnostic
Expected behavior
Don't show the title
Neovim version (nvim -v)
NVIM v0.9.0-dev-763+ge86d2734a
lspsaga commit
ac13404
Terminal name/version
kitty

The Msg and Fix aren't titles? It would be nice to hide them too.

it's hardcoded.  about ui  I will do some change in next version.


Rule contradicts with story although slots infulencing conversations should disambiguate them

Rasa version: 2.1.3
Rasa SDK version: 2.1.2
Python version: 3.7.9
Operating system: Ubuntu
Issue:
I have a rule with a condition that a text slot (which influence conversation) is set. I have a story which has this slot set to null very early in the conversation. The validation fails stating that the story and rule contradicts each other but this slot makes them different.
rule.yml
version: "2.0"
rules:
- rule: respond to apartment FAQs
  conversation_start: false
  condition:
    - slot_was_set:
      - slug: ABCDE
  steps:
  - intent: faq_apartment
  - action: action_faq_apartment

story.yml
version: "2.0"
stories:
- story: Story from Conversation ID 633c1ae1e2694de1ac4ad254346fd2ce
  steps:
  ...
  - slot_was_set:
    - slug: null
  ... many intents, actions and slot_was_set events, none of which setting slug...
  - intent: faq_apartment
    entities:
    - time: '2021-01-03T00:00:00.000-05:00'
    - number: 1
    - mention: the third one
  - action: action_set_apt_selected
  - slot_was_set:
    - slug: ABCDE

Error (including full traceback):
InvalidRule:
Contradicting rules or stories found 🚨

- the prediction of the action 'action_set_apt_selected' in story 'Story from Conversation ID 633c1ae1e2694de1ac4ad254346fd2ce' is contradicting with rule(s) 'respond to apartment FAQs' which predicted action 'action_faq_apartment'.
Please update your stories and rules so that they don't contradict each other.
You can find more information about the usage of rules at https://rasa.com/docs/rasa/rules.

Command or request that led to error:
rasa train core

Content of configuration file (config.yml) (if relevant):
policies:
  - name: TEDPolicy
    max_history: 7
    epochs: 200
  - name: RulePolicy
    check_for_contradictions: true

Content of domain file (domain.yml) (if relevant):
slots:
  slug:
    type: text
    influence_conversation: true

Thanks for raising this issue, @joejuzl will get back to you about it soon✨
Please also check out the docs and the forum in case your issue was raised there too 🤗

@Ghostvv is it expected behaviour that we flag a rule and story as contradicting even if they have different slot conditions?

It feels like a bug. Strange, I thought I tested for this case

@nbeuchat Thanks for flagging the issue.
I recreated your example but could not reproduce the error. I’m able to invoke the contradiction error when there is indeed a contradiction, but not when there isn’t.
Is this still a problem that you’re facing? Could you please upgrade to the latest version of Rasa and try again? If the issue persists, then please provide me with enough details to reproduce the error. Perhaps you can supply the complete rather than partial story, and anything else that might be relevant (e.g., custom action or form).
Thanks!

Hi @aeshky! Thanks for your response. I have since then quite significantly changed my stories and rules and updated to a latest version of Rasa. I haven't faced this issue since though

You can probably close for now. If I get this issue again I'll ask to reopen

Thanks for your quick response @nbeuchat.
I'm happy to hear that you haven't faced this issue since. I'll go ahead and close it, and please reopen if it comes up again.


Add page for tools

As a start, only the browser extension is listed, but this can serve as a place for more tools.
I only added the Firefox link, we can figure out later how to add the Chrome one.
No link to this page yet, as I couldn't find a good place to link from.
Fixes #209.

Would we want to mention tool related stuff for editing like the schema and AutoIdentifierInput?

Would we want to mention tool related stuff for editing like the schema and AutoIdentifierInput?

It could make sense as a section, yes. But let's add them later.


DDL: Add support for placement feature id(/*T![placement]... */).

What problem does this PR solve?
related to https://github.com/pingcap/tidb/pull/27792
particial close: https://github.com/pingcap/tidb/issues/18030

DDL syntax support parse /*T[placement]*/
binlog downstream DDL compatibility support, which depends on the first one.

What is changed and how it works?
Check List
Tests

Unit test
Integration test

Well done, should TiDB side test need modification?

Well done, should TiDB-side tests need modification?

Some test cases added, it seems work well.
https://github.com/pingcap/tidb/pull/28055

/merge


Change the default grid size to 4x4

A plurality (9/20) of the top puzzles are 4x4, despite 5x5 being the default.  We should make 4x4 the default instead, since that size clearly tends to produce better puzzles.

I haven't tested this at all btw; let me know if you want me to or if it's easier for you to just do it anyway.

I did a quick sanity test and it seems to work.


Update Go to 1.20.6,1.19.11

go1.20.6 (released 2023-07-11) includes a security fix to the net/http package, as well as bug fixes to the compiler, cgo, the cover tool, the go command, the runtime, and the crypto/ecdsa, go/build, go/printer, net/mail, and text/template packages. See the Go 1.20.6 milestone on our issue tracker for details.
https://github.com/golang/go/issues?q=milestone%3AGo1.20.6+label%3ACherryPickApproved
Full diff: https://github.com/golang/go/compare/go1.20.5...go1.20.6
These minor releases include 1 security fixes following the security policy:

net/http: insufficient sanitization of Host header
The HTTP/1 client did not fully validate the contents of the Host header. A maliciously crafted Host header could inject      additional headers or entire requests. The HTTP/1 client now refuses to send requests containing an invalid Request.Host or      Request.URL.Host value.

Thanks to Bartek Nowotarski for reporting this issue.
Includes security fixes for CVE-2023-29406 and Go issue https://go.dev/issue/60374

@thaJeztah For once I checked my personal email and caught it same day 🤣 I always see the announcement a day after

I missed the pre-announcement for this one, but maybe they didn't send one? And I was away from my keyboard so 😂


Blazor Server detailed errors experience

Fixes  #15624
Only Blazor Server, correct? Even if so, I wonder if we need a sister section for Blazor WebAssembly that merely states that the dev should look at the dev tools console. We do say in the live topic ...

During development, Blazor usually sends the full details of exceptions to the browser's console to aid in debugging.

... down in the Log errors with a persistent provider section.
I'm thinking 🤔 that we should add a short section on this PR at the top near this new section calling that guidance out for Blazor WebAssembly to balance the coverage up there. We can leave that existing line in place ... it's true for both hosting models. Should I do it?

@scottaddie ... thanks for taking a look. Recommend tho that we hold the docs team review until I chat with engineering on the coverage.
Major content changes may occur on any given PR during this stage of high Blazor churn. It would be costly 💰 for us to review a draft and then re-review after major changes. I suggest we have engineering look at my 🙈 RexHacks:tm: 🙈 first ... say 'ok' or 'do this' ... react to feedback and then have the docs cats help fix up the rough spots.


Enhancement: support for vmware workstation

I have other VMs that only work with vmware (and not virtualbox) that I would like to interact with Attack Range.

Closing this issue as Attack Range Local has been deprecated (and functionality migrated into Attack Range).  Please use https://github.com/splunk/attack_range for all future simulation needs.  If this continues to be an issue, please open a ticket in that repo.


third party submodules

would it make sense to add third party libraries as submodules?

None of the third party "libraries" have actually been implemented as modules, and so the code is not importable. The directories included in this repo contain code very close to the original implementation. I don't intend to maintain forks of these repos as these are unlikely to see development.


Save context menu selection on json file.

My menu was built by reading a json file; If I make a change using the contextmenu plugin, can I save it in the same json file? Ex: If I add a node in a treeview I wont to save it on json file.
Thanks
Albe

Yes, but this is not something jstree can do for you - that is server-side logic. You have many options - for example listening for the events you are interested in, in the handlers calling get_json() and sending the result to the server and saving it. Or have a dedicated save button, etc, but this is all out of the jstree-code scope. All the events and methods you need are documented on the API page on jstree.com


First dev version of ARIMA generator

Hi Nicola, here is a first drop of the ARIMA generator with a demo notebook. For now both code and demo notebook are in the demo folder as I'd like still to integrate all the generation functions used in the other demo in the generator module before submitting it for the main library.
Still I'd like to get feedback before going too far.

Sorry I found a bug in the I part of the ARIMA generator, please wait before integrating to dev

Don't worry, I wait your ok to integrate. 😉

@mallibus can I merge?

Go!


[Feature][WIP] Show Operation with Tabs

WHY
BEFORE - What was wrong? What was happening before this PR?
Nothing was wrong... but the Show Operation can be improved by adding tabs to it!
AFTER - What is happening after this PR?
Columns are grouped by Tabs in Show Operation.
HOW
How did you achieve that, in technical terms?
Not too many changes, I think.
Is it a breaking change?
Nope.
How can we test the before & after?
Test with and without this branch, add 'tab' => 'First tab' values to columns, and boom!
Horizontal tabs:

Vertical tabs

This is starting to look so good! Awesome, I'll let you guys work at it. My only mention @maurohmartinez is in terms of design polish - I don't like the padding that goes from the table to the actual card:

I think without that padding (and after solving the double-borders that would inevitably come if that padding disappears) it will look KICKASS.

My question is: can we abstract this tabs logic to a view/partials reused by create/update/show ?

Yes, I investigated a bit, and it looks like the structure for those blades are very similar.
Am I right thinking that you were considering this for a different task? If yes, I can create an issue so that we don't forget about it.
Mauro

My question is: can we abstract this tabs logic to a view/partials reused by create/update/show ?

Yes @pxpm, I investigated a bit, and it looks like the structure for those blades are very similar. Am I right thinking that you were considering this for a different task? If yes, I can create an issue so that we don't forget about it.
Mauro

I don't think this should be done in a different task. We are launching this feature and cleaning the house as we go (as long as the cleaning does not involve a full time team, if you get what I mean).
I also saw some patterns, that's why I decided to ask, but I think this should be done in this feature.
Changing blades later, after people could potentially publish them will be a BC because we will be removing files.
What you think @tabacitu ?

I don't feel strongly either way. Moving the actual tabs to a separate file might clean things up, I agree. Not sure it's worth it though, considering the move to v6 themes and everything. You guys decide.

I don't feel strongly either way. Moving the actual tabs to a separate file might clean things up, I agree. Not sure it's worth it though, considering the move to v6 themes and everything. You guys decide.

does the "bootstrap tab structure" change from theme to theme, or theme is just style concerned ?

Mauro knows more than me on that front.

I loved the discussion between you two @tabacitu & @pxpm! I learned a couple of things, became a bit more familiar with Backpack structure, and even got a glance of what is coming in the future. Great to be part of this!
I made the required changes. Let me know if I got what you guys decided right.
If yes, then this is ready!
Cheers!

Hmmm I wasn't able to get this working, to test. Any idea why?
https://www.loom.com/share/0f61ebf274204fb890b786ce24ca07f1

Hmmm I wasn't able to get this working, to test it. Any idea why?
https://www.loom.com/share/0f61ebf274204fb890b786ce24ca07f1

My guess is that you need to enable tabs for the new value in config show.
src/config/backpack/operations/show.php
// Enable to group columns in tabs
    'tabsEnabled' => false, // <------ this one

By default, if that value is not enabled, we ignore tabs.
Is that the expected behaviour @tabacitu? Or something needs to be adjusted?

Hmmm I wasn't able to get this working, to test it. Any idea why?
https://www.loom.com/share/0f61ebf274204fb890b786ce24ca07f1

My guess is that you need to enable tabs for the new value in config show.
src/config/backpack/operations/show.php
// Enable to group columns in tabs
    'tabsEnabled' => false, // <------ this one

By default, if that value is not enabled, we ignore tabs. Is that the expected behaviour @tabacitu? Or something needs to be adjusted?

Hey @maurohmartinez you are right. I think we need to keep it that way. Otherwise someone that uses the field definition with tab attribute to setup the columns in ListOperation and then use the list operation columns in show operation, would have now the tabs displayed, while before they were ignored.
$columnsAndFields = [
    [
        'name' => 'name',
        'tab' => 'tab1'
    ]
];

// setupCreateOperation
$this->crud->addFields($columnsAndFields); // will use the tab

// setupListOperation
$this->crud->addColumns($columnsAndFields); // will disregard

// setupShowOperation
$this->crud->setupListOperation(); // will disregard

Unless @tabacitu thinks this is not that relevant and decide to make tabsEnabled => true by default, that I think we should do, but in v6.

OK let’s disable it by default in this version, and will make it enabled in v6.

Hey Backpack team,
Just done composer update to apply this on our Biiiig running project & It's really super duper awesome..
Was waiting for this feature since so long and finally got that.

This is really cool feature. Request you to please mention in Backpack doc to change config in config/backpack/show.php, set tabsEnabled to true.
Keep growing team.
Cheers..

Thanks @munjaldevelopment it's already on the docs: https://backpackforlaravel.com/docs/5.x/crud-operation-show#tabs-display-columns-in-tabs


Support user-owned, cross revision MeshConfig fragments

MeshConfig is an alpha API controlling the config of experimental and alpha features, as well as a set of internal
settings that are not editable by users ( like discoveryAddress ).
Current installer has the MeshConfig tied to the revision - this prevents the install of one revision from breaking an
existing revision. Helm also doesn't allow 2 different installs to 'own' the same file, and while kubectl allows
that, if user runs production and canary revisions and they both make changes to a shared configmap  the
result will be unpredictable.
In env WG we discussed merging the per-revision, installer-owned configmap with a set of user-owned fragments.
The code is relatively simple and safe - all MeshConfig loading is in one place, and we already have merging with
the hardcoded default.
The requirements are:

use a different prefix, to avoid conflicts/confusion with istio-REVISION config maps. For example 'user-istio-logging', or 'istiod-user-logging'.
installer should NEVER create such config maps
like all resources loaded by Istiod, it must respect the istio.io/rev annotation, so users can still 'tie' the fragment to a revision for safe canary of any config change
an additional validator should be added, restricting the use of 'internal' fields.

It would also be good if default ProxyConfig changes are done in separate config maps.
The roadmap includes 'cleaning' mesh config and we have discussed moving it to CRD or graduating various parts -
this remains a goal, but we have an immediate problem we can solve for the existing alpha with minimal impact
and disruption.
Describe the feature request
Describe alternatives you've considered
[ ] Docs
[ ] Installation
[ ] Networking
[ ] Performance and Scalability
[ ] Extensions and Telemetry
[ ] Security
[ ] Test and Release
[ ] User Experience
[ ] Developer Infrastructure
Additional context

For reference, https://github.com/istio/istio/issues/31387 is proposing adding support for editing the per-revision mesh config, but as explained in my comment any in-place upgrade or 'apply' would override the edits, and it doesn't address the problem that the config tied to one revision.

I am generally in favor, but one concern about many "fragments". What is the merging order? Are we going to end up in confusing situations where a user needs to look at 8 configmaps to find the one that they put accessLogFile in? Will we have users setting accessLogFile: foo and it not apply since another configmap already set it to bar?
Do we need many fragments, or just allow one user setting?
If the user setting is to just allow user overrides in external control plane, do we even need multiple configmap reads, or just configmap overriding a mounted file (with restrictions)?

This is probably a dependency/requirement for the 'floating labels' proposal to have in-place like upgrade using revisions.
If user defines a 'canary' and 'prod', and uses 1.9.1 as prod and 1.9.2 as canary, we would have several configmaps:

istio-1.9.1 - actually used by the 1.9.1 rev, associated with prod
istio-1.9.2 - used by the 1.9.2 rev, associated with canary

User should be able to edit 'istio-prod' and 'istio-canary'
Maybe we can restrict it this way, with the 'floating' name owned by user.

I.e. - agree with John on many fragments. We should start with only one or 2, i.e.

user-istio -> shared by all revisions ( 1.10+)
user-istio-prod -> shared by the revisions with floating label 'prod'.

UX wants a istioctl describe mesh-type command that will tell a user the settings of the mesh.
For example, the Zipkin address and sampling rate that new pods will receive on startup.
Will it be possible for a CLI tool to get the values -- both defaults and the cluster overrides -- for display purposes?

There is already a debug endpoint to get the mesh config. We can use that,
if Iris work lands
On Fri, Mar 12, 2021 at 8:19 AM Ed Snible @.***> wrote:

UX wants a istioctl describe mesh-type command that will tell a user the
settings of the mesh.
For example, the Zipkin address and sampling rate that new pods will
receive on startup.
Will it be possible for a CLI tool to get the values -- both defaults and
the cluster overrides -- for display purposes?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/istio/istio/issues/31400#issuecomment-797595910, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAEYGXKANTT7NDN2IYKINOTTDIWH7ANCNFSM4ZARAVFQ
.


Indentifier-o-Rama

Change an Identifier's E55_Type
Currently:
"https://sk.acdh.oeaw.ac.at/types/idno/geonames"
Change to:
"https://sk.acdh.oeaw.ac.at/types/idno/URL/geonames"
Currently:
"https://sk.acdh.oeaw.ac.at/types/idno/gnd"
Change to:
"https://sk.acdh.oeaw.ac.at/types/idno/URL/gnd"
Currently:
"https://sk.acdh.oeaw.ac.at/types/idno/wikidata"
Change to:
"https://sk.acdh.oeaw.ac.at/types/idno/URL/wikidata"
Change an Identifier and it's E55_Type
Currently:
"https://sk.acdh.oeaw.ac.at/types/idno/GND" and  "118566288"
Change to:
"https://sk.acdh.oeaw.ac.at/types/idno/URL/gnd" and  "https://d-nb.info/gnd/118566288"

Hm; can't find it on Varuna yet


BREAKING CHANGES:

Removed DISABLE_AMAVIS
Renamed DISABLE_* to ENABLE_* with 0 as default value. (this must be explicit)
Added missing tests for ENABLE_*
Improved readme and docker-compose example

Should fix #256 and #386
This will be released as tvial/docker-mailserver:2.1

Great improvement, thanks for your work @tomav!
I'm wondering if this change needs to introduce a new major version an in my current view it should. The reason is that the new variable names are not backwards-compatible, so those who do docker pull for v2 will encounter issues. How about giving the new release v3?

Hi @kachkaev, you're right, that's why I released a 2.1 (removed the v by the way), but not a 3.0 yet.

There's still a SMTP_ONLY which should be ENABLE_IMAP.


Espanso Emote replace dont work

Checklist

[X] I'm reporting a problem with Chatterino
[X] I've verified that I'm running the most recent nightly build or stable release
[X] I've looked for my problem on the wiki
[X] I've searched the issues and pull requests for similar looking reports

Describe your issue
Im using espanso for replacing characters with emotes, for example: :D gets replaced with 😂
in chatterino this function is not working
Screenshots
No response
OS and Chatterino Version
Windows. Chatterino 2.4.4

Use our native ignore feature

Use our native ignore feature

I believe this references the https://espanso.org/ tool which allows you to type shorthand cues which get replaced with a different text. You could make e.g. LGTM become "Looks good to me".
The user seems to be suggesting that this functionality somehow doesn't work with out text input.

Use our native ignore feature

I believe this references the espanso.org tool which allows you to type shorthand cues which get replaced with a different text. You could make e.g. LGTM become "Looks good to me".
The user seems to be suggesting that this functionality somehow doesn't work with out text input.

exactly, tried the ignore filter but didnt work.

I believe this references the espanso.org tool which allows you to type shorthand cues which get replaced with a different text. You could make e.g. LGTM become "Looks good to me".
The user seems to be suggesting that this functionality somehow doesn't work with our text input.

I wasn't aware we did anything abnormal with the text box. 🤔

something abnormal must be there, anywhere else in apps and systems its working fine (steam is more a day to day thing).
i disabled the : emote setting too

intresting, on linux (arch) its working just fine, so its a windows special thing?

for example: :D gets replaced with 😂

I tested this on Windows 10 and Qt 6 with:
matches:
  - trigger: ':D'
    replace: '😂'

This worked fine for me.

Im on Win11 Qt5
Normally i use this:

trigger: ':)'
replace: "\U0001F60A"

Just for completness i used this now

trigger: ':D'
replace: "😂"

all the same problem

Can you try it on the Qt 6 build?

Chatterino Nightly 2.4.4 (commit 76527073) built on 2023-07-02 with Qt 6.5.0, MSVC 193532217
Running on Windows 11 Version 22H2, kernel: 10.0.22621
its the same issue i have

Alright so I am able to replicate your issue only when using unicode, but I do have a workaround.
Due to the way we handle unicode, you'll need to replace :D with :joy: - since that's obviously an inconvenience for the other applications you likely use, I went ahead and read over Espanso's documentation and found the following solution.
You'll want to go ahead and make a chatterino.yml file in your config folder, and put the following in it:
filter_exec: Chatterino

extra_includes:
  - "../match/_chatterino.yml"

extra_excludes:
  - "../match/base.yml"

If your main config is no longer called base.yml, replace it with the name of your config in that file.

As well as that, you'll add a file called _chatterino.yml to your match folder, and put the following in that:
matches:
  - trigger: ':D'
    replace: ':joy:'

This setup will allow you to have both a working :D -> 😂 setup in Chatterino, but without it causing issues in your other programs.

ok feels wired while typing but works 😊 thanks for your workaround 😊


Fine tuning DistilBERT model OSError: Unable to load weights from pytorch checkpoint file.

Hello! Thanks for the excellent tutorial of an awesome DistilBERT model.  I learned and reproduced it successfully. I tried to load and predict this model "pytorch_distilbert_news.bin"  with tokenizer "vocab_distilbert_news.bin" (I changed model name as "pytorch_model.bin" and tokenizer vocab as "vocab.txt" ). I wrote the scripts as below and tested it as below, but got an error and couldn't find solution.
# Importing the libraries needed
import pandas as pd
import torch
import transformers
from torch.utils.data import Dataset, DataLoader
from transformers import DistilBertModel, DistilBertTokenizer
test ="He'll give us really healthy competition with our goalkeepers and we wish him the very best of luck."
tokenizer = transformers.DistilBertTokenizer.from_pretrained('model/')
model= transformers.DistilBertModel.from_pretrained('model/')
---------------------------------------------------------------------------
AttributeError                            Traceback (most recent call last)
~/anaconda3/envs/hgface/lib/python3.7/site-packages/transformers/modeling_utils.py in from_pretrained(cls, pretrained_model_name_or_path, *model_args, **kwargs)
    658             try:
--> 659                 state_dict = torch.load(resolved_archive_file, map_location="cpu")
660             except Exception:
~/anaconda3/envs/hgface/lib/python3.7/site-packages/torch/serialization.py in load(f, map_location, pickle_module, **pickle_load_args)
579                 return _load(opened_zipfile, map_location, pickle_module, **pickle_load_args)
--> 580         return _legacy_load(opened_file, map_location, pickle_module, **pickle_load_args)
~/anaconda3/envs/hgface/lib/python3.7/site-packages/torch/serialization.py in _legacy_load(f, map_location, pickle_module, **pickle_load_args)
759     unpickler.persistent_load = persistent_load
--> 760     result = unpickler.load()
AttributeError: Can't get attribute 'DistillBERTClass' on <module '__main__'>
During handling of the above exception, another exception occurred:
OSError                                   Traceback (most recent call last)
<ipython-input-24-827530780d10> in <module>
----> 1 model= transformers.DistilBertModel.from_pretrained('model/')
~/anaconda3/envs/hgface/lib/python3.7/site-packages/transformers/modeling_utils.py in from_pretrained(cls, pretrained_model_name_or_path, *model_args, **kwargs)
660             except Exception:
--> 662                     "Unable to load weights from pytorch checkpoint file. "     663                     "If you tried to load a PyTorch model from a TF 2.0 checkpoint, please set from_tf=True. "
OSError: Unable to load weights from pytorch checkpoint file. If you tried to load a PyTorch model from a TF 2.0 checkpoint, please set from_tf=True.
Please help. Thanks.

Hi @learnercat , i am afraid the methods specified in the Hugging Face library cannot be directly used for saving and loading these models (specially in case of Multi-class classification) since that experiment has a custom network.
We have added a few more layers on top of the Distilbert model. Hence, in order to save the model you will have to rely on the model saving and loading methods native to pytorch library. Load and Save Pytorch models
For tokenizer the hugging face procedure should work.
I tested the torch.save() and torch.load() method and it worked for me. Let me know if this helps.

Hi @abhimishra91, Thank you very much. I tried it again with touch.load(), but didn't work.
The model and tokenizer were saved as your example :
output_model_file = './models/pytorch_distilbert_news.bin'
output_vocab_file = './models/vocab_distilbert_news.bin'
model_to_save = model
torch.save(model_to_save, output_model_file)
tokenizer.save_vocabulary(output_vocab_file)
Tokenizer loaded with hugging face procedure, but there is the warning. Then model loading has got another AttributeError. Here is the scripts and error details:
# Importing the libraries needed
import torch
import transformers
import numpy as np
from torch.utils.data import Dataset, DataLoader
from transformers import DistilBertModel, DistilBertTokenizer, DistilBertForSequenceClassification
tok_path = "models/vocab_distilbert_news.bin"
tokenizer = transformers.DistilBertTokenizer.from_pretrained(tok_path)
inputs = tokenizer.convert_tokens_to_ids("He'll give us really healthy competition with our goalkeepers and we wish him the very best of luck.")
"Calling DistilBertTokenizer.from_pretrained() with the path to a single file or url is deprecated"
model_path="models/pytorch_distilbert_news.bin"
model = torch.load(model_path)
outputs = model(inputs)
last_hidden_states = outputs[0]
Here are errors-->
AttributeError                            Traceback (most recent call last)
<ipython-input-29-48088a60bf09> in <module>
1 model_path="models/pytorch_distilbert_news.bin"
----> 2 model = torch.load(model_path)
3 outputs = model(inputs)
4 last_hidden_states = outputs[0]
~/anaconda3/envs/hgface/lib/python3.7/site-packages/torch/serialization.py in load(f, map_location, pickle_module, **pickle_load_args)
578                     return torch.jit.load(f)
579                 return _load(opened_zipfile, map_location, pickle_module, **pickle_load_args)
--> 580         return _legacy_load(opened_file, map_location, pickle_module, **pickle_load_args)
~/anaconda3/envs/hgface/lib/python3.7/site-packages/torch/serialization.py in _legacy_load(f, map_location, pickle_module, **pickle_load_args)
758     unpickler = pickle_module.Unpickler(f, **pickle_load_args)
759     unpickler.persistent_load = persistent_load
--> 760     result = unpickler.load()
762     deserialized_storage_keys = pickle_module.load(f, **pickle_load_args)
AttributeError: Can't get attribute 'DistillBERTClass' on <module '__main__'>
I am not sure that my scripts might be wrong in tokenizer step. Please check it. Can I look your load and test function example? Thanks in advance.

Hi @learnercat , apologies i have been tied up with another project that i am working on.
I will be able to share a script with you by the end of this weekend. Hope that does not hamper your learning too much.

Hi @abhimishra91 , thank you so much for your kind support. I have just solved the problem. Let me share it.
After I retrained it, I saved model and vocab files as below:
model_to_save = model.module if hasattr(model, 'module') else model
torch.save(model_to_save.state_dict(), output_model_file)
tokenizer.save_vocabulary(output_vocab_file)
I input DistillBERTClass from training.ipynb to predict.ipynb;
!pip install import-ipynb
import import_ipynb
from training import DistillBERTClass
Input to tokenizer -->
tok_path = "models/vocab_distilbert_news.bin"
tokenizer = transformers.DistilBertTokenizer.from_pretrained(tok_path)
inputs = tokenizer.encode_plus("Hello, my dog is cute", return_tensors="pt", add_special_tokens=True)
Input to model -->
model_path="./models/pytorch_distilbert_news.bin"
model = DistillBERTClass()
model.to(device)
model.load_state_dict(torch.load(model_path))
model.eval()
Create predict function -->
def predict(model, inputs):
    model.eval()
    with torch.no_grad():
.         ids = inputs['input_ids'].to(device, dtype = torch.long)
.         mask = inputs['attention_mask'].to(device, dtype = torch.long)
.         outputs = model(ids, mask).squeeze()
          big_val, big_idx = torch.max(outputs.data, dim=1)
   return big_idx[0].item()
result = predict(model, inputs)
print(result)
1
I learned a lot. Again thank you very much. Have a great weekend!

Yup, this is great stuff.
You can also reduce a line of code by specifying the device when loading the model dict with the following line:
model.load_state_dict(torch.load(model_path), map_location=device)

Hi @learnercat I did the same thing as you did but I get the following error:
when I try to predict


Generalize inception layer's pooling

Hi, I'd like to use inception layers with l2 pooling, like in FaceNet, but Inception.lua only uses max pooling.
As a quick workaround for myself, I've modified the Inception layer in the master branch of my fork to accept a generic pool argument instead of just the size and stride of max pooling:
https://github.com/bamos/dpnn/commit/c91d263add5832d7209ab5e3d6fd20e73d6e8c97
This works well for me, but the downside is that I've changed the API.

Hi, I'm about to release a project that depends on the pool param in my forked version. Another idea that doesn't break the API is to keep poolSize and poolStrideto configure a max pooling layer as before, but also addpool` parameter that will override the pooling layer. Thoughts?

Done :
https://github.com/nicholas-leonard/dpnn/pull/17
Keep me posted on your release!

Awesome, thanks @nicholas-leonard!

Hi @nicholas-leonard,
Thanks again for merging this PR.
I've finally released the code that depends on it at https://github.com/cmusatyalab/openface.
dpnn made writing the network much easier.
-Brandon.

Awesome work brandon.
Love how detailed your README is. I added a link to your repo in the dpnn
documentaion :
https://github.com/nicholas-leonard/dpnn/blob/master/README.md#nn.Inception
.
Regards,
--Nick
Nicholas Léonard
917-741-7570
On Tue, Oct 13, 2015 at 9:54 AM, Brandon Amos<EMAIL_ADDRESS>wrote:

Hi @nicholas-leonard https://github.com/nicholas-leonard,
Thanks again for merging this PR.
I've finally released the code that depends on it at
https://github.com/cmusatyalab/openface.
dpnn made writing the network much easier.
-Brandon.
—
Reply to this email directly or view it on GitHub
https://github.com/nicholas-leonard/dpnn/issues/11#issuecomment-147722192
.


eShopLegacyWebForms does not compile

I found this project during MS Learn Tutorial: https://docs.microsoft.com/pl-pl/learn/modules/aspnet-session/
During exercise I was told to download project from this repository. As stated in instructions, VS asked me to install additional components. During all this time, solution did not compile.
Unfortunately VS provided only ambiguous messages about missing or conflicting packages without any error code. However, after some research, I was able to fix this error by downgrading log4net nuget package to <IP_ADDRESS>.
I can prepare a pull request if needed.

same here,  tried to build on 2 machine. installed the .net 4.7.2 which is missing on 1 machine. doesn't work on any of both.
Can someone look into this matter.

Hi @PRudykIteo / @anirugu - thank you for reaching out and reporting this behavior. Will test and update.

Hey @PRudykIteo, yes, your analysis was correct. 👍 There is some issue with the log4net package. Actually, within the src\eShopLegacyWebForms\eShopLegacyWebForms.csproj file package is still pointing to the old version 2.0.8.
And that's the reason if you downgrade the log4net, then the project gets build successfully. My suggestion would be, let's update the solution with log4net version as 2.0.10`.
You could submit a PR with the changes. We will be happy to review and merge the changes with the main branch.
Thank you.

This issue has been fixed. So closing it. Thank you.


[Bug]: Unable to extend monster's languages

Check for existing bug reports before submitting.

[X] I searched for existing Bug Reports and found no similar reports.

Expected Behavior
The Brass Dragon Wyrmling statblock has the language of Draconic.
The documentation states Any field that is a plain string or an array can be added to, by specifying the name of the field followed by a +..
So I expected, when rendered, the languages to be Draconic, Common, Infernal, Elvish.
Current behaviour
When rendered, the languages are still just Draconic.
Reproduction
monster: Brass Dragon Wyrmling
name: Dabshabah
languages+: Common, Infernal, Elvish
traits+:
  - name: Skilled Dancer

Which Operating Systems are you using?

[ ] Android
[ ] iPhone/iPad
[X] Linux
[ ] macOS
[ ] Windows

Obsidian Version Check
1.3.5
Plugin Version
3.6.5
Confirmation

[X] I have disabled all other plugins and the issue still persists.

Possible solution
Wondering if this field was just missed when extensions were added as a feature.

Hi @Gander7. This should be resolved in #249. Can you update the plugin and confirm it appears fixed for you?

Good day @sigrunixia . Updated plugin and can confirm that it is fixed.


mwc-textfield input chinese error on ios

I use mwc-textfield on my project recently. But it not work fine on IOS, include safari and chrome.
When inputing chinese use Pinyin Input Method, mwc-textfield will hold the pinyin.
input sequence is
 b -> u -> q -> u -> 不去

the value in textfield is
bbubuqbuqu不去

cannot reproduce with Simulator (iphone XR) on a mac. Can you please produce a repro case?

The device is iphone se with IOS 12.3.1
The Link is We Boo Sign In
Iphone Pinyin Input Method

I was able to reproduce your issue on that site, but unfortunately it is not one of our Textfields. The author of @authentic/mwc-textfield seems to have implemented their own version. We will soon release our @material/mwc-textfield in the next release. I was unable to reproduce the behavior on that version of mwc-textfield.

ok thx


SELinux avc agetty checkpoint_restore denied

After enabling SELinux on AWS OL9, we are getting the following messages in the audit log:
----
type=PROCTITLE msg=audit(07/29/2024 11:34:36.305:129) : proctitle=/sbin/agetty -o -p -- \u --keep-baud 115200,57600,38400,9600 - vt220
type=SYSCALL msg=audit(07/29/2024 11:34:36.305:129) : arch=x86_64 syscall=ioctl success=yes exit=0 a0=0x0 a1=0x5457 a2=0x7fffdb635b80 a3=0x8 items=0 ppid=1 pid=795 auid=unset uid=root gid=root euid=root suid=root fsuid=root egid=root sgid=root fsgid=root tty=ttyS0 ses=unset comm=agetty exe=/usr/sbin/agetty subj=system_u:system_r:getty_t:s0-s0:c0.c1023 key=(null)
type=AVC msg=audit(07/29/2024 11:34:36.305:129) : avc:  denied  { checkpoint_restore } for  pid=795 comm=agetty capability=checkpoint_restore  scontext=system_u:system_r:getty_t:s0-s0:c0.c1023 tcontext=system_u:system_r:getty_t:s0-s0:c0.c1023 tclass=capability2 permissive=0
----
type=PROCTITLE msg=audit(07/29/2024 11:34:36.434:130) : proctitle=/sbin/agetty -o -p -- \u --noclear - linux
type=SYSCALL msg=audit(07/29/2024 11:34:36.434:130) : arch=x86_64 syscall=ioctl success=yes exit=0 a0=0x0 a1=0x5457 a2=0x7ffc3aebe600 a3=0x8 items=0 ppid=1 pid=794 auid=unset uid=root gid=root euid=root suid=root fsuid=root egid=root sgid=root fsgid=root tty=tty1 ses=unset comm=agetty exe=/usr/sbin/agetty subj=system_u:system_r:getty_t:s0-s0:c0.c1023 key=(null)
type=AVC msg=audit(07/29/2024 11:34:36.434:130) : avc:  denied  { checkpoint_restore } for  pid=794 comm=agetty capability=checkpoint_restore  scontext=system_u:system_r:getty_t:s0-s0:c0.c1023 tcontext=system_u:system_r:getty_t:s0-s0:c0.c1023 tclass=capability2 permissive=0
----
...

There are no such messages for the same test on AWS RH9.
As I understand, here is the relevant Red Hat Bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=2259622
The fix was to alter selinux-policy: https://github.com/fedora-selinux/selinux-policy/commit/1e73385958fce313a6155d494a6ec5a0227d82df
Raising this issue to investigate and get a fix for Oracle Linux.

Oracle Linux customers, please file your issue at https://support.oracle.com
Thanks for filing an issue with Oracle Linux.
GitHub Issues is not an official support channel and we don't offer
product support here. If you're not yet an Oracle Linux customer,
consider signing up at https://linux.oracle.com.
Even if you're not a customer, if we can confirm that an issue is a
bug we will do our best to fix it and to update this issue
once it has been fixed. We don't guarantee a fix or feedback and
for now, we will close this issue. If you have Oracle Linux support,
please use support.oracle.com to report issues.

Oracle Linux customers, please file your issue at https://support.oracle.com
Thanks for filing an issue with Oracle Linux.
GitHub Issues is not an official support channel and we don't offer
product support here. If you're not yet an Oracle Linux customer,
consider signing up at https://linux.oracle.com.
Even if you're not a customer, if we can confirm that an issue is a
bug we will do our best to fix it and to update this issue
once it has been fixed. We don't guarantee a fix or feedback and
for now, we will close this issue. If you have Oracle Linux support,
please use support.oracle.com to report issues.

Duplicated the issue internally.

This should be fixed in version SELINUX-POLICY-38.1.35-2.0.5.EL9_4.2.


docker: install cudnn with source build only (PR2456)

Before submitting

[x] Was this discussed/approved via a Github issue? (no need for typos and docs improvements)
[x] Did you read the contributor guideline, Pull Request section?
[x] Did you make sure to update the docs?
[x] Did you write any new necessary tests?

What does this PR do?
The problem is:

torch 2.2 downloads cudnn from pypi

this is 8.9.2

thunder's docker container also has cudnn from deb pkg

https://github.com/Lightning-AI/lightning-thunder/blob/main/dockers/ubuntu-cuda/Dockerfile#L83
this is 8.9.7

FE v1.2 prefers cudnn from deb over pypi

and hence there is a mismatch

so far, we expect two kinds of users:

mainstream - install PT from the latest published (this kind of user wont play with unstill some system package and reinstall with another)
developer - fine to compile news from the source and, in such case also set any desired cudnn versio

PR review
Anyone in the community is free to review the PR once the tests have passed.
If we didn't discuss your PR in Github issues there's a high chance it will not be merged.
Did you have fun?
Make sure you had fun coding 🙃

this is not supported yet, cc @t-vi @mruberry