opening an exclusive window on hyprland crashes it [BUG]

Checklist before submitting an issue

[X] I have searched through the existing closed and open issues for eww and made sure this is not a duplicate
[X] I have specifically verified that this bug is not a common user error
[X] I am providing as much relevant information as I am able to in this bug report (Minimal config to reproduce the issue for example, if applicable)

Description of the bug
My configuration is rather simple.
(defwindow bar
           :monitor 0
           :geometry (geometry :x "0%"
                               :y "97.5%"
                               :width "100%"
                               :height "2.5%"
                               :anchor "top center")
           :stacking "fg"
           :exclusive true
           :namespace "eww_bar"
  "wyli")

a simple what should be bar that takes up the bottom strip of the screen.
However, when I run this on hyprland, this first resets the screen so that I can only see the wall paper and the bar at the bottom. And then upon further interaction (when i attempt to spawn a kitty terminal with a keybind) crashes hyprland and sends me back to sddm's login screen.
This does not occur when it is set as :exclusive false
In plasma's wayland variant. this works as expected and there is a bar that can also be focused on.
furthermore, eww log only shows this.

Reproducing the issue
On endeavour os using the linux zen kernel 6.2.10-zen1-1-zen
build eww using the wayland feature flag
cargo build --release --no-default-features --features=wayland
set your ~/.config/eww.yuck as
(defwindow bar
           :monitor 0
           :geometry (geometry :x "0%"
                               :y "97.5%"
                               :width "100%"
                               :height "2.5%"
                               :anchor "top center")
           :stacking "fg"
           :exclusive true
           :namespace "eww_bar"
  "wyli")

and clear eww.scc
start the eww daemon
eww daemon
open the bar
eww open bar
Expected behaviour
For Hyprland to not remove all windows and then crash when opening an eww window and provide exclusive space to the bar.
Additional context
neofetch for additional system information:

the bar:

I also forgot to mention the additional debug logs if that may help
(eww:233501): Gtk-WARNING **: 23:05:40.596: Theme parsing error: gtk.css:1649:16: '-gtk-icon-size' is not a valid property name

(eww:233501): Gtk-WARNING **: 23:05:40.596: Theme parsing error: gtk.css:1652:16: '-gtk-icon-size' is not a valid property name
 2023-04-29T15:05:40.610Z DEBUG eww::server > Initializing script var handler
 2023-04-29T15:05:40.628Z INFO  eww::ipc_server > IPC server initialized
 2023-04-29T15:05:41.928Z DEBUG eww::ipc_server > received command from IPC: Ping
 2023-04-29T15:05:41.928Z DEBUG eww::ipc_server > Waiting for response for IPC client
 2023-04-29T15:05:41.928Z DEBUG eww::app        > Handling event: NoOp
 2023-04-29T15:05:41.928Z DEBUG eww::ipc_server > received command from IPC: OpenWindow { window_name: "bar", screen: None, pos: None, size: None, anchor: None, should_toggle: false }
 2023-04-29T15:05:41.929Z DEBUG eww::ipc_server > Waiting for response for IPC client
 2023-04-29T15:05:41.929Z DEBUG eww::app        > Handling event: OpenWindow { window_name: "bar", pos: None, size: None, anchor: None, screen: None, should_toggle: false, sender: DaemonResponseSender(UnboundedSender { chan: Tx { inner: Chan { tx: Tx { block_tail: 0x7fe7d8001570, tail_position: 0 }, semaphore: Semaphore(0), rx_waker: AtomicWaker, tx_count: 1, rx_fields: "..." } } }) }
 2023-04-29T15:05:41.929Z INFO  eww::app        > Opening window bar
Gdk-Message: 23:06:11.909: Error reading events from display: Broken pipe

Hyprland crashes after
2023-04-29T15:05:41.929Z INFO  eww::app        > Opening window bar
furthermore, the exact signal given is
fish: Job 1, 'Hyprland' terminated by signal SIGABRT (Abort)play error: Connection reset by peer_Tp&, const _Tp&) with [_Tp = double]: Assertion \!(__hi < __lo)` falied.

@vaxerski, I assume this is more of a hyprland issue than an eww issue 🤔

You've got the nerve to say my software has issues 😤


Convert changelog to style used by catkin for releases.

This change is needed for catkin_prepare_release and catkin_generate_changelog. It matches other repos like rqt_plot.


Istio installation missing add-ons

As part of latest Istio release installation via HELM, i am not seeing the adds(grafana, Kiali etc) even though i have enabled them using --set option
Expected to see all addon that I defined as part of installation
1.)helm install istio /root/istio-setup/istio-1.1.2/install/kubernetes/helm/istio --namespace istio-system --set grafana.enabled=true --set grafana.service.type=LoadBalancer --set kiali.enabled=true --set tracing.enabled=true --set tracing.service.type=LoadBalancer --tls
Version (include the output of istioctl version --remote and kubectl version)
Kuberntes v1.12.7
Helm v2.12.3
Istio 1.1.2
How was Istio installed?
HELM
Environment where bug was observed (cloud vendor, OS, etc)
VMware PKS
Additionally, please consider attaching a cluster state archive by attaching
the dump file to this issue.

What do you mean when you say "I am not seeing the addons". Are you not seeing the pods installed/running in the istio-system namespace? Or are you not seeing them in your browser (i.e. their GUIs are not exposed)?
To see if the pods are actually installed/running:
kubectl get pods -n istio-system
and see what you have - do you see the grafana and kiali pods running?
IIRC, recently the gateways were removed, so I'm not sure the add-ons are externally exposed to browsers out of the box anymore. You might have to do that yourself now. See these, I think they are related:

PR https://github.com/istio/istio/pull/12309
Issue https://github.com/istio/istio/issues/12301

Yes, I am not seeing the pods installed/running in istio-system namespace.
kubectl get pods -n istio-system
==> v1/Pod(related)
NAME                                    READY  STATUS   RESTARTS  AGE
istio-galley-787758f7b8-nq6wz           1/1    Running  0         24h
istio-ingressgateway-58c77897cc-cpxll   1/1    Running  0         24h
istio-egressgateway-88887488d-zg9zf     1/1    Running  0         24h
istio-telemetry-7fb48dc68b-zn6xs        2/2    Running  0         24h
istio-policy-56c4579578-ct9wn           2/2    Running  0         24h
istio-pilot-868cdfb5f7-98957            2/2    Running  0         24h
prometheus-76db5fddd5-6j7l6             1/1    Running  0         24h
istio-citadel-7dd558dcf-fgltt           1/1    Running  0         24h
istio-sidecar-injector-d7f98d9cb-8gszw  1/1    Running  0         24h

I did try an install to my IBM cloud cluster of 1.1.2 using the `--set``'s and things worked.

Good to hear that its working for you.
For me its not working though.
I tried in a different way, by install istio 1.0.6 first which got installed successfully and
then tried upgrading  to istio 1.1.3 but got below error.
[root@linuxhost1 istio-1.1.3]# (Kubernetes-prod) helm upgrade istio /root/istio-setup/istio-1.1.3/install/kubernetes/helm/istio --values /root/istio-setup/istio-1.1.3/install/kubernetes/helm/istio/values-istio-demo.yaml --tls
Error: UPGRADE FAILED: no PodDisruptionBudget with the name "istio-galley" found
Can i get some help with this.

Resolved this issue  by manually deleting all PodDisruptionBudget resources in istio-system namespace and then attempted the upgrade which finally upgraded my istio to 1.1.0.


sometimes not rendering google ads same as dangerousinnerhtml

Hello i have this code
renderHTML("<script async src='//pagead2.googlesyndication.com/pagead/js/adsbygoogle.js'></script><ins class='adsbygoogle' style='display: inline-block; width: 300px; height: 250px;' data-ad-client='ca-pub-8115515276052071' data-ad-slot='7807585453'></ins><script>(adsbygoogle = window.adsbygoogle || []).push({});</script>")
but not always rendering.

Script tags aren't properly rendered in React. Please refer to the following SO threads.

https://stackoverflow.com/questions/34424845/adding-script-tag-to-react-jsx
https://stackoverflow.com/questions/31276926/how-to-add-script-tag-using-reactjs


NumPad Decimal Point not working

My PC current locale is 'es-US' and I have a numeric column with mask = "#,##.000" and decimal = ".", when I'm editing the cell, If I press the decimal key in the NumPad nothing happend, but if I press the same key "." in the typewriter keys it works.

