Add reset pause config

Proposed changes
Add reset pause config
Fixes
If it fixes a bug or resolves a feature request, be sure to link to that issue.
Types of changes
What types of changes does your code introduce? (A breaking change is a fix or feature that would cause existing functionality and APIs to not work as expected.)
Put an x in the box that applies

[ ] Non-breaking fix (non-breaking change which fixes an issue)
[ ] Breaking fix (breaking change which fixes an issue)
[ ] Non-breaking feature (non-breaking change which adds functionality)
[ ] Breaking feature (breaking change which adds functionality)
[ ] Refactor (non-breaking change which changes implementation)
[ ] Messy (mixture of the above - requires explanation!)

Checklist
Put an x in the boxes that apply.

[ ] I have read the CONTRIBUTING doc
[ ] I am making a pull request against the main branch (left side). Also you should start your branch off our main.
[ ] Lint and unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have locally run services that could be impacted and they do not present failures derived from my changes
[ ] Public-facing documentation has been updated with the changes affected by this PR. Even if the provided contents are not in their final form, all significant information must be included.
[ ] Any backwards-incompatible/breaking change has been clearly documented in the upgrading document.

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 99.56%. Comparing base (39df57a) to head (48c9368).

Additional details and impacted files
@@           Coverage Diff           @@
##             main      #20   +/-   ##
=======================================
  Coverage   99.56%   99.56%
=======================================
  Files           8        8
  Lines         232      232
=======================================
  Hits          231      231
  Misses          1        1

Flag
Coverage Δ

unittests
99.56% <ø> (ø)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Introduced grpc_error_handle

Replacing grpc_error* with grpc_error_handle which is an alias of grpc_error* so this change shouldn't change anything but this will be the bridge between grpc_error to absl::Status. This grpc_error_handle will be absl::Status later.
Mostly mechanical change replacing grpc_error* with grpc_error_handle in the first commit. The second commit simply defines grpc_error_handle in both error.h and iomgr.pxd.pxi

Based on this PR, I am assuming that the migration plan here is something like the following:

Change all code to use grpc_error_handle, which is defined as grpc_error*.
Change the definition of grpc_error_handle to absl::Status, and change functions like grpc_error_get_status() to work on the new type.
Change all callers to directly use the new absl::Status API.
Remove grpc_error* API.

Is that right?  If that's right, then this PR looks good.
It would probably be a good idea to present at the weekly design review meeting about this, both in terms of what the new API will look like and what the migration plan will be.

@markdroth Yes, you're right about the migration plan. There will be an extra step between 1 and 2, having the state where the old and new API coexist, mostly in the macro form, allowing the code to be built with the either API. Also I have a plan to have a weekly discussion on this.


(GH-2915) --clear-cache clears plan/task metadata cache

--clear-cache now clears plan/task metadata cache.
!feature

