+250-300?

Hi Amanj,
This might not be very useful to you but still.
You claimed a 250-300 Elo improvement by v1.0.0 over v0.3.0. Therefore for my current tournament I selected opponents in the 2160-2200 range (to be on the safe side). However, even this selection has proved too strong. At the time of writing Zahak has a score of 6 out of 30.
I watched some of the games. It is hard to point to a salient problem. It seemes to me one of the problems is in endgames with passed pawns. Also, somehow the depth reached is less than that of most of the opponents. Zahak seems to fall for traps.
I may send you the PGN if you are interested. You can find my e-mail address in my CCC profile.
Best regards,
Gabor

Interesting, my tests showed that (well, with self play):
https://github.com/amanjpro/zahak/pull/49#issuecomment-814260987
https://github.com/amanjpro/zahak/pull/49#issuecomment-814261970
mmm... most likely the problem is with self-play. I think it is time for me to expand the pool of the engines, on which I test Zahak for

I would be grateful to see PGNs, thanks a lot

I read at CCC that the real difference is about 70 % of what self play
shows.
In my tournament Zahak is on 17/68. I attach the PGN.
------ Eredeti üzenet ------
Feladó: "Amanj Sherwany" @.>
Címzett: "amanjpro/zahak" @.>
Másolat: "Gabor Szots" @.>; "Author"
@.>
Elküldve: 2021.04.09. 15:48:42
Tárgy: Re: [amanjpro/zahak] +250-300? (#51)

Interesting, my tests showed that (well, with self play):
#49 (comment)
https://github.com/amanjpro/zahak/pull/49#issuecomment-814260987
#49 (comment)
https://github.com/amanjpro/zahak/pull/49#issuecomment-814261970
mmm... most likely the problem is with self-play. I think it is time
for me to expand the pool of the engines, on which I test Zahak for
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/amanjpro/zahak/issues/51#issuecomment-816695153,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AFRWZ6KBEAWXJILGTERETHTTH4ASXANCNFSM42UWWBDA.

Well, I'm not sure I have sent the PGN. I can't see it here.

You cannot send attachments by email to a github comment, unfortunately :(

Maybe this way.
Zahak 1.0.0 64-bit - Apr 9.pgn.zip

Thank you a lot :)

FYI, I also measure a great difference in self play.
Score of Zahak_0.3.0-x64 vs Zahak_1.0.0-x64: 1 - 13 - 6 [0.200]
... Zahak_0.3.0-x64 playing White: 0 - 6 - 4 [0.200] 10
... Zahak_0.3.0-x64 playing Black: 1 - 7 - 2 [0.200] 10
... White vs Black: 7 - 7 - 6 [0.500] 20
Elo difference: -240.8 +/- 159.1, LOS: 0.1 %, DrawRatio: 30.0 %
20 of 20 games finished.
This was played at 30s+0,2s TC.

FYI, I also measure a great difference in self play. Score of Zahak_0.3.0-x64 vs Zahak_1.0.0-x64: 1 - 13 - 6 [0.200] ... Zahak_0.3.0-x64 playing White: 0 - 6 - 4 [0.200] 10 ... Zahak_0.3.0-x64 playing Black: 1 - 7 - 2 [0.200] 10 ... White vs Black: 7 - 7 - 6 [0.500] 20 Elo difference: -240.8 +/- 159.1, LOS: 0.1 %, DrawRatio: 30.0 % 20 of 20 games finished. This was played at 30s+0,2s TC.

My explanation is passed pawns, I know I can easily prune promotions, or passed pawn moves... my move ordering doesn't care much about them. This might explain why it can crush weaker engines (old version), but struggles to convert against equal strength engines? as they usually require good endgames? just a theory, not proven yet

So, this is really strange, I have been playing with passed pawns, and currently running a match (still going on):
Rank Name                          Elo     +/-   Games    Wins  Losses   Draws   Points   WWins  WLoss.  WDraws   BWins  BLoss.  BDraws
   0 zahak_dev                     -27      53     130      46      56      28     60.0      25      25      15      21      31      13
   1 baislicka                     289     185      22      16       1       5     18.5       8       1       2       8       0       3
   2 Achillees                     191     157      22      14       3       5     16.5       7       1       3       7       2       2
   3 gopher_check                   64     141      22      11       7       4     13.0       7       3       1       4       4       3
   4 zahak-darwin-amd64-1.0.0      -64     131      22       6      10       6      9.0       4       4       3       2       6       3
   5 vice                          -70     136      20       5       9       6      8.0       3       3       4       2       6       2
   6 rustic                       -213     194      22       4      16       2      5.0       2       9       0       2       7       2

Started game 133 of 1200 (zahak_next vs zahak-darwin-amd64-latest)

Looking at gopher-check, even though it is supposed to be 100 elo stronger than Achillees and Baislicka, but it does much worse than both of them. Not sure what to make with this really

I'll have results tomorrow, and will update here

As promised I came back with my final numbers for the above match. And gopher-check still does less good than the "lower rated" engines. This is interesting/strange to me. Even looking at vice (which is rated around 2000), does terribly bad against Zahak. I'll be working on Zahak to see the reason behind it.
Rank Name                          Elo     +/-   Games    Wins  Losses   Draws   Points   WWins  WLoss.  WDraws   BWins  BLoss.  BDraws
   0 zahak_next (PR #52 )          -14      18    1200     461     508     231    576.5     251     236     113     210     272     118
   1 baislicka                     189      49     200     133      34      33    149.5      73      13      14      60      21      19
   2 Achillees                     166      49     200     129      40      31    144.5      64      22      14      65      18      17
   3 gopher_check                  109      43     200     104      43      53    130.5      57      15      28      47      28      25
   4 zahak-darwin-amd64-1.0.0      -26      40     200      60      75      65     92.5      37      32      31      23      43      34
   5 vice  (v 1.1)                -173      48     200      37     129      34     54.0      16      59      25      21      70       9
   6 rustic   (1 alpha 2)         -179      53     200      45     140      15     52.5      25      69       6      20      71       9

Finished match

And according to bayeselo:
ResultSet>readpgn zahak_games/passed-pawns-1.pgn
1200 game(s) loaded
ResultSet>elo
ResultSet-EloRating>mm
00:00:00,00
ResultSet-EloRating>exactdist
00:00:00,00
ResultSet-EloRating>ratings
Rank Name                       Rating   Δ     +    -     #     Σ    Σ%     W    L    D   W%    =%   OppR
---------------------------------------------------------------------------------------------------------
   1 baislicka                   3282   0.0   41   39   200  149.5  74.8  133   34   33  66.5  16.5  3090
   2 Achillees                   3264  18.4   40   39   200  144.5  72.2  129   40   31  64.5  15.5  3090
   3 gopher_check                3196  67.7   37   36   200  130.5  65.2  104   43   53  52.0  26.5  3090
   4 zahak_next                  3090 106.2   16   16  1200  576.5  48.0  461  508  231  38.4  19.2  3102
   5 zahak-darwin-amd64-latest   3066  24.5   34   35   200   92.5  46.2   60   75   65  30.0  32.5  3090
   6 vice                        2911 154.4   38   40   200   54.0  27.0   37  129   34  18.5  17.0  3090
   7 rustic                      2890  21.1   41   43   200   52.5  26.2   45  140   15  22.5   7.5  3090
---------------------------------------------------------------------------------------------------------
  Δ = delta from the next higher rated opponent
  # = number of games played
  Σ = total score, 1 point for win, 1/2 point for draw

Zahak 2.0.0 should fullfil the promise


net/http: error unwrapping broken on readLoopPeekFailLocked

What version of Go are you using (go version)?

$ go version
go version go1.19.2 linux/amd64

Does this issue reproduce with the latest release?
Yes
What operating system and processor architecture are you using (go env)?
go env Output
$ go env
GO111MODULE=""
GOARCH="amd64"
GOBIN=""
GOCACHE="/home/circleci/.cache/go-build"
GOENV="/home/circleci/.config/go/env"
GOEXE=""
GOEXPERIMENT=""
GOFLAGS=""
GOHOSTARCH="amd64"
GOHOSTOS="linux"
GOINSECURE=""
GOMODCACHE="/home/circleci/go/pkg/mod"
GONOPROXY=""
GONOSUMDB=""
GOOS="linux"
GOPATH="/home/circleci/go"
GOPRIVATE=""
GOPROXY="https://proxy.golang.org,direct"
GOROOT="/usr/local/go"
GOSUMDB="sum.golang.org"
GOTMPDIR=""
GOTOOLDIR="/usr/local/go/pkg/tool/linux_amd64"
GOVCS=""
GOVERSION="go1.19.2"
GCCGO="gccgo"
GOAMD64="v1"
AR="ar"
CC="gcc"
CXX="g++"
CGO_ENABLED="1"
GOMOD="/dev/null"
GOWORK=""
CGO_CFLAGS="-g -O2"
CGO_CPPFLAGS=""
CGO_CXXFLAGS="-g -O2"
CGO_FFLAGS="-g -O2"
CGO_LDFLAGS="-g -O2"
PKG_CONFIG="pkg-config"
GOGCCFLAGS="-fPIC -m64 -pthread -Wl,--no-gc-sections -fmessage-length=0 -fdebug-prefix-map=/tmp/go-build2218043753=/tmp/go-build -gno-record-gcc-switches"

What did you do?

Here's my repro that only seems to work on Linux: https://go.dev/play/p/k305YHkn2QM
You can run it a couple of times to get results like this:
Get "http://localhost:35633": write tcp <IP_ADDRESS>:52368-><IP_ADDRESS>:35633: use of closed network connection
in chain: false
Get "http://localhost:35633": read tcp <IP_ADDRESS>:52368-><IP_ADDRESS>:35633: use of closed network connection
in chain: true
Get "http://localhost:35633": read tcp <IP_ADDRESS>:52368-><IP_ADDRESS>:35633: use of closed network connection
in chain: true
Get "http://localhost:35633": readLoopPeekFailLocked: read tcp <IP_ADDRESS>:52368-><IP_ADDRESS>:35633: use of closed network connection
in chain: false
Get "http://localhost:35633": write tcp <IP_ADDRESS>:52368-><IP_ADDRESS>:35633: use of closed network connection
in chain: false

What did you expect to see?
I expected net.ErrClosed to always be part of the error chain
What did you see instead?
It looks like for the write tcp and readLoopPeekFailLocked the error chain can't be unwrapped entirely.

i can make a PR for this!

cc @neild

These code paths all long predate error wrapping.
I'm happy to review a CL fixing the wrapping in places where we're getting it wrong now.


Updated to include Karate web testing framework

Karate- has its own DSL and specifically targeted at web services integration testing
https://github.com/intuit/karate

Thanks bhau👍🏼👍🏼
On Wed, Apr 18, 2018 at 6:48 PM Viraj G. Kulkarni (विराज गु. कुलकर्णी) <
<EMAIL_ADDRESS>wrote:

Merged #2 https://github.com/virajkulkarni14/awesome-cucumber/pull/2.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/virajkulkarni14/awesome-cucumber/pull/2#event-1582765843,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABXmDJJZFazNkkFIX-l452UvhhGz3Sbiks5tp-zZgaJpZM4TU0iW
.

--
Regards,
Sushrut Hajirnis
Phone :<PHONE_NUMBER>
LinkedIn https://www.linkedin.com/in/sushruthajirnis


Coupling between RSGI and asyncio

The spec refers explicitly to an asyncio event loop here and here.
Is this intentional? This seems to shut out possible use of anyio and/or trio.

Given at the moment Granian is the only server implementation of RSGI, the spec and Granian code are quite tightened.
Granian doesn't support any async implementation other than asyncio, as several parts of its internals interacts or mimic asyncio specific methods or objects.
Personally I have not enough experience with trio to state wether a compatibility layer can be added to Granian in future; it's also unclear to me wether we'll see other RSGI servers popping up in the future. So probably the best approach here is to wait until a server implements support for trio and thus we can update the spec accordingly. Changing the spec before that might led to conditions in which that spec is hard to implement or just badly designed.

It seems to me that coupling a server specification to a backing async implementation so tightly will 100% mean a (heavily) breaking change in the future, and more or less shuts out anyio and trio users permanently?
note: I have no horse in this race; just want to clarify the intended direction of the project.

It seems to me that coupling a server specification to a backing async implementation so tightly will 100% mean a (heavily) breaking change in the future

That's not necessarily an issue. RSGI has a {major}.{minor} version spec, nothing prevents us to issue a new major version of the protocol spec to introduce breaking changes. And I don't see any reason why to be worried right now about it anyways..

and more or less shuts out anyio and trio users permanently?

True. But again: there's no spec/integration facilities for anyio/trio in PyO3 nowadays; nor specific interest into the relevant communities do introduce those.
anyio can be used with Granian/RSGI without any issue, given the underlying impl is using asyncio.
And for the trio compatibility, to me unless a big number of RSGI applications out there (which again, no frameworks provide use for the protocol except for Emmett) start asking for such compatibility, and the relevant involved communities (trio and pyo3) are willing to help on that, I don't see this becoming a priority in the near future. So.. again, why should we worry about this and introduce additional abstraction layers over the protocol today? – which also means we might still need to change those in the future, given the uncertainty.
Does this make sense to you @marcuslimdw?


Cannot read properties of undefined (reading 'forEach')

Describe the bug
Clicking "detect from image" or "add background image" throws error in console.
To Reproduce
Click one of the buttons
Expected behavior
No errors
Additional context
Uncaught (in promise) TypeError: Cannot read properties of undefined (reading 'forEach')
    at st (index.4395ab38.js:76:2728)

Below, data is undefiend
function st(xt) {
    xt.data.forEach((dt,Gt)=>{
        if (typeof dt == "object" && dt !== null && dt.__type__ === "update") {
            for (const [zt,Lt] of Object.entries(dt))
                zt !== "__type__" && n(11, L[jt[Gt]].props[zt] = Lt, L);
            n(9, m)
        } else
            n(11, L[jt[Gt]].props.value = dt, L)
    }
    )
}

after today update still same :c

I've done a bit of research and it seems that this is a problem on the gradio side as per https://github.com/AlUlkesh/stable-diffusion-webui-images-browser/issues/28
So I'll wait for the gradio fix.

I guess it's not bugs,  that the  model doesn't exist
https://huggingface.co/lllyasviel/ControlNet/tree/main/models


feat(clusters): add new endpoint for clusters duplication

This branch only contains the back-end part.
One thing to note is that the code doesn't work for short term storages on variants (it doesn't update the matrix).
That bug will be fixed when this PR is merged : https://github.com/AntaresSimulatorTeam/AntaREST/pull/1971

@skamril @MartinBelthle There is issues with variant studies. I am working on it. Stay tuned!

By correcting the duplication of thermal and renewable clusters and short-term storage for the study variants, I also found an anomaly that I have corrected. This was an issue concerning the saving of short-term storage matrices: matrices were being saved directly in the variant's snapshot instead of generating commands.

Related to #1971


Incorrect webpage link display on hover

On the "Phaser" page under the "Effect" menu the webpage link that gets displayed on hovering over the term "Wikipedia" in line 2 of the contents is incorrect. There is a closing bracket missing from the displayed link.
(Observe the bottom left corner of the webpage)

Current link: https://en.wikipedia.org/wiki/Phaser_(effect
Correct link: https://en.wikipedia.org/wiki/Phaser_(effect)

@prachiagrawal269 Good catch. Thanks! Seems like there's a problem with the way i'm parsing markdown links when i generate the docs. I'll take care of that soon.

@tambien I tried using markdown livedemo (referred link: http://markdown-here.com/livedemo.html)
and this is what I found:

I think the problem is with the way the markdown translation works. May be during the translation the webpage link that is being considered is until the occurence of the first closing round bracket (instead of matching valid parenthesis).
One hack to this problem could be the following:

Basically replacing the round brackets with square brackets along with giving index to the referred webpage link ([1] in this case) and inserting that index in the second set of squared brackets might work.

New docs and the link issue is fixed in the latest. It had to do with the way that i was processing markdown which should be corrected now.


Update tables.md

corresponding docs to: table-responsive change:
removed 100% width in combination with block, it will break the float in grids and alignments and always clear the preceding. Also the .table-responsive cannot be applied to the <table> as display: block; breaks the automatic column width resizing. It should be applied to a wrapping div for overflow and above problems to work correctly

Superseded by #22217


utils, decouple

Codecov Report

Merging #29 (6a25b57) into master (d7a5e5a) will increase coverage by 2.78%.
The diff coverage is 64.76%.

@@            Coverage Diff             @@
##           master      #29      +/-   ##
==========================================
+ Coverage   67.01%   69.79%   +2.78%
==========================================
  Files           2        3       +1
  Lines         194      192       -2
==========================================
+ Hits          130      134       +4
+ Misses         64       58       -6

Flag
Coverage Δ

unittests
69.79% <64.76%> (+2.78%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

src/twitter_network.py
64.39% <47.61%> (-2.08%)
:arrow_down:

src/core.py
71.79% <80.95%> (ø)

utils/api/twitter.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Fixed NPE on new json

NPE caused because baseJs absent on new json, this PR is fixing this, we just grab it from embed page

I'm assuming this will still break for videos with the new json response but embedding disabled?

@Devoxin If video with disabled embedding it still provide baseJs

Ah, very good to know. LGTM


Osc and VRC wont connect

Hey i bought your toggle and followed the whole tutorial process and everything, it worked just fine until i looged out of vrchat and the next day in vrchat. i looked for trouble solving even deleted the OSC in %appdata% etc on your gumroad but nothing.. it just wont work, it shows the toggle from the vrc pishock controller in the osc debug, the pishocker reacts to the controller on the website but vrchat just dont send infos to the osc like i can turn it off and on over and over again but it wont give me a notification that it sends to the osc... which means it just dont work anymore for me i tried it on a different avatar. same problem nothing helps i tried recreating everything. nothing...please i need help

Was resolved in private.


modify the logging module

replace the manual logging module with python package "logging.Logger"

Hi @zzzzwj, thanks for the PR!
Could you provide a snippet of the logging results ?

Hi @zzzzwj, thanks for the PR!
Could you provide a snippet of the logging results ?

Of course, yes. Here is an example output logging by running examples/classification_cifar10_cnn.py.

Anyway you can define your own logger by configuring logging.Logger like that in utils.get_default_logger() if you don't like the logging format.

Of course, yes. Here is an example output logging by running examples/classification_cifar10_cnn.py.

Anyway you can define your own logger by configuring logging.Logger like that in utils.get_default_logger() if you don't like the logging format.

Looks great! I will take a look at your codes latter :-)

Looks great! I will take a look at your codes latter :-)

Hi @zzzzwj, I have left several comments on your submitted code.
Let me know if solving these comments would be better, and always open for discussion.

Hi @zzzzwj, I have left several comments on your submitted code.
Let me know if solving these comments would be better, and always open for discussion.

Thanks, the logger looks much better now :-).
Here is a problem: It looks like that the logging results were printed twice, could you fix it ?

