Enable the new model serialization for recoverry service backup

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

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


[Prototype] Institution details

Please note: This is a draft PR, do not merge.
Related to https://github.com/cfpb/sbl-frontend/issues/72
Changes

Removed History of changes
Initial implementation of Institution Details page

Preview
LIVE PREVIEW DEPLOYMENT
Screenshots (Updated 12/6/23)

@meissadia - I see updates in Figma, need to apply those to the mockup

Great to see this in the app!


How to merge class prototype into one object?

Here is a test class below:
class Animal {
  name: string;
  constructor(name: string) {
    this.name = name;
  }
  sayHi(): string {
    return `My name is ${this.name}`;
  }
  sayHello(): string {
    return `hello`;
  }
}

It will compile to:
var Animal = /** @class */ (function () {
    function Animal(name) {
        this.name = name;
    }
    Animal.prototype.sayHi = function () {
        return "My name is " + this.name;
    };
    Animal.prototype.sayHello = function () {
        return "hello";
    };
    return Animal;
}());

Because of "prototype" is a keywords in javascript ,  it will not uglify. Whether a complier options for tsc to merge class prototype together,  just like below:
var Animal = /** @class */ (function () {
  function Animal(name) {
    this.name = name;
  }
  var _pro = {
    sayHi: function () {
      return "My name is " + this.name;
    },
    sayHello: function () {
      return "hello";
    }
  };
  //__extends  is typescript complie function
  __extends(Animal.prototype, _pro);
  return Animal;
}());

In my project, it find almost 5k words "prototype" in tsc compiler products , if I can do above , it may save many size.

Other tools depend on looking for assignments like this to do other stuff; we can't really change it. With the vanishing number of ES5 runtimes, it's not worth adding a compiler option for.
Do remember that if you're gzipping your JS, the actual cost of repeated uses of the same sequence of characters is much smaller than it might seem.


Paring down MeasureBase

The current MeasureTheory/MeasureBase partitioning is kind of ad hoc. What we really need is for MeasureBase to contain only

Whatever is needed for defining new measures
Anything else needed to avoid type piracy

The biggest source of code will be the need to specify base measures. For example, MeasureBase needs to have ProductMeasure, or people won't be able to define anything having a product as a base measure.
Let's identify things not required by the above criteria and discuss moving them to MeasureTheory, to allow MeasureBase to be lighter-weight.

Here are some details of the current state, with some ideas for where to go next. Not complete yet, I'll add more details soon
Measures
DensityMeasure
Constructed using ∫. For example, given a measure α and a function f, μ = ∫(f, α) builds a measure μ with density f and base-measure α
PointwiseProductMeasure
Constructed using ⊙. Takes a "prior" measure μ and a Likelihood ℓ, and builds a new measure representing the posterior. This is mathematically equivalent to ∫(ℓ, μ), but in terms of our implementation there's a difference in the base measures. More specifically,
basemeasure(∫(ℓ, μ)) == μ
basemeasure(μ ⊙ ℓ) == basemeasure(μ)

Affine
Represents a pushforward of a measure on ℝⁿ through an affine transformation.
RestrictedMeasure
μ = restrict(f, base) takes f as a predicate for the support. This is like a truncated distribution, but "truncate" has the connatation of renormalization. The implementation is simple:
struct RestrictedMeasure{F,M} <: AbstractMeasure
    f::F
    base::M
end

@inline function logdensity(d::RestrictedMeasure, x)
    d.f(x) || return -Inf
    return 0.0
end

function density(d::RestrictedMeasure, x)
    d.f(x) || return 0.0
    return 1.0
end

Half
Starting with a symmetric univariate measure, this gives a new measure restricted to the half-line. Like RestrictedMeasure, but more efficient.
SuperpositionMeasure
Very much like mixture distributions, but without the reweighting. There are subtleties that come up here for determining the base measure; see the paper for details. Our implementation of this is not yet complete.
SpikeMixture
Superposition of a Dirac with a Lebesgue-dominated measure. Useful for building spike and slab priors, and used in Moritz's "sticky zigzag" sampler.
FactoredBase
It's very common for a log-density with respect to a primitive measure to be sum of three kinds of terms:

Data-dependent
Parameter-dependent
Constant

In addition, the support is often restricted by some predicate.
FactoredBase tries to put all of this base-measure information in one place
struct FactoredBase{R,C,V,B} <: AbstractMeasure
    inbounds::R  # A predicate for membership in the support
    constℓ::C    # A constant
    varℓ::V      # A nullary function (takes no args) carrying parameter-dependent terms
    base::B      # The base measure
end

@inline function logdensity(d::FactoredBase, x)
    d.inbounds(x) || return -Inf
    d.constℓ + d.varℓ()
end

For example, here's how this can be used for Half:
unhalf(μ::Half) = μ.parent

@inline function basemeasure(μ::Half)
    inbounds(x) = x > 0
    constℓ = logtwo
    varℓ() = 0.0
    base = basemeasure(unhalf(μ))
    FactoredBase(inbounds, constℓ, varℓ, base)
end

I think this is kind of nice, but I'm not yet sure it's the "right" way to set up base measures. We still need to weigh some tradeoffs to get to an approach to advocate as idiomatic.
Kernel
Abstractly, a kernel is a function mapping each value in the domain to a measure. But functions are opaque, and it can be important for us to have more information available statically. So we separate this into two components. In Kernel(f, ops),

ops maps values (in whatever space) to the measure's "parameters". Exactly what is considered a parameter is measure-dependent. For convenience, ops can also be a named tuple of functions.
f uses the result of ops to construct the measure. f is typically a UnionAll, but it can also be a generic function.

For example, a Normal approximation to a Poisson could be represented as any of
k1 = λ -> Normal(λ, λ^2)
k2 = kernel(k1)
k3 = kernel(Normal, λ -> (μ=λ, σ=λ^2))
k4 = kernel(Normal) do λ (μ=λ, σ=λ^2) end
k5 = kernel(Normal, (μ = identity, σ = λ -> λ^2))

The information available statically roughly increases at each step (k4 is the exception)
ProductMeasure
This takes a kernel and an array, and returns an abstraction representing the kernel applied to each value. For example,
myprod = ProductMeasure(k, rand(10))

where k is any Kernel above.
TupleProductMeasure
Same, but for tuples
WeightedMeasure
Scale a measure by some positive constant
ParamWeightedMeasure
Similar to a special case of FactoredBase. Not yet in use. Part of exploration to find a good way to represent base measures of parametric measures.
struct ParamWeightedMeasure{L,N,T,B} <: AbstractWeightedMeasure
    ℓ::L
    par::NamedTuple{N,T}
    base::B
end

basemeasure(d::ParamWeightedMeasure) = d.base

logdensity(d::ParamWeightedMeasure, x) = d.ℓ(d.par)

Lebesgue
"Volume" measure. This will probably be refactored to
struct Lebesgue{T} <: PrimitiveMeasure
    dimension :: T
end

Then dimension could be ::Int or ::StaticInt
CountingMeasure
The counting measure of a set is its cardinality. Unless Lebesgue, this will probably never be used directly, but only as a base measure. So we could have
struct CountingMeasure <: PrimitiveMeasure end

Dirac
A point mass, with Dirac(x) ≪ CountingMeasure().
TrivialMeasure
The measure for which every set has measure zero. This is the identity element for superposition.
For any measure μ,
TrivialMeasure() ≪ μ ≪ CountingMeasure()

Measure-Related
Density
AffineTransform
Likelihood
Domains
IntegerRange
RealInterval
Utilities
MapsTo
Iterable
NonIterable
Outdated
Exp
Integral


Show values for each column (data point)

Hey guys!
I am searching for a functionality whether it exists. Is it possible to show values for each data point? I am also using the stacked bar chart (with additional line chart applied on it) so I would like to show the value for each data point for these two bar data sets (excluding the Line chart)
The app is made with Ionic 2 (Angular2) and it seems, that I don't have all of the possibilites to call different helpers provided by Chart class. I see that a lot of examples include such things. So how can I call helpers from Chart class?
Thank you very much in advance!

This has been asked many times. We have a sample file that shows how to do this. :smile:


[http] display the jitter

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

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

🏷 Feature Request Type
UI Feature
🔖 Feature description
Print the jitter for http / ping probe for given period
✔ Solution
Max latenci - min latenci = jitter
❓ Alternatives
No response
📝 Additional Context
No response

ping is tracked in #1724 => have reworded the issue to only inlcude this


Adding few links for better accessibility

Links are a great way to direct the audience to the actual place.
Adding Medium and The Conferences link will definitely make the platform more accessible.

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


Use AppId function to delete orphaned extension data

Problem: Before apps not installed since 14.x might be missing a package ID. So we are unable to delete them by packageID
Fix: Delete by AppId

@microsoft-github-policy-service agree company="Microsoft"

@microsoft-github-policy-service agree company="Microsoft"


Nuget Release fails

