[FEATURE] Change the default option of ui-source from Auto to Bundled

The problem
The default option of ui-source is Auto, which equals to External, the problem is:

Require additional external connection
Hard to address UI issues if user didn't change the option to Bundled.

The Solution
Change the default option Auto to point to Bundled, or change the default option from Auto to Bundled.
(Actually I thought we might not need Auto option, bit confusing that it is pointed to which option)
The Alternatives
Let it become configurable when installing.  (both ISO and config file)
Additional Context
Bundled UI should have a regularly build, as PR of dashboard repo would not trigger installer to build new iso, a weekly trigger would be nice for verify UI issues.

The Harvester UI follows the same pattern as the Rancher UI does:

By default the ui-source option is Auto, it will use the embedded UI when the server version is started with v* tag, otherwise it will default to fetch from the remote server.
The master-head harvester image has already packaged the latest Harvester UI as the bunded one. https://github.com/harvester/harvester/blob/master/package/Dockerfile#L18

@guangbochen

By default the ui-source option is Auto, it will use the embedded UI when the server version is started with v* tag, otherwise it will default to fetch from the remote server.

We will need a note for air-gapped environment in case of we release some master-head version for customers to testing in the future.


Can't feed result of get operation into feed delete/update

feed_iterable requires ids to be formatted as just last component without namespace etc, but get operation returns the raw document id from vespa.

Good point. You could of course infer the id from the doc_id for now, but we'll see if we can make this easier in the future.


backup: Use tar --transform to arrange the tarball instead of symlinks

This allows tar to print the real paths in error messages if something goes wrong.
Testing Plan: Ran a dev backup and restore, checking that the tarball had the right contents and restored files went to the right places.

Looks good, thanks @andersk!  (And sorry for the slow review)


Speaker "Not Supported" in iOS Home app

Thank you for fixing #35 !
Now the accessory is created (and no crash) but in Home on iOS, it merely shows "Not Supported" for the Speaker.
There's no related logs in homekit2mqtt output.
I'm running iOS 10.3.3. Is this an iOS 11 feature?
I've just implemented just the minimal configuration:
{
  "Speaker": {
    "service": "Speaker",
    "name": "Speaker",
    "topic": {
      "setMute": "home/speaker/mute"
    },
    "payload": {
      "muteTrue": "mute",
      "muteFalse": "unmute"
    }
  }
}

Is there anything useful I can do to debug this?

Yes, the iOS 10 Home app doesnt support speakers. You can use them with the Elgato Eve app.


logging: OpenTelemetry spans are ignored as parents for LogRecords

Tracking the same issue as 9302 to propagate correct TraceId and SpanId for logging and tracing correlation.
Client
nodejs-logging
Context
In nodejs-logging libraries, the current implementation will always use a remote trace ID and span ID parsed from HTTP headers that originate from outside the application:
https://github.com/googleapis/nodejs-logging/blob/53c5c248b05dd987ee8675d1d250261698ba9ba3/src/utils/context.ts#L95
As a result, logs are associated with the parent span rather than the span of interest.
Expected behavior
If the user is using opentelemetry instrumentation, we want to use the traceID and spanID of the span that OpenTelemetry created. This way, when a user looks for logs associated with that span, the logs produced by this logging library will appear.

To fix this issue in nodejs logging repo, @dashpole suggested importing OpenTelemetry Api and using nodejs spanContext to retrieve current traceId and spanId:https://github.com/googleapis/google-cloud-go/issues/9302#issuecomment-1930391821
@aabmass David mentioned that you may help review the fixes for nodejs and java. I added the following logic to retrieve spanContext locally and it seemed working fine locally:
import { trace, context, isSpanContextValid} from '@opentelemetry/api';
import { isTracingSuppressed } from '@opentelemetry/core';

   const activeContext = context.active();
    const spanContext = trace.getSpanContext(activeContext);

    if (spanContext != undefined && isSpanContextValid(spanContext) && !isTracingSuppressed(activeContext)) {
      const otelSpanContext = {
        trace: spanContext?.traceId,
        spanId: spanContext?.spanId,
        traceSampled: spanContext?.traceFlags === 1,
      };
    }

I am wondering if you can help with a couple of questions:

is context.active() the correct way to get the current active context and then use it to retrieve spanContext? It's mentioned that context.active() will work only with context Manager configured, otherwise it will always return ROOT_CONTEXT: https://opentelemetry.io/docs/languages/js/context/#active-context
Do we need to configure context Manger in that case?

Do you think we need to validate !isTracingSuppressed(activeContext) as well? Looks like this is introduced from opentelemetry-core


Make dev profile faster by compiling deps with opt-level=3

As the code explains it, this is a list of dependencies that we compile with opt-level=3 when doing a plain cargo build.

Oh... well, I'll re-do the PR.

For reference, this seems to cause warnings to be printed when someone runs cargo install --git .. subkey.
I've opened https://github.com/rust-lang/cargo/issues/8328


Allow formatting arbitrary selection on arbitrary webpage

Without needing to copy/paste or open a separate tab.
Usage flow:

Navigate to a webpage containing JSON string (text book, presentation, server log file, etc.)
Use the mouse to select some text.
Right-click to bring up the browser context menu. Similar to AdBlock, there should be a "Format as JSON" item.
Select the "Format as JSON" menu item.
The extension puts up a bubble (looks like a speech bubble or a dictionary look up bubble, or a tooltip, etc.) on top of the selected text, which renders the pretty-formatted JSON string or any validation errors.

This is already an excellent tool, and would be made a lot better with this feature.

Despite being 7 years late, If it can still be of any use I forked this repository and made a browser context menu button to format as json. It's still a bit ugly and broken (didn't figure out how to load icons yet), but it should already get the job done.
https://github.com/fredtrentini/json-formatter


TypeError: 'int' object does not support item assignment

Running on Python 3.5 (Linux)
[...]
  File "/home/andreas/Envs/newsi/lib/python3.5/site-packages/newspaper/article.py", line 219, in parse
    meta_data = self.extractor.get_meta_data(self.clean_doc)
  File "/home/andreas/Envs/newsi/lib/python3.5/site-packages/newspaper/extractors.py", line 514, in get_meta_data
    ref[part] = value
TypeError: 'int' object does not support item assignment

Thanks for finding this!

Will investigate, there seems to be a few errors in the html parse/extract logic

The latest fix by @megatron-me-uk at https://github.com/codelucas/newspaper/pull/426 should fix your issue :) Please pull the latest master version of newspaper and reattempt this.
Otherwise, I plan on bumping the newspaper version and updating sometime this week.


Install fails with conda and python10

Describe the bug
The following fails on a M1 Macbook Pro:
conda create -n runhouse python==3.10
conda activate runhouse
pip install --no-cache "runhouse[aws]"

The error is:
Installing build dependencies ... done
  Getting requirements to build wheel ... error
  error: subprocess-exited-with-error

  × Getting requirements to build wheel did not run successfully.
  │ exit code: 1
  ╰─> [48 lines of output]
      running egg_info
      writing lib3/PyYAML.egg-info/PKG-INFO
      writing dependency_links to lib3/PyYAML.egg-info/dependency_links.txt
      writing top-level names to lib3/PyYAML.egg-info/top_level.txt
      Traceback (most recent call last):
        File "/Users/abeatson/mambaforge/envs/runhouse3/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 353, in <module>
          main()
        File "/Users/abeatson/mambaforge/envs/runhouse3/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 335, in main
          json_out['return_val'] = hook(**hook_input['kwargs'])
        File "/Users/abeatson/mambaforge/envs/runhouse3/lib/python3.10/site-packages/pip/_vendor/pyproject_hooks/_in_process/_in_process.py", line 118, in get_requires_for_build_wheel
          return hook(config_settings)
        File "/private/var/folders/1n/t9p25xtd4sl4zxdt57hjlc7m0000gn/T/pip-build-env-obpqea6w/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 325, in get_requires_for_build_wheel
          return self._get_build_requires(config_settings, requirements=['wheel'])
        File "/private/var/folders/1n/t9p25xtd4sl4zxdt57hjlc7m0000gn/T/pip-build-env-obpqea6w/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 295, in _get_build_requires
          self.run_setup()
        File "/private/var/folders/1n/t9p25xtd4sl4zxdt57hjlc7m0000gn/T/pip-build-env-obpqea6w/overlay/lib/python3.10/site-packages/setuptools/build_meta.py", line 311, in run_setup
          exec(code, locals())
        File "<string>", line 271, in <module>
        File "/private/var/folders/1n/t9p25xtd4sl4zxdt57hjlc7m0000gn/T/pip-build-env-obpqea6w/overlay/lib/python3.10/site-packages/setuptools/__init__.py", line 103, in setup
          return distutils.core.setup(**attrs)
        File "/private/var/folders/1n/t9p25xtd4sl4zxdt57hjlc7m0000gn/T/pip-build-env-obpqea6w/overlay/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 185, in setup
          return run_commands(dist)
        File "/private/var/folders/1n/t9p25xtd4sl4zxdt57hjlc7m0000gn/T/pip-build-env-obpqea6w/overlay/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 201, in run_commands
          dist.run_commands()
        File "/private/var/folders/1n/t9p25xtd4sl4zxdt57hjlc7m0000gn/T/pip-build-env-obpqea6w/overlay/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 969, in run_commands
          self.run_command(cmd)
        File "/private/var/folders/1n/t9p25xtd4sl4zxdt57hjlc7m0000gn/T/pip-build-env-obpqea6w/overlay/lib/python3.10/site-packages/setuptools/dist.py", line 963, in run_command
          super().run_command(command)
        File "/private/var/folders/1n/t9p25xtd4sl4zxdt57hjlc7m0000gn/T/pip-build-env-obpqea6w/overlay/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
          cmd_obj.run()
        File "/private/var/folders/1n/t9p25xtd4sl4zxdt57hjlc7m0000gn/T/pip-build-env-obpqea6w/overlay/lib/python3.10/site-packages/setuptools/command/egg_info.py", line 321, in run
          self.find_sources()
        File "/private/var/folders/1n/t9p25xtd4sl4zxdt57hjlc7m0000gn/T/pip-build-env-obpqea6w/overlay/lib/python3.10/site-packages/setuptools/command/egg_info.py", line 329, in find_sources
          mm.run()
        File "/private/var/folders/1n/t9p25xtd4sl4zxdt57hjlc7m0000gn/T/pip-build-env-obpqea6w/overlay/lib/python3.10/site-packages/setuptools/command/egg_info.py", line 551, in run
          self.add_defaults()
        File "/private/var/folders/1n/t9p25xtd4sl4zxdt57hjlc7m0000gn/T/pip-build-env-obpqea6w/overlay/lib/python3.10/site-packages/setuptools/command/egg_info.py", line 589, in add_defaults
          sdist.add_defaults(self)
        File "/private/var/folders/1n/t9p25xtd4sl4zxdt57hjlc7m0000gn/T/pip-build-env-obpqea6w/overlay/lib/python3.10/site-packages/setuptools/command/sdist.py", line 112, in add_defaults
          super().add_defaults()
        File "/private/var/folders/1n/t9p25xtd4sl4zxdt57hjlc7m0000gn/T/pip-build-env-obpqea6w/overlay/lib/python3.10/site-packages/setuptools/_distutils/command/sdist.py", line 251, in add_defaults
          self._add_defaults_ext()
        File "/private/var/folders/1n/t9p25xtd4sl4zxdt57hjlc7m0000gn/T/pip-build-env-obpqea6w/overlay/lib/python3.10/site-packages/setuptools/_distutils/command/sdist.py", line 336, in _add_defaults_ext
          self.filelist.extend(build_ext.get_source_files())
        File "<string>", line 201, in get_source_files
        File "/private/var/folders/1n/t9p25xtd4sl4zxdt57hjlc7m0000gn/T/pip-build-env-obpqea6w/overlay/lib/python3.10/site-packages/setuptools/_distutils/cmd.py", line 107, in __getattr__
          raise AttributeError(attr)
      AttributeError: cython_sources
      [end of output]

