Shell false positives for rules 932260 and 932236

Description
I've encountered some shell false positives for 932260 (PL1) , 932236 and 932239 (PL2) for commands like sudo, df, fd, and grc.
Some of these I'm obviously familiar with, but others like 'fd' or 'grc' I've never come across before. I'm not sure exactly what they are or how commonly they may be used in attacks/information leakage, or how relaxed is even appropriate. Would it be acceptable for 'sudo' to be broken out into sudo@ and sudoedit, sudoreplay, etc, fd to fd@, df to<EMAIL_ADDRESS>I'd think this would be ok, but I also don't know if there are additional commands that these substrings were intended to match on. And more generally should these lists be revisited to ensure the matches are concise enough? I feel like there's some potential for additional FPs on unix-shell-upto3.ra and even some of the 4 character words on unix-shell-4andup.ra (expr, sched, uniq).
I didn't include any examples for grc. It just happens to match on the first 3 characters of a cookie prefix we use for a site and I've taken care of those individually. Just thought it was worth mentioning due to my unfamiliarity and the general questions.
How to reproduce the misbehavior (-> curl call)
932260 - PL1 on 'sudo' in REQUEST_COOKIES:fpestid
curl -H "x-format-output: txt-matched-rules" --cookie "fpestid=SUDoLongRandomString" https://sandbox.coreruleset.org/
932260 PL1 Remote Command Execution: Direct Unix Command Execution
949110 PL1 Inbound Anomaly Score Exceeded (Total Score: 5)
980170 PL1 Anomaly Scores: (Inbound Scores: blocking=5, detection=5, per_pl=5-0-0-0, threshold=5) - (Outbound Scores: blocking=0, detection=0, per_pl=0-0-0-0, threshold=4) - (SQLI=0, XSS=0, RFI=0, LFI=0, RCE=5, PHPI=0, HTTP=0, SESS=0, COMBINED_SCORE=5)
-
[Mon Feb 26 20:14:58.290634 2024] [:error] [pid 32480] [client <IP_ADDRESS>:56492] [client <IP_ADDRESS>] ModSecurity: Access denied with code 403 (phase 2). Pattern match "(?i)(?:^|b[\\"'\\\\)\\\\[-\\\\x5c]*(?:(?:(?:\\\\|\\\\||&&)[\\\\s\\\\v]*)?\\\\$[!#\\\\(\\\\*\\\\-0-9\\\\?-@_a-\\\\{]*)?\\\\x5c?u[\\"'\\\\)\\\\[-\\\\x5c]*(?:(?:(?:\\\\|\\\\||&&)[\\\\s\\\\v]*)?\\\\$[!#\\\\(\\\\*\\\\-0-9\\\\?-@_a-\\\\{]*)?\\\\x5c?s[\\"'\\\\)\\\\[-\\\\x5c]*(?:(?:(?:\\\\|\\\\||&&)[\\\\s\\\\v]*)?\\\\$[!#\\\\(\\\\*\\\\-0-9 ..." at REQUEST_COOKIES:fpestid. [file "crs/rules/REQUEST-932-APPLICATION-ATTACK-RCE.conf"] [line "498"] [id "932260"] [msg "Remote Command Execution: Direct Unix Command Execution"] [data "Matched Data: SUDo found within REQUEST_COOKIES:fpestid: SUDoLongRandomString"] [severity "CRITICAL"] [ver "OWASP_CRS/4.0.1-dev"] [tag "application-multi"] [tag "language-shell"] [tag "platform-unix"] [tag "attack-rce"] [tag "paranoia-level/1"] [tag "OWASP_CRS"] [tag "capec/1000/152/248/88"] [tag "PCI/6.5.2"] [hostname "www.example.com"] [uri "/abc/"] [unique_id "Zd1ForZabQ9-ap78Ly4PHQAAAAs"], referer: https://www.example.com/xyz/

932236 - PL2 on 'df', 'fd', in ARGS (uniqid, uuid, or hex type values)
curl -H "x-format-output: txt-matched-rules" -H "x-crs-paranoia-level: 2" "https://sandbox.coreruleset.org/get?abc=dfc987c2-72e2-4a8e-ad98-e0bf1bc3a01c"
932236 PL2 Remote Command Execution: Unix Command Injection (command without evasion)
949110 PL1 Inbound Anomaly Score Exceeded (Total Score: 5)
980170 PL1 Anomaly Scores: (Inbound Scores: blocking=5, detection=5, per_pl=0-5-0-0, threshold=5) - (Outbound Scores: blocking=0, detection=0, per_pl=0-0-0-0, threshold=4) - (SQLI=0, XSS=0, RFI=0, LFI=0, RCE=5, PHPI=0, HTTP=0, SESS=0, COMBINED_SCORE=5)
-
[Sat Mar 23 18:36:57.137426 2024] [:error] [pid 30042] [client <IP_ADDRESS>:53294] [client <IP_ADDRESS>] ModSecurity: Access denied with code 403 (phase 2). Pattern match "(?i)(?:^|b[\\"'\\\\)\\\\[\\\\x5c]*(?:(?:(?:\\\\|\\\\||&&)[\\\\s\\\\v]*)?\\\\$[!#\\\\(\\\\*\\\\-0-9\\\\?@_a-\\\\{]*)?\\\\x5c?u[\\"'\\\\)\\\\[\\\\x5c]*(?:(?:(?:\\\\|\\\\||&&)[\\\\s\\\\v]*)?\\\\$[!#\\\\(\\\\*\\\\-0-9\\\\?@_a-\\\\{]*)?\\\\x5c?s[\\"'\\\\)\\\\[\\\\x5c]*(?:(?:(?:\\\\|\\\\||&&)[\\\\s\\\\v]*)?\\\\$[!#\\\\(\\\\*\\\\-0-9\\\\?@_ ..." at ARGS:abc. [file "crs/rules/REQUEST-932-APPLICATION-ATTACK-RCE.conf"] [line "1368"] [id "932236"] [msg "Remote Command Execution: Unix Command Injection (command without evasion)"] [data "Matched Data: df found within ARGS:abc: dfc987c2-72e2-4a8e-ad98-e0bf1bc3a01c"] [severity "CRITICAL"] [ver "OWASP_CRS/4.0.1-dev"] [tag "application-multi"] [tag "language-shell"] [tag "platform-unix"] [tag "attack-rce"] [tag "paranoia-level/2"] [tag "OWASP_CRS"] [tag "capec/1000/152/248/88"] [tag "PCI/6.5.2"] [hostname "www.example.com"] [uri "/xyz/"] [unique_id "Zf9nmYvL5W2kWBKkT1JMpQAAAAI"]

and REQUEST_COOKIES (ids, hex values, etc)
curl -H "x-format-output: txt-matched-rules" -H "x-crs-paranoia-level: 2" --cookie "abc=fd01bfcfdbe02" https://sandbox.coreruleset.org/
932236 PL2 Remote Command Execution: Unix Command Injection (command without evasion)
949110 PL1 Inbound Anomaly Score Exceeded (Total Score: 5)
980170 PL1 Anomaly Scores: (Inbound Scores: blocking=5, detection=5, per_pl=0-5-0-0, threshold=5) - (Outbound Scores: blocking=0, detection=0, per_pl=0-0-0-0, threshold=4) - (SQLI=0, XSS=0, RFI=0, LFI=0, RCE=5, PHPI=0, HTTP=0, SESS=0, COMBINED_SCORE=5)
-
[Sat Mar 23 06:18:31.906424 2024] [:error] [pid 208032] [client <IP_ADDRESS>:36324] [client <IP_ADDRESS>] ModSecurity: Access denied with code 403 (phase 2). Pattern match "(?i)(?:^|b[\\"'\\\\)\\\\[\\\\x5c]*(?:(?:(?:\\\\|\\\\||&&)[\\\\s\\\\v]*)?\\\\$[!#\\\\(\\\\*\\\\-0-9\\\\?@_a-\\\\{]*)?\\\\x5c?u[\\"'\\\\)\\\\[\\\\x5c]*(?:(?:(?:\\\\|\\\\||&&)[\\\\s\\\\v]*)?\\\\$[!#\\\\(\\\\*\\\\-0-9\\\\?@_a-\\\\{]*)?\\\\x5c?s[\\"'\\\\)\\\\[\\\\x5c]*(?:(?:(?:\\\\|\\\\||&&)[\\\\s\\\\v]*)?\\\\$[!#\\\\(\\\\*\\\\-0-9\\\\?@_ ..." at REQUEST_COOKIES:abc. [file "crs/rules/REQUEST-932-APPLICATION-ATTACK-RCE.conf"] [line "1368"] [id "932236"] [msg "Remote Command Execution: Unix Command Injection (command without evasion)"] [data "Matched Data: fd found within REQUEST_COOKIES:abc: fd01bfcfdbe02"] [severity "CRITICAL"] [ver "OWASP_CRS/4.0.1-dev"] [tag "application-multi"] [tag "language-shell"] [tag "platform-unix"] [tag "attack-rce"] [tag "paranoia-level/2"] [tag "OWASP_CRS"] [tag "capec/1000/152/248/88"] [tag "PCI/6.5.2"] [hostname "www.example.com"] [uri "/xyz/"] [unique_id "Zf66hyl54eZv1SgtgUHGRQAAAA0"], referer: https://www.example.com/

932239 - PL2 for REQUEST_HEADERS:Referer
curl -H "x-format-output: txt-matched-rules" -H "x-crs-paranoia-level: 2" --referer "https://sandbox.coreruleset.org/get?abc=dfc987c2-72e2-4a8e-ad98-e0bf1bc3a01c" https://sandbox.coreruleset.org/
932239 PL2 Remote Command Execution: Unix Command Injection found in user-agent or referer header
949110 PL1 Inbound Anomaly Score Exceeded (Total Score: 5)
980170 PL1 Anomaly Scores: (Inbound Scores: blocking=5, detection=5, per_pl=0-5-0-0, threshold=5) - (Outbound Scores: blocking=0, detection=0, per_pl=0-0-0-0, threshold=4) - (SQLI=0, XSS=0, RFI=0, LFI=0, RCE=5, PHPI=0, HTTP=0, SESS=0, COMBINED_SCORE=5)
-
[Sat Mar 23 19:55:03.716728 2024] [:error] [pid 6278] [client <IP_ADDRESS>:38730] [client <IP_ADDRESS>] ModSecurity: Access denied with code 403 (phase 1). Pattern match "(?i)(?:^|b[\\"'\\\\)\\\\[\\\\x5c]*(?:(?:(?:\\\\|\\\\||&&)[\\\\s\\\\v]*)?\\\\$[!#\\\\(\\\\*\\\\-0-9\\\\?@_a-\\\\{]*)?\\\\x5c?u[\\"'\\\\)\\\\[\\\\x5c]*(?:(?:(?:\\\\|\\\\||&&)[\\\\s\\\\v]*)?\\\\$[!#\\\\(\\\\*\\\\-0-9\\\\?@_a-\\\\{]*)?\\\\x5c?s[\\"'\\\\)\\\\[\\\\x5c]*(?:(?:(?:\\\\|\\\\||&&)[\\\\s\\\\v]*)?\\\\$[!#\\\\(\\\\*\\\\-0-9\\\\?@_ ..." at REQUEST_HEADERS:Referer. [file "crs/rules/REQUEST-932-APPLICATION-ATTACK-RCE.conf"] [line "1430"] [id "932239"] [msg "Remote Command Execution: Unix Command Injection found in user-agent or referer header"] [data "Matched Data: =fd found within REQUEST_HEADERS:Referer: https://www.example.com/xyz/?abc=dfc987c2-72e2-4a8e-ad98-e0bf1bc3a01c"] [severity "CRITICAL"] [ver "OWASP_CRS/4.0.1-dev"] [tag "application-multi"] [tag "language-shell"] [tag "platform-unix"] [tag "attack-rce"] [tag "paranoia-level/2"] [tag "OWASP_CRS"] [tag "capec/1000/152/248/88"] [tag "PCI/6.5.2"] [hostname "www.example.com"] [uri "/news/"] [unique_id "Zf9556f1ZVkt2o@NOscW7gAAABc"], referer: https://www.example.com/xyz/

Your Environment

CRS version (e.g., v3.3.4): 4.0.1-dev
Paranoia level setting (e.g. PL1) : PL1+ (can change dynamically based on geolocation, rbl scores, etc)
ModSecurity version (e.g., 2.9.6): 2.9.7-1+b1
Web Server and version or cloud provider / CDN (e.g., Apache httpd 2.4.54): Apache 2.4.57-2
Operating System and version: Debian 12

Confirmation
[X] I have removed any personal data (email addresses, IP addresses,
passwords, domain names) from any logs posted.

Thank you very much for an excellent bug report. And sorry for the hassles.
You are not on the full CRS 4.0.0 release, but I've looked up the 4 examples they gave and they are still set as reported by you.
So just make sure we're on the same page, you suggest the following:
./regex-assembly/include/unix-shell-upto3.ra

df -> df@
fd -> fd@
grc -> grc@

./regex-assembly/include/unix-shell-4andup.ra

sudo -> sudo@  sudoedit, sudoreplay, etc. (?)

But this is part of a larger problem for you.
You happen to use grc as a cookie prefix - well, that's just bad luck. But you also encounter FPs with uuids with the 2- and 3-letter combinations in unix-shell-upto3.ra, so you see a general problem there.
Most of the commands in unix-shell-upto3.ra come with the @ macro extension, but this was done based on English language use, but with uuid in mind as far as I can see.
This is substantial feedback and while the suggestions above are easy to implement, the general extension of all the commands in unix-shell-upto3.ra takes some thinking.

I don't have any suggestions for fd and grc at this time since I'm not really sure what they were originally intended to match on. These could be exact matches or partial prefixes for a whole suites of utilities behind it, covering things like fdisk, fd(u)mount, fdfind, etc. grc could be the generic colouriser at https://github.com/garabik/grc. If so, and this pattern is necessary, then it may be worth splitting those up into grc@ and grcat. I tried to find changelogs and checkins for these but didn't notice anything. If 'df' is meant to match on the actual df command then changing it to 'df@' may be prudent.
These are all PL2, meaning increased scrutiny and potentially increased false positives as well. I think most people understand that and that's fine. I don't want to presume anything or recommend changes that would drastically weaken the higher paranoia levels. I've already solved my issue with the grcxyz_ cookie prefix issue, and can make other changes to reduce the PL2 usage for suspicious traffic. I just thought this would be worth mentioning given what I've been seeing and the potential for 'df' and 'fd' to match on hex or UUID type values that may be on cookies or parameters and their related usage in the Referer header.
sudo is a PL1 so I do think that's worth considering. On Debian 12 the sudo package has 5 binaries that start with 'sudo'. If it was necessary to match on most or all of them then 'sudo' could be broken out into: sudo@, sudoedit, sudoreplay, sudo_logsrvd, and sudo_sendlog. sudoedit is a symlink to sudo. The longer binary names seem far less likely to hit on random strings like the SUDoXyZ... fpestid cookie I ran across the other day so they may not need the @. Who knows, maybe it's already very unlikely for someone to run across a cookie or other random value that starts with sudo. But generally speaking if we know or can make an educated guess on what the original intent was then maybe it's worth being more precise with some of them, especially the shorter strings.

I've taken a crack at trying to solve this issue, and I don't think adding @ will be able to fully solve this false positive. It'll make it less frequent and therefore less painful, but it won't fundamentally solve the false positives with session cookies, tokens, UUIDs and such. I tried to at least take care of false positives with UUIDs by adding @ to any command that solely consists of characters between 0-9 a-f, but some commands like df can be executed without any arguments so that will lead to false negatives.
The real problem here is that invalid commands are being matched when neither @ or ~ is specified, if we stop matching invalid commands then that should fix all false positives with session cookies, tokens, and UUIDs while still blocking the execution of commands with no arguments. I've also taken a crack at trying to solve the invalid matching of commands, the closest I got was by adding a negated set at the end of each command sudo[^a-z0-9\-], however I don't think doing that will be very readable or good for performance. I'm not very experienced with the CRS toolchain, so maybe someone more knowledgeable than me may have a better solution.
Either way, it will take some time to find all the commands that each entry in the unix-shell-* was intended to match, and some commands will likely be missed (Simply due to human error) so a false negative may be unavoidable.

I am not very familiar with CRS, but wouldn't it be enough to check whether there is at least one alphabetic or numeric characters before or after the match and if this is the case than this can not be a valid unix command so reject it.
There seems to be an equivalent discussion about the php functions, which sounds very similar: https://github.com/coreruleset/coreruleset/pull/3273#issuecomment-1673961872

Thanks @EsadCetiner for trying. Indeed, this is only one of several reports of issues with the shell injection rules and we need to solve this on a conceptual level and not case by case.
@niklasweimann That's not a bad idea. @EsadCetiner do you want to give it a try? I currently have a few other things to finish.

@niklasweimann Sorry for the late reply
If I understand you correctly, I think I've already tried that with a negated set without much success. I was able to prevent matches of invalid commands, but it didn't block the execution of commands without arguments.

There seems to be an equivalent discussion about the php functions, which sounds very similar: https://github.com/coreruleset/coreruleset/pull/3273#issuecomment-1673961872

we're already excluding commands at PL-1 that match with common english words, but thank you for the suggestion.
@theseion
I was able to come up with this after a bit more thinking which blocks execution of commands without arguments while also preventing invalid matches:
sudo(?:$|[^a-z0-9])

However I have to add this to end of all commands, and I don't know how bad the performance will be since I'm using a non capturing group.
Although in the past 3 weeks I did find all of the commands with 5 characters or less that don't require arguments and added @ to them. I tried to find all of the commands that they were originally intended to match, I found a fair few but I doubt I've found them all.

Thanks @EsadCetiner. I'll get back to the RCE issue once I'm done with a couple of other things. If anybody else want's to take a crack at the Unix RCE rules in the mean time, I'll be happy to give some pointers.

If nobody else has any other ideas, I'm going to open a PR that prevents invalid matches on commands with 5 characters or less. I'm not sure how ideal this solution is, but it does work.

Go for it, I think it's a good idea. Be careful though, @ and ~ will add suffixes to some commands, so an expression may end up looking like this:
perf[\s<>&|)](?:$|[^a-z0-9])

This is probably not what you want. Your solution needs to take the use of these suffixes into account. Maybe they can be dropped, be applied conditionally, .... Ping me if you have questions.

@theseion wdym by conditionals, I thought they weren't allowed because of ReDoS risk?

Ah 😄. I wasn't talking about regex conditionals. I mean conditionally in the sense that the crs-toolchain could, theoretically, be used to append a suffix conditionally. The condition would then be part of the regex-assembly macro language.

Well, as I've said elsewhere, I think we need to solve this with an altered approach, which will probably require some changes to the setup of the way the regular expressions are generated for the 932xxx rules, and / or changes to the crs-toolchain.
For example, we could extend the cmdline processor to append a suffix (which could be user defined). Imagine something like this:
##!> cmdline unix (?:$|[^a-z0-9])
  <list of commands>
##!<

Then the crs-toolchain could generate the regular expression for some command cmd by first appending the supplied suffix, followed by expansion of @ or ~. So cmd@ would become cmd[\s<>&|)](?:$|[^a-z0-9]).
There are two things to consider here:

For 932260 we don't actually use the cmdline processor, but replace @ and ~ as part of the include-except processor
It probably makes more sense to configure the suffix in toolchain.yaml instead of allowing it to be specified as part of the cmdline processor.

There are probably other wise to go about this, I'm just trying to give you some idea where this could go. I know this might all seem a bit much, I'll try to put more energy into this soon.

@theseion

For example, we could extend the cmdline processor to append a suffix (which could be user defined). Imagine something like this:

I thought about this too, but I'm not sure if there's a way to specify a default suffix (i.e when neither @ or ~ is specified, append (?:$|[^a-z0-9]) to the end of a command), just adding (?:$|[^a-z0-9]) to all commands causes false negatives and tests to fail as mentioned earlier.
I don't know if it's a good idea to get rid of @, append(?:$|[^a-z0-9]) to all commands by default and keep ~ for when we want to match permutations of a commands. It would be clean and the performance shouldn't suffer if there's nothing else that I'm missing.

I think you need the semantics of @, i.e., I would probably merge your suffix with the definition for @. We have to be pretty careful how we do this though, because adding a suffix to every command, without being able to group, will lead to an explosion in the length of the regular expressions. However, the generator does a pretty good job of reducing expressions, so you could simply give it a try by creating an example file with just a couple of commands and then passing that to the toolchain: crs-toolchain regex generate - < some_file.ra. Then you could estimate how big the effect on the length would be.

@theseion

I think you need the semantics of @, i.e., I would probably merge your suffix with the definition for @.

hm... so then we'd add @ to commands that consists of 5 chars or less? that's where most of the false positives are so that should be good enough, but it won't fully prevent invalid matches of all commands.

We have to be pretty careful how we do this though,

Agreed, I just don't see many good options. A suffix has to be added to the end of at least most commands to prevent invalid matches, unless I'm missing something.

because adding a suffix to every command, without being able to group, will lead to an explosion in the length of the regular expressions.

Yeah I saw that based on the work I've done so far, the more I look at this the more that looks unavoidable.
I think you've confused me more 😆, I can open a PR with the modified definition of @, add it to 5 characters or less if it will be easier to work like that or if it's a good enough solution.

Sure, let's try that.


TKET does not respect uni-directional layout

At the moment, mapped circuits produced by TKET to architectures the are not bidirectional may contain invalid gates.
An example of this can be observed for 3-qubit DJ mapped to OQC Lucy with TKET using the Graph Placement, which results in
// Benchmark was created by MQT Bench on 2022-12-14
// For more information about MQT Bench, please visit https://www.cda.cit.tum.de/mqtbench/
// MQT Bench version: 0.2.2
// TKET version: 1.9.1
// Used Gate Set: ['rz', 'sx', 'x', 'ecr', 'measure']
// Coupling List: [[0, 1], [0, 7], [1, 2], [2, 3], [7, 6], [6, 5], [4, 3], [4, 5]]

OPENQASM 2.0;
include "qelib1.inc";
opaque ecr q0,q1;

qreg node[3];
creg c[2];
sx node[0];
rz(0.5*pi) node[1];
sx node[2];
rz(2.5*pi) node[0];
sx node[1];
rz(2.5*pi) node[2];
sx node[0];
rz(0.5*pi) node[1];
sx node[2];
rz(1.5*pi) node[0];
sx node[1];
rz(1.5*pi) node[2];
x node[0];
sx node[1];
x node[2];
rz(3.5*pi) node[0];
rz(3.5*pi) node[2];
ecr node[0],node[1];
sx node[0];
sx node[1];
rz(0.5*pi) node[0];
sx node[1];
ecr node[2],node[1];  # <--- invalid
rz(1.0*pi) node[1];
sx node[2];
rz(0.5*pi) node[2];
barrier node[0],node[2],node[1];
measure node[0] -> c[0];
measure node[2] -> c[1];

I marked the invalid gate. that direction should not be possible according to the coupling map.
I suspect this has something to do with the way the TKET Architecture is constructed.
The architecture is constructed just fine and only contains uni-directional links. Must be something else.

From the documentation of the RoutingPass:

Most notably: Edge direction is ignored


BUG - Can't change networks a second time

Bug: Unable to set network a second time.
Steps:

Set a network - works
Try to change/set another - it fails to change, retains initial setting
Can set a second network if docker container is deleted - suspect that something is being persisted there.

Expect to be able to set connection several times:

I am also experiencing this issue. The docs don't indicate whether there is an endpoint for disconnecting/reconnecting from a network. Its really important to be able to associate with different networks without completely killing the service.

I noticed a factor that can contribute to this.  Over the course of testing, I've restarted the container many times and often found it would connect at first but subsequent attempts wouldn't work until I rebooted the device.  It turns out the hardware device name had been incremented, so instead of phy#0 I had phy#3, thus the uap0 interface could not be created on top of it.  Check if yours has changed with the iw dev command.
As a workaround, I added a parameter to the wificfg.json file that lets me specify the device name.  I'm also using a shell script to update this value prior to starting the container.
diff --git a/iotwifi/commands.go b/iotwifi/commands.go
index 88fe8c7..ebd085c 100644
--- a/iotwifi/commands.go
+++ b/iotwifi/commands.go
@@ -36,7 +36,7 @@ func (c *Command) UpApInterface() {

 // AddApInterface adds the AP interface.
 func (c *Command) AddApInterface() {
-       cmd := exec.Command("iw", "phy", "phy0", "interface", "add", "uap0", "type", "__ap")
+       cmd := exec.Command("iw", "phy", c.SetupCfg.HostApdCfg.Phy, "interface", "add", "uap0", "type", "__ap")
        cmd.Start()
        cmd.Wait()
 }
diff --git a/iotwifi/types.go b/iotwifi/types.go
index b1074cb..04db1c9 100644
--- a/iotwifi/types.go
+++ b/iotwifi/types.go
@@ -20,6 +20,7 @@ type HostApdCfg struct {
        WpaPassphrase string `json:"wpa_passphrase"` // wpa_passphrase=iotwifipass
        Channel       string `json:"channel"`        //  channel=6
        Ip            string `json:"ip"`             // <IP_ADDRESS>
+       Phy           string `json:"phy"`            // phy=phy0
 }

 // WpaSupplicantCfg configures wpa_supplicant and is used by SetupCfg

This is a kludge and I don't recommend doing this, which is why I'm not submitting it as a pull request, but it may be helpful to someone.  Ideally, the code would detect the current device name but I'm not sure what would be the best way to handle the case where multiple wireless devices are present.


Error: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /src/node_modules/snappy/build/Release/binding.node)

I try to build a dockerfile with your lib, it doesn't work :+1:
FROM node:latest
COPY package.json /src/package.json
RUN cd /src; npm install
COPY . /src
CMD node /src/index.js
Error: /usr/lib/x86_64-linux-gnu/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /src/node_modules/snappy/build/Release/binding.node)
I tried this solution : http://askubuntu.com/questions/575505/glibcxx-3-4-20-not-found-how-to-fix-this-error
but it just doesn't work.
What do I have to do to make this work inside a docker ?
Thanks for your anwser

Its a snappy module compilation issues. Try 2.6.0 which makes snappy an optional dependancy.


EAS build --local  takes 30+ mins.

Build/Submit details page URL
it's local build
Summary
EAS build --local  takes 30+ mins.  Looking into the build log task bundleReleaseJsAndAssets cost around 12 mins.
Related log:
13:21:24 [RUN_GRADLEW] > Task :app:bundleReleaseJsAndAssets
13:33:02 [RUN_GRADLEW] Execution optimizations have been disabled for task ':app:bundleReleaseJsAndAssets' to ensure correctness due to the following reasons:
13:33:02 [RUN_GRADLEW]   - Gradle detected a problem with the following location: '/opt/user/dev/eas_workingdir/build/expo-proj'. Reason: Task ':app:bundleReleaseJsAndAssets' uses this output of task ':expo-application:compileReleaseAidl' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.3.3/userguide/validation_problems.html#implicit_dependency for more details about this problem.
Managed or bare?
managed
Environment
expo-env-info 1.0.4 environment info:
System:
OS: Linux 3.10 CentOS Linux 7 (Core)
Shell: 4.2.46 - /bin/bash
Binaries:
Node: 16.14.2 - ~/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/16.14.2/bin/node
Yarn: 1.22.18 - /opt/nick/node-v17.9.0-linux-x64/bin/yarn
npm: 8.5.0 - ~/tools/jenkins.plugins.nodejs.tools.NodeJSInstallation/16.14.2/bin/npm
npmPackages:
expo: ~43.0.5 => 43.0.5
react: 17.0.1 => 17.0.1
react-dom: 17.0.1 => 17.0.1
react-native: 0.64.3 => 0.64.3
react-native-web: 0.17.1 => 0.17.1
Expo Workflow: managed
================
Expo doctor log from build log:
13:18:15 [RUN_EXPO_DOCTOR] Running "expo doctor"
13:18:17 [RUN_EXPO_DOCTOR] - Finding all copies of expo-modules-autolinking
13:18:18 [RUN_EXPO_DOCTOR] ��� Failed to find dependency tree for expo-modules-autolinking: npm exited with non-zero code: 1
13:18:18 [RUN_EXPO_DOCTOR] [01:18:18] npm exited with non-zero code: 1
13:18:18 [RUN_EXPO_DOCTOR] [01:18:18] Error: npm exited with non-zero code: 1
13:18:18 [RUN_EXPO_DOCTOR]     at ChildProcess.completionListener (/opt/nick/dev/npm_cache/_npx/2773/lib/node_modules/eas-cli-local-build-plugin/node_modules/expo-cli/node_modules/@expo/spawn-async/src/spawnAsync.ts:65:13)
13:18:18 [RUN_EXPO_DOCTOR]     at Object.onceWrapper (events.js:520:26)
13:18:18 [RUN_EXPO_DOCTOR]     at ChildProcess.emit (events.js:400:28)
13:18:18 [RUN_EXPO_DOCTOR]     at maybeClose (internal/child_process.js:1058:16)
13:18:18 [RUN_EXPO_DOCTOR]     at Process.ChildProcess._handle.onexit (internal/child_process.js:293:5)
13:18:18 [RUN_EXPO_DOCTOR]     ...
13:18:18 [RUN_EXPO_DOCTOR]     at spawnAsync (/opt/nick/dev/npm_cache/_npx/2773/lib/node_modules/eas-cli-local-build-plugin/node_modules/expo-cli/node_modules/@expo/spawn-async/src/spawnAsync.ts:26:19)
13:18:18 [RUN_EXPO_DOCTOR]     at explainAsync (/opt/nick/dev/npm_cache/_npx/2773/lib/node_modules/eas-cli-local-build-plugin/node_modules/expo-cli/src/commands/info/doctor/depedencies/explain.ts:24:30)
13:18:18 [RUN_EXPO_DOCTOR]     at warnAboutDeepDependenciesAsync (/opt/nick/dev/npm_cache/_npx/2773/lib/node_modules/eas-cli-local-build-plugin/node_modules/expo-cli/src/commands/info/doctor/depedencies/explain.ts:43:30)
13:18:18 [RUN_EXPO_DOCTOR]     at validateSupportPackagesAsync (/opt/nick/dev/npm_cache/_npx/2773/lib/node_modules/eas-cli-local-build-plugin/node_modules/expo-cli/src/commands/info/doctor/doctorAsync.ts:28:13)
13:18:18 [RUN_EXPO_DOCTOR]     at actionAsync (/opt/nick/dev/npm_cache/_npx/2773/lib/node_modules/eas-cli-local-build-plugin/node_modules/expo-cli/src/commands/info/doctor/doctorAsync.ts:41:5)
13:18:19 [RUN_EXPO_DOCTOR] Command "expo doctor" failed.
Error output

Reproducible demo or steps to reproduce from a blank project
not available now. I'll try to create one later.

Thanks @wkozyra95, We did use FontAwesome in our Proj. I will see if remove it can help with the build time :)


terminate called after throwing an instance of 'mperf::MperfError'

./cpu_pmu_transpose
1 1 INSTRUCTIONS
the warm iter 0, and time use 19.946565
the warm iter 1, and time use 13.541801
the warm iter 2, and time use 13.487423
the warm iter 3, and time use 13.471814
the warm iter 4, and time use 13.482091
terminate called after throwing an instance of 'mperf::MperfError'
what():  Failed to get a file descriptor for INSTRUCTIONS

请问是android平台吗？这种是event系统调用的访问权限问题，可以尝试
echo -1 > /proc/sys/kernel/perf_event_paranoid

或者检查一下/sys/bus/event_source/devices目录下有没有类似armv8_pmuv3这样的cpu pmu文件夹，因为有些嵌入式开发板上面就没有cpu pmu，所以自然就fail了


V0.4 Milestone

Coverage increased (+1.01%) to 70.95% when pulling 826ec60a0661124431532627494c15313dc7f10e on V0.4 into 66464448d4c744de7c240b591b7b0ed56046f426 on master.


Missing Logout Mechanism

JWT logout option seems to be missing in this, could you please introduce it here.
I tried some guess work by removing local storage items associated with JWT authentication e.g. token, exp, user. But somehow they gets refreshed in subsequent requests through backend because of this unable to manage logout functionality in JWT.
In case if I am missing here any step then please guide me OR if you guys are currently implementing JWT Logout feature then please let me know when may I expect next release with it.

Since JWT is a stateless authentication mechanism, logging the user out is simply a matter of removing any reference to their token. If you have saved their token in local storage, then it is necessary to remove it from there, but it also may be necessary to deal with any kind of caching of the token that may have happened. Do you have some kind of header caching happening for your $http requests?

Thanks Ryan for your quick response & highlighting hotspot of this issue.
After spending quality time in debugging our SSO implementation layer found
it was the main culprit that was passing new token back in case of
unauthorized state which in turn stored back to local storage after wiping
it out in subsequent request.
On 24-Apr-2017 10:30 pm, "Ryan Chenkie"<EMAIL_ADDRESS>wrote:

Since JWT is a stateless authentication mechanism, logging the user out is
simply a matter of removing any reference to their token. If you have saved
their token in local storage, then it is necessary to remove it from there,
but it also may be necessary to deal with any kind of caching of the token
that may have happened. Do you have some kind of header caching happening
for your $http requests?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/auth0/angular-jwt/issues/149#issuecomment-296744872,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AOMenzfYXZbFQUdvpF1WrLhlktTBTytFks5rzNVGgaJpZM4NF_Yw
.

You also need to set $rootScope.isAuthenticated to false.

but friend,
how am i suppose to do it?
i'm stuck with this...
`
import { Injectable } from '@angular/core';
import { Http, Headers, RequestOptions } from '@angular/http';
import 'rxjs/add/operator/map';
//import { tokenNotExpired } from 'angular2-jwt';
import { JwtHelperService } from '@auth0/angular-jwt';
import { environment } from '../../environments/environment';
@Injectable({
providedIn: 'root'
})
export class AuthService {
// domain = ""; // Production
domain = environment.domain;
authToken;
user;
options;
constructor(
private http: Http,
public jwtHelper: JwtHelperService
) { }
// Function to create headers, add token, to be used in HTTP requests
createAuthenticationHeaders() {
this.loadToken(); // Get token so it can be attached to headers
// Headers configuration options
this.options = new RequestOptions({
headers: new Headers({
'Content-Type': 'application/json', // Format set to JSON
'authorization': this.authToken // Attach token
})
});
}
// Function to get token from client local storage
loadToken() {
this.authToken = localStorage.getItem('token');; // Get token and asssign to variable to be used elsewhere
}
// Function to login user
login(user) {
return this.http.post(this.domain + 'authentication/login', user).map(res => res.json());
}
// Function to store user's data in client local storage
storeUserData(token, user) {
localStorage.setItem('token', token); // Set token in local storage
localStorage.setItem('user', JSON.stringify(user)); // Set user in local storage as string
this.authToken = token; // Assign token to be used elsewhere
this.user = user; // Set user to be used elsewhere
}
// Function to logout
logout() {
this.authToken = null; // Set token to null
this.user = null; // Set user to null
localStorage.clear(); // Clear local storage
}
// Function to check if user is logged in
loggedIn() {
return this.jwtHelper.isTokenExpired()
//return tokenNotExpired();
//return false;
//this.jwtHelper.isTokenExpired()
}
}
`


When I ran ''sudo python3 setup.py install'', error occurred "ModuleNotFoundError: No module named 'torch'"

When I run ''sudo python3 setup.py install'' ,error occurred

it shows I don't have torch module, but the picture shows I have installed the torch

When I run ''sudo python3 setup.py install'' ,error occurred  it shows I don't have torch module, but the picture shows I have installed the torch

you can try again with the command: "sudo python setup.py install"

When I run ''sudo python3 setup.py install'' ,error occurred  it shows I don't have torch module, but the picture shows I have installed the torch

you can try again with the command: "sudo python setup.py install"

I try again with the command but a weird error is reported. I have installed setuptools

When I run ''sudo python3 setup.py install'' ,error occurred  it shows I don't have torch module, but the picture shows I have installed the torch

you can try again with the command: "sudo python setup.py install"

I try again with the command but a weird error is reported. I have installed setuptools

I also encountered the same error, have you resolved it? I have tested torch.

 Tôi đã cài đặt công cụ thiết lập

I have installed the environment for this NeRF-SLAM algorithm many times without encountering any errors like yours. You can follow the steps I have previously performed as follows:

Step 1: conda create --name NeRF-SLAM python=3.9
Step 2: git clone https://github.com/jrpowers/NeRF-SLAM.git --recurse-submodules
Next, you should follow the subsequent steps as guided in the readme file.
I will continue to support you if you need it. Good luck!

I also encountered the same error, have you resolved it?

I also encountered the same error, but I didn't find a useful answer. I tried "python3 setup.py install", but I didn't have permission. So, I added write permission for path /usr/lib/python3.8/site-packages/, then tried "python3 setup.py install" again. At last, it installed successfull.


chore(ava): update lint and test

chore(codecov): switch to use codecov

Current coverage is 100.00%

Branch #3 has no coverage reports uploaded yet.

No diff could be generated. No reports for master found.

Powered by Codecov. Updated on successful CI builds.


No data for endpoint /wp-json/posts/33

I have all acf datas in /wp-json/posts?type=actualite (archive) but not in /wp-json/posts/33 (singular)
I'm using ACF Pro. Any idea ? Thanks !

Sorry you're having trouble with the plugin!
I'm not able to reproduce this issue, although I'm not using ACF Pro which is probably why.
It'll be a few days before I can spend any more time on it, but I'll do a more thorough test of the plugin with ACF Pro to see if I can find the cause of the problem you're having.

@will83 I've now tested this with ACF Pro and haven't been able to reproduce this issue. Can you share any updated progress you've made?
If you're still struggling with it can you share an export of your ACF field configuration?

Closing this due to inactivity. @will83, please comment again if you're still struggling with this.


Allow vendoring multiple Cargo.locks

To give people the option of maintaining a single vendor directory across multiple crates/workspaces.

I'm not sure this behaves correctly with --git. If two crates depend on the same version of a package, but the two dependencies aren't identical (if one or both are fetched via git), you'll get an error like
error: checksum for `autocfg v0.1.4` changed between lock files

this could be indicative of a few possible errors:

    * the lock file is corrupt
    * a replacement source in use (e.g., a mirror) returned a different checksum
    * the source itself may be corrupt in one way or another

unable to verify that `autocfg v0.1.4` is the same as when the lockfile was generated

This isn't unique to this PR though, for example the same behavior can be triggered using workspaces.

I'm sorry but I no longer have the time to maintain this repository. I don't have time to review this but if others are interested in maintaining this command I can transfer ownership!

@sebastianblunt - I've taken over this project from Alex. I'm happy to review your PR, but it looks like you have an outstanding question regarding handling the case when there are conflicting sources for a crate version.
It would be great if you could give a better error message in this case, and by better I mean something that will make it easier for a user to solve the problem. For example, show which Cargo.lock files contained which sources for the conflicted crate. Further, if all the sources are identical then the error should explain the other possibilities - e.g. corruption.
Anyway, let me know when you're ready for me to review your changes and I'll have a look.

Hi Chris, thanks for taking over.
So the error I quoted is not actually given by cargo-local-registry, it's given afterwards by cargo when trying to compile. cargo-local-registry currently gives no error at all on conflicting packages.
Multiple conflicting packages can already happen before my PR, my PR adds another avenue from which conflicting packages can occur (syncing two different Cargo.locks using different sources.)
Up to you whether you want to go ahead and review my changes, or you'd rather wait for a separate PR to add a check and warnings for conflicting packages.

@sebastianblunt - yes I understand that cargo-local-registry doesn't detect the conflict. I think it should, although I get that you might not want to implement that checking to get your PR in.
Could you explain how conflicting packages can already happen without this PR? I'm sure you're right, just so that we have an example to make the discussion easier. Perhaps something to do with multiple registries. So a single .lock file declares two dependencies A and B where dependency A from registry 1 pulls in a transitive dependency T from registry 1 and and dependency B from registry 2 pulls in a transitive dependency T from registry 2. Is that what you mean?
In your comment on the 9th of June, you asked "cargo-vendor seems to have a check for this ...  But from your comment yesterday, I'm not so sure. Would you be prepared to add one? If not, we can still put this PR in, there's just more potential for user confusion.
In terms of long term vision, I wonder whether the output registry directory should have subdirectories when there are multiple source (different registries, git repos etc.) and then the output from running cargo-local-registry would output a .cargo/config file that mapped the each of the source registries to the appropriate subdirectory. Perhaps then this gets around the whole problem with crate conflicts. I wonder what your PR would look like doing that? Is that something you'd be prepared to implement?

I wouldn't mind implementing the check for conflicting packages, it shouldn't be too hard.
Here's one way to trigger it right now:
./Cargo.toml:
[workspace]
members = [
	"bar",
	"foo",
]

./foo/Cargo.toml:
[package]
name = "foo"
version = "0.1.0"

[dependencies]
autocfg = "0.1.5"

./bar/Cargo.toml:
[package]
name = "bar"
version = "0.1.0"

[dependencies]
autocfg = { git = "https://github.com/cuviper/autocfg/", rev = "81ea9f3120f20d684fb97fe90f2848f137519dfc" }

and then fn main() {} in foo and bar's src/main.rs. Then running cargo-local-registry with --git will trigger the error.
Having different subdirectories would be really nice. Do you think that'd be feasible without having to modify cargo, by specifying multiple replacements in .cargo/config?

@sebastianblunt - I strongly suspect that we could make multiple subdirectories work without modifying cargo.
A tricky bit is defining the name for the subdirectory for each source. It would likely have to contain all the information that defines the source (for git sources this might include a branch, tag or revision) and still be a valid directory name on all supported filesystems.
I think the situation I described with two registries has the potential for conflicting versions, even if a crate in crates.io can't depend on a crate from another source. If A comes from crates.io and B comes from patchedcrates.io registry (I just made that one up). A depends on T from crates.io and B depends on T from patchedcrates.io - conflict. In this situation, patchedcrates.io is in the same role as a git repo using a --git option.
Anyway, just decide what you'd like to do for now:
a) stick with the current PR
b) add some conflict checking
c) go full subdirectories!
It would be a shame to go with option a) - especially as you say you'd be happy to implement some checking.

