[NetAppFiles] Apply 2020-12-01 api-version and recordings

https://github.com/Azure/azure-rest-api-specs/pull/13388
All SDK Contribution checklist:
This checklist is used to make sure that common guidelines for a pull request are followed.

[ ] Please open PR in Draft mode if it is:

Work in progress or not intended to be merged.
Encountering multiple pipeline failures and working on fixes.

[x] If an SDK is being regenerated based on a new swagger spec, a link to the pull request containing these swagger spec changes has been included above.
[x] I have read the contribution guidelines.
[x] The pull request does not introduce breaking changes.

General Guidelines and Best Practices

[x] Title of the pull request is clear and informative.
[x] There are a small number of commits, each of which have an informative message. This means that previously merged commits do not appear in the history of the PR. For more information on cleaning up the commits in your PR, see this page.

Testing Guidelines

[x] Pull request includes test coverage for the included changes.

SDK Generation Guidelines

[x] The generate.cmd file for the SDK has been updated with the version of AutoRest, as well as the commitid of your swagger spec or link to the swagger spec, used to generate the code. (Track 2 only)
[x] The *.csproj and AssemblyInfo.cs files have been updated with the new version of the SDK. Please double check nuget.org current release version.

Additional management plane SDK specific contribution checklist:
Note: Only applies to Microsoft.Azure.Management.[RP] or Azure.ResourceManager.[RP]

[x] Include updated management metadata.
[x] Update AzureRP.props to add/remove version info to maintain up to date API versions.

Management plane SDK Troubleshooting

If this is very first SDK for a services and you are adding new service folders directly under /SDK, please add new service label and/or contact assigned reviewer.
If the check fails at the Verify Code Generation step, please ensure:

Do not modify any code in generated folders.
Do not selectively include/remove generated files in the PR.
Do use generate.ps1/cmd to generate this PR instead of calling autorest directly.
Please pay attention to the @microsoft.csharp version output after running generate.ps1. If it is lower than current released version (2.3.82), please run it again as it should pull down the latest version,

Old outstanding PR cleanup
Please note:
If PRs (including draft) has been out for more than 60 days and there are no responses from our query or followups, they will be closed to maintain a concise list for our reviewers.

Note we had issues with generated validation code (not checking for null values) causes issues for SDK clients such as powershell. See: Azure/autorest#3585
However that issue seems to have been fixed and we can use that fix that issue by running autorest with
--use<EMAIL_ADDRESS>like so:
autorest.cmd https://github.com/Azure/azure-rest-api-specs/blob/master/specification/netapp/resource-manager/readme.md --csharp --version=v2 --use<EMAIL_ADDRESS>--reflect-api-versions --csharp-sdks-folder=C:\Users****\Source\repos\azure\azure-sdk-for-net\sdk
Now it looks like this shows in the pipeline as it thinks generated code was changed. It was not changed in this case. The tool in the pipeline probably uses generate.ps1 that creates a slightly different autorest command line command that would include this validation bug (not checking for nulls).
Is there a way to update the tooling to use this autorest cmd line or resolve this pipeline issue some other way?
update: I tried to update the generate.ps1 script and ran locally with updated autorest command that worked. But it seems like the validation tool is using some other autorest command so that does not fix the issue.
This was also flagged in previous version https://github.com/Azure/azure-sdk-for-net/pull/18851

@JonathanCrd The CI issue is due to the pipeline incorrectly assumes discrepancy with generated code and reference code, it thinks generated code has been changed. It has not been changed and this was an issue with last release as well due to AutoRest flags being used.
@allenjzhang can you assist with this issue?

@JonathanCrd Jonathan Cardenas FTE The CI issue is due to the pipeline incorrectly assumes discrepancy with generated code and reference code, it thinks generated code has been changed. It has not been changed and this was an issue with last release as well due to AutoRest flags being used.
@allenjzhang Allen Zhang (DEVDIV) FTE can you assist with this issue?

Yes, the reason they are failing it's because the version is hardcoded in the generate script.
Everything looks good, so I'm going to merge this PR.

/azp run net - mgmt - ci


git remote config

instead of half blah please make a video to setup a git remote repository.
and at the gui in the ide the textboxes need a hint.
we already have a git server running in intranet
in tortoise it looks like
git@ip:Company/IDE/Project.git
for ms vs 2022 ide i must google ...
[Enter feedback here]

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

ID: 12b2342e-c5d1-49d6-a36b-8c51a634af4d
Version Independent ID: f4fe13a4-7538-2d1e-d989-f0e2263e234f
Content: Git settings in Visual Studio
Content Source: docs/version-control/git-settings.md
Product: visual-studio-windows
Technology: vs-ide-general
GitHub Login: @Taysser-Gherfal
Microsoft Alias: tglee

@AuchMarkus -- Markus, thank you for your suggestions.  Please add them here:

Use the new Suggest a feature for Visual Studio IDE menu item.
Suggest a feature, track product issues, and find answers in the Visual Studio Developer Community.

Also, consider these resources:

Visual Studio on Microsoft Q&A
Visual Studio MSDN Forum
Stack Overflow
Reddit


list and export commands display different packages

Brief description of your issue

Shouldn't they be the same? Meaning the installed packages available on winget should be shown as available on winget both on the list list and the export list.
Steps to reproduce

Run:

winget list
winget export --output out.txt

Compare the two outputs.

Expected behavior

If a package is on the export list, then it's also displayed as available on the list list, and visa versa.
Actual behavior

Certain packages listed on the list list are shown as unavailable on the export list (and visa versa), e.g. 7-zip.
Environment
Windows Package Manager v1.0.11692
Windows: Windows.Desktop v10.0.17763.2145
Package: Microsoft.DesktopAppInstaller v1.12.11692.0

Any other software?

Can you please post screenshots for a better understanding of the issue?

Sure.
winget list

winget export

Also, why it add the extra space after semicolon?

Export would be the subset of packages that have been identified in one of the configured sources. Export should always at least be a subset of list, but not all packages are available in any known sources today. Many packages may not yet be in either the Microsoft Community Repository or the experimental store source.
We will have to look at the white space issue with the JSON output.

But in this case, export is a superset. It has things list doesn't have.
I'm not sure I follow the explanation. Export pulls from Community Repo and experimental store, while export pulls from those two + somewhere else? What is the reasoning behind this? Why not have them pull from the same sources?

The "Available" and "Version" column in the winget list output are displaying if a package has an upgrade available from a configured source. It doesn't provide an indication if there is a mapping to a source. My comment was in reference to the list command providing a list of "everything" installed on the machine (whether it's available in a configured source or not). The export command would be a subset of the installed packages based on those matched with a configured source. The UI is a bit confusing which is why we have added an issue for #1155 "Enhancements to list command" coming that should help provide a bit more clarity.

Oh I think I see now. Just to make sure I'm understanding correctly: if I want to know which of the installed packages is available through winget (no matter whether they were installed using winget or an exe/store/another package manager), list is useless, because it only says if an update is available through winget? Meaning 7-zip was listed only in export because I already have the latest version?
What do you mean by "a mapping to a source"? I tried searching through the linked issue and the repo but didn't find anything.

Sadly, yes, list isn't going to display all available packages until we get the other feature completed.
You may have more than one source. "winget" is the default source pointing to the community repository. We're also working on an experimental source for the Microsoft Store Apps. If that is enabled and/or you have private repositories configured, list would show upgrades available across sources. Similarly, if you had packages from more than one source, export would include Apps from all configured sources during export. The import side would only install Apps from configured sources, it will not automatically add additional sources, you would get a warning.

Okay thanks for a very thorough explanation and bearing with me. I think this can be closed? Since it's not a bug but my ignorance. Save for the white space part.

Feel free to close yourself.

I'm OK with leaving it open if you'd like the whitespace fixed.

@github-account1111 we're using a library to generate the file, and the whitespace doesn't seem to be trivial to address. I'm going to go ahead and close this as "not planned".


Undetected missing latex library detection in HTML version

Description
Paper uses a package (I thunk siunitx) which is not processed properly for the html version, but there is also no warning about the package being unimplemented.
(Optional:) Please add any files, screenshots, or other information here.
Can be observed in the abstract of the paper.
(Required) What is this issue most closely related to? Select one.
Other
Internal issue ID
e9014174-a74c-451a-b7ac-750f10136bd1
Paper URL
https://arxiv.org/html/2404.10866v1
Browser
Chrome/<IP_ADDRESS>
Device Type
Android

Also, it appears the figures are not showing properly, but there is also no warning there either.


Future of this package

I am looking for a pusher replacement package at the moment when i came across this one.
It looks like the development was very active a year ago but seems it stopped there.
Just asking if it is abandoned and i must look further, or can i safely use this in production?

Since I am not running in production anymore I don't have plans to add new features.
You could use it in production, but, at your own risk.
I am open to reviewing any contribution coming from the community, feel free to send any PR with anything you find.
Thanks for your interest.


refactor: allow procedure to acquire share lock

I hereby agree to the terms of the GreptimeDB CLA
What's changed and what's your intention?

Implement KeyRwLock
Use KeyRwLock instead of LockMap
Use StringKey instead of String
remove redundant code

Background
During reading the paper(Granularity of Locks and Degrees of Consistency in a Shared Data Base).
I realized that to acquire a lock on the subtree, there are two ways:

Implicitly locking: Hierarchical locking, Root-to-Leaf.
Explicitly locking: Leaf-to-Root (Locks an entire subtree is to lock each node of the subtree in leaf-to-root order)

We're stuck in the first way and always imagine we must acquire the lock in Root-to-Leaf order and need to employ something like a Hierarchical lock.
In fact, the order acquiring locks doesn't really matter in our scenario. We only have three levels, and it's enough to meet the invariant in our system if we acquire one lock on each level.
Invariant in our system

The same table's (different) Region migration procedures are compatible.
The same DB's Ops, DDL, and Region migration procedures are incompatible with one another.

Checklist

[x]  I have written the necessary rustdoc comments.
[x]  I have added the necessary unit tests and integration tests.
[x]  This PR does not require documentation updates.

Refer to a related PR or issue link (optional)
#2700

That paper is inspiring, maybe we need to adopt the whole idea from it, including lock scheduler and deadlock detection.

That paper is inspiring, maybe we need to adopt the whole idea from it, including lock scheduler and deadlock detection.

For deadlock detection, we now simply acquire all locks in the lexicographical order. I think it enough for now. cc @evenyag  @fengjiachun

@evenyag @MichaelScofield @fengys1996 @fengjiachun PTAL


Missing empty optional fields in response after create

Bug Report
Optional fields are missing from response when are not present during create.
Expected Behavior
When item is created and optional field is not present in payload then this field should be visible with null value.
Current Behavior
When item is created and optional field is not present in payload then this field is not visible in response.
Steps to Reproduce