That has been fixed on the Jexcel Pro distribution (https://jexcel.net/v7) and we would bring to the Ce distribution on the next release.

Thanks @paulhodel Is there an expected release date for it?

We still planning for that. If you subscribe the newsletter I can keep you informed. Meawhile, if you wish to test the Pro distribution for free and send you feedback would  be great.
Regards,

This has been included on the CE v4.4.1+
Regards,

Hi, I just updated jexcel and the issue persist :(

Hi, I've just updated and the issue persist :(

Hi @paulhodel could you reopen this issue? regards

I have suffered this issue, until now. (jSpreadsheet CE 4.6.0)

@cbeltrangomez84 The issue was solved after updating jsuite to the updated files https://github.com/jsuites/jsuites .

Thanks a lot @misol


Service registry RHOAS CLI

Updates to the Getting Started CLI guides

Creates three guides as follows:
-- Installing and configuring the rhoas CLI
-- Getting started with the rhoas CLI for OpenShift Streams for Apache Kafka
-- Getting started with the rhoas CLI for OpenShift Service Registry
Removes install steps from the getting tarted guides, replaced by prereq that goes to the new common _Install_guide
Updates links and attributes to reflect the new structure
Removes the Commands for... tables to replace with -h list and link to command reference guide
Pushes the Using procedures for Kafka Getting Started up a level (==) and removes the discrete title flag

🤩

🤩  @PaulRMellor How I can verify/render this - I'm aware of the quickstart procedure. How to run/verify tutorials?

@PaulRMellor Amazing work! This is not only looking very good it will also:

Remove content that was really hard for us to maintain and often get out of sync
Provide clear path for future services.

#tech-ack

While changes look good there are some build issues related to duplicated keys.
We need to add -cli suffix to them:

While changes look good there are some build issues related to duplicated keys. We need to add -cli suffix to them:

Doesn't the context make a difference? I've changed these two. :+1:

Doesn't the context make a difference? I've changed these two. 👍

Tooling validates if id's are not the same and fails. We need to try to be as specific as possible to avoid clashes.

DO we know what this means:
asciidoctor: ERROR: modules/guides/proc-creating-kafka-instance-cli.adoc: line 2: level 0 sections can only be used when doctype is book
asciidoctor: ERROR: modules/guides/proc-creating-service-registry-instance-cli.adoc: line 2: level 0 sections can only be used when doctype is book

@bibryam - Hi Bilgin. This PR has the Getting started with the rhoas CLI for OpenShift Service Registry (rhoas-cli-service-registry/readme.adoc) and a (now) separate Installing and configuring the rhoas CLI guide (rhoas-cli/readme.adoc)
Would appreciate a review.

@wtrocki  @PaulRMellor this look very good. Great job Wojciech!
A few notes bellow:

"This example switches to the my-registry instance that was previously created." - is this needed? If there is a single instance, can that be selected by default?

rhoas service-registry artifact create --type=AVRO --artifact-id=my-artifact avro-userInfo.json

Do we need to specify the type? I was expecting the type to be auto detected?

After a schema is updated, can we use the command for setting the compatability level and demonstrate that?

@EricWittmann is RBAC feature in prod? I see role assigment demonstrated here? That will require also docs to be available IMO

"This example switches to the my-registry instance that was previously created." - is this needed? If there is a single instance, can that be selected by default?

I have followed up pattern we have in Kafka thinking that this was intentional to show user how to switch, but it in fact seems redundant and counterintuitive.

rhoas service-registry artifact create --type=AVRO --artifact-id=my-artifact avro-userInfo.json

Do we need to specify the type? I was expecting the type to be auto detected?

Sadly we need to. Not sure why but the backend is not working well with AVRO schemas. It even has troubles with schemas that are provided in the service registry repository as examples:
https://github.com/Apicurio/apicurio-registry/tree/master/integration-tests/testsuite/src/test/resources/artifactTypes
This might be due to reliance on content type that comes from browser environment etc.?
We did not had issues with OpenAPI but for this guide we wanted to show Avro.

@EricWittmann is RBAC feature in prod? I see role assigment demonstrated here? That will require also docs to be available IMO

As solution for this I think we can have this step commented out for the moment and let team to uncomment it when this is there.

"This example switches to the my-registry instance that was previously created." - is this needed? If there is a single instance, can that be selected by default?

I have followed up pattern we have in Kafka thinking that this was intentional to show user how to switch, but it in fact seems redundant and counterintuitive. @PaulRMellor Do you think we can remove it?

[PAUL] I've removed as a step, but I think it's useful to point it out. Added as a note in prereqs.

rhoas service-registry artifact create --type=AVRO --artifact-id=my-artifact avro-userInfo.json
>
>
Do we need to specify the type? I was expecting the type to be auto detected?

Sadly we need to. Not sure why but the backend is not working well with AVRO schemas that are sent by CLI. It even has troubles with schemas that are provided in the service registry repository as examples:
https://github.com/Apicurio/apicurio-registry/tree/master/integration-tests/testsuite/src/test/resources/artifactTypes
This might be due to reliance on content type that comes from browser environment etc.? We did not had issues with OpenAPI but for this guide we wanted to show Avro.

@EricWittmann is RBAC feature in prod? I see role assigment demonstrated here? That will require also docs to be available IMO

As solution for this I think we can have this step commented out for the moment and let team to uncomment it when this is there.

[PAUL]  I've commented out the role creation step. We don't refer to role in the following tasks. Will we need it in the guide at all?

[PAUL] I've commented out the role creation step. We don't refer to role in the following tasks. Will we need it in the guide at all?

Yes.. That will be the only place in the docs that mention needs to apply separate role in service account.
Apart from that we going to also add that in software:
https://github.com/redhat-developer/app-services-cli/issues/1118

@bhardesty Good for docs review

I guess we good to merge?


Electricity demand is lower than production, but there is no import and there are no blackout hours

An external user drew our attending to some issues in this scenario.
The total demand for electricity is lower than the electricity production.
However, there is no import of electricity and there are 0 blackout hours. There is some export of electricity.
Adding a gas plant (for example Gas CCGT) does not result in extra electricity production even though according to the demand vs production there still is a deficit.
@jorisberkhout told this might be due to a small bug related to electricity demand input for Merit.

I went through each week in the "Electricity production per hour" chart, and can't find any period where supply fails to meet (or exceed) demand, so as far as Merit is concerned there are indeed no blackout hours. The HV network node has the same amount of energy entering as leaving. Is there evidence of a mismatch between supply and demand in ETEngine, or is it just in the ETModel front-end (e.g. charts) where we see the error?
If the latter, is it possible we're simply missing a source of electricity from the electricity_production group? Or something amiss in one of the electricity_produced_from_(carrier) queries?

Is there evidence of a mismatch between supply and demand in ETEngine, or is it just in the ETModel front-end (e.g. charts) where we see the error?

I've not yet looked into ETEngine. So as far as I know it's just in the ETModel front-end.

If the latter, is it possible we're simply missing a source of electricity from the electricity_production group? Or something amiss in one of the electricity_produced_from_(carrier) queries?

I'll look into this

@jorisberkhout thought this might be due to a small bug related to electricity demand input for Merit.

Merit is told that total electricity demand is 30.729 PJ, and Merit meets or exceeds demand at all times (total production of all Merit order participants is 37.754 PJ). The chart shows output of under 30PJ.

That's not to say it's definitely a chart or query issue, but it would certainly be my first guess.

That's not to say it's definitely a chart or query issue, but it would certainly be my first guess.

You're probably right, @antw . I have attached an Excel-file to this issue that shows the production of all converters in this scenario (loads.308620.xlsx, see Sheet 2). Would you have time to analyse this, @DorinevanderVlies . Maybe you can figure out which production is missing form the chart.

I found that agriculture_chp_engine_network_gas and industry_chp_combined_cycle_gas_power_fuelmix seem to be missing from the chart.
There is also something with biomass being coal being 0.467 PJ higher in the excel file than in the chart. Solid biomass on the other hand is 0.467 lower. The weird thing is that I cannot find coal attributes that can make up 0.467.
Furthermore green gas is 0.0098 PJ in the production chart, but there is no green gas in Excel.
The following shows my comparison of the ETM production chart and the Excel file from @jorisberkhout.
loads.308620 dv.xlsx

Good observations, @DorinevanderVlies ! I looked into this a bit more and found that not only are agriculture_chp_engine_network_gas and industry_chp_combined_cycle_gas_power_fuelmix missing from this chart, but if you query their electricity production in this specific scenario this returns 0 in both cases. My suspicion is that merit takes these converters into account, but afterwards their demands are set to 0 because the sectors they are in (agriculture and industry respectively) are excluded in this scaled scenario. What do you think about this suspicion, @antw ?

The other two observations are easier explained, @DorinevanderVlies .
In you Excel-analysis you labelled two cofiring converters as using just coal. These converters do, however, use 50% coal input and 50% solid biomass input. This explains why you see to little solid biomass consumption and to much coal consumption.
The green gas is a result of the fact that most gas-fired electricity producer use network_gas, which is a mixture of natural gas and green gas. The scenario has 0.4% green gas in the gas network which explains the 0.0098 PJ electricity production from green gas

My suspicion is that merit takes these converters into account, but afterwards their demands are set to 0 because the sectors they are in (agriculture and industry respectively) are excluded in this scaled scenario. What do you think about this suspicion, @antw ?

100% correct. Good catch.
For producers in the energy sector we'd set number of units to zero. This prevented their used in Merit. I've widened this to producers in all sectors:

The fix is now on beta; should we also apply it to production? I don't expect there to be any fallout.

Thanks for fixing this @antw !

The fix is now on beta; should we also apply it to production? I don't expect there to be any fallout.

I can imagine that there will be changes to the merit order results for some scaled scenario's now that electricity producers in the agriculture and industry sector are taken into account correctly. I do not know if this will cause any issues. I guess @DorinevanderVlies knows more about scaled scenario's. Could you decide whether this can be applied to production or needs some more testing, @DorinevanderVlies ?

Clever thinking @jorisberkhout. And good fix @antw.

Could you decide whether this can be applied to production or needs some more testing, @DorinevanderVlies?

Yes I will look into this. I'll try to do it today, but it will probably be after the weekend.

The fix is now on beta; should we also apply it to production? I don't expect there to be any fallout.

Let's do this first thing in January @antw! Our external user would like to use the current results on production for the coming week.

I looked into previously made local scenario's on the beta server and found no issues in them.
So, I think this fix can be applied to production.


Modify the read lilypond sequence

[x] increase/decrease tempo by fixed value
[x] increase/decrease tempo by specified value
[x] set tempo to specified value
[x] increase/decrease volume by fixed value
[x] increase/decrease volume by specified value
[ ] set volume to specified value
[ ] add swing
[ ] transpose
[ ] ...

Are the other ones in progress @scaredycode ?

#212 seems to be included in this ticket? I'm wondering @scaredycode

Are the other ones in progress @scaredycode ?

no, @yunlong-wang-cn and I decided against including anymore lilypond modification functionality.
I tested adding swing and transpositions some weeks ago, but this of course caused the parser to fail :)
Regarding setting volume to a specified value, I suggested adding commands such as "Play in fortissimo" or similar, but it is currently not implemented neither in the speech node nor in the behavior. We also thought that this might not be a use case a "usual" user would go for (more "Play x steps louder" might be much more intuitive).

@scaredycode
I close this because you moved this into "Done".


SupersetErrorType.ADHOC_SUBQUERY_NOT_ALLOWED_ERROR thrown for valid quoted column name

Bug description
I set up a bar chart X axis value to a column named 'Created on'.
When the chart data loads I get an error: "Custom SQL fields cannot contain sub-queries."
Sample chart SQL query: SELECT DATE_TRUNC('day', "Created on") AS "Created on", sum("Estimated savings / Month") AS "SUM(Estimated savings / Month)"  FROM public."Opportunities_4_userfriendly"  WHERE ("Status" NOT IN ('Dismissed', 'Completed')) GROUP BY DATE_TRUNC('day', "Created on")   LIMIT 50000;
In my case, choosing any other column containing the token 'on'  for the X axis, such as "Update on" will lead to the same error.
My guess is the bug originates from superset/models/helpers.py#validate_adhoc_subquery. The parser is likely incorrectly interpreting "Created on" as a table reference because of the word "on"
Screenshots/recordings

Superset version
master / latest-dev
Python version
3.9
Node version
16
Browser
Chrome
Additional context
No response
Checklist

[X] I have searched Superset docs and Slack and didn't find a solution to my problem.
[X] I have searched the GitHub issue tracker and didn't find a similar bug report.
[X] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

ALLOW_ADHOC_SUBQUERY

I appreciate your support +1
I was aware of the feature flag mentioned above.
However, using it is not acceptable for my use case. According to the changelog entry, the flag is turned off by default for security reasons

19242: Adhoc subqueries are now disabled by default for security reasons. To enable them, set the feature flag ALLOW_ADHOC_SUBQUERY to True.

I would appreciate if the maintainers would take this bug report into considerations, and maybe we will get a proper fix one day.

@dosu
Please consider my previous response, I don't think valid column names such as "Update on" should be flagged as a subquery to begin with.

However, using it is not acceptable for my use case. According to the changelog entry, the flag is turned off by default for security reasons
https://github.com/apache/superset/pull/19242: Adhoc subqueries are now disabled by default for security reasons. To enable them, set the feature flag ALLOW_ADHOC_SUBQUERY to True.

I have the same issue in TABLE chart in RAW RECORDS query mode for columns with a dot in their names - this showed up after upgrading from 4.0.2 to 4.1.1. Enabling "ALLOW_ADHOC_SUBQUERY": True resolved issue by now...

I have a query that also triggered the error.
create or replace view view_investors_payouts as
SELECT
  any_value(party.name) as "Имя инвестора",
  coalesce(abs(sum(case when monetary_delta_required_to_compensate_difference < 0 AND re_cf.currency_code = '₽' then monetary_delta_required_to_compensate_difference end)), 0) as "Мы должны ₽",
  coalesce(abs(sum(case when monetary_delta_required_to_compensate_difference > 0 AND re_cf.currency_code = '₽' then monetary_delta_required_to_compensate_difference end)), 0) as "Нам должны ₽",
  coalesce(abs(sum(case when           expected_monetary_delta_of_our_balance < 0 AND re_cf.currency_code = '₽' then expected_monetary_delta_of_our_balance           end)), 0) as "Ожидаемые расходы ₽",
  coalesce(abs(sum(case when           expected_monetary_delta_of_our_balance > 0 AND re_cf.currency_code = '₽' then expected_monetary_delta_of_our_balance           end)), 0) as "Ожидаемые доходы ₽",
  coalesce(abs(sum(case when               real_monetary_delta_of_our_balance < 0 AND re_cf.currency_code = '₽' then     real_monetary_delta_of_our_balance           end)), 0) as "Реальные расходы ₽",
  coalesce(abs(sum(case when               real_monetary_delta_of_our_balance > 0 AND re_cf.currency_code = '₽' then     real_monetary_delta_of_our_balance           end)), 0) as "Реальные доходы ₽",

  coalesce(abs(sum(case when re_cf.currency_code = '₽' then expected_monetary_delta_of_our_balance end)), 0) as "Ожидаемая дельта нашего баланса ₽",
  coalesce(abs(sum(case when re_cf.currency_code = '₽' then     real_monetary_delta_of_our_balance end)), 0) as "Реальная дельта нашего баланса ₽"

from view_real_and_expected_cash_flows as re_cf
join party_involved_in_deal using (deal_id)
join party using (party_id)
where reason_from_db in ('investment', 'profit_payouts')
group by party_id
;

I guess it doesn't like spaces inside the column names instead of disliking on.
Because as soon as I changed it to this:
create or replace view view_investors_payouts as
SELECT
  any_value(party.name) as investor_name,
  coalesce(abs(sum(case when monetary_delta_required_to_compensate_difference < 0 AND re_cf.currency_code = '₽' then monetary_delta_required_to_compensate_difference end)), 0) as we_owe_rubles,
  coalesce(abs(sum(case when monetary_delta_required_to_compensate_difference > 0 AND re_cf.currency_code = '₽' then monetary_delta_required_to_compensate_difference end)), 0) as they_owe_rubles,
  coalesce(abs(sum(case when           expected_monetary_delta_of_our_balance < 0 AND re_cf.currency_code = '₽' then expected_monetary_delta_of_our_balance           end)), 0) as expected_expenses_rubles,
  coalesce(abs(sum(case when           expected_monetary_delta_of_our_balance > 0 AND re_cf.currency_code = '₽' then expected_monetary_delta_of_our_balance           end)), 0) as expected_income_rubles,
  coalesce(abs(sum(case when               real_monetary_delta_of_our_balance < 0 AND re_cf.currency_code = '₽' then     real_monetary_delta_of_our_balance           end)), 0) as real_expenses_rubles,
  coalesce(abs(sum(case when               real_monetary_delta_of_our_balance > 0 AND re_cf.currency_code = '₽' then     real_monetary_delta_of_our_balance           end)), 0) as real_income_rubles,

  coalesce(abs(sum(case when re_cf.currency_code = '₽' then expected_monetary_delta_of_our_balance end)), 0) as expected_delta_to_our_balance_rubles,
  coalesce(abs(sum(case when re_cf.currency_code = '₽' then     real_monetary_delta_of_our_balance end)), 0) as real_delta_to_our_balance_rubles

from view_real_and_expected_cash_flows as re_cf
join party_involved_in_deal using (deal_id)
join party using (party_id)
where reason_from_db in ('investment', 'profit_payouts')
group by party_id
;

It started working flawlessly and doesn't require increasing potential attack surface, by enabling feature flag


Images not working at all.

I made this big blog post thing with a lot of images. However, when viewing the post on the server, I noticed none of the images were showing up. I'm quite new to Hugo (started today), so I don't know whether I'm doing something wrong or if there's an actual bug.
Also, I just noticed that on the github-uploaded version some of the images are showing up, while others are not. That's quite weird, too.
Here's the github link: https://github.com/stayinside4ever/stayinside4ever.github.io
(also, I know one of the images is named "a.jpg" and in the code there's "1_1.jpg" that doesn't exist, it was my attempt to change the name from "1_1" to "a" to see if the numbers were influencing anything, apparently they're not)
EDIT: forgot to mention, the post i'm talking about is the drawabox one, and all the images are stored in the folder by that name, too

my fault. the images that didn't work had the .JPG extension, while the working ones had .jpg. didn't know Hugo would recognize a difference, since Windows certainly doesn't.


extreme RAM Usage

Nach neustart wieder normal

Steht was in den logs?

Ähm. Ja. Bei https://github.com/copystring/ioBroker.roborock/issues/34 ist nichts weiter passiert.

Bitte entschuldige. Ich zieh gleich morgen das Log und lade es hier hoch

Habe das gleiche Problem.  Objekte werden auch nicht mehr upgedated. Sauger ist ein S7+

Nach einem restart ist es erstmal OK allerdings steigt die RAM Nutzung schnell wieder an:

Hier ein log nach restart des Adapters:
mirko@iobroker:~$ tail -f /opt/iobroker/log/iobroker.current.log |grep roborock

2023-02-02 15:50:38.847  - info: host.iobroker stopInstance system.adapter.roborock.0 (force=false, process=true)

2023-02-02 15:50:38.851  - info: roborock.0 (77838) Got terminate signal TERMINATE_YOURSELF

2023-02-02 15:50:38.853  - info: roborock.0 (77838) terminating

2023-02-02 15:50:38.854  - info: roborock.0 (77838) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

2023-02-02 15:50:39.007  - info: host.iobroker stopInstance system.adapter.roborock.0 send kill signal

2023-02-02 15:50:40.012  - info: host.iobroker stopInstance system.adapter.roborock.0 killing pid 77838

2023-02-02 15:50:40.323  - info: host.iobroker instance system.adapter.roborock.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)

2023-02-02 15:50:42.148  - info: host.iobroker instance system.adapter.roborock.0 started with pid 89295

2023-02-02 15:50:43.974  - info: roborock.0 (89295) starting. Version 0.0.6-alpha.0 (non-npm: copystring/ioBroker.roborock) in /opt/iobroker/node_modules/iobroker.roborock, node: v16.19.0, js-controller: 4.0.24

2023-02-02 15:50:44.177  - info: roborock.0 (89295) MQTT initialized

2023-02-02 15:51:23.345  - info: host.iobroker "system.adapter.roborock.0" disabled

2023-02-02 15:51:23.346  - info: host.iobroker stopInstance system.adapter.roborock.0 (force=false, process=true)

2023-02-02 15:51:23.360  - info: roborock.0 (89295) Got terminate signal TERMINATE_YOURSELF

2023-02-02 15:51:23.364  - info: roborock.0 (89295) terminating

2023-02-02 15:51:23.365  - info: roborock.0 (89295) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

2023-02-02 15:51:23.392  - info: host.iobroker stopInstance system.adapter.roborock.0 send kill signal

2023-02-02 15:51:23.954  - warn: roborock.0 (89295) get state error: Connection is closed.

2023-02-02 15:51:23.956  - error: roborock.0 (89295) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

2023-02-02 15:51:23.956  - error: roborock.0 (89295) unhandled promise rejection: DB closed

2023-02-02 15:51:23.956  - error: roborock.0 (89295) Error: DB closed

2023-02-02 15:51:23.956  - error: roborock.0 (89295) DB closed

2023-02-02 15:51:24.059  - info: host.iobroker instance system.adapter.roborock.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)

