Unexpected behaviour when making prop (ref) object reactive

Vue version
3.2.47
Link to minimal reproduction
https://sfc.vuejs.org/#eNqlVEuT2jAM/iuaXGBnIJnSGwXaTvdx2Q6dLkdfQqKAaWJ7bCd7YPLfKzuPze4Gpo8LWJL1Wd8nKefgq1JhVWKwDFYm0VxZMGhLtWGCF0pqC2fQmM1Aiu+yFBZTqCHTsoAJZU36W99koVp/GDnDgVKYiUQKY6EwB1g7pOlN57JIP43vzASA1ByFjS2XYgmTPBapSWLlQGrKYaKvYDq9gfUGfBLhhlWcl0hI3uFQl83xGiRATbgN9CpqmBNnMiwWKo8tkgWwOn7Y/MQ4sbxCkPsTJrZhqbRUwI0pcRXRHX83cRpUc56tWUB1sQCWpUoJap7xHOd0il8irs4Fme6f7IggVlH/djALGmHnRazCk5GCGuRJsTZgWNDTZAGJ7WwWHK1VZhlFJktcB04mlPoQ0SnUpB0vMERTzPdaPhvUBMyC2QAjImeFeq5RpKhRX8N8c/UdbqcxUenm4fqQtSoPx+uTZyygGRinuaE+p5hxgT+c5SaHEZJT+Z5EviWNl7D1jWqIeZ0HrvqmA/WoMscwl4epx6ZZcJHmtUzqwsH5EW1qa+Y0DEN/O3z97DvoF4jFZQxf3kiqlYdDjltNmYNphx7SJ1If+vmmi1di6/Vw/OEzTJzsOuZ2AmObMVaKYzFay+JCHW/8f1vDtbVMeeUPbkM/tieAW0TVbmkbjProIAXgvlthQzt0hteNhNoL4LIHzwzTH2US531HPUQ/LaPJ+9JakuBLkvPkl1v6VlIW9Ji7u6cd7LYPD493HUCTNcLz6RjnuXz+F6p+3v6L4YXsSxQXf8yxgxt+BuvfBSAx5g==
Steps to reproduce

Create ref with object deep at least 2 levels
pass it through props to child component
create local, reactive variable in child component using object descructuring
make some changes to local object

What is expected?
Changing local variable should not change prop (parent component's) variable
What is actually happening?
Changing local variable also introduces change of original variable from parent component
System Info
No response
Any additional comments?
No response

This appears to be working correctly to me.
msg.value and props.updateFileData are the same object. This is creating a shallow copy of that object:
const formData = reactive({
  ...props.updateFileData
});

So formData is a different object. But the nested object in msg.value.test and props.updateFileData.test is the same object as formData.test. Try adding {{ updateFileData.test === formData.test }} to your template, it should confirm that they are the same object.
If you have further questions about this I suggest asking on the Vue Discord at https://chat.vuejs.org/.


Flow controllers are not exported correctly

The index file is supposed to export all the flow controllers at the end of the file:
// Export all flow controllers and the main concurrently function,
// so that 3rd-parties can use them however they want
exports.concurrently = concurrently;
exports.Logger = Logger;
exports.InputHandler = InputHandler;

This does not work because you have redefined module.exports and exports no longer references module.exports:
module.exports = (commands, options = {}) => { /*...*/ };

// This will not export anything
exports.Logger = Logger;

A simple fix is to use module.exports everywhere instead of exports.

🤦 thanks for catching this!!


Changing prefix (/IoTmanager by default) is not loded to dasboard

If change prefix from /IoTmanager to /IoTmanager/m for example in settings of IoTmanager and in my app,
IoTmanager still use /IoTmanager/+/config instead of /IoTmanager/m/+/config for load configuration of dashboard. For msg with topic like  /IoTmanager/m/deviceID/config in logs I see "Unexpected message arrived "

You can use "one-level" prefix only, ex "/myhome" or "myhome". Its bug will be fixed in furture.

Try 2.1.0 version


Filter boxes (specifically dashboards and tasks) should treat spaces as AND

for example, the existing logic would take a filter string "use:slo owner:edd" and search for that exact phrase.  This would update that filter to filter "use:slo" AND "owner:edd".

Alternately / related, consider a label-picker?


[Feature] Add version numbers to themes and plugins

Before Requesting

[X] I found no existing issue matching my feature request
[X] This request is related to Millennium, and not a request for a specific theme/addon

Describe the feature you'd like!
Right now it hard to tell what version of millennium or any theme I'm on since it not shown. This could be shown next to the name
Name - v2.0.0
Anything else?
No response

The version of a theme is available under the (i) icon in the themes panel.

You can see the version of Millennium by running
millennium --version in cmd/powershell


[23051][Fix] LAContext and AccessControl tests fixed.

Ticket

[23051]

Description

Tests created to validate Keychain with AccessControl and LAContext.
Tests moved to specific class in order to run them on real devices only (integration suite).

Commit message

[23051][Fix] LAContext and AccessControl tests fixed.

Screenshot

Testing

[ ] Added unit tests
[ ] Ran unit tests successfully
[ ] Added documentation for public APIs and/or Wiki

Code coverage
Total coverage: 94.57%

Powered by Slather

  Generated by :no_entry_sign: Danger


#706 Fixing issue when importing a job template with a schedule.

Coverage decreased (-0.04%) to 64.276% when pulling e7a5d275bde668999275c98819675bdd60295bf3 on john-westcott-iv:master into fa54024d2eeb097fcfa4eaf45d60b196addd941d on ansible:master.

Coverage decreased (-0.04%) to 64.276% when pulling e7a5d275bde668999275c98819675bdd60295bf3 on john-westcott-iv:master into fa54024d2eeb097fcfa4eaf45d60b196addd941d on ansible:master.

this is going to be fixing #706, and I'm going to be marking that for the next release


[Compute] az vm host group create: Add new parameters --ultra-ssd-enabled to support Ultra SSD

Description

Changes related to dedicated host group for Ultra SSD support https://github.com/Azure/azure-cli/issues/21997
wait SDK update(waiting)
Testing Guide

History Notes

[Component Name 1] BREAKING CHANGE: az command a: Make some customer-facing breaking change
[Component Name 2] az command b: Add some customer-facing feature

This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] The PR title and description has followed the guideline in Submitting Pull Requests.

[ ] I adhere to the Command Guidelines.

[ ] I adhere to the Error Handling Guidelines.

Compute


Redirect in action

I want to redirect after receive response from server in action. What is the best way to do it?
export const redirect = (event) : Function => {
  return (dispatch: Function) => {
    event.preventDefault()
     return axios.post('http://localhost:8080/api/some',data)
            .then((res) => {
                //redirect here
               })
               .catch((err) => {
                    dispatch(handleErrors(err.response.data.error))
               })
   }
}

You can import push or replace function from react-router-redux. They accept url or desctiption object as param, described here
 import { push, replace } from 'react-router-redux'

// and then anywhere in the code
dispatch(push('/url'))
dispatch(replace('/url'))

Thank you I've tried, url is changing but page stills the same, I have tried redux-router but same issue.

I'm using browserHistory.push from react-router.
import { browserHistory } from 'react-router'
...
browserHistory.push('/url')

Only context router is working for me. It is a good practice?
Like,
class Header extends React.Component{
 logout(e){
   e.preventDefault()
   this.props.logout()
   this.context.router.push('/auth')
 }
render(){...}
}
Header.contextTypes = {
  router: React.PropTypes.object.isRequired
}
export default connect(null , {logout})(Header)

@enesTufekci
In case if you use react-router-redux and routerMiddleware + createBrowserHistory then it should be possible to do that with push from the same module. Then it should be synced with the redux store accordingly. Doesn't this work for you? I'm also curious how would you test routes in this case.

`import { locationChange } from 'store/location'
export const redirect = (event) : Function => {
return (dispatch: Function) => {
event.preventDefault()
return axios.post('http://localhost:8080/api/some',data)
.then((res) => {
dispatch(locationChange(location = 'your url'))
})
.catch((err) => {
dispatch(handleErrors(err.response.data.error))
})
}
}`


Issue with New Code

Hi,
I get error with new code as soon as I run it.
On the CMD screenshot below, I have split it into two errors:

When we run the program as is.
When we comment out the if chapter_title line then we get the second error.

Please find the screenshot as below:

Thanks for pointing it out! I commited the wrong files yesterday, should be working now.
I did not get the second error in my testing, if it does appear in the new version just comment under this issue with the specific chapter number and book name so I can take a look.

Thanks, the first error is gone. However, the second one persists.
In order to reproduce it, try the following:
**> Novel: Martial World

Start: 1476
End: 1499**
Thanks again for the prompt responses

I see. The way I wrote the part to get the chapter title doesn't seem to work out as expected. Only tested the code on two novels. I'll write a fix for it in the next couple of days.
For now just change line 39 in getify.py to:
chapter_title = soup.find("span").text
or to:
chapter_title = soup.find("strong").extract().text
This will make it work for matrial world but will break code for some other novels.
I can't test it atm but if both of those fixes don't work just use:
chapter_title = "Some random string"
this will break the table of contents but will fix this bug across all novels.

Actually found some time. New update should fix the problem. Didn't check but it should work now for all novels.


config file draft

