pyalarmdotcom: Error while setting up platform

Home Assistant release (hass --version):
0.33
Python release (python3 --version):
3.4
Component/platform:
Alarmdotcom/Raspberry Pi 2b with hassbian
Description of problem:
Alarm.com integration broken. It seems it can't access phantomjs in the hassbian image and AiO installer. Installing everything manually works UNTIL I install pozw.
Problem-relevant configuration.yaml entries and steps to reproduce:
## Alarm.com
alarm_control_panel:
  name: Alarm
  platform: alarmdotcom
  username: redacted
  password: redacted

Traceback (if applicable):
16-11-19 22:21:13 homeassistant.components.alarm_control_panel: Error while setting up platform alarmdotcom
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/helpers/entity_component.py", line 150, in _async_setup_platform
    entity_platform.add_entities, discovery_info
  File "/usr/lib/python3.4/asyncio/futures.py", line 388, in __iter__
    yield self  # This tells Task to wait for completion.
  File "/usr/lib/python3.4/asyncio/tasks.py", line 286, in _wakeup
    value = future.result()
  File "/usr/lib/python3.4/asyncio/futures.py", line 277, in result
    raise self._exception
  File "/usr/lib/python3.4/concurrent/futures/thread.py", line 54, in run
    result = self.fn(*self.args, **self.kwargs)
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/alarm_control_panel/alarmdotcom.py", line 42, in setup_platform
    add_devices([AlarmDotCom(hass, name, code, username, password)], True)
  File "/srv/homeassistant/lib/python3.4/site-packages/homeassistant/components/alarm_control_panel/alarmdotcom.py", line 51, in __init__
    self._alarm = Alarmdotcom(username, password, timeout=10)
  File "/home/homeassistant/.homeassistant/deps/pyalarmdotcom/pyalarmdotcom.py", line 82, in __init__
    if not self._login():
  File "/home/homeassistant/.homeassistant/deps/pyalarmdotcom/pyalarmdotcom.py", line 95, in _login
    self._driver = webdriver.PhantomJS()
  File "/home/homeassistant/.homeassistant/deps/selenium/webdriver/phantomjs/webdriver.py", line 51, in __init__
    log_path=service_log_path)
  File "/home/homeassistant/.homeassistant/deps/selenium/webdriver/phantomjs/service.py", line 50, in __init__
    service.Service.__init__(self, executable_path, port=port, log_file=open(log_path, 'w'))
PermissionError: [Errno 13] Permission denied: 'ghostdriver.log'

Extra info:
I've tried the fix mentioned here: https://community.home-assistant.io/t/alarm-com-issue/262/19 and me and a few others are still not able to get it working.

See my comment here on a possible fix, I don't know how to implement or test it: https://github.com/Xorso/pyalarmdotcom/issues/4

Running this command fixes the issue, but it's kind of a temporary workaround in my opinion.
sudo touch /ghostdriver.log && sudo chmod 777 /ghostdriver.log


LoRA tuning for few-shot adaptation

Hey @Asad-Ismail,
Is there a way to fine-tune GDINO with LoRA adapters using your code? If its possible, can you please add a sample code to show how its done?
Thanks!

Same question，and is there a way to fine-tune gdino with p-tuning？

Will be prioritizing this feature this week apologies for delay so far.

Added Lora finetuning using PEFT from HF, please see this PR https://github.com/Asad-Ismail/Grounding-Dino-FineTuning/pull/15


Typora not recommended as markdown editor anymore (not free to use anymore)

Fix README
README contains information that Typora shall be used as a markdown editor, I suggest to change it to MarkText or other free alternatives. VSCode could also be mentioned as it supports markdown via extensions.

DONE! Changed to MarkText...


NIFI-3025: Bump nifi-spark-receiver's jackson version to match Spark 2.0.1

Thank you for submitting a contribution to Apache NiFi.
In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:
For all changes:

[ ] Is there a JIRA ticket associated with this PR? Is it referenced
in the commit message?

Yes

[ ] Does your PR title start with NIFI-XXXX where XXXX is the JIRA number you are trying to resolve? Pay particular attention to the hyphen "-" character.

Yes

[ ] Has your PR been rebased against the latest commit within the target branch (typically master)?

Yes

[ ] Is your initial contribution a single, squashed commit?

Yes
For code changes:

[ ] Have you ensured that the full suite of tests is executed via mvn -Pcontrib-check clean install at the root nifi folder?

Yes

[ ] Have you written or updated unit tests to verify your changes?

N/A

[ ] If adding new dependencies to the code, are these dependencies licensed in a way that is compatible for inclusion under ASF 2.0?

N/A

[ ] If applicable, have you updated the LICENSE file, including the main LICENSE file under nifi-assembly?

N/A

[ ] If applicable, have you updated the NOTICE file, including the main NOTICE file found under nifi-assembly?

N/A

[ ] If adding new Properties, have you added .displayName in addition to .name (programmatic access) for each of the new properties?

N/A
For documentation related changes:

[ ] Have you ensured that format looks appropriate for the output in which it is rendered?

N/A
Note:
Please ensure that once the PR is submitted, you check travis-ci for build issues and submit an update to your PR as soon as possible.

Tests all passed locally for me, also on travis-ci.. maybe the AppVeyor CI infrastructure has problems tonight?
I see two unrelated errors:

NPM errors during nifi-web build -- unrelated and not sure they're even errors? <3 npm
PersistentProvenanceRepository tests -- unsure about this one, but passed locally for me

After opening and closing the PR to re-run tests, AppVeyor failed with a different error (testSendLargeFileHTTPWithProxy).
I think it's safe to say it's a problem with AppVeyor's boxes.

+1 Merging


Visual artifact

There is an diagonal artifact in the plot if resolution is lowered from 15 -> 2, source of problem unknown

Resolve my using bresenham


Configurable statement_indentation rule

I've updated Laravel Pint from 1.7 to 1.8, and now my lines with comments are moving.
I can disable this rule, but it will allow my co-workers do mistakes. PhpStorm doesn't follow this rule when I press the shortcut to comment lines.

on the 1.7 version there wasn't this problem

I rollback pint's changes, and downgrade to 1.7 version, run pint again, and it gave "success" result without changes

@theeldarka This is not a problem with Laravel Pint.
Because the PSR-12 ruleset is not decided here but in https://github.com/PHP-CS-Fixer/PHP-CS-Fixer
statement_indentation rule was added to PSR-2 which is also used in PSR-12:
https://github.com/PHP-CS-Fixer/PHP-CS-Fixer/pull/4885/files#diff-363628d5d69ccafd96d2e0af8e53953f65ced7cc64fd9c5dc63631977e5abfa6R58

@nunomaduro @Jubeki this does seem problematic to me? Afaik comments always start at char 0.

@driesvints Well yeah, its kind of a bug of the statement_indentation rule.
(VS Code places the comment correctly aligned with the code, were PhpStorm places it as the beginning of the line it seems)
What I meant:
The laravel preset has the rule disabled.
Where as PSR-12 (via PSR-2) has it enabled. So I think the right place to report it would be PHP-CS-Fixer instead of here.


📃: Greedy algorithm folder

:red_circle: Title : Greedy Algorithm Problems - DSA Codes
:red_circle: Aim : To provide a collection of Data Structures and Algorithms (DSA) problems solved using the greedy algorithm, demonstrating its application in optimization problems.
:red_circle: Brief Explanation : This folder contains various DSA problems solved using the greedy algorithm. Greedy algorithms work by choosing the best option at each step with the hope of finding the global optimum. The problems include well-known scenarios such as the activity selection problem, fractional knapsack, Huffman coding, and minimum spanning tree (using Prim's and Kruskal's algorithms). These solutions will help learners understand how to apply the greedy technique to solve optimization and decision-making problems efficiently.
Screenshots 📷
NA

:white_check_mark: To be Mentioned while taking the issue :

Full name :  Riya Rane
What is your participant role? GSSOC , HACTOBERFEST

Happy Contributing 🚀
All the best. Enjoy your open source journey ahead. 😎

@riyarane46 what all you are going to cover on this issue? As we have already have a greedy algorithms folder you can check our repo structure for it.


Initial Commit

This PR introduces MySql-based Akka.Persistence plugin. It's using MySql.Data for communication.

merged this in - still need to setup CI


specs: tail padding shares

Context
Similar to https://github.com/celestiaorg/celestia-app/issues/1136 but for tail padding shares

Closed by https://github.com/celestiaorg/celestia-app/pull/1244


Get Involved: Writing Documentation

Writing documentation and samples: a section should be added in github right now and a clear call to contributing doc/merge request should be featured

