Upgrade systemd from 255 to 256

Upgrade systemd from 255 to 256
Fixes: https://github.com/flatcar/Flatcar/issues/1501
Testing done
[Describe the testing you have done before submitting this PR. Please include both the commands you issued as well as the output you got.]

[ ] Changelog entries added in the respective changelog/ directory (user-facing change, bug fix, security fix, update)
[ ] Inspected CI output for image differences: /boot and /usr size, packages, list files for any missing binaries, kernel modules, config files, kernel modules, etc.

The github actions fail with vm being emergency shelled at boot with the error: systemd: system is tainted: unmerged bin, needs investigation.

From https://lists.freedesktop.org/archives/systemd-devel/2024-June/050407.html:
        Service Management:

        * New system manager setting ProtectSystem= has been added. It is
          analogous to the unit setting, but applies to the whole system. It is
          enabled by default in the initrd.

          Note that this means that code executed in the initrd cannot naively
          expect to be able to write to /usr/ during boot. This affects
          dracut <= 101, which wrote "hooks" to /lib/dracut/hooks/. See
          https://github.com/dracut-ng/dracut-ng/commit/a45048b80c27ee5a45a380.

https://github.com/dracut-ng/dracut-ng/commit/a45048b80c27ee5a45a380 -> this commit shows how to fix dracut 100, not applicable, as dracut used by Flatcar is an older version 0.53.
But ignition-setup.service fails to run at this line, as /usr is mount as ro: https://github.com/flatcar/bootengine/blob/flatcar-master/dracut/30ignition/ignition-setup.sh#L15.

One option, is, obviously, to disable the default ProtectSystem, as the initrd Flatcar workflow is reliant on writing to rootfs, similar to this, in bootengine, using a dracut module definition, similar to: https://github.com/flatcar/bootengine/blob/flatcar-master/dracut/99switch-root/nocgroup.conf
Another would be to fix all the bootengine /usr writes and maybe move those to /etc or /var.

Full error for the initrd break point:
journalctl -xeu ignition-setup.service

Sep 25 08:17:15 localhost systemd[1]: Starting ignition-setup.service - Ignition (setup)...
Sep 25 08:17:15 localhost ignition-setup[891]: cp: cannot create regular file '/bin/is-live-image': Read-only file system
Sep 25 08:17:15 localhost systemd[1]: ignition-setup.service: Main process exited, code=exited, status=1/FAILURE
Sep 25 08:17:15 localhost systemd[1]: ignition-setup.service: Failed with result 'exit-code'.
Sep 25 08:17:15 localhost systemd[1]: Failed to start ignition-setup.service - Ignition (setup).
Sep 25 08:17:15 localhost systemd[1]: ignition-setup.service: Triggering OnFailure= dependencies.

To overcome the current limitation imposed by systemd 256 regarding the ignition-setup[891]: cp: cannot create regular file '/bin/is-live-image': Read-only file system, there are two options I can think of:

use /mnt/oem or even /tmp as a temporary place to store the is-live-image but this needs a $PATH change so that it can be found by Ignition -> https://github.com/search?q=repo%3Acoreos%2Fignition is-live-image&type=code
Temporarily remount the /usr as mount -o remount,rw /usr, do the required change and then mount -o remount,ro /usr

I am not convinced these two ideas are the best, maybe there is another option?
Thanks.

With the is-live-image issue fixed, systemd 256 expects dracut 059 -> see https://github.com/systemd/systemd/commit/1c585a4ccda3258088d7bc27b27a314e7ed8be80
Until dracut is updated, we need to revert this commit manually in systemd: https://github.com/systemd/systemd/commit/1c585a4ccda3258088d7bc27b27a314e7ed8be80

Updating Dracut has proven tricky, mainly due to size issues, so I wouldn't wait for that.

Updating Dracut has proven tricky, mainly due to size issues, so I wouldn't wait for that.

yeap, will add the patch to systemd ebuild.

AMD64 Flatcar running with systemd 256 and linux 6.10:
root@localhost ~ # cat /etc/os-release
NAME="Flatcar Container Linux by Kinvolk"
ID=flatcar
ID_LIKE=coreos
VERSION=4102.0.0+nightly-20240923-2100-26-g730775213c
VERSION_ID=4102.0.0
BUILD_ID=nightly-20240923-2100-26-g730775213c
SYSEXT_LEVEL=1.0
PRETTY_NAME="Flatcar Container Linux by Kinvolk 4102.0.0+nightly-20240923-2100-26-g730775213c (Oklo)"
ANSI_COLOR="38;5;75"
HOME_URL="https://flatcar.org/"
BUG_REPORT_URL="https://issues.flatcar.org"
FLATCAR_BOARD="amd64-usr"
CPE_NAME="cpe:2.3:o:flatcar-linux:flatcar_linux:4102.0.0+nightly-20240923-2100-26-g730775213c:*:*:*:*:*:*:*"
root@localhost ~ # uname -a
Linux localhost 6.10.9-flatcar #1 SMP PREEMPT_DYNAMIC Thu Sep 26 06:21:38 -00 2024 x86_64 Intel(R) Xeon(R) Gold 6134 CPU @ 3.20GHz GenuineIntel GNU/Linux
root@localhost ~ # systemctl --version
systemd 256 (256.2)
+PAM +AUDIT +SELINUX -APPARMOR +IMA +SMACK +SECCOMP +GCRYPT -GNUTLS +OPENSSL -ACL +BLKID +CURL +ELFUTILS -FIDO2 +IDN2 -IDN +IPTC +KMOD +LIBCRYPTSETUP +LIBCRYPTSETUP_PLUGINS +LIBFDISK +PCRE2 -PWQUALITY -P11KIT -QRENCODE +TPM2 +BZIP2 +LZ4 +XZ +ZLIB +ZSTD -BPF_FRAMEWORK -XKBCOMMON +UTMP -SYSVINIT +LIBARCHIVE

The github actions failed because of the Mantle tests using cgroupv1. See https://github.com/systemd/systemd/releases/tag/v256-rc3 -> systemd will refuse to boot in normal circumstances.
Support for cgroup v1 ('legacy' and 'hybrid' hierarchies) is now
      considered obsolete and systemd by default will refuse to boot under
      it. To forcibly reenable cgroup v1 support,
      SYSTEMD_CGROUP_ENABLE_LEGACY_FORCE=1 must be set on kernel command
      line. The meson option 'default-hierarchy=' is also deprecated, i.e.
      only cgroup v2 ('unified' hierarchy) can be selected as build-time
      default.

We should add code to our update postinstall hook to detect if the user is still on cgroups v1 and abort the update.

