Better document how to make an authenticated call to google storage

Making an authenticated call to google storage should be better documented. I filed a ticket with the google samples repo here: https://github.com/GoogleCloudPlatform/golang-samples/issues/1335
Basically, I have some auth info here:
const authInfo = {
  "type": "service_account",
  "project_id": "cp",
  "private_key_id": "219ea05d6xxxxxxxxxxxxxxxxxx15c9d58ae41",
  "private_key": "-----BEGIN PRIVATE KEY-----\nMIIEuwIBADANBgkqhkiG9w0BAQEFAASCBKUwggShAgEAAoIBAQCwv8UbpV5+FCYs\nITueZWyrcxxMaos+QBFU0GMBVWxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxD2tK1aaUR6+ovhj70yBnHDRdAu\nAnskcDEi6vTPKU6gNz8dC0gdE94dfaQy7k6tlg9hQq/J+MgrUAR3HOf1FyzhMyLh\n7qlnN5WNgBIz1imM/u9k\n-----END PRIVATE KEY-----\n",
  "client_email"<EMAIL_ADDRESS>  "client_id": "1071381xxxxx900319",
  "auth_uri": "https://accounts.google.com/o/oauth2/auth",
  "token_uri": "https://oauth2.googleapis.com/token",
  "auth_provider_x509_cert_url": "https://www.googleapis.com/oauth2/v1/certs",
  "client_x509_cert_url": "https://www.googleapis.com/robot/v1/metadata/x509/back-end%40cp.iam.gserviceaccount.com"
}

why can't I find a good example of how to pass the auth info to the google storage initialization here:
const {Storage} = require('@google-cloud/storage');

const storage = new Storage();

const bucketName = 'bucket-name';

async function createBucket() {
  await storage.createBucket(bucketName);
}

so if I have the auth info where the f do I stick it and how?
something like this:
const {Storage} = require('@google-cloud/storage');

const storage = new Storage(authInfo);  // here maybe?

const bucketName = 'bucket-name';

async function createBucket() {
  await storage.createBucket(bucketName, authInfo); // or here maybe?
}

I realize there is probably more than one way to authenticate but with some keys and certs I just want to get it done.

For example, I see this:
 const storage = new Storage({keyFilename: "key.json"});

umm so why don't we have an example of just passing a JS object?
 const js = require('../key.json'); // we get the file
 const storage = new Storage(js); // we pass the object not the filepath

seems like the object version instead of the filepath version is more intuitive and type-checking is also easier?

keyFilename is for passing a path, credentials is used to pass a credentials object.  Like so:
const {Storage} = require('@google-cloud/storage');

const storage = new Storage({
  credentials: authInfo
});

const bucketName = 'bucket-name';

async function createBucket() {
  await storage.createBucket(bucketName);
}

that's cool, any idea how to do that with the golang library? GoogleCloudPlatform/golang-samples#1335

is there a way to use the .json file in the front-end? or does this lib only work with node.js?

i think it is  poorly documented how to use the credentials object. Having to use a json file in some scenarios is overwhelming. Having environment variables that could handle that for you.
Is there anyone that have found the correct way of using credentials?

