Rectangle 27 433

This is a known bug with the official Chromecast JavaScript library. Instead of failing silently, it dumps these error messages in all non-Chrome browsers as well as Chrome browsers where the Chromecast extension isn't present.

The Chromecast team have indicated they won't fix this bug.

If you are a developer shipping with this library, you can't do anything about it according to Chromecast team. You can only inform users to ignore the errors. (I believe Chromecast team is not entirely correct as the library could, at the least, avoid requesting the extension scipt if the browser is not Chrome. And I suspect it could be possible to suppress the error even if it is Chrome, but haven't tried anything.)

If you are a user annoyed by these console messages, you can switch to Chrome if not using it already.

Wow. This is like leaving all your console.log() statements in a production product.

@RenaissanceProgrammer Using Chrome and installing Chromecast solves it for you individually, yes. The question is more aimed at programmers who want to remove the problem for their end-users.

Hey, it's now Feb, '16 and I have the latest version of Chrome and it hasn't been fixed. Any updates?

It's March 7th 2016. Chrome just updated, I'm still getting the console errors.

javascript - Google chrome cast sender error if chrome cast extension ...

javascript google-chrome-extension google-chrome-devtools chromecast
Rectangle 27 433

This is a known bug with the official Chromecast JavaScript library. Instead of failing silently, it dumps these error messages in all non-Chrome browsers as well as Chrome browsers where the Chromecast extension isn't present.

The Chromecast team have indicated they won't fix this bug.

If you are a developer shipping with this library, you can't do anything about it according to Chromecast team. You can only inform users to ignore the errors. (I believe Chromecast team is not entirely correct as the library could, at the least, avoid requesting the extension scipt if the browser is not Chrome. And I suspect it could be possible to suppress the error even if it is Chrome, but haven't tried anything.)

If you are a user annoyed by these console messages, you can switch to Chrome if not using it already.

Wow. This is like leaving all your console.log() statements in a production product.

@RenaissanceProgrammer Using Chrome and installing Chromecast solves it for you individually, yes. The question is more aimed at programmers who want to remove the problem for their end-users.

Hey, it's now Feb, '16 and I have the latest version of Chrome and it hasn't been fixed. Any updates?

It's March 7th 2016. Chrome just updated, I'm still getting the console errors.

javascript - Google chrome cast sender error if chrome cast extension ...

javascript google-chrome-extension google-chrome-devtools chromecast
Rectangle 27 433

This is a known bug with the official Chromecast JavaScript library. Instead of failing silently, it dumps these error messages in all non-Chrome browsers as well as Chrome browsers where the Chromecast extension isn't present.

The Chromecast team have indicated they won't fix this bug.

If you are a developer shipping with this library, you can't do anything about it according to Chromecast team. You can only inform users to ignore the errors. (I believe Chromecast team is not entirely correct as the library could, at the least, avoid requesting the extension scipt if the browser is not Chrome. And I suspect it could be possible to suppress the error even if it is Chrome, but haven't tried anything.)

If you are a user annoyed by these console messages, you can switch to Chrome if not using it already.

Wow. This is like leaving all your console.log() statements in a production product.

@RenaissanceProgrammer Using Chrome and installing Chromecast solves it for you individually, yes. The question is more aimed at programmers who want to remove the problem for their end-users.

Hey, it's now Feb, '16 and I have the latest version of Chrome and it hasn't been fixed. Any updates?

It's March 7th 2016. Chrome just updated, I'm still getting the console errors.

javascript - Google chrome cast sender error if chrome cast extension ...

javascript google-chrome-extension google-chrome-devtools chromecast
Rectangle 27 433

This is a known bug with the official Chromecast JavaScript library. Instead of failing silently, it dumps these error messages in all non-Chrome browsers as well as Chrome browsers where the Chromecast extension isn't present.

The Chromecast team have indicated they won't fix this bug.

If you are a developer shipping with this library, you can't do anything about it according to Chromecast team. You can only inform users to ignore the errors. (I believe Chromecast team is not entirely correct as the library could, at the least, avoid requesting the extension scipt if the browser is not Chrome. And I suspect it could be possible to suppress the error even if it is Chrome, but haven't tried anything.)

If you are a user annoyed by these console messages, you can switch to Chrome if not using it already.

If you are a user annoyed by these console messages, you can switch to Chrome if not using it already and install the Chromecast extension. (I mention that because people are landing here after searching for this error.)

Update [Nov 13, 2014]: The problem has now been acknowledged by Google. A member of the Chromecast team seems to suggest the issue will be bypassed by a change the team is currently working on.

