ResolvePackageAssets error NETSDK1064: Package XYZ, version 5.1.2 was not found.

ResolvePackageAssets error NETSDK1064: Package XYZ, version 5.1.2 was not found.
@nguerrera  Posting this here in case anyone else runs into this issue, and would like some suggestions on how to troubleshoot it.
Under certain conditions, a build pipeline may not be repeatable due to ResolvePackageAssets step internal to dotnet.exe clean failing:
C:\Program Files\dotnet\sdk\3.1.101\Sdks\Microsoft.NET.Sdk\targets\Microsoft.PackageDependencyResolution.targets(234, 5): error NETSDK1064: Package Autofac, version 5.1.2 was not found. It might have been deleted since NuGet restore. Otherwise, NuGet restore might have only partially completed, which might have been due to maximum path length restrictions.

Example pipeline:

dotnet.exe clean Tools.sln --configuration Release
NuGet.CommandLine.4.9.2\tools\NuGet.exe restore Tools.sln
dotnet.exe rebuild Tools.sln --configuration Release

General
TeamCity was configured to use NuGet.CommandLine.4.9.2.  Upgraded to NuGet.CommandLine.5.4.0
TeamCity version was 2019.1.1 (build 66192).  Upgraded to TeamCity server version is 2019.2.2 (build 71923).
Visual Studio Build Tools 2019 was 16.4.3. Upgraded to Visual Studio Build Tools 2019 16.4.5
Was using Microsoft (R) Build Engine version 16.4.0+e901037fe for .NET Framework
Possible Ideas on What Causes This Issue