Versions
Please run the following and paste the output below.
wget https://raw.githubusercontent.com/run-house/runhouse/main/collect_env.py
# For security purposes, please check the contents of collect_env.py before running it.
python collect_env.py

Output:
python collect_env.py
Python Platform: macOS-13.4-arm64-arm-64bit
Python Version: 3.10.0 | packaged by conda-forge | (default, Nov 20 2021, 02:27:15) [Clang 11.1.0 ]

Relevant packages:
wheel==0.42.0

sh: sky: command not found
sh: sky: command not found

Hi @alexub, thanks for flagging this! Looks like an issue while installing pyyaml during the awscli installation for the specific version pinned in stable right now. This should be resolved in our next release, but a couple of options to get around this for now:

Run pip install from the Runhouse main dev branch, which has relaxed the awscli version.
pip install "git+https://github.com/run-house/runhouse.git#egg=runhouse[aws]"

Run pip install runhouse (no aws extension), and then manually install the specific versions of awscli/boto you need.

First install pyyaml (5.4.1 works for me), then run pip install "runhouse[aws]"

Let me know if you're still running into anything!

I just reran your commands with the new runhouse version (v0.0.15) released a few days ago and the installation should be fixed now! Closing this issue but feel free to reopen or create a new one if you're still encountering this or running into a new error 🙂


string property after decompress became array

Tried to use this package for app I working on, have big complex nested structures json, one important property was string, but after decompress became array. Will try a bit later to make reproducable example as can't really share original json.

Look forward to an example reproducing this bug

Look forward to an example reproducing this bug

@Cherviakov wish you could give an example reproducing the bug, then we can fix it

@Cherviakov wish you could give an example reproducing the bug, then we can fix it

Here it is, though now error is different
{
        "json": {
                "versions": [
                        {
                                "things": [
                                        {
                                                "ID": 1,
                                                "GUID": "e96bd89e-86eb-42da-99c9-345adb3a89d6",
                                                "Name": "Test",
                                                "Description": "",
                                                "Subthings": [
                                                        {
                                                                "ID": 7,
                                                                "GUID": "10666c0a-12a5-44e9-860c-684b7f1de6ab",
                                                                "Name": "Start",
                                                                "Triangles": {
                                                                        "Triangles": [
                                                                                {
                                                                                "Name": "Triangle-01"
                                                                                }
                                                                        ]
                                                                }
                                                        }
                                                ]
                                        }
                                ]
                        }
                ]
        }
}

Here is also code snippet I used to check what is wrong:
const { compress, decompress } = require('compress-json');
const test = require('./Test.json');

const isEqual = (json1, json2) => {
  return JSON.stringify(json1) === JSON.stringify(json2);
};

const com = compress(test);
const decom = decompress(com);
console.log(isEqual(test, decom));
console.log(isEqual(test.json.versions[0].things[0].Subthings[0].Triangles.Triangles, decom.json.versions[0].things[0].Subthings[0].Triangles.Triangles));
console.log(test.json.versions[0].things[0].Subthings[0].Triangles);
console.log(decom.json.versions[0].things[0].Subthings[0].Triangles);

Output I got
false
false
{ Triangles: [ { Name: 'Triangle-01' } ] }
{ T: [ { N: 'Triangle-01' } ] }

Additional info:
os: Linux-Mint-18 4.15.0-129-generic #132~16.04.1-Ubuntu SMP Wed Dec 16 06:46:04 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
node: v15.0.1
npm: 7.0.3

Here it is, though now error is different
{
        "json": {
                "versions": [
                        {
                                "things": [
                                        {
                                                "ID": 1,
                                                "GUID": "e96bd89e-86eb-42da-99c9-345adb3a89d6",
                                                "Name": "Test",
                                                "Description": "",
                                                "Subthings": [
                                                        {
                                                                "ID": 7,
                                                                "GUID": "10666c0a-12a5-44e9-860c-684b7f1de6ab",
                                                                "Name": "Start",
                                                                "Triangles": {
                                                                        "Triangles": [
                                                                                {
                                                                                "Name": "Triangle-01"
                                                                                }
                                                                        ]
                                                                }
                                                        }
                                                ]
                                        }
                                ]
                        }
                ]
        }
}

Here is also code snippet I used to check what is wrong:
const { compress, decompress } = require('compress-json');
const test = require('./Test.json');

const isEqual = (json1, json2) => {
  return JSON.stringify(json1) === JSON.stringify(json2);
};

const com = compress(test);
const decom = decompress(com);
console.log(isEqual(test, decom));
console.log(isEqual(test.json.versions[0].things[0].Subthings[0].Triangles.Triangles, decom.json.versions[0].things[0].Subthings[0].Triangles.Triangles));
console.log(test.json.versions[0].things[0].Subthings[0].Triangles);
console.log(decom.json.versions[0].things[0].Subthings[0].Triangles);

Output I got
false
false
{ Triangles: [ { Name: 'Triangle-01' } ] }
{ T: [ { N: 'Triangle-01' } ] }

Additional info:
os: Linux-Mint-18 4.15.0-129-generic #132~16.04.1-Ubuntu SMP Wed Dec 16 06:46:04 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux
node: v15.0.1
npm: 7.0.3

Thanks for the sample data. I can reproduce the problem, hopefully will resolve it over this weekend.

Thanks for the sample data. I can reproduce the problem, hopefully will resolve it over this weekend.

The bug when running above sample data is fixed and the new version is published as v1.0.2 on npm.
However, the original reported bug 'string property after decompress became array' is not reproduced yet.

The bug when running above sample data is fixed and the new version is published as v1.0.2 on npm.
However, the original reported bug 'string property after decompress became array' is not reproduced yet.

The reported bug(s) should have been fixed in<EMAIL_ADDRESS>@Cherviakov, might you confirm that with your data set? Thanks.

The reported bug(s) should have been fixed in<EMAIL_ADDRESS>@Cherviakov, might you confirm that with your data set? Thanks.

Tested, can't reproduce nor last problem neither original one. Thanks.

Tested, can't reproduce nor last problem neither original one. Thanks.


Store Id Token in session cookie

Core Library
MSAL.js v2 (@azure/msal-browser)
Core Library Version
2.22.0
Wrapper Library
MSAL React (@azure/msal-react)
Wrapper Library Version
1.3.0
Description
I have an SPA that has links to multiple portals hosted in different domains. Each of these portals in turn have integrated SSO using flask-appbuilder. When logged-in to my SPA, I want the links of other portals to open without asking for login again.
I checked Flask code and it checks if JWT token is present in session cookie.
In my SPA, I have integrated msal, but it does not allow me to store idToken in session cookie.
Can this be achieved with msal library or whats the best way to store idToken in session cookie ?
MSAL Configuration
import { Configuration } from "@azure/msal-browser";

export const MSAL_CONFIG: Configuration = {
  auth: {
    clientId: '<CLIENT_ID>',
    authority: 'https://login.microsoftonline.com/<TENANT_ID>',
    redirectUri: 'http://localhost:9000/',
    postLogoutRedirectUri: 'http://localhost:9000/'
  },
  cache: {
    cacheLocation: "localStorage",
    storeAuthStateInCookie: true,
    secureCookies: false,
  },
};

/**
 * Scopes you add here will be prompted for user consent during sign-in.
 * By default, MSAL.js will add OIDC scopes (openid, profile, email) to any login request.
 * For more information about OIDC scopes, visit:
 * https://docs.microsoft.com/en-us/azure/active-directory/develop/v2-permissions-and-consent#openid-connect-scopes
 */
 export const loginRequest = {
  scopes: ["User.Read"]
};

/**
* Add here the scopes to request when obtaining an access token for MS Graph API. For more information, see:
* https://github.com/AzureAD/microsoft-authentication-library-for-js/blob/dev/lib/msal-browser/docs/resources-and-scopes.md
*/
export const graphConfig = {
  graphMeEndpoint: "https://graph.microsoft.com/v1.0/me"
};

export default MSAL_CONFIG;

Relevant Code Snippets
No response
Identity Provider
Azure AD / MSA
Source
Internal (Microsoft)

