TP Link Smartplug doesn’t seem to be working

Hi,
I can see the TP Link Smartplug plugin, but clicking on it, trying to « slide it », doesn’t seem to do anything. The plugin is working right from the Octoprint web interface, but I would like to be able to do the same in the OctoPod app.
Thank you.

Gaston,

The debug logging was already ON. From what I can seen in the log file, everything seems to be fine.

The actual “button” doesn’t seem to be a button at all: I could be clicking on it all day long and it wouldn’t do a thing. I’m not getting in feedback whatsoever.

As I said, I’m not getting any feedback from the app. Here’s a screenshot:

Hum, I tried to send you once with the screenshot and i got an email delivery error message. I’m trying to send the email again without the screenshot. Please tell me how to send you this screenshot correctly.
I can’t test it right now because I’m in the middle of a print job, but if you have suggestions, I will try them once it’s finished.
Thanks.
Jean-Francois Chabot

Capitaine
Equipe Extra-Life des Bionic Marmots|
Bionic Marmots Extra Life Team|
www.extra-life.org/participant/jfchabot

Le 19 déc. 2018 à 13:26, Gaston Dombiak<EMAIL_ADDRESS>a écrit :
Hi Hedrakk,
Couple of questions to gather more info and help troubleshoot this.
In OctoPrint, could you go to Settings -> TP-Link Smartplug and enable debug logging? Try again switching things on/off from OctoPod. Then go back to OctoPrint -> Settings -> Logging and paste here the content of the file "plugin_tplinksmartplug_debug.log"
When you try to turn off the switch from the app, do you get a confirmation dialog?
Are you getting a dialog after you clicked on turn on/off from the app saying something like "ailed to request to turn power on/off"?
Thanks,
Gaston
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Bonjour Jean-Francois,
If button is disabled then nothing will happen when you click on it which seems to be your case. Could you paste in here the content of the file plugin_tplinksmartplug_debug.log before and after you open OctoPod and go to the TP-Link Smartplugs page? I'm trying to see any log entries created when OctoPod requested the status of the plugs.
Buttons are disabled when OctoPod failed to get the status of the switch. Since state is unknown, to OctoPod, then we do not know if we should offer the option to turn it on or off. An improvement I could do is to display next to each plug any error message so we can troubleshoot things easier.
Merci,
Gaston (French name but don't speak French)

Thanks. That information helps. This part looks suspicious:

[2018-12-20 17:16:16,780] DEBUG: «
[1]Ê"system":{"get_sysinfo":{"err_code":0,"sw_ver":"1.2.5 Build 171206
Rel.085954","hw_ver":"1.0","type":"IOT.SMARTPLUGSWITCH","model":"HS110(US)",
"mac":"50:C7:BF:00:54:C2","deviceId":"8006470C5A65A52B396E8795E8CB52F716C1FE
EE","hwId":"60FF6B258734EA6880E186F8C96DDC61","fwId":"0000000000000000000000
0000000000","oemId":"FFF22CFF774A0B89F7624BFC6F50D5DE","alias":"Wanhao
Di3","dev_name":"Wi-Fi Smart Plug With Energy
Monitoring","icon_hash":"","relay_state":1,"on_time":183313,"active_mode":"n
one","feature":"TIM:ENE","updating":0,"rssi":-74,"led_off":0,"latitude":45.5
34626,"longitude":-73.939842}},"emeter":{"get_realtime":{"current":0.213500,
"voltage":120.206845,"power":14.224610,"total":7.583000,"err_code":0}}}

Look at the text after DEBUG:  and before "system". If that is the actual text then that is the problem since that is not valid JSON. Could you confirm this is not a copy/paste corruption but the actual text in the log file?
This is an example of what I have in my log

[2018-12-21 19:27:12,120] DEBUG: {'emeter': {'err_code': True}, 'system': {'get_sysinfo': {'relay_state': 3}}}

I would expect your entry in the log to look like this:

[2018-12-20 17:16:16,780] DEBUG: {"system":{"get_sysinfo":{"err_code":0,"sw_ver":"1.2.5 Build 171206
Rel.085954","hw_ver":"1.0","type":"IOT.SMARTPLUGSWITCH","model":"HS110(US)",
"mac":"50:C7:BF:00:54:C2","deviceId":"8006470C5A65A52B396E8795E8CB52F716C1FE
EE","hwId":"60FF6B258734EA6880E186F8C96DDC61","fwId":"0000000000000000000000
0000000000","oemId":"FFF22CFF774A0B89F7624BFC6F50D5DE","alias":"Wanhao
Di3","dev_name":"Wi-Fi Smart Plug With Energy
Monitoring","icon_hash":"","relay_state":1,"on_time":183313,"active_mode":"n
one","feature":"TIM:ENE","updating":0,"rssi":-74,"led_off":0,"latitude":45.5
34626,"longitude":-73.939842}},"emeter":{"get_realtime":{"current":0.213500,
"voltage":120.206845,"power":14.224610,"total":7.583000,"err_code":0}}}

If that is the actual text in the log file then I would recommend contacting the plugin developer and open an issue to see if that is corrupted JSON?
Could you check one more thing? Go to octoprint.log and paste here the entries for octoprint.plugins.tplinksmartplug. I wonder if there are 500 errors.
Thanks,
Gaston

I know, the code looks weird... it’s not the same when I look at it from Notepad++ and when I paste it in an email. It would be easier if I could simply attach the log file to this email. Is it possible? When I tried with a screenshot, it didn’t worked.
Jean-Francois Chabot

Capitaine
Equipe Extra-Life des Bionic Marmots|
Bionic Marmots Extra Life Team|
www.extra-life.org/participant/jfchabot

Le 21 déc. 2018 à 18:50, Gaston Dombiak<EMAIL_ADDRESS>a écrit :
Thanks. That information helps. This part looks suspicious:
[2018-12-20 17:16:16,780] DEBUG: «
[1]Ê"system":{"get_sysinfo":{"err_code":0,"sw_ver":"1.2.5 Build 171206
Rel.085954","hw_ver":"1.0","type":"IOT.SMARTPLUGSWITCH","model":"HS110(US)",
"mac":"50:C7:BF:00:54:C2","deviceId":"8006470C5A65A52B396E8795E8CB52F716C1FE
EE","hwId":"60FF6B258734EA6880E186F8C96DDC61","fwId":"0000000000000000000000
0000000000","oemId":"FFF22CFF774A0B89F7624BFC6F50D5DE","alias":"Wanhao
Di3","dev_name":"Wi-Fi Smart Plug With Energy
Monitoring","icon_hash":"","relay_state":1,"on_time":183313,"active_mode":"n
one","feature":"TIM:ENE","updating":0,"rssi":-74,"led_off":0,"latitude":45.5
34626,"longitude":-73.939842}},"emeter":{"get_realtime":{"current":0.213500,
"voltage":120.206845,"power":14.224610,"total":7.583000,"err_code":0}}}
Look at the text after DEBUG: and before "system". If that is the actual text then that is the problem since that is not valid JSON. Could you confirm this is not a copy/paste corruption but the actual text in the log file?
This is an example of what I have in my log
[2018-12-21 19:27:12,120] DEBUG: {'emeter': {'err_code': True}, 'system': {'get_sysinfo': {'relay_state': 3}}}
I would expect your entry in the log to look like this:
[2018-12-20 17:16:16,780] DEBUG: {"system":{"get_sysinfo":{"err_code":0,"sw_ver":"1.2.5 Build 171206
Rel.085954","hw_ver":"1.0","type":"IOT.SMARTPLUGSWITCH","model":"HS110(US)",
"mac":"50:C7:BF:00:54:C2","deviceId":"8006470C5A65A52B396E8795E8CB52F716C1FE
EE","hwId":"60FF6B258734EA6880E186F8C96DDC61","fwId":"0000000000000000000000
0000000000","oemId":"FFF22CFF774A0B89F7624BFC6F50D5DE","alias":"Wanhao
Di3","dev_name":"Wi-Fi Smart Plug With Energy
Monitoring","icon_hash":"","relay_state":1,"on_time":183313,"active_mode":"n
one","feature":"TIM:ENE","updating":0,"rssi":-74,"led_off":0,"latitude":45.5
34626,"longitude":-73.939842}},"emeter":{"get_realtime":{"current":0.213500,
"voltage":120.206845,"power":14.224610,"total":7.583000,"err_code":0}}}
If that is the actual text in the log file then I would recommend contacting the plugin developer and open an issue to see if that is corrupted JSON?
Could you check one more thing? Go to octoprint.log and paste here the entries for octoprint.plugins.tplinksmartplug. I wonder if there are 500 errors.
Thanks,
Gaston
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Have you tried dropping the file on the comment window as described in here: https://help.github.com/articles/file-attachments-on-issues-and-pull-requests/ ? If that does not work then I can give you my email

I'm replying from the desktop interface, on my laptop, it should be easier to attach any file. I was replying to you through my mail app... I guess github doesn't like attachments sent using email app.
Anyhow, here's the log file in question and the screen shot of OctoPod TPLink "not so button" button :)
By the way, even thought I'm printing and I'm in read-only, the button is the same whatever I'm printing or not.
I hope it will help.

plugin_tplinksmartplug_debug_Before_OctoPod_Launch.log
plugin_tplinksmartplug_debug_After_OctoPod_Launch.log

Yep, button is disabled so clicking on it does nothing. Could you attach your octoprint.log file? We can see there a little more about what happens in OctoPrint when the TP-Link plugin receives API calls. I think they will appear with this text octoprint.plugins.tplinksmartplug.
I think that I will add a text that displays the reason for being disabled. It will help users self-troubleshoot this problem.
Thanks for your patience.
Gaston

I agree. I won’t be able to send you the log file right now, I’m kinda busy with Holidays preparations. But I’m making a note to send you the file as soon as I can.
Jean-Francois Chabot

Capitaine
Equipe Extra-Life des Bionic Marmots|
Bionic Marmots Extra Life Team|
www.extra-life.org/participant/jfchabot

Le 23 déc. 2018 à 14:04, Gaston Dombiak<EMAIL_ADDRESS>a écrit :
Yep, button is disabled so clicking on it does nothing. Could you attach your octoprint.log file? We can see there a little more about what happens in OctoPrint when the TP-Link plugin receives API calls. I think they will appear with this text octoprint.plugins.tplinksmartplug.
I think that I will add a text that displays the reason for being disabled. It will help users self-troubleshoot this problem.
Thanks for your patience.
Gaston
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Here's the octoprint.log file
octoprint.log

