text:
Boinc client unable to properly communicate with BOINC server (internal 500 error)

Mon 29 Aug 2016 13:20:19 BST | boincserver | project resumed by user
Mon 29 Aug 2016 13:20:24 BST | boincserver | update requested by user
Mon 29 Aug 2016 13:20:25 BST | boincserver | Sending scheduler request: Requested by user.
Mon 29 Aug 2016 13:20:25 BST | boincserver | Requesting new tasks for CPU
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] HTTP_OP::init_post(): http://192.168.56.101/boincserver_cgi/cgi
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Info:    Trying 192.168.56.101...
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Info:  Connected to 192.168.56.101 (192.168.56.101) port 80 (#1)
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Sent header to server: POST /boincserver_cgi/cgi HTTP/1.1
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Sent header to server: Host: 192.168.56.101
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Sent header to server: User-Agent: BOINC client (x86_64-pc-linux-gnu 7.6.31)
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Sent header to server: Accept: */*
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Sent header to server: Accept-Encoding: deflate, gzip
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Sent header to server: Content-Type: application/x-www-form-urlencoded
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Sent header to server: Accept-Language: en_GB
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Sent header to server: Content-Length: 5703
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Sent header to server: Expect: 100-continue
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Sent header to server:
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Received header from server: HTTP/1.1 100 Continue
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Info:  We are completely uploaded and fine
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Received header from server: HTTP/1.1 500 Internal Server Error
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Received header from server: Date: Mon, 29 Aug 2016 11:46:40 GMT
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Received header from server: Server: Apache/2.4.10 (Debian) PHP/5.6.17 OpenSSL/1.0.1k
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Received header from server: Content-Length: 539
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Received header from server: Connection: close
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Received header from server: Content-Type: text/html; charset=iso-8859-1
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Received header from server:
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Received header from server: <!DOCTYPE HTML PUBLIC "-//IETF//DTD HTML 2.0//EN">
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Received header from server:
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Received header from server: <title>500 Internal Server Error</title>
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Received header from server:
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Received header from server:
Internal Server Error

Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Received header from server:
The server encountered an internal error or
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Received header from server: misconfiguration and was unable to complete
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Received header from server: your request.

Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Received header from server:
Please contact the server administrator at
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Received header from server:  contact@project-rain.co.uk to inform them of the time this error occurred,
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Received header from server:  and the actions you performed just before this error.

Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Received header from server:
More information about this error may be available
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Received header from server: in the server error log.

Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Received header from server:
Mon 29 Aug 2016 13:20:25 BST | boincserver | [http] [ID#1] Info:  Closing connection 1
Mon 29 Aug 2016 13:20:26 BST | boincserver | Scheduler request failed: HTTP internal server error

Moving project rain fields from 'user' table into custom 'project rain' table! https://github.com/grctest/project-rain-site/commit/c421e84bc1b6df422a34b64e50873dd1aefbbf07

After having created a separate table for the project rain, I've got past this internal 500 error!

repo: grctest/project-rain-site


text:
(1) Update zeromq from 4.6.0 to 5.2.8. (2) simpleui-server needs pack…

…ages charenc from base_app.

Looks good to me.

source: gharchive/pull-request

repo: greg-ses/simpleui

license: MIT

license_type: permissive

license_source: github-api


text:
Publish docs

Generate API docs with Codox and literate docs with Marginalia.

Done!

source: gharchive/issue

repo: greglook/clj-multihash

license: unlicense

license_source: bigquery


text:
Optionally not fire onRowClick ?

When adding a button to a row in a given column, I'd like to be able to click that button without onRowClick firing (or find some other way of cancelling the actions of onRowClick).
Expected Behavior
I have a 6 column table of 'events'.  When someone clicks a row, I want the onRowClick function to run -- this function loads the event (or whatever)...  This works.
In column 2, I have a button on each row.  When this button is pressed, I want the event downloaded (or whatever) and NOT loaded.  Unfortunately, when I click the button, both the buttton's onClick method AND the onRowClick method fire.  This makes sense, but I'd like a way to cancel the onRowClick firing.
I have attempted to play with setting a state variable in the 'dowload' function (Which does, in fact, run before the onRowClick function)... unfortunately, due to the async nature of setState, the variable does not actually get set in state before onRowClick runs.
I should note the 'select row' checkboxes seem to cancel running onRowClick.

I understand your issue, and I've actually run across it myself while using this library on a project. I was able to get around it, but I don't remember exactly how. onCellClick actually fires before onRowClick and it contains information about the column that triggered the callback, so I think I was able to use that to set something on state which would then determine if I should run my onRowClick functions. See if that works for in the mean time.
As far as a way to optionally fire onRowClick for certain rows, I'm open to suggestions on ways to implement this. We perhaps add an optional array argument that instructs it on which rows should fire the callback, or something like that.

I solved the problem by just using onCellClick and checking that the column Index doesn't match the column with the secondary behavior.

Hi @jfederer / @gabrielliwerant How to setState onRowClick ?

I solved the problem by just using onCellClick and checking that the column Index doesn't match the column with the secondary behavior.

Hi @jfederer
Can you show a sample code of you did that?

Easy Solution:
onCellClick: (colData: any, cellMeta: { colIndex: number, rowIndex: number, dataIndex: number }) => {
if (cellMeta.colIndex !== 5 && cellMeta.colIndex !== 6) {
// perform action here....
}
}

Is there another way to get around this issue?
I am currently redirecting with onRowClick, and i want to insert a button into the table.
clicking on the button fires the onRowClick and redirects me...
I can not use onCellClick as my redirect based on an ID which I retrieve from the row data.
clicking on a 'date' cell for example will not provide me with the ID to properly redirect

The best way around this is to use only option i.e onCellClick and conditionally check the column index. The index key can be obtained from cellMeta  .  I have implemented  a delete button that opens a popup and when you click any other cell you navigate to a different path which in this case is the rest part of the row. Here is the sample code and some screen shots of the implementation
`const options = {
filterType: 'dropdown',
responsive: 'scrollMaxHeight',
filter: false,
sort: false,
download: false,
search: false,
rowsPerPage: 50,
selectableRows: false,
tableBodyMaxHeight: '100%',
rowsPerPageOptions: [10, 50, 100],
onCellClick: (colData, cellMeta) => onClickHandler(cellMeta),
};
const onClickHandler = (cellMeta) => {
	const rowdata = _Infos.data[cellMeta.rowIndex];
	console.log(rowdata);
	if (cellMeta.colIndex === 4) {
		setOpenPopup({
			open: true,
			id: rowdata.id,
			name: rowdata?.petName,
			picture: rowdata?.picture,
		});
	} else {
		history.push({
			pathname: '/management/view/edit-pet',
			PetId: rowdata.id,
		});
	}
};`

event.stopPropogation() should do the trick. https://stackoverflow.com/a/67565218/4993912

repo: gregnb/mui-datatables


text:
CustomFilterListRender not working when ServerSide = true

CustomFilterListRender does not work when ServerSide = true

Expected Behavior
After a filter has been applied, the chip should display with the filtered data.
Current Behavior
No chip pops up, with/without customFilterListRender specified.
Steps to Reproduce (for bugs)

apply any filter from the filter list
a chip with the filter value should pop up
Works using v2.11.1
Doesn't work using v2.12.0

Your Environment

Tech
Version

Material-UI

MUI-datatables
2.12.0

React
16.9.0

browser
chrome

etc

Seeing this same issue - is there an update on this?

Server side filters have been overhauled as they didn't quite work before. The way you specify your rendered filter chips now is with serverSideFilterList. Not having this work alongside customFilterListRender was an oversight. I don't have any timeline, but feel free to jump in with a fix.

I'm not so sure this is a bug, looking at the code, customFilterListRender does look like it gets applied. However, in the example above, there's no serverSideFilterList option provided. If serverSide is set to true, then the filter list is rendered using the serverSideFilterList. Also, in the example above, the filter dialog has no footer for submitting filters.
I've been thinking about this and I believe the library would be improved if this line https://github.com/gregnb/mui-datatables/blob/master/src/components/TableFilterList.js#L102 was changed to this:
    {(serverSide && serverSideFilterList)

That way the table would continue it's previous behavior if the user wasn't using the serverSideFilterList option.
I have a few more ideas regarding server-side filters, I may put in a PR for them.

I can confirm this bug still happens on v2.14.0

authors: akirwin danielbyun gabrielliwerant giorgiofellipe patorjk


text:
Add a Dir argument or setting for functions writing to Datastore

Currently, functions writing to Datastore (hdf5.R: initDataset, setInDatastore and inputsToDatastore) use the working directory. It'd be useful if users can change the behavior through an argument or setting, for example, configure a project directory for data that is separate from code (working directory).

We decided for data integrity purposes to only allow writing to one datastore in the working directory.  If you want your datastore to be in a different directory, you can specify it in the run parameters json file.

repo: gregorbj/VisionEval


text:
Remove empty continuation lines in Dockerfile

I got this warning when building the container:
[WARNING]: Empty continuation line found in:
    RUN apt-get update && apt-get install -y   libtinfo5   autoconf automake libtool make libgmp-dev ncurses-dev g++ python bzip2 ca-certificates   llvm   llvm-6.0   xz-utils   ghc-8.4.4   alex   cabal-install-2.4   happy   sudo xutils-dev   xsltproc docbook-xsl   python-sphinx   texinfo   python3   time   git php-cli php-curl libssl-dev vim-tiny   && apt-get clean
[WARNING]: Empty continuation lines will become errors in a future release.

This commit fixes that by just adding some more backslashes.

thanks!

authors: gregwebs mtzguido

repo: gregwebs/ghc-docker-dev

license: mit


text:
Use ES6 in hoxy, particularly generators.

PROS:
Reduces dependence on callbacks. Writing code in a synchronous/suspended style would make it easier to reason about and refactor.
CONS:
Limits hoxy use to newer node platforms, namely iojs or node 0.11 / --harmony.
Cons might be mitigated by use of transpilers. Also by hoxy being a dev-focused tool rather than a production one, thus not locked to mission-critical systems and more under control of devs.
If/when iojs becomes stable/popular and/or Joyent releases node 0.12 with native generator support the cons will be minimized in my view.

@greim It's awesome that this is done. I'm now trying to figure out how to use it. Am I correct in understanding that an ES6 module which imports hoxy 2.x (and sits in a package having hoxy installed as a typical package.json dependency) is to be run with babel-node?
I keep getting stuff like this...
/Users/sholladay/Code/experiment/es6-proxy/node_modules/hoxy/node_modules/babel/node_modules/babel-core/lib/babel/polyfill.js:16
  throw new Error("only one instance of babel/polyfill is allowed");
        ^
Error: only one instance of babel/polyfill is allowed
    at Object.<anonymous> (/Users/sholladay/Code/experiment/es6-proxy/node_modules/hoxy/node_modules/babel/node_modules/babel-core/lib/babel/polyfill.js:16:9)
    at Module._compile (module.js:460:26)
    at Module._extensions..js (module.js:478:10)
    at Object.require.extensions.(anonymous function) [as .js] (/usr/local/lib/node_modules/babel/node_modules/babel-core/lib/babel/api/register/node.js:215:7)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/Users/sholladay/Code/experiment/es6-proxy/node_modules/hoxy/node_modules/babel/node_modules/babel-core/lib/babel/api/register/node-polyfill.js:11:1)
    at Module._compile (module.js:460:26)

But using typical node doesn't work, either ...
/Users/sholladay/Code/experiment/es6-proxy/node_modules/hoxy/lib/proxy.js:6
import http from 'http'
^^^^^^
SyntaxError: Unexpected reserved word
    at exports.runInThisContext (vm.js:73:16)
    at Module._compile (module.js:443:25)
    at Module._extensions..js (module.js:478:10)
    at Object.require.extensions.(anonymous function) [as .js] (/Users/sholladay/Code/sitecues/sitecues-proxy/node_modules/hoxy/node_modules/babel/node_modules/babel-core/lib/babel/api/register/node.js:215:7)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (/Users/sholladay/Code/sitecues/sitecues-proxy/node_modules/hoxy/hoxy.js:9:13)
    at Module._compile (module.js:460:26)

There must be something basic I'm missing here.

Hoxy being written in es6 is supposed to be invisible to the outside world. AKA you should be able to npm install hoxy into es5 projects, var hoxy = require('hoxy') from es5 modules, and run it using node v0.10 or higher without --harmony flags.
Obviously something isn't playing well with your environment. You definitely shouldn't need babel-node for Hoxy, but perhaps your babel-node is a different version from the one Hoxy depends on? I suspect something like this needs to be added to Hoxy.

Right. Okay, we're on the same page. I only tried babel-node after reaching a dead-end with ES5 at:
import http from 'http'
^^^^^^
SyntaxError: Unexpected reserved word

(last comment has full trace)
My limited understanding of how Babel works tells me that we either need that runtime like you mentioned or that hoxy needs to be transpiled at prepublish time when pushing up to npm with a package script.

It will definitely be good to do some of these things that generally make the lib more self-contained, but if you could describe the minimum conditions to trigger this specific error, that would be helpful too. And maybe filed as a separate issue.

Just published 2.1.1 which uses a prepublish script. Let me know whether that works.

Unfortunately, it's not working for me:
λ node proxy.js
module.js:338
    throw err;
          ^
Error: Cannot find module './lib/proxy'
    at Function.Module._resolveFilename (module.js:336:15)
    at Function.Module._load (module.js:278:25)
    at Module.require (module.js:365:17)
    at require (module.js:384:17)
    at Object.<anonymous> (c:\xampp\htdocs\mms\node_modules\hoxy\index.js:6:13)
    at Module._compile (module.js:460:26)
    at Object.Module._extensions..js (module.js:478:10)
    at Module.load (module.js:355:32)
    at Function.Module._load (module.js:310:12)
    at Module.require (module.js:365:17)

In proxy.js is only one line :
var hoxy = require('hoxy');

I'm using node v0.12.0.

@majdamarcin - Are you pulling directly from this repo, instead of from npm? If so, you'll need to run npm run compile before anything will work. If not, could you describe your setup so that I can try to replicate the issue?

Hmm. There was an error in the .npmignore file which is fixed in v2.2.3. Let me know whether that fixes this issue.

@greim I just installed version v2.2.3 and everything looks fine, thanks :clap:

I'm sorry for disinformation, but I just tried to write simple script:
var hoxy = require('hoxy');
var proxy = new hoxy.Proxy();

proxy.intercept({
    phase: 'response',
    url: '/api/v1/sample/',
    methdod: 'POST',
    mimeType: 'application/json',
    as: 'json'
}, function(req, resp) {
    console.log(resp.userProfile.roles);
});
proxy.listen(8001);

and unfortunately it's not working. I get an error:
*truncated*\node_modules\hoxy\lib\proxy.js:263
      _co2['default'].call(_this2, regeneratorRuntime.mark(function callee$3$0
                                   ^
ReferenceError: regeneratorRuntime is not defined
    at Server.<anonymous> (*truncated*\node_modules\hoxy\lib\proxy.js:263:36)
    at Server.emit (events.js:98:17)
    at HTTPParser.parser.onIncoming (http.js:2113:12)
    at HTTPParser.parserOnHeadersComplete [as onHeadersComplete] (http.js:122:23)
    at Socket.socket.ondata (http.js:1971:22)
    at TCP.onread (net.js:528:27)

I installed hoxy via npm, my configuration:
λ node -v
v0.10.36

λ cat package.json
{
  "name": "app",
  "version": "0.1.0",
  "devDependencies": {
    "bluebird": "^2.9.34",
    "chromedriver": "~2.8.0",
    "grunt": "~0.4.2",
    "grunt-contrib-clean": "~0.4.1",
    "grunt-contrib-compass": "~0.2.0",
    "grunt-contrib-concat": "~0.1.3",
    "grunt-contrib-copy": "~0.5.0",
    "grunt-contrib-jshint": "~0.3.0",
    "grunt-contrib-uglify": "~0.2.0",
    "grunt-contrib-watch": "~0.5.3",
    "grunt-contrib-yuidoc": "~0.4.0",
    "grunt-css": "~0.5.4",
    "grunt-ddescribe-iit": "0.0.6",
    "grunt-html2js": "~0.2.4",
    "grunt-hub": "~0.6.0",
    "grunt-karma": "~0.8.3",
    "grunt-protractor-runner": "^2.0.0",
    "grunt-remove-logging": "~0.1.1",
    "grunt-replace": "~0.4.2",
    "grunt-sass": "~0.4.0",
    "grunt-selenium-simple": "~0.1.1",
    "hoxy": "^2.2.3",
    "install": "^0.1.8",
    "jasmine-core": "^2.2.0",
    "jasmine-spec-reporter": "^1.1.2",
    "karma": "~0.12.19",
    "karma-chrome-launcher": "~0.1.4",
    "karma-firefox-launcher": "~0.1.3",
    "karma-html-reporter": "^0.2.6",
    "karma-jasmine": "^0.3.5",
    "karma-phantomjs-launcher": "~0.1.4",
    "karma-safari-launcher": "~0.1",
    "karma-verbose-reporter": "0.0.1",
    "moment": "^2.10.3",
    "npm": "^2.6.1",
    "phantomjs": "~1.9.7",
    "protractor": "^2.1.0",
    "protractor-html-screenshot-reporter": "0.0.19",
    "selenium": "~2.20.0",
    "underscore": "^1.8.3"
  }

@majdamarcin I had the same issue while using browserify.
You need the babel polyfill as described in the docs and in this stack overflow question.
Adding require('babel/polyfill'); fixed it for me.

@nerdbeere  thank you very much!
npm install babel --save-dev

and
require('babel/polyfill');

resolved my issues.

Thanks for the workaround @nerdbeere. I believe this is a bug in Hoxy and I'll have a fix ready to go soon. This is the first time I've published an npm module using babel so thanks for bearing with me.

Fix published in 2.2.4.

authors: greim majdamarcin nerdbeere sholladay

repo: greim/hoxy


text:
[BUG] Error: Invalid count argument

Error: Invalid count argument
│
│   on .terraform/modules/vpc-peering/main.tf line 59, in resource "aws_route" "this_routes":
│   59:   count                     = var.from_this ? length(local.this_routes) : 0
│
│ The "count" value depends on resource attributes that cannot be determined
│ until apply, so Terraform cannot predict how many instances will be created.
│ To work around this, use the -target argument to first apply only the
│ resources that the count depends on.

Error: Invalid count argument
│
│   on .terraform/modules/vpc-peering/main.tf line 71, in resource "aws_route" "peer_routes":
│   71:   count                     = var.from_peer ? length(local.peer_routes) : 0
│
│ The "count" value depends on resource attributes that cannot be determined
│ until apply, so Terraform cannot predict how many instances will be created.
│ To work around this, use the -target argument to first apply only the
│ resources that the count depends on.

Hello @djkerya ,
This problem may appear when this module is dependant on some other module. For example, when you're using a module to create VPCs and then this module to peer them together in one Terraform run. The cause it that Terraform the data sources of this module cannot fetch required references, since those resources are not yet created. Notice, that the data sources are calculated as the first step of anu plan/apply operation.
Here is an example of how to use this module with the depends_on directive. Notice, that you have to explicitly provide references of the route tables in this case.
Hope, this helps!

Closing this issue due to no activity.

It is just hilarious to close the issue independently it is solved or not.
сб, 26 мар. 2022 г., 16:21 Yurii Rochniak @.***>:

Closed #83
https://github.com/grem11n/terraform-aws-vpc-peering/issues/83.
—
Reply to this email directly, view it on GitHub
https://github.com/grem11n/terraform-aws-vpc-peering/issues/83#event-6311875931,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ADDGNZZI2OY77AIY5CN4TGDVB4MOLANCNFSM5OCLD7MQ
.
You are receiving this because you were mentioned.Message ID:
@.***
com>


text:
一人称に表現を追加

knsh14チャン、お早う😘オイラ明日も仕事だけどなかなか寝れないよ〜(◎ ＿◎;)早くknsh14チャンに会いたい、よ💔ナンチャッテ😃☀ 天気悪いと気分もよくないよね(￣Д￣；；じゃあ今日は会社休んでオイラとデートしよう、😄ナンチャッテ😃

@knsh14 ちゃん、 オイラも、いいと、思うぞ 💪 😃💗😃

repo: greymd/ojichat


text:
Refactoring for send_byps/send_keep

Such the pattern is frequently observed on the code base.
https://github.com/greymd/teip/blob/master/src/procs.rs#L152-L165
        if is_in && !last_is_in {
            ch.send_keep(str_out.to_string())?;
            str_out.clear();
        } else if !is_in && last_is_in {
            ch.send_byps(str_in.to_string())?;
            str_in.clear();
        }
        last_is_in = is_in;
    }
    if last_is_in && !str_in.is_empty() {
        ch.send_byps(str_in)?;
    } else {
        ch.send_keep(str_out)?;
    }

This procedure can be unified to a single function.

I was working this issue on other branch but I noticed that this change degrades performance.
Prerequisites
Prepare a CSV file for benchmarking.
https://github.com/greymd/teip/wiki/CSV-Benchmark
Benchmark
teip 2.2.0
$ file $(which teip)
/usr/bin/teip: ELF 64-bit LSB shared object, x86-64, version 1 (SYSV), dynamically linked, BuildID[sha1]=e5ee576d461e79055f66d53ff6d55ff792606721, stripped

$ teip --version
teip 2.2.0

~/repos/greymd/teip [git:feature/extended_list@teip]
$ sudo sh -c 'echo 3 > /proc/sys/vm/drop_caches'; time teip -c 1-10,20- -f 2 -- tr '[:print:]' '@' < test.csv > /dev/null
teip -c 1-10,20- -f 2 -- tr '[:print:]' '@' < test.csv > /dev/null  4.38s user 0.42s system 159% cpu 3.000 total

~/repos/greymd/teip [git:feature/extended_list@teip]
$ sudo sh -c 'echo 3 > /proc/sys/vm/drop_caches'; time teip -c 1-10,20- -f 2 -- tr '[:print:]' '@' < test.csv > /dev/null
teip -c 1-10,20- -f 2 -- tr '[:print:]' '@' < test.csv > /dev/null  4.45s user 0.37s system 161% cpu 2.978 total

~/repos/greymd/teip [git:feature/extended_list@teip]
$ sudo sh -c 'echo 3 > /proc/sys/vm/drop_caches'; time teip -c 1-10,20- -f 2 -- tr '[:print:]' '@' < test.csv > /dev/null
teip -c 1-10,20- -f 2 -- tr '[:print:]' '@' < test.csv > /dev/null  4.44s user 0.35s system 161% cpu 2.966 total

Refactored teip 2.2.0
$ sudo sh -c 'echo 3 > /proc/sys/vm/drop_caches'; time ./target/release/teip -c 1-10,20- -f 2 -- tr '[:print:]' '@' < test.csv > /dev/null
./target/release/teip -c 1-10,20- -f 2 -- tr '[:print:]' '@' < test.csv >   5.23s user 0.31s system 117% cpu 4.732 total

~/repos/greymd/teip [git:feature/extended_list@teip]
$ sudo sh -c 'echo 3 > /proc/sys/vm/drop_caches'; time ./target/release/teip -c 1-10,20- -f 2 -- tr '[:print:]' '@' < test.csv > /dev/null
./target/release/teip -c 1-10,20- -f 2 -- tr '[:print:]' '@' < test.csv >   5.62s user 0.24s system 118% cpu 4.952 total

~/repos/greymd/teip [git:feature/extended_list@teip]
$ sudo sh -c 'echo 3 > /proc/sys/vm/drop_caches'; time ./target/release/teip -c 1-10,20- -f 2 -- tr '[:print:]' '@' < test.csv > /dev/null
./target/release/teip -c 1-10,20- -f 2 -- tr '[:print:]' '@' < test.csv >   5.18s user 0.28s system 117% cpu 4.627 total

How source code updated
Add following statements to proc.rs
/// Bypassing character range ( -c )
pub fn char_proc(
    ch: &mut PipeIntercepter,
    line: &Vec<u8>,
    ranges: &Vec<list::ranges::Range>,
) -> Result<(), errors::ChunkSendError> {
    let line = String::from_utf8_lossy(&line).to_string();
    let cs = line.chars();
    let mut ri = 0; // range index
    // Merge consequent characters' range to execute commands as few times as possible.
    for (i, c) in cs.enumerate() {
        // If the current position is out of the range, go to the next range.
        if ranges[ri].high < (i + 1) && (ri + 1) < ranges.len() {
            ri += 1;
        }
        if ranges[ri].low <= (i + 1) && (i + 1) <= ranges[ri].high {
            ch.buf_send_byps(c.to_string())?
        } else {
            ch.buf_send_keep(c.to_string())?
        }
    }
    ch.flush_byps()?;
    ch.flush_keep()?;
    Ok(())
}

Add following statements to chunk.rs
#[derive(Debug)]
pub enum ChunkGroup {
    Keep,   // a string under masking tape. Printed as is.
    Hole,   // A hole on the masking tape. The string in the hole being processed other thread.
}

Add following statements to pipeintercepter.rs
pub struct ChunkBuf {
    keep_buf: String,
    byps_buf: String,
    last_target: Option<ChunkGroup>,
}

impl ChunkBuf {
    fn new() -> ChunkBuf {
        ChunkBuf {
            keep_buf: String::with_capacity(DEFAULT_CAP),
            byps_buf: String::with_capacity(DEFAULT_CAP),
            last_target: None,
        }
    }
}

/// struct for bypassing input and its interface
pub struct PipeIntercepter {
    tx: Sender<Chunk>,
    pipe_writer: BufWriter<Box<dyn Write + Send + 'static>>, // Not used when -s
    handler: Option<JoinHandle<()>>,                         // "option dance"
    line_end: u8,
    solid: bool,
    dryrun: bool,
    chunk_buf: ChunkBuf,
}

Add following statements to pipeintercepter.rs under PipeIntercepter struct
    /// Used as send_keep() but it prevents sending chunk immediately.
    /// Keep the chunk in the buffer until the next Hole is found.
    /// Actually, send_keep() is not called directly but called by buf_send_byps().
    pub fn buf_send_keep(&mut self, msg: String) -> Result<(), errors::ChunkSendError> {
        // append msg to keep_buf
        self.chunk_buf.keep_buf.push_str(&msg);
        match self.chunk_buf.last_target {
            Some(ChunkGroup::Keep) => {
                return Ok(());
            }
            Some(ChunkGroup::Hole) => {
                match self.send_byps(self.chunk_buf.byps_buf.clone()) {
                    Ok(_) => {
                        // clear keep_buf
                        self.chunk_buf.byps_buf.clear();
                        self.chunk_buf.last_target = Some(ChunkGroup::Keep);
                        return Ok(());
                    }
                    Err(e) => return Err(e),
                }
            }
            // Initialize
            None => {
                self.chunk_buf.last_target = Some(ChunkGroup::Keep);
                return Ok(());
            }
        }
    }

    /// Used as send_byps() but it prevents sending chunk immediately.
    /// Keep the chunk in the buffer until the next Keep is found.
    /// Actually, send_byps() is not called directly but called by buf_send_keep().
    pub fn buf_send_byps(&mut self, msg: String) -> Result<(), errors::ChunkSendError> {
        // append msg to byps_buf
        self.chunk_buf.byps_buf.push_str(&msg);
        match self.chunk_buf.last_target {
            Some(ChunkGroup::Keep) => {
                match self.send_keep(self.chunk_buf.keep_buf.clone()) {
                    Ok(_) => {
                        // clear keep_buf
                        self.chunk_buf.keep_buf.clear();
                        self.chunk_buf.last_target = Some(ChunkGroup::Hole);
                        return Ok(());
                    }
                    Err(e) => return Err(e),
                }
            }
            Some(ChunkGroup::Hole) => {
                return Ok(());
            }
            // Initialize
            None => {
                self.chunk_buf.last_target = Some(ChunkGroup::Hole);
                return Ok(());
            }
        }
    }

    // send remaining chunks to be bypassed in the buffer
    pub fn flush_byps(&mut self) -> Result<(), errors::ChunkSendError> {
        if !self.chunk_buf.byps_buf.is_empty() {
            match self.send_byps(self.chunk_buf.byps_buf.clone()) {
                Ok(_) => {
                    // clear keep_buf
                    self.chunk_buf.byps_buf.clear();
                    self.chunk_buf.last_target = None;
                    return Ok(());
                }
                Err(e) => return Err(e),
            }
        }
        return Ok(());
    }

    pub fn flush_keep(&mut self) -> Result<(), errors::ChunkSendError> {
        if !self.chunk_buf.keep_buf.is_empty() {
            match self.send_keep(self.chunk_buf.keep_buf.clone()) {
                Ok(_) => {
                    // clear keep_buf
                    self.chunk_buf.keep_buf.clear();
                    self.chunk_buf.last_target = None;
                    return Ok(());
                }
                Err(e) => return Err(e),
            }
        }
        return Ok(());
    }

teip does not sacrifice performance for better maintainability. Therefore, we have decided not to address this Issue.

repo: greymd/teip


text:
Gridsome build ignores browser field of node module

Description
I'm using paper.js with gridsome. gridsome develop works fine, but gridsome build crashes with the following error:
Error: Can't resolve 'jsdom/lib/jsdom/living/generated/utils' in '/Users/arnoson/Development/gridsome-paper/node_modules/paper/dist/node'
    at doResolve (/Users/arnoson/Development/gridsome-paper/node_modules/enhanced-resolve/lib/Resolver.js:209:21)
    at hook.callAsync (/Users/arnoson/Development/gridsome-paper/node_modules/enhanced-resolve/lib/Resolver.js:285:5)
    at _fn0 (eval at create (/Users/arnoson/Development/gridsome-paper/node_modules/enhanced-resolve/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:15:1)
    at resolver.doResolve (/Users/arnoson/Development/gridsome-paper/node_modules/enhanced-resolve/lib/UnsafeCachePlugin.js:44:7)
    at hook.callAsync (/Users/arnoson/Development/gridsome-paper/node_modules/enhanced-resolve/lib/Resolver.js:285:5)
    at _fn0 (eval at create (/Users/arnoson/Development/gridsome-paper/node_modules/enhanced-resolve/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:15:1)
    at hook.callAsync (/Users/arnoson/Development/gridsome-paper/node_modules/enhanced-resolve/lib/Resolver.js:285:5)
    at _fn0 (eval at create (/Users/arnoson/Development/gridsome-paper/node_modules/enhanced-resolve/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:27:1)
    at resolver.doResolve (/Users/arnoson/Development/gridsome-paper/node_modules/enhanced-resolve/lib/DescriptionFilePlugin.js:67:43)
    at hook.callAsync (/Users/arnoson/Development/gridsome-paper/node_modules/enhanced-resolve/lib/Resolver.js:285:5)
    at _fn4 (eval at create (/Users/arnoson/Development/gridsome-paper/node_modules/enhanced-resolve/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:28:1)
    at resolver.doResolve (/Users/arnoson/Development/gridsome-paper/node_modules/enhanced-resolve/lib/ModuleKindPlugin.js:30:40)
    at hook.callAsync (/Users/arnoson/Development/gridsome-paper/node_modules/enhanced-resolve/lib/Resolver.js:285:5)
    at _fn0 (eval at create (/Users/arnoson/Development/gridsome-paper/node_modules/enhanced-resolve/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:15:1)
    at hook.callAsync (/Users/arnoson/Development/gridsome-paper/node_modules/enhanced-resolve/lib/Resolver.js:285:5)
    at _fn2 (eval at create (/Users/arnoson/Development/gridsome-paper/node_modules/enhanced-resolve/node_modules/tapable/lib/HookCodeFactory.js:33:10), <anonymous>:16:1)

Looking inside paper.js package.json there is browser field that disables the library that is causing the error, so it seems that gridsome ignores this field.
"browser": {
  "canvas": false,
  "jsdom": false,
  "jsdom/lib/jsdom/living/generated/utils": false,
  "source-map-support": false,
  "./dist/node/self.js": false,
  "./dist/node/extend.js": false
},

Steps to reproduce
Create a new gridsome project.
gridsome create gridsome-paper

Install paper.js
npm install paper

Import paper.js somewhere
import paper from 'paper'

Here is a demo project that renders a red circle with paper.js in the index.vue page.
Environment
  System:
    OS: macOS High Sierra 10.13.6
    CPU: (2) x64 Intel(R) Core(TM)2 Duo CPU     L9600  @ 2.13GHz
  Binaries:
    Node: 11.8.0 - ~/.nvm/versions/node/v11.8.0/bin/node
    Yarn: 1.12.3 - /usr/local/bin/yarn
    npm: 6.12.0 - ~/.nvm/versions/node/v11.8.0/bin/npm
  Browsers:
    Chrome: 78.0.3904.70
    Firefox: 70.0
    Safari: 13.0.2
  npmPackages:
    gridsome: ^0.7.0 => 0.7.9
  npmGlobalPackages:
    @gridsome/cli: 0.3.1

This issue can be solved by adding a webpack IgnorePlugin inside the gridsome.config.js file.
const webpack = require('webpack');

module.exports = {
  siteName: 'gridsome-paper',
  plugins: [],
  chainWebpack: config => {
    config.plugin().use(new webpack.IgnorePlugin(/jsdom/));
  },
};

authors: arnoson casderooij

repo: gridsome/gridsome


text:
AddDepthBuffer Breaks iOS

When AddDepthBuffer is used on iOS only a black screen is rendered thereafter. Apparently, the colorbuffer needs to be rebound after the depth_buffer calls.
I used this question to find the solution: https://stackoverflow.com/questions/9909473/opengl-es-2-0-buffer-setup
I rebound the color buffer afterwards and everything worked as expected. I tested this on iOS using OpenGLES 2.0 and 3.0 and OpenGL 3 on my Mac.
Below are the changes I made to AddDepthBuffer of renderer_GL_common.inl. I wasn't sure what the colorbuffer id was so I used glGetIntegerv. It was 1. Maybe it's always 1.
GLint param;
glGetIntegerv(GL_RENDERBUFFER_BINDING, &param);

glGenRenderbuffers(1, &depth_buffer);
glBindRenderbuffer(GL_RENDERBUFFER, depth_buffer);
glRenderbufferStorage(GL_RENDERBUFFER, GL_DEPTH_COMPONENT16, target->base_w, target->base_h);
glFramebufferRenderbuffer(GL_FRAMEBUFFER, GL_DEPTH_ATTACHMENT, GL_RENDERBUFFER, depth_buffer);

glBindRenderbuffer(GL_RENDERBUFFER, param);

That's weird.  I'm fine merging that in, though I'm not certain what the consequences of this behavior are generally.

please set an IOS check macro arround the new code , we don't want weird behaviours to appear in other platforms , i mean if the code it restrickted to IOS

authors: DiegoAce dhiahassen grimfang4


text:
Suggestion for improvements

I'm using Grist daily at the charity where I work and some little things have caught my attention:

The application does not open with window maximized by default. On Windows this is not a problem, but on the Linux version I couldn't find a solution.

The system keeps the order in which the columns were created, ignoring the order in which they were rearranged by the user. This causes the generated cards to be "messy", especially when the table has a lot of data.

When trying to attach a file, I couldn't find an indicator that accurately indicated the file size limit. The bar exists, but no indicator is shown. Maybe it's an electron compilation problem.

There are no labels to separate the tables, being necessary to create an "empty" table to group others in order to create a hierarchy.

The fact that aggregated tables always open expanded.

GRIST really is a fantastic piece of software, but among these suggestions, number 1, 2, 3 have a huge impact on day-to-day productivity

Thanks for the feedback and sorry for our delayed response.
Your 1st point can be addressed by persisting window size as suggested in #28, hence will be tracked there.
Your other points are not specific to Grist Desktop, and would require changes to Grist Core. Could you open corresponding issues under the grist-core repo instead?

Don't quite know where to add this information, but there's a new option for signing on Windows that I wasn't aware of https://news.ycombinator.com/item?id=40715250

authors: SleepyLeslie guilherme15990 paulfitz

repo: gristlabs/grist-desktop


text:
se_bugfixes

This change is

Codecov Report

Merging #33 into develop will decrease coverage by 0.39%.
The diff coverage is 100%.

@@            Coverage Diff             @@
##           develop      #33     +/-   ##
==========================================
- Coverage    96.17%   95.78%   -0.4%
==========================================
  Files           11       11
  Lines          471      474      +3
==========================================
+ Hits           453      454      +1
- Misses          18       20      +2

Impacted Files
Coverage Δ

grmpy/simulate/simulate.py
100% <100%> (ø)
:arrow_up:

grmpy/test/test_unit.py
100% <100%> (ø)
:arrow_up:

grmpy/test/random_init.py
99.02% <100%> (ø)
:arrow_up:

grmpy/__init__.py
41.66% <0%> (-2.78%)
:arrow_down:

Continue to review full report at Codecov.

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

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

grmpy/test/random_init.py, line 4 at r1 (raw file):

import uuid

import numpy as np

... order by length of import within blocks. Good idea to move to Wishart.

grmpy/test/random_init.py, line 78 at r1 (raw file):

    if not is_deterministic:
        x = np.identity(3)
        b = wishart.rvs(df=10, scale=x, size=1, random_state=seed)

Do we need to set the random_state explicitly?

grmpy/test/random_init.py, line 86 at r1 (raw file):

    dict_['DIST']['coeff'].append(b[0, 2])
    dict_['DIST']['coeff'].append(b[1, 1] ** 0.5)
    dict_['DIST']['coeff'].append(b[2, 1])

Please change to b[1, 2] so we stay within the logic of selecting from the upper triangular.

Comments from Reviewable

Reviewed 1 of 1 files at r2.
Review status: all files reviewed at latest revision, 3 unresolved discussions.

Comments from Reviewable

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

Comments from Reviewable

authors: SeBecker codecov-io peisenha

repo: grmToolbox/grmpy


text:
Generic Commands?

I am curious why Command does not make use of generics like Action does.  Wouldn't it be better to define Command like this?
public interface Command<STATE> {
  Observable<? extends Action<STATE> actions();
}

It sounds to me, but I don't remember why we didn't do it this way... We should definitely give it a try. Do you wanna do a PR @wongcain ?

Thanks @stephanenicolas. PR submitted.

Oops. My change broke the samples and now I see why it probably implemented this way... the generic prevents you from using the Observable.cast() function to support the success vs error Action emissions.  I've updated my PR to do the casting in the map() function instead.  I personally like this approach better, but I understand if prefer you prefer the non-generic Command version.  It's easy enough to make use of my own generic version of Command instead of the library.

 It's easy enough to make use of my own generic version of Command instead of the library.

@wongcain can you explain why would you use your versions of command instead of the ones in the library? We would be happy to make it better

Well I have been trying to make use of them in Kotlin and have been running into type-safety issues since store.dispatch is expecting a typed action and Command is emitting a generic one. I admit that my issue may be due to the limits of my understanding of generics and/or Kotlin,
Take this example from your project:
clicks(button)             .map(click -> new RefreshColorCommand())             .flatMap(RefreshColorCommand::actions)             .subscribe(store::dispatch, this::doLog)
The only way I've figured out how to implement that line in Kotlin is with an unchecked cast on the Action:
                clicks(button)                         .map { click -> RefreshColorCommand() }                         .flatMap<Action<*>>({ it.actions() })                         .subscribe(                                 { store.dispatch(it as Action<State>?) },                                 { this.doLog(it) })
But using my version of Command with generics, the cast is unnecessary:
                clicks(button)                         .map { click -> RefreshColorCommand() }                         .flatMap<Action<State>>({ it.actions() })                         .subscribe({ store.dispatch(it) }, { this.doLog(it) })
It also gives me piece of mind that there is a contract in place for each command to only emit Actions of a single state-type.

We've ended up doing the same because of our use of grox in Kotlin. Typing the Command and action observable it returns makes the Kotlin compiler happy and since we don't use the .cast() operator we don't have any issues from that. We can still do error actions using .onErrorResumeNext
interface Command<STATE> {
    fun actions(): Observable<out Action<STATE>>
}

and an example implementation:
return api.makeApiCall(argument)
            .map { result -> SuccessResultAction(result) }
            .onErrorResumeNext({ t: Throwable -> Observable.just(ErrorAction(t))})

@chenthorne https://github.com/groupon/grox/pull/40 what do you think? We are currently testing this approach in our app also.

Any update on merging PR #40 ?

@chenthorne Waiting for QA green light on this and our first release with the new update. We wanna make sure it works for us before releasing into the wild

I was about to avoid using Grox due to this issue being open, until I realized Grox 1.1.2 implements the changes mentioned here. Any reason why this is still open @alin-turcu? 🙂

@mradzinski thanks. I forgot about it. Closing it now

authors: alin-turcu chenthorne mradzinski stephanenicolas wongcain

repo: groupon/grox


text:
Device unsupported

After install and pairing(iTunes from my Mac) - iTunes device appears in Home app, but says that it not supported.

https://github.com/grover/homebridge-dacp/blob/master/docs/configuration/features.md

repo: grover/homebridge-dacp


text:
liveness and readiness throws protocol error.

Hello team,
I am having a strange problem. I have a Kubernetes deployment, a grpc service. I have included the grpc-health-probe bundled with my service binaries in the docker container. I have included the health proto inside service and then used HealthServiceImpl (in-built library from c#).
After I deploy to K8s, the pods never start. they fail the probes with the following error-

deploy yaml
`apiVersion: apps/v1
kind: Deployment
metadata:
name: grundfosgicwwncnetworkapi
labels:
app: grundfosgicwwncnetworkapi
name: grundfosgicwwncnetworkapi
spec:
replicas: 2
selector:
matchLabels:
app: grundfosgicwwncnetworkapi
template:
metadata:
labels:
app: grundfosgicwwncnetworkapi
environment: ENV
projectSpace: WWNC
spec:
containers:
- name: grundfosgicwwncnetworkapi
image: {{dockerRegistry}}/grundfosgicwwncnetworkapi:{{dockerVersion}}
imagePullPolicy: Always
ports:
- containerPort: 80
readinessProbe:
failureThreshold: 3
exec:
command: ["/bin/grpc_health_probe", "-addr=:80"]
periodSeconds: 5
initialDelaySeconds: 5
successThreshold: 1
timeoutSeconds: 30
livenessProbe:
failureThreshold: 3
exec:
command: ["/bin/grpc_health_probe", "-addr=:80"]
periodSeconds: 5
initialDelaySeconds: 5
successThreshold: 1
timeoutSeconds: 30
volumeMounts:
- name: configsettings
mountPath: /app/configmap
- name: secretsettings
mountPath: /app/secrets
readOnly: true
volumes:
- name: configsettings
configMap:
# Provide the name of the Secret containing the files you want
# to add to the container
name: grundfos.gic.wwnc.network.api
- name: secretsettings
secret:
# Provide the name of the Secret containing the files you want
# to add to the container
secretName: grundfos.gic.wwnc.network.msi.api
kind: Service
apiVersion: v1
metadata:
name: grundfosgicwwncnetworkapi-service
spec:
Expose the service on a static port on each node
so that we can access the service from outside the cluster
type: NodePort
When the node receives a request on the static port (30163)
"select pods with the label 'app' set to 'echo-hostname'"
and forward the request to one of them
selector:
app: grundfosgicwwncnetworkapi
ports:
# Three types of ports for a service
# nodePort - a static port assigned on each the node - reachable from outside
# port - port exposed internally in the cluster
# targetPort - the container port to send requests to
- port: 80
targetPort: 80`

`apiVersion: apps/v1
kind: Deployment
metadata:
name: grundfosgicwwncnetworkapi
labels:
app: grundfosgicwwncnetworkapi
name: grundfosgicwwncnetworkapi
spec:
replicas: 2
selector:
matchLabels:
app: grundfosgicwwncnetworkapi
template:
metadata:
labels:
app: grundfosgicwwncnetworkapi
environment: ENV
projectSpace: WWNC
spec:
containers:
- name: grundfosgicwwncnetworkapi
image: {{dockerRegistry}}/grundfosgicwwncnetworkapi:{{dockerVersion}}
imagePullPolicy: Always
ports:
- containerPort: 80
readinessProbe:
failureThreshold: 3
exec:
command: ["/bin/grpc_health_probe", "-addr=:80"]
periodSeconds: 5
initialDelaySeconds: 5
successThreshold: 1
timeoutSeconds: 30
livenessProbe:
failureThreshold: 3
exec:
command: ["/bin/grpc_health_probe", "-addr=:80"]
periodSeconds: 5
initialDelaySeconds: 5
successThreshold: 1
timeoutSeconds: 30
volumeMounts:
- name: configsettings
mountPath: /app/configmap
- name: secretsettings
mountPath: /app/secrets
readOnly: true
volumes:
- name: configsettings
configMap:
# Provide the name of the Secret containing the files you want
# to add to the container
name: grundfos.gic.wwnc.network.api
- name: secretsettings
secret:
# Provide the name of the Secret containing the files you want
# to add to the container
secretName: grundfos.gic.wwnc.network.msi.api
kind: Service
apiVersion: v1
metadata:
name: grundfosgicwwncnetworkapi-service
spec:
Expose the service on a static port on each node
so that we can access the service from outside the cluster
type: NodePort
When the node receives a request on the static port (30163)
"select pods with the label 'app' set to 'echo-hostname'"
and forward the request to one of them
selector:
app: grundfosgicwwncnetworkapi
ports:
# Three types of ports for a service
# nodePort - a static port assigned on each the node - reachable from outside
# port - port exposed internally in the cluster
# targetPort - the container port to send requests to
- port: 80
targetPort: 80`

I got the same issue, any advice for that??

Quick google search of the error shows me that this is a gRPC version compatibility issue between the client (this probe) and the server (your app) —although I'm not sure why something like this would happen.
What version do you have? Probe currently uses v1.24.0

I have an own error with my configuration, I've solved it.

I have an own error with my configuration, I've solved it. you can close this issue
@gasperlf  Do you mind sharing your solution? I'm running into same issue. Thanks!

@rui-wang-imprivata I did something like this.
FROM [java image]
LABEL mantainer=[project]
ARG user_name=[user]
ARG user_id=999
Create users
RUN useradd -u $user_id -c "$user_name System Account" -r -U -m $user_name
RUN GRPC_HEALTH_PROBE_VERSION=v0.3.2 &&
wget -qO/bin/grpc_health_probe https://github.com/grpc-ecosystem/grpc-health-probe/releases/download/${GRPC_HEALTH_PROBE_VERSION}/grpc_health_probe-linux-386 &&
chmod +x /bin/grpc_health_probe
COPY ./target/application-grpc.jar /app/application.jar
COPY ./distribution/docker/run.sh /app/bin/run.sh
RUN chown -R "${user_name}:${user_name}" "/app"
&& find /app -type d -exec chmod 750 {} ;
&& find /app -type f -exec chmod 640 {} ;
&& find /app -type f -name '*.sh' -exec chmod 750 {} ;
USER ${user_id:-nobody}
WORKDIR /app
EXPOSE 8080
ENTRYPOINT ["/app/bin/run.sh"]

@gasperlf  Thanks for your info! I just figured my issue is different from yours, turns out I just needed to install the latest version(v0.4.11) of grpc health prob (I was on an older version).

authors: SidGrundfos ahmetb gasperlf rui-wang-imprivata

repo: grpc-ecosystem/grpc-health-probe


text:
Send HTTP/2 SETTINGS_TIMEOUT.

It would be helpful to debug misbehaving clients, proxies & servers if gRPC closed connection with a  SETTINGS_TIMEOUT error if it didn't receive SETTINGS ACK frame in a reasonable amount of time (see: #13061).
This is especially important for the initial SETTINGS frame, where misbehaving clients might completely ignore SETTINGS frame which arrived upon successful connection, but before client sent its own SETTINGS frame.
From RFC7540, sec. 6.5.3. Settings Synchronization:

If the sender of a SETTINGS frame does not receive an acknowledgement
within a reasonable amount of time, it MAY issue a connection error
(Section 5.4.1) of type SETTINGS_TIMEOUT.

cc @ctiller @fengli79 @louiscryan

Effectively we'll need a timer in chttp2_transport that's armed whenever we send settings, cancelled when we get the ack, and fails the connection when it expires.
Care will need to be given to ensure that we don't start sending the next settings until the timer callback is actually made.

authors: PiotrSikora ctiller

repo: grpc/grpc


text:
Python: Add unit tests to examples/python/helloworld

We already have documentation for our unit testing framework published here: https://grpc.io/grpc/python/grpc_testing.html
But it would be helpful for users to have a stand-alone example of unit tests for greeter_client and greeter_server when getting started with gRPC Python, as the only other usages of the testing APIs are in our own internal tests, which can be hard for new users to parse through

I have doubts about the usability of grpcio-testing package. It requires to retrieve ProtoBuf descriptors about the servicer, but it seems not supported yet. There are two related issues:
https://github.com/grpc/grpc/blob/618a3f561d4a93f263cca23abad086ed8f4d5e86/src/python/grpcio_tests/tests/testing/_application_testing_common.py#L20
https://github.com/grpc/grpc/blob/618a3f561d4a93f263cca23abad086ed8f4d5e86/src/python/grpcio_tests/tests/testing/_application_testing_common.py#L21
#11657 got closed and moved to https://github.com/grpc/grpc/issues/3898 which got closed and never solved.
The implementation of grpcio-testing is correct and the unit test passed steadily. However, it is using hard-coded method descriptors... Before further investigation, I won't be confident to recommend this package to gRPC Python users.

Absolutely!

That would be awesome!

That would be indeed awesome. It feels a little odd that the code is so well documented but usage is quite under-documented.
Maybe @nathanielmanistaatgoogle could chime in? I was browsing around and saw a few PRs and SO comments but none led to me a full/complete example of using the testing framework unfortunately :(

I've figured out how to use the grpc_testing server test suite and created a minimal running example for Greeter helloworld service. Available here.
I'm not sure where exactly it should go in the grcp/grcp repo structure, so not sure how to create a pull request for this.
Also I'm not sure that I'm not doing anything stupid in the example I've created, so would want some sanity check from @nathanielmanistaatgoogle, @ericgribkoff or anyone else in the know of how the grpc_testing actually should be used.

@alexykot These tests look great. We'd be more than happy to take a PR.
We've actually started adding tests to each example as it's added. Check out the multiprocessing and wait_for_ready directories. All that should differ is the infrastructure surrounding the test. We're trying to converge around bazel.

@alexykot Are you still hoping to contribute unit tests to the helloworld example?

Sorry, this is unlikely now as we've switched over to Go entirely in our stack and phased out Python services, so I'm not using Python gRPC anymore.

@gnossen I don't mind contributing @alexykot 's example back to gRPC, if I have his permissions. I recently stumbled upon it his example and it was great to follow!

Oh, I didn't realize this is still not solved and my solution is actually workable.
I'll move the examples from my archive to gRPC asap.

Created PR #27481  to relocate my examples into the upstream.

+1

How can I configure interceptors on the test server?

I'm struggling with this too. From the grpcio-testing documentation, I figured there isn't a way to inject interceptors to the server. Any possible workaround for this available?
IMO, this is very useful feature to include.

authors: Lawouach alexykot ericgribkoff ericxiao251 gnossen kavithamadhavaraj lidizheng lucascharlesz shahidash


text:
Objc build failure: error: variable 'token_lifetime' may be uninitialized when used here

=== BUILD TARGET nanopb-macOS OF PROJECT Pods WITH CONFIGURATION Test ===
Check dependencies
Write auxiliary files
write-file /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Intermediates.noindex/Pods.build/Test/nanopb-macOS.build/nanopb-macOS-all-non-framework-target-headers.hmap
write-file /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Intermediates.noindex/Pods.build/Test/nanopb-macOS.build/nanopb-macOS-project-headers.hmap
write-file /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Intermediates.noindex/Pods.build/Test/nanopb-macOS.build/nanopb-macOS-own-target-headers.hmap
write-file /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Intermediates.noindex/Pods.build/Test/nanopb-macOS.build/nanopb-macOS.hmap
write-file /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Intermediates.noindex/Pods.build/Test/nanopb-macOS.build/nanopb-macOS-generated-files.hmap
/bin/mkdir -p /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Intermediates.noindex/Pods.build/Test/nanopb-macOS.build/Objects-normal/x86_64
write-file /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Intermediates.noindex/Pods.build/Test/nanopb-macOS.build/Objects-normal/x86_64/nanopb-macOS.LinkFileList
write-file /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Intermediates.noindex/Pods.build/Test/nanopb-macOS.build/nanopb-macOS-all-target-headers.hmap
=== BUILD TARGET gRPC-macOS-gRPCCertificates OF PROJECT Pods WITH CONFIGURATION Test ===
Check dependencies
Create product structure
/bin/mkdir -p /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-macOS/gRPCCertificates.bundle/Contents
/bin/mkdir -p /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-macOS/gRPCCertificates.bundle/Contents/Resources
ProcessInfoPlistFile /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-macOS/gRPCCertificates.bundle/Contents/Info.plist Target\ Support\ Files/gRPC-macOS/ResourceBundle-gRPCCertificates-Info.plist
    builtin-infoPlistUtility /Volumes/BuildData/tmpfs/src/github/grpc/workspace_objc_macos_opt_native/src/objective-c/tests/Pods/Target\ Support\ Files/gRPC-macOS/ResourceBundle-gRPCCertificates-Info.plist -expandbuildsettings -platform macosx -o /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-macOS/gRPCCertificates.bundle/Contents/Info.plist
CpResource /Volumes/BuildData/tmpfs/src/github/grpc/workspace_objc_macos_opt_native/etc/roots.pem /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-macOS/gRPCCertificates.bundle/Contents/Resources/roots.pem
Touch /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-macOS/gRPCCertificates.bundle
    /usr/bin/touch -c /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-macOS/gRPCCertificates.bundle
CodeSign /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-macOS/gRPCCertificates.bundle
Signing Identity:     "-"
    /usr/bin/codesign --force --sign - --timestamp=none /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-macOS/gRPCCertificates.bundle
=== BUILD TARGET gRPC-Core-macOS OF PROJECT Pods WITH CONFIGURATION Test ===
Check dependencies
Warning: Multiple build commands for output file /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-Core-macOS/alloc.h
Warning: Multiple build commands for output file /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-Core-macOS/arena.h
Warning: Multiple build commands for output file /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-Core-macOS/atm.h
Warning: Multiple build commands for output file /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-Core-macOS/atm_gcc_atomic.h
Warning: Multiple build commands for output file /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-Core-macOS/atm_gcc_sync.h
Warning: Multiple build commands for output file /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-Core-macOS/atm_windows.h
Warning: Multiple build commands for output file /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-Core-macOS/byte_buffer.h
Warning: Multiple build commands for output file /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-Core-macOS/byte_buffer_reader.h
Warning: Multiple build commands for output file /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-Core-macOS/connectivity_state.h
Warning: Multiple build commands for output file /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-Core-macOS/fork.h
Warning: Multiple build commands for output file /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-Core-macOS/fork.h
Warning: Multiple build commands for output file /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-Core-macOS/log.h
Warning: Multiple build commands for output file /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-Core-macOS/port_platform.h
Warning: Multiple build commands for output file /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-Core-macOS/slice.h
Warning: Multiple build commands for output file /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-Core-macOS/status.h
Warning: Multiple build commands for output file /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-Core-macOS/sync.h
Warning: Multiple build commands for output file /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-Core-macOS/sync.h
Warning: Multiple build commands for output file /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-Core-macOS/sync_custom.h
Warning: Multiple build commands for output file /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-Core-macOS/sync_generic.h
Warning: Multiple build commands for output file /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-Core-macOS/sync_posix.h
Warning: Multiple build commands for output file /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Products/Test/gRPC-Core-macOS/sync_windows.h
Write auxiliary files
/bin/mkdir -p /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Intermediates.noindex/Pods.build/Test/gRPC-Core-macOS.build/Objects-normal/x86_64
write-file /Users/kbuilder/Library/Developer/Xcode/DerivedData/Tests-fbrsdwcwvahgdwfbkkumiqqzuyix/Build/Intermediates.noindex/Pods.build/Test/gRPC-Core-macOS.build/Objects-normal/x86_64/gRPC-Core-macOS.LinkFileList
/Volumes/BuildData/tmpfs/src/github/grpc/workspace_objc_macos_opt_native/src/core/lib/security/credentials/oauth2/oauth2_credentials.cc:243:47: error: variable 'token_lifetime' may be uninitialized when used here [-Werror,-Wconditional-uninitialized]
                         gpr_time_from_millis(token_lifetime, GPR_TIMESPAN))
                                              ^~~~~~~~~~~~~~
/Volumes/BuildData/tmpfs/src/github/grpc/workspace_objc_macos_opt_native/src/core/lib/security/credentials/oauth2/oauth2_credentials.cc:230:29: note: initialize the variable 'token_lifetime' to silence this warning
  grpc_millis token_lifetime;
                            ^
                             = 0
1 error generated.
kill -9 `jobs -p` ; echo "EXIT TIME:  $(date)"
jobs -p
date
EXIT TIME:  Thu Jun 27 15:37:59 PDT 2019

https://source.cloud.google.com/results/invocations/8b752d4e-fa33-43fc-95cb-2b4349727a07/targets/github%2Fgrpc%2Fobjc_macos_opt_native/tests

Already fixed by #19492

authors: apolcyn muxi


text:
Grpc.Tools: using ProtoRoot property messes up Visual Studio

What version of gRPC and what language are you using?
GRPC.Tools 2.24
using Build Integration specified at https://github.com/grpc/grpc/blob/master/src/csharp/BUILD-INTEGRATION.md and #13207
What operating system (Linux, Windows,...) and version?
Windows 10 Pro 18362.356
What runtime / compiler are you using (e.g. python version or version of gcc)
GRPC.Tools integrated compiler
What did you do?
I have created a repo that demonstrates the issue https://github.com/sudsy/GRPC.Tools.Issue
If you open the solution in Visual Studio 2019 you will see that the project ConsoleApp1 imports a proto file from the Messages project. To make this work, ProtoRoot=".." was added to ConsoleApp1.csproj
Adding ProtoRoot=".." requires the include path to be specified relative to the ProtoRoot however visual studio then shows a folder marked with a cross within the Consoleapp1 project
What did you expect to see?
I did not expect to see the phantom folder within ConsoleApp1
What did you see instead?
I saw the phantom folder with a cross

@kkm000  any ideas?

@sudsy  I cloned the repo you provided and I'm also seeing the "ConsoleApp1" phantom folder with a cross. Nevertheless

building the solution still works just fine
the "phantom folder" can easily be removed by setting Link attribute on your Protobuf item: <Protobuf Include="ConsoleApp1/Protos.proto" Link="Protos.proto" ProtoRoot=".." />

The structure of the projects and protos in your example is actually quite odd so I'm not really all that surprised that VS has trouble handling that layout, but since setting the Link attribute fixes this (rather cosmetic) problem, I'm going to close as "working as intended".

authors: jtattermusch sudsy


text:
Python Install

What version of gRPC and what language are you using?
grpcio 1.11.0
What operating system (Linux, Windows,...) and version?
Windows 10
What runtime / compiler are you using (e.g. python version or version of gcc)
python 3.9.1
What did you do?
ran "pip install grpcio==1.11.0" from powershell comand line ( tried as admin and regular same result)
What did you expect to see?
Expected a successful installation of grpcio
What did you see instead?
Go the following long error message:
Collecting grpcio==1.11.0
Using cached grpcio-1.11.0.tar.gz (14.2 MB)
Requirement already satisfied: six>=1.5.2 in c:\users\shree\appdata\local\packages\pythonsoftwarefoundation.python.3.9_qbz5n2kfra8p0\localcache\local-packages\python39\site-packages (from grpcio==1.11.0) (1.11.0)
Requirement already satisfied: protobuf>=3.5.0.post1 in c:\users\shree\appdata\local\packages\pythonsoftwarefoundation.python.3.9_qbz5n2kfra8p0\localcache\local-packages\python39\site-packages (from grpcio==1.11.0) (3.15.0)
Building wheels for collected packages: grpcio
Building wheel for grpcio (setup.py) ... error
ERROR: Command errored out with exit status 1:
command: 'C:\Users\shree\AppData\Local\Microsoft\WindowsApps\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\python.exe' -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\Users\shree\AppData\Local\Temp\pip-install-gba23662\grpcio_bfd768fa280047b498d6335e41535718\setup.py'"'"'; file='"'"'C:\Users\shree\AppData\Local\Temp\pip-install-gba23662\grpcio_bfd768fa280047b498d6335e41535718\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' bdist_wheel -d 'C:\Users\shree\AppData\Local\Temp\pip-wheel-cvz0engc'
cwd: C:\Users\shree\AppData\Local\Temp\pip-install-gba23662\grpcio_bfd768fa280047b498d6335e41535718
Complete output (141 lines):
Found cython-generated files...
running bdist_wheel
running build
running build_py
running build_project_metadata
creating python_build
creating python_build\lib.win-amd64-3.9
creating python_build\lib.win-amd64-3.9\grpc
copying src\python\grpcio\grpc_auth.py -> python_build\lib.win-amd64-3.9\grpc
copying src\python\grpcio\grpc_channel.py -> python_build\lib.win-amd64-3.9\grpc
copying src\python\grpcio\grpc_common.py -> python_build\lib.win-amd64-3.9\grpc
copying src\python\grpcio\grpc_grpcio_metadata.py -> python_build\lib.win-amd64-3.9\grpc
copying src\python\grpcio\grpc_interceptor.py -> python_build\lib.win-amd64-3.9\grpc
copying src\python\grpcio\grpc_plugin_wrapping.py -> python_build\lib.win-amd64-3.9\grpc
copying src\python\grpcio\grpc_server.py -> python_build\lib.win-amd64-3.9\grpc
copying src\python\grpcio\grpc_utilities.py -> python_build\lib.win-amd64-3.9\grpc
copying src\python\grpcio\grpc_init_.py -> python_build\lib.win-amd64-3.9\grpc
creating python_build\lib.win-amd64-3.9\grpc\beta
copying src\python\grpcio\grpc\beta\implementations.py -> python_build\lib.win-amd64-3.9\grpc\beta
copying src\python\grpcio\grpc\beta\interfaces.py -> python_build\lib.win-amd64-3.9\grpc\beta
copying src\python\grpcio\grpc\beta\utilities.py -> python_build\lib.win-amd64-3.9\grpc\beta
copying src\python\grpcio\grpc\beta_client_adaptations.py -> python_build\lib.win-amd64-3.9\grpc\beta
copying src\python\grpcio\grpc\beta_metadata.py -> python_build\lib.win-amd64-3.9\grpc\beta
copying src\python\grpcio\grpc\beta_server_adaptations.py -> python_build\lib.win-amd64-3.9\grpc\beta
copying src\python\grpcio\grpc\beta_init_.py -> python_build\lib.win-amd64-3.9\grpc\beta
creating python_build\lib.win-amd64-3.9\grpc\experimental
copying src\python\grpcio\grpc\experimental\gevent.py -> python_build\lib.win-amd64-3.9\grpc\experimental
copying src\python\grpcio\grpc\experimental_init_.py -> python_build\lib.win-amd64-3.9\grpc\experimental
creating python_build\lib.win-amd64-3.9\grpc\framework
copying src\python\grpcio\grpc\framework_init_.py -> python_build\lib.win-amd64-3.9\grpc\framework
creating python_build\lib.win-amd64-3.9\grpc_cython
copying src\python\grpcio\grpc_cython_init_.py -> python_build\lib.win-amd64-3.9\grpc_cython
creating python_build\lib.win-amd64-3.9\grpc\framework\common
copying src\python\grpcio\grpc\framework\common\cardinality.py -> python_build\lib.win-amd64-3.9\grpc\framework\common
copying src\python\grpcio\grpc\framework\common\style.py -> python_build\lib.win-amd64-3.9\grpc\framework\common
copying src\python\grpcio\grpc\framework\common_init_.py -> python_build\lib.win-amd64-3.9\grpc\framework\common
creating python_build\lib.win-amd64-3.9\grpc\framework\foundation
copying src\python\grpcio\grpc\framework\foundation\abandonment.py -> python_build\lib.win-amd64-3.9\grpc\framework\foundation
copying src\python\grpcio\grpc\framework\foundation\callable_util.py -> python_build\lib.win-amd64-3.9\grpc\framework\foundation
copying src\python\grpcio\grpc\framework\foundation\future.py -> python_build\lib.win-amd64-3.9\grpc\framework\foundation
copying src\python\grpcio\grpc\framework\foundation\logging_pool.py -> python_build\lib.win-amd64-3.9\grpc\framework\foundation
copying src\python\grpcio\grpc\framework\foundation\stream.py -> python_build\lib.win-amd64-3.9\grpc\framework\foundation
copying src\python\grpcio\grpc\framework\foundation\stream_util.py -> python_build\lib.win-amd64-3.9\grpc\framework\foundation
copying src\python\grpcio\grpc\framework\foundation_init_.py -> python_build\lib.win-amd64-3.9\grpc\framework\foundation
creating python_build\lib.win-amd64-3.9\grpc\framework\interfaces
copying src\python\grpcio\grpc\framework\interfaces_init_.py -> python_build\lib.win-amd64-3.9\grpc\framework\interfaces
creating python_build\lib.win-amd64-3.9\grpc\framework\interfaces\base
copying src\python\grpcio\grpc\framework\interfaces\base\base.py -> python_build\lib.win-amd64-3.9\grpc\framework\interfaces\base
copying src\python\grpcio\grpc\framework\interfaces\base\utilities.py -> python_build\lib.win-amd64-3.9\grpc\framework\interfaces\base
copying src\python\grpcio\grpc\framework\interfaces\base_init_.py -> python_build\lib.win-amd64-3.9\grpc\framework\interfaces\base
creating python_build\lib.win-amd64-3.9\grpc\framework\interfaces\face
copying src\python\grpcio\grpc\framework\interfaces\face\face.py -> python_build\lib.win-amd64-3.9\grpc\framework\interfaces\face
copying src\python\grpcio\grpc\framework\interfaces\face\utilities.py -> python_build\lib.win-amd64-3.9\grpc\framework\interfaces\face
copying src\python\grpcio\grpc\framework\interfaces\face_init_.py -> python_build\lib.win-amd64-3.9\grpc\framework\interfaces\face
creating python_build\lib.win-amd64-3.9\grpc_cython_cygrpc
copying src\python\grpcio\grpc_cython_cygrpc_init_.py -> python_build\lib.win-amd64-3.9\grpc_cython_cygrpc
creating python_build\lib.win-amd64-3.9\grpc_cython_credentials
copying src\python\grpcio\grpc_cython_credentials\roots.pem -> python_build\lib.win-amd64-3.9\grpc_cython_credentials
running build_ext
Found cython-generated files...
building 'grpc._cython.cygrpc' extension
Traceback (most recent call last):
File "C:\Users\shree\AppData\Local\Temp\pip-install-gba23662\grpcio_bfd768fa280047b498d6335e41535718\src\python\grpcio\commands.py", line 292, in build_extensions
build_ext.build_ext.build_extensions(self)
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\command\build_ext.py", line 449, in build_extensions
self._build_extensions_serial()
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\command\build_ext.py", line 474, in _build_extensions_serial
self.build_extension(ext)
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\site-packages\setuptools\command\build_ext.py", line 208, in build_extension
_build_ext.build_extension(self, ext)
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\command\build_ext.py", line 529, in build_extension
objects = self.compiler.compile(sources,
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils_msvccompiler.py", line 323, in compile
self.initialize()
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils_msvccompiler.py", line 220, in initialize
vc_env = _get_vc_env(plat_spec)
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\site-packages\setuptools\msvc.py", line 314, in msvc14_get_vc_env
return _msvc14_get_vc_env(plat_spec)
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\site-packages\setuptools\msvc.py", line 268, in _msvc14_get_vc_env
raise distutils.errors.DistutilsPlatformError(
distutils.errors.DistutilsPlatformError: Microsoft Visual C++ 14.0 is required. Get it with "Build Tools for Visual Studio": https://visualstudio.microsoft.com/downloads/
During handling of the above exception, another exception occurred:
Traceback (most recent call last):
File "", line 1, in
File "C:\Users\shree\AppData\Local\Temp\pip-install-gba23662\grpcio_bfd768fa280047b498d6335e41535718\setup.py", line 297, in
setuptools.setup(
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\site-packages\setuptools_init_.py", line 165, in setup
return distutils.core.setup(**attrs)
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\core.py", line 148, in setup
dist.run_commands()
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\dist.py", line 966, in run_commands
self.run_command(cmd)
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\dist.py", line 985, in run_command
cmd_obj.run()
File "C:\Users\shree\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages\wheel\bdist_wheel.py", line 299, in run
self.run_command('build')
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\dist.py", line 985, in run_command
cmd_obj.run()
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\command\build.py", line 135, in run
self.run_command(cmd_name)
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\cmd.py", line 313, in run_command
self.distribution.run_command(command)
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\dist.py", line 985, in run_command
cmd_obj.run()
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\site-packages\setuptools\command\build_ext.py", line 87, in run
_build_ext.run(self)
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\command\build_ext.py", line 340, in run
self.build_extensions()
File "C:\Users\shree\AppData\Local\Temp\pip-install-gba23662\grpcio_bfd768fa280047b498d6335e41535718\src\python\grpcio\commands.py", line 295, in build_extensions
support.diagnose_build_ext_error(self, error, formatted_exception)
File "C:\Users\shree\AppData\Local\Temp\pip-install-gba23662\grpcio_bfd768fa280047b498d6335e41535718\src\python\grpcio\support.py", line 104, in diagnose_build_ext_error
raise commands.CommandError(
commands.CommandError:
We could not diagnose your build failure. If you are unable to proceed, please file an issue at http://www.github.com/grpc/grpc with [Python install] in the title; please attach the whole log (including everything that may have appeared above the Python backtrace).
Traceback (most recent call last):
File "C:\Users\shree\AppData\Local\Temp\pip-install-gba23662\grpcio_bfd768fa280047b498d6335e41535718\src\python\grpcio\commands.py", line 292, in build_extensions
build_ext.build_ext.build_extensions(self)
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\command\build_ext.py", line 449, in build_extensions
self._build_extensions_serial()
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\command\build_ext.py", line 474, in _build_extensions_serial
self.build_extension(ext)
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\site-packages\setuptools\command\build_ext.py", line 208, in build_extension
_build_ext.build_extension(self, ext)
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\command\build_ext.py", line 529, in build_extension
objects = self.compiler.compile(sources,
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils_msvccompiler.py", line 323, in compile
self.initialize()
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils_msvccompiler.py", line 220, in initialize
vc_env = _get_vc_env(plat_spec)
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\site-packages\setuptools\msvc.py", line 314, in msvc14_get_vc_env
return _msvc14_get_vc_env(plat_spec)
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\site-packages\setuptools\msvc.py", line 268, in _msvc14_get_vc_env
raise distutils.errors.DistutilsPlatformError(
distutils.errors.DistutilsPlatformError: Microsoft Visual C++ 14.0 is required. Get it with "Build Tools for Visual Studio": https://visualstudio.microsoft.com/downloads/

ERROR: Failed building wheel for grpcio
Running setup.py clean for grpcio
Failed to build grpcio
Installing collected packages: grpcio
Attempting uninstall: grpcio
Found existing installation: grpcio 1.35.0
Uninstalling grpcio-1.35.0:
Successfully uninstalled grpcio-1.35.0
Running setup.py install for grpcio ... error
ERROR: Command errored out with exit status 1:
command: 'C:\Users\shree\AppData\Local\Microsoft\WindowsApps\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\python.exe' -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\Users\shree\AppData\Local\Temp\pip-install-gba23662\grpcio_bfd768fa280047b498d6335e41535718\setup.py'"'"'; file='"'"'C:\Users\shree\AppData\Local\Temp\pip-install-gba23662\grpcio_bfd768fa280047b498d6335e41535718\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' install --record 'C:\Users\shree\AppData\Local\Temp\pip-record-1mo3hz2b\install-record.txt' --single-version-externally-managed --user --prefix= --compile --install-headers 'C:\Users\shree\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\Include\grpcio'
cwd: C:\Users\shree\AppData\Local\Temp\pip-install-gba23662\grpcio_bfd768fa280047b498d6335e41535718
Complete output (143 lines):
Found cython-generated files...
running install
running build
running build_py
running build_project_metadata
creating python_build
creating python_build\lib.win-amd64-3.9
creating python_build\lib.win-amd64-3.9\grpc
copying src\python\grpcio\grpc_auth.py -> python_build\lib.win-amd64-3.9\grpc
copying src\python\grpcio\grpc_channel.py -> python_build\lib.win-amd64-3.9\grpc
copying src\python\grpcio\grpc_common.py -> python_build\lib.win-amd64-3.9\grpc
copying src\python\grpcio\grpc_grpcio_metadata.py -> python_build\lib.win-amd64-3.9\grpc
copying src\python\grpcio\grpc_interceptor.py -> python_build\lib.win-amd64-3.9\grpc
copying src\python\grpcio\grpc_plugin_wrapping.py -> python_build\lib.win-amd64-3.9\grpc
copying src\python\grpcio\grpc_server.py -> python_build\lib.win-amd64-3.9\grpc
copying src\python\grpcio\grpc_utilities.py -> python_build\lib.win-amd64-3.9\grpc
copying src\python\grpcio\grpc_init_.py -> python_build\lib.win-amd64-3.9\grpc
creating python_build\lib.win-amd64-3.9\grpc\beta
copying src\python\grpcio\grpc\beta\implementations.py -> python_build\lib.win-amd64-3.9\grpc\beta
copying src\python\grpcio\grpc\beta\interfaces.py -> python_build\lib.win-amd64-3.9\grpc\beta
copying src\python\grpcio\grpc\beta\utilities.py -> python_build\lib.win-amd64-3.9\grpc\beta
copying src\python\grpcio\grpc\beta_client_adaptations.py -> python_build\lib.win-amd64-3.9\grpc\beta
copying src\python\grpcio\grpc\beta_metadata.py -> python_build\lib.win-amd64-3.9\grpc\beta
copying src\python\grpcio\grpc\beta_server_adaptations.py -> python_build\lib.win-amd64-3.9\grpc\beta
copying src\python\grpcio\grpc\beta_init_.py -> python_build\lib.win-amd64-3.9\grpc\beta
creating python_build\lib.win-amd64-3.9\grpc\experimental
copying src\python\grpcio\grpc\experimental\gevent.py -> python_build\lib.win-amd64-3.9\grpc\experimental
copying src\python\grpcio\grpc\experimental_init_.py -> python_build\lib.win-amd64-3.9\grpc\experimental
creating python_build\lib.win-amd64-3.9\grpc\framework
copying src\python\grpcio\grpc\framework_init_.py -> python_build\lib.win-amd64-3.9\grpc\framework
creating python_build\lib.win-amd64-3.9\grpc_cython
copying src\python\grpcio\grpc_cython_init_.py -> python_build\lib.win-amd64-3.9\grpc_cython
creating python_build\lib.win-amd64-3.9\grpc\framework\common
copying src\python\grpcio\grpc\framework\common\cardinality.py -> python_build\lib.win-amd64-3.9\grpc\framework\common
copying src\python\grpcio\grpc\framework\common\style.py -> python_build\lib.win-amd64-3.9\grpc\framework\common
copying src\python\grpcio\grpc\framework\common_init_.py -> python_build\lib.win-amd64-3.9\grpc\framework\common
creating python_build\lib.win-amd64-3.9\grpc\framework\foundation
copying src\python\grpcio\grpc\framework\foundation\abandonment.py -> python_build\lib.win-amd64-3.9\grpc\framework\foundation
copying src\python\grpcio\grpc\framework\foundation\callable_util.py -> python_build\lib.win-amd64-3.9\grpc\framework\foundation
copying src\python\grpcio\grpc\framework\foundation\future.py -> python_build\lib.win-amd64-3.9\grpc\framework\foundation
copying src\python\grpcio\grpc\framework\foundation\logging_pool.py -> python_build\lib.win-amd64-3.9\grpc\framework\foundation
copying src\python\grpcio\grpc\framework\foundation\stream.py -> python_build\lib.win-amd64-3.9\grpc\framework\foundation
copying src\python\grpcio\grpc\framework\foundation\stream_util.py -> python_build\lib.win-amd64-3.9\grpc\framework\foundation
copying src\python\grpcio\grpc\framework\foundation_init_.py -> python_build\lib.win-amd64-3.9\grpc\framework\foundation
creating python_build\lib.win-amd64-3.9\grpc\framework\interfaces
copying src\python\grpcio\grpc\framework\interfaces_init_.py -> python_build\lib.win-amd64-3.9\grpc\framework\interfaces
creating python_build\lib.win-amd64-3.9\grpc\framework\interfaces\base
copying src\python\grpcio\grpc\framework\interfaces\base\base.py -> python_build\lib.win-amd64-3.9\grpc\framework\interfaces\base
copying src\python\grpcio\grpc\framework\interfaces\base\utilities.py -> python_build\lib.win-amd64-3.9\grpc\framework\interfaces\base
copying src\python\grpcio\grpc\framework\interfaces\base_init_.py -> python_build\lib.win-amd64-3.9\grpc\framework\interfaces\base
creating python_build\lib.win-amd64-3.9\grpc\framework\interfaces\face
copying src\python\grpcio\grpc\framework\interfaces\face\face.py -> python_build\lib.win-amd64-3.9\grpc\framework\interfaces\face
copying src\python\grpcio\grpc\framework\interfaces\face\utilities.py -> python_build\lib.win-amd64-3.9\grpc\framework\interfaces\face
copying src\python\grpcio\grpc\framework\interfaces\face_init_.py -> python_build\lib.win-amd64-3.9\grpc\framework\interfaces\face
creating python_build\lib.win-amd64-3.9\grpc_cython_cygrpc
copying src\python\grpcio\grpc_cython_cygrpc_init_.py -> python_build\lib.win-amd64-3.9\grpc_cython_cygrpc
creating python_build\lib.win-amd64-3.9\grpc_cython_credentials
copying src\python\grpcio\grpc_cython_credentials\roots.pem -> python_build\lib.win-amd64-3.9\grpc_cython_credentials
running build_ext
Found cython-generated files...
building 'grpc._cython.cygrpc' extension
Traceback (most recent call last):
File "C:\Users\shree\AppData\Local\Temp\pip-install-gba23662\grpcio_bfd768fa280047b498d6335e41535718\src\python\grpcio\commands.py", line 292, in build_extensions
build_ext.build_ext.build_extensions(self)
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\command\build_ext.py", line 449, in build_extensions
self._build_extensions_serial()
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\command\build_ext.py", line 474, in _build_extensions_serial
self.build_extension(ext)
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\site-packages\setuptools\command\build_ext.py", line 208, in build_extension
_build_ext.build_extension(self, ext)
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\command\build_ext.py", line 529, in build_extension
objects = self.compiler.compile(sources,
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils_msvccompiler.py", line 323, in compile
self.initialize()
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils_msvccompiler.py", line 220, in initialize
vc_env = _get_vc_env(plat_spec)
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\site-packages\setuptools\msvc.py", line 314, in msvc14_get_vc_env
return _msvc14_get_vc_env(plat_spec)
File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\site-packages\setuptools\msvc.py", line 268, in _msvc14_get_vc_env
raise distutils.errors.DistutilsPlatformError(
distutils.errors.DistutilsPlatformError: Microsoft Visual C++ 14.0 is required. Get it with "Build Tools for Visual Studio": https://visualstudio.microsoft.com/downloads/
During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "C:\Users\shree\AppData\Local\Temp\pip-install-gba23662\grpcio_bfd768fa280047b498d6335e41535718\setup.py", line 297, in <module>
    setuptools.setup(
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\site-packages\setuptools\__init__.py", line 165, in setup
    return distutils.core.setup(**attrs)
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\core.py", line 148, in setup
    dist.run_commands()
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\dist.py", line 966, in run_commands
    self.run_command(cmd)
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\dist.py", line 985, in run_command
    cmd_obj.run()
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\site-packages\setuptools\command\install.py", line 61, in run
    return orig.install.run(self)
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\command\install.py", line 546, in run
    self.run_command('build')
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\dist.py", line 985, in run_command
    cmd_obj.run()
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\command\build.py", line 135, in run
    self.run_command(cmd_name)
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\cmd.py", line 313, in run_command
    self.distribution.run_command(command)
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\dist.py", line 985, in run_command
    cmd_obj.run()
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\site-packages\setuptools\command\build_ext.py", line 87, in run
    _build_ext.run(self)
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\command\build_ext.py", line 340, in run
    self.build_extensions()
  File "C:\Users\shree\AppData\Local\Temp\pip-install-gba23662\grpcio_bfd768fa280047b498d6335e41535718\src\python\grpcio\commands.py", line 295, in build_extensions
    support.diagnose_build_ext_error(self, error, formatted_exception)
  File "C:\Users\shree\AppData\Local\Temp\pip-install-gba23662\grpcio_bfd768fa280047b498d6335e41535718\src\python\grpcio\support.py", line 104, in diagnose_build_ext_error
    raise commands.CommandError(
commands.CommandError:

We could not diagnose your build failure. If you are unable to proceed, please file an issue at http://www.github.com/grpc/grpc with `[Python install]` in the title; please attach the whole log (including everything that may have appeared above the Python backtrace).

Traceback (most recent call last):
  File "C:\Users\shree\AppData\Local\Temp\pip-install-gba23662\grpcio_bfd768fa280047b498d6335e41535718\src\python\grpcio\commands.py", line 292, in build_extensions
    build_ext.build_ext.build_extensions(self)
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\command\build_ext.py", line 449, in build_extensions
    self._build_extensions_serial()
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\command\build_ext.py", line 474, in _build_extensions_serial
    self.build_extension(ext)
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\site-packages\setuptools\command\build_ext.py", line 208, in build_extension
    _build_ext.build_extension(self, ext)
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\command\build_ext.py", line 529, in build_extension
    objects = self.compiler.compile(sources,
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\_msvccompiler.py", line 323, in compile
    self.initialize()
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\distutils\_msvccompiler.py", line 220, in initialize
    vc_env = _get_vc_env(plat_spec)
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\site-packages\setuptools\msvc.py", line 314, in msvc14_get_vc_env
    return _msvc14_get_vc_env(plat_spec)
  File "C:\Program Files\WindowsApps\PythonSoftwareFoundation.Python.3.9_3.9.496.0_x64__qbz5n2kfra8p0\lib\site-packages\setuptools\msvc.py", line 268, in _msvc14_get_vc_env
    raise distutils.errors.DistutilsPlatformError(
distutils.errors.DistutilsPlatformError: Microsoft Visual C++ 14.0 is required. Get it with "Build Tools for Visual Studio": https://visualstudio.microsoft.com/downloads/

----------------------------------------

Rolling back uninstall of grpcio
Moving to c:\users\shree\appdata\local\packages\pythonsoftwarefoundation.python.3.9_qbz5n2kfra8p0\localcache\local-packages\python39\site-packages\grpc
from C:\Users\shree\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages~rpc
Moving to c:\users\shree\appdata\local\packages\pythonsoftwarefoundation.python.3.9_qbz5n2kfra8p0\localcache\local-packages\python39\site-packages\grpcio-1.35.0.dist-info
from C:\Users\shree\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\site-packages~rpcio-1.35.0.dist-info
ERROR: Command errored out with exit status 1: 'C:\Users\shree\AppData\Local\Microsoft\WindowsApps\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\python.exe' -u -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'C:\Users\shree\AppData\Local\Temp\pip-install-gba23662\grpcio_bfd768fa280047b498d6335e41535718\setup.py'"'"'; file='"'"'C:\Users\shree\AppData\Local\Temp\pip-install-gba23662\grpcio_bfd768fa280047b498d6335e41535718\setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(file);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, file, '"'"'exec'"'"'))' install --record 'C:\Users\shree\AppData\Local\Temp\pip-record-1mo3hz2b\install-record.txt' --single-version-externally-managed --user --prefix= --compile --install-headers 'C:\Users\shree\AppData\Local\Packages\PythonSoftwareFoundation.Python.3.9_qbz5n2kfra8p0\LocalCache\local-packages\Python39\Include\grpcio' Check the logs for full command output.
Make sure you include information that can help us debug (full error message, exception listing, stack trace, logs).
See TROUBLESHOOTING.md for how to diagnose problems better.
Anything else we should know about your project / environment?

You are using Python 3.9. When we ship gRPC Python 1.11, the Python 3.9 isn't released yet. Please consider upgrade to latest version.

authors: lidizheng shreethatte


text:
Insecure server construction should be explicit in Node.js

Constructing a server that does NOT use SSL should follow an API where there is an explicit insecure credential object passed during server construction. This ensures that server authors learn the API for building a secure server, and that they never build an insecure server implicitly.

Servers are not inherently secure or insecure. Is this supposed to be about creating channels (which is what I thought at first given the recent grpc_channel_create -> grpc_insecure_channel_create), or about binding secure/insecure ports to servers?

Secure : Servers that are set up with an SSL/TLS cert , Insecure: No
SSL/TLS cert.
On Mon, Jul 27, 2015 at 3:01 PM, Michael Lumish notifications@github.com
wrote:

Servers are not inherently secure or insecure. Is this supposed to be
about creating channels (which is what I thought at first given the recent
grpc_channel_create -> grpc_insecure_channel_create), or about binding
secure/insecure ports to servers?
—
Reply to this email directly or view it on GitHub
https://github.com/grpc/grpc/issues/2615#issuecomment-125355673.