posix: clock: current method of capturing elapsed time leads to loss in seconds

Describe the bug
Although it is a boundary, before the 64-bit tick counter rolls-over, the value of the monotonic clock (seconds field) should equal UINT64_MAX / CONFIG_SYS_CLOCK_TICKS_PER_SEC (integer division).
Currently, it seems to be off by an order of magnitude (test case provided in PR).
Please also mention any information which could help others to understand
the problem you're facing:

What target platform are you using? all
What have you tried to diagnose or workaround this issue? written a test case
Is this a regression? If yes, have you been able to "git bisect" it to a
specific commit? No

To Reproduce
Steps to reproduce the behavior:

apply changes in referenced PR
un-apply changes to lib/posix/clock.c
west build -p auto -b qemu_x86_64 -t run tests/posix/common
See error

Expected behavior
*** Booting Zephyr OS build zephyr-v3.2.0-2459-gdffb02fd134e ***
Running TESTSUITE posix_apis
===================================================================
START - test_clock_gettime_rollover
CONFIG_SYS_CLOCK_TICKS_PER_SEC: 100
rollover_s:<PHONE_NUMBER>37095516
t-1: {184467440737095516, 140000000}
t+0: {184467440737095516, 150000000}
t+1: {0, 0}
 PASS - test_clock_gettime_rollover in 0.063 seconds
 ===================================================================

Impact
That really depends on the application. It can be an annoyance for some but a showstopper for others.
Logs and console output
*** Booting Zephyr OS build zephyr-v3.2.0-2459-gdffb02fd134e ***
Running TESTSUITE posix_apis
===================================================================
START - test_clock_gettime_rollover
CONFIG_SYS_CLOCK_TICKS_PER_SEC: 100
rollover_s:<PHONE_NUMBER>37095516
t-1: {18446744073709551, 596000000}

    Assertion failed at WEST_TOPDIR/zephyr/tests/posix/common/src/clock.c:169: posix_apis_test_clock_gettime_rollover: rollover_s not equal to ts[0].tv_sec

 FAIL - test_clock_gettime_rollover in 0.025 seconds
 ===================================================================

Environment (please complete the following information):

OS: (e.g. Linux, MacOS, Windows): any
Toolchain (e.g Zephyr SDK, ...): Zephyr SDK 0.15.2
Commit SHA or Version used: bba9fc98535567008728143cc3b8c029670d84c6

Additional context
This issue was encountered while writing tests to verify the fixes in

https://github.com/zephyrproject-rtos/zephyr/pull/41602
https://github.com/zephyrproject-rtos/zephyr/pull/41814
and while working on
https://github.com/zephyrproject-rtos/zephyr/issues/52825

[generator.cpp.txt](https://github.com/zephyrproject-rtos/zephyr/files/10269878/generator.cpp.txt)
Technically, I believe we are seeing a bug in z_tmcvt() which does not have a comprehensive testsuite, AFAIK. So #52977 is more of a workaround for the POSIX subsystem.
Also, I should mention, the error factor is 1 order of magnitude with ticks/s = 100. With ticks/s = 10, it's 2 orders of magnitude. With ticks/s >= 1000 the error vanishes.
I'm fairly concerned about the test coverage for z_tmcvt().


Treat impacted parameters from downstream dependencies as triggered fixes.

Resolves #64 by treating impacted parameters by downstream dependencies as triggered fixes while processing public methods.
It also resolves issue with updating the stored impacts in downstream dependencies after each injection to prevent double counting.

@lazaroclapp This PR is ready for review. This changes made a lot of issues to avoid double counting since we are treating impacted parameters as triggered fixes. It also includes a refactoring to clean instantiating explorers since downstream dependency analysis is added as part of the explorers. Please let me know if you prefer to break this PR into multiple PRs. Thank you very much :)

Taking a look... not sure if I'll be able to finish my pass tonight, but for now, one thing worth pointing out is that the description for this PR seems incomplete, at the very least this is also solving the separate issue of the shared library models directory... (I think that would be an argument for it to be split into multiple PRs, each addressing a different bug or feature, but I also think we are short on time, so let me take a look as is, just make sure we document what this PR is actually changing 🙂 )

Hi @lazaroclapp, thank you very much for the review, I resolved your comments and left a question. This is ready for another review. Thanks.

🚀

Thank you very much for the review, I created all the requested issue. Will land this now. 🙂


minor worker refactoring

I ran into the following error when running the main branch as is:

I refactored a bit to help debug.

You have to use the following because in asyncio, the wait() statement on an empty list isn't allowed.
if self.background_get_job_tasks:
      await asyncio.wait(self.background_get_job_tasks)

All tests pass now with full code coverage. I'll start testing vLLM now.


Font charwidth has no effect

Checklist

[x] I have read the appropriate section in the contributing
guidelines
[x] I believe this issue is a problem with polybar itself and not a misconfiguration on my part.
[x] I have searched for other open and closed issues that
may have already reported this problem.
[x] I have checked the known issues page for this problem.

Describe the bug
If I set
font-0 = Terminus-10

