[beta] fixes instrumentation & adds e2e tests for coverage

fixes instrumentation (cache key not using the instrument option)
adds a unit test for the above
fixes double instrumentation when babel is enabled
adds unit tests for the aboce
adds e2e tests for instrumentations (coverages) in all environments

Coverage increased (+0.01%) to 79.584% when pulling 659a7fb1ffc8e66c675839895b2a5743dd2c9eea on huafu:e2e-coverage into bfe9346aadade7c5898fddae3a8b2a9cb60bca33 on kulshekhar:beta.


Preparation for .NET Core

Upgrading RestSharp to latest (106.3.1)
Upgrading Newtonsoft.Json to latest (11.0.2)
Upgrading to .NET Framework 4.6.2 (compatible with .NET Standard 2.0)

Part of #32 (not sure if it's enough to fix it completely?)

Thanks for putting this together! We'll try to get this tested and released in the near future.

Hi,
I'll close this for now. We're not in need of it anymore, so I don't think this PR adds any direct value. Feel free to reopen it if you want to reuse it in the future.
Thanks,
Christian


Issue Title: "Enhance 'What We Do' Section"

i would like to enhance this
Issue Description: I would like to enhance the "What We Do" section of the website. This could involve improving the layout, adding more detailed descriptions, visuals, and highlights of key services or products to provide users with a clearer understanding of what the company offers.
I’d like to work on enhancing this feature. Please assign this issue to me under gssoc-ext, hacktoberfest-accepted, level

Okay @AswaniBolisetti, I'm assigning to you.

hey could you please help me, when i'm running the code it is showing this
only, as ui
On Thu, Oct 10, 2024 at 2:54 PM Anuj Verma @.***> wrote:

Assigned #48 https://github.com/Bitbox-Connect/Bitbox/issues/48 to
@AswaniBolisetti https://github.com/AswaniBolisetti.
—
Reply to this email directly, view it on GitHub
https://github.com/Bitbox-Connect/Bitbox/issues/48#event-14587712707,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4CL2QY4RKS5NHPEH3JSEQTZ2ZBWHAVCNFSM6AAAAABPWFVLCGVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJUGU4DONZRGI3TANY
.
You are receiving this because you were assigned.Message ID:
@.***>

hey could you please help me, when i'm running the code it is showing this only, as ui
…
On Thu, Oct 10, 2024 at 2:54 PM Anuj Verma @.> wrote: Assigned #48 <#48> to @AswaniBolisetti https://github.com/AswaniBolisetti. — Reply to this email directly, view it on GitHub <#48 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/A4CL2QY4RKS5NHPEH3JSEQTZ2ZBWHAVCNFSM6AAAAABPWFVLCGVHI2DSMVQWIX3LMV45UABCJFZXG5LFIV3GK3TUJZXXI2LGNFRWC5DJN5XDWMJUGU4DONZRGI3TANY . You are receiving this because you were assigned.Message ID: @.>

Okk I'll fix this in sometime. Keep Patience. One of the contributor is done this.

Hyy @AswaniBolisetti, Can you give star to this repo.

Sure!
On Thu, Oct 10, 2024, 4:17 PM Anuj Verma @.***> wrote:

Hyy @AswaniBolisetti https://github.com/AswaniBolisetti, Can you give
star to this repo.
—
Reply to this email directly, view it on GitHub
https://github.com/Bitbox-Connect/Bitbox/issues/48#issuecomment-2404748059,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4CL2QY66ANAMXZD7P6RWTLZ2ZLMZAVCNFSM6AAAAABPWFVLCGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDIMBUG42DQMBVHE
.
You are receiving this because you were mentioned.Message ID:
@.***>


Cookbook missing from the supermarket

I followed the instructions in the README and added cookbook 'ops_tcpdump_handler' to my Berksfile but when I ran berks install I got a failure that it was unable to find a solution.  I then looked for the cookbook in the supermarket and realized it wasn't present.  You should either release it to the supermarket or fix the README to reference the git location so the usage steps actually work.

Tagged and uploaded to the public supermarket https://supermarket.chef.io/cookbooks/ops_tcpdump_handler


Rust: says we are missing listing key exercises but that is checked

If you go to the Rust track status it says we still need to list out key concepts:
https://v3.exercism.io/rust/maintaining/launch
I would expect it to say we have finished that since we have itemized the bulk of them and our readme has it checked.
This is looooow priority :smile:

Going to tag onto this rather than open a separate issue ....because there are many many more things that are more important!  😄
The same is true for the Python track.  We've just updated https://github.com/exercism/v3/tree/master/languages/python, but that's not reflected in the info on https://tracks.exercism.io/python.

