Error 404 on api/v2/monitor/system/status

FotiOS version : 5.6.8
Hello,
I have an error with the exporter :
2022/02/10 14:08:49 Error: API connectivity test failed, Response code was 404, expected 200 (path: "api/v2/monitor/system/status")
2022/02/10 14:08:49 Probe of "https://myip" failed, took 0.016 seconds
I verifiy thet my token was correct and it seems to be correct  :
curl -k https://myip/api/v2/monitor/system/resource/usage?access_token=mytoken
"vdom":"myvdom",
"path":"system",
"name":"resource",
"action":"usage",
"status":"success",
"serial":"myserial",
"version":"v5.6.8",
"build":1672
can someone help me ?

up please

I think the oldest version we have tested with is FortiOS 6.0. Anything older than that is unsupported

我认为我们测试过的最旧版本是 FortiOS 6.0。任何早于此的内容均不受支持

Sorry, the problem still exists in my version
Fortigate_exporter Version: 1.23.2
Fortigate Version: v7.0.12
prometheus Version:v2.47.0
This causes Fortigate data to be discontinuous and intermittent.😒
systemctl --no-pager  status fortigate-exporter.service
● fortigate-exporter.service - fortigate-exporter
     Loaded: loaded (/etc/systemd/system/fortigate-exporter.service; enabled; vendor preset: enabled)
     Active: active (running) since Tue 2024-01-02 15:10:47 CST; 34min ago
   Main PID: 4025680 (fortigate-expor)
      Tasks: 11 (limit: 19119)
     Memory: 11.2M
     CGroup: /system.slice/fortigate-exporter.service
             └─4025680 /usr/local/bin/fortigate-exporter -insecure --auth-file /data/prometheus/fortigate-key.yaml

1月 02 15:42:55 prometheus-server fortigate-exporter[4025680]: 2024/01/02 15:42:55 Warning: Response code was 404, expected 200 (path: "api/v2/monitor/system/sensor-info")
1月 02 15:42:55 prometheus-server fortigate-exporter[4025680]: 2024/01/02 15:42:55 Probe of "https://<IP_ADDRESS>:10443" failed, took 5.667 seconds
1月 02 15:43:20 prometheus-server fortigate-exporter[4025680]: 2024/01/02 15:43:20 Warning: Response code was 404, expected 200 (path: "api/v2/monitor/system/sensor-info")
1月 02 15:43:20 prometheus-server fortigate-exporter[4025680]: 2024/01/02 15:43:20 Probe of "https://<IP_ADDRESS>:10443" failed, took 0.641 seconds
1月 02 15:43:55 prometheus-server fortigate-exporter[4025680]: 2024/01/02 15:43:55 Warning: Response code was 404, expected 200 (path: "api/v2/monitor/system/sensor-info")
1月 02 15:43:57 prometheus-server fortigate-exporter[4025680]: 2024/01/02 15:43:57 Probe of "https://<IP_ADDRESS>:10443" failed, took 7.315 seconds
1月 02 15:44:25 prometheus-server fortigate-exporter[4025680]: 2024/01/02 15:44:25 Warning: Response code was 404, expected 200 (path: "api/v2/monitor/system/sensor-info")
1月 02 15:44:25 prometheus-server fortigate-exporter[4025680]: 2024/01/02 15:44:25 Probe of "https://<IP_ADDRESS>:10443" failed, took 5.636 seconds
1月 02 15:44:50 prometheus-server fortigate-exporter[4025680]: 2024/01/02 15:44:50 Warning: Response code was 404, expected 200 (path: "api/v2/monitor/system/sensor-info")
1月 02 15:44:50 prometheus-server fortigate-exporter[4025680]: 2024/01/02 15:44:50 Probe of "https://<IP_ADDRESS>:10443" failed, took 0.641 seconds

@happinesslijian see https://github.com/bluecmd/fortigate_exporter/issues/190#issuecomment-1228537332

@happinesslijian参见#190（评论）

I have filtered as follows, it was fine at first, but after waiting for a while, the following problem occurred. I'm not sure how to solve this problem. I read related issues. My prometheus fetches every 30 seconds.
global:
  scrape_interval: 30s

exclude:
  - System/SensorInfo

