[EVM] Make metagraph data available as precompile

Add a new precompile contract that will expose following state to EVM in the following methods. All methods should accept netuid as a parameter. Also, all methods except get get_netuid_count accept uid parameter.

Method
State returned

get_uid_count
SubnetworkN

get_stake
Total stake of the neuron in Tao

get_rank
Rank score of the neuron

get_trust
Trust score assigned to the neuron by other neurons

get_consensus
Consensus score of the neuron

get_incentive
Incentive score representing the neuron's incentive alignment

get_dividends
Dividends earned by the neuron

get_emission
Emission received by the neuron (with 18 decimals)

get_vtrust
Validator trust score indicating the network's trust in the neuron as a validator

get_validator_status
Validator status of the neuron

get_last_updated
Number of blocks since the neuron's last update

get_is_active
Activity status of the neuron

get_axon
Network endpoint information of the neuron

get_hotkey
Hotkey (public key as bytes32) of the neuron

get_coldkey
Coldkey (public key as bytes32) of the neuron

Acceptance Criteria:

[x] Precompile implemented
[x] ABI and sol files added
[x] e2e JS tests implemented for each method

We also need (either a second precompile, etc.) access to the current subnets to verify a subnet is still registered/when it deregisters.

Test

subnet is registered interface is added.


eslint-import-resolver-node can't handle "exports"

🐛 Bug Report
"exports" field seems to be ignored by eslint-import-resolver-node, resulting with unexpected error thrown by import/no-unresolved rule even though Node is capable of resolving the paths.
https://nodejs.org/api/esm.html#esm_package_entry_points
To Reproduce
Steps to reproduce the behavior:
I have a simple utils package in my workspace, that's shaped like this:
/dist
  array.js
  …
/src
  array.js
  …
package.json

package.json:
{
  "name": "@my-org/utils",
  "version": "1.0.0",
  "exports": {
    "./array": "./dist/array.js",
    "./boolean": "./dist/boolean.js",
    "./math": "./dist/math.js",
    "./number": "./dist/number.js",
    "./object": "./dist/object.js",
    "./promise": "./dist/promise.js",
    "./string": "./dist/string.js"
  }
}

This allows me to use it in my main project by importing utils like this:
import { min } from '@my-org/utils/math'

This works both in native ES modules environment in Node 14, and in code transpiled by Babel. But this line is flagged by import/no-unresolved.
Expected behavior
"exports" to be respected and understood by eslint-import-resolver
Link to repo
https://github.com/wojtekmaj/resolve-exports-issue
envinfo
  System:
    OS: macOS 11.0
    CPU: (8) x64 Intel(R) Core(TM) i5-8259U CPU @ 2.30GHz
  Binaries:
    Node: 14.5.0 - /usr/local/bin/node
    Yarn: 2.1.1 - /usr/local/bin/yarn
    npm: 6.14.5 - /usr/local/bin/npm

Duplicate of #1868.


chore(main): release 1.2.1

:robot: I have created a release beep boop
1.2.1 (2022-12-31)
Bug Fixes

build: use release-specific token (4fbcaad)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/Falklian/cloudflare-ddns/releases/tag/v1.2.1 :sunflower:


Simplifying non-square meshes

Great library @mourner. I've been adapting this to simplify non-square meshes, by buffering the east and southern edges with filler values. This forms a bigger square, whatever the next larger 2^n +1 integer may be (a 225x500 mesh becomes 513x513).
To keep the algorithm from simplifying away vertices on the real edge, I fill the placeholder values with a constant, extremely low/high elevation, and then trim them away:

Two questions:

is this worth adding into core functionality? I'm curious if we can further optimize by skipping simplification on values that are known to be placeholders.

this strategy forms an interesting bandana pattern, where the eastern and southern edges keep a really fine detail (probably finer than necessary) where they were trimmed away. The savings might be minimal, but can we simplify those edges further?

Hey Peter! It's probably not worth adding to the core unless it can be done minimally (to keep the library as simple as possible), and I'm not sure how to approach it (needs to be investigated), but have you seen https://github.com/mapbox/delatin? It's much better suited for cases like this, unless you need real time hierarchical simplification on the fly.


find icon images for achievements

Can use placeholder trophy icons for now, until we have bandiwdth to make icons for all of them


Birth by Sleep documentation.

This includes updated documentation.
Updated information:

PMO
PMP
PAM

New file formats:

EXA
EPD
OLO
BEP
PTX

It also includes changes to some BBS constants, an update to BBSA's hash list and a fix for Tm2's class.

Waiting for Azure Pipelines.

Waiting for Azure Pipelines.


Fix Submit Buttons CSS Selector

Submit1 = (By.CSS_SELECTOR, "#et_pb_contact_form_0 button.et_pb_contact_submit")
Submit2 = (By.CSS_SELECTOR, "#et_pb_contact_form_1 button.et_pb_contact_submit")

is either not working or the wait is not working as the assert gets back:
AssertionError: assert '5 + 15 =\nSubmit' == 'Success'
+ Success
- 5 + 15 =
- Submit

The wait is giving back a:
TypeError: __init__() takes 3 positional arguments but 4 were given

Fixed in PR #9


Feature/implementation

Codecov Report
Attention: 253 lines in your changes are missing coverage. Please review.

Comparison is base (26be98b) 0.00% compared to head (8185dec) 53.40%.

Files
Patch %
Lines

src/bin/select_colors.rs
0.00%
211 Missing :warning:

src/ansi256.rs
76.36%
26 Missing :warning:

src/ansi256_quantize.rs
96.11%
7 Missing :warning:

src/palette.rs
42.85%
4 Missing :warning:

src/color.rs
0.00%
3 Missing :warning:

src/oklch.rs
93.75%
2 Missing :warning:

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@            Coverage Diff             @@
##            main       #2       +/-   ##
==========================================
+ Coverage   0.00%   53.40%   +53.40%
==========================================
  Files          1        6        +5
  Lines          3      543      +540
==========================================
+ Hits           0      290      +290
- Misses         3      253      +250

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


Material Wall Graphs

Adds construction and deconstruction graphs for Wood, Plastic, Silver, Gold, Uranium, and Plasma walls.

That's a based PR and I totally missed it


pint context

Is there a(lready) way to provide pint context to the QuanityField?
Best
Matthias

check_matching_unit_dimension uses a very rigid definition of matching dimensions by checking dimensionality which will never take more sophisticated conversions into account [An example, on earth, a weight is also always associated with a corresponding force by 9.81m/s**2 acceleration constant (neglective that it's a function of height)]. Changing this to literally testing if units can be converted allows you to use with ureg.context('earth') scopes during QuantityField definition. Still have to investigate, if we need further modifications when data is loaded from the db. But the below proposed solution is imho also more in line with the python principle of 'if it quacks like a duck it is a duck'.
from pint import DimensionalityError, UnitRegistry
from typing import List

def check_matching_unit_dimension(
    ureg: UnitRegistry, base_units: str, units_to_check: List[str]
) -> None:
    """
    Check if all units_to_check have the same Dimension like the base_units
    If not
    :raise DimensionalityError
    """

    base_unit = getattr(ureg, base_units)

    base_quant = 1 * base_unit

    for unit_string in units_to_check:
        unit = getattr(ureg, unit_string)
        try:
            base_quant.to(unit)
        except DimensionalityError:
            raise DimensionalityError(base_unit, unit)

I had some issues, because I also use the django simple history extension, but if you can globally set your context: ureg.enable_contexts("earth"), with the above modification it seems to work.
Do you want me to put a PR for the change above or rather do that yourself?

Hi, thank you for your issue.
I didn't know the feature existed.
A PR including test is welcome :-)


Fix node token path

After running the steps in https://github.com/rancher/k3s#building-from-source up to running dev-agent.sh, the node token was in:
/var/lib/rancher/k3s/server/node-token (this VM has never had binary release installed on it)
So changed dev-agent.sh to reflect this.
Note: I haven't tested change to dev-docker-agent.sh separately yet and out of time for this evening

@dpen2000 This must be because you are running as root.  The proper thing to do here would be to check if [ $(id -u) = 0 ] then use /var/lib if not use ${HOME}

@ibuildthecloud Updated after your feedback and squashed.

@ibuildthecloud Pushed again to remove blank line added above existing line (there were added around here in previous version of code)


Update menubar-weather extension

Description

Update icons of Raycast icon style
Improve the implementation of SF Symbols icon style

Checklist

[x] I read the extension guidelines
[x] I read the documentation about publishing
[x] I ran npm run build and tested this distribution build in Raycast
[x] I checked that files in the assets folder are used by the extension itself
[x] I checked that assets used by the README are placed outside of the metadata folder

@xilopaint Thank you for your contribution! 🎉
@pernielsentikaer LGTM


Can not install successfully

Hi,
I've followed the installation guide to set a virtual environment in anaconda to reproduce this awesome work, however, I can not install it successfully.
Instead, I've tried to marked the packages which have wrong paths or versions, but it showed conflicts in the end, as following image:

Any suggestions or new version of requirements.txt file will be released?

The problem seems to be that the local mkl-random requires a higher numpy version. Pyraformer is not very demanding on the version of numpy, so I think you can try to fix this by upgrading numpy to 1.21.4. By the way, thanks for your advice, we have updated a new requirements.txt file.


refactor(pid_longitudinal_controller): set stopped state if ego is not in autonomous mode

Description

In the current implementation of pid_longitudinal_controller, if the operation mode is changed, the state will be the same. In this situation, if the goal is set, controller enters into DRIVE state until the vehicle reaches the goal. However, if the operation mode is changed while driving and set autonomous again, controller state stays in DRIVE and the controller does not check the keep_stopped_condition. So vehicle starts to driving without checking steering converged or not.
Tests performed

Tested in planning simulator, worked well.
Not applicable.
Effects on system behavior

Not applicable.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[ ] I've confirmed the contribution guidelines.
[ ] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@TakaHoribe Looks good to me. Could you double check please.


label should not be required

While I understand the desire to ensure screen readers are taken care of, it isn't really the job of a polyfill to enforce best practices. There exist valid use cases for an input without a label, and requiring a label keeps this from being a completely usable polyfill.
If the label is not present, the placeholder can be appended to the input's parent.

I agree, it might not be the job of a polyfill to enforce best practices but I strongly believe it's my job.
As I see no reason ever to have a input or textarea element without a label I will not change this.
Thanks for your contribution though. The new Version 1.3 including your previous changes just went live.


Finished changing the homepage and pokedex page

Changed the home screen information box, colored and adjusted the pokemon name on the Pokedex page, and provided the source link on the search by type page.

Functionally it is ok. In the future consider using an external or internal style sheet with pokedex.html so that you don't have to repeatedly create the same style attribute to change the padding on several elements.


How to MiTM between nex servers and 3ds? (Game servers, not auth)

I was wondering if this is possible, i believe its udp but charles doesnt support that, is there anything that works?

There's wireshark with nex-dissector

There's wireshark with nex-dissector

Is there a way to do it in real-time?

It is in real time


Game broken

When attempting to access this at https://githubschool.github.io/github-games-MatousRokosPowel/, I am getting a 404. This could be caused by a couple things:

GitHub pages needs to be enabled on main. You can fix this in the repository settings.
the index.html file is incorrectly named inde.html. We will fix this together in class.

Can you please fix the first bullet @MatousRokosPowel?

Published page on main and fixed the index name


Mangled Text Encoding

In certreq -new, the mangled text
“template�?
�?WebServer�?

appears.
Unfortunately, it's in critical sections regarding inf file syntax that make the correct syntax difficult to guess.
Please fix these text encoding issues?

I've updated the encoding. Thanks!


fix favicon not displaying in browser tab

I usually add <link rel="icon" href="%PUBLIC_URL%/favicon.ico" /> to the <head> of the index.html but i couldn't get it to work with WTT.
I found an npm package called react-favicon and it works on my local machine.

Oh my bad. For some reason it doesn't show any favicon in production for
me.
I've tried 3 different browsers and 2 different machines (linux and mac)
and all I'm getting is the default globe icon.
[image: Screenshot from 2022-09-16 10-28-43.png]
[image: Screenshot from 2022-09-16 10-28-37.png]
On Thu, Sep 15, 2022 at 10:04 PM Rose @.***> wrote:

I see the favicon on production... [image: favicon]
https://raw.githubusercontent.com/zoobot/screenshots/main/production.png
Where is this broken?
—
Reply to this email directly, view it on GitHub
https://github.com/waterthetrees/wtt_front/pull/289#issuecomment-1248922266,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARRHLMHVLKSRPVT2XUTXXDLV6P5VPANCNFSM6AAAAAAQM2XM5Y
.
You are receiving this because you authored the thread.Message ID:
@.***>

Ya I definitely wasn't a fan of loading the favicon into the App component
either, it was just the only way i could get it to work for this project.
Normally I just add

to the  of the index.html and it works.
I'm still trying to figure out why that doesn't work in this case.
On Fri, Sep 16, 2022 at 2:19 PM Rose @.***> wrote:

Hmm, so maybe it is still an issue then. I don't see it in firefox. Is
there a way we can do this without loading the favicon into the App
component? How do react apps usually handle the favicon? Currently I think
it's just in the public folder.
—
Reply to this email directly, view it on GitHub
https://github.com/waterthetrees/wtt_front/pull/289#issuecomment-1249826241,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ARRHLMAJ3V6LQPI4VAYPYMTV6TP7NANCNFSM6AAAAAAQM2XM5Y
.
You are receiving this because you authored the thread.Message ID:
@.***>

@MattPereira - You should be able to add a new line in the webpack config as shown here: https://stackoverflow.com/a/54178489
Here's the file you need to modify: https://github.com/waterthetrees/wtt_front/blob/main/webpack.config.js#L83

I implemented the changes to the webpack.config.js file as suggested but I still can't get the favicon to actually display on my local machine.

@MattPereira - If you have time and are interested in doing more research do you want to give an general overview of how our webpack config works during the Wednesday meeting, in addition to your changes in this PR? I would just focus on at least what's in the entry, output, module, plugins keys. You can also do more if you feel up to it. Good learning opportunity and I can try to help fill in the gaps if you get stuck.


last updated information

Should we indicate when information on the guide was last updated somehow?
Some ideas:

NEWS.md that tracks updated changes moving forward
a tip box that gets added to each index when updated that autmatically pulls in the date of update.

Something else?

you mean for any commit, or for each release?

up for debate! just to give context to readers. for example, this came up in the discussion of updated guidelines for zoom bombers.  for software specific things like that, does knowing the last time something was updated help the reader? as defaults and policies can change over time.

Hugo has the option to show information about last commited changes to a file. We can add that to the pages. That would be the most accurate, right ?
tagging @maelle as she set it up and might now how easy/hard it would be to get set up.

NEWS.md would make sense but a) is a lot of work b) might not be read.
Adding the date and time could work with Git info and a custom layout, not too much work once we decide where it goes. https://gohugo.io/methods/page/gitinfo/#authordate
Would bottom-right make sense?

