Status: 500. Message: db query error: pq: invalid input syntax for type json

Is there an existing issue for this?

[X] I have searched the existing issues

What happened?
Followed the exact steps mentioned here:
https://docs.teslamate.org/docs/installation/docker
Description:    Ubuntu 24.04.1 LTS
Release:        24.04
Codename:       noble
Docker version 27.3.1, build ce12230
teslamate:
image: teslamate/teslamate:latest
database:
image: postgres:17
grafana:
image: teslamate/grafana:latest
mosquitto:
image: eclipse-mosquitto:2
Expected Behavior
The dashboards are supposed to show data
Steps To Reproduce

Creating docker-compose.yml file as mentioned in this document (https://docs.teslamate.org/docs/installation/docker)
docker compose up
access the webUI using http://ipaddress:4000 (provide the access and refresh tokens)
access the Dashboard UI http://ipaddress:3000 (change admin password, and access battery dashboard)

Relevant log output
database-1   | 2024-12-18 22:09:35.034 UTC [89] ERROR:  invalid input syntax for type json at character 41
database-1   | 2024-12-18 22:09:35.034 UTC [89] DETAIL:  The input string ended unexpectedly.
database-1   | 2024-12-18 22:09:35.034 UTC [89] CONTEXT:  JSON data, line 1:
database-1   | 2024-12-18 22:09:35.034 UTC [89] STATEMENT:  SELECT
database-1   |    CASE WHEN 0 > 0 THEN 0 ELSE (''::json ->> 'MaxRange')::float END as "maxrange_mi",
database-1   |    (''::json ->> 'CurrentRange')::float  as "currentrange_mi",
database-1   |    CASE WHEN 0 > 0 THEN 0 ELSE (''::json ->> 'MaxRange')::float END - (''::json ->> 'CurrentRange')::float as "range_lost_mi"
grafana-1    | logger=context userId=1 orgId=1 uname=admin t=2024-12-18T22:09:35.03529099Z level=info msg="Request Completed" method=POST path=/api/ds/query status=400 remote_addr=<IP_ADDRESS> time_ms=6 duration=6.782616ms size=577 referer="http://<IP_ADDRESS>:3000/d/jchmRiqUfXgTM/battery-health?orgId=1" handler=/api/ds/query status_source=downstream
database-1   | 2024-12-18 22:09:35.041 UTC [90] ERROR:  invalid input syntax for type json at character 30
database-1   | 2024-12-18 22:09:35.041 UTC [90] DETAIL:  The input string ended unexpectedly.
database-1   | 2024-12-18 22:09:35.041 UTC [90] CONTEXT:  JSON data, line 1:
database-1   | 2024-12-18 22:09:35.041 UTC [90] STATEMENT:  SELECT GREATEST(0, 100.0 - ((''::json ->> 'CurrentCapacity')::float * 100.0 / CASE WHEN 0 > 0 THEN 0 ELSE (''::json ->> 'MaxCapacity')::float END))
database-1   |
database-1   |
grafana-1    | logger=context userId=1 orgId=1 uname=admin t=2024-12-18T22:09:35.041586079Z level=info msg="Request Completed" method=POST path=/api/ds/query status=400 remote_addr=<IP_ADDRESS> time_ms=5 duration=5.134265ms size=414 referer="http://<IP_ADDRESS>:3000/d/jchmRiqUfXgTM/battery-health?orgId=1" handler=/api/ds/query status_source=downstream
database-1   | 2024-12-18 22:09:35.076 UTC [90] ERROR:  invalid input syntax for type json at character 52
database-1   | 2024-12-18 22:09:35.076 UTC [90] DETAIL:  The input string ended unexpectedly.
database-1   | 2024-12-18 22:09:35.076 UTC [90] CONTEXT:  JSON data, line 1:
database-1   | 2024-12-18 22:09:35.076 UTC [90] STATEMENT:  SELECT
database-1   |    LEAST(100, (100 - GREATEST(0, 100.0 - ((''::json ->> 'CurrentCapacity')::float * 100.0 / CASE WHEN 0 > 0 THEN 0 ELSE (''::json ->> 'MaxCapacity')::float END)))) as "Battery Health (%)"
database-1   |
database-1   |
grafana-1    | logger=context userId=1 orgId=1 uname=admin t=2024-12-18T22:09:35.077350684Z level=info msg="Request Completed" method=POST path=/api/ds/query status=400 remote_addr=<IP_ADDRESS> time_ms=5 duration=5.366221ms size=467 referer="http://<IP_ADDRESS>:3000/d/jchmRiqUfXgTM/battery-health?orgId=1" handler=/api/ds/query status_source=downstream
database-1   | 2024-12-18 22:09:35.080 UTC [91] ERROR:  invalid input syntax for type json at character 71
database-1   | 2024-12-18 22:09:35.080 UTC [91] DETAIL:  The input string ended unexpectedly.
database-1   | 2024-12-18 22:09:35.080 UTC [91] CONTEXT:  JSON data, line 1:
database-1   | 2024-12-18 22:09:35.080 UTC [91] STATEMENT:  SELECT
database-1   |          floor(sum(charge_energy_added) / CASE WHEN 0 > 0 THEN 0 ELSE (''::json ->> 'MaxCapacity')::float END) AS "# of Charging cycles"
database-1   |  FROM charging_processes WHERE car_id = 1 AND charge_energy_added > 0.01
grafana-1    | logger=context userId=1 orgId=1 uname=admin t=2024-12-18T22:09:35.081911145Z level=info msg="Request Completed" method=POST path=/api/ds/query status=400 remote_addr=<IP_ADDRESS> time_ms=7 duration=7.241703ms size=2270 referer="http://<IP_ADDRESS>:3000/d/jchmRiqUfXgTM/battery-health?orgId=1" handler=/api/ds/query status_source=downstream
database-1   | 2024-12-18 22:09:35.108 UTC [87] ERROR:  invalid input syntax for type json at character 9
database-1   | 2024-12-18 22:09:35.108 UTC [87] DETAIL:  The input string ended unexpectedly.
database-1   | 2024-12-18 22:09:35.108 UTC [87] CONTEXT:  JSON data, line 1:
database-1   | 2024-12-18 22:09:35.108 UTC [87] STATEMENT:  SELECT (''::json ->> 'RatedEfficiency')::float * 10 / convert_km(1, 'mi') AS efficiency_mi
database-1   | 2024-12-18 22:09:35.109 UTC [88] ERROR:  invalid input syntax for type json at character 48
database-1   | 2024-12-18 22:09:35.109 UTC [88] DETAIL:  The input string ended unexpectedly.
database-1   | 2024-12-18 22:09:35.109 UTC [88] CONTEXT:  JSON data, line 1:
database-1   | 2024-12-18 22:09:35.109 UTC [88] STATEMENT:  SELECT * FROM ((SELECT usable_battery_level * (''::json ->> 'CurrentCapacity')::float / 100 as kWh, date, (''::json ->> 'CurrentCapacity')::float as Total
database-1   |  FROM positions
database-1   |  WHERE car_id = 1  AND usable_battery_level IS NOT NULL
database-1   |  ORDER BY date DESC
database-1   |  LIMIT 1)
database-1   |  UNION
database-1   |  (SELECT battery_level * (''::json ->> 'CurrentCapacity')::float / 100 as kWh, date, (''::json ->> 'CurrentCapacity')::float as Total
database-1   |  FROM charges c
database-1   |  JOIN charging_processes p ON p.id = c.charging_process_id
grafana-1    | logger=context userId=1 orgId=1 uname=admin t=2024-12-18T22:09:35.109453618Z level=info msg="Request Completed" method=POST path=/api/ds/query status=400 remote_addr=<IP_ADDRESS> time_ms=6 duration=6.222082ms size=348 referer="http://<IP_ADDRESS>:3000/d/jchmRiqUfXgTM/battery-health?orgId=1" handler=/api/ds/query status_source=downstream
database-1   |  WHERE p.car_id = 1  AND usable_battery_level IS NOT NULL
grafana-1    | logger=context userId=1 orgId=1 uname=admin t=2024-12-18T22:09:35.109636506Z level=info msg="Request Completed" method=POST path=/api/ds/query status=400 remote_addr=<IP_ADDRESS> time_ms=6 duration=6.425238ms size=876 referer="http://<IP_ADDRESS>:3000/d/jchmRiqUfXgTM/battery-health?orgId=1" handler=/api/ds/query status_source=downstream
database-1   |  ORDER BY date DESC
database-1   |  LIMIT 1)) AS last_usable_battery_level LIMIT 1
database-1   | 2024-12-18 22:09:35.142 UTC [87] ERROR:  invalid input syntax for type json at character 100
database-1   | 2024-12-18 22:09:35.142 UTC [87] DETAIL:  The input string ended unexpectedly.
database-1   | 2024-12-18 22:09:35.142 UTC [87] CONTEXT:  JSON data, line 1:
database-1   | 2024-12-18 22:09:35.142 UTC [87] STATEMENT:  SELECT convert_km(AVG(p.odometer)::numeric,'mi') AS "Odometer",
database-1   |          AVG(c.rated_battery_range_km * (''::json ->> 'RatedEfficiency')::float / c.usable_battery_level) AS "kWh",
database-1   |          --MAX(cp.id) AS id,
database-1   |          to_char(cp.end_date, 'YYYY-MM-dd') AS "Date"
database-1   |          FROM charging_processes cp
database-1   |                  JOIN (SELECT charging_process_id, MAX(date) as date     FROM charges WHERE usable_battery_level > 0 GROUP BY charging_process_id) AS last_charges       ON cp.id = last_charges.charging_process_id
database-1   |                  INNER JOIN charges c
database-1   |                  ON c.charging_process_id = cp.id AND c.date = last_charges.date
database-1   |                  INNER JOIN positions p ON p.id = cp.position_id
database-1   |          WHERE cp.car_id = 1
database-1   |                  AND cp.end_date IS NOT NULL
database-1   |                  AND cp.charge_energy_added >= (''::json ->> 'RatedEfficiency')::float
database-1   |          GROUP BY 3
database-1   | 2024-12-18 22:09:35.142 UTC [88] ERROR:  invalid input syntax for type json at character 155
database-1   | 2024-12-18 22:09:35.142 UTC [88] DETAIL:  The input string ended unexpectedly.
database-1   | 2024-12-18 22:09:35.142 UTC [88] CONTEXT:  JSON data, line 1:
database-1   | 2024-12-18 22:09:35.142 UTC [88] STATEMENT:  SELECT
database-1   |    ROUND(MIN(convert_km(p.odometer::numeric,'mi')),0) AS "Odometer",
database-1   |          ROUND(PERCENTILE_CONT(0.5) WITHIN GROUP(ORDER BY c.rated_battery_range_km * (''::json ->> 'RatedEfficiency')::float / c.usable_battery_level)::numeric,1) AS "kWh",
database-1   |          to_char(cp.end_date, 'YYYYMM') || CASE WHEN to_char(cp.end_date, 'DD')::int <= 15 THEN '1' ELSE '2' END  AS Title
database-1   |          FROM charging_processes cp
database-1   |                  JOIN (SELECT charging_process_id, MAX(date) as date     FROM charges WHERE usable_battery_level > 0 GROUP BY charging_process_id) AS last_charges       ON cp.id = last_charges.charging_process_id
database-1   |                  INNER JOIN charges c
database-1   |                  ON c.charging_process_id = cp.id AND c.date = last_charges.date
database-1   |                  INNER JOIN positions p ON p.id = cp.position_id
grafana-1    | logger=context userId=1 orgId=1 uname=admin t=2024-12-18T22:09:35.143609772Z level=info msg="Request Completed" method=POST path=/api/ds/query status=400 remote_addr=<IP_ADDRESS> time_ms=6 duration=6.415031ms size=2236 referer="http://<IP_ADDRESS>:3000/d/jchmRiqUfXgTM/battery-health?orgId=1" handler=/api/ds/query status_source=downstream
database-1   |          WHERE cp.car_id = 1
database-1   |                  AND cp.end_date IS NOT NULL
database-1   |                  AND cp.charge_energy_added >= (''::json ->> 'RatedEfficiency')::float
database-1   |          GROUP BY 3
database-1   | 2024-12-18 22:10:49.309 UTC [88] ERROR:  invalid input syntax for type json at character 9
database-1   | 2024-12-18 22:10:49.309 UTC [88] DETAIL:  The input string ended unexpectedly.
database-1   | 2024-12-18 22:10:49.309 UTC [88] CONTEXT:  JSON data, line 1:
database-1   | 2024-12-18 22:10:49.309 UTC [88] STATEMENT:  SELECT (''::json ->> 'RatedEfficiency')::float * 10 / convert_km(1, 'mi') AS efficiency_mi

Screenshots

Additional data
No response
Type of installation
Docker
Version
Latest (v1.32)

All it needed was more data, a couple of charging sessions helped populate the data slowly. However, if anyone can include error handling when the data is NULL that would be something good to have.

I have the same errors on the Battery Health page. I have now Teslamate with Grafana for 1 week on my synology nas, running in docker (Portainer).
How can i fix this?

Wait for the next release or charge your car ;)

