failed to analyze lowered AST: SemanticError { kind: AlreadyDefined, context: [] } at compiler/src/lib.rs:55:59

Compiling this file:
contract Foo:
        my_other_tuple: (address, address)
struct tuple_address_address:
        value: u256

thread 'main' panicked at 'failed to analyze lowered AST: SemanticError { kind: AlreadyDefined, context: [] }', compiler/src/lib.rs:54:60
stack backtrace:
   0:     0x556704b0e390 - std::backtrace_rs::backtrace::libunwind::trace::h9d49145f95eb5894
                               at /rustc/9c09c1f7cfcf9de0522bcd1cfda32b552195c464/library/std/src/../../backtrace/src/backtrace/libunwind.rs:90:5
   1:     0x556704b0e390 - std::backtrace_rs::backtrace::trace_unsynchronized::hab1d020365bb6864
                               at /rustc/9c09c1f7cfcf9de0522bcd1cfda32b552195c464/library/std/src/../../backtrace/src/backtrace/mod.rs:66:5
   2:     0x556704b0e390 - std::sys_common::backtrace::_print_fmt::h7659588431e304bd
                               at /rustc/9c09c1f7cfcf9de0522bcd1cfda32b552195c464/library/std/src/sys_common/backtrace.rs:67:5
   3:     0x556704b0e390 - <std::sys_common::backtrace::_print::DisplayBacktrace as core::fmt::Display>::fmt::h09f4a9e3befae3c7
                               at /rustc/9c09c1f7cfcf9de0522bcd1cfda32b552195c464/library/std/src/sys_common/backtrace.rs:46:22
   4:     0x556704b280ec - core::fmt::write::hf3fdfde304b9a088
                               at /rustc/9c09c1f7cfcf9de0522bcd1cfda32b552195c464/library/core/src/fmt/mod.rs:1092:17
   5:     0x556704b0b2f2 - std::io::Write::write_fmt::h1cb850689c7116f0
                               at /rustc/9c09c1f7cfcf9de0522bcd1cfda32b552195c464/library/std/src/io/mod.rs:1568:15
   6:     0x556704b10555 - std::sys_common::backtrace::_print::hdbccd5aa093ba544
                               at /rustc/9c09c1f7cfcf9de0522bcd1cfda32b552195c464/library/std/src/sys_common/backtrace.rs:49:5
   7:     0x556704b10555 - std::sys_common::backtrace::print::hc639c4f320222558
                               at /rustc/9c09c1f7cfcf9de0522bcd1cfda32b552195c464/library/std/src/sys_common/backtrace.rs:36:9
   8:     0x556704b10555 - std::panicking::default_hook::{{closure}}::hdb012dd7a485bb5d
                               at /rustc/9c09c1f7cfcf9de0522bcd1cfda32b552195c464/library/std/src/panicking.rs:208:50
   9:     0x556704b10003 - std::panicking::default_hook::h75facbce77b6ba91
                               at /rustc/9c09c1f7cfcf9de0522bcd1cfda32b552195c464/library/std/src/panicking.rs:225:9
  10:     0x55670423ef1f - fe_compiler::errors::DEFAULT_PANIC_HOOK::{{closure}}::{{closure}}::hd71e839699e0bfd6

You've hit an internal compiler error. This is a bug in the Fe compiler.
Fe is still under heavy development, and isn't yet ready for production use.

If you would, please report this bug at the following URL:
  https://github.com/ethereum/fe/issues/new
Aborted

