Can't blacklist a certain term that uses "S&S" as a label

Having trouble doing a specific blacklisting "s&s" from a force subtitle condition.  Not sure how to properly escape this, I would assume that within the double quotations it would read everything as is.
Currently this is how I setup the blacklist in the json:
{
"alang": ["jpn", "ja"],
"slang": "eng?",
"blacklist": [ "sign", "s&s" ],
"condition": "sub.forced"
}

What is the error message?

These are what the logs show related to the sub_select portion.  This after opening the video then closing after the fact.
Line 150: [   0.006][d][sub_select] Loading lua script D:/mpv/portable_config/scripts/sub-select.lua...
Line  155: [   0.007][d][sub_select] loading mp.defaults
Line  168: [   0.007][d][sub_select] loading file D:/mpv/portable_config/scripts/sub-select.lua
Line  178: [   0.007][d][sub_select] reading options for sub_select
Line  180: [   0.008][v][sub_select] Opened config file script-opts/sub_select.conf.
Line  377: [   0.016][v][sub_select] predicted audio track is 2
Line  378: [   0.016][d][sub_select] select subtitle for {"title" = "", "type" = "audio", "src-id" = 3, "image" = false, "id" = 2, "ff-index" = 2, "visual-impaired" = false, "hearing-impaired" = false, "external" = false, "selected" = false, "lang" = "jpn", "audio-channels" = 2, "demux-channel-count" = 2, "demux-channels" = "unknown2", "demux-samplerate" = 48000, "codec" = "opus", "albumart" = false, "dependent" = false, "forced" = false, "default" = false}
Line  379: [   0.016][d][sub_select] Checking for valid audio: jpn
Line  380: [   0.016][v][sub_select] valid audio preference found: {"jpn", "ja"}
Line  381: [   0.016][d][sub_select] checking for valid sub: eng?
Line  382: [   0.016][d][sub_select] evaluating string return sub.forced
Line  383: [   0.016][d][sub_select] Checking for valid audio: jpn
Line  384: [   0.016][v][sub_select] valid audio preference found: {"jpn", "ja"}
Line  385: [   0.016][d][sub_select] checking for valid sub: jpn
Line  386: [   0.016][d][sub_select] checking for valid sub: ja
Line  387: [   0.016][d][sub_select] Checking for valid audio: jpn
Line  388: [   0.016][v][sub_select] valid audio preference found: {"jpn", "ja"}
Line  389: [   0.016][d][sub_select] checking for valid sub: eng?
Line  390: [   0.016][v][sub_select] setting sid to 1
Line 3239: [   0.802][i][sub_select] detected audio change - reselecting subtitles
Line 3245: [   0.802][d][sub_select] select subtitle for {"title" = "", "type" = "audio", "src-id" = 3, "image" = false, "id" = 2, "ff-index" = 2, "visual-impaired" = false, "hearing-impaired" = false, "external" = false, "selected" = false, "lang" = "jpn", "audio-channels" = 2, "demux-channel-count" = 2, "demux-channels" = "unknown2", "demux-samplerate" = 48000, "codec" = "opus", "albumart" = false, "dependent" = false, "forced" = false, "default" = false}
Line 3247: [   0.802][d][sub_select] Checking for valid audio: jpn
Line 3248: [   0.802][v][sub_select] valid audio preference found: {"jpn", "ja"}
Line 3249: [   0.802][d][sub_select] checking for valid sub: eng?
Line 3250: [   0.802][d][sub_select] evaluating string return sub.forced
Line 3251: [   0.802][d][sub_select] Checking for valid audio: jpn
Line 3252: [   0.802][v][sub_select] valid audio preference found: {"jpn", "ja"}
Line 3253: [   0.802][d][sub_select] checking for valid sub: jpn
Line 3254: [   0.802][d][sub_select] checking for valid sub: ja
Line 3255: [   0.802][d][sub_select] Checking for valid audio: jpn
Line 3256: [   0.802][v][sub_select] valid audio preference found: {"jpn", "ja"}
Line 3257: [   0.802][d][sub_select] checking for valid sub: eng?
Line 3258: [   0.802][v][sub_select] setting sid to 1
Line 6653: [   7.026][d][sub_select] Exiting...

Are you sure you're using the latest version of sub-select? It looks like you may not be. Also please upload the logs again, but this time use ---msg-level=sub_select='trace'.

Well I am using the one available on this page.  When running mpv and executing the command from the console it says ---msg-level=sub_select='trace' is not found
But checking the logs I did find more details being shown:
Line   153: [   0.007][d][sub_select] Loading lua script D:/mpv/portable_config/scripts/sub-select.lua...
Line   155: [   0.007][d][sub_select] loading mp.defaults
Line   166: [   0.008][d][sub_select] loading file D:/mpv/portable_config/scripts/sub-select.lua
Line   178: [   0.008][d][sub_select] reading options for sub_select
Line   184: [   0.008][v][sub_select] Opened config file script-opts/sub_select.conf.
Line   377: [   0.016][v][sub_select] predicted audio track is 2
Line   378: [   0.016][d][sub_select] select subtitle for {"forced" = false, "src-id" = 3, "default" = false, "image" = false, "albumart" = false, "dependent" = false, "type" = "audio", "hearing-impaired" = false, "external" = false, "selected" = false, "audio-channels" = 2, "demux-channel-count" = 2, "demux-channels" = "unknown2", "demux-samplerate" = 48000, "codec" = "opus", "lang" = "jpn", "visual-impaired" = false, "title" = "", "id" = 2, "ff-index" = 2}
Line   379: [   0.016][d][sub_select] checking pref: {"alang" = {"jpn", "ja"}, "condition" = "sub.forced", "blacklist" = {"sign", "s&s"}, "slang" = "eng?"}
Line   380: [   0.017][d][sub_select] checking pref: {"alang" = {"jpn", "ja"}, "blacklist" = {"sign"}, "slang" = {"jpn", "ja"}}
Line   381: [   0.017][d][sub_select] checking pref: {"alang" = {"jpn", "ja"}, "blacklist" = {"force", "sign", "song"}, "slang" = "eng?"}
Line   382: [   0.017][v][sub_select] valid audio preference found: {"jpn", "ja"}
Line   383: [   0.017][v][sub_select] valid subtitle preference found: "eng?"
Line   384: [   0.017][v][sub_select] setting sid to 1
Line  3233: [   0.808][i][sub_select] detected audio change - reselecting subtitles
Line  3240: [   0.808][d][sub_select] select subtitle for {"forced" = false, "src-id" = 3, "default" = false, "image" = false, "albumart" = false, "dependent" = false, "type" = "audio", "hearing-impaired" = false, "external" = false, "selected" = false, "audio-channels" = 2, "demux-channel-count" = 2, "demux-channels" = "unknown2", "demux-samplerate" = 48000, "codec" = "opus", "lang" = "jpn", "visual-impaired" = false, "title" = "", "id" = 2, "ff-index" = 2}
Line  3241: [   0.808][d][sub_select] checking pref: {"alang" = {"jpn", "ja"}, "condition" = "sub.forced", "blacklist" = {"sign", "s&s"}, "slang" = "eng?"}
Line  3242: [   0.808][d][sub_select] checking pref: {"alang" = {"jpn", "ja"}, "blacklist" = {"sign"}, "slang" = {"jpn", "ja"}}
Line  3243: [   0.808][d][sub_select] checking pref: {"alang" = {"jpn", "ja"}, "blacklist" = {"force", "sign", "song"}, "slang" = "eng?"}
Line  3244: [   0.808][v][sub_select] valid audio preference found: {"jpn", "ja"}
Line  3245: [   0.808][v][sub_select] valid subtitle preference found: "eng?"
Line  3246: [   0.808][v][sub_select] setting sid to 1

Sorry I added an extra hyphen, it should be --msg-level=sub_select='trace'. And it's a commandline argument to pass to mpv, not a command.