It's reflected. Click the ❌ . It's very clear on why it's an X.

[Python] Totally get that for our concept exercises  😄   Buuuuut -

"Have a kick off discussion" and
"Add GitHub issues for 20 concept exercises (ok, ok - it is officially 19 atm, but we closed one as completed....)

Are indeed both complete, but not noted.  I'll take care of the TODO in the concept file as well.  😄

Have a kick off discussion could not be automated, so there is no ✔  and not ❌.
🙉 ❤

@ErikSchierboom for the items that don't have a check, perhaps we add a ➖ or ❔ ?

Sounds like a good idea!

I'm wondering if we should keep the "Have a kick-off discussion between track maintainers" item, as we have no way of checking it.

I've created a PR to dynamically check the status of 20 Concept Exercise issues item.

PR was merged and deployed!

I don't mind not being able to verify it, but it is rather variable in terms of if all the maintainers change its a useless tickbox. So maybe remove it now we're further in?

Yep, that would also be my suggestion. Let me do that.


'ar' missing from CommonLanguageCode type

https://github.com/DeepLcom/deepl-node/blob/main/src/types.ts#L168 is missing 'ar' which is supported by DeepL.

This is released in v1.2.0, which is already on npm

Do you mean v1.12.0 (published a day ago)?

Yes, sorry for the typo


MSID: 90959 Version: 2 DOI: 2<IP_ADDRESS>8652

[PLACE MANUSCRIPT AND EDITOR DETAILS HERE WHEN AVAILABLE] See step 3
[PLACE PDF URL HERE WHEN AVAILABLE] See step 7
Step 1. Inform bioRxiv
Who can help: @QueenKraken, @nlisgo, @scottaubrey