I'm not sure this crashes on latest.  When I try to build, I get:
   Compiling typenum v1.13.0
   Compiling semver v1.0.0
   Compiling num-traits v0.2.14
   Compiling regex v1.5.2
   Compiling serde v1.0.125
   Compiling rand v0.7.3
   Compiling vec1 v1.8.0
   Compiling solc v0.1.0 (https://github.com/g-r-a-n-t/solc-rust#fcb91059)
error[E0658]: the `unsafe_op_in_unsafe_fn` lint is unstable
  --> /home/user/.cargo/registry/src/github.com-1ecc6299db9ec823/semver-1.0.0/src/lib.rs:66:50
   |
66 | #![cfg_attr(not(no_unsafe_op_in_unsafe_fn_lint), deny(unsafe_op_in_unsafe_fn))]
   |                                                  ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
   |
   = note: see issue #71668 <https://github.com/rust-lang/rust/issues/71668> for more information
   = help: add `#![feature(unsafe_block_in_unsafe_fn)]` to the crate attributes to enable

error: aborting due to previous error

For more information about this error, try `rustc --explain E0658`.
error: could not compile `semver`

To learn more, run the command again with --verbose.
warning: build failed, waiting for other jobs to finish...
error: build failed

[profile.dev]
debug = true
panic = "abort"

for fuzzing.  Using https://github.com/agroce/afl-compiler-fuzzer

Yes, after a rust uninstall/install nightly, I was able to build (though not the solc backend, solc compile fails due to some missing file...) and:
Warning: bytecode output requires 'solc-backend' feature. Try `cargo build --release --features solc-backend`. Skipping.
thread 'main' panicked at 'failed to analyze lowered AST: AnalyzerError { diagnostics: [], classic: Some(SemanticError { kind: AlreadyDefined, context: [] }) }', compiler/src/lib.rs:55:59
note: run with `RUST_BACKTRACE=1` environment variable to display a backtrace

You've hit an internal compiler error. This is a bug in the Fe compiler.
Fe is still under heavy development, and isn't yet ready for production use.

If you would, please report this bug at the following URL:
  https://github.com/ethereum/fe/issues/new
Aborted

error[E0658]: the unsafe_op_in_unsafe_fn lint is unstable

This was stabilized in rust 1.52; it should build on non-nightly rust if you rustup update stable.

I'll work on this.
ref: #377

I'll work on #326 first and rewrite lowering tests, currently which doesn't work when an unexpected symbol is prepended in lowering pass like $.

This particular issue doesn't seem to be a problem anymore with the generated tuple being named $tuple_address_address_ now. There is still #477 with ideas to generally improve the naming strategy but it seems that this concrete bug is already fixed.


FastAPI - Starter Policy Sample Application

This pull request introduces a sample application, based on the oso-sdk FastAPI integration. It uses the upcoming "Starter Policy" functionality from Oso Cloud.
The sample application demonstrates how to use the @oso.enforce decorators to protect routes. It's meant as a sort of tutorial for using the library - every route will return a 404 Not Found at first, but by adding specific facts (which are described in the documentation and in source docstrings), you can get each route returning a 200 OK!

Really like the comments. Not blocking but I wonder if we need to include the distinction of anonymous vs admin for the sake of a sample app. I think it would still be valuable to include the comment on the user_from_request function to highlight that they could discover the user from the request. IMO, we can achieve the same functionality with a single user and it would simplify the descriptions since we can assume that there will only be a single user.

Thanks for the feedback, totally agreed on all comments. What do you think of this latest revision, @uncommoncense?


Environment
Docker
Version
0.11.5
Describe the problem
dash的小挂件在外网情况下，无法显示，内网是正常的，这个问一下，是因为安全性问题禁用了外网显示吗？
dash主程序是可以在外网显示的
Logs

Context
No response
Please tick the boxes

[X] I confirm that I attached the proper logs
[X] I've read the docs
[X] I've checked for duplicate issues
[X] I've tried to debug myself

Hey @jiaoting , we do not offer support in languages other than English because we do not speak them. Could you please translate your issue in English?

Dash widget in the case of the network, can not be displayed, the network is normal, this question, is because of security issues to disable the network display?
The dash main program can be displayed on the external network

Closing this, because the duplicate is in english.

Dash widget in the case of the network, can not be displayed, the network is normal, this question, is because of security issues to disable the network display?
The dash main program can be displayed on the external network

Use the external address for Dash. It is an iFrame so you need to use the external address because the browser will generate it (so local address doesn’t work)

I just use external address for Dash。


Are there OpenDrive alternatives for Carla to import lane graph?

Hi team, I think Carla uses OpenDrive data format to define the relationship between road. Is it the only way that Carla supports? Right now, I have lane graph defined in vector format, e.g. in GeoJSon or .shp file. However, the only way I know to convert from vector format to opendrive data format is using RoadRunner, which is not a free tool.
So my question is, is there other ways for me to add my lane graph representation (in the format of geojson) to Carla? Thanks a lot!

Unfortunately not, OpenDRIVE is currently the only format supported.

They should match the fbx in world coordinates, bear in mind UE4 uses left-handed axis and centimeters, sometimes things appear reflected depending on how you export the files.
When you import you should see a lot of trigger boxes and splines along the road, those are generated based on the XODR, that should help you debugging.

It remains as XODR, you can retrieve it in the API with world.get_map().to_opendrive().


Support specifying target_type

https://github.com/WiserSolutions/terraform-aws-lb/blob/master/main.tf#L378 Should be decommented and it should be possible to declare the instance type.
Currently this module is not usable with Fargate because of this.

I'm not currently doing anything with Fargate. Do you know if this is the only change needed to support Fargate? If so, easy to create a variable for it.

AFAICT this is the only required change. I'm trying to create a fargate-backed lb using a local copy of v3.3.0 of this module, will let you know ASAP.

I created branch 'target-type' with the changes for this. But have not had time to do any testing

Merged and released as v3.5.0


Rework exceptions to be native types

This is a rework of pyo3's exception types to be more in line with the rest of the Python native types.
I introduce new exception types PyException, PyRuntimeError etc. These must be accessed through either Py<PyBaseException>, Py<PyRuntimeError> or gil-scoped references &PyBaseException , &PyRuntimeError, just like other native types.
To minimise breakage the old types Exception, RuntimeError continue to exist and behave as they did before, but I mark them deprecated with a suggestion to use the new types.
I think this is an important first step of #295 - we should then be able to make something very similar to #[pyclass] for exceptions. It should also enable #682 to be done relatively cleanly by building off these implementations.
I based this PR on the work of #686, which I think can now be closed. As well as Py<PyBaseException>, I was able to implement std::error::Error for Py<T> and &T for all the error types T.
This PR will introduce a couple of minor breaking changes, but I think it's worth it:

PyBorrowError and PyBorrowMutError no longer have dedicated Python types and just raise RuntimeError in Python.
I could undo this change, however the try_borrow() would have to return &PyBorrowError and we'll take a little performance hit.
The imported exceptions e.g. socket::herror are now only accessible as native types; existing code using these will break slightly.

If you like this, I'll press ahead with documentation.
TODO:

[ ] Documentation EDIT: I'm going to write docs after some follow-up PRs, when it's easier to see what the final result looks like.

Thank you, looks good except the approach to the breaking change(i.e., Py prefix) :thinking:
Is there any simpler solution? (e.g., type Exception = Py<PyException>)

Is there any simpler solution? (e.g., type Exception = Py)

I think any alternative, including the above, would break more user code than this PR already does.
The simplest alternative would be to embrace the breaking change and just remove the old types.

The simplest alternative would be to embrace the breaking change and just remove the old types.

If you think it's okay, I would be very happy to do this. It keeps the pyo3 codebase smaller and I can document these breaking changes immediately in the migration guide.

How about
type BaseException = PyBaseException;

?
This is enough for me.

How about
type BaseException = PyBaseException;

?
This is enough for me.

sounds good to me if it's marked deprecated

Agreed marking the old functionality as deprecated. I'll try to finish off this PR at the weekend.

I've updated this PR and rebased.
I was originally intending to write more documentation as part of this PR, but now as I've been thinking about related designs such as impl std::error::Error for PyErr I want to get those into shape before writing new docs.


Stability analysis: add number of roots for Davidson solver

Hi devs!
Problem description
I just found for a varity of radicals, wavefunction stability analysis does not show correct judgement.
This is because not enough number of roots are required for davidson solver (orbital hessian diagonalization). Then this solver may not give the lowest eigenvalue in some cases.
Reporduction of this problem
An example could be molecule F2 (spin=0).
from pyscf import gto, scf
from pyscf.scf.stability import rhf_external

if __name__ == '__main__':
    mol = gto.Mole(atom="F; F 1 1.4113", basis="6-31G").build()
    mf = scf.RHF(mol).run()
    rhf_external(mf)

Before this pull request, stability found minimum excitation for RHF->UHF instability is 0.07058134 Hartree and thus F2 is stable. This may be not correct.
To show this value, one need to debug program at https://github.com/pyscf/pyscf/blob/0df2ead0cc9b80a1b8bf0f26b5d1755baf1a472f/pyscf/scf/stability.py#L388.
After this PR
When set logger level as debug, we may see lowest three eigenvalues to be
rhf_external: lowest eigs (e3) of H = [-0.10795055  0.07058127  0.07058504]

This gives correct RHF->UHF instability of F2 molecule.
Variable STAB_NROOTS indicates space of davidson solver for stability check. I hardcoded this value to be 3.
It seems that recommended value of number of roots are: QChem 2; ORCA 3; Gaussian 6 first time, 3 second time.
Additional notes
This PR modification will increase computational resources for stability analysis.
Convergence criteria of lowest eigenvalue in PySCF is prehaps 1e-4 amplitude (tol=1e-4).
Criteria of Gaussian seems to be extremely loose (0.01 eV). In example of ORCA manual, this value is 1e-4 Hartree.
So maybe efficiency of stability check in PySCF can be further elevated by tatics of convergence.

I agree. I've observed similar issue from insufficient roots before, too.

Convergence criteria of lowest eigenvalue in PySCF is prehaps 1e-4 amplitude (tol=1e-4).
Criteria of Gaussian seems to be extremely loose (0.01 eV).

I think 1e-4 is loose enough. And in some edge cases it's not tight enough. So I made it an option in this PR.

There's 2 failed tests for the first CI build:
FAILED pyscf/scf/test/test_stability.py::KnownValues::test_uhf_stability - As...
FAILED pyscf/scf/test/test_stability.py::KnownValues::test_uhf_stability_with_status
=== 2 failed, 2239 passed, 163 deselected, 28 warnings in 4149.25s (1:09:09) ===
Error: Process completed with exit code 1.

Did you try to run all the tests (and make sure they pass) before opening the pull request?

@ndattani I'd admit that I didn't run tests before this PR. Thanks for reminder!
I suggest to lower the criteria threshold of unittests in scf.test.test_stability.
Before this additional commit (22e6485), tests does not pass when evaluating overlap between original molecular coefficients mf1.mo_coeff and initial guess after stability check for external UHF mo_e.
This overlap changes a bit (up to about 1e-6) when increasing number of roots STAB_NROOTS from 1 to 3.
For my view, this overlap change is quite minor, as well as initial guess still gives correct ground state after GHF SCF process; so loosen the threshold of overlap check does not invalidates purpose of this unittest.

I see that you got the tests to pass by changing the testing criteria in the test itself, from matching 6 digits to matching only 5 digits for s:
s = mf1.det_ovlp(mo_e, mf1.mo_coeff, mf1.mo_occ, mf1.mo_occ,mf1.get_ovlp())[0]

Why is it that this ovlp can't be made to agree in 6 digits when you make STAB_NROOTS = 3?

@ndattani I couldn't fully resolve your concern currently. Some new problem found, and may occur in function lib.davidson1; and I don't know how to handle that.

The reason of ovlp can't be made to agree in 6 digits, is that this test almostly must run when nroots = 1 as well as tol = 1e-4 for davidson solver. Otherwise, test may fail. even increasing threshold of davidson solver (giving more precise eigen solution) can fail.
To demonstrate this, I extracted and modified some source codes from PySCF, in the following collapsed code block. Function deviate refers to deviate of the molecular orbital coefficient overlap between computed result and known value.

Definition of function `deviate`
from pyscf import gto, scf, lib
import numpy
import numpy as np
import scipy
from pyscf.scf.stability import _gen_hop_uhf_external
from pyscf.soscf import newton_ah
from pyscf.lib import logger

np.set_printoptions(6, suppress=True, linewidth=150)

def uhf_external(mf, with_symmetry=True, verbose=None, return_status=False, tol=1e-4, nroots=1):
    log = logger.new_logger(mf, verbose)
    hop1, hdiag1, hop2, hdiag2 = _gen_hop_uhf_external(mf, with_symmetry)
    stable = True

    def precond(dx, e, x0):
        hdiagd = hdiag2 - e
        hdiagd[abs(hdiagd)<1e-8] = 1e-8
        return dx/hdiagd
    x0 = numpy.zeros_like(hdiag2)
    x0[hdiag2>1e-5] = 1. / hdiag2[hdiag2>1e-5]
    if not with_symmetry:  # allow to break point group symmetry
        x0[numpy.argmin(hdiag2)] = 1
    e3, v = lib.davidson(hop2, x0, precond, tol=tol, nroots=nroots, verbose=log)
    if nroots != 1:
        e3, v = e3[0], v[0]
    log.debug('uhf_external: lowest eigs of H = %s', e3)
    mo = scipy.linalg.block_diag(*mf.mo_coeff)
    if e3 < -1e-5:
        log.note(f'{mf.__class__} wavefunction has an UHF/UKS -> GHF/GKS instability.')
        occidxa = numpy.where(mf.mo_occ[0]> 0)[0]
        viridxa = numpy.where(mf.mo_occ[0]==0)[0]
        occidxb = numpy.where(mf.mo_occ[1]> 0)[0]
        viridxb = numpy.where(mf.mo_occ[1]==0)[0]
        nocca = len(occidxa)
        nvira = len(viridxa)
        noccb = len(occidxb)
        nvirb = len(viridxb)
        nmo = nocca + nvira
        dx = numpy.zeros((nmo*2,nmo*2))
        dx[viridxa[:,None],nmo+occidxb] = v[:nvira*noccb].reshape(nvira,noccb)
        dx[nmo+viridxb[:,None],occidxa] = v[nvira*noccb:].reshape(nvirb,nocca)
        u = newton_ah.expmat(dx - dx.conj().T)
        mo = numpy.dot(mo, u)
        mo = numpy.hstack([mo[:,:nocca], mo[:,nmo:nmo+noccb],
                           mo[:,nocca:nmo], mo[:,nmo+noccb:]])
        stable = False
    else:
        log.note(f'{mf.__class__} wavefunction is stable in the UHF/UKS -> '
                 'GHF/GKS stability analysis')
    return mo, stable, e3, v

def uhf_external_exact(mf, with_symmetry=True, verbose=None, return_status=False):
    log = logger.new_logger(mf, verbose)
    hop1, hdiag1, hop2, hdiag2 = _gen_hop_uhf_external(mf, with_symmetry)
    stable = True

    dim = hdiag2.size
    h = np.zeros((dim, dim))
    for i in range(dim):
        vi = np.zeros(dim)
        vi[i] = 1
        h[i] = hop2(vi)
    e3, v = np.linalg.eigh(h)
    v = v.T
    e3, v = e3[0], v[0]
    log.debug('uhf_external: lowest eigs of H = %s', e3)
    mo = scipy.linalg.block_diag(*mf.mo_coeff)
    if e3 < -1e-5:
        log.note(f'{mf.__class__} wavefunction has an UHF/UKS -> GHF/GKS instability.')
        occidxa = numpy.where(mf.mo_occ[0]> 0)[0]
        viridxa = numpy.where(mf.mo_occ[0]==0)[0]
        occidxb = numpy.where(mf.mo_occ[1]> 0)[0]
        viridxb = numpy.where(mf.mo_occ[1]==0)[0]
        nocca = len(occidxa)
        nvira = len(viridxa)
        noccb = len(occidxb)
        nvirb = len(viridxb)
        nmo = nocca + nvira
        dx = numpy.zeros((nmo*2,nmo*2))
        dx[viridxa[:,None],nmo+occidxb] = v[:nvira*noccb].reshape(nvira,noccb)
        dx[nmo+viridxb[:,None],occidxa] = v[nvira*noccb:].reshape(nvirb,nocca)
        u = newton_ah.expmat(dx - dx.conj().T)
        mo = numpy.dot(mo, u)
        mo = numpy.hstack([mo[:,:nocca], mo[:,nmo:nmo+noccb],
                           mo[:,nocca:nmo], mo[:,nmo+noccb:]])
        stable = False
    else:
        log.note(f'{mf.__class__} wavefunction is stable in the UHF/UKS -> '
                 'GHF/GKS stability analysis')
    return mo, stable, e3, v

def deviate(mo):
    global mf_ghf
    ovlp_known_value = 0.57993272190912937
    return mf_ghf.det_ovlp(
        mo, mf_ghf.mo_coeff, mf_ghf.mo_occ, mf_ghf.mo_occ, mf_ghf.get_ovlp())[0] - ovlp_known_value

Then we see that, either adding nroots or decreasing tol, or both, will give about 8e-7 deviation, which usually changes a 6th digit.
# note: symmetry = 1
mol = gto.M(atom='O 0 0 0; O 0 0 1.2222', basis='631g*', symmetry=1,
            spin=2, verbose=5, output='/dev/null')
mf = scf.ROHF(mol).run(conv_tol=1e-12)
mf = mf.to_uks()
mf_ghf = mf.to_ghf()

deviate(uhf_external(mf)[0])
# 1.3322676295501878e-15
deviate(uhf_external(mf, tol=1e-12)[0])
# 8.503216496480448e-07
deviate(uhf_external(mf, nroots=3)[0])
# 8.76435113594809e-07
deviate(uhf_external(mf, nroots=144, tol=1e-12)[0])
# -0.4577170240997388; this may be erronuous
deviate(uhf_external_exact(mf)[0])
# 8.503105437540626e-07

I guess that known value 0.57993272190912937 unittest is generated by condition nroots = 1 and tol = 1e-4, which is approximately correct but not exact. The better reference value should be 0.5799335722196731.
But I think, that since stability check only requires to provide qualitatively correct stability and initial mo_coeff guess, this level (8e-7 in mo_coeff overlap) of precision loss is tolarable. I still think that matching only 5 digits does not invalidates purpose of this unittest.

But I'd note that if increases nroots to 144, this example of ROHF/6-31G* dioxygen with symmetry will fail, as the code above shows. I'm not sure whether this is numerical instability or internal error of lib.davidson1.
If symmetry is set to False (C1), then no problem occurs.
# note: symmetry = 0
mol = gto.M(atom='O 0 0 0; O 0 0 1.2222', basis='631g*', symmetry=0,
            spin=2, verbose=5, output='/dev/null')
mf = scf.ROHF(mol).run(conv_tol=1e-12)
mf = mf.to_uks()
mf_ghf = mf.to_ghf()

deviate(uhf_external(mf)[0])
# 5.6036550242222205e-06
deviate(uhf_external(mf, tol=1e-12)[0])
# 8.49294683247237e-07
deviate(uhf_external(mf, nroots=3)[0])
# 8.864743483716353e-08
deviate(uhf_external(mf, nroots=144, tol=1e-12)[0])
# 8.503105506374453e-07; this is the correct value
deviate(uhf_external_exact(mf)[0])
# 8.503105519697129e-07

But I'd note that if increases nroots to 144, this example of ROHF/6-31G* dioxygen with symmetry will fail, as the code above shows.

I can't reproduce this. It works well. Is your eigenvalue in this case looks right?

@hebrewsnabla This error seems to be always showing on my own PC. But after some check, on another linux server, in most cases there's no error (but still occasionally error occurs) ... 😵 I'm not sure why this happens on my PC. Maybe math libraries.

Anyway, that's another problem, has nothing to do with the change of this PR.

"The reason of ovlp can't be made to agree in 6 digits, is that this test almostly must run when nroots = 1 as well as tol = 1e-4 for davidson solver. "

I don't know enough to see why that's the case. Hopefully others will be able to give more helpful comments on your pull request!

Will be resolved in https://github.com/pyscf/pyscf/pull/1416. I suggest to close this pull request.


Update toc.yml

Removing references to "REST"

#sign-off @dsk-2015

@dsk-2015 - Would you review the proposed changes? Thanks


avoid failing the report if one chart fails

Added try-except on 2 charts that failed with too many configurations.

This is a quick workaround for the bug: https://agilestudio.pega.com/prweb/AgileStudio/app/agilestudio/bugs/BUG-893503. Just added a try except to skip the failing plots (Predictor Importance & Predictor Count). We can implement a solution to make the charts actually work but it needs a bit of thinking because I think if we allow the report to include 50 charts for each analysis it won't render. Currently it hardly renders even though we skip these 2 charts. Should we just merge this and release a patch to not block Abhijith @StijnKas ?

Makes sense to merge. I rather have the HC doc fail gracefully - but preferably with some (red) errors highlighting the issue.
BTW have you considered using Quarto's (or pandoc) column capabilities instead of plotly facets? I'm using them somewhere in one of the reports already.


PAB activate contract API for parameterised contract

Area
[] Plutus Application Framework Related to the Plutus application backend (PAB), emulator, Plutus libraries
Describe the feature you'd like
At the moment we have an api to create contract instance like in examples
POST /api/contract/activate
Starts a new instance of the contract. Expects a ContractActivationArgs object. Example:
[source,json]
{ "caID": "Currency"
, "caWallet": { "getWallet": 1 }
}

Issue that this approach does not work when we have parametrized contracts, could we add some caArgs parameter where we could pass JSON encoded parameters used for instance creation
e.g. if our Contract schema is  myContract:: Integer -> String -> Contract w s e ()
json example
{ "caID": "Contract"
, "caWallet": { "getWallet": 1 }
, "caArgs" : [1, "MyStringParameter"]
}

This does not match the current wallet API, does it?

This does not match the current wallet API, does it?

At the moment there is no api to instantiate parameterised contract


safePreventDefault Prevents Scrolling With Preact

safePreventDefault Prevents Scrolling With Preact
event is undefined so it runs event.preventDefault();

https://github.com/MANTENN/preact-slick


Model not reloading, no matter what I try

From the same picture I am getting result "100% A" in TeachableMachine, but in node red I am getting 100% B.  (which I was getting before training it more).
It seems to completely ignore any changes I've done to the training.
Is there a file of the model downloaded somewhere that I could delete so that it re-downloads the model?
Disabling does not fix it, deleting the node and reinserting another does not fix it, giving it an invalid URL and then the correct one does not fix it.
EDIT:  The problem is definitely there because I changed the name of class A, to something else, and it's still using the old name.

For how you describe it, it seems the label does not get updated if you try to reload it...
Exactly, if you send a message with a msg.reload field it supposedly to re-download and reload all the files. There should be an example template.

Could you check that using a different model with different labels those also change if you change the URL of a different model?
Also check the URL is the right one.

I've tested this on my side and I don't have any issues, reloading the model with different labels works as expected. Model in teachable machine behaves equally as using the node-red node. I would need more information to reproduce your bug, or find out what is being bad configured.
Thanks!

Yes it seems to reload successfully, just that new labels are a bit delayed in updating.  I just updated the model and some labels, and reloaded, let me check if the new label appears with a test right now.
[After the test]  The new label is updated, everything works perfectly fine.  I don't know why it was delayed yesterday, maybe because of the ways I messed with it before discovering msg.reload.
By the way, my set-up for reloading, for maybe future readers, is like this:

Simple like that.  :)
Thank you for responding @bonastreyair

