entities do not start after HA restart

After rebooting HA, all entities report that they are unavailable, it helps to select the reload option on each
HA wersja 2022.11.4
PowerCalc - v1.1.8

Do you have this after every reboot or incidentially?
Anything in the logs? also try to enable debug logging.

this happens after every reset. Now I noticed in the logs that maybe because I gave autodiscover earlier.
powercalc:
energy_sensor_precision: 2
force_update_frequency: 00:00:15
create_energy_sensors: true
#enable_autodiscovery: true    --------------------------------------
energy_sensor_naming: "{} Energysensor"
power_sensor_naming: "{} Powersensor"
create_utility_meters: true
2023-01-02 22:23:07.988 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration powercalc which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-01-02 22:23:24.018 DEBUG (MainThread) [custom_components.powercalc] Start auto discovering entities
2023-01-02 22:23:24.019 DEBUG (MainThread) [custom_components.powercalc.power_profile.model_discovery] media_player.salon: Auto discovered model (manufacturer=Google Inc., model=Google Home)
2023-01-02 22:23:24.023 DEBUG (MainThread) [custom_components.powercalc] media_player.salon: Model not found in library, skipping discovery
2023-01-02 22:23:24.023 DEBUG (MainThread) [custom_components.powercalc.power_profile.model_discovery] media_player.wszystkie: Auto discovered model (manufacturer=Google Inc., model=Google Cast Group)
2023-01-02 22:23:24.023 DEBUG (MainThread) [custom_components.powercalc] media_player.wszystkie: Model not found in library, skipping discovery
2023-01-02 22:23:24.024 DEBUG (MainThread) [custom_components.powercalc.power_profile.model_discovery] switch.schedule_f14e96: Auto discovered model (manufacturer=@nielsfaber, model=Scheduler)
2023-01-02 22:23:24.024 DEBUG (MainThread) [custom_components.powercalc] switch.schedule_f14e96: Model not found in library, skipping discovery
2023-01-02 22:23:24.024 DEBUG (MainThread) [custom_components.powercalc.power_profile.model_discovery] switch.schedule_f8cec3: Auto discovered model (manufacturer=@nielsfaber, model=Scheduler)
2023-01-02 22:23:24.025 DEBUG (MainThread) [custom_components.powercalc] switch.schedule_f8cec3: Model not found in library, skipping discovery

disabling autodiscovery didn't help

