Cert renewal loop

Describe the bug:
As initially discussed in https://github.com/jetstack/cert-manager/issues/3813, the Vault Issuer clamps duration according to its max_ttl value, which defaults to 30 days. It also backdates notBefore by 30 seconds (https://www.vaultproject.io/api-docs/secret/pki#not_before_duration). With these default settings, this certificate will renew every 30 seconds:
apiVersion: cert-manager.io/v1
kind: Certificate
metadata:
  name: example
spec:
  duration: 1440h   # 60d
  renewBefore: 720h # 30d
  issuerRef:
    kind: Issuer
    name: vault
  secretName: example

What happens is Vault clamps duration to 30 days, then increases it to 30 days and 30 seconds by backdating notBefore. So actual duration becomes 720h0m30s, which is 30s greater than the renewBefore value of 720h0m0s. Since renewBefore is less than actual duration, cert-manager uses this value instead of the 2/3 default:https://github.com/jetstack/cert-manager/blob/2bdda7210dd368cb6f04a2398c6da87524719b54/pkg/controller/certificates/util.go#L304
Expected behaviour:
The intent of the above spec is to have the certificate renewed 50% of the way through its validity period. It definitely should not cause a renewal loop.
The logic in https://github.com/jetstack/cert-manager/pull/4040 prevents these kinds of renewal loops, but it was lost in https://github.com/jetstack/cert-manager/pull/4092 in order to allow users to specify a renewBefore value greater than 2/3 of duration. I have 2 proposals for preventing renewal loops while respecting these constraints:

If renewBefore is provided, scale it by the ratio of actual duration to duration. In the above example, this would result in the certificate being renewed every 15 days instead of every 30 seconds. The same renewal loop could still occur if a user set duration=720h and renewBefore=719h59m30s, but it wouldn't occur by accident.
Enforce a minimum interval between renewals to prevent renewal loops. A sane default minimum for most use cases might be 1h, but this could be a configuration flag. This would prevent the hot renewal loops, but renewals would still be occurring much more frequently than the user had intended.

Implementing both proposals would provide the benefits of each.
Environment details::

cert-manager version: v1.4.2 (the relevant logic is unchanged in v1.5)

/kind bug

/kind bug

