The command az webapp up failed with an unexpected error - Python 2.7

This is autogenerated. Please review and update as needed.
Describe the bug
Command Name
az webapp up
Errors:
The command failed with an unexpected error. Here is the traceback:

glob() got an unexpected keyword argument 'recursive'
Traceback (most recent call last):
  File "/usr/lib64/az/lib/python2.7/site-packages/knack/cli.py", line 206, in invoke
    cmd_result = self.invocation.execute(args)
  File "/usr/lib64/az/lib/python2.7/site-packages/azure/cli/core/commands/__init__.py", line 603, in execute
    raise ex
TypeError: glob() got an unexpected keyword argument 'recursive'

To Reproduce:
Steps to reproduce the behavior. Note that argument values have been redacted, as they may contain sensitive information.

Put any pre-requisite steps here...
az webapp up -g {} -n {} -l {} --sku {} -p {}

Expected Behavior
Environment Summary
Linux-3.10.0-957.21.3.el7.x86_64-x86_64-with-centos-7.6.1810-Core
Python 2.7.5
Shell: bash

azure-cli 2.0.70

Additional Context

@gustavo-accellog please update the python version 3.5 or higher & this should be resolved. Looks like I missed a part of the code which is still using glob that is not available on older versions of Python.

I had the same problema in az aks creat and it was ok now.
https://github.com/Azure/azure-cli/issues/9651#issuecomment-518289351
I'm using CentOS 7 and the python 2.7 is default. But I use python 3.6 too.


Multi repos support

Hello.
Some might want to update GitHub Secrets in multiple repositories by specifying two or more repos in OWNER_REPOSITORY.  eg. OWNER_REPOSITORY: ${{ github.repository }},ScatteredTuna/supreme-tuna.
@kneemaa  Could you take a look at the PR if you have time?
Thanks.

@taizo i just approved https://github.com/kneemaa/github-action-rotate-aws-secrets/pull/2 - do you mind resolving the conflicts and testing before I review?

@kneemaa Thank you for the reply.
Resolved the conflicts and confirmed that's working correctly. Could you please review the PR? 🙇♂

To ensure I'm on the same page. The idea is that a single action could update the IAM keys of multiple repositories if the Github Dev Token has permissions?

update the example on line 59 of README.md

Thank you for your suggestion.
I've updated the param usage part to add an example of multiple repos support instead of updating the example of line 59 because a user mostly want to update secret in single repository. The example of line 59 should be more general.