From: Adrian Vladu @.>
Sent: Thursday, September 26, 2024 3:39:36 AM
To: flatcar/scripts @.>
Cc: Jeremi Piotrowski @.>; Review requested @.>
Subject: Re: [flatcar/scripts] Upgrade systemd from 255 to 256 (PR #2145)
The github actions failed because of the Mantle tests using cgroupv1. See https://github.com/systemd/systemd/releases/tag/v256-rc3 -> systemd will refuse to boot in normal circumstances.
Support for cgroup v1 ('legacy' and 'hybrid' hierarchies) is now
considered obsolete and systemd by default will refuse to boot under
it. To forcibly reenable cgroup v1 support,
SYSTEMD_CGROUP_ENABLE_LEGACY_FORCE=1 must be set on kernel command
line. The meson option 'default-hierarchy=' is also deprecated, i.e.
only cgroup v2 ('unified' hierarchy) can be selected as build-time
default.
—
Reply to this email directly, view it on GitHubhttps://github.com/flatcar/scripts/pull/2145#issuecomment-2376583368, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABXINVQUZN6IBMQMAL3GTWLZYPP6RAVCNFSM6AAAAABLKHBRBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZWGU4DGMZWHA.
You are receiving this because your review was requested.Message ID: @.***>

Or is it worth still letting users stay with cgroups v1 if they set this flag? we would still want to validate before commiting the update.

From: Jeremi Piotrowski @.>
Sent: Thursday, September 26, 2024 8:15:27 PM
To: flatcar/scripts @.>; flatcar/scripts @.>
Cc: Review requested @.>
Subject: Re: [flatcar/scripts] Upgrade systemd from 255 to 256 (PR #2145)
We should add code to our update postinstall hook to detect if the user is still on cgroups v1 and abort the update.

From: Adrian Vladu @.>
Sent: Thursday, September 26, 2024 3:39:36 AM
To: flatcar/scripts @.>
Cc: Jeremi Piotrowski @.>; Review requested @.>
Subject: Re: [flatcar/scripts] Upgrade systemd from 255 to 256 (PR #2145)
The github actions failed because of the Mantle tests using cgroupv1. See https://github.com/systemd/systemd/releases/tag/v256-rc3 -> systemd will refuse to boot in normal circumstances.
Support for cgroup v1 ('legacy' and 'hybrid' hierarchies) is now
considered obsolete and systemd by default will refuse to boot under
it. To forcibly reenable cgroup v1 support,
SYSTEMD_CGROUP_ENABLE_LEGACY_FORCE=1 must be set on kernel command
line. The meson option 'default-hierarchy=' is also deprecated, i.e.
only cgroup v2 ('unified' hierarchy) can be selected as build-time
default.
—
Reply to this email directly, view it on GitHubhttps://github.com/flatcar/scripts/pull/2145#issuecomment-2376583368, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABXINVQUZN6IBMQMAL3GTWLZYPP6RAVCNFSM6AAAAABLKHBRBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZWGU4DGMZWHA.
You are receiving this because your review was requested.Message ID: @.***>

Or is it worth still letting users stay with cgroups v1 if they set this flag? we would still want to validate before commiting the update.
…
________________________________ From: Jeremi Piotrowski @.> Sent: Thursday, September 26, 2024 8:15:27 PM To: flatcar/scripts @.>; flatcar/scripts @.> Cc: Review requested @.> Subject: Re: [flatcar/scripts] Upgrade systemd from 255 to 256 (PR #2145) We should add code to our update postinstall hook to detect if the user is still on cgroups v1 and abort the update.
________________________________ From: Adrian Vladu @.> Sent: Thursday, September 26, 2024 3:39:36 AM To: flatcar/scripts @.> Cc: Jeremi Piotrowski @.>; Review requested @.> Subject: Re: [flatcar/scripts] Upgrade systemd from 255 to 256 (PR #2145) The github actions failed because of the Mantle tests using cgroupv1. See https://github.com/systemd/systemd/releases/tag/v256-rc3 -> systemd will refuse to boot in normal circumstances. Support for cgroup v1 ('legacy' and 'hybrid' hierarchies) is now considered obsolete and systemd by default will refuse to boot under it. To forcibly reenable cgroup v1 support, SYSTEMD_CGROUP_ENABLE_LEGACY_FORCE=1 must be set on kernel command line. The meson option 'default-hierarchy=' is also deprecated, i.e. only cgroup v2 ('unified' hierarchy) can be selected as build-time default. — Reply to this email directly, view it on GitHub<#2145 (comment)>, or unsubscribehttps://github.com/notifications/unsubscribe-auth/ABXINVQUZN6IBMQMAL3GTWLZYPP6RAVCNFSM6AAAAABLKHBRBSVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDGNZWGU4DGMZWHA. You are receiving this because your review was requested.Message ID: @.***>

Hello @jepio, indeed, we have just a few paths forward:

follow systemd approach no questions asked related to the cgroupv1 and block the Flatcar upgrade in the postinstall hook.
Document the transition and disseminate the information on all possible channels about it.
Document the usage of SYSTEMD_CGROUP_ENABLE_LEGACY_FORCE=1 with ignition / manual update for the new/old instances.
set SYSTEMD_CGROUP_ENABLE_LEGACY_FORCE=1 on all images (not the best), this flat might be also removed in subsequent versions
patch systemd to remove the check (even less)
block the systemd upgrade until another option appears. Meanwhile, announce this future upgrade path and wait for more feedback from the community.

Thanks.

we have just a few paths forward:
1. follow systemd approach no questions asked related to the cgroupv1 and block the Flatcar upgrade in the postinstall hook.
   Document the transition and disseminate the information on all possible channels about it.
   Document the usage of SYSTEMD_CGROUP_ENABLE_LEGACY_FORCE=1 with ignition / manual update for the new/old instances.

2. set SYSTEMD_CGROUP_ENABLE_LEGACY_FORCE=1 on all images (not the best), this flat might be also removed in subsequent versions

3. patch systemd to remove the check (even less)

4. block the systemd upgrade until another option appears. Meanwhile, announce this future upgrade path and wait for more feedback from the community.

I am for 1, deprecate cgroup v1 and document as much as possible.
Other options look like nothing more than delaying issues.
Even if we go for 1, users still have workaround to revert the behavior.

follow systemd approach no questions asked related to the cgroupv1 and block the Flatcar upgrade in the postinstall hook.

I agree with Dongsu to take the 1 approach, and add to the notes section in the Release notes section, and into documentation.

During the office hours there was an idea of adding the kernel parameter to the nodes that were still using cgroupv1. This probably would be a smooth way of updating Flatcar to a version with systemd 256.
Of course, with cgroupv1 being on chopping block, we would need to define how long we are going to support cgroupv1. My proposal would be to spin up new LTS version (which is due anyway) and announce that support for cgroupv1 in Flatcar will bound to the lifetime of the new LTS. For other channels we could say support will be until end of this year or something. For people still needing cgroupv1 after that, we could point them to use LTS, so they'll have a bit more time to move off to cgroupv2 (like until mid-2026, I think).

Thank you @krnowak . Summing things up:

LTS 2024 will remain on 255 and continue to provide cgroups-v1.
All releases with 265 included will not support v1 anymore.

[_] Add a check to update_engine's post-install script and refuse to update (fail the update) on instances that use cgroups-v1. Bump the update engine ebuild to include the new UE version and add it to this systemd PR.
[_] Fail deployments that try to enable cgroups-v1 via the command line (as per docs)
[_] Add tests for the two bullet points above

Mantle tests cannot be fixed via ignition setting of the Linux kernel cmdline param SYSTEMD_CGROUP_ENABLE_LEGACY_FORCE=1, as ignition starts after systemd (of course). So, the cgroup v1 mantle tests can only be done by changing the image before booting (hard) or using a specialized image (no go).
At this moment, I recomend to just skip those cgroup v1 mantle tests on version higher than this one.

CI http://localhost:8080/job/container/job/sdk/1883/


Update ideas-list.md

making the list a table

Ping me once this is merged so I can add my ideas without creating a conflict.

@7yl4r merged.


Enable/Disable Signups

There are two things I would like to see in this.

Being able to manually enable/disable signups
Automatically disable logins after a certain amount of signups.

Not sure if the latter is possible, but knowing you, you'll figure it out

This is an old issue, but if you're looking to manually enable/disable signups, you can simply set the environment variable ITC_CLOSED_TEXT to whatever message you want to give the user when they hit your signup page.
Automatically disabling doesn't appear to be available, though.

:+1:


Webcam image is tinted blue in safari

When I capture an image using the Flash fallback, the image appears tinted blue. I'm drawing the data URI of the flash image to a canvas, but not performing any pixel color manipulation. This seems like a bug with either webcamjs, or with Flash itself. When I open the page in a browser that supports getUserMedia with Safari still open to the Flash version, both versions appear correctly. Is anyone else experiencing similar issues?

I'm also experiencing this issue


onlyCalendar prop is not working

Environment

Tech
Version

material-ui-pickers
^1.0.0-rc.17

material-ui
^3.0.1

React
16.4.2

Browser
Chrome

Peer library
moment ^2.22.2

Steps to reproduce

Just add the onlyCalendar prop

Expected behavior
To only show the calendar
Actual behavior
I see the toolbar header in the datepicker and the console log throws this warning:
index.js:2178 Warning: Unknown event handler property onlyCalendar. It will be ignored.

It is working only for popover mode

Why not using the Calendar directly? ;D
import Calendar from 'material-ui-pickers/DatePicker/components/Calendar'
<Calendar
                        date={new Date()}
                        disablePast={true}
                        disableFuture={maybe}
                        onChange={(date) => console.log(date)}
                        leftArrowIcon={<KeyboardArrowLeft/>}
                        rightArrowIcon={<KeyboardArrowRight/>}
                      />
                    </div>

@valorize It looks like it's not possible to import the Calendar directly.
Probably because of using the default import?
WithUtils.js:23 Uncaught Error: Can not find utils in context. You either
  a) forgot to wrap your component tree in MuiPickersUtilsProvider; or
  b) mixed named and direct file imports.
  Recommendation: use named imports from the module index.
    at checkUtils (WithUtils.js:23)

If I change it to:
- import Calendar from 'material-ui-pickers/DatePicker/components/Calendar';
+ import { Calendar } from 'material-ui-pickers/DatePicker/components';

I get this error instead:
Module not found: Can't resolve 'material-ui-pickers/DatePicker/components' in '/Users/daniel/git/dough/dough-react/src/components/ChipSetReminder'

Any idea?

Did you wrap your calendar into?:
import DateFnsUtils from '@date-io/date-fns';
import { MuiPickersUtilsProvider } from 'material-ui-pickers';

function App() {
  return (
    <MuiPickersUtilsProvider utils={DateFnsUtils}>
      <Calendar ... />
    </MuiPickersUtilsProvider>
  );
}

@danieljuhl Actually it's required to use only path imports or core import. Here you mixed them. I know that it is tricky to change your imports for using static example.
I am considering to add exports in the core module the most usable internal controls like calendar clock and so on. @TrySound What do you think? From where I stand it should not affect treeshaking of esmodules

@dmtrKovalenko Yeah, I also wanted to propose this for my range picker.


make sure required options are not empty

since these options are required, I think it is necessary to make sure they are not empty.

Thanks.  From PHP manual:
The following things are considered to be empty:

"" (an empty string)
0 (0 as an integer)
0.0 (0 as a float)
"0" (0 as a string)
NULL
FALSE
array() (an empty array)
$var; (a variable declared, but without a value)

Some options may use above values, so we cannot restrict options not empty.
Right?


chore: Use verified publisher image hashicorp/vault

Fixes https://github.com/bank-vaults/bank-vaults/issues/2040
Hashicorp has deprecated Duplicative Docker Images (see https://developer.hashicorp.com/vault/docs/v1.13.x/deprecation).
New versions of vault are only published to https://hub.docker.com/hashicorp/vault.
https://hub.docker.com/_/vault only contains old versions up to 1.13.3.

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


Core dump when predicting on 3'UTR sequences

Thank you for providing GraphProt!
I am trying to predict TIA1 binding to a larger set of 3'UTRs and running into Core dumps with no output generated. Any help/advice on identifying the offending sequence would be much appreciated!
GraphProt.pl \
  -action=predict \
  -fasta=../split0.3utr.fa
  -onlyseq
  -model=../../GraphProt_models_CLIP/sequence/ICLIP_TIA1.slop15.train.model
  -keep-tmp
  -prefix=split0

produces an empty split0.predicions file (and somehow seems to clear the tmp directory with the core dump?. At least I can't find it.) I attach the sequences used:
split0.3utr.fa.zip
The model file is linked from the main page so I assume you have it?
Using graphprot-1.1.7-h3445559_4 from bioconda on ubuntu 18.04 LTS. Thank you for your time. Best regards,
-Marvin
Here's the output:
Using parameters:
R: 1
D: 4
bitsize: 14
epochs: 10
lambda: 0.001

using empty set of unknowns!
touch /scratch2/GraphProt/k562/TIA1/GraphProt_tmp-d7RIf4.test.unknowns.fa
( perl /home/mjens/miniconda2/libexec/graphprot//fastapl -p -1 -e '$head .= " 1";' < /scratch2/GraphProt/k562/TIA1/GraphProt_tmp-d7RIf4.test.positives.fa; \
  perl /home/mjens/miniconda2/libexec/graphprot//fastapl -p -1 -e '$head .= " -1";' < /scratch2/GraphProt/k562/TIA1/GraphProt_tmp-d7RIf4.test.negatives.fa; \
  perl /home/mjens/miniconda2/libexec/graphprot//fastapl -p -1 -e '$head .= " 0";' < /scratch2/GraphProt/k562/TIA1/GraphProt_tmp-d7RIf4.test.unknowns.fa ) > /scratch2/GraphProt/k562/TIA1/GraphProt_tmp-d7RIf4.test.fa
cp /scratch2/GraphProt/k562/TIA1/GraphProt_tmp-d7RIf4.param /scratch2/GraphProt/k562/TIA1/GraphProt_tmp-d7RIf4.test.param
perl /home/mjens/miniconda2/libexec/graphprot//fasta2shrep_gspan.pl --vp --seq-graph-t -nostr -stdout -fasta /scratch2/GraphProt/k562/TIA1/GraphProt_tmp-d7RIf4.test.fa | \
gzip > /scratch2/GraphProt/k562/TIA1/GraphProt_tmp-d7RIf4.test.gspan.gz; exit ${PIPESTATUS[0]}
perl /home/mjens/miniconda2/libexec/graphprot//fastapl -e '@ry = split(/\s/,$head); print $ry[-1], "\n"' < /scratch2/GraphProt/k562/TIA1/GraphProt_tmp-d7RIf4.test.fa > /scratch2/GraphProt/k562/TIA1/GraphProt_tmp-d7RIf4.test.affy
bash /home/mjens/miniconda2/libexec/graphprot//check_sync_gspan_class.sh /scratch2/GraphProt/k562/TIA1/GraphProt_tmp-d7RIf4.test.gspan.gz /scratch2/GraphProt/k562/TIA1/GraphProt_tmp-d7RIf4.test.affy && \
OMP_NUM_THREADS=1 /home/mjens/miniconda2/libexec/graphprot//EDeN -a FEATURE -i /scratch2/GraphProt/k562/TIA1/GraphProt_tmp-d7RIf4.test.gspan.gz -r 1 -d 4 -b 14 -g DIRECTED
OK: gspan and class in sync
----------------------------------------------------------------
EDeN (Explicit Decomposition with Neighborhoods) Vers. 0.4.2 (15 June 2013)
Author: Fabrizio Costa<EMAIL_ADDRESS>----------------------------------------------------------------
Processing I/O file: /scratch2/GraphProt/k562/TIA1/GraphProt_tmp-d7RIf4.test.gspan.gz
.......terminate called without an active exception
make: *** [/home/mjens/miniconda2/libexec/graphprot//Makefile:266: /scratch2/GraphProt/k562/TIA1/GraphProt_tmp-d7RIf4.test.feature] Aborted (core dumped)
paste: /scratch2/GraphProt/k562/TIA1/GraphProt_tmp-d7RIf4.test.predictions_sgd: No such file or directory
GraphProt predictions written to file split0.predictions

I bisected the fasta file and after 11 steps narrowed it down to a single sequence that triggers the error. I had hoped there would be something obvious like N's or a very long sequence or short. But that's not the case. Looks okay to me head-scratch
> ENST00000568252.1_1.UTR3
tgagtgatgtttcaggctggaagcggtgagccactgacagggatcagagaattccccacagaatttggcagtcacatgcatggatttagaaagacaaagttggaaatgaattgttgcagctaatttctccctcaagacattgtctacattctgaagctagatctggtggcagaggagactaaggagctcagtatttccacatagtaacaacaaacattctaaaaagaaacaagagaacaatcttacttacaacagcttcaaaaaataaaatatttagaaataagtttaaccaagaaggtgaaagacctgtacactgaaaaatgttaataacaaaaattatagaagacacaaataaattggaagatattctgtgttcatagattggaagaataatgttgctaaaatgtccatactaccccaaatgacttatagactcaaagcaatttctaacaaaattgtaatgtaattattcatagtaacagaaaaaaatataaaattaatgtggaaccacaacaaactctgaatagccaaaggaatcatgagtaagaagatgaaagctggaggcaccaaccacatgcatgatttaaaactacactacaaagcaatagtaattaaaacagtgtgatactggcatgaaaatagactcgttggctgggtgcagtggctcacgcctgtaatcccagcacgttgggagtctgaggcaggaagatcatgaggttaggagtttgagaccagcctgaccaacatggtgaaagcccgtctctacaaaaaatacaaaaattagccaggcatggtggcacatgccggtaatcccagctactcaggcaactgaggcaggagaattgcttgaacccgggaggcagaggctgcagtgagcctagattacaccactgcactcccgcctgggtgacagagcaagactctatctcaa

LOL! If I change all letters to upper-case it no longer crashes. Alright, I'm glad because that's easy to fix.
That being said, it would be great if this requirement were prominently placed in the help text or the README.md. (or just switch up all seqs to upper-case, internally?)

Glad you found a solution! There used to be a check for all lowercase sequences, I have to look into that.

@marvin-jens  @dmaticzka weird thing is I ran your previous fasta file that you have attached (as it is ) and it worked for me however when I run my fasta file with and without changing all the sequences to upper case I get the same error no matter what. Would any body be able to help me with this?
Thanks


Add contribution guidelines

https://github.com/sindresorhus/awesome/blob/master/awesome.md#include-contribution-guidelines

Please create a pull request.

Added contribution guidelines.


[match] Add note about the adhoc type during "match nuke"

This references #4186 and adds a bit more explanatory detail around using the adhoc type during match nuke.

Great addition, thanks 👍


PNG decoder will not read trailing text chunks

The state diagram doesn't seem to allow for this situation, and key-value-pairs.png.make-artificial.txt doesn't test it.
I've previously scanned all non-thumbnail PNGs that I keep around, and 845 out of 10748 have trailing text chunks (none of them have other kind of trailing chunks). The thumbnail specification I'm implementing doesn't say anything about metadata placement, and although Qt and gdk-pixbuf always write them at the beginning of a file, I should support both options.
Also, the WEBP specification, which is on the roadmap, says EXIF and XMP metadata should both be placed at the end of a file.
What API should be used to retrieve it?

What API should be used to retrieve it?

In the C API, wuffs_png__decoder__decode_image_config or wuffs_png__decoder__decode_frame_config will report metadata, as before. The difference is that you will now have to do so in a loop (instead of calling wuffs_png__decoder__decode_frame_config just once) if you want trailing metadata. The test/c/std/png.c change in google/wuffs@c5e41f0 has an example.
In the C++ API (which only decodes still images, or the first frame of animated images), wuffs_aux::DecodeImageCallbacks::HandleMetadata should now call you back for both leading and trailing metadata, not just leading metadata, provided that you've opted into e.g. wuffs_aux::DecodeImageArgFlags::REPORT_METADATA_KVP for textual metadata (key-value pairs).

Thank you, I'll try to integrate this. Another beta would be nice to see soon.

I have just tagged v0.3.0-beta.15.

In case it wasn't obvious, you should be able to build and run the new script/print-image-metadata.cc program, pointing it at your PNG files, and it should pick up (leading and trailing) text chunks (marked as KVPK and KVPV for Key Value Pair {Key,Value}).
$ g++ script/print-image-metadata.cc
$ ./a.out test/data/hibiscus.primitive.png
test/data/hibiscus.primitive.png
  PNG
  KVPK
    53 6F 66 74 77 61 72 65 -- -- -- -- -- -- -- --    Software--------
  KVPV
    77 77 77 2E 69 6E 6B 73 63 61 70 65 2E 6F 72 67    www.inkscape.org

Alright, my image viewer has finally stopped using Wuffs together with spng. *Tired "Yay!"*

my image viewer has finally stopped using Wuffs together with spng.

I assume that you don't mean "(stopped using Wuffs) and (stopped using spng)", but that you mean "stopped using (Wuffs together with spng), and now uses Wuffs only".
:-)


Favor installed packages when breaking grammar score ties

If two grammars are both registered for the same file type, use the one from the non-bundled package.
This allows bundled grammars to be easily overridden by installed packages.
This takes away the stress from adding/removing more file types to core grammars in fear that they will break installed packages.
Basically installed packages will always win.
Refs https://github.com/atom/language-python/pull/61
Refs https://github.com/atom/language-php/pull/50
Refs https://github.com/atom/language-xml/issues/23
/cc @atom/feedback
/cc @lee-dohm @thomasjo

Awesome! :sparkling_heart:

Fantastic :grinning:

Looks good to me :+1:

Looks good.


insertdData into db

Is it possible to insert data into a influxdb with the InfluxDBStudio?

HI
This project contains write interface.But you need to write a piece of code to call this interface.

@Myth2018 hi，how to call this interface?


Policy: Document supported release tooling

NOTE: There needs to be further discussion and agreement on this before we decide.
Narrowing down our supported release tooling will greatly simplify our release processes. ie: by removing helm from our official support of release tooling, we can focus on tooling that is specific to OSM. This can allow us to place more guardrails and safety checks in the OSM cli.
We can still allow power users to leverage helm, but our official support (and the happy path), is through the OSM CLI.

This feels like we need to create a Discussion on GitHub or a thread in Slack


Concise UI automate with Java!

Concise UI automate with Java!
change vision to these：test，rpa，web automate，desktop UI automate

@roughsoft What do you mean? do you want to request some feature or suggest some changes in code or site?

I think selenide is great work!
It can do more things, no only test field.
It can do web automate,desktop ui automate,rpa.

Thank you for the feedback!


Upload modified directories & modified build script

Upload the modified directories and modified build

Please do the pull request against your own master branch

I apologize, I didn't even realize it was against your master branch. Won't happen again.
Get Outlook for Androidhttps://aka.ms/ghei36

From: Ed Griebel<EMAIL_ADDRESS>Sent: Saturday, February 8, 2020 7:48:01 PM
To: edgriebel/rit-iste422-project<EMAIL_ADDRESS>Cc: Vanguard714<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [edgriebel/rit-iste422-project] Upload modified directories & modified build script (#2)
Please do the pull request against your own master branch
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/edgriebel/rit-iste422-project/pull/2?email_source=notifications&email_token=AGWYD6MPFQIXG5NTJPZCGC3RB5HEDA5CNFSM4KR5G5Y2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOELF7NDI#issuecomment-583792269, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AGWYD6LNR52QTOSRRONXLYDRB5HEDANCNFSM4KR5G5YQ.


Basic support for unevaluated constants

Fixes #625

I meant in the fields of a struct?
On Thu, Aug 15, 2024 at 5:59 PM Nico Lehmann @.***>
wrote:

@.**** commented on this pull request.
In crates/flux-middle/src/rty/expr.rs
https://urldefense.com/v3/__https://github.com/flux-rs/flux/pull/719*discussion_r1719164054__;Iw!!Mih3wA!FTYDhh7eHoytVzVOxdBpPJdXcmpKjCRwrE7NJ-TWRCGj55DfgyoJgGUOPZVtXHUS0OxFKugQQbfR87PUFIf7-Jlx$
:

       ConstKind::Unevaluated(ue) => {

           let val = const_eval::unevaluated_to_constant(tcx, ue).unwrap();

           Expr::constant(val)

       }

if a function signature contains a struct with const arguments we will
normalize it when we normalize the signature.
—
Reply to this email directly, view it on GitHub
https://urldefense.com/v3/__https://github.com/flux-rs/flux/pull/719*discussion_r1719164054__;Iw!!Mih3wA!FTYDhh7eHoytVzVOxdBpPJdXcmpKjCRwrE7NJ-TWRCGj55DfgyoJgGUOPZVtXHUS0OxFKugQQbfR87PUFIf7-Jlx$,
or unsubscribe
https://urldefense.com/v3/__https://github.com/notifications/unsubscribe-auth/AAMS4ODTFN4CQEU6GGXFEQLZRVFIPAVCNFSM6AAAAABMTA3RSGVHI2DSMVQWIX3LMV43YUDVNRWFEZLROVSXG5CSMV3GSZLXHMZDENBRGU4DMNZQGI__;!!Mih3wA!FTYDhh7eHoytVzVOxdBpPJdXcmpKjCRwrE7NJ-TWRCGj55DfgyoJgGUOPZVtXHUS0OxFKugQQbfR87PUFAE0UUwd$
.
You are receiving this because you were mentioned.Message ID:
@.***>

I meant in the fields of a struct?

When we construct a struct we create a function signature from the struct definition which we will normalize before "calling" it.


Revert "make GC deterministic in distributed"

revert #821, which may cause the failure in mpi jobs.

bors r+

bors r+

bors r+


Add OpenGrok Dockerfiles

OpenGrok is an Oracle project that was being hosted under github.com/OpenGrok. This PR is part of the migration of OpenGrok to the Oracle organization. One of their assets is a Dockerfile for creating a Docker image with the project pre-installed.
The latest version of those files are in this PR.

I will leave this PR closed and wait for the OpenGrok team to decide how to migrate their Dockerfiles. If they want.

Yeah, updating it to use https://hub.docker.com/r/oracle/glassfish/ would be good.


Build is failing with Java 11.

Running build with Java 11 is failing (probably just an issue with tests).

@maciejwalkowiak The tests in ContextCredentialsConfigurationRegistrarTest are failing while asserting the following:
List<CredentialsProvider> credentialsProviders = (List<CredentialsProvider>) ReflectionTestUtils
				.getField(awsCredentialsProvider, "credentialsProviders");
assertThat(credentialsProviders).hasSize(1);
assertThat(credentialsProviders.get(0)).isInstanceOf(AWSStaticCredentialsProvider.class); //FAILING

Here the imported CredentialsProvider is org.apache.http.client.CredentialsProvider. I think it should be cast to List<com.amazonaws.auth.AWSCredentialsProvider> instead of List<org.apache.http.client.CredentialsProvider> as follows:
List<AWSCredentialsProvider> credentialsProviders = (List<AWSCredentialsProvider>) ReflectionTestUtils
				.getField(awsCredentialsProvider, "credentialsProviders");
assertThat(credentialsProviders).hasSize(1);
assertThat(credentialsProviders.get(0)).isInstanceOf(AWSStaticCredentialsProvider.class);

Casting to List<org.apache.http.client.CredentialsProvider> is also done in io.awspring.cloud.context.config.xml.ContextCredentialsBeanDefinitionParserTest and io.awspring.cloud.context.config.annotation.ContextCredentialsConfigurationRegistrarTest but these tests are passing because there are no instanceOf() assert.
I believe casting to List<com.amazonaws.auth.AWSCredentialsProvider> instead of List<org.apache.http.client.CredentialsProvider>  is the right fix because I don't see org.apache.http.client.CredentialsProvider being used in any of the CredentialProvider implementations.
Another way to fix this is to change the way we assert to the following:
From:
assertThat(credentialsProviders.get(0)).isInstanceOf(AWSStaticCredentialsProvider.class);

To:
assertThat(AWSStaticCredentialsProvider.class.isInstance(credentialsProviders.get(0))).isTrue();

Still, I am not sure why it is passing in Java 8 but failing in Java 11.
Please let me know your thoughts on this, I can create a PR.


Prism does not check duplicated variable name or duplicated key name in capture pattern

These codes are SyntaxError(duplicated variable name or duplicated key name) in Ruby
1 in [a, a]
1 in { a:, a: }
1 in a => a
1 => a => a
1 in a => b => a
1 => a => b => a

As a note, this is failing a language spec:
    it "does not support using variable name (except _) several times" do
      -> {
        eval <<~RUBY
          case [0]
          in [a, a]
          end
        RUBY
      }.should raise_error(SyntaxError, /duplicated variable name/)
    end


PA-626: Fix BackupRestartPX testcase failure in system test runs

What this PR does / why we need it:
We were seeing that the torpedo system test runs for px-backup was failing with the below trace:
19:23:56  ERRO[2023-02-20 13:53:48] Actual:TEST-ERROR, Expected: PASS
19:23:56  INFO[2023-02-20 13:53:48] --------Test End------
19:23:56  INFO[2023-02-20 13:53:48] #Test: BackupRestartPX
19:23:56  INFO[2023-02-20 13:53:48] #Description: Restart PX when backup in progress
19:23:56  INFO[2023-02-20 13:53:48] ------------------------
19:23:56
19:23:56  • Failure [887.057 seconds]
19:23:56  {BackupRestartPX}
19:23:56  /go/src/github.com/portworx/torpedo/tests/backup/backup_test.go:3409
19:23:56    Restart PX when backup in progress [It]
19:23:56    /go/src/github.com/portworx/torpedo/tests/backup/backup_test.go:3458
19:23:56
19:23:56    Unexpected error:
19:23:56        <*task.ErrTimedOut | 0xc00085eb60>: {
19:23:56            Reason: "context deadline exceeded",
19:23:56        }
19:23:56        timed out performing task., Error was: context deadline exceeded
19:23:56    occurred
19:23:56
19:23:56    /go/src/github.com/portworx/torpedo/pkg/log/log.go:334
19:23:56
19:23:56    Full Stack Trace
19:23:56    github.com/portworx/torpedo/pkg/log.FailOnError({0x739b9e0, 0xc00085eb60}, {0x6c8e6c0?, 0x35?}, {0xc0014f30b8?, 0xc0012c9078?, 0x219651e?})
19:23:56    	/go/src/github.com/portworx/torpedo/pkg/log/log.go:334 +0x290
19:23:56    github.com/portworx/torpedo/tests/backup.glob..func19.2.8()
19:23:56    	/go/src/github.com/portworx/torpedo/tests/backup/backup_test.go:3560 +0x2f2
19:23:56    github.com/portworx/torpedo/tests/backup.glob..func19.2()
19:23:56    	/go/src/github.com/portworx/torpedo/tests/backup/backup_test.go:3535 +0x713
19:23:56    github.com/portworx/torpedo/tests/backup.TestBasic(0x0?)
19:23:56    	/go/src/github.com/portworx/torpedo/tests/backup/backup_basic_test.go:59 +0xb9
19:23:56    testing.tRunner(0xc0004d8b60, 0x6d9cf20)
19:23:56    	/usr/local/go/src/testing/testing.go:1446 +0x10b
19:23:56    created by testing.(*T).Run
19:23:56    	/usr/local/go/src/testing/testing.go:1493 +0x35f
19:23:56  ------------------------------

The torpedo run output isn’t very clear, so tried running the test and logged in to the machine with central admin user. I was able to see that the backup is failing with the below error which is mostly due to the backup not being able to get status from the api server:

I was suspecting that the portworx-api restart is happening too quickly hence tried out with some sleep.

With Sleep of 2 mins, Dashboard URL : http://aetos.pwx.purestorage.com/resultSet/testSetID/103489
With Sleep of 30 sec, Dashboard URL : http://aetos.pwx.purestorage.com/resultSet/testSetID/103505
With Sleep of 20 sec, Dashboard URL : http://aetos.pwx.purestorage.com/resultSet/testSetID/103510
With Sleep of 10 sec, Dashboard URL : http://aetos.pwx.purestorage.com/resultSet/testSetID/103571
With Sleep of 5 sec,  Dashboard URL : http://aetos.pwx.purestorage.com/resultSet/testSetID/103595

Now for the above experiment was using time.Sleep() calls for the patch will be using WaitDriverUpOnNode() and do run the case multiple times and will open a PR.
Testing Data
Ran the testcase 5 times and haven't seen the failure even once. Below is the dashboard links for all five runs:

Dashboard URL : http://aetos.pwx.purestorage.com/resultSet/testSetID/103663
Dashboard URL : http://aetos.pwx.purestorage.com/resultSet/testSetID/103674
Dashboard URL : http://aetos.pwx.purestorage.com/resultSet/testSetID/103718
Dashboard URL : http://aetos.pwx.purestorage.com/resultSet/testSetID/103729
Dashboard URL : http://aetos.pwx.purestorage.com/resultSet/testSetID/103741

Which issue(s) this PR fixes (optional)
Closes # PA-626
Special notes for your reviewer:

Dashboard URL : http://aetos.pwx.purestorage.com/resultSet/testSetID/103811 (After addressing the comments).


feat: collect calico-system and tigera-operator logs

What type of PR is this?
/kind feature
What this PR does / why we need it:
Add calico-system and tigera-operator namespaces to container logs collected by sync-container-logs.sh script. This will be used by AKS on-call to troubleshoot issues in clusters with Calico enabled.
Which issue(s) this PR fixes:

Fixes #
Requirements:

[x] uses conventional commit messages
[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
Collect logs from containers in calico-system and tigera-operator namespaces.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
2293

Relevant Lines:
2890

💛  - Coveralls


Transforms do not support n>250

Describe the bug
the Transforms UI item is limited to 250 transforms, effectively blocking edits to all transforms after the first 250
To Reproduce

have 251 transforms
try to find #251 in the plugin

Expected behavior
Transforms should either have:
a) a load-more button
b) paginate automatically and return All transforms
Environment

"List transforms" does not support sorters.
I will use the "paginate" function to get all transforms, and sort by name "client side".
If there is more than 250 transforms, it's going to be a very long list -> thanks to VSCode capability, it's possible to search in the tree view

Fixed in 1.3.9.


Remove Null Access Token Error to enable responses without access tokens

This PR:

Removes the Null Access Token Entity Error thrown in generateAuthenticationResult when the cached authentication result contains no access token
Reverts AuthenticationResult.expiresOn type to Date | null to support cases in which an AuthenticationResult does not contain an access token
Fixes #3530

Coverage increased (+2.7%) to 86.472% when pulling 4a80cae893cc7c6ccd455f02eb3018126d5bd21c on fix-null-access-token-error into d7cdf7554de29f6171082f41701c19632e7ec48f on dev.


Support SwaggerUI V4?

I'd love to use this action, but with openapi 3.1, and it looks like swaggerUI V4 supports that. Any plan to update this action to use swaggerui v4 instead of v3? or any recommended alternatives?

Does swagger UI 4 also support older versions of openapi, 3.0 and older?

Ok then I think we should add an option to the action which allows to select the swagger ui version.

I just recognized that there is already an undocumented version option. But I don't know if the templating works with a new major version.

@melissarh57 have you checked that you can use swagger ui v4 using this parameter?


The description of the Summary API Source section does not match the KEP and code implementation

Problem:
When I was reading this page, I felt very confused.
The Kubelet gathers stats at node, volume, pod and container level, and omits them in the Summary API for consumers to read.

The meaning of this sentence is to explain that the node, volume, pod and container level information cannot be obtained from the summary API?
But I read  cAdvisor-less, CRI-full Container and Pod Stats KEP and code implementation:
enhance the CRI API with enough metrics to be able to supplement the pod and container fields in the summary API directly from CRI.

My understanding is:
The node, volume, pod and container level information can be obtained from the summary API.
So is omits them in the Summary API for consumers to read an expression error?
Proposed Solution:
Enhanced description to avoid ambiguity or misrepresentation.
Suggested modification:
The Kubelet gathers stats at node, volume, pod and container level, and outputs their statistics in the Summary API for consumers to read.

Page to Update:
https://kubernetes.io/docs/tasks/debug-application-cluster/resource-metrics-pipeline/

/assign @haircommander

Hi @mengjiao-liu, agree it needs fixing per https://github.com/kubernetes/website/issues/27840. I have a bunch of notes, please add your thoughts so we can clarify this matter. It is confusing.

/language en
The best place to add more notes is issue #27840

Thanks for the reminder, I've added comments to #27840

The Kubelet gathers stats at node, volume, pod and container level, and omits them in the Summary API for consumers to read.

it sounds like the original author intended emits instead. Outputs definitely works too.

it sounds like the original author intended emits instead. Outputs definitely works too.

Use emits as the word makes sense, thanks for the reply!

/triage accepted


Encryption-at-rest pattern: EBS and EFS

Issue #, if available:
Description of changes:
Adding a new security blueprint for data-at-rest encryption.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

@aliaksei-ivanou 1.7.1 is out, please update in package.json, I will retest after it.

Done


Provide specialized writeBytes override in NioBuffer

Motivation:
The NioBuffer implementation does not override the default Buffer version of writeBytes (array and ByteBuffer) leading to reduced performance for large arrays or buffers due to how the base methods are implemented, such as arrays which get written a byte at a time triggering a bounds check on each setByte call.
Modifications:
Implement writeBytes overrides in NioBuffer to increase performance of code that writes arrays or ByteBuffers into a NioBuffer
Result:
Improved throughput in application that utilize these methods.

Thanks!


Improve usability of Autocomplete

Search values with underscore by using blank space instead underscore

Show values when type in dynamic prompt

Would you mind explaining how to enable autocomplete? Even when (it seems to be) enabled, it never shows up, not even in your Note node...

I didn't create an option in settings.
it's always applied in textarea.

Did you setup the Custom words?


Update to BarterDEX Marketmaker v1.0.861

Time for an update.
Changes: https://github.com/artemii235/SuperNET/compare/v1.0.707...v1.0.861

Merging. I've had successful trades with both master and this PR today.


Add Transaction::salt(&self) -> Option<&Salt>

This method should return &Salt if the type is Transaction::create

This appears to be done already: https://github.com/FuelLabs/fuel-tx/blob/v0.19.0/src/transaction.rs#L294


update config with new arbitrum l1 security council; run discovery

With the execution of AIP 6 (activating security council elections), the L1 security council is a new contract.

thanks for the PR! the change was already in progress here: #1919
@DZGoldman why is the canceller now the UpgradeExecutor and not the SC directly? what's the advantage? it looks to me that the DAO still cannot cancel pending proposals, right?

@lucadonnoh

thanks for the PR! the change was already in progress here: https://github.com/l2beat/l2beat/pull/1919

ah, didn't see that, ty! feel to close this

why is the canceller now the UpgradeExecutor and not the SC directly? what's the advantage? it looks to me that the DAO still cannot cancel pending proposals, right?

Correct, the functionality of giving the role to SC would be materially the same; we give it to the UpgradeExecutor for consistency and simplicity. I.e., (now) wherever a contract wants to give an affordance to the SC, it does so via granting it to UpgradeExecutor, making the UpgradeExecutor the single source of truth for upgrade rights.

solved in the other PR


Bug report: wrong number of arguments when installing Lightroom 6.7

Remember to follow the pre bug report guide beforehand. Failure to do so might get your issue closed.
Yes, I did all that after the first time I saw this failure.
❯ cd $(brew --repo); git fetch; git reset --hard origin/master
❯ brew untap phinze/cask; brew untap caskroom/cask; brew uninstall --force brew-cask
❯ brew cleanup; brew cask cleanup; brew update

Description of issue
I'm installing on a new machine that has never had Lightroom or Adobe Creative Cloud installed. It fails with a Ruby stacktrace as shown in the output below.
Output of `brew cask  --verbose`
❯ brew cask install adobe-photoshop-lightroom --verbose
==> Caveats
Installation or Uninstallation may fail with Exit Code 19 (Conflicting Processes running) if Browsers, Safari Notification Service or SIMBL Services are running or Adobe Creative Cloud or any other Adobe Products are already installed. See Logs in /Library/Logs/Adobe/Installers if Installation or Uninstallation fails, to identify the conflicting processes.

==> Satisfying dependencies
==> Installing Cask dependencies: caskroom/versions/adobe-photoshop-lightroom600
caskroom/versions/adobe-photoshop-lightroom600 ...
==> Caveats
Installation or Uninstallation may fail with Exit Code 19 (Conflicting Processes running) if Browsers, Safari Notification Service or SIMBL Services are running or Adobe Creative Cloud or any other Adobe Products are already installed. See Logs in /Library/Logs/Adobe/Installers if Installation or Uninstallation fails, to identify the conflicting processes.

==> Downloading http://trials3.adobe.com/AdobeProducts/LTRM/6/osx10/Lightroom_6_LS11.dmg
/usr/bin/curl --fail --remote-time --location --user-agent Homebrew/1.1.4-2-g9cd5a21b (Macintosh; Intel macOS 10.12.2) curl/7.51.0 http://trials3.adobe.com/AdobeProducts/LTRM/6/osx10/Lightroom_6_LS11.dmg -C 0 -o /Users/nathany/Library/Caches/Homebrew/Cask/adobe-photoshop-lightroom600--6.0.dmg.incomplete -A Mozilla/5.0 (Macintosh; Intel Mac OS X 10) http://caskroom.io -b MM_TRIALS=1234
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  726M  100  726M    0     0   975k      0  0:12:43  0:12:43 --:--:--  915k
==> Verifying checksum for Cask adobe-photoshop-lightroom600
No matching processes belonging to you were found
Password:
Starting Installer... In Silent mode.
Begin Adobe Setup
UI mode: Silent
100.00%
End Adobe Setup.  Exit code: 0
Installation successful.
Exiting Installer with Code: 0
🍺  adobe-photoshop-lightroom600 was successfully installed!
done
complete
==> Downloading http://swupdl.adobe.com/updates/oobe/aam20/mac/AdobeLightroom-6.0/6.7/setup.dmg
/usr/bin/curl --fail --remote-time --location --user-agent Homebrew/1.1.4-2-g9cd5a21b (Macintosh; Intel macOS 10.12.2) curl/7.51.0 http://swupdl.adobe.com/updates/oobe/aam20/mac/AdobeLightroom-6.0/6.7/setup.dmg -C 0 -o /Users/nathany/Library/Caches/Homebrew/Cask/adobe-photoshop-lightroom--6.7.dmg.incomplete
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100  414M  100  414M    0     0   904k      0  0:07:49  0:07:49 --:--:--  982k
==> Verifying checksum for Cask adobe-photoshop-lightroom
==> No matching processes belonging to you were found
Error: Command failed to execute!

==> Failed command:
/usr/bin/killall -kill SafariNotificationAgent

==> Standard Output of failed command:

==> Standard Error of failed command:
No matching processes belonging to you were found

==> Exit status of failed command:
#<Process::Status: pid 47855 exit 1>
==> No matching processes belonging to you were found
Password:
==> Starting Installer... In Silent mode.
==> Installation successful.
==> Exiting Installer with Code: 0
Error: wrong number of arguments (1 for 4)
Follow the instructions here:
  https://github.com/caskroom/homebrew-cask/blob/master/doc/reporting_bugs/pre_bug_report.md

If this doesn’t fix the problem, please report this bug:
  https://github.com/caskroom/homebrew-cask#reporting-bugs

/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/exceptions.rb:60:in `initialize'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/installer.rb:156:in `exception'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/installer.rb:156:in `raise'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/installer.rb:156:in `rescue in install_artifacts'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/installer.rb:135:in `install_artifacts'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/installer.rb:87:in `install'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/install.rb:25:in `block in install_casks'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/install.rb:19:in `each'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/install.rb:19:in `install_casks'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli/install.rb:10:in `run'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:110:in `run_command'
/usr/local/Homebrew/Library/Homebrew/cask/lib/hbc/cli.rb:149:in `process'
/usr/local/Homebrew/Library/Homebrew/cask/cmd/brew-cask.rb:8:in `<top (required)>'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/rubygems/core_ext/kernel_require.rb:55:in `require'
/usr/local/Homebrew/Library/Homebrew/brew.rb:24:in `require?'
/usr/local/Homebrew/Library/Homebrew/brew.rb:100:in `<main>'
Error: Kernel.exit

Output of `brew doctor`
Please note that these warnings are just used to help the Homebrew maintainers
with debugging if you file an issue. If everything you use Homebrew for is
working fine: please don't worry and just ignore them. Thanks!

Warning: "config" scripts exist outside your system or Homebrew directories.
`./configure` scripts often look for *-config scripts to determine if
software packages are installed, and what additional flags to use when
compiling and linking.

Having additional scripts in your path can confuse software installed via
Homebrew if the config script overrides a system or Homebrew provided
script of the same name. We found the following "config" scripts:
  /Applications/Postgres.app/Contents/Versions/latest/bin/gdal-config

Output of `brew cask doctor`
❯ brew cask doctor
==> macOS Release:
10.12.2
==> Hardware Architecture:
intel-64
==> Ruby Version:
2.0.0-p648
==> Ruby Path:
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/bin/ruby
==> Homebrew Version:
Homebrew 1.1.4-2-g9cd5a21b
Homebrew/homebrew-core (git revision 90d2; last commit 2016-12-14)
==> Homebrew Executable Path:
/usr/local/bin/brew
==> Homebrew Cellar Path:
/usr/local/Cellar
==> Homebrew Repository Path:
/usr/local/Homebrew
==> Homebrew Origin:
https://github.com/Homebrew/brew
==> Homebrew-Cask Version:
Homebrew-Cask 1.1.4-2-g9cd5a21b
caskroom/homebrew-cask (git revision 09b3; last commit 2016-12-15)
==> Homebrew-Cask Install Location:
<NONE>
==> Homebrew-Cask Staging Location:
/usr/local/Caskroom
==> Homebrew-Cask Cached Downloads:
/Users/nathany/Library/Caches/Homebrew/Cask
2 files, 1.1G (warning: run "brew cask cleanup")
==> Homebrew-Cask Default Tap Path:
/usr/local/Homebrew/Library/Taps/caskroom/homebrew-cask
==> Homebrew-Cask Alternate Cask Taps:
/usr/local/Homebrew/Library/Taps/caskroom/homebrew-versions
==> Homebrew-Cask Default Tap Cask Count:
3485
==> Contents of $LOAD_PATH:
/usr/local/Homebrew/Library/Homebrew/cask/lib
/usr/local/Homebrew/Library/Homebrew
/Library/Ruby/Site/2.0.0
/Library/Ruby/Site/2.0.0/x86_64-darwin16
/Library/Ruby/Site/2.0.0/universal-darwin16
/Library/Ruby/Site
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0/x86_64-darwin16
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby/2.0.0/universal-darwin16
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/vendor_ruby
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/x86_64-darwin16
/System/Library/Frameworks/Ruby.framework/Versions/2.0/usr/lib/ruby/2.0.0/universal-darwin16
==> Contents of $RUBYLIB Environment Variable:
<NONE>
==> Contents of $RUBYOPT Environment Variable:
<NONE>
==> Contents of $RUBYPATH Environment Variable:
<NONE>
==> Contents of $RBENV_VERSION Environment Variable:
<NONE>
==> Contents of $CHRUBY_VERSION Environment Variable:
<NONE>
==> Contents of $GEM_HOME Environment Variable:
<NONE>
==> Contents of $GEM_PATH Environment Variable:
<NONE>
==> Contents of $BUNDLE_PATH Environment Variable:
<NONE>
==> Contents of $PATH Environment Variable:
PATH="/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin:/Applications/Postgres.app/Contents/Versions/latest/bin:/Users/nathany/src/go.googlesource.com/go/bin:/Users/nathany/bin:/usr/local/Homebrew/Library/Taps/homebrew/homebrew-bundle/cmd:/usr/local/Homebrew/Library/Homebrew/cask/cmd:/usr/local/Homebrew/Library/Homebrew/shims/scm"
==> Contents of $SHELL Environment Variable:
SHELL="/bin/zsh"
==> Contents of Locale Environment Variables:
LANG="en_CA.UTF-8"
LC_CTYPE="en_CA.UTF-8"

Affected cask: https://github.com/caskroom/homebrew-cask/blob/master/Casks/adobe-photoshop-lightroom.rb

Here is what the preflight stanza was before the implementation of system_command:
  preflight do
    system '/usr/bin/killall', '-kill', 'SafariNotificationAgent'
    system '/usr/bin/sudo', '-E', '--', "#{staged_path}/AdobePatchInstaller.app/Contents/MacOS/AdobePatchInstaller", '--mode=silent'
  end

Ping @reitermarkus.

fyi, this was on macOS Sierra 10.12.2 on a 13" MacBook Pro (2016) w/Touch Bar.

I've got exactly the same error installing skype-for-business.
I just mention this here just in case the cause is a more general thing than something related to the cask.

@cldsnchz I do not think your issue is related to this one, as Skype-for-business.rb does not use system_command.
Would you mind following the instructions here and submitting a separate issue?

Ah, yes, this is because system_command defaults to must_succeed: true, while system doesn't raise an exception if the exit code is non-zero.

@nathany would you mind reinstalling adobe-photoshop-lightroom.rb via the command brew cask install https://raw.githubusercontent.com/reitermarkus/homebrew-cask/496208073a784eafd2f6654f049d4a7d9fdfaf1d/Casks/adobe-photoshop-lightroom.rb and let us know if PR #27884 fixes your problem?

Thanks Markus. 👍


Fix classification crash when toggling translucency

Fixes https://github.com/CesiumGS/cesium/issues/9421.
The idea behind this fix is that it is possible for the translucent command in TranslucentTileClassification to have a previously destroyed shader by the time getDerivedCommand is called from executeTranslucentCommands. One clue that supports this idea is that the crash only seems to happen when the translucency checkbox is turned on, and not off (see the Sandcastle). If the command is dirty by the time getDerivedCommand is called, the shader should be recreated instead of reusing the outdated one from when the tileset was opaque.
I'm still not 100% sure when the command state gets messed up, but I believe the bug happens because:

Toggling on translucency changes the translucency command's shaders.
The translucency command now has dirty = true.
Scene never checks whether the translucent commands are dirty (i.e. like it does with shadow maps in updateDerivedCommands, and the state is only visible from the loop over commands inside executeTranslucentCommands. For this reason, checking for ... || command.dirty inside TranslucentTileClassification#getDerivedCommand makes sense to me (as opposed to somewhere higher up like Scene).
If the derived command is never updated in a dirty command, the shader program can be pointing to an outdated shader that has already been destroyed.

Thanks for the pull request @ebogo1!

:heavy_check_mark: Signed CLA found.
:grey_question: CHANGES.md was not updated.

If this change updates the public API in any way, please add a bullet point to CHANGES.md.

:grey_question: Unit tests were not updated.

Make sure you've updated tests to reflect your changes, added tests for any new code, and ran the code coverage tool.

Reviewers, don't forget to make sure that:

[ ] Cesium Viewer works.
[ ] Works in 2D/CV.
[ ] Works (or fails gracefully) in IE11.

Unfortunately due to how convoluted derived commands are the simple fix ended up not being enough. Stepping through the code the log depth command was always dirty and the original command was always not dirty. This meant that when log depth was enabled it would create a new depth-only derived command every frame, and when log depth was disabled the fix wouldn't work, both bad.
Scene.prototype.updateDerivedCommands is what handles deriving commands and it's called well before TranslucentTileClassification.prototype.executeTranslucentCommands, so relying on the dirty property won't work in this case.
I realized there was a simpler fix that could use the existing depth-only derived command that's created in updateDerivedCommands in Scene. This depth-only command is created for all commands except when pickOnly = true. pickOnly will be false for opaque/translucent 3D Tiles commands so it's safe to rely on it existing.
The last fix was addressing the render states. Previously the TranslucentTileClassification derived command would set rs.stencilTest = StencilConstants.setCesium3DTileBit(); to order for classification to work at all. The better fix was to set the stencil state when the translucent render states were originally created.
Because of the idiosyncrasies of derived commands, stencil state, etc I just pushed the changes directly. At some point we should refactor derived commands because they are very difficult to navigate.


Investigate storing much of the data in a database, to reduce load time and memory use

This pull request adds an alternative option to looking up constant properties in Pandas dataframes. Essentially, a common path is to use a function like Tb without a method specified; and to not use either the Tb_methods or the Tb_sources function and variable respectively. For this one common application, the only needed information is the Tb value itself.
Therefore, a script dev/generate_sqlite_database.py was created to obtain the default values for each constant property in chemicals. The resulting database is 7.3 MB, and compresses to 3.3 MB in a zip archive.
The sqlite database is always stored on disk, so there is substantial memory savings from this approach. The query time is acceptable in general. When using something like %timeit, one search is 10-15 us. However, in this case the used database pages being cached in memory. On my machine when the disk has to be accessed (as measured by doing a single read), the time is about 800 us. I wrote the database lookup to retrieve all of the pure component properties for a compound at once, and cache them in memory once accessed. The layout of sqlite is such that this is as fast as only retrieving one property.
Loading the sqlite3 module takes ~3 ms. It is delayed until needed.
There is a setting chemicals.data_reader.USE_CONSTANTS_DATABASE which defaults to True. The sqlite database can't be committed to git as it will be updated regularly and therefore bloat up the repository size unreasonably.
Included with this change is further work on the int_CAS setting earlier discussed. The files with CAS numbers using int_CAS are now expected to have the CAS number without the dashes included, i.e. 50000 instead of 50-00-0. Doing the conversion in Python turned out to be quite slow, and this way the Pandas csv reader can read them directly as integers. To make this work, all of the data files had their header corrected to use CAS as the index variable.
There are a few more minor data corrections as well.
This PR does add considerably complexity to the project, but I believe it will be appreciated and will make the project better. In the future, it may be possible to provide something for temperature dependent properties as well.

@CalebBell, this is awesome. I don't think there is much complexity added. I made some minor edits here and there under the assumption that the index must be either a string or an integer. The database_constant_lookup fails in my machine every time with the following exception:
File "...\chemicals\data_reader.py", line 247, in cached_constant_lookup
    CONSTANTS_CURSOR.execute("SELECT * FROM constants WHERE `index`=?", (str(CASi),))

OperationalError: no such table: constants

I have not worked with sql before so I am not able to debug this quickly, but maybe you could help me? I added some code that prevent database lookup after the first failure related to sql searches.
Other than getting the search to work. I think this branch can be merged whenever. Feel free to revert any of my changes that aren't helpful.
Thanks!

Hi Yoel!
I hope you are well and thank you for the feedback! It is always nice to not be alone. Thank you for taking the time to take a look! I hope this branch can improve your libraries as well as mine.
I believe the error you are getting is that the database isn't on your machine. It needs to be generated first:
python dev/generate_sqlite_database.py
Please let me know if this doesn't work for you.
The database is easy to distribute as part of the pip release. It will take a little more work to get the conda build to ship with it. This is a big part of my reluctance to the approach; but as more and more data is added to the library this type of approach seems like the only one that doesn't unduly increase load time.

@yoelcortes have you been able to check if the database generation script works for you?

Hi @CalebBell, sorry about that, I meant to get back to you sooner but was doing some traveling memorial for memorial weekend. Yes, it works well on my computer. I also fixed some bugs I introduced in my past commits (which required the sql file to run). As always, your work on enhancing your ChemE libraries is much appreciated by me and tons others. I am happy I can help and contribute too :)
By the way, I like the new int_CAS parameter. Would it be a good idea to load other files in chemicals using this? I'm not sure if it would add too much overhead, what do you think? Here are some of the files that whose index are not currently converted to iCASs:
Physical Constants of Inorganic Compounds.csv
Physical Constants of Organic Compounds.csv
IUPACOrganicCriticalProps.tsv
CRCCriticalOrganics.tsv
Mathews1972InorganicCriticalProps.tsv
Appendix to PSRK Revision 4.tsv
PassutDanner1973.tsv
Yaws Collection.tsv
DIPPRPinaMartines.tsv
Antoine Collection Poling.tsv
Table 2-8 Vapor Pressure of Inorganic and Organic Liquids.tsv
Alcock_Itkin_Horrigan_metalic_elements.tsv
Wagner Original McGarry.tsv
Wagner Collection Poling.tsv
Antoine Extended Collection Poling.tsv
VDI PPDS Boiling temperatures at different pressures.tsv
Florian_Liming_RON_experimental.tsv
Florian_Liming_MON_experimental.tsv
Florian_Liming_RON_MON_ANN.tsv
Travis_Kessler_Combustdb_RON.tsv
Travis_Kessler_Combustdb_MON.tsv
Travis_Kessler_Combustdb_predictions.tsv
Dahmen_Marquardt_ignition_delay_IQT.tsv
Poling Dipole.csv
cccbdb.nist.gov Dipoles.csv
Muller Supporting Info Dipoles.csv
psi4_dipoles.tsv
Official Global Warming Potentials 2007.tsv
Official Global Warming Potentials 2014.tsv
Ozone Depletion Potentials.tsv
CRC logP table.tsv
Syrres logP data.csv.gz
PolingDatabank.tsv
TRC Thermodynamics of Organic Compounds in the Gas State.tsv
CRC Standard Thermodynamic Properties of Chemical Substances.tsv
MuleroCachadinaParameters.tsv
Jasper-Lange.tsv
Somayajulu.tsv
SomayajuluRevised.tsv
VDI PPDS surface tensions.tsv
MagalhaesLJ.tsv
PolingLJ.tsv
psi4_radius_of_gyrations.tsv
chemsep_radius_of_gyrations.tsv
psi4_linear.tsv
Permittivity (Dielectric Constant) of Liquids.tsv
Yaws Boiling Points.tsv
OpenNotebook Melting Points.tsv
Ghazerati Appendix Vaporization Enthalpy.tsv
CRC Handbook Heat of Vaporization.tsv
CRC Handbook Heat of Fusion.tsv
Ghazerati Appendix Sublimation Enthalpy.tsv
Table 2-150 Heats of Vaporization of Inorganic and Organic Liquids.tsv
VDI PPDS Enthalpies of vaporization.tsv
Alibakhshi one-coefficient enthalpy of vaporization.tsv
API TDB Albahri Hf (g).tsv
ATcT 1.112 (g).tsv
ATcT 1.112 (l).tsv
Yaws Hf S0 (g).tsv
CRC Handbook Organic RI.csv
NFPA 497 2008.tsv
IS IEC 60079-20-1 2010.tsv
DIPPR T_flash Serat.csv
National Toxicology Program Carcinogens.tsv
IARC Carcinogen Database.tsv
Dutt Prasad 3 term.tsv
Viswanath Natarajan Dynamic 3 term.tsv
Viswanath Natarajan Dynamic 2 term.tsv
Viswanath Natarajan Dynamic 2 term Exponential.tsv
Table 2-313 Viscosity of Inorganic and Organic Liquids.tsv
Table 2-312 Vapor Viscosity of Inorganic and Organic Substances.tsv
VDI PPDS Dynamic viscosity of saturated liquids polynomials.tsv
VDI PPDS Dynamic viscosity of gases polynomials.tsv
Table 2-314 Vapor Thermal Conductivity of Inorganic and Organic Substances.tsv
Table 2-315 Thermal Conductivity of Inorganic and Organic Liquids.tsv
VDI PPDS Thermal conductivity of saturated liquids.tsv
VDI PPDS Thermal conductivity of gases.tsv
Staveley 1981.tsv
COSTALD Parameters.tsv
Mchaweh SN0 deltas.tsv
Perry Parameters 105.tsv
CRC Liquid Inorganic Constant Densities.tsv
CRC Solid Inorganic Constant Densities.tsv
VDI PPDS Density of Saturated Liquids.tsv
CRC Inorganics densties of molten compounds and salts.tsv
CRC Virial polynomials.tsv
Please feel free to merge whenever,
Thanks!

Forgot to mention, I think adding the sql database to the pip installation would be a good idea. I'm not sure how to add it to the conda installation either.

Hi Yoel!
We are very lucky - the conda package is built right from the package uploaded to PyPi. Because of that, the default.sqlite database needs to be generated on the machine which uploads the package to pypi. I added a script dev/prerelease.py which creates the database and will do other things related to the release as required. I am very pleased with this development; I didn't expect such a large win. The maintenance overhead will very hopefully be minimal.
The new release is version 1.1.1, as this feels like a major change. I have tested and confirmed both releases ship with the sqlite database.
I am not sure the idea of converting older .tsv files to use integer CAS numbers is worthwhile. In particular, I know of some people indexing into those files using CAS numbers as strings, so it would not be good to break that functionality them. I think pursuing expanding the database with temperature dependent property fits is a larger win, and hope to focus potential future memory reduction efforts into that.
Thank you for your excellent review!
Caleb


Doesn't work in laravel 4

i had try to require this package in laravel 4, but i doesn't work.
"Could not find package skmetaly/laravel-smtp-email-verifier at any version for your minimum-stability (stable). Check the package spelling or your minimum-stability"
please fix it. at least please more documentation about minimum stability. and what version of laravel can use it.

Hi,
For now, at least temporarily go to composer.json file and change minimum stability to :
  "minimum-stability": "dev"

and redo a
composer install


accept a class parameter (slice or string) and append to

This allows css manipulation of pagination block via utility classes.
By default the pagination block is justify:left and it can only be justified to the center via css (not utility classes, which this template is written with)

@sean-pwd Thanks for this. I'll be working on this embedded template in the coming days to address an unrelated issue, and I will give this some thought. One of my concerns is, if we do this, are we going to have similar requests for the other embedded templates and built-in shortcodes? That's not a necessarily a bad thing, but it would set a precedent.

I'm not sure about the precedent, but as a template that utilizes bootstrap
utility classes it's hard to work with - I wrapped it in a div and was
unable to center the buttons with utility classes on the div.
On Thu, 11 Nov 2021, 6:48 am Joe Mooring, @.***> wrote:

@sean-pwd https://github.com/sean-pwd Thanks for this. I'll be working
on this embedded template in the coming days to address an unrelated issue,
and I will give this some thought. One of my concerns is, if we do this,
are we going to have similar requests for the other embedded templates and
built-in shortcodes? That's not a necessarily a bad thing, but it would set
a precedent.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gohugoio/hugo/pull/9154#issuecomment-965687236, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ARTWGA34GOCQDCH7OLVTL23ULLEB3ANCNFSM5HXW5RLA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

@sean-pwd you center your pagination using BS5 with flex like this, works with the internal pagination template:

Thanks for that, that was a big oversight on my part.
I'll leave it up to you guys if its appropriate to include the class
parameter
Sean Emerson
Web Developer, Powerful Web Design
02 8004 3293 <212-931-0000>
| @.***
www.powerfulwebdesign.com.au
http://www.facebook.com/ http://www.linkedin.com/ http://twitter.com/
http://instagram.com/
On Thu, 11 Nov 2021 at 15:15, Patrick Kollitsch @.***>
wrote:

@sean-pwd https://github.com/sean-pwd you center your pagination using
BS5 with flex like this, works with the internal pagination template:

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/gohugoio/hugo/pull/9154#issuecomment-965973085, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ARTWGA6WUYFZ4D4DYF7ZXYDULM7ORANCNFSM5HXW5RLA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


Database migrations

Planning to add database migrations, might switch out exposed with something else

Fixed in #6


[Enhancement] - Replace logo with terminal video

A video of the CLI in action would be more useful to potential users than the logo.
Potential solutions
asciinema seems to provide the recording functionality

Fixed following #2


How to add a documentation column to HTML reports

Is there an easy way to add a documentation column to the runs in  HTML report (log.html) ?

Could you clarify? Notice also that robotframework-users and other such forums are better for questions. If you got a concrete enhancement request, this is the correct place to submit it.


Feature/header setup

This pull request aims to merge the config-and-basic-setup branch into the develop branch of the repository. I have completed all the specific and general requirements for the basic project setup, as well as the following points:
Details
Config & Basic Setup:

[x] Use  components for navigation links with active styling to indicate the selected section/page.

General Requirements:

[x] Fix all linter errors and follow the correct Gitflow workflow.
[x] Maintain a consistent code structure and applied best practices for HTML, CSS, and JavaScript.
[x] Document all work, providing explanatory comments in the code and a detailed description of this pull request.

I appreciate your time in reviewing and approving this pull request. If there are any suggestions or further improvements, I'll be happy to make the necessary changes.

Thank you for reviewing and considering this pull request for merging into the "develop" branch!
@ClaudiaRojasSoto

@ClaudiaRojasSoto The license has been included, thanks for your review


fix(deps): update all non-major

This PR contains the following updates:

Package
Type
Update
Change

base64
dependencies
patch
0.21.4 -> 0.21.5

futures-util (source)
dependencies
patch
0.3.28 -> 0.3.29

serde (source)
dependencies
patch
1.0.189 -> 1.0.190

Release Notes

marshallpierce/rust-base64 (base64)
v0.21.5
Compare Source

Add Debug and Clone impls for the general purpose Engine

rust-lang/futures-rs (futures-util)
v0.3.29
Compare Source

Add TryStreamExt::try_ready_chunks (#2757)
Add TryStreamExt::{try_all,try_any} (#2783)
Add UnboundedSender::{len,is_empty} (#2750)
Fix Sync impl of FuturesUnordered (#2788)
Fix infinite loop caused by invalid UTF-8 bytes (#2785)
Fix build error with -Z minimal-versions (#2761)

serde-rs/serde (serde)
v1.0.190
Compare Source

Preserve NaN sign when deserializing f32 from f64 or vice versa (#2637)

Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
👻 Immortal: This PR will be recreated if closed unmerged. Get config help if that's undesired.

[ ] If you want to rebase/retry this PR, check this box

This PR has been generated by Renovate Bot.

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

GitHub release
v1.2.4

Your semantic-release bot :package::rocket:


Try Nesting Tests Inside Package

Any background context you want to provide?
What does this PR accomplish?
How should this be manually tested?
What are the relevant tickets?

Screenshots (if appropriate)

@JingWang-CUB ignore the ruff failures for now. Can you try this to see if it fixes your testing issues?
@vtnate if this works, maybe we can polish this up and use it instead of #33 ?

@vtnate if this works, maybe we can polish this up and use it instead of #33 ?

@mitchute This works on my mac. Needs a little cleanup that I can take care of.
@JingWang-CUB, Will you pull this version and try running the tests in a Python 3.9 environment? If it works, that would mean we don't have to change the python requirement.

I'm still having test failures on Windows with Python 3.9. See errors below.
============================= test session starts =============================
platform win32 -- Python 3.9.0, pytest-7.4.4, pluggy-1.5.0
rootdir: C:\GitHub\ThermalNetwork
configfile: pyproject.toml
testpaths: thermalnetwork/tests
plugins: cov-4.1.0, syrupy-4.6.1
collected 0 items / 3 errors
=================================== ERRORS ====================================
_____ ERROR collecting thermalnetwork/tests/test_ground_heat_exchanger.py _____
ImportError while importing test module 'C:\GitHub\ThermalNetwork\thermalnetwork\tests\test_ground_heat_exchanger.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
C:\Users\jwang5\Anaconda3\envs\gmt\lib\importlib_init_.py:127: in import_module
return _bootstrap.gcd_import(name[level:], package, level)
thermalnetwork\tests\test_ground_heat_exchanger.py:1: in
from thermalnetwork.ground_heat_exchanger import GHE
E   ModuleNotFoundError: No module named 'thermalnetwork'
___________ ERROR collecting thermalnetwork/tests/test_heat_pump.py ___________
ImportError while importing test module 'C:\GitHub\ThermalNetwork\thermalnetwork\tests\test_heat_pump.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
C:\Users\jwang5\Anaconda3\envs\gmt\lib\importlib_init.py:127: in import_module
return _bootstrap.gcd_import(name[level:], package, level)
thermalnetwork\tests\test_heat_pump.py:3: in
from thermalnetwork.heat_pump import HeatPump
E   ModuleNotFoundError: No module named 'thermalnetwork'
____________ ERROR collecting thermalnetwork/tests/test_network.py ____________
ImportError while importing test module 'C:\GitHub\ThermalNetwork\thermalnetwork\tests\test_network.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
C:\Users\jwang5\Anaconda3\envs\gmt\lib\importlib_init.py:127: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
thermalnetwork\tests\test_network.py:5: in
from thermalnetwork.network import run_sizer_from_cli_worker
E   ModuleNotFoundError: No module named 'thermalnetwork'
----------- coverage: platform win32, python 3.9.0-final-0 -----------
Coverage HTML written to dir htmlcov
=========================== short test summary info ===========================
ERROR thermalnetwork/tests/test_ground_heat_exchanger.py
ERROR thermalnetwork/tests/test_heat_pump.py
ERROR thermalnetwork/tests/test_network.py
!!!!!!!!!!!!!!!!!!! Interrupted: 3 errors during collection !!!!!!!!!!!!!!!!!!!
============================== 3 errors in 0.22s ==============================
All tests pass on Windows with Python 3.10.
============================= test session starts =============================
platform win32 -- Python 3.10.12, pytest-7.4.4, pluggy-1.3.0
rootdir: C:\GitHub\ThermalNetwork
configfile: pyproject.toml
testpaths: thermalnetwork/tests
plugins: anyio-4.4.0, cov-4.1.0, syrupy-4.5.0
collected 6 items
thermalnetwork\tests\test_ground_heat_exchanger.py .                     [ 16%]
thermalnetwork\tests\test_heat_pump.py .                                 [ 33%]
thermalnetwork\tests\test_network.py ....                                [100%]
---------- coverage: platform win32, python 3.10.12-final-0 ----------
Coverage HTML written to dir htmlcov
======================== 6 passed in 221.62s (0:03:41) ========================

I sometimes have this issue when using VSCode (on Mac) because... (IDK... the env vars don't get set properly??) What I usually have to do is add the following.
$ PYTHONPATH=. pytest ...
i.e. the "PYTHONPATH" part. Does that help?

I sometimes have this issue when using VSCode (on Mac) because... (IDK... the env vars don't get set properly??) What I usually have to do is add the following.
$ PYTHONPATH=. pytest ...
i.e. the "PYTHONPATH" part. Does that help?

It might have helped a little. Now I got different errors.
$ PYTHONPATH=. pytest
============================= test session starts =============================
platform win32 -- Python 3.9.0, pytest-7.4.4, pluggy-1.5.0
rootdir: C:\GitHub\ThermalNetwork
configfile: pyproject.toml
testpaths: thermalnetwork/tests
plugins: cov-4.1.0, syrupy-4.6.1
collected 1 item / 2 errors
=================================== ERRORS ====================================
_____ ERROR collecting thermalnetwork/tests/test_ground_heat_exchanger.py _____
ImportError while importing test module 'C:\GitHub\ThermalNetwork\thermalnetwork\tests\test_ground_heat_exchanger.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
C:\Users\jwang5\Anaconda3\envs\gmt\lib\importlib_init_.py:127: in import_module
return _bootstrap.gcd_import(name[level:], package, level)
thermalnetwork\tests\test_ground_heat_exchanger.py:1: in
from thermalnetwork.ground_heat_exchanger import GHE
thermalnetwork\ground_heat_exchanger.py:7: in
from ghedesigner.manager import GHEManager
E   ModuleNotFoundError: No module named 'ghedesigner'
____________ ERROR collecting thermalnetwork/tests/test_network.py ____________
ImportError while importing test module 'C:\GitHub\ThermalNetwork\thermalnetwork\tests\test_network.py'.
Hint: make sure your test modules/packages have valid Python names.
Traceback:
C:\Users\jwang5\Anaconda3\envs\gmt\lib\importlib_init.py:127: in import_module
return _bootstrap._gcd_import(name[level:], package, level)
thermalnetwork\tests\test_network.py:5: in
from thermalnetwork.network import run_sizer_from_cli_worker
thermalnetwork\network.py:10: in
from rich.logging import RichHandler
E   ModuleNotFoundError: No module named 'rich'
----------- coverage: platform win32, python 3.9.0-final-0 -----------
Coverage HTML written to dir htmlcov
=========================== short test summary info ===========================
ERROR thermalnetwork/tests/test_ground_heat_exchanger.py
ERROR thermalnetwork/tests/test_network.py
!!!!!!!!!!!!!!!!!!! Interrupted: 2 errors during collection !!!!!!!!!!!!!!!!!!!
============================== 2 errors in 0.66s ==============================

pip freeze shows ghedesigner and rich?

This is an artifact of the differences between PyCharm's native formatter and Ruff. Maybe I can configure PyCharm to pick up a Ruff formatting file...

https://docs.astral.sh/ruff/editors/

Creating a clean conda environment with Python 3.9 worked. All tests passed.
============================= test session starts =============================
platform win32 -- Python 3.9.19, pytest-8.3.2, pluggy-1.5.0
rootdir: C:\GitHub\ThermalNetwork
configfile: pyproject.toml
testpaths: thermalnetwork/tests
plugins: anyio-4.4.0, cov-4.1.0
collected 6 items
thermalnetwork\tests\test_ground_heat_exchanger.py .                     [ 16%]
thermalnetwork\tests\test_heat_pump.py .                                 [ 33%]
thermalnetwork\tests\test_network.py ....                                [100%]
---------- coverage: platform win32, python 3.9.19-final-0 -----------
Coverage HTML written to dir htmlcov
======================== 6 passed in 216.90s (0:03:36) ========================

@vtnate Anything else to do here?

@mitchute This is great! Perhaps remove testing on macos in CI? I think it's good to go. I'll close the other PR.

Perhaps remove testing on macos in CI?

Yeah, up to you on that one. I'm good either way.


Polluting simple web page

When have the extension enabled it pollutes a web page looking like this:
<!DOCTYPE html>
<html>
    <head>
        <title>title</title>
    </head>
    <body>
        Text
    </body>
</html>

to this:
<html>
    <head>
        <title>title</title>
    </head>
    <body>
        <pre>
           Text
	</pre>
    </body>
</html>

This is a very hard bug to fix, to properly fix this the extension should ignore anything that is text/html but some weird APIs insist in return the wrong mime-type, I think I will add a config to disable this behavior.

Just came across this today completely messing up this simple page:

some weird APIs insist in return the wrong mime-type

I don't know what those weird APIs are, but should this really be accommodating for the exceptions?  Any news on the config option? :slightly_smiling_face:


Swift 4 support

I started Swift 4 support (https://github.com/carlbrown/http/tree/swift4), but got blocked on #22. It doesn't look like that's going to get fixed, so I'll work around it, starting with #39
Once that gets merged, I'll push a new swift-tools-version = 4.0 Package.swift file and associated fixes to either develop or a swift4 specific branch, whichever we think makes the most sense.

This has been done, so I'll close this one off.


Download output files via DataStaging in JSDL

The current method of retrieving output files does not work for outputs other than std{out,err}, since they are deleted when the job status changes to Finished.
Since it takes ages (~3 minutes) for the status to change, I had not noticed it before.

See if it possible to download files back to client using <DataStaging> elements in the JSDL
Otherwise wrap job to zip/tar everything up and save to stdout location

Done by setting DeleteOnTermination flag to false for a specified file/directory in the JSDL.
0d143a39a2509690c21599c1398c543ad3e4aaf4


Azure App Service pricing inconsistent use of term "stamp fee"

ASEv3 doesn't have a stamp fee, but we're using the term "stamp fee" to refer to ASEv3 instances with no instances in use (minimum instance charge).
Leads to some confusion around ASEv2 vs. ASEv3 pricing.  Should rework the article to change the terminology.

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

ID: fb1c7712-7798-3505-4545-b44cd9870034
Version Independent ID: 49bd2e58-0d17-784d-26d6-5c1275131d69
Content: Reservation discounts for Azure App Service - Microsoft Cost Management
Content Source: articles/cost-management-billing/reservations/reservation-discount-app-service.md
Service: cost-management-billing
Sub-service: reservations
GitHub Login: @bandersmsft
Microsoft Alias: banders

@aionic
Thanks for your feedback! We will investigate and update as appropriate.

@bandersmsft FYI

@aionic Hi there. I've spoken with the App Service engineering team about this issue. We're updating the article for clarity in our terminology with the following addition:

App Service Environment v3 uses isolated v2 instances – there are no stamp fees, and you buy a reservation for the instances themselves.
App Service Environment v2 uses isolated instances – there is a stamp fee, and you can only buy reservations for the stamp fee, not the instances.

I hope this helps.
https://github.com/MicrosoftDocs/azure-docs-pr/pull/236949
#please-close


[SPARK-45396][DOCS] Add doc entry for pyspark.ml.connect module

What changes were proposed in this pull request?

Add doc entry for pyspark.ml.connect module
Why are the changes needed?

Without doc entry page, user cannot view pyspark.ml.connect python APIs on doc website.
Does this PR introduce any user-facing change?

No.
How was this patch tested?

Manually
Was this patch authored or co-authored using generative AI tooling?

No.

Actually let me take this over since doc build fails.

Let me take it over at https://github.com/apache/spark/pull/43210

@HyukjinKwon Could you backport this to spark 3.5 branch ?


Fix custompage issue when there are two

Fix #3386

It appears the current regen shows some odd swapping from ctor to Create which doesn't seem right.  https://github.com/Azure/azure-sdk-for-net/pull/36206/files#diff-a076be848338a356eff6ca0db1f64dfb29bd595405264856797b6041c97e2ad2R123
Please send an updated regen PR.  Did we manually check this against this branch to see that the two lists now generate as expected?

It appears the current regen shows some odd swapping from ctor to Create which doesn't seem right. https://github.com/Azure/azure-sdk-for-net/pull/36206/files#diff-a076be848338a356eff6ca0db1f64dfb29bd595405264856797b6041c97e2ad2R123
Please send an updated regen PR. Did we manually check this against this branch to see that the two lists now generate as expected?

This is already updated. We have that change in regen PR is because @JoshLove-msft did this change manually https://github.com/Azure/azure-sdk-for-net/pull/36192 and testcommon doesn't have a ci.yml there so we cannot regen after that manual change. @JoshLove-msft I think the autogenerated code is expected, we shouldn't have manually change them. Is there any reason you did this?
Yes, I checked their entire spec and the generated code is expected.

The testcommon library is pinned to a specific version of AutoRest so it doesn't pick up new changes. Should we try to unpin it?

The testcommon library is pinned to a specific version of AutoRest so it doesn't pick up new changes. Should we try to unpin it?
https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/testcommon/Azure.Graph.Rbac/src/Azure.Graph.Rbac.csproj#L16

@m-nash Seems you did this change. Any background here? I create an issue here: https://github.com/Azure/azure-sdk-for-net/issues/36235

The testcommon library is pinned to a specific version of AutoRest so it doesn't pick up new changes. Should we try to unpin it?
https://github.com/Azure/azure-sdk-for-net/blob/main/sdk/testcommon/Azure.Graph.Rbac/src/Azure.Graph.Rbac.csproj#L16

We can't unpin it, we would either need to sync the release label that is pinned now and create a fix in a hotfix branch and release from there and update the version, OR we need to move this to manual code, we cannot change generated files manually.

Commented out the download shared source check until this gets resolved https://github.com/Azure/autorest.csharp/pull/3392


Indent when surrounding multiple lines

I noticed that when surrounding multiple lines like this

My Header

Other Stuff

the output is not indented

My Header

Other Stuff

It does the indenting when using line visual selection mode and surrounding in that mode

My Header

Other Stuff

It works this way, see:

My Header

Other Stuff

This issue is related to this other issue #208
i'm on main latest version btw

First and foremost, sorry for the delay! I've been a bit busy recently with classes and whatnot. I think that the key here is that ys won't put delimiters on their own line, so asking to reindent doesn't really make sense IMO. As of right now, the semantics are that stuff that puts delimiters on new lines should re-indent. In your particular use case, does ySjtdiv work?

Thank you for your response, I didn't know yS was possible, it works, thank you.


Use DateTimeFormatter to produce localized AM/PM labels for TimePicker

WHAT
Use DateTimeFormatter to produce localized AM/PM labels for TimePicker instead of string resource with translation.
WHY
In some languages, the translated AM/PM labels are too long for a watch screen.
HOW
Checklist :clipboard:

[ ] Add explicit visibility modifier and explicit return types for public declarations
[ ] Run spotless check
[ ] Run tests
[ ] Update metalava's signature text files

Added a screenshot test case with localized am label in en-rGB. In this case, this change will use am instead of a.m..


Add JsonSerializerSettings in Global configuration for Request Body

I encountered an error because the serialization of objects didn't change it to camel case, which the end point was expecting. As such, I recommend adding to the configuration the ability to specify deserialization settings.
Here is what I propose:
_globalConfiguration = new GlobalConfiguration.Builder()
    .AuthManagers(new Dictionary<string, AuthManager> {
        { "global", new BearerAuthManager(accessToken) }
    })
    .HttpConfiguration(new CoreHttpClientConfiguration.Builder().Build())
    .ServerUrls(urlMap, Server.Default)
    .JsonSerializerSettings(new JsonSerializerSettings
    {
        ContractResolver = new DefaultContractResolver
        {
            NamingStrategy = new CamelCaseNamingStrategy()
        },
        MaxDepth = 128
    })
    .UserAgent(USER_AGENT)
    .Build();

I applied this logic for my current project and it worked smoothly. But I think solution should also consider XML serialization which my work didn't consider/take into account.
Hope this helps, and if you want the current solution, I'm happy to push a PR.

I forgot to mention, debugging was a bit a pain because the ExecuteAsync doesn't return the context. I made a change to add that as an option.

Hi @all4peace
Sorry for getting back to you late on this. The property names can be modified using the JsonPropertyAttribute specified over the properties in the model classes to match the endpoint requirements. The apimatic/core-lib-csharp specifically is designed to be used with the auto-generated C# SDKs by APIMatic. The models auto-generated in the C# SDK use the serialization attributes from the API specification file. We also support a basic level of XML serialization. More information on the SDK generation using APIMatic can be found here https://www.apimatic.io/.
Furthermore, you can get the context using the ContextAdder delegate in ApiCall > ResponseHandler
I hope this helps!


[Error 193] %1 is not a valid Win32 application

Expected Behavior
Actual Behavior
File "pokecli.py", line 501, in
main()
File "pokecli.py", line 130, in main
report_summary(bot)
File "pokecli.py", line 139, in report_summary
metrics.capture_stats()
File "D:\programs\git\pokemongo-Bot\pokemongo-Bot\pokemongo_bot\metrics.py", line 76, in capture_stats
response_dict = request.call()
File "D:\programs\git\pokemongo-Bot\pokemongo-Bot\pokemongo_bot\api_wrapper.py", line 106, in call
result = self._call()
File "D:\programs\git\pokemongo-Bot\pokemongo-Bot\pokemongo_bot\api_wrapper.py", line 63, in _call
return PGoApiRequest.call(self)
File "d:\programs\git\pokemongo-bot\pokemongo-bot\src\pgoapi\pgoapi\pgoapi.py", line 210, in call
request.activate_signature(lib_path)
File "d:\programs\git\pokemongo-bot\pokemongo-bot\src\pgoapi\pgoapi\rpc_api.py", line 85, in activate_signature
self.signature_lib = ctypes.cdll.LoadLibrary(lib_path)
File "D:\Python27\lib\ctypes_init.py", line 443, in LoadLibrary
return self.dlltype(name)
File "D:\Python27\lib\ctypes_init.py", line 365, in init
self._handle = _dlopen(self._name, mode)
WindowsError: [Error 193] %1 is not a valid Win32 application
Steps to Reproduce
Bot logs in succesfully then this
Other Information
OS:  W7
Python Version: 2.7.10

Change encrypt.so to encrypt.dll. They are working with Linux, poor instructions really.

Same issue. I'm using the encrypt.dll one though.

You actually have to download encrypt32bit.dll even if you're on a 64 bit OS, then change the name to encrypt.dll, place it in the root of your bot directory.
It isn't referring to your OS when it determines whether you need 32 or 64 bit.

Assume solved.


The link to the heading in the current file is invalid.

Link to other heading inside same file doesn't work, like inside a.md, link xxx doesn't work, it has to be [xxx])(a#test).

Thank you for reporting!
Yes, I embarrassingly have not implemented this yet. I also just added it as a checkbox to the readme.
Since it is now on the roadmap, I'll close this.
Feel free to reopen and/or continue commenting here

(no reason to close I realize)


[Enhancement] Pam Modules (yubikey) auth

So I know, that this is probably just supposed to be a lightweight, KISS lua implementation of PAM, but I was wondering, if it was possible to add support for other Pam-authentication modes (such as yubikey auth).
I know, that yubikey auth is setup properly on my system, since I do not need a Password on sudo, or sudo login.
I had a quick glance at the docs, and know, that this is a really hard improvement.
As a starter, have a look at the following: pam_sm_authenticate

There is a yubikey pam module, but i have no yubikey, so cannot write and test for yubikey, sorry.

This Issue is more meant for general pam-module auth, so other auth factors than password can be used. There are also U2F modules. Honestly more, than one could imagine. If I really want support I'll do a pr.
Until then, I think that we should keep this open, if you don't think, that this is out of place.

This Issue is more meant for general pam-module auth, so other auth factors than password can be used.

A good idea, i will try to find some ways later if i have time.

Ok, so something interesting, I have a working version (sadly not cross distro). I changed the service name to common-auth (that's where I defined my yubikey auth) and added a pam_end() call at the end.
I will have to check, on how to get it working with login as the service name.


Providing support for AWS Memcached ElastiCache cluster

Can you add possibility to setup option, e.g.:
$dynamic_client->setOption(Memcached::OPT_CLIENT_MODE, Memcached::DYNAMIC_CLIENT_MODE);

See: http://docs.aws.amazon.com/AmazonElastiCache/latest/UserGuide/AutoDiscovery.html#AutoDiscovery.ModifyAppPHP
Amazon provides special version of Memcached client for PHP that is able to auto-detect nodes but the option needs to be specified explicitly.

Can you do a PR please? I have no way of testing AWS, so I would kindly ask for your help here :-)


update contact Page(links work, dark mode, content, theme{background with some animations simple design})

issue #89
update contact Page(links work, dark mode, content, theme{background with some animations simple design})

PLease add ss or vids of  work as per pr template

@Kritika30032002

@Kritika30032002

@ElvinPero

@Kritika30032002 1) It is contact us(not contact me)
2) Please design the form layout in dark with white text during dark mode .
3) For any queries regarding templates ,contact us (This line can be added )your line has gramatical mistakes.

It has been a lot of time since i assigned and this result more or less looks like the previous one  :/
can you make a good contact us ? or are you fine with me assigning someone else

It has been a lot of time since i assigned and this result more or less looks like the previous one :/ can you make a good contact us ? or are you fine with me assigning someone else

you can assign to someone else!