Running build tasks as SYSTEM\NT Authority may be problematic (searching online, this appears to be a common problem setting up Jenkins to build C# projects) for some reason
If you have two packages with the same version anywhere in your nuget PackageReference dependency graph (I tested this, and this did not seem to be the root cause)
If you are on an older version of NuGet
If you are using MSBuild.exe or Visual Studio Build Tools 2019 instead of dotnet.exe to build a .NET SDK csproj formatted project file (I'm not sure why this would cause the problems)

Removing nuget.exe step altogether seems to fix the problem.  That makes sense since dotnet build should do the restore.  Issue was likely caused migrating from old csproj file format to newer csproj file format.

I think I’ve seen this before. When you restore with a system account, the nuget global packages folder under the user profile directory ends up being in a location that is subject to virtualization between x64 and x86 processes. Then if you restore with say an x86 nuget.exe and build with an x64 dotnet.exe, the build can’t find the packages that the prior restore claims it acquired because the path in project.assets.json doesn’t work in a process of different bitness!

Thank you for separating this out, I think it will be very helpful for others down the road.

We are hitting this issue at the moment in Azure Pipelines.  It took us a few days to figure out what the issue was and honestly, we still don't know why it is occurring.  Our solution is to point Nuget to restore packages to a folder that does not virtualize between x86 and x64.
I think at the very least Nuget should alter the error message to suggest this as a possible solution.  It already suggests the max path length as a solution (which actually led us up the garden path for quite a while).
i am not sure which repo I should raise this in - which one do you think?

I have the same issue. It causes me 1 day until I read your advice. I have to change to x64, before it was x86

Just to give some more information as to our specific issue.  Our Azure private agent was running as Local System rather than a User.  This meant that the centralised Nuget location for this user is in a folder that is subject to x64 and x86 bitness changes.  So if the packages were restored using x64 Nuget but then your build used x86 MSBuild, the MSBuild would not see any packages there.  We fixed it by changing the user that our agent runs under.

@gregpakes What should we do in case we want to build the x86 project but need to keep the x64 agent since we can use this agent for building other x64 projects later?

What user is your agent running as?  Read my previous message.

I got this same error on Jenkins build. I changed the agent service's user and solved the problem.

I got this same error on Jenkins build. I changed the agent service's user and solved the problem.

I tried change user:
I logged into the operating system(Windows) as a different user.
I run in CMD 'msbuild .....' and this is working.
But I don't know haw changed the agent service's user.
How you changed the agent service's user?

I got this same error on Jenkins build. I changed the agent service's user and solved the problem.

Just to give some more information as to our specific issue. Our Azure private agent was running as Local System rather than a User. This meant that the centralised Nuget location for this user is in a folder that is subject to x64 and x86 bitness changes. So if the packages were restored using x64 Nuget but then your build used x86 MSBuild, the MSBuild would not see any packages there. We fixed it by changing the user that our agent runs under.

I tried change user:
I logged into the operating system(Windows) as a different user.
I run in CMD 'msbuild .....' and this is working.
But I don't know haw changed the agent service's user.
How you changed the agent service's user?

You can gon run > services.msc, search for the Jenkins service name and click with right button and go to the properties. Go to the logon tab and set user and password agent.

I got this same error on Jenkins build. I changed the agent service's user and solved the problem.

Just to give some more information as to our specific issue. Our Azure private agent was running as Local System rather than a User. This meant that the centralised Nuget location for this user is in a folder that is subject to x64 and x86 bitness changes. So if the packages were restored using x64 Nuget but then your build used x86 MSBuild, the MSBuild would not see any packages there. We fixed it by changing the user that our agent runs under.

I tried change user:
I logged into the operating system(Windows) as a different user.
I run in CMD 'msbuild .....' and this is working.
But I don't know haw changed the agent service's user.
How you changed the agent service's user?

You can gon run > services.msc, search for the Jenkins service name and click with right button and go to the properties. Go to the logon tab and set user and password agent.

Is there a way to get rid of this error without changing the user under which the agent is running?

If I am changing user for the Jenkins service, I am losing all settings Jenkins.

Try cleaning completely out the build server repository directory so that no cached files are present.
Then try restoring the whole solution using dotnet.exe
Then do the rest of the dotnet.exe lifecycle but specify --no-restore in each of those steps, to avoid triggering ResolvePackageAssets.
Basically, if you look at my original repro, you'll see in step 2, I am not using dotnet.exe.  That is the "problem", so to speak.

Try cleaning completely out the build server repository directory so that no cached files are present.
Then try restoring the whole solution using dotnet.exe
Then do the rest of the dotnet.exe lifecycle but specify --no-restore in each of those steps, to avoid triggering ResolvePackageAssets.
Basically, if you look at my original repro, you'll see in step 2, I am not using dotnet.exe. That is the "problem", so to speak.

I changed the agent service's user. And moved files Jenkins from profile folder 'old user' to 'new user'- This is working.
Thank you!

Try cleaning completely out the build server repository directory so that no cached files are present.
Then try restoring the whole solution using dotnet.exe
Then do the rest of the dotnet.exe lifecycle but specify --no-restore in each of those steps, to avoid triggering ResolvePackageAssets.
Basically, if you look at my original repro, you'll see in step 2, I am not using dotnet.exe. That is the "problem", so to speak.

I changed the agent service's user. And moved files Jenkins from profile folder 'old user' to 'new user'- This is working.
Thank you!

I had the same problem and this configuration solved it for me. Deploy of .net framework 4.8

msbuild /p:SkipInvalidConfigurations=true /t:Restore

@psouki SkipInvalidConfigurations skips configurations in your platform/configurations defined in your csproj that are invalid.  Thus, this is probably not a real solution - you are treating an error as a warning.  It is very unlikely NETSDK1064 is related to the error you were getting if your solution 'worked' for you, since you would also hit a different error for an invalid configuration. https://learn.microsoft.com/en-us/visualstudio/msbuild/common-msbuild-project-properties?view=vs-2019


2.2 Ensure that sinks are configured for all log entries - problem with multiple projects in an aggregator

Describe the bug
When using this dashboard against an aggregator returning a set of GCP projects, only the last project will return a correctly configured log sink although every other one is configured the same (using terraform)

I will post a MR to update the query so that it successfully works for all projects with a correctly configured sink.

Steampipe version (steampipe -v)
steampipe 0.20.9
Plugin version (steampipe plugin list)
gcp: 0.41.0
To reproduce
Use this dashboard against an aggregator or put multiple gcp project in the search-path
Expected behavior
For every project in the search-path (or aggregator), all projects with correctly configured log sinks should return as OK

Here is the PR : https://github.com/turbot/steampipe-mod-gcp-compliance/pull/111

@M0nsieurChat, Thanks for using Steampipe!
Nice catch on this; I appreciate raising PR for this as well 👍
Just adding this image to track and explain how the query behaved differently. Not sure even why we might have used this string_agg. Anyways, we will go ahead and approve the PR

After the fix

Addressed in https://github.com/turbot/steampipe-mod-gcp-compliance/pull/111 !!
Thanks @M0nsieurChat for the fix 👍.


Tag mismatch when using asm chacha20_poly1305_{seal, open} directly for rfc7539

Hi @vkrasnov -
Since the EVP_CIPHER_CTX_ctrl API for c20p is specifically for TLS (with the 13-byte AAD + seq number mixing), I'm trying to use the underlying ASM seal/open APIs to get rfc7539 behavior. From looking at e_chacha20_poly1305.c, there doesn't seem to be any TLS-specific details in the ASM implementation. Code snippet adapted from e_chacha20_poly1305.c behavior per https://github.com/cloudflare/sslconfig/blob/master/patches/openssl__chacha20_poly1305_draft_and_rfc_ossl102j.patch#L4159-L4163
unsigned char key_iv[32 + 4 + 12];
memcpy(key_iv, key, 32);
memset(key_iv + 32, 0, 4);
memcpy(key_iv + 32 + 4, iv, 12);
chacha20_poly1305_seal(ciphertext, plaintext, plaintext_len + 16, (uint8_t*)aad, aad_len, key_iv);
return plaintext_len + 16;
Since we're not doing this for TLS, there are no seq numbers to XOR into the IV. However, on testing this with the input here: https://tools.ietf.org/html/rfc7539#appendix-A.5 - the encryption and decryption work correctly but the tag is wrong. Any ideas how to fix this? Thanks

The length argument should be the length of the plaintext without the tag. The tag length is implicit.

Wow, that was indeed simple; I also had to do ciphertext_len - 16 and it works now! Thanks!
I was misled by this snippet :)
/* Fix for MAC */
inl -= POLY1305_MAC_LEN;


Investigate why the comment was not posted for #71

PR: https://github.com/stoat-dev/stoat-action/pull/71
It's likely because the PR was created from a fork.

Yeah it's just because it's for a fork.
Maybe we should allow manually triggering for a whitelisted commit on a fork somehow? The build was triggered when you reviewed, right? Those aren't differentiated in our db vs non-fork PRs, but that's probably fine since it's approved?

The build was triggered when you reviewed, right?

Yes, I approved the action on that PR, and the action did run. It's probably a permission issue from the GITHUB_TOKEN.

All of the GITHUB_TOKEN-related auth in the action run looks like it worked properly, it's the webhook that wasn't triggered or allowed (not sure)


Add a link back to task src on notification

Issue created with imdone.io

DOING: Add a link back to task src on notification id:143 +feature
lib/views/imdone-atom-view.coffee:248
@imdone Issue Creator. The developer's task board. imdone.io

READY: Add a link back to task src on notification id:143 +feature gh:223
lib/views/imdone-atom-view.coffee:248
@imdone commenter. The developer's task board. imdone.io

DONE: Add a link back to task src on notification id:143 +feature gh:223
lib/views/imdone-atom-view.coffee:248
@imdone Issue Closer. The developer's task board. imdone.io


Not able to run docker image in docker container.

Whenever I configured docker first time it will work perfectly. but after around 2 months I am trying to run my cypress test into docker, and it will not work.
Below is my Dockerfile.
FROM cypress/base:14.19.0
RUN mkdir /legrande-cypress
WORKDIR /legrande-cypress
COPY ./package.json .
COPY ./cypress.json .
COPY ./cypress  ./cypress
RUN npm install --dev
RUN npm install
ENTRYPOINT ["npm","cypress","run"]

I am able to build docker images and it will be successfully built using docker build -t cypress-image .. But when I am trying to run that image using docker run -i -v "%cd%":/legrande-cypress -t cypress-image:latest --spec cypress/integration/examples/*.js OR docker run -t cypress-image . it will through below instruction.
Usage: npm <command>

where <command> is one of:
    access, adduser, audit, bin, bugs, c, cache, ci, cit,
    clean-install, clean-install-test, completion, config,
    create, ddp, dedupe, deprecate, dist-tag, docs, doctor,
    edit, explore, fund, get, help, help-search, hook, i, init,
    install, install-ci-test, install-test, it, link, list, ln,
    login, logout, ls, org, outdated, owner, pack, ping, prefix,
    profile, prune, publish, rb, rebuild, repo, restart, root,
    run, run-script, s, se, search, set, shrinkwrap, star,
    stars, start, stop, t, team, test, token, tst, un,
    uninstall, unpublish, unstar, up, update, v, version, view,
    whoami

npm <command> -h  quick help on <command>
npm -l            display full usage info
npm help <term>   search for help on <term>
npm help npm      involved overview

Specify configs in the ini-formatted file:
    /root/.npmrc
or on the command line via: npm <command> --key value
Config info can be viewed via: npm help config

<EMAIL_ADDRESS>/usr/local/lib/node_modules/npm

I don't know what's going wrong here. any suggestions?

@KrupalVaghasiya
This is an old issue and it refers to a version which is no longer supported. I'm going to close the issue now. If you still have a problem with a current Cypress Docker image please comment and we can take it from there.


Make sure that messages from private channels can't be ducked

Since our #duck-pond channel can be viewed by all our Helpers and we apparently can't trust our Moderators (me included :pensive:), we need to add a check to make sure that messages from channels not viewable by Helpers can't be relayed to the duck pond.
This can be done by adding a new check function in bot/bot/exts/fun/duck_pond.py and using it in on_raw_reaction_add().

I'd like to work on this 😄

I'd like to work on this 😄


Update material-top-tab-navigator.md

Adding "overScrollMode" prob to the Tab-Navigator removes and setting to "false" removes the overScrollMode animation in Andriod. I think Should be added in the docs.

Thanks for creating this PR. However, this prop is not added in typescript types so if you want to add this behavior to docs then you would also need to update the types.


Conditional steps are not reviewed by RC008, RC009

Orb version:
v11.1.0
What happened:
First described in #128 by @wyardley, run-steps within conditional steps are not checked by RC008 and RC009
Expected behavior:
This is expected to fail RC008 and RC009
steps:
  - checkout
  - restore-deps
  - run: npm run thing1
  - when:
      condition: << parameters.run-thing2 >>
      steps:
        run: npm run thing2

Additional Information:

Fixed with this PR.


Button icon shadow when disabled

https://morewings.github.io/koval-ui/?path=/story/components-button--primary&args=disabled:!true;type:submit;variant:success;prefix:withPrefix;suffix:withSuffix

:tada: This issue has been resolved in version 0.15.11 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


LB rules are not functional when source and tagert ports for service targets are different.

Server version - v0.29.0-rc1
steps to reproduce the problem:
Created a LB service with source port as 7777 and target port as 80.
Added 1 service and chose only service (did not provide any other parameters).
API shows ports on LB service is set correctly:
"ports": [
"7777:80",
],
source port is not configured in happroxy

iptables cofigured for source port on host as expected:
-A CATTLE_PREROUTING -p tcp -m addrtype --dst-type LOCAL -m tcp --dport 7777 -j DNAT --to-destination <IP_ADDRESS>:7777
LB rules are not functional:
Sangeethas-MBP:testwget sangeethahariharan1$ wget http://<IP_ADDRESS>:7777/name.html
--2015-07-22 09:04:00--  http://<IP_ADDRESS>:7777/name.html
Connecting to <IP_ADDRESS>:7777... failed: Connection refused.
Sangeethas-MBP:testwget sangeethahariharan1$

happens because private port is not set correctly. Fixing it.

Tested with build from master:
LB rules are functional when source and tagert ports for service targets are different.
source port is configured in happroxy.


feat(helpers) add support for Gateway API v1beta1

What this PR does / why we need it:
Gateway API is now in beta (https://gateway-api.sigs.k8s.io/v1alpha2/references/spec/) and RBAC rules should be
created for this version.
Special notes for your reviewer:
Checklist
[Place an '[x]' (no spaces) in all applicable fields. Please remove unrelated fields.]

[x] PR is based off the current tip of the main branch.
[x] Changes are documented under the "Unreleased" header in CHANGELOG.md
[x] Commits follow the Kong commit message guidelines

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

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


With JS off, right navbar blocks out checkboxes in My bookmarks & My subs tables

As you can see in attached screenshots, in no-js mode the checkboxes are unclickable so it's impossible to un-bookmark / unsubscribe an item. This happens in Chrome and Safari, in Firefox the checkboxes are only partly shut out and somehow clickable. /cc @jcreamer898

@jcreamer898 I am not sure if it counts as bug.  However, it would be nice to fix it :).

@thomasthesecond, this is still a problem.


Tf12 upgrade

This updates the examples and our CI environment to use Terraform 12. As a part of that transition, this PR drops support for TF11 in the various output related functions.
Additional upgrades:

Update examples to be compatible with packer 1.5
Update GCP code to be compatible with google provider 3.x
Update fixtures to be compatible with terragrunt 19

Thanks for review! Going to go ahead and merge + release this!


ci: release when a new feature hits main

Pull Request

Proposed Changes

Since enhancements are getting put in under the feat: prefix, let's change this to release on new feature.
Readiness Checklist
Author/Contributor

[x] If documentation is needed for this change, has that been included in this pull request
[x] run make lint and fix any issues that you have introduced
[x] run make test and ensure you have test coverage for the lines you are introducing

Reviewer

[ ] Label as either fix, documentation, enhancement, infrastructure, maintenance or breaking

If approved, we may wan to make this change in all other OSPO actions repos.

While we are in this file do we want to remove pull_request and just leave pull_request_target? To prevent double releases? And I agree, this change needs to go to all actions.


Data Source for the Map

Hi,
Can you please let me know the data source which you are using in the Flask Server API?
Thanks,

I'm using the official Wikipedia API hosted at https://en.wikipedia.org/w/api.php to retrieve the HTML of each wikipedia article, and the logic for extracting connections is my own algorithm, accessible here in this repo. The documentation for the API is here.


Added Italian language on ui-text.yml

I added the Italian translation on ui-text.yml.
Please see my ui-text.yml file for the code and the related website for a live example.
Please let me know if you need something more.

I don't think this pull request is going to work as it has about 300 commits and is bringing in stuff from your repo.
Try forking the minimal-mistakes repo and then commit your changes that add the Italian text.
You should be able to submit a pull request to master from that repo and I'll be able to merge it in.
https://help.github.com/articles/using-pull-requests/


feat(ldap): Adding support for LDAP authentication

This PR adds a rudimentary support for LDAP authentication.

Hey, sorry I'm quite busy at the moment but I'm looking forward to review it ASAP.


Executing a code cell should mark the notebook as dirty

Seems like dirty should be handled in the notebook model. Any change to the notebook model (or its persisted subset) should trigger dirty. Executing a cell should do this indirectly by clearing output and prompt.
If the model is stored with something like immutable.js, it should be easy for the saving code to easily track 'is the current state what I last saved'

Yes, the intent was to make this semantically part of the model.  I just quickly made the issue while I was working on another issue.  We are also considering moving delete/undelete and copy/paste to the model, since the undelete stack and copied cells could be considered state, what are your thoughts on that?

That's one thing where we want to be clear about treating "application" state and "document" state differently. copied data is logically application state (unless we can actually use the clipboard), but I wouldn't consider it document state.

yes, the same could be said of active and selected state

We could have a base model that is only for rendering, and then add these features on top.

So far, we are more treating the model as a "view model" of sorts that has
some state that is view related. We could create a separate layer for the
actual document state, but we though that the amount of state for the view
was minimal enough that it wasn't worth it.
On Tue, Mar 22, 2016 at 6:04 AM, Steven Silvester<EMAIL_ADDRESS>wrote:

We could have a base model that is only for rendering, and then add these
features on top.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/jupyter/jupyter-js-notebook/issues/117#issuecomment-199803582

--
Brian E. Granger
Associate Professor of Physics and Data Science
Cal Poly State University, San Luis Obispo
@ellisonbg on Twitter and GitHub
<EMAIL_ADDRESS>and<EMAIL_ADDRESS>


how did you record the gif?


DOM structure constancy

It's more like a question. For my projects it's important to have constant DOM structure generated for each of the file(I use css selectors of nodes to programmatically navigate through them, mainly element>element selector). I spotted that the same PDF file was rendered in not the same way with versions 1.7 and 2.* - the DOM trees are not equal.
What is the policy regarding the constancy of DOM structure generated by pdf.js ? I think I am not in right to think it won't change from version to version, right?
Currently we use 1.7.354 and planning to use 2.*

What is the policy regarding the constancy of DOM structure generated by PDF.js?

What do you actually mean with "DOM structure" here, the textLayer which is used to enable text-selection/copying in the default viewer or something else?
If the former then that's not guaranteed to remain unchanged over time/versions, since it's not part of the core library API. The official PDF.js API can be found at https://github.com/mozilla/pdf.js/blob/master/src/display/api.js, and is the only thing that won't be changed in backwards incompatible ways (unless absolutely necessary, in which case it's gradually deprecated).
I.e. the streamTextContent and getTextContent methods in the API should remain compatible between versions, but how the viewer then uses the returned information through https://github.com/mozilla/pdf.js/blob/master/web/text_layer_builder.js and https://github.com/mozilla/pdf.js/blob/master/src/display/text_layer.js is subject to changes (at any time).

I mean textLayer. Thank you for clarification

What is the policy regarding the constancy of DOM structure generated by PDF.js?

What do you actually mean with "DOM structure" here, the textLayer which is used to enable text-selection/copying in the default viewer or something else?
If the former then that's not guaranteed to remain unchanged over time/versions, since it's not part of the core library API. The official PDF.js API can be found at https://github.com/mozilla/pdf.js/blob/master/src/display/api.js, and is the only thing that won't be changed in backwards incompatible ways (unless absolutely necessary, in which case it's gradually deprecated).
I.e. the streamTextContent and getTextContent methods in the API should remain compatible between versions, but how the viewer then uses the returned information through https://github.com/mozilla/pdf.js/blob/master/web/text_layer_builder.js and https://github.com/mozilla/pdf.js/blob/master/src/display/text_layer.js is subject to changes (at any time).


[WFCORE-5108] Drop duplicate FlexBase64 provided in a context that ha…

…s access to the original.
https://issues.redhat.com/browse/WFCORE-5108

@bstansberry thanks


Suggestion for error code to be switch to a string

I wanted to check and see if people would be open to switching the error code returned as part of the spec to a string instead of an integer. So things would like like this:
{
    code: 'ITEM_NOT_PINNED',  (short error code)
    message: `Current user does not have this item pinned` (more detailed message)
}

From my experience, strings are a little easier to manage in the codebase and can be easily understood better by the consumer.
I'm completely fine implementing the spec as is, I just wanted to throw this up for discussion to see if people cared one way or the other.

Listing the most common error types in the spec is a good idea.
While we do it, we may change the format if there is a good reason. Let's discuss this.

@obo20 Good question regarding code.
Current version with numeric code and text message is solely inspired by IPFS Cluster API where HTTP status code in duplicated in JSON as code:
{
  code: 400
  message: 'ITEM_NOT_PINNED'
}

The problem with this approach is that multiple errors will be returned with HTTP status 400, so it becomes mostly informational, and the real "error code" needs to be returned in message.
Right now, the spec does not specify details of error response.
If we decide to change this, we should make it really intuitive.
Perhaps something along these lines (details being optional):
{
  error: {
	  reason: 'ITEM_NOT_PINNED'
	  details: 'Current user does not have this item pinned'
  }
}

cc @andrew  @aschmahmann @ipfs/wg-pinning-services
Thoughts on how to proceed?

For reference, afaik there is no standard convention, everyone returns whatever stuff they want:

https://api.twitter.com/1.1/statuses/mentions_timeline.json
https://api.spotify.com/v1/me/player/currently-playing
https://graph.facebook.com/v2.9/me?fields=id%2Cname%2Cpicture%2C picture&access_token=xxxxxxxxxxx
https://tools.ietf.org/html/rfc7807 (attempt to standardize application/problem+json, never seen it in production)

I don't have a particularly strong opinion here other than wanting to make sure we all agree and it's in the yaml spec.
Since it seems like the errors are service specific as opposed to shared across all implementations I feel like the question is what type of behavior do we want to encourage:

Having the error code be an integer basically requires that any reasonable developer would add a useful details message. Developers might also choose to have more unique error codes based on their situation.
Having the error code be a string essentially requires developers to have reasonable short error codes, but they might choose not to put much deatils into the details section (e.g. Current user does not have this item pinned adds minimal information over ITEM_NOT_PINNED, but perhaps there was more context to be added).

I feel like, while integer codes might encourage more flexibility for developer debugging, string codes might be more friendly and so we should go with them. However, I'm persuadable :smile:

Whilst putting together my basic pinning service api, I wasn't really sure what kinds of errors to expect to be sending back to the client, so having a list of standard(ish) ones to expect in the spec would be great.
I'm currently bubbling up any errors I get from the go-ipfs HTTP API to the client which is pretty nasty as the error code is usually 0 or 1 which I believe is intended for the CLI to return as the exit code, in other words, 0 is an ignorable error and 1 is more serious?

Good point about bubbling up codes. Personally I don't like the idea of "external" numeric code being shared by multiple error types. Switching to string makes it harder to do the wrong thing.
I took a stab at string codes in https://github.com/ipfs/pinning-services-api-spec/pull/59 – please review.


In JS, typedefs should be automatically exported

// @Filename: module.js
/** @typedef {number} Num */
module.exports = { a: 1 }

// @Filename: use.js
/** @type {import("./module.js").Num} */
var n;

Expected:
Num is visible in use.js
Actual:
Num is not visible.
Note that the checker already has code to handle structures like this, so modules with modules.exports= should already almost work. Other kinds of modules may or may not.
The special-case merge code for module.exports= in the checker puts SymbolFlags.Value on all the symbols, which will be incorrect for this case, so that code will need to be updated.

This will hugely unlock TS usage to check JS codebases.
Imagine the following:
models/a.js
const createSomething = ({some, thing}) => ({
    some: String(some),
    thing: String(thing),
});

/**
 * @typedef {ReturnType<typeof createSomething>} Something
 */

export const createA = ({something}) => ({
    something: createSomething(something),
});

actions/a.js
/**
 * @typedef {ReturnType<typeof import('../models/a').createA>} A
 */
/**
 * @typedef {ReturnType<typeof import('../models/a').Something>} Something
 */

/**
 * @param {A[]} as
 * @param {Something} something
 */
export const getABySomething = (as, something) => {/* do stuff */};

I know the A part will with actual master code, and if I understand well, it should do in the future for the typedef of Something.
Would this work?

Wouldn't the second typedef in actions/a.js be just /** @typedef {import('../models/a').Something} Something */ ?

Wooops, that's right.

@SergioMorchon Yes, it should work. Let me know if you have a chance to test it with typescript@next starting tomorrow.

It worked, @sandersn. Nice :D
Anyway, related to this, VSCode does shows 0 references in the sourced JSDoc, although a property rename with refactor action (F2) works fine across all usages that imported the exposed typedef.

@SergioMorchon I filed #23863 to track that problem. I couldn't get rename to work either, but I wasn't using VS Code.


fix issue #146

closes #146
julia> X = Tables.table(coerce(rand("abc", 5, 3), Multiclass))
Tables.MatrixTable{CategoricalArrays.CategoricalMatrix{Char, UInt32, Char, CategoricalArrays.CategoricalValue{Char, UInt32}, Union{}}} with 5 rows, 3 columns, and schema:
 :Column1  CategoricalArrays.CategoricalValue{Char, UInt32}
 :Column2  CategoricalArrays.CategoricalValue{Char, UInt32}
 :Column3  CategoricalArrays.CategoricalValue{Char, UInt32}

julia> scitype(X)
Table{AbstractVector{Multiclass{3}}}

Codecov Report

Merging #151 (5d37505) into dev (1aa5bbf) will decrease coverage by 0.34%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##              dev     #151      +/-   ##
==========================================
- Coverage   94.53%   94.19%   -0.35%
==========================================
  Files           7        7
  Lines         293      293
==========================================
- Hits          277      276       -1
- Misses         16       17       +1

Impacted Files
Coverage Δ

src/convention/scitype.jl
78.37% <ø> (ø)

src/schema.jl
97.14% <0.00%> (-2.86%)
:arrow_down:

Continue to review full report at Codecov.

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


Support content-encoding in worker/publisher

Similar to the content-encoding header in HTTP, ContentEncoding implemented here provides a way to encode/decode (compress/decompress) messages on the fly. Like original ContentType, ContentEncoding can be configured like:
Sneakers::ContentEncoding.register(
  content_encoding: 'gzip',
  decoder: ->(payload) { ActiveSupport::Gzip.decompress(payload) },
  encoder: ->(payload) { ActiveSupport::Gzip.compress(payload) },
)

When messages arrive with the given content type and content encoding set the payload will be decoded and then deserialized. Before publishing, message will be serialized and then encoded with given content_type and content_encoding. Most of code are borrowed from ContentType (#152), thus behavior of configurations and options is pretty much the same.
With combination of ContentType and  ContentEncoding, we can easily deal with something like 'text/plain'+'gzip', 'application/json'+'gzip' or 'application/json'+'zstd' without any duplicated code.

Thank you. This is a non-trivial contribution I generally would like to see more feedback on. However, this fits the kind of features Sneakers strives to provide, and complements content encoding support nicely. So I think this should not receive a lot of pushback :)

One thing this could do on the publisher side but does not is set the message property for content encoding, which AMQP 0-9-1 has. It also has one for content type and that isn't set either, which may be why this PR does nothing about it. The field is purely informative for
applications and is not used by RabbitMQ itself in any way.

One thing this could do on the publisher side but does not is set the message property for content encoding, which AMQP 0-9-1 has. It also has one for content type and that isn't set either, which may be why this PR does nothing about it. The field is purely informative for applications and is not used by RabbitMQ itself in any way.

Thanks for merging code.  On the publisher side, properties for content encoding and  content type will be set automatically by bunny because we pass them as options to Bunny::Exchange::publish. Those options will be encoded as properties in here and then here.

@ansoncat then they are not "set automatically by Bunny" but rather by your code ;) which is fine, of course.