Hi @tejaswibm , thanks for raising the issue!
Setting the ID Token in the session cookie is only useful for the app on a specific domain maintaining its own access while the session is active, since cookies are partitioned by domain. This means even if you did set it, it would not be accessible from the other portals/apps on different domains.
As far as how to achieve SSO across domains, each app still has to make a token request through MSAL by either using our interactive APIs (loginRedirect/loginPopup) or by leveraging ssoSilent. I hope this helps.

@hectormmg - Thanks for providing your insights.

All portals in our eco-system are hosted on the same domain (only sub-domains are different).
Flask-AppBuilder lib uses session cookie to check if JWT is already present; if not then makes token request call.

Given above 2 points, do you still suggest not to set session cookie with JWT manually ? Is there any security risks in doing so manually ?

@tejaswibm Since the cache is not shared between sub-domains, each app would have to go to the network to request tokens. Our recommendation would still be to leverage ssoSilent instead of setting the cookies manually.


Adds crawl-delay to robots.txt

Sets delay to 1s

No use for this rule since Sep 2019 https://developers.google.com/search/blog/2019/07/a-note-on-unsupported-rules-in-robotstxt


add more actions

Add more actions:

Set input
Send key
Set volume
Mute volume
Set energy saving level (blank screen)

I'm not sure if disconnect() actually does anything, but I can see destroy() is not a valid function.
I also added an option to configure custom WOL IP address because my TV is on a different subnet.  I designated one unused IP for this and created a static ARP entry in my router: set protocols static arp <IP_ADDRESS> hwaddr ff:ff:ff:ff:ff:ff.  I also removed this IP from the DHCP range to avoid conflicts.

@JeffreyDavidsz

This looks good to me

Looks good to me


Add option to choose Jira API version

Would be interesting to have a key in plugin configuration object to choose the jira api version?
something like
plugin: {
  jiraApiVersion: 2,
  debug: true
}

For some reason the plugin is working locally, but isn't in CI, only the 3.3.3 plugin version, that apparently uses the version 2 JIRA API.
I have set up all credentials needed.

But even so I got the summary error:

Hey, thanks for the suggestion.
I'm not entirely opposed to it, but I'd like to investigate your problem a little more (Jira explicitly states that the APIs offer the same functionalities).

Do you have any additional plugins/cypress modifications going on?
Are the credentials you're using in CI different from your local ones?

What would help me most is if you shared the data as described here (only the data, not the headers containing your credentials). You can obviously replace the summaries and domain with garbage text, if you don't want to share them.

It's probably a difference in CI environment and my machine that I can't identify

We have 2 plugins being used. 1 for coverage and other is the dotenv, which I had checked and was working fine locally.
The credentials are the same. I ran and checked several times.

I will try to get the data that you needs and put it here when possible

@csvtuda only updating, I got vacations a while ago and when I go back to work, I will try to get the logs on CI enviroment as you suggested

@csvtuda I just ran some tests with the version 4.0.4 and it mysteriously worked. Before, the problem happens in 4.0.2. (I cannot use versions 5> because the node version cap)
Thanks!

@RenanPaixao thanks for the feedback. Glad to hear it's "just working" now.
Should the issue reappear in the future feel free to reopen this issue or just create a new one. And don't forget to update Node sooner or later 😃


Support reverse proxy and writeup some documentation

Support a reverse proxy by not overriding the BASE_URL appending the (internal) port to the request if it's behind a proxy.  This will allow the reverse proxy to work properly and not cause Tau to try to include the internal port for requests to twitch for the callback.
Also wrote up some documentation on various environment variables that are available to the administrator (including the new one)

This would be useful to me for sure, so please let me know when this is merged.

Merged in now @j-dogcoder

Yay! Thanks @FiniteSingularity!


Update README to include steps for running the NextJS example

@zacherygentry fixed this with the pr #20


CGShading stubs

Dear WinObjC Engineers,
It would be nice to implement these stubs:
CGShadingCreateAxial()
CGShadingCreateRadial()
CGFunctionCreate()
and associated functions while considering: https://github.com/Microsoft/WinObjC/issues/1541
Sincerely,
Ed

@edvv we will evaluate this independent of #1541, which appears to be code refactor/cleanup work.

@edvv, there is very little documentation available on shading and its usage.  Apple's own docs on CGContextDrawShading recommends CGGradient instead.  Given this, we are not planning on doing it at this point.  If usage of CGGradient doesn't work for you, let us know what your scenario is.

They "prefer" (not recommend) CGGradient because it is easier. This:
https://developer.apple.com/reference/coregraphics/cgshading?language=objc
says "CGGradient objects are much simpler to use."
which is true. From my memory, about a decade ago Apple depreciated CGShading but then changed their minds and re-appreciated the feature. The function callbacks for CGShading is spread out, but it is all available on Apple's site. CGGradient is not a replacement for CGShading because it is not general enough. CGGradient can only approximate smoothly varying shading functions (sine, etc.).

@edvv, thanks!  Yes, the documentation indeed says this is not "prefered".
From a feature standpoint, shading and function support are not easy to support (if at all).


Decoding error on response of ECS.describeServices

While requesting API for ECS.describeServices, I have got an error:
dataCorrupted(Swift.DecodingError.Context(codingPath: [CodingKeys(stringValue: "services", intValue: nil), _DictionaryKey(stringValue: "Index 0", intValue: 0), CodingKeys(stringValue: "propagateTags", intValue: nil)], debugDescription: "Cannot initialize PropagateTags from invalid String value NONE", underlyingError: nil))

My actual raw json response is:
...\"propagateTags\":\"NONE\",...

Here is definition of PropagateTags in Swift.
public enum PropagateTags: String, CustomStringConvertible, Codable {
    case taskDefinition = "TASK_DEFINITION"
    case service = "SERVICE"
}

NONE is missing or models is outdated?

Hi @novi
We pull definitions from the go sdk json, which is also missing the NONE case for this enum.
If you want to submit a PR that adds this?

This is now fixed by https://github.com/swift-aws/aws-sdk-swift/pull/123


Renamed a few functions and modified some docstrings

Let me know if you're ok with the new names and formulations...

Looks all good to me. Thanks for even clarifying the docstrings.


Move linalg.pad_tensor conversion to subtensor_insert into a separate pass

This is currently done on the HLO to Linalg conversion, which meant
the TOSA path didnt get this conversion. This is needed for the vulkan
codegen to handle pad operation.
Fixes #6077

I don't see pad_tensor_to_tensor.mlir deletion in the files changed. I'm not sure if this is an UI bug, but please make sure the file is deleted in the PR.

It is moved. I dont know the UI, but I see it listed as moved


Facilitate 'post mortem' retrospective around Acquia BLT

Description
Hoping to gain a shared understanding among the tech team and technical stakeholders around our experience (ups/downs) using Acquia BLT
Definition of done

[x] schedule meeting w/ core tech team during core pairing time
[x] Draft PM of BLT experience
[x] Share w/ Ben Schwarten, Jake BG, Suey, Gary

Attachments
title

Will do this as part of our standing engineering time next week

Meeting held Aug 14,
Postmortem writeup
https://docs.google.com/document/d/15w2h1R6lm_FbgMdT-f4S4Utir3ev0Ug8QZPXwiMQW4U/edit
One pager on Acquia BLT and Acquia Cloud experlence
https://docs.google.com/document/d/1DxPeIJQzAI0x4B0IWwJGQTOvwiQ4NG5KLDt4DpKhLdI/edit#heading=h.jmjn81mtfaop
Both documents and the earlier Django/Drupal evaluation were emailed out as well.

moving to done opened the issue?


Support the multiViewport feature.

Clients can now set multiple viewports and scissor rects, but without a
geometry shader, it won't be much use. For now, however, we can support
VK_EXT_shader_viewport_index_layer, which will make this feature more
useful despite us not having geometry shaders.

@cdavis5e
Thanks. Just a couple of code convention adjustments needed.
Do you want to include VK_EXT_shader_viewport_index_layer in the list of supported extensions?
Do you need to pull in your latest SPIRV-Cross (viewport index) commit?
Also...while you are tweaking this...can you bump the value of MVK_VERSION_PATCH, please?
Every time the SPIRV-Cross pull commit in SPIRV-Cross_repo_revision changes...we should bump the the value of MVK_VERSION_PATCH. The reason is that the MoltenVK version number is a component of the pipelineCacheUUID...which is used to determine whether an external pipeline cache is still valid. In MoltenVK, the pipeline cache holds MSL, and any update to SPIRV-Cross might modify how the MSL is converted...and so it is safest to convert again and not to reload the MSL from cache.
Sorry...I should have caught that on your previous PR which did update SPIRV-Cross_repo_revision.

I intended to add VK_EXT_shader_viewport_index_layer in a later commit. I have another change that cleans up the extension list first. Do you want me to add that now?
(I also fixed the one you missed in GPUObjects/MVKDevice.mm. :)


ceph-mon: Generate initial keyring

Minor fix so that initial keyring can be generated using python3.
Signed-off-by: Ha Phan<EMAIL_ADDRESS>

@haphan could you please rebase on master?

jenkins test pipeline


browser.clickLink doesn't like link

When attempting to click a link to "javascript:" I get the exception
Error: Cannot load resource: javascript:

The HTML I'm trying to click is
link

Thanks in advance!
Greg

To support "javascript://" links I added this lines to history.coffee:
(at line 67)
    # FIX: adding javascript resource loading
    if url.protocol == "javascript:"
      @_browser.evaluate(url.href.substr("javascript:".length))
      return

so is there a fix for this problem or do we need to modify the code as benjamine has suggested?


Test sending SQL queries with a variable pre-set

Make research on setting SQL variable prior to making SQL query

http://stackoverflow.com/questions/28221356/in-django-can-i-set-a-variable-in-a-preamble-before-retrieving-a-queryset


[Snyk] Security upgrade @angular-devkit/build-angular from 0.1100.7 to 15.0.0

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to fix one or more vulnerable packages in the `yarn` dependencies of this project.
Changes included in this PR