Let's go with b, I'll add conflict checking to this PR.
Then maybe we should open a separate issue for subdirectories? It would be a very convenient feature to have, and I suspect others may have input as well.

@sebastianblunt - great!
I've created #153 to track the multiple subdirectories discussion.
I look forward to reviewing your PR when you're happy with it.

@sebastianblunt - did you get anywhere with this? Just wondering whether we should close this PR.

Sorry, I never did get around to starting on adding a check for conflicting dependencies. If anybody else wants to take up the work, please feel free, otherwise I'll start on it at some point and write so here.

@sebastianblunt - are you OK with closing this PR then? Feel free to open another.

I still think it can stand on its own, but we can close it and then I can just reopen it later.


Frequently loading resources in Openfl 8.6.2 version will cause a crash and cause a flashback

10-16 19:24:13.214: A/DEBUG(27530): Build fingerprint: 'HONOR/BND-AL10/HWBND-H:7.0/HONORBND-AL10/C00B192:user/release-keys' 10-16 19:24:13.214: A/DEBUG(27530): Revision: '0' 10-16 19:24:13.214: A/DEBUG(27530): ABI: 'arm' 10-16 19:24:13.214: A/DEBUG(27530): pid: 27114, tid: 27368, name: SDLThread  >>> com.ipeaksoft.keng8 <<< 10-16 19:24:13.214: A/DEBUG(27530): signal 11 (SIGSEGV), code 1 (SEGV_MAPERR), fault addr 0x0 10-16 19:24:13.214: A/DEBUG(27530):     r0 00000000  r1 bdc78678  r2 00000000  r3 00000001 10-16 19:24:13.214: A/DEBUG(27530):     r4 c30ec860  r5 bdc781c8  r6 bdc78678  r7 c30ec874 10-16 19:24:13.214: A/DEBUG(27530):     r8 00000001  r9 00000000  sl c30ec878  fp c30ec870 10-16 19:24:13.214: A/DEBUG(27530):     ip bdc78678  sp c3b7e1b0  lr c2a9da0c  pc c2e45658  cpsr 200f0030 10-16 19:24:13.219: A/DEBUG(27530): backtrace: 10-16 19:24:13.219: A/DEBUG(27530):     #00 pc 00484658  /data/app/com.ipeaksoft.keng8-1/lib/arm/liblime.so 10-16 19:24:13.219: A/DEBUG(27530):     #01 pc 000dca08  /data/app/com.ipeaksoft.keng8-1/lib/arm/liblime.so 10-16 19:24:13.219: A/DEBUG(27530):     #02 pc 000dcfc8  /data/app/com.ipeaksoft.keng8-1/lib/arm/liblime.so 10-16 19:24:13.219: A/DEBUG(27530):     #03 pc 000660bc  /data/app/com.ipeaksoft.keng8-1/lib/arm/liblime.so 10-16 19:24:13.220: A/DEBUG(27530):     #04 pc 00599978  /data/app/com.ipeaksoft.keng8-1/lib/arm/libApplicationMain.so 10-16 19:24:13.220: A/DEBUG(27530):     #05 pc 007006cc  /data/app/com.ipeaksoft.keng8-1/lib/arm/libApplicationMain.so 10-16 19:24:13.220: A/DEBUG(27530):     #06 pc 006da000  /data/app/com.ipeaksoft.keng8-1/lib/arm/libApplicationMain.so 10-16 19:24:13.220: A/DEBUG(27530):     #07 pc 003f2400  /data/app/com.ipeaksoft.keng8-1/lib/arm/libApplicationMain.so 10-16 19:24:13.220: A/DEBUG(27530):     #08 pc 0049b174  /data/app/com.ipeaksoft.keng8-1/lib/arm/libApplicationMain.so 10-16 19:24:13.220: A/DEBUG(27530):     #09 pc 0040ba00  /data/app/com.ipeaksoft.keng8-1/lib/arm/libApplicationMain.so 10-16 19:24:13.220: A/DEBUG(27530):     #10 pc 00495d7c  /data/app/com.ipeaksoft.keng8-1/lib/arm/libApplicationMain.so 10-16 19:24:13.220: A/DEBUG(27530):     #11 pc 00309af0  /data/app/com.ipeaksoft.keng8-1/lib/arm/libApplicationMain.so 10-16 19:24:13.220: A/DEBUG(27530):     #12 pc 00bbcf34  /data/app/com.ipeaksoft.keng8-1/lib/arm/libApplicationMain.so 10-16 19:24:13.220: A/DEBUG(27530):     #13 pc 00bbcf34  /data/app/com.ipeaksoft.keng8-1/lib/arm/libApplicationMain.so 10-16 19:24:13.220: A/DEBUG(27530):     #14 pc 00408c14  /data/app/com.ipeaksoft.keng8-1/lib/arm/libApplicationMain.so 10-16 19:24:13.220: A/DEBUG(27530):     #15 pc 003d7d78  /data/app/com.ipeaksoft.keng8-1/lib/arm/libApplicationMain.so 10-16 19:24:13.220: A/DEBUG(27530):     #16 pc 003d7f28  /data/app/com.ipeaksoft.keng8-1/lib/arm/libApplicationMain.so 10-16 19:24:13.220: A/DEBUG(27530):     #17 pc 00cd1084  /data/app/com.ipeaksoft.keng8-1/lib/arm/libApplicationMain.so 10-16 19:24:13.220: A/DEBUG(27530):     #18 pc 00775f84  /data/app/com.ipeaksoft.keng8-1/lib/arm/libApplicationMain.so 10-16 19:24:13.220: A/DEBUG(27530):     #19 pc 00bfa7b4  /data/app/com.ipeaksoft.keng8-1/lib/arm/libApplicationMain.so 10-16 19:24:13.220: A/DEBUG(27530):     #20 pc 00bfac5c  /data/app/com.ipeaksoft.keng8-1/lib/arm/libApplicationMain.so 10-16 19:24:13.220: A/DEBUG(27530):     #21 pc 00cd0fd0  /data/app/com.ipeaksoft.keng8-1/lib/arm/libApplicationMain.so 10-16 19:24:13.220: A/DEBUG(27530):     #22 pc 00c90b7c  /data/app/com.ipeaksoft.keng8-1/lib/arm/libApplicationMain.so 10-16 19:24:13.220: A/DEBUG(27530):     #23 pc 000c2460  /data/app/com.ipeaksoft.keng8-1/lib/arm/liblime.so 10-16 19:24:13.220: A/DEBUG(27530):     #24 pc 000c26b8  /data/app/com.ipeaksoft.keng8-1/lib/arm/liblime.so 10-16 19:24:13.220: A/DEBUG(27530):     #25 pc 000bf8f4  /data/app/com.ipeaksoft.keng8-1/lib/arm/liblime.so 10-16 19:24:13.220: A/DEBUG(27530):     #26 pc 00bfb760  /data/app/com.ipeaksoft.keng8-1/lib/arm/libApplicationMain.so 10-16 19:24:13.220: A/DEBUG(27530):     #27 pc 00bee1ac  /data/app/com.ipeaksoft.keng8-1/lib/arm/libApplicationMain.so 10-16 19:24:13.220: A/DEBUG(27530):     #28 pc 00bee710  /data/app/com.ipeaksoft.keng8-1/lib/arm/libApplicationMain.so 10-16 19:24:13.220: A/DEBUG(27530):     #29 pc 00c8df40  /data/app/com.ipeaksoft.keng8-1/lib/arm/libApplicationMain.so (hxcpp_main+36) 10-16 19:24:13.220: A/DEBUG(27530):     #30 pc 00452d40  /data/app/com.ipeaksoft.keng8-1/lib/arm/liblime.so (Java_org_libsdl_app_SDLActivity_nativeRunMain+508) 10-16 19:24:13.220: A/DEBUG(27530):     #31 pc 0035cca5  /data/app/com.ipeaksoft.keng8-1/oat/arm/base.odex (offset 0x342000)
Flashback occurs when testing the openfl8.6.2 Android platform, which often occurs when it is frequently loaded. Approximately 80% chance of an exception will cause a crash. In the old version 8.2.0 this problem does not exist, I have only done one thing may have an impact but not sure: I customized the template (but I think it may not be related to this).
All of my current versions are in version 8.2.0. The above is a crash log, I hope to help.