2023-01-03 23:03:14.958 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration powercalc which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-01-03 23:03:31.951 DEBUG (MainThread) [custom_components.powercalc.power_profile.model_discovery] sensor.klima_current_power: Auto discovered model (manufacturer=Broadlink, model=SP3S-EU)
2023-01-03 23:03:31.954 DEBUG (MainThread) [custom_components.powercalc.sensors.power] Creating power sensor (entity_id=sensor.klima_current_power entity_category=None, sensor_name=Klima energia Powersensor strategy=FixedStrategy manufacturer= model= standby_power=0.20 unique_id=34ea347a15ab-power)
2023-01-03 23:03:31.955 DEBUG (MainThread) [custom_components.powercalc.sensors.energy] Creating energy sensor: Klima energia Energysensor
2023-01-03 23:03:31.955 DEBUG (MainThread) [custom_components.powercalc.sensors.utility_meter] Creating utility_meter sensor: Klima energia Energysensor daily (entity_id=sensor.klima_energia_energy_daily)
2023-01-03 23:03:31.956 DEBUG (MainThread) [custom_components.powercalc.sensors.utility_meter] Creating utility_meter sensor: Klima energia Energysensor weekly (entity_id=sensor.klima_energia_energy_weekly)
2023-01-03 23:03:31.956 DEBUG (MainThread) [custom_components.powercalc.sensors.utility_meter] Creating utility_meter sensor: Klima energia Energysensor monthly (entity_id=sensor.klima_energia_energy_monthly)
2023-01-03 23:03:31.957 DEBUG (MainThread) [custom_components.powercalc.power_profile.model_discovery] sensor.smart_socket_3_power: Auto discovered model (manufacturer=Tuya, model=Smart Socket (37mnhia3pojleqfh))
2023-01-03 23:03:31.961 DEBUG (MainThread) [custom_components.powercalc.sensors.power] Creating power sensor (entity_id=sensor.smart_socket_3_power entity_category=None, sensor_name=Suszarka Energy Calc Powersensor strategy=FixedStrategy manufacturer= model= standby_power=0.20 unique_id=tuya.3038076070039f64c8cacur_power)
2023-01-03 23:03:31.962 DEBUG (MainThread) [custom_components.powercalc.sensors.energy] Creating energy sensor: Suszarka Energy Calc Energysensor
2023-01-03 23:03:31.962 DEBUG (MainThread) [custom_components.powercalc.sensors.utility_meter] Creating utility_meter sensor: Suszarka Energy Calc Energysensor daily (entity_id=sensor.suszarka_energy_calc_energysensor_daily)
2023-01-03 23:03:31.963 DEBUG (MainThread) [custom_components.powercalc.sensors.utility_meter] Creating utility_meter sensor: Suszarka Energy Calc Energysensor weekly (entity_id=sensor.suszarka_energy_calc_energysensor_weekly)
2023-01-03 23:03:31.964 DEBUG (MainThread) [custom_components.powercalc.sensors.utility_meter] Creating utility_meter sensor: Suszarka Energy Calc Energysensor monthly (entity_id=sensor.suszarka_energy_calc_energysensor_monthly)
2023-01-03 23:03:31.965 DEBUG (MainThread) [custom_components.powercalc.power_profile.model_discovery] sensor.aubess_smart_socket_20a_em_power: Auto discovered model (manufacturer=Tuya, model=Aubess Smart Socket 20A#slash#EM (2iepauebcvo74ujc))

last log:
2023-01-03 23:25:25.962 DEBUG (MainThread) [custom_components.powercalc.sensors.power] sensor.smart_socket_3_power: State changed to "2891.0". Power:320.00
2023-01-03 23:25:30.973 DEBUG (MainThread) [custom_components.powercalc.sensors.power] sensor.smart_socket_3_power: State changed to "2886.0". Power:320.00
2023-01-03 23:25:35.999 DEBUG (MainThread) [custom_components.powercalc.sensors.power] sensor.smart_socket_3_power: State changed to "2881.0". Power:320.00
2023-01-03 23:25:39.139 DEBUG (MainThread) [custom_components.powercalc.sensors.power] sensor.lazienka_bojler_power: State changed to "1529". Power:1507.00
2023-01-03 23:25:46.071 DEBUG (MainThread) [custom_components.powercalc.sensors.power] sensor.smart_socket_3_power: State changed to "2884.0". Power:320.00
2023-01-03 23:25:51.060 DEBUG (MainThread) [custom_components.powercalc.sensors.power] sensor.smart_socket_3_power: State changed to "2879.0". Power:320.00

create_energy_sensors: false
create_utility_meters: false
disable this option helped

Interesting finding.
What do you mean with unavailable exactly? Do you have a screenshot of the situation.
You are only using the GUI configuration right?
I think you might have the same issue as reported here: https://github.com/bramstroker/homeassistant-powercalc/issues/1153.
But I was never able to reproduce or fix this.
When you have these config settings than the entities are created succesfully after every restart?
create_energy_sensors: false
create_utility_meters: false

What if you only disable utility meters or energy sensors to find the actual cause?

but didn't help, the entity is still not anailable

2023-01-05 14:36:14.974 WARNING (SyncWorker_0) [homeassistant.loader] We found a custom integration powercalc which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-01-05 14:36:31.126 DEBUG (MainThread) [custom_components.powercalc.power_profile.model_discovery] sensor.klima_current_power: Auto discovered model (manufacturer=Broadlink, model=SP3S-EU)
2023-01-05 14:36:31.130 DEBUG (MainThread) [custom_components.powercalc.sensors.power] Creating power sensor (entity_id=sensor.klima_current_power entity_category=None, sensor_name=Klima energia Powersensor strategy=FixedStrategy manufacturer= model= standby_power=0.20 unique_id=34ea347a15ab-power)
2023-01-05 14:36:31.130 DEBUG (MainThread) [custom_components.powercalc.sensors.energy] Creating energy sensor: Klima energia Energysensor
2023-01-05 14:36:31.131 DEBUG (MainThread) [custom_components.powercalc.sensors.utility_meter] Creating utility_meter sensor: Klima energia Energysensor daily (entity_id=sensor.klima_energia_energy_daily)
2023-01-05 14:36:31.131 DEBUG (MainThread) [custom_components.powercalc.sensors.utility_meter] Creating utility_meter sensor: Klima energia Energysensor weekly (entity_id=sensor.klima_energia_energy_weekly)
2023-01-05 14:36:31.132 DEBUG (MainThread) [custom_components.powercalc.sensors.utility_meter] Creating utility_meter sensor: Klima energia Energysensor monthly (entity_id=sensor.klima_energia_energy_monthly)
2023-01-05 14:36:31.133 DEBUG (MainThread) [custom_components.powercalc.power_profile.model_discovery] sensor.smart_socket_3_power: Auto discovered model (manufacturer=Tuya, model=Smart Socket (37mnhia3pojleqfh))

This means not the entity is unavailable, but the entity is not created by powercalc at all in HA, which seems rather similar bug as I linked above.
On the integration overview page when you click a config entry (where you reload), are you seeing any entities there. Or is that list empty and after reload entities appear?
Do you have this issue with all powercalc entities or only some of them?
You mentioned that setting create_energy_sensors to false worked, but later when I asked again it didn't work?

In fact, entities do not create after the restart, only after reloading.
with all powercalc entities

From the logs the results that energy sensors are formed. I found something like this in the logs after restart:
2023-01-07 11:58:49.562 DEBUG (MainThread) [custom_components.powercalc.sensors.utility_meter] Creating utility_meter sensor: Lustro Energia Energysensor daily (entity_id=sensor.lustro_energia_energysensor_daily)
2023-01-07 11:58:49.572 DEBUG (MainThread) [custom_components.powercalc.sensors.utility_meter] Creating utility_meter sensor: Lustro Energia Energysensor weekly (entity_id=sensor.lustro_energia_energysensor_weekly)
2023-01-07 11:58:49.573 DEBUG (MainThread) [custom_components.powercalc.sensors.utility_meter] Creating utility_meter sensor: Lustro Energia Energysensor monthly (entity_id=sensor.lustro_energia_energysensor_monthly)
2023-01-07 11:58:49.719 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.lustro_energia_energysensor_daily to device 04a26ee2097ac8bc5678b774e153c10f
2023-01-07 11:58:49.727 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.lustro_energia_energysensor_weekly to device 04a26ee2097ac8bc5678b774e153c10f
2023-01-07 11:58:49.734 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.lustro_energia_energysensor_monthly to device 04a26ee2097ac8bc5678b774e153c10f

checking by mistake I checked the entities created in HA as a media counter and not the one from powercalc

This is all expected and just says powercalc tried to create the 3 utility meters during startup. There is no indication these entities are not created and no further error which makes it very strange. Seems some strange bug in internals of HA, as it only hits a handful of users. hundreds to thousands of users are using the powercalc GUI config on a daily basis without any problems.
For every powercalc entry you should see the following in the logs:

Creating power sensor (1 time)
Creating energy sensor (1 time, only when create_energy_sensor is not false)
Creating utility_meter sensor (multiple times depending on configured utility meter cycles, only when create_utility_meters it true)

The only common thing #1153 is that you are also using Tuya.
Could you try temporarily disabling that integration and restarting to see if that resolves something?
How many powercalc entries do you have?
Maybe you can also try disabling them one by one to see if this resolves anything, so we can find the culprit.
It's very cumbersome, I know. but without any reproduction steps I have no idea how to resolve the issue.
I will ask around on discord to the HA devs if anyone has seen a similar issue before.

I also found such a thing
Logger: custom_components.powercalc.sensors.power
Source: custom_components/powercalc/sensors/power.py:94
Integration: Powercalc (documentation, issues)
First occurred: 14:17:51 (4 occurrences)
Last logged: 14:17:51
switch.grzejnik_socket_1: Skipping sensor setup Model not found in library (manufacturer: Tuya, model: Wifi Plug (j0zozzoarutv0nu1))
switch.grzejnik_socket_1: Skipping sensor setup: Model not found in library (manufacturer: Tuya, model: Wifi Plug (j0zozzoarutv0nu1))
switch.lazienka_bojler: Skipping sensor setup Model not found in library (manufacturer: TuYa, model: Smart plug (with power monitoring) (TS011F_plug_1))
switch.lazienka_bojler: Skipping sensor setup: Model not found in library (manufacturer: TuYa, model: Smart plug (with power monitoring) (TS011F_plug_1))

That is just some debug information of the auto discovery routine which is run during HA startup.
Powercalc will look at all your entities in you whole installation and checks if it has manufacturer and model informaiton available. When it has it checks if a matching power profile is available in powercalc library.
When that is not the case you'll see Skipping sensor setup: Model not found in library in the logs.
I'm 99% certain this has no relation to your issue.
But just to be sure you could try disabling autodiscovery enable_autodiscovery: false, but you already tried looking at one of your first comments.

I noticed one more thing, I re-enabled the creation of energy and meters and newer Tuya devices that work in HA through Z2M in Zigbee works powercalc, while those created through Tuya integrations entities do not create.

enable_autodiscovery now I have false all the time

First:
sensor.suszarka_energy_calc_energysensor to device c3e728fadebd879a4670d5c749400b8a
2023-01-07 14:17:51.309 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.suszarka_energy_calc_energysensor_daily to device c3e728fadebd879a4670d5c749400b8a
2023-01-07 14:17:51.316 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.suszarka_energy_calc_energysensor_weekly to device c3e728fadebd879a4670d5c749400b8a
2023-01-07 14:17:51.322 DEBUG (MainThread) [custom_components.powercalc.sensors.abstract] Binding sensor.suszarka_energy_calc_energysensor_monthly to device c3e728fadebd879a4670d5c749400b8a
Meter is create:
2023-01-07 14:17:51.172 DEBUG (MainThread) [custom_components.powercalc.sensors.utility_meter] Creating utility_meter sensor: Suszarka Energy Calc Energysensor daily (entity_id=sensor.suszarka_energy_calc_energysensor_daily)
2023-01-07 14:17:51.172 DEBUG (MainThread) [custom_components.powercalc.sensors.utility_meter] Creating utility_meter sensor: Suszarka Energy Calc Energysensor weekly (entity_id=sensor.suszarka_energy_calc_energysensor_weekly)
2023-01-07 14:17:51.173 DEBUG (MainThread) [custom_components.powercalc.sensors.utility_meter] Creating utility_meter sensor: Suszarka Energy Calc Energysensor monthly (entity_id=sensor.suszarka_energy_calc_energysensor_monthly)
2023-01-07 14:17:51.174 DEBUG (MainThread) [custom_components.powercalc.power_profile.model_discovery]

@salut1a All these logs don't help further as they don't provide any information as to why the entities are not created, so please don't post them anymore to not pollute the issue. As long as you see Creating utility_meter sensor: than powercalc has correctly delegated entity creation to HA. Something goes wrong in HA internals, but I have no clue.
To progress any further you really have to answer the questions.

How many powercalc sensors do you have setup?
Are all powercalc sensors based on a source sensor from the Tuya integration or also other integrations?
If also other integrations, are these powercalc entities correctly? Previously you said none of the powercalc sensors were created after startup, but on one of your last comments you said they are created correctly with the Z2M integration.

The goal is to find the culprit by finding a pattern. When only the Tuya integration causes issues than we have something to go forward with.

Unless the PowerCalc just starts earlier than the Tuya and therefore the entities do not form

I have now 6 powercalc sensors (I'm starting my adventure with HA)
1 is Broadlink (working), 2 Z2M (working) and 3 older Tuya (need reloading)
these 2 already have their own energy entity and the 3 older ones are only with the power entity
because I forgot that I tested different options and left create energy and meters disabled. Currently I have this set:
powercalc:
energy_sensor_precision: 2
force_update_frequency: 00:00:15
create_energy_sensors: true
enable_autodiscovery: false

energy_sensor_naming: "{} Energysensor"
power_sensor_naming: "{} Powersensor"
create_utility_meters: true
so sometimes I get mixed up with settings, integrations, etc.
But I also think the problem is with Tuya
by the way, you can create powercalc entities for a device that consumes variable power over time, e.g. air conditioning, for now I use the Riemann integral for it.
Sorry for too many logos but I wanted to provide as much information as possible.

We all started once. HA has all kind of terminology which you'll need to get familiar with. It's a whole voyage ;-)
Ok good to know, it seems definitely a problem with the Tuya based sensors.
I think I might need to buy some hardware to see if I can reproduce. What would I need exactly, cheapest option?
One question. Could you click on the three dots on the right bottom for one of the problematic Tuya sensors and Download diagnostics. Than share it here.

create_energy_sensors option will just create a Riemann integral sensor under the hood. This would be similar to creating a Riemann sensor using the HA helpers.
create_utility_meters option will create utility meters, same as with the HA helpers.
The options are just there to easily create these directly for you virtual power sensors (without needing to setup the helpers manually), but when you already have a real power sensor (for the air conditioner) there is no real advantage to do it via powercalc.
You can however using the power_sensor_id and energy_sensor_id option to refer to an existing power sensor, see the readme.

https://pl.aliexpress.com/item/4000478798085.html?spm=a2g0o.order_list.order_list_main.153.56091c242LTl4D&gatewayAdapt=glo2pol
I am looking for the best solution to evaluate the daily, monthly and total energy consumption for a meter that gives only power to HA through Tuya integration (although the smart application has access to daily and total energy). At constant power it works great for variables I use helper.
config_entry-powercalc-6504adf033da32916027e9aafa626f2b.json.txt

I will see, it will take a few weeks for order at aliexpress to arrive to the Netherlands.
Could you try one final thing and that is defining a unique_id yourself when setting up a new powercalc sensor with the GUI. First remove one of the Tuya entries from powercalc. And next add it again but fill in a unique_id.
Try restarting another time and see if it survives restarts now without the need to reload.
You could also have a look into creating the power sensors for Tuya using the YAML configuration, as it was also found in the other referenced issue that it was working (also after restarts) with YAML.
sensor:
  - platform: powercalc
    entity_id: sensor.aubess_smart_socket_20a_em_power
    name: Lustro Energia
    create_utility_meters: true
    standby_power: 0.2
    ignore_unavailable_state: true
    fixed:
      power: 320

Unfortunately, giving unique_id did not help
super :) Typing the definition into sensor.yaml worked for me enough success :)
Extra super thank you for your help, very much, I will only be left with the correct choice of calculation method for devices that only transmit power entities to have a day, a month, full
As I choose the method of integration on left, because it should be from the description of the settings, the sensor calculates too high energy consumption by converting power to daily consumption in kWh

I think I have found the issue by digging through the Tuya integration source code.
There is some logic in place which migrates entities have unique id tuya.xxxxx to a new format. This happens during startup. Looking at the diagnostics of your powercalc config entry the unique id is tuya.bf6a6bfb475e1f6942h32ycur_power. Tuya is modifying and breaking the powercalc entities because it sees this unique id.
I will make some changes in powercalc code to make the unique id prefix with pc_ or something like that to circumvent this issue.

I have a fix now in the master branch. Are you able to install that with HACS? You'll need to click redownload en also check the beta checkbox.
After that you'll need to add the power sensor for the Tuya switch again with the GUI, and you can remove from the YAML.
Now after each restart it will hopefully persist.
Are you able to test that?

ok will it work with my HA 2022.11.4

Yes it will work with your HA version, but you don't need powercalc 1.2.4, but install the master branch.
Click redownload on integration page in HACS.

when I created a new powercalc and gave reload, no entities are created

I doubt you are on latest master as the unique id in your config entry is still the same:
"unique_id": "tuya.bf6a6bfb475e1f6942h32ycur_power",
It should be the following now:
"unique_id": "pc_tuya.bf6a6bfb475e1f6942h32ycur_power",
Did you restart HA first after you redownloaded powercalc master branch?

I gave reload I have now versions 1.2.4

You must have master not 1.2.4, see my screenshots above...

ok i changed to master. i just directly treated your sreen where it was highlighted 1.2.4 :)

config_entry-powercalc-d47108ccfc03f84be80f42f8198a4438.json.txt

entity not created requires reload

You are sure you did delete the config entry before and created a new one?
With "Add integration" button.

I gave a different name I thought a new powercalc would be created, one moment :)

deleted, restarted, created a new one in gui, not auto create
config_entry-powercalc-bcbe4aaac4acfb9980d278dc6cc655ee.json.txt

