Multicoin Explorer?

How difficult will it be to extend this project to support LTC, DOGE and more and have one explorer for many coins similar to bitcoin-abe?

Would need indexes added in relevant coin (as similar to https://github.com/bitpay/bitcoin).


Add mechanism to forward Heartbeat status for LPC/LPP usecases to CEM

Depending on if the Heartbeats are correctly received by a Controlbox for an interval determines different states that the system needs to go into.
Therefor we need to inform the CEM about the current Heartbeat status so the same is able to handle missing heatbeats and inform other entities to go into failsafe state.

This is implemented in eebus-go repository.


odo deploy: auto-started components (e.g. with deployByDefault= true) are applied even if Devfile has no deploy command

/kind bug
What versions of software are you using?

Sample starter project:

odo init --name bug-deploy --devfile go --devfile-version 1.0.2 --starter go-starter

Edit Devfile
Now edit the Devfile by adding a component that needs to be created automatically (e.g;, Kubernetes/OpenShift component with deployByDefault=true, or not referenced by any apply command), e.g.:

--- a/devfile.yaml
+++ b/devfile.yaml
@@ -21,6 +21,19 @@ commands:
     workingDir: ${PROJECT_SOURCE}
   id: run
 components:
+- kubernetes:
+    inlined: |
+      apiVersion: v1
+      kind: Pod
+      metadata:
+        name: my-nginx
+      spec:
+        containers:
+        - name: nginx
+          image: nginx
+          ports:
+            - containerPort: 80
+  name: my-k8s-component
 - container:
     args:
     - tail

Run odo deploy:

odo deploy

Actual behavior
Automatic components are applied, and after that, odo deploy checks if the Devfile has a deploy  command:
  __
 /  \__     Running the application in Deploy mode using bug-deploy Devfile
 \__/  \    Namespace: default
 /  \__/    odo version: v3.9.0
 \__/

↪ Deploying Kubernetes Component: my-nginx
 ✓  Creating resource Pod/my-nginx
 ✗  no default deploy command found in devfile

Expected behavior
We should check if the Devfile has a deploy  command first prior to starting to apply automatic components.
Otherwise, odo deploy  will error out, but with partial resources created into the cluster.
Also, running odo describe component  would show the component as running in Deploy mode, which is not strictly true:
$ odo describe component

Name: bug-deploy
Display Name: Go Runtime
Project Type: Go
Language: Go
Version: 1.0.2
Description: Go (version 1.18.x) is an open source programming language that makes it easy to build simple, reliable, and efficient software.
Tags: Go

Running in: Deploy

Running on:
 •  cluster: Deploy

Supported odo features:
 •  Dev: true
 •  Deploy: false
 •  Debug: false

Container components:
 •  runtime
    Source Mapping: /projects

Kubernetes components:
 •  my-k8s-component

Any logs, error output, etc?

/remove-lifecycle stale
/lifecycle active


Mobile site

Is there a way to disable the mobile site? In my opinion it is not as good looking as the full site and doesn't display featured images.
Also, on mobile there's an issue with rendering when scrolling. Is there a fix for that? It happens no matter what version of the site you use. I'm using chrome on Android.

I think it's not good idea when try to disable the mobile support feature. I mean, it seems like we're looking forward but trying to step backward.
Instead, we'll try to improve this one.

Oh the site looks beautiful when I choose to view the desktop one on my
phone. If it wasn't for the scrolling/rendering issue, it'd be perfect. I'm
not suggesting it's disabled for everyone, just instructions to disable it
myself and maybe set a custom default zoom level for phones.
On 28 Aug 2016 06:01, "n2i"<EMAIL_ADDRESS>wrote:

I think it's not good idea when try to disable the mobile support feature.
I mean, it seems like we're looking forward but trying to step backward.
Instead, we'll try to improve this one.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/TaylanTatli/Moon/issues/55#issuecomment-242956466,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIhzn9QZOvkB1gDjLl4flwmoyFsLXMYrks5qkRYlgaJpZM4Jq1Cy
.

How to get sharing button in mobile ?

In addition to what I said before, rather than just disabling it manually, there could be an option in config.yml to disable it.


Stop allocating the documents we return in RAM

Describe the bug
We allocate a lot of RAM to make search requests or document requests with a very high limit.
milli seems to handle that well, but in meilisearch, we then enter in the function that deserializes and allocates every document in RAM.
For a few thousand documents, that can easily take multiple MiB in RAM. And when people are running requests like that under a high load, it can get us OOM-killed. I think that's what is happening here (private link): https://github.com/meilisearch/meilisearch-support/issues/100

For the search: https://github.com/meilisearch/meilisearch/blob/ff76d8f21aa73c2a07c80501958904d53c6a10f5/meilisearch/src/search.rs#L592-L644
For the documents route: https://github.com/meilisearch/meilisearch/blob/ff76d8f21aa73c2a07c80501958904d53c6a10f5/meilisearch/src/routes/indexes/documents.rs#L554-L602

And as a bonus, it should make the search slightly faster when people are getting a lot of documents.
I’ve added the spike label because since we’re not returning the results in json-lines, I don’t know how it’ll work out with serde_json.
We may need to do something very custom 😬
Expected behavior
We stream the requests to the end user without ever allocating more than one document at a time.
See https://docs.rs/actix-web/latest/actix_web/struct.HttpResponseBuilder.html#method.streaming
Meilisearch version:
all

Update after a first investigation
By limiting the maximum number of searches processed at the same time, we're limiting by a lot the RAM consumption.
Fixing this issue would make the engine faster (and able to process more search requests) but not especially avoid crashes.

We cannot fix this issue without breaking the get documents and search routes by streaming our answer to the client.


[stable/redis] Adds fullnameOverride support

Adds fullnameOverride value support to redis.fullname helper (as generated by the helm create command of Helm-2.8.1)
Upgrades redis chart version: 1.1.17 → 1.1.18

/assign @unguiculus

/ok-to-test

/lgtm


Add test of QuantEcon McCall code to the fixed-point testsuite to compare performance.

Look at https://lectures.quantecon.org/jl/mccall_model_with_separation.html
I think the key code is
using Distributions

# A default utility function

function u(c::Real, σ::Real)
    if c > 0
        return (c^(1 - σ) - 1) / (1 - σ)
    else
        return -10e6
    end
end

# default wage vector with probabilities

const n = 60                                   # n possible outcomes for wage
const default_w_vec = linspace(10, 20, n)      # wages between 10 and 20
const a, b = 600, 400                          # shape parameters
const dist = BetaBinomial(n-1, a, b)
const default_p_vec = pdf.(dist, support(dist))

mutable struct McCallModel{TF <: AbstractFloat,
                           TAV <: AbstractVector{TF},
                           TAV2 <: AbstractVector{TF}}
    α::TF         # Job separation rate
    β::TF         # Discount rate
    γ::TF         # Job offer rate
    c::TF         # Unemployment compensation
    σ::TF         # Utility parameter
    w_vec::TAV    # Possible wage values
    p_vec::TAV2   # Probabilities over w_vec

    McCallModel(α::TF=0.2,
                β::TF=0.98,
                γ::TF=0.7,
                c::TF=6.0,
                σ::TF=2.0,
                w_vec::TAV=default_w_vec,
                p_vec::TAV2=default_p_vec) where {TF, TAV, TAV2} =
        new{TF, TAV, TAV2}(α, β, γ, c, σ, w_vec, p_vec)
end

"""
A function to update the Bellman equations.  Note that V_new is modified in
place (i.e, modified by this function).  The new value of U is returned.

"""
function update_bellman!(mcm::McCallModel,
                         V::AbstractVector,
                         V_new::AbstractVector,
                         U::Real)
    # Simplify notation
    α, β, σ, c, γ = mcm.α, mcm.β, mcm.σ, mcm.c, mcm.γ

    for (w_idx, w) in enumerate(mcm.w_vec)
        # w_idx indexes the vector of possible wages
        V_new[w_idx] = u(w, σ) + β * ((1 - α) * V[w_idx] + α * U)
    end

    U_new = u(c, σ) + β * (1 - γ) * U +
                    β * γ * dot(max.(U, V), mcm.p_vec)

    return U_new
end

function solve_mccall_model(mcm::McCallModel;
                            tol::AbstractFloat=1e-5,
                            max_iter::Integer=2000)

    V = ones(length(mcm.w_vec))    # Initial guess of V
    V_new = similar(V)             # To store updates to V
    U = 1.0                        # Initial guess of U
    i = 0
    error = tol + 1

    while error > tol && i < max_iter
        U_new = update_bellman!(mcm, V, V_new, U)
        error_1 = maximum(abs, V_new - V)
        error_2 = abs(U_new - U)
        error = max(error_1, error_2)
        V[:] = V_new
        U = U_new
        i += 1
    end

    return V, U
end
mcm = McCallModel()
V, U = solve_mccall_model(mcm)

With this

[ ] Get it working (essentially as-is) and add this to the NLsolve  ranch as a new test called mccall.jl or something like that.
[ ] Maybe put it in a separate function so that you can run the @btime on it.  You will want to keep that version in the test as a comparison
[ ] Now, we want to make a separate version of this using the fixedpoint library, and changing as little else as possible.
[ ] I think the key here is first to rewrite the update_bellman! to be an inplace function which can be used with a fixed point iteration.

rename the update_bellman! function to be bellman_operator! or something like that
move the mcmc::McCallModel to the end of the signature
In particular, this means you will want to change the signature to not return U_new but rather to have the whole thing in a single vector with the V_new and U_new stacked and the V and U stacked.  Then it becomes a true fixed point operator on a vector

Get that working fully first, where the solve_mccall_model function is modified to use the changed bellman_operator! function, but leave the rest of fixed point iteration the same.
Check the performance of this with a @btime compared to the original code, to make sure that this didn't add a huge amount of overhead.
[ ] After that, you can modify the iteration in solve_mccall_model to use the bellman_operator! with the fixedpoint function you designed.  This probably involves creating a simple closure in that function prior to calling it.  i.e.

T!(x_new, x) = bellman_operator!(x_new, x, mcm)
#...
solution = fixedpoint(T!, x0, inplace=true, ftol=tol)

[ ] Make sure that you are using the same tolerances, and do a @btime to see if there is a difference.  Try it with m=1 or m=2 as well.

Makes sense. I'll probably step out for lunch and then get to this.

Done. See commit XYZ for benchmarking code and
What we see is that two simple iteration schemes are about as fast as each other (~513 μs naive, and about 580 μs stacked), and all the nlsolve() schemes are about 2X slower (for various memory parameters m).
Code is up at 50077b5 for inspection. It's possible (maybe even probable) there's some type instability somewhere, so I'll look into that.

50077b5

@jlperla OK, I'm going to close this since the code is up at the server since the tests pass and obey the speed rules we think they do.
But it's worth looking at the accuracy here; all the results converge by nlsolve()'s ftol <= 1e-5 rule. But the roots found by different m values are pretty far apart (1e-4, 3e-4, 1e-6 for pairwise consecutive on 0, 1, 2, 7). It's probably still true that these all end up close enough to where the Bellman operator sends them. But this is probably the kind of thing users would need to know.
What's interesting is that roots found by the higher m values (which run faster) are closer together.

Just confirming that all the solutions here are equally accurate, in that their difference from their successor under Bellman iteration is less than required.
norm(old - cat(1, U_new, V_new), Inf) = 9.670017810492482e-6 # QuantEcon implementation
norm(default_fixedpoint_results.zero - newVec, Inf) = 9.867365108107151e-6 # m = 0
norm(fixedpoint_results_1.zero - newVec, Inf) = 7.116237924265079e-6
norm(fixedpoint_results_2.zero - newVec, Inf) = 2.3626285639011257e-7
norm(fixedpoint_results_7.zero - newVec, Inf) = 1.399587077344222e-7


Permit array as root form fields

Currently the fields passed to a formAtom() must be an object.
type FormFields = {
    [key: string | number]: FieldAtom<any> | FormFields | FormFields[] | FieldAtom<any>[];
};

It could be generalized, to accept also array:
type FormArrayFields = FormFields[] | FieldAtom<any>[];
type FormFields = {
    [key: string | number]: FieldAtom<any> | FormFields | FormArrayFields;
} | FormArrayFields;

This could enable the submit value to be passed directly to some endpoints. For example, when configuring contact persons, I can submit the form data directly, as my endpoint expects array payload.
Currently, best we can do is to have the contact persons under some key in the form, which requires us to unwrap the data on submit:
const contactsForm = formAtom({persons: [...]}) // must use arbitrary key just to fulfil the interface

const { submit } = useForm(contactsForm)
// unnecessary unwrapping required
<form onSubmit={submit(({ persons }) => saveContactPersons(persons))}>

This could be:
const contactsForm = formAtom([...]) // array form fields

const { submit } = useForm(contactsForm)

<form onSubmit={submit(saveContactPersons)}>

Have to think about this one. Seems like a minor inconvenience for users and a limited use case.


ignore device monitor logs

updated the gitignore to ignore all logs generated by using the serial device monitor in platformio

closing because feature/storage-with-preferences already has the log files ignored


Bump magic-string

Closes #183
Care was taken to use versions of Node and NPM as discussed in https://github.com/Rich-Harris/buble/pull/184 for generating minimal changes to package-lock.json.
$ node --version
v10.15.1
$ npm --version
5.8.0

Wow, that's effort. Thanks!

Hooray! Thanks for merging.


Selector Dropdown is displayed strangely

The example can be found in the TCA Manual, Filename CtrlType

I can reproduce the issue in Codeception as well as in the bundled package php-webdriver/webdriver. It is either a problem with that package, or with the bundled Selenium standalone server, or with the bundled Chrome Driver + Chrome Browser. I started to report the issue for the php-webdriver level and will drive it through all layers:
https://github.com/php-webdriver/php-webdriver/issues/905


words  joined  at chunk boundaries

When  decoding large files  with continuous _decoding  option  , two words  are  joined  at chunk boundaries. (in the asr output text)  Cannot  observe this  with  small file  and  chunk_size  set to -1.  (English model)

please give some examples.

Sorry  for  the  late follow  up. Since I fixed  it by  a work around, I forgot to take it up again.
Pls see  the below  decoding result
./build/bin/decoder_main
--chunk_size 16
--num_left_chunks -1
--wav_path $1
--onnx_dir $onnx_dir
--continuous_decoding
--num_threads 2
--unit_path $units
--result $2  2>&1 | tee log.txt
we're gathered at this sacred placein this solemn hour engage in most fundamental of undertakings the right of remembranceremember those who gave their all in the service of america and the service of freedomservice of justice remember their sacrifice their valor and their graceremember their smiles their lovesafter therepotential vibrant and transcendent humanityfor while we stand amid monuments of stonenever forget that each of these markers for those known and unknown here at arlington and far beyondthat a precious life a son a daughter a mother a spouse brother a sister of friend a neighborthose who mourna loved one todayyou and i have some idea how you're feelingour losses are not the samebut that black coal you feel in your chest as if it's going to suck you into itwe geti know the incredible pride you felt senior loved one wear the uniform of our countrypride they felt wearing itour son bose service the dela robbery national guard unit the year is spent deployed in iraqone of the things that he was most proud of in lifeyesterday mark the anniversary of his deathand it's a hard timehard time of year for meand our familylike it is for so many of youit can hurt to remember butis how we feel and how we healalways feel both close to me at memorial day i know exactly where i need to behere honoring our fallen heroesgo through pain and anguish of his loss i remember the pride on his face that penned those bars on his shouldersall of you who are fighting with the fresh pain of losshard it is to believe i promise you thisah day will comeimage of your loved one will bring a smile to your lips before it brings a tear to your eyesbible teaches blessed are they that mourn for they shall be comfortedcomfort that reassurance can be a long time in coming but it will come i promise youum prayer for all of you is that they that that day will come sooner rather than laterwe're all known memorials day origins lying the wake of the civil warfor for the freedom of allfor unionfor for libertyah preservation of the constitutionin calling for such today general john logan commander of the grand army of the republic issued general order number elevenhe directed the nation set aside a day to honor and i quote those who died in defense of their country during the late rebellion and whose bodies now lie in almost every city village and hamlet churchyard throughout the landand so we haveso we do again today in our timewhere the childrenum sacrifice made by a long line of american service members each a link in that chain of honorwe live by the light of the flame of libertyah kept bernie we're free because theyhere on these gentle rolling green hills and across america and around the globe lie buried the heroes of the greatest experiment the world has ever known ever seenbears the noble name the united states of americawomen and menthose we honor todaytheir lives for their countrybut they live forever in our hearts forever proud forever honorable forever americanthey are they are the sentinels of liberty defenders of the downtrodg liberators of nationsand still todayis stand watch around the worldtheir great personal perilwar and conflict death and lossnot relics of our american historypart of american storyhere in arlington why heroes who gave a president lincoln called the last full measure of devotionit did not only die at gettysburg or in flanders field or in the beaches of normantyah mountains of afghanistan the deserts of iraqtwenty yearssex and sixty when i walk through it reminds me of the cost of warhundreds of graves hundreds of graves are here from recent conflictshundreds of patriots gave their alleach of the maybe behind the familywhat their pain and their absence every single dayi want to assure each of those families we will never forgetwhat you gave to our countrywe will never fail to honoryour sacrificeeach dayanyone i was vice president united statescarry in my pocket a number of troops killed during the warsafghanistan and iraqan approximation not rounded off numbersthe eastly behind the entire community and familytoday that number is seven thousand and thirty sixthousand and thirty six fallen angelslost their livesconflictsthis memorial dayand their legacy and their sacrificehonor countrythey lived for it they died for itand we as a nation are eternally gratefulso america has been forged in the baz and the fires of warah freedom and the freedom of innumerable others has been secured by young men and women who answered the call of history and gave everything the service of an ideathe idea of americait's the greatest idea in the long history of humankind an ideawe're all created equal in the image of almighty godall entitled to dignity as my father would say and respectdecency and honorneighbor they're not empty wordsbut the vital beating heart of our nationand that democracy must be defended at all costs where democracy makes all this possible democracythat's the soul of americaand i believe it's a soul worth fighting for and so to you a soul worth dying forheroes who lie in eternal peace this beautiful place this sacred place they believe that tooall of america is animatedby the perennial battle betweenah worst instincts which we've seen of late and our better angelsbetween me first andbe the peoplebetween greed and generosity cruelty and kindnessactivity and freedomthe americans of lexington and concord of new orleans gettysburg the argon io g and normandy korean vietnam afghanistan and iraq and thousands of places in betweenthese americans weren't fighting for dictators they were fighting for democracythey weren't fighting to exclude or to enslave they were fighting to build and broaden and liberatethey weren't fighting for self they were fighting for the soul of the nationfor liberty and simple fair playfull fair play and decencydays remember their sacrificeremind ourselves of our duty to their memory to the future they fought forwe owe the honored dead debt we can never fully repay we owe them our whole souls we owe them our full best efforts to perfect the union for which they diedwe owe them the work of our hands and our heartsmake grill the promise of a nation founded on the proposition that all of us all of us all of uscreated equal and deserved to treat it that way throughout our livesdemocracy is more than a form of government its way of being it's a way of seeing the worlddemocracy means the rule of the peoplerule of the peoplenot the rule of monarchsthe role of the moneyed not the rule of the mighty literally the rule of the peoplethe lives of billions from antiquity to our own hourshape by the battle between aspirations of the many and the greed of the few between people right to self determination and the self seeking of the dictator between dreams of democracy and appetites for autocracy which were seen around the worldum who fought this battle on fields around the world but also theof our timeand the mission falls to each of us each and every daysee itselfpair of here at home and around the worldwhat we do nowdo now how we honor the memory of the fallendetermine whether or not democracy will long endurewe all take you for granted we think we learn in school you have that every generation has to fight for itlookit's the biggest question whether a system that prizes the individual that bends towards libertyeverybody a chance of prosperity whether that system can and willah against powerful forces that wish it harmthat we do in our common life as a nation is part of that struggleah go for democracy is taking place around the world democracy and autocracyfor decency and dignitysimple decencystruggle for posterity prosperity and progress and yesstruggle for the soul of americaitselffolksyou all know it democracy thrives when the infrastructure democracy is strongum people have the right to votereally and fairly and conveniently when a free and independent press pursues the truth founded on facts not propaganda on the rule of law applies equally and fairly to every citizen and regardless of where they come from what they look likeexcuse mewherever americans are therethere is democracysynagogues and mosquesand coffee shops and dinersleeiters and kids baseball or soccer gameand parksdemocracy begins to grow in the open heart and the impetus to come together for a common causeand i might know parenthetically thank you taps that's what you doand that's where we'll be preservedfor empathy is the fuel democracy let me say that again empathy empathy is the fuel ofdemocracy are willing to see each othernot as enemy as neighbors even we disagreed to understandbut the other's going throughstate the obviousracies imper it always has been but americans have all backgrounds races creeds gender identities sexual orientations have long spillled their blood to defend our democracy the diversity of our country and our arm and of our armed services is inhas been an incredible strengthand generation after generation of american heroes have signed up to be part of the fight because they understand the truth that lives in every american heartliberationopportunity justice are far more likely to come to pass in a democracy than an autocracyif every person is sacred and every person writes our sacredindividual dignity individual worth individualsanctityright to life liberty the pursuit of happiness we say those words so often but think of itthe right to voteright to rise in a world as far as utalu can take you unlimited by unfair barriers of privilege and powersuch are the principles of democracyso how would you put these noble principles into practice how do we do thatmake the idea real or as close to real as we can make it this nation was built on an idea the only nation in the world built an idea every other nation is built on ethnicity geography religionetc we were built on an idea the idea of libertyan opportunity for allnever fully realized that aspiration of our founding but every generation has opened the door a little widerevery generation is open to wider and wider to be more inclusive include those who've been excluded beforeit's a mission handed down generation to generation the work of perfecting our unionthirtywhen we're a young nationdisunionists put their sexual interest ahead of the common gooda great senator daniel websterand the capital to defend the unionwe're not just a collection of competing forces but a coherent wholehis cry firstah just across the potomac in the capitol resonates even nowstood in the floor and he said liberty and union now and forever one and inseparable liberty and union more than one hundred and forty two years laterfirst came to the united states senate at a time when our country was so deeply divided over vietnam the struggle of civil rights the fight of our women's rights inotion that my first task as i stood to make my first speech on the floor of the senate that all of a sudden hit me i'm standing where daniel weptridge stood his desk was next to minei was struck by the weight of history as cornies it soundslegacy the work were charged to carry forward liberty and unionnow and forevernow is thenunity is essential to life liberty and the pursuit of happinessand so remember those who gave their all the cause of unity and the cause of a nation that endures because of themhonor their sacrificegaining the best of america while honestly confronting all that we must do to make our nation fuller freer and more justrememberwe may find the light in the wisdom and yes the courage to move forward in the words of that great hymnfight as they nobly thought of oldwhen remembrance lies not just our history but our hopenot just our solemn remembrance but our renewed purpose not just our solace but our strengththis memorial daybut not all of us are called to make the ultimate sacrificewe all are calm by god and by history andconscienceto make our nation free and fair just and strong noble and wholethis battlemay we now dedicate our souls that our work may prove worthy of the blood of our fallen for this work the work of democracy is the work of our time and for all timeand if we do our duty then age is still to come we'll look back on us and say that we too kept the faiththere's nothing more importantmore sacred nothing more american than keeping the faithand god bless the united states of americaand may the light perpetually shine upon the fallah bring comfort to their familiesum god protect our troopstoday andgod bless you allum


Make some buttons unclickable until server feedback

Similar to how we made the task collection button not clickable twice while waiting on server feedback, we should do this for other buttons as well.
This came up because it was possible (due to some performance issues in 1.4.1) for users to submit the same job multiple times by clicking the Confirm button in "Run workflow" multiple times. We should think about whether other buttons also could have this issue where it would matter.
I don't care too much about behaviors that would be unproblematic. e.g. download job logs: If a user clicks that 5x, they may get the job logs 5 times. But nothing breaks.
Buttons to deactivate after click until server response:

[x] Confirm job submission
[x] Task updating (on the workflow page)
[x] Maybe project creation?
[x] Maybe dataset creation?
[x] Maybe workflow creation/import?

Not 100% sure whether it makes sense for the new creation buttons / how they'd handle multiple clicks if the server response was very slow

That looks great!


command_callback deprecation warning

Information
VIM version NVIM v0.3.4

Operating System:  macOS 10.14
What went wrong

I get the following warning when I start neovim.
command_callback is deprecated. Use `let g:ale_ignore_2_4_warnings = 1` to disable this message.
command_callback is deprecated. Use `let g:ale_ignore_2_4_warnings = 1` to disable this message.

I found a recent addition still using the deprecated options, but there might be others from other plugins. grep your linters from various plugings, and let me know which ones still use command_callback. They'll have to be updated to use command instead. You can disable the warning with the variable in the message.

@w0rp Thank you. I already had the warning disabled, but I reported the issue to help others.
Grepping the plugins folder returns a large list.
rg -l command_callback output:
plugged/ale/test/test_temporary_file_management.vader
plugged/ale/doc/ale-development.txt
plugged/ale/test/test_linter_defintion_processing.vader
plugged/ale/test/handler/test_lacheck_handler.vader
plugged/ale/test/command_callback/test_html_stylelint_command_callback.vader
plugged/ale/test/command_callback/test_ruby_solargraph.vader
plugged/ale/test/command_callback/test_scala_sbtserver.vader
plugged/ale/ale_linters/powershell/psscriptanalyzer.vim
plugged/ale/autoload/ale/linter.vim
plugged/ale/autoload/ale/assert.vim
plugged/ale/test/fixers/test_standardrb_fixer_callback.vader
plugged/ale/test/fixers/test_php_cs_fixer.vader
plugged/ale/test/fixers/test_uncrustify_fixer_callback.vader
plugged/ale/test/fixers/test_autopep8_fixer_callback.vader
plugged/ale/test/fixers/test_tslint_fixer_callback.vader
plugged/ale/test/fixers/test_rufo_fixer_callback.vader
plugged/ale/test/fixers/test_swiftformat_fixer_callback.vader
plugged/ale/test/fixers/test_clangformat_fixer_callback.vader
plugged/ale/test/fixers/test_phpcbf_fixer_callback.vader
plugged/ale/test/fixers/test_rubocop_fixer_callback.vader
plugged/ale/test/fixers/test_prettier_fixer_callback.vader
plugged/ale/test/fixers/test_bibclean_fixer_callback.vader
plugged/ale/test/fixers/test_tidy_fixer_callback.vader
plugged/ale/test/fixers/test_isort_fixer_callback.vader
plugged/ale/test/fixers/test_yapf_fixer_callback.vader
plugged/ale/test/fixers/test_puppetlint_fixer_callback.vader
plugged/ale/test/fixers/test_scalafmt_fixer_callback.vader
plugged/ale/test/fixers/test_black_fixer_callback.vader

Looks like the only one you had was psscriptanalyzer, the one I just updated.


Should extension contributes.keybindings work

@CGNonofr when I directly set keybindings in the contributes section of the object that I pass to registerExtension(extension) I get the following error. Is this expected behaviour, because it is not supported? Setting it with updateUserKeybindings works:

Well spotted, I didn't use that part so I didn't test it
here's the fix: https://github.com/CodinGame/monaco-vscode-api/pull/88
btw, the configuration and configurationDefault extensions point are not handled, it'll come soon in another PR

Sounds great


[DO NOT MERGE] Add analytics from govuk_frontend_toolkit

What
Migrate analytics code from govuk_frontend_toolkit into static.
Why
We are trying to retire govuk_frontend_toolkit and many other applications depend upon these analytics scripts. Moving these scripts into static is the first step in the eventual plan to move them into govuk_publishing_components.
WIP
Todo:

fix failing tests (failing tests are currently skipped). Currently this is only the error tracking tests.

Supersedes https://github.com/alphagov/static/pull/1777/

We might need to press ahead with this (for reasons, happy to discuss).
The only thing that isn't finished here yet is I still haven't figured out a way of testing the error-tracking. The test actually passes, but because we're generating a deliberate error, jasmine notices and counts it as a test failure (I've tried a lot of workarounds but if you think of anything let me know). I've currently marked the two tests in question as 'skip' (see the commit marked WIP).
@alex-ju @vanitabarrett @injms