Changes to the following files to upgrade the vulnerable dependencies to a fixed version:

package.json
yarn.lock

Vulnerabilities that will be fixed
With an upgrade:

Severity
Priority Score (*)
Issue
Breaking Change
Exploit Maturity

551/1000  Why? Recently disclosed, Has a fix available, CVSS 5.3
Regular Expression Denial of Service (ReDoS) SNYK-JS-LOADERUTILS-3105943
Yes
No Known Exploit

(*) Note that the real score may have changed since the PR was raised.
Check the changes in this PR to ensure they won't cause issues with your project.

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open fix PRs.
For more information:
🧐 View latest project report
🛠 Adjust project settings
📚 Read more about Snyk's upgrade and patch logic

Learn how to fix vulnerabilities with free interactive lessons:
🦉 Regular Expression Denial of Service (ReDoS)

there is a more up to date one


Integrated TinyMCE to notes app

TinyMCE is a rich-text editor that allows users to create formatted content within a user-friendly interface. I have integrated it in notes app.
Solves issue #176
@theashikagupta @yashmandi
kindly review my PR and provide the labels of gssoc extended,hactoberfest accepted and level 2.
Also let me know if there are any changes to be made.

@yashmandi @theashikagupta
kindly review my PR and provide the labels of gssoc extended,hactoberfest accepted and level 2.
Also let me know if there are any changes to be made.

Add screen recording

Add screen recording

The pull request was closed due to the synchronization of fork I had to discard the changes I did
So I am reopening it again .

@KGupta2601 Attach screen recording of the implementation.

@theashikagupta yes I am working on it
Actually I am encountering some issues in setting up the backend in my laptop so I am trying to resolve them

No issues Take your time @KGupta2601

@theashikagupta I am unable to sign in

TinyMCE.webm
This is the screen recording
@theashikagupta kindly check the attached screen recording of my implementation

@yashmandi Kindly check the recording I have attached
If there are any further changes to be done, please let me know.


Support AssemblyScript imports

I'm proposing adding two function imports for AssemblyScript that work sort-of like wasi does. The Javascript implementations of these functions exist in the assemblyscript loader located here:
https://github.com/AssemblyScript/assemblyscript/blob/master/lib/loader/index.js#L70
The functions are very straight forward and simply write to stdout.
In order to get a string out of an AssemblyScript module, assemblyscript passes up a pointer that points directly at the start of a utf16le string.
The only way to figure out how to determine the size of the string is to inspect the rtSize property of the header block that exists directly before the pointer. The formula is rtSize >>> 1 because rtSize is a byte length not a string length. The header block definition is shaped like the following struct/class:
https://github.com/AssemblyScript/assemblyscript/blob/master/std/assembly/rt/common.ts#L36
This file explains the header of each AssemblyScript block which is 16 bytes (32 bit wasm) or (20 bytes in 64 bit wasm) in offset directly before the pointer.
Please ask any questions, because I'm sure I forgot lots of details and this would help assemblyscript devs get started a lot easier.

This would have to be added when WASI is added as an environment embedding that follows the interface proposal.

I started peeking at the interface proposal, and I'm wondering if this would be better to implement as an interface, or if they are simplistic enough that a minimal C implementation (like innative-env) would be more useful?

They are very simple. Yes. I'll message you on discord later about it.

I will have to try this out!


Map Camunda 7 businessKey to a Zeebe proces variable named "businessKey"

To make extensive usage of the businessKey in Camunda 7 easier for migration, map the content into a variable called businessKey.
Technically it should be an easy fix in these lines: https://github.com/camunda-community-hub/camunda-7-to-8-migration/blob/main/camunda-7-adapter/src/main/java/org/camunda/community/migration/execution/AbstractDelegateExecution.java#L138-L149
Potentially it could conflict to a BusinessKey that could be implemented in Zeebe itself in the future.
But after a long time, it is not build there. And the main purpose, to identify a process instance easily in the relation database, it not required in the Zeebe distributed architecture.

I think it is only a leftover for migration. Zeebe runs forever without a business key and technically there is no need for an extra identifier (as it was in the relation database). No best practices required here.


use xesam:artist instead of xesam:albumArtist

As noted in https://github.com/Sinono3/souvlaki/issues/21#issuecomment-1015691265, the GNOME mpris indicator displays "Unknown artist" instead of the artist's name, even though the xesam:albumArtist is provided.
This is due to the fact that most MPRIS indicators out there use xesam:artist (GNOME, KDE). With this patch applied, the track is showing correctly for me:

PS: If you'd like to, you can either use this screenshot for the demonstration in the README (#17) or I can take another screenshot, if you rather like to have a different area displayed.

Thanks! I'll use the pic for the example. I'll release a patch to apply these fixes.


packages/mjml-head-attributes/README.md

changes only one file: packages/mjml-head-attributes/README.md

#2276 completes #2266


RFC: allow ⱼ in identifiers

Proposal

User Experience: I believe this feature will slightly improve the aesthetics of some code written in Lean. It is unfortunate that Unicode doesn't have subscript characters for all letter from the Latin alphabet. Nevertheless, it would be good to have as many subscript characters as possible. Currently ⱼ is supported by both Unicode and the VS Code extension but not by Lean.

Beneficiaries: Mathematicians who are used to naming variables xⱼ will like that they don't have to change their notation in this case. On the other hand, I am bit worried it might slightly slow down the lexing of all Lean code (even when ⱼ is not present in it).

Maintainability: This will probably worsen code maintenance, as ⱼ is not in the same interval as other subscript characters in Unicode.

Community Feedback
https://leanprover.zulipchat.com/#narrow/stream/270676-lean4/topic/.E2.9C.94.20.E2.B1.BC.20.28U.2B2C7C.29.20in.20identifiers
Impact
Add :+1: to issues you consider important. If others benefit from the changes in this proposal being added, please ask them to add :+1: to it.

Here is some previous Zulip discussion where @digama0 investigated what's allowed in identifiers. I think there was another thread too, but I couldn't quickly locate it.


Implement NumPy's __array_function__ protocol for array methods that are not in the Array API Standard

