-
-
Notifications
You must be signed in to change notification settings - Fork 775
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
WOC: Update Gitcoin for breaking MetaMask changes #1992
WOC: Update Gitcoin for breaking MetaMask changes #1992
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1992 +/- ##
=======================================
Coverage 25.41% 25.41%
=======================================
Files 132 132
Lines 10842 10842
Branches 1449 1449
=======================================
Hits 2755 2755
Misses 8009 8009
Partials 78 78 Continue to review full report at Codecov.
|
@@ -652,7 +652,7 @@ input[type=text].loading { | |||
color: #4aeba8; | |||
} | |||
|
|||
.submit_bounty select[name=deonomination] { | |||
.submit_bounty select[name=denomination] { |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
You'll want to update your master branch and this PR branch from our upstream to remove these previously introduced line changes.
hey @zevaverbach, wanted to check in and see if you were able to give @mbeacom's comments some thought! I've snoozed Gitcoin bot for you on the main issue page. |
Hey sorry for the radio silence here. I’ll be trimming that stuff out and
moving ahead on this issue this week.
…On Thu, Aug 23, 2018 at 12:55 PM, Frank ***@***.***> wrote:
hey @zevaverbach <https://github.com/zevaverbach>, wanted to check in and
see if you were able to give @mbeacom <https://github.com/mbeacom>'s
comments some thought! I've snoozed Gitcoin bot for you on the main issue
page.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1992 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACtRNHphcvxSwGMrSW9FkftYlVeWOFVnks5uTt5vgaJpZM4V5URV>
.
|
Thanks for the update @zevaverbach! |
hey @zevaverbach are you still interested in this? |
@owocki yes I would like to come back to this. Would by the end of October
be soon enough?
On Sat, Oct 6, 2018 at 5:26 PM Kevin Owocki ***@***.***> wrote:
@zevaverbach <https://github.com/zevaverbach> ?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1992 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACtRNNq_49GLKEBkUINq1h2emjY_zV2Yks5uiR_3gaJpZM4V5URV>
.
--
Zev Averbach
Averbach Transcription
(802) 276-5934
avtranscription.com <http://www.avtranscription.com/>
|
@zevaverbach how late in October? dropdead date for this is November 2nd per the metamask post |
I know it's cutting it close, but how about by midnight on Sunday 10/28?
Zev Averbach
Averbach Transcription
(802) 276-5934
avtranscription.com <http://www.avtranscription.com/>
…On Thu, Oct 11, 2018 at 11:59 AM, Kevin Owocki ***@***.***> wrote:
@zevaverbach <https://github.com/zevaverbach> how late in October?
dropdead date for this is November 2nd per the metamask post
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1992 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/ACtRNEwFOZGG5S-LDSRkPt1mXxMEO4yGks5uj2rWgaJpZM4V5URV>
.
|
I think we can live with that.
On Fri, Oct 12, 2018 at 9:22 AM Zev Averbach <[email protected]>
wrote:
… I know it's cutting it close, but how about by midnight on Sunday 10/28?
Zev Averbach
Averbach Transcription
(802) 276-5934
avtranscription.com <http://www.avtranscription.com/>
On Thu, Oct 11, 2018 at 11:59 AM, Kevin Owocki ***@***.***>
wrote:
> @zevaverbach <https://github.com/zevaverbach> how late in October?
> dropdead date for this is November 2nd per the metamask post
>
> —
> You are receiving this because you were mentioned.
> Reply to this email directly, view it on GitHub
> <#1992 (comment)>, or
mute
> the thread
> <
https://github.com/notifications/unsubscribe-auth/ACtRNEwFOZGG5S-LDSRkPt1mXxMEO4yGks5uj2rWgaJpZM4V5URV
>
> .
>
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#1992 (comment)>, or mute
the thread
<https://github.com/notifications/unsubscribe-auth/AAfXianA8uoM3Tzn7ssBL4Mia3jRrTQHks5ukLO6gaJpZM4V5URV>
.
_________________________________________
check out what i'm building on github <http://github.com/owocki>
or what i'm shooting on photoshelter <http://photography.owocki.com/>
or find me on twitter <http://www.twitter.com/owocki>, facebook
<http://www.facebook.com/kevinowocki>, instagram
<http://instagram.com/owocki>, linkedin <http://www.linkedin.com/in/owocki>,
and owocki.com <http://www.owocki.com/?utm_source=emailsig>.
see you around teh internets!
PS -- Come to the next Boulder Blockchain
<https://www.meetup.com/Boulder-Blockchain/> meetup. Be there or be ^ 2.
PPS -- Have I mentioned that *G**itcoin is live?* More @ https://gitcoin.co
|
FYI -- theres a new post from metamask about how to update dapps to the new metamask => https://medium.com/metamask/eip-1102-preparing-your-dapp-5027b2c9ed76 |
Addressed in #2548 |
Description
I will replace all direct reliance on injected web3 with a check to request permission and initialize web3 manually.
NOTE: This will not work with the current release of Metamask, but rather with this branch, which hopefully will be the current release by November 2018.
Checklist
Affected core subsystem(s)
Testing
Refers/Fixes
Fixes #1964 (once completed)