The info that we need is not present in the log. When I swipe the panels in OctoPod and I get to the TPLink Smartplugs window, I get these 2 entries in octoprint.log:

2018-12-26 15:48:53,671 - tornado.access - INFO - 200 POST /api/plugin/tplinksmartplug (<IP_ADDRESS>) 10006.37ms
2018-12-26 15:48:53,672 - tornado.access - INFO - 200 POST /api/plugin/tplinksmartplug (<IP_ADDRESS>) 10006.69ms

I'm trying to look into the number before the POST to confirm that it's returning a 200 and not a 500. Let me know once you see the POST /api/plugin/tplinksmartplug entries in the log.
Thanks,
Gaston

I have a log file here that doesn't contain POST /api/plugin/tplinksmartplug but as several instances of tornado.access and all of them have Warning with them. I don't know if it's related, but you can have a look at it...
octoprint.2018-12-25.log

The 404 are expected since those URLs are invalid in OctoPrint. I guess something on your network is making those requests. The only 409 is also expected since the printer was offline when you collected the log.
Could you do this final test to see if we can collect the info we need?

 It should appear the entries we are looking for

Thanks,
Gaston

Here's the OctoPrint Log file after the described steps. But it doesn't seem to have the lines you are looking for. Have a look.
octoprint.log

One last test (before running out of ideas) :(

Make sure that OctoPrint is up and connected to a printer
Go to OctoPod, go to the Move tab
Click on any of the move axis

You should see things like this in the logs:

018-12-27 17:11:22,475 - tornado.access - INFO - 204 POST /api/printer/printhead (<IP_ADDRESS>) 6.64ms
2018-12-27 17:11:22,476 - tornado.access - INFO - 200 POST /api/printer/printhead (<IP_ADDRESS>) 7.31ms

With this test we can confirm that the app can talk via HTTP to OctoPrint and that tornado logs are logging correctly. If they appear fine then it is a mystery why it is not logging the HTTP request to get the switch statuses. If logs for tornado appear and still our request does not appear then we could try using some networking tool that captures HTTP traffic to see what is going on with the mysterious request. Not sure how comfortable you are with these things.
Gaston

I don't know if it help solve the mystery, but I finally manage to be able to use the OctoPod TPLink button.
But it seems like the button is not always active. It became active for the first time when I used the plugin from within the Octoprint web interface. Once I turned on and off the TPLink plug within Octoprint, the button became "available" in Octopod. I was able to turn my TPLink plug on and off from OctoPod. Then I closed/killed the app and reopened it. Once again, the button was not functioning anymore.
I redid the OctoPrint cycle and the OctoPod button "availability" came back again. There is a problem though. I'm getting warning messages, either when turning on and off about failed requests, but the plug do turn on and off. It seems like a false warning message, but maybe there's a reason behind that.
So here's some screen shot of the warning messages and the log files.

octoprint.2018-12-28.2.log
plugin_tplinksmartplug_debug.2018-12-28.log

Thanks for this info.
Let me share this piece of information (ignore if you knew how OctoPrint works). OctoPrint has 2 "communication channels". 1) You can make HTTP requests to execute actions or request information and 2) You can use websockets to read information from OctoPrint. TPLink Smartplug plugin uses HTTP requests to toggle switches and uses websockets to report status of the switches.
Having said that, did the printer move when you pressed the move button on any of the axis? If it moved then HTTP requests communication channel works fine and for some reason OctoPrint's log is not logging tornado.access entries since they do not appear in the log as you correctly observed. More about logging network traffic below....
This is what we learned from your last test: when you clicked the TP Link switch button from OctoPrint itself, OctoPrint sent updated switches information via the websockets channel. This is why OctoPod shows correctly the status of the button. However, when you pressed the button from OctoPod, OctoPod used the  HTTP requests communication channel and this failed as seen by the dialogs that you saw in the app.
Summary of what we know so far:

Your  websockets communication channel works fine
Not clear if your HTTP requests communication channel is working fine. If the test of moving the printer's axes from OctoPod worked then this channel is working fine.

Since OctoPrint is not logging HTTP traffic for some reason, we will need to resort to other ways to capture this information and finally get to the root of this mystery. :)
If you know how to capture network traffic this ignore the rest of this response. There are different tools that you can use to capture network traffic. You will need to ssh into the octopi box for all of them. I do not have a raspberry pi with me now so giving a few options to try.
I think that TCPDUMP is already available on raspbian. Follow this guide to see how to log HTTP traffic. Might need to add sudo at the beginning if not enough permission. If this tool is not already installed then this guide will help.
If that tool is not working for you then you can try using justniffer. If install is giving some errors then this other guide has more info that might help.
Last tool to try is httpry. If this tool is not already available in Raspbian then you can compile it from source:

sudo apt-get install gcc make git libpcap0.8-dev
git clone https://github.com/jbittel/httpry.git
cd httpry
make
sudo make install

You then use it like this:

sudo httpry -i <network-interface>

To answer you question about the move, yes it does when I push displacement buttons in OctoPod.
Unfortunately, I don't think I'll be able to log the HTTP traffic. I've taken a look at the different options you mentioned and It's beyond my level: It could be written in Russian I couldn't say.
Oh well, 98% of Octopod is working awesome for me, I think I will have to live without the support of my SmartPlug.
Thanks again for your help.

Great news Hedrakk!
I got to the bottom of this. The TPLinkSmartplug plugin has been recently updated and the way to interact with it (i.e. its API) has changed and is no longer compatible with OctoPod. I updated OctoPod to use the new API of the plugin and things work fine again.
I also learned how to make OctoPrint log those "missing" tornado entries. No longer needed but sharing info just in case. Go to OctoPrint -> Settings -> Logging. Under Logging Levels you need to add a new row for "tornado.access" using level "INFO". Save the new settings and you are good to go.
If you want I can let you know once the new beta is ready to be tested so you can confirm that things work fine for you. I will need a way to reach out to you (eg. email, facebook) to share a link with you.
Thanks for bringing this issue up.

Great news indeed! I was ready to give up on this feature.
Thanks a lot for your determination.
How can I share my email with you so not everyone will see it?
Jean-Francois Chabot

Capitaine
Equipe Extra-Life des Bionic Marmots|
Bionic Marmots Extra Life Team|
www.extra-life.org/participant/jfchabot

Le 29 déc. 2018 à 13:31, Gaston Dombiak<EMAIL_ADDRESS>a écrit :
Great news Hedrakk!
I got to the bottom of this. The TPLinkSmartplug plugin has been recently updated and the way to interact with it (i.e. its API) has changed and is no longer compatible with OctoPod. I updated OctoPod to use the new API of the plugin and things work fine again.
I also learned how to make OctoPrint log those "missing" tornado entries. No longer needed but sharing info just in case. Go to OctoPrint -> Settings -> Logging. Under Logging Levels you need to add a new row for "tornado.access" using level "INFO". Save the new settings and you are good to go.
If you want I can let you know once the new beta is ready to be tested so you can confirm that things work fine for you. I will need a way to reach out to you (eg. email, facebook) to share a link with you.
Thanks for bringing this issue up.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub, or mute the thread.

Send me an email. Same username that you see in github at gmail.com

The plugin works for me but each time I turn on or off the plug I get a message that it failed even though it works.  Anyone else getting this pop up message?  Anyway to fix it?


Pivot doesn't accept exclusion and inclusions. PivotUI does.

Hi.
I found a quite confusing issue concerning the pivot table when showing the table without configurations.
When setting the exclusions and inclusions attribute in the pivotUI() config element the according filters are set. Using the same config in the pivot() function for displaying just the table the result looks different.
I also created a js fiddle to show you the problem:
https://jsfiddle.net/ngw1dmtp/10/
Cheers

Yes, pivot() and pivotUI() do slightly different things and have slightly different input parameters: https://github.com/nicolaskruchten/pivottable/wiki/Parameters

Is it possible to also accept exclusions in pivot() parameters for your next release?
At the moment I have the issue when I saving a config from the pivotUI() and display it afterwards in pivot() doesn't look the same and that makes it actually quite unhandy.

I'm not that interested in changing the existing behaviour of pivot(), no...
I've looked at creating a new function, something like pivotNoUI() or adding a hideUI parameter to pivotUI() but neither seemed particularly easy to do. I'd happily accept a PR for it though!

That's disappointing...this is exactly what I need in my current implementation of an executive dashboard. Give the user a master pivotUI that allows them to set their options the way they want it, and then click a button to save the config, allowing multiple pivots on the same dashboard, etc.  Then when they load the dashboard page they don't need the entire UI, just the resultant pivot.
Just out of curiosity, what were they issues you ran into looking at a new function?

@jneilliii the issue is that pivotUI stores its state in the DOM, so we can't just not render those elements.
The latest release (v2.21.0) papers over this by adding showUI parameter that can be set to false to hide the UI. It literally hides the UI: the DOM elements are created but then made invisible via CSS ;)

The documentation has been updated in various place, so I'm closing this issue.

Thanks, that's actually the approach I took in my application, hiding things after load. Having it built in as an option makes it much cleaner.


Found a bug in Latest wysihtml-toolbar.min.js v0.5.5

Hello,
I am using this script in my project but i have found a bug in latest version of this script.
/*! wysihtml - v0.5.5 (2016-01-06) */
When i make any word hyperlink it works, but after it if i want to remove hyperlink from that word then i clear the link but the word remains also anchor without any hyperlink.
Would you like to solve it in this version because it works in v0.5.0

I wasn't able to repro this issue. What's your html specifically?
However, I did notice that this happens if you have an anchor tag wrapping another node. E.g.

In this case, if you remove the image, the  tag remains and is unable to be removed.
btw - I'm not a maintainer of wysihtml or anything, I'm just working a lot with it now and saw that I might have had a similar issue as you.

I have a video that will show the bug.
http://screenpresso.com/=CQdlb
Please see it. After making any word anchor then we can't make it normal word(without anchor).

Ok confirmed this is an issue. It seems you cannot remove a link. I'll need to fix this on my installation as well, so I'll investigate and do a pull request. The current workaround is to remove the entire element.
Leo

Thanks Leo,
I just want to inform you about this issue.
On Sat, Jan 23, 2016 at 8:54 PM, Leonard Teo<EMAIL_ADDRESS>wrote:

Ok confirmed this is an issue. It seems you cannot remove a link. I'll
need to fix this on my installation as well, so I'll investigate and do a
pull request. The current workaround is to remove the entire element.
Leo
—
Reply to this email directly or view it on GitHub
https://github.com/Voog/wysihtml/issues/296#issuecomment-174193518.