[12:35:59 PM] [semantic-release] › ℹ  Running semantic-release version 23.0.0
(node:26) ExperimentalWarning: Importing JSON modules is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)
[12:36:01 PM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "@semantic-release/changelog"
[12:36:01 PM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "@semantic-release/gitlab"
[12:36:01 PM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "@semantic-release/npm"
[12:36:01 PM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "@semantic-release/git"
[12:36:01 PM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "semantic-release-presets/plugins/ms-teams"
[12:36:01 PM] [semantic-release] › ✔  Loaded plugin "verifyConditions" from "semantic-release-presets/plugins/nuget"
[12:36:01 PM] [semantic-release] › ✔  Loaded plugin "analyzeCommits" from "@semantic-release/commit-analyzer"
[12:36:01 PM] [semantic-release] › ✔  Loaded plugin "generateNotes" from "@semantic-release/release-notes-generator"
[12:36:01 PM] [semantic-release] › ✔  Loaded plugin "prepare" from "@semantic-release/changelog"
[12:36:01 PM] [semantic-release] › ✔  Loaded plugin "prepare" from "semantic-release-replace-plugin"
[12:36:01 PM] [semantic-release] › ✔  Loaded plugin "prepare" from "@semantic-release/npm"
[12:36:01 PM] [semantic-release] › ✔  Loaded plugin "prepare" from "@semantic-release/git"
[12:36:01 PM] [semantic-release] › ✔  Loaded plugin "prepare" from "semantic-release-presets/plugins/nuget"
[12:36:01 PM] [semantic-release] › ✔  Loaded plugin "publish" from "@semantic-release/gitlab"
[12:36:01 PM] [semantic-release] › ✔  Loaded plugin "publish" from "@semantic-release/npm"
[12:36:01 PM] [semantic-release] › ✔  Loaded plugin "publish" from "semantic-release-presets/plugins/nuget"
[12:36:01 PM] [semantic-release] › ✔  Loaded plugin "addChannel" from "@semantic-release/npm"
[12:36:01 PM] [semantic-release] › ✔  Loaded plugin "success" from "@semantic-release/gitlab"
[12:36:01 PM] [semantic-release] › ✔  Loaded plugin "success" from "semantic-release-presets/plugins/ms-teams"
[12:36:01 PM] [semantic-release] › ✔  Loaded plugin "fail" from "@semantic-release/gitlab"
[12:36:01 PM] [semantic-release] › ✔  Loaded plugin "fail" from "semantic-release-presets/plugins/ms-teams"
[12:36:03 PM] [semantic-release] › ✔

[REDACTED]

[12:36:03 PM] [semantic-release] › ✔  Allowed to push to the Git repository
[12:36:03 PM] [semantic-release] › ℹ  Start step "verifyConditions" of plugin "@semantic-release/changelog"
[12:36:03 PM] [semantic-release] › ✔  Completed step "verifyConditions" of plugin "@semantic-release/changelog"
[12:36:03 PM] [semantic-release] › ℹ  Start step "verifyConditions" of plugin "@semantic-release/gitlab"
[12:36:03 PM] [semantic-release] [@semantic-release/gitlab] › ℹ

[REDACTED]

[12:36:06 PM] [semantic-release] › ✔  Completed step "verifyConditions" of plugin "@semantic-release/gitlab"
[12:36:06 PM] [semantic-release] › ℹ  Start step "verifyConditions" of plugin "@semantic-release/npm"
[12:36:06 PM] [semantic-release] › ✔  Completed step "verifyConditions" of plugin "@semantic-release/npm"
[12:36:06 PM] [semantic-release] › ℹ  Start step "verifyConditions" of plugin "@semantic-release/git"
[12:36:06 PM] [semantic-release] › ✔  Completed step "verifyConditions" of plugin "@semantic-release/git"
[12:36:06 PM] [semantic-release] › ℹ  Start step "verifyConditions" of plugin "semantic-release-presets/plugins/ms-teams"
[12:36:06 PM] [semantic-release] › ✔  Completed step "verifyConditions" of plugin "semantic-release-presets/plugins/ms-teams"
[12:36:06 PM] [semantic-release] › ℹ  Start step "verifyConditions" of plugin "semantic-release-presets/plugins/nuget"
NuGet Command Line
<IP_ADDRESS>
[12:36:07 PM] [semantic-release] › ✔  Completed step "verifyConditions" of plugin "semantic-release-presets/plugins/nuget"
[12:36:07 PM] [semantic-release] › ℹ  Found git tag v1.7.2 associated with version 1.7.2 on branch main
[12:36:07 PM] [semantic-release] › ℹ  Found 15 commits since last release
[12:36:07 PM] [semantic-release] › ℹ  Start step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: fix(nuget): bump dependency versions
[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The release type for the commit is patch
[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: chore(npm): bump husky and configure, remove obsolete file
[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: chore(release): 1.7.3

[REDACTED]

[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: fix(project): merge branch 'renovate/all-minor-patch' into 'main'

chore(deps): update all non-major dependencies

[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The release type for the commit is patch
[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: chore(deps): update all non-major dependencies
[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: chore(project): merge branch 'renovate/all-minor-patch' into 'main'

chore(deps): update all non-major dependencies

[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: fix(deps): update all non-major dependencies
[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The release type for the commit is patch
[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: chore(project): merge branch 'renovate/all-minor-patch' into 'main' [skip ci]

chore(deps): update all non-major dependencies

[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: chore(deps): update all non-major dependencies
[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: chore(project): merge branch 'renovate/all-minor-patch' into 'main' [skip ci]

chore(deps): update dependency dotnet-reportgenerator-globaltool to v5.2.1

[REDACTED]

[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: chore(deps): update dependency dotnet-reportgenerator-globaltool to v5.2.1
[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: chore(project): merge branch 'renovate/all-minor-patch' into 'main' [skip ci]

chore(deps): update all non-major dependencies

[REDACTED]

[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: chore(deps): update all non-major dependencies
[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: chore(project): merge branch 'renovate/all-minor-patch' into 'main' [skip ci]

chore(deps): update all non-major dependencies

[REDACTED]

[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analyzing commit: chore(deps): update all non-major dependencies
[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  The commit should not trigger a release
[12:36:07 PM] [semantic-release] [@semantic-release/commit-analyzer] › ℹ  Analysis of 15 commits complete: patch release
[12:36:07 PM] [semantic-release] › ✔  Completed step "analyzeCommits" of plugin "@semantic-release/commit-analyzer"
[12:36:07 PM] [semantic-release] › ℹ  The next release version is 1.7.3
[12:36:07 PM] [semantic-release] › ℹ  Start step "generateNotes" of plugin "@semantic-release/release-notes-generator"
[12:36:07 PM] [semantic-release] › ✔  Completed step "generateNotes" of plugin "@semantic-release/release-notes-generator"
[12:36:07 PM] [semantic-release] › ℹ  Start step "prepare" of plugin "@semantic-release/changelog"

[REDACTED]

[12:36:07 PM] [semantic-release] › ✔  Completed step "prepare" of plugin "@semantic-release/changelog"
[12:36:07 PM] [semantic-release] › ℹ  Start step "prepare" of plugin "semantic-release-replace-plugin"
[12:36:07 PM] [semantic-release] › ✔  Completed step "prepare" of plugin "semantic-release-replace-plugin"
[12:36:07 PM] [semantic-release] › ℹ  Start step "prepare" of plugin "@semantic-release/npm"

[REDACTED]

[12:36:07 PM] [semantic-release] › ✔  Completed step "prepare" of plugin "@semantic-release/npm"
[12:36:07 PM] [semantic-release] › ℹ  Start step "prepare" of plugin "@semantic-release/git"
[12:36:07 PM] [semantic-release] [@semantic-release/git] › ℹ  Found 1 file(s) to commit
[12:36:11 PM] [semantic-release] [@semantic-release/git] › ℹ  Prepared Git release: v1.7.3
[12:36:11 PM] [semantic-release] › ✔  Completed step "prepare" of plugin "@semantic-release/git"
[12:36:11 PM] [semantic-release] › ℹ  Start step "generateNotes" of plugin "@semantic-release/release-notes-generator"
[12:36:11 PM] [semantic-release] › ✔  Completed step "generateNotes" of plugin "@semantic-release/release-notes-generator"
[12:36:11 PM] [semantic-release] › ℹ  Start step "prepare" of plugin "semantic-release-presets/plugins/nuget"
[12:36:11 PM] [semantic-release] [semantic-release-presets/plugins/nuget] › ℹ

[REDACTED]

Package source with Name: gitlab added successfully.
[12:36:11 PM] [semantic-release] [semantic-release-presets/plugins/nuget] › ℹ  Packing with configuration Release.
  Determining projects to restore...
  Restored /builds/[REDACTED].csproj (in 8.95 sec).
  Restored /builds/[REDACTED].csproj (in 8.95 sec).
/usr/share/dotnet/sdk/8.0.201/Sdks/NuGet.Build.Tasks.Pack/buildCrossTargeting/NuGet.Build.Tasks.Pack.targets(221,5): error NU5026: The file '/builds/[REDACTED].dll' to be packed was not found on disk. [/builds/[REDACTED].csproj]
[12:36:22 PM] [semantic-release] [semantic-release-presets/plugins/nuget] › ✘  Error: Command failed with exit code 1: dotnet pack --configuration Release --output output --nologo
    at makeError (file:///usr/lib/node_modules/execa/lib/error.js:60:11)
    at handlePromise (file:///usr/lib/node_modules/execa/index.js:124:26)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async default (file:///usr/lib/node_modules/semantic-release-presets/plugins/nuget/prepare.js:31:5)
    at async validator (file:///usr/lib/node_modules/semantic-release/lib/plugins/normalize.js:36:24)
    at async file:///usr/lib/node_modules/semantic-release/lib/plugins/pipeline.js:38:36
    at async file:///usr/lib/node_modules/semantic-release/lib/plugins/pipeline.js:32:5
    at async pluginsConfigAccumulator.<computed> [as prepare] (file:///usr/lib/node_modules/semantic-release/lib/plugins/index.js:87:11)
    at async run (file:///usr/lib/node_modules/semantic-release/index.js:202:3)
    at async Module.default (file:///usr/lib/node_modules/semantic-release/index.js:278:22)
[12:36:22 PM] [semantic-release] › ✘  Failed step "prepare" of plugin "semantic-release-presets/plugins/nuget"
[12:36:22 PM] [semantic-release] › ℹ  Start step "fail" of plugin "@semantic-release/gitlab"
[12:36:22 PM] [semantic-release] [@semantic-release/gitlab] ›

[REDACTED]

[12:36:22 PM] [semantic-release] › ✔  Completed step "fail" of plugin "@semantic-release/gitlab"
[12:36:22 PM] [semantic-release] › ℹ  Start step "fail" of plugin "semantic-release-presets/plugins/ms-teams"
[12:36:24 PM] [semantic-release] [semantic-release-presets/plugins/ms-teams] › ℹ  Message sent to Microsoft Teams
[12:36:24 PM] [semantic-release] › ✔  Completed step "fail" of plugin "semantic-release-presets/plugins/ms-teams"
[12:36:24 PM] [semantic-release] › ✘  EDOTNET_PACK_FAILED dotnet pack failed with exit code 1
dotnet pack --configuration Release --output output --nologo

SemanticReleaseError: dotnet pack failed with exit code 1
    at default (file:///usr/lib/node_modules/semantic-release-presets/plugins/nuget/prepare.js:41:11)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async validator (file:///usr/lib/node_modules/semantic-release/lib/plugins/normalize.js:36:24)
    at async file:///usr/lib/node_modules/semantic-release/lib/plugins/pipeline.js:38:36
    at async file:///usr/lib/node_modules/semantic-release/lib/plugins/pipeline.js:32:5
    at async pluginsConfigAccumulator.<computed> [as prepare] (file:///usr/lib/node_modules/semantic-release/lib/plugins/index.js:87:11)
    at async run (file:///usr/lib/node_modules/semantic-release/index.js:202:3)
    at async Module.default (file:///usr/lib/node_modules/semantic-release/index.js:278:22)
    at async default (file:///usr/lib/node_modules/semantic-release/cli.js:55:5) {
  code: 'EDOTNET_PACK_FAILED',
  details: 'dotnet pack --configuration Release --output output --nologo',
  semanticRelease: true,
  pluginName: 'semantic-release-presets/plugins/nuget'
}section_end:1708346195:step_script

False positive due to misconfiguration of project.


internal/scylla: add err codes mapping to metadata

Fixes #50
The codes.txt is created by copying the text content of the following element:
//*[@id="swagger-ui"]/section/div[2]/div[2]/div[1]/section/div/div/div/div/pre/code/text()

From the following document:
https://api.cloud.scylladb.com/docs/swagger.json

Tested by creating a cluster with already taken name:
Plan: 1 to add, 0 to change, 0 to destroy.

Do you want to perform these actions?
  Terraform will perform the actions described above.
  Only 'yes' will be accepted to approve.

  Enter a value: yes

scylladbcloud_cluster.scylladbcloud: Creating...
╷
│ Error: error creating cluster: Error "040703": Cluster name is already used (http status 200, url "https://app-api-tfe2e.ext.dev.scylla.cloud/account/1/cluster")
│
│   with scylladbcloud_cluster.scylladbcloud,
│   on main.tf line 37, in resource "scylladbcloud_cluster" "scylladbcloud":
│   37: resource "scylladbcloud_cluster" "scylladbcloud" {
│
╵


uv pip compile removes via -r requirements.in

I found this kind pretty useful to immediately see which entries in requirements.txt come from direct dependencies, and to also see which ones are both direct and transitive ones.
To reproduce:

Clone https://github.com/indico/indico/ (or get the requirements* files)
Run uv pip compile requirements.in -o requirements.txt
See the (partial) diff below:

diff --git a/requirements.txt b/requirements.txt
index e376581100..b2eae90d3f 100644
--- a/requirements.txt
+++ b/requirements.txt
@@ -1,40 +1,26 @@
-#
-# This file is autogenerated by pip-compile with Python 3.9
-# by the following command:
-#
-#    pip-compile --strip-extras
-#
+# This file was autogenerated by uv v0.1.0 via the following command:
+#    uv pip compile requirements.in -o requirements.txt
 alembic==1.12.1
-    # via
-    #   -r requirements.in
-    #   flask-migrate
+    # via flask-migrate
 amqp==5.2.0
     # via kombu
 asttokens==2.4.1
     # via
     #   sentry-sdk
     #   stack-data
-async-timeout==4.0.3
-    # via redis
 attrs==23.1.0
     # via
     #   jsonschema
     #   referencing
 authlib==1.2.1
-    # via -r requirements.in
 babel==2.13.1
-    # via
-    #   -r requirements.in
-    #   flask-babel
+    # via flask-babel
 bcrypt==4.0.1
-    # via -r requirements.in
 billiard==4.2.0
     # via celery
 bleach==6.1.0
-    # via -r requirements.in
[...]

Especially while this tool is new it also makes it MUCH harder to compare output from pip-tools and uv, since there's lots of noise in the diff from this.

Not removing it would also allow for something similar to ruff's ecosystem checks. Not sure if such checks exist atm (I found some issues related to them but no actual code)...

The lack of the -r requirements.in in the output has been a blocker on using uv to replace pip-compile in some projects I work on.  Glad to see this already on the radar.

FYI, I'm (slowly) having a bit of of a poke at this one. @charliermarsh I'm assuming you'd be interested in PRs for this one right?

Yeah happily. Let me know if you run into issues or have questions.

@charliermarsh (and anyone else interested): https://github.com/astral-sh/uv/pull/3269 is a first draft at this. It has the major redeeming feature that it works (i.e. does the requested item here), but there's a stack of unresolved questions in the PR that need figuring out.
Also, it's needed some fairly chunky changes overall, and there's probably at least some stylistic changes that are wanted (although I tried to keep to the same style as the surrounding code)!

Will be supported in the next version thanks to @palfrey.

Thank you @palfrey - this will make dependabot updates so much less annoying


GraphQL intropection: The server introspection response cannot be parsed as a valid JSON object.

GraphQL intropection: The server introspection response cannot be parsed as a valid JSON object.
how to fix it ? i don't know.

I am getting the same error for remote schema https://api.monday.com/v2/get_schema It seems it gets HTML page instead the JSON and therefore it is not able to parse it.
I have no idea why, even simple curl https://api.monday.com/v2/get_schema gets me the right JSON file without any extra parameters or headers being provided.

Update: using http:// instead of https:// allowed me to move forward...


feat: default to no confirmation prompts for CLI commands

The CLI commands all printed confirmation prompts for the various flags
they exposed. This commit modifies that logic, so that there is no longer
a -y flag, but instead a --confirm or -c flag for each command, and
prompts are only displayed if using this flag. In most cases, the derived
values are printed even if not prompted for.
In call cases where the user is prompted, I have removed the "Verbose"
prompt, as that seems less like a configuration option that needs to be
confirmed, and more like just a CLI option for the current run which we
can just accept as-is.
The text for the prompts has also been reduced to one or two words.
Also added are some checks around image naming and repositories, short
circuiting failures that could occur if these are not specified or are
unknown. For example, if a user does faas init and then faas deploy
we don't yet know what the image name should be - one hasn't been built.
Fixes: https://github.com/boson-project/faas/issues/91
Fixes: https://github.com/boson-project/faas/issues/90
Fixes: https://github.com/boson-project/faas/issues/89

@lance is envvar FAAS_CONFIRM really used anywhere?

@lance is envvar FAAS_CONFIRM really used anywhere?

Well, not explicitly. But neither was FAAS_YES :laughing:. However, you could set it in your environment to have all commands generate prompts.
faas on  lance/reverse-confirm-logic [$?] via 🐹 v1.14.4 took 3s
❯ set -x FAAS_CONFIRM true                                                                                3360ms  Fri 11 Sep 2020 10:07:17 AM EDT

faas on  lance/reverse-confirm-logic [$?] via 🐹 v1.14.4
❯ mkdir test-fn                                                                                Fri 11 Sep 2020 01:21:59 PM EDT

faas on  lance/reverse-confirm-logic [$?] via 🐹 v1.14.4
❯ ./faas init -p ./test-fn -l node                                                                                Fri 11 Sep 2020 01:22:09 PM EDT
Project path (./test-fn):
Project name (test-fn.faas.boson-project.github.com):
Runtime (node):
Trigger (http):

faas on  lance/reverse-confirm-logic [$?] via 🐹 v1.14.4 took 3s
❯                                                                                3545ms  Fri 11 Sep 2020 01:22:28 PM EDT


feat: undeploy-my-kibana

What
An initial attempt to move away from a finer-grained token and use ephemeral tokens.
Further details
It's difficult to migrate https://github.com/elastic/apm-pipeline-library/tree/main/.github/actions/undeploy-my-kibana to use the GH App ephemeral tokens.
It requires different permissions to access the members of a given org, so it can add an extra validation if the PR author is a member of Elastic.
I decided to remove that because it will require further complicated code, and the GitHub labels filtering in the workflows are good enough:

https://github.com/elastic/kibana/blob/8d83a075f6228bb5a6e35a9bb4654fe29cee0cff/.github/workflows/undeploy-my-kibana.yml#L21

Interestingly, e2e tests work but production workflow doesn't work:

https://github.com/elastic/kibana/actions?query=is%3Afailure

Run tibdex/github-app-token@3beb63f4bd073e61482598c45c71c1019b59b73a
  with:
    app_id: ***
    private_key: ***
    permissions: {
    "contents": "read",
    "issues": "write"
  }
    repositories: ["observability-test-environments"]
    github_api_url: https://api.github.com
    installation_retrieval_mode: repository
    installation_retrieval_payload: elastic/kibana
    revoke: true
Error: Could not create installation access token.
    at createInstallationAccessToken (file:///home/runner/work/_actions/tibdex/github-app-token/3beb63f4bd073e614[8](https://github.com/elastic/kibana/actions/runs/11223820283/job/31199282113?pr=195312#step:2:9)2598c45c71c101[9](https://github.com/elastic/kibana/actions/runs/11223820283/job/31199282113?pr=195312#step:2:10)b59b73a/dist/main/index.js:9:86267)
    at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
    at async file:///home/runner/work/_actions/tibdex/github-app-token/3beb63f4bd073e61482598c45c71c[10](https://github.com/elastic/kibana/actions/runs/11223820283/job/31199282113?pr=195312#step:2:11)19b59b73a/dist/main/index.js:9:87518
    at async run (file:///home/runner/work/_actions/tibdex/github-app-token/3beb63f4bd073e61482598c45c71c1019b59b73a/dist/main/index.js:9:888[11](https://github.com/elastic/kibana/actions/runs/11223820283/job/31199282113?pr=195312#step:2:12))
    at async file:///home/runner/work/_actions/tibdex/github-app-token/3beb63f4bd073e6[14](https://github.com/elastic/kibana/actions/runs/11223820283/job/31199282113?pr=195312#step:2:15)82598c45c71c1019b59b73a/dist/main/index.js:9:87468 {
  [cause]: Error: Could not retrieve installation.
      at retrieveInstallationId (file:///home/runner/work/_actions/tibdex/github-app-token/3beb63f4bd073e61482598c45c71c1019b59b73a/dist/main/index.js:9:87232)
      at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
      at async createInstallationAccessToken (file:///home/runner/work/_actions/tibdex/github-app-token/3beb63f4bd073e61482598c45c71c1019b59b73a/dist/main/index.js:9:86069)
      ... 2 lines matching cause stack trace ...
      at async file:///home/runner/work/_actions/tibdex/github-app-token/3beb63f4bd073e61482598c45c71c1019b59b73a/dist/main/index.js:9:87468 {
    [cause]: RequestError [HttpError]: Not Found
        at file:///home/runner/work/_actions/tibdex/github-app-token/3beb63f4bd073e61482598c45c71c1019b59b73a/dist/main/index.js:1:64431
        at process.processTicksAndRejections (node:internal/process/task_queues:95:5)
        at async retrieveInstallationId (file:///home/runner/work/_actions/tibdex/github-app-token/3beb63f4bd073e61482598c45c71c1019b59b73a/dist/main/index.js:9:87014)
        at async createInstallationAccessToken (file:///home/runner/work/_actions/tibdex/github-app-token/3beb63f4bd073e61482598c45c71c1019b59b73a/dist/main/index.js:9:86069)
        at async file:///home/runner/work/_actions/tibdex/github-app-token/3beb63f4bd073e61482598c45c71c1019b59b73a/dist/main/index.js:9:875[18](https://github.com/elastic/kibana/actions/runs/11223820283/job/31199282113?pr=195312#step:2:19)
        at async run (file:///home/runner/work/_actions/tibdex/github-app-token/3beb63f4bd073e61482598c45c71c10[19](https://github.com/elastic/kibana/actions/runs/11223820283/job/31199282113?pr=195312#step:2:20)b59b73a/dist/main/index.js:9:88811)
        at async file:///home/runner/work/_actions/tibdex/github-app-token/3beb63f4bd073e61482598c45c71c1019b59b73a/dist/main/index.js:9:87468 {
      status: 404,
      response: [Object],
      request: [Object]
    }
  }
}

I cannot understand what's the different between these two:

https://github.com/elastic/oblt-actions/actions/runs/11213506268/job/31166699157?pr=140

Run tibdex/github-app-token@3beb63f4bd073e61482598c45c71c1019b59b73a
  with:
    app_id: ***
    private_key: ***
    permissions: {
    "contents": "read",
    "issues": "write"
  }
    repositories: ["observability-test-environments"]
    github_api_url: https://api.github.com/
    installation_retrieval_mode: repository
    installation_retrieval_payload: elastic/oblt-actions
    revoke: true

unless the checkout step is somehow related ?!

aha
https://github.com/tibdex/github-app-token/blob/3eb77c7243b85c65e84acfa93fdbac02fb6bd532/action.yml#L11-L20

and it works as expected now
https://github.com/elastic/kibana/actions/runs/11231085849/job/31219753582?pr=190211


Weird issue

ok just had a weird issue
I'm on V0.0.61
I have set up for expansion sort
I search for armor and click a piece from Shadowlands to sell it and it sold
The issue was all my armor disappeared from my bags
It didn't sell it(checked the buyback tab)
Had to reload game to see it again
I tried to reproduce it by selling another piece after reload but I couldn't so this is just a heads up that it happened

I just pushed a bug fix that I think might resolve this. I'm going to close this, but if you can reproduce it, please re-open this.
Thanks!


cleanup stats vs usage

The 'agent_git' tool has been refactored to 'defAgent' with a simplified interface. Verify that the documentation reflects the correct usage and that examples are updated to match the new interface.


Jdbc Type handler does not match the website information

I use jdbcType to specify the Entity properties type when writing SQL in Mapper file. I reference website for the long type specified jdbcType is LONG INTEGER. But I found that the actual jdbcType should be BIGINT, please correct it in time.

Please give the example code or xml file?

Could you send a pull request?
The xdoc files are in the site directory.

Sure, When I write a Mapper as follow:
<select id="selectById" parameterType="long" resultType="User">
     SELECT
     <include refid="columns" />
     FROM `user`
     <where>
     	`id` = #{id, jdbcType=LONG INTEGER}
     </where>
</select>

JDBC type refer to typeHandler:

But it show the error info :
...
Caused by: java.lang.IllegalArgumentException: No enum constant org.apache.ibatis.type.JdbcType.LONG INTEGER
	at java.lang.Enum.valueOf(Enum.java:238)
	at org.apache.ibatis.type.JdbcType.valueOf(JdbcType.java:25)
	at org.apache.ibatis.builder.BaseBuilder.resolveJdbcType(BaseBuilder.java:71)
	... 60 more

So I found JdbcType and should be replace with BIGINT

@mybatis Sorry, I just close this issues accidentally. Could you help me reopen it!

FYI, jdbcType is optional and is rarely necessary.
And if you specify jdbcType, it should be the actual column type defined in the database, not the one that is documented.
Anyway, I agree that "BIGINT" is better than "LONG INTEGER" here, so a pull request is welcome!

Similarly, I think better that "SHORT INTEGER" change to "SMALLINT".

@JamesMung
Thanks for your reporting! I've fixed this.


fix: differentiate Action / Trigger / Recognizer from custom schema

Description
fixes #2946
Previously, custom Triggers / Recognizers were incorrectly grouped as Custom actions.
This PR implements a stricter schema $role filter to differentiate Adatpive Action / Trigger / Recognizer.
As an example, I have a custom $kind Microsoft.CustomResource.

When it's declared as IDialog, it appears under the 'Custom actions' label.

When it's declared as ITrigger or other type, it won't be recognized as a custom action.

Task Item

Screenshots

Coverage increased (+0.04%) to 57.196% when pulling 8c471c31d1c2ac4256267035cfcb1063466cc9e1 on yeze322:visual/idialog-filter into e157b0f498f6c6e648ab7e16dbf4881a6bee7d10 on microsoft:main.


Build problems for sources with names start with number.

Find any bundle having source started with number:
brfss for example:
name, title	dest_table_name, ...
2013, 2013, 2013, ...

try to build:
bambry -i d034003 ingest
bambry -i d034003 build

File "/tmp/ambry/build/cdc.gov/brfss-0.0.3/code/casters/2013.py", line 6
def 2013_id_0(v, i_s, i_d, header_s, header_d, row, row_n, errors, scratch, accumulator, pipe, bundle, source):
^
SyntaxError: invalid syntax

As a workaround, just change the name. "2014" isn't informative enough anyway, so "brfss2014" is probably better,


Add license to .java file

This change is

Reviewed 3 of 4 files at r1.
Review status: 3 of 4 files reviewed at latest revision, 1 unresolved discussion.

vaadin-icons/src/main/java/com/vaadin/icons/VaadinIcons.java, line 2 at r1 (raw file):

/*
 * Copyright 2000-2017 Vaadin Ltd.

Looks logically correct to me, but will this pass checkstyles in the framework repository?

Comments from Reviewable

Review status: 3 of 4 files reviewed at latest revision, 1 unresolved discussion.

vaadin-icons/src/main/java/com/vaadin/icons/VaadinIcons.java, line 2 at r1 (raw file):
Previously, hesara (Henri Sara) wrote…
Looks logically correct to me, but will this pass checkstyles in the framework repository?

It won't. Looks like we need to upgrade all license headers there.

Comments from Reviewable

Reviewed 1 of 4 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


feat(core): add applied_time_extras to QueryObject

🏆 Enhancements
Add applied_time_extras to QueryObject to be able to identify which filters have been set/overridden by extra_filters.

Thanks @pkdotson !

Thanks for comments @ktmud , I'll add some more context to make this clearer and do the suggested code improvements. This is something that is needed to be able to complete the p0 filter indicator feature (filter indicators will otherwise not work with the chart data endpoint). I envision this and other related structures, namely how ad-hoc filters are transformed into simple filters + static wheres and havings will need to change soon when we start working on native filter components. Therefore I was hoping to make this slightly simpler so that we don't have to do a much more comprehensive refactor of this code up front.

I'm not sure what applied_extra_filters is meant to be used for. Is it a mapping to column names?

@suddjian and @ktmud thanks for your comments, I did my best to address them. I added a link to the incubator-superset PR, which implements these changes for the new chart data endpoint (also implements the same for the legacy endpoint).


Error with MySQL v5.5

When trying to create a dump on a system with (admittedly way too old) MySQL Version 5.5 the tool is exiting with error message:
[ERROR] mysqldump: unknown option '--no-tablespaces'
Would it be possible to provide a fix for this?
Thanks and keep up the amazing work! 👍

With version v2.5.5 a database version check is implemented and the option '--no-tablespaces' will be ignored for mysql < v5.6.


updated SUPPORTED_COINS to most recent list.  Moved it to bottom of f…

…ile for future similar commits.
Description

Updated SUPPORTED_COINS to latest from https://api.coingecko.com/api/v3/coins/list .
Moved SUPPORTED_COINS to bottom of file for future similar commits.

Copilot

copilot:all

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


Ensure that binding file name is always unique to avoid name conflict during deployment

When adding a binding file as an application resource, modify the bindings XML file name from PortBindings.xml to [BizTalkAppName].PortBindings.xml so that the filename remains unique when multiple Deployment Framework projects are deployed to the same BizTalk group.
This work item was migrated from CodePlex
CodePlex work item ID: '4771'
Assigned to: 'tfabraham'
Vote count: '1'

[UnknownUser@2/10/2010]
Resolved with changeset 36196.

[UnknownUser@2/21/2013]

[UnknownUser@5/16/2013]


Is it possible to implement Windows Desktop GPU Support using the ANGLE library?

Please correct me if I'm wrong about anything. My understanding of MediaPipe is limited :)
From what I've read, MediaPipe only supports GPU acceleration on Linux, Android, iOS, and the web. I want to create an application using the hand tracking demo which can run on Windows with a desktop GPU. However, it is not supported. I believe that by using the already-built ANGLE library, along with MediaPipe's OpenGL ES 3.1 backend, it is possible to implement Windows desktop support through OpenGL ES 3.1 emulation. Is this feasible, or is there something I'm missing? Thanks.

Unfortunately, MediaPipe doesn't support Windows yet.

I am aware of that. I was wondering if it was possible to port it to Windows using ANGLE myself.

To future visitors, yes it is possible. Angle can be used as the GL ES implementation. I was able to get it running on a windows machine with vulkan backend being used for Angle. In mediapipe source aside from GL ES itself, there are a few calls to the p_thread api as well that have to be changed, but it's trivial to replace them with std::thread equivalents.

That answers my question. Thank you!

If anyone's interested here's how I changed mediapipe source to work with gpu on windows: angle vulkan, pthread refactor. Besides this there's a couple more compilation errors in the tensorflow library gpu code when compiling with msvc but they are simple syntax replacements. Note that these changes will likely only work on Windows.
I also faced an issue with angle-vulkan on my machine where GLSyncWait call doesn't work as intended with GL_SYNC_FLUSH_COMMANDS_BIT flag. Manually adding a glFlush before the wait fixed the issue.

I have successfully run Face Detection model on Windows with Angle + Vulkan, as @ashikns has suggested.
However, I have experienced slower (..) inference using gl delegate on Face Detection than XNNPACK delegated graph by a large margin. Luckily, using OpenCL resulted in a slightly faster inference time, but still slower than XNNPACK.
I am wondering if there are others who has run TfLite on Windows with Vulkan + Angle combination have experienced slower inference time than running the graph with XNNPACK delegate. Any conjectures over this issue would be appreciated.
(The device I am using is Nvidia 3080 laptop GPU, if this helps.)

@songwoh For the windows platform specifically I ended up converting the tflite model to onnx and running it against native winml. I had to ditch mediapipe at that point since writing a winml calculator was too much effort for me.

@ashikns What was the primary reason for converting to winml inference engine instead of using TfLite? Did you experience the same performance issues as I have?

Why is this issue closed when Windows (and also MacOS) GPU support isn't added yet? On these platforms it would be of great benefit for performance in different app use-cases. Does anyone have any update on plans for Mediapipe Windows/MacOS GPU support?


Rich Presence not updating when state and details not set

Hi !
Calling DiscordRpc.updatePresence(DiscordRichPresence)  on a presence that has neither details nor state has no effect. Indeed, if these properties are not set (or empty) then Discord is not updated.
Since Discord's developer documentation seems to indicate that all fields are optional when updating a presence, I assume that it is a bug related to this implementation.
I can reproduce the bug by taking the example SimpleGame.java and commenting one of the lines that set the details or the state (on lines 91, 92).
Does someone have an idea about how to resolve this issue ? I'm on Windows, by the way.

I think that I've found why !
Currently, the JSON sent to Discord contains the state and details fields, even when they are empty. For instance, the following presence:
discordRichPresence.setState("Doing something");
discordRichPresence.setStartTimestamp(System.currentTimeMillis() / 1000);
discordRpc.updatePresence(discordRichPresence);

leads to the following JSON:
{
   "nonce":"1",
   "cmd":"SET_ACTIVITY",
   "args":{
      "pid":15228,
      "activity":{
         "state":"Doing something",
         "details":"",
         "timestamps":{
            "start":1524398662
         },
         "instance":false
      }
   }
}

and Discord displays neither the state nor the elapsed time.
However, if we avoid empty unspecified fields and generate the JSON as follows:
{
   "nonce":"1",
   "cmd":"SET_ACTIVITY",
   "args":{
      "pid":968,
      "activity":{
         "state":"Doing something",
         "timestamps":{
            "start":1524398370
         },
         "instance":false
      }
   }
}

then Discord shows the state and the elapsed time as expected.
That's kind of strange: I would expect Discord to handle empty fields. I'll do further tests and will submit a PR if this fix works well.


Interactive / Life TypeScript code samples for 2.0

🚀 Feature
I have used Docusaurus 2.0 for documenting Hookstate - supercharged useState hook library for all possible state management needs. Docusaurus 2.0 was all very nice and working smoothly, although it was only alpha version. Thanks for this great quality!
One feature I would like to have built-in into Docusaurus is interactive / life Typescript code samples. You can see what I mean in this page: there is a code snippet and after this is life interactive example running.
Because this feature was not available in the Docusaurus, I have implemented PreviewSample component to do it for me. The limitation of this custom solution is that source code for samples is effectively in separate files, which I need to load asynchronously from github when in runtime.
If it was available in Docusaurus, I would be able to achieve the same result by posting source code within the content of markdown files and annotating, which code samples should be turned into life. Not sure about the syntax, but maybe the following would work (notice -life suffix):
// my code sample here

Have you read the Contributing Guidelines on issues?
yes
Motivation
I would like to retire my custom Typescript source code preview sample component and use more of the standard Docusaurus, which will likely be better styled, built, etc. I hope it will allow me to return code samples back to MD files.
Pitch
(Please explain why this feature should be implemented and how it would be used.)
As you can see this feature is used almost on every page of the documentation for Hookstate. And I feel (and others confirmed) it makes the docs a magnitude better: clearer, easier, more concise. - It is what Typescript lib developers need for sure.

We do have some support for live editing - Have you seen this - https://v2.docusaurus.io/docs/markdown-features#interactive-code-editor

Yeh, I have forgotten that I have tried it some time ago. I abandoned to use after I could not make it working for me. The main problems were:

it did not work with external libraries (like import)
I could not use it with typescript
I could not disable editor mode (wanted view only, no edit), but it was minor
Also I needed to fold down source code or life view (because some of the samples are rendering large page, so I though 'hide sample' was important, but can live without it)

If 1 and 2 has changed recently, I would try it again.

I have changed the title and the description of the ticket to target Typescript specifically.

Alright so I was writing a new issue for this because I NEED Typescript on Docusaurus, but since there's already an issue here, I will write it as a comment here.

Right now we are using react-live to render React components live (at least in v2, I'm not sure about v1), and react-live does not support components in written in Typescript by default, as @avkonst has put it very clearly.
As mentioned by https://github.com/FormidableLabs/react-live/issues/8#issuecomment-613444102, it is easily possible to integrate Typescript. However I know that we very much care about bundle sizes.
So I guess we could add one boolean prop to know if the live code is using Typescript or something like that to either:

conditionally import Typescript compiler, or
dynamically attach <script src="https://klesun-misc.github.io/TypeScript/lib/typescriptServices.js"></script> inside <head>.

Please let me your thoughts 🙏🏼  @yangshun @slorber @lex111

If there is no quick progress on discussion for now.. I will write a simple plugin for this because i really need it.

@9oelM thanks for your suggestion. I won't be able to work on this soon so you'd rather try to make a plugin or submit a PR

@slorber thanks for the reply :) I will submit a PR soon.

Live editing + TypeScript are almost never going to work together, because this inevitably means porting the entire Babel runtime into the bundle, which isn't affordable for the Docusaurus core. There are TypeScript-optimized code blocks like shiki-twoslash, and if anyone really wants a live one, it would be doable in userland in a similar way we implemented the live codeblock, but I don't think it's worth adding in the core considering the inevitable overhead.


GNU PREREQ Error with gcc 9.3.0

Describe what you want to achieve.
I am trying to run some production code with gcc 9.3.0 in Cygwin(64bit) and want to get it compile successfully. My same code runs fine with gcc version 4.8.x, but not with the latest gcc version.
Below error i am getting continously in cygwin console.
/usr/include/_ansi.h:24:19: error: missing binary operator before token "("
24 | #if __GNUC_PREREQ (3, 3)
|                   ^
/usr/include/_ansi.h:72:19: error: missing binary operator before token "("
72 | #if __GNUC_PREREQ (3, 1)
Describe what you tried.
i have tried many ways and even searched in google to fix that issue, but nothing helped me.
Describe which system (OS, compiler) you are using.
I have windows 10 machine with 64bit Cygwin and gcc/g++ installed is 9.3.0 version.
Describe which version of the library you are using (release version, develop branch).
gcc - 9.3.0
g++ 9.3.0
please help me, it's been 10days i am trying every way to fix this

Maybe one of your head file name in your code is the same as the name of a file in the gcc 9.3.0 in Cygwin.

thanks :) .. there's one more error i am encoutering
Error"../../../../ut/CppUTest/include/CppUTestExt/MockSupport.h:40: error: default argument for ‘MockFailureReporter* failureReporterForThisCall’ has type ‘void*’
Here's the Prototype of function
MockSupport& mock(const SimpleString& mockName = "", MockFailureReporter* failureReporterForThisCall = NULL);
Defination
MockSupport& mock(const SimpleString& mockName, MockFailureReporter* failureReporterForThisCall)
{
MockSupport& mock_support = (mockName != "") ? *global_mock.getMockSupportScope(mockName) : global_mock;
mock_support.setActiveReporter(failureReporterForThisCall);
return mock_support;
}
MockSupport::MockSupport()
: strictOrdering_(false), standardReporter_(&defaultReporter_), ignoreOtherCalls_(false), enabled_(true), lastActualFunctionCall_(NULL), tracing_(false)
{
setActiveReporter(NULL);
}
MockSupport::~MockSupport()
{
}
I am totally clue less what's this error is ?

I can see no connection to this library.


Doc Improvement: FastAPI Deployment Section

First Check

[X] I added a very descriptive title to this issue.
[X] I used the GitHub search to find a similar issue and didn't find it.
[X] I searched the FastAPI documentation, with the integrated search.
[X] I already searched in Google "How to X in FastAPI" and didn't find any information.
[X] I already read and followed all the tutorial in the docs and didn't find an answer.
[X] I already checked if it is not related to FastAPI but to Pydantic.
[X] I already checked if it is not related to FastAPI but to Swagger UI.
[X] I already checked if it is not related to FastAPI but to ReDoc.

Commit to Help

[X] I commit to help with one of those options 👆

Example Code
URL to issue: https://fastapi.tiangolo.com/deployment/manually/

Description
This doc section needs improvement: Not A Bug - Probably an ellipsis :)
Someone can rectify this while working on something else and push it all together:

Head over to: https://fastapi.tiangolo.com/deployment/manually/
Now navigate to Run A Server Manually -Uvicorn, then to Run the Server Program

Operating System
Linux
Operating System Details
No response
FastAPI Version
0.75.0
Python Version
3.10.0
Additional Context
No response

What do you want to change in docs?

What do you want to change in docs?

Just a minor change:
Addition of "Run" in-between, 'You can' and ' then ...' as seen in the attached screenshot.
I don't intend to change it. I was hoping if someone is working on another issue can as well rectify that word omission and ship the changes altogether.

There's already PR https://github.com/tiangolo/fastapi/pull/4629
Thanks for reporting :)

There's already PR #4629
Thanks for reporting :)

Awesome 👍


[Edit Profile] The User can not add a city and country just from the drop-down list

Environment: Windows 10 Pro, Google Chrome (116.0.5845.96)
Reproducible: always
Build found: 23.08.2023
Steps to reproduce

Go to https://www.greencity.social/#/profile
Sing in as user
Open 'My space' page
Click on the 'Edit profile icon near the photo
Enter the 'Lviv' value into the 'City' text field.

Actual result
The drop-down list is not shown. The 'Lviv' value was entered in the 'City' text field.
Expected result
The drop-down list is shown, where the user can choose the 'Lviv, Ukraine' value.
User story and test case links
User story #1102
GC-7827

Bug is not resolved, the drop-down list is not shown


Using firebase

Anyone have any luck running firebase. I kept receiving errors that the firebase app had already been initialized. Does this have something to do with SSR? Whenever a hard refresh was done it would throw this error. I loaded my firebase config in the pages/index.js file and then called firebase.initializeApp(config).

@knipferrc This example uses firebase, it may help you https://github.com/now-examples/next-news

@impronunciable maybe we should add an example for firebase, since it's pretty well know 😄

Yes I still think it would be quite helpful to centralize examples, now they're a bit spread around:

https://github.com/zeit/next.js/tree/master/examples
https://github.com/now-examples/next-news
https://github.com/zeit/nextgram
?

Or at least link them all from a single place.

Might be good to add a open source example apps section. I know you did a lot of work on relate.now.sh @sedubois, nextgram is the official example app, and next-news is a side project from @rauchg, which serves as a really good example of a production app 👍. I made next-episode which is also a small sample app.

Oh yes and there's also the examples listed in this issue: https://github.com/zeit/next.js/issues/727

@rauchg @nkzawa @arunoda what's your opinion on adding a open projects sections?

@timneutkens I think it's better if we keep them in a wiki or in a awesome-nextjs list.
BTW: There's already an awesome next.js list here: https://github.com/unicodeveloper/awesome-nextjs
May be we could link to that list from our README. (Better to do it the top of the README)

@arunoda Ah, great idea. I didn't know someone made an awesome list already 💯 Will add it.

I think in order to make nextjs become more attractive to those that are new to web development, it is a good idea to include some examples and short tutorials for how to connect and use a database. How can you create realtime apps with nextjs?

@arashsa i feel like the problems with examples ist, that they have to be maintained and the more examples you have the more likely it is that they end up hanging around outdated in the main repository. I feel like a wiki list is the better approach as you can simply remove and add links.
@knipferrc I'm currently working on a short firebase+next.js tutorial series: https://blog.mvp-space.com/next-js-meets-firebase-and-mobx-ii-f89a6bbe7521#.5uw4ar4x8 feel free to check it out(till now it's just authentication - on monday a data subscription part will be added).

Just added pr #1476, curious what you all think about my approach. I'm a new to Firebase so I might be missing some things.

I posted this in another issue, but posting here as well - I also have a firebase+next.js example, that uses firebase-admin on the server. It renders firebase data both on the server and the client. next-example

How can I deploy to firebase?

@rebelliard did you manage to deploy it to firebase? Do you init the firebase project in the .next folder, and choose the 'dist' folder as your build?

I've been working on a solution to this Next.js on Firebase for the last month or so. Sorry I haven't posted here sooner, but I had some issues stopping me from posting. Here's my solution https://github.com/jthegedus/firebase-functions-next-example and an accompanying blog post (as part of my series) that explains how I got this all working. I had help from @geovanisouza92 and collaborated on partial solution late last month here serverless-firebase

Are there more examples of Next.js + Firebase? Preferrably using Redux?
I've tried using Next.js with both react-redux-firebase and react-rebase but I think both require serious tinkering to get to work with Next.js.
The Next-News example feels a bit verbose in structure, a framework would be nice.
I found this tutorial that uses Next.js + Firebase + Mobx: https://blog.mvp-space.com/next-js-meets-firebase-and-mobx-b3ae90d5b879 (note: series of articles).

@tomsoderlund As I found with the Next.js hosted with Firebase Hosting getting the examples to be small enough to be digestible and prove the point at the same time is hard. It's going to be difficult to make an example using Redux, Firebase and Next.js that isn't verbose in structure. The required knowledge to understand all aspects of what is happening in such an example would be quite high. Implementing them each yourself by composing what you find from each of the individual examples will give a complete understanding of how they work together and a structure you desire. Since I'm personally heading down the Firebase, GraphQL, Next.js & Apollo pathway I won't be implementing the libraries you mention in any examples.
This is an older example I could find using Redux with Firebase - https://medium.com/@prescottprue/firebase-with-redux-82d04f8675b9

@jthegedus Thanks!
The article you mention doesn't use Next.js though. I've had no problems with react-redux-firebase nor react-rebase with create-react-app, but I get weird Firebase-related errors when using with Next.js.

My Next.js with Firebase Hosting article might cover some of the problems you are having with Next.js.

@jthegedus Thanks!

I made an example project using both next.js, firebase, and redux. Thought it might help others get started. Any feedback is appreciated.

Stats from current PR

Default Server Mode

General

zeit/next.js canary
zeit/next.js canary
Change

buildDuration
15.3s
16s
⚠ +615ms

nodeModulesSize
48.3 MB
48.3 MB
✓

Client Bundles (main, webpack, commons)

zeit/next.js canary
zeit/next.js canary
Change

main-HASH.js
18.9 kB
18.9 kB
✓

main-HASH.js gzip
6.79 kB
6.79 kB
✓

webpack-HASH.js
1.53 kB
1.53 kB
✓

webpack-HASH.js gzip
746 B
746 B
✓

4952ddcd88e7..2b8407376.js
21.9 kB
21.9 kB
✓

4952ddcd88e7..7376.js gzip
7.81 kB
7.81 kB
✓

de003c3a9d30..6604acae7.js
43.2 kB
43.2 kB
✓

de003c3a9d30..cae7.js gzip
15.5 kB
15.5 kB
✓

framework.5b..dbaff70d3.js
125 kB
125 kB
✓

framework.5b..70d3.js gzip
39.4 kB
39.4 kB
✓

Overall change
211 kB
211 kB
✓

Client Bundles (main, webpack, commons) Modern

zeit/next.js canary
zeit/next.js canary
Change

main-HASH.module.js
17.2 kB
17.2 kB
✓

main-HASH.module.js gzip
6.52 kB
6.52 kB
✓

webpack-HASH.module.js
1.53 kB
1.53 kB
✓

webpack-HASH..dule.js gzip
746 B
746 B
✓

de003c3a9d30..42.module.js
45.6 kB
45.6 kB
✓

de003c3a9d30..dule.js gzip
16.5 kB
16.5 kB
✓

framework.5b..d3.module.js
125 kB
125 kB
✓

framework.5b..dule.js gzip
39.4 kB
39.4 kB
✓

Overall change
190 kB
190 kB
✓

Client Pages

zeit/next.js canary
zeit/next.js canary
Change

_app.js
1.81 kB
1.81 kB
✓

_app.js gzip
873 B
873 B
✓

_error.js
12 kB
12 kB
✓

_error.js gzip
4.73 kB
4.73 kB
✓

hooks.js
12.7 kB
12.7 kB
✓

hooks.js gzip
4.79 kB
4.79 kB
✓

index.js
318 B
318 B
✓

index.js gzip
222 B
222 B
✓

link.js
8.14 kB
8.14 kB
✓

link.js gzip
3.5 kB
3.5 kB
✓

routerDirect.js
408 B
408 B
✓

routerDirect.js gzip
281 B
281 B
✓

withRouter.js
419 B
419 B
✓

withRouter.js gzip
280 B
280 B
✓

Overall change
35.8 kB
35.8 kB
✓

Client Pages Modern

zeit/next.js canary
zeit/next.js canary
Change

_app.module.js
1.7 kB
1.7 kB
✓

_app.module.js gzip
832 B
832 B
✓

_error.module.js
23.3 kB
23.3 kB
✓

_error.module.js gzip
8.59 kB
8.59 kB
✓

hooks.module.js
1.52 kB
1.52 kB
✓

hooks.module.js gzip
793 B
793 B
✓

index.module.js
294 B
294 B
✓

index.module.js gzip
223 B
223 B
✓

link.module.js
8.53 kB
8.53 kB
✓

link.module.js gzip
3.68 kB
3.68 kB
✓

routerDirect.module.js
394 B
394 B
✓

routerDirect..dule.js gzip
281 B
281 B
✓

withRouter.module.js
404 B
404 B
✓

withRouter.m..dule.js gzip
278 B
278 B
✓

Overall change
36.1 kB
36.1 kB
✓

Client Build Manifests

zeit/next.js canary
zeit/next.js canary
Change

_buildManifest.js
81 B
81 B
✓

_buildManifest.js gzip
61 B
61 B
✓

_buildManifest.module.js
81 B
81 B
✓

_buildManife..dule.js gzip
61 B
61 B
✓

Overall change
162 B
162 B
✓

Rendered Page Sizes

zeit/next.js canary
zeit/next.js canary
Change

index.html
3.62 kB
3.62 kB
✓

index.html gzip
945 B
945 B
✓

link.html
3.66 kB
3.66 kB
✓

link.html gzip
954 B
954 B
✓

withRouter.html
3.67 kB
3.67 kB
✓

withRouter.html gzip
942 B
942 B
✓

Overall change
10.9 kB
10.9 kB
✓

Serverless Mode

General

zeit/next.js canary
zeit/next.js canary
Change

buildDuration
16s
15.9s
-163ms

nodeModulesSize
48.3 MB
48.3 MB
✓

Client Bundles (main, webpack, commons)

zeit/next.js canary
zeit/next.js canary
Change

main-HASH.js
18.9 kB
18.9 kB
✓

main-HASH.js gzip
6.79 kB
6.79 kB
✓

webpack-HASH.js
1.53 kB
1.53 kB
✓

webpack-HASH.js gzip
746 B
746 B
✓

4952ddcd88e7..2b8407376.js
21.9 kB
21.9 kB
✓

4952ddcd88e7..7376.js gzip
7.81 kB
7.81 kB
✓

de003c3a9d30..6604acae7.js
43.2 kB
43.2 kB
✓

de003c3a9d30..cae7.js gzip
15.5 kB
15.5 kB
✓

framework.5b..dbaff70d3.js
125 kB
125 kB
✓

framework.5b..70d3.js gzip
39.4 kB
39.4 kB
✓

Overall change
211 kB
211 kB
✓

Client Bundles (main, webpack, commons) Modern

zeit/next.js canary
zeit/next.js canary
Change

main-HASH.module.js
17.2 kB
17.2 kB
✓

main-HASH.module.js gzip
6.52 kB
6.52 kB
✓

webpack-HASH.module.js
1.53 kB
1.53 kB
✓

webpack-HASH..dule.js gzip
746 B
746 B
✓

de003c3a9d30..42.module.js
45.6 kB
45.6 kB
✓

de003c3a9d30..dule.js gzip
16.5 kB
16.5 kB
✓

framework.5b..d3.module.js
125 kB
125 kB
✓

framework.5b..dule.js gzip
39.4 kB
39.4 kB
✓

Overall change
190 kB
190 kB
✓

Client Pages

zeit/next.js canary
zeit/next.js canary
Change

_app.js
1.81 kB
1.81 kB
✓

_app.js gzip
873 B
873 B
✓

_error.js
12 kB
12 kB
✓

_error.js gzip
4.73 kB
4.73 kB
✓

hooks.js
12.7 kB
12.7 kB
✓

hooks.js gzip
4.79 kB
4.79 kB
✓

index.js
318 B
318 B
✓

index.js gzip
222 B
222 B
✓

link.js
8.14 kB
8.14 kB
✓

link.js gzip
3.5 kB
3.5 kB
✓

routerDirect.js
408 B
408 B
✓

routerDirect.js gzip
281 B
281 B
✓

withRouter.js
419 B
419 B
✓

withRouter.js gzip
280 B
280 B
✓

Overall change
35.8 kB
35.8 kB
✓

Client Pages Modern

zeit/next.js canary
zeit/next.js canary
Change

_app.module.js
1.7 kB
1.7 kB
✓

_app.module.js gzip
832 B
832 B
✓

_error.module.js
23.3 kB
23.3 kB
✓

_error.module.js gzip
8.59 kB
8.59 kB
✓

hooks.module.js
1.52 kB
1.52 kB
✓

hooks.module.js gzip
793 B
793 B
✓

index.module.js
294 B
294 B
✓

index.module.js gzip
223 B
223 B
✓

link.module.js
8.53 kB
8.53 kB
✓

link.module.js gzip
3.68 kB
3.68 kB
✓

routerDirect.module.js
394 B
394 B
✓

routerDirect..dule.js gzip
281 B
281 B
✓

withRouter.module.js
404 B
404 B
✓

withRouter.m..dule.js gzip
278 B
278 B
✓

Overall change
36.1 kB
36.1 kB
✓

Client Build Manifests

zeit/next.js canary
zeit/next.js canary
Change

_buildManifest.js
81 B
81 B
✓

_buildManifest.js gzip
61 B
61 B
✓

_buildManifest.module.js
81 B
81 B
✓

_buildManife..dule.js gzip
61 B
61 B
✓

Overall change
162 B
162 B
✓

Serverless bundles

zeit/next.js canary
zeit/next.js canary
Change

_error.js
253 kB
253 kB
✓

_error.js gzip
67.9 kB
67.9 kB
✓

hooks.html
3.75 kB
3.75 kB
✓

hooks.html gzip
979 B
979 B
✓

index.js
254 kB
254 kB
✓

index.js gzip
68.2 kB
68.2 kB
✓

link.js
261 kB
261 kB
✓

link.js gzip
70.3 kB
70.3 kB
✓

routerDirect.js
255 kB
255 kB
✓

routerDirect.js gzip
68.3 kB
68.3 kB
✓

withRouter.js
254 kB
254 kB
✓

withRouter.js gzip
68.4 kB
68.4 kB
✓

Overall change
1.28 MB
1.28 MB
✓

Commit: d299811bfaea36088e037618c71fc6762df8b1c3


Example of a redirect route

More of a snippet instead of an issue, but for anyone looking for a simple Redirect route (like in react-router) this seem to work great;
import { Component } from 'preact';
import { route } from 'preact-router';

export default class Redirect extends Component {
  componentWillMount() {
  	route(this.props.to);
  }

  render() {
  	return null;
  }
}

And you can use it like this;
<Router>
   <Redirect path="/from" to="/to" />
</Router>

If @developit  likes the idea, I can add it as a PR to the library 🙃

Hiya @robinvdvleuten - I love the idea!  Maybe best as a "recipe" of sorts in the README?  There are already a few here.

@developit I've created a PR for it (#201)

Awesome, thanks for setting that up!


[SP-6128] Backport of PDI-19423 - Calculator step: The result of SQRT(AA+BB) is incorrect (9.3 Suite)

@smmribeiro
@bcostahitachivantara
@renato-s

:white_check_mark: Build finished in 23m 12s
Build command:
mvn clean verify -B -e -Daudit -amd -pl core,engine

:exclamation: No tests found!
:information_source:  This is an automatic message


⚠ Bofrost.at has degraded performance

In ba9c135, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 2097 ms

Resolved: Bofrost.at performance has improved in d1088f7 after 13 minutes.


[Fetch Data] Linearized buffer memory managment

This commit removes freeLinearizedBuf() to avoid chunks that have
references to deleted buffers. They will now be marked as deleted when
unpinned. All buffers should now be removed via BufferManagers::free.
Signed-off-by: Dmitrii Makarenko<EMAIL_ADDRESS>

@alexbaden @kurapov-peter PTAL, this pr changes free method contract a little, and also changes interaction of buffer with bufferManager. It works, but perhaps you have some recommendations about method's visibility and class responsibilities.


re.ChatGPT.revChatGPT module not found.

I installed revCHatGPT through pip but when I run the content generation file it gives me this error
Traceback (most recent call last):   File "C:\Users\Inaam\ChatGPT-Content-Generator\content_gen.py", line 4, in <module>     from chat_gpt_interface import get_video_script, save_script   File "C:\Users\Inaam\ChatGPT-Content-Generator\chat_gpt_interface.py", line 1, in <module>     from revChatGPT.revChatGPT import Chatbot ModuleNotFoundError: No module named 'revChatGPT.revChatGPT'
I guess the issue is just due to path, but do not know how to resolve this.

I have same issue! running on osx.

Try: from revChatGPT.ChatGPT import Chatbot

I installed revCHatGPT through pip but when I run the content generation file it gives me this error
Traceback (most recent call last): File "C:\Users\Inaam\ChatGPT-Content-Generator\content_gen.py", line 4, in <module> from chat_gpt_interface import get_video_script, save_script File "C:\Users\Inaam\ChatGPT-Content-Generator\chat_gpt_interface.py", line 1, in <module> from revChatGPT.revChatGPT import Chatbot ModuleNotFoundError: No module named 'revChatGPT.revChatGPT'
I guess the issue is just due to path, but do not know how to resolve this.

IF you guys have not found the solution, here what I did
pippip install --upgrade revChatGPT
and a bit change in code
`from revChatGPT.ChatGPT import Chatbot
import os
def get_video_script(token, video_topic, tone = "funny", length = "60"):
# For the config please go here:
# https://github.com/acheong08/ChatGPT/wiki/Setup
config = { "session_token": token }
prompt = "Write me a " + length + " second TikTok video script about " + video_topic + " with a " + tone + " "
if tone == "funny":
    prompt += "Please include a specific punchline and a joke."
elif tone == "informative":
    prompt += " Please include a specific fact and a tip."
elif tone == "romantic":
    prompt += "Please include a specific compliment and a love quote."
elif tone == "motivational":
    prompt += "Please include a motivational quote from a well-liked personality and a wellness tip."
elif tone == "inspirational":
    prompt += "Please include an inspiring quote from a celebrity and a tip about how to achieve your dreams."
elif tone == "educational":
    prompt += "Please include a specific fact and a tip about how to learn more about " + video_topic + "."
elif tone == "scary":
    prompt += "Please include a specific scary fact and a scary quote from someone who is not well-liked in the eyes of the public."
elif tone == "sad":
    prompt += "Please include a sad fact about " + video_topic + " and a sad quote from a well-liked celebrity or personality."
elif tone == "happy":
    prompt += "Please include a happy fact about " + video_topic + " and a happy quote from a well-liked personality."
elif tone == "angry":
    prompt += " with an angry tone. Please include a fact that most people would generally consider to be frustrating about " + video_topic + "."

prompt += " Please include a transition phrase at the end of each sentence. Also, please include a call to action at the end of the script, such as 'subscribe to @AI_TikTok_Bot' or 'follow @AI_TikTok_Bot for more videos like this. Also, create a clever title for the video, and introduce the title at the beginning of the script. Please make the title something catchy and attention-grabbing, such as 'The Most Dangerous Animal in the World' or 'The Most Dangerous Animal in the World is...'. Don't label things like 'Title: ', 'Opening: ', 'Ending: ', etc. Simply write the title, opening, and ending as if they were part of a cohesive script."

chatbot = Chatbot(config, conversation_id=None)

response = chatbot.ask(prompt,conversation_id=None, parent_id=None)
print(response)

return response

def save_script(script, current_working_dir, file_name):
file_path = os.path.join(current_working_dir + '/script', file_name)
# create a text file and write the script to it
with open(file_path, "w") as f:
    f.write(script)
    print("Saved script to " + file_path)
`


[documentation]: Update tutorial snippets

Signed-off-by: Ekaterina Mekhnetsova<EMAIL_ADDRESS>Changes in tutorial: https://github.com/hyperledger/iroha-2-docs/pull/246
This way the code snippets are pulled directly from this repo to the tutorial

@6r1d If you have the time, have a quick look and approve.


Add rustfmt

As this crate is almost rustfmt compatible, why don't we add it to the CI?
Also, this moves the rustup invocations to install which travis provides.
This make no difference now, but if we add more ci jobs with matrix, rustup wouldn't be called for every job.

Awesome! Still getting around to your other updates, thanks for your patience! 😋


JSON Schema not backward compatible with V1

I believe that this change introduced a backward compatibility change between v1 and v2:
https://github.com/stargate/stargate/pull/1867/commits/ba6a1d5963eb5404d912bc390a08c5a7abba2612
The V1 is wrapping the schema in the schema property, which is not done now in V2. In addition it was a good approach as enables us to add additional things in the future in different properties.

@Eric please let me know if I am wrong here, but I doubt..

Done in #1885.


Wrong type in syscall type Utsname: uint8 instead of int8

What version of Go are you using (go version)?

go version go1.4.3 linux/arm

What operating system and processor architecture are you using?

$ uname -a
Linux ef19e7655f61 4.2.5-263 #1 SMP Wed Nov 4 17:03:17 UTC 2015 armv7l armv7l armv7l GNU/Linux
$ cat /etc/os-release
NAME="Ubuntu"
VERSION="14.04.2 LTS, Trusty Tahr"
ID=ubuntu
ID_LIKE=debian
PRETTY_NAME="Ubuntu 14.04.2 LTS"
VERSION_ID="14.04"
HOME_URL="http://www.ubuntu.com/"
SUPPORT_URL="http://help.ubuntu.com/"
BUG_REPORT_URL="http://bugs.launchpad.net/ubuntu/"

What did you do?

I want to compile Docker for ARM but stumbled upon a problem that the type of Utsname is different for linux/arm to all other intel platforms.
Also the official golang docs says that it uses [65]int8 but for linux/arm it is [65]uint8.

What did you expect to see?

To have the same types for linux/arm

What did you see instead?

I had to add a workaround to read the value into a string in two different ways, one for intel, one for linux/arm.

linux/386: https://github.com/golang/go/blob/master/src/syscall/ztypes_linux_386.go#L555-L560
linux/amd64: https://github.com/golang/go/blob/master/src/syscall/ztypes_linux_amd64.go#L571-L576
linux/arm: https://github.com/golang/go/blob/master/src/syscall/ztypes_linux_arm.go#L543-L548
linux/arm64: https://github.com/golang/go/blob/master/src/syscall/ztypes_linux_arm64.go#L549-L554

Is there any reason that the type is different here?

The problem is because the signedness of the char type in C is different on
different architectures.
On ARM, due to limitations of old generation architectures, char is
unsigned, so the translated Go type is uint8 not int8.
We probably should have fixed this before Go 1, but now we cannot do
anything about it due to the Go 1 API guarantee.

Possibly this could be addressed in the implementation in the x/sys repo.
Possibly it already has, I haven't checked.
On Thu, Nov 19, 2015 at 11:03 AM, Minux Ma<EMAIL_ADDRESS>wrote:

The problem is because the signedness of the char type in C is different on
different architectures.
On ARM, due to limitations of old generation architectures, char is
unsigned, so the translated Go type is uint8 not int8.
We probably should have fixed this before Go 1, but now we cannot do
anything about it due to the Go 1 API guarantee.
—
Reply to this email directly or view it on GitHub
https://github.com/golang/go/issues/13318#issuecomment-157903892.

I don't think we should change x/sys/unix too, as it will
break already working programs.
It hasn't changed:
https://github.com/golang/sys/blob/master/unix/ztypes_linux_arm.go#L542

Package syscall is OS-dependent. One should guard code that uses it with +build tags. You should never expect a syscall invocation to work on multiple platforms. That's what the os package is for.

That to clarify this.


Complicated sentence is complicated

This sentence is difficult to grok. Please break it up into multiple sentences:

A service worker registration has one or more task queues that back up the tasks, whose task source is either the handle fetch task source or the handle functional event task source, from its active worker's event loop's corresponding task queues when the user agent terminates the active worker and re-queue those tasks to the active worker's event loop's corresponding task queues when the active worker spins off.

(as a general rule, try to keep sentences no longer than 17-20 words ... and only have a maximum of two ideas per sentence)


Fix mistake: miliseconds -> milliseconds

https://en.wikipedia.org/wiki/Millisecond

Thanks, I'll merge this before the release of next version (coming soon), as there will be more metric name changes


Make a generic redis-based deduplicator

So we're gonna take the same approach to deduplication as we do for blacklisting.
We will have a separate deduplicator module with a configured redistribution client and will unconditionally send all the messages to the deduplicator. Then it will, just like MediaWiki version, first check whether the message individually is a duplicate - e.g. if the message with exact same ID was recently processed by exact same rule. Also, if there's information about the root_event - attempt to deduplicate based on the root event.
This also switches the dependency processor to the new reduplication method. Will need to update schemas, but it doesn't really matter, because these events are not going via the proxy service, so the schemas are just for the documentation purposes.
@wikimedia/services

Coverage decreased (-0.5%) to 88.903% when pulling fcd7112bb8169a876da459362a6da32796e1bf4b on Pchelolo:redis_dedupe into<PHONE_NUMBER>9a7e7456a9b0ad45ea6d0c6c3bfec9 on wikimedia:master.

Coverage increased (+0.6%) to 89.949% when pulling cadac2d46f4673f82699ff004b4c9782399d2877 on Pchelolo:redis_dedupe into<PHONE_NUMBER>9a7e7456a9b0ad45ea6d0c6c3bfec9 on wikimedia:master.

Coverage increased (+0.6%) to 89.949% when pulling cadac2d46f4673f82699ff004b4c9782399d2877 on Pchelolo:redis_dedupe into<PHONE_NUMBER>9a7e7456a9b0ad45ea6d0c6c3bfec9 on wikimedia:master.

Coverage increased (+0.6%) to 89.962% when pulling 988e89245f6f06303406a7589908f4a13dc2e03c on Pchelolo:redis_dedupe into<PHONE_NUMBER>9a7e7456a9b0ad45ea6d0c6c3bfec9 on wikimedia:master.

Coverage increased (+0.5%) to 89.861% when pulling 5df70ae6d949f265882e0a36233bb98df732a6c8 on Pchelolo:redis_dedupe into<PHONE_NUMBER>9a7e7456a9b0ad45ea6d0c6c3bfec9 on wikimedia:master.

A couple of thoughts:

Separate end point vs. filter: Deduplication (and rate limiting) seem like they might fit the filter interface. The attraction would be that deduplication could be configured quite easily on different end points. I know we discussed this idea before, and you looked into it, so I'm curious what your conclusion was on that direction.
Mixin vs. composition: In terms of readability and ease of understanding, inheritance and mixins often tend to be worse than composition. In this case, it seems that the main functionality provided is a somewhat hyperswitch-specific redis wrapper. Just making that a plain class member could be easier to understand.
HTTP interface: The current POST interface returning 200 and true / false seems very RPC-y. A more idiomatic HTTP approach could be a PUT to a key with If-None-Match: *. This would also move the key selection to the client.

Separate end point vs. filter: Deduplication (and rate limiting) seem like they might fit the filter interface. The attraction would be that deduplication could be configured quite easily on different end points. I know we discussed this idea before, and you looked into it, so I'm curious what your conclusion was on that direction.

I've been exploring these 2 options for a while now and I couldn't come up with a decent use of filters. The main issue is that a filter must be set on an endpoint - that means we need to introduce one level of indirection on a rule - add a special rerender_restbase endpoint for example and then call it from the rule. The problem with this approach is that every rule serenaders RESTBase slightly differently, so creating one single rerender_restbase endpoint that fit all the use-cases is VERY tricky. And if we create one per rule, that makes the config completely unreadable, way longer and way trickier to write. I do agree that having a filter would be nice, but I've already spent way too much time trying to fit the filters into the system and they just don't fit in. It's like fitting a cube into a round hole. I think eventually we will come up with a solution, but that could be made as a refactoring step - the core functionality will stay unchanged.

Mixin vs. composition: In terms of readability and ease of understanding, inheritance and mixins often tend to be worse than composition. In this case, it seems that the main functionality provided is a somewhat hyperswitch-specific redis wrapper. Just making that a plain class member could be easier to understand.

The mixin thingy was my little experiment on how would people react to this kind of multiple inheritance based composition. We already have a delegate approach here in KafkaFactory - an object factory that encapsulates all the setup for a Kafka client. I don't really have strong feelings towards any of the options, so whatever everyone thinks is better I will use.

HTTP interface: The current POST interface returning 200 and true / false seems very RPC-y. A more idiomatic HTTP approach could be a PUT to a key with If-None-Match: *. This would also move the key selection to the client.

Ye, it is kinda an RPC here.. And the idea with a header seems nice, lemme redo that.

Corresponding deploy repo config change:  https://gerrit.wikimedia.org/r/374629


Bardic Inspiration (CRP) not working

Bardic Inspiration (CRP) does not work as it says the character is out of resource.  It maybe be that the importer is adding this in error.

Please can you provide a character link and screen shots of the options used on the import and active effects pages, and are you using the Link Resources 5e module?


Once driver register successfully, stop it to connect to master.

This commit is to resolve SPARK-12396.

Can one of the admins verify this patch?

This PR was merged by mistake, reverted, sorry.


Update documentation to support modern CMake FetchContent method over ExternalProject.

Description

Hello, thank you for creating or contributing to such a useful and vital tool.
The current build_system documentation describes using the CMake ExternalProject mechanism for acquiring the doctest header file and using it in a CMake project. ExternalProject is great for use with Non-CMake externals, but doctest is a modern CMake package with target support, so users can instead use the more efficient and elegant FetchContent mechanism.
FetchContent supports CMake targets. It also moves the download step to project configure time rather build time like ExternalProject.
I suggest updating the documentation to prefer FetchContent.
For example:

You can also use the following CMake snippet to automatically fetch the entire doctest repository from github and configure it as an available target:

include(FetchContent)
FetchContent_Declare(
  doctest
  GIT_REPOSITORY https://github.com/doctest/doctest
  GIT_TAG master # or any SHA, Branch or tag like v2.4.9
)
FetchContent_MakeAvailable(doctest)

The target doctest::doctest is now exposed at the global scope
And later you'll be able to use the doctest include directory like this:
# Link doctest to a target
target_link_libraries(my_target PUBLIC doctest::doctest)

# Or link it globally
link_libraries(doctest::doctest)

Access the doctest headers with a scoped #include directive. For example in tests/main.cpp
#define DOCTEST_CONFIG_IMPLEMENT_WITH_MAIN
#include "doctest/doctest.h"

int factorial(int number) { return number <= 1 ? number : factorial(number - 1) * number; }

TEST_CASE("testing the factorial function") {
    CHECK(factorial(1) == 1);
    CHECK(factorial(2) == 2);
    CHECK(factorial(3) == 6);
    CHECK(factorial(10) == 3628800);
}

If this is something you're interested in supporting I can open a PR with the above changes.
Steps to reproduce

Extra information

doctest version: v42.42.42
Operating System: Joe's discount operating system
Compiler+version: Hidden Dragon v1.2.3

Thanks for these instructions! I was missing the scoped include directive.

I'm trying to get this working, however the test discovery function doctest_discover_tests can't be found. I need to include something but I'm not sure what. I think this information would be good to include in the docs.

ok, so if you include("${CMAKE_SOURCE_DIR}/build/_deps/doctest-src/scripts/cmake/doctest.cmake") it works but that doesn't seem like the right way.

slightly better, include("${doctest_SOURCE_DIR}/scripts/cmake/doctest.cmake"). Is there a better way?

I figured out another way
list(APPEND CMAKE_MODULE_PATH "${doctest_SOURCE_DIR}/scripts/cmake")
include(doctest)

This is how I do it - not sure if it is the best way:
include(CTest)
enable_testing()
include(${doctest_SOURCE_DIR}/scripts/cmake/doctest.cmake)
# automatically add doctest tests to CTest; specify WORKING_DIRECTORY to ensure that relative paths are correct for CTest
doctest_discover_tests(${TESTS_EXE_NAME} WORKING_DIRECTORY ${CMAKE_RUNTIME_OUTPUT_DIRECTORY})

What is the advantage of list(APPEND ... ?

I don't know what the implications of adding ${doctest_SOURCE_DIR}/scripts/cmake to the CMAKE_MODULE_PATH are. Maybe if you wanted to include multiple things. But if you are just including one thing, maybe it's best to just include the one file.

This discussion has moved here: https://github.com/doctest/doctest/pull/866 .
My bad for reviewing issues in the wrong order, but I'll mark this as a duplicate even though it was opened first, apologies for that.


sqlite3.OperationalError: no such column:

If a file is read in with a new pelican tag that doesn't exist as a column in the table the an error is thrown:
sqlite3.OperationalError: no such column: <column name>

Looks like I should try and use datasette-init

No longer needed with 59519f14976784eec33477868a42eeefb77b5e4b


Audio durations not matching up.

Asalamu Aleykum. So I was on this site trying to listen to a surah. Pretty simple, right? But then I noticed something about the durations. They weren't matching up. Look at the screenshot below:

As you can see, the audio player has the correct duration while the duration on the preview (I guess we could call it that??????) is smaller than the actual duration. API issue?

I've noticed the same. I'm currently setting it up locally. I will try give this a go.

Thanks for raising this issue, we're a community fo volunteers. Can I help you try to debug this issue and maybe submiit a fix? Many thanks

Sure, I could try but I'm a Python person and your API is written in Ruby (I think).

wa3laikum alsalam,
this might actually be a data issue since these times are in the database today.
we should be able to re-run the script to get the correct timings.
walsalam 3alaikum.

@ahmedre Asalamu Aleykum. Database problem huh? Oh well. Let me know when the fix is up and I'll close the issue.

wa3laikum alsalam wa ra7matullahi wa barakatuh,
fixed, jazakumAllah khairan

Thanks - it works now :)


What notification is expected after queue is completed?

There is a preference option "Notify when complete". With version 2.3.3, I don't get an alert sound, notification center alert or any other noticeable action. What should I be looking for?
When I disabled this option to test if the expected behavior was reversed (I've seen this before ;), the app crashed. It ran normally on relaunch, but still no notification.

It's a bug, it should both notify and make a sound when the process is done and the window is out of focus. It worked before, so I must have done something. Why it crashed when the option was deselected, though, I must look into.

@mikemcduffie The notifications (and sound alert) works for me. The notifications only show when app is out of focus, which is how it should be. But I'll be adding the sound alert, whether the app is in focus or not.

Same here. I just hadn't ran it out of focus as my tests so far have completed very quickly (3-5 folders of average comic size).

Sound notification added in version 2.3.4.


Update tests that generate CMake projects to use main project's C++ compiler

Update tests that generate CMake projects to use the CMAKE_CXX_COMPILER the main project was CMake'd with. Fixes #1747.

Pull request checklist
Read the Contribution Guidelines for detailed information.

[x]  Changes are described in the pull request, or an existing issue is referenced.
[ ]  The test suite compiles and runs without error.
[ ]  Code coverage is 100%. Test cases can be added by editing the test suite.
[ ]  The source code is amalgamated; that is, after making changes to the sources in the include/nlohmann directory, run make amalgamate to create the single-header file single_include/nlohmann/json.hpp. The whole process is described here.

Please don't

The C++11 support varies between different compilers and versions. Please note the list of supported compilers. Some compilers like GCC 4.7 (and earlier), Clang 3.3 (and earlier), or Microsoft Visual Studio 13.0 and earlier are known not to work due to missing or incomplete C++11 support. Please refrain from proposing changes that work around these compiler's limitations with #ifdefs or other means.
Specifically, I am aware of compilation problems with Microsoft Visual Studio (there even is an issue label for these kind of bugs). I understand that even in 2016, complete C++11 support isn't there yet. But please also understand that I do not want to drop features or uglify the code just to make Microsoft's sub-standard compiler happy. The past has shown that there are ways to express the functionality such that the code compiles with the most recent MSVC - unfortunately, this is not the main objective of the project.
Please refrain from proposing changes that would break JSON conformance. If you propose a conformant extension of JSON to be supported by the library, please motivate this extension.
Please do not open pull requests that address multiple issues.

Coverage remained the same at 100.0% when pulling fbb0bd7556f1fe7c6e9540e1a40af085c7861032 on Tridacnid:develop into e7b3b40b5a95bc74b9a7f662830a27c49ffc01b4 on nlohmann:develop.

Thanks!

🔖 Release item
This issue/PR will be part of the next release of the library. This template helps preparing the release notes.
Type

[ ] ✨ New Feature
[ ] 🐛 Bug Fix
[ ] ⚡ Improvement
[x] 🔨 Further Change
[ ] 🔥 Deprecated function

Description

Update tests that generate CMake projects to use main project's C++ compiler. #1747 #1844


Statistics generation enhancements

#426

@mariano-dagostino please review

@mariano-dagostino
Made minor change at 82a1548.


Add import/no-cycle

https://github.com/benmosher/eslint-plugin-import/blob/master/docs/rules/no-cycle.md

The rule is apparently quite computationally expensive and I'm a bit hesitant to add it, since bundlers have some support for circular imports. I'd wait if we run into this problem again before enabling this.


Timers vs Worldsaves

During a Worldsave
-Timerf's timers will freeze and wait for the save to end
-Item timers that uses the on=@timer trigger will keep rolling during the save.
On=@timer's timers should freeze during a worldsave just like Timerf

https://github.com/Sphereserver/Source-X/commit/0d42711b61b3c920217160b4167edd10c35fedd0 Should fix this.


chore: add .vscode and .idea to .gitignore

Ignore .vscode and .idea to prevent contributor's personal configuration from polluting the project.

LGTM, thank you!


Integration of schedule, makeup and cancel commands

These commands are all interlinked as they affect the overall schedule of the user. Adding and cancelling of regular and makeup lessons needs to be integrated properly.

Will need to implement check for clashes

bumping to v1.4


Start a deployment also if only residency or upgradeStrategy is changed.

LGTM although there is no test. I could be mean, you know … ;)

waiting for the tests ...

Thanks @aquamatthias!


Added receive records to peer forwarder

Signed-off-by: Asif Sohail Mohammed<EMAIL_ADDRESS>Description
Added receive record which reads the records from buffer forwarded by other peers, and sends them to process locally.
Issues Resolved
Check List

[x] New functionality includes testing.
[ ] New functionality has been documented.

[ ] New functionality has javadoc added

[ ] Commits are signed with a real name per the DCO

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #1761 (0ea4c64) into main (73d8d86) will increase coverage by 0.06%.
The diff coverage is 100.00%.

@@             Coverage Diff              @@
##               main    #1761      +/-   ##
============================================
+ Coverage     93.41%   93.47%   +0.06%
- Complexity     1406     1407       +1
============================================
  Files           187      187
  Lines          4162     4170       +8
  Branches        329      329
============================================
+ Hits           3888     3898      +10
+ Misses          193      191       -2
  Partials         81       81

Impacted Files
Coverage Δ

.../dataprepper/peerforwarder/LocalPeerForwarder.java
100.00% <100.00%> (ø)

...taprepper/peerforwarder/PeerForwarderProvider.java
96.55% <100.00%> (ø)

...eerforwarder/PeerForwardingProcessorDecorator.java
100.00% <100.00%> (ø)

...dataprepper/peerforwarder/RemotePeerForwarder.java
82.22% <100.00%> (+3.27%)
:arrow_up:

...peerforwarder/server/PeerForwarderHttpService.java
97.77% <100.00%> (ø)

...dataprepper/plugins/source/RandomStringSource.java
73.33% <0.00%> (-3.34%)
:arrow_down:

.../org/opensearch/dataprepper/pipeline/Pipeline.java
92.85% <0.00%> (+4.28%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


fix: e2e-test run  in  given workspace against RHTAP-Stage

…ecting RHTAP-Stage.
Description
When initializing framework object to run against RHTAP-Stage ,  if utils.Options.Workspace   is  ""
then the offline-connection will be to the default workspace
if  utils.Options.Workspace is defined to a workspace , the connection will be in specified workspace
HACBS-2507
Type of change

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] This change requires a documentation update

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Checklist:

[ ] I have performed a self-review of my code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] I have added meaningful description with JIRA/GitHub issue key(if applicable), for example HASSuiteDescribe("STONE-123456789 devfile source")
[ ] I have updated labels (if needed)

/test redhat-appstudio-e2e

/test redhat-appstudio-e2e

/test redhat-appstudio-e2e

/test redhat-appstudio-e2e

This is adding another condition or if block can you utilize the exsiting if block down in
https://github.com/redhat-appstudio/e2e-tests/blob/1f729dc6308607d8989b162b60c4eccf5b29165c/pkg/framework/framework.go#L65
and add this peice of code there.

Done,
looks much better,

/test redhat-appstudio-e2e


possible solution for #8257

taking first breakpoint and check if smallest and define it as zero-breakpoint

Thanks for putting this together! My feedback:

Name the variable $-zf-zero-breakpoint. The prefix emphasizes that it's a private variable—we don't need developers using it in their own code.
You'll need to replace every instance of @include breakpoint(small) in the framework with @include breakpoint($-zf-zero-breakpoint), so that if someone renames small in their breakpoint list, all of the internals of the framework are able to switch over to the new name.

Thanks for the feedback. I hoped I already found all references to small, but I'll check again. I'll make the changes as soon as possible.

I change the variable following your feedback and replaced all usages of small breakpoint. I wasn't 100% sure about one place. It's _rows.scss:83

Is there anything more to do?

Nope, looks good. Thanks for putting it together!

So what's the quick-and-dirty guide to implementing this change in our bleeding-edge code? Do we just add something like this to settings.scss:
$-zf-zero-breakpoint: 'small'; // or 'xsmall' or 'tiny' or 'smallest' or whatever

@proimage That will probably work.

Thou assumest too muchly - I roll Foundation SCSS manually. :p
For the record, yes, after downloading the latest develop branch and using the scss folder therein, adding that one line above to my settings.scss appears to have brought things back to the way they were in 6.1.x. Much grass!