Parallelize independent clones?

For most workspaces the calls to git clone could be done in parallel, at least at the top level of the dependency tree, and it would greatly speed up initializing a complex workspace. It seems like this method would need to be reworked to support this: https://github.com/sifive/wit/blob/master/lib/wit/workspace.py#L180.

Somewhat related is https://github.com/sifive/wit/pull/211/ which does a parallel clone

Another attempt at adding parallelism: https://github.com/sifive/wit/pull/222


appIndex must be provided if using watch mode on web component Scaffold

"npm run start" script throws this error:
"Error: appIndex must be provided if using watch mode".
It happens in a new Web Component Project, created by doing this steps:

npm init @open-wc
Scaffold a new project > Web Component
Choosing: Buiding, linting, demoing
Installing dependencies by npm

And Later:

cd project-name
npm run start

I am using Mac OS X, Node V10.15.3 and npm 6.9.0
It seems that the problem is the lack of the -app-index argument in the npm "start" script. But placing that argument do not solve the script problem. In that case the problem appears in the browser: a 404 error when fetching the component Javascript file.

Thanks we will look into this

I fixed this in https://github.com/open-wc/open-wc/pull/503, just adding --app-index looks to solve it. You mention it doesn't work for you, can you try again and see if it works now?

Yes, is solved now. Thanks


can not add favorite currency list

It's correct to setup base currency.

But it seem to can not recognize this command curcon LIST.

Is there some wrong operation for me?
Node: v17.9.0
Alfred: 4.6.4 Powerpack
alfred-currency-conversion: 0.2.0

It seems that the new feature Set your own favorite currency list is not included in version 0.2.0.
Is there deadline to release new version?

Yes, when I install this it seems like the code is quite different from master. I don't get the favoriteCurrencies.
I hover made this change in the source:
const topCurrencies = process.env['CURRENCIES'] ?
  process.env['CURRENCIES'].split(',') :
  ["USD", "EUR", "JPY", "GBP", "CHF", "CAD", "AUD"];
const allCurrencies = ["AUD", "BGN", "BRL", "CAD", "CHF", "CNY", "CZK", "DKK", "EUR", "GBP", "HKD", "HRK", "HUF", "IDR", "ILS", "INR", "ISK", "JPY", "KRW", "MXN", "MYR", "NOK", "NZD", "PHP", "PLN", "RON", "RUB", "SEK", "SGD", "THB", "TRY", "USD", "ZAR"];
const currencies = [...new Set([...topCurrencies, ...allCurrencies])];

And I set comma separated currencies in environment variables and that works for me.
I guess I might lose this change on update but I don't mind that much.

how can I paste it into the workflow?

There you can find the source. Good luck!

did you replaced all three variable for it to work?

yes!


macOS Helper apps without signing do not have sandbox entitlements, but with the main app crashes

Issue Details

Electron Packager Version:

14.0.6 and master

Electron Version:

6.0.11

Operating System:

macOS

Expected Behavior
An app built using electron-packager, should run and have sandbox entitlements for Helper Apps (GPU, Renderer and Plugin) for submission to the mac app store (mas)
Actual Behavior
An app built using electron-packager runs when signed following the electron mac app store instructions, but when uploaded using Application Loader, there is an error saying that the Helper Apps do not have sandbox entitlements.
If the script is modified to add sandbox entitlements and sign the Helper Apps (GPU, Plugin, Renderer), the app no longer runs, but crashes with 'Crashed Thread:        24  ThreadPoolSingleThreadForegroundBlocking0......'
To Reproduce
My original packager command is:
electron-packager . --app-bundle-id=com.weareamplify.disconnect --app-category-type=public.app-category.lifestyle --overwrite --platform=mas --arch=x64 --icon=Icon.icns --prune=true --out=mas-builds

My signing script is:
#!/bin/bash

# Name of your app.
APP="disconnect"
APP_FOLDER="/Users/stephen/Documents/Development/amplify/disconnected/mas-builds/disconnect-mas-x64"
# The path of your app to sign.
APP_PATH="$APP_FOLDER/disconnect.app"
# The path to the location you want to put the signed package.
RESULT_PATH="$APP_FOLDER/$APP.pkg"
# The name of certificates you requested.
APP_KEY="3rd Party Mac Developer Application: Louder Productions Limited (HKH4LU2D76)"
INSTALLER_KEY="3rd Party Mac Developer Installer: Louder Productions Limited (HKH4LU2D76)"
# The path of your plist files.
CHILD_PLIST="/Users/stephen/Documents/Development/amplify/disconnected/child.plist"
PARENT_PLIST="/Users/stephen/Documents/Development/amplify/disconnected/parent.plist"
LOGINHELPER_PLIST="/Users/stephen/Documents/Development/amplify/disconnected/loginhelper.plist"

FRAMEWORKS_PATH="$APP_PATH/Contents/Frameworks"

codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$FRAMEWORKS_PATH/Electron Framework.framework/Versions/A/Electron Framework"
codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$FRAMEWORKS_PATH/Electron Framework.framework/Versions/A/Libraries/libffmpeg.dylib"
codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$FRAMEWORKS_PATH/Electron Framework.framework"
codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$FRAMEWORKS_PATH/$APP Helper.app/Contents/MacOS/$APP Helper"
codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$FRAMEWORKS_PATH/$APP Helper (GPU).app/Contents/MacOS/$APP Helper (GPU)"
codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$FRAMEWORKS_PATH/$APP Helper (Plugin).app/Contents/MacOS/$APP Helper (Plugin)"
codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$FRAMEWORKS_PATH/$APP Helper (Renderer).app/Contents/MacOS/$APP Helper (Renderer)"
codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$FRAMEWORKS_PATH/$APP Helper.app/"
codesign -s "$APP_KEY" -f --entitlements "$LOGINHELPER_PLIST" "$APP_PATH/Contents/Library/LoginItems/$APP Login Helper.app/Contents/MacOS/$APP Login Helper"
codesign -s "$APP_KEY" -f --entitlements "$LOGINHELPER_PLIST" "$APP_PATH/Contents/Library/LoginItems/$APP Login Helper.app/"
codesign -s "$APP_KEY" -f --entitlements "$CHILD_PLIST" "$APP_PATH/Contents/MacOS/$APP"
codesign -s "$APP_KEY" -f --entitlements "$PARENT_PLIST" "$APP_PATH"

productbuild --component "$APP_PATH" /Applications --sign "$INSTALLER_KEY" "$RESULT_PATH"

Additional Information
I have tried submitting this as a documentation bug on the electron repository, but i noticed that a recent fix was made for these Helper apps in this repository, so wondered if you might know what entitlements these Helper apps might need or if there is any other reason for a crash?
Also, I note that although i can see a fix for Helper acts which is supposed to be in electron-packager 14.0.6, installing via npm does not include this fix, so i tried installing master directly.

This isn't a bug/question related to Electron Packager itself, but rather about macOS code signing, which Packager delegates to electron-osx-sign. However, I discourage you from filing yet another issue in that repository - the electron-osx-sign maintainer was pinged in the Electron issue, so another copy of that issue would be just noise at that point.

Thanks for looking into it for me. I think i may need to look at what these Electron Helper apps are for, and what 'entitlements' they need on a mac with its newer security features.

@malept, i don't expect you to re-open this issue, but i think you may have missed my point about the current release on npm not including fixes that I expected: "Also, I note that although i can see a fix for Helper acts which is supposed to be in electron-packager 14.0.6, installing via npm does not include this fix, so i tried installing master directly."

I've verified that the fixes for the Electron 6 helpers in #1036 and #1046 are in the NPM release of 14.0.6. master should only contain an unreleased feature unrelated to the new helpers at the time of this comment.

ok - thanks - i must have misunderstood which fixes were meant to be in the release.
btw - i'm making progress with the Helper app entitlements, having delved into the Chromium commits...


Roll engine 0e2c8feeeb47..d41e25b5492d (10 commits)