Update 2 [Feb 17, 2015]: The team claim there's nothing they can do to remove the error logs as it's a standard Chrome network error and they are still working on a long-term fix. Public comments on the bug tracker were closed with that update.

Wow. This is like leaving all your console.log() statements in a production product.

@RenaissanceProgrammer Using Chrome and installing Chromecast solves it for you individually, yes. The question is more aimed at programmers who want to remove the problem for their end-users.

Hey, it's now Feb, '16 and I have the latest version of Chrome and it hasn't been fixed. Any updates?

I hope they fix it soon, cause we're still getting those errors without the Chromecast extension.

It's March 7th 2016. Chrome just updated, I'm still getting the console errors.

After being forced to install the plugin, I get 4 'untrusted origin' warnings from the same script. It's over, Google won.

javascript - Google chrome cast sender error if chrome cast extension ...

javascript google-chrome-extension google-chrome-devtools chromecast
Rectangle 27 430

There is a known bug with specifying default command timeout within the EF connection string.

Remove the value from the connection string and set it on the data context object itself. This will work if you remove the conflicting value from the connection string.

this.context.Database.SetCommandTimeout(180);
this.context.Database.CommandTimeout = 180;
((IObjectContextAdapter)this.context).ObjectContext.CommandTimeout = 180;
this.context.CommandTimeout = 180;

I have updated the accepted answer be a community wiki since this API seems to change every so often. Now anyone can help keep the accepted answer accurate. Thanks everyone!

How can I achieve this using edmx?

In which version of the EntityFramework is this fixed? I can't find the EF bug for it.

I don't believe this is a bug, but rather by design, see Remarks section here link

Because some settings are in ms and some in s, I looked it up here, CommandTimeout is in seconds.

c# - Entity Framework Timeouts - Stack Overflow

c# asp.net entity-framework entity-framework-4 connection-string
Rectangle 27 419

There is a known bug with specifying default command timeout within the EF connection string.

Remove the value from the connection string and set it on the data context object itself. This will work if you remove the conflicting value from the connection string.

this.context.Database.SetCommandTimeout(180);
this.context.Database.CommandTimeout = 180;
((IObjectContextAdapter)this.context).ObjectContext.CommandTimeout = 180;
this.context.CommandTimeout = 180;

I have updated the accepted answer be a community wiki since this API seems to change every so often. Now anyone can help keep the accepted answer accurate. Thanks everyone!

How can I achieve this using edmx?

In which version of the EntityFramework is this fixed? I can't find the EF bug for it.

I don't believe this is a bug, but rather by design, see Remarks section here link

Because some settings are in ms and some in s, I looked it up here, CommandTimeout is in seconds.

c# - Entity Framework Timeouts - Stack Overflow

c# asp.net entity-framework entity-framework-4 connection-string
Rectangle 27 189

This is a known bug under MinGW. Relevant Bugzilla. In the comments section you can get a patch to make it work with MinGW.

This issue has been fixed in MinGW-w64 distros higher than GCC 4.8.0 provided by the MinGW-w64 project. Despite the name, the project provides toolchains for 32-bit along with 64-bit. The Nuwen MinGW distro also solves this issue.

Thank you! I didn't have the courage to point a finger at the mighty g++. Even if I do it in future now (as a last resort), I now know the official place to confirm my conspiracy theories. Thank you!

I'm using MinGW-w64 version 4.8.1 and it is not working. I copied the exact program from the question. I still get the 'to_string' is not a member of 'std' error. I compiled it as: g++ -std=c++0x -o tostring_test.exe tostring_test.cpp

@zam664 I can't explain why, but I got std::to_string to work by installing MinGW 4.8.1 (specifically, x32-4.8.1-posix-dwarf-rev5) through MinGW-builds. In contrast, to_string did not work with MinGW 4.8.1 installed through either the "mingw-get" installer or the TDM-GCC package.

#define _GLIBCXX_USE_C99 1
C:\MinGW\lib\gcc\mingw32\4.8.1\include\c++\mingw32\bits\c++config.h

@Cerran "MinGW-builds" are builds of MinGW-w64, a different project to MinGW. One reason that MinGW-w64 was forked off was so they they could in fact fix bugs like the one this thread was about.

c++ - to_string is not a member of std, says g++ (mingw) - Stack Overf...

c++ c++11 g++ mingw tostring
Rectangle 27 188

This is a known bug under MinGW. Relevant Bugzilla. In the comments section you can get a patch to make it work with MinGW.