[x] Manuscript is in data hub index (https://data-hub-api.elifesciences.org/enhanced-preprints/docmaps/v2/by-publisher/elife/get-by-manuscript-id?manuscript_id=90959)

Step 2. Create preview of manuscript
Who can help: @fred-atherden, @nlisgo, @scottaubrey

[ ] Manuscript is available for preview (https://prod--epp.elifesciences.org/preview/90959/v2)

[ ] Trigger import for staging: https://prod--epp.elifesciences.org/import
[ ] Sync data folder with s3://prod-elife-epp-data/data
[ ] Trigger import for staging: https://staging--epp.elifesciences.org/import
[ ] Sync data folder with s3://staging-elife-epp-data/data
[ ] Pull request created to enhanced-preprint-data
[ ] Post link to pull request below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-manuscript
Step 3: Awaiting public reviews and QC
Who can help: Production team

[ ] QC passed or QC not needed

Who can help: Editorial team

[x] Public reviews available on sciety (https://sciety.org/articles/activity/10.1101/2<IP_ADDRESS>8652)
[ ] Manuscript and editor details at the top of this issue (Supplied by Editorial team)
[ ] Reviews returned by EPP - https://prod--epp.elifesciences.org/api/reviewed-preprints/90959/v2/reviews

Example
"msas": "Genetics and Genomics", "Neuroscience"
"msid": "84628"
"version": "1"
"preprintDoi": "10.1101/2<IP_ADDRESS>4241"
"articleType": "Reviewed Preprint"
"status": "Published from the original preprint after peer review and assessment by eLife."

"Reviewed Preprint posted": "2023-01-02"
"Sent for peer review": "2022-10-28"
"Posted to bioRxiv": "2022-11-21" (link: "Go to bioRxiv": "https://www.biorxiv.org/content/10.1101/2<IP_ADDRESS>4241v1")

Editors:
Reviewing Editor
Michael B Eisen
University of California, Berkeley, United States
Senior Editor
Michael B Eisen
University of California, Berkeley, United States

Step 4: Modify manuscripts.json (no PDF)

[ ] Reviewed preprint is published to EPP (https://elifesciences.org/reviewed-preprints/90959)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[ ] Request that a doi be registered

[ ] Post link to #enhanced-preprint comment below

Pull request: [PLACE LINK TO PULL REQUEST HERE]
#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]

Instructions to modify manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/publish-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/334/files
Once the pull request is merged in it should be available a few minutes later.

Request that a doi
Post the following in #enhanced-preprint:
@Fred can you register a doi for https://elifesciences.org/reviewed-preprints/90959

Step 5: Awaiting search reindex

[ ] Reviewed preprint is avaliable on journal homepage (https://elifesciences.org)

The search reindex is triggered once an hour. We need the reviewed preprint to be indexed as the search application serves the journal homepage.

Additional info
If needed, the jenkins pipeline to reindex search can be triggered sooner.
https://alfred.elifesciences.org/job/process/job/process-reindex-reviewed-preprints/

Step 6: Published! Request PDF generation

[ ] Post the link to the PDF url at the top of the issue

[ ] Post link to #enhanced-preprint comment below

#enhanced-preprint comment thread: [PLACE LINK TO COMMENT HERE]
Post the following to the #enhanced-preprint on slack:
@Ryan Dix-Peek please can you generate a PDF for https://elifesciences.org/reviewed-preprints/90959

Step 7: Introduce PDF to data folder and git repo

[ ] PDF is avaliable at https://github.com/elifesciences/enhanced-preprints-data/raw/master/data/90959/v2/90959-v2.pdf

Detailed instructions: https://github.com/elifesciences/enhanced-preprints-data#add-a-pdf
Step 8: Add PDF url to manuscripts.json

[ ] Reviewed preprint PDF is available for download (https://prod--epp.elifesciences.org/reviewed-preprints/90959)

[ ] Pull request created to enhanced-preprint-client
[ ] Pull request switched to "Ready for review"
[ ] Post link to pull request below

[PLACE LINK TO PULL REQUEST HERE]

Instructions to add PDF url to manuscripts.json

Visit: https://github.com/elifesciences/enhanced-preprints-client/actions/workflows/add-pdf-url-to-manuscript.yaml
Click: Run workflow
Complete the form and click "Run workflow"
A successful run should result in a new pull request at https://github.com/elifesciences/enhanced-preprints-client/pulls
Open the pull request and click the "Ready for review" button to trigger tests
Once the tests pass and you are happy with the changes the PR can be merged

Example pull request: https://github.com/elifesciences/enhanced-preprints-client/pull/397/files
Once the pull request is merged in it should be available a few minutes later.

Step 9: Done!

[ ] Kettle is on!

elocations missing from references


Chrome PWAs have an empty title (and crash list-windows --all --format "%{window-title}")

I was trying to print the window title of some PWAs from chrome (I have the same PWA in two different profiles; while they share the app name, they do have different titles). When I ran the command aerospace list-windows --all --format "%{window-title}", aerospace crashed constantly with the following trace:
Common/commonUtil.swift:44: Fatal error:
Please report to:
    https://github.com/nikitabobko/AeroSpace/issues/new
    Please describe what you did to trigger this error

Message: The data couldn’t be read because it isn’t in the correct format.
Version: 0.14.2-Beta
Git hash: 0cb8dbdfc5ee73b8cbc200f175f467ebead55201
Coordinate: /Users/bobko/a/AeroSpace/Sources/Cli/main.swift:59:91 run(_:stdin:)
recursionDetectorDuringFailure: false
cli: true

Stacktrace:
0   aerospace                           0x00000001029b9560 $s6Common6errorT_4file4line6column8functionxSS_SSS2iSStlFs5NeverO_Tg5 + 740
1   aerospace                           0x00000001029d2324 $ss6ResultO6CommonE10getOrThrow_4file4line6column8functionxSS_SSS2iSStF + 360
2   aerospace                           0x000000010286e58c $s3Cli3run_5stdin6Common12ServerAnswerVSaySSG_SStF + 1252
3   aerospace                           0x000000010286daa4 main + 1556
4   dyld                                0x000000019487b154 start + 2476
[1]    94223 trace trap  aerospace list-windows --all --format "%{window-title}"

This crash didn't happen if I added other options to <output-format>. I then noticed that the PWAs show with an empty title on aerospace (fyi I tried other different PWAs too). Therefore, I would say that the bug consists of two parts:

chrome PWAs showing with an empty title
aerospace crashing when one of the lines for list-windows is empty

Let me know if there's anything else I can help with to debug this issue.
Checklist

[x] I've searched for duplicates. My search queries were (please don't forget to search in closed issues too):

chrome --window-title
--window-title
pwa
empty window title

[x] I've read the documentation https://nikitabobko.github.io/AeroSpace/guide & https://nikitabobko.github.io/AeroSpace/commands
[ ] I've searched in the documentation. My search queries were:

aerospace CLI client version: 0.14.2-Beta 0cb8dbdfc5ee73b8cbc200f175f467ebead55201
AeroSpace.app server version: 0.14.2-Beta 0cb8dbdfc5ee73b8cbc200f175f467ebead55201

Can you please attach /tmp/bobko.aerospace/aerospace-runtime-error.txt? The error you attached is from CLI client. CLI client simply failed because it couldn't receive data from the server (I agree that error reporting can be improved here)

Nevermind, reproduced, it's an "unhandled" crash and /tmp/bobko.aerospace/aerospace-runtime-error.txt doesn't exist. The crash stack trace can be found in the Console.app
-------------------------------------
Translated Report (Full Report Below)
-------------------------------------

Process:               AeroSpace [67761]
Path:                  /Applications/AeroSpace.app/Contents/MacOS/AeroSpace
Identifier:            bobko.aerospace
Version:               0.14.2-Beta (???)
Code Type:             ARM-64 (Native)
Parent Process:        launchd [1]
User ID:               502

Date/Time:             2024-08-21 15:41:35.4744 +0200
OS Version:            macOS 14.5 (23F79)
Report Version:        12
Anonymous UUID:        82D4F35D-AB0F-405F-EBA2-43B399FFBA68

Sleep/Wake UUID:       213F17D7-9CBF-4574-A402-2E62AC4C7296

Time Awake Since Boot: 5200000 seconds
Time Since Wake:       430970 seconds

System Integrity Protection: enabled

Crashed Thread:        0

Exception Type:        EXC_BREAKPOINT (SIGTRAP)
Exception Codes:       0x0000000000000001, 0x00000001a0cc2a40

Termination Reason:    Namespace SIGNAL, Code 5 Trace/BPT trap: 5
Terminating Process:   exc handler [67761]

Thread 0 Crashed:
0   libswiftCore.dylib            	       0x1a0cc2a40 closure #1 in closure #1 in closure #1 in _assertionFailure(_:_:file:line:flags:) + 240
1   libswiftCore.dylib            	       0x1a0cc2908 closure #1 in closure #1 in _assertionFailure(_:_:file:line:flags:) + 344
2   libswiftCore.dylib            	       0x1a0cc2264 _assertionFailure(_:_:file:line:flags:) + 188
3   libswiftCore.dylib            	       0x1a0ca0250 Array._checkSubscript(_:wasNativeTypeChecked:) + 160
4   libswiftCore.dylib            	       0x1a0ca0b08 Array.subscript.getter + 88
5   AeroSpace                     	       0x103177c18 partial apply for closure #1 in Array.transposed<A>() + 32
6   libswiftCore.dylib            	       0x1a0c9f380 Collection.map<A>(_:) + 724
7   AeroSpace                     	       0x10317749c Array.transposed<A>() + 364
8   AeroSpace                     	       0x102fb8fb4 Array<A>.format(_:) + 1160
9   AeroSpace                     	       0x102fcd378 specialized ListWindowsCommand._run(_:stdin:) + 1764
10  AeroSpace                     	       0x102fcbf9c protocol witness for Command._run(_:stdin:) in conformance ListWindowsCommand + 40
11  AeroSpace                     	       0x102fa3030 Array<A>._run(_:stdin:) + 1056
12  AeroSpace                     	       0x102fa2714 Command.run(_:stdin:) + 292
13  AeroSpace                     	       0x103000cb8 closure #1 in closure #3 in newConnection(_:) + 160
14  AeroSpace                     	       0x102f9ca3c specialized refreshSession<A>(startup:forceFocus:body:) + 928
15  AeroSpace                     	       0x103000bd8 closure #3 in newConnection(_:) + 84
16  AeroSpace                     	       0x1030017dd partial apply for closure #3 in newConnection(_:) + 1
17  AeroSpace                     	       0x103000e55 thunk for @escaping @callee_guaranteed @Sendable @async () -> (@owned ServerAnswer) + 1
18  AeroSpace                     	       0x10300164d partial apply for thunk for @escaping @callee_guaranteed @Sendable @async () -> (@owned ServerAnswer) + 1
19  AeroSpace                     	       0x103000f21 thunk for @escaping @callee_guaranteed @Sendable @async () -> (@owned ServerAnswer, @error @owned Error) + 1
20  AeroSpace                     	       0x1030017d5 partial apply for thunk for @escaping @callee_guaranteed @Sendable @async () -> (@owned ServerAnswer, @error @owned Error) + 1
21  libswift_Concurrency.dylib    	       0x2591330f9 completeTaskWithClosure(swift::AsyncContext*, swift::SwiftError*) + 1


Have a max app name length and allowed characters check

as we sanitize resource names for IaC it will be a lot simpler if we have restrictions on the appname since we are going to use it in every resource name

Do we need to push this all the way to the customer, or can we do some sort of early-stage transform on it internally?

Discussed in triage. We're going to do this as written: it's an easy impl, and it's always easier to relax constraints than add new ones (from a backwards compat perspective).