Thanks, the logger looks much better now :-).
Here is a problem: It looks like that the logging results were printed twice, could you fix it ?


Add structure for additional cloud providers.

Hi
I like to see what the recommended folder structure would look like, if additional cloud providers were to be used. Some environment parameters could be consistent across clouds.
I think some scenarios may be difficult to represent. For example, maybe I have an EKS cluster in prod on AWS and a GKE cluster in prod on GCP. But perhaps, I wish to use terraform to deploy the same Helm Chart or K8s resources to these clusters. How could I represent that best, where the helm values could be shared across clouds but also overridden for specific values.
Thank you

What approach did you take on this?, we have plans to use as well GKE and we don't know yet how to locate our Terraform/Terragrunt folder


Open specific component of  if a push notification is received when the application is in background

How can I navigate to a specific component if a notification is received when the application is in background?
I could easily do this when the notification is opened manually, i.e. notification is received and user has tapped on the notification to open it.
I can even do this when the app is in foreground. I just add onReceived event listener described.
But my question is how can I automatically open the application and navigate to a particular component when a notification is received?

@mostafiz93 It sounds like you want to launch your app as soon as a notification is received, not when it is tapped on. It is only recommend that this is own if you are making a calling app. This is explained in the following issue.
https://github.com/geektimecoil/react-native-onesignal/issues/312


Java 9 support

In an email exchange today with one of the Jetty developers, I was told that Jetty 9.3 will be tracking Java 9 to take advantage of its built-in support for ALPN.
It doesn't look like openjdk-9-* packages for Debian Sid are even a glimmer in anyone's eye yet, so perhaps this would be the time to start to exploring compilation from source.
Based on the comments in the Dockerfile, it looks like the objections to doing a source build revolved around the need to install a bootstrap JDK and Oracle's licensing. It looks like installing a boostrap JDK is still a requirement in the current jdk9 build (cf. http://hg.openjdk.java.net/build-infra/jdk9/file/50da9851d248/README-builds.html#l352).

There's https://bugs.debian.org/751519, but it was shot down for openjdk-8 being available; no idea WTF that's about. :confused:

Yeah, that's a bit odd. Perhaps it makes more sense to someone more involved in the Debian Java community.
I started looking into the situation a bit more and it looks like they only want to have a single default JDK per Debian release, so openjdk-9 will presumably not be available until Debian 10...

I think "NEW" is this: https://wiki.debian.org/NewQueue
And from my reading it looks like they don't want openjdk-9 in "NEW" until openjdk-8 is out. And I think openjdk-8 moving out of "NEW" may be dependent on this: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=760984
So it seems that openjdk-8 will likely be part of Debian 9/Stretch, at which point openjdk-9 can go into Sid.

The fact that an "openjdk-8" package is available for installing means it's
moved out of NEW already. :disappointed:

And looking at https://packages.debian.org/sid/openjdk-8-jdk, it's clear
it's not available in Jessie, which means they must be targeting Stretch.

There's a thread on debian-java about the plans for Java in Stretch: https://lists.debian.org/debian-java/2015/04/msg00082.html

Wow, even adding "Ensure our openjdk-8 package passes the TCK";
they're definitely getting ambitious!
(cc @jpetazzo)

Indeed! I hope this'll also make @giltene happier with the current state of Java-on-Docker :-)

This was fixed in https://github.com/docker-library/openjdk/pull/55. :+1:

@tianon For some reason I missed this last month, but I thought I'd check if you guys have an ETA or any expectations for an Alpine variant for OpenJDK 9.

It looks like I commented on the PR itself back in November 2015 though 😕

As soon as https://pkgs.alpinelinux.org/packages?name=openjdk9* returns something (ie, there's an Alpine package for it), so can't actually say for certain. :disappointed:


hb-service update-node error