Create collection with at least one not required field.
Create item with POST method and skip this field in payload.
Created item does not display this field.

Detailed Description
const Clients: CollectionConfig = {
  slug: "clients",
  admin: {
    useAsTitle: "name",
  },
  fields: [
    {
      name: "name",
      type: "text",
      required: true,
    },
    {
      name: "description",
      type: "text",
    },
  ],
}

Create request:
POST http://localhost:3000/api/clients
{"name": "Foo"}

Response:
{
    "message": "Client successfully created.",
    "doc": {
        "name": "Foo"
    }
}

Payload behavior for missing values being undefined instead of null is the way it is due to the underlying Mongo driver.
I think this is expected for any no-sql type database. If you wish to save or retrieve field values as null instead of undefined, you could consider adding afterRead or beforeChange hooks instead of undefined values if that is what you prefer from your API. I haven't tested what impacts that might have on the UI though so I can't say this is recommended.
I'm happy to discuss further or consider any documenation you can point me to if I'm missing something.


[Flaw] Cease sending users to malware distributing sites (here: APKPure)!

Jolla still suggests to use APKPure (apkpure.com, apkpure.net), despite APKPure having lost the fight against malicious APKs (e.g. "fake apps", "typo-squatting apps") years ago.  While APKPure was and still is one of the best curated, alternative sources for Android apps, simply downloading and installing apps from APKPure's web-site or via the APKPure client app is outright dangerous; only with much know-how, experience and checks & balances (e.g. tediously cross-checking hash values of downloaded APKs with the ones from other alternative app sources; i.e. one must not use the APKPure client app) an APK from APKPure can be assumed to be genuine.
Hence please do stop advertising APKPure and …

… eliminate all references to APKPure at jolla.com, i.e. on the "Services and Support" page (one reference) and in these Sailfish X installation guides (i.e. all of them, except the three for the Xperia X):

For the Xperia XA2 series (one reference): Linux, Windows, MacOS
For the Xperia 10 series (one reference): Linux, Windows, MacOS
For the Xperia 10 II (one reference): Linux, Windows, MacOS
For the Xperia 10 III (one reference): Linux, Windows, MacOS

… eliminate all references to APKPure at docs.sailfishos.org:

On the Android App Support page (two references)
Delete the complete APKPure directory
For other occurrences, see the results of this code search.

Mind that F-Droid.org and the Google Play Store (via Aurora Store app) are the only two major sources of Android apps, which are not significantly compromised by malware, e.g. "fake apps", "typo-squatting apps" etc.
P.S.: BTW, at a few places APKPure was misspelled as "APKpure".
P.P.S.: See also a similar issue report for Aptoide; eliminating both issues in one go likely requires less effort.

Point 2 in the initial message is resolved by PR #404.


Improve performance of calling ICustomTypeDescriptor.GetProperties

Hi,
I noticed this

A frequent performance issue that comes up is JSON.NET's JObject, which for reasons we haven't fully researched, has very slow reflection characteristics when used as a model in Handlebars.Net.