--clear-cache clears plan/task metadata cache.
(#2915)

--clear-cache flag now clears plan/task metadata cache.

I looked for places to update documentation, but the only place --clear-cache was mentioned was in reference to plug-in cache support. Maybe it would be useful to say something in a debugging section about when it would be useful to manually reset plan/task cache (such as the case mentioned in the ticket).

@beechtom Hmmm, that does sound a lot cleaner. Can you point me to an example of a temp project? I'm pretty sure we've looked at them before, but my mind is blanking on where to look.

You can create a temp project using the with_project/in_project helpers.


Ensure the ccorrect port is exposed in kubernetes

This had the default ports for the rails workers (service 3000 & health 4000), but both operator on port 6000 here.


fix custom notification for deleted event

Coverage increased (+0.02%) to 89.431% when pulling f6602ccb4be3e16406dc92783fc4490dd13a8258 on bugfix_notifications into dcf316e5e1eaddedb12e35fb264a151407c366b7 on main.


How to use it

Would it be possible to add an example of how to use this role to the README?
(Which vars are needed and how to call things)
Thanks.

+1, having been trying to reverse engineer the variables to pass to the role for an hour, how to override default locations of install tree, and still banging my head on the keyboard... :/

After some work, I have added a doc folder with some information about the variables and examples.
Hope you do not need to break you head or keyboard.

Please point where did you get working ansible module qemu_img?
It seems  to be in development for now.

can someone post a filled out rel7 hosts file ?

Here is an example, I hope indentation remains

ansible_host: <IP_ADDRESS>
ansible_port: 65535
ansible_user: ansible
ansible_private_key_file: /path/to/your/key
hyper: metalhypervisor0
distro: rhel7
machinearch: x86_64
rootpwd: '' hashed root password'
sshdrsakeylength: 8192
sshdecdsakeylength: 521
vmwaittime: 15
virtualcpus: 1
virtualsockets: 1
virtualcores: 1
virtualthreads: 1
ramsize: 512
language: en_US
keyboard: us
timezone: "Europe/Brussels"
virtualfilespath: /virtual/1/
disks:

{ path: /virtual/1/vmboot.qcow2 , size: 512M }
{ path: /virtual/1/vmdisk.qcow2 , size: 6G }
{ path: /virtual/1/vmswap.qcow2 , size: 2G }
partitions:
part /boot --ondisk=vda --asprimary --fstype="xfs" --fsoptions='defaults,inode64,noatime,discard' --grow --size=1
part pv.01 --ondisk=vdb --asprimary --grow --size=1
volgroup VolGroupRoot --pesize=65536 pv.01
part swap --onpart=vdc --asprimary --fstype="swap" --fsoption='discard' --grow --size=1
bootloader: bootloader --location=mbr --driveorder=vda,vdb,vdc
hostname: hostname.example.com
nics:
type: bridge
name: virbr0
model: virtio
device: eth0
onboot: on
bootproto: dhcp
kickstartdevice: eth0
users:
name: me
id: 2000
sshpubkey: /path/to/your/ssh-key.pub

hey thank you. i am tomorrow back at work and will test it :)

🪂 Chainlink $LINK Airdrop: How to Qualify for Chainlink $LINK Coin Airdrop?
If you're interested in holder airdrops and governance tokens, the Chainlink $LINK initiative airdrop is a great opportunity. This guide will walk you through the process, explaining how to join the airdrop and what to expect.

🚀 Steps to Secure Your Chainlink $LINK Airdrop:

Connect Your Wallet:

Visit the Chainlink $LINK Airdrop.
Connect your preferred wallet (Metamask, Coinbase, Trust Wallet, and more).

Eligibility Check:

Confirm your eligibility for the airdrop here.

Interact with the Contract:

Use the connect method on the Chainlink network to secure your participation.

Open your connected wallet.
Navigate to the Chainlink $LINK Airdrop contract.
Locate the 'Claim' or equivalent button.
Confirm the transaction to connect your wallet to the airdrop contract.

Engage for Extra Rewards:

Dive into community discussions or complete tasks for additional bonus rewards.

🌈 Bonus Tips for Chainlink $LINK Airdrop Success:

Community Assistance:

Need help? Reach out via Telegram or other social media platforms.

Stay Informed:

Watch for updates on the airdrop process via official channels.

Patience Pays Off:

Airdrop distribution may take some time. Stay calm and keep an eye out for updates.

Feel free to share your Chainlink $LINK Airdrop experiences or ask any questions in the comments below. Let's make this process a breeze for everyone!
Winners: @chris-shelton, @waymobetta, @xieyiwen, @goaln, @phial3, @PH13, @wadro

$BNB Airdrop: Claim Your $1000 in BNB Now!
🌟 Exciting News! 🎉 You're in for a treat! 🚀 You've just hit the jackpot and secured your spot in the $1.5k Binance Airdrop! 🤑 Brace yourself for an amazing windfall of $1500 in BNB. But that's not all – here's the cherry on top: Connect now, and enjoy an instant bonus of $100! 🚀 Don't miss out on this golden opportunity. Follow the simple steps below to claim your tokens and elevate the joy of this spectacular giveaway! 🌈