the Terminus font is loaded as expected (I've double checked it in fc-match). However, I find its characters are too spread apart from each other, so I tried the charwidth specifier:
font-0 = Terminus-10:charwidth=7

Expected behavior:
The characters of the font should be slightly squeezed together.
Actual behavior:
No effect, the font is loaded as just before.
Was it working before?
I don't know because I did not use Polybar before.
To Reproduce

[bar/issue]
font-0 = Terminus-10:charwidth=10
modules-right = text
[module/text]
type = custom/text
content = label

Polybar Log

For charwidth=10:
notice: Parsing config file: /home/user/.config/polybar/config
notice: Loaded font "Terminus-10:charwidth=10" (name=Terminus, offset=0, file=/usr/share/fonts/opentype/terminus/terminus-normal.otb)

For charwidth=7:
notice: Parsing config file: /home/user/.config/polybar/config
notice: Loaded font "Terminus-10:charwidth=7" (name=Terminus, offset=0, file=/usr/share/fonts/opentype/terminus/terminus-normal.otb)

Screenshots

Environment:

WM: Spectrwm
Distro: Debian
Output of polybar -vvv:

polybar 3.5.5

Features: +alsa +curl +i3 +mpd +network(libnl) +pulseaudio +xkeyboard

X extensions: +randr (+monitors) +composite +xkb +xrm +xcursor

Debian package, build flags removed from output for reproducibility
You can refer to the build logs at:
https://buildd.debian.org/status/package.php?p=polybar

Additional context

The exact same setting does work in the built-in bar of my window manager (Spectrwm). Please note that changing the format to Terminus:size=10:charwidth=7 also has no effect, and that I tried various charwidth values.

Our text rendering isn't the best because we do it at a very low level, so unless cairo (what we use for font rendering) directly honors this property or the property causes a different font file to be loaded, it probably won't work in polybar.
At some point we will want to start using a more powerful font rendering library that does the heavy lifting for us (see https://github.com/polybar/polybar/issues/2369).
I'm going to mark this as "won't fix" because any time spent on implementing this would be better spent on exploring a different font rendering library.

Thanks. If someone stumbles on this issue, I've found that Dzen works fine.


Add unit for network components characteristics and fix some type error

Could you also change in code examples single quotes into double quotes (in rendering engine, single quotes are supposed to be used only for chars) ?


bump-formula-pr: misleading error message when API token lacks scope

[x] ran brew update and can still reproduce the problem?
[x] ran brew doctor, fixed all issues and can still reproduce the problem?
[x] ran brew config and brew doctor and included their output with your issue?

What you were trying to do (and why)
Bump a version of a formula using the brew bump-formula-pr command.
What happened (include command output)
I ran:
brew bump-formula-pr --strict chezmoi --tag=v1.8.1 --revision=4def4f3b96cb01cefe8d7887e8dbfb77908ef267 -v

and got the error message:
Error: Unable to fork: Not Found!

Command output

==> replace /^  revision \d+\n(\n(  head "))?/m with "\\2"
==> replace "v1.8.0" with "v1.8.1"
==> replace "017a83f4055a98ac90b030d5739aa560dde239b7" with "4def4f3b96cb01cefe8d7887e8dbfb77908ef267"
/usr/local/bin/brew audit --strict /usr/local/Homebrew/Library/Taps/homebrew/homebrew-core/Formula/chezmoi.rb
Error: Unable to fork: Not Found!

What you expected to happen
I expected the bump formula PR to create a PR, or to give a helpful error message as to why it couldn't.
Step-by-step reproduction instructions (by running brew commands)
I did some digging into the code and I found the following:

The GitHub personal access token I was using for Homebrew did not have public_repo scope, it only had public access.
Consequently the call to Github.create_fork (https://github.com/Homebrew/brew/blob/master/Library/Homebrew/dev-cmd/bump-formula-pr.rb#L419) was raising an exception, presumably because the GitHub API was returning a 404 somewhere.
Using a new access token with the public_repo scope allowed brew bump-formula-pr to complete successfully (https://github.com/Homebrew/homebrew-core/pull/54333).

So, this issue should be reproducible with:

Create a GitHub access token with no scopes (i.e. just public access).
Use the access token with brew bump-formula-pr.

brew already has nice code for reporting insufficient scopes (e.g. https://github.com/Homebrew/brew/blob/master/Library/Homebrew/utils/github.rb#L131), however it looks like the GitHub API is returning a 404 Not Found, not a 401 Unauthorized. I have not verified this.
Output of brew config and brew doctor commands
Likely not relevant but included for completeness.

brew config

HOMEBREW_VERSION: 2.2.15-18-g61b98a5
ORIGIN: https://github.com/Homebrew/brew
HEAD: 61b98a5e2ed3d8d00ae93ae325a8fe5363ae2ac2
Last commit: 5 hours ago
Core tap ORIGIN: https://github.com/Homebrew/homebrew-core
Core tap HEAD: cb163da7f4d59dd5634ea41bddf1b5aa2dac90f1
Core tap last commit: 45 minutes ago
HOMEBREW_PREFIX: /usr/local
HOMEBREW_DISPLAY: /private/tmp/com.apple.launchd.qHAJpoqlvu/org.macosforge.xquartz:0
HOMEBREW_EDITOR: vim
HOMEBREW_GITHUB_API_TOKEN: set
HOMEBREW_MAKE_JOBS: 8
CPU: octa-core 64-bit haswell
Homebrew Ruby: 2.6.3 => /System/Library/Frameworks/Ruby.framework/Versions/2.6/usr/bin/ruby
Clang: 11.0 build 1100
Git: 2.26.2 => /usr/local/bin/git
Curl: 7.64.1 => /usr/bin/curl
Java: 13.0.1
macOS: 10.15.4-x86_64
CLT: <IP_ADDRESS>
Xcode: N/A
XQuartz: 2.7.11 => /opt/X11

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 or file an issue; just ignore this. Thanks!
Warning: A newer Command Line Tools release is available.
Update them from Software Update in System Preferences or run:
softwareupdate --all --install --force
If that doesn't show you an update run:
sudo rm -rf /Library/Developer/CommandLineTools
sudo xcode-select --install
Alternatively, manually download them from:
https://developer.apple.com/download/more/.
Warning: You have unlinked kegs in your Cellar.
Leaving kegs unlinked can lead to build-trouble and cause brews that depend on
those kegs to fail to run properly once built. Run brew link on these:
docker

it looks like the GitHub API is returning a 404 Not Found, not a 401 Unauthorized. I have not verified this.

Can you verify this?
Obviously/unfortunately if the API returns 404 we cannot tell whether it's an invalid scope or the resource doesn't exist.

This should be fixed by #7634.

Wow, thanks @zmwangx!

No problem!


skrooge: 2.27.0 -> 2.28.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/skrooge/versions.
meta.description for skrooge is: "A personal finances manager, powered by KDE"
meta.homepage for skrooge is: "https://skrooge.org/"
meta.changelog for skrooge is: ""
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2.28.0 with grep in /nix/store/mvbwhnzj3gqq4jafyw7s0b87akbwigwx-skrooge-2.28.0
found 2.28.0 in filename of file in /nix/store/mvbwhnzj3gqq4jafyw7s0b87akbwigwx-skrooge-2.28.0

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
skrooge

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/mvbwhnzj3gqq4jafyw7s0b87akbwigwx-skrooge-2.28.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A skrooge https://github.com/r-ryantm/nixpkgs/archive/11b8569e72df6372e29442353740ad79dadb47f5.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/mvbwhnzj3gqq4jafyw7s0b87akbwigwx-skrooge-2.28.0
ls -la /nix/store/mvbwhnzj3gqq4jafyw7s0b87akbwigwx-skrooge-2.28.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

skrooge

Maintainer pings
cc @jokogr for testing.

Result of nixpkgs-review pr 184709 run on x86_64-linux 1

1 package built:

skrooge


composer error

When I run composer require vladimir-yuldashev/laravel-queue-rabbitmq I get the error message :
  Could not find package vladimir-yuldashev/laravel-queue-rabbitmq at any version for your minimum-stability (stable). Check the package spelling or
   your minimum-stability

Have you guys ever seen that ?

It could be due to the changeover on php-amqplib. I get this warning now:
Package videlalvaro/php-amqplib is abandoned, you should avoid using it. Use php-amqplib/php-amqplib instead.

I got that when installing the preferred distribution of laravel via composer. It installs laravel 5.2 . The current latest version of this package requires laravel 5.1 .
You can install that with the following composer command
composer create-project laravel/laravel project-name "5.1.*"

Just tagged 5.2


v3.2.0

Add spi_mode to the hardware configuration.
For SPI attached cards, SPI Mode 3 can significantly improve performance.
See SPI Controller Configuration.
Make timeouts configurable. See Timeouts.
Add retries in SPI driver sd_read_blocks.

Addresses Semaphore use in spi.c


Lattice and array operations, including setF

Lots of basic lemmas on Arrays, and some new reasoning in PropFun about lattices, complements, and eqsat.

addresses #13

I'm trying to keep the core sorry-free. Are you using the sorry'd lemmas in PPA? maybe we put the setF file in experiments with the PPA implementation


Updated package design

The main thing to review in this PR is the new file structure.

Thought on structure/naming - I wonder if we could make the names of directories which hold classes for implementations on top of the base Stage classes plural (i.e. model_stage -> model_stages, etc.). Tiny thing but to me that makes it a bit clearer that these are instances of Stages built on top of ModelStage (etc) rather than components required in the core implementation of ModelStage (etc)


[SSV]: Implement encrypted keys and fix small bugs

Summary

[ ] Implemet encrypted keys (for new setups)
[ ] Migrate raw keys to encrypted keys (for existing setups)
[x] Equal Expert Mode container ports with TcpPort and UdpPort in SSV Config file
[ ] Fix "My Operator Page" URL for specific network
[ ] Fix GUI for existing operator

Resources:

SSV -> Create Configuration File
SSV -> Generate Operator Keys (Encrypted)
SSV -> How do I migrate raw (deprecated) Operator Keys

Details
Below the issues listed above are described in detail.
Implemet encrypted keys (for new setups)
New nodes should setup SSV with encrypted keys by default.
Suggestion: Extend the existing GUI to do this automatically
Migrate raw keys to encrypted keys (for existing setups)
On existing nodes raw (deprecated) keys should be migrated to encrypted keys with a further Stereum update.
Suggestion: Provide a new or extend the existing GUI to do this automatically
Equal Expert Mode container ports with TcpPort and UdpPort in SSV Config file
Currently the Expert Mode container ports are 12000/udp and 13000/tcp
However the ports in SSV config file are UdpPort: 12001 and TcpPort: 13001
Expert Mode container ports

SSV Config file

Fix My Operator Page URL
A click on the "My Operator Page" button sends the user always to https://explorer.ssv.network/operators/ which is for Mainnet
 but other networks have a different URL. For example, Goerli should be https://goerli.explorer.ssv.network/operators
Fix GUI for existing Operator
After registering a new Operator the GUI changes to show current Operator settings:

However, after a certain time the GUI changes again as if no Operator was registered:

Then you try to register your existing Operator again with the current public key:

But the process goes stuck with a never ending spinner:

Make sure the GUI stays with the already installed Operator screen if public/secret keys are added/detectd in the SSV config file.

Talked with Martin, will do some UI to choose between the legacy key fromat & the new encrypted
Legacy stays as is, with the additional option to migrate from legacy to encrypted
The encrypted option should consist of a file selector

Here are the adapted UI to address the encrypted.
First a general change to the current SSV Page when opening the modal in the header, when a registered key is already imported

Note: First button displays network name

The encrypted key setup changes
The new first steps now depend on the user & what kind of key they use. If they want to continue using a raw (unencrypted) private key, they can - however joining now is the option the generate a encrypted & as well to import one

RAW SETUP STEPS
NOTE: Here we want to over to migrate the keys to encrypted ones

STEP
IMAGE

1#

2#

GENERATE ENCRYPTED KEY

STEP
IMAGE

1#

2#

3#

4#

5#

6#

IMPORT ENCRYPTED KEY

STEP
IMAGE

1#

2#

3#


Job submitted to scaled down cluster

Old thread: https://github.com/awslabs/cfncluster/issues/208
I've just confirmed that this issue can still happen, especially when there is large number of nodes being scaled down very fast.
The output from qstat -f is below
<EMAIL_ADDRESS>BIP   0/2/1          -NA-     lx-amd64      aduo
2863 0.60500 cromwell_f ec2-user     r     03/06/2018 18:44:21     2
I confirmed using intermediate files that this job did not start at all.

Side question, is there a way to configure cfncluster so the scaling down doesn't happen so fast?

Please look at http://cfncluster.readthedocs.io/en/latest/configuration.html#scaling-cooldown  who can help in scaling down slower. Note this parameter can affect your scale up behavior too

Is there a way for the SGE system to detect such events and exit out the jobs on these scaled down/dead clusters with an error code?

In addition, I have observed times where the node was scaled down while the job was still running.

This bug has been resolved in the upcoming 1.6.0 release:
https://github.com/awslabs/cfncluster/blob/develop/CHANGELOG.rst#160
If you are willing to test the release candindate you can install it with:
pip install -Iv cfncluster==1.6.0rc1
Please keep us updated if you have the opportunity to test the rc1 or please stay tuned for the upcoming 1.6.0 release.

We have been running v1.6.1 for almost a week now, and continue to see this issue, along with #334.  I think these two issues are related.
I documented one instance here: https://github.com/awslabs/cfncluster/issues/334#issuecomment-435142259
The problem occurs rather frequently, at least once a day or so, and often requires manual intervention to clear out.  Note that we also were experiencing the problem prior to v1.6.1 as well.  Any help on this would be appreciated.  I would also be interested in knowing if others have been experiencing this as well.

FYI we (same org as @tkuzuhara) still have this issue on pcluster 2.1.1
An example of a job that ran into this (just a hostname; sleep X):
$ qacct -j 149
==============================================================
qname        all.q
hostname     ip-172-31-128-119.us-west-2.compute.internal
group        eng
owner        keien
project      NONE
department   defaultdepartment
jobname      hostname
jobnumber    149
taskid       undefined
account      sge
priority     0
qsub_time    Fri Feb 15 13:30:37 2019
start_time   -/-
end_time     -/-
granted_pe   smp
slots        36
failed       25  : rescheduling
exit_status  0
ru_wallclock 0s
ru_utime     0.000s
ru_stime     0.000s
ru_maxrss    0.000B
ru_ixrss     0.000B
ru_ismrss    0.000B
ru_idrss     0.000B
ru_isrss     0.000B
ru_minflt    0
ru_majflt    0
ru_nswap     0
ru_inblock   0
ru_oublock   0
ru_msgsnd    0
ru_msgrcv    0
ru_nsignals  0
ru_nvcsw     0
ru_nivcsw    0
cpu          0.000s
mem          0.000Bs
io           0.000B
iow          0.000s
maxvmem      0.000B
arid         undefined
ar_sub_time  undefined
category     -l h_rt=86400,s_rt=86400 -pe smp 36
==============================================================
qname        all.q
hostname     ip-172-31-128-19.us-west-2.compute.internal
group        eng
owner        keien
project      NONE
department   defaultdepartment
jobname      hostname
jobnumber    149
taskid       undefined
account      sge
priority     0
qsub_time    Fri Feb 15 13:50:26 2019
start_time   Fri Feb 15 13:51:27 2019
end_time     Fri Feb 15 16:05:49 2019
granted_pe   smp
slots        36
failed       100 : assumedly after job
exit_status  137                  (Killed)
ru_wallclock 8062s
ru_utime     0.065s
ru_stime     0.107s
ru_maxrss    2.812KB
ru_ixrss     0.000B
ru_ismrss    0.000B
ru_idrss     0.000B
ru_isrss     0.000B
ru_minflt    29458
ru_majflt    0
ru_nswap     0
ru_inblock   64
ru_oublock   184
ru_msgsnd    0
ru_msgrcv    0
ru_nsignals  0
ru_nvcsw     301
ru_nivcsw    65
cpu          0.172s
mem          17.826KBs
io           2.392MB
iow          0.000s
maxvmem      2.160MB
arid         undefined
ar_sub_time  undefined
category     -l h_rt=86400,s_rt=86400 -pe smp 36

the host it was initially put on was brought up, then quickly brought down:
$ grep 128-119 /var/log/sqswatcher
2019-02-15 13:49:13,299 INFO [sqswatcher:pollQueue] Adding Hostname: ip-172-31-128-119
2019-02-15 13:49:13,299 INFO [sge:addHost] Adding ip-172-31-128-119 with 36 slots
ip-172-31-128-119.us-west-2.compute.internal added to administrative host list
ip-172-31-128-119.us-west-2.compute.internal added to submit host list
<EMAIL_ADDRESS>added "ip-172-31-128-119.us-west-2.compute.internal" to exechost list
2019-02-15 13:49:13,340 INFO [sge:addHost] Connecting to host: ip-172-31-128-119 iter: 0
2019-02-15 13:51:18,047 INFO [sge:removeHost] Removing ip-172-31-128-119
<EMAIL_ADDRESS>removed "ip-172-31-128-119.us-west-2.compute.internal" from administrative host list
<EMAIL_ADDRESS>removed "ip-172-31-128-119.us-west-2.compute.internal" from execution host list
<EMAIL_ADDRESS>removed "ip-172-31-128-119.us-west-2.compute.internal" from submit host list

normally the job would not have even restarted, and instead sit forever in the running state on a host that doesn't exist anymore, while qconf -de on the host would've failed because of the job still in the queue as we've previously shown in #334; we have had to build our own rescheduler to deal with this
I don't have any logs from the host that was brought up and subsequently brought down - this issue isn't very easily reproducible so it's hard to catch it on the fly

Hi @keien, while we investigate

Hi @keien
while we investigate, can you send us the configuration of the cluster, the full /var/log/sqswatcher and /var/log/jobwatcher?

Cluster config:
[global]
update_check = true
sanity_check = true
cluster_template = m5-4xlarge-ami-02860d917774b37b8-spot

[cluster m5-4xlarge-ami-spot]
custom_ami = XXXXXX
# below is inserted from config/m5-4xlarge-spot
compute_instance_type = m5.4xlarge
cluster_type = spot
spot_price = 1.00
master_instance_type = t2.medium
master_root_volume_size = 100
compute_root_volume_size = 100
initial_queue_size = 0
max_queue_size = 16
maintain_initial_size = false
base_os=centos7
key_name = ec2-admin
pre_install = s3://XXXXXX/pre_install.sh
post_install = s3://XXXXXX/post_install.sh
extra_json = { "cluster" : { "cfn_scheduler_slots" : "cores" } }
vpc_settings = default
scaling_settings = default
# below is inserted from config/vpc-default
[vpc default]
vpc_id = XXXXXX
master_subnet_id = XXXXXX
vpc_security_group_id = XXXXXX
use_public_ips = false
# below is inserted from config/scaling-profiles
[scaling default]
# Threshold for triggering CloudWatch ScaleUp action
# (defaults to 1 for default template)
scaling_threshold = 1
# Number of instances to add when called CloudWatch ScaleUp action
# (defaults to 1 for default template)
scaling_adjustment = 1
# Threshold for triggering CloudWatch ScaleUp2 action
# (defaults to 200 for default template)
#scaling_threshold2 = 200
# Number of instances to add when called CloudWatch ScaleUp2 action
# (defaults to 20 for default template)
#scaling_adjustment2 = 20
# Period to measure ScalingThreshold
# (defaults to 60 for default template)
scaling_period = 30
# Period to measure ScalingThreshold
# (defaults to 2 for default template)
scaling_evaluation_periods = 2
# Amount of time in seconds to wait before attempting further scaling actions
# (defaults to 300 for the default template
scaling_cooldown = 300

# scaling config for aggressive one-job-one-instance burst usage
[scaling one-to-one]
scaling_threshold = 1
scaling_adjustment = 1
scaling_threshold2 = 20
scaling_adjustment2 = 10

sqswatcher and jobwatcher: https://gist.github.com/keien/ed121f5e678b2b7788f339783d9fdff5
FYI after some investigation, we may have a clue about what's causing this: it seems that our AMI takes quite a bit of time to start (for unknown reasons) and it looks like the ASG itself is terminating the instance shortly after it comes up once it gets past the health check grace period. We manually increased the health check grace period and we're now monitoring to see if it fixes the issue.
Along those lines, I couldn't find any information about adding additional configuration to the CloudFormation template to do things like set the health check grace period for the ASG - is there a way to do that through pcluster?

Since version 1.6.0 the scaling logic changed and the new logic is described here.
The scaling parameters in your current config (scaling_threshold, scaling_adjustment, etc.) are no longer used.
The new (and only) scaling parameter is now scaledown_idletime, which is 10 minutes by default.
If your instance is taking more time to be ready (because of the custom ami, the pre and post install scripts) it's likely that it's being terminated by this timeout.
Try to increase the scaledown_idletime value.

Thanks @lukeseawalker
we fixed our AMI startup time and it seems to have fixed this particular issue
will try the scaledown_idletime if we see similar issues again
thanks for the info


Compile Error with VS2022 and C++ 20

Describe the issue
I generated with the following command.
cmake -G "Visual Studio 17 2022" -A x64 -DTARGET_ARCH=WINDOWS -DCMAKE_BUILD_TYPE=Release -DCPP_STANDARD=20 -DCMAKE_CXX_STANDARD=20 -DBUILD_ONLY="dynamodb" -DCMAKE_PREFIX_PATH=../sdk-vs2022 -DCMAKE_INSTALL_PREFIX=../sdk-vs2022 ../aws-sdk-cpp
And, build
msbuild ALL_BUILD.vcxproj -p:Configuration=Release

C7527: Missing "#include <string>"
Error message: aws-sdk-cpp\crt\aws-crt-cpp\include\aws/crt/StringView.h(856,45): error C7527: 'Traits': template parameter name cannot be redeclared.

Solution:
Add "#include <string>"

C2280: Reference a deleted function
Error message: aws-sdk-cpp\aws-cpp-sdk-core\source\utils\crypto\bcrypt\CryptoImpl.cpp(129,21): error C2280: 'std::basic_ostream<char,std::char_traits> &std::operator <<<std::char_traits>(std::basic_ostream<char,std::char_traits> &,const wchar_t *)': attempting to reference a deleted function

Solution:
Add "#include <aws/core/utils/StringUtils.h>"
Change
AWS_LOGSTREAM_ERROR(logTag, "Failed initializing BCryptOpenAlgorithmProvider for " << algorithmName);
to
AWS_LOGSTREAM_ERROR(logTag, "Failed initializing BCryptOpenAlgorithmProvider for " << Aws::Utils::StringUtils::FromWString(algorithmName));

C2593: 'operator <<' is ambiguous
Error message: aws-sdk-cpp\testing-resources\include\aws/external/gtest.h(10356,1): error C2593: 'operator <<' is ambiguous

Solution:
Add function in gtest.h
#if GTEST_LANG_CXX11
inline void PrintTo(std::nullptr_t, ::std::ostream* os) { *os << "(nullptr)"; }
#endif  // GTEST_LANG_CXX11
Reference: https://github.com/google/googletest/pull/1620/commits/f66ab00704cd47e4e63ef6d425ca14b9192aaebb

Steps to Reproduce
No response
Current behavior
No response
AWS CPP SDK version used
1.9.187
compiler and version used
Visual Studio 2022, C++ 20
Operating System and version
Windows 10 21H2 x64

Hi @bspfp ,
Short answer here is, C++20 does introduce some compatibility issues with the SDK, we are working on it but yea for now (if possible) use C++17 or lower.

I have this issue too, waiting for the fix. :)

merged the fix to fix the described use case. If it is reproduce-able under other circumstances, please let us know.

I am struggling with these issues too.
Plz help me someone to fix that.
Thanks !


node[:languages][:ruby] is not updated

Note: I think it is not a problem of this cookbook - rather, it seems to be Chef/Ohai limitation.
node[:languages][:ruby] is set by ohai ruby plugin at the compile time.
rbenv community cookbook makes easy to install rbenv and new ruby versions.
The problem happens when installing rbenv at first. Since there is no rbenv when chef-client starts, Ohai cannot set node[:languages][:ruby]. When chef-client run installs rbenv (creating /etc/profile.d) and new ruby version, still chef-client does not access to them because chef-client run executed without rbenv init. To allow the current chef-client run to access new ruby from rbenv, the cookbook sets PATH variable in initialize_rbenv ruby_block.
At this moment, gem_package resource can install gems in the new ruby from rbenv because it calls 'gem' by default. ref
However node[:languages][:ruby] is still not set. If any other recipes uses node[:languages][:ruby] (either in recipe or attribute), it will be nil.
This happens when I used bluepill cookbook. When running rbenv and bluepill recipies, it installed bluepill gem under rbenv ruby but failed to run blupill service because the bluepill cookbook uses node information to determine ruby bin_dir. ref
I don't know how to deal with this problem. Reloading ohai does not seem to work because it will not change node attributes compiled in other recipes. fnichol/chef-rbenv introduces another LWRP, but it requires updating all other cookbooks to use the LWRP.

from ruby_block

The ruby_block resource is used to execute Ruby code during a chef-client run. Ruby code in the ruby_block resource is evaluated with other resources during convergence, whereas Ruby code outside of a ruby_block resource is evaluated before other resources, as the recipe is compiled.

Chef Ohai: how to use newly installed Ruby with gem_package
OHAI-389: When reloading the hostname plugin via the ohai resource, node['fqdn'] is not updated
fnichol/chef-user #35: Reload ohai passwd after user creation

I'm seeing a similar issue, but what I see is node[:languages][:ruby] is updated on the run that the the profile.d template is created. If that file is present and no changes necessary there is no notification triggered to the ruby_block[initialize_rbenv] resource.  I have a working solution, not at all elegant, perhaps someone can make it more pleasant and or address the issue in the default recipe
ruby_block 'load rbenv' do
  block do
    true
  end
  notifies :create, 'ruby_block[initialize_rbenv]', :immediately
end

ohai 'ruby' do
  subscribes :reload, 'ruby_block[initialize_rbenv]', :immediately
end

Then my recipe that uses bluepill has a ruby_block that subscribes to that ohai resource and updates my bluepill paths.


[LEAGUE LOADER]: Dealing with changed ownership

League Loader
ESPN
Summary
When trying to load multiple seasons of a given league an exception error is raised for _getOwnerByName in LeagueLoader if a different owner is identified for a given team slot. Is there a workaround to allow analysis of leagues with ownership changes?  I dont want to merge changed owners, I would like to keep them separate for statistical purposes.
League Info
No response
Error Logs
No response

Currently there is not a way to load a league with different owners unless you merge them.
Behind the scenes for calculating stats accurately with this change it's a lot more work than I had anticipated and an update will be out at some point to add this functionality.


no module named craigslist

daniel@865c00180794:/opt/wwc/apartment-finder# python scraper.py
Traceback (most recent call last):
File "scraper.py", line 1, in
from craigslist import CraigslistHousing
ImportError: No module named craigslist

you have to install craigslist first.

I tried two methods

Update requirements file and let docker get the lastest and then 2.
launching docker and connecting to the instance. But pip update wasn't
working that way.

what way should I be doing? This is my first time using docker
On Thu, Jun 1, 2017 at 7:53 PM Sicheng Li<EMAIL_ADDRESS>wrote:

you have to install craigslist first.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/VikParuchuri/apartment-finder/issues/20#issuecomment-305667664,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFz0pB4pWud0gEVctKzHrLAG3bQc_NpKks5r_2s1gaJpZM4Nq9TI
.

from within the docker instance I ran:
pip3 install python-craigslist --upgrade
everything is working now


Update request: distrobox <IP_ADDRESS> → <IP_ADDRESS>

Package name:distrobox
Latest released version: <IP_ADDRESS>

Current version on the unstable channel: <IP_ADDRESS>
Current version on the stable/release channel: <IP_ADDRESS>

[X ] Checked the nixpkgs pull requests

Notify maintainers

Note for maintainers: Please tag this issue in your PR.

Add a :+1: reaction to issues you find important.

I attempted to build <IP_ADDRESS> via overrieAttrs and it did not work, For the record
{
  config,
  lib,
  pkgs,
  ...
}:
pkgs.distrobox.overrideAttrs (final: prev: {
  pname = "distrobox";
  version = "<IP_ADDRESS>";
  src = pkgs.fetchFromGitHub {
    owner = "89luca89";
    repo = final.pname;
    rev = final.version;
    hash = "sha256-UWrXpb20IHcwadPpwbhSjvOP1MBXic5ay+nP+OEVQE4=";
  };
})

however, the derivation builds but any attempt to 'distrobox enter' results in an error about entrypoint not being found

just found https://github.com/NixOS/nixpkgs/pull/268800


[Box] Test props to attributes forwarding

~This currently creates invalid HTML. Not sure if desired or not but the behavior should be documented in some form (e.g. a test).~
Box does not forward the props as DOM attributes.

It's a bug.

Turns out I was running the wrong test suite. @material-ui/core/Box actually works as expected. The examples at https://next--material-ui.netlify.com/system/basics/ only create invalid HTML.

@eps1lon It's just a bug in styled-components then?

@eps1lon It's just a bug in styled-components then?

I mean not really. Why should styled-components decide what props to forward and which to block? It's following the same behavior that react changed in v16: Forward every prop to the host instance without a warning instead of issuing a warning and blocking those props.
We should probably show in the examples how this could be avoided.

Why should styled-components decide what props to forward and which to block?

They do it to ease the DX. It's arbitrary, they are using an emotion package actually:  https://github.com/styled-components/styled-components/issues/439.

Why should styled-components decide what props to forward and which to block?

They do it to ease the DX. It's arbitrary, they are using an emotion package actually.

Since this issue is still open I don't think this is expected behavior. Sounds like they do forward everything.

@eps1lon Should we close the pull request?

@eps1lon Should we close the pull request?

I would keep it as a regression test. I'd have to dig more into styled-components and style function but in the current state I wouldn't recommend using our style functions with styled-components because they pollute the DOM.

@eps1lon The problem impacts styled-system too https://codesandbox.io/s/kxwwqkrkmv. I'm not aware of any alternative than to write a custom filter logic like we do in Material-UI/Box.

Well then even better we put a test for this behavior in place. Sounds like this was deliberately implemented but not actually tested.


google image search problem

Hi，I recheck all three search engines, there still works.
Please check your network configuration.


Rephrase the first sentence of this block?

https://github.com/WebOfTrust/ietf-cesr-proof/blob/main/draft-pfeairheller-cesr-proof.md#nested-partial-signatures
CESR Proof Signatures can be used to sign as many portions of a SAD (including the entire SAD) whether the signed subsets are SADs or the self-addressing identifer (SAID) of a SAD.
CESR Proof Signatures can be used to sign as many portions (or 'subsets') of a SAD as needed, including the entire SAD. The signed subsets are either SADs themselves or the multisig part of the / one or more* self-addressing identifers (SAID) of Self Addressing Data (SAD).

I don't have clue, what it needs to be, but you get the idea: pls use shorter sentences and write the concept out a bit more for better understanding ;)

Closed with PR #19


Is there a chance of 'late arrivals' when obtaining data using ActivityEvents REST API?

aka when is the safest I can call the cmdlet/script to export full data for the previous completed UTC day.

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

ID: a0e8bce0-95c1-07f7-d3a3-a1c22bd21f29
Version Independent ID: dddd1e30-4a88-1293-1264-3214cc4b6dc8
Content: Track user activities in Power BI - Power BI
Content Source: powerbi-docs/service-admin-auditing.md
Service: powerbi
Sub-service: powerbi-admin
GitHub Login: @kfollis
Microsoft Alias: kfollis

@olyamusok - Thanks for being patient while I investigated. Yes, it can take up to 24 hours for an event show up. It typically happens much sooner than that. I've added a note to the article to make that clarification.


Move FlutterMain.lookupKeyForAsset() to a non-static place for plugins.

Move FlutterMain.lookupKeyForAsset() to a non-static place for plugins.
We don't want this to be static because it's something that will likely need to be controlled in tests.

Done. A FlutterAssets object is now exposed from the FlutterPluginBinding and exposes asset path retrieval methods.


Update axios dependency due to security vulnerability

Do you want to request a feature or report a bug?
Report an outdated, vulnerable dependency.
What is the current behavior?
axios is not updated to a fixed version for the following advisory ( https://www.npmjs.com/advisories/1594 ) as bundlesize depends on axios ^0.19.0 which prevents npm from updating the dependency to 0.21.1 or higher.
If the current behavior is a bug, please provide the steps to reproduce.
N/A
What is the expected behavior?
axios dependency is updated to >=0.21.1 to depend on a version that fixes the following advisory: https://www.npmjs.com/advisories/1594
If this is a feature request, what is motivation or use case for changing the behavior?
N/A
Please mention other relevant information.
N/A

Additional note, there are two paths bundlesize pulls in axios, one being direct and one being transient:

bundlesize > axios
bundlesize > github-build > axios

Additional note, there are two paths bundlesize pulls in axios, one being direct and one being transient:

bundlesize > axios
bundlesize > github-build > axios

+1

+1

+1

+1

+1

+1

+1

+1

+1

+1

Happy to accept a pull request for both github-build and bundlesize

Happy to accept a pull request for both github-build and bundlesize

Fixed in<EMAIL_ADDRESS>

Fixed in<EMAIL_ADDRESS>

Also fixed in https://github.com/siddharthkp/bundlesize2

Also fixed in https://github.com/siddharthkp/bundlesize2


error message of register_label_attr

Prerequisites

[x] Put an X between the brackets on this line if you have done all of the following:

Check that your issue is not already filed.
Reduce the issue to a minimal, self-contained, reproducible test case. Avoid dependencies to mathlib4 or std4.

Description
register_label_attr has the following behavior.
import Lean.LabelAttribute

register_label_attr rom

/-- error: unknown attribute [rom] -/
#guard_msgs in @[rom]
def womp : 2 + 2 = 4 := by rfl

Expected behavior: The possible solution is displayed in the error message. An error message appears saying, “Since it is not possible to register and use labels in the same file, please consider separating the files." (this message is a example)
Actual behavior: It simply displays “unknown attribute” and does not show possible solutions.
Versions

Lean v4.7.0

Additional Information
see https://leanprover.zulipchat.com/#narrow/stream/113488-general/topic/Lean.20register_labell_attr.20not.20working
Impact
Add :+1: to issues you consider important. If others are impacted by this issue, please ask them to add :+1: to it.

If someone would like to make a PR improving the error message that would be great.

I’ll try to make a PR.


GitHub is HTTPS by default

This reduces unnecessary redirection from http://... to https://... when someone visits this gem's homepage via https://rubygems.org/gems/rspec_junit_formatter or some tools or APIs that use the gem's metadata.

Thansk!


Add Rate Limiting Feature docs

Description:

Add Rate Limiting Feature docs

Update
Had a discussion with Hisan on APK Rate Limiting REST API & CR aspect
Friday, March 24⋅1:40 – 2:30pm


Data from nested lists in richt text is incorrect

Bug Report
Nested lists from the rich text fields are rendering incorrectly.
In Payload:

In my frontend:

This is the incorrect HTML it generates:

And this is what it's supposed to generate (ignore the ::marker or spans, just look at the structure):
.
The
 of the second level would kinda need to be part of the first level; however, it's not. This is the relevant part of the data from the rest API.
{
    "type":"li",
    "children":[
        {
            "text":"A"
        }
    ]
},
{
    "type":"li",
    "children":[
    {
        "type":"ul",
        "children":[
            {
                "type":"li",
                "children":[
                {
                    "text":"B"
                }
                ]
            },
            {
                "type":"li",
                "children":[
                {
                    "type":"ul",
                    "children":[
                        {
                            "type":"li",
                            "children":[
                            {
                                "text":"C"
                            }
                            ]
                        },
                        {
                            "type":"li",
                            "children":[
                            {
                                "text":"C"
                            }
                            ]
                        }
                    ]
                }
                ]
            }
        ]
    }
    ]
},

As you can see, "B" is not part of "A" here. Not sure if that's an issue with what the rest API outputs or with how it's rendered (I just followed what's explained in your docs there).

Hey @AlessioGr — Payload I believe is currently outputting correctly formatted JSON for nested lists — however, browsers have weirdness with nested lists, which is what you're showing in your screenshot. Basically, if you have an li within an li, you'll get two bullets.
The solution is to use CSS, and to do something like this in your HTML serializer, which disables list style if there is an embedded list:
case 'li':
  const hasListChildren = node.children ? node.children.find((child) => child?.type && ['ul', 'ol'].includes(child.type)) : false;
  return (

      <Serialize
        customRenderers={customRenderers}
        overrides={overrides}
        content={node.children}
      />

  );

Hey @AlessioGr — Payload I believe is currently outputting correctly formatted JSON for nested lists — however, browsers have weirdness with nested lists, which is what you're showing in your screenshot. Basically, if you have an li within an li, you'll get two bullets.
The solution is to use CSS, and to do something like this in your HTML serializer, which disables list style if there is an embedded list:
case 'li':
  const hasListChildren = node.children ? node.children.find((child) => child?.type && ['ul', 'ol'].includes(child.type)) : false;
  return (

      <Serialize
        content={node.children}
      />

  );

Hey, that could work visually. Semantically I don't think it's correct too, though. Shouldn't the second-level
 be nested inside an
 in the top-level
? Because right now, they are on the same level.
So instead of:

  A

      B

It should be:

  A

      B

to be semantically correct, shouldn't it?

@jmikrut Do you think the weird behaviour about the indent/outdent feature, that I show in the video below, might be related to this issue :)?

(https://user-images.githubusercontent.com/4012401/188283007-92e96d94-2dc9-4b51-8d4b-2c924c5e1b41.mp4)

@katywings it sure is!
We are going to tackle this issue next. Give us a few days here and I will report back with our progress. Thanks for the video - this is super helpful!

Hey @Stupidism we're going to address this after launch week! Got some other features prioritized over this issue at the moment. But it is indeed on our radar.

When is launch week? a week in a month? @jmikrut

I think this was referred: https://payloadcms.com/blog/launch-week

this resolved yet? @jmikrut

Hallelujah it's a Christmas miracle.
I just wasted about 1,000,000 brain cells on fixing this issue but it is now done and will be released shortly!

🤩🎉

@jmikrut Thank you so much for your work! I wish you an amazzzing Christmas with lots of payload in form of Christmas presents 🥳

Awesome, thank you @jmikrut! Happy holidays to you and everyone 🎄


Update README: flip renamed to reverse

In 037e8de8c58e77bca68bd99e0c38f8142d217231, flip was renamed to
reverse.

Changes Unknown when pulling 7f2309c4146174f32c5b6e95e119f79c5dd61ac2 on reverse into ** on master**.


fix(config): change template file name from config.ts => config.txt

When I run node ace invoke adonis5-cache, following error is generated:
(node:420) UnhandledPromiseRejectionWarning: Error: Template file not found: .../node_modules/adonis5-cache/build/templates/config.txt
Apparently, config.txt file exists as config.ts in templates directory.

@mastermunj released v1.1.2


Events from 27 to 31 of march

Hi, I have an issue with events at the end of march, but not of all years and only in "month" view.
Starting from the input below, I had a wrong result where I put a "-" sign, and a good result where I put a "+" sign:
- "start":new Date(2011, 2, 28),"end":new Date(2011, 2, 28)
- "start":new Date(2012, 2, 28),"end":new Date(2012, 2, 28)
+ "start":new Date(2013, 2, 28),"end":new Date(2013, 2, 28)
+ "start":new Date(2014, 2, 28),"end":new Date(2014, 2, 28)
+ "start":new Date(2015, 2, 28),"end":new Date(2015, 2, 28)
- "start":new Date(2016, 2, 28),"end":new Date(2016, 2, 28)
- "start":new Date(2017, 2, 28),"end":new Date(2017, 2, 28)
- "start":new Date(2018, 2, 28),"end":new Date(2018, 2, 28)
+ "start":new Date(2019, 2, 28),"end":new Date(2019, 2, 28)
+ "start":new Date(2020, 2, 28),"end":new Date(2020, 2, 28)
+ "start":new Date(2021, 2, 28),"end":new Date(2021, 2, 28)
What happens?
Thanks in advance,
Davide

Thanks to solve this issue so fast, I tried the fix on my locale machine.
When did you think to release this fix officially on NPM?
thanks, Davide


BA-756 Replace NPM with Yarn

Add yarn to Dockerfile
Update yarn.lock
Refactor package.json to support yarn workflow
Suppress error message in dev.sh

@sutherlanda please review

Merged.  Thanks Alejandro.


fix(interactions): DefaultPermission should not be a bool ptr

DefaultPermission should not be a bool pointer.
You can no longer pass in true or false, it must be a variable and you need to take the address of it. This absolutely makes no sense.

Additionally, the same will happen when #1026 will be merged. It has *float64 fields to allow json encoder to omit them as well, to not set a max/min value.

Also, @Lucaskyy, you can read more about this behavious here

Ah yeah you're right, it's inconvenient but since there's no other way to do this in Go we'll have to live with it :)

There is a couple of ways, but this one is the easiest, since it requires just one wrapper function.


Adapt data model to EpicDemo #17

Merge changes from diliger/Simplified

@diliger Thanks a lot for helping out with this. Your changes are merged to EpicDemo branch. Please review my changes there.


fix feminine_hygiene terms

Sorry, yesterday I inserted the terms for 'feminine_hygiene' wrongly

No worries, what you did originally was fine too..


Blocking the zeppelin-web build error.

What is this PR for?
This PR is for blocking unnecessary zeppelin-web build errors.
[ERROR] npm WARN package.json<EMAIL_ADDRESS>No license field.
[ERROR] bower perfect-scrollbar extra-resolution Unnecessary resolution: perfect-scrollbar#~0.5.4

What type of PR is it?
Improvement
What is the Jira issue?
https://issues.apache.org/jira/browse/ZEPPELIN-1014
How should this be tested?
You can run mvn clean package -DskipTests in the zeppelin-web folder.
Questions:

Does the licenses files need update? no
Is there breaking changes for older versions? no
Does this needs documentation? no

Is it a build WARNING or an actual error?
Asking as have not seen CI build failure due to this error before

It's not actual error just error messsage.

It's not an ERROR and doesn't break the build.
It's more of a warning/info but when running it is shown with [ERROR] which can be misleading when looking for build errors.
I actually get a few more if I clean the repo like a new clone with: git clean -dxf
(Warning, this will wipe out your notebooks and config files)
[ERROR] npm WARN deprecated<EMAIL_ADDRESS><EMAIL_ADDRESS>is no longer maintained. Upgrade to<EMAIL_ADDRESS>[ERROR] npm WARN deprecated<EMAIL_ADDRESS>graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to<EMAIL_ADDRESS>as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
[ERROR] npm WARN deprecated<EMAIL_ADDRESS>graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to<EMAIL_ADDRESS>as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
[ERROR] npm WARN deprecated<EMAIL_ADDRESS>graceful-fs v3.0.0 and before will fail on node releases >= v7.0. Please update to<EMAIL_ADDRESS>as soon as possible. Use 'npm ls graceful-fs' to find it in the tree.
[ERROR] npm WARN deprecated<EMAIL_ADDRESS>the module is now available as 'css-select'
[ERROR] npm WARN deprecated<EMAIL_ADDRESS>the module is now available as 'css-what'

However some of those errors are more related to deprecated versions and might need more tests if we update the dependencies.
Maybe it should be done in a different PR.

@corneadoug Thank you very much for the clarification!

Looks good! +1

Merging if there is no more discussions

Sounds great, thank you for explanation


Implement Cancel trait for Timer

Timer in stm32f4xx-hal crate implements the Cancel trait.
You may be interested in doing the same for this crate.
Examples:

https://github.com/stm32-rs/stm32f4xx-hal/blob/master/examples/timer-periph.rs
https://github.com/stm32-rs/stm32f4xx-hal/blob/master/examples/timer-syst.rs

Yeah, this would be a nice feature to have!

As I can see this issue might be close because it resolved by PR #50.


Decreased the landing page size #54

Description
Decreased the landing page size by removing the extra elements from the main landing page
There were two nav bars and two info divs . So according to the issue removed them so as to decrease the page size.. Also decreased the size of social icons. And fixed the footer..
Fixes #54
Type of Change:
Changes in index.html and css file
-Bug
Screenshots
Screenshots of the proposed changes compared with the current version of the project

Checklist:

[x] My code follows the style guidelines(Clean Code) of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[x] I have added tests/screenshots(If any) that prove my fix is effective or that my feature works

Hey @Aakansha99 , I've removed the extra elements from the landing page.. Kindly review the changes..

Please resolve this merge conflict

Hey @Aakansha99 , I've resolved the conflicts.. Take a look now..


Remove class constraint on entity type (#65)

Codecov Report

Merging #67 (674f35b) into develop (9b8ee77) will increase coverage by 7.09%.
The diff coverage is 69.48%.

@@             Coverage Diff             @@
##           develop      #67      +/-   ##
===========================================
+ Coverage    79.43%   86.53%   +7.09%
===========================================
  Files          261      259       -2
  Lines        18818    16392    -2426
  Branches      1209     1205       -4
===========================================
- Hits         14949    14185     -764
+ Misses        3598     1938    -1660
+ Partials       271      269       -2

Impacted Files
Coverage Δ

...s/Loader/Implementations/BaseLoaderFieldBuilder.cs
100.00% <ø> (ø)

...uilders/Loader/Implementations/FromBatchBuilder.cs
100.00% <ø> (ø)

...ders/Loader/Implementations/InlineObjectBuilder.cs
96.52% <ø> (ø)

...der/Implementations/SelectAndReferenceToBuilder.cs
55.55% <ø> (ø)

...L/Builders/Loader/Implementations/SelectBuilder.cs
100.00% <ø> (ø)

...ders/MutableLoader/Implementations/FieldBuilder.cs
76.84% <ø> (ø)

.../MutableLoader/Implementations/FromBatchBuilder.cs
52.94% <ø> (ø)

...Loader/Implementations/FromBatchEditableBuilder.cs
81.81% <ø> (ø)

...lementations/FromBatchEnumerableEditableBuilder.cs
15.78% <ø> (ø)

...lementations/FromBatchSelectableEditableBuilder.cs
77.77% <ø> (-11.12%)
:arrow_down:

... and 114 more

Continue to review full report at Codecov.

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


feat(plugins): Plugin binary store service

Refactors front50-s3 config so that the StorageService can decoupled from S3 configuration. Added a new storage service just for plugin binaries that can use different (already available) blob stores. Only wrote an S3 implementation for now since that's all Netflix cares about.
Also wrote a little local filesystem cache that delegates to actual storage services.
Additional steps:

Get the gradle plugin to work with these endpoints
Get the plugin framework to download from front50

For Front50 plugin bootstrapping itself, its plugins will need to be baked into the image, or sourced from an already existing Front50 deployment.

I like the S3 config refactors, much cleaner.


Outlook 365 hangs

Hi Does anyone face the same problem as me. Windows 10 Pro 64bit Version 2004.
After doing this, outlook 365 hangs frequently. Meaning it freezes and shows (Not Responding).
I have to restart the program.
I have tried to modify office in settings meaning repair only. Did not do a full uninstall and reinstall as
I dont want to mess with my emails.
By frequently crashing, I mean at least 3 times a day.
Any ideas?

Hello. I'm using Office 365. I do not belive that enabling/disabling some Win features can cause Outlook freezes. I'll try to find trial Office 365 and make some tests.

Installed Outlook 365. So did you install it first and then applied script or vise versa?

As a last resort I can connect to your PC via TeamViewer to see the bug by myself...

Couldn't reproduced. :( Everything runs very smoothly.

Hi Farag,Nevermind then. If I cannot take it later I may reinstall the whole office. I had my outlook 365 before running your script.
Keep up the good work!
cheers
On Friday, September 25, 2020, 03:06:46 PM GMT+8, Dmitry Nefedov<EMAIL_ADDRESS>wrote:

Couldn't reproduced. :( Everything runs very smoothly.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or unsubscribe.


Navbar UI Enhancement for Better Layout and Alignment

The current navbar layout has a few inconsistencies affecting the overall appearance and usability of the website. Here are the proposed enhancements:

Logo Alignment: The logo on the left side of the navbar appears slightly misaligned. Ensuring it aligns properly with the rest of the elements will enhance visual symmetry.

Spacing Between Tabs: The tabs in the navbar have inconsistent spacing between them, which makes the layout look crowded. Adding uniform padding between each tab will improve readability and aesthetics.

Dark Mode Toggle Position: The dark mode toggle switch is currently placed in the middle of the navbar. For better usability and a cleaner design, it should be moved to the far right, aligning with the "Login" or "Community Support" tab. This change will make the navbar elements appear in a single, orderly line.

Single-Line Layout: All elements in the navbar should ideally align on a single line to maintain a clean and professional look.

Proposed Solution

Adjust logo positioning to align it properly with other navbar items.
Add consistent padding between tabs to ensure equal spacing.
Move the dark mode toggle to the right side of the navbar, aligning it with other elements.
Ensure all navbar elements are vertically centered and aligned in a single line for consistency.

I have seen many navbar issues, and i have mentioned it before for contributors to not create issues regarding navbar and there should be no more navbar issues, so i have closed this issue, if you have any queries, you can join discord server for further updates and communication.
we are not looking for navbar updates for now, as it was done and changes many times before.
So I am closing this issue.
please understand.


我来反馈第一个BUG

使用Docker部署时，我想使用mysql容器名作为数据库地址，但是不支持这个格式，原版是支持的。

后台有好多东西也不能用，验证码图片无法正常显示，系统设置里的所有功能都显示配置不存在，站点目录权限都有递归755

Composer也是有执行权限的
/mcy-shop # echo "application ALL=(ALL) NOPASSWD: /mcy-shop/composer" >> /etc/sudoers
/mcy-shop # cat /etc/sudoers | grep composer
application ALL=(ALL) NOPASSWD: /mcy-shop/composer
/mcy-shop # ps aux | grep php-fpm
   48 root      0:00 php-fpm: master process (/usr/local/etc/php-fpm.conf)
  141 applicat  0:01 php-fpm: pool www
  142 applicat  0:01 php-fpm: pool www
  143 applicat  0:00 php-fpm: pool www
  145 root      0:00 grep php-fpm
/mcy-shop #

PHP扩展也都齐全。
shell_exec函数也是启用的。
/mcy-shop # php -r "echo in_array('shell_exec', explode(',', ini_get('disable_functions'))) ? 'Disabled' : 'Enabled';"
Enabled/mcy-shop #

容器完整日志，基于webdevops/php-nginx:8.1-alpine镜像构建
2024-10-15 22:47:06,833 INFO Included extra file "/opt/docker/etc/supervisor.d/postfix.conf" during parsing
2024-10-15 22:47:06,833 INFO Included extra file "/opt/docker/etc/supervisor.d/ssh.conf" during parsing
2024-10-15 22:47:06,833 INFO Included extra file "/opt/docker/etc/supervisor.d/syslog.conf" during parsing
2024-10-15 22:47:06,833 INFO Set uid to user 0 succeeded
2024-10-15 22:47:06,851 INFO RPC interface 'supervisor' initialized
2024-10-15 22:47:06,852 INFO supervisord started with pid 1
2024-10-15 22:47:07,858 INFO spawned: 'syslogd' with pid 46
2024-10-15 22:47:07,864 INFO spawned: 'nginxd' with pid 47
2024-10-15 22:47:07,870 INFO spawned: 'php-fpmd' with pid 48
2024-10-15 22:47:07,875 INFO spawned: 'crond' with pid 50
-> Executing /opt/docker/bin/service.d/syslog-ng.d//10-init.sh
-> Executing /opt/docker/bin/service.d/nginx.d//10-init.sh
2024-10-15 22:47:07,878 INFO success: nginxd entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-10-15 22:47:07,879 INFO success: php-fpmd entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
2024-10-15 22:47:07,879 INFO success: crond entered RUNNING state, process has stayed up for > than 0 seconds (startsecs)
-> Executing /opt/docker/bin/service.d/php-fpm.d//10-init.sh
Setting php-fpm user to application
-> Executing /opt/docker/bin/service.d/cron.d//10-init.sh
[2024-10-15T22:47:07.914874] WARNING: Your configuration file uses an obsoleted keyword, please update your configuration; keyword='stats_freq', change='Use the stats() block. E.g. stats(freq(1));', location='/etc/syslog-ng/syslog-ng.conf:19:5'
[SYSLOG] syslog-ng[46]: syslog-ng starting up; version='4.7.1'
[15-Oct-2024 22:47:08] NOTICE: fpm is running, pid 48
[15-Oct-2024 22:47:08] NOTICE: ready to handle connections
2024-10-15 22:47:09,231 INFO success: syslogd entered RUNNING state, process has stayed up for > than 1 seconds (startsecs)

The database address format restriction has been removed. It is recommended to try to rebuild it after the next version update.


when reaching the end of a scrollable area, continue scroll the surrounding element. e.g: window

Using a trackpad try to scroll down this example:
https://jsfiddle.net/gbfLazpx/35/
without releasing the trackpad and re-placeing the cursor outside of the ps-container, it is not possible to reach the bottom of the page.
Any regular scrollable element will do just that.
I included a textarea at the bottom of the fiddle to try.  Since there already is a ps-x-reach-end event, it should be possible to replicate this behaviour even without changing anything on the library, right?

When setting wheelPropogation to true the behaviour takes place that you expect. https://jsfiddle.net/DanielApt/7vvycnep/1/

that is perfect.
Thank you

Haha perfect comment right there :wink: !
Feel free to contribute by opening any other issues or by sending a pull request. Thanks!


Implement Helmet Middleware

Is there an existing issue for this?

[X] I have searched the existing issues

Current behavior
We have a middleware service where we do add services that can be used dynamically by the developer during the application development like so:
@provide(App)
export class App extends AppExpress {
    private middleware: IMiddleware;
    private provider: IProvider;

    constructor() {
        super();
        this.middleware = container.get<IMiddleware>(Middleware);
        this.provider = container.get<IProvider>(Provider);
    }

    protected configureServices(): void {
        this.middleware.addBodyParser();
        this.middleware.setErrorHandler();
    }

    protected postServerInitialization(): void {
        if (this.isDevelopment()) {
            this.provider.envValidator.checkAll();
        }
    }

    protected serverShutdown(): void {}
}

The middleware are added in the middleware service as mentioned above as well as it's interfaces implemented here.
The interfaces are the options that can be optionally passed to the middleware.
This task has the objective of implementing the middleware Helmet embedded in the ExpressoTS platform as the other middlewares.
More information here: https://github.com/helmetjs/helmet
Steps to reproduce
N/A
Expected behavior
Helmet as an option in middleware service
Package version
2.2.1
Node.js version

18

In which operating systems have you tested?

[X] macOS
[X] Windows
[X] Linux

Other
No response

@rsaz , I need to implement the interface for helmet right according the options provided in expressjs library.
Right?

@rsaz , I need to implement the interface for helmet according the options provided in expressjs library. Right?

Correct, that's the idea.


Run without warnings

When using approvals in a project, running with Ruby 2.2, a number of warnings were being shown.  The various commits in this PR fix all of the warnings.
There are a couple of commits where I'm concerned about breaking existing functionality, so please review those carefully, notably the commit that fixes the redefinition of the write method in BinaryWriter.  All of the tests are still passing, though.
I really hate having to explicitly initialize an instance variable to nil when it's using the lazy-initialization pattern, but without it, there is a really annoying warning message printed for each individual spec that uses approvals.
See the individual commit comments for more details on each change.
With this version, approvals runs with no warnings in my test rspec project.

Wow, thank you! I am in the middle of moving, and it may take a few days before I can get to this.
I basically wrote this as a hack when I knew very little ruby, and I haven't given proper consideration to many of the choices I made back then... I would be happy to discuss alternative approaches or better interfaces or whatever, if you have any ideas.

No worries, and no rush.  I noticed the warnings the other day and had some time to try to fix them today.
I'm not really clear on how the BinaryWriter is supposed to be used, so I'm not sure I have suggestions for alternative approaches; I haven't studied the whole system that closely.
Good luck with the move!

The changes seem fine to me. It does reveal that the namers use inheritance where (I suspect) composition would be better. It seems the 'name_for_example' part is a class on its own which could be passed to the part with the normalize.
Regarding the binary writer I'm still of the opinion someone should step up and 'adopt' it (add tests, documentation), or it should be removed. It adds costs, without (imo) providing clear advantage.

It does reveal that the namers use inheritance where (I suspect) composition would be better

Yah, back when I wrote this I was experimenting with all sorts of things (singleton, anyone?) and would certainly not solve it the same way again.
I am fine with removing the binary writer if nobody adopts it.


missing fits

while inspecting light curves, I click on some point after 1600 days and get error

It looks like the data is missed from IRSA IPAC, this folder is empty for me right now
https://irsa.ipac.caltech.edu/ibe/data/ztf/products/sci/2022/1217

this error appears not for all objects - https://ztf.snad.space/view/644212300005848 this one works properly

It works again, closing it because we can do nothing with it


chore: update CODEOWNERS

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

v3.0.1
GitHub release

Your semantic-release bot :package::rocket:


Fix deadlock in sqlite Connection.sync

Fix deadlock in sqlite Connection.sync by moving publishers off of "SQLite.Database" queue as described in https://github.com/aws-amplify/amplify-ios/issues/1405
Description of changes:
use subscribe(on:) in the transaction completion handler to move work off of the sqlite synchronous queue to the datastore's work queue.
A receive(on:) before the sink would probably work as well, but it seems like this work should be on the work queue rather than sqlite's queue.
I've validated this fixes my issue, but have no idea how to construct a test this would resolve.
Check points:

[ ] Added new tests to cover change, if needed
[ ] All unit tests pass
[ ] All integration tests pass
[ ] Documentation update for the change if required
[ ] PR title conforms to conventional commit style

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Note to @aws-amplify/ios-team -- we could probably test this by writing a test that sends a bunch of save()s with DispatchQueue.concurrentPerform, where each save callback is matched with an individual expectation. If we don't get all expectations fulfilled within a short time, we're probably hitting the deadlock.

@palpatim can I help get this merged? I'd like to get this into our app to fix issues we're seeing now in production.

@ashiemke Thanks for reporting this issue and submitting this PR.  We are investigating this change and will provide an update soon.

Hi @ashiemke, thanks for opening this PR. I added a PR with an integration test that performs a bunch of save's concurrently, with your fix included: https://github.com/aws-amplify/amplify-ios/pull/1415 . From my investigation, scheduling on the internal queue instead of defaulting to the SQL queue would definitely reduce the consuming the SQL thread. Although I couldn't reproduce the deadlock with the integ test, I don't think it should block this from merging.

this fix is on 1.14.0 branch


Data Update Errors

Version of the custom_component
1.6.0
HA Version: 2024.10.0
Bestway device
Bestway MCU Hardware Version: P4960011
Bestway MCU Software Version: D4H90227
Bestway Protocol Version: 3
Bestway Wi-Fi Hardware Version: 0ESP32C3
Bestway Wi-Fi Software Version: 04X3000B
Describe the bug
Lots of data update errors in the HA logs since installing using this integration. Note: it's working, but noisy.
Logs
Logger: custom_components.bestway.coordinator
Source: custom_components/bestway/coordinator.py:36
integration: Bestway ([documentation](https://github.com/cdpuk/ha-bestway), [issues](https://github.com/cdpuk/ha-bestway/issues))
First occurred: October 3, 2024 at 5:13:51 PM (55 occurrences)
Last logged: 12:27:48 PM

Data update failed
Traceback (most recent call last):
  File "/config/custom_components/bestway/bestway/api.py", line 76, in _raise_for_status
    api_error = await response.json()
                ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/aiohttp_client.py", line 80, in json
    return await super().json(*args, loads=loads, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/client_reqrep.py", line 1243, in json
    raise ContentTypeError(
aiohttp.client_exceptions.ContentTypeError: 502, message='Attempt to decode JSON with unexpected mimetype: text/plain; charset=utf-8', url='https://usapi.gizwits.com/app/bindings'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/config/custom_components/bestway/coordinator.py", line 36, in _async_update_data
    await self.api.refresh_bindings()
  File "/config/custom_components/bestway/bestway/api.py", line 140, in refresh_bindings
    device.device_id: device for device in await self._get_devices()
                                           ^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/bestway/bestway/api.py", line 145, in _get_devices
    api_data = await self._do_get(f"{self._api_root}/app/bindings")
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/bestway/bestway/api.py", line 436, in _do_get
    await _raise_for_status(response)
  File "/config/custom_components/bestway/bestway/api.py", line 78, in _raise_for_status
    response.raise_for_status()
  File "/usr/local/lib/python3.12/site-packages/aiohttp/client_reqrep.py", line 1121, in raise_for_status
    raise ClientResponseError(
aiohttp.client_exceptions.ClientResponseError: 502, message='Bad Gateway', url='https://usapi.gizwits.com/app/bindings'

and
Logger: custom_components.bestway.coordinator
Source: custom_components/bestway/coordinator.py:37
integration: Bestway ([documentation](https://github.com/cdpuk/ha-bestway), [issues](https://github.com/cdpuk/ha-bestway/issues))
First occurred: October 3, 2024 at 5:02:22 PM (46 occurrences)
Last logged: 12:27:19 PM

Data update failed
Traceback (most recent call last):
  File "/config/custom_components/bestway/bestway/api.py", line 76, in _raise_for_status
    api_error = await response.json()
                ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/src/homeassistant/homeassistant/helpers/aiohttp_client.py", line 80, in json
    return await super().json(*args, loads=loads, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/aiohttp/client_reqrep.py", line 1243, in json
    raise ContentTypeError(
aiohttp.client_exceptions.ContentTypeError: 502, message='Attempt to decode JSON with unexpected mimetype: text/plain; charset=utf-8', url='https://usapi.gizwits.com/app/devdata/38AAsh8iG06FZKTTepPBuj/latest'

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/config/custom_components/bestway/coordinator.py", line 37, in _async_update_data
    return await self.api.fetch_data()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/bestway/bestway/api.py", line 168, in fetch_data
    latest_data = await self._do_get(
                  ^^^^^^^^^^^^^^^^^^^
  File "/config/custom_components/bestway/bestway/api.py", line 436, in _do_get
    await _raise_for_status(response)
  File "/config/custom_components/bestway/bestway/api.py", line 78, in _raise_for_status
    response.raise_for_status()
  File "/usr/local/lib/python3.12/site-packages/aiohttp/client_reqrep.py", line 1121, in raise_for_status
    raise ClientResponseError(
aiohttp.client_exceptions.ClientResponseError: 502, message='Bad Gateway', url='https://usapi.gizwits.com/app/devdata/38AAsh8iG06FZKTTepPBuj/latest'

HA Version: 2024.10.0

There's certainly something that can be done to clean up the noise in the logs, however the HTTP 502 error indicates a problem at the Bestway end, which is quite common.
When this happens, how long does it take to recover? Are these just one off issues? Or do they come in waves of minutes, hours, etc?

Closing this for now. Noise should be better as of version 1.6.2. If the 502 responses turn out to be truly one-offs, then perhaps something can be done to improve reliability.

Thanks. I will see if I can correlate the 502s to anything or see if they come in "waves".


Order Return: Clicking back from the browser does not keep the entry input previously entered

Environment Details
Spartacus: epic/order-return-cancel branch
Browser: Chrome
Device: mac
Happens on: http://dev-com-10.accdemo.b2c.ydev.hybris.com:4200/electronics-spa/en/USD
Steps to Reproduce

Login
Place an order
Go to Order History
Click on the order placed
Click on "Request a Return"
Add one item to return
Click on "Continue"
From the Order Return Confirmation Page, click on "Back" button from the browser.

Actual Result
The entry input is not kept.

Tested on dev10, on the epic branch. It works now.


Update Google Sheets plugin to 1.0.0

isolation of python dependencies in a code env
upgrade to use the latest versions of the dependencies
now use Google Sheets API v4 + more restricted oauth scope
no hard coded limits anymore
fix the order of the columns bug
JSON key can be provided with a file path
nicer error messages

Here is a zip of the plugin version 1.0.0:
dss-plugin-googlesheets-1.0.0.zip


cmd/compile: regression in DWARF location lists caused by "issue VarDef only for pointer-ful types"

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

go1.20. Also tip. Also go1.20-a74e5f584e.

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

What did you do?
There appears to have been a regression in the quality of debug information between 1.19 and 1.20. I have bisected it to
a74e5f584 (cmd/compile: issue VarDef only for pointer-ful types), which is https://go-review.googlesource.com/c/go/+/419320.
It seems that this patch caused some local variables to no longer get their location lists emitted (i.e. the information telling debuggers the memory location of the variable in relation to different code locations).
Please consider the following program, which is the simplest repro I could produce:
https://go.dev/play/p/u9iYmn8GXVz
package main

type T struct {
	// The size of the array matters; only 1 element is not enough for the demo.
	x [2]byte
	// Adding a pointer makes the problem go away, which seems to track with a74e5f584e.
	// p *int
}

//go:noinline
func foo() T {
	// t1 has a loclist before a74e5f584e
	var t1, t2 T
	_ = t2 // t2 is necessary for the demo; without it t1 is completely optimized out?
	return t1
}

func main() {
	foo()
}

Before a74e5f584e, the variable t1 has the location information in debug info (pointing to the stack):
llvm-dwarfdump-16 --debug-info --color  --name=t1 --show-children <binary>

0x00015395: DW_TAG_variable
              DW_AT_name        ("t1")
              DW_AT_decl_line   (13)
              DW_AT_type        (0x0000000000001bf4 "main.T")
              DW_AT_location    (0x00000f61:
                 [0x000000000045747c, 0x0000000000457490): DW_OP_fbreg -18)

After the patch though, it's no longer there:
0x00015395: DW_TAG_variable
              DW_AT_name        ("t1")
              DW_AT_decl_line   (13)
              DW_AT_type        (0x0000000000001bf4 "main.T")
              DW_AT_location    (<empty>)

Luckily, the generated machine code for main.foo is not changed by a74e5f584e as far as I can tell, so I am hoping that the code-generation benefits of that patch are not at odds with the quality of the debug info.
The problem does not affect non-optimized builds (`-gcflags="all=-N").
What did you expect to see?
I would like to have the location list for the t1 variable.
What did you see instead?
Location list is missing.

cc @randall77 @dr2chase  - the author and reviewer of a74e5f584e.
Also kindly cc @aarzilli @thanm @neild - folks involved with https://go-review.googlesource.com/c/go/+/433479 which fixed other debug-info problems apparently caused by a74e5f584e.
I would like to timidly volunteer myself to work on a fix if that would be useful, provided that someone knowledgeable would enjoy holding my hand a bit and showing me the ropes in the relevant parts of the compiler. I would like to personally take a longer-term interest in Go's debug info.

The place that was probably expecting the VarDefs is in cmd/compile/internal/ssa/debug.go.
Do you know about using GOSSAFUNC (e.g GOSSAFUNC=foo go build main.go) to generate ssa.html files so you can see what the code looks like?
If you decide that code looks unpleasant, apologies, I touched it last, but I would love to have more people able to work with Go's debug info.

Do you know about using GOSSAFUNC (e.g GOSSAFUNC=foo go build main.go) to generate ssa.html files so you can see what the code looks like?

I didn't know about GOSSAFUNC. Groovy tool!
As expected, I believe it tells us that some VarDefs are gone. In particular, (13) = VarDef <mem> {t1} v6 is gone (in the "before" case, that declaration survives until the end of the compiler passes).

before 7ad92e95b5
before insert phis
b1:-
v1 (?) = InitMem <mem>
v2 (?) = SP <uintptr>
v3 (?) = SB <uintptr>
v4 (?) = LocalAddr <*T> {~r0} v2 v1
v5 (11) = VarDef <mem> {~r0} v1
v6 (11) = Zero <mem> {T} [2] v4 v5
v7 (13) = VarDef <mem> {t1} v6
v8 (13) = LocalAddr <*T> {t1} v2 v7
v9 (13) = Zero <mem> {T} [2] v8 v7
v10 (13) = VarDef <mem> {t2} v9
v11 (13) = LocalAddr <*T> {t2} v2 v10
v12 (13) = Zero <mem> {T} [2] v11 v10
v13 (14) = LocalAddr <*T> {t2} v2 v12
v14 (14) = Load <T> v13 v12
v15 (15) = LocalAddr <*T> {t1} v2 v12
v16 (15) = VarDef <mem> {~r0} v12
v17 (15) = LocalAddr <*T> {~r0} v2 v16
v18 (15) = Move <mem> {T} [2] v17 v15 v16
v20 (15) = LocalAddr <*T> {~r0} v2 v18
v21 (15) = Dereference <T> v20 v18
v19 (15) = MakeResult <T,mem> v21 v18
Ret v19 (+15)

after 7ad92e95b5
before insert phis
b1:-
v1 (?) = InitMem <mem>
v2 (?) = SP <uintptr>
v3 (?) = SB <uintptr>
v4 (?) = LocalAddr <*T> {~r0} v2 v1
v5 (11) = Zero <mem> {T} [2] v4 v1
v6 (13) = LocalAddr <*T> {t1} v2 v5
v7 (13) = Zero <mem> {T} [2] v6 v5
v8 (13) = LocalAddr <*T> {t2} v2 v7
v9 (13) = Zero <mem> {T} [2] v8 v7
v10 (14) = LocalAddr <*T> {t2} v2 v9
v11 (14) = Load <T> v10 v9
v12 (15) = LocalAddr <*T> {t1} v2 v9
v13 (15) = LocalAddr <*T> {~r0} v2 v9
v14 (15) = Move <mem> {T} [2] v13 v12 v9
v16 (15) = LocalAddr <*T> {~r0} v2 v14
v17 (15) = Dereference <T> v16 v14
v15 (15) = MakeResult <T,mem> v17 v14
Ret v15 (+15)

Like you say, cmd/compile/internal/ssa/debug.go seems to look for VarDef.
7ad92e95b5 stated that:

VarDef markers are only used for liveness analysis, and that only runs on pointer-ful variables.

It seems to me that that assessment was perhaps not entirely right?
I gather that 7ad92e95b5 did have some beneficial code generation effects in some cases (right?). My understanding/guess based on @randall77's https://github.com/golang/go/issues/53810#issuecomment-1192755557 is that that inhibiting the generation of VarDefs was simply an expedient way to allow some optimization pass to kick in.
Do you reckon that we could have both the desired optimization and the VarDefs? Or, otherwise, any thoughts on how to get the VarDefs back?

CC @golang/compiler

I can reproduce. Here's a simpler repro:
package main

type T struct {
	a [2]byte
}

//go:noinline
func f(p *T) {
}

func main() {
	var t1 T
	f(&t1)
}

I'm a little bit unclear about what we do want to appear in these lists. At least, when -N is not specified.
The repro requires [2]byte to demonstrate that we got a location list with 1.19 but not with 1.20 or tip.
If we use [1]byte we don't get location lists in any of those versions.
So although I agree that we're missing some debug info that we used to have, it doesn't seem qualitatively different. Location lists are still missing for lots of stuff in either case. (It's only variables with non-SSAable, pointerless types that have changed?)
If we think that location lists are important for optimized code, we should probably figure out a way to make them available generally. At least, for things that don't get totally optimized away.

I take some of that back, for my repro using [1]byte 1.19.4 still generates a location list for t1.

(But the original repro does not.)

So although I agree that we're missing some debug info that we used to have, it doesn't seem qualitatively different. Location lists are still missing for lots of stuff in either case. (It's only variables with non-SSAable, pointerless types that have changed?)
If we think that location lists are important for optimized code, we should probably figure out a way to make them available generally. At least, for things that don't get totally optimized away.

Debug info for optimized code in general, and variable location lists in particular, are quite important for debugging optimized code in some of the trickiest, production-only investigations. At least that's my conclusion after the past years of working on CockroachDB. As of recently, I'm working on tooling for making better use of this debug info, and hopefully bringing production debugging to more people. So, I personally am very interested in the quality of this info. I'd like to personally contribute to it on the compiler side, if opportunity presents itself. So if you have thoughts on other places where the compiler doesn't maintain the right info that could be improved, and if a newcomer like me can help, I'll always be interested.

It's only variables with non-SSAable, pointerless types that have changed?

This particular regression seems significant to me; I've immediately gotten bitten by it when upgrading to go1.20. I think maybe every local var of struct type that doesn't contain a pointer is affected?

I think maybe every local var of struct type that doesn't contain a pointer is affected?

I think it would only be ones that are not SSAable for some reason. They are large, contain somewhere an array of length > 1, or have their address taken. Otherwise such structs would be broken up into pieces and put in registers.


How to open .h5 file in Python?

I tried teachable machine image classification model. I has downloaded (.h5) model file of the image model I built using "Export Model>tensorflow>keras". I want to view the code in Pycharm IDE. How to open the (.h5) model in python. Please advice.

Checkout the snippet added in #44 for an overview on how to use the keras .h5 model in your python projects.


Implement IMA policy conversion script

This script should serve as an upgrade path for the eventual IMA policy format overhaul, as laid out in Keylime enhancement https://github.com/keylime/enhancements/pull/71.
Note that this is NOT a complete implementation of the IMA policy format overhaul; it merely produces valid-formatted IMA policies according to the enhancement.
Signed-off-by: Mark Bestavros<EMAIL_ADDRESS>

An update for those following: I've implemented support for signing Keylime policies in the DSSE format (spec, for reference: https://github.com/secure-systems-lab/dsse).
I'm also marking this as a draft, since it currently relies on a Git dependency for in-toto's downstream securesystemslib implementation. When DSSE support is upstreamed, this dependency can be made a normal pip dependency and will then be eligible for merge.

Codecov Report

Merging #1113 (568c53b) into master (f969d39) will increase coverage by 0.00%.
The diff coverage is 100.00%.

Additional details and impacted files

Flag
Coverage Δ

packit-e2e
72.42% <100.00%> (+<0.01%)
:arrow_up:

testsuite
54.15% <100.00%> (+0.01%)
:arrow_up:

unittests
14.64% <100.00%> (+0.02%)
:arrow_up:

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

Impacted Files
Coverage Δ

keylime/ima/ima.py
72.11% <100.00%> (+0.23%)
:arrow_up:

@mpeters @THS-on I've dropped DSSE signing for now, since the status of required dependencies for that feature is in flux. The conversion script should be ready for review - please let me know your feedback!

@mpeters Addressed your feedback; ready for another review.

I think it is similar to the config script also a good idea to put this script under keylime/cmd because it is an official part of Keylime.
In general it LGTM, but I still need to test it. Can you add some unit tests to that script?

@THS-on I implemented a basic test suite. Let me know how it looks.

/packit retest-failed

I would say this is nearly ready to go. Following changes I think are still necessary:

drop changes to the create_allowlist script (currently not really useful)
Add the script entry point to https://github.com/keylime/keylime/blob/master/setup.cfg
squash commits together: 1x for script, 1x for the tests, 1x for the changes to ima.py

@THS-on I've made your requested changes and squashed/tidied up my commits - there are now just three commits, one for the reference IMA policy in ima.py, one for the conversion script, and one for the test suite.
@mpeters Would love for you to have another look - anything else you think is needed before merge?

I'm assuming the codecov failure is spurious - @mpeters @THS-on how would I re-run that?


Add push notifications for watched repos

It would be awesome to get push notifications for my watched repos. This is something that all other GitHub apps either don't have or are a paid feature.
I could definitely work on at least the iOS push notifications, though Android doesn't seem to be much different.
This might help: https://medium.com/differential/how-to-setup-push-notifications-in-react-native-ios-android-30ea0131355e

I think this is an outstanding idea, please feel free to go ahead trying it with iOS. I can (or anybody else with Android) will be happy to help with Android if they happen to be different.
So push notifications for watched repos is a great start. Definitely worth exploring push notifications for other things (such as a user has followed you for example) but I think that's just cherries on top. Definitely worth getting watched repo notifications up and running first.

Best way to go about this IMO is to poll each user's notifications feed every ~2 minutes and send any new notifications to OneSignal. Tell me if anyone has any better ideas tho!

Just contacted GitHub about the possibility of adding webhooks for users as that would make this all a lot easier.

Something else I'm looking into is setting up Firebase Cloud Function on a 2-5 minute cron job. We get 125,000 calls/month for free, which would be 2.89 calls/minute.
Here's my thinking for the flow of how this would work:

User enables push notifications in settings.

Username and FCM token are saved to Firebase.
In addition, one of the following is stored (still need to decide on which one makes more sense):

The user's private RSS feed (https://github.com/andrewda.private.atom?token=abc123).
The user's access token for use with the notification feed API.

Cron job polls ever 2 minutes for new notifications.

If need be, we can create several cron jobs that split up the work. First job takes users 1-10, second job takes users 11-20, third job takes 21-30.

Cron job sends push notification (using the FCM token saved above) whenever it finds a new notification.

I think this is the best we can do until GitHub adds user event webhooks.

That sounds amazing @andrewda 🙌  I'm always impressed with how much Firebase provides for free. Even though costs can get steep with priced plans, they always have awesome free starting points. Appreciate you looking into this.
Couple of things I'm curious about:

What's an FCM token? (forgive me if this is a foolish question :P)
Yep definitely something we need to decide. If the user's private RSS feed will work that might definitely be a more secure route - storing the user's access token can definitely bring up some security concerns (and it's something we'll need to declare ino ur privacy policy). We'll definitely chat about this.

For 2 & 3 I like the sound of that 👍

FCM token = Firebase Cloud Messaging token - it identifies the user so we can send that specific user notifications in the future.
Totally agree about the RSS feed. The only problem with it is that we would have to parse the RSS and decide what notifications to send to the user ourselves, as opposed to just going off of what the user already gets notifications about in their notification feed.

Hmm you're right it very well might be easier to leverage the user's access token in that case - let's decide at that point if storing the user token in a secure server is a viable option

It's also completely up to the user whether their token would be stored, and we would make it clear that the token would be immediately when the user disables push notifications.

Is there a way that we can get a separate token with only the notification reading scope? I think it would be fine if that only required another sign in from the user.

I think that's a great idea. We may be able to leverage Basic Auth specifically creating a scope for notification and then clearing it when they disable again. If this happens to require an additional sign in, I'm okay with that as long as we briefly explain to the user why it's necessary (for improved security and so forth)

This feature would be golden! 🥇

Any update on this feature? Would love it implemented within the app

Hallo @housseindjirdeh and @andrewda , I am using GitPoint for a few weeks now and it's a pleasure to work with this app! Is there any update on this push notification feature? Have to agree with @henrikra: it would be golden! =:-)

Me too! Initially, I thought I had missed out on some setting but only later realized that push notifications are not a feature of the app yet. Any updates? It would be awesome!

Unfortunately I've been busy lately and have been away from the project for a while, but I'm looking to get back into GitPoint soon and will continue looking into a way to make notifications work!

Same here, I've been a bit occupied this past while unfortunately and most of the maintainers have :(
But I'm also looking to get back into the swing of things in the coming weeks. If this is a priority, I can work on this first as well :)

I just read this article, and I wonder if we could do something similar to send push notifications?
https://towardsdatascience.com/using-gitlabs-ci-for-periodic-data-mining-b3cc314ecd85


the status of two store are abnormal and some tikv oom while run sysbench

Bug Report

What version of TiKV are you using?
v5.2.1
What operating system and CPU are you using?
k8s 3PD、2TiDB、4TiKV
8 Core 16G mem
Steps to reproduce
case:TiKVWorkloadStress005（do not scale TiKV）
run sysbench prepare
threads=64
tables=512
What did you expect?
all store are normal
What did happened?
the status of two store are abnormal while run sysbench

some tikv oom

/type bug

/severity major

/assign hicqu

It can't be continued until we improve TiKV heap profiling. So let's close it now.


missing /rchash endpoint in openapi files

Can't seem to find any /rchash endpoint info in the openapi yaml files.

I get 404 if I tried to trigger the test:
 curl -X GET http://localhost:1633/rchash/10/randomstring
#OR
 curl -X GET http://localhost:1635/rchash/10/randomstring

Is this the same issue?


QuicXplo 1.0.2: File gets corrupted when a duplicate copy is pasted in the same folder

Expected behavior
On copying a file, and trying to paste the duplicate in the same folder as the original, the new duplicate should be renamed before getting pasted. Or a dialogue shows that same file name exists in the folder.
Actual behavior
The existing file gets corrupted and becomes 0byte when a duplicate copy is being pasted in the same folder as the original, having the same file name.
how to reproduce

Open device storage and navigate to a file of choice (use a test file because it would get corrupted)
Tap and hold to select the file
Click copy from the pop-up menu
Select directory and folder to paste file in (the same folder as the original file copied)
Tap the paste icon to paste the file
Check the file property and see it corrupted.

Device: Tecno K7
App version: 1.0.2
Operating system: Android Nougat 7.0

recording of bug
https://youtu.be/YRmIXJHSfmo

I will check and fix it as soon as possible


BE: add GDG Davao as a special email in the Events Service

In backend/usecase/email_usecase.py add the GDG Davao email details in the __sender_name_map.
This makes sure that there will be no SPARCS related content in the emails sent.
Deploy changes to dev and test if everything else is still working.
Attach a recording to this ticket after code approval as proof.
Inform Arnel if you are about to begin the task for AWS Credentials

PE merged @jcomrade . Please do an end-to-end test on dev environment. Attach a recording to this ticket that its functional. Once done, please move ticket to Done. Thanks!

https://github.com/user-attachments/assets/3c50199f-c20e-4960-b420-6ff5b2df1c58

https://github.com/user-attachments/assets/71aee9a7-69f8-4cd2-9261-4dcf02f9d088
Sampe event with random Konfhub Credentails
Expected output: No email recieved

https://github.com/user-attachments/assets/22250cbb-50bd-4061-9e48-996744105ac9
Sample Event creation using Special Email
Expected Output: Email Received without SPARCS related content in the email body


Release v0.2.8

Documentation

Added link to the PyPI project on the Sphinx site (#410)
Added link shortcuts for MCNP manual, and github issues and pull requests (#417).
Added discussion of MCNP output files to FAQ (#400).
Updated MCNP 6.3 manual link to point to OSTI/DOI (#424).

CI/CD

Fixed project metadata for author to show up correctly on PyPI (#408)
Removed automated versioning from CI/CD, and simplified deploy process (#418)

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 98.223%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
5750

Relevant Lines:
5854

💛  - Coveralls

We can complete the review and approve this now, I won't merge and deploy this until we get the montepy.org custom domain working.

I have actually removed the need for reviews for this as I don't think two checks of the same code is worthwhile use of resources.


Make Topology-Aware Scheduling compatible with cohorts and preemption

What would you like to be added:
Make TAS compatible with cohorts and preemption.
Why is this needed:
Currently, TAS does not work when cohorts or preemption are used. In that case the CQ is marked as inactive (see https://github.com/kubernetes-sigs/kueue/tree/main/keps/2724-topology-aware-scheduling#alpha).
Completion requirements:
This enhancement requires the following artifacts:

[ ] Design doc
[ ] API change
[ ] Docs update

The artifacts should be linked in subsequent comments.

cc @mwielgus @mwysokin @tenzen-y


fs: decouples sysfs from fs.FS and consolidates guest path logic

This decouples sysfs.FS from fs.FS by introducing a temporary type FSHolder, which will be removed when we top-level FSConfig (shortly).
This further reduces complexity by consolidating guest path configuration into the only type that uses it: CompositeFS.
The next PR will add FSConfig and be a lot smaller due to extracting this stuff now.

I will fix the windows error tomorrow