Ok, had to correct the CLI it is trace without the single quotes.  Here is the logs parsed specifically for sub_select:
Line  149: [   0.008][d][sub_select] Loading lua script D:/mpv/portable_config/scripts/sub-select.lua...
Line  172: [   0.009][d][sub_select] loading file D:/mpv/portable_config/scripts/sub-select.lua
Line  182: [   0.009][d][sub_select] reading options for sub_select
Line  186: [   0.010][v][sub_select] Opened config file script-opts/sub_select.conf.
Line  379: [   0.017][t][sub_select] formatted track info: 000-1-01
Line  155: [   0.008][d][sub_select] loading mp.defaults
Line  380: [   0.018][t][sub_select] formatted track info: 002-0-00
Line  381: [   0.018][v][sub_select] predicted audio track is 2
Line  382: [   0.018][d][sub_select] select subtitle for {"default" = false, "title" = "", "src-id" = 3, "image" = false, "albumart" = false, "dependent" = false, "visual-impaired" = false, "hearing-impaired" = false, "external" = false, "selected" = false, "ff-index" = 2, "id" = 2, "lang" = "jpn", "type" = "audio", "demux-samplerate" = 48000, "audio-channels" = 2, "forced" = false, "demux-channel-count" = 2, "demux-channels" = "unknown2", "codec" = "opus"}
Line  383: [   0.019][d][sub_select] checking pref: {"slang" = "eng?", "condition" = "sub.forced", "blacklist" = {"sign", "s&s"}, "alang" = {"jpn", "ja"}}
Line  384: [   0.019][t][sub_select] Checking for valid audio: jpn
Line  385: [   0.020][t][sub_select] valid audio preference found: {"jpn", "ja"}
Line  386: [   0.020][t][sub_select] checking for valid sub: eng?
Line  387: [   0.021][t][sub_select] checking sub eng? against track {"id" = 0}
Line  388: [   0.021][t][sub_select] checking sub eng? against track {"default" = false, "hearing-impaired" = false, "external" = false, "selected" = false, "ff-index" = 3, "id" = 1, "lang" = "eng", "type" = "sub", "codec" = "ass", "visual-impaired" = false, "title" = "S&S", "src-id" = 4, "forced" = true, "image" = false, "albumart" = false, "dependent" = false}
Line  389: [   0.022][t][sub_select] S&S passed whitelist: nil | failed blacklist: {"sign", "s&s"}
Line  390: [   0.022][t][sub_select] checking sub eng? against track {"default" = true, "hearing-impaired" = false, "external" = false, "selected" = false, "ff-index" = 4, "id" = 2, "lang" = "eng", "type" = "sub", "codec" = "ass", "visual-impaired" = false, "title" = "Dialog - ENG", "src-id" = 5, "forced" = false, "image" = false, "albumart" = false, "dependent" = false}
Line  391: [   0.023][t][sub_select] Dialog - ENG passed whitelist: nil | passed blacklist: {"sign", "s&s"}
Line  392: [   0.023][t][sub_select] evaluating string return sub.forced
Line  393: [   0.023][t][sub_select] checking sub eng? against track {"default" = false, "hearing-impaired" = false, "external" = false, "selected" = false, "ff-index" = 5, "id" = 3, "title" = "[Tenrai-Sensei/NepSubs-modified] No Honorifics", "type" = "sub", "lang" = "und", "codec" = "ass", "visual-impaired" = false, "src-id" = 6, "forced" = false, "image" = false, "albumart" = false, "dependent" = false}
Line  394: [   0.024][d][sub_select] checking pref: {"slang" = {"jpn", "ja"}, "blacklist" = {"sign"}, "alang" = {"jpn", "ja"}}
Line  395: [   0.026][t][sub_select] Checking for valid audio: jpn
Line  396: [   0.026][t][sub_select] valid audio preference found: {"jpn", "ja"}
Line  397: [   0.027][t][sub_select] checking for valid sub: jpn
Line  398: [   0.027][t][sub_select] checking sub jpn against track {"id" = 0}
Line  399: [   0.028][t][sub_select] checking sub jpn against track {"default" = false, "hearing-impaired" = false, "external" = false, "selected" = false, "ff-index" = 3, "id" = 1, "lang" = "eng", "type" = "sub", "codec" = "ass", "visual-impaired" = false, "title" = "S&S", "src-id" = 4, "forced" = true, "image" = false, "albumart" = false, "dependent" = false}
Line  400: [   0.028][t][sub_select] checking sub jpn against track {"default" = true, "hearing-impaired" = false, "external" = false, "selected" = false, "ff-index" = 4, "id" = 2, "lang" = "eng", "type" = "sub", "codec" = "ass", "visual-impaired" = false, "title" = "Dialog - ENG", "src-id" = 5, "forced" = false, "image" = false, "albumart" = false, "dependent" = false}
Line  401: [   0.029][t][sub_select] checking sub jpn against track {"default" = false, "hearing-impaired" = false, "external" = false, "selected" = false, "ff-index" = 5, "id" = 3, "title" = "[Tenrai-Sensei/NepSubs-modified] No Honorifics", "type" = "sub", "lang" = "und", "codec" = "ass", "visual-impaired" = false, "src-id" = 6, "forced" = false, "image" = false, "albumart" = false, "dependent" = false}
Line  402: [   0.029][t][sub_select] checking for valid sub: ja
Line  403: [   0.029][t][sub_select] checking sub ja against track {"id" = 0}
Line  404: [   0.030][t][sub_select] checking sub ja against track {"default" = false, "hearing-impaired" = false, "external" = false, "selected" = false, "ff-index" = 3, "id" = 1, "lang" = "eng", "type" = "sub", "codec" = "ass", "visual-impaired" = false, "title" = "S&S", "src-id" = 4, "forced" = true, "image" = false, "albumart" = false, "dependent" = false}
Line  405: [   0.030][t][sub_select] checking sub ja against track {"default" = true, "hearing-impaired" = false, "external" = false, "selected" = false, "ff-index" = 4, "id" = 2, "lang" = "eng", "type" = "sub", "codec" = "ass", "visual-impaired" = false, "title" = "Dialog - ENG", "src-id" = 5, "forced" = false, "image" = false, "albumart" = false, "dependent" = false}
Line  406: [   0.031][t][sub_select] checking sub ja against track {"default" = false, "hearing-impaired" = false, "external" = false, "selected" = false, "ff-index" = 5, "id" = 3, "title" = "[Tenrai-Sensei/NepSubs-modified] No Honorifics", "type" = "sub", "lang" = "und", "codec" = "ass", "visual-impaired" = false, "src-id" = 6, "forced" = false, "image" = false, "albumart" = false, "dependent" = false}
Line  407: [   0.031][d][sub_select] checking pref: {"slang" = "eng?", "blacklist" = {"force"}, "alang" = {"jpn", "ja"}}
Line  408: [   0.032][t][sub_select] Checking for valid audio: jpn
Line  409: [   0.032][t][sub_select] valid audio preference found: {"jpn", "ja"}
Line  410: [   0.033][t][sub_select] checking for valid sub: eng?
Line  411: [   0.033][t][sub_select] checking sub eng? against track {"id" = 0}
Line  412: [   0.033][t][sub_select] checking sub eng? against track {"default" = false, "hearing-impaired" = false, "external" = false, "selected" = false, "ff-index" = 3, "id" = 1, "lang" = "eng", "type" = "sub", "codec" = "ass", "visual-impaired" = false, "title" = "S&S", "src-id" = 4, "forced" = true, "image" = false, "albumart" = false, "dependent" = false}
Line  413: [   0.034][t][sub_select] S&S passed whitelist: nil | passed blacklist: {"force"}
Line  414: [   0.036][v][sub_select] valid audio preference found: {"jpn", "ja"}
Line  415: [   0.036][v][sub_select] valid subtitle preference found: "eng?"
Line  416: [   0.037][v][sub_select] setting sid to 1
Line 3265: [   0.817][i][sub_select] detected audio change - reselecting subtitles
Line 3272: [   0.818][d][sub_select] select subtitle for {"default" = false, "title" = "", "src-id" = 3, "image" = false, "albumart" = false, "dependent" = false, "visual-impaired" = false, "hearing-impaired" = false, "external" = false, "selected" = false, "ff-index" = 2, "id" = 2, "lang" = "jpn", "type" = "audio", "demux-samplerate" = 48000, "audio-channels" = 2, "forced" = false, "demux-channel-count" = 2, "demux-channels" = "unknown2", "codec" = "opus"}
Line 3273: [   0.819][d][sub_select] checking pref: {"slang" = "eng?", "condition" = "sub.forced", "blacklist" = {"sign", "s&s"}, "alang" = {"jpn", "ja"}}
Line 3274: [   0.819][t][sub_select] Checking for valid audio: jpn
Line 3275: [   0.820][t][sub_select] valid audio preference found: {"jpn", "ja"}
Line 3278: [   0.820][t][sub_select] checking for valid sub: eng?
Line 3280: [   0.821][t][sub_select] checking sub eng? against track {"id" = 0}
Line 3281: [   0.822][t][sub_select] checking sub eng? against track {"default" = false, "hearing-impaired" = false, "external" = false, "selected" = false, "ff-index" = 3, "id" = 1, "lang" = "eng", "type" = "sub", "codec" = "ass", "visual-impaired" = false, "title" = "S&S", "src-id" = 4, "forced" = true, "image" = false, "albumart" = false, "dependent" = false}
Line 3282: [   0.822][t][sub_select] S&S passed whitelist: nil | failed blacklist: {"sign", "s&s"}
Line 3284: [   0.823][t][sub_select] checking sub eng? against track {"default" = true, "hearing-impaired" = false, "external" = false, "selected" = false, "ff-index" = 4, "id" = 2, "lang" = "eng", "type" = "sub", "codec" = "ass", "visual-impaired" = false, "title" = "Dialog - ENG", "src-id" = 5, "forced" = false, "image" = false, "albumart" = false, "dependent" = false}
Line 3286: [   0.824][t][sub_select] Dialog - ENG passed whitelist: nil | passed blacklist: {"sign", "s&s"}
Line 3287: [   0.824][t][sub_select] evaluating string return sub.forced
Line 3288: [   0.825][t][sub_select] checking sub eng? against track {"default" = false, "hearing-impaired" = false, "external" = false, "selected" = false, "ff-index" = 5, "id" = 3, "title" = "[Tenrai-Sensei/NepSubs-modified] No Honorifics", "type" = "sub", "lang" = "und", "codec" = "ass", "visual-impaired" = false, "src-id" = 6, "forced" = false, "image" = false, "albumart" = false, "dependent" = false}
Line 3290: [   0.827][d][sub_select] checking pref: {"slang" = {"jpn", "ja"}, "blacklist" = {"sign"}, "alang" = {"jpn", "ja"}}
Line 3292: [   0.828][t][sub_select] Checking for valid audio: jpn
Line 3296: [   0.828][t][sub_select] valid audio preference found: {"jpn", "ja"}
Line 3297: [   0.829][t][sub_select] checking for valid sub: jpn
Line 3300: [   0.829][t][sub_select] checking sub jpn against track {"id" = 0}
Line 3301: [   0.830][t][sub_select] checking sub jpn against track {"default" = false, "hearing-impaired" = false, "external" = false, "selected" = false, "ff-index" = 3, "id" = 1, "lang" = "eng", "type" = "sub", "codec" = "ass", "visual-impaired" = false, "title" = "S&S", "src-id" = 4, "forced" = true, "image" = false, "albumart" = false, "dependent" = false}
Line 3302: [   0.831][t][sub_select] checking sub jpn against track {"default" = true, "hearing-impaired" = false, "external" = false, "selected" = false, "ff-index" = 4, "id" = 2, "lang" = "eng", "type" = "sub", "codec" = "ass", "visual-impaired" = false, "title" = "Dialog - ENG", "src-id" = 5, "forced" = false, "image" = false, "albumart" = false, "dependent" = false}
Line 3303: [   0.831][t][sub_select] checking sub jpn against track {"default" = false, "hearing-impaired" = false, "external" = false, "selected" = false, "ff-index" = 5, "id" = 3, "title" = "[Tenrai-Sensei/NepSubs-modified] No Honorifics", "type" = "sub", "lang" = "und", "codec" = "ass", "visual-impaired" = false, "src-id" = 6, "forced" = false, "image" = false, "albumart" = false, "dependent" = false}
Line 3304: [   0.832][t][sub_select] checking for valid sub: ja
Line 3305: [   0.833][t][sub_select] checking sub ja against track {"id" = 0}
Line 3306: [   0.834][t][sub_select] checking sub ja against track {"default" = false, "hearing-impaired" = false, "external" = false, "selected" = false, "ff-index" = 3, "id" = 1, "lang" = "eng", "type" = "sub", "codec" = "ass", "visual-impaired" = false, "title" = "S&S", "src-id" = 4, "forced" = true, "image" = false, "albumart" = false, "dependent" = false}
Line 3308: [   0.834][t][sub_select] checking sub ja against track {"default" = true, "hearing-impaired" = false, "external" = false, "selected" = false, "ff-index" = 4, "id" = 2, "lang" = "eng", "type" = "sub", "codec" = "ass", "visual-impaired" = false, "title" = "Dialog - ENG", "src-id" = 5, "forced" = false, "image" = false, "albumart" = false, "dependent" = false}
Line 3310: [   0.835][t][sub_select] checking sub ja against track {"default" = false, "hearing-impaired" = false, "external" = false, "selected" = false, "ff-index" = 5, "id" = 3, "title" = "[Tenrai-Sensei/NepSubs-modified] No Honorifics", "type" = "sub", "lang" = "und", "codec" = "ass", "visual-impaired" = false, "src-id" = 6, "forced" = false, "image" = false, "albumart" = false, "dependent" = false}
Line 3314: [   0.837][d][sub_select] checking pref: {"slang" = "eng?", "blacklist" = {"force"}, "alang" = {"jpn", "ja"}}
Line 3315: [   0.838][t][sub_select] Checking for valid audio: jpn
Line 3317: [   0.838][t][sub_select] valid audio preference found: {"jpn", "ja"}
Line 3318: [   0.839][t][sub_select] checking for valid sub: eng?
Line 3320: [   0.839][t][sub_select] checking sub eng? against track {"id" = 0}
Line 3327: [   0.840][t][sub_select] checking sub eng? against track {"default" = false, "hearing-impaired" = false, "external" = false, "selected" = false, "ff-index" = 3, "id" = 1, "lang" = "eng", "type" = "sub", "codec" = "ass", "visual-impaired" = false, "title" = "S&S", "src-id" = 4, "forced" = true, "image" = false, "albumart" = false, "dependent" = false}
Line 3330: [   0.842][t][sub_select] S&S passed whitelist: nil | passed blacklist: {"force"}
Line 3331: [   0.842][v][sub_select] valid audio preference found: {"jpn", "ja"}
Line 3333: [   0.843][v][sub_select] valid subtitle preference found: "eng?"
Line 3334: [   0.844][v][sub_select] setting sid to 1