systemctl status fortigate-exporter.service
● fortigate-exporter.service - fortigate-exporter
     Loaded: loaded (/etc/systemd/system/fortigate-exporter.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2024-01-03 10:29:46 CST; 2h 8min ago
   Main PID: 4159665 (fortigate-expor)
      Tasks: 11 (limit: 19119)
     Memory: 11.1M
     CGroup: /system.slice/fortigate-exporter.service
             └─4159665 /usr/local/bin/fortigate-exporter -insecure --auth-file /data/prometheus/fortigate-key.yaml

1月 03 12:37:50 prometheus-server fortigate-exporter[4159665]:         /opt/hostedtoolcache/go/1.21.5/x64/src/net/http/server.go:2136 +0x29
1月 03 12:37:50 prometheus-server fortigate-exporter[4159665]: net/http.(*ServeMux).ServeHTTP(0xd32020?, {0x9d8f98, 0xc0000de0e0}, 0xc000314100)
1月 03 12:37:50 prometheus-server fortigate-exporter[4159665]:         /opt/hostedtoolcache/go/1.21.5/x64/src/net/http/server.go:2514 +0x142
1月 03 12:37:50 prometheus-server fortigate-exporter[4159665]: net/http.serverHandler.ServeHTTP({0xc000711620?}, {0x9d8f98?, 0xc0000de0e0?}, 0x6?)
1月 03 12:37:50 prometheus-server fortigate-exporter[4159665]:         /opt/hostedtoolcache/go/1.21.5/x64/src/net/http/server.go:2938 +0x8e
1月 03 12:37:50 prometheus-server fortigate-exporter[4159665]: net/http.(*conn).serve(0xc00045c000, {0x9d9b08, 0xc0001b61b0})
1月 03 12:37:50 prometheus-server fortigate-exporter[4159665]:         /opt/hostedtoolcache/go/1.21.5/x64/src/net/http/server.go:2009 +0x5f4
1月 03 12:37:50 prometheus-server fortigate-exporter[4159665]: created by net/http.(*Server).Serve in goroutine 7
1月 03 12:37:50 prometheus-server fortigate-exporter[4159665]:         /opt/hostedtoolcache/go/1.21.5/x64/src/net/http/server.go:3086 +0x5cb
1月 03 12:37:57 prometheus-server fortigate-exporter[4159665]: 2024/01/03 12:37:57 Probe of "https://<IP_ADDRESS>:10443" succeeded, took 7.583 seconds

The intuitive feeling is that the fortigate-exporter service is normal for a while and abnormal for a while. I'm not sure how to solve this problem. Need your help thanks.

@happinesslijian see #190 (comment)

@bluecmd This bothers me a lot, I don’t know what the problem is 😣Fortigate exporter service sometimes works well and sometimes bad
systemctl status fortigate-exporter.service
● fortigate-exporter.service - fortigate-exporter
     Loaded: loaded (/etc/systemd/system/fortigate-exporter.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2024-01-03 10:29:46 CST; 3h 0min ago
   Main PID: 4159665 (fortigate-expor)
      Tasks: 11 (limit: 19119)
     Memory: 11.9M
     CGroup: /system.slice/fortigate-exporter.service
             └─4159665 /usr/local/bin/fortigate-exporter -insecure --auth-file /data/prometheus/fortigate-key.yaml

1月 03 13:24:52 prometheus-server fortigate-exporter[4159665]: 2024/01/03 13:24:52 Probe of "https://<IP_ADDRESS>:10443" succeeded, took 2.689 seconds
1月 03 13:25:25 prometheus-server fortigate-exporter[4159665]: 2024/01/03 13:25:25 Probe of "https://<IP_ADDRESS>:10443" succeeded, took 5.588 seconds
1月 03 13:25:50 prometheus-server fortigate-exporter[4159665]: 2024/01/03 13:25:50 Probe of "https://<IP_ADDRESS>:10443" succeeded, took 0.633 seconds
1月 03 13:26:22 prometheus-server fortigate-exporter[4159665]: 2024/01/03 13:26:22 Probe of "https://<IP_ADDRESS>:10443" succeeded, took 2.693 seconds
1月 03 13:26:50 prometheus-server fortigate-exporter[4159665]: 2024/01/03 13:26:50 Probe of "https://<IP_ADDRESS>:10443" succeeded, took 0.641 seconds
1月 03 13:27:26 prometheus-server fortigate-exporter[4159665]: 2024/01/03 13:27:26 Probe of "https://<IP_ADDRESS>:10443" succeeded, took 7.109 seconds
1月 03 13:27:55 prometheus-server fortigate-exporter[4159665]: 2024/01/03 13:27:55 Probe of "https://<IP_ADDRESS>:10443" succeeded, took 5.636 seconds
1月 03 13:28:25 prometheus-server fortigate-exporter[4159665]: 2024/01/03 13:28:25 Probe of "https://<IP_ADDRESS>:10443" succeeded, took 5.628 seconds
1月 03 13:28:57 prometheus-server fortigate-exporter[4159665]: 2024/01/03 13:28:57 Probe of "https://<IP_ADDRESS>:10443" succeeded, took 7.624 seconds
1月 03 13:29:25 prometheus-server fortigate-exporter[4159665]: 2024/01/03 13:29:25 Probe of "https://<IP_ADDRESS>:10443" succeeded, took 5.615 seconds

systemctl status fortigate-exporter.service
● fortigate-exporter.service - fortigate-exporter
     Loaded: loaded (/etc/systemd/system/fortigate-exporter.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2024-01-03 10:29:46 CST; 3h 5min ago
   Main PID: 4159665 (fortigate-expor)
      Tasks: 11 (limit: 19119)
     Memory: 9.1M
     CGroup: /system.slice/fortigate-exporter.service
             └─4159665 /usr/local/bin/fortigate-exporter -insecure --auth-file /data/prometheus/fortigate-key.yaml

1月 03 13:35:20 prometheus-server fortigate-exporter[4159665]: net/http.HandlerFunc.ServeHTTP(0x445200?, {0x9d8f98?, 0xc0000de000?}, 0x6a79ba?)
1月 03 13:35:20 prometheus-server fortigate-exporter[4159665]:         /opt/hostedtoolcache/go/1.21.5/x64/src/net/http/server.go:2136 +0x29
1月 03 13:35:20 prometheus-server fortigate-exporter[4159665]: net/http.(*ServeMux).ServeHTTP(0xd32020?, {0x9d8f98, 0xc0000de000}, 0xc0001a1800)
1月 03 13:35:20 prometheus-server fortigate-exporter[4159665]:         /opt/hostedtoolcache/go/1.21.5/x64/src/net/http/server.go:2514 +0x142
1月 03 13:35:20 prometheus-server fortigate-exporter[4159665]: net/http.serverHandler.ServeHTTP({0xc00033ecc0?}, {0x9d8f98?, 0xc0000de000?}, 0x6?)
1月 03 13:35:20 prometheus-server fortigate-exporter[4159665]:         /opt/hostedtoolcache/go/1.21.5/x64/src/net/http/server.go:2938 +0x8e
1月 03 13:35:20 prometheus-server fortigate-exporter[4159665]: net/http.(*conn).serve(0xc00023e3f0, {0x9d9b08, 0xc0001b61b0})
1月 03 13:35:20 prometheus-server fortigate-exporter[4159665]:         /opt/hostedtoolcache/go/1.21.5/x64/src/net/http/server.go:2009 +0x5f4
1月 03 13:35:20 prometheus-server fortigate-exporter[4159665]: created by net/http.(*Server).Serve in goroutine 7
1月 03 13:35:20 prometheus-server fortigate-exporter[4159665]:         /opt/hostedtoolcache/go/1.21.5/x64/src/net/http/server.go:3086 +0x5cb

@happinesslijian since it's not related to this GitHub issue, can you open a new one? It's not nice to spam an unrelated one.

@happinesslijian since it's not related to this GitHub issue, can you open a new one? It's not nice to spam an unrelated one.

@bluecmd https://github.com/bluecmd/fortigate_exporter/issues/266


The map is recognizable as the Student Union Building.

Steps:

[x] #31
[ ] #103

I had been able to complete all five buildings for this and was just needing to get feedback on if we wanted to add a few details.  While I can't seem to get my backup to work correctly I'm hoping that I might be able to get that back. If not I have a long week ahead of me redoing that and trying to get it into testing.

Branch #204 has some of my changes that I had done in the middle of the sprint but I hope to be able to get my final changes back and have that pushed before I merge it to the dev branch.

I had done close to 12 hours if not more in the first week reworking the level.

While the 3D model is done it has not been successfully imported into Unreal as everytime I have tried so far it has crashed either Unreal or my computer. I will be simplifying the 3D model this coming sprint and possibly adding obstacles and invisible barriers so that the map can be tested next week.


chore: deduplicate GritQL snippets

Summary
When matching GritQL snippets against a syntax tree, it tries various contexts in which the syntax could occur. These contexts allow it to parse snippets that would not be valid syntax if they were pasted into a top-level source file. Unfortunately, some of them could still end up parsing to the same syntax tree, in which case we end up matching redundant trees. By deduplicating, we can speed up the snippet matching.
Test Plan
Let's see what Codspeed says :)

Unfortunately, this PR doesn't show any performance improvements in Codspeed. It could very well be that any improvements are specific to particular queries. This would make sense, since not all queries are parseable in multiple source contexts. In any case, it seems deduplicating is a good thing to do, so I'll merge anyway and maybe it gives some improvements in some situations. Oh well :shrug:


How to add a different model

Is it possible to add a different model maybe something that we can change in the code if it's not directly supported? If we are using openrouter which has openai compatible API Is there any way we can use some other models that are available on openrouter

It's possible and is really something I should officially support at some point.  For now you can hack it together by making the following changes.

Set GROQ_BASE_URL to your customer OpenAI compatible server, i.e. export GROQ_BASE_URL=http://<IP_ADDRESS>:6748/v1
Modify server.py to return a list of valid models  for groq.  The models should all start with groq/, i.e. groq/llama3

Let me know if that works for you.  Eventually we could make this more pluggable / a native feature.


Add support in ingress for multiple domains+custom ssl certs and domain -> pod rules

I have multiple subdomains (part of a wildcard tld) as well as multiple TLD coming in to my cluster.
For compliance reasons, i have to use certificates issued by a CA - both wildcard and single domain. I cannot use letsencrypt.
What is the k3s configuration i need for the inbuilt traefik to pick these certificates and then route the domains to the right pods ?

also commentng here. we also want similar help

Just another user here, but I think the default traefik configuration doesn't allow for the setup you need.
Instead you should use the --no-deploy=traefik option and supply your own traefik manifest, where you can configure Traefik as you want (just see the documentation for the traefik helm chart: https://github.com/helm/charts/tree/master/stable/traefik).
If you don't know where to start, take a copy of the currently generated traefik manifest in /var/lib/rancher/k3s/server/manifests before changing the startup script, and adapt to your liking (that's what I did).

@mortenlj yes - which is pretty much k8s territory.
This issue is basically trying to highlight that this is a baseline feature that should be done by the k3s cli in some way. Because this is such a fundamental, yet superhard to setup thing in kubernetes. I dont want to figure out traefik and spend time learning traefik.
I'm requesting the developers to give me a way to auto-configure it using k3s cli. Otherwise we are basically back into k8s complexity.

Closing due to age - please open new issues as problems arise.


Prerequites in complex environment

Hi.
What are communication requirements between Workstation(where running SCCM console)  - SCCM server - Endpoint when using CM pivot ?

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

ID: f0c8158c-1c8e-1567-d96d-222f5b4aec21
Version Independent ID: f6674943-3564-2250-2334-b88c42f3a8a6
Content: CMPivot for real-time data - Configuration Manager
Content Source: sccm/core/servers/manage/cmpivot.md
Product: configuration-manager
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

Thanks @AndresPae for the feedback. That's good additional detail to include. CMPivot uses the client notification channel, which is on port 10123 by default. For reference, you can see that in the Ports article.

This issue is closed because @mestew made changes to this article, which should publish later today.


Feature Request:  Text Input should support an optional Clear function

Select one ...  (check one with "x")
[ ] bug
[x] feature request
[ ] enhancement

Expected behavior
In some cases text inputs are used to insert long strings, and the removal of the long strings may be tedious.  In such case, it's useful to present a "clear" button at the end of the input to immediately remove everything in the input value.  Search and Filter inputs tend to be the most common cases requiring this feature, but others may exist.
Actual behavior
Feature doesn't exist
Environment details

Angular version: 2.0.X

Clarity version: 0.9.X

This was something that was spec'd out in the Search Design on #186

Changing #2718 to UX Ready - please make sure to enable the clear function in the date picker when addressing this.

Ok I didn't have time to setup a sync.

The optional clear function can be added but require that it is placed inside of an clr-input-container to work properly. I'm ok with that, its a new feature and won't work without it.
Look at the DOM structure of input groups in the dev app and the password. That is something we'd have to support (conditionally) when using this functionality. It makes for a more complicated template, which is the main challenge I see in this feature. There should be no need to set explicit widths.
Good question about should the clear button be there always or not. With the input group layout, it could be hidden until the control is dirty, which makes sense to me, and still hold the space. The validation icon is the right padding you highlighted above, which needs to be retained.
Color-wise, let's use the default colors and we'll get UX to confirm.
This can be done without breaking changes, but if you are concerned about that then I would shelve it for something different.

@gnomeontherun
Have we considered what we would do for browsers (like IE, Edge, and some types of form fields in Chrome) that add this functionality all on their own?

My thinking was we'd disable/remove the behavior if we are implementing it ourselves. There are pseudo selectors to target this IIRC.

I would like to be assigned to this issue.

in progress or hold this issue ?

Its currently in backlog.

The feature request here has been captured into our list and we’re going to take it into consideration as we develop Clarity Core capabilities. In an effort to clean up our backlog and focus our attention, I’m going to close this as captured in our feature requests. Please follow our development and releases to see when we release relevant components to make this possible. Future feature requests can be made in our GitHub Discussions.


Use SDK helper function for parsing AppGenesis from bytes

Summary
Use the added function in the e2e genesis setup to read the app genesis from the provided bytes
see relevant comment

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged/assigned

this is actually required for our backwards compatibility tests to work, I'll add this to the v8 milestone

looks like this was implemented here


quiche_conn_peer_cert returns pointer to freed data?

I've done a first take at implementing support for quiche_conn_peer_cert() in curl (from #1120). This is started in https://github.com/curl/curl/pull/8273
The code looks like this:
https://github.com/curl/curl/blob/99b843e49eebcfcd66ff78dae199077621f4b730/lib/vquic/quiche.c#L304-L317
With that PR applied to the latest curl (from git) using the latest quiche from git, valgrind goes nuts. It appears to me as if the certificate pointer we get returned in quiche_conn_peer_cert() is in fact freed?
Maybe I'm reading it wrong...
$ valgrind ./src/curl --http3 https://www.cloudflare.com/ -o /dev/null

==2567409== Invalid read of size 1
==2567409==    at 0x4D84BF0: ASN1_get_object (asn1_lib.c:121)
==2567409==    by 0x4D85807: asn1_check_tlen (tasn_dec.c:909)
==2567409==    by 0x4D863DF: asn1_item_ex_d2i (tasn_dec.c:329)
==2567409==    by 0x4D87380: ASN1_item_ex_d2i (tasn_dec.c:468)
==2567409==    by 0x4D87380: ASN1_item_d2i (tasn_dec.c:149)
==2567409==    by 0x18489C: quiche_has_connected (quiche.c:311)
==2567409==    by 0x184A8B: Curl_quic_is_connected (quiche.c:365)
==2567409==    by 0x18C0BD: Curl_is_connected (connect.c:887)
==2567409==    by 0x156964: multi_runsingle (multi.c:2013)
==2567409==    by 0x157FA4: curl_multi_perform (multi.c:2638)
==2567409==    by 0x142B05: easy_transfer (easy.c:606)
==2567409==    by 0x142D31: easy_perform (easy.c:696)
==2567409==    by 0x142D7B: curl_easy_perform (easy.c:715)
==2567409==  Address 0x5ae94a0 is 0 bytes inside a block of size 1,324 free'd
==2567409==    at 0x484217B: free (vg_replace_malloc.c:872)
==2567409==    by 0x489F345: quiche_conn_peer_cert (alloc.rs:104)
==2567409==    by 0x18487B: quiche_has_connected (quiche.c:309)
==2567409==    by 0x184A8B: Curl_quic_is_connected (quiche.c:365)
==2567409==    by 0x18C0BD: Curl_is_connected (connect.c:887)
==2567409==    by 0x156964: multi_runsingle (multi.c:2013)
==2567409==    by 0x157FA4: curl_multi_perform (multi.c:2638)
==2567409==    by 0x142B05: easy_transfer (easy.c:606)
==2567409==    by 0x142D31: easy_perform (easy.c:696)
==2567409==    by 0x142D7B: curl_easy_perform (easy.c:715)
==2567409==    by 0x13842D: serial_transfers (tool_operate.c:2386)
==2567409==    by 0x1388EA: run_all_transfers (tool_operate.c:2557)
==2567409==  Block was alloc'd at
==2567409==    at 0x483F7B5: malloc (vg_replace_malloc.c:381)
==2567409==    by 0x48CAF76: quiche::tls::Handshake::peer_cert (alloc.rs:86)
==2567409==    by 0x489F31C: quiche_conn_peer_cert (lib.rs:4505)
==2567409==    by 0x18487B: quiche_has_connected (quiche.c:309)
==2567409==    by 0x184A8B: Curl_quic_is_connected (quiche.c:365)
==2567409==    by 0x18C0BD: Curl_is_connected (connect.c:887)
==2567409==    by 0x156964: multi_runsingle (multi.c:2013)
==2567409==    by 0x157FA4: curl_multi_perform (multi.c:2638)
==2567409==    by 0x142B05: easy_transfer (easy.c:606)
==2567409==    by 0x142D31: easy_perform (easy.c:696)
==2567409==    by 0x142D7B: curl_easy_perform (easy.c:715)
==2567409==    by 0x13842D: serial_transfers (tool_operate.c:2386)
==2567409==

Looking at the code again, yes, this seems to be a bug in the quiche_conn_peer_cert() wrapper as it returns a pointer to a Rust vector which gets freed when the function returns. quiche_conn_session() has the same problem AFAICT.

@LPardue we need to figure out a different way to implemet these wrappers, as we can't just return a Rust Vec pointer to C like this.


Feat / Change Headline in Templates

OP-1982 - Related organisations: change titel (h3) in overview of district, gemeente and OCMW

(hey, small note before i review, we only put the task number but not the link for confidentiality reasons)


[pigeon] java: add checks for null nested classes.

@gaaclarke
I have a nested class that I'm passing down to the platform.

class TrackProxy {
    MediaFormatProxy mediaFormat;
}

During development I forgot to initialise the nested 'mediaFormat' class.
The result was an NPE in the java code caused by the following code:
 static TrackProxy fromMap(HashMap map) {
      TrackProxy fromMapResult = new TrackProxy();
      Object mediaFormat = map.get("mediaFormat");
      fromMapResult.mediaFormat = MediaFormatProxy.fromMap((HashMap)mediaFormat);

The call to map.get("mediaFormat") correctly returned a null causing the fromMap method to throw an NPE when it tried to deserialise the mediaFormat.
The error that is returned provides no details on what went wrong:
2020-10-08 11:45:59.036 7191-7224/com.bsutton.sounds.sounds_example E/flutter: [ERROR:flutter/lib/ui/ui_dart_state.cc(177)] Unhandled Exception: PlatformException(NullPointerException, java.lang.NullPointerException: Attempt to invoke virtual method 'java.lang.Object java.util.HashMap.get(java.lang.Object)' on a null object reference, null, null)
    #0      SoundsToPlatformApi.startPlayer (package:sounds_platform_interface/sounds_platform_interface.dart:868:7)
    <asynchronous suspension>
    #1      SoundPlayer.play (package:sounds/src/sound_player.dart:310:19)
    <asynchronous suspension>
    #2      SoundPlayerUIState._start (package:sounds/src/ui/sound_player_ui.dart:447:21)
    <asynchronous suspension>

To resolve the issue I had to trace through the pigeon java code.
This process feels onerous.
I think the generated code should include checks that nested objects have been initialised before we try to deserialise the object.
The check then should return a helpful error.

@gaaclarke we can close this one now right?

@xster You talking about after the null safety PR?  That fixed Dart, I haven't looked into this for Java.  I have unit tests for java generated code I'd like to land to assert things like this.

ah right

If there are concerns about performance we could place the null checks behind a 'debug' build option for pigeon. However I really don't think it will be necessary and not for v 1.0.

Hi guys, that's still happening on 0.2.2 for Android/Java generated code. Is there any branch where it is sorted?

Still happens on current version. Any workarounds apart from manually editing the code?

I would have expected this to be resolved in 0.3.0 when we moved to the custom codec.  I haven't gotten around to verifying it yet though.  Care to share what code change you had to make in 0.3.0?

I just looked into this a bit further.  It still happens in 0.3.0, but it is a bit different.  To be clear, we don't to remove the error, that is correct.  We want to make the error more clear.

I added the following test:
  @Test
  public void encodeWithNullField() {
    Pigeon.NestedRequest request = new Pigeon.NestedRequest();
    request.setContext("hello");
    MessageCodec<Object> codec = Pigeon.NestedApi.getCodec();
    ByteBuffer message = codec.encodeMessage(request);
  }

Pigeon:
enum LoadingState {
  loading,
  complete,
}

class SetRequest {
  int? value;
  LoadingState? state;
}

class NestedRequest {
  String? context;
  SetRequest? request;
}

@HostApi()
abstract class Api {
  void setValue(SetRequest request);
}

@HostApi()
abstract class NestedApi {
  void setValueWithContext(NestedRequest request);
}

The exception was:
java.lang.NullPointerException
	at com.example.android_unit_tests.Pigeon$NestedRequest.toMap(Pigeon.java:99)
	at com.example.android_unit_tests.Pigeon$NestedApiCodec.writeValue(Pigeon.java:199)
	at io.flutter.plugin.common.StandardMessageCodec.encodeMessage(StandardMessageCodec.java:73)
	at com.example.android_unit_tests.PigeonTest.callWithNullField(PigeonTest.java:112)
        ...

Pigeon.java:99 is toMapResult.put("request", request.toMap());
I don't think it is that difficult to debug currently, right?

Hi @gaaclarke,
Could you explain the choice of keeping the NPE?
By the Flutter code, on your sample, those are not mandatory fields, SetRequest is nullable in NestedRequest. And it would make sense for me to not have all parameters in that object. Adding a validation for null and ignoring the object if not sent is not more compatible with the generated code on Flutter?
Thank you in advance.

Okay, I was wrong.  I was thinking we wanted NPE because we wanted those to be nonnull fields but are working around the limitations of Java's null safety.
What I'm realizing is that the code looks like this in pigeon:
class Foo {}
class Bar {
  Foo? foo;
}
@HostApi()
abstract class Api {
  void x(Bar bar);
}

That means that the foo field should be allowed to be null.  That's how it works in Dart and how it should work in Java.  I was mistaken.  I'll fix it.  Thanks for pushing back.

I've posted a fix for it here: https://github.com/flutter/packages/pull/430  But just know that I'm in the midst of a massive overhaul of pigeon for a 1.0 release and this PR is in the middle of it.  So it's probably going to delay the time until it is posted to pub.


docs: readability improvements

Signed-off-by: Ryan Russell<EMAIL_ADDRESS>Description
Small readability fixes in .md.
Author's Checklist:

[x] I have updated the documentation as needed.

Reviewer's Checklist:

[ ] I kept my comments to the author positive, specific, and productive.
[ ] I tested the code and didn't find any new problems.
[ ] I think the motivation is good for the project.
[ ] I think the code works to satisfies the motivation.

Beautiful. Thank you.


Add Makefile with needed targets

See #1
@gileno I included the Makefile as a suggestion. Feel free to improve it whenever you want.

@gileno, I tried to publish the package to PyPI using the proposed Makefile but encounter the following error during pip install -r requirements.txt command:
ERROR: Could not find a version that satisfies the requirement pkg_resources==0.0.0 (from versions: none)
ERROR: No matching distribution found for pkg_resources==0.0.0

As pointed out here pkg_resources and other dependencies packages are installed with setuptools. It wouldn't be better to specify only the setuptools library on the requirements.txt file instead of all its dependencies packages? This way it'll prevent these kinds of problems. What do you think?

I believe it is the best option, as well as ckanext-datapackager as per link:
https://github.com/frictionlessdata/ckanext-datapackager/blob/main/requirements.txt
I will the update in the current branch (1/publish-package-on-pypi), ok?

@gileno sure! You can use the same branch to review the requirements.txt file.


Failing because builder failed to delete resources

Having build fail with
Submitting the template
Submitted template:
 Succeeded
Starting run template...
Error: During the image build a failure has occurred. Please review the build log to identify which build/customization step failed. For more troubleshooting steps go to https://aka.ms/azvmimagebuilderts. Image build log location: https://xjsg7ig6s0p71zg9ntss9c8j.blob.core.windows.net/packerlogs/4249f343-cc1e-4b00-a1[96](https://github.com/org/repo/runs/5616388078?check_suite_focus=true#step:11:96)-015b25120d21/customization.log. OperationId: a2cbf965-1cb1-43de-9663-0f2767d27acd. Use this operationId to search packer logs.
$(imagebuilder-run-status) =  failed
Error: Error: Post template call failed for template imagebuilderTemplate_1647766604241 with error: ***"statusCode":200,"message":"During the image build a failure has occurred. Please review the build log to identify which build/customization step failed. For more troubleshooting steps go to https://aka.ms/azvmimagebuilderts. Image build log location: https://xjsg7ig6s0p71zg9ntss9c8j.blob.core.windows.net/packerlogs/4249f343-cc1e-4b00-a196-015b25120d21/customization.log. OperationId: a2cbf965-1cb1-43de-9663-0f2767d27acd. Use this operationId to search packer logs.","code":"PackerBuildFailed"***
Error: Action run failed.

Looking at the build logs
Error: network.VirtualNetworksClient#Delete: Failure sending request: StatusCode=0 -- Original Error: Code="InUseSubnetCannotBeDeleted" Message="Subnet pkrsnpo7ai8nvl9 is in use by /subscriptions/subscription-id/resourceGroups/IT_my-rg_imagebuilderTemplate_1647765614_6cd361c7-8c30-4597-be22-12b2634897d6/providers/Microsoft.Network/networkInterfaces/pkrnipo7ai8nvl9/ipConfigurations/ipconfig and cannot be deleted. In order to delete the subnet, delete all the resources within the subnet. See aka.ms/deletesubnet." Details=[]

ERR ==> azure-arm: The resource group was not created by Packer, not deleting ...
ERR ==> Builds finished but no artifacts were created.

The build leaves the resource group and the storage account in it every time. Seems like its unable to delete these resources for a reason I can figure out. I can post the whole logs here.

Hey @zemuldo
I would say the action's readme and end-to-end tutorial doc  covers the scenarios and action usage pretty well. Please go through them to understand why it's failing. Also regarding the extra resource group and  storage account thing you may look at this issue https://github.com/Azure/build-vm-image/issues/13. Feel free to share your workflow and logs if you still face the problem after trying this.

The image actually gets created and are usable on VMs. Its the builder failing to delete the resources

Closing this. Ended up executing packer myself with setup packer.


Warn / log if DNS TTL is long/infinite

When debugging connection issues, it would be useful to know the DNS caching policy. Perhaps we could log the value of java.security.Security.getProperty("networkaddress.cache.ttl"); when the library is initialised?

On thing to consider is that calling Security.getProperty is itself restricted by a SecurityPermission. [1]
So in the case where a SecurityManager is active (the most likely scenario for an infinitely cached DNS entry) we may not have access to read the value anyway and would need to handle the security exception.


Customer Meeting on June 3, 2022

User story

As a PO
I want / need to conduct the meeting with our customer
So that we can demo our current progress and ask specific questions

Agenda for the meeting

Demo of the current status of the app by one SD (who?)
POs discuss their internal prioritization of features with customer´s prioritization
If time left: open discussion with customer regarding technical questions

Who will attend?
Please check if you attend the meeting.

[ ] @cynthiachen28
[x] @Meisterlu
[x] @codingwithelijah
[ ] @domi1504
[x] @Chippelius
[ ] @Interperle
[ ] @Wandinad
[ ] @jannikbmc
[ ] @NicoStellwag

As always i cannot attend it, because i am working that day.

@SDs: If you have any questions, that could be also interesting to clarify from a business perspective, just post them here. Then I will add them in the discussion with the customer. :)

Things to discuss:
#105 --> see comment from @Chippelius


Geographic Queries x/y lon/lat coordinate confusion

The geographic query documentation is unclear about the relation of latitude/longitude to horizontal/vertical and x/y coordinates for querying.
Affected Version
0.18.0 (all versions that support spatial queries?)
Description
In Geography: longitude is the horizontal dimension and latitude is the vertical dimension
In Geometry: x is the horizontal dimension and y is the vertical dimension
For Polygons: abscissa is the horizontal dimension values and ordinate is the vertical dimension values
The Geographic Query documentation page has an example that shows indexing dimensions being given as: "dims": ["lat", "long"].
The spatial filter documentation for rectangular and radius bounds specifies queries should provide coordinates as [x, y, z, …]
This is confusing, and if followed to the letter, won't work as expected. Either I'm misunderstanding something, or else the person who wrote the documentation didn't understand the difference between geographic coordinate order vs geometric coordinate order.
The same issues exists with polygon bounds, as providing the index dimensions as in the example will require the abscissa to contain latitude (vertical) values.
The correct fix would be to specify your index dimensions as ["long","lat"], but that could be very confusion for anyone who has already been using spatial queries. An alternative is to enshrine the ["lat", "long"] ordering by specifying that spatial bounds should provide coordinates in ["lat", "long"]`  order.

Druid's Geographic Queries is not a real Geographic Queries. So the documentation don’t care about the relation of latitude/longitude to horizontal/vertical and x/y coordinates for querying.

But it does care, as it uses the terms lat and long in the example; but it uses them as x and y, when they are actually y and x. As I said, this means that anyone who follows the example, and then queries using, for instance, correct polygon coordinates, will not get correct results.
Perhaps the most simple fix would be to remove the usage of the terms lat and long from the page entirely.

I second the suggestion from @lokkju. For those trying to use the spatial features of Druid with the current documentation, they will likely fail to see that the order of the dimensions used in the spatial ingestion spec must be equal to the order of the dimestions used in the filtering spec.
Since, as @SWH12 correctly explained, the geographic queries are not actually geographic but instead geometric queries, removing all mentions of latitude and longitude from the documentation and replacing with x & y will be beneficial for the users.

I second the suggestion from @lokkju. For those trying to use the spatial features of Druid with the current documentation, they will likely fail to see that the order of the dimensions used in the spatial ingestion spec must be equal to the order of the dimestions used in the filtering spec.
Since, as @SWH12 correctly explained, the geographic queries are not actually geographic but instead geometric queries, removing all mentions of latitude and longitude from the documentation and replacing with x & y will be beneficial for the users.


npm not configured

CreateJS projects have been added to npm's registery, but they don't download any code because they have not been configured correctly
They are therefore incompatible with any projects using npm instead of bower

There is currently no NPM support, we just reserved the package. It is on our short list for the next version, as it requires some reconfiguring to properly support. See #713


If I use RGB

I wonder how did you train your robot when you use RGB image as input?

Hi, unfortunately, this feature is not implemented in this repo.


docs: Updates to Quarkus quick start for Service Registry to describe manual connection use case

Notes for reviewers

An HTML preview is available for review here

LGTM, thanks John!

Thanks, for reviewing, @smccarthy-ie. One additional commit to come, to pull the RHOSAK quick starts back in line with the approach followed here.


Check if prometheus_scrape provider is compatible with machine charms.

https://github.com/canonical/prometheus-k8s-operator/blob/0a22b74bfde434f9a2b19635abc2fb507d664ce2/lib/charms/prometheus_k8s/v0/prometheus_scrape.py#L1543-L1561
This block in MetricsEndpointProvider may not be compatible with machine charms. It depends on whether _charm.meta.containers raises an exception or not. If so, some code change will be needed.

I'm currently testing this situation trying to have a cross-model relation with a node_exporter. When deploying a machine charm, the charm gets into an active|idle status. Will update with more info if I find something relevant. (The charm I'm using)

This will, never, ever fail. In the worst case it's an empty dict with length 0, and we fall though.


Datepicker min and max values are not correctly updated.

Hello,
I've noticed a problem with the min and max values on the displayed date picker control.  From what I can see, if the attributes max or min are updated via javascript then these changes are not propagated to the date picker.  Please note, however that the initial values are correctly taken into account.
I've created a simple example to illustrate the problem :

https://jsfiddle.net/FeetInAncientTime/ww5p7tfL/4/

The basic idea of the pair of date inputs in the example is that it should not be possible to enter a start date that is later than the end date and vice versa.  The date picker should also be updated to reflect this.
After running the script, if you click on the start date input then you will see that the max limit is correctly set to the 30th June 2017.  Do not change the start date and click on the end date input.  You should see that the min limit is set to 1st June 2017.  The date picker correctly indicates that it is not possible to select the dates before or after the limits.
Re-run the script and click on the start date input.  Change the start date to 8th June 2017.  Click on the end date input and you will see that the min date has been set to the 8th June 2017.  However, if you click on the start date input you should see that the max date has not been altered.
I've deliberately tried to keep the code simple, but I apologise in advance if the problem is not related to the polyfill.  For information, I fire a change event in order to update the date picker (I noticed that this was necessary for a related problem that I had with the value attribute.)
Thanks for writing this polyfill !

@FeetInAncientTime sorry for such a long reply. I believe the issue was fixed in the latest version, try updated demo https://jsfiddle.net/g6xL2pob/4/.


Datetime module

~#1301 is required for tests~
#1302 is a blocking issue for other tests

@youknowone do you want to merge this work, or wait until #1302 is solved?

datetime.py itself is (partially) working without editing. So merging now will be fine. Bugs will be naturally fixed by catching up other issues.


Run Repulsion (Lettvin Edge10Mappings) reevaluation

Run range test on Edge10Mappings.
Insert results and new plots.
See:
https://github.com/LightStage-Aber/LightStage-Repo/blob/master/exp/Lettvin_Repulsion/run_range_test_lettvin_diffuse.sh

Started running on OVH test server 2017/06/06: 19.00 GMT+07.

Exp Script Executing: https://github.com/LightStage-Aber/LightStage-Repo/blob/4d769f527c2da4c08dae631c3562f870827833f3/exp/Lettvin_Repulsion/run_range_test_lettvin_diffuse.sh
Expect 50543*3=32250 configurations. Estimate of 3.73 days, based on 30 sec estimate for an average evaluation set of 3 evaluators (Raw, VertexMapped, EdgeMapped).
Note: Evaluations that do not hit all target surfaces (for example. those with 1 LED) will not be reported in CSV results file.

Run completed on OVH test server 2017/06/08 16.01 GMT+07.
/Results_RangeTest_2017-06-06_14-00/
    10822   2056180  43712387 lambertian_led_sets_Edge10MappedPositionEvaluator.csv
    10840   1972880  43273455 lambertian_led_sets_RawPositionEvaluator.csv
    10750   1988750  43144224 lambertian_led_sets_VertexMappedPositionEvaluator.csv
    32412   6017810 130130066 total
``
- 162 missing runs. Expected reason due to "Not all surfaces hit." Can test by verifying which configurations have less than 50 iteration runs. VertexMapped have the lowest qty of runs, also coarsest positioning, so this point supports the conjecture.
- $(Seq 3 2 90) sequence used in this test run.
- See https://github.com/LightStage-Aber/LightStage-Repo/blob/4d769f527c2da4c08dae631c3562f870827833f3/exp/Lettvin_Repulsion/run_range_test_lettvin_diffuse.sh

Start running on OVH test server 2017/06/11 14.00 GMT+07

Sequence: $(seq 4 2 90) - See https://github.com/LightStage-Aber/LightStage-Repo/commit/ce3e5807b02b7bbfe28aef90136970e364a1e49f
Expect 2 days. 50 x 43 x 5 x 3 = 32250 configurations.

Run completed on OVH test server 2017/06/13 15:35 GMT+07.
/Results_RangeTest_2017-06-11_09-00$ wc *.csv
    11000   2090000  44448290 lambertian_led_sets_Edge10MappedPositionEvaluator.csv
    11000   2002000  43947624 lambertian_led_sets_RawPositionEvaluator.csv
    11000   2035000  44161046 lambertian_led_sets_VertexMappedPositionEvaluator.csv
    33000   6127000 132556960 total

Zero missing configurations.


[Transporter Error Output]: An error occurred while uploading the package: 639234809.itmsp.

[16:19:29]: Making sure the latest version on App Store Connect matches '7.8.0' from the ipa file...
[16:19:34]: '7.8.0' is the latest version on App Store Connect
[16:19:36]: Uploading binary to App Store Connect
[16:19:41]: Going to upload updated app to App Store Connect
[16:19:41]: This might take a few minutes. Please don't interrupt the script.
[16:36:12]: [Transporter Error Output]: An error occurred while uploading the package: 639234809.itmsp.
[16:36:12]: [Transporter Error Output]: An exception has occurred: The transport has been detected as having stalled and has been aborted.  Please try again.
16:36:16: Transporter transfer failed.
16:36:16:
16:36:16: An error occurred while uploading the package: 639234809.itmsp.
An exception has occurred: The transport has been detected as having stalled and has been aborted.  Please try again.
16:36:16: [iTMSTransporter] [2019-05-16 16:36:16 CST]  DBG-X: Apple's web service operation return value:
16:36:16: [iTMSTransporter] [2019-05-16 16:36:16 CST]  DBG-X:   parameter EnableJWTForAllCalls = false
16:36:16: [iTMSTransporter] [2019-05-16 16:36:16 CST]  DBG-X:   parameter SessionExpiration = 2019-05-20T08:36:12.955Z
16:36:16: [iTMSTransporter] [2019-05-16 16:36:16 CST]  DBG-X:   parameter Success = true
16:36:16: [iTMSTransporter] [2019-05-16 16:36:16 CST]  DBG-X:   parameter StreamingSettings = {LogStreamingEnabled=true, MultipartUploadsEnabled=true, AssetDescriptionStreamingEnabled=false}
16:36:16: [iTMSTransporter] Package Summary:
16:36:16: [iTMSTransporter] 1 package(s) were not uploaded because they had problems:
16:36:16: [iTMSTransporter] 	/tmp/639234809.itmsp - Error Messages:
16:36:16: [iTMSTransporter] 		An error occurred while uploading the package: 639234809.itmsp.
16:36:16: [iTMSTransporter] 		An exception has occurred: The transport has been detected as having stalled and has been aborted.  Please try again.
16:36:16: [iTMSTransporter] [2019-05-16 16:36:16 CST]  DBG-X: Returning 1
16:36:16: iTunes Transporter output above ^
16:36:16: An error occurred while uploading the package: 639234809.itmsp.
An exception has occurred: The transport has been detected as having stalled and has been aborted.  Please try again.
Return status of iTunes Transporter was 1: An error occurred while uploading the package: 639234809.itmsp.
\nAn exception has occurred: The transport has been detected as having stalled and has been aborted.  Please try again.
The call to the iTMSTransporter completed with a non-zero exit status: 1. This indicates a failure.

Could you please fill the issue template https://github.com/fastlane/fastlane/issues/new?template=BUG_REPORT.md? This asks for all the information we need to maybe be able to help you.

same

bundle update fastlane work for me


Cannot create SSH Tunnel

# ssh -L 3001:localhost:3001 myserver -N
setsockopt IPV6_V6ONLY: Invalid argument
bind: Invalid argument
channel_setup_fwd_listener: cannot listen to port: 3001
Could not request local forwarding.

#68
#128

Yes, I can confirm that the IPV6_V6ONLY socket option is currently not supported. We have opened a bug on our end to track this. Thanks for the feedback.

Is there a workaround to use ipv4?

does this work?
# ssh -4 -L 3001:localhost:3001 myserver -N

yes, thank you!

With the help of the Windows networking team, we were able to fully implement the IPV6_V6ONLY flag. That should resolve the issue here. The fix is still in our dev branch, but should soon hit the release branch.

Just FYI that the IPV6_V6ONLY issue is fixed in 14936 (see release notes)

Closing this out since this should be now resolved in Insider builds 14942+. If it is broken, please let us know. And, thanks for all the feedback.


Super-TeX-hero duck

The Super-TeX-Hero duck is happily swimming in "The Duck Pond": https://tex.stackexchange.com/a/387050/36296


Cannot rebuild

Hi,
I can rebuild script using command "npm run build". I was follow instructions step by step.
This is output from terminal:
><EMAIL_ADDRESS>build E:\js\vis-graph3d
> npm run js:graph3d

><EMAIL_ADDRESS>js:graph3d E:\js\vis-graph3d
> rollup --config rollup.build.js && rollup --config rollup.config.js

[!] Error: Cannot find module 'vis-dev-utils'
Require stack:
- E:\js\vis-graph3d\rollup.build.js
- C:\Users\Acer\AppData\Roaming\npm\node_modules\rollup\dist\shared\loadConfigFile.js
- C:\Users\Acer\AppData\Roaming\npm\node_modules\rollup\dist\bin\rollup
Error: Cannot find module 'vis-dev-utils'
Require stack:
- E:\js\vis-graph3d\rollup.build.js
- C:\Users\Acer\AppData\Roaming\npm\node_modules\rollup\dist\shared\loadConfigFile.js
- C:\Users\Acer\AppData\Roaming\npm\node_modules\rollup\dist\bin\rollup
    at Function.Module._resolveFilename (internal/modules/cjs/loader.js:957:15)
    at Function.Module._load (internal/modules/cjs/loader.js:840:27)
    at Module.require (internal/modules/cjs/loader.js:1019:19)
    at require (internal/modules/cjs/helpers.js:77:18)
    at Object.<anonymous> (E:\js\vis-graph3d\rollup.build.js:8:19)
    at Module._compile (internal/modules/cjs/loader.js:1133:30)
    at Object.require.extensions.<computed> [as .js] (C:\Users\Acer\AppData\Roaming\npm\node_modules\rollup\dist\shared\loadConfigFile.js:516:20)
    at Module.load (internal/modules/cjs/loader.js:977:32)
    at Function.Module._load (internal/modules/cjs/loader.js:877:14)
    at Module.require (internal/modules/cjs/loader.js:1019:19)

npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>js:graph3d: `rollup --config rollup.build.js && rollup --config rollup.config.js`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>js:graph3d script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      C:\Users\Acer\AppData\Roaming\npm-cache\_logs\2020-05-02T13_06_22_336Z-debug.log
npm ERR! code ELIFECYCLE
npm ERR! errno 1
npm ERR<EMAIL_ADDRESS>build: `npm run js:graph3d`
npm ERR! Exit status 1
npm ERR!
npm ERR! Failed at the<EMAIL_ADDRESS>build script.
npm ERR! This is probably not a problem with npm. There is likely additional logging output above.

npm ERR!      C:\Users\Acer\AppData\Roaming\npm-cache\_logs\2020-05-02T13_06_22_527Z-debug.log

My environtments:

OS: Windows 10
Browser: Chrome
Version: Latest

Could you provide some more info? I tried building on Windows 10 and it went fine (except for corrupted color output). Node version? Npm version?
It seems to me that there's something fishy about the imports. AFAIK everything should be contained within the local node_modules in the project but your log talks about C:\Users\Acer\AppData\Roaming\npm\node_modules. Do you have all dependencies installed properly (npm ci)?

Ok thank you for your information. After updated node and npm, it works!

Hello,

Hello,
After build I found errors when run examples.
Uncaught TypeError: no is not a function
    at fails.js:5
    at vis-graph3d.min.js:26
    at vis-graph3d.min.js:26
Uncaught TypeError: vis.DataSet is not a constructor
    at getDataCsv (playground.js:315)
    at drawCsv (playground.js:461)
    at loadCsvExample (playground.js:59)
    at load (playground.js:8)
    at onload (index.html:22)
Uncaught TypeError: vis.DataSet is not a constructor
    at getDataCsv (playground.js:315)
    at drawCsv (playground.js:461)
    at draw (playground.js:455)
    at HTMLInputElement.onclick (index.html:66)

I just rebuid not modified any code.

I encountered this too. It happens only on Windows. So build on Linux/Mac? I'm sorry, this is far from ideal solution but I don't know why it happens or how to fix it. Sadly I don't have the time to properly debug it right now (and probably won't have for at least a few weeks).
 That should narrow down the potential causes and make it easier to fix.


Send messages to the app without injecting Javascript

Bug description:
I need to add Apple Pay to the WebView but reading from the documentation, it's not possible to do so without sacrificing the injection methods. Since I'm relying on it to send notification tokens down to the website (as well as some other variables), I'd really need a way to do so.
In the docs, it says:
If you are required to send message to App , webpage has to explicitly call webkit message handler and receive it on onMessage handler on react native side
But from what I understand this way can only communicate from the webpage to the webview and not viceversa.
Any solution to this?
Environment:

OS: iOS
OS version: 15.0
react-native version: 0.64.2
react-native-webview version: 11.14.2

RN -> WebView: webViewRef.postMessage('Your message') and
window.addEventListener('message', (event) => event.data) to receive messages inside webview
WebView -> RN: window.ReactNativeWebView.postMessage('your message) in your web inside web view and prop onMessage={(event} => event.nativeEvent.data to handle messages from web

hello @alitsvin, i'm using enableApplePay prop and i want to catch an event from webpage when a deposit is made with succes, as i understood, i can't insert JS in page, i added on webpage 	window.webkit.messageHandlers.ReactNativeWebView.postMessage('Hello') but i don't get any event on onMessage props. do you know how i can fix it?
thanks!

RN -> WebView: webViewRef.postMessage('Your message') and window.addEventListener('message', (event) => event.data) to receive messages inside webview
WebView -> RN: window.ReactNativeWebView.postMessage('your message) in your web inside web view and prop onMessage={(event} => event.nativeEvent.data to handle messages from web

why me invoke webViewRef.postMessage('Your message'), window.addEventListener('message', (event) => event.data) dosn't recive anything.


Cannot save reminder preferences

I can't save my preferences of reminder – especially start time, end time and days. Checkbox for activating reminder and time input works.
Everything else is reset when the dialog is saved.

Windows 10.0.10240 PRO, 64-bit
Toggl Desktop version is 7.2.281

Thanks for reporting the problem!
It looks like Toggl.SetSettings() has not been updated for the additional settings. A clear oversight on our part.

you're welcome. :)

Fixed with 2007c9997af315c8009b6c2001d3cfd80e176fa2.


Support multiple pools

Continuation of #725.
Fixes #569.

Excellent. I have added just two minor comments!

@josevalim force pushed.

:heart: :green_heart: :blue_heart: :yellow_heart: :purple_heart:


SMA Negeri Modal Bangsa

https://www.sman-modalbangsa.sch.id/
SMA Negeri Modal Bangsa

@iqbalhafidh First stage of verification passed, official domain for SMA Negeri Modal Bangsa is sman-modalbangsa.sch.id as far as I verified. This is just an informational note. Pull request is still in the review. I appreciate your patience while waiting for the final decision.

@iqbalhafidh Thank you for your patience while waiting for a review and processing your request. Pull request merged.
Please start requesting the licenses in about an hour, to let the changes to propagate through our system.


Removed +1 from date.

This fixes the bug described here: https://github.com/precisiontox/ptox-metadata-manager/issues/167
However, it's not clear why that +1 was there in the first place.
Currently, I don't know how to run the tests locally (is there any documentation for this?) so I'm not sure if anything else is affected.

Thanks. I'll merge this, but please do let me know if you have any info. on local tests.


Can pick up item frame's items in deny regions

I'm not sure what this is supposed to mean?

You can edit the item frame content, i ll make a video

Fixed in a70efa4873a15d91cd8a40f4b2d1acf66d30f278

Isn't fixed

@TiTi-418 How so?

Im uploading a video.

http://youtu.be/6rt76Srs8cc (uploading)


Draw problem after a few value updates

I recently updated from v1 to v2.1.7.
I have some gaugaes on a page, updated from PLC values.
I noticed that after a few updates, without me moving the browser window, the gauge is drawn on another part of the screen (the left-top-quarter of the original position) - see screenshot.
How can I avoid it?

(using FireFox 117.0 (64-bit))

i have the same problem, but only with firefox (now release 118.0.2)
I have solved moving the creation of the gauge in a function with a value parameter for start the needle in the last position and every 5 or 10 second i destroy the gauge and recreate it, preserving the value for mantaining the last value

example:
function create_gauge(valuestart){
var GAUGE = new RadialGauge({
renderTo: 'gauge1',
width: 180,
height: 180,
units: '°C',
title: 'Temp',
value: valuestart,
minValue: -10,
maxValue: 60,
ticksAngle: 225,
startAngle: 67.5,
majorTicks: [
'-10','0','10','20','30','40','50','60'
],
minorTicks: 5,
strokeTicks: false,
//barStrokeWidth: 1,
//barWidth:5,
highlights: [
{ from: -10, to: 10, color: 'rgba(0,0,255,.7)' },
{ from: 10, to: 20, color: 'rgba(0,226,255,.8)' },
{ from: 20, to: 34, color: 'rgba(0,255,0,.7)' },
{ from: 34, to: 44, color: 'rgba(255,245,0,.7)' },
{ from: 44, to: 50, color: 'rgba(255,120,0,.8)' },
{ from: 50, to: 60, color: 'rgba(255,0,0,.6)' }
],
colorPlate: '#fff',
colorMajorTicks: '#f5f5f5',
colorMinorTicks: '#ddd',
colorTitle: '#000',
colorUnits: '#000',
colorNumbers: '#000',
colorNeedle: 'rgba(240, 128, 128, 1)',
colorNeedleEnd: 'rgba(255, 160, 122, .9)',
colorBorderOuter:'#fff',
colorBorderOuterEnd:'#fff',
colorBorderMiddle:'#fff',
colorBorderMiddleEnd:'#fff',
colorBorderInner:'#fff',
colorBorderInnerEnd:'#fff',
colorBorderShadow: '#fff',
valueDec:1,
valueInt:1,
fontNumbers: "Verdana",
fontValueStyle: 'italic',
fontNumbersSize: 22,
fontNumbersStyle: 'italic',
fontNumbersWeight: 'bold',
fontTitleSize: 40,
fontUnitsSize: 30,
fontValueSize: 50,
colorValueText: "#000",
colorValueBoxRect: "#fff",
colorValueBoxRectEnd: "#fff",
colorValueBoxBackground: "#fff",
colorValueBoxShadow: false,
colorValueTextShadow: false,
//fontValueSize:30,
valueBox: true,
animationRule: 'linear',
animationDuration: 500
}).draw();
return GAUGE;
}
then add a onload call in body for first draw:
onload="create_gauge(0);"
and in the refresh animation some changes:
// animage all gauges on a page
window.addEventListener('load', function() {

	setInterval(function() {
		document.gauges.forEach(function(gauge) {
				var value = gauge.value;
				var new_value = Math.random() *
				(gauge.options.maxValue - gauge.options.minValue) + gauge.options.minValue;
				gauge.destroy();
				var GAUGE_new = create_gauge(value);
				GAUGE_new.value = new_value;
			});

	}, 1000);

});

this for me works well
i have also added a counter for refresh the draw only every 10 second

Different issue but similar workaround: https://github.com/Mikhus/canvas-gauges/issues/248#issuecomment-1943632686
You can use the "render" events to call redraw after a certain limit.


Windows Terminal session restore is not remembering the last directory that was set in each tab

Windows Terminal version
1.15.2875.0
Windows build number
10.0.22621.0
Other Software
I did have Oh-My-Posh module loading in via PowerShell profile, but I have since commented out that module from loading and running to eliminate it from this issue.
Steps to reproduce
Pre-Requisites
In your  Windows Terminal Settings page set the following:

Settings => Startup => When Terminal Starts set value to Open windows from previous session.
The PowerShell profile you are using has a startingDirectory set e.g. "startingDirectory": "%USERPROFILE%"

Steps

Load 2 PowerShell tabs in Windows Terminal
Rename the tabs Tab 1 and Tab 2
In Tab 2 change the directory so that it is different to the directory in Tab 1.
Close Windows Terminal
Re-Open Windows Terminal

Expected Behavior
When Re-Opening Windows Terminal Tab 1 and Tab 2 are restored with their tab names (Tab 1 and Tab 2) plus the initial directory in each tab is the same as it was when the previous Windows Terminal session was closed.
Actual Behavior
When Re-Opening Windows Terminal Tab 1 and Tab 2 are restored with their tab names (Tab 1 and Tab 2) however the initial directory in each tab is NOT the same as it was when the previous Windows Terminal session was closed, but tabs appear to have the same directory set.
I have tried changing the startingDirectory for the profile I was using from "startingDirectory": "%USERPROFILE%" to "startingDirectory": null but it makes no difference.

Did you make sure you've actually configured your shell to tell the Terminal what the CWD is?
Refer to: Opening a tab or pane in the same directory in Windows Terminal.

I've just tried coping in the prompt function from powershell-with-posh-git to configure CWD on PowerShell with posh-git.
This does and doesn't work for my scenario.  It works to remember the previous CWD for each tab when startingDirectory  is set to null.
I am also using oh-my-posh to format the PowerShell prompt on top of posh-git and with the prompt function in my PowerShell profile I lose all of my oh-my-posh look and feel.

I think I have it working now with oh-my-posh too.
I've set the startingDirectory to null and added "pwd": "osc99" to my on-my-posh config as stated here


Promise support + existsSymlinks

Hi, I need a package like this in pnpm.
Would you accept a pull request that would add promise to the async function and maybe a new existsSymlink function?

absolutely!
If cb  is provided in the async method use it; otherwise, return a promise. I used that in other projects.

Also take in consideration the node environment. I prefer don't include a promise polyfill, so I accept drop old node versions.

I also have a nice plugin for testing usage examples in Readme. It would be nice to test the example in this package. https://github.com/mosjs/mos/tree/master/packages/mos-plugin-example

I think this validation check is weird https://github.com/Kikobeats/exists-file/blob/master/index.js#L13
If it is not a string an error has to be thrown. Otherwise it is a silent error

@zkochan I think that you're right!

Open a new issue/pr for existsSymlinks support if you need it 😄

Actually I think it would look nicer in a separate package and then we can cross-reference each-other

@zkochan I think the same, so 👍


App Broken - Ubisoft Connect - Game news

App Broken in game news/info  - Ubisoft Connect
How can i determine which host was blocked through windows hosts? I am using ultimate energized hosts.
I removed all energized hosts and the game info is shown again.
Can someone please guide me. Thank you!

I removed the energized hosts, and with Glasswire I was able to track the hosts where the app connects that are included in the energized hosts:
<IP_ADDRESS> o.ss2.us
<IP_ADDRESS> lookup.qubit.com
<IP_ADDRESS> cdn.cquotient.com
<IP_ADDRESS> stash.qubitproducts.com
<IP_ADDRESS> p.cquotient.com
<IP_ADDRESS> gong-eb.qubit.com
however I don't know yet which exactly of these actually breaks the functionality.
What I really cannot figure out and cannot find the answer on the Internet is how could I actually find which domain is being blocked by windows hosts without actually disabling energized hosts and exposing myself to tracking,advertisements etc..
I tried wireshark, but the query is not logged there of course because hosts mapping happens before dns query..
I would be really greatful if someone is willing to enlighten me.


How to use in combination with baseHref on external url?

🧩 Feature request
Description
Hey guys,
I was testing scully and encountered an issue that when you define baseHref in angular.json to an external URL such as:
 "configurations": {
            "production": {
              "outputPath": "dist/prod",
              "baseHref": "https://cdn.com/app/",
              "optimization": true,
              "outputHashing": "all",
              ...

the generated html files are pretty much empty, which makes sense because the files are not yet uploaded to external source and requests to files fail with 404. The external source in this case is CDN where the final build is pushed.
Is there a way to let scully use "local" base href to generate html files, but use external baseHref in final output build so that it can then be deployed to external destination?

Same with all custom baseHref's which are different than the default "/". It a baseHref is set, the prerendered html files are empty within the  part. Same things happen when you use the angular i18n tools and build your project with the --localize flag, then angular automatically sets the baseHref to "/de/" or "/en/" automatically because angular builds a separate project for each language into a subfolder...
I thing this is definitely a bug, because setting the baseHref is a default feature of angular but scully is not yet using the baseHref

@dyingangel666 Setting the base-href is a feature of Angular-CLI. Angular itself does actually nothing.
I'm currently working on a plugin that allows you to rewrite the base-href. That will be configurable, and even different for routes. Ihope this will be available this week.


Cannot return NotImplemented from in-place arithmetic operators

Bug Description
The in-place arithmetic magic methods (e.g. __iadd__) can return NotImplemented in Python space, and this is used to delegate a += b to a = type(b).__radd__(b, a) if a's __iadd__ returns NotImplemented.  For example (pardon the terribly behaved objects):
class NoAdd:
    def __iadd__(self, other):
        return NotImplemented

class AllowsRightAdd:
    def __radd__(self, other):
        return "hello, world"

x = NoAdd()
x += AllowsRightAdd()
assert x == "hello, world"

If I understand the code/error message correctly, PyO3 requires the happy-path return from __iadd__ and other in-place operators to be () such that it can fill in the self return that Python wants.  This makes it not possible to return NotImplemented to allow delegation in these methods.
Steps to Reproduce
Define a Rust #[pyclass] that implements one of the in-place arithmetic operators, attempting to return NotImplemented with any signature, including ones where the self object is returned.  Something like this is probably minimal:
use pyo3::prelude::*;

#[pyclass]
struct MyStruct;

#[pymethods]
impl MyStruct {
    fn __iadd__(slf_: Bound<Self>, _other: Bound<PyAny>) -> Py<PyAny> {
        slf_.py().NotImplemented()
    }
}

#[pymodule]
fn core(m: &Bound<PyModule>) -> PyResult<()> {
    m.add_class::<MyStruct>()?;
    Ok(())
}

Backtrace
Compiling the above file gives something like

error[E0277]: the trait bound `pyo3::Py<pyo3::PyAny>: IntoPyCallbackOutput<()>` is not satisfied
   --> src/lib.rs:6:1
    |
6   | #[pymethods]
    | ^^^^^^^^^^^^ the trait `IntoPyCallbackOutput<()>` is not implemented for `pyo3::Py<pyo3::PyAny>`
    |
    = help: the following other types implement trait `IntoPyCallbackOutput<Target>`:
              `()` implements `IntoPyCallbackOutput<()>`
              `()` implements `IntoPyCallbackOutput<i32>`
              `*mut PyObject` implements `IntoPyCallbackOutput<*mut PyObject>`
              `HashCallbackOutput` implements `IntoPyCallbackOutput<isize>`
              `Result<T, E>` implements `IntoPyCallbackOutput<U>`
              `bool` implements `IntoPyCallbackOutput<bool>`
              `bool` implements `IntoPyCallbackOutput<i32>`
              `usize` implements `IntoPyCallbackOutput<isize>`
              `usize` implements `IntoPyCallbackOutput<usize>`
note: required by a bound in `pyo3::callback::convert`
   --> /Users/jake/code/pyo3/pyo3/src/callback.rs:170:8
    |
168 | pub fn convert<T, U>(py: Python<'_>, value: T) -> PyResult<U>
    |        ------- required by a bound in this function
169 | where
170 |     T: IntoPyCallbackOutput<U>,
    |        ^^^^^^^^^^^^^^^^^^^^^^^ required by this bound in `convert`
    = note: this error originates in the attribute macro `pymethods` (in Nightly builds, run with -Z macro-backtrace for more info)

For more information about this error, try `rustc --explain E0277`.
error: could not compile `pyo3_test` (lib) due to 1 previous error

Your operating system and version
macOS 14
Your Python version (python --version)
Python 3.10.6
Your Rust version (rustc --version)
rustc 1.81.0 (eeb90cda1 2024-09-04)
Your PyO3 version
0.22.3 or commit 4cbf6e0
How did you install python? Did you use a virtualenv?
Built from source, run from a venv.
Additional Info
Fwiw, I don't think it's a good idea to write classes that do this, I just found this while trying to make a new type in Rust that matches some questionable Python-space behaviour of a pre-existing related class.  I'm not actually going to match the behaviour in the end, so this isn't a high priority for me at all.
This feels like a case that could degrade the user experience to resolve if not careful - if the in-place arithmetic methods are updated to allow signatures that return arbitrary Python objects, we'd have to have a way of teaching users that they're supposed to return the self object from in-place operations in the happy path, which previously they've not had to do.  It feels clear to me that the default and suggested form should continue to be to have the method return impl IntoPyCallbackOutput<()>, and anything that allows support for NotImplemented should be something that's explicitly opted into.

For example with the potential confusion, #4507 shows that there's definitely some expectations around the return types, and people who've tried to return self.  I'm slightly worried that making it possible to return NotImplemented makes it quite easy to accidentally start doing the wrong thing.
Maybe a #[pyo3(arbitrary_inplace_return)] annotation or something like that to enable a different mode for the callback generation, so the user has to be way more explicit about doing something non-standard?

I think there's definitely scope to improve here, and we can probably do it backwards-compatibly. Ideally we should match more closely to the Python behaviour, because that's most intuitive for users (as you yourself suggest).
Related to these operators is also #4026 where my main concern was the __radd__ operators and friends and the complexity we have internally there. Perhaps both of these problems can be solved at the same time.


MudBadge: Center content with flex instead of negative margins

Description
MudBadge component currently uses margins to calculate the proper center position of the icon (or content in general).
When changing the browser zoom the icon inside of the MudBadge has been misplaced due to this calculations.
This PR uses flexbox to center the elements vertically and horizontally without any specific pixel definitions, which is more stable.
It is known that the misalignment is still happening, but according to my current knowledge this is caused by calculations of the positions that might end up being subpixel and browser shifts it to the left or right.
Resolves #9294
How Has This Been Tested?
Issue can be tested on https://mudblazor.com/components/badge#usage page with "Security issues" badge.
Type of Changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation (fix or improvement to the website or code docs)

Checklist

[x] The PR is submitted to the correct branch (dev).
[x] My code follows the code style of this project.
[ ] I've added relevant tests.

Thanks!


Add DDEV maintainer job description, fixes ddev/ddev#4867

The Issue

https://github.com/ddev/ddev/issues/4867
#50

How This PR Solves The Issue
First stab at paid maintainer opportunity
Blog for review is https://36860f41.ddev-com-front-end.pages.dev/blog/maintainer-job-description/

Good suggestions and thanks @mattstein , it's more of an announcement now, would love another quick scan.

Thanks so much for your help on this.


Broken link in README

Hello!
I noticed that the link to the releases page in the "Download the App" section does not lead to anywhere. It seems to be missing a colon after the "https".

PR #97 appears to fix this.  Can you confirm?

Yes, it's been fixed!


Add yarnrc files to all templates

This should prevent yarn from using the root yarn version because of config merging with parent folders.

Replaced by https://github.com/thetribeio/generator-project/pull/1749


Can't use get_total_balance method

When I am trying to get total balance, I am getting that error
File "C:\Users\User\Desktop\venv\myvenv\lib\site-packages\kucoin\client.py", line 1003, in get_total_balance
coins_csl = ','.join([b['coinType'] for b in balances])
File "C:\Users\User\Desktop\venv\myvenv\lib\site-packages\kucoin\client.py", line 1003, in
coins_csl = ','.join([b['coinType'] for b in balances])
TypeError: string indices must be integers

Hi @MoXyLe can you test it again with the latest version, there was a change to an underlying call which has been fixed.

I tested, everything is fine


Pretrained Cnn14 16kHz wrong shape errors

After downloading Cnn14_16k_mAP=0.438.pth and following these instructions:
MODEL_TYPE="Cnn14_16k"
CHECKPOINT_PATH="Cnn14_16k_mAP=0.438.pth"   # Trained by a later version of code, achieves higher mAP than the paper.
CUDA_VISIBLE_DEVICES=0 python3 pytorch/inference.py audio_tagging --sample_rate=16000 --window_size=512 --hop_size=160 --mel_bins=64 --fmin=50 --fmax=8000 --model_type=$MODEL_TYPE --checkpoint_path=$CHECKPOINT_PATH --audio_path='resources/R9_ZSCveAHg_7s.wav' --cuda

I get the following error:
Traceback (most recent call last):
  File "pytorch/inference.py", line 201, in <module>
    audio_tagging(args)
  File "pytorch/inference.py", line 42, in audio_tagging
    model.load_state_dict(checkpoint['model'])
  File "/home/*user*/anaconda3/envs/onseilake/lib/python3.7/site-packages/torch/nn/modules/module.py", line 847, in load_state_dict
    self.__class__.__name__, "\n\t".join(error_msgs)))
RuntimeError: Error(s) in loading state_dict for Cnn14_16k:
	size mismatch for spectrogram_extractor.stft.conv_real.weight: copying a param with shape torch.Size([257, 1, 512]) from checkpoint, the shape in current model is torch.Size([129, 1, 256]).
	size mismatch for spectrogram_extractor.stft.conv_imag.weight: copying a param with shape torch.Size([257, 1, 512]) from checkpoint, the shape in current model is torch.Size([129, 1, 256]).
	size mismatch for logmel_extractor.melW: copying a param with shape torch.Size([257, 64]) from checkpoint, the shape in current model is torch.Size([129, 64]).

Thank you for open sourcing everything!

Hi, just to confirm, have you executed: CHECKPOINT_PATH="Cnn14_16k_mAP=0.438.pth"?

Yes, this is the output of the variable:
echo $CHECKPOINT_PATH
# output: Cnn14_16k_mAP=0.438.pth

To make sure I didn't make any mistake or used outdated code (using master branch), I ran the following commands in a new terminal again:
$ git pull
Already up to date.
$ git branch
* master
$ MODEL_TYPE="Cnn14_16k"
$ CHECKPOINT_PATH="Cnn14_16k_mAP=0.438.pth"
$ echo $CHECKPOINT_PATH
Cnn14_16k_mAP=0.438.pth
$ CUDA_VISIBLE_DEVICES=0 python3 pytorch/inference.py audio_tagging --sample_rate=16000 --window_size=512 --hop_size=160 --mel_bins=64 --fmin=50 --fmax=8000 --model_type=$MODEL_TYPE --checkpoint_path=$CHECKPOINT_PATH --audio_path='resources/R9_ZSCveAHg_7s.wav' --cuda
*Same error as first post*

Unfortunately still the same error...

Is there any chance that you renamed the wrong model (a 32k model) to Cnn14_16k_mAP=0.438.pth before uploading it to Zenodo?
The model I downloaded is 358.7 MB, matching the info from version 3 of the Zenodo page.

Here are the details of the model in case it helps:
import torch
model = torch.load("Cnn14_16k_mAP=0.438.pth")
for name, tensr in model['model'].items():
    print(name, tensr.shape)

Output:
spectrogram_extractor.stft.conv_real.weight torch.Size([257, 1, 512])
spectrogram_extractor.stft.conv_imag.weight torch.Size([257, 1, 512])
logmel_extractor.melW torch.Size([257, 64])
bn0.weight torch.Size([64])
bn0.bias torch.Size([64])
bn0.running_mean torch.Size([64])
bn0.running_var torch.Size([64])
bn0.num_batches_tracked torch.Size([])
conv_block1.conv1.weight torch.Size([64, 1, 3, 3])
conv_block1.conv2.weight torch.Size([64, 64, 3, 3])
conv_block1.bn1.weight torch.Size([64])
conv_block1.bn1.bias torch.Size([64])
conv_block1.bn1.running_mean torch.Size([64])
conv_block1.bn1.running_var torch.Size([64])
conv_block1.bn1.num_batches_tracked torch.Size([])
conv_block1.bn2.weight torch.Size([64])
conv_block1.bn2.bias torch.Size([64])
conv_block1.bn2.running_mean torch.Size([64])
conv_block1.bn2.running_var torch.Size([64])
conv_block1.bn2.num_batches_tracked torch.Size([])
conv_block2.conv1.weight torch.Size([128, 64, 3, 3])
conv_block2.conv2.weight torch.Size([128, 128, 3, 3])
conv_block2.bn1.weight torch.Size([128])
conv_block2.bn1.bias torch.Size([128])
conv_block2.bn1.running_mean torch.Size([128])
conv_block2.bn1.running_var torch.Size([128])
conv_block2.bn1.num_batches_tracked torch.Size([])
conv_block2.bn2.weight torch.Size([128])
conv_block2.bn2.bias torch.Size([128])
conv_block2.bn2.running_mean torch.Size([128])
conv_block2.bn2.running_var torch.Size([128])
conv_block2.bn2.num_batches_tracked torch.Size([])
conv_block3.conv1.weight torch.Size([256, 128, 3, 3])
conv_block3.conv2.weight torch.Size([256, 256, 3, 3])
conv_block3.bn1.weight torch.Size([256])
conv_block3.bn1.bias torch.Size([256])
conv_block3.bn1.running_mean torch.Size([256])
conv_block3.bn1.running_var torch.Size([256])
conv_block3.bn1.num_batches_tracked torch.Size([])
conv_block3.bn2.weight torch.Size([256])
conv_block3.bn2.bias torch.Size([256])
conv_block3.bn2.running_mean torch.Size([256])
conv_block3.bn2.running_var torch.Size([256])
conv_block3.bn2.num_batches_tracked torch.Size([])
conv_block4.conv1.weight torch.Size([512, 256, 3, 3])
conv_block4.conv2.weight torch.Size([512, 512, 3, 3])
conv_block4.bn1.weight torch.Size([512])
conv_block4.bn1.bias torch.Size([512])
conv_block4.bn1.running_mean torch.Size([512])
conv_block4.bn1.running_var torch.Size([512])
conv_block4.bn1.num_batches_tracked torch.Size([])
conv_block4.bn2.weight torch.Size([512])
conv_block4.bn2.bias torch.Size([512])
conv_block4.bn2.running_mean torch.Size([512])
conv_block4.bn2.running_var torch.Size([512])
conv_block4.bn2.num_batches_tracked torch.Size([])
conv_block5.conv1.weight torch.Size([1024, 512, 3, 3])
conv_block5.conv2.weight torch.Size([1024, 1024, 3, 3])
conv_block5.bn1.weight torch.Size([1024])
conv_block5.bn1.bias torch.Size([1024])
conv_block5.bn1.running_mean torch.Size([1024])
conv_block5.bn1.running_var torch.Size([1024])
conv_block5.bn1.num_batches_tracked torch.Size([])
conv_block5.bn2.weight torch.Size([1024])
conv_block5.bn2.bias torch.Size([1024])
conv_block5.bn2.running_mean torch.Size([1024])
conv_block5.bn2.running_var torch.Size([1024])
conv_block5.bn2.num_batches_tracked torch.Size([])
conv_block6.conv1.weight torch.Size([2048, 1024, 3, 3])
conv_block6.conv2.weight torch.Size([2048, 2048, 3, 3])
conv_block6.bn1.weight torch.Size([2048])
conv_block6.bn1.bias torch.Size([2048])
conv_block6.bn1.running_mean torch.Size([2048])
conv_block6.bn1.running_var torch.Size([2048])
conv_block6.bn1.num_batches_tracked torch.Size([])
conv_block6.bn2.weight torch.Size([2048])
conv_block6.bn2.bias torch.Size([2048])
conv_block6.bn2.running_mean torch.Size([2048])
conv_block6.bn2.running_var torch.Size([2048])
conv_block6.bn2.num_batches_tracked torch.Size([])
fc1.weight torch.Size([2048, 2048])
fc1.bias torch.Size([2048])
fc_audioset.weight torch.Size([527, 2048])
fc_audioset.bias torch.Size([527])

Hi Stef,
My bad! I have fixed this bug! The error comes from that the Cnn14_16k

model file is not updated. Just pull the latest code version, and it should
run! (Zenodo models are unchanged.) By the way, I have also added the 8 kHz
model!
Please let me know if there are any further questions!

Best wishes,
Qiuqiang
On Mon, 24 Aug 2020 at 16:51, Stef | ステフ<EMAIL_ADDRESS>wrote:

Yes, this is the output of the variable:
echo $CHECKPOINT_PATH# output: Cnn14_16k_mAP=0.438.pth
To make sure I didn't make any mistake or used outdated code (using master
branch), I ran the following commands in a new terminal again:
$ git pull
Already up to date.
$ git branch* master
$ MODEL_TYPE="Cnn14_16k"
$ CHECKPOINT_PATH="Cnn14_16k_mAP=0.438.pth"
$ echo $CHECKPOINT_PATH
Cnn14_16k_mAP=0.438.pth
$ CUDA_VISIBLE_DEVICES=0 python3 pytorch/inference.py audio_tagging --sample_rate=16000 --window_size=512 --hop_size=160 --mel_bins=64 --fmin=50 --fmax=8000 --model_type=$MODEL_TYPE --checkpoint_path=$CHECKPOINT_PATH --audio_path='resources/R9_ZSCveAHg_7s.wav' --cudaSame error as first post
Unfortunately still the same error...
Is there any chance that you renamed the wrong model (a 32k model) to
Cnn14_16k_mAP=0.438.pth before uploading it to Zenodo?
The model I downloaded is 358.7 MB, matching the info from version 3 of
the Zenodo page https://zenodo.org/record/3987831.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/qiuqiangkong/audioset_tagging_cnn/issues/18#issuecomment-678998108,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADFXTSJLZE5RCWQWP6H6WZ3SCISZJANCNFSM4QJEP5VA
.

I have fixed this bug by updating pytorch/models.py. All Zenodo models are unchanged. Please git pull, and it should work!

It works now! Thanks for the quick fix.
There is a small issue with the instructions, however. The README.md says to use --audio_path='resources/R9_ZSCveAHg_7s.wav', but that should be changed to .mp3.
There is no .wav in the folder resources.

Hi Stef,
I have added the wav file to resources/R9_ZSCveAHg_7s.wav. Many thanks!

Best wishes,
Qiuqiang
On Tue, 25 Aug 2020 at 10:12, Stef | ステフ<EMAIL_ADDRESS>wrote:

It works now! Thanks for the quick fix.
There is a small issue with the instructions, however. The README.md says
to use --audio_path='resources/R9_ZSCveAHg_7s.wav', but that should be
changed to .mp3.
There is no .wav in the folder resources.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/qiuqiangkong/audioset_tagging_cnn/issues/18#issuecomment-679460611,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADFXTSJYEJH7DGWEWUJ6DS3SCMMXBANCNFSM4QJEP5VA
.

Thank you for your quick fixes! Your work will progress the field of audio deep learning!


Finance Tracker

🛠 Issue (Number)

Closes #887
Description
I have fixed the bug and the project is running smoothely.
Type of change

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

Checklist:

[x] I have made this from my own
[ ] I have taken help from some online resourses
[x] My code follows the style guidelines of this project
[x] have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] The title of my pull request is a short description of the requested changes.

ATTACH SCREEN-SHOTS / DEPLOYMENT LINK

@zugzwang03  Added README FILE and updated the branch

it is not updated

@zugzwang03  please check it again from my computer it is saying everything up to date.

please help me if i have done something wrong.

please reveiw this

update from your forked repo


IYO GUID feature

only needed from API
allow any APP (API client linked to organization) to request a unique GUID for a user or organization
only this APP can request which user is behind the GUID
each ORG can ask max 10 of these unique GUID's for 1 specific user or org
there is also feature which allows APP to store some data behind this GUID in IYO, this is just binary info & only means something for the APP (max size = 1kb), only APP can retrieve if it also knows the GUID.

e.g. use case tokens in TF app

we register info on blockchain e.g. tierion.com but we don't want to put email or other identifiable ID
this allows the APP (which is org with API client) to create a link between GUID and a user or organization and register that way
if ever needed this APP can retrieve the user ID but only this APP

use case for the data

keep track of metadata relevant to this user
e.g. imagine app is storing coin info in the blockchain, it needs to be able to remember previous registrations for this user (or a link to the previous one so the app can walk back). can do this as e.g. a json in this data field

other use case

register info in Zero-Tlog server, when Tlog server finishes, register the hash & other relevant info in tierion (encrypted using the IYO GUID) which is only known by the APP
this allows the APP to keep track of lots of info which is stored in Zero-STOR through TLOG server & can be used for full audit trails

@despiegk, do we really need this feature. I think we can achieve exactly the same by using an hmac of a secret only known by the app and the username.

@despiegk What is the relevance for this feature? To me it feels like a GUID (or something similar) is just some random data we generate, i.e. it has no real (personal) value for a user, unlike all the other info we keep . Furthermore, since only an organization can request GUIDs for a user, this really feels like app-specific functionality.

I like this feature,  since we want to move away from username as much as possible, it would be like a consumer specific ID and since you can request multiple, this prevents datamining on them

@robvanmieghem @despiegk See https://github.com/itsyouonline/identityserver/blob/1.0.0/specs/GUID_feature.md for a small spec + some remarks about this feature. Please approve , post remarks, give feedback, etc...

@LeeSmet  shouldn't we allow these identifiers to be used instead of {username} in the api?

yes, that is the plan, however that brings up a first possible implementation issue

Updated the spec to be more clear / add another possible issue

@LeeSmet where are the usernames used in json structures?

A few places in the organizations api currently, for example when inviting a user (in this case the json is just a string with a username/email/phone number). Also when chaning the role of a user in an organization (promoting member to owner or the other way around), in this case the json body is a username and a (new) role

Ability to create, list and lookup such ids implemented according to the spec written earlier, bar some small changes to solve some practical issues. I'll update the spec later.
Still need to implement the ability to use these as valid identifiers in urls and request bodies


Speech v1

This updates our manual client library to the Speech v1 API.
This entails several backwards incompatible changes:

The language_code parameter is no longer optional anywhere. It must be explicitly specified, and does not default to 'en-US'.
The sync_recognize method has been renamed to recognize on every class where it appears.
The async_recognize method has been renamed to long_running_recognize on every class where it appears.
The sample_rate parameter and property has been renamed to sample_rate_hertz everywhere it appears.

Additionally, the backend API contains a backwards incompatible change which does not require a code change in the client library, but will likely require one downstream: The START_OF_SPEECH, END_OF_SPEECH, and END_OF_AUDIO events have been removed.

LGTM pending CI

@gguuss Are the samples ready for this? We are ready to push it out once your documentation is updated.

I'll let y'all know when I have my change in a branch

Sample changes staged here

@lukesneeringer seems weird that the samples have to do speech_client.speech_api.x?

@jonparrott We do not. Those changes are red in the diff. :-)

@gguuss I am ready to push this to PyPI, as soon as you say you are ready.

@gguuss Poke. (This is due today, so I will push it to PyPI around noon regardless.)

I'm ready to go.

hello


89 segfault in enumerative balancedness test

Refactored matrix slicing. These were renamed:

CMRchrmatZoomSubmat is now CMRchrmatSlice
CMRintmatZoomSubmat is now CMRintmatSlice
CMRdblmatZoomSubmat is now CMRdblmatSlice
CMRsubmatZoomSubmat is now CMRsubmatSlice

A new function CMRsubmatUnslice was added for reverting a slicing operation (on the level of indices).

@xuluze The renaming of the *Zoom function is probably also relevant for you!

@xuluze The renaming of the *Zoom function is probably also relevant for you!

Thank you! I will check it out.


Added fastp to pipeline

PR checklist

[ ] This comment contains a description of changes (with reason).
[ ] If you've fixed a bug or added code that should be tested, add tests!
[ ] If you've added a new tool - have you followed the pipeline conventions in the contribution docs
[ ] If necessary, also make a PR on the nf-core/nfcoredevtest branch on the nf-core/test-datasets repository.
[ ] Make sure your code lints (nf-core lint).
[ ] Ensure the test suite passes (nextflow run . -profile test,docker --outdir <OUTDIR>).
[ ] Check for unexpected warnings in debug mode (nextflow run . -profile debug,test,docker --outdir <OUTDIR>).
[ ] Usage Documentation in docs/usage.md is updated.
[ ] Output Documentation in docs/output.md is updated.
[ ] CHANGELOG.md is updated.
[ ] README.md is updated (including new tool citations and authors/contributors).

yes


chore: cache crosseref DOI GET requests

https://github.com/ietf-tools/bibxml-service/issues/364

DOIs requests to Crossref are now being cached. In case we do not have a cached version, or the user tries to retrieve an invalid DOI, I've added the following message.
Does this align what you had in mind @kesara ?

The error message has been further improved in https://github.com/ietf-ribose/bibxml-service/pull/38/commits/98203206570e69909a9aff3b7b1714dbbbd284fe, the screenshot is only a reference to how the message will look like.

@stefanomunarini yeah, this implementation looks good to me.


Column.xlf Translation is missing

The english translation file Resources/Private/Translations/en/NodeTypes/Column.xlf is missing

Fixed with release 0.0.3


fix(tool): add default mode to parameters

When the tool component loads, the default parameter is grabbed and then an effect is run to emit an
event to actually change the color mode on the story component.
fix #3

:tada: This PR is included in version 1.1.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


feat: add solana network connection support

This PR introduces support for the Solana network, enabling seamless wallet connections for users. The following enhancements have been made:

Added Solana Wallet Provider: Integrated the Solana wallet provider to facilitate wallet connections.
Updated Wallet Connector Mapping: Enhanced the mapping logic to render available wallet connectors for the Solana network.
Implemented Connect/Disconnect Handlers: Developed handlers for connecting and disconnecting the Solana wallet within the useConnectWallet hook, ensuring a smooth user experience.
Root Layout Integration: Wrapped the root layout with the Solana wallet provider to ensure that all components have access to the wallet context.

Example:

Also need to add a feature flag that enables Solana, since other parts of the app is not ready. Also need to support Solana execlusive behaviour for Solana specific site.


Can't receive incoming mails: 550 Invalid server token

Hello, I have an issue with incoming emails. (maybe same problem as #167)
Version used: 1.0.0-7d2484d47f-stable
I made an organization and a mail server.
Then, I have set up a route:
Name<EMAIL_ADDRESS>Endpoint<EMAIL_ADDRESS>Then, when I send a message with an another mail client to this mail, example:
Mail from<EMAIL_ADDRESS>to<EMAIL_ADDRESS>Gmail send me a message:
 550 Invalid server token

Final-Recipient: rfc822<EMAIL_ADDRESS>Action: failed
Status: 5.0.0
Remote-MTA: dns; testmail.xxxxx.fr. (178.xx.xx.152, the server for the
 domain testmail.xxxxx.fr.)
Diagnostic-Code: smtp; 550 Invalid server token
Last-Attempt-Date: Wed, 31 May 2017 05:45:19 -0700 (PDT)

When I look at the logs in /opt/postal/log/smtp_server.log:
[smtp.1:6819] [2017-05-31T12:16:59.950] INFO -- : Listening on port 25
[smtp.1:6819] [2017-05-31T12:24:11.918] DEBUG -- : [LK9UHO]    Connection opened from ::ffff:<IP_ADDRESS>
[smtp.1:6819] [2017-05-31T12:24:11.919] DEBUG -- : [LK9UHO]    Client identified as ::ffff:<IP_ADDRESS>
[smtp.1:6819] [2017-05-31T12:24:12.104] DEBUG -- : [LK9UHO] <= EHLO mail-ua0-f177.google.com
[smtp.1:6819] [2017-05-31T12:24:12.113] DEBUG -- : [LK9UHO] => 250-My capabilities are
[smtp.1:6819] [2017-05-31T12:24:12.113] DEBUG -- : [LK9UHO] => 250-STARTTLS
[smtp.1:6819] [2017-05-31T12:24:12.113] DEBUG -- : [LK9UHO] => 250 AUTH CRAM-MD5 PLAIN LOGIN
[smtp.1:6819] [2017-05-31T12:24:12.336] DEBUG -- : [LK9UHO] <= STARTTLS
[smtp.1:6819] [2017-05-31T12:24:12.337] DEBUG -- : [LK9UHO] => 220 Ready to start TLS
[smtp.1:6819] [2017-05-31T12:24:12.753] DEBUG -- : [LK9UHO] <= EHLO mail-ua0-f177.google.com
[smtp.1:6819] [2017-05-31T12:24:12.761] DEBUG -- : [LK9UHO] => 250-My capabilities are
[smtp.1:6819] [2017-05-31T12:24:12.761] DEBUG -- : [LK9UHO] => 250 AUTH CRAM-MD5 PLAIN LOGIN
[smtp.1:6819] [2017-05-31T12:24:12.984] DEBUG -- : [LK9UHO] <= MAIL<EMAIL_ADDRESS>[smtp.1:6819] [2017-05-31T12:24:12.985] DEBUG -- : [LK9UHO] => 250 OK
[smtp.1:6819] [2017-05-31T12:24:13.077] DEBUG -- : [LK9UHO] <= RCPT<EMAIL_ADDRESS>[smtp.1:6819] [2017-05-31T12:24:13.551] DEBUG -- : [LK9UHO] => 550 Invalid server token
[smtp.1:6819] [2017-05-31T12:24:13.644] DEBUG -- : [LK9UHO] <= QUIT
[smtp.1:6819] [2017-05-31T12:24:13.644] DEBUG -- : [LK9UHO] => 221 Closing Connection
[smtp.1:6819] [2017-05-31T12:24:13.644] DEBUG -- : [LK9UHO]    Connection closed

The output of the host testmail.xxxxx.fr command:
testmail.xxxxx.fr has address 178.xx.xx.152
testmail.xxxxx.fr mail is handled by 10 testmail.xxxxx.fr.

(So I have a good DNS MX setup)
Can you help me please? Thank you very much.

You can't configure Postal to receive messages on the same domain as that which is used dns.return_path or any domain that beings with the dns.custom_return_path_prefix.

Thank you for you response. So what can I do to achieve my goal?
If I set a different dns.return_path value, now I have the error:
550 Invalid route token

It also can't be the same as dns.route_domain

Adam, I just have installed one postal on one of my VPS, there is several concepts I have confused, for example could you please explain more detail about dns.return_path and dns.custom_return_path_prefix

@Nurza did you get this resolved?

Yes, I created a sub domains for each service very much like this: https://github.com/atech/postal/wiki/Domains-&-DNS-Configuration
And it worked.
Thank you very much !


Fix regression in reroute logic when a node passes disk watermarks.

Summary of the changes / Why this improves CrateDB
DiskUsage takes disk path total bytes instead of
available bytes as the last argument.
relates to #9153
Checklist

[x] User relevant changes are recorded in CHANGES.txt
[x] Touched code is covered by tests
[ ] Documentation has been updated if necessary
[x] CLA is signed
[x] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

retest this please


Update aspnet_identity.rst

Typo in the word "authentication" in the last paragraph
What issue does this PR address?
Does this PR introduce a breaking change?
Please check if the PR fulfills these requirements

[x] The commit follows our guidelines
[x] Unit Tests for the changes have been added (for bug fixes / features)

Other information:

ah, good catch. thanks!


fix: skip float16 and float64 for bn

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation and Context
skip float16 and float64 for bn
Description
set in device_config
Use cases (Optional)

BC-breaking (Optional)

Checklist
Before PR:

[x] I have read and followed the workflow indicated in the Contributors.md to create this PR.
[x] Pre-commit or linting tools indicated in Contributors.md are used to fix the potential lint issues.
[x] Bug fixes are covered by unit tests, the case that causes the bug should be added in the unit tests.
[x] New functionalities are covered by complete unit tests. If not, please add more unit test to ensure the correctness.
[x] The documentation has been modified accordingly, including docstring or example tutorials.

After PR:

[x] CLA has been signed and all committers have signed the CLA in this PR.

close this pr since it's not neccessary


Upgrade Go from 1.4.2 to 1.5

PS. From the v1.5, the minimum OS X version is 10.8.

Please don’t remove the conditional. Adapt the cask to it.

@vitorgalvao You mean the line if MacOS.release <= :mountain_lion should be there without any else condition? Hm...

No, I mean there should be a new intermediary condition. The latest version always remains on the else.

@vitorgalvao Frankly, I don't get what you're trying to say :cry:

I mean not undoing what works, but adding to it.
Thank you anyway for your work.

@vitorgalvao Ach so, now I get your point. Wow. However, this seems rather weird to me. Anyway, thanks for help!

However, this seems rather weird to me.

Why? Many other casks follow this solution.

@vitorgalvao When there's a newer app version and a vendor for it has constricted the number of supported OS versions, it's no accident. What is more, I don't understand why some things are to entirely be rewritten and for the rest we should leave the mentioning of the previous versions. The old version is the old version, and, to my mind, it must be everywhere either kept or removed. But maybe I don't merely see the real advantage :rooster:

If we did it the way you suggest, than anyone with an OS X version under Mountain Lion would be left in the dust and wouldn’t be able to get Go from the cask. This way, everyone get the latest version available for their OS. There is no downside to users with this method, but there would be with yours.

@vitorgalvao Yep, but I still see no difference in whether these users of the old OS X versions cannot upgrade Go themselves because the vendor didn't make it possible, or it won't be accessible through the Cask. However, I partly agree with you that if there's a temporary way out, why not.


Filter out empty outputs (fix #3251)

This PR removes empty outputs mentioned in #3251

Pre-submit checklist:

Branch

[x] Commit sequence broadly makes sense
[x] Key commits have useful messages
[x] Relevant tickets are mentioned in commit messages
[ ] Formatting, materialized Nix files, PNG optimization, etc. are updated

PR

[x] Self-reviewed the diff
[x] Useful pull request description
[x] Reviewer requested

Pre-merge checklist:

[ ] Someone approved it
[ ] Commits have useful messages
[ ] Review clarifications made it into the code
[ ] History is moderately tidy; or going to squash-merge

conflicts


Fixed heroku links on win7 and win8 if the toolbelt isn't available.

Should we just remove the dashboard images? It looks like they're wrong and need to be updated.

Thx Brian!


add new dropdown menu button in apply section for content of page.also provide dircet link to that.

adding a new dropdown menu button in apply section  will greatly enhance the user experience by consolidating all project information into a single, easily accessible dropdown. This improvement will save users time and effort by allowing them to view all their projects at once, streamlining navigation and making the interface more efficient.
make changes at this page :

@ceilican I want to work on this issue. please assign it to me

okk,Harsh do it !!!

I would like to work on this issue. Can You please assign this issue to me.


Postgres image now requires POSTGRES_PASSWORD

Source: https://github.com/docker-library/postgres/pull/658#pullrequestreview-336007842

This is a breaking change, but I think it's one that makes sense overall (and that the benefit outweighs the pain in this instance).

We need to add a password in docker-compose.yml and make sure it is passed properly in the contribution doc (CONTRIBUTING.rst)

@charlesaracil-ulti up for it ?

@ewjoachim of course !

Closed by #177