Describe The Bug
hb-service update-node error
Logs
sudo hb-service update-node
/opt/homebridge/lib/node_modules/homebridge-config-ui-x/dist/bin/hb-service.js:796
        const currentLts = versionList.filter(x => x.lts)[0];
                                       ^

TypeError: versionList.filter is not a function
    at HomebridgeServiceHelper.checkForNodejsUpdates (/opt/homebridge/lib/node_modules/homebridge-config-ui-x/dist/bin/hb-service.js:796:40)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)

Node.js v20.9.0

Config
No response
Homebridge UI Version
4.52.3
Homebridge Version
latest
Node.js Version
20.09
Operating System
Raspberry Pi OS / Raspbian
Environment Info

[ ] Using Docker?
[ ] Using Hyper-V?
[X] Using hb-service?

Raspberry Pi Model
Raspberry Pi 4 B

Working on a fix for this.
As a workaround, can you try downgrading to 4.52.0 and then update-node and then update homebridge-config-ui-x

Ended up working after four or five tries. I do not know why.
Thank you for all.

We think it was a temporary issue with the node website that wasn’t returning a version list properly. So not particular to any version of homebridge or the ui.
we will add a check for this in our code to handle this more gracefully in the future if it happens again.


Allow for helper function calls within prompt

Helper functions were not in scope when validate would call the function defined for prompt. Now you can access them, but you have to use a passed terminal object.
Example:
prompt: function (cb, term) {
	cb(term.login_name() + " >");
}