Update RecyclerExecuteICUWithRetry to provide more verbose asserts

We are seeing a handful of failfasts come up in crawler around this function that are difficult to act on, so hopefully these asserts should make it more clear what is going on. See OS#16964000

FWIW, LGTM too.

@dotnet-bot test OSX static_osx_osx_debug please
test OSX static_osx_osx_release please


F5 starts debugging when inactive, but refreshes the page when active

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: 1.80
OS Version: macOS 13.4.1

Steps to Reproduce:
I don't know how to reproduce this in VSCode, which does not have native browser refresh, or in vscode.dev, which does not have debugging, but this issue is occurring in Google's web version of VSCode that does support debugging, and would ideally be fixed upstream since you already distinguish isWeb and isPlatform and this will be broken when you or anybody does support debug on web. For us to reproduce it you start debugging with F5, and then press F5 again which then refreshes the page stopping the debugging etc.)
F5 in browsers is a fairly common shortcut for refresh. I think it should not be used to start debugging on web (isWeb && !isStandalone()). Instead, maybe we can use alt-F5 on web? That does not seem to be taken yet.
Please let me know if you would accept a contribution.

I also have some issues with the web version refreshing the page on F5 and ctrl+R, ... or ctrl+w that closes the browser tab.  (quite bad if hit ctrl + w accidentally)
Can vscode intercept those shortcuts bindings to block them even when no commands are bound to them?