Prepare object_store 0.9.0 (#5224)

Which issue does this PR close?

Closes #5224
Rationale for this change

What changes are included in this PR?

Are there any user-facing changes?

The error appears to relate to some issue internal to localstack pertaining to Content-Length. Given we never set Content-Length, I am inclined to chalk this up to some localstack specific error.


Release a new version with an update ref to 'Azure.Identity'

'Azure.Identity' 1.11.3 has a known moderate severity vulnerability, https://github.com/advisories/GHSA-m5vv-6r4h-3vj9
can you release a version that updates this reference

We'll look to have this scheduled for our next release

this is a poor experience for consumers. for anyone who has CVE scanning turned on it breaks builds. and they need to explicitly add an azure reference to work around it. so for us it means doing a temporary hack on approx 40 projects just to build again. note that we dont even use azure.
if the sqlclient wants force a transitive azure ref on non azure users, then you pro-actively release cve related fixes for azure.

if the sqlclient wants force a transitive azure ref on non azure users

or a version (stripped down?) without this nuget and whatever it offers? or how about the default version doesn't have this at all and a 2nd version has this so people who want to use Azure.Identity with their SqlClient can use that version. For the 99% rest of us, we don't need to worry about this transitive dep anymore/then.

One reason of many to want https://github.com/dotnet/SqlClient/issues/1108.

@jnm2 Sure, but a better solution is to have a short timeline for release of s patch.

For this individual occurrence, yes, but I'm also thinking of the future ones.

@jnm2 Sure, but a better solution is to have a short timeline for release of s patch.

Why is a better solution to have a shorter timeline on a dependency that many people don't even need? It would be one thing if SQL Server was Azure only, but there are the obvious cases of people hosting on-prem, on AWS and elsewhere - even on an Azure VM.

@CamiloTerevinto if you are on premises I guess the vulnerability would not affect you, but Azure users would want a patch as soon as possible?

@ErikEJ it affects everyone that treats package vulnerability warnings as errors and those that use SCA as well.

@CamiloTerevinto Exactly, so "a short timeline for release of a patch" would solve it for everyone! 😄

@CamiloTerevinto Exactly, so "a short timeline for release of a patch" would solve it for everyone! 😄

During last two months, Azure.Identity has released 5 consecutive version which  four of them are deprecated now. Your suggestion indicates we should have had almost 3 patch releases per month.
An automated process could be created to check Azure.Identity latest version for deprecation notice and if there is any, hotfix release pipeline could be triggered to release a new version....
Let me discuss this internally with other team members and get back to you.

@JRahnama yeah, it is a lot of updates, but would make all your consumers happy, and potentially avoid/obliviate the requirement to split the package.

@JRahnama If you do this, consider that Azure.Identity depends on Microsoft.Identity.Client, so you should really not have an explicit dependcy on Micrsoft.Identity.Client, like you do today:
https://www.nuget.org/packages/Azure.Identity#dependencies-body-tab
    <AzureIdentityVersion>1.11.3</AzureIdentityVersion>
    <MicrosoftIdentityClientVersion>4.60.3</MicrosoftIdentityClientVersion>

@JRahnama yeah, it is a lot of updates, but would make all your consumers happy, and potentially avoid/obliviate the requirement to split the package.

@ErikEJ I don't understand this position to be honest. Why do you think that having dependencies that aren't needed for some clients but that are kept up to date somehow better than just not having the dependencies at all?
Even if you updated Azure.Identity and other dependencies quickly for security vulnerabilities, that's only meant for customers that are using Azure SQL - for the rest, you're making them see the release notes for this package to see how the release affects them.
You are also hoping that users will update this package quickly enough with the security vulnerability warning, and I have seen people ignore these on VS even.
@JRahnama If Azure.Identity is your dependency, to me, it doesn't matter how many security hotfix releases they do, it should be a high priority to get this dependency updated. Otherwise you are saying to users of this package that you don't care about their security.

@CamiloTerevinto Because I seriously doubt the package split will ever happen, and given that, this would be the desired outcome that pleases most users expect the ones concerned about a few more MB payload.

Because I seriously doubt the package split will ever happen, and given that, this would be the desired outcome that pleases most users expect the ones concerned about a few more MB payload.

Sadness. :(
Putting MB payload size and shorter timeframes, etc aside - the issue is really about RESPECT for the consumers here. I (and I feel like many others) find the poor solution design to bake in Azure in to the core product as message suggesting (assuming? or pushing from a sales perspective?) that users should be using SQL with SqlAzure. Not the other options/flavours.
A more respectful solution would be to split out the specific pieces of sql like SqlAzure, etc to their own nugets so people can use what is the bare necessity to them.
What we (the consumers) have to deal with now is the "dependency-hassle" of components/parts of SqlClient which we will never use. This hassle IS NOT about a payload size. sheesh!
And to hand wave this off as 'just deal with it/get over it/it's nothing', we feel is a bit rude :(
ESPECIALLY when this could potentially (I believe) be architected in way to split these concerns out.
If it's about (lack of) manpower - then say so.
If it's about (lack of) budget - then say so.
If it's about a strong design decision - then please educate us so we can understand the gap in understanding.
If it's just a low priority / can't be bothered - then also, please say so.
If you would accept a PR for this - also say as such.

@PureKrome This has been discussed at very great length here: https://github.com/dotnet/SqlClient/pull/2247
And based on the fact that this comment from @David-Engel is now 5 months old, I am considering altrnative approaches
Also, I am not a Microsoft vendor, I am just an open source contributor from the .NET community.

Thanks heaps @ErikEJ - sincerely appreciate the links, comments and help 🤗 🍰

@JRahnama If you do this, consider that Azure.Identity depends on Microsoft.Identity.Client, so you should really not have an explicit dependcy on Micrsoft.Identity.Client, like you do today:
https://www.nuget.org/packages/Azure.Identity#dependencies-body-tab
    <AzureIdentityVersion>1.11.3</AzureIdentityVersion>
    <MicrosoftIdentityClientVersion>4.60.3</MicrosoftIdentityClientVersion>

ActiveDirectoryAuthenticationProvider and some other classes is using Microsoft.Identity.Client for AAD authentication. There is a possibility to use Azure.Identity replacement for AAD, but that will limit the useage to Azure users. Can you add a bit more to clarify it?

I just meant that you do not need an explicit reference and version spec to Microsoft.Identity.Client, it is already referenced via the use of Azure.Identity - I will create a PR to demonstrate

Can you add a bit more to clarify it?

@JRahnama I just meant that you do not need an explicit reference and version spec to Microsoft.Identity.Client, it is already referenced via the use of Azure.Identity - I will create a PR to demonstrate

Awesome, it will make it much easier to create an azure function to trigger build pipelines when a new version is released.

@JRahnama Guess I should really backport the reference reduction change to 5.1 and 5.2 then?

@JRahnama I'd highly recommend simply looking at enabling Dependabot for dependency changes, rather than building some custom mechanism you'd need to maintain (e.g. via Azure Functions). Dependabot is a built-in Github feature which automatically submits PRs to your repo whenever a dependency is released, and is specifically geared towards keeping your library secure in the face of security issues in its dependency graph (see docs).
Note that for Dependabot to function correctly, your project needs to follow some basic standard .NET patterns in how it represents the versions in csproj; I know SqlClient has a somewhat complicated build structure which may interfere with that. But i'd recommend looking into it, and cleaning up the SqlClient build system would ideally be a goal unto itself.
That takes care of bumping dependency versions - but when you actually release a new SqlClient version to your users is another question. I'd advise against trying to automatically release anything; not every patch version bump of Azure.Identity (or some other dependency) is something that merits immediately releasing a new SqlClient version - that would cause lots of churn to users that may not care (or even use Azure). I'd invest in being able to release very quickly for when a security issue (or other critical bug) is discovered, but otherwise keep the actual decision to release manual.
Finally, as discussed many times before, I'd keep the dependency management/releasing conversation distinct from whether SqlClient should depend on Azure.Identity at all - the two really are orthogonal (even if the dependency causes a lot of grief in terms of needing to release). I absolutely agree that SqlClient should not depend on Azure.Identity (#1108), but the dependency management/releasing question must be solved regardless of that. After all, even if the Azure.Identity dependency were split off to an external package (e.g. Microsoft.Data.SqlClient.Azure), the exact same problems would apply there.

out of curiosity, do MS projects not do CVE checking? ie by enabling  this in your Directory.Build.props
    <NuGetAuditMode>all</NuGetAuditMode>
    <NuGetAuditLevel>low</NuGetAuditLevel>
    <TreatWarningsAsErrors>true</TreatWarningsAsErrors>

@JRahnama Guess I should really backport the reference reduction change to 5.1 and 5.2 then?

Did this happen?

@cremor No.

Hotfixes 5.1.6 and 5.2.2 have been released which address this issue! Appreciate everyone's patience

5.2.2 contains System.Text.Json 8.0.0 which gives:
NU1903: Warning As Error: Package 'System.Text.Json' 8.0.0 has a known high severity vulnerability, https://github.com/advisories/GHSA-8g4q-xg66-9fp4
so, the dependency tree of 5.2.2 still causes any solution/project which references it to fail the build in azure devops pipelines.
        ├─ Microsoft.Data.SqlClient (v5.2.2)
        │  └─ Azure.Identity (v1.11.4)
        │     ├─ Azure.Core (v1.38.0)
        │     │  ├─ System.ClientModel (v1.0.0)
        │     │  │  ├─ System.Memory.Data (v1.0.2)
        │     │  │  │  └─ System.Text.Json (v8.0.0)
        │     │  │  └─ System.Text.Json (v8.0.0)
        │     │  ├─ System.Memory.Data (v1.0.2)
        │     │  │  └─ System.Text.Json (v8.0.0)
        │     │  └─ System.Text.Json (v8.0.0)
        │     └─ System.Text.Json (v8.0.0)

and no, we will not turn off "Warning As Error", we're health care software providers with some of the highest security requirements that exist in the industry.

@dlatikaynen there's no need to turn off "warning as error" - you can simply take a direct reference on a newer version System.Text.Json which doesn't have the CVE. That doesn't mean things shouldn't be updated on the SqlClient/Azure.Identity side, but you shouldn't be blocked by this.

newer version System.Text.Json which doesn't have the CVE

@roji it seems a weird to suggest that every consumer of the SqlClient  (i assume there a many at 348.6K downloads per day) apply a hack, instead of making one fix in this codebase and fix it for everyone.
for some context, across out various code bases, we currently have 48 direct reference to various MS packages to avoid CVEs. This is difficult to keep track of since there is no automated way to work out when those CVE hacks are redundant. we need to periodically go back and manually remove them to see if they are still required.
This could be greatly mitigated if MS was pro-active about releasing new nugets that do not have transitive CVEs

@dlatikaynen there's no need to turn off "warning as error" - you can simply take a direct reference on a newer version System.Text.Json which doesn't have the CVE. That doesn't mean things shouldn't be updated on the SqlClient/Azure.Identity side, but you shouldn't be blocked by this.

No sorry taking directly dependencies fundamentally goes against the entire purpose of transitive dependencies being introduced.
I have had to disable warnings as errors for vulnerabilities because I’ve got warnings from dependencies 3-4 levels deep.
Microsoft needs to fix this at nuget level to take latest minor or build versions.

https://blogs.microsoft.com/blog/2024/05/03/prioritizing-security-above-all-else/

If you’re faced with the tradeoff between security and another priority, your answer is clear: Do security. -- Satya Nadella

https://blogs.microsoft.com/blog/2024/05/03/prioritizing-security-above-all-else/

If you’re faced with the tradeoff between security and another priority, your answer is clear: Do security. -- Satya Nadella

This is funny. So instead of doing security. Microsoft decided to add work arounds to prevent doing security.

you can simply take a direct reference on a newer version System.Text.Json which doesn't have the CVE

A better solution is to use central package management with transitive pinning and only add a <PackageVersion> element for the updated transitive dependency. That way it stays a transitive dependency instead of becoming a direct one.
But even if you do it that way you still have to manually check it all the time in the future because the tooling doesn't support that very well. See https://github.com/NuGet/Home/issues/13646

I have had to disable warnings as errors for vulnerabilities because I’ve got warnings from dependencies 3-4 levels deep.

I agree that Microsoft should release updated package versions for all their packages when a dependency is updated because of a security problem.
But if you want to ignore those warnings for now - which seems to be the case since you disabled warnings as errors - you can set <NuGetAuditMode>direct</NuGetAuditMode> to ignore security warnings from transitive dependencies. Documentation: https://learn.microsoft.com/en-us/nuget/concepts/auditing-packages#configuring-nuget-audit

But if you want to ignore those warnings for now - which seems to be the case since you disabled warnings as errors - you can set <NuGetAuditMode>direct</NuGetAuditMode> to ignore security warnings from transitive dependencies. Documentation: https://learn.microsoft.com/en-us/nuget/concepts/auditing-packages#configuring-nuget-audit

Thanks.
I’ll give it a go in the morning. I tried disabling for the advisory url but it didn’t work because the projects and SDK is .NET 8 but I have .NET 9 installed. It worked when I changed to NET 9 but I can’t roll out a NET 9 app yet. Just finishing off Framework 4.7.# to NET 8 and have to move to centralised package versioning to fix dependency mismatch on a 300 project solution.

@SimonCropp

it seems a weird to suggest that every consumer of the SqlClient (i assume there a many at 348.6K downloads per day) apply a hack, instead of making one fix in this codebase and fix it for everyone.

First, I never said SqlClient shouldn't themselves update to a newer version that doesn't have a CVE - I believe they should. My answer was to @dlatikaynen's comment just above, that he'd consider turning off warnings-as-errors because of this: that's really unnecessary when one can simply make the problem go away by taking a direct dependency instead. The problem is that many users somehow miss the fact that they can take direct dependencies, and think that they're stuck until SqlClient (or whatever intermediate library) updates.
It's also important to make clear that there's no "hack" being suggested here: taking a direct dependency on a transitive dependency achieves exactly the same thing as SqlClient doing the update on their side. It's not ideal to have everyone do that, but it's a very reasonable workaround in the meantime.

The problem is that many users somehow miss the fact that they can take direct dependencies, and think that they're stuck until SqlClient (or whatever intermediate library) updates.

This is a hacky work-around. There is literally no point in Microsoft implementing transitive dependencies if we are required to take direct dependencies to fix CVE issues.
Microsoft is 100% at fault here for wasting time implementing features to ignore advisory urls, disable errors, etc, instead of having a default or a setting to automatically take the latest major/minor/build version of a transitive dependency instead of taking the lowest 100% of the time.

@phillip-haydon not every library will be able to bump a dependency and release at the exact moment that one of its dependencies has a CVE published against it - every time that happens. It's fine to ask SqlClient to update (and they should), but it's also completely fine (and not at all a hack) for an application to temporarily reference a transitive dependency with a CVE.

instead of having a default or a setting to automatically take the latest major/minor/build version of a transitive dependency instead of taking the lowest 100% of the time.

You're basically talking about floating a dependency version, and that is a really bad idea for quite a few reasons.

@roji could you expand on why it should be easier for the consumer of a library to validate the library with a new version of a dependency of the library than it would be for the auther of the library?
What prevents a library author from bumping the dependency, if it is not validation of the new version? Even a one man team should be able to run the test suites and publish a new version withing hours, let alone a corporation the size of microsoft.

What prevents a library author from bumping the dependency, if it is not validation of the new version? Even a one man team should be able to run the test suites and publish a new version withing hours, let alone a corporation the size of microsoft.

That is absolutely not how things work, especially not in a large corporation. Releasing .NET, for example, is a long process with lots of process and verification - it simply isn't possible to "just release" within a few hours.

Without validating the library with the new version of the dependency, this is the textbook definition of hack.

It is not.
SqlClient is does not specify a single, specific version of its own dependencies; it could do that via nuget, saying that it will only work with a specific version, but instead it does the default thing of requiring only a minimum version. It is common and accepted for people to bump patch (but not major) versions of a transitive dependency, because e.g. a bug is fixed in that transitive dependency and a newer version of the direct dependency hasn't been released (remember, this isn't just about security). For example, with EF, it's fine for people to depend on a newer version of SqlClient than is specified by EF's SQL Server provider; the compatibility bar is generally very high.
And regardless, ultimate validation that everything works is your responsibility as the app developer. Even if SqlClient was tested to be compatible with a certain version of its own transitive dependency, upgrading to that transitive dependency may cause issues in your own application in various ways.

Stepping back... Everyone, this isn't the place to debate general .NET practices around transitive dependencies and CVEs. Nobody is saying that SqlClient shouldn't update its dependencies to avoid having CVEs in its transitive dependency graph; but this simply isn't something that can always happen immediately.
You certainly have the right to expect SqlClient (and any other maintained library) to bump its own dependency versions and release, so that there are no transitive CVEs. But you cannot expect that to happen 5 minutes after a CVE is published.


Is there a good way to specify struct return types for CEnv c_func_defs?

I want to add a function to a CEnv environment that returns a struct.
cffi exposes the ffi.new() (doc) function to allow array and struct types to be defined. Otherwise, ffi.cdef won't understand the struct type in the function signature. Is there some good way to pass the struct name to CEnv so that it will be loaded in time for the ffi.cdef of the function signature to catch it?

I apologize, I was misunderstanding how cffi works. In order to define a custom struct you need to make a cdef call defining the full struct ahead of time.
super.__init__(
  ...,
  c_func_defs=["struct s {int a; float b;};", "struct s func();"]
)


pretty-printer: consistently print nested tuples with (,) syntax

The tuple printer p_tmTuple was calling p_tmEq for values inside the tuple, but p_tmEq was printing nested tuples as Mktuple2. I've added a check inside p_tmEq to call back to the tuple printer, which matches how dependent tuples are printed too.

Nice Amos, thank you!


Farm Designer Additions

Farm Designer:

Add slider to map image settings menu to quickly view photos taken during a single day.

Coverage increased (+0.1%) to 87.722% when pulling cac15db5b68dd480a4c68567817710f930e2f171 on gabrielburnworth:master into 49c61134daa983cd6b108ccd9737379ac85f04ed on FarmBot:staging.


Cannot reference JS asset files in Liquid

Followup to #407 and #408
Problem
There is currently a bug when including a script asset reference, e.g. <script src="{{ '../assets/scripts/modernizr.js' | asset_url }}"></script>, where the src gets transformed into {{ [object Object] | asset_url }} and not {{ 'modernizr.js' | asset_url }}.
Replication steps
How to replicate the problem. Screenshots or video?
More Information
This transformation happens so that in dev build (slate-tools start) we can reference the localhost, and then in prod build (slate-tools build) we can reference the lib uploaded on the Shopify CDN. To avoid this transformation and always reference the Shopify CDN, developers could use double quotes, e.g. {{ "../assets/vendors/modernizr.js" | asset_url }}, but we should also support the above approach.

Right now working with static JS files does feel a bit clumsy.  The other thing to note about the scenario above is that it seems like you would have to name the file modernizr.js.liquid so that it uploaded with slate-tools.  Otherwise yarn start will assume that the file is being served locally from /dist.
Personally I would like to have a way to work with dependancies that are completely separate from bundled files.  An example of this would be using a package like lazysizes.  LazySizes needs to load as soon as possible with async, so including it in theme.js would not make sense with the files being deferred (#437).
Would it be realistic to have a build process that could do the following?

Load a file like lazysizes.js from vendor/static
lazysizes.js includes the various required plugins
Inject a script tag with lazysizes.js as async

Wait so for my own sanity, it's currently impossible to include a script from the assets folder, right?
Like the tutorial for multiple currencies is currently not actually achievable in Slate?

@MitchEff -- correct. In the mean time, just import that file like any other JS file into your main theme JS file:
src/assets/layout/theme.js
import 'jquery.currencies.min.js';

It also seems to be stripping stylesheet_tag and script_tag filters.
input
{{ '../assets/static/some-asset.js' | asset_url | script_tag }}
{{ '../assets/static/some-asset.scss' | asset_url | stylesheet_tag  }}

output
https://localhost:8080/some-asset.js
https://localhost:8080/some-asset.scss

this seems like it's still an issue right?
i have a rather complex workflow and i just need to send along some js that runs along side the webpacked js.

@numediaweb can you show how you're referencing the file in your theme.liquid?

@sebbean I fixed it by switching single quotes to double.. wasn't easy to find though in documentation :(

@numediaweb Where did you put your source css or js sources? I've tried putting them in various locations in the src folder, such as "src/assets/scripts", "src/assets/templates", "src/assets/static", but the slate-tools watcher doesn't do anything with them. I've also tried moving them to the "/dist" folder.
I've only found two options that work, but they aren't the best solution:
a) Compile JS using CodeKit and upload via the web interface (too slow). Haven't found a way to compile JS via yarn / slate-tools yet.
b) Insert CSS into "src/assets/styles/theme.scss" as @import statements. I've also found I can insert css into theme.scss.liquid. Is there a way to insert a new css link though?
All of this was pretty straightforward with Slate v0, but Slate v1 is throwing me for a loop.

