« first day (2794 days earlier)      last day (118 days later) » 

12:00 AM
v3 has to do LSP I think...
 
REFRESH!
[Minesweeper] 126 Games Played. 84 Bombs Used. 15685 Moves Performed. 29 New Users
[Zomis/status-check] 63 additions. 0 deletions. 1 commits
[rubberduck-vba/Rubberduck] 1 issue comments
[Zomis/Duga] 4 additions. 2 deletions. 2 commits
 
@mansellan LSP was first mentioned in 2016 in this chatroom... yikes
 
ikr...
 
I just reread a bit of one of the first proper discussions on that...
 
It's actually easier to do it whilst we have everything in .Net. There are NuGets available.
 
12:04 AM
And noticed that I raised the issue of the VBE prettyprinting certain things and the compiled VBA possibly differing from the source code input..
 
huh?
 
mostly thundercode is an issue here...
like the use or bracketed names
 
you still talking about LSP?
 
especially of bracketed names for reserved identifiers
which is... basically unsolvable at the parser level with the setup we currently have anyways..
@mansellan yea. in a way
 
oh... yea i see
daaaang
LSP not designed for... "unusual" languages.
 
12:07 AM
VBA is not an unusual language
the VBE is just a horrible messy and actively sabotaging environment to extend
 
[_I
Disagree
A Bit]
As String
 
@mansellan yes
 
@mansellan um... how do line continuations work inside bracketed identifiers? while were at that?
 
@Vogel612 bah. clearly not a thunder user. My point stands, plenty of weirdness available.
 
12:33 AM
Can we up to net472? It's plenty old now, but lets you use many bits of C#10.
 
@mansellan good question
honestly we could even try for core 3, I think
 
the leap from framework to core is scary for some I think. and 4.8 is pointless. our company has been trying to move from 472 to core for ~2 years now..
472 with c#10 is pretty good tbh
 
we wanted to try for core basically since it reached version 2
 
our newer stuff is on 6. it's awesome.
 
 
3 hours later…
3:53 AM
 
 
2 hours later…
5:42 AM
while a number of projects probably can run on .net 5/6, the Rubberduck.VBEditor probably can't due to the typelib support.
 
 
5 hours later…
11:05 AM
Just to mention it, if we go LSP, we will have to send some data you usually do not sed. AFAIU, usually, you only send over source changes. We will also have to send info from the typelib API.
And we can basically only query the changes there on project level.
 
 
1 hour later…
12:10 PM
I've been round tripping a project between VBA and twinBasic. Rubberduck picks up an awful lot of fluff that is not yet flagged in twinBasic.
 
 
4 hours later…
3:43 PM
[rubberduck-vba/Rubberduck] build for commit f9baa8cf on next: AppVeyor build cancelled
BUILD FAILURE!
[rubberduck-vba/Rubberduck] build for commit f9baa8cf on next: CI failed.
BUILD FAILURE!
[rubberduck-vba/Rubberduck] build for commit f9baa8cf on next: CI failed.
BUILD FAILURE!
 
3:59 PM
The webhook URL format seems to have changed, as well as the content type. I think the hook setup is missing the "secret" ...would that be the PAT we've regenerated and encrypted on AppVeyor?
> {"message":"Webhook request does not contain signature."}
 
4:22 PM
Dammit this is so frustrating
 
4:48 PM
Webhook gets delivered, receives a 204 OK, ..and then nothing.
 
which webhook are we talking about?
 
5:08 PM
The AppVeyor CI hook that's supposed to trigger builds for PR and push events
 
5:42 PM
according to GH's setting, the content is application/x-www-url-encoded but AppVeyor's documentation seem to imply it's JSON.
 
[rubberduck-vba/Rubberduck] web-flow pushed commit 394cfab9 to next: Update appveyor.yml
[rubberduck-vba/Rubberduck] web-flow pushed commit 7a6bfed9 to next: Update appveyor.yml
[rubberduck-vba/Rubberduck] build for commit 7a6bfed9 on next: Error parsing appveyor.yml
BUILD FAILURE!
[rubberduck-vba/Rubberduck] web-flow pushed commit 0adff04b to next: Update appveyor.yml
[rubberduck-vba/Rubberduck] build for commit 0adff04b on next: Error parsing appveyor.yml
BUILD FAILURE!
 
looks like push is working (kinda) on next
 
[rubberduck-vba/Rubberduck] web-flow pushed commit 7c523c49 to next: Update appveyor.yml
 
6:04 PM
@Duga queued for 22 minutes, and counting... wtf
 
[rubberduck-vba/Rubberduck] build for commit 394cfab9 on next: AppVeyor build failed
BUILD FAILURE!
 
geez
wow nice, some random test failing out of the blue
at least it built
so push works, but not pr
I'm contacting support
 
6:20 PM
@this wrong webhook end.
Mat is talking about the webhook that sends a request to appveyor, not the ones we can trigger from appveyor
 
6:40 PM
> CI build isn't triggering, AppVeyor support says to try closing & reopening the pull request - just a heads-up that I'm going to try doing that.
 
redelivered the "opened" webhook payload...
still no luck it seems
 
