Can't copy ABI on new remix - ethereum

I have been trying to copy the ABI of my contract but when I copy and paste it, what I see is "[ ]". Please help

I faced this issue in Google Chrome. This issue resolved itself by changing the browser to Mozilla Firefox.

Related

Cloud Shell: Editor is not loading in incognito mode

So I have been following the following step for past few months:
Log in to Google Cloud Console from Chrome's incognito mode
Activate Cloud Shell
From there, I usually opened Editor and managed my files in a new window
Today while I was following the above steps, this issue raised up:
Basically, I cannot open editor anymore. I have already went through similar posts, and my issue is that I am using incognito where browser extensions or cookies shouldn't be an issue.
I am facing this problem for the first time and if anyone knows what is the cause or any suggestions would be appreciated.
EDIT:
For now Microsoft Edge InPrivate Mode is working for me. I am still interested in fixing the issue for Chrome.
Have reported the issue in Issue Tracker. Please "start" for more attention.
This started happening recently because third-party cookies stopped being supported in Incognito mode as of Chrome 83. Third-party cookies are required for the editor to work because of the way the open-source Theia IDE is integrated into Cloud Shell. The team is exploring various fixes, but in the mean time the following workaround should work:
In Incognito Mode, click on the crossed out 'eye' icon on the address bar.
Click on 'Site not working?'
Click on 'Allow cookies'
Safari problem stems from the same issue, but I am not certain if a similar workaround exists.
I've encountered the same issue myself (I tried this on Chrome running on both ChromeOS and MacOS) - it looks like a bug so in this case I'd recommend reporting it on Google's Issuetracker (you can even put a link to this post).
UNfortunately it looks like it's not just the Chrome browser. I tried this on Safari 13.1 and found the issue you described is also present.
I didn't check other browsers but IssueTracker is the way to go. And be patient :)

Google Colab not responding

I have a Google Colab notebook which was working properly before but now it does not respond at all. When I execute a cell containing a simple python Hello World program, the cell starts to run but does not give any response. Even I cannot interrupt the execution.
When I open this notebook in an incognito tab, it works. I tried with clearing browser cache but it did not work.
My other notebooks work without any problem.
I am using Google Chrome browser.
Please try by reinstalling the google chrome.

Typing accents (diacritics) in a Google Docs document, using Google Chrome in Ubuntu 16.04

On the other hand, I can do it everywhere: the address bar, in a Google Spreadsheet... even in a Google Docs document using Mozilla Firefox.
I am having this same problem since Version 53.0.2785.101 (64-bit). It works on every site, except Google docs products. On a spreadsheet it only works if I type on the formula bar. If I type on any cell it doesn't.
So I found others are having the same issue here. Reverting back to version 52 solved the issue for me, so it is for sure an issue with version 53. I reported the issue to Google Chrome and I suggest you do the same.

Google Apps Script editor not launching

From this morning I have no possibility to edit scripts. My existing script link to a spreadsheet continue to work but when I try to edit them or to edit a new one , I only get a shaded upper bar, and no possibility to use it.
Last times one of my scripts was getting some errors, is it possible that google "ban" me from using script due to too much memory using?
Thanks in advance,
david
I used Chrome Incognito mode as a temporary fix.
Hopefully, this works for you as well.
Switch you drive locale settings to English and it will work. This is a temporary workaround to use until they fix the bug. see issue 4339
Turned out I was still signed into another account despite the UI suggesting otherwise. Restarting the browser and checking who you are logged in as in Drive (and potentially signing the incorrect user out) fixed the problem for me.
Exactly. I was signed with different account without permits. Request access to the Sheet with full access without restrictions and it will work :)

ScriptDB Visualiser not working ?Caja

I have been using the excellent ScriptDB visualiser to help develop a google-apps-script.
This uses the HTMLService and worked last week, but now I cannot get it to work.
The HTML still is served & loads, but no javascript runs. When a button is clicked the error console (in firefox) gives the error;
Error: shouldn't happen: ES5/3 object passed to makeDOMAccessible
Source File: https://ssl.gstatic.com/caja/5346m/es53-taming-frame.opt.js?debug=1
Line: 1788
I suspect some Caja issue, but I went to the Caja playground and could not make any headway.
Any suggestions how to get this working again.
As the message suggests, this shouldn't happen.
That is, this is an internal bug in Caja or possibly Google Apps Script's use of Caja. Please report it on the Caja issue tracker including a (preferably as short as you can make it) example of HTML which causes the error (preferably when run in the Caja Playground, but if not then in Google Apps Script).