How are you loading your resources? Are you using Loader, URLLoader, Assets, or some other method? Are they located in the APK, or are they located remotely?

I am using URLLoader to load local resources. I have tried the same problem with Assets before. The resources I mainly load are some XML, PNG, OGG and other format resources.

In my application, jpeg images are downloaded from the internet and the application crashes frequently. I am using development branch of openfl. There are two differen call stacks below. Bytes class is used in both of them but Bytes class is not thread safe.  Using Bytes from two different threads corrupts the heap (One call is from main thread, the other is from FutureWork(thread pool)).

To fix the problem, the last parameter should be false at loadFromBytes in lime.graphics.Image.

Does this appear to be an issue when using Bytes from two different threads (even totally different instances), or is it referencing the same Bytes object from two threads, somehow?

Bytes using static std::map's internally to track some states. Because it is static, all threads use the same std::map instance and this causes heap corruption eventually, even if Bytes instances are different.

Thanks, I believe this should fix it:
https://github.com/openfl/lime/commit/ab4dcf243a4664e4d72ae2fcfc594d2f5c25bf7c
Would love feedback if someone gets a chance to use a dev version of Lime

@jgranick, why can't we use member variables for hadValue and usingValue like this.
struct Bytes {

  hl_type* t;
  int length;
  unsigned char* b;
  bool hadValue;
  bool usingValue;

