Don't validate trailing whitespace for *.md files.

Markdown file has certain lines that have trailing whitespace and they are legitimate as a way to prevent markdown rendering from collapsing the newlines.
This is a follow-up on #24951

Thank you for your contribution! Follow this checklist to help us incorporate your contribution quickly and easily:

[ ] Mention the appropriate issue in your description (for example: addresses #123), if applicable. This will automatically add a link to the pull request in the issue. If you would like the issue to automatically close on merging the pull request, comment fixes #<ISSUE NUMBER> instead.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.
To check the build health, please visit https://github.com/apache/beam/blob/master/.test-infra/BUILD_STATUS.md
GitHub Actions Tests Status (on master branch)

See CI.md for more information about GitHub Actions CI.

R: @kennknowles

Closed in favor of https://github.com/apache/beam/pull/25055, can always revert that and get this in.


YouTube links don't work anymore

They used to be fine, but now YouTube channel or video links don't yield a real title but Before you continue to YouTube.

Links used: https://www.youtube.com/teded, https://www.youtube.com/watch?v=xy9nj94xvKA.
It looks like YouTube's cookie consent page's title for when you first open the site in a browser.

Hmm interesting, those are both still resolving correctly for me
[TED-Ed - YouTube](https://www.youtube.com/teded)
[How do wind turbines work? - Rebecca J. Barthelmie and Sara C. Pryor - YouTube](https://www.youtube.com/watch?v=xy9nj94xvKA)

I see that if I can block cookies from consent.youtube.com this screen can be bypassed but there doesn't seem to be any method of disabling cookies in the electron WebBrowser.
I can block all web requests to that url in my electron WebBrowser but I'm not certain if that will have the intended effect as I can't seem to recreate that behavior myself.

I've also tried this plugin, which still works for me for YouTube.

I had no idea that plugin existed! Interesting, if I had found that when I started I likely would have just done some pull requests instead. Seems it utilizes node-fetch, I'll check to see if node-fetch passes the muster on sites that the CORS proxy failed on and do some comparisons as I want to ensure this plugin supports mobile.

Hm yeah, that solution fails on domains that enforce CORS so if you attempted to paste:
https://www.newegg.com/
or
https://www.reddit.com/r/ObsidianMD/
it fails to resolve the title.
I'll continue to see if I can reproduce the consent.youtube.com cookie issue, I'll ping you on discord to see if my filter blocking web requests to that subdomain corrects the issue for you.

Any news ? I also face this issue

The new Obsidian release (v0.12.11) might help with CORS restrictions.

YouTube videos work now (a change on YouTube's end), but channels and playlists still turn up as Before you continue to YouTube.
@zolrath do you think this is possible now, with the Obsidian CORS API update and stuff that is in the other plugin?

YouTube Videos, channels, and playlists work for me.

For china users, we need proxy settings to let it work, will it be possible to be added in the plugin or only can have it in Obsidian itself?

Now videos often turn up "Site Unreachable" but find the right title with the refresh command.

For china users, we need proxy settings to let it work, will it be possible to be added in the plugin or only can have it in Obsidian itself?

add below line in main.js of the plugin.
window.webContents.session.setProxy({"mode":"system"});


[Question] Contributing to the documentation

Subject

[x] I would like to contribute to the project (code, documentation, advocacy, integration, ...)

Now my question:
I would like to contribute to the documentation and describe some use cases that are not listed right now (e.g. create alias with multiple recipients) or update some hints (fail2ban commands from debugging also in fail2ban or at least mentioned).
How is the procedure here? As far as i see i can simply edit the wiki pages. Is it desired that i open an issue for that changes to be approved?
Keep up the good work.
Cheers!

I haven't seen any rules about who can edit the wiki, so just make sure that you know what you are doing (test first!). You don't need to open issues. Thanks for helping!


webpack-remove-empty-scripts is removing asset.php files

Describe the bug
The build process is running @WordPress/Scripts. This will also output an asset.php file for each CSS file generated.
I want to use that plugin to remove the .JS files that get created with the compiled CSS files. These .JS files are empty and just annoying to have in there.
When using the plugin it is also removing my asset.php files as well. I have tried the options including ignoring asset.php files but it still doesn't work.
Any ideas? Below is the code I have:
const otherStyleConfig = {
    ...defaultConfig,
    entry: {
        'blog': path.resolve( './src/sass', 'blog.scss' ),
        'editor': path.resolve( './src/sass', 'editor.scss' ),
        'header-footer': path.resolve( './src/sass', 'header-footer.scss' ),
        'partners': path.resolve( './src/sass', 'partners.scss' ),
        'posts-and-pages': path.resolve( './src/sass', 'posts-and-pages.scss' ),
        'resource-center': path.resolve( './src/sass', 'resource-center.scss' ),
        'resource-single': path.resolve( './src/sass', 'resource-single.scss' ),
        'support-center': path.resolve( './src/sass', 'support-center.scss' ),
        'table-of-contents': path.resolve( './src/sass', 'table-of-contents.scss' ),
        'widgets': path.resolve( './src/sass', 'widgets.scss' ),
    },
    module: {
        rules: [
        {
            test: /\.scss$/,
            exclude: /node_modules/,
            use: [
                MiniCssExtractPlugin.loader,
                {
                    loader: "css-loader",
                    options: {
                        url: false, //Don't do anything with image url's
                    },
                },
                {
                    loader: "postcss-loader",
                    options: {
                        postcssOptions: {
                            plugins: [
                                sortMediaQueries(),
                                presetEnv(),
                                mergeLonghand(),
                                mergeRules(),
                                cssnano( {
                                    reduceIdents: false,
                                    zindex: false,
                                    autoprefixer: false,
                                } ),
                            ],
                            options: {},
                        },
                     },
                },
                'resolve-url-loader',
                'sass-loader',
            ],
        },
        ],
    },
    output: {
        path: path.resolve(__dirname, 'build/css'),
    },
    devtool: 'source-map',
    plugins: [
        new MiniCssExtractPlugin(),
        new DependencyExtractionWebpackPlugin(),
        new RemoveEmptyScriptsPlugin({
            verbose: true,
            ignore: [
                /.*asset.php$/,
            ]
        }),
    ]
}

To Reproduce

Create a simple SASS compile in Webpack config like the example above.
Use @WordPress/Scripts for the build process. This should be in your package.json file "build": "wp-scripts build --mode=production",
You will see the empty .js files are no longer there but the asset.php files are not there either. If you remove the plugin from the Webpack config you will see that the asset.php files are there and the empty .js files.

Expected behavior
To just remove the empty JS files and not asset.php files
Dev Environment (please complete the following information):

OS: MacOS
Node: v14.17.0

@webdiscus Can I just provide you with a small repo? I think docker is overkill here.

@webdiscus Can I just provide you with a small repo? I think docker is overkill here.

yes, of cause a repo is enough. I have macOS, M1.

@webdiscus Here is the test repo for you:
https://github.com/tstokes8040/remove-empty-scripts-test
Please let me know if you have any questions.

@tstokes8040
I found two bugs/features in Webpack. They are very difficult to around.
When is deleted empty main.js asset via Webpack API compilation.deleteAsset(file), then Webpack automatically deleted main.asset.php too.
P.S.: I have an idea, but I need time to test and not break everything that already works ;-)

@tstokes8040,
I have fixed the issue. Try please v0.8.3.

@webdiscus NICE WORK! Thank you SO much for this update. This is amazing!!!! It works great! I will go ahead and close out this bug. Thanks again!

@tstokes8040
By fixing this issue was broken compatibility with vast majority other plugins.
Therefore I have new v1.0.0 released.
In this version was reverted defaults behaviour as in v0.8.1 - remove empty scripts before other plugins will be called.
To fix your issue is added new stage option with following values:

RemoveEmptyScriptsPlugin.STAGE_BEFORE_PROCESS_PLUGINS (default)
Remove empty scripts before processing other plugins.
For example, exact this stage needs for properly work of the webpack-manifest-plugin.
RemoveEmptyScriptsPlugin.STAGE_AFTER_PROCESS_PLUGINS
Remove empty scripts after processing all other plugins.
For example, exact this stage needs for properly work of the @wordpress/dependency-extraction-webpack-plugin.

If you update to v1.0.0 then add the stage option as following:
new RemoveEmptyScriptsPlugin({
    stage: RemoveEmptyScriptsPlugin.STAGE_AFTER_PROCESS_PLUGINS, // <- use this option
}),

@webdiscus Thanks so much! I've got this updated!!


number of users on /teams/ list is wrong

double counting

also folders, can see # of folders total and not what you have access to


Port write paths of ReactiveDocumentService v1 to v2

What this PR does:
Which issue(s) this PR fixes:
Fixes #1729
Checklist

[x] Changes manually tested
[x] Automated Tests added/updated
[x] Documentation added/updated
[x] CLA Signed: DataStax CLA

Hey @EricBorczuk, it's impossible to review this due to the git thinking that there were bunch of changes in the DocumentWriteService.. So I'll push a commit with the simple rename if that's OK.. This would also make sure write bridge stuff is correctly mapped in git as move and not new file..
You just need to update your local branch then.. I'll review it asap..


Expand to other torrent sources

Thanks for this tool, I was actively looking for exactly that some weeks ago, glad to find it on r/commandline today!
In Stremio, a GUI application that does similar things, Torrentio is a major source for torrents and seems to simply be the best for most movies or TV shows in terms of seeds and leechers, at least for 4K. Would it be feasible to expand cthulhu so that it can fetch magnets from Torrentio too (and possibly others in the future)?

I appreciate you trying the tool out.
From what I read, TorrentIO itself has a scraper that scrapes from other sources (nyaa.si, piratebay, etc), so it would be difficult to integrate that directly into cthulhu. What I can probably do instead is just add more sources manually. I'll do some more research to see if I can implement something similar to TorrentIO.

Oh, that makes sense. Actually I never really tried to go to torrentio directly outside Stremio, but that would explain why most sources usually appear as coming from torrentio itself. Thanks for your reply.
I'll keep using your tool anyway, it is pretty useful. My only concern is that peerflix seems to be unmaintained as opposed to webtorrent-cli that notflix uses, but on the other hand it's more minimal which I think is better.
On 2022-01-09 21:36 Raiyan @.***> wrote:

I appreciate you trying the tool out.
From what I read, TorrentIO itself has a scraper that scrapes from
other sources (nyaa.si, piratebay, etc), so it would be difficult to
integrate that directly into cthulhu. What I can probably do instead
is just add more sources manually. I'll do some more research to see
if I can implement something similar to TorrentIO.
--
Reply to this email directly or view it on GitHub:
https://github.com/trianglecirclexyz/cthulhu/issues/2#issuecomment-100
8379341
You are receiving this because you authored the thread.
Message ID:
@.***>

Yeah, I also used peerflix because it had more features such as being able to play multiple files at once. If you prefer to switch to webtorrent, you can just change os.system(f'peerflix --mpv -a \'{magnet_link}\'') to os.system(f'webtorrent --mpv \'{magnet_link}\'') on line 53 easily enough. If peerflix starts causing any problems, I might make webtorrent the default.

Great to hear, makes cthulhu future-proof while keeping it minimal as long as possible. It could be an option with a default value (if the dependency is met) I guess. I read here that webtorrent is supposed to be faster than peerflix but I have no idea if that is true, and sensible.
While we're at it, I opened an issue at webtorrent's repository for improving ssh use, but I'm wondering if this is something that could be done on cthulhu (or notflix in that case since I was thinking about webtorrent) side instead?
I posted there because I was thinking it could be done by altering the mpv command behind webtorrent/peerflix magnet --mpv --remote into something like $TERMINAL -e bash -c "DISPLAY=:0 mpv localhost-url, but I failed to code that in node and maybe there could be easier ways if doing that into cthulhu instead? Let me know and I can open an issue here if that's relevant. Else I'll stop the off-topic here!

Hmm I was investigating some hacky ways for it to work via ssh directly from cthulhu, but was not successful. Might play around with it some more later down the line. Thanks for the suggestion.

Added support for new sources as explained by the most recent pull request (#8). Current sources are nyaa and 1337x, but more can be added fairly easily by adding a new class and including the necessary methods for parsing. Planning on making config file for changing the default source so users don't have to always specify --source <source>.


INTRO

Proshach's Introduction

Hello, I'm Proshach!
Thanks for visiting my page. I'm a programmer who loves Python!
Click me!
Check out my menu:

Home
About Me
Projects
Contact

Test on Intro


improved logging - include node url, allow ?reqID query argument(s)

Node URI included in logs
Allow ?reqID=... request argument, which will be included in the logs (will be used to correlate relay logs with validation queue logs, i.e. by blockhash)
Allow multiple reqID args, in format of: ?reqID:name=something&reqID:name2=also_something

Tagged v0.7a2

Tagged commit b7b858e as v0.7-alpha3

Tagged commit 965de9c as v0.7-alpha4


Arch Linux support

Hello guys,
did anyone try to install vNext on Arch Linux?
Thanks.

I recommend working with the .NET CLI folks on this issue.


Error in setCookie

It was working just few minutes ago and now the cookies.set() is not working? What is the reason?

Sorry for not elaborating the question, I posted the issue ahead presuming it might be the package problem when it suddenly stopped working without any change in our code. But during our debugging process, it is found that the size of the cookie exceeded the limit and that was the reason of error. What is the standard process for storing such large data in cookies? By the way thanks for your response.

Hi @Sagaryalioe
Cookies should not exceed 4K (including name and all the formatting). You are probably safe if you keep it under 4000 bytes because you still have 96 bytes for the name and options. See https://stackoverflow.com/a/4604212/1692356
However, keep in mind that your cookies are sent with all your HTTP requests. You might want to use the localStorage instead because the limit is 5 MB: https://developer.mozilla.org/en-US/docs/Web/API/Window/localStorage
However, with the local storage you would not be able to do server-side rendering if you need it.
I hope that helps!

Thanks for the suggestion.


Remove unused kueue-viz frontend dependencies

What type of PR is this?
/kind bug

What this PR does / why we need it:
Removes yet now unused chart.js and react-chartjs-2 as they are still not compatible with react 19
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?

NONE

/lgtm
Thanks!

/kind cleanup

/remove-kind cleanup

/assign @mimowo @trasc @tenzen-y


Add example of Array comprehesion expression

This adds an example of how to use expressions in a for loop array comprehension.
This is something found in other programming languages (and yet others use map for this) so for programmers who know this it will be valuable to see a minimal example of how it's done in haxe.

While this might be a worthwhile addition, it's not a good place for it. The example in question appears in the context of https://haxe.org/manual/lf-array-comprehension.html, so randomly adding two lines of code there doesn't work so well.

I added these lines because it appears in that article.
That article does not have a good example of how the expression can be used to perform the same functionality as a map function.
The first example only puts the same values that are being iterated over in the array.
There is a more complex example on that page, but that also introduces multiple for loops being used in the same comprehension.
I thought it would be useful to have an example that's somewhat in between in complexity.


azure functions Could not load file or assembly System.IdentityModel.Tokens.Jwt.dll The system cannot find the file specified.

When I run my Azure Functions project in vscode, the System.IdentityModel.Tokens.Jwt.dll file is being removed from the \PROJECTNAME\bin\Debug\net6.0\bin folder.
The only way I can find to fix this overly aggressive cleaning of the folder is to use the  _FunctionsSkipCleanOutput setting.  Of course this also leave so many other DLLs in the folder as well.
<TargetFramework>net6.0</TargetFramework>
<AzureFunctionsVersion>v4</AzureFunctionsVersion>
<_FunctionsSkipCleanOutput>true</_FunctionsSkipCleanOutput>

Yes, I am creating objects from this DLL in my code.
Example:  var handler = new System.IdentityModel.Tokens.Jwt.JwtSecurityTokenHandler();
But for some reason, the tooling is not recognizing that my code is really using the DLL and that it must be included and not removed.
Can you please fix this?
Thank you!

Hi @longtimedeveloper
Sorry for the issue, but I don't think the extension tools can really do anything about this.  If you check your task.json, we are running a dotnet clean before a build or publish task.
Since we're just running dotnet CLI command, I don't think we have control over exactly what gets cleaned and what doesn't.  There may be a way to set up exceptions and pass those files in as arguments?
You may also have some better luck asking over at the C# Extension since they are .NET subject matter experts.  They may have a setting in their extension for this already.

@nturinski thank you for the response.  I'll follow your recommendation and log the issues in C# Extension.  Thank you.


[Feature] Window & Display & SwapChain

Progress:

[x] lstg.Display
[x] lstg.Window
[x] lstg.SwapChain

Woah, that's a lot of changes there... Maybe I'll see if I can adapt these to Evo (for the sake of preserving some semblance of compatibility between branches). Of course, there's a lot of platform details, so not everything may be feasible to implement perfectly.
PS: I tried emailing your new address, but I never got a reply... Besides communication over email, how would I go about getting in touch with active LuaSTG development? (I've seen progress in areas such as Editor Sharp v2 and THlib aex+, but this is lost to the Western side of the LuaSTG community-- I'd love to see the two halves come closer together.)

PS: I tried emailing your new address, but I never got a reply...

抱歉，我今天才回复你的邮件。我几乎每天都会查看GitHub，但查看电子邮件的次数一个月不超过10次。
DeepL ZH/EN:
Sorry I didn't respond to your email until today. I browse GitHub almost every day, but read emails no more than 10 times per month.

Alright, I sent you a reply. Thanks
DeepL:
好的，我给你发了回复。谢谢


Run the pa11y tests on stage deployments

We should run pa11y tests alongside the e2e tests, and have them block deployments – this would prevent accessibility issues reaching the live site.

Sometimes pa11y errors occur for reasons outside of code changes, so it shouldn't prevent deployments. We've not had anything really bad happen so far and Natalie looks at pa11y every day so anything gets flagged quite quickly and gets addressed if a priority. So I think we can close this.


Perpetual 401(Unauthorized) after running fine for period of time

I have built a conference scheduling app that uses ews-java-api to browse and book meetings.
The app will run fine until a certain number of requests and mid-stream the Exchange EWS service will return only 401(Unauthorized). The only way to reset this state is to start the application again.
No ExchangeService instances are cached, that is, each request stream creates a new instance of ExchangeService. The request stream is basically fetching calendar items by impersonating the application user. I get the same behavior with both the Sept 2015 release and latest bits from the head.
Any ideas would be appreciated.
Monte
code to create a service instance for an impersonated request:
    // Create the EWS service instance.
    ExchangeService svc = new ExchangeService( ExchangeVersion.Exchange2010_SP2 /*server is actually Ex2013*/ );
    svc.setUrl( exchangeewsuri );
    svc.setCredentials( new WebCredentials( Property.getEwsUser(), Property.getEwsPassword() ) );

    // We use the context user to define what user to impersonate.
    String impersonatedaddress = contextusermailbox;

    // Impersonate the context user.
    svc.setImpersonatedUserId( new ImpersonatedUserId( ConnectingIdType.SmtpAddress, impersonatedaddress ) );

    if ( Property.getEwsTraceEnabled() )
    {
      svc.setTraceEnabled(true);
      svc.setTraceFlags( EnumSet.allOf(TraceFlags.class) );
      svc.setTraceListener( new ITraceListener()
      {
        public void trace(String traceType, String traceMessage)
        {
          logger.debug( "Type:" + traceType + " Message:" + traceMessage );
        }
      } );
    }

    return svc;

It's worth noting that I am parallelizing requests across a thread pool for performance reasons.

I believe this is a result of throttling policies being applied on the Exchange server. I am investigating this further by changing or lifting those values for validation purposes.
Now, if this is so, I would suggest this response to be a failing of either the EWS client (my guess is the .NET version as well), or the EWS soap service. That is, I do not believe it to be appropriate to respond with a 401(Unauthorized) since the response has absolutely nothing to do with authentication. Some might think that the intent could be to be evasive for security purposes, but I think such evasiveness is secondary to the http model itself.
Given such a condition, there are other (appropriate) responses such as 403 Forbidden, or even 418 I'm a teapot =) is more suitable than 401(Unauthorized).

Throttling on the exchange side will never result in a 401.   Throttling will only result in either a 500 with a SOAP fault or a 503 ServerBusy.
From: montehansen<EMAIL_ADDRESS>Sent: Tuesday, September 20, 2016 10:19 AM
To: OfficeDev/ews-java-api<EMAIL_ADDRESS>Subject: Re: [OfficeDev/ews-java-api] Perpetual 401(Unauthorized) after running fine for period of time (#560)
I believe this is a result of throttling policies being applied on the Exchange server. I am investigating this further by changing or lifting those values for validation purposes.
Now, if this is so, I would suggest this response to be a failing of either the EWS client (my guess is the .NET version as well), or the EWS soap service. That is, I do not believe it to be appropriate to respond with a 401(Unauthorized) since the response has absolutely nothing to do with authentication. Some might think that the intent could be to be evasive for security purposes, but I think such evasiveness is secondary to the http model itself.
Given such a condition, there are other (appropriate) responses such as 403 Forbidden, or even 418 I'm a teapot =) is more suitable than 401(Unauthorized).
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOfficeDev%2Fews-java-api%2Fissues%2F560%23issuecomment-248369219&data=02|01|davster%40exchange.microsoft.com|4e508266df094b9a2e3c08d3e17a261e|72f988bf86f141af91ab2d7cd011db47|1|0|636099887151353311&sdata=c63vjeBR%2B7YrU1eUZ0XBwd14g5AtuF%2FImUoXxIPFhNg%3D, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAILDSh-phayiXU5HSFhbvEnYt-VffZsOks5qsBVngaJpZM4J_-3-&data=02|01|davster%40exchange.microsoft.com|4e508266df094b9a2e3c08d3e17a261e|72f988bf86f141af91ab2d7cd011db47|1|0|636099887151353311&sdata=a%2BcCe5B3ULmtFtiqpsgXqwwvhLMQoChM%2BoXiJ7uiDvE%3D.

Thanks Dave.
I am attempting to prove or disprove that theory. If not a result of throttling, I would love any thoughts from any in the know. The issue can manifest following a stream of successful requests. I have stepped the java-ews-api source and it is in fact receiving this 401 response. Same result with or without pre-authenticate.

I wrote the throttling code in Exchange ☺  Aside from that, 401s can happen for a variety of reasons.  Are you calling against O365 or on-prem?
From: montehansen<EMAIL_ADDRESS>Sent: Tuesday, September 20, 2016 1:07 PM
To: OfficeDev/ews-java-api<EMAIL_ADDRESS>Cc: David Sterling (EXCHANGE<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [OfficeDev/ews-java-api] Perpetual 401(Unauthorized) after running fine for period of time (#560)
Thanks Dave.
I am attempting to prove or disprove that theory. If not a result of throttling, I would love any thoughts from any in the know. The issue can manifest following a stream of successful requests. I have stepped the java-ews-api source and it is in fact receiving this 401 response. Same result with or without pre-authenticate.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOfficeDev%2Fews-java-api%2Fissues%2F560%23issuecomment-248418395&data=02|01|davster%40exchange.microsoft.com|bf28bbc9014c45b04ca908d3e1919fae|72f988bf86f141af91ab2d7cd011db47|1|0|636099987966803352&sdata=H6ZAa5Cz1k%2Bu%2BGpxMvdE919%2FVr14gEMMeTqJcwc3Bns%3D, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAILDShxi6BzFWFYKie9Pa0SrQ3DQqjOpks5qsDzJgaJpZM4J_-3-&data=02|01|davster%40exchange.microsoft.com|bf28bbc9014c45b04ca908d3e1919fae|72f988bf86f141af91ab2d7cd011db47|1|0|636099987966803352&sdata=8IuEYOFk8%2FUnQ1KP7w%2BxTaBebkMfruVQZOoTJt72bT4%3D.

Thanks, Dave. I'd like to buy you a beer then =)
I am calling that via on-prem Ex2013. The extent of the questions being asked of Exchange are generally to acquire appointments for a date range (such as a work week) for a group of users, and the conference room. These requests are spread across a thread pool (the attendee questions are impersonated).
Monte

Can you get access to the protocol logs on the on-prem server?  Even better, the IIS logs.  The 401 will often have a subcode and win32 status code that gives further info about why the auth failed.  I assume Kerberos/NTLM auth?
From: montehansen<EMAIL_ADDRESS>Sent: Tuesday, September 20, 2016 1:28 PM
To: OfficeDev/ews-java-api<EMAIL_ADDRESS>Cc: David Sterling (EXCHANGE<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [OfficeDev/ews-java-api] Perpetual 401(Unauthorized) after running fine for period of time (#560)
Thanks, Dave. I'd like to buy you a beer then =)
I am calling that via on-prem Ex2013. The extent of the questions being asked of Exchange are generally to acquire appointments for a date range (such as a work week) for a group of users, and the conference room. These requests are spread across a thread pool (the attendee questions are impersonated).
Monte
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOfficeDev%2Fews-java-api%2Fissues%2F560%23issuecomment-248423762&data=02|01|davster%40exchange.microsoft.com|56c403d44bf2441115c708d3e1948fad|72f988bf86f141af91ab2d7cd011db47|1|0|636100000586266006&sdata=vFMj%2FelIli2t9dAUJpx5hH4oZ5dJbWkXI%2F5zP27W6H4%3D, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAILDSvyM6Vi2I5tyDrZGjpQFv_dOcCYaks5qsEG3gaJpZM4J_-3-&data=02|01|davster%40exchange.microsoft.com|56c403d44bf2441115c708d3e1948fad|72f988bf86f141af91ab2d7cd011db47|1|0|636100000586266006&sdata=FoD3NWz88u8Ga6hWyKK3JWAmgza4AFUr5wNZLtQuUig%3D.

NTLM. Working on those logs...

I managed to get my hands on some IIS logs that are in the format of HttpProxy. Fortunately, the java EWS client uses a unique user-agent so I was able to spot the http requests, and sure enough it reports some of them as 401 Unauthenticated. Not sure what to make of this because I could reproduce+step on the client and all requests appear authenticated (albeit impersonated). I am attaching an excel export showing some of the traffic. Unfortunately, HttpProxy doesnt include the soap envelope so kinda blind there.
My Exchange admin days are mui rusty and not sure what I can do on the server side to better correlate the client requests.
Thanks so much for your insight.
ExchangeServicesClient.xlsx

Those look like Exchange CAFÉ logs (from v15\logging\httpproxy…) rather than IIS logs.  If you find one of the 401s from that log, it will show you the server it tried to proxy to.  You can then look in the iisLogs folder on that dest server to find the corresponding entries.  Can probably find it roughly by datetime.
From: Monte Hansen<EMAIL_ADDRESS>Sent: Wednesday, September 21, 2016 10:12 AM
To: OfficeDev/ews-java-api<EMAIL_ADDRESS>Cc: David Sterling (EXCHANGE<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [OfficeDev/ews-java-api] Perpetual 401(Unauthorized) after running fine for period of time (#560)
I managed to get my hands on some IIS logs that are in the format of HttpProxy. Fortunately, the java EWS client uses a unique user-agent so I was able to spot the http requests, and sure enough it reports some of them as 401 Unauthenticated. Not sure what to make of this because I could reproduce+step on the client and all requests appear authenticated (albeit impersonated). I am attaching an excel export showing some of the traffic. Unfortunately, HttpProxy doesnt include the soap envelope so kinda blind there.
My Exchange admin days are mui rusty and not sure what I can do on the server side to better correlate the client requests.
Thanks so much for your insight.
ExchangeServicesClient.xlsxhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOfficeDev%2Fews-java-api%2Ffiles%2F485617%2FExchangeServicesClient.xlsx&data=02|01|davster%40exchange.microsoft.com|593344fd13f54c7bcc1608d3e24269a4|72f988bf86f141af91ab2d7cd011db47|1|1|636100747285090784&sdata=sl9BYIIuLkbercEISI1wP3MV%2FZ%2F5L2lAEhXIn6x3Qbs%3D
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FOfficeDev%2Fews-java-api%2Fissues%2F560%23issuecomment-248679096&data=02|01|davster%40exchange.microsoft.com|593344fd13f54c7bcc1608d3e24269a4|72f988bf86f141af91ab2d7cd011db47|1|0|636100747285090784&sdata=eYHGOuhlc%2BToa4LA3tpxH%2BCtNO2lyWQgAztTK0raVDs%3D, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAILDStwWlYSeqYn3hXrILT5PkoOdVjp5ks5qsWVjgaJpZM4J_-3-&data=02|01|davster%40exchange.microsoft.com|593344fd13f54c7bcc1608d3e24269a4|72f988bf86f141af91ab2d7cd011db47|1|0|636100747285090784&sdata=U1vXR7LFV7CZl0sXmNrvyN0eF5IQUT3nkGUns6gkwN0%3D.

Hi Monte..
We are facing similar issue in spring boot openshift architecture.we use ews-java-api 2.1 version.
Can you please help me with ..which version it's resolved ur issue?

Those look like Exchange CAFÉ logs (from v15\logging\httpproxy…) rather than IIS logs. If you find one of the 401s from that log, it will show you the server it tried to proxy to. You can then look in the iisLogs folder on that dest server to find the corresponding entries. Can probably find it roughly by datetime.
From: Monte Hansen<EMAIL_ADDRESS>Sent: Wednesday, September 21, 2016 10:12 AM To: OfficeDev/ews-java-api<EMAIL_ADDRESS>Cc: David Sterling (EXCHANGE<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Subject: Re: [OfficeDev/ews-java-api] Perpetual 401(Unauthorized) after running fine for period of time (#560)
I managed to get my hands on some IIS logs that are in the format of HttpProxy. Fortunately, the java EWS client uses a unique user-agent so I was able to spot the http requests, and sure enough it reports some of them as 401 Unauthenticated. Not sure what to make of this because I could reproduce+step on the client and all requests appear authenticated (albeit impersonated). I am attaching an excel export showing some of the traffic. Unfortunately, HttpProxy doesnt include the soap envelope so kinda blind there.
My Exchange admin days are mui rusty and not sure what I can do on the server side to better correlate the client requests.
Thanks so much for your insight.
ExchangeServicesClient.xlsxhttps://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fOfficeDev%2fews-java-api%2ffiles%2f485617%2fExchangeServicesClient.xlsx&data=02%7c01%7cdavster%40exchange.microsoft.com%7c593344fd13f54c7bcc1608d3e24269a4%7c72f988bf86f141af91ab2d7cd011db47%7c1%7c1%7c636100747285090784&sdata=sl9BYIIuLkbercEISI1wP3MV%2fZ%2f5L2lAEhXIn6x3Qbs%3d
— You are receiving this because you commented. Reply to this email directly, view it on GitHubhttps://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fOfficeDev%2fews-java-api%2fissues%2f560%23issuecomment-248679096&data=02%7c01%7cdavster%40exchange.microsoft.com%7c593344fd13f54c7bcc1608d3e24269a4%7c72f988bf86f141af91ab2d7cd011db47%7c1%7c0%7c636100747285090784&sdata=eYHGOuhlc%2bToa4LA3tpxH%2bCtNO2lyWQgAztTK0raVDs%3d, or mute the threadhttps://na01.safelinks.protection.outlook.com/?url=https%3a%2f%2fgithub.com%2fnotifications%2funsubscribe-auth%2fAILDStwWlYSeqYn3hXrILT5PkoOdVjp5ks5qsWVjgaJpZM4J_-3-&data=02%7c01%7cdavster%40exchange.microsoft.com%7c593344fd13f54c7bcc1608d3e24269a4%7c72f988bf86f141af91ab2d7cd011db47%7c1%7c0%7c636100747285090784&sdata=U1vXR7LFV7CZl0sXmNrvyN0eF5IQUT3nkGUns6gkwN0%3d.

Hi Davster..
We user inbuilt tomcat with springboot..Where i can get the traffic logs?


recent senders: Use message ids instead of timestamps for sorting.

Fixes: 5956.

Merged, after fixing the commit message to actually close #5956 and explain why this change is desirable.  Please be more careful when writing commit messages in the future.  Thanks @shubhamdhama!


VCF loaded but not the corresponding VCF.gz (without VCF.gz.tbi)

Dear IGV Team,
I use dceoy/igv-webapp docker image to load my data through https://github.com/igvteam/igv.js-flask.git (docker service named "DAS")
I perfectly load BAM, CRAM and BED files.
However, I've some problems to load VCF files.
I used multiples VCF files (*vcf and *vcf.gz), all passing BCFTOOLS "validation" (no error when "view" and "sort")
They all work using Tracks > Local Files...
When I used these files through the "DAS" service (and a json file):

all *vcf files are correctly loaded,
all corresponding *vcf.gz with associated *vcf.gz.tbi are correctly loaded,
but corresponding *vcf.gz without associated *vcf.gz.tbi are not.

Here are few examples:
ACROMETRIX.final.vcf OK
ACROMETRIX.final2.vcf OK
ACROMETRIX.final3.vcf OK
ACROMETRIX.final4.vcf OK
ACROMETRIX.final.vcf.gz KO
ACROMETRIX.final2.vcf.gz KO
ACROMETRIX.final3.vcf.gz KO
ACROMETRIX.final4.vcf.gz OK
examples.tar.gz
Here is a screenshoot of IGV-web:

All *vcf are loaded. Only 1 *vcf.gz is correctly loaded (ACROMETRIX.final4.vcf.gz), because of some removed annotations (INFO and FORMAT). The only difference between ACROMETRIX.final4.vcf.gz and ACROMETRIX.final3.vcf.gz is "FORMAT/PL" annotation.
Javascript error message for ACROMETRIX.final.vcf.gz:
"Malformed VCF header line: ##INFO=<ID=PZScore-HEMATOLOGY,Number=.,Type=Integer,Description="Prioritization Score for filter 'HEMATOLOGY', depending on th" (igv.min.js:39)
As there is no error message (e.g. window message), it's dangerous to load *vcf.gz files (without associated tbi), because no variant loaded does not mean there is no variants! A Javascript message informs that "Warning: index file not specified.  The entire vcf file will be loaded." (igv.min.js:39), but it seems that it's not the case.
I'll change my code to force *vcf.gz.tbi with *vcf.gz, but it could be great to either fix or prevent loading *vcf.gz without *vcf.gz.tbi.
Best regards

I'm not following all the details here,  but its perfectly legal to load a non-indexed vcf, even if its gzipped or bgzipped.    If you are encountering an error for this case please try to provide a reproducible test case.

As I mentioned in my previous message, and in order to provide a reproducible test case, the following VCF (bgzipped) are not properly loaded through URL when I don't provide associated index (see examples.tar.gz):
ACROMETRIX.final.vcf.gz
ACROMETRIX.final2.vcf.gz
ACROMETRIX.final3.vcf.gz
I can not provide a JSON with accessible URL, because I use an internal serveur. Here is an example of (part of) JSON file:
{
 "url": "http://localhost:4201/static/data/public/repositories/Archives/SOMATIC/HEMATOLOGY/190927_M01656_0335_000000000-CLGGY/ACROMETRIX/ACROMETRIX.final2.vcf.gz",
 "indexURL": null,
 "name": "ACROMETRIX.final2.vcf.gz",
 "sourceType": "file",
 "format": "vcf",
 "order": 8,
 "height": "40",
 "type": "variant"
}

And here is the output, with regions (in red) without variants that are though present in VCF:

OK I'll look at it.  You should not provide indexURL: null, btw, that might
be an issue.   null is a value, it is not "undefined", if you wish to load
a file with index its best to explicitly indicate that with "indexed:
false",  but do not set indexURL (or any other property) to "null".
On Fri, Nov 12, 2021 at 6:02 PM antonylebechec @.***>
wrote:

As I mentioned in my previous message, and in order to provide a
reproducible test case, the following VCF (bgzipped) are not properly
loaded through URL when I don't provide associated index (see
examples.tar.gz):
ACROMETRIX.final.vcf.gz
ACROMETRIX.final2.vcf.gz
ACROMETRIX.final3.vcf.gz
I can not provide a JSON with accessible URL, because I use an internal
serveur. Here is an example of (part of) JSON file:
{
"url": "http://localhost:4201/static/data/public/repositories/Archives/SOMATIC/HEMATOLOGY/190927_M01656_0335_000000000-CLGGY/ACROMETRIX/ACROMETRIX.final2.vcf.gz",
"indexURL": null,
"name": "ACROMETRIX.final2.vcf.gz",
"sourceType": "file",
"format": "vcf",
"order": 8,
"height": "40",
"type": "variant"
}
And here is the output, with regions (in red) without variants that are
though present in VCF:
[image: Capture d’écran 2021-11-13 à 00 40 39 2]
https://user-images.githubusercontent.com/40463532/141601681-4884781b-8f6a-4e1e-82b4-833808ea6982.png
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/igvteam/igv-webapp/issues/221#issuecomment-967760614,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHD2HE2FKG55J4X4D24OMLULXBLNANCNFSM5H553SDA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I'm going to transfer this issue to igv.js, since its really not about the webapp wrapper per se.


HELP:  Unable to install ngx-popperjs since ngx-ui-tour-core is present inside project.

Hi @tonysamperi I have removed other static descriptions and sorry about that. Here is the error that I am getting, I understood from the error but since ngx-ui-tour-core is heavily used and was working with ngx-popper earlier how can we fix this? is there any alternative way to fix this instead of using ngx-tour-wizard?
Error: Unfortunately ngx-popperjs is not compatible with ngx-ui-tour-core!
We are planning to remove ngx-popper and use ngx-popperjs but getting this error.
Could you please mention reason behind it?

@pavandixit93 yes I can explain!

Hi @tonysamperi Could you please explain it? So that we will add the same inside Notes section and will try this upgrade in the future by removing ngx-ui-tour-core and add ngx-tour-wizard.


Update docfx.json

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Web-Apps-Server-loc/docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

Web-Apps-Server-loc/docfx.json
:white_check_mark:Succeeded

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:warning: Validation status: warnings

File
Status
Preview URL
Details

Web-Apps-Server-loc/deploy-office-web-apps-server.md
:warning:Warning

Details

Web-Apps-Server-loc/docfx.json
:white_check_mark:Succeeded

Web-Apps-Server-loc/deploy-office-web-apps-server.md

[Warning] Author Mike Plumley cannot be recognized in GitHub.

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

:x: Validation status: errors

File
Status
Preview URL
Details

:x:Error

Details

[Error] Cannot sync git repo to specified state. Please make sure the pull request is mergeable. Details: Git merge results in conflict, repository remote url: https://github.com/MicrosoftDocs/OfficeDocs-OfficeOnlineServer-Test-loc-pr.de-de, working directory: W:\gn1r-s, target branch: master, target branch commit: a822e9ca93fb55d571717fd9ad546d932b13b19c, source branch: 858003e36b5721bf94e28c60a30a9dcb/master, source branch commit: .

For more details, please refer to the build report.
Note: If you changed an existing file name or deleted a file, broken links in other files to the deleted or renamed file are listed only in the full build report.

Closing PR without merging as there are build failures


Modifying test files is not supported in Code modifier compiler plugins

Description:
We would need to introduce new APIs as modifyTestFile for code modifier compiler plugins.
Steps to reproduce:
Affected Versions:
OS, DB, other environment details and versions:
Related Issues (optional):

Suggested Labels (optional):

Suggested Assignees (optional):

The method name modifyTestFile doesn't make sense to me. My suggestion is modifyTestSourceFile and that goes well with the existing method modifySourceFIle.
In the future, we may have to add methods to modify resources files and method names can be modifyResourceFile and modifyTestResourceFile

According to the above comment,  added modifyTestFile method should be removed, and modifying test files support should be added to the same modifySourceFIle method.

Decided to keep the modifyTestFile after renaming it to modifyTestSourceFile.


Rolling update from "CeresDB" binaries and libraries to the new "HoraeDB" ones

We should discuss about how the existing CeresDB provisions and libraries can be rolling updated to the new "HoraeDB" ones.
For example, we may duplicate the service CeresmetaRpcService with HoraeMetaRpcService. Release a version that contains both of these two endpoint, and a new one that only the HoraeMetaRpcService exists.

被京东收购了？

@chunshao90 @jiacai2050 @tanruixiang do we have a resolution now? Maybe we can close this issue with the resolution. Or we'll have a plan to finish it.

@chunshao90 @jiacai2050 @tanruixiang do we have a resolution now? Maybe we can close this issue with the resolution. Or we'll have a plan to finish it.

I've been dealing with it recently and expect it to be resolved within a week.

This https://github.com/apache/incubator-horaedb/pull/1455 list what are required to upgrade to latest main branch.
During the update process, there will be errors between horaedb-server and horaemeta, but should be fine when all servers updated.


add scale to header so it is visible in scroll

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Ex. I'm always frustrated when [...]
Describe the solution you'd like
A clear and concise description of what you want to happen.
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

Have this sorta working locally.
Adding axis to bottom of svg_header svg is easy.
Getting it to appear with an appropriate number of ticks and in the right place no matter the number of curves or explicitly set size of header is taking more time.


Upload current version to PyPI

Hi. Is it possible to update the version of this project to include the most recent changes? I want to use it on a project, but the current version (2.0.2) does not include simplejwt integration, which I need. Thanks.

Hi Pedro.
Yes, I'll update the version soon, just want to do some final improvements. It will be published in next couple of days.

@phlucas96
Deployed to pypi: v2.1.0.


CNV-49305: fix for virt perspective

From virt perspective, when the user go to the RoutePage, the perspective change to admin. We don't want that behavior

/lgtm

/cherry-pick release-4.17


Is it possible to change the base URL?

Is there support for running requestbin on a mapped url (e.g. mapped via a reverse proxy from http://example.com/requestbin/ to the docker container's /)? It doesn't seem like it, but I just wanted to make sure I didn't miss something super obvious.
Thank you!

Yeah - I did try it and the front page (at least) does not render correctly. All of the self-referencing links for stylesheets and script content appear to be defined absolutely (so they're trying to load /blah.css when you're seeing it as /httpbin/blah.css). Actually, come to think of it, that's almost all swagger content. I bet the individual endpoints probably work fine. So, it may not be that it's entirely broken.

For S

A little bit, I think? It seems as though swagger does infer some settings based upon how it's called (you call using https, it responds accordingly). It doesn't seem like that works for the base path, however. Perhaps this would need to be changed to make it work "perfectly" when proxied in this way. I haven't pulled it to try to rebuild it myself to test that, but I'm guessing an environment variable tied to that would probably do the job.
Totally could be wrong, though - still noodling it. And this is also really not a big deal. The testing endpoints still work and it's not as if this is something everyone wants or needs to be able to do. It's helpful to me as a testing service to make sure ingress is working properly in a kubernetes environment and you don't need the UI to look perfect in order to use it for that.


Test observed light curves against references

@jchiang87 If you can take @rbiswas4 code and use it to make Monitor plots of an observed light curve with reference light curve overlaid, you win the prize of being able to close this issue! You may need to upgrade the Monitor's visualization capabilities to do this - you can issue that too, and hence double the size of your prize! :-)

@rbiswas4 What's the relationship between the idValue in the TwinkSN table and the instance catalog sourceID from the phosim input files?  I had thought they were the same, but the idValue examples in your notebook have too few digits (and don't appear in the Run1.1 instance catalogs) and the sourceId for an obvious SN in the phosim data isn't found by your RefLightCurves code.  I recall there was some discussion regarding generating unique sourceIDs for phosim, but I thought that only pertained to the lensed AGNs.

@jchiang87 Thanks! That was indeed a lack of thought on my part. I will fix this before issueing the PR.

@jchiang87 Could you please give me a couple of IDs taken from the Instance Catalog, so that I can run some tests? Thanks

Hi @rbiswas4,  I think these should be good to try:
6144007055260714,<PHONE_NUMBER>480362,<PHONE_NUMBER>753642,<PHONE_NUMBER>279914,<PHONE_NUMBER>709290

@jchiang87  Thanks! Those were useful to set up an example ipython notebook.

Here are some plots comparing the reference light curves (in blue) and the forced source light curves (in red):

I found the sourceId's (the term used in the PhoSim centroid files for the instance catalog object ids) by looking at the light curves inferred from the centroid files and picking out the ones that look like SNs.   The objectIds for the forced source fluxes (red points) were found by positional coincidence with the instance catalog coordinates.  I'd say all but objectId 56569 (middle bottom) are correct associations.  Some of the light curves match pretty well, others not so much. Given that these are fairly bright, I would have expected they all would match more consistently than this.

@jchiang87
Are there error bars that I am not able to see because the errors are too small? Are these coadds? The blue light curves look rather smooth!

Yep, the error bars are being plotted, and for the red points (which I assume you meant), the errors are from doing the forced photometry on the calexp images (if I understand things correctly).  I even made the points using fmt='.' so as not to obscure the error bars.  Here is the script that produced those plots for reference.

Hmm. Actually I meant both, and particularly the blue points (because I am in  a better position to interpret/change/compare with other ideas etc.).

Please have a look at the compare_lcs.py script and make sure I'm unpacking the errors for the reference light curves correctly.  It seems straight-forward.

@jchiang87 I just looked at your script, and did not see anything wrong in the script. And these are not coadds either. I realized, that I was suspecting them to be coadds because (a) they looked smooth and (b) because there were not the usual number of points I am used to seeing in DDF fields. But I just remembered that (b) is not valid because Twinkles cadence is not DDF cadence.
So, perhaps these are simply super bright objects and therefore smooth ... So, I checked, and indeed these are intrinsically very bright objects and are at low redshifts < 0.1. So, maybe they should be smooth.

Here are plots showing the comparison for all six bands for a handful of the brighter SNe:


netns: allow to listen to events for multiple paths

This allows to add /var/run/docker/netns

rerun tests


route can nuke root

As a note, with the following routes, I get a 404 for "/"
get "/" do |env|
end

get "somewhere" do |env|
end

My hunch is the last one should be disallowed or something. Cheers!

Yeah, this is a bug!


Feature: Change repository name

Describe your feature request or suggestion in detail
It should not pass the compilation tests, because the name does not respect the format it must have in the emulator API.
Describe a possible solution to your feature or suggestion in detail
The repository should be called: mod-better-item-reloading, in the same way as it is currently found in the AzerothCore community.
Additional context
No response

Updated the name. Hope that was right? :)

Updated the name. Hope that was right? :)

It looks like it is. That would be enough. Thank you.


Projects should be required to have a unique name

Currently it is possible to have multiple projects with exactly the same name, this makes searching and keeping track of projects difficult.

Some thoughts:

We need a plan for how to deal with pre-existing collisions.
Ideally it should be enforced by the database. That will help in avoiding a TOCTOU bug.

 reco v0.7.0

Here's some words for the error message: https://docs.google.com/document/d/1_GO6XnwR4rcwd2YFRUHW8SWvW5sFGXiWtFi7a0Abhtg/edit#heading=h.e1kl1dljw39o


[Feature]: Tinted background

Is there an existing issue for this?

[X] I have searched the existing issues

Describe your idea or feature request
I think it would be cool to have an option to color/tint the blurred background of vscode to allow for more customization, this color setting could come from the theme iteself or the user
Anything else?
I photoshopped a screenshot to serve as an example:
Original Theme (Colors by One Dark Pro)

Simulated custom color

Some sort of theme customization would certainly be nice to have, though if you'd rather not wait, you can also use the custom CSS import functionality to add a tint yourself. You can just copy the theme file CSS from this folder and replace all "transparent" colors with whichever color you want + an alpha value, for example by adding background: #ff000080 where 80 is 50% opacity in hex form.


Document how to use Heroku + RDS

Using the deploy to heroku button on the repo
Describe available options
Show the anatomy of a postgresql connection string
Mention RDS IP permissions
Keeping the DB geographically near the heroku dyno (virginia region)

I'll close citing the same reason as in https://github.com/PostgREST/postgrest-docs/issues/3#issuecomment-521739306.
Priority should be core functionality and ppl have been managing.


[BUG]: Module not found in model structural comparison

In model comparison operator, use the notebook-tab to compare the models structurally, we get the follow error about missing modules.

This is likely due to conditional packages shifting around in MIRA and we need to update the install commands.


.NET manual: independent and new root docs

This fixes https://github.com/open-telemetry/opentelemetry.io/issues/1073 and brings the manual instrumentation bit up to par with JS.

@reyang Sorry for not pinging, thought I had. Can you take another look to see if the changes are suitable?

@reyang any chance to take another look? Looking to get through our open PRs this week.


[Bug]: Error: net::ERR_CONNECTION_REFUSED

Bug description
Hey i am facing an issue while trying to connect to localhost or<IP_ADDRESS> when trying to run tests with mocha and puppetter. ( iam using vs code on windows 10, no issues with linux virtual machine).
before(async () => { /* before hook for mocha testing */
page = await browser.newPage();
await page.waitForTimeout(5000);
await page.goto(https://<IP_ADDRESS>:${config.port}/app.html);
await page.setViewport( { width: 1920, height: 1080} );
});
Puppeteer version
11
Node.js version
12.14.1
npm version
8.1.3
What operating system are you seeing the problem on?
Windows
Relevant log output
Error: net::ERR_CONNECTION_REFUSED at https://<IP_ADDRESS>:3030/app.html
      at navigate (node_modules\puppeteer\lib\cjs\puppeteer\common\FrameManager.js:155:23)
      at runNextTicks (internal/process/task_queues.js:59:5)
      at listOnTimeout (internal/timers.js:501:9)
      at processTimers (internal/timers.js:475:7)
      at async FrameManager.navigateFrame (node_modules\puppeteer\lib\cjs\puppeteer\common\FrameManager.js:130:21)
      at async Frame.goto (node_modules\puppeteer\lib\cjs\puppeteer\common\FrameManager.js:500:16)
      at async Page.goto (node_modules\puppeteer\lib\cjs\puppeteer\common\Page.js:1167:16)
      at async Context.<anonymous> (test\frontend\test\index.test.js:68:7)

fixed?

As part of the puppeteer tests, i added a server for client tests: (not the solution but what i used before and caused the error)
const server_opt = {
      cwd: './',
      env: process.env,
};
server_process = await spawn('npm', ['run',  "test-server"], server_opt);

The fix was to add to the server_opt the "port" property and the server port number. for me it was "port: 3010" but your port maybe different.

im also getting this error

Has anyone found a solution for this?
I have the node js app runs with docker

Localhost runs just fine
But on Gitlab CI, this error occurred


Add @AliNurisiahsiahi as a collaborator to the new repo

Ali accepted the invitation and is now added as a collaborator to the new repo


Reschedule snap refresh

Currently, default snap refresh schedule is 00:00~24:00/4 (4 times/day). Reschedule it to atleast once per month and at midnight.

what is the past impacts of snap refresh ?


Make CatchClause scope optional

CatchClause does not need a scope if there's no param e.g. try {} catch {}. Add back #[scope(if(self.param.is_some()))].
As discussed in https://github.com/oxc-project/oxc/pull/4192#pullrequestreview-2171374436, there's an argument for making all scopes unconditional. But in my opinion, either way the most important thing is to be consistent, so scopes-related code is easier to reason about.
At present, our policy is not to create a scope if none is needed (because it has no bindings). So we should keep to that policy for CatchClause. If we want to change the policy, we can do that, but we should do it consistently for all scopes.

Fixed in #4346.


[WIP] Refactor/project controller

[ ] Make projectController a singleton instead of three simultaneous instances accidentally working
[ ] Review with fresh eyes
[ ] Verify that project list still works in the empty-state

Refactoring the AppDelegate and moving most of the stuff out to a projectController.

Couldn't find a way to do IB-compatible singleton. Making a regular singleton and piping through VCs for now.


Nx Jest Playwright reporters ?

Wondering how to configure reporters for nx jest playwright?

Hello, I must say I have never played with that. I would imagine it would be similar to setting it up for jest.

Since there is no activity I am closing issue. Please feel free to reopen.


Add a "recenty used input" to user inputs for tasks.

Rationale:
The "Task: Run Task" picker puts the most recently used task as the first one in the list (with other recently used tasks), which makes it easy to re-run the same task without typing.
The same behavior is not present for the input pickers (both "pickString" and "promptString" pickers), which makes it harder to re-run the same task if the arguments were not the default ones.
Details:
Consider the following tasks.json file:
{
	"version": "2.0.0",
	"tasks": [
		{
			"label": "echo free",
			"type": "shell",
			"command": "echo ${input:any}",
			"problemMatcher": []
		},
		{
			"label": "echo list",
			"type": "shell",
			"command": "echo ${input:list}",
			"problemMatcher": []
		}
	],
	"inputs": [
		{
			"id": "list",
			"description": "arguments in a list",
			"default": "a",
			"type": "pickString",
			"options": [ "a", "b", "c" ]
		},
		{
			"id": "any",
			"description": "any arg",
			"default": "",
			"type": "promptString"
		}
	]
}

If my development workflow requires me to run "echo list" with argument "c" frequently (i.e. building a specific module in a big project), I can quickly find the right task (it is likely at the top of the recently used tasks inside the Run Task picker), but I will still have to lookup or type the argument (and in my real-life use case, the argument is not a single letter, and the list has ~150 elements). Having a "recenty used input" list would be helpful for this.
The same goes for a "echo free"-like task (I have this case passing custom arguments to a build system script, as I would do in a shell, but with a problemMatcher parsing the output), but as the arguments are not selected from a list, the number of "recently used inputs" would probably have to be limited to a sane level.

There's a Rerun Last Task command, where if you set the task's "runOptions": { "reevaluateOnRerun": false} you'll be able to run the last task with the same input. I know that's not quite what you're asking for here, but it might help for now.

I also needed that functionality, for now the reevaluateOnRerun setting is fine, thanks !

Related https://github.com/microsoft/vscode/issues/72944

Here it is May 2020 and this feature is still not available? I have a use-case which needs the selection of the user to be remembered. In our case we need to get the branch name to update from git, but each user of the tasks.json may be working on other branches. We should be able to remember the last value used to avoid having the user re-select the branch.

@alexr00 with input variables supported in debug configurations, there is no "rerun last debug" that remembers it.
A common use case is manually specifying which test I want to run in golang, but I have to type it every single time instead of being able to "rerun last debug"

If we are entering passwords etc, maybe they could be remembered until next time you start the editor? Unless there's a way to load them from a separate file that doesn't get checked into source control.

+1 for this option.  I love having my launch files be configurable in different environments but man is it a pain to re-paste in paths and what not every single time.  At least a session-based cache would be great.

I apologize for not following up on this feature request after satisfying my own related needs.
I have found that the "Memento Inputs" (spadin.memento-inputs) extension fills my related use-case needs quite well.

@bryceschober wow that's exactly what I wanted.  Thanks a ton for the link!

+1 even just remembering the last input per task would be a great help!

Related: https://github.com/microsoft/vscode/issues/131128

After investigation, I don't think this is something we need to build into core given @alexr00 's suggestion fixes this issue for running tasks.
"runOptions": { "reevaluateOnRerun": false}

This is separate from the debug issue mentioned above. As for that, doesn't workbench.action.debug.restart work?

For the use case mentioned at the start of this issue, creating a task specifically for the command you want to run would avoid having to choose from a long list of inputs.


".import" on Windows is not working

I am trying to debug code with .import using relative path on Windows, which gives the error below:

Error: ENOENT: no such file or directory, open '/D:/0000/CS61C/CS61C-fa20/proj2/unittests/assembly/TestAbs_test_minus_one.s'

perhaps the '/' prefix is causing the problem?
the code is from cs61c proj2, here is an example

i meet the same problem

Thank you. We will look into it!


lua_newthread can't work

I want to run script in independent stack but have some shared global things, so use lua_newthread to create one, but sol::state_view seems only throw things on main lua state. Isn't it the right way to do it?
My sol version only use c++14.
#include
#include
#include "sol.hpp"
int main(int, char*[]) {
sol::state lua;
lua.open_libraries();
auto L = lua_newthread(lua.lua_state());
 sol::state_view runner_thread_state = L; // runner_thread.state();
runner_thread_state.do_string("function fun() print('fuck') end");
runner_thread_state["fun"]();
try
{
	lua["fun"]();
}
catch (std::exception const& e)
{
	std::cerr << e.what() << std::endl;
}
return 0;

}

lua_newthread pushes a new thread onto the stack. If you want something that is managed, you should be using sol::thread, and its creation utility sol::thread::create. Then, you can get the state for that thread with runner_thread.state();
Finally, Lua threads do not guarantee atomicity. Nor does it guarantee that the operations won't hit a common place in Lua -- e.g., the global table. You can of course get away with maybe having a separate stack, but unless you understand the stack and how to use it you'll likely do something wrong. I wouldn't recommend it, to be perfectly honest. What Lua considers a "thread" and what C++ considers a "thread", and what the two consider "thread local", don't seem to be the same thing.


[RFC] Combined Attestation for CoCo

Motivation
Currently, some workloads in TVM, such as AI, rely on external devices for acceleration. In these scenarios, the Device TEE should also be included in the TCB, for the confidentiality of data. This means that the Relying Party not only needs to perform attestation on TVM, but also needs to perform attestation on the Confidential Device. However, the current confidential containers (CoCo) stack, especially CoCo AA and CoCo AS, lack support for device attestation. Specifically, we are missing the following parts:

The current Attestation Agent only provides attestation for CPU TEE and does not provide reliability information for the external Device TEE of TVM to the relying party.
The current Attestation Service implementation does not support the combined verification of CPU TEE + Device TEE.

It is worth mentioning that there is currently a discussion in the community about TDM, which attempts to address the attestation for Device TEE in TVM. Combined Attestation is a related but different topic with different purposes. Here is also a slide on this proposal.
Thanks to @jingyao-zhang @jialez0 @Xynnn007 @jiazhang0 for their suggestions for this proposal.
Goals

Add Device TEE Attestation to the existing TVM Attestation process so that the relying party can verify the Device TEE attached to the TVM.
Define a Combined Attestation Evidence format so that we can bind the Device TEE info (e.g. Attestation Results or Evidence), and TVM Evidence together in a cryptographically protected form.
Define a unified format for Attestation Results that can be accepted by components between TDM and AA.
Ensure compatibility with the existing CoCo KBS protocol (RCAR protocol).

Design

The following is an abstract of the basic workflow of Combined Attestation. The verification materials from CPU TEE and Device TEE are combined to obtain Combined Attestation Evidence, which is used to request an Attestation Token from the Attestation Service.

For option 1, one approach is to interact with TDM, which will provide Device Attestation Results. The architecture is following:

The entire process can be seen as Local/Remote Device Attestation + Remote TVM Attestation.

Steps 1-4 are Local/Remote Device Attestation, which is implemented by TDM. In the early stages of TVM, the TDM daemon performs Local Attestation/Remote Attestation on the Device TEE separately and obtains Attestation Results.
Steps 5-11 are based on Remote TVM Attestation. The changes made to achieve Combined Attestation mainly occur in three parts: steps 5, 8, and 10. In step 8, the Attestation Agent combines the Device Attestation Results (obtained from step 5) with the TVM Evidence (obtained from step 7) to form Combined Attestation Evidence.

Option 2 is a simpler approach. Compared to option 1, this approach allows the Attestation Agent to directly obtain Device Evidence from the guest kernel without relying on TDM to provide Attestation Results. Then, the Attestation Agent combines the Device Evidence with the TVM Evidence to form Combined Attestation Evidence. This approach is suitable for the case where remote Relying Party wants to verify the Device Evidence themselves.

Design details
In this section, we will introduce some details of the Proposal. Note these are just reference designs, and suggestions are welcome.
The struct of Combined Attestation Evidence
According to the current RCAR protocol design, the "tee-evidence" field in the Attestation request represents Attestation Evidence of TVM, and its format is specified by Attestation Service.
{
    /*
     * A JWK-formatted public key, generated by the KBC running in the HW-TEE.
     * It is valid until the next time an attestation is required. Its hash must
     * be included in the HW-TEE evidence and signed by the HW-TEE hardware.
     */
    "tee-pubkey": $pubkey

    /* The attestation evidence. Its format is specified by Attestation-Service. */
    "tee-evidence": {}
}

In the current implementation, the field "tee-evidence" contains TEE evidence information. For example, for SGX ECDSA, it is:
{
    "quote": "AwACAAAAAAAIAA0Ak5pyM/ecTKmUCg2zlX8GB9zN6bMc6IYFSBc7tKKle..."
}

For TDX, it is:
{
    "cc_eventlog": "AAAAAAMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACgAAABTcGVjIElEIEV2ZW50...",
    "quote": "BAACAIEAAAAAAAAAk5pyM/ecTKmUCg2zlX8GB9CZv+wKR3qoWmBdzqvysQgA..."
}

To enhance support for Combined Attestation while keeping loose coupling with the RCAR protocol, we propose making changes only to the content of the "tee-evidence" field. The following is a tree-like design consisting of two types of structures:

“evidence” struct
{
    "evidence": {
        "tee-type": "", // The type of TEE
        "evidence": {}, // The evidence generated by Attester in AA
        "custom-claims": { // A set of key-value pair, for extra data associated with this evidence
            "nested-tee": [], // A list of information about nested TEEs
						...
        }
    }
}

Note that each element in the "nested-tee" field can be either an "evidence" struct or an "attestation-results" struct.

“attestation-results” struct
{
    "attestation-results": {
        "evaluation-report": "", // The output of policy engine, and should have the same value as the evaluation-report field in the validation token.
        "attestation-service-type": "", // The type of attestaion service for device attestation, can be "local-coco-as" or "remote-coco-as".
        "attestation-service-url": "" // (optional) The URL of the attestation service used for device attestation
    }
}

For example, here is an example of combining TDX Evidence and GPU Device Attestation Results into Combined Attestation Evidence:
{
    "evidence": { // evidence of a tdx guest
        "tee-type": "tdx",
        "evidence": { /* evidence generated by tdx Attester in Attestation Agent */},
        "custom-claims": {
            "nonce": h"ea46fa5c77f6c6a3d16d...",
            "tee-pubkey": h"609fccc4d9e9a21e58343788167a9e9c...",
            "nested-tee": [
                { // attestation result of GPU 0
                    "attestation-results": {
                        "evaluation-report": "output of policy engine",
                        "attestation-service-type": "remote-coco-as",
                        "attestation-service-url": "https://coco-as.example.com/"
                        /* ... */
                    }
                }
            ]
        }
    }
}

One of the advantage of this tree-like design is the flexibility. We can not only combine Device Attestation Results and TVM Evidence, but also combine Evidence from different TEEs(in this case is Device Evidence and TVM Evidence) in any way while still maintaining the hierarchical relationship, thus accommodating more complex scenarios. For example, a combined attestation evidence can be:

A TVM Evidence nesting any number of Device Attestation Results
A TVM Evidence nesting any number of Device Evidence
Only containing a TVM Evidence (consistent with the current CoCo TVM attestation process)
Only containing a Device Evidence (usable for Device remote attestation process in TDM)

Cryptographically protected binding between TEEs
In order to prevent attackers from forging Device TEE info by tampering with Combined Attestation Evidence (for example, by replacing the Device Attestation Results in the Combined Attestation Evidence), the binding relationship between CPU TEE and Device TEE needs to be cryptographically protected.
This is achieved through the presence of the report_data field in the outer TEE (CPU TEE) hardware evidence. In the current CoCo AA and CoCo AS, the report_data field in hardware evidence is implemented as hash(nonce | tee-pubkey). We recommend changing it to hash(custom-claims), where custom-claims represents the string of the "custom-claims" json object in the "evidence" struct.
Expanding claims generated in Attestation Service

Currently in the Attestation Service, the process of evidence verification is as follows:

Call the Verifier corresponding to the TEE Evidence.

Compare the report_data in the evidence with the report_data computed by the Attestation Service.
Verify the integrity of the evidence with the help of endorsements materials.
Parse the evidence into claims (key-value pairs derived from the fields of the evidence).

Fetch the reference value from the Reference Value Provider Service.
Invoke the policy engine with the claims, reference value, and policy as inputs, and obtain the evaluation-report (the output value of the policy engine).
Issue an Attestation Token based on the claims and evaluation-report.

To support Combined Attestation, This proposal suggests:

Expand the claims to include information from multiple TEEs.
For example, here are the claims that result from parsing the TDX evidence (the content has been simplified for illustration purposes).
{
    "ccel": {},
    "quote": {
        "header": {},
        "body": {
            "mr_config_id": "000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
            "mr_owner": "000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
            "mr_owner_config": "000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
            "mr_td": "705ee9381b8633a9fbe532b52345e8433343d2868959f57889d84ca377c395b689cac1599ccea1b7d420483a9ce5f031",
            "mrsigner_seam": "000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
            "report_data": "7c71fe2c86eff65a7cf8dbc22b3275689fd0464a267baced1bf94fc1324656aeb755da3d44d098c0c87382f3a5f85b45c8a28fee1d3bdb38342bf96671501429"
        }
    }
}

For Combined Attestation Evidence, we propose to add a field called nested-tee, which is an array where each element the claims corresponding to the Device TEE being nested. for example.
For example:
{
    "ccel": {},
    "quote": {
        "header": {},
        "body": {
            "mr_config_id": "000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
            "mr_owner": "000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
            "mr_owner_config": "000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
            "mr_td": "705ee9381b8633a9fbe532b52345e8433343d2868959f57889d84ca377c395b689cac1599ccea1b7d420483a9ce5f031",
            "mrsigner_seam": "000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000000",
            "report_data": "7c71fe2c86eff65a7cf8dbc22b3275689fd0464a267baced1bf94fc1324656aeb755da3d44d098c0c87382f3a5f85b45c8a28fee1d3bdb38342bf96671501429"
        }
    },
    "nested-tee": [
        {
            /* claims of GPU 0 */
        },
    ],
}

It is worth noting that when validating claims, the AS must validate the claims in the nested-tee field. This can be achieved by:

Adding the reference value of the nested Devices to the RVPS.
Adding a policy entry to the policy used by the policy engine to validate the hierarchical relationship between CPU TEE and device TEE.

cc @sameo @zvonkok @thomas-fossati

Hi, thanks for involving me in this conversation, I appreciate it!
Just a quick comment on the data formats for compound evidence.  I may be biased (obviously I am 😄 ), but it turns out that RATS CMWs have all you need for the encapsulation of evidence and attestation results - and more.
They are simple, explicitly typed wrappers for everything RATS that are JSON- and CBOR-friendly.  In the CoCo case, RCAR is JSON-based so you'd use a JSON array serialisation.
For example, a compound attestation with only evidence payloads (TDX quote, TDX event log, and GPU) could look like this:
{
  "tee-pubkey": "MIIBIjANBgkqh...",
  "tee-evidence": {
    "composite": [
      [
        "application/vnd.intel.tdx-quote",
        "BAACAIEAAAAAAAAAk5pyM/ecTKmUCg2zlX8GB9CZv+wKR3qoWmBdzqvysQgA...",
        4
      ],
      [
        "application/vnd.intel.tdx-eventlog",
        "AAAAAAMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACgAAABTcGVjIElEIEV2ZW50...",
        4
      ],
      [
        "application/vnd.nvidia.gpu",
        "2TslxJCFRw++zU1acyFeOQ...",
        4
      ]
    ],
    "custom-claims": {}
  }
}

4 is the "conceptual message indicator" that means "evidence".
The same compound attestation, this time with EAR attestation results for the GPU, would look like:
{
  "tee-pubkey": "MIIBIjANBgkqh...",
  "tee-evidence": {
    "compound": [
      [
        "application/vnd.intel.tdx-quote",
        "BAACAIEAAAAAAAAAk5pyM/ecTKmUCg2zlX8GB9CZv+wKR3qoWmBdzqvysQgA..."
        4,
      ],
      [
        "application/vnd.intel.tdx-eventlog",
        "AAAAAAMAAAAAAAAAAAAAAAAAAAAAAAAAAAAAACgAAABTcGVjIElEIEV2ZW50..."
        4,
      ],
      [
        "tag:github.com,2023:veraison/ear",
        "eyJhbGciOiJFUzI1NiIsInR5cCI6IkpXVCJ9..."
        8,
      ]
    ],
    "custom-claims": {}
  }
}

Hi @thomas-fossati. Sorry for my late reply!
Thank you for your comment! The RATS CMWs look great, and make for a consistent wrapper for all payloads (both evidence and proof results). I'd love to see more people's take on this.
Also, what are your thoughts on the "nested-tee" field added to the CPU TEE evidence (as runtime-data) in this proposal? It reflects the affiliation between CPU TEE and GPU TEE (which I've represented as a tree).

@fitzthum @mythi @mkulke
Hey folks! I'd be grateful if you could spare a moment to check out this proposal.
Open to any inputs from anyone. Thanks!

We recommend changing it to hash(custom-claims), where custom-claims represents the string of the "custom-claims" json object in the "evidence" struct.

since the TEE's pubkey is a key part of the protocol and must be mixed into the evidence hash(custom-claims) would not guarantee that for a TVM-only attestion? having the pubkey nested under custom-claims prop feels odd.

in the proposed schema for tee-evidence, tee-type is introduced. At the moment, in an RCAR exchange the TEE type is set as part of the Request. is there a redundancy?

in this example:
{
    "ccel": {},
    "quote": {
        "header": {},
        "body": {
            ...
        }
    },
    "nested-tee": [
        {
            /* claims of GPU 0 */
        },
    ],
}

...nested-tee would be on the same level as the TEE-specific evidence, shouldn't it be under in a custom-claims property, which is next to evidence?

@mkulke Thanks for your reply!

We recommend changing it to hash(custom-claims), where custom-claims represents the string of the "custom-claims" json object in the "evidence" struct.

since the TEE's pubkey is a key part of the protocol and must be mixed into the evidence hash(custom-claims) would not guarantee that for a TVM-only attestion? having the pubkey nested under custom-claims prop feels odd.

I understand your concern.
In the current implementation of AA and AS, the user-data of quote is calculated as hash(nonce | tee-pubkey), which is hard-coded. In contrast, moving the nonce tee-pubkey into custom-claims will gain flexibility in computation of user-data. It's worth noting that this is consistent with the goals of another RFC: https://github.com/confidential-containers/kbs/issues/259
This proposal is still compatible with "TVM-only attestation" case, where we just need to remove the "nested-tee" field.

in the proposed schema for tee-evidence, tee-type is introduced. At the moment, in an RCAR exchange the TEE type is set as part of the Request. is there a redundancy?

Yes, the introduction of tee-type into tee-evidence was intended to identify the type of evidence. In this proposal, we only have one CPU TEE, therefore it is a redundant. I will remove it later. Thank you.

So it seems like we will need to differentiate between the CPU evidence and all the other evidence. Essentially this is because the attestation part of RCAR is transmitted in the clear, so we need to create a binding between the CPU evidence and all the additional evidence. Otherwise the evidence could be modified in transit to include a valid device attestation that does not represent the VM.
We could probably implement this by keeping the existing limitation of one TEE/attester per guest and adding an additional set of attesters for devices. Ideally these could have a simple coupling. We would run the device attesters first and generate all the evidence for all the devices (or if using the TDM we would actually have the claims at this point). These claims would be part of the input to the TEE attester.
The proposal here talks about hashing the evidence and including it in the report data, but I wonder if we should consider signing the evidence instead, perhaps with the keypair that is already represented in the report data. This might make the coupling between the device attesters and the CPU attester simpler. I'm not sure.
At the moment I am not sure about the status of the TDM. If we want to get things moving quickly, option 2 might be better. I guess we are sort of juggling complexity between the TDM and Trustee either way.


Improves conditionals by refactoring it into smaller, more readable methods

Maybe it's clearer and more elegant in general to use short-circuit instead of guard clauses mixed with a returning false statement. The resulting methods created were named in order to be explicit about its intentions, namely #matches_string? and #matches_regex?. I wonder if #matches shouldn't have a '?' as well...
Also created a test case for when matches receives nil.

Nice. I like it.


inconsistent or confusing cloudevent type mapping in cloudevents-binding spec

The cloudevents-binding spec states that the cloudevent type must be set to the cdevent type but then the included HTTP example has a mismatch between the ce-type: dev.cdevents.taskrun.started.0.1-draft header and the data's "context"."type":"dev.cdevents.taskrun.started" field.

Thanks @strangemonad for reporting this, that is indeed an oversight, I will make a PR to fix it.


poolSnapshots returns only 1 data point

This query should return multiple data points as I added liquidity multiple times, but it's returning only last data point.

Not a bug, all the tx were done in the same day ( query ) . The pool snapshot is per day.  It represents the total at the end of the day

ha, that like makes total sense, was so used to our live behavior


test/testutil.c: Flush stdout when running tests

Because stdout is usually buffered and stderr isn't, error output
might get printed in one bunch and all the lines saying which test
failed all in one bunch, making it difficult to see exactly what error
output belongs to what test.  Flushing stdout makes sure the runner
output is displayed together with the corresponding error output.

Checklist

[x] tests are added or updated

Merged.  a743b817d28ced8c8a4f2250ae9cbec39af937aa


[Callbacks] Named arguments not supported

Dash now supports named arguments in the callbacks (see here). However, using it with dash-extensions does not work.
MWE:
from dash import dcc, html, Input, Output, Dash
from dash_extensions import Dash as DashExtensions

# app = Dash(__name__) # this works
app = DashExtensions(__name__) # this does not

app.layout = html.Div([
    html.H6("Change the value in the text box to see callbacks in action!"),
    html.Div([
        "Input: ",
        dcc.Input(id='my-input', value='initial value', type='text')
    ]),
    html.Br(),
        html.Div(id='my-output'),
    ])

@app.callback(
    output=[Output('my-output', 'children')],
    inputs={'input_value': Input('my-input', 'value')}
    )
def update_output_div(input_value):
    return [f'Output: {input_value}']

if __name__ == '__main__':
    app.run_server(debug=True)

Support has been added in dash-extensions==0.1.3. Please let me know if everything works as intended.


Build docker image with disabling max readahead

Ⅰ. Describe what this PR does
Ⅱ. Does this pull request fix one issue?

Ⅲ. List the added test cases (unit test/integration test) if any, please explain if no tests are needed.
Ⅳ. Describe how to verify it
Ⅴ. Special notes for reviews

Codecov Report

Merging #203 into master will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #203   +/-   ##
=======================================
  Coverage   18.82%   18.82%
=======================================
  Files          47       47
  Lines        2003     2003
=======================================
  Hits          377      377
  Misses       1587     1587
  Partials       39       39

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 9836259...4b13a6d. Read the comment docs.


[Feature] Dashboard filter indicators

CATEGORY
Choose one

[ ] Bug Fix
[x] Enhancement (new features, refinement)
[x] Refactor
[x] Add tests
[ ] Build / Development Environment
[ ] Documentation

SUMMARY

BEFORE/AFTER SCREENSHOTS OR ANIMATED GIF

TEST PLAN

ADDITIONAL INFORMATION

[ ] Has associated issue:
[x] Changes UI
[ ] Requires DB Migration.
[ ] Confirm DB Migration upgrade and downgrade tested.
[x] Introduces new feature or API
[ ] Removes existing feature or API

REVIEWERS

Needs rabasing (build error fixed in master)

Codecov Report

Merging #7908 into master will decrease coverage by 0.15%.
The diff coverage is 54.1%.

@@            Coverage Diff             @@
##           master    #7908      +/-   ##
==========================================
- Coverage    65.8%   65.64%   -0.16%
==========================================
  Files         461      479      +18
  Lines       22210    22518     +308
  Branches     2425     2502      +77
==========================================
+ Hits        14616    14783     +167
- Misses       7473     7604     +131
- Partials      121      131      +10

Impacted Files
Coverage Δ

...ets/src/visualizations/FilterBox/transformProps.js
0% <ø> (ø)
:arrow_up:

superset/assets/src/chart/chartReducer.js
20.33% <ø> (ø)
:arrow_up:

superset/assets/src/dashboard/reducers/index.js
100% <ø> (ø)
:arrow_up:

...sets/src/dashboard/containers/DashboardBuilder.jsx
0% <ø> (ø)
:arrow_up:

.../assets/src/dashboard/containers/DashboardGrid.jsx
100% <ø> (ø)
:arrow_up:

...ts/src/dashboard/containers/DashboardComponent.jsx
100% <ø> (ø)
:arrow_up:

...ssets/src/dashboard/containers/DashboardHeader.jsx
100% <ø> (ø)
:arrow_up:

...rset/assets/src/dashboard/containers/Dashboard.jsx
0% <ø> (ø)
:arrow_up:

superset/assets/src/dashboard/util/isEmptyValue.js
0% <0%> (ø)

...t/assets/src/dashboard/reducers/getInitialState.js
0% <0%> (ø)
:arrow_up:

... and 57 more

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 ee3430c...2e92ec9. Read the comment docs.

ping @etr2460 I rebased onto master, fixed most of comments. Please take a second look. Thanks.

I can't wait to see this through. Hats off to everyone involved!

Any update?

This will probably get merged today!

YAY!!!!!


style: formatted with black eegnb/ --skip-string-normalization

Used the wonderful black to format the codebase.
Kind of a "meaningless" change (there are benefits to consistent formatting, but I won't argue them here), just wanted to put the suggestion out there.
Can wait for consideration until after all the upcoming hackathon PRs are merged (reapplying is trivial).
Someone will inevitably mention that this breaks git blame et al, but you can use git blame --ignore-rev=<commit> (or --ignore-rev-file=<filename-with-commit-ids.txt>) to have it ignore the style applying commits.

CI is failing because of this needed fix: #31

Sounds like a good idea to me.

I think using something like black is a good idea overall. We decided against it in braindecode (see https://github.com/braindecode/braindecode/pull/32) to instead use flake8 and rely on the CI to catch formatting problems. But if we don't care whether the code is pep8 compliant then using black is probably a good way to save time! :)

ok, approving if no objections ?

@JohnGriffiths Merge #41 when ready and then I'll reapply the formatting and merge.


media includes video tracks but none are playable by this device issue

Dear ExoPlayer Development Team,
I’m encountering an issue with a live HLS stream in my application that uses Media3 ExoPlayer. When attempting to play the stream, I receive the following error message:
"Media includes video tracks but none are playable by this device."
I have tested the same stream with the latest version of the ExoPlayer demo app, and the issue persists. However, the stream works perfectly fine in other players like VLC Player without any problems.
This suggests that the stream is valid but might not be compatible with the current implementation of ExoPlayer. If required, I can email you the stream link for testing.
I would greatly appreciate it if you could investigate this issue and let me know if a fix or workaround is possible.
Looking forward to your feedback.
Best regards,

Thanks for your report!

This suggests that the stream is valid but might not be compatible with the current implementation of ExoPlayer.

ExoPlayer supports what the device supports on which it runs, so having this info would be important too.
Easiest to provide us with all the information required: Please attempt to play the stream and then after the exception happend create a bug report and upload it here or send it to us by email together with the stream URI. If the stream needs specific config on our side to be accessible, please explain accordingly.
Please send the test stream URI to<EMAIL_ADDRESS>using a subject in the format "Issue #1965". Please also update this issue to indicate you’ve done this.

Hi again ,

Hi again ,
I sent the sample stream link 2 days ago . Please check Email . Thanks


Client enables logging non-typical error responses from the server

Motivation and context

How has this been tested?

Checklist

[x] I submit my changes into the develop branch
[ ] I have created a changelog fragment
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (see GitHub docs)
[ ] I have increased versions of npm packages if it is necessary
(cvat-canvas,
cvat-core,
cvat-data and
cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.

Summary by CodeRabbit

Bug Fixes

Improved error logging by selectively logging ServerError based on specific error codes, reducing unnecessary log entries.

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

Project coverage is 74.21%. Comparing base (12dac6d) to head (2478bb1).
Report is 1 commits behind head on develop.

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #8538      +/-   ##
===========================================
- Coverage    74.24%   74.21%   -0.04%
===========================================
  Files          400      400
  Lines        43207    43210       +3
  Branches      3905     3906       +1
===========================================
- Hits         32081    32067      -14
- Misses       11126    11143      +17

Components
Coverage Δ

cvat-ui
78.60% <100.00%> (-0.09%)
:arrow_down:

cvat-server
70.47% <ø> (ø)


[WIP] Fix native test

Related to https://github.com/kiegroup/kogito-runtimes/pull/1631 and to this failure https://github.com/quarkusio/quarkus/issues/12486#issuecomment-938477386
Many thanks for submitting your Pull Request :heart:!
Please make sure that your PR meets the following requirements:

[ ] You have read the contributors guide
[ ] Your code is properly formatted according to this configuration
[ ] Pull Request title is properly formatted: KOGITO-XYZ Subject
[ ] Pull Request title contains the target branch if not targeting main: [0.9.x] KOGITO-XYZ Subject
[ ] Pull Request contains link to the JIRA issue
[ ] Pull Request contains link to any dependent or related Pull Request
[ ] Pull Request contains description of the issue
[ ] Pull Request does not include fixes for issues other than the main ticket

How to retest this PR or trigger a specific build:

Run all builds
Please add comment: Jenkins retest this

Run (or rerun) specific test(s)
Please add comment: Jenkins (re)run [runtimes|optaplanner|apps|examples] tests

Quarkus LTS checks
Please add comment: Jenkins run LTS

Run (or rerun) LTS specific test(s)
Please add comment: Jenkins (re)run [runtimes|optaplanner|apps|examples] LTS

Native checks
Please add comment: Jenkins run native

Run (or rerun) native specific test(s)
Please add comment: Jenkins (re)run [runtimes|optaplanner|apps|examples] native

Full Kogito testing (with cloud images and operator BDD testing)
Please add comment: Jenkins run BDD
This check should be used only if a big change is done as it takes time to run, need resources and one full BDD tests check can be done at a time ...

Jenkins run runtimes native

Jenkins run runtimes native

The (build) Examples check has failed. Please check the logs.

The (build) kogito-examples check has failed. Please check the logs.

The (build) kogito-apps check has failed. Please check the logs.

The (build) kogito-examples check has failed. Please check the logs.

The (build) kogito-apps check has failed. Please check the logs.


Feature request: Calculator

A user on Google Play suggested I add a calculator to Trail Sense for use in survival / hiking.
I need to do more research before I close this without changes to confirm that there is nothing I could add that fits within Trail Sense's use case (that isn't already covered by a tool).
Most likely, I'll change this issue to a mention in the recommended apps guide.

This was requested by another user, I have still not received any feedback on how a calculator would be useful under TS' use cases though.

Not going to add this, too general for Trail Sense (I prefer the tools to do their own calculations)


Centralized risk factors, outcomes etc dictionaries

Currently, every time a new risk factor or outcome is created/added in the simulation, it needs to be manually included everywhere in the code there is an iteration (or some sort of iteration) over risk factors or outcomes...and this introduces the high probability that at some point we will forget to include it somewhere...
The idea is that we will create a dictionary with keys all risk factors, and a dictionary with keys all outcomes (and perhaps more dictionaries for other things as well). The values will be the methods needed to calculate or obtain these risk factors and outcomes.
Any part of the simulation that needs to iterate over risk factors, outcomes etc will automatically access that dictionary to obtain the list of risk factors, outcomes etc.
So that when we add a new key:value pair that is all that should be needed to do.

Done.