2023-02-02 15:52:43.193  - info: host.iobroker "system.adapter.roborock.0" enabled

2023-02-02 15:52:43.422  - info: host.iobroker instance system.adapter.roborock.0 started with pid 89332

2023-02-02 15:52:44.603  - info: roborock.0 (89332) starting. Version 0.0.6-alpha.0 (non-npm: copystring/ioBroker.roborock) in /opt/iobroker/node_modules/iobroker.roborock, node: v16.19.0, js-controller: 4.0.24

2023-02-02 15:52:44.827  - info: roborock.0 (89332) MQTT initialized

2023-02-02 15:54:25.755  - info: host.iobroker "system.adapter.roborock.0" disabled

2023-02-02 15:54:25.756  - info: host.iobroker stopInstance system.adapter.roborock.0 (force=false, process=true)

2023-02-02 15:54:25.769  - info: roborock.0 (89332) Got terminate signal TERMINATE_YOURSELF

2023-02-02 15:54:25.772  - info: roborock.0 (89332) terminating

2023-02-02 15:54:25.772  - info: roborock.0 (89332) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason

2023-02-02 15:54:25.800  - info: host.iobroker stopInstance system.adapter.roborock.0 send kill signal

2023-02-02 15:54:26.440  - warn: roborock.0 (89332) get state error: Connection is closed.

2023-02-02 15:54:26.441  - error: roborock.0 (89332) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

2023-02-02 15:54:26.441  - error: roborock.0 (89332) unhandled promise rejection: DB closed

2023-02-02 15:54:26.442  - error: roborock.0 (89332) Error: DB closed

2023-02-02 15:54:26.442  - error: roborock.0 (89332) DB closed

2023-02-02 15:54:26.533  - info: host.iobroker instance system.adapter.roborock.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)

Danke für das log. Leider steht dort nur, dass der Adapter abgeschossen wurde. Klar. Bei so RAM-Belegung ist das so. Es wäre nun zu schauen was dazu führt, dass so viel RAM belegt wird. Kommen denn Fehler vor dem Absturz?