Wait for the next release or charge your car ;)

As you can see, i've already charged my car 4 times in this current installation?

Oh, is it an lfp battery ? What percentage have you charged to?

No, i have the NMC-battery (Model Y 2024 Long Range RWD) . But i see that LFP battery is enabled in the Teslamate settings...
For now disabled. I hope the data will be recovered soon.

🤔 i wonder why it happens in your case... can you go into dashboard settings -> Variable -> aux and see the preview of the value? is it completely empty? - what shows up if you change the sql to this one:
WITH Aux AS
(
		SELECT
    car_id,
		COALESCE(efficiency,
		(SELECT efficiency
			FROM cars WHERE id = $car_id) * 100) AS efficiency
	FROM (
		SELECT ROUND((charge_energy_added / NULLIF(end_rated_range_km - start_rated_range_km, 0))::numeric, 3) * 100 as efficiency,
			COUNT(*) as count, $car_id AS car_id
		FROM charging_processes
		WHERE car_id = $car_id
			AND duration_min > 10
			AND end_battery_level <= 95
			AND start_rated_range_km IS NOT NULL
			AND end_rated_range_km IS NOT NULL
			AND charge_energy_added > 0
		GROUP BY 1
		ORDER BY 2 DESC
		LIMIT 1
	) AS DerivatedEfficiency
),
CurrentCapacity	 AS
(
	SELECT AVG(Capacity) AS Capacity
FROM (
SELECT
	c.rated_battery_range_km * aux.efficiency / c.usable_battery_level AS Capacity
	FROM charging_processes cp
		INNER JOIN charges c
		ON c.charging_process_id = cp.id
                INNER JOIN aux ON cp.car_id = aux.car_id
	WHERE cp.car_id = $car_id
		AND cp.end_date IS NOT NULL
		AND cp.charge_energy_added >= aux.efficiency
		AND c.usable_battery_level > 0
	 ORDER BY cp.end_date DESC LIMIT 10) AS lastCharges
),
MaxCapacity AS
(
	SELECT
		MAX(c.rated_battery_range_km * aux.efficiency / c.usable_battery_level) AS Capacity
	FROM charging_processes cp
		INNER JOIN (
			SELECT charging_process_id, MAX(date) as date FROM charges WHERE usable_battery_level > 0 GROUP BY charging_process_id) AS gcharges
			ON cp.id = gcharges.charging_process_id
		INNER JOIN charges c
		ON c.charging_process_id = cp.id AND c.date = gcharges.date
		INNER JOIN aux ON cp.car_id = aux.car_id
	WHERE cp.car_id = $car_id
		AND cp.end_date IS NOT NULL
		AND cp.charge_energy_added >= aux.efficiency
),
CurrentRange AS
(
    SELECT (range * 100.0 / usable_battery_level) AS range
	FROM (
		(SELECT date, ${preferred_range}_battery_range_km AS range, usable_battery_level AS usable_battery_level
			FROM positions	WHERE car_id = $car_id AND ideal_battery_range_km IS NOT NULL AND usable_battery_level > 0  ORDER BY date DESC LIMIT 1)
		UNION ALL
		(SELECT date, ${preferred_range}_battery_range_km AS range, usable_battery_level as usable_battery_level
			FROM charges c JOIN charging_processes p ON p.id = c.charging_process_id
			WHERE p.car_id = $car_id AND usable_battery_level > 0 ORDER BY date DESC LIMIT 1)
	) AS data
	ORDER BY date DESC
	LIMIT 1
),
MaxRange AS
(
    SELECT
		floor(extract(epoch from date)/86400)*86400 AS time,
	    CASE WHEN sum(usable_battery_level) = 0 THEN sum(${preferred_range}_battery_range_km) * 100
		     ELSE sum(${preferred_range}_battery_range_km) / sum(usable_battery_level) * 100
	END AS range
    FROM (
		SELECT battery_level, usable_battery_level, date,  ${preferred_range}_battery_range_km from charges c
		JOIN charging_processes p ON p.id = c.charging_process_id
		WHERE p.car_id = $car_id AND usable_battery_level IS NOT NULL) AS data
	GROUP BY 1
	ORDER BY 2 DESC
	LIMIT 1
),
Base as (
	select null
)
SELECT
  json_build_object(
    'MaxRange', convert_km(MaxRange.range,'$length_unit'),
    'CurrentRange', convert_km(CurrentRange.range,'$length_unit'),
    'MaxCapacity', MaxCapacity.Capacity,
    'CurrentCapacity', CASE WHEN CurrentCapacity.Capacity IS NULL THEN 1 ELSE CurrentCapacity.Capacity END,
    'RatedEfficiency', aux.efficiency
  )
FROM Base, MaxRange, CurrentRange, Aux, MaxCapacity, CurrentCapacity

Sure :)
But currently see: There are no variables added.
When i click on add variables i see this.
What should I select and where should I add your code?

You need to go to the battery health dashboard first


feat: Add support for ROG Ally

Adds support for the Asus ROG Ally

Spoke with @bsherman about this, my understanding is we'll eventually be able to build kmods for this kernel in ublue-os/akmods and then we can get this shipped @EyeCantCU.

Spoke with @bsherman about this, my understanding is we'll eventually be able to build kmods for this kernel in ublue-os/akmods and then we can get this shipped @EyeCantCU.

Awesome! That would be perfect

https://github.com/ublue-os/asus
Follow here for further updates


feat: dont underscore numbers when formatting module names

Fixes https://github.com/jsr-io/jsr/issues/803 but I'd like to know how or if I could better test this.
I eventually got here by looking at how the identifier for the file was created:

The identifier replacing all non-characters with underscores seems to be the source so adjusting the regex to allow numbers.
Though this regex might need to account for a leading number and replace that since you can't have a module identifier prefixed by a number (must be a character)

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

I'm not sure the regex would want to handle something as complex as "allow a-Za-z0-9 but if the string starts with 0-9 then prepend _" and I'm not sure that would be a valid export so I don't think that should be a concern here. Any inputs?

@c43721 yes it should handle the case of a starting number

@c43721 for test, you can update the module doc name in tests/testdata/multiple/b.ts


hope i got the right name changes this time

Hmm it says there are 12448 lines different, some sort of MAC vs Windows problem I'm guessing.

I think this is stale, @jackwingsam  you need to reupdate this file.


Instance Model typo for gamephys.srs stable version

SRS->Instance Models-> IM3
P**k**(to) is how the variable is defined in the input and output section however
p**i**(t) is how it is defined in the description
all the other variables for this instance model are defined using k consistently in input, output and description:
v**k**(to)
v**k**(t)
is I and k being used interchangeably for position?
also a "p2(t)" is defined in output, but doesn't seem to defined or used anywhere in that specific instance model.

i and k are dummy variables, so technically i or k (or anything else could be used).  However, it really doesn't make sense to be inconsistent.  Please use k for all instances.
Please remove p_2(t).  It seems to be an error to me.

Updated to use k of for all instances, and removed p_2(t). 418fcc7


forward() got an unexpected keyword argument 'cross_attn_head_mask'

----> 1 paraphrase_t5("Kyle Lowry scored 33 points and Norman Powell added 23 to lift the Toronto Raptors to a 122-125 victory over the Boston Celtics on Wednesday night.")

4 frames
/usr/local/lib/python3.7/dist-packages/torch/nn/modules/module.py in _call_impl(self, *input, **kwargs)
   1049         if not (self._backward_hooks or self._forward_hooks or self._forward_pre_hooks or _global_backward_hooks
   1050                 or _global_forward_hooks or _global_forward_pre_hooks):
