resholve: update README

Motivation for this change
Partially addressing doc feedback from @domenkozar on IRC.

This is great! Thanks for doing it.
Another thing that comes to mind is that the current approach of wrapping a derivation is not as composable as it could be, for example it's harder to use with other derivation wrapping things like building haskell/python packages .

This is great! Thanks for doing it.
Another thing that comes to mind is that the current approach of wrapping a derivation is not as composable as it could be, for example it's harder to use with other derivation wrapping things like building haskell/python packages .

Another thing that comes to mind is that the current approach of wrapping a derivation is not as composable as it could be, for example it's harder to use with other derivation wrapping things like building haskell/python packages .

Yes. I assume there'll be some more variants that fill in over time as people identify itches to scratch with it. In the interim, it's possible to just use the resholve package itself and directly invoke in the appropriate phase as needed.

Another thing that comes to mind is that the current approach of wrapping a derivation is not as composable as it could be, for example it's harder to use with other derivation wrapping things like building haskell/python packages .

Yes. I assume there'll be some more variants that fill in over time as people identify itches to scratch with it. In the interim, it's possible to just use the resholve package itself and directly invoke in the appropriate phase as needed.


Update pom.xml

:tada: This PR is included in version 2.0.16 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


feat(chor): add bin executable

This MR adds bin executable into /node_modules/.bin/ folder after package is installed to simplify "provider" usage to just "prisma-json-schema-generator".

@muxahuk Thank you for your contribution! 🥳


Add FAQ for using remote instances with the project workflow

This was asked here and here, but I'm not sure the project guide is the best place to add this.

Thanks for the fix!


CORS error

I have used cloud flare to point my domain to my servers IP address.
After this I got an SSL certificate using letsEncrypt.
I updated the domain to https in the .env file.
but now I am getting CORS errors. Is this a nginx issue?
Access to XMLHttpRequest at 'https://myurl/api/guest/feed?sort=hot&page=1&filter=subscribed&exclude_liked_submissions=0&include_nsfw_submissions=0&exclude_bookmarked_submissions=0&submissions_type=All&all_tags=0' from origin 'https://myurl' has been blocked by CORS policy: Request header field X-Socket-Id is not allowed by Access-Control-Allow-Headers in preflight response.
https://i.imgur.com/m8JJs4d.png
Thanks for any help

Fixed by including:
composer require barryvdh/laravel-cors


Improved Jira Issues config docs for authentication

If you provide the email and Atlassian API token as written, the JiraClient assumes the token is a password and tries to call the API with username (=email) and password (=token). This doesn't work.
Description
Adjusted the config example and added a sentence explaining the two options: a) using a personal access token or b) using email and password to authenticate with the JiraClient.
Checklist

[ ] The base branch of this PR is preview, rather than main

Thanks for the update!


Purge to clean

This PR migrates our purgeban command away from Discord's native purgeban in favour of our custom logic.
Discord's native purgeban does not leave us with any evidence or context of what messages were deleted. So when mods reference the infraction at a later date, as example for an appeal, they are lacking required information.
Instead, we can use our custom clean cog to delete all messages from the user in question for the last hour, and automatically append the link to that clean log to the infraction reason.

Since this changeset introduces additional cross-cog dependencies, I'm planning on writing some tests for this new behaviour. Will get around to it later this evening/tomorrow.

Since this changeset introduces additional cross-cog dependencies, that could be unintentionally broken, I'm planning on writing some tests for this new behaviour. Will get around to it later this evening/tomorrow.

There are some aditional bugs with undefined behavior related to this, depending on how they are implemented.
Please check https://github.com/python-discord/bot/issues/2022#issuecomment-997541569 for more information.
(Also, Happy new year!)

Since this changeset introduces additional cross-cog dependencies, that could be unintentionally broken, I'm planning on writing some tests for this new behaviour. Will get around to it later this evening/tomorrow.

There are some aditional bugs with undefined behavior related to this, depending on how they are implemented.
Please check https://github.com/python-discord/bot/issues/2022#issuecomment-997541569 for more information.
(Also, Happy new year!)

I'm only importing for type checking, so I dont follow how that applies for this case?


✨ add koa-performance package

Description
This PR adds the koa companion library to @shopify/react-performance. It is mostly the same as the impelmentation in Shopify-web, with a few minor changes:

it bundles in body parsing using koa-compose
it no longer exposes the browser abstraction to custom tag functions, instead it just passes the user-agent header directly
we add a bit of a README

Checklist

[x] I have added a changelog entry, prefixed by the type of change noted above

@michenly  all feedback should be addressed, let me know if you see issues with the solution for the snakecase stuff


APEXCORE-411 support restarting app without app package or jar files

@tweise please review

@tweise explanation is added in the comment.


use babel-plugin-transform-flow-comments instead of babel-plugin-strip-types to preserve flow types.

this way the /es builds will still have all their type info
Fixes #4

Close this PR, cause Flow must respect .js..flow files which already included in the package.
Feel free to discuss your problem in #4


[Bug fix] make fails because of invalid assertion in py-qfactor

Thank you for catching this and proposing a fix. Fortunately, this was addressed quickly by https://github.com/eclipse/xacc/pull/396. Try to pull and rebuild to see that your build is fixed.

Yes, you're right. Thanks! I am closing the pull request.


Switch to using json for config

So it will work for a JS linter

#57 is related.

I'm not sure about this any more.
JSON means a whole lot boilerplate than Ruby for the very basic cases, and the runner is in Ruby. Also you can't do anything dynamic in JSON, which is why I think we struggled to find the right shape for this new configuration when we had a little play with this idea.
We know that testing a single page in a browser is useful, but we haven't established that running a whole suite in a browser is possible yet. IMO we should spike running a whole suite in a browser before doing this.

Ok sounds sensible. Let's defer this for now. Shall we just close the
ticket? We're hardly likely to forget the idea.
On Mon, 4 Jan 2016 at 13:08, Josh Chisholm<EMAIL_ADDRESS>wrote:

I'm not sure about this any more.
JSON means a whole lot boilerplate than Ruby for the very basic cases, and
the runner is in Ruby. Also you can't do anything dynamic in JSON, which is
why I think we struggled to find the right shape for this new configuration
when we had a little play with this idea.
We know that testing a single page in a browser is useful, but we haven't
established that running a whole suite in a browser is possible yet. IMO we
should spike running a whole suite in a browser before doing this.
—
Reply to this email directly or view it on GitHub
https://github.com/cucumber-ltd/bbc-a11y/issues/60#issuecomment-168673238
.

Yep let's close for now


fix wrong repository url

Coverage remained the same at 71.231% when pulling 28e8fe13a3095cfdbf7bdff7e6e4eb76c7fc1bd0 on fix-typo-in-url into 2d83952b580bca7a28b59be0e899f79adae3aca8 on master.


Bug: no-missing-require incorrectly flagging module as missing

Environment
Node version: v20.11.0
npm version: v10.4.0
ESLint version: v9.0.0
eslint-plugin-n version: v17.2.0
Operating System: win32 10.0.19045
What rule do you want to report?
no-missing-require
Link to Minimal Reproducible Example
https://github.com/eslint/eslint/pull/18313
What did you expect to happen?
That the rule would correctly find the module @humanwhocodes/retry.
Worked in v16.6.2, stopped working in v17.0.0.
Participation

[ ] I am willing to submit a pull request for this issue.

Additional comments
No response

After some looking, this is related to: https://github.com/eslint-community/eslint-plugin-n/issues/182
The error is that the exports are the wrong way around:
https://github.com/humanwhocodes/retry/blob/8f8af13/package.json#L10-L13
Therefore this error is getting triggered:
https://github.com/webpack/enhanced-resolve/blob/main/lib/util/entrypoints.js#L475

For context: Sounds like this regression is caused by https://github.com/eslint-community/eslint-plugin-n/pull/139 then
@scagood Want help to look into it?

Yeah, I would tend to agree. I am thinking about what the best course here is.
We could:

Ignore the error (but then not have a path)
Pr enhanced resolve to allow the error to be ignored via an option (I don't understand why it throws as opposed to just accepting the default as default)

seems it's working as expected - as said in the node.js docs:

"default" - the generic fallback that always matches. Can be a CommonJS or ES module file. This condition should always come last.

https://nodejs.org/docs/latest/api/packages.html
the next steps:

it should report the exact error message in the rule, than just ignoring.
fix @humanwhocodes/retry to put the default to last.

The think that is in in the back of my head is related to this:

This condition should always come last.

I interpret this as should always be checked last, not should always appear last in the object's properties
I do know that as of es2020 property ordering is expected (eg in for-in). But before that I don't think there was any guarantee of order :thinking:

maybe (I'm not a native English speaker). but it's also saying:

Within the "exports" object, key order is significant. During condition matching, earlier entries have higher priority and take precedence over later entries. The general rule is that conditions should be from most specific to least specific in object order.

generally, it should be a best practice to put it in the last.

Fair point! notes for next time include to read the source! :sweat_smile:

Note that the "types" condition should always come first in "exports".

Taken from https://www.typescriptlang.org/docs/handbook/release-notes/typescript-4-7.html#packagejson-exports-imports-and-self-also supports this

I think we should then close this and proceed with #182 (My first attempt to make that more verbose is here: #231)

Well, if node.js can resolve the module and the issue this plugin finds isn’t within the project that runs the linting but rather in one of its dependencies, then I think the linting shouldn’t fail as it’s kind of a false alarm?
Such a failed linting should happen in the project that published the incorrect fields instead.

Well, if node.js can resolve the module and the issue this plugin finds isn’t within the project that runs the linting but rather in one of its dependencies, then I think the linting shouldn’t fail as it’s kind of a false alarm?
Such a failed linting should happen in the project that published the incorrect fields instead.

I agree with this. The current setup for the retry package works fine in Node.js so I don't think it should be considered a problem. This seems more like something that other tooling is trying to enforce rather than an actual problem with the package.
That said, I can update the package to swap the order of exports.

Agreed, I think I will do point two:

Pr enhanced resolve to allow the error to be ignored via an option

It may also be worth seeing if we can add a rule to eslint-plugin-package-json too specifically about this if there is not one already 🤔


CORE-17899: Eliminate use of deprecated annotation for Ingress

Before the change:
> helm install corda -n corda charts/corda --values values-prereqs.yaml --wait
W1024 13:39:43.341482   16912 warnings.go:70] annotation "kubernetes.io/ingress.class" is deprecated, please use 'spec.ingressClassName' instead

Tested-by: vkolomeyko
By using local deployment of C5 cluster

Looks like more work is required to remove this working due to:
The newer ingressClassName field on Ingresses is a replacement for that annotation, but is not a direct equivalent. While the annotation was generally used to reference the name of the Ingress controller that should implement the Ingress, the field is a reference to an IngressClass resource that contains additional Ingress configuration, including the name of the Ingress controller.


Index addressable content types

Index addressable content types in a new Elasticsearch index as per the "All" search RFC.
This ticket will also ensure the correct mapping is defined.
Ready when these are done:

[ ] #155
[ ] #156

I'll do the prep for this although it needs #156, it'll just be ready for when we have transformers. https://github.com/wellcomecollection/content-api/pull/162


Style Guide

I am working on standardizing the colors and fonts across all pages so that we can have a concise and easy to follow style guide.  This should extend to iOS and Android Apps.

Thumbs up! Please drop a heads' up to Michael and the project leads as I'd
like them to add OS-specific hooks [ie app extensions ] to handle
conformance automatically in conjunction with your style guidelines
On Sun, Sep 17, 2017 at 11:47 AM Leikela<EMAIL_ADDRESS>wrote:

I am working on standardizing the colors and fonts across all pages so
that we can have a concise and easy to follow style guide. This should
extend to iOS and Android Apps.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/CodeDoesGood/Mercury-Web/issues/43, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AEXrU9Unfi8kr7YjJOrl437vz4MAhl4Jks5sjWlRgaJpZM4PaPQS
.

Moved to mercury front.


Allow accents in file names

Closes: #16

@basak Was there still something blocking merge of this?

I rebased the patch to master and add there some python3 compatibility code.


genshin: Migrate to new global API Endpoint

The genshin gacha & Account Records API of global(Asia/EU/NA) seems to have been migrated to the similar sub-domain as the mihoyo ver.
fix: #987

Thanks for your contribution.


Export ES module

We should export an ES module along with the normal CommonJS module so people using modern tools can benefit from things like tree shaking.

Exporting with zcomponent.es.js. Modern web package managers should handle it automatically via jsnext:main or module keywords in package.json.


[Connectivity] Checking private or public Wi-Fi network

I want to check if I have connected to home Wi-Fi or public Wi-Fi (say, hotel Wi-Fi or hotspot) and depending on it, restrict some app features for security reasons.

Hello, seems to be not possible on iOS, for now, :/ https://stackoverflow.com/questions/7030561/can-you-determine-if-wifi-security-is-enabled-on-network-youre-connected-to-on


Links are absolute instead of relative inside the docs generated

Links are absolute instead of relative inside the docs generated
as in: Defined in c:\msweb\signagestudio_web-lite_views\AddBlockView.js:249
instead of: Defined in _views\AddBlockView.js:249
this works fine from command line but using the gulp-yuidoc the links are abolsute which is no good if we host on web server...
please help
Sean.

I guess it was fixed here:
https://github.com/jsBoot/gulp-yuidoc/pull/13/files
please update npm as it still is without this critical fix..
regards

I installed two days ago and I had the same issue. Have the fixed version been published on npm?

hello!? can you push this fix please?


client: export GetLeaderAddr

Signed-off-by: disksing<EMAIL_ADDRESS>What problem does this PR solve?
Some tools need to access PD's HTTP API but cannot know which PD is current leader.
What is changed and how it works?
export GetLeaderAddr.
Check List
Tests

only export exsisted function.

/run-all-tests


vim no response

vim or neovim?

[ ] vim
[x] neovim

Output of vim --version or nvim --version:
NVIM v0.4.0-632-g9d77a0768
Build type: Release
LuaJIT 2.0.5
Compilation: /Applications/Xcode-10.1.app/Contents/Developer/Toolchains/XcodeDefault.xctoolchain/usr/bin/clang -U_FORTIFY_SOURCE -D_FORTIFY_SOURCE=1 -O2 -DNDEBUG -DMIN_LOG_LEVEL=3 -Wall -Wextra -pedantic -Wno-unused-parameter -Wstrict-prototypes -std=gnu99 -Wshadow -Wconversion -Wmissing-prototypes -Wimplicit-fallthrough -Wvla -fstack-protector-strong -fdiagnostics-color=auto -DINCLUDE_GENERATED_DECLARATIONS -D_GNU_SOURCE -DNVIM_MSGPACK_HAS_FLOAT32 -DNVIM_UNIBI_HAS_VAR_FROM -I/Users/travis/build/neovim/bot-ci/build/neovim/build/config -I/Users/travis/build/neovim/bot-ci/build/neovim/src -I/Users/travis/build/neovim/bot-ci/build/neovim/.deps/usr/include -I/usr/local/opt/gettext/include -I/usr/include -I/Users/travis/build/neovim/bot-ci/build/neovim/build/src/nvim/auto -I/Users/travis/build/neovim/bot-ci/build/neovim/build/include
Compiled by<EMAIL_ADDRESS>
Features: +acl +iconv +tui
See ":help feature-compile"
system vimrc file: "$VIM/sysinit.vim"
fall-back for $VIM: "/share/nvim"
Run :checkhealth for more info

Output of :echo has("python"): 0
Output of :echo has("python3"): 1
Output of :echo &pythondll(only vim, not neovim):
Output of :echo &pythonthreedll(only vim, not neovim):
Output of :py print(sys.version): not found
Output of :py3 print(sys.version):
3.7.3 (default, Apr 11, 2019 07:24:24)
[Clang 10.0.1]
Output of :echo g:Lf_Debug_Cmd:
undefined variable
Output of :echo g:Lf_FilesFromCache:
undefined variable
Operating system:

[ ] Linux
[x] Mac OS X
[ ] Windows
[ ] Etc.

Configurations related to LeaderF in vimrc:
let g:Lf_ShortcutF = ''
let g:Lf_CommandMap = {'': ['']}
let g:Lf_DefaultMode = 'NameOnly'
let g:Lf_WindowHeight = 0.3
let g:Lf_WorkingDirectoryMode = 'Ac'

Describe your question, feature request, or bug.
When :Leaderf rg  to search something, sometimes no response. this time I wanted to search for .xml,  I input (trying to input .xml)
.
and then no response
Steps to reproduce
not sure if you can have same issue.
Actual behaviour
Expected behaviour

It is fuzzy mode, you don't have to escape the dot, just input .xml is OK.

that did the trick. hope this can help you debug

How to reproduce the error?

This issue should be the same reason as #318 , Could you please provide the file src/assets/img/Avatar-White-Wat..., so that I can reproduce it ?


[web] --web-renderer html includes canvaskit

Is there an existing issue for this?

[X] I have searched the existing issues
[X] I have read the guide to filing a bug

Steps to reproduce
I'm reopening #96509 as this issue still hasn't been resolved. In contrast to the original issue, the canvaskit folder is always created for me when running
flutter build web --web-renderer html

The result is that the default counter app clocks in at 20 instead of 3MB.
Expected results
I'd expect the web build folder to look like this, without canvaskit included.
.
├── assets
│   ├── AssetManifest.bin
│   ├── AssetManifest.json
│   ├── FontManifest.json
│   ├── fonts
│   │   └── MaterialIcons-Regular.otf
│   ├── NOTICES
│   ├── packages
│   │   └── cupertino_icons
│   │       └── assets
│   │           └── CupertinoIcons.ttf
│   └── shaders
│       └── ink_sparkle.frag
├── favicon.png
├── flutter.js
├── flutter_service_worker.js
├── icons
│   ├── Icon-192.png
│   ├── Icon-512.png
│   ├── Icon-maskable-192.png
│   └── Icon-maskable-512.png
├── index.html
├── main.dart.js
├── manifest.json
└── version.json

Actual results
The web build folder includes a 16MB large canvaskit folder which isn't necessary to run the app.
.
├── assets
│   ├── AssetManifest.bin
│   ├── AssetManifest.json
│   ├── FontManifest.json
│   ├── fonts
│   │   └── MaterialIcons-Regular.otf
│   ├── NOTICES
│   ├── packages
│   │   └── cupertino_icons
│   │       └── assets
│   │           └── CupertinoIcons.ttf
│   └── shaders
│       └── ink_sparkle.frag
├── canvaskit
│   ├── canvaskit.js
│   ├── canvaskit.wasm
│   ├── chromium
│   │   ├── canvaskit.js
│   │   └── canvaskit.wasm
│   ├── skwasm.js
│   ├── skwasm.wasm
│   └── skwasm.worker.js
├── favicon.png
├── flutter.js
├── flutter_service_worker.js
├── icons
│   ├── Icon-192.png
│   ├── Icon-512.png
│   ├── Icon-maskable-192.png
│   └── Icon-maskable-512.png
├── index.html
├── main.dart.js
├── manifest.json
└── version.json

Code sample
Code sample
[Paste your code here]

Screenshots or Video

Screenshots / Video demonstration
[Upload media here]

Logs
Logs
[Paste your logs here]

Flutter Doctor output
Doctor output
[✓] Flutter (Channel stable, 3.10.0, on Garuda Linux 6.3.1-zen2-1-zen, locale en_US.UTF-8)
    • Flutter version 3.10.0 on channel stable at /opt/flutter
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 84a1e904f4 (4 days ago), 2023-05-09 07:41:44 -0700
    • Engine revision d44b5a94c9
    • Dart version 3.0.0
    • DevTools version 2.23.1

[✗] Android toolchain - develop for Android devices
    ✗ ANDROID_HOME = /opt/android-sdk
      but Android SDK not found at this location.

[✓] Chrome - develop for the web
    • CHROME_EXECUTABLE = /usr/bin/chromium

[✓] Linux toolchain - develop for Linux desktop
    • clang version 15.0.7
    • cmake version 3.26.3
    • ninja version 1.11.1
    • pkg-config version 1.8.1

[!] Android Studio (not installed)
    • Android Studio not found; download from https://developer.android.com/studio/index.html
      (or visit https://flutter.dev/docs/get-started/install/linux#android-setup for detailed instructions).

[✓] Connected device (2 available)
    • Linux (desktop) • linux  • linux-x64      • Garuda Linux 6.3.1-zen2-1-zen
    • Chrome (web)    • chrome • web-javascript • Chromium 113.0.5672.92 Arch Linux

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 2 categories.

Thanks for the report. Seeing the same behavior as reported, as canvaskit folder gets created upon running the provided command.

 stable, master flutter doctor -v
[!] Flutter (Channel stable, 3.10.0, on macOS 12.2.1 21D62 darwin-x64, locale
    en-GB)
    • Flutter version 3.10.0 on channel stable at
      /Users/dhs/documents/fluttersdk/flutter
    ! Warning: `flutter` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/flutter, which is not inside
      your current Flutter SDK checkout at
      /Users/dhs/documents/fluttersdk/flutter. Consider adding
      /Users/dhs/documents/fluttersdk/flutter/bin to the front of your path.
    ! Warning: `dart` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/dart, which is not inside your
      current Flutter SDK checkout at /Users/dhs/documents/fluttersdk/flutter.
      Consider adding /Users/dhs/documents/fluttersdk/flutter/bin to the front
      of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 84a1e904f4 (2 days ago), 2023-05-09 07:41:44 -0700
    • Engine revision d44b5a94c9
    • Dart version 3.0.0
    • DevTools version 2.23.1
    • If those were intentional, you can disregard the above warnings; however
      it is recommended to use "git" directly to perform update checks and
      upgrades.

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] VS Code (version 1.62.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

[!] Flutter (Channel master, 3.11.0-6.0.pre.63, on macOS 12.2.1 21D62
    darwin-x64, locale en-GB)
    • Flutter version 3.11.0-6.0.pre.63 on channel master at
      /Users/dhs/documents/fluttersdk/flutter
    ! Warning: `flutter` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/flutter, which is not inside
      your current Flutter SDK checkout at
      /Users/dhs/documents/fluttersdk/flutter. Consider adding
      /Users/dhs/documents/fluttersdk/flutter/bin to the front of your path.
    ! Warning: `dart` on your path resolves to
      /Users/dhs/Documents/Fluttersdk/flutter/bin/dart, which is not inside your
      current Flutter SDK checkout at /Users/dhs/documents/fluttersdk/flutter.
      Consider adding /Users/dhs/documents/fluttersdk/flutter/bin to the front
      of your path.
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision 7b8f7a2a64 (7 hours ago), 2023-05-14 17:42:29 -0400
    • Engine revision 326de1d849
    • Dart version 3.1.0 (build 3.1.0-110.0.dev)
    • DevTools version 2.23.1
    • If those were intentional, you can disregard the above warnings; however
      it is recommended to use "git" directly to perform update checks and
      upgrades.

[!] Android toolchain - develop for Android devices (Android SDK version 30.0.3)
    • Android SDK at /Users/dhs/Library/Android/sdk
    ✗ cmdline-tools component is missing
      Run `path/to/sdkmanager --install "cmdline-tools;latest"`
      See https://developer.android.com/studio/command-line for more details.
    ✗ Android license status unknown.
      Run `flutter doctor --android-licenses` to accept the SDK licenses.
      See https://flutter.dev/docs/get-started/install/macos#android-setup for
      more details.

[✓] Xcode - develop for iOS and macOS (Xcode 13.2.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 13C100
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] IntelliJ IDEA Ultimate Edition (version 2021.3.2)
    • IntelliJ at /Applications/IntelliJ IDEA.app
    • Flutter plugin version 65.1.4
    • Dart plugin version 213.7228

[✓] VS Code (version 1.62.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.29.0

[✓] Connected device (3 available)
    • Darshan's iphone (mobile) • 21150b119064aecc249dfcfe05e259197461ce23 • ios
      • iOS 15.3.1 19D52
    • macOS (desktop)           • macos                                    •
      darwin-x64     • macOS 12.2.1 21D62 darwin-x64
    • Chrome (web)              • chrome                                   •
      web-javascript • Google Chrome 109.0.5414.119

[✓] Network resources
    • All expected network resources are available.

! Doctor found issues in 1 category.

[!] Xcode - develop for iOS and macOS (Xcode 12.3)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    ! Flutter recommends a minimum Xcode version of 13.
      Download the latest version or update via the Mac App Store.
    • CocoaPods version 1.11.2

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] VS Code (version 1.62.0)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension version 3.21.0

[✓] Connected device (5 available)
    • SM G975F (mobile)       • RZ8M802WY0X • android-arm64   • Android 11 (API 30)
    • Darshan's iphone (mobile)  • 21150b119064aecc249dfcfe05e259197461ce23 •
      ios            • iOS 14.4.1 18D61
    • iPhone 12 Pro Max (mobile) • A5473606-0213-4FD8-BA16-553433949729     •
      ios            • com.apple.CoreSimulator.SimRuntime.iOS-14-3 (simulator)
    • macOS (desktop)            • macos                                    •
      darwin-x64     • Mac OS X 10.15.4 19E2269 darwin-x64
    • Chrome (web)               • chrome                                   •
      web-javascript • Google Chrome 98.0.4758.80

[✓] HTTP Host Availability
    • All required HTTP hosts are available

! Doctor found issues in 1 category.

@higaski to clarify, your app isn't actually referencing or using canvaskit, this is just tracking having the tool not even generate the canvaskit directory, is that right?

@higaski to clarify, your app isn't actually referencing or using canvaskit, this is just tracking having the tool not even generate the canvaskit directory, is that right?

Not to my knowledge, at least I haven't explicitly written anything which would touch wasm.

This is intentional. Since CanvasKit files are not actually fetched by the browser, their presence has no effect on user experience. Are these files causing issues?

Not directly, but the file sizes can be. Think small embedded devices for e.g. home automation. Those devices might run from small NOR flashes with a couple of MB. An app might no longer fit in memory if a developer forgets to strip the canvaskit folder before deploying a new binary.
May I suggest a CLI option to configure if canvaskit is included or not given html is chosen as renderer? The option could be on by default to not change the current behavior.

I'm seeing the same behavior and agree with @higaski, if I'm building specifying the web renderer I don't expect to have the canvaskit directory created.

We could offer something like this. It would be best to find a way to make this work without too much complexity in the tool. Right now it's simple "dump everything into the build/web directory", but sounds like it's not optimal for all use-cases.


Adding movie page and links

Issue Number
fixes #
ISSUE #163
-->
Describe the changes you've made
Created a movie page with a slider and added 5 categories of movies and linking it with other pages
Describe if there is any unusual behaviour of your code(Write NA if there isn't)
NA
Additional context (OPTIONAL)
NA
Test plan (OPTIONAL)
Clicking on the links
Checklist

[ x] I have added my name in the contributors list at the end of README.md file.
[ x] My code follows the code style of this project.
[ x] My change requires a change to the documentation.
[ x] I have updated the documentation accordingly.
[ x] I have added tests to cover my changes.
[ x] All new and existing tests passed.
[ x] The title of my pull request is a short description of the requested changes.
[ x] Open Source Program names(OPTIONAL: If you participated in any open-source program then please mention the program name here)

@QAZIMAAZARSHAD Sir
I am not able to figure out why this problem is being created when i added movie.html in other files why files are conflicting. Yesterday I spent 5 hours to find the solution. Today also I spent 3 hours but the issue is still not resolved.

Maybe your repo is not updated. Fetch upstream then push changes.
Add only necessary changes, don't change anything.

Everytime before i push file , I clone the new repo and add the movie page and only change the links of every page to movie.html . And then i create a pull request. After that i resolve the conflicts for half an hour but then also🥺🥺🥺 Is there any other way or resource to do it ?

Reach out to mentors in slack channels they will help you in resolving issues.

Okay Sir


Question: is this library still maintained?

Looks like there are 9 months since the last commit. The library still has some bugs and a good amount of issues and PRs.
I wonder if we should move to another package.
Does anyone know if the author still plans to support this library or any other good substitute?

Hi, maintainer here! As long as I am using this library in my own projects (I still very much am), I will continue maintaining this library!


Update server SDK protocol by adding helpful fields.

Changes are the same as the previous PR and spec updates are included in this one.
Changes:

Add MigratableStatus field to HandshakeRequestMessage to indicate if the client connection mapped to the designated server connection can be migrated to another server connection.
Add SequenceId field to ConnectionDataMessage to help the server-side SDK to guarantee the message order (cause it could be sent from a different signalr-runtime instance in the future)
Add LastSequenceId field to CloseConnectionMessage to acknowledge the last acked SequenceId, which could help the ASRS to replay the message to the target server.

[5, ConnectionId, ErrorMessage]

also update this

Refers to: specs/ServiceProtocol.md:146 in f93858b. [](commit_id = f93858ba95f9c791202b16fe477fc69f1d46681b, deletion_comment = False)


Fix ECS DescribeServices max service limit

ECS has a max limit of 10 services per call, not 100. When more than 10 services is in a cluster, the existing method produces a stack trace. https://docs.aws.amazon.com/cli/latest/reference/ecs/describe-services.html
Fixes:
Traceback (most recent call last):
  File "/usr/local/lib/python3.7/site-packages/cartography/sync.py", line 74, in run
    stage_func(neo4j_session, config)
  File "/usr/local/lib/python3.7/site-packages/cartography/util.py", line 117, in timed
    return method(*args, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/cartography/intel/aws/__init__.py", line 225, in start_aws_ingestion
    requested_syncs,
  File "/usr/local/lib/python3.7/site-packages/cartography/intel/aws/__init__.py", line 163, in _sync_multiple_accounts
    aws_requested_syncs=aws_requested_syncs,  # Could be replaced later with per-account requested syncs
  File "/usr/local/lib/python3.7/site-packages/cartography/intel/aws/__init__.py", line 60, in _sync_one_account
    RESOURCE_FUNCTIONS[func_name](**sync_args)
  File "/usr/local/lib/python3.7/site-packages/cartography/util.py", line 117, in timed
    return method(*args, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/cartography/intel/aws/ecs.py", line 571, in sync
    region,
  File "/usr/local/lib/python3.7/site-packages/cartography/util.py", line 117, in timed
    return method(*args, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/cartography/util.py", line 146, in wrapper
    return func(*args, **kwargs)
  File "/usr/local/lib/python3.7/site-packages/cartography/intel/aws/ecs.py", line 76, in get_ecs_services
    services=service_arn_chunk,
  File "/usr/local/lib/python3.7/site-packages/botocore/client.py", line 415, in _api_call
    return self._make_api_call(operation_name, kwargs)
  File "/usr/local/lib/python3.7/site-packages/botocore/client.py", line 745, in _make_api_call
    raise error_class(parsed_response, operation_name)
botocore.errorfactory.InvalidParameterException: An error occurred (InvalidParameterException) when calling the DescribeServices operation: service names can have at most 10 items.

Looks good to me, thanks for submitting! Can you please sign the CLA?

Huh. Maybe the CLA check needs to re-run? I signed the CLA about 30 minutes after submitting the PR.

Sometimes the CLA check is flaky - can you close and reopen this PR to restart it?

No problem! Closing


Every part can now have assets

that are are added to the assets of the style and included in the head.
This is particularly useful for bundling small pieces of javascript or css with the components that need them and thereby gets us closer to being able to write truly self contained "components".  As a proof of concept I did so for the tables javascript parts.  The naming takes care of deduplication of assets.  This can be witnessed in the new two table example (where the javascript is included just once).  Also hat-tip to Johan's cleanup of the examples they are much nicer to read now.
But note the TODO in Part.all_assets and the one in table.py, both of which I would love to cleanup before we release this.

Codecov Report

Merging #83 into master will decrease coverage by 0.02%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master      #83      +/-   ##
==========================================
- Coverage   98.83%   98.81%   -0.03%
==========================================
  Files          64       64
  Lines        8395     8411      +16
==========================================
+ Hits         8297     8311      +14
- Misses         98      100       +2

Impacted Files
Coverage Δ

iommi/part.py
100.00% <100.00%> (ø)

iommi/table.py
98.43% <100.00%> (-0.22%)
:arrow_down:

Continue to review full report at Codecov.

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

We should have a make target to generate all .po files, because it seems we ping pong between running the django commands in various folders, so the translation files are all changed all the time. I think the paths you have in this commit are better than the ones that are on master right now!

I've pushed make targets that we should use to make sure we don't get this ping pong thing in the future:
make makemessages
make compilemessages

Me and @boxed is working on some further improvement on your branch. I hope its ok if we just pile on top of your branch?

Sure go ahead
On Tue, 27 Oct 2020 at 13:38, Johan Lübcke<EMAIL_ADDRESS>wrote:

Me and @boxed https://github.com/boxed is working on some further
improvement on your branch. I hope its ok if we just pile on top of your
branch?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/TriOptima/iommi/pull/83#issuecomment-717214417, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHQUJLMVTUT4SKLHQCME2DSM25KPANCNFSM4S6LWGVQ
.

I think we're done :P We were talking and wondering if you'd like to do some video call where we talk through a few things in the future? Or if you want us to go through our thinking so far or whatever. We do a lot of our stuff in video calls anyway.

I had a read.  Making an Asset a specialized fragment is a very good idea -- did not see that at all.
Happy to have a video chat.

We'll have to figure out what system to use for the video call... We've had bad luck with discord (great sound quality and latency but often doesn't work).

facetime or zoom ?

Didn't think about facetime! I would like to try that for multiple people.

So I pushed another change.  Basically I want assets in styles to behave like Assets in parts, because anything else I consider roughly unexplainable (it's bad enough not to have a good type checker, so let's at least try to be consistent).
This patch get's us closer, in particular one can now write something like:
Style(..., assets__foo__template="my_template_file.html")

and it will work as expected.  Sadly a difference remains in Style assets can be instances of anything that has a __str__ method.  But in parts all Assets must be instances of Asset, so with other words this works:
Style(..., assets__bar=Fragment.link(...))

But this does not
Part(..., assets__bar=Fragment.link(...))

There are two ways to fix this (i.e. make both behave always the same):

Make classes other than Asset not work inside styles.  One could simply not do the collecting exercise of assets of styles but rely on the same side effect to populate them (the pushed change gets the change via both ways -- which of course is somewhat silly).

Make classes other than Asset work inside parts.  Todo that we would have to revert to something closer to the code I had originally pushed (aka walking the tree recursively and collecting all elements) (which presumably for big pages is slower than the side effects (because most children don't have any assets), but I never actually checked).

Thoughts?
Also my implementation will probably again show how I don't really understand tri_declarative.  But I'll start a review and make the appropriate comments

I added some tests, and I found out that the lazy=False was indeed needed. We need to force the evaluation since the assets are never looked for by the render traversal.

Hah I should trust myself more. Or write clearer  comments
On Tue, 27 Oct 2020 at 22:51, Johan Lübcke<EMAIL_ADDRESS>wrote:

I added some tests, and I found out that the lazy=False was indeed
needed. We need to force the evaluation since the assets are never looked
for by the render traversal.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/TriOptima/iommi/pull/83#issuecomment-717561396, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAHQUJOJFLIETZVMAFBOYTTSM46F7ANCNFSM4S6LWGVQ
.

I added two test for the style assets case while meditating over how to do this

Regarding that any Part works in Style(..., assets__foo=part) but only an Asset works in Part(..., assets__bar=asset) I think it will be tricky. I think it will not hurt a lot to require that it is an Asset.

I have cleaned up some more to be more "ideomatic"

Regarding that any Part works in Style(..., assets__foo=part) but only an Asset works in Part(..., assets__bar=asset) I think it will be tricky. I think it will not hurt a lot to require that it is an Asset.

Fair but I think in that case we should make it such that only assets work in Style as well.  That is this should still work:

StyleOrPart(..., assets__foo__template="my_template_file.html")

but this should no longer work

Style(..., assets__bar=Fragment.link(...))

Cause otherwise this is just a strange gotcha people will fall into.  I think that should be fairly easy if we just make the collection in the assets rely on the same side effect.  At least I think it should be easy but I no longer understand the code after you made it more "ideomatic".   I suspect that's because I don't understand Style.component ...
Anyhow here is a concrete question why does this still work after your cleanup?

Style(..., assets__foo__template="my_template_file.html")

In the old code that was easy there was an explicit turn Namespace into Asset(**...) in the code.  Now I suspect it's somewhere but I don't understand where.

The magic in why it works is that the Assets class is sent to collect_members as the default type to use when it ends up with just a bunch of config and not an instance.
And I agree that we should have the same requirements and error message in both the style and the explicit case.

The magic in why it works is that the Assets class is sent to collect_members as the default type to use when it ends up with just a bunch of config and not an instance.

I understand that is what happens in Part but how is that done for the assets of Style?

The magic line is line 99-100 in style.py where the style application just take the assets-namespace from all the styling and put it as assets-config on the root element. Then the root element will apply it via the _iommi_collected_assets dict like any other node in the tree. That's why I added an extra is_root argument to the style application to know when style was applied to the root.

Also, I think I fixed the any-type-of-asset problem. I realized that we could just move the move-the-assets-to-the-side-waiting-for-rendering to the parent of the Asset instead of the on_bind of assets.

That's much better.
Also thanks for the explanation.  I think the big thing that was not sufficiently in my head was that by the time the relevant part of Part.bind (no pun intended) is run the code in Traversable.bind will have applied the style.  Sigh I don't like OOP much.

Also, good feedback that in some cases "ideomatic" means less readable. Maybe we should have some kind of picture of how the data flows and what instances are created. (And also .component() is one of those things that need a docstring or three...)


Implement UTF-8 encode/decode

Fixes #2304

Current coverage is 81.46% (diff: 100%)

No coverage report found for master at 7d9c373.

Powered by Codecov. Last update 7d9c373...f1e97b6

Ping!


Publish ?

Time have passed since previous release, and I personaly need domainoption which is not on npm.

Hi @cyrilchapon, I've just published 1.0.0, which supports this option. Please let me know if this works for you.


Axi test harness

Thought it would be useful to open a draft PR to allow time to get feedback  while classes are starting and I'm less available. This is nearly done.
Pull request allows for runt testing of cocotb simulation which outputs the execution of a kernel based on examples/dahlia .data and .expected files.
Also introduces a subdirectory specifically for cocotb tests.
DRAFT: Regarding the reason this is a draft. Currently, running the make commands from runt does not behave the same way as running each command from a single shell one by one. Specifically, the Makefile does not use a new toplevel.v in spite of the -B flag. This means that a single computation (i.e dot-product) is performed on all data (i.e vectorized add data).
Additionally, make outputs some text which is specific to the file system running the command. For example, make outputs the commands it performs. Is there a way to selectively gather this text within runt? Just adding some tail and head commands to our output in the rust.toml?

Currently changing this to only test a single calyx program: vectorized-add. I think one test is better than no test, and runt behaves strangely when supplied more than one directory.
(It doesn't seem to fetch the correct toplevel, but will perform same computation on different input data, i.e dot product on vadd data).
Additionally, I am getting this weird unclosed file error which is polluting runt's expected output. As soon as that is fixed, this should be ready for deployment.

The unclosed file error is sadly expected. It is a problem with cocotb and they haven’t fixed it

hmm, runt should correctly work with multiple directories. Not sure why it’s failing to do thag

Can you try changing the runt command to cd into the directory and run make from there?

So (finally!) had some time to fix this! Apologies for taking so long. I believe the most recent push should fix the one-computation-kernel issue

@nathanielnrn seems like the tests are failing?

@nathanielnrn seems like the tests are failing?

Has to do with the AxBurst ports I added to make cocotb happy, probably should have made another branch for this. Updated runt gold files fixes this.

Hm, still seems to be failing

Looks like everything is passing @nathanielnrn! Merge when ready!

Latest commit makes the toplevel.v and main.sv we use for cocotb be dynamically generated as expected. However, the runt tests we have aren't passing due to differences in a newline here and lack of a new line there. I'm not able to reproduce failing cases on locally built docker containers.
Any thoughts from anyone by any chance? I'll keeping looking into it in the mean time.

Neat! Hella weird about the newline nonsense. I guess I suspect some vagary about the test's shell pipeline…
May I recommend using fud -v or whatever it is to get verbose output from Fud instead of that progress indicator thingy ⠋⠙?

Usually we use -q with fud in tests to make it stop producing any execution related output

Okay, my changes should fix the silly fud problem @nathanielnrn was running into. Once this is merged, we should check off tasks in #1104 and create a new issue to turn the cocotb hackery embedded in the runt commands into a fud stage so we can start running lots of different Calyx kernels with this harness

@nathanielnrn if you'd like, feel free to press the big green button! Congratulations on a successful summer research project!


Support parallelism is build

Signed-off-by: Julien Pivotto<EMAIL_ADDRESS>

I have tested this and it works.


Fix FMC image size for 2x displays

Updates the requested image size for Featured Menu Content images so that they're high-res on 2x displays.
Changes

Calls the original rendition for FMC images instead of width-270

Testing

Pull branch
Ensure you have an FMC image uploaded locally
Reload a page
Inspect the image and see that it's using the original 540x300 image, scaled down to 270x150

Checklist

[ ] PR has an informative and human-readable title
[ ] Changes are limited to a single goal (no scope creep)
[ ] Code can be automatically merged (no conflicts)
[ ] Code follows the standards laid out in the development playbook
[ ] Passes all existing automated tests
[ ] Any change in functionality is tested
[ ] New functions are documented (with a description, list of inputs, and expected output)
[ ] Placeholder code is flagged / future todos are captured in comments
[ ] Visually tested in supported browsers and devices (see checklist below :point_down:)
[ ] Project documentation has been updated
[ ] Reviewers requested with the Reviewers tool :arrow_right:

Seems to work like it says on the tin, but I was wondering where this was not already in effect, eg, it seems all the FMC images in the mega menu are already 540x300 displayed as 270x150

@wpears It's because Wagtail can generate alternate image sizes for uploaded images. The original 'width-270' (being replaced here) asks Wagtail for a "rendition" (in their parlance) of this image at 270px width. You aren't seeing that on the live site at this moment because the Wagtail-powered mega menu has been flipped off to address a different bug, so it's loading ye olde checked-in FMC images at their original size, rather than the images uploaded to Wagtail.


Provide an easier way to set aria-label

In order to be compliant with the WCAG guidelines, one should set a aria-label to the breadcrumb navigation, if there are more than one  element on the page. This is the case on most pages.
There is a workaround by appying the aria-label to the TagName of the BreadcrumbOptions like this:
o.TagName = "nav aria-label=\"Some description of the navigation\"";
An appropriate property would be a better way to handle this and should be fairly easy to implement.

I agree, there should be a way to do it that doesn't feel like a hack.
I'll try to find the time for it.

Added in 3.4!


Scan Docker images layer per layer

Description
This PR is part of the work to cache scanning of docker layers. It refactors docker scanning to do it layer per layer.
What has been done
The first 2 commits refactor the scanning code to run one scan per layer.
This worked but when SecretScanner reported skipped files using display_info() the output was messy as the message for the skipped files interfered with the progress bars:

This is because display_info() uses Click, but the progress bars are drawn by Rich. The solution to that is to make SecretScanner use Rich to print message while scanning. But SecretScanner should not need to know about the way its progress is reported, so I introduced an abstract class to represent its UI: SecretScannerUI, and wrote an implementation of it using Rich. This is what the 3 next commits do.
The scan now looks like this:

(The colored filenames are done automagically by Rich)
As a bonus, I added another commit to fix progress getting stuck at 100% for a while.

Codecov Report

Merging #508 (1a52dc0) into main (714ec41) will increase coverage by 0.02%.
The diff coverage is 97.59%.

:mega: This organization is not using Codecov’s GitHub App Integration. We recommend you install it so Codecov can continue to function properly for your repositories. Learn more
@@            Coverage Diff             @@
##             main     #508      +/-   ##
==========================================
+ Coverage   93.92%   93.95%   +0.02%
==========================================
  Files          79       80       +1
  Lines        3690     3722      +32
==========================================
+ Hits         3466     3497      +31
- Misses        224      225       +1

Flag
Coverage Δ

unittests
93.95% <97.59%> (+0.02%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

ggshield/cmd/secret/scan/docker.py
100.00% <ø> (ø)

ggshield/cmd/secret/scan/dockerarchive.py
100.00% <ø> (ø)

ggshield/cmd/secret/scan/docset.py
67.74% <ø> (ø)

ggshield/scan/scanner.py
93.84% <94.73%> (+0.22%)
:arrow_up:

ggshield/scan/docker.py
91.09% <97.43%> (+0.65%)
:arrow_up:

ggshield/cmd/secret/scan/archive.py
100.00% <100.00%> (ø)

ggshield/cmd/secret/scan/path.py
100.00% <100.00%> (ø)

ggshield/cmd/secret/scan/pypi.py
94.87% <100.00%> (-0.26%)
:arrow_down:

ggshield/scan/__init__.py
100.00% <100.00%> (ø)

ggshield/scan/rich_secret_scanner_ui.py
100.00% <100.00%> (ø)

... and 1 file with indirect coverage changes
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

@agateau-gg : I started having a look, note that some checks are failing (Lint + Windows).

@agateau-gg : I started having a look, note that some checks are failing (Lint + Windows).

Indeed. Just fixed the lint one. Looking at Windows right now.


How to speedup concurrent merge

Description
Hi, I have encountered a problem when using lucene in windows.
When I run IndexWriter.commit(), I may wait several minutes for doing background index merge.
The amount of data is about 20k+ items, not too much.
So what can I do to improve background index merging performance, aiming to reduce merge time?
Thanks for your advice.

What version are you using? Lucene 9.11 introduced concurrent merging to help speed up merging, see #13124.

When this is happening (you are waiting for merge) are you continuing to index new documents, or do you commit() and then during that time not submit any new docs (ie with IndexWriter.addDocuments or updateDocuments)?

When this is happening (you are waiting for merge) are you continuing to index new documents, or do you commit() and then during that time not submit any new docs (ie with IndexWriter.addDocuments or updateDocuments)?

Just wait for commit() to finish, not submit any new docs

What version are you using? Lucene 9.11 introduced concurrent merging to help speed up merging, see #13124.

Now I'm using 9.9.1 version, I'll check this 9.11 version, thanks

I see you closed the issue, yet I'm still curious - did upgrading to 9.11 fix the problem you saw?


Update modal.js example to properly handle the response

The $ionicModal constructor seems to return the new modal controller instance but the docs showed that it returned a promise. Using the example from the docs, you will get 'undefined is not a function'. This is an updated example code snippet that will work for people implementing $ionicModal.

fromTemplateUrl returns a promise: https://github.com/driftyco/ionic/blob/master/js/angular/service/modal.js#L303
fromTemplate returns the modal:
https://github.com/driftyco/ionic/blob/master/js/angular/service/modal.js#L283


Add EMD for Rare Phenomena at Colliders

Dear all,
Would it be possible to add our preprint to the IML paper list?
https://inspirehep.net/literature?sort=mostrecent&size=25&page=1&q=find eprint 2004.09360
Thanks a lot,
Nuno

Would it be possible to add our preprint to the IML paper list?

Sure, though I won't get to it until tomorrow. It will be faster for you to just open a PR.

Thanks a lot. I'm happy to do what is needed - but what you like me to do?

There are instructions in CONTRIBUTING.md: https://github.com/iml-wg/HEP-ML-Resources/blob/master/CONTRIBUTING.md#how-do-i-add-a-paper

thanks.
PR done: https://github.com/iml-wg/HEP-ML-Resources/pull/75


Customize Per Endpoint TLS Settings

Title: Feature Request, Customize Per Endpoint TLS config
Description:
Today Envoy each cluster has a single TLS configuration. We would like to be able to customize TLS config as per endpoint basis.
A potential solution could be extend the cluster filter, interface. At the time of a transport socket is about to be created, the cluster filter callbacks can be invoked, and return TLS configuration.
Welcome some other API/mechanism design as alternatives.
Use Case
With context of Istio, we are able to let control plane distribute label information to each endpoint(able to accept mTLS or not). Then client envoy, with this information, initiate TCP or TLS connection to different endpoints, decided as per endpoint level.
This eases the mTLS rollout a lot, customers don't have to configure the entire cluster TLS config. Instead they can get more and more mTLS traffic as more and more server side endpoints migrated with Envoy sidecar injected.

@PiotrSikora @rshriram @lizan
Welcome comments, thanks.

A proposal using cluster filter for this customization can be found here
Let me know if this is the right direction to proceed with some prototype, thanks!


⚠ Bofrost.de has degraded performance

In e7afa50, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 752 ms

Resolved: Bofrost.de performance has improved in b9b13a8 after 6 minutes.


FPS issue

Hi @TBSniller - I noticed a message on the UI that limiting FPS doesn't seem to work properly.
The usage text suggests that not setting the FPS argument results in an unlimited FPS cap but my Hyperion receives 15 FPS in this scenario.
Trying to set the FPS to 60 results in a small bump to 17 FPS.
Is the issue that the CPU in the TV is unable to process the Flat Buffers packets faster than 15 Hz? Is this functionality just not ready? Or is there likely something wrong with my Hyperion?
Thanks

Hey,
so limiting using PicCap has caused segmentation faults. Havent looked any deeper into it, thats why its not used also if set.
Setting it in CLI will cause it "working", but the FPS calculation in hyperion-webos isn't real, it may differ a few fps from what hyperiond will recieve.
The FPS flag is also only for limitting the FPS and not to set them. If you set it to unlimited, it will be as fast as your TV supports. Mine goes up to ~23 FPS with libvtcapture & halgal combined.
At the moment we are really really unoptimized, I think it will change when libdile_vt is ready to use. It seems like a promising alternative.

At the moment we are really really unoptimized, I think it will change when libdile_vt is ready to use. It seems like a promising alternative.

Is there anywhere to track the progress on this new/alternative library? I'm super keen to remove the usb grabber from my setup so I'd like to keep an eye on how this all progresses : smile

I think looking at JohnPauls work here https://github.com/webosbrew/hyperion-webos/pull/12 would be come a progressbar the nearst :)

How do you even check FPS? I want to check what I have on my CX, but there is no counter on both hyperion and piccap. No fps counter in hyperion with debug option or if I start hyperion-webos_libvtcapture from cli.

At the moment its not possible to check the FPS directly in libvtcapture. Gave up after few hours trying to get the really real FPS.
You can try to get the FPS out of hyperiond. Otherwise you can edit the hyperion-webos source to output it to a MJPEG-Stream and get the FPS from ffmpeg. Notice that this FPS will differ, but you will get a idea how much it is.

How do you even check FPS? I want to check what I have on my CX, but there is no counter on both hyperion and piccap. No fps counter in hyperion with debug option or if I start hyperion-webos_libvtcapture from cli.

I can check the received FPS in 2 ways:

HyperHDR shows the FPS in the logs
WLED can display the received FPS

If you can't use any of these then you'll probably have to do as @TBSniller suggested

WLED can display the received FPS

WLED report something unreliable, most of the time ~26fps, sometimes 300+fps

HyperHDR shows the FPS in the logs

In custom build probably? As there is nothing about fps in logs.
But I can confirm @tavalin observation: when you set fps limit with -f flag, it gives you a few extra fps. Hyperion preview looks smoother. Also doesn't matter what number you put there: with -f 1 it works as fast as with -f 60 and it's better than without -f
Latency also lower by ~50ms with -f flag set

I think looking at JohnPauls work here webosbrew/hyperion-webos#12 would be come a progressbar the nearst :)

Are there any instructions on how to compile this? Would be keen to test the PR

You can get prebuilt binaries in summary of most pushed commits CI build: https://github.com/webosbrew/hyperion-webos/actions/runs/1570119948

Solved via unicapture branch.


Debugger silently fails to connect to target process on Arch

Issue Description
Breakpoints do not work when running either a console or web application...most of the time.
On occasion, it will randomly begin running correctly. Even when stopping and immediately starting the project again.
Steps to Reproduce
dotnet new console
// set breakpoint
// debug project

or
dotnet new mvc
// set breakpoint in controller
// debug project

Expected Behavior
Program to stop execution on breakpoints selected
Actual Behavior
console -> Program runs to end of execution (this was a new console project)
mvc -> Breakpoint is grayed out and never hit
// hovering over the grayed out breakpoint gives the message: 'The breakpoint is pending and will be resolved when debugging starts.'
Logs
NOTE: These logs were from running a new mvc project
OmniSharp log
Starting OmniSharp server at 5/11/2020, 8:34:56 AM
Target: /[path]/[to]/[project]/demo
OmniSharp server started with Mono 6.4.0.
Path: /home/[user]/.vscode/extensions/ms-dotnettools.csharp-1.21.18/.omnisharp/1.35.1/omnisharp/OmniSharp.exe
PID: 4375
    Starting OmniSharp on arch 0.0 (x64)

    DotNetPath set to dotnet

    It looks like you have Mono 6.4.0 or greater installed but MSBuild could not be found.

Try installing MSBuild into Mono (e.g. 'sudo apt-get install msbuild') to enable better MSBuild support, or upgrade to latest Mono: https://www.mono-project.com/download/stable/.
info: OmniSharp.MSBuild.Discovery.MSBuildLocator
Located 1 MSBuild instance(s)
1: StandAlone 16.4 - "/home/[user]/.vscode/extensions/ms-dotnettools.csharp-1.21.18/.omnisharp/1.35.1/omnisharp/.msbuild/Current/Bin"
info: OmniSharp.MSBuild.Discovery.MSBuildLocator
MSBUILD_EXE_PATH environment variable set to '/home/[user]/.vscode/extensions/ms-dotnettools.csharp-1.21.18/.omnisharp/1.35.1/omnisharp/.msbuild/Current/Bin/MSBuild.dll'
info: OmniSharp.MSBuild.Discovery.MSBuildLocator
Registered MSBuild instance: StandAlone 16.4 - "/home/[user]/.vscode/extensions/ms-dotnettools.csharp-1.21.18/.omnisharp/1.35.1/omnisharp/.msbuild/Current/Bin"
CscToolExe = csc.exe
MSBuildToolsPath = /home/[user]/.vscode/extensions/ms-dotnettools.csharp-1.21.18/.omnisharp/1.35.1/omnisharp/.msbuild/Current/Bin
CscToolPath = /home/[user]/.vscode/extensions/ms-dotnettools.csharp-1.21.18/.omnisharp/1.35.1/omnisharp/.msbuild/Current/Bin/Roslyn
BypassFrameworkInstallChecks = true
MSBuildExtensionsPath = /home/[user]/.vscode/extensions/ms-dotnettools.csharp-1.21.18/.omnisharp/1.35.1/omnisharp/.msbuild
info: OmniSharp.Cake.CakeProjectSystem
Detecting Cake files in '/[path]/[to]/[project]/demo'.
info: OmniSharp.Cake.CakeProjectSystem
Could not find any Cake files
info: OmniSharp.MSBuild.ProjectSystem
No solution files found in '/[path]/[to]/[project]/demo'
info: OmniSharp.MSBuild.ProjectManager
Queue project update for '/[path]/[to]/[project]/demo/demo.csproj'
info: OmniSharp.Script.ScriptProjectSystem
Detecting CSX files in '/[path]/[to]/[project]/demo'.
info: OmniSharp.Script.ScriptProjectSystem
Could not find any CSX files
info: OmniSharp.WorkspaceInitializer
Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.CSharpFormattingWorkspaceOptionsProvider, Order: 0
info: OmniSharp.WorkspaceInitializer
Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.RenameWorkspaceOptionsProvider, Order: 100
info: OmniSharp.WorkspaceInitializer
Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.ImplementTypeWorkspaceOptionsProvider, Order: 110
info: OmniSharp.WorkspaceInitializer
Invoking Workspace Options Provider: OmniSharp.Roslyn.CSharp.Services.BlockStructureWorkspaceOptionsProvider, Order: 140
info: OmniSharp.MSBuild.ProjectManager
Loading project: /[path]/[to]/[project]/demo/demo.csproj
info: OmniSharp.WorkspaceInitializer
Configuration finished.
info: OmniSharp.Stdio.Host
Omnisharp server running using Stdio at location '/[path]/[to]/[project]/demo' on host 4176.
info: OmniSharp.MSBuild.ProjectManager
Successfully loaded project file '/[path]/[to]/[project]/demo/demo.csproj'.
info: OmniSharp.MSBuild.ProjectManager
Adding project '/[path]/[to]/[project]/demo/demo.csproj'
info: OmniSharp.MSBuild.ProjectManager
Update project: demo
C# log
(no output)
Environment information
VSCode version: 1.45.0
C# Extension: 1.21.18
Mono Information
        OmniSharp using global mono :6.4.0
Dotnet Information
.NET Core SDK (reflecting any global.json):
 Version:   3.1.103
 Commit:    6f74c4a1dd
Runtime Environment:
OS Name:     arch
OS Version:
OS Platform: Linux
RID:         arch-x64
Base Path:   /usr/share/dotnet/sdk/3.1.103/
Host (useful for support):
Version: 3.1.3
Commit:  ed88943d24
.NET Core SDKs installed:
3.1.103 [/usr/share/dotnet/sdk]
.NET Core runtimes installed:
Microsoft.AspNetCore.App 3.1.3 [/usr/share/dotnet/shared/Microsoft.AspNetCore.App]
Microsoft.NETCore.App 3.1.3 [/usr/share/dotnet/shared/Microsoft.NETCore.App]
To install additional .NET Core runtimes or SDKs:
https://aka.ms/dotnet-download

Visual Studio Code Extensions

Extension
Author
Version

asp-net-core-vs-code-extension-pack
temilaj
1.0.3

aspnet-helper
schneiderpat
0.6.4

cpptools
ms-vscode
0.27.1

csharp
ms-dotnettools
1.21.18

Csharp-ASPNETCore
rahulsahay
1.11.0

csharpextensions
jchannon
1.3.1

docomment
k--kato
0.1.9

dotnet-test-explorer
formulahendry
0.7.1

gc-excelviewer
GrapeCity
2.1.34

java
redhat
0.61.0

mssql
ms-mssql
1.9.0

python
ms-python
2020.4.76186

razor-plus
austincummings
0.1.4

remote-containers
ms-vscode-remote
0.117.0

vsc-community-material-theme
Equinusocio
1.4.1

vsc-material-theme
Equinusocio
32.6.0

vsc-material-theme-icons
equinusocio
1.1.4

vscode-docker
ms-azuretools
1.1.0

vscode-java-debug
vscjava
0.25.1

vscode-java-dependency
vscjava
0.10.0

vscode-java-pack
vscjava
0.9.0

vscode-java-test
vscjava
0.22.3

vscode-maven
vscjava
0.21.3

vscode-typescript-tslint-plugin
ms-vscode
1.2.3

vscodeintellicode
VisualStudioExptTeam
1.2.7

vsliveshare
ms-vsliveshare
1.0.2106

I realize this is similar to issue #3773. There are differences:

The breakpoints do not work
There seems to be no error given

Also did try this: https://github.com/OmniSharp/omnisharp-vscode/wiki/Enabling-C%23-debugger-logging#full-method
Here's the output:
-> (C) {"command":"initialize","arguments":{"clientID":"vscode","clientName":"Visual Studio Code","adapterID":"coreclr","pathFormat":"path","linesStartAt1":true,"columnsStartAt1":true,"supportsVariableType":true,"supportsVariablePaging":true,"supportsRunInTerminalRequest":true,"locale":"en-us","supportsProgressReporting":true},"type":"request","seq":1}
<- (R) {"seq":1,"type":"response","request_seq":1,"success":true,"command":"initialize","message":"","body":{"supportsConfigurationDoneRequest":true,"supportsFunctionBreakpoints":false,"supportsConditionalBreakpoints":true,"supportsHitConditionalBreakpoints":true,"supportsEvaluateForHovers":true,"exceptionBreakpointFilters":[{"filter":"all","label":"All Exceptions","default":false},{"filter":"user-unhandled","label":"User-Unhandled Exceptions","default":true}],"supportsSetVariable":true,"supportsGotoTargetsRequest":true,"supportsModulesRequest":true,"additionalModuleColumns":[],"supportedChecksumAlgorithms":["MD5","SHA1","SHA256"],"supportsExceptionOptions":true,"supportsValueFormattingOptions":true,"supportsExceptionInfoRequest":true,"supportTerminateDebuggee":true,"supportsSetExpression":true,"supportsReadMemoryRequest":true,"supportsExceptionConditions":true,"supportsLoadSymbolsRequest":true,"supportsModuleSymbolSearchLog":true,"supportsDebuggerProperties":true,"supportsSetSymbolOptions":true}}
-> (C) {"command":"initialize","arguments":{"clientID":"vscode","clientName":"Visual Studio Code","adapterID":"coreclr","pathFormat":"path","linesStartAt1":true,"columnsStartAt1":true,"supportsVariableType":true,"supportsVariablePaging":true,"supportsRunInTerminalRequest":true,"locale":"en-us","supportsProgressReporting":true},"type":"request","seq":1}
<- (R) {"seq":4,"type":"response","request_seq":1,"success":true,"command":"initialize","message":"","body":{"supportsConfigurationDoneRequest":true,"supportsFunctionBreakpoints":false,"supportsConditionalBreakpoints":true,"supportsHitConditionalBreakpoints":true,"supportsEvaluateForHovers":true,"exceptionBreakpointFilters":[{"filter":"all","label":"All Exceptions","default":false},{"filter":"user-unhandled","label":"User-Unhandled Exceptions","default":true}],"supportsSetVariable":true,"supportsGotoTargetsRequest":true,"supportsModulesRequest":true,"additionalModuleColumns":[],"supportedChecksumAlgorithms":["MD5","SHA1","SHA256"],"supportsExceptionOptions":true,"supportsValueFormattingOptions":true,"supportsExceptionInfoRequest":true,"supportTerminateDebuggee":true,"supportsSetExpression":true,"supportsReadMemoryRequest":true,"supportsExceptionConditions":true,"supportsLoadSymbolsRequest":true,"supportsModuleSymbolSearchLog":true,"supportsDebuggerProperties":true,"supportsSetSymbolOptions":true}}
-> (C) {"command":"launch","arguments":{"name":".NET Core Launch (web)","type":"coreclr","request":"launch","preLaunchTask":"build","program":"/[path]/[to]/[project]/demo/bin/Debug/netcoreapp3.1/demo.dll","args":[],"cwd":"/[path]/[to]/[project]/demo","stopAtEntry":false,"serverReadyAction":{"action":"openExternally","pattern":"^\s*Now listening on:\s+(https?://\S+)"},"env":{"ASPNETCORE_ENVIRONMENT":"Development","ASPNETCORE_URLS":"https://localhost:5001;http://localhost:5000"},"sourceFileMap":{"/Views":"/[path]/[to]/[project]/demo/Views"},"logging":{"engineLogging":false},"debugServer":4711,"noDebug":true,"internalConsoleOptions":"openOnSessionStart","__sessionId":"178c63ed-f3f3-49df-b5ee-1f1f92221172"},"type":"request","seq":2}
-> (C) {"seq":7,"type":"request","command":"handshake","arguments":{"value":"1wnOLCxVzYltSow7yPp8gXLiSMgWFPQDZ83+w2PqBn0="}}

You may only use the Microsoft .NET Core Debugger (vsdbg) with
Visual Studio Code, Visual Studio or Visual Studio for Mac software
to help you develop and test your applications.

The "noDebug":true kinda has me wondering.

@bDarbonne Is that the end of your debug log? It is strangely truncated, maybe because vsdbg-ui crashed? You might get more info using the 'full method'.

Hi All,  I have the same issue.  Here is my debug log using the "full method" described here: [https://github.com/OmniSharp/omnisharp-vscode/wiki/Enabling-C%23-debugger-logging#full-method]. Is there any workaround for this?
Waiting for communication on port 4711...

accepted connection from client
-> (C) {"command":"initialize","arguments":{"clientID":"vscode","clientName":"Code - OSS","adapterID":"coreclr","pathFormat":"path","linesStartAt1":true,"columnsStartAt1":true,"supportsVariableType":true,"supportsVariablePaging":true,"supportsRunInTerminalRequest":true,"locale":"en-gb","supportsProgressReporting":true},"type":"request","seq":1}
<- (R) {"seq":0,"type":"response","request_seq":1,"success":true,"command":"initialize","message":"","body":{"supportsConfigurationDoneRequest":true,"supportsFunctionBreakpoints":false,"supportsConditionalBreakpoints":true,"supportsHitConditionalBreakpoints":true,"supportsEvaluateForHovers":true,"exceptionBreakpointFilters":[{"filter":"all","label":"All Exceptions","default":false},{"filter":"user-unhandled","label":"User-Unhandled Exceptions","default":true}],"supportsSetVariable":true,"supportsGotoTargetsRequest":true,"supportsModulesRequest":true,"additionalModuleColumns":[],"supportedChecksumAlgorithms":["MD5","SHA1","SHA256"],"supportsExceptionOptions":true,"supportsValueFormattingOptions":true,"supportsExceptionInfoRequest":true,"supportTerminateDebuggee":true,"supportsSetExpression":true,"supportsReadMemoryRequest":true,"supportsExceptionConditions":true,"supportsLoadSymbolsRequest":true,"supportsModuleSymbolSearchLog":true,"supportsDebuggerProperties":true,"supportsSetSymbolOptions":true}}
-> (C) {"command":"initialize","arguments":{"clientID":"vscode","clientName":"Code - OSS","adapterID":"coreclr","pathFormat":"path","linesStartAt1":true,"columnsStartAt1":true,"supportsVariableType":true,"supportsVariablePaging":true,"supportsRunInTerminalRequest":true,"locale":"en-gb","supportsProgressReporting":true},"type":"request","seq":1}
-> (C) {"command":"launch","arguments":{"name":".NET Core Launch (console)","type":"coreclr","request":"launch","preLaunchTask":"build","program":"/home/pauls/Dev/sandbox/c#/ConsoleApp/bin/Debug/netcoreapp3.1/ConsoleApp.dll","args":[],"cwd":"/home/pauls/Dev/sandbox/c#/ConsoleApp","logging":{"engineLogging":false},"console":"internalConsole","stopAtEntry":false,"debugServer":4711,"internalConsoleOptions":"openOnSessionStart","__sessionId":"eaa62012-7144-40b7-9bb0-bf86654dfc1c"},"type":"request","seq":2}
<- (E) {"seq":3,"type":"event","event":"output","body":{"category":"console","output":"-------------------------------------------------------------------\nYou may only use the Microsoft .NET Core Debugger (vsdbg) with\nVisual Studio Code, Visual Studio or Visual Studio for Mac software\nto help you develop and test your applications.\n-------------------------------------------------------------------\n"}}
<- (R) {"seq":4,"type":"response","request_seq":2,"success":true,"command":"launch"}
<- (E) {"seq":5,"type":"event","event":"output","body":{"category":"telemetry","output":"VS/Diagnostics/Debugger/vsdbg/CommandFailed","data":{"VS.Diagnostics.Debugger.vsdbg.AdapterId":"coreclr","VS.Diagnostics.Debugger.vsdbg.ErrorCode":-1989017584,"VS.Diagnostics.Debugger.vsdbg.Distribution.Name":"d241e93b","VS.Diagnostics.Debugger.vsdbg.Command":"handshake","VS.Diagnostics.Debugger.vsdbg.OSFamily":"Linux","VS.Diagnostics.Debugger.vsdbg.Version":"16.6.20415.1 commit:0184bb70e1ed40656c0dfa53125805036207007b"}}}
<- (R) {"seq":6,"type":"response","request_seq":1,"success":false,"command":"handshake","message":"Error processing 'handshake' request. Unknown Error: 0x89720010"}

@paulsebeikin: your issue is actually different. Your problem is that you installed the OSS version of Visual Studio Code, but the debugger is only licensed to work in official Microsoft products. Unfortunately due to both a bug in the debugger, and a bug in VS Code, that error message doesn't come up. You can fix the issue by installing the official version of VS Code from Microsoft. More info: https://github.com/OmniSharp/omnisharp-vscode/wiki/Microsoft-.NET-Core-Debugger-licensing-and-Microsoft-Visual-Studio-Code

Can confirm that OSS version of vscode doesn't work with C# debugger.
Microsoft version of vscode works fine.
Tested with visual-studio-code-bin package from AUR.

@gregg-miskelly Yes. That's the end of the debug log. The output was actually from ./vsdbg-ui --server --engineLogging.
Here is the output from ./vsdbg-ui --server --consoleLogging:
Waiting for communication on port 4711...

accepted connection from client
-> (C) {"command":"initialize","arguments":{"clientID":"vscode","clientName":"Visual Studio Code","adapterID":"coreclr","pathFormat":"path","linesStartAt1":true,"columnsStartAt1":true,"supportsVariableType":true,"supportsVariablePaging":true,"supportsRunInTerminalRequest":true,"locale":"en-us","supportsProgressReporting":true},"type":"request","seq":1}
<- (R) {"seq":0,"type":"response","request_seq":1,"success":true,"command":"initialize","message":"","body":{"supportsConfigurationDoneRequest":true,"supportsFunctionBreakpoints":false,"supportsConditionalBreakpoints":true,"supportsHitConditionalBreakpoints":true,"supportsEvaluateForHovers":true,"exceptionBreakpointFilters":[{"filter":"all","label":"All Exceptions","default":false},{"filter":"user-unhandled","label":"User-Unhandled Exceptions","default":true}],"supportsSetVariable":true,"supportsGotoTargetsRequest":true,"supportsModulesRequest":true,"additionalModuleColumns":[],"supportedChecksumAlgorithms":["MD5","SHA1","SHA256"],"supportsExceptionOptions":true,"supportsValueFormattingOptions":true,"supportsExceptionInfoRequest":true,"supportTerminateDebuggee":true,"supportsSetExpression":true,"supportsReadMemoryRequest":true,"supportsExceptionConditions":true,"supportsLoadSymbolsRequest":true,"supportsModuleSymbolSearchLog":true,"supportsDebuggerProperties":true,"supportsSetSymbolOptions":true}}
-> (C) {"command":"initialize","arguments":{"clientID":"vscode","clientName":"Visual Studio Code","adapterID":"coreclr","pathFormat":"path","linesStartAt1":true,"columnsStartAt1":true,"supportsVariableType":true,"supportsVariablePaging":true,"supportsRunInTerminalRequest":true,"locale":"en-us","supportsProgressReporting":true},"type":"request","seq":1}
-> (C) {"command":"launch","arguments":{"name":"launch - manual debugger","type":"coreclr","request":"launch","preLaunchTask":"build","program":"/[path]/[to]/[project]/demo/bin/Debug/netcoreapp3.1/demo.dll","args":[],"cwd":"/[path]/[to]/[project]/demo","stopAtEntry":false,"serverReadyAction":{"action":"openExternally","pattern":"^\s*Now listening on:\s+(https?://\S+)"},"env":{"ASPNETCORE_ENVIRONMENT":"Development","ASPNETCORE_URLS":"https://localhost:5001;http://localhost:5000"},"sourceFileMap":{"/Views":"/[path]/[to]/[project]/demo/Views"},"logging":{"engineLogging":false},"debugServer":4711,"noDebug":true,"internalConsoleOptions":"openOnSessionStart","__sessionId":"a0c1eaaa-122d-4ab3-890c-44887b05b377"},"type":"request","seq":2}
<- (E) {"seq":3,"type":"event","event":"output","body":{"category":"console","output":"-------------------------------------------------------------------\nYou may only use the Microsoft .NET Core Debugger (vsdbg) with\nVisual Studio Code, Visual Studio or Visual Studio for Mac software\nto help you develop and test your applications.\n-------------------------------------------------------------------\n"}}
<- (R) {"seq":4,"type":"response","request_seq":2,"success":true,"command":"launch"}
<- (E) {"seq":5,"type":"event","event":"initialized","body":{}}
-> (C) {"command":"setBreakpoints","arguments":{"source":{"name":"HomeController.cs","path":"/[path]/[to]/[project]/demo/Controllers/HomeController.cs","checksums":[{"algorithm":"SHA1","checksum":"499f334cbbd92ca9d80169f2b828b50f0ad45432"},{"algorithm":"SHA256","checksum":"2116510a12be6daa6c6d779aa1a699461464f26e63b78f8c1a39af300dcc0546"},{"algorithm":"SHA1","checksum":"e99e2cbf015da6e56326de2deebebbd8062d639a"},{"algorithm":"SHA256","checksum":"923c5ae532d651f687631e2b3c159e3e2a1be124f337721f45f8398b6520f296"}]},"lines":[17],"breakpoints":[{"line":17}],"sourceModified":false},"type":"request","seq":3}
<- (R) {"seq":6,"type":"response","request_seq":3,"success":true,"command":"setBreakpoints","message":"","body":{"breakpoints":[{"id":1,"verified":false,"message":"The breakpoint is pending and will be resolved when debugging starts.","line":17}]}}
-> (C) {"command":"setExceptionBreakpoints","arguments":{"filters":["user-unhandled"]},"type":"request","seq":4}
<- (R) {"seq":7,"type":"response","request_seq":4,"success":true,"command":"setExceptionBreakpoints"}
-> (C) {"command":"configurationDone","type":"request","seq":5}
<- (E) {"seq":8,"type":"event","event":"process","body":{"name":"/[path]/[to]/[project]/demo/bin/Debug/netcoreapp3.1/demo.dll","systemProcessId":4951,"isLocalProcess":true,"startMethod":null}}
<- (E) {"seq":9,"type":"event","event":"output","body":{"category":"telemetry","output":"VS/Diagnostics/Debugger/vsdbg/Launch","data":{"VS.Diagnostics.Debugger.vsdbg.AdapterId":"coreclr","VS.Diagnostics.Debugger.vsdbg.SourceFileMappings":1,"VS.Diagnostics.Debugger.vsdbg.VisualizerFileUsed":false,"VS.Diagnostics.Debugger.vsdbg.Launch.Duration":140,"VS.Diagnostics.Debugger.vsdbg.Distribution.Name":"arch","VS.Diagnostics.Debugger.vsdbg.TargetType":"Live","VS.Diagnostics.Debugger.vsdbg.OSFamily":"Linux","VS.Diagnostics.Debugger.vsdbg.Version":"16.6.20415.1 commit:0184bb70e1ed40656c0dfa53125805036207007b"}}}
<- (R) {"seq":10,"type":"response","request_seq":5,"success":true,"command":"configurationDone"}
-> (C) {"command":"threads","type":"request","seq":6}
<- (E) {"seq":11,"type":"event","event":"output","body":{"category":"telemetry","output":"VS/Diagnostics/Debugger/vsdbg/CommandFailed","data":{"VS.Diagnostics.Debugger.vsdbg.AdapterId":"coreclr","VS.Diagnostics.Debugger.vsdbg.ErrorCode":-2147019873,"VS.Diagnostics.Debugger.vsdbg.Distribution.Name":"arch","VS.Diagnostics.Debugger.vsdbg.Command":"threads","VS.Diagnostics.Debugger.vsdbg.OSFamily":"Linux","VS.Diagnostics.Debugger.vsdbg.Version":"16.6.20415.1 commit:0184bb70e1ed40656c0dfa53125805036207007b"}}}
<- (R) {"seq":12,"type":"response","request_seq":6,"success":false,"command":"threads","message":"Error processing 'threads' request. Unknown Error: 0x8007139f"}
<- (E) {"seq":13,"type":"event","event":"output","body":{"category":"stdout","output":"\u001B[40m\u001B[32minfo\u001B[39m\u001B[22m\u001B[49m: Microsoft.Hosting.Lifetime[0]\n"}}
<- (E) {"seq":14,"type":"event","event":"output","body":{"category":"stdout","output":"      Now listening on: https://localhost:5001\n"}}
<- (E) {"seq":15,"type":"event","event":"output","body":{"category":"stdout","output":"\u001B[40m\u001B[32minfo\u001B[39m\u001B[22m\u001B[49m: Microsoft.Hosting.Lifetime[0]\n"}}
<- (E) {"seq":16,"type":"event","event":"output","body":{"category":"stdout","output":"      Now listening on: http://localhost:5000\n"}}
<- (E) {"seq":17,"type":"event","event":"output","body":{"category":"stdout","output":"\u001B[40m\u001B[32minfo\u001B[39m\u001B[22m\u001B[49m: Microsoft.Hosting.Lifetime[0]\n"}}
<- (E) {"seq":18,"type":"event","event":"output","body":{"category":"stdout","output":"      Application started. Press Ctrl+C to shut down.\n"}}
<- (E) {"seq":19,"type":"event","event":"output","body":{"category":"stdout","output":"\u001B[40m\u001B[32minfo\u001B[39m\u001B[22m\u001B[49m: Microsoft.Hosting.Lifetime[0]\n"}}
<- (E) {"seq":20,"type":"event","event":"output","body":{"category":"stdout","output":"      Hosting environment: Development\n"}}
<- (E) {"seq":21,"type":"event","event":"output","body":{"category":"stdout","output":"\u001B[40m\u001B[32minfo\u001B[39m\u001B[22m\u001B[49m: Microsoft.Hosting.Lifetime[0]\n"}}
<- (E) {"seq":22,"type":"event","event":"output","body":{"category":"stdout","output":"      Content root path: /[path]/[to]/[project]/demo\n"}}

Is this what you were referring to as the 'full method'?

Thanks. That makes way more sense. What I believe is going on is that inter process communications between the .NET Debugging services (which run in the debugger process) and the .NET Runtime (which runs in your app) is silently failing. So the result is that the debugger is never told that the .NET Runtime loaded, and nothing will work.
Unfortunately, since the failure is silent, there is nothing in the log to explain what is going on. One thing you could try -- try attaching to an already running process, and see if we get an error that way. You will probably need to check the logs as VS Code has a bug (that was just fixed in Insiders) where they weren't displaying errors from the configurationDone request.

Ok. I ran the project and attached to the process to begin debugging. Here's what I have:
output.txt

Interesting. So in case it isn't obvious what happened there: everything worked just fine when you attached.
This means either:

Somehow the debugger is debugging the wrong process in the 'launch' case.
-or-
The IPC for raising the 'runtime loaded' event is broken, but all the other IPC is working fine.

To try and differentiate the two, if you look at a trace when you do the launch, you will see a process event like the following, which indicates the process the debugger is attached to:
{"seq":8,"type":"event","event":"process","body":{"name":"/[path]/[to]/[project]/demo/bin/Debug/netcoreapp3.1/demo.dll","systemProcessId":4951,"isLocalProcess":true,"startMethod":null}}

Does the process id reported from that event match the process where your code is loaded?

The process id does match.

Hmm... unfortunately the .NET Runtime code isn't the easiest to troubleshoot. If you feel up for it, I can tell you what repo to build, .so to patch and where you could set breakpoints to try and figure this out.

Sure!

Okay, so here is the interesting code that gets loaded into the debugger's process: libdbgshim.so!PAL_RuntimeStartupHelper::Register
If you want to debug into this, you should be able to by:

git clone https://github.com/dotnet/coreclr.git <insert-dest-dir-here> -b release/3.1
cd to your enlistment
build.sh skiptests skipmscorlib skipbuildpackages (I am figuring out this from memory and looking at the usage, so you may need to tweak this)

And then copy the libdbgshim.so that you built into the C# extension's debugger directory.  Now you can launch vsdbg-ui under a native debugger (ex: use the VS Code C++ extension, or GDB by hand) in server mode (the same thing you did for logging) and be able to debug things.
After the target process starts, it should attempt to open that semaphore and signal it. Debugging that code is a bit harder. But if you want to read it look at PAL_NotifyRuntimeStarted. That code will be in libcoreclr.so.

thanks @gregg-miskelly your advice resolved my issue.

Thank you @gregg-miskelly! Funny thing happened. I followed your instructions. Ran the project with ./vsdbg-ui --server --consoleLogging one final time (with the generated libdbgshim.so) before trying to debug as suggested... The breakpoints work now. Decided to swap out the .so file for the original just for kicks and giggles. It's working just fine.


Links in messages

Juggernaut should detect links in messages and present a clickable option to visit the site. Well, I guess there are some security implications also when any stranger on the lightning network can send you links, so maybe should we handle that somehow, either by disabling links from untrusted contacts or adding an option in the future settings menu?
What about link previews?

Yeah, I think parsing out links and presenting them as actual clickable links is a good idea.
Link previews are kind of a problem potentially because without a third party server the message passes through to generate the preview it means the client will have to automatically ping the url and generate the preview.  People might not to want to automatically 'click' links like that.
Another alternative would be that the sender actually generates the preview and sends it as part of their message but this might be problematic because there's a message size limit we'd likely run into.


Micropolis: Add missing HCS order for VGI

Merged, thanks (also, if you have a known good flux image and VGI file for a blank Micropolis disk, it can be added to https://github.com/davidgiven/fluxengine-testdata to check for further regressions).


Remove setIsOptedOut method and added disableTracking and enableTracking

Added enableTracking & disableTracking methods to opt In or opt out tracking. Replacement of setIsOptedOut method.
Updated readme.


History need restore features

Is your feature request related to a problem?
No response
Describe the solution you'd like
add a button to restore history
Describe alternatives you've considered
none
Additional context
No response

@crete555 UI/UX design support required, thanks.

@mashcard/designers

@Brickdoctor @ziyanchen327 @zaotang We need design support here.

add simple restore button at #496, not final design, does not mean this is complete.


[Refactor] Adjust stream load planner timeout reduce the db lock timeout error (#18992)

Signed-off-by: meegoo<EMAIL_ADDRESS>(cherry picked from commit f0195f56db63271858fdaefeec3fb46b179fcc27)
What type of PR is this：

[ ] BugFix
[ ] Feature
[ ] Enhancement
[ ] Refactor
[ ] UT
[ ] Doc
[ ] Tool

Which issues of this PR fixes ：

Fixes #
Problem Summary(Required) ：

Checklist:

[ ] I have added test cases for my bug fix or my new feature
[ ] This pr will affect users' behaviors
[ ] This pr needs user documentation (for new or modified features or behaviors)

[ ] I have added documentation for my new feature or new function

Bugfix cherry-pick branch check:

[ ] I have checked the version labels which the pr will be auto backported to target branch

[ ] 3.0
[ ] 2.5
[ ] 2.4
[ ] 2.3

run all

@rebase

@mergify rebase

@mergify rebase

@Mergify rebase


failed to pull and unpack image "registry.redhat.io/rhel8/python-39:1-120.1684740828": failed to resolve reference "registry.redhat.io/rhel8/python-39:1-120.1684740828": failed to authorize: failed to fetch anonymous token

Issue
The cronjob image-controller fails to download the image as the image requires to be authenticated with the registry: registry.redhat.io/.
Is it possible to use a public registry for konflux upstream ?
[snowdrop@charles-vm ~]$ k describe pod/image-controller-image-pruner-cronjob-28825920-5ttph -n image-controller
Name:             image-controller-image-pruner-cronjob-28825920-5ttph
Namespace:        image-controller
Priority:         0
Service Account:  default
Node:             konflux-control-plane/<IP_ADDRESS>
Start Time:       Tue, 22 Oct 2024 10:10:50 +0000
Labels:           batch.kubernetes.io/controller-uid=b8452e67-1b5f-4586-a679-f6a0e4e055c0
                  batch.kubernetes.io/job-name=image-controller-image-pruner-cronjob-28825920
                  controller-uid=b8452e67-1b5f-4586-a679-f6a0e4e055c0
                  job-name=image-controller-image-pruner-cronjob-28825920
Annotations:      <none>
Status:           Pending
IP:               <IP_ADDRESS>
IPs:
  IP:           <IP_ADDRESS>
Controlled By:  Job/image-controller-image-pruner-cronjob-28825920
Containers:
  image-pruner:
    Container ID:
    Image:         registry.redhat.io/rhel8/python-39:1-120.1684740828
    Image ID:
    Port:          <none>
    Host Port:     <none>
    Command:
      /bin/bash
      -c
      python /image-pruner/prune_images.py --namespace $(NAMESPACE)
    State:          Waiting
      Reason:       ImagePullBackOff
    Ready:          False
    Restart Count:  0
    Limits:
      cpu:     500m
      memory:  512Mi
    Requests:
      cpu:     150m
      memory:  128Mi
    Environment:
      QUAY_TOKEN:  <set to the key 'quaytoken' in secret 'quaytoken'>     Optional: false
      NAMESPACE:   <set to the key 'organization' in secret 'quaytoken'>  Optional: false
    Mounts:
      /image-pruner from image-pruner-volume (rw)
      /var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-gbf4w (ro)
Conditions:
  Type                        Status
  PodReadyToStartContainers   True
  Initialized                 True
  Ready                       False
  ContainersReady             False
  PodScheduled                True
Volumes:
  image-pruner-volume:
    Type:      ConfigMap (a volume populated by a ConfigMap)
    Name:      image-controller-image-pruner-configmap-cbd96747df
    Optional:  false
  quaytoken:
    Type:        Secret (a volume populated by a Secret)
    SecretName:  quaytoken
    Optional:    false
  kube-api-access-gbf4w:
    Type:                    Projected (a volume that contains injected data from multiple sources)
    TokenExpirationSeconds:  3607
    ConfigMapName:           kube-root-ca.crt
    ConfigMapOptional:       <nil>
    DownwardAPI:             true
QoS Class:                   Burstable
Node-Selectors:              <none>
Tolerations:                 node.kubernetes.io/not-ready:NoExecute op=Exists for 300s
                             node.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:
  Type     Reason     Age                   From               Message
  ----     ------     ----                  ----               -------
  Normal   Scheduled  3m39s                 default-scheduler  Successfully assigned image-controller/image-controller-image-pruner-cronjob-28825920-5ttph to konflux-control-plane
  Normal   Pulling    2m7s (x4 over 3m39s)  kubelet            Pulling image "registry.redhat.io/rhel8/python-39:1-120.1684740828"
  Warning  Failed     2m6s (x4 over 3m39s)  kubelet            Failed to pull image "registry.redhat.io/rhel8/python-39:1-120.1684740828": failed to pull and unpack image "registry.redhat.io/rhel8/python-39:1-120.1684740828": failed to resolve reference "registry.redhat.io/rhel8/python-39:1-120.1684740828": failed to authorize: failed to fetch anonymous token: unexpected status from GET request to https://registry.redhat.io/auth/realms/rhcc/protocol/redhat-docker-v2/auth?scope=repository%3Arhel8%2Fpython-39%3Apull&service=docker-registry: 401 Unauthorized

We should be able to patch the configs kustomize is pulling from https://github.com/konflux-ci/image-controller.
We can do that quickly and then figure out if it can be changed at the source.

@cmoulliard I merged the fix. Let me know if you're seeing any issues with that in the future.

I reinstalled konflux and created a job manually
k create job --from=cronjob/image-controller-image-pruner-cronjob -n image-controller test-image-pruner

and the pod was able to download the image from the public red hat registry
Events:
  Type    Reason     Age   From               Message
  ----    ------     ----  ----               -------
  Normal  Scheduled  18s   default-scheduler  Successfully assigned image-controller/test-image-pruner-45c5n to my-konflux-control-plane
  Normal  Pulling    17s   kubelet            Pulling image "registry.access.redhat.com/ubi8/python-39:1-201.1729679484"

@yftacherzog

Thank you for checking and letting us know!


Message is not recieved in conents.js from background.js

hey! I was learning to build chrome extensions. In part 11.5 video, there is a functionality where a message is passed from background.js to content.js and then log that message, but that is not working. I tried even pasting the same code as in the respective repo but still not working.
Repo link:- https://github.com/CodingTrain/website/tree/master/Courses/programming_with_text/session11/11-04_Chrome_Extensions_Background_Scripts
Video link: -https://www.youtube.com/watch?v=ew9ut7ixIlI

I pulled the repository fresh today and nothing seems broken...
Can you post steps to re-create the error?

Hey everyone!
This repository manages the Coding Train website, it isn't the right place for asking questions.
The best things you can do is join our discord.
P.S. Sorry for the late reply, we didn't use the issue section of this repository for a long while.
Hope to see you there!


Added support for fakes

Hi! Being inspired by your project and wanting to try out developing for the tessle NOW-NOW-NOW, I've created a fakes extension which I'd love for you to merge.
Syntax: tessel fake <script name>
With the tessel-fakes npm package, we have support for blinky:

I will write a blog post about this support once the merge is complete. :-)

@samilamti just FYI, We have VM for Tessel 2 so you could have this same sort of functionality for newer hardware :) https://github.com/tessel/t2-vm

Awesome! I'll be sure to mention that in my post as I had a hard time finding a test harness (via Google) as I was reading the docs :-)
// Sami

On 28 jun 2015, at 03:07, Jon<EMAIL_ADDRESS>wrote:
@samilamti just FYI, We have VM for Tessel 2 so you could have this same sort of functionality for newer hardware :) https://github.com/tessel/t2-vm
—
Reply to this email directly or view it on GitHub.

@samilamti Let me know if you get a chance to try out the VM. Also, I'd love to hear your thoughts on the documentation I'm developing for T2 - let me know if it's useful!
I'm stoked to see how excited you are about Tessel but I'm not going to merge this particular PR - partially because the Tessel Project is investing most of its time on T2 and we already have this functionality with the VM and partially because I don't think we should set a precedent of having a CLI functionality be dependent on a Node module that must be installed separately.
Thank you very much for the PR though! Feel free to keep 'em coming, especially for T2 repos.


[Place Details API response] geometry field  - LatLngLiteral does not specify the geocode level

This response does not include the precision/"geocode level"  as returned in location_type field within geometry by geocoding api.
Until the response is enhanced, API docs should specify what geocode level can be expected for the lat,lng returned in Place Details.

PLEASE READ
If you have a support contract with Google, please create an issue in the support console. This will ensure a timely response.
Discover additional support services for the Google Maps Platform, including developer communities, technical guidance, and expert support at the Google Maps Platform support resources page.
If your bug or feature request is not related to this particular library, please visit the Google Maps Platform issue trackers.
Check for answers on StackOverflow with the google-maps tag.

Please be sure to include as much information as possible:
Environment details

Specify the API at the beginning of the title (for example, "Places: ...")
OS type and version
Library version and other environment information

Steps to reproduce

?

Code example
# example

Stack trace
# example

Following these steps will guarantee the quickest resolution possible.
Thanks!

If you would like to upvote the priority of this issue, please comment below or react on the original post above with :+1: so we can see what is popular when we triage.
@sanjeevchopra Thank you for opening this issue. 🙏
Please check out these other resources that might help you get to a resolution in the meantime:

Check the issue tracker - bugs and feature requests for Google Maps Platform APIs and SDKs
Open a support case - Get 1:1 support in Cloud Console.
Discord - chat with other developers
StackOverflow - use the google-maps tag

This is an automated message, feel free to ignore.


GDScript LSP: Implement goto declaration

Stop make client to show native symbol documentation page when resolving native symbols.
The documentation page can be show in when request go to decleation.
Fix https://github.com/godotengine/godot-vscode-plugin/issues/131

Thanks!


[modify] event agents nodes page long term class

Coverage decreased (-0.009%) to 84.566% when pulling 57c74c0ff4c2d69ddc3bf3de1568f9388b8af5a9 on pr-event-page-long-term-class into 10e4d10ba4daf7ce184e0faf706f29efb9a58cd8 on master.