@callaginn i'm putting them in my static folder actually src/assets/static/vueapp.js
seems to work ok - only on a full deploy.
npm start doesn't seem to see any file changes in there while i'm deving

Assets have been simplified in #850 and the change is now available in v1.0.0-beta.12.
Docs that have also been updated:
https://github.com/Shopify/slate/wiki/Slate-themes
https://github.com/Shopify/slate/wiki/Template-and-layout-bundles
https://github.com/Shopify/slate/wiki/Local-development


JAVA-1794: Driver tries to create a connection array of size -1

I'll look on branch 4.x to see if it suffers from a similar issue

@tolbertam as this is a small change I just made made an amend.

I've already signed the CLA. Ping me if I need to take any further action!

I've already signed the CLA. Ping me if I need to take any further action!

Hrm, something must be wrong with our CLA bot, we're looking into it, thanks

Rebased on 3.x and updated changelog and force pushed, will merge if travis build goes well :+1:


Provide documentation on the embed functionality e.g. data.gov.uk

Currently there's no standalone documentation on the embed functionality. As a developer asked to integrate certificates into a data store I can't see what the options are, or any examples.
The embed codes are only available to the owner of a published certificate.

I may be off topic here but is this of any use https://stephen-gates.github.io/certificates/DisplayYourOpenDataCertificate2.pdf

This to be revisited as part of the overall documentation work.


failure to use the rusqlite rust crate - error: linking with cc failed: exit status: 1 (...) cannot find -lsqlite3: No such file or directory

Describe the bug
I have a rust project that uses rusqlite. I get the error when I write the "use rusqlite:: ...." line, but it compiles fine if i simply put it in the Cargo.toml file without using it.
The compilation error is quite lengthy but the first and last lines are most relevant:
https://pastebin.com/Gy1kHUSY
error: linking with cc failed: exit status: 1
....
....
= note: /nix/store/rq6bh3qfrqnyqwik0w3q6w180zg3w2pa-binutils-2.38/bin/ld: cannot find -lsqlite3: No such file or directory
collect2: error: ld returned 1 exit status
Steps To Reproduce
Steps to reproduce the behavior:

add my packages that might be relevant in my default nix  config: cargo, cmake, gcc
clone the project i tried to run https://github.com/TBS1996/flash-tui
cargo run

Metadata
[user@system:~]$ nix-shell -p nix-info --run "nix-info -m"
>

i havent used nix-shell, ive just edit the main config on nixos

You have a dependency on libsqlite, so you need the libsqlite package in your build environment.  You need to use nix-shell or similar for this, as libraries cannot be globally installed in NixOS configuration.


Extracting component to its own npm package

I had been working on a project for a while, and decided that one of the components was generalised enough to go into its own package, that I would then include in my main project. The component wasn't done, but it made more sense that it be separate from the main project. I tried to include the package into my main project using npm link. The package is written with react and es6, but has no need for HRM because its just a library. Because the HRM babel preset was not present in the package, I got this error while trying to run npm start in my main project:
Module build failed: Error: Couldn't find preset "react-hmre" relative to directory ".../local_package/lib"

This is not an issue with this boilerplate, but with the babel loader and webpack, there are many issues open regarding this. They also mention a workaround, which worked for me (kind of).
By changing line 61 in internals/webpack/webpack.dev.babel.js, from presets: ['react-hmre'], to presets: [require.resolve('babel-preset-react-hmre')], I am now able to work on both my local npm package and my main project (which uses this boilerplate) with the main project running with hot reloading for both the main project and package. I also had to add my local project to the dllPlugin::exclude packages. Obviously this only works for the HRM preset, and the same would have to be done to other presets as well, but this worked for me.
The key thing here is that now I can write my local package in es6 without having to build the package whenever I make a change, so in the package.json of my local package I can have "main": "src/index.js" instead of "main": "lib/index.js".
This fails when trying to build the package due to previously mentioned issues in webpack. Also, the main issue for me was ease of development.
I think this should be documented somewhere (if I missed this in the docs on this, I apologise), since one of the most compelling points of the self contained containers/components to me was that you could easily extract them from the project into their own package.
My solution isn't perfect, but I would love to get input on how this could be improved, or what a better way of working on local packages in parallel would be.

Absolutely agree, this warrants a discussion! I don't have time to dive in at the moment, but I would love for you to submit a PR adding docs and fixing bugs to make this easier to do!

Sure thing, I'll do what I can!

I've created a PR #979 that adds some the documentation and fix for what I've described above.
There are still a couple of issues and I don't have much experience with webpack to know what causes some of them. The development process using my fix is very nice, webpack updates the bundle each time the linked package is changed.
A minor annoyance is that each time you want to publish the separate package to the npm registry, you've got to make sure to change the src/index.js in the package.json to lib/index.js. This can get very annoying. One solution would be to write a simple sed script that would change it before publishing, but that's limited to unix (I don't believe Windows has sed), so that might be able to be improved.
The big thing is that the build process fails when trying to compile a linked module. I'm actually not sure what's the cause for this, as far as I can tell, it's either webpack or babel. The best solution I've come up with is to remove the symlink from node_modules and do a quick npm install to fetch the latest published version of the package. This is, again, very annoying, but I don't run the build command very often. This should probably be improved, because I imagine if you build often, this would become more than a little bit annoying, but I'm not sure how I would go about fixing this.
Any suggestions or feedback would be welcome.

npm link is a good choice, but this solution can't work well.
Look this babel/babel-loader#149, webpack/webpack#1866.
It's seem only<EMAIL_ADDRESS>can work, but when I try it in<EMAIL_ADDRESS>it will lead to more errors.
Now I have try serveral methods,like give a new presets in package.json or webpack.dev.babel.js but my third package still can't find react

Module not found: Error: Can't resolve 'react' in /Users/xxx/third/package/index.js;

Yes, I was wondering why I wasn't getting this error but, this should be easily fixable, as it's the same problem I ran into with HRM. I've seen the issues you linked, and the fix should apply to this as well. It's just a matter of finding where to stick the require.resolve in the config files.
This may be tricky because some of the presets and plugins are specified in the package.json from which (as I understand), babel reads directly, so that may be an issue. Perhaps moving those settings to the webpack.dev.babel.js with .map(require.resolve) may fix the issue?

@pavlin-policar Thanks for reply;
My webpack.dev.babel.js looks like this:
  babelQuery: {
    // presets: ['react-hmre'],
    // http://stackoverflow.com/questions/34574403/how-to-set-resolve-for-babel-loader-presets/
    presets: [
      'babel-preset-es2015',
      'babel-preset-stage-0',
      'babel-preset-react',
      'babel-preset-react-hmre'
    ].map(require.resolve),
    //plugins: ['babel-plugin-transform-async-to-generator'].map(require.resolve)
  },

and It will lead to Module not found: Error: Can't resolve'react' in and when i remove my third package and just run a base example, lead to other error in brower:
store.js?fa02:12 Uncaught TypeError: (0 , _reduxSaga2.default) is not a function
I don't install any packages in my third package, node_modules is empty.

@bugkiwi This last bug doesn't seem related to this particular issue. I know there are some issues with the current release where the dependencies are outdated and cause errors, but those are easily fixable.
I have, however, played around with removing some of the babel presets to the webpack.base.js, since I don't think there's a way to change how webpack resolves relative imports from there.
This function
const resolvePreset = (preset) => {
  if (Array.isArray(preset)) {
    const [p, ...opts] = preset;
    return [require.resolve(`babel-preset-${p}`), ...opts];
  }
  return require.resolve(`babel-preset-${preset}`);
}

along with changing the babel options in webpack.base.js to
    {
      test: /\.js$/, // Transform all .js files required somewhere with Babel
      loader: 'babel',
      exclude: /node_modules/,
      query: {
        presets: [
          ['es2015', { modules: false }],
          'react',
          'stage-0',
          ...(options.babelQuery ? options.babelQuery.presets : [])
        ].map(resolvePreset),
        plugins: [],
      }

I removed all the changes I made in webpack.dev.js and removed the options from package.json and this worked. I haven't tested it for plugins, though I imagine it should be relatively straightforward.

@pavlin-policar Yeah, I had try give a simple pure js without any dependencies in my third lib, everything worked well.
I think if I give my third lib a completely package, and compile them, everything should work well; but i don't have time to do that, and now i just use a copy on my apps.When I have some free time, I will try that again;

A few days ago I tried it, all work well.
Before there are some problems because I cited the wrong lead, and I'm very sorry.
Thank you @pavlin-policar :)

I'm not very familiar with Babel, but why are some things configured in package.json while one thing is configured in webpack.dev.babel.js#L45?

I'm not very familiar with Babel, but why are most things configured in package.json with the exception of one thing configured in webpack.dev.babel.js#L45?

If someone wants to transpile a server with babel also, and today it happed: #1170, hot reloading won't work in that environment.

I'm not very familiar with Babel, but why are most things configured in package.json with the exception of one thing configured in webpack.dev.babel.js#L45?

That's a great point actually. We should move that back to the package.json in dev!

I had to do that in a universal app, but maybe here it's fine as module.hot is only used on the client?

Documented by the amazing @pavlin-policar in #979!

I've also extracted a component to a separate package and used a slightly different approach to preserve hot reloading for the sources of that component:

I'm using webpack's resolve.alias rather than npm link for referring to the component.  (This was not for a deep reason but just because I was not aware of npm link.)
The idea was to define the alias in webpack.dev.babel.js, whereas webpack.prod.babel.js does not contain the alias.  The alias points to the component's src directory.

To make this work I had to change webpack.base.babel.js to merge options.resolve into its own resolve parameter.  (The standard code from react-boilerplate ignored options.resolve.)

BTW: webpack.base.babel.js implements the merging of the parameters from the specific configuration with its own base-configuration parameters.  In this situation it would have been more comfortable if the merging were implemented in webpack.(dev|test|prod).babel.js. webpack.base.babel.js should just export its parameters as a data object.  (But there might be other situations where the current behavior is more comfortable.)

I also got the error message about the react-hmre preset as in the original post of this issue.  (I actually found the current issue by googling for the error message.)  @pavlin-policar's solution with [require.resolve('babel-preset-react-hmre')] worked for me as well.  Thanks a lot!

I also added the alias to webpack.test.babel.js to avoid eslint errors about unresolvable imports. (In package.json eslint is configured to use that file for module resolving.)

Hot reloading from the extracted component works nicely.  Also there is no need to tweak the "main" parameter of the component's package.json since my alias points directly to the source directory.  And finally the approach does not involve my (and my colleague's) global npm repository.
However, my experience is limited for now:

My extracted component has only a single dependency.  (And in particular it does not depend on React.)  So I do not yet know how well the component's dependencies interact with the main app's dependencies.
I'm not yet actually creating prod builds.

Maybe this approach is useful for somebody.  If you are interested I can go into more detail or report about how it's going when I'll extract more complex components.


feature: Fail fast - fixes #178

A POC implementation of https://github.com/awaitility/awaitility/issues/178 - fail fast. Seems to work ok. Review?

Not sure I used the appropriate factory setup / options setup

This is cool! Great work @astubbs, I can really see the usefulness of this. Is there anything in particular we ought to discuss/change before I merge it?

Great! Just a couple of questions - did I use the ConditionFactory correctly?
Also, what about including a message/explanation for the fail fast? or do you think this is enough? e.g:
 .failFast("System has crashed", ()->testForCrash());

Actually, adding a reason I think is quite a good idea:
.failFast(()->testForCrash(), ()->getCrashReason());
That way it's easier as in your logs you may not have to scroll up to find the exception that crashed your system for example..

Ok, new commit gives the following. Thoughts?:
                .failFast(failFastCondition, () -> new Exception("System crash")).until(() ->
                        ai.get(),
                equalTo(-1) // will never be true
        );

org.awaitility.core.TerminalFailureException: Fail fast condition found!

	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:104)
	at org.awaitility.core.AbstractHamcrestCondition.await(AbstractHamcrestCondition.java:86)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:916)
	at org.awaitility.core.ConditionFactory.until(ConditionFactory.java:622)
	at org.awaitility.FailFastTest.fail_fast(FailFastTest.java:39)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
	at java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
	at java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
	at java.base/java.lang.reflect.Method.invoke(Method.java:566)
	at org.junit.runners.model.FrameworkMethod$1.runReflectiveCall(FrameworkMethod.java:50)
	at org.junit.internal.runners.model.ReflectiveCallable.run(ReflectiveCallable.java:12)
	at org.junit.runners.model.FrameworkMethod.invokeExplosively(FrameworkMethod.java:47)
	at org.junit.internal.runners.statements.InvokeMethod.evaluate(InvokeMethod.java:17)
	at org.junit.runners.ParentRunner.runLeaf(ParentRunner.java:325)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:78)
	at org.junit.runners.BlockJUnit4ClassRunner.runChild(BlockJUnit4ClassRunner.java:57)
	at org.junit.runners.ParentRunner$3.run(ParentRunner.java:290)
	at org.junit.runners.ParentRunner$1.schedule(ParentRunner.java:71)
	at org.junit.runners.ParentRunner.runChildren(ParentRunner.java:288)
	at org.junit.runners.ParentRunner.access$000(ParentRunner.java:58)
	at org.junit.runners.ParentRunner$2.evaluate(ParentRunner.java:268)
	at org.junit.runners.ParentRunner.run(ParentRunner.java:363)
	at org.junit.runner.JUnitCore.run(JUnitCore.java:137)
	at com.intellij.junit4.JUnit4IdeaTestRunner.startRunnerWithArgs(JUnit4IdeaTestRunner.java:69)
	at com.intellij.rt.junit.IdeaTestRunner$Repeater.startRunnerWithArgs(IdeaTestRunner.java:33)
	at com.intellij.rt.junit.JUnitStarter.prepareStreamsAndStart(JUnitStarter.java:220)
	at com.intellij.rt.junit.JUnitStarter.main(JUnitStarter.java:53)
Caused by: java.lang.Exception: System crash
	at org.awaitility.FailFastTest.lambda$fail_fast$2(FailFastTest.java:39)
	at org.awaitility.core.ConditionAwaiter.await(ConditionAwaiter.java:103)
	... 26 more

I'm also adding two convenience methods to construct from a string directly

Happy new year @johanhaleby ! Do you have any further input on this feature? I think it's super useful now after using it for a while (and having to comment it's use out as it's not in upstream yet :). Or can you delegate to another maintainer?

Happy new year @johanhaleby ! Do you have any further input on this feature? I think it's super useful now after using it for a while (and having to comment it's use out as it's not in upstream yet :). Or can you delegate to another maintainer?

@astubbs Sorry for being so slow with everything. I've spent quite a lot of free time on other open-source engagements and I've been sick with long-covid for over 4 months :(

@astubbs Would it make sense to add some overloading methods such as failFast(<condition>, "my error message") and perhaps just failFast(<condition>) that will give you a default error message?

Also I wonder if perhaps it would make sense to expand to make use of hamcrest matchers? E.g. failFast(() -> someMethod.someInt(), greaterThan(20))? We could save this for the future though :)

Yet another thing, is it really that useful to supply you error using a custom exception? I.e. is failFast<condition>, () -> new Exception("description") really all that valuable if you have failFast(<condition>, "my error message")?
Also, maybe we should use ThrowingCallable instead of Callable so that the fail fast condition fails if the callable throws an exception?

And to make the API better interact with Kotlin I think I would perfer to have the error message before the condition, i.e.: failFast(<condition>, "my error message"). This way you can do like this in Kotlin:
await().failFast("my error message") {
      sometThing.someValue() == 10
}
..

@astubbs Sorry for being so slow with everything. I've spent quite a lot of free time on other open-source engagements and I've been sick with long-covid for over 4 months :(

Oh noo! So sorry to hear that :/
This time I'm sorry for MY delay - been moving countries and houses several times... doh.

@astubbs Would it make sense to add some overloading methods such as failFast(<condition>, "my error message") and perhaps just failFast(<condition>) that will give you a default error message?

Yes, definitely..

Also I wonder if perhaps it would make sense to expand to make use of hamcrest matchers? E.g. failFast(() -> someMethod.someInt(), greaterThan(20))? We could save this for the future though :)

Yeah that sounds cool.

Yet another thing, is it really that useful to supply you error using a custom exception? I.e. is failFast<condition>, () -> new Exception("description") really all that valuable if you have failFast(<condition>, "my error message")?
Also, maybe we should use ThrowingCallable instead of Callable so that the fail fast condition fails if the callable throws an exception?

Yes absolutely. For dynamic failure reasons.
I see you've gone ahead and changed it. That's a shame. The failure reason can be dynamic. That is why the reason is a callable, and not a plan string. It's a shame you didn't leave the original in at least as well. I.e. failure reason cannot be known at compile time.
Does that make sense? Or do you need an explicit example?
Can you add it? (My reasons are all dynamic).

And to make the API better interact with Kotlin I think I would perfer to have the error message before the condition, i.e.: failFast(<condition>, "my error message"). This way you can do like this in Kotlin:
await().failFast("my error message") {
      sometThing.someValue() == 10
}
..

Oh nice catch. Probably the same for Scala - awesome.

ping @johanhaleby =D

Dynamic reasons are also very useful when there can be several different conditions which can cause a fail fast.

FYI Just to quickly clarify:
.failFast(...,
 ()-> subSystem.hasFailed(),
 ()-> "Subsystem XYZ has failed, due to " + subSystem.getFailureCause()
)

ping @johanhaleby ?

ping @johanhaleby ? any chance we can improve this? Might open a new PR for the adjustment I suppose..

Created a new issue to track dynamic fail fast reason: https://github.com/awaitility/awaitility/issues/240


RFC: Implement parent items with child traits

This RFC allows to implement functions, associated types and associated constants to be defined while implementing a child trait.
Therefore you have to define them in a special way, using the parent traits.
Rendered

cc @withoutboats @nikomatsakis

@porky11
The motivation section is rather brief and I'm not sure I understand it. I think I get the ergonomics point - if your type has a lot of parameters with bounds and such it can be quite annoying to reiterate this. However, "implied bounds" alleviates a lot of this pain.
This second motivation is intriguing, but I don't understand what you mean:

being able to change trait hierarchy by splitting types as a crate maintainer without breaking anything.

Can you elaborate on this, maybe show some examples?

@withoutboats
My text already contains examples.
But maybe they are too abstract, so here another one:
Assuming, you define a trait for objects moving in space. You can access the position, the velocity and displace the object by some delta and accelerated by some force:
trait Moving<T> {
    fn pos(&self) -> T;
    fn displace(&self, delta: T);
    fn vel(&self) -> T;
    fn accelerate(&self, force: T);
}

Now you use this trait in many places, maybe even other people use this crate.
Then you see, other than you thought first, that it's useful to have a trait for some objects, that don't have a velocity, but have a position and can be displaced:
trait Positional<T> {
    fn pos(&self) -> T;
    fn displace(&self, delta: T);
}

But now you would also like to be able to use the functions, you define for your Positional trait for all objects, that are Moving.
You could define the function for all Movers:
impl<M,T> Positional<T> for M where M: Moving<T> {
    fn pos(&self) -> T {
        self.pos()
    }
    fn displace(&mut self, delta: T) {
        self.displace(delta);
    }
}