---
Want to back this issue? **[Post a bounty on it!](https://www.bountysource.com/issues/8138159-get-involved-writing-documentation?utm_campaign=plugin&utm_content=tracker%2F10548672&utm_medium=issues&utm_source=github)** We accept bounties via [Bountysource](https://www.bountysource.com/?utm_campaign=plugin&utm_content=tracker%2F10548672&utm_medium=issues&utm_source=github).

This is going to depend on us figuring out how we want to do documentation. Either through raw html/css or through some kind of docs system like http://www.mkdocs.org/

@danrabbit I think that you should choose GitHub + Markdown, the language used all around GitHub. That way, we could all participate in the progress, and it is pretty easy to export Markdown documents in HTML code to use it in the website itself once we write them. Markdown is pretty easy to learn and powerful enough accomplish all of the styling needed to make documentations. No additional package or web service is required. Everything could be done right here inside of a new repository.

Since we've gone with MDR, we can just add a section to CONTRIBUTE.md that details how to use Markdown.

This is somewhat dependent on #612 being merged, so I'm going to wishlist it for now.

I am unsure we now need a "writing documentation" document, most of our docs look pretty awesome already and I'm not sure what else we'd add. That said, adding a little to CONTRIBUTE.md about how to handle docs would probably help.


Remove endpoint check and update operatorGroup for DFC offering

Remove storageProvider endpoint check

loadbalancer IP that we get from provider storage cluster does not have a scheme
parsing host from url return empty string if scheme is not mentioned
parsing loadbalancer IP does not make sense because we not using a part of it
instead we are using it as a whole

Update operatorGroup to allnamespace scope for DFC

LGTM


Scope out migrating metadata instances off sha1

saml  metadata instances are still using deprecated sha1 for openssl. This needs to be migrated off sha1 to sha256 ideally

I thought this was metadata instances, not services?

you are right puku! Just testing you

Hi guys,  trying to follow this - which use of SHA1 is this about?
I can see that your metadata is signed with SHA256 - in https://md.aaf.edu.au/aaf-metadata.xml, I can see:
<ds:SignatureMethod Algorithm="http://www.w3.org/2001/04/xmldsig-more#rsa-sha256"/> and <ds:DigestMethod Algorithm="http://www.w3.org/2001/04/xmlenc#sha256"/>.
And your metadata signing certificate advertised there also uses sha256WithRSAEncryption .... so just curious, what SHA1 use is this about?

i think we did a quick scan of requests and found reqs like
I, [2023-05-24T00:52:04.451039 #15293]  INFO -- : [9e4ce88c-2d60-42a0-a6f0-d96b3b7c49f3] method=GET path=/mdq/federation-manager/entities/%7Bsha1%7D7b51df8e123263ee0a1XXXXXXXXXX format= controller=MetadataQueryController action=specific_entity_sha1 status=200 duration=311.86 view=0.96 db=200.50 params={"instance"=>"federation-manager", "identifier"=>"{sha1}

and db entries for out db like
{
    :id=>4,
    :name=>"aaf.edu.au",
    :extensions=>nil,
    :created_at=>2016-10-05 23:13:22 UTC,
    :updated_at=>2018-04-10 01:04:46 UTC,
    :ca_verify_depth=>nil,
    :hash_algorithm=>"sha1",
    :keypair_id=>2,
    :identifier=>"aaf-legacy",
    :all_entities=>true,
    :federation_identifier=>"aaflegacy",
    :validity_period=>604800,
    :cache_period=>21600,
    :primary_tag=>"aaflegacy"
}

so it may just be an issue with our data. though to be fair maybe we didnt look hard enough
@bo-aaf mind doing a bigger review of all this incase we were looking int he wrong direction?

Hi @phyzical , thanks for the context - I think you are following a false lead here.
This is not about using SHA1 in any way related to cryptography.
This is just the standard Metadata Query (MDQ) interface, which also provides a way of requesting metadata for an entity based on the SHA1 hash of its entityID.
Have a look at the section 4.2.  Use of SHA-1 in Transformed Identifiers in the MDQ spec at https://datatracker.ietf.org/doc/draft-young-md-query-saml/
They conclude they do not see the use of SHA1 as a concern at the moment - with recommendations on treating collisions in MDQ implementations.
But without changing the MDQ specification, there is not much you'd be able to do about this....
Cheers,
Vlad

@vladimir-mencl-eresearch thanks for that,
just for your context the last bit that i think wasn't mentioned is that this all stemmed from this test,
https://github.com/ausaccessfed/saml-service/blob/master/spec/support/metadata/signature.rb#L95
So your probably right and its just a redundant test at this point. but to be safe we will have to review all data in all environments

Thanks for that!
I see ... the MetadataInstance model in app/models/metadata_instance.rb allows hash_algorithm to be either sha1 or `sha256.
The tests aim to cover all paths, so also try signing metadata with SHA1.
The actual algorithm used by a MetadataInstance is selected by its hash_algorithm - which defaults to SHA256, as per https://github.com/ausaccessfed/saml-service/blob/master/bin/configure.rb#L94-L95
So it should be enough for you to audit existing MetadataInstance instances and check their HashAlgorithm.
E.g. with:
MetadataInstance.all { |md| puts "#{md.name} #{md.hash_algorithm}" } ; nil
But unless it was explicitly overridden to SHA1, it should be SHA256 - the default was there from the beginning.
So maybe the right solution would be just dropping the tests for SHA1 and maybe even restricting the model for MetadataInstance to not allow SHA1 for hash_algorithm ....
Cheers,
Vlad

PS: Just checked our instances: all using SHA256.


fix touser and toparty do not work

Thank you for your code, but they have a little problem. I do not know if this is the correct solution to the problem, I have a simple success test 4 it.

yes, you r right and thank you . push  message to the tag is  very flexible   for the prod mode .I recommend using totag instead of touser and toparty.


Daemonize rpc-downloader and importer-offline

User description
Turns rpc_downloader and importer_offline as daemon, so they can keep running unstoppable

PR Type
Enhancement

Description

Implemented daemon mode for both importer_offline and rpc_downloader, allowing them to run continuously and process new blocks.
Added configuration options for daemon mode and interval in src/config.rs.
Enhanced importer_offline to support continuous block processing in daemon mode, with error handling and shutdown mechanisms.
Modified rpc_downloader to support continuous downloading of blocks and balances in daemon mode.
Improved error handling and added graceful shutdown capabilities for both binaries.

Changes walkthrough 📝
Relevant filesEnhancement

importer_offline.rsImplement daemon mode for importer_offline

src/bin/importer_offline.rs
Added daemon mode functionality to the external RPC storage loader  Implemented continuous block processing in daemon mode  Added error handling and shutdown mechanisms

+56/-38

rpc_downloader.rsAdd daemon mode to rpc_downloader

src/bin/rpc_downloader.rs
Added daemon mode to continuously download blocks and balances  Implemented a loop to restart the download process after a wait period  Added shutdown handling for daemon mode

+22/-7

Configuration changes

config.rsAdd daemon mode configuration options

src/config.rs
Added daemon mode configuration option for RpcDownloaderConfig  Added daemon mode and interval configuration options for ImporterOfflineConfig

+12/-0

💡 PR-Agent usage: Comment /help "your question" on any pull request to receive relevant information

/benchmark

Benchmark:
Run ID: bench-1677534657
Git Info:

Branch: feat-daemonize
Commit: 5021f7c
PR: #1854

Configuration:

Target Account Strategy: Default

RPS Stats: Max: 1005.00, Min: 650.00, Avg: 822.13, StdDev: 52.47
TPS Stats: Max: 937.00, Min: 701.00, Avg: 796.68, StdDev: 59.93
Plot: View Plot


Pluggable HTTP request identifiers

Adds a linkerd-identifer-http module, and uses the current http.Identifier for the BasicHttpIdentifierInitializer.
I'm not very happy about adding a finagle http dependency to linkerd-core, but I needed HttpIdentifierInitializer in core in order to call LoadService[HttpIdentifierInitializer]() ... while at the same time wanting it typed to Identifier[http.Request]. Not sure if anyone has suggestions there.
(also...the reverse of echo is ohce)
Fixes #120

What about renaming HttpIdentifierInitializer to just IdentifierInitializer and moving it into core?  You would still have BasicHttpIdentifierInitializer extend IdentifierInitializer and you'd be able to change the load service line to LoadService[IdentifierInitializer] and kill the unwanted dependency.

@adleong yeah I think I understand what you're proposing there, there's just an added wrinkle where I want a type-safe way to make sure the identifier can be used in the http router. Users shouldn't be able to use io.l5d.identifier.basicHttp in the thrift router etc.
...maybe a moot point since only http accepts identifiers right now? But I think oliver had a similar request in #120 "These plugins must be protocol-specific"

HttpConfig would still contain a HttpIdentifierConfig so you would only be able to specify an http identifier in the http config.  HttpIdentifierConfig would still produce an Identifier[http.Request] so I think you're still good from a type-safety point of view.
With my suggestion, all IdentifierInitializers would get loaded (potentially for multiple protocols) but they would only be used if there was a config class that included them.

ok cool, I'll try it out, thanks :)

note: i would prefer if users don't have to specify fully-qualified paths.  I'd love it if each protocol could have a default identifier, and others could be provided.  Not a hard requirement but io.l5d.identifier.basicHttp is a bit verbose when we're already in the identifier field in the http protocol.

:star: nice! :id:

squashed and rebased after latest master conflict

This is looking good! just a few comments around clarity

:star: :stars: Looks good. Just noting that changing the nesting on httpUriInDst is a breaking config change and will require a minor version bump when we release.

rebased and added to changelog


Fixed a bug which caused an erroneous '.' prefix on extracted qualified names when classes had no package. [phab:D1874]

Created by craigbarber at 2017-08-15 00:09:59:

craigbarber wrote at 2017-08-15 00:11:34:

Appled google-java-format

craigbarber wrote at 2017-08-15 00:12:34:

Appled google-java-format

fromberger accepted this revision at 2017-08-15 01:14:35

craigbarber closed via commit a08817dad724c32be8541a841254e6c9e491a590 at 2017-08-15 16:12:37


Ignores config point size and always "Font size changed to Size(22)" instead

Which operating system does the issue occur on?

Ubuntu 18.10, freshly installed alarcritty, config copied from this repo.

If on linux, are you using X11 or Wayland?

X11
Alacritty seems to ignore size: 11.0 setting and always resizes font to 22:
[INSERT] % alacritty -v
Created log file at "/tmp/Alacritty-3200.log"
[2019-03-16 10:59] [INFO] Welcome to Alacritty
[2019-03-16 10:59] [INFO] Configuration loaded from "/home/artem/.config/alacritty/alacritty.yml"
[2019-03-16 10:59] [INFO] Device pixel ratio: 2.1666666666666665
[2019-03-16 10:59] [INFO] Width: 2219, Height: 1664
[2019-03-16 10:59] [INFO] Initializing glyph cache...
[2019-03-16 10:59] [INFO] ... finished initializing glyph cache in 0.027609956s
[2019-03-16 10:59] [INFO] Width: 2219, Height: 1664
[2019-03-16 10:59] [INFO] Cell Size: (19 x 37)
[2019-03-16 10:59] [INFO] Padding: (4.333333333333333 x 4.333333333333333)
[2019-03-16 10:59] [INFO] PTY Dimensions: Line(44) x Column(116)
[2019-03-16 10:59] [INFO] Initialisation complete
[2019-03-16 10:59] [INFO] Font size changed to Size(22) with DPR of 2.1666666666666665
[2019-03-16 10:59] [INFO] Width: 2560, Height: 1391

Why is this? And how can I make it respect the size setting?
Thank you!

The font is using douple the size internally to increase precision without using full floating point numbers.
This is intended.

If by 'same results' you mean that the size 12 is printed in the log, then everything's fine.
If you're still getting 22, the config file is likely at a different location than what you're changing.

Oh yeah, you're right - I was changing the wrong config... Thanks!


SOAPRequest deprecated from Cloud SDK 5.4.0 version

Hi Team,
I have noticed that the SOAPRequest class has been deprecated after the recent Cloud SDK changes and would like to know what could be an alternative for the same.
Regards,
Amna

Hi @AmnaNizarHussain,
unfortunately, we are not planning to provide any alternative for our current SOAP functionality.
Best regards,
Johannes

Hi @Johannes-Schneider ,
I understand there are still many SOAP based APIs exposed by SAP and Cloud SDK provides the convenience of consuming these APIs.
Dont you think this has a wider impact on the solutions (Both for SAP as well as Custom Built applications for System to System Communications) relying on Cloud SDK to connect with SAP SOAP APIs?
It would be better if this was never removed and kept deprecated for future major version releases.
Thanks,
Animesh

Hi @AnimeshKumar03,
I think I'm the wrong person to answer those questions.
Therefore, pinging @jjtang1985 (product owner of the SAP Cloud SDK).
Best regards,
Johannes

Hi @AnimeshKumar03 ,
Thank you very much for approaching us.

Dont you think this has a wider impact on the solutions (Both for SAP as well as Custom Built applications for System to System Communications) relying on Cloud SDK to connect with SAP SOAP APIs?

We have no ideas about how many users are using SAP SOAP APIs.
However, from our statistics of the SDK users, the share of SOAP users is limited.
The deprecation message is an indicator that we will remove that in the future (no timeline so far), so users can find other alternatives:

other SDKs or copy the same code
switch to OData based API if possible

Thank you very much for your understanding.
Best regards,
Junjie


Move off of project.json and back to .csproj

It's going to have to happen sometime. :smile:
One consideration is whether we stick with .NET CLI. Once the embedded Mono work is done (#666), OmniSharp won't need to run on .NET Core. Additionally, if OmniSharp moves off of .NET Core during the move to .csproj, support won't implicitly be dropped for versions of Visual Studio earlier than 2017.

yes, I vote for dropping .NET Core as it will not add any value anymore after #666 / #709 and less complexity is always better

most definitely, we only jumped on board because mono was a painful dependency.

I'll try to get us moved over to csproj next week in that case.

Looks like I actually got this done. :smile:


fixed react 19 errors

Summary
Fixes major bug with React 19 release candidate, which is causing errors in dotcom when using React Next FF.
Makes parts of react-dom full externals of the library, to prevent conflict in React 19+/
What should reviewers focus on?

Check our Storybook, which uses React 18 still works okay
Check integration tests pass (currently use React 18)

Steps to test:

Storybook

Contributor checklist:

[ ] All new and existing CI checks pass
[ ] Tests prove that the feature works and covers both happy and unhappy paths
[ ] Any drop in coverage, breaking changes or regressions have been documented above
[ ] New visual snapshots have been generated / updated for any UI changes
[ ] All developer debugging and non-functional logging has been removed
[ ] Related issues have been referenced in the PR description

Reviewer checklist:

[ ] Check that pull request and proposed changes adhere to our contribution guidelines and code of conduct
[ ] Check that tests prove the feature works and covers both happy and unhappy paths
[ ] Check that there aren't other open Pull Requests for the same update/change

Screenshots:
Fixed and tested in Next.js RC

 Before  After

👍
Do you think it's worth bumping our Next.js integration test to use the Next 15 RC so we can keep an eye on React 19 compatibility in the pipelines? Once Next 15 reaches GA we can revert so we're not constantly tracking an RC.

The current Next.js test is still valid, and arguably more important than the RC as we need to ensure compat with latest stable Next.js. We could create a second integration test though specifically for React 19, and use Next.js RC as the mechanism to verify. That's a good shout, I'll take a look later this week.


Can't join the server

server started but I can't join server :<

@Alanaktion

@Alanaktion

@discordenjoyer Can you provide additional details of the problem?

Does the Server have an public IP ?
Is the server in your Local Network?

If you are in the same network as the server, you should use the local IP
Other users should use the Public IP

Log files:

Minecraft Server Logs
PHP Server Logs
Server Process Tree (list of running processes) (optional)

Please specify which Software/Versions are used:

Operation System
PHP
Webserver (ex.: Apache/Nginx)
Java
screen


Helm Controller is constantly requeuing deployments

Hi
Using version 0.13.2 here and running into the issue that the helm controller is constantly redeploying the jobs even when no HelmChart changes happen:
time="2023-04-08T21:37:23Z" level=info msg="Event(v1.ObjectReference{Kind:\"HelmChart\", Namespace:\"kube-system\", Name:\"gitea\", UID:\"c7440515-b8a0-415f-aaeb-0188c3c1bd75\", APIVersion:\"helm.cattle.io/v1\", ResourceVersion:\"71794639\", FieldPath:\"\"}): type: 'Normal' reason: 'ApplyJob' Applying HelmChart using Job kube-system/helm-install-gitea"
time="2023-04-08T21:37:23Z" level=error msg="error syncing 'kube-system/gitea': handler helm-controller-chart-registration: helmcharts.helm.cattle.io \"gitea\" not found, requeuing"

I use this to deploy to k3s 1.26.3:
apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
metadata:
  name: helmcharts.helm.cattle.io
spec:
  group: helm.cattle.io
  names:
    kind: HelmChart
    plural: helmcharts
    singular: helmchart
  preserveUnknownFields: false
  scope: Namespaced
  versions:
  - additionalPrinterColumns:
    - jsonPath: .status.jobName
      name: Job
      type: string
    - jsonPath: .spec.chart
      name: Chart
      type: string
    - jsonPath: .spec.targetNamespace
      name: TargetNamespace
      type: string
    - jsonPath: .spec.version
      name: Version
      type: string
    - jsonPath: .spec.repo
      name: Repo
      type: string
    - jsonPath: .spec.helmVersion
      name: HelmVersion
      type: string
    - jsonPath: .spec.bootstrap
      name: Bootstrap
      type: string
    name: v1
    schema:
      openAPIV3Schema:
        properties:
          spec:
            properties:
              bootstrap:
                type: boolean
              chart:
                nullable: true
                type: string
              chartContent:
                nullable: true
                type: string
              failurePolicy:
                nullable: true
                type: string
              helmVersion:
                nullable: true
                type: string
              jobImage:
                nullable: true
                type: string
              repo:
                nullable: true
                type: string
              repoCA:
                nullable: true
                type: string
              set:
                additionalProperties:
                  nullable: true
                  type: string
                nullable: true
                type: object
              targetNamespace:
                nullable: true
                type: string
              timeout:
                nullable: true
                type: string
              valuesContent:
                nullable: true
                type: string
              version:
                nullable: true
                type: string
            type: object
          status:
            properties:
              jobName:
                nullable: true
                type: string
            type: object
        type: object
    served: true
    storage: true

---
apiVersion: apiextensions.k8s.io/v1
kind: CustomResourceDefinition
metadata:
  name: helmchartconfigs.helm.cattle.io
spec:
  group: helm.cattle.io
  names:
    kind: HelmChartConfig
    plural: helmchartconfigs
    singular: helmchartconfig
  preserveUnknownFields: false
  scope: Namespaced
  versions:
  - name: v1
    schema:
      openAPIV3Schema:
        properties:
          spec:
            properties:
              failurePolicy:
                nullable: true
                type: string
              valuesContent:
                nullable: true
                type: string
            type: object
        type: object
    served: true
    storage: true

---
apiVersion: v1
kind: ServiceAccount
metadata:
  labels:
    app.kubernetes.io/component: controller
    app.kubernetes.io/name: helm-controller
  name: helm-controller
  namespace: kube-system
---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  labels:
    app.kubernetes.io/component: controller
    app.kubernetes.io/name: helm-controller
  name: helm-controller
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: cluster-admin
subjects:
- kind: ServiceAccount
  name: helm-controller
  namespace: kube-system

---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: helm-controller
  namespace: kube-system
  labels:
    app: helm-controller
spec:
  replicas: 1
  selector:
    matchLabels:
      app: helm-controller
  template:
    metadata:
      labels:
        app: helm-controller
    spec:
      containers:
        - name: helm-controller
          image: rancher/helm-controller:v0.13.2
          command: ["helm-controller"]
      enableServiceLinks: false
      serviceAccountName: helm-controller

The reason why I deploy the helm controller to k3s is because since upgrading to k3s 1.26.3 (from 1.26.1) the embedded helm controller does not deploy any HelmChart ressources anymore. I might open a seperate issue in k3s, but for now this should do the job.

since upgrading to k3s 1.26.3 (from 1.26.1) the embedded helm controller does not deploy any HelmChart ressources anymore.

That seems like a more important issue, can you open an issue in the k3s repo and provide additional information on what's going on with that?

I would also note that if you're going to deploy this to k3s, you should be sure to add the --disable-helm-controller option to the k3s servers.

I would also note that if you're going to deploy this to k3s, you should be sure to add the --disable-helm-controller option to the k3s servers.

This is done with the following line in k3s config.yaml file:
# Disabled components
disable:
    - servicelb
    - traefik
    - metrics-server
    - helm

Let me know if I should do it with the option
How can I enable the debug option in helm-controller.
The k3s issue will be in a 2nd step, for now it's just important that it works, because I need the helm deployments (critical for networking)

disable:
   - servicelb
   - traefik
   - metrics-server
   - helm

no, that's not right. It is --disable-helm-controller as I said.

How can I enable the debug option in helm-controller.

adding the --debug flag to the command line args should do it?

Thanks you,
Using the disable-helm-controller: true in the k3s.yaml file fixed the issue. I guess the 2 controllers fought each other in state.
I also upgraded to 0.13.3 now and it seems to run stable.
I have the feeling that my etcd is somewhat borked (why the k3s internal controller doesn't work anymore), but since it's a production cluster, I can not easily revert to the embedded helm controller and I would rather have it externally and properly loggable.
Another question would be if I can somehow tolerate the node-not-ready condition, because I am deploying the CNI with Helm.
How is this done within k3s?
Thanks for the nice and fast help.

For the controller, because it will need to spawn before the CNI plugin can spawn

You would need to add a NotReady toleration to the example deployment, set it up to run with host network, and add node selectors that require it to run on control-plane node.


⚠ Bofrost.de has degraded performance

In 12f9f2f, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1687 ms

Resolved: Bofrost.de performance has improved in c6d2f79.


New Issue Test

body https://github.com/KnpLabs/php-github-api/blob/master/doc/issues.md

A

b

Novoooo 🧠


DH keys too small after conversion --> Dovecot does not allow logins --> Suggest auto-fix after conversion

Is your feature request related to a problem? Please describe.
After the conversion of a server, Dovecot email login was no longer possible due to short keys used on the server.
Describe the solution you'd like
https://support.plesk.com/hc/en-us/articles/12377016572439-Unable-to-log-in-to-Roundcube-webmail-or-using-email-client-on-Plesk-server-Can-t-load-DH-parameters-dh-key-too-small
# plesk sbin sslmng --service dovecot --strong-dh --dhparams-size=2048
(fixed it)
Describe alternatives you've considered
n/a
Additional context
Maybe it would be good if the script could check whether the issue described in the KB article exists after a conversion and then automatically run the dhparams-size command to increase the key size.

The problem should be fixed in #191.


Keychain credentials - better support for protocol and port

Motivation:
KeychainAuthorizationProvider supports HTTPS only and no port. Credentials for URLs that include port or HTTP URLs stored in Keychain are not found.
Changes:

Support HTTP
Use URL port as search criteria

@swift-ci please smoke test

@swift-ci please smoke test Linux

@swift-ci please smoke test Linux

@swift-ci please smoke test

@swift-ci please test Windows platform


Interface to let moderators create additional public chat channels that users can find and join

Also make an option to make them announcements

Closing as the new UI has been developed after this issue was opened and this issue relates only to the old UI.
(The new UI has this)


first demo

I should make one demo first
should do some basic thing

[x]   http service
[x]   crawl spider
[x]   record crawl status
[ ]   cluster status
[ ]   node cluster interaction

demo is ok


Allow passing custom fetch function

This PR introduces a small feature where fetch function used within the HttpClient class can be customized.
Allowing to pass a custom fetch function enables a few things -

Add implicit telemetry to the fetch function
hook into before and after the function call is made in a generic way
Handle special cases in a generic way around fetch function itself

Implements the feature from: #219

Hello @sushruth !
Thanks for your contribution!
This changes will be added in the next release


Add convenience function to wrap a Workflow with Anyworkflow

Is your feature request related to a problem? Please describe.
To match the current pattern for building Workflows it would be great to be able to end the build chain with
eraseToAnyWorkflow. This would follow other modern swift paradigms (example AnyPublisher).
Describe the solution you'd like
Create an extension method on Workflow that will return the current Workflow erased as AnyWorkflow
Describe alternatives you've considered
N/A
Additional context
N/A

It certainly aligns with other concepts like Combine's eraseToAnyPublisher(). I also wonder if there's some version of this that makes sense with SwiftUI tests, since SwiftUI workflows tend to get really complex type information.
This is probably a low-priority addition, but PRs are welcome!


Implement MockQuerySnapshot.metadata

Just use the already implemented class MockSnapshotMetadata .

Thank you!

Just published your fix to https://pub.dev/packages/fake_cloud_firestore/changelog#210. Thanks again


Action button style on Box L and Box M

Description
The hover state of Box L and Box M does not change the control button style according to the Design Library definition.

Expectation
The control button changes its background color and icon color as shown in the screenshot below.

@panchovm after clicking the play button should the button be with black background and the pause icon in white?


Update to Swift 2.2

Talk about update! 👍  I have forgotten to update this pod 🍡  and its almost Swift 3.0!

@nferocious76 we can create a swift3 branch and I can update it. Then when Xcode 8 GM comes up we can merge with master

Ah yes.. no problem! thanks. I have never visited this project since I thought no one would use it. I think I need to visit this one from time to time haha


refactor(supplementary-contracts): update TokenUnlocking scripts

This is Great!
Looking forward to Taiko Mainnet
It's been a long Journey down here.
Kudos to the entire Team
Congratulations 🎊 🥳

Let's goo ✅

Hi

0xf02186Fd29D685666525903B83aeEE1fA0E28395
i hope will eligibile TGE Taiko

I don't know yet


Document Supported cases for Co-author

Document Supported cases for Co-author
@nickmango to document this
@mlehotskylf to upload it to EasyCLA docs

Document has been shared with the team
cc @mlehotskylf

@mlehotskylf to review doc provided by @nickmango.
Once done then @nickmango work with Sourabh to update EasyCLA documentation.

https://docs.linuxfoundation.org/lfx/easycla/v2-current/easycla-and-co-author-compliance-guide


Fix configuration of trigger layers in V16 geometry

[x] Change set of disconnected trigger layers for V16 era
[x] Update layer weights for V16 era
[ ] Change layer numbers values for V16 in configuration files

After fixing the layer weights for V16, shift cluster pT upwards [1], and changes in the max layer distribution in particular around the transition between CE-E and CE-H [2].
Changes are expected since weights are larger and the first CE-H layer is shifted from layer 29 to layer 27.
[1]

[2]


Excluded tasks are not taken into consideration

Experiment 5 of the Gradle validation scripts does not consider tasks which have been excluded using the -x Gradle option. In order to better provide a consistent experience, we should add support for this.
Note: This will also require a change to the Gradle Enterprise API as excluded tasks are not returned in the API response.

I've asked the engineering team to expose this value in the Enterprise API of GE 2023.1.

Closing for now.


Build Error in Ubuntu 16.04 with <IP_ADDRESS>-beta

Hi
I'm new to building nginx with pagespeed by hand, but I think I followed this article on DigitalOcean OK (changing the version numbers).
nginx-1.10.0 in Ubuntu 16.04
I'm getting this output when running sudo dpkg-buildpackage -b
...
o objs/addon/src/ngx_pagespeed.o \
    /home/ricardo/custom-nginx/nginx-1.10.0/debian/modules/ngx_pagespeed/src/ngx_pagespeed.cc
cc: internal compiler error: Killed (program cc1plus)
...
objs/Makefile:1317: recipe for target 'objs/addon/src/ngx_pagespeed.o' failed
make[3]: *** [objs/addon/src/ngx_pagespeed.o] Error 4
make[3]: Leaving directory '/home/ricardo/custom-nginx/nginx-1.10.0/debian/build-light'
Makefile:8: recipe for target 'build' failed
make[2]: *** [build] Error 2
make[2]: Leaving directory '/home/ricardo/custom-nginx/nginx-1.10.0/debian/build-light'
debian/rules:161: recipe for target 'build.arch.light' failed
make[1]: *** [build.arch.light] Error 2
make[1]: Leaving directory '/home/ricardo/custom-nginx/nginx-1.10.0'
debian/rules:143: recipe for target 'build' failed
make: *** [build] Error 2
dpkg-buildpackage: error: debian/rules build gave error exit status 2

My rules file:
...
light_configure_flags := \
    $(common_configure_flags) \
    --with-http_gzip_static_module \
    --without-http_browser_module \
    --without-http_geo_module \
    --without-http_limit_req_module \
    --without-http_limit_conn_module \
    --without-http_memcached_module \
    --without-http_referer_module \
    --without-http_scgi_module \
    --without-http_split_clients_module \
    --without-http_ssi_module \
    --without-http_userid_module \
    --without-http_uwsgi_module \
    --add-module=$(MODULESDIR)/nginx-echo \
    --add-module=$(MODULESDIR)/ngx_pagespeed

I try it in the full mode as well, same error.
What am I missing?
Thanks

how much memory do you have on your VM? It looks to me like your compiler OOM'd from the line
cc: internal compiler error: Killed (program cc1plus)

512MB
Never thought about that.
What would be the minimum RAM need to build this?
Thanks

To be totally honest, I'm not exactly sure how much memory is needed. I think 512mb should be workable if there's nothing else competing for the ram. Can you try building immediately after a reboot?

@crowell  Thanks, it was the RAM
I started a 4GB (just in case) VM in DigitalOcean, and everything built. Copied over the files to my original VM and they installed perfectly.

Hi Ricardo,
I'm trying to do the same .. and same error :)
Did you try to add swap file before ram update?
Can you post your used psol version?
Thanks

Hi @TihomirS
No, I didn't. Since DigitalOcean is SSD based they advise you not to enable swap. But it didn't cost more than a few cents, to run the 4GB VM, I destroyed it afterwards.
The versions where
nginx-1.10.0
ngx_pagespeed release-<IP_ADDRESS>-beta.zip
psol <IP_ADDRESS>.tar.gz

Hi @ricardogomes
thank you for fast reply .. will try again with 3g swap (only for build) and this versions :)
and yes .. if fail again will try with 4 g real ram ..
best wishes from Bulgaria
T.

WOW :) with right psol <IP_ADDRESS>.tar.gz build is smooth and OK
Thank you @ricardogomes

I faced a similar issue when building pagespeed v<IP_ADDRESS>-stable with nginx. I was doing this on an Amazon LightSail VPS (with 512 MB Memory). I re-tried a few times and but there always build failure ( The error message was cc: internal compiler error: Killed (program cc1plus) but the files causing it changed) But then I tried with a 1GB Memory instance (EC2 t2.micro) and was able to build without problem. Didn't test extensively,  but I suppose we need around 1GB Memory to make this work


Email settings user widget - can't subscribe user to list

EmailSettingsFormFactory in formSucceeded loads only user preferences. So user can't be subscribed to new created mailing list because user doesn't have record in user_subscriptions table for this list.

Hm, that's weird. Creating mailing list should trigger creation of mail_user_subscription record in Mailer. Looking at the handler, I see the issue: https://github.com/remp2020/remp/blob/master/Mailer/app/hermes/ListCreatedHandler.php#L41
We'll remove this line so the record is always created correctly.
Until then, please run php bin/command.php mail:sync-user-subscriptions in Mailer to add missing mail subscription records.

As i see this is not problem with mailer but with mailer module. In EmailSettingsFormFactory is iteration only over userPreferences. https://github.com/remp2020/crm-remp-mailer-module/blob/a3db2bf7092f08ec1780ea5a27087c0f7c3c1ec3/src/Forms/EmailSettingsFormFactory.php#L155
So if user has no record for list in mail_user_subscriptions then it is impossible to subscribe user via this widet to this list.

After your fix in mailer i think this problem persists only on not auto subscribe lists.

@ricco24 Reading userPreferences is intentional, as there's an expectation that Mailer keeps track of all newsletter-user subscription combinations. That means that each user should have record (userPreference) for each newsletter whether she is subscribed to it or not. That's why reading userPreferences` should be sufficient.
When the new user is registered, CRM calls Register API to create these records (see highlighted lines):
https://github.com/remp2020/remp/blob/master/Mailer/app/api/v1/Handlers/Users/UserRegisteredHandler.php#L65
And when new newsletter is created in Mailer, it's handled by the handler I referenced before:
https://github.com/remp2020/remp/blob/master/Mailer/app/hermes/ListCreatedHandler.php#L47
It looks to me that there are only these two scenarios that can affect mail_user_subscriptions and both are covered by CRM's Mailer module and by REMP Mailer.
Are you still seeing the issue, after running the mail:sync-user-subscriptions command and trying the fixed version from July 13+? If so, is there a way how to identify the users with missing newsletter subscription info? (whether they're new registrations?)


Incorrect referrals are somehow accepted by the system

In order to generate a referral, the simple way is to head to the URL and check that the game and discount is there. However, it seems that the API prematurely returns this, and THEN checks if you actually have access, which means I am taking false-positives :(
Since all I do is a fetch, this can be troublesome to debug.
To consider options

Used puppeteer to ensure that the referral is valid


[WIP] Document KEP 3157 (watch-list) for milestone 1.31

Document https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/3157-watch-list

Thank you for the early review. I have a question: As part of the graduation, we also enabled the feature for KCM just under a different FG (WatchListClient) - the FG is part of the client-go library (default off). Do we want to document this as well? If so, where would be the best place to include this information?

I'm assuming that you'll be able to enable the WatchListClient feature gate via k-c-m's command line. If that's right, we need a PR to document the feature gate.
If it's an internal detail of client-go, documenting it is optional. The documentation for client-go (and other client libraries) is much less detailed than the main K8s docs, and we wouldn't delay the v1.31 release to get that level of detail changed.

/sig api-machinery

I'm closing this placeholder PR since the feature will miss the 1.31 release
/close


operators [CI] hive-operator

Abhinav and Devan are no longer on the team
I misspelled Joel's handle via #142 / 22e823f :(

/ok-to-test

/merge possible


Split Release Job to Publish Job for Documents Publications only

Description
There are times where the documents are the only thing to be released and not the packages themselves. Hence, it's best to split into 2 Jobs:

Release - for the products' release.
Publish - for only the document release.

Expected Behavior
Release Job and Publish Job are separated where the latter is executed after the former.
Current Behavior
Release Job handles both works and it's hard to update documents without manually deleting pkg/ directory.
Associated Data Files
No response

definitely not backward compatible.


10 Small Aircraft thumbnail does not display in search results

Thumbnail for 10 Small Aircraft image id:79ec58d78b8f42e7871e350abbf79787 does not display in search results list

This is typically an issue with the thumbnail size being larger then the required size.

Fixed, please verify.

verified as fixed


refactor(paeckchen-core): call sorcery async

Coverage remained the same at 100.0% when pulling 1eb3b85d10a89d8167ccc4020fbee6311c6a30b8 on core/async-sorcery into 3fdf5c0e44aa1bd486c87345fdd0c9dde994e490 on master.


Chore: add npm scripts: test

IMO it's better to add #!/bin/sh to test.sh, chmod +x it and then add ./test.sh as a script because it's sh compatible and there is no need for bash per se.

Just as option, maybe it's worth considering replacing sh with shelljs just like vue?

@nickmessing up to this. I encountered some questions when running test on windows 10. https://github.com/vuejs-templates/webpack/issues/748#issuecomment-309307368

@Aladdin-ADD, that is fixed by using shelljs which is cross-platform

@nickmessing is this good to merge for you?

@LinusBorg, yes, I use only linux based operating systems but this solution will not work on windows. As long as nobody who works on this template uses windows it's fine but if there is requirement to support windows I'd highly recommend rewriting test.sh in .js with shelljs.
So it's your call, do you want to support windows or unix is okay? :wink:

I think this is ready to merge. 🚀
to replace sh to shelljs, we can finish it in another PR.


[6.0] Bug Redis queue

Laravel Version: 6.0.3
PHP Version: 7.3
Database Driver & Version: mariadb / Redis 5.0.5 / phpredis
Description:
I had a couple of queue jobs failed in Horizon (with redis) and when I resubmitted them via Horizon I got an error from Bugsnag. This wont stop until I restarted the Horizon worker...
https://github.com/laravel/framework/blob/6.x/src/Illuminate/Queue/RedisQueue.php#L230
/src/Illuminate/Queue/RedisQueue.php:230

[$job, $reserved] = $nextJob;

ErrorException Undefined offset: 1
    /home/test/releases/341/vendor/laravel/framework/src/Illuminate/Queue/RedisQueue.php:230 Illuminate\Foundation\Bootstrap\HandleExceptions::handleError
    /home/test/releases/341/vendor/laravel/framework/src/Illuminate/Queue/RedisQueue.php:230 Illuminate\Queue\RedisQueue::retrieveNextJob
    /home/test/releases/341/vendor/laravel/framework/src/Illuminate/Queue/RedisQueue.php:169 Illuminate\Queue\RedisQueue::pop
    /home/test/releases/341/vendor/laravel/horizon/src/RedisQueue.php:92 Laravel\Horizon\RedisQueue::pop
    /home/test/releases/341/vendor/laravel/framework/src/Illuminate/Queue/Worker.php:264 Illuminate\Queue\Worker::getNextJob
    /home/test/releases/341/vendor/laravel/framework/src/Illuminate/Queue/Worker.php:118 Illuminate\Queue\Worker::daemon
    /home/test/releases/341/vendor/laravel/framework/src/Illuminate/Queue/Console/WorkCommand.php:112 Illuminate\Queue\Console\WorkCommand::runWorker
    /home/test/releases/341/vendor/laravel/framework/src/Illuminate/Queue/Console/WorkCommand.php:96 Illuminate\Queue\Console\WorkCommand::handle
    /home/test/releases/341/vendor/laravel/horizon/src/Console/WorkCommand.php:46 Laravel\Horizon\Console\WorkCommand::handle
    [internal] call_user_func_array
    /home/test/releases/341/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:32 Illuminate\Container\BoundMethod::Illuminate\Container\{closure}
    /home/test/releases/341/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:90 Illuminate\Container\BoundMethod::callBoundMethod
    /home/test/releases/341/vendor/laravel/framework/src/Illuminate/Container/BoundMethod.php:34 Illuminate\Container\BoundMethod::call
    /home/test/releases/341/vendor/laravel/framework/src/Illuminate/Container/Container.php:591 Illuminate\Container\Container::call
    /home/test/releases/341/vendor/laravel/framework/src/Illuminate/Console/Command.php:192 Illuminate\Console\Command::execute
    /home/test/releases/341/vendor/symfony/console/Command/Command.php:255 Symfony\Component\Console\Command\Command::run
    /home/test/releases/341/vendor/laravel/framework/src/Illuminate/Console/Command.php:179 Illuminate\Console\Command::run
    /home/test/releases/341/vendor/symfony/console/Application.php:915 Symfony\Component\Console\Application::doRunCommand
    /home/test/releases/341/vendor/symfony/console/Application.php:272 Symfony\Component\Console\Application::doRun
    /home/test/releases/341/vendor/symfony/console/Application.php:148 Symfony\Component\Console\Application::run
    /home/test/releases/341/vendor/laravel/framework/src/Illuminate/Console/Application.php:90 Illuminate\Console\Application::run
    /home/test/releases/341/vendor/laravel/framework/src/Illuminate/Foundation/Console/Kernel.php:131 Illuminate\Foundation\Console\Kernel::handle
    /home/test/releases/341/artisan:37 [main]

I sometimes have the same issue... https://github.com/laravel/framework/issues/29969

Did you updated your code? You should always restart horizon when code changes during deployment.

For me it seems to happen after a job has failed, even without horizon I get this error sometimes

@it-can did you try one of the support channels like I asked in the issue?

nevermind, there are multiple people now also having this issue. It seems to happen on v6 on laravel, before no problems at all with 5.6 - 5.8 for me... Nothing changed in my queue jobs whatsoever, only upgraded to v6.

@it-can can you please try on a support channel first?

nevermind

This problem has not been fixed in the 6.x branch, can you still release the version here?

@cloud-arrow 6.x isn't supported anymore sorry. Please upgrade to v10


bunch of additions

sorry for packing this all in one pr, i thought i'd just try. i added a bunch of stuff and updated the docs.
in detail, roughly sorted by impact:

add matomo analytics integration
added remark42 comments engine (unfortunately dependent on the cactus comments "fix")
fixed that the cactus comments script is not included/loaded if cactus comments are not enabled
add a switch for disabling the page gallery (which is really annoying if you want to include images)
add an option for an <hr> element before comments

should all be tested, at least it works on my site :) .

+1


Coastalv2

Front end shows highest value between Alfieri and coastal flooding Water Level as per Ata

It seems like you have 3 PRs that do partly the same things!!


e-mail uniqueness check fails when e-mail address not provided

This issue is reprinted from https://github.com/Tivix/django-rest-auth/issues/485  (PR:https://github.com/Tivix/django-rest-auth/pull/537)
(When using social login)

I traced the problem to the user not providing an e-mail address (which is valid in my use case), which results in a 400 error: "User is already registered with this e-mail address."

I can also confirm that this bug exists in version 1.1.0, not sure if this has been fixed in later versions.

Thank you for investigating.


Generate the encryption key if it was not provided

@pedro-hos, this PR supports the generation of the encryption keys.
So if the user has not provided a key then it will be generated and base64url encoded. if the user has already provided some secret string then it will only be base64url-encoded. The decryption code decodes the encryption key first, then gets a digest out of it and finally uses it to decrypt.
Please try this PR and let me know what you think, thanks

Hi, @sberyozkin I've tested here the base64url-encoded. It sounds good.

Thanks @pedro-hos, the auto-generation will be preferred, as we will increase it to 32 chars for ex or even longer


Adding a proper README

Adding commits guideline, fastAPI introduction and project overview to the README.

Does its issue has been complete?

@lucasmontano fastapi supports async functions, watch out ^

its on their doc

one more thing to update on readme.... thanks lucas hahaha

Does its issue has been complete?

@jbarbosaamancio nops, i already sent a pull request, but i was for flask content, now i updated it, and im waiting response...

@ArthurFleischman I sent pull request to readme only, after do you may see my pull request about readme? I'm seeing some things about fast API it's amazing and easy is much similar to flask

@jbarbosaamancio its good, but now, you already have stuff to put in, not just the headers

go to my patch-1 branch and read my README.md. @lucasmontano didnt like just the main.py and README in the SAME pull request

@ArthurFleischman I checked your PR, but you're changing multiples files. ReadME PR should change only the ReadME file. All PRs need to be concise and address only what's needed to resolve an issue.

ok! bad habit...

of mine


Why is this fixed to localhost?

I want to run the server on one of my local machines and use if from from other ones in the same private network. I wonder why this (and some other similar software) is only running on localhost? I can rewrite it to use another host. I just wonder why it is how it is?

It can actually run on any server. Not just localhost. Here for instance is a customized version. Running perfectly on a live server: https://chat.thephai.com/.
You simply just rebuild it from source or do however you like with docker and then expose your running installation port to a reverse proxy.
Just do:
OLLAMA_HOST=<IP_ADDRESS> OLLAMA_ORIGINS=* ollama serve
Or with docker, you can specify a port.
docker run -d -v ./ollama -p 11434:11434 -e OLLAMA_ORIGINS="*" --name ollama ollama/ollama
Then from there do a reverse proxy to forward 11434 to https via 443 or standard ssl.

OK. I missed the OLLAMA_HOST / OLLAMA_ORIGINS env variables. I just found them in the FAQ. I think this belongs into the documentation.


[PE-D][Tester C] Quick Notes functionality undocumented & unable to save

Steps to replicate:
After text has been entered in the box, and the save button is entered, nothing really happens so not sure if this is intended behaviour or not. Furthermore there is no mention of this in the UG or at least a quick glance and search through the table of context does not show how it should work

Labels: type.FeatureFlaw severity.Medium
original: lilozz2/ped#6

Issue raised is intended behaviour.
TODO:
Improve documentation on Quick Notes.

#199


settings lock paired with scheduler

Hi,
so excited about the recent merge and the whole new host of features, thank you so much @roberttidey.
One thing I was thinking about is locking stuff like awb/exposure because I'm noticing substantial fluctuations in color and light with the pinoir on my security camera prototype if there's any movement in the scene.
Playing with the python picamera for faster prototyping I seem to be getting decent results by settings and releasing awb and exposure_mode at short intervals to let it adjust to the new light conditions before locking it again (computing new settings manually doesn't seem feasible/accurate).
Do you think this makes sense and could be included in RPI_CWI?
thanks,
Spike

Can you clarify a couple of things on this? When you say set and release do you mean alternate between auto and some other mode? Plus what sort of time interval are we talking about?

@roberttidey I mean auto Vs manual settings. So basically set awb_mode to auto for example and give it a few ms to level out the gains, save them and then set it to off and assigned the saved gains. Same for exposure_mode and exposure_speed. Repeat this process maybe ever 5-10 mins, considering light might change quite a bit over that time period.
This is an example with picamera: http://picamera.readthedocs.org/en/latest/recipes1.html#capturing-consistent-images
lemme know if that makes enough sense now. Thanks.

You could sort of do this today using schedule management_command, at least as a test to check feasibility.

Set management_interval to 600 for 10 minute check
Write script to echo -n 'wb auto' >/var/www/FIFO sleep for say 1 sec then echo -n 'wb off' >/var/www/FIFO
Make script executable
Set management_command to execute script

not sure that will work, maybe raspimjpeg is different, but as far as I understand once you set awb_mode to off you're on your own, meaning you need to set the various gains yourself and I've no idea how to go about calculating those myself so I'd have to read them out after sleeping for 1sec, but I don't know that that is possible through the pipe, is it?


Question:Is DOH/DOT resolver supported by godns?

The situation is that some isp or vps provider may hijack public dns server like <IP_ADDRESS>/<IP_ADDRESS> or even all（by redirect udp port 53 request),which results a dns cache longer than expected.
Even if the dns record is already updated,the result we got from server by looking up through public dns server is still the outdated one.This could lead to a duplicated dns record update and notify.eg,If the cache is 5mins and the cronjob frequency is 1min,we will see a 4~5 times duplicated dns record update and nofity.
This is why I reopened https://github.com/TimothyYe/godns/issues/172 today by mistake and the close it after I found it's actually a dns cache problem.
DOH/DOT resolver seems to be a good solution for such kind of dns hijack(cache) problem,is it possible to add support to godns?
Thanks!

or we can simply just add custom resolver port support and we run a doh/dot client by ourselves locally.


Expiration dates divided by 1000?

I'm having problems with validating tokens coming back from the Identity Server.
Looking through the code I'm seeing this bit:
let expires_in = parseInt(values.expires_in);
        if (typeof expires_in === 'number' && expires_in > 0) {
            let now = parseInt(Date.now() / 1000);
            this.expires_at = now + expires_in;
        }

I'm trying to understand the logic here. I'm assuming that IdentityServer is doing something similar on its end, because parsing the exp and auth_time values on the access_token coming back is giving me values in 1970.
The openId Connect spec seems to imply seconds from 1970
"exp
REQUIRED. Expiration time on or after which the ID Token MUST NOT be accepted for processing. The processing of this parameter requires that the current date/time MUST be before the expiration date/time listed in the value. Implementers MAY provide for some small leeway, usually no more than a few minutes, to account for clock skew. Its value is a JSON number representing the number of seconds from 1970-01-01T0:0:0Z as measured in UTC until the date/time. See RFC 3339 [RFC3339] for details regarding date/times in general and UTC in particular."
Am I missing something?

I think you are looking at the wrong part of the specification. See https://openid.net/specs/openid-connect-core-1_0.html#ImplicitAuthResponse
expires_in
OPTIONAL. Expiration time of the Access Token in seconds since the response was generated.

The division is done to get the nearest second for doing access token expiration checks. That's unrelated to id_token checks.


nixos/nextcloud: remove invalid --database-table-prefix option

Motivation for this change
This doesn't work anymore and thus breaks the installation leaving a
broken /var/lib/nextcloud.
It isn't a big deal since we set this value in the override config
before, so the correct table-prefix is still used. In order to confirm
that, I decided to add a custom prefix to the basic test.
Things done

Built on platform(s)

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

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
21.11 Release Notes (or backporting 21.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

[x] Fits CONTRIBUTING.md.

Leaving an option that does nothing will probably be confusing and potentially misleading.

Well the feature works perfectly fine (as demonstrated by the test) because the option in override.config.php still exists.

Oh, sorry. I misunderstood the motivation. Read again after your comment and I think I get it now. In that case 👍 from me!


undefined method `reload_shim' for PoiseService::Resources::PoiseService::Resource

following the doc i stumbled into an issue:
  poise_service 'srv' do
    command 'somecmd'
    user 'someuser'
    directory '/somedir''
    provider :upstart
    reload_shim true
    stop_signal 'KILL'
  end

chef 12.5.1 running on ubuntu 12.04 including upstart 1.5. regards

Duplicate of #16.


Merge feature/kotlin to convert library to Kotlin

Removes old Java code.

Since each module had its own Kotlin conversion PR into the feature/kotlin branch and review comments were addressed there I will skip the review phase for this enormous PR.


Use file!() macro to avoid manually defining the name of migration

PR Info

Closes #705

Adds

[x] DeriveMigrationName procedural macro
[x] get_file_stem helper method to parse and get file stem

Changes

[x] Update all migrations to use the new DeriveMigrationName procedural macro

Awesome


Ability to configure Geoform with more layout flexibility

It would be great to be able to format the layout of the Geoform with additional non-field elements in the Geoform builder. For example, the ability to add text/custom HTML blocks between fields, and to be able to group fields into categories with a heading above each. These sort of features exist in traditional forms but would be extremely useful for Geoforms as well.

I would like to have the ability to move the map to the top of the form so users can see what information has been entered. This is important for my users since spatial relationships and time are a concern.

Yes, we'll add this option when we make the 4x JSAPI version of this app.

Yes. like to see could customize organize the text boxes. For instance, I have a long list of attribute fields info need to input, it will be much user friendly  if I can group the text boxes and give it a group title.


Decoding xl_heap_delete and xl_heap_update structs is missing t_cid field

In waldecoder.rs:
 pub struct XlHeapDelete {
     pub xmax: TransactionId,
     pub offnum: OffsetNumber,
     pub infobits_set: u8,
     pub flags: u8,
 }

But the corresponding Postgres struct in heap_xlog.h looks like this:
/* This is what we need to know about delete */
typedef struct xl_heap_delete
{
	TransactionId xmax;			/* xmax of the deleted tuple */
	OffsetNumber offnum;		/* deleted tuple's offset */
	uint32      t_cid;
	uint8		infobits_set;	/* infomask bits */
	uint8		flags;
} xl_heap_delete;

The Rust version is missing the t_cid field. Because of that, we won't read the XLH_DELETE_ALL_VISIBLE_CLEARED flag in 'flags' correctly, and might fail to clear the VM bit correctly,
I suspect that this explains https://github.com/zenithdb/zenith/issues/460, but I'm opening a new issue because I'm not sure.

#460 reproduces on my laptop and with following patch:
diff --git a/pageserver/src/waldecoder.rs b/pageserver/src/waldecoder.rs
index bc072ff..874bb3c 100644
--- a/pageserver/src/waldecoder.rs
+++ b/pageserver/src/waldecoder.rs
@@ -368,6 +368,7 @@ impl XlHeapMultiInsert {
 pub struct XlHeapDelete {
     pub xmax: TransactionId,
     pub offnum: OffsetNumber,
+    pub t_cid: u32,
     pub infobits_set: u8,
     pub flags: u8,
 }
@@ -377,6 +378,7 @@ impl XlHeapDelete {
         XlHeapDelete {
             xmax: buf.get_u32_le(),
             offnum: buf.get_u16_le(),
+            t_cid: buf.get_u32_le(),
             infobits_set: buf.get_u8(),
             flags: buf.get_u8(),
         }

test is working. So probably that was the reason.

#460 reproduces on my laptop and with following patch:
diff --git a/pageserver/src/waldecoder.rs b/pageserver/src/waldecoder.rs
index bc072ff..874bb3c 100644
--- a/pageserver/src/waldecoder.rs
+++ b/pageserver/src/waldecoder.rs
@@ -368,6 +368,7 @@ impl XlHeapMultiInsert {
 pub struct XlHeapDelete {
     pub xmax: TransactionId,
     pub offnum: OffsetNumber,
+    pub t_cid: u32,
     pub infobits_set: u8,
     pub flags: u8,
 }
@@ -377,6 +378,7 @@ impl XlHeapDelete {
         XlHeapDelete {
             xmax: buf.get_u32_le(),
             offnum: buf.get_u16_le(),
+            t_cid: buf.get_u32_le(),
             infobits_set: buf.get_u8(),
             flags: buf.get_u8(),
         }

test is working. So probably that was the reason.

You missed the padding before 't_cid', so that's still not actually decoding it right. See https://github.com/zenithdb/zenith/pull/462. Maybe it was still the same bug and this still fixes it, not sure?

You missed the padding before 't_cid', so that's still not actually decoding it right. See #462. Maybe it was still the same bug and this still fixes it, not sure?

Yeah, right. Test in #462 was able to catch missing buf.get_u16_le()


Persistent storage for snap server data

Is your feature request related to a problem? Please describe.
I run the Snap.Net system tray applet on my Windows computer and Android phone, both of which allows me to manage device volumes and give names to each device on my fleet.  However, each time the snapcast server is restarted, either because the multiroom-server container is restarted or the device is rebooted, the information I've set for my fleet is lost.
Describe the solution you'd like
There appears to be a way to persistently store the device info on the snapcast server, using a configuration option in snapserver.conf.
[server]
datadir = /var/cache/snapcast/
And then provide that location as a volume in Docker.  (My local repo is too messed up to try this myself at the moment.)
Configured Snap.Net client:

Initial state, and what it looks like any time I restart the sanpserver:

I'd love to see this too. I've been trying to use homeassistant to do some automations, but everytime one or all of the devices are restartet, the group names change and thus breaking all set automations.

I'd love to see this too. I've been trying to use homeassistant to do some automations, but everytime one or all of the devices are restartet, the group names change and thus breaking all set automations.

I've been struggling with this exact problem as well.  Between Snapcast and Plex, I had to kill of media player discovery entirely because it has just been adding WAY too many dynamic entities.


Not compatible with latest Androidx version

Describe the bug
A clear and concise description of what the bug is.
com.amplifyframework.ui:authenticator:1.0.0 is not working with latest compose bom library . It is only being compatable with androidx.compose.animation:animation:1.4.3 .And it is not working with any of the upper version.
We are faing this issue to implement amplify in Android:-
java.lang.NoSuchMethodError: No static method AnimatedContent(Ljava/lang/Object;Landroidx/compose/ui/Modifier;Lkotlin/jvm/functions/Function1;Landroidx/compose/ui/Alignment;Ljava/lang/String;Lkotlin/jvm/functions/Function4;Landroidx/compose/runtime/Composer;II)V in class Landroidx/compose/animation/AnimatedContentKt; or its super classes (declaration of 'androidx.compose.animation.AnimatedContentKt' appears in /data/app/~~6bhZICrgqVij99eBwBhVhA==/com.kotak.kotakpro.qa-b8N8K3H1VJQv0sX17v-0zQ==/base.apk)
at com.amplifyframework.ui.authenticator.ui.AuthenticatorKt.Authenticator(Authenticator.kt:112)
To Reproduce
A code sample or steps:

   Authenticator(
            signInContent = {
                Amplify.Auth.signIn(
                    "888888888888", "8888888888", { result ->
                        if (result.isSignedIn) {

                            Toast.makeText(context, "authenticated", Toast.LENGTH_SHORT).show()

                    } else {
                        Toast.makeText(context, "not authenticated", Toast.LENGTH_SHORT).show()
                    }
                }, {
                    startSensorEvent.value = true
                }
            )
        }
    ) {
     //content
    }

Which AWS service(s) are affected?
amplify authenticator

I've transfered this issue to the authenticator repsoitory.
@manas661 please confirm that you're using the latest version of Authenticator, 1.3.0. There was a fix around the animation libraries included back in 1.0.2.


"Auto Apply" not working

Bug:
The "Auto Apply" option is not working.
Expected Behaviour:
I couldn't find a description to what it is supposed to do, but I'm assuming it is used in combo with "hide controls" so we can get the output on the day selection action.
Reproduce:

Angular 12.0.4
Datetimerangepicker: 2.4.3
Chrome Version 91.0.4472.114
(As for now jul/2021 the demo is also not working https://angular-datetimerangepicker.surge.sh/)

__ footnote:
Very useful module, thank you sir :)

@BrunoWB
If you have time picker enabled its not easy to decide on when to auto apply.
So it get automatically disabled. Try disabling timepicker and auto apply will work fine.

This makes for a very inconsistent behaviour, when you say "not easy to decide on when to auto apply" you mean functionality-wise or technical/code-wise?
If you think this should stay as is, I'd recommend adding a mutual exclusion contraint on the demo, so ppl will know that using the timepicker will disable auto-apply. :)
(getting a bit ahead of your answer, if you meant functionality-wise) Ideas for expected UX behaviour:
I'd think having the (rangeSelected) for when user press 1)apply | (if on flyout mode) 2)press enter or 3)exits the "flyout" calendar. this would also be legacy-friendly ppl wouldn't have issues updating the component
add (rangeChanged) outputs an event any time calendar suffered a change from user input, in the date or in time, I think this is going to be most useful for devs, we can handle changes as we see fit


[Feature] Add support for responsive options declaration

The aim of this PR is to add support for responsive options declaration with the data-option-... attributes. The suggested API is the following:

Declare an option with responsive capabilities in its configuration:

import { Base, withResponsiveOptions } from '@studiometa/js-toolkit';

class Component extends withResponsiveOptions(Base) {
  static config = {
    options: {
      foo: {
        type: String,
        responsive: true
      },
    },
  };
}

Use data-option-... attributes to define different values for different breakpoints in your HTML:

<div data-component="Component"
  data-option-foo="default value"
  data-option-foo[xs,s]="value for `xs` and `s` breakpoints"
  data-option-foo[l]="value for `l` breakpoint">
  ...

The feature can be tested in the browser in the deploy-preview of the demo.
To be noted:

Responsive options are readonly
This feature will not be compatible with withFreezedOptions decorator
This does not make options reactive, the different values are resolved when the option is accessed

To do:

[x] Move the changes in OptionsManager to a child class, which would override the get() method (to avoid bloating)
[x] Find a way to change the managers used by a component to allow usage of child classes (dependency injection via a new managers parameter for the constructor method?)
[x] Use the ResponsiveOptionsManager class in the withResponsiveOptions decorator
[ ] Add documentation

@studiometa/core, does this seem like a very useful, somehow useful or not needed feature?

Not sure this is important to us, but data-option-foo[xs,s]="..." does not pass W3C validator
I do link the syntax 😄

Not sure this is important to us, but data-option-foo[xs,s]="..." does not pass W3C validator I do link the syntax 😄

That's why responsive options are readonly, an error is thrown when we do:
element.dataset['data-option-foo[xs]'] = 'foo';

The : is valid, so we could use it instead:
element.dataset['data-option-foo:xs'] = 'foo';

But the , is not valid, so we cannot use multiple breakpoints. Maybe we should use min-width tests instead of exact match?

I updated the syntax to use : as separator to be W3C compliant :
  <div data-component="Component"
    data-option-foo="default value"
-   data-option-foo[xs,s]="value for `xs` and `s` breakpoints"
+   data-option-foo:xs:s="value for `xs` and `s` breakpoints"
-   data-option-foo[l]="value for `l` breakpoint">
+   data-option-foo:l="value for `l` breakpoint">
    ...

cc @perruche

I updated the syntax to use : as separator to be W3C compliant :
  <div data-component="Component"
    data-option-foo="default value"
-   data-option-foo[xs,s]="value for `xs` and `s` breakpoints"
+   data-option-foo:xs:s="value for `xs` and `s` breakpoints"
-   data-option-foo[l]="value for `l` breakpoint">
+   data-option-foo:l="value for `l` breakpoint">
    ...

cc @perruche

nice !


Feature/rfc 1035 domain name syntax

What is this pull request?
Relax the current restriction on account names. This commit supports account names of the domain-name syntax defined in RFC1035.
Why do you implement it? Why do we need this pull request?
We needed to create an account based on an e-mail address.  For example, when a user register into our system with his/her email address, our system creates an account in iroha ledger from email-addresses' local part.
How to use the features provided in the pull request?
From the interface's point of view, this commit changes what sequence of characters are accepted as a valid account name, and does not change the current interface nor add new interface.
Details/Features
List of features / major commits

Add a utility class DnsParser which validates if a string conforms to domain-name syntax(4b134338)

Codecov Report

Merging #694 into develop will decrease coverage by 0.06%.
The diff coverage is 12.5%.

@@             Coverage Diff             @@
##           develop     #694      +/-   ##
===========================================
- Coverage     43.1%   43.03%   -0.07%
===========================================
  Files          302      304       +2
  Lines        12324    12345      +21
  Branches      6826     6846      +20
===========================================
+ Hits          5312     5313       +1
  Misses         713      713
- Partials      6299     6319      +20

Impacted Files
Coverage Δ

irohad/model/execution/impl/command_executor.cpp
40.86% <0%> (-0.07%)
:arrow_down:

.../module/irohad/model/execution/dns_parser_test.cpp
0% <0%> (ø)

...ule/irohad/model/command_validate_execute_test.cpp
13.02% <100%> (-0.02%)
:arrow_down:

irohad/model/execution/impl/dns_parser.cpp
25% <25%> (ø)

Continue to review full report at Codecov.

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

Thank you for your first time contribution! We are really pleased to see improvements like these
It would be nice to see also contribution to https://github.com/hyperledger/iroha-api in docs branch, to keep the docs about API consistent

Does sorabot have anything to say?

@Warchant you see — for some reason sorabot haven't triggered on such PR, can you please check that?

Guten Tag
Ich bin aktuell nicht im Büro, Ihre Mail wird daher nicht umgehend bearbeitet.
Wenden Sie sich bei dringenden Angelegenheiten bitte an<EMAIL_ADDRESS>oder 061 261 43 48.
Freundliche Grüsse
Markus Stauffiger

@neewy sorabot does not work for forks. If you want to trigger sorabot, then setup SORABOT_TOKEN env variable inside circle CI. It should contain personal access token with repo permission. Account which analyzes PR should have push access to this PR.

Next time please don't forget to rebase branch onto develop :)
# once add hyperledger/iroha repo as upstream
git remote add upstream git@github.com:hyperledger/iroha.git
git fetch upstream

# then, to rebase:
git checkout $yourbranch
git rebase -i upstream/develop

I did this for you this time.


Scrape "People also ask" from search engines

Thanks for this wonderful tool! One function I found useful is to scrape "People also ask" section from search engines. Both Google and Bing have this functionality, it often shows up when the input query is some kind of question, e.g. "capital of USA". It includes a list of question/answers related to the input query.
Thanks!

I will add it if you provide me with the javascript code that implements this functionality.


apache-directory-studio: Update urls

Relate to https://repology.org/repository/scoop/problems

Homepage link http://directory.apache.org/studio/ is a permanent redirect to its HTTPS counterpart https://directory.apache.org/studio/ and should be updated.

https://www.apache.org/dist redirect to https://downloads.apache.org

[X] I have read the Contributing Guide.

/verify


Visible notifier3D problem Godot 4 RC

Godot version
v4.0.rc1.official [8843d9ad3]
System information
Windows 10, Forward+, Intel Iris Xe Graphics
Issue description
I used 2 signals, one for when entering screen, it makes the node visible, other for exiting screen, it makes the node invisible, both technically work, but when a node becomes invisible after exiting screen, it doesn't become visible when entering screen. i can still interact wih it, it just doesn't become visible.
This doesn't happen in godot 3.4.
Steps to reproduce

Minimal reproduction project
N/A

actually we talked about it in reddit https://www.reddit.com/r/godot/comments/10xnd62/visible_notifier3d_problem_godot_4_rc/

here is the sceen with the visiblenotifier btw same hierarchy as how it was in godot 3.4 before i ported it

It isn't a bug, it's a consequence of how the implementation works, why should the notification of visible be fired if the node isn't actually visible

It isn't a bug, it's a consequence of how the implementation works, why should the notification of visible be fired if the node isn't actually visible

Are you talking about the if statement? it happens even without the if statements.

No I'm talking about the if statement, are you not making the notifier hierarchy not visible, if it isn't visible on screen it isn't visible

No I'm not talking about the if statement, are you not making the notifier hierarchy not visible, it isn't visible on screen if it isn't visible

ah ok, i wasn't sure that's how it worked in godot 4. Thanks!
In godot  3.4, you don't have to worry about that

That's what I gathered from the original bug referenced above and in the Reddit thread

Also if you consider this to not be a good functionality I'd suggest opening a discussion in proposals as bug reports aren't for making statements, that's what it sounded like given the comment on the Reddit thread

If you (or anyone else) are not happy with this new behavior please submit a bug report

To clarify what is happening, every Node3D/CanvasItem has logic like this:

is node visible? (visible is true, and in case of CanvasItems, modulate.a > 0)
is rect/aabb on screen?
If yes, draw. If not, don't draw.

This code is run for every CanvasItem/Node3D node to cull items that don't need drawing and is very performant. VisibilityNotifier used to run some specific logic, but now it hooks into the drawing code, which makes it more accurate and performant.

To clarify what is happening, every Node3D/CanvasItem has logic like this:

is node visible? (visible is true, and in case of CanvasItems, modulate.a > 0)
is rect/aabb on screen?
If yes, draw. If not, don't draw.

This code is run for every CanvasItem/Node3D node to cull items that don't need drawing and is very performant. VisibilityNotifier used to run some specific logic, but now it hooks into the drawing code, which makes it more accurate and performant.

every node3d has logic like that without even using visibility notifier node, right?

Yes.

ok thanks

Since this came up on reddit, if you need the ability to turn off the visibility (and thus the culling pass for a canvas item) based on whether it would be visible in the camera or not,

having VisibilityNotifier perform the same culling checks even when visible=false would mean doubling up culling work in all cases where that node is used. This would clearly be a deficiency in the engine. The new behavior is both consistent and better performing than previous uses of the node.
trust that 2D culling is doing the job you were previously trying to accomplish (it probably is)
If 2d culling is the actual root of your performance issue (profile before premature optimization!), and you are not using multiple viewports, you can solve most of the problem by just checking the CanvasItem's distance-squared from the main camera node and switching visible based on that. This will introduce a new design constraint for you: any individual CanvasItem affected by this must not be so large as to have its center point exceed the distance between the visible-boundary and the actual viewport bounds.
If you have a need for multiple viewports with different cameras, you must rely on culling instead, as you cannot mutate a node between viewport renders.

Note that VisibilityNotifier takes arbitrary NodePath to a node, so you can put it anywhere in your tree.


October View works improperly on Firefox 40.0.3

Hi everybody.
I'm having a problem with October month on IE and Firefox 40.0.3.
When I start the JSFiddle, the 3-calendar view on October has two 17 days. As you can see on image below.
Firefox (http://jsfiddle.net/z4fmvuzb/)

If I select September, 18th, October starts to show normally, but when I click on other day, October crashes again.
It happens when I change to only one calendar view too.
Could you fix this? Thanks.

There is no such issue in Firefox on Linux. Which means that you likely have outdated version of Windows with buggy patch applied (there was such an issue with RTZ 2 at least). It was discussed already even in this repository and have known fixes (the best one is just to install latest updates to buggy Windows version).
Look here for details:

https://github.com/nazar-pc/PickMeUp/issues/42
https://github.com/nazar-pc/PickMeUp/issues/47

(some comments in Russian)


Installation on Windows 10 Help.

Hello, I am unable to install Pylyzer on windows 10 to be used in Virtual Studio Code. Please Help.

Unable to install the VSCode extension?
Please show me any error logs if you have.

Windows 11x64
VSCode -- updated
Rust - ustalled + updated
VScode extention pylyzer is installed without problem.
But after open the python file return error
[Error - 3:16:26 PM] pylyzer client: couldn't create connection to server.
Launching server using command pylyzer failed. Error: spawn pylyzer ENOENT

When we try to install pylyzer by cargo catch the error:
   Compiling py2erg v0.0.23
error[E0432]: unresolved import `erg_compiler::erg_parser::ast::SimpleTypeSpec`
  --> C:\Users\kobzar\.cargo\registry\src\github.com-1ecc6299db9ec823\py2erg-0.0.23\convert.rs:15:16
   |
15 |     Signature, SimpleTypeSpec, SubrSignature, Tuple, TypeAscription, TypeBoundSpecs, TypeSpec,
   |                ^^^^^^^^^^^^^^
   |                |
   |                no `SimpleTypeSpec` in `ast`
   |                help: a similar name exists in the module: `TupleTypeSpec`

error[E0599]: no variant or associated item named `Simple` found for enum `PreDeclTypeSpec` in the current scope
   --> C:\Users\kobzar\.cargo\registry\src\github.com-1ecc6299db9ec823\py2erg-0.0.23\convert.rs:525:65
    |
525 |                 let none = TypeSpec::PreDeclTy(PreDeclTypeSpec::Simple(SimpleTypeSpec::new(
    |                                                                 ^^^^^^ variant or associated item not found in `PreDeclTypeSpec`

error[E0599]: no variant or associated item named `Simple` found for enum `PreDeclTypeSpec` in the current scope
   --> C:\Users\kobzar\.cargo\registry\src\github.com-1ecc6299db9ec823\py2erg-0.0.23\convert.rs:610:89
    |
610 |             ExpressionType::Identifier { name } => TypeSpec::PreDeclTy(PreDeclTypeSpec::Simple(
    |                                                                                ^^^^^^ variant or associated item not found in `PreDeclTypeSpec`

error[E0599]: no variant or associated item named `Simple` found for enum `PreDeclTypeSpec` in the current scope
   --> C:\Users\kobzar\.cargo\registry\src\github.com-1ecc6299db9ec823\py2erg-0.0.23\convert.rs:613:74
    |
613 |             ExpressionType::None => TypeSpec::PreDeclTy(PreDeclTypeSpec::Simple(
    |                                                                          ^^^^^^ variant or associated item not found in `PreDeclTypeSpec`

error[E0599]: no variant or associated item named `Simple` found for enum `PreDeclTypeSpec` in the current scope
    --> C:\Users\kobzar\.cargo\registry\src\github.com-1ecc6299db9ec823\py2erg-0.0.23\convert.rs:1018:83
     |
1018 |                         let param_typ_spec = TypeSpec::PreDeclTy(PreDeclTypeSpec::Simple(
     |                                                                                ^^^^^^ variant or associated item not found in `PreDeclTypeSpec`

error[E0599]: no variant or associated item named `Simple` found for enum `PreDeclTypeSpec` in the current scope
    --> C:\Users\kobzar\.cargo\registry\src\github.com-1ecc6299db9ec823\py2erg-0.0.23\convert.rs:1071:63
     |
1071 |         let class_spec = TypeSpec::PreDeclTy(PreDeclTypeSpec::Simple(SimpleTypeSpec::new(
     |                                                               ^^^^^^ variant or associated item not found in `PreDeclTypeSpec`

error[E0599]: no variant or associated item named `Simple` found for enum `PreDeclTypeSpec` in the current scope
    --> C:\Users\kobzar\.cargo\registry\src\github.com-1ecc6299db9ec823\py2erg-0.0.23\convert.rs:1098:63
     |
1098 |         let class_spec = TypeSpec::PreDeclTy(PreDeclTypeSpec::Simple(SimpleTypeSpec::new(
     |                                                               ^^^^^^ variant or associated item not found in `PreDeclTypeSpec`

error[E0599]: no variant or associated item named `Simple` found for enum `PreDeclTypeSpec` in the current scope
    --> C:\Users\kobzar\.cargo\registry\src\github.com-1ecc6299db9ec823\py2erg-0.0.23\convert.rs:1203:58
     |
1203 |         let class = TypeSpec::PreDeclTy(PreDeclTypeSpec::Simple(SimpleTypeSpec::new(
     |                                                          ^^^^^^ variant or associated item not found in `PreDeclTypeSpec`

Some errors have detailed explanations: E0432, E0599.
For more information about an error, try `rustc --explain E0432`.
error: could not compile `py2erg` due to 8 previous errors

but install is continiued and finished
error: failed to compile `pylyzer v0.0.23`, intermediate artifacts can be found at `C:\Users\kobzar\AppData\Local\Temp\cargo-installC6QmgR`

Destructive updates of dependencies are now supported (in v.0.0.24).

0.0.25 installed and working.

You can close this issue.
0.0.26 was installed and working to.


Misplaced data on Statistics section on Homepage

Describe the Bug
There is a redundant space added as margin-top on the statiscts blocks wrappers which misplaces them (both for mobile and desctop).
The issue seems to be fixed if the margin-top is removed.:

Please observe if it affects other elements.
To Reproduce

Go to https://podkrepi.bg/
Scroll down to "Какво постигнахме досега? / What we achieved so far?" section.
Observe the right section with the statistics - the blocks are not centered vertically.

Expected Behavior
The elements should be centered vertically.

I'd like to take this issue.


💥 [DevOps] Discussion for how we can restructure the service

💥 DevOps ticket

Discussion for how we can restructure the service so we have a clear and set goal and have @Mogge start working on that
Aims are:

How can we implement backend test?
How can we have a proper API definition, preferable graphql?
What languages should we use?

I believe we came to the conclusion that:
We want to (What)

remove the community server in the long run
use an unified GraphQL api interface towards the frontend
implement backend tests on top of the GraphQL interface
let nginx handle the webserver stuff
move the functionality of the community server either in the login server, the node or the GraphQL interface implementation
have @Mogge implement this GraphQL backend part and the communication towards the frontend via GraphQL aswell as the GraphQL definitions
let @Mogge use the language of his choice (most likely js/node) since c++ seem to have limited support for graphql (besides the elevated implementation effort)

Why do we do this (Goals)

Backend tests and an unified interface for them
Modern and consistent API with GraphQL
Separate Front- from Backend
Remove PHP as language from the project
Have a chance to restructure the project and implement standards (jwt, graphql, nginx webserver, ...)

Closing this for now, please reopen if there is disagreement on the posted conclusion.


[USMON-358] postgres monitoring

What does this PR do?
Add initial and simple support for USM to capture postgres traffic.
USM is now able to capture plaintext simple postgres queries, and report the operation (select, insert, update, drop, create table) and the table name, along with latency and request count.
The PR makes the initial ramp up around adding a new protocol to USM, and intentionally keeps the simplicity of tracked queries.
In a series of following PR will add support to more complicated queries, more postgres scenarios, add postgres-TLS support, and more.

Motivation
USM's roadmap is to expand to new protocols, especially DB protocols.

Additional Notes

[x] Merge agent-payload PR
[x] Dogfooding
[x] Add UT suite

Possible Drawbacks / Trade-offs

Describe how to test/QA your changes

/merge

/merge


Removing a link-feed?

I wanted to remove a link-feed that was created while running through a tutorial, but there are no details on how to do that.
e.g.
>azsphere feed list
Listing all feeds.
Retrieved feeds:
--> [3369f0e1-dedf-49ec-a602-2aa98669fd61] 'Retail Azure Sphere OS'
--> [82bacf85-990d-4023-91c5-c6694a9fa5b4] 'Retail Evaluation Azure Sphere OS'
--> [409021f9-dac7-4a04-9b98-0dfa10760ee5] 'test-1'

I want to be able to remove the test-1 link-feed from my system. The same goes for device-groups and skus. I effectively would like to be able to wipe any configuration data setup during tutorials so that I can start clean but nothing in the documentation describes how.

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 16395218-fa75-bd42-ee22-d48eb25f61b2
Version Independent ID: 161af554-9e3c-550c-4b0f-792446b9decc
Content: Link the device to a feed - Azure Sphere
Content Source: AzureSphere/articles/deployment/link-to-feed.md
Product: azure-sphere
GitHub Login: @pennyo
Microsoft Alias: azurespheredocs

@Lnk2past  Thanks for the question! We are investigating and will update you shortly.

@Lnk2past In order to best address your question, could you provide us with the URL of the MS Doc that you were following, if any?

Hi @CHEEKATLAPRADEEP-MSFT & @AshokPeddakotla-MSFT, thank you for following up!
I was following this: https://docs.microsoft.com/en-us/azure-sphere/deployment/link-to-feed
and was also looking at the reference documentation: https://docs.microsoft.com/en-us/azure-sphere/reference/azsphere-feed
I am really new to all of this (Azure, Azure Sphere, IoT) so maybe I am missing something simple :)

@Lnk2past Thanks for the information. We are checking on this internally and will update you as earliest.

@Lnk2past Currently, there is no way to delete the feeds and cloud config once set. I suggest you, please create a feedback item on the UserVoice and upvote. All the feedback you share in these forums will be monitored and reviewed by the Microsoft engineering teams responsible for building Azure.

@AshokPeddakotla-MSFT please this is crucial capability. Removing feed from group as well as removing device from group. These capabilities should be provided no matter if they are stated UserVoice or not.


Rename omni.nim to omni-lang.nim and have a general omni compiler

This allows to have a single omni compiler, named omni, which compiles omni code to a shared library. This shared library can then be used however by hooking to its functions Omni_Constructor, Omni_Perform and Omni_Destructor.
OmniJIT, omnicollider, omnimax and omnipd would then be built as different projects on top of the omni compiler.
Things to do to make this happen:

Have a way to hook into the allocator. Perhaps, the alloc / free function could just be passed as function pointers as a first initilization step, or directly to Omni_Constructor (alloc) and Omni_Destructor (free). In this latter case (passing function pointers to constructor/destructor), no allocation functions would be passed to Omni_Perform, as no allocs should happen in the perform loop.
In nim, there would just be an opaque void* function pointer used for the allocs. This would be defaulted to malloc and free.

How to have a Buffer interface that works for any environment? SC and Max/PD have two completely different ways of dealing with them (addressing by input/buf number on server and addressing by name/string).
Perhaps, two standard Buffer interfaces could be provided. One that works with bufnum, supporting SC, and one working with string, supporting max and pd.

Fix: #28


New Version Notifications

Add support for checking for new versions from GitHub into the load process to notify the users when new versions are released.

Checked in on 2/2


Benchmarks

Pull Request Test Coverage Report for Build 7c04d7cefc0ffd27cb2cf58bf2157908be6647dc-PR-194

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 83.829%

Totals

Change from base Build 2d06fcfb9d568cf40d40f27a10be98534cf6e963:
0.0%

Covered Lines:
3805

Relevant Lines:
4539

💛  - Coveralls


Support aliases for qbraid_qir.qasm3.qasm3_to_qir

Resolve #78
Changes

qbraid_qir.qasm3.qasm3_to_qir now supports openqasm3.ast.AliasStatement
Supports aliasing quantum register or indexed quantum register
Note that an alias for the concatenated register has yet to be supported, but it might be better to work on separate PR since it can be complicated. (e.g. Identifier + Identifier, Identifier + IndexExpression, AliasStatement + IndexExpression etc.)

@king-p3nguin Thanks for the PR, at first glance these updates look great!
@TheGupta2012 will take a closer look and review.
Also sorry about the formatting workflow thing, seems to be a small bug. Just ignore it.

Hi @king-p3nguin , was checking in to make sure you got the review comments. All the best for the remaining hack!

Sorry for the delay. Once I figure out the problem with the scope of the alias, it should be ready for review.

Hey, thanks for the updates @king-p3nguin. Just so you don't miss the unitary hack timelines, you can push the final changes (even though a little buggy) and open a follow-up issue to solve the scope bug.
Note that you'll also have to rebase on top of main as another PR was recently merged.

Hi @TheGupta2012, I added self._label_scope_level and self._curr_scope so that the scope of the alias is also considered when using the alias.

Thank you for reviewing the code! I will check the follow-up issue and send the pull request if I can fix it.