Thanks! I will add this information in the README to explain the how to us it.
Closing the issue then!


New command: restore role inheritance on list/lib

Usage
spo list roleinheritance reset
Description
restore role inheritance on list or library
Options

Option
Description

-u, --webUrl <webUrl>
URL of the site where the list to retrieve is located

-i, --listId [listId]
ID of the list to retrieve information for. Specify either id or title but not both

-t, --listTitle [listTitle]
Title of the list to retrieve information for. Specify either id or title but not both

Additional Info
for this command we may use
_api/web/lists/getbytitle('${ListTileHere}')/resetroleinheritance

hi since I added issue for the break role inheritance we also need a command to restore it back which I totally forgot😅.
Let me know if there is something which should be clarified here or we (maybe I 😉) could start coding this 😊?

Very nice spec. Since the last noun in the command is roleinheritance, let's update the id and title options so listId and listTitle. Otherwise we'd make it seem like they refer to roleinheritance ID and title, which isn't the case.

done ✅. @waldekmastykarz, as always thanks for the comment 👍.
Do you think it is ready to start coding ?

Yes, it is! Would you like to take it on yourself?

No not really... Only joking ... Yes 😉

Sold! 🚀


Relax Sized trait bound on TypeName impl for &T

Is there any reason not to relax the Sized trait bound on T in the implementation of TypeName for &T.
Currently the following code would be rejected:
    #[derive(TypeName)]
    struct UnsizedStruct {
        a: u32,
        b: [u32],
    }
    let _ = <&UnsizedStruct>::build_type_name(|_| {});