This is to support nanmean, nansum (see #153), and pad (#461).
The previous attempt at this in #468 was reverted in #469, since it was causing problems when used with Xarray (https://github.com/pydata/xarray/issues/8834#issuecomment-2124914727).
When Xarray is working we can re-introduce the changes here.

The Xarray change that enables this has been merged (https://github.com/pydata/xarray/pull/9530).
I've re-created the branch from #468 here: https://github.com/cubed-dev/cubed/tree/np-array-function. However, when I run the cubed-xarray tests I get some failures:
FAILED cubed_xarray/tests/test_wrapping.py::test_to_zarr[single-threaded] - TypeError: no implementation found for 'numpy.isclose' on types that implement __array_function__: [<class 'cubed.array_api.a...
FAILED cubed_xarray/tests/test_wrapping.py::test_to_zarr[processes] - TypeError: no implementation found for 'numpy.isclose' on types that implement __array_function__: [<class 'cubed.array_api.a...
FAILED cubed_xarray/tests/test_xarray.py::TestVariable::test_binary_op_bitshift - TypeError: no implementation found for 'numpy.full_like' on types that implement __array_function__: [<class 'cubed.array_api...
FAILED cubed_xarray/tests/test_xarray.py::TestVariable::test_reduce - TypeError: no implementation found for 'numpy.isclose' on types that implement __array_function__: [<class 'cubed.array_api.a...
FAILED cubed_xarray/tests/test_xarray.py::TestDataArrayAndDataset::test_lazy_array - TypeError: no implementation found for 'numpy.isclose' on types that implement __array_function__: [<class 'cubed.array_api.a...
FAILED cubed_xarray/tests/test_xarray.py::TestDataArrayAndDataset::test_dataarray_pickle - TypeError: no implementation found for 'numpy.full_like' on types that implement __array_function__: [<class 'cubed.array_api...
FAILED cubed_xarray/tests/test_xarray.py::TestDataArrayAndDataset::test_dataset_pickle - AssertionError: Left and right Dataset objects are not identical
FAILED cubed_xarray/tests/test_xarray.py::test_unify_chunks - AssertionError: Left and right Dataset objects are not identical
================================ 8 failed, 41 passed, 2 skipped, 15 xfailed, 3 warnings in 3.47s =================================

There is no isclose function in the Array API (https://github.com/data-apis/array-api/issues/170), so we may need to build one (in Xarray?).
cc @keewis @TomNicholas


Add README

We need to add a README, which would include:

The rationale behind the Widget
Some examples of how it should look
Usage instructions

Basic usage
Customization (UI layout, theming)
Localization (depends on #7)

References:

https://pub.dev/packages/badges
https://pub.dev/packages/home_widget
https://pub.dev/packages/scratcher


Channel 4: Time Team - Unable to download Season 01, Episode 4

Describe the bug
I get an error when I try to download Time Team Season 1 Episode 04 (https://www.channel4.com/programmes/time-team/on-demand/16521-004)
To Reproduce
To invoke:
python freevine.py get --episode https://www.channel4.com/programmes/time-team/on-demand/16521-00

Result:
❯_freevine v1.1.1

19:40:13.851 INFO : ALL4
19:40:13.851 INFO : + Loading user profile
19:40:13.853 INFO : Using cached tokens
Traceback (most recent call last):
  File "/home/evan.brown/Desktop/freevine/freevine.py", line 15, in <module>
    cli()
  File "/home/evan.brown/.local/lib/python3.10/site-packages/click/core.py", line 1157, in __call__
    return self.main(*args, **kwargs)
  File "/home/evan.brown/.local/lib/python3.10/site-packages/click/core.py", line 1078, in main
    rv = self.invoke(ctx)
  File "/home/evan.brown/.local/lib/python3.10/site-packages/click/core.py", line 1688, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/home/evan.brown/.local/lib/python3.10/site-packages/click/core.py", line 1434, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/home/evan.brown/.local/lib/python3.10/site-packages/click/core.py", line 783, in invoke
    return __callback(*args, **kwargs)
  File "/home/evan.brown/Desktop/freevine/utils/commands.py", line 81, in get
    Service(config, **kwargs)
  File "/home/evan.brown/Desktop/freevine/services/channel4/channel4.py", line 63, in __init__
    self.get_options()
  File "/home/evan.brown/Desktop/freevine/services/channel4/channel4.py", line 378, in get_options
    self.download(download, title, bearer)
  File "/home/evan.brown/Desktop/freevine/services/channel4/channel4.py", line 381, in download
    self.res, manifest, token = self.get_mediainfo(stream.id, self.quality, bearer)
  File "/home/evan.brown/Desktop/freevine/services/channel4/channel4.py", line 306, in get_mediainfo
    heights, self.soup = get_heights(self.client, manifest)
  File "/home/evan.brown/Desktop/freevine/utils/utilities.py", line 125, in get_heights
    r.raise_for_status()
  File "/home/evan.brown/.local/lib/python3.10/site-packages/requests/models.py", line 1021, in raise_for_status
    raise HTTPError(http_error_msg, response=self)
requests.exceptions.HTTPError: 400 Client Error: Bad Request for url: http://ak.dash01.stream.c4assets.com/wvmod-stream/CH4_33_05_42_16521004001002_002.mpd?c3.ri=13494009089843244131

Expected behavior
The episode should download without error.

Ah, it just worked.  I think Channel 4 uses rate limiting...
Is it possible to add a delay in the script to prevent this?  Tidal-DL does this for downloading songs from Tidal without a too many requests error.

can confirm channel 4 does have a rate limit... specifically user request limit, if you request too many pages and files too quickly from the same ip you get temp banned and that error is thrown.
my logical way to combat this was a longwinded one
create a bash script (im running ubuntu so not sure about windows)
sudo python3 freevine.py get --threads 1 -e S01E01 urlhere
sleep 240
sudo python3 freevine.py get --threads 1 -e S01E02 urlhere
sleep 240
sudo python3 freevine.py get --threads 1 -e S01E03 urlhere
sleep 240
sudo python3 freevine.py get --threads 1 -e S01E04 urlhere
sleep 240
sudo python3 freevine.py get --threads 1 -e S01E05 urlhere
sleep 240
sudo python3 freevine.py get --threads 1 -e S01E06 urlhere
sleep 240
this does three things, limit the download requests to one thread and it forces it to get a specific episode instead of going via complete, which can error with the 400 rate limit, it then gets the episode and when done sleeps for 240 seconds before attempting the next episode

Reducing the threads does help but the process still crashes with a 400 on a long complete series download.  Maybe we could have a retry mechanism on bad request which incorporates a sleep?
Also I have noticed that if you do a complete download invocation and it crashes, repeating the same command skips downloading existing episodes but the process generates a 400 from Channel 4 sooner than the last existing file.  I think this means that a request is being made to the C4 server even where the episode already exists in the download folder.  An improvement would be to check for an existing file first before a server call is made.  get-iplayer uses a cache system to achieve the same effect.

Thanks very much!


RD2 : Fixed Length RD Visualization

As a user I want to see the future installments for my fixed length donations so that I can understand expected installments.
Critical Changes
Changes
Issues Closed
Community Ideas Delivered
New Metadata
Deleted Metadata

**lurch: attach W-039803

Tracking W-039803

**lurch: detach W-039803

Detached W-039803


Event Bus PutEventsAsync is slow on first execution

Describe the bug
On the first execution, the PutEventsAsync is running slow.
My lambda with a Dotnet api project was running slow, so I created a single function to send an event and it also runs slow and I tracked the slowest part to the AWS Command  PutEventsAsync.
Here is my code:
Expected Behavior
I expected this command to run in less than 50ms.
Current Behavior
It takes over 5 seconds to issue the command the first time.
Reproduction Steps
Execute the lambda function
using Amazon.CloudWatchEvents;
using Amazon.CloudWatchEvents.Model;
using Amazon.Lambda.Core;
using Microsoft.Extensions.DependencyInjection;
using System.Text.Json.Serialization;
using System.Text.Json;
using System.Diagnostics;

// Assembly attribute to enable the Lambda function's JSON input to be converted into a .NET class.
[assembly: LambdaSerializer(typeof(Amazon.Lambda.Serialization.SystemTextJson.DefaultLambdaJsonSerializer))]

namespace PutEventTimingTest;

public class Function
{
    private class TestClass
    {
        public int Id { get; set; }
        public string Name { get; set; }
    }

    public async Task FunctionHandler(string input, ILambdaContext context)
    {
        var services = new ServiceCollection();
        services.AddAWSService<IAmazonCloudWatchEvents>();

        ServiceProvider serviceProvider = services.BuildServiceProvider();

        var eventService = serviceProvider.GetRequiredService<IAmazonCloudWatchEvents>();

        var test = new TestClass { Id = 1, Name = "Slow Function Test" };

        var putEvent = new PutEventsRequest
        {
            Entries = new List<PutEventsRequestEntry> {
                new PutEventsRequestEntry {
                    Source = "testSource",
                    Detail = JsonSerializer.Serialize<TestClass>(test, new JsonSerializerOptions {
                        MaxDepth = 10,
                        ReferenceHandler = ReferenceHandler.Preserve,
                        PropertyNamingPolicy = JsonNamingPolicy.CamelCase,
                        PropertyNameCaseInsensitive = true,
                    }),
                    DetailType = "slowTestEvent",
                    Time = DateTime.UtcNow,
                    EventBusName = "testBus"
                } }
        };

        var stopwatch = Stopwatch.StartNew();
        await eventService.PutEventsAsync(putEvent);
        stopwatch.Stop();
        Console.WriteLine($"put took {stopwatch.ElapsedMilliseconds}ms");
    }
}

Possible Solution
unknown.
Additional Information/Context
No response
AWS .NET SDK and/or Package version used
<PackageReference Include="Amazon.Lambda.Core" Version="2.1.0" />
<PackageReference Include="Amazon.Lambda.Serialization.SystemTextJson" Version="2.3.1" />
<PackageReference Include="AWSSDK.CloudWatchEvents" Version="<IP_ADDRESS>" />
<PackageReference Include="AWSSDK.Extensions.NETCore.Setup" Version="3.7.7" />
<PackageReference Include="Microsoft.Extensions.DependencyInjection" Version="7.0.0" />

Targeted .NET Platform
.net 6
Operating System and version
Amazon Linux (Lambda)

Here is the log showing the times:
INIT_START Runtime Version: dotnet:6.v20	Runtime Version ARN: arn:aws:lambda:us-east-2::runtime:cc188eef0afc9baf44ce1d6bd4559c2d28b14aa063885a2f3b2bd2ba64788992
START RequestId: a4c5cf23-5cf4-42cc-9806-60348319516f Version: $LATEST
2023-09-11T21:47:59.768Z	a4c5cf23-5cf4-42cc-9806-60348319516f	info	put took 1,779 ms
END RequestId: a4c5cf23-5cf4-42cc-9806-60348319516f
REPORT RequestId: a4c5cf23-5cf4-42cc-9806-60348319516f	Duration: 2780.77 ms	Billed Duration: 2781 ms	Memory Size: 256 MB	Max Memory Used: 97 MB	Init Duration: 243.25 ms
START RequestId: 8a39dfd7-0ef2-4e50-8d3d-d2a945598d45 Version: $LATEST
2023-09-11T21:48:20.986Z	8a39dfd7-0ef2-4e50-8d3d-d2a945598d45	info	put took 99 ms
END RequestId: 8a39dfd7-0ef2-4e50-8d3d-d2a945598d45
REPORT RequestId: 8a39dfd7-0ef2-4e50-8d3d-d2a945598d45	Duration: 130.54 ms	Billed Duration: 131 ms	Memory Size: 256 MB	Max Memory Used: 98 MB

Now the example above basically took 2 seconds and that is too slow for an api call, but the actual code in my test environment is taking between 5 and 11 seconds to run the first time.
Here is 1, and the whole api process took 11 seconds.    Which is totally unacceptable for an api call.  I don't know what else is taking so long but this piece is the longest.
put took 5,796.000ms

@michaelakin Thanks for opening the issue. Could you please enable verbose logging in your code so that we could examine what operation is taking most time.
Amazon.AWSConfigs.LoggingConfig.LogResponses = Amazon.ResponseLoggingOption.Always;
Amazon.AWSConfigs.LoggingConfig.LogTo = Amazon.LoggingOptions.SystemDiagnostics;
Amazon.AWSConfigs.AddTraceListener("Amazon", new System.Diagnostics.ConsoleTraceListener());

SDK would try to resolve credentials (usually via attached IAM role) and region endpoint, before making the service API call.
Thanks,
Ashish

Sure, here it is:
INIT_START Runtime Version: dotnet:6.v20	Runtime Version ARN: arn:aws:lambda:us-east-2::runtime:cc188eef0afc9baf44ce1d6bd4559c2d28b14aa063885a2f3b2bd2ba64788992
START RequestId: 1ae90f3a-533b-4828-b8f9-e80bef41889f Version: $LATEST
Amazon Information: 0 :
2023-09-12T23:33:46.770Z	1ae90f3a-533b-4828-b8f9-e80bef41889f	info	UserCrypto is not supported.  This may be due to use of a non-Windows operating system or Windows Nano Server, or the current user account may not have its profile loaded. Unable to load shared library 'Crypt32.dll' or one of its dependencies. In order to help diagnose loading problems, consider setting the LD_DEBUG environment variable: libCrypt32.dll: cannot open shared object file: No such file or directory
Amazon Information: 0 :
2023-09-12T23:33:46.881Z	1ae90f3a-533b-4828-b8f9-e80bef41889f	info	Credentials found using environment variables.
Amazon Information: 0 :
2023-09-12T23:33:46.962Z	1ae90f3a-533b-4828-b8f9-e80bef41889f	info	The environment variable AWS_ENABLE_ENDPOINT_DISCOVERY was not set with a value.
Amazon Information: 1 :
2023-09-12T23:33:46.962Z	1ae90f3a-533b-4828-b8f9-e80bef41889f	info	The environment variable AWS_MAX_ATTEMPTS was not set with a value.
Amazon Information: 2 :
2023-09-12T23:33:46.962Z	1ae90f3a-533b-4828-b8f9-e80bef41889f	info	The environment variable AWS_RETRY_MODE was not set with a value.
Amazon Information: 3 :
2023-09-12T23:33:46.962Z	1ae90f3a-533b-4828-b8f9-e80bef41889f	info	The environment variable AWS_EC2_METADATA_SERVICE_ENDPOINT was not set with a value.
Amazon Information: 4 :
2023-09-12T23:33:46.963Z	1ae90f3a-533b-4828-b8f9-e80bef41889f	info	The environment variable AWS_EC2_METADATA_SERVICE_ENDPOINT_MODE was not set with a value.
Amazon Information: 5 :
2023-09-12T23:33:46.963Z	1ae90f3a-533b-4828-b8f9-e80bef41889f	info	The environment variable AWS_USE_DUALSTACK_ENDPOINT was not set with a value.
Amazon Information: 6 :
2023-09-12T23:33:46.963Z	1ae90f3a-533b-4828-b8f9-e80bef41889f	info	The environment variable AWS_USE_FIPS_ENDPOINT was not set with a value.
Amazon Information: 7 :
2023-09-12T23:33:46.963Z	1ae90f3a-533b-4828-b8f9-e80bef41889f	info	The environment variable AWS_IGNORE_CONFIGURED_ENDPOINT_URLS was not set with a value.
Amazon Information: 0 :
2023-09-12T23:33:46.963Z	1ae90f3a-533b-4828-b8f9-e80bef41889f	info	Unable to find a profile named 'default' in store Amazon.Runtime.CredentialManagement.CredentialProfileStoreChain
Amazon Information: 0 :
2023-09-12T23:33:46.982Z	1ae90f3a-533b-4828-b8f9-e80bef41889f	info	Region found using environment variable.
Amazon Information: 0 :
2023-09-12T23:33:46.982Z	1ae90f3a-533b-4828-b8f9-e80bef41889f	info	Resolved DefaultConfigurationMode for RegionEndpoint [us-east-2] to [Legacy].
Amazon Information: 1 :
2023-09-12T23:33:47.382Z	1ae90f3a-533b-4828-b8f9-e80bef41889f	info	Credentials found using environment variables.
Amazon Verbose: 0 :
2023-09-12T23:33:49.021Z	1ae90f3a-533b-4828-b8f9-e80bef41889f	info	Received response (truncated to 1024 bytes): [
{
"Entries": [
{
"EventId": "aa8dce84-02c5-09c9-399b-2694a0fb1d3c"
}
],
"FailedEntryCount": 0
}
]
2023-09-12T23:33:49.042Z	1ae90f3a-533b-4828-b8f9-e80bef41889f	info	put took 1781ms
END RequestId: 1ae90f3a-533b-4828-b8f9-e80bef41889f
REPORT RequestId: 1ae90f3a-533b-4828-b8f9-e80bef41889f	Duration: 2772.58 ms	Billed Duration: 2773 ms	Memory Size: 256 MB	Max Memory Used: 97 MB	Init Duration: 258.28 ms
START RequestId: ec64484a-1dc0-4649-96f7-43d2e69d9193 Version: $LATEST
Amazon Information: 1 :
2023-09-12T23:33:57.610Z	ec64484a-1dc0-4649-96f7-43d2e69d9193	info	Resolved DefaultConfigurationMode for RegionEndpoint [us-east-2] to [Legacy].
Amazon Information: 2 :
2023-09-12T23:33:57.612Z	ec64484a-1dc0-4649-96f7-43d2e69d9193	info	Credentials found using environment variables.
Amazon Verbose: 1 :
2023-09-12T23:33:57.735Z	ec64484a-1dc0-4649-96f7-43d2e69d9193	info	Received response (truncated to 1024 bytes): [
{
"Entries": [
{
"EventId": "6fe22bf8-4f03-b009-8090-4756b7bb84cf"
}
],
"FailedEntryCount": 0
}
]
2023-09-12T23:33:57.735Z	ec64484a-1dc0-4649-96f7-43d2e69d9193	info	put took 123ms
END RequestId: ec64484a-1dc0-4649-96f7-43d2e69d9193
REPORT RequestId: ec64484a-1dc0-4649-96f7-43d2e69d9193	Duration: 128.06 ms	Billed Duration: 129 ms	Memory Size: 256 MB	Max Memory Used: 98 MB

Here's the one that started all this in a minimal api.  Not sure the format you need here.
timestamp,message
1694622583135,"INIT_START Runtime Version: dotnet:6.v20	Runtime Version ARN: arn:aws:lambda:us-east-2::runtime:506d05e64635e29564050c864e65e71056f9b490ab564c9d40c9b73cdd9f030d
"
1694622583825,"START RequestId: 9826a85c-da3d-4d49-af9d-55631019b157 Version: $LATEST
"
1694622586502,"info: AWSSDK[0]
"
1694622586502,"Found AWS options in IConfiguration
"
1694622586683,"Amazon Information: 0 : UserCrypto is not supported.  This may be due to use of a non-Windows operating system or Windows Nano Server, or the current user account may not have its profile loaded. Unable to load shared library 'Crypt32.dll' or one of its dependencies. In order to help diagnose loading problems, consider setting the LD_DEBUG environment variable: libCrypt32.dll: cannot open shared object file: No such file or directory
"
1694622586863,"Amazon Information: 0 : Credentials found using environment variables.
"
1694622586864,"info: AWSSDK[0]
"
1694622586864,"Found credentials using the AWS SDK's default credential search
"
1694622587043,"Amazon Information: 0 : The environment variable AWS_ENABLE_ENDPOINT_DISCOVERY was not set with a value.
"
1694622587044,"Amazon Information: 1 : The environment variable AWS_MAX_ATTEMPTS was not set with a value.
"
1694622587044,"Amazon Information: 2 : The environment variable AWS_RETRY_MODE was not set with a value.
"
1694622587045,"Amazon Information: 3 : The environment variable AWS_EC2_METADATA_SERVICE_ENDPOINT was not set with a value.
"
1694622587045,"Amazon Information: 4 : The environment variable AWS_EC2_METADATA_SERVICE_ENDPOINT_MODE was not set with a value.
"
1694622587045,"Amazon Information: 5 : The environment variable AWS_USE_DUALSTACK_ENDPOINT was not set with a value.
"
1694622587045,"Amazon Information: 6 : The environment variable AWS_USE_FIPS_ENDPOINT was not set with a value.
"
1694622587062,"Amazon Information: 7 : The environment variable AWS_IGNORE_CONFIGURED_ENDPOINT_URLS was not set with a value.
"
1694622587065,"Amazon Information: 0 : Unable to find a profile named 'default' in store Amazon.Runtime.CredentialManagement.CredentialProfileStoreChain
"
1694622587183,"Amazon Information: 0 : Region found using environment variable.
"
1694622587702,"2023-09-13T16:29:47.663Z	9826a85c-da3d-4d49-af9d-55631019b157	info	Send Event
"
1694622588083,"2023-09-13T16:29:48.083Z	9826a85c-da3d-4d49-af9d-55631019b157	info	{""Entries"":[{""Detail"":""{\u0022$id\u0022:\u00221\u0022,\u0022token\u0022:{\u0022$id\u0022:\u00222\u0022,\u0022factorId\u0022:7,\u0022userId\u0022:400169,\u0022roleId\u0022:3,\u0022factorEmail\u0022:\u0022Sumit.Tipkurle@gmail.com\u0022,\u0022factorPhone\u0022:\u002211-222-3333\u0022,\u0022factorCompany\u0022:\u0022SRB COMPANYS\u0022,\u0022factorLogo\u0022:\u0022logo_1691606669602.jpg\u0022,\u0022factorClientId\u0022:93914,\u0022clientUserId\u0022:400169,\u0022groupId\u0022:14106,\u0022creditorUuid\u0022:\u002295e26a15-e0d8-46e8-a19b-4fcfa1d387d1\u0022,\u0022syndication\u0022:0,\u0022languageId\u0022:1,\u0022timeZoneId\u0022:17,\u0022countryId\u0022:25,\u0022dateFormat\u0022:\u0022dd/MM/yy\u0022,\u0022datePickerFormat\u0022:\u0022MM/dd/yyyy\u0022,\u0022factorStaffUserId\u0022:0,\u0022pageSize\u0022:0,\u0022asoniaUserName\u0022:\u0022\u0022,\u0022asoniaPassword\u0022:\u0022\u0022,\u0022asoniaFtpUserName\u0022:\u0022\u0022,\u0022creditSafeUserName\u0022:\u0022\u0022,\u0022creditSafePassword\u0022:\u0022\u0022,\u0022franchisorId\u0022:0},\u0022uploadOnlyAttachment\u0022:{\u0022$id\u0022:\u00223\u0022,\u0022invoiceGroupId\u0022:\u0022138938-20920-2002=22\u0022,\u0022invoice_amount\u0022:55169.0,\u0022mc_number\u0022:\u0022adipiscing laoreet.\u0022,\u0022load_number\u0022:\u0022aliquam adi\u0022,\u0022invoice_number\u0022:\u0022ut consectetuer magna eli\u0022,\u0022payment_id\u0022:1,\u0022device_id\u0022:\u0022laoreet dolore tincidunt d\u0022,\u0022location\u0022:\u0022dolor diam. ut eli\u0022,\u0022ip_address\u0022:null,\u0022ip_location\u0022:\u0022consectetuer sit euismod tincidunt magna. lor\u0022,\u0022comment\u0022:\u0022ipsum sit l\u0022}}"",""DetailType"":""InvoiceUploaded"",""EventBusName"":""invoice"",""Resources"":[],""Source"":""ffng"",""Time"":""2023-09-13T16:29:47.9448981Z"",""TraceHeader"":null}]}
"
1694622588103,"Amazon Information: 0 : Resolved DefaultConfigurationMode for RegionEndpoint [us-east-2] to [Legacy].
"
1694622588662,"Amazon Information: 1 : Credentials found using environment variables.
"
1694622591544,"Amazon Verbose: 0 : Received response (truncated to 1024 bytes): [{""Entries"":[{""EventId"":""8a742d0c-15fe-8511-a61e-c482c188b295""}],""FailedEntryCount"":0}]
"
1694622592304,"END RequestId: 9826a85c-da3d-4d49-af9d-55631019b157
"
1694622592304,"REPORT RequestId: 9826a85c-da3d-4d49-af9d-55631019b157	Duration: 8478.87 ms	Billed Duration: 8479 ms	Memory Size: 256 MB	Max Memory Used: 130 MB	Init Duration: 688.18 ms
"
1694622670891,"START RequestId: 7a51f851-556b-4ac1-89e6-5848e4cf86ab Version: $LATEST
"
1694622670943,"2023-09-13T16:31:10.943Z	7a51f851-556b-4ac1-89e6-5848e4cf86ab	info	Send Event
"
1694622670980,"2023-09-13T16:31:10.980Z	7a51f851-556b-4ac1-89e6-5848e4cf86ab	info	{""Entries"":[{""Detail"":""{\u0022$id\u0022:\u00221\u0022,\u0022token\u0022:{\u0022$id\u0022:\u00222\u0022,\u0022factorId\u0022:7,\u0022userId\u0022:400169,\u0022roleId\u0022:3,\u0022factorEmail\u0022:\u0022Sumit.Tipkurle@gmail.com\u0022,\u0022factorPhone\u0022:\u002211-222-3333\u0022,\u0022factorCompany\u0022:\u0022SRB COMPANYS\u0022,\u0022factorLogo\u0022:\u0022logo_1691606669602.jpg\u0022,\u0022factorClientId\u0022:93914,\u0022clientUserId\u0022:400169,\u0022groupId\u0022:14106,\u0022creditorUuid\u0022:\u002295e26a15-e0d8-46e8-a19b-4fcfa1d387d1\u0022,\u0022syndication\u0022:0,\u0022languageId\u0022:1,\u0022timeZoneId\u0022:17,\u0022countryId\u0022:25,\u0022dateFormat\u0022:\u0022dd/MM/yy\u0022,\u0022datePickerFormat\u0022:\u0022MM/dd/yyyy\u0022,\u0022factorStaffUserId\u0022:0,\u0022pageSize\u0022:0,\u0022asoniaUserName\u0022:\u0022\u0022,\u0022asoniaPassword\u0022:\u0022\u0022,\u0022asoniaFtpUserName\u0022:\u0022\u0022,\u0022creditSafeUserName\u0022:\u0022\u0022,\u0022creditSafePassword\u0022:\u0022\u0022,\u0022franchisorId\u0022:0},\u0022uploadOnlyAttachment\u0022:{\u0022$id\u0022:\u00223\u0022,\u0022invoiceGroupId\u0022:\u0022138938-20920-2002=22\u0022,\u0022invoice_amount\u0022:55169.0,\u0022mc_number\u0022:\u0022adipiscing laoreet.\u0022,\u0022load_number\u0022:\u0022aliquam adi\u0022,\u0022invoice_number\u0022:\u0022ut consectetuer magna eli\u0022,\u0022payment_id\u0022:1,\u0022device_id\u0022:\u0022laoreet dolore tincidunt d\u0022,\u0022location\u0022:\u0022dolor diam. ut eli\u0022,\u0022ip_address\u0022:null,\u0022ip_location\u0022:\u0022consectetuer sit euismod tincidunt magna. lor\u0022,\u0022comment\u0022:\u0022ipsum sit l\u0022}}"",""DetailType"":""InvoiceUploaded"",""EventBusName"":""invoice"",""Resources"":[],""Source"":""ffng"",""Time"":""2023-09-13T16:31:10.9446652Z"",""TraceHeader"":null}]}
"
1694622670981,"Amazon Information: 2 : Credentials found using environment variables.
"
1694622671142,"Amazon Verbose: 1 : Received response (truncated to 1024 bytes): [{""Entries"":[{""EventId"":""972b0c74-7063-7560-1d42-427fce1015bf""}],""FailedEntryCount"":0}]
"
1694622671146,"END RequestId: 7a51f851-556b-4ac1-89e6-5848e4cf86ab
"
1694622671146,"REPORT RequestId: 7a51f851-556b-4ac1-89e6-5848e4cf86ab	Duration: 254.29 ms	Billed Duration: 255 ms	Memory Size: 256 MB	Max Memory Used: 131 MB
"

Sure, here it is:
INIT_START Runtime Version: dotnet:6.v20 Runtime Version ARN: arn:aws:lambda:us-east-2::runtime:cc188eef0afc9baf44ce1d6bd4559c2d28b14aa063885a2f3b2bd2ba64788992 START RequestId: 1ae90f3a-533b-4828-b8f9-e80bef41889f Version: $LATEST Amazon Information: 0 : 2023-09-12T23:33:46.770Z 1ae90f3a-533b-4828-b8f9-e80bef41889f info UserCrypto is not supported. This may be due to use of a non-Windows operating system or Windows Nano Server, or the current user account may not have its profile loaded. Unable to load shared library 'Crypt32.dll' or one of its dependencies. In order to help diagnose loading problems, consider setting the LD_DEBUG environment variable: libCrypt32.dll: cannot open shared object file: No such file or directory Amazon Information: 0 : 2023-09-12T23:33:46.881Z 1ae90f3a-533b-4828-b8f9-e80bef41889f info Credentials found using environment variables. Amazon Information: 0 : 2023-09-12T23:33:46.962Z 1ae90f3a-533b-4828-b8f9-e80bef41889f info The environment variable AWS_ENABLE_ENDPOINT_DISCOVERY was not set with a value. Amazon Information: 1 : 2023-09-12T23:33:46.962Z 1ae90f3a-533b-4828-b8f9-e80bef41889f info The environment variable AWS_MAX_ATTEMPTS was not set with a value. Amazon Information: 2 : 2023-09-12T23:33:46.962Z 1ae90f3a-533b-4828-b8f9-e80bef41889f info The environment variable AWS_RETRY_MODE was not set with a value. Amazon Information: 3 : 2023-09-12T23:33:46.962Z 1ae90f3a-533b-4828-b8f9-e80bef41889f info The environment variable AWS_EC2_METADATA_SERVICE_ENDPOINT was not set with a value. Amazon Information: 4 : 2023-09-12T23:33:46.963Z 1ae90f3a-533b-4828-b8f9-e80bef41889f info The environment variable AWS_EC2_METADATA_SERVICE_ENDPOINT_MODE was not set with a value. Amazon Information: 5 : 2023-09-12T23:33:46.963Z 1ae90f3a-533b-4828-b8f9-e80bef41889f info The environment variable AWS_USE_DUALSTACK_ENDPOINT was not set with a value. Amazon Information: 6 : 2023-09-12T23:33:46.963Z 1ae90f3a-533b-4828-b8f9-e80bef41889f info The environment variable AWS_USE_FIPS_ENDPOINT was not set with a value. Amazon Information: 7 : 2023-09-12T23:33:46.963Z 1ae90f3a-533b-4828-b8f9-e80bef41889f info The environment variable AWS_IGNORE_CONFIGURED_ENDPOINT_URLS was not set with a value. Amazon Information: 0 : 2023-09-12T23:33:46.963Z 1ae90f3a-533b-4828-b8f9-e80bef41889f info Unable to find a profile named 'default' in store Amazon.Runtime.CredentialManagement.CredentialProfileStoreChain Amazon Information: 0 : 2023-09-12T23:33:46.982Z 1ae90f3a-533b-4828-b8f9-e80bef41889f info Region found using environment variable. Amazon Information: 0 : 2023-09-12T23:33:46.982Z 1ae90f3a-533b-4828-b8f9-e80bef41889f info Resolved DefaultConfigurationMode for RegionEndpoint [us-east-2] to [Legacy]. Amazon Information: 1 : 2023-09-12T23:33:47.382Z 1ae90f3a-533b-4828-b8f9-e80bef41889f info Credentials found using environment variables. Amazon Verbose: 0 : 2023-09-12T23:33:49.021Z 1ae90f3a-533b-4828-b8f9-e80bef41889f info Received response (truncated to 1024 bytes): [ { "Entries": [ { "EventId": "aa8dce84-02c5-09c9-399b-2694a0fb1d3c" } ], "FailedEntryCount": 0 } ] 2023-09-12T23:33:49.042Z 1ae90f3a-533b-4828-b8f9-e80bef41889f info put took 1781ms END RequestId: 1ae90f3a-533b-4828-b8f9-e80bef41889f REPORT RequestId: 1ae90f3a-533b-4828-b8f9-e80bef41889f Duration: 2772.58 ms Billed Duration: 2773 ms Memory Size: 256 MB Max Memory Used: 97 MB Init Duration: 258.28 ms START RequestId: ec64484a-1dc0-4649-96f7-43d2e69d9193 Version: $LATEST Amazon Information: 1 : 2023-09-12T23:33:57.610Z ec64484a-1dc0-4649-96f7-43d2e69d9193 info Resolved DefaultConfigurationMode for RegionEndpoint [us-east-2] to [Legacy]. Amazon Information: 2 : 2023-09-12T23:33:57.612Z ec64484a-1dc0-4649-96f7-43d2e69d9193 info Credentials found using environment variables. Amazon Verbose: 1 : 2023-09-12T23:33:57.735Z ec64484a-1dc0-4649-96f7-43d2e69d9193 info Received response (truncated to 1024 bytes): [ { "Entries": [ { "EventId": "6fe22bf8-4f03-b009-8090-4756b7bb84cf" } ], "FailedEntryCount": 0 } ] 2023-09-12T23:33:57.735Z ec64484a-1dc0-4649-96f7-43d2e69d9193 info put took 123ms END RequestId: ec64484a-1dc0-4649-96f7-43d2e69d9193 REPORT RequestId: ec64484a-1dc0-4649-96f7-43d2e69d9193 Duration: 128.06 ms Billed Duration: 129 ms Memory Size: 256 MB Max Memory Used: 98 MB

@michaelakin I'm unsure if I see the same delay. Are you able to reproduce the issue consistently at your end?

Yes, it is very consistent.
Here are the two lines that highlight the problem.
1694622592304,"REPORT RequestId: 9826a85c-da3d-4d49-af9d-55631019b157 Duration: 8478.87 ms Billed Duration: 8479 ms Memory Size: 256 MB Max Memory Used: 130 MB Init Duration: 688.18 ms
"
1694622671146,"REPORT RequestId: 7a51f851-556b-4ac1-89e6-5848e4cf86ab Duration: 254.29 ms Billed Duration: 255 ms Memory Size: 256 MB Max Memory Used: 131 MB

I'm seeing something very similar with the dynamo client as well. Logged the metrics:
First call:

Second call:

I expect the first call to be a little slower, by like 1-200ms for the HTTP setup etc, not having a difference of 2-3 seconds. Checked the metrics on DynamoDB on all response times are under 50ms. So to me, this is definitely looks like an SDK issue.
My stack: .NET 8 AOT, AL2023 on arm64, SourceGenerators for anything where I can. Latest packages etc.
Happy to try out things out to help get this resolved as this will ultimately cost me and others money :)


Support Inputs in pipeline config, hashes are per task

Add support for "inputs": [<file glob>] to pipeline config
In the case of "inputs", use git ls-files to calculate file hashes
Remove package-level hash and file hash
Hash combinations of package-inputs
Hashing of package-tasks is now done inline while walking the graph
Update e2e test to highlight new hashing behavior

Because task hashing now only takes into account the hash of task-graph dependencies, tasks that don't have task-graph dependencies won't have new hashes when package-dependencies change. The classic example is lint. If a depends on b, and b changes, that should no longer force a cache miss for a#lint, so long as the lint task has no dependencies.
Remaining work:

[x] Update fallback for git ls-file to properly handle inputs
[x] Add tests for inputs
[x] Update global hash key (not technically necessary, but may be a good idea)

Fixes #523

lgtm

This is a very exciting change. One thing I wanted to note is that this should likely also be documented as a configuration option.

@ObliviousHarmony docs coming in #1046


Server-side source context

Add support for serve-side source context using source bundles.
https://docs.sentry.io/workflow/debug-files/#source-context
Overview
At the moment, the Contextify Frames Integration in the SDK automatically grabs context lines when those are available nearby a running binary.
We document how this can be used when deploying to a serverless platform.
While that integration can be used in certain contexts, it won't help when you (have to) distribute binaries without source code available.
The solution is to add source context on the Sentry server, and that is done by uploading source bundles after building a program.

Development notes
Creating source bundles
Use sentry-cli to generate a zip archive with source files and a manifest:

Bump symbolic dependency in Cargo.toml to at least https://github.com/getsentry/symbolic/commit/8f9a01756e48dcbba2e42917a064f495d74058b7
(edit: not needed anymore, bumped upstream).

Run
cargo run -- difutil bundle-sources /path/to/binary...

Inspect manifest.json in source archive
unzip -p /path/to/file.src.zip manifest.json | jq -C | less

code_id is the gnu.build-id.
debug_id is a transformation from code_id if it exists, or otherwise a hash of the text section.

See<EMAIL_ADDRESS>

References:

https://docs.sentry.io/development/sdk-dev/event-payloads/debugmeta/
<EMAIL_ADDRESS>https://github.com/gimli-rs/findshlibs

TODO
On the SDK, we need:

[ ] Send debug_id in the event payload along with other required files in the images attribute.
See https://docs.sentry.io/development/sdk-dev/event-payloads/debugmeta/.

[ ] Linux support
[ ] Windows support
[ ] macOS support

This feature would be extremely helpful. 🚀

Is this work scheduled / is there going to be some other way to get the source context in stacktraces without shipping the source alongside built binaries? We love Sentry and love that feature, but we don't want to start shipping source code in our containers that hold our golang web servers just to get slightly more usable stacktraces. I know that "Stack trace linking" via Github integration is now in beta, and that for Javascript there's a way to upload source maps as part of releases, and when I squint that looks like the same thing that we'd want to do here, but whatever the implementation method I'd really like to see the surrounding code inside stacktraces on error pages.

Is this work scheduled / is there going to be some other way to get the source context in stacktraces without shipping the source alongside built binaries? We love Sentry and love that feature, but we don't want to start shipping source code in our containers that hold our golang web servers just to get slightly more usable stacktraces. I know that "Stack trace linking" via Github integration is now in beta, and that for Javascript there's a way to upload source maps as part of releases, and when I squint that looks like the same thing that we'd want to do here, but whatever the implementation method I'd really like to see the surrounding code inside stacktraces on error pages.

Sharing here that another viable way to get source code context in stack traces is to use Sentry's GitHub/Gitlab integrations:
https://docs.sentry.io/product/integrations/github/#stack-trace-linking
https://docs.sentry.io/product/integrations/gitlab/#stack-trace-linking

Sharing here that another viable way to get source code context in stack traces is to use Sentry's GitHub/Gitlab integrations:
https://docs.sentry.io/product/integrations/github/#stack-trace-linking https://docs.sentry.io/product/integrations/gitlab/#stack-trace-linking

As it has been written, Stack trace linking is supported only for Python and JS.

Hey folks, is #44525 something you could take on as part of this initiative? I'm happy to guide

@armenzg I assume we could do something with our GitHub integration.
Sample error from our profiling ingestion service https://sentry.sentry.io/issues/3908326163/ (internal link). All paths are preserved in the stack trace, so we could fetch the source context with that from a repo.


"No Man's Sky" cannot detect HDR mode.

I tested several HDR games, and most of them had no issues. However, "No Man's Sky" couldn't detect HDR. This game normally has an HDR option when using a true HDR screen, but it doesn't show up when using VDD.

I have also encountered this in a few games like "Elden Ring" or "Doom Eternal". When I try to enable HDR in the Video Settings I get a message along the lines of: "The Monitor does not support HDR.".  HDR is definitely on and it also work for some other games like "Monster Hunter World". I also tried to disconnect/disable all other monitors but the issue persists.

same issue. seems to occur with many games. this has compelled me to buy an HDMI dummy plug instead of continuing to hassle with virtual displays.

same issue. this seems to occur in many games. this shortcoming spurred me to buy an hdmi dummy plug. can't continue waiting for virtual display implementations to figure all the bugs out.

I've summed up that this is due to these games using "NVIDIA-specific NVAPI HDR", which doesn't work the same as the rest of Windows HDR. This is the same reason why these games don't look correct when streaming via Sunshine.
In Elden Ring SpecialK can rewrite these NVAPI calls on the fly into DXGI which makes the HDR look as expected via Sunshine. This works when using a suitably capable EDID emulator, but I don't believe this approach will work for a VDD (at least not without substantial effort). The NVAPI HDR cannot be enabled without the target display being connected to a Nvidia display adapter.


Update UserGuide.md and fix some messages in commands

Codecov Report

Merging #169 (cdb9899) into master (3ace693) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head cdb9899 differs from pull request most recent head 8b2e2f5. Consider uploading reports for the commit 8b2e2f5 to get more accurate results

@@            Coverage Diff            @@
##             master     #169   +/-   ##
=========================================
  Coverage     71.14%   71.14%
  Complexity      783      783
=========================================
  Files           111      111
  Lines          2596     2596
  Branches        340      340
=========================================
  Hits           1847     1847
  Misses          639      639
  Partials        110      110

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Fix more lint issues across services

After these changes we only have <30 lint issues remaining.

Codecov Report

Merging #1667 into master will decrease coverage by <.01%.
The diff coverage is 80%.

@@            Coverage Diff             @@
##           master    #1667      +/-   ##
==========================================
- Coverage   48.75%   48.74%   -0.01%
==========================================
  Files          27       27
  Lines        4080     4076       -4
==========================================
- Hits         1989     1987       -2
+ Misses       1672     1669       -3
- Partials      419      420       +1

Impacted Files
Coverage Δ

snapshot/overlay/overlay.go
47.58% <0%> (ø)
:arrow_up:

snapshot/storage/bolt.go
61.55% <100%> (ø)
:arrow_up:

metadata/content.go
31.57% <100%> (+0.53%)
:arrow_up:

snapshot/btrfs/btrfs.go
50.6% <100%> (ø)
:arrow_up:

metadata/db.go
64% <0%> (-1.5%)
:arrow_down:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 3679a55...ab5f4e2. Read the comment docs.

LGTM
If you want more warnings, I think you crank up the levels.


Add NAT support

This PR adds NAT/proxy support.
Currently after _getCapabilities() succeeds node-onvif will resolve to use direct ip address of the devices and ignore the xaddr/addess passed in by the user in  constructor OnvifDevice
This is undesired if the device is behind a NAT or is routed by an nginx server with multiple subpaths such as <IP_ADDRESS>:8000 or <IP_ADDRESS>/route-to-device/. node-onvif won't be able to connect.
Change in this PR allows user to pass in ip address or url pathname as the preferred connection string  so node-onvif will always use this value to connect to the device and ignore the device's internal ip address.
For example:
OnvifDevice({ address: '10.10.2:300', user: 'user', 'pass': 'pass'})
OnvifDevice({ address: '<IP_ADDRESS>/route-to-device', user: 'user', 'pass': 'pass'})
Tested with node 6 and 8

Sorry my action is late. I'm grateful for your PR.


cnear library blog post

@joe-rlo , quick question, should the blog post be part of docs.near.org , or the new substack blog site? (or maybe both?)
https://github.com/NEAR-DevHub/content/issues/5

Published on Substack: https://neardevhub.substack.com/p/the-cnear-library


CFFL

CFFL

Linter check found the following problems:
The following problems have been found:
ERROR: /tmp/abs_cdubi4665i/clone/recipe/meta.yaml:35: duplicate_key_in_meta_yaml: The recipe meta.yaml contains a duplicate key
Errors were found