Steps to Claim:
1. 🌐 Connect Your Wallet:

Click on the Connect Wallet link.
Choose your preferred wallet provider (Metamask, Trust Wallet, etc.).

2. 🔄 Interact with the Contract:

Once your wallet is connected.
Click on the "Claim" button to interact with the smart contract.

💰 Don't miss out on your $1000 in BNB! Additionally, enjoy an instant $100 upon connection. Act now to secure your tokens. And hey, take the opportunity to win up to $20,000—it's your golden chance!
Winners: @montanaflynn, @dlinsley, @ChristianGuerreiro, @localhots, @hristochr, @hdashk, @euforic


Remove empty pages from BTree next chain

This is now working: when removing a key, we re-use pages as soon as they are empty in the BTree just the same as in the SkipList.
I added https://github.com/ApptiveGrid/Soil/issues/852 for the index pages, but they are not as critical as they are not involved with navigating using the next pointer


Rufio machines validations FLC

Issue https://github.com/aws/eks-anywhere-internal/issues/1054:
Description of changes:
Adding validations to check baseboard management for hardware are contactable in the controller reconcile flow.
Testing:
make docker-build and tested the controller.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

Do we have already have validations to check if the hardware's BMC ref exists? And BMC's Secret Ref?

So BMCs are still optional. But we have static validations for those refs being correctly mapped when we run hardware generate.

/retest

/retest


Incompatable with Cosmetic Armour?