This is like https://github.com/microsoft/vscode/issues/181792. I wouldn't remove the existing keybinding on web, but I would take a PR that adds alt+F5 as an alternate keybinding.

Actually, two things. It seems like that keybinding is actually claimed

And in Edge and Chrome on Mac, F5 doesn't do anything. Maybe that is Windows only?

You are right, Mac does not seem to use F5 for refresh. Windows I don't have around for testing, but on my Linux F5 does refresh. This apparently unreliable source claims "all modern browsers use F5 for refreshing", which is clearly wrong on Mac, but may be true for the other OSes? https://www.computerhope.com/jargon/f/f5.htm#:~:text=In all modern Internet browsers,contents of the page again.
I think an alternative keyboard shortcut does not solve the problem, which is that depending on what state you are in, F5 does something very different, and while you are in a debug session it is destructive (F5 reloads the page and ends your debugging session).
I see two main directions:

VSCode overwrites F5, even on web. In that case I would like to make it also overwrite it, and possibly do nothing, in the cases not yet covered, e.g. when a debugger is running but not currently stopped at a breakpoint, to avoid the disruptive refresh which kills you debug session.
VSCode stops overwriting F5 on web because that is, at least on Linux and possibly on Windows, for refreshing the page. But then an alternative keyboard shortcut does not work - it needs to completely stop hogging F5 so that it can be used for refreshing always.

I think the current mixed state is very frustrating, at least for those on systems where this happens.

@rehmsen indeed, mixed behaviors are annoying. In my opinion, the 'refresh' is dangerous as it can be accidentally pressed. And since this is a 'web application' more than a 'webpage', i think the F5 should always be overridden - at worse to do 'nothing'
A real, intentional 'refresh' can be still initiated by the user with the mouse press on the refresh button that all browsers do have.

Guess I didn't follow up here- F5 does 'start' when debugState == inactive and 'continue' when debugState == 'stopped'. It would probably work to add a dummy command that runs when debugState is not inactive or stopped, just to fill the gap and block the keybinding from the browser.


Update _index.md

improved top-level description of this section

Summary

improved top-level description of this section

Related issue :

Thanks @mviljoen-egi, it's still failing the tests due to spaces at end of lines: https://github.com/EGI-Federation/documentation/pull/218/checks?check_run_id=2665456529
Can you please edit this PR to fix this?
You should be able to edit the file by going to the https://github.com/EGI-Federation/documentation/pull/218/files tabs and using Edit file from the ... menu.


Slow unit test - getLatestWeakSubjectivityCheckpointEpoch

Describe the bug
Review the workload happening there
getLatestWeakSubjectivityCheckpointEpoch
 ✓ should have 256 mod for slot 8192 and activeValidatorCount of 8192 (91ms)
 ✓ should have 256 mod for slot 16384 and activeValidatorCount of 16384 (160ms)
 ✓ should have 512 mod for slot 32768 and activeValidatorCount of 32768 (295ms)
 ✓ should have 1024 mod for slot 65536 and activeValidatorCount of 65536 (640ms)
 ✓ should have 1792 mod for slot 131072 and activeValidatorCount of 131072 (1154ms)
 ✓ should have 3328 mod for slot 262144 and activeValidatorCount of 262144 (2317ms)

Expected behavior
Unit tests should be under < 50ms

@3xtr4t3rr3str14l Can you open a separate PR just fixing this test only?


add a blog (wetchat-bot-chat)

Fixes # .
Make sure these boxes are checked before creating your pull request -- thank you!

[x] Add Blog Header, including title, author, date.
For example:
---
title: "Your Great Blog Title"
author: your_github_id
image: /assets/2020/08-your-blog-slug/teaser.jpg
---

YOUR_FIRST_SENTENCE_SHOULD_BE_A_SUMMARY_FOR_YOUR_POST

[x] Keep all filenames & url as lowercase, and use - to connect words instead of space. e.g. 2017-10-06-wechat-pc-impactor instead of 2017-10-06-WeChat PC Impactor,

[x] Embed the photo & video before publishing, save all external file to a folder named by ${MONTH}-${YOUR_BLOG_SLUG}/ under /assets/2020 directory.

[x] Add teaser image for the blog

[x] Add your self as an author to the author data file at https://github.com/wechaty/wechaty.js.org/blob/master/_developers/YOUR_GITHUB_USERNAME.md with your GitHub username. And please also remember to reference yourself with the Github username in your blog post, so that we can have nice author information besides your blog after we published it!
For excample:
---
name: Jiarui LI (李佳芮)
site: https://lijiarui.github.io
bio: 句子互动创始人 & CEO，微软人工智能最具价值专家 (AI MVP)
avatar: /assets/developers/lijiarui/avatar.png
email<EMAIL_ADDRESS>twitter: https://weibo.com/u/2175505900
---

Here is the example file:

lijiarui.md: https://github.com/wechaty/wechaty.github.io/blob/master/_developers/lijiarui.md
It will shown like this on wechaty blog: https://wechaty.github.io/developers/lijiarui/

To read more about the contribute guideline, visit: https://github.com/wechaty/wechaty.js.org#contribute-guideline

Thank you very much for sharing this great post, the blog is online with URL https://wechaty.js.org/2020/10/22/wetchat-bot-chat

You've invited slx1997 to Wechaty! They'll be receiving an email shortly. They can also visit https://github.com/wechaty to accept the invitation.

I have invited you to join the Wechaty Contributor Team on our GitHub Wechaty Organization, please accept it by visiting https://github.com/wechaty
We have a WeChat room for Wechaty Contributors only, if you'd like to join, please contact @lijiarui on WeChat.


Script for visualizing poses

Hi @hjxwhy,
This is amazing work. If you don't mind, may I ask which scripts are used for visualizing poses?

Thanks, you can visualize poses using this script https://github.com/hjxwhy/mipnerf_pl/blob/dev/utils/visualize_cameras.py

Thanks, you can visualize poses using this script https://github.com/hjxwhy/mipnerf_pl/blob/dev/utils/visualize_cameras.py

Thanks


Dart editor incremental parser doesn't handle string interpolation properly

This issue was originally filed by<EMAIL_ADDRESS>
When inserting a "${0} at the beginning of a huge file, editor adds a error markers to all lines in the file and scrolling and editing become very slow.
Strings without interpolation (e.g. "foo) are handled correctly.

Dart Editor is dead. And this seems like it is maybe a dup of #946 as its filed just under "analyzer-recovery" now. Close?

Most issues reported against Dart Editor were really issues with the analyzer.
It's a slightly different case from a recovery perspective because the string is not terminated.

Closing as stale.


Timeline for version 1.7.0

When do you plan to release the next version? We're currently running our own version, to allow rfc2136 updates without authentication and would like to follow the official releases again.

Releases are monthly around the end of the month.  But I'm not sure how the server version has anything to do with running a different copy of that external-dns catalog item.


Fix value of urlPattern in RegexParser

Summary

Fixed the problem that other string after url are recognized as url
Add a file RegexParserTest.swift

Screenshot

Before
After

@pisces i just noticed that deep links like my-bundle-id://resource/id aren't picked up by the urlPattern, i tend to use them a lot in customer support context while on device, more reliable "user proofing" than a universal link.
Anyways, i guess i can add a custom handler. That NSRegularExpression escaping in the regexp string for URL makes it so much harder to decompose

@rromanchuk
I think the existing url pattern doesn't support custom scheme, right?


Text Field needs minimum width.

Currently, when the field is empty, it is nearly impossible to tap for focus (or even click with a mouse pointer in the emulator).

Fixed #437 https://github.com/google/blockly-android/pull/437/commits/431194066c16461d472628aff91db88e315d7683


chore: update dev dependencies

This PR was automatically generated to update versions of dev dependencies to their latest versions. This helps ensure we get fixes and improvements in a timely fashion and reduces the impact of updating the versions that can arise if versions are allowed to become stale for an extended period.
What did you change?
This action ran yarn upgrade:automatic to update package.json files to request the latest versions of each package. Certain critical packages are intentionally excluded.
This action also deleted the yarn.lock file in order to recreate it with the latest matching versions of secondary dependencies.
This PR includes the various package.json that pull our dependencies forward to the latest versions, the yarn.lock update that maps required versions to the actual versions to be used, and updates the offline mirror.
How did you test and verify your work?
This PR should not normally significantly affect the build outputs or runtime packages. Ensure that yarn ci-check runs cleanly and all tests pass (done automatically as part of the PR checks).

@davidmenendez Thanks for opening the eslint issue. I wouldn’t considered this issue blocked though — I would recommend that our devs downgrade eslint in the dev dependencies PRs until #6187 is addressed so that we are able to include at least other updates.

Closing in favor of #6215


Dropdown caret icon vertical alignment is not perfect

BT version: bootstrap-4.1.1-dist
OS: Windows 10
Browser: Chrome 67.0.3396.99
How its currently display: https://prnt.sc/k45ham
How its should be: https://prnt.sc/k45i4o
Big thanks for BT dev team :)

Bug reports must include a live demo of the problem. Per our contributing guidelines, please create a reduced test case via CodePen or JS Bin and report back with your link, Bootstrap version, and specific browser and OS details.

Bootstrap documentation can use as a demo in this case.
https://getbootstrap.com/docs/4.1/components/dropdowns/

This is probably the intended behavior, CC @mdo

Duplicate of #26602.


Failed to register GATT advertisement: org.freedesktop.DBus.Error.NoReply

28.06.21 22:14:15 (+0000)  gateway-config  DEBUG:root:Wi-Fi Complete
28.06.21 22:14:30 (+0000)  gateway-config  DEBUG:root:Wi-Fi Scanning
28.06.21 22:14:30 (+0000)  gateway-config  DEBUG:root:Wi-Fi Complete
28.06.21 22:14:35 (+0000)  gateway-config  Failed to register GATT advertisement: org.freedesktop.DBus.Error.NoReply: Did not receive a reply. Possible causes include: the remote application did not send a reply, the message bus security policy blocked the reply, the reply timeout expired, or the network connection was broken.

The problem turned out to be the Bluetooth firmware, like we mentioned earlier. Radxa released a new firmware for it an we've shared it with Balena to release a new OS revision. I'll be tracking the progress.
Note: The firmware is working fine on an AW-NB197SM but yet to see the effects on an AP6212.

Confirmed on testnet, everything is fine right now. All has been fixed with the 2022.1.4 RockPi BalenaOS release. (Included in 2022.04.15+ production images)


[loc][Query][VSCode] Please provide more context