Hier das Log vor dem Absturz:
Line 128802: 2023-01-30 21:27:49.521  - debug: roborock.0 (21442) getParameter: get_consumable
	Line 128803: 2023-01-30 21:27:49.521  - debug: roborock.0 (21442) getParameter: get_network_info
	Line 128804: 2023-01-30 21:27:49.521  - debug: roborock.0 (21442) getParameter: get_carpet_mode
	Line 128805: 2023-01-30 21:27:49.521  - debug: roborock.0 (21442) getParameter: get_carpet_clean_mode
	Line 128806: 2023-01-30 21:27:49.943  - debug: roborock.0 (21442) Requested new map
	Line 128807: 2023-01-30 21:27:50.943  - debug: roborock.0 (21442) Requested new map
	Line 128809: 2023-01-30 21:27:51.944  - debug: roborock.0 (21442) Requested new map
	Line 128810: 2023-01-30 21:27:52.944  - debug: roborock.0 (21442) Requested new map
	Line 128811: 2023-01-30 21:27:53.943  - debug: roborock.0 (21442) Requested new map
	Line 128812: 2023-01-30 21:27:54.943  - debug: roborock.0 (21442) Requested new map
	Line 128813: 2023-01-30 21:27:55.943  - debug: roborock.0 (21442) Requested new map
	Line 128814: 2023-01-30 21:27:56.943  - debug: roborock.0 (21442) Requested new map
	Line 128815: 2023-01-30 21:27:57.944  - debug: roborock.0 (21442) Requested new map
	Line 128816: 2023-01-30 21:27:58.945  - debug: roborock.0 (21442) Requested new map
	Line 128817: 2023-01-30 21:27:59.947  - debug: roborock.0 (21442) Requested new map
	Line 128818: 2023-01-30 21:28:00.947  - debug: roborock.0 (21442) Requested new map
	Line 128819: 2023-01-30 21:28:01.947  - debug: roborock.0 (21442) Requested new map
	Line 128820: 2023-01-30 21:28:02.947  - debug: roborock.0 (21442) Requested new map
	Line 128821: 2023-01-30 21:28:03.949  - debug: roborock.0 (21442) Requested new map
	Line 128822: 2023-01-30 21:28:04.949  - debug: roborock.0 (21442) Requested new map
	Line 128823: 2023-01-30 21:28:05.950  - debug: roborock.0 (21442) Requested new map
	Line 128824: 2023-01-30 21:28:06.951  - debug: roborock.0 (21442) Requested new map
	Line 128825: 2023-01-30 21:28:07.951  - debug: roborock.0 (21442) Requested new map
	Line 128826: 2023-01-30 21:28:08.953  - debug: roborock.0 (21442) Requested new map
	Line 128827: 2023-01-30 21:28:09.953  - debug: roborock.0 (21442) Requested new map
	Line 128828: 2023-01-30 21:28:10.955  - debug: roborock.0 (21442) Requested new map
	Line 128829: 2023-01-30 21:28:11.955  - debug: roborock.0 (21442) Requested new map
	Line 128830: 2023-01-30 21:28:12.955  - debug: roborock.0 (21442) Requested new map
	Line 128833: 2023-01-30 21:28:13.955  - debug: roborock.0 (21442) Requested new map
	Line 128834: 2023-01-30 21:28:14.956  - debug: roborock.0 (21442) Requested new map
	Line 128835: 2023-01-30 21:28:15.956  - debug: roborock.0 (21442) Requested new map
	Line 128836: 2023-01-30 21:28:16.957  - debug: roborock.0 (21442) Requested new map
	Line 128837: 2023-01-30 21:28:17.958  - debug: roborock.0 (21442) Requested new map
	Line 128838: 2023-01-30 21:28:18.958  - debug: roborock.0 (21442) Requested new map
	Line 128839: 2023-01-30 21:28:19.521  - debug: roborock.0 (21442) Latest data requested
	Line 128840: 2023-01-30 21:28:19.522  - debug: roborock.0 (21442) getParameter: get_status
	Line 128841: 2023-01-30 21:28:19.522  - debug: roborock.0 (21442) getParameter: get_water_box_custom_mode
	Line 128842: 2023-01-30 21:28:19.522  - debug: roborock.0 (21442) getParameter: get_consumable
	Line 128843: 2023-01-30 21:28:19.522  - debug: roborock.0 (21442) getParameter: get_network_info
	Line 128844: 2023-01-30 21:28:19.522  - debug: roborock.0 (21442) getParameter: get_carpet_mode
	Line 128845: 2023-01-30 21:28:19.523  - debug: roborock.0 (21442) getParameter: get_carpet_clean_mode
	Line 128846: 2023-01-30 21:28:19.959  - debug: roborock.0 (21442) Requested new map
	Line 128847: 2023-01-30 21:28:20.961  - debug: roborock.0 (21442) Requested new map
	Line 128848: 2023-01-30 21:28:21.963  - debug: roborock.0 (21442) Requested new map
	Line 128849: 2023-01-30 21:28:22.963  - debug: roborock.0 (21442) Requested new map
	Line 128850: 2023-01-30 21:28:23.964  - debug: roborock.0 (21442) Requested new map
	Line 128851: 2023-01-30 21:28:24.966  - debug: roborock.0 (21442) Requested new map
	Line 128852: 2023-01-30 21:28:25.967  - debug: roborock.0 (21442) Requested new map
	Line 128853: 2023-01-30 21:28:26.967  - debug: roborock.0 (21442) Requested new map
	Line 128854: 2023-01-30 21:28:27.967  - debug: roborock.0 (21442) Requested new map
	Line 128855: 2023-01-30 21:28:28.967  - debug: roborock.0 (21442) Requested new map
	Line 128856: 2023-01-30 21:28:29.967  - debug: roborock.0 (21442) Requested new map
	Line 128857: 2023-01-30 21:28:30.968  - debug: roborock.0 (21442) Requested new map
	Line 128858: 2023-01-30 21:28:31.967  - debug: roborock.0 (21442) Requested new map
	Line 128859: 2023-01-30 21:28:32.968  - debug: roborock.0 (21442) Requested new map
	Line 128860: 2023-01-30 21:28:33.968  - debug: roborock.0 (21442) Requested new map
	Line 128861: 2023-01-30 21:28:34.969  - debug: roborock.0 (21442) Requested new map
	Line 128862: 2023-01-30 21:28:35.970  - debug: roborock.0 (21442) Requested new map
	Line 128863: 2023-01-30 21:28:36.971  - debug: roborock.0 (21442) Requested new map
	Line 128864: 2023-01-30 21:28:37.973  - debug: roborock.0 (21442) Requested new map
	Line 128865: 2023-01-30 21:28:38.974  - debug: roborock.0 (21442) Requested new map
	Line 128866: 2023-01-30 21:28:39.975  - debug: roborock.0 (21442) Requested new map
	Line 128867: 2023-01-30 21:28:40.977  - debug: roborock.0 (21442) Requested new map
	Line 128868: 2023-01-30 21:28:41.652  - info: host.iobroker stopInstance system.adapter.roborock.0 (force=false, process=true)
	Line 128869: 2023-01-30 21:28:41.655  - info: roborock.0 (21442) Got terminate signal TERMINATE_YOURSELF
	Line 128870: 2023-01-30 21:28:41.655  - info: roborock.0 (21442) terminating
	Line 128871: 2023-01-30 21:28:41.655  - info: roborock.0 (21442) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
	Line 128872: 2023-01-30 21:28:41.700  - info: host.iobroker stopInstance system.adapter.roborock.0 send kill signal
	Line 128873: 2023-01-30 21:28:41.977  - debug: roborock.0 (21442) Requested new map
	Line 128874: 2023-01-30 21:28:42.701  - info: host.iobroker stopInstance system.adapter.roborock.0 killing pid 21442
	Line 128875: 2023-01-30 21:28:42.892  - info: host.iobroker instance system.adapter.roborock.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
	Line 128876: 2023-01-30 21:28:44.856  - info: host.iobroker instance system.adapter.roborock.0 started with pid 38022
	Line 128877: 2023-01-30 21:28:46.092  - info: roborock.0 (38022) starting. Version 0.0.6-alpha.0 (non-npm: copystring/ioBroker.roborock) in /opt/iobroker/node_modules/iobroker.roborock, node: v16.19.0, js-controller: 4.0.24
	Line 128877: 2023-01-30 21:28:46.092  - info: roborock.0 (38022) starting. Version 0.0.6-alpha.0 (non-npm: copystring/ioBroker.roborock) in /opt/iobroker/node_modules/iobroker.roborock, node: v16.19.0, js-controller: 4.0.24
	Line 128877: 2023-01-30 21:28:46.092  - info: roborock.0 (38022) starting. Version 0.0.6-alpha.0 (non-npm: copystring/ioBroker.roborock) in /opt/iobroker/node_modules/iobroker.roborock, node: v16.19.0, js-controller: 4.0.24
	Line 128878: 2023-01-30 21:28:46.271  - info: roborock.0 (38022) MQTT initialized
	Line 128890: 2023-01-30 21:30:58.660  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 128893: 2023-01-30 21:32:26.677  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 129022: 2023-01-30 21:53:48.892  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 129080: 2023-01-30 22:03:27.186  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 129091: 2023-01-30 22:06:23.284  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 129094: 2023-01-30 22:07:51.301  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 129097: 2023-01-30 22:09:19.986  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 129195: 2023-01-30 22:34:28.548  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 129268: 2023-01-30 22:48:31.139  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 129292: 2023-01-30 22:55:51.912  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 129305: 2023-01-30 23:00:21.830  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 129374: 2023-01-30 23:26:53.102  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 129400: 2023-01-30 23:36:30.918  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 129441: 2023-01-30 23:54:57.488  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 129448: 2023-01-30 23:56:25.489  - error: roborock.0 (38022) Failed to creating canvas: retry
Line 1088: 2023-01-31 00:06:04.154  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1104: 2023-01-31 00:10:28.200  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1107: 2023-01-31 00:11:56.216  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1120: 2023-01-31 00:20:07.443  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1145: 2023-01-31 00:31:54.366  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1169: 2023-01-31 00:41:30.286  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1179: 2023-01-31 00:44:26.317  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1180: 2023-01-31 00:45:54.989  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1197: 2023-01-31 00:50:24.905  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1198: 2023-01-31 00:51:08.458  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1205: 2023-01-31 00:54:04.738  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1232: 2023-01-31 01:02:55.424  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1238: 2023-01-31 01:06:39.121  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1254: 2023-01-31 01:15:27.328  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1266: 2023-01-31 01:22:09.744  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1276: 2023-01-31 01:25:05.894  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1310: 2023-01-31 01:36:56.691  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1323: 2023-01-31 01:43:32.612  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1349: 2023-01-31 01:52:27.278  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1353: 2023-01-31 01:54:39.104  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1377: 2023-01-31 02:04:57.811  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1383: 2023-01-31 02:07:57.717  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1392: 2023-01-31 02:11:37.575  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1395: 2023-01-31 02:14:33.600  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1402: 2023-01-31 02:17:29.625  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1407: 2023-01-31 02:20:28.272  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1459: 2023-01-31 02:33:00.069  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1504: 2023-01-31 02:48:30.712  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1519: 2023-01-31 02:55:13.008  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1535: 2023-01-31 03:01:05.473  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1542: 2023-01-31 03:04:01.484  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1554: 2023-01-31 03:10:43.730  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1558: 2023-01-31 03:13:39.947  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 1585: 2023-01-31 03:27:00.672  - error: roborock.0 (38022) Failed to creating canvas: retry