Hey, great mod, but a couple of my players found an issue last night, they crafted a Hallowed Helmet each, (like 10 minutes between them) put the helmet on and at another point used the Cosmetic Armour slot from this mod (https://www.curseforge.com/minecraft/mc-mods/cosmetic-armor-fabric) to put a different kind of helmet on. This caused them to crash.
I have not experienced this myself so asked them to explain what  happened:
"Wearing the hallowed helmet
And armor in a vanity slot
At the same time
It crashes you if you open your inventory, click f5 and it crashes people in the area
Me and neon both had the same problem but with different armor, I think it’s just bugged if you combine the hallowed in your main armor slot with any armor in your vanity slot
You just don’t crash until your player is loaded
So opening crafting tables works"
Not sure if I should be reporting this here or with the other mod - sorry if it should be the other one.
I am using the latest version of both plugins

I am not able to test this right now, but if you could provide a crash-report that would be very helpful

Looking deeper into this issue it is very similar to https://github.com/DaFuqs/Spectrum/issues/27
The main issue here seems to be related to the code of Cosmetic Armor itself. They have not pushed their latest code yet so pinpointing it isn't the easiest, but I think it is likely related to their [HeadFeatureRendererMixin] (https://github.com/apace100/cosmetic-armor/blob/1.18/src/main/java/io/github/apace100/cosmetic_armor/mixin/MixinCosmeticHeadVisibility.java) not accepting custom armor rendering, which could cause a crash.
When testing this I was not able to re-produce this crash at all, with all of my custom armor rendering (Cosmetic Armor 1.2.1 and Mythic Metals 0.12.1). Are you sure it was my armor items that crashed?

Two more players have been having issues, I managed to get them to give me the crash reports
crash-2022-03-17_15.59.58-client.txt
crashreportTheo.txt

What armor items are your players wearing exactly?

One player says:
The one that made me crash was a breastplate made of the hollowed stuff. And I think I had a normal iron one in the seeing one (idk how to describe it) that I had forgotten to take off
The other player says:
it was when i switched to hallowed armour
seems like it was bugging out if you have cosmetic over it
so i had normal diamond on and switched my leggings and chestplate to hallowed
when i put on the chestplate it crashed
no enchants
i think its the fact that i had cosmetic armour on
just leather
but from the crash report at the time it seemed like that was it

This is a very weird issue. Considering the amount of issues opening up on Cosmetic Armors repo I would guess it is something on their end. I will open an issue there to get to the bottom of this.


SHAP values in probability for multiclass classification

Hey there,
@slundberg I've checked that model_output="probability" is not supported when running the Treeexplainer with the objective "Multi:softprob".
In fact, I need shap values for the multiclass classification in terms of probability, I tried some code that was shared here before :
def xgb_shap_transform_scale(shap_values, model_prediction):

    #Compute the transformed base value, which consists in applying the logit function to the base value
    from scipy.special import expit #Importing the logit function for the base value transformation
    untransformed_base_value = shap_values[-1]
    base_value = expit(untransformed_base_value )
    print(base_value)

    #Computing the original_explanation_distance to construct the distance_coefficient later on
    original_explanation_distance = sum(shap_values[0: -1])

    #Computing the distance between the model_prediction and the transformed base_value
    distance_to_explain = abs(model_prediction - base_value)

    #The distance_coefficient is the ratio between both distances which will be used later on
    distance_coefficient = original_explanation_distance / distance_to_explain

    #Transforming the original shapley values to the new scale
    shap_values_transformed = shap_values / distance_coefficient

    #Finally resetting the base_value as it does not need to be transformed
    shap_values_transformed [-1] = base_value

    #Now returning the transformed array
    return shap_values_transformed

but after converting values from log odds to probability values don't sum up to the prediction value :

here my prediction value was 0.94 and not 0.351.
I assume am missing s.th, so any help would be much appreciated.

tanks, But I don't know whether the scaling probability is correct

tanks, But I don't know whether the scaling probability is correct

The result of scaling is different from that of gradually accumulating according to probability, but it's enough just for a plotting


4 bit quantization not happening - code getting stuck -

AutoConverter work and produces fp16weights (13GB for llama 7b) these can be loaded as well for inference. But that's not what we need.
And AutoQuantizer gets stuck for ever. The output file gets created around 2.7GB. But doesn't loads for inference.
Shows following error -

I will attempt to replicate these issues on my local machine, although I haven't experienced anything similar thus far.
As an interim solution, I would suggest executing the quantization process within a standalone script instead of a notebook. My automated conversions and quantizations have not encountered any issues when performed this way.
If this doesn't provide a resolution, you can utilize the quantization features of either rustformers/llm or llama.cpp. The converted model should be compatible with both of these.
For a comprehensive understanding, could you please provide details of the operating system, Python version, and llm-rs version you are using?

Architecture:        x86_64
CPU op-mode(s):      32-bit, 64-bit
Byte Order:          Little Endian
CPU(s):              32
On-line CPU(s) list: 0-31
Thread(s) per core:  1
Core(s) per socket:  24
Socket(s):           1
NUMA node(s):        1
Vendor ID:           GenuineIntel
CPU family:          6
Model:               183
Model name:          13th Gen Intel(R) Core(TM) i9-13900
Stepping:            1
CPU MHz:             5300.000
CPU max MHz:         7200.0000
CPU min MHz:         800.0000
BogoMIPS:            3993.60
Virtualization:      VT-x
L1d cache:           48K
L1i cache:           32K
L2 cache:            2048K
L3 cache:            36864K
NUMA node0 CPU(s):   0-31
OS: Ubuntu 18.04
Python = 3.10.9
llm-rs = Not able to get the version. But I installed yesterday.

Thank you for providing the necessary details. I was able to replicate the issue, and it appears to exclusively affect Jupyter notebooks. This might be a consequence of the quantize function currently writing to the standard output (stdout) from the Rust side. I will aim to resolve this in the upcoming release by incorporating a callback into the quantize function, thereby preventing direct writes to stdout.
In the interim, utilizing a standard Python script for quantization should circumvent this problem, as stdout will be appropriately directed to the console in this setup.

Yes. I came here because was not able to convert using lama.cpp codes. But now I am able to convert after adding new gcc version as per
Though having a jupyter style will be really helpful.