This also works for most cases. But it's not, what you would like to have. If it wouldn't break anything, you would have used different design, but when you don't want to break, you cannot change it anymore.
This design also has some more problems:
Assuming you use Positional and Moving in the same module:
mod test {
    use Mover;
    use Positional;
    fn test() {
        let p = MyPositional{…}
        let m = MyMover{…}
        println("{:?}, {:?}", p.pos(), m.pos());
    }
}

This would cause an error like that: error[E0034]: multiple applicable items in scope
This could not happen with the other approach.
Another example is, you have multiple traits, that you want to implement a new parent trait for, when you found, that multiple traits share some functions, here a Drawable, which also has a position and can be displaced.
Maybe also allowing this would be more useful, but I don't think, this will work soon, if at all.
And when you create the Drawable trait afterwards, it won't be a problem, since you can just make the Positional trait a parent of it.
I hope this helps to understand.

@nikomatsakis
As I told here, this choice may be preferable. It also is more like the default syntax for using and will still work, if something like partial impls are supported.
Your suggestion to only allow this inside a single crate seems like a good restriction.

I could imagine being explicit impl<..> (TraitA<..>,TraitB<..>,TraitC<..>) for Type<..> where .. perhaps, with perhaps trait MyTraits<..> = (TraitA<..>,TraitB<..>,TraitC<..>); providing this.

@burdges Why (TraitA, TraitB) syntax instead of TraitA + TraitB?

Just my mistake

@burdges
This may be useful for ergonomics, but won't fix the main problem of splitting traits into multiple traits

While I understand the rationale behind the RFC, I don't think this helps understanding the code in any way, because now one must remember the super traits of all implemented traits at all time. I feel like this optimises for things that are just a bit painful to write when they are implemented the first time, but will hinder understanding those very same impls a few weeks later.
My experience implementing a massive amount of traits for a massive amount of data types in Servo and in particular Stylo makes me conclude that this is unneeded and potentially harmful.

I was thinking about this the other day. I would like to propose an alternative. I think we should generalize the syntax of impl so that it takes a list of bounds, rather than a single trait ref:
impl<..> Trait1<P1..Pn> + Trait2<P1..Pn> for P0

This would be exactly equivalent to independent impls:
impl<..> Trait1<P1..Pn> for P0 { .. }
impl<..> Trait2<P1..Pn> for P0 { .. }

where the generic parameters and items are divided accordingly.
There are some things to work out:

What to do if both traits define the same item? (Easiest answer: error)
Can we cleanly divide up the trait parameters between the two? (I don't see an issue)

If we did this, and we combine with trait aliases, then I think we get a lot of the goals of this RFC. For example, we could (I think) backwards compatibly change
trait Foo {
   fn a();
   fn b();
}

into
trait Foo = Foo1 + Foo2;
trait Foo1 { fn a(); }
trait Foo2 { fn b(); }

Not having something in this space is why .Net has IList that doesn't implement IReadOnlyList, so I feel like having something allowing splits like that is valuable, though I don't really have an opinion on whether exactly what's proposed here is the way to do that.
For example, I wish we could generalize .clone_from() in some way, which might need making Clone a combination of something else in some way.

@rfcbot fcp postpone
My feeling on this RFC is that it is tackling the right problem but the design is not quite there yet. Therefore, I'd prefer to postpone in favor of more discussion on internals or elsewhere. I do want to thank @porky11 for the interesting idea, though.
Some concerns about the specific form of this RFC:

Adding another knob to supertraits (trait Foo: use Bar) feels like it is a pretty heavy-weight change; we had better be sure it's worth it.
I'd like to give end users the choice to implement the component traits independently (per @petrochenkov's point).

Personally, I'm enthusiastic about this direction of being able to leverage trait aliases, but I'm open to other ideas. It certainly has its complications too: for example, I just realized that the trait alias approach runs into the semver concerns that @cramertj mentioned, which seem more problematic in that context.

Closing per completed FCP with a motion to postpone.
Thanks to @porky11 for the RFC =)


ignore drift in rds.Cluster and rds.Instance due to engine_version diff arising out of automanaged upgrades

Description of your changes

Fixes https://github.com/crossplane-contrib/provider-upjet-aws/issues/1504
RDS DB Cluster and Instance resources configured with autoMinorVersionUpgrade: true will have RDS managed service upgrade the DB cluster/instances automatically to new available minor/patch versions during the configured preferred maintenance window. the provider-upjet-aws-rds controller currently, detects this auto version upgrade as a drift from the desired spec (if the spec.forProvider.engineVersion is specified in the resource spec) and ends up doing an endless diff and update cycle, resulting in exhaustion of the RDS API calls quota. AWS RDS doesn't allow engine version downgrades. So the update calls keep getting returned with error.
This change customizes the terraform InstanceDiff for Cluster and Instance rds resources to account for the above automanaged upgrades by ignoring the engine version diff, if the desired spec version is lower than the external's actual version.
I have:

[X] Read and followed Crossplane's contribution process.
[X] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR if necessary.

How has this code been tested

unit tests
Manually tested by:

created a rds cluster Cluster.rds.aws.upbound.io managed resource with spec.forProvider.engine_version: 8.0.mysql_aurora.3.06.1 with autoMinorVersionUpgrade: true
Instead of waiting for the RDS Managed service to auto upgrade to latest 8.0 release version during the next maintenance window, manually upgraded the engine_version in RDS Console/UI to 8.0.mysql_aurora.3.07.1. the database cluster engine version gets updated successfully.
verified the cluster.rds managed resource remains synced: True, without any previous endless drift->update cycle behavior.

Credits: this is reusing the engine version util code from https://github.com/crossplane-contrib/provider-aws/pull/1765

/test-examples="examples/rds/v1beta1/instance.yaml"

/test-examples="examples/rds/v1beta1/cluster.yaml"


not able to use the ssh tunnel to connect to a remote database

System information:

Operating system (distribution) and version - Mac M1 2021 Montery Macbook pro
DBeaver version
Additional extensions

Connection specification:

Database name and version - Postgresql
Driver name - org.postgresql.Driver
Do you use tunnels or proxies (SSH, SOCKS, etc)? ssh

Describe the problem you're observing:
I'm having trouble connecting to my remote amazon aws instance.  When i use my terminal:
ssh -i "timescale.pem"<EMAIL_ADDRESS>i am able to connect via my terminal.
In dbeaver, i am getting connection issues
Steps to reproduce, if exist:
Went to SSH and clicked on Use SSH tunnel
Then typed my host/ip: secret.amazonaws.com
Username: ubuntu
Authentication Method: Public Key
Private Key: /Users/me/timescale.pem
Advanced settings: SSHJ.
Test tunnel configuration says its connected.
Then i go to Main tab and put host: localhost, database: example, authentication: database native, username: postgres, password: ******, test connection gives me error "FATAL error, could not write init file"

Hello @mrajancsr,
Thanks for the detailed description.
Could you please attach debug logs? Please see Log files.

There have been no updates on the issue for a long time. If the issue is still present - feel free to reopen it with additional info.


PP-682 Make Resource a POST

WHAT
A brief description of the pull request:

Having the resource accept GET runs the risk of the card number
being printed in access logs. Therefore making this a POST to avoid it.

HOW
Steps to test or reproduce:
WHO
Who should review this pull request:

[x] Developers

👍


ark-curve25519 uses a different encoding than curve25519-dalek

It seems that the following code fails
   type GroupG = curve25519_dalek::edwards::EdwardsPoint;
    type GroupF = curve25519_dalek::scalar::Scalar;
    let mut ark_generator_bytes = Vec::new();
    ArkG::generator().serialize_compressed(&mut ark_generator_bytes).unwrap();
    let dalek_generator_bytes = <GroupG as GroupEncoding>::to_bytes(&GroupG::generator());
    assert_eq!(&ark_generator_bytes, &dalek_generator_bytes);

with error:
assertion `left == right` failed
  left: [88, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 230]
 right: [88, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102, 102]

It looks like we're using a different generator than dalek. Specifically, the test passes with -GroupG::generator(). This issue is to track the issue and make sure that the points are compatible.
The reason for this is to make implementations inter-operable and set a standard for formats that nimue can enforce.

Being fixed in #767


Clarify usage of the TaskPath Parameter

Module:  scheduledtasks
My expectation was that i can pass a TaskPath without any slash. 'ThePathName'
Got an Error
So I tried an TaskPath with an Slash in front '\ThePathName'
Got an Error
i never, never thought that i have to provide a slash in Front and in back. '\ThePathName'
Even the Examples are not clear because they use an Star ...  '\ThePathName*'
so please clarify usage of the TaskPath Parameter

@Kriegel. Which article are you referring

In the past the Articles got referenced automatically, because I have started the issue from the Article.
But in this case i must not reference a single article,
because many cmdlets of the PowerShell  scheduledtasks Module (which i have mentioned) are using the -TaskPath Parameter.
here is the one i started from:
https://docs.microsoft.com/en-us/powershell/module/scheduledtasks/get-scheduledtask?view=win10-ps

@Kriegel. taskpath parameter will be with this cmdlet ** New-ScheduledTask**
for more information, see below link
https://docs.microsoft.com/en-us/powershell/module/scheduledtasks/new-scheduledtask?view=win10-ps

@RAJU2529
Following your Link,
at the documenting page of 'New-ScheduledTask' I did not found neither the '-TaskPath' not a '-Path' parameter.
So what should I do with your statement?

@Kriegel , see below page
https://docs.microsoft.com/en-us/powershell/module/scheduledtasks/set-scheduledtask?view=win10-ps

@RAJU2529
Do you ever proof your statements before posting it ?
in your Link to the 'Set-ScheduledTask' cmdlet there is a documentation for the Parameter '-TaskPath' but this documentation is lacking any needful Information.
please see attached Screen shot:

I think ALL documented cmdlets in  Module: scheduledtasks need an overhaul  to clarify the usage of the '-TaskPath' Parameter.
I think to do this overhaul cost less work then this discussion here.

@Kriegel
The issue is under investigation and you will be notified with any changes on the way.
Thank you for providing feedback.

Thank you @e0i @velkovb @tiburd  documentation looks great now!
Better than I excpected!
Stay well!
Live long and prosper.


Data received error on admin page, 403 forbidden

maybe API fetching wrong API on frontend, I've tested backend API and functioning correctly.

Found where the problem is, the issue is fixed


fix(TextField, TextArea): append  ids to aria-described-by

The aria-described-by should not be overwritten by the "character limit" configuration. The correct behaviour should be to append the id to the aria-described-by attribute.
Documentation of aria-describedby from web-docs:
"The global aria-describedby attribute identifies the element (or elements) that describes the element on which the attribute is set. The aria-describedby attribute lists the ids of the elements that describe the object."