The blacklist and the forced condition both seem to be working, what exactly is the issue? What combination of audio and subtitle tracks are you expecting to be selected?

Here is my current JSON setup, but from the video it hard 3 subtitles, the forced one which just S&S (signs and songs) and the 2nd one had the [eng] with Dialog in the text.  My assumption was that the forced subs would see the blacklist and move onto the next set of subs.
[
{
"alang": ["jpn", "ja"],
"slang": "eng?",
"blacklist": [ "sign", "s&s" ],
"condition": "sub.forced"
},
{
"alang": ["jpn", "ja"],
"slang": ["jpn", "ja"],
"blacklist": [ "sign" ]
},
{
"alang": ["jpn", "ja"],
"slang": "eng?",
"blacklist": [ "force" ]
},
{
"alang": ["jpn", "ja"],
"slang": "eng?",
"blacklist": [ "sign" ]
},
{
"alang": ["jpn", "ja"],
"slang": "eng?",
"blacklist": [ "song" ]
},
{
"alang": ["jpn", "ja"],
"slang": "eng?",
"whitelist": [ "full" ],
},
{
"alang": ["jpn", "ja"],
"slang": "eng?",
"whitelist": [ "honorific" ]
},
{
"alang": ["jpn", "ja"],
"slang": "eng?",
"whitelist": [ "dialog" ]
},
{
"alang": ["jpn", "ja"],
"slang": "eng?",
"whitelist": [ "english" ]
},
{
"alang": "*",
"slang": [ "eng?", "und" ]
},
{
"alang": "no",
"slang": "no"
}
]

"blacklist": [ "force" ] doesn't work, it only searches for subtitles with force in the name. It looks like you want to be using "conditon": "not sub.forced".
What is currently happening is that the first condition is failing to match any subtitles because there are not that are both forced, and lack the S&S text in the title. The second condition fails because there are no Japanese subtitle tracks. But the third condition looks at the first track and finds that it is english, and it lacks forced anywhere in the title. Hence it selects it.

Was looking at the said track-list property, but I am not sure how to set the JSON to select a track based on the sub.title condition.  Here is what I setup, but it looks like it will only select the first available [eng] track on the list of empty ones.
{
"alang": "*",
"slang": "eng?",
"condition": "sub.title == ' ' and sub.sid==2"
},
From what I observed every second [eng] track is the one that has the full subtitles but since neither of them as titles, I want to enforce blindly selecting the second [eng] track in order to "assume" it is corret.

If there is genuinely no title, you may need to do not sub.title.

Thanks that worked, covered about 95% of the use cases after doing some testing.  There is a question I have about the blacklist and whitelist.  Is there anyway to define an order within the lists and use that as the criteria to filter before moving to the next criteria?
Example:
[eng] Full English [ABC]
[eng] Full English [XYZ]
{
"alang": "*",
"slang": "eng?",
"whitelist": [ "xyz", "abc", "full", "english"]
},
What I noticed is that "full" would determine the subtitle and not based on the order the white list is set which is "xyz", "abc".  I expected the second subtitle be select first because "xyz" was the first in the whitelist (reading left to right).

You can do them as four separate items:
{
    "alang": "*",
    "slang": "eng?",
    "whitelist": [ "xyz"]
},
{
    "inherit": "^",
    "whitelist": [ "abc"]
},
{
    "inherit": "^",
    "whitelist": [ "full"]
},
{
    "inherit": "^",
    "whitelist": [ "english"]
},

"inherit: "^" copies all of the filters for the above item unless overwritten.

Rather than opening a new thread for diagnosing most likely my misinterpretation of the code I will just post in this old thread as I assume it is not a bug.  I have already updated to the latest lua script from last week and adjusted my json to be a bit more "optimized" but I can't seem to filter out PGS subtitles from the Japanese subtitle track to force to move to the English track check.
Here is the way I structured the json.  Also let me know of "or" statement actually is valid, it appears to work based on how the English track filter behaves.
The file in question has the following alang slang properties:
Audio: jpn
Subtitles:

[eng] English (Fansub)
[jpn] English (PGS)

I checked the properties and only the jpn subtitles has sub.codec == 'pgs'.  This is what I wanted to filter out to force to move to the English filters but it seems to be caught by the lowest filter.
[
{
"inherit": "jpnfilter",
"condition": "not sub.codec == 'pgs' or not sub.codec ~= 'pgs'"
},
{
"inherit": "jpnfilter",
"blacklist": [ "no honor" ],
"whitelist": [ "honor" ]
},
{
"inherit": "jpnfilter",
"whitelist": [ "col" ],
},
{
"inherit": "^",
"whitelist": [ "full" ]
},
{
"inherit": "^",
"whitelist": [ "dialog" ]
},
{
"inherit": "^",
"whitelist": [ "eng" ]
},
{
"inherit": "jpnfilter",
"blacklist": [ "sign", "song", "s&s", "force", "no honor" ],
},
{
"alang": "*",
"slang": ["jpn", "ja" ],
"condition": "sub.codec == 'ass' or sub.codec ~= 'ass'",
"id": "jpnfilter"
},
]
I also tried replacing the  "condition": "sub.codec == 'ass' or sub.codec ~= 'ass'", with the "condition": "not sub.codec == 'pgs' or not sub.codec ~= 'pgs'" but it will still insist on selecting the [jpn] subtitle.

Your very first subtitle preference is selecting Japanese subtitles if they are or aren't PGS. That essentially cancels the condition out, so japanese subtitles will be selected by default.


feat: add helm chart for bootstrapper

Closes #22

Yah this isn't done yet. 😬😁 I just wanted to have something up quickly. I kind of would like to add a values file as well. But don't necessarily see the purpose since I don't have too many settings anyways.

Okay, I'm trying helm releaser. Let's see if I'm doing the right URLs and stuff...

Going to finish this on Monday.


verdor memory io default value

TEST1A/B should be set to False when we work on normal mode
There is only LS input instead of LSA or LSB
RME setting can be set to False as default, let the SRAM choose internal default RM setting.
DA and QB as data input and output interface.

Thanks, the bugs above have been fixed.


Automatic promotion of variable part of assignment

In some cases, promoted variables by the parallelize directive might be used in the rhs of an assignment statement. Like the z(k) = t(k) + q(k) in the following code. In this case, the variable zmust be promoted as well.
To be able to perform this, defined dimension information should be stored in the module file.
MODULE mo_column
  IMPLICIT NONE
CONTAINS

  SUBROUTINE compute_all(nz, q, t)
    INTEGER, INTENT(IN)   :: nz   ! Size of the array field
    REAL, INTENT(INOUT)   :: t(:) ! Field declared as one column only
    REAL, INTENT(INOUT)   :: q(:) ! Field declared as one column only
    REAL :: z(1:nz)
    INTEGER :: k

    DO k=1,nz
      z(k) = t(k) + q(k)
    END DO

    !$claw parallelize forward
    CALL compute_column(nz, q, t)

  END SUBROUTINE compute_all

  ! Compute only one column
  SUBROUTINE compute_column(nz, q, t)
    IMPLICIT NONE

    INTEGER, INTENT(IN)   :: nz   ! Size of the array field
    REAL, INTENT(INOUT)   :: t(:) ! Field declared as one column only
    REAL, INTENT(INOUT)   :: q(:) ! Field declared as one column only
    INTEGER :: k                  ! Loop index
    REAL :: c                     ! Coefficient

    ! CLAW definition

    ! Define one dimension that will be added to the variables defined in the
    ! data clause.
    ! Apply the parallelization transformation on this subroutine.

    !$claw define dimension proma(1:nproma) &
    !$claw parallelize

    c = 5.345
    DO k = 2, nz
      t(k) = c * k
      q(k) = t(k - 1)  + t(k) * c
    END DO
    q(nz) = q(nz) * c

  END SUBROUTINE compute_column
END MODULE mo_column

Most of it is done.
See todo in https://github.com/C2SM-RCM/claw-compiler/blob/89d879e1c551a9f10f0785328787f9f080cccffd/omni-cx2x/src/cx2x/translator/transformation/claw/parallelize/ParallelizeForward.java#L545


How and where can I set the CUDA_VISIBLE_DEVICES when using vllm?

Such as, I set tensor_parallel_size = 1, then it will use the default GPU. Now I want run vllm in another one GPU, so how and where can I set the CUDA_VISIBLE_DEVICES?

OK, I find it. In the work/work.py, the function
def init_model(self) -> None:
        # torch.distributed.all_reduce does not free the input tensor until
        # the synchronization point. This causes the memory usage to grow
        # as the number of all_reduce calls increases. This env var disables
        # this behavior.
        # Related issue:
        # https://discuss.pytorch.org/t/cuda-allocation-lifetime-for-inputs-to-distributed-all-reduce/191573
        os.environ["TORCH_NCCL_AVOID_RECORD_STREAMS"] = "1"

        # This env var set by Ray causes exceptions with graph building.
        os.environ.pop("NCCL_ASYNC_ERROR_HANDLING", None)
        # Env vars will be set by Ray.
        self.rank = self.rank if self.rank is not None else int(
            os.getenv("RANK", "-1"))
        local_rank = int(os.getenv("LOCAL_RANK", "0"))
        self.device = torch.device(f"cuda:{local_rank}")
        if self.rank < 0:
            raise ValueError("Invalid or unspecified rank.")
        torch.cuda.set_device(self.device)

        _check_if_gpu_supports_dtype(self.model_config.dtype)

        # Initialize the distributed environment.
        _init_distributed_environment(self.parallel_config, self.rank,
                                      self.distributed_init_method)

        # Initialize the model.
        set_random_seed(self.model_config.seed)

we just need change local_rank = int(os.getenv("LOCAL_RANK", "0")) to local_rank = int(os.getenv("LOCAL_RANK", "k"))，then the specified GPU is altered from 0 to k.

CUDA_VISIBLE_DEVICES=1 python -m vllm...


PHP formatter breaks when variable does not exist inside current scoop

Check for existing issues

[X] Completed

Describe the bug / provide steps to reproduce it
When you want to format code that have copied or typed that uses a variable that doesn't exist inside the current scope, the formatter will format the code in a weird way, as you can see inside the video below.
Environment
Zed: v0.97.5 (preview)
OS: macOS 14.0.0
Memory: 16 GiB
Architecture: aarch64
If applicable, add mockups / screenshots to help explain present your vision of the feature
https://github.com/zed-industries/community/assets/62463826/fde90765-29d0-4984-8078-2258aca7a519
If applicable, attach your ~/Library/Logs/Zed/Zed.log file to this issue.
If you only need the most recent lines, you can run the zed: open log command palette action to see the last 1000.
No response

Hey @RemcoSmitsDev -  We're likely just using the formatter that comes with the language server, so I'm curious if this issue comes up in any other editors.

@JosephTLyons Looks like VS Code can handle this situation:
https://github.com/zed-industries/community/assets/62463826/381d1041-34d5-4e30-9181-de3d24f11ef0
It looks like Zed can format the code but you have to do the following:

paste code
save file (auto format)
undo save
save file (auto format)