This issue has been fixed in MinGW-w64 distros higher than GCC 4.8.0 provided by the MinGW-w64 project. Despite the name, the project provides toolchains for 32-bit along with 64-bit. The Nuwen MinGW distro also solves this issue.

Thank you! I didn't have the courage to point a finger at the mighty g++. Even if I do it in future now (as a last resort), I now know the official place to confirm my conspiracy theories. Thank you!

I'm using MinGW-w64 version 4.8.1 and it is not working. I copied the exact program from the question. I still get the 'to_string' is not a member of 'std' error. I compiled it as: g++ -std=c++0x -o tostring_test.exe tostring_test.cpp

@zam664 I can't explain why, but I got std::to_string to work by installing MinGW 4.8.1 (specifically, x32-4.8.1-posix-dwarf-rev5) through MinGW-builds. In contrast, to_string did not work with MinGW 4.8.1 installed through either the "mingw-get" installer or the TDM-GCC package.

#define _GLIBCXX_USE_C99 1
C:\MinGW\lib\gcc\mingw32\4.8.1\include\c++\mingw32\bits\c++config.h

@Cerran "MinGW-builds" are builds of MinGW-w64, a different project to MinGW. One reason that MinGW-w64 was forked off was so they they could in fact fix bugs like the one this thread was about.

c++ - to_string is not a member of std, says g++ (mingw) - Stack Overf...

c++ c++11 g++ mingw tostring
Rectangle 27 3

This is a (known) bug in Chrome for iOS. If you want to report it so you can get notified when it's fixed, file a bug and pick "iOS issue" from the Template menu.

Chrome for IOS not opening new window correctly in iframe - Stack Over...

ios google-chrome
Rectangle 27 2

This is a known bug in the chrome webdriver. Ex1, Ex2

After a very brief read, it looks like their developers are having some trouble reproducing the bug. @dimkin mentioned CDNs as a possible cause for the bug. It looks like others have reported the bug and have similar suspicions that cdn content is not resolving DNS appropriately.

I was able to isolate the issue. In my case it was happening only for pages referencing a static file (an image in a HTML tag for instance http://cdn.local.myproject.net/static/myimage.png) on my custom local cdn domain. The was not present if I used a relative path "/static/myimage.png" or localhost "http://127.0.0.1/static/myimage.png" so I figured it was a DNS problem.

I was able to bypass the problem by using the --dns-prefetch-disable option of chrome.

from selenium import webdriver
from selenium.webdriver.chrome.options import Options
chrome_options = Options()
chrome_options.add_argument("--dns-prefetch-disable")
driver = webdriver.Chrome(chrome_options=chrome_options)

Another workaround mentioned looks promising. It doesn't fix anything but could possibly get around the problem. It catches the exception and simply attempts a refresh:

from selenium.common.exceptions import TimeoutException
try:
   webDriver.get(url);
except TimeoutException as ex:
   print(ex.Message)
   webDriver.navigate().refresh()

A question regarding the code in the yellow boy: where do you define the options in the six line?

Sorry, that came from a direct cut and paste from the bug report. I've corrected the code sample and it should run now.

Ok, thanks. Just tried the upper one out but still I get the timeout errors. About the second code: Where do I have to insert this? Looks like Javascript bc of the curly brackets....Sorry for being such a beginner.

Ok, even downgraded the Mac, problem still persists...

Chrome Webdriver produces timeout in Selenium - Stack Overflow

google-chrome selenium webdriver
Rectangle 27 5

The actual answer: It's a known, verified bug. *(recently fixed!... ma...

Looks like a known, longstanding issue with Chrome: http://crbug.com/39402

If you want it fixed sooner, star the issue. More people starring the issue will likely increase its priority and possibly get it fixed faster.

****UPDATE 1***: As of May 15 of this year (2013)--four years after this question was asked--it looks like the issue has been fixed in version 29: http://crbug.com/39402#c47

Feel free to undo all your hacks and workarounds. :]

****UPDATE 2 (2015-01)***: This is apparently still an issue for some users, according to the same issue link. :/

2016 and still getting "404 Not Found" in Chrome.

Why is Chrome searching for my favicon.ico when I serve up a file from...

asp.net-mvc favicon
Rectangle 27 5

The actual answer: It's a known, verified bug. *(recently fixed!... ma...

Looks like a known, longstanding issue with Chrome: http://crbug.com/39402

If you want it fixed sooner, star the issue. More people starring the issue will likely increase its priority and possibly get it fixed faster.

****UPDATE 1***: As of May 15 of this year (2013)--four years after this question was asked--it looks like the issue has been fixed in version 29: http://crbug.com/39402#c47

Feel free to undo all your hacks and workarounds. :]