I'd prefer prompt being able to use this, but I had some difficulty pulling that off. Unsure if something will come to mind, but this patch has solved the immediate issue I'm having.
For reference, the error I get looks like this:
00:00:00 test@localhost ~ derp
command not found: derp
[PROMPT]: this.login_name is not a function
TypeError: this.login_name is not a function
    at prompt (http://localhost:4567/:49:89)
    at validate (http://localhost:4567/js/jquery.terminal.js:3765:21)
    at ready (http://localhost:4567/js/jquery.terminal.js:5238:25)
    at DelayQueue.add (http://localhost:4567/js/jquery.terminal.js:200:17)
    at init.set_prompt (http://localhost:4567/js/jquery.terminal.js:5237:17)
    at init.set_prompt (http://localhost:4567/js/jquery.terminal.js:5893:32)

Looks like this is a Window object when called from validate. You can reproduce this in the current version by using the example function below, just dropping in this for term.

Coverage remained the same at 79.325% when pulling a9878359694c5779259c1723ff263bfcbc078f60 on nicholaswold:master into cd61c893c51fb0c3dcb226f6f7ea4eb0b8153e5f on jcubic:master.

One more thing, if you making a change please use devel branch on fork and create pull request to devel branch as well.
Master is always latest version and devel is for next version. Sometimes I've used master branch (when I had one bug fix) but I'll try to only use devel branch for development.

I've resolved the issue with prompt in devel branch, sorry that I give you the chance to fix it yourself.


Embedded toolchain paths aren't digestable by gromacs_check_compiler

(@junghans how does the conda-forge votca handle this? Does it just use an arbitrary compiler and not run the check_compiler() function?)

VOTCA's CMake runs check_cxx_compiler_flag(), but we haven't seen any problems with gromacs yet.

Sorry. I was vague and inaccurate. Historically, GROMACS recommended that client software run gromacs_check_compiler(CXX) as in https://gitlab.com/gromacs/gromacs/-/blob/main/share/template/CMakeLists.txt.template, but this generally hasn't worked when gromacs was installed with conda (because the embedded toolchain paths are as seen during the isolated conda-build).
I'm assuming VOTCA doesn't use the gromacs_check_compiler(), then. Do you do anything else to ensure a compatible toolchain? Maybe it just tend to work fine with default conda build tools?
Originally posted by @eirrgang in https://github.com/conda-forge/gromacs-feedstock/issues/10#issuecomment-1239615783

@eirrgang - unfortunately I'm not working on this project anymore, so don't have much time to do more than maintain the current releases.
But, could you post below examples of what output you get when using gromacs_check_compiler on standard gromacs installs, and conda installed gromacs, so that other developers could look into this?

Installing gromacs from conda-forge, the compiler reported by gmx --version is not a locally available compiler.
(issue11) MacBook-Pro:~ eric$ gmx --version
                   :-) GROMACS - gmx, 2022.2-conda_forge (-:

Executable:   /usr/local/Caskroom/miniconda/base/envs/issue11/bin.AVX2_256/gmx
Data prefix:  /usr/local/Caskroom/miniconda/base/envs/issue11
Working dir:  /Users/eric
Command line:
  gmx --version

GROMACS version:    2022.2-conda_forge
Precision:          mixed
Memory model:       64 bit
MPI library:        thread_mpi
OpenMP support:     enabled (GMX_OPENMP_MAX_THREADS = 128)
GPU support:        disabled
SIMD instructions:  AVX2_256
CPU FFT library:    fftw-3.3.10-sse2-avx
GPU FFT library:    none
RDTSCP usage:       enabled
TNG support:        enabled
Hwloc support:      disabled
Tracing support:    disabled
C compiler:         /Users/runner/miniforge3/conda-bld/gromacs_1657275317958/_build_env/bin/x86_64-apple-darwin13.4.0-clang Clang 13.0.1
C compiler flags:   -mavx2 -mfma -Wno-missing-field-initializers -O3 -DNDEBUG
C++ compiler:       /Users/runner/miniforge3/conda-bld/gromacs_1657275317958/_build_env/bin/x86_64-apple-darwin13.4.0-clang++ Clang 13.0.1
C++ compiler flags: -mavx2 -mfma -Wno-reserved-identifier -Wno-missing-field-initializers -Weverything -Wno-c++98-compat -Wno-c++98-compat-pedantic -Wno-source-uses-openmp -Wno-c++17-extensions -Wno-documentation-unknown-command -Wno-covered-switch-default -Wno-switch-enum -Wno-extra-semi-stmt -Wno-weak-vtables -Wno-shadow -Wno-padded -Wno-reserved-id-macro -Wno-double-promotion -Wno-exit-time-destructors -Wno-global-constructors -Wno-documentation -Wno-format-nonliteral -Wno-used-but-marked-unused -Wno-float-equal -Wno-conditional-uninitialized -Wno-conversion -Wno-disabled-macro-expansion -Wno-unused-macros -fopenmp=libomp -O3 -DNDEBUG

Unusable toolchain paths are also embedded in the installed gromacs-config.cmake and gromacs-hints.cmake files.
Effects
If someone tries to use the compiler named by gmx --version or gromacs-hints.cmake, they will get an error that includes text like the following.
      CMake Error at CMakeLists.txt:42 (project):
        The CMAKE_CXX_COMPILER:

          /Users/runner/miniforge3/conda-bld/gromacs_1657275317958/_build_env/bin/x86_64-apple-darwin13.4.0-clang++

        is not a full path to an existing compiler tool.

If they specify a valid CMAKE_CXX_COMPILER and try to build the sample code from https://gitlab.com/gromacs/gromacs/-/tree/main/share/template or https://gitlab.com/gromacs/gromacs/-/tree/main/python_packaging/sample_restraint, or a dependent package that uses the boiler plate from https://gitlab.com/gromacs/gromacs/-/blob/main/share/template/CMakeLists.txt.template, CMake (from gromacs_check_compiler) will issue a warning like the following.
CMake Warning at /usr/local/Caskroom/miniconda/base/envs/issue11/share/cmake/gromacs/gromacs-config.cmake:139 (message):
  You are compiling with a different C++ compiler from the one that was used
  to compile GROMACS.  This may lead to linking or runtime problems.  GROMACS
  was compiled with Clang 13.0.1
  (/Users/runner/miniforge3/conda-bld/gromacs_1657275317958/_build_env/bin/clang-13).

I believe the Spack recipe is now using a feature that replaces toolchain paths on installation. I couldn't find such a tool for conda-build the last time I looked.

(@junghans how does the conda-forge votca handle this? Does it just use an arbitrary compiler and not run the check_compiler() function?)

VOTCA's CMake runs check_cxx_compiler_flag(), but we haven't seen any problems with gromacs yet.

Sorry. I was vague and inaccurate. Historically, GROMACS recommended that client software run gromacs_check_compiler(CXX) as in https://gitlab.com/gromacs/gromacs/-/blob/main/share/template/CMakeLists.txt.template, but this generally hasn't worked when gromacs was installed with conda (because the embedded toolchain paths are as seen during the isolated conda-build).
I'm assuming VOTCA doesn't use the gromacs_check_compiler(), then. Do you do anything else to ensure a compatible toolchain? Maybe it just tend to work fine with default conda build tools?

In VOTCA we don't check and never have. So far no big problems hence I am not pushing for it.


Deletion

Handle in WARP
Handle in B+ Tree. Set value to Nothing. Our approach to handle deletion is to mark the deleted values as Nothing. The key will stay in the data store. Once in a while (may be a month), the data store will reconstruct to clean out AriaKVs with value as Nothing
Library

Handled in Warp ✓
Handled in BPT ✓
Library : will do soon


Expect a int but got a float64 from values.yaml

What happened
Hello, I want to take a integer value from values.yaml to control the looping times of a range block in my templates. Let's say I set count: 1 in values.yaml. Commonly it should be inferred to a integer, but when I run helm install, .Values.count is envalued to a float64 type.
And I have to use pipeline function as a workaround.
{{ $count := .Values.count | int }}
{{ range until $count }}
    count to {{.}}
{{ end }}

I've checked the docs, but I'm not sure if values.yaml applies the same rule. Is that a expected behavior? And if it is, while the pipeline function like int is sometimes necessary but not mentioned directly in helm's document. Is that a good idea to add some additional example for it?
How to reproduce
$ cat test-helm.sh
mkdir -p templates
echo """
apiVersion: v1
description: helm template test
name: helm-template-test
version: 0.1.0
""" > Chart.yaml
echo """
{{- range until .Values.count }}
	test={{.}}
{{- end }}
""" > templates/test.yaml
echo """
count: 3
""" > values.yaml

$ ./test-helm.sh
$ helm install -n test-helm . --dry-run --debug
[debug] Created tunnel using local port: '33823'

[debug] SERVER: "<IP_ADDRESS>:33823"

[debug] Original chart version: ""
[debug] CHART PATH: /root/gitlab/cubes/charts/test-helm

Error: render error in "helm-template-test/templates/test.yaml": template: helm-template-test/templates/test.yaml:2:23: executing "helm-template-test/templates/test.yaml" at <.Values.count>: wrong type for value; expected int; got float64

Output of helm version:
helm version
Client: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.9.1", GitCommit:"20adb27c7c5868466912eebdf6664e7390ebe710", GitTreeState:"clean"}

Output of kubectl version:
$ kubectl version
Client Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.1", GitCommit:"4ed3216f3ec431b140b1d899130a69fc671678f4", GitTreeState:"clean", BuildDate:"2018-10-05T16:46:06Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"12", GitVersion:"v1.12.1", GitCommit:"4ed3216f3ec431b140b1d899130a69fc671678f4", GitTreeState:"clean", BuildDate:"2018-10-05T16:36:14Z", GoVersion:"go1.10.4", Compiler:"gc", Platform:"linux/amd64"}

Cloud Provider/Platform (AKS, GKE, Minikube etc.):

closing as a duplicate of https://github.com/helm/helm/issues/1707 :) thanks!

change to:
{{ $count := (.Values.count | int) }}
{{ range until $count }}
    count to {{.}}
{{ end }}


Do not fix numpy version

Thanks a lot for your work on dsfaker.
numpy version was fixed to a specific version, which prevented me to use dsfaker in another library because of version conflict.

Codecov Report

Merging #13 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master      #13   +/-   ##
=======================================
  Coverage   96.85%   96.85%
=======================================
  Files          14       14
  Lines         700      700
=======================================
  Hits          678      678
  Misses         22       22

Continue to review full report at Codecov.

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

Hi @pajachiet, thanks a lot :) merging

Thanks a lot for your quick merge !
tsfaker setup.py shoud work when you update dsfaker on pypi :)

@pajachiet It is updated to the last 0.2.3 version on pypi


Upgrade from 0.84.6 fails on typing_extensions

Home Assistant release with the issue:

0.84.6
Last working Home Assistant release (if known):
0.84.6
Operating environment (Hass.io/Docker/Windows/etc.):

Raspberry pi / raspbian/virtualenv
Component/platform:

Upgrade package
Description of problem:
Following the upgrade process described here:
https://www.home-assistant.io/docs/installation/virtualenv/#upgrading-home-assistant
The upgrade process script appears to be fine at first, but crashes while trying to move a .pyc file (see bolded text below) when the "Installing collected packages" phase begins.
Below is the terminal output after the crash:
Installing collected packages: typing-extensions, aiohttp, Unidecode, python-slugify, ruamel.yaml, idna, requests, pip, homeassistant
Exception:
Traceback (most recent call last):
  File "/srv/homeassistant/lib/python3.5/site-packages/pip/basecommand.py", line 215, in main
    status = self.run(options, args)
  File "/srv/homeassistant/lib/python3.5/site-packages/pip/commands/install.py", line 360, in run
    prefix=options.prefix_path,
  File "/srv/homeassistant/lib/python3.5/site-packages/pip/req/req_set.py", line 784, in install
    **kwargs
  File "/srv/homeassistant/lib/python3.5/site-packages/pip/req/req_install.py", line 851, in install
    self.move_wheel_files(self.source_dir, root=root, prefix=prefix)
  File "/srv/homeassistant/lib/python3.5/site-packages/pip/req/req_install.py", line 1064, in move_wheel_files
    isolated=self.isolated,
  File "/srv/homeassistant/lib/python3.5/site-packages/pip/wheel.py", line 345, in move_wheel_files
    clobber(source, lib_dir, True)
  File "/srv/homeassistant/lib/python3.5/site-packages/pip/wheel.py", line 323, in clobber
    shutil.copyfile(srcfile, destfile)
  File "/usr/lib/python3.5/shutil.py", line 121, in copyfile
    with open(dst, 'wb') as fdst:
**_PermissionError: [Errno 13] Permission denied: '/srv/homeassistant/lib/python3.5/site-packages/__pycache__/typing_extensions.cpython-35.pyc'_**
(homeassistant) pi@JONASRPI:/srv/homeassistant $

Problem-relevant configuration.yaml entries and (fill out even if it seems unimportant):

Traceback (if applicable):

Additional information:

Closing due to lack of input.


Spotify specs

What Redirect URI should we include?

Hello
Sorry about that, i will update the documentation tomorrow
The redirect uri is : obsidian://spotify-auth/

Updated the documentation at :
https://studiowebux.github.io/obsidian-plugins-docs/docs/spotify-link/configuration/
Thanks for reporting this !

Thanks. It's still not connecting. Should tick a particular API in the second part of the screen?

Yes it should open your browser to authorize the application.
After copying the client id and secret id in the obsidian plugin settings,
you can click the Spotify logo (left bar in obsidian)
then it will open the browser (I tested only on Iphone and MacOS, so in my case it is Safari)
Then you need to authorize the app and after that it will go back automatically to obsidian (using the redirect URI) to setup the login. and you should see a popup saying successfully connected (same as in the footer in obsidian, only on desktop app)
Extra details:
Optionally you can change the  state
You should not have to change the Scopes
Let me know if you have issues following these steps
thanks!

Thanks. It was clicking on the Spotify logo which was the missing step. You
might like to highlight that.
It would be great to be able to customise the information from Spotify to
be able to include details like album name, but not track progress.
I look forward to seeing how you develop this useful plugin.
Kevin
On Sat, 25 Nov 2023 at 10:55, Tommy Gingras @.***>
wrote:

Yes it should open your browser to authorize the application.
After copying the client id and secret id in the obsidian plugin
settings,
you can click the Spotify logo (left bar in obsidian)
then it will open the browser (I tested only on Iphone and MacOS, so in my
case it is Safari)
Then you need to authorize the app and after that it will go back
automatically to obsidian (using the redirect URI) to setup the login. and
you should see a popup saying successfully connected (same as in the footer
in obsidian, only on desktop app)
Extra details:
Optionally you can change the state
You should not have to change the Scopes
Let me know if you have issues following these steps
thanks!
—
Reply to this email directly, view it on GitHub
https://github.com/studiowebux/obsidian-spotify-link/issues/2#issuecomment-1826148081,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARTR6N7TJWWNNNMKHNAM74DYGEXYLAVCNFSM6AAAAAA7XHFWZ6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQMRWGE2DQMBYGE
.
You are receiving this because you authored the thread.Message ID:
@.***>

I've updated the documentation with screenshots: https://studiowebux.github.io/obsidian-plugins-docs/docs/spotify-link/steps
and improved the "first time setup" page : https://studiowebux.github.io/obsidian-plugins-docs/docs/spotify-link/spotify


NVD_API_TOKEN environment variable does not work

Description
I am using the NVD_API_TOKEN environment variable to provide nvd-clojure with my NVD API key, and it does not work. Using the Clojure Tools method, I should have either expected the scan to proceed, or nvd-clojure to throw an "No NVD API key supplied as config settings or env var." exception. Instead, it seems that nvd-clojure recognizes that the env var was set, but that var is not passed to DependencyCheck. Thus, I get this result (note the first and last lines):
% NVD_API_TOKEN=[REDACTED] clojure -J-Dclojure.main.report=stderr -Tnvd nvd.task/check :classpath \""$(clojure -Spath)\""
[2024-01-31 14:37:19.398] INFO nvd-clojure - User-provided config: {:nvd {:suppression-file "nvd_suppressions.xml", :nvd-api {:key nil}}, :delete-config? false}
Jan 31, 2024 2:37:19 PM org.apache.commons.jcs3.engine.control.CompositeCacheManager
INFO: Instance is null, returning unconfigured instance
Jan 31, 2024 2:37:19 PM org.apache.commons.jcs3.engine.control.CompositeCacheManager
INFO: Setting default auxiliaries to "ODC"
Jan 31, 2024 2:37:19 PM org.apache.commons.jcs3.engine.control.CompositeCacheManager
INFO: setting defaultCompositeCacheAttributes to [ useLateral = true, useRemote = true, useDisk = true, maxObjs = 0, maxSpoolPerRun = -1, diskUsagePattern = UPDATE, spoolChunkSize = 2 ]
Jan 31, 2024 2:37:19 PM org.apache.commons.jcs3.engine.control.CompositeCacheManager
INFO: setting defaultElementAttributes to [ IS_LATERAL = false, IS_SPOOL = true, IS_REMOTE = false, IS_ETERNAL = false, MaxLifeSeconds = 86400, IdleTime = 1800, CreateTime =<PHONE_NUMBER>698, LastAccessTime =<PHONE_NUMBER>698, getTimeToLiveSeconds() = 86399, createTime =<PHONE_NUMBER>698 ]
Jan 31, 2024 2:37:19 PM org.apache.commons.jcs3.engine.memory.AbstractDoubleLinkedListMemoryCache
INFO: initialized MemoryCache for CENTRAL
Jan 31, 2024 2:37:19 PM org.apache.commons.jcs3.engine.control.CompositeCache
INFO: Constructed cache with name [CENTRAL] and cache attributes [ useLateral = true, useRemote = true, useDisk = true, maxObjs = 0, maxSpoolPerRun = -1, diskUsagePattern = UPDATE, spoolChunkSize = 2 ]
Jan 31, 2024 2:37:19 PM org.apache.commons.jcs3.auxiliary.AuxiliaryCacheConfigurator
INFO: No cache event logger defined for auxiliary [jcs.auxiliary.ODC]
Jan 31, 2024 2:37:19 PM org.apache.commons.jcs3.auxiliary.AuxiliaryCacheConfigurator
INFO: Using standard serializer [org.apache.commons.jcs3.utils.serialization.StandardSerializer@476fde05] for auxiliary [jcs.auxiliary.ODC]
Jan 31, 2024 2:37:19 PM org.apache.commons.jcs3.auxiliary.disk.indexed.IndexedDiskCache
INFO: Region [CENTRAL] : Set maxKeySize to: "1,000,000"
Jan 31, 2024 2:37:19 PM org.apache.commons.jcs3.auxiliary.disk.indexed.IndexedDiskCache
INFO: Region [CENTRAL] : Cache file root directory: ~/.m2/repository/org/owasp/dependency-check-utils/9.0.8/data/9.0/cache
Jan 31, 2024 2:37:19 PM org.apache.commons.jcs3.auxiliary.disk.indexed.IndexedDiskCache
INFO: Region [CENTRAL] : Indexed Disk Cache is alive.
Jan 31, 2024 2:37:19 PM org.apache.commons.jcs3.engine.memory.AbstractDoubleLinkedListMemoryCache
INFO: initialized MemoryCache for POM
Jan 31, 2024 2:37:19 PM org.apache.commons.jcs3.engine.control.CompositeCache
INFO: Constructed cache with name [POM] and cache attributes [ useLateral = true, useRemote = true, useDisk = true, maxObjs = 0, maxSpoolPerRun = -1, diskUsagePattern = UPDATE, spoolChunkSize = 2 ]
Jan 31, 2024 2:37:19 PM org.apache.commons.jcs3.auxiliary.AuxiliaryCacheConfigurator
INFO: No cache event logger defined for auxiliary [jcs.auxiliary.ODC]
Jan 31, 2024 2:37:19 PM org.apache.commons.jcs3.auxiliary.AuxiliaryCacheConfigurator
INFO: Using standard serializer [org.apache.commons.jcs3.utils.serialization.StandardSerializer@1df9186f] for auxiliary [jcs.auxiliary.ODC]
Jan 31, 2024 2:37:19 PM org.apache.commons.jcs3.auxiliary.disk.indexed.IndexedDiskCache
INFO: Region [POM] : Set maxKeySize to: "1,000,000"
Jan 31, 2024 2:37:19 PM org.apache.commons.jcs3.auxiliary.disk.indexed.IndexedDiskCache
INFO: Region [POM] : Cache file root directory: ~/.m2/repository/org/owasp/dependency-check-utils/9.0.8/data/9.0/cache
Jan 31, 2024 2:37:19 PM org.apache.commons.jcs3.auxiliary.disk.indexed.IndexedDiskCache
INFO: Region [POM] : Indexed Disk Cache is alive.
Jan 31, 2024 2:37:19 PM org.apache.commons.jcs3.engine.memory.AbstractDoubleLinkedListMemoryCache
INFO: initialized MemoryCache for NODEAUDIT
Jan 31, 2024 2:37:19 PM org.apache.commons.jcs3.engine.control.CompositeCache
INFO: Constructed cache with name [NODEAUDIT] and cache attributes [ useLateral = true, useRemote = true, useDisk = true, maxObjs = 0, maxSpoolPerRun = -1, diskUsagePattern = UPDATE, spoolChunkSize = 2 ]
Jan 31, 2024 2:37:19 PM org.apache.commons.jcs3.auxiliary.AuxiliaryCacheConfigurator
INFO: No cache event logger defined for auxiliary [jcs.auxiliary.ODC]
Jan 31, 2024 2:37:19 PM org.apache.commons.jcs3.auxiliary.AuxiliaryCacheConfigurator
INFO: Using standard serializer [org.apache.commons.jcs3.utils.serialization.StandardSerializer@682e422c] for auxiliary [jcs.auxiliary.ODC]
Jan 31, 2024 2:37:19 PM org.apache.commons.jcs3.auxiliary.disk.indexed.IndexedDiskCache
INFO: Region [NODEAUDIT] : Set maxKeySize to: "1,000,000"
Jan 31, 2024 2:37:19 PM org.apache.commons.jcs3.auxiliary.disk.indexed.IndexedDiskCache
INFO: Region [NODEAUDIT] : Cache file root directory: ~/.m2/repository/org/owasp/dependency-check-utils/9.0.8/data/9.0/cache
Jan 31, 2024 2:37:19 PM org.apache.commons.jcs3.auxiliary.disk.indexed.IndexedDiskCache
INFO: Region [NODEAUDIT] : Indexed Disk Cache is alive.
Jan 31, 2024 2:37:19 PM org.apache.commons.jcs3.engine.control.CompositeCacheConfigurator
INFO: Parsed regions [CENTRAL, POM, NODEAUDIT]
Jan 31, 2024 2:37:19 PM org.apache.commons.jcs3.engine.control.CompositeCacheManager
INFO: Finished configuration in 72 ms.
[2024-01-31 14:37:19.761] WARN NexusAnalyzer - Disabling Nexus analyzer - please specify the URL to a Nexus Server
Checking dependencies for stdin...
  using nvd-clojure: 4.0.0 and dependency-check: 9.0.8
[2024-01-31 14:37:40.641] INFO Engine - Checking for updates
[2024-01-31 14:37:40.648] WARN NvdApiDataSource - An NVD API Key was not provided - it is highly recommended to use an NVD API key as the update can take a VERY long time without an API Key

followed by the NVD download failing due to the lack of an NVD API key.
Version
4.0.0
Java version
11.0.10

Installation compliance

[X] I have read again and made sure that I'm following exactly the instructions for my tool of choice (Leiningen, Clojure CLI, Clojure CLI Tool).
[X] I understand that false positives can be skipped locally and should be reported to DependencyCheck.

Indeed that does work, but I am using nvd-clojure in a context where having a static config file is not very practical.

Furthermore, I realize that there is a related issue: when you execute nvd-clojure without any NVD API key whatsoever, i.e. not set in the config file nor set as an env var, it should terminate after throwing the "No NVD API key supplied as config settings or env var." exception. However, instead, just like with the first example, nvd-clojure thinks there is a env var, so that exception is not thrown, and the error is only noticed at the DependencyCheck level.

Yes, I had noticed, sorry about that as well.
You might want to generate the .edn file dynamically for now.
The fix should be small anyway and can land soon.

Indeed, you might've already found the bug, but it's a one line fix. Specifically this line (since the ::not-found does not apply when the value is nil instead of nonexistent).

If you are willing to go through a local install process and verify it works, extending the integration test as well, PR welcome
But the hint is appreciated anyway!

I seem to be hitting this as well, but putting the into my nvd-clojure.edn doesn't help, I get the same errors. I've verified that my token is correct, following the instruction.

Hi @hlship , I've used successfully nvd-clojure with an api key in Lein and deps.edn projects alike.
May you share your config file redacted?

Actually, the code is public:

https://github.com/pedestal/pedestal

clj -T:build cve-check builds the classpath, then invokes NVD to do the work.

This is a file that I've verified to work:
https://github.com/akvo/unep-gpml/blob/3a9782e9e7e7cc1154219f6a3f78d64deb578a63/backend/.nvd/nvd.edn
I don't consider the API keys incredibly secret btw, they are more akin to a username. Cheap to obtain with no PII associated. But one could still build them dynamically if that felt more adequate.

@hlship are you sure it's an issue with the API token ? If you verified it and it's not present in the config file it should work. It could be this problem instead: https://github.com/rm-hull/nvd-clojure/pull/179


Documentation misspelling

Badges -> Dropdown ->http://materializecss.com/badges.html#collections In code semple exist redundat  instead
http://screencloud.net/v/fTgj

I don't know what you're talking about

please look on screenshot http://screencloud.net/v/fTgj   4th line here closing tag  without opening it.
This is lint issue also. because it is not correct to use  directly in .

Already fixed by #1232


[BUG] Navbar options are not visible in light/system theme

Change the style (CSS) of navbar options

@mehul-m-prajapati
go for it


Wrong property comment/description in AzureFileLoggerOptions

Property FileName has the same description/comment as property RetainedFileCountLimit:
https://github.com/aspnet/Logging/blob/master/src/Microsoft.Extensions.Logging.AzureAppServices/AzureFileLoggerOptions.cs

Good find! This issue is up-for-grabs in case anyone would like to send a PR. This is a pretty easy one to get started with!


Remove tabindex from main element

Reverts https://github.com/alphagov/govuk_elements/pull/225
See: https://github.com/alphagov/govuk_template/pull/321
Putting tabindex on the <main> element causes different problems:

Some apps will display the browser's default focus styles around the main element
When clicking anywhere in the page focus will return back to the top

Consider a user interacting with an input field who clicks away from it to remove
the focus style. Should they then hit tab they will be taken to the top of the page.
The linked to browser bug was fixed in Apr. Testing on Safari 10.1.1 it works with VoiceOver on desktop. Testing on iOS 10.2.1 it works in mobile Safari with VoiceOver on.
More context around the issue:
https://github.com/twbs/bootstrap/issues/20732
Example problem
GIF showing focus styles and tab order problem on Registers:

It looks like all the browser vendors have fixed the bug that was the reason for this. But it would be good to have a list of all the browsers this was tested in.

I commented over on GOV.UK template - this was added as a fix to ensure the target of the skiplink was focussed. If this is no longer an issue - I'm happy for this code to be deleted.

@gemmaleigh As we don't control the HTML of pages, should we leave in the outline rule within layout.scss?

@fofr can we leave it in for now and add a comment that the tabindex attribute is no longer required, then we can remove it in a later release?

@gemmaleigh 👍  @fofr can you update please? This seems fairly important would be good to get a new release out.

@gemmaleigh @nickcolley outline kept in but deprecated in 5bdc062

thanks @fofr 👍

And no-one has checked in which browsers it actually works? I would think that's vital.

@selfthinker IMO the bug this introduced was worse than the one it fixed. Which makes it less vital.
Tested on:

Safari 10.1.1 it works with VoiceOver on MacOS Sierra
iOS 10.2.1 and 10.3.3 it works in mobile Safari with VoiceOver on

These were the browsers the bug fix appeared to target.


M5Stack Core2's fixes, partial TouchPanel support  (part 1) , initialization of external I2C PortA, TO-DOs

M5Stack Core2's public static partial class M5Core2 PARTIAL initialization fixes and TO-DOs:

Description

There are bugs and missing stuff, the proposed changes are just the starting point to fix them all:
The Core2 external I2C port A  as documented in https://docs.m5stack.com/en/core/core2 uses GPIO 32 and 33
additionally GPIO 39 is used as INT output from Touch panel chip FT6336
Check TO-DO remarks for things to do next.
I commented out old code that must be disabled i.e. wrongly assigned GPIO pins

Motivation and Context

I am trying to help solving the current missing stuff on M5 Stack Core2
The first issue would allow to use/attach external I2C devices on PortA because the first I2C bus is used internally only
The second issue is the starting point to add support for Core2 Touch Panel
The proposed changes could not be tested nor completely solve the problems at hand; i hope it will help the next contributor
complete all the necessary tasks (See //TO-DO comments)

Fixes/Closes/Resolves nanoFramework/Home#NNNN

How Has This Been Tested?

As i said, i have NOT being able to test any of the proposed modifications

Screenshots
Types of changes

[x] Improvement (non-breaking change that improves a feature, code or algorithm)
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Config and build (change in the configuration and build system, has no impact on code or features)
[ ] Dependencies (update dependencies and changes associated, has no impact on code or features)
[ ] Unit Tests (work on Unit Tests, has no impact on code or features)
[ ] Documentation (changes or updates in the documentation, has no impact on code or features)

Checklist:

[ ] My code follows the code style of this project.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.
[ ] I have added tests to cover my changes.
[ ] All new and existing tests passed.

 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.:x: jcabad100 sign nowYou have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for the submission. What I propose is to implement properly the touch screen and have it added to the IoT.Device repository. This will be reusable. Like this, the touch is not really useful. If you want to raise an event, there is a different way to do it. Also, I'm quite sure that if the touch screen is not setup properly, interrupts won't be activated.
I found the datasheets for it, one is the register (an Excel file :-)). All seems quite ok and will require work but doesn't seem too long.

and what happened with this old PR?

and what happened with this old PR?

It's here... not sure exactly what you wanted to know about it...

@jcabad100 closing this one as present in the latest changes.


Next major version 2.0.0: Switch to runtime value definitions

Addression https://github.com/simonlmn/can-wifi-gateway-stiebel-eltron/issues/5. See comments there for preliminary documentation.
API and UI documentation need to be updated / extended and the UI is very limited. But since the UI was never meant for more complex interactions and is rather poorly written, the effort to make this more user-friendly and comfortable may mean to rewrite that from scratch...

I installed the 2.0alpha today and it seems that it worked like expected. Only thing which is missing is the "how to do the config file". Installation was without problems.

Good morning,
Can anyone give me the HTTP command to write a value.
Example on the hot water writing instruction:
items>SYS>'0'>'19'>value
THANKS
Nicolas

Good morning, Can anyone give me the HTTP command to write a value.
Example on the hot water writing instruction: items>SYS>'0'>'19'>value
THANKS Nicolas

Writing works by sending a PUT request to /api/data/{deviceType}/{address}/{valueId}, so in your case /api/data/SYS/0/19. In addition, you need to provide the "accessMode" configured for the datapoint in the "accessMode" query parameter, which kind of acts as a safeguard against accidentally writing a value (I am debating if I should remove that as it does not really add any "safety").
The body is the JSON representation of the value to be written (i.e. the same representation as given as the "value" property when reading the data). So for numeric values, something like 123 or 1.23.
So if you have configured the value for writing with the standard "Writable" access mode, the request would look something like this:
PUT /api/data/SYS/0/19?accessMode=Writable
42.5


Fix AOT build, replace angular scaffolding in favour of CLI

Fixed AOT build
Greatly simplified the app scaffolding by using the angular CLI, which gives us an unified way of building apps and modules.
Used angular-library-builder to accomplish up to date building of shareable modules with complete metadata

You can check the update working by using
npm i --save<EMAIL_ADDRESS>

hi @sandman21dan thanks for your effort on this. I will check this later and try to run locally and if everything works I'll merge this. Can you please bump version in package.json so I can publish this later?

@jkuri Bumped version, brough back lots of bits lost from package.json renamed package to original name, and bumped the version.
Should be good to go
Let me know about any issues you might encounter

hi @sandman21dan I am just checking this and when trying to the demo I got ERROR in AppModule is not an NgModule, can you fix it please?

sorry, had to reinstall packages - it does work.
one more thing, can you preserve .sass styles and include it in ng2-datepicker.component.ts as .sass file and remove the compiled .css one?

@jkuri All done, seems like everything works just as expected (neved tried sass rather than scss on the CLI before)

thanks, I would add bundle too but I can add this later. merging.


Upgrade react-scripts to use jest 22

When upgrading jest to v22, our tests (run with react-scripts) break due to react-scripts v1.0.17 still using v20, while v22 added a breaking change, upgrading JSDOM from v9 to v11.
This results in the tests breaking with error TypeError: environment.setup is not a function. (related issue raised @jest )

You can't "update Jest to v22" while using react-scripts. The point of react-scripts is to hide Jest (and a few other tools) under one umbrella. It is not, and has never been supported to try to install tools directly.
I suppose it's time we start breaking the build when people attempt that. We get too many issues like this when people break their setups.
(As for updating to 22, yes, we'll do that in the near future. We were just waiting for it to come out.)

We track Jest update in https://github.com/facebookincubator/create-react-app/issues/2639.
I created a new issue for breaking the build when one attempts to update tools circumventing react-scripts: https://github.com/facebookincubator/create-react-app/issues/3638.
So I think we can close this.


Using "media_ids[]" as key for media_ids is not adding media to status via API

My app is posting status with media. Through testing it seems that Takahe is not recognizing media_ids[] as key in JSON data submitted to /api/v1/statuses endpoint.
Sending the following JSON results in no attachments added to the post:
{
    "status": "capybara #capybara https://redd.it/10rwhmv",
    "visibility": "unlisted",
    "sensitive": true,
    "media_ids[]": [
        "19456"
    ]
}

This is contrary to the Mastodon API definition
As a workaround i am also adding the same media ids with a JSON key of media_ids as below which seems to work.
{
    "status": "capybara #capybara https://redd.it/10rwhmv",
    "visibility": "unlisted",
    "sensitive": true,
    "media_ids[]": [
        "19456"
    ],
    "media_ids": [
        "19456"
    ]
}

Interesting - most clients we've tested this with use formdata rather than JSON bodies for this, so we missed that.
Are you sure the Mastodon key is media_ids[] in JSON body mode? https://docs.joinmastodon.org/client/intro/#array would indicate otherwise, which is why I coded it like this.

I've been using media_ids[] key with Mastdon (botsin.space) and Pleroma (cawfee.club) server instances for quite some time successfully. While you're interpretation of the Mastodon doc might be correct, from my experience it certainly is different to how the servers react.
I'll do some more testing on my end...

It certainly would not be the first time the Mastodon API docs don't match the implementation! I suspect it might accept both arrangements.
Either way, if they support it, so should we. I'll need to redo our API parser layer a bit first - the way Mastodon mangles together JSON, formdata, and query params is taking a bit of effort to convince Django to do.

So I changed my code back to using formdata as below:
        form_data = aiohttp.FormData()
        form_data.add_field(name="status", value=status)
        form_data.add_field(name="visibility", value=visibility)
        form_data.add_field(name="sensitive", value=sensitive)
        if media_ids:
            form_data.add_field(name="media_ids[]", value=media_ids)
        if spoiler_text:
            form_data.add_field(name="spoiler_text", value=spoiler_text)

        async with self.session.post(
            url=url,
            headers=headers,
            data=form_data,
        ) as response:

and again I get the media not attached to the post (https://takahe.social/@capybara/posts/144139249467906208/)
Looking at my debug output, I can see the media has been uploaded successfully to Takahe. /api/v1/media responded with:
{
    "id": "19584",
    "type": "image",
    "url": "https://storage.googleapis.com/takahe-social/attachments/2023/2/3/6LuvUQxQFTkS7ijzMrbTgWYaqA0.webp",
    [...]
}

PS: trying to add the media_ids field without [] to the formdata errors out, so I am assuming formdata.addField parses the name to decided if the field is an array or not.

I just looked at the code and it appears I misspoke earlier - we seem to only accept media in the JSON body form without the square brackets. I think I was thinking of media uploads themselves always being multipart data instead.
Thus, the workaround in your first message would be best for now; I'll get our stuff fixed up so that this works across all versions.

This should now be fixed with the new API framework we have - it's both checked into main and up on takahe.social. If you could verify it would be appreciated!

Awesome... just did a quick test without my workaround.
I am happy to confirm that I no longer need the workaround and using "media_ids[]" works same as on Mastodon and Pleroma instances I interact with.
Thank you


Random MOVED errors.

I use MaxRedirects: 1 in cluster client and redis 4.0.2, and sometimes see MOVED errors, but cluster nodes output not changes, cluster not resharded.

Are you able to isolate the problem and write a program that reproduces the problem?

I will try to isolate, but it's very difficult, with total load of 300000 rps I see about 3-10 errors per second.

I think that I get this error because with MaxRedirects: 1 if first request is RetryableError than client select random node and that node returns MOVED error to first failed node. In this case MOVED error message looks unclear. You can close issue if you think that this behavior is right.

We're seeing this too. Here's a simple program to reproduce it (it simply GETs random keys concurrently):
package main

import "github.com/go-redis/redis"
import "math/rand"
import "fmt"

func main() {
        client := redis.NewClusterClient(&redis.ClusterOptions{
                Addrs:    []string{":7000"},
                PoolSize: 16,
        })

        const concurrency = 10

        for i := 0; i < concurrency; i++ {
                go func() {
                        for {
                                rnd := ""
                                for i := 0; i < 10; i++ {
                                        rnd += string(rune(int(rune('a')) + rand.Intn(int(rune('z') - rune('a')))))
                                }
                                fmt.Printf("GET %s\n", rnd)
                                err := client.Get(rnd).Err()
                                if err != nil && err != redis.Nil {
                                        panic(err)
                                }
                        }
                }()
        }

        select{} // sleep
}

If I set const concurrency = 1 the error doesn't happen, so it seems to be a bug with multiple goroutines using the same ClusterClient.

My test program still fails after commit 092971361bcfb3fd8c0cb21d55f959ddd5cecbca

I did not try to run your program, because there is nothing special in it and I can't believe that it is broken because of concurrency (who does not use Redis concurrently?). Also it is obvious that you have a different problem so it is better to open new issue.
Are you able to reproduce the problem using test suite? E.g. there are concurrent tests in https://github.com/go-redis/redis/blob/master/race_test.go#L288-L343 and lots of cluster tests https://github.com/go-redis/redis/blob/master/cluster_test.go


UEDA logo

@khanyisa12 Please check with Bongiwe if we can get a high quality version of the logo, I've made the changes, but it looks abit  off, have you seen it yet?

okay. Cc Bongiwe says that she doesn't have another logo with best quality

okay. Cc Bongiwe says that she doesn't have another logo with best quality

Okay not a problem, I will work on formatting the image to the correct one tomorrow


hex::FromHex for Vec<Vec>?

Is there any way of serializing a Vec<Vec<u8>> into a Vec<T> where each T is a hex encoded string?
Sorry if it has been asked before but I couldn't find any related issue.

If you mean converting a Vec<String> to a Vec<Vec<u8>> i believe doing something like hex_strings.into_iter().map(|s| hex::decode(s)).collect::<Result<Vec<_>>() would do the trick

Sorry, the question was not properly formatted, my bad.
I actually mean doing it the other way around. I have a collection of Vec<u8> that needs to be serialized to a collection of hex encoded Strings, so that's be Vec<Vec<u8>> -> Vec<String>

Well the answer would be kinda the same, but also the other way around :p
bytes_collection.into_iter().map(hex::encode).collect::<Vec<_>>()

I just realised I should have been way more precise with my question.
What I'm aiming for is being able to use it with serde so I can derive the serialization of such a field in a struct.
The issue I'm facing is that the trait is not implement for Vec<Vec<u8>> (hence my question regarding if it was possible) nor can it be implemented externally to hex.
Is the only option to define such a function in my crate and then use #[serde(serialize_with = "path")] in the struct to link it?

Is the only option to define such a function in my crate and then use #[serde(serialize_with = "path")] in the struct to link it?

I was able to make it work following this approach, not sure it there is a cleaner way to do it.
pub fn serialize_vec_vec_u8(v: &Vec<Vec>, s: S) -> Result<S::Ok, S::Error>
where
S: Serializer,
{
let mut seq = s.serialize_seq(Some(v.len()))?;
for element in v.iter() {
seq.serialize_element(&hex::encode(element))?;
}
seq.end()
}


useFormikContext is throwing undefined when used along withFormik

🐛 Bug report
Current Behavior
 const { values, submitForm } = useFormikContext();
Throws the following error
TypeError: Cannot destructure property 'values' of 'Object(...)(...)' as it is undefined.

Expected behavior
To get the values from Formik form
Your environment

Software
Version(s)

Formik
2.1.5

React
0.0.0-experimental-94c0244ba

Browser
Firefox

npm/Yarn
6.14.5

Operating System
MacOS

For what it's worth, the behavior that the absence of a Formik context should return undefined caught me by surprise as well. Given that I will commonly destructure attributes from hooks that return an object, I would have expected that the hook would have returned an empty object rather than undefined.
Additionally, if I'm reading the types properly I believe the TS types do not reflect this possibility, so even running TS with --strictNullChecks may not flag this as a potential case to handle.
Have you all considered returning an empty object instead of undefined?

You should receive an error message when using useFormikContext without a context in the hierarchy. I don't see a reason to add an empty object here when your app has entered an exceptional state. Further, an empty object would be a lie. There is no context, so returning an empty object would lead to a false sense of security.
You can instead write something like const { handleChange } = useFormikContext() ?? {};
The main problem with updating the types to reflect that undefined is a possibility is that code that works properly will now need to do conditional checks for everything in TypeScript. See:
const MyForm = () => {
  <Formik><MyFields /></Formik>
}

const MyFields = () => {
-  const { handleChange, submitForm, touched, errors, values } = useFormikContext(); // ERROR formik is possibly undefined
+ const { handleChange, submitForm, touched, errors, values } = useFormikContext() ?? {};

  return <>
    { /* OK */ }
    <form onSubmit={submitForm}>
      My Field
      <input
        id="myField"
        name="myField"
        { /* OK, I guess */ }
        value={values?.myField}
        { /* this is bad */ }
        onChange={handleChange ? handleChange('myField') : undefined}
      />
      { /* that's a lot of question marks */ }
      {touched?.myField && errors?.myField &&
{errors?.myField}
}
    </form>
  </>
}

Interestingly, the only fix for this would be to remove your ability to destructure right away:
const MyFields = () => {
  const formik = useFormikContext();

  if (!formik) {
    throw "Error loading form";
  }

  const { handleChange, submitForm, touched, errors, values } = formik;

  return <OK />
}

I think that's actually a pretty nice API, or at the very least a more in tune with the way React Context itself works. But every bit of code that's ever been written in TypeScript using Formik would be broken if we made this change.

I assume the reason why useFormikContext() does not throw is so that users can identify if they are within a Formik tree. If this is not considered a common use-case, then I would recommend an approach similar to React Router, where useFormikContext() would throw if no context is found. This would also "fix" the TypeScript typings such that undefined could never be returned:
export function useFormikContext<T>(): Context<T> | never;

It isn't a common pattern because nothingness is meaningful. There are two different nothings in JavaScript, that is how meaningful nothingness is. Many backend libraries lean towards useful defaults and throwables for very good reasons. In the backend, if a variable you expect doesn't exist, you are likely to throw. Nothingness is instead an instantiated value that is assigned to null.
Throwing is nice when you have a backend because you catch it in your logging and exceptional code is part of the ongoing iteration. Exceptions also help protect critical code from being reached with exceptional states.
On the client side, both of these patterns are a little less intuitive. Firstly, you don't want to interrupt your user. One missed catch on the front-end might completely bork your frontend and make your site unusable. Many people do not have comprehensive client-side analytics set up, so they might not notice until a customer complained about their website not working. If Formik is the reason code is throwing all over the internet, we'll never hear the end of it.
Second, in many languages the concept of nothingness is almost an afterthought. Null is a positive value meaning nothing, whereas undefined is the absence of anything. JavaScript is a nothingness-forward language because of its use in the browser, where variables you are looking for just may completely not exist, like the return value of useFormikContext without a context over it. In this case, undefined is the perfect value representing the state of Formik's context.
Meaningful defaults can also be useful, and I agree with them, but they have to be meaningful and not a lie. A fake formik context isn't meaningful to me, and it would make it more complicated to detect whether or not there is a context above. To me, it would be a lie.
Interestingly, the exact opposite issue exists on this repository, as well. Hopefully it shows that we walk a pretty balanced line with a lot of different perspectives (and yours is appreciated!) #2338
TL:dr; user wants check if useFormikContext returns undefined, and if so, do something else.

@varunrayen hopefully my explanation above helped solidify why we'll continue to return undefined.
As explained above you can do this to fix your original issue. If using typescript you'll probably have to do some extra finessing.
const { values, submitForm } = useFormikContext() ?? {};

Just for whomever might be reading this: I had a component with a different version of formik than the main project in a monorepo and that was giving me this error. I aligned the versions and that fixed it.


Panic for proptest::sample::subsequence(vec![], 0..0)

The most reduced test-case for my example, is the empty vector.
Given the empty vector (and asked for zero samples), proptest panics with

... panicked 'attempt to subtract with overflow', .cargo/registry/src/github.com-1ecc6299db9ec823/proptest-0.8.5/src/collection.rs:111:61

Minimal example:
proptest! {
    #[test]
    fn reproduction(input in (1..33usize).prop_flat_map(|size| (Just(size), prop::sample::subsequence((1..size).collect::<Vec<usize>>(), 0..size-1).boxed()))) {
        panic!("Nope {:?}", input);
    }
}

Output:
---- reproduction stdout ----
thread 'reproduction' panicked at 'Nope (13, [3, 4, 5, 10, 11])', src/test.rs:670:13
note: Run with `RUST_BACKTRACE=1` for a backtrace.
thread 'reproduction' panicked at 'Nope (13, [4, 5, 10, 11])', src/test.rs:670:13
thread 'reproduction' panicked at 'Nope (13, [5, 10, 11])', src/test.rs:670:13
thread 'reproduction' panicked at 'Nope (13, [10, 11])', src/test.rs:670:13
thread 'reproduction' panicked at 'Nope (13, [11])', src/test.rs:670:13
thread 'reproduction' panicked at 'Nope (13, [])', src/test.rs:670:13
thread 'reproduction' panicked at 'Nope (7, [1, 2, 4, 5, 6])', src/test.rs:670:13
thread 'reproduction' panicked at 'Nope (7, [2, 4, 5, 6])', src/test.rs:670:13
thread 'reproduction' panicked at 'Nope (7, [4, 5, 6])', src/test.rs:670:13
thread 'reproduction' panicked at 'Nope (7, [5, 6])', src/test.rs:670:13
thread 'reproduction' panicked at 'Nope (7, [6])', src/test.rs:670:13
thread 'reproduction' panicked at 'Nope (7, [])', src/test.rs:670:13
thread 'reproduction' panicked at 'Nope (4, [1, 3])', src/test.rs:670:13
thread 'reproduction' panicked at 'Nope (4, [3])', src/test.rs:670:13
thread 'reproduction' panicked at 'Nope (4, [])', src/test.rs:670:13
thread 'reproduction' panicked at 'Nope (2, [])', src/test.rs:670:13
thread 'reproduction' panicked at 'attempt to subtract with overflow', .cargo/registry/src/github.com-1ecc6299db9ec823/proptest-0.8.5/src/collection.rs:111:61

Some discussion on this in: https://github.com/AltSysrq/proptest/issues/85#issuecomment-415779809.

sample(input, 0..0) can't do anything but panic because the size range is empty, i.e., there are no sizes at all that it would be allowed to generate

@AltSysrq But of course! My bad, sorry.

So, after some experiments; How WOULD I go about generating a [potentially 0-length] set of samples from a [potentially 0-length] collection?
sample(vec![], 0..1) does not seem legal either? (Despite the only valid value for output-size is now exactly 0 elements)
Right now I completely side-step subsequence for the special-case of input being empty, but that does not seem right.
In particular, I ponder the error:

Illegal SampledBitSetStrategy: have 12 bits available, but requested size is 0..13

So, the maximum possible requested size is exactly 12. Is this really an error?

There might be something going on there. I'm looking at other stuff involving size ranges in a bit anyway, maybe they have the same root cause.

There were a couple off-by-one errors. They have been fixed in 0.8.6. 0.8.6 also has an explicit check for things like 0..0 so the problem is more obvious.


NMS does not work properly, the IoU calculation is wrong.

When calculating the area of the rectangle, the code uses the (x2-x1+1)*(y2-y1+1) formula (here and here).
This would be fine if the coordinates were integers and we would calculate in pixel space (it would mean that we consider the [x1, x2]x[y1,y2] closed 2d interval as the rectangle as opposed to the [x1, x2)x[y1,y2) half open intervals). I suppose this was the case in the original Fast R-CNN project.
But here we call this function with [0,1] normalized coordinates, which makes the IoU calculation wrong.
Practically it drops even the not overlapping detections. So the face detector only works properly when only one face is present on the image.

When py_cpu_nms is called, the coordinates are converted back to pixel space, not normalised to [0, 1]. Hence +1 doesn't make the results wrong.


Initialised app shows error when opening in the iOS emulator

The app which I created using XDE runs into the error in the screenshot when running in iOS emulator.
Also, I am unable to open the project on Android device, it gets stuck in the Fetching JS Bundle window and nothing else shows up.
xde version: 2.17
Expo app: 1.15.1

hi there! this can happen if the simulator is in a bad state, unfortunately it has nothing to do with expo -- you'll need to run "Reset Content and Settings" in the simulator.

Thanks @brentvatne !

My guess it that this was an intermittent error with our tunnel provider. Does this happen consistently after pressing "Restart"?

@jesseruder It does many times I start the emulator. Comment from @brentvatne helped, but this error still does come up few times in between.


Django Compatibility Errors

So I just ran the command: pip install -r requirements.txt in the virual env and I ran into the following errors:
django-twilio 0.9.0 has requirement twilio<7,>=6.3.0, but you'll have twilio 4.4.0 which is incompatible. oauth2client 1.4.11 has requirement rsa==3.1.4, but you'll have rsa 3.4.2 which is incompatible. django-scheduler 0.7.5 has requirement argparse==1.1, but you'll have argparse 1.4.0 which is incompatible. django-phonenumber-field 2.0.0 has requirement Django>=1.11, but you'll have django 1.8.11 which is incompatible.

Hi, please note this project is not active: https://github.com/ustream/openduty/issues/92#issuecomment-374231734

I was able to get everything to work. https://github.com/SDasman/openduty
Changed the whole requirements.txt file.


Remove basic language support for yaml

This is already supported by Monaco editor by default.

I’m going to delay this until monaco-editor 0.34.0 is released, because that release will include the onEnterRules that were included in the monaco-yaml basic language support.

I’m delaying this further. CI is broken for monaco-editor 0.34.0 upstream and I don’t trust that release for now.

I’m going to keep this. monaco-editor might already define this, but not monaco-editor-core.


CI. Github Actions

A new github actions for aur.

After a year and a half, I find myself happy with manual aur release, supported by a 40-line-long python script. Thank you for the effort though : )


[Snyk] Fix for 1 vulnerabilities

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `npm` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

services/video-conferencing-service/package.json
services/video-conferencing-service/package-lock.json

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

748/1000  Why? Proof of Concept exploit, Recently disclosed, Has a fix available, CVSS 7.1
Cross-site Request Forgery (CSRF) SNYK-JS-AXIOS-6032459
Yes
Proof of Concept

(*) Note that the real score may have changed since the PR was raised.

Commit messages

Package name: twilio
    The new version differs by 3 commits.

ce1c027 Release 4.6.0
b5204c0 Adding Beta and Preview products to main artifact
1168168 [Librarian] Regenerated @ 61e059e9694883693c4919778c1e37947fdb3168

See the full diff

Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Cross-site Request Forgery (CSRF)

Done Already


Change docstrings to match discord's new channel namings

https://github.com/discord/discord-api-docs/commit/3812cb5d97f524308e50d59c109586d6af94003b

HTTP wrappers was removed in #201 so this is not needed


mold linker

how can we use mold linker with cargo-chef? This is my current Dockerfile:
FROM lukemathwalker/cargo-chef:latest-rust-bullseye AS chef
WORKDIR /sushibot

FROM chef AS planner
COPY . .
RUN cargo chef prepare --recipe-path recipe.json

FROM chef AS builder
COPY --from=planner /sushibot/recipe.json recipe.json
RUN cargo chef cook --release --recipe-path recipe.json
COPY . .
RUN cargo build --release --bin sushibot

FROM debian:bullseye-slim AS runtime
WORKDIR /sushibot
COPY --from=builder /sushibot/target/release/sushibot /usr/local/bin
ENTRYPOINT ["/usr/local/bin/sushibot"]

I don't think there is anything specific to be done apart from setting mold to be your linker in the .cargo/config.toml file and copying that over before calling build!


[master] Extend center-on-float to work with windows floating because of a rule and float-non-resizable

center-on-float currently does not apply to windows floating because of a rule (e.g. kwmc rule owner="Mail" name="" properties={float="true"}) or because of float-non-resizable.

Uh, I have not confirmed this, but sounds like a bug if this doesn't work.

For what it's worth, the float-dim setting doesn't work with them either.

For what it's worth, the float-dim setting doesn't work with them either.

Note: The float-dim setting will only apply to resizable windows.
Non-resizable windows will be given (x, y) -> (width / 4, height / 4)

Makes sense, not sure what I was thinking there back in October.
Thanks for the fix! 👍

So due to #555 I suppose windows affected by float-non-resizable should not conform to this.


Add a return_response_from equivalent for non-idempotent upstreams.

In similar lines to the return_response_from directive of degressly-core, there should be an option where the request from the candidate downstream is allowed to flow to the upstream API instead of that of the primary.

Wrong repository


macaroon_deserialize_json is not declared in macaroons.h

There is a macaroon_serialize_json function, but no macaroon_deserialize_json function.

Oops, my mistake. It just not mentioned in the macaroons.h file.

The JSON format is not yet stabilized, so we didn't (fully) expose the functions to work with it.


Add base_name for compose-images and build-images

This way they can be referenced easily

This is not necessary. The base name only needs to be manually specified if the viewset does not use a model. In this case, there alredy is a basename of composeimage, which can be referenced by composeimage-list and composeimage-detail. Please note that unit tests already use these names.

Meh, I realized this is not needed. There was a typo in my template


Error on sorting properties

@ptrushin

error node_modules/antd-table-ext/dist/useHistory.js (3:0) @ eval
error ReferenceError: window is not defined

TypeError: Cannot read properties of undefined (reading 'defaultSortOrder')

Thanks. Please specify which device you are using the library on?


Nuclio Connection error in Kubernetes

i deploy cvat in kubernetes(using helm ) and checked create task successfully.
but i  cant connect Nuclio (Nuclio also deployed in kubernetes) . So i edit cvat backend deployment ( add ENV NUCLIO_HOST, NUCLIO PORT). i checked env is set in pod
but connection error is same. how to connect Nuclio?
i
My deployment is that.

i can't found model menu in cvat

Hi, you should also pass additional env variable, because this functionality disabled by default https://github.com/openvinotoolkit/cvat/blob/develop/components/serverless/docker-compose.serverless.yml#L23
Also, most likely function invocation will not work in the current version, so you need to modify request headers here https://github.com/openvinotoolkit/cvat/blob/develop/cvat/apps/lambda_manager/views.py#L47-L49
like this:
        extra_headers = {
            'x-nuclio-project-name': 'cvat',
            'x-nuclio-function-namespace': {your nuclio namespace},
            'x-nuclio-invoke-via': 'domain-name',
        }

We are currently working to extend current helm chart to add availability run CVAT with nuclio.


ENH:

Use Case
Specifying virtual tags that are more flexible functions of constituent tags (allowing for addition of and multiplication by a constant)
Solution
A flexible way of specifying affine and polynomial expressions would be ideal
Alternatives
Creating additional tags with constants for multiplication/addition is possible but cumbersome

Closed by #74


Docs WG Meeting #4 - 2016-##-## @ 10:00AM PST

This issue (for now) serves as kick-off for a new meeting scheduled by @chrisdickinson. I wanted to open it to collect issues tagged with label wg-agenda or otherwise noted below.
Docs WG Meeting #4 2016-##-
Present
In-meeting
In-chat
Agenda

Docs WG Sign-up Round #2 #63 and related...
notes: handle increasing amounts of notes (that are very specific) #98
State of the doctool https://github.com/nodejs/node/pull/5408

With Priority

error docs / guide #82
proposal: use hard wrapping for code and soft wrapping for prose #53

It would be nice if we could discuss https://github.com/nodejs/node/pull/6136#issuecomment-207968546 (collapsing notes except their first line by default).

+1 on this meeting 🎱

It'd be good to figure out where the doc tool stuff is at. I did a bit of work on that and then got too busy to continue, @kahwee also did some work in https://github.com/nodejs/node/pull/5408, but it appears to have stalled.

I feel bad about that, got too busy at work. I've got some time off this week from work and will try correcting that.

ping @chrisdickinson

Ping @chrisdickinson

ping @chrisdickinson

When is the next working group meeting? Is this that?

I think it's save to say that this working group has stalled. Unless anyone revives it, there likely won't be a meeting. cc @jasnell what is the general process with stalled WGs?


[ISSUE #251]Support avg function in WindowStream

Hi teams, I have completed the main part of avg calculation. Could you please review the code?

Besides, I'm a little confused. For the average calculation in the Accumulator, is the merge only allowed for the same type accumulator?
I wrote an example to test. Here is the test result.

time:23:00:58.644, input:6
time:23:00:59.883, input:7
time:23:01:01.492, input:8
[2023-01-27 23:00:55 - 2023-01-27 23:01:00](key=key, value=6.0)
time:23:01:13.550, input:9
[2023-01-27 23:01:00 - 2023-01-27 23:01:05](key=key, value=8.0) ```

Good catch, Thanks very much your pr.

merge is a reserved method,  It use to merge two AvgAccumulator during calculation process；
the result of example seems not very accurate，pr 263 maybe solve this problem, please check this example again after that pr merged；
It is best to stop the RocketMQStream when program exit，like other examples.

@Jargon9 你好，能否看看这个pr，最近可能发版本，能带上最好。

好的！感谢帮忙cr代码。不好意思我前几天有点忙，周末会继续完成它的。

Hi teams, I found that the log truncation of the previous results is incomplete. I retested the function. It should be OK.
Besides, thank you for your help, I add a WindowAvg-shutdown-hood  when program exit , like other examples.
time:21:54:12.507, input:1
time:21:54:17.498, input:2
[2023-02-05 21:54:00 - 2023-02-05 21:54:15](key=key, value=1.0)
time:21:54:22.507, input:3
time:21:54:27.516, input:4
time:21:54:32.531, input:5
[2023-02-05 21:54:15 - 2023-02-05 21:54:30](key=key, value=3.0)
time:21:54:37.538, input:6
time:21:54:42.545, input:7
time:21:54:47.560, input:8
[2023-02-05 21:54:30 - 2023-02-05 21:54:45](key=key, value=6.0)
time:21:54:52.571, input:9
time:21:55:44.630, input:1
[2023-02-05 21:54:45 - 2023-02-05 21:55:00](key=key, value=8.5)
time:21:55:48.642, input:2
[2023-02-05 21:55:30 - 2023-02-05 21:55:45](key=key, value=1.0)
time:21:55:52.651, input:3
time:21:55:56.657, input:4
time:21:56:00.669, input:5
[2023-02-05 21:55:45 - 2023-02-05 21:56:00](key=key, value=3.0)
time:21:56:04.677, input:6
time:21:56:08.681, input:7
time:21:56:12.691, input:8
time:21:56:16.701, input:9
[2023-02-05 21:56:00 - 2023-02-05 21:56:15](key=key, value=6.5)

Codecov Report

Merging #259 (e6eec5d) into develop (608ccae) will not change coverage.
The diff coverage is 0.00%.

@@           Coverage Diff           @@
##           develop    #259   +/-   ##
=======================================
  Coverage     0.00%   0.00%
=======================================
  Files           85      87    +2
  Lines         3027    3084   +57
  Branches       296     301    +5
=======================================
- Misses        3027    3084   +57

Impacted Files
Coverage Δ

...eams/core/function/accumulator/AvgAccumulator.java
0.00% <0.00%> (ø)

...ocketmq/streams/core/rstream/WindowStreamImpl.java
0.00% <0.00%> (ø)

.../rocketmq/streams/core/util/OperatorNameMaker.java
0.00% <ø> (ø)

...he/rocketmq/streams/examples/window/WindowAvg.java
0.00% <0.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Adding improvements to the README file

Multiple changes to the README file:

Adding instructions for Arch/Manjaro
Adding table of contents
Re-ordered sections
Re-worded a few instructions

@rdbreak I don't how often you dealing with pull requests, but if you are going to merge this soon, I have a few additional changes to make. Should be adding them in the next few days.

I'm ended up making a long list of fixes and improvements. I will merge everything together.


Enhance Rocket.Chat Notifications for Deployment Status

Description
Enhance notifications in the #app-dev-team channel on Rocket.Chat to include updates on deployment status for the following events:

Successful deployment on Prod
Successful deployment on Test
Failed deployment on Prod
Failed deployment on Test
Failed deployment on Dev

Technical Details

Use the existing notification setup for successful deployments on Prod as a reference.

Definition of Done (DOD)

Rocket.Chat is updated with notifications including necessary information, such as GitHub links, for the specified deployment events.

After adding the webhooks to repository the notifications work as expected:

Avatar image fixed later:


Refactor/arco

Skeleton: remove union type
PasswordInput: add default value
Input/passwordInput: fix a bug where inserting a slot causes it to be unselected(Cannot get the latest dom element by ref.current)
others: Add missing titles, improve descriptions, re-categorise and use appropriate widgets for display

 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.xzdry 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.


Update vagrant push to upload sparkjob to Bintray

Not sure on it. Need to test somehow.

No worries - I'll test when it's time to release!


feat: Support loading parameter values from configmaps

Fixes https://github.com/argoproj/argo-workflows/issues/3212. This builds on top of the informer added in https://github.com/argoproj/argo-workflows/pull/6644.
Tips:

Maybe add you organization to USERS.md.
Your PR needs to pass the required checks before it can be approved. If the check is not required (e.g. E2E tests) it does not need to pass
Sign-off your commits to pass the DCO check: git commit --signoff.
Run make pre-commit -B to fix codegen or lint problems.
Say how how you tested your changes. If you changed the UI, attach screenshots.
If changes were requested, and you've made them, then dismis the review to get it looked at again.
You can ask for help!

This is a great improvement!
Question - what happens when values of configmaps change while the workflow is running? Will the behavior be unpredictable or do we remember the configmap values at the point of use?

This is a great improvement!
Question - what happens when values of configmaps change while the workflow is running? Will the behavior be unpredictable or do we remember the configmap values at the point of use?

Great question. Let me try to answer that to my best knowledge in theory but we can double check by running some experiments if needed.
For local/template level variables, here are the two cases:

For workflow pods, these values are retrieved during the creation time of workflow pods so once the pods are created, the values won't change.
For controller pod, the values are retrieved everytime when the controller executes the template and returns the updated node status so the parameter values will change when they change in configmaps.

For global variables, the values from configmaps are retrieved every time when the controller processes/operates a workflow so the parameter values will change when they change in configmaps.

https://github.com/argoproj/argo-workflows/pull/6691

🚀 great stuff - a big feature which will make users very happy!

Looking forward to this feature! Do you all know when this will be released?

It's already part of v3.2.0rc3 so you should be able to try it out now.

Hi @terrytangyuan! I tried this example https://github.com/argoproj/argo-workflows/blob/master/examples/arguments-parameters-from-configmap.yaml
but I receive the following error while running the flow:
unable to retrieve inputs.parameters.message from ConfigMap: ConfigMap 'simple-parameters-configmap' does not exist
and yes, the configmap exists :)
k get configmap simple-parameters-configmap -o
apiVersion: v1
data:
  msg: hello world
kind: ConfigMap
metadata:
  creationTimestamp: "2021-09-27T15:42:48Z"
  name: simple-parameters-configmap
  namespace: my-namespace
  resourceVersion: "252410349"
  selfLink: /api/v1/namespaces/my-namespace/configmaps/simple-parameters-configmap
  uid: 65d4258f-38fb-498c-81dd-18b1862b5fa6

Any idea?
Thank you!

@softwarebloat Thanks for trying it out! Do you mind filing a bug report instead with other useful information such as logs? I'll help look into it from there.


InternalServerError: Can't find materialized set when using assert_single

EdgeDB Version: 3.0-dev.7347+d56cc2a
EdgeDB CLI Version: n/a
OS Version: n/a

Steps to Reproduce:
Removing either assert_single below fixes the bug.
SELECT std::assert_single((
SELECT DETACHED default::A {
  b := (
    WITH
      __scope_1_defaultB := .b
    SELECT __scope_1_defaultB {
      c := (
        std::assert_single((
        SELECT __scope_1_defaultB.c {
          single b_id := __scope_1_defaultB.id
        }
        ))
      ),
    }
  )
}
))

InternalServerError: Can't find materialized set (__derived__::expr~15).>b_id[IS std::uuid]

Schema:
module default {
  type A {
    multi link b := .<a[is B];
  }
  type B {
    multi link a -> A;
    multi link c := .<b[is C];
  }
  type C {
    required link b -> B;
  }
}

This query, while infrequently run, used to work for us, so this is a regression as of one of the recent versions.

Any leads on this?