with:
error[E0599]: the function or associated item `build_type_name` exists for reference `&UnsizedStruct`, but its trait bounds were not satisfied
   --> rkyv_typename\tests\test_derive.rs:263:31
    |
259 |     struct UnsizedStruct {
    |     -------------------- doesn't satisfy `UnsizedStruct: Sized`
...
263 |     let _ = <&UnsizedStruct>::build_type_name(|_| {});
    |                               ^^^^^^^^^^^^^^^ function or associated item cannot be called on `&UnsizedStruct` due to unsatisfied trait bounds
    |

but this code would compile fine with the relaxed trait bound.

This is just an oversight. Fixed by #387


SuperToast is crashing

Previously it wasn't crashing but a few days back i found out that whenever or whereever we call supertoast it crashes the application with this message
android.view.WindowManager$BadTokenException: Unable to add window -- token null is not valid; is your activity
what i have already tried.

debug passing correct context .. still no luck
tried putting the show toast method into a new runnable method... no luck

See #108 - supertoasts isn't compatible with android O (yet?).


Build a part when its BOM has trackable part(s)

Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

Describe the bug*
It needs more investigating, but it seems something is wrong handling a build order of a part which has trackable items in its BOM.
Steps to Reproduce

Make a new part, make a BOM, get a trackable (serialized) part and an untracked part
Make a new build order for that part
In the build order where you allocate the parts the trackable item from the BOM are missing completely. So you cannot allocate it.
In order to go forward with the build, I set the trackable part to untrackable. After this it shows up in the list.
complete the allocation, complete the build
the allocated trackable part still remains on the stock, while the untracked one do not.

Expected behavior
Handle trackable BOM parts correctly
Deployment Method

[ ] Docker
[X] Bare metal

Version Information
reproduced on demo server
Version Information:
InvenTree-Version: 0.9.0 dev
Django Version: 3.2.16
Commit Hash: 0bb2dd5
Commit Date: 2022-11-10
Database: postgresql
Debug-Mode: False
Deployed using Docker: True
Active plugins: False
Relevant log output
No response

@rkalman it sounds like the system is working as intended. "tracked" BOM items need to be allocated against a particular build output, not against the build itself.
https://docs.inventree.org/en/latest/build/allocate/#untracked-vs-tracked-stock
Please close the issue if you feel it has been adequately addressed

Oh, I am sorry, I completely missed that part of the documentation.
And yes it is working correctly in these situations:

if we have a stock item of a tracked part with serials assigned:

this is the case I missed completely, we can allocated individual stock items to the build output, nice and ok, thank you
allocated item installed in the completed build output

if we have a stock item of an untracked part without serials:

allocate stock to build as normally do
stock consumed if the build finished

if we have a stock item of a tracked part, which has no serials assigned

we can allocate it to the individual build output without serial, I guess it is ok, we can complete the build without the tracked BOM item serial if it is not provided
Just a small note here, even if the part is tracked it is not required to supply the serials, so basically we can have a stock item of tracked parts without serials, so basically they are untracked... For example if somebody receives the arrived stock items against a PO and forget to fill in the serials. But it is acceptable and I think anybody can live with this behaviour.

And the problem which I met:

if we have a stock item of an untracked part which has serials assigned

yes I know it is crazy, but if you remove the tracking requirement from the part, the serials remains there on the stock items (for ex. somebody has changed the part from tracked to untracked but there are serialised and unserialised stock items present)
we can allocate these stock items to the build as we do with normal untracked BOM items
and finally when you complete the build these items are not removed from the stock. They are not consumed by the build, each of them remains available.

So I think one solution would be to remove all the serials from the stock items when the part goes from tracked to untracked, or investigate why these items remains on the stock after the build completes.
Thank you for your time!


Register semjj.is-cool.dev

Added semjj.is-cool.dev using the CLI.

CLA Assistant Lite bot: Thank you for your submission, we really appreciate it. Like many open-source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution. You can sign the CLA by just posting a Pull Request Comment same as the below format.

I have read the CLA Document and I hereby sign the CLA

You can retrigger this bot by commenting recheck in this Pull Request

please write cla


Action-a

Created Dockerfile

I learnt how to a basic workflow works including the creation of a Dcokerfile, an entrypoint to the Dockerfile, added some metadata in an action.yml file, added a workflow and ran an action from the workflow where the trigger was creating a commit

merged pull requests


Object flow is same as object velocity in Nuscenes?

Hi,
Thanks for releasing the data. The supplementary material says that "we annotate the flow velocity of voxel based
on the 3D box velocity". Does this step simply take the object velocity in the Nuscenes ground truth, and rename it as the flow for each voxel in the object? Or is there any difference?

@bbzh I know it has been a long time since you posted this issue, but I have a question about the flow annotations. I am trying to train a network that predicts the dynamic voxels in a scene, so I need to link annotated flow to annotated voxels. Do you remember if it's possible to link the flow with each voxel? I wasn't able to figure out the relation between the two looking at the arrays and didn't find any information on this. Thank you!


EPIC: QAMP SPRING 2022

Operationalizing Quantum Kernels
Stories
Data

[x] #6

Studies / Experiments

[x] #3
[x] #4
[x] #2

Code

[x] #63
[x] #12
[x] #7
[x] #8

Operational

[x] #59
[x] #1

QAMP issue https://github.com/qiskit-advocate/qamp-spring-22/issues/7

@cfilleke @Travis-S-IBM YOUHHHOUUUUUU 🥳
We finished it !


removed noble-mac version spec

removed version since git checkout was hanging on the 0.0.4

I've been using @abandonware/noble in other projects. I need to spend some time updating this package and republishing.

Thanks Paul. Great library and nice work! Btw, that PR was an accident in
case it wasn't obvious, ha. Cheers!
On Wed, Mar 18, 2020 at 1:27 PM Paul Bates<EMAIL_ADDRESS>wrote:

I've been using @abandonware/noble in other projects. I need to spend
some time updating this package and republishing.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/pryomoax/ortho-remote-node/pull/4#issuecomment-600842120,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABPMDGFFOCKNUEDTC5X7RZDRIEVBXANCNFSM4LOY3TVA
.

I figured :)
Thanks! The only thing annoying is not being able to reset or change the
modulation wheel CC. I found a dev at Teenage Engineering but couldn’t
offer the right command to reset.
I have a similar package for Nuimo.
On Wed, Mar 18, 2020 at 14:05 matthew sibigtroth<EMAIL_ADDRESS>wrote:

Thanks Paul. Great library and nice work! Btw, that PR was an accident in
case it wasn't obvious, ha. Cheers!
On Wed, Mar 18, 2020 at 1:27 PM Paul Bates<EMAIL_ADDRESS>wrote:

I've been using @abandonware/noble in other projects. I need to spend
some time updating this package and republishing.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<
https://github.com/pryomoax/ortho-remote-node/pull/4#issuecomment-600842120
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/ABPMDGFFOCKNUEDTC5X7RZDRIEVBXANCNFSM4LOY3TVA
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/pryomoax/ortho-remote-node/pull/4#issuecomment-600857681,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABCAEHVAGGWS4VAGZAR4DLRIEZQLANCNFSM4LOY3TVA
.

I just pushed v0.2.0 with all dependencies upgraded
On Wed, Mar 18, 2020 at 2:10 PM Paul Bates<EMAIL_ADDRESS>wrote:

I figured :)
Thanks! The only thing annoying is not being able to reset or change the
modulation wheel CC. I found a dev at Teenage Engineering but couldn’t
offer the right command to reset.
I have a similar package for Nuimo.
On Wed, Mar 18, 2020 at 14:05 matthew sibigtroth<EMAIL_ADDRESS>wrote:

Thanks Paul. Great library and nice work! Btw, that PR was an accident in
case it wasn't obvious, ha. Cheers!
On Wed, Mar 18, 2020 at 1:27 PM Paul Bates<EMAIL_ADDRESS>wrote:

I've been using @abandonware/noble in other projects. I need to spend
some time updating this package and republishing.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<
https://github.com/pryomoax/ortho-remote-node/pull/4#issuecomment-600842120
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/ABPMDGFFOCKNUEDTC5X7RZDRIEVBXANCNFSM4LOY3TVA
.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/pryomoax/ortho-remote-node/pull/4#issuecomment-600857681,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AABCAEHVAGGWS4VAGZAR4DLRIEZQLANCNFSM4LOY3TVA
.

