lang: #[interface] does not use set_return_data

This does not allow to return values from inside interfaces.
I am willing to implement this feature.

interface attribute macro was removed in https://github.com/coral-xyz/anchor/pull/2285.


[Don't merge] Publish tooltips

⚠ DO NOT MERGE
This pr is just to publish the alpha build of this pr https://github.com/primer/primer/pull/362
Suspect something to do with the primer-css => primer name changed borked things up.
To do:

[ ] move doc changes into brocs/tooltipped branch

Closing in favor of https://github.com/primer/primer/pull/404


Upgrade go

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 39.91%. Comparing base (924867e) to head (57e8d74).

Additional details and impacted files
@@           Coverage Diff           @@
##           master      #85   +/-   ##
=======================================
  Coverage   39.91%   39.91%
=======================================
  Files          20       20
  Lines        1478     1478
=======================================
  Hits          590      590
  Misses        808      808
  Partials       80       80

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Lambda runner not resolving with default values

I'm just starting to try this out, so I followed the instructions to setup on a clean cdk project and did GitHubRunners() with no params and I got some errors.
    new GitHubRunners(this, 'runners', {})

From the best I can tell, it was complaining that the Lambda imagebuilder couldn't find it's runner files. I see this was recently refactored, and if I changed the contents of the components file I was able to get past this error
It was throwing errors that it couldn't find runner.js, it appears this path perhaps recently change, so I updated the paths in
https://github.com/CloudSnorkel/cdk-github-runners/blob/main/src/image-builders/components.ts#L509
to look like this and it got further:
            getAssets(_os, _architecture) {
                return [
                    {
                        source: path.join(__dirname, '..', '..', 'assets', 'docker-images', 'lambda', 'linux-x64', 'runner.js'),
                        target: '${LAMBDA_TASK_ROOT}/runner.js',
                    },
                    {
                        source: path.join(__dirname, '..', '..', 'assets', 'docker-images', 'lambda', 'linux-x64', 'runner.sh'),
                        target: '${LAMBDA_TASK_ROOT}/runner.sh',
                    },
                ];
            }

Since I don't intend to use the Lambda runners, I just turned them off like this:
    new GitHubRunners(this, 'runners', {
      providers: [
        new CodeBuildRunnerProvider(this, 'CodeBuild', {}),
        new FargateRunnerProvider(this, 'Fargate', {}),
      ]
      }),

Thanks!


Turned featherlight.js into UMD module

Now we can use it in ES6 code like import 'featherlight'; and it will not say there's no jQuery if you use webpack.
No code inside Featherlight itself was changed, just wrapped into UMD loader.

Any status update on this?

Thanks for the ping!
Merged and release. Thanks for the great PR.

Hi all,
Wondering how the gallery works?
import featherlight from 'featherlight'; seems to work for me - but I can't figure out how to import the gallery.

Hi all, Wondering how the gallery works?
import featherlight from 'featherlight'; seems to work for me - but I can't figure out how to import the gallery.

anyone, any idea?


fix: Issues with widget name focus

Description

Removed black border around the organisation name
Fix the widget's name not getting focused on widget addition if we are doing a reflow

Fixes #14392
Fixes #14265
Type of change

Bug fix (non-breaking change which fixes an issue)

How Has This Been Tested?

manual

Checklist:

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

/ok-to-test sha=efb0794


Update cases.md with a new case design

Hi - would like to share a new case design i did recently...
Thank you for your great project!
Cheers,
R.

Great design! Thank you!