@andysellick I think we can create issues for that test and move on with it

@alex-ju awesome. I've just gone through this PR, I've structured the commits to make it easy to review. Hopefully shouldn't take long.

@alex-ju I've now tested this using a locally running copy of collections pointing to a locally running copy of static. There was an error, which I have fixed, which was related to the 'fix ecommerce tests' commit. GA events are now firing correctly. Good idea to test locally!
I agree that merging all the scripts into the same dir at some point is a good idea but actually for now it's been helpful to have them separate as it's easier to see where they're coming from in the browser. This has been helpful for reasons I can go into offline, if you're interested.

Tested this by comparing logs from Google Analytics debug. Also checked that beacon messages are being sent and interactions are triggered. 🤞


[gatsby-theme-minimal-blog]How do I got about adding a contact form (just like the about section in this theme)?

I am a beginner to React and Gatsby.
Firstly, I tried to make a contact folder in pages and added an index.mdx. However, it was not able to render the form. It seems I need to create a contact.js file in the pages but when I did so it did not work.
I was trying to follow this: https://www.gatsbyjs.com/docs/building-a-contact-form/

this will help you on what "Shadowing" mechanism is on Gatsby
[(https://www.gatsbyjs.com/docs/recipes/pages-layouts/)]

Hey, thanks for the question!
Like with the "About" section you should create a MDX file inside the content/pages directory: https://github.com/LekoArts/gatsby-starter-minimal-blog/tree/master/content/pages
You then can (like in the about page) write/add content you like, including React components. Of course, you can also create a file src/pages/contact.js but then you'll need to import components from the theme to keep the same aesthetics.
So create a file at content/pages/contact/index.mdx with the contents:
---
title: Contact
slug: "/contact"
---

import ContactForm from "./contact-form"

You can contact me here:

<ContactForm />

You'll need to have a ContactForm component in the same directory for this to work.

Hi,
Thank you for taking the time to give a response. Really appreciate it!


Cognito not recognised as second auth type

Before opening, please confirm:

[X] I have installed the latest version of the Amplify CLI (see above), and confirmed that the issue still persists.
[X] I have searched for duplicate or closed issues.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

How did you install the Amplify CLI?
No response
If applicable, what version of Node.js are you using?
No response
Amplify CLI Version
4.52.0
What operating system are you using?
Mac
Amplify Categories
auth
Amplify Commands
push
Describe the bug
I would like to use multiple auth types within my schema. I'm using IAM and Cognito. When I add Cognito related permissions and push I receive an error and the project rolls back. I've been trying to resolve this for weeks, but no matter the documentation I've been unable to resolve it.
Expected behavior
I would expect to be able to use this syntax within my schema:
      { allow: public, provider: iam, operations: [read] }
      {
        allow: groups
        groups: ["MEMBER", "EDITOR"]
        operations: [read]
      }
      {
        allow: groups
        groups: ["ADMIN"]
        operations: [read, update, create, delete]
      }

Reproduction steps

On my Admin UI Data modeling screen the Authorization mode is IAM.
On AppSync under settings I can see my Default authorization mode is IAM, and I've added an additional authorization Cognito User Pool provider which has my correct UserPoolID assigned.

At this point I when I added a cognito auth directive to my schema and ran amplify push, I received an error saying cognito was not added to the project. I then followed the steps below.
Add Cognito as an additional auth type via cli

amplify update api
graphQL
Walkthrough all configurations
IAM
Yes, I want to make some additional changes.
Configure additional auth types: Y
Cognito UserPool configuration
amplify push

The cli then updates backend-config to add the following:
 "api": {
    "goodsoulsevents": {
      "service": "AppSync",
      "providerPlugin": "awscloudformation",
      "output": {
        "authConfig": {
          "defaultAuthentication": {
            "authenticationType": "AWS_IAM"
          },
          "additionalAuthenticationProviders": [
            {
              "authenticationType": "AMAZON_COGNITO_USER_POOLS",
              "userPoolConfig": {
                "userPoolId": "authgoodsoulsevents"
              }
            }
          ]
        }
      }
    }

Note: I'm unsure where this userPoolId comes from? It is not the ID that I see when I go to my userpool in Cognito.

I then add an additional auth type to my schema:

type Event
	@model
	@auth(
		rules: [
			{ allow: public, provider: iam, operations: [read] }
			{ allow: groups, groups: ["MEMBER", "EDITOR"], operations: [read] }
			{
				allow: groups
				groups: ["ADMIN"]
				operations: [read, update, create, delete]
			}
		]
	) {

note: ["MEMBER", "EDITOR", "ADMIN"] are groups I have set up within Cognito.

amplify push

I then receive this error:
Resource is not in the state stackUpdateComplete An error occurred during the push operation: Resource is not in the state stackUpdateComplete
GraphQL schema(s)
No response
Log output

# Put your logs below this line

Additional information
No response

@jhockett is it possible to get a response to this? It's completely blocking me from launching my app. If there's no credible fix I'll need to consider solutions away from AWS as I've spent so much time already faffing around with various issues like this.

hi @kymmeh - i'm curious how you've created the Cognito User Pool? Did you run amplify add auth or configure it through the Admin UI?

@renebrandel yes I did. I decided to remove the auth and set it up again today so I can be clear on the steps followed.

I ran amplify add auth and set up cognito with some groups
I then ran amplify update api setting IAM as default, and cognito as an additional type
I then ran amplify push which deployed with no problem
At this point I'm able to access data from the API when logged out
I add the below to one one of the auth directives on my schema:

      {
        allow: groups
        provider: userPools
        groups: ["MEMBER", "EDITOR"]
        operations: [read]
      }

I then ran amplify push which fails on deployment with error:

Resource is not in the state stackUpdateComplete. An error occurred during the push operation: Resource is not in the state stackUpdateComplete

@renebrandel @jhockett Is there going to be a response to this? I think the only safe solution for my project is to move away from AWS despite all of the time I've put it. Various features seem to be "in flux" which is creating far too much risk. This is hugely disappointing.

hi @kymmeh - sorry for dropping the ball on this. We're still in the process of reproducing this.

Hey @kymmeh :wave: I'm actively working through reproducing this issue, but in the mean time could you send your project's /amplify folder as a ZIP archive to<EMAIL_ADDRESS>?

Hey @kymmeh 👋 I'm actively working through reproducing this issue, but in the mean time could you send your project's /amplify folder as a ZIP archive to<EMAIL_ADDRESS>?

Thanks. I've sent this across.

Hey @kymmeh thank you for sending that over. I have received it and am actively investigating

@kymmeh was the Cognito resource initially added to AppSync via the console or Admin UI and then also attached with the CLI steps provided? I am not able to reproduce on the current version of the CLI (5.1.0) with the steps provided.
Does running amplify api gql-compile before push change the push behavior? This error you received is what I am currently looking into, however after downgrading to version 4.52.0 of the Amplify CLI I was still not able to reproduce.
No data source found named NONE (Service: AWSAppSync; Status Code: 404; Error Code: NotFoundException

Are you also experiencing this error with the most recent version of the CLI?

I'm using version 5.1.0 of the CLI. I added Cognito via the console. I ran
amplify api gql-compile and that made no difference.
This is the rule I added to the User model:
@auth(
rules: [
{ allow: public, provider: iam }
{
allow: groups
provider: userPools
groups: ["MEMBER", "EDITOR"]
operations: [read]
}
]
)

Here's the error I get:
Following resources failed

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Mutation/resolvers/updateUser
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-User-10F3OHJY21R83%2Ff02c0c60-51d3-11eb-8af5-02058636b1d6/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Mutation/resolvers/deleteUser
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-User-10F3OHJY21R83%2Ff02c0c60-51d3-11eb-8af5-02058636b1d6/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Mutation/resolvers/createUser
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-User-10F3OHJY21R83%2Ff02c0c60-51d3-11eb-8af5-02058636b1d6/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Query/resolvers/getUser
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-User-10F3OHJY21R83%2Ff02c0c60-51d3-11eb-8af5-02058636b1d6/events

Resource Name: SubscriptiononDeleteUserResolver (AWS::AppSync::Resolver)
Event Type: create
Reason: No data source found named NONE (Service: AWSAppSync; Status Code:
404; Error Code: NotFoundException; Request ID:
0def9803-f035-4ed4-b008-cd0356047c6f; Proxy: null)

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Mutation/resolvers/deleteReservation
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-Reservation-1GU7IIZ9ZGV17%2F1d292a20-6243-11eb-8464-06134378e41e/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Query/resolvers/syncReservations
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-Reservation-1GU7IIZ9ZGV17%2F1d292a20-6243-11eb-8464-06134378e41e/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Query/resolvers/syncStayInTouches
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-StayInTouch-8QVIUQZN0TKQ%2F440b1dc0-a509-11eb-9793-0ae41cec514c/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Mutation/resolvers/deleteStayInTouch
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-StayInTouch-8QVIUQZN0TKQ%2F440b1dc0-a509-11eb-9793-0ae41cec514c/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Mutation/resolvers/updateEventPhoto
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-EventPhoto-1N4DK3UUN15AN%2F6bce9150-6244-11eb-9945-0226e4e68a80/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Mutation/resolvers/deleteEventPhoto
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-EventPhoto-1N4DK3UUN15AN%2F6bce9150-6244-11eb-9945-0226e4e68a80/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Query/resolvers/listNotifications
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-Notification-F8ZKAQTOKGTH%2F1d1b2060-6243-11eb-8b59-06c3ce5b0f0a/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Mutation/resolvers/deleteNotification
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-Notification-F8ZKAQTOKGTH%2F1d1b2060-6243-11eb-8b59-06c3ce5b0f0a/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Mutation/resolvers/createUserReview
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-UserReview-18X4XPZ484G0D%2F4419c3c0-a509-11eb-b8f9-0a97cf2c2e0e/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Mutation/resolvers/deleteUserReview
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-UserReview-18X4XPZ484G0D%2F4419c3c0-a509-11eb-b8f9-0a97cf2c2e0e/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Query/resolvers/getGender
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-Gender-U22384L245YG%2Fae954850-ba49-11eb-b772-0623977acff8/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Mutation/resolvers/updateReview
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-Review-ZHCYJHY6APNW%2F420f3610-9aea-11eb-83de-0274299c8dfc/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Mutation/resolvers/updateEventUser
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-EventUser-3BQZB5TCA8TJ%2F6bca99b0-6244-11eb-b0ca-02eb877371f0/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Mutation/resolvers/deleteEventUser
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-EventUser-3BQZB5TCA8TJ%2F6bca99b0-6244-11eb-b0ca-02eb877371f0/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Query/resolvers/syncEventUsers
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-EventUser-3BQZB5TCA8TJ%2F6bca99b0-6244-11eb-b0ca-02eb877371f0/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Mutation/resolvers/createPhoto
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-Photo-10N3OXZBVS5HC%2F881ce440-56bb-11eb-9981-0684d2026fa4/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Mutation/resolvers/deleteEvent
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-Event-6TJGLVAXSFY9%2F9d4c2730-54f0-11eb-9318-0612de4ab1bc/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Query/resolvers/syncEvents
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-Event-6TJGLVAXSFY9%2F9d4c2730-54f0-11eb-9318-0612de4ab1bc/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Mutation/resolvers/updateEmail
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-Email-1N8K7762GBIQW%2F23b0b3d0-82b0-11eb-a6d5-0a844c99bfea/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Query/resolvers/syncEmails
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-Email-1N8K7762GBIQW%2F23b0b3d0-82b0-11eb-a6d5-0a844c99bfea/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Mutation/resolvers/deleteGroupSegment
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-GroupSegment-1QG3MR4TSNRVS%2F4e5eb390-a027-11eb-89a9-0a673ba33448/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Mutation/resolvers/deleteAnnouncement
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-Announcement-1OBGHM5FZZWQ6%2F57c7a3f0-9c45-11eb-872a-06e4688f56d2/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Mutation/resolvers/createAnnouncement
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-Announcement-1OBGHM5FZZWQ6%2F57c7a3f0-9c45-11eb-872a-06e4688f56d2/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Query/resolvers/syncAnnouncements
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-Announcement-1OBGHM5FZZWQ6%2F57c7a3f0-9c45-11eb-872a-06e4688f56d2/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Query/resolvers/listAnnouncements
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-Announcement-1OBGHM5FZZWQ6%2F57c7a3f0-9c45-11eb-872a-06e4688f56d2/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Query/resolvers/listEventKeywords
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-EventKeyword-X6OHVYAGENYS%2F4e492fc0-a027-11eb-8ec4-02c760682c3a/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Mutation/resolvers/deleteBookmark
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-Bookmark-IPZ8YX7WPZDM%2F1d3eadf0-6243-11eb-91e1-0a0bde0688ce/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Query/resolvers/getBookmark
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-Bookmark-IPZ8YX7WPZDM%2F1d3eadf0-6243-11eb-91e1-0a0bde0688ce/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Query/resolvers/listBookmarks
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-Bookmark-IPZ8YX7WPZDM%2F1d3eadf0-6243-11eb-91e1-0a0bde0688ce/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Query/resolvers/listPosts
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-Post-1H4NNURVJ3856%2F9dbbc710-9afb-11eb-a622-027a3181b48c/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Mutation/resolvers/createContent
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-Content-116EUQU7YF20C%2F57d363c0-9c45-11eb-82c1-0676d2896756/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Query/resolvers/syncContents
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-Content-116EUQU7YF20C%2F57d363c0-9c45-11eb-82c1-0676d2896756/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Query/resolvers/getBooking
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-Booking-1IK3YEPLOALXT%2Fccb9af90-61b8-11eb-adbd-0297c9045a12/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Query/resolvers/listBookings
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-Booking-1IK3YEPLOALXT%2Fccb9af90-61b8-11eb-adbd-0297c9045a12/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Mutation/resolvers/updateBooking
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-Booking-1IK3YEPLOALXT%2Fccb9af90-61b8-11eb-adbd-0297c9045a12/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Query/resolvers/syncBookings
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-Booking-1IK3YEPLOALXT%2Fccb9af90-61b8-11eb-adbd-0297c9045a12/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Mutation/resolvers/deleteBooking
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-Booking-1IK3YEPLOALXT%2Fccb9af90-61b8-11eb-adbd-0297c9045a12/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Mutation/resolvers/updateArticle
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-Article-1S2Q4HNX0O58D%2F22b65340-9ae3-11eb-a694-0242e9b025b6/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Query/resolvers/getArticle
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-Article-1S2Q4HNX0O58D%2F22b65340-9ae3-11eb-a694-0242e9b025b6/events

Resource Name:
arn:aws:appsync:eu-west-2:386265790739:apis/i3jji5w3xrhf3gfj77zihsbf6m/types/Mutation/resolvers/deleteArticle
(AWS::AppSync::Resolver)
Event Type: update
Reason: Resource update cancelled
URL:
https://console.aws.amazon.com/cloudformation/home?region=eu-west-2#/stacks/arn%3Aaws%3Acloudformation%3Aeu-west-2%3A386265790739%3Astack%2Famplify-goodsoulsevents-develop-170310-apigoodsoulsevents-1UXIWJ21IGUMT-Article-1S2Q4HNX0O58D%2F22b65340-9ae3-11eb-a694-0242e9b025b6/events

✖ An error occurred when pushing the resources to the cloud

Resource is not in the state stackUpdateComplete
An error occurred during the push operation: Resource is not in the state
stackUpdateComplete

On Thu, 8 Jul 2021 at 20:44, josef @.***> wrote:

@kymmeh https://github.com/kymmeh was the Cognito resource initially
added to AppSync via the console or Admin UI and then also attached with
the CLI steps provided? I am not able to reproduce on the current version
of the CLI (5.1.0) with the steps provided.
Does running amplify api gql-compile before push change the push
behavior? This error you received is what I am currently looking into,
however after downgrading to version 4.52.0 of the Amplify CLI I was still
not able to reproduce.
No data source found named NONE (Service: AWSAppSync; Status Code: 404; Error Code: NotFoundException
Are you also experiencing this error with the most recent version of the
CLI https://github.com/aws-amplify/amplify-cli/releases/tag/v5.1.0?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aws-amplify/amplify-cli/issues/7500#issuecomment-876697566,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ABCKEAAMFEIYVPLVABQ2423TWX5ZPANCNFSM46PA5SLA
.

Thank you @kymmeh for confirming! May you also verify there is a NONE data source showing in the AppSync console under "Data Sources"?

To follow-up on my last comment, we should also see the creation of the NoneDataSource in the CloudFormation logs. This can be found via the console at CloudFormation > Stacks > click on appropriate nested stack for the API (example: amplify-{projectName}-{env}-101907-api{projectName}-5QRHM2077BZ9) > click on "Resources" tab > filter for "none"

@josefaidt thank you for helping with this! For the first time in months I'm unblocked. I created a data source of NONE (which obviously is not ideal), but it has meant I'm able to push without errors.

🙌 I'm glad we were able to get a workaround to the issue! This does seem like it is a bug given that data source was not created. Were you able to identify any errors in the logs in CloudFormation or CloudWatch? I created a new project following the steps provided and was able to get almost identical CFN templates but without reproducing this issue so I'm curious if there's anything that stands out in the logs.

Closing issue, @kymmeh if you experience this issue again or identify any significant logs in CloudFormation or CloudWatch related to the creation of the NONE data source please let us know and we can re-open this issue to investigate further 🙂


Add installation instructions

As a new user, it's confusing to figure out how I have to install this. This makes it explicit and easy.

Wox is also portable, so I think if we add installation instructions, we need to clarify those two ways.


Add booleans to the language

Add boolean as privimites
Add and, not  and or as boolean operation

As discussed, an alternative is to make syntax for booleans instead of providing primitive variables.
Scheme uses #t and #f @tkers

We should then add some constrain in the compiler to avoid overwriting primitives (or maybe a subset of them 🤔 ). I do not really like a lot having true and false defined as #t and #f.

Well, if you have #t and #f you don't need true and false!
Probably we should make just impossible to redefine things (outside of the REPL).


refact: enhance state management and full typescript support

cleaner and more readable code

I thought it would be more understandable for newcomers and much easier and less intimidating to add new features if the code was strongly typed and split into a hierarchy :)

I plan to review/test this tonight or tomorrow

I had some issues running the orig repo (and yours) but they are on my side. I'll come back to this soon.

please reinstall dependencies using yarn

@2byrds have you had a chance to integration test this PR?


@reduce decorator

We currently do not have anything similar to @cuda.reduce and the output of this step should be a design to support a similar @reduce decorator for numba-dppy.

Related issues:

https://github.com/IntelPython/numba-dppy/issues/71
https://github.com/IntelPython/numba-dppy/issues/78
https://github.com/IntelPython/numba-dppy/issues/96
https://github.com/IntelPython/numba-dppy/issues/93

Related issues:

https://github.com/IntelPython/numba-dppy/issues/71
https://github.com/IntelPython/numba-dppy/issues/78
https://github.com/IntelPython/numba-dppy/issues/96
https://github.com/IntelPython/numba-dppy/issues/93


RFP- qBittorrent Beta

qBittorrent beta builds are officialy available at fosshub.com.

Oops, probably, this package is not allowed: https://github.com/chocolatey/package-validator/wiki/ScriptsDoNotDownloadFromFossHub

since a beta package should be provided as a part of the stable package, and not a separate package.
Please open an issue over at the maintainer repository: https://github.com/chocolatey/chocolatey-coreteampackages

@AdmiringWorm Thanks for the info. But is Firefox's package different?
https://chocolatey.org/packages/firefox
https://chocolatey.org/packages/firefox-beta

@dimqua not really, just different maintainers, and the duplication was maybe not noticed when it was pushed.


Add support for tabs

Tabs are represented by tab characters in Mobiledoc, ala \t, and in rendered DOM are represented as an emspace: \u2003. This is a compromise for expediency. To use a non-character (a span without contenteditable enabled) we would need to take on many of the challenges atoms area already taking on. I prefer to call this a workable solution and we can tweak the DOM representation at a later time.
Additionally fix an issue with white-space only markers being the first thing in a section. They were disregarded by the renderer, errantly.

This will require followup PRs to the renderers, but is harmless to merge (the renderer will just render a tab character, which in HTML will be invisible).
Fixes https://github.com/bustlelabs/mobiledoc-kit/issues/187

Looks good! @mixonic I added few style and clarity-related suggestions.

:clap:


ESP crashes when trying to destroy websocket. (IDFGH-12584)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

IDF version.
4.3.7
Espressif SoC revision.
ESP32 Wrover IE
Operating System used.
Windows
How did you build your project?
Command line with idf.py
If you are using Windows, please specify command line type.
CMD
Development Kit.
ESP 32 Wrover IE
Power Supply used.
External 3.3V
What is the expected behavior?
Websocket should be properly closed all mallocated memory should be free.
What is the actual behavior?
ESP32 crashing instead of freeing old websocket memory.

Steps to reproduce.

Step create websocket.
Step force to send server close frame.
Step when you receive close frame form server now try to destroy socket.
...

Debug Logs.
D (174181) TRANSPORT_WS: Opcode: 8, mask: 0, len: 2

D (174191) event: running post WEBSOCKET_EVENTS:3 with handler 0x400ebc1c and context 0x3ffe5b1c on loop 0x3ffb5e80
0x400ebc1c: websocket_event_handler at c:\users\bacancy\desktop\current_wd\bac7k4_glcd_fv_2_3\build/../components/ocpp/src/ocpp-client.c:237

W (174191) ocpp: Received data from server:�

D (174191) WEBSOCKET_CLIENT: Received close frame
D (174201) WEBSOCKET_CLIENT: Closing initiated by the server, sending close frame
D (174211) TRANSPORT_WS: Sending raw ws message with opcode 136
D (174211) RANDOM: getrandom(buf=0x3ffea162, buflen=4, flags=0)
D (174221) RANDOM: getrandom returns 4
D (174231) WEBSOCKET_CLIENT:  Waiting for TCP connection to be closed by the server
D (174231) event: running post WEBSOCKET_EVENTS:4 with handler 0x400ebc1c and context 0x3ffe5b1c on loop 0x3ffb5e80
0x400ebc1c: websocket_event_handler at c:\users\bacancy\desktop\current_wd\bac7k4_glcd_fv_2_3\build/../components/ocpp/src/ocpp-client.c:237

E (174241) ocpp: E   ocpp:  264: WEBSOCKET_EVENT_CLOSED

I (174561) ocpp: E   ocpp: 4438: ==== ocpp_handle_local_client START ====

W (174571) FREEHEAP: Free Heap = 103020
I (174571) ocpp: E   ocpp: 4470: OCPP websocket not connected trying to reconnect (old handle address) 0x3ffe34d4

W (174581) WEBSOCKET_CLIENT: Client was not started
I (174641) app ui: systemTickTimer called....

W (174851) graphic_lcd: Novoton FV : 0.01
W (174851) graphic_lcd: GLCD Id Tag :
W (174851) graphic_lcd: u8EvState 1 u8Mode 8
W (174851) graphic_lcd: u8err_code 0
W (174851) graphic_lcd: fVoltage 263.02 fEnergykwh 0.00
W (174861) graphic_lcd: Charging start time 0:0:0
D (175591) event: deleted loop 0x3ffb5e80
Guru Meditation Error: Core  1 panic'ed (StoreProhibited). Exception was unhandled.

Core  1 register dump:
PC      : 0x400995b6  PS      : 0x00060333  A0      : 0x80099ef9  A1      : 0x3ffec0e0
0x400995b6: insert_free_block at C:/Espressif/frameworks/esp-idf-v4.3.7/components/heap/heap_tlsf.c:237
 (inlined by) block_insert at C:/Espressif/frameworks/esp-idf-v4.3.7/components/heap/heap_tlsf.c:263
 (inlined by) tlsf_free at C:/Espressif/frameworks/esp-idf-v4.3.7/components/heap/heap_tlsf.c:946

A2      : 0x3ffe4364  A3      : 0xa5a5a5a5  A4      : 0xfffffffc  A5      : 0x00000004
A6      : 0x00000014  A7      : 0x3ffebfa0  A8      : 0x3ffe5aec  A9      : 0x00000018
A10     : 0x0000000f  A11     : 0x3ffe5af4  A12     : 0x3ffe43b8  A13     : 0x00000004
A14     : 0x00000001  A15     : 0xff000000  SAR     : 0x0000001c  EXCCAUSE: 0x0000001d
EXCVADDR: 0xa5a5a5b1  LBEG    : 0x4000c46c  LEND    : 0x4000c477  LCOUNT  : 0x00000000

Backtrace:0x400995b3:0x3ffec0e0 0x40099ef6:0x3ffec100 0x40081e6a:0x3ffec120 0x4009ae51:0x3ffec140 0x400943fe:0x3ffec160 0x4014ce89:0x3ffec180 0x400f4fb8:0x3ffec1a0 0x400f612f:0x3ffec1d0 0x4009746d:0x3ffec1f0
0x400995b3: insert_free_block at C:/Espressif/frameworks/esp-idf-v4.3.7/components/heap/heap_tlsf.c:236
 (inlined by) block_insert at C:/Espressif/frameworks/esp-idf-v4.3.7/components/heap/heap_tlsf.c:263
 (inlined by) tlsf_free at C:/Espressif/frameworks/esp-idf-v4.3.7/components/heap/heap_tlsf.c:946

0x40099ef6: multi_heap_free_impl at C:/Espressif/frameworks/esp-idf-v4.3.7/components/heap/multi_heap.c:212

0x40081e6a: heap_caps_free at C:/Espressif/frameworks/esp-idf-v4.3.7/components/heap/heap_caps.c:339

0x4009ae51: free at C:/Espressif/frameworks/esp-idf-v4.3.7/components/newlib/heap.c:46

0x400943fe: vEventGroupDelete at C:/Espressif/frameworks/esp-idf-v4.3.7/components/freertos/event_groups.c:658

0x4014ce89: esp_websocket_client_destroy at C:/Espressif/frameworks/esp-idf-v4.3.7/components/esp_websocket_client/esp_websocket_client.c:457

0x400f4fb8: bac_ocpp_handle_local_client at c:\users\bacancy\desktop\current_wd\bac7k4_glcd_fv_2_3\build/../components/ocpp/src/ocpp-client.c:4479 (discriminator 6)

0x400f612f: ocpp_client_task at c:\users\bacancy\desktop\current_wd\bac7k4_glcd_fv_2_3\build/../components/ocpp/src/ocpp-client.c:5094

0x4009746d: vPortTaskWrapper at C:/Espressif/frameworks/esp-idf-v4.3.7/components/freertos/port/xtensa/port.c:168

ELF file SHA256: c908ef861af12ac4

Rebooting...
ets Jul 29 2019 12:21:46

rst:0xc (SW_CPU_RESET),boot:0x13 (SPI_FAST_FLASH_BOOT)
configsip: 0, SPIWP:0xee
clk_drv:0x00,q_drv:0x00,d_drv:0x00,cs0_drv:0x00,hd_drv:0x00,wp_drv:0x00
mode:DIO, clock div:2
load:0x3fff0030,len:7264
load:0x40078000,len:15132
load:0x40080400,len:3712
0x40080400: _init at ??:?

More Information.
I try to reconnect websocket without esp_websocket_client_destroy() API and it worked but it took 10k malloced memory (instead of releasing old memory and reusing it)
memory leak issue generated here.
plus i am destroying my websocket from my local task.

It was memory leak issue from another task.

same code working on ESP IDF 4.3.6

@Dhruvan1 I noticed that you closed and reopened the issue. Please be aware that IDF release/4.3 is no longer supported. Are you still experiencing the issue?

Yes issue was there, i found workaround and temporarily fixed it but there is something fishy there not sure what it is.
and i still can not call client stop and destroy in linear manner. (before calling this i was manually closing websocket).
if you want to check and fix it then it would be very helpful not for 4.3.7, but also for  5.x.x version also.


[Bug]: Style Settings Headers Error

When editing the style setting "Heading Font Caps Variant", Stylesettings begins erroring out.
I honestly do not use headers enough to determine if it is hindering the functionality of the setting; it does not seem to hinder color settings. I have included a gif of the action and error.

Looking at the style settings snippet, I do not see anything outwardly incorrect, but there might be something I am missing.

I can't recreate this. What are all of the versions? Do you have a partial/alpha/experimental build of anything? The values you're picking are all valid css values..

I have determined this was likely an issue with the older data.json I had with Stylesettings, so no issue! Closing. :)


Bug | Home Manager Module | Desktop Environment Icons

Description
When flatpaks are installed via the Home Manager module, Desktop Environment icons don't appear. The applications are installed under ~/.local/share/flatpak/app, and can be launched from the terminal.
Launch Output
Output when flatpaks are launched via the terminal:
Note that the directories

'/var/lib/flatpak/exports/share'
'/home/reedclanton/.local/share/flatpak/exports/share'

are not in the search path set by the XDG_DATA_DIRS environment variable, so
applications installed by Flatpak may not appear on your desktop until the
session is restarted.

Temporary Fix
Add the bellow to your Home Manager configuration:
xdg.systemDirs.data = [
    "/var/lib/flatpak/exports/share"
    "/home/<userName>/.local/share/flatpak/exports/share"
];

Reproduce

Fresh NixOS install w/ Gnome done with the provided NixOS GUI installer.
Only install the Home Manger nix-flatpak module.

My nix-flatpak Nix File
{ nix-flatpak, pkgs, user, ... }: {
        home.packages = with pkgs; [ flatpak ];

        services.flatpak = {
                enable = true;
                packages = [ { appId = "com.github.tchx84.Flatseal"; origin = "flathub"; } ];
                # TODO: Troubleshoot why adding a remote prevents flatpak install and add issue to nix-flatpak github.
#               remotes = [{
#                       name = "flathub-beta";
#                       location = "https://flathub.org/beta-repo/flathub-beta.flatpakrepo";
#               }];
                update = {
                        auto.enable = true;
                        onActivation = true;
                };
        };

#       xdg.systemDirs.data = [
#               "/var/lib/flatpak/exports/share"
#               "${user.home}/.local/share/flatpak/exports/share"
#       ];
}

They also don't appear for me as well and I am not using home manager. I can run it through command line just fine but I get the same paths error.


can i get some docs about index architecture for understand ?

rencently i start to study vespa，but i come to trouble in understanding the architecture  about Index ，and there is no explain in vespa document ，could anybody send some doc about this to my email，thanks 。
my email<EMAIL_ADDRESS>

Hi! Please refer to https://docs.vespa.ai/documentation/proton.html#index - the whole document should be relevant - and let us know what you think is missing (i.e. what questions you have that at not addressed). Thanks!
P.S. It is also a good start to read https://docs.vespa.ai/documentation/overview.html to get the full picture

thanks for your reply.
i read the url that you give me ,these docs  focus  on how use index,bud not explain how the index system is built in code ,i need help like this.
now i am reading the code of vespa about the index core conception,such as postlist,bitvector,dictionary,zcbuf,btree and so on. and i also run vespa in docker ,found that there is a lot  type of files in  index filed dir。i don't understand  how the data, struct and file is organized in the index system.
i also have a question about 0.already and 2.notalready,why this two subdb requierd to set?  how vespa is benefited from this mechanism?for one data,is it inserted to these two subdb at the sametime?

You can read about read, not ready etc. here: https://docs.vespa.ai/documentation/proton.html
We have some more design documentation but we're not keeping it up to date and therefore not publishing it. You don't need to know internal details to use Vespa effectively though ... what are you trying to achieve?

now i am intresting about index filed, and i reseaching lucence at the same while .lucence can‘t satisfy my requirement on some business scenes，but vespa perhaps can，so i intend to know more about the difference of index mechanism between the vespa and lucence，if some more design documentation can be offered，it's very helpful for me，could  the  design documentation be shared to me even the doc is not up to date ? thanks。

I am sorry we will not share the design documentation as-is, as it is at best inaccurate and misleading. As I don't know what you are looking for, I cannot easily forward a subset. Can you describe the problem you are trying to solve, then we can maybe help you? Thanks!

thanks for your reply.
I want to select a index system of high throughput rate for write and write，I try lucence and es ，but they can't satisfied ，and I found vespa in github, the document  describe that performance of vespa is very good，so i want to know the advance of it's index mechanism and the difference of performance between es and vespa, or are there some sucessful cases for reference in other companies except yahoo ? rencently I also read the document of the openseach of alibaba, i feel some similar with openseach in architecture，is there some relevance between opensearch and  vespa?

Thanks for the explanation. The usual way that search engines achieve real-time writes is by building a small reverse index (posting list) for recent wries and merging them in the background. Since inserts quickly becomes expensive even in a quite small posting list, while merging with the large posting list takes a very long time, it is often necessary to use multiple progressively larger posting lists and merge multiple times. With a high sustained write rate this becomes quite expensive and creates a lot of garbage which must be cleaned up which leads to problems sustaining stable write and query rates.
We used to do this in Vespa as well until about 8 years ago or so. Then we switched to a design where recent changes go into in-memory B-trees instead of a small posting lists which is then merged with posting lists in the background. (In addition they are appended to a transaction log for replay to guarantee durable writes).
Queries always evaluate over both B-trees and posting lists on disk. Changes to B-trees are lock free by creating new nodes up to the root on inserts/removals. Queries observe immutable B-trees during their lifetime.
Since updates in larger B-trees are cheap this design avoid the need for progressively larger indexes, and generates much less garbage and large memory operations, which makes it possible to sustain a high rate of change over long periods of time. Compared to Lucene-based systems it also helps that the Vespa backend is written in C++ which avoids GC problems typically encountered with large heaps in JVMs.
You should expect an update rate of a couple of thousand to a couple of tens of thousands write operations per second per node (depending on the size of the documents etc.) while also handling a substantial query load. Partial updates of single in-memory fields (attributes) should reach above 70k writes/sec per node.
I don't know much about Alibaba opensearch and there's no relation afaik. From a quick look it seems to be a hosted service for structured search only optimized for mobile devices (i.e small data sets moved to clients etc.)

Hello, I have another question to confirm，the memory index of vespa use B-Tree struct, is the disk index also use B-Tree struct? or other data struct?

Disk indexes (i.e the portion of the data of a field with "index" which isn't recently written and therefore is flushed to disk storage) uses a different data structure, namely a dictionary + posting list.

from the code，the dictionary and posting list structs make special designs，what benefits can be taken to vespa from this designs?

Dense storage + fast lookup (at the cost of very expensive updates, which is what the B-trees ameliorates). It's a standard data structure in search engines.


Unable to load planetDefs.xml during world loading, crashes whole client

Version of Advanced Rocketry
86
Have you verified this is an issue in the latest unstable build
N/A
Version of LibVulpes
0.2.8-32
Version of Minecraft
Forge 2709
Crash report or log (if applicable)
A high-lighted full log
https://pastebin.com/bJUUK7fJ
Complete full log
https://1drv.ms/u/s!AuxrrFvXeZw1g4h3ZwaGVp7tEgLz8A
Description of the problem
[How can you reliably reproduce the problem]

What libVulpes version? Can you pastebin the planetDefs.xml? And link it here.
Sent from my iPhone

On Jul 1, 2018, at 11:34 AM, Pythonic-Rainbow<EMAIL_ADDRESS>wrote:
Version of Advanced Rocketry
86
Have you verified this is an issue in the latest unstable build
N
Version of LibVulpes
[insert here]
Version of Minecraft
Forge 2709
Crash report or log (if applicable)
A high-lighted full log
https://pastebin.com/bJUUK7fJ
Complete full log
https://1drv.ms/u/s!AuxrrFvXeZw1g4h3ZwaGVp7tEgLz8A
Description of the problem
[How can you reliably reproduce the problem]
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

@dmodoomsirius
planetDefs.zip

I don't know if something is wrong with your planetDefs.xml but when i extract it its not valid showing a ton of 000 000 000's

@dmodoomsirius thats unfortunate. However I found that the issue happens in both client and server side. If it occurs again I will try to reupload a sample to you


OpenSSL.Light <IP_ADDRESS>000000 installs directly to C:\

previous versions installed to %ProgramFiles%, so this is is probably a bug

Definitely an oversight when I migrated the openssl.light package to AU.
I don't know when it will get fixed though, but a temporary workaround you can use is
to call choco install/upgrade with the following arguments
--params '"/DIR=C:\path\you\want\to\install\into"'


[Python][Easy] update parameterization util to catch whitespace bug

[Python][Easy] update parameterization util to catch whitespace bug

strip the whitespace of handlebars tags.
Previously found a bug where the whitespace was causing errors in catching the tags

Stack created with Sapling. Best reviewed with ReviewStack.

-> #72
#74
#71
#70
#69
#68
#67
#66
#73
#64
#63
#62

Testplan:
Created a test harness to test interop of default model, gpt model parser and HF Text generation model Parser


client.com.atproto.repo.describe_repo stopped working in atproto==0.0.49

When trying to use client.com.atproto.repo.describe_repo, from atproto==0.049 onwards & with Python 3.12.1, I get the following error, for multiple different DIDs:
BadRequestError: Response(success=False, status_code=400, content=XrpcError(error='RepoNotFound', message='Could not find repo for DID: did:plc:jcoy7v3a2t4rcfdh6i4kza25'), headers={'x-powered-by': 'Express', 'access-control-allow-origin': '*', 'ratelimit-limit': '3000', 'ratelimit-remaining': '2993', 'ratelimit-reset': '1725272140', 'ratelimit-policy': '3000;w=300', 'content-type': 'application/json; charset=utf-8', 'content-length': '98', 'etag': 'W/"62-CG83jMd+MVjPpLUk0Afdz4DlUTc"', 'vary': 'Accept-Encoding', 'date': 'Mon, 02 Sep 2024 10:15:29 GMT', 'keep-alive': 'timeout=90', 'strict-transport-security': 'max-age=63072000'})

Full traceback: traceback.txt
Contents of pip list for my test with atproto==0.0.49: requirements.txt
The following code should reproduce the bug:
from atproto import client, models

client = Client()
client.login(...)  # Add your details here
params = models.com.atproto.repo.describe_repo.Params(repo="did:plc:jcoy7v3a2t4rcfdh6i4kza25")
client.com.atproto.repo.describe_repo(params)

I tested this code in atproto==0.0.48 (where it worked), in atproto==0.0.49 (where it doesn't work), and also in atproto==0.0.52 (doesn't work).
Thanks!

(P.S. this isn't urgent as atproto.IdResolver works for what I need and that seems to be fine)

Could not find repo for DID: did:plc:jcoy7v3a2t4rcfdh6i4kza25

did you switch to proper PDS (where this DID is hosted) before calling describe_repo?

It's possible that's the problem, but I'm not sure - the code above still works right now with atproto==0.0.48 (which was released June 1st, way after multiple PDSes were implemented).
#188 references a method in atproto.sync, whereas this is in atproto.repo - not sure if that matters.
How... do you switch PDS with the client? The parameters model for the method only has a repo argument, so I'm not sure how to do that. (Sorry!)

Hmm... This is because the "main" bsky PDS is just a proxy to many other PDS... so it can automatically choose the right one. This proxy was in use before 0.0.48, right. But this is not the best way how to deal with it imho.
This is pseudo-code:
did = 'did:123'
resolver = ....
resolved_did = resolve.resolve(did)

client = Client(base_url=resolved_did.get_pds_endpoint())
repo = cllient.describe_repo(did)
print(repo)

probably it could be a cool feature to disable pds auto switching

hi @emilyhunt! do you expect any further work here or we could close it?

Can be closed!


event pass through

This makes it so that you can configure events to be allowed to be passed to overlapping siblings. This is necessary for the widget gallery that creates highlight overlays over items.
This also fixes #665

Do we want to do it via something similar to pointer-events: none;?

What about an enum: Block, Passthrough, None?

I also wasn't prefectly sure on the naming. pointer-events:none is what it is on the web so it might just be good to use that since it will be common/discoverable as the name

Yeah following with the web's name would be fine since we already have done lots of that.

Hmm. I'll skip on the enum for now. just the two states covers all current use cases so I'll just do that


2 change contact area calculation of threerollpasses

Changed the Contact area calculation so that its more representative for three-roll rolling.
Currently there is also a factor 0.999 necessary to correctly calculate the in_profile local_width - probably due to small numerical deviations.

Without further review of the code, the proposed tests still yield errors.
See:
FAILED             [100%]
test_contact_area.py:51 (test_plotted_contact_area_3fold)
self = PassSequence(in_profile=InProfile(classifiers={'round'}, cross_section=Polygon(area=0.000313654849054594, height=0.02,... zouhar_contact_c1=0.45, zouhar_contact_c2=0.18, zouhar_contact_c3=1, zouhar_contact_in_width=0.00040710935249972473)])
def _solve_subunits(self):
    if self._subunits:
        last_profile = self.in_profile

        for u in self._subunits:
            try:

              last_profile = u.solve(last_profile)

../.venv/lib/python3.12/site-packages/pyroll/core/unit/unit.py:167:

../.venv/lib/python3.12/site-packages/pyroll/core/unit/unit.py:189: in solve
current_results = self.get_root_hook_results()
../.venv/lib/python3.12/site-packages/pyroll/core/roll_pass/roll_pass.py:159: in get_root_hook_results
super_results = super().get_root_hook_results()
../.venv/lib/python3.12/site-packages/pyroll/core/unit/unit.py:157: in get_root_hook_results
self_results = self.evaluate_and_set_hooks()
../.venv/lib/python3.12/site-packages/pyroll/core/hooks.py:466: in evaluate_and_set_hooks
return list(_gen())
../.venv/lib/python3.12/site-packages/pyroll/core/hooks.py:450: in _gen
result = h.get_result(self)
../.venv/lib/python3.12/site-packages/pyroll/core/hooks.py:277: in get_result
result = f(instance)
../.venv/lib/python3.12/site-packages/pyroll/core/hooks.py:77: in call
result = self.function(instance, **extra_args)
../.venv/lib/python3.12/site-packages/pyroll/core/roll_pass/hookimpls/roll_pass.py:46: in roll_force
return (self.in_profile.flow_stress + 2 * self.out_profile.flow_stress) / 3 * self.roll.contact_area
../.venv/lib/python3.12/site-packages/pyroll/core/hooks.py:163: in get
return hook.get(instance, owner)
../.venv/lib/python3.12/site-packages/pyroll/core/hooks.py:202: in get
result = self.get_result(instance)
../.venv/lib/python3.12/site-packages/pyroll/core/hooks.py:277: in get_result
result = f(instance)
../.venv/lib/python3.12/site-packages/pyroll/core/hooks.py:77: in call
result = self.function(instance, **extra_args)
../pyroll/zouhar_contact.py:79: in contact_area
out_width = rp.out_profile.contact_lines[1].width
../.venv/lib/python3.12/site-packages/pyroll/core/hooks.py:163: in get
return hook.get(instance, owner)
../.venv/lib/python3.12/site-packages/pyroll/core/hooks.py:202: in get
result = self.get_result(instance)
../.venv/lib/python3.12/site-packages/pyroll/core/hooks.py:277: in get_result
result = f(instance)
../.venv/lib/python3.12/site-packages/pyroll/core/hooks.py:77: in call
result = self.function(instance, **extra_args)
../.venv/lib/python3.12/site-packages/pyroll/core/roll_pass/hookimpls/deformation_unit.py:100: in contact_contour_lines
upper_contact_contour = linemerge(upper_groove_cl.intersection(self.cross_section.exterior))
../.venv/lib/python3.12/site-packages/shapely/ops.py:105: in linemerge
source = MultiLineString([ls.coords for ls in lines.geoms])
../.venv/lib/python3.12/site-packages/shapely/geometry/multilinestring.py:50: in new
line = linestring.LineString(lines[i])
../.venv/lib/python3.12/site-packages/shapely/geometry/linestring.py:73: in new
geom = shapely.linestrings(coordinates)
../.venv/lib/python3.12/site-packages/shapely/decorators.py:77: in wrapped
return func(*args, **kwargs)

coords = array([[0.00908349, 0.00124419]]), y = None, z = None, indices = None
out = None, kwargs = {}
@multithreading_enabled
def linestrings(coords, y=None, z=None, indices=None, out=None, **kwargs):
    """Create an array of linestrings.

    This function will raise an exception if a linestring contains less than
    two points.

    Parameters
    ----------
    coords : array_like
        An array of lists of coordinate tuples (2- or 3-dimensional) or, if ``y``
        is provided, an array of lists of x coordinates
    y : array_like, optional
    z : array_like, optional
    indices : array_like, optional
        Indices into the target array where input coordinates belong. If
        provided, the coords should be 2D with shape (N, 2) or (N, 3) and
        indices should be an array of shape (N,) with integers in increasing
        order. Missing indices result in a ValueError unless ``out`` is
        provided, in which case the original value in ``out`` is kept.
    out : ndarray, optional
        An array (with dtype object) to output the geometries into.
    **kwargs
        See :ref:`NumPy ufunc docs <ufuncs.kwargs>` for other keyword arguments.
        Ignored if ``indices`` is provided.

    Examples
    --------
    >>> linestrings([[[0, 1], [4, 5]], [[2, 3], [5, 6]]]).tolist()
    [<LINESTRING (0 1, 4 5)>, <LINESTRING (2 3, 5 6)>]
    >>> linestrings([[0, 1], [4, 5], [2, 3], [5, 6], [7, 8]], indices=[0, 0, 1, 1, 1]).tolist()
    [<LINESTRING (0 1, 4 5)>, <LINESTRING (2 3, 5 6, 7 8)>]

    Notes
    -----
    - Usage of the ``y`` and ``z`` arguments will prevents lazy evaluation in ``dask``.
      Instead provide the coordinates as a ``(..., 2)`` or ``(..., 3)`` array using only ``coords``.
    """
    coords = _xyz_to_coords(coords, y, z)
    if indices is None:

      return lib.linestrings(coords, out=out, **kwargs)

E           shapely.errors.GEOSException: IllegalArgumentException: point array must contain 0 or >1 elements
../.venv/lib/python3.12/site-packages/shapely/creation.py:119: GEOSException
The above exception was the direct cause of the following exception:
def test_plotted_contact_area_3fold():
    import pyroll.zouhar_contact

    p: Profile = Profile.round(
        diameter=20e-3,
        temperature=1200 + 273.15,
        material=["C45", "Steel"],
        length=1,
        flow_stress=100e6
    )

    ps: PassSequence = PassSequence(
        [
            ThreeRollPass(
                label="Pass1",
                roll=Roll(
                    groove=CircularOvalGroove(
                        r1=1e-3,
                        r2=12e-3,
                        depth=3.3e-3,
                        pad_angle=30
                    ),
                    nominal_radius=150e-3,
                    rotational_frequency=1,
                ),
                inscribed_circle_diameter=18e-3
            )])

  ps.solve(p)

test_contact_area.py:80:

../.venv/lib/python3.12/site-packages/pyroll/core/unit/unit.py:186: in solve
self._solve_subunits()

self = PassSequence(in_profile=InProfile(classifiers={'round'}, cross_section=Polygon(area=0.000313654849054594, height=0.02,... zouhar_contact_c1=0.45, zouhar_contact_c2=0.18, zouhar_contact_c3=1, zouhar_contact_in_width=0.00040710935249972473)])
def _solve_subunits(self):
    if self._subunits:
        last_profile = self.in_profile

        for u in self._subunits:
            try:
                last_profile = u.solve(last_profile)
            except Exception as e:

              raise RuntimeError(f"Solution of sub units failed at unit {u}.") from e

E                   RuntimeError: Solution of sub units failed at unit ThreeRollPass 'Pass1'.
../.venv/lib/python3.12/site-packages/pyroll/core/unit/unit.py:169: RuntimeError

Sry didnt mention:
To have these changes on the zouhar package work the changes made in pyroll-project/pyroll-core#241 are also required, as the updated contact_lines property is required.
In my venv i included those changes with a .whl.
I suppose thats where the error comes from, but if not i can have a closer look again.

Added the ThreeRollPass handling to a separate Hook function - but i dont know what you specifically mean with not needing the core changes now? (or is this already clarified with the changes i did there?)

Did you resolve everything?

Added the ThreeRollPass handling to a separate Hook function - but i dont know what you specifically mean with not needing the core changes now? (or is this already clarified with the changes i did there?)

Added the ThreeRollPass handling to a separate Hook function - but i dont know what you specifically mean with not needing the core changes now? (or is this already clarified with the changes i did there?)

With this two hooks you circumvent the problem with the precedence of the hooks in the core for 3RP

I think also the comments by @axtimhaus are resolved. So please proceed.


keyv doesn't work in pnpm monorepo

Trying to use keyv and @keyv/mongo works with npm (duh), pnpm, but not if the project is a pnpm workspace. The error is "Error: Cannot find module '@keyv/mongo'".
Repro repo at https://github.com/dandv/pnpm-monorepo-keyv
Any idea what might cause this?

Ahh, so seems like pnpm is hijacking the Node.js dependency resolution algorithm somehow.
I wouldn't really consider this a bug in Keyv so I'll close this issue. Glad you got it sorted though. Thanks for reporting, hopefully this issue will help anyone else who gets stuck using Keyv with pnpm. 👍

I saw this error when I deployed my app to vercel.
I simply added one line and it worked without any other changes.
import Keyv from 'keyv'
import '@keyv/mongo' // <===
```