  Bytes ();
...

@kodekuru There may be another way around this, but the change was made for better HashLink support. In HashLink, we can directly cast incoming Haxe objects to C++ structs, so long as the type signature matches. As a result, the Bytes class was rewritten to allow it to exactly mirror the Haxe Bytes class, so that bytes objects can be passed directly in and out of the native code, without need for copying or boxing.
I agree it's not the best way to handle this otherwise, maybe there's a compromise that makes the best of things for both HL and other environments

@jgranick, i can confirm that this commit solves the crashes in my application.


Include Negation and Hedging

make sure makes it to the output, perhaps as a larger confidence score that includes document confidence?

closed bc subsumed by #407


Fix debounce issue when book toc is updated

Move the reInitializeContents logic to bookModel due to debounce method not taking into account the parameters. Every time we pulled changes and there were multiple books it only registered the changes from the last call.
Also I moved the unwatch/watch toc methods to the bookModel since it makes more sense for them to be called from the book's object.
This PR fixes the third scenario of #9249

@barbaravaldez It appears you have a test failure now

Pull Request Test Coverage Report for Build 593914788

19 of 25 (76.0%)  changed or added relevant lines in 2 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+0.006%) to 43.275%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

extensions/notebook/src/book/bookModel.ts
15
18
83.33%