-> 1051             return forward_call(*input, **kwargs)
   1052         # Do not call functions when jit is used
   1053         full_backward_hooks, non_full_backward_hooks = [], []

TypeError: forward() got an unexpected keyword argument 'cross_attn_head_mask'

I am having the same issue on latest version of transformers(4.8.0), a workaround would be to downgrade transformers to 4.4.2 and it'll works. But still needs fixing.

It's enough to downgrade to 4.7.0. Version 4.4.2 doesn't have this patch: https://github.com/huggingface/transformers/pull/10651

Any update on this? When trying to downgrade to either 4.4.2 or 4.6.1 and trying to run the inference example, I'm getting the following error:
RuntimeError: output with shape [5, 12, 1, 2] doesn't match the broadcast shape [5, 12, 2, 2]

I still hit this error. If I downgrade transformers to 4.6.1, then I get an error ImportError: cannot import name 'AutoModelForSeq2SeqLM'
Anyone figured this out?

This is actually not a small thing. Here's what I think is going on:
First, check out this transformers PR:
https://github.com/huggingface/transformers/pull/11621
before that PR,

T5 does not use head masks properly (there’s an old glitch that the decoder uses encoder’s head_mask instead of cross_attn_head_mask)

and I think fastT5's current implementation relies on that old behavior, in that the decoders use the encoder's attention mask. So AFAICT, there needs to be a non-negligible rewrite to use newer versions of transformers

@sam-writer Thanks, I got it working by installing fastt5 on a clean conda slate

This is actually not a small thing. Here's what I think is going on:
First, check out this transformers PR: huggingface/transformers#11621
before that PR,

T5 does not use head masks properly (there’s an old glitch that the decoder uses encoder’s head_mask instead of cross_attn_head_mask)

and I think fastT5's current implementation relies on that old behavior, in that the decoders use the encoder's attention mask. So AFAICT, there needs to be a non-negligible rewrite to use newer versions of transformers

@kagrze @Ki6an please correct me if I am wrong

I get the same error with the newest verion of transfroemrs and 4.6.1 does not work at all.

Also with 4.4.2 it does not work at all.
So no way  to get it to work now.

Yeah, I'm having the same problem, I can't get it to work at all. I set up a huggingface space to demonstrate the problem: https://huggingface.co/spaces/aseifert/fastt5 (this will show the output of pip freeze before it throws a ImportError: cannot import name 'AutoModelForSeq2SeqLM' from 'transformers' (unknown location) due to running from fastT5 import export_and_get_onnx_model, get_onnx_model
Underlying code: https://huggingface.co/spaces/aseifert/fastt5/blob/main/app.py
requirements.json: https://huggingface.co/spaces/aseifert/fastt5/blob/main/requirements.txt
logs from building the container: https://huggingface.co/spaces/aseifert/fastt5/logs/build

@aseifert you forgot to import AutoTokenizer in your code
first, import it and try again,
from transformers import AutoTokenizer

I tried it on my machine and it gives the following output without any error.
You are using a model of type mt5 to instantiate a model of type t5. This is not supported for all configurations of models and can yield errors.
Exporting to onnx... |################################| 3/3
Quantizing... |################################| 3/3
Setting up onnx model...
You are using a model of type mt5 to instantiate a model of type t5. This is not supported for all configurations of models and can yield errors.
Done!
Dieго vienでಗೆ about08 су су су су су су су су су су су су

the output is similar to the output of the original model.

@Ki6an thank you so much for looking into this! Indeed I forgot to include the AutoTokenizer. However, adding it doesn't resolve the problem in the huggingface space environment (cf. links above). It's weird …

@aseifert I assume the huggingface space is using a version of transformers > 4.6.1, which fastt5 can't work with currently
I think there are 2 issues here, @Ki6an :

people trying to use fastt5 with a version of transformers which it does not support (anything > 4.6.1)
what I am trying to point out, which is the reason that fastt5 is stuck on v4.6.1 of transformers

FWIW, I am currently working on a fix so that fastt5 will be able to support transformers v4.7.0 and above

@sam-writer I pinned transformers to 4.6.1 in the requirements, and I check this by writing the output of pip freeze to the streamlit app, which indeed shows transformers==4.6.1

@aseifert fwiw I get a 503 when I try to look at the Spaces log
when I look at @Ki6an 's colab, it looks like it is doing the same thing as your space, right? If that is the case, then it has to do the environment (HF Spaces) not this library... does that sound right?

@sam-writer You are right, it does look like something specific to the env. I opened an issue here https://github.com/huggingface/transformers/issues/14604
Thanks!

@sam-writer @aseifert  I was able to fix this issue, the changes to transformers were made right after I created a PR.   here  and that was causing the issue.
it's a simple one-line fix https://github.com/Ki6an/fastT5/commit/97d5505ccc1ceec8fd8708f92d6df313f6ce601a

@Ki6an I will check it out. I was expecting there to also be changes to generate_onnx_representation, so I will play around with that

cross_attn_head_mask  is an optional parameter like head_mask and decoder_head_mask, currently we are exporting decoder to onnx with only one optional parameter decoder_attention_mask .
https://github.com/huggingface/transformers/blob/73ec4340ec651ca1fe4f8ead9206297a4d4ed79c/src/transformers/models/t5/modeling_t5.py#L1150
we could add these additional params (while exporting) if they improve the speed or accuracy.

It would probably be good to have some script for testing the accuracy of the ONNX version... I think I saw something like this in the TensorRT demo from NVIDIA

I am still experiencing this problem


[Bug] Advanced inscriber not receiving power through quartz fiber

Hello,
I'm using <IP_ADDRESS> (the rv3 alpha) on the FTB Infinity Evolved modpack (set to normal mode), but I've run into an issue trying to power the advanced inscriber.
Seeing as how a picture is worth a thousand words, this is an image of my setup. What it's supposed to do, is send power from the 'main' network's blue cables, through the quartz fiber and then into the advanced inscriber via the red glass cable. As you should be able to see, that isn't happening (and for the record, the inscriber is filled with a calculation press and pure certus quartz): The inscriber is sleeping, and has no power.
If I remove the red wire and the quartz fiber and connect the inscriber to the network through a blue cable, the inscriber starts receiving power and works as intended.

I'll look into it when i get the chance... but that setup is pretty pointless. Since it doesn't use channels you can just have it on your main network.

I'm closing this issue as part of a spring cleaning of my issue trackers from old stuff.
If you believe it's a bug that is still relevant in Minecraft 1.12 - Feel free to reopen it.


Loot rarity coloring system doesn't seem to work with controllers

Description of the bug
When active, and using a controller when looting anything the loot is either replaced with an invisible object of no description or detail or is replaced with an image of a scroll of no detail.
Steps To Reproduce
Activate Loot Rarity
Connect Controller
Try to loot anything
Expected Behavior
No response
Log Files
No response
Save File
No response
Screenshots

Settings
No response
Toybox Version
1.5.34
Operating System
No response
What game are you using Toybox on?
Pathfinder Wrath of the Righteous
Game Version
2.3.3k
Anything else?
No response

Another controller issue, looks like?  Using controller with Toybox breaks a lot of things.
As said on the issue on the main repo, Toybox would need a significant rewrite to work with controllers
https://github.com/cabarius/ToyBox/issues/999

I'll leave this open since this repo doesn't have an issue related to Controller interaction yet; but ToyBox behaving weird with Controllers is a known issue and not something I plan to look into in the near future.
If someone else wants to take a shot feel free; the issue is that the game picks either ...PCView or ...ConsoleView classes. ToyBox patches are mostly done on ...PCView. Since it also sometimes accesses some Unity object which does not exist it can cause NullReferenceExceptions and stuff; which is more or less the root of the error.


Fix e2e tests so they work with bitcoind 0.21.0

When I tried running the e2e tests, they would hang indefinitely. While debugging I found that bitcoind would get caught at bitcoin_cli.getnewaddress() in /test/teos/conftest.py, getting the error: A default wallet is no longer automatically created
I'm running version 0.21.0 of bitcoin, and it looks like in version 0.21.0 of bitcoind "Bitcoin Core will no longer automatically create new wallets on startup": https://lists.linuxfoundation.org/pipermail/bitcoin-core-dev/2021-January/000097.html
Proposing the following change, which allows tests to run smoothly while running the latest version of bitcoind

@sr-gi Cool fixed that & the formatting issue ~ I forgot to set up signed commits on my new desktop!


Removed "main" task to save 4k of RAM.

Linking is achieved by keeping a reference to the first added task.

closes #18

ups sorry, wrong source branch


Updating entity with composite key is problematic

This is tangential to #189. I'm finding it difficult to take the same approach with composite key entities. Here's some example code:
[Entity]
public interface IParentEntity
{
    [Identifier("http://example.org/repro/")]
    string Id
    {
        get;
    }

    ICollection<IChildEntity> Children
    {
        get;
        set;
    }
}

[Entity]
public interface IChildEntity
{
    [Identifier("http://example.org/repro/", KeyProperties = new[] { "Parent", "Code" })]
    string Id
    {
        get;
    }

    string Code
    {
        get;
        set;
    }

    string Description
    {
        get;
        set;
    }

    [InverseProperty("Children")]
    IParentEntity Parent
    {
        get;
        set;
    }
}

using (var context = new MyEntityContext(connectionString))
{
    var parent = context.ParentEntities.Create();
    var child = context.ChildEntities.Create();
    child.Code = "child";
    child.Description = "Some description";
    child.Parent = parent;
    context.ChildEntities.Add(child);

    context.SaveChanges();
}

using (var context = new MyEntityContext(connectionString))
{
    var parent = context.ParentEntities.First();
    var child = context.ChildEntities.First();

    child.Description = "Update description";

    context.SaveChanges();
}

This results in an exception in the second call to SaveChanges():
BrightstarDB.EntityFramework.EntityKeyChangedException was unhandled
  HResult=-2146233088
  Message=The entity's key properties have been modified without updating the identity value.
  Source=BrightstarDB
  StackTrace:
       at BrightstarDB.EntityFramework.BrightstarEntityContext.EnsureIdentity(IEntityObject item)
       at BrightstarDB.EntityFramework.BrightstarEntityContext.EnsureIdentity()
       at BrightstarDB.EntityFramework.BrightstarEntityContext.SaveChanges()
<snip>

I also ran into a bunch of other issues just getting the repro to this point, including:

I had to use the Create() method to create the child entity (I couldn't just new it up as you'd expect)
I had to set Parent on the child rather than adding the child to the parent's Children collection. This might be related to #184 but I got a different exception this time, so not convinced

This is happening because your composite key includes an inverse property. Inverse properties are not loaded by default when you retrieve an entity - they are instead lazily loaded when you ask for the property value. The problem is that the code that constructs the identifier doesn't trigger the lazy loading. It would probably be good if it did, so this is a bug. But even if it did that means you always end up loading that inverse relationship during a SaveChanges because the identifier is always recomputed and validated.
So my recommendation would be to swap things so that the [InverseProperty] is on IParentEntity.Children. This will (a) work around the bug for now and (b) be more efficient anyway once the bug is fixed.

Thanks Kal - just tried your suggestion and can confirm that it works in my repro. I'm getting a different error in my real project now, but will look into that separately.
It would be pure awesome sauce if the t4 template issued an appropriate warning if it detects the scenario where a composite key is specified on a lazy-loaded property.

I've changed the code now so that identity changes are handled much better. It should update references to the entity that has changed identity both locally and in the store.
However, I have not currently implemented any notion of "cascading" identity changes down to other entities that have an identity that depends on the identity of the modified entity.


Incorrect and duplicated values in the ref_series table in the displayName and notes columns

Both production and dev ref_dataSeries tables are showing the same numerous issues with the values of in the displayName and noes columns (see below).
After fixing these issues, we should add a uniqueness constraint at the very least on the displayName column, as there is no reason to ever have duplicate values and it will avoid the kind of issues we are seeing now.  We also need to discuss issue #3 below as it seems to be a major issue that can affect existing models
Issues:

Duplicate and either incorrect values in the displayName column: e.g.,  'Water Temperature' value appears 4 times, 2 of which to describe air temperature :-(
Not distinguishing between predictions and measurements in the displayName column
The 12 series storing mean calculations:  we should discuss why we are storing calculated values.  And we need to give each a unique display name.

https://docs.google.com/spreadsheets/d/1vse3ADuG75BQ2kK78LOTe8_1hG-NW8X4XA9PJwSvJ64/edit?usp=sharing
Here is a exel sheet with the proposed DB changes and the files/DSPECS that will be effected

Refactor plan

Create DB Migration scrip to update DB information as detailed in the above spreadsheet.
Create a PPC (post processing class) for 4 max mean.
Refactor MLP-OP to fix broken reference
Update (ar, nj, pi, rp)mlp(12h, 24h, 72h) models and ar_inundation_(jan, feb, mar,...)  models to 2.0 using the updated dspec version
Refactor test_API, test_NOAATANDC, test_dspec, NDBC, NOATANDC files to fix broken references to changed DB information

08-23-2024 Meeting Notes:
split into two stories: one migration just to fix the display names that are wrong, another to fix the issue of soring calculated values
prioratize what models need to be moved up to 2.0
refactor NDFD to pull lon and lat from the data_location_source_mapping rather than directly referencing the location table


Examples and Errors for Scripting API

[x] This contribution adheres to CONTRIBUTING.md.

What does this Pull Request accomplish?
Adds and exports DSF error file with descriptions. Adds and exports examples for the scripting API.
Why should this Pull Request be merged?
Examples demonstrate use of the scripting API and specific error descriptions help debug scripting applications for the Data Sharing Framework.
What testing has been done?
Local build successful. PR build will be validated by installation and validation of package. New scripting tests are also being added.

we are aware of an issue with the use of version-specific packages to install a common file to a shared (non-version-specific) destination. As currently designed, installation of multiple versions of the DSF Custom Device will install a DSF-errors.txt file to
National Instruments\Shared\Errors\English. Uninstallation of any of the versions removes the error text which removes the error description support for remaining version of the DSF custom device.
The following proposal was submitted by @rtzoeller

NIPM does not do ref counting for file-based package files. ... the CD packages install error files to the LV runtime errors directory directly, and the CD scripting APIs depend on a single package that installs the error file to the development errors directory


It hangs

Upon loading second time previous image sticks and scan button does not work

@sangeetjass Thanks for reporting. We will look into it.

@aahedi Fixed in version 2 which is live now 👍


gh-2457 double caching issue

Related Issue

Resolve #2457

Codecov Report

Merging #2595 (f20e089) into v2-alpha (d598fcf) will decrease coverage by 0.19%.
The diff coverage is 53.84%.

@@              Coverage Diff               @@
##             v2-alpha    #2595      +/-   ##
==============================================
- Coverage       65.30%   65.10%   -0.20%
- Complexity       2429     2430       +1
==============================================
  Files             872      872
  Lines           27209    27200       -9
  Branches         3165     3153      -12
==============================================
- Hits            17768    17709      -59
- Misses           8044     8093      +49
- Partials         1397     1398       +1

Impacted Files
Coverage Δ

.../src/main/java/uk/gov/gchq/gaffer/cache/Cache.java
57.69% <0.00%> (-7.53%)
:arrow_down:

.../src/main/java/uk/gov/gchq/gaffer/graph/Graph.java
66.49% <0.00%> (-2.16%)
:arrow_down:

...java/uk/gov/gchq/gaffer/jobtracker/JobTracker.java
0.00% <0.00%> (ø)

.../src/main/java/uk/gov/gchq/gaffer/store/Store.java
70.30% <0.00%> (ø)

...java/uk/gov/gchq/gaffer/store/StoreProperties.java
43.75% <0.00%> (-1.42%)
:arrow_down:

...va/uk/gov/gchq/gaffer/graph/GraphSerialisable.java
49.05% <32.50%> (-6.90%)
:arrow_down:

...gov/gchq/gaffer/federatedstore/FederatedStore.java
90.98% <50.00%> (-1.46%)
:arrow_down:

...q/gaffer/federatedstore/FederatedGraphStorage.java
74.07% <73.10%> (-6.80%)
:arrow_down:

...chq/gaffer/federatedstore/FederatedStoreCache.java
90.90% <100.00%> (+5.90%)
:arrow_up:

...affer/federatedstore/FederatedStoreProperties.java
84.21% <100.00%> (-1.51%)
:arrow_down:

... and 9 more

Continue to review full report at Codecov.

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

blocked by #2769

I can see quite a few comments of TODO FS. Could it be clarified if this PR is ready for merge? Some of the comment do look like they can be addressed later.
Instead of leaving these comments in the code, a follow up issue could be raised - especially for the comments in the tests.

These are left in for when I'm showing team the code.
It's so people know what I'm thinking and where I'm thinking it, before a ticket is made.
Most of these TODOs will be addressed during Alpha stages.
The comments do not affect reviewing of code.


Can't pickle the faiss vector store object in langchain

Issue you'd like to raise.
I got the error OSError: [Errno 22] Invalid argument when trying to pickle the faiss vector store. with the following code
merge_file_path = "combined_hf_faiss_vectorstore.pkl"
with open(merge_file_path, "wb") as f:
    pickle.dump(csfaq_index, f)

It works on mac local laptop but not on the linux machine in the Databricks cloud.
Here is the system info:
sysname='Linux',  release='5.15.0-1035-aws', version='#39~20.04.1-Ubuntu SMP Wed Apr 19 15:34:33 UTC 2023', machine='x86_64'
Any suggestion?
Suggestion:
No response

I'm getting this error while trying to dump my vectorstore ,here is the error  File "C:\chatbot_new\api\routers\pdf\multiple_pdf_router.py", line 148, in upload_files
serialized_document_search = gzip.compress(pickle.dumps(document_search))
TypeError: cannot pickle '_thread.RLock' object

Similar issue here to @adiigeek. Simple text file split and embedded via langchain.text_splitter import RecursiveCharacterTextSplitter  and langchain.embeddings import OpenAIEmbeddings
import pickle

vectorstore = FAISS.from_documents(documents, embeddings)

with open("vectorstore.pkl", "wb") as f:
    pickle.dump(vectorstore, f)

Leads to this error:
[4](vscode-notebook-cell:?execution_count=13&line=4) vectorstore = FAISS.from_documents(documents, embeddings)
[6](vscode-notebook-cell:?execution_count=13&line=6) with open("vectorstore.pkl", "wb") as f:
----> [7](vscode-notebook-cell:?execution_count=13&line=7)     pickle.dump(vectorstore, f)

TypeError: cannot pickle '_thread.RLock' object

@steve-barnard  installing  langchain==0.0.316 and openai==0.28.1 may resolve your issue. Please check.

Thank you @adiigeek, seems to be a simple version issue that is no longer supported in openai and langchain installs as of 1-11-2024.
This was the workaround I used and hopefully, this is helpful for someone else:
from langchain.vectorstores.faiss import FAISS
from langchain.embeddings import OpenAIEmbeddings

embeddings = OpenAIEmbeddings()

vectorstore = FAISS.from_documents(documents, embeddings)

vectorstore.save_local("vectorstore")

x = FAISS.load_local("vectorstore", OpenAIEmbeddings())

retriever = x.as_retriever()

Hi @steve-barnard, thanks for your suggestion! There do seem to be a few versioning issues with langchain and openai. Your approach worked for me, and didn't even need to create the retriever object.

Try this :
embeddings = OpenAIEmbeddings()
vectorstore = FAISS.from_documents(docs, embeddings)
vectorstore.save_local("vectorstore")
x = FAISS.load_local("vectorstore", OpenAIEmbeddings(), allow_dangerous_deserialization=True)
retriever = x.as_retriever()

Thank you I will give it a try and let you know
Regards
Hetesh
On Fri, 26 Apr 2024 at 8:19 AM, Madhumitha Kolkar @.***>
wrote:

Try this :
embeddings = OpenAIEmbeddings()
vectorstore = FAISS.from_documents(docs, embeddings)
vectorstore.save_local("vectorstore")
x = FAISS.load_local("vectorstore", OpenAIEmbeddings(),
allow_dangerous_deserialization=True)
retriever = x.as_retriever()
—
Reply to this email directly, view it on GitHub
https://github.com/langchain-ai/langchain/issues/5145#issuecomment-2078541487,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJLLWJTHCWWB2C5LFUDTLRDY7G6FDAVCNFSM6AAAAAAYMLWUMOVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDANZYGU2DCNBYG4
.
You are receiving this because you commented.Message ID:
@.***>


文件头部添加或规范化License内容

Ⅰ. Describe what this PR does
This pr is to add copyright in pkg/controllers/v1alpha1/jindo/suite_test.go
Ⅱ. Does this pull request fix one issue?

fixes #XXXX
Ⅲ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

/assign @ronggu


Adding ability to control red/green colors to make it more accessibility-friendly

LifetimeTracker is brilliant! I love it :)
One small suggestion I'd make is to make it possible for a developer to change the tint color of the text. This would be beneficial for developers who are a bit more visually impaired (so they can pick a green with their ideal contrast ratio), and for those who have red-green color blindness.
Just a small suggestion! Keep it up 🥇