hmm, have we missed a potention a11y bug?
Looking closer at the implementation in InputWrapper for characterLimit. The describedBy is always set to be characterLimitDescriptionId, even though users have not activated this feature for their text field/area.

Also begs to question if  aria-describedby="" is a valid value. I would think the attribute should not be present if it has not value.

Also begs to question if  aria-describedby="" is a valid value. I would think the attribute should not be present if it has not value.

I agree, the best solution here is to refactor the code to avoid setting the aria-describeby instead of an empty string. Looks like screen readers ignore it when it's empty, but I will refactor it anyway. :)

hmm, have we missed a potential a11y bug?
Looking closer at the implementation in InputWrapper for characterLimit. The describedBy is always set to be characterLimitDescriptionId, even though users have not activated this feature for their text field/area. This means that we have an aria-describedby that is pointing to an element that does not exist in the dom, which I believe is invalid. Note under Example here

Nice catch!! It's important that all ids that are set into aria-describedby match some elements within the same document. I will fix this as well. :)

@mimarz I have done a small refactoring and added a few more unit-tests on aria-describedby. :)


python(x,y) doesn't run on Windows 7

From<EMAIL_ADDRESS>on 2010-10-24T00:58:15Z
Plugin 'spyder' was found (Version: 1.1.5)
Traceback (most recent call last):
File "C:\Python26\Scripts\xyhome.pyw", line 21, in <module>
xyhome.main()
File "C:\Python26\lib\site-packages\xy\xyhome.pyw", line 672, in main
form=MainWindow(options)
File "C:\Python26\lib\site-packages\xy\xyhome.pyw", line 130, in init
self.scanstartup()
File "C:\Python26\lib\site-packages\xy\xyhome.pyw", line 561, in scanstartup
default_startup()
File "C:\Python26\lib\site-packages\xy\config.py", line 85, in default_startup
filename=osp.join(STARTUP_PATH, CONF.get(None, 'startup'))

File "C:\Python26\lib\ntpath.py", line 108, in join
path += "\" + b
UnicodeDecodeError: 'ascii' codec can't decode byte 0xc0 in position 9: ordinal
not in range(128)
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=426

From pierre.raybaut on 2010-10-26T04:28:45Z
Summary: python(x,y) doesn't run on Windows 7

From<EMAIL_ADDRESS>on 2010-10-23T23:03:35Z
python(x,y) doesn't run on Windows 7.
When run it in interactive mode console output error.
It seems that cant't process russian symbols in path.
(sorry for bad report, i have accidentally press enter and bug committed. Now i can't change it, only comment)

From pierre.raybaut on 2010-10-27T13:01:42Z
This bug is directly related to Python(x,y) and has nothing to do with Spyder.
I see that you have submitted the same "Issue" on the Python(x,y) bug tracker: this issue will be handle there.
Status: Invalid


handling promises in no-kafka

If i have any errors sending data to my kakfa broker using producer.send() where do i look for it ?
is it returned in .then(result) or in .catch(error) ?

Kafka errors (like wrong/failed partition, etc) are returned in .then as a grand total result of publishing many messages to different topic/partitions pairs (some may succeed while other may fail). Severe errors (such as network errors, etc) are returned as rejected promise and should be processed .catch

Thanks for quick response, i was looking at documentation and found that result returned in then() looks something like this :- [ { topic: 'kafka-test-topic', partition: 0, offset: 353 } ] . If there is any error, other property like "error":"" is added in the object ? or i get completely different response ?

The property error is always there. It is set to null when there is no error.

perfect!
But the typings file doesn't have error,
https://github.com/oleksiyk/kafka/blob/master/types/producer.d.ts#L182
Can we have to update the result interface in typings file to something like below ?
    {
 topic: string;
  partition: number;
offset: number;
error:NodeJS.ErrnoException
  }


Aditya

Title :
Aditya's First PR On TCET OPENSOURSE "HACKER WEEK"
Issue no :

Description
Added Name
Screenshots (if applicable)

Checklist

[x] I have read and agree to abide by the Code of Conduct
[x] I have read and followed the Contributing Guidelines

Please Check


Sentry integration

WHAT
Add Sentry integration for error tracking
WHY
Currently, there is no way to track errors (server is unavailable, etc) in real time, except checking error logs at CloudWatch Logs. It's inconvenient to me.
REF

getsentry/sentry-go: Official Sentry SDK for Go

Now it works well


Where blockchains are stored in Ubuntu?

I asked this question before, and you guys have told me that it was stored in Consensus.md file. But there is one problem. The size of my Consensus.md file is 20kb, very very small, so it cannot be stored there. And currently my blockchain is synced.

.config/Sia-UI/Sia/

Okay thanks I see where it is now.
One more question, is there anyway to move these files to external drive to turn this a cold wallet?

See https://github.com/johnathanhowell/sia-coldstorage


Cannot find package

Hi, when I create the project and generate the image I get this error
Template: https://github.com/openfaas/golang-http-template/tree/master/template/golang-http
Do you have any idea why?
Step 21/36 : RUN GOOS=${TARGETOS} GOARCH=${TARGETARCH} go test ./... -cover
 ---> Running in f56f8b3d9eee
handler.go:7:2: cannot find package "github.com/openfaas/templates-sdk/go-http" in any of:
	/usr/local/go/src/github.com/openfaas/templates-sdk/go-http (from $GOROOT)
	/go/src/github.com/openfaas/templates-sdk/go-http (from $GOPATH)
The command '/bin/sh -c GOOS=${TARGETOS} GOARCH=${TARGETARCH} go test ./... -cover' returned a non-zero code: 1

This is solved by merging https://github.com/openfaas/golang-http-template/pull/58

You can turn on Go modules without any PRs, please see the openfaas docs.


Update AdversarialPatchNumpy for video format

Description
This pull request fixes bugs in art.attacks.evasion.AdversarialPatchNumpy to enable the support of video data.
Type of change
Please check all relevant options.

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

Checklist

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code
[x] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

Codecov Report

Merging #838 (b85b75d) into dev_1.5.2 (654d2d7) will decrease coverage by 0.04%.
The diff coverage is 72.72%.

@@              Coverage Diff              @@
##           dev_1.5.2     #838      +/-   ##
=============================================
- Coverage      64.96%   64.92%   -0.05%
=============================================
  Files            176      176
  Lines          17099    17096       -3
  Branches        3156     3157       +1
=============================================
- Hits           11109    11100       -9
- Misses          4749     4755       +6
  Partials        1241     1241

Impacted Files
Coverage Δ

...asion/adversarial_patch/adversarial_patch_numpy.py
59.93% <72.72%> (-1.11%)
:arrow_down:

art/attacks/evasion/brendel_bethge.py
60.05% <0.00%> (-0.45%)
:arrow_down:

art/estimators/classification/keras.py
75.07% <0.00%> (+0.59%)
:arrow_up:

Codecov Report

Merging #838 (b85b75d) into dev_1.5.2 (654d2d7) will decrease coverage by 0.04%.
The diff coverage is 72.72%.

@@              Coverage Diff              @@
##           dev_1.5.2     #838      +/-   ##
=============================================
- Coverage      64.96%   64.92%   -0.05%
=============================================
  Files            176      176
  Lines          17099    17096       -3
  Branches        3156     3157       +1
=============================================
- Hits           11109    11100       -9
- Misses          4749     4755       +6
  Partials        1241     1241

Impacted Files
Coverage Δ

...asion/adversarial_patch/adversarial_patch_numpy.py
59.93% <72.72%> (-1.11%)
:arrow_down:

art/attacks/evasion/brendel_bethge.py
60.05% <0.00%> (-0.45%)
:arrow_down:

art/estimators/classification/keras.py
75.07% <0.00%> (+0.59%)
:arrow_up:


Bug: invalid window-id when using zen-mode and/or maximize-window on close-event

When moving the mouse over an lsp-message in a maximized or zen-mode window/pane I get the desired floating-window with it's corresponding message.
Bug:
When moving the mouse away, the window doesn't disappear, instead I get an error:
zen-mode-error:
E5108: Error executing lua: .../share/nvim/lazy/hoverhints.nvim/lua/hoverhints/init.lua:279: Invalid window id: 1000
stack traceback:
        [C]: in function 'nvim_set_current_win'
        .../share/nvim/lazy/hoverhints.nvim/lua/hoverhints/init.lua:279: in function 'check_mouse_win_collision'
        .../share/nvim/lazy/hoverhints.nvim/lua/hoverhints/init.lua:246: in function <.../share/nvim/lazy/hoverhints.nvim/lua/hoverhints/init.lua:237>

maximize-window-error:
E5108: Error executing lua: .../share/nvim/lazy/hoverhints.nvim/lua/hoverhints/init.lua:279: Invalid window id: 1000
stack traceback:
        [C]: in function 'nvim_set_current_win'
        .../share/nvim/lazy/hoverhints.nvim/lua/hoverhints/init.lua:279: in function 'check_mouse_win_collision'
        .../share/nvim/lazy/hoverhints.nvim/lua/hoverhints/init.lua:126: in function 'close_float_window'
        .../share/nvim/lazy/hoverhints.nvim/lua/hoverhints/init.lua:254: in function <.../share/nvim/lazy/hoverhints.nvim/lua/hoverhints/init.lua:237>

While it seems the error is possibly caused by other plugins (I don't know who's responsibility it should be?) ...
I'd love to see you safeguard for this error in this plugin.

Anyway:
I frequently use maximized windows because I focus on a pane while having splits in my layout.
If the error isn't fixed, I guess I'll have to disable/uninstall it and look for another solution to display my lsp-errors,
which would be a pity, especially since this plugin brings value on top of my necessity.
I can't have my workflow disrupted this way, having to manually/:q close my overlay every time I hover an lsp-error in a currently maximized window.
Solution:
Can you safeguard the error and make the window disappear anyway?
Maybe you can keep the window-id of the window in which the last overlay was triggered in some global var???
And remove the window when the caught error occurs - instead of having nvim through an error?

Awesome!!
Just FYI:
Following plugins in my config would be the suspects I guess:
folke/zen-mode.nvim  => zen-mode
anuvyklack/windows.nvim  => maximize (plus auto-slight-resizing & animation stuff via below deps)
anuvyklack/middleclass
anuvyklack/animation.nvim

Hi again, I have pushed a hotfix that I believe should fix these issues. Inform me if that's the case so I can close it.

hey, almost there I think ... or then, actually there ...
But:
In the same context of (split windows and also as of windows in other tabs) I've found another bug.
I shall report in another ticket. Please feel free to close this one.


Space bar not working in Textbox on linux

Describe the bug
on recent nightly builds the TextBox ignores the space bar on linux i.e. you press space and it does not appear in the textbox.
It works on windows and mac but not on linux x64 or linux arm32.
To Reproduce
type a space into any TextBox
Expected behavior
A space appears.
Screenshots
Desktop (please complete the following information):
11.0.999-cibuild0028785-beta
Additional context

Any possible relation to #9623?

the whitespace test here looks a bit suspicious
https://github.com/AvaloniaUI/Avalonia/blob/ac491e798c25426349516fbef3e5a2882e1992d5/src/Avalonia.X11/X11Window.cs#L734


Enable foreign key constraint enforcing in SQLite

By default, you can insert e.g. an involved entry even though the corresponding entry in markers doesn't exist, for example because it was not loaded because it does not have the x and y fields (as in accident<PHONE_NUMBER> from H20081161.
Since the constraint is enforced in Postgresql, this results in an error when loading into the server DB. We should see the same error in SQLite so that the behavior is the same, so as not to make it hard to debug problems.

There's a pragma to enable this constraint enforcement for SQLite. It just needs to be added at the right place...

First we need to update our SQLite to a more recent version (at least 3.6.19).
Then we need to enable foreign key constraints on every connection to the database.


Merging row groups throws panic when rows from one group are empty

Merging multiple sorted row groups will throw a panic when one of the groups returns empty rows during ReadRows, even if n is correctly returned as 0. The reason why we sometimes return empty rows is because we apply filtering during the merge process, and occasionally no rows will match the filter. I think this only happens when the entire row group is empty.
Here is a PR reproducing the issue: https://github.com/parquet-go/parquet-go/pull/67.

The bug is only present when using the WriteRowsTo method because it uses the newly introduced mergeBuffer: https://github.com/parquet-go/parquet-go/blob/0205873edb71c7175cb4abb8f136e574e7a5cdae/merge.go#L111-L118.
Not a long term solution, but temporarily I was able to move forward by wrapping merge row groups in a new struct that looks like this, which basically strips that method:
type rowGroupReaderOnly struct {
	parquet.RowGroup
}

func (r rowGroupReaderOnly) Rows() parquet.Rows {
	return readRowsOnly{r.RowGroup.Rows()}
}

type readRowsOnly struct {
	parquet.Rows
}

@fpetkovski I might be late, did you share the stack trace of the panic somewhere ?

Hey @gernest, there is one stacktrace here https://github.com/parquet-go/parquet-go/pull/61#issuecomment-1721517007.

Am I correct to say that the stack trace you linked is for this issue but the comment is on a thread that is not directly related to this issue ?
I just don't want to confuse things.    For context , there is a reason why we have WriteRowsTo. And Indeed this panic looks interesting  but I'm seeing /go/pkg/mod/github.com/zolstein/segio-parquet-  on the stack trace.  I assume this doens't  reflect how you came across the issue it contains unrelated changes.
So, I can't run your repro yet, If you don't mind can you re run the repro on  based on current master branch and  share the stack trace with me ?

gentle ping @fpetkovski

Sorry @gernest, I missed your last message. I rebased my branch on latest main and ran the test again. Here is the stack trace from the panic, let me know if this helps:
--- FAIL: TestMergeRowGroups (0.01s)
    --- FAIL: TestMergeRowGroups/buffer (0.00s)
        --- FAIL: TestMergeRowGroups/buffer/reproduce_issue_#66,_merging_rows_with_an_empty_row_group (0.00s)
panic: runtime error: index out of range [0] with length 0 [recovered]
	panic: runtime error: index out of range [0] with length 0

goroutine 25 [running]:
testing.tRunner.func1.2({0x177c800, 0xc0000280c0})
	/usr/local/go/src/testing/testing.go:1396 +0x24e
testing.tRunner.func1()
	/usr/local/go/src/testing/testing.go:1399 +0x39f
panic({0x177c800, 0xc0000280c0})
	/usr/local/go/src/runtime/panic.go:884 +0x212
github.com/parquet-go/parquet-go.(*mergeBuffer).read(0xc0022b0000)
	/Users/filippetkovski/Projects/parquet-go/merge.go:463 +0x1ba
github.com/parquet-go/parquet-go.(*mergeBuffer).WriteRowsTo(0xc0022b0000, {0x18d3820, 0xc000515b90})
	/Users/filippetkovski/Projects/parquet-go/merge.go:434 +0x6b
github.com/parquet-go/parquet-go.(*mergedRowGroupRows).WriteRowsTo(0xc000513380, {0x18d3820, 0xc000515b90})
	/Users/filippetkovski/Projects/parquet-go/merge.go:114 +0x1ca
github.com/parquet-go/parquet-go.copyRows({0x18d3820, 0xc000515b90}, {0x276a320, 0xc000513380}, {0x0, 0x0, 0x0})
	/Users/filippetkovski/Projects/parquet-go/row.go:319 +0x3d5
github.com/parquet-go/parquet-go.CopyRows(...)
	/Users/filippetkovski/Projects/parquet-go/row.go:293
github.com/parquet-go/parquet-go_test.copyRowsAndClose({0x18d3820?, 0xc000515b90?}, {0x18df770?, 0xc000513380?})
	/Users/filippetkovski/Projects/parquet-go/parquet_test.go:992 +0xc5
github.com/parquet-go/parquet-go_test.TestMergeRowGroups.func1.1(0xc0004b8ea0)
	/Users/filippetkovski/Projects/parquet-go/merge_test.go:345 +0x505
testing.tRunner(0xc0004b8ea0, 0xc00050eca8)
	/usr/local/go/src/testing/testing.go:1446 +0x10b
created by testing.(*T).Run
	/usr/local/go/src/testing/testing.go:1493 +0x35f

@fpetkovski thanks, I think I have an idea to address this.
I am preparing a patch  to fix this. Will ping you when its ready.


addreserved dispatch during PipeWire screen recording crashes Hyprland

To reproduce:

Start OBS (or any other PipeWire screen recording tool)
Select a full screen capture of a monitor
Issue a command like hyprctl keyword monitor DP-1,addreserved,0,0,0,0 where DP-1 is the same monitor you're capturing
Hyprland crashes.

Crash log: addreserved-while-screen-recording.txt

@jonhoo hey today there was a pipewire update in the arch repos
have you rebooted the machine?
Have you tried the -git version from the AUR?
Or building it on your own
❯ git clone --recursive https://github.com/hyprwm/Hyprland
cd Hyprland
sudo make install

When I screencapture via Firefox (g meet, mozilla gUM )
https://mozilla.github.io/webrtc-landing/gum_test.html
it doesn't crash when I execute the command in a terminal.
PS: love your Rust sessions :)