Oh! Amazing turnaround. Thank you! 👍
On Wed, Mar 18, 2020 at 4:55 PM Paul Bates<EMAIL_ADDRESS>wrote:

I just pushed v0.2.0 with all dependencies upgraded
On Wed, Mar 18, 2020 at 2:10 PM Paul Bates<EMAIL_ADDRESS>wrote:

I figured :)
Thanks! The only thing annoying is not being able to reset or change the
modulation wheel CC. I found a dev at Teenage Engineering but couldn’t
offer the right command to reset.
I have a similar package for Nuimo.
On Wed, Mar 18, 2020 at 14:05 matthew sibigtroth <
<EMAIL_ADDRESS>wrote:

Thanks Paul. Great library and nice work! Btw, that PR was an accident
in
case it wasn't obvious, ha. Cheers!
On Wed, Mar 18, 2020 at 1:27 PM Paul Bates<EMAIL_ADDRESS>wrote:

I've been using @abandonware/noble in other projects. I need to spend
some time updating this package and republishing.
—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
<

https://github.com/pryomoax/ortho-remote-node/pull/4#issuecomment-600842120

,
or unsubscribe
<

https://github.com/notifications/unsubscribe-auth/ABPMDGFFOCKNUEDTC5X7RZDRIEVBXANCNFSM4LOY3TVA

.

—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<
https://github.com/pryomoax/ortho-remote-node/pull/4#issuecomment-600857681
,
or unsubscribe
<
https://github.com/notifications/unsubscribe-auth/AABCAEHVAGGWS4VAGZAR4DLRIEZQLANCNFSM4LOY3TVA

.

—
You are receiving this because you modified the open/close state.
Reply to this email directly, view it on GitHub
https://github.com/pryomoax/ortho-remote-node/pull/4#issuecomment-600914575,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABPMDGCMJT4CGN5J62XMGNTRIFNNZANCNFSM4LOY3TVA
.


feat: add merchant_name field in the response body

Type of Change

[ ] Bugfix
[ ] New feature
[x] Enhancement
[ ] Refactoring
[ ] Dependency updates
[ ] Documentation
[ ] CI/CD

Description
Made some changes in the core/payment_methods/cards.rs and added a field of merchant_name to the response body of the List of Payment Methods
Additional Changes

[ ] This PR modifies the API contract
[ ] This PR modifies the database schema
[ ] This PR modifies application configuration/environment variables

Motivation and Context
How did you test it?
I tested it manually.
Checklist

[x] I formatted the code cargo +nightly fmt --all
[x] I addressed lints thrown by cargo clippy
[ ] I reviewed submitted code
[ ] I added unit tests for my changes where possible
[ ] I added a CHANGELOG entry if applicable

Add a screenshot in the PR description as to what visible changes are in this PR

Going ahead and merging this, only the OpenAPI spec had to be updated in the recent conflict resolution.


change black background-color on child div of the root container

The problem - the first child of the root wrapper container i.e. the div that is the actual parent of the iframe has a background-color: black on it and I don't see any way to edit this inline style.
I have tried - adding inline styles to the parent container (which didn't affect the child background-color obviously) and hacking the height of the parent container (i.e. the root of React_Player) so that the black background is covered up...but on resize you can see the black background and at certain sizes it has an ever-so-slight black border.
Any advice on how to alter this background-color? Seems like such a simple thing, but I didn't see anything in the documentation about being able to access the styles on this child div that houses the iframe.
See screen shot for a more specific target of the div in question.

That div is rendered by the vimeo SDK, which we have no direct control over.
However, wouldn't this CSS do the job?
.video-player > div {
  background-color: transparent !important;
}

yes that worked! the !important is key. thank you!

perfect it to work for me :-)


Revise clang-tidy rules and make them more strict

close #4

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 0.00%. Comparing base (d4de2c9) to head (2384125).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@          Coverage Diff          @@
##            main      #9   +/-   ##
=====================================
  Coverage   0.00%   0.00%
=====================================
  Files          1       1
  Lines          1       1
=====================================
  Misses         1       1

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


FLAKE: //test/core/end2end:h2_census_test@filter_call_init_fails[darwin-opt]

https://source.cloud.google.com/results/invocations/994ae5f0-71ef-4cf2-9d53-e17e68ca8fd7/targets/%2F%2Ftest%2Fcore%2Fend2end:h2_census_test@filter_call_init_fails/log
exec ${PAGER:-/usr/bin/less} "$0" || exit 1
Executing tests from //test/core/end2end:h2_census_test@filter_call_init_fails
-----------------------------------------------------------------------------
D0203 16:33:02.516043000<PHONE_NUMBER>78144 test_config.cc:385]           test slowdown factor: sanitizer=1, fixture=1, poller=1, total=1
D0203 16:33:02.517339000<PHONE_NUMBER>78144 ev_posix.cc:174]              Using polling engine: poll
D0203 16:33:02.517484000<PHONE_NUMBER>78144 dns_resolver_ares.cc:503]     Using ares dns resolver
I0203 16:33:02.517611000<PHONE_NUMBER>78144 filter_call_init_fails.cc:503] Testing SERVER_CHANNEL filter.
I0203 16:33:02.517636000<PHONE_NUMBER>78144 filter_call_init_fails.cc:47] Running test: filter_call_init_fails/chttp2/fullstack+census
I0203 16:33:02.521035000<PHONE_NUMBER>78144 subchannel.cc:1055]           New connected subchannel at 0x7fc2a8705420 for subchannel 0x7fc2a8702ee0
I0203 16:33:02.540660000<PHONE_NUMBER>78144 chttp2_transport.cc:1088]     ipv6:[::1]:10610: Got goaway [11] err={"created":"@1580747582.540641000","description":"GOAWAY received","file":"src/core/ext/transport/chttp2/transport/chttp2_transport.cc","file_line":1077,"grpc_status":14,"http2_error":11,"raw_bytes":"Buffers full"}
E0203 16:33:02.540765000<PHONE_NUMBER>78144 filter_call_init_fails.cc:171] assertion failed: status == GRPC_STATUS_PERMISSION_DENIED

*******************************
Caught signal SIGABRT
  no backtrace
/Volumes/BuildData/tmpfs/tmp/bazel/a002d9727939acebf422134be2d181ab/sandbox/darwin-sandbox/7187/execroot/com_github_grpc_grpc/bazel-out/darwin-opt/bin/test/core/end2end/h2_census_test@filter_call_init_fails.runfiles/com_github_grpc_grpc/test/core/end2end/h2_census_test@filter_call_init_fails: line 22: 31049 Abort trap: 6           "$1" "$2"

Also seen with h2_ssl_cred_reload_nosec_test:
https://source.cloud.google.com/results/invocations/9aa5506a-25eb-4a69-af12-f113a87d84c8/targets/%2F%2Ftest%2Fcore%2Fend2end:h2_ssl_cred_reload_nosec_test@filter_call_init_fails/log


Mocha has wrong text color on "reply" and "view x replies" button.

What happened?
Catppuccin Theme - Mocha has wrong text color on "reply" and "view x replies" button.
The button text should be light instead of dark color.
Screenshots

fixed in 1.3.2


Standalone store

This PR introduces a store that stands a bit more alone: give it a solution and it prepares it for use by the solution-* components. Once a solution is loaded, a component can use it without dependencies on other components.
To keep the PR size manageable, the store is not yet used by any components.

solution-store.ts
disabled broken unit tests
added coverage scan
some additional typing


Suggestions about Homepage

:heart: the new look :+1:
I do have 2 thoughts about the communication of the product, on the homepage.
GOAL: Have an utter noob (cough like me cough) spend 5 seconds looking at the page and going "Ahhhh!!! I get it!".
CURRENTLY: Too much text. IMO, doesn't explain the product in <= 5 seconds.
Title / Catch phrase / Sales pitch / whatever the first line a person reads.
PROBLEM 1: It's not specific enough
SUGGESTION 1: change it / make it specific

