WIP: Add ChainRules

Closes #18
Adds support for ChainRules 1.0.
This tests
*(::AbstractVecOrMat, ::Woodbury)::Matrix
*(::Real, ::Woodbury)::WoodburyPDMat

and adds in some constructor tests too.

what's the error for 2. ? I will try to take a look at the end of the day

what's the error for 2. ? I will try to take a look at the end of the day

It is numerically very very wrong.

Not sure why the passing the Tangent was failing (the math looked fine) but solved it by creating an intermediate Woodbury. Also putting the times_pullback outside of the rrule somehow solves the inference (we have seen this before, but I don't understand it).
I still don't know why the following fails though:
julia> W = WoodburyPDMat(rand(3,2), Diagonal(rand(2,)), Diagonal(rand(3,)))
3×3 WoodburyPDMat{Float64, Matrix{Float64}, Diagonal{Float64, Vector{Float64}}, Diagonal{Float64, Vector{Float64}}}:
 1.26364   0.194865   0.14236
 0.194865  0.553561   0.0738048
 0.14236   0.0738048  0.366308

julia> T = Tangent{WoodburyPDMat}(;A=W.A, D=W.D, S=W.S)
Tangent{WoodburyPDMat}(A = [0.6529299263287578 0.9705937318111584; 0.2742328923999924 0.5824550169874951; 0.14327303956778725 0.6355464664765937], D = [0.6900525901684949 0.0; 0.0 0.12613565656887138], S = [0.8506296051551665 0.0 0.0; 0.0 0.4588742330641957 0.0; 0.0 0.0 0.3011946555949865])

julia> test_rrule(*, 2.0, W ⊢ W; output_tangent=W)
test_rrule: * on Float64,WoodburyPDMat{Float64, Matrix{Float64}, Diagonal{Float64, Vector{Float64}}, Diagonal{Float64, Vector{Float64}}}: Test Failed at /Users/mzgubic/.julia/packages/ChainRulesTestUtils/8380y/src/check_result.jl:24
  Expression: isapprox(actual, expected; kwargs...)
   Evaluated: isapprox(2.1647628223399655, 1.5169372885519636; rtol = 1.0e-9, atol = 1.0e-9)
Stacktrace:
 [1] test_approx(actual::Float64, expected::Float64, msg::String; kwargs::Base.Iterators.Pairs{Symbol, Float64, Tuple{Symbol, Symbol}, NamedTuple{(:rtol, :atol), Tuple{Float64, Float64}}})
   @ ChainRulesTestUtils ~/.julia/packages/ChainRulesTestUtils/8380y/src/check_result.jl:24
 [2] macro expansion
   @ ~/.julia/packages/ChainRulesTestUtils/8380y/src/testers.jl:238 [inlined]
 [3] macro expansion
   @ /Users/julia/buildbot/worker/package_macos64/build/usr/share/julia/stdlib/v1.6/Test/src/Test.jl:1151 [inlined]
 [4] test_rrule(::ChainRulesTestUtils.ADviaRuleConfig, ::typeof(*), ::Float64, ::Vararg{Any, N} where N; output_tangent::WoodburyPDMat{Float64, Matrix{Float64}, Diagonal{Float64, Vector{Float64}}, Diagonal{Float64, Vector{Float64}}}, check_thunked_output_tangent::Bool, fdm::FiniteDifferences.AdaptedFiniteDifferenceMethod{5, 1, FiniteDifferences.UnadaptedFiniteDifferenceMethod{7, 5}}, rrule_f::Function, check_inferred::Bool, fkwargs::NamedTuple{(), Tuple{}}, rtol::Float64, atol::Float64, kwargs::Base.Iterators.Pairs{Union{}, Union{}, Tuple{}, NamedTuple{(), Tuple{}}})
   @ ChainRulesTestUtils ~/.julia/packages/ChainRulesTestUtils/8380y/src/testers.jl:194
Test Summary:                                                                                | Pass  Fail  Total
test_rrule: * on Float64,WoodburyPDMat{Float64, Matrix{Float64}, Diagonal{Float64, Vector{Float64}}, Diagonal{Float64, Vector{Float64}}} |    8     1      9
ERROR: Some tests did not pass: 8 passed, 1 failed, 0 errored, 0 broken.

Also, I don't think we have fully figured out our story in testing arbitrary tangents (like passing a Matrix instead of the Woodbury as output_tangent). I will write an issues about this.

OK, I undestand a bit more about what's going on now:
Consider this snippet - (the tests pass at least locally (note I am using the commit prior to the one just added where the woodburyPDMat constructor is added to the pullback):
            primal = R * W

            # Generate the Tangent as ChainRulesTestUtils would do
            W̄ = rand_tangent(Random.GLOBAL_RNG, collect(primal))
            T = ProjectTo(primal)(W̄)

            res = ChainRulesCore.rrule(*, R, W)
            f_jvp = j′vp(ChainRulesTestUtils._fdm, x -> (*(x...)), T, (R, W))[1]

            # Expected
            R̄ = ProjectTo(R)(dot(W̄, W'))
            W̄ = ProjectTo(W)(conj(R) * W̄)

            R̄_rrule = unthunk(res[2](T)[2])
            W̄_rrule = unthunk(res[2](T)[3])

            @test res[1] == primal
            @test R̄ ≈ f_jvp[1]
            @test W̄.A ≈ f_jvp[2].A
            @test W̄.D ≈ f_jvp[2].D
            @test W̄.S ≈ f_jvp[2].S

ProjectTo is pushing the tangent W̄ into it's constituents, A, D and S. It is not the case that W̄ = ∂W.A * ∂W.D * ∂W.A' + ∂W.S. We want W̄.

I'm not sure what is intended is possible in the present set-up. If we consider the pullback and the projection:
function _times_pullback(Ȳ::AbstractMatrix, A, B, proj)
    Ā = proj.A(dot(Ȳ, B)')
    B̄ = proj.B(A' * Ȳ)
    return (NoTangent(), Ā, B̄)
end

function (W::ProjectTo{T})(W̄) where {T<:WoodburyPDMat}
    Ā(W̄) = ProjectTo(W.A)((W̄ + W̄') * (W.A * W.D))
    D̄(W̄) = ProjectTo(W.D)(W.A' * (W̄) * W.A)
    S̄(W̄) = ProjectTo(W.S)(W̄)
    return Tangent{T}(; A = Ā(W̄), D = D̄(W̄), S = S̄(W̄))
end

We want the pullback to support Ȳ::Tangent{WoodburyPDMat. The snippet above shows that passing through W̄ .
However, this will have the fields A,D,S with their associated pullbacks due to the Projection. Not W̄ .
Two options to consider:
We can't recover W̄ from the Projection (non of the entries are invertable, in general projections are likely to be lossy). Put another way, the structured differentials can't recover the natural differential (if this is the right language to use). Which may imply that this projection isn't what we want.
We could extend the tangent representation to include the natural differential, however with some playing with the canonicalize this isn't possible as CRC assumes for any structured matrix the tangent fields match the primal fields.
So we want the projection when testing the vectorised representation of the woodbury, but we also don't want it if we want to push the tangent back further down the chain rule.
Though I've probably misunderstood something somewhere.

I was thinking about the last option. I only think it is possible to go from Woodbury to a vector, but not back (as far as I know it is not possible to "factorise" an arbitrary dense matrix to a Woodbury?).
It might still solve our problems, because in some cases only going to a vector is required (and not going back).

I've cleaned up this MR now - it should be ready to go.
As there were several discussion points previously, I'll give an overview:

Updates to use ChainRulesCore v1.

Inplements a ProjectTo for the Woodbury that takes a dx::AbstractMatrix and projects that pushback onto the constituent elements of the Woodbury. Essentially, as we know that W = A D A' + S, we know how Ā, D̄, S̄ can be constructed from W̄. So if W̄ is a Matrix, Project is used to produce the Tangent{WoodburyPDMat}(A = Ā, D = D̄, S = S̄). If W̄ is already a Tangent, Project just passes this through as it is in the correct subspace.

The rrules for Diagonal * Woodbury (and reverse), and the rrules for Real * Woodbury (and reverse) are implemented. These capture two different scenarios for the rrules. In the first case, abbreviated to Dmat * W this returns a dense Matrix in the primal, and thus the cotangent will be a Matrix. In the second case, abbreviated to R * W, this returns another Woodbury, and thus the cotangent will be of type Tangent{WoodburyPDMat}. So we have:

(D * W)::Matrix - This is covered by existing rrules as the cotangent will be a Matrix and we have ProjectTo specified.
(R * W)::WoodburyPDMat - This requires custom rrules because we need to work with a cotangent of type Tangent{WoodburyPDMat}.

We don't need to test (D * W) with a Tangent{WoodburyPDMat} cotangent because the primal type is a Matrix. I have added a  (R * W) with a Matrix cotangent test but we can't use test_rrule for this directly, as commented.

The WoodburyLike thing is removed. In retrospect I don't particularly like the Woodbury being force-constructed from the constiutent gradients, but it does mean that the existing tests can just be used (i.e. the output of f_jvp does create a Woodbury, but it's unlikely to be a valid one).

Will take out of WIP.

I'm just going to close this MR. I had largely set-out to try and understand CR through implementing rules for the woodbury (and follow up with a resolution to the Woodbury * diagonal AD workaround that was neccessary) with the presumption that the rules would be more performant (i neever got to benchmarking these) but this seems the wrong view.
There may be some follow-ups (such as opt-outs and supporting CRC 1) but it seems best to do that with a clean slate.


Same-origin server fetch missing credentials for absolute paths

Describe the bug
https://github.com/sveltejs/kit/blob/5cea0c2e1b350d4f1794d5dd9572c940178c3478/packages/kit/src/runtime/server/page/load_node.js#L100-L103
Currently, all absolute fetch requests are treated as cross-origin, and cookies are not passed through. This does not adequately cover the three main cases of same-origin sites where cookies are shared:

Different port on the same domain, e.g. localhost:3000 and localhost:5000
Subdomains, e.g. api.domain.com and domain.com
The same domain and port, but specified as an absolute path to satisfy some library (e.g. Apollo, which sucks)

However, this is not a trivial fix:

Passing in cookies for all external requests would lead to indiscriminately sending cookies to cross-origin domains, which is wasted bandwidth at best and a security violation at worst.
Browsers do not send the domain associated with cookies. A SvelteKit server hosted at sub.domain.com can receive cookies from domain.com OR sub.domain.com and cannot distinguish the two.

The lack of domain information presents various issues and limitations for potential solutions.
[Loose] If we assume that received cookies all belong to the second-level domain:

We must identify what a "second-level domain" actually is (e.g. domain.co.uk exists, so we cannot blindly assume the level of the domain based on the number of separators)
This is a security issue for subdomains that are shared with others, as is common in shared hosting (e.g. vercel, github pages, js.org) as it can happily send all vercel.app cookies to malicious.vercel.app
This assumption is invalid for any pages hosted on direct IP addresses (eg. https://<IP_ADDRESS> from Cloudflare)

[Strict] If we pick the strictest domain and assume received cookies belong to the current domain of the application:

A SvelteKit app hosted at sub.domain.com would have to assume domain.com cookies as sub.domain.com cookies, and so api.domain.com would not be eligible to receive the cookies from server-side fetch using this algorithm, despite the fact that they would normally be passed by the browser clientside.
The above behavior would require extensive documentation, as it would be a difference between the client and the server fetch.

The above also assumes we can adequately identify the current host. The Host HTTP header can be manipulated by the client, which seems questionable. A configurable setting may lead unaware devs to emulate the loose mode to "make things work" and turn the feature into a footgun.
To Reproduce
https://github.com/GrygrFlzr/sk-cookie-issue
Expected behavior
Cookies passed through to the API endpoint for the "Same Domain and Port" and "Same Domain, Different Port" cases.
Information about your SvelteKit Installation:
Diagnostics
  System:
    OS: Windows 10 10.0.22000
    CPU: (16) x64 AMD Ryzen 7 3700X 8-Core Processor
    Memory: 15.96 GB / 31.93 GB
  Binaries:
    Node: 14.16.0 - C:\program files\nodejs\node.EXE
    Yarn: 1.22.10 - ~\AppData\Roaming\npm\yarn.CMD
    npm: 6.14.13 - C:\program files\nodejs\npm.CMD
  Browsers:
    Chrome: 91.0.4472.124
    Edge: Spartan (44.22000.1.0), Chromium (91.0.864.59)
    Internet Explorer: 11.0.22000.1
  npmPackages:
    @sveltejs/kit: next => 1.0.0-next.119
    svelte: ^3.34.0 => 3.38.3

Severity
Depends:

Annoyance for situations where proxying the API in SvelteKit is possible - it's an extra network trip.
Blocking for situations involving third party libraries.

Thank you for opening this.
I feel like behaviour should follow browser standards.
domain.com cookies should only be for "domain.com" - and not subdomains.
.domain.com cookies are available on all subdomains.
There is no need to "assume received cookies belong to the current domain" when there is already an explicit way of specifying what the cookie belongs to.

I don't know how to emphasize "browsers do not send domain information of cookies" more than I already have, which is why we're stuck with assuming in the first place.

I feel like behaviour should follow browser standards.
domain.com cookies should only be for domain.com - and not subdomains.
.domain.com cookies are available on all subdomains.

This is outdated and has not been true for a while. RFC 2109 describes the behavior you mentioned, but RFC 6265 trumps it and ignores the leading dot:

The Domain attribute specifies those hosts to which the cookie will be sent. For example, if the value of the Domain attribute is "example.com", the user agent will include the cookie in the Cookie header when making HTTP requests to example.com, www.example.com, and www.corp.example.com. (Note that a leading %x2E ("."), if present, is ignored even though that character is not permitted, but a trailing %x2E ("."), if present, will cause the user agent to ignore the attribute.) If the server omits the Domain attribute, the user agent will return the cookie only to the origin server.

Ah well that's good to know. I still see it around so much (including right here on Github). Thanks for the response and for looking into this issue in any case. I'll probably just be heading down the proxy route in the meanwhile, but hopefully this can be resolved for the future.

And sorry, I see your point now on not knowing what domain the cookie is actually set up for. Makes sense.
In some other scenarios, I've seen this dealt with by optional attributes/settings along the lines of "domainCookie=true" or similar to force the framework to set domain cookies. Perhaps a similar approach could be used?

Has this been released as of 1.0.0-next.162? I'm having this issue still.

if you talking about https://github.com/sveltejs/kit/pull/1847/files, yes that should work. at least for me. maybe share the code which is not working for you?

The code is nothing special. It's a simple fetch to an absolute URL on the same domain, no options being passed in.
fetch('http://localhost:8080/api/dictionaries')
Checking the cookie header in the handle-hook will reveal that during SSR no cookies are passed through , but if I disable SSR for the module the cookies arrive as expected.

where are you calling the fetch method? in needs to be inside the module script tag. also directly in the load method. if you do it anywhere else not the internal fetch method from svelte-kit will be used. as i wanted to use it in some api wrapper i basically store the fetch object for later usage there from the __layout file. then when i want to make an api call i just use it. you should also include credentials:'include'
let me share some code to you:
__layout.svelte
<script context="module">
	import { setup } from "$lib/utils/api.js";

	export async function load({ page,fetch,session}) {
              setup(fetch); //<-- store internal fetch for later usage. you can also pass it everytime, but i didn't wanted that
........

someFile.svelte
<script context="module">
    import { print } from 'graphql/language/printer.js'
    import { query } from "$lib/utils/api";
    import gql from "graphql-tag";

        export async function load({ session, fetch, context, page }) {
            let res = await query(gql` //<--- i am calling an graphql endpoint by hand ,but this can also just be a regular rest server. in fact i am doing both
                        query {
                            ......
                        }
                    `
                )
            return {
                props: {
                    xxxxxx
                }
            };
        }
    </script>

api.js
export function setup(fetchlib) {
    if(myFetch) return;
    myFetch = fetchlib;
}
export async function query(query) {
  let res = await myFetch(VITE_APIURL + "/graphql",
  {
    method: 'POST',
		mode: "cors",
    credentials:'include',
    body: JSON.stringify({query: print(query)}),
    headers: {
      'Accept': 'application/json, text/plain, */*',
      'Content-Type': 'application/json'
    },
  })

  if (res.status != 200) {
    throw new Error(`expected status 200, got ${res.status}`)
  }

  return await res.json()
}

hope there is something here that helps you out

There's also https://github.com/sveltejs/kit/pull/2362 pending which might help you

@eikaramba Thanks for the thorough explanation.
I must've been using the wrong fetch since it started working after som refactoring. It's really confusing that the functions have the same signature but behave different depending on context though...

I am really struggling with the same problem and I have no idea how to make authentication work with HttpOnly cookies. I am running SvelteKit on http://localhost:4000, I have an API running on http://localhost:8000, and when log in on the API server, it returns a set-cookie header with a token (and HttpOnly set). But none of the API requests I make after that contain that token cookie, even though I did include credentials: "include" in my fetch options.
I have no clue what I am doing wrong, of if SvelteKit (as of 165) even supports this kind of setup at all? Do I need to route all API requests through SvelteKit endpoints? I'd be very happy to pay an expert to help me get this all sorted out.

@kevinrenskers sounds like you did not set the handle function in the hooks file (hooks/index.js). Your setup definitely should work, i have the same. you can also ping me directly if you want
import * as cookie from 'cookie';
/**
 * The getContext hook return value is exposed on the request object that is passed to endpoint routes. This is data that is, in general, not necessarily safe to expose to the browser.
 */
export async function handle({ request,resolve }) {
	const cookies = cookie.parse(request.headers.cookie || '');

	const token = cookies['token']
	const jwtPayload = token ? jwt.decode(token) : false;
	request.locals.authenticated = !!jwtPayload

	const response = await resolve(request);

	return {
		...response,
		headers: {
			...response.headers,
		}
	}
}
/**
 * The getSession hook takes this context and returns the session that is exposed to load functions (and in the $session store).
 */
export function getSession(request) {
				// only include properties needed client-side —
			// exclude anything else attached to the user
			// like access tokens etc
	return {
		// user:  context.user,
		...request.locals
	}
}

My hooks currently look like this:
import cookie from "cookie";

export const handle = async ({ request, resolve }) => {
  const cookies = cookie.parse(request.headers.cookie || "");
  console.log(cookies);
  request.locals.token = cookies.token;
  return await resolve(request);
};

export function getSession({ locals }) {
  return {
    token: locals.token,
  };
}

Also with mode:"cors" added, it still doesn't work. I'd love to ping you directly but you have no contact info in your GitHub profile 🙈


Responsive issues

Hi there, I'm using Bootstrap 4 (as many people) so for example, when using xs breakpoint (ie. mobile devices) some elements converts to "100% width blocks" so we need to avoid the animations.
As with laxxx library we are using data-attributes and we can't manage theme with media queries, is there any way to manage animations regarding breakpoints?
My suggestion:
Be able to define breakpoints in the setup:
lax.setup({breakpoints: {xs:0, sm:'576px', md:'768px', lg:'992px'}});
So we could use like this:

Hey,
Yes - something like this makes sense. I'll take a look, maybe data-lax-opacity#md would be better.

@afanjul I have implemented support for breakpoints (not on presets yet). Please take a look at docs/simple.html on this branch I created: https://github.com/alexfoxy/laxxx/tree/responsive
Also try out the library from this branch in src/lax.js and see how you get on. If it works well for you I will add support for presets and merge with the master branch.
Usage is like this:
lax.setup({
  breakpoints: { xs: 0, s: 576, m: 768, l: 992  }
})
```
then
```

```
You don't have to define all the breakpoints, it will just fallback to the default setup.

Wow @alexfoxy !! I was forking your code just to add the responsive support ^_^ but what a surprise when I saw that you have already done it !!
And in deed I was testing it already (as soon as I saw a responsive branch ^·^).
I saw a problem in https://github.com/alexfoxy/laxxx/blob/fee90b3a82d30380d7617937608b9fb131a17d7f/src/lax.js#L253 because if we use #xs for the data attribute, the queryAllSelector does not get them...
Maybe is what you referred for "preset" support?

Wow @alexfoxy !! I was forking your code just to add the responsive support ^_^ but what a surprise when I saw that you have already done it !!
And in deed I was testing it already (as soon as I saw a responsive branch ^·^).
I saw a problem in
laxxx/src/lax.js
Line 253 in fee90b3
document.querySelectorAll(selector).forEach(this.addElement)
because if we use #xs #md (or whatever with #) for the data attribute, the queryAllSelector does not get them...
Maybe is what you referred for "preset" support?

In deed, I don't know how it is working using for example: (data-lax-scale#s="0 1, vh 1") because the queryAllSelector is over a set of:
"[data-lax-opacity],[data-lax-translate],......,[data-lax-preset]" selectors....
Are you telling me that you can add whatever after an # (anchor symbol) in a data attribute, and the selector still works? 😮 that is new for me...

Hm, yes not sure how it works haha 🤔- need to find some docs on it. Just in case I should probably change the querySelectorAll to be more like data-lax-opacity*
I haven't added support for data-lax-preset#xs yet.

https://stackoverflow.com/questions/25897910/valid-characters-in-custom-data-attribute-name-in-html5
Could change to "_" to be on the safe side e.g. data-lax-scale_s="0 1, vh 1

https://stackoverflow.com/questions/25897910/valid-characters-in-custom-data-attribute-name-in-html5
Could change to "_" to be on the safe side e.g. data-lax-scale_s="0 1, vh 1

You are right, but "_" it's a bit uglier, maybe you could use ":", more prettier and seems allowed: data-lax-scale:sx="0 1, vh 1"

According to this comment: https://stackoverflow.com/questions/25897910/valid-characters-in-custom-data-attribute-name-in-html5#comment40534319_25898182 (that references to this image http://www.asciitable.com/index/asciifull.gif) you are right (and its prettier) using "#" character, because is Dec 35, so its between Dec 32 - Dec 126.

Hm, yes not sure how it works haha 🤔- need to find some docs on it. Just in case I should probably change the querySelectorAll to be more like data-lax-opacity*
I haven't added support for data-lax-preset#xs yet.

Maybe should be easy to just force user to use a class "lax" so you could easily  queryAll elements, its a bit less "direct to use" but I think people is used to use a "class" for such a things (all libraries forces to use a class typicaly with the name of the library)... and it's better for performance I think....

Yes, I think that's a good idea.
Also realised that el.setAttribute("name#3", 1) throws an error:
VM1307:1 Uncaught DOMException: Failed to execute 'setAttribute' on 'Element': 'x#2' is not a valid attribute name.

It's ok if I use :

Just pushed some fixes. Should now be able to do:

Ok I was doing some changes to improve the code, I did a pull request so you could review it

According to the same stackoverflow comments, somebody warned about to use ":" as a separator, regarding issues with "namespaces", and he seems right because my webeditor complains about that: https://i.snag.gy/3JZ0tL.jpg So I pushed a '#' version for breakpoints to the responsive branch so the webeditor doesnt complains and it seems to work fine

I think we should avoid "#" as that causes the error 'name#3' is not a valid attribute name - do we have an alternative?

yeah I saw... let me check
Alejandro Fanjul
@alejandrofanjul
<EMAIL_ADDRESS>
El 22 mar 2019, a las 14:24, Alex Fox<EMAIL_ADDRESS>escribió:
I think we should avoid "#" as that causes the error 'name#3' is not a valid attribute name - do we have an alternative?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

Hi Alex, I added a "breakpointsSeparator" option to allow users specify their prefered character, and after trying many characters with the w3c validator (https://validator.w3.org/nu/#textarea) I only could manage the "." and "" as valid ones... but I think both are a bit ugly, because "." it's used for "properties" in objects and "" its mainly use for separate "multiple terms words", so if you use "data-lax-preset_sx" it looks like  more like "data lax preset_sx" than "data-lax-preset sx"... so I ended using "--" as the separator "character"...an it looks a bit prettier at least... "data-lax-preset--xs" or "data-lax-translate-x--lg"
Finally I fixed some issues in code regarding the "find presets" loop...
both changes are in the commit: https://github.com/alexfoxy/laxxx/commit/9589627ed7dd549bf97602826d35fb7946f3ee14
Should be awesome to allow specify "easing" for transform, either as string "easeIn" or a beizer curve function "cubic-bezier(0.445, 0.050, 0.550, 0.950)".
Animista has very cool timing functions: http://animista.net/

Should be awesome to allow specify "easing" for transform, either as string "easeIn" or a beizer curve function "cubic-bezier(0.445, 0.050, 0.550, 0.950)".
Animista has very cool timing functions: http://animista.net/

Sorry I was thinking in css animations, so for javascript maybe is not that easy ...

I merged in your changes, though I am going to make the syntax use "_" because I want to split on a single character, let's not worry too much about how it looks. Also I want to remove the ability for people to customise it, I think it's a bit unnecessary.

Perfect !
 Also I want to remove the ability for people to customise it, I think it's a bit unnecessary.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

pushed my changes

Merged our changes and released in 1.2.0


Format

Running scalafmt on the code base.
@DanSimon @aliyakamercan @jlbelmonte @amotamed

Codecov Report

Merging #650 into develop will increase coverage by 0.02%.
The diff coverage is 90.47%.

@@            Coverage Diff             @@
##           develop    #650      +/-   ##
==========================================
+ Coverage    85.58%   85.6%   +0.02%
==========================================
  Files          105     105
  Lines         4510    4510
  Branches       408     408
==========================================
+ Hits          3860    3861       +1
+ Misses         650     649       -1

Impacted Files
Coverage Δ

...protocols/http/streaming/StreamingHttpClient.scala
92.85% <ø> (ø)
:arrow_up:

.../main/scala/colossus/metrics/senders/package.scala
0% <ø> (ø)
:arrow_up:

...s/src/main/scala/colossus/service/ServiceDSL.scala
81.13% <ø> (ø)
:arrow_up:

...rotocols/http/streaming/StreamingHttpMessage.scala
100% <ø> (ø)
:arrow_up:

.../main/scala/colossus/protocols/redis/package.scala
100% <ø> (ø)
:arrow_up:

...in/scala/colossus/protocols/http/HttpRequest.scala
92.06% <ø> (ø)
:arrow_up:

...colossus/protocols/http/streaming/HttpStream.scala
90.47% <ø> (ø)
:arrow_up:

...ain/scala/colossus/util/compress/ZCompressor.scala
100% <ø> (ø)
:arrow_up:

.../scala/colossus/metrics/collectors/Histogram.scala
90.57% <ø> (ø)
:arrow_up:

...s/src/main/scala/colossus/core/WorkerManager.scala
86.45% <ø> (ø)
:arrow_up:

... and 12 more

Continue to review full report at Codecov.

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


Concurrent bootstrap attempts can fail

Steps to Reproduce
Running multiple rye (sync in particular, but likely any command which uses an interpreter) processes concurrently, some of the processes can fail with:
$ rye sync --no-lock
Bootstrapping rye internals
Downloading<EMAIL_ADDRESS>Checking checksum
Unpacking
error: could not sync because bootstrap failed

Caused by:
    0: failed to fetch internal cpython toolchain<EMAIL_ADDRESS>    1: unpacking of downloaded tarball https://github.com/indygreg/python-build-standalone/releases/download/20240224/cpython-3.12.2%2B20240224-x86_64-unknown-linux-gnu-pgo%2Blto-full.tar.zst to<EMAIL_ADDRESS>failed
    2: failed to unpack `python/build/Modules/Setup` into<EMAIL_ADDRESS>    3: File exists (os error 17)

...while the others succeed.
Expected Result
Unpacked artifacts should be moved to their final location atomically.
Actual Result
See above.
Version Info
$ rye --version
rye 0.31.0
commit: 0.31.0 (72e239b8f 2024-03-22)
platform: linux (x86_64)
self-python<EMAIL_ADDRESS>symlink support: true
uv enabled: true

Stacktrace
No response

I think that this can also exhibit as:
Bootstrapping rye internals
Found a compatible Python version<EMAIL_ADDRESS>  × Querying Python at
  │<EMAIL_ADDRESS>failed with
  │ status exit status: 1 with exit status: 1
  │ --- stdout:

  │ --- stderr:
  │ 'import warnings' failed; traceback:
  │ ModuleNotFoundError: No module named 'warnings'
  │ Could not import runpy module
  │ Traceback (most recent call last):
  │   File "<frozen runpy>", line 14, in <module>
  │   File
  │<EMAIL_ADDRESS>  │ line 57, in <module>
  │     import warnings
  │ ModuleNotFoundError: No module named 'warnings'
  │ ---
error: error bootstrapping venv

Caused by:
    Failed to create self venv using<EMAIL_ADDRESS>uv exited with status: exit status: 1

...perhaps if a Python install was partially extracted when another run tried to use it?


Make gas objects in shared bench not run out of gas

Since we reuse the gas objects in shared bench, we start running out of gas in long running benchmarks

Thanks @huitseeker


Docs: Fix misleading naming error on CMS_PERMISSION(S)

@mkoistinen would you merge this on support than I'll forward port to develop?

Merged into support, will port to develop when forward porting support


Suppress warning 'export xxx was not found in xxx'

Fix issue to due compiled TypeScript leaving empty exports. #6855
@williaster @mistercrunch

Codecov Report

Merging #6871 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #6871   +/-   ##
=======================================
  Coverage   56.31%   56.31%
=======================================
  Files         527      527
  Lines       23529    23529
  Branches     2782     2782
=======================================
  Hits        13251    13251
  Misses       9866     9866
  Partials      412      412

Continue to review full report at Codecov.

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

Codecov Report

Merging #6871 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master    #6871   +/-   ##
=======================================
  Coverage   56.31%   56.31%
=======================================
  Files         527      527
  Lines       23529    23529
  Branches     2782     2782
=======================================
  Hits        13251    13251
  Misses       9866     9866
  Partials      412      412

Continue to review full report at Codecov.

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

Close in favor of #6894


aquired is a misspelling of acquired

Signed-off-by: wgliang<EMAIL_ADDRESS>

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Thanks for your submission @wgliang :+1:


Drivers pods are in PENDING state because of insufficient CPU even though enough CPU is available.

Since installing the latest helm chart (with webhook enabled) all spark applications' have this issue.
The requirement is set to 1 core, and I tried using 4 and even 8 core machines for the underlying node, still the same.
I can schedule other non-spark applications on those nodes just fine.

not an issue, my mistake


⚠ Bofrost.de has degraded performance

In 1b2c182, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 950 ms

Resolved: Bofrost.de performance has improved in 5688f53.


[REVIEW] Please review my resume 🤓

Remove all personal data, otherwise the resume will be deleted.
Resume link: SS Resume.pdf
You can also join the discord community here
Feel free to check out other cool repositories of EddieHub Community here

The resume looks great, everything is well organized and it's a one page resume. one thing I would suggest is to add some color to it, maybe change the color of skills or headings. it will make the resume a bit more attractive.

Thank you @Prince-Shaikh 👍🏻 I'll see what I can do

@schmelto Thank you for the review. Can you please clarify which line are you talking about? 🤔

sure

Those lines under the headings. I personally prefer if there is a little bit space between end of document.

Hey - I've updated the resume. I'll be more than happy to see what you think about the new version 🤩

Like it!

Thank you for sharing, we will review on a live stream soon 👍 It looks like you are getting great community feedback already 💥

Reviewed on live stream https://www.youtube.com/watch?v=8SmgE7X9yHg
Looks awesome, very clean and concise, I don't have many suggestions

could maybe use colours a bit for the skill badges and type (could they be grouped)


Replace PromiseKit with native Swift Concurrency

Remove Promises Dependency and replace with Swift Concurrency

I am still learning open source practices, as such was committing extra changes against this will reopen one with fewer commits/changes


Concourse container explosions

We're having concourse issues. @jmcarp could you fill this out a bit more?

Starting last Thursday, when govcloud concourse auto-upgraded to 1.4.0, cpu usage jumped to 100% on the corresponding rds instance, making concourse unusable. Upgrading to concourse 1.4.1 had no discernible effect. Resizing the rds instance from m3.medium to m3.xlarge brought cpu usage back to an acceptable level.
I'm still not sure why the upgrade (apparently) spiked cpu usage, and I'm not sure why we haven't seen the same thing go wrong on east/west. But since resizing the rds instance resolved the immediate issue, I think we can call this done.


maven code generators cannot be used in sbt 1.3.x with coursier

Follow-up of https://github.com/thesamet/sbt-protoc/issues/64
https://github.com/sbt/sbt/issues/5132 causes https://github.com/thesamet/sbt-protoc/commit/1eab9ba71b3d55ec395be8ab9235f23979f7417d#diff-608890ca313eef1990a1b4bb7bb3d467R259-R260 to return false, so the plugin protoc argument is not populated.
Workaround is to disable coursier via useCoursier := false
Opening here just for visibility on the problem and the workaround, I don't think it's worth fixing/hacking something in this project.

Fixed in coursier https://github.com/coursier/coursier/issues/1391. Now waiting for a release of that to be shipped in sbt 1.3.x.

Fixed as of sbt 1.3.4


Monkey-patch on('exit') so that we always get it

Make sure that outputCoverage is always run at the end of the exit
handlers, even if that means it gets run multiple times.
Otherwise, a user-added on('exit') handler won't get coverage.
Note: this brings test coverage of node-tap's lib/root.js up to 94.44 where it belongs ;)

Coverage decreased (-5.43%) to 93.58% when pulling ac706a72226e7d6ceb8b2d6037acedac5f8f2270 on isaacs:on-exit-monkey into 812260d761061578a72e37b24740bbde9fe6f32f on bcoe:master.

This needs a test, clearly.

@isaacs sorry about that! addressed in https://github.com/bcoe/nyc/pull/10


fix: Sort non-variable routes before variable ones, to prioritize them.

Now matches foo/new.vue before foo/_id.vue consistently.

@ktsn Thanks for the prompt review! Pushed some tweaks for your style/readability feedback.

@petejohanson
Hi! Do you have a motivation to finish this PR still? If don't, I can take over. 🙂

Please feel free to take over. I've been too busy recently to return to this.
Thanks for checking in!

I've implemented remaining thing on #5 and just released v0.2.2 which includes the fixes.
Thanks for your initial work!

Looks great! Thanks!


Propagate navigation events + add enableInternalRouting config

Just like with other events the new navigation event must be reemitted in Shell.component.wc.vue
Even with this fix and setting enableInternalRouting I don't seem to receive navigation events because here it won't reach event emitting because we don't have $route in the web component:
https://github.com/describo/crate-builder-component/blob/0c26c555fc542bd9c368cc0bd7bd479f4b33493b/src/crate-builder/Shell.component.vue#L193

Sorry about this. I forgot about mapping the changes through the web component!


the error of "call() got an unexpected keyword argument 'training'",when convert to tflite

when convert to tflite,the error of "call() got an unexpected keyword argument 'training'" appear,how to resolve it?
import tensorflow as tf
import keras
from keras.layers import BatchNormalization,  ReLU
from keras.backend import pool2d
from utils import focal_loss
modelpath = r'./model/c3ae_model_v2.h5'
model = keras.models.load_model(modelpath, custom_objects={"pool2d": pool2d, "ReLU": ReLU,
"BatchNormalization": BatchNormalization, "tf": tf, "focal_loss_fixed": focal_loss([1] * 12)})
converter = tf.lite.TFLiteConverter.from_keras_model(model)
tflite_model = converter.convert()
savepath = r'./model.tflite'
open(savepath, "wb").write(tflite_model)
the  above is the code I used,how to resolve this error?

keras not test yet! you should use tf. keras,  which tf=2.1


"releases list" fails with undefined function

PHP 8.1.2 (cli)
php carbuncle.php releases list fails with call to undefined function.
PHP Fatal error:  Uncaught Error: Call to undefined function Realitaetsverlust\Carbuncle\curl_init() in /home/sergio/Carbuncle/Classes/Api.class.php:75
Stack trace:
#0 /home/sergio/Carbuncle/Classes/Api.class.php(41): Realitaetsverlust\Carbuncle\Api::fetchDataFromApi()
#1 /home/sergio/Carbuncle/Commands/ReleasesManager.php(14): Realitaetsverlust\Carbuncle\Api::fetchData()
#2 /home/sergio/Carbuncle/Carbuncle.php(46): Realitaetsverlust\Carbuncle\ReleasesManager->exec()
#3 /home/sergio/Carbuncle/Carbuncle.php(12): Realitaetsverlust\Carbuncle\Carbuncle->parseCommand()
#4 /home/sergio/Carbuncle/carbuncle.php(23): Realitaetsverlust\Carbuncle\Carbuncle->__construct()
#5 {main}
  thrown in /home/sergio/Carbuncle/Classes/Api.class.php on line 75

Fatal error: Uncaught Error: Call to undefined function Realitaetsverlust\Carbuncle\curl_init() in /home/sergio/Carbuncle/Classes/Api.class.php:75
Stack trace:
#0 /home/sergio/Carbuncle/Classes/Api.class.php(41): Realitaetsverlust\Carbuncle\Api::fetchDataFromApi()
#1 /home/sergio/Carbuncle/Commands/ReleasesManager.php(14): Realitaetsverlust\Carbuncle\Api::fetchData()
#2 /home/sergio/Carbuncle/Carbuncle.php(46): Realitaetsverlust\Carbuncle\ReleasesManager->exec()
#3 /home/sergio/Carbuncle/Carbuncle.php(12): Realitaetsverlust\Carbuncle\Carbuncle->parseCommand()
#4 /home/sergio/Carbuncle/carbuncle.php(23): Realitaetsverlust\Carbuncle\Carbuncle->__construct()
#5 {main}
  thrown in /home/sergio/Carbuncle/Classes/Api.class.php on line 75

Hi @SSUPII
to me, this looks like the cURL-module is missing in your installation. Could you please execute php -m | grep "curl" and check if there is any output?

Hi @SSUPII
to me, this looks like the cURL-module is missing in your PHP-installation. Could you please execute php -m | grep "curl" and check if there is any output?
I honestly assumed that the cURL-Extension is distributed by default on almost every distro, but I have updated the README to include all necessary modules.

Not in Debian at least. In fact, php -m | grep "curl" has no output.
Simply installing php-curl from apt seems to have resolved this issue.

Quite interesting, I'm always fascinated how basic modules are missing in certain distros. But as mentioned, I added it to the README to avoid any confusion in the future.
Glad I could help, and please, if you have any suggestions or bugs, feel free to report them. :)


Be able to change icon in the menuBar

The menu bar has an icon with dots already, it would be really cool to be able to choose to see the last week/month with like green/white dots. Also be able to change the icon to the OctoCat would also be cool since its a GitHub feature (for now?). 😄
The icon could maybe take up more space also based on how long you want to preview - 1week, 1month, 3months etc.

Thanks a lot for the feature request! 😊 I agree those sound like good features to implement. I will try to get on it some time this week. I'll tag you when I have something working!


Smoothing skeleton jitter not working!

Thanks for your amazing project.
Smoothing from neighbor repository is not working in this demo.
I had tried this code. Still no luck!

Hi! What are you want to achieve? As you see, that code works in the neighbor repository. So did not get your problem.

I want to smooth skeletons in this repository for 2d pose.

Does smoothing work for you in the neighbor repository? If it works there, looks like you have missed something in your implementation. You can print out keypoints coordinates before and after smoothing to check what is going on.

Hope, it is clear now.


[WIP] Cleanup move semantics in low level functions/classes and fixup beta-binomial-lpmf

Summary
I was trying to figure some of the internals (vectorbuilder and *_seq_view and in the process refactored the beta-binomial lpdf. It had a bunch of if statements in loops so the code should be a bit cleaner and a teeny bit faster.
I also added "const correct" accessors for vectorbuilder, it's helpers, and scalar_seq_view. scalar_seq_view now also has a perfect forwarding constructor
Tests
This is a refactor so I don't expect any new tests.
Checklist

[x] Math issue #1308

[x] Copyright holder: Steve Bronder

[x] the basic tests are passing

unit tests pass (to run, use: ./runTests.py test/unit)
header checks pass, (make test-headers)
docs build, (make doxygen)
code passes the built in C++ standards checks (make cpplint)

[x] the code is written in idiomatic C++ and changes are documented in the doxygen

[x] the new changes are tested

why is the beta-binomial pdf cleanup in a single PR with the heavy meta-munging cleanup? Not sure I see the relation here...

tbh no relation. I was going through beta_binomial just to work out some stuff. They are both p small though so I figured it might be fine to just include them on one PR. If that's confusing / weird I can break them up

Alrighty so I get what's going on here / causing it to break. I'm going to separate this into a few smaller PRs


Add DGCNN

Description

Add model DGCNN
Checklist
Please feel free to remove inapplicable items for your PR.

[ ] The PR title starts with [$CATEGORY] (such as [NN], [Model], [Doc], [Feature]])
[ ] Changes are complete (i.e. I finished coding on this PR)
[ ] All changes have test coverage
[ ] Code is well-documented
[ ] To the best of my knowledge, examples are either not affected by this change,
or have been fixed to be compatible with this change
[ ] Related issue is referred in this PR

Changes

https://github.com/pyg-team/pytorch_geometric/blob/master/test/nn/conv/test_edge_conv.py


Loop confirmation target interaction should warn of action consequences

Related with #165.
When defining the confirmation target for the sweep transaction, the relation between the target and the cap it sets for the on-chain fee is unclear. This can lead a new user to try a large target (400, fx.), receiving an on-chain transaction that has a fee too low to confirm, and, if uncapable of doing a CPFP transaction, losing their funds. That risk should be clearer.
In my view, the ideal solution would be for the user to define a fee cap instead of a confirmation target, making the risk explicit in the choice.
A lower effort solution would be to replace the tooltip text from:
The number of blocks to target for confirmation of the on-chain swap transaction.
Specify a larger number to reduce fees.

To something like:
The number of blocks to target for confirmation of the on-chain swap transaction.
Larger numbers will reduce fees, but if the transaction doesn't confirm you could lose your funds.

Even if you specify a very large conf target it will ignore the low fee target at the end of the timer to avoid trusting the server not to take the on-chain funds

I think I misunderstood the loop mechanism (my knowledge is limited to this article).
So what you're saying is that if the on-chain transaction never confirms and is dropped from the mempool, or the target is reached, there's no sweep transaction, the preimage is never revealed and the swap just fails?

I'm saying that at the end of the specified confirmation target that target will be ignored to use RBF to more rapidly increase the sweep fee to get a confirmation during the time when there is no possibility that the server could take the funds
RBF is also used continuously to keep the sweep fee related to the confirmation target setting and the transaction in the mempool

Ah, ok! A lot of misunderstanding on my part. No merit in this issue then. I'll close it.
Thank you for the explanation.


Add start_spoof and stop_spoof cheatcodes

Closes #1806
Related cairo-protostar compiler PR: https://github.com/MaksymilianDemitraszek/cairo-protostar/pull/3
Checklist

[x] Relevant issue is linked
[ ] Docs updated/issue for docs created
[x] Added relevant tests

@karol-bisztyga I added info about spoof cheatcodes to the linked issue.


Throw exception if route does not exist

Check if route for given HTTP verb does exist. Otherwise throw an exception.
https://github.com/timtegeler/routerunner/blob/d6c7fc43781ab9a43fa1ba29f65b061e9731e693/src/Components/Dispatcher.php#L54
Behavior at the moment: Controller can not be found.
https://github.com/timtegeler/routerunner/blob/d6c7fc43781ab9a43fa1ba29f65b061e9731e693/src/Components/Dispatcher.php#L94

That was actually an error in my code and not Routerunner's fault. :nerd_face:


ENH: _res support for initialization from a tuple of size 2

https://github.com/opendatacube/odc-geo/blob/159ae64a973f322736b56633701647388ccffdf7/odc/geo/types.py#L279
Currently get this error: ValueError: Unsupported input type: res_(x: <class 'tuple'>)

that's by design. thinking here is that order of resolution within a tuple is ambiguous, is it x,y is it y,x, you are supposed to use resyx_/resxy_ instead.

Within datacube code itself resolution was mostly supplied in y,x order, but I can not 100% confirm that. So maybe it's worthwhile having a separate "datacube compatibility" version of that function, but behavior of res_ itself won't change from the current one.

Sounds good, thanks :+1:


Crash: First(Accounts).Tasks causes exception

First(Accounts).Tasks
System.NotSupportedException: Specified method is not supported.
at Microsoft.PowerFx.Core.IR.IRTranslator.IRTranslatorVisitor.Visit(DottedNameNode node, IRTranslatorContext context)
at Microsoft.PowerFx.Syntax.DottedNameNode.Accept[TResult,TContext](TexlFunctionalVisitor`2 visitor, TContext context)
at Microsoft.PowerFx.Core.IR.IRTranslator.Translate(TexlBinding binding)
at Microsoft.PowerFx.CheckResult.ApplyIR()
at Microsoft.PowerFx.CheckResultExtensions.GetEvaluator(CheckResult result, StackDepthCounter stackMarker)
at FxPlayground.Core.Session.TryEvalAsync(String expression, UserInfo user, CancellationToken cancel) in D:\dev\pa2\PowerFxPlayground\src\FxPlaygroundCore\Session.cs:line 519
Like from here, because Account.Tasks is a relationship and that's not supported.
https://github.com/microsoft/Power-Fx/blob/bbeb145263301f5caa8f21ece945401e456605f8/src/libraries/Microsoft.PowerFx.Core/IR/IRTranslator.cs#L609
Likely because Accounts.Tasks is a 1:N relationship

Could pretty easily just remove that check and treat it like a field access. The backing RecordValue can handle that it's a relationship, the IR doesn't need to.


Check for option value before using NoOptDefVal

Relates to https://github.com/spf13/pflag/issues/134
Fixes inconsistent behavior when using NoOptDefVal.

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.

Reason for closing: https://github.com/spf13/pflag/issues/134#issuecomment-321541601


Updated: super-productivity 2.13.3

Newer version of super-productivity (2.13.6) is now available in master.


local: return error if write to tikv returns no leader info

What problem does this PR solve?

return an error if write to tikv finished with no leader info returned
fix an error if write and ingest all retry failed will just treat it as success

What is changed and how it works?
Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Side effects
Related changes

LGTM


incorrect dependency details for rust projects

For example, here is the latest scan from my rsPhate repo:
                             Dependency Scan Results (rust)
╔══════════════════════╤═════════╤════════════╤═════════╤════════════╤══════════╤═══════╗
║ Id                   │ Package │ Used?      │ Version │ Fix        │ Severity │ Score ║
║                      │         │            │         │ Version    │          │       ║
╟──────────────────────┼─────────┼────────────┼─────────┼────────────┼──────────┼───────╢
║ CVE-2020-25576       │ rand    │ N/A        │ <0.4.2  │ 0.4.2      │ CRITICAL │   9.8 ║
║ CVE-2020-7465        │ mpd     │ N/A        │ <5.9    │ 5.9        │ CRITICAL │   9.8 ║
║ CVE-2020-7466        │ mpd     │ N/A        │ <5.9    │ 5.9        │ HIGH     │   7.5 ║
║ CVE-2017-16138       │ mime    │ N/A        │ <1.4.1  │ 1.4.1      │ HIGH     │   7.5 ║
╚══════════════════════╧═════════╧════════════╧═════════╧════════════╧══════════╧═══════╝

The latest version of the mpd crate is 0.0.12, so I'm not exactly sure where 5.9 is coming from.
And it thinks that my rand version is less than 0.4.2, when it's actually 0.7.3.

This is unrelated, but all scans fail do to being unable to upload the report:
Error: No SARIF files found to upload in "reports".
Error: No SARIF files found to upload in "reports".
    at Object.upload (/home/runner/work/_actions/github/codeql-action/v1/lib/upload-lib.js:82:19)
    at run (/home/runner/work/_actions/github/codeql-action/v1/lib/upload-sarif-action.js:29:46)

Hi @Phate6660
Thank you for reporting the issue. On checking Cargo.lock I can see the vulnerable version of rand mentioned here - https://github.com/Phate6660/rsPhate/blob/master/Cargo.lock#L1212 . Have to read up on Cargo lock files to find which version would get used if multiple entries are present. Will you be able to point in the right direction here?
mpd and mime findings are false positive. Scan uses dep-scan which uses NVD as a data source. Both mpd and mime has the group with suffix _project. Eg: mpd_project. In case of CVE-2020-25576 rand_project turned out to be the group name for a legitimate crate package. However, clearly this suffix is creating FP in case of mpd and mime.
What I can do is for rust projects try to use rust advisory-db as a datasource instead of NVD. The change should happen here - https://github.com/AppThreat/vulnerability-db/tree/master/vdb/lib . Will you be able to contribute a PR?
Regarding upload action failures, the codeql upload step that is mentioned in the workflow is refusing to work without any SARIF files. I added some logic to create an empty sarif file here - https://github.com/ShiftLeftSecurity/sast-scan/blob/master/scan#L580 . Looks like it has be extended to cover languages such as rust for which scan doesn't have any sast tool available.
To summarize, there is quite a bit of work involved to support rust properly at this stage. Will keep this issue open and update with the progress made.

https://github.com/github/codeql-action/issues/282

Package rofl is indeed pulling the old version of rand here - https://github.com/Phate6660/rsPhate/blob/master/Cargo.lock#L1427

I can see that build failures due to missing sarif files is resolved now with the latest commit.

FYI, this is still failing due to the absence of reports for me: https://github.com/noclick-me/noclickd/pull/22/checks?check_run_id=1650729881

FYI, this is still failing due to the absence of reports for me: https://github.com/noclick-me/noclickd/pull/22/checks?check_run_id=1650729881

I can see what is going on. Fix coming shortly but might ask for your help to retest

I can see what is going on. Fix coming shortly but might ask for your help to retest

@llucax Can you rerun the github action workflow?

@llucax Can you rerun the github action workflow?

Sorry for the late reply, I did and it worked (as in the action didn't fail with an error). Thanks for the super fast reply!
On an unrelated note, I was trying this action thinking that it will report any found vulnerabilities in dependencies in GitHub's Security tab as the ones you receive with officially supported languages (like ruby), but I guess if the report that is uploaded to GitHub is empty, that won't happen?

Sorry for the late reply, I did and it worked (as in the action didn't fail with an error). Thanks for the super fast reply!
On an unrelated note, I was trying this action thinking that it will report any found vulnerabilities in dependencies in GitHub's Security tab as the ones you receive with officially supported languages (like ruby), but I guess if the report that is uploaded to GitHub is empty, that won't happen?

@llucax Glad it fixed the errors.
Depscan results are currently not integrated with GitHub code scanning. I wish GitHub would partner with us in opening the dependency scan results tab instead of keeping it locked to dependabot alone.
Some folks like anchore convert depscan findings to SARIF format to make it appear in code scanning. I'm not in favor of this workaround although this is kinda possible. The json reports produced by scan can be consumed to have any custom workflow. For eg: https://slscan.io/en/latest/integrations/github-actions/ here there is an upload artifact step to upload all reports. Some users have built custom scripts for notifications and uploading reports to s3 bucket and so on.
Hope this helps!

@llucax Glad it fixed the errors.
Depscan results are currently not integrated with GitHub code scanning. I wish GitHub would partner with us in opening the dependency scan results tab instead of keeping it locked to dependabot alone.
Some folks like anchore convert depscan findings to SARIF format to make it appear in code scanning. I'm not in favor of this workaround although this is kinda possible. The json reports produced by scan can be consumed to have any custom workflow. For eg: https://slscan.io/en/latest/integrations/github-actions/ here there is an upload artifact step to upload all reports. Some users have built custom scripts for notifications and uploading reports to s3 bucket and so on.
Hope this helps!


Small alteration to install and uninstall scripts

I have changed the returns to breaks which should fix #50
Please try and see if this has resolved the issue

Damn - should have been a second PR but I have fixed #51 as well by adding a parameter to the install of jobowner and a check for existence and a replacement in the install sql agent job sql file
Successful check for sa

Failed Check for Bill


DIfference between ^ and _ in normal mode?

They same to do the same thing, so was wondering if there's any difference. If there's no difference, maybe the key can be changed so by default one of them is more useful for something else? Or is there a reason for them to be the same?

the difference becomes apparent, once you use them in operator pending mode.
If you want to map them away, you are free to do so however.

@chrisbra If I map them, no one benefits. If you make different behaviors in vim, everyone benefits (people who really want old behavior can easily add the mapping).

Please don't use issues for discussions, the maillist is for that.


Schema cache cut out to simple component.

Q
A

Is bugfix?
no

New feature?
yes

Breaks BC?
no

Tests pass?
yes

Fixed issues

Schema cache cut out to simple component.
Now it can replace to custom implementation.
Backward compatibility is available (old implementations marked as deprecated).

Кэширование схемы таблиц перенесено в отдельный компонент.
Теперь появилась возможность задать свою реализацию кэширования.
Изменения не ломают обратную совместимость (старая реализация помечена как deprecated).

Can you explain why you need this and what a custom implementation would do?

We are use custom TagDepencency and extend Cache functions (include statistic and debug-panel), so we are need to cache schema via own components.
For example, we don't invalidate cache when tag is out of date - we only mark it as older.
But we can do it because Yii use hard code dependency for caching schema.
P.S.:
May be it's a old error, but only schema cache use cache key name as array - it's not needed strong.
This "feature" required additional support in code, which is not functional needed.

@zalatov tests are failing after these changes. Seems to be incomplete. Overall it may make sense to decouple it a bit more as you propose so logic is a bit simpler in each class.

Ok, I understood that I'll correct tests and commit changes.

Fix tests

I need to add row into CHANGELOG? Create new section with 2.1.0 under development?

not yet, we are going to review the changes for 2.1 and if we agree on a solution, you can add a changelog. otherwise it will likely cause unnecessary merge conflicts.

Update:
Backward compatibility is available (old implementations marked as deprecated).

Build still fails: https://travis-ci.org/yiisoft/yii2/builds/179311073

Won't make it into 2.0.


ALE won't parse kotlinc errors

Information
VIM version:
VIM - Vi IMproved 8.0 (2016 Sep 12, compiled Dec  5 2017 23:09:19)

Operating System:
Windows 10x64

:ALEInfo
 Current Filetype: kotlin
Available Linters: ['kotlinc', 'ktlint']
  Enabled Linters: ['kotlinc', 'ktlint']
 Linter Variables:

let g:ale_kotlin_kotlinc_classpath = ''
let g:ale_kotlin_kotlinc_config_file = '.ale_kotlinc_config'
let g:ale_kotlin_kotlinc_enable_config = 0
let g:ale_kotlin_kotlinc_module_filename = 'module.xml'
let g:ale_kotlin_kotlinc_options = ''
let g:ale_kotlin_kotlinc_sourcepath = ''
let g:ale_kotlin_kotlinc_use_module_file = 0
let g:ale_kotlin_ktlint_executable = 'ktlint'
let g:ale_kotlin_ktlint_format = 0
let g:ale_kotlin_ktlint_rulesets = []
 Global Variables:

let g:ale_echo_cursor = 1
let g:ale_echo_msg_error_str = 'Error'
let g:ale_echo_msg_format = '%code: %%s'
let g:ale_echo_msg_warning_str = 'Warning'
let g:ale_enabled = 1
let g:ale_fix_on_save = 0
let g:ale_fixers = {}
let g:ale_keep_list_window_open = 0
let g:ale_lint_delay = 200
let g:ale_lint_on_enter = 1
let g:ale_lint_on_save = 1
let g:ale_lint_on_text_changed = 'always'
let g:ale_linter_aliases = {}
let g:ale_linters = {}
let g:ale_open_list = 0
let g:ale_set_highlights = 1
let g:ale_set_loclist = 1
let g:ale_set_quickfix = 0
let g:ale_set_signs = 1
let g:ale_sign_column_always = 0
let g:ale_sign_error = '>>'
let g:ale_sign_offset = 1000000
let g:ale_sign_warning = '--'
let g:ale_statusline_format = ['%d error(s)', '%d warning(s)', 'OK']
let g:ale_warn_about_trailing_whitespace = 1
  Command History:

(executable check - success) kotlinc
(started) 'cmd /c kotlinc    [SNIP]/ProjectName/src/app.kt'
(executable check - failure) ktlint
(finished - exit code 1) 'cmd /c kotlinc    [SNIP]/ProjectName/src/app.kt'

<<<OUTPUT STARTS>>>
[SNIP]\ProjectName\src\app.kt:5:9: error: unresolved reference: sdsd
        sdsd
        ^
<<<OUTPUT ENDS>>>
(executable check - failure) ktlint

What went wrong
I've written an error into my Kotlin hello world app, trying to get ALE to show up. No error seems to be recognized or reported, despite showing up in the :ALEInfo output.
I'm running the latest version of ALE and the latest available version of GVIM off github.
Reproducing the bug
Steps for repeating the bug:
Where the file's contents is:
fun main(args: Array<String>) {
    asdasd
}

Open a .kt file: :e app.kt
Write an error into the file and save osdsdd<C-C>:w<CR>
No sidebar highlighting the line shows up and  :cc or :cc or :copen shows no errors,
:ALEInfo shows some content:

<<<OUTPUT STARTS>>>
[SNIP]\ProjectName\src\app.kt:5:9: error: unresolved reference: sdsd
        sdsd
        ^
<<<OUTPUT ENDS>>>

My :pwd was set to a different folder. Changing that to the root of my project resolved the issue and now the errors are showing up as intended.


[Fleet] UI mixes up Git Repo target types

Create a Git Repo using the form and select "Target Type -> No Clusters"

Notice that the repo overview page shows the "Target" for the created repo is showing "All" instead of "None".

Choose "Edit as Form" for that repo and notice that in the "Target Type" dropdown the active item is set to "All clusters in the workspace"

Modify the Git Repo just by adding a label then click "Save"
Notice that the Git Repo is now being applied to all clusters instead of none.

Rancher 2.5.1

Reproduced in Rancher version v2.5.1

Rancher version master-head (11/02/2020) 6d4d6b0
Validated the fix. When selected None it stays as None selected.
Editing or creating with other Target types are also working.


[WIP] implement basic rate limiting

Addresses #31
This uses rocket-governor to implement rate limiting.

I fail to see the benefits of doing rate limiting in the app, instead of at the load-balancer/proxy level. Do you think it would be beneficial to have both?

@sbihel I agree more or less (that rate limiting could simply be achieved by putting a load balancer or etc in front) -- this is definitely something up for discussion. The way it's filed @wyc did seem to want rate limiting as an option in the rocket app itself.
If we decide this is not needed I can close this PR, but it doesn't seem difficult to add if needed.

Will close this but keep it in mind as an option. Will rephrase the issue.


Show the actual table size in the TableSize view

Hi,
here is the snipped of the code, which I tested locally, which will add more information to the TableSize, especially the actual tables sizes.

from django.utils.translation import ugettext_lazy as _
from postgres_metrics.metrics import Metric, registry

class DetailedTableSize(Metric):
    """
    Table size per table

    - total_size: table size + indexes \n
    - table_size: table size \n

    """

    header_labels = [
        _("Table"),
        _("total_size_MB"),
        _("table_size"),
        _("relation_size_main"),
        _("relation_size_fsm"),
        _("relation_size_vm"),
        _("relation_size_init"),
    ]
    label = _("Detailed Table Size")
    ordering = "-2"
    slugify = "detailed-table-size"
    sql = """
        SELECT
            relname,
            pg_total_relation_size(relid)::float / 1024.0 / 1024.0,
            pg_size_pretty(pg_table_size(relid)) as table_size,
            pg_size_pretty(pg_relation_size(relid, 'main')) as relation_size_main,
            pg_size_pretty(pg_relation_size(relid, 'fsm')) as relation_size_fsm,
            pg_size_pretty(pg_relation_size(relid, 'vm')) as relation_size_vm,
            pg_size_pretty(pg_relation_size(relid, 'init')) as relation_size_init
        FROM
            pg_stat_user_tables
        {ORDER_BY}
        ;
    """

registry.register(DetailedTableSize)

You can find more explanation here: https://stackoverflow.com/questions/41991380/whats-the-difference-between-pg-table-size-pg-relation-size-pg-total-relatio
The second column is casted to MB:
 pg_total_relation_size(relid)::float / 1024.0 / 1024.0,

since it can be nicely sorted (disclaimer I'm not an SQL expert), but you will probably find a better fix sorting issue.

Thank you!

Thanks for the initial code. I merged two commits, one including the additional data and one changing the behavior of the sorting. Could you check out the main branch and see if this works for you? If it does I'll do a release.

Hi, cool ! I can confirm that everything works fine in my case. Thanks for quick feedback.

Wonderful! :confetti_ball: Please enjoy version 0.10.0 from PyPI


Bring numeric extension to core GIL

Earlier GIL was a simple Image manipulation library and then it made sense to keep numeric as an extension but as we are now moving forward with the inclusion of image processing algorithms and features such as histogram, the numeric extension is a complement to the image processing module and if image processing is implemented in core GIL then numeric should also be in the core IMO.

This is a good idea. By the way, we are also planning of moving whole or parts of the toolbox into core, see #75.

Shall we move everything in one go or feature by feature as required by our current activities (GSoc)?
Shall we introduce proxy headers in boost/gil/extension/numeric for some transition period, in case there are users of the numeric?

Shall we move everything in one go or feature by feature as required by our current activities (GSoc)?

IMO, it is not a huge task we can move it in one go, I'll work on it.(I'll try to complete my all pending promises too before next release :wink:)

Shall we introduce proxy headers in boost/gil/extension/numeric for some transition period, in case there are users of the numeric?

I would suggest that we should keep proxy header for a couple of releases, with throwing some warnings of deprecation of the header.

IMO, it is not a huge task we can move it in one go

I asked not worrying about the size of the task but about moving unnecessary things from an extension to core. Do we need all features of numeric in core?

I think we can deprecate:
affine.hpp, sampler.hpp, resample.hpp. If you go to sampler.hpp or resampler.hpp you'll know why I said that and affine.hpp is only used in those two headers.
Apart from that
channel_numeric_operations.hpp and pixel_numeric_operations.hpp can be useful many times into image processing algorithms it would make things simple in future. I am not aware if it is used anywhere into the core but it should be used.
and then there are kernel.hpp and convolve.hpp which is used in core so without any doubt, we should move them and it uses functions from algorithm.hpp so also move that. But the primary reason to move this header into the core is not because we use it in the core, but they are already some very useful image processing algorithms which we should have in core/image_processing

If you go to sampler.hpp or resampler.hpp you'll know why I said that and affine.hpp is only used in those two headers.

I don't mind deprecating those.
Those fit in the examples better indeed, which structure, by the day, could be cleaned up into folders, then example/resample/.
Thanks for clarifying my questions. No objections from me.

these resampling and affine examples also have tests. I am not sure what to do with them.
I typically don't like removing tests, more cases to test less the bug.
But if we more those headers in examples I am not sure if it is a good idea to use example headers in the tests.(and on the other hand it will add unnecessary complications in configuration)
looking for suggestions on what to do with those headers...

these resampling and affine examples also have tests. I am not sure what to do with them.
I typically don't like removing tests, more cases to test less the bug.
But if we more those headers in examples I am not sure if it is a good idea to use example headers in the tests.(and on the other hand it will add unnecessary complications in configuration)
looking for suggestions on what to do with those headers...
@mloskot @simmplecoder @sdebionne

these resampling and affine examples also have tests. I am not sure what to do with them.

How about keeping these example-like to-be-deprecated headers inside boost/gil/extension/numeric for now?
In other words

move the useful stuff from boost/gil/extension/numeric upward into boost/gil  core
keep the rest of the stuff inside boost/gil/extension/numeric
keep the current structure of tests and examples for the stuff from 2.

This would seem like the least disruptive approach giving us time for further refactoring.


Add a basic description of the project idea to the README.md

Key Questions to Answer with the Dataset
Descriptive Analysis:

What are the basic statistics (mean, median, standard deviation) of the clinical features?
How is the age distribution of patients?
What is the proportion of patients with conditions like anaemia, diabetes, and high blood pressure?

Correlation and Feature Importance:

Which clinical features are most strongly correlated with the DEATH_EVENT? And what are the most important features for predicting heart failure outcomes?
How do different clinical features contribute to the risk of death due to heart failure?

Predictive Analysis:

How accurately can we predict DEATH_EVENT using clinical features?
Which machine learning model performs best for this prediction task? (We can use DecisionTrees, RandomForest or other classifiers) Let us use scikit-learn
How do different models compare in terms of accuracy, precision, recall, and other metrics?

Survival Analysis:

What is the survival rate of patients over the follow-up period?
How do survival rates vary with different clinical features (e.g., age, ejection fraction)?
Can we identify patient subgroups with higher or lower survival probabilities?

Risk Factor Analysis:

How does smoking affect the risk of death in heart failure patients?
What is the impact of serum creatinine and serum sodium levels on patient outcomes?
How does the combination of multiple risk factors affect the likelihood of heart failure-related death?

If we want to work on this topic. I created a PR with the corresponding dataset: https://github.com/NoTopicYet-ResearchSE-SS24/NoTopicYet/pull/9


Remove never-encode-slash feature

and make the right behavior the default.
This was merged in #236, but never made it to a release and now it's gone again on develop too. I'm hoping that was just an accident.

I can update the tests if you decide you want this in again, but the whole situation is a bit unclear to me for now so I'll wait.

@jplatte thanks for the catch, an omission on my part


Show small popup when keys are registered and actions taken

Occasionally, I'm unsure if my keys had been registered by Saka Key for actions that do not have immediate feedback, such as closing or switching a tab or scrolling. Notably, actions involving the clipboard.
Additionally, for multi-key bindings it would be nice if the current key chord state (i.e. the registered buttons of the current chord) were displayed somewhere. Going further into this, the remaining options for the current chord could be displayed somewhere as well.
Here is a small example from ranger, a CUI file manager, after pressing y. The chord progress is shown at the top right (next to open tabs, window is very small here) and available options on the bottom.

Contextual help would be a nice add yep.

I implemented some sort of contextual help in a project to build modal interfaces.
@eejdoowad The data model of commands is not that far from yours, so I guess you can take the draw() function easily.


Accessing files from AWS: S3 buckets

I have a question with respect to accessing files from AWS: S3 buckets. Is it possible to access files from AWS: S3 buckets and checking for compliance from Netflix photon tool.
Any pointers I can think about?
Regards,
Ayyappan

Apparently OwnZones fork has this support.

Thanks for the updates. Will check this.

This code may be doing what you want: https://github.com/OwnZones/photon/commit/ca746a3cda840e8aa1f587b45773f6bb378bea7b


storage: spawn a background task to return deadline error

What problem does this PR solve?
It is important to respond to the client in time. Otherwise, the client is hard to distinguish a down TiKV from a busy TiKV. And lost response may cause more "undetermined errors" at the client.
Although we have added deadline checks at many places after latches are all acquired, there are still various possibilities for a command to stuck at the scheduler, such as blocked by the latch of another throttled command.
So this PR hopes to reduce the chance of client recv timeout as much as possible.
What is changed and how it works?
When scheduling a command, spawn a task that calls the callback of the command if it expires. An extra flag owned is added to make sure the callback is not called twice.
Related change: https://github.com/tikv/client-go/pull/271
Check List
Tests

Unit test
Integration test
Manual test (add detailed scripts or steps below)
No code

Side effects

Performance regression

Consumes more CPU
Consumes more MEM

Breaking backward compatibility

Release note
Respond with deadline error even if the command is waiting in the scheduler.

I wonder its performance impact.

It depends on how many conflicts there are. If all latches are acquired successfully at first, the background task is not started.
For conflicted scenarios, I test sysbench zipfian (exp=0.99) as an example:

The global timer increases about 0.4% CPU and spawning the background task increases 0.4% CPU.
The final QPS and latency impact is hardly noticeable.


BytesQueue allocateAdditionalMemory Questions

Hi, I have a question in BytesQueue part.
Why reset (q.head = leftMarginIndex, q.tail = q.rightMargin) in function allocateAdditionalMemory. Will it cause some entries live longer than lifeWindow during cache cleanUp when additional memory allocated?

@janisz @mxplusb 😉

My expertise is in the server implementation, this is definitely a @janisz question, lol.


command not found

I need help trying to figure why I am getting the "command not found" error when I try to do:
bundle exec middleman
This used to work, but I needed to reinstall bundler (probably after an OS upgrade) and since then it no longer works.
"bundle check" does not report any errors.
There is an executable script "middleman" in /Library/Ruby/Gems/2.0.0/gems/middleman-core-3.4.0/bin.
/Library/Ruby/Gems/2.0.0/gems/middleman-core-3.4.0 is one of the paths shown by bundle show --paths.
bundle -- version says: 1.15.4
By the way, I know nothing whatsoever about Ruby. I just want to use middleman!
Thank you.

Please share the output of bundle env

Environment
Bundler   1.15.4
Rubygems  <IP_ADDRESS>
Ruby      2.0.0p648 (2015-12-16 revision 53162) [universal.x86_64-darwin16]
Git       2.11.0 (Apple Git-81)
Platform  universal-darwin-16
OpenSSL   OpenSSL 0.9.8zc 19 Mar 2015

Gemfile
Gemfile
# If you do not have OpenSSL installed, update
# the following line to use "http://" instead
source 'https://rubygems.org'

gem "middleman", "~>3.4.0"

# Live-reloading plugin
gem "middleman-livereload", "~> 3.1.0"

# For faster file watcher updates on Windows:
gem "wdm", "~> 0.1.0", :platforms => [:mswin, :mingw]

# Windows does not come with time zone data
gem "tzinfo-data", platforms: [:mswin, :mingw, :jruby]

Gemfile.lock
GEM
  remote: https://rubygems.org/
  specs:
    activesupport (4.2.4)
      i18n (~> 0.7)
      json (~> 1.7, >= 1.7.7)
      minitest (~> 5.1)
      thread_safe (~> 0.3, >= 0.3.4)
      tzinfo (~> 1.1)
    capybara (2.4.4)
      mime-types (>= 1.16)
      nokogiri (>= 1.3.3)
      rack (>= 1.0.0)
      rack-test (>= 0.5.4)
      xpath (~> 2.0)
    chunky_png (1.3.4)
    coffee-script (2.4.1)
      coffee-script-source
      execjs
    coffee-script-source (<IP_ADDRESS>)
    compass (1.0.3)
      chunky_png (~> 1.2)
      compass-core (~> 1.0.2)
      compass-import-once (~> 1.0.5)
      rb-fsevent (>= 0.9.3)
      rb-inotify (>= 0.9)
      sass (>= 3.3.13, < 3.5)
    compass-core (1.0.3)
      multi_json (~> 1.0)
      sass (>= 3.3.0, < 3.5)
    compass-import-once (1.0.5)
      sass (>= 3.2, < 3.5)
    em-websocket (0.5.1)
      eventmachine (>= 0.12.9)
      http_parser.rb (~> 0.6.0)
    erubis (2.7.0)
    eventmachine (1.0.8)
    execjs (2.6.0)
    ffi (1.9.10)
    haml (4.0.7)
      tilt
    hike (1.2.3)
    hooks (0.4.1)
      uber (~> 0.0.14)
    http_parser.rb (0.6.0)
    i18n (0.7.0)
    json (1.8.3)
    kramdown (1.8.0)
    listen (3.0.3)
      rb-fsevent (>= 0.9.3)
      rb-inotify (>= 0.9)
    middleman (3.4.0)
      coffee-script (~> 2.2)
      compass (>= 1.0.0, < 2.0.0)
      compass-import-once (= 1.0.5)
      execjs (~> 2.0)
      haml (>= 4.0.5)
      kramdown (~> 1.2)
      middleman-core (= 3.4.0)
      middleman-sprockets (>= 3.1.2)
      sass (>= 3.4.0, < 4.0)
      uglifier (~> 2.5)
    middleman-core (3.4.0)
      activesupport (~> 4.1)
      bundler (~> 1.1)
      capybara (~> 2.4.4)
      erubis
      hooks (~> 0.3)
      i18n (~> 0.7.0)
      listen (~> 3.0.3)
      padrino-helpers (~> 0.12.3)
      rack (>= 1.4.5, < 2.0)
      thor (>= 0.15.2, < 2.0)
      tilt (~> 1.4.1, < 2.0)
    middleman-livereload (3.1.1)
      em-websocket (>= 0.2.0)
      middleman-core (>= 3.0.2)
      multi_json (~> 1.0)
      rack-livereload
    middleman-sprockets (3.4.2)
      middleman-core (>= 3.3)
      sprockets (~> 2.12.1)
      sprockets-helpers (~> 1.1.0)
      sprockets-sass (~> 1.3.0)
    mime-types (2.6.1)
    mini_portile (0.6.2)
    minitest (5.8.0)
    multi_json (1.11.2)
    nokogiri (<IP_ADDRESS>)
      mini_portile (~> 0.6.0)
    padrino-helpers (0.12.5)
      i18n (~> 0.6, >= 0.6.7)
      padrino-support (= 0.12.5)
      tilt (~> 1.4.1)
    padrino-support (0.12.5)
      activesupport (>= 3.1)
    rack (1.6.4)
    rack-livereload (0.3.16)
      rack
    rack-test (0.6.3)
      rack (>= 1.0)
    rb-fsevent (0.9.5)
    rb-inotify (0.9.5)
      ffi (>= 0.5.0)
    sass (3.4.18)
    sprockets (2.12.4)
      hike (~> 1.2)
      multi_json (~> 1.0)
      rack (~> 1.0)
      tilt (~> 1.1, != 1.3.0)
    sprockets-helpers (1.1.0)
      sprockets (~> 2.0)
    sprockets-sass (1.3.1)
      sprockets (~> 2.0)
      tilt (~> 1.1)
    thor (0.19.1)
    thread_safe (0.3.5)
    tilt (1.4.1)
    tzinfo (1.2.2)
      thread_safe (~> 0.1)
    uber (0.0.14)
    uglifier (2.7.2)
      execjs (>= 0.3.0)
      json (>= 1.8.0)
    xpath (2.0.0)
      nokogiri (~> 1.3)

PLATFORMS
  ruby

DEPENDENCIES
  middleman (~> 3.4.0)
  middleman-livereload (~> 3.1.0)
  tzinfo-data
  wdm (~> 0.1.0)

BUNDLED WITH
   1.10.6

This used to work, but I needed to reinstall bundler (probably after an OS upgrade) and since then it no longer works.

In what way does it not work?

"command not found"

@cbfiddle could you please paste the stacktrace you're getting?

Please share the full output of the command you're trying to run, otherwise it's hard to tell what's actually happening

Here is the command and the output:
$ bundle exec middleman
bundler: command not found: middleman
Install missing gem executables with `bundle install`

There is no stack trace.

did you run bundle install as suggested?

I had not done that, because bundle check said everything was fine.
So I have now run bundle install, and as expected, it also says the bundle is complete.
The problem remains.

can you run the following for me: ruby -rbundler/setup -e 'puts Gem.bin_path("middleman", "middleman"); puts ENV["PATH"] ?

$ ruby -rbundler/setup -e 'puts Gem.bin_path("middleman", "middleman"); puts ENV["PATH"]'
/Library/Ruby/Gems/2.0.0/gems/middleman-core-3.4.0/bin/middleman
/Library/Ruby/Gems/2.0.0/bin:/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin:/usr/local/ant/bin:/usr/local/mysql/bin:/Library/Java/JavaVirtualMachines/1.8.0.jdk/Contents/Home/bin:/Users/alan/bin:/SharedApplications/android-sdk-macosx/tools:/Library/Ruby/Gems/2.0.0

super weird, there should be a bin stub in /Library/Ruby/Gems/2.0.0/bin named middleman that loads Gem.bin_path("middleman", "middleman"), I'm not sure why it isn't

There is no directory "bin" in /Library/Ruby/Gems/2.0.0.
How do I fix this?

Hmmm.... I was reading through similar Middleman's issues, and came across this. This doesn't fix the crux of the problem, but possibly try gem install middleman, and then try bundle exec middleman as a work around.

I tried the following, because I do not want to change middleman versions:
$ sudo gem install middleman -v 3.4.0
Fetching: sprockets-3.7.1.gem (100%)
ERROR:  Error installing middleman:
	sprockets requires concurrent-ruby (~> 1.0)

ah, so turns out the middleman command is in the middleman-cli gem, so try gem install middleman-cli or gem pristine middleman-cli ?

I assume you mean middleman-core?
I did this:
sudo gem install middleman-core -v 3.4.0
and this:
sudo gem pristine middleman-core -v 3.4.0
There is still no /Library/Ruby/Gems/2.0.0/bin directory (there is a gems/middleman-core-3.4.0/bin), but the good news is that it now works!
Thank you for your help.

I have to admit I never understood how the above magic fixed my problem, and perhaps it didn't. The problem has reappeared, but with a twist:

If I run bundle exec middleman build from the terminal in my project directory, it works.
If I invoke bundle with the same arguments from a Java application running under the IDEA debugger (connected to the project directory), it works.
If I run the same Java application that has been packaged as an macOS application, it fails as above (middleman not found).

I modified the Java application to run bundle env after a failure, and it produces the same output as I get doing this from the terminal.
I then modified the Java application to run env after a failure, and I discovered that when run as a bundled app, the PATH is different. In particular, it does not contain /usr/local/bin, which is where the bundle program lives.
So, I changed the Java application to add /usr/local/bin to the PATH when running bundle, and it worked. I also tried running /usr/local/bin/bundle from the terminal without /usr/local/bin in the PATH, and it failed (the same way).
The upshot seems to be that bundle needs something, perhaps itself, to be in the PATH.
Is that a surprise? Seems like a bad idea to me.

I think there is a bug here because the behaviors of bundle exec and bundle env are inconsistent.
In my example, there are two values of PATH:

/usr/bin:/bin:/usr/sbin:/sbin
/usr/bin:/bin:/usr/sbin:/sbin:/usr/local/bin

There are also two versions of Ruby (this is macOS, which comes with a version of Ruby):

/usr/bin/ruby [2.0.0p648]
/usr/local/bin/ruby [2.4.1p111]

bundle exec apparently uses PATH to find Ruby and its database. It behaves differently given the two PATHs above.
bundle env apparently does not use PATH, because it produces the exact same output for the two PATHs.
One of them must be wrong.

Thanks for the hint. For me I actually see the bin under middleman-cli. So I added this to my PATH and it works now: /Library/Ruby/Gems/2.3.0/gems/middleman-cli-4.2.1/bin

This sounds like a ruby/rubygems installation / path issue to me


[OAP-COMMON] Fix link error

What changes were proposed in this pull request?
Fix link error
How was this patch tested?
Manully test

@winningsix


Update to new Dokku API for installing SSL certificates

@brambokdam I looked at this, but I can't really figure out what is new with their API?


Modal Service: Add support for dynamic component

Currently it seems the modal service does not support dynamic components as the modal component does. Dynamic components enable developers to add markup to the body.
For example, I would like to display key value pairs in a user friendly way.
N.B. I could not get the normal modal to work while nested deep in a component. Its logic seems to conflict with my Blazor Server application as the modal is visible but behind the transparent overlay, same as the rest of the page. So there is nothing left to interact with.

@gvreddy04
I second this. The Modal component already provides the ShowAsync call with a generic type  (the childComponent to render).
Adding a property for the ChildContent type in ModalOption (that gets passed to the ModalService) or making a generic ModalOption signature like ModalOption would provide more flexibility of the content type to render, other than rendering only string based content. Also this means we can use the ModalService with one Modal component instance placed at the top most position in the DOM tree preventing a) unnecessary Modal instances within the DOM tree and thus better performance and b) nesting Modal instances within the DOM tree with dynamic rendered parent components can lead to CSS problems (mentioned by OP)

I agree this would be great. At the moment the fact that it's considered a string rather than something like a HTML string doesn't make it as useful as it could be.


export offset using @Binding

Hi there, thanks for the lib!
As this view makes some work already to get scrollView offset, i'm wondering if you can expose offset value using @Binding or closure?
That would be super helpful for making parallax-like effects for headers etc.

Currently you can access the percentage (0 - 1) of of how far along the drag gesture is via RefreshState.dragPosition
You can access this struct by providing a custom refreshView - in the example it's implicitly passed to the default constructor. However you should be able to explicitly capture it with something like:
.refresher(refreshView: { $state in
    return DefaultRefreshView(state: $state)
        // Do something with state.dragPosition
        .onChange(of: state.dragPosition) { newPosition in
            print(newPosition)
        }
}) { ...

Or you can implement your own custom refresh view similar to the example that captures and uses the RefreshState struct.
Let me know if this works for your use case. If you need an explicit offset, I can add that as well - but you may be able to derive the offset you need from the dragPosition


redo forms for new frontend

[ ] new / edit project
[ ] new / edit dosed pk model
[ ] new / edit pd model

Use to automatically create forms for django serializers:

https://github.com/drf-forms/drf-schema-adapter
https://github.com/rjsf-team/react-jsonschema-form


TfLite support

Is there any model that can support tflite conversion?

sorry for the late reply. You can use the newest tensorflow version to convert all the models listed in Athena. If you encounter any problem, please let me know.

thx for the reply


Ensure that KC remembers the role you last used for a particular account

I didn't dismiss any reviews, I just mistakenly pushed a new commit to my main branch before this one was merged. I'm merging this as we already did a review of this PR and it has not changed


Support for selector: enabled and disabled

Implemented support for css selector using: disabled e: enabled

Added issue
#1407

(Closing old PRs; thanks for your interest and apologies for the late review. I don't plan to merge this as without a javascript runtime I don't think this is particularly useful; but if you believe there is still an issue, please leave a comment.)


example notebook using rslaser.pulse.LaserPulse

Added a new notebook SinglePass01-LaserPulse.ipynb which is the conversion of SinglePass01 using the rslaser.pulse.LaserPulse for calculations. Added uti_plot calls to verify plot orientation.

I agree that the file trimming should be removed.

This is working fine with prop_type = 'n0n2_srw'.
If you change it to 'n0n2_lct', then the LCT algorithm hangs.
I believe the best solution is to pad the data out to a 64 by 64 mesh.
I still agree that deleting rows or columns from the mesh is not the right thing to do.
@moellep -- please have a look at my changes and accept the PR if you approve.
@k-wolfinger -- in your active branch, please check whether your data padding algorithm will accommodate the WFS data files with no initial truncation of the mesh.


Fix typos ('proxyies' -> 'proxies') and broken bit.ly links (bit.ly/a…

…nMa4g is now a dead link; updated to bit.ly/1IZIRcY, which is the Internet Archive's most recent scrape of the dead link's target).

Thanks !

Integrated, thanks.

Awesome - thanks!


deno.land/x ?

Love it!
why is not publish in deno.land/x ?
I was lookinh for it for a long time!

+1

After fixing a few things the module is now findable on deno.land/x/question

🎉


Refactor the List and ListDir interface

Klaus - can you take a look at this please?
I've taken your original work and extended it.  I had to change the original concept a bit in order to get it to work in a race free way, but it seems to!
I've updates all the remotes and it is all working (except for 1 test which I'll fix).
If you have time I'd love to have your comments.
I rebased it (quite tricky!).  I squashed all the commits since there were lots and they were mostly noise of me changing my mind about various things.
Thanks
Nick

Gives more accurate error propagation, control of depth of recursion
and short circuit recursion where possible.
Most of the the heavy lifting is done in the "fs" package, making file
system implementations a bit simpler.
This commit contains some code originally by Klaus Post.
Fixes #316

I've merged this to master now :-)  It has been a long journey!


https option

Can we make it possible to use https instead of http. Perhaps with options: https, key and cert?
Greetings
Christian

Hi, I just release v1.7.0 which adds an https option.
Thanks for the suggestion.


Array offset error when using the Concurrency facade

Laravel Version
11.23.2
PHP Version
8.3.11
Database Driver & Version
SQLite
Description
The Concurrency facade returns a "Trying to access array offset on null" error, when attempting to use the run method. This error seems to be at $result['successful'] within the ProcessDriver class.
From some testing I've done myself it still seems that Laravel is unable to find the php binary from Herd, as (new PhpExecutableFinder)->find(false) returns false.
Steps To Reproduce
Create a route like the following:
Route::get('/concurrency', function () {
    [$test] = Concurrency::run([
        fn () => DB::table('users')->get(),
    ]);

    return response()->json([
        'test' => $test,
    ]);
});

Laravel will error out at the Concurrency::run line.

Hey @crynobone, seems the issue still exists when using Laravel Herd.
Latest Herd (just updated), Laravel 11.23.4, PHP 8.3.11

For future travelers, if you're using the latest version of Laravel, the issue isn't Herd. Trying using the fork driver as described here: https://laravel.com/docs/11.x/concurrency#how-it-works

For future travelers, if you're using the latest version of Laravel, the issue isn't Herd. Trying using the fork driver as described here: https://laravel.com/docs/11.x/concurrency#how-it-works

The problem is fork is only supported in CLI. Do we have a solution without using fork?

PR #52744 should fix this issue.

I still have this issue in Laravel 11.30.0

@misodrobny please submit new bug report with reproducing code instead of commenting on closed issue.


fix: set reputation change for already seen txs to 0

Closes #2933 #2451
from the spec:

Including hashes that the sending peer could reasonably be considered to know (due to the fact they were previously informed of because that node has itself advertised knowledge of the hashes through NewBlockHashes) is considered bad form, and may reduce the reputation of the sending node.

however, this seems to be a very common thing:
reth_network_messages_with_already_seen_transactions 1110                                                                 reth_network_propagated_transactions 10740
reth_network_reported_bad_transactions 21                                                                                reth_transaction_pool_basefee_pool_size_bytes 1791688
reth_transaction_pool_basefee_pool_transactions 10001                                                                     reth_transaction_pool_inserted_transactions 78536                                                                         reth_transaction_pool_invalid_transactions 4647
reth_transaction_pool_pending_pool_size_bytes 19784                                                                       reth_transaction_pool_pending_pool_transactions 42                                                                        reth_transaction_pool_queued_pool_size_bytes 2700965
reth_transaction_pool_queued_pool_transactions 9988
reth_transaction_pool_removed_transactions 7460

I suggest disabling this for now and investigate how other implementations handle this, because I assume this is not only spam

fyi @0xvanbeethoven

Codecov Report

Merging #2945 (ea133a5) into main (5dd49e4) will decrease coverage by 28.71%.
The diff coverage is n/a.

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@             Coverage Diff             @@
##             main    #2945       +/-   ##
===========================================
- Coverage   71.05%   42.35%   -28.71%
===========================================
  Files         517      517
  Lines       67056    67056
===========================================
- Hits        47645    28399    -19246
- Misses      19411    38657    +19246

Flag
Coverage Δ

integration-tests
17.29% <ø> (-0.01%)
:arrow_down:

unit-tests
34.65% <ø> (-31.32%)
:arrow_down:

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

Impacted Files
Coverage Δ

crates/net/network/src/peers/reputation.rs
67.50% <ø> (-2.50%)
:arrow_down:

... and 251 files with indirect coverage changes


Make webpage on meme.institute

I should make a page on meme.institute (meme.institute/swood?) with a troubleshooting page with those fancy links that go directly to the section of the page relating to your thing (a href="#memes"? Not sure) (Ref Issue #3)
Follow the same guidelines as the GXSCC page

Sort of finished, just a link to the GitHub https://meme.institute/swood

Ok it's really finished now. Online demo and everything.


Where is the tracker list?

I'm looking for the tracker-list which, according to the documentation, is supposed to be found at https://github.com/humanswitch/consentcookie/blob/master/src/assets/json/trackers.json. This file does not exist though...

We removed the tracker list from the ConsentCookie project and its now maintained externally.
For the moment you can get the latest version at: link
Also it it possible to make use of our configurator tool to get an better overview which applications are available and you can submit any missing application.
Documentation is currently be updated with this info.


CreateRepository request is not allowed because there is no existing repository in this AWS account or AWS Organization

Good Day,
Attempting to deploy Superbase on AWS using the launch templates but getting the below error:
CreateRepository request is not allowed because there is no existing repository in this AWS account or AWS Organization (Service: AWSCodeCommit; Status Code: 400
AWS has deprecated AWS CodeCommit and this might be the reason for the error.
Could you kindly assist in finding a new solution and updating the cloudformation stack.

Facing the same issue. Would appreciate a solution a lot:)

Any fixes/alternatives?

I set up business support on my aws account and logged a ticket for CodeCommit.

man i just switched to appwrite and got it setup like 30 mins ago, but ill keep that in mind in case i need to switch back, thank you!

CodeCommit is being sunset, so it's not available to any customers that don't already have respositories in CodeCommit. I assume the project will remove CodeCommit dependencies at some point - unitl then no new deployments will be possible using this Cloudformation template.
https://aws.amazon.com/blogs/devops/how-to-migrate-your-aws-codecommit-repository-to-another-git-provider/


How can I implement multi-viewtype if you hide viewType parameter when calling abstract method onCreateViewHolder in UltimateViewAdapter class?

Can you give me a email address so we can discuss some issues about this library?

I found that on the Readme


Release/v1.8.0

Purpose

How does the solution address the problem

Changes made

prnet cleaned-up successfully