Oh that's fascinating — it does indeed no longer crash now! I guess we can close this then :tada: How's that for timing.
And thanks, I appreciate it :D Doing a stream on Friday, and am trying to get my new Wayland-based desktop up and running by that time, which includes replicating all of my weird X tools for getting the stream screen just-so.

@jonhoo perfect, always happy to help, especially you 😅
Good luck with your setup.
I was just buffled to see you here because you always had your setup even though people asked and suggested other window managers. 😅
See you on Friday.


Changes for websocket entities

MSFT employees can try out our new experience at OpenAPI Hub  - one location for using our validation tools and finding your workflow.

Changelog
Please ensure to add changelog with this PR by answering the following questions.

What's the purpose of the update?

[ ] new service onboarding
[ ] new API version
[X] update existing version for new feature
[ ] update existing version to fix swagger quality issue in s360
[ ] Other, please clarify

When you are targeting to deploy new service/feature to public regions? Please provide date, or month to public if date is not available yet.
When you expect to publish swagger? Please provide date, or month to public if date is not available yet.
If it's an update to existing version,  please select SDKs of specific language and CLIs that require refresh after swagger is published.

[ ] SDK of .NET (need service team to ensure code readiness)
[ ] SDK of Python
[ ] SDK of Java
[ ] SDK of Js
[ ] SDK of Go
[ ] PowerShell
[ ] CLI
[ ] Terraform
[x] No, no need to refresh for updates in this PR

Contribution checklist:

[x] I commit to follow the Breaking Change Policy of “no breaking changes
[x] I have reviewed the documentation for the workflow.
[x] Validation tools were run on swagger spec(s) and errors have all been fixed in this PR. How to fix?

If any further question about AME onboarding or validation tools, please view the FAQ.
ARM API Review Checklist

[ ] Ensure to check this box if one of the following scenarios meet updates in the PR, so that label “WaitForARMFeedback” will be added automatically to involve ARM API Review. Failure to comply may result in delays for manifest application. Note this does not apply to data plane APIs, all “removals” and “adding a new property” no more require ARM API review.

Adding new API(s)
Adding a new API version
Adding a new service

[ ] Please ensure you've reviewed following guidelines including ARM resource provider contract and REST guidelines. Estimated time (4 hours). This is required before you can request review from ARM API Review board.

[ ] If you are blocked on ARM review and want to get the PR merged with urgency, please get the ARM oncall for reviews (RP Manifest Approvers team under Azure Resource Manager service) from IcM and reach out to them.

Breaking Change Review Checklist
If there are following updates in the PR, ensure to request an approval from API Review Board as defined in the Breaking Change Policy.

[ ] Removing API(s) in stable version
[ ] Removing properties in stable version
[ ] Removing API version(s) in stable version
[ ] Updating API in stable version with Breaking Change Validation errors
[ ] Updating API(s) in preview over 1 year

Action: to initiate an evaluation of the breaking change, create a new intake using the template for breaking changes. Addition details on the process and office hours are on the Breaking change Wiki.
Please follow the link to find more details on PR review process.

          }

missing
` {
"value": "webscoket",
"description": "Imports the Soap API having a SOAP front end.",
"name": "SoapPassThrough"
}`

Refers to: specification/apimanagement/resource-manager/Microsoft.ApiManagement/preview/2020-06-01-preview/definitions.json:416 in f6d85d7. [](commit_id = f6d85d78a51a7ba9083f33c0a89074f7ce2ca185, deletion_comment = False)

          "modelAsString": false

let flip this to modelAsString: true

Refers to: specification/apimanagement/resource-manager/Microsoft.ApiManagement/preview/2020-06-01-preview/definitions.json:282 in f6d85d7. [](commit_id = f6d85d78a51a7ba9083f33c0a89074f7ce2ca185, deletion_comment = False)

          "modelAsString": false

lets flip this to modelAsString:true

Refers to: specification/apimanagement/resource-manager/Microsoft.ApiManagement/preview/2020-06-01-preview/definitions.json:748 in f6d85d7. [](commit_id = f6d85d78a51a7ba9083f33c0a89074f7ce2ca185, deletion_comment = False)

          "modelAsString": false