Whatever the text says (enable? enabling? .. ?? ) it tells the USER what it means to them in plain, simple, english.
I still don't see any quick visual 'gotcha'
PROBLEM 2: too much text after that..
SOLUTION 2:
a) Shrink the image with the fire and sharp (and that blurb) (to make more realestate above the fold
b) Then add an animated gif under with each browser and it showing some simple .NET dev with autocomplete, etc (and have a little watermark in the corner with the name of the Editor => vim, atom, whatever.. (now that we have more space to use..)
CONCLUSION

Make me read one line only.
Make me see this stuff in action .. in 10-20 seconds and go 'AHH! GOTCHA'.

UPDATE / EDIT:
What can we do, now?

Discuss this idea, in this thread.
Post animated gif's for the Editor you use or are developing on.
Come up with a consensus ... then I (or anyone) can create a PR.

now, have a sloth.

:+1:, had the same thoughts when looking at the new page. Like I said on jabbr, I feel like the "We say yes!" section doesn't really convey what Omnisharp is about (the middle section about OWIN/Azure seems particularly unrelated).
Love the suggestion about a gif with Omnisharp in action.

Absolutely! This is step one from which we can grow further :smile:
I hear you on the above fold needs less logo and more video/animated gif but we need to have that content which we do not at moment.
As far as I'm concerned the whole screen estate now taken up by the logo should be seen as placeholder for a carrousel of video's or animated gifs showcasing the different integrations. Our logo is not that important :smile:
I personally like the "Cross Platform .NET development!" better then "Enabling .NET development in the editor of your choice". The former is spoken from a position of strength where the latter feels more meh. If we have more visual content both the logo and catchphrase will be a crapload smaller.
I quite like the "We say yes!" and the "Here's how you can too" flow as well to be honest though.
Also not a fan of changing the icons to animated gifs, to much visual noise. (although we could incorporate them into hover states).
The current behaviour of having modals containing the setup information is also less then ideal I would like to work towards a setup as envisioned here: https://github.com/OmniSharp/OmniSharp.github.io/issues/5#issuecomment-74845391
But current state is as far as I got yesterday.PR's welcome! :+1:

logo should be seen as placeholder for a carrousel of video's or animated gifs

:+1:

I personally like the "Cross Platform .NET development!"

I agree that it's nice .. maybe I need to see what it looks like with the animated . I just though that it didn't link to an editor/editors obviously enough.


Fix missing and duplicate alt-text warnings

Ripple 3 validation cleanup for missing and duplicate alt text descriptions.

Docs Build status updates of commit b04795d:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

biztalk/core/basic-orchestration-design5.md
:bulb:Suggestion
View
Details

biztalk/core/creating-affiliate-applications3.md
:bulb:Suggestion
View
Details

biztalk/adapters-and-accelerators/accelerator-swift/end-to-end-tutorial2.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/step-2-create-an-application-definition-file-for-the-sap-artifacts.md
:white_check_mark:Succeeded
View

biztalk/core/adding-biztalk-adapter-for-jd-edwards-oneworld.md
:white_check_mark:Succeeded
View

biztalk/core/how-to-add-index-functoids-to-a-map.md
:white_check_mark:Succeeded
View

biztalk/core/how-to-add-the-bam-interceptor-behavior-to-the-machine-config-file.md
:white_check_mark:Succeeded
View

biztalk/core/transmitter-interfaces.md
:white_check_mark:Succeeded
View

technical-reference/ibasemessagepart-methods-com.md
:white_check_mark:Succeeded
View

technical-reference/ibttransportproxy-methods-com.md
:white_check_mark:Succeeded
View

technical-reference/inameditem-properties-com.md
:white_check_mark:Succeeded
View

biztalk/core/basic-orchestration-design5.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: Basic Orchestration Design' is duplicated in 'core/basic-orchestration-design2.md(2,14)', 'core/basic-orchestration-design3.md(2,14)', 'core/basic-orchestration-design4.md(2,14)', 'core/basic-orchestration-design5.md(2,14)'.

biztalk/core/creating-affiliate-applications3.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: Creating Affiliate Applications' is duplicated in 'core/creating-affiliate-applications1.md(2,14)', 'core/creating-affiliate-applications3.md(2,14)', 'core/creating-affiliate-applications4.md(2,14)'.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit 9cb3152:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

biztalk/core/creating-affiliate-applications3.md
:bulb:Suggestion
View
Details

biztalk/adapters-and-accelerators/accelerator-swift/end-to-end-tutorial2.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/step-2-create-an-application-definition-file-for-the-sap-artifacts.md
:white_check_mark:Succeeded
View

biztalk/core/adding-biztalk-adapter-for-jd-edwards-oneworld.md
:white_check_mark:Succeeded
View

biztalk/core/basic-orchestration-design2.md
:white_check_mark:Succeeded
View

biztalk/core/basic-orchestration-design5.md
:white_check_mark:Succeeded
View

biztalk/core/how-to-add-index-functoids-to-a-map.md
:white_check_mark:Succeeded
View

biztalk/core/how-to-add-the-bam-interceptor-behavior-to-the-machine-config-file.md
:white_check_mark:Succeeded
View

biztalk/core/transmitter-interfaces.md
:white_check_mark:Succeeded
View

technical-reference/ibasemessagepart-methods-com.md
:white_check_mark:Succeeded
View

technical-reference/ibttransportproxy-methods-com.md
:white_check_mark:Succeeded
View

technical-reference/inameditem-properties-com.md
:white_check_mark:Succeeded
View

biztalk/core/creating-affiliate-applications3.md

Line 2, Column 14: [Suggestion-duplicate-descriptions] Attribute 'description' with value 'Learn more about: Creating Affiliate Applications' is duplicated in 'core/creating-affiliate-applications1.md(2,14)', 'core/creating-affiliate-applications3.md(2,14)', 'core/creating-affiliate-applications4.md(2,14)'.

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

Docs Build status updates of commit b5de227:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

biztalk/adapters-and-accelerators/accelerator-swift/end-to-end-tutorial2.md
:white_check_mark:Succeeded
View

biztalk/adapters-and-accelerators/adapter-sap/step-2-create-an-application-definition-file-for-the-sap-artifacts.md
:white_check_mark:Succeeded
View

biztalk/core/adding-biztalk-adapter-for-jd-edwards-oneworld.md
:white_check_mark:Succeeded
View

biztalk/core/basic-orchestration-design2.md
:white_check_mark:Succeeded
View

biztalk/core/basic-orchestration-design5.md
:white_check_mark:Succeeded
View

biztalk/core/creating-affiliate-applications3.md
:white_check_mark:Succeeded
View

biztalk/core/how-to-add-index-functoids-to-a-map.md
:white_check_mark:Succeeded
View

biztalk/core/how-to-add-the-bam-interceptor-behavior-to-the-machine-config-file.md
:white_check_mark:Succeeded
View

biztalk/core/transmitter-interfaces.md
:white_check_mark:Succeeded
View

technical-reference/ibasemessagepart-methods-com.md
:white_check_mark:Succeeded
View

technical-reference/ibttransportproxy-methods-com.md
:white_check_mark:Succeeded
View

technical-reference/inameditem-properties-com.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel

@MandiOhlinger These validation fixes are ready for your review. Thanks!


ci: scan licenses

What feature or improvement would you like to see?
Like apache/arrow#40896
Scan Java, Go, Python

The upstream PR wasn't accepted so I don't see a point here either


static link on windows

this helps avoid library load errors if client machine is missing msvc
redistributables at the cost of ~150KB extra binary size in Release
mode. Seems worth it!

Referenced in https://github.com/tryphotino/photino.NET/issues/60

Any idea when this will be included in a released version?

@mdemler We have been updating all of our samples and are nearly done. We still have a few JavaScript library updates to do and test. Then we'll publish new versions of everything, followed by the new samples, all pointing to the latest versions, followed by new project and item templates for both VS and VS Code. We're getting close!


raftstore: Add a timeout mechanism on snapshot send

Bug Report

What version of TiKV are you using?

7.6 or older
What operating system and CPU are you using?

Steps to reproduce

In an environment where network is very slow,  it's possible that a region's leader cannot transfer leader to other peer.
"[2024/01/18 08:39:09.814 +00:00] [INFO] [peer.rs:3274] ["reject to transfer leader"] [last_index=118] [index=118] [reason="pending snapshot"] [to="id:<PHONE_NUMBER> store_id: 3163 role: IncomingVoter"] [peer_id=1013386609] [region_id=1012011487]",
And this is because the send_snapshot may be stuck and it does not return success or failure, as the log below shows, it did not show either snapshot sent success or failure.
    "[2024/01/18 08:21:11.882 +00:00] [INFO] [snap.rs:1050] [\"scan snapshot\"] [takes=1.354081432s] [size=6574425] [key_count=83914] [snapshot=/var/lib/tikv/snap/gen_1012011487_12_116_(default|lock|write).sst] [region_id=1012011487]",

[2024/01/18 08:21:10.528 +00:00] [INFO] [peer_storage.rs:520] [\"requesting snapshot\"] [request_peer=1013195901] [request_index=0] [peer_id=1013386609] [region_id=1012011487]

What did you expect?
Send snapshot should have timeout mechanism.
What did happened?
Send snapshot may be stuck there forever and the leader cannot get rid of the "pending snapshot" status.

What happens if follower response is lost. Is the leader going to remain in ProgressState::snapshot() forever ? https://github.com/tikv/raft-rs/blob/65a00620d80a89603c3358fd4b90265a692ae767/src/raft.rs#L1783

And also i don't see a retry if snapshot send is failed. https://github.com/tikv/tikv/blob/43d0e061159100092d89147480a94b51b6a158b4/src/server/raft_client.rs#L448C8-L448C26

@mittalrishabh

What happens if snapshot response from follower is lost. Is the leader going to remain in ProgressState::snapshot forever ?

The peer state is changed the snapshot is sent(either finished or failed), it will call the callback and call report_snapshot_status with send a SignificantMsg::SnapshotStatus to the raftstore, on this message, the region leader will change target peer's state to Replicate.

And also i don't see a retry if snapshot send is failed.

Yes, there is no retry here, so if send failed the peer status will change back to replicate. And the snapshot procedure will be trigger after an AppendResponse(triggered by new raft log) or a HeartbeatResponse(if no new message aft 1 tick).

I am new to this code. I still don't understand it. SignificantMsg::SnapshotStatus sends a status message to the peer. I couldn't find the code other than https://github.com/tikv/raft-rs/blob/65a00620d80a89603c3358fd4b90265a692ae767/src/raft.rs#L1783 where peer status in leader is changed to Replicate if snapshot request fails.

I found the code where it is changing it to probe here. https://github.com/tikv/raft-rs/blob/65a00620d80a89603c3358fd4b90265a692ae767/src/raft.rs#L1943. But lets say snapshot request is succeffuly sent but the response is dropped from the peer than would it remain in pause state forever.

it is doing pause here https://github.com/tikv/raft-rs/blob/65a00620d80a89603c3358fd4b90265a692ae767/src/raft.rs#L1979.
Can you point me to the code who is unpausing after the above code in case of response failure or snapshot failure. I am looking at these places because one of the node was stuck in "snapshot pending" state after logging a snapshot failure message.
2024/01/18 08:54:07.429 +00:00] [ERROR] [snap.rs:462] ["failed to send snap"] [err=Grpc(RemoteStopped)] [region_id=1012095669] [to_addr=mussel-prod-replace-tikv-22.mussel-prod-replace-tikv-peer.tidb-mussel-prod-replace.svc.us-east-1a.mussel-prod-replace.tidb.musta.ch:20160]

Can you point me to the code who is unpausing after the above code in case of response failure or snapshot failure. I am looking at these places because one of the node was stuck in "snapshot pending" state for days after logging a snapshot failure message.

you can see there are both resume() call in handle_append_response and handle_heartbeat_response that will resume the pause status.

makes sense. Thanks for the explanation.


Japanese report UnicodeDecodeError

UnicodeDecodeError
report type: GET_BRAND_ANALYTICS_SEARCH_TERMS_REPORT
market: JP
I used the function get_report_document(reportDocumentId=report_document_id, download=True, decrypt=True,
character_code=character_code)
to get report document.The report market is Japan, character_code is "shift_jis", but it raise the UnicodeDecodeError,
'shift_jis' codec can't decode byte 0x83 in position 312: illegal multibyte sequence. I try to use character_code="ISO-8859-1",
but the return data is Garbled code.
Which character_code I should use to get Japanese report?
To Reproduce
character_code = "shift_jis"
get_report_document(reportDocumentId=report_document_id, download=True, decrypt=True,
character_code=character_code)
Desktop (please complete the following information):

OS: Mac

python-amazon-sp-api=0.12.2
api version:  2021-06-30


Move package to handlers

Description
The org.opensearch.sdk package is beginning to become cluttered with boilerplate FooResponseHandler classes.
We should create a subpackage org.opensearch.sdk.handlers and move these classes to it so the important sdk classes are more easily found.
Issues Resolved
https://github.com/opensearch-project/opensearch-sdk/issues/73
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Looks like DCO is failing - did you add the -s flag during the commit?

Not sure if this is necessary for creating a new package, but do you need to add the line package org.opensearch.sdk.handlers to the handler classes in the new folder?

Yes


Database Collation causing case insensitive comparison.

I don't know if we can solve this problem because our bigger concern is having UTF8 support for emojis, and UTF8 does not seem to have any _cs options.
Needs more research...

It seems MySQL has implemented case-sensitive utf8mb4 collations with utf8mb4_0900_as_cs, though it is not available on MariaDB, nor is there any news on their Jira tracker about it.
Only way I can see us implementing this is either going to MySQL, or migrating to PostgreSQL which is case-sensitive out of the box and allegedly supports unicode very well, meaning emojis can be added.


Scroll to top on route change?

Trying to have the browser scroll to the top upon cliking a router . Curren't it is preserving the scroll position.
Could not find anywhere in the documentation.
my render looks something like this
React.render(
  <Router history={createBrowserHistory()} routes={routes} />,
  document.getElementById('root')
);

There's been a lot of discussion in previously filed (and closed) issues on the topic of scroll behavior with 1.0. Check em out! :)
https://github.com/rackt/react-router/issues?utf8=✓&q=is%3Aissue+scroll

I'm on 1.0.0-rc1 and also need conventional browser scroll behaviour (preserve scroll position when using the back button, scroll up when you come to a new page).
Any chance you can give us an ETA for getting this into 1.0.0, or a quick-fix until? None of the closed issues matching 'scroll' give a hint..

+1

Use onUpdate, from #2144
<Router onUpdate={() => window.scrollTo(0, 0)} history={createBrowserHistory()}>
  ...
</Router>

@darreng see my comment on implementing the behavior "preserve scroll position when using the back button, scroll up when you come to a new page" https://github.com/rackt/react-router/issues/2144#issuecomment-150939358

Is the onUpdate={() => window.scrollTo(0, 0)} and https://github.com/rackt/react-router/issues/2144#issuecomment-150939358 the proposed way to handle this in 1.0.0?
I have tried to read through all the issues but have not found anything that makes this clear.

how do I get the current location in the onUpdate() function?

@webular I don't think you can.  I had the same need and switched from using onUpdate to history's listen method (first argument is the location object): https://github.com/rackt/history/blob/master/docs/GettingStarted.md

@jackmoore thx

@webular if you're looking to preserve scroll depth for the back button, you can just use the window.location.

This really deserves a FAQ or a mention in the readme. I have read through a lot of issues and I have no idea what the current stance is on it.

I think there is still no mention on this. The current advice you find first is to use onUpdate={() => window.scrollTo(0, 0)} which scrolls to the top on every transition. I don't think that is what most people want?
Maybe we can agree on a proposed way to do this and push it to the docs afterwards. You can llisten for route changes on history.listen or history.listenBefore. You can then easily "whitelist" the location changes you would like to use for window.scrollTo(0, 0).
let prevLocation = {};
history.listenBefore(location => {
  const pathChanged = prevLocation.pathname !== location.pathname;
  const hashChanged = prevLocation.hash !== location.hash;
  if (pathChanged || hashChanged) window.scrollTo(0, 0);
  prevLocation = location;
});

What do you guys think?

As documented in the upgrade guide, the best recommended solution right now is to use scroll-behavior, per https://github.com/reactjs/react-router/blob/master/upgrade-guides/v1.0.0.md#scrolling and https://github.com/reactjs/react-router/blob/master/upgrade-guides/v2.0.0.md#using-scroll-behavior.
We hope to eventually have a better solution, but this is the best one available at the moment.

In a real-world scenario, I found there is no common pattern that can be extrapolated - sometimes scroll-to-top is desired; sometimes it isn't. This method allows absolute control on a link-by-link basis:
https://github.com/taion/scroll-behavior/issues/15#issuecomment-173746149

As you can see, the browser bug in question is getting fixed, and there is support for controlling when to update the scroll position on a transition-by-transition basis in scroll-behavior now.

@taion Where is the documentation for this transition-by-transition control in scroll-behaviour?

@taion as we can see where? Where is any documentation for per-transition control in scroll-behaviour?

Browser issue noted https://github.com/taion/scroll-behavior/issues/15#issuecomment-198339485. Scroll suppression support was added in https://github.com/taion/scroll-behavior/pull/35, and I'd be happy to receive any contributions to the docs to document this feature.

Documented here now: https://github.com/taion/scroll-behavior#suppressing-scroll-updates

As I understand the new documentation, it is still not possible to control the transition on a case-by-case basis - the same rule will be used for all transitions from /a to /b.

You have access to all the location data you need, including anything you might want to set on location.state to specifically identify the transition, as well as the ability to close over local state in the callback (though you should probably not do that).

@taion thanks for the solution! It works for me :)