Hi, here's a very basic config file template designed to work with pproxy. I'm open for all sorts of feedback and improvement as this probably covers ~60 percent of what pproxy offers.
{
    "general":{
        "block":{
            "enabled": true,
            "type": "path_list/regex_list",
            "values": [
                "<IP_ADDRESS>/24",
                "<IP_ADDRESS>/24",
                "in case of path_list => /path/to/the/file1",
                "in case of path_list => /path/to/the/file2"
            ]
        },
        "check_alive":{
            "enabled": true,
            "interval": 30
        },
        "schedule":{
            "enabled":true,
            "algorithm": "fa"
        },
        "pac":{
            "enabled": true,
            "path": "asdasds"
        },
        "sys":{
            "enabled": true
        },
        "test":{
            "enabled": true,
            "path": "http://ident.me"
        }

    },
    "servers":[
            {
                "enabled": true,
                "name": "SERVER1",
                "type": "in/out",
                "addr": "<IP_ADDRESS>",
                "port": "80",
                "unix_socket": "/tmp/myproxy",
                "inverse": false,
                "http_settings":{
                    "enabled": true,
                    "disable_http_connect": true,

                    "auth": {
                        "enabled": true,
                        "creds": [
                            "user1:pass1",
                            "user2:pass2"
                        ]
                    },
                    "ssl": {
                        "enabled": true,
                        "type": "base64/path/insecure",
                        "cert": "asdasdasd",
                        "key": "asdasdasd"
                    }
                },
                "socks_settings":{
                    "enabled":true,
                    "version": "4/5/4+5",
                    "auth": {
                        "enabled": true,
                        "creds": [
                            "user1:pass1",
                            "user2:pass2"
                        ]
                    },
                    "ssl": {
                        "enabled": true,
                        "type": "base64/path/insecure",
                        "cert": "asdasdasd",
                        "key": "asdasdasd"
                    }
                },
                "ss_settings":{
                    "enabled": true,
                    "password": "123",
                    "cipher": "aes-256-gcm",
                    "ssl": {
                        "enabled": true,
                        "type": "base64/path/insecure",
                        "cert": "asdasdasd",
                        "key": "asdasdasd"
                    }
                },
                "ssr_settings":{
                    "enabled":true,
                    "password": "123",
                    "cipher": "aes-256-gcm",
                    "plugins":{
                        "enabled": true,
                        "values":[
                            "plain",
                            "origin",
                            "http_simple",
                            "tls1.2_ticket_auth",
                            "verify_simple",
                            "verify_deflate"
                        ]
                    }
                },
                "redir_settings":{
                    "enabled": true
                },
                "tunnel_settings":{
                    "enabled": true,
                    "hosts": ["www.google.com"]
                },
                "ssh_settings":{
                    "enabled": true,
                    "remote_host": "<IP_ADDRESS>",
                    "remote_port": 22,
                    "cred_type": "password/key_path/key_base64",
                    "username": "root",
                    "cred": "whatever"
                },
                "ws_settings":{
                    "enabled": true,
                    "ssl": {
                        "enabled": true,
                        "type": "base64/path/insecure",
                        "cert": "asdasdasd",
                        "key": "asdasdasd"
                    }
                }
            }
        ]
}

couple of points:

It's json instead of yaml (#45) because I didn't want to introduce a new dependency
I have no idea how to implement relays (with __ syntax) in this json :)

Cool template design!
My suggestion is relays can be implemented by adding a key "relay" in "servers".
It can be nested with several layers.
for example:
"servers": [
{
"enabled": true,
"name": "SERVER1",
........
"relay": {
"enabled": true,
"name": "SERVER2",
........
"relay": {
"enabled": true,
"name": "FINAL_SERVE",
........
}
}
}
]

ok I think I got your point. But here's a bigger question. Do we need to identify one of the methods (config file or command line arguments) as a main template and convert the other one to the template? This way we can make pluggable configuration formats connected to pproxy if we wanted.

Currently I don't see great benefits of using a configuration file. Maybe converting from json config file to command line argument parameter is a good way to make it easier.

I agree with this not being a high priority. Let's keep this here as an open improvement issue but with lower priority. Meanwhile, I'll try to work on some low hanging fruit.

Form my side i dont like that auth informations are handled via command option. I'm under linux and when im doing ps i see my proxy password what i dont want to!
So in general a +1 from me for the config file! Maybe start with a MVP just for the pw ;)
It would be nice if passwords are not stored in plaintext  somewhere. Instead it would be nice if passwords are fetched from linux keyring. e.g. via secret-tool but i guess that is to os specific.

Form my side i dont like that auth informations are handled via command option. I'm under linux and when im doing ps i see my proxy password what i dont want to!
So in general a +1 from me for the config file! Maybe start with a MVP just for the pw ;)
It would be nice if passwords are not stored in plaintext somewhere. Instead it would be nice if passwords are fetched from linux keyring. e.g. via secret-tool but i guess that is to os specific.

I use python script to avoid auth information leak via command option.
Python script is better than config file, I think.

Forget shadowsocks. We config like this:
arg=(
'-l','socks5://<IP_ADDRESS>:8080',
'-r','ss://cipher:key@<IP_ADDRESS>:8000',
)
pproxy.server.main(args)
Wasn't is cool?


MDC-101>Step 4> Issue id: ObsoleteLayoutParam

Noob Alert:
android:layout_alignParentEnd="true"
android:layout_alignParentRight="true"
When adding this code to the MaterialButton, i get the following.

Not sure what I'm doing wrong here. Ofcourse, I'm able to see the output properly. But I want to understand what is obsolete here. Is it a mistake from my side?

So I have typed the same line inside  & <..MaterialButton>
The code below is a param of RelativeLayout which is the parent layout for material button.Where as it is not a param for LinearLayout which is the parent layout for Relativelayout.
android:layout_alignParentEnd="true" android:layout_alignParentRight="true"
I hope this gives you some understanding.


Fixes #297

Fixes #297

I'm not sure about the Veniam>Nexar change, but I guess they hire remote either way so it should be fine.


Feature/init no connection

Adding a init() that doesn't connect the MM wallet to the safe, for read only tests

I just decided to fix this branch and also commit the new test here as well instead of creating a whole new branch for it


Black picture

https://github.com/RobertLucian/license-plate-dataset/blob/master/dataset/train/images/dayride_type1_001.mp4%23t%3D558.jpg
Doesn't seem to show something other than black.

and 809


"Radu Negru" is listed in the drop-down menu

Description:
"Radu Negru" is listed in the drop-down menu alongside its corresponding county and commune, according to the law
Precondition:
The website is up an running.

Step 1
Type "Radu Negru" in the search bar.

Expected results
The location is listed in the drop-down menu as "Radu Negru, Argeș (Călinești)".


Command mysql not found

Laravel Version: 8.44.0
PHP Version: 8.0.3
Database Driver & Version: MySQL 5.7.34