Hi, thanks for the clear and detailed issue!
I also find it confusing; for me, the confusion comes from the fact that the "actual duration" is unknown when I choose a value for renewBefore, meaning I can end up with a hot loop without realizing it.
For example, when I use the Venafi Issuer with a Windows Certificate Authority template that "clamps" the duration to 2 years (which I didn't know beforehand), I choose the renewBefore value depending on the duration I give. For example, with a 2 months duration, I'd like the renew to happen 30 days before expiry:
kind: Certificate
spec:
  duration: 2160h   # 90d
  renewBefore: 720h # 30d

But if I knew that the "actual" duration would be 2 years, I would much rather have set the renewBefore value to 6 months!
kind: Certificate
spec:
  duration: 2160h   # 90d (ignored)
  renewBefore: 720h # 30d
status:
  notAfter: 2023-10-07 # 2 years from now
  renewalTime: 2023-09-07 # 30 days before expiry

Sometimes I wish the renewBefore value didn'nt exist, and that instead we would have a renewAtPercent. Since we (mostly) never know what is going to be the "actual" duration, it would be so much easier to say "I want the renewal to happen at 70% of the actual duration". But since we probably don't want to add new fields to the Certificate resource, I guess we have to stick to renewBefore.

/remove-lifecycle stale

Apologies on the delay @maelvls, I missed your response initially.

Sometimes I wish the renewBefore value didn'nt exist, and that instead we would have a renewAtPercent. Since we (mostly) never know what is going to be the "actual" duration, it would be so much easier to say "I want the renewal to happen at 70% of the actual duration". But since we probably don't want to add new fields to the Certificate resource, I guess we have to stick to renewBefore

Would you be open to making renewBefore accept either a percent or a duration? Similar to the maxUnavailable and maxSurge fields for deployments?

Maybe think this issue is more of a UX issue than a bug? I.e., the renewal loop is surprising when thinking that duration will be honored but is not honored.

I don't disagree per se, but as operators of cert-manager in a multi-tenant cluster we need some means of technical enforcement to prevent renewal loops. My proposal to optionally enforce a minimum interval between renewals (e.g. make it a parameter that defaults to 0s) could address this without changing any other semantics.

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale

/remove-lifecycle stale

Would you be open to making renewBefore accept either a percent or a duration? Similar to the maxUnavailable and maxSurge fields for deployments?

@cbroglie For the record, I think that is a great idea. And we would gladly accept a PR like that.

/remove-lifecycle stale

/remove-lifecycle stale

@cbroglie
A pre-release is now available containing the fix for this issue. Please test and feedback if you have time.

https://github.com/cert-manager/cert-manager/releases/tag/v1.16.0-alpha.0

@wallrj I can give this a shot first thing next week and report back

@wallrj v1.16.0-alpha.0 + renewBeforePercentage seems to be working well in my testing 👍

Still need to document this new feature. If you have time please submit a PR against the cert-manager/website release-next branch:

https://release-next--cert-manager.netlify.app/docs/releases/release-notes/release-notes-1.16#themes
https://release-next--cert-manager.netlify.app/docs/usage/certificate/#reissuance-triggered-by-expiry-renewal

Opened https://github.com/cert-manager/website/pull/1551

A beta-release is now available which contains the fix for this issue. Please test and feedback if you have time.

https://github.com/cert-manager/cert-manager/releases/tag/v1.16.0-beta.0


Implement simple "controller" for adaptive time stepping

In most papers about MPRK schemes the Robertson problem is "adaptively" solved by setting $\Delta t_{i+1}=c\Delta t_i$ for some constant $c$. We should also have this option for comparisons.

That's already possible right now with a callback:
julia> using OrdinaryDiffEq

julia> ode = ODEProblem((du, u, p, t) -> du .= -u, [1.0], (0.0, 1.0))
ODEProblem with uType Vector{Float64} and tType Float64. In-place: true
timespan: (0.0, 1.0)
u0: 1-element Vector{Float64}:
 1.0

julia> sol = solve(ode, ImplicitEuler();
                   adaptive = false, dt = 1 / 2^5,
                   callback = DiscreteCallback(Returns(true),
                       integrator -> set_proposed_dt!(integrator, 2 * get_proposed_dt(integrator));
                       save_positions = (false, false)));

julia> diff(sol.t)
6-element Vector{Float64}:
 0.03125
 0.0625
 0.125
 0.25
 0.5
 0.03125

But it would definitely be nice to document this explicitly.

This approach  results in an OutOfMemoryError() when we try to solve prob_pds_robertson. Would be great to make this work. This should also be included in the tests.
julia> using PositiveIntegrators, OrdinaryDiffEq
julia> sol = solve(prob_pds_robertson, ImplicitEuler();
                          adaptive = false, dt = 1e-5,
                          callback = DiscreteCallback(Returns(true),
                          integrator -> set_proposed_dt!(integrator, 2 * get_proposed_dt(integrator));
                          save_positions = (false, false)));
ERROR: OutOfMemoryError()
Stacktrace:
  [1] sizehint!
    @ ./array.jl:1351 [inlined]
  [2] __init(prob::ODEProblem{…}, alg::ImplicitEuler{…}, timeseries_init::Tuple{}, ts_init::Tuple{}, ks_init::Tuple{}, recompile::Type{…}; saveat::Tuple{}, tstops::Tuple{}, d_discontinuities::Tuple{}, save_idxs::Nothing, save_everystep::Bool, save_on::Bool, save_start::Bool, save_end::Nothing, callback::DiscreteCallback{…}, dense::Bool, calck::Bool, dt::Float64, dtmin::Float64, dtmax::Float64, force_dtmin::Bool, adaptive::Bool, gamma::Rational{…}, abstol::Nothing, reltol::Nothing, qmin::Rational{…}, qmax::Int64, qsteady_min::Int64, qsteady_max::Rational{…}, beta1::Nothing, beta2::Nothing, qoldinit::Rational{…}, controller::Nothing, fullnormalize::Bool, failfactor::Int64, maxiters::Int64, internalnorm::typeof(DiffEqBase.ODE_DEFAULT_NORM), internalopnorm::typeof(LinearAlgebra.opnorm), isoutofdomain::typeof(DiffEqBase.ODE_DEFAULT_ISOUTOFDOMAIN), unstable_check::typeof(DiffEqBase.ODE_DEFAULT_UNSTABLE_CHECK), verbose::Bool, timeseries_errors::Bool, dense_errors::Bool, advance_to_tstop::Bool, stop_at_next_tstop::Bool, initialize_save::Bool, progress::Bool, progress_steps::Int64, progress_name::String, progress_message::typeof(DiffEqBase.ODE_DEFAULT_PROG_MESSAGE), progress_id::Symbol, userdata::Nothing, allow_extrapolation::Bool, initialize_integrator::Bool, alias_u0::Bool, alias_du0::Bool, initializealg::OrdinaryDiffEq.DefaultInit, kwargs::@Kwargs{})
    @ OrdinaryDiffEq ~/.julia/packages/OrdinaryDiffEq/J5YGH/src/solve.jl:288
  [3] __init (repeats 5 times)
    @ ~/.julia/packages/OrdinaryDiffEq/J5YGH/src/solve.jl:10 [inlined]
  [4] __solve(::ODEProblem{…}, ::ImplicitEuler{…}; kwargs::@Kwargs{…})
    @ OrdinaryDiffEq ~/.julia/packages/OrdinaryDiffEq/J5YGH/src/solve.jl:5
  [5] __solve
    @ ~/.julia/packages/OrdinaryDiffEq/J5YGH/src/solve.jl:1 [inlined]
  [6] solve_call(_prob::ODEProblem{…}, args::ImplicitEuler{…}; merge_callbacks::Bool, kwargshandle::Nothing, kwargs::@Kwargs{…})
     Use `show(err)` to see complete types.

We need a kind of ugly hack here:
julia> sol = solve(prob_pds_robertson, ImplicitEuler();
                   adaptive = false, dt = Inf,
                   callback = DiscreteCallback(Returns(true),
                       integrator -> set_proposed_dt!(integrator, 2 * get_proposed_dt(integrator));
                       save_positions = (false, false),
                       initialize = (c, u, t, integrator) -> set_proposed_dt!(integrator, 1.0e-5)));

should work. The reason is that OrdinaryDiffEq.jl wants to allocate memory for the solution. With adaptive = false, it divides the time span by the given dt to get the number of steps. This is of course completely wrong in this case since the initial dt is tiny compared to tspan. The hack above avoids this.

Documented in #110


[Feature Request] Update to Minecraft 1.21

What new features do you want?
PCA needed!
Latest CI build tested

[X] I confirm that the feature I requested is not in the latest CI build.

1.21 mod seems to be close... You can already download a preview version in the Actions page.

There's already an issue about this.已经有一个关于此的问题。 btw 1.21 mod seems to be close... You can already download a preview version in the Actions page.顺便提一下，1.21 模组似乎快要来了……你可以在 Actions 页面下载预览版。

However, the preview version doesn't seem to work; I've tried both 1.21 and 1.21.1, and both crashed.

There's already an issue about this.已经有一个关于此的问题。 btw 1.21 mod seems to be close... You can already download a preview version in the Actions page.顺便提一下，1.21 模组似乎快要来了……你可以在 Actions 页面下载预览版。

However, the preview version doesn't seem to work; I've tried both 1.21 and 1.21.1, and both crashed.

me either... its possible that the author set some kind of restrictions
idk maybe its just sth went wrong with my environment

There's already an issue about this.已经有一个关于此的问题。 btw 1.21 mod seems to be close... You can already download a preview version in the Actions page.顺便提一下，1.21 模组似乎快要来了……你可以在 Actions 页面下载预览版。

However, the preview version doesn't seem to work; I've tried both 1.21 and 1.21.1, and both crashed.

Hi, could you please post those crash logs? Better if use mclo.gs

There's already an issue about this.已经有一个关于此的问题。 btw 1.21 mod seems to be close... You can already download a preview version in the Actions page.顺便提一下，1.21 模组似乎快要来了……你可以在 Actions 页面下载预览版。

However, the preview version doesn't seem to work; I've tried both 1.21 and 1.21.1, and both crashed.

Try this method
https://github.com/Nyan-Work/plusls-carpet-addition/issues/39#issue-2558447909


Cut Version 3.0.0

Cut a new release given PR #189
I think waiting another month to see if there are any more breaking changes seems reasonable. If there are other preferences, feel free to voice them! I'm glad to cut a new release earlier if someone thinks they will benefit substantially.

New version cut: https://github.com/spdx/ntia-conformance-checker/releases/tag/v3.0.0


Instructions to run outside of Docker?

I don't use docker; is running this just a matter of cloning the repo, installing the reqs, setting the ENVs and running with python?

FWIW I was able to run successfully in a VENV.

Apologies, I will add some non dockerised instructions soon to the repo.

From: sshaikh @.>
Sent: 13 June 2024 15:05
To: JosephRPalmer/octopus-usage-exporter @.>
Cc: Subscribed @.***>
Subject: Re: [JosephRPalmer/octopus-usage-exporter] Instructions to run outside of Docker? (Issue #2)
FWIW I was able to run successfully in a VENV.
—
Reply to this email directly, view it on GitHubhttps://github.com/JosephRPalmer/octopus-usage-exporter/issues/2#issuecomment-2165775989, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AAU4FSB6RMEXMH55XSNVLN3ZHGRJXAVCNFSM6AAAAABI5Q2HL6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNRVG43TKOJYHE.
You are receiving this because you are subscribed to this thread.Message ID: @.***>


Update CODE_OF_CONDUCT.md

updated language and contact information

@SaraJaoude maybe one thing in addition.
The contact website in the title has Website. (see top left corner)

Maybe Eddie (or you) want to adjust this

@SaraJaoude maybe one thing in addition.
The contact website in the title has Website. (see top left corner)

Maybe Eddie (or you) want to adjust this

Thanks @schmelto - totally agree.  We will update it to refer to "Contact Page".


Get release history seems not work well

I had deploy swift on k8s and encounter some problem:
Every endpoint works well, but the Release history endpoint always return empty json data {},while I use helm client directy , it return responding info.
My Tiller Version:
λ helm version
Client: &version.Version{SemVer:"v2.7.2", GitCommit:"8478fb4fc723885b155c924d1c8c410b7a9444e6", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.8.0", GitCommit:"14af25f1de6832228539259b821949d20069a222", GitTreeState:"clean"}

Swift pod info:(with image: appscode/swift:0.6.0)
{
  "kind": "Deployment",
  "apiVersion": "extensions/v1beta1",
  "metadata": {
    "name": "xinge-swift-swift",
    "namespace": "kube-system",
    "selfLink": "/apis/extensions/v1beta1/namespaces/kube-system/deployments/xinge-swift-swift",
    "uid": "c33a1e58-0664-11e8-8074-00163e0af3dd",
    "resourceVersion": "2403043",
    "generation": 3,
    "creationTimestamp": "2018-01-31T08:57:27Z",
    "labels": {
      "app": "swift",
      "chart": "swift-0.3.0",
      "heritage": "Tiller",
      "release": "xinge-swift"
    },
    "annotations": {
      "deployment.kubernetes.io/revision": "3"
    }
  },
  "spec": {
    "replicas": 1,
    "selector": {
      "matchLabels": {
        "app": "swift",
        "release": "xinge-swift"
      }
    },
    "template": {
      "metadata": {
        "creationTimestamp": null,
        "labels": {
          "app": "swift",
          "release": "xinge-swift"
        }
      },
      "spec": {
        "volumes": [
          {
            "name": "chart-volume",
            "emptyDir": {}
          }
        ],
        "containers": [
          {
            "name": "swift",
            "image": "appscode/swift:0.6.0",
            "args": [
              "run",
              "--v=3",
              "--connector=incluster"
            ],
            "ports": [
              {
                "name": "pt",
                "containerPort": 9855,
                "protocol": "TCP"
              },
              {
                "name": "tls",
                "containerPort": 50055,
                "protocol": "TCP"
              },
              {
                "name": "ops",
                "containerPort": 56790,
                "protocol": "TCP"
              }
            ],
            "resources": {},
            "volumeMounts": [
              {
                "name": "chart-volume",
                "mountPath": "/tmp"
              }
            ],
            "terminationMessagePath": "/dev/termination-log",
            "terminationMessagePolicy": "File",
            "imagePullPolicy": "IfNotPresent"
          }
        ],
        "restartPolicy": "Always",
        "terminationGracePeriodSeconds": 30,
        "dnsPolicy": "ClusterFirst",
        "serviceAccountName": "xinge-swift-swift",
        "serviceAccount": "xinge-swift-swift",
        "securityContext": {},
        "schedulerName": "default-scheduler"
      }
    },
    "strategy": {
      "type": "RollingUpdate",
      "rollingUpdate": {
        "maxUnavailable": "25%",
        "maxSurge": "25%"
      }
    },
    "revisionHistoryLimit": 2,
    "progressDeadlineSeconds": 600
  },
  "status": {
    "observedGeneration": 3,
    "replicas": 1,
    "updatedReplicas": 1,
    "readyReplicas": 1,
    "availableReplicas": 1,
    "conditions": [
      {
        "type": "Available",
        "status": "True",
        "lastUpdateTime": "2018-01-31T08:57:29Z",
        "lastTransitionTime": "2018-01-31T08:57:29Z",
        "reason": "MinimumReplicasAvailable",
        "message": "Deployment has minimum availability."
      },
      {
        "type": "Progressing",
        "status": "True",
        "lastUpdateTime": "2018-02-05T09:38:14Z",
        "lastTransitionTime": "2018-01-31T08:57:27Z",
        "reason": "NewReplicaSetAvailable",
        "message": "ReplicaSet \"xinge-swift-swift-55d5b78447\" has successfully progressed."
      }
    ]
  }
}

kubeneters version:
λ kubectl version
Client Version: version.Info{Major:"1", Minor:"9", GitVersion:"v1.9.0", GitCommit:"925c127ec6b946659ad0fd596fa959be43f0cc05", GitTreeState:"clean", BuildDate:"2017-12-15T21:07:38Z", GoVersion:"go1.9.2", Compiler:"gc", Platform:"windows/amd64"}
Server Version: version.Info{Major:"1", Minor:"8+", GitVersion:"v1.8.3-rancher1", GitCommit:"beb8311a9f114ba92558d8d771a81b7fb38422ae", GitTreeState:"clean", BuildDate:"2017-11-14T00:54:19Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}

Request with curl:
λ curl -X GET \
>   http://k8s.fxdayu.com/swift/tiller/v2/releases/test-release/json \
>   -H 'Authorization: Basic eGl*******pZnQ=' \
>   -H 'Cache-Control: no-cache' \
>   -H 'Postman-Token: 0ea146cd-21c0-205b-f6ed-8d412141da80'
{}

Request with helm client Directly:
λ helm list test-release
NAME            REVISION        UPDATED                         STATUS          CHART               NAMESPACE
test-release    3               Mon Feb  5 18:08:19 2018        DEPLOYED        test-chart-0.1.0    default
λ helm history test-release
REVISION        UPDATED                         STATUS          CHART                   DESCRIPTION
1               Mon Feb  5 17:45:20 2018        SUPERSEDED      test-chart-0.1.0        Install complete
2               Mon Feb  5 18:08:16 2018        SUPERSEDED      test-chart-0.1.0        Upgrade complete
3               Mon Feb  5 18:08:19 2018        DEPLOYED        test-chart-0.1.0        Upgrade complete

Is there anyone encountered the similar problem?
I'm not familiar with Golang,  could anyone give some help, thanks very much.

Please use the url http://k8s.fxdayu.com/swift/tiller/v2/releases/test-release/json?max=10 to get history. Since the max parameter was not set, it was defaulted to 0 and returned no results.
Please reopen if you are still having issue.


fix(windows): connect network for non-admin users

Description
While connecting to a network in windows by a non-admin user, the connection fails if the project/package-workspace is under some restricted location (Ex: Program Files) because the nodeWifiConnect.xml is created is not getting created due to permission issues.
Changed the location of nodeWifiConnect.xml to be created in a temporary directory (C:\Users\AppData\Local\Temp) so that work flow is uninterrupted for non-admin user also.
Motivation and Context
This change is required as all window users (Admin and Non-Admin) should be able to connect to the network.
#159
Usage examples

How Has This Been Tested?
After the required changes are done, we tried to connect to the network in a non-admin user machine, which works as expected.
Types of changes

[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[ ] Refactorization (non-functional change which improve code readibility)

Hi, give me 2 days to process this PR.

Perfect 👌

This pull request has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.


Failure of -isMethodReturnType:compatibleWithValueType: for some methods taking structs with iOS 11 SDK

Chrome on iOS is building with iOS 11 SDK and experiencing errors when trying to mock returning/passing some structure by reference (see http://crbug.com/736987).
The issue happens because the code tries to compare the following two strings:
r^{GURL={basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >={__compressed_pair<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::__rep, std::__1::allocator<char> >={__rep}}}B{Parsed={Component=ii}{Component=ii}{Component=ii}{Component=ii}{Component=ii}{Component=ii}{Component=ii}{Component=ii}B^{}}{unique_ptr<GURL, std::__1::default_delete<GURL> >={__compressed_pair<GURL *, std::__1::default_delete<GURL> >=^{}}}}

and
r^{GURL={basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >={__compressed_pair<std::__1::basic_string<char, std::__1::char_traits<char>, std::__1::allocator<char> >::__rep, std::__1::allocator<char> >={__rep=(?={__long=QQ*}{__short=(?=Cc)[23c]}{__raw=[3Q]})}}}B{Parsed={Component=ii}{Component=ii}{Component=ii}{Component=ii}{Component=ii}{Component=ii}{Component=ii}{Component=ii}B^{Parsed}}{unique_ptr<GURL, std::__1::default_delete<GURL> >={__compressed_pair<GURL *, std::__1::default_delete<GURL> >=^{GURL}}}}

Some things that the code does not like are {} and {__rep}.

Forgot to mention that this happens with HEAD version of ocmock fetched from github.

Yeah, I had noticed that, too. And I'm glad that you've provided a fix. It would have taken me a while to get into this. Thanks.

Thanks! Have merged the PR now.


zephyr-dom0-xt: rpi5; remove usage of xen_dom0 snippet

The usage of xen_dom0 with Zephyr applications is proved to be
problematic [1]. And moving only "hypervisor" and "memory" nodes in
zephyr-dom0-xt rpi_5.overlay doesn't solve all problems as it cuses build
warning due to different usage of #address-cells/size-cells in RPI5 DTS.
Actulaly if "hypervisor" and "memory" are moved in application board
files the xen_dom0 snippet will be left to provide just proper Xen
HVC console and to enable CONFIG_XEN_DOM0.
Hence, drop usage of xen_dom0 snippet for zephyr-dom0-xt application and
move all needed parts in application board files. Now everything is one
place.
[1] https://github.com/xen-troops/zephyr-xenlib/pulls

@lorc @oleksiimoisieiev @dsemenets @firscity

Yep. LGTM Reviewed-by: Oleksii Moisieiev<EMAIL_ADDRESS>Closing #107

Should be appropriate PR in meta-xt-rpi5-prod-devel

Acked-by: Dmytro Semenets<EMAIL_ADDRESS>


Index overflow in FF register file in RV32E configuration

Observed Behavior
In the FF register file there is following assignment:
assign rdata_a_o = rf_reg[raddr_a_i];
assign rdata_b_o = rf_reg[raddr_b_i];
When LW instruction is executed and immediate offset is >15, it causes index overflow in rf_reg[raddr_b_i]. This causes X values to propagate through out the CPU from this assignment.
It also causes IbexDataReqPayloadX assert to trigger.
Expected Behavior
It appears that in the LATCH register file this is avoided by:
assign raddr_a_int = raddr_a_i[ADDR_WIDTH-1:0];
assign raddr_b_int = raddr_b_i[ADDR_WIDTH-1:0];
assign waddr_a_int = waddr_a_i[ADDR_WIDTH-1:0];
assign rdata_a_o = mem[raddr_a_int];
assign rdata_b_o = mem[raddr_b_int];
Steps to reproduce the issue
Configure IBEX core with FF register file and RV32E instruction set.
For example following instructions decode will cause the issue:
0x03412783          	lw	a5,52(sp)
This instruction will cause 20(dec) to be inserted into the rf_reg[20] but that array has only size of 16.
My Environment
I am using the IBEX core with RV32E extension. (reduced register file)
Version of the Ibex source code:
It appears the latest version of FF register file on GIT still has the assignments in question.
assign rdata_a_o = rf_reg[raddr_a_i];
assign rdata_b_o = rf_reg[raddr_b_i];

Hmm, that's odd. Could you generate a simple example firmware (a few lines of assembly!) that shows the problem and paste the code here?
I'm also a bit confused because you're looking at (e.g.) the rdata_a_o output from the register file (filled by reading a register) and executing an LW instruction (which writes to a register). Something seems to be a little amiss!


samples_Fonts share

We can share  samples_Fonts in this title?
my archieve is https://github.com/mumin16/GTK-4-Reference-Manual-pdf/blob/main/samples_Fonts.rar

I can add links for font icons yes like i started to do in the wiki . but i will not embed sample fonts in this repo.
If you can make a list of font icon url its cool.
by url, i mean to point on original link (for license term and credits)

I can add links for font icons yes like i started to do in the wiki . but i will not embed sample fonts in this repo.
If you can make a list of font icon url its cool.
by url, i mean to point on original link (for license term and credits)


[BUG]  Azure.Communication.Chat is not mockable

Library name and version
Azure.Communication.Chat 1.3.1
Describe the bug
The Azure Communication Chat library is not mockable.
Especially for a service that I cannot emulate locally, I need to be able to mock out the interactions with it.
Expected behavior
I would expect the library to adhere to the design guidlines for testability:
https://learn.microsoft.com/en-us/dotnet/azure/sdk/unit-testing-mocking?tabs=csharp
Actual behavior
I cannot mock:

CreateChatThreadResult
ChatThreadProperties
there's probably many more

Reproduction Steps
n/a
Environment
No response

Hi @cmeyertons.  Thanks for reaching out and we regret that you're experiencing difficulties.   To my knowledge, the Chat library is following Azure SDK standards for mockability and testing.  As the unit testing article describes in the note from this section:

Some input models have read-only properties that are only populated when the model is returned by the service. In this case, a model factory method will be available that allows setting these properties.

The types that you're asking about fall into that category and can be created using the ChatModelFactory:

CreateChatThreadResult
ChatThreadProperties

If there are types that are not publicly constructable and do not exist in the model factory, please let us know so that we can make the necessary adjustments.


What is the best (most idiomatic?) way to implement plaquettes?

Is your feature request related to a problem? Please describe.
From a comment thread:
@inmzhang

For CNOT based circuits, I suggest to use X-basis reset/measurement instead of Z-basis ones with H gates. So this can be "RX - CX - CX - MX". The same for other X-basis plaquettes. This is followed by the convention that is widely used in the QEC papers:

CZ-based gateset(CZ, RZ, MZ, ...) which is used by the superconducting architecture and can be tested under SI1000 noise model.
CX-based gateset(CX, RZ, MZ, RX, MX) which is a universal test case for the code performance and usually is tested under uniform depolarizing noise model.

@nelimee

That would simplify things a little bit. What about Pauli syndromes measuring ZXXZ? I do not see a way of "removing" the H here.

@inmzhang

I suppose you mean ZXXZ plaquettes used in Google's experiment. They use the CZ-based gateset and then there should be a moment of H gates after resets and before measurements. But for the standard CSS type surface code here, with RX/MX available, the moment of H gates can be removed safely.
Maybe Austin @afowler can provide some opinions on the usage of the different gatesets?

What is the best (most idiomatic?) way to implement plaquettes?

Start with RX-CNOT-MX and RZ-CNOT-MZ circuits for testing and debugging and
benchmarking with depolarizing noise then exchange each CNOT with H-CZ-H
and expand RX and MX using H. You'll find that every weight 4 plaquette
becomes the same up to interaction order, and you'll have 10 moments,
R-H-CZ-H-CZ-CZ-H-CZ-H-M. The H gates amongst the CZ gates will be on the
data qubits.
Best,
Austin.
On Mon, Oct 7, 2024, 5:50 AM Adrien Suau @.***> wrote:

Is your feature request related to a problem? Please describe.
From a comment thread
https://github.com/QCHackers/tqec/pull/334#discussion_r1789772177:
@inmzhang https://github.com/inmzhang
For CNOT based circuits, I suggest to use X-basis reset/measurement
instead of Z-basis ones with H gates. So this can be "RX - CX - CX - MX".
The same for other X-basis plaquettes. This is followed by the convention
that is widely used in the QEC papers:

CZ-based gateset(CZ, RZ, MZ, ...) which is used by the
superconducting architecture and can be tested under SI1000 noise model.
CX-based gateset(CX, RZ, MZ, RX, MX) which is a universal test case
for the code performance and usually is tested under uniform depolarizing
noise model.

@nelimee https://github.com/nelimee
That would simplify things a little bit. What about Pauli syndromes
measuring ZXXZ? I do not see a way of "removing" the H here.
@inmzhang https://github.com/inmzhang
I suppose you mean ZXXZ plaquettes used in Google's experiment. They use
the CZ-based gateset and then there should be a moment of H gates after
resets and before measurements. But for the standard CSS type surface code
here, with RX/MX available, the moment of H gates can be removed safely.
Maybe Austin @afowler https://github.com/afowler can provide some
opinions on the usage of the different gatesets?
What is the best (most idiomatic?) way to implement plaquettes?
—
Reply to this email directly, view it on GitHub
https://github.com/QCHackers/tqec/issues/337, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKAXTB57OAVTVBVK5VV2Y3Z2J7P7AVCNFSM6AAAAABPP3NJUOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGU3TAMZUHE2TKMY
.
You are receiving this because you were mentioned.Message ID:
@.***>

Figure S12 of https://arxiv.org/abs/2408.13687 contains the full circuit
for the surface code on Google hardware.
Best,
Austin.
On Mon, Oct 7, 2024 at 9:02 AM Austin Fowler @.***>
wrote:

Start with RX-CNOT-MX and RZ-CNOT-MZ circuits for testing and debugging
and benchmarking with depolarizing noise then exchange each CNOT with
H-CZ-H and expand RX and MX using H. You'll find that every weight 4
plaquette becomes the same up to interaction order, and you'll have 10
moments, R-H-CZ-H-CZ-CZ-H-CZ-H-M. The H gates amongst the CZ gates will be
on the data qubits.
Best,
Austin.
On Mon, Oct 7, 2024, 5:50 AM Adrien Suau @.***> wrote:

Is your feature request related to a problem? Please describe.
From a comment thread
https://github.com/QCHackers/tqec/pull/334#discussion_r1789772177:
@inmzhang https://github.com/inmzhang
For CNOT based circuits, I suggest to use X-basis reset/measurement
instead of Z-basis ones with H gates. So this can be "RX - CX - CX - MX".
The same for other X-basis plaquettes. This is followed by the convention
that is widely used in the QEC papers:

CZ-based gateset(CZ, RZ, MZ, ...) which is used by the
superconducting architecture and can be tested under SI1000 noise model.
CX-based gateset(CX, RZ, MZ, RX, MX) which is a universal test
case for the code performance and usually is tested under uniform
depolarizing noise model.

@nelimee https://github.com/nelimee
That would simplify things a little bit. What about Pauli syndromes
measuring ZXXZ? I do not see a way of "removing" the H here.
@inmzhang https://github.com/inmzhang
I suppose you mean ZXXZ plaquettes used in Google's experiment. They use
the CZ-based gateset and then there should be a moment of H gates after
resets and before measurements. But for the standard CSS type surface code
here, with RX/MX available, the moment of H gates can be removed safely.
Maybe Austin @afowler https://github.com/afowler can provide some
opinions on the usage of the different gatesets?
What is the best (most idiomatic?) way to implement plaquettes?
—
Reply to this email directly, view it on GitHub
https://github.com/QCHackers/tqec/issues/337, or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAKAXTB57OAVTVBVK5VV2Y3Z2J7P7AVCNFSM6AAAAABPP3NJUOVHI2DSMVQWIX3LMV43ASLTON2WKOZSGU3TAMZUHE2TKMY
.
You are receiving this because you were mentioned.Message ID:
@.***>


New Dataset [Subseasonal Rodeo Dataset]

Dataset Name
The SubseasonalRodeo Dataset
Dataset URL
https://dataverse.harvard.edu/dataset.xhtml?persistentId=doi:10.7910/DVN/IHBANG
Description
A benchmark dataset for training and evaluating subseasonal forecasting systems—systems predicting temperature or precipitation 2-6 weeks in advance—in the western contiguous United States. This dataset gathers various datas concerning precipitation and temperature, used in the Rodeo forecasting model.
Size
The datasets consists of 160 Mb files in a total of 10 GB.
License
Unknown
Data Format
HDF
Data Format (other)
.h5
Access protocol
HTTP(S)
Source File Organization
The source files aren't quite organized in this dataset. It gathers datas of different parameters (precipitation, wind, temperature...) from different eras.
Example URLs
https://dataverse.harvard.edu/dataset.xhtml?persistentId=doi:10.7910/DVN/IHBANG

Authorization
No; data are fully public
Transformation / Processing
There's nothing to modify in this dataset. The forecasting model is able to work with this dataset. No more analysis is needed.
Target Format
Other
Comments
they have to keep the same name and the same format (.h5)

Is there any ability to combine some of these datasets? Or should each file be mapped to a single zarr store?

Actually no... each file is named for a certain reason and used at different moments in the algorithm. Each file may have to exist in its own zarr...

Closing this as wontfix due to inactivity.


UndoRedo support for the TimelineEditor

Created to solve #426 and #321.
Implemented with a local instance of godots UndoRedo.
By the time of writing this, it should work for:

deleting events (with DELETE key)
pasting events (CRTL+V)
cutting events (CRTL+X)
moving events (by dragging them)

When it messes up:

if you do a not undoable action between these actions, the undo might do unexpected things (move the wrong item, etc.)

Future ideas:

would love to make adding of events via the buttons and CRTL+T undoable, same goes for duplication. Also the option buttons and movement using ALT+Arrow keys.

Please test this!

Thanks for testing.
About Redo (CRTL+Y):
Actually in godot (at least for me, not sure if it's the same for you) Redo works with CRTL+SHIFT+Z. That should actually work already.

ah, that is in actually didn't notice, guess it's just because I'm using CTRL+Y for redoing actions, thanks though!

I've pushed a fix for CRTL+Y. Don't think it hurts.

Okay I finally managed to implement all the features I wanted for this now. Feel free to test again. Adding in events should be undoable as well as duplicating. I'll be away the next couple of days so if there's a problem you'll need to wait a bit.

I will test this now and see if I can merge to main


Log input files and test case paths when ONNX tests fail.

Fixes https://github.com/nod-ai/SHARK-TestSuite/issues/319

Sample compile error logs: https://gist.github.com/ScottTodd/1fbb40a72b226464b9ec2a1396880914
Sample run error logs: https://gist.github.com/ScottTodd/111320271f012f42f984fdd5cfc65186

Ping?


Y24-121 - As a developer (Ben) I would like there to be fine-grained batch creation validation for sequencing pipelines

User story
As a developer (Ben) I would like there to be fine-grained batch creation validation for sequencing pipelines.
Currently batch validation for sequencing pipelines lives in a few places, default records, sequencing pipeline model, batch model. This implementation limits any new validation to be added as global validation to every batch (validation in batch.rb). However with some pipelines we want fine grained batch creation behaviour like NovaSeqX
The aim of this story is to enable custom/individual batch validation for each pipeline. There may be a few ways to do this and it may require some investigation prior to implementation. My suggested implementation:

Adding a custom validator class for each  required pipeline. This validator would be referenced in the pipeline config or similar. All existing pipelines could fall back on a 'standard' validator class which contains the existing validation. Then we add a validator class for each pipeline that requires custom validation.
We would move the current pipeline/batch.rb validation to the 'standard' validator class.
Ensure the batch creation javascript works with the updated methods. https://github.com/sanger/sequencescape/blob/develop/app/views/pipelines/show.html.erb contains some logic to fade out unusable requests when creating a batch and this should still work. Also consider whether this can refactored and allow us to use other logic ontop of batch size.

Who are the primary contacts for this story
Ben T, Tris B
Who is the nominated tester for UAT
Tris B
(May not need UAT as there should be noticeable difference)

Adding a custom validator class for each required pipeline. This validator would be referenced in the pipeline config or similar. All existing pipelines could fall back on a 'standard' validator class which contains the existing validation. Then we add a validator class for each pipeline that requires custom validation.

Hi @BenTopping, I assume you're suggesting adding a fine-grained validator for each pipeline in config/default_records/pipelines/default_records.yml? For example:
NovaSeqX PE:
  name: NovaSeqX PE
  active: 1
  sti_type: SequencingPipeline
  sorter: 10
  max_size: 8
  summary: 1
  externally_managed: 0
  group_name: Sequencing
  control_request_type_id: 0
  min_size: 8
  request_type_keys:
    - illumina_htp_novaseqx_paired_end_sequencing
  workflow:
    name: NovaSeqX PE
    item_limit: 8
 validator: NovaSeqXPEValidator

@dasunpubudumal Good question. I think limiting to the custom validator is the most flexible option. It may cause some code duplication but it allows greater flexibility. It might also be possible to make validator subclasses or import a validator into another validator in which case that might be the best of both worlds.

Hi @BenTopping @andrewsparkes given that there's only a default_records.yml at config/default_records/pipelines/default_records.yml, is it only the pipelines NovaSeqX PE and NovaSeq 6000 PE that contain custom validations?

@dasunpubudumal The idea for this story it to setup the sequencing pipelines in such a way that allows us to use custom validators for NovaSeqX PE and Novaseq 6000 PE in other stories. If you think the custom validation should be included in this story as well then we can do that but I think the idea is to cover that in https://github.com/sanger/sequencescape/issues/4068 and https://github.com/sanger/sequencescape/issues/3770.
You might be able to create a custom validator now for Novaseq 6000 as I think the work done here should have been just for Novaseq 6000 in reality.
Hopefully that makes sense.

I have created app/validators/batch_validator.rb, which itself is a ActiveRecord::Validator as a standard validator for batch.rb model.

Leaving a note on app/models/pipeline/batch_validation.rb:

This module declares some functions that are reused in pipeline validations.
These functions are used in app/models/batch/pipeline_behaviour.rb module, which is included in app/models/batch.rb. That is, there are additional validations for batch model declared in batch.rb.
-pipeline_behaviour.rb does this by overriding included function which includes additional associations and validations to the model class.

def self.included(base)
  base.class_eval do
    # The associations with the pipeline
    belongs_to :pipeline
    delegate :workflow, :item_limit, to: :pipeline
    delegate :tasks, to: :workflow, allow_nil: true

    # The validations that the pipeline & batch are correct
    validates :pipeline, presence: true

    # Validation of some of the batch information is left to the pipeline that it belongs to
    validate { |record| record.pipeline.validation_of_batch(record) if record.pipeline.present? }

    # The batch requires positions on it's requests if the pipeline does
    delegate :requires_position?, to: :pipeline
  end
end

One possible solution for adding unique validations for specific pipelines:
# frozen_string_literal: true

require 'rails_helper'

module DynamicValidationsTest

  extend ActiveSupport::Concern

  # Add the following in the real logic which is not supported in the test.
  # For it to be supported PipelineX should be an ActiveRecord model.
  #
  # included do
  #   after_initialize do |record|
  #     add_dynamic_validations(record)
  #   end
  # end

  def add_dynamic_validations(record)
    self.class.validates_with record.validator_class_name.constantize
  end

end

# In the business logic, if a pipeline X wants custom validations, it should:
# 0. Add a migration to add attribute validator_class_name to pipelines table
# 1. Implement the custom validator class
# 2. Include the DynamicValidations module
# 3. Call add_dynamic_validations in the initialize method.
class PipelineXValidator < CustomValidatorBase
  def validate(record)
    record.errors.add :base, 'PipelineXValidator failed'
  end
end

class PipelineX
  include ActiveModel::Model
  include ActiveModel::Validations
  include DynamicValidationsTest

  attr_accessor :validator_class_name

  # In real logic, this would be a dynamic list of validations
  # It should be possible to access validator_class_name from the record (because it's in pipelines schema)
  def initialize(validator_class_name)
    # This is not required in the real logic, because it's part of the schema
    @validator_class_name = validator_class_name
    # This is not required in the real logic, because it's called in the after_initialize hook
    add_dynamic_validations(self)
  end

end

RSpec.describe DynamicValidations do
  it 'adds dynamic validations' do
    pipeline = PipelineX.new( 'PipelineXValidator')
    pipeline.valid?
    expect(pipeline.errors[:base]).to include('PipelineXValidator failed')
  end
end

The idea is to declare an attribute (say, validator_class_name) in the pipelines schema, and use that along with constantize. Depending on where the validations are required (whether if it is batch.rb or pipeline.rb, in which both are ApplicationRecord instances), it should give the ability for us to include DynamicValidations mixin into the pipeline model (or, the batch; this would require some modifications) and dynamically add validates_with with the class specified in the pipeline record.


Add a flag to forc contract-id command to show it in bech32 format

Currently forc-contract-id show the contract id in hex format but it is possible that users may want to get in bech32 format as well. We should have a flag for this

Hey, I would like to work on this!

Hey, I would like to work on this!

Sounds great! go for it :) assigned to you

Hey, quick question, I recently tried to modify https://github.com/FuelLabs/sway/blob/master/forc/src/ops/forc_contract_id.rs and I wanted to test my modifications to the command, could you please lead me to the right part of the documentation that would help me modify the forc binary installed to get started on this

Hey, quick question, I recently tried to modify https://github.com/FuelLabs/sway/blob/master/forc/src/ops/forc_contract_id.rs and I wanted to test my modifications to the command, could you please lead me to the right part of the documentation that would help me modify the forc binary installed in my setup to get started on this

Great to hear that you are making progress! You can build your version of forc with cargo build and use forc with absolute path ./target/debug/forc from the root of the sway repo. Or you can remove your current forc installation (if you installed it through cargo check your ./cargo/bin/ or if you installed it from fuelup check your ./fuelup/bin) and install your modified version with cargo install. Also consider opening a PR once you feel like it to start review process.

Hi, I did integrate the flag, I wanted a hint on how the forc contract-id --help command prints out information so that I could integrate a line on --bech32

Hi @kayagokalp could you assist me with this last bit? :)

Hey @ADTmux please open a PR so that i can see your WIP and assist you better. You should add this new flag to  https://github.com/FuelLabs/sway/blob/daee1c247c86038bf9a3faefbca80d0aca4ebf0e/forc/src/cli/commands/contract_id.rs#L18C12-L18C19

@kayagokalp Can we close this since we are removing Bech32 format from the wallet?

Yes that seems reasonable to me :)


[Pop!_OS] Update release links

Old release blog posts of Pop!_OS moved to tumblr

Thanks @bobidle !


Sorry, Mr Xao
That was a mistake...
Could you please discard my Pull Request?

—
Reply to this email directly, view it on GitHub
https://github.com/apache/incubator-nuttx-apps/pull/1096#issuecomment-1080528131,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AV6JHU6YBIKO5YHCBRHFT3TVCGJATANCNFSM5R2XVGAQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

Sure, you can close by yourself through button at bottom right.


Request to add git tag

@Dakkers I was trying to add this library to CDNJS based on the request here https://github.com/cdnjs/cdnjs/issues/12020  . One of the pre-requisites to add a library is to have git tags checked in.  If you could please add the git tags , I can go ahead and send a PR for cdnjs to add this lib.
Thanks!

@austin665 https://github.com/numbers/numbers.js/releases/tag/v0.6.0
Thanks for getting this going! Let me know if there is anything else required..

@sjkaliski Thanks for the quick turnaround. The cdnjs PR was approved and the author will get a notification once it is added to cdnjs. Cheers!


What OS is this for please?

Running the Go install doesn't appear to put the binary on the system anywhere.
Errors on building on Intel Mac Sonoma 14.5
go build
package github.com/netr0m/az-pim-cli
	imports github.com/netr0m/az-pim-cli/cmd
	imports github.com/netr0m/az-pim-cli/pkg/pim
	imports github.com/Azure/azure-sdk-for-go/sdk/azidentity: build constraints exclude all Go files in<EMAIL_ADDRESS>
Tried with no effect
sudo
CGO_ENABLED=1
export GOOS=darwin
export GOARCH=amd64

Hi, thanks for the report. Please provide the output of commands:

go version
go env

It should be OS-independent, though I have only tested it on Linux (Arch) myself.
I also tried to build for MacOS with GOOS=darwin GOARCH=amd64 go build just now, both on my machine and through a Docker container with
docker run -it golang bash
git clone https://github.com/netr0m/az-pim-cli.git
cd az-pim-cli
GOOS=darwin GOARCH=amd64 go build

which both ran without error.
go build should produce a binary in the current working directory, i.e. a file named az-pim-cli. A successful run of that command should not produce any output to the console.
The output from your command;
package github.com/netr0m/az-pim-cli
	imports github.com/netr0m/az-pim-cli/cmd
	imports github.com/netr0m/az-pim-cli/pkg/pim
	imports github.com/Azure/azure-sdk-for-go/sdk/azidentity: build constraints exclude all Go files in<EMAIL_ADDRESS>
indicates that something failed.
A search for 'build constrains exclude all Go files in' got me this answer on StackOverflow, which recommends trying to run go clean -modcache before retrying the go build command.
If this doesn't get you anywhere, please let me know.

Thank you,
Really sorry, didn't think to check Go version as I rarely use it.  I was on v1.17, upgrading to 1.22.3 allowed it to build correctly.
I still couldn't find the binary anywhere using the go install method, not sure whats going on there...
╰─➤  go install github.com/netr0m/az-pim-cli@latest
go: downloading github.com/netr0m/az-pim-cli v0.0.0-20240522110536-57e447247280

thats all it does.

go install installs the binary in $GOPATH/bin;

Executables are installed in the directory named by the GOBIN environment variable, which defaults to $GOPATH/bin or $HOME/go/bin if the GOPATH environment variable is not set.
[from https://pkg.go.dev/cmd/go#hdr-Compile_and_install_packages_and_dependencies]

So, if you've added $GOPATH to your PATH, the command az-pim-cli should be available in your shell.
docker run --rm -it golang bash
root@b89582da6c93:/go# go install github.com/netr0m/az-pim-cli@latest
go: downloading github.com/netr0m/az-pim-cli v0.0.0-20240522110536-57e447247280
go: downloading github.com/spf13/cobra v1.8.0
go: downloading github.com/spf13/viper v1.18.2
go: downloading github.com/spf13/pflag v1.0.5
go: downloading github.com/Azure/azure-sdk-for-go/sdk/azidentity v1.5.2
go: downloading github.com/Azure/azure-sdk-for-go/sdk/azcore v1.11.1
go: downloading github.com/golang-jwt/jwt/v5 v5.2.1
go: downloading github.com/google/uuid v1.6.0
go: downloading github.com/spf13/cast v1.6.0
go: downloading github.com/sagikazarmark/slog-shim v0.1.0
go: downloading github.com/mitchellh/mapstructure v1.5.0
go: downloading github.com/spf13/afero v1.11.0
go: downloading github.com/fsnotify/fsnotify v1.7.0
go: downloading github.com/subosito/gotenv v1.6.0
go: downloading github.com/hashicorp/hcl v1.0.0
go: downloading gopkg.in/ini.v1 v1.67.0
go: downloading github.com/magiconair/properties v1.8.7
go: downloading github.com/pelletier/go-toml/v2 v2.1.0
go: downloading gopkg.in/yaml.v3 v3.0.1
go: downloading golang.org/x/text v0.14.0
go: downloading github.com/Azure/azure-sdk-for-go/sdk/internal v1.5.2
go: downloading golang.org/x/sys v0.18.0
go: downloading github.com/AzureAD/microsoft-authentication-library-for-go v1.2.2
go: downloading golang.org/x/crypto v0.21.0
go: downloading golang.org/x/net v0.23.0
go: downloading github.com/kylelemons/godebug v1.1.0
go: downloading github.com/pkg/browser v0.0.0-20240102092130-5ac0b6a4141c
root@b89582da6c93:/go# which az-pim-cli
/go/bin/az-pim-cli


Added functionality like google photos zooming and swipe to skip

Added swipe gesture on image while pan to zoom is also enabled
Swipe to next and previous image only if image is not zoomed.

i.e., added functionality like google photos zooming and swipe to skip

@manbir-app-curefit A ton of thanks to you for this PR, it saved my lot of effort to implement this feature, I was really struggling for. <3

First of all - Thanks for the contribution.
However, I couldn't make it work and the code is a bit confusing for me to fix.
Also this.animatedScale._value always returns 0 if useNativeDriver set to true, so this should be done some other way to be supported on modern RN versions.
I'm now doing the cleanup for this repo (read more in #129). Using React-native-reanimated is on the roadmap (for the future major version) and these features will be improved. I will close this PR for now, but if you want to contribute please come back in a week when the code is a cleaned up and its a bit more clear what and how to go forward with this package. 🙂


Username format issues

Hi,
Great tool, love it.
Would be nice if you supported usernames in the domain\username format as well as usernames that contain a space. It appears that domain\username becomes domainusername unless you encapsulate it in single quote marks.
However in the brief testing I have performed here passing known good credentials in the domain\username format encapsulated with single quotes seems to always result in a 'No result is found error'.
 Never discount that possibility!

Hi,
As you said if you use username which contains space, it cannot work properly. I have fixed this issue and some bugs. I have just releases a new version. Could you try this one ? if you have any feedback, please let me know.
Thank you for your valuable support. Best regards.

This looks like a great tool, how does it compare to ncrack in speed when doing RDP? Additionally does this work with proxychains?

I am not sure whether the crowbar can work with proxychains or not, but i think it works. Because as far i know how proxychains works, the only thing which you need is the proxy like TOR or any other SOCKS and set the config file. After that you are able to run crowbar with proxychains.
I dont have any experiences about this issue. But if you have experience about this issue, please let me know.


Update zio, zio-test, zio-test-magnolia, ... to 2.1.0 in main

About this PR
📦 Updates

dev.zio:zio
dev.zio:zio-test
dev.zio:zio-test-magnolia
dev.zio:zio-test-sbt

from 2.0.22 to 2.1.0
📜 GitHub Release Notes - Version Diff
Usage
✅ Please merge!
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

⚙ Adjust future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio" } ]

Or, add this to slow down future updates of this dependency:
dependencyOverrides = [{
  pullRequests = { frequency = "30 days" },
  dependency = { groupId = "dev.zio" }
}]

labels: library-update, early-semver-minor, semver-spec-minor, commit-count:1

Superseded by #306.


Q: Expressing content of Aspect about an Object

This question is closed for it contains an error and will be corrected and re-issued.

This question is closed for it contains an error and will be corrected and re-issued by Huibert

This question is closed for it contains an error and will be corrected and re-issued.

@jpalmeida João, As an external user it seems I cannot close the issue, so could you do that for me, please.


Update examples to use "source" jupyter notebooks

One jupyter notebook per module (data_drift, concept_drift)

The jupyter notebook has pretty formatting, in-line display of tables, figures, etc. We should be able to include the html files via sphinx.

[ ] Confirm that including an nbconverted html file is easy to do via sphinx.

Seems to be possible to include notebooks directly via nbsphinx, which will execute the notebooks upon creating the docs.
nbconvert can be used to convert notebooks into notebooks, which would allow us to filter out certain tags from a given notebook and automatically generate a new one. Might end up needlessly elaborate..

[ ] Figure out what all nb_extensions we need and how to include them in the setup.cfg

each jupyter notebook uses the "tag" feature to specify cells corresponding to example (e.g. "all_examples" and "ADWIN" tags)
use nbconvert with the tag option to convert the single jupyter notebook

[ ] Mock up a script that can be added to the pipeline to do this conversion. May be able to base this on an example. Remember to mark this with @pytest.mark.no_cover so that it doesn't inflate the coverage statistics.

[ ] Switch the .py scripts to jupyter, using the tags.

[ ] Update the README and setup.cfg, with instructions on how to use:

default install includes the visualization dependencies necessary to run each example.py script
barebones install is bare minimum dependencies, no visuals.
dev install includes the above, but also sphinx and everything else.
For the non-dev configs, look into not downloading e.g. docs, tests, etc., as they're a waste of bandwidth.

This lets us maintain the examples in jupyter notebooks and have them be pretty, so that someone can just read the documentation and see what stuff does, while also allowing the user to run stuff without forcing them to install jupyter.

It looks like this isn't so easy to do within "a pipeline" proper, since that runner isn't and shouldn't be in a position to write to the repo.
For now, writing up the current scripts as notebooks, and then using nbconvert to spit out .py files and committing both should be sufficient. If they diverge, we can overwrite as we go if needed.
Maybe we can add a README.md to the examples folder that contains the example nbconvert commands.


HIVE-24491 : setting custom job name is ineffective if the tez session pool is configured or in case of session reuse.

What changes were proposed in this pull request?
HIVE-23026 add capability to set tez.job.name but it's not effective if tez session pool manager is configured or tez session reuse. with this change whenever user set tez.job.name, hive will force a new Tez Session instead using the one from the pool.
Why are the changes needed?
without this change setting tez.job.name is not effective if tez session is reuse.
Does this PR introduce any user-facing change?
No
How was this patch tested?
on local reproduce cluster.

+1 LGTM

+1 LGTM


How to perform semantic segmentation with semantic_head?

Hi, @chhluo @BIGWangYuDong
By adding semantic_head, we can introduce semantic segmentation tasks at training time, however there seems to be no tutorial and config that let us output semantic segmentation results at test time as well?
Update:
I found an closed PR, but it did not get pulled.

Sorry for the late reply, we will update docs and other important think ASAP


Wrong width on ios11

Hello now the width is smaller than the button so the image and text cuts off

Hi, this library is actually not supported anymore in iOS 11. You should use UIContextualAction. — If you're interested in updating the code to use this automatically for iOS 11+, please submit a pull-request with your changes.
FYI, you're probably seeing stuff in the log/console warning you about this.

[TableView] Setting a pattern color as backgroundColor of UITableViewRowAction is no longer supported.


Typo on #18

Thank you for contributing! Please confirm the following:

[x] I followed the contributing guidelines: https://github.com/github/explore/blob/master/CONTRIBUTING.md
[x] I have no affiliation with the project I am suggesting (as a maintainer, creator, contractor, or employee).

Which change are you proposing?

[x] Suggesting edits to an existing topic or collection
[ ] Curating a new topic or collection

Editing an existing topic or collection
I'm suggesting these edits to an existing topic or collection:

[ ] Image (and my file is *.png, square, dimensions 288x288)
[x] Content (and my changes are in index.md)

Found a typo on string #018.

Curating a new topic or collection

[ ] I've formatted my changes as a new folder directory, named for the topic or collection as it appears in the URL on GitHub (e.g. https://github.com/topics/[NAME] or https://github.com/collections/[NAME])
[ ] My folder contains a *.png image (if applicable) and index.md
[x] All required fields in my index.md conform to the Style Guide and API docs: https://github.com/github/explore/tree/master/docs

Please replace this line with an explanation of why you think this topic or collection should be curated.

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

Thanks so much for your first contribution; nice catch!  You rock, @kant!


HBASE-22881 Fix non-daemon threads in hbase server implementation (#512)

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
81
Docker mode activated.

_ Prechecks _

+1
dupname
1
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 2 new or modified test files.

_ branch-2.1 Compile Tests _

0
mvndep
15
Maven dependency ordering for branch

+1
mvninstall
310
branch-2.1 passed

+1
compile
144
branch-2.1 passed

+1
checkstyle
178
branch-2.1 passed

+1
shadedjars
244
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
115
branch-2.1 passed

0
spotbugs
85
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
368
branch-2.1 passed

_ Patch Compile Tests _

0
mvndep
18
Maven dependency ordering for patch

+1
mvninstall
291
the patch passed

+1
compile
144
the patch passed

+1
javac
144
the patch passed

+1
checkstyle
27
The patch passed checkstyle in hbase-common

+1
checkstyle
38
The patch passed checkstyle in hbase-client

-1
checkstyle
84
hbase-server: The patch generated 2 new + 166 unchanged - 7 fixed = 168 total (was 173)

+1
checkstyle
27
hbase-thrift: The patch generated 0 new + 10 unchanged - 2 fixed = 10 total (was 12)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
248
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1206
Patch does not cause any errors with Hadoop 2.7.7 2.8.5 or 3.0.3 3.1.2.

+1
javadoc
114
the patch passed

+1
findbugs
418
the patch passed

_ Other Tests _

+1
unit
183
hbase-common in the patch passed.

+1
unit
212
hbase-client in the patch passed.

-1
unit
12667
hbase-server in the patch failed.

+1
unit
187
hbase-thrift in the patch passed.

+1
asflicense
119
The patch does not generate ASF License warnings.

17889

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-558/1/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/558

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 0ac868d48bc1 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-558/out/precommit/personality/provided.sh

git revision
branch-2.1 / 29d168d90f

Default Java
1.8.0_181

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-558/1/artifact/out/diff-checkstyle-hbase-server.txt

unit
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-558/1/artifact/out/patch-unit-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-558/1/testReport/

Max. process+thread count
4812 (vs. ulimit of 10000)

modules
C: hbase-common hbase-client hbase-server hbase-thrift U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-558/1/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.

:broken_heart: -1 overall

Vote
Subsystem
Runtime
Comment

0
reexec
44
Docker mode activated.

_ Prechecks _

+1
dupname
0
No case conflicting files found.

+1
hbaseanti
0
Patch does not have any anti-patterns.

+1
@author
0
The patch does not contain any @author tags.

+1
test4tests
0
The patch appears to include 2 new or modified test files.

_ branch-2.1 Compile Tests _

0
mvndep
15
Maven dependency ordering for branch

+1
mvninstall
383
branch-2.1 passed

+1
compile
135
branch-2.1 passed

+1
checkstyle
185
branch-2.1 passed

+1
shadedjars
311
branch has no errors when building our shaded downstream artifacts.

+1
javadoc
122
branch-2.1 passed

0
spotbugs
96
Used deprecated FindBugs config; considering switching to SpotBugs.

+1
findbugs
417
branch-2.1 passed

_ Patch Compile Tests _

0
mvndep
17
Maven dependency ordering for patch

+1
mvninstall
358
the patch passed

+1
compile
159
the patch passed

+1
javac
159
the patch passed

+1
checkstyle
30
The patch passed checkstyle in hbase-common

+1
checkstyle
43
The patch passed checkstyle in hbase-client

-1
checkstyle
102
hbase-server: The patch generated 2 new + 166 unchanged - 7 fixed = 168 total (was 173)

+1
checkstyle
30
hbase-thrift: The patch generated 0 new + 10 unchanged - 2 fixed = 10 total (was 12)

+1
whitespace
0
The patch has no whitespace issues.

+1
shadedjars
302
patch has no errors when building our shaded downstream artifacts.

+1
hadoopcheck
1520
Patch does not cause any errors with Hadoop 2.7.7 2.8.5 or 3.0.3 3.1.2.

+1
javadoc
123
the patch passed

+1
findbugs
468
the patch passed

_ Other Tests _

+1
unit
189
hbase-common in the patch passed.

+1
unit
224
hbase-client in the patch passed.

+1
unit
8690
hbase-server in the patch passed.

+1
unit
166
hbase-thrift in the patch passed.

+1
asflicense
120
The patch does not generate ASF License warnings.

14675

Subsystem
Report/Notes

Docker
Client=19.03.1 Server=19.03.1 base: https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-558/2/artifact/out/Dockerfile

GITHUB PR
https://github.com/apache/hbase/pull/558

Optional Tests
dupname asflicense javac javadoc unit spotbugs findbugs shadedjars hadoopcheck hbaseanti checkstyle compile

uname
Linux 644c2e8df254 4.15.0-58-generic #64-Ubuntu SMP Tue Aug 6 11:12:41 UTC 2019 x86_64 GNU/Linux

Build tool
maven

Personality
/home/jenkins/jenkins-slave/workspace/HBase-PreCommit-GitHub-PR_PR-558/out/precommit/personality/provided.sh

git revision
branch-2.1 / 3b6f6b623d

Default Java
1.8.0_181

checkstyle
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-558/2/artifact/out/diff-checkstyle-hbase-server.txt

Test Results
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-558/2/testReport/

Max. process+thread count
5005 (vs. ulimit of 10000)

modules
C: hbase-common hbase-client hbase-server hbase-thrift U: .

Console output
https://builds.apache.org/job/HBase-PreCommit-GitHub-PR/job/PR-558/2/console

versions
git=2.11.0 maven=2018-06-17T18:33:14Z) findbugs=3.1.11

Powered by
Apache Yetus 0.10.0 http://yetus.apache.org

This message was automatically generated.


Don't handle requestexception

First, thanks for this library. Came in clutch right when I needed it. It's great!
While I was testing, I fed some wrong data and wrote my own exception handler and was surprised to find out the library handles it itself and prints it. This has a few issues in that I can't handle the exception the way I want to.
https://github.com/aritsulynn/anipie/blob/3d35394f8559c8222edb86b8061a47276a12f81d/anipie/search_by_query.py#L27-L34
My proposed solution is to either raise a custom exception or just remove the try catch so the requestexception propagates to the library user (me) and then I can handle it according to my own needs

Thanks for reporting the issue! I've made a change to search_by_query.py (lines 35-36) that should prevent the error you encountered.
https://github.com/aritsulynn/anipie/blob/3640c97b228d3c0c7c256464c0499a8592910e62/anipie/search_by_query.py#L35C9-L36C21

this still has the same issue, you shouldn't return it but simply let it raise

#3  We got update here to handle the error

That works! Thank you!


Unable to stop a market watcher or Strat runner

Is there any way?

Lurking for a while now: this is a question i can answer easily :)
The documentation states:

Stopping Gekko :  In the command line hold ctrl + c.

It is on the bottom of this page: https://gekko.wizb.it/docs/installation/installing_gekko_on_windows.html

Yeah I can stop the script, but I just want to stop the Strat from running

Ah. I recognize the problem. If you have two Strats running you have to kill both. Somewhere i read this is on the roadmap. I have solved this for now by starting each gekko in a separate directory with their own port. C:\Gekko0=3000, C:\gekko1=3001, enz..  I sometimes copy the database between them or to a third directory to test strategys..

Another way of doing this is saving the PID of each process into the database and then KILL the process you want to remove. You could make a html button to remove each processes. I recommend saving them in the DB because if the main program crashes, the child processes can still be controlled upon restart of the UI program. Of course you would have to check to see if the processes are still running every now and then and remove the ones that are not from the DB but that should be simple.

The UI is very basic for now. This will be properly supported in the next version. See #911 for details :)

I finally got this fixed. See my last comment on #2059.


ruby.sh: allow running on older Ruby versions

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[ ] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew tests with your changes locally?

When installing on a fresh pre-10.15 system, the installer throws an error because /usr/bin/ruby is 2.3.7, but Version.canonical_segments didn't arrive until 2.5.0.
...
 * [new tag]             2.2.7      -> 2.2.7
 * [new tag]             2.2.8      -> 2.2.8
 * [new tag]             2.2.9      -> 2.2.9
HEAD is now at 8e984d621 Merge pull request #7419 from Bo98/audit
-e:1:in `<main>': undefined method `canonical_segments' for #<Gem::Version "2.3.7"> (NoMethodError)
==> Downloading https://homebrew.bintray.com/bottles-portable-ruby/portable-ruby-2.6.3.mavericks.bottle.tar.gz
...

Can you rebase on master to get the workflow changes?


Runs prematurely when using with Travis

https://travis-ci.org/knownasilya/google-maps-markup/jobs/72847801#L397
Seems like it runs before the tests are finished. Not sure what's wrong with my setup.

looks like you don't have a coverage directory (that's the issue I see in that log)
closing - if that's not the issue, feel free to reopen


Tracking PR for release v0.2.0

Draft because done on top of https://github.com/rust-bitcoin/hex-conservative/pull/37
We have a few nice changes, especially #37 when it merges. We can cut a release!

If/when we merge and release this one want to merge #34 and cut a 1.0.0-beta and release?

I forgot I did this, replaced by #64


Update 'ros_environment' to 1.2.1-p0

I've followed this guide step by step carefully. [Yes]

I've tested this package remotely and have excluded all broken builds.
Here is the links to the Travis/AppVeyor with status "All passed":

https://ci.appveyor.com/project/kgeorgiev93/hunter/builds/25007853
https://travis-ci.com/kgeorgiev93/hunter/builds/114133018

Testing:

https://ci.appveyor.com/project/ingenue/hunter/builds/25008980
https://travis-ci.org/ingenue/hunter/builds/540850466?utm_source=github_status&utm_medium=notification

We need a release of hunter in order to progress with https://github.com/ruslo/hunter/issues/1397.

Released:

https://github.com/ruslo/hunter/releases/tag/v0.23.186

just for your info you can pick a random commit like this:
HunterGate(
    URL "https://github.com/ruslo/hunter/archive/76c3fd69bbe742859a006bd28415eeb76093b091.zip"
    SHA1 "9c8c28c56036bea0d3df78268867dfd128a1a076"
)

Released:

https://github.com/ruslo/hunter/releases/tag/v0.23.186

just for your info you can pick a random commit like this:
HunterGate(
    URL "https://github.com/ruslo/hunter/archive/76c3fd69bbe742859a006bd28415eeb76093b091.zip"
    SHA1 "9c8c28c56036bea0d3df78268867dfd128a1a076"
)

Ok, thanks!


Support model merging

Model merging was removed from the main UI with plans to move that functionality to this repo. It was removed because it wasn't a super popular feature and maintaining the routes and fairly complex form UI didn't make sense given the low demand.
The merging logic itself is pretty straightforward: https://github.com/invoke-ai/InvokeAI/blob/main/invokeai/backend/model_manager/merge.py
I imagine/hope it will be pretty straightforward to add a simple Gradio UI for it.
Related issue from main UI repo: https://github.com/invoke-ai/InvokeAI/issues/6241
@RyanJDick Please correct me if I am wrong, but I think we would be happy to review a PR that adds this functionality to the training app.

@RyanJDick Please correct me if I am wrong, but I think we would be happy to review a PR that adds this functionality to the training app.

@psychedelicious Absolutely. I think invoke-training is the right place for that to live.


Exporting in View Mode: Outline resulted outlines to be exported

Expected Behaviour
It should exported the document as seen in View Mode: Normal instead. Another suggestion would be to have View Mode: Outline export as a separate export option (if necessary).
Steps to Reproduce

Switch from View Mode: Normal to View Mode: Outline
Export document
Saved document is in outline mode

Thanks for finding this. It isn't necessary to provide an option to export in outline mode, that wouldn't be helpful to users.

@Keavon I'll work on this


int64 Implementation

@tylerb I removed type switch and here you can find reason why:
http://stackoverflow.com/questions/17220764/go-cast-any-int-value-to-int64-in-type-switch
Any objections? Can I merge this to master?

Coverage increased (+0.04%) to 91.165% when pulling cb34d5160ef673d318675c695158acc2f3aba2e4 on Release into 3438f0879cbf7e5c63c47cde246073b48ffdacfc on master.

Coverage increased (+0.04%) to 91.165% when pulling cb34d5160ef673d318675c695158acc2f3aba2e4 on Release into 3438f0879cbf7e5c63c47cde246073b48ffdacfc on master.

That's fine by me. The main reason I see for making it accept an interface{} is to make it easier to use, but the argument could be made either way. I'm fine with having it accept int64.


Update zip.go

Remove compressed formats check to avoid zip header check exception in java.util.zip.ZipInputStream(only DEFLATED entries can have EXT descriptor)

Sorry, but this seems like a Java problem, not an issue with archiver, which is fully spec-compliant in this matter...


BUG: Setup.py File Contains Python Errors

Issue Description
When I try to run setup.py I get the following error:

File "setup.py", line 20
current_system: Version = parse(platform.mac_ver()[0])
^
SyntaxError: invalid syntax

Minimal Reproducible Example
Run from command line:

`python setup.py install --user`

Traceback
No response
Expected Behavior
No response
Bug report checklist

[X] I have checked that this issue has not already been reported.
[X] I have confirmed this bug exists on the latest release of shap.
[ ] I have confirmed this bug exists on the master branch of shap.
[ ] I'd be interested in making a PR to fix this bug

Installed Versions
The latest version

Hi @JBarsotti , thanks for raising the issue. FYI, calling python setup.py directly has been deprecated for some time now, you may read https://setuptools.pypa.io/en/latest/deprecated/commands.html for more information.
Will close this as a won't fix.


neonKUBE versioning and multi-part image uploads to S3

We need to be able to bump neonKUBE version numbers at will; we've been stuck at neonkube-0.1.0-alpha since the beginning of time.  There are some problems:

[x] We've accumulated multiple version constants over time in both of the neonKUBE and neonCLOUD repos.  We need to consolidate these into a single constant.

[x] openebs-cstor-csi-driver setup image build is failing

We implemented multi-part image uploads as GitHub releases and this was really nice because we did MD5 checks top ensure that the latest version was always downloaded.  Unfortunately, we ran into GitHub rate limits when because cluster setup will not have the user's GitHub credentials available.  So we've reverted to single-part S3 images.  This has been causing lots of confusion because it's very easy to forget to clear the %USERPROFILE%\.neonkube\vm-images folder when deploying clusters.
The solution is to generalize the multi-part downloads so these can be hosted on S3 as well:

[x] Neon.Deployment: Add an AwsCli.UploadMultipartFile() method that uploads a multi-part file to S3 and returns a Download instance.  This will work much the same as GitHubReleaseApt.UploadMultipartAsset().

[x] Add a unit tests

[x] Generalize the GitHubReleaseApi.DownloadAsync() method by relocating it to DeploymentHelper() since this not GitHub Releases specific any more.

[x] Let's deprecate the S3 downloads folder and relocate the the download JSON file as well as the part files to the vm-images folder.  This will look like:
neon-public/vm-images/hyperv/node/
    neonkube-0.1.0-alpha.hyperv.amd64.vhdx.gz.manifest
    neonkube-0.1.0-alpha.hyperv.amd64.vhdx.gz.parts/
        part-0000
        part-0001
        part-0002
        ...

[x] Misc issues

[x] neonCLOUD image publish.ps1 script need to publish the neonKUBE base and service images too
[x] neonKUBE publish.ps1 script is not building neon-acme and neon-cluster-api containers
[x] neon-image build containers needs verify that all of the containers exist in the GHCR registry with the correct tad and are visible to everyone.

JEFF: This ended up being a hardcoded container image tag

[x] The neon-cluster-api service is not deploying correctly.  This container image probably hasn't been rebuild for some time due to the first misc issue above.  We need to remove this service and related database from cluster install and replace it with a CRD and a refactored neon-cluster-operator.

[x] Note that we're going to change the file type for the download from .gz (which is confusing because it isn't actually gzipped) to gz.manifest.  We'll need tweak how image building and cluster prepare works to so that the image name after downloading ends in .gz.  We may already be doing this via the Download.Filename property.

[x] Remove the GitHub neon-image publication options

[ ] neon-image multi-part support

[x] hyperv:

[x] base
[x] node
[x] ready-to-go

[x] WSL2:

[x] base
[x] node

[x] xenserver:

[x] base
[x] node

DONE


fix(NODE-4425): webpack optional import of FLE issue

Description
What is changing?
Move FLE require back into a try catch block.
What is the motivation for this change?
Webpack needs optional requires to be inside of a try catch.
Double check the following

[x] Ran npm run check:lint script
[x] Self-review completed using the steps outlined here
[x] PR title follows the correct format: <type>(NODE-xxxx)<!>: <description>
[ ] Changes are covered by tests
[ ] New TODOs have a related JIRA ticket

Should we add a test for fle to optional_require.test.js?

From slack, decided to follow up with this: https://jira.mongodb.org/browse/NODE-4442


mutex lock when trying to sync new node

How I get to a locked node while syncing
I have a node with 11000 ish blocks
I create a new node (HW) with clean setup (no folders) and generate a new wallet
I added the allready generating nodes address to the gateway list of the new node.
All well when syncing for around 1600 blocks (is not specific)
Then there is a double lock:
Last part of the rivined debug:
t.CoinOutputSum()
0
Demote5041975 /home/niko/go/src/github.com/rivine/rivine/modules/consensus/accept.go 261 true
!Lock5298963 /home/niko/go/src/github.com/rivine/rivine/modules/transactionpool/update.go 21 true
Demote5300958 /home/niko/go/src/github.com/rivine/rivine/modules/transactionpool/update.go 115 true
DemotedUnlock5301004 /home/niko/go/src/github.com/rivine/rivine/modules/transactionpool/update.go 117 true
DemotedUnlock5042158 /home/niko/go/src/github.com/rivine/rivine/modules/consensus/accept.go 266 true
!Lock5041384 /home/niko/go/src/github.com/rivine/rivine/modules/consensus/accept.go 200 true
inputSum
0
t.CoinOutputSum()
0
Demote5041975 /home/niko/go/src/github.com/rivine/rivine/modules/consensus/accept.go 261 true
!Lock5298963 /home/niko/go/src/github.com/rivine/rivine/modules/transactionpool/update.go 21 true
Demote5300958 /home/niko/go/src/github.com/rivine/rivine/modules/transactionpool/update.go 115 true
DemotedUnlock5301004 /home/niko/go/src/github.com/rivine/rivine/modules/transactionpool/update.go 117 true
DemotedUnlock5042158 /home/niko/go/src/github.com/rivine/rivine/modules/consensus/accept.go 266 true
!Lock5041384 /home/niko/go/src/github.com/rivine/rivine/modules/consensus/accept.go 200 true
inputSum
0
t.CoinOutputSum()
0
Demote5041975 /home/niko/go/src/github.com/rivine/rivine/modules/consensus/accept.go 261 true
!Lock5298963 /home/niko/go/src/github.com/rivine/rivine/modules/transactionpool/update.go 21 true
Demote5300958 /home/niko/go/src/github.com/rivine/rivine/modules/transactionpool/update.go 115 true
DemotedUnlock5301004 /home/niko/go/src/github.com/rivine/rivine/modules/transactionpool/update.go 117 true
DemotedUnlock5042158 /home/niko/go/src/github.com/rivine/rivine/modules/consensus/accept.go 266 true
!Lock5041384 /home/niko/go/src/github.com/rivine/rivine/modules/consensus/accept.go 200 true
inputSum
0
t.CoinOutputSum()
0
RLock5138726 /home/niko/go/src/github.com/rivine/rivine/modules/consensus/synchronize.go 182 true
RLock5074045 /home/niko/go/src/github.com/rivine/rivine/modules/consensus/consensusset.go 270 true
RLock5074045 /home/niko/go/src/github.com/rivine/rivine/modules/consensus/consensusset.go 270 true

The prints are done in demotemutex.go but its printing -1 of the stack its on, so printing the place where the mutex lock is called.
When killing the deamon and restarting, It went till the last block and keep synced.

For now I'll take a quick look to see if I can easily pinpoint the problem. If not, then this will probably surface again in the test network with more reliable/up to date info

@nvinken seemed to bump into this one easily, so hopefully you can pinpoint it. Fairly sure that Sia has fixed quite some deadlocks already though, some on purpose, while others by accident. We should probably start merging stuff over slowly but surely, as it might fix some bugs (perhaps including this one).

It seems that i can reproduce this by forcing a call to checkConsistency. Because of another bug (#61), this call eventually starts a panic (in debug builds), which seems to be the culprit.

goroutine 26 [semacquire]:
sync.runtime_Semacquire(0xc4202221b4)
	/usr/local/go/src/runtime/sema.go:56 +0x39
sync.(*RWMutex).RLock(0xc4202221a8)
	/usr/local/go/src/sync/rwmutex.go:50 +0x95
github.com/rivine/rivine/vendor/github.com/NebulousLabs/demotemutex.(*DemoteMutex).RLock(0xc4202221a0)
	/home/lee/go/src/github.com/rivine/rivine/vendor/github.com/NebulousLabs/demotemutex/demotemutex.go:42 +0x3f
github.com/rivine/rivine/modules/consensus.(*ConsensusSet).managedReceiveBlocks.func3(0xc420222000, 0xc4203f9217)
	/home/lee/go/src/github.com/rivine/rivine/modules/consensus/synchronize.go:182 +0x65
panic(0xb4aaa0, 0xc4201a4170)
	/usr/local/go/src/runtime/panic.go:491 +0x2a2
github.com/rivine/rivine/modules/consensus.manageErr(0xc42035e2a0, 0xf3ca00, 0xc4201a4170)
	/home/lee/go/src/github.com/rivine/rivine/modules/consensus/consistency.go:20 +0x6c
github.com/rivine/rivine/modules/consensus.checkCoinCount(0xc42035e2a0, 0xa)
	/home/lee/go/src/github.com/rivine/rivine/modules/consensus/consistency.go:110 +0x843
github.com/rivine/rivine/modules/consensus.(*ConsensusSet).checkConsistency(0xc420222000, 0xc42035e2a0)
	/home/lee/go/src/github.com/rivine/rivine/modules/consensus/consistency.go:176 +0x9f
github.com/rivine/rivine/modules/consensus.(*ConsensusSet).maybeCheckConsistency(0xc420222000, 0xc42035e2a0)
	/home/lee/go/src/github.com/rivine/rivine/modules/consensus/consistency.go:194 +0x7c
github.com/rivine/rivine/modules/consensus.(*ConsensusSet).addBlockToTree.func1(0xc42035e2a0, 0xc1dc08, 0xc42035e2a0)
	/home/lee/go/src/github.com/rivine/rivine/modules/consensus/accept.go:142 +0x12b
github.com/rivine/rivine/vendor/github.com/NebulousLabs/bolt.(*DB).Update(0xc4201f21e0, 0xc4203f8f28, 0x0, 0x0)
	/home/lee/go/src/github.com/rivine/rivine/vendor/github.com/NebulousLabs/bolt/db.go:595 +0xc2
github.com/rivine/rivine/modules/consensus.(*ConsensusSet).addBlockToTree(0xc420222000, 0x453f489db813076c, 0x33453e65533e9638, 0xea683f259c72862f, 0xa921b66e865e4da7, 0x5a7887ca, 0xa, 0x0, 0x0, 0xc4201f1140, ...)
	/home/lee/go/src/github.com/rivine/rivine/modules/consensus/accept.go:136 +0x191
github.com/rivine/rivine/modules/consensus.(*ConsensusSet).managedAcceptBlock(0xc420222000, 0x453f489db813076c, 0x33453e65533e9638, 0xea683f259c72862f, 0xa921b66e865e4da7, 0x5a7887ca, 0xa, 0x0, 0x0, 0xc4201f1140, ...)
	/home/lee/go/src/github.com/rivine/rivine/modules/consensus/accept.go:252 +0x1df
github.com/rivine/rivine/modules/consensus.(*ConsensusSet).managedReceiveBlocks(0xc420222000, 0xf46cc0, 0xc42021c4c0, 0x0, 0x0)
	/home/lee/go/src/github.com/rivine/rivine/modules/consensus/synchronize.go:212 +0x4b2
github.com/rivine/rivine/modules/consensus.(*ConsensusSet).(github.com/rivine/rivine/modules/consensus.managedReceiveBlocks)-fm(0xf46cc0, 0xc42021c4c0, 0xb606c0, 0xc4202402e0)
	/home/lee/go/src/github.com/rivine/rivine/modules/consensus/synchronize.go:389 +0x56
github.com/rivine/rivine/modules/gateway.(*Gateway).managedRPC(0xc4201ba420, 0xc42019db20, 0x10, 0xbf7d06, 0xa, 0xc4202042b0, 0x0, 0x0)
	/home/lee/go/src/github.com/rivine/rivine/modules/gateway/rpc.go:57 +0x28b
github.com/rivine/rivine/modules/gateway.(*Gateway).RPC(0xc4201ba420, 0xc42019db20, 0x10, 0xbf7d06, 0xa, 0xc4202042b0, 0x0, 0x0)
	/home/lee/go/src/github.com/rivine/rivine/modules/gateway/rpc.go:67 +0xdf
github.com/rivine/rivine/modules/consensus.(*ConsensusSet).threadedInitialBlockchainDownload.func1(0xc420222000, 0xc4203f9eb8, 0xc4203f9e28, 0xc4203f9e30, 0x0, 0x0)
	/home/lee/go/src/github.com/rivine/rivine/modules/consensus/synchronize.go:520 +0x1b0
github.com/rivine/rivine/modules/consensus.(*ConsensusSet).threadedInitialBlockchainDownload(0xc420222000, 0x0, 0x0)
	/home/lee/go/src/github.com/rivine/rivine/modules/consensus/synchronize.go:546 +0x1e0
github.com/rivine/rivine/modules/consensus.New.func1(0x1, 0xc4201a42d0, 0xc420222000, 0xf46f40, 0xc4201ba420)
	/home/lee/go/src/github.com/rivine/rivine/modules/consensus/consensusset.go:155 +0x59b
created by github.com/rivine/rivine/modules/consensus.New
	/home/lee/go/src/github.com/rivine/rivine/modules/consensus/consensusset.go:148 +0xf26

Note that no panic message seems to be written to the terminal where the daemon was started

It seems like this (https://github.com/rivine/rivine/blob/master/modules/consensus/accept.go#L200) is the offending lock, deeper in the callstack it might call checkConsistency, which currently fails due to another bug. Upon failure in debug mode, causing the lock to never unlock. Running a non debug build indeed prints the error without locking up

After fixing #61, it seems like this is probably not related after all, so the root cause will need to be examined again

I seem to be unable to reproduce this bug at the moment (building from master), so I'll just let this rest for now.

unable to reproduce for now


deis apps:destroy isn't fully removing contents from etcd

When an integration test failed mid-run, I tried restarting the test and found that even though deis apps reported an empty list:
~/code/rigger :  deis apps
=== Apps

there was still application specific data in etcd:
core@ip-xxxxx ~ $ etcdctl ls /deis/services/
/deis/services/testing
/deis/services/configsample
/deis/services/buildsample

And directories weren't necessarily empty either:
core@ip-xxxxx ~ $ etcdctl ls /deis/services/testing
/deis/services/testing/testing_v2.web.1
core@ip-xxxxx ~ $ etcdctl ls /deis/services/configsample
/deis/services/configsample/configsample_v7.web.1
core@ip-xxxxx ~ $ etcdctl ls /deis/services/buildsample

Failed to push deis master after deis apps:create, and delete the git manually:
$ vagrant ssh deis-01 -- -A
$ nse deis-builder
$ rm -rf home/git/zircon-tinkerer
still found the app by deis apps:list

closing this as it's not a serious issue, and we've removed reliance on etcd in deis v2.


Getting Initialize Error when loading CET

CET Version: fix 1 for game version 1.61 (12th of nov release date)
Cyberpunk version: 1.61
OS: Windows 10
Description:
My game launches fine, however CET does not appear to be loading properly, you will see the error "42120" in the log file that I provide. Please note that this was done on a fresh install of CP2077 & Vortex. I installed the mod through nexus & vortex.
Config: There doesn't appear to be a config.json file in my "cyber_engine_tweaks" directory.
Log: cyber_engine_tweaks.log

Just tried to launch again, here is the updated .log file:
cyber_engine_tweaks.log

After checking the discord, it appears that CET is not yet updated for the most recent patch. Closing this issue.

same question.
so how to reslove?


Configurable fluid tank capacity

Description
Added option to change the fluid capacity of fluid tanks

seams i messed up something

okay from what i see to get this syncing properly on servers this would requre a rewrite of the fluid tanks witch i am to dumb to do so i am just going to leave this here if someone wants to pick it up and finish it. the config is there i just dont know how to sync the capacity over to the client

@davidCMs should we consider this PR as abandoned ?
Also, do explain what parts for tank needs refactoring.

I just made a the additions to the configs but i don't know how to make it work in multiplayer so as far as i know the tank classes need refactoring to sync the max capacity with the client but i am not familiar enough with forge to do that, i have looked at how the max energy config is done but i don't entirely understand how that works. I don't plan on editing this further i just left it here in case someone knows how to make it work in multiplayer so they have the configs all ready made .


OptionParser::InvalidOption: invalid option: --sourcemap=none

I'm using gulp-ruby-sass version 1.0.1 with a single configuration and not source map ({sourcemap: false} and I'm getting the follow error:
gulp-ruby-sass stderr: OptionParser::InvalidOption: invalid option: --sourcemap=none
any idea?

Check out closed issues and the readme. Does your version of Sass meet the version requirements of this plugin?

My bad. I should look into close issue first. I'm using a old sass version. Thanks too much @robwierzbowski :+1:

No problem :).

OptionParser::InvalidOption: invalid option: --exclude-ruby-options=includePaths
Use --trace for backtrace.
How can in fix this error

OptionParser is part of the Sass gem. It looks like you're passing
something to the gem that it doesn't understand.
I'm not sure what that option is, but you might try include-paths.
On Friday, October 30, 2015, srinivas<EMAIL_ADDRESS><javascript:_e(%7B%7D,'cvml','notifications@github.com');>> wrote:

OptionParser::InvalidOption: invalid option:
--exclude-ruby-options=includePaths
Use --trace for backtrace.
How can in fix this error
—
Reply to this email directly or view it on GitHub
https://github.com/sindresorhus/gulp-ruby-sass/issues/220#issuecomment-152550144
.

--
Rob Wierzbowski
@robwierzbowski http://twitter.com/#!/robwierzbowski
http://github.com/robwierzbowski
http://robwierzbowski.com

If I run sass -h to get Sass command line options I don't see exclude-ruby-options.
gulp-ruby-sass understands a few custom options (documented in the readme) and Sass options.

Updating Sass gem solved it for me :+1:


Retention service hangs and does not remove old shards

Under certain conditions, the retention service can become hung waiting on a shard's reference count to drop to zero. When this happens, no other shards can be removed by the retention service. This can eventually result in high disk usage.
The attached goroutine trace shows a system exhibiting the issue. The retention service is stuck on waiting on the WaitGroup used to indicate that the references to the shard have dropped to zero.
goroutine.txt

Can you create port issues for all the repos and branches, @gwossum ?


Updating spelling and grammar in the spelling and grammar section

Pointed out by Timmoneer, there were a couple of spelling mistakes in the spelling and grammar section!

🤦♂


Update .openpublishing.publish.config.json

Docs Build status updates of commit 368f24d:
:x: Validation status: errors
Please follow instructions here which may help to resolve issue.

File
Status
Preview URL
Details

.openpublishing.publish.config.json
:x:Error

Details

.openpublishing.publish.config.json

[Error]

Publish service's config file: .openpublishing.publish.config.json is not valid. Details: System.ArgumentException: Invalid json string ---> Newtonsoft.Json.JsonReaderException: After parsing a value an unexpected character was encountered: ". Path 'docs_build_engine', line 57, position 1.
   at Newtonsoft.Json.JsonTextReader.ParsePostValue()
   at Newtonsoft.Json.JsonTextReader.Read()
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.PopulateObject(Object newObject, JsonReader reader, JsonObjectContract contract, JsonProperty member, String id)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.CreateObject(JsonReader reader, Type objectType, JsonContract contract, JsonProperty member, JsonContainerContract containerContract, JsonProperty containerMember, Object existingValue)
   at Newtonsoft.Json.Serialization.JsonSerializerInternalReader.Deserialize(JsonReader reader, Type objectType, Boolean checkAdditionalContent)
   at Newtonsoft.Json.JsonSerializer.DeserializeInternal(JsonReader reader, Type objectType)
   at Newtonsoft.Json.JsonConvert.DeserializeObject(String value, Type type, JsonSerializerSettings settings)
   at Newtonsoft.Json.JsonConvert.DeserializeObject[T](String value, JsonSerializerSettings settings)
   at Microsoft.OpenPublishing.Build.Common.JsonUtility.FromJsonString[T](String value) in d:\a\1\s\Libraries\Common\JsonUtility.cs:line 93
   --- End of inner exception stack trace ---
   at Microsoft.OpenPublishing.Build.Common.JsonUtility.FromJsonString[T](String value) in d:\a\1\s\Libraries\Common\JsonUtility.cs:line 97
   at Microsoft.OpenPublishing.Build.WorkflowTasks.SyncGitSourceWithDownloadingPackage.CheckPublishConfig() in d:\a\1\s\Libraries\WorkflowTasks\SyncGitSourceWithDownloadingPackage.cs:line 68

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Docs Build status updates of commit 7d10bcb:
:warning: Validation status: warnings

File
Status
Preview URL
Details

mixed-reality-docs/mrlearning-asa-ch4.md
:warning:Warning
View
Details

.openpublishing.publish.config.json
:white_check_mark:Succeeded

mixed-reality-docs/mrlearning-asa-ch4.md

Line 172: [Warning] Invalid file link: 'images/Module2chapter4step24im.png'.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.