@taion is there a way to delay the scroll update until the next page has mounted? We're seeing an issue where the scroll position updates on the current page because the next page takes a second or so to load.

Use your top level route component to scroll on location change in
componentDidUpdate?
Mike
On Fri, Apr 29, 2016 at 5:40 PM, Brandon Dail<EMAIL_ADDRESS>wrote:

@taion https://github.com/taion is there a way to delay the scroll
update until the next page has mounted? We're seeing an issue where the
scroll position updates on the current page because the next page takes a
second or so to load.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/reactjs/react-router/issues/2019#issuecomment-215888868

@mikestopcontinues that would break the behavior we want, which is scroll-behavior's useStandardScroll. We also want to track scroll position for POP events.

@koichik added it to scroll-behavior in https://github.com/taion/scroll-behavior/pull/58 but I haven't had a chance to write a proper router integration yet.

now you can use react-router-scroll

Thanks!

Um, if you want to just always go to the top of the page when changing routes, you can window.scrollTo(0, 0) in your componentWillMount method of your view. Working well for me. Of course if you need fancy stuff then maybe this doesn't cut it.

As noted above, please use react-router-scroll if you need this.
I don't think it's fully ready to be pulled in here, but it's good enough for general use.

...

function handleUpdate() {
  let {
    action
  } = this.state.location;

  if (action === 'PUSH') {
    window.scrollTo(0, 0);
  }
}

...

<Router
  onUpdate={handleUpdate}
/>

...

Worked pretty well for me, so thought I'd share :sun_with_face:

Here is my solution for react-router 2.8.1 version :) In this version we preserve scroll location only if user goes back one route (POP) otherwise scroll to top.
import React from "react";
import { Route } from "react-router";

import App from "components/App";
import Profile from "components/Profile";