good idea, I'd be happy to accept a pr with that improvement :)

PR with update has been merged. Closing.


Fix new executor is removing associative array when using custom scalar

Hi, I just came across that the new CoroutineExecutor is converting associative arrays to simple array, if such array would ever happen in your schema. The ReferenceExecutor is keeping the associative array.
Failing test
1) GraphQL\Tests\Executor\ExecutorSchemaTest::testExecutesUsingASchema
Failed asserting that two arrays are equal.
--- Expected
+++ Actual
@@ @@
             'body' => 'This is a post'
             'author' => Array (...)
             'meta' => Array (
-                'title' => 'My Article 1 | My Blog'
+                0 => 'My Article 1 | My Blog'
             )
         )
     )
 )

Example data / my use case:
In my side project I wanted to pass cropped image URLs for my js component, but the list is dynamic (some images have only 1 configuration, some can have 20 different ones).
{
  "id": "4574BB",
  "variantUrls": {
    "00": "/uploads/00/16029619-136d-4110-a31c-3e00c06cb482",
    "cb": "/uploads/cb/16029619-136d-4110-a31c-3e00c06cb482",
    "og": "/uploads/og/aa6f99d0-4710-4cf1-8e30-604d47be5cf4",
  }
}

When I created simple Scalar type, that was just passing variable out (as I trust the associative array from backend) the new Coroutine Executor is changing associative array to simple array without keys.
I probably should have created an ObjectType for that, but this way is slightly simpler to foreach, not having to check for nulls.

After I made all of this I noticed, that if I wrap the associative array in some kind of stdClass, this problem disappears. But at least I found out about this difference between executors.

@jakubkulhan Could you please review it?


Incorrect information about version skew in AKS

Your page about supported Kubernetes versions says:

Supported kubectl versions
You can use one minor version older or newer of kubectl relative to your kube-apiserver version, which is consistent with the Kubernetes support policy for kubectl.
For example, if your kube-apiserver is at 1.17, then you can use versions 1.16 to 1.18 of kubectl with that kube-apiserver.

But since Managed AAD was introduced, kubectl must be at least 1.18:

Prerequisites
The Azure CLI version 2.11.0 or later
Kubectl with a minimum version of 1.18.1 or kubelogin

We were running an AKS cluster with kube-apiserver version v1.17.7 with kubectl version 1.17.11 and noticed RBAC totally breaking down for us. Diagnose and Solve problems was very helpful for us to figure this out, but otherwise we would probably have spent a very long time before figuring this out, since the officially supported version skew (both by you and Kubernetes), states that kubectl 1.17 should work with kube-apiserver 1.17.

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

ID: ec484163-5d73-af3a-3d7b-9e0d421d2824
Version Independent ID: 42da7aed-a33d-e331-fb7f-4fb4b40e5813
Content: Supported Kubernetes versions in Azure Kubernetes Service - Azure Kubernetes Service
Content Source: articles/aks/supported-kubernetes-versions.md
Service: container-service
GitHub Login: @palma21
Microsoft Alias: jpalma

Thanks for the feedback, not sure I completely understood it though so please bear with me, the reason AAD clusters need 1.18.1+ kubectl is because it requires fixes and features that we introduced and were released in that version. Kubectl 1.18.1 is still within the supported skew window of +-1 minor version, so it's totally fine and supported to use it with a 1.17.7 cluster.
Your kubectl 1.17.11 works fine with the API server but does not support the AAD feature as listed on the requirements. So from what I can see both docs are correct?
Does this clarify? Is there something we could have done better here in your opinion?

Thanks for the feedback and bringing this to our notice . At this time we are reviewing the feedback and will update the document as appropriate .

Thanks for the response. I will try to clarify.

Kubectl 1.18.1 is still within the supported skew window of +-1 minor version, so it's totally fine and supported to use it with a 1.17.7 cluster.

Yes, I mostly agree about this part. Indeed kubectl 1.18.1 is supposed to be compatible with server version 1.17.7, and I also believe it is.
The big issue here is that it's obviously not true that "if your kube-apiserver is at 1.17, then you can use versions 1.16 to 1.18 of kubectl with that kube-apiserver", if Managed AAD is enabled. It should be true, but it isn't. The user cannot use kubectl 1.16 or 1.17 if Managed AAD is enabled (except maybe if the user is cluster owner). Instead the user must use kubectl 1.18. That is not what the documentation says.
Having put some thought about it since yesterday, I am fairly sure this is actually an accidental breakage of AKS rather than a documentation issue. So perhaps we should take this to another forum?

Your kubectl 1.17.11 works fine with the API server but does not support the AAD feature as listed on the requirements.

Yes, that is technically true. The documentation only mentions the supported version skew between kubectl and kube-apiserver; it never mentions Managed AAD. However, in practice the user would expect kubectl 1.17 to work with "any" Kubernetes cluster with API server version 1.17. But here it happens to be the case that Managed AAD breaks that compatibility.
Since Managed AAD breaks compatibility with kubectl <1.18, that feature should not have been made available until API server version 1.19, since users should expect kubectl 1.17 to be compatible with API server 1.17 and 1.18.

It's a very fair point, we're looking into ways of letting users know about their kubectl version compat. We didn't want to limit it just to 1.18 API since you can technically use normally with 1.17 API and 1.18 kubectl or with any version of Kubernetes and kubelogin which also allows you to use any kubectl version too.
We will try to be more proactive in that warning when the feature is enabled.

We didn't want to limit it just to 1.18 API since you can technically use normally with 1.17 API and 1.18 kubectl or with any version of Kubernetes and kubelogin which also allows you to use any kubectl version too.

I think that's inaccurate. If I'm not mistaken, RBAC cannot be disabled once Managed AAD is enabled, thus kubectl <1.18 will not work at all for anyone (except for cluster owners, whom may use the az aks get-credentials --admin option to bypass RBAC).
Also, it would not help to limit it to API server version 1.18, since kubectl 1.17 should work with server version 1.18. You would have to limit it to server version 1.19, since kubectl 1.17 is expected to not be compatible with that version.
And what's your plan for applications like Kubeapps, that may use the API server version to infer which version of the client side API to use?

We will try to be more proactive in that warning when the feature is enabled.

I'm glad to hear you will try to be more proactive about warnings about this in the future. A first step could be to make sure there's a user prompt before enabling it. We accidentally pressed the button that said "Click here to configure Managed AAD", and suddenly we had irreversibly enabled it for our cluster and have to inform our customers about the change, before we had the time to investigate all aspects of how it would impact our organization.

Thank you @lindhe for the feedback.
Based on the the discussion, there does seem to be any updates needed to the article.
#please-close


Fixed lucene url

Description
Fixed lucene url
Issues Resolved
https://github.com/opensearch-project/opensearch-build/issues/3874#issuecomment-1934891715
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Backport workflow failed because of a - in the branch name. Closed https://github.com/opensearch-project/anomaly-detection/pull/1158


Specify thread block size of a kernel launch

Can a user specify the thread block size when launching a kernel ?  It seems that the size is fixed at 256.  Thanks.

Hi @jinz2014, thanks for the suggestion. I'll update you when we have added this feature.


brotli handling #2

Not being able to import the brotli dependency should lead to a default of self.allow_brotli = kwargs.pop('allow_brotli', False).

I'm guessing this would be a fitting fix:
try:
    import brotli
except ImportError:
    brotli = None

self.allow_brotli = kwargs.pop('allow_brotli', bool(brotli))

well.. since its a dependency of setup.py ... not really a problem is it?

perhaps you should'nt harvest the code for your personal project and perhaps just incorporate my module as a dependency for yours?
just my 2 cents..

@pannal i have pushed 1.1.2 which will now address your 'issue' if you wish to repackage my module.

Refer ae146b460b332638bd1fb1a952321534c42187e9

I really appreciate what you're doing here. I hope this is always clear.
I have to reincorporate your project into mine, because I can't use your dependencies.
This is not something I do because I want to, but because I am caged by the Plex Media Server Python environment.
If I could, I would create pull requests that you could actually use.
Sorry.

Also, an issue posted here about your code is never meant to be negative.

@pannal As a past Plex channel developer, I know exactly what you mean by needing to reincorporate but where is the copyright notice?!

MIT License

Copyright (c) 2019 VeNoMouS

Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:

The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.

 IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.

The LICENSE file has now been incorporated. I'm sorry for not realizing that.
And to make sure: I don't make any meaningful money from my project.

It's MIT, make $$$ Just give credit where it's due if you do. :smiley:

You can see that I normally do, this was not intentional :)

@pannal Indeed.

It's MIT, make $$$ Just give credit where it's due if you do. 😃
I reinvest the ~20$ that my project makes into other developers. This is a zero-sum-game.

@pannal
https://blog.fossa.io/you-cant-get-around-code-scanning-if-you-care-about-open-source-licenses-2db1fde43fb5 -> https://fossa.com/ -> https://app.fossa.com/account/login?next=%2F -> https://github.com/badges/shields/issues/1529 ->


Update dependencies in glide.yaml for make to succeed in building odo binary

What type of PR is this?
/kind code-refactoring
What does does this PR do / why we need it:
This PR is based on doing glide update -v and trying to fix the errors to help make succeed in building the odo binary. This is proposed as a separate PR because glide update -v on the current master branch breaks make.
Which issue(s) this PR fixes:
None. But it unblocks #2920 as well as @mik-dass.
More info can be found on https://github.com/openshift/odo/issues/2920#issuecomment-639384058 and discussion thereafter.
How to test changes / Special notes to the reviewer:
CI should pass.

Travis failure looks unrelated to the changes made:
[odo]  ✗  Creating component [192ms]