Hi, we have a question from our translator. Can you help please? Thanks!
Source:
Delete All Right
File Name:
src\vs\editor\contrib\linesOperations\common\linesOperations.nls.resx
Resource ID:
".resx", 0; "lines.deleteAllRight"
Query:
Please provide more context: does it mean "delete everything on the right?

Yes, it means "delete everything to the right of the cursor".


Update netty-all to 4.1.75.Final

Updates io.netty:netty-all from 4.1.69.Final to 4.1.75.Final.
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "io.netty", artifactId = "netty-all" } ]

labels: library-update, commit-count:1

Superseded by #43.


Tell if Stopify is “running”

Here's a problem: We want Pyret's arrays to be the same kind of arrays as those on the rest of the page.
We don't want to enforce a wrapping/unwrapping step at the Pyret boundary; we've tried this in other implementations and it's a huge headache (think nested arrays, 3rd party libraries that .map, etc).
The current polyfill strategy for HoFs makes Stopified arrays special. If a client of some Stopified code tries to map or filter on an array, they'll almost certainly get (nondeterministically!) some kind of uncaught Capture or similar, because that array's callbacks have been replaced. For the same reason, it doesn't work to patch in the Stopified polyfills on the array prototype, since that would break innocuous non-stopped code.
One thing we'd like to try is writing polyfills with a dispatch, for example:
  function stopifyDispatch(stopped : any, native : any) {
    // @stopify flat
    return function(this : any) {
        // @stopify flat
        if(isStopifyRunning()) {
            return stopped.apply(this, arguments);
        }
        else {
            return native.apply(this, arguments);
        }
    }
  }

Array.prototype.map = stopifyDispatch(array_map_polyfill, Array.prototype.map);
Array.prototype.filter = ...

Thing is, we can't figure out how to write isStopifyRunning()
There's a lot of states Stopify can be in – is there a way provided by the Stopify runtime to write this predicate? We tried various combinations of eventMode and rts.mode and rts.capturing, but can't seem to express it. Is there a concise way to tell if the stack is currently a Stopify stack that's ready for captures/suspends, or if it's on the plain JS stack?

OK, I think we have this working with this:
/**
 * This works around what may be state management issues related to eventMode. The relevant enum is
 *
 * enum EventMode { Running, Paused, Waiting }
 *
 * First, in its initial state, the runner is set to `RUNNING` when it should be set to `WAITING`
 *
 * Second, when pausing with pauseK, it doesn't set the mode to `PAUSED` (there is a comment that this has to do with the debugger in that code)
 *
 * The pauseK wrapper handles pausing/unpausing, and doing the run on the empty program sets things to `WAITING`.
 */
currentRunner = stopify.stopifyLocally("", { newMethod: 'direct' });
currentRunner.run(() => { });

let originalPauseK = currentRunner.pauseK;

currentRunner.pauseK = function patchedPauseK(k : any) {
  return originalPauseK.call(this, (resumer : (result: any) => void) => {
    const oldMode = currentRunner.eventMode;
    currentRunner.eventMode = 1;
    return k((result : any) => {
      currentRunner.eventMode = oldMode;
      return resumer(result);
    });
  })
}

Relevant comment for pauseK: https://github.com/nuprl/Stopify/blob/275d950193a9fc04175ed810834f9e1778108229/stopify/src/runtime/abstractRunner.ts#L200
Then our predicate is:
  function isStopifyRunning() {
    /**
     * The relevant enum is
     *
     * enum EventMode { Running = 0, Paused = 1, Waiting = 2 }
     *
     * The check below returns true when that mode is Running, indicating the Stopify stack is live.
     * Paused means “a stack is captured and waiting to be resumed”
     * Waiting means “we are between/after a completed run of a stopify program/event handler”
     */
    // @ts-ignore
    return typeof $STOPIFY !== "undefined" && $STOPIFY.eventMode === 0;
  }