const routes = (
  <Route
    component={App}
    path="/"
    onChange={(prevState, nextState) => {
      if (nextState.location.action !== "POP") {
        window.scrollTo(0, 0);
      }
    }}
  >
    <Route path="profile" component={Profile} />
    // ...
    // more routes here
  </Route>
);

export default routes;

how do you solve this in react-router v4?

In addition to @FoxWhite in v4, I tried the follow:
<Match pattern="*" compoent={ScrollToTop} />

const ScrollToTop = () => {
  window.scrollTo(0, 0);
  return null;
}

But the side affect of this is if you have <Miss> it will never be called.
Any suggestions?

it'd be nice to have a callback to pass on Router, like onUpdate()

I've solved it this way (for v4 router):
import React, { Component } from 'react'
import { Match, propTypes as routerPropTypes } from 'react-router'

export class SomeRootComponent extends Component {

    static contextTypes = {
        history: routerPropTypes.historyContext.isRequired,
    }

    componentDidMount() {

        const { context } = this

        this.historyUnlisten = context.history.listen(() => this.scrollToTop())

    }

    componentWillUnmount() {

        this.historyUnlisten()

    }

    scrollToTop() {

        // In fact here I have some more complicated logic for smooth animation,
        // but this one is ok too
        window.scrollTo(0, 0)

    }

    render() {

        return <Match pattern="/" component={SomeComponent} />

    }

}

Another iteration similar to @antipin's v4 solution, but avoiding reading from context directly by using withRouter to look for location changes
export class RouteHandler extends React.Component {

  componentWillReceiveProps(nextProps) {

    const { location, history: { action } } = nextProps;
    if (location !== this.props.location && action === 'PUSH') {
      // new navigation - scroll to top
      window.scrollTo(0, 0);
   }

    // eventually we might want to try setting up some scroll logic for 'POP'
    // events (back button) to re-set the previous scroll position

  }

  render() {
    return this.props.children;
  }
}

export default withRouter(RouteHandler);

The solution that works for me is just add <Route> at the top level component:
<BrowserRouter>
      <Route component={ScrollToTop} />
      <Switch> // rest of the routes definition
       ....
</BrowserRouter>

const ScrollToTop = () => {
  window.scrollTo(0, 0);
  return null;
};

@idanwe Your solution gives me the following error: "A  may have only one child element".
I have one  component in my BrowserRouter, so not sure how you made it work?

@mmcgahan You solution won't work robustly

both the back and forward buttons in a web browser trigger a POP action

Let's say the navigation stack is
-> A -> B
Then we press go back, POP
-> A
navigate somewhere deep in page A
Then we press go forward, still POP action
-> A -> B
We will end up with some deep down in page B also

Here's a naively implemented solution. It works for me so far.
Do note that there are browser discrepancies not handled (like browser fire on scroll event for push state change etc)
// @flow
import React, { Component, Children } from 'react';
import { withRouter } from 'react-router';
import type { Location, RouterHistory } from 'react-router';

type PropTypes = {
  location: Location,
  history: RouterHistory,
  children: any,
};

const PREFIX = '@@scroll/';

class ScrollBehavior extends Component {
  props: PropTypes;
  static locationVisited: {
    [key: string]: number,
  } = {};

  constructor(props: PropTypes) {
    super(props);
    (this: any).onScroll = this.onScroll.bind(this);
  }
  componentDidMount() {
    history.scrollRestoration = 'manual';
    window.addEventListener('scroll', this.onScroll);
  }

  componentWillUnmount() {
    history.scrollRestoration = 'auto';
    window.removeEventListener('scroll', this.onScroll);
  }

  onScroll() {
    requestAnimationFrame(() => {
      console.log('on scroll', this.getLocationKey(this.props.location.key), window.scrollY);
      ScrollBehavior.locationVisited[this.getLocationKey(this.props.location.key)] = window.scrollY;
    });
  }

  getLocationKey(key) {
    return PREFIX + (key || '');
  }

  scrollTo(Y: number) {
    requestAnimationFrame(() => {
      window.scrollTo(0, Y);
    });
  }

  componentWillReceiveProps(nextProps: PropTypes) {
    const { location, history: { action } } = nextProps;
    if (location !== this.props.location) {
      if (action === 'PUSH') {
        // new navigation - scroll to top
        this.scrollTo(0);
      } else {
        const key = this.getLocationKey(location.key);
        console.log('on scroll', ScrollBehavior.locationVisited, scrollY);
        if (ScrollBehavior.locationVisited.hasOwnProperty(key)) {
          const scrollY = ScrollBehavior.locationVisited[key];
          this.scrollTo(scrollY);
        }
      }
    }
  }

  render() {
    return Children.only(this.props.children);
  }
}

export default withRouter(ScrollBehavior);

@Floriferous Add a  to contain the new Route and you existing route.
const App = () => {
  return (
    <BrowserRouter>
       <div>
          <Route component={ScrollToTop} />
           {/*
              rest of the routes definition
              <Switch>, more <Route>, etc ....
           */}
       </div>
    </BrowserRouter>
  );
}

const ScrollToTop = () => {
  window.scrollTo(0, 0);
  return null;
};

I ended up using the <ScrollToTop> workaround described in the react-router docs.
Here is my implementation, and an example usage (Typescript).

thank you @pedi, yours works for me perfectly!

window.scrollTo(0, 0) never worked for me anywhere. I had to put a fixed element on the top of each page and then do document.getElementById('fixed-element').scrollIntoView() inside componentDidMount().

thank you @vivmaha
I just used what was prescribed in the official docs

I'm using this and it works
<Route path="/booking" onEnter={() => setTimeout(function () { window.scrollTo(0, 0);}, 100)} ... />
p.s: setTimeout is used since it has issues on chrome

I'm just wrapping my routes components with this:
`const ScrollTop = ({children}) => {
window && window.scrollTo(0,0)
return children
}`
Would look something like this
<Router>      <ScrollTop>           <Route .... />           <Route .... />      </ScrollTop> </Router>


ContractAddress, ClassHash and EthAddress decoding

Actually this types are handle as common numeric types :
https://github.com/0xSpaceShard/starknet-hardhat-plugin/blob/afc83b3a5892caab6cfbc64701422521f4de43af/src/adapt.ts#L8-L20
It could be converted to hex representation
ie :
3407481119780572850671182801001023516830125398818876583940565901076194792664 would decode to 0x78890e347461d95a8eacddaeb35b577f4ef29a6fbf825326d8d97022e2a14d8

Would make sense for ContractAddress, ClassHash and EthAddress. But this would be a breaking change.


Update Composer dependencies (2024-03-04-00-10)

Visual regression test passed!
View the visual regression test report


Update MediaElement.md fix demo bug:

fix demo bug:  Cannot resolve type "http://schemas.microsoft.com/dotnet/2022/maui/toolkit:MediaElementState".

Hello there, thanks for this PR! I don't think this should be necessary though. Did you see any errors while trying this sample?

only this:

More info :
Mac M1 pro  13.3.1
visurlStudio : 17.5.5 (build 2)
MediaElement: installed 1.0.2
xml header added:   xmlns:toolkit="http://schemas.microsoft.com/dotnet/2022/maui/toolkit"
.net version :7.0;

Seems this is all resolved then. Thank you!


RtcPeerConnection support setConfiguration function

Motivation
I would like to be able to use all available methods of RTCPeerConnection defined here. One of missing methods is setConfiguration, which is often used to change configuration without need to create new Peer Connection.
Proposed Solution
Implement a binding between JS API, and Rust WASM API.
I have created a PR: https://github.com/rustwasm/wasm-bindgen/pull/4105, there are few test cases failing. I am happy to finalize the work, with some assistance how to resolve those failures.

Addressed by #4105.


Added ausiasmarch domain.

I'm unable to confirm that the school is at academic level?
It's English site tells me that it's only a fundamental level school:

@Ruubenf Pull request merged. Thank you!


Highlight column name in insert/select-clause based on order of column

Is your feature request related to a problem? Please describe.
I'm always frustrated when I read code with INSERT query with long list of columns and I have to figure out with eyes the corresponding column in SELECT-query for some column in INSERT-query and vice versa.
Describe the solution you'd like
See how your rival highlights the corresponding columns, fixing my issue.
I suggest to add the similar feature.
Notice that the whole expression in select-clause is highlighted, even if it is a subquery, not a simple expression or column name.
https://github.com/user-attachments/assets/f16f5235-ef86-4b65-b1e1-c998c357ca15

Thank you for the idea.
It looks like a duplicate of #22522, except that you're asking to highlight expressions in select too.

Yes.
I suggest a more general way: highlight the text in both directions based on current position of the caret.


Regression test look for extension crashes caused by entering more than 6 decimal places

Try out this version of the Hiro Wallet - download extension builds.

This is a regression test to look for web wallet crashes that are caused by entering more than 7 decimal places. The test attempts to reproduce the P1 bug we found in issue #1698 as well as additional test that test edge cases related to that functionality.
@UXTEAM
cc/ @aulneau @kyranjamie @fbwoolf @beguene @markmhx @Eshwari007 @andresgalante

I will fix these linting issues reformatted but prettier did not take.

Looks great @timstackblock except for the formatting issues Kyran pointed out.


Update readme.md

Minor fix in Self-Host documentation.
it's index.js not bot.js :)

There was more that needed to be fixed, in #75 😅