Very strange, as your unique id is still the same. Is suspect you are still on an old version of powercalc somehow.
Anyway I will release to v1.2.5 soon. Then you can try again.
When it is still not working I will go forward an order some Tuya device at aliexpress to do some further testing myself.

for me the version of the entries in sensors.yaml is a very good solution.

to be sure, I gave reload master + restart + create new sensor again, it does not create, but for me the entry in yaml is enough
config_entry-powercalc-8c50cf2e2043c1c0273b46c35bab867a.json.txt

Closing this issue, as YAML is ok for you. Maybe my fix did the magic for others. I have ordered a Tuya switch anyhow, so when that arrives in coming weeks I'll also be able to test myself.

I see that you already closed this issue, but just wanted to let you know that I am seeing the same issue with all of my ESPHome devices. Other type of devices work fine.
Might be useful information :)


No CMAKE_CUDA_COMPILER could be found.

Hi!
Unable to build GPU support. Please help.
I had tried VS 2017 with CUDA 8.0, 9.0, 10.0, 10.1 and 10.2 and also VS 2019 with CUDA 10.2. I am installing on Windows 10 inside Anaconda Prompt.
Below reports show details of my software and failure report.

You should be able to install pre-built XGBoost from PyPI, by running:
python -m pip install xgboost

It supports GPU out of the box.

Oh. Thanks! Silly me. XGBOOST crew need to make it more obvious in the documentation section. Issue resolved.


my rule can alertd at 'elastalert-test-rule' mode with '--alert',but not work at 'elastalert' mode

Hello,I write a rule to watch nginx logs,the rule workd at 'elastalert-test-rule' mode with  '--alert', it send email success, but when I run it in 'elastalert',It can't work,Is there an error in my configuration file?please help me.Thinks .
My OS is CentOS Linux release 7.6.1810 (Core) , elasticsearch version is 5.6.1,  python version is 3.7.4 and elastalert version is 0.2.4.
here is my  config.yaml:
rules_folder: /etc/elastalert/rules
run_every:
  minutes: 1
buffer_time:
  minutes: 15
es_host: <IP_ADDRESS>
es_port: 9200
writeback_index: elastalert_status
writeback_alias: elastalert_alerts
alert_time_limit:
  days: 2

and here is my rule.yaml:
es_host: <IP_ADDRESS>
es_port: 9200
name: 502 error
type: frequency
index: access-*
num_events: 10
timeframe:
  minutes: 1
filter:
- term:
    status: "502"
alert_text: "Nginx has {0} 502 now!"
alert_text_args:
  - num_hits
smtp_host: smtp.XXX.com
smtp_port: 25
smtp_auth_file: /etc/elastaler/smtp_auth_file.yaml
email_reply_to<EMAIL_ADDRESS>from_addr<EMAIL_ADDRESS>alert:
- email

email:
-<EMAIL_ADDRESS>
when I run it at 'elastalert-test-rule' mode with  '--alert',here is output, and it send a email to me.
# /opt/python3.74/bin/elastalert-test-rule  --config /etc/elastalert/config.yaml /etc/elastalert/rules/502.yaml --alert
Didn't get any results.
1 rules loaded
INFO:apscheduler.scheduler:Adding job tentatively -- it will be properly scheduled when the scheduler starts
INFO:elastalert:Queried rule 502 error from 2020-09-25 16:23 CST to 2020-09-25 16:24 CST: 26 / 26 hits
INFO:elastalert:Sent email to<EMAIL_ADDRESS>INFO:elastalert:Ignoring match for silenced rule 502 error

Would have written the following documents to writeback index (default is elastalert_status):

silence - {'exponent': 0, 'rule_name': '502 error', '@timestamp': datetime.datetime(2020, 9, 25, 8, 24, 57, 783966, tzinfo=tzutc()), 'until': datetime.datetime(2020, 9, 25, 8, 25, 57, 783945, tzinfo=tzutc())}