yeah i agree re news. still could be helpful moving forward.
not sure about bottom right as some pages are so long?? no strong preference though.

will try to implement something soon!

#146


File Group Header - Dark Theme - Hard to Read

When importing the Dark Theme, the File/Fold Group Header blue color is hard to read.
Recommend changing to something easier on the eyes.
Settings-->Preferences-->Colors and Fonts--->File and Folder Colors --> File group header, Text Color.
I made it lime green and increased the font size a few points (to 11) under, Settings-->Preferences-->Colors and Fonts-->Fonts-->File display groups, Font Size.

Fixed in V3 - https://github.com/AndrewRathbun/DirectoryOpus-DFIRConfig/releases/tag/V3


Problem with Ollama API in Visual ChatGPT Studio

I'm currently testing this addon with Visual Studio 2019 and local models like Ollama. The issue is that you're setting an empty value for the "stop" property. This is causing Ollama to stop providing any responses, and it doesn't work properly. If possible, could you avoid setting this empty stop parameter? That way, it should work with Ollama.
Request Content: {"model":"deepseek-coder:1.3b","messages":[{"role":"system","content":"You are a helpful programmer of c# language."},{"role":"user","content":"just ping to me please"}],"temperature":0.9,"n":1,"stream":false,"stop":"","max_tokens":8192,"frequency_penalty":0.0,"presence_penalty":1.0}
Response Content: {"id":"chatcmpl-584","object":"chat.completion","created":1731542541,"model":"deepseek-coder:1.3b","system_fingerprint":"fp_ollama","choices":[{"index":0,"message":{"role":"assistant","content":""},"finish_reason":"stop"}],"usage":{"prompt_tokens":28,"completion_tokens":1,"total_tokens":29}}
In the picture example without stop property.

@przemsiedl,
do you mean instead set an empty value, set null?

Today I was advised to check LM Studio - unusual behavior like ollama is repeated.
By the way, pay attention to the “Add resume” command - it works by default, without editing the stop line.

Yeah, the null value worked correctly. I'm not sure why, but not all models exhibited this behavior—about 7 out of 10 did. Setting the value to null works well.
CC: @jeffdapaz

Thanks for the feedback @przemsiedl.
I published a new version that will always send null for the stop parameter if it was not filled through the options.


Incorrect usage of word in Spanish language

When using Spanish language translation, the message that stands for "Por favor, introduzca 1 carácter" is incorrect used, since the word "carácter" refers to someone attitude (because is a word with diacritics). The correct usage should be: "Por favor, introduzca 1 caracter".

We're always accepting pull requests to improve translations.


Fix incorrect PostgrestRequest.RPC.method

Method for RPC should be POST.

Included in 0.4.0-beta-2


[Feature] improve the way AppConfig handle workloads changed by others

A workload is rendered and created in AppConfig controller. After the workload is created in the cluster, AppConfig controller will reconcile it periodically to make it matching the desired state.
Besides AppConfig controller, there are other two kinds of controllers, workload controllers and trait controllers, with interest in workloads. They are both possible to change the state of workloads in the cluster, namely, to break the state expected by AppConfig controller. To avoid making conflicting decisions on workloads, it's necessary for the builders of workload/trait controllers to be clear with how AppConfig reconciles workloads.
Currently, AppConfig controller uses Patch method to update the workloads: the patch type is  application/merge-patch+json and the patch data is the whole workload object the same as the one it's created. As a result of no diff calculation, AppConfig controller cannot remove the fields that are not included in the original workload object.
For example, below workload object is created by AppConfig controller.
spec:
  f1: v1
  f2: v2

Afterward, a trait controller changed it into below.
spec:
  f1: vX # change value of f1
  # remove f2
  f3: v3 # add f3

Then AppConfig controller will change it into below in the following round of reconciliation.
spec:
  f1: v1 # revert value of f1
  f2: v2 # restore f2
  f3: v3 # still retain f3

For changed fields like f1, AppConfig controller will replace the changed value with the original one, no matter it's a normal JSON object or array type object.
For removed fields like f2, AppConfig controller will revert it.
For latter-added fields like f3, AppConfig controller has NO way to handle them now.

For latter-added fields, the same situation also happened to trait but it's fixed through replacing Patch with Update, related issue  and PR.
If we allow others except AppConfig controller to changed the state of workloads, especially the spec, how does AppConfig controller handle those latter-added fields?

Currently, if controllers except AppConfig controller changed the configuration of a workload, it depends on whether the changed fields are touched by workload renderer.
If touched, AppConfig controller will revert it.
If not touched, AppConfig controller has no effect on it.  Furthermore, even if AppConfig spec is changed later, AppConfig controller cannot revert previous changes either. But users may expect AppConfig controller to "gc" those changes, e.g., a trait is removed from the AppConfig spec, accordingly, changes the trait controller brought are supposed to be reverted.
Here's a proposal for AppConfig applying mechanism.
It allows users to choose a specific mechanism while starting up an AppConfig controller. That may help users and workload/trait controllers to reach a consensus on the behavior of AppConfig controller.

mode
reconcile (no spec change)
spec changed
Privileges of other controllers

strict
use Update to apply workloads/traits
use Update to apply
Not allow to change ANY configuration of workloads/traits

default
use Patch to apply workloads/traits
use Update to apply
Only allow to change the configuration that is not touched by renderer

apply-once-only
skip applying after created, create if deleted
use Update to apply
Allow to change any configuration but not allow to delete workloads/traits

apply-once-only-force
skip applying after created, skip creating if deleted
use Update to apply
Allow to change any configuration or delete workloads/traits

Currently, if controllers except AppConfig controller changed the configuration of a workload, it depends on whether the changed fields are touched by workload renderer.
If touched, AppConfig controller will revert it.
If not touched, AppConfig controller has no effect on it.  Furthermore, even if AppConfig spec is changed later, AppConfig controller cannot revert previous changes either. But users may expect AppConfig controller to "gc" those changes, e.g., a trait is removed from the AppConfig spec, accordingly, changes the trait controller brought are supposed to be reverted.
Here's a proposal for AppConfig applying mechanism.
It allows users to choose a specific mechanism while starting up an AppConfig controller. That may help users and workload/trait controllers to reach a consensus on the behavior of AppConfig controller.

mode
reconcile (no spec change)
spec changed
Privileges of other controllers

strict
use Update to apply workloads/traits
use Update to apply
Not allow to change ANY configuration of workloads/traits

default
use Patch to apply workloads/traits
use Update to apply
Only allow to change the configuration that is not touched by renderer

apply-once-only
skip applying after created, create if deleted
use Update to apply
Allow to change any configuration but not allow to delete workloads/traits

apply-once-only-force
skip applying after created, skip creating if deleted
use Update to apply
Allow to change any configuration or delete workloads/traits

I wonder when does a trait need to "remove" a field from the workload? This seems to be a rather rare case.

On a different note, it seems there should be some way for the component/workloadDefinition to indicate what fields can be changed and what fields are immutable. The render should maintain those immutable ones in the reconciliation loop and leave the other fields alone.

I wonder when does a trait need to "remove" a field from the workload? This seems to be a rather rare case.

trait rarely needs to remove a field but is possible to add a field. e.g., VolumeMount trait has to add Volumes field to the workload.

I wonder when does a trait need to "remove" a field from the workload? This seems to be a rather rare case.

trait rarely needs to remove a field but is possible to add a field. e.g., VolumeMount trait has to add Volumes field to the workload.

VolumeMount trait has to add Volumes field to the workload. If the trait is removed, currently, there's no way to remove the Volumes field it added.

I think the trait controller can use finalizer mechanism, if it was removed, the finalizer should clean the fields added to workload.

VolumeMount trait has to add Volumes field to the workload. If the trait is removed, currently, there's no way to remove the Volumes field it added.

I think the trait controller can use finalizer mechanism, if it was removed, the finalizer should clean the fields added to workload.

Currently, if controllers except AppConfig controller changed the configuration of a workload, it depends on whether the changed fields are touched by workload renderer.
If touched, AppConfig controller will revert it.
If not touched, AppConfig controller has no effect on it. Furthermore, even if AppConfig spec is changed later, AppConfig controller cannot revert previous changes either. But users may expect AppConfig controller to "gc" those changes, e.g., a trait is removed from the AppConfig spec, accordingly, changes the trait controller brought are supposed to be reverted.
Here's a proposal for AppConfig applying mechanism.
It allows users to choose a specific mechanism while starting up an AppConfig controller. That may help users and workload/trait controllers to reach a consensus on the behavior of AppConfig controller.
mode	reconcile (no spec change)	spec changed	Privileges of other controllers
strict	use Update to apply workloads/traits	use Update to apply	Not allow to change ANY configuration of workloads/traits
default	use Patch to apply workloads/traits	use Update to apply	Only allow to change the configuration that is not touched by renderer
apply-once-only	skip applying after created, create if deleted	use Update to apply	Allow to change any configuration but not allow to delete workloads/traits
apply-once-only-force	skip applying after created, skip creating if deleted	use Update to apply	Allow to change any configuration or delete workloads/traits