fix: add user agent header

Should we delete the header TursoCliVersion?
closes https://github.com/chiselstrike/turso-cli/issues/517

If we do, I think it should conform to the typical user agent format.
https://developer.mozilla.org/en-US/docs/Web/HTTP/Headers/User-Agent

User-Agent:  /

Thanks for bringing that to my awareness. Changed it, would love to hear comments about the new format :)


[PLACES-421] Sidebar Redesign: Filter Updates

@FacundoMalgieri I've pushed my changes, merge whenever you feel it!


Update sbt-typelevel to 0.4.1

Updates org.typelevel:sbt-typelevel from 0.4.0 to 0.4.1.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

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

labels: sbt-plugin-update, early-semver-minor, semver-spec-patch, commit-count:1

Codecov Report

Merging #355 (20373c9) into main (4f66a03) will increase coverage by 0.18%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##             main     #355      +/-   ##
==========================================
+ Coverage   96.74%   96.92%   +0.18%
==========================================
  Files           9        9
  Lines        1106     1106
  Branches      103      103
==========================================
+ Hits         1070     1072       +2
+ Misses         36       34       -2

Impacted Files
Coverage Δ

core/shared/src/main/scala/cats/parse/Parser.scala
96.74% <0.00%> (+0.10%)
:arrow_up:

...shared/src/main/scala/cats/parse/Accumulator.scala
100.00% <0.00%> (+2.43%)
:arrow_up:

Continue to review full report at Codecov.

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


GitHub dependencies don't work with private repositories

Adding github org/repo Path/Here to paket.dependencies fails if org/repo is a private repository on GitHub. Would be super useful to have :grimacing:
@caindy mentioned this over in #284 a few months ago

Just noticed this was still open. Happily closing thanks to #1084


azureml.core

Related command

Is your feature request related to a problem? Please describe.

Describe the solution you'd like

Describe alternatives you've considered

Additional context

from azureml.core import Workspace
ws = Workspace.from_config()

Please provide detailed info for the ask

@Nealit25 Please provide more information about the issue, the command and also version details.


Do we need a transactions per impression opportunity?

https://github.com/criteo/addressable-network-proposals/blob/906e33ed128dec9cf5c0203bdc6ffc97627c8761/mvp-spec/audit-log-requirements.md?plain=1#L69
Transaction ID is the generated identifier for a dedicated placement. One
Transaction ID per Audit Log.
I have been reviewing all of the different specifications and thinking about how the design could be simplified, and one of the design decisions I see that I don't think is necessary is the transaction_id per placement. The original SWAN model terms were written to describe the sending and receiving of data, and did not actually get detailed on the relation to actual advertisements on the page. I think this is a very reasonable way to do it and vastly simplifies design.
If you treat PAF transactions as being just a sending and receiving of user data which I think is reasonable you can save on compute and complexity for all the parties involved. I think the only real concern is the construction of an audit trail, but I do believe that can be solved in another technical way using existing fields in OpenRTB and other specifications.
I would love to start a discussion about this and hear concerns about an approach like this, either technical or legal.
Lastly, I am wondering if the design and requirements being written are meant to be for a finished PAF system, or if they are for the trial only. I ask because my understanding of the trial is that it has relaxed audit requirements which would relate only to an advertisement served using PAF data, and if that is the case could warrant a simpler design in this case.

Hi Brian,
Answering first the last bit:

Lastly, I am wondering if the design and requirements being written are meant to be for a finished PAF system, or if they are for the trial only. I ask because my understanding of the trial is that it has relaxed audit requirements which would relate only to an advertisement served using PAF data, and if that is the case could warrant a simpler design in this case.

The audit trail designed in this MVP is meant to reflect the end user audit needs of the "finished" PAF system.
Other audit needs (from publishers, advertisers...) are not yet defined but could be included in future evolutions of PAF. It might then make sense to extend the design and requirements, or to define separate ones - it's a bit early to tell.


[SelectField] Dropdown Menu pulldown in Select Field component appears in top left corner when zoomed in

Dropdown Menu pulldown in Select Field component appears in top left corner when zoomed in even when passing in anchorOrigin
Versions

Material-UI: 0.18.1
React: >= 0.15.0
Browser: Chrome

Description
Whenever I zoom in on the browser, the dropdown menu doesn't appear correctly.
Here is what my dropdown looks like at 100%:

and what is looks like at 110%:

I'd want the pull down to come from below, instead of popping up. I'm passing in
anchorOrigin: {
   vertical: 'bottom',
   horizontal: 'left',
},

but the canAutoPosition in the popover seems to be overriding this? Not sure...
This seems to also be an issue on: http://www.material-ui.com/#/components/select-field as well when zoomed in 125%.

I was looking around and it doesn't like look there are any props that can fix this behavior. On a coworker's screen, it only works for them at 90% but looks weird at 100% so we can't move on.
Thanks for all your hard work :)

You can just set maxHeight to be smaller and it fixes this issue. It would be nice to be able to have the pulldown trail off the screen like other pulldowns, but for now that's fine


Debug hover does not work in some cases

Test Tour MERN https://github.com/Microsoft/vscode/issues/22277

VSCode Version: Insiders
OS Version: macOS

Steps to Reproduce:

Clone MERN starter kit
Start debugging
Set a breakpoint in post.controller.js on line 13
Refresh the app

I expect to be able to hover over variables and inspect. Instead when I hover I don't see anything.

I think you are trying to access a variable from another scope.

Dup of https://github.com/Microsoft/vscode/issues/24520

Reopening because there is some funky behavior shown to me by @weinand that I would like to investigate

The problem seems to resolve if all blank lines and comments are removed from the TS file.

@dotnetengineers that seems highly unlikely

The above mentioned is reproducible with sample code that at https://github.com/dotnetengineers/Issue_-24277.  On app.ts set a breakpoint on Line 39, start debugger, the last variable that displays hover values is schoolBooks on line 27, any variables after that have no hover value.  Remove all blank lines from app.ts and re-run, all variables now have a hover value.
Windows 10.0.14393
VSCode 1.12.0-insider
Node 7.8.0
TSC 2.2.2

Hello Isidor – I’ve posted some sample code that replicates issue #24277 and resolves when empty lines are removed.
From: Isidor Nikolic<EMAIL_ADDRESS>Sent: Wednesday, April 12, 2017 04:05
To: Microsoft/vscode<EMAIL_ADDRESS>Cc: dsbailey<EMAIL_ADDRESS>Mention<EMAIL_ADDRESS>Subject: Re: [Microsoft/vscode] Debug hover does not work in some cases (#24277)
@dotnetengineers https://github.com/dotnetengineers  that seems highly unlikely
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/Microsoft/vscode/issues/24277#issuecomment-293504117 , or mute the thread https://github.com/notifications/unsubscribe-auth/ALnZmxN7CeQ34eEgMnq7Cezap2WH85iFks5rvIWhgaJpZM4M3dN_ .  https://github.com/notifications/beacon/ALnZm-tj8jjea9Nfo4yqDMtdV7bQKetLks5rvIWhgaJpZM4M3dN_.gif

@dotnetengineers thanks, I will investigate more next week

@dotnetengineers thanks for aweseme repro steps!
The issue here seems to be that we are getting bad scope ranges from the node2 debug adapter
fyi @roblourens
This seems to happen because we are hovering over a typescript file and the scope ranges have line numbers with respect to the javascript file.
To work around this issue I made our scope search strategy a bit more flexibile: if none of the scopes satisfies the range we are searching in -> still try to search across all scopes.
This fallback mechanism fixes this issue.

Is this fixed? @isidorn @chrmarti
I opened a new issue, I hope it is ok
#30286

There is a workaround in place (as @isidorn mentioned above).
But the underlying issues is probably not fixed.
@roblourens does the inspector protocol node debugger map the scope ranges via source maps?

Yes, when I tried this, it worked fine for me - https://github.com/Microsoft/vscode-chrome-debug/issues/429

I'm still this as only half-working with node.
Here it is working for an object:

But then I don't get much else, here I am hovering over isWhitelisted:

And again nothing for req or req.path:

This is our launch configuration:
    {
      "type": "node",
      "request": "attach",
      "name": "Attach To Running Server",
      "restart": true,
      "sourceMaps": true,
      "showAsyncStacks": true,
      "port": 9231
    },

Are you using babel?

Yes, in the worst way possible: requiring babel-register.

(We just activated the "lock old issues" bot, nothing personal 😄 )
That is kind of unavoidable right now but will be fixed by #37838


Change behavior of offsets

It seems like V8 optimizes empty functions differently based on how hot they are.
We gather offsets once per every Suite. The number of iterations is determined by the deviationPercent.
The problem comes from for example offsets being stable after 2 500 iterations while the benchmark being stable after 500 000 iterations. The cost of the wrapper function seems to be much lower after 500 000 iterations than in 2 500 iterations.
What this causes is that if the benchmark take 2 ns and the difference of wrapper function cost (2 500 vs 500 000) is 4 ns then the result is -2 ns which is clamped to 0 ns making it infinite.

One way to solve it is to run offsets AFTER EVERY benchmark and to run it N times based on how many times the benchmark was ran.
Another solution might be to dynamically change the koefficient based on the smallest number. If the koefficient is 1, the offset 50 ns and the results [35, 64, 97, 122] then the koefficient must be changed to less than 0.7 to make the results look like this [1, 30, 63, 88]. This way there is no infinite result and all the results still have the same difference between them (in percent). The problem with this solution are benchmarks that should be infinite which is a benchmark of an empty function. Maybe in such a case the koefficient might be set to 0.

So I've tried doing some tests regarding the number of iterations. Here are the results:

cycles
async cpu
async ram
sync cpu
sync ram

50
77
448
51
256

2500
58
448
38
256

100000
22
304
24
256

10000000
20
304
21
256

It's very apparent that the more iterations the more the JS engine (in this case V8) optimizes even a simple empty function with literally nothing inside. Interestingly enough ram of async function changes somewhere between 2500 and 100000 iterations from 448 to 304.
This basically confirms my theory. So now the next step is to do iteration based offset calculations.
The easiest thing would be to run the offsets after all benchmarks have run, gather iterations and run offsets for each iteration amount and then just subtract the offset from benchmarks. But this would defeat the whole event-based and real-time thing.
So instead I'm gonna move offset calculations at the end of every benchmark. I'm gonna keep a map of iteration amounts and their offsets and check if the offsets already exist before actually running them. If all benchmarks take the same amount of iterations (which they usually do) it's still gonna calculate offsets just once. If however they differ then there will be an appropriate number of offsets based on iteration count.
Hopefully the JS engine won't optimize and remember the optimized version of one offset. Effectively leaking optimization from one offset calculation to the other one making them yet again unreliable. If I find out that's the case then I'll be forced to move the offset calculations to their own threads/JS realms.

So after moving the offsets after each benchmark as mentioned in the previous message I'm still struggling with the infinite results.
When it comes to slow/complex benchmarks that take thousands of nanoseconds it doesn't matter since the const of the benchmark wrapper function is gonna be small (depending on the number of iteration somewhere between 30 - 80 nanoseconds).
But when it comes to fast/small benchmarks where you care about every small increment it's very important for the bench lib to not introduce any noise in the form of the wrapper function perf cost. If the logic inside that function takes 4 nanoseconds and the wrapper itself takes 40 nanoseconds then all of the benchmarks will look basically the same since most of the nanoseconds don't come from them but from the wrapper function.
It might not be the best DX, but right now I think the only viable solution to this would be passing two functions down into the wrapper function. start and end. It'll move the actual benchmarking logic into the body of the wrapper function virtually getting rid of the cost (I'm not sure about RAM though).
This is how it could look like:
new Suite("Array loops")
  .add("for", function({ start, end }) {
    start();

    for(let i = 0; i < 10000; ++i) {
      tmp = i;
    }

    end();
  })