These are the choices for authentication:
new Storage({ keyFilename: '/path/to/service-account-key.json' })
new Storage({ credentials: require('/path/to/service-account-key.json' })
new Storage() // env var: GOOGLE_APPLICATION_CREDENTIALS=/path/to/service-account-key.json

thanks @stephenplusplus plus
I ended up setting this
const storage = new Storage({
  credentials: {
    client_email: process.env.GOOGLE_CLIENT_EMAIL,
    private_key: process.env.GOOGLE_PRIVATE_KEY.replace(/\\n/g, '\n')
  },
  projectId: process.env.GOOGLE_PROJECTID
})

@rafinskipg thank you! This is so much simpler than having to get a file system involved!


ERROR | Attributeerror : module 'whisper' has no attribute 'version'

same issue

Have you guys installed pip install -r requirements.txt and followed all the installation steps for your operating system?

Yes
On Fri, Jul 21, 2023 at 4:07 PM Rayventura @.***> wrote:

Have you guys installed pip install -r requirements.txt and followed all
the installation steps for your operating system?
—
Reply to this email directly, view it on GitHub
https://github.com/RayVentura/ShortGPT/issues/32#issuecomment-1646186026,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AYHD3SOWZ5NHIZSKW5GC3HTXRLORTANCNFSM6AAAAAA2TBVLOY
.
You are receiving this because you commented.Message ID:
@.***>

It is probably an error with your whisper installation, try pip install git+https://github.com/linto-ai/whisper-timestamped and tell me if that fixes it.

Yes both are installed getting this error
ERROR | Urlerror : [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: self signed certificate in certificate chain (_ssl.c:1002)

On Jul 21, 2023, at 4:07 PM, Rayventura @.***> wrote:
Have you guys installed pip install -r requirements.txt and followed all the installation steps for your operating system?
—
Reply to this email directly, view it on GitHub https://github.com/RayVentura/ShortGPT/issues/32#issuecomment-1646186026, or unsubscribe https://github.com/notifications/unsubscribe-auth/AYHD3SOWZ5NHIZSKW5GC3HTXRLORTANCNFSM6AAAAAA2TBVLOY.
You are receiving this because you commented.

I have fully installed PIP packages (pip install -r requirements.txt) but still getting the above error

Try to uninstall ffmpeg and install python-ffmpeg


Sample 18 - Add react hot loader support

Add react hot loader support based on:
https://github.com/wmaurer/react-hot-boilerplate-ts/blob/master/src/App.tsx
http://blog.novanet.no/hot-loading-react-in-typescript/

Merged PR #68


change all references on the page to Colorflow

fixed in https://github.com/inttter/colorflow/commit/103e46f9a38ac5e301e3da8198972976f4ad9ef9


ignored css not working

Does the gulp plugin allow for this functionality? It doesn't seem to be doing anything for me.
/* uncss:ignore /
.selector1 {
/ this rule will be ignored */
}

Does the gulp plugin allow for this functionality?

Yes, it was added in 1.0.0. Are you using the latest version?

Yeah, I found the problem. Sass is exporting the comments in strange places. I'll have to play with it.Thanks!

:+1:


[Adopter]: Binero Group

Name
Binero Group
Website
https://binero.com/en
Logos

The Legal Stuff

[X] My organization consents to their logo being displayed on the Eclipse Temurin adopters page.

Closed via https://github.com/adoptium/adoptium.net/commit/61f56a5e31558a55ff00344e1e9a4f1c439e888b


How to run  InferAnalyze binary correctly?

I dowmload Infer version 0.8.0 in https://github.com/facebook/infer/releases.
Then I run "tar xf infer-linux64-v0.8.0.tar.xz" in Linux.
(The version of Python is 2.7 )
I modify the PATH as follows:
cd infer-*v0.\1.0 &&
echo "export PATH="$PATH:pwd/infer/infer/bin"" \ >> ~/.bash_profile &&
source ~/.bash_profile
But I cannot run InferAnalyze binary.
What should I do if I want to use infer check my code.

Hi @AliceTENGZI, these instructions are out of date, please follow this instead: http://fbinfer.com/docs/getting-started.html
On Linux you can use either Docker or build infer from source.

I saw some dependences as follows:
Infer dependencies for Linux
Here are the prerequisites to be able to compile Infer on Linux. This is required to be able to use the release (faster), or to compile everything from source (see the end of this document).
opam >= 1.2.0
Python 2.7
Java (only needed for the Java analysis)
gcc >= 4.7.2 or clang >= 3.1 (only needed for the C/Objective-C analysis)
autoconf >= 2.63 and automake >= 1.11.1 (if building from git)。。。。
Are the all dependences required if I just want to analysing java code???

Some of these dependencies are not needed for the java analysis: those marked "only needed for the C/Objective-C analysis". So what you need to build from a release is:

opam >= 1.2.0
Python 2.7
Java

[@sjs_14_125 bianyuteng]# opam --version
1.2.2
[@sjs_14_125 bianyuteng]# python -V
Python 2.7.5
[@sjs_14_125 bianyuteng]# java -version
java version "1.8.0_25"
Java(TM) SE Runtime Environment (build 1.8.0_25-b17)
Java HotSpot(TM) 64-Bit Server VM (build 25.25-b02, mixed mode)
[@sjs_14_125 infer-linux64-v0.8.0]# cat /etc/redhat-release
Red Hat Enterprise Linux Server release 6.2 (Santiago)
Above is my install enviroment.
But when I run "./build-infer.sh"
As follows the err information:
[@sjs_14_125 infer-linux64-v0.8.0]# ./build-infer.sh
initializing opam...
[WARNING] Running as root is not recommended
[ERROR] Initialisation failed
Fatal error:
Sys_error("No space left on device")
[WARNING] Running as root is not recommended
Checking for available remotes: [ERROR] Initialisation failed
Sys_error("No space left on device")
Fatal error:
Sys_error("No space left on device")

Sys_error("No space left on device")

Your disk ran out of space.

When I clean my disk for enough space.
and run "./build-infer.sh "..Error still exists as follows.
[@sjs_14_125 infer-0.8.0]# ./build-infer.sh
initializing opam...
[WARNING] Running as root is not recommended
[WARNING] Running as root is not recommended
preparing build...
checking if we are in an Infer release build... no
checking whether to use the compilers in /search/bianyuteng/infer-0.8.0/facebook-clang-plugins/clang/bin... no
checking for shasum... shasum
checking for python2.7... python2.7
checking for xcode-select... no
checking for C compiler default output file name... a.out
checking whether the C compiler works... yes
checking whether we are cross compiling... no
checking for suffix of executables...
checking for suffix of object files... o
checking whether we are using the GNU C compiler... yes
checking whether gcc -std=gnu99 accepts -g... yes
checking for gcc -std=gnu99 option to accept ISO C89... none needed
checking for gawk... gawk
checking for a BSD-compatible install... /usr/bin/install -c
checking whether ln -s works... yes
checking whether make sets $(MAKE)... yes
checking how to run the C preprocessor... gcc -std=gnu99 -E
checking whether we are using the GNU C++ compiler... yes
checking whether g++ -std=gnu++0x accepts -g... yes
checking if the C/C++ compiler is recent enough... no
configure: error:
Your C/C++ compiler seems to be too old to build clang, which is
required by the facebook-clang-plugins. Please install either
gcc version >= 4.7.2 or clang version >= 3.1.
See the output of ./configure --help to force the use of a different
C compiler.
Alternatively, you can checkout a release of infer with clang
pre-compiled here:
https://github.com/facebook/infer/releases/


ESA CCI V4 notebook new edits

updated description

Added some comments about the formatting, most of it just being small stuff and things to help with consistency with the other tutorials we updated. Overall it looks like a great notebook!

Hi @smk0033 @emileten ..Thanks for your inputs. I have addressed the comments and requested re-review. Please let me know if it looks good.

Thank you so much @jjfrench ..I have updated the notebook and requested your re-review.


Show tooltip on label instead of dom node at bug viewer.

Show tooltip on label instead of dom node at bug viewer.

Do I understand it right that the change is that the tooltip starts on the text, and not at the beginning of the line?
Current behaviour: https://github.com/Ericsson/codechecker/blob/1368e0bc4931cc7ce54e3ec828abd77aa23b1f8e/docs/images/viewer.png

Yes, you are right.


[BUG] Can not send telemetry from React app in Chrome

I configured application insights inside of my react app using the NPM Setup. I can send telemetry from Edge, but not from Chrome. The error I get in my console is as follows.
VM292:1 OPTIONS https://dc.services.visualstudio.com/v2/track net::ERR_BLOCKED_BY_CLIENT
Here is the error I get when I open the failed network call
Request URL: https://dc.services.visualstudio.com/v2/track
Referrer Policy: no-referrer-when-downgrade
Provisional headers are shown
Access-Control-Request-Headers: content-type,sdk-context
Access-Control-Request-Method: POST
Origin: http://localhost:3000
Referer: http://localhost:3000/login
Sec-Fetch-Mode: cors
User-Agent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/77.0.3865.120 Safari/537.36

Probably because of adblock


[-ContentLocation ]

I don't believe this switch works correctly, could you add an example
For Set-CMScriptDeploymentType and Set-CMWindowsAppxDeploymentType - these work as expected for those types of Deployment Type with just the content location ( no file names required. )
For Set-CMMSIDeploymentType, it appears you don't use a content location, you have to use a file path.
If you browse to the content location for the MSI, locate an MSI in there and append that to the content location, this then updates the content location, HOWEVER, it also wipes the current installation command and replaces it with a generic msi installation commandline for the MSI you appended to the command.
maybe just an example of ONLY changing the content path without modifying the installation properties.
this is what I would think the command should be
set-CMMsiDeploymentType -ApplicationName 'MyApp' -DeploymentTypeName 'MyDType - Windows Installer (*.msi file)' -ContentLocation '\myserver\myapp\V1'
If I use this (which updates the content path, it also wipes my installation command. )
set-CMMsiDeploymentType -ApplicationName 'MyApp' -DeploymentTypeName 'MyDType - Windows Installer (*.msi file)' -ContentLocation '\myserver\myapp\V1\myMSIv1.msi'
that is, rather than this command
set-CMMsiDeploymentType -ApplicationName 'MyApp' -DeploymentTypeName 'MyDType - Windows Installer (*.msi file)' -ContentLocation '\myserver\myapp\V1'
I use this (which updates the content path, but also wipes my installation command. )
set-CMMsiDeploymentType -ApplicationName 'MyApp' -DeploymentTypeName 'MyDType - Windows Installer (*.msi file)' -ContentLocation '\myserver\myapp\V1\myMSIv1.msi'

For a Script Deployment Type, this command works - that is, it ONLY changes the content path without changing the installation properties
set-CMScriptDeploymentType -ApplicationName 'MyApp' -DeploymentTypeName 'MyDType' -ContentLocation '\myserver\myapp\V1'

For an Appx Deployment Type, this command works - that is, it ONLY changes the content path without changing the installation properties
set-CMWindowsAppxDeploymentType -ApplicationName 'MyApp' -DeploymentTypeName 'Windows app package (*.appx, *.appxbundle)' -ContentLocation '\myserver\myapp\V1'

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 7b2ed382-df64-0705-8d70-a74ab4032d6f
Version Independent ID: 0400a5c5-6659-85ee-dbec-8ca6fa163d54
Content: Set-CMWindowsAppxDeploymentType (ConfigurationManager) - Configuration Manager
Content Source: sccm-ps/ConfigurationManager/Set-CMWindowsAppxDeploymentType.md
Product: configuration-manager
Technology: configmgr-other
GitHub Login: @aczechowski
Microsoft Alias: aaroncz

Hi @PaulKlerkx, I'm checking with the engineering team, I wonder if this is a bug?
Also, the feedback is assigned to the Set-CMWindowsAppxDeploymentType cmdlet (appx), but it seems like you're talking about the Set-CMMsiDeploymentType cmdlet (MSI)? Just making sure...

Assuming that the thrust of your feedback is around Set-CMMsiDeployment...we do have a couple of product bugs for it, specifically one about how changing the content location resets the DT. It would also improve the cmdlet to match the UI experience, where supposedly you can specify either a file or folder path.
I can't make any promises as to when those changes will happen, but it looks promising for a release later this year 😉 So I'm going to close this issue and not make any changes to the article, and wait for the changes to the cmdlet.


Typo in BTC RPC Explorer dialog [release 1.6]

"build" --> "built"

Thanks - typo fix will be part of service release 1.6.1.


DCR: .dialog resource binding should fallback to non-hardcoded extensions.

We should add fallback for string reference binding "foo.xxx" => looks for "foo.xxx.dialog" and if not found attempts to bind to "foo.xxx",
The point of these changes is that it allows new extensions to be added to the resource explorer, and if there are object bindings for those extensions they will be used. If a file is valid json but NOT a dialog file (Such as .schema files) then they can be used directly without having to have .dialog extension.
For example, this captures the 2 scenarios:

"recognizer":"foo.lu" => will bind to attempt to bind to "foo.lu.dialog"
"schema":"foo.schema" => will attempt to bind to foo.schema.dialog, and then fall back to foo.schema, which is a valid JSON object to bind and it will load it. (Thus removing the need to have schema file be foo.schema.dialog.

PR is #3640

i didn't fully get this short-term fix, i mean i understand what it does, but seems not align with long term goal.  By fall-backing to resource.id, we are implying that we are encouraging using different file extension to distinguish types.  How about we just fallback from resource.id.dialog to resourc.id.json, and start encouraging people to serialize stuff other than dialog into json, and use "name" instead of "extension" to distinguish, like "recongizera.json"?
I means we are easily go from recongzier_a.json to a.recoginzer, but probably not the vice versa

This is about allowing you to refer to a json file (regardless of extension) without having to add .dialog on to the reference.


Revert "2024.1.0: Advanced clock - draw date"

Reverts lubeda/EspHoMaTriXv2#197
Your sample does not work!
Compiling .pioenvs/m5mic/src/main.cpp.o
<unicode string>: In lambda function:
<unicode string>:173:16: error: 'class esphome::EHMTX' has no member named 'set_clock_infotext_color'; did you mean 'set_infotext_color'?
<unicode string>:174:16: error: 'class esphome::EHMTX' has no member named 'set_adv_clock_color'; did you mean 'set_clock_color'?
<unicode string>:177:16: error: 'class esphome::EHMTX' has no member named 'set_date_infotext_color'; did you mean 'set_infotext_color'?
*** [.pioenvs/m5mic/src/main.cpp.o] Error 1

Your sample does not work!

This is a piece of my working config, which I use constantly every day, yesterday I rebuilt it and everything came together perfectly.
Are you sure you haven't forgotten about advanced_clock: true ?
https://github.com/lubeda/EspHoMaTriXv2/pull/198/files#diff-345f4882a9621cc8a04520b628475a419357f3b98b092260e4749d646698ab16L241-L247


Code refactor

Currently, the code is written mostly in functions. Would be good to introduce classes into the code architecture.
Update the commit history as well.

Can this issue be edited only to commit history?
As we have introduce classes everywhere?

@iammarco11 It was a general idea, perhaps we can close it soon enough when most of the code has been re-written in the past few days


README.md refers to tohuw fork

Hi,
Great that the tohuw fork was merged ( #28 )!
I have spotted one cosmetic flaw: The caveats section of README.md talks about "if you are coming from ..." as if you've switched to the tohuw fork.

Good catch! Thanks.


Disabled CollisionShape2D still interacts with one way collision shapes

Godot version:
Godot 3.1 Beta 4
OS/device including version:
Windows 10 64 bit
Issue description:
A disabled CollisionShape2D child of a KinematicBody2D makes a call to move_and_collide return a collision with a one way collision body even if no collision should happen.
The bug is present in 3.1 Beta 4, but it wasn't in 3.1 Alpha 2.
Steps to reproduce:
This is the player scene view:

The gray rectangle in the middle, AlternativeShape2D, is a disabled rectangle, so it shouldn't interfere with collisions. The bigger one is CollisionShape2D.
When the player jumps but doesn't reach the top of the one way platform, he lands in the air:

While changing AlternativeShape2D's parent node the player behaves as expected::

Minimal reproduction project:
disabled_collider_test.zip

I dont understand the bug by just looking at it or testing it, but I fixed what seemed to be an inconsistency.
Can you give it a try and reopen if the problem persists?

The bug is fixed now, thanks!


Sass instruction work well in App but not in Addon

Hi,
I am faced with something really weird.
I am tying evolve the ember-bulma add-on to a sass import version like ember-cli-foundation-sass.
Everything could working well unless one thing.
I have already used bulma sass with ember-cli-sass from scratch and everything goes OK. But when I use it inside an addon, only one line of the bulma source make it just crash.
.header-item > a:not(.button)

I really do not know why this specific line break it only in addon.

I finally found the guilty.
In my ember-app the node-sass version used is 3.4.2 and in the recent addon the version is 3.5.3.
So I force to fallback into the first one version and everything work well, right now.

May be linked to aexmachina/broccoli-sass-source-maps/issues/19

@aexmachina - I think you have hundreds of people hitting this error now. Due to the crash happening inside native code, inside a node-gyp wrapper, inside a broccoli plugin, inside an ember addon, it's extremely difficult for a novice developer to troubleshoot and track down.
My suggestion is that, per aexmachina/broccoli-sass-source-maps/issues/19 you roll back the supported node-sass version so there's an easy and conventional path forward (i.e., install the addon and you're good to go, for all versions of node.js that ember-cli officially supports).

Thanks @mike-north, but the solution to this issue is to specify which version of node-sass to use until the underlying issue is fixed.


How is the FPS of MVP?

I'm curious about the FPS of MVP. Is it much slower than pure centerpoint?

I don't have exact number but it is slower as we need to run a 2d model on top of 6 camera images. So the runtime is like 6 * CenterNet + 1 * CenterPoint + 5~10ms for virtual point generation.

Thanks！

@tianweiy The CenterNet is very slow.

Well, it depends(on your definition of slow). It is 40fps(for one image) in our setup and different image could be pipelined in real deployment.

How can you achieve 40fps??? So amazing.

OK! Thank you, I will have a try. Making the total model real-time is so hard.

OK! Thank you, I will have a try. Making the total model real-time is so hard especially on Xavier.

Well, I suggest using lidar only model on Xavier then. Any camera will be too slow..

OK!


Changed the 1st blog title blog-sidebar-left.html

Changed the 1st blog title on blog-sidebar-left.html page under agriculture
redo this to resolve the conflicts

This already has a title that works fine. No need to change.


inspect commands return structured JSON

0c4e5bcce52c6d746db29aa3d3043eb1a38f65df
:round_pushpin: return structured JSON instead of pretty string for address introspection
So that the output can be easily parsed and used by another software.

TODO: key inspect as well for consistency.

Great work @KtorZ. I've defined types for Daedalus (Flow) as follows:
export type IntrospectAddressRequest = {
  input: string
};

export type AddressStyle = 'Byron' | 'Icarus' | 'Jormungandr' | 'Shelley'

export type ChainPointer = {
  slot_num: number,
  transaction_index: number,
  output_index: number
}

export type AddressBase = {
  address_style: AddressStyle,
  network_tag: number | null
}

export type ByronAddress = AddressBase & {
  stake_reference: 'none',
  address_root: string,
  derivation_path: string,
}

export type IcarusAddress = AddressBase & {
  stake_reference: 'none',
  address_root: string,
}

export type JormungandrAddress = AddressBase & {
  address_type: 'single' |'group' | 'account' | 'multisig',
  account_key?: string,
  merkle_root?: string,
  stake_reference: 'by value' | 'none',
  spending_key?: string,
  stake_key?: string,
}

export type ShelleyAddress = AddressBase & {
  pointer?: ChainPointer,
  stake_reference: 'by pointer' | 'none',
  script_hash?: string,
  spending_key_hash?: string,
  stake_key_hash?: string,
  stake_script_hash?: string,
}

export type IntrospectAddressResponse = {
  introspection: ByronAddress | IcarusAddress | JormungandrAddress | ShelleyAddress
} | 'Invalid';

Is AddressBase.network_tag typed correctly for all styles?

@rhyslbw there are 3 fields that are on every address, so I'd suggest AddressBase as follows:
export type AddressBase = {
  address_style: AddressStyle,
  network_tag: number | null,
  stake_reference: 'none' | 'by value' | 'by pointer'
}

Also, the network_tag can only be null for Icarus & Byron addresses. It'll necessarily exists on Shelley & Jormungandr addresses. Not sure if this needs to be captured.

Not sure if this needs to be captured.
If we're merging the two stake_reference types then I think this is fine for the current use-case


Refactor checkout-flow e2e tests

checkout-flow.e2e-spec.ts recently failed on Jenkins.
I will be refactoring checkout-flow.ts as it is the helper class for all checkout tests.
This test has always been inconsistent and I believe it's due to the size of the test.
I'm going to attempt to make it consistent by applying cypress waits for every page redirect.

PR: https://github.com/SAP/cloud-commerce-spartacus-storefront/pull/3750


BUG - Invalid URL error when entering a valid PR link during onboarding

There seems to be a bug during onboarding.
Service Name: Fairfield Gardens
Offering Name: Fairfield Gardens
PR Links:
Data Plane PR: https://github.com/Azure/azure-rest-api-specs-pr/issues/15060
Management Plane PR: https://github.com/Azure/azure-rest-api-specs-pr/pull/15107

@ladonnaq

Data Plane PR: https://github.com/Azure/azure-rest-api-specs-pr/issues/15060

This is incorrect. They are linking a GH issue that tracks the stewardship meeting. See how the URL has issues in it instead or pull. Looking at that issue, the PR for data plane is https://github.com/Azure/azure-rest-api-specs-pr/pull/15290


Jupyter Book: Collapse multiple books in the workspace setting

Is your feature request related to a problem? Please describe.
My workspace has more than 7 books with multiple chapters. When the workspace is opened, the books are all expanded to the first level chapters.
Describe the solution or feature you'd like
When opening a workspace with multiple books, it should be possible to configure the workspace to open the books collapsed by default.
Describe alternatives you've considered
Manually collapsing book one by one.
Additional context
Livesite

Ack. Until we have this implemented, it's good to direct folks to the collapse action in the viewlet:


upgrade to new analytics-browser SDK

Upgrades the package to the newer analytics-browser SDK following the direction from the migration documentation

@maecapozzi I linked this package into our DS package to test my changes but when I run storybook I'm getting really obtuse errors that don't seem to be related to the new SDK but I'm unsure. Is this the correct way to test this package?
unable to close vite server
REPOPATH/node_modules/@storybook/core-server/dist/cjs/build-dev.js:191
    } else if ((_error$compilation = error.compilation) !== null && _error$compilation !== void 0 && _error$compilation.errors) {
                                           ^

TypeError: Cannot read properties of undefined (reading 'compilation')
    at buildDev (REPOPATH/node_modules/@storybook/core-server/dist/cjs/build-dev.js:191:44)

Node.js v18.15.0
error Command failed with exit code 1.
info Visit https://yarnpkg.com/en/docs/cli/run for documentation about this command.

@jimmynotjim - how did you link it? Can you provide a code snippet to show what you did?
I set this package up to publish "canary" releases, so you should also be able to test it by installing this version<EMAIL_ADDRESS>

I used yarn link in this repo and then ran yarn link @amplitude/storybook-addon-amplitude in the package in our private repo. Turns out using the canary build works great though so I think this PR is ready for review.

Yeah, I feel like yarn link can be kind of sketchy, so I always publish a canary version as well.


Tag spacing

Description of Changes
Please check that the PR fulfills these requirements

[ ] Tests for the changes have been added (for bug fixes / features)
[ ] Docs have been added / updated (for bug fixes / features)
[ ] Add a changelog entry (for non-trivial bug fixes / features)
[ ] CI passes

Log Files
Logs / Second
CPU Average (%)
Memory Average (MB)

1
1000
2.6207511
27.641163

1
5000
5.3621716
32.889145

1
10000
9.017445
40.215652

1
50000
36.1053
129.33675

1
100000
68.12026
210.32974

10
100
3.5690384
27.912312

10
500
7.034582
33.893456

10
1000
12.276412
43.93669

10
5000
41.98384
95.93629

10
10000
73.843346
204.113


tests: add tests for tld and domain transformations.

Continuation of #101
This PR adds tests for new transformations: tld and domain and tests code added in https://github.com/OISF/suricata/pull/4063
This update modifies the domain rule per updated domain transform logic.

Looks like the pcap files are pcap-ng. Unfortunately not all our supported platforms support that yet. Can you convert them to regular pcap?

Continued in #105


Podium: banner element/tile for Issue

Hi @rdunk -- can we append the Issue number to the banner and tile in the following two instances (ideally this would be dynamic):
Tile:

Banner:
Can we also add the contributors to the banner element?

Chinese syntax:
Podium Issue {1}
博文集第{1}期
Not having the Issue number there is less than ideal when viewing the site in Chinese.

Hi @chrismplus, almost ready to push this—it was a little tricky to implement. The implementation means I can easily add it for other sections too though (i.e. search results, suggested items), would this be preferable?

Implemented in c546850b42905bbf92d986f3ff085e73230c06d9. Let me know if you want me to roll it back for search results.

@rdunk -- do you mean when Issues are returned through search results? I don't think Issues will surface easily in search results--they're not really being surfaced through searches at the moment. In ticket #125 we actually discuss removing the Issue as a search filter.

Hi @rdunk -- noted the Issue number is appended to Podium Issue. This fixes the syntax issue we were facing with Chinese language page. As noted above in the ticket--is it also possible to include the contributors in the banner?

Ah, I didn't see that one. Yep should be possible, can implement that today.

Done a3e3ff2f83cef952c63a689c03ba0b3dfe4a9b72!


Really?

Obviously adding the domain to tenant whitelist resolves most of if not all email deliverability issues, however is that really a practicable solution at present time, considering the 'well-known' nature of the domain in question? Will it never be spoofed by anyone??

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 43bc0cae-682a-7227-35d6-d3c37545a3a4
Version Independent ID: fbcd00ac-8899-fb95-28aa-dfc523b81c65
Content: Add the Microsoft Teams SMTP domain as an allowed sender domain in Exchange Online
Content Source: Teams/SMTP-accepted-domain.md
Service: msteams
GitHub Login: @LolaJacobsen
Microsoft Alias: lolaj

@NormundsKarklins Thank you for this inquiry
I am not sure of the answer for this domain whitelist inquiry. Let me get this over to the Teams writing team for investigation.
Thank you for reporting and making the docs better. Much appreciated.
I made a note to request the team to update this when the work is complete.

@NormundsKarklins - thank you for taking the time to submit feedback on the content. I can work with you to figure out how to make the content better.

@NormundsKarklins - I am reading through the article and thinking what could be done to the article to make it better and address your concern about spoofing. Do you have any suggestions? As you mentioned, any domain could be spoofed to avoid a spam filter.
Perhaps the best thing to do is add a note to the article that if you prefer not to whitelist the domain then you need to make sure your users check their spam folder? Open to any suggestions here. Thanks.

In my humble opinion, Teams ‘as a service’ should not transpose the responsibility to Customers for this matter in first place.
Apologies for being unable to provide a perfect suggestion here – I do not work at Microsoft and I have no experience in interacting with Exchange ‘Forefront’ (aka EOP) or ATP people of Microsoft 365 platform (where the false-positive spam detection apparently can occur).
If it is impractical to achieve satisfactory cooperation with the Microsoft cloud service teams in charge for spam detection, I’d personally think of a possibility to insert into message headers of Teams a tenant-configurable text string which then respective mailserver admins could use to ‘whitelist’ the actual messages from Teams.
It is a bit old school approach in the modern days of domain validation means such as DMRD/DKIM/SPF being available, of course, but if the circumstances require additional actions to assure messages from Teams are not junked by Recipients, then ‘wholesale’ domain whitelisting, in my humble opinion, should be the last resort in case of a well-known source domain.
Sincerely,
N.Karklins
From: Ken Withee<EMAIL_ADDRESS>Sent: Monday, December 10, 2018 10:23 PM
To: MicrosoftDocs/OfficeDocs-SkypeForBusiness<EMAIL_ADDRESS>Cc: Karklins, Normunds<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [MicrosoftDocs/OfficeDocs-SkypeForBusiness] Really? (#1134)
@NormundsKarklinshttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FNormundsKarklins&data=02|01||d846b07343244fd4884a08d65ee5a661|1a407a2d76754d178692b3ac285306e4|0|0|636800737758383066&sdata=yopx9%2FPeZDlvnfDpmaCsJXWvAK5rHoHcfeRCnO%2FYjis%3D&reserved=0 - I am reading through the article and thinking what could be done to the article to make it better and address your concern about spoofing. Do you have any suggestions? As you mentioned, any domain could be spoofed to avoid a spam filter.
Perhaps the best thing to do is add a note to the article that if you prefer not to whitelist the domain then you need to make sure your users check their spam folder? Open to any suggestions here. Thanks.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2FOfficeDocs-SkypeForBusiness%2Fissues%2F1134%23issuecomment-445978482&data=02|01||d846b07343244fd4884a08d65ee5a661|1a407a2d76754d178692b3ac285306e4|0|0|636800737758383066&sdata=N%2F%2B%2F0EfQQSRN0uezsgQW%2Fnl5t38MZdaw8t6D%2B0bTL6k%3D&reserved=0, or mute the threadhttps://emea01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FArR13VK9op-1ITdOK180mDEgdys2ujOPks5u3tCsgaJpZM4Y0wxn&data=02|01||d846b07343244fd4884a08d65ee5a661|1a407a2d76754d178692b3ac285306e4|0|0|636800737758393070&sdata=lDjmDucnzlHb2Qla0bW2D51s92mVA6ux46dn4v9lqRg%3D&reserved=0.

The information contained in this message may be confidential and legally protected under applicable law. The message is intended solely for the addressee(s). If you are not the intended recipient, you are hereby notified that any use, forwarding, dissemination, or reproduction of this message is strictly prohibited and may be unlawful. If you are not the intended recipient, please contact the sender by return e-mail and destroy all copies of the original message.

@NormundsKarklins - this is great information and I agree with you that there needs to be a better way to handle this. I know the Teams group gets their user information from a place called User Voice ( microsoftteams.uservoice.com ) and they do work across teams to focus on the user experience and not the internal organization. In the past Microsoft was a very different place but now it seems the organizational structure takes a far back seat to the customer needs and experience.
I did a search on 'whitelist' on the User Voice, https://microsoftteams.uservoice.com/forums/555103-public?query=whitelist and I am going to go through and up vote similar issues too. If you don't mind taking a look and if you would want to open another specific issue please let me know and I will use my up votes to up vote it. I think it is really good feedback that the Teams group should hear. I will close this out and head over to User Voice but you can continue to reply here if you want to let everyone know of a specific User Voice that we can all up vote. Thanks again for taking the time to improve the content and the product. I hear first hand how much everyone around Microsoft and the community appreciates it.


Adding new custom attributes that we use internally

Includes one to return the active IP address (useful when a machine is on a VPN), SSH version, OpenSSL version, local admin accounts on a machine, and a machines local hostname.

@jbaker10  Thanks for these updates. Once you amend your commit message to include the DCO (Developer Certificate of Origin), I'll merge the request.
How to amend commit

Hi @menelson I added the DCO for each commit and squashed them into 1. Does that work?

Gentle bump on this PR

Thanks for the contribution @jbaker10!!


Expose health-check via RPC

Request from testnet validators:

For monitoring purposes it is maybe handy to get the health-check on the rpc.

which RPC? external chains?

Indeed, it's handy to have most of the checks via rpc. So docker and binary will have the same check.


Move staff email addresses to settings

We have a number of email addresses embedded in the code that are sent emails on events (like a new sponsor application being submitted).  The financial aid application makes provision to override the default address using settings, but we're not using that.
The result is probably that the people at the other end of these addresses are getting emailed as we do our testing on local systems and the staging site, and have to ignore these test messages.
We should have all these addresses in settings, and only point them at the real addresses for production. The others should either go nowhere or to the development team by default.

One thought, then :email:


why the official website of uploadify is redirected to here ?

I decided to open source the code. The Flash version is no longer supported, but the HTML5 version is available here. I still need to move over all the documentation though.

Where can I find some documentation about uploadify? Thanks.


Trollweiss Cave Upgrade

Defines textures on objects and walls inside of the Trollweiss caves, also sets environment.

I ended up removing this part, as it effectively only changed 92 & 94 from dirt to grunge, and it wasn't restricted to a specific area:
// Default underlays
UNDERLAY_TROLLWEISS_CAVE_FLOOR(GroundMaterial.GRUNGE, p -> p
        .ids(92, 94) // 8 = Jatizso, 60 = GotR, 92 = Eadgars Cave
        .replaceWithIf(WINTER_GRUNGE, plugin -> plugin.configWinterTheme)
),


Support remote debug for functions written in C#

Repro steps:

Action: azureFunctions.startRemoteDebug
Error type: Error
Error Message: Azure Remote Debugging is currently only supported for Node.js Function Apps running on Linux App Service plans. Consumption plans are not supported.
Version: 0.19.1
OS: darwin
Product: Visual Studio Code
Product Version: 1.39.2
Language: en

Call Stack
Object.t.checkForRemoteDebugSupport extension.bundle.js:353:77791
extension.bundle.js:353:77501
o extension.bundle.js:353:76816
process._tickCallback next_tick.js:68:7

any updates to this?

No plans at the moment. Related to https://github.com/microsoft/vscode-azurefunctions/issues/314

This issue has become stale and is at risk of being closed. The community has 60 days to upvote the issue. If it receives 5 upvotes we will keep it open and take another look. If not, we will close it. To learn more about how we handle issues, please see our documentation.\n\nHappy Coding!

:slightly_frowning_face: In the last 60 days, this issue has received less than 5 community upvotes and we closed it. Still a big Thank You to you for taking the time to create it! To learn more about how we handle issues, please see our documentation.
Happy Coding!


[mitigated] HDR Screen Dim

VSCode Version: 1.42.0-insider (user setup)
OS Version: Windows_NT x64 10.0.19041

Steps to Reproduce:

Open VSCode on Win 10 with an HDR screen

Does this issue occur when all extensions are disabled?: Yes
I know this issue was resolved previously (https://github.com/microsoft/vscode/issues/68069 and https://github.com/microsoft/vscode/issues/72373). The --force srgb trick still works, but for the past few weeks it was not necessary.

@deepak1556 looks like this was fixed originally by an electron update, something regress here?

@AzureWolf ok let's try that experiment again if you can. There is a newer build available [1]

close any running instance of VSCode
download [1]
quick open command palette and pick "Configure Runtime Arguments"
replace the file with the contents below [2]
close
start same version again

=> are the colors better?
[1] https://az764295.vo.msecnd.net/insider/a1f569c66f67287c525ee50b5f46ced8a50b4551/VSCode-darwin-insider.zip
[2]
{
	"disable-color-correct-rendering": true,
	"force-color-profile": "srgb"
}

@AzureWolf ping

I pushed support for configuring the color profile via our runtime arguments file. Steps to enable this:

use command palette to find runtime arguments command [1]
add "force-color-profile": "srgb" to the end of the file
restart

[1]

Hey super sorry. I'll check it out when I get a chance. For now I just removed HDR from my monitor settings so I have to set that up again when I'm not busy. It was a real pain to see a daily loss of brightness at the start of the day and it's been busy. I'll let you know.
Very sorry about that

Hey just tested this out and it does and doesn't work. So putting "disable-color-correct-rendering" to false fixes the issue. Setting it to true does not resolve the issue. Setting it to true and adding the color profile (as the screenshot you see here) does not fix the issue.

Thank you so much for this! I can finally go back to using HDR on my monitor! I don't know what it is, but it doesn't really make a big difference but all the colors are "softer" or less intense except where appropriate. It's hard to describe, but it makes it easier to work longer, so I'm super grateful. I'll be sure to thank you guys wherever possible.

@AzureWolf thanks for giving this a try. Since you see yellow squigglies in the editor I wonder if you maybe tried with VSCode stable and not insiders? Can you recheck this with our insiders build?
You can give our preview releases a try from: https://code.visualstudio.com/insiders/
You should not see a yellow warning like that which indicates that this property is not being applied.

This regression is still present in the 1.43 final release and 1.44 insiders. It looks like the upstream Chromeium bug mentioned by @deepak1556  has been fixed upstream just 16 days ago. @bpasero can you integrate that fix? I'm not even sure if it has made it's way into a stable release of Chromium or Electron yet though.

Can VSCode have a unit test around HDR to prevent these regressions? This isn't the first time this issue has been reported

@seanthegeek @SidShetye See the releases notes

I can confirm this issue reappearing today for me with 1.43, and that the workaround in the release note works. What I don't understand is why 1.43 was fine up to some hours ago, then stopped working properly as soon as I moved from Edge 44 to Edge 80. How is the installation of Edge even connected to VSCode in the first place… Oh, well…

@Varstahl It shouldn't be related to Edge at all. Maybe the Edge install turned on HDR in Windows? Or maybe you turned on HDR and forgot?

I always have HDR active having an HDR monitor, and the original problem followed #68069 (bright and washed out colors) and was fixed up to today. Then, today, after moving from legacy to recent Edge, the issue appeared in a different form: now it's like there's a black overlay plus some artifacts in the text editor. It's fixed as per the other issue with --force-color-profile srgb, just as with the disable-color-correct-rendering option.
I've tried re-installing the latest version of Code as well as trying the insider, but still the same issue, after updating to Edge 80 the issue started in Code (and in Code alone). Weird.

@varanshukla I had the same problem. The new workaround for VSCode 1.43 is different than the past ones you are talking about.

From the release notes section @michaelchiche linked to:

In the meantime, we have a temporary workaround for this issue:

1.Open the Command Palette (Ctrl+Shift+P).
2. Run the Preferences: Configure Runtime Arguments command.
3. This command will open a argv.json file to configure runtime arguments. There might be some default arguments there already.
4. Edit "disable-color-correct-rendering": true to "disable-color-correct-rendering": false.
5. Restart VS Code.

@seanthegeek assuming you were replying to me, yeah, I know. As I said both the runtime option and the force srgb command parameter fix that issue, I've already applied the change to argv.json myself. I was merely reporting the issue because I never saw screens like it and because it happened after installing Edge, which is something I still can't wrap my head around.

I'm on 1.43 with HDR enabled and FreeSync. Issue cropped up after update, but @bpasero's force-color-profile : srgb DID work for me and resolve the issue without changing disable-color-correct-rendering, which remains true.

Resurfaced after updating to 1.43.
To clarify what the workaround is, that works for me as well:
Open the "Preferences: Configure Runtime Arguments" action which opens the argv.json file and add the setting "force-color-profile": "srgb".
Disabling disable-color-correct-rendering did improve/change the rendering but did not really fix the contrast issue. With the above workaround this setting can be left at true.

@Kissaki "force-color-profile": "srgb" is the best fix, instead of disable-color-correct-rendering. it also fixed the screenshot problem I reported in issue #92365. Thank you!

Just to note that this is still an issue in 1.46.1

You can see the contrast difference (and the bizarre random white box) between the VS Code window and a normal Windows UI window it's sitting on top of ..

The issue should be fixed in latest insiders https://code.visualstudio.com/insiders/, please verify by removing any workarounds added via argv.json

@deepak1556 Verified fixed in Insiders. Thanks!

Still exists for me with the insiders version, as long as i have vs code windowed it works, but as soon as i go to fullscreen the screen dims.

We have reverted the runtime which contains the fix for this iteration. The fix will be available again from next week once we update to Electron 9 in master.

Hi this is still broken for me

Not sure if it can be seen but most of the screen is dim except for a couple of blocks where there is no text
For what it's worth, other electron apps that I use don't have these problems

I edited my runtime args disable-color-correct-rendering to false and now things work. Granted, I have no idea if it is "correct".
Both of my screens (internal laptop 4k OLED w/ HDR and external 4k LCD no HDR) support DCI P3. Would like to make sure my colors are correct.

The upstream fix will be available with upcoming stable release and is already available with current insiders, please check. Thanks!

Putting "force-color-profile": "srgb" in argv.json fixed it for me
(Samsung G9 HDR)

This has finally been fixed in 1.49.1 with Electron 9.2.1


Bug Examination for 1.0 Release

I am planning to release the stable version of EasyCrossPlatform 1.0
Examination shall be needed to examine the stability of this library. I will need people to help me with it.
I will start testing with raspberry pi(ARMv6), and Windows 10(x86, x64), Linux(Ubuntu 16.04LTS x64), MacOS(High Sierra x64).
Anyone can do the linux x86 test for me?

Just found a logical design problem in libuv wrapper class. I will fix it in a few days and open a new issue about it.

After fixed the logical error mentioned above(#3 )
I think this version is nearly stable.
Still need test.

Now, Several Segmentation Fault was found on Rpi 3B.
I think one of the problem is the charset of the code, another is that Linux does not initialize the value for the variable in the class, so it sucks.
I am working on it.

A lot of the problems are caused by Linux's C++ runtime.
It does not intialize the variables in classes's fields. I have worked on it and hopefully I can test it tomorrow.

Raspberry Pi 3B passed the TCP Server Test.
Oh yeah!


Add React and Hook config for ESLint

This PR adds eslint-plugin-react and eslint-plugin-react-hooks to the swr repository.
ESLint config extends plugin:react/recommended and add the react-hooks/rules-of-hooks rule as warning.
The use of useMemo after the early return in if (config.suspense) is a violation of the rules of hooks and even if I do not expect config.suspense to change during the normal use of the library, I moved it above that piece of code. I think it is a safer approach. We could add and an eslint-disable-next-line comment if you prefer.

@innocentiv could you rebase please to increase the chance of a merge?

I have rebased this feature, updated the eslint plugins to the latest version, changed the rules to the recommended config from react docs (now they fixed the autofix on react-hooks/exhaustive-deps). I hope this suffices, but after seven months I have nome doubt 😄


Conditions with timer.

I would to to suggest some conditions working with a timer, For example: the guy take damage and get shocked until the next turn, so at the start of their round the conditions reset. Another example: the guys need 2 turns to prepare a bow or reload ammo so you can set the numbers of rounds and it start a counter. There's a module called utility Belt that does it but does,t work for us.

We have every intention on doing this.    Foundry calls these "Active effects", and one of their main features is a "duration".
However, we are waiting to see how far SJG will let us go with this level of automation.
Since this has been discussed many times before, I am going to close this issue.  If SJG games allows us to provide this level of automation... we will implement it almost immediately ;-)


Number of return values in rmm_handler does not match with EL3(TF-A)

In RMM, rmm_handler returns X0-X5 to NS host. However, I notice in TF-A, rmmd_rmi_handler overwrites the X5 register which is the fourth output of a RMI request when the case is RMM_RMI_REQ_COMPLETE. I tested smc_rtt_read_entry and found that the value of RIPAS is always 0.
RMM smc_rtt_read_entry
x0  SMC_RMM_REQ_COMPLETE
x1  RMI_SUCCESS
x2  last_level
x3  HIPAS
x4  pa
x5  RIPAS

I modified smc_rtt_read_entry() to return 0xAA55 instead of RIPAS_EMPTY (0) and added logging of ret_val.ret0-ret4 in TFTF's  host_rmi_handler(). This the output I got:
RMM:
SMC_RMM_RTT_READ_ENTRY        88219000 0 0 > RMI_SUCCESS 0 2 8821c000 aa55
TFTF:

Executing 'Realm EL1 creation and execution test'
INFO:    Realm start adr=0x88119000
[VMID 0][Rec 0]: going to sleep for 20ms
INFO:    === 0x0
INFO:    === 0x0
INFO:    === 0x2
INFO:    === 0x8821c000
INFO:    === 0xaa55

rmmd_rmi_handler(..):
..
switch (smc_fid) {
case RMM_RMI_REQ_COMPLETE: {
uint64_t x5 = SMC_GET_GP(handle, CTX_GPREG_X5);
	return rmmd_smc_forward(REALM, NON_SECURE, x1,
				x2, x3, x4, x5, handle);
}

Oh, It is my mistake. It seems my local TF-A code misses this patch which looks like
 	switch (smc_fid) {
	case RMM_RMI_REQ_COMPLETE:
		return rmmd_smc_forward(REALM, NON_SECURE, x1,
					x2, x3, x4, 0, handle);

The RMI request can return the fourth argument correctly now.


jedilsp crashes on pydantic in insiders

I'm now getting crashes with a missing module for jedilsp/pydantic.
Not sure if this is the correct place to report this, but its somehow related to the changes that have been happening with the JediServer portion of the plugin that originated this ticket...
  File "/Users/username/.vscode/extensions/ms-python.python-2021.4.680137574-dev/pythonFiles/run-jedi-language-server.py", line 9, in <module>
    from jedi_language_server.cli import cli
  File "/Users/username/.vscode/extensions/ms-python.python-2021.4.680137574-dev/pythonFiles/lib/jedilsp/jedi_language_server/cli.py", line 5, in <module>
    from .server import SERVER
  File "/Users/username/.vscode/extensions/ms-python.python-2021.4.680137574-dev/pythonFiles/lib/jedilsp/jedi_language_server/server.py", line 15, in <module>
    from pygls.lsp.methods import (
  File "/Users/username/.vscode/extensions/ms-python.python-2021.4.680137574-dev/pythonFiles/lib/jedilsp/pygls/lsp/__init__.py", line 21, in <module>
    from pygls.lsp.types import *
  File "/Users/username/.vscode/extensions/ms-python.python-2021.4.680137574-dev/pythonFiles/lib/jedilsp/pygls/lsp/types/__init__.py", line 2, in <module>
    from pygls.lsp.types.basic_structures import *
  File "/Users/username/.vscode/extensions/ms-python.python-2021.4.680137574-dev/pythonFiles/lib/jedilsp/pygls/lsp/types/basic_structures.py", line 52, in <module>
    class JsonRpcMessage(Model):
  File "/Users/username/.vscode/extensions/ms-python.python-2021.4.680137574-dev/pythonFiles/lib/jedilsp/pydantic/main.py", line 298, in __new__
    config=config,
  File "/Users/username/.vscode/extensions/ms-python.python-2021.4.680137574-dev/pythonFiles/lib/jedilsp/pydantic/fields.py", line 419, in infer
    field_info=field_info,
  File "/Users/username/.vscode/extensions/ms-python.python-2021.4.680137574-dev/pythonFiles/lib/jedilsp/pydantic/fields.py", line 342, in __init__
    self.prepare()
  File "/Users/username/.vscode/extensions/ms-python.python-2021.4.680137574-dev/pythonFiles/lib/jedilsp/pydantic/fields.py", line 456, in prepare
    self.populate_validators()
  File "/Users/username/.vscode/extensions/ms-python.python-2021.4.680137574-dev/pythonFiles/lib/jedilsp/pydantic/fields.py", line 670, in populate_validators
    *(get_validators() if get_validators else list(find_validators(self.type_, self.model_config))),
  File "/Users/username/.vscode/extensions/ms-python.python-2021.4.680137574-dev/pythonFiles/lib/jedilsp/pydantic/validators.py", line 674, in find_validators
    if is_builtin_dataclass(type_):
  File "/Users/username/.vscode/extensions/ms-python.python-2021.4.680137574-dev/pythonFiles/lib/jedilsp/pydantic/dataclasses.py", line 79, in is_builtin_dataclass
    import dataclasses
ModuleNotFoundError: No module named 'dataclasses'

_Originally posted by @paulo-serrao in https://github.com/microsoft/vscode-python/issues/15586#issuecomment-813298969_

@rohel01 Can you file a separate bug? this seems unrelated. If you are using python version that has built in dataclasses then it should not reach this code. So we need to know the python version and build you are using to diagnose this further. This looks unrelated to the other types of crashes we have seen.
A simple mitigation would be to ensure that you have dataclasses installed in your environment. If you are using python 3.7 then dataclasses should be in available. Error above seems to indicate that it is a python version that supports dataclasses but is not available. Which means either the environment is somehow broken.

@rohel01 Can you file a separate bug? this seems unrelated. If you are using python version that has built in dataclasses then it should not reach this code. So we need to know the python version and build you are using to diagnose this further. This looks unrelated to the other types of crashes we have seen.
A simple mitigation would be to ensure that you have dataclasses installed in your environment. If you are using python 3.7 then dataclasses should be in available. Error above seems to indicate that it is a python version that supports dataclasses but is not available. Which means either the environment is somehow broken.

@karthiknadig Done, please see #16119 . As described in this ticket, I am using python 3.6.9


Suggestion: Add an effect to post a message into a specified channel to Automoderator v2

Hey,
looks like there is no way to kinda "log" Automoderator-Actions into channels in your discord. This makes it harder to follow up what exactly happened, when your Audit-Log is spammed and not all your moderators have access to read the bots logs.
Would it be possible to add an effect to send a Message X into Channel Y just like the ones for joins and leaves?
Best wishes

Already possible under Tools & Utility > Moderation


HN appears to have updated some code?

I'm seeing this:

Validated in latest Chrome and Thorium. Submitted #8 as possible fix.

fixed by #8


Fix cron trigger links

Many of the links were dead or using HTTP instead of HTTPS. This fixes both.

Jonathan, thanks a lot for contributing! I will now merge your pull request.


partners[milvus]: fix integration test issues

fix some integration test issues: https://github.com/langchain-ai/langchain/actions/runs/10688447230/job/29628412258

there are some issues introduced in history, i fixed them:

fix problem that can't get db_name from addr
fix mmr search test result
add milvus_model dependency into integration test of poetry requirement
update milvus-lite dependency to 2.4.10(x86 linux released), which is the latest one with the array bug fixed


chore(txpool): add IntoRecoveredTransaction to PoolTransaction

add missing trait bound to PoolTransaction.
we want this so we can easily convert from and to TransactionSignedEcRecovered

Codecov Report

Merging #1750 (1fbbe8e) into main (ee3a8af) will decrease coverage by 55.85%.
The diff coverage is 0.00%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@             Coverage Diff             @@
##             main    #1750       +/-   ##
===========================================
- Coverage   72.65%   16.80%   -55.85%
===========================================
  Files         392      392
  Lines       47168    47171        +3
===========================================
- Hits        34269     7928    -26341
- Misses      12899    39243    +26344

Flag
Coverage Δ

integration-tests
16.80% <0.00%> (-3.35%)
:arrow_down:

unit-tests
?

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

Impacted Files
Coverage Δ

crates/transaction-pool/src/traits.rs
0.00% <ø> (-2.98%)
:arrow_down:

crates/transaction-pool/src/validate.rs
0.00% <0.00%> (-19.34%)
:arrow_down:

... and 283 files with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.


Failed to execute question for question 9ffaf8f4-e720-46fe-acda-26d600466137

Hi, it's failed to execute question
Question title
react projects by most lines of code in typescript
Error message
Query execution timeout.
Generated SQL
SELECT
  `gr`.`repo_name` AS `repo_name`,
  SUM(`ge`.`additions`) AS `additions`,
  SUM(`ge`.`deletions`) AS `deletions`
FROM
  `github_events` AS `ge`
  INNER JOIN `github_repos` AS `gr` ON `ge`.`repo_id` = `gr`.`repo_id`
WHERE
  `gr`.`primary_language` = 'TypeScript'
  AND `gr`.`description` LIKE '%react%'
GROUP BY
  `gr`.`repo_name`
ORDER BY
  SUM(`ge`.`additions`) + SUM(`ge`.`deletions`) DESC
LIMIT
  20

Chart info
{
  "chartName": "BarChart",
  "title": "React Projects by Most Lines of Code in TypeScript",
  "x": "repo_name",
  "y": [
    "additions",
    "deletions"
  ]
}

Closed by tidb v6.6


Add support for "Translator" badge

Badges images can be found here? http://www.fevgames.net/new-translator-medal/

cc71ffc adds the badges to the swatch

Support for the badge has been added, so let's close this ticket.
We will add the images for the remaining tiers under #36


Improvement Improve decimal operation

Proposed changes
TPCH 100G Q1: 1.8s -> 1.7s
Problem summary
Describe your changes.
Checklist(Required)

[ ] Does it affect the original behavior
[ ] Has unit tests been added
[ ] Has document been added or modified
[ ] Does it need to update dependencies
[ ] Is this PR support rollback (If NO, please explain WHY)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

TeamCity pipeline, clickbench performance test result:
the sum of best hot time: 33.23 seconds
stream load tsv:          425 seconds loaded<PHONE_NUMBER>9 Bytes, about 167 MB/s
stream load json:         20 seconds loaded<PHONE_NUMBER> Bytes, about 112 MB/s
stream load orc:          72 seconds loaded<PHONE_NUMBER> Bytes, about 14 MB/s
stream load parquet:          31 seconds loaded 861443392 Bytes, about 26 MB/s
https://doris-community-test-1308700295.cos.ap-hongkong.myqcloud.com/tmp/20230407023857_clickbench_pr_125761.html


Update Key Vault Administration README with assignment recommendations

Please have a look at PR Azure/azure-sdk-for-net#20359 and make similar changes to your README to recommend and link to information about role assignments.

See also: Azure/azure-sdk-for-net#21212


Support for ES6 'goog:foo.bar.baz' imports

The latest versions of google closure support es6 modules, as well as closure-specific module syntax in the form of import foo from 'goog:foo.bar.baz'. This allows for files (for example, the google closure js library itself) to continue to goog.provide('foo.bar.baz') while having their code imported into es6 modules.
Would it be simple to make this work with the loader, and correctly resolve both new- and old-style imports/requires? I've had a first attempt at modifying the loader, adding an additional regex in the form of  ^import (.+) from ['"]goog:(.+)['"], but can't get things working yet: I intend to continue testing this out but thought I'd post here in the meantime in case there's any existing work on this or any roadblocks I'm overlooking.
Just to clarify, my intention would be only to transpile these special prefixed imports, and leave the pure es6 imports down to something like babel-loader since that feels more appropriate.

Hi @jdb8,
the main focus of this loader is to enable developers to keep using code files that make use of goog.provide and goog.require until they have can upgrade to a proper module system.
The syntax you describe is non-standard ES2015 and specific to the closure compiler. I do not aim to fully replace the closure loader. If you use the given syntax you are already inside a ES2015 file and thus could use any other import.
That being said: I would be willing to merge a PR if you also provide an example that shows the syntax being used and which updates the readme. Also please think about making this feature opt-in via the configuration.
I think your RegEx is a good start and you should handle it mostly like a goog.require with the same values, so I guess it shouldn't be too hard.

Hey @eXaminator,
Thanks for responding so quickly. I agree that the purpose of the closure-loader should stay as you've described. However, for anyone who is aiming to transition to a codebase consisting purely of ES2015 imports/exports, and is also tied down to the closure library (which doesn't provide native ES2015 exports), using the pseudo-ES2015 syntax described above is somewhat of a necessity as an interim step as far as I can see.
My understanding of webpack's loader system is not complete, but I was under the impression that it's totally possible and supported to run two loaders on the same set of files - for example, in my tests I added babel-loader with the ES2015 plugin enabled, which seemed able to deal with the non-goog ES2015 imports appropriately while delegating to closure-loader for anything else. It's possible that this is not the case though: I'll need to try out some more examples and make sure nothing conflicts (I feel like babel may possibly choke on anything non-standard which resembles an ES2015 import, but perhaps it's written better than that :)
Anyway, I'm glad you're open to receiving PRs on this! I'll play around and see if anything's possible without moving away from the core focus of this loader. Worst-case scenario, I can look into forking this for my purposes or moving some additional logic to a plugin which I'm writing anyway. Thanks for providing this in the first place!

You are right about loaders and any loader that would parse this syntax would need to be run before babel.
Loaders simply receive a string of code and transform it in some way. The transformed code will then be passed to the next loader in line.
Thus I would expect the easiest way for this to work be to replace matching import statements (probably with a regex like the one you described) with actual commonjs requires (they are a bit simpler for this case than just rewriting the actual ES6 import), just like the closure-loader already does for goog.require statements.
So it might actually be enough to check for your RegExp (in addition to the goog.require RegExp) and do the same processing (you will have to change the variable name that this will be assigned to though).
I would help more, but I don't have a lot spare time right now and as I myself don't have any use for this right now I would rather use my time for other stuff ;-)
But I'll gladly help you in trying to answer your questions regarding this.

Great. This sounds like the approach I started with, so I'm glad to know there shouldn't be any major blockers.
Thanks for your help, I'll let you know if there are any unforeseen blockers.


Exception while deserializing Color property with default value "Empty"

After updating from 9.0.1 to 10.0.3 objects with "Color" properties can't be deserialized anymore if the property has the following default value attribute: "[DefaultValue(typeof(Color), "Empty")]"
It crashes at System.Drawing.ColorConverter.ConvertFrom because the input value ist "Empty" (literally Empty as string)
I think the ColorConverter should be able to handle "Empty", but I don't know whats the chance and timeframe for fixing a .net bug is. So I hope there is something to fix or make a workaround in Newtonsoft.Json.
Source/destination types
//In my case:
Telerik.WinControls.UI.ConditionalFormattingObject

//But any class with a Color property with:
[DefaultValue(typeof(Color), "Empty")]

Source/destination JSON
{
   "ConditionType":1,
   "TValue1":"0",
   "TValue2":"",
   "CaseSensitive":false,
   "TextAlignment":16,
   "RowTextAlignment":16,
   "Enabled":true,
   "CellForeColor":"",
   "CellBackColor":"",
   "RowForeColor":"ControlDark",
   "RowBackColor":"",
   "CellFont":null,
   "RowFont":null,
   "Name":"Inaktiv",
   "ApplyToRow":true,
   "ApplyOnSelectedRows":true
}

Expected behavior
deserializing a Color property with "[DefaultValue(typeof(Color), "Empty")]" the "Empty" should be handled as "" so that the System.Drawing.ColorConverter.ConvertFrom will handle it correctly
Actual behavior
System.FormatException occurred
  HResult=-2146233033
  Message=Input string was not in a correct format
  Source=mscorlib
  StackTrace:
       bei System.Number.StringToNumber(String str, NumberStyles options, NumberBuffer& number, NumberFormatInfo info, Boolean parseDecimal)
  InnerException:

Steps to reproduce
.net 4.5.1

// Not tested
public class MyObject
{
    [DefaultValue(typeof(Color), "Empty")]
    public Color CellForeColor { get; set; }
}

MyObject test = new MyObject();
string json = JsonConvert.SerializeObject(test, Newtonsoft.Json.Formatting.None);
test = JsonConvert.DeserializeObject(json);

Environment -> .Net Framework : 4.5.1, Newtonsoft.Json : 10.0.3
This is not producing any error. Can you please elaborate more about your problem?
    public class MyObject
    {
        [DefaultValue(typeof(Color), "Empty")]
        public Color CellForeColor { get; set; }
    }

    class Program
    {
        static void Main(string[] args)
        {
            MyObject test1 = new MyObject();
            test1.CellForeColor = Color.Red;
            string json1 = JsonConvert.SerializeObject(test1, Formatting.None);
            test1 = JsonConvert.DeserializeObject<MyObject>(json1);
            Console.WriteLine(test1.CellForeColor);
            //Output : Color [Red]

            MyObject test2 = new MyObject();
            string json2 = JsonConvert.SerializeObject(test2, Formatting.None);
            test2 = JsonConvert.DeserializeObject<MyObject>(json2);
            Console.WriteLine(test2.CellForeColor);
            //Output : Color [Empty]
        }
    }

If you activate the "Common Language Runtime Exceptions" (CTRL+E CTRL+B) then you will see the Exception. It does not bubble up completely. I hope this helps.

It does not bubble up completely

So it's being caught internally in JSON.NET then and not propogated to the caller?  That's not necessarily a problem.  If I'm interpreting you correctly then it's similar to writing a TryParse function like
public bool TryParse(string s, out int i)
{
    try
    {
        i = Int32.Parse(s);
        return true;
    }
    catch
    {
        i = 0;
        return false;
    }
}

If you try to parse the string "abc" you'll get an exception internally in the method but the caller would remain blissfully unaware.  I can see the error in the debugger but not have it affect my program.
Is this what you're saying?  Sorry if I've misunderstood.

Yes, you are right.
Maybe I was to rash. I've the CRL Exceptions on all the time and my colleague made the 9.0.1 to 10.0.3 update and I just saw the Exceptions.  I've to re-update to 10.0.3 to see if this causes any real problem, so sorry for that.
But I would prefer it if the exceptions wouldn't occur, because every exception adds time to the de/serializing process.


SSH / SFTP automatic instrumentation capabilities

I have a use case where it would be very nice to perform SSH / SFTP automatic instrumentation. I'm using ssh2-sftp-client in order to establish a SFTP connection with a remote server and upload / download various files.
I would like to see those interactions with the server in my traces (e.g. start and end time of the operation, transferred file metadata).
In there any mechanism to do this? I couldn't find any instrumentation library for this matter.
If there is no solution at this point, is there any chance that an instrumentation library for this will be developed in the future?

You can do this in your application by starting a span just before calling the SFTP api and end it once done.
You can create a PR to ssh2-sftp-client library to call OTel API (or ask there for if someone has fun to do this).
Having the library itself call otel is preferred because any updates there would not break any independent created instrumenation library.
Likely creating a monkey patching instrumenation lib would be also possible but best would be to avoid the need for monkey patching by add monitoring support directly into the library itself.

@Flarna ,
Thanks for the answer. Could you please elaborate on the needed changes in the ssh2-sftp-client library? I can imagine that spans should be manually handled by the library using the opentelemetry API, right?
For example, a span could be started before a SSH connection is established and ended after that connection has been closed. Similarly, a span should be started before initiating the upload / download of a file and ended after the file transfer is complete.
Are there any code modifications needed besides manually creating spans and adding the right data to them?
Additionally, calling the OTel API inside the library itself implies the fact that the library will have OTel-related packages as dependencies. What happens if someone just wants to use the library without any OTel instrumentation?
If you could provide an example where the OTel API is called from inside the library itself would be very helpful.

Yes, calling the OTel API like startSpan()/endSpan()/... at the matching time would be the way to go. There should be only a dependency needed to the API, not to any SDK/Exporter/... component.
The API includes lightweight dummy stubs to keep overhead very low if there is no OTel SDK configured in the final application.
If the dependency to otel api is unwanted (which I fully understand as there are more trace tools around the world so why stick on OTel) an approach would be to add public apis to register some hooks, e.g. when a upload starts/ends/... This allows to write an independent instrumentation module adding OTel support which requires only public APIs of the module to monitor.
Most of the current instrumentations use monkey patching to re-write parts of the module internal on the fly. Which this approach has the advantage that no changes are needed in the module to monitor it tends to break every now and then because it relies on internals.
I don't know about any module which has OTel API calls built in unconditionally (which doesn't mean that it doesn't exist). support for hooks like above is e.g. in undici (never tried them so can't tell if they are sufficient for an Otel undici module).


Fix CLA link

Thanks for contributing to the cloud_controller_ng. To speed up the process of reviewing your pull request please provide us with:

A short explanation of the proposed change:
I fix CLA links on CONTRIBUTING.md because original link pages are not found.

An explanation of the use cases your change solves
Viewers can get to the right pages.

[x] I have viewed signed and have submitted the Contributor License Agreement
I belong to NTT Communications Corporation. Is it necessary to prove this?

[x] I have made this pull request to the master branch

[x] I have run all the unit tests using bundle exec rake

[x] I have run CF Acceptance Tests on bosh lite

I've publicized my membership in cloudn organization.

Hey @t-seyama,
Thanks for bringing to our attention the broken links. We were cautious to link against wordpress files, so we spoke with the foundation web team to get us more stable links for the CLA files. We are going to close this PR and update the 'CONTRIBUTING.md' file to have the correct links.
Thanks!
CAPI Community Pair - @aashah & @rizwanreza

Hi @aashah,
Noted.
Thanks for your correspondence.
@t-seyama


cmd/go: provide straightforward way to see non-test dependencies

It's important to be able to see the full set of dependencies used by production code exclusive of tests, particularly with different major versions as distinct modules, as inadvertently using an import with a different major version can introduce bugs (also, some external dependencies can be toxic to have in production code).
The go mod why command provides a -vendor flag to exclude tests; perhaps go list could provide a similar flag to exclude testing dependencies.
In addition to the above, it is also useful to be able to be able to see modules used by local production code and tests, but not transitively by tests in external dependencies, as external dependencies are harder to change, and inadvertently forked modules are still an issue for tests too. I'm not sure of a good way to specify that, though.

We should see if it's better to have this information directly in the go.mod file (like // test or separate sections of require). Or if it's better to use a cmd or a web site like godoc.org ?

@flibustenet - just in case you haven't seen https://github.com/golang/go/issues/26913#issuecomment-411976222 yet.
I think it's worth focussing on what people are trying to achieve here... which I agree has some overlap with their workflow and hence the tools they are using, but in the case of using godoc.org, I believe the underlying question that someone is trying to answer is "what dependencies does module M have?" and making some judgement on whether or not to use M using that information. Getting more detail on that will, I think, help to steer us towards the building blocks we then need in place.
As I noted on Slack:

Because all of these sorts of queries are possible using go list.... but the very fact we're having this discussion means that that solution is probably too esoteric. And if the queries are common enough it probably makes sense to provide something more accessible for day-to-day use

That said, we don't need to load everything into the go tool; if it provides the building blocks for some other solution that answers these same questions but via a different UI/UX then that's just as good.

As an example of the issue here, I just noticed a dependency on github.com/jtolds/gls which I wasn't expecting. The go mod why output looked like this:
# github.com/jtolds/gls
github.com/juju/charmstore-client/cmd/charm
github.com/juju/juju/juju/osenv
github.com/juju/juju/juju/osenv.test
github.com/juju/juju/testing
github.com/juju/juju/api/block
github.com/juju/juju/api/block.test
github.com/juju/juju/state
github.com/juju/juju/state.test
github.com/juju/juju/component/all
github.com/juju/juju/cmd/juju/commands
github.com/juju/juju/provider/all
github.com/juju/juju/provider/ec2
gopkg.in/ini.v1
gopkg.in/ini.v1.test
github.com/smartystreets/goconvey/convey
github.com/jtolds/gls

So the shortest path to this dependency takes us through four levels of external test dependencies. In practice I almost never care about test dependencies of external dependencies.

Hi,  I'm redirecting the comment here
Russ's comment about scopes is compelling to have unified go.mod, but not compelling to hide scopes (build tags x test).
I think having go mod why not refer to scopes can be confusing or worse: go mod why is arguably not providing the functionality advertised (i.e. explaining why) if it doesn't also give scope information, at least for the main module.

I would like to be able to look at go.mod and find out which packages are needed to build and run tests in the current module.  In particularly, this is needed if you have a policy that all open-source / "external" (outside of your company control) packages must be mirrored on internal servers.
One idea is for go to add comments like github.com/gopherjs/gopherjs v0.0.0-20181004151105-1babbf986f6f // indirect-test for indirect dependencies that are dependencies from tests in the dependencies' modules.  Then one could look at go.mod and see that packages/modules marked as // indirect-test are needed only if you want to run go test all or go test ... but not for the "regular" workflow of go install -v .... && go test -v ./... (to build and test your own code).

Tests dependencies should be visible, even for direct test dependencies. It's a valuable information. I'd like to choose a lib with as few dependency as possible to run but the most tests (and test dependencies if needed) as possible...

In particularly, this is needed if you have a policy that all open-source / "external" (outside of your company control) packages must be mirrored on internal servers.

That's probably a task better suited to GOPROXY than to go.mod. (In particular, I would expect the company to provide a GOPROXY server containing all of the approved/vetted versions of external modules.)

I would like to be able to look at go.mod and find out which packages are needed to build and run tests in the current module.

I think the go tool would be better.  But, in theory the problem of deciding whether or not a file has satisfiable build tags is NP-complete :)

perhaps go list could provide a similar flag to exclude testing dependencies.

I'm curious: does go list -f '{{with .Module}}{{.Path}} {{.Version}}{{end}}' ./... | sort -u produce the list that you want? (It's possible that the same flag can address both this use-case and #27900.)

I'm curious: does go list -deps -f '{{with .Module}}{{.Path}} {{.Version}}{{end}}' ./... | sort -u produce the list that you want? (It's possible that the same flag can address both this use-case and #27900.)

Per my answer in https://github.com/golang/go/issues/27900#issuecomment-437926158, I think it depends if you expect/want that answer to be irrespective of build constraints.

I'm curious: does go list -deps -f '{{with .Module}}{{.Path}} {{.Version}}{{end}}' ./... | sort -u produce the list that you want? (It's possible that the same flag can address both this use-case and #27900.)

Yes, this is pretty much exactly what I was after (I wasn't aware of the -deps flag). For the request in my final paragraph, go list -test -deps -f '{{with .Module}}{{.Path}} {{.Version}}{{end}}'| sort -u does the job. Not that either of these are particularly easy to type, but I can write a script. It would be nice if go mod why could work with this call graph instead of the regular one though.
PS I'd be happier if the go command never looked at external test dependencies (they can be enormous and it's often impossible or uneconomic to run all tests in all third party modules), but that's another story.

Story
I want to share my frustrating journey to this problem. I recently started a new project and from the get go I wanted dependency management to be done purposefully. Meaning that i want to be careful and conscious about how codes get into my binary.
I'm not building any thing exotic, a basic web app with a database. This is my go.mod file:
module github.com/my/project

go 1.12

require (
	github.com/advanderveer/go-test v1.0.1
	github.com/golang-migrate/migrate/v4 v4.2.4
	github.com/google/wire v0.2.1
	github.com/hashicorp/go-uuid v1.0.1
	github.com/lib/pq v1.0.0
)

As a general policy I wanted all my dependencies to be at version v1 or higher. So unfortunately wire stands out here. I though that wire was only for code generation purposes so I was confused as to why it was here. Ergo, i run go why github.com/google/wire and it gives me no new information as to "why" it is there even though i guarded it from building //+build wireinject flag. Googling around a bit I start to accept that the whole build flag thing is a bit confusing for determining what modules are important here. So i cut my losses and simply add a comment to the mod file for the future, I'm unsure if this comment stays intact why I'm adding more dependencies but I have bigger fish to fry:
Because during my research above I went on to to open my go.sum file. Even though I managed my dependencies carefully I somehow ended up with 200 lines of packages I don't directly seem to use. Some of them quite big:
...
cloud.google.com/go
github.com/aws/aws-sdk-go
github.com/cockroachdb/cockroach-go
github.com/gogo/protobuf
github.com/gopherjs/gopherjs
google.golang.org/grpc
...

So why are they there? go mod why github.com/gogo/protobuf says: # github.com/gogo/protobuf (main module does not need package github.com/gogo/protobuf). Eehm Ok. So why are they listed there? After some googling I run into this reddit thread which refers me to this issues  where it is said: "If you have dependencies only needed for tests, then they will show up in your go.mod, and go get will download their go.mods, but it will not download their code" Even though they are not in my go.mod I think believe this changed 1.12(?) as I used to have his behaviour. At this point I'm just thinking that these dependencies are listed in my go.sum for testing purposes. It is cool that I can test my code and all dependencies but it is impractical for me because when I do this go test all it fails to compile on some deep package github.com/jackc/pgx and starts testing cockroachdb itself (which is huge).
At this point I start googling and find all kinds of commands in issues such as go mod why all go mod why -vendor, go list or event go list -test -deps -f '{{with .Module}}{{.Path}} {{.Version}}{{end}}'| sort -u to figure how how these dependencies end up in my project. None of them seem to give a conclusive answer so I take a step back:
Want I want to know is which code ends up in the binary I ship. So I can also just look at the build and see which packages are included for that, so I run: go build -o /tmp/my-project -v. I was pretty sure that the -v command would show which packages are being build (help says: "print the names of packages as they are compiled." ) but instead I got empty output... Hmm maybe its using some cache? Sure enough, when I add the -a flag I finally get mostly the information i'm looking for.
Solution
If you're looking for the list of packages that:

Are not (indirect) test dependencies
Take into account build flags

Simply build your binary using go build -v -a and see which packages are listed there. It also lists standard library packages so it still convoluted with information that you might not be interested in but at least it gives answer to the question.
Ideas
It is not that i'm new to programming with Go, and have spent considerate amount teaching the language to (new) engineer. I'm a big fan of the design rational (having read all the blog posts, they are awesome!) but experiences like the one above leave a lot to be desired. I have the following ideas that could solve the (problematic) user story above.

have a comment in the go.sum file that indicate whether a dependency is indirect and/or just for testing. A I understand is the .sum file acts as the ultimate list of all external dependencies that are needed in one-way or the other and new comers always like to look a files first. Having the information there makes it more accessible
the go why should always have an answer for each module in .sum file. And specifically without any extra flags. A user user goes like this: "Hey there is a dependency here I didn't expect, why?" and expects to get some sort of answer with "go why "
Have a command that shows which external packages will be used for a build without the binary actually being build. I my usecase I just wanted to know what external was shipping with my application.
Maybe update the FAQ in the wiki with some of the information above?
Maybe have the -v flag of the build command show when packages are not being build because of the cache?

Hopefully this information is usefully and I know that there are probably complex underlying issues that I don't understand as i'm not very knowledgable about how it all works. But go modules is also a part of the tooling  new comers will interact with from the get go (phun intentded), so it makes sense to put some effort in the usability aspects.
Cheers,
Ad

Want I want to know is which code ends up in the binary I ship.

That's what the -deps flag to go list is for:
go list -deps -f '{{with .Module}}{{.Path}} {{.Version}}{{.end}}' ./my-project | sort -u

the go why should always have an answer for each module in .sum file

go.sum is not intended for human consumption. However, go mod graph should include the information you're looking for. (See also #27900.)

Thank you for your response. I think in general my feedback here is that, besides making sure that dependencies are there for a code base, the module system is also a means for engineers to understand a codebase. Especially in large projects, developers need to understand what parts are included when they open and start working on a project. The module system acts as a BoM (bill of materials) in that sense, it acts as the blueprint of a piece of software. In my experience (having tough this practice) the current tooling is ill suited for this activity. I understand that somewhere between:

go list [....]
go mod why [...]
go mod graph [...]
the go.mod file
the go.sum file

there is a way of answering these questions but as it is now this information and spread out and confusing.

Is there something that prevent to put something like // indirect-test in go.mod ?
It's not clear if it's not because we don't want this design or because of a technical difficulty ?

@flibustenet, not all dependencies of your module are listed in your module's go.mod file. It only includes requirements that satisfy direct imports from your module, or that are needed by a transitive dependency but not required in any dependency's go.mod file.
So a comment in the go.mod file would be actively misleading: it would convey the impression that all indirect dependencies are listed there, and in the long term the vast majority probably won't be.

Sometimes users of a lib will check go.mod files to see how heavy a given dependency for their project is. If the repository lists 5 binary dependencies and 95 test dependencies it is definitely less scary to use than a package that lists 100 dependencies (numbers exaggerated, but you get the point).
Separating the binary deps and test deps into 2 separate categories (build and test) inside the go.mod file would avoid this confusion.
require.build (
	dep/1
	dep/2
)

require.test (
	dep/3
	dep/4
)```

I would like to add that in downstream Linux packaging, we would like to have an easy way to split tests dependencies from non-tests dependencies. It is important for us to be able to disable tests and tests deps to solve cyclic dependencies (since we build iteratively, not everything together, it happens often).
(speaking as a Go-SIG member for Fedora).

To complete what @eclipseo wrote: if go.mod stated something was only needed for tests, it would be possible to configure the CI/CD toolchain to ignore it for builds that are not expected to run tests¹
If the info is not available in go.mod, and you need to re-parse the project tree to get it, why bother with the module system at all? You end up rewriting your own private module-like component handling logic.
And I write go.mod here, but I actually not care that much, if the info can be requested via golang/x/mod and not written in the go.mod file itself, that would work for us, though I suspect many would find it terribly inconvenient.
¹ The general case, since the Go definition of a test is lax enough, to allow dependencies on network calls, private servers, private accounts, root access, etc all things that can not be relied to exist outside the original test writer private env. Trying to run a set of Go tests, written by another org, is an exercise in frustration, just to sift real code failures from differences in environment.

@seebs, the general solution for that case is to load the dependency graph lazily, not to omit dependencies from it altogether.
We're looking at what it would take to facilitate lazy loading of the module graph for 1.15. Hopefully we'll have something to propose not too long after the 1.14 freeze.

Can we kindly get an update on this? This is still critical for downstream packaging. We can't upgrade our tooling to include Go modules if we can't spit the test dependencies from the build dependencies.

@eclipseo Does https://github.com/golang/go/issues/26955#issuecomment-437476523  work for you?

@eclipseo Does #26955 (comment) work for you?

As @nim-nim said:

If the info is not available in go.mod, and you need to re-parse the project tree to get it, why bother with the module system at all? You end up rewriting your own private module-like component handling logic.

So no, it's not a solution that we are currently planning. We would somehow rewrite a tool to map the output of go list to the output of go mod, to determine which modules is tests only.

So, to recap the issue,

we have a CI/CD system
for security reasons, it’s not allowed to trawl the internet, only internal stashes of vetted data
runs (including Go builds) are done in network-less ephemeral containers populated from this internal stash
we need to parse go.mod  files (either via custom code relying on golang.org/x/mod, or via parsing the output of a go mod foo  tool provided by the Go project) to identify the Go artefacts that need to be present in an ephemeral container for a Go build to succeed
as long as test dependencies are not clearly indicated as such in go.mod or some go mod foo command provided by the Go project, we are forced to populate containers with test dependencies too
test dependencies are sufficiently problematic that go get ignores them by default. We just want to replicate this mode when populating containers that build Go software

as long as test dependencies are not clearly indicated as such in go.mod or some go mod foo command provided by the Go project, we are forced to populate containers with test dependencies too

You can discover the package dependency structure using go list with either the -json or -f flags. (Also note that go list populates the module cache on demand as it walks the import graph, so you can also use go list itself to download dependencies — go mod download is a simplified command-line API for simple use-cases.)
So, no: you are not “forced” to populate containers with test dependencies; nor do you “need to parse go.mod files” in order for the build to succeed.

We fill an issue to make module usable in offline context.
You reply "you can just use pre-module commands that download things"
This is not constructive (to be polite)

@nim-nim, the design of modules integrates module operations into existing commands. It is not productive to ignore the possibility of using those commands, since they are part of the supported API for working with modules.

@bcmills then suggest things that do not download things and do not require re-parsing the module code.
The source code has already been parsed. That’s what produced go.mod. If we need to reparse it, because you don’t want to produce an inclusive module desing that addresses the needs or others rm -f go.mod and we’ll stop our work to convert to modules.
If your suggestion is to run commands that will download things for us when our use-case is offline then than is also completely useless.
We know about go list. What do you think we’ve been using all those years? If your suggestion is to continue using go list, except it will now do things that are incompatible with our workflow and download things if we make the mistake to enable modules, then we’ll force disable module everywhere forever (we’re already been doing it, except we didn’t want that to get permanent) . And ask all the projects w work with to drop modules and use go dep or any other system that works for our needs.

@nim-nim I support the general idea of this issue, and have been lurking the thread since it was created. Your latest comments haven't been constructive, and I think that's quickly derailing this thread and lowering the chances that it will get any further attention.
To give everyone the bigger picture here, there are lots of important issues with modules that need to be worked on. And there are just a few people working on them full-time, like @bcmills. Just look at the sheer amount of open issues. They aren't perfect people, but they are doing their best to resolve issues in a way that helps Go in the long run. So, please, be respectful.

@nim-nim, my suggestion is to either:
a. populate a Go module cache by whatever means you like (go mod download is one way, but there are others), and then set GOPROXY to point to that cache during offline use, or
b. use go list -json and/or go list -json -m to enumerate dependencies, and then set up a secondary module that uses replace directives to redirect those dependencies in the local filesystem.
Once you have tried either or both of those options, show us the concrete, actionable problems you encountered (problems, not prescriptive solutions!), and we can figure out how to address them in a way that is consistent with the rest of the design of the go command and Go modules.

@bcmills as we told you repeatedly for more than a year we already perform code analysis with golist and we already set up a cache using GOPATH and the result of the code analysis.  And we’ve done tens of thousands of production builds of hundreds of Go projects over the years using this code. It works and we understand why it works and what are its limitations.
However, we do not like maintaining tooling with behaviour that may differ or not from the behaviour of tooling other people had to write for the same reasons.
When Go modules were announced it looked like the Go project was serious about obviating the need of such custom tooling and provide upstream primitives that worked for everyone.
I personally invested months of work to identify the minimal requirements to switch our build system modules. And weeks more to report them.
You persist in dismissing this work. Your answer is basically “just continue to use custom go list logic, I’m not interested in your use case, report if it does not work” (except when we do report, you just ask us to go back to step 1).
FINE
GO111MODULES=OFF as far as I’m concerned.
Not going to invest more months of migration to modules just to get back to the custom go list logic stage.

@nim-nim once again, be cordial. It is fine to disagree, but being condescending or dramatic (e.g. dismissing modules entirely) is unnecessary. See https://golang.org/conduct.
If you really intend to not participate here anymore, that's your choice.

@nim-nim, the numerous issues that you filed are prescribing specific API changes. Specific API changes should go through the proposal process, and in general must meet a high bar — especially if they address use-cases that can already be handled using the existing API.
I am suggesting that you will likely have more success if you report use-cases instead of specific APIs, and make use of the existing APIs already designed for those use-cases when possible. (#35922 is a good example following that model for the use-case of distro packaging specifically. Note that that issue is an ongoing conversation, and we have not yet decided what — if any — additional API may be needed to address that use-case.)

At any rate, this discussion has clearly wandered far from the topic of viewing non-test dependencies. I'm going to hide some comments to get it back on track.

Hello @nim-nim and @eclipseo, one quick comment is that if you haven't already read this, it is probably worth reading https://github.com/golang/go/issues/29410#issuecomment-515203754 and some of the related discussion in #29410 around Go modules packaging approaches for Debian. Debian is distinct from Fedora, so that might not be useful, but maybe there is some overlap at least in terms of some of the challenges.  There is also a short comment there from @qbit (who I think works on packaging for OpenBSD) at https://github.com/golang/go/issues/29410#issuecomment-527678401. Again, perhaps not useful, but wanted to at least mention it.
I have followed some of the different issues you have submitted, but not all of them, so sorry if this is redundant or otherwise not helpful.

I am laymen.
I simply look for when ater I run go mod tidy, those package apparently used only within *_test.go file will not be external

hubris got the better of me and I created: https://github.com/komuw/ote which adds a // test comment next to test dependencies

It would be useful if there was a way to get an equivalent list with go list as you get from go version -m binary.  If you are planning to distribute the binary, it's valuable to know this list quickly perhaps without having to run a build.

Have any resolution?

Hi @so2bin, does https://github.com/golang/go/issues/26955#issuecomment-437476523 work for you?


src_dir to os.curdir for output, and poetry as alternative to conda.

Sorry for missing this PR for over 2 months!
I just checked the changed files and find that it’s minor changes for personal preferences. I’m afraid that this PR might not be accepted. (Sorry for the upsetting fact!)