We have merged 3-way-merge patch now, this is not correct any more.

Currently, if controllers except AppConfig controller changed the configuration of a workload, it depends on whether the changed fields are touched by workload renderer.
If touched, AppConfig controller will revert it.
If not touched, AppConfig controller has no effect on it. Furthermore, even if AppConfig spec is changed later, AppConfig controller cannot revert previous changes either. But users may expect AppConfig controller to "gc" those changes, e.g., a trait is removed from the AppConfig spec, accordingly, changes the trait controller brought are supposed to be reverted.
Here's a proposal for AppConfig applying mechanism.
It allows users to choose a specific mechanism while starting up an AppConfig controller. That may help users and workload/trait controllers to reach a consensus on the behavior of AppConfig controller.
mode	reconcile (no spec change)	spec changed	Privileges of other controllers
strict	use Update to apply workloads/traits	use Update to apply	Not allow to change ANY configuration of workloads/traits
default	use Patch to apply workloads/traits	use Update to apply	Only allow to change the configuration that is not touched by renderer
apply-once-only	skip applying after created, create if deleted	use Update to apply	Allow to change any configuration but not allow to delete workloads/traits
apply-once-only-force	skip applying after created, skip creating if deleted	use Update to apply	Allow to change any configuration or delete workloads/traits

We have merged 3-way-merge patch now, this is not correct any more.

I mark this issue as wontfix, the appconfig controller should not change the fields managed by others.

I mark this issue as wontfix, the appconfig controller should not change the fields managed by others.

I mark this issue as wontfix, the appconfig controller should not change the fields managed by others.

Agreed!  Closed since current appconfig already works as expected.


iPhoneX FaceID prompt

Hi Eddy!
Have a cordova app which includes v3.2.0 of this plugin.
Upon launching on the new iPhoneX with FaceID, users are prompted with the following:

Are there any changes required to "update" the app in order to "officially" support FaceID?

Hmm interesting - can you perhaps Google that phrase?

I tried looking for it, the only mention I could find was in a iPhoneX review article:

Since Face ID is replacing Touch ID, you may run into some odd issues getting it to work in lieu of a fingerprint sensor.  For example, with our  Discover banking app, it initially asked us to sign in, and the app’s respective settings only made note of activating Touch ID. After enabling it, closing the app, and re-opening it, we got a message indicating the app “was designed to support Touch ID. It has not been updated for Face ID.” It still gave us the option to use Face ID, and we were able to quickly jump into these apps securely with just our face. Most of our apps that required a pin entry or password were able to use Face ID effortlessly, and this is because Apple said Face ID uses the same framework as Touch ID.

Ah, so it seems like somehow Apple detects your app hasn't been updated for Face ID, but it still allows you to use it.
It may be as simple as building your app with the iOS 11 SDK (Xcode 9), but I can't tell for sure at this point.

For reference, app was built with xcode 9 / iOS 11.0 SDK
I was going through the LocalAuthentication documentation and comparing with the implementation in the plugin -- nothing stood out to me. It seems like it should just work as you mentioned in #33! But I'm a not a fluent ObjectiveC speaker 😅
I'll keep an open eye for other reports of such behavior in other apps and keep this issue updated.
Thanks for your insight though.. much appreciated!

And thank you as well, I'm sure we can narrow this down one day. I'll be receiving my iPhone X (hopefully) in December and I'm sure that will give me some incentive to dig around.

Looks like here's the answer: https://forums.developer.apple.com/thread/91253
If the NSFaceIDUsageDescription key (and value) misses in the Plist, then the simulator shows this warning. On a real device (iPhone X) the app probably crashes. So we need to add the string during plugin installation.

Check this out 🎉 https://github.com/EddyVerbruggen/cordova-plugin-touch-id#face-id-support

🎉 🎉
Thanks @ajcrites and @EddyVerbruggen


python36Packages.filebytes: 0.9.17 -> 0.9.18

Semi-automatic update generated by https://github.com/ryantm/nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/python3.6-filebytes/versions.
meta.description for python36Packages.filebytes is: '"Scripts to parse ELF, PE, Mach-O and OAT (Android Runtime)"'.

Checks done (click to expand)

built on NixOS

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 0.9.18 with grep in /nix/store/k52bnh9xskwha8bp2rp3jxfimj01fm4l-python3.6-filebytes-0.9.18

directory tree listing: https://gist.github.com/560ad3902cb9ba38bf4f644714512c6a

du listing: https://gist.github.com/d78dd25167b3eb618b5c4d6792c080b6

Rebuild report (click to expand)