[odo]  ✗  Failed to create component with name nodejs. Please use `odo config view` to view settings used to create component. Error: failed to create component with args {Name:nodejs SourcePath:./ SourceRef: SourceType:local ImageName:nodejs EnvVars:[DEBUG_PORT=5858] Ports:[8080/TCP] Resources:&ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{},} ApplicationName:nodeapp Wait:false StorageToBeMounted:map[/mnt/pv1:&PersistentVolumeClaim{ObjectMeta:{pv1-nodeapp-pvc  ckbbugylgw /api/v1/namespaces/ckbbugylgw/persistentvolumeclaims/pv1-nodeapp-pvc 17dc54ec-b137-11ea-bac5-42010a1e0034 3398 0 2020-06-18 07:41:16 +0000 UTC <nil> <nil> map[app:nodeapp app.kubernetes.io/instance:nodejs app.kubernetes.io/managed-by:odo app.kubernetes.io/managed-by-version:v1.2.2 app.kubernetes.io/part-of:nodeapp app.kubernetes.io/storage-name:pv1] map[] [] [kubernetes.io/pvc-protection]  []},Spec:PersistentVolumeClaimSpec{AccessModes:[ReadWriteOnce],Resources:ResourceRequirements{Limits:ResourceList{},Requests:ResourceList{storage: {{1073741824 0} {<nil>} 1Gi BinarySI},},},VolumeName:,Selector:nil,StorageClassName:nil,VolumeMode:nil,DataSource:nil,},Status:PersistentVolumeClaimStatus{Phase:Pending,AccessModes:[],Capacity:ResourceList{},Conditions:[]PersistentVolumeClaimCondition{},},}] StdOut:<nil>}: unable to update owner reference of storage: Operation cannot be fulfilled on persistentvolumeclaims "pv1-nodeapp-pvc": the object has been modified; please apply your changes to the latest version and try again

Deleting project: ckbbugylgw

Running odo with args [odo project delete ckbbugylgw -f]

[odo] I0618 07:41:17.459903   24338 application.go:49] Unable to list Service Catalog instances: unable to list ServiceInstances: serviceinstances.servicecatalog.k8s.io is forbidden: User "developer" cannot list serviceinstances.servicecatalog.k8s.io in the namespace "ckbbugylgw": no RBAC policy matched

[odo] This project contains the following applications, which will be deleted

[odo] Application nodeapp

[odo] I0618 07:41:17.473653   24338 occlient.go:2825] Getting DeploymentConfig: nodejs-nodeapp

[odo] I0618 07:41:17.496363   24338 component.go:987] Source for component nodejs is  (local)

[odo] I0618 07:41:17.496379   24338 url.go:379] Listing routes with label selector: app.kubernetes.io/part-of=nodeapp,app.kubernetes.io/instance=nodejs

[odo] I0618 07:41:17.496384   24338 occlient.go:2684] Listing routes with label selector: app.kubernetes.io/part-of=nodeapp,app.kubernetes.io/instance=nodejs

[odo] I0618 07:41:17.510614   24338 occlient.go:2825] Getting DeploymentConfig: nodejs-nodeapp

[odo] This application has following components that will be deleted

[odo] I0618 07:41:17.551070   24338 occlient.go:2825] Getting DeploymentConfig: nodejs-nodeapp

[odo] I0618 07:41:17.554933   24338 component.go:987] Source for component nodejs is  (local)

[odo] I0618 07:41:17.554953   24338 url.go:379] Listing routes with label selector: app.kubernetes.io/part-of=nodeapp,app.kubernetes.io/instance=nodejs

[odo] I0618 07:41:17.554958   24338 occlient.go:2684] Listing routes with label selector: app.kubernetes.io/part-of=nodeapp,app.kubernetes.io/instance=nodejs

[odo] I0618 07:41:17.560637   24338 occlient.go:2825] Getting DeploymentConfig: nodejs-nodeapp

[odo] I0618 07:41:17.623986   24338 request.go:565] Throttling request took 63.29841ms, request: GET:https://<IP_ADDRESS>:8443/apis/apps.openshift.io/v1/namespaces/ckbbugylgw/deploymentconfigs/nodejs-nodeapp

[odo] I0618 07:41:17.824009   24338 request.go:565] Throttling request took 196.963633ms, request: GET:https://<IP_ADDRESS>:8443/apis/apps.openshift.io/v1/namespaces/ckbbugylgw/deploymentconfigs?labelSelector=app.kubernetes.io%2Fpart-of%3Dnodeapp%2Capp.kubernetes.io%2Finstance%3Dnodejs

[odo] component named nodejs

[odo] No services / could not get services

[odo] I0618 07:41:17.830676   24338 project.go:136] unable to list services: unable to list ServiceInstances: serviceinstances.servicecatalog.k8s.io is forbidden: User "developer" cannot list serviceinstances.servicecatalog.k8s.io in the namespace "ckbbugylgw": no RBAC policy matched

[odo]  ✓  Deleted project : ckbbugylgw

[odo]  ⚠  Warning! Projects are deleted from the cluster asynchronously. Odo does its best to delete the project. Due to multi-tenant clusters, the project may still exist on a different node.

[odo] I0618 07:41:17.836219   24338 odo.go:72] Could not get the latest release information in time. Never mind, exiting gracefully :)

Deleting dir: /tmp/836974187

• Failure [3.114 seconds]

odo storage command tests

/home/travis/gopath/src/github.com/openshift/odo/tests/integration/cmd_storage_test.go:13

  when using storage command with default flag values

  /home/travis/gopath/src/github.com/openshift/odo/tests/integration/cmd_storage_test.go:53

    should add a storage, list and delete it [It]

    /home/travis/gopath/src/github.com/openshift/odo/tests/integration/cmd_storage_test.go:54

    No future change is possible.  Bailing out early after 0.594s.

    Running odo with args [odo push --context /tmp/836974187]

    Expected

        <int>: 1

    to match exit code:

        <int>: 0

    /home/travis/gopath/src/github.com/openshift/odo/tests/helper/helper_run.go:34

/test v4.5-integration-e2e
#2641
 • Failure [341.483 seconds]
odo supported images e2e tests
/go/src/github.com/openshift/odo/tests/e2escenarios/e2e_images_test.go:14
  odo supported images deployment
  /go/src/github.com/openshift/odo/tests/e2escenarios/e2e_images_test.go:83
    Should be able to verify the centos7-s2i-nodejs:10.x image [It]
[Fail] odo supported images e2e tests odo supported images deployment [It] Should be able to verify the centos7-s2i-nodejs:10.x image
/go/src/github.com/openshift/odo/tests/helper/helper_generic.go:140
Ran 23 of 23 Specs in 873.305 seconds
FAIL! -- 22 Passed | 1 Failed | 0 Pending | 0 Skipped

@johnmcollier @yangcao77 We need your inputs on this. Not just PR review, but we need you to let us know if the changes proposed in this PR could break anything w.r.t. docker support. Pinged you folks because you worked the most on adding docker support.
@adisky @girishramnani @kadel if you have any inputs on this, please let us know.

Most of the PR changes are dependencies changes, I don't see any impact on docker URL, which I was specifically working on.
The changes to test code looks good to me as well.

Looks like the tests failed because of lack of resources on the infra.
4.2 failure logs:
 2020/06/18 12:24:41 Acquiring lease for "aws-quota-slice"
2020/06/18 14:24:41 No custom metadata found and prow metadata already exists. Not updating the metadata.
2020/06/18 14:24:42 Ran for 2h3m37s
error: some steps failed:
  * could not run steps: step integration-e2e failed: failed to acquire lease: resources not found
time="2020-06-18T14:24:42Z" level=info msg="Reporting job state \"failed\" with reason \"executing_graph:step_failed:utilizing_lease:acquiring_lease\""

4.5 failure logs:
 2020/06/18 14:24:55 No custom metadata found and prow metadata already exists. Not updating the metadata.
2020/06/18 14:24:56 Ran for 2h4m4s
error: some steps failed:
  * could not run steps: step integration-e2e failed: failed to acquire lease: resources not found
time="2020-06-18T14:24:56Z" level=info msg="Reporting job state \"failed\" with reason \"executing_graph:step_failed:utilizing_lease:acquiring_lease\""

/retest

Travis failures look to be related to failure in pulling images from quay.io:
[odo]  ✗  Failed to start component with name gmerej.
[odo] Error: Failed to create the component: unable to create or update component: unable to pull and start container runtime for component gmerej: Unable to pull quay.io/eclipse/che-nodejs10-ubi:nightly image: Unable to pull image: Error response from daemon: Get https://quay.io/v2/: EOF
[odo]  ✗  Pulling image quay.io/eclipse/che-nodejs10-ubi:nightly [78ms]
Removing locally running Docker images with label component=gmerejListing locally running Docker images with label component=gmerejRunning docker with args [docker ps -q --filter label=component=gmerej]
Setting current dir to: /home/travis/gopath/src/github.com/openshift/odo/tests/integration/devfile/docker
Deleting dir: /tmp/419640540
• Failure [16.312 seconds]
odo docker devfile url pushtarget command tests
/home/travis/gopath/src/github.com/openshift/odo/tests/integration/devfile/docker/cmd_docker_devfile_url_pushtarget_test.go:14
  Switching pushtarget
  /home/travis/gopath/src/github.com/openshift/odo/tests/integration/devfile/docker/cmd_docker_devfile_url_pushtarget_test.go:44
    switch from kube to docker, odo push should display warning [It]
    /home/travis/gopath/src/github.com/openshift/odo/tests/integration/devfile/docker/cmd_docker_devfile_url_pushtarget_test.go:63

and
[odo] I0618 12:47:50.059616   10676 utils.go:86] Found component "Container" with name "runtime"
[odo]  •  Pulling image quay.io/eclipse/che-nodejs10-ubi:nightly  ...
[odo]  ✗  Pulling image quay.io/eclipse/che-nodejs10-ubi:nightly [15s]
[odo]  ✗  Failed to start component with name lhvfye.

/approve

@dharmit looks good to me, There should be no problem in future too as we updated our docker mock client as per docker api.

4.5 failure looks like a flake since it's happening in JustBeforeEach IIUC:
 Created dir: /tmp/745678176