from https://github.com/rexm/Handlebars.Net/blob/master/README.md
also see https://github.com/rexm/Handlebars.Net/issues/56#issuecomment-114599359
I checked the code of ICustomTypeDescriptor.GetProperties and I see that PropertyDescriptorCollection starts with a capacity of 0... (see https://referencesource.microsoft.com/#System/compmod/system/componentmodel/PropertyDescriptorCollection.cs,97) - not sure if that's the real issue, but it isn't a good init capacity if you known the capacity already ;)
So I improved that by creating an own array and don't use the PropertyDescriptorCollection.Add

Thanks! Merged here https://github.com/JamesNK/Newtonsoft.Json/pull/2136


Adding HTTP header with empty string value yields confusing error #11032

Summary of the changes (Less than 80 chars)

Pre-Check headerValueBytes length
if header value is empty than throw exception with custom message

Addresses #11032

This also needs some tests

There's a case in the request headers where a Host header must be allowed with an empty string value. Otherwise no, empty headers don't make much sense.
Note I'm pretty sure HttpSys an Kestrel already silently ignore empty headers. Throwing isn't great because headers are usually sent indirectly via operations like WriteAsync.

Kestrel skips StringValues with 0 entries and any individual null values in the list. It does not skip empty strings.
https://github.com/aspnet/AspNetCore/blob/a79bb2a79d76a39d31809b71335e5a20e0747ff3/src/Servers/Kestrel/Core/src/Internal/Http/HttpResponseHeaders.cs#L43-L56
HttpSys skips StringValues with 0 entries and converts null entries to empty strings.
https://github.com/aspnet/AspNetCore/blob/a79bb2a79d76a39d31809b71335e5a20e0747ff3/src/Servers/HttpSys/src/RequestProcessing/Response.cs#L507

I'm also fine with ignoring empty string header values.
Considering that setting an empty string header value would cause the header to be sent in Kestrel instead of ignored, we should probably write an info-level log or something when we ignore an empty string header value in IIS.

@Tratcher @anurse we should revitalize this PR for master when we get the chance. Putting in the 5.0.0-preview1 milestone for now.

We actually fixed this earlier by simply no-oping if the header value is empty. I think this isn't relevant any more.


LEAN-2553 -- Add new role (Proofer) to schema

@hhusban can we update also other repos for V2.1.1 like transform


feat: protocol update

Woah I somehow missed this notification. Sorry.

Yes sir, Fly apps do exist and environment variables have been set.
New tracer has been created.
Yup, was thinking the same. Development at this time should be on that version and any changes in the future would be a leading change.


Word Search: Documentation and Demo

I couldn't find any demo/documentation about word search.
@lcdsantos Is this feature provided ?

Word search is available and works with western latin characters set (e.g.: á, ñ, ç...)

thx @gearsdigital for reply - is word search working without any previous options/configuration ? I have integrated the plugin, but I can not see the word search part in the dropdown.
do you have any example or demo link?


Fix TouchHistoryMath import

The reference needed to be updated after the file was moved in this commit:
https://github.com/facebook/react-native/commit/06085d38366373f3135074dc14e2c9871ca4fe29
Otherwise, results in the packager failing with the following error:

Unable to resolve module TouchHistoryMath from /node_modules/react-native/Libraries/Interaction/PanResponder.js: Module TouchHistoryMath does not exist in the Haste module map

Not sure if we should just add @providesModule to TouchHistoryMath instead, RN still uses haste module for pretty much everything.
cc @sebmarkbage

Yea, providesModule would be better.
I think the plan is to eventually not have to specify it (which is probably why it works internally at FB).

Any plan to fix this, current RNTester won't compile because of this.


GDScript: Improve highlighting of types

Fixes #82506.

Fix highlighting of for loop variable type.
Highlight void, bool, int, and float as types, not as keywords. This is especially good when there is another keyword next to the type (like if a is int or a is float).
Fix highlighting of type chains (like Variant.Type).
Add Ctrl+Click for Variant.

This also resolves https://github.com/godotengine/godot/issues/44922 :slightly_smiling_face:

#82326 is still relevant and not superseded.

Good lord, thank you for making the numeric types green, it was bothering me for so long.

Is it possible to look into this also, if not let me know, I can create a separate issue.
set and get are not colored.

Thanks

Is it possible to look into this also

Given the way highlighter works, the only solution I see is to highlight all set and get identifiers as method calls. This won't affect identifier parts (like set_name), string literals, comments, etc., but set and get will be highlighted as method calls even without parentheses (if you pass them as Callables). But I think it has more pros than cons.

I think get and set are not keywords because they can be method names.
In that case it is ok.
Ideally I thought get and set when not methods(without parentheses) should be treated(highlight only) like keywords

Highlighting set and get as keywords or as method definitions depending on the context is possible, but it is more difficult. I think the simple solution looks good for now.

Thanks!


Support for Deezer and Apple Music

I would really love to see the support for Deezer and Apple Music if it's possible. Also, discord.js is releasing v14 so adding support to it too would be great.

Hello, I will try adding Apple and Deezer support for this module soon with some fixes. But, what do you mean making this module support v14? I have a bot with v14 and this module works fine, let me know what is your problem with kazagumo in v14.

Sorry, I didn't knew it is compatible with v14 too. I have seen shoukaku not working well when v13 was released and kazagumo is based on shoukaku so I thought there might be problems with v14 too. I'll use it v14 and let you know if I get some issues. Good luck man you're doing a great job

Hello, I will try adding Apple and Deezer support for this module soon with some fixes. But, what do you mean making this module support v14? I have a bot with v14 and this module works fine, let me know what is your problem with kazagumo in v14.

Thank you making it like erela it easy to recode to this npm
Deezer and Apple Music support waiting to see this on feutre

@sarcasterXO I think this plugin will help you https://www.npmjs.com/package/kazagumo-deezer
For the Apple Music, im trying to get the info song from it but idk how to get that.

tbh I can make it too but ig takiyo was already working on it so i didn't. but let's see once i again start working on my bot's rewrite i may create a plugin for apple music too.

The problem is that when u provide to a search function a deezer link the lavalink server resolve it using yt source instead of getting the native deezer audio . ( I have the https://github.com/TopiSenpai/LavaSrc plugin )

@Nico-ITA, @sarcasterXO Now v3 can play native deezer audio and other src using lavalink plugin


Added moment to Concerto-ui

Signed-off-by: kanav<EMAIL_ADDRESS>Issue #29
Added moment dependency for date creation
Changes
Using moment for date creation rather than custom JavaScript Date
Flags

Related Issues

Issue #
Pull Request #

Kindly review @irmerk, @jeromesimeon and @mttrbrts

This package doesn't need the moment library (and all of the bundled locale packaged) just to render an ISO compliant date. Adding moment adds 50% to the bundle size of the core package which is unnecessary.
Please address this issue without adding extra libraries.

@mttrbrts Kindly tell me how should I address this without adding extra library llike moment.
Thanks


Sliver/CustomScrollView have occasional floating point precision issues.

Description

I try to add a print method into the sdk code, and breakpoint it.
https://github.com/flutter/flutter/blob/94b7ff241e6e5445b7f30215a777eb4971311797/packages/flutter/lib/src/rendering/sliver_list.dart#L294
Due to commercial projects, I can't open source this part of the code.
The main reason is that the internal item contains a GridView, and the GridView is shrinkWrap: true, so the GridView's height is double type.
At present, I solved it by calculating the height of GridView and all other controls in this item and using ceilToDouble. But this calculation is complicated, so I think there should be a better solution to solve it.

Because of the assertion of floating-point precision, this problem will occur during the development process, causing all subsequent rendering processes to be terminated.
But because the assert does not terminate the rendering in the release, it may not cause problems in the release environment.
But in any case, I think this kind of problem may be flooded in the process of various SDKs, are there some effective solutions to avoid it?
flutter doctor -v

[✓] Flutter (Channel unknown, v1.17.1, on Mac OS X 10.15.2 19C57, locale zh-Hans-CN)
    • Flutter version 1.17.1 at /Volumes/Evo512/sdk/flutter/fvm/1.17.0
    • Framework revision f7a6a7906b (3 weeks ago), 2020-05-12 18:39:00 -0700
    • Engine revision 6bc433c6b6
    • Dart version 2.8.2
[✓] Android toolchain - develop for Android devices (Android SDK version 29.0.2)
• Android SDK at /Users/cai/Library/Android/sdk
• Platform android-29, build-tools 29.0.2
• ANDROID_HOME = /Users/cai/Library/Android/sdk
• Java binary at: /Applications/Android Studio.app/Contents/jre/jdk/Contents/Home/bin/java
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
• All Android licenses accepted.
[✓] Xcode - develop for iOS and macOS (Xcode 11.1)
• Xcode at /Applications/Xcode.app/Contents/Developer
• Xcode 11.1, Build version 11A1027
• CocoaPods version 1.9.1
[✓] Chrome - develop for the web
• Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
[✓] Android Studio (version 4.0)
• Android Studio at /Applications/Android Studio.app/Contents
• Flutter plugin version 45.1.2
• Dart plugin version 193.7361
• Java version OpenJDK Runtime Environment (build 1.8.0_242-release-1644-b3-6222593)
[✓] Android Studio (version 3.6)
• Android Studio at /Volumes/Evo512/application/jetbrains/apps/AndroidStudio/ch-0/192.6392135/Android Studio.app/Contents
• Flutter plugin version 42.1.1
• Dart plugin version 191.8593
• Java version OpenJDK Runtime Environment (build 1.8.0_212-release-1586-b4-5784211)
[!] IntelliJ IDEA Ultimate Edition (version 2019.3.1)
• IntelliJ at /Users/cai/Applications/JetBrains Toolbox/IntelliJ IDEA Ultimate.app
✗ Flutter plugin not installed; this adds Flutter specific functionality.
✗ Dart plugin not installed; this adds Dart specific functionality.
• For information about installing plugins, see
https://flutter.dev/intellij-setup/#installing-the-plugins
[✓] VS Code (version 1.45.1)
• VS Code at /Applications/Visual Studio Code.app/Contents
• Flutter extension version 3.11.0
[✓] Connected device (4 available)
• MI 8       • b6ec3684   • android-arm64  • Android 10 (API 29)
• macOS      • macOS      • darwin-x64     • Mac OS X 10.15.2 19C57
• Chrome     • chrome     • web-javascript • Google Chrome 83.0.4103.61
• Web Server • web-server • web-javascript • Flutter Tools
! Doctor found issues in 1 category.

Hi @CaiJingLong
there's no need to share your production code,
but could you please provide a reproducible minimal code sample
Thank you

Without additional information we are unfortunately not sure how to resolve this issue.
We are therefore reluctantly going to close this bug for now.
Please don't hesitate to comment on the bug if you have any more information for us; we will reopen it right away!
Thanks for your contribution.


Research capability for smoke-testing the plugin in headless mode within CI pipeline

Actually, according to https://github.com/JetBrains/gradle-intellij-plugin/blob/master/README.md, buildSearchableOptions (a dependency of buildPlugin) already runs a headless IDE instance.
Possibly verifyPlugin can bring some added value (?)

For record, as for now, building fat jar from https://github.com/VirtuslabRnD/ide-probe/pull/97

Headless mode doesn't allow for easily opening a view/tab... let's ditch this, we have other priorities.

Actually, partly addressed by #216 (coz so far majority of problems such that the plugin was building successfully but later failed to launch were actually caused by missing/superfluous jars in the plugin zip).

Experience show that this is of high importance, re-opening


Cap running events request

Overview
Granicus seems to be having intermittent issues with their running meetings endpoint. This PR aims to put a hard limit on requests to Granicus to make sure that our pages remain accessible regardless of the status of the running meetings endpoint.
Connects #1118
Testing Instructions

Verify that tests pass
Verify that the review app's homepage works correctly

The running meetings endpoint isn't the only Granicus endpoint we rely on on the homepage (we also use it on event pages). I'm thinking that if we like this approach, we should make a custom requests.get function.
What do you think, @hancush?

@antidipyramid Sure, we could make a reusable thing to use wherever we make external requests.


Configurable Transport

GraphQL does not define the transport and it might be interesting to provide other means of transport like websockets for example

"might be interesting" is not a strong motivator for me. If you have a use case, I'd like to hear it, thanks!


Re-land: Fix bug where InputLayout objects failed to paint or layout correctly

This is a re-land of PR #545, with the following changes:

Restricted to <input> elements.
Adjusts footnote and chapter text to clarify why this is specific to <input>

Ok re-land is ready for your review. I responded to your editorial and structural feedback and incorporated it.
Also, regarding input and buttons not being special: I think they are a bit special, and indicated the way I think so in the proposed text. Also, it is true that we don't paint inlines correctly in various other ways. I tried to come up with a simple solution to that but failed to. So I just added a sentence to the footnote admitting as such.

Going to land this now and discuss later.


additional-checkout-buttons.css included on all pages : google pagespeed issue

In the theme.liquid file, the variable {{ content_for_header }} include additional-checkout-buttons.css file on all pages, no matter if the additional checkout buttons are activated or not.
In google page speed, this CSS file block the page rendering on mobile, decreasing a lot the google pagespeed score : https://developers.google.com/speed/pagespeed/insights/?hl=us&url=https%3A%2F%2Fwww.bichette.co%2F
2 solutions :

only include this css file on the cart page.
do not include this css file if no additional checkout buttons are configured.

Good spot, think this is an area where Shopify could improve how it uses the head content rather than a timber theme issue.

@NathanPJF are you able to triage this in core?

@cshold Cool, will do.
@tlandru thanks for bring this up.  I agree Shopify can do something about this render blocking.  Something worth noting about one of the solutions you proposed:

only include this css file on the cart page.

These additional checkout buttons can be used in ajax carts which appear on multiple pages.  So we don't want to limit it to /cart.  Doc link: https://help.shopify.com/themes/customization/cart/add-more-checkout-buttons-to-cart-page#show-checkout-buttons-in-a-cart-drawer-popup-or-sidebar
As for the other solution:

do not include this css file if no additional checkout buttons are configured.

I'll include this in my write-up in core.  Right now the stylesheet gets included the moment you select a provider for processing credit cards - might be an oversight, but if there's a reason for it I'll report back.

I have a customer that I have setup mod_pagespeed for just to inline this CSS file. Would be great if Shopify could just inline it..


NMDC schema slots to NCBI MIxS term matching

Fixes #1940

This PR is ready to be reviewed/merged.

Running the below command:
nmdc-schema git:(issue-1940) ✗ nmdc-ncbi-mapping package-specific-curation assets/ncbi_mappings/ncbi_attribute_mappings_filled.tsv
Optional NCBI Attribute names that do not have NMDC slot mappings: ['collection_method', 'isolation_source', 'neg_cont_type', 'omics_observ_id', 'pos_cont_type', 'ref_biomaterial', 'rel_to_oxygen', 'samp_collect_device', 'source_material_id']

Manual mappings for the above slots that can be filled out:

NCBI Attribute name
NMDC schema slot (mapped manually)

collection_method
samp_collec_method

isolation_source
MAN_IGNORE

neg_cont_type
MAN_IGNORE

pos_cont_type
MAN_IGNORE

ref_biomaterial
nucleic_acid_sequence_source_field

rel_to_oxygen
oxy_stat_samp

samp_collect_device
samp_collec_device

source_material_id
id

@turbomam requesting for a review on this PR. I suggest merging this in, and I will add my suggestions from the above comment to https://github.com/microbiomedata/nmdc-schema/blob/issue-1940/assets/ncbi_mappings/ncbi_attribute_mappings_filled.tsv once it has been created in main.

do you still want this merge in here, as opposed to nmdc-runtime?

I guess so since they are changes and not additons


fix: make ahjo_case_id read_only

Description :sparkles:
Application.ahjo_case_id (Diaarinumero) was not read_only, so in some scenarios, the frontend could update it as None which is not what we want ever.
Issues :bug:
Testing :alembic:
Screenshots :camera_flash:
Additional notes :spiral_notepad:

API branch is deployed to platta: https://helsinkilisa-pr3091.api.dev.hel.ninja/healthz :rocket::rocket::rocket:

APPLICANT branch is deployed to platta: https://helsinkilisa-ui-pr3091.dev.hel.ninja :rocket::rocket::rocket:

HANDLER branch is deployed to platta: https://helsinkilisa-ui-handler-pr3091.dev.hel.ninja :rocket::rocket::rocket:

TestCafe result is success for https://helsinkilisa-ui-handler-pr3091.dev.hel.ninja :laughing::tada::tada::tada:

TestCafe applicant result is failed for https://helsinkilisa-ui-pr3091.dev.hel.ninja :crying_cat_face::anger::boom::boom:


test: reduce artillery runtime to 1 minute from 10

Fixes #1146
Signed-off-by: Youngone Lee<EMAIL_ADDRESS>
Although the original issue mentioned that the artillery runtime was 10 minutes, it might have been at 5 minutes. I'm not sure if I've altered the correct code for this issue but I edited the avgLatency. Please let me know if there's something else I should have done!!
It also looks like this testcase wasn't passing the tests (this was before I made any changes), do you want me to make a separate issue to fix the failing test cases? @petermetz

Codecov Report

Merging #1235 (2599c00) into main (57afe15) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##             main    #1235   +/-   ##
=======================================
  Coverage   71.95%   71.95%
=======================================
  Files         270      270
  Lines        9438     9438
  Branches     1112     1112
=======================================
  Hits         6791     6791
  Misses       2075     2075
  Partials      572      572

Continue to review full report at Codecov.

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

@Leeyoungone
Hey Wen, have you got an example of these tests failing? It's merge into main and I see many of the builds passing.
Cheers,
Trav

@travis-payne
Hello Travis, I was running the artillery-api-benchmark-test.ts (packages/cactus-cmd-api-server/src/test/typescript/benchmark/artillery-api-benchmark.test.ts) on the main branch and it looks like it wasn't passing a few tests. Here's the screenshot below


Improve error handling

Show better error messages for:

[x] Terraform binary missing
[x] An unsupported Terraform version is used
[x] The dir isn't a Terraform dir
[x] Plan/JSON file does not exist
[x] Terraform vars are missing
[x] Terraform var file does not exist
[x] Any error returned from Terraform binary
[x] Any internal panic

Fixes https://github.com/infracost/infracost/issues/146


Predict next Sequence of numbers Using LSTM

Fixed: #806
Here, I have Taken Long Term Short Memory (LSTM) approach with importing libraries like numpy, pandas and PyTorch.
Loaded the dataset (Created on my own self) based on the airline passengers like monthly, number of passengers on that date.
Done Data Preprocessing, Split the data into testing and training set, Defined the LSTM Model, Trained the model, Evaluated and Got the final result.
The model's performance is evaluated, demonstrating its capability to generate sequences that follow the learned pattern from the training data.
I have done with this issue. Kindly Review and Merge my Pull Request.
I have resolved file and added new outputs.

@Niketkumardheeryan, @invigorzz313 I have resolved the entire file and added new outputs,
Please review and merge it.

Okay, i will add it

@vivekvardhan2810 You can also add Readme.md file here in this same branch instead of closing PR


support for level in NIP files

Details
I'm not entirely sure if this is a problem with koolo, or the NIP parser in the d2go repo but I would like to be able to have the bot keep ilvl 91+ grand charms (from diablo, baal, or TZ monsters mlvl >= 91) so i can try re-rolling them into the elusive vita skillers.
In theory, from this NIP guide, [level] can be used as a property, but when i start the Koolo exe the NIP parser returns an error on:
[name] == grandcharm && [quality] == magic && [level] >= 91

using it as a [stat] (ie after a #) doesn't seem to work (as that guide says, it won't). I tried it and although it didn't trigger an error when koolo starts, i caught the bot skipping over a GC dropped by Diablo.
Thanks so much for your work on this! Eases up on the SSF grind for sure and it works great :)
Version
dev 37bebc0507aaa8a7e8031455a3b87909591b9d6c
Logs
logs don't have any pertinent information for this problem

I haven't looked into it but I'm 90% sure it used to work just fine with Koolo. So it's likely some of the reference files in Koolo or D2GO have changed, or the D2R patch somehow broke something.
In the meantime I filter to pickup charms that have the lvl91 suffix itself i.e. +36 to life. But get far fewer.


Fix style issues

Hi Elijah,
It looks like this change disables the core functionality of the website. i.e. text doesn't translate.
Cheers
(I have limited time this weekend so apologies if I'm not very responsive)

Should be fixed now

Thanks Elijah, I appreciate we all have our way of working so splitting the css between bespoke and generated is a great change that is very appreciated!
I'll leave a couple questions on some changes I'm not certain of the motivation behind but other than that it looks great.
Thanks for your contributions


Myfeature

dubbo protocol的客户端

 Thank you for your submission, we really appreciate it. Like many open source projects, we ask that you all sign our Contributor License Agreement before we can accept your contribution.0 out of 2 committers have signed the CLA.:x: 高辛格:x: AlexStocks高辛格 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


fix: remove duplicate event emission

Closes: #XXX
What is the purpose of the change

Add a description of the overall background and high level changes that this PR introduces

(E.g.: This pull request improves documentation of area A by adding ....
Testing and Verifying
(Please pick one of the following options)
This change is a trivial rework / code cleanup without any test coverage.
(or)
This change is already covered by existing tests, such as (please describe tests).
(or)
This change added tests and can be verified as follows:
(example:)

Added unit test that validates ...
Added integration tests for end-to-end deployment with ...
Extended integration test for ...
Manually verified the change by ...

Documentation and Release Note

[ ] Does this pull request introduce a new feature or user-facing behavior changes?
[ ] Changelog entry added to Unreleased section of CHANGELOG.md?

Where is the change documented?

[ ] Specification (x/{module}/README.md)
[ ] Osmosis documentation site
[ ] Code comments?
[ ] N/A

Somehow, removing the events is not working as expected. For instance, when removing them on the single call, we should expect a single event auto populated, but after removing we get zero

We should not merge until we figure out what the sdk meant when they said these events can be removed

Bez explained that if there is duplication on the application side, the event is not duplicated. That being said, we should still remove this here, but it explains why the events weren't adding up to what I thought it should.


chore(main): release 1.0.3

:robot: I have created a release beep boop
1.0.3 (2024-06-09)
Bug Fixes

deps: update dependency matterbridge-home-assistant to v0.1.1 (#14) (58610cb)

This PR was generated with Release Please. See documentation.

:robot: Release is at https://github.com/t0bst4r/matterbridge-home-assistant-addon/releases/tag/v1.0.3 :sunflower:


Compatibility with Angular universal and material

Is RecordRTC compatible with Angular universal and Material?
I have been working on an Angular 5 project that uses server side rendering and material. However, when I use RecordRTC for video recording, the server side rendering fails. For some reason, using recordRTC makes CDK to error out.
I understand that recordRTC uses a lot of things that would only be supported on browser, but then there should be a way to make other pages render on the server. I added a conditional check isPlatformBrowser(platformId) for initializing recordRTC, but it seems the error occurs due to the import.
I have posted a similar issue at the material repository here as I am not even sure who should handle this.
Thanks!

I have used RecordRTC in production succesfully. I used Angular 5 with Material (not universal) with AOT enabled.
No particular issues were encountred in that particular configuration

Is RecordRTC compatible with Angular universal and Material?
I have been working on an Angular 5 project that uses server side rendering and material. However, when I use RecordRTC for video recording, the server side rendering fails. For some reason, using recordRTC makes CDK to error out.
I understand that recordRTC uses a lot of things that would only be supported on browser, but then there should be a way to make other pages render on the server. I added a conditional check isPlatformBrowser(platformId) for initializing recordRTC, but it seems the error occurs due to the import.
I have posted a similar issue at the material repository here as I am not even sure who should handle this.
Thanks!

Any solution we got??? I am facing same issue and help less to integrate voice recorder with my angular app having angular material and universal (SSR) enabled.

        let RecordRTC;
        let moduleRecord;
        await this.ngZone.run(async () => {
          // https://stackoverflow.com/a/58859327/5748537
          moduleRecord = await import('recordrtc');
          RecordRTC = (moduleRecord as any).default;
        });

        this.record = new RecordRTC(this.stream, {
          mimeType: 'audio/wav',
          type: 'audio',
          numberOfAudioChannels: 1,
          disableLogs: true,
          desiredSampRate: 12000,
          recorderType: RecordRTC.StereoAudioRecorder,
        });

        ```
        tested with angular 14 SSR

        do you love me?


@sanex3339 => react-native-obfuscating-transformer maintainership

Hi @sanex3339! :wave: Sorry for making this a github issue, I didn't know how else to contact you.
I'm no longer actively maintaining react-native-obfuscating-transformer so would like to add some more maintainers who can keep it up to date. Unfortunately I don't have admin rights over that repo after transferring ownership to the javascript-obfuscator org. Can you give me those rights? Or if not, then can you at least add @jesucarr  as a collaborator?
Thanks :heart:

@sanex3339 yes, and I see a long-waiting pull request in that repo. I don't have enough expertise in React Native to merge this PR.

Hi. Sorry, i'm to late. Sent the invite for you

The invite is sent, closed.


SharePoint Online - Custom List - JSON action editProps - Right Side Pane is now Too Wide

Target SharePoint environment
SharePoint Online
What SharePoint development model, framework, SDK or API is this about?
Site designs & site scripts
Developer environment
Windows
What browser(s) / client(s) have you tested

[ ] 💥 Internet Explorer
[X] 💥 Microsoft Edge
[X] 💥 Google Chrome
[X] 💥 FireFox
[ ] 💥 Safari
[ ] mobile (iOS/iPadOS)
[ ] mobile (Android)
[ ] not applicable
[ ] other (enter in the "Additional environment details" area below)

Additional environment details

Most up to date browser versions.

Describe the bug / error
I created a SharePoint Online Custom List around 10/1/2020. In the "Edit Ticket" column, I input the JSON code that implements the action editProps, which results in an orange pencil symbol appearing in that column. Upon clicking it, the item edit/details pane will open on the right-side, which used to consume about 30-40% of the whole screen.
Starting yesterday 9/28/2021, whenever anyone clicks the edit pencil JSON code symbol, the edit/details pane now takes up 95% of the whole screen, which is too wide for our users. It reduces the description column content width (multiple lines of text) which forces users to scroll down a lot.
Did something happen to the JSON action editProps source code that widens the edit pane? Please let me know if there is anything that can be done to revert it back from taking up 95% of the screen to just 30% like before.
JSON action editProps code: https://github.com/pnp/List-Formatting/blob/master/column-samples/generic-rowactions/editProps.json
I attached images that show the difference.
Edit symbol:

Old edit pane at a nice small width:

New edit pane at a very large width:

Thanks
Steps to reproduce
Based on the message and images above, click the edit pencil symbol to open the details pane.
Expected behavior
I expected the pane to remain at its smaller width, but now it's very wide.

Hi, unfortunately, this is currently how formatting works. Any customization to the form will result in the wide screen layout for the form.


Evaluate frameworks for processing and sending emails

In the past we have always written wrappers around the Python email library to solve issues like:

Templating
Asset bundling

There are projects like red-mail looking closely at these problems.
We should evaluate such libraries so we aren't maintaining this layer ourselves

Decided to stick with red-mail as it supports Jinja2 out of the box, attaching files and inline images


Fix README to use sidekiq server middleware for the server

The sidekiq server needs to retrieve the request_id from the redis data
and set it on Thread.current, not set request_id on the sidekiq client
as the documentation shows.

This change makes sense to me ;).

@ejholmes, don't mean to bug you but what do we need to do here to get this PR merged?
This change was helpful when our team recently installed the gem.
Thanks!

Sorry for the delay. This lgtm.


Fix incorrect error value in decomposeMatrix().

decomposeMatrix() was returning false instead of null causing the wrong code path to be triggered and exceptions to be thrown.
Fixes #118.

Whoops, I should have said this fixes #115. #118 is karlhaas' fix for the same bug.

@alancutter FYI, #115 is still open


Endpoint to calculate Refinance

The refinance calculation can help plan the refinancing of a loan given various situations, and also allows the side-by-side comparison of the existing or refinanced loan.
Perform all the calculations in the function.py file present in helpers folder
Create the endpoint refinance in the main.py file and return the required result in a proper format

@ighoshsubho I want to make that endpoint, please assign me that task

go ahead @EdKsenia! :)

pull request #220


Back in black

Resolves #1205
Update of pull request #1225
This PR converts the code style to Black with sorted imports, and replaces the pycodestyle tool with the black and isort tools.
@neilCrosswaite has written a good summary of the effects on code in a comment on #1205.
These changes have been reviewed in PR #1225, but this branch rearranges the commit history in order to bring this branch up to date with latest master branch, and allow for easy rebasing if further updates are needed.
Testing:

[x] Ran tests and they passed OK

 Here is an overview of what got changed by this pull request:

Issues
======
+ Solved 11
- Added 10

Clones added
============
- improver_tests/utilities/cube_manipulation/test_MergeCubes.py  1
- improver_tests/nbhood/nbhood/test_NeighbourhoodProcessing.py  1
- improver_tests/nowcasting/accumulation/test_Accumulation.py  2
- improver_tests/nbhood/use_nbhood/test_CollapseMaskedNeighbourhoodCoordinate.py  5
- improver_tests/nbhood/nbhood/test_BaseNeighbourhoodProcessing.py  1
- improver_tests/ensemble_copula_coupling/ensemble_copula_coupling/test_utilities.py  1
- improver_tests/calibration/ensemble_calibration/test_EstimateCoefficientsForEnsembleCalibration.py  4
- improver_tests/lapse_rate/test_LapseRate.py  5
- improver_tests/utilities/test_pad_spatial.py  4
- improver_tests/nbhood/square_kernel/test_SquareNeighbourhood.py  2
- improver_tests/blending/spatial_weights/test_SpatiallyVaryingWeightsFromMask.py  2
- improver_tests/blending/weighted_blend/test_MergeCubesForWeightedBlending.py  2
- improver_tests/nowcasting/optical_flow/test_OpticalFlow.py  2
- improver_tests/nbhood/use_nbhood/test_ApplyNeighbourhoodProcessingWithAMask.py  2

Clones removed
==============
+ improver_tests/threshold/test_BasicThreshold.py  -7
+ improver_tests/ensemble_copula_coupling/ensemble_copula_coupling/test_RebadgePercentilesAsRealizations.py  -1
+ improver_tests/calibration/reliability_calibration/test_ConstructReliabilityCalibrationTables.py  -2
+ improver_tests/generate_ancillaries/test_GenerateTopographicZoneWeights.py  -5
+ improver_tests/standardise/test_AdjustLandSeaPoints.py  -2
+ improver_tests/nbhood/circular_kernel/test_GeneratePercentilesFromACircularNeighbourhood.py  -11
+ improver_tests/ensemble_copula_coupling/ensemble_copula_coupling/test_EnsembleReordering.py  -11
+ improver_tests/ensemble_copula_coupling/ensemble_copula_coupling/test_ConvertLocationAndScaleParametersToPercentiles.py  -2
+ improver_tests/utilities/test_OccurrenceWithinVicinity.py  -1
+ improver_tests/calibration/utilities/test_utilities.py  -2

See the complete overview on Codacy


Markers Color

How do I add different status colors to the markers? Like, I have icons with different status which should be displayed with different colors.

  let arrow = L.polylineDecorator(layer, {
                id: layer._leaflet_id,
                patterns: [
                  {
                    offset: '100%',
                    endOffset: '100%',
                    repeat: 0,
                    symbol: L.Symbol.arrowHead({
                      pixelSize: 15,
                      polygon: false,
                      pathOptions: {
                        fill: false,
                        fillColor: '',
                        fillOpacity: 1,
                        stroke: true,
                        **color: feature.properties.color,**
                        opacity: 1,
                        weight: 5,
                        lineCap: 'square',
                        lineJoin: 'miter',
                      },
                    }),
                  },
                ],
              }).addTo(vm.map);

Thanks for this. Where do you get feature.properties.color from? Also is ti possible to have a custom marker (perhaps svg) instead of arrow head? Thanks

The idea is to have each marker to have a color based on some variable. Say, red for high, green for normal, yellow for low and so on.

@mugambi40 you don't need SVG. You have the props color und there you can change your current color.
And feature.properties.color  is only my way to take the right data for the current arrow marker from DB.

See the image attached. I simply want to load different icon color based on some variables

See the image attached. I simply want to load different icon color based on some variables

Without your code, I cannot help you.

@miko866 below is my code
`var multiCoords1 = [
[51.4266, 2.8564], [51.7542, 2.1093]],
[[48.0193, -2.8125], [46.3165, -2.8564], [44.9336, -1.0107], [44.5278, 1.5820], [44.8714, 3.7353], [45.8287, 5.1855], [48.1953, 5.1416]]
];
var plArray = [];
for(var i=0; i<multiCoords1.length; i++) {
plArray.push(L.polyline(multiCoords1[i]).addTo(map));
}
var icon = L.divIcon({
className: "svg-marker",
html: <svg xmlns="http://www.w3.org/2000/svg">         <defs>                <filter id="f1" x="0" y="0" width="200%" height="200%">                    <feOffset result="offOut" in="SourceAlpha" dx="5" dy="5" />                    <feGaussianBlur result="blurOut" in="offOut" stdDeviation="3" />                    <feBlend in="SourceGraphic" in2="blurOut" mode="normal" />             </filter>         </defs>             <path d="m23.582 9.161c1.07 1.274 2.134 2.553 3.051 3.944 1.567 2.366 2.928 4.82 3.438 7.667 0.434 2.488-0.012 4.804-1.284 6.967-0.672 1.145-1.504 2.158-2.564 2.97-2.293 1.768-4.869 2.502-7.752 2.162-1.963-0.236-3.732-0.917-5.241-2.22-1.501-1.303-2.503-2.913-3.034-4.821-0.751-2.7-0.467-5.332 0.547-7.909 0.953-2.424 2.316-4.612 3.841-6.708 1.27-1.754 2.655-3.419 4.119-5.012 0.736-0.799 1.793-0.736 2.563 0.122 0.812 0.91 1.547 1.89 2.316 2.838z"              filter="url(#f1)"           clip-rule="evenodd" fill="#8BA845" fill-rule="evenodd"/>         <path d="m16.823 18.64c-2.434 1.975-2.483 5.133-0.869 7.213 1.729 2.232 5 2.599 7.19 0.852 2.228-1.769 2.607-4.983 0.857-7.189-1.741-2.188-5.05-2.6-7.178-0.876z" clip-rule="evenodd" fill="#fff" fill-rule="evenodd"/>         </svg>,
// iconSize: null,
iconAnchor: [18, 18],
});
L.polylineDecorator(multiCoords1, {
    patterns: [
        {
            offset: '5%',
            repeat: 50,
            symbol: L.Symbol.marker({
                rotate: true,
                markerOptions: {
                    clickable: true,
                    interactive: true,
                    icon: icon
                },
                listeners: {
                    click: this.onTrackLineClick,
                    scope: this
                }
            })
        }
    ]

}).addTo(map);

`

I use Vue.js but the logic is the same you muss only the code little change.
Marker Icon:
const icon = L.icon({         iconUrl: require('@/assets/img/FireStation.svg'),         iconSize: [30, 30],         iconAnchor: [13, 30],         popupAnchor: [0, -18],       });
Then you can dynamically load your new iconUrl depends on the data and simply show it.

Hey @miko866
But how do you make different colors for each marker?
For example, I need 10 markers on the same line but different colors?
Thanks


UX issue with Mikan screen [wightwulf]

The navigation drawer is accessible from Mikan screen.
Mikan screen should behave as a child screen and therefore should have a back or close button for app bar navigation action. This has the adverse effect of being able to navigate forward to the Home screen which no longer makes it the root screen in the navigation heirarchy and causes weird behavior with the back button.
Lateral navigation is also fine, but that can be done by switching fragments instead of launching a new activity
NB : This issue is directly linked to #60

Fixed by cdbdbf455f268edbffee76c0444cad71292c7f61


Include pointers in docstring

It would be helpful to give pointers to references with more details on the algorithms used in this package.
For instance, in the docstrings of

[ ] isotypical_basis
[ ] matrix_projection

I don't think there's much to add here. There aren't really any advanced algorithms involved.
If π: G → GL(n,K) is a matrix representation, then this homomorphism has canonical extension to a homomorphism of  group algebra into the algebra M(n,n,K) of matrices over K. The matrix_projection (probably not a great name) is just realization of this extension. If χ:G → K is a function on the group (e.g. a character) (often written as Σ χ(g)·g), then matrix_projection is just Σ χ(g)·π(g), a weighted sum of matrices. Since every character is an idempotent in the group algebra, matrix_projection is a projection (e.g. in the sense of linear algebra) in the fixed basis.
Character (as an idempotent) and matrix_projection (as matrix) play the same game as quadratic form and its matrix realization in classical linear algebra.
isotypical_basis just finds a maximal set of independent vectors in the image of a projection. One could use rref for this, or SVD as I did here:
https://github.com/kalmarek/PropertyT.jl/blob/db044301059cecc3dfe7aa22325aa39e4109b981/src/blockdecomposition.jl#L28
Isotypical refers to the fact that a representation may decompose into constitutents (~irreducible summands) with multiplicities (so called isotypical decomposition). The returned basis is a basis for the whole block of such type.
Since characters (in the group algebra) are orthogonal, in the sense of this dot:
https://github.com/kalmarek/SymbolicWedderburn.jl/blob/5ec5eff1e6a11bd8e908e3b122fc5adb68cf608b/src/characters.jl#L5
(which is just a specialization of a general dot on the group algebra), the derived matrix projections are orthogonal (i.e. their images are orthogonal subspaces), so combining/concatenating their images gives you blocks of orthogonality.

Probably at a later stage we may opt to provide more thorough explanation in e.g. a case-study documentation as you do here:
https://jump.dev/SumOfSquares.jl/latest/generated/Symmetry reduction/
??

Thanks for the details!
So the primitive central idempotents of CG are e_i = χ_i(1)/|G| * sum_g χ_i(inv(g)) * g where χ_i are the characters of the irreps.
We drop the χ_i(1)/|G| as it's just constant and we compute instead sum_g χ_i(g) * inv(g). The regular representation of inv(g) is the matrix with i^g in each row i which gives
https://github.com/kalmarek/SymbolicWedderburn.jl/blob/5ec5eff1e6a11bd8e908e3b122fc5adb68cf608b/src/projections.jl#L45-L51
since val is χ_i(g), correct ?

Probably at a later stage we may opt to provide more thorough explanation in e.g. a case-study documentation

Yes, it's a good idea. I do something similar in https://jump.dev/SumOfSquares.jl/latest/generated/Polynomial Optimization/#A-deeper-look-into-atom-extraction.

that's correct, with a small amendment, that it's not the regular representation (group acting by left/right multiplication on itself), but the representation given by the action of the group on the basis.
In our case we have π:G → GL(basis) and to obtain projections for central idempotents (~characters) one need to evaluate the action matrix for each element g∈G. (yes, I forgot about g⁻¹ above).
For matrix groups precisely this function needs to be extended.

Thanks, that clarifies it :)


There are no commands defined

Laravel Version: 5.4.23
Voyager Version: 0.11.10
PHP Version: 7.1.1
Database Driver & Version: MySQL, <IP_ADDRESS>

Description:
In the last step for Installation of Voyager, while running
php artisan voyager:install or php artisan voyager:install --with-dummy
an error occurs
'  [Symfony\Component\Console\Exception\CommandNotFoundException]
There are no commands defined in the "voyager" namespace.'
I've tried most of the solutions provided before, nothing seems to work as a solution, also to cut is short, I've already added a provider, ran on a clear cache, autodumped, and nothing seems to help.
Steps To Reproduce:

Have you tried composer dump-autoload? It should be run automatically when doing a composer update or composer install.  If that doesn't help, please verify that your providers array has TCG\Voyager\VoyagerServiceProvider::class, per the documentation

I tried both of dump-autoload and I added the provider before I run the installer n sorrowfully it doesn't work.

Try
php artisan config:clear

@YuriZakaria, have you resolved this issue? If not, please try artisan config:clear as suggested.  Something is holding onto that configuration.

I also have this kind of problem
There are no commands defined in the "voyager" namespace.'
run php artisan config:clear, but it doesn't work.

@FireLustre, this has been closed for 6 months.  If you have an problem that you suspect is a bug in the code, please open a new issue and reference the old one.  If you need help with implementation of Voyager, or just general questions, it would be better asked in our Slack group.


.gitignore files missing in generated project

Expected Behaviour
The archetype should generate appropriate .gitignore files for files that can safely be ignored from source control and for files that should NOT be committed to source control.

/.gitignore (project root)
/ui.frontend/.gitignore
/ui.apps/.gitignore

Actual Behaviour
.gitignore files are not included in new project generated from archetype 35
Reproduce Scenario (including but not limited to)
Generate a project using the ootb maven command:
mvn -B org.apache.maven.plugins:maven-archetype-plugin:3.2.1:generate \
 -D archetypeGroupId=com.adobe.aem \
 -D archetypeArtifactId=aem-project-archetype \
 -D archetypeVersion=35\
 -D appTitle="My Site" \
 -D appId="mysite" \
 -D groupId="com.mysite"

Observe that no .gitignore files are created.

Looks like in develop branch this PR https://github.com/adobe/aem-project-archetype/pull/876/files moved the .gitignore file from the root...
Although I'm still not sure why in a project generated using the released version of Archetype 35 it is no longer there?

Doing a little digging looks like the update to use 3.2.1 for the maven-archetype-plugin changed the behavior for what files are copied into the generated project and looks like the way . dot files were copied in the archetype-metadata.xml:
<fileSets>
    <fileSet encoding="UTF-8">
      <directory></directory>
      <includes>
        <include>README.md</include>
        <include>README-CIF.md</include>
        <include>README-precompiled-scripts.md</include>
        <include>.gitignore</include>
        <include>.gitattributes</include>
        <include>LICENSE</include>
      </includes>
    </fileSet>

Isn't behaving the same way. I could workaround it by updating the plugin configuration:
<plugin>
      <artifactId>maven-archetype-plugin</artifactId>
      <version>${maven.archetype.version}</version>
      <configuration>
          <useDefaultExcludes>false</useDefaultExcludes>
      </configuration>
  </plugin>

cc. @stefanseifert if he has ideas.


Support for Annotations

Continue GProM integraton by adding a new annotation operator.

commit c39044ccbff153f38bf38b7c96266914a2729f5e merged initial annotate operator into master


Unable to submit license request form for egoexo4d "failed to fetch"

I can't submit the license request form for egoexo4d https://ego4ddataset.com/egoexo-license/
In case it's relevant: I did request the ego4d license recently.
Thanks

Okay, it's working now


Speed up build times.

What problem does this feature solve?
So I have a (not really that large) project in Vue 3 and TypeScript, using the latest versions of the available packages at the time of posting this.
Some details:

46 .vue files.
16 .ts files.
9 additional vendor packages (fontawesome - fortawesome, lodash.orderby, jquery, c3).

Environment:

Docker Container
Image: Ubuntu 20.04.1
CPUs: 2c/4t
RAM: 16GB

I am seeing build speeds of around 20 minutes.
This can't be normal? or expected, considering this same project without Vue CLI and in the older vue project takes a minute or 2 max. So what could be happening? There must be something that could be disabled or changed to fix this?
I just can't see Vue staying "ahead" if the build times stay this high, 20 minutes to build for production is pretty bad.
Is there anything we can change?
I have also disabled productionSourceMaps, and skipped the eslint plugin in the build command, but as of now I am out of ideas.
To confirm, I am unable to send you to a reproduction because it's a closed source project for my company - I can answer any questions relating to the project if required though.
What does the proposed API look like?
N/A

Ignore, I spent some time working in the project, looks like it was related to SCSS compilation and fontawesome imports.

Ignore, I spent some time working in the project, looks like it was related to SCSS compilation and fontawesome imports.

@dannysmc95 It would be really helpful if you share what exactly you did to reduce the build time.
Thanks in advance.

@dannysmc95 It would be really helpful if you share what exactly you did to reduce the build time.
Thanks in advance.

@Anjgpt that's fair.
I mean I have not got the code to hand, but essentially.
So time summary;
Original Compilation - Between 15 - 20 minutes
Updated Compilation - Between 45 seconds - 1 minute and 20 seconds.
(First compilation is usually slower, the first one took around 1 minute and 20 seconds for me then the ones after only took around 45/48 seconds.)
Point 1 - SCSS imports.
I was using a base SCSS folder which included like 6 other SCSS files, 2 of them were just mixins and variables, the other 4 were helpers, and pre-defined styles, and one of the helpers loops and generates like loads of classes, and this was being imported into every single .vue file I had, instead I changed it to only import the two variables and mixins files, and then imported the other 4 files into the main App.vue file instead - this did speed up the SCSS compilation part dramatically.
Point 2: Font Awesome imports.
This was a bit more obvious, but a silly oversight on my end, I was using the @fortawesome package with the SVG fonts that they offered, and using the beta version of the vue-fontawesome component, this was fine, but I was importing the entire font awesome library (over 1600 icons?), instead I imported only the icons I needed which was about 30/40 icons. This sped up the compilation process massively, and also lowered the vue webpack dev server initial's download, which was originally around 58MB to now 16MB.
TL;DR - Import only the fonts you need and make sure, when using fortawesome and SVG icons, do not import the entire icon library, and instead import only the icons you need. If you use like base SCSS sheets and you use scoped styling for your components, only import variables and mixins to each Vue file, and load helpers and any looping SCSS code globally to help with speeds.

@Anjgpt that's fair.
I mean I have not got the code to hand, but essentially.
So time summary;
Original Compilation - Between 15 - 20 minutes
Updated Compilation - Between 45 seconds - 1 minute and 20 seconds.
(First compilation is usually slower, the first one took around 1 minute and 20 seconds for me then the ones after only took around 45/48 seconds.)
Point 1 - SCSS imports.
I was using a base SCSS folder which included like 6 other SCSS files, 2 of them were just mixins and variables, the other 4 were helpers, and pre-defined styles, and one of the helpers loops and generates like loads of classes, and this was being imported into every single .vue file I had, instead I changed it to only import the two variables and mixins files, and then imported the other 4 files into the main App.vue file instead - this did speed up the SCSS compilation part dramatically.
Point 2: Font Awesome imports.
This was a bit more obvious, but a silly oversight on my end, I was using the @fortawesome package with the SVG fonts that they offered, and using the beta version of the vue-fontawesome component, this was fine, but I was importing the entire font awesome library (over 1600 icons?), instead I imported only the icons I needed which was about 30/40 icons. This sped up the compilation process massively, and also lowered the vue webpack dev server initial's download, which was originally around 58MB to now 16MB.
TL;DR - Import only the fonts you need and make sure, when using fortawesome and SVG icons, do not import the entire icon library, and instead import only the icons you need. If you use like base SCSS sheets and you use scoped styling for your components, only import variables and mixins to each Vue file, and load helpers and any looping SCSS code globally to help with speeds.

@dannysmc95 Thanks for the detailed summary.


Suggestion to add Move.IsPromotion and Move.IsEnpassant

I found a way to achieve this
move.Parameter is MovePromotion returns true when the move is a promotion.
And to find out what the promoted piece is, I do
Piece p = new Piece(move.Parameter.ShortStr[1]);
Console.WriteLine(p.Type);

And to check whether a move is EnPassant, I do
move.Parameter is MoveEnPassant
I guess this works since a move can't be both En Passant and promotion at the same time. But it's not very straightforward.
It would be nice if the library supported
Move.Promotion which returns the promoted piece or null when there is no promotion.
Also consider adding Move.IsEnPassant and Move.IsCastling
Anyways, thanks for the amazing library.

I like the idea!
Thank you for your feedback!

First of all, thanks for this awesome project! Also thanks for making this specific issue, I had the exact same problem and was happy with the solution shown here.
Knowing the solution, I'm honestly quite happy with the current implementation. You can elegantly check the type of move with an is statement and cast it to the specific type (e.g. MovePromotion) to get detailed information (e.g. to which piece the pawn is being promoted). For me this is mainly an issue of documentation. The Parameter property is named very generically and isn't found in the main documentation.
So my suggestion would be to rename the Parameter property to something more intuitive like "SpecialMoveDetails", add a more detailed description than "Move additional parameter", and include a short example in the main documentation on how it can be used to check for move type and get the move details from it.

@AlphaYui thank you for the feedback, I will make sure the docs are more descriptive


New-HTMLTableCondition doesn't work as expected

I have the following code here:
$baselinejson = Get-Content somejson.json | ConvertFrom-Json
$newjson = Get-Content newjson.json | ConvertFrom-Json
      $baselinejson,$newjson | Out-HtmlView -Compare -HighlightDifferences -Filtering -WordBreak break-all -
      {
        New-HTMLTableCondition -Name 'Status' -ComparisonType string -Operator eq -Value $false -BackgroundColor Red -Color White
      }

Issue is that the Status column with false values do not change the font color from black to white as specified in New-HTMLTableCondition.
Am I missing something here? Or is it not correct to use it this way?

Most likely ComparisonType needs to be set to bool?

No, just tried that and it does not work with bool also.
{
New-HTMLTableCondition -Name 'Status' -ComparisonType bool -Operator eq -Value $false -BackgroundColor Red -Color White
}

You sure
 $baselinejson,$newjson | Out-HtmlView -Compare -HighlightDifferences -Filtering -WordBreak break-all -
      {
        New-HTMLTableCondition -Name 'Status' -ComparisonType string -Operator eq -Value $false -BackgroundColor Red -Color White
      }

Is correct? What about that - at the end?

"-" at the end is added by mistake in the comment. Following is the correct code:
$baselinejson,$newjson | Out-HtmlView -Compare -HighlightDifferences -Filtering -WordBreak break-all
{
New-HTMLTableCondition -Name 'Status' -ComparisonType string -Operator eq -Value $false -BackgroundColor Red -Color White
}
But it still does not work

Without some reproducible code it will be hard to help you. I don't have the json files. Can you replicate it on smaller example?

Okay, will the below json work?
$baselinejson = {
"auditReportVersion": 4,
"vulnerabilities": {
"@pmmmwh/react-refresh-webpack-plugin": {
"name": "@pmmmwh/react-refresh-webpack-plugin",
"severity": "high",
"isDirect": false,
"via": [
"ansi-html"
],
"effects": [
"react-scripts"
],
"range": "<=0.5.0-rc.6",
"nodes": [
"node_modules/@pmmmwh/react-refresh-webpack-plugin"
],
"fixAvailable": {
"name": "react-scripts",
"version": "5.0.1",
"isSemVerMajor": true
}
}
$newjson= {
"auditReportVersion": 2,
"vulnerabilities": {
"@pmmmwh/react-refresh-webpack-plugin": {
"name": "@pmmmwh/react-refresh-webpack-plugin",
"severity": "high",
"isDirect": false,
"via": [
"ansi-html"
],
"effects": [
"react-scripts"
],
"range": "<=0.5.0-rc.6",
"nodes": [
"node_modules/@pmmmwh/react-refresh-webpack-plugin"
],
"fixAvailable": {
"name": "react-scripts",
"version": "5.0.1",
"isSemVerMajor": true
}
}

It's a nested object, isn't it? So how are you comparing it?

$baselinejson = Get-Content old.json | ConvertFrom-Json
$newjson = Get-Content new.json | ConvertFrom-Json

$baselinejson, $newjson | Out-HtmlView -Compare -Filtering -WordBreak break-all {
    New-HTMLTableCondition -Name 'Status' -ComparisonType string -Operator eq -Value $false -Color Blue -BackgroundColor YourPink
} -FlattenObject

If I add highlight

It seems to work fine, with exception of the background color which probably is in conflict with built-in rules.

Oh, I get it. It is working fine for me now. Thanks much.
Also, is there a way we can get the value of Status in a variable?


Placing node_modules outside project directory breaks Sails

Sails version: 0.12.3
Node version: 5.11.0
NPM version: 3.9.0
Operating system: Docker / Alpine Linux

See also closed issue #2505.
Sails breaks when the node_modules directory is outside the project directory. In my case, I have installed node_modules one level above my project source. Node is supposed to walk up the filesystem looking for matching node_modules directories.
This is extremely important when creating an isolated development environment in Docker. It is a Docker best practice to inject development code into a container by mounting a local volume from the Host. Requiring the node_modules directory to be inside the project directory means that any developer working on my source must install node, npm, and all the dependencies locally -- which defeats the purpose of running a Docker development environment. More importantly, the container is forced to use the local system's node_modules. If there are any modules that have native dependencies, this setup will not work cross-platform. (again, defeating the purpose of Docker...)
To recreate this issue, simply take any working sails project and move the node_modules directory up one level. I received the following errors when I did so:
info: Could not find module: ejs in path: /app/src/node_modules
error: A hook (`session`) failed to load!
error: Could not load Connect session adapter :: connect-redis

Error from adapter:
Error: Cannot find module '/app/src/node_modules/connect-redis'
    at Function.Module._resolveFilename (module.js:339:15)
    at Function.Module._load (module.js:290:25)
    at Module.require (module.js:367:17)
    at require (internal/module.js:20:19)
    at Hook.SessionHook.initialize (/app/node_modules/sails/lib/hooks/session/index.js:163:32)
    at Hook.wrapper [as initialize] (/app/node_modules/sails/node_modules/lodash/index.js:3095:19)
    at /app/node_modules/sails/lib/hooks/index.js:74:16
    at /app/node_modules/sails/node_modules/async/lib/async.js:52:16
    at /app/node_modules/sails/node_modules/async/lib/async.js:548:17
    at /app/node_modules/sails/node_modules/async/lib/async.js:542:17
    at _arrayEach (/app/node_modules/sails/node_modules/async/lib/async.js:85:13)
    at Immediate.taskComplete (/app/node_modules/sails/node_modules/async/lib/async.js:541:13)
    at tryOnImmediate (timers.js:534:15)
    at processImmediate [as _immediateCallback] (timers.js:514:5)

Do you have the Connect session adapter installed in this project?
Try running the following command in your project's root directory:
npm install connect-redis
(Note: Make sure the version of the Connect adapter you install is compatible with Express 3/Sails v0.10)

error: A hook (`orm`) failed to load!
error: ** Grunt :: An error occurred. **
error:
------------------------------------------------------------------------
Aborted due to warnings.
>> Local Npm module "grunt-contrib-clean" not found. Is it installed?
>> Local Npm module "grunt-contrib-coffee" not found. Is it installed?
>> Local Npm module "grunt-contrib-concat" not found. Is it installed?
>> Local Npm module "grunt-contrib-copy" not found. Is it installed?
>> Local Npm module "grunt-contrib-cssmin" not found. Is it installed?
>> Local Npm module "grunt-contrib-jst" not found. Is it installed?
>> Local Npm module "grunt-contrib-less" not found. Is it installed?
>> Local Npm module "grunt-sails-linker" not found. Is it installed?
>> Local Npm module "grunt-sync" not found. Is it installed?
>> Local Npm module "grunt-contrib-uglify" not found. Is it installed?
>> Local Npm module "grunt-contrib-watch" not found. Is it installed?
Warning: Task "watch" not found.
------------------------------------------------------------------------

error: Looks like a Grunt error occurred--
error: Please fix it, then **restart Sails** to continue running tasks (e.g. watching for changes in assets)
error: Or if you're stuck, check out the troubleshooting tips below.

error: Troubleshooting tips:
error:
error:  *-> Are "grunt" and related grunt task modules installed locally?  Run `npm install` if you're not sure.
error:
error:  *-> You might have a malformed LESS, SASS, CoffeeScript file, etc.
error:
error:  *-> Or maybe you don't have permissions to access the `.tmp` directory?
error:      e.g., `/app/src/.tmp` ?
error:
error:      If you think this might be the case, try running:
error:      sudo chown -R YOUR_COMPUTER_USER_NAME /app/src/.tmp

Symlinking the node_modules directory, as discussed in the closed issue I referenced earlier, will not help. When you inject a local Host volume into a container, the Host volume overlays the existing content in the container. Therefore, any symlink would also be masked from the container. For anyone not familiar with Docker, the idea would be to have a directory layout like the following in the container:
-- app
    -- node_modules
    -- src

With this structure, you can inject the app/src directory from the Host without disturbing the dependencies and without requiring anything but the project source files on the Host. Please see https://docs.docker.com/engine/userguide/containers/dockervolumes/#mount-a-host-directory-as-a-data-volume for more info.

Wow...  30 days and nothing except bot responses. I've heard rumors sails development was stalled, but the deathly silence here is much more troubling. Is it time to find a new framework?

What other Node.js frameworks survive moving the node_modules directory outside of the project directory?  Doesn't really matter if it's in a linked folder on the host, they don't need Node.js or a build environment. Only the container needs have those.

It's part of the Node spec that the node_modules directory can be located anywhere in the parent directory structure:  https://nodejs.org/api/modules.html#modules_loading_from_node_modules_folders. Do you have examples of other frameworks that break this?
The container does run npm install. The problem is, if I inject code into the container during development, the node_modules directory disappears -- unless it also exists in the development source. That's the way Docker works. If I have my sails project in /app/src in the container and I inject my local source code using the the -v flag ---  -v ${PWD}:/app/src --- the current directory on the host overlays the /app/src directory in the container. So, if node_modules is required to be in that directory, it must also exist on the host, symlink or not.
I've recently found a hacky work-around. If you create a symlink in the container to a node_modules outside the project, and then create a symlink in the development source on the host to an empty node_modules directory in the same relative location, it seems to work. I mention this for other people struggling with the same issue. YMMV. My fear is the sails response will be, "Oh, well it's fixed!", this issue will be closed, and the underlying problem will continue to bite people.
And none of this addresses my other point:  the absolute lack of involvement on this issues board. I've looked through the currently open issues and the vast majority of responses here are from @sailsbot. It begs the question of how many open issues go 30 days without a response and then just get automatically closed by the bot system. Not very confidence inspiring.
I LIKE sails. I want to continue USING sails. But I don't want to get stuck in a framework that doesn't have a robust development community.

First off, if you're running a development environment, as such, why can't you have the developer run a container command that fires off an npm install in the linked source directory?
Secondly, if we're relying on the package maintainer to perform every task, including bug-fixes and support, we're hardly a community, now are we? Most of the issues on the board are in fact not bugs, a large number of them are requests for support. And, there are much better channels for support than trying to get a response from a package maintainer. There's IRC, there's Gitter, and there's all kinds of resources on the web to consult if you've run into a problem.
If it's a pull request, sometimes it's not something a maintainer wants to handle on their own since it will impact a larger number of people that already use the project. So, let's do what open source software communities do... Implode... Or I guess we can take some of this responsibility upon ourselves and see if we can't move the project along.
What would it take, in your opinion, to get proper node spec support for node_modules directories outside of the project directory? Have you dug into the code? Is there a pull request we can mess around with? Unit tests? What can I do to help?

The "linked source directory" is the directory on the host machine -- in other words, it's the developer's own local environment. If you "fire off an npm install" in that directory, you are essentially installing all of the node / project dependencies onto the developer's local machine. This completely defeats the purpose of container isolation that you are trying to achieve by using Docker. I'm not sure how to be more clear on that...
Package maintainers may not be able to perform every task, but shouldn't they at least take the responsibility to respond to issues and pull requests? It would be nice to at least hear from a maintainer -- "Hey! That's a really tough issue. I don't have time to work on it right now. I can help you, if you'd like to try to contribute. It's located in these files. You should watch out for things like this..." But dead silence for 30 days, and the only way to get someone to respond is to question the viability of the project? Really? That doesn't fire me up to want to break open the code and contribute. There are thousands of projects to work on and lots have open and inviting communities that encourage involvement -- not automated, issue tracking bots that close open issues and sweep them under the rug after 30 days. It's not like this is a new problem. It was first reported in December 2014. (#2505) Same basic use case -- wanting to isolate a dev environment.
FYI, there was a pull request submitted by @stanislavromanov 17 days ago, right under my initial comment, if you're serious about offering to help. (and I appreciate your offer) However, there's been no response on that thread either. No matter how much anyone wants to help, the maintainers are the only ones who can approve and commit new code. If pull requests are completely ignored -- no input, no guidance, no recommendation on how to proceed or insight on why it's not being accepted -- we're hardly encouraging the community to contribute, now, are we?

@jeff-kilbride
What I did is just forked the latest stable release of Sails, put it in my package.json and it does what I want. It's not like Sails is updating anyway so it's perfectly fine with me.

@stanislavromanov
Thanks! Yeah, I've been considering doing that myself. I've dug around in the code a bit before to help chase down a problem with the way models were handling email addresses. That issue got resolved relatively quickly, but that was a while ago. I've looked at your commit. What bothers me is that, from your example, this seems like a simple fix -- don't prepend the project path to the require statement. But who knows if there are other gotchas or if this was done for a reason at some point in the past.
My bigger issue is the fact that sails isn't updating. I've taken the time to learn sails and I really like everything it does. I even recommend it to others when starting new projects. However, I'm not comfortable relying on it for production when there's little participation and the issues board is a ghost town.  I think it's a legitimate concern. There are a ton of node / javascript frameworks. There are even other languages I want to explore, like Go. I hate the idea of walking away from the time I've spent in the sails learning curve, but I also don't want to wind up maintaining my own fork by myself. Not getting any response here makes it easier to choose something else.

@jeff-kilbride
I use Sails in pretty large project with enough traffic and I found no issues with this "fix" so far.
As for your second concern - I don't recommend using Sails in any new project. It might be harsh but it's true.

@stanislavromanov
Thanks for the honesty. Unfortunately, that's the decision I'm coming to myself.

Could try trails... The sails ES6 spin off from a former sails.js
contributor/team. I haven't tried it yet, but seems promising. We are still
tightly coupled with sails with several existing web applications.
On Fri, Jun 17, 2016 at 6:15 PM Jeff Kilbride<EMAIL_ADDRESS>wrote:

@stanislavromanov https://github.com/stanislavromanov
Thanks for the honesty. Unfortunately, that's the decision I'm coming to
myself.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/balderdashy/sails/issues/3732#issuecomment-226894248,
or mute the thread
https://github.com/notifications/unsubscribe/ACsR6GLb2a-MxzQNqqIsjj9tjm84oGfdks5qMxyKgaJpZM4IfJP-
.

@animedbz16
I looked at trails the other day. Unfortunately, there's very little documentation. Oh well...  at least it's given me the push to start reading "Go in Action".

@tbjers @jeff-kilbride @stanislavromanov @animedbz16 First of all, thanks for taking the time to share your thoughts and feedback.  I did my best to address points brought up by everyone below, and then followed up with an explanation
@jeff-kilbride Thanks for posting the solution that worked for you.  I understand this is a limitation for certain use cases, and I'm more than happy to help get a solution merged. More on that in a sec.
@stanislavromanov Forking is an excellent option when you need something in core that a project hasn't merged.  As you mentioned, the only problem is dealing with merging upstream edits.  Fortunately, as you pointed out, since Sails has become increasingly stable over the years, we've been careful to focus our changes on security, performance, and stability.  This makes the experience of working with Sails better for everyone, since you don't have to worry about everything breaking when you upgrade to the next version.

Aside: @stanislavromanov Just to be transparent, you should be aware that Sails v1.0 will bring some major changes-- but I think based on what you mentioned, you'll be fine on your fork.  The only thing I'd watch out for is the federation of core hooks (but even then, worst case you'll just need to spend a few minutes applying the change to a separate repo).  See #3504 for more information.

What's important to me is that we keep moving towards Sails becoming even more stable, efficient, and secure.  Obviously, productivity features are important to me as well-- but at the end of the day, that really comes down to flexibility.  Everyone has their own idea of what they'd like to see in Sails, and so to allow that, we've worked to make the framework as customizable as possible via custom database adapters, generators, asset pipeline tasks, view engines, session adapters, file upload adapters, socket adapters, and hooks.  Of course, as an opinionated framework, we have to use a set of relatively strong default conventions.  And since the final decision on those conventions is inevitably decided by me, it means it won't always be right for everyone out of the box.  Also, as @tbjers pointed out, because there are so many people using Sails nowadays, we have to be really careful not to mess things up for existing users.
Still- that doesn't mean we won't merge code that isn't a bug fix (especially if it's something that deals with optimization or making things more flexible).  It's just that I ask that the people who need the feature go through the process of opening a proposal to discuss, gauge community interest, and spec out what changes will need to take place in the core code base, in the tests, and in the documentation (see https://github.com/balderdashy/sails/blob/master/CONTRIBUTING.md#v-proposing-features-and-enhancements for guidelines).
The issue being discussed here is a change in how Sails works by default-- but it's a change that I agree with. The question is just how we do it.  So all I'd ask is that we go through the process of opening a proposal to discuss.
I responded w/ some ideas and a request for a proper proposal here: https://github.com/balderdashy/sails/issues/2505#issuecomment-227216195


CORGI-613: Add Django/DRF Token Authentication

https://issues.redhat.com/browse/CORGI-613
This adds an example view and tests to demonstrate using DRF Token-based authentication only on write operations.

@RedHatProductSecurity/corgi-devs Please review. My intent is that we can add this type of authentication transparently to endpoints that need write capabilities.


add gulp workflow #147

Signed-off-by: Zell Liew<EMAIL_ADDRESS>

Thanks for working on this! However, I see several issues that prevent me from merging this for now:

Obsolete prefixed properties and functions have been added, such as -webkit-transform or -webkit-linear-gradient(). The target browser support for this project is recent versions of evergreen browsers, since slides are a controlled environment.
Inline source maps add weight
I personally find mandatory auto-browser reload quite annoying and wouldn't want to impose it on people.
You didn't use git add . --all, so moved files are presented as new files, making it impossible to review their diff.

To be honest, I'm not sure if adding a gulp workflow would help if you don't want to:

Reload the browser
Preprocess / postprocess CSS
Add vendor prefixes

imo, it doesn't add much value to just add cssnext, because it doesn't help much too. What do you think?


超长稿件标题过长上传失败

标题超过80字符导致上传任务失败，能否添加标题字数限制，自动删减超出字符

[youtube] 8dpdNWd2bBs: Downloading webpage
[youtube] 8dpdNWd2bBs: Downloading js player 7bc032d0
[youtube] 8dpdNWd2bBs: Downloading js player 7bc032d0
[youtube] 8dpdNWd2bBs: Downloading MPD manifest
[download] videos\8dpdNWd2bBs.mp4 has already been downloaded and merged
[Download] All done
[Upload] Start uploading
[Upload] Uploaded video file successfully.
[Upload] Uploaded thubmnail successfully.
[Upload] Submitting
(21103, '稿件标题过长,已经超过80个字符')

[youtube] 8dpdNWd2bBs: Downloading webpage
[youtube] 8dpdNWd2bBs: Downloading js player 7bc032d0
[youtube] 8dpdNWd2bBs: Downloading js player 7bc032d0
[youtube] 8dpdNWd2bBs: Downloading MPD manifest
[download] videos\8dpdNWd2bBs.mp4 has already been downloaded and merged
[Download] All done
[Upload] Start uploading
[Upload] Uploaded video file successfully.
[Upload] Uploaded thubmnail successfully.
[Upload] Submitting
(21103, '稿件标题过长,已经超过80个字符')

已修复

已修复


Updated react-komposer, dependencies

@arunoda can we pull these in, the wrapper packages are using pretty dated versions

Please upgrade to<EMAIL_ADDRESS><EMAIL_ADDRESS>depends<EMAIL_ADDRESS>and it conflits with other libraries that depend mobx@3. <EMAIL_ADDRESS>removes dependency of mobx.

Can I help maintain this?
@arunoda @sungwoncho @tomitrescak

@ndelangen i think this is part architecture problem. the fact that there are umbrella packages within mantra is part of the issue with it. you'll always have outdated deps that need updating. it looks like a smell to me. i think it's better to write abstractions into your local codebase for needed methods instead of looking at the mantra package for the versions.

I've published @storybook/mantra-core to alleviate our peer dependency warnings for React 16.
@ndelangen I don't think we should be maintaining this ecosystem for the sake of Storybook. We should really just migrate off of it.

I agree @danielduan, we should move away from unmaintained packages, or somehow get them to be maintained again, maintain them ourselves or otherwise.
By forking and republishing you've essentially chosen to start maintaining without the 'burden' of current users. Forking should be the last resort.
Having said that; I support your choice 100%, it seems these packages have been abandoned, and now no-one is left to transfer ownership even.

Still open to help get this package updated a bit. Give me access to the repo and npm, and I'll do it.

@ndelangen I do not have admin access to this repo. I think @arunoda never did a proper handover before leaving Meteor. Therefore all Mantra related projects are in a limbo. I tried to ping him many times but sadly never got a reply.

@sungwoncho thanks for trying anyway!


[Spotify] Option to hide menu bar player when nothing is playing, truncate text to length

Extension
https://www.raycast.com/mattisssa/spotify-player
Description
I'd like it if the Spotify menu bar feature would either minify itself down to just the spotify logo or somehow go away if I've been not playing anything for more than a few minutes (possibly configurable). Menu bar space is precious on a macbook air and I don't really need to know what's going on most of the time.
Also, if the song title is on the longer side, it can easily drive the menu bar into the annoying state where the date becomes only the day of the week and the menu bar item becomes cutoff. It would be preferable if the name would truncate to a certain length!
Example of a (actually pretty reasonable song name) causing overflow and being cutoff

Who will benefit from this feature?
All users of the menu bar extension, which I'd imagine many users have tried and then disabled because some of how it behaves is really frustrating and a bit of a non-starter.
Anything else?
Just the images above showing the issue!

Hey! Thanks for the suggestion. Have you seen this feature in the command's preferences?

Or would you like to have a separate action that allow you to expand/collapse it dynamically?


Automated build for PRs?

While #15 adds instructions for users to build the portal site locally, which is great for testing purposes, it would be even better to automate this.
Is there a github action or other mechanism we can use so that the rendered site is built automatically for every open pull request? E.g. anyone can download a zip file of the rendered site and view locally in a browser?

Now that #17 has been merged, any subsequent PR event will trigger a build on Readthedocs... Clicking on details takes the user to a preview link on Readthedocs:

Now that #17 has been merged, any subsequent PR event will trigger a build on Readthedocs... Clicking on details takes the user to a preview link on Readthedocs:

@andersy005 this is great! I just test-drove this over at #15 and it works great. This should accelerate our work of building out the  site.

@andersy005 this is great! I just test-drove this over at #15 and it works great. This should accelerate our work of building out the  site.

I'll close this, since we now have a great working solution.

I'll close this, since we now have a great working solution.


New autocomplete is broken for JOINs

Description

https://github.com/user-attachments/assets/0394d3df-bd94-4919-bae5-fb8e8f681d8e
DBeaver Version
DBeaver 24.2.4
Operating System
windows 10
Database and driver
No response
Steps to reproduce
No response
Additional context
No response

verified