16 total rebuild path(s)
4 package rebuild(s)
4 x86_64-linux rebuild(s)
4 i686-linux rebuild(s)
4 x86_64-darwin rebuild(s)
4 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
python27Packages.filebytes
python27Packages.ropper
python36Packages.filebytes
python36Packages.ropper

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/k52bnh9xskwha8bp2rp3jxfimj01fm4l-python3.6-filebytes-0.9.18 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(r-ryantm's Cachix cache is only trusted for this store-path realization.)
Or, build yourself:
nix-build -A python36Packages.filebytes https://github.com/r-ryantm/nixpkgs/archive/e57dc48c251975be4a0002052c6c58e015a7d561.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/k52bnh9xskwha8bp2rp3jxfimj01fm4l-python3.6-filebytes-0.9.18
ls -la /nix/store/k52bnh9xskwha8bp2rp3jxfimj01fm4l-python3.6-filebytes-0.9.18/bin

cc @bennofs for testing.

Success on aarch64-linux (full log)
Attempted: python36Packages.filebytes
Partial log (click to expand)
writing top-level names to filebytes.egg-info/top_level.txt
reading manifest file 'filebytes.egg-info/SOURCES.txt'
writing manifest file 'filebytes.egg-info/SOURCES.txt'
running build_ext

----------------------------------------------------------------------
Ran 0 tests in 0.000s

OK
/nix/store/jb12kgrw4j2lfrdgrn08fswqjn3gnwc6-python3.6-filebytes-0.9.18

Success on x86_64-darwin (full log)
Attempted: python36Packages.filebytes
Partial log (click to expand)
writing top-level names to filebytes.egg-info/top_level.txt
reading manifest file 'filebytes.egg-info/SOURCES.txt'
writing manifest file 'filebytes.egg-info/SOURCES.txt'
running build_ext

----------------------------------------------------------------------
Ran 0 tests in 0.000s

OK
/nix/store/j5rb6vfjjwd6iaksacyp2yc3ip6dc65v-python3.6-filebytes-0.9.18

Success on x86_64-linux (full log)
Attempted: python36Packages.filebytes
Partial log (click to expand)
writing top-level names to filebytes.egg-info/top_level.txt
reading manifest file 'filebytes.egg-info/SOURCES.txt'
writing manifest file 'filebytes.egg-info/SOURCES.txt'
running build_ext

----------------------------------------------------------------------
Ran 0 tests in 0.000s

OK
/nix/store/k52bnh9xskwha8bp2rp3jxfimj01fm4l-python3.6-filebytes-0.9.18


Synchronizing the content of wasm folder

Hello,
Can we consider auto-synchronizing the content of wasm folder with  extism/plugins ?
https://github.com/extism/plugins/issues/5 might have an impact on this one.
Thanks.

We can certainly look into it - did you encounter an issue this would solve?

When testing https://github.com/extism/extism/issues/673, I faced a small issue :
The extism/wasm/http.wasm expose 1 function http_request, the one in plugins repo expose 2 functions http_get and http_post. I was confused for a second by it :D.
I am not sure if other plugins and other repo that have .wasm copy in them are affected by this. Would be nice to centralize all wasm binaries used in all extism repos in one place.

We've since removed the plugins folder and now the tests point directly to the releases on that repo. So i think this should effectively solve the problem. Let me know if i misinterpreted though!


Support CUB prefix sum & product

In the demo below, CUB gets about a 4x speed-up on a P100:
>>> import cupy as cp
>>> import cupyx
>>>
>>> a = cp.random.random(1000000)
>>>
>>> cp.cuda.cub_enabled  =False
>>> print(cupyx.time.repeat(cp.cumprod, (a, )))
cumprod             :   428.775 us   +/-57.870 (min:  396.988 / max:  976.234) us    471.108 us   +/-45.524 (min:  449.888 / max:  992.736) us
>>> cp.cuda.cub_enabled = True
>>> print(cupyx.time.repeat(cp.cumprod, (a, )))
cumprod             :   103.053 us   +/-19.460 (min:   84.242 / max:  229.079) us    132.358 us   +/-17.695 (min:  113.888 / max:  250.048) us
>>>
>>> cp.cuda.cub_enabled = False
>>> print(cupyx.time.repeat(cp.cumsum, (a, )))
cumsum              :   428.253 us   +/-55.802 (min:  398.817 / max:  978.976) us    470.163 us   +/-43.695 (min:  450.464 / max:  995.872) us
>>> cp.cuda.cub_enabled = True
>>> print(cupyx.time.repeat(cp.cumsum, (a, )))
cumsum              :   103.998 us   +/-17.858 (min:   86.243 / max:  234.290) us    133.392 us   +/-16.486 (min:  115.808 / max:  256.320) us

TODO:

[ ] compare performance with cupy.core._routines_math.scan() (Rel: #2905)
[ ] add a CUB call path to cupy.core._routines_math.scan()
[x] check if CUB handles NaNs correctly
[ ] add tests (Question: to here or to #2598?)

The first two action items are for speeding up certain fancy indexing cases.

Nice. I tried this out and the only problem I encountered was in the shape of the returned result when axis=None and the input is nD. (The output should be a ravelled array)
Simple example with CUB enabled/disabled (the disabled behavior matches NumPy):
import cupy as cp
import numpy as np

a = cp.testing.shaped_arange((4, 5), cp, float)
cp.cumsum(a)
# array([[  1.,   3.,   6.,  10.,  15.],
#        [ 21.,  28.,  36.,  45.,  55.],
#        [ 66.,  78.,  91., 105., 120.],
#        [136., 153., 171., 190., 210.]])

cp.cuda.cub_enabled = False
cp.cumsum(a)
# array([  1.,   3.,   6.,  10.,  15.,  21.,  28.,  36.,  45.,  55.,  66.,
#         78.,  91., 105., 120., 136., 153., 171., 190., 210.])

Oops, thanks @grlee77! I read the spec wrong...

I was actually working on this :D.
I let you take care of it better :).
One of the things I saw is that CUB scanning does not support axis selection, so implementing that correctly may be a bit trickier.

Oh sorry for duplicate work @emcastillo. Which branch is it? I could cherry pick your code.

One of the things I saw is that CUB scanning does not support axis selection, so implementing that correctly may be a bit trickier.

I don’t think CUB can support axis != None...

No worries, your PR is going to be better than mine so do the cub part and I will take care of improving the non-cub kernels.

@emcastillo This PR should be considered jointly with your #2907. Looks like cupy.core._routines_math.scan() is really good. It is slower than CUB only when there are >= 10^6 elements (for float64 in this case):
>>> a = cp.random.random(1000)
>>> print(cupyx.time.repeat(cp.cuda.cub.device_scan, (a, 5)))
device_scan         :    98.163 us   +/-16.937 (min:   76.599 / max:  222.032) us    106.869 us   +/-18.320 (min:   77.120 / max:  236.768) us
>>> print(cupyx.time.repeat(cp.core._routines_math._scan_for_test, (a, )))
_scan_for_test      :    67.176 us   +/- 9.349 (min:   49.020 / max:  147.861) us     76.206 us   +/-10.508 (min:   56.064 / max:  163.200) us
>>>
>>> a = cp.random.random(100000)
>>> print(cupyx.time.repeat(cp.cuda.cub.device_scan, (a, 5)))
device_scan         :    97.013 us   +/-17.426 (min:   76.346 / max:  215.663) us    105.617 us   +/-18.885 (min:   83.296 / max:  300.320) us
>>> print(cupyx.time.repeat(cp.core._routines_math._scan_for_test, (a, )))
_scan_for_test      :    67.560 us   +/- 9.815 (min:   49.441 / max:  181.684) us     76.555 us   +/-11.008 (min:   56.416 / max:  198.016) us
>>>
>>> a = cp.random.random(1000000)
>>> print(cupyx.time.repeat(cp.cuda.cub.device_scan, (a, 5)))
device_scan         :    94.037 us   +/-17.865 (min:   74.958 / max:  278.390) us    124.621 us   +/-16.371 (min:  106.752 / max:  301.504) us
>>> print(cupyx.time.repeat(cp.core._routines_math._scan_for_test, (a, )))
_scan_for_test      :    90.543 us   +/-17.130 (min:   70.443 / max:  201.541) us    123.582 us   +/-10.805 (min:  107.584 / max:  223.040) us
>>>
>>> a = cp.random.random(10000000)
>>> print(cupyx.time.repeat(cp.cuda.cub.device_scan, (a, 5)))
device_scan         :    82.406 us   +/-12.235 (min:   74.969 / max:  204.807) us    650.291 us   +/- 6.245 (min:  644.096 / max:  714.784) us
>>> print(cupyx.time.repeat(cp.core._routines_math._scan_for_test, (a, )))
_scan_for_test      :    78.777 us   +/- 9.734 (min:   72.235 / max:  196.004) us    822.750 us   +/- 8.690 (min:  816.992 / max:  901.280) us

So, if cupy.core._routines_math.scan() is tweaked a bit (simply by changing the accumulator += to *= I guess), perhaps in addition to cumsum() it can also do cumprod(), and we either wouldn't need CUB at all, or would switch to CUB only when the array is excessively large?
(Actually I already cheated a bit in the above comparison by using cp.cuda.cub.device_scan() instead of cp.cuda.cub.cub_scan(): the latter adds about 8 us on my machine due to extra checks...)

we either wouldn't need CUB at all, or would switch to CUB only when the array is excessively large?

We could also let users decide if they want to use CUB scan, as usual by toggling cp.cuda.cub_enabled.

I wouldn't set sub-optimal implementations by default

Another thing: CUB cumsum and cumprod seems to be buggy for complex numbers. I am not sure why, but this is deterministically reproducible. The cumulation stopped at the 449-th element of the result:
>>> import cupy as cp
>>> a = cp.random.random(500) + 1j*cp.random.random(500)
>>> cp.cuda.cub_enabled = True
>>> b = cp.cumsum(a)  # wrong
>>> cp.cuda.cub_enabled = False
>>> c = cp.cumsum(a)  # correct
>>> cp.allclose(b[0:447],c[0:447])
array(True)
>>> cp.allclose(b[0:448],c[0:448])
array(True)
>>> cp.allclose(b[0:449],c[0:449])
array(False)
>>> b[448] == a[448]
array(True)
>>> c[448] == a[448]
array(False)

Looking into this...

@emcastillo I suggest we consider the PRs in the following order: #2919 (this PR) -> #2907 for two reasons.
First, I do not deal with the complexity of out and dtype, as outlined in https://github.com/cupy/cupy/pull/2919#issuecomment-575705775, and simply let the caller functions  (cumsum and cumprod) handle it, whereas in #2907 the caller code is refactored.
Second, while Gregory's suggestion on a separate helper is tempting, I don't see immediately how such helper can be applicable since the rules vary across different functions.
If we want to make the implementation more NumPy-compliant, we can make another PR to address https://github.com/cupy/cupy/pull/2919#issuecomment-575705775 after both are merged, as you suggested earlier.
If you agree with my suggestion, the only question I have for you is:

[ ] add tests (Question: to here or to #2598?)

Thanks 🙂

Lets do that

Cool, if we don’t need to add tests here, this PR is ready.

Lets add tests in #2598 thanks!

I fixed the compilation error.

Thanks @emcastillo!


Add a parser result object

Right now yp_parse only returns an AST node.  This is kind of cumbersome because as the compiler recurses the AST, we must pass a node and a parser object in order to get data such as newline information.
I think newline information shouldn't be stored on the parser, but rather a parse result object.  The result object should contain information that's contextually important to the document we parsed, but isn't associated wit a parser (newline information being a prime example).

This is already the case in the Ruby API: https://github.com/ruby/yarp/blob/a8904e013e767c6793d9acaa32348471aa39dd5e/lib/yarp.rb#L147
We should do the same for the Java API (I can do that),
and for the C API too, as you say.

Related:
https://github.com/ruby/yarp/pull/1112#discussion_r1249513857
https://github.com/ruby/yarp/pull/1112#discussion_r1249517829

We have this now in the prism compiler in CRuby.


Call git-credential approve on successful credential usage

After we have successfully used a generated credential we should inform Git that the credential is valid and should be stored, by calling git credential approve.
We make an effort to not call approve (which calls gcm store) if we've already called it once before for the currently cached credential to prevent a store per successfully auth'd network request.
Fixes #745

I want to take this change, but let's target the release after the one that we're starting to prepare.

@jrbriggs am I OK to merge this into master now?

Yes, @mjcheetham -- master targets M149. Thanks!


Callback Once Snackbar Disappears

I'm not sure if this exists currently or not but a good feature would be a callback so when the dialog disappears you can run a function. Prefect for any undo button, simply don't do anything until the callback is called.

There's already a built in method to do this. Just set a OnVisibiltyChangeListener like so:
.withVisibilityChangeListener(new SnackBar.OnVisibilityChangeListener() {
		@Override
		public void onShow(int stackSize) {
			Log.i("SNACKBAR", "onShow Snacks left to show: "+stackSize);
		}

		@Override
		public void onHide(int stackSize) {
			Log.i("SNACKBAR", "onHide Snacks left to show: "+stackSize);
		}
})


Cuda kernel function doesn't print in wsl2

Windows Version
Microsoft Windows [version 10.0.19045.3570]
WSL Version
<IP_ADDRESS>
Are you using WSL 1 or WSL 2?

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>
Distro Version
Ubuntu 22.04
Other Software
Cuda compilation tools, release 12.3, V12.3.52
Nvidia Driver version: 537.58
Repro Steps
I use a cuda kernel function in file hello.cu:
#include <stdio.h>

__global__ void hello() {
    printf("Hello from GPU\n");
}

int main() {
    hello<<<1, 1>>>();
    {
        cudaError_t e = cudaDeviceSynchronize();
        if (e != cudaSuccess)
            printf("kernel launch failed with error \"%s\".\n",
                   cudaGetErrorString(e));
        else
            printf("kernel launch succeeded");
    }
    return 0;
}

then I compile this file:
nvcc hello.cu -o hello

finnally execute:
./hello

Expected Behavior
it should print:
Hello from GPU
kernel launch succeeded

Actual Behavior
kernel launch succeeded

Diagnostic Logs
No response

how did you solve this problem?


Filedriver purge didn't work in docker

###PHP version

PHP 7.3.3-1+ubuntu18.04.1+deb.sury.org+1 (cli) (built: Mar  7 2019 20:31:49) ( NTS )
Copyright (c) 1997-2018 The PHP Group
Zend Engine v3.3.3, Copyright (c) 1998-2018 Zend Technologies
with Zend OPcache v7.3.3-1+ubuntu18.04.1+deb.sury.org+1, Copyright (c) 1999-2018, by Zend Technologies
with Xdebug v2.7.0, Copyright (c) 2002-2019, by Derick Rethans

tedivm/stash version: v0.14.2
Steps to reproduce
$result = [
    'hittedAfterPurge' => 0,
    'hitted' => 0,
    'missed' => 0,
];
$i = 1000;
while ($i-- > 0) {
    $expiresIn = mt_rand(40, 1000);
    $cacheKey = hash('sha256', 'some string' . $expiresIn);
    $data = ['key1' => 1, 'key2' => 2];
    $pool = new Stash\Pool(new \Stash\Driver\FileSystem);
    $pool->purge();
    if ($pool->hasItem($cacheKey)) {
        $result['hittedAfterPurge']++;
    }
    $cacheItem = $pool->getItem($cacheKey)
        ->set($data)
        ->expiresAt(new \DateTime('@' . (time() + $expiresIn)));

    $saved = $pool->save($cacheItem);
    $hasItem = $pool->hasItem($cacheKey);
    if ($hasItem) {
        $result['hitted']++;
        continue;
    }
    $result['missed']++;
}
foreach ([
             'hittedAfterPurge' => $result['hittedAfterPurge'],
             'hitted' => $result['hitted'],
             'missed' => $result['missed'],
         ] as $key => $value) {
    echo $key, ' : ', var_export($value), PHP_EOL;
}

Result
hittedAfterPurge : 351
hitted : 991
missed : 9

Purge doesn't erase items from the cache, it simply cleans up items from the filesystem that have already expired (for some backends this happens automatically and purge doesn't do anything at all).
If you want to remove everything from the cache you need to run clear instead of purge.

mom said i'm special (с)
Thanks


ARROW-9861: [Java] Support big-endian in DecimalVector

This PR fixes failures in DecimalVectorTest on a big-endian platform

@kiszk you'll probably need to make some fixes for Decimal256 as well, I think.
@BryanCutler you mentioned you could devote some time to reviewing Big Endian changes?  Would you mind taking a look through this one and  @kiszk other Java changes?

Sure, I can take a look. It might a day or two before I can though @kiszk .

@emkornfield Sure, I will work for supporting Decimal256.

I will update the Decimal256Vector class late today or tomorrow.

The test error with Java JNI looks unrelated and seems to be an env issue with ORC, I'll go ahead with merging this.

merged to master, thanks @kiszk !

@BryanCutler Thank you. One comment.
According to the document, benchmarking is necessary before merging features (I think that the test code does not affect the performance)

Benchmarks for performance critical parts of the code to demonstrate no regression.

I am working for benchmark bot for Java here. It would be good to merge new features after this bot will be available.
cc @emkornfield

I did not see anything that looks like it would affect performance here, but I agree we should get some benchmarks going to be sure. I will look at you other PR next.


Combining meshes and rotating them?

First of all, great work! Let's say there are three cubes stacked on top of each other or some more complex geometry. How is it possible to group them into one single mesh (to later rotate the mesh)? There is not much to be found about combining 3d meshes in the examples. Thanks
const c1 = app.stage.addChild(Mesh3D.createCube());
const c2 = app.stage.addChild(Mesh3D.createCube());
const c3 = app.stage.addChild(Mesh3D.createCube());

// ..? Combine & rotate c1,c2,c3 as one mesh?

Hello!
Just like PixiJS you just add your objects to a container, and then rotate that container.
const container = app.stage.addChild(new PIXI3D.Container3D())

const c1 = container.addChild(PIXI3D.Mesh3D.createCube());
c1.x = -2.5
const c2 = container.addChild(PIXI3D.Mesh3D.createCube());
c2.x = 0
const c3 = container.addChild(PIXI3D.Mesh3D.createCube());
c3.x = +2.5

let rotation = 1
app.ticker.add(() => {
  container.rotationQuaternion.setEulerAngles(rotation++, 0, 0)
})


[content] complete indigenous content for American region

Related to other issues, this should be retired when we have all indigenous tribes represented within the American (modern-day definition) region. Other issues will cover Mexico and Central American region, as well as Canadian region.

This was completed with the last of the Alaskan and Canadian tribes added in #250, #251 and #252


Add a possibility to make groups and priority's

⚠ Please verify that this feature request has NOT been suggested before.

[X] I checked and didn't find similar feature request

🏷 Feature Request Type
Other
🔖 Feature description
Create groups names and priority number by machine, if a  machine in a group fails first, don't try others in same group because all will be down. Example: 100 alerts will be send at the moment in one gateway fails...
✔ Solution
If one machine with priority 0 in same group fails don't try to check if others with priority 1,2,3 are alive.
Only one alert is send inform that groups name, machine is down.
❓ Alternatives
No response
📝 Additional Context
No response

#1236 will basically meet your needs.

@vslinuxdotnet https://github.com/louislam/uptime-kuma/pull/2693 has been merged and is avaliable in 1.22.
I think this issue is resolved. Could you close this issue?

@
We are consolidating duplicate issues a bit to make issue management easier.
I think, we should track this issue in https://github.com/louislam/uptime-kuma/pull/2693 https://github.com/louislam/uptime-kuma/issues/1089 https://github.com/louislam/uptime-kuma/issues/2487 as there is no functional difference (maybe just small naming differences, but nothing that would require a different issue imo)
⇒ I am going to close this as a duplicate.


Logging for non-provider data

Current provider setup allows you to add logging element to a provider pipe. Depending on the exact configuration you can log either raw data (not yet in SK format) or after conversion to SK format.
However data produced by plugins does not flow through a provider pipe and thus logging is not possible.

How about making it possible to create provider pipes for plugins, identified by plugin id?
Currently plugins are supposed to call app.handleMessage to insert deltas. What delta from plugins was inserted into the beginning of a pipe, if there is a matching (provider id === plugin id) pipe?
This would allow we to use same logging configuration and possibly other pipe elements.
@sbender9 your thoughts?

I like it. Maybe allow to configure for "all" plugins, so we don't need to configure for each one unless needed.

Fixed quite some time ago.


Mininet startup/shutdown can be very slow

Particularly on a VM, mininet startup is extremely slow. Adding links and starting switches can be very sluggish.
It seems that Mininet cs244/2.0 might even be slower than 1.0? Or perhaps it just takes up more CPU/memory?
We should add some Mininet startup/shutdown performance benchmarks, and also attempt to identify and fix the cause of the slowdown.

sudo mn --topo torus,10,10 --test build results in completed in 25.852 seconds, was it faster in 1.0? is this still relevant? it seems like startup time on a recent machine is not a problem anymore

I declare it good enough for government work.


Hook: Set properties on default volume type

Cinder always creates a default volume type called DEFAULT, and this type is unrestricted, so new volumes can go to any volume back-end running on the deployment if an unrestricted volume type is not specified.
This can be problematic for some tempest tests when running on a multi back-end deployment.
This hook allows a job to define the properties (extra specs) of the default volume type. The most common way of using it is to set the volume_backend_name so volumes are created in a specific back-end, but other properties can be added as well.
As a pull request owner and reviewers, I checked that:

[x] Appropriate testing is done and actually running
[x] Appropriate documentation exists and/or is up-to-date:

[x] README in the role
[x] Content of the docs/source is reflecting the changes

/lgtm
Tested internally, the patch applies the property as expected. You need to set something like:
cifmw_cinder_default_type_properties:
volume_backend_name: foobar

/approve


add function to copy all function name

For convenience , I wish to add a button (or something else) to copy the symbol list from panel node.
May I do a PR for it?

I don't believe there is anything in the VS Code API for accessing the clipboard, but you should be able to use a Node package like clipboardy to accomplish that.


cv.stereoCalibrate does not work

After successfully calibrating the individual cameras of the stereo camera pair, cv.stereoCalibrate does not work. First, I spotted a typo in stereoCalibrate, (defauly -> default).
But even after fixing the typo I still get an error:
/home/username/torch/install/share/lua/5.1/cv/init.lua:328: attempt to call method 'cdata' (a nil value)
stack traceback:
	/home/username/torch/install/share/lua/5.1/cv/init.lua:328: in function 'prepare_for_wrapping'
	/home/username/torch/install/share/lua/5.1/cv/init.lua:337: in function 'wrap_tensor'
	/home/username/torch/install/share/lua/5.1/cv/calib3d/init.lua:824: in function 'stereoCalibrate'

Can you fix the type please and have a look what else is wrong? The parameters I provide to stereoCalibrate should be OK, because they work with cv.calibrateCamera (IR and RGB are my two cameras):
  local errorIR, cameraMatrixIR, distCoeffsIR, rvecsIR, tvecsIR = cv.calibrateCamera{objectPoints=objectPoints, imagePoints=imagePointsIR, imageSize=imageSize}
  local errorRGB, cameraMatrixRGB, distCoeffsRGB, rvecsRGB, tvecsRGB = cv.calibrateCamera{objectPoints=objectPoints, imagePoints=imagePointsRGB, imageSize=imageSize}

  print("Reprojection error for ir="..errorIR..", rgb="..errorRGB)
  print("Intrinsic calibration IR cam: ")
  print(cameraMatrixIR);
-- [...]  Print all the other matrices, they look OK

  local _MatrixCam1, _DistortCam1, _MatrixCam2, _DistortCam2, R, T, E, F =  cv.stereoCalibrate{objectPoints=objectPoints, imagePoints1=imagePointsIR, imagePoints2=imagePointsRGB,
                    cameraMatrix1=cameraMatrixIR, distCoeffs1=distCoeffsIR, cameraMatrix2=cameraMatrixRGB, distCoeffs2=distCoeffsRGB,
                    imageSize=imageSize}   -- -> produces the error shown above

thanks for checking, you can use it now


syncStripe method in Subscription class

New method "syncStripe" in Subscription class, to perform full synchronization. Motivation: active scope from subscriptions check status but also "ends_at" value (and ignore canceled status).

No plans on adding this.

You should configure your Stripe webhooks to keep your susbcriptions up to date: https://laravel.com/docs/7.x/billing#handling-stripe-webhooks


Signature method should remove unused keys

The signature method generates invalid signatures if you have a data value that is not used.
One way around this is to wrap all optional parameters in ifs or to strip out the unused values in the signature.
I'll happily look at this in the next few days and propose a patch.

We're using exactly the same signing method as the official library. I'm now unsure this is a bug. I'll close the ticket and open it again if there are other issues that I can track down.


teensy: add west flash teensy_loader_cli integration

Allows Teensy 4.0 and 4.1 board to be flashed using the west flash command.

I've got CI in an okayish state but I'm not sure how to resolve this pylint error. Could someone help me further?

@danieldegrasse thank you for the suggestions I've cleaned-up the python code could you take a look again?

@mbolivar-ampere, can you help take a look at this PR.

@mbolivar-ampere, moved this over to me as assignee as it is mostly a platform with an NXP part on it. If you object then please adjust back.


fix-hero-typo

When you say every piece of, then it means you are referring to a single noun, so you need to use singular instead of plural. Hence, 'product' instead of 'products'.

Thank you for highlighting and fixing the error. Happy Contribution!!! 😊✨


⚠ BeyondHD has degraded performance

In 589e101, BeyondHD ($BHD) experienced degraded performance:

HTTP code: 200
Response time: 16451 ms

Resolved: BeyondHD performance has improved in 9f0d7f0 after 6 minutes.


Couldn't load plugin 'qgis_gee_data_catalog' due to an error when calling its classFactory() method

Receiving this error when starting.
ModuleNotFoundError: No module named 'ee'
Traceback (most recent call last):
File "C:\PROGRA~1/QGIS32~1.1/apps/qgis/./python\qgis\utils.py", line 423, in startPlugin
plugins[packageName] = package.classFactory(iface)
File "C:\Users/.../AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\qgis_gee_data_catalog_init.py", line 33, in classFactory
from .qgis_gee_data_catalog import GeeDataCatalog
File "C:\PROGRA~1/QGIS32~1.1/apps/qgis/./python\qgis\utils.py", line 888, in _import
mod = _builtin_import(name, globals, locals, fromlist, level)
File "C:\Users/l...AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\qgis_gee_data_catalog\qgis_gee_data_catalog.py", line 26, in
from .ee_interface import (add_ee_image_layer, download_ee_image_layer,
File "C:\PROGRA~1/QGIS32~1.1/apps/qgis/./python\qgis\utils.py", line 888, in _import
mod = _builtin_import(name, globals, locals, fromlist, level)
File "C:\Users/.../AppData/Roaming/QGIS/QGIS3\profiles\default/python/plugins\qgis_gee_data_catalog\ee_interface.py", line 6, in
import ee
File "C:\PROGRA~1/QGIS32~1.1/apps/qgis/./python\qgis\utils.py", line 888, in _import
mod = _builtin_import(name, globals, locals, fromlist, level)
ModuleNotFoundError: No module named 'ee'

nevermind I think I just solved it lol. Should have read your instructions better.

hi, I have this error, can you help me? tanks

Sorry for the poor documentation. Can you try the instructions in
Portuguese from this link?
Instalacao · sandroklippel/qgis_gee_data_catalog Wiki · GitHub
https://github.com/sandroklippel/qgis_gee_data_catalog/wiki/Instalacao
Em ter., 16 de jan. de 2024 às 18:54, Santiago Gaston Cameto Hernandez <
@.***> escreveu:

hi, I have this error, can you help me? tanks
—
Reply to this email directly, view it on GitHub
https://github.com/sandroklippel/qgis_gee_data_catalog/issues/10#issuecomment-1894576947,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AIBSMEFBMOZ4ZGAC2P6OJTDYO3ZKTAVCNFSM6AAAAAASMW4PZKVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTQOJUGU3TMOJUG4
.
You are receiving this because you are subscribed to this thread.Message
ID: @.***>


Receipts are not loading for historical report previews

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number:
Reproducible in staging?: needs reproduction
Reproducible in production?: needs reproduction
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @shawnborton
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1721074439242059
Action Performed:

Go to workspace chat which has lots of expenses from the past
Scroll up to see the workspace history and many of the old expenses do not show receipt thumbnail

Expected Result:
If there are expenses with receipts should show the receipt thumbnail
Actual Result:
Old expenses do not show the receipt thumbnail. However, once I click into the report it does indeed show a thumbnail, and then when I navigate back to the workspace chat, the thumbnail appears in the preview.
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

[ ] Android: Native
[ ] Android: mWeb Chrome
[ ] iOS: Native
[ ] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[ ] MacOS: Desktop

Screenshots/Videos
https://github.com/user-attachments/assets/527f0134-08de-4702-904f-f8c5ac452063

View all open jobs on GitHub

This has been labelled "Needs Reproduction". Follow the steps here: https://stackoverflowteams.com/c/expensify/questions/16989

I've tried to repro this but all mine are there:

@shawnborton is this still happening for you?

Just checked and it is not happening anymore, who knows! Going to close in the meantime.


Enable WriteCore feature for consumption

We need to enable WriteCore feature to consumption. Therefore add use-write-core: true and do a regen.

API change check
APIView has identified API level changes in this PR and created following API reviews.
Azure.ResourceManager.Consumption


Rebrand to ts-node?

The command line interface is ts-node, which is inconsistent with the package name. Should I make the CLI longer (unlikely, too much to type), rename the package for consistency or ignore it?

yes


Adds scope to add translations fields to the selection

Compared to the listsTranslations scope, this scope just adds the fields to the selection. It also propose an easy way of sorting results by a translated field.

This won't work. If you check the mysql queries that are executed you'll see that $query->addSelect($this->getTranslationsTable().'.'.$translationField); has no effect because laravel doesn't know this extra select belongs to a translation relationship.


plugins or integrations

hey,
is there something to write plugins or do integrations with the helpdesk?
would be nice to have someting like that.

Hi @traskat, sorry for delay. Plugins are not supported in this version, but you can extend code by your needs. I wan to update the HelpDesk in the new year.


Some regressions in how generation of fresh symbolic values was working.

I guess we need to decide how much of this is desired behavior.
It makes sense to me that this function should be annotated with impure, since it will be returning a different value dependent on the backend environment each time.

Neither the impure attribute nor the memo attribute should have any impact on the result value of a function call.

Taken care of by #354


mtl_transformer_ctc 模型论文

问下 ASR模型中，模型 mtl_transformer_ctc 的实现， 有对应的论文么

The paper for MTL training can be found here
The paper for transformer based ASR can be found here
The paper for MTL decoding can be found here


Cannot Install Application

Getting the following message when attempting to install in sandbox:
"The AppExchange package has been deprecated and can no longer be installed. Please try installing a newer version, or contact the package owner directly to resolve."
Am I using an outdated version?
Here's the link:
https://appexchange.salesforce.com/listingDetail?listingId=a0N3000000B45gWEAR

Yes, please see the README file for latest package link.


SSH Key Validation in onboarding

Fixes #30. Now SSH keys are validated that they have access to the specified repo. Uses a temp script that forces ssh keys and tries to call git ls-remote from the remote. Should help catch SSH key issues early.
Thanks, @accatyyc for help with this one!

Result of integration 1
Build failed 2 tests out of 11

Result of integration 2
Perfect build! All 9 tests passed. :+1:


Use generated code for all "Options" JS bindings.

TypeScript declarations and Java are still TBD.

wow this is cool. Did you find any "bugs"/"differences" compared to the manual implementations?

wow this is cool. Did you find any "bugs"/"differences" compared to the manual implementations?

The most common bug was incompleteness.  For example, many blue options were missing.


Features Request Board

I am planning to add a cache auto-expire feature
function Layout(){
  return (<KeepAlive maxAliveTime={"20s"}>
        {/*....*/}
  </KeepAlive>)
}

function Layout(){
  return (<KeepAlive maxAliveTime={{
   "admin/dashboard":"20s"
  }}>
        {/*....*/}
  </KeepAlive>)
}

Any plan to support react-router v7?

Any plan to support react-router v7?

in comming

Would you please make activeCacheKey optional instead of omit?
export interface KeepAliveRouteOutletProps extends Omit<KeepAliveProps, "activeCacheKey">

In my case, I have nested routes and I need to cache the outter outlet with more general name. If not, both outlet would have the active/inactive state change because they share the same key.
// url: /:parent/:child?foo=bar
<KeepAliveRouteOutlet activeCacheKey={parent_path}>  // cache by /:parent
    <KeepAliveRouteOutlet />  // cache as usual
</KeepAliveRouteOutlet>

Would you please make activeCacheKey optional instead of omit?

export interface KeepAliveRouteOutletProps extends Omit<KeepAliveProps, "activeCacheKey">

In my case, I have nested routes and I need to cache the outter outlet with more general name. If not, both outlet would have the active/inactive state change and break the transition.

// url: /:parent/:child?foo=bar

<KeepAliveRouteOutlet activeCacheKey={parent_path}>  // cache by /:parent

    <KeepAliveRouteOutlet />  // cache as usual

</KeepAliveRouteOutlet>

keepalive should be used on top level onece and subpages' layout use Outlet imported from react-router-dom

keepalive should be used on top level once and subpages' layout use Outlet imported from react-router-dom

Then I have 2 questions:

Does that mean the subpages' Outlets are NOT keep alived?
If so, does that mean this lib only supports top level keepalive (& transition)?

Thanks for answering

keepalive should be used on top level once and subpages' layout use Outlet imported from react-router-dom

Then I have 2 questions:

Does that mean the subpages' Outlets are NOT keeped alive?

If so, does that mean this lib only supports top level keepalive (& transition)?

Thanks for answering

There are cached together and have holistic transition， you can visit the demo website https://super-admin.tech/#/admin/nested/nested-1/nested-1-1

They are cached together and have holistic transition

Well, that's excatly my problem. The parent route should not be flickering with the child route.
My solution is to use <KeepAlive activeCacheKey={parentPath}/> to hold parent outlet and <KeepAliveRouteOutlet /> inside. The only thing I did is to gain fine-grain control over theactiveCacheKey instead of asserted location.path+location.search. And I did not see any nagetive impact on <KeepAliveRouteOutlet />side (to take it as an optional prop), from my point of view.
To me the KeepAliveRouteOutlet is a syntax sugar over the KeepAlive. I understand that it may be your design decision as a top-level wrapper, but it would be great for taking it into consideration.

They are cached together and have holistic transition

Well, that's excatly my problem. The parent route should not be flickering with the child route.
My solution is to use <KeepAlive activeCacheKey={parentPath}/> to hold parent outlet and <KeepAliveRouteOutlet /> inside. The only thing I did is to gain fine-grain control over theactiveCacheKey instead of asserted location.path+location.search. And I did not see any nagetive impact on <KeepAliveRouteOutlet />side (to take it as an optional prop), from my point of view.
To me the KeepAliveRouteOutlet is a syntax sugar over the KeepAlive. I understand that it may be your design decision as a top-level wrapper, but it would be great for taking it into consideration.

Great, I will make this feature released in the next version.

您好，请问未来会考虑“记住滚动条位置”这个功能吗？

How to restore the scrollbar to its previous position #17
未保存滚动条位置，如果table有虚拟滚动的话，会导致数据空白 #12

issues17和issues12，我都看了。对于简单页面或者只有一个滚动条的页面，上述方法确实可用。
我的项目里，页面比较多，也比较复杂。单个页面里可能有2个、3个、甚至多个滚动条。如果每个有滚动条的地方都用MemoScrollTopWrapper包裹一层的话，项目的代码改动量会很大。
如果keepalive-for-react本身支持记住滚动条位置，我项目里的子页面就无需改动，只改路由和顶层的几个根组件即可。
所以我想问一下，keepalive-for-react，未来会考虑增加“记住滚动条位置”这个功能吗？

这个库和 react router viewTransition api 存在冲突?


Contrastive loss should be applied to L2-normed embeddings instead of layer normed?

Hi @lucidrains, thank you for the implementation. Just wanted to confirm this with you, based on your code we're normalizing the img embedding and text embedding respectively using a learnable Layer Norm transformation before applying the contrastive loss. But based on my understanding, for contrastive loss we typically maximize the relative cosine similarity so the embeddings should be L2-normed instead of layernormed? Thank you.

@fedshyvana Hi Max! Indeed I made an error :pray: and it should be fixed here
Ugh, where would I be without smart PhD students reviewing my code haha

thank you!


Contract is not working

For some reason even given the fact I followed all the instructions - I face the following issues when trying to run a batch of 1 calls over 1 validator. Could you please check?
I also tried both compiled version from dockerhub and version I've compiled myself.
Fetching existing deposits
(node:7) UnhandledPromiseRejectionWarning: Error: This contract object doesn't have address set yet, please set an address first.
    at Object.ContractNoAddressDefinedError (/app/node_modules/web3-eth/node_modules/web3-core-helpers/lib/errors.js:122:16)
    at Contract._generateEventOptions (/app/node_modules/web3-eth/node_modules/web3-eth-contract/lib/index.js:534:22)
    at Contract.getPastEvents (/app/node_modules/web3-eth/node_modules/web3-eth-contract/lib/index.js:635:49)
    at getPastLogs (/app/scripts/deposit.js:133:21)
    at main (/app/scripts/deposit.js:73:26)
    at processTicksAndRejections (internal/process/task_queues.js:95:5)
(Use `node --trace-warnings ...` to show where the warning was created)
(node:7) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
(node:7) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code.

I was missing:
# address of the GBC deposit contract
DEPOSIT_CONTRACT_ADDRESS=0x0B98057eA310F4d31F2a452B414647007d1645d9

The documentation on https://docs.gnosischain.com/validator-info/validator-deposits/manual-deposit-method has been updated to reflect proper configuration for the deposit script. Thanks!


Swagger support

modified init, routes, and test_routes to make it support swagger docss
Significant modifications in routes to meet Swagger docs requirements
all modification has been covered by test, but the test coverage is still under 95%, need add more test case in future
lint test 9.94, all of four question about import, cannot be handled easily, will fix in future

I have checked CI test report and code, all error about import should be disabled because there are pylint comments, but looks like these pylint cannot be identified by CI, also cannot be identified by my local pylint


Beta unable to resume Sync if stopped

Describe the bug
When starting a sync attempt with the new db specifically the 0.2.0-beta.1 tag everything works fine
Logs are as expeccted
024-03-07T21:45:51.088706Z DEBUG provider::static_file: Commit segment=Transactions path="/root/.local/share/reth/mainnet/static_files/static_file_transactions_6500000_6999999" duration=8.485221ms
2024-03-07T21:45:51.089378Z DEBUG provider::static_file: Commit segment=Receipts path="/root/.local/share/reth/mainnet/static_files/static_file_receipts_0_499999" duration=574.081<C2><B5>s
2024-03-07T21:45:51.089980Z DEBUG provider::static_file: Commit segment=Headers path="/root/.local/share/reth/mainnet/static_files/static_file_headers_19000000_19499999" duration=530.265<C2><B5>s
2024-03-07T21:45:51.091622Z DEBUG storage::db::mdbx: Commit total_duration=1.558627ms commit_latency=Some(CommitLatency(MDBX_commit_latency { preparation: 0, gc_wallclock: 2, audit: 0, write: 0, sync:
96, ending: 0, whole: 99, gc_cputime: 0, gc_prof: MDBX_commit_latency__bindgen_ty_1 { wloops: 0, coalescences: 0, wipes: 0, flushes: 0, kicks: 0, work_counter: 0, work_rtime_monotonic: 0, work_xtime_cp
u: 0, work_rsteps: 0, work_xpages: 0, work_majflt: 0, self_counter: 0, self_rtime_monotonic: 0, self_xtime_cpu: 0, self_rsteps: 0, self_xpages: 0, self_majflt: 0 } })) is_read_only=false
2024-03-07T21:45:51.091700Z  INFO reth_node_core::events::node: Executing stage pipeline_stages=2/12 stage=Bodies checkpoint=6955000 target=19385733
2024-03-07T21:45:51.091715Z DEBUG sync::stages::bodies: Commencing sync stage_progress=6955001 target=19385733 start_tx_id=365799100

but after stopping the node and starting it back up again it is unable to connect to prysm and prysm is unable to connect to it.
the logs change as follows
2024-03-07T23:31:30.384083Z DEBUG storage::db::mdbx: Commit total_duration=1.347<C2><B5>s commit_latency=Some(CommitLatency(MDBX_commit_latency { preparation: 0, gc_wallclock: 0, audit: 0, write: 0, sync: 0, ending: 0, whole: 1, gc_cputime: 0, gc_prof: MDBX_commit_latency__bindgen_ty_1 { wloops: 0, coalescences: 0, wipes: 0, flushes: 0, kicks: 0, work_counter: 0, work_rtime_monotonic: 0, work_xtime_cpu: 0, work_rsteps: 0, work_xpages: 0, work_majflt: 0, self_counter: 0, self_rtime_monotonic: 0, self_xtime_cpu: 0, self_rsteps: 0, self_xpages: 0, self_majflt: 0 } })) is_read_only=true
2024-03-07T23:31:30.527650Z DEBUG storage::db::mdbx: Commit total_duration=1.836<C2><B5>s commit_latency=Some(CommitLatency(MDBX_commit_latency { preparation: 0, gc_wallclock: 0, audit: 0, write: 0, sync: 0, ending: 0, whole: 1, gc_cputime: 0, gc_prof: MDBX_commit_latency__bindgen_ty_1 { wloops: 0, coalescences: 0, wipes: 0, flushes: 0, kicks: 0, work_counter: 0, work_rtime_monotonic: 0, work_xtime_cpu: 0, work_rsteps: 0, work_xpages: 0, work_majflt: 0, self_counter: 0, self_rtime_monotonic: 0, self_xtime_cpu: 0, self_rsteps: 0, self_xpages: 0, self_majflt: 0 } })) is_read_only=true
2024-03-07T23:31:35.388570Z DEBUG storage::db::mdbx: Commit total_duration=1.967<C2><B5>s commit_latency=Some(CommitLatency(MDBX_commit_latency { preparation: 0, gc_wallclock: 0, audit: 0, write: 0, sync: 0, ending: 0, whole: 1, gc_cputime: 0, gc_prof: MDBX_commit_latency__bindgen_ty_1 { wloops: 0, coalescences: 0, wipes: 0, flushes: 0, kicks: 0, work_counter: 0, work_rtime_monotonic: 0, work_xtime_cpu: 0, work_rsteps: 0, work_xpages: 0, work_majflt: 0, self_counter: 0, self_rtime_monotonic: 0, self_xtime_cpu: 0, self_rsteps: 0, self_xpages: 0, self_majflt: 0 } })) is_read_only=true
2024-03-07T23:31:35.530038Z DEBUG storage::db::mdbx: Commit total_duration=2.588<C2><B5>s commit_latency=Some(CommitLatency(MDBX_commit_latency { preparation: 0, gc_wallclock: 0, audit: 0, write: 0, sync: 0, ending: 0, whole: 1, gc_cputime: 0, gc_prof: MDBX_commit_latency__bindgen_ty_1 { wloops: 0, coalescences: 0, wipes: 0, flushes: 0, kicks: 0, work_counter: 0, work_rtime_monotonic: 0, work_xtime_cpu: 0, work_rsteps: 0, work_xpages: 0, work_majflt: 0, self_counter: 0, self_rtime_monotonic: 0, self_xtime_cpu: 0, self_rsteps: 0, self_xpages: 0, self_majflt: 0 } })) is_read_only=true

I am able to get the db to start syncing again if i blow the db away
Steps to reproduce
Start reth and your choice of consensus engine
let it begin syncing
stop the node and let it gracefully shutdown,
restart reth observe it stops progressing
Node logs
2024-03-07T21:46:45.255151Z DEBUG storage::db::mdbx: Commit total_duration=1.569981ms commit_latency=Some(CommitLatency(MDBX_commit_latency { preparation: 0, gc_wallclock: 1, audit: 0, write: 0, sync:
97, ending: 0, whole: 99, gc_cputime: 0, gc_prof: MDBX_commit_latency__bindgen_ty_1 { wloops: 0, coalescences: 0, wipes: 0, flushes: 0, kicks: 0, work_counter: 0, work_rtime_monotonic: 0, work_xtime_cp
u: 0, work_rsteps: 0, work_xpages: 0, work_majflt: 0, self_counter: 0, self_rtime_monotonic: 0, self_xtime_cpu: 0, self_rsteps: 0, self_xpages: 0, self_majflt: 0 } })) is_read_only=false
2024-03-07T21:46:47.773384Z DEBUG reth::cli: shutting down gracefully
2024-03-07T21:46:47.774411Z  INFO reth::cli: Wrote network peers to file peers_file="/root/.local/share/reth/mainnet/known-peers.json"
2024-03-07T21:46:47.774433Z DEBUG reth_tasks: gracefully shut down
2024-03-07T23:05:15.163255Z  INFO reth::cli: Opening database path="/root/.local/share/reth/mainnet/db"
2024-03-07T23:05:15.172474Z  INFO reth::cli: Configuration loaded path="/root/.local/share/reth/mainnet/reth.toml"
2024-03-07T23:05:15.185811Z  INFO reth::cli: Database opened
2024-03-07T23:05:15.185829Z  INFO reth::cli: Starting metrics endpoint addr=<IP_ADDRESS>:9001
2024-03-07T23:05:15.186553Z DEBUG reth::cli: Initializing genesis chain=mainnet genesis=0xd4e56740f876aef8c010b86a40d5f56745a118d0906a34e69aec8c0db1cb8fa3
2024-03-07T23:05:15.187690Z DEBUG reth_node_core::init: Genesis already written, skipping.
2024-03-07T23:05:15.187904Z  INFO reth::cli: Pre-merge hard forks (block based):
- Frontier                         @0
- Homestead                        @1150000
- Dao                              @1920000
- Tangerine                        @2463000
- SpuriousDragon                   @2675000
- Byzantium                        @4370000
- Constantinople                   @7280000
- Petersburg                       @7280000
- Istanbul                         @9069000
- MuirGlacier                      @9200000
- Berlin                           @12244000
- London                           @12965000
- ArrowGlacier                     @13773000
- GrayGlacier                      @15050000
Merge hard forks:
- Paris                            @58750000000000000000000 (network is known to be merged)

Post-merge hard forks (timestamp based):
- Shanghai                         @1681338455
- Cancun                           @1710338135

2024-03-07T23:05:15.187916Z DEBUG reth::cli: Spawning stages metrics listener task
2024-03-07T23:05:15.192744Z DEBUG reth::cli: configured blockchain tree
2024-03-07T23:05:15.193091Z DEBUG reth::cli: creating components
2024-03-07T23:05:15.193671Z DEBUG txpool::blob: Removed blob store directory blob_dir="/root/.local/share/reth/mainnet/blobstore"
2024-03-07T23:05:15.193683Z DEBUG txpool::blob: Creating blob store blob_dir="/root/.local/share/reth/mainnet/blobstore"
2024-03-07T23:05:15.245017Z  INFO reth::cli: Transaction pool initialized
2024-03-07T23:05:15.245269Z DEBUG reth::cli: Spawned txpool maintenance task
2024-03-07T23:05:15.245309Z  INFO reth::cli: Connecting to P2P network
2024-03-07T23:05:15.245320Z DEBUG reth::cli: Loading p2p key file network_secret_path="/root/.local/share/reth/mainnet/discovery-secret"
2024-03-07T23:05:15.246505Z  INFO net::peers: Loading saved peers file=/root/.local/share/reth/mainnet/known-peers.json
2024-03-07T23:05:15.252224Z DEBUG discv4: pinging boot node record=NodeRecord { address: <IP_ADDRESS>, tcp_port: 30303, udp_port: 30303, id: 0xd860a01f9722d78051619d1e2351aba3f43f943f6f00718d1b9baa410
1932a1f5011f16bb2b1bb35db20d6fe28fa0bf09636d26a87d31de9ec6203eeedb1f666 }
2024-03-07T23:05:15.252284Z DEBUG discv4: pinging boot node record=NodeRecord { address: <IP_ADDRESS>, tcp_port: 30303, udp_port: 30303, id: 0x22a8232c3abc76a16ae9d6c3b164f98775fe226f0917b0ca871128a74a8
e9630b458460865bab457221f1d448dd9791d24c4e5d88786180ac185df813a68d4de }
2024-03-07T23:05:15.252320Z DEBUG discv4: pinging boot node record=NodeRecord { address: <IP_ADDRESS>, tcp_port: 30303, udp_port: 30303, id: 0x2b252ab6a1d0f971d9722cb839a42cb81db019ba44c08754628ab4a82
3487071b5695317c8ccd085219c3a03af063495b2f1da8d18218da2d6a82981b45e6ffc }
2024-03-07T23:05:15.252348Z DEBUG discv4: pinging boot node record=NodeRecord { address: <IP_ADDRESS>, tcp_port: 30303, udp_port: 30303, id: 0x4aeb4ab6c14b23e2c4cfdce879c04b0748a20d8e9b59e25ded2a08143
e265c6c25936e74cbc8e641e3312ca288673d91f2f93f8e277de3cfa444ecdaaf982052 }
2024-03-07T23:05:15.252876Z DEBUG discv4: pinging boot node record=NodeRecord { address: <IP_ADDRESS>, tcp_port: 30303, udp_port: 30303, id: 0xd860a01f9722d78051619d1e2351aba3f43f943f6f00718d1b9baa410
1932a1f5011f16bb2b1bb35db20d6fe28fa0bf09636d26a87d31de9ec6203eeedb1f666 }
2024-03-07T23:05:15.252908Z DEBUG discv4: pinging boot node record=NodeRecord { address: <IP_ADDRESS>, tcp_port: 30303, udp_port: 30303, id: 0x22a8232c3abc76a16ae9d6c3b164f98775fe226f0917b0ca871128a74a8
e9630b458460865bab457221f1d448dd9791d24c4e5d88786180ac185df813a68d4de }
2024-03-07T23:05:15.252911Z DEBUG discv4: pinging boot node record=NodeRecord { address: <IP_ADDRESS>, tcp_port: 30303, udp_port: 30303, id: 0x2b252ab6a1d0f971d9722cb839a42cb81db019ba44c08754628ab4a82
3487071b5695317c8ccd085219c3a03af063495b2f1da8d18218da2d6a82981b45e6ffc }
2024-03-07T23:05:15.252912Z DEBUG discv4: pinging boot node record=NodeRecord { address: <IP_ADDRESS>, tcp_port: 30303, udp_port: 30303, id: 0x4aeb4ab6c14b23e2c4cfdce879c04b0748a20d8e9b59e25ded2a08143
e265c6c25936e74cbc8e641e3312ca288673d91f2f93f8e277de3cfa444ecdaaf982052 }
2024-03-07T23:05:15.252940Z DEBUG igd_next::aio::tokio: sending broadcast request to: <IP_ADDRESS>:1900 on interface: Ok(<IP_ADDRESS>:51379)
2024-03-07T23:05:15.253069Z DEBUG reth::cli: calling on_component_initialized hook
2024-03-07T23:05:15.253412Z  INFO reth::cli: StaticFileProducer initialized
2024-03-07T23:05:15.254803Z  INFO reth::cli: Pruner initialized prune_config=PruneConfig { block_interval: 5, segments: PruneModes { sender_recovery: None, transaction_lookup: None, receipts: None, acc
ount_history: None, storage_history: None, receipts_log_filter: ReceiptsLogPruneConfig({}) } }
2024-03-07T23:05:15.254875Z  INFO reth::cli: Consensus engine initialized
2024-03-07T23:05:15.254913Z  INFO reth::cli: Engine API handler initialized
2024-03-07T23:05:15.254921Z DEBUG reth::cli: Reading JWT auth secret file user_path="/root/jwt/jwt.hex"
2024-03-07T23:05:15.255187Z DEBUG reth::cli: Using RPC module config http=Some(Selection([Eth, Net, Web3])) ws=None
2024-03-07T23:05:15.266427Z  INFO reth::cli: RPC auth server started url=<IP_ADDRESS>:8551
2024-03-07T23:05:15.267047Z  INFO reth::cli: RPC IPC server started url=/tmp/reth.ipc
2024-03-07T23:05:15.267063Z  INFO reth::cli: RPC HTTP server started url=<IP_ADDRESS>:8545
2024-03-07T23:05:15.267096Z  INFO reth::cli: Starting consensus engine
2024-03-07T23:05:15.268700Z DEBUG consensus::engine::hooks: Next hook is not ready hook="StaticFile"
2024-03-07T23:05:15.283453Z DEBUG disc::dns: Failed to lookup entry err=invalid child hash in branch:  domain=all.mainnet.ethdisco.net hash="FDXN3SN67NA5DKA4J2GOK7BVQI"
2024-03-07T23:05:17.328108Z DEBUG connection{ESC[3mremote_addrESC[0mESC[2m=ESC[0m<IP_ADDRESS>:59228 ESC[3mconn_idESC[0mESC[2m=ESC[0m0}: jsonrpsee_server::server: Accepting new connection 1/500
2024-03-07T23:05:18.257686Z  INFO reth::cli: Status connected_peers=0 freelist=13 latest_block=0
2024-03-07T23:05:21.384556Z DEBUG disc::dns: No dns entry domain=all.mainnet.ethdisco.net hash="6QKNDVNXUKNWQNCURI5BUQ"
2024-03-07T23:05:24.379767Z DEBUG disc::dns: No dns entry domain=all.mainnet.ethdisco.net hash="WEEBRG5GPKFH5V563N7I4P"
2024-03-07T23:05:25.255606Z DEBUG net::nat: Failed to resolve external IP via UPnP: failed to find gateway err=IO error: search timed out
2024-03-07T23:05:25.289620Z DEBUG discv4: Updating external ip external_ip=
2024-03-07T23:05:25.508200Z DEBUG storage::db::mdbx: Commit total_duration=2.961<C2><B5>s commit_latency=Some(CommitLatency(MDBX_commit_latency { preparation: 0, gc_wallclock: 0, audit: 0, write: 0, sync: 0, ending: 0, whole: 1, gc_cputime: 0, gc_prof: MDBX_commit_latency__bindgen_ty_1 { wloops: 0, coalescences: 0, wipes: 0, flushes: 0, kicks: 0, work_counter: 0, work_rtime_monotonic: 0, work_xtime_cpu: 0, work_rsteps: 0, work_xpages: 0, work_majflt: 0, self_counter: 0, self_rtime_monotonic: 0, self_xtime_cpu: 0, self_rsteps: 0, self_xpages: 0, self_majflt: 0 } })) is_read_only=true
2024-03-07T23:05:25.647629Z DEBUG storage::db::mdbx: Commit total_duration=2.844<C2><B5>s commit_latency=Some(CommitLatency(MDBX_commit_latency { preparation: 0, gc_wallclock: 0, audit: 0, write: 0, sync: 0, ending: 0, whole: 1, gc_cputime: 0, gc_prof: MDBX_commit_latency__bindgen_ty_1 { wloops: 0, coalescences: 0, wipes: 0, flushes: 0, kicks: 0, work_counter: 0, work_rtime_monotonic: 0, work_xtime_cpu: 0, work_rsteps: 0, work_xpages: 0, work_majflt: 0, self_counter: 0, self_rtime_monotonic: 0, self_xtime_cpu: 0, self_rsteps: 0, self_xpages: 0, self_majflt: 0 } })) is_read_only=true

Platform(s)
Linux (x86)
What version/commit are you on?
reth Version: 0.2.0-beta.1 Commit SHA: aec59b73 Build Timestamp: 2024-03-07T17:10:28.313032547Z Build Features: jemalloc Build Profile: maxperf
What database version are you on?
reth db version
Current database version: 2
Local database version: 2
What type of node are you running?
Archive (default)
What prune config do you use, if any?
No response
If you've built Reth from source, provide the full command you used
docker build . -t local-reth-beta --build-arg BUILD_PROFILE=maxperf --build-arg FEATURES=jemalloc,asm-keccak
Code of Conduct

[X] I agree to follow the Code of Conduct

    volumes:
      - rethdata_mainnet:/root/.local/share/reth/mainnet
      - rethdata_sepolia:/root/.local/share/reth/sepolia
      - rethlogs:/root/rethlogs
      - ./jwttoken:/root/jwt:ro

also works fine

Thanks! @joshieDo @shekhirin

@argakiig can you also share the CL logs? I don't see any forkchoice updates in Reth logs, and we can't start the sync without at least one.

It's currently a day and a half into the latest sync, I don't wanna try and repro currently, using l
Prysm, 5.0.1 and it seems to be working currently

updated to the latest v0.2.0-beta1 tag at 66c9403e and the networking issues seem to have gone away. In checking my logs yes prysm was also having network issues at the time..
It also appears that the issue I was seeing where my tracked peers decrease instead of increase over time has gone away with the above update. I am going to close this out. Thanks for including the directory changes as well :)


Mobile Play

I created a page on my site at https://boredhumans.com/chess.php using your program, but it is hard to get the pieces to move on my iPhone.  I can't drag them like on PC, I have to click the piece first (which then makes a giant sized version of it pop up which I then have to click again get off the screen) and then click where I want it to go.  Any suggestions on how to improve that?

Hi,
Add the code below at the beginning of the main.js file :
function touchHandler(event) {
var touch = event.changedTouches[0];
var simulatedEvent = document.createEvent("MouseEvent");
    simulatedEvent.initMouseEvent({
    touchstart: "mousedown",
    touchmove: "mousemove",
    touchend: "mouseup"
}[event.type], true, true, window, 1,
    touch.screenX, touch.screenY,
    touch.clientX, touch.clientY, false,
    false, false, false, 0, null);

touch.target.dispatchEvent(simulatedEvent);
event.preventDefault();

}
function init() {
var d = document.querySelectorAll("#myBoard img");
for (var i = 0; i < d.length; i++) {
d[i].addEventListener("touchstart", touchHandler, true);
d[i].addEventListener("touchmove", touchHandler, true);
d[i].addEventListener("touchend", touchHandler, true);
d[i].addEventListener("touchcancel", touchHandler, true);
}
}
and at the  of the file add : init();
Should work now on mobile devices.....

Maybe you could port chess-ai from "chessboard" to "chessboard2" (https://github.com/oakmac/chessboard2) ? It has much better mobile devices touch support. It even works with Amazon Kindle devices.


build: use twine check --strict instead of python setup.py check -s -m

https://github.com/pypyr/pypyr/blob/master/ops/build.yaml#L22 expects twine to be used in future to test the metadata.
According to: https://packaging.python.org/guides/making-a-pypi-friendly-readme/#validating-restructuredtext-markup and my quick check this time is already here.
However, as twine is able to do the check only on built package, the question is, where to put it. I would think of moving i to packaging and forget about it in the lint.

Thanks for looking into this @vlcinsky, much appreciated! It was about time to check on where twine is at with the check progress, so thank you!
setup.py check -m -s does more than just validate the README.
Compare https://hg.python.org/cpython/file/6969bac411fa/Lib/distutils/command/check.py to https://github.com/pypa/twine/blob/main/twine/commands/check.py
ln 82 in distutils check.py is of especial interest - the check_metadata function. There are required metadata checks for name, version, url and some checks on author/maintainer emails. These checks are in setup.py check -m, but I don't see them in twine --check (yet). Unless I'm missing it, in which case please feel free to correct me!
By the way, twine check is actually irrelevant for .md validation. . . so in the case of pypyr we've got a README.md rather than README.rst, it's not validating the README anyway.
You raise a very valid point, though, which is when the check moves to twine we're going to have to re-think where to put it, and yes you're right, it'll prob have to go to the package step-group - it's actually there already, it's just not doing much under the covers in this case (since pypyr has an .md).

Superseded by new flit PEP 517 build front-end. #289


Push Fails and Documentation isn't Helping to Resolve

@dankuchem Thanks for the Feedback.
Can you please share the link of the document you are referring to.

@dankuchem Any update on this?

I got this part working, but I'm now stuck with an issue on one of the other tutorials in the group on AKS.  It's a well done site, but I think the documentation may need some updating.
dk
From: VikasPullagura-MSFT @.>
Sent: Friday, March 26, 2021 12:50 AM
To: MicrosoftDocs/azure-docs @.>
Cc: Dan Kuchem @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Push Fails and Documentation isn't Helping to Resolve (#72732)
@dankuchemhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdankuchem&data=04|01|dankuchem%40microsoft.com|deea381eb0bd4a943f0608d8f012ae64|72f988bf86f141af91ab2d7cd011db47|1|0|637523310317549762|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=N6MNuTdWQ1WRTIhOW0M3JsRAeyzk0b239lWcpQvfQdg%3D&reserved=0 Any update on this?

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F72732%23issuecomment-807932956&data=04|01|dankuchem%40microsoft.com|deea381eb0bd4a943f0608d8f012ae64|72f988bf86f141af91ab2d7cd011db47|1|0|637523310317559763|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=J7sd1P4JQADdy1NykQ0L5BmmRweWUQJ%2F%2BA0fsVz46IU%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FATFTVSEQJF5DCTKH5NBMLYDTFQHBLANCNFSM4ZYKGZWQ&data=04|01|dankuchem%40microsoft.com|deea381eb0bd4a943f0608d8f012ae64|72f988bf86f141af91ab2d7cd011db47|1|0|637523310317559763|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=xkgh0UKDtTYXrrG9e7DswXwqLa7%2FCTbWDZFYQF15Xdg%3D&reserved=0.

@dankuchem Can you share the document link which needs updating, share your feedback along with the document link. I will share the feedback with the document author team for updating.

Vikas:
Thanks - it may well be that it's because I'm new at this (My role also doesn't require a deep AKS skill set, but does require I can work with basic concepts.)
The Tutorial # 4 - Run Application asks you to update the Manifest file, which I previously uploaded via the Azure Portal - Azure Cloud Shell Bash cut & past input.  The yellow-highlighted below make the assumption that you can connect with / find the yaml file created in Tutorial # 1 (Prepare Application for AKS) to update line # 60 of the yaml to put your own ACR login server name in.
I successfully went through tutorials 1 - 3 and tested the functionality.  I also did not delete the image when a executed the "docker-compose down" command in Tutorial # 1 of the series.
@.***D72241.081A02E0]
@.***D72241.E1D01C90]
Regards,
Dan Kuchem
Azure App Dev Specialist, Microsoft
+1<PHONE_NUMBER>tel:+1<PHONE_NUMBER>
|
<EMAIL_ADDRESS>@.***D72241.E1D01C90]
From: VikasPullagura-MSFT @.>
Sent: Friday, March 26, 2021 8:17 AM
To: MicrosoftDocs/azure-docs @.>
Cc: Dan Kuchem @.>; Mention @.>
Subject: Re: [MicrosoftDocs/azure-docs] Push Fails and Documentation isn't Helping to Resolve (#72732)
@dankuchemhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fdankuchem&data=04|01|dankuchem%40microsoft.com|5c64ed6cbf0447a6624808d8f0510a43|72f988bf86f141af91ab2d7cd011db47|1|0|637523578142710360|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=7RxOZjE%2Bw9kBiSKvzR7ttIoHgd%2BO0FdvrD1zK8fciww%3D&reserved=0 Can you share the document link which needs updating, share your feedback along with the document link. I will share the feedback with the document author team for updating.

You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F72732%23issuecomment-808170663&data=04|01|dankuchem%40microsoft.com|5c64ed6cbf0447a6624808d8f0510a43|72f988bf86f141af91ab2d7cd011db47|1|0|637523578142720357|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=wyJY4UCPVdhxL%2FHljL6MuSw3h1o9o%2BHTJUR7C%2FRrRm0%3D&reserved=0, or unsubscribehttps://nam06.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FATFTVSEXTZIBMKPUDMGSNJLTFR3LJANCNFSM4ZYKGZWQ&data=04|01|dankuchem%40microsoft.com|5c64ed6cbf0447a6624808d8f0510a43|72f988bf86f141af91ab2d7cd011db47|1|0|637523578142720357|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=h5FGVyiwJaqiyCfGhf4EwOKUbqM2iCnnBbcb8OB2W4k%3D&reserved=0.

Thanks for sharing the details. I have assigned the issue to the content author to investigate further and update the document as appropriate.

Thank you @dankuchem for the feedback.
I'm unclear about where you're running into issues.
In this section:
https://docs.microsoft.com/azure/aks/tutorial-kubernetes-deploy-application?tabs=azure-cli#update-the-manifest-file
the action is to update the manifest you cloned from the git repository to your development computer. You then use that updated file in the next section.
#please-close