Ab 3:27Uhr nichts mehr im Log bis 17:43
Line 4972: 2023-02-01 17:43:13.798  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 7648: 2023-02-01 18:38:37.824  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 7655: 2023-02-01 18:40:05.862  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 10475: 2023-02-01 19:00:02.801  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 10650: 2023-02-01 19:01:32.128  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 10770: 2023-02-01 19:03:02.036  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 11350: 2023-02-01 19:06:45.533  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 12628: 2023-02-01 19:11:10.051  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 15282: 2023-02-01 19:28:09.815  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 16157: 2023-02-01 19:34:02.194  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 17480: 2023-02-01 19:43:45.227  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 22412: 2023-02-01 20:17:46.745  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 25371: 2023-02-01 20:37:45.761  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 26926: 2023-02-01 20:48:02.791  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 28398: 2023-02-01 20:59:11.012  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 29144: 2023-02-01 21:03:35.205  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 29547: 2023-02-01 21:06:32.334  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 30408: 2023-02-01 21:12:32.049  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 33005: 2023-02-01 21:30:16.278  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 35007: 2023-02-01 21:45:02.617  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 36035: 2023-02-01 21:51:46.249  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 37953: 2023-02-01 22:03:35.362  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 38805: 2023-02-01 22:09:33.243  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 39497: 2023-02-01 22:14:47.217  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 39787: 2023-02-01 22:17:02.517  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 39958: 2023-02-01 22:17:46.276  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 40075: 2023-02-01 22:18:32.599  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 40656: 2023-02-01 22:22:12.917  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 40887: 2023-02-01 22:25:09.812  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 42075: 2023-02-01 22:32:32.925  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 43810: 2023-02-01 22:45:16.924  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 44384: 2023-02-01 22:48:13.600  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 45527: 2023-02-01 22:57:05.493  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 48386: 2023-02-01 23:17:08.797  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 48954: 2023-02-01 23:20:06.183  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 49481: 2023-02-01 23:23:04.468  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 51130: 2023-02-01 23:33:34.369  - error: roborock.0 (38022) Failed to creating canvas: retry
	Line 52108: 2023-02-01 23:40:15.010  - error: roborock.0 (38022) Failed to creating canvas: retry

Hier noch der Rest von heute mit meinen restarts
Line 336: 2023-02-02 00:00:20.126  - info: host.iobroker stopInstance system.adapter.roborock.0 (force=false, process=true)
	Line 1009: 2023-02-02 00:00:27.891  - warn: host.iobroker instance system.adapter.roborock.0 terminated due to SIGKILL
	Line 1010: 2023-02-02 00:00:27.891  - info: host.iobroker instance system.adapter.roborock.0 terminated with code null ()
	Line 2830: 2023-02-02 00:00:28.409  - info: host.iobroker stopInstance system.adapter.roborock.0 send kill signal
	Line 4235: 2023-02-02 00:04:19.079  - info: host.iobroker instance system.adapter.roborock.0 started with pid 77838
	Line 4236: 2023-02-02 00:04:20.165  - info: roborock.0 (77838) starting. Version 0.0.6-alpha.0 (non-npm: copystring/ioBroker.roborock) in /opt/iobroker/node_modules/iobroker.roborock, node: v16.19.0, js-controller: 4.0.24
	Line 4237: 2023-02-02 00:04:20.349  - info: roborock.0 (77838) MQTT initialized
	Line 5284: 2023-02-02 00:12:22.736  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 5311: 2023-02-02 00:23:28.085  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 5349: 2023-02-02 00:38:58.666  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 5387: 2023-02-02 00:51:33.077  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 5423: 2023-02-02 01:04:07.644  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 5469: 2023-02-02 01:28:26.540  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 5490: 2023-02-02 01:38:04.928  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 5495: 2023-02-02 01:39:32.936  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 5512: 2023-02-02 01:46:55.507  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 5529: 2023-02-02 01:53:35.454  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 5534: 2023-02-02 01:55:03.469  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 5551: 2023-02-02 02:03:56.286  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 5558: 2023-02-02 02:05:26.115  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 5576: 2023-02-02 02:17:56.686  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 5599: 2023-02-02 02:29:00.381  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 5633: 2023-02-02 02:31:57.053  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 5638: 2023-02-02 02:33:27.017  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 5652: 2023-02-02 02:38:38.744  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 5654: 2023-02-02 02:40:06.756  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 5661: 2023-02-02 02:43:02.810  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 5682: 2023-02-02 02:48:57.400  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 5691: 2023-02-02 02:52:41.079  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 5717: 2023-02-02 03:07:28.050  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 5722: 2023-02-02 03:09:39.906  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 5732: 2023-02-02 03:14:03.912  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 5742: 2023-02-02 03:21:28.568  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 5752: 2023-02-02 03:22:58.450  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 5763: 2023-02-02 03:29:34.276  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 6787: 2023-02-02 03:36:59.006  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 7764: 2023-02-02 03:44:29.345  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 9067: 2023-02-02 03:52:37.179  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 9752: 2023-02-02 03:57:01.229  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 10902: 2023-02-02 04:05:11.871  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 12317: 2023-02-02 04:15:29.856  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 12487: 2023-02-02 04:16:59.763  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 16750: 2023-02-02 04:46:30.789  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 17160: 2023-02-02 04:49:30.728  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 24257: 2023-02-02 05:39:42.314  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 26252: 2023-02-02 05:53:45.034  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 27103: 2023-02-02 05:59:37.079  - error: roborock.0 (77838) Failed to creating canvas: retry
	Line 80115: 2023-02-02 15:50:38.847  - info: host.iobroker stopInstance system.adapter.roborock.0 (force=false, process=true)
	Line 80116: 2023-02-02 15:50:38.851  - info: roborock.0 (77838) Got terminate signal TERMINATE_YOURSELF
	Line 80117: 2023-02-02 15:50:38.853  - info: roborock.0 (77838) terminating
	Line 80118: 2023-02-02 15:50:38.854  - info: roborock.0 (77838) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
	Line 80119: 2023-02-02 15:50:39.007  - info: host.iobroker stopInstance system.adapter.roborock.0 send kill signal
	Line 80120: 2023-02-02 15:50:40.012  - info: host.iobroker stopInstance system.adapter.roborock.0 killing pid 77838
	Line 80121: 2023-02-02 15:50:40.323  - info: host.iobroker instance system.adapter.roborock.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
	Line 80122: 2023-02-02 15:50:42.148  - info: host.iobroker instance system.adapter.roborock.0 started with pid 89295
	Line 80125: 2023-02-02 15:50:43.974  - info: roborock.0 (89295) starting. Version 0.0.6-alpha.0 (non-npm: copystring/ioBroker.roborock) in /opt/iobroker/node_modules/iobroker.roborock, node: v16.19.0, js-controller: 4.0.24
	Line 80126: 2023-02-02 15:50:44.177  - info: roborock.0 (89295) MQTT initialized
	Line 80137: 2023-02-02 15:51:23.345  - info: host.iobroker "system.adapter.roborock.0" disabled
	Line 80138: 2023-02-02 15:51:23.346  - info: host.iobroker stopInstance system.adapter.roborock.0 (force=false, process=true)
	Line 80139: 2023-02-02 15:51:23.360  - info: roborock.0 (89295) Got terminate signal TERMINATE_YOURSELF
	Line 80140: 2023-02-02 15:51:23.364  - info: roborock.0 (89295) terminating
	Line 80141: 2023-02-02 15:51:23.365  - info: roborock.0 (89295) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
	Line 80142: 2023-02-02 15:51:23.392  - info: host.iobroker stopInstance system.adapter.roborock.0 send kill signal
	Line 80143: 2023-02-02 15:51:23.954  - warn: roborock.0 (89295) get state error: Connection is closed.
	Line 80144: 2023-02-02 15:51:23.956  - error: roborock.0 (89295) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
	Line 80145: 2023-02-02 15:51:23.956  - error: roborock.0 (89295) unhandled promise rejection: DB closed
	Line 80146: 2023-02-02 15:51:23.956  - error: roborock.0 (89295) Error: DB closed
	Line 80152: 2023-02-02 15:51:23.956  - error: roborock.0 (89295) DB closed
	Line 80153: 2023-02-02 15:51:24.059  - info: host.iobroker instance system.adapter.roborock.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)
	Line 80164: 2023-02-02 15:52:43.193  - info: host.iobroker "system.adapter.roborock.0" enabled
	Line 80165: 2023-02-02 15:52:43.422  - info: host.iobroker instance system.adapter.roborock.0 started with pid 89332
	Line 80166: 2023-02-02 15:52:44.603  - info: roborock.0 (89332) starting. Version 0.0.6-alpha.0 (non-npm: copystring/ioBroker.roborock) in /opt/iobroker/node_modules/iobroker.roborock, node: v16.19.0, js-controller: 4.0.24
	Line 80167: 2023-02-02 15:52:44.827  - info: roborock.0 (89332) MQTT initialized
	Line 80176: 2023-02-02 15:54:25.755  - info: host.iobroker "system.adapter.roborock.0" disabled
	Line 80177: 2023-02-02 15:54:25.756  - info: host.iobroker stopInstance system.adapter.roborock.0 (force=false, process=true)
	Line 80178: 2023-02-02 15:54:25.769  - info: roborock.0 (89332) Got terminate signal TERMINATE_YOURSELF
	Line 80179: 2023-02-02 15:54:25.772  - info: roborock.0 (89332) terminating
	Line 80180: 2023-02-02 15:54:25.772  - info: roborock.0 (89332) Terminated (ADAPTER_REQUESTED_TERMINATION): Without reason
	Line 80181: 2023-02-02 15:54:25.800  - info: host.iobroker stopInstance system.adapter.roborock.0 send kill signal
	Line 80182: 2023-02-02 15:54:26.440  - warn: roborock.0 (89332) get state error: Connection is closed.
	Line 80183: 2023-02-02 15:54:26.441  - error: roborock.0 (89332) Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().
	Line 80184: 2023-02-02 15:54:26.441  - error: roborock.0 (89332) unhandled promise rejection: DB closed
	Line 80185: 2023-02-02 15:54:26.442  - error: roborock.0 (89332) Error: DB closed
	Line 80191: 2023-02-02 15:54:26.442  - error: roborock.0 (89332) DB closed
	Line 80192: 2023-02-02 15:54:26.533  - info: host.iobroker instance system.adapter.roborock.0 terminated with code 11 (ADAPTER_REQUESTED_TERMINATION)

Hoffe das hilft dir.

Wenn das passiert ist eine Karte in der App zu sehen?

Kann dir nur sagen das unmittelbar bar nach stoppen des Adapters die Karte in der App war. Als der Adapter hing habe ich die App nicht kontrolliert.