extensions/notebook/src/book/bookTreeView.ts
4
7
57.14%

Totals

Change from base Build 590552607:
0.006%

Covered Lines:
25010

Relevant Lines:
52977

💛  - Coveralls


bug(Call): Take much time for user join the room

Investigate this problem and improve time to join the room

@lgmarchi do you still get this bug on dev? @phillsatellite and i tested and we dont get that bug


[2.3] Mac OS X Xcode App template unable to copy framework

Context
System: Mac OS X 10.10.3
SFML version: SFML-2.3-osx-clang-universal
Downloaded today (2015-06-05) from: http://www.sfml-dev.org/files/SFML-2.3-osx-clang-universal.tar.gz
After applying the procedure for the Frameworks described in: http://www.sfml-dev.org/tutorials/2.3/start-osx.php
Error: ditto: can't get real path for source '/Users/m/Prog/Projects/SFML/git/packaging/tmp//install//Library/Frameworks/sfml-system.framework' couldn't copy /Users/m/Prog/Projects/SFML/git/packaging/tmp//install//Library/Frameworks/sfml-system.framework to /Users/8F5FA1581B223693008DC26C/Library/Developer/Xcode/DerivedData/My_First_SFML_App-fiwggsvwdnxwwqdfobspmbhcngfi/Build/Products/Debug/My First SFML App.app/Contents/Frameworks//sfml-system.framework
Correction
Patch command:
curl -fsSl https://gist.githubusercontent.com/mantognini/307d63352c136e47b34d/raw/996aa52d60c0e171a435d6b3802abaf1214d572c/template.patch | patch '/Library/Developer/Xcode/Templates/SFML/SFML App.xctemplate/TemplateInfo.plist'
Manual patch:

Edit /Library/Developer/Xcode/Templates/SFML/SFML\ App.xctemplate/TemplateInfo.plist
Replace the following lines (149-150):

CMAKE_INSTALL_FRAMEWORK_PREFIX="/Users/m/Prog/Projects/SFML/git/packaging/tmp//install//Library/Frameworks"
CMAKE_INSTALL_LIB_PREFIX="/Users/m/Prog/Projects/SFML/git/packaging/tmp/install/usr/local/lib"
by the following:

CMAKE_INSTALL_FRAMEWORK_PREFIX="/Library/Frameworks"
CMAKE_INSTALL_LIB_PREFIX="/usr/local/lib"

Test and enjoy!

Yes, this is a known issue. See here for an automatic patch.

Sorry for the inconvenience, I should have also searched in the forum.
I updated my previous comment with your patch command from the forum.

The archive on the download page has been updated. @mantognini

Thanks. :)

Hi, I tried both the patch command and the manual edit and I still get the error.

As you can see above, the package has been updated and you should not suffer from the issue.

But I do still have the issue.. is it because I'm using 2.3 instead of 2.3.1? There is no 2.3.1 on the downloads page for Mac yet.

No, it is not related to a specific version, it was merely a packaging issue. The archive you can download was fixed, and if by any chance it wasn't, you can still apply the patch. If you have a specific issue, please open a thread on the forum and describe precisely the error you're encountering.


