how to print options by default? options do not display unless -h is passed

How do I print the options by default (without passing -h)?
he documentation doesn't make clear the -h argument must be passed to print the 'options'. As I don't even have a -h usage line, and this is more work for my users, I would rather print the options by default.

If you mean: when user gives non-match cli args, print usage and options
I guess the answer is: no api in docopt can do this, according to source code here and here
If you dont mind, I wrote a similar project that have this behavior, here is the online demo

Hello, everybody.
@nmz787: If you make all the options/sub-commands mandatory then, when your program is executed, the help text will be printed by default.

I also need this ability.
@Odyseus do you mean this ?

[ ] (brackets) optional elements. e.g.: my_program.py [-hvqo FILE]

So it means I have to put everything inside brackets ?
I tried it with no luck. Would you like to give slight example from naval_fate
Thanks

Hello, @azzamsa.
Now that I read nmz787's message with more attention (and awake), I completely misunderstood the issue.
Currently, it is not possible to execute a command without arguments and obtain the following output.
$❯ my-app
Usage:
    my-app --option

Options:
    -h --help     Show this screen.
    --option      Description.

Maybe TylerTemp's answer would be more suited to your needs.

no api in docopt can do this,

Did he meant that docopt can't achieve this ? because the source code says if nothing match, then exit and he suggested to give try docpie instead ?

@azzamsa hi,
Yes,

docopt can not achieve this
Well, that's only one suggestion. Other way is,  you can modify docopt source code by yourself and use it, or wait docopt to support this feature

@TylerTemp Hi Tyler. Thanks lot for great explanation.

While docopt doesn't support it directly, this is the small cheat I often use:
"""
Usage:
    my-app --option

Options:
    -h --help     Show this screen.
    --option      Description.
"""
import docopt
import sys

def main():
    args = docopt.docopt(__doc__)

if __name__ == '__main__':
    if len(sys.argv) == 1:
        sys.argv.append('-h')
    sys.exit(main())

Hi Bob, I will give your suggestion a try on Monday, it looks simple
enough. Thanks.
On Sat, Jul 14, 2018, 4:48 AM Bob Tolbert<EMAIL_ADDRESS>wrote:

While docopt doesn't support it directly, this is the small cheat I often
use:
"""Usage:    my-app --optionOptions:    -h --help     Show this screen.    --option      Description."""import docoptimport sys
def main():
args = docopt.docopt(doc)
if name == 'main':
if len(sys.argv) == 1:
sys.argv.append('-h')
sys.exit(main())
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/docopt/docopt/issues/420#issuecomment-405018014, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABE7RuJoMmbr3ZoV8-FOwO-aOlv4yzMwks5uGdqMgaJpZM4VFzuZ
.

A little something I use myself :
def print_help():
    sys.argv.append('-h')
    docopt.docopt(__doc__)


Improvement of UI in Find a Doctor page

Description
UI Improvements for the "Find a Doctor" Page
-> Added spacing between icons and text in the navbar.
-> Applied background color to the dropdown list and Sort button.
-> Adjusted layout to fit two cards into one row.
Related Issues

Closes #1108

Type of PR

[X] (Bug Fix)

Screenshots / videos (if applicable)

Before:

After:

Checklist

[X] I have gone through the contributing guide
[X] I have updated my branch and synced it with project main branch before making this PR
[X] I have performed a self-review of my code
[X] I have tested the changes thoroughly before submitting this pull request.
[X] I have provided relevant issue numbers, screenshots, and videos after making the changes.
[X] I have commented my code, particularly in hard-to-understand areas.

Additional context:

@Anishkagupta04 @varshith257
Please review this PR and assign labels.

@varshith257 Kindly review this PR.

@varshith257 Please review this PR.
Thank you.

@varshith257
Please review this PR and assign labels.
Thank you.

@varshith257
Please review this PR.
Thank you.

@varshith257
Is this fine or do I need to make any changes.
If no please merge this PR and assign labels.

@varshith257
Please review this PR.

Thank you @varshith257

Hi @varshith257 , I've really appreciated your guidance and would like to stay connected. Could you please share your LinkedIn profile so I can add you to my network..


Scam Account Submission

Duplicate Submissions

[X] Yes, I checked that the account name is not currently in the list
[X] I read the wiki explaining each different categories and examples before submitting

(Required) Spam Comment Direct Link
There's no option for me to submit this kind of spammer, so I'll just put it under Scam Accounts. It did not get caught by using the auto-smart mode.
Video Link: https://youtu.be/YJSMlkGvSzE
Spammer channel link: https://www.youtube.com/channel/UCDmzkegVrrlY08aYXMae5TQ
(Optional) Screenshot of comments referencing the scam account

(Required) List of the scam account names
⛔tap my profile to meet me and more⛔

Yep the program used to miss these, but as of today, the latest releases should catch them (2.16.10 and 2.17 betas):


plot range in x and y works differently if scatter=True

calling plot_points with scatter=True plots point with a larger range than data for x and y, a white frame is shown around data. Normal plot (without scatter), plots exact range of data (preferred behaviour).

this is a feature of plt.scatter vs plt.plot(). Maybe there is an option or a workaround to make it more uniform.

Hi,
Can I join this project?


Switch to Python 3.13 stable

What I did
Move to Python 3.13 from 3.13.0-rc.2

Label to run tests once 3.13 is in the python-runner action

Running tests.


Ensure every resource helper includes cmdlet

Once naming conventions for cmdlets is decided on, existing cmdlets should be updated to match naming convention
Acceptance Criteria:

[ ] Cmdlets names are updated to match naming conventions and checked into repository

This issue may already be covered by #32 ?

Document added to the Team Channel's Files.


Chore/upgrade node

Node v14 reached end-of-life-status last year, this upgrades the package to use Node v20.
Node v10 & v12 support is dropped. All apps using this package are on Node v14 or greater.
Note: I bumped the package version to 0.3.7, but am unsure if I should have for this.

From semver:
Patch version Z (x.y.Z | x > 0) MUST be incremented if only backward compatible bug fixes are introduced. A bug fix is defined as an internal change that fixes incorrect behavior.
Minor version Y (x.Y.z | x > 0) MUST be incremented if new, backward compatible functionality is introduced to the public API. It MUST be incremented if any public API functionality is marked as deprecated. It MAY be incremented if substantial new functionality or improvements are introduced within the private code. It MAY include patch level changes. Patch version MUST be reset to 0 when minor version is incremented.
Major version X (X.y.z | X > 0) MUST be incremented if any backward incompatible changes are introduced to the public API. It MAY also include minor and patch level changes. Patch and minor versions MUST be reset to 0 when major version is incremented.
A pre-release version MAY be denoted by appending a hyphen and a series of dot separated identifiers immediately following the patch version. Identifiers MUST comprise only ASCII alphanumerics and hyphens [0-9A-Za-z-]. Identifiers MUST NOT be empty. Numeric identifiers MUST NOT include leading zeroes. Pre-release versions have a lower precedence than the associated normal version. A pre-release version indicates that the version is unstable and might not satisfy the intended compatibility requirements as denoted by its associated normal version. Examples: 1.0.0-alpha, 1.0.0-alpha.1, 1.0.0-0.3.7, 1.0.0-x.7.z.92, 1.0.0-x-y-z.--.


cigien: Watch oxygenmag.com

cigien requests the watch of the watch_keyword oxygenmag\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

oxygenmag\.com has been seen in 1 true positive, 0 false positives, and 0 NAAs.

Approved by Spevacus in Charcoal HQ


Getting and building wiki page should be updated to refer to VS 16.0 (or 16.1 preview?)

https://github.com/aspnet/EntityFrameworkCore/wiki/getting-and-building-the-code

Updated.


Generate collections for all classes

In populate.rs, a long list of Collections are constructed - one for each class in Atomic Data (Class, Commit, Agent, etc.). This is because as an end-user, I want to browser this data. I want to be able to share a URL for each of these concepts. How should these collections be constructed?
Manually create collections
This is what I'm currently doing with the atomic_lib::populate::populate_collections function. Not great. I've made things a bit cleaner by having a helper functionL CollectionBuilder::class_collection.
In populate, iterate over all Classes

It only generates the collections once, which is efficient.
The collections themselves exist in the store this way, which means they are indexed and can be searched through.

Let the dynamic 'collections' collection generate dynamic collections
When a users requests the Collections collection, the back-end fetches all Classes, and generates a Collection for each class. But how would the individual Collections be resolved?
Let the front-end generate collection links
Since collections are fully dynamic, the URL can be created by the front-end. example.com/collection?property=isA&value=myClass.
However, these cannot be discovered when browsing the API, and the URLs will be long and hard to read. Not good.
I feel like opting for option 2: In populate, iterate over all Classes

Now, collections are generated by populate_collections. The generated URLs use the shortname property, which results in paths like /class instead of a plural like /classes. Plurals are more conventional, and they seem more semantically correct, as the path actually resolves to multiple instances instead of the class itself.
Approaches:

Add a plural_shortname property to classes
Add an s to the shortname (doesn't work for propertys)
Revert to manual collection creation
Add a collection/{} prefix


Image isn't properly ratioed in GridItems

If you can see from the above image , after taking all the photos to convert to pdf the page where it displays does not have proper ratioed image view function.

If you consider this to be resoled can you assign this issue to me. If yes can you add the gssoc21 label too

Shouldn't you guys be adding the lable too of gssoc21

Shouldn't you guys be adding the lable too of gssoc21

Ya. I was expecting the github action to take care of it

haha its alright. May i ask when im merging should i do anything in the issue part. Do i just have to merge it into a new branch.

merge it in master only.


Missing types in dist of release 6.1.2

Environment

System:

OS: macOS 14.1.2
CPU: (8) arm64 Apple M1 Pro
Memory: 321.38 MB / 32.00 GB
Shell: 5.9 - /bin/zsh

Binaries:

Node: 20.8.1 - /opt/homebrew/bin/node
Yarn: 1.22.21 - /opt/homebrew/bin/yarn
npm: 10.1.0 - /opt/homebrew/bin/npm
pnpm: 8.9.2 - /opt/homebrew/bin/pnpm

Reproduction
Steps to reproduce
Install the latest version of styled-components "6.1.2"
Expected Behavior
types are included in the dist.
Actual Behavior
There are not types included in the dist
Last working version was "6.1.1"

Please pass the necessary basic testing when releasing the new version.

same here, no types


Xrm.Utility.refreshParentGrid: lookupOptions does not require Id.

[Enter feedback here]
Currently the Xrm.Utility.refreshParentGrid() lookupOptions object does not require an Id value to run.  If the Id is not set, then all views of the provided entityType will refresh.

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

ID: 865dbc8c-3efc-003e-daa0-1da2df35a014
Version Independent ID: f197b7d3-fcc9-8949-ff4c-513e1baf4109
Content: refreshParentGrid (Client API reference) in model-driven apps - Power Apps
Content Source: powerapps-docs/developer/model-driven-apps/clientapi/reference/Xrm-Utility/refreshParentGrid.md
Service: powerapps
Sub-service: mda-developer
GitHub Login: @jasongre
Microsoft Alias: jasongre

Thanks for your comment, @ThreeTen22. This issue has been assigned to the doc author for review.

@ThreeTen22
Hi -
Thanks for your feedback.
Just paraphrasing to make sure I understand:

The article calls out that the Id parameter is required. Seems like you are expecting an error if it isn't provided.
Because it isn't provided, then all the views for the specified entitytype are refreshed.

@jasongre:
Some options here:
If updating all the views for the specified entitytype has value, we could update this to call out that this is by-design.
Otherwise, it seems like we have a validation bug and we should throw an error if the id value isn't specified.
How would you like to handle this?

@ThreeTen22
Thanks for updating. I've heard from @jasongre about this and it looks like what you have observed is correct.
We are awaiting confirmation from dev team.
I'm also curious why someone would want to provide the id parameter value, assuming it would only refresh one of the views. What is the benefit there?

It might just update the row on views which matches the Id given, which would skip views that may not need to be refreshed.  Helpful for editable grids and views with lots of rows


Make manifest redirections sticky for updates

Resolves https://github.com/google/shaka-player/issues/1367

@joeyparrish, I have seen that there was a test that covered the functionality, so I have updated it to meet the new requirements.

Something seems to be wrong with our build bot.  I will investigate.

Thank you!


Spike: Use ProtoBuf with PySpark

Synopsis
Evaluate whether ProtoBuf can be used with PySpark.
Acceptance Criteria
Criteria does not need to be deployed to nor tested in neither U nor T. Localhost and separate branch will suffice.

Messages on the Eventhub is stored in protobuf format
The streaming job can consume the protobuf message from the Eventhub
The streaming job can validate timeseries in the protobuf format.

For tester: Code is in branch Use_protobuf_for_received_time_series and usable CIM XML documents exist in the Postman collection. Feel free to reach out to @BjarkeMeier or @HenrikSommer for assistance as needed.

Btw, I skipped the review stage of the issue as this is only a spike to proof that we are able to use ProtoBuf in PySpark.

Test
I've send the message in the postman

Then the streamingjob procssed the data

verified that valid data was stored.


Attaching sources for eclipse

In Eclipse, does anyone know how to attach BC sources using archive files provided on the website?
Usually dedicated source jar archive is used and then you can define in Source Attachment Configuration the jar location containing the source for a library.
Sources and Javadoc are available here in section source and Javadoc
https://www.bouncycastle.org/latest_releases.html

I'm not sure, if I understand your question.
So let me start with, that I use maven.
<dependency>
	<groupId>org.bouncycastle</groupId>
	<artifactId>bctls-jdk15on</artifactId>
	<version>1.70</version>
</dependency>
<dependency>
	<groupId>org.bouncycastle</groupId>
	<artifactId>bcutil-jdk15on</artifactId>
	<version>1.70</version>
</dependency>

With the eclipse maven plugin the BC source are attached without any special "to do". It just works. So, mayb just using maven as build systems works for you as well?

Usually dedicated source jar archive is used and then you can define in Source Attachment Configuration the jar location containing the source for a library.

Not sure, if I understand that. You setup Eclipse IDE as usual, but with the BC sources from that downloads it doesn't work?
Maybe you try out the jars (class + source) from maven central?

Thank you for the inputs Achim.
I was finally able to configure Eclipse to access the BC source code by using the source jars available on maven central.


Update machine version

This change is

src/AssemblyInfo.props line 6 at r1 (raw file):

		<Version Condition=" '$(VersionSuffix)' != '' ">$(Version)-$(VersionSuffix)</Version>
		<AssemblyVersion><IP_ADDRESS></AssemblyVersion>
		<FileVersion><IP_ADDRESS></FileVersion>

If we are going to lock down the pull request and commits directly to main, we need to have an efficient release process that doesn't require pull requests, etc.  One option could be https://github.com/versionize/versionize?tab=readme-ov-file.  It may require a bit more research, especially looking at using conventional commits throughout, but it may be valuable long term.

src/AssemblyInfo.props line 6 at r1 (raw file):
Previously, johnml1135 (John Lambert) wrote…
If we are going to lock down the pull request and commits directly to main, we need to have an efficient release process that doesn't require pull requests, etc.  One option could be https://github.com/versionize/versionize?tab=readme-ov-file.  It may require a bit more research, especially looking at using conventional commits throughout, but it may be valuable long term.

Actually versionize also commits directly to main - let me see if there is another way around this.

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

Project coverage is 67.04%. Comparing base (a9058ce) to head (d1392d3).

Additional details and impacted files
@@           Coverage Diff           @@
##           master     #183   +/-   ##
=======================================
  Coverage   67.04%   67.04%
=======================================
  Files         441      441
  Lines       34831    34831
  Branches     4670     4670
=======================================
  Hits        23351    23351
  Misses      10387    10387
  Partials     1093     1093

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

src/AssemblyInfo.props line 6 at r1 (raw file):
Previously, johnml1135 (John Lambert) wrote…
Actually versionize also commits directly to main - let me see if there is another way around this.

In looking at the various options, I am inclined to think that we should just allow commits to master.  We make make explicit the convention that we have been using, namely that commits can be made directly to master for:

Version increments and releases
CI updates
Documentation updates? (do we want to review these?  Are any documentation updates ok?  What about Swagger documentation, or Readme?)

For documentation, although I have committed documentation directly to master before, the urgency and complex dependencies for CI and versioning are not there while the importance of discretion, wording and clarity is.  Let's say that all documentation updates need a pull request.

src/AssemblyInfo.props line 6 at r1 (raw file):
Previously, johnml1135 (John Lambert) wrote…
In looking at the various options, I am inclined to think that we should just allow commits to master.  We make make explicit the convention that we have been using, namely that commits can be made directly to master for:

Version increments and releases
CI updates
Documentation updates? (do we want to review these?  Are any documentation updates ok?  What about Swagger documentation, or Readme?)

For documentation, although I have committed documentation directly to master before, the urgency and complex dependencies for CI and versioning are not there while the importance of discretion, wording and clarity is.  Let's say that all documentation updates need a pull request.

Also, should I be an admin on Machine?


Emit Tcl with PIM configuration

This will make it possible to drive synthesis from the PIM decisions.  E.g., Quartus can detect
that HSSI is in use with:
[info exists platform_cfg::AFU_TOP_REQUIRES_HSSI_RAW_PR]

Tests pass: http://sw-pert.altera.com/pert/pert.php?test_run_id=2174609
Also built a few AFUs (outside arc)


Helm has no versions in cache.json

https://github.com/devops-works/binenv/blob/a755fd9516a63162f89f7d0d331870ded3b795f6/distributions/cache.json#L2658
$ binenv version
binenv version 0.12.0 (built 2021-08-06T06:27:10Z)

$ binenv update helm
2021-09-27T14:31:40-07:00 INF retrieving distribution cache from https://raw.githubusercontent.com/devops-works/binenv/develop/distributions/cache.json
2021-09-27T14:31:40-07:00 INF fetched updates for 195 distributions

$ binenv versions helm
# Most recent first; legend: active, installed, available
helm:

Thanks for the report.
Seems that latest cache solves this. Do you confirm ?
(dups #156)

Problem with helm is fixed.
Though some other distributions have no versions:

awless
bat
fzf
github-release-notes
gitjacker
gosec
havener
helmfile
himalaya
k6
kcli
kubeconf
micro
peco
phpsecscan
procs
sshproxy
tf2pulumi
ytt

Let's move discussion to #156
Fell free to close this dup


Use of unresolved identifier 'FirebaseApp'

[REQUIRED] Step 1: Describe your environment
Xcode version: 11.5
Firebase SDK version: 6.28.1
Firebase Component: FirebaseApp config
Installation method: CocoaPods
[REQUIRED] Step 2: Describe the problem
Steps to reproduce:
Hi, I just update firebase v6.28.0 to v6.28.1, when update finish and build it said "Use of unresolved identifier 'FirebaseApp' ", and when I revert back to v6.28.0 it's normal. Do you know why ?

It has been resolved by import FirebaseCore.

Was literally having the same issue and scratching my head. Thanks @nguyencongthienvu

@nguyencongthienvu Thanks

Duplicate of #6066

Could you please update the documentation at https://firebase.google.com/docs/crashlytics/get-started?platform=ios because it says import Firebase which is misleading?

@stanfeldman import Firebase should still work and is supported. See the ongoing issue at #6066.

Could you please update the documentation at https://firebase.google.com/docs/crashlytics/get-started?platform=ios because it says import Firebase which is misleading?

Please update documentation Auth also has the same issue until you import FirebaseAuth and import FirebaseCore

Hi all. I'm still in trouble from last week. I have tried what sdnetwork specifies, and it only works at few times. It mainly fails when working with a physical device. With the simulator it compiles well.
Firebase installed pods:
pod 'Firebase/Analytics'
pod 'Firebase/DynamicLinks'
pod 'Firebase/Crashlytics'
pod 'Firebase/Messaging'
pod 'Firebase/RemoteConfig'
log from pod install:
Installing Firebase (6.28.1)
Installing FirebaseABTesting (4.0.0)
Installing FirebaseAnalytics (6.6.2)
Installing FirebaseCore (6.9.1)
Installing FirebaseCoreDiagnostics (1.5.0)
Installing FirebaseCrashlytics (4.3.0)
Installing FirebaseDynamicLinks (4.2.0)
Installing FirebaseInstallations (1.5.0)
Installing FirebaseInstanceID (4.5.0)
Installing FirebaseMessaging (4.6.0)
Installing FirebaseRemoteConfig (4.7.0)
XCode version: 11.6
physical device: iPhone 11 Pro iOS 13.6
CocoaPod version: 1.8.4
MacOS Catalina version: 10.15.6

@rastorgaespinoza for FirebaseApp use import FirebaseCore and I would assume for Messaging do import FirebaseMessaging

Just ran in to this issue myself when setting up Firebase Dynamic Links. It worked fine until I did a Clean Build Folder under Product tab in XCode...then for some reason I had to use FirebaseCore to initialize and then import FirebaseDynamicLinks for the Dynamic Links code. Anyone else have this type of scenario? I'd prefer to just import Firebase link the instructions say here: https://firebase.google.com/docs/ios/setup#analytics-enabled

no such module FirebaseCore

No such module 'FirebaseAuth'

See the resolution at https://github.com/firebase/firebase-ios-sdk/issues/6066#issuecomment-662580211. If that still doesn't work, we'll need a reproducible example to help with this issue.


Switches to stiches

Ditches Tailwind for Stitches. This will make the landing page easier and make it easier to use shared components from webapp if we ever do that. I also made some fixes to the changelog page so its styles are consistent with the rest of the docs pages and look ok in light mode.

Should this be merged into main? don't need a feature branch if this can be atomically merged

Should this be merged into main? don't need a feature branch if this can be atomically merged

agreed, and also git conflict so idk


ARD livestream broken

the ARD livestream doesn't work since some days. I found the new adress:
https://mcdn.daserste.de/daserste/de/master.m3u8
Please insert into zapp.
The zapp app is great. I use it via sideload on Amanzon fire stick. The best livestream app.

This issue will be fixed with version 2.2.1 which will hit FDroid in a few days. Thank you very mich for reporting!

That's strange! I have just deinstalled old ZAPP release and then installed new ZAPP from F-Droid. The problem still is the same. A some weeks old part of "Tagesschau" is playing around and round instead of seeing live program.
Perhaps it is better, to check this again?

@Ricolette256 I cannot reproduce this issue. Can you please check, which version of Zapp is installed on your device? 2.2.2 is the latest version right now.


The top N populated cities in a region where N is provided by the user.

Unable to complete due to project time constraints


Invalid launch parameter tests exceed spec requirements

The SMART Invalid Launch Parameter tests (6.4) require that a server fail to authorize a client which sends an invalid launch parameter. The SMART App Launch IG states that clients send back the same launch parameter they received from the server, but does not state any requirements for how the server handles an invalid or missing launch parameter.
See discussion on zulip.

@yunwwang @arscan
Hi,
We are currently using [v2.2.1] and this test case is failing for us. Is there an ETA or version number where this constraint will be removed? Thanks.


[TNT-41651] download property-specific artifact if a token is specified

Description
Prior to this change, the node SDK always downloaded the "global" rules.json file, so that it could answer calls for any property -- even if the SDK had been configured with a property token on init.  But this change makes it so the SDK downloads the property-specific artifact only if one is specified on init.  This helps for those with server-side constraints where large artifact sizes are not ideal.
Related Issue
https://jira.corp.adobe.com/browse/TNT-41651
How Has This Been Tested?
added a test case adds property token if provided
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[X] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[X] I have signed the Adobe Open Source CLA.
[X] My code follows the code style of this project.
[X] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[X] I have read the CONTRIBUTING document.
[X] I have added tests to cover my changes.
[X] All new and existing tests passed.

Coverage decreased (-0.003%) to 92.652% when pulling d6e690b79bd7c2598f1ad6d21612fc03c39c3287 on jasonwaters:property-specific-artifact into 0800a0594fd3328bce7a2b65f70d267736b7916d on adobe:main.


Global variable undefined when testing with Jest

This runs fine and my global config variable is defined when running outside of a test environment.
However, when I run this with vue-cli and jest unit testing (e.g. vue-cli-service test:unit), I get a
  ● Test suite failed to run

    ReferenceError: APP_CONFIG is not defined

// vue.config.js
...
 configureWebpack: {
    plugins: [
      new ConfigWebpackPlugin('APP_CONFIG')
    ]
  },
...

What is a good way around this? Is it because Jest starts executing the JS files before the node-config can finish switching out all global variables with their values?

I presume it's because Jest doesn't involve webpack when running tests. Webpack is the one that's injecting the config object into the code. To make it work in Jest, you'll have to configure a global with your config.
A known issue with Jest is that there's a lot of duplication between the Jest and Webpack configs.

Thanks, I tried setting globals in the Jest config but problem was the config was supposed to be dynamic (taking from test.json first, and then the rest from default.json). However, I suppose I can provide a complete copy of the test config. However, I think I may end up using option 1 here: github.com/lorenwest/node-config/wiki/Webpack-Usage

You would need to put the config object itself as a Jest global. node-config-webpack shouldn't play a role here. There's no reason it shouldn't pull from test.json if the environment is set correctly. Can you link a repo where you see this problem?


feat: add hydration to initial value hook

BREAKING CHANGE: adds Jotai hydration to the initial value hook which has potential side effects for existing forms

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

Comparison is base (c7d2751) 97.05% compared to head (aadca1f) 97.06%.
Report is 1 commits behind head on main.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #67      +/-   ##
==========================================
+ Coverage   97.05%   97.06%   +0.01%
==========================================
  Files           3        3
  Lines        2447     2456       +9
  Branches      253      255       +2
==========================================
+ Hits         2375     2384       +9
  Misses         72       72

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

can you revert to the equality checking introduced in https://github.com/form-atoms/form-atoms/commit/c7d2751d53da2eb3be616eb32f4b71a66592ab5a?
It causes this issue for me: https://github.com/form-atoms/field/issues/104
Why can't we rely on React's dependency tracking?

Using React dependency tracking doesn't work for objects/arrays

yeah the user needs to care about referential equality, but this is typical in React libraries.

If I reverted, you have a bug and you aren't aware of it. With the way things are now, you have a bug and you know it :)

If I reverted, you have a bug and you aren't aware of it. With the way things are now, you have a bug and you know it :)

I think I'm with @schiller-manuel on this one. E.g. the areEqual is basically second check for dirty (when field.value is compared).
I tried to wrap my head around implementation for the listField, but all ended up looking like trash

Not sure what the suggestion is. What good does reverting do?

@jaredLunde we just want to return to the original version, where the efeect hook uses depeneencies as it should...
No need for anything special for the listField here.
Whats the point of the areEqual? I believe it was added to fix the issue of set-in-render we had earlier and now is not needed as you merged the hydration which we originally wanted.
So like we need one step back on that front 😁

I'm not reverting the change. Outside of potential bug fixes this library is "done" at this point as the project goals have been achieved. areEqual solves an initial value case for something like below where you have a <textarea> that has email addresses separated by commas.
// Atoms
const sendInvitesFormStore = createStore();
const sendInvitesForm = formAtom({
  emails: fieldAtom<string[]>({
    value: [],
    validate: validate(
      z.array(z.string().email()).nonempty(
        "Must contain at least one email address.",
      ).max(25, "Must contain at most 25 email addresses"),
    ),
  }),
});

// Field
<Form.Field
  atom={fields.emails}
<EMAIL_ADDRESS>  render={(state, actions) => {
    return (
      <Input.DescriptiveLabel
        title="Email addresses"
        description={
          <>
            Send up to 25 invites at a time. Separate multiple email addresses
            with commas.
          </>
        }
      >
        <Textarea
          autoResize
          autoFocus
<EMAIL_ADDRESS><EMAIL_ADDRESS>          rows={4}
          value={state.value.join(", ")}
          onChange={(event) => {
            actions.setValue(
              event.currentTarget.value
                .split(/,\s+/g)
                .map((v) => v.trim()),
            );
          }}
        />
      </Input.DescriptiveLabel>
    );
  }}
/>

Again, this is an issue with your field, not the library. The library works as advertised.


.NET Framework SQLCLR support

This partially comes from the netfx/netcore project merge, but has opened into a more general question: is SqlClient's .NET Framebuild build supported for use in SQLCLR scenarios? My experience so far has been that it isn't working, but some review of the code suggests to me that it can't work.
Background context
I'm trying to test the context connection. When Context Connection is true, SqlClient starts to use a lot of the *Smi and Smi* classes which are in the .NET Framework project, plus various branches within other classes. My library is the foundation of a testbed to prove that the functionality works: first with .NET Framework's intrinsic System.Data.SqlClient, second with Microsoft.Data.SqlClient as-is, and third after any code merges.
System.Data.SqlClient
The sample library which I've used as a testbed is pretty simple. It contains one class, as below:
public class NetFxStoredProcedures
{
    [Microsoft.SqlServer.Server.SqlProcedure]
    public static void uspEcho(System.Data.SqlTypes.SqlString spToEcho)
    {
        var record = new Microsoft.SqlServer.Server.SqlDataRecord(
            new Microsoft.SqlServer.Server.SqlMetaData("Echo", System.Data.SqlDbType.NVarChar, 200)
        );

        record.SetSqlString(0, spToEcho);

        Microsoft.SqlServer.Server.SqlContext.Pipe.Send(record);
    }

    [Microsoft.SqlServer.Server.SqlProcedure]
    public static void uspPrintDate()
    {
        using (var cConn = new System.Data.SqlClient.SqlConnection("Context Connection=true"))
        {
            cConn.Open();

            var cmd = new System.Data.SqlClient.SqlCommand("select getdate() as MyDate", cConn);

            DateTime dt = (DateTime)cmd.ExecuteScalar();

            Microsoft.SqlServer.Server.SqlContext.Pipe.Send("The current date is: " + dt.ToString("O"));
        }
    }
}

I then load it into SQL Server with the script:
use [master]

create database SqlClrTestDb

alter database SqlClrTestDb
    set trustworthy on

go

use [SqlClrTestDb]

create assembly NetFx from '<path>\SqlClrTestbed.dll'
    with permission_set = unsafe
go

create procedure usp_NetFxEcho
    @spToEcho nvarchar(200)
as external name NetFx.[SqlClrTestbed.NetFxStoredProcedures].uspEcho
go

create procedure usp_NetFxPrint
as external name NetFx.[SqlClrTestbed.NetFxStoredProcedures].uspPrintDate
go

exec usp_NetFxEcho 'Hello, world!'
exec usp_NetFxPrint
go

drop procedure usp_NetFxEcho
drop procedure usp_NetFxPrint
drop assembly NetFx
go

use [master]
drop database SqlClrTestDb
go

This tests three situations:

SQL Server can load the DLL at all
uspEcho allows me to issue a result set back to the caller
uspPrintDate can make use of the Context Connection connection string parameter and run a query

It works as expected.
Microsoft.Data.SqlClient
Microsoft.Data.SqlClient has a few problems. I've adapted the class as below:
public class MdsStoredProcedures
{
    /*[Microsoft.SqlServer.Server.SqlProcedure]
    public static void uspEcho(System.Data.SqlTypes.SqlString spToEcho)
    {
        var record = new Microsoft.Data.SqlClient.Server.SqlDataRecord(
            new Microsoft.Data.SqlClient.Server.SqlMetaData("Echo", System.Data.SqlDbType.NVarChar, 200)
        );

        record.SetSqlString(0, spToEcho);

        Microsoft.SqlServer.Server.SqlContext.Pipe.Send(record);
    }*/

    [Microsoft.SqlServer.Server.SqlProcedure]
    public static void uspPrintDate()
    {
        using (var cConn = new Microsoft.Data.SqlClient.SqlConnection("Context Connection=true"))
        {
            cConn.Open();

            using (var cmd = new Microsoft.Data.SqlClient.SqlCommand("select getdate() as MyDate", cConn))
            {
                DateTime dt = (DateTime)cmd.ExecuteScalar();

                Microsoft.SqlServer.Server.SqlContext.Pipe.Send("The current date is: " + dt.ToString("O"));
            }
        }
    }
}

uspEcho is laid out as per the documentation here. The primary problem for this method is that there's no Microsoft.Data.SqlClient.Server.SqlContext class (or its supporting classes) and thus, no way to return result sets. I did try to use Microsoft.SqlServer.Server.SqlContext, but there's no type forwarding from Microsoft.SqlServer.Server.SqlDataRecord to Microsoft.Data.SqlClient.Server.SqlDataRecord. I commented it out to avoid the compilation error.
uspPrintDate was going to be a bit more important, since it exercises the context connection. This is almost identical to the System.Data.SqlClient classes, and it compiles - I don't think there's much to look at here.
Failure
Once compiled, I can't load the library which uses Microsoft.Data.SqlClient into SQL Server. I'm using this SQL script:
use [master]

create database SqlClrTestDb

alter database SqlClrTestDb
    set trustworthy on

go

use [SqlClrTestDb]

create assembly NetFx from '<path>\SqlClrTestbed.dll'
    with permission_set = unsafe
go

create procedure usp_MdsPrint
as external name NetFx.[SqlClrTestbed.MdsStoredProcedures].uspPrintDate
go

exec usp_MdsPrint
go

drop procedure usp_MdsPrint
drop assembly NetFx
go

use [master]
drop database SqlClrTestDb
go

This behaves unexpectedly; I'm unable to create the assembly as a result of SQL Server trying to load two versions of System.Runtime.CompilerServices.Unsafe. The output I receive is:
Warning: The Microsoft .NET Framework assembly 'system.numerics.vectors, version=<IP_ADDRESS>, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
Warning: The Microsoft .NET Framework assembly 'system.runtime.compilerservices.unsafe, version=<IP_ADDRESS>, culture=neutral, publickeytoken=b03f5f7f11d50a3a, processorarchitecture=msil.' you are registering is not fully tested in the SQL Server hosted environment and is not supported. In the future, if you upgrade or service this assembly or the .NET Framework, your CLR integration routine may stop working. Please refer SQL Server Books Online for more details.
Msg 10300, Level 16, State 1, Line 68
Assembly 'System.Memory' references assembly 'system.runtime.compilerservices.unsafe, version=<IP_ADDRESS>, culture=neutral, publickeytoken=b03f5f7f11d50a3a.', which is not present in the current database. SQL Server attempted to locate and automatically load the referenced assembly from the same location where referring assembly came from, but that operation has failed (reason: version, culture or public key mismatch). Please load the referenced assembly into the current database and retry your request.

Interestingly, this occurs even with a binding redirect in sqlservr.exe.config, excerpted below. I'm a little suspicious that SQL Server's assembly load rules might be ignoring this though.
<dependentAssembly>
  <assemblyIdentity name="System.Runtime.CompilerServices.Unsafe" publicKeyToken="b03f5f7f11d50a3a" culture="neutral" />
  <bindingRedirect oldVersion="<IP_ADDRESS>-<IP_ADDRESS>" newVersion="<IP_ADDRESS>" />
</dependentAssembly>

System.Runtime.CompilerServices.Unsafe v<IP_ADDRESS> corresponds to the NuGet package version 4.5.3. I'm not sure why it's binding to that version of the package - all of the direct and transitive dependencies require at least version <IP_ADDRESS>, and I've walked through the references of every built DLL and found no other version.
I located the v<IP_ADDRESS> System.Runtime.CompilerServices.Unsafe DLLs and tried adding them as assemblies manually, but SQL Server won't allow two versions of the same assembly to be loaded. I thus can't load my testbed DLL to check whether context connections work.
Speculative failure
I'm trying to test context connections because I'm not sure they can actually work. The core of the context connection logic comes from SmiContextFactory. In the constructor, we see the Microsoft.SqlServer.Server.InProcLink.Instance field is converted to a Microsoft.Data.SqlClient.Server.SmiLink object, then the result of SmiLink.GetCurrentContext is passed a Microsoft.Data.SqlClient.Server.SmiEventSink instance and its return value is converted to a Microsoft.Data.SqlClient.Server.SmiContext object. However, when I look at the SqlAccess assembly which is shipped as part of SQL Server, all of these types are in the Microsoft.SqlServer.Server namespace in System.Data; I think the type conversion will fail, leaving the connection unable to open.
Issue/question
I've raised this as an issue because adding Microsoft.Data.SqlClient to a clean .NET Framework project results in SQL Server being unable to load the resultant DLL. My broader question is whether SQLCLR usage is supported in SqlClient's .NET Framework build - both for context connections, and for returning result sets.
If M.D.S' .NET Framework build is supposed to support SQLCLR usage, does a working sample environment exist? I didn't see anything in the test projects. If it's not supposed to support SQLCLR, I'll close this issue with a couple of PRs to make sure that the Context Connection connection string parameter throws and to remove the underlying classes from the .NET Framework library.

is SqlClient's .NET Framework build supported for use in SQLCLR scenarios?

Not at this time.

If M.D.S' .NET Framework build is supposed to support SQLCLR usage, does a working sample environment exist? I didn't see anything in the test projects. If it's not supposed to support SQLCLR, I'll close this issue with a couple of PRs to make sure that the Context Connection connection string parameter throws and to remove the underlying classes from the .NET Framework library.

No, a working sample doesn't exist.
First, thanks for actually trying it out. I knew it wouldn't work, but I've never actually tried it to see what the errors look like.
While MDS in SQLCLR isn't supported at this time, there is the open question of whether it will be supported in the future. That question hasn't been answered. Since SDS feature development has stopped, it seems obvious that, just like every other product that has an SDS dependency, SQL will either need to move forward with SQLCLR support with MDS or deprecate SQLCLR. I imagine the answer will eventually be made based on customer demand. (Not my call.) In the meantime, we've tried to keep the SQLCLR-related code intact in the inherited netfx code in the hopes that it will make any future SQLCLR support decision easier to implement. So please leave the existing code there, for now.
David

Thanks @David-Engel - that makes sense.
I'm afraid I'm not able to test what the MDS context connections' errors would actually look like though - I can't get SQLCLR to load any DLL referencing MDS. I've been able to get further than before, but I quickly hit a roadblock which had the same effect. The details are at the end, but they're not all that relevant - "MDS isn't supported for use in SQLCLR environments" is clear enough. I wasn't able to find that in any documentation though, and the connection string doesn't throw. Could the MDS and the SQLCLR documentation be changed to make that clearer please?

Since SDS feature development has stopped, it seems obvious that, just like every other product that has an SDS dependency, SQL will either need to move forward with SQLCLR support with MDS or deprecate SQLCLR. I imagine the answer will eventually be made based on customer demand. (Not my call.)

To speculate here: I think deprecation's slightly more likely. Between SQL Server Language Extensions (for .NET Core integration and code execution) and the recent JSON support (potentially for data transport) it feels like SQL Server's headed in that direction. It'd be nice if there was more clarity on that though.

The original issue was essentially that SQL Server wouldn't allow two versions of the same assembly to be loaded, and wasn't respecting the binding rules in app.config. That description of behaviour is accurate - this blog post confirms that SQLCLR doesn't support using the app.config file to perform assembly redirection. Instead, the correct approach is to create the oldest required version of the assembly, then use ALTER ASSEMBLY multiple times to direct it to each newer version required.
I also need to load some of my SQLCLR testbed's dependencies into SQL Server manually via CREATE ASSEMBLY. This is because the DLLs don't pass SQL Server's verification process, so can't load automatically. Oddly enough, if they're loaded manually once and then their assembly is dropped, they'll load automatically following that. It's strange and would need to be fixed before MDS introduced SQLCLR support, but I was simply trying to shoehorn the assemblies in so that I could test the use of a context connection!
I loaded the assemblies below, in order:

DLL
Version
NuGet version
Path within package

System.Runtime
<IP_ADDRESS>
4.0.0
ref/dotnet

System.Runtime.CompilerServices.Unsafe
<IP_ADDRESS>
4.5.1
lib/netstandard2.0

System.Runtime.CompilerServices.Unsafe
<IP_ADDRESS>
4.5.2
lib/netstandard2.0

System.Runtime.Caching
<IP_ADDRESS>
(GAC)

System.Runtime.Serialization
<IP_ADDRESS>
(GAC)

System.Net.Http
<IP_ADDRESS>
(GAC)

System.Windows.Forms
<IP_ADDRESS>
(GAC)

System.Threading.Tasks
<IP_ADDRESS>
(GAC)

System.Collections
<IP_ADDRESS>
(GAC)

System.Threading.Tasks.Extensions
<IP_ADDRESS>
(GAC)

System.Runtime.CompilerServices.Unsafe
<IP_ADDRESS>
6.0.0
lib/net461

I wasn't able to load System.Runtime.CompilerServices.Unsafe <IP_ADDRESS>. When I tried to alter the assembly based on the file from lib/net461 in the NuGet package, I received the error:

ALTER ASSEMBLY failed because the referenced assemblies would change. The referenced assembly list must remain the same.

This is because earlier versions of the library referenced System.Runtime, while this one doesn't. When I tried to do the same thing based on the file from lib/netstandard2.0, I had to load the .NET Standard DLL first. Retrying the ALTER ASSEMBLY for System.Runtime.CompilerServices.Unsafe resulted in the same error: the referenced assemblies would change.
Wrapping that attempt up, I'm reasonably sure that there'll need to be changes to SQL Server simply to allow any assembly referencing MDS to be loaded, plus the ones you've mentioned to let context connections work. None of that's a SqlClient issue exactly; I just can't find a reference to the fact that it's unsupported in the documentation.

With the merge of #2862, the use of Context Connection=true in a connection string is blocked. While the .NET Framework build of Microsoft.Data.SqlClient could potentially work when run in a SQLCLR context, it doesn't support connections to the context connection.
I've got a set of PRs following this which will remove the now-unused set of classes. To track this:

[x] Prevent users from accessing Context Connection functionality: #2862
[ ] Remove SqlCommand code paths. Removes SqlDataReaderSmi, SqlClientWrapperSmiStream, SqlClientWrapperSmiStream, SqlClientWrapperSmiStreamChars, SqlSequentialTextReaderSmi, SqlSequentialStreamSmi
[ ] Remove SqlConnection code paths. Removes SqlInternalConnectionSmi, SmiLink, SmiContext, SmiRequestExecutor, SmiEventStream
[ ] Clean up references to SmiContextFactory. Removes SmiContextFactory, SmiStream, .NET Framework-only components of SmiXetterAccessMap, TriggerAction, SmiConnection
[ ] Modify ValueUtilsSmi et all, removing references to the rarely-referenced and now unused SmiEventSink type hierarchy
[ ] Remove SmiEventSink type hierarchy
[ ] Simplify the ITypedSetters, ITypedGetters and SmiRecordBuffer type hierarchies. Removes SmiRecordBuffer

I don't expect any of these besides #2862 to require public API surface changes. They'll all be quite large PRs though, so I might spread the changes out over more of them as makes sense over the coming months.

Hi @edwardneal

but some review of the code suggests to me that it can't work.

it can work - but with a completely different solution.
Short: Create a web service (use old asp, use wcf, use NET.8 minimal web api) that can talk via raw http, SOAP or POST + Xml or JSON.
Create a background procedure in NET.4.8 with a class that inherits System.Web.Services.Protocols.HttpGetClientProtocol (POST is included). This procedure talks with your web service.
Create some CLR-SP in NET.4.8, they send the data to that procedure.
So only DLL listet
https://learn.microsoft.com/en-us/sql/relational-databases/clr-integration/database-objects/supported-net-framework-libraries?view=sql-server-ver16
are used. System.Web.Services is supported. No additional dll must be loaded, only GAC dlls used.
--
I'm running an old application, startet 2006. Switched to a newer SQL server with CLR-integration. Loading additional assemblies is a terrible idea. Breaks updates / patches. So first I've started using NET.Remoting (loading assemblies unsafe). Later switched to that solution with wcf and a SOAP client.
Last year switched to a NET.8 service, connected from a small NET.4.8 client. The client creates a Xml-document, via POST, a different Xml-document is returned.

Thanks @JuergenAuer. The approach you're describing makes sense, and once a SQLCLR SP is running, as you've said, it can naturally POST to any HTTP endpoint - whether it's backed by .NET Framework, .NET Core, or any other runtime/language.
The problems that this issue relates to are twofold:

Microsoft.Data.SqlClient can't connect to a context connection
I can't figure out how to load assemblies referencing Microsoft.Data.SqlClient for SQLCLR purposes

The first problem is partially resolved by #2862: we're explicitly stating that SqlClient doesn't support context connections (and can't - SQL Server reflects into a type with the same name in System.Data.SqlClient.) The more complete resolution will come as progressively more of the never-functional SQLCLR infrastructure is removed.
I'm planning to re-run the tests in this issue at some point after the release of SqlClient v6.0. Its updated references might have fixed this problem.

Hi @edwardneal

I can't figure out how to load assemblies referencing Microsoft.Data.SqlClient for SQLCLR purposes

simple answer: Don't try it, forget it. I've used such things between 2008 and 2012. It's terrible, a database with tons of system-assemblies, every patch day trouble.
Then switched to the "small client", no single system assembly loaded. Now life is much easier. Using only the published list of supported DLL was an excellent decision.

@edwardneal I recently was trying to get a better understanding of how CER works and according to a stack overflow answer (https://stackoverflow.com/a/1348291) it was mostly added to our codebase to make it resilient when running as SQL CLR. ie, To prevent SQL Server from crashing when encountering stack overflows, out-of-memory, and thread aborted exceptions. I'm wondering, if we remove the SQL CLR code from the codebase, can we also remove the CER stuff? That'd be so pleasant 😌

I partially agree, I've had to deal with merging some of those and it was never easy to deal with.
In my opinion, it's actually a design question: should SqlClient try to be resilient to scenarios where some of the CLR's runtime environment has collapsed? roji and I had a conversation on that topic with respect to connection pooling in #2612. If we want to guarantee that we'll make a best-effort to close the connection in an orderly manner, the CERs need to stay in situ. If the view is that when the runtime collapses, we step into undefined behaviour and it's acceptable to give up, the CERs (and potentially the try-catches covering stack overflows, out of memory and thread abort exceptions) probably don't serve any purpose and can be removed.

I'm mostly of the opinion that if the CLR blows up, we're not on the hook to clean up after it blows up. But of course, that's just my opinion. If it were just closing a connection, then I wouldn't be concerned. But considering sessions may be riding on the connection, it implies data loss may occur if the connection isn't closed up neatly, for example.
I doubt my opinion alone carries enough weight to justify deleting the CER code. But I'd be very happy to do it if there is consensus to do so.


Cant find a release on a specific tracker

Hello,
i cant find Torrents from one of my trackers. Jackett works perfect, but cross-seed cant find the results, here is the Jackett Log:

2021-02-02 20:50:45
Info
Manual search in "TRACKERNAME" for "MOVIENAME" => Found 4 releases

2021-02-02 20:50:45
Info
Manual search in "TRACKERNAME" for bscdjpstabgdspjdasmomdsenqciadsnocdpsikncaodsnimcdqsanc => Found 0 releases

That gibberish search is intended. Can you try running cross-seed with verbose logging (-v)?

Im sry for my late response. I have cleared the cache with the "clear-cache" command and updatet Jackett. Everything is working fine now. Thank you!


chore: bdd-gh-1577537502 to 0.0.1

chore: Promote bdd-gh-1577537502 to version 0.0.1

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by:
To fully approve this pull request, please assign additional approvers.
We suggest the following additional approvers:
If they are not already assigned, you can assign the PR to them by writing /assign  in a comment when ready.
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


Question - Scoping Styles to Component

Hello hello!
The library seems great 😃and almost exactly perfectly fits my use case - however, my concern is that the styles are in no way scoped to the component, correct?
i.e I have 2 components built using this library (X and Y), and they co-exist on one page at render. Because they both inject a <style> tag into the DOM, the styles from X can affect the presentation of Y? If for example they both use <p> tags, and X includes styles along the lines of p { color: red }
Am I correct in this line of thinking?

Oh damn, I was for some reason not watching this repo and thus didn't see that issue :/
Still leaving an answer: Yeah, that's right. This library doesn't aim to solve class name conflicts and whatever. To achieve that, I'd actually recommend using a CSS in JS library.
You could also write a helper or sth. to generate unique class names for a given input if that helps.


Whitespaces in taxonomies

Describe the bug
Line 19 in partials/post/meta.html (https://github.com/razonyang/hugo-theme-bootstrap/blob/master/layouts/partials/post/meta.html) inserts whitespaces into taxonomies.

There are also whitspaces in the sidebar taxonomies.
Change Line 19 in partials/post/meta.html to:
{{- range $taxonomies -}}
and
Line 27 in partials/sidebar/taxonomies.html:
{{- if and (lt $count $taxonomyCount) (ne .Name "") -}}
Expected behavior
No whitespaces

BTW, It should have no side effect on production mode with hugo --minify.


Add support for Python < 3.8

This PR adds support for Python < 3.8.
The motivation behind this PR is that I wanted to check the module on Google Colab, but since it (surprisingly) still runs Python 3.7, the typing.TypedDict import was failing. This type was introduced in Python 3.8.
Fortunately or unfortunately, the reality is that a lot of people use Colab, so making the module work on it will probably be helpful for the project.
The fix is based on https://github.com/python/typeshed/issues/3500#issuecomment-560958608.

Thanks for your contribution, sorry for not noticing earlier!


fixed typo (public PR only due to repo access)

fixed typo

@MarileeTurscak-MSFT : Thanks for your contribution! The author(s) have been notified to review your proposed change.


Websocket threading implementation query?

Just a quick question, is the ES architecture that each web-socket subscription is effectively running in its own thread? I know the code is heavily async/await based but what I'm wondering about is reentrancy. If I have callbacks set on 3 different web-sockets, can all be called at once, or are all updates placed on some internal queue? Or, could a single callback be called multiple times at once e.g. does my callback block the next message on this channel or is each message going to call into my callback even if it's already running?

I didn't write the internals, but from what I can gather, all updates are placed in an internal queue. The callbacks block the next message so they are executed sequentially. You can override that behavior in your own code if you'd like.

This would make sense. I might try examining the call-stack but I'm working on Mac and their version of Visual Studio leaves quite a lot to be desired.

Web socket is a serial queue for callbacks and sent messages


chore: update VHD size of 23H2 back to 35GB

What type of PR is this?
/kind feature

What this PR does / why we need it:
update VHD size of 23H2 back to 35GB.
Which issue(s) this PR fixes:

Fixes #
Requirements:

[x] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[ ] tested upgrade from previous version

Special notes for your reviewer:
Release note:
none

Pull Request Test Coverage Report for Build<PHONE_NUMBER>2
Details

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 71.271%

Totals

Change from base Build<PHONE_NUMBER>5:
0.0%

Covered Lines:
2590

Relevant Lines:
3634

💛  - Coveralls


[scintilla] update to 4.4.6

Library name: scintilla
New version number: 4.4.6
Other information that may be useful (release notes, etc...)

Home Page
Version 4.4.6 fixes building with Xcode 12 #2187
Download Site

Please could we add the changes in PR [scintilla] Update include files path #15129 also, to put the include files in its own include/scintilla since this port's includes conflict with port tesseract include?

Hi @StarGate-One ,As you said I Update include files path


Invalid character recognition on 1bpp images

Hi,
This mostly happens on binary image snippet, It seems that the image padding is not managed.
In function TransferDataFormat1bppIndexed defined in BitmapToPixConverter.cs, line 98, the with is computed as imgData.Width / 8.
If the image width is mot a multiple of 8 some bits are missing.
This could be workaround by passing 8bpp images.
Thanks a lot,
Arnaud

Thanks I'll have a look at this over the next couple days hopefully.


Unable to cancel characteristic write operations

To help us fix your issue, please provide the information in the below template. If something causes a crash, provide as much information as you can gather.
Just imagine: we do not know what you are doing!

Note: There is often little we can do without a minimal reproducible sample of the issue, so please provide that in a standalone git repository and link it here.

Unable to cancel long running write operations. Cancellation tokens are declared as input parameters for WriteAsync method in Plugin.BLE.Abstractions/CharacteristicBase.cs, but do not work in practice (and don't appear to be passed along to native write invocations)
        using (var cts = CancellationTokenSource.CreateLinkedTokenSource(cancellationToken))
        {
            var combinedToken = cts.Token;

            try
            {
                var writeTimeoutSpan = TimeSpan.FromSeconds(5.0);
                cts.CancelAfter(writeTimeoutSpan);

                combinedToken.Register(() =>
                {
                    _commandStatus = CommandStatus.TCMD_TIMEOUT;
                    _asyncAutoResetEvent.Set();
                }, false);

                while (size > 20)
                {
                    Array.Copy(writeBuffer, writeBuffer.Length - size, chunk, 0, 20);

                    combinedToken.ThrowIfCancellationRequested();

                    var written = await _txCharacteristic.WriteAsync(chunk, combinedToken).ConfigureAwait(false);

                    if (!written)
                       throw new DeviceException(Name, $"Failed to write data for message: {messageType}");

                    size -= 20;
                }

                var lastChunk = new byte[size];
                Array.Copy(writeBuffer, writeBuffer.Length - size, lastChunk, 0, size);

                combinedToken.ThrowIfCancellationRequested();

                var written2 = await _txCharacteristic.WriteAsync(lastChunk, combinedToken).ConfigureAwait(false);

                if (!written2)
                    throw new DeviceException(Name, $"Failed to write data for message: {messageType}");
            }
            catch (Exception exception)
            {
                _logger.Error(exception, "Write error");

                cts.Cancel();
            }
        }

I have seen in practice (e.g. once every 24 hours) writes to this characteristic (has a Default WriteType) take 5+ MINUTES to complete. It nominally takes < 200ms. I am unable to cancel the outlier writes cleanly which are hung up in the WriteAsync implementation. I have not yet resorted to a brute force thread abort approach for fear of destabilizing the BLE stack. At this point I've just resorted to registering an Action on the cancellation token's timeout to keep the app happy; however, the thread with the write request lives on and can (eventually) complete the write. This situation has bad implications.
Steps to reproduce

Pass in a cancelled token to Characteristic.WriteAsync

Expected behavior
WriteAsync method (and ReadAsync) methods that accept a CancellationToken should throw a System.Threading.Tasks.TaskCanceledException exception when the token is cancelled.
Actual behavior
CancellationToken is ignored
Crashlog
If something causes an exception paste full stack trace + Exception here
Configuration
Version of the Plugin: 1.3.0 stable
Platform: e.g. Android 6.0.1
Device: e.g. Google Nexus 5

Hi @rtompot,
I'm the friendly issue checker.
Thanks for using the issue template :star2:
I appreciate it very much. I'm sure, the maintainers of this repository will answer, soon.


Unexpected newlines before and after interpolated value in Ractive.js v0.8.0-edge

Description of the bug::
Edge is adding unexpected newlines where 0.7.3 did not.  I've linked to an example run two ways (with 0.7.3 and with Edge) to show the change in behavior.
Versions affected:
Ractive.js v0.8.0-edge
Sat Apr 02 2016 22:38:06 GMT+0000 (UTC) - commit 9b0c45d6fce87b096196d37a489feb00fee63411
Platforms affected:
Chrome Version 49.0.2623.110 m on Windows 10
also on MS Edge and IE11 on Windows 10
Reproduction:
RactiveJS 0.7.3 (no unexpected newlines in style section of template)
http://jsfiddle.net/5n85mkds/

RactiveJS Edge (unexpected newlines after font-size: and the interpolated value for {{size}} (= 36) in the style section of the template)
http://jsfiddle.net/8h8a3y94/

Code:
HTML

JavaScript
var ractive = new Ractive({
    el: 'main',
    template: '
hello
',
    data: {
        size: 36
    }
});

It looks like Ractive isn't actually adding newlines. I'm guessing since each text segment and interpolator gets its own DOM node, the various inspectors show them on separate lines.
Is this causing issues somewhere? I don't think it would, but if it is, we can add a special element handler for style tags that sets innerHTML/cssText/whatever when rendering instead of just letting the normal element render process handle it.

I have a much more complex case where it might be causing an issue.  Something changed from 0.7.3 to edge and this is what I first noticed as a difference in generated DOM.  I will keep investigating.
How easy would is it to add a special element handler?
Also, is it "unusual" to have sequential Text nodes like that, rather than coalescing the text content into one node?

In RactiveJS 0.7.3, the


Final commit with all the files added , hopefullt didn't miss anything.

Description 📜
I have added my project which is a newsletter signup page, fully functional, deployed and responsive.
Fixes #41

Type of change 📝
Please delete options that are not relevant.And in order to tick the check box just but x inside them for example [x] like this

[x] Add a new project

Domain of Contribution 📊
Please delete options that are not relevant.And in order to tick the check box just but x inside them for example [x] like this

[x] Project using only HTML & CSS
[x] Project using HTML, CSS & JS

Checklist ✅
Please delete options that are not relevant.And in order to tick the check box just but x inside them for example [x] like this

[x] I have performed a self-review of my own code or work.
[x] I have commented my code, particularly in hard-to-understand areas.
[x] My changes generates no new warnings.
[x] I'm GSSoC'22 contributor

Screenshots / Gif (Optional) 📸
Add the screenshot of the changes you have made

@meinhoonharsh please review this and let me know the changes.

@meinhoonharsh i have asked @khushi-purwar whether I can do it or not, she said I can as it is deployed one can see the final project too. Since she allowed it, i coded it.

@meinhoonharsh ????

@khushi-purwar Please Look into it

@khushi-purwar can you please look into it??

@khushi-purwar Please update what else is needed to be done.
@meinhoonharsh


Split steps.lua

Split the generated steps into multiple files
This has 2 advantages:
Performance: It could make generation of the step files faster, if we only need to generate the last fraction of the steps.
Debugger: At least in my setup, the Factorio mod debugger has trouble with Lua files in excess of 10k lines.
This idea is fairly simple, though implementation could still be a bit tricky.
I am imaginen having 1 steps.lua file, this file then have references to several files with the actual steps.
We would split these lesser steps files with about 5k steps in each.
The Lua generator, would have to keep a state of which files have to be updated.

I am not entirely sold on the idea of introducing this type of complexity unless there is a very tangible benefit to doing it. Have you investigated what causes the debugger to have problems when the file is larger than 10k steps - does it need to keep track of all the steps?

I have received confirmation that it is in fact a bug in the debugger, that it can't handle large files.
I think there is still value in a faster script generation step. Whether it is enough value for the trouble, perhaps not.

Have the generation time degregated? When I last generated the script for my run it was so fast it almost didn't make sense to show the progress bar.

FWIW, my script with ~30k tasks takes about 2 seconds to generate. Because it is not clear when the generation is finished this sometimes means I launch from the save point before generation is finished and so I get the "old" version of the script playing instead of new, which is confusing as it's not clear if the change I made had no effect or if the change didn't happen at all.

Aren't there being shown a progress bar when you generate the script?
I don't remember it as taking anywhere near that amount for my run which was more than 30k if I remember correctly. This could be due to hardware, but the tool isn't multi-threaded so it shouldn't be possible for it to be crazy much faster on high- vs low-end gear.

Yes I have the progress bar which appears in a new window that is underneath the main window, so I don't get to see it

Why have you dragged the progress bar where you cannot see it? 😅
It would be pretty neat if the progress bar was integrated in the main window. I am though not aware if the framework supports it.

I see, that way "goes underneath". 🙂

Keep in mind that Zaspar usually streams his development, which steals significant resources too.
It should be possible to integrate the progress bar on the main window, using basically the same elements. Though that should probably be raised as it's own issue.

Ahh Yeah, that could cause performance issues of there isn't a thread available. I would though guess the vast majority of the load from streaming would be taken by the GPU, but none the less it could be the reason.
Agreed.


Announcement: RealSense SDK version 2.38.1 now available

Hi everyone,
Version 2.38.1 of the RealSense SDK is now available from the link below.
https://github.com/IntelRealSense/librealsense/releases/tag/v2.38.1
The full details of API and SDK changes can be read at the links below.
API
https://github.com/IntelRealSense/librealsense/wiki/API-Changes#version-2381
SDK
https://github.com/IntelRealSense/librealsense/wiki/Release-Notes#release-2381

unfortunately，THE Link"https://github.com/IntelRealSense/librealsense/releases/tag/v2.38.1 " is 404 error. Please update it.

Great news, I like the fixes for l515. Still the lack of support for t265 on Android is quite a pain for me and my project. Anyways keep up the good work. I'd really like to use Android because of better 3d engines support than other arm Linux distros, and native vr support.

Thanks so much for the feedback @TheBricktop    :)

When will the LabVIEW examples support L515 devices？My projects urgently need it

Hi  @huoxinr1998  Can you create a new case to ask this question in please by visiting the front page of this GitHub forum at the link below and clicking the New Issue button.  This will bring it to the attention of RealSense team members who handle L515 questions.   Thanks!
https://github.com/IntelRealSense/librealsense/issues

Thank you! I can now use the 515 in Unity.  I can use a 435, 455, and 515 at the same time(!)  there seems to be an issue with mixing up rgb streams, if i cant figure it out, ill make a test case.

Great to hear @chrisrogers3d  - if you do find that you need assistance, feel free to create a case on the forum to ask about it. Thanks!

I don't know if this is the proper place to address this issue but ive asked in other places and didnt hear any answear and this is pretty vital for my project:
There is a merge request for changes that enable t265 support on android but they are stalling on review  could anyone with proper authority look on it and tell us if this is viable for merging or not and why? @MartyG-RealSense  @smartynenko  @dorodnic
Enable android support for t265 #6011

@TheBricktop   I'm not involved in T265 related issues as other Intel RealSense team members are responsible for that camera.

@MartyG-RealSense sorry for asking i was thinking that You might have some informations about it.  There was no direct answer  about the status of android support for t265, neither about the stalled merge request in #6011. I hope it is not because some NDA or other legal issues.

@TheBricktop   I will refer your question to @RealSenseSupport for a response.

Thank You @MartyG-RealSense .


My thoughts about StatusLine(NC)? group, change the background

I think background of the status line should be darker and its foreground should be gray like this. What do you think about that? It's still okay if you don't think it's good. I also wanted to ask what is the reason behind making all background color bright. I don't know if it's just me but currently it doesn't look good. This is just a feedback.

highlight! StatusLine guibg=#818596 guifg=#1e2132
highlight! StatusLineNC guibg=#3e445e guifg=#1e2132

Thank you for the feedback! I'm considering about visibility of an edge between vertically-split windows and carefully picked these colors. For example:
darker:

current:

I think in my version it's still obvious which pane is active. After then that, do I really need a more obvious indicator which pane is really active. It's rather distracting.  Again, that's my opinion. I think your project is awesome, there are some of the details I don't like, I already did override them for my likings.

I partially agree with you, but at least for now I still feel the current version is good. Maybe it is important for me to recognize edges of windows clearly because I use Vim with heavily-split windows.

There are as many color preferences as there are people. Satisfying everyone with single color scheme is impossible. You can fork the repository or modify the coloration as you did.

Thanks for you kind answers. I also partially agree with you. I don't use splits as much as you do, so it's rather pointless for me to make that bright. But in the screenshots, I see clearly why you choosed that way. I'm closing the issue, thanks again!


Aggregation Extension

Related Issue(s):

#567

Description:
Adds base support for the STAC API Aggregation Extension
PR Checklist:

[ x ] pre-commit hooks pass locally
[ x ] Tests pass (run make test)
[ ] Documentation has been updated to reflect changes, if applicable, and docs build successfully (run make docs)
[ ] Changes are added to the CHANGELOG.

That's great to see movement in that direction! I have some questions/comments.

AggregationExtensionPostRequest is defined but not used.
Is it meant to be used with the filter extension or solely with the search API?
Are there any changes that need to be made in stac-fastapi-pgstac to make it compatible with that backend?

Thanks in advance.

Thank you for the comments @drnextgis

AggregationExtensionPostRequest is defined but not used.

Ah, yes. The aggregation extension spec defines the methods for /aggregate and /aggregation should be get or post. I will add post to the available methods.

Is it meant to be used with the filter extension or solely with the search API?

The aggregation extension spec as-is relies only on the core item-search afaik. However, the one implementation in stac-server includes cql2 query parameter, meaning it relies on the  Filter extension. So perhaps there are some updates needed in the Aggregation extension spec.

Are there any changes that need to be made in stac-fastapi-pgstac or in pgstac to make it compatible with that backend?

I am working on an implementation for elasticsearch and opensearch I am not sure how an implementation would be handled in pgstac.

Hey @philvarner let me know what you think of the changes to this PR. I think it is close to being complete.

Need to resolve conflicts too

Linting

Linting

@jonhealy1 Sorry, fixed

@vincentsarago Hi Vincent. How does this look now?

Great work @jamesfisher-gis


Pass metadata along with stream creation command

In our program different streams should be handled differently in a non-deterministic way. To determine how exactly each stream should be handled we're passing metadata along with it's creation command. I believe others too can benefit from such feature and it's optional and don't break API.

Codecov Report

Merging #46 into master will decrease coverage by 0.59%.
The diff coverage is 70%.

@@           Coverage Diff            @@
##           master     #46     +/-   ##
========================================
- Coverage    87.5%   86.9%   -0.6%
========================================
  Files           4       4
  Lines         392     397      +5
========================================
+ Hits          343     345      +2
- Misses         44      47      +3
  Partials        5       5

Impacted Files
Coverage Δ

stream.go
81.87% <50%> (-1.69%)
:arrow_down:

session.go
89.26% <83.33%> (+0.1%)
:arrow_up:

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 f4f6ca3...143fe60. Read the comment docs.

why not just send metadata as the first few bytes？

that would be a separate packet then, which requires handling in case of error, etc. in this case you 100% have metadata once stream is open which quite simplifies code.

@xtaci can you please look at this again?

@xtaci can you please look at this again?
as I said before,  you can just just send metadata as the first few bytes of the streams.


Events not always shown in correct order

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
When having multiple calendars, if the page is refreshed the ordering appears to change / be incorrect.
for example. I set a limit of 4 events, I have the following events in one calendar:
04 - event
04 - Night routine
05 - night routine
06 - night routine
in the 2nd calendar there is an event:
12 - reservation
the reservation should not be shown, the first 4 events should be shown only. however sometimes if the card is reloaded the 06 - night routine is swapped with the 12 - Reservation
Expected behaviour
card should show the following events:
04 - event
04 - Night routine
05 - night routine
06 - night routine
Steps To Reproduce

Use the configuration
refresh the page multiple times
events will change on the last day

Card Version
7.0.0-b3
Home Assistant Version
2022.3.8
Configuration
firstDayOfWeek: 1
maxDaysToShow: 14
maxEventCount: 4
showLoader: true
showDeclined: true
showDate: true
sortByStartTime: false
showLocation: true
hideDuplicates: true
showCurrentEventLine: false
showMonth: false
showDescription: false
dayWrapperLineColor: gray
eventBarColor: gray
locationLinkColor: gray
locationTextSize: 85
showWeekDay: true
disableEventLink: false
showNoEventsForToday: false
showEventIcon: true
showFullDayProgress: true
showHiddenText: false
calShowDescription: true
showLastCalendarWeek: false
dateFormat: LL
hideFinishedEvents: true
showProgressBar: true
refreshInterval: 300
name: Kalender
showRelativeTime: false
cardHeight: 100%

Relevant log output
N/A

Code of Conduct

[X] I agree to follow this project's Code of Conduct

I think I have the same problem. If you remove the maxEventCount setting, does the order behave as expected?
I think it has to do with the way it's sorting recurring events when using that setting. Maybe it's sorting by the first ever occurrence and not the next upcoming one.

After doing some more testing, I'm pretty sure I disproved my theory. I might have a different issue altogether. I'll make a separate issue for it, if it hasn't already been reported.

Same probleme here.  removing maxEventCount seem fixing the issue.  but creating mess in my dashboard by creating to big list ;)


Closes issue 8275

Dynamically resizes the "Got it" button to fit whatever text is put
inside it (up to a point).

Ready for review

@patricknaughton01 thanks for working on this.    It also looks like the hotspot in English looks quite different from the original.
Read about how to use Git rebase properly on our GitHub guide for more details.
I'm closing this PR; submit a new one if you end up fixing this issue properly.


Add job scheduler plugin to test cluster

Description
Add job scheduler plugin to test cluster, to work with gradlew run and debug mode
Test
Before:
> Task :opensearch-sql-plugin:run FAILED
Exec output and error:
| Output for ./bin/opensearch-plugin:-> Installing file:/local/home/clingzhi/workplace/sql/plugin/build/distributions/opensearch-sql-<IP_ADDRESS>-SNAPSHOT.zip
| -> Downloading file:/local/home/clingzhi/workplace/sql/plugin/build/distributions/opensearch-sql-<IP_ADDRESS>-SNAPSHOT.zip
| -> Failed installing file:/local/home/clingzhi/workplace/sql/plugin/build/distributions/opensearch-sql-<IP_ADDRESS>-SNAPSHOT.zip
| -> Rolling back file:/local/home/clingzhi/workplace/sql/plugin/build/distributions/opensearch-sql-<IP_ADDRESS>-SNAPSHOT.zip
| -> Rolled back file:/local/home/clingzhi/workplace/sql/plugin/build/distributions/opensearch-sql-<IP_ADDRESS>-SNAPSHOT.zip
| Exception in thread "main" java.lang.IllegalArgumentException: Missing plugin [opensearch-job-scheduler], dependency of [opensearch-sql]
|       at org.opensearch.plugins.PluginsService.addSortedBundle(PluginsService.java:527)
|       at org.opensearch.plugins.PluginsService.sortBundles(PluginsService.java:495)
|       at org.opensearch.plugins.InstallPluginCommand.jarHellCheck(InstallPluginCommand.java:855)
|       at org.opensearch.plugins.InstallPluginCommand.loadPluginInfo(InstallPluginCommand.java:829)
|       at org.opensearch.plugins.InstallPluginCommand.installPlugin(InstallPluginCommand.java:874)
|       at org.opensearch.plugins.InstallPluginCommand.execute(InstallPluginCommand.java:276)
|       at org.opensearch.plugins.InstallPluginCommand.execute(InstallPluginCommand.java:250)
|       at org.opensearch.cli.EnvironmentAwareCommand.execute(EnvironmentAwareCommand.java:104)
|       at org.opensearch.cli.Command.mainWithoutErrorHandling(Command.java:138)
|       at org.opensearch.cli.MultiCommand.execute(MultiCommand.java:104)
|       at org.opensearch.cli.Command.mainWithoutErrorHandling(Command.java:138)
|       at org.opensearch.cli.Command.main(Command.java:101)
|       at org.opensearch.plugins.PluginCli.main(PluginCli.java:66)

FAILURE: Build failed with an exception.

After:
...
[2024-08-30T14:00:38,537][INFO ][o.o.j.JobSchedulerPlugin ] [integTest-0] Loaded scheduler extension: async-query-scheduler, index: .async-query-scheduler
...
[2024-08-30T14:00:38,546][INFO ][o.o.p.PluginsService     ] [integTest-0] loaded plugin [opensearch-job-scheduler]
[2024-08-30T14:00:38,546][INFO ][o.o.p.PluginsService     ] [integTest-0] loaded plugin [opensearch-sql]...
...

[2024-08-30T14:00:42,788][INFO ][o.o.g.GatewayService     ] [integTest-0] recovered [0] indices into cluster_state
[2024-08-30T14:00:43,181][DEBUG][o.o.c.c.ElectionSchedulerFactory] [integTest-0] scheduleNextElection{gracePeriod=500ms, thisAttempt=1, maxDelayMillis=200, delayMillis=532, ElectionScheduler{attempt=2, ElectionSchedulerFactory{initialTimeout=100ms, backoffTime=100ms, maxTimeout=10s}}} not starting election
[2024-08-30T14:05:42,561][INFO ][o.o.j.s.JobSweeper       ] [integTest-0] Running full sweep
[2024-08-30T14:10:42,562][INFO ][o.o.j.s.JobSweeper       ] [integTest-0] Running full sweep
<============-> 98% EXECUTING [10m 17s]
> :opensearch-sql-plugin:run

Check List

[x] New functionality includes testing.
[x] Commits are signed per the DCO using --signoff.

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.
For more information on following Developer Certificate of Origin and signing off your commits, please check here.

Are grammar files changes needed?

Are grammar files changes needed?

I think these are auto included by syncing from spark repo


Ac read docs

various documentation changes and removal of requirements.py file.

@AndreasHeger  could you please review before merging please.


Placeholder Text for Cancellation

So we post this message and hide all the other pages by comment out the links?

I can comment out the links for the header bar, we can also make them not accessible. I'm not sure what we want to preserve and what we want to change, but (for instance) I can make the button on the front page ("Join us at SLDS 2020") unclickable.

I want to preserve the content.


Rancher Machine Rename

Remove shim machine-pacakge repo and rename docker-machine to rancher-machine.

machine
https://github.com/rancher/machine/pull/51
https://github.com/rancher/machine/pull/52
https://github.com/rancher/machine/pull/53
and
rancher
https://github.com/rancher/rancher/pull/24161

@izaac  As part of validating this issue , we need to make sure that all driver machine works as expected when provisioning nodes from all the supported node drivers:
Amazon EC2
Azure
Digital Ocean
Linode
Vsphere

Could this other GKE issue be related to this renaming? https://github.com/rancher/rancher/issues/24218 @luthermonson

@izaac not related and i do see you closed out that other issue. just thought i'd respond :)

Tested with Rancher version "2.4 master-head (11/25/2019) addeb8399"
Clusters created (and also removed) for:

Amazon EC2
Azure
Digital Ocean
Linode
vSphere

vSphere cluster:

The others:

@luthermonson as per our conversation, please check if this coverage is enough to QA all the changes made in the renaming. If this is good we can close the issue.

@izaac legit, this makes me happy to see. thanks!

@izaac back ported this issue, will put it back to test when it's merged: https://github.com/rancher/rancher/pull/24618

Version bump and rancher-machine rename in 2.3 now. Please run cluster creation automation against release/v2.3 and let's see how this goes.

Tested with Rancher version 2.3-head d73dff8df
Clusters created (and also removed) for:

Amazon EC2 (Automation)
Azure (Automation)
Digital Ocean (Automation/Manual)
Linode (Manual)
vSphere (Manual)

I've notice an issue but I logged it separately https://github.com/rancher/rancher/issues/24695 @luthermonson
Closing.


New Badge

Is it possible to integrate this badge from commits-top-badge to this project?
![commits.top ranking](http://biego.tech/commits?user=fbiego&country=kenya&bg_color=333333&text_color=77fe89&border_color=89452e)

@fbiego I'm not sure which of the options below you meant:

mention the above markdown as an alternative in the generated site
actually generate the badge itself via the CF Worker

If it's option 1, I'm not averse to linking to a landing page on your site which allows a user to build the badge.
If it's option 2, I think I like the current badge a bit more, yours feels too big. I'm not averse to loading it if given a variant=XXX query string and from the above URL, but I'm not sure about the uptime of your site (btw, why isn't the URL HTTPS?) as compared to shields.io. I'd have preferred to generate the SVG directly from the worker, but I wasn't sure about the widths etc and just pushed the problem elsewhere :slightly_smiling_face:

Please re-open if you can respond to the above comment, as I'm not sure what needs to happen here


shadowenv: 1.2.1 -> 1.3.1

Minor upstream changes, pretty much just adds a flag to shadowenv exec.

@GrahamcOfBorg build shadowenv

Thank you!


idprovider

Hello,
Great tutorial. I have the question about idprovider in
Credentials GetCredentials(String idprovider, String id) { }
What should it be?
Thank you,
Serge

Found the answer
    String result = cognitoHelper.ValidateUser("user", "XXXXX");
    if (result != null) {
        System.out.println("User is authenticated:" + result);
        JSONObject payload = CognitoJWTParser.getPayload(result);
        String provider = payload.get("iss").toString().replace("https://", "");

        Credentials credentails = cognitoHelper.GetCredentials(provider, result);

        System.out.println(credentails);
    }

Good to hear that you are enjoying the samples!


Getting started README Fix

Fixed #159
Error when trying Getting Started command cargo run --bin hello_world

Hi @edgarriba, CI have 2 failures

Error: buildx failed with: ERROR: failed to solve: process "/bin/sh -c cargo build --release"
error[E0599]: no variant or associated item named Bfloat16found for enumTensorElementType in the current scope

Is this a known issue? I have only Updated readme. Is there anything required from my end to fix this ?

@jeffin07 yep, not sure what is it but defenitely something is trying to pull ort-2.0.0-rc8 which seems to be broken. The only place this should happen is here https://github.com/kornia/kornia-rs/blob/main/examples/onnx/Cargo.toml#L18 and as you see the version doesn't match at all.

In any case, we can merge this PR -- and investigate what's causing the other failure.


SHR (not an issue)

Hi @007revad,
Thanks for providing these scripts. Much appreciated.
I am currently using a RAID1 configuration but plan to add additional drives so your script allows me to consider migrating to RAID5 or SHR.
How dows this work? I mean, I am not an expert user but Synology does not allow to move from RAID to SHR, so was wondering which kind of sorcery :-) are you using, and which will be the process.
Thanks in advance for your help and support.

The script doesn't allow changing an existing RAID 5 storage pool to SHR, or vice versa. It only enables the option to create an SHR storage pool on enterprise models that don't have SHR.

Oh, I see.
Thanks for clarifying.
On Sat, Jun 1, 2024 at 11:02 PM Dave Russell @.***>
wrote:

The script doesn't allow changing an existing RAID 5 storage pool to SHR,
or vice versa. It only enables the option to create an SHR storage pool on
enterprise models that don't have SHR.
—
Reply to this email directly, view it on GitHub
https://github.com/007revad/Synology_SHR_switch/issues/51#issuecomment-2143588670,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ALKMG4QEJR7Q5TGI4JPIE2DZFIZGPAVCNFSM6AAAAABIUI2E5CVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNBTGU4DQNRXGA
.
You are receiving this because you authored the thread.Message ID:
@.***>


Only create redirect URLs for older versions

We create redirect urls for each page in the docs because we've changed what docs are on the site and where. This way old URLs that persist in Google searches will still take the user to the correct spot.
We were generating this URL based on all versions of Electron listed in the _config but the old urls only exist for versions prior to 1.0.
This PR updates the script so that we're only creating redirect URLs for versions prior to 1.0.
You can see the result of this change in the new docs PR #302.
/cc @kevinsawicki

Looks good 👍


Chore: UX improvements for arguments passing

[ ] Add "?" button into the input field (position it to the right). Clicking the button will show a tooltip or a popup with info how to use the arguments, similar to the #38 PR description. Make sure it works on mobile
[ ] Remove the :focus shadow in the input element, we don't use shadows in this app. Flashing cursor is IMO enough to signal to the user they are inside the input and can start typing

I'm on it !


Bigfoot browser compatibility - Internet Explorer

It looks like bigfoot is not working in internet explorer 8.0 in my application . So up to which version of internet explorer would Bigfoot support ?

Haven't tested thoroughly, but my guess would be IE9+ since IE9 adds support for transforms.


Cesium.DefaultProxy always appends ?url-to-fetch to the request

The Cesium.DefaultProxy always appends ?url-to-fetch to
the request which makes it harder for other
proxy implementations which perhaps expect a
/proxy?get_url=url-to-fetch parameter
So my wish is to have something like:
var provider = new WebMapServiceImageryProvider({
url: 'http://sampleserver1/WMSServer',
layers : '0',
proxy: new Cesium.DefaultProxy('/proxy/?url=') /* dont just append
?url to that proxyurl */
});

good job!


ModNMask constants should match up to modN options passed to the client

Running berryc resize_mask "shift|mod4" does not work. When pressing Super+Shift and moving the mouse, nothing happens. However, running berryc resize_mask "shift|mod5" does allow Super+Shift to resize the mouse when dragging. This is because in client.c, the options mod1 and mod2 are mapped both to Mod1Mask and subsequent options are all also off by one (thus mod3 maps to Mod2Mask, mod4 maps to Mod3Mask, etc). This patch fixes that.

Good catch and thanks for this. Technically speaking this is a "breaking" change, so I'll be sure to add it to the changelog when I go to release.