Creating a new project: esmqrrjxge
Running odo with args [odo project create esmqrrjxge -w -v4]
[odo]  ✗  invalid configuration: [context was not found for specified context: uujiobnmxh/api-ci-op-c6zsjp7f-2f74e-origin-ci-int-aws-dev-rhcloud-com:6443/developer, cluster has no server defined]
[odo] Please login to your server:
[odo]
[odo] odo login https://mycluster.mydomain.com
[odo]
Deleting project: amcjulaaaa
Running odo with args [odo project delete amcjulaaaa -f]
[odo]  ✗  The project amcjulaaaa does not exist. Please check the list of projects using `odo project list`
Deleting dir: /tmp/745678176
• Failure in Spec Setup (JustBeforeEach) [0.820 seconds]
odo component command tests
/go/src/github.com/openshift/odo/tests/integration/cmd_cmp_test.go:13
  Creating component
  /go/src/github.com/openshift/odo/tests/integration/component.go:52
    should error when listing components (basically anything other then creating) with --project and --context  [JustBeforeEach]
    /go/src/github.com/openshift/odo/tests/integration/component.go:80
    No future change is possible.  Bailing out early after 0.134s.

    Running odo with args [odo project create esmqrrjxge -w -v4]
    Expected
        <int>: 1
    to match exit code:
        <int>: 0

Weirdly, 4.2 is also failing due to project creation error:
 Created dir: /tmp/880224045
Creating a new project: nckoeoehmn
Running odo with args [odo project create nckoeoehmn -w -v4]
[odo]  •  Waiting for project to come up  ...
[odo]  ✗  Timeout: request did not complete within requested timeout 30s
[odo]  ✗  Waiting for project to come up [30s]
Deleting project:
Running odo with args [odo project delete  -f]
[odo] I0619 07:31:24.680148    9656 request.go:757] Error in request: resource name may not be empty
[odo]  ✗  The project  does not exist. Please check the list of projects using `odo project list`
• Failure in Spec Setup (BeforeEach) [31.058 seconds]
odo storage command tests
/go/src/github.com/openshift/odo/tests/integration/cmd_storage_test.go:13
  when running storage list command to check state [BeforeEach]
  /go/src/github.com/openshift/odo/tests/integration/cmd_storage_test.go:144
    should list storage with correct state
    /go/src/github.com/openshift/odo/tests/integration/cmd_storage_test.go:145
    No future change is possible.  Bailing out early after 30.622s.

    Running odo with args [odo project create nckoeoehmn -w -v4]
    Expected
        <int>: 1
    to match exit code:
        <int>: 0

/retest

I am gonna LGTM this even though I am also the approver because the AC of this PR is about updating the deps and make the tests pass in the process. Which is achieved.
/lgtm

I am gonna LGTM this even though I am also the approver because the AC of this PR is about updating the deps and make the tests pass in the process. Which is achieved.
/lgtm

Thank you!


FLX-182

Provide system load to service mesh

Long int has at least 32 bits -> enough for 68 years of uptime.
uptime_seconds appears to be of type 'long long int' (64 bit) on armhf, but of type 'long int' (at least 32 bit, but probably 64) on arm64 and amd64
solved by casting to 'unsigned long int' first.


Hint to "try: --prerelease=allow" when I already am

Apologies for not minimising this reproduction - I do not have the time right now and I hope that this report is still useful.
I am trying to restore an old project, https://github.com/adamtheturtle/dcos-e2e.
I try to install dependencies:
$ uv --version
uv 0.1.45
$ uv pip install --exclude-newer 2018-10-08 --prerelease=allow --verbose .
INFO Found a virtualenv through VIRTUAL_ENV at: /Users/adam/.virtualenvs/dcos-e2e
DEBUG Cached interpreter info for Python 3.12.3, skipping probing: /Users/adam/.virtualenvs/dcos-e2e/bin/python
DEBUG Using Python 3.12.3 environment at /Users/adam/.virtualenvs/dcos-e2e/bin/python
DEBUG Trying to lock if free: /Users/adam/.virtualenvs/dcos-e2e/.lock
DEBUG At least one requirement is not satisfied: file:///Users/adam/Documents/forks/dcos-e2e
DEBUG Using registry request timeout of 30s
DEBUG Trying to lock if free: /Users/adam/Library/Caches/uv/built-wheels-v3/path/ffcc5eebe36891de/.lock
DEBUG Preparing metadata for: file:///Users/adam/Documents/forks/dcos-e2e
DEBUG No static `PKG-INFO` available for: file:///Users/adam/Documents/forks/dcos-e2e (MissingPkgInfo)
DEBUG No static `pyproject.toml` available for: file:///Users/adam/Documents/forks/dcos-e2e (MissingPyprojectToml)
DEBUG Solving with target Python version 3.12.3
DEBUG Adding direct dependency: setuptools>=40.8.0
DEBUG Found fresh response for: https://pypi.org/simple/setuptools/
DEBUG Searching for a compatible version of setuptools (>=40.8.0)
DEBUG No compatible version found for: setuptools
error: Failed to build: `file:///Users/adam/Documents/forks/dcos-e2e`
  Caused by: Failed to install requirements from setup.py build (resolve)
  Caused by: No solution found when resolving: setuptools>=40.8.0
  Caused by: Because only setuptools<40.8.0 is available and you require setuptools>=40.8.0, we can conclude that the requirements are unsatisfiable.

hint: Pre-releases are available for setuptools in the requested range (e.g., 63.0.0b1), but pre-releases weren't enabled (try: `--prerelease=allow`)

I would not expect the hint at the bottom - I am already using --prerelease=allow.

Thanks.

Mmm we don't propagate pre-releases to source distribution builds IIRC.

Not sure what to do here. I guess: don't show this at all for source builds?


When using devops, devops-jenkins restarts frequently.

What is version of KubeSphere DevOps has the issue?
v3.3.0-rc.3
How did you install the Kubernetes? Or what is the Kubernetes distribution?
No response
What happened?
When using devops, devops-jenkins restarts frequently. I found that the memory and cpu usage reached the limits.

Relevant log output
No response
Additional information
No response

I saved this problem by increase limits.

/remove-kind bug


Install and configure on Synology Nas

Anybody know how to get this installed on a synology nas docker using qbitorrent docker also? I am a little new to this

I installed it on my synology nas but not in a docker container.  I just followed the install steps exactly.  It does communicate to my rtorrent instances in a docker container on my nas tho

I installed it on my synology nas but not in a docker container. I just followed the install steps exactly. It does communicate to my rtorrent instances in a docker container on my nas tho

Do you mind sharing your steps? I want to see about getting it to work with qbitorrent

I literally followed the quickstart guide
python3 -m venv ~/.autotorrent # Create virtual environment where we install autotorrent2
~/.autotorrent/bin/pip install autotorrent2 # Actually install autotorrent2