****UPDATE 2 (2015-01)***: This is apparently still an issue for some users, according to the same issue link. :/

2016 and still getting "404 Not Found" in Chrome.

Why is Chrome searching for my favicon.ico when I serve up a file from...

asp.net-mvc favicon
Rectangle 27 19

It is a known bug in node.js that has been recently fixed (although not backported to v0.10).

There is a workaround where you alter the command-line for each worker process, although the API was not meant to be used this way (the workaround might stop working in the future). Here is the source code from the github issue:

var cluster = require('cluster');
var http = require('http');

if (cluster.isMaster) {
  var debug = process.execArgv.indexOf('--debug') !== -1;
  cluster.setupMaster({
    execArgv: process.execArgv.filter(function(s) { return s !== '--debug' })
  });
  for (var i = 0; i < 2; ++i) {
    if (debug) cluster.settings.execArgv.push('--debug=' + (5859 + i));
    cluster.fork();
    if (debug) cluster.settings.execArgv.pop();
  }
}
else {
  var server = http.createServer(function(req, res) {
    res.end('OK');
  });
  server.listen(8000);
}

Is there a way to achieve the same thing with child.fork()?

@GuyKorland Of course, just add --debug={port} to command-line arguments of your child process.

I struggled on this because I affected the child_process module to a local variable called process, hiding the node process global variable, hence process.execArgv was not defined. Beaware "process" is a node global variable!

debugging - How to debug Node.JS child forked process? - Stack Overflo...

node.js debugging intellij-idea
Rectangle 27 19

It is a known bug in node.js that has been recently fixed (although not backported to v0.10).

There is a workaround where you alter the command-line for each worker process, although the API was not meant to be used this way (the workaround might stop working in the future). Here is the source code from the github issue:

var cluster = require('cluster');
var http = require('http');

if (cluster.isMaster) {
  var debug = process.execArgv.indexOf('--debug') !== -1;
  cluster.setupMaster({
    execArgv: process.execArgv.filter(function(s) { return s !== '--debug' })
  });
  for (var i = 0; i < 2; ++i) {
    if (debug) cluster.settings.execArgv.push('--debug=' + (5859 + i));
    cluster.fork();
    if (debug) cluster.settings.execArgv.pop();
  }
}
else {
  var server = http.createServer(function(req, res) {
    res.end('OK');
  });
  server.listen(8000);
}

Is there a way to achieve the same thing with child.fork()?

@GuyKorland Of course, just add --debug={port} to command-line arguments of your child process.

I struggled on this because I affected the child_process module to a local variable called process, hiding the node process global variable, hence process.execArgv was not defined. Beaware "process" is a node global variable!

debugging - How to debug Node.JS child forked process? - Stack Overflo...

node.js debugging intellij-idea
Rectangle 27 3

Unfortunately this is a known bug in the DragPanelExtender. I would recommend dropping the modal extender all together if it's an option and you're comfortable with javascript.

<form id="form1" runat="server">
  <br />
  Clicking the button will bring up the modal dialog<br />
  <br />    
  <div>
    <br />
    <asp:Button ID="Button1" runat="server" Text="Button" />
    <br />
    <div id="myModal" Style="display: None" background="#CCCCCC" title="Caption/Dialog Title">
        <table>
            <tr>
                <td>
                    <asp:Label ID="lblFirst" runat="server" Text="First" />
                </td>
                <td>
                    <asp:TextBox ID="txtFirst" runat="server" />
                </td>
            </tr>
            <tr>
                <td>
                    <asp:Label ID="lblLast" runat="server" Text="Last" />
                </td>
                <td>
                    <asp:TextBox ID="txtLast" runat="server" />
                </td>
            </tr>
        </table>
    </div>
    <asp:Label ID="lblMessage" runat="server"></asp:Label>
    <br />
    <br />
    </div>
</form>
<script type="text/javascript">
  $(function() {
    $("#<%= Button1.ClientID %>").click() {
      $("#myModal").dialog({ buttons: { "Ok": function() { $(this).dialog("close"); } } });
    }
  });
</script>

This is a whole different way of programming, but results in a much richer UI experience for the user. If you're willing to learn jQuery and how it hooks up, it's a really natural/fluid syntax that can add a great deal of power/flexibility to your web pages. Now keep in mind that I prefer jQuery but that there are many other javascript libraries available. You should at least browse around and see what looks the most comfortable if you're just getting started...it's possible since you're from a VB background (I'm from C#) that another libraries coding style/syntax is much more appealing.