Wie voll sollte der RAM sein? dann zieh ich an der Stelle das Log-File ab

Wie voll sollte der RAM sein? dann zieh ich an der Stelle das Log-File ab

Deutlich unter 1 GB. So 500-600mb stehen bei mir wobei ich überrascht bin, dass das so viel ist aber darum muss ich mich später kümmern.

Habe jetzt die Version von hier installiert: https://github.com/copystring/ioBroker.roborock/issues/50#issuecomment-1416355177
RAM nach neustart 72MB, ohne Nutzung des Roboters scheint es zwischen 73-75 zu Pendeln.
Werde weiter beobachten wenn der Sauger mal einen Einsatz hatte.

Hi,
so der Sauger ist gefahren. 2x und die RAM Nutzung ist angestiegen:

Geht nach beenden des Saugvorganges auch nicht wieder runter.
Es hilft nur ein Instanz neustart:

Musst du noch irgendwelche logs dazu haben?

Moin. 120 MB find ich ja okay für das was gemacht wird. Wir hatten davor ja teilweise mehrere GB (z.B. 8Gb). Wenn es nicht wesentlich mehr also 120mb wird sehe ich hier keinen Handlungsbedarf.

Wenn es dabei bleibt ist es OK.
Wie sieht es beim Issue Ersteller aus?

Bei mir sieht es auf Version 0.0.7 gut aus. aktuell läuft er seit ca 8 Uhr mit 1 Reinigung und ist bei 262 MB. Zwischendrin war er mal bei 350 MB was ich vertretbar finde.


magicdrop refactor and contract factory

setup foundry
add contract factory
various refactors for code quality and file structure

hardhat tests passing

Inheritance graph looking knee-ice

piggybacking on @raymond-me 's via-ir -> This will affect static analysis as well. So some tooling (slither security tool) may have issues with via-ir

Possibly unrelated, because it does not seem to be part of the changes, but when I run hardhat tests I get an "unable to estimate gas" error on this line
https://github.com/me-foundation/magicdrop/blob/757d3c502172fdba7139ec3490dc85ede07b28bf/test/erc1155m/ERC1155M.test.ts#L70
When I override the gasLimit to something like 3_000_000 I get a "reverted with custom error Unauthorized" coming from Ownable for setDefaultRoyalty
    Error: VM Exception while processing transaction: reverted with custom error 'Unauthorized()'
    at ERC1155M._checkOwner (solady/src/auth/Ownable.sol:162)
    at ERC1155M.onlyOwner (solady/src/auth/Ownable.sol:279)
    at ERC1155M.setDefaultRoyalty (contracts/nft/erc1155m/ERC1155M.sol:284)
    at ERC1155M.constructor (contracts/nft/erc1155m/ERC1155M.sol:72)

can you help fix the CI?


Change sections and segments services

When segments are created, the corresponding section is updated
Adjusted section and segments schemas
Other small fixes

still need to:

properly delete segments from sections and volunteers
properly update segments when the section changes


"taskset" ignored by Seastar applications

Seastar applications by default create a thread on each of the machine's CPUs. However, Linux provides a mechanism for limiting a child process to only a subset of the CPUs (see taskset(1) and sched_setaffinity(2)), but Seastar silently ignores it.
For example, on a 4-cpu machine, if someone runs:
    taskset -c 0,1 some_seastar_program

Thinking the Seastar program will be limited only to these two CPUs, he'll be mistaken.
Seastar does provide options to override the default of taking over all the cpus (-c and --cpuset), but it's still confusing that "taskset" is silently ignored. I think we have two options to fix it:

Respect the CPU set returned by sched_getaffinity(2), and only use a subset of it.
At least warn that one or more of the CPUs we've picked to run on is not in sched_getaffinity(2) - which will let the user realize his "taskset" attempt is being ignored.

seastar applications have --cpuset flag that allows setting cpus - so we
support it internally
On Wed, Sep 16, 2015 at 10:39 AM, nyh<EMAIL_ADDRESS>wrote:

Seastar applications by default create a thread on each of the machine's
CPUs. However, Linux provides a mechanism for limiting a child process to
only a subset of the CPUs (see taskset(1) and sched_setaffinity(2)), but
Seastar silently ignores it.
For example, on a 4-cpu machine, if someone runs:
taskset -c 0,1 some_seastar_program

Thinking the Seastar program will be limited only to these two CPUs, he'll
be mistaken.
Seastar does provide options to override the default of taking over all
the cpus (-c and --cpuset), but it's still confusing that "taskset" is
silently ignored. I think we have two options to fix it:

Respect the CPU set returned by sched_getaffinity(2), and only use
a subset of it.
At least warn that one or more of the CPUs we've picked to run on
is not in sched_getaffinity(2) - which will let the user realize his
"taskset" attempt is being ignored.

—
Reply to this email directly or view it on GitHub
https://github.com/cloudius-systems/seastar/issues/56.

On Wed, Sep 16, 2015 at 10:54 AM, slivne<EMAIL_ADDRESS>wrote:

seastar applications have --cpuset flag that allows setting cpus - so we
support it internally

Please read my bug report. I know about the "cpuset" flag, and mentioned it
in the bug report, but before I noticed it (when Avi pointed it out to me),
I incorrectly assumed that "taskset" was being respected, which it wasn't.
I'm not saying it's a super-important or urgent, but I do think that
silently ignoring "taskset" is a bug, not a feature.


Can the Docker version support linux/arm64/v8

Can the Docker version support Linux/arm64/v8 platform。
ERROR：
WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
exec /app/entrypoint.sh: exec format error

I'm afraid that's unlikely. In my own experience, I had to manually install it on my Raspberry Pi without relying on Docker or any virtualization software. It appears that the root of the issue lies with the '/app/entrypoint.sh' file, which doesn't seem to be compatible with the arm64 architecture.


typo: Double word "of"

@nschonni : Thanks for your contribution! The author, @ghogen, has been notified to review your proposed change.

#sign-off


joystick: use long controller

Puts more longcontrol behavior in the loop, such as PID gains, long control states like stopping/starting, prevent_overshoot
Bolt with joystick before this is smooth as we can modulate the accel smoothly, however the PID gains make it much more unstable which we should hit with joystick mode

mostly feels like the old joystick now with the missing long deadzone added. not sure what the point is any more


⚠ Bofrost.at has degraded performance

In d1b2023, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1441 ms

Resolved: Bofrost.at performance has improved in 190c51b after 9 minutes.


ARROW-2891: [Python] Preserve schema in write_to_dataset

Codecov Report

Merging #2302 into master will increase coverage by 2.39%.
The diff coverage is 100%.

@@            Coverage Diff            @@
##           master   #2302      +/-   ##
=========================================
+ Coverage    84.4%   86.8%   +2.39%
=========================================
  Files         293     237      -56
  Lines       44652   41918    -2734
=========================================
- Hits        37688   36386    -1302
+ Misses       6933    5532    -1401
+ Partials       31       0      -31

Impacted Files
Coverage Δ

python/pyarrow/tests/test_parquet.py
96.97% <100%> (ø)
:arrow_up:

python/pyarrow/parquet.py
90.54% <100%> (+0.07%)
:arrow_up:

cpp/src/arrow/util/thread-pool-test.cc
98.91% <0%> (-0.55%)
:arrow_down:

go/arrow/math/int64.go

go/arrow/array/numeric.gen.go

rust/src/array.rs

go/arrow/type_string.go

go/arrow/array/data.go

go/arrow/math/uint64_amd64.go

go/arrow/datatype_numeric.gen.go

... and 50 more

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 2ff8708...83d0048. Read the comment docs.

@jkulzick Thank you for having the patience to fix this!

@xhochy Happy to contribute. Thanks for this great package!

Thanks @jkulzick!

Thank you @jkulzick -- running into this issue right now!

I've looked everywhere I could think of. Is there any place which provides an estimation of when the next release including this fix might be made? -- Thanks!


Correlation tab merge for downloadButton on corrplot

png file at 800px x 800px with download link

corrplot command is not updated. please review @yipcma


Parent.config Issue

Hi,
We have have a scenario, where we have to point three origin server in parent config, when client requested to play a video any one of the origin server which having video need to complete the request.
Could you please share me if any roles.
Thanks in advance
Satheesh R

the<EMAIL_ADDRESS>mailing list is also a great place to ask questions.

Thank you
On Tue, 5 Feb 2019 at 9:08 PM, David Neuman<EMAIL_ADDRESS>wrote:

the<EMAIL_ADDRESS>mailing list is also a great place to
ask questions.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/trafficcontrol/issues/3285#issuecomment-460684629,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AhuO0PvZ3SVkHpUlkk24KjD4cC0hkx_5ks5vKaV8gaJpZM4aa6vY
.


Create a  character list

Create a list of cards to display characters showing the image and name

#8


Support for multiple selections

This pull request adds support for multiple selections.
Multiple selections work the same way single ones do : inline tag wrap is supported as well as multiline "block" tag wrap. We can also have a mix of the two.