Description:
I've implemented https://github.com/laracasts/cypress into our application. It injects endpoints into the framework to enable migrations from a Javascript API. It basically does this:
Route::post('/__cypress__/artisan', function (Request $request)
{
    Artisan::call($request->input('command'), $request->input('parameters', []));
}

I've also used php artisan schema:dump --prune to clear our migrations. The endpoint returns the following error when I call it.
I suspect it has to do with this line of code. It works when I replace the mysql-command with the full path command.
[2021-06-03 14:48:07] local.ERROR: The command "mysql  --user="${:LARAVEL_LOAD_USER}" --password="${:LARAVEL_LOAD_PASSWORD}" --host="${:LARAVEL_LOAD_HOST}" --port="${:LARAVEL_LOAD_PORT}" --database="${:LARAVEL_LOAD_DATABASE}" < "${:LARAVEL_LOAD_PATH}"" failed.

Exit Code: 127(Command not found)

Working directory: /Users/nick/Code/pixeo-flowlab/public

Output:
================

Error Output:
================
sh: mysql: command not found
 {"exception":"[object] (Symfony\\Component\\Process\\Exception\\ProcessFailedException(code: 0): The command \"mysql  --user=\"${:LARAVEL_LOAD_USER}\" --password=\"${:LARAVEL_LOAD_PASSWORD}\" --host=\"${:LARAVEL_LOAD_HOST}\" --port=\"${:LARAVEL_LOAD_PORT}\" --database=\"${:LARAVEL_LOAD_DATABASE}\" < \"${:LARAVEL_LOAD_PATH}\"\" failed.

Exit Code: 127(Command not found)

Working directory: /Users/nick/Code/pixeo-flowlab/public

Output:
================

Error Output:
================
sh: mysql: command not found
 at /Users/nick/Code/pixeo-flowlab/vendor/symfony/process/Process.php:267)
[stacktrace]
#0 /Users/nick/Code/pixeo-flowlab/vendor/laravel/framework/src/Illuminate/Database/Schema/MySqlSchemaState.php(77): Symfony\\Component\\Process\\Process->mustRun(NULL, Array)
#1 /Users/nick/Code/pixeo-flowlab/vendor/laravel/framework/src/Illuminate/Database/Console/Migrations/MigrateCommand.php(145): Illuminate\\Database\\Schema\\MySqlSchemaState->load('/Users/nick/Cod...')
#2 /Users/nick/Code/pixeo-flowlab/vendor/laravel/framework/src/Illuminate/Database/Console/Migrations/MigrateCommand.php(113): Illuminate\\Database\\Console\\Migrations\\MigrateCommand->loadSchemaState()
#3 /Users/nick/Code/pixeo-flowlab/vendor/laravel/framework/src/Illuminate/Database/Console/Migrations/MigrateCommand.php(77): Illuminate\\Database\\Console\\Migrations\\MigrateCommand->prepareDatabase()

Hi there,
Thanks for reporting but it looks like this is a question which can be asked on a support channel. Please only use this issue tracker for reporting bugs with the library itself. If you have a question on how to use functionality provided by this repo you can try one of the following channels:

Laracasts Forums
Laravel.io Forums
StackOverflow
Discord
Larachat
IRC

However, this issue will not be locked and everyone is still free to discuss solutions to your problem!
Thanks.

Your machine dont have mysql-cli installed. Install, for example, with
apt install default-mysql-client

There was a problem with my mysql installation. The problem was resolved after upgrading to mysql 8 🤷


B-18989 Show Shipment Locator for QAE tab

B-18989
Summary
Given I'm a QAE the Shipment Locator will be listed next to each shipment instead of the 5 digit identifier
Verification Steps for Reviewers
These are to be checked by a reviewer.

[ ] Has the branch been pulled in and checked out?
[ ] Have the BL acceptance criteria been met for this change?
[ ] Was the CircleCI build successful?
[ ] Has the code been reviewed from a standards and best practices point of view?

How to test

As a customer create any kind of partial or full shipment
As the Service Counselor approve the move
Login as a QAE/CSR officer
Click the "Quality assurance" tab
Verify ShipmentID shows shipment locator
Click view, create or edit report if available and verify ShipmentID shows shipment locator

Frontend

[ ] There are no aXe warnings for UI.
[ ] This works in Supported Browsers and their phone views (Chrome, Firefox, Edge).
[ ] There are no new console errors in the browser devtools.
[ ] There are no new console errors in the test output.
[ ] If this PR adds a new component to Storybook, it ensures the component is fully responsive, OR if it is intentionally not, a wrapping div using the officeApp class or custom min-width styling is used to hide any states the would not be visible to the user.
[ ] This change meets the standards for Section 508 compliance.

Screenshots
ShipmentID on QAE table/Evaluation Reports list

Shipment Locator on Evaluation Report

Recommendations:

In stead of "Shipment ID:" it should read something else since there's already an existing piece of data called the shipment id (also correct in other places where it references Shipment ID)
Take this opportunity to improve the test that is in the spot you are improving.

Recommendations:

In stead of "Shipment ID:" it should read something else since there's already an existing piece of data called the shipment id (also correct in other places where it references Shipment ID)
Take this opportunity to improve the test that is in the spot you are improving.

I added some changes to the assertions on the test files so they now use data-testids and they check the globally set values to make them easier to debug if necessary in the future.


Support for padded input_tensors in ttnn.line_all_gather

Description
In Llama3-70B we split 32 users across 4 device columns in galaxy for parallelizing the FlashDecode across batch. Then before Selfout we use ttnn.line_all_gather to concatenate the users back.
However, since the users spilt_size = 8(<TILE_HEIGHT), it contains padding and ttnn.line_all_gather doesn't remove the padding before gathering. As a workaround we use a user_selection matrix and do a matmul  with the activations to remove the padding. Presently the user_selection matmul takes around 6500 ns on device. This workaround is not that costly but we hope that the feature support for padded input tensors in line_all_gather could remove this overhead.
Requirement

Before all_line_gather
Shape of input_tensor on each device -> [1, 1, 8[32], 1024]
After all_line_gather
Shape of input_tensor on each device -> [1, 1, 32, 1024]

fyi @uaydonat, @johanna-rock-tt , @cglagovichTT , @cfjchu


Selecting datalake storage

URL: https://s.asm0dey.ru/Gpp4h
Review (1-2 sentences): Non-immutable formats are the new trend of data storage. Hudi, Iceberg, Delta Lake… which suits your needs better? Check out this article by @lakeFS and choose wisely!
Do not forget to add labels.

Published in Digest #7.


Finishing up the wrapper

I spoke to @jajhall today, and it hadn't been clear to him the state of the JuMP interface and what's blocking on whose side.
From skimming the issues, the items on HiGHS's side are:

[ ] https://github.com/ERGO-Code/HiGHS/issues/210#issuecomment-546374257 Exposing enums(?)
[ ] https://github.com/ERGO-Code/HiGHS/issues/215 cross-compilation fails (so we can't use Julia's infrastructure for building binaries for MacOS or Windows)
[ ] https://github.com/ERGO-Code/HiGHS/issues/222 query objective sense
[ ] https://github.com/ERGO-Code/HiGHS/issues/223 setOptionValue

On the JuMP interface side:

[ ] Pass MOI's LP solver tests

After the wrapper's ready, I'm happy to advertise it to current Clp users as @odow suggested in https://github.com/ERGO-Code/HiGHS/issues/210#issuecomment-544760567.
CC @matbesancon @odow @mtanneau @feldmeier

thanks for pushing this. There were issues I still had mostly with incremental changes (for which some warnings were still there).
There were some issues on getting info for individual constraints, I'll have to see whether that's fixed

The other point was to have first releases of HiGHS, even if they are not 1.0 yet, and ERGO-Code/HiGHS#215 is blocking for having a multi-platform package

Hi Miles - Salut Mathieu!
Thanks for this. I've forwarded the messages to my PhD student, Ivet Galabova (@galabovaahttps://github.com/galabovaa CCed in this message)  who is best able to handle them from the HiGHS side.
@Miles I'll be in touch tomorrow about the other things we discussed today,
All the best,
Julian
I spoke to @jajhallhttps://github.com/jajhall today, and it hadn't been clear to him the state of the Julia wrapper and what's blocking on whose side.
From skimming the issues, the items on HiGHS's side are:

ERGO-Code/HiGHS#210 (comment)https://github.com/ERGO-Code/HiGHS/issues/210#issuecomment-546374257 Exposing enums(?)
ERGO-Code/HiGHS#215https://github.com/ERGO-Code/HiGHS/issues/215 cross-compilation fails (so we can't use Julia's infrastructure for building binaries for MacOS or Windows)
ERGO-Code/HiGHS#222https://github.com/ERGO-Code/HiGHS/issues/222 query objective sense
ERGO-Code/HiGHS#223https://github.com/ERGO-Code/HiGHS/issues/223 setOptionValue

On the wrapper side:

Pass MOI's LP solver tests

After the wrapper's ready, I'm happy to advertise it to current Clp users as @odowhttps://github.com/odow suggested in ERGO-Code/HiGHS#210 (comment)https://github.com/ERGO-Code/HiGHS/issues/210#issuecomment-544760567.
CC @matbesanconhttps://github.com/matbesancon @odowhttps://github.com/odow @mtanneauhttps://github.com/mtanneau @feldmeierhttps://github.com/feldmeier
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHubhttps://github.com/matbesancon/HiGHS.jl/issues/4, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AFMWLY7SYGPLMR57MNWKQKLRJJ7TJANCNFSM4LTZMMDA.
--
Julian Hall (Operational Research MSc Academic Selector)
Dr. J. A. Julian Hall, Reader, School of Mathematics,
University of Edinburgh, James Clerk Maxwell Building,
Peter Guthrie Tait Road, EDINBURGH, EH9 3FD, UK.
Room: 5418 Phone: +44 650 5075 Email: J.A.J.Hall<EMAIL_ADDRESS>Web: https://www.maths.ed.ac.uk/school-of-mathematics/people/a-z?person=47
[HiGHS]http://www.highs.dev
My working hours may not be your working hours. Do not feel pressure to reply to this email outside your working hours.
The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.

We moved this repository to the JuMP-dev org (the new JuliaOpt) for easier collaboration. I gave @galabovaa maintainer access. Let me know if anyone else on the HiGHS team should have acces.

Now that https://github.com/ERGO-Code/HiGHS/issues/215 appears to have been fixed, does anything remain to be done (@matbesancon ) before this issue can be closed?

Some things are still broken, I'll have to go around https://github.com/ERGO-Code/HiGHS/issues/215 for now


Forum page styling improvement

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Please assign me

@Sheriff-Oladimeji Assigned!


Add various acknowledgements

Using the @all-contributors  bot add various contributors to the CONTRIBUTORS.md  file

@all-contributors add @bilalshaikh42,  @jonrkarr, @gmarupilla for code. Add @moraru, @mpw6 for infrastructure

@all-contributors add @jonrkarr  for code

@all-contributors add @gmarupilla for code

@all-contributors add @moraru for infrastructure

@all-contributors add @mpw6 for infrastructure

@all-contributors add @moraru for infrastructure

@all-contributors add @jonrkarr for design

@all-contributors add @nsf-open for financial

@all-contributors add @NIHGOV for funding

@all-contributors add @NIHGOV for financial

@all-contributors add @NSF-open for financial

@all-contributors add @NIBIB for financial

@all-contributors add @reproducible-biomedical-modeling for financial, fundingFinding, projectManagement

@all-contributers add @artgoldberg for ideas

@bilalshaikh42 Thanks Bilal.

@bilalshaikh42 Thanks Bilal.

No worries! though you might get a few more notifications as I debug the bot!


TSI files not backed up

Bug report
System info: tsi branch
Steps to reproduce:

INFLUXDB_DATA_INDEX_VERSION=tsi1 influxd
influx_stress
influxd backup -database stress /tmp/backup
tar -tvf /tmp/backup/stress.autogen.00001.00

Expected behavior:
The contents of the backups should have the index directory and tsi files.
Actual behavior:
No tsi files are backed up.

Fixed with 57f44d5.


add structured debug representation

As requested @ml86
Ideally we'd use the intellij annotation stuff to avoid having to manually configure out IDEs (we would pull in the annotations as dependency, but no actual code). Unfortunately I couldn't get that to work :(

Good solution, not having to add another dependency and being able to structurally debug these values 👍🏻


[test][embedded] Declare embedded-volatile as a test depdency

We fail to build the embedded variant of this target before running the embedded/volatile* tests, then fail to import _Volatile. Add the embedded-volatile target as a test dependency.

@swift-ci Please test


Get game controller id/index assigned by backend

This is a new method that returns an id or index number generated for a game controller by the backend. They are assigned differently by each backend when the controller is connected.
Javascript returns the value of Gamepad.index
Android returns the value of InputDevice.getId()
Lwjgl2 & Lwjgl3 return an index
This is mostly useful if you need to interface with code on a specific backend. This would let you expand the controller functions without having to edit libGDX.

IMO having this method in the core interface does not make any sense. There's nothing platform-agnostic you can do with this information.

@MrStahlfelge It's mostly for if someone needs to expand/fix something in the controller support for Android/Javascript without having to edit/update libGDX. The game engine I'm switching away from is closed source, but it's not really necessary when you know how to edit libGDX. Now that I have a good setup for editing libGDX I'm no longer in need of this. I'll be fine with it whether it gets accepted or not.

I think this make sense to have an unique ID to identify a controller especially to identify if a controller changed? Any reason this shouldn't be added?

I don't know much about controllers but I agree with @MrStahlfelge this doesn't seem right on the core interface. @noblemaster Isn't there a proper mechanism to notify when controllers are connected/disconnected?
OP answers he doesn't needs this anymore but the original use case for it was to "fix/expand" a specific implementation. If a controller implementation needs a "fix" we want it done in libGDX project. Regarding the "expand" part I think we need a specific example to justify adding this.

Added feature getUniqueId() to controllerutils in the meantime

Now that I have a good setup for editing libGDX I'm no longer in need of this.
Closing this because has conflicts, won't get updated and there's no reason to return the internal assigned id back to the core.


evaluate 4dface

https://github.com/patrikhuber/4dface

The eos component is already integrated for testing and evaluation.  More work may be required for real-time use.


Window Not Defined

Error when deploying build w/ Gatsby (static site generator), -> WebpackError: window is not defined.
Looking for a workaround right now (https://www.gatsbyjs.org/docs/debugging-html-builds/#fixing-third-party-modules) but apparently the module can be fixed.

I'm not sure ReactPlayer will work as part of a static site. The library heavily relies on the browser environment and 3rd party libraries to play videos. Even if you fixed the problem here (adding typeof window !== 'undefined' in the FilePlayer.canPlay() logic) I'm still not sure it would work.
That said, I suppose the package is popular enough to warrant making sure it doesn't cause errors when rendering on the server/node (even if it doesn't actually work when compiled).

Forgot to said it - I haven't gotten it to work yet when deploying, but the library works perfectly in local development builds though.

@lecarles Hello, I have the same issue, did you found a solution ?

No, not really - I haven't really tried because I've been looking for a an alternative (as @CookPete said that he wasn't sure reactvideo was the most adequate thing to use with a static site). Anyway if you want to fix it you can look at this https://www.gatsbyjs.org/docs/debugging-html-builds/#fixing-third-party-modules or maybe try and implement the solution he said a few comments up.

This should be sorted in 1.6.3.


693 | Binary Number with Alternating Bits | C++

693 | Binary Number with Alternating Bits | C++ -
Type of Issue - question
Please add/delete options that are not relevant.

[x] Adding New Code
[x] Improving Code
[x] Improving Documentation
[ ] Bug Fix

Programming Language
Please add/delete options that are not relevant.

[ ] Python
[x] C++
[ ] Java
[ ] SQL

Self Check

[x] Ask for an issue assignment and wait to get assigned to it before making Pull Request.
[x] Add your file to the proper folder
[x] Clean Code and Documentation for better readability
[x] Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Discord server ✉ - https://discord.gg/CXksGdn
Happy Coding,

please assign me this issue.

could you assign this issue to me?
I want to add new code.


Dop/update sample issues

@shellygill Please review for beta-dev branch inclusion.

@doneill Couple of minor comments, back to you.

Thanks @shellygill updated with your comments and am merging.


DocsArchive-<IP_ADDRESS>Auto archive content

Please don't merge this PR until target archive repo PR https://github.com/OPS-E2E-PPE/docs-yml-archive-non-versioning-archive/pull/231 is merged into live branch.
Auto archive content to https://github.com/opstest2/docs-yml-archive-non-versioning-archive.git

Docs Build status updates of commit 92d0ac9:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

.openpublishing.redirection.json
:white_check_mark:Succeeded

docs/TOC.yml
:white_check_mark:Succeeded
View

docs/index.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/article3-1-3.yml
:white_check_mark:Succeeded
View

docs/to-be-archive/level1/sql-database-engine.png
:white_check_mark:Succeeded

docs/to-be-archive/level2/article3-2-1.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-2.md
:white_check_mark:Succeeded
View

docs/to-be-archive/level2/article3-2-3.yml
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching the docs.microsoft.com contributor guidesPost your question in the Docs support channel


fix: Mobile Transfer Responsive Layout

@JoseRFelix this issue is fixed but on wallet connect window others wallets appear for a sec.
.


ERROR: ProcessNewBlock: AcceptBlock FAILED (bad-txnmrklroot, hashMerkleRoot mismatch)

This issue was observed three days ago: it appears to be the case that the merkle tree root hash computed in the python script when there are more transactions than just the coinbase is not validated by the node. I've looked at mining code for bitcoin and the FACTOR.py script computes the merkle tree root hash in just the same way. Maybe Bitcoin TapRoot, tag v22.0, changed something about how the merkle tree root hashes are computed?
Here are some of the merkle tree root hashes computed after successfully submitting a block that only has the coinbase transaction.
2022-06-22T02:35:58Z UpdateTip: new best=721ba5214561024e93af5dc67019f50415244edec2f21230ba9a23d486e25991 height=20714 version=0x20000000 nBits=260 wOffset=9 log2_work=55.675297 nonce=3069314557446586543 tx=20715 date='2022-06-22T01:44:00Z' progress=0.999368 cache=0.0MiB(38txo)
2022-06-22T02:35:58Z CreateNewBlock(): block weight: 11677 txs: 1 fees: 25800 sigops 437
GetHash[0]: 8f38f43df1532cd9874eeafa61b1485aae65b13686450655f23c522004fce62e
GetHash[1]: fc2b752ef5b0d8caa388d3d0d08c87b748fe80df27482d5de3d581783fbc3b24
MerkleRoot: 80189b3b4f080a5d8116d475ec3e4a98fd4fe84de64cfbdbc439701ace74396c
GetHash[0]: 5b60947dc6e00916518b93a66c3788a4352c1cb5e1d3c51bdecee9363c6ac9b9
MerkleRoot: 5b60947dc6e00916518b93a66c3788a4352c1cb5e1d3c51bdecee9363c6ac9b9
2022-06-22T02:55:42Z UpdateTip: new best=38a0e83727077fe61cb8103a4138ed554465b29be931a1150fafb779618b49f4 height=20715 version=0x20000000 nBits=260 wOffset=3964 log2_work=55.675448 nonce=12698259158398758397 tx=20716 date='2022-06-22T02:36:26Z' progress=0.999766 cache=0.0MiB(39txo)
2022-06-22T02:55:42Z CreateNewBlock(): block weight: 11677 txs: 1 fees: 25800 sigops 437
GetHash[0]: 6dcecc3ab69259145075dfa179336e41ffeb05efabcc1f196d8afe6054c8a564
GetHash[1]: fc2b752ef5b0d8caa388d3d0d08c87b748fe80df27482d5de3d581783fbc3b24
MerkleRoot: 7385091c89398ffb0d1d9f0720077842a5c622f3e752db6732f89670daa9b884
GetHash[0]: ae0c07a5203dd969164759daca7cd64df661244d21a70f6d23217a5f6780b870
MerkleRoot: ae0c07a5203dd969164759daca7cd64df661244d21a70f6d23217a5f6780b870

It is unclear why the first merkle tree root hash is computed at all, since the coinbase's hash would be the merkle tree hash as it is the only transaction.
Help in diagnosing the real problem and fix for it would be greatly appreciated. @daedalus
In the meantime, miners can mine blocks that include only the coinbase until a fix is found. To do that:

Rename the ~/.factorn/mempool.dat file to save the transactions in the mempool and restore them later.
Start the factorn daemon as follows ./factorn -blocksonly.

Now when you mine, only the coinbase transaction will be made for a block. Until a fix is found for the merkle tree calculation. The function that computes the merkle tree is here: https://github.com/FACT0RN/factoring/blob/main/FACTOR.py#L309

The problem lies in the line 331, the order in wich the hashes of the transactions are computed changes the final hash.

Look at this thread:
https://bitcoin.stackexchange.com/questions/53081/how-to-make-simplecoins-powerpool-to-support-litecoin-segwit
I think data is what you put in the OP_RETURN in the txout[1] of the coinbase as explained in:
https://github.com/bitcoin/bips/blob/master/bip-0141.mediawiki#specification
  if (self.default_witness_commitment is not None):
        combs = self.default_witness_commitment.decode("hex")
        data += b'\x6a'
        data += self.varlen_encode(len(combs)+4)
        data += b'\xaa\x21\xa9\xed'
        data += combs

I'm testing this on testnet atm

Tested on mainnet.

Tested on mainnet.

did you find the answer？I tested on the regtest

@midas-echo This issue was resolved over a year ago.

How? I had this problem recently


Add Spyderbat output

What type of PR is this?
/kind feature
Any specific area of the project related to this PR?
/area outputs
What this PR does / why we need it:
This PR adds Spyderbat as an output module.
Note: in order for Spyderbat to be able to use the data gathered from Falcosidekick, it needs process IDs, so my PR https://github.com/falcosecurity/falco/pull/2211 needs to be merged for this to be useful.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: spyder-kyle
Once this PR has been reviewed and has the lgtm label, please assign leogr for approval by writing /assign @leogr in a comment. For more information see:The Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

Welcome @spyder-kyle! It looks like this is your first PR to falcosecurity/falcosidekick 🎉

Done, thanks

Examples are optionnal, if you have a nice screenshot you can add it for sure

I see, I don't have anything in particular in mind for that then

I'm waiting for the release of falco 0.33 and I'm approving your PR

LGTM label has been added.  Git tree hash: b1423fcd91e79bfc8689af393a4a3a274caddeb2

@spyder-kyle can you rebase on master please

New changes are detected. LGTM label has been removed.

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: spyder-kyle
Once this PR has been reviewed and has the lgtm label, please ask for approval from issif by writing /assign @issif in a comment. For more information see:The Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@spyder-kyle: Adding label do-not-merge/contains-merge-commits because PR contains merge commits, which are not allowed in this repository.
Use git rebase to reapply your commits on top of the target branch. Detailed instructions for doing so can be found here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Whoops, misinterpreted that

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Issif, spyder-kyle
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Issif]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

LGTM label has been added.  Git tree hash: 9d1b581391ad08c8b2a393efe15a975e83df4bfe


Question: Is XML human-generated?

I have a question about that repository.
Are these XML classes human-generated, or are they generated in some other way?
XML definitions are usually done in XSD.
For example http://intel.com/wbem/wscim/1/amt-schema/1/AMT_EthernetPortSettings is there an xsd definition of a class like this?
Actually my purpose is to generate the amt class in java.

Hello!
Development of wsman-messages (and majority of go-wsman-messages) were manual efforts through the use of the Intel AMT SDK documentation.  The SDK does provide MOF files but we were not able to use them for generation although potentially possible. You can see some info about them and the classes in general in the SDK Docs.
You can download the SDK from here..  The MOFs should be in the WS-Management**Module.zip directories.  I believe Java has a spec, JMI, that might make use of the MOFs. But, I am not overly familiar with that path.
I'll close the issue, but feel free to re-open if you have follow-on questions.


⚠ Turnos 24x7 has degraded performance

In 524f655, Turnos 24x7 (https://reservas-dev.alternativasinteligentes.com/) experienced degraded performance:

HTTP code: 200
Response time: 1359 ms

Resolved: Turnos 24x7 performance has improved in 1285743.


How to load multi-bot at the same time?

Hi all,
I would like to know if there is a way to load multi- bot at the same time.
Thanks

Hey @Asma-droid any updates ???on how to load multi-bot on same time


[Git] Cannot pull the changes from remote Github repository.

There is only "fetch" function but no "pull" function. The command "git pull" doesn't work.
In order to get the latest changes in the file, I deleted the local repository and cloned it again.
The experience will be better if this is fixed. Thanks!

I did the workaround and it worked. But for those like me who are comfortable using the git commands on the terminal, the experience on the app will be better if this a part of the enhancement. Thanks!

I understand and it's being working on.

Pull is now available.


Refactor unchecked retval to work with newer version of laser

This detection module depends on an older version of laser, so it should be refactored to work with the newer version


[SPARK-21485][FOLLOWUP][SQL][DOCS] Describes examples and arguments separately, and note/since in SQL built-in function documentation

What changes were proposed in this pull request?
This PR proposes to separate extended into examples and arguments internally so that both can be separately documented and add since and note for additional information.
For since, it looks users sometimes get confused by, up to my knowledge, missing version information. For example, see<EMAIL_ADDRESS>For few good examples to check the built documentation, please see both:
from_json - https://spark-test.github.io/sparksqldoc/#from_json
like - https://spark-test.github.io/sparksqldoc/#like
For DESCRIBE FUNCTION, note and since are added as below:
> DESCRIBE FUNCTION EXTENDED rlike;
...
Extended Usage:
    Arguments:
      ...

    Examples:
      ...

    Note:
      Use LIKE to match with simple string pattern

> DESCRIBE FUNCTION EXTENDED to_json;
...
    Examples:
      ...

    Since: 2.2.0

For the complete documentation, see https://spark-test.github.io/sparksqldoc/
How was this patch tested?
Manual tests and existing tests. Please see https://spark-test.github.io/sparksqldoc
Jenkins tests are needed to double check

Test build #79999 has started for PR 18749 at commit 0958c0b.

Test build #79999 has finished for PR 18749 at commit 0958c0b.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/79999/
Test FAILed.

Test build #80002 has started for PR 18749 at commit d9277bf.

Test build #80003 has started for PR 18749 at commit cb2dfe7.

Test build #80004 has started for PR 18749 at commit 54e6d82.

Test build #80002 has finished for PR 18749 at commit d9277bf.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80002/
Test FAILed.

Test build #80003 has finished for PR 18749 at commit cb2dfe7.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80003/
Test FAILed.

Merged build finished. Test FAILed.

Test build #80004 has finished for PR 18749 at commit 54e6d82.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80004/
Test PASSed.

cc @rxin, @srowen and @cloud-fan, I believe this one is ready for a review. Could you take a look when you have some time?

Will address comments within few days. (I am reading docs just to get used to things around my updated status)

Test build #80043 has started for PR 18749 at commit bf48875.

Test build #80044 has started for PR 18749 at commit f51ee74.

Test build #80044 has finished for PR 18749 at commit f51ee74.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test build #80043 has finished for PR 18749 at commit bf48875.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80044/
Test PASSed.

Merged build finished. Test PASSed.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80043/
Test PASSed.

Test build #80111 has started for PR 18749 at commit 389fc6e.

For source compatibility, in the commit, https://github.com/apache/spark/pull/18749/commits/389fc6ef788bf971f846ca36f49cea6a1c98b0d0, I tried to move back to extended to show it passes the tests and keep the source compatibility.
For binary compatibility, I tested in the way I described before - https://github.com/databricks/scala-style-guide/issues/46.
With ExpressionDescription.java assuming this is Spark 2.2.0:
import java.lang.annotation.Retention;
import java.lang.annotation.RetentionPolicy;
@Retention(RetentionPolicy.RUNTIME)
public @interface ExpressionDescription {
    String usage() default "";
    String extended() default "";
}

With Main.scala assuming this is the user application compiled with Spark 2.2.0:
@ExpressionDescription(
  usage = "I am usage",
  extended = """
    I am extended
  """)
case class A()

object Main {
  def main(args: Array[String]): Unit = {
    val df = scala.reflect.classTag[A].runtimeClass.getAnnotation(classOf[ExpressionDescription]).
    println(df.usage())
    println(df.extended())
  }
}

javac ExpressionDescription.java
scalac Main.scala
scala Main

prints
I am usage

    I am extended

And then, I changed ExpressionDescription.java assuming we merged this change into Spark's next release:
 import java.lang.annotation.Retention;
 import java.lang.annotation.RetentionPolicy;
 @Retention(RetentionPolicy.RUNTIME)
 public @interface ExpressionDescription {
     String usage() default "";
     String extended() default "";
+    String arguments() default "";
+    String examples() default "";
+    String note() default "";
+    String since() default "";
 }

and then I ran
javac ExpressionDescription.java
scala Main

this looks working fine as below:
I am usage

    I am extended

I will revert 389fc6e if the test passes.

Test build #80113 has started for PR 18749 at commit f76af78.

Test build #80111 has finished for PR 18749 at commit 389fc6e.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80111/
Test FAILed.

Merged build finished. Test FAILed.

The test failure above is due to extended being null. I also allowed this case in f76af78415085cff1f1d6dd31cb97d464b4fa52b.

Test build #80115 has started for PR 18749 at commit 980ede7.

Test build #80113 has finished for PR 18749 at commit f76af78.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80113/
Test FAILed.

Test build #80116 has started for PR 18749 at commit 1fa02c8.

Test build #80115 has finished for PR 18749 at commit 980ede7.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80115/
Test PASSed.

Test build #80116 has finished for PR 18749 at commit 1fa02c8.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80116/
Test PASSed.

Test build #80118 has started for PR 18749 at commit b037592.

Now I am pretty confident for the compatibility concern given:

the commit, https://github.com/apache/spark/commit/389fc6ef788bf971f846ca36f49cea6a1c98b0d0 (and with a little additional change, 1fa02c8), where I intendedly left extendeds as are in ExpressionDescription and ExpressionInfo usage, instead of setting new examples and arguments by the change proposal here to check the source compatibility.

the manual tests, https://github.com/apache/spark/pull/18749#issuecomment-319286575, above to check binary compatibility.

I am quite sure if the current state should be ready for another look if the last test passes, where I reverted the former, 389fc6e, above. I guess it should pass because the only diff is 1fa02c8 but will wait for the results before pinging again.

Test build #80118 has finished for PR 18749 at commit b037592.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80118/
Test FAILed.

retest this please

Test build #80123 has started for PR 18749 at commit b037592.

Test build #80123 has finished for PR 18749 at commit b037592.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80123/
Test PASSed.

Merged build finished. Test PASSed.

@srowen, @rxin and @cloud-fan, I am confident for the compatibility concern per https://github.com/apache/spark/pull/18749#issuecomment-319364607 and believe it is ready for another look.

What is the compatibility concern?

Here, both comments by Sean, https://github.com/apache/spark/pull/18749#discussion_r129929153 and https://github.com/apache/spark/pull/18749#discussion_r129927520.
It looks we are okay to change this given https://github.com/apache/spark/pull/18749#discussion_r129802019 but it is said in the comment, "DeveloperApi". So, I tried to keep the compatibility at my best.
So, I tried to think both possible compatibility cases:

Checking If existing usage by developer still works with this change:
 @ExpressionDescription(
    usage = "...",
    extended = """
      ...
    """)

The current PR changes extended to examples and arguments in its usage. So, I manually reverted this usage and checked if it passes the test.

Checking binary compatibility by annotation. I added few element in this PR, examples, arguments, note and since.  I manually checked this in https://github.com/apache/spark/pull/18749#issuecomment-319286575.

Did I maybe misunderstand something?

OK great. I think we should avoid breaking developer APIs, unless it has a huge upside. It wouldn't be fun to break it just for some cosmetic things ...

Will keep in mind that.

@rxin, does this look okay to you too?

seems fine to me.

Will go merging this one. Thanks for reviewing this @srowen and @rxin.

Before merging the PR, you have to wait for another committer to say LGTM. I think this is still required.

I think @srowen did it here using the new github approval: srowen approved these changes 20 hours ago
@srowen might be better if we stick with the LGTM one.

https://spark-prs.appspot.com does not show GITHUB approval. If we can put LGTM explicitly, it will help us track the progress.

I think we should rather make https://spark-prs.appspot.com recognising the github approval as well .. I considered github approval as an approval for this patch.
BTW, for now, is it documented that "LGTM" is required somewhere?

It is documented: http://spark.apache.org/contributing.html
It's been the convention forever and it's also good to use one way rather than multiple, so I'd prefer us just using that ... until we have a compelling reason to change.

Yes.

I understood Spark have used LGTM as convention and it is a good way to show an approval as a sign-off but I meant, is "LGTM", not any other methods, required before merging it?

What's your point? You should be able to merge PR without anybody reviewing?

I was wondering if other methods such as SGTM or a Github approval aa an approval for a patch are not allowed by rule. I usually say based on documentation or references to other guys and I read documentation a lot really but it wasn't in my head.. Just want to be sure and follow the rule. I am asking this really only because I am curious and want to be sure.

Ah OK. That's what we are discussing here. In the past it has always been an explicit "LGTM". That was defined before github had even the approval feature. Now most committers are actually not ASF github org members so they don't even have the permission to use this approve feature, and for whatever legacy reason almost everybody I know (except Sean) uses explicit LGTM. We also have tooling that checks the LGTM.
So rather than complicating tooling or changing everybody's behavior, I was suggesting to @srowen maybe he should just use LGTM.

I see. Thanks for the details and explanation.

Formally, our model is "Commit Then Review". No approval or vote is required for any change, but changes can be retroactively vetoed. https://www.apache.org/foundation/glossary.html#CommitThenReview
Of course, we don't actually just commit things and then see what people think. But voting on every change is infeasible. It is a judgment call. My decision depends on things like: do I believe in good faith that any committer would be surprised if I merged this? are they likely to want to review first? am I confident enough to take on the consequence of fixing things if this causes a problem? Hence I leave changes open longer and ping more people the bigger the change is. Eventually, you get feedback from everyone who cares and tacit consent from anyone who hasn't commented.
Can you merge a change that nobody else has explicitly approved? yes, but, would only do so if it's trivial or if you have asked for a while for input and nobody has given any.
"LGTM" is not a formal mechanism or vote, and that text doesn't say it is. It's there to help contributors understand that's a common way to indicate approval.
I didn't realize that only ASF members can use the "Approve/Comment/Request Changes" feature. I prefer it just because it renders more nicely and doesn't generate an email. I see no reason to prefer that or "LGTM" or "SGTM" or "+1" or whatever. Any clear indication of approval is equivalent; these are just English words, not a formal vote. I am happy to update the doc to that effect.

Actually Sean I disagree. Spark has always been review then commit from the days before it entered ASF. In a huge debate last year within the ASF on RTC vs CTR, Spark was cited as a prominent example. Sometimes there are tiny teeny patches that committers can use their own judgements and don't necessarily require somebody else to sign-off.

RTC means a vote happens for each change: https://www.apache.org/foundation/glossary.html#ReviewThenCommit
That's not what we do. What debate are you referring to?

(BTW, just for clarification, I think anyone can use that approve feature. I did it before - https://github.com/apache/spark/pull/17734)

@srowen search for "RTC vs CTR (was: Concerning Sentry...)"
From Todd Lipcon:
I don't have incubator stats... nor do I have a good way to measure "most
active" or "most successful" projects in the ASF (seems that itself could
be a 'centithread'-worthy discussion). But a potential proxy could be the
number of stars on github:
https://github.com/search?utf8=%E2%9C%93&q=user%3Aapache&type=Repositories&ref=searchresults
 (sort by number of stars)

Of the top ten:

Spark: RTC via github pull request
Storm: RTC (https://storm.apache.org/documentation/BYLAWS.html see "Code
Change")
Cassandra: RTC (based on my skimming the commit log which has "Reviewed by"
quite often)
CouchDB: RTC (http://couchdb.apache.org/bylaws.html see "RTC" section)
Kafka: RTC (based on "Reviewed by" showing up in recent commit logs)
Thrift: CTR
Mesos: RTC (based on reviewboard links in most of the recent commits)
Zookeeper: RTC (based on personal experience and comments above in this
thread)
Cordova: CTR (based on
https://github.com/apache/cordova-coho/blob/master/docs/committer-workflow.md
)
Hadoop: RTC (based on personal experience)

Briefly looking through the #11 through #30 projects I also see a
substantial number which operate on RTC (and others for which I don't know)

So, I don't think there's much evidence that RTC prevents a project from
becoming successful in the eyes of the developer community. Also worth
noting that several of these are relatively new TLPs (i.e. within the last
~3 years) whereas others are quite old but still active and successful.

BTW I didn't realize (and neither did Todd) ASF's definition of "RTC" is min 3 vote consensus, which is pretty odd.
The convention has always been find somebody who understands the area to review and give explicit LGTM. There are some exceptions like tiny changes (basically very similar to your paragraph on judgement call).

@HyukjinKwon you weren't a committer before :)

Yes, this isn't RTC. It isn't even RTC with 1-vote consensus, because you rightly say that you could merge with no other votes if it were obviously not required. But whatever. We can pick the process we want, and the name isn't important. I agree with your take and I think that's already the current process.
This change was clearly reviewed by several other people, so I don't see an issue with merging. If the objection was, "you didn't literally write 'LGTM'" then no I don't agree that this is important, and not a convention I've seen observed consistently. Think about the implication: someone says "yeah this looks good" and then you block for a day begging them to come back and write 'LGTM'?

Test build #80248 has started for PR 18749 at commit 974eab2.

Test build #80248 has finished for PR 18749 at commit 974eab2.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80248/
Test FAILed.

retest this please

Test build #80250 has started for PR 18749 at commit 974eab2.

Test build #80250 has finished for PR 18749 at commit 974eab2.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80250/
Test FAILed.

Merged build finished. Test FAILed.

retest this please

Test build #80253 has started for PR 18749 at commit 974eab2.

We have to define a clear rule. We do not want to revert the PRs merged by others. It just makes others awkward.
In the past, based on my observation in the Spark SQL, when the committers left SGTM or looks good to me, it does not mean the quality is good enough for merging. That only means the quality or solution looks OK but needs more reviews/changes. I am not sure how the other Spark components work. However, I believe this is the rule we follow in Spark SQL. That is why I am surprised some committers merge the PR without an explicit LGTM message.

We have never had such a rule here or in any other project. Let's use common sense. If someone says 'looks good' that's fine. Or anything equivalent. If in doubt ask.

In Spark SQL, we require such an explicit message. That is my understanding. If we want a change, I think we need to send a note to all the committers and let them know it. Then, they will leave such messages more carefully.
Spark SQL becomes more and more complex. It is very easy to break the backward compatibility or even return an incorrect result. We are building infrastructure software. We have to be more careful, because our current test case coverage is still not good enough.

@gatorsmile, I really don't want to go through your PRs and I have not ever done such things i the past. Let's document this and then let me follow. Please open a discussion in a mailing list if you are in doubt. We are not supposed to make a long term decision.

@gatorsmile you are the one asking for a change, and I do not see support for it. I am not aware of any Spark SQL-specific rule; what are you referring to? Reynold agrees above, for example, that in some cases it's justified to merge a change with no other review. This alone suggests there is no rule about typing "LGTM".
You rightly say that things need review. The important change, the more it needs review. That is not an argument for a voting rule; it's an argument for good judgment among committers, and I see no evidence that's lacking. An "LGTM" rule doesn't solve that problem: a committer with bad judgment can always approve something for merging that shouldn't, right?
I further can't understand what's special about "LGTM". You are saying that committers say "sounds good to me" when they mean "this is not ready for merging" but whenever they say "LGTM" they always mean "this is ready for merging" -- sorry, what?
You are suggesting a change to a form of RTC, which would require a PMC vote. Consider the implications: nobody can merge a change until a vote completes. Are you sure?
In the meantime, come now, let's move ahead with this PR, which was obviously reviewed.

@srowen that's not what I said. Almost always an explicit LGTM is preferred. There are tiny changes that might not require them, and it is up to the judgement of the committer. But those are more exceptions than the norm.

Yep, I agree with 'almost always', and tiny changes might not require them. I think that's what I said you said? "some cases". See also https://github.com/apache/spark/pull/18749#issuecomment-319892145
But this alone disagrees with the idea that all changes need the string "LGTM" typed.
I am not sure why this popped up, but I propose we continue with the same process and conventions we always have. If anyone's unsure about whether an important review is affirmative: please ask.
Can we put this to bed now?

Test build #80253 has finished for PR 18749 at commit 974eab2.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80253/
Test FAILed.

retest this please

Test build #80261 has started for PR 18749 at commit 974eab2.

I am also afraid somebody might misunderstand what I or a few other committers say SGTM or looks good in Spark SQL. When a committer tries to merge Spark SQL related PRs based on these messages, please double checks. Does this sound reasonable?

Test build #80261 has finished for PR 18749 at commit 974eab2.

This patch fails PySpark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

I think of opening a discussion in the mailing list if you are suggesting something. I don't think we should talk about this here.

retest this please

Test build #80274 has started for PR 18749 at commit 974eab2.

Test build #80274 has finished for PR 18749 at commit 974eab2.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds no public classes.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80274/
Test FAILed.

retest this please

Test build #80282 has started for PR 18749 at commit 974eab2.

Test build #80282 has finished for PR 18749 at commit 974eab2.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/80282/
Test PASSed.

Other test failures look spurious and unrelated. I guess we are okay to go ahead with this PR anyway?

LGTM.
Thanks! Merging to master.


Add ignored tests

Fixes #852
Test Plan

How do we know the code works?
.

Ignored test should't shows on FTL
Checklist

[ ] Documented
[ ] Unit tested
[ ] release_notes.md updated
[X] Add ignored tests to test app

Codecov Report

Merging #853 into master will decrease coverage by 0.12%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##             master     #853      +/-   ##
============================================
- Coverage     81.39%   81.27%   -0.13%
+ Complexity      638      637       -1
============================================
  Files           167      167
  Lines          3257     3257
  Branches        468      468
============================================
- Hits           2651     2647       -4
- Misses          342      343       +1
- Partials        264      267       +3


The signature submitted in claim() can be reused multiple times

The signature in claim() refers only to the destination address.
So, once a valid signature has been published for a specific destination, It can be reused to claim all the funds for any Id where funds[Id].signer is the same signer.
I am not sure that it is or not the intention of the developper, but we can have N send() from one signer, then 1 claim() with its signature and we can generate immediately the N-1 claim() to the same destination.
I propose to sign keccak256(Id, address) to prevent this replay attack.

I do not think it's a replay attack for the scope of this contract. It is a type of vault, so it is correct to have access to the funds where you are a signer.
My doubt is about what happens when it expires. It is not clear. Up to now it looks like it remains locked in the contract.

I confirm that there is a replay attack.
Let H be a holder and C be the claimer.

H calls send(id1, sig1) where sig1 has been signed by himself
H signs keccak256(address(C)) = sig2 and publishes sig2 offline
Someone (C ?) calls Claim(id1, sig2, address(C))
if (sig1and sig2) are signed by H, then transfer(some ETH) to C

Later, H wants to reuse the wallet but to transfer funds to Z. C is not in the process.
5. H calls send(id2, sig3) where sig3 has been signed by himself
6. C has observed the previous tx and calls Claim(id2, sig2, address(C)) immediately
7. if (sig3 and sig2) are signed by H (this is the case), then transfer(some ETH) to C.
At step 6, C replays sig2 that was part of the previous cycle, and steals the funds of Z.
It means that each time H wants to reuse the wallet, C will take the funds by replaying sig2 again and again.

Ok, I agree. It is a replay attack and a possible case for this contract. This contract should have similar mechanisms to an EOA. It should have a nonce that increases on every send transaction.

Just doubled up the bounty on the audit and I want to make sure we reward the active audit of the contract. @riusricardo and @catageek could you guys him me up on Twitter or Telegram @austingriffith so I can make direct contact?

I'm ktageek on twitter (not catageek, already taken). Following you now.


Build on OpenBSD fails, it's about libcppnet's use of Boost asio. Can you fix/provide pointers please?

Hi!
I am trying to build cppnetlib as follows: wget http://downloads.cpp-netlib.org/0.12.0/cpp-netlib-0.12.0-final.tar.gz; tar xvfz cpp-netlib*.tar.gz; cd cpp-netlib*; cd cpp-netlib*; CC=eg++ CXX=eg++ CXXFLAGS="-pthreads" cmake .; make
cppnetlib depends on asio. asio as downloaded from http://think-async.com/ /  https://sourceforge.net/projects/asio/files/asio/1.10.6 (Stable)/asio-1.10.6.tar.gz/download does NOT build on OpenBSD, BUT Boost bundles asio, and that one is located in "/usr/local/include/boost/asio/", and, the cppnetlib build process does try to use that one.
I'm trying to understand why libcppnet's Boost asio use fails. Find the build failure log below here.
If I at least would understand the nature of the problem, I could try other build parameters or the like, e.g. the STDC++X11 support is not switched on and that's the problem, or whatever.
Can you please explain why it not worked, and provide any pointers to how I can make it build?
Thanks!
$ eg++ --version
eg++ (GCC) 4.9.3
$ CC=eg++ CXX=eg++ CXXFLAGS="-pthreads" cmake .; make
-- Boost version: 1.58.0
-- Configuring done
-- Generating done
-- Build files have been written to: /home/MYUSER/cpp-netlib-0.12.0-final
/usr/local/bin/cmake -H/home/MYUSER/cpp-netlib-0.12.0-final -B/home/MYUSER/cpp-netlib-0.12.0-final --check-build-system CMakeFiles/Makefile.cmake 0
/usr/local/bin/cmake -E cmake_progress_start /home/MYUSER/cpp-netlib-0.12.0-final/CMakeFiles /home/MYUSER/cpp-netlib-0.12.0-final/CMakeFiles/progress.marks
make -f CMakeFiles/Makefile2 all
make -f libs/network/src/CMakeFiles/cppnetlib-server-parsers.dir/build.make libs/network/src/CMakeFiles/cppnetlib-server-parsers.dir/depend
cd /home/MYUSER/cpp-netlib-0.12.0-final && /usr/local/bin/cmake -E cmake_depends "Unix Makefiles" /home/MYUSER/cpp-netlib-0.12.0-final /home/MYUSER/cpp-netlib-0.12.0-final/libs/network/src /home/MYUSER/cpp-netlib-0.12.0-final /home/MYUSER/cpp-netlib-0.12.0-final/libs/network/src /home/MYUSER/cpp-netlib-0.12.0-final/libs/network/src/CMakeFiles/cppnetlib-server-parsers.dir/DependInfo.cmake --color=
make -f libs/network/src/CMakeFiles/cppnetlib-server-parsers.dir/build.make libs/network/src/CMakeFiles/cppnetlib-server-parsers.dir/build
[  2%] Built target cppnetlib-server-parsers
make -f libs/network/src/CMakeFiles/cppnetlib-client-connections.dir/build.make libs/network/src/CMakeFiles/cppnetlib-client-connections.dir/depend
cd /home/MYUSER/cpp-netlib-0.12.0-final && /usr/local/bin/cmake -E cmake_depends "Unix Makefiles" /home/MYUSER/cpp-netlib-0.12.0-final /home/MYUSER/cpp-netlib-0.12.0-final/libs/network/src /home/MYUSER/cpp-netlib-0.12.0-final /home/MYUSER/cpp-netlib-0.12.0-final/libs/network/src /home/MYUSER/cpp-netlib-0.12.0-final/libs/network/src/CMakeFiles/cppnetlib-client-connections.dir/DependInfo.cmake --color=
make -f libs/network/src/CMakeFiles/cppnetlib-client-connections.dir/build.make libs/network/src/CMakeFiles/cppnetlib-client-connections.dir/build
[  3%] Building CXX object libs/network/src/CMakeFiles/cppnetlib-client-connections.dir/client.cpp.o
cd /home/MYUSER/cpp-netlib-0.12.0-final/libs/network/src && /usr/local/bin/eg++   -DASIO_HEADER_ONLY -DBOOST_NETWORK_ENABLE_HTTPS -DBOOST_SPIRIT_THREADSAFE -DBOOST_TEST_DYN_LINK -I/usr/local/include -I/home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include -I/home/MYUSER/cpp-netlib-0.12.0-final  -Wall -std=c++11   -o CMakeFiles/cppnetlib-client-connections.dir/client.cpp.o -c /home/MYUSER/cpp-netlib-0.12.0-final/libs/network/src/client.cpp
In file included from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/error_code.hpp:185:0,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/scheduler.hpp:20,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/system_executor.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/associated_executor.hpp:21,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/bind_handler.hpp:20,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/wrapped_handler.hpp:18,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/io_service.hpp:24,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/basic_io_object.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/basic_socket_acceptor.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/ip/tcp.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/boost/network/protocol/http/client/connection/normal_delegate.ipp:12,
from /home/MYUSER/cpp-netlib-0.12.0-final/libs/network/src/client.cpp:13:
/home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/impl/error_code.ipp:40:15: error: looser throw specifier for 'virtual const char* asio::detail::system_category::name() const'
const char* name() const ASIO_ERROR_CATEGORY_NOEXCEPT
^
In file included from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/error_code.hpp:21:0,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/scheduler.hpp:20,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/system_executor.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/associated_executor.hpp:21,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/bind_handler.hpp:20,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/wrapped_handler.hpp:18,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/io_service.hpp:24,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/basic_io_object.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/basic_socket_acceptor.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/ip/tcp.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/boost/network/protocol/http/client/connection/normal_delegate.ipp:12,
from /home/MYUSER/cpp-netlib-0.12.0-final/libs/network/src/client.cpp:13:
/usr/local/include/c++/4.9.3/system_error:81:5: error:   overriding 'virtual const char* std::error_category::name() const noexcept'
name() const noexcept = 0;
^
In file included from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/error.hpp:349:0,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/impl/pipe_select_interrupter.ipp:33,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/pipe_select_interrupter.hpp:80,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/select_interrupter.hpp:27,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/kqueue_reactor.hpp:32,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/reactor.hpp:23,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/impl/scheduler.ipp:22,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/scheduler.hpp:183,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/system_executor.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/associated_executor.hpp:21,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/bind_handler.hpp:20,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/wrapped_handler.hpp:18,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/io_service.hpp:24,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/basic_io_object.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/basic_socket_acceptor.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/ip/tcp.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/boost/network/protocol/http/client/connection/normal_delegate.ipp:12,
from /home/MYUSER/cpp-netlib-0.12.0-final/libs/network/src/client.cpp:13:
/home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/impl/error.ipp:34:15: error: looser throw specifier for 'virtual const char* asio::error::detail::netdb_category::name() const'
const char* name() const ASIO_ERROR_CATEGORY_NOEXCEPT
^
In file included from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/error_code.hpp:21:0,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/scheduler.hpp:20,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/system_executor.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/associated_executor.hpp:21,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/bind_handler.hpp:20,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/wrapped_handler.hpp:18,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/io_service.hpp:24,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/basic_io_object.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/basic_socket_acceptor.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/ip/tcp.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/boost/network/protocol/http/client/connection/normal_delegate.ipp:12,
from /home/MYUSER/cpp-netlib-0.12.0-final/libs/network/src/client.cpp:13:
/usr/local/include/c++/4.9.3/system_error:81:5: error:   overriding 'virtual const char* std::error_category::name() const noexcept'
name() const noexcept = 0;
^
In file included from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/error.hpp:349:0,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/impl/pipe_select_interrupter.ipp:33,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/pipe_select_interrupter.hpp:80,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/select_interrupter.hpp:27,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/kqueue_reactor.hpp:32,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/reactor.hpp:23,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/impl/scheduler.ipp:22,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/scheduler.hpp:183,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/system_executor.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/associated_executor.hpp:21,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/bind_handler.hpp:20,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/wrapped_handler.hpp:18,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/io_service.hpp:24,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/basic_io_object.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/basic_socket_acceptor.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/ip/tcp.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/boost/network/protocol/http/client/connection/normal_delegate.ipp:12,
from /home/MYUSER/cpp-netlib-0.12.0-final/libs/network/src/client.cpp:13:
/home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/impl/error.ipp:66:15: error: looser throw specifier for 'virtual const char* asio::error::detail::addrinfo_category::name() const'
const char* name() const ASIO_ERROR_CATEGORY_NOEXCEPT
^
In file included from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/error_code.hpp:21:0,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/scheduler.hpp:20,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/system_executor.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/associated_executor.hpp:21,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/bind_handler.hpp:20,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/wrapped_handler.hpp:18,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/io_service.hpp:24,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/basic_io_object.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/basic_socket_acceptor.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/ip/tcp.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/boost/network/protocol/http/client/connection/normal_delegate.ipp:12,
from /home/MYUSER/cpp-netlib-0.12.0-final/libs/network/src/client.cpp:13:
/usr/local/include/c++/4.9.3/system_error:81:5: error:   overriding 'virtual const char* std::error_category::name() const noexcept'
name() const noexcept = 0;
^
In file included from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/error.hpp:349:0,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/impl/pipe_select_interrupter.ipp:33,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/pipe_select_interrupter.hpp:80,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/select_interrupter.hpp:27,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/kqueue_reactor.hpp:32,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/reactor.hpp:23,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/impl/scheduler.ipp:22,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/scheduler.hpp:183,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/system_executor.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/associated_executor.hpp:21,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/bind_handler.hpp:20,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/wrapped_handler.hpp:18,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/io_service.hpp:24,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/basic_io_object.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/basic_socket_acceptor.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/ip/tcp.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/boost/network/protocol/http/client/connection/normal_delegate.ipp:12,
from /home/MYUSER/cpp-netlib-0.12.0-final/libs/network/src/client.cpp:13:
/home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/impl/error.ipp:96:15: error: looser throw specifier for 'virtual const char* asio::error::detail::misc_category::name() const'
const char* name() const ASIO_ERROR_CATEGORY_NOEXCEPT
^
In file included from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/error_code.hpp:21:0,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/scheduler.hpp:20,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/system_executor.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/associated_executor.hpp:21,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/bind_handler.hpp:20,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/wrapped_handler.hpp:18,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/io_service.hpp:24,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/basic_io_object.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/basic_socket_acceptor.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/ip/tcp.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/boost/network/protocol/http/client/connection/normal_delegate.ipp:12,
from /home/MYUSER/cpp-netlib-0.12.0-final/libs/network/src/client.cpp:13:
/usr/local/include/c++/4.9.3/system_error:81:5: error:   overriding 'virtual const char* std::error_category::name() const noexcept'
name() const noexcept = 0;
^
In file included from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/ssl/error.hpp:65:0,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/ssl/impl/context.ipp:25,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/ssl/context.hpp:755,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/ssl.hpp:18,
from /home/MYUSER/cpp-netlib-0.12.0-final/boost/network/protocol/http/client/connection/ssl_delegate.ipp:12,
from /home/MYUSER/cpp-netlib-0.12.0-final/libs/network/src/client.cpp:16:
/home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/ssl/impl/error.ipp:32:15: error: looser throw specifier for 'virtual const char* asio::error::detail::ssl_category::name() const'
const char* name() const ASIO_ERROR_CATEGORY_NOEXCEPT
^
In file included from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/error_code.hpp:21:0,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/scheduler.hpp:20,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/system_executor.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/associated_executor.hpp:21,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/bind_handler.hpp:20,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/wrapped_handler.hpp:18,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/io_service.hpp:24,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/basic_io_object.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/basic_socket_acceptor.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/ip/tcp.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/boost/network/protocol/http/client/connection/normal_delegate.ipp:12,
from /home/MYUSER/cpp-netlib-0.12.0-final/libs/network/src/client.cpp:13:
/usr/local/include/c++/4.9.3/system_error:81:5: error:   overriding 'virtual const char* std::error_category::name() const noexcept'
name() const noexcept = 0;
^
In file included from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/ssl/context.hpp:755:0,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/ssl.hpp:18,
from /home/MYUSER/cpp-netlib-0.12.0-final/boost/network/protocol/http/client/connection/ssl_delegate.ipp:12,
from /home/MYUSER/cpp-netlib-0.12.0-final/libs/network/src/client.cpp:16:
/home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/ssl/impl/context.ipp: In constructor 'asio::ssl::context::context(asio::ssl::context_base::method)':
/home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/ssl/impl/context.ipp:88:29: error: '::SSLv3_method' has not been declared
handle_ = ::SSL_CTX_new(::SSLv3_method());
^
/home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/ssl/impl/context.ipp:91:29: error: '::SSLv3_client_method' has not been declared
handle_ = ::SSL_CTX_new(::SSLv3_client_method());
^
/home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/ssl/impl/context.ipp:94:29: error: '::SSLv3_server_method' has not been declared
handle_ = ::SSL_CTX_new(::SSLv3_server_method());
^
In file included from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/impl/pipe_select_interrupter.ipp:33:0,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/pipe_select_interrupter.hpp:80,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/select_interrupter.hpp:27,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/kqueue_reactor.hpp:32,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/reactor.hpp:23,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/impl/scheduler.ipp:22,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/scheduler.hpp:183,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/system_executor.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/associated_executor.hpp:21,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/bind_handler.hpp:20,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/detail/wrapped_handler.hpp:18,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/io_service.hpp:24,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/basic_io_object.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/basic_socket_acceptor.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/ip/tcp.hpp:19,
from /home/MYUSER/cpp-netlib-0.12.0-final/boost/network/protocol/http/client/connection/normal_delegate.ipp:12,
from /home/MYUSER/cpp-netlib-0.12.0-final/libs/network/src/client.cpp:13:
/home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/error.hpp: At global scope:
/home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/error.hpp:256:36: warning: 'asio::error::system_category' defined but not used [-Wunused-variable]
static const asio::error_category& system_category
^
/home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/error.hpp:258:36: warning: 'asio::error::netdb_category' defined but not used [-Wunused-variable]
static const asio::error_category& netdb_category
^
/home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/error.hpp:260:36: warning: 'asio::error::addrinfo_category' defined but not used [-Wunused-variable]
static const asio::error_category& addrinfo_category
^
/home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/error.hpp:262:36: warning: 'asio::error::misc_category' defined but not used [-Wunused-variable]
static const asio::error_category& misc_category
^
In file included from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/ssl/impl/context.ipp:25:0,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/ssl/context.hpp:755,
from /home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/ssl.hpp:18,
from /home/MYUSER/cpp-netlib-0.12.0-final/boost/network/protocol/http/client/connection/ssl_delegate.ipp:12,
from /home/MYUSER/cpp-netlib-0.12.0-final/libs/network/src/client.cpp:16:
/home/MYUSER/cpp-netlib-0.12.0-final/deps/asio/asio/include/asio/ssl/error.hpp:33:36: warning: 'asio::error::ssl_category' defined but not used [-Wunused-variable]
static const asio::error_category& ssl_category
^
*** Error 1 in . (libs/network/src/CMakeFiles/cppnetlib-client-connections.dir/build.make:66 'libs/network/src/CMakeFiles/cppnetlib-client-connections.dir/client.cpp.o')
*** Error 1 in . (CMakeFiles/Makefile2:130 'libs/network/src/CMakeFiles/cppnetlib-client-connections.dir/all')
*** Error 1 in /home/MYUSER/cpp-netlib-0.12.0-final (Makefile:142 'all')

0.12.0 does not use Boost.ASIO. That version uses the standalone ASIO, which you can get either from:

getting the submodules that cpp-netlib depends on
getting it from http://think-async.com/ (or https://github.com/chriskohlhoff/asio)


Add necessary changes to apim-pre-release branch to support pre-release versions

Fixed by following PRs

https://github.com/wso2/testgrid/pull/1416
https://github.com/wso2/testgrid/pull/1417
https://github.com/wso2/testgrid/pull/1418
https://github.com/wso2/testgrid/pull/1419
https://github.com/wso2/testgrid/pull/1420
https://github.com/wso2/testgrid/pull/1421


cmd/pprof: pprof create profile directory under the root dir, not %USERPROFILE% on windows

Please answer these questions before submitting your issue. Thanks!
What version of Go are you using (go version)?
go version go1.7.3 windows/amd64
What operating system and processor architecture are you using (go env)?
set GOARCH=amd64
set GOBIN=
set GOEXE=.exe
set GOHOSTARCH=amd64
set GOHOSTOS=windows
set GOOS=windows
set GOPATH=
set GORACE=
set GOROOT=C:\Go
set GOTOOLDIR=C:\Go\pkg\tool\windows_amd64
set CC=gcc
set GOGCCFLAGS=-m64 -mthreads -fmessage-length=0 -fdebug-prefix-map=C:\Users\Hiroshi\AppData\Local\Temp\go-build623875630=/tmp/go-build -gno-record-gcc-switches
set CXX=g++
set CGO_ENABLED=1

What did you do?
If possible, provide a recipe for reproducing the error.
A complete runnable program is good.
A link on play.golang.org is best.
run go tool pprof mybin on cmd.exe.
What did you expect to see?
profile directory should not be created on the root directory.
What did you see instead?
C:\Users\Hiroshi\work>dir C:\pprof
 Volume in drive C is Windows10_OS
 Volume Serial Number is 6203-7069

 Directory of C:\pprof

01/31/2017  01:08 PM    <DIR>          .
01/31/2017  01:08 PM    <DIR>          ..
               0 File(s)              0 bytes
               2 Dir(s)  10,739,838,976 bytes free

I suggest you wait for the merge from upstream pprof before submitting patches... I vaguely remember an issue about pprof's TMPDIRS and I think the mechanism has been fixed upstream.

Thank you for quick suggestion.
It seems google/pprof has the same issue.
https://github.com/google/pprof/blob/master/internal/driver/fetch.go#L220
Maybe I should make PR for google/pprof instead and wait for the merge.