Now if you're unwilling to go down that road and it's too unfamiliar, your only alternative as far as I can see is to do what you don't want to...compile the AJAX Control Toolkit yourself. If you want to go this route, grab the latest source from codeplex and modify the below section of Release\AjaxControlToolkit\Compat\DragDrop\DragDropScripts.js:

_drag: function(isInitialDrag) {
  var ev = window._event;
  var mousePosition = { x: ev.clientX, y: ev.clientY };
_drag: function(isInitialDrag) {
  if (!this._activeDragVisual) return;
  var ev = window._event;
  var mousePosition = { x: ev.clientX, y: ev.clientY };

The _onScrollerTick operation in certain browsers bombs out and nulls the dragVisual function. Credit is due here: A post on the ASP.Net forums by freakyer led me down this debug path to figure out where it's breaking...but I see no other solution as there is an actual bug in certain browsers not-fixable without a script change and recompile.

OK, I'll buy your answer, tho not the one I hoped for. Thx

Sorry it's not what you're after...I've run into the same problems with the toolkit before and had to run a custom build before they were fixed months later. There's a lot of work being done for 4.0 where they're incorporating the toolkit into the overall Microsoft AJAX Framework (or whatever it's called this week), hopefully some of the bugs like you're seeing will be taken care of soon. Also, the toolkit has changed over to the CodePlex Foundation, so they can take community patches much more easily, it's possible you can provide this fix to them and see it in the next build.

vb.net - ModalPopupExtender: Dragging dialog box results in 'scrolllef...

vb.net ajax visual-studio-2008 modalpopupextender
Rectangle 27 3

This is a known bug in Eclipse, tracked here:

Awesome, thanks Ben. I saw reference to a similar bug in my searching, but it was from long ago and I didn't expect such an issue to be present in a mainstream ide.....

Why is eclipse adding single quotes to my C command line parameters? -...

c eclipse debugging command-line quotes
Rectangle 27 7

This is a known bug, that will be fixed in ICS MR1.

anyone know the bug url?

I'm still seeing a similar (if not identical) leak in Android L.

Maybe this workaround might help you : stackoverflow.com/a/27231817/1532108

android - Why does EditText retain its Activity's Context in Ice Cream...

android memory-leaks android-4.0
Rectangle 27 12

This is a known bug in the 7.1 betas which was never fixed in the final release.

Like you, I have had the same problem and had to set it manually as a fix.

It is recommended that if you want to set a global tint color, to do so in -application:will/didFinishLaunchingWithOptions:. Alternatively, if you want specific colors for each view controller, to do so in prepareForSeque:.

Personally I have tried setting it in -viewWillAppear:animated: in my UINavigationController root view and it appears to work fine.

The jist of the thread is that you must manually set the tint color. The recommended way is in your application delegate didFinishLaunching method.

uitabbarcontroller - Storyboard Global Tint UITabBar Tint changed in I...

ios uitabbarcontroller
Rectangle 27 4

According to the Firebase Google Group, this is a known bug with Firebase:

This is a known bug on our end. As you noted, after deleting a user, existing auth tokens are still valid and can be used to read and write to your Firebase database. Security Rules are still enforced on these tokens and that user will still only be able to access their own Firebase data (if your rules are set up as such). Those auth tokens will be valid until they expire. There is currently no workaround for this bug although we are going to be fixing this in a future release.

The only thing I can think to do is check whether you can read to your users area, and if there's nothing there, force a log out.

I'm having a similar issue. Pretty frustrating that they don't have a workaround yet. I'd think it would be pretty simple to implement a check for if their token corresponds to an authenticated user or not.

check whether you can read to your users area, and if there's nothing there, force a log out
with
withCancel

firebase - Remove a user through dashboard, but the user is still logg...

firebase appcelerator firebase-authentication
Rectangle 27 4

According to the Firebase Google Group, this is a known bug with Firebase:

This is a known bug on our end. As you noted, after deleting a user, existing auth tokens are still valid and can be used to read and write to your Firebase database. Security Rules are still enforced on these tokens and that user will still only be able to access their own Firebase data (if your rules are set up as such). Those auth tokens will be valid until they expire. There is currently no workaround for this bug although we are going to be fixing this in a future release.

The only thing I can think to do is check whether you can read to your users area, and if there's nothing there, force a log out.

I'm having a similar issue. Pretty frustrating that they don't have a workaround yet. I'd think it would be pretty simple to implement a check for if their token corresponds to an authenticated user or not.

check whether you can read to your users area, and if there's nothing there, force a log out
with
withCancel

firebase - Remove a user through dashboard, but the user is still logg...

firebase appcelerator firebase-authentication