# Optional, add at2 to your commandline
echo "alias at2=~/.autotorrent/bin/at2" >> ~/.bashrc
source ~/.bashrc
```

I installed it on my synology nas but not in a docker container. I just followed the install steps exactly. It does communicate to my rtorrent instances in a docker container on my nas tho

Can you please share with us the [clients] setup for rtorrent in (config.toml)? Is there anything I've to do to enable the scgi port in rtorrent?
Also, how did you align the paths in both rtorrent docker and autotorrent2?
I was able to connect to qBittorrent and Transmission, but the path wasn't aligned.
Thank you.

[clients.rtorrent-2020]
display_name = "rtorrent-2020"
client_type = "rtorrent"
url = "http://<IP_ADDRESS>:8006/RPC2"
session_path = "/volume3/docker/crazy-max-rutorrent-PAll-2020/rtorrent/.session/"

For the paths refer to https://github.com/JohnDoee/autotorrent2/issues/13 and subsequently https://github.com/JohnDoee/autotorrent/issues/33

Thanks a lot! It worked. The "RPC2" url should be added to the documentation.


Website is down for me

Unable to access any part of the discordlookup.mesavirep.xyz/ website

ditto

same


Update makefiles to work properly with custom $N64_INST

These changes fix the following issues:

Update n64.mk to install using sudo so if you do have permission to write to $PREFIX you will be able to write there
Update the RSP build command to use $ASFLAGS instead of $N64_ASFLAGS. This fixes an issue I saw when trying to build @snacchus ugfx code with a custom $N64_INST path. $N64_ASFLAGS does not include the additional -I$(CURDIR)/include so rsp code that is in the libdragon library tree won't be able to find rsp.inc
Another problem seen with ugfx, if you're building rsp code in the libdragon library tree, when it creates the section names it will use the whole $BUILD_DIR path in the section name. If the path name has periods in it, gcc will make those underscores instead. The make file needs to substitute periods with underscores like it does for slashes.

For problem #1, I've modified it to instead install the n64.mk file in $(INSTALLDIR)/include/n64.mk and updated the examples to use
include $(N64_INST)/include/n64.mk

We could also updated it to install to $(INSTALLDIR)/n64.mk and update the examples to use
include $(N64_INST)/n64.mk

Although this makes the include line in the make file simpler, the default $N64_INST is /usr/local and this would pollute the root of /usr/local with the n64.mk file. Therefore I think we should go with the longer path that includes the "include" folder.

I'm removing that comment in the docker PR.


Iterate on new planetarydata.org updates per feedback

💡 Description

[ ] partner page - link to agency websites where possible
[ ] partner page - the logos are not really readable. may need different layout to actually see what they are
[ ] Add IPDA logo (from @edwardbarraza )
[ ] Link Contact Us to email PDS Help Desk and remove address info
[ ] Remove Social section
[ ] Add favicon (some simple planet image?)
[ ] Update theme to use fonts and color scheme from HDS (sent via email). contact @edwardbarraza for additional guidance.

https://app.zenhub.com/files/349191592/bfc963a9-efea-46ed-ad7a-124ffa43d399/download
Potential logos in the PDF above

Nice 'n minimal 👍

@edwardbarraza how do I get ahold of the NASA HDS theme for WordPress?

@nutjob4life note to self; see https://developer.nasa.gov/nwmt/hds-wordpress/tree/preprod/themes

Added @edwardbarraza as an Administrator on the site.

@edwardbarraza @jordanpadams the NASA HDS theme is now installed onto the site, but all content is now invisible. I don't suppose you know of any HDS experts who can advise? I'm tempted to go back to the "Marenda" theme.

@nutjob4life we can just go with another theme for now. the HDS team is not accessible. the catch being I just want to make sure we adapt our color scheme to be appropriately accessible

@jordanpadams I'm leave the NASA HDS theme active for now; maybe @edwardbarraza has an idea on how to work it?

@nutjob4life unfortunately, no one on the team has any experience with Wordpress. so I think we are just going to have to drop it for now 😞

Fair enough 😕

@jordanpadams to review

@nutjob4life can we update the "IPDA" links at the top and bottom of the page with the icon? Looks a little weird...

@nutjob4life can we update the "IPDA" links at the top and bottom of the page with the icon? Looks a little weird...

@jordanpadams by "icon" you mean the logo that @edwardbarraza created?

@nutjob4life yes! Thanks!

@jordanpadams will see if I can wedge it into those places, as soon as DSIO-3426 is fixed

@jordanpadams done!

@nutjob4life looks great! can we run another scan for accessibility?
also, one typo "discovery" -> "discover"
is there a login to wordpress somewhere so I could make updates in the future for silly things like that?

@jordanpadams fixed the typo.
It looks like you have an account on the site already. I've had the site send you a password reset prompt. Let me know if the email doesn't show up.


DHCPD service times out multiple times during boot, postponing it by more than a minute

Describe the bug
On the latest upgrade, I experienced the dhcpd service timing out multiple times, postponing the appearance of the graphics target service by more than a minute. It did eventually come up with working networking.
The problem doesn't arise with the default networking.networkmanager.wifi.backend setting, only with iwd.
With git bisect I managed to pinpoint the commit causing the regression: 713b60460fb502651ec1b9f6c92d34ad448346a7.
Could  you @xaverdh perhaps look into it a bit?
To Reproduce
Steps to reproduce the behavior:

Having the following in my configuration.nix file:

  networking.networkmanager.enable = true;
  networking.networkmanager.wifi.backend = "iwd";

  networking.useDHCP = false;
  networking.interfaces.enp0s31f6.useDHCP = false;
  networking.interfaces.wlp3s0.useDHCP = true;

Changing to a commit after 713b60460fb502651ec1b9f6c92d34ad448346a7
Having the following network interfaces:

1: lo: <LOOPBACK,UP,LOWER_UP> mtu 65536 qdisc noqueue state UNKNOWN mode DEFAULT group default qlen 1000
    link/loopback 00:00:00:00:00:00 brd 00:00:00:00:00:00
2: enp0s31f6: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc fq_codel state UP mode DEFAULT group default qlen 1000
    link/ether e8:6a:64:dc:c8:38 brd ff:ff:ff:ff:ff:ff
4: wlan0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UP mode DORMANT group default qlen 1000
    link/ether 98:2c:bc:4c:d3:35 brd ff:ff:ff:ff:ff:ff
    altname wlp3s0

Journal log
Jan 18 18:53:46 nixos iwd[1159]: Wiphy: 0, Name: phy0
Jan 18 18:53:46 nixos iwd[1159]:         Permanent Address: 98:2c:bc:4c:d3:35
Jan 18 18:53:46 nixos iwd[1159]:         Bands: 2.4 GHz 5 GHz
Jan 18 18:53:46 nixos iwd[1159]:         Ciphers: CCMP TKIP BIP
Jan 18 18:53:46 nixos iwd[1159]:         Supported iftypes: ad-hoc station ap p2p-client p2p-go p2p-device
Jan 18 18:53:46 nixos kernel: ------------[ cut here ]------------
Jan 18 18:53:46 nixos kernel: WARNING: CPU: 2 PID: 1159 at net/wireless/nl80211.c:7575 nl80211_get_reg_do+0x1f6/0x230 [cfg80211]
Jan 18 18:53:46 nixos kernel: Modules linked in: bnep ccm algif_aead cbc des_generic libdes ecb algif_skcipher hmac cmac sha512_ssse3 sha512_generic md4 algif_hash af_alg 8021q snd_hda_codec_hdmi snd_hda_codec_realtek snd_hda_codec_gener>
Jan 18 18:53:46 nixos kernel:  x86_pkg_temp_thermal intel_powerclamp nls_cp437 libarc4 snd_compress coretemp ac97_bus crc32_pclmul ghash_clmulni_intel ip6table_filter snd_pcm_dmaengine vfat aesni_intel drm fat iwlwifi deflate snd_hda_int>
...
Jan 18 18:53:46 nixos kernel: ---[ end trace a52ce925392eb8c5 ]---
Jan 18 18:53:46 nixos systemd[1]: Finished Address configuration of enp0s31f6.
Jan 18 18:54:16 nixos dhcpcd[1155]: timed out
Jan 18 18:54:16 nixos dhcpcd[1155]: timed out
Jan 18 18:54:16 nixos dhcpcd[1155]: forked to background, child pid 1538
Jan 18 18:54:16 nixos dhcpcd[1538]: main: eloop_start: Invalid argument
Jan 18 18:54:16 nixos systemd[1]: dhcpcd.service: Can't open PID file /run/dhcpcd.pid (yet?) after start: Operation not permitted
Jan 18 18:54:16 nixos dhcpcd[1538]: dhcpcd exited
Jan 18 18:54:16 nixos systemd[1]: dhcpcd.service: Failed with result 'protocol'.
Jan 18 18:54:16 nixos systemd[1]: Failed to start DHCP Client.
Jan 18 18:54:16 nixos systemd[1]: Starting Network Manager Script Dispatcher Service...
Jan 18 18:54:16 nixos systemd[1]: Started Network Manager Script Dispatcher Service.
Jan 18 18:54:17 nixos systemd[1]: dhcpcd.service: Scheduled restart job, restart counter is at 1.
Jan 18 18:54:17 nixos systemd[1]: Stopped DHCP Client.
Jan 18 18:54:17 nixos systemd[1]: Starting DHCP Client...
Jan 18 18:54:17 nixos systemd[1]: systemd-hostnamed.service: Succeeded.
Jan 18 18:54:17 nixos dhcpcd[1542]: dev: loaded udev
Jan 18 18:54:17 nixos dhcpcd[1542]: no valid interfaces found
Jan 18 18:54:17 nixos dhcpcd[1542]: no valid interfaces found
Jan 18 18:54:27 nixos systemd[1]: NetworkManager-dispatcher.service: Succeeded.
Jan 18 18:54:47 nixos dhcpcd[1542]: timed out
Jan 18 18:54:47 nixos dhcpcd[1542]: timed out
Jan 18 18:54:47 nixos dhcpcd[1542]: forked to background, child pid 1545
Jan 18 18:54:47 nixos systemd[1]: Started DHCP Client.
Jan 18 18:55:14 nixos systemd[1]: sys-subsystem-net-devices-wlp3s0.device: Job sys-subsystem-net-devices-wlp3s0.device/start timed out.
Jan 18 18:55:14 nixos systemd[1]: Timed out waiting for device /sys/subsystem/net/devices/wlp3s0.
Jan 18 18:55:14 nixos systemd[1]: Dependency failed for Address configuration of wlp3s0.

Expected behavior
It should not hold up boot
Metadata

system: "x86_64-linux"
host os: Linux 5.10.5, NixOS, 21.03pre262347.257cbbcd3ab (Okapi)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.3.10
channels(user): "home-manager, nixpkgs-21.03pre264143.7d71001b796"
channels(root): "nixos-21.03pre263901.68398d2dd50"
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Does it work again, if you replace  networking.interfaces.wlp3s0.useDHCP = true by networking.interfaces.wlan0.useDHCP = true?

Does it work again, if you replace  networking.interfaces.wlp3s0.useDHCP = true by networking.interfaces.wlan0.useDHCP = true?

Yes, it did solve the problem, thank you very much!
Should I look into how the default installer's auto-generated config file handles the issue? Is there a possibility for a bug there (like in my case, would it still generate wlp3s0?)

Yes, it did solve the problem, thank you very much!
Should I look into how the default installer's auto-generated config file handles the issue? Is there a possibility for a bug there (like in my case, would it still generate wlp3s0?)

Yes, it did solve the problem, thank you very much!
Should I look into how the default installer's auto-generated config file handles the issue? Is there a possibility for a bug there (like in my case, would it still generate wlp3s0?)

It will generate that line based on the names of the interface the system sees when booting from the install medium. Since the installer doesn't use iwd by default, the interface will be different (there is a fundamental difference in naming between the iwd setup and the wpa_supplicant one). Not sure what the right thing to do is here, since this can not easily be abstracted away I think.

Yes, it did solve the problem, thank you very much!
Should I look into how the default installer's auto-generated config file handles the issue? Is there a possibility for a bug there (like in my case, would it still generate wlp3s0?)

It will generate that line based on the names of the interface the system sees when booting from the install medium. Since the installer doesn't use iwd by default, the interface will be different (there is a fundamental difference in naming between the iwd setup and the wpa_supplicant one). Not sure what the right thing to do is here, since this can not easily be abstracted away I think.


grafana: tighten grafana charts k8s RBAC permissions (ClusterRole -> Role)

I saw that Grafana is creating a PodSecurityPolicy, which is something that is being deprecated and removed from k8s and we get warnings about it.
Looking into that further, I see that grafana chart is granted a ClusterRole to read configmaps and secrets, which I suspect may be more permissions than is relevant for grafana to have - at least i suspect so when its in the same k8s namespace as prometheus.
With that in mind, I'd like to try tighten the permissions. This means that if the grafana software would be compromised for example, they can't read k8s Secrets in other namespaces etc.
Action point

Trial setting rbac.namespaced=true and rbac.pspEnabled=false

Related

Default values include rbac.namespaced=false and rbac.pspEnabled=true
Role and ClusterRole resources.

The ClusterRole created for our grafana isn't containing any rules, so why not declare rbac.namespaced=true and avoid making someone consider reviewing such unexpected permissions grant again.
I think it should be fine to adjust these default values.
The PSP enforces this currently:
support-grafana         false          RunAsAny   RunAsAny    MustRunAs   MustRunAs   false            configMap,emptyDir,projected,csi,secret,downwardAPI,persistentVolumeClaim

spec:
  allowPrivilegeEscalation: false
  fsGroup:
    ranges:
    - max: 65535
      min: 1
    rule: MustRunAs
  requiredDropCapabilities:
  - ALL
  runAsUser:
    rule: RunAsAny
  seLinux:
    rule: RunAsAny
  supplementalGroups:
    ranges:
    - max: 65535
      min: 1
    rule: MustRunAs
  volumes:
  - configMap
  - emptyDir
  - projected
  - csi
  - secret
  - downwardAPI
  - persistentVolumeClaim