> In your AppVeyor account GitHub is authorized as “GitHub App”, so repository-level webhooks won’t work. GitHub App uses a single centralized webhook handler.
 
that's under "Integrated Apps" in the settings
you might be able to update the access for the app here
 
> OK, it looks like "AppVeyor" GitHub App is not installed for account rubberduck-vba.
> I mean it's probably installed on GitHub side, but AppVeyor doesn't see it. Go to "New project" page in AppVeyor and do "Import existing installations".
[rubberduck-vba/Rubberduck] build for commit 7c523c49 on next: AppVeyor build failed
BUILD FAILURE!
> @FeodorFitsner now I can see the project twice... once with the (correct) buildnumber 6051 as the last build and once as the new project.
[rubberduck-vba/Rubberduck] build for commit 7c523c49 on next: CI failed.
BUILD FAILURE!
[rubberduck-vba/Rubberduck] build for commit 7c523c49 on next: CI failed.
BUILD FAILURE!
 
6:56 PM
wtf AV, why would you search for the sln there?
> msbuild "C:\projects\rubberduck\Rubberduck.sln"[..]
 
7:07 PM
@Duga that's the AV support guy!
 
@MathieuGuindon yea, I ran into him back when I was bugging them about csproj patching not working
 
> You don't need to create a new project under your user.
If you go to https://github.com/organizations/rubberduck-vba/settings/installations ensure you have "AppVeyor" app installed:

![image](https://user-images.githubusercontent.com/5041459/151674267-83231616-1f18-469a-a8e3-1c6446d56876.png)
 
^ that's for you, mat, cuz I can't go there
 
> @FeodorFitsner I confirm that AV is installed, and has the following permissions:

- Read access to code, members, metadata, and pull requests
- Read and write access to checks and commit statuses

Repository access
- All repositories
This applies to all current and future repositories.
 
Weird, I thought you had org-level admin access
 
7:17 PM
seems to require owner privs
 
in any case, the app is there and has the required accesses
> If you are planning to use GitHub App (vs OAuth) going forward then you can remove that webhook. Not sure what you mean by “org-level” webhook – AppVeyor expect org-level webhook configured only for syncing teams/memberships.
 
> OK, would you mind if I create a fake test PR and play with it?
> @FeodorFitsner absolutely no problem with that!
> null
 
I'm confused. if "your AppVeyor account GitHub is authorized as “GitHub App”, so repository-level webhooks won’t work" and then "AppVeyor expect org-level webhook configured only for syncing teams/memberships", and "you can remove that [repository-level] webhook" -- something isn't adding up
 
> I can see the GitHub webhook firing and receiving a 204 OK response, but on the AppVeyor side there's no event, and nothing happening.
> OK, thanks for letting know. That webhook is ignored when GitHub is authorized as an App.

However, it looks like we've found the issue. We'll take a deeper look at what's going on and deploy a bug fix later today. Thanks for your patience! I'll provide an update here.
 
7:37 PM
welp
good to know that apparently appveyor is that bad at their job :D
bit harsh, but eh
 
> That webhook is ignored when GitHub is authorized as an App
is it just me or that makes no sense at all??
like, I'd need to _un_authorize GitHub for it to work?
I guess we'll have to wait for the update
 
 
3 hours later…
10:34 PM
> We've deployed AppVeyor update with a fix. I've been able to start a new build of my test PR: https://ci.appveyor.com/project/rubberduck-vba-releasebot/rubberduck/history

Well, you have to close/open this PR again to start a new build.
[rubberduck-vba/Rubberduck] build for commit 634e8c93 on unknown branch: AppVeyor build succeeded
 
10:57 PM
Woot!
 
@Duga okay wow that's... new
We could really try to get that bot it's proper (bot) tag
 
[rubberduck-vba/Rubberduck] build for commit 634e8c93 on unknown branch: 97.58% (target 0.00%)
> @FeodorFitsner Thanks for the help :+1:
> OK, it looks like "AppVeyor" GitHub App is not installed for account rubberduck-vba.
> Sure, glad it works again!
> I mean it's probably installed on GitHub side, but AppVeyor doesn't see it. Go to "New project" page in AppVeyor and do "Import existing installations".
> @FeodorFitsner now I can see the project twice... once with the (correct) buildnumber 6051 as the last build and once as the new project.
> @FeodorFitsner I confirm that AV is installed, and has the following permissions:

- Read access to code, members, metadata, and pull requests
- Read and write access to checks and commit statuses

Repository access
- All repositories
This applies to all current and future repositories.
> OK, would you mind if I create a fake test PR and play with it?
> @FeodorFitsner absolutely no problem with that!
> You don't need to create a new project under your user.
If you go to https://github.com/organizations/rubberduck-vba/settings/installations ensure you have "AppVeyor" app installed:

![image](https://user-images.githubusercontent.com/5041459/151674267-83231616-1f18-469a-a8e3-1c6446d56876.png)
> cleaned up some comments from the troubleshooting of the AppVeyor issues we've been having
 
@Vogel612 sure!
 
11:45 PM
[rubberduck-vba/Rubberduck] 1508 stars vs. [decalage2/oletools] 1899 stars
 
something's still wrong with the damn coverage reporting.
blegh
 

« first day (2794 days earlier)      last day (118 days later) »