Maybe the start and end function will have to be async requiring the wrapper function to also be async in order to await them. Also the functions themselves might also have some perf cost so it might not solve the problem at all.
The last option would be to introduce some sort of compilation step which would get rid of all the junk that is here for the DX and possible run every benchmark in it's own thread/JS realm but all that sounds way too complex. However what I'm after is the most statistically sounds JS/TS benchmarking lib so if there will be no other option then I guess I'll go the compilation route.

I've figured out that the way I was creating medians was flawed so I'm gonna redo it. Also even though Median Absolute Deviation is better for results it makes the benchmarks end too soon so in the end I'm gonna use Standard Deviation (but I'm gonna return both from the benchmark).
Also I've stumbled upon HDR Histograms. I don't think they can improve the way we run the benchmarks but it might be a nice addition to the data I return from each benchmark so I'm gonna add it.

This is how a benchmark of empty functions looks like now.

Previously the number of iterations were exactly the same for both. Now you can see that with Standard Deviation as opposed to Median Absolute Deviation it takes much longer for async to stabilize than sync. That's exactly what we want.

I've tried "compiling" benchmarks (using Function) in order to get rid of overhead of calling now and memory functions. It did work (but not as well as I've hoped for) but I couldn't execute benchmarks that used anything outside their scope (not very usable for testing libraries) so I reverted it back.
There is a way of "compiling" and executing code outside of the scope of the benchmark functions just like benchmark.js does it (save benchmarks into an object and access that object from inside the compiled function). I might implement this later once everything else is working and stable since like I've mentioned the difference was negligible.
At first the offsets were being computed before benchmarks were executed. Now I've tried computing them together with benchmarks. It seems that the best solution is gonna be computing them after all benchmarks have finished.
Let's say we have these tuples of benchmark and offset in nanoseconds: [[36, 21], [56, 41]]. After subtracting the offsets from benchmark results we get [15, 15]. Both are 15. But that's wrong. Why is it wrong? Because the first one gets offset penalty of 21 and the second one gets 41 (given the algorithm that I use right now). Here we can argue that we can simply use the smaller offset 21 for both. But what if the order was different?
So the only reasonable thing to do is to run all benchmarks, figure out the smallest median and keep running the offset function until its median becomes smaller than the smallest benchmark result and only after that apply it to all of the benchmarks.
This will require the terminal to re-render after offsets are gathered and applied so I think I'll finally switch from my very underground process.stdout to something like ink.
(I hope this is gonna be it because I've rewritten the whole library like 6 times already in the last week)


Is there any public API to manipulate the data set?

Hello,
The idea behind this project is kind of cute and is appreciated by developers. I installed the Chrome extension a few months back and now I'm curious to know if there's a public API to be able to do CRUD operations (without DELETE :grinning:) on the data set the extension using. I think it would be nice to have something like that and even if you're not interested in the idea that much to implement it yourself, or if you're busy and looking for a person to do the job, I'm in.

Hey @amirhoseinsalimi 👋
At this time the API for fetching all snippets doesn't exist. However, this is something that we had in plan for a long time at our organization.
If we ever decide to implement it we have to really plan it out well. The 30-sec-knowledge repo does a decent job of grouping data from different 30-sec repositories but it doesn't auto-fetch it, and it's not as robust as it should be - If the snippet structure changes on any of the projects it's just not going to work anymore.
I'm going to introduce @Chalarangelo and @skatcat31 to discuss this as it's quite the topic that comes from time to time and we still haven't decided what to do with it.

As far as I know, we're migrating most of the projects to Gatsby this year. In my opinion, if we ever decide to go for this we should make API per project and 30-sec-knowledge would just need to fetch that API.

or

We decide to not implement this as this is the way to much work for very little use (still don't know how many people would use it and for what purposes).

Anyways thanks @amirhoseinsalimi for offering us help. If we ever plan this out you can definitely help us build the API. We just have to be sure not to leave any repo behind this plan as one of the goals of 30-seconds is to make educational materials accessible to everyone.

An API is too much work, but we can ask individual repos to host their snippetData.json as part of their website, so  that anyone (30 seconds of knowledge included) can fetch the data from that. We can even make it part of the starter before we complete any migrations.

That would be a good option. Not too much work but definitely serves a purpose. WDYT @amirhoseinsalimi ?

Having considered what you said, I think this is not a good time to implement such a feature but it still worth it to keep the idea in a wishlist. 30-sec-knowledge can become a culture and I thought maybe a twitter bot and an API to seed the database could help it to gain the popularity it deserves. Anyways, I wish the core team the best and I would welcome any opportunity to help the product in the future. BTW, thank you for your time.

Chiming in with my two cents here.
Plugging 30 sec of knowledge to any online API would defeat the purpose of the extension, which is to be an all the time accessible plugin feeding you the snippets whether you are online or not. I got a lot of comments from people claiming they appreciate the fact they could read through the snippets while offline (airplane, bus and so on...) Introducing an API would make this impossible.
A more probable way of dealing with it is having all 30 sec repos share the same project structure, then using those repos as submodules within 30 sec of code, to update the extension on a monthly basis. This means that the extension would need to be manually updated every month which isn't really a problem since any structural change would require manual upload to both the chrome and firefox stores anyway. Submodule updates could be handled through a simple bash/node script run every time the extension update is needed or on build.

@petrovicstefanrs Good idea. The common infrastructure is already the priority if you are following the latest discussion in the @30-seconds/meta team.
However, submodules should not be in 30-seconds-of-code, but rather a new repo, in my opinion, one where all of the repositories are submodules and it does all of the heavy lifting for us. This seems to me to separate concerns rather nicely and allow for future repositories, official or not, to be integrated more easily.
Provided that fact that we can use a system like that, all repositories should still host their own JSON files and maybe we could make the extension auto-update its content file once a week or so while releasing major versions manually monthly or quarterly. Is that an option? I haven't got much experience with browser extensions.

@Chalarangelo Yes, I'm trying to keep up with the discussion on @30-seconds/meta as much as I can :D
Submodules would be a part of the extension repo, in a scenario where a new 30 sec repo for a new language was released I would just add that repo as a submodule, provided that the structure is the same for all repos ( what you are trying to achieve already ) there would be no need for much coding to update the extension, I think it could be even be automated so the only action needed to update the extension is adding a new submodule.
Now all this being said existing languages (submodules) would still need to be updated by a simple git pull in each submodule ( a simple bash script could automate this and be run on build ).
Ther release needs to be manual, I couldn't find any possible way to automate it, especially as Firefox store requires human to human correspondence to check the extension every time you update it.


Add support for skipped fields

Hi all
I made this PR to support maybe skipped fields, either always or dynamically with #[serde(skip_serializing_if = "Option::is_none")].
I have considered hiding the function behind a feature flag and adding a runtime Err without the flag so consumers of the crate notice that they were trying to serialize an object that would not be readable again.
Looking forward hearing from you,
Stefan
PS: I assume that None::<()> takes the same amount of space as None::<u128> or something else would and that trick then allows us to stay with the wire format, 99% sure of that, happy to learn :blush:

Does this also fix the #[serde(skip)] attribute ? or is it only targetted to skip_serializing_if ?

It works with skip, but it serialized it to a None, so I am not sure what happens if your type is not Option<T>

This works for (conditionally) skipped fields of type Option<T>, but I don't think it will work for fields with different types, for skipped variants, or for skipped fields of tuple structs/variants (since those don't have skip_field() methods). Unfortunately, I don't see a way to handle skipped fields in their full generality given serdes current APIs without serializing field names or indices, which would break the wire format and add overhead to structs with no skipped fields.


⚠ Bofrost.es has degraded performance

In 52b6b77, Bofrost.es (https://www.bofrost.es) experienced degraded performance:

HTTP code: 200
Response time: 1976 ms

Resolved: Bofrost.es performance has improved in 047590f after 6 minutes.


A11y contrast fix/work around

Here is something I made at work to try to help my company with color contrast issues
Added a button that toggles a class of high contrast that fixes some of the issues related to color contrast found in AXE. The body changes from the background image you currently have to black and then changes the subscribe link buttons to be black and white again to help with contrast issues. I positioned it in the upper right hand corner right now to not take away from everything else and not to make it look like a call to action button

@shortnd Hey Collin 👋🏼 This is a great idea. Although, running a Lighthouse Audit on the page gives it a 100/100 on Accessibility. Is there a tool you use to check for contrast that the app fails on? Would love to learn more!

@416serg Sergiy 👋 I use the axe chome extension to do most of my accessibility checking and looking at it says there are 25 color contrast issues. Some of the issues are because of the items being background images or gradients and tool can't find the background color.
https://chrome.google.com/webstore/detail/axe/lhdoppojpmngadmnindnejefpokejbdd?hl=en-US


Set buffer size in DownloadFile() to 8192KB from 10KB

I found the downloads proceeding extremely slowly (~100-150 KBps) with the buffer size set to 10KB. I increased it 8192 and my speeds increased to around ~10-15 MBps.

Hi @timsutton, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

This seems like a small (but important) contribution, so no Contribution License Agreement is required at this point. Real humans will now evaluate your PR.

TTYL, MSBOT;

You are right.  That does decrease the download time.  We appreciate the input!


Clarifications

[Enter feedback here]
For this section:
Find accounts you have access to

First issue:
Both REST and AZ CLI does not return this section:

"enrollmentAccounts": [
          {
            "id": "/providers/Microsoft.Billing/billingAccounts/1234567/enrollmentAccounts/7654321",
            "name": "7654321",
            "type": "Microsoft.Billing/enrollmentAccounts",
            "properties": {
              "accountName": "Contoso",
              "accountOwnerEmail"<EMAIL_ADDRESS>              "costCenter": "Test",
              "isDevTest": false
            }
          }
        ],

When using REST method, the entire section is missing
When using AZ CLI, it returns:
"enrollmentAccounts": null,

As such, I wasn't able to retrieve enrollmentAccounts ID in this format:
/providers/Microsoft.Billing/billingAccounts/1234567/enrollmentAccounts/7654321

I had better luck calling this API instead to retrieve the list of enrollment accounts, after knowing my billing account id:
Enrollment Accounts - List By Billing Account Name
GET https://management.azure.com/providers/Microsoft.Billing/billingAccounts/{billingAccountName}/enrollmentAccounts?api-version=2019-10-01-preview

Second issue:
These wordings are ambiguous

The values for a billing scope and id are the same thing. The id for your enrollment account is the billing scope under which the subscription request is initiated. It’s important to know the ID because it’s a required parameter that you use later in the article to create a subscription.

In the sample REST output, there were two seperate IDs:
"id": "/providers/Microsoft.Billing/billingAccounts/1234567",

"id": "/providers/Microsoft.Billing/billingAccounts/1234567/enrollmentAccounts/7654321",

Since my 1st issue, I had spinning on my wheel for quite a long time, even after a support ticket<PHONE_NUMBER>006060 opened with Microsoft, but the support seems to only familiar with Azure Portal, I had hard time to communicate with them, as they don't understand REST or AZ CLI. It would help if you clearly mention the expected id should be formated as:
/providers/Microsoft.Billing/billingAccounts/1234567/enrollmentAccounts/7654321

Third minor issue:
REST section:

GET https://management.azure.com/providers/Microsoft.Billing/billingaccounts/?api-version=2020-05-01

The forward slash / behind billingaccounts should to be removed:
GET https://management.azure.com/providers/Microsoft.Billing/billingaccounts?api-version=2020-05-01

As stated here:
Billing Accounts - List

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

ID: 0d73f3e0-d3d3-eca9-483f-4a787fa77bb2
Version Independent ID: d4046a56-c05e-e278-382d-2cb26dd5c20f
Content: Programmatically create Azure Enterprise Agreement subscriptions with the latest APIs
Content Source: articles/cost-management-billing/manage/programmatically-create-subscription-enterprise-agreement.md
Service: cost-management-billing
Sub-service: billing
GitHub Login: @bandersmsft
Microsoft Alias: banders

@jyeblog Thank you for reaching out to us with your queries and feedback on the document. We will review it and also check with our internal team and get back to you at the earliest.

@jyeblog - these are great pieces of feedback. Thank you very much for taking the time. These are all valid and we will take steps to update the documentation to address these.

@jyeblog As Anurag commented, your feedback is correct and we'll update the docs as soon as we can to address your points. Thanks for letting us know!
#please-close


Error while trying to scan a DVD

When I try to scan a DVD I get an error in the log and the scan fails. The error reads "This application version is too old.  Please download the latest version at http://www.makemkv.com/ or enter a registration key to continue using the current version.", "This application version is too old.  Please download the latest version at %1 or enter a registration key to continue using the current version.", "http://www.makemkv.com/"
I already tried to set the beta key from the makemkv page as documented in the readme, but this did not lead to any improvement. I also tried to build the Docker image myself, but the same error occurs. The day before yesterday I could scan DVDs so something must have changed yesterday/today.
I hope you can help me further.

Hi @JustM3dium
The beta key is valid until end of July. Even rebuilding the image will fail until the ppa:heyarje/makemkv-beta repository is updated with latest beta 1.16.4. current version from this ppa repository is 17 weeks old, not sure it's version 1.16.4
You can either wait for it to be updated or look for a fork with an image build from makemv sources. ;)
as I'm no makemkv expert the root cause could be something else.
You may have tried to remove settings.conf to force the container to set the key with the beta serial on next restart.

https://github.com/rix1337/docker-ripper#makemkv-needs-an-update

update triggered

@edgd1er could be right though. The PPA potentially needs an update first


[chunkcopy_safe] Use temporary variable to store safe length to avoid wraparound due to cast to unsigned type.

When comparing two pointers, the result is signed integer, but len is unsigned integer
Remove base address when linking Windows dynamic library, as it has to be different for 32-bit and 64-bit versions

Fixes #1012.

Fixing the warning on Windows unmasked error in AArch64 build. This should be fixed when second bug mentioned in #979 is also fixed.


[release-1.5] Use injector configmap for sidecar version mismatch analysis

This is an automated cherry-pick of #20929

@istio-testing: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-istioio-k8s-tests_istio_release-1.5
d975a4f163757ce60646b2e96b80fafd536331db
link
/test integ-istioio-k8s-tests_istio_release-1.5

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. I understand the commands that are listed here.

/retest


siegelslopes is not available on Windows.

My issue is about ...siegelslopes is not available on Windows. Same code runs fine on Ubuntu.
Reproducing code example:

Sample code to reproduce the problem

Error message:

Traceback (most recent call last):
  File "<stdin>", line 1, in <module>
  ...

module 'scipy.stats.mstats' has no attribute 'siegelslopes'
Traceback (most recent call last):
File ".<>.py", line 584, in main_trade_function
low_prices_slope, low_prices_intercept = stats.mstats.siegelslopes(
AttributeError: module 'scipy.stats.mstats' has no attribute 'siegelslopes'
<class 'AttributeError'>
Scipy/Numpy/Python version information:

Python 3.7.1 (v3.7.1:260ec2c36a, Oct 20 2018, 14:57:15) [MSC v.1915 64 bit (AMD64)] on win32
Type "help", "copyright", "credits" or "license" for more information.

import sys, scipy, numpy; print(scipy.version, numpy.version, sys.version_info)
1.1.0 1.15.4 sys.version_info(major=3, minor=7, micro=1, releaselevel='final', serial=0)

Hi @tg12 can you try importing it as a standalone object via
from scipy.stats.mstats import siegelslopes

from scipy.stats.mstats import siegelslopes

ImportError: cannot import name 'siegelslopes' from 'scipy.stats.mstats' (C:\Users\Barry\AppData\Local\Programs\Python\Python37\lib\site-packages\scipy\stats\mstats.py)
Same error. The same code works fine on Ubuntu.

Then probably something went wrong with your windows installation. If you can please reinstall by first removing and then make sure that your ubuntu installation version is also up to date.

Sure, It's all at the very latest code. I installed both using pip.

doesn't look like a pip issue, but like being in the wrong environment or something. siegelslopes is in 1.2.0, and pip install scipy --upgrade will install 1.2.0. So closing this.
@tg12 feel free to keep commenting here if you need help sorting out your install issue (we'll need more details on how you installed Python, and if you install with pip add the -v flag for verbose output to see what's happening).


[rt.openssl.org #4695] calloc issue in crypto\LPdir_win.c

Migrated from rt.openssl.org#4695 (status was 'new')
Requestors:

<EMAIL_ADDRESS>
From<EMAIL_ADDRESS>on 2016-10-03 07:00:26:
Hi -
I had a link failure due to an unresolved external "calloc" when
trying to build a WindowsCE application using OpenSSL 1.0.2j.

calloc appears in crypto\LPdir_win.c on line 98.

I think one is supposed to use LocalAlloc for WindowsCE instead of
malloc or calloc.

I didn't get a link error for malloc that appears on line 72 of that
file (on line 77, that memory is zeroed out), so it seems like a fix
for me would be to use a malloc and memset instead of calloc.

calloc also appears in ssl\kssl.c, though my application does not use
functions from that file.  I was puzzled to see calls to "calloc" and
also "kssl_calloc"

-Geoffrey

calloc is part of the C standard library, like malloc and free.  The work-around is fine.

Another option is to add this:
#include <stdlib.h>

In the book "Making Win32 Applications Mobile: Porting to Windows CE" by Nancy Nicolaisen, it says: "Don't use the C runtime functions to allocate memory on CE; doing so will cause unpredictable behavior.
Porting Tip: Eliminate all calls to calloc(), malloc(), and alloc(). Replace these with the Windows CE memory allocation APIs that best suit your needs."

According to the MSDN reference for Win CE 5, https://msdn.microsoft.com/en-us/library/ms859607.aspx
calloc() is declared in malloc.h (not in stdlib.h, where malloc() is found).

So, I just had to do my work-around again. Is there any chance a change can be checked in so I don't have to keep making my own updates?

See PR #4587

Hi @gjcoram, we finally got a solution in, freshly approved and merged.  See #4594 for details.

Thanks - 1.0.2m compiled (and linked!) for me just fine.


Windows Terminal Preview hangs on Windows 11

Windows Terminal version
1.16.2642.0
Windows build number
10.0.22621.819
Other Software
No response
Steps to reproduce
There is no consistent reproduction. It happens often enough, usually after logged in Windows after logging out for a while or after waking up the machine from sleep.
Dump file: The dump file can be downloaded from https://1drv.ms/u/s!AvrzkkkRHNSrhic-ffAuUGxdtbc_?e=0LhRhk
When this happens, I cannot open another Windows Terminal, but have to forcefully close the one that is hanging.
Below is a screenshot of the Windows Terminal when it happens. Please note the small close button highlighted in the red circle. This small close button stays even after forcefully closing the Windows Terminal process, and I have to click on it to make that button disappear.

Expected Behavior
Windows Terminal should not hang
Actual Behavior
It hangs from time to time.

main thread is in OnDwpSysCommand north of DefWndProc
message, wparam, lparam= 0x112, 0x0f020, 0
Never seen one of these before:
:013> k
 # Child-SP          RetAddr               Call Site
00 00000012`8d1ff658 00007ffc`9bf91b86     win32u!ZwUserGetMessage+0x14 [onecoreuap\windows\core\umode\moderncore\objfre\amd64\usrstubs.asm @ 189]
01 00000012`8d1ff660 00007ffc`91035065     user32!GetMessageA+0x46 [onecoreuap\restricted\windows\inc\private\core\ntuser\client\ntcftxt.h @ 537]
02 00000012`8d1ff6c0 00007ffc`9c71244d     winmm!mciwindow+0x135 [multimedia\media\winmm\mmwnd.cpp @ 457]
03 00000012`8d1ff760 00007ffc`9d2cdfb8     kernel32!BaseThreadInitThunk+0x1d [clientcore\base\win32\client\thread.c @ 75]
04 00000012`8d1ff790 00000000`00000000     ntdll!RtlUserThreadStart+0x28 [minkernel\ntdll\rtlstrt.c @ 1166]

That small close button is a conhost process, with a window that should not be visible. Next time this happens, there should be an openconsole.exe in the Terminal process tree. Mind grabbing a dump of that?

Wait there's an internal mail thread for this one already. This is a /dupe of #14134


updated package.json

updated package eslint from 3.18.0 to 3.19.0
Npm link :  https://www.npmjs.com/package/eslint
Repository link : https://github.com/eslint/eslint/releases

Sorry, I meant to review this sooner. Why did you close it? Also I believe eslint 4 is out now.


Depends on Laravel 9, but that dependency is not specified in composer.json

The current composer.json allows installation in a Laravel 8 application, but that causes the Arr::map does not exist error described in this issue.
I suppose either the composer.json should be updated to reflect this dependency on Laravel 9 or the project should be made backwards compatible with Laravel 8.

Heya. I removed the Arr::map calls in version 5.8.4. I hope this fixed the backwards compatibility. I had no idea it was added with Laravel 9. Good luck!


changie new editor is incredibly narrow

Thanks for submitting a bug report, please fill in the following details.
Description
When I run changie new I get an editor that gives me barely 30 characters to edit with:

This makes it very difficult to actually write a useful message!
Reproduction Steps
Steps to reproduce the behavior:

Run changie new
Choose a kind
Write a message

What happened
I get about 40 columns to edit in and then it starts scrolling.
Expected behavior
No UI fanciness at all, just let me type and let my terminal do the rest.
Additional context
I would also be happy if I could just write with $EDITOR. This would also have the benefit of giving me syntax highlighting.

Currently the only option is to set the body to block mode https://changie.dev/config/#bodyconfig-block
I do think using an editor is a good idea but feel like it may need to be an env var or something. Not sure.

towncrier uses --edit, maybe that would fit here too?

I didn't know changie didn't allow newlines in change log messages, but I suppose that a question for changie overall. I do use newlines in individual change log entries in general though (e.g., https://hackage.haskell.org/package/rel8-<IP_ADDRESS>/changelog has a few multi-paragraph bullet points). We would probably need to answer the question of whether or not changie should support newlines first though.

Changie supports newlines iff you specify in the body config to use "Block" mode. Then you get a text input that supports newlines and you just need to make sure your change format expects and deals with newlines however it needs to. The issue comes up if you do not have block mode enabled and someone tries using there editor to edit the body.
As you suggested the flow would be to not accept the body and to relaunch the editor, similar to any other validation. Maybe you just need to enable block mode and see how the editing feels in that. I think the logic above for --editor should be fine. I am wondering if it should apply to custom inputs as well. Like maybe --editor overrides the default text block input for any text block custom type as well. Hard to say.

Oh, you are creating full on code samples in your changelogs, got it. Then yea using your editor makes way more sense. One of the core reasons for switching to bubbletea was to use the exec process feature to launch your editor for this particular reason. I just have not needed it myself yet to develop it. Basically this example: https://github.com/charmbracelet/bubbletea/blob/master/examples/exec/README.md having a use case of writing entire code samples is something I was missing.

Closing in favor of https://github.com/miniscruff/changie/issues/505
Reopen if you believe this is incorrect.


magic_enum: 0.8.1-1 in 'humble/distribution.yaml' [bloom]

Increasing version of package(s) in repository magic_enum to 0.8.1-1:

upstream repository: https://github.com/Neargye/magic_enum.git
release repository: https://github.com/nobleo/magic_enum-release.git
distro file: humble/distribution.yaml
bloom version: 0.11.2
previous version for package: null

Holding for Humble Sync.


recycle method required

Hi!
It would be greate to have a public method for release all resources like private method reset(boolean newImage).

Public recycle method now exposed.


Update install directions

should be gem 'octopress-feeds' (the "s" is missing).

Thanks!

I've fixed the Readme and released a new version.


Merging changes up to the end of lesson 9

Merging changes up to the end of lesson 9

@hclivess Excellent work. Does this conclude this course?

@mikeckennedy I think it does, Mike

Perfect, I'll merge it all back into the site. Thanks!

All the changes are now pushed to https://training.talkpython.fm and should be live now.


[Build] support building targets for platform and arch inputs

Description
Adding platform and arch as a build argument to be passed to
the build target. This enables cross-platform cross-arch builds,
for example, we can build linux x64 on a linux ARM64 machine.
We would want to do this because some of the libraries that are
required for building (not for runtime) are not available for
certain operating systems.
Also updated the OpenSearch Dashboards Jenkinsfile to pass the
platform and arch.
Signed-off-by: Kawika Avilla<EMAIL_ADDRESS>Issues Resolved
https://github.com/opensearch-project/opensearch-build/issues/739
Check List

[x] Commits are signed per the DCO using --signoff

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Codecov Report

Merging #776 (9240eae) into main (b2fe209) will increase coverage by 0.03%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##             main     #776      +/-   ##
==========================================
+ Coverage   91.29%   91.33%   +0.03%
==========================================
  Files          75       75
  Lines        1999     2007       +8
==========================================
+ Hits         1825     1833       +8
  Misses        174      174

Impacted Files
Coverage Δ

src/build_workflow/builder.py
100.00% <ø> (ø)

src/assemble_workflow/bundle_recorder.py
100.00% <100.00%> (ø)

src/build_workflow/build_args.py
100.00% <100.00%> (ø)

src/build_workflow/build_recorder.py
100.00% <100.00%> (ø)

src/build_workflow/build_target.py
100.00% <100.00%> (ø)

src/run_build.py
85.00% <100.00%> (ø)

src/system/os.py
100.00% <100.00%> (ø)

Continue to review full report at Codecov.

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


Configuration changes by other packages get purged

When installing the package aadsshlogin from Microsoft, the file /etc/ssh/ssd_config
gets modified. This modification is needed but gets overwritten the next time
Ansible run the ssh role as this role manages the file as a whole. Having
Microsoft drop the snippet into an include file in conf.d is not feasible.
How should changes done to sshd_config be managed?
The snippet in question looks like this:
Match User *@*,????????-????-????-????-????????????    # Added by aadsshlogin installer
AuthenticationMethods publickey
PubkeyAuthentication yes
AuthorizedKeysCommand /usr/sbin/aad_certhandler %u %k
AuthorizedKeysCommandUser root

After some discussion with Gunnar and Kevin, handling this types of snippets should not be a concern of this generic role. This snippet should be handled by the azure_arc role that is technically the right. Now, how to "insert" this code into the sshd config is a whole other story. See id-unibe-ch/ansible-role-azure-arc#2 for the follow-up.


Enable execution of the UI against a local development server.

Codecov Report

Merging #500 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #500   +/-   ##
=======================================
  Coverage   84.27%   84.27%
=======================================
  Files         155      155
  Lines        2289     2289
  Branches      363      363
=======================================
  Hits         1929     1929
  Misses        321      321
  Partials       39       39

Continue to review full report at Codecov.

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

Codecov Report

Merging #500 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #500   +/-   ##
=======================================
  Coverage   84.27%   84.27%
=======================================
  Files         155      155
  Lines        2289     2289
  Branches      363      363
=======================================
  Hits         1929     1929
  Misses        321      321
  Partials       39       39

Continue to review full report at Codecov.

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


Meetup Agenda section

[ ] Title
[ ]  First row of cards.

I'm trying to do this part....

@tonalmathew Go ahead :+1:

Done :+1:


ModelsBuilder Options Not Updated Unless Models Build UI is Opened

I have many projects using ModelsBuilder and when I switch between them and attempt to run the tool it fails the first time until I open the ModelsBuilder Options UI where it shows the previous sites url, username and password. After closing the dialog (without any changes) and reopening it, the details appear to then be corrected and loaded from the solutions .UmbracoModelsBuilder.user file.

Yeah we are having this issue as well. We are using the Custom Tool for a lot of our projects, but when changing project the settings are not loaded.

odd - going to look into this
just to be sure, "multiple projects" = real different projects within the same VS solution, or different solutions?

Different solutions. E.g. Close one solution then open the next and the previous solution settings are still in place when you first try to connect or open the dialogue.

thanks - would be settings not being updated when opening / closing solutions - looking into it

Yeah same thing here. Does not matter if i open/close solutions using Team Explorer (Git) or the File menu, the setting is not updated until either closing VS or opening the options menu.

I don't know for sure from a technical standpoint but my guess is that the tool is an extension of Visual Studio (the host) itself so a change of context in regards to the solution does not make much if any difference to the host. This theory is supported by the fact that you can access the extension settings even with no solution open in Visual Studio.

Done in source. See core task 4880 for release.


Show what the system understands from message

Description
As a user, I would like the system to show me what it understood from my message.
Currently, a key-value pair is displayed, which does not mean much to a user of our system
Scope of Work

[ ] Create a mock-up of interaction
[ ] Either re-prompt the same question when the user indicates that the system did not understand correctly, or automatically deduce the correct answer.
[ ] Incorporate the understood facts within the textual response from the chatbot

Demo requirement
1.
Acceptance Criteria

The user types in a fact (e.g. tenant has not paid rent for 3 weeks)
Zeus says "I know how difficult it can be to collect rent. Your tenants haven't paid you in 3 weeks..."
User can click on "3 weeks" and change it to a different number (e.g. 4 weeks)

Documentation, files, diagrams, etc. relating to this feature:
Url, books, etc.
Changes:

[Optional]

This is already implemented within our system by #162


[1.5] Optimize namespace controller in Pilot (#20915)

Optimize namespace controller

Right now the ns controller runs at a rate of 2.5 namespaces/s due to
kube client rate limiting. We also resync every 30s. This means that if
you have over 75 namespaces, you will be constantly writing config map.
Even worse, this limit is shared with the rest of istiod.
There is no real reason to resync every 30s, its just excessive.  Note - Galley has never had a resync period and I
have never heard of a "missed event" issue as a result. Kubernetes
provides the same guidance.

fix lint

fix test

fix type

clean up per comments

improve error handling

fix nits

fix flake

(cherry picked from commit 7bcc71e51b87098bbd3da1523dcf6e9a94dbb5a3)

@howardjohn: The following test failed, say /retest to rerun all failed tests:

Test name
Commit
Details
Rerun command

integ-istioio-k8s-tests_istio_release-1.5
d97d52d3bd0f3ad82e176d069919766a268c1ae8
link
/test integ-istioio-k8s-tests_istio_release-1.5

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. I understand the commands that are listed here.

/retest


APEXMALHAR-2510 adding all matching keys to result for join accumulation

@chinmaykolhatkar @ShunxinLu please review.

I think this is good. Thanks for the quick response.

@Hitesh-Scorpio Can you check why the builds are failing?

@chinmaykolhatkar  In Jenkins I am getting the build success message but still it is failing with "Warning: this build has no associated authentication, so build permissions may be lacking, and downstream projects which cannot even be seen by an anonymous user will be silently skipped
Finished: UNSTABLE".
Travis is passing here as well as on my local machine. Should I close and reopen the PR?
--Hitesh

@Hitesh-Scorpio I tested the fix in an application. Even though the previous problem we discussed is fixed, the app still seems to be still unable to behave correctly. I dug deeper into the new problem and it looks like that Kryo creates couple more instances of join accumulation by calling its default constructor. And this wipes out all the keys (left, right) stored in the first place, so that when doing accumulation, the left and right keys are always empty, and therefore the inner join is not being performed correctly.
Making the default constructor do nothing and changing the member fields of AbstractPojoJoin to static kind of fix the issue. But I wonder if that's the correct way to do this. Could you please take a look into this problem as well? Thanks!

@ShunxinLu  I think you can open a separate JIRA for that issue and we can discuss it separately.

@Hitesh-Scorpio Agree. Will open a JIRA shortly. @chinmaykolhatkar I believe this PR is ready to merge.

@Hitesh-Scorpio @ShunxinLu  Thanks for resolution on this. I'll merge this PR in couple of days.

@Hitesh-Scorpio @ShunxinLu @chinmaykolhatkar closed due to inactivity


Upgrade pyarlo to 0.1.8 to support Arlo Baby monitor

Description:
Upgraded to Pyarlo to 0.1.8 to support Arlo Baby monitor
Example entry for configuration.yaml (if applicable):
arlo:
  username: foo
  password: bar

Checklist:

[x] The code change is tested and works locally.
[x] Local tests pass with tox. Your PR cannot be merged unless tests pass

If user exposed functionality or configuration variables are added/changed:

[ ] Documentation added/updated in home-assistant.github.io

If the code communicates with devices, web services, or third-party tools:

[x] New dependencies have been added to the REQUIREMENTS variable ([example][ex-requir]).
[x] New dependencies are only imported inside functions that use them ([example][ex-import]).
[x] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[ ] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

What about the Arlo Q and Arlo Q plus? will they also work now? have not been working since version 0.72.

are there more sensors coming with it? There are more than a standard Camera. Things like. The baby crying detection.. the temp/humidity/air quality that it has, etc.


Development: Improve grouping of e2e cypress page objects

Motivation and Context

This PR is purely improving the grouping of the page objects for Cypress. This should improve the readablity a bit and help writing new tests.
Steps for Testing

Tests are executed by Bamboo. All tests are still executed without any undefined failures
Review Progress

Code Review

[ ] Review 1
[ ] Review 2

There will be many merge conflicts coming up with the id refactorings. I will keep this PR blocked until the refactorings are done and then will solve all merge conflicts


Update issue templates

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 26.136%

Totals

Change from base Build<PHONE_NUMBER>0:
0.0%

Covered Lines:
68

Relevant Lines:
222

💛  - Coveralls


[api-minor] Set font size and color for text widget annotations

The display layer for annotation did not consider the font size in input fields.
I added the parsing and assigning of the font size of the input field. Aside from my own issues of PDFs not beeing correctly rendered on Screen, this fixes the too large rendered text fields in issue #7367 as well as the too small rendered text field in issue #11199 .
I did not change any rendering steps, as the font size seems to be considered there. One remaining issue are fields with font size "auto" which corresponds to size 0.
Fixes #7367.
Fixes #11199.

If #12831 gets merged, i would rewrite my changes to use the defaultAppearance parser and font-size calculations for auto-size provided in that PR

I've rewritten my old commit and now use the parsed default appearance data which was introduced by @calixteman in #12831 .
As this is my first PR, maybe someone can guide me how to go on from now? Just wait till someone is going to review this PR or is there anything to do now?

I've rewritten my old commit and now use the parsed default appearance data which was introduced by @calixteman in #12831 .
As this is my first PR, maybe someone can guide me how to go on from now? Just wait till someone is going to review this PR or is there anything to do now?

See also https://github.com/mozilla/pdf.js/wiki/Squashing-Commits

See also https://github.com/mozilla/pdf.js/wiki/Squashing-Commits

Please also follow https://github.com/mozilla/pdf.js/wiki/Squashing-Commits

Please also follow https://github.com/mozilla/pdf.js/wiki/Squashing-Commits

Looks good to me once the merge conflict is resolved (happened because we just merged #12886 that also touched the same code, but simplified it). We'll run a preview and the tests after this is done.

Looks good to me once the merge conflict is resolved (happened because we just merged #12886 that also touched the same code, but simplified it). We'll run a preview and the tests after this is done.

/botio-linux preview

/botio-linux preview

/botio test

/botio test

Thank you for fixing this!
/botio makeref

Thank you for fixing this!
/botio makeref

/botio-linux makeref

/botio-linux makeref


Email is not a link in Контакти section

Pull Request Template
Type of Pull Request *

[] CHANGE (fix or feature that would cause existing functionality to not work as expected)
[ ] FEATURE (non-breaking change which adds functionality)
[x] BUGFIX (non-breaking change which fixes an issue)
[ ] ENHANCEMENT  (non-breaking change which improves existing functionality)
[ ] NONE (if none of the other choices apply. For example, tooling, build system, CI, docs, etc.)

Related links
Issue link
'Conditions and Contacts' page: Email is not a link in 'Контакти' section
Story link
Story
Description *
Describe the big picture of your changes here.
If it fixes a bug or resolves a feature request, be sure to link to that issue.
###Summary of issue
Email is not a link in 'Контакти' section of the 'Condition and Contacts' page
###Summary of change
added few styles


Copy all files from src/main/appengine for staging

...Not just app.yaml

Are you sure? /src/main/appengine is not creating a 'context' the way a
docker root is supposed to.  Also looking at Ray's last email I'm starting
to question the validity of copying all of docker into the staging
directory.
On Thu, May 26, 2016 at 11:50 AM, meltsufin<EMAIL_ADDRESS>wrote:

...Not just app.yaml
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub
https://github.com/GoogleCloudPlatform/app-tools-lib-for-java/issues/96

I'm not sure, actually. I based this on the comment from Salmaan. But now I'm thinking that he meant the Docker-related files, when Dockerfile is in the appengine directory.
I think we should hold working on this until we get it all cleared up.

So, we've made the decision to copy all known and supported App Engine configuration files from src/main/appengine. If any other files are found in the directory, including the Dockerfile, we'll throw an error asking the user to remove the unsupported files. In the case of the Dockerfile, we'll instruct them to move the file under the src/main/docker folder.

@arouzrokh Do you have a list of all supported App Engine config files that can go into 'src/main/appengine'?

Let's take a step back. Assuming that we copy all files excluding the Dockerfile and know Docker related files (since they have to live in the docker folder), we'd be covering ourselves against all scenarios. Can you describe the reason behind this requirement?

I don't think we can know what all of the Docker-related files are. Hence, we took the whitelisting approach. We do, however, provide a special error message if we find Dockerfile in the appengine directory.


VSCode Language Server Extension

I just found out about the project and wanted to fiddle with it a bit, but when I searched for a Clue extension on VSCode it wasn't there.
I think that's something really useful for the userbase and should 100% be implemented.
Here's the official guide on how to make one and this one seems to be a bootstrapper tool to make a syntax highlighter
Typescript example

While it is nowhere near complete there is an extension for vscode
https://github.com/ClueLang/Clue-for-VSCode
It has not been published to the marketplace yet, so you have to manually install it for now

We have to make a ton of updates to Clue for vscode

The syntax highlighting is easy enough to fix once 3.0 is out, but should the language server be made for 3.0 or 4.0?

The syntax highlighting is easy enough to fix once 3.0 is out, but should the language server be made for 3.0 or 4.0?

it would be quite some work to implement all the relevant requests

A language server for 3.0 would just handle syntax errors and maybe some text completion.

A language server for 3.0 would just handle syntax errors and maybe some text completion.

and maybe implement goto and refactor related requests

What?

What?

like Go to definition and rename symbol

Oh. We will see.

Since a language server is now being worked on, should we close this?


I think your linux python3.5 1.2rc whl is actually installing TF 1.1.0, the Python 3.6 one works

Please go to Stack Overflow for help and support:
http://stackoverflow.com/questions/tagged/tensorflow
If you open a GitHub issue, here is our policy:

It must be a bug or a feature request.
The form below must be filled out.

Here's why we have that policy: TensorFlow developers respond to issues. We want to focus on work that benefits the whole community, e.g., fixing bugs and adding features. Support only helps individuals. GitHub also notifies thousands of people when issues are filed. We want them to see you communicating an interesting problem, rather than being redirected to Stack Overflow.

System information

Have I written custom code (as opposed to using a stock example script provided in TensorFlow):
OS Platform and Distribution (e.g., Linux Ubuntu 16.04):
Linux Ubuntu 16.04
TensorFlow installed from (source or binary):
https://storage.googleapis.com/tensorflow/linux/gpu/tensorflow_gpu-1.2.0rc1-cp35-cp35m-linux_x86_64.whl
TensorFlow version (use command below):
was trying to install 1.2rc but got 1.1.0
Bazel version (if compiling from source):
CUDA/cuDNN version:
8.0
GPU model and memory:
Titan X
Exact command to reproduce:

THIS CREATES THE PROBLEM:
source activate tfpy35
pip install --ignore-installed --upgrade https://storage.googleapis.com/tensorflow/linux/gpu/tensorflow_gpu-1.2.0rc1-cp35-cp35m-linux_x86_64.whl
python
>>> import tensorflow as tf
>>> print(tf.__version__)
1.1.0
IT SHOULD BE 1.2.0-RC1

THIS WORKS:
conda create --name tensorflow python=3
source activate tensorflow
pip install --ignore-installed --upgrade https://storage.googleapis.com/tensorflow/linux/gpu/tensorflow_gpu-1.2.0rc1-cp36-cp36m-linux_x86_64.whl
python
>>> import tensorflow as tf; print(tf.__version__)
1.2.0-rc1

Describe the problem
I am using anaconda and created a py3.5 env
I installed TF GPU as per https://www.tensorflow.org/versions/r1.2/install/install_linux#the_url_of_the_tensorflow_python_package
for python 3.5
But when I run python then import tensorflow as tf; print(tf.version)
I get 1.1.0
If I do exactly the same thing but create a python 3 enviornment and then load the 3.6 gpu whl it works
Source code / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached. Try to provide a reproducible test case that is the bare minimum necessary to generate the problem.
paul@SPEED:~$ conda create --name tfpy35 python=3.5
Fetching package metadata ...........
Solving package specifications: .

Package plan for installation in environment /home/paul/anaconda3/envs/tfpy35:

The following NEW packages will be INSTALLED:

    openssl:    1.0.2l-0
    pip:        9.0.1-py35_1
    python:     3.5.3-1
    readline:   6.2-2
    setuptools: 27.2.0-py35_0
    sqlite:     3.13.0-0
    tk:         8.5.18-0
    wheel:      0.29.0-py35_0
    xz:         5.2.2-1
    zlib:       1.2.8-3

Proceed ([y]/n)? y

python-3.5.3-1 100% |################################| Time: 0:00:03   4.96 MB/s
setuptools-27. 100% |################################| Time: 0:00:00   5.59 MB/s
wheel-0.29.0-p 100% |################################| Time: 0:00:00   7.59 MB/s
#
# To activate this environment, use:
# > source activate tfpy35
#
# To deactivate this environment, use:
# > source deactivate tfpy35

paul@SPEED:~$ source activate tfpy35

(tfpy35) paul@SPEED:~$ pip install --ignore-installed --upgrade https://storage.googleapis.com/tensorflow/linux/gpu/tensorflow_gpu-1.2.0rc1-cp35-cp35m-linux_x86_64.whl
Collecting tensorflow-gpu==1.2.0rc1 from https://storage.googleapis.com/tensorflow/linux/gpu/tensorflow_gpu-1.2.0rc1-cp35-cp35m-linux_x86_64.whl
  Using cached https://storage.googleapis.com/tensorflow/linux/gpu/tensorflow_gpu-1.2.0rc1-cp35-cp35m-linux_x86_64.whl
Collecting markdown==2.2.0 (from tensorflow-gpu==1.2.0rc1)
Collecting wheel>=0.26 (from tensorflow-gpu==1.2.0rc1)
  Using cached wheel-0.29.0-py2.py3-none-any.whl
Collecting numpy>=1.11.0 (from tensorflow-gpu==1.2.0rc1)
  Using cached numpy-1.12.1-cp35-cp35m-manylinux1_x86_64.whl
Collecting protobuf>=3.2.0 (from tensorflow-gpu==1.2.0rc1)
  Using cached protobuf-3.3.0-cp35-cp35m-manylinux1_x86_64.whl
Collecting werkzeug>=0.11.10 (from tensorflow-gpu==1.2.0rc1)
  Using cached Werkzeug-0.12.2-py2.py3-none-any.whl
Collecting bleach==1.5.0 (from tensorflow-gpu==1.2.0rc1)
  Using cached bleach-1.5.0-py2.py3-none-any.whl
Collecting html5lib==0.9999999 (from tensorflow-gpu==1.2.0rc1)
Collecting six>=1.10.0 (from tensorflow-gpu==1.2.0rc1)
  Using cached six-1.10.0-py2.py3-none-any.whl
Collecting setuptools (from protobuf>=3.2.0->tensorflow-gpu==1.2.0rc1)
  Using cached setuptools-36.0.1-py2.py3-none-any.whl
Installing collected packages: markdown, wheel, numpy, six, setuptools, protobuf, werkzeug, html5lib, bleach, tensorflow-gpu
Successfully installed bleach-1.5.0 html5lib-0.9999999 markdown-2.2.0 numpy-1.12.1 protobuf-3.3.0 setuptools-36.0.1 six-1.10.0 tensorflow-gpu-1.2.0rc1 werkzeug-0.12.2 wheel-0.29.0

(tfpy35) paul@SPEED:~$ python
Python 3.5.3 |Continuum Analytics, Inc.| (default, Mar  6 2017, 11:58:13)
[GCC 4.4.7 20120313 (Red Hat 4.4.7-1)] on linux
Type "help", "copyright", "credits" or "license" for more information.
>>> import tensorflow as tf
>>> print(tf.__version__)
1.1.0

@av8ramit can you take a look please?

I checked this on a clean nvidia docker image and I cannot reproduce the problem. Here are the commands I ran:
$ nvidia-docker run -it nvidia/cuda:8.0-cudnn5-devel-ubuntu16.04 bash
# apt-get update
# apt-get install python3-pip
# pip3  install --ignore-installed --upgrade https://storage.googleapis.com/tensorflow/linux/gpu/tensorflow_gpu-1.2.0rc1-cp35-cp35m-linux_x86_64.whl
# python3
>>> import tensorflow as tf
>>> tf.__version__
'1.2.0-rc1'

There are bugs around anaconda where sometimes it cannot install a new version even when --upgrade flag is provided. It is possible you are running into one of these.
You should be able to check again on a clean conda environment.
As I cannot reproduce this, I will close this bug as not reproducible.


Reserving x18 for AArch64 platforms

Currently reserving X18 register for all AArch64 platforms. This is a workaround if https://reviews.llvm.org/D145131 doesn't land

If you see my commit history I tried that and it doesn't work because that function doesn't get called when I am compiling for host/generic. Either that check has to be removed or we can only add this where I put it.

If you see my commit history I tried that and it doesn't work because that function doesn't get called when I am compiling for host/generic. Either that check has to be removed or we can only add this where I put it.

See line 117 for what I am talking about w.r.t. host/generic check

That's a very weird condition and a very misnamed function. That's annoying. Can you add a TODO to merge the functionality?

That's a very weird condition and a very misnamed function. That's annoying. Can you add a TODO to merge the functionality?

Done!


add unzip_either helper method.

Iterator::unzip collects an Iterator<Item = (A, B)> into (ExtendA, ExtendB). unzip_either is similar, but it collects each L and R
into separate collections.

This is essentially what Itertools::partition_map does.

@cuviper fantastic, I had a look in itertools and couldn't find it and had an internal debate as to which crate it belonged in.


Reflect 4.6.7 release

Summary of the changes / Why this improves CrateDB
🐌
Checklist

[x] Added an entry in CHANGES.txt for user facing changes
[x] Updated documentation & sql_features table for user facing changes
[x] Touched code is covered by tests
[x] CLA is signed
[x] This does not contain breaking changes, or if it does:

It is released within a major release
It is recorded in CHANGES.txt
It was marked as deprecated in an earlier release if possible
You've thought about the consequences and other components are adapted
(E.g. AdminUI)

Some unexpected test failures

Some unexpected test failures

yep I made a mistake in the version number declaration. Already fixed


Create compilable code examples using tut

Hey, I'm looking at good first issues tag to see where can I start doing small contributions and I found this one.
Can you elaborate a little bit more on this one @jdegoes?
The only lead I have on this is the 8af2db6 commit which actually is not very self-explanatory

@nebtrx Please see the website for tut.
We should have lots of executable code snippets as part of the documentation.

Cool thx! I'll take a look at the tool and the proper way to use it

In #163 I am doing most of the heavy-lifting.
I think this ticket here should probably be to replace the remaining non-tut blocks.
What do you think, @jdegoes ?

@NeQuissimus Sounds good to me!

Issue description updated


Fix inconsistent error behavior

Summary

restore serializeError
wrap provider.request to catch error and serialize to the same error format
nit: fix error type for invalid arg check

https://github.com/coinbase/coinbase-wallet-sdk/blob/965119c7a66bb5b8f94bfc47cb6813f260e40dd8/packages/wallet-sdk/src/provider/CoinbaseWalletProvider.ts#L471
How did you test your changes?

existing tests

Review Error for eric-ships @ 2024-05-09 23:33:30 UTC
User failed mfa authentication, see go/mfa-help


Fix syntax typo in code example in the Context README

Spotted a typo when copy/pasting a code example.

Hi @augustjk, I think this could be merged maybe? :)


Unknown Color Format error, continuous loop

This error loops infinitely and ends up crashing the browser.
Unknown color format! Error: Unknown color format!
at Object.toRGB (https://cdn.metroui.org.ua/v4/js/metro.min.js:7:15230)
at Object.isDark (https://cdn.metroui.org.ua/v4/js/metro.min.js:7:17464)
at Object.isLight (https://cdn.metroui.org.ua/v4/js/metro.min.js:7:17546)
at Object._createStructure (https://cdn.metroui.org.ua/v4/js/metro.min.js:7:208981)
at Object._create (https://cdn.metroui.org.ua/v4/js/metro.min.js:7:208439)
at Object.init (https://cdn.metroui.org.ua/v4/js/metro.min.js:7:208032)
at HTMLUListElement. (https://cdn.metroui.org.ua/v4/js/metro.min.js:7:5536)
at Function.each (http://localhost:55734/Scripts/jquery-3.3.1.js:354:19)
at jQuery.fn.init.each (http://localhost:55734/Scripts/jquery-3.3.1.js:189:17)
at jQuery.fn.init.t.fn.(anonymous function) [as tabs] (https://cdn.metroui.org.ua/v4/js/metro.min.js:7:5489)

I have to guess which code leads to errors?

Before create issue:
check for existing issues
create pen on codepen.io with your problem
describe the problem in detail

The tabs plugin fails on initialization.

Clear cache

please, if you want to receive answers, follow the three simple requirements for posing the problem


Implement VK audio API

[x] audio.get
[x] audio.getById
[x] audio.getLyrics
[x] audio.search
[x] audio.getUploadServer
[x] audio.save
[x] audio.add
[x] audio.delete
[x] audio.edit
[x] audio.reorder
[x] audio.restore
[x] audio.getAlbums
[x] audio.addAlbum
[x] audio.editAlbum
[x] audio.deleteAlbum
[x] audio.moveToAlbum
[x] audio.setBroadcast
[x] audio.getBroadcastList
[x] audio.getRecommendations
[x] audio.getPopular
[x] audio.getCount

The audio.getBroadcastList is unstable for now