https://github.com/zed-industries/community/assets/62463826/29713132-96bc-4ff8-bd2f-cf85e45dbf93
Or you can do it by:

add new line after {
paste code
save file (auto format)

https://github.com/zed-industries/community/assets/62463826/34e5c3d5-3d9f-4e55-9c78-b871b11cc1a9

Thanks for the detailed report @RemcoSmitsDev, strange that this is happening.  I'll pass it along to the team.

Could you share your config?

Could you share your config?

Which config do you want? I have everything default except the keybinds there from vscode.

Oh. settings.json would be sweet, though if you're not using anything custom then I suppose it's not necessary anymore.

@osiewicz
// Zed settings
//
// For information on how to configure Zed, see the Zed
// documentation: https://zed.dev/docs/configuring-zed
//
// To see all of Zed's default settings without changing your
// custom settings, run the `open default settings` command
// from the command palette or from `Zed` application menu.
{
  "theme": "One Light",
  "base_keymap": "VSCode",
  "buffer_font_size": 15
}

Hi Remco, could you please verify whether this issue still occurs with recent Zed versions? I can't repro this on latest Preview.

@osiewicz I cannot reproduce it anymore as well. So this issue can be closed.

@osiewicz Since a couple of days I have this issue again. I am not sure which update causes this issue again. I will try to find it out.


unapplied trx queue fixes - 2.2

Change Description

Fix handling of duplicate transaction in unapplied_transaction_queue.
Honor return_failure_trace in unapplied_transaction_queue.
Add producer_plugin test for processing transactions
-- Verify no transactions are dropped
-- Verify all transactions are reported
-- Test aborts blocks and creates various invalid transactions
-- Based on amqp_trx_plugin test case

Change Type
Select ONE:

[ ] Documentation

[x] Stability bug fix

[ ] Other

[ ] Other - special case

Testing Changes
Select ANY that apply:

[x] New Tests

[ ] Existing Tests

[ ] Test Framework

[ ] CI System

[ ] Other

Consensus Changes

[ ] Consensus Changes

API Changes

[ ] API Changes

Documentation Additions

[ ] Documentation Additions

https://github.com/EOSIO/eos/pull/10687


Content Screening Logic

Corporate TOS issue:  “We do not pre-screen User-Generated Content, but we have the right (though not the obligation) to refuse or remove any User-Generated Content that, in our sole discretion, violates any GitHub terms or policies.” Logically, how do you “refuse” content you’re not pre-screening before it goes live?

Thanks, we'll take a look.


Add PIC option

Just add a PIC option: no change of behavior, default still OFF.

@gchatelet  any way to merge that one before the new tag/release ? tks

@gchatelet any way to merge that one before the new tag/release ? tks

Sorry I had a pending review that was never sent ...

Thx for working on this @WilliamTambellini !


Set USER environment variable by default

Start a container and you'll note that the $USER environment variable won't be set. This variable should be injected in the container by VSCode since it knows which is the user name.
In my case, I use this environment variable in my dotfiles/install script.

Workaround:
// devcontainer.json
{
  "containerUser": "vscode",
  "containerEnv": {
      "USER": "vscode"
    }
}

Yeah, script-library/common-debian.sh should be able to add this via .bashrc/.zshrc using the id command.

@Chuxel that would not solve the problem, since .bashrc and .zshrc are replaced when using dotfiles.
We need to find something different.

That's then a feature request for the extension.  Will move to the other repo. //cc: @chrmarti


Notifications: don't go to top page when closing it

When clicking on the X, now it calls preventDefault() to avoid moving to the top
I added some id= attributes in the index page to test this manually

Closes #246

I would say it's fine as is, your fix does solve the problem. In places where we need to worry about users with JS disabled, it's best to make this a valid URL. But obviously we don't have that problem with Addons.


Added config-provider

Example:
angular.module('chosenExampleApp', ['localytics.directives'])
    .config(['chosenProvider', function (chosenProvider) {
        chosenProvider.setOption({
            no_results_text: 'Haha! There is no results!',
	    placeholder_text_multiple: 'Choose a few!'
        });
    }]);

@leocaseiro, hi! There is cool feature!

Hi @zlodes, thanks for sending this PR. I'll have a deep look next week, so I can publish within the next release.

Release 1.6.0!!!
🎉  🍺


Packet loss: 0%

6-8 precision would be better than rounding to 0 %
.000000

0% means no packets were lost. There's 2 digits of precision currently with packet loss present.


changed the gitter link in docs>faq.rst

Changed the gitter link from https://gitter.im/golastmile/rasa_nlu to https://gitter.im/RasaHQ/rasa_nlu in faq.rst in reference to issue #396

Why the tests are failing on fixing a link in docs?

There was an issue with the git history, please merge in the latest master.


🐛 API | New users are redirected to Admin portal after they confirm their email

@AntPolkanov can you please add a description here?

Figure: Entering Admin portal when signing up (probably every 1/5 logins)


Upgrade pip in Dockerfile.ui_service to version 22.0.4

Fix https://github.com/Netflix/metaflow-service/issues/311 by upgrading pip in Dockerfile.ui_service

Thanks for the PR! I failed to reproduce this but it seems like the culprit is that the python:3.7 image you had locally had an older version of pip than the most recent one. If you do docker pull python:3.7 && docker run -it --rm python:3.7 pip -V today you'll see that it is already 22.0.4
I found that it has been upgraded in this commit https://github.com/docker-library/python/commit/a9815ead3ae016edf7039285cb267b14a5700169
I'm thinking maybe a slightly cleaner fix for this issue would be to pin image version to 3.7.13 in FROM but continue using pip that comes with the base image.

Ah thanks! Yes that makes a lot more sense, have updated the PR


Add API endpoint to get latest version of all projects

There are projects like https://release-monitoring.org/ which want to monitor PyPI to see when new versions of specific projects are released. Currently this requires doing 1 HTTP request per tracked project which can easily turn into hundreds or thousands of HTTP requests. Offering an endpoint that simply lists the names and versions of all projects can make this take a single HTTP request.

\cc

It'd also be helpful if it was possible to search through the list with some filters. I've been meaning to add an instant answer to duckduckgo for python packages, but sadly it's not possible right now as there is no search API. I can also work on it. Just wondering why it doesn't exit yet.

Would it be possible to solve this need (the use case for release-monitoring.org) instead by streaming and parsing the PyPI update changelog, similar to how bandersnatch figures out what new updates to sync on a mirror?

Would be also useful for PyCharm IDE to notify about outdated packages in the integrated package manager.

It could be efficient to also serve cached deltas of the whole catalog? e.g. an optional from=iso8601datetime?

Is there something like DRPMS or rsync over HTTP that could reasonably be added in a view and generated in a celery WarehouseTask?
etags, If-Modified-Since

@traff it seems that pulling current versions for all packages on the index may be a bit overzealous. getting a list from /simple should be sufficient for offering users a dialog of installable packages... the current/latest version identifier is arguably unimportant at that point.
perhaps after a user as identified a package by name, a cheap (cached at edge) call to the json API would be successful for offering a list of installable versions. GET https://pypi.python.org/pypi/<package_name>/json
regarding offering updates, again the existing json api would support a call per package to get current versions using the same call as above . these calls are cached at the edge, should be fast for end users, and are 100% fair game for community use.
i suppose my question is how is 1 long (2-10s) request to obtain a list of all package/versions better than N 200-500ms requests (which can be submitted concurrently) in order to provide information on current versions and available updates.

to be clear, i'm not opposed to supporting the specific feature request in this issue. but am trying to aide in guiding PyCharm off of the currently used index page they are scraping for this information.
that page is incredibly expensive to generate and often causes congestion for the PyPI backends.

@ewdurbin Yes, that makes sense. The only doubt we had is that making N request is worse than making one. But in this case it could be on the contrary.

indeed, @dstufft did a great job of summarizing the state of the world:
here and here

Relevant mailing list threads:

"[Distutils] PyPI index workaround" https://mail.python.org/pipermail/distutils-sig/2016-July/029236.html

re: efficient ways to poll for latest versions of multiple PyPI packages

One thing like this could allow for is providing a JSON API for this info instead of having to parse the HTML of the /simple page to just get a list of projects.

So, what is the objective here:

"Add API endpoint to get latest version of all projects"

add versions to /simple

cache invalidate on every package upload and then JOIN all packages
(so that everyone re-downloads the whole catalog every time)

"Add API endpoint to get latest versions and package checksums of a
specific subset of projects matching version and/or package and platform
constraints"

On Aug 6, 2016 3:18 PM, "Brett Cannon"<EMAIL_ADDRESS>wrote:

One thing like this could allow for is providing a JSON API for this info
instead of having to parse the HTML of the /simple page to just get a list
of projects.

So, caching and conditional requests (with etags) would probably be the
only way to afford this functionality (SELECT * FROM packages WHERE package
IN {pip, pytest, virtualenv, scripttest, mock, pretend})
Seemingly OT, but this may be the best guide to REST API cache management
(cache keys, etags, invalidation) I've ever read:
http://chibisov.github.io/drf-extensions/docs/#caching

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or mute the thread.

Would love to be able to checksums for the releases from this API somehow.

@jakirkham Checksum for what? The files?

Sorry for the delay. Yes, for the files.

Added issue ( https://github.com/pypa/warehouse/issues/1638 ) for getting the checksums via the API.

+1 here, the same is needed for repology.org, from which I've had to remove PyPi support since https://pypi.python.org/pypi/ which it used got deprecated.
So, it'd be nice to have a (not necessary realtime, regenerated hourly is ok for my purposes) machine-readable dump of all PyPi packages with versions and preferrably other metadata such as summaries and licenses.
Example of what I'd like to have for repology:
[
    {
        "name": "requests",
        "version": "2.18.1",
        "summary": "Python HTTP for Humans."
    }
    ...
]

I recognize that this is beyond the scope of this particular issue, but,
how is this problem different from BitTorrent w/ HTTP web seeds?
https://en.wikipedia.org/wiki/BitTorrent#Web_seeding

manifest
hashes
mirroring

On Thursday, August 10, 2017, Wes Turner<EMAIL_ADDRESS>wrote:

I recognize that this is beyond the scope of this particular issue, but,
how is this problem different from BitTorrent w/ HTTP web seeds?
https://en.wikipedia.org/wiki/BitTorrent#Web_seeding

manifest
hashes
mirroring

(In context to mirroring with e.g. bandersnatch).

MD5 is no longer recommended?
https://en.wikipedia.org/wiki/MD5#Overview_of_security_issues

It could be efficient to also serve cached deltas of the whole catalog? e.g. an optional from=iso8601datetime?

Is there something like DRPMS or rsync over HTTP that could reasonably be added in a view and generated in a celery WarehouseTask?
etags, If-Modified-Since

Zsync is like rsync over HTTP
http://zsync.moria.org.uk/

zsync provides transfers that are nearly as efficient as rsync -z or cvsup, without the need to run a special server application. All that is needed is an HTTP/1.1-compliant web server.

[...]

Single meta-file — zsync downloads are offered by building a .zsync file, which contains the meta-data needed by zsync. This file contains the precalculated checksums for the rsync algorithm; it is generated on the server, once, and is then used by any number of downloaders.

I'm grateful for the discussion here and apologize for the slow response.
There's now an open issue #1478 for getting a regular dump of the PyPI database, and other open issues tagged as "APIs/feeds". And now, https://warehouse.readthedocs.io/api-reference/ has a bunch more guidance on how developers can use the Warehouse APIs (RSS feeds, JSON, /simple/ emulation of the legacy API, and XML-RPC methods) already available at https://pypi.org .
The folks working on Warehouse have gotten funding to concentrate on improving and deploying Warehouse, and have kicked off work towards our development roadmap -- the most urgent task is to improve Warehouse to the point where we can redirect pypi.python.org to pypi.org so the site is more sustainable and reliable, and shut down the legacy site. We discussed this issue in our core developers' meeting today. Since this feature isn't something that the legacy site has, I've moved it to a future milestone.
I would be pleased to add this issue to the list of things people work on at this year's PyCon sprints if folks are interested.
Thanks and sorry again for the wait.

Folks who need this might want to check whether the Libraries.io API for https://libraries.io/pypi might suit their needs in the short term.

It doesn't look suitable - I see no means to bulk get information on all projects. The closest search endpoint returns right information, but it's only possible to request packages page by page and maximal page size is 100 items, which, given API rate limit of 60 requests/minute and PyPi size of >136k packages gives us more than 20 minutes needed to get all the data - this is too much. There are other issues as well:

there's no option of getting results sorted by package name (other sort variants may lead to lost or duplicate packages because of reordering during retrieval)
the API doesn't seem to be stable, I'm having 500 errors when requesting above 100th page
the requirement to get an API key may be unacceptable to some users (including me)
the requirement to use third party site is also not good

Hi there, just to throw in my $0.0.2 here - I use a utility which checks a requirements.txt file's pinned versions to see if there are newer releases existing on pypi. If there are N packages in the file I currently make N requests to pypi.

@wimglenn which util is this?   I'm looking for this type of tool.

I predict that work on this may depend on the progress of #284.
From December 2017 till the end of April 2018, PyPI had funding to get the new site up and running and perform the switchover. Then the grant ran out and we have, as far as I know, no one paid to work on PyPI; volunteers are maintaining and improving the software and infrastructure sides of things, but we need dedicated funding to add complex features. The Packaging Working Group is seeking donations and applying for further grants to fund more design work, more and faster development (including reviewing code contributed by volunteers), and requisite project management.
Sorry for the wait.

@retr0h  This was a tool developed internally at $EMPLOYER, but I've since requested permission to open source it and $EMPLOYER has agreed.  It's on PyPI so you can pip install luddite and the project homepage is now right here on github.

process_line() in https://github.com/pypa/pip/blob/master/src/pip/_internal/req/req_file.py may be helpful for parsing requirements files; though this does not solve for "API endpoint to get latest version of all projects".


Library to Manipulate array as Table.

I have implemented an Array manipulation library which works similar to Codeigniter Query Builder.
Consider Associate/result array as an table and library can handle it.
This feature is really required one too.
It will help us reduce repeated calls of mysql.
Read  this to know more about the features include within the library.
As a codeigniter user, I want to contribute my work for the forth development. Please review and let me know.
Thanks...!

First off - looks like a very cool library with some pretty thorough features. Probably a lot of work put into that, nice job!
That being said, I'm not convinced that's right for the core framework. What do you think @jim-parry ?

Interesting library, for sure. I agree - it doesn't fit with the framework at the moment.
It could be an interesting third-party addin.

@lonnieezell  @jim-parry  Thanks...! :smile:
Understood. It can fit as a library. It's also nice.
And I have an idea, Is it possible..., CI can create a section for all kind of third-party add on/libraries, in CI repo/guide?
We know composer is good. But if its available directly in CI that will be help everyone too.. :smiley:

We plan an addins section on our website. Putting third party addins into the main repo/guide is the same as including them with the framework - they need to be external.

Ok. understood...! @jim-parry


Formating data after multiple fetch in atmo indice, still lot of format pb

Formating data after multiple fetch in atmo indice, still lot of format pb

:tada: This PR is included in version 1.14.0 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Make Profile page design cosistent with the rest of UI

Is your feature request related to a problem? Please describe.
The Profile Page UI looks not consistent alongside other pages.
Describe the solution you'd like
Refresh the UI.
Describe alternatives you've considered
N/A
Additional context
Specific changes can be listed here:

[ ] Center circular progress loaders
[ ] Chose right color palete
[ ] Resize sub-components

Also worth implementing with #420


Brings CamelCase naming convention for Vue component files

Brings CamelCase naming convention for Vue component files based on TYPO3 content element types (https://github.com/TYPO3-Initiatives/nuxt-typo3/issues/46)

Updated pull-request: https://github.com/TYPO3-Initiatives/nuxt-typo3/pull/50

@Moongazer brilliant 🥇 can we split this PR ? I mean - backend layouts changes should be on separated branch.


Enable useBitLib option by default?

Lua 5.3 added bitwise operators (<<, >>, &, |, ~).
LuaJIT has the bit module.
Fennel has the functions lshift, rshift, band, bor, bxor, bnot.
By default, these compile to be Lua 5.3 operators.  You can pass the option useBitLib to the Fennel compiler to make it use the bit module.  This is not mentioned in the API reference so it may not be considered "stable" but it's what the Fennel CLI uses for the --use-bit-lib argument.
Given that hotpot targets Neovim specifically I think this should always be done.

I don't disagree that it could be enabled by default, but I am hesitant to do it because it isn't a complete compatibility layer: "The integer division operator (//) is only available in Lua 5.3+" and they "cannot be used as higher-order functions".
I think that puts some onus on the user to know what they want to use and how they can use it so it should probably be opt in.

I was just reading the Fennel reference and saw that passage.  I guess useBitLib is documented after all.

cannot be used as higher-order functions

That's always true though, LuaJIT or not.

The integer division operator (//) is only available in Lua 5.3+

There is, indeed, nothing that can be done in this case.
Still, not using the option is definitely the less correct solution for Neovim (at least so long as LuaJIT is the only supported implementation).

Hello!
Seeing this issue and fennel's supports for bitlib, how do I enable it within hotpot?
fennel.compile doesn't seem to take any related options and passing any of "--use-bit-lib", "use-bit-lib" to hotpotConfig.compiler table doesn't provide support for it
require("hotpot").setup {
  provide_require_fennel = true,
  enable_hotpot_diagnostics = true,
  compiler = {
    ["--use-bit-lib"] = true,
    ["use-bit-lib"] = true,
    "--use-bit-lib",
    "use-bit-lib",
    modules = {
      correlate = true,
    },
  },
}

It needs to go in the modules (and optionally macros) table, the option name is useBitLib per  https://fennel-lang.org/reference.

These all work as you would expect, with a few caveats. The bitwise operators are only available in Lua 5.3+, unless you use the --use-bit-lib flag or the useBitLib flag in the options table, which lets them be used in LuaJIT. The integer division operator (//) is only available in Lua 5.3+.

modules = {
  correlate = true,
  useBitLib = true,
},

You might have to touch/save/edit files that you want to use the bit operators in to trigger a recompile with the new options.

Many thanks


Package Declarations1

Description
Package Declarations1
Change request type

[ ] Release or process automation (GitHub workflows, internal scripts)
[ ] Internal documentation
[ ] External documentation
[x] Query files (.ql, .qll, .qls or unit tests)
[ ] External scripts (analysis report or other code shipped as part of a release)

Rules with added or modified queries

[ ] No rules added
[x] Queries have been added for the following rules:

DCL37-C

[ ] Queries have been modified for the following rules:

rule number here

Release change checklist
A change note (development_handbook.md#change-notes) is required for any pull request which modifies:

The structure or layout of the release artifacts.
The evaluation performance (memory, execution time) of an existing query.
The results of an existing query in any circumstance.

If you are only adding new rule queries, a change note is not required.
Author: Is a change note required?

[ ] Yes
[x] No

Reviewer: Confirm that either a change note is not required or the change note is required and has been added.

[ ] Confirmed

Query development review checklist
For PRs that add new queries or modify existing queries, the following checklist should be completed by both the author and reviewer:
Author

[ ] Have all the relevant rule package description files been checked in?
[ ] Have you verified that the metadata properties of each new query is set appropriately?
[ ] Do all the unit tests contain both "COMPLIANT" and "NON_COMPLIANT" cases?
[ ] Are the alert messages properly formatted and consistent with the style guide?
[ ] Have you run the queries on OpenPilot and verified that the performance and results are acceptable?As a rule of thumb, predicates specific to the query should take no more than 1 minute, and for simple queries be under 10 seconds. If this is not the case, this should be highlighted and agreed in the code review process.
[ ] Does the query have an appropriate level of in-query comments/documentation?
[ ] Have you considered/identified possible edge cases?
[ ] Does the query not reinvent features in the standard library?
[ ] Can the query be simplified further (not golfed!)

Reviewer

[ ] Have all the relevant rule package description files been checked in?
[ ] Have you verified that the metadata properties of each new query is set appropriately?
[ ] Do all the unit tests contain both "COMPLIANT" and "NON_COMPLIANT" cases?
[ ] Are the alert messages properly formatted and consistent with the style guide?
[ ] Have you run the queries on OpenPilot and verified that the performance and results are acceptable?As a rule of thumb, predicates specific to the query should take no more than 1 minute, and for simple queries be under 10 seconds. If this is not the case, this should be highlighted and agreed in the code review process.
[ ] Does the query have an appropriate level of in-query comments/documentation?
[ ] Have you considered/identified possible edge cases?
[ ] Does the query not reinvent features in the standard library?
[ ] Can the query be simplified further (not golfed!)

Notes DCL37-C
I did not implement the future library directions restrictions for this rule, and described that in the implementation notes, however if it seems like these would be crucial, I can add those

Notes DCL31-C
currently not supporting "check for implicit function declarations" portion of the rule, only supporting "Omission of type specifiers" portion
I need a reminder for what to do if our test setup doesnt compile a certain test, but other compilers do
the following:
int main(void) {
  for (int i = 0; i < 100; ++i) {
    /* int malloc() assumed */
    char *ptr = (char *)malloc(0x10000000);
    *ptr = 'a';
  }
  return 0;
}

compiles with: gcc -c test.c
with
gcc-11 (Homebrew GCC 11.3.0) 11.3.0
but codeql test run --show-extractor-output --search-path .  c/cert/test/rules/DCL31C/DeclareIdentifiersBeforeUsingThem.qlref fails (for clang)

RULE-5-1 notes
some perf issue exists for this one currently, related to joining on names I think, but was hoping that external identifiers subclass was a small enough set to avoid this

"Ok, let's add an issue to this repository to investigate using a different data source for the C standard library names."
done


Sigma split

SigmaStockRecolor was split into Jool Recolor (new) and Eve Recolor (holds identifier).
SigmaRTExpansion was moved to github and renamed to Sigma: Antennas (holds identifier).
SigmaModExpansions was moved to github and renamed to Sigma: OuterSpaceComms (holds identifier).
SigmaBinary was split into SigmaBinary-core and SigmaBinary-DunaIke (both hold there identifier).

I clearly don't understand enough of Jenkins and while this fails.

SigmaBinary-DunaIke.netkan needs a ksp_version.
SigmaBinary-DunaIke.netkan and SigmaBinary-core.netkan would benefit from a netkan epoch.
@Sigma88 would appreciate you giving this a once-over.

@plague006  sorry but I have exactly zero idea of what that mean :)

everything seems fine to me

:+1: merging with my thanks.


Implement Hash for Schema

Which issue does this PR close?
Closes #2182.
Rationale for this change
Hash is sometimes helpful, see #2182 for some examples.
What changes are included in this PR?
Implements Hash for Schema.
Are there any user-facing changes?
New trait implementation, not a breaking change.

I think this is fine, although I do wonder if we need some way to highlight that this is a relatively expensive computation...

The "expensiveness" was more concerned regarding the usage. I think a user should judge how expensive Eq/Hash on complex/container-like data structures are. You can easily Eq/Hash BTreeSet<BTreeMap<String, Vec<String>>> but sure, it's expensive. Same goes for a Schema, esp. if you attach LOADS for metadata.
However we could add a doc comment somewhere.


Update akka-stream to 2.6.11

Updates com.typesafe.akka:akka-stream from 2.6.10 to 2.6.11.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "com.typesafe.akka", artifactId = "akka-stream" } ]

labels: library-update, semver-patch

Superseded by #53.

Superseded by #53.


virt-launcher, agent-poller, Fix replaceTicker logic

Guest agent poller timer has exponential backoff logic.
Since interval is already a time.Duration, it means it is already multiplied
by time.Second (see pollInitialInterval declaration).
Multiplying it again, will result in multiplying it by
1,000,000,000, and the pollers whose ticker is updated
won't be run for a long time, since the new
interval is not the expected one, but much bigger.
Fix it by removing the extra unneeded multiply.
Fix unit tests to validate the exponential backoff logic.
Signed-off-by: Or Shoval<EMAIL_ADDRESS>None

/cc @EdDev

Validated that with the fix its working as expected, 10, 20 ... 120 ... 120 ...
Without the fix it ran only the two first time (one outside the for, and the first in the for)
{"component":"virt-launcher","level":"info","msg":"DBGDBG1 guest-network-get-interfaces","pos":"agent_poller.go:363","timestamp":"2021-04-01T14:00:57.880085Z"}
{"component":"virt-launcher","level":"info","msg":"DBGDBG1 guest-network-get-interfaces","pos":"agent_poller.go:363","timestamp":"2021-04-01T14:01:07.887445Z"}
{"component":"virt-launcher","level":"info","msg":"DBGDBG1 guest-network-get-interfaces","pos":"agent_poller.go:363","timestamp":"2021-04-01T14:01:27.891681Z"}
{"component":"virt-launcher","level":"info","msg":"DBGDBG1 guest-network-get-interfaces","pos":"agent_poller.go:363","timestamp":"2021-04-01T14:02:07.897586Z"}
{"component":"virt-launcher","level":"info","msg":"DBGDBG1 guest-network-get-interfaces","pos":"agent_poller.go:363","timestamp":"2021-04-01T14:03:27.903438Z"}
{"component":"virt-launcher","level":"info","msg":"DBGDBG1 guest-network-get-interfaces","pos":"agent_poller.go:363","timestamp":"2021-04-01T14:05:27.909797Z"}
{"component":"virt-launcher","level":"info","msg":"DBGDBG1 guest-network-get-interfaces","pos":"agent_poller.go:363","timestamp":"2021-04-01T14:07:27.909826Z"}
{"component":"virt-launcher","level":"info","msg":"DBGDBG1 guest-network-get-interfaces","pos":"agent_poller.go:363","timestamp":"2021-04-01T14:09:27.909829Z"}
{"component":"virt-launcher","level":"info","msg":"DBGDBG1 guest-network-get-interfaces","pos":"agent_poller.go:363","timestamp":"2021-04-01T14:11:27.909818Z"}
{"component":"virt-launcher","level":"info","msg":"DBGDBG1 guest-network-get-interfaces","pos":"agent_poller.go:363","timestamp":"2021-04-01T14:13:27.909841Z"}
{"component":"virt-launcher","level":"info","msg":"DBGDBG1 guest-network-get-interfaces","pos":"agent_poller.go:363","timestamp":"2021-04-01T14:15:27.909838Z"}
{"component":"virt-launcher","level":"info","msg":"DBGDBG1 guest-network-get-interfaces","pos":"agent_poller.go:363","timestamp":"2021-04-01T14:17:27.909827Z"}
{"component":"virt-launcher","level":"info","msg":"DBGDBG1 guest-network-get-interfaces","pos":"agent_poller.go:363","timestamp":"2021-04-01T14:19:27.909854Z"}
{"component":"virt-launcher","level":"info","msg":"DBGDBG1 guest-network-get-interfaces","pos":"agent_poller.go:363","timestamp":"2021-04-01T14:21:27.909829Z"}

This should work:
diff --git a/pkg/virt-launcher/virtwrap/agent-poller/agent_poller_test.go b/pkg/virt-launcher/virtwrap/agent-poller/agent_poller_test.go
index 14df4002a..dfc2a5a09 100644
--- a/pkg/virt-launcher/virtwrap/agent-poller/agent_poller_test.go
+++ b/pkg/virt-launcher/virtwrap/agent-poller/agent_poller_test.go
@@ -106,12 +106,12 @@ var _ = Describe("Qemu agent poller", func() {

                It("executes the agent commands based on the minimum interval at initial run", func() {
                        const interval = 30
-                       const expectedExecutions = 2
+                       const expectedExecutions = 3

                        // Given the initial interval is 10sec, the code under test is expected to execute the commands at time:
                        // 0, 10sec, 10sec + 2*10sec
-                       // Therefore, setting a timeout limit of 20sec should cover the first 2 executions.
-                       t := 2 * pollInitialInterval
+                       // Therefore, setting a timeout limit of 40sec should cover the first 3 executions.
+                       t := 4 * pollInitialInterval
                        commandExecutions := runPollAndCountCommandExecution(interval, expectedExecutions, t)

                        Expect(commandExecutions).To(Equal(expectedExecutions))

It will add 20 second to the unit tests, which already fail sometimes because they are too long,
so maybe worth to add a parameter of starting interval to func (p *PollerWorker) Poll,
So the unit test can use 1 or 2 seconds while the production code will use the 10 seconds?

It will add 20 second to the unit tests, which already fail sometimes because they are too long,
so maybe worth to add a parameter of starting interval to func (p *PollerWorker) Poll,
So the unit test can use 1 or 2 seconds while the production code will use the 10 seconds?

I guess you mean making the pollInitialInterval an argument of the Poll function.
I'm ok with that. Just make it a separate commit in order to reason for it well (allowing testability).

Adapted unit tests

/test pull-kubevirt-unit-test
failed on something else which seems to be flake before that

Addressed comments

/retest
unrelated just docker timeout on sriov lane while pulling imega/jq:1.6

Updated according comment

The value 30 is fine, I do not understand why you touched it. The point of the test, as the text says, is to execute the agent commands based on the minimum interval, i.e. the initial-interval.
So this "stable" interval is not relevant except for being high enough not to reach it (which now you changed).

For some reason its not in a thread,
i think that we should scale also the 30 seconds, once we are changing the interval to 1 second, in this test
but will change it back to 30 seconds.

Addressed comments

Addressed comments

Thanks @EdDev
/cc @enp0s3
can you take a look please?

Do we need to cherry-pick this to release 0.39.1 ?
its not there

/cherry-pick release-0.36


Reset to specific revision

I would like to reset HEAD~1 --hard , so reset to a specific revision / drop the last commit.
Right now it's not clear to me how to pass the revision to the Dolt.reset() method.
A possible solution could be adding the revision as the first parameter (not passing via kwargs) and appending it to args before --soft / --hard :
def reset(
    self,
    revision: str,
    tables: Union[str, List[str]] = [],
    hard: bool = False,
    soft: bool = False,
    **kwargs,
):
    """
    Reset a table or set of tables that have changes in the working set to their value at the tip of the current
    branch.
    :param tables:
    :param hard:
    :param soft:
    :return:
    """
    if not isinstance(tables, (str, list)):
        raise ValueError(
            f"tables should be: Union[str, List[str]]; found {type(tables)}"
        )

    to_reset = to_list(tables)

    args = ["reset"]

    if hard and soft:
        raise ValueError("Specify one of: hard=True, soft=True")

    if (hard or soft) and to_reset:
        raise ValueError("Specify either hard/soft flag, or tables to reset")

    args.append(revision)

    if hard:
        args.append("--hard")
    elif soft:
        args.append("--soft")
    elif not tables:
        args.append("--soft")
    else:
        args += to_reset

    self.execute(args, **kwargs)

We don't actively maintain the Dolt python interface.
We've moved most of our effort to supporting the SQL interface because that works in every language.
This seems like a simple patch though. I'll see if I can get someone to crank it out.

I think this PR should help expose the revision parameter to match our CLI more closely: https://github.com/dolthub/doltcli/pull/41


Docker cli command for support has container in it. Please remove container from docker run.

File: datacenter/ucp/2.2/guides/get-support.md, CC @jimgalasyn

docker container run and docker run can be used interchangeably. We favor docker container run since it's more verbose and easier for new Docker users.


Fix typo

I think the 'kubernets' should be start with 'K', so I fix it.

/assign @ahmetb

@ahmetb Can you help review this PR? thanks!

/lgtm


ScannetV2_train/test.txt Path

Thank you for sharing interesting work here. I'm curious about your caption module, but it seems that there exists a dataset_path folder for scannetv2_train.txt that can not be found in your updated folder, need I to download it somewhere?

Hi, thanks for your interest in our paper. You may need to download the dataset required for training and inference. Please refer to this doc: https://github.com/CVMI-Lab/PLA/blob/main/docs/DATASET.md.

Thanks, what great work!


Django1.9

Updates all required packages to run on Django 1.9.
Please note: you will need to update your settings.py to replace the TEMPLATE_* settings with the following:
TEMPLATES = [
{
    'BACKEND': 'django.template.backends.django.DjangoTemplates',
    'DIRS': [
        "/var/django/dplace/dplace_app/templates",
    ],
    'APP_DIRS': True,
    'OPTIONS': {
        'debug': DEBUG,
        'context_processors': [
            'django.contrib.auth.context_processors.auth',
            'django.template.context_processors.debug',
            'django.template.context_processors.i18n',
            'django.template.context_processors.media',
            'django.template.context_processors.static',
            'django.template.context_processors.tz',
            'django.contrib.messages.context_processors.messages',
        ],
    },
},

]
See here for more details.

Current coverage is 89.60%

Merging #242 into master will decrease coverage by -0.72% as of f0a1681

@@            master   #242   diff @@
=====================================
  Files           25     25
  Stmts         1674   1674
  Branches         0      0
  Methods          0      0
=====================================
- Hit           1512   1500    -12
  Partial          0      0
- Missed         162    174    +12

Review entire Coverage Diff as of f0a1681

Powered by Codecov. Updated on successful CI builds.

Hi @SimonGreenhill. If DEBUG = false we have to set ALLOWED_HOSTS. But if I upgrade my local installation to Django 1.9.2 I get the following error if I try to run the server via
./manage.py runserver <IP_ADDRESS>:8000:
(env_dplace)dplace_user@precise64:/var/django/dplace$ ./manage.py runserver <IP_ADDRESS>:8000 Unhandled exception in thread started by <function wrapper at 0x1bc5aa0> Traceback (most recent call last):   File "/home/dplace_user/env_dplace/local/lib/python2.7/site-packages/django/utils/autoreload.py", line 226, in wrapper     fn(*args, **kwargs)   File "/home/dplace_user/env_dplace/local/lib/python2.7/site-packages/django/core/management/commands/runserver.py", line 109, in inner_run     autoreload.raise_last_exception()   File "/home/dplace_user/env_dplace/local/lib/python2.7/site-packages/django/utils/autoreload.py", line 249, in raise_last_exception     six.reraise(*_exception)   File "/home/dplace_user/env_dplace/local/lib/python2.7/site-packages/django/utils/autoreload.py", line 226, in wrapper     fn(*args, **kwargs)   File "/home/dplace_user/env_dplace/local/lib/python2.7/site-packages/django/__init__.py", line 18, in setup     apps.populate(settings.INSTALLED_APPS)   File "/home/dplace_user/env_dplace/local/lib/python2.7/site-packages/django/apps/registry.py", line 85, in populate     app_config = AppConfig.create(entry)   File "/home/dplace_user/env_dplace/local/lib/python2.7/site-packages/django/apps/config.py", line 123, in create     import_module(entry)   File "/usr/lib/python2.7/importlib/__init__.py", line 37, in import_module     __import__(name) ImportError: Import by filename is not supported.
Any hints?

@SimonGreenhill : What do you mean in settings.template line 126 ?
124 INSTALLED_APPS = (
125    'django.contrib.auth',
126    'django.contrib./Users/dan/Code/django/dplace/dplace_app/templatesenttypes',

If I change line 126 back to:
'django.contrib.contenttypes'
the server runs. It only gives a warning:
/home/dplace_user/env_dplace/local/lib/python2.7/site-packages/django_filters/filterset.py:103: RemovedInDjango110Warning: 'get_field_by_name is an unofficial API that has been deprecated. You may be able to replace it with 'get_field()'   rel, model, direct, m2m = opts.get_field_by_name(parts[-1])

I tried to rebuild the db, but load_all_datasets.sh gives many errors like:
Traceback (most recent call last):   File "./dplace_app/load.py", line 9, in <module>     from load.util import configure_logging, csv_dict_reader   File "/var/django/dplace/dplace_app/load/util.py", line 9, in <module>     from dplace_app.models import Society, GeographicRegion   File "/var/django/dplace/dplace_app/models.py", line 28, in <module>     class ISOCode(models.Model):   File "/home/dplace_user/env_dplace/local/lib/python2.7/site-packages/django/db/models/base.py", line 94, in __new__     app_config = apps.get_containing_app_config(module)   File "/home/dplace_user/env_dplace/local/lib/python2.7/site-packages/django/apps/registry.py", line 239, in get_containing_app_config     self.check_apps_ready()   File "/home/dplace_user/env_dplace/local/lib/python2.7/site-packages/django/apps/registry.py", line 124, in check_apps_ready     raise AppRegistryNotReady("Apps aren't loaded yet.") django.core.exceptions.AppRegistryNotReady: Apps aren't loaded yet.

Hi @Bibiko, sorry for the hassles. Yes, that's a glitch in settings.template -- should be 'django.contrib.contenttypes'


this.$validatior.reset() resets valid flag to null

When I save my form I am calling this.$validator.reset() to reset the field flags like changed, dirty, etc. But the reset command updated the valid field to null instead to true.
Any idea why?
This breaks functionality for this computed property, to which sets if entire form is valid:
  computed: {
    formValid () {
      return Object.keys(this.vFields).every(field => {
        return this.vFields[field] && this.vFields[field].valid
      })
    }
}

I had this problem and found this issue. In my use case, I am saving data to my server and then once the data has been successfully saved, I want the form to reset to its original state. I am using reset() to do this. In my case, I know the data is valid since it just got echoed back from my server, so I did the following:
    isFormValid () {       // loop over all contents of the fields object and check if they exist and valid or valid == null.       return Object.keys(this.veeFields).every(field => {         return this.veeFields[field] && (this.veeFields[field].valid || (this.veeFields[field].valid == null));       });     }

closed in adf4709d for v3


Cannot rely on HTTP_HOST

https://bugsnag.com/errors/5217b6becf4cfd7373c945d8/events/newest
The above bug from my account shows
PHP Notice: Undefined index: HTTP_HOST
/var/lib/openshift/5217b6484382ecd56c001d7d/app-root/runtime/repo/vendor/bugsnag/bugsnag/src/Bugsnag/Request.php:70 • [main]

Hi, that is very old issue but still valid.
https://bugsnag.com/aikidesk-ltd/ad-www/errors/577ba99205b6c8c6cf49cce3
we are using php 7.0.x (latest) and we get logged exceptions from random IPs around the world (probably HTTP 1.0 bots)
http://php.net/manual/en/reserved.variables.server.php

Contents of the Host: header from the current request, if there is one.

We are using 2.x but as i see even 3.x use same HTTP_HOST without checking for availability.

Does https://github.com/bugsnag/bugsnag-php/pull/302 fix this for you please?


chore(deps): bump versions in package.json

Updates versions of everything (or nearly everything, at least). Uses a <21 version for @types/node to keep it in approximate sync with our nodejs version.

Note that we are getting a warning related to Vue3Snackbar in the dev console. I think that's an upstream issue.


Make date portion of the search optional

As a user trying to search for an email by keyword across my whole history, I do not want to even select any kind of option for the dates. I would like to just enter my keyword and search, but right now I'm forced to manually scroll back in time to select a date range from then until today.
Acceptance Criteria

By default, entering a keyword and selecting search will search across all dates.

tested on android

tested on iPhone

tested on iPad

Verified - Test PASS


Fix typo in separate word

https://github.com/Microsoft/TypeScript-Node-Starter/pull/144

This was merged with #144 - thanks @jarifibrahim


[K8s][Helm] Certmanager Software Update

This pull request implements the deployment of Certmanager in Kubernetes using a Helm chart. Thoroughly tested for Certmanager by checking the logs and pods running. Added essential file such as values.yaml. Updated Certmanager image version from v1.26.1 to v1.28.2

Can one of the admins verify this patch?


Add release notes for 2.0.13 release

@derekbekoe,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

latest/docs-ref-conceptual/release-notes-azure-cli.md
:white_check_mark:Succeeded
View (azure-cli-latest)

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

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified commit because branch heads/e82423c66c51eae75295b0493a07d291/cli-release-0811 has been deleted or has been force pushed: fatal: Could not parse object '00d1b3884adf0982d53efd13d8bd63db35e626c2'.

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

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

latest/docs-ref-conceptual/release-notes-azure-cli.md
:white_check_mark:Succeeded
View (azure-cli-latest)

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


Iuliuscompany  - Missing " Targetare .ro" button

ENVIRONMENT: production
URL: https://scrapers.peviitor.ro
Browser: Chrome
Device: Laptop
OS: Windows 10
STEPS TO REPRODUCE:

Open the URL in the browser
Search for " Iuliuscompany" Company
Click on the "Targetare.ro" button
Open page "Targetare.ro"

EXPECTED RESULTS:
The "Targetare.ro" button is functional and the page is opened.
ACTUAL RESULTS:
Missing "Targetare.ro" button.

Fixed!

Re-tested, The "Targetare.ro" button is functional and the page is opened.


Segregate database access with multiple proxys

Describe the task
For auth lambda use database user with limited permissions separate from database user for api lambda
Acceptance Criteria

[ ] Create new appropriately named database proxy account for auth lambda
[ ] Analyze required permissions for api lambda proxy account
[ ] reduce privileges for api lambda
[ ] generate sql scripts to create new auth lambda user
[ ] create new AWS Secret for auth lambda user
[ ] auth lambda connections use lower privileged db user
[ ] api lambda connections use higher privileged db user

Additional context

https://apps.nrs.gov.bc.ca/int/confluence/display/FSAST1/Improving+Security (#9 level 1)
Additional design work needed to clarify if the auth/api labmda split is sufficient, or if further segregation is warranted.

I've started with a PR to create a separate auth lambda db user with restricted access.
The second step (not started yet) is to reduce the permissions of the API db user.

Auth lambda work is done. Reducing access of API DB user is in progress, see PR https://github.com/bcgov/nr-forests-access-management/pull/745

For the short term solution:

Auth function: tests run with master db, since we want auth lambda user to be locked down as much as possible (and letting the tests run with auth lambda user requires opening up inserts on various tables)
API function: tests run with API db user, the expansion of permissions to have tests run is reasonable - just some extra deletes. The work to refactor the tests to avoid these extra delete permissions has been descoped and moved to new issue #751.


Bandarussr/services form component

Description
Created the services section of the form. Has a mobile and desktop views and can handle an unlimited number of services. Zod validation schema is set up and works for text fields.
Relevant issue(s)

#58

Questions/Notes

Zod validation is set up but does not appear for checkboxes and hidden text fields.
Hours component and subsequent validation will be added by #79

Type of change

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

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] I have assigned reviewers to this PR

as a note on this PR, the original implementation used the shadcn Checkbox component. We may want to utilize the shadcn Form wrapper at some point to better support shadcn components that utilize Radix components


Initial port of CLI to new abstractions

Initial (rough) port of agentos {init, train, test} command-line tools to the new abstractions.  Issuing this PR in case you all want to start writing code against these changes.
See design discussion here.
Demo
# Create new agent dir
mkdir andy_agent
cd andy_agent/

# Initialize your agent
agentos init . -n AndyAgent

# Train your agent in a loop for 5 iterations
agentos learn 5

# Run your agent
agentos run

Limitations
This is a very rough first stab, some limitations:

I assume you will be running these commands within the agent directory (and don't support specifying  custom agent.ini yet) train and run now support a -f flag to specify the agent.ini to use.
I skipped all but one two of the tests (😬).  They'll come back online as we port example agents and run_agent to the new  abstractions.
I added agentos test (instead of modifying agentos run)
General API instability

Next step

I'd like to port run_agent (and the dependent tests) to the new abstractions.  Thoughts?
Reinstate the skipped tests
Porting over agents to use the new abstractions
Making a plan for action_space and observation_space in Policy

Updated this PR to remove the Trainer abstraction.

Made some more progress on porting the core and CLI to the new abstractions.

Can you link to the design discussion thread in the first comment of this PR conversation?

Added a first cut at agentos install.  Demo has been updated in this PR description.

@andyk

Do we want to cut 0.0.7 before we merge this into master?

Just checking that I understand this proposal:

Update master so we're on version 0.0.7 (instead of 0.0.7-alpha)
Merge this PR
Call master 0.0.8-alpha (or whatever is after 0.0.7)

is that right?  If so, sounds good to me!

@andyk

Do we want to cut 0.0.7 before we merge this into master?

Just checking that I understand this proposal:
* Update master so we're on version 0.0.7 (instead of 0.0.7-alpha)

* Merge this PR

* Call master 0.0.8-alpha (or whatever is after 0.0.7)

is that right? If so, sounds good to me!

Yeah, this is what I was thinking with one more step before these that you listed being: merge in #93

Call master 0.0.8-alpha (or whatever is after 0.0.7)

I propose we update the version to 0.1.0-alpha because it will change core abstractions quite a bit

@andyk branch and versioning plan sounds good to me!

97014da adds the ability to install 2048 via the agentos CLI.  Demo updated.

@andyk branch and versioning plan sounds good to me!

Moving ahead with this plan in #102


Fix futhark build on Darwin

Motivation for this change
Futhark won't build on Darwin and there's duplication (obsolete non-hackage package).
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[ ] NixOS
[X] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[X] Fits CONTRIBUTING.md.

Can it compile anything on Darwin though? Just run through the first example on https://futhark-lang.org/examples.html
And what was the error on Darwin?

Works for me with the OpenCL backend. Keep in mind you need to pass arguments on stdin.

Odd, because the wrapping thing is not present at all on Darwin now, no idea how it can still work.

I don't know what you mean, can you elaborate?

The line in this PR makes it such that on Darwin it uses the unwrapped Futhark package. The wrapping logic under that line will only be applied on non-Darwin. And I added that logic down there to make compiling work, because it didn't work if it wasn't wrapped properly.

Have you tried it on Darwin? What's the error?

Um, I thought you were on Darwin, because I asked earlier whether it worked on Darwin and you replied that it does..

I'm on Darwin and it does work for me, I was just asking if it was different for you.
The wrapper isn't needed on Darwin. There's no ocl-icd and everything should be available through OpenCL.framework.

Oh I see, no I'm not on darwin.
@jacereda Do you have gcc or clang in your PATH though? Because that's another thing the wrapper does for you. Try compiling a Futhark program with export PATH="" beforehand

It's finding impure dependencies, it will run if you leave /usr/bin in the path.

Yeah but we don't want impure dependencies in Nix. If somebody doesn't have gcc/clang installed, the program should still run.


Improve Simple mode by showing VM Counts

fixes https://github.com/hobbyfarm/hobbyfarm/issues/340

This PR will display the VM count in the simple mode. Also when editing ScheduledEvents it is tried to calculate the number of users back so a single integer. if there is a single integer that divides all the VM Counts without a reminder the simple mode will be used, otherwise the AdvancedMode will be shown as before


Q: How to change the color for all lines in one go?

First of all, thanks for making this tool.
I wish to use flowchart.js on a site using a dark template. This means that black connector lines are hardly visible. I understand I can change the color for strokes between containers on a per connection basis as demonstrated in the third demo on the official website. But is there a way to just set a color for all connector lines at once?

just set the appropriate color in the options: 'line-color': 'white'
example: https://github.com/adrai/flowchart.js/blob/master/example/index.html#L40


Robert Longson: Watch healthcarebloger.com

Robert Longson requests the watch of the watch_keyword healthcarebloger\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

healthcarebloger\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Cody Gray in Charcoal HQ


Channel-Client should not expect an immediate response for API calls

Currently Channel-Client expects a response immediately for any API call it makes. However the xstate-wallet sends a response after a user has confirmed it in the UI. This currently causes the channel-client to time out.

What are our options for handling this?

What are our options for handling this?

I think we need to remove the timeout logic from channel-client. That does mean that you may receive a promise from the channel-client that doesn't resolve for a while. (which means it may be hard to detect if the wallet isn't responding or is just waiting on the user)
The other option is changing the channel-client interface a bit so that it's similar to how the API works. You call createChannel which returns immediately and sometime later a ChannelCreated event is fired by the channel-client which the app listens for.


[Feature Request]: Infinite Liked by a user | Addition of Persistent Storage

Is there an existing issue for this?

[X] I have searched the existing issues

Feature Description
Infinite Liked by a user | User Data (Like/Dislike) should also store in Local Storage to Prevent this.
In future this will store in DB.
Use Case
Single user like only one time.
Benefits
No response
Add ScreenShots
https://github.com/user-attachments/assets/5d7b0c89-5f42-4ed8-bf45-5067c5a27ae0
Priority
High
Record

[X] I have read the Contributing Guidelines
[X] I'm a GSSOC-EXT contributor
[X] I'm a HACKTOBERFEST contributor
[X] I have starred the repository

@jeevan10017 assign this to me


support repeatable directive

At the moment a repeatable directive is executed once: the first directive only.
The 2nd one instead is not executed or processed.
const Fastify = require('fastify')
const mercurius = require('mercurius')
const mercuriusAuth = require('mercurius-auth')

const schema = `
  directive @hasPermission (grant: String!) repeatable on OBJECT | FIELD_DEFINITION

  type Message {
    title: String!
    notes: String @hasPermission(grant: "lv1") @hasPermission(grant: "lv2")
  }

  type Query {
    publicMessages(org: String): [Message!]
  }
`

const resolvers = {
  Query: {
    publicMessages: async () => {
      return [
        { title: 'one', message: 'acme one', notes: 'acme-one' },
        { title: 'two', message: 'acme two', notes: 'acme-two' }
      ]
    }
  }
}

const app = Fastify()
app.register(mercurius, {
  graphiql: true,
  schema,
  resolvers
})

app.register(mercuriusAuth, {
  authContext: hasPermissionContext,
  applyPolicy: hasPermissionPolicy,
  namespace: 'authorization-filtering',
  authDirective: 'hasPermission'
})

app.listen(3000)

function hasPermissionContext (context) {
  return { permission: context.reply.request.headers['x-permission'].split(',') }
}
async function hasPermissionPolicy (authDirectiveAST, parent, args, context, info) {
  const needed = authDirectiveAST.arguments.find(arg => arg.name.value === 'grant').value.value
  const hasGrant = context.auth.permission.includes(needed)
  if (!hasGrant) {
    throw new Error(`Needed ${needed} grant`)
  }
  return true
}

I think the issue is on this line:
https://github.com/mercurius-js/auth/blob/16db4b5324bbadef85b36e911bd31dfec03511da/lib/auth.js#L29
find should be filter instead.
Changing the output to an array impacts to the getPolicy() public API. I'm not sure about the impacts

Good find and nice explanation - we should definitely support this (as you mentioned, I think we may need to add this support to the external policy API - so we'll need to be careful to avoid breaking existing functionality) - would you like to work on a draft PR so we can discuss the approach there?


Main bar height should not be a magic number

This will require revisiting the gulpfile, since there's variables sprinkled throughout the js which depend on the menu bar height. 724db0af8b429753389481df10e529b123e179b0 mostly addressed scss files, since sharing variables between scss and js within gulp just feels hacky.


[BUG] No replica is created after increased replica count

Describe the bug
Test case test_extra_replica_cleanup fails on master-head because it expects a unschedulable replica will be created after updated the volume replica count from 3 to 4:
https://ci.longhorn.io/job/public/job/master/job/sles/job/amd64/job/longhorn-tests-sles-amd64/961/testReport/tests/test_ha/test_extra_replica_cleanup/
client = <longhorn.Client object at 0x7f7d0d77b150>
volume_name = 'longhorn-testvol-ojrmht', settings_reset = None

    def test_extra_replica_cleanup(client, volume_name, settings_reset): # NOQA
        """
        Test extra failed to scheduled replica cleanup
        when no eviction requested

        1. Make sure 'Replica Node Level Soft Anti-Affinity' is disabled.
        2. Create a volume with 3 replicas.
        3. Attach the volume to a node and write some data to it and
        save the checksum.
        4. Increase the volume replica number to 4.
        5. Volume should show failed to schedule and an extra stop replica.
        6. Decrease the volume replica number to 3.
        7. Volume should show healthy and the extra failed to scheduled replica
        should be removed.
        8.
Expected behavior

Support bundle for troubleshooting

Environment

Longhorn version: master-head
Impacted volume (PV):
Installation method (e.g. Rancher Catalog App/Helm/Kubectl): helm
Kubernetes distro (e.g. RKE/K3s/EKS/OpenShift) and version: v1.30.0+k3s1

Number of control plane nodes in the cluster:
Number of worker nodes in the cluster:

Node config

OS type and version: sles 15-sp5
Kernel version:
CPU per node:
Memory per node:
Disk type (e.g. SSD/NVMe/HDD):
Network bandwidth between the nodes (Gbps):

Underlying Infrastructure (e.g. on AWS/GCE, EKS/GKE, VMWare/KVM, Baremetal):
Number of Longhorn volumes in the cluster:

Additional context

This behavior is expected following the changes in https://github.com/longhorn/longhorn-manager/pull/2918. We implemented a precheck before creating a new Replica CR, so no new Replica will be created is no suitable node and disk are available.

Verified pass on longhorn master(longhorn-test d3a059) by run test_replica_should_not_be_created_when_no_suitable_node_found 5 times all passed.


Remove legacy webfont architecture from paying-for-college disclosures

The Paying for College disclosures was applying webfonts via the font CSS attribute. However, it needed to be font-family to actually apply:

So all the font rules are not applying, so we can just remove them as the app will be unchanged to how it is now.
Removals

Removes invalid font CSS rules from paying for college disclosures app.
Removes legacy @webfont- variables and licensed-fonts font-face rules.

How to test this PR

./frontend.sh and contact Bill H for test URL.

I pushed up https://github.com/cfpb/consumerfinance.gov/pull/6874/commits/1566b9c4819f27c04fc36608b9e6c907b1d4b87a, which migrates the Avenir demi to regular avenir with a "bolder" setting. This is slightly less bold than the current implementation. I think it's worth it, maintenance-wise.
Before:

After:

These changes are more pronounced on /retirement/, which sees some things getting bolder (also note the dollar amount numbers were not the same style as those in the chart before):
Before:

After:


[Deployment] Ignite K8s yaml, docker, and xml files

This PR adds new configuration files for Ignite

K8s yaml file
xml file customized for Alcor
Docker file

@Gzure This is current version of Ignite deployment files.

@kevin-zhonghao
Ignite docker build file
`# Dockerfile for Customized Ignite Image
FROM apacheignite/ignite:2.8.1
MAINTAINER Liguang Xie<EMAIL_ADDRESS>Generate container image and run container
COPY ./target/common-0.1.0-SNAPSHOT.jar /opt/ignite/apache-ignite/libs/common-0.1.0-SNAPSHOT.jar
CMD $IGNITE_HOME/run.sh
Container port exposure
EXPOSE 11211 47100 47500 49112 10800 8080
Ignite deployment yamlapiVersion: apps/v1
kind: Deployment
metadata:
name: ignite-cluster
spec:
selector:
matchLabels:
app: ignite
replicas: 3
template:
metadata:
labels:
app: ignite
spec:
#hostNetwork: true
serviceAccountName: ignite
containers:
- name: ignite-node
image: ignite:v1.2
#image: apacheignite/ignite:2.8.1
imagePullPolicy: IfNotPresent
resources:
requests:
cpu: "16"
env:
- name: OPTION_LIBS
value: ignite-kubernetes,ignite-rest-http
- name: CONFIG_URI
value: /opt/ignite/config/ignite-config.xml
- name: IGNITE_QUIET
value: "false"
- name: JVM_OPTS
value: "-Djava.net.preferIPv4Stack=true"
ports:
- containerPort: 11211 # REST port number.
- containerPort: 47100 # communication SPI port number.
- containerPort: 47500 # discovery SPI port number.
- containerPort: 49112 # JMX port number.
- containerPort: 10800 # SQL port number.
- containerPort: 10900 # Thin clients port number.
volumeMounts:
- name: ignite-config-volume
mountPath: /opt/ignite/config
volumes:
- name: ignite-config-volume
configMap:
name: ignite-config`

@kevin-zhonghao Could you please arrange to check in the latest yaml files to the master? Either update this PR or start a new PR.