https://github.com/flutter/engine/compare/0e2c8feeeb47...d41e25b5492d
git log 0e2c8feeeb47..d41e25b5492d --first-parent --oneline
2020-03-10<EMAIL_ADDRESS>Revert "Revert "fix shadows and mask filter blurs (#16963)" (#17008)" (flutter/engine#17040)
2020-03-10<EMAIL_ADDRESS>Add support for firefox mac installer. Update web_ui pubspec for http.wq (flutter/engine#17044)
2020-03-09<EMAIL_ADDRESS>fix "TREE INCONSISTENT" noise in compositing_test.dart (flutter/engine#16995)
2020-03-09<EMAIL_ADDRESS>Add more child lifecycle tests (flutter/engine#16689)
2020-03-09<EMAIL_ADDRESS>Add libfreetype6-dev to desktop Linux dependencies (flutter/engine#17020)
2020-03-09<EMAIL_ADDRESS>Disable shell benchmarks (flutter/engine#17038)
2020-03-09<EMAIL_ADDRESS>Fix bounds of image_filter_layer (flutter/engine#16960)
2020-03-09<EMAIL_ADDRESS>Record fml and shell benchmarks (flutter/engine#16991)
2020-03-09<EMAIL_ADDRESS>Roll src/third_party/skia c56950442dd1..23899c64e3db (11 commits) (flutter/engine#17033)
2020-03-09<EMAIL_ADDRESS>use commit date instead of author date (flutter/engine#17032)
If this roll has caused a breakage, revert this CL and stop the roller
using the controls here:
https://autoroll.skia.org/r/flutter-engine-flutter-autoroll
Please CC<EMAIL_ADDRESS>on the revert to ensure that a human
is aware of the problem.
To report a problem with the AutoRoller itself, please file a bug:
https://bugs.chromium.org/p/skia/issues/entry?template=Autoroller+Bug
Documentation for the AutoRoller is here:
https://skia.googlesource.com/buildbot/+/master/autoroll/README.md

Gold has detected one or more untriaged digests on patchset 10.
Please triage them at https://flutter-gold.skia.org/search?issue=52299.

Commit queue failed; closing this roll.


See also ShowModal property

https://docs.microsoft.com/en-us/office/vba/language/reference/user-interface-help/showmodal-property

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 93a2758f-6eb0-98ce-12eb-8e33b243aeb0
Version Independent ID: 218ef567-bf1f-f829-47c6-2a645292cf98
Content: Show Method
Content Source: Language/Reference/User-Interface-Help/show-method.md
Product: office
GitHub Login: @o365devx
Microsoft Alias: o365devx

@geoffm
Thanks. I added the See also link to the show method page. Changes will be live later today.


PasswordBox Update and minor styling changes

This PR updates the password box. It includes an updating progress bar for password setter box as well. Also included is a smaller update to remove-key styling.
resolves #250
resolves #197
resolves #271

No way we deploy this without a way to start over with pasword input.

you can just use the back arrow?

No way we deploy this without a way to start over with pasword input.

you can just use the back arrow?

Nope, I stil have to input the same password then.

No way we deploy this without a way to start over with pasword input.

you can just use the back arrow?

Nope, I stil have to input the same password then. At least it was like this in my tests.

Clarification: Just figured out with @sisou that the back button in the interface does work, but browser back doesn't.

There is also no a visual glitch when going to "export words" during Logout. While the page is spinning around, the blurred Login File is shown on the white side.

I have just tried out the changes, and the history method does not actually work for me. Nothing happens after the first click on the back button while in repeat-password state. Neither on export(file) nor on change password (both cases for a key that is unencrypted).
Furthermore, the password repeat input shakes and tells me "the password is too short" while repeating and stopping to input after e.g. 3 characters (here the rule is missing that prevents validation while the input is shorter than the first password).

The visibility indicator for the shake animation I'd like to postpone until it is clear whether or not the shake animation for the input stays, or if the box will be shaken.


[Questions] Architecture and DI Container in IGListKit

Hello,
I would like to ask some questions to the community here because we are struggling a bit to understand some topics and connect them with IGListKit.
I am aware that these topics are not related to IGListKit code, but more architectural questions and software engineering knowledge, but I hope this could help creating some know-how around IGListKit and maybe transform this into a best-practices section later on with a PR.
1- Is IGListKit written on top of a specific architecture? (eg: Is it following MVVM?) I am not clear if it is and it would be interesting to understand it. Does this impact the use of it inside any other architecture, due to the requirements of the patterns behind it?
2- How would you suggest to use a Dependency Injection framework with IGListKit AdapterDataSource to initialise all section controllers?
The Adapter needs to create SectionControllers, and using a dependency injection framework, a container is going to resolve this controllers and the sub-dependencies.
Should the datasource own this container, even if it is a singleton? (but then, how do we test our datasource?)
or should the datasource delegate everything to a factory instead? (but then you don't test factories?)

1- Is IGListKit written on top of a specific architecture?

IMO pigeon-holing architectures isn't useful. I wouldn't say we follow any single strict architecture/pattern, more that we follow a few guidelines that make our code easy to maintain & test:

Inject dependencies instead of rely on global state (unless where it aides the API)
Decompose objects so they have a single-responsibility. We're not perfect here, but do a pretty good job.

How would you suggest to use a Dependency Injection framework with IGListKit

I'm not sure I'd suggest using a framework for dependency injection at all 😅
I've never seen a DI framework that doesn't result in code bloat and hidden magic. At Instagram, we just write object initializers w/ lots of parameters. Sure, they get long, but its stupid-easy to figure out what is happening.
You can definitely do any type of initialization-dependency-injection w/ Section Controllers that you want. Just init the controllers in the adapter and pass in w/e stuff you want (we do this in Instagram all the time).

a container is going to resolve this controllers and the sub-dependencies

I'm not sure how this works or what it does, but again I would personally avoid it.

Should the datasource own this container, even if it is a singleton?

No way, I would never, ever, ever make a data source of anything a singleton. Global, mutable state = bad time.

or should the datasource delegate everything to a factory instead (but then you don't test factories?)

We create separate data source objects at Instagram that handle all of this. We initialize the data sources w/ w/e dependencies that are required by the section controllers it ends up initializing. It keeps the "flow" of dependencies one way, and eliminates any need for global state.
Not totally sure I follow the "don't test factories". What stops them from being tested? If they are stateless the tests should be relatively easy, right?

@rnystrom Thanks for the info and your view on it.
I am exploring the world of architectural decisions/Frameworks/Container vs No Container trying to improve my codebase and it is always helpful to have some information from other developers, especially when they are working on a big app that is used by a lot of people and works (and it maintainable and scale)
For sure I guess the best path to follow, instead of pointing different arch/framework is going SOLID, as you were highlighting
I agree with the constructor dependencies being enough, sometimes however when you need something very low in the stack, you end up with a guy been passed from root to bottom, being never used in the middle. (or maybe I am approaching this wrong :D)
and that global state is bad 😡
Regarding factories, I was pointing out that, if this factories use the container, so they have a singleton inside/global state, then they get harder to mock/test

@rnystrom I actually have another question, regarding how you use IGListKit in Instagram.
Let's say my Section Controllers are fetching data, need to do some calculation or whatever else.
If I want to use DI and split responsibilities, then the datasource needs to be aware and get injected with all section controller requirements.
Then if I need to add one section controller to my app, I need to change the initialiser of every single layer that is above the datasource and fill the datasource initialiser with tenths of arguments.
This is something I cannot wrap my head around and brought me thinking that a DI Container framework is needed.
How do you handle the generation of components? They are in the root of the app, and injected down everywhere (and in this case how you solve the missing encapsulation problem)?

Ryan has a very important point here I want to repeat

MO pigeon-holing architectures isn't useful. I wouldn't say we follow any single strict architecture/pattern, more that we follow a few guidelines that make our code easy to maintain & test

Keep researching. Get inspired. Discuss with other developers. Grab onto the things you think make sense and forget the rest. You are clearly on a good path and do not get frustrated because you havent really found how you can solve all of your architectural problems with something like dependency injection... because you wont 😄   There will always been pros and cons. Shortcuts will be made. There are no such things as a project with a perfect architecture.  Hell, there are some things about IGListKit that I would consider break some best practices. Do I still use love it? Absolutely. The pros clearly outweight the cons.
A bit off topic but if I were to suggest any talks / readings I would say read up on some light functional programming topics in swift, VIPER / VIP / MVVM and start using the small things you like. Watch Garys Boundries talk. Read Jereds recent blogpsot and keep reading how you can use dependency injection in your Swift projects 👍  Over time you will improve. A lot. But even after many years in this industry, most of us (especially me) feel like complete nub multiple times a day 💃
I would gladly try to help you (if I can) with any more questions, just hit me up on twitter 💯
Maybe this issue could be closed as it is... far beyond the scope of IGListKit? 🤔

@heumn Thank you 😄
That is exactly why I asked some question here ehe, to discuss a bit on this open community and get some feedbacks! I am going to jump into your links and keep trying to find out what works best.
There is always so much to learn in Software Engineering, always, too much 🤣
Thanks again, I will close this issue

My pleasure :)


Feature Add function strcmp

Proposed changes
Issue Number: close #33093

mysql> select strcmp("test1", "test");
+-------------------------+
| strcmp('test1', 'test') |
+-------------------------+
|                       1 |
+-------------------------+
1 row in set (0.02 sec)

mysql> select strcmp("test", "test");
+------------------------+
| strcmp('test', 'test') |
+------------------------+
|                      0 |
+------------------------+
1 row in set (0.00 sec)

mysql> select strcmp("test", "test1");
+-------------------------+
| strcmp('test', 'test1') |
+-------------------------+
|                      -1 |
+-------------------------+
1 row in set (0.00 sec)

Further comments
If this is a relatively large or complex change, kick off the discussion at<EMAIL_ADDRESS>by explaining why you chose the solution you did and what alternatives you considered, etc...

run buildall

run p0

run p0

run buildall

run p0

run buildall

@zclllyybb please review this pr.

please add my wechat torch-wood_ for talking about this pr

run buildall

run beut

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

run buildall

run cloud_p1


[libpq] build failure

Host Environment

OS: Windows - windows-x64
Compiler: latest

To Reproduce
Steps to reproduce the behavior:
./vcpkg install libpq
Failure logs
vcpkg\buildtrees\libpq\x64-windows-rel\src\interfaces\libpq\fe-secure-openssl.c(707,45): error C2065: 'OPENSSL_INIT_LOAD_CONFIG': undeclared identifier [D:\Pro\vcpkg\buildtrees\libpq\x64-windows-rel\libpq.vcxproj]

Rebuild OpenSSL and try again. You probably still have version 1.0.2 installed


RemoteRenderer.OnRenderCompleted doesn't run on renderer sync context

This is more of a question than a bug report, but while investigating a different reliability issue, I noticed that OnRenderCompleted (the thing that can throw the Received a notification for a rendered batch when not expecting it exception) doesn't run on the renderer sync context.
I've been trying to use this knowledge to create some failure scenario I can report, but have been unable to objectively prove this can lead to any problem. So, this is really more of a question for people who've been working in this area: did we expect calls to this method to be serialized, or is it expected that the calls are unsynchronized?
For a while I thought this might explain any possible Received a notification for a rendered batch when not expecting it error, since if it runs in parallel on separate threads for the same circuit, then we might expect to find batch B before batch A, and hence throw. However, even adding random Thread.Sleep calls didn't allow me to create a repro. My remaining theory is that SignalR itself is ensuring no two calls occur in parallel for the same hub, which would alleviate any possible bug, although it would be a bit awkward for us to rely on this implicitly without even a comment about that.
@pranavkm @rynowak Do we believe it's safe for RemoteRenderer.OnRenderCompleted calls to be unsynchronized?

My remaining theory is that SignalR itself is ensuring no two calls occur in parallel for the same

From what I gathered, with a send, the client waits until the hub method is invoked, but does not wait for a response. This should mean that you could have concurrency in the body of the Hub method unless SignalR uses synchronization primitives on the server. @anurse \ @davidfowl would certainly know best.
That said, the body of RemoteRenderer.OnRenderCompleted doesn't look like it needs to be synchronized. The completed render task that would get processed further should run in the sync context. Here's the method for reference:
https://github.com/aspnet/AspNetCore/blob/master/src/Components/Server/src/Circuits/RemoteRenderer.cs#L196-L217

with a send, the client waits until the hub method is invoked

Send waits for the bytes to be taken by the OS. Inside SignalR we accept bytes and consume them synchronously.

Received a notification for a rendered batch when not expecting it

This should be fixed by @pranavkm because blazer wasn't awaiting sends and there is now an internal queue for sends.

My remaining theory is that SignalR itself is ensuring no two calls occur in parallel for the same hub, which would alleviate any possible bug, although it would be a bit awkward for us to rely on this implicitly without even a comment about that.

SignalR does currently ensure that no two invocations for the same connection occur on a hub on the server, but this is something we are thinking about changing post-3.0 (#5351). However, we'd do so in an opt-in manner because there may be users depending on the serialized behavior. I think you can safely rely on the fact that for any given connection, no two invocations will be executing(*) at once.
(* - i.e. we won't process the next message until the Task returned by the Hub method is completed)

Thanks everyone! Andrew’s last post explains why I can’t observe any buggy behaviour then.
The remaining question is whether we want to be more explicit about this inside Blazor by dispatching to the renderer sync context. If not we should at least add a comment to explain why it’s safe to assume correct ordering of this: https://github.com/aspnet/AspNetCore/blob/master/src/Components/Server/src/Circuits/RemoteRenderer.cs#L204

One thing, that doesn't really apply to you now but may later: This does not quite hold for Streaming (i.e. returning IAsyncEnumerable<T> from a Hub method). In that case we move on to the next message after starting the stream, and don't wait for all the items to be yielded.
Blazor isn't using streaming so it's not directly relevant, but useful context to have :).

Added comment in https://github.com/aspnet/AspNetCore/pull/11141


modify_enchantment_damage_dealt doesn't work

Once again using the example from here and forge 1.19.2, it doesn't crash anymore but twiddling with the values it also doesn't seem to do anything at all, the damage stays constant at its vanilla value.
I'm also not sure what its supposed to do, is it just a shorthand for modifying the damage but with filtering for the user's enchantment or does it actually mixin the damage modifier formula for sharpness/bane of arthropods/smite/...?

On Forge, it modifies the damage through an event.
base_value is the damage at level 1. With any more levels, the modifier is applied as many times as more levels there are.

Thank you for the report though, I should really stop assuming things work after one fix.

I was accidentally setting the power to equal the modify enchantment damage taken amount, which was 0.
This has now been fixed.

Fixed in v2.1.p


❓ Enable Flash when using frameProcessor

Question
How can I enable the flash light while using a frameProcessor. I'm using the Colorwaver example at the moment. Also thank you for this amazing package
What I tried
No response
VisionCamera Version
2.9.4
Additional information

[ ] I am using Expo
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar questions in the issues page as well as in the discussions page and found none.

Hey! Thanks for the kind words, you can pass torch={true}. :)

Thanks for your swift reply. torch={'on'} did the trick


KAFKA-3475; Introduce our own MiniKdc

This also fixes KAFKA-3453 and KAFKA-2866.

Started a system tests run as MiniKdc is also used by system tests:
https://jenkins.confluent.io/job/system-test-kafka-branch-builder/396/console

Tests passed locally, Jenkins failure is in the streams code, which is unrelated.

Fixed minikdc.py and started another system tests build:
https://jenkins.confluent.io/job/system-test-kafka-branch-builder/397/

There was an unrelated transient failure with security protocol PLAINTEXT. To be sure, I launched another branch builder job, which had a different transient failure with security protocol SSL:
https://jenkins.confluent.io/job/system-test-kafka-branch-builder-2/46/console
So, I think this PR is fine.
Review by @gwenshap

Looks awesome to me. I like how flexible the class is :)


remove extra footer padding nd margin

Hi, I would like to work on this issue. Could you please assign it to me?

for sure


Fix Usage instructions in README

DocParser and HtmlRenderer are not needed, CommonMarkConverter was missing config parameter.

This is why I should not release things when I'm tired... haha.
Thank you for catching and fixing this!


SqlServer: Fluent API to configure a column as SPARSE column

I know I can do this with raw SQL in Up method, but can this be done with fluent API.
If it can How, and if not, are there plans to add this feature in future versions?
Further technical details
EF Core version: 1.1.1
Database Provider: Microsoft.EntityFrameworkCore.SqlServer
Operating system: Windows 10
IDE: Visual Studio 2017

Documentation link: https://docs.microsoft.com/en-us/sql/relational-databases/tables/use-sparse-columns
@borisdj - There is no fluent api at present.

@borisdj It would be interesting to add fluent API extension methods for this for the SQL Server provider. However, it is not a high priority for us, so putting it on the backlog. We would consider at a high-quality PR from the community for this.

Hey @ajcvickers : I have some time spare on Friday, so I can give this a go?
Questions

Would you want this to be an PropertyBuilder extension in here for SQL Server?

https://github.com/aspnet/EntityFrameworkCore/blob/469177a49d251bb81184b42ce4cd2ffe623b345a/src/EFCore.SqlServer/Extensions/SqlServerPropertyBuilderExtensions.cs

Would it require a DataAnnotation to identify a SPARSE column?

@garfbradaz Yes, that's the appropriate place for the fluent API. It's fine to not have data annotation support for this--there are many places where the fluent API is the only way to configure something. Also, provider-specific attributes for mapping is a space that we haven't yet ventured into.

/cc @AndriySvyryd @bricelam @divega

Smashing. @ajcvickers . Spent Friday familiarizing myself with the code (and today as well). Quite a complex beast (which is fun to learn).
Questions if I may:

There are some SPARSE restrictions - Do these need to be applied as a SqlServerConventionSetBuilder where appropriate?

I couldn't find a SQL Server implementation of  Microsoft.EntityFrameworkCore.Migrations.Operations.CreateTableOperation  &   Microsoft.EntityFrameworkCore.Migrations.Operations.AlterTableOperation - I presume a SqlServerCreateTableOperation & SqlServerAlterTableOperation will be needed then to satisfy this feature, including the SPARSE elements.

Obviously any tests associated with the new code.

have a look at: https://github.com/aspnet/EntityFrameworkCore/blob/master/src/EFCore.SqlServer/Migrations/SqlServerMigrationsSqlGenerator.cs#L455
and
https://github.com/aspnet/EntityFrameworkCore/blob/master/src/EFCore.SqlServer/Migrations/SqlServerMigrationsSqlGenerator.cs#L196

Awesome thanks @ErikEJ

Has Entity Framework Core come to support SPARSE columns in the meantime?
I have made an SQL script by hand, which drops indexes, alter columns to be SPARSE and re-adds indexes because you cannot alter a column to be SPARSE if there's an index, so it could be rather convenient with up-front support for SPARSE so I can get rid of this script.

@henrikdahl8240 This issue is in the Backlog milestone. This means that it is not planned for the next release (EF Core 5.0). We will re-assess the backlog following the this release and consider this item at that time. However, keep in mind that there are many other high priority features with which it will be competing for resources.

Note: as mentioned by @henrikdahl8240 in https://github.com/dotnet/efcore/issues/20880#issuecomment-626234870, SPARSE columns could be a good fit for TPH.

@ajcvickers Is the EF Core team still open to accepting a solution from the community? If so, I'd like to spend a few more days preparing a PR for review.
With the help of the prior discussions in this issue, I was able to locate most places that will require code changes and spent some time getting familiar with PropertyBuilder's and MigrationsSQLGenerator's. Please let me know if you have any suggestions and/or if I should put a hold on this effort.

@jonlouie Yes, still interested, and I don't think there is any reason to put it on hold. :-)

@jonlouie, just wondering if you had any luck with preparing PR for this?

@eugbaranov Unfortunately, I did not end finding the time to complete my PR. If you are looking to pick up this issue, here are some places that likely need modifications or additions:

src/EFCore.SqlServer/Extensions/SqlServerPropertyBuilderExtensions.cs
src/EFCore.SqlServer/Extensions/SqlServerPropertyExtensions.cs
src/EFCore.SqlServer/Internal/SqlServerModelValidator.cs
src/EFCore.SqlServer/Metadata/Internal/SqlServerAnnotationNames.cs
src/EFCore.SqlServer/Metadata/Internal/SqlServerAnnotationProvider.cs
src/EFCore.SqlServer/Migrations/SqlServerMigrationsSqlGenerator.cs


Unexpected trailing contents with file target and content targeting a specific line

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
When defining a target with kind: file, using line together with content referencing a variable, the line is properly updated but some cruft is added at the end of the file, which seems the trailing text present in content after the {{ variable }} is being used.
Expected Behavior
Since I am targeting a specific line, I expect that only that line should be modified, and the entire line should be overwritten completely with the content provided, independently from the pre-existing text on that line.
Steps To Reproduce
Have a pipeline with the following targets:
targets:
  updateSyncServiceVersion:
    name: Bump Sync Service version
    kind: file
    scmid: securityTestingRepo
    sourceid: syncServiceVersion
    spec:
      file: configs/Sync Service/urls_to_upload_and_scan.txt
      line: 1
      content: org.alfresco.services.sync:service-sync:${ARTIFACT_VERSION:-{{ source `syncServiceVersion` }}}:jar
  updateDeviceSyncRepoVersion:
    name: Bump Device Sync Repo version
    kind: file
    scmid: securityTestingRepo
    sourceid: syncServiceVersion
    spec:
      file: configs/Sync Service/urls_to_upload_and_scan.txt
      line: 2
      content: org.alfresco.services.sync:alfresco-device-sync-repo:${ARTIFACT_VERSION:-{{ source `syncServiceVersion` }}}:amp

the target file contents are:
org.alfresco.services.sync:service-sync:${ARTIFACT_VERSION:-5.0.1-SNAPSHOT}:jar
org.alfresco.services.sync:alfresco-device-sync-repo:${ARTIFACT_VERSION:-5.0.1-SNAPSHOT}:amp

Environment
- OS: Ubuntu 22.04
- updatecli: v0.71.0

Anything else?
First commit (after first target update):

Second commit (after second target update):

I think this line flag to be os.O_WRONLY|os.O_TRUNC

...O_TRUNC // truncate regular writable file when opened.

https://github.com/updatecli/updatecli/blob/296e67c2b723b2f8f2a523cf70701e17aa363d09/pkg/core/text/main.go#L238

It looks like the its leaving remaining characters of line minus source


Manually register base classes

My idea is to setup a system to automatically enable RTTR so I'm using libclang to parse the project code to auto generate RTTR_REGISTRATION in a separate file.
The only thing I cant figure to solve is how to avoid RTTR_ENABLE inside the class definition.
There is a way to register base classes in RTTR_REGISTRATION ?

At the moment there is now way to register base classes without RTTR_ENABLE.
This would only be possible when I use RTTI from C++.
And RTTR does work without RTTI support.
I could maybe support both ways. But I have unfortunately not time to do this atm.


operator [N] move2kube-operator (0.3.8)

Thanks for submitting your Operator. Please check the below list before you create your Pull Request.
New Submissions

[y] Are you familiar with our contribution guidelines?
[y] Have you packaged and deployed your Operator for Operator Framework?

[y] Have you considered whether you want to use semantic versioning order?
[y] Is your submission signed?
[y] Is operator icon set?

Updates to existing Operators

[ ] Did you create a ci.yaml file according to the update instructions?
[ ] Is your new CSV pointing to the previous version with the replaces property if you chose replaces-mode via the updateGraph property in ci.yaml?
[ ] Is your new CSV referenced in the appropriate channel defined in the package.yaml or annotations.yaml ?
[ ] Have you tested an update to your Operator when deployed via OLM?
[ ] Is your submission signed?

Your submission should not

[n] Modify more than one operator
[n] Modify an Operator you don't own
[n] Rename an operator - please remove and add with a different name instead
[n] Modify any files outside the above mentioned folders
[n] Contain more than one commit. Please squash your commits.

Operator Description must contain (in order)

[y] Description of the managed Application and where to find more information
[y] Features and capabilities of your Operator and how to use it
[y] Any manual steps about potential pre-requisites for using your Operator

Operator Metadata should contain

[y] Human readable name and 1-liner description about your Operator
[y] Valid category name1
[y] One of the pre-defined capability levels2
[y] Links to the maintainer, source code and documentation
[y] Example templates for all Custom Resource Definitions intended to be used
[y] A quadratic logo

Remember that you can preview your CSV here.
--
1 If you feel your Operator does not fit any of the pre-defined categories, file an issue against this repo and explain your need
2 For more information see here

closing since https://github.com/redhat-openshift-ecosystem/community-operators-prod/pull/3086 got merged


Swap Open Payments description for metadata

See here: https://github.com/interledger/open-payments/issues/221

Needed this for both Gatehub & PCH project. KYC information in the payment is necessary.


Mini.statusline highlights are reversed.

I have done the following steps before reporting this issue:

[X] I have searched the existing issues
[X] I have read the FAQ in the help doc

Operating system/version
Ubuntu 24.04 WSL2
Terminal emulator/version
Windows Terminal
$TERM environment variable
tmux-256color
Tmux version
3.4
Feature matrix

==============================================================================
conform:                                     require("conform.health").check()

conform.nvim report ~
- Log file: /home/zeltron/.local/state/nvim/conform.log
- OK black ready (python)
- OK clang_format ready (c)
- OK gofmt ready (go)
- OK google-java-format ready (java)
- OK jq ready (json)
- OK latexindent ready (tex)
- OK npm-groovy-lint ready (groovy)
- OK prettier ready (css, json, svelte, typescript, html, javascript, jsonc)
- OK rustfmt ready (rust)
- OK shfmt ready (sh)
- OK stylua ready (lua)
- OK xmllint ready (xml)
- OK yamlfmt ready (yaml)

==============================================================================
dap:                                             require("dap.health").check()

dap: Adapters ~

dap.adapter: delve ~

dap.adapter: lldb ~
- OK is executable: /usr/bin/lldb-dap-18

dap.adapter: nlua ~
- Adapter is a function. Can't validate it

dap.adapter: go ~
- Adapter is a function. Can't validate it

dap.adapter: python ~
- Adapter is a function. Can't validate it

dap.adapter: debugpy ~
- Adapter is a function. Can't validate it

dap.adapter: pwa-node ~
- OK is executable: node

dap: Sessions ~
- OK No active sessions

==============================================================================
fzf_lua:                                                  health#fzf_lua#check

fzf-lua [required] ~
- OK 'fzf' `0.55 (devel)`
- OK 'git' `git version 2.47.0`
- OK 'rg' `ripgrep 14.1.1`
- OK 'fd' `fd 10.2.0`

fzf-lua [optional] ~
- OK `nvim-web-devicons` found
- OK 'rg' `ripgrep 14.1.1`
- OK 'fd' `fd 10.2.0`
- OK 'bat' `bat 0.24.0`
- OK 'delta' `delta 0.18.2`

fzf-lua [optional:media] ~
- WARNING 'viu' not found
- WARNING 'chafa' not found
- WARNING 'ueberzugpp' not found

fzf-lua [env] ~
- OK `FZF_DEFAULT_OPTS` is not set
- OK `FZF_DEFAULT_OPTS_FILE` is not set

==============================================================================
lspconfig:                                 require("lspconfig.health").check()

LSP configs active in this session (globally) ~
- Configured servers: angularls, lua_ls, html, lemminx, clangd, rust_analyzer, yamlls, basedpyright, svelte, vtsls, eslint, jsonls, texlab, cssls, bashls, gopls
- OK Deprecated servers: (none)

LSP configs active in this buffer (id=1) ~
- Language client log: ~/.local/state/nvim/lsp.log
- Detected filetype: `ministarter`
- 0 client(s) attached to this buffer

Docs for active configs: ~
-

==============================================================================
nvim-treesitter:                     require("nvim-treesitter.health").check()

Installation ~
- OK `tree-sitter` found 0.24.3 (bdfe32402e85673bbc693216f0a6ef72c98bb665) (parser generator, only needed for :TSInstallFromGrammar)
- OK `node` found v20.18.0 (only needed for :TSInstallFromGrammar)
- OK `git` executable found.
- OK `cc` executable found. Selected from { vim.NIL, "cc", "gcc", "clang", "cl", "zig" }
  Version: cc (Ubuntu 13.2.0-23ubuntu4) 13.2.0
- OK Neovim was compiled with tree-sitter runtime ABI version 14 (required >=13). Parsers must be compatible with runtime ABI.

OS Info:
{
  machine = "x86_64",
  release = "<IP_ADDRESS>-microsoft-standard-WSL2",
  sysname = "Linux",
  version = "#1 SMP Fri Mar 29 23:14:13 UTC 2024"
} ~

Parser/Features         H L F I J
  - angular             ✓ ✓ ✓ ✓ ✓
  - awk                 ✓ . . . ✓
  - bash                ✓ ✓ ✓ . ✓
  - bibtex              ✓ . ✓ ✓ ✓
  - c                   ✓ ✓ ✓ ✓ ✓
  - cmake               ✓ . ✓ ✓ ✓
  - cpp                 ✓ ✓ ✓ ✓ ✓
  - css                 ✓ . ✓ ✓ ✓
  - csv                 ✓ . . . .
  - diff                ✓ . ✓ . ✓
  - dockerfile          ✓ . . . ✓
  - doxygen             ✓ . . ✓ ✓
  - fish                ✓ ✓ ✓ ✓ ✓
  - git_config          ✓ . ✓ . ✓
  - git_rebase          ✓ . . . ✓
  - gitcommit           ✓ . . . ✓
  - gitignore           ✓ . . . ✓
  - go                  ✓ ✓ ✓ ✓ ✓
  - gomod               ✓ . . . ✓
  - gosum               ✓ . . . .
  - gowork              ✓ . . . ✓
  - graphql             ✓ . . ✓ ✓
  - groovy              ✓ ✓ ✓ ✓ ✓
  - html                ✓ ✓ ✓ ✓ ✓
  - http                ✓ . . . ✓
  - hurl                ✓ . ✓ ✓ ✓
  - ini                 ✓ . ✓ . ✓
  - java                ✓ ✓ ✓ ✓ ✓
  - javascript          ✓ ✓ ✓ ✓ ✓
  - jq                  ✓ ✓ . . ✓
  - jsdoc               ✓ . . . .
  - json                ✓ ✓ ✓ ✓ .
  - json5               ✓ . . . ✓
  - latex               ✓ . ✓ . ✓
  - lua                 ✓ ✓ ✓ ✓ ✓
  - luadoc              ✓ . . . .
  - make                ✓ . ✓ . ✓
  - markdown            ✓ . ✓ ✓ ✓
  - markdown_inline     ✓ . . . ✓
  - meson               ✓ . ✓ ✓ ✓
  - ninja               ✓ . ✓ ✓ ✓
  - nix                 ✓ ✓ ✓ ✓ ✓
  - perl                ✓ . ✓ . ✓
  - php                 ✓ ✓ ✓ ✓ ✓
  - pug                 ✓ . . . ✓
  - python              ✓ ✓ ✓ ✓ ✓
  - query               ✓ ✓ ✓ ✓ ✓
  - regex               ✓ . . . .
  - requirements        ✓ . . . ✓
  - ruby                ✓ ✓ ✓ ✓ ✓
  - rust                ✓ ✓ ✓ ✓ ✓
  - scala               ✓ ✓ ✓ . ✓
  - scss                ✓ . ✓ ✓ ✓
  - sql                 ✓ . . ✓ ✓
  - ssh_config          ✓ ✓ ✓ ✓ ✓
  - starlark            ✓ ✓ ✓ ✓ ✓
  - svelte              ✓ ✓ ✓ ✓ ✓
  - toml                ✓ ✓ ✓ ✓ ✓
  - typescript          ✓ ✓ ✓ ✓ ✓
  - vim                 ✓ ✓ ✓ . ✓
  - vimdoc              ✓ . . . ✓
  - vue                 ✓ . ✓ ✓ ✓
  - xml                 ✓ ✓ ✓ ✓ ✓
  - yaml                ✓ ✓ ✓ ✓ ✓
  - yuck                ✓ ✓ ✓ ✓ ✓
  - zig                 ✓ ✓ ✓ ✓ ✓

  Legend: H[ighlight], L[ocals], F[olds], I[ndents], In[j]ections
         +) multiple parsers found, only one will be used
         x) errors found in the query, try to run :TSUpdate {lang} ~

==============================================================================
render-markdown:                     require("render-markdown.health").check()

render-markdown.nvim [version] ~
- OK plugin 7.3.11
- OK neovim >= 0.10

render-markdown.nvim [configuration] ~
- OK valid

render-markdown.nvim [nvim-treesitter] ~
- OK installed
- OK markdown: parser installed
- OK markdown: highlight enabled
- OK markdown_inline: parser installed
- OK markdown_inline: highlight enabled
- OK latex: parser installed

render-markdown.nvim [executables] ~
- WARNING latex2text: not installed
  - ADVICE:
    - Disable LaTeX support to avoid this warning by setting { latex = { enabled = false } }

render-markdown.nvim [conflicts] ~
- OK headlines: not installed
- OK obsidian: not installed

==============================================================================
vim.deprecated:                       require("vim.deprecated.health").check()

- OK No deprecated functions detected

==============================================================================
vim.health:                               require("vim.health.health").check()

Configuration ~
- OK no issues found

Runtime ~
- OK $VIMRUNTIME: /home/zeltron/.local/share/bob/nightly/share/nvim/runtime

Performance ~
- OK Build type: RelWithDebInfo

Remote Plugins ~
- OK Up to date

terminal ~
- key_backspace (kbs) terminfo entry: `key_backspace=\177`
- key_dc (kdch1) terminfo entry: `key_dc=\E[3~`
- $TERM_PROGRAM="tmux"

tmux ~
- OK escape-time: 1
- OK focus-events: on
- $TERM: tmux-256color

External Tools ~
- OK ripgrep 14.1.1 (/home/zeltron/.cargo/bin/rg)

==============================================================================
vim.lsp:                                     require("vim.lsp.health").check()

- LSP log level : WARN
- Log path: /home/zeltron/.local/state/nvim/lsp.log
- Log size: 1017 KB

vim.lsp: Active Clients ~
- No active clients

vim.lsp: File Watcher ~
- file watching "(workspace/didChangeWatchedFiles)" disabled on all clients

vim.lsp: Position Encodings ~
- No active clients

==============================================================================
vim.provider:                           require("vim.provider.health").check()

Clipboard (optional) ~
- OK Clipboard tool found: xsel

Node.js provider (optional) ~
- Node.js: v20.18.0

- WARNING Missing "neovim" npm (or yarn, pnpm) package.
  - ADVICE:
    - Run in shell: npm install -g neovim
    - Run in shell (if you use yarn): yarn global add neovim
    - Run in shell (if you use pnpm): pnpm install -g neovim
    - You may disable this provider (and warning) by adding `let g:loaded_node_provider = 0` to your init.vim

Perl provider (optional) ~
- WARNING "Neovim::Ext" cpan module is not installed
  - ADVICE:
    - See :help |provider-perl| for more information.
    - You may disable this provider (and warning) by adding `let g:loaded_perl_provider = 0` to your init.vim
- WARNING No usable perl executable found

Python 3 provider (optional) ~
- WARNING No Python executable found that can `import neovim`. Using the first available executable for diagnostics.
- WARNING Could not load Python :
  /usr/bin/python3 does not have the "neovim" module.
  /usr/bin/python3.12 does not have the "neovim" module.
  python3.11 not found in search path or not executable.
  python3.10 not found in search path or not executable.
  python3.9 not found in search path or not executable.
  python3.8 not found in search path or not executable.
  python3.7 not found in search path or not executable.
  /usr/bin/python does not have the "neovim" module.
  - ADVICE:
    - See :help |provider-python| for more information.
    - You may disable this provider (and warning) by adding `let g:loaded_python3_provider = 0` to your init.vim
- Executable: Not found

Python virtualenv ~
- OK no $VIRTUAL_ENV

Ruby provider (optional) ~
- Ruby: ruby 3.2.3 (2024-01-18 revision 52bb2ac0a6) [x86_64-linux-gnu]
- WARNING `neovim-ruby-host` not found.
  - ADVICE:
    - Run `gem install neovim` to ensure the neovim RubyGem is installed.
    - Run `gem environment` to ensure the gem bin directory is in $PATH.
    - If you are using rvm/rbenv/chruby, try "rehashing".
    - See :help |g:ruby_host_prog| for non-standard gem installations.
    - You may disable this provider (and warning) by adding `let g:loaded_ruby_provider = 0` to your init.vim

==============================================================================
vim.treesitter:                       require("vim.treesitter.health").check()

- Nvim runtime ABI version: 14
- OK Parser: angular              ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/angular.so
- OK Parser: awk                  ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/awk.so
- OK Parser: bash                 ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/bash.so
- OK Parser: bibtex               ABI: 13, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/bibtex.so
- OK Parser: c                    ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/c.so
- OK Parser: cmake                ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/cmake.so
- OK Parser: cpp                  ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/cpp.so
- OK Parser: css                  ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/css.so
- OK Parser: csv                  ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/csv.so
- OK Parser: diff                 ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/diff.so
- OK Parser: dockerfile           ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/dockerfile.so
- OK Parser: doxygen              ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/doxygen.so
- OK Parser: fish                 ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/fish.so
- OK Parser: git_config           ABI: 13, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/git_config.so
- OK Parser: git_rebase           ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/git_rebase.so
- OK Parser: gitcommit            ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/gitcommit.so
- OK Parser: gitignore            ABI: 13, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/gitignore.so
- OK Parser: go                   ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/go.so
- OK Parser: gomod                ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/gomod.so
- OK Parser: gosum                ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/gosum.so
- OK Parser: gowork               ABI: 13, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/gowork.so
- OK Parser: graphql              ABI: 13, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/graphql.so
- OK Parser: groovy               ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/groovy.so
- OK Parser: html                 ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/html.so
- OK Parser: http                 ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/http.so
- OK Parser: hurl                 ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/hurl.so
- OK Parser: ini                  ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/ini.so
- OK Parser: java                 ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/java.so
- OK Parser: javascript           ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/javascript.so
- OK Parser: jq                   ABI: 13, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/jq.so
- OK Parser: jsdoc                ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/jsdoc.so
- OK Parser: json                 ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/json.so
- OK Parser: json5                ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/json5.so
- OK Parser: latex                ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/latex.so
- OK Parser: lua                  ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/lua.so
- OK Parser: luadoc               ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/luadoc.so
- OK Parser: make                 ABI: 13, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/make.so
- OK Parser: markdown             ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/markdown.so
- OK Parser: markdown_inline      ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/markdown_inline.so
- OK Parser: meson                ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/meson.so
- OK Parser: ninja                ABI: 13, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/ninja.so
- OK Parser: nix                  ABI: 13, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/nix.so
- OK Parser: perl                 ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/perl.so
- OK Parser: php                  ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/php.so
- OK Parser: pug                  ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/pug.so
- OK Parser: python               ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/python.so
- OK Parser: regex                ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/regex.so
- OK Parser: requirements         ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/requirements.so
- OK Parser: ruby                 ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/ruby.so
- OK Parser: rust                 ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/rust.so
- OK Parser: scala                ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/scala.so
- OK Parser: scss                 ABI: 13, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/scss.so
- OK Parser: sql                  ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/sql.so
- OK Parser: ssh_config           ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/ssh_config.so
- OK Parser: starlark             ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/starlark.so
- OK Parser: svelte               ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/svelte.so
- OK Parser: toml                 ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/toml.so
- OK Parser: typescript           ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/typescript.so
- OK Parser: vim                  ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/vim.so
- OK Parser: vimdoc               ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/vimdoc.so
- OK Parser: vue                  ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/vue.so
- OK Parser: xml                  ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/xml.so
- OK Parser: yaml                 ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/yaml.so
- OK Parser: yuck                 ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/yuck.so
- OK Parser: zig                  ABI: 14, path: /home/zeltron/.local/share/nvim/site/pack/deps/opt/nvim-treesitter/parser/zig.so
- OK Parser: c                    ABI: 14, path: /home/zeltron/.local/share/bob/nightly/lib/nvim/parser/c.so
- OK Parser: lua                  ABI: 14, path: /home/zeltron/.local/share/bob/nightly/lib/nvim/parser/lua.so
- OK Parser: markdown             ABI: 14, path: /home/zeltron/.local/share/bob/nightly/lib/nvim/parser/markdown.so
- OK Parser: markdown_inline      ABI: 14, path: /home/zeltron/.local/share/bob/nightly/lib/nvim/parser/markdown_inline.so
- OK Parser: query                ABI: 14, path: /home/zeltron/.local/share/bob/nightly/lib/nvim/parser/query.so
- OK Parser: vim                  ABI: 14, path: /home/zeltron/.local/share/bob/nightly/lib/nvim/parser/vim.so
- OK Parser: vimdoc               ABI: 14, path: /home/zeltron/.local/share/bob/nightly/lib/nvim/parser/vimdoc.so
- Can load WASM parsers: false

Minimal vimrc that can reproduce this bug.
Any minimal setup with everforest colorscheme and mini.statusline configured.
Steps to reproduce this bug using minimal vimrc
Open the editor with everforest colorscheme.
You can see that the section for filename and section for diagnostics and filetype colors are swapped and the dark one is used for diagnostics and filetype sections while lighter one is used for filename sections.

Expected behavior
The colors to be swapped to look like ones in the screenshot in README.md of this colorscheme repo.
Actual behavior
They look the opposite.

This was a conscious styling decision from the author of mini.nvim, who contributed this to Everforest (if I remember correctly).
The way colors are distributed among the different sections of status bars is highly dependent on what these sections actually contain. With that being said, I agree that we should be consistent across status bars and will see how I can improve the current mini.nvim styling.

I just looked into this issue (sorry for the delay!).
Here is the statusline generated by mini.statusline with plain defaults:
:=MiniStatusline.active()
%#MiniStatuslineModeNormal# Normal %#MiniStatuslineDevinfo#  main  +6 %<%#MiniStatuslineFilename# %F%m%r %=%#MiniStatuslineFileinfo#  lua utf-8[unix] 21.42KiB %#MiniStatuslineModeNormal# %l|%L│%2v|%-2{virtcol("$") - 1}

It look different from what can be seen in your screenshot:

The middle part has the same background as the main window, which is wrong, but other than that the shades look close to what you expected I guess?

I just looked into this issue (sorry for the delay!).
Here is the statusline generated by mini.statusline with plain defaults:
:=MiniStatusline.active()
%#MiniStatuslineModeNormal# Normal %#MiniStatuslineDevinfo#  main  +6 %<%#MiniStatuslineFilename# %F%m%r %=%#MiniStatuslineFileinfo#  lua utf-8[unix] 21.42KiB %#MiniStatuslineModeNormal# %l|%L│%2v|%-2{virtcol("$") - 1}

It looks different from what can be seen in your screenshot:

The middle part has the same background as the main window, which is wrong1, but other than that the usage of shades is what you expected I guess?
Footnotes
1. <img alt="image" width="364" src="https://github.com/user-attachments/assets/e6320125-1809-4bd2-8752-625b688b4375">
   [↩](#user-content-fnref-1-ab97440b8d484a163f93aed4f66ca640)

Hi yeah. Altough the middle part is also coloured according to the picture in README.md and is not the same color as background.

I just drafted a fix, what do you think about it?

I just drafted a fix, what do you think about it?

Yup this seems to be right! Thank you for accomodating the change. All other mini.plugins that I use have correct highlighting. This was the only issue I found.


Something wrong with lab key selling prices

General information
Project issue is for:
Dont really know
Expected result:
To sell green lab key for ~1.000.000
Actual result:
I sold it for ~10.000.000
So, i can buy green lab key for 8-9kk on flea and sell it for 10kk to therapist. Prices are broken for ALL lab keys (green, red...). Tested with and without mods (deleted "plugins" and "mods" with creating new easy start profile)
How to reproduce

Find green, red... lab key on flea
Buy it
Sell to therapist

Attachments

server-2024-09-08.log (1462 KiB)
LogOutput.log (35 KiB)
2024.09.08_14-59-48_<IP_ADDRESS>.30626 traces.log (44 KiB)
image.png (1601 KiB)

Originally written by DaytonFox

This is caused by changes BSG made to live that tanked the price of keycards, which is being imported via the Live Flea Prices mod.
SPT uses the higher of either the listed flea price, or the Handbook price as the base price for items. In this case, while Live Flea Prices sets the flea price to 1.8 million, the handbook price for SPT 3.9.8 (And in live 0.14.9) is 11.8 million, resulting in the behaviour you're seeing
tl;dr: Not an SPT bug, BSG changed the price of keycards in live

Originally written by DrakiaXYZ

This is caused by changes BSG made to live that tanked the price of keycards, which is being imported via the Live Flea Prices mod.
SPT uses the higher of either the listed flea price, or the Handbook price as the base price for items. In this case, while Live Flea Prices sets the flea price to 1.8 million, the handbook price for SPT 3.9.8 (And in live 0.14.9) is 11.8 million, resulting in the behaviour you're seeing
tl;dr: Not an SPT bug, BSG changed the price of keycards in live

But flea prices still less than 10kk selling price, any fixes for this? And 10kk "problem" will be "fixed" will next updates?

Originally written by DaytonFox

The flea price for keycards is only less than the vendor sell price if you're running Live Flea Prices or some other mod that adjusts flea prices to be lower than vendor prices. If that happens, SPT utilizes the vendor price as a base price, with a random up/down adjustment, which means items can end up cheaper than the vendor price
SPT with no flea price adjusting mods will not have this issue

Originally written by DrakiaXYZ

The flea price for keycards is only less than the vendor sell price if you're running Live Flea Prices or some other mod that adjusts flea prices to be lower than vendor prices. If that happens, SPT utilizes the vendor price as a base price, with a random up/down adjustment, which means items can end up cheaper than the vendor price
SPT with no flea price adjusting mods will not have this issue

do you know is this issue works only on lab keys?

Originally written by DaytonFox

It will happen on anything that has a lower current live flea price than its vendor price was in 0.14.9

Originally written by DrakiaXYZ

It will happen on anything that has a lower current live flea price than its vendor price was in 0.14.9

thx. meanwhile i found another issue. I can sell items without "finded in raid" status. should i create new ticket (all logs will be same)?

Originally written by DaytonFox

It will happen on anything that has a lower current live flea price than its vendor price was in 0.14.9

thx. meanwhile i found another issue. I can sell items without "finded in raid" status. should i create new ticket (all logs will be same)?

This is how it is on live now too.

Originally written by Lacyway


Add support for submitting build step as a job rather than build locally

This feature is would help us a lot because we have a heterogenous cluster, so the microarchitecture of the login node is not necessarily the same as that of the compute nodes.

Hi @smoors , if we add an attribute to the test so that the building happens remotely in the valid system you have chosen, would that be a solution for you?


vscode e2e flakiness: increase timeout on inputbox

see: https://github.com/metalbear-co/mirrord/actions/runs/5200449364/jobs/9379382868?pr=1496
waiting on release after https://github.com/redhat-developer/vscode-extension-tester/issues/821 has been closed

same issue: https://github.com/redhat-developer/vscode-extension-tester/issues/214

@eyalb181 not yet, this needs to be resolved on the library end I believe, ill give this another try today


Brand Colour Correction

The Pull Request is purely a colour correction for the Brand Colour

[x] I attest that the connector doesn't exist on the Power Platform today. I've verified by checking the pull requests in GitHub and by searching for the connector on the platform or in the documentation.
[x] I attest that the connector works and I verified by deploying and testing all the operations.
[x] I attest that I have added detailed descriptions for all operations and parameters in the swagger file.
[x] I attest that I have added response schemas to my actions, unless the response schema is dynamic.
[x] I validated the swagger file, apiDefinition.swagger.json, by running paconn validate command.
[x] If this is a certified connector, I confirm that apiProperties.json has a valid brand color and doesn't use an invalid brand color, #007ee5 or #ffffff. If this is an independent publisher connector, I confirm that I am not submitting a connector icon.

Hello @thedarkjester,
Congratulations, your PR is approved and merged. Please update your submission in ISV Studio by using the latest commit ID.
Let us know if you have any questions.


fixed #74, adding support for Laravel 5.1

I'm not able to run the tests because of the following error, but this should fix the error with Laravel 5.1. It's also the way the firstByAttribute is suggested to be replaced: https://github.com/laravel/framework/pull/7303
PHPUnit 4.7.5 by Sebastian Bergmann and contributors.

Runtime:	PHP 5.5.20
Configuration:	/Users/fabianpimminger/Development/forks/LaravelFacebookSdk/phpunit.xml.dist

.......PHP Fatal error:  Call to a member function connection() on a non-object in /Users/fabianpimminger/Development/forks/LaravelFacebookSdk/vendor/illuminate/database/Eloquent/Model.php on line 3138

Any idea what's the problem here?

Thanks for the contribution @fabianpimminger! I had already asked @nkwaerd to do this in #74 and he sent a new PR in #80 with the fix. Although both of these PR's break the tests so I'm going to fix those now and tag a stable 3.0 release for Laravel 5.1 people.


Behat dependency fails installation due to higher version of PHP required

executing composer require behat/behat --dev with php 5.5.38. I get the following output. behat/behat should support above 5.3.2.

that's not related to Behat, that's related to your existing dependencies (doctrine/annotations is marked as locked in the output, which means it is already part of your project).
It looks like your existing lock file was generated with a newer PHP version, and so your local set of dependencies is not compatible with PHP 5.5.38. Try running composer install instead. I'm quite sure it will fail in the same way.
composer require performs a partial update, which means that the solver is not allowed to upgrade or downgrade any of your existing packages, and so it cannot downgrade doctrine/annotations.

I'm closing this issue, as it has nothing to do with Behat (try with any other package name in your broken project, and they will also fail...)


Fix autoslug generation when existing model is copied

Fixes the issue described by @tisdall in #1171 that occurs when an existing autoslug model is copied.

Coverage remained the same at 54.513% when pulling 3eaa21c694a45e8d5f427ccb1c124dfaa4b67b1c on cloudsmith-io:bugfix-slug-copy into b1a8efd61c9aab8366b8e50df67d0c41229b9599 on django-extensions:master.

Thanks !


Unable to delete files

I am not able to delete files stored on iCloud storage using the delete function. The function doesn't throw any error, but listFiles as well as watchFiles still returns that file, which i just deleted.
Can you please confirm, if delete operation takes some time to reflect, and if yes then how much?

I have the same problem. I don't know the reason behind it, but the native code cannot find the file and therefore also not remove it, so soon as the is an underscore in the filename.

It seems you have to download the files first, before you can delete them. The list shows you all files in the iCloud. But I was only able to delete the ones I either uploaded from that device, or downloaded to the current device. Can anybody confirm, that this is the normal behaviour?

@REKURDennis You're correct. I am able to delete the files after downloading them.

This has been fixed in 0.2.3. Thanks for reporting this bug.


Proposal to make a new android Quiz App

Hello @aadityamp01
I want to add a Quiz Application for hacktoberfest,
Please assign this to me.

Okay, Go ahead!
Please Note:

Please go through README.md and CONTRIBUTING.md
Already existing apps on github will be considered as spam, try to make your own UI
Please use appropriate comments to self describe your code
Add necessary readme.md - references of your learnings and dependencies, images (screenshots); refer latest added apps for this task.

Assigning to you!

Thanks for assigning me. 🙂🙂


Indicator showing who the card played will affect

Maybe some sort of arrows pointing to them

https://www.gamedeveloper.com/business/how-to-work-with-bezier-curve-in-games-with-unity


[SMALLFIX] Made field a local variable in BlockMetaTest

Made a field a local variable in the BlockMetaTest class.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Alluxio-Pull-Request-Builder/9963/
Test PASSed.

Merged build finished. Test PASSed.

LGTM. Thanks


Unlisted requirement on packaging?

I recently tried to update some pre-existing code that was using dask_searchcv to use dask_ml, but my 1-2 line change didn't seem to take.
In particular, I received this error which seemed to indicate that I need packaging (this?) to run. Is this expected?
  File "/opt/python/common/model/runner.py", line 11, in <module>
    from dask_ml.model_selection import GridSearchCV
  File "/usr/local/lib/python3.6/site-packages/dask_ml/model_selection/__init__.py", line 6, in <module>
    from ._search import (
  File "/usr/local/lib/python3.6/site-packages/dask_ml/model_selection/_search.py", line 9, in <module>
    import packaging.version
ModuleNotFoundError: No module named 'packaging'

Thanks. How'd you install dask-ml?

We should probably include setuptools in https://github.com/dask/dask-ml/blob/master/setup.py#L13 directly.

How'd you install dask-ml?

I did this:
pip install dask-ml[xgboost]


cmd/atlas/apply: without printing diff

good catch, missed on the merge.
On Wed, Nov 10, 2021 at 1:49 PM Rotem Tamir @.***>
wrote:

@.**** commented on this pull request.
In cmd/atlas/mux.go
https://github.com/ariga/atlas/pull/211#discussion_r746512482:

@@ -93,10 +102,14 @@ func schemaNameFromDSN(url string) (string, error) {
}
return cfg.Database, err
default:

return "", fmt.Errorf("unknown database type: %q", key)

return "", errors.New("failed to get DB name from connection")

?
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/ariga/atlas/pull/211#pullrequestreview-802477760, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ABJYECWUAJSXTZZVHC5CUQ3ULJL3VANCNFSM5HXKG6CA
.


[java] Unusable code emitted when a field is overwritten

This is clearly an edge case, but I would still like to report it to gather feedback.
I keep finding this pattern:
openapi: 3.0.3
info:
  title: Test API
  description: "A test API"
  version: 0.13.0-SNAPSHOT
paths:
  /api/v1/users:
    get:
      summary: Retrieves a list of users
      description: "Returns a list of all users"
      responses:
        "200":
          description: List of users
          content:
            application/json:
              schema:
                $ref: '#/components/schemas/UserList'
components:
  schemas:
    List:
      required:
      - total
      - items
      type: object
      properties:
        kind:
          type: string
        items:
          type: array
          items:
            type: object
        total:
          format: int32
          description: Total number of entries in the full result set
          type: integer
          nullable: false
        size:
          format: int32
          description: Number of entries per page (returned for fetch requests)
          type: integer
        page:
          format: int32
          description: Current page number (returned for fetch requests)
          type: integer
    UserList:
      allOf:
      - $ref: '#/components/schemas/List'
      - description: List of users
        type: object
        properties:
          items:
            type: array
            items:
              type: string

The intention is clear, declare an abstract List and have concrete instances of it overwriting the items field.
It's pretty clearly not defined behavior, but I keep finding it in various places and it shows that, probably, OpenAPI tooling is handling this (most of those)cases according to the intention (as opposed to the spec).
Removing the items field from the "parent" produces the expected output.
Now, I'm not sure how to proceed here, should we fail instead of silently producing unusable code? Or should we handle this case(since is quite popular) with some kind of overwriting mechanism?

kiota should fail and tell you it doesn't know what to do with the items property in the List base type.

I just tested the snippet above with the CLI freshly built from main, if this is the expected behavior, is buggy 🐛 🙂 or there is something unexpected going on.
I completely understand the reasons for not doing more advanced "reasoning" and taking "smarter" decisions, completely fine by me as long as the validation rule kicks in.

what's the current behaviour you're experiencing?

code is generated, but the items field is unusable as it's not overwritten (e.g. the parent's type is used).

yeah that property should be skipped and a warning should be emitted since we don't have enough information. And resolving that would mean the derived type would have the property now (it's probably not adding it because it's in the parent).
Do you want to have a look at that?

I can have a look but I don't guarantee when 🙂 fortunately just got all the relevant PRs merged and this is not directly on my way at the moment.

@andreaTP I'm getting closer to being able to have a look at this one. Just wanted to confirm you're not working on it at this moment?

Thanks for checking, I confirm I'm not working on this currently (and tomorrow is liberation day in Pt 🙂 ).
Happy to see you around picking up the challenges @baywet 🙏 !

Actually sorry, I got confused while sorting through issues. Leaving this for now.

@papegaaij started some interesting work in the space with #2836 you might want to checkout @andreaTP

@andreaTP to resume our discussion from the PR here. As far as I can remember, from the PR mentioned in my last comment, any property that "overrides" a parent's type property will get a unique name so it doesn't hide it. During serialization/deserialization, due to the structure of things, it should also take precedence.
I don't think we need a warning anymore/action needs to be taken. Besides maybe verifying this is actually the case. Thoughts?

Ok, I took a look at the situation using kiota at version 1.9.0-preview.202311230001.

any property that "overrides" a parent's type property will get a unique name so it doesn't hide it.

Using the repro description in the initial report I cannot confirm that this is the current behavior.
The items  field in the UserList class is not present nor does it have a different name.
I think that this issue has to remain open, at least for now.


Apple Mach-O Linker Error

This is the error message:
ld: warning: directory not found for option '-L/Users/iDay/Documents/fishead/WeixinActivity/WeixinActivity/Resources'
ld: library not found for -lWeChatSDK
clang: error: linker command failed with exit code 1 (use -v to see invocation)
Any help please?

change 'LIBRARY_SEARCH_PATHS' in your project

How should I change this?


[zh-cn]sync network-plugins field-selectors replicaset statefulset

# Changes to be committed:
#       modified:   content/zh-cn/docs/concepts/extend-kubernetes/compute-storage-net/network-plugins.md
#       modified:   content/zh-cn/docs/concepts/overview/working-with-objects/field-selectors.md
#       modified:   content/zh-cn/docs/concepts/workloads/controllers/replicaset.md
#       modified:   content/zh-cn/docs/concepts/workloads/controllers/statefulset.md

/approve


Rft/add config enhance generic dubbo

添加 generic dubbo 样例
配置 .run 目录下 .xml 配置文件的环境变量和文件路径

please merge config-enhance.

Pls merge config-enhance branch and add array+=("generic/default") to pass ci check. @yaoyinnan

@LaurenceLiZhixin Please approve running CI workflows.

@LaurenceLiZhixin  Please approve running CI workflows.


Grid Layout added in Home Fragment along with ScrollView

Constraint --> ScrollView --> Constraint --> TV and RV

Will Accept after Review @RahulSoni0 .
Review Pending

Ok Checked . @RahulSoni0 merge to master
@Joaquin144  avoid using hindi comments😅🤣🤣

Thanks @Joaquin144


Make items on Installed charts page to be correct hyperlinks

To be able to open releases in a new browser tab, intuitively.
Installed charts in list should be correct links, and full row should be a link, not just header text.
Top menu items Installed/Repository should be correct links.
Revision links on the left should be correct links.

@ahaw023 this is from your feedback, thanks for your exciting demos

@undera can you please add more details for the below 2 items?

Top menu items Installed/Repository should be correct links.
Revision links on the left should be correct links.

We have a top menu items "Installed" and "Repository". Those are now not hyperlinks, and handled on JS side. Those should become valid hyperlinks, so I'm able to do right click on those and choose "Open in new tab".
Same kind of behavior is expected for items in Installed list and in Revision list.


Add tender_uaid to arguments

Add tender_uaid to keywords arguments because it was missed

This change is

Reviewed 3 of 3 files at r1.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Add continuous deployment

Deploy the website on a hosting platform preferably Netlify and use continuous deployment to keep track of latest release.

Deployed (here)[https://bug-busters-portfolio.netlify.app]


tuya shutter, the up button close and the down open

Describe the bug
tuya shutter, the up button close the shutter and the down open, and the percentage is also opposite from expected

Me too


Fix wrong name for kfserving-monitoring namespace

What this PR does / why we need it:
Right now the created namespace will get a kfserving- prefix which will create a namespace called kfserving-kfserving-monitoring.
This will make subsequent object creations to fail since they will be meant for the kfserving-monitoring namespace.
Here's the result of running kustomize build docs/samples/metrics-and-monitoring/prometheus-operator | k apply -f -, as the instructions suggest https://github.com/kubeflow/kfserving/blob/master/docs/samples/metrics-and-monitoring/README.md#install-prometheus
namespace/kfserving-kfserving-monitoring created
customresourcedefinition.apiextensions.k8s.io/alertmanagerconfigs.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/alertmanagers.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/podmonitors.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/probes.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/prometheuses.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/prometheusrules.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/servicemonitors.monitoring.coreos.com created
customresourcedefinition.apiextensions.k8s.io/thanosrulers.monitoring.coreos.com created
clusterrole.rbac.authorization.k8s.io/kfserving-prometheus-operator created
clusterrolebinding.rbac.authorization.k8s.io/kfserving-prometheus-operator created
Error from server (NotFound): error when creating "STDIN": namespaces "kfserving-monitoring" not found
Error from server (NotFound): error when creating "STDIN": namespaces "kfserving-monitoring" not found
Error from server (NotFound): error when creating "STDIN": namespaces "kfserving-monitoring" not found

Which issue(s) this PR fixes
Bumped into this while working on extending the current monitoring manifests with the InferenceServices web app #1328
Special notes for your reviewer:
This is because the kustomization.yaml file for the prometheus-operator defines a kfserving- prefix and the namespace's name is also kfserving-monitoring as well, which results in this duplication.

I'll also mention some relevant people based on @animeshsingh's comment https://github.com/kubeflow/kfserving/pull/1328#issuecomment-797797948. Hope I'm not missing someone!
/cc @pvaneck @sriumcp @yuzisun @Tomcli
/assign @kimwnasptd

/lgtm

/approve


Release v0.2.0

Update pod versions and migrate to Swift 5 #22

wait until #24 is merged as the readme updates needs to get in with this PR


Is shuffle batch norm tied with momentum contrast training?

Hi, first thank you for the work. I am wondering if one wants to use shuffle BN, the training has to be in the momentum update fashion. Because it seems to me that in shuffle BN, the encoder which encodes the shuffled batch cannot be updated by backprop even if one wants to. Is this a correct understanding or am I getting something wrong? Thank you.

You can implement backward for the shuffling if you need. MoCo does not need this, so it was not implemented.

thank you for the quick reply! But in that case, in one gpu, it needs to backprop the encoding calculated by models from other gpus. Is it possible through pytorch DDP? When I am trying the shuffle BN, I keep getting such errors:
RuntimeError: Expected to have finished reduction in the prior iteration before starting a new one. This error indicates that your module has parameters that were not used in producing loss. You can enable unused parameter detection by (1) passing the keyword argument find_unused_parameters=Truetotorch.nn.parallel.DistributedDataParallel; (2) making sure all forward function outputsparticipate in calculating loss.
and I know this is caused by the shuffle BN. I am not sure how to further debug this. I am suspecting that pytorch couldn't figure out how to backprop here. I would greatly appreciate any help!

pytorch has some tutorials for how to implement backward for a function, e.g. https://pytorch.org/tutorials/beginner/examples_autograd/two_layer_net_custom_function.html

Ah I see. So I should implement backprop for _batch_shuffle_ddp and _batch_unshuffle_ddp to show pytorch which gpu the encoding is from? It doesn't sound straightforward to me and I need to think about it... Thank you again for the prompt help!

One more question to confirm if my understanding of shuffle BN is correct:
The reason shuffle BN is needed is because if using standard BN in DDP, the query and its correct key would be encoded using the same (or strongly correlated) batch stats, while the incorrect key would likely be encoded using different batch stats since they are trained in a different batch. By using shuffle BN, the query and its correct key are also encoded using different batch stats. This effectively solve the cheating issue where the model finds the correct key based on the batch stats.

Hello @dongyaoli10x.
Did you solve the problem? Could you share your backprop implementations?
Best regards.


Unstable results on every new process when I restarted the server

This is the python code I used for generating trees from my data.
params = {
    'objective': 'binary',
    'deterministic': True,
    'force_row_wise': True,
    'num_threads': 8,
    'learning_rate': 0.05,
    'max_depth': 3,
    'tree_learner': 'data',
    'boosting_type': 'gbdt',
    'feature_fraction': 0.7,
    'bagging_fraction': 0.8,
    'bagging_freq': 5,
    'verbose': -1,
    'seed': 8,
}
random.seed(8)
np.random.seed(8)

dataset = lgb.Dataset(X, y)
bst = lgb.train(params, dataset, 10, keep_training_booster=True)
trees = bst.dump_model()["tree_info"]

I was testing it out on my local macbook M2 machine with a flask server.

The code does give me stable result when I run the algorithm in a row without restarting the process.
Every time when I reboot the server, it always give me a new randomized version of the code.
I've tested out every possible instruction in https://lightgbm.readthedocs.io/en/latest/Parameters.html
I've even tried setting the random seed of python / numpy, but it doesn't work
I've also disabled parallelism by setting num_threads to 1, but it doesn't help

Thanks for using LightGBM.
Can you please try to provide a minimal, reproducible example? I don't understand what you mean by the following:

"run the algorithm in a row"
"new randomized version of the code"
"setting the random seed of Python"

Please also provide the details that the issue template asked for, including:

what version of LightGBM?
what commands did you run to install it?
what operating system are you on?

I see you've also double-posted this to Stack Overflow (link). Please do not do that.
We monitor the [lightgbm] tag on Stack Overflow just like we monitor this issues page.... it's possible that I could have been responding to you on Stack Overflow at the same time someone else was responding here, which would have been a waste of maintainers' very limited time. Double-posting can also make it less likely that others facing the same issue will be able to find the answer from search engines.


R.Swift not working in Development Pod

I am trying to create Resources dev pod, but R.swift generate empty(with default code only) R.generated.swift
"$PODS_ROOT/R.swift/rswift" generate "$SRCROOT/Modules/ModuleName/R.generated.swift"

I also added sub-arguments --xcodeproj --target, --project --input-files, but still no output from script

For some reason, "Copy bundle resources" in DevPod is empty. Trying to understant why to fix that

--target ${PRODUCT_NAME}-Resources resolve it


Refac/opacity

reduced computation time for hjert and ljert in 25%.
added a unit test for ljert

self merge


Button-group is not working on ipad

Button-group is not working on ipad. It's not even showing the active button with blue color.
I have imported all the button-group related css files

It sounds like the styles are being not imported correctly.
I have two simple examples below one for Polymer 1 and one for Polymer 2. Both examples work in  safari & chrome mobile.
My .scss file
$inuit-enable-btn--primary : true;
@import 'px-buttons-design/_objects.buttons.scss';
@import "px-button-group-design/_objects.button-group.scss";

Polymer 2 example. The way styles are imported in Polymer 2 has changed. Note you can only have one  in a <custom style></custom style>.
<!DOCTYPE html>

  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <title>Predix UI</title>

  <link rel="import" href="../../polymer/polymer.html" />
  <link rel="import" href="../../px-theme/px-theme-styles.html">
  <link rel="import" href="../css/px-button-styles.html" />

  <custom-style>

  </custom-style>
  <custom-style>

  </custom-style>

  <button class="btn">Label</button>

    <input id="id1" name="btn-group"  type="radio">
    Label 1
    <input id="id2" name="btn-group"  type="radio">
    Label 2

Polymer 1 example
<!DOCTYPE html>

  <meta charset="utf-8">
  <meta name="viewport" content="width=device-width, initial-scale=1">
  <title>Predix UI</title>

  <link rel="import" href="../../polymer/polymer.html" />
  <link rel="import" href="../../px-theme/px-theme-styles.html">
  <link rel="import" href="../css/px-button-styles.html" />

  <button class="btn">Label</button>

    <input id="id1" name="btn-group"  type="radio">
    Label 1
    <input id="id2" name="btn-group"  type="radio">
    Label 2

button group is not working in mobile as well.
Even below example is not working as expected
https://www.predix-ui.com/#/css/visual/buttons/px-button-group-design

select label 1 (button 1)
now try to click 2nd button. it wont work. it wont work in any touch devices. Only mouse click is working as of now

This is actually a known limitation of the label tag on WebKit mobile, they disable the behavior of automatically toggling a checkbox / radio button or focusing an input field, presumably to prevent interference with the tap-and-hold-to-select-text interaction. Aside from wrapping this component as a Polymer component, I'm not sure there's a pure HTML/CSS way to make this component work on mobile.


Deterministic noise with different batch sizes

Currently supporting smaller batch sizes with an offset. See if we can make this cleaner:
okay this self.offset thing is a bit gnarly, but I think we should just revisit this.
I have a few ideas how to fix this later
Originally posted by @turian in https://github.com/turian/torchsynth/pull/247#r606004673

Now supports batch size multiples of 32


Provider for Philippines?

Hello Sir @stelgenhof,
I tried to use this package and it's actually great. I'm actually interested to create a provider for Philippines holidays because as of the moment, there's no open-source projects written yet for providing data for Philippine holidays in PHP. Will it be alright if I will try to contribute something to the project?
Cheers and regards,

Hi @Angelo8828,
Thank you for willing to contribute to this library. New countries are more than welcome! The best way to get started is by looking at other country providers (you can even copy one as a begin).
Let me know if you have any questions.
Cheers! Sacha


Fix Unfollow/Follow button font size

In particular, the "Unfollow" button looks too big for the space allotted.  This is the kind of little thing that hampers the site's credibility. Need to reduce font size.

This is fixed on production.


Sema: Downgrade potentially unavailable enum cases to a warning in module interfaces [5.5]

There are two pieces here:

A -warn-on-potentially-unavailable-enum-case flag is passed down by
the driver when producing a swiftinterface

When consuming a swiftinterface, also enable this behavior

Part of rdar://problem/78306593.

Build failed
Swift Test Linux Platform
Git Sha - 2fb3f6d31570c1cc7feb772b6e0f419a9eb8c97b

Build failed
Swift Test OS X Platform
Git Sha - 2fb3f6d31570c1cc7feb772b6e0f419a9eb8c97b

https://github.com/apple/swift-driver/pull/708
@swift-ci Please test

Build failed
Swift Test OS X Platform
Git Sha - 2fb3f6d31570c1cc7feb772b6e0f419a9eb8c97b

apple/swift-driver#708
@swift-ci Please test macOS

apple/swift-driver#708
@swift-ci Please test Windows


Darkmode added in mobile dimensions

Fixes Issue
Closes #451

Changes proposed
The darkmode is added in mobile dimensions also.

Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[ ] My change requires changes to the documentation.
[ ] I have updated the documentation accordingly.
[ ] All new and existing tests passed.

Heyy could u change it like this! Currently visibility of dark/light mode is not that much in mobile menu..

Yes .SURE!!

Done . Now it is looking like the second screenshot .

Heyy..don't change the alignment of the current button! I told you to improve the visibility of the button as it is in website view

See it's not that visible!

Now the button is aligned back to its position and it's visibility is improved in the dark mode.

Can you please attach labels to this PR?

Can you please attach labels to this PR?

Hey level labels are added to issues not PRs!

Oh .Thanks for the information.


Allow container-specific IPC

Unix IPC primitives are a bit nasty in a shared environment: by default, they are system-wide, a scarce resource, and not automatically cleaned up when the invoking process exits.
If available, utilize the CLONE_NEWIPC flag so containers don't leak Unix IPC usage.

I used to have this enabled, but I think I disabled it due to it breaking some MPI communication pathways. I will have to go back and see why I disabled and retest now that we know MPI is working properly.

I would imagine this has the potential to break MPI (well, and Postgres servers - let's hope that's not a problem!) - but, OTOH, it's tiring and painful to clean up IPC after poorly written jobs.
It should be possible to unshare the MPI process into the same IPC namespace as the container.

This should also be easily setup to be a configurable option as the PID namespace is.
I am not sure about joining the orted/MPI IPC namespace, but that is an interesting idea. With the Open MPI modular architecture, it should be pretty easy to inject some code to make sure we join the PPID's namespace (using setns()). This might prove to be temperamental but would be very interesting to implement.

CLONE_NEWIPC is now in [master 140ff41]. Thanks!


Switch to yarn

Fixes #24

@ivaibhavjindal Did you test run the bot after making the migration?

Yes I did and it was working perfectly.

Great. Merging it in. Thanks 👍💯


[WIP] virtcontainers: support network hotplug

At present, only implement the add network, the function entry is:
func addNetworkToPod(podID,  ifName string) error

The function accepts two parameters: pod ID and net interface name. Other network information will be obtained by virtcontainers according to ifName.
This is only the initial completion of the basic code flow, but has not yet been functionally tested.
/cc @sboeuf
Signed-off-by: Yanqiang Miao<EMAIL_ADDRESS>

@sboeuf I'm not familiar with qmp, so I'm not sure the code in this PR can work, so hope to get your guidance. :-P

@miaoyq I'll take a look. Just wanted to let you know I didn't forget your PR !


CommonPickerModel is not public

How exactly we can customize it, if main class is not public and variables controlling date picker are private ?
I mean I can extend model, but I cannot access private params such as:
_currentLeftIndex = 0;
_currentMiddleIndex = this.currentTime.hour;
_currentRightIndex = this.currentTime.minute;

So please change it add add customisation docs

yes, properties with _ are private, but you can override methods defined in BasePickerModel

Ok will try that, thx


Fix issue 137: added Transform.CurrentRawRecord() for caller of omniparser to access the raw ingested record.

Fix #137

FYI @DGollings

FYI @DGollings

Cool, thanks. Two remarks:

Maybe instead of returning interface{} return say
type RawRecorder interface {
  UUIDv3() // (or Checksum() if you want to be more schema agnostic)
}

That way a user can get useful output without any casts or RTFM, if they want more they can always cast to actual type.

I kind of liked the output of
            "hash_json_input": { "custom_func": {
                "name": "javascript_with_context",
                "args": [ { "const": "_node" } ]
            }},

Seeing that say SG25/SG26/position had value "1" is much clearer than the concatenated fieldless output of rawRecord.Node.InnerText()
Had a look around, none of the simpel options (json.marshal and Sprintf("%+v") resulted in similar output. Could probably generate similar output by walking the tree but that's non-trivial code. Was wondering if you had a better solution.
Although this is not really an issue, I already store a checksum of the entire schema, so if schemaChecksum == storedChecksum && rawRecordChecksum == storedRecordChecksum I can safely assume that the schema can be used to debug an original input file. Even without knowing the exact input.
And in a sense, that's better, I can feed the transformed output to a retry function (fixing import errors), I can't feed {""SG25/SG26/position" : "1"} to anything. Well, not without making changes
For context, say fixing an incomplete address for delivery purposes.
rawRecord.UUIDv3() + transformed output is probably better, I just kind of liked how hash_json_input/_node looked :)

Cool, thanks. Two remarks:

Maybe instead of returning interface{} return say
type RawRecorder interface {
  UUIDv3() // (or Checksum() if you want to be more schema agnostic)
}

That way a user can get useful output without any casts or RTFM, if they want more they can always cast to actual type.

I kind of liked the output of
            "hash_json_input": { "custom_func": {
                "name": "javascript_with_context",
                "args": [ { "const": "_node" } ]
            }},

Seeing that say SG25/SG26/position had value "1" is much clearer than the concatenated fieldless output of rawRecord.Node.InnerText()
Had a look around, none of the simpel options (json.marshal and Sprintf("%+v") resulted in similar output. Could probably generate similar output by walking the tree but that's non-trivial code. Was wondering if you had a better solution.
Although this is not really an issue, I already store a checksum of the entire schema, so if schemaChecksum == storedChecksum && rawRecordChecksum == storedRecordChecksum I can safely assume that the schema can be used to debug an original input file. Even without knowing the exact input.
And in a sense, that's better, I can feed the transformed output to a retry function (fixing import errors), I can't feed {""SG25/SG26/position" : "1"} to anything. Well, not without making changes
For context, say fixing an incomplete address for delivery purposes.
rawRecord.UUIDv3() + transformed output is probably better, I just kind of liked how hash_json_input/_node looked :)

given we have vastly different implementation of schema handlers across different versions I don't want to force any constraints (e.g. an interface) onto what each schema handler want to define as a raw record. It's highly version specific. So no.

you can use idr.JSONify2(*idr.Node) to marshal an IDR tree into a mimified JSON blob. That's how javascript_with_context does it.

given we have vastly different implementation of schema handlers across different versions I don't want to force any constraints (e.g. an interface) onto what each schema handler want to define as a raw record. It's highly version specific. So no.

you can use idr.JSONify2(*idr.Node) to marshal an IDR tree into a mimified JSON blob. That's how javascript_with_context does it.

but it wouldn't enforce anything regarding implementation, constraints or definition of a raw record in any way? The only thing it would enforce would be the existence of a function called Hash() or Checksum(), which returns a string, and that string could be "not implemented"
thanks :)

but it wouldn't enforce anything regarding implementation, constraints or definition of a raw record in any way? The only thing it would enforce would be the existence of a function called Hash() or Checksum(), which returns a string, and that string could be "not implemented"
thanks :)

After some thinking, I agree with 1, PR coming.

After some thinking, I agree with 1, PR coming.