elastalert - {'match_body': {'date': '20200925', 'TT': '25/Sep/2020:16:24:17 +0800', '------some other log body -----, 'status': 502, '_id': 'AXTEXTSDBClKD64H2ie5', '_index': 'access-2020.09.25', '_type': 'fluentd', 'num_hits': 26, 'num_matches': 2}, 'rule_name': '502 error', 'alert_info': {'type': 'email', 'recipients'<EMAIL_ADDRESS>'alert_sent': True, 'alert_time': datetime.datetime(2020, 9, 25, 8, 24, 57, 784562, tzinfo=tzutc()), 'match_time': '2020-09-25T16:24:17.315257+08:00'}

elastalert_status - {'rule_name': '502 error', 'endtime': datetime.datetime(2020, 9, 25, 8, 24, 57, 595284, tzinfo=tzutc()), 'starttime': datetime.datetime(2020, 9, 25, 8, 23, 56, 995284, tzinfo=tzutc()), 'matches': 2, 'hits': 26, '@timestamp': datetime.datetime(2020, 9, 25, 8, 24, 59, 413644, tzinfo=tzutc()), 'time_taken': 1.774747610092163}

but when I run it use  'elastalert',the out put is like that,and it not work,:
# /opt/python3.74/bin/python3.7 -m elastalert.elastalert --verbose  --config /etc/elastalert/config.yaml
1 rules loaded
INFO:elastalert:Starting up
INFO:elastalert:Disabled rules are: []
INFO:elastalert:Sleeping for 59.999901 seconds
INFO:elastalert:Disabled rules are: []
INFO:elastalert:Sleeping for 59.99972 seconds
INFO:elastalert:Background configuration change check run at 2020-09-25 16:37 CST
INFO:elastalert:Background alerts thread 0 pending alerts sent at 2020-09-25 16:37 CST
INFO:elastalert:Background configuration change check run at 2020-09-25 16:38 CST
INFO:elastalert:Background alerts thread 0 pending alerts sent at 2020-09-25 16:38 CST
INFO:elastalert:Disabled rules are: []
INFO:elastalert:Sleeping for 59.999808 seconds
INFO:elastalert:Background alerts thread 0 pending alerts sent at 2020-09-25 16:39 CST
INFO:elastalert:Background configuration change check run at 2020-09-25 16:39 CST
INFO:elastalert:Disabled rules are: []
INFO:elastalert:Sleeping for 59.999712 seconds

any body here?

me too

Ok perhaps I come to reply a bit late... If the elastalert-test-rule works but the rule does NOT seem to work when run by elastalert, check that your timestamp is not offset. By default Elastalert looks for entries that have appeared in the last minute.
If your timestamps are not correctly set (typically I myself made a mistake with a date parser and all my timestamps were 1 hour "older" than what they should have been) then Elastalert will not pick up the events, but since elastalert-test-rule looks for matches in the last 24 hours it will pick those events up.
Hope this heps


Assigning the same variable to itself at variable definition statement, does not semantically fail

Below should semantically fail
string s = s;

Currently, it passes the semantic checks but throws the below error at runtime.
error: ballerina.lang.errors:Error, message: 1
	at main(mainFunction.bal:13)

Fixed in v0.95.1.
Gets the below error now:
error: mainFunction.bal:3:14: self referenced variable 's'


fixes #3509

Fixes #3509
Proposed Changes

Rename config-kafka-features feature flags to be consistent with eventing core feature flag names

Hello @cdalar,
thanks for your PR. As we squash the commits and use the PR title as commit message, can you please rename the PR to something meaningful? And as this is a user facing change, can you please add a release note comment in the PR description:
via
https://github.com/knative-extensions/eventing-kafka-broker/blob/ddd03f9fcdb16b928e5662ff1f3c9ff3ca97f176/.github/pull-request-template.md?plain=1#L34-L36
/ok-to-test

Test failures are unrelated

/retest

@cdalar thanks a lot for fixing this :+1:
Lately some tests are flaky. You can simply retrigger a retest via the following:
/retest


xen fails to build on unstable

Describe the bug
Xen is not building this is the error:
builder for '/nix/store/m4id5qm2a742c11xzrx03ix1z29jwxps-xen-4.10.4.drv' failed with exit code 2; last 10 log lines:
  make[5]: Leaving directory '/build/xen-4.10.4/tools/firmware'
  make[4]: *** [Makefile:37: all] Error 2
  make[4]: Leaving directory '/build/xen-4.10.4/tools/firmware'
  make[3]: *** [/build/xen-4.10.4/tools/../tools/Rules.mk:245: subdir-install-firmware] Error 2
  make[3]: Leaving directory '/build/xen-4.10.4/tools'
  make[2]: *** [/build/xen-4.10.4/tools/../tools/Rules.mk:240: subdirs-install] Error 2
  make[2]: Leaving directory '/build/xen-4.10.4/tools'
  make[1]: *** [Makefile:74: install] Error 2
  make[1]: Leaving directory '/build/xen-4.10.4/tools'
  make: *** [Makefile:127: install-tools] Error 2

To Reproduce
Steps to reproduce the behavior:

nix-shell -p xen
The error

Expected behavior
A clear and concise description of what you expected to happen.
Screenshots
If applicable, add screenshots to help explain your problem.
Additional context
Add any other context about the problem here.
Notify maintainers

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.

system: "x86_64-linux"
host os: Linux 5.10.4, NixOS, 21.03.20210104.1a57d96 (Okapi)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.4pre20201201_5a6ddb3
channels(root): "nixos-21.03pre250162.34ad166a830"
nixpkgs: /etc/nixpkgs

Maintainer information:
# a list of nixpkgs attributes affected by the problem
attribute:
# a list of nixos modules affected by the problem
module:

Actual error (from nix log nixpkgs.xen or Hydra):
drivers/infiniband/flexboot_nodnic.c: In function 'flexboot_nodnic_create_qp':
drivers/infiniband/flexboot_nodnic.c:368:53: error: implicit conversion from 'enum ib_queue_pair_type' to 'nodnic_queue_pair_type' [8;;https://gcc.gnu.org/on
linedocs/gcc/Warning-Options.html#index-Wenum-conversion^G-Werror=enum-conversion8;;^G]
  368 |  status = nodnic_port_create_qp(&port->port_priv, qp->type,
      |                                                   ~~^~~~~~
drivers/infiniband/flexboot_nodnic.c: In function 'flexboot_nodnic_destroy_qp':
drivers/infiniband/flexboot_nodnic.c:409:45: error: implicit conversion from 'enum ib_queue_pair_type' to 'nodnic_queue_pair_type' [8;;https://gcc.gnu.org/on
linedocs/gcc/Warning-Options.html#index-Wenum-conversion^G-Werror=enum-conversion8;;^G]
  409 |  nodnic_port_destroy_qp(&port->port_priv, qp->type,
      |                                           ~~^~~~~~

Possibly triggered by the GCC 10 upgrade.

Actual error (from nix log nixpkgs.xen or Hydra):
drivers/infiniband/flexboot_nodnic.c: In function 'flexboot_nodnic_create_qp':
drivers/infiniband/flexboot_nodnic.c:368:53: error: implicit conversion from 'enum ib_queue_pair_type' to 'nodnic_queue_pair_type' [8;;https://gcc.gnu.org/on
linedocs/gcc/Warning-Options.html#index-Wenum-conversion^G-Werror=enum-conversion8;;^G]
  368 |  status = nodnic_port_create_qp(&port->port_priv, qp->type,
      |                                                   ~~^~~~~~
drivers/infiniband/flexboot_nodnic.c: In function 'flexboot_nodnic_destroy_qp':
drivers/infiniband/flexboot_nodnic.c:409:45: error: implicit conversion from 'enum ib_queue_pair_type' to 'nodnic_queue_pair_type' [8;;https://gcc.gnu.org/on
linedocs/gcc/Warning-Options.html#index-Wenum-conversion^G-Werror=enum-conversion8;;^G]
  409 |  nodnic_port_destroy_qp(&port->port_priv, qp->type,
      |                                           ~~^~~~~~

Possibly triggered by the GCC 10 upgrade.

@andersk  I found this patch https://lists.ipxe.org/pipermail/ipxe-devel/2020-May/007047.html

@andersk  I found this patch https://lists.ipxe.org/pipermail/ipxe-devel/2020-May/007047.html

Also, it seems to me that Xen is not needed in gnome-boxes. I created an overlay removing xen from buildInputs and it builds without a problem. Also I saw that there is no Xen as dependency in Gnome-boxes Flatpak neither in its Debian Package.

Also, it seems to me that Xen is not needed in gnome-boxes. I created an overlay removing xen from buildInputs and it builds without a problem. Also I saw that there is no Xen as dependency in Gnome-boxes Flatpak neither in its Debian Package.

Also, it seems to me that Xen is not needed in gnome-boxes. I created an overlay removing xen from buildInputs and it builds without a problem. Also I saw that there is no Xen as dependency in Gnome-boxes Flatpak neither in its Debian Package.

Can confirm here, also I am bit confused too, in my case xen is failing to build for libguestfs which in turn is needed for vagrant, and I did not understand why, from a quick search Debian neither Arch uses xen as a dep in neither of this packages.

Also, it seems to me that Xen is not needed in gnome-boxes. I created an overlay removing xen from buildInputs and it builds without a problem. Also I saw that there is no Xen as dependency in Gnome-boxes Flatpak neither in its Debian Package.

Can confirm here, also I am bit confused too, in my case xen is failing to build for libguestfs which in turn is needed for vagrant, and I did not understand why, from a quick search Debian neither Arch uses xen as a dep in neither of this packages.

I submitted a PR to remove Xen as dependency from Gnome-boxes. https://github.com/NixOS/nixpkgs/pull/108716

I submitted a PR to remove Xen as dependency from Gnome-boxes. https://github.com/NixOS/nixpkgs/pull/108716

Guys I am a bit lost here, I failed to apply the patches here, one motive is that is for 4.13+ and we are in 4.10, other is the needed options for building in GCC10, I do not know exactly where to put it, based on the patches from Gentoo (xen-tools-4.13.0-gcc10.patch and xen-tools-4.13.0-ipxe-gcc10.patch, available here https://github.com/hydrapolic/gentoo-dist/blob/master/xen/xen-gentoo-patches-21.tar.xz and here https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ab132ad91fa4e41eca3bc48eebae586c6ba58a11) the IPXE one, set the CFLAGS for the whole project, for example:
diff --git a/src/Makefile b/src/Makefile
index d74565d..2ad5b39 100644
--- a/src/Makefile
+++ b/src/Makefile
@@ -4,7 +4,7 @@
 #

 CLEANUP                :=
-CFLAGS         :=
+CFLAGS         := -Wno-enum-conversion -Wno-array-bounds -fcommon
 ASFLAGS                :=
 LDFLAGS                :=
 HOST_CFLAGS    :=

The other patch changes some little things plus a modifies a CFLAG for a specific module:
--- xen-4.13.0/tools/xenstore/utils.h.orig	2019-12-17 14:23:09.000000000 +0000
+++ xen-4.13.0/tools/xenstore/utils.h	2020-01-21 21:13:05.108957447 +0000
@@ -24,7 +24,7 @@
 void barf(const char *fmt, ...) __attribute__((noreturn));
 void barf_perror(const char *fmt, ...) __attribute__((noreturn));

-void (*xprintf)(const char *fmt, ...);
+extern void (*xprintf)(const char *fmt, ...);

 #define eprintf(_fmt, _args...) xprintf("[ERR] %s" _fmt, __FUNCTION__, ##_args)

--- xen-4.13.0/tools/xenstore/xenstored_core.h.orig	2020-01-21 21:15:19.243931307 +0000
+++ xen-4.13.0/tools/xenstore/xenstored_core.h	2020-01-21 21:38:35.340617819 +0000
@@ -204,7 +204,7 @@
 /* Open a pipe for signal handling */
 void init_pipe(int reopen_log_pipe[2]);

-xengnttab_handle **xgt_handle;
+extern xengnttab_handle **xgt_handle;

 int remember_string(struct hashtable *hash, const char *str);

--- xen-4.13.0/tools/libxl/libxlu_pci.c.orig	2019-12-17 14:23:09.000000000 +0000
+++ xen-4.13.0/tools/libxl/libxlu_pci.c	2020-01-21 21:56:26.812212916 +0000
@@ -48,7 +48,7 @@
 int xlu_pci_parse_bdf(XLU_Config *cfg, libxl_device_pci *pcidev, const char *str)
 {
     unsigned state = STATE_DOMAIN;
-    unsigned dom, bus, dev, func, vslot = 0;
+    unsigned dom = 0, bus = 0, dev = 0, func = 0, vslot = 0;
     char *buf2, *tok, *ptr, *end, *optkey = NULL;

     if ( NULL == (buf2 = ptr = strdup(str)) )
--- xen-4.13.0/tools/libxl/libxl_utils.c.orig	2019-12-17 14:23:09.000000000 +0000
+++ xen-4.13.0/tools/libxl/libxl_utils.c	2020-01-21 22:34:52.096300774 +0000
@@ -1259,7 +1259,7 @@
     }
     memset(un, 0, sizeof(struct sockaddr_un));
     un->sun_family = AF_UNIX;
-    strncpy(un->sun_path, path, sizeof(un->sun_path));
+    strncpy(un->sun_path, path, sizeof(un->sun_path)-1);
     return 0;
 }

--- xen-4.13.0/tools/debugger/kdd/kdd.h.orig	2019-12-17 14:23:09.000000000 +0000
+++ xen-4.13.0/tools/debugger/kdd/kdd.h	2020-01-21 23:35:55.458605582 +0000
@@ -323,7 +323,7 @@
         kdd_msg msg;
         kdd_reg reg;
         kdd_stc stc;
-        uint8_t payload[0];
+        uint8_t payload[65535];
     };
 } PACKED kdd_pkt;

--- xen-4.13.0/tools/xenpmd/Makefile.orig	2019-12-17 14:23:09.000000000 +0000
+++ xen-4.13.0/tools/xenpmd/Makefile	2020-01-22 22:13:16.564873608 +0000
@@ -3,6 +3,7 @@

 CFLAGS += -Werror
 CFLAGS += $(CFLAGS_libxenstore)
+CFLAGS += -Wno-error=format-truncation

 LDLIBS += $(LDLIBS_libxenstore)

But there is no definition for this in our makefile (source https://github.com/xen-project/xen/blob/stable-4.10/Makefile).
I did try to add it on NIX_CFLAGS_COMPILE as 50dad9e873d5ee60f008ab0d415afde7b4f3acdd did
But adding --fcommon gives error on the configuration step:
configure: running /nix/store/zcl19h06322c3kss6bvf05w2pxg4kfll-bash-4.4-p23/bin/bash ./configure --disable-option-checking '--prefix=/nix/store/9ajj3drb9aqgin2qjqnyiab54x40h52d-xen-4.10.4'  '--enable-qemu-traditional' --cache-file=/dev/null --srcdir=.
configure: WARNING: Setting CC, CFLAGS, LDFLAGS, LIBS, CPPFLAGS or CPP is not recommended, use PREPEND_INCLUDES, PREPEND_LIB, APPEND_INCLUDES and APPEND_LIB instead when possible.
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/build/xen-4.10.4/tools':
configure: error: C compiler cannot create executables
See `config.log' for more details
configure: error: ./configure failed for tools
builder for '/nix/store/b4wv1j8wmn2d4x35p6rp4s19v0g6qjiq-xen-4.10.4.drv' failed with exit code 77
cannot build derivation '/nix/store/xh360fdfvisvvxb5wj7nzbismdrlnli7-libguestfs-1.40.2.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/n319dgfqmv0vmn3322wrj731yqasvc9r-vagrant-2.2.14.drv': 1 dependencies couldn't be built

Without it, advances a lit bit more but also fails:
cc1plus: error: command-line option '-Wno-enum-conversion' is valid for C/ObjC but not for C++ [-Werror]
cc1plus: all warnings being treated as errors
make[10]: *** [Makefile:123: headers++.chk] Error 1
rm compat/callback.c compat/memory.c compat/arch-x86/xen-mca.c compat/tmem.c compat/arch-x86/xen-x86_32.c compat/nmi.c compat/hvm/hvm_vcpu.c compat/grant_table.c compat/physdev.c compat/version.c compat/hvm/dm_op.c compat/sched.c compat/trace.c compat/xenoprof.c compat/features.c compat/arch-x86_32.c compat/kexec.c compat/platform.c compat/arch-x86/pmu.c compat/arch-x86/xen.c compat/pmu.c compat/xen.c compat/vcpu.c
make[10]: Leaving directory '/build/xen-4.10.4/tools/firmware/xen-dir/xen-root/xen/include'
make[9]: *** [Makefile:142: /build/xen-4.10.4/tools/firmware/xen-dir/xen-root/xen/xen] Error 2
make[9]: Leaving directory '/build/xen-4.10.4/tools/firmware/xen-dir/xen-root/xen'
make[8]: *** [Makefile:45: build] Error 2
make[8]: Leaving directory '/build/xen-4.10.4/tools/firmware/xen-dir/xen-root/xen'
make[7]: *** [Makefile:51: xen-shim] Error 2
make[7]: Leaving directory '/build/xen-4.10.4/tools/firmware/xen-dir'
make[6]: *** [/build/xen-4.10.4/tools/firmware/../../tools/Rules.mk:245: subdir-all-xen-dir] Error 2
make[6]: Leaving directory '/build/xen-4.10.4/tools/firmware'
make[5]: *** [/build/xen-4.10.4/tools/firmware/../../tools/Rules.mk:240: subdirs-all] Error 2
make[5]: Leaving directory '/build/xen-4.10.4/tools/firmware'
make[4]: *** [Makefile:37: all] Error 2
make[4]: Leaving directory '/build/xen-4.10.4/tools/firmware'
make[3]: *** [/build/xen-4.10.4/tools/../tools/Rules.mk:245: subdir-install-firmware] Error 2
make[3]: Leaving directory '/build/xen-4.10.4/tools'
make[2]: *** [/build/xen-4.10.4/tools/../tools/Rules.mk:240: subdirs-install] Error 2
make[2]: Leaving directory '/build/xen-4.10.4/tools'
make[1]: *** [Makefile:74: install] Error 2
make[1]: Leaving directory '/build/xen-4.10.4/tools'
make: *** [Makefile:127: install-tools] Error 2
builder for '/nix/store/vrsgfvq6sq692c8l19xn9zgaj4c1lxvv-xen-4.10.4.drv' failed with exit code 2
cannot build derivation '/nix/store/b8f0mhll77v62hcfgkkpxm1c8kb9l7j9-libguestfs-1.40.2.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/15g9m9x2r5cmrvjya4xx51s1m67mxvh0-vagrant-2.2.14.drv': 1 dependencies couldn't be built

From a bit more of research, Vagrant depends on libguestfs because of the libvirt plugin, which in turn depends on xen, I think is better to version bump our xen then patches it for GCC10.
For now I using (vagrant.override { withLibvirt = false; }) on home-manager.users.bryan.home.packages. At least I can use Virtualbox for quick experiments.

Guys I am a bit lost here, I failed to apply the patches here, one motive is that is for 4.13+ and we are in 4.10, other is the needed options for building in GCC10, I do not know exactly where to put it, based on the patches from Gentoo (xen-tools-4.13.0-gcc10.patch and xen-tools-4.13.0-ipxe-gcc10.patch, available here https://github.com/hydrapolic/gentoo-dist/blob/master/xen/xen-gentoo-patches-21.tar.xz and here https://gitweb.gentoo.org/repo/gentoo.git/commit/?id=ab132ad91fa4e41eca3bc48eebae586c6ba58a11) the IPXE one, set the CFLAGS for the whole project, for example:
diff --git a/src/Makefile b/src/Makefile
index d74565d..2ad5b39 100644
--- a/src/Makefile
+++ b/src/Makefile
@@ -4,7 +4,7 @@
 #

 CLEANUP                :=
-CFLAGS         :=
+CFLAGS         := -Wno-enum-conversion -Wno-array-bounds -fcommon
 ASFLAGS                :=
 LDFLAGS                :=
 HOST_CFLAGS    :=

The other patch changes some little things plus a modifies a CFLAG for a specific module:
--- xen-4.13.0/tools/xenstore/utils.h.orig	2019-12-17 14:23:09.000000000 +0000
+++ xen-4.13.0/tools/xenstore/utils.h	2020-01-21 21:13:05.108957447 +0000
@@ -24,7 +24,7 @@
 void barf(const char *fmt, ...) __attribute__((noreturn));
 void barf_perror(const char *fmt, ...) __attribute__((noreturn));

-void (*xprintf)(const char *fmt, ...);
+extern void (*xprintf)(const char *fmt, ...);

 #define eprintf(_fmt, _args...) xprintf("[ERR] %s" _fmt, __FUNCTION__, ##_args)

--- xen-4.13.0/tools/xenstore/xenstored_core.h.orig	2020-01-21 21:15:19.243931307 +0000
+++ xen-4.13.0/tools/xenstore/xenstored_core.h	2020-01-21 21:38:35.340617819 +0000
@@ -204,7 +204,7 @@
 /* Open a pipe for signal handling */
 void init_pipe(int reopen_log_pipe[2]);

-xengnttab_handle **xgt_handle;
+extern xengnttab_handle **xgt_handle;

 int remember_string(struct hashtable *hash, const char *str);

--- xen-4.13.0/tools/libxl/libxlu_pci.c.orig	2019-12-17 14:23:09.000000000 +0000
+++ xen-4.13.0/tools/libxl/libxlu_pci.c	2020-01-21 21:56:26.812212916 +0000
@@ -48,7 +48,7 @@
 int xlu_pci_parse_bdf(XLU_Config *cfg, libxl_device_pci *pcidev, const char *str)
 {
     unsigned state = STATE_DOMAIN;
-    unsigned dom, bus, dev, func, vslot = 0;
+    unsigned dom = 0, bus = 0, dev = 0, func = 0, vslot = 0;
     char *buf2, *tok, *ptr, *end, *optkey = NULL;

     if ( NULL == (buf2 = ptr = strdup(str)) )
--- xen-4.13.0/tools/libxl/libxl_utils.c.orig	2019-12-17 14:23:09.000000000 +0000
+++ xen-4.13.0/tools/libxl/libxl_utils.c	2020-01-21 22:34:52.096300774 +0000
@@ -1259,7 +1259,7 @@
     }
     memset(un, 0, sizeof(struct sockaddr_un));
     un->sun_family = AF_UNIX;
-    strncpy(un->sun_path, path, sizeof(un->sun_path));
+    strncpy(un->sun_path, path, sizeof(un->sun_path)-1);
     return 0;
 }

--- xen-4.13.0/tools/debugger/kdd/kdd.h.orig	2019-12-17 14:23:09.000000000 +0000
+++ xen-4.13.0/tools/debugger/kdd/kdd.h	2020-01-21 23:35:55.458605582 +0000
@@ -323,7 +323,7 @@
         kdd_msg msg;
         kdd_reg reg;
         kdd_stc stc;
-        uint8_t payload[0];
+        uint8_t payload[65535];
     };
 } PACKED kdd_pkt;

--- xen-4.13.0/tools/xenpmd/Makefile.orig	2019-12-17 14:23:09.000000000 +0000
+++ xen-4.13.0/tools/xenpmd/Makefile	2020-01-22 22:13:16.564873608 +0000
@@ -3,6 +3,7 @@

 CFLAGS += -Werror
 CFLAGS += $(CFLAGS_libxenstore)
+CFLAGS += -Wno-error=format-truncation

 LDLIBS += $(LDLIBS_libxenstore)

But there is no definition for this in our makefile (source https://github.com/xen-project/xen/blob/stable-4.10/Makefile).
I did try to add it on NIX_CFLAGS_COMPILE as 50dad9e873d5ee60f008ab0d415afde7b4f3acdd did
But adding --fcommon gives error on the configuration step:
configure: running /nix/store/zcl19h06322c3kss6bvf05w2pxg4kfll-bash-4.4-p23/bin/bash ./configure --disable-option-checking '--prefix=/nix/store/9ajj3drb9aqgin2qjqnyiab54x40h52d-xen-4.10.4'  '--enable-qemu-traditional' --cache-file=/dev/null --srcdir=.
configure: WARNING: Setting CC, CFLAGS, LDFLAGS, LIBS, CPPFLAGS or CPP is not recommended, use PREPEND_INCLUDES, PREPEND_LIB, APPEND_INCLUDES and APPEND_LIB instead when possible.
checking build system type... x86_64-unknown-linux-gnu
checking host system type... x86_64-unknown-linux-gnu
checking for gcc... gcc
checking whether the C compiler works... no
configure: error: in `/build/xen-4.10.4/tools':
configure: error: C compiler cannot create executables
See `config.log' for more details
configure: error: ./configure failed for tools
builder for '/nix/store/b4wv1j8wmn2d4x35p6rp4s19v0g6qjiq-xen-4.10.4.drv' failed with exit code 77
cannot build derivation '/nix/store/xh360fdfvisvvxb5wj7nzbismdrlnli7-libguestfs-1.40.2.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/n319dgfqmv0vmn3322wrj731yqasvc9r-vagrant-2.2.14.drv': 1 dependencies couldn't be built

Without it, advances a lit bit more but also fails:
cc1plus: error: command-line option '-Wno-enum-conversion' is valid for C/ObjC but not for C++ [-Werror]
cc1plus: all warnings being treated as errors
make[10]: *** [Makefile:123: headers++.chk] Error 1
rm compat/callback.c compat/memory.c compat/arch-x86/xen-mca.c compat/tmem.c compat/arch-x86/xen-x86_32.c compat/nmi.c compat/hvm/hvm_vcpu.c compat/grant_table.c compat/physdev.c compat/version.c compat/hvm/dm_op.c compat/sched.c compat/trace.c compat/xenoprof.c compat/features.c compat/arch-x86_32.c compat/kexec.c compat/platform.c compat/arch-x86/pmu.c compat/arch-x86/xen.c compat/pmu.c compat/xen.c compat/vcpu.c
make[10]: Leaving directory '/build/xen-4.10.4/tools/firmware/xen-dir/xen-root/xen/include'
make[9]: *** [Makefile:142: /build/xen-4.10.4/tools/firmware/xen-dir/xen-root/xen/xen] Error 2
make[9]: Leaving directory '/build/xen-4.10.4/tools/firmware/xen-dir/xen-root/xen'
make[8]: *** [Makefile:45: build] Error 2
make[8]: Leaving directory '/build/xen-4.10.4/tools/firmware/xen-dir/xen-root/xen'
make[7]: *** [Makefile:51: xen-shim] Error 2
make[7]: Leaving directory '/build/xen-4.10.4/tools/firmware/xen-dir'
make[6]: *** [/build/xen-4.10.4/tools/firmware/../../tools/Rules.mk:245: subdir-all-xen-dir] Error 2
make[6]: Leaving directory '/build/xen-4.10.4/tools/firmware'
make[5]: *** [/build/xen-4.10.4/tools/firmware/../../tools/Rules.mk:240: subdirs-all] Error 2
make[5]: Leaving directory '/build/xen-4.10.4/tools/firmware'
make[4]: *** [Makefile:37: all] Error 2
make[4]: Leaving directory '/build/xen-4.10.4/tools/firmware'
make[3]: *** [/build/xen-4.10.4/tools/../tools/Rules.mk:245: subdir-install-firmware] Error 2
make[3]: Leaving directory '/build/xen-4.10.4/tools'
make[2]: *** [/build/xen-4.10.4/tools/../tools/Rules.mk:240: subdirs-install] Error 2
make[2]: Leaving directory '/build/xen-4.10.4/tools'
make[1]: *** [Makefile:74: install] Error 2
make[1]: Leaving directory '/build/xen-4.10.4/tools'
make: *** [Makefile:127: install-tools] Error 2
builder for '/nix/store/vrsgfvq6sq692c8l19xn9zgaj4c1lxvv-xen-4.10.4.drv' failed with exit code 2
cannot build derivation '/nix/store/b8f0mhll77v62hcfgkkpxm1c8kb9l7j9-libguestfs-1.40.2.drv': 1 dependencies couldn't be built
cannot build derivation '/nix/store/15g9m9x2r5cmrvjya4xx51s1m67mxvh0-vagrant-2.2.14.drv': 1 dependencies couldn't be built

From a bit more of research, Vagrant depends on libguestfs because of the libvirt plugin, which in turn depends on xen, I think is better to version bump our xen then patches it for GCC10.
For now I using (vagrant.override { withLibvirt = false; }) on home-manager.users.bryan.home.packages. At least I can use Virtualbox for quick experiments.

If version bumping Xen fixes this, I can’t imagine a reason that wouldn’t be our first choice—we should do it.

If version bumping Xen fixes this, I can’t imagine a reason that wouldn’t be our first choice—we should do it.

If version bumping Xen fixes this, I can’t imagine a reason that wouldn’t be our first choice—we should do it.

It will help, but we will still need patches for GCC10 until we have a release to address that (from upstream). At least that's what I understood by reading the issues and PR from the Gentoo team.

If version bumping Xen fixes this, I can’t imagine a reason that wouldn’t be our first choice—we should do it.

It will help, but we will still need patches for GCC10 until we have a release to address that (from upstream). At least that's what I understood by reading the issues and PR from the Gentoo team.

Quick update, libguestfs doesn't need xen as a dependency, I'm trying to compile it without xen to allow vagrant and friends to build it again.

Quick update, libguestfs doesn't need xen as a dependency, I'm trying to compile it without xen to allow vagrant and friends to build it again.

Ok, the bump of autoconf to 2.70 also breaks building libguestfs on unstable, on 20.09 I can build libguestfs without xen and any problem.

Ok, the bump of autoconf to 2.70 also breaks building libguestfs on unstable, on 20.09 I can build libguestfs without xen and any problem.

@bryanasdev000 I saw that autoconf needs this patch https://git.savannah.gnu.org/cgit/autoconf.git/commit/?h=branch-2.70&id=35b1708c3961dce31e4ce43014e71d77aa4b5e31

@bryanasdev000 I saw that autoconf needs this patch https://git.savannah.gnu.org/cgit/autoconf.git/commit/?h=branch-2.70&id=35b1708c3961dce31e4ce43014e71d77aa4b5e31

@bryanasdev000 I submitted a PR to remove Xen from libguestfs: https://github.com/NixOS/nixpkgs/pull/108882
I needed to change autoconf to version 2.64.

@bryanasdev000 I submitted a PR to remove Xen from libguestfs: https://github.com/NixOS/nixpkgs/pull/108882
I needed to change autoconf to version 2.64.

@bryanasdev000 I submitted a PR to remove Xen from libguestfs: #108882
I needed to change autoconf to version 2.64.

I was just trying to force the build with an older version of autoconf, I tried to update libguestfs to version 1.44, it reduced the errors but it still did not build.
Thanks! Excellent job!

@bryanasdev000 I submitted a PR to remove Xen from libguestfs: #108882
I needed to change autoconf to version 2.64.

I was just trying to force the build with an older version of autoconf, I tried to update libguestfs to version 1.44, it reduced the errors but it still did not build.
Thanks! Excellent job!

Guys with the fix of Vagrant (Libguestfs) I did not check Xen anymore, did anyone advance with that?
If not I can try to mess with it, but somebody will need to test since I don't use Xen at all.


:bug: fix(BalListItemSubtitle): Subtitle text breaks on mobile view, if right icon is present

Current Behavior
If bal-list-item-subtitle's text is long enough (at least 2 lines) AND right icon present in parent bal-list-item, the mobile view of this component (subtitle) will break, with an effect of center aligned text, as shown below

Note that there is also some padding and/or margin present around the text
Expected Behavior
It is expected for text in component to be left aligned
Steps to Reproduce

go to mobile view of this page https://baloise-design-system.vercel.app/iframe.html?args=&id=components-list--download-list&viewMode=story
add couple of lines of text to subtitle component

Version
13.4.0
Browsers
Chrome
Device
Mobile
Code Reproduction URL
No response
Additional Information
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

/cib


test: 💍 ensure the test fails

Codecov Report
Patch coverage has no change and project coverage change: -0.86 :warning:

Comparison is base (dd8f9fc) 90.26% compared to head (fee0275) 89.40%.

:exclamation: Current head fee0275 differs from pull request most recent head 5582946. Consider uploading reports for the commit 5582946 to get more accurate results

Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1414      +/-   ##
==========================================
- Coverage   90.26%   89.40%   -0.86%
==========================================
  Files         186      153      -33
  Lines       11028     7681    -3347
==========================================
- Hits         9954     6867    -3087
+ Misses       1074      814     -260

Flag
Coverage Δ

jobs_cache_maintenance
99.08% <ø> (ø)

jobs_mongodb_migration
83.49% <ø> (ø)

libs_libcommon
?

services_admin
86.05% <ø> (ø)

services_api
87.73% <ø> (ø)

services_worker
91.46% <ø> (-0.16%)
:arrow_down:

Flags with carried forward coverage won't be shown. Click here to find out more.
see 34 files with indirect coverage changes

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


[Feature] Support fe login using sql tools when no be is available.

When no backend(be) available, eg first time before setup or all be is down, we cannot login to fe using most sql tools, eg datagrip, querious.
This is because these tools call select version() or  select @@version_comment … right after login, when there is no backend available, the login will fail.
I make this pr to support login when no be available, so we can add backend or modify some configuaration using GUI sql tools, especially the first setup time.
This pr is working at precondition that，sql tools only query very simple information that fe can handle, there is no need to send the request to be.
So I check the query type and BE status, if we can handle the query and no BE is available, we will intercept and process in fe.
some screenshots

Proposed changes
Describe the big picture of your changes here to communicate to the maintainers why we should accept this pull request. If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce to Doris?
Put an x in the boxes that apply

[ ] Bugfix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation Update (if none of the other choices apply)
[ ] Code refactor (Modify the code structure, format the code, etc...)

Checklist
Put an x in the boxes that apply. You can also fill these out after creating the PR. If you're unsure about any of them, don't hesitate to ask. We're here to help! This is simply a reminder of what we are going to look for before merging your code.

[x] I have created an issue on (Fix #ISSUE) and described the bug/feature there in detail
[x] Compiling and unit tests pass locally with my changes
[x] I have added tests that prove my fix is effective or that my feature works
[x] If these changes need document changes, I have updated the document
[x] Any dependent changes have been merged

Thanks for your PR. This is indeed a problem.
But I think it could be better to handle this situation in StmtExecutor.handleQueryStmt().
Because here we have analyzed the statement, and all constant exprs has been calculated, so that we can simple check
if there is no table ref in statement and all select items are constant literal, and there is no alive backend, then return the result by FE.
This can cover more situation than only handle select version() and select @@variables;

Thanks for your PR. This is indeed a problem.
But I think it could be better to handle this situation in StmtExecutor.handleQueryStmt().
Because here we have analyzed the statement, and all constant exprs has been calculated, so that we can simple check
if there is no table ref in statement and all select items are constant literal, and there is no alive backend, then return the result by FE.
This can cover more situation than only handle select version() and select @@variables;

Good suggestion，I will move the code to handleQueryStmt and make it more general

when this pr is working, constant exprs will be handled in fe when no be is available. eg
select version()
select now()
SELECT  @@session.auto_increment_increment AS auto_increment_increment, @@character_set_client AS character_set_client, @@character_set_connection AS character_set_connection, @@character_set_results AS character_set_results, @@character_set_server AS character_set_server, @@collation_server AS collation_server, @@collation_connection AS collation_connection, @@init_connect AS init_connect, @@interactive_timeout AS interactive_timeout, @@license AS license, @@lower_case_table_names AS lower_case_table_names, @@max_allowed_packet AS max_allowed_packet, @@net_buffer_length AS net_buffer_length, @@net_write_timeout AS net_write_timeout, @@query_cache_size AS query_cache_size, @@query_cache_type AS query_cache_type, @@sql_mode AS sql_mode, @@system_time_zone AS system_time_zone, @@time_zone AS time_zone, @@tx_isolation AS transaction_isolation, @@wait_timeout AS wait_timeout

the following GUI sql tools will work without be.

DataGrip
SQLPro
Navicat for MySQL
Querious

and can handle those query that is constant at
some initial sql to use
datagrip :
SELECT  @@session.auto_increment_increment AS auto_increment_increment, @@character_set_client AS character_set_client, @@character_set_connection AS character_set_connection, @@character_set_results AS character_set_results, @@character_set_server AS character_set_server, @@collation_server AS collation_server, @@collation_connection AS collation_connection, @@init_connect AS init_connect, @@interactive_timeout AS interactive_timeout, @@license AS license, @@lower_case_table_names AS lower_case_table_names, @@max_allowed_packet AS max_allowed_packet, @@net_buffer_length AS net_buffer_length, @@net_write_timeout AS net_write_timeout, @@query_cache_size AS query_cache_size, @@query_cache_type AS query_cache_type, @@sql_mode AS sql_mode, @@system_time_zone AS system_time_zone, @@time_zone AS time_zone, @@tx_isolation AS transaction_isolation, @@wait_timeout AS wait_timeout

querious:
select @@version_comment limit 1

all done


Next.config still using webpack v4

devDAO members reported issues that we're still using webpack v4 in next.config.js. This should be fixed to use webpack 5 as indicated in package.json.
Might be also related to issues reported with regard to PR #678

Assigned to @zhyd1997


Move the readme into right folder

The PR is to move current READMEs under right monikers.
latest goes to api/overview/azure/latest
preview goes to api/overview/azure/preview

Is there a docs review site link?

We did not link markdowns to toc yet. This is one of the .NET monikerization


Add links to the HelloWorld and ZappysPlayground

Here's the HelloWorld GitHub Repo. https://github.com/EricVoll/MRTK_HelloWorld
I added a small description of how to reproduce the results in the ReadMe there. Maybe I'll find some more time later on this week to add buttons or so into the HelloWorld app.


Re-rendering PR?

Appears this hasn't been re-rendered in a very long time and there doesn't appear to be a recent re-rendering PR. While we can certainly re-render this manually, I would like to understand why this happened (or hasn't if you will) and fix it. Do you have any thoughts on this, @pelson?

Ping to https://github.com/conda-forge/conda-forge-webservices/issues/29. I'll try to fix shortly.


Help with the simulations from the paper

Hi,
Great paper and package. Thanks alot for making the code open source. I am trying to simulate the dataset for benchmarking cell-cell interaction tools following the Figure 1 f,g,h of the paper. I read the an adapted version of SVCA is being used for simulation. However I am unable to find the source code (or scripts for running SVCA) to generate or reproduce the ROC plots from the paper. It would be great to get some pointers to simulate the data as described.
Thanks again,
Best

Hi @hiraksarkar ,
Thanks for your question and patience. I didn't include simulation codes because it was mostly identical to SVCA. Please see the adapted codes below and refer to SVCA when needed. Note that you need to stack the simulated counts for each scenario afterwards. Also you need to turn the negatively correlated simulations to positive manually. We didn't explore other possibilities to simulate spatial interaction data, so it may not be the best approach especially after a year of submission.
import numpy as np
import scipy as s
import pandas as pd
from svca.models.model1 import Model1
from svca.simulations.from_real import FromRealSimulation
from svca.models.io import *
from svca.util_functions import utils
import sys
from limix.utils.preprocess import covar_rescaling_factor_efficient
from copy import deepcopy

def run(data_dir, protein_index, output_dir, bootstrap_index,
        normalisation='standard', permute=False):
    # reading all data
    ####################################################################
    expression_file = data_dir + 'exp.txt'
    position_file = data_dir+'pos.txt'
    # protein_name, phenotype, X = pr names, pr expr values, positions
    db = pd.read_csv('/CellChatDB_db2.csv',
                     index_col=0)
    protein_names, phenotypes, X = utils.read_data(expression_file,
                                                   position_file)

  # import pdb; pdb.set_trace()
  # protein_name = protein_names[protein_index, :]
  protein_name = db.index[protein_index]
  print(protein_name)
  phenotype = phenotypes[:, (protein_names==protein_name.split("_")[0])[:,0]]
  #import pdb; pdb.set_trace()
  sel = np.arange(phenotypes.shape[1])
  sel =list(sel[pd.Series(protein_names[:,0]).isin(db.loc[protein_name,
                                                ['R1', 'R2']].dropna().values).values])
  kin_from = phenotypes[:, sel] # remove the selected pr
  N_samples = X.shape[0]

  # permuting cells
  if permute:
      perm = np.random.permutation(X.shape[0])
      X = X[perm, :]

  # do simulations
  ####################################################################
  sim = FromRealSimulation(X, phenotype[:,0], kin_from)
  file_prefix = protein_name
  Y_sim = sim.simulate(interactions_size = None)
  np.save(output_dir+ 'nul/'+file_prefix, Y_sim)
  Y_sim = sim.simulate(interactions_size=0.25)
  np.save(output_dir+ 'rescale25/' + file_prefix, Y_sim)
  Y_sim = sim.simulate(interactions_size=0.99)
  np.save(output_dir+ 'full/' + file_prefix, Y_sim)
  Y_sim = sim.simulate(interactions_size=0.75)
  np.save(output_dir+ 'rescale75/' + file_prefix, Y_sim)
  Y_sim = sim.simulate(interactions_size=0.5)
  np.save(output_dir+ 'half/' + file_prefix, Y_sim)
  Y_sim = sim.simulate(interactions_size = 0.99)
  np.save(output_dir+ 'full/'+file_prefix, Y_sim)

  # run model on simulated data
  ####################################################################
  # intrinsic and environmental term
  ####################################################################
  cterms = ['intrinsic', 'environmental']
  model = Model1(Y_sim, X, norm=normalisation, oos_predictions=0., cov_terms=cterms, kin_from=kin_from)
  model.reset_params()
  model.train_gp(grid_size=10)

  file_prefix = protein_name[0] + '_' + str(bootstrap_index) + '_local'
  write_variance_explained(model, output_dir, file_prefix) # local_effects
  write_LL(model, output_dir, file_prefix) # LL

  int_param = model.intrinsic_cov.getParams()
  env_param = model.environmental_cov.getParams()
  noise_param = model.noise_cov.getParams()

  ####################################################################
  # add cell-cell interactions
  ####################################################################
  model.add_cov(['interactions'])

  LL = np.Inf
  for i in range(5):
      if i == 0:
          int_bk = int_param
          local_bk = env_param
          noise_bk = noise_param
          scale_interactions = True
      else:
          int_bk = int_param * s.random.uniform(0.8, 1.2, len(int_param))
          local_bk = env_param * s.random.uniform(0.8, 1.2, len(env_param))
          noise_bk = noise_param * s.random.uniform(0.8, 1.2, len(noise_param))
          scale_interactions = False
      model.set_initCovs({'intrinsic': int_bk,
                      'noise': noise_bk,
                      'environmental':local_bk})
      if scale_interactions:
          model.set_scale_down(['interactions'])
      else:
          model.use_scale_down = False

      model.reset_params()
      model.train_gp(grid_size=10)
      if model.gp.LML() < LL:
          LL = model.gp.LML()
          saved_params = model.gp.getParams()

  model.gp.setParams(saved_params)
  file_prefix = protein_name[0] + '_' + str(bootstrap_index) + '_interactions'
  write_variance_explained(model, output_dir, file_prefix)
  write_r2(model, output_dir, file_prefix)
  write_LL(model, output_dir, file_prefix)
  # write_Ks(model, output_dir, file_prefix)

  if __name__ == '__main__':
    data_dir = sys.argv[1]
    output_dir = sys.argv[2]
    protein_index = int(0)
    bootstrap_index = 1
    normalisation =  'quantile'

    run(data_dir, protein_index, output_dir, bootstrap_index, normalisation)

Thanks for replying. Assuming "CellChatDB_db2.csv" is a standard cellchat database I assume the R1 and R2 are possible receptors? Am I right? I am actually trying to reproduce the plot in Figure 1f. Can you please share the script for that? Precisely I want to check the ROC score for a few different methods for benchamrking. Thanks!


RBQFetchRequest add fetchLimit support.

Sometimes may need limit fetched count like NSFetchRequest, can you add fetchlimit to RBQFetchRequest? Thanks.

This won't be possible right now because Realm doesn't make available limiting through their query API (I believe the TightDB core offers this though they just haven't added it to the wrapper). So the only way would be to loop through the RLMResults and copy the first X into a NSArray for example. You can do this manually since it wouldn't make sense to setup RBQFetchrequest to work this way, because if you don't need a limit this isn't very performant. Makes sense?

FYI: here's relevant Realm issue regarding adding a limit to RLMResults (which RBQFetchRequest uses) https://github.com/realm/realm-cocoa/issues/1448

Thanks for your reply.I'll try other way to solve my problem, wish realm can update soon.

No problem, sorry couldn't be of more help. The one thing I should note is that at least in terms of memory management it isn't necessary to limit the results since RLMResults lazy loads the objects. So if you simply used the RLMResults directly as a UITableView datasource (instead of the FRC since internally it has its own cache complicating my point), then when the user scrolls and a cell is created, only then is the data accessed from the object at that specific index in the RLMResults. This prevents the need to limit the results or do any paging.

Yeah, I limit the count just for paging logic.

Ah, well in that case if you are simply trying to achieve a UI effect, you don't need to actually page the RLMResults to improve performance. Just limit the rows on the UITableview manually (i.e. don't match the rows in UITableview datasource to the RLMResults count), and then increase this by X until you reach the results count in response to the user requesting to see more.

The only tricky thing with this would be if you plan to use RBQFetchedResultsController to manage changes to the UITableView, you would have to catch any delegate calls that reference a index path that is not currently visible and not pass that change to the UITableView or you will get an assertion failure.

That's the problem so I tried other way: every model I have a flag and I reset all model's flag to false after refresh then set the new fetched model's flag to true then addOrUpdate.Througn this way i can limit the count.

Ah that makes sense, glad you figured out a fix for the time being.

Great thanks! I noticed this post is a bit old, are there any updates?


Matchers for bodies that are not json

I'm trying to create a matcher for a body that is not json, for example:
"response": {
        "status": 200,
        "headers": {
          "Content-Length": "500",
          "Content-Type": "text/plain",
        },
        "body": "blahSomeStringHere",
        "matchingRules": {
          "body": {
            "$": {
              "combine": "AND",
              "matchers": [
                {
                  "match": "regex",
                  "regex": "blah.*"
                }
              ]
            }
          }

I have not found a way to create this type of matcher, and always seems to result in a
java.lang.AssertionError:
0 - / -> [{mismatch=mismatch, diff=}]

I met the same error , PactDslJsonRootValue.stringType() or stringMatcher doesn't work

Version 3.5.3 has been released


Fix backup suspend timeout

Currently delegated backup would timeout on suspend when the primary master takes long time to acquire exclusive lock during busy hours. This change adds a function in state lock manager to allow suspend of journal before every retry of lock, which should greatly improve the chance of keeping secondary master ready during the locking stage.

@yuzhu @calvinjia PTAL.

@yuzhu @calvinjia PTAL.

alluxio-bot, merge this please.

alluxio-bot, merge this please.

alluxio-bot, cherry-pick this to branch-2.4 please.

alluxio-bot, cherry-pick this to branch-2.4 please.

alluxio-bot, cherry-pick this to branch-2.3 please


Add integration tests for Wasm module remote load

https://github.com/istio/istio/issues/29989
Update metric customization to use wasm remote load, instead of nullvm.
Also added a test to verify that bad Wasm config won't bring down envoy.
The test will fail right now, since it checks Wasm remote load metrics and relies on istio/istio#30239. (The PR was just merged. Test should be passing now).

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
ce62d350aa3f030ee2d719ec3b13d6266080b28f
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
ce62d350aa3f030ee2d719ec3b13d6266080b28f
link
/test release-notes_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
ce62d350aa3f030ee2d719ec3b13d6266080b28f
link
/test release-notes_istio

lint_istio
ce62d350aa3f030ee2d719ec3b13d6266080b28f
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
ce62d350aa3f030ee2d719ec3b13d6266080b28f
link
/test release-notes_istio

lint_istio
ce62d350aa3f030ee2d719ec3b13d6266080b28f
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
ce62d350aa3f030ee2d719ec3b13d6266080b28f
link
/test release-notes_istio

lint_istio
ce62d350aa3f030ee2d719ec3b13d6266080b28f
link
/test lint_istio

gencheck_istio
ce62d350aa3f030ee2d719ec3b13d6266080b28f
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
ce62d350aa3f030ee2d719ec3b13d6266080b28f
link
/test release-notes_istio

lint_istio
ce62d350aa3f030ee2d719ec3b13d6266080b28f
link
/test lint_istio

gencheck_istio
ce62d350aa3f030ee2d719ec3b13d6266080b28f
link
/test gencheck_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
ce62d350aa3f030ee2d719ec3b13d6266080b28f
link
/test release-notes_istio

lint_istio
ce62d350aa3f030ee2d719ec3b13d6266080b28f
link
/test lint_istio

gencheck_istio
ce62d350aa3f030ee2d719ec3b13d6266080b28f
link
/test gencheck_istio

analyze-tests_istio
ce62d350aa3f030ee2d719ec3b13d6266080b28f
link
/test analyze-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

release-notes_istio
ce62d350aa3f030ee2d719ec3b13d6266080b28f
link
/test release-notes_istio

lint_istio
ce62d350aa3f030ee2d719ec3b13d6266080b28f
link
/test lint_istio

gencheck_istio
ce62d350aa3f030ee2d719ec3b13d6266080b28f
link
/test gencheck_istio

analyze-tests_istio
ce62d350aa3f030ee2d719ec3b13d6266080b28f
link
/test analyze-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio
0ae994064b4073b3353e515266eb3f0f32baffca
link
/test analyze-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio
0ae994064b4073b3353e515266eb3f0f32baffca
link
/test analyze-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
e73b2ba872fb31c488e07d9ff43c676ed487533b
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
e73b2ba872fb31c488e07d9ff43c676ed487533b
link
/test integ-telemetry-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
e73b2ba872fb31c488e07d9ff43c676ed487533b
link
/test integ-telemetry-mc-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio
e73b2ba872fb31c488e07d9ff43c676ed487533b
link
/test integ-telemetry-mc-k8s-tests_istio

integ-telemetry-k8s-tests_istio
c3c21c8bcdfda8382e68c90c5269970c464b43e9
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio
e73b2ba872fb31c488e07d9ff43c676ed487533b
link
/test integ-telemetry-mc-k8s-tests_istio

integ-telemetry-k8s-tests_istio
c3c21c8bcdfda8382e68c90c5269970c464b43e9
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
c3c21c8bcdfda8382e68c90c5269970c464b43e9
link
/test integ-telemetry-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
c3c21c8bcdfda8382e68c90c5269970c464b43e9
link
/test integ-telemetry-mc-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
c3c21c8bcdfda8382e68c90c5269970c464b43e9
link
/test integ-telemetry-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
c3c21c8bcdfda8382e68c90c5269970c464b43e9
link
/test integ-telemetry-mc-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

/retest

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
c3c21c8bcdfda8382e68c90c5269970c464b43e9
link
/test integ-telemetry-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
c3c21c8bcdfda8382e68c90c5269970c464b43e9
link
/test integ-telemetry-mc-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
c3c21c8bcdfda8382e68c90c5269970c464b43e9
link
/test integ-telemetry-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
c3c21c8bcdfda8382e68c90c5269970c464b43e9
link
/test integ-telemetry-mc-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio
c3c21c8bcdfda8382e68c90c5269970c464b43e9
link
/test integ-telemetry-mc-k8s-tests_istio

integ-telemetry-k8s-tests_istio
c3c21c8bcdfda8382e68c90c5269970c464b43e9
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio
c3c21c8bcdfda8382e68c90c5269970c464b43e9
link
/test integ-telemetry-mc-k8s-tests_istio

integ-telemetry-k8s-tests_istio
c3c21c8bcdfda8382e68c90c5269970c464b43e9
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio
c3c21c8bcdfda8382e68c90c5269970c464b43e9
link
/test integ-telemetry-mc-k8s-tests_istio

integ-telemetry-k8s-tests_istio
c3c21c8bcdfda8382e68c90c5269970c464b43e9
link
/test integ-telemetry-k8s-tests_istio

integ-pilot-multicluster-tests_istio
602a277dd7feb0262c71f1bc183775a53ad846f2
link
/test integ-pilot-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio
c3c21c8bcdfda8382e68c90c5269970c464b43e9
link
/test integ-telemetry-mc-k8s-tests_istio

integ-telemetry-k8s-tests_istio
c3c21c8bcdfda8382e68c90c5269970c464b43e9
link
/test integ-telemetry-k8s-tests_istio

integ-pilot-multicluster-tests_istio
602a277dd7feb0262c71f1bc183775a53ad846f2
link
/test integ-pilot-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

/retest

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
c3c21c8bcdfda8382e68c90c5269970c464b43e9
link
/test integ-telemetry-k8s-tests_istio

integ-pilot-multicluster-tests_istio
602a277dd7feb0262c71f1bc183775a53ad846f2
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
602a277dd7feb0262c71f1bc183775a53ad846f2
link
/test integ-telemetry-mc-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
c3c21c8bcdfda8382e68c90c5269970c464b43e9
link
/test integ-telemetry-k8s-tests_istio

integ-pilot-multicluster-tests_istio
602a277dd7feb0262c71f1bc183775a53ad846f2
link
/test integ-pilot-multicluster-tests_istio

integ-telemetry-mc-k8s-tests_istio
602a277dd7feb0262c71f1bc183775a53ad846f2
link
/test integ-telemetry-mc-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio
6d40ef4afc7d174ae1fcfc4a6b3bc8782684f69a
link
/test integ-telemetry-mc-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-mc-k8s-tests_istio
6d40ef4afc7d174ae1fcfc4a6b3bc8782684f69a
link
/test integ-telemetry-mc-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
890557684b9d5db36bdfa3f515f4d4786b8d63a4
link
/test integ-security-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-security-k8s-tests_istio
890557684b9d5db36bdfa3f515f4d4786b8d63a4
link
/test integ-security-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

/retest

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio
787636c1abf4633571a2f1cc7ca7d99760d3a2ee
link
/test analyze-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio
787636c1abf4633571a2f1cc7ca7d99760d3a2ee
link
/test analyze-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio
787636c1abf4633571a2f1cc7ca7d99760d3a2ee
link
/test analyze-tests_istio

lint_istio
787636c1abf4633571a2f1cc7ca7d99760d3a2ee
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio
787636c1abf4633571a2f1cc7ca7d99760d3a2ee
link
/test analyze-tests_istio

lint_istio
787636c1abf4633571a2f1cc7ca7d99760d3a2ee
link
/test lint_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio
787636c1abf4633571a2f1cc7ca7d99760d3a2ee
link
/test analyze-tests_istio

lint_istio
787636c1abf4633571a2f1cc7ca7d99760d3a2ee
link
/test lint_istio

integ-telemetry-k8s-tests_istio
787636c1abf4633571a2f1cc7ca7d99760d3a2ee
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio
787636c1abf4633571a2f1cc7ca7d99760d3a2ee
link
/test analyze-tests_istio

lint_istio
787636c1abf4633571a2f1cc7ca7d99760d3a2ee
link
/test lint_istio

integ-telemetry-k8s-tests_istio
787636c1abf4633571a2f1cc7ca7d99760d3a2ee
link
/test integ-telemetry-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio
787636c1abf4633571a2f1cc7ca7d99760d3a2ee
link
/test analyze-tests_istio

lint_istio
787636c1abf4633571a2f1cc7ca7d99760d3a2ee
link
/test lint_istio

integ-telemetry-k8s-tests_istio
787636c1abf4633571a2f1cc7ca7d99760d3a2ee
link
/test integ-telemetry-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
787636c1abf4633571a2f1cc7ca7d99760d3a2ee
link
/test integ-telemetry-mc-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

analyze-tests_istio
787636c1abf4633571a2f1cc7ca7d99760d3a2ee
link
/test analyze-tests_istio

lint_istio
787636c1abf4633571a2f1cc7ca7d99760d3a2ee
link
/test lint_istio

integ-telemetry-k8s-tests_istio
787636c1abf4633571a2f1cc7ca7d99760d3a2ee
link
/test integ-telemetry-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
787636c1abf4633571a2f1cc7ca7d99760d3a2ee
link
/test integ-telemetry-mc-k8s-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
787636c1abf4633571a2f1cc7ca7d99760d3a2ee
link
/test integ-telemetry-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
787636c1abf4633571a2f1cc7ca7d99760d3a2ee
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
76001ed31a7b96968ecb3238781a36e032e238b1
link
/test integ-pilot-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@bianpengyuan: The following tests failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-telemetry-k8s-tests_istio
787636c1abf4633571a2f1cc7ca7d99760d3a2ee
link
/test integ-telemetry-k8s-tests_istio

integ-telemetry-mc-k8s-tests_istio
787636c1abf4633571a2f1cc7ca7d99760d3a2ee
link
/test integ-telemetry-mc-k8s-tests_istio

integ-pilot-multicluster-tests_istio
76001ed31a7b96968ecb3238781a36e032e238b1
link
/test integ-pilot-multicluster-tests_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest

/retest


'flow check -all' catches error while 'flow' or 'flow check' catches no errors

I have some code with running flow server. flow gives as response No errors! when i add the following code to the file:
// ... some code
/* @flow */
function add(num1, num2) {
  return num1 + num2;
}
var x = add(3, '0');
console.log(x);
// ... some code

Running flow still gives back No errors!. Running flow check gives back Found 0 errors
running flow check --all does echo the errors (among others ofcourse). Is this normal behavior (I started experimenting with flowtype)?

yeah, that's expected. the /* @flow */ applies to the whole file and has to be in a comment that's first thing in the file. so, turns out it wasn't doing anything. :/
we should add some better docs on what that comment does, and mention them in the Type Annotations guide you were following. i'm going to hijack this issue for that.

Great, seems to working better now. However, when running flow I still get the errors from the previous run, while the echo'ed lines by flow do give back the updated line of code. Should I always run flow check? This is not suggested by the documentation, I believe.