The pull request also addresses the bug with empty selections (#6) which are now supported (both with single or multiple selections).
Thank you !

Will anyone be able to review this ? @bgashler1 ?

Thanks @hmigneron for your contribution.  I'll be taking a look.

This issue was moved to bgashler1/vscode-htmltagwrap#10


Add dev tools jq and HTTPie to ov

Description

This PR adds tools jq and HTTPie that I use frequently during development to the ov container. I believe other people in the team will appreciate these tools. On that note, we should define some criteria for what tools should be included in the dev-env image.
Testing Instructions

Build a new ov image using ov build.

Get rid of the old ov container using ov stop && docker container rm openverse-dev-env.

Run ov bash to get a fresh instance.

Run http or jq or both:

Checklist

[x] My pull request has a descriptive title (not a vague title likeUpdate index.md).
[x] My pull request targets the default branch of the repository (main) or a parent feature branch.
[x] My commit messages follow best practices.
[x] My code follows the established code style of the repository.
[ ] I added or updated tests for the changes I made (if applicable).
[ ] I added or updated documentation (if applicable).
[x] I tried running the project locally and verified that there are no visible errors.
[ ] I ran the DAG documentation generator (./ov just catalog/generate-docs for catalog
PRs) or the media properties generator (./ov just catalog/generate-docs media-props
for the catalog or ./ov just api/generate-docs for the API) where applicable.

Developer Certificate of Origin

Developer Certificate of Origin
Developer Certificate of Origin
Version 1.1

Copyright (C) 2004, 2006 The Linux Foundation and its contributors.
1 Letterman Drive
Suite D4700
San Francisco, CA, 94129

Everyone is permitted to copy and distribute verbatim copies of this
license document, but changing it is not allowed.

Developer's Certificate of Origin 1.1

By making a contribution to this project, I certify that:

(a) The contribution was created in whole or in part by me and I
    have the right to submit it under the open source license
    indicated in the file; or

(b) The contribution is based upon previous work that, to the best
    of my knowledge, is covered under an appropriate open source
    license and I have the right under that license to submit that
    work with modifications, whether created in whole or in part
    by me, under the same open source license (unless I am
    permitted to submit under a different license), as indicated
    in the file; or

(c) The contribution was provided directly to me by some other
    person who certified (a), (b) or (c) and I have not modified
    it.

(d) I understand and agree that this project and the contribution
    are public and that a record of the contribution (including all
    personal information I submit with it, including my sign-off) is
    maintained indefinitely and may be redistributed consistent with
    this project or the open source license(s) involved.

Ah yes that would be because /opt has a volume mounted at the path, which prevents the changes from showing up. We should probably look into that.


Add identicons to address/contract/token pages.

Add identicons to address page, contract page and token page (if it doesn't have an icon).
Acceptance Criteria
On Address Page and for contracts, add the generated icon  "blockie" or "identicon" used on the search bar:

Display it here:

instead of the generic face icon.

this issue resolved?


Repository_dispatch jobs deploy master branch

While #39 implemented support for repository_dispatch events, I don't see yet how to use it when someone makes a PR from his fork. I understand the concept of using /ok-to-test and dispatching via repository_dispatch.
However, when I print the variables in the okteto/deploy-preview job:
GITHUB_EVENT_NAME=repository_dispatch
GITHUB_REF_NAME=master
GITHUB_REF=refs/heads/master

Which contains master instead of the PR branch! And okteto/deploy-preview is figuring out the branch var to pass to the okteto deployer: https://github.com/okteto/deploy-preview/blob/main/entrypoint.sh#L34-L38 so it ends up passing the master branch to the okteto deployer.
So in the end this happens:

Someone forks your repository and creates a PR
You type /ok-to-deploy sha=XXX
An ok-to-deploy action is triggered which triggers an okteto-preview-deploy action (repository_dispatch)
The script in okteto/deploy-preview determines master branch should be deployed based on GITHUB_REF
A preview deploy is made using changes from the latest master branch, not from the PR

Any good suggestion to tackle this? I can make a PR, however I suppose we need to pass our custom own env var with the branch BRANCH since we don't have the PR number in the default env vars (it's dispatched)?
      - name: Deploy preview environment
        uses: okteto/deploy-preview@main
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          BRANCH: 'refs/pull/${{ github.event.client_payload.pull_request.number }}/merge'
        with:
          name: ${{ env.DEPLOY_NAME }}

Did you also observe this @ikuradon ?

@jessedobbelaere which version of the action are you using?


compatibility with variadic parameters

First of all, thank you for developing the PetriNet/DES simulator. It's a great tool!
I have updated the parameter validation to support user variadic functions. It is useful when the number of input parameters is unknown at coding time or when working with a large system (e.g., a full-scale factory).
Below is an example:
from simpn.simulator import SimProblem, SimToken

P = SimProblem()

clock = P.add_var("clock")
places=[clock]
N=5 #<--- changing the PetriNet topology
for i in range(N):
    places.append( P.add_var("S"+str(i)) )

def behavior(clock, *stores):
    out=[SimToken(clock+1, delay=1)]
    for store in stores:
        out.append( SimToken(store+1, delay=1) )
    return out

def guard(clock, *stores):
    return sum(stores)<100

# init 0
for p in places:
    p.put(0,time=0)

P.add_event(inflow=places, outflow=places, behavior=behavior, guard=guard)

# Running
from simpn.reporters import SimpleReporter
P.simulate(10, SimpleReporter())
from simpn.visualisation import Visualisation
v = Visualisation(P)
v.show()

Thanks, I also put a release on GitHub with your addition.
On Fri, Sep 6, 2024 at 7:22 PM PierrickPochelu @.***>
wrote:

First of all, thank you for developing the PetriNet/DES simulator. It's a
great tool!
I have updated the parameter validation to support user variadic
functions. It is useful when the number of input parameters is unknown at
coding time or when working with a large system (e.g., a full-scale
factory).
Below is an example:
from simpn.simulator import SimProblem, SimToken
P = SimProblem()
clock = P.add_var("clock")
places=[clock]
N=5 #<--- changing the PetriNet topology
for i in range(N):
places.append( P.add_var("S"+str(i)) )
def behavior(clock, *stores):
out=[SimToken(clock+1, delay=1)]
for store in stores:
out.append( SimToken(store+1, delay=1) )
return out
def guard(clock, *stores):
return sum(stores)<100
init 0
for p in places:
p.put(0,time=0)
P.add_event(inflow=places, outflow=places, behavior=behavior, guard=guard)
Running
from simpn.reporters import SimpleReporter
P.simulate(10, SimpleReporter())
from simpn.visualisation import Visualisation
v = Visualisation(P)
v.show()

You can view, comment on, or merge this pull request online at:
https://github.com/bpogroup/simpn/pull/2
Commit Summary

2101fdf
https://github.com/bpogroup/simpn/pull/2/commits/2101fdff2d26678546df7863bf4934afb2a8c656
compatibility with variadic parameters

File Changes
(1 file https://github.com/bpogroup/simpn/pull/2/files)

M simpn/simulator.py
https://github.com/bpogroup/simpn/pull/2/files#diff-b40d0d9b003f85ecca9295da2ba3dcffbed3ba09f4b0a6195d4d9d60002367df
(14)

Patch Links:

https://github.com/bpogroup/simpn/pull/2.patch
https://github.com/bpogroup/simpn/pull/2.diff

—
Reply to this email directly, view it on GitHub
https://github.com/bpogroup/simpn/pull/2, or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADHF2CXVUWWV4QGFESP5VF3ZVHQFBAVCNFSM6AAAAABNY7PMO2VHI2DSMVQWIX3LMV43ASLTON2WKOZSGUYTAOBYGY2TEMI
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


BCeID Wording changes

Changes requested by IDIM:

Whenever you make reference to [ Business BCeID ] or [ Basic BCeID ] in your communications material, please stay ‘on brand’... It isn’t ‘BCeID Business’ or ‘BCeID Basic’ or just ‘Basic’:

Same ‘on brand’ [ Business BCeID ] & [ Basic BCeID ] challenges here:

Hey team! Please add your planning poker estimate with Zenhub @AntBush @marcellmueller @matthieu-foucault @wenzowski

merged with #484


"error using text editor for pull request message"

Hi! When I pull request with "hub pull-request", this error "error using text editor for pull request message" happens!  So, Can I pull request on command line with "hub"?

Hi! When I pull request with "hub pull-request", this error "error using text editor for pull request message" happens! So, Can I pull request on command line with "hub"?

My machine environment:
git version 2.21.0.windows.1
hub version 2.12.8

Hi, you need to configure your git settings to specify a text editor that will open when you run hub pull-request.
You can see your current editor with git config core.editor
If it lists an editor you're unfamiliar with, see here to find out how to change that setting to an editor you prefer: https://help.github.com/en/articles/associating-text-editors-with-git


[ci] Fix ffmpeg Url

List of Changes

Fix Ffmpeg URL for windows ci as the previous upstream is down for a week.

Motivation
TO prevent failing tests for windows which could happen when Github Cache expires next month.
Acknowledgement

[x] I have read the Contributing Guidelines

This needs an review to be merged.


deploy: Remove liveness and readiness probes

Parca-Agent no longer listens on all interfaces by default, therefore this doesn't work anymore.

Does not work, I tried.

If you can get it to work on a Kubernetes cluster I'm perfectly fine with keeping them but I tried that configuration and it didn't work so I think removing is the best option. Besides, parca-agent doesn't serve traffic so I find the HTTP based probes kind of silly to begin with.

I think this explains quite well why: https://stackoverflow.com/questions/62615675/kubernetes-redinessprobe-httpget-on-tomcat-image-reports-connection-refused
The host is the what the kubelet uses to perform the request, but the kubelet is in a different net namespace than the container, therefore the container's <IP_ADDRESS> is not the same interface as the kubelet's <IP_ADDRESS>. The pod IP (which is the default) worked before because that was uniquely identifying.

Let me know if you have any other concerns!

Also listening on localhost, does it mean we do not want observability endpoints (/metrics and /debug/pprof) accessible by default?

I think we would need make them accessible in the demo again at least, I believe we were using them there

And I guess it is not possible to port-forward with this config either. For a systemd service, it'd be fine, but maybe it should continue to listen on all interfaces in the Kubernetes deployment by default? We could add a NetworkPolicy blocking by default if it's a concern?

I think I'd be ok with explicitly setting --listen-address=:7071 as well if you prefer that?

Ok so false alarm, it was just Polar Signals' manifest that was not working, as we didn't specify --listen-address=:7070 explicitly, but actually these upstream manifests do.

I'd still like to remove liveness probes as I think they're generally more harm than good, but I'll close this PR here and open a new one.


Fetch response.json() returns native js object instead of Map

Dart SDK Version 2.1.0-dev.8.0
MacOS Mojave
Chrome 70

I was just testing out fetch with DDC (webdev serve) and noticed response.json() returns a native JS object, when I would think it should return a Dart Map:
final fetch = WorkerGlobalScope.instance.fetch;

final response = await fetch('https://api.github.com/users/mnordine');
final json = await response.json();
print(json.runtimeType);

Output: NativeJavaScriptObject
An obvious workaround is to json.decode(await response.text())
A bigger issue I ran into was this throws a runtime error when doing webdev build, but it doesn't with webdev build --no-release
Update: I've filed another issue for the runtime error here: https://github.com/dart-lang/sdk/issues/34924

CC @terrylucas RE his latest updates to these APIs

Also, response above should be a Stream, since it's a ReadableStream in JS


promise.fulfill rejects the promise

I'm encountering a behaviour where calling promise.fulfill with an Error argument results in the promise being rejected:
struct SomeError: Error {}

let promise = Promise<Error?>.pending()
promise.then {_ in
    print("Promise fulfilled")
}.catch {_ in
    print("Promise rejected")
}

promise.fulfill(SomeError())

The resulting output is Promise rejected instead of Promise fulfilled. Is this expected behaviour?
It appears that fulfill and reject are not distinguished on the objc layer: https://github.com/google/promises/blob/7373adec497aaf3e18fe0b9c11a39e7b8c1b5337/Sources/Promises/Promise.swift#L57-L64

Hi Ben,
Yes, that's made deliberately, so that a promise cannot be fulfilled with an error, but only rejected.
Thanks.

Hi @shoumikhin,
Thanks for the quick reply! Any idea why this decision was made deliberately? Coming from a Javascript background I was expecting promise.fulfill to fulfill the promise regardless of what's passed in.
Thanks

Actually, I'd be curious to learn why JS promises allow fulfilling with errors.
Perhaps, because JS is an untyped language and it's not feasible to distinguish between errors and everything else? Or maybe there're real use cases when you want a promise fulfilled with an error?
Don't know. It just seems right to treat a promise resolved with an error as rejected.

That's a very good question that I don't have an answer for 😄. Interesting that it never occurred to me before. I think a use case for fulfilling with an error may occur when we are want a function that asynchronously returns an error object (for passing to other parts of the application):
let errObj: CustomError? = try? await(getErrorObj())
// use errObj elsewhere

or is this just bad programming?
Anyway, the purpose of this issue is fulfilled. I'll close it now.

By the way, this prevents extending a type (i.e. String) to conform to Error- a fulfilled promise with a String return value would be kicked into being rejected.


[Backport 2.3] Fix registry credentials so that it doesn't crash

Backport for https://github.com/rancher/rancher/issues/26981

Reproduced the issue in v2.3.7

Create a registry selecting "Available to all namespaces" and save
UI is stuck in saving state and does not complete.

Validated in  v2.3-head(aea3cc0)

Add a registry selecting the scope "Available to all namespaces".
Configure Dockerhub/quay/artifactory/custom registry then save
Registry gets created as expected without any errors.
Creating a registry in a single namespace also works fine.

This was validated with 2.3-head, but was missed in the UI release that was shipped with 2.3.8, so moved to 2.3.9.


Matcha-TTS has very low GPU utilization.

First of all thanks for very nice TTS system. This is very interresting and inspiring system.

I tried to train it, but it seems to train very slowly  I see 0.5 to 1.6 iterations per second. At the same time I see neglectable GPU utilization.  Is that to be expected?  (Running on A100 gpu)

I expect that yes, and by looking at the number of parameters the model is quite small one, so I would assume the speed is slow because of  CPU based MAS computation.

Are you aware of any reason why using alignment implemented by FastPitch team would not work? The implementation in NVidia Deeplearning examples is very snappy.  https://arxiv.org/abs/2108.10447

Thanks for your great work and insights!

Thank you very much for your kind words :)

I tried to train it, but it seems to train very slowly I see 0.5 to 1.6 iterations per second. At the same time I see neglectable GPU utilization. Is that to be expected? (Running on A100 GPU)

I expect that yes, and by looking at the number of parameters the model is quite small one, so I would assume the speed is slow because of CPU based MAS computation.

Precisely! Its the MAS that is taking the most time, what you can do is once it is reasonably trained save the alignments and then train using those alignments. (I do it too for other purposes works like a charm)

Are you aware of any reason why using alignment implemented by FastPitch team would not work? The implementation in NVidia Deeplearning examples is very snappy. https://arxiv.org/abs/2108.10447

It would work just fine! I tried it but at least on my consumer grade GPU it was giving similar results. So I stuck with the easier codebase but feel free to replace it and post your experience.
Hope it helps!

Thanks for such a quick repsonse!  I'll try the aligner and share my results.

Hello!
I have added the source code of this and added documentation around it! Hopefully it will help :)
https://github.com/shivammehta25/Matcha-TTS/wiki/Improve-GPU-utilisation-by-extracting-phoneme-alignments
Kind Regards,
Shivam