flip to modelAsString true

Refers to: specification/apimanagement/resource-manager/Microsoft.ApiManagement/preview/2020-06-01-preview/definitions.json:803 in f6d85d7. [](commit_id = f6d85d78a51a7ba9083f33c0a89074f7ce2ca185, deletion_comment = False)

n": "Imports the W

This change for soap api and not applicable for websocket

          }

missing
` {
"value": "webscoket",
"description": "Imports the Websocket API.",
"name": "WebSocket"
}`
https://github.com/Azure/azure-rest-api-specs/pull/11912/checks?check_run_id=1942814117
Refers to: specification/apimanagement/resource-manager/Microsoft.ApiManagement/preview/2020-06-01-preview/definitions.json:416 in f6d85d7. [](commit_id = f6d85d7, deletion_comment = False)

Applicable for soap api and not for websocket


[Tests] Comment out ksh dependency installation, cc #574

ref: afba4e08fd18c73907025850239a0adf4104c611

Looks like I messed this up in 70370a857f0bc16af50f4196afe9af03b100535e


Deployment Error

Hi Florian,
I have run into an issue, I am trying to deploy this as an addon with some custom feature on side menu however, when I deploy the release via clasp which works just fine but when I test the deployment on a test sheet I see the following error on onOpen:
TypeError: Cannot set property 'defineSimpleMode' of undefined     at [unknown function](codemirror/third_party/codemirror/addon/mode/simple:14:31)     at [unknown function](codemirror/third_party/codemirror/addon/mode/simple:10:5)     at [unknown function](codemirror/third_party/codemirror/addon/mode/simple:11:3)
Could you advise on this?

My first guess is, that you are not uploading the files in the right order.
If you look at https://github.com/floitsch/syntax-addon/blob/master/codemirror/.clasp.json you can see that the shim must be uploaded first, followed by codemirror.js and clike.js.

Thank you for quick revert. I have never deployed any script using clasp before and this is my first time.
So what I understood after reading your comment and also README here (https://github.com/floitsch/syntax-addon/tree/master/codemirror):

Deploy the codemirror on a standalone apps script
Deploy the doc version on another script
Finally, import the codemirror library inside the doc version script

Does that make sense? Just to let you know that I am trying to pull on the doc version of the syntax library.

That is correct.
However, when deploying with clasp, you also need to make sure that clasp uploads the files in the right order.
You can just take the .clasp.json that I have, and replace the scriptID with yours. After that, a clasp push will upload the files again, but this time in the right order.

Also see https://openbase.com/js/@google/clasp/documentation#filepushorder-optional

Hi Florian,
It worked indeed. Thanks again for your support.
Have a nice day!


Add .RenderShortcodes

I have been hit by this issue twice recently -- so I assume this is a problem worth solving (I know there are similar issue, and this also relates to .RenderString.
Currently we have:

.Content which gives rendered HTML with shortcodes rendered.
.RawContent which gives the raw source excluding front matter. No shortcodes rendered.

A common pattern is to include files using .GetPage via a shortcode, e.g.:

# Title

{{< include "foo.md" >}}

Using the {{< means you can include just about anything and it will be preserved as-is. But it will not partake in the global rendering context re. table of contents, foot notes etc.
You can do this in your shortcode:
{{ (site.GetPage "foo.md").RawContent n}}

And then

# Title

{{% include "foo.md" %}}

The above will work but any shortcodes in foo.md will not be rendered.
Which this issue is all about.
I assume that it makes sense that .RenderString uses this method internally by default, but what I need is basically:
{{ $markdownWithRenderedShortcodes := .RawContent | .RenderShortcodes }}

These should also work:
{{ $markdownWithRenderedShortcodes := .RenderShortcodes }}
{{ $markdownWithRenderedShortcodes := "string with shortcodes" | .RenderShortcodes }}

/cc @regisphilibert @onedrawingperday @digitalcraftsman @moorereason  and gang
And yes, this is tightly connected to a Page so I think a method makes sense.

Would this feature, if implemented, render the shortcodes for the current output format? That'd be super great!

Yes.

Is this going to get implemented at all any time soon? People keep asking how to build my PR and since no equivalent functionality exists in mainline and @bep outright rejected my PR likely as they felt this was a better way to implement this (and therefore it became the only implementation they'd accept, apparently) I don't have any actual alternative option to get shortcodes processed in JSON output.

Checking your PR it was rejected not outright for a feeling but for missing formalities. Open an issue, describe and discuss your issue, then if it is deemed a good addition to hugo open a PR referencing that issue number.

A need for this came up again yesterday:
https://discourse.gohugo.io/t/export-to-markdown-with-shortcodes/39590

And again: https://discourse.gohugo.io/t/table-of-contents-render-hook/45352

Tried it out, works great, thanks!


added validate binary search tree algorithm

PR Checklist:

[x] My submission is formatted according to the guidelines in the contributing guide
[x] My addition is on refer on the language README.md file
[x] My addition does not have a spelling problem
[x] My submission has a proper and user-friendly description of the algorithm
[x] My submission has the time complexity of the algorithm
[x] My submission has sample input-output of the program (NOT FOR PYTHON)

What kind of change does this PR introduce? (check at least one)

[ ] Bugfix
[x] New algorithm
[ ] Optimization in previous algorithms
[ ] Code style update
[ ] Refactor
[ ] Documentation
[ ] Other, please describe:

Briefly describe the changes in this PR

Other information:

Added a validate binary search tree algorithm by which you can check if a tree is a binary search tree or not, just simply pass the root of a tree into the function and it will recursively check that tree and output result as true or false.

Please Merge this pull request


Crash

The game keeps crashing when I load it, I use Jumploader.
I expected it to load.

Minecraft Version: [1.16.5]
mod version is 1.0.0

Crash report please


remove bootstrap icons (causes bootstrap-vue-3.es.js huge build file size 1.2M)

node_modules/bootstrap-vue-3/dist/bootstrap-vue-3.es.js
has 1.2M and is included in project's vendor.js bundle. This is huge.
node_modules/bootstrap/dist/js/bootstrap.esm.min.js has 73k, so it's not bootstrap's fault.
Trying to find the cause.

added stats PR.
bootstrap-icons/bootstrap-icons.svg has 1M
My projects are already including icons via CDN, as .css file has only 500k
https://icons.getbootstrap.com/#install
and is loaded later, after main app.
Like any other icon fonts, we're using them with , not with b-icon
Again, this is consistent with all other icon fonts.
We can switch from bootstrap icons to any other icon font, while continuing to use bootstrap CSS/JS. They are not dependent.
Would you please remove bootstrap icons from this project? Having a 1.2M vendors.js file isn't acceptable.
Thanks!

I disagree with this. I think that they should be included, but perhaps more information on proper use could be added. In bootstrap-vue v2, one could drastically reduce the build size by importing icons directly. On many of my projects, I saw the project build size going to about 10% of what it was by importing icons directly. This is something you could not achieve if you were using other css frameworks. Vuetify allows you to use material design icons, but the project immediately imports the CDN from https://materialdesignicons.com/. This has it's advantages, but treeshaking out specific icons is not one of them. Perhaps a better alternative would be to implement automatic treeshaking to include icons or information on how to do it yourself.

Bootstrap doesn't force developers to use bootstrap-icons. One can happily use fontawesome or whatever (so many choices, all using  convention.
Why should this project force (by shoving it down my throat / build) bootstrap-icons? Let it be a separate npm, if desired, like bootstrap does.

I'll try to check it out and get a feel for what you're seeing. But I was just noting that I think the importing components directly was the preferred solution in V2 if you cared about size.

i think @mariusa is right. ive always used fontawesome over bootstrap icons and now i am "forced" to waste valuable bandwidth for something i am not even using

I have to agree with @mariusa here as well. I've always used external icon libraries, and will never use Bootstrap icons, so this is just unnecessary bloat.

In order to KISS, I'll remove bootstrap icons from this project.
If one wants to optionally use bootstrap icons, one can do it similarly with any other icon font . If some people prefer b-icon, then please make a new package, eg bootstrap-icons-vue, which interested people can install like any other library.

Could you then please update the docs https://cdmoro.github.io/bootstrap-vue-3/components/Icon.html#usage ?

@comod Hi Comod I am working on refactoring Docs to be part of a subworkspace. Will need to talk to CDMoro with what is best to deploy.

@VividLemon saw you started to include icons again. Would you please make sure that it doesn't add anything to the build for people not using that custom functionality? Other use other icon fonts. I personally use  which works great, no need for extra code to output this. Thanks

@mariusa we understand your concerns but the current direction will not involve including the entire sprite package as originally done thus limiting size to only chosen icons ( still in development).

It's a separate package


Map does not seem to reflect all cases

This may be minor, but when I look at this map, the number of pins totals about 1850 cases. However, Articles.count = 2088.  Trying to figure out if this is a bug, recognizing it may be nothing.

Nevermind.  I think this is because ~220 cases have no lat/long. Closing this.

Need to adjust the count at the top of the map page to only include cases with a lat and long value as those are the only ones that will appear on the map.

How about we find Lat/long for those cases?

On Jun 4, 2016, at 1:25 PM, campgurus<EMAIL_ADDRESS>wrote:
Need to adjust the count at the top of the map page to only include cases with a lat and long value as those are the only ones that will appear on the map.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or mute the thread.

We will do our best, but addresses initially input by editors may not have enough detail to generate a lat long, so for a period of time until we get to it, the number will not be accurate without the conditional that discounts those records.

closing this.


[FEA] support build with bazel

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I wish I could use RAFT to do [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context, code examples, or references to existing implementations about the feature request here.

Hi @hsgui
There is no current plan for cuvs ( or any part of RAPIDS ) to have support for building via bazel.
Your options include using something like https://github.com/bazelbuild/rules_foreign_cc to bridge between bazel and CMake or to use an existing build of cuvs and bring it into bazel as an external dependency.

@robertmaynard thanks for your suggestions!


Post notification in slack room after deploying

Posts a message like below into the moj-dsds slack room after every deploy (aka git push) to staging

/cc @oskarpearson you ok with hard coding variables in here? Is is worth using ENV?

I like the idea. But: is it not perhaps a problem that we have these tokens as public on Github now? (Since the repo isn't private, I mean.)
We could add the auth variables to the encrypted ENV store in Ansible, so that they aren't stored in plaintext anywhere. The deploy code runs with those as environment variables, so they would be accessible to the script.
Probably best to revoke the token in the code while we figure this out, since the token might be able to read our slack group chat?

@ansonK I've regenerated the token so we won't be getting spam messages in the room :smile:

@pixeltrix thanks - on 2nd thoughts shouldn't have pushed that with the token in it
@oskarpearson that sounds like a plan, lets pick it up on monday