@blerner and I spent some time reconstructing this. I think this could be useful as an exposed API, though may end up finding other cases where the state needs to be managed a bit to have eventMode match the right definition of isStopifyRunning. But we pushed through a bunch of issues and got a .map that seamlessly works with this dispatch (and we had versions that very much didn't work, breaking both the stopped side and the page side).


Weird user error with config option for testing

If you are reporting a bug, please fill in below. Otherwise feel free to remove this template entirely.
Can you reproduce the problem with latest npm?
Yes, this is after a very recent clean install
Description
When using --config with the test script, very strange errors are reported, that literally blame the user.
Using the command:
env CI=true react-scripts test --coverage --env=jsdom --config jest-config.js

Error: Unknown config option "0" with value "jest-config.js". This is either a typing error or a user mistake and fixing it will remove this message.
Error: Unknown config option "1" with value "{"collectCoverageFrom":["src/**/*.{js,jsx}"],"setupFiles":["/mnt/data/git/turalt-react-instrument/node_modules/react-scripts/config/polyfills.js"],"testPathIgnorePatterns":["<rootDir>[/\\\\](build|docs|node_modules)[/\\\\]"],"testEnvironment":"node","testURL":"http://localhost","transform":{"^.+\\.(js|jsx)$":"/mnt/data/git/turalt-react-instrument/node_modules/react-scripts/config/jest/babelTransform.js","^.+\\.css$":"/mnt/data/git/turalt-react-instrument/node_modules/react-scripts/config/jest/cssTransform.js","^(?!.*\\.(js|jsx|css|json)$)":"/mnt/data/git/turalt-react-instrument/node_modules/react-scripts/config/jest/fileTransform.js"},"transformIgnorePatterns":["[/\\\\]node_modules[/\\\\].+\\.(js|jsx)$"],"moduleNameMapper":{"^react-native$":"react-native-web"},"rootDir":"/mnt/data/git/turalt-react-instrument"}". This is either a typing error or a user mistake and fixing it will remove this message.

This does seem to be valid according to the --help text.
Expected behavior
The jest-config.js file should be passed to Jest.
Actual behavior
The whole test framework gets misconfigured.
Environment
Run these commands in the project folder and fill in their results:

npm ls react-scripts (if you haven’t ejected): 0.8.4
node -v: v4.5.0
npm -v: 2.15.9

Then, specify:

Operating system: Mac OSX 10.12.2
Browser and version: n/a

Reproducible Demo
Minimal test appears to be:
env CI=true node_modules/.bin/react-scripts test --config '{"verbose":true}'

And doesn't really require a specific app. Same effect appears on a vanilla app created by the command line.

Hmm, I don't think we ever officially supported passing custom config to Jest. The error isn't nice but this is not something we intend to support before ejecting.

Well, react-scripts test --help says:
  --config, -c                    The path to a jest config file specifying how
                                  to find and execute tests. If no rootDir is
                                  set in the config, the current directory is
                                  assumed to be the rootDir for the project.
                                  This can also be a JSONencoded value which
                                  Jest will use as configuration.       [string]

There's only so much we can do delegating to Jest. --help is a Jest command, not ours, but since we delegate all commands to it (and they usually work well) we likely won't make exceptions here, sorry. I know it's not perfect, and we might expose Jest config more directly in the future, but not right now.


[Wait for #1079] [IniInterpreter] Add ini backbone deserialization

[IniInterpreter] Add ini backbone deserialization

**Changes proposed in this PR:**
- Add ini backbone deserialization support

**Self evaluation:**
1. Build test: [X]Passed [ ]Failed [ ]Skipped
2. Run test: [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: Jihoon Lee<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.4.20191203. Thank you for submitting PR #1080. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://nnsuite.mooo.com/.

:octocat: cibot: @zhoonit, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/1080-202104062220190.52792811393738-0bfaa92f3c39af2c45e8ec207430f54d39d56a24/.

:octocat: cibot: @zhoonit, One of the module of prebuild group is failed. If you want to get a hint to fix this issue, please go to https://github.com/nnstreamer/nntrainer/wiki/.

:octocat: cibot: @zhoonit, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://nnsuite.mooo.com/nntrainer/ci/repo-workers/pr-checker/1080-202104062232090.52418303489685-6e304d95d95300831ce25056b55d3040c1a3ea8d/.

I think we need to distinguish.. graph and section and mergiablegraph.


Add compiled files to git

Compile files to dist folder and make the script copy only them to main

@dotansimha please reference the commits

Fixed in https://github.com/Urigo/angular2-meteor/commit/8234bd4a4adcd5fe603ab49fd5d93ec51f48b184


[Tooling] Apply everywhere SwiftLint rules for sorted_imports, identifier_name and type_name

Prerequisites

[X] I have searched the backlog for duplicate or closed feature requests

As a
developper
... I want to
apply rule for sorted imports and length of variable names.
... so that I can
see all import sorted and warn design team of too long tokens names. It seems in demo app the rules are not applied, at least
Motivation and context
No response
Proposed Solution
See:

https://realm.github.io/SwiftLint/type_name.html
https://realm.github.io/SwiftLint/identifier_name.html

Other
No response
Contact Details
No response

FYI a bug report has been submitted as I was not able to trigger any warnings fr the sorted_imports
https://github.com/realm/SwiftLint/issues/5823

ℹ Released with version v0.4.0 🚀


fill_halos! functionality

We want a fill_halos! functionality. E.g., for periodic the process of filling up the halos is unambiguous, e.g.:
function fill_halos!(field::Field1D)
    nx, hx = field.grid.nx, field.grid.hx

    for j in 1:hx
        field.data[nx+j] = field.data[j]
        field.data[-j+1] = field.data[nx-j+1]
    end

    return nothing
end

Now, how do we make sure that the above is only applied for periodic dimensions? We need to think how to do that...

We can just have an if condition for grids. Something like:
function fill_halos!(field::Field1D)
    nx, hx = field.grid.nx, field.grid.hx

    if(typeof(field.grid) == Grid1D(Periodic)
        for j in 1:hx
            field.data[nx+j] = field.data[j]
            field.data[-j+1] = field.data[nx-j+1]
    else if(typeof(field.grid) == Grid1D(Bounded)
        ...........
    end

    return nothing
end

We don't wanna be calling if statements...
We wanna be writing different methods for different types of arguments.

Also, if topology is Bounded still the way you fill the halo points depends on the actual boundary condition (Dirichet, Neumann, something else). Only for Periodic topologies the way you fill the halo regions is unambiguous.
We don't need to write the most general code at this point. But we just need to do something that it's correct. To support periodic boundary conditions is relatively easy. To support other boundary conditions we need to think a bit.

We can just have an if condition for grids. Something like:
function fill_halos!(field::Field1D)
    nx, hx = field.grid.nx, field.grid.hx

    if(typeof(field.grid) == Grid1D(Periodic))
        for j in 1:hx
            field.data[nx+j] = field.data[j]
            field.data[-j+1] = field.data[nx-j+1]
    else if(typeof(field.grid) == Grid1D(Bounded))
        ...........
    end

    return nothing
end

What you wrote above could be done, for example, like (take this with a grain of salt... I just wrote the code here, didn't really test it):
function fill_halos!(field::Field1D{Any, G}) where G::Grid1D{Periodic}
    nx, hx = field.grid.nx, field.grid.hx
    for j in 1:hx
        field.data[nx+j] = field.data[j]
        field.data[-j+1] = field.data[nx-j+1]
    end

    return nothing
end

function fill_halos!(field::Field1D{Any, G}) where G::Grid1D{Bounded}
    nx, hx = field.grid.nx, field.grid.hx
    for j in 1:hx
        [do something else]
    end

    return nothing
end

I'm continuing here some discussion that was going on in #9:
@dhruvbhagtani argues that fill_halos!() requires user data; @navidcy argues that it does not require any user data but simply the type of boundary conditions.
I gave some examples above for Periodic boundary conditions -- no data was required. Probably I'm missing something? @dhruvbhagtani can you elaborate a bit on an example where user-data is required to fill in the halo points?

Didn't we talk about this @navidcy, and I realised I was wrong? But, on second thought, I believe we require user data if we are dealing with anything other than periodic boundary conditions. For Dirichlet or Neumann boundary conditions, we require the user to give us some data for the end points.

We did talk about this and settles some things. But the issue is still open because we haven't implemented fill_halos! functionality for 2D yet.
If you mean like the 2 values of the field in each side of the domain, or of it's derivative then sure.
If you mean anything more than that then I disagree, unless you convince me otherwise with an example. :)


ConstraintMaker's size property doesn't work as expected.

0.17.0
This doesn't show the view.
foregroundImageView.snp_makeConstraints { [unowned self](make) -> Void in
            make.size.equalTo(self.foregroundImageSize)
            make.center.equalTo(self)
}

This shows the view.
foregroundImageView.snp_makeConstraints { [unowned self](make) -> Void in
            make.width.equalTo(self.foregroundImageSize.width)
            make.height.equalTo(self.foregroundImageSize.width)
            make.center.equalTo(self)
}

Duplicate: #169

@efremidze thx!


Proposed changes to non-cryptographic SFRs and non-technical changes to cryptographic SFRs

Changes justified inline.

@jvdsn can you check this pull request for the merge conflicts. The three I couldn't resolve I think are conflicts, otherwise this seems fine to merge, so I think if you can resolve the conflicts we will be able to merge the changes.

@jvdsn can you check this pull request for the merge conflicts. The three I couldn't resolve I think are conflicts, otherwise this seems fine to merge, so I think if you can resolve the conflicts we will be able to merge the changes.

this PR is no longer intended for merging; I am/was planning to submit all changes as separate PRs to ease the review

Most changes are now incorporated through various other PRs. The other important issues are CSPs (#263) and the dependency table (#347).


[Feature request] Reduce bin size by excluding serial log from code

Similar to https://github.com/sparkfun/SparkFun_SCD4x_Arduino_Library/issues/3 I'm still working on reducing code size for ESPEasy 😃
So in that same line, I'm proposing to add a similar compiler flag for reducing the bin size.
//Enable/disable including debug log (to allow saving some space)
#ifndef MAX1704X_ENABLE_DEBUGLOG
  #if defined(LIBRARIES_NO_LOG) && LIBRARIES_NO_LOG
    #define MAX1704X_ENABLE_DEBUGLOG 0 // OFF/disabled/excluded on demand
  #else
    #define MAX1704X_ENABLE_DEBUGLOG 1 // ON/enabled/included by default
  #endif
#endif

I'll open a PR to get that included.

It took a little (more) time, but the PlatformIO registry now has picked up the latest release 🍾


Dev command

Currently, there isn't an easy way to run resin-electronjs on your local machine. You have to manually pass in a URL_LAUNCHER because it defaults to absolute path /usr/data/index.html.
We should also add an npm dev script for convenience (with doesn't start x server).

I use https://www.npmjs.com/package/dotenv and it seems to work nicely.


Exception happened during processing of request from ('IP ADDRESS')

i'm running into an error when i try and connect to any stager using any computer. it all sets up and runs but when an inbound connection happens it crashes. i have installed all dependencies including rjsmin and jsmin. side note, a very old version of koadic from around a year ago work just fine.
Error Message:
(koadic: sta/js/mshta)$ ----------------------------------------
Exception happened during processing of request from ('<IP_ADDRESS>', 51305)
Traceback (most recent call last):
File "/usr/lib/python3.6/socketserver.py", line 651, in process_request_thread
self.finish_request(request, client_address)
File "/usr/lib/python3.6/socketserver.py", line 361, in finish_request
self.RequestHandlerClass(request, client_address, self)
File "/usr/lib/python3.6/socketserver.py", line 721, in init
self.handle()
File "/home/anon/github/koadic/core/handler.py", line 90, in handle
return BaseHTTPRequestHandler.handle(self)
File "/usr/lib/python3.6/http/server.py", line 418, in handle
self.handle_one_request()
File "/usr/lib/python3.6/http/server.py", line 406, in handle_one_request
method()
File "/home/anon/github/koadic/core/handler.py", line 149, in do_GET
return self.handle_new_session()
File "/home/anon/github/koadic/core/handler.py", line 197, in handle_new_session
data = self.post_process_script(self.options.get("STAGE"))
File "/home/anon/github/koadic/core/handler.py", line 311, in post_process_script
from rjsmin import jsmin
ModuleNotFoundError: No module named 'rjsmin'
[!] Zombie 0: Timed out.

"ModuleNotFoundError: No module named 'rjsmin'"
pip install rsjmin

I have already tried running that, its installed already.

Are you sure you have rjsmin installed for python3? "ModuleNotFoundError: No module named 'rjsmin'" is a pretty clear error.

That's what I thought but it's already installed.

Try a virtualenv, that will solve it for sure.

Ok, I'll give it a shot and report back.

Using virtualenv worked, I got it to run perfectly. Thank you for your assistance on this weird issue I was having.


cli: de-clutter CLI

Fixes #6943 (partially for now, but foundation)
Details of current draft implementation
@helderco we had a sync, but I might have forgotten some parts ahah (sorry 👼). Feel free to tell if I'm completely off on some interpretation / implementation:

[x] Add line break between error and usage
This has been added in cmd/dagger/functions.go

[x] Style headings in BOLD UPPERCASE to help break sections visually
A new helper function has been added and the corresponding template has been updated

[x] Remove discrepancy between dagger query and the rest of the commands
This sub-command hasn't been updated in months and having a separate template is more coordination work. It might be time to make them 1:1 ?

[x] Conventionalize on either <command> or COMMAND syntax in cmd.Use
I updated all COMMAND as uppercase. I did not remember if you were also referencing on the usage examples inside square brackets like [arguments] -> [ARGUMENTS]  ? I followed the CLI examples we discussed and some did it that way, in doubt I applied it everywhere but totally open for change

[ ] Figure out if arguments are better above or below functions/commands ??
I experimented on this one, and I haven't found an easy way: on a given function call, I do agree that having the commands at the bottom does make sense. However, changing the order on the template directly also changes the order for commands such as: dagger --help. What do you think is the best implementation on this one ? Shall we tweak the template to make it specific for just the dagger call section ? I feared adding complexity to the template logic

[ ] Visual cue for required flags
As you proposed last time, the idea would be to have a required flags section for the dagger call function subcommands only ? Will take a look tomorrow. Same fear on the added complexity on the main template, but this one seems more manageable: it is just a section wrapped in an if to show it on dagger call subcommand context

[x] "Options" instead of "Flags"?1
This is done, with our own implementation of useLine to print options instead of args by default.
Solomon requested arguments on above issue though. I followed your terminology, but shall we make a specific case for arguments in dagger call / dagger functions scope ?

[ ] Help topics for dagger call to keep --help lean while still providing more documentation
What topics do you think we should cover first ? More than the implementation, the most important might be the documentation added to those topics. Which could be the first 2 topics to create, so that i draft the implementation tomorrow ?

[ ] Global flags only on root command and top level commands

Remove persistent flags from child commands after being parsed? Or just hide?

TUI (--silent, --focus)
Modules (-m)

This is the one I am currently trying to implement in a clean way (using the hiding method at first), and might need some guidance again. I have been trying to extend the callCmd implementation by implementing a new persistentPreRunE:
PersistentPreRunE: func(_ *FuncCommand, cmd *cobra.Command, _ []string) error {
    rootCmd := cmd
    for rootCmd.Parent() != nil {
        rootCmd = rootCmd.Parent()
    }
    hideGlobalFlags(rootCmd)
    return nil
},

to control the behavior and potentially use the funcCommand infos or the cmd infos to mark as hidden, as you suggested, when the call command has subcommands
However, I'm still having a hard time on this part. Will keep iterating tomorrow again

[x] Talk about Functions and arguments instead of Function commands
This is partially done as I used your options terminology globally instead of arguments. It is true that arguments is pretty accurate in a dagger call functions context, but then, do we talk about arguments inside dagger functions usage examples too ?

cc @helderco

Fixes #6943 (partially for now, but foundation)

A separate PR for each item would actually be preferred, especially if it can stand on its own or it may warrant some discussion or design decision.

[x]  Remove discrepancy between dagger query and the rest of the commands
This sub-command hasn't been updated in months and having a separate template is more coordination work. It might be time to make them 1:1 ?

👍

[x] Conventionalize on either <command> or COMMAND syntax in cmd.Use
I updated all COMMAND as uppercase. I did not remember if you were also referencing on the usage examples inside square brackets like [arguments] -> [ARGUMENTS]  ? I followed the CLI examples we discussed and some did it that way, in doubt I applied it everywhere but totally open for change

Yes, it's applied everywhere. The idea is to choose a syntax for representing usage and stick to it. Last time I changed to [OPTIONS] but than reverted back to [flags] because while I prefer the former for avoiding confusion with static argument names and user provided values in some cases, Cobra uses the latter syntax. So it can seem like swimming against the current because you need to override some default behavior. The Docker CLI does it, but I’m not sure it’s worth it for us.
The gh tool uses Cobra’s default, maybe copy that as it’s more common anyway, I believe. I suggest looking at git too since there’s lots of examples there.

[ ]  Figure out if arguments are better above or below functions/commands ??
I experimented on this one, and I haven't found an easy way: on a given function call, I do agree that having the commands at the bottom does make sense. However, changing the order on the template directly also changes the order for commands such as: dagger --help. What do you think is the best implementation on this one ? Shall we tweak the template to make it specific for just the dagger call section ? I feared adding complexity to the template logic

Cobra’s default is to put flags after subcommands. In some cases it seemed like I was looking for the flags next to the usage line, so I experimented with moving them there. That’s that docker does, but you’ll find a hard time finding a docker command with flags and sub-commands (example: docker compose --help).
However, when you have a lot of sub-commands, as when you do  dagger call on a function that returns a container, then it’s much harder to find the flags because that long list will occupy the whole screen. Doubly confusing to have “Global flags” at the bottom since that “hints” that non-global flags would be next to them.
Note that with docker, in this case, you only see “Global options” in the root  command (docker --help), not in any children. That inspired me to do the same.

[ ]  Visual cue for required flags
As you proposed last time, the idea would be to have a required flags section for the dagger call function subcommands only ? Will take a look tomorrow. Same fear on the added complexity on the main template, but this one seems more manageable: it is just a section wrapped in an if to show it on dagger call subcommand context

I wouldn’t put an if in the template looking for the call command specifically. In this case it can be more general. Rather than breaking in two sections because of required, just append [required] to flags marked as required, same as what’s done for default values, and make sure they’re sorted before the others (better in its own PR).
It’s what Typer does, for example:
Usage: app [OPTIONS] NAME

Options:
  --lastname TEXT       Last name of the person [required]
  --help                Show this message and exit.

The idea of a “required option” can be strange though, but at least right now that only happens in dagger call, which brings us to the next point.

[x]  "Options" instead of "Flags"?1
This is done, with our own implementation of useLine to print options instead of args by default.
Solomon requested arguments on above issue though. I followed your terminology, but shall we make a specific case for arguments in dagger call / dagger functions scope ?

dagger functions doesn’t show any function arguments. It doesn’t even create sub-commands so they don’t show in --help as well. It works by normal stdout so no customization necessary here.
Also, remember that dagger call (top level command) is the only command that can have two kinds of flags. An actual flag like --output and flags from constructor arguments. But for any dagger call <function> sub-command, it’s just function arguments.
If it was just the latter, it would be simply a matter of customizing the name of the section via an annotation, for example. But I think there’s a value in separating the flags in call and the constructor arguments.
How to do that? If you see how marking a flag as required works, Cobra is adding an annotation through the flagset. So you can just create an annotation for marking a flag as a “function argument”, and in the template, similarly to how you handle required flags, you split argument flags, and if there’s any, show a section below “Options” for “Arguments”.
Both sections will only show at the same time in the top-level dagger call and flags marked as “required" will only show under Arguments so there’s no “required option” incongruity in practice.
I suggest three separate PRs then:

Replace “Flags” with “Options”
Append [required] to a flag marked as required, and sort the list of flags with the required ones first
Adopt “Functions” and “Arguments” terminology in dagger call

[ ]  Help topics for dagger call to keep --help lean while still providing more documentation
What topics do you think we should cover first ? More than the implementation, the most important might be the documentation added to those topics. Which could be the first 2 topics to create, so that i draft the implementation tomorrow ?

Not a priority, better create a separate issue for this. The intent is to provide more information to the user in the CLI (i.e., without requiring a visit to the docs), while reducing the clutter in normal --help. A good example for dagger call is how it works through chaining, what happens with a few core types (Contaienr, Directory…), how to use --output and --json, etc.
gh uses help topics for this, but docker relies on web documentation, doing its utmost to keep --help output to a minimum. I didn’t find any help topic being used (as a feature) in that CLI.
Since Dagger has its nuances, I’ve been wondering which approach is better here. We could just “link” to the web for more information. \cc @vikram-dagger

[ ]  Global flags only on root command and top level commands

Remove persistent flags from child commands after being parsed? Or just hide?

TUI (--silent, --focus)
Modules (-m)

This is the one I am currently trying to implement in a clean way (using the hiding method at first), and might need some guidance again. I have been trying to extend the callCmd implementation by implementing a new persistentPreRunE:
PersistentPreRunE: func(_ *FuncCommand, cmd *cobra.Command, _ []string) error {
    rootCmd := cmd
    for rootCmd.Parent() != nil {
        rootCmd = rootCmd.Parent()
    }
    hideGlobalFlags(rootCmd)
    return nil
},

to control the behavior and potentially use the funcCommand infos or the cmd infos to mark as hidden, as you suggested, when the call command has subcommands However, I'm still having a hard time on this part. Will keep iterating tomorrow again

The way I’ve envisioned this is through main.go, for all commands. Not just call. docker hides them for any command that’s not the root command. So you’d only see --debug and --silent for example, in dagger --help but not dagger call.
I think some of those can be useful at “top level”  though (direct child of root), especially -m,--mod, but has been painful only in dagger call <function> sub-commands actually. Additionally, some of the global flags have already been either hidden or removed since I first added this to the item list.
So I’d just not add these flagsets to “function” sub-commands in call (not simply hide), which also helps prevent collisions with a user’s argument name choices. Including -m,--mod

[x]  Talk about Functions and arguments instead of Function commands
This is partially done as I used your options terminology globally instead of arguments. It is true that arguments is pretty accurate in a dagger call functions context, but then, do we talk about arguments inside dagger functions usage examples too ?

Already talked about this in a previous point. To reiterate, "Options" is also closer to function arguments than “Flags”, but it’s better to have constructor arguments in dagger call be separate from that command’s own flags like --output, and it also avoids having “required options”, since that only happens for function arguments.
None of this applies to dagger functions since it works differently. It’s not through --help like call. There’s no child subcommands and not flags from function arguments, just normal positional arguments to the functions command.

@grouville, with "Figure out if arguments are better above or below functions/commands", I realize I wasn't clear in addressing your question. The answer to doing it only for call is no. Do it for every command, i.e., basically revert this commit: https://github.com/dagger/dagger/pull/6549/commits/a8ae912c52437e5be755bb38ee48c29a449a9ebd
Note that only dagger call may have a long list of sub-commands. But if there's a command (like dagger config) that can also have sub-commands, it won't be that big, so I don't think you'll notice that much if the flags are below or above the sub-commands as they should be easy to find. So reposiitioning for all commands is the best option.


Multiple Google Analytics Accounts?

Can this plugin be used with multiple Google Analytics Accounts?  If not, might there be an easy way to modify it so it can support multipole accounts?

How does it work with google tag manager?


Envoy Buffering TCP connection

Issue Template
Buffering TCP Connection: Envoy seems to be buffering the initial response from an upstream SMTP
Description:
I'm using envoy in an Istio deployment. I've noticed when I deploy the envoy sidecar to a postfix SMTP server I get strange behavior. Namely the initial MOTD/Banner/220 response from the postfix server is not presented to the client until a message is sent from the client to the server. This causes some clients to timeout while they wait for the initial protocol message.
Here is a connection made without the proxy in between:
$ telnet postfix-relay 25
Trying <IP_ADDRESS>...
Connected to postfix-relay.default.svc.cluster.local.
Escape character is '^]'.
220 postfix-relay-749cf779c8-8zhg7.localdomain ESMTP Postfix
HELO example.com
250 postfix-relay-749cf779c8-8zhg7.localdomain
^]
telnet>

And here is a connection made with envoy in the middle.
$ telnet postfix-relay 25
Trying <IP_ADDRESS>...
Connected to postfix-relay.default.svc.cluster.local.
Escape character is '^]'.
HELO example.com
220 postfix-relay-6f789ddcd5-fl9qm.localdomain ESMTP Postfix
250 postfix-relay-6f789ddcd5-fl9qm.localdomain
^]
telnet>

Note that the client is coming from a Kubernetes pod that does not have the Istio envoy sidecar enabled, so there is only one envoy in the middle of these connections.
Logs:
Let me know what other information I can provide since this is in an Istio deployment, I'm not sure what the relevant logs would be. Here are the logs from the postfix container and sidecar, there doesn't seem to be any envoy logging that correlates with the connections that are being made.
logs-from-istio-proxy-in-postfix-relay-6f789ddcd5-6m7rj (1).txt
logs-from-postfix-in-postfix-relay-6f789ddcd5-6m7rj (1).txt

This is expected behavior when you have mTLS in permissive mode. Istio proxy is trying to see first bytes to see whether the connection is TLS. Make your mTLS strict or disable it would solve the issue.

That makes perfect sense, thanks for clearing that up. It works as expected with mTLS turned off via policy.

Closing as answered, feel free to re-open or raise a new one if you have more question.


Added Support for Linux On Power

Hi,
I had added ppc64le(Linux on Power) support on travis-ci in the branch and looks like its been successfully added. I believe it is ready for the final review and merge. The travis ci build logs can be verified from the link below.
https://travis-ci.com/github/ujjwalsh/gulp-babel/builds/209181128
Please have a look.
Regards,
ujjwal

What is the reason for this change? gulp-babel is not affected by the CPU architecture.
Also, I noticed that there have been a lot of "ppc64le" PRs on GitHub and I struggle to understand why :thinking: https://github.com/search?q=ppc64le+is%3Apr&type=Issues


feat(snap): use updated environment variable injection

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/device-mqtt-go/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[x] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[x] I am not introducing a new dependency (add notes below if you are)
[ ] I have added unit tests for the new feature or bug fix (if not, why?)
[x] I have fully tested (add details below) this the new feature or bug fix (if not, why?) https://github.com/canonical/edgex-snap-testing/pull/48
[ ] I have opened a PR for the related docs change (if not, why?)

Testing Instructions

set up:

snap install edgexfoundry
snapcraft
snap install edgex-device-mqtt_2.2.0-dev.15_amd64.snap --devmode
snap connect edgexfoundry:edgex-secretstore-token edgex-device-mqtt:edgex-secretstore-token

validate that mix of legacy option env. and apps./config. will be rejected:

$ snap set edgex-device-mqtt env.service.port=3000
$ snap set edgex-device-mqtt apps.device-mqtt.config.service.port=2000
error: cannot perform the following tasks:
- Run configure hook of "edgex-device-mqtt" snap (run hook "configure":
-----
edgex-device-mqtt.configure: could not process options: 'config.' and 'app.' options must not be mixed with legacy 'env.' options: {
	"service": {
		"port": 3000
	}
}
-----)

validate that apps. will be applied when config supplies a different value, because apps. has higher precedure:

$ snap stop edgex-device-mqtt
$ snap set edgex-device-mqtt config.service.port=5000
$ snap set edgex-device-mqtt apps.device-mqtt.config.service.port=6000
$ cat /var/snap/edgex-device-mqtt/current/config/device-mqtt/res/device-mqtt.env
export SERVICE_PORT=5000
export SERVICE_PORT=6000
$ snap start edgex-device-mqtt
msg="Web server starting (localhost:6000)"

New Dependency Instructions (If applicable)

@farshidtz  Could you please review this? Thanks.

Codecov Report

Merging #365 (d466526) into main (4d191eb) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main     #365   +/-   ##
=======================================
  Coverage   21.34%   21.34%
=======================================
  Files           5        5
  Lines         492      492
=======================================
  Hits          105      105
  Misses        374      374
  Partials       13       13

Continue to review full report at Codecov.

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

This PR will be ready for merge, once the new hook has been tagged.


Update release script to tag Wallaroo Docker image as latest and push

this step is currently done manually, and should be part of the scripted process

this is in place


Fix a typo in README

Just a typo fix. :)

Closing; duplicate. Thanks!

(Well, technically, this one came first, but I saw the other one first in the UI. :-p)


Fix out-of-tree builds

Fix issues with building outside swift-apis repository. Add the relevant headers to the top-level module.modulemap, they'll be distributed as part of the toolchain.

Depends on https://github.com/apple/swift/pull/30568.

I really think that this needs to be adjusted - the X10 modules should not be part of CTensorFlow.


burp-suite-community-np: Add autoupdate hash extraction

[x] I have read the Contributing Guide.

/verify


Exclude cygrpc.so from the Python package

cc @jtattermusch
Once released will address #5280.

Can one of the admins verify this patch?

Can one of the admins verify this patch?

Looks good; merge at your leisure.

Cool!

I'd really like a release with this fix:  #5280 is blocking me integrating grpc into gcloud-python.

We're in the process of doing a lot of various fixes at the moment this week. We're likely to do a 0.13.1 release early next week with the result of all that.

:+1:


Testing

This is only a test.
**lurch:add

**lurch:add

**lurch:add

**lurch:add

**lurch: add

It's alive... ALIIIIVE!!!

**lurch: detach

Detached W-008153

**lurch: attach

Tracking W-008154


Getting the mauve source - Cannot connect to host sourceware.org

We have an issue getting the mauve source Cannot connect to host sourceware.org:2401 in systemtest.getDependency. The following PRs cannot be verified at the moment.
https://github.com/adoptium/aqa-systemtest/pull/489
https://github.com/adoptium/aqa-tests/pull/5711
https://github.com/adoptium/STF/pull/140
https://github.com/adoptium/TKG/pull/633
get-source:
     [exec] Could not read password for host: java.io.FileNotFoundException: /home/jenkins/.cvspass (No such file or directory)
     [exec] Cannot connect to host sourceware.org:2401.
     [exec] Result: 1

https://github.com/adoptium/aqa-systemtest/blob/901f940a97d4a21fa740189e03d5518799c60c14/openjdk.test.mauve/build.xml#L380-L390

Identified git repos for mauve:

https://github.com/koadman/mauve
https://github.com/koadman/mauve

This is our last successful mauve build link, it can be unjar to find the source code. Thanks.

Last successful at the adoptium server is here: https://ci.adoptium.net/job/systemtest.getDependency/202/
mauve.jar.zip

https://openj9-jenkins.osuosl.org/job/systemtest.getDependency/51/ still failed.
I am considering backing the changes and branching out for the January release.
Moving forward, we should compare source code in the jar (https://github.com/adoptium/aqa-tests/issues/5760#issuecomment-2486600539) with identified mauve git repos and build from the update to date material. We might also want to keep a copy ourselves as a backup in case the personal git repo is deleted.

https://github.com/adoptium/aqa-systemtest/pull/493
https://github.com/adoptium/aqa-tests/pull/5773
https://github.com/adoptium/STF/pull/141
https://github.com/adoptium/TKG/pull/639


fix error logging

the defer here doesn't seem to work properly, instead just keep it simple and log twice manually

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


Clean up: ErrorList.HandleError() is no longer used.

We need to remove this method that is no longer used.

Fixed


Move raw input generation to khiin-data

Currently, the database contains entries in Lômájī, and we generate the raw input sequences (e.g. Lo5ma2ji7) here. This logic should be moved out of the engine and into khiin-data so that it is available statically within the engine and does not need to be generated dynamically. The original idea was to allow users to select their own keys for certain items like tones, and regenerate these input sequence maps on demand. However, this generation is too slow and making it happen in a background thread was more difficult than expected. Moving it into khiin-data (in Python) would be much easier at this point.

The table generation on khiin-data side are done: https://github.com/aiongg/khiin-data/commit/4e6fcca00f58a428e32a6d6a130118eb7f951d05
Now it just needs to be implemented in Database.cpp and Dictionary.cpp.

Finished by #4


060 - Record-to-Report

Thank you for your feedback on the data elements. We will consider your feedback as we continually assess how we can improve data definitions.
This is the place to leave your feedback and questions about the following data elements:
• UniqueInvestmentIdentifier
• AccrualAdjustmentAmount
Also, after reviewing these elements and the selected DAIMS and Fiscal Service Data Registry elements, if you believe that there are data elements that have been excluded from this end-to-end business process, please comment here as well.
The feedback period for these elements closes on 2/16/2018.

Are agencies expected to have a field called uniqueInvestmentIdentifier in their financial systems?

Short answer, no...
We do not require that there is a field explicitly called "uniqueInvestmentIdentifier" in your agency's FM system, however we do expect that there is data that can be used to identify the information outlined in our newly proposed definition of "uniqueInvestmentIdentifier".
Check out our definition then evaluate your FM systems/solutions.  If you have feedback on the definition that we have presented, be sure to provide it by 2/16!!
I hope that I've answered your question!
FIT


feat: fixed for the issue (#260)

1. Description

1.1. Checklist

[ ] The title of my PR starts with a Conventional Commit prefix (fix:, feat:, docs: etc).
[ ] I have read the Contributor Guide and followed the process outlined for submitting PRs.
[ ] I have updated/added tests for ALL new/updated/fixed functionality.
[ ] I have updated/added relevant documentation in docs and added dartdoc comments with ///.
[ ] I have updated/added relevant examples in examples.

1.2. Breaking Change

[ ] Yes, this is a breaking change.
[ ] No, this is not a breaking change.

1.3. Related Issues

Codecov Report

Merging #560 (897117a) into main (e6e846e) will increase coverage by 0.13%.
The diff coverage is 100.00%.

:exclamation: Current head 897117a differs from pull request most recent head 05cf1a1. Consider uploading reports for the commit 05cf1a1 to get more accurate results

:exclamation: Your organization is not using the GitHub App Integration. As a result you may experience degraded service beginning May 15th. Please install the Github App Integration for your organization. Read more.
@@            Coverage Diff             @@
##             main     #560      +/-   ##
==========================================
+ Coverage   67.55%   67.69%   +0.13%
==========================================
  Files         204      206       +2
  Lines        1945     1953       +8
==========================================
+ Hits         1314     1322       +8
  Misses        631      631

Impacted Files
Coverage Δ

packages/atproto/lib/src/entities/server_info.dart
100.00% <100.00%> (ø)

...es/atproto/lib/src/entities/server_info_links.dart
100.00% <100.00%> (ø)

...kages/atproto/lib/src/servers/servers_service.dart
100.00% <100.00%> (ø)

packages/bluesky/lib/src/bluesky_base_service.dart
100.00% <100.00%> (ø)

packages/bluesky/lib/src/feeds/feeds_service.dart
97.22% <100.00%> (ø)

...ackages/bluesky/lib/src/graphs/graphs_service.dart
100.00% <100.00%> (ø)

...y/lib/src/notifications/notifications_service.dart
100.00% <100.00%> (ø)

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Add Opensearch Test Coverage Report to CodeCov

Is your feature request related to a problem? Please describe
When running gradle check for opensearch repo, we can also generate test coverage report and upload them to CodeCov.
Describe the solution you'd like
Using this ./gradlew check -Dtests.coverage=true --no-daemon --no-scan we can generate coverage report and using script something similar to this:
TOKEN=
curl -Os https://uploader.codecov.io/v0.1.0_4653/linux/codecov
chmod +x codecov
./codecov -t ${TOKEN} -f "codeCoverageReport.xml"

we can upload it to codecov. We need to hide actual TOKEN value in above script
Describe alternatives you've considered
No response
Additional context
No response

Closing this issue. This work is already tracked on issue #1320


Fix unregister reminder concurrency issue

Description
There was a concurrency issue with actors that resulted in some actors not getting deleted from the state store. This was due to being able to unregister/delete a reminder between our reminder existence checks. We could call an update to the store after the deletion and recreate the entry. This commit adds an additional check to see if the reminder is still active before sending an update request to the store.
Issue reference
Please reference the issue this PR will close: #4801
Checklist
Please make sure you've  completed the relevant tasks for this PR, out of the following list:

[x] Code compiles correctly
[ ] Created/updated tests
[x] Unit tests passing
[ ] End-to-end tests passing
[ ] Extended the documentation / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Specification has been updated / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]
[ ] Provided sample for the feature / Created issue in the https://github.com/dapr/docs/ repo: dapr/docs#[issue number]

/ok-to-test


Not sure how to setup zulip as a self hosted server, ubuntu 22.04

Hey there guys, I am trying to setup a self-hosted zulip but once I get my one time use link and put it in the url it doesnt work,

I get that it is a.b.c.d , though it should still work on my local network correct?

I'm going to close this issue because there isn't enough to understand the issue.  If you're still having trouble, do reach out in #production help on the Zulip development community server.


Add new revenge proxy to PROXY_PREFIXES

This PR adds the new revenge proxy (https://revenge-plugins.github.io/proxy) to the
PROXY_PREFIXES.

but we have #33 so this is kinda unnecessary

but we have #33 so this is kinda unnecessary

ah, didn't notice that :woozy_face:

closing because #33 has more functionality


Missing usbhid in Host-Specific Image

I have encountered an issue where the usbhid module is missing from the generated initramfs image when no USB devices are connected during the build process. This issue prevents the unlocking of LUKS volumes using FIDO2. It occurs specifically when creating a host-specific image, which only includes kernel modules used by the current host.
Force loading these modules (as in #236, plus hid_generic) is a potential solution, but it was removed in 31d06a47708a139c159cb96dc7dc067a64230db0.

cc @c3Ls1US
I wonder if would want to restore the force-load part.
for _, file := range conf.extraFiles {
		if file == "fido2-assert" {
			conf.modulesForceLoad = append(conf.modulesForceLoad, "usbhid", "hid_sensor_hub")
			break
		}
	}

We could, but, strictly in terms of creating a host specific image,  isn’t the system working as intended?
But if we want to look into fixing this, instead of force loading, maybe a better idea is for Booster to detect if the user’s root volume was FIDO2 encrypted then include the module. I believe that metadata should be in the LUKS2 header, especially if systemd was used.

Hello @c3Ls1US,
Image builds could occur during package updates when the FIDO2 device may not be accessible, which is not the intended behavior for users. I agree that it would be better for Booster to detect the volumes and determine which modules to include accordingly.