Mspsds 491 product search fixes

Pull Request Test Coverage Report for Build 624

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage remained the same at 87.304%

Files with Coverage Reduction
New Missed Lines
%

../helpers/products_helper.rb
2
91.18%

Totals

Change from base Build 623:
0.0%

Covered Lines:
1004

Relevant Lines:
1150

💛  - Coveralls

Pull Request Test Coverage Report for Build 625

0 of 0   changed or added relevant lines in 0 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage remained the same at 87.304%

Files with Coverage Reduction
New Missed Lines
%

../helpers/products_helper.rb
2
91.18%

Totals

Change from base Build 623:
0.0%

Covered Lines:
1004

Relevant Lines:
1150

💛  - Coveralls


Help: ...

What VPN service provider are you using?

[X] PIA
[ ] Mullvad
[ ] Windscribe

What's the version of the program?
`Running version latest build

What are you using to run the container?

[ ] Docker run
[X] Docker Compose
[ ] Kubernetes
[ ] Docker stack
[ ] Docker swarm
[ ] Podman
[ ] Other:

What's the problem?

I get following warnings in the log:
INFO	dns configurator: using DNS address <IP_ADDRESS> internally
dns configurator: using DNS address <IP_ADDRESS> system wide
WARN	dns configurator: could not resolve github.com (try 1 of 10): lookup github.com on <IP_ADDRESS>:53: read udp <IP_ADDRESS>:51037-><IP_ADDRESS>:53: read: connection refused

WARNING: 'link-mtu' is used inconsistently, local='link-mtu 1570', remote='link-mtu 1542'
WARNING: 'cipher' is used inconsistently, local='cipher AES-256-CBC', remote='cipher BF-CBC'
WARNING: 'auth' is used inconsistently, local='auth SHA256', remote='auth SHA1'
WARNING: 'keysize' is used inconsistently, local='keysize 256', remote='keysize 128'

Hi there, thanks for your issue!
The first warning is fine, it's just the first DNS resolution try to wait for Unbound to be launched. I may add a few milliseconds before the first try to avoid showing the warning.
For the second warnings, that's just PIA doing their strange configuration server side, see this in the FAQ.


import-blacklist regex

Feature request
Is your feature request related to a problem? Please describe.
I would really like to be able to add a regex to the import-blacklist
Describe the solution you'd like
e.g.
<EMAIL_ADDRESS>

Thanks for the suggestion @pburkindine! Agreed that this would be useful, but this looks like it's a bit tricky. Since the configuration already allows direct string comparisons with / forward slashes, there would need to be some way to indicate whether a blacklisted string is a regular string or meant to be a regex.

This would be very beneficial when using non-relative path import in the tsconfig.json to disallow imports like app/ or ../../module. Currently I have to replicate the paths in both tsconfig and tslint

This is supported in 5.13.0, issue can be closed.

Good catch! https://github.com/palantir/tslint/pull/3504


Blind failed transactions

I noticed that there isn't a way to now if a batch failed, since once it's registered into  the queue, a 200 status code is returned. I was thinking about, instead of returning a 200 status code, return 201 and some id that relates to the created batch. So you can query /services//batch/<id> and get the status of this transaction.

+1.  When i was about to post the same question, I came across this comment. Is there any update on this concern? Our application needs to capture the failure transactions for troubleshooting and retrying if necessary.

Sounds like a good addition. Can you work on this and send me a pull request?


WIP | Upgrade @octokit/rest to v17

Alright, I think I'm back to working on stuff.
Draft PR created for external parties to view the status of this upgrade.
Unfortunately, this PR will have to be squashed since migration wasn't a linear process.
TODOs

[ ] Adapt addGraphql method within GitHubAPI function.
[ ] Adapt addPagination method within GitHubAPI function.

Hey Maxim, could you comment on the state of the PR?

@MaximDevoir @gr2m Is there an update on this PR?

Unfortunately, I am mostly unavailable during the COVID-19 pandemic until June - I hope. It’d be awesome if someone else could take over this issue. If not, I’ll try to find some free time on the random days I am available.

Thanks Maxim, very much understandable.
If you find a moment, in case someone wants to take over, it would be helpful  what state the PR is in right now, what's left to do, etc.

I'll try to take it from here :)

closing in favor of https://github.com/probot/probot/pull/1250


Add eslint-plugin-html plugin

Add eslint-plugin-html plugin that allows linting html files.

Thanks @andrey-git. #183 was merged adding this package.


remove etcd service

We no longer need to create this.
/assign @sttts @mfojtik

/lgtm
This is logically not belonging to this operator anyway.


Text can't show degress if the value of the string is passed by a variable

Description
I think Text doesn't behave the same if the text is passed via a variable
Version
0.70.1
Output of npx react-native info
System:
OS: macOS 12.3.1
CPU: (8) arm64 Apple M1
Memory: 160.70 MB / 16.00 GB
Shell: 5.8 - /bin/zsh
Binaries:
Node: 16.17.1 - /usr/local/bin/node
Yarn: Not Found
npm: 8.19.2 - /opt/homebrew/bin/npm
Watchman: Not Found
Managers:
CocoaPods: 1.11.3 - /opt/homebrew/bin/pod
SDKs:
iOS SDK:
Platforms: DriverKit 21.4, iOS 15.4, macOS 12.3, tvOS 15.4, watchOS 8.5
Android SDK: Not Found
IDEs:
Android Studio: 2021.1 AI-211.7628.21.2111.8193401
Xcode: 13.3/13E113 - /usr/bin/xcodebuild
Languages:
Java: <IP_ADDRESS> - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: 18.1.0 => 18.1.0
react-native: 0.70.1 => 0.70.1
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
import React from 'react';
import {Text} from 'react-native';

const reproduceTextBug = () => {
  const text = '10°';
  return (
    <Text>
      10°
      {text}
    </Text>
  );
};

Snack, code example, screenshot, or link to a repository

https://www.npmjs.com/package/html-entities using this library resolves the problem...


iosApp run configuration not found

Describe the bug
I cloned https://github.com/JetBrains/compose-multiplatform-ios-android-template/tree/dde60620de9f8e3ba4d82e08141712a467af5d86 and tried to run the demo on an iOS simulator from Android Studio as the README says. However, Android Studio does not show any iosApp run configuration and no option is available to create one.
Affected platforms

iOS

Versions

Kotlin version*: kotlin.version=1.8.20
Compose Multiplatform version*: compose.version=1.4.0
OS version(s)* (required for Desktop and iOS issues): macOS Ventura 13.3.1
OS architecture (x86 or arm64): Apple M2 - arm64
Android Studio Flamingo | 2022.2.1

To Reproduce
Steps and/or the code snippet to reproduce the behavior:

unzip https://github.com/JetBrains/compose-multiplatform-ios-android-template/archive/dde60620de9f8e3ba4d82e08141712a467af5d86.zip
Open directory in Android Studio
NB: there are warnings, see screenshot below
As per the screenshots, there is no iosApp run configuration

Expected behavior
It should be possible to run the iosApp in an iOS simulator from Android Studio.
Screenshots

Do you have the latest KMM plugin installed in your Android Studio?

Thank you @eymar, sorry that I missed that item in the README. It would be nice if kdoctor could check that.
After installing the plugin "Kotlin Multiplatform Mobile" (v 4.22) I can start the app in the iPhone 14 simulator.

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Expose codec_context.codec_tag (fixes: #741)

This is just #748 with an additional test

The other problem is that the current get/set test only really tests that the get and the set are compatible with each other - they don't really test the representation is stored into the codec tag correctly. A related issue here is that 'divx' and 'xvid' are both valid tags so a problem with the endianness might be hard to spot.
However, I tested it locally with libx265 and the hvc1 tag and the output confirmed that the tag was working properly.

I agree, we're only testing the consistency of our getter/setter. Do you know if any files in the FATE test suite might allow us to get the tag from an existing file?


pull

What this PR does / why we need it:
Which issue this PR fixes(if applicable):
fixes #
Special notes for reviewers:

Release note:

update

update