Dynamic duration: Make duration shorter/longer depending how far away the elements are from each other

See: https://material.io/design/motion/speed.html#controlling-speed
Thoughts:

this is less about spring and more about setting sane defaults so consumers don't even have to worry about setting configuration
we know the origin/destination bounding boxes and viewport dimensions, we have all the data we need to calculate this

Done!


Reading FLV continuously

Hi,
I have a server writing a FLV file continuously for live streaming. For example I can set the server to write up to 20 frames (or any other value) to the file, then it writes the file again with the 20 next frames, and so on....
I would like this FLV file to be consumed by flv.js in order to play live content.
But it seems the flv.js player stops to read the file once it reaches the end of has read the initial file size.
Is there a way to read such file continuously without interruption so I could read the FLV as live content ?
Otherwise, I could slit the FLV into multiple segments, but is there a way to define multiple segments without knowing how much segments there will be (because it is live content and segments are produced live) ?
Thanks for your help.

For http-flv live stream, the http response should be a continuous stream, which should not specify a length.
In other words the Content-Length header should not appear. Then pass all the data through the same http response.

Alright thanks for your answer, I will try it.


Optimize btreemap::range(...).count()

Features
It would be nice to expose a more performant way to get to know the number of entries in the stable structure btreemap where keys belong to the specified range than my_btree_map.range().count().
Context
In Juno, while I still need to perform quite some work to improve my code's usage of stable structures, I have exposed a few "count documents and assets" functions. These functions inform the developer about the number of elements in a collection. Therefore, it would be handy for my use case if such information could be found in a performant way.
Notes

Follow-up of forum thread.

This suggestion is not a blocker on my side.

@peterpeterparker with #190, range(...)count() should be much faster. Here are our benchmarks:
---------------------------------------------------

Benchmark: btreemap_iter_count_small_values
  total:
    instructions: 10.12 M (improved by 60.45%)
    heap_increase: 0 pages (no change)
    stable_memory_increase: 0 pages (no change)

---------------------------------------------------

Benchmark: btreemap_iter_count_10mib_values
  total:
    instructions: 497.38 K (improved by 97.89%)
    heap_increase: 0 pages (no change)
    stable_memory_increase: 0 pages (no change)

---------------------------------------------------

Once we release a version containing #190, we can close this issue. Thanks @dragoljub-duric for taking care of this!

Aweome 🔥


feat: exceptional halts in AVM simulator (like div/0) consume all remaining allocated gas

LG but is this in sync with witgen?

... nope! Going to figure out how to do the witgen side of it before we merge. Will flag WIP

I wouldn't be surprised if you need to disable some constraint (or modify it to accomodate the  jump in gas unrelated to the cost of the opcode)

Replaced by https://github.com/AztecProtocol/aztec-packages/pull/10731


V0.3 feedback

Regarding User Guide:
Perhaps add more partial screenshots that captures the usage of command(s)?
The 'Command summary' section will be used heavily by our testers. Good job giving examples for each command.
Regarding Developer Guide:
Good job updating the developer guide =).

Perhaps you guys can explain what the interface Changeable is for?

Shouldn't there be a return arrow?
Good job having a comprehensive list for the product survey =). Perhaps it would be clearer if it was to be in a table?
It may be more practical to give a few examples of interesting test cases and explain the thinking behind how you arrived at those test cases, rather than try to give a comprehensive list of all test cases.
Perhaps explain how your design support undo/redo. There are multiple ways this can be done, so it will be useful to explain how you do it and why you chose to do it that way.
Glossary:
Perhaps glossary could be updated with terms for floating task, attachments and such?
Overall:
Try to do a peer review on each other's PRs.
Please close this issue after reading it.

@brandonyeoxg for the changeable interface, I realised that I created that interface for my previous implementation of the Undo command. I have updated the interface and updated the development guide. The updates will be reflected in the next milestone. Thanks for looking through our development guide and giving some feedback and suggestions for improvement!


OpenAi endpoint support

Added ability to drive OpenAI endpoints via a new backend_client

new "openAI" service-kind
new "endpoint" option in CLI
Added OpenAI into model parser

All OpenAI models have a single input called "payload" that will take any json format
All OpenAI models have a single output called "response" that will contain the response from the server

This is going into a feature branch. More testing will be added before being merged into the real branch

Looks pretty great overall. Thanks for the hard work everyone 🙏

Requested review from @rmccorm4--Ryan, feel free to cut it short if the code looks too unfamiliar, just curious your high-level opinion on code structure/flows and usability.


build(pm2): add keys

Pull Request Test Coverage Report for Build 1917

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

Totals

Change from base Build 1916:
0.0%

Covered Lines:
120

Relevant Lines:
172

💛  - Coveralls


Issue with running post quantized TF Lite on ArmNN

I am have following setup:
Original Model: Retrained Mobilenetv2 with lesser classes (using TF-Keras APIs)
Converted Model: Post quantized- Full integer quantization- uint8 TFLite Model (using TF-Keras APIs)
Tensorflow version: 1.15
I am trying to run this model on a GPU using ArmNN support.
I faced the following issue:
Optimize graph and load the optimized graph onto a compute device...
Warning: WARNING: Layer of type Convolution2d is not supported on requested backend GpuAcc for input data type QAsymmS8 and output data type QAsymmS8 (reason: in validate src/runtime/CL/functions/CLGEMMConvolutionLayer.cpp:423: Input data type not compatible with Weights), falling back to the next backend.
Warning: ERROR: Layer of type Convolution2d is not supported on any preferred backend [GpuAcc ]
I got the following reply from ArmNN git:
That error occurs if the weights are QSymm8 with per channel quantization (that's QSYMM8_PER_CHANNEL) and the input is not QAsymm8. In this case your input is QAsymmS8 so it's not supported right now.
In order to use the GpuAcc you would have to retrain the model to use QASymm8 instead of QAsymmS8 or not to use per channel quantization on your weights.
Link: https://github.com/ARM-software/armnn/issues/425
I don't quite understand how I can do the above mentioned using the TFLite Converter. Please help. Thanks in advance

@kratika5
Please share a simple stand alone indented code for us to replicate the issue faced or if possible share a colab gist with the error faced.

Here is a link to Keras model training and conversion to TFLite:
https://colab.research.google.com/drive/1lLSimDVdU2oFYH1HH00uYyzRogWkFCuJ?usp=sharing
For the second part, as it runs on an embedded platform, I cannot share a direct colab.
I am using this test code provided by ArmNN and I use the TFLite model generated above.
Just for additional information, pretrained quantized models as well as a quantize-aware trained uint8 model (using TF1.15 Slim) work fine with ArmNN.

Could you share which datatype of the model ArmNN is complaining?
"src/runtime/CL/functions/CLGEMMConvolutionLayer.cpp:423: Input data type not compatible with Weights), falling back to the next backend."

The model I have is a uint8 (post quantized model), the error mentioned above says:
Input/Output Datatypes - QAsymmS8

@daverim could you guide this?

Hi There,
We are checking to see if you still need help on this, as you are using an older version of tensorflow which is officially considered end of life . We recommend that you upgrade to the latest 2.x version and let us know if the issue still persists in newer versions. Please open a new issue for any help you need against 2.x, and we will get you the right help.
This issue will be closed automatically 7 days from now. If you still need help with this issue, please provide us with more information.


Fix build url on the readme

Description
In this PR, the readme ospo url were updated

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
531

Relevant Lines:
531

💛  - Coveralls


update > for issue #1791

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Potato seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


fix: add truncate and source to newly added blog

Fixes: #295
Changes:
update traffic-split-in-ingress-controller.md

/lgtm
Thanks @KishaniKandasamy .

👍🏻👍🏻


pkg/trace: add tests for sublayer annotation

This adds tests to ensure that sublayer annotation is done when a trace is
sampled, and not done when the trace is not sampled.
This relates to #5961
There should be no release notes related to this change, as it only adds tests and will not affect the end user.
Motivation
This testing was performed as part of QA for release 7.22.0

I don't see how the appveyor/pr failure could be related to this PR.
It seems to be an issue on Windows. I'm guessing it's somehow related to the TestProfileProxyHandler/error test, because it's the only reference to the bad site "asd:\r\n" that shows up in the error:
    api_test.go:880: Post http://localhost:8126/v0.4/traces: write tcp <IP_ADDRESS>:1349-><IP_ADDRESS>:8126: wsasend: An established connection was aborted by the software in your host machine.
Error: Profile forwarder is OFF because of invalid intake URL: parse https://intake.profile.asd:
/v1/input: net/url: invalid control character in URL
FAIL

TestProfileProxyHandler/error:
https://github.com/DataDog/datadog-agent/blob/master/pkg/trace/api/profiles_test.go#L106
n


unable to request account

Describe the bug
I am facing issue when request account. My internet & email are no problem.
Screenshots

Desktop (please complete the following information):

OS: MacOS
Browser: safari

I've been trying using another email and facing same issue. How to resolve this issue?

I got the same error

I'm getting the same error too. I wonder if it is because of the refferal code. What did you write for that one @khanifah-gif ?

Thank you for your patience. We are investigating this issue. We would like to designate a single point of contact, therefore, we will be closing this issue. Please watch the following issue to monitor the progress.
https://github.com/aws/studio-lab-examples/issues/254


Missing tiles in UE 5.2 in shipping builds with water mask enabled

As reported here:
https://community.cesium.com/t/grey-image-tiles-while-moving-away-from-the-ground-in-ue-5-2-1/25718
The problem seems to be that something is wrong with the default water material in UE 5.2, so all tiles that are supposed to be rendered as full or partial water instead get rendered as the default material. But not in the Editor, only in Shipping builds.

Oh yes, there's a message in the log about it:

UATHelper: Packaging (Windows): LogShaderCompilers: Warning: Failed to compile Material /CesiumForUnreal/Materials/M_CesiumBaseMaterial.M_CesiumBaseMaterial (MI:/Game/CesiumSamples/Materials/MI_CesiumCustomWater.MI_CesiumCustomWater) for platform PCD3D_SM5, Default Material will be used in game.
UATHelper: Packaging (Windows):   C:\Engine\Private\BasePassPixelShader.usf.intermediate.hlsl(185,74-84):  warning X3577: value cannot be NaN, isnan() may not be necessary.  /Gis may force isnan() to be performed
UATHelper: Packaging (Windows):   C:\Engine\Private\BasePassPixelShader.usf.intermediate.hlsl(344,19-30):  warning X3577: value cannot be NaN, isnan() may not be necessary.  /Gis may force isnan() to be performed
UATHelper: Packaging (Windows):   C:\Engine\Private\BasePassPixelShader.usf.intermediate.hlsl(95,14-41):  err0r X4510: maximum ps_5_0 sampler register index (16) exceeded

#490 is a viable solution to this, but it's challenging. We have to decide statically, in the material, whether to use a shared sampler or not. And if we do, then none of the customizations (such as filtering mode) will have any effect anymore.
Or maybe we can use a static switch for parameters that are known at Editor time? Such as number of raster overlays and whether they need custom filtering.


ll40ls: added support for 'blue label' lidars

the key is splitting up read_reg() into two transfers

Awesome, applied!


Typo

@kmgallahan : Thanks for your contribution! The author(s) have been notified to review your proposed change.


[AMBARI-24310] UI sends host check request for custom jdk with invalid hosts

What changes were proposed in this pull request?
UI sends "java_home_check" host check with all populated hosts instead hosts with passed registration only. This can cause 500 server exception due HostNotFoundException.
2018-07-05 14:10:30,930 ERROR [ambari-client-thread-573] AbstractResourceProvider:295 - Caught AmbariException when creating a resource
org.apache.ambari.server.HostNotFoundException: Host not found, hostname=test-0000
        at org.apache.ambari.server.state.cluster.ClustersImpl.getHost(ClustersImpl.java:456)
        at org.apache.ambari.server.state.ConfigHelper.getEffectiveDesiredTags(ConfigHelper.java:189)
        at org.apache.ambari.server.state.ConfigHelper.getEffectiveDesiredTags(ConfigHelper.java:173)
        at org.apache.ambari.server.controller.AmbariManagementControllerImpl.findConfigurationTagsWithOverrides(AmbariManagementControllerImpl.java:2353)

POST http://host:8080/api/v1/requests 500 (Internal Server Error)
send @ vendor.js:8630
jQuery.extend.ajax @ vendor.js:8082
send @ app.js:192735
doCheckJDK @ app.js:41241
(anonymous function) @ app.js:41318
fire @ vendor.js:1141
self.fireWith @ vendor.js:1252
done @ vendor.js:8178
callback @ vendor.js:8702

Body of request:
{"RequestInfo":{"context":"Check hosts","action":"check_host","parameters":{"threshold":"60","java_home":"/tmp/jdk1.8.0_171/","jdk_location":"http://host:8080/resources","check_execute_list":"java_home_check"}},"Requests/resource_filters":[{"hosts":"test-0000,test-0001,test-0002,...

How was this patch tested?
21797 passing (25s)
48 pending

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/3168/
Test FAILed.
Test FAILured.

retest this please

Refer to this link for build results (access rights to CI server needed):
https://builds.apache.org/job/Ambari-Github-PullRequest-Builder/3175/
Test PASSed.


"The classes are un-ordered" warning when classes are indeed ordered

julia> using MLJ
julia> X, y = @load_crabs;
julia>  y = coerce(y, OrderedFactor);
julia> scitype(y)
AbstractArray{OrderedFactor{2},1}

julia> MLJ.fp(y, y)
┌ Warning: The classes are un-ordered,
│ using: negative='B' and positive='O'.
│ To suppress this warning, consider coercing to OrderedFactor.
└ @ MLJBase ~/Dropbox/Julia7/MLJ/MLJBase/src/measures/confusion_matrix.jl:73
0

Analysis
I can reproduce the bug, it stems from this:
y = coerce(y, OrderedFactor)
scitype(y)            # AbstractArray{OrderedFactor{2},1}
scitype_union(y) #  Multiclass{2}

Note  that I know you've been warning against the use of scitype_union but doing the check  with scitype is  actually annoying and I do  just  want to get the "element" scitype (i.e. the _get_elst temporary fix suggested in the PR below).
Fix
PR #112 a simple fix in dev which does what I was expecting scitype_union to do above which fixes the issue.
I guess there's a couple oof options as to  how we can proceed here:

deprecate scitype_union and make it do  what the simple _get_elst does in the PR above
fix  scitype_union if the above is a bug
not do anything and just merge the PR and come back to this  later

As discussed here, I believe the offending problem is a bug in CategoricalArrays.

@tlienart Is this resolved by https://github.com/alan-turing-institute/ScientificTypes.jl/pull/54 ?

yes


Convert time::Duration to std::time::Duration

This seems to fix it, strange that time did not implement From but TryFrom since it seems we should always be able to convert between the both, e.g.
#[cfg(feature = "std")]
impl From<std::time::Duration> for Duration {
    fn from(value: std::time::Duration) -> Self {
        Self::new(value.as_secs(), value.as_nanos())
    }
}

#[cfg(feature = "std")]
impl From<Duration> for std::time::Duration {
    fn from(value: Duration) -> Self {
        Self::new(value.seconds, value.nanoseconds)
    }
}

This shouldn't be required. I was missing a feature flag to enable impl Add<time::Duration> for SystemTime in time.


Question: Does libonnx support dynamic shape/CUDA ?

Dear friends,
Thanks for good job.
We have two question:  1) Does libonnx support dynamic shape input ? If not, how to implement it ? (Just some hints.);
2) How to support CUDA inference on libonnx ?

see struct onnx_tensor_t, this can expressd for any data type, CUDA  inference, you must write a struct onnx_resolver_t, this is a iterface for some hardware acceleration

@jianjunjiang ,Thank you.  We also wonder how support dynamic input shape with libonnx ? Would you please give us some advance ?

https://github.com/xboot/libonnx/blob/8f6c6a02a28d330b5c640856664a5cf835dfdb7c/examples/hello/main.c#L2272
using onnx_tensor_apply function to modify input tensor

Many thanks.


⚠ Bofrost.fr has degraded performance

In 6694924, Bofrost.fr (https://www.bofrost.fr) experienced degraded performance:

HTTP code: 200
Response time: 968 ms

Resolved: Bofrost.fr performance has improved in 0f47fcc after 6 minutes.


connectivity: Don't fail if cilium-cli-helm-values doesn't exist

Assume the default version if cilium-cli-helm-values secret doesn't
exist to retain the previous behavior.
Fixes: 22e5ec96560b ("connectivity: Remove --base-version flag")
Fixes: #927
Signed-off-by: Michi Mutsuzaki<EMAIL_ADDRESS>

manually tested with:
% helm install cilium cilium/cilium --version 1.11.6 --namespace kube-system
...

% ./cilium connectivity test
...
⚠  Unable to detect Cilium version, assuming v1.11.5 for connectivity tests
...
✅ All 11 tests (68 actions) successful, 0 tests skipped, 0 scenarios skipped.


fix(secondary-nav): mobile menu overflow

What I did

Moved overflow mobile menu list to an outer container.
Removed orphaned code.

Testing Instructions

Go to the Secondary Nav Deploy Preview for the Dark variant and the Default
Set the viewport with height < 850px such as an iPhone.
Open the mobile menu.
Click "Other examples".
Try and scroll to CTA.  It should be visible

Notes to Reviewers
You should be able to scroll to and view the CTA when a mobile menu is open in the netlify preview.
However, if you run the code locally in the dev demo npm start you will have to remove the demo's overflows in order to see the change correctly due to conflicting CSS.

Didn't catch this branch had issues before pushing it and creating the PR.  Going to refactor the branch locally a reopen a different PR.


Node version requirements too strict?

It looks like the node version requirements for this package are restricted to just the latest LTS:
"node": ">= 18.12 <19"

Is there some reason for this restriction, i.e. does it not work under older or newer versions of Node?  Sure, folks should generally want to be on the latest-available LTS, but actually making that decision should be done by the implementer of the requesting package, unless there's reason why this package wouldn't work under any other node range requirement.

You are right. I will remove it. Thanks for noticing Dan!

@DanHulton removed in v0.2.4.


fix(providers): error of providers link

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


using 2FA with cli-github

How should I use 2FA with cli-github?
Right now my transcript looks like the following:
║                                                                                Logging in ...                                                                                GitHub Username: timurb
GitHub Password:
2FA Authentication Code:

I've tried pasting the tokens generated at https://github.com/settings/applications but these do not work and I have received no auth codes to my mobile.
Do you think I have some issue with 2FA configured or using cli-github with 2FA or have I missed something during the configuration?

You will receive a SMS message on your phone, containing the authentication code. Write that code there.
If you didn't receive any auth codes on mobile, then that's most probably an issue with GitHub. But I will test it if it works for me.

/cc @remixz Can you look at this part of code? Do you see anything wrong?
At what step is GitHub supposed to send the SMS message? Probably here?

@timurb Run npm install cli-github@latest so you get 1.6.1 which should work fine with two factor authentication.

Works fine now, thanks!

Cool!


How to get the latest version of 'qa_generated.json' from Wikidata?

Hi, thanks for your solid work!
Could you share the code or detailed instructions on how to build the latest version of 'qa_generated.json‘ from Wikidata?
Looking forward to your reply.

Hi, we are happy you find it interesting. We will share the code to generate the 'qa_generated.json‘ soon. A brief description as the procedure is available in the new version of our paper. Basically,

we select the subject (entity name) and the relation (property), for instance "subject:Cristiano Ronaldo", and "property:sports team"
using Wikidata API we collect the data related to the selected subject by its unique wikidata ID  (subject:Cristiano Ronaldo, ID: Q11571) and (property:sports team, ID: P54).
for each attribute value, we also collect the start and end times (properties P580 and P582).

as mentioned, we will release the code soon!!
does this explanation help you?

Thanks for your detailed reply! I will try it myself.


Add identifiers to entity records (from 1822)

Problem description:  We are adding more identifiers to Works records on #944 .  There are also identifiers that need to be identified and shown on People, Place, Concept and Events pages.
Expected Behavior: Ensure all identifiers that should be shown to users are displayed.
Needed

[ ] Confirmation of missing identifiers for People - Kelly
ORCID
[ ] Confirmation of missing identifiers for Places - Kelly
[ ] Confirmation of missing identifiers for Concepts - Kelly
[ ] Confirmation of missing identifiers for Events - Kelly
[ ] Confirm UAT links for above - Heather
[ ] Mockups to confirm where these are shown - is ordering, as provided in data?
People
https://lux.collections.yale.edu/view/person/783e7e6f-6863-4978-8aa3-9e6cd8cd8e83
Places
https://lux.collections.yale.edu/view/place/0f7662ab-35d1-4b90-ba96-66b3663cc512
Concepts
https://lux.collections.yale.edu/view/concept/f4dc7026-690c-452d-b976-9fc939591b6a
Events
https://lux.collections.yale.edu/view/activity/4d1f9ff3-a42f-46f4-9da1-4295e169d130

Comments from old tix:
kd736  -
"@prowns this can't be worked on yet. the inspiring ticket was for Works missing IDs, which exist in the data and aren't being shown, but none of these entities have identifier data not being shown. We intend to add ORCIDs (and perhaps other identifiers) for some people but they're not there yet."

@kkdavis14 were the ORCID's (and other identifiers) added? or are we still waiting on this?

@roamye there aren't any examples yet. We may be better served by closing this ticket and opening one when we have an example.

Per UAT leaving this opened @kkdavis14.

per tick forming this is not blocked and will be worked on in the future.


I've added in the comment text from https://github.com/github/customer-success-engineering/issues/1490#issuecomment-1756356610 and added some reporting so that we can see which discussions will be affected.

I've added in the comment text from https://github.com/github/customer-success-engineering/issues/1490#issuecomment-1756356610 and added some reporting so that we can see which discussions will be affected.
As of now, none of the discussions will be commented on, but once we're happy that we've targeted the correct ones, I can change that before merging this PR.
I'm going to run the Action manually from this branch before it can comment on any discussions to make sure that everything is working as expected.
Originally posted by @mgriffin in https://github.com/community/community/pull/69778

There is not a label identifying the kind of this issue.
Please specify it either using /kind <group> or manually from the side menu.

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

ei @CastorPollox could you explain what is the purpose of this issue?


merge stable

Issue 21250 - dirEntries on non-existent directory causes assert error
merged-on-behalf-of: Andrei Alexandrescu<EMAIL_ADDRESS>

https://app.circleci.com/pipelines/github/dlang/phobos/2726/workflows/88c3d13f-b532-4387-9eda-ce36be90d8f6/jobs/12296
Using SSH Config Dir /home/circleci/.ssh
Cloning into '.'...
Warning: Permanently added the RSA host key for IP address '<IP_ADDRESS>' to the list of known hosts.
remote: Enumerating objects: 25, done.
remote: Counting objects: 100% (25/25), done.
remote: Compressing objects: 100% (19/19), done.
remote: Total 83012 (delta 10), reused 14 (delta 5), pack-reused 82987
Receiving objects: 100% (83012/83012), 56.65 MiB | 37.52 MiB/s, done.
Resolving deltas: 100% (59040/59040), done.
fatal: Could not parse object '1cc776fdf0c4cc51827e9f7ff814ad4124659345'.

???

https://github.com/dlang/phobos/pull/7664


add integrity checks to IntervalHeap

cc #85

@Gankro Added some documentation to is_valid, tried to make the code more readable, and added a test.

Nice! This looks good to me.


Deep Zoom support

For whatever reasons, some folks want to view Deep Zoom images (high resolution images stored in a tiled gaussian pyramid) in Neuroglancer, so the 2D counter part of precomputed. This data source (deepzoom://) enables them doing that.
https://github.com/Tevemadar/neuroglancer/blob/deepzoom-support/src/neuroglancer/datasource/deepzoom/log.md contains the story, the most important points are related to backend.ts:

PNG tile support is stable for sure (I'm very familiar with the internals of PNG)
JPEG tile support is somewhat hairy (I'm not very familiar with the internals of JPEG)
there's an alternative implementation commented out, which is stable and actually does work on every current browser, but doesn't work on Safari from more than a week ago or Firefox from more than half year ago.

I have no idea of the IPR stuff related to Deep Zoom image format. There are many software supporting it (OpenSeadragon being the most widely used, but there's OpenZoom from the past, etc.), but I couldn't locate anything related to the format.

Thanks --- this will be a nice addition!

Can you include this data source in the top-level README, and if there is a public example dataset you can link to, perhaps include that in the examples as well?


Issue - Upvote Reaction throws an error

TypeError: Cannot read property 'user' of null
    at MessageReactionAddEvent.handleRep (file:///B:/Projects/Zen/main/events/messageReactionAdd.js:46:16)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async MessageReactionAddEvent.execute (file:///B:/Projects/Zen/main/events/messageReactionAdd.js:26:11)
TypeError: Cannot read property 'user' of null
    at MessageReactionAddEvent.handleRep (file:///B:/Projects/Zen/main/events/messageReactionAdd.js:46:16)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async MessageReactionAddEvent.execute (file:///B:/Projects/Zen/main/events/messageReactionAdd.js:26:11)
TypeError: Cannot read property 'user' of null
    at MessageReactionAddEvent.handleRep (file:///B:/Projects/Zen/main/events/messageReactionAdd.js:46:16)
    at processTicksAndRejections (node:internal/process/task_queues:96:5)
    at async MessageReactionAddEvent.execute (file:///B:/Projects/Zen/main/events/messageReactionAdd.js:26:11)

Member might need to be fetched for handle rep in both add and remove reaction.

Fixed


cloudant package actions do not provide any sampleInput or sampleOutput annotations

See weather or utils or slack for examples of packages that provide sampleInput and sampleOutput annotations on their actions.
These annotations help quite a bit with UX.

@johnsolm @dubeejw if still relevant please move to proper repo.

Issue moved to openwhisk/openwhisk-package-cloudant #69 via ZenHub


Event Mesh -- Queue not created (package.json does not work as described)

Hi guys,
I deployed a node app (no errors). The deployment created an instance of the event mesh as expected (I see the client in the SAP Event MeshApp). Due to your documentation I added the definition of a queue to package.json:
  "cds": {
    "requires": {
      "[production]": {
        "auth": "xsuaa",
        "messaging": {
          "kind": "enterprise-messaging",
          "publishPrefix": "$namespace/",
          "subscribePrefix": "$namespace/",
           "queue": { "name": "$namespace/my/first/queue" }
        }

I can't see the queue:

I created an event and an action in the service cds:
    action raiseEvent();

    event NewEmployeeHired {
        employeeId   : Integer;
        employeeName : String;
        department   : String;
        hireDate     : Date;
    }

When the action is executed I emit the event:
 const messaging = await cds.connect.to('messaging');

 this.on("raiseEvent", async (req) => {
     await messaging.emit("NewEmployeeHired", {
        employeeId: 12345,
        employeeName: "Mickey",
        department: "Mouse",
        hireDate: new Date().toDateString(),
      });
    });

This seems to work (debugged this) but nothing happens (no event recorded on the BTP, no error raised).
I followed your documentation on https://cap.cloud.sap/docs/guides/messaging/event-mesh.

Why was the queue not created (package.json)?
Why does the "emit" work but nothing happens? (No event created on BTP)

Thanks,
Jan

Hi Jan,
I do understand your questions. Please raise this question in the community or create a support ticket.
This repo is solely for documentation contributions and fixes. We can't offer support here.
Thanks René


set config_cache_path config to data/cache/config-cache.php

with inside data/cache directory

I've looked through the various scripts:

bin/clear-config-cache.php (mapped to composer clear-config-cache) uses the $config['config_cache_path'] value to determine where the file exists.
zf-development-mode also uses the config value.

Knowing this, I think we can safely accept this for version 3.

Thanks, @samsonasik!


Distracted Driver Detection using DL

Deep Learning Simplified Repository (Proposing new issue)
:red_circle: Project Title : Distracted Driver Detection using DL
:red_circle: Aim : To identify whether the driver driving the vehicle is distracted or not.
:red_circle: Dataset :  https://www.kaggle.com/competitions/state-farm-distracted-driver-detection/data
:red_circle: Approach : Try to use 3-4 algorithms to implement the models and compare all the algorithms to find out the best fitted algorithm for the model by checking the accuracy scores. Also do not forget to do a exploratory data analysis before creating any model.

📍 Follow the Guidelines to Contribute in the Project :

You need to create a separate folder named as the Project Title.
Inside that folder, there will be four main components.

Images - To store the required images.
Dataset - To store the dataset or, information/source about the dataset.
Model - To store the machine learning model you've created using the dataset.
requirements.txt - This file will contain the required packages/libraries to run the project in other machines.

Inside the Model folder, the README.md file must be filled up properly, with proper visualizations and conclusions.

:red_circle::yellow_circle: Points to Note :

The issues will be assigned on a first come first serve basis, 1 Issue == 1 PR.
"Issue Title" and "PR Title should be the same. Include issue number along with it.
Follow Contributing Guidelines & Code of Conduct before start Contributing.

:white_check_mark: To be Mentioned while taking the issue :

Full name :
GitHub Profile Link :
Email ID :
Participant ID (if applicable):
Approach for this Project :
What is your participant role? (Mention the Open Source program)

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

Issue assigned to you @achrekarom12


fixed typo

Docs Build status updates of commit 9dba582:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

mixed-reality-docs/gaze-and-commit.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.


ADD opencv-python to requirements

Needed to install it using pip to make the script run.
Command I used:
pip install opencv-python

Thank you. Dependency environment has been updated.


Researching Container technologies Podman vs Docker

What is Docker?Docker is a widely-used platform designed to simplify the process of building, deploying, and managing applications using container technology. Containers are lightweight, portable, and self-contained environments that include everything needed to run a piece of software, such as code, runtime, libraries, and system tools.Key Features of Docker:Containerization: Docker makes it easy to create, manage, and run containers.Docker Hub: A centralized repository for Docker images, where users can upload, share, and pull pre-built images.Docker Compose: A tool for defining and running multi-container Docker applications.Swarm Mode: Docker’s native clustering and orchestration tool, allowing you to manage containers across a cluster of Docker hosts.Client-Server Architecture: Docker uses a daemon (Docker engine) that communicates with the Docker client. The daemon runs containers and manages other container-related services.What is Podman?Podman (short for "Pod Manager") is an open-source container management tool developed by Red Hat that provides many of the same features as Docker but with a different approach to container management.Key Features of Podman:Daemonless Architecture: Unlike Docker, Podman does not require a background daemon to run. Each container runs as a child process under the user’s control, which improves security and resource management.Rootless Containers: Podman allows users to run containers as non-root users by default, improving security by reducing the attack surface.Compatibility with OCI (Open Container Initiative): Podman is compatible with OCI-compliant container images and runtime, meaning it can run most Docker images.Pod Support: In addition to managing individual containers, Podman supports the concept of “pods” (borrowed from Kubernetes), where multiple containers can share network and storage resources.No Centralized Repository: Unlike Docker’s Hub, Podman uses a decentralized approach and integrates with various container registries (e.g., Quay, Red Hat, or even Docker Hub).Comparison between Docker and Podman

Feature
Docker
Podman

Architecture
Daemon-based (client-server)
Daemonless (runs containers directly)

Security
Root privileges by default (though rootless mode is possible)
Rootless by default, better for unprivileged use cases

Container Orchestration
Docker Swarm or Kubernetes (with additional setup)
Kubernetes (via CRI-O)

Pods Support
No native pods (requires Kubernetes for multi-container)
Native pod support, allowing for multi-container management

Image Compatibility
Docker images from Docker Hub or other registries
Compatible with Docker images (OCI-compliant)

Management Tools
Docker CLI, Docker Compose, Docker Swarm
Podman CLI, Podman Compose (Docker Compose compatible)

Resource Usage
Requires Docker Daemon running in the background
Lightweight, as it does not require a background daemon

Use Cases
Popular for development, production, and CI/CD workflows
Focuses on security, system resource management, and integration with Kubernetes

Key Differences:Daemon vs. Daemonless: Docker relies on a daemon that runs with root privileges, which could be a potential security risk. Podman does not require a daemon, giving users more control over security and resources.Rootless Containers: Podman allows for running containers without root privileges by default, whereas Docker typically runs with root access, though it can be configured for rootless operation.Orchestration: Docker uses its own Swarm mode for container orchestration, whereas Podman doesn’t have native orchestration but integrates with Kubernetes (using tools like CRI-O).When to Use Docker vs. Podman:Use Docker if you are looking for a tool with extensive community support, a built-in orchestration tool (Swarm), and a large library of pre-built container images (Docker Hub).Use Podman if you prioritize security (rootless containers), need a daemonless architecture, and want seamless integration with Kubernetes.Both tools are highly capable, but your choice will depend on your use case, security requirements, and workflow preferences.

From ChatGPT

Docker preference by customer


Update version

Pull request checklist

[ ] Add a clear description of the change
[ ] Add any new tests needed
[ ] Run spell check on new text visible to user (documentation, GUI etc.)
[ ] Check any changes to requirements.txt are reflected in setup.py and conda-forge feedstock
[ ] Check code passes CI checks (run run_ci.sh or check GitHub Actions)

See CONTRIBUTING.md for more details.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

56 of 56 (100.0%)  changed or added relevant lines in 6 files are covered.
2 unchanged lines in 1 file lost coverage.
Overall coverage decreased (-0.07%) to 99.503%

Files with Coverage Reduction
New Missed Lines
%

planetmapper/body.py
2
99.69%

Totals

Change from base Build<PHONE_NUMBER>:
-0.07%

Covered Lines:
2909

Relevant Lines:
2923

💛  - Coveralls