imgproxy: 3.13.0 -> 3.13.1

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/imgproxy/imgproxy/releases.
meta.description for imgproxy is: Fast and secure on-the-fly image processing server written in Go
meta.homepage for imgproxy is: https://imgproxy.net
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 3.13.1 with grep in /nix/store/r9n1bzy0bbwxg1d312khhf9iblafy46d-imgproxy-3.13.1
found 3.13.1 in filename of file in /nix/store/r9n1bzy0bbwxg1d312khhf9iblafy46d-imgproxy-3.13.1

Rebuild report (if merged into master) (click to expand)

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
imgproxy

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/r9n1bzy0bbwxg1d312khhf9iblafy46d-imgproxy-3.13.1 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A imgproxy https://github.com/r-ryantm/nixpkgs/archive/0c541d2ac5953980ed8835c0a3167f85109f017b.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/r9n1bzy0bbwxg1d312khhf9iblafy46d-imgproxy-3.13.1
ls -la /nix/store/r9n1bzy0bbwxg1d312khhf9iblafy46d-imgproxy-3.13.1/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

1 package built:

imgproxy

Maintainer pings
cc @paluh for testing.

Result of nixpkgs-review pr 211964 run on x86_64-linux 1

1 package built:

imgproxy


Expose issue events in Danger DSL

It could be useful to have access to have DSL access to the list of events for a given GitHub issue. This would provide a way to determine for sure that one issue had referenced another, like we try to do in fastlane: https://github.com/fastlane/fastlane/pull/4985
It might also be interesting/useful to know that certain actors get mentioned in the ticket as well!

This one is super tied to GitHub, but a good idea on the side of general usefulness.
Sounds like we should start thinking about exposing a Plugin that does useful GitHub related things to the DSL. E.g github.events and github.octokit

This should be doable now that we have split out the github-specific code into it's own plugin.


Fix typo in README

Ah, #10 already exists. Let me close this. @kmizu Can you take a look at the pull request when you have time?

@seratch Thanks.  Certainly, a typo is found in README.  I'll fix it.


ENOENT when using only a text template

The following error is returned after creating a text.ejs file without an html.ejs or style.ejs in the same directory:
[Error: ENOENT, stat ''] errno: 34, code: 'ENOENT', path: ''

Adding an empty html.ejs doesn't seem to help, but renaming the text file to html.ejs works.

Closing as related PR is closed. If still persists please add a new issue.


feat: support refresh operation and loading page

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.飞澋 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

Codecov Report
Attention: 100 lines in your changes are missing coverage. Please review.

Comparison is base (8e70877) 0.95% compared to head (02a3df4) 0.95%.

Files
Patch %
Lines

...kotlin/com/alibabacloud/api/service/ProcessMeta.kt
0.00%
65 Missing :warning:

...kotlin/com/alibabacloud/api/service/ApiExplorer.kt
0.00%
22 Missing :warning:

.../main/kotlin/com/alibabacloud/ui/BaseToolWindow.kt
0.00%
13 Missing :warning:

Additional details and impacted files
@@          Coverage Diff           @@
##           master     #12   +/-   ##
======================================
  Coverage    0.95%   0.95%
======================================
  Files          20      20
  Lines         842     842
  Branches      125     125
======================================
  Hits            8       8
  Misses        833     833
  Partials        1       1

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


Choose camera option

It keeps opening the front camera on my mobile device. Wouldn't it be more practical if the user could pass the complete videoConstraints instead of just the deviceId? That way, users could specify the 'facing'-value as well as any other required value. Or you could add a facing-Prop and change line 59 to "videoConstraints={{ deviceId: deviceId, facingMode: facing || 'environment' }}"

Hey @ysuzuki19, is it possible to add facingMode parameter, like the deviceId on QrCodeReader?
Thank you!

By the way, I just created a pull request with the change: https://github.com/ysuzuki19/react-qrcode-reader/pull/6


cargo doc: add option to document only public items for binary crates

Describe the problem you are trying to solve

https://github.com/rust-lang/cargo/pull/7593 enables --document-private-items flag by default for binary crates. As stated in the PR:

We should also probably add a --document-only-public-items flag or something like that if we change the default behavior. Otherwise users have no way to not document private items for binary crates. Right? -> We can do it later

Describe the solution you'd like

Add flag like --document-only-public-items which can be used for binary crates to disable flag --document-private-items (which is enabled by default)

Took a whack at this in #10979. Hopefully that solves the need :)

Hi, just wanted to bump this, as it's definitely still something I would find useful. Generating documentation for a binary package can be useful to someone navigating a codebase for the first time, but unfortunately, certain macros tend to leave undocumented private items all over a crate (e.g: Tracing leaves private CALLSITE and META statics wherever any of its macros are used). The reasoning for closing #10979 was that #[doc(hidden)] can be used, but obviously in such cases, this is not possible. Plus tagging everything with #[doc(hidden)] gets kind of annoying anyway. Would the Cargo team be interested in merging a PR to address this?


insertInManagedObjectContext: returns objects of wrong class

I'm having an issue with using mogenerator together with MagicalRecord.
I have two entities, File, which is the parent entity, and Attachment, which is a child of the former. I also use MagicalRecord for creating entities like so:
managedObject = [entityClass MR_createEntityInContext:self.managedObjectContext];

Before converting my project to mogenerator everything worked fine but now all of a sudden the above code creates a wrong entity: instead of an Attachment it creates a File.
It seems to have something to with the insertInManagedObjectContext: method generated by mogenerator because MagicalRecord uses it to create entities:
if ([self respondsToSelector:@selector(insertInManagedObjectContext:)] && context != nil)
{
    id entity = [self performSelector:@selector(insertInManagedObjectContext:) withObject:context];
    return entity;
}

Right now I'm trying to find out why it stopped working... I'll add more information later if I discover anything useful.

It looks like the subclass's version of insertInManagedObjectContext: is never actually called.
However, when I check the class on which MR_createEntityInContext: in the debugger the class is correct.

Nevermind, it was my fault.


Add Xcode as dependency of flutter_view_macos__start_up in .ci.yaml

flutter_view_macos__start_up test landed in https://github.com/flutter/flutter/pull/111326, but lacked the dependencies that it needed to run successfully in postsubmit. This change adds Xcode as a dependency so that the flutter_view_macos__start_up test can be run in postsubmit.
There's no filed issue for this.
Pre-launch Checklist

[x] I read the [Contributor Guide] and followed the process outlined there for submitting PRs.
[x] I read the [Tree Hygiene] wiki page, which explains my responsibilities.
[x] I read and followed the [Flutter Style Guide], including [Features we expect every widget to implement].
[x] I signed the [CLA].
[ ] I listed at least one issue that this PR fixes in the description above.
[x] I updated/added relevant documentation (doc comments with ///).
[x] I added new tests to check the change I am making, or this PR is [test-exempt].

only affect code inside the .github directory, .cirrus.yml or .ci.yaml config files.

[x] All existing and new tests are passing.

Tested by removing bringup in f4701f8 (#111624).

Works with updated Xcode dependency 14a5294e. Thanks for letting me know @keyonghan!

Works with updated Xcode dependency 14a5294e. Thanks for letting me know @keyonghan!

Seems one more place referencing the old xcode: Mac flutter_gallery_macos__start_up. Could you fix that as well?

Seems one more place referencing the old xcode: Mac flutter_gallery_macos__start_up. Could you fix that as well?

✅ done


Article updates are incomplete

This article claims Get-MgUser is part of the AzureAD module, this is not true.
Also, if you're going to change the cmdlets used from AzureAD to Graph, as has been done in this document, you should include the profile used and the scopes required for Connect-MGGraph in order to run the listed commands.

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

ID: f52c6916-7e79-9a9c-b7a6-47041ddb81e3
Version Independent ID: 43c9b873-d354-d814-3065-1e8832361b86
Content: Set an individual user's password to never expire - Microsoft 365 admin
Content Source: microsoft-365/admin/add-users/set-password-to-never-expire.md
Service: microsoft-365-business
GitHub Login: @kwekuako
Microsoft Alias: kwekua

@justinmontgomeryCF Thank you for your feedback. We have made changes to the document via PR#https://github.com/MicrosoftDocs/microsoft-365-docs/pull/12127
Once the author approves, the changes will be live.
Thanks
Sri


Feature Request: tree-structured regression and classification models

I'm trying to visualize a decision tree. The interpretable ML book has a nice visualization for it:
library("partykit")
set.seed(42)
n = 100
dat_sim = data.frame(feature_x1 = rep(c(3,3,4,4), times = n), feature_x2 = rep(c(1,2,2,2), times = n), y = rep(c(1, 2, 3, 4), times = n))
dat_sim = dat_sim[sample(1:nrow(dat_sim), size = 0.9 * nrow(dat_sim)), ]
dat_sim$y = dat_sim$y + rnorm(nrow(dat_sim), sd = 0.2)
ct = ctree(y ~ feature_x1 + feature_x2, dat_sim)
plot(ct, inner_panel = node_inner(ct, pval = FALSE, id = FALSE),
  terminal_panel = node_boxplot(ct, id = FALSE))

Maybe this would be a nice feature for GraphMakie as well

Actually this would be interesting if we could dispatch on scatter and instead of circles, draw general objects.


Group5

Roger Gordon
Will Noland

I suggest taking a look at PEP8 and PEP257
You're using docstrings as block comments and it makes your code hard to read.  Your nested for loop and if statement on lines 25-42 really should be grouped together instead of broken up with all those comments.

Thanks @Metallidog and @corginomics for the feedback. You are right about the comments littering the code. We put these in to aid each other as me and @Landl3ss are in completely different time zones (9 hours apart) so weren't able to complete the solution together. We should have removed these before making the pull request. Will make sure that is done next time!


[ISSUE#6929] Temporarily ignoring testQueryMessageAsync testing on the Linux platform

Which Issue(s) This PR Fixes

Fixes #6929
Brief Description

Temporarily ignoring testQueryMessageAsync testing on the Linux platform
How Did You Test This Change?

Codecov Report

Merging #6930 (9b0605c) into develop (2246c32) will decrease coverage by 0.05%.
The diff coverage is 52.22%.

@@              Coverage Diff              @@
##             develop    #6930      +/-   ##
=============================================
- Coverage      42.61%   42.56%   -0.05%
- Complexity      9122     9153      +31
=============================================
  Files           1128     1131       +3
  Lines          80133    80221      +88
  Branches       10432    10468      +36
=============================================
+ Hits           34146    34149       +3
- Misses         41706    41798      +92
+ Partials        4281     4274       -7

Impacted Files
Coverage Δ

.../apache/rocketmq/filter/parser/ParseException.java
56.71% <ø> (+7.46%)
:arrow_up:

...ocketmq/filter/parser/SelectorParserConstants.java
100.00% <ø> (ø)

...pache/rocketmq/filter/parser/SimpleCharStream.java
37.94% <ø> (ø)

.../java/org/apache/rocketmq/filter/parser/Token.java
61.53% <ø> (ø)

...g/apache/rocketmq/filter/parser/TokenMgrError.java
0.00% <ø> (ø)

...apache/rocketmq/remoting/protocol/RequestCode.java
0.00% <ø> (ø)

...cketmq/remoting/protocol/header/ExtraInfoUtil.java
11.53% <0.00%> (-0.37%)
:arrow_down:

...cketmq/broker/processor/PopBufferMergeService.java
29.85% <16.66%> (-0.66%)
:arrow_down:

.../apache/rocketmq/filter/parser/SelectorParser.java
45.63% <35.49%> (+5.52%)
:arrow_up:

...etmq/filter/parser/SelectorParserTokenManager.java
47.36% <45.78%> (+0.33%)
:arrow_up:

... and 9 more

... and 36 files with indirect coverage changes
:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


[JAX] Bug fix for distributed normalization

Description

Added CudnnHandlerInit into the prepare phases of normalization custom calls.
Make NormalizationPlanRegistry thread_local.

These changes should fix the failures in test_distributed_layernorm.py.
Type of change

[ ] Documentation change (change only to the documentation, either a fix or a new content)
[x] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Infra/Build change
[ ] Code refractor

Checklist:

[x] I have read and followed the contributing guidelines
[x] The functionality is complete
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[ ] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes

/te-ci jax L1


error with pass.lst

It need the right path to your pass.lst file

but where is the pass.lst in the instagram folder?

You have to create it yourself; there are many ways to create it, but you can use this script


Define equivalence classes between cards to reduce search thrashing

For instance the following cycles are equivalent in terms of the simplified colorless mana producer:

Talisman Cycle
Signet Cycle

This will not apply to a deeper analysis when color is included, but until that is a necessity, this could save a lot of time.

Completed.


Fix invalid insert_with_values loop

The set methods are where the bug originated.

Heh, it's not fair that this PR fails the tests because #268 hasn't been merged :)

Isn't it? :p


Changing default schema name prevents change data tables/views from being defined

When the default schema value is modified to anything other than a value of "dbo" and real-time updates are enabled which results in a the ChangeFeed folder being created then the anticipated "cdc" prefix is not applied to views or table names in Synapse for the tables located in the ChangeFeed folder.   A modification to the manifestToSQLMetadata method in the ManifestHandler.cs file addresses this as seen in the screenshot.  Removing the dependency on the schema name allows for the "cdc" prefix to be applied to ChangeFeed tables.  The result of not have having this change is that when running the CDMUtil as a Function App whenever an event is fired the views or tables are redefined and could be pointing to either either the Table folder or the ChangeFeed folder in the ADLS depending on the last event processed.  CC: @jiyada

@jiyada
is this done by design?
https://github.com/microsoft/Dynamics-365-FastTrack-Implementation-Assets/blame/e272c7f266dfb329c4a4a6ef722eba3c325ebbab/Analytics/CDMUtilSolution/CDMUtil/Manifest/ManifestHandler.cs#L363

Thanks for pointing this out. I believe the intent here was if you are trying to create view on the Changefeed folder, you probably are trying to use the pipeline to copy the data incrementally to SQL . For simplicity, pipeline defaults to dbo to switch between table and _cdc table. However, this does have potential bug as described above and will fix it.
Happy to accept the PR and merge it  @russtolsma  @adriennn


fix: get OPENAI_API_PROXY_ADDR environment variable error

书写错误，应为 OPENAI_API_PROXY_ADDR

https://github.com/soulteary/sparrow/releases/tag/v0.6.0  @cdswyda


xmlns

The API looks really nice! Do you have plans to support parsing XML that uses namespaces?

I just added a basic byNamespace selector to master, but I haven't used it in a practical progra yet. I'm planning on writing some xleb-based parsers for more "real world" XML that includes namespaces to experiment and find out whether this naïve implementation is sufficient or if I need something more elaborate, so it's definitely planned!


Update sensitivity-labels.md

@JohanFreelancer9  could you copy edit this and then at-mention me so I can merge it ASAP please?

@JohanFreelancer9 I copy edited it myself. It needed to go live. Sorry for bothering you.


Fixed add question bug

handleAddQClick was not bind before sending it down to child component to be used

Makes sense!
I noticed you are using a few different styles for binding:

Bind in the constructor
Bind in the props
Buttons are using anon arrow function style

The one in the constructor looks like this:
this.handleAddAnswerClick = this.handleAddAnswerClick.bind(this);

You may want to handle the rest of the methods the same way for few reasons:

Binding happens once (during construction) rather than on every render or button click
All of the binds are in one place, so you always know where to go when adding/removing methods
It makes the code easier to read wherever you invoke them

If you go this route, then in render you can just reference the method name without using bind(this) or arrow functions:
<QuestionsList questions={this.state.displayQuestions} handleAddAnswer={this.handleAddAnswerClick} handleAddQ={this.handleAddQClick} handleMoreQuestions={this.handleMoreAnsweredQuestions} />
<AnswerModal show={this.state.answerShow} handleClose={this.handleAddAnswerClick} question={this.state.questionId} />
<AddQuestion show={this.state.questionShow} handleClose={this.handleAddQClick} />
<button onClick={this.handleMoreAnsweredQuestions}>More Answered Questions</button>
<button onClick={this.handleAddQClick}>Add a question</button>

I also noticed that when rendering the QuestionsList component, you are passing handleAddQ as a prop, but QuestionsList does not call anything, so I think you can remove that as a prop.

Last thought, and this is not specific to the PR, but something I noticed just now as in PR-review mode that we might want to discuss as a team and possibly change.
First, understand that my comment here is...

Not a prescription, just a thought I had while reviewing code that I think it worth sharing
Something I see in react docs too, so maybe I'm way off on this
Something I do as well (but think I will change)
A low priority to change given our timeline

Methods named "handleX" or similar require you to read the method to know what they are doing. A method name like this is just repeating what you already know by seeing where it's invoked. For example, if it's on a button click, you already know it's handling the button click. It might be helpful for "future us" or other devs if the methods were more descriptive of what they do.
For example:

handleMoreAnsweredQuestions --> showMoreQuestions
handleAddAnswerClick --> showAddAnswerForm
handleAddQClick --> showAddQuestionForm

Not picking on you, just noticed how I was thinking while looking at things and wanted to capture the thought.


index pages have hardcoded version

consider getting the latest version from the version store
e.g. https://github.com/ardc-fair-checklist/ssg/blob/4f7d5cf8e056c538d92d351bd7a627b1596edff4/pages/software/v0.2/index.page.vue#L79

partly fixed by fda6670, still some references in BadgeSnippets:
https://github.com/ardc-fair-checklist/ssg/blob/fda66701d35e54ba2b08e5b80820224be1c5bccb/pages/software/v0.2/BadgeSnippets.vue#L41-L50

no more hardcoded version strings in code base, reactivity problems (#36) seem to have been solved by 49dee0d


fix(product-sync): fix setting multiple category order hints at once

[x] commit messages are commitizen-friendly
[x] code is unit tested
code is integration tested
public code is documented
[ ] code is reviewed by at least one person
[x] code satisfies linter rules

Coverage increased (+0.006%) to 97.232% when pulling 38867b4541a9abca95588f4e78cc58c1ed517dae on fix-setting-multiple-category-order-hints into 2599b5b1ede35699b9720f507ae21fc6eb089355 on master.


Feature/183/alert component

Description
Closes #183
Added a concept Alert component for usage in for example the issue described in #183

Has several configuration options, easily scalable

Works alright on darkmode. Readable

Type of change
Please select the option that is relevant

[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected)
[ ] Documentation

Checklist

[x] I have commented my code, particularly in hard-to-understand areas.
[x] All the required documentation is added.
[x] My code follows the style guidelines of this project.
[x] I have performed a self-review of my own code.

Additional information
Considerations
Placement
Not sure if this is the right place to put the alert box. Should it be added to more pages? Do we still need a sidenav item to resolve #183 #184
Do we even need this with the sidenav implemented?
Icons
I am not sure what icons are used (which libary). Thus I cannot add icons appropiate for the Alert. e.g. a checkmark on a success message. All use information icon for now

Thanks. Personally I don't agree with the prominent place the alert gets. I did it more subtle here (https://deploy-preview-184--stellular-banoffee-031bf4.netlify.app/)
I do think we can use this alert boxes on other routes:

https://ictresearchmethods.nl/research-pattern-navigator/
https://ictresearchmethods.nl/methods-overview/

Going to create a new version of the methods overview next week, so an alert that the content might be more clear on the old site might work.
Thanks!

Thanks. Personally I don't agree with the prominent place the alert gets. I did it more subtle here (https://deploy-preview-184--stellular-banoffee-031bf4.netlify.app/)
I do think we can use this alert boxes on other routes:
1. https://ictresearchmethods.nl/research-pattern-navigator/

2. https://ictresearchmethods.nl/methods-overview/

Going to create a new version of the methods overview next week, so an alert, that the content might be more clear on the old site, might work for now.
Could you implement the info/blue one on top of those two pages. That will definitely help the user.
Thanks!

Honestly agree.
Will revert changes on the homepage so the component is isolated in the branch.
Otherwise feel free to cherypick if deemed component could be useful

Perfect! I've merged the other one. The additions on this MR might be very helpful for the users that prefer the old one.
Not planning to keep the wiki all the time, but collecting feedback from the users is very helpful to eventually remove the whole wiki.

@NoWarries I was wrong. It's pretty nice to have those alert boxes on the main page. I added those and will merge it. You can adjust things if you want, but it's comparable with your initial design.


Fixing multiple docker issues

Fixes #377

Trusted LGTM

LGTM

I have run this PR within Docker, and gitea still seems to require the public and template directories. How do they get set into the container if not being copied in at build time?

There is the generate make task and the bindata build tag

So these two directories are getting bundled into the binary

Thanks - works now. Perhaps you can automatically add the bindata tag to the "Make docker:" target? I didn't know to set the bindata tag.


Change Title and Chat Format

Hey there,
now the site is working fine. But how can i change the title "$0.00 | CSGO Win Big" and how can i remove the time and fate stamp in chat.
thank you in advance.

https://github.com/ztizzlegaming/CSGOWinBig/blob/master/src/script.js#L252

And for Time look in line 440
str += '' + date + ' at ' + time + '';


Added GUI interface main.py

Type of change

[ ] Added new project
[x] Bug fix
[x] New features
[x] Enhanced documentation

Changes proposed in this pull request

Project name : Weather

Short description :

Added a gui interface for easy display of weather data.
Also added pressure and humidity display functionality
made the code more clear and user friendly

Checklist

[x] The code is Python 3 compatible
[x] I have added relevant comments in my file to make code understandable
[x] I have added my project in a folder which includes all the necessary files

@robertlent @iamshreeram @IamSoo @this-mkhy This pr is for hacktoberfest. Kindly merge if everything's alright.


[RunequestGQS] Statistics bonuses are not transferred to skills in the QS sheet

In the RunequestGQS character sheet, if you select QS version, add some stats etc.
The bonuses are not added to either the bonus boxes on the Skills tab or to the skills themselves.
Current game version tested with a new game created 11/08/2020 and the sheet imported.

Why are using the QS that was created as a  stop gap and  should  have been deprecated but I didn't want the hassle of getting it deprecated.

I was exploring using it for a starter adventure I am writing that uses non-humanoid characters.
If it is deprecated - maybe just add a couple of comments: one in the UI so it reads "Quick Start (deprecated)" and another in the code at the start of the QS section.
In the end I have just customer edited the character sheet (html and css) into a specific version for these non-humanoids.  As they are all of the same species and all the other creatures are NPCs this should work.
On a completely different topic, is there a reason why you were not able to simplify the the dice roll button calling code to encapsulate the success/fail/special/critical/fumble chances and outcomes rather than adding long repeated code lines?
Note: I am not a JavaScript developer so it could be something blindingly obvious to you.

Sheet authors have very limited access to javascript and the template that
produces the results is very limited also.  I am no longer supporting this
sheet.
On Tue, 18 Aug 2020 at 09:47, Lewis Jardine<EMAIL_ADDRESS>wrote:

I was exploring using it for a starter adventure I am writing that uses
non-humanoid characters.
If it is deprecated - maybe just add a couple of comments: one in the UI
so it reads "Quick Start (deprecated)" and another in the code at the start
of the QS section.
In the end I have just customer edited the character sheet (html and css)
into a specific version for these non-humanoids. As they are all of the
same species and all the other creatures are NPCs this should work.
On a completely different topic, is there a reason why you were not able
to simplify the the dice roll button calling code to encapsulate the
success/fail/special/critical/fumble chances and outcomes rather than
adding long repeated code lines?
Note: I am not a JavaScript developer so it could be something blindingly
obvious to you.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/Roll20/roll20-character-sheets/issues/7186#issuecomment-675348733,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACET77MJ43N664KDMYF334DSBI527ANCNFSM4P6NU32Q
.


SDK Reference?

The guides on read-the-docs are super helpful, but just wondering if there is a reference document somewhere with all of the available methods and arguments?

Unfortunately not at the moment, until now I thought that IDE autocompletion and the GitHub code browser were enough (and I shied away from the additional build steps and deployments of the generated API docs, after finding a good generator 😅).

No worries, I can get by with autocompletion :)


v3 support?

Support guidelines

[X] I've read the support guidelines

I've found a bug and checked that ...

[X] ... the documentation does not mention anything about my problem
[X] ... there are no open or closed issues that are related to my problem

Description
Looks like this isn't automatically updating with v3 support.
Expected behaviour
v3 support available.
Actual behaviour
Stuck at v<IP_ADDRESS>-r15
Steps to reproduce
N/A
Docker info
N/A

Version
N/A
Docker compose
N/A

Container logs
N/A
Additional info
No response

Yes working on it

Ah nice okay, thank you 😄


Load subscription data on app startup

The Issue
Currently, we don't check the API or load subscription data until the user subscribes to something or visits the subscriptions page. This should be loaded on startup instead.
Side effect: Clearing cache or logging into a new PC with old account will result in a subscription 101 notification if you subscribe to something before visiting the subscription page.
Thanks @ceogear for finding this one!
System Configuration

LBRY Daemon version:
LBRY App version:
LBRY Installation ID:
Operating system:

Anything Else

Screenshots

@daovist probably easy to roll into current sub work?

Yes, this is going in my subscriptions epic.

Completed and confirmed in https://github.com/lbryio/lbry-desktop/pull/1872


[5.7] Multiple mail connections

I'm currently working on a project where multiple mails should be sent in a single request, each requiring their own SMTP settings and there's even one that could be sent using another driver. At the moment Laravel constructs the Mailer during first initialisation and then doesn't allow switching driver or even configuration like SMTP settings that easily.
I think the Mail component could benefit greatly from adopting a similar setup as the Database component: 1) multiple connections can be defined, which accommodates the need for multiple configurations using the same driver but with different settings; and 2) the "connection" can be chosen on runtime without any hassle.
For example, this could be the config/mail.php file, and then mails could be sent as follows:
Mail::send(...); // Uses the default connection.
Mail::connection('other_smtp')->send(...); // Uses the "other_smtp" connection
Mail::connection('sparkpost')->send(...); // Uses the "sparkpost" connection

I'm eager to learn your insights.

The manager is missing the ability to extend with more drivers. Might be cool to go as far as having a custom driver like the LogManager does.

Yeah as I mentioned in the disclaimer it's far from perfect (and perhaps isn't even working in its current state). Just wanted to reach out first to avoid spending too much time on a concept that gets rejected.

As an additional note: the DatabaseManager deviates from Illuminate\Support\Manager in the sense that a driver is defined on connection level, while the Manager directly asks for and returns various drivers.
If the overall concept is ok, perhaps this is a good moment to introduce a second Manager-like Support class (e.g. ConnectionManager) and let DatabaseManager and MailManager extend from it?

It's certainly the thing Laravel is missing.
When I need this I use this workaround

I'm generally fine with the idea behind it if you want to polish it up and test it.

@decadence Me too, I have to override the method sendof Mailable Class.

Awaiting feedback on the referenced PR that adds the mentioned ConnectionManager support class.

I don't want to get bogged down with new abstractions and generalizations yet. Let's just focus on the mail aspect.

Here's a first take on this. I'm unsure if the tests are fine and could use some advice on this.
Here's the PR for changes in the default config file.
Looking forward to feedback.

Hey @Propaganistas
This looks good overall, not sure if you plan on working on this a bit further so we can get this merged soon?
I've a question though, would this allow each connection to have it's send from.name and from.address instead of using the global one?
The idea would be to still have the global one though, but been able to override it per connection i guess.

Hi @brunogaspar, I'm still waiting for some feedback as well. I think the core team wants to finish up some other stuff before merging this one.
Currently allowing each connection to specify its own from address isn't implemented but I really like the idea. Gonna take a shot at it. Thanks!

@Propaganistas

Currently allowing each connection to specify its own from address isn't implemented but I really like the idea. Gonna take a shot at it. Thanks!

That's cool :)

I'm still waiting for some feedback as well.

I'm going to give this PR a try really soon and will leave some feedback after.

I think I'm going to hold off on this for now. I will try my own take at it sometime.

Is this still on the list?

Is this something still on the roadmap?

i'm waiting feature 🤔


Virtual Env issues.

I installed the virtualenv as described in the install walkthrough.  Once I did and set the other two commands, then attempted to download via pip, I get HTTP errors in orange text.  I restarted and tried again, same result.  Takes forever to complete the attempts and retries but never downloads.  Also after that the pi is running pihole super slow.  Any thoughts?

well after a second restart it took the command and installed...found the modem...as soon as I dialed a test call, pihole died and then call attendent stopped working.  Since pihole died my network dns went down.
Is the two softwares running at the same time, one in virtual...too much for a pi 3b+, I checked systems resources when both were running and only 38% of RAM was used up...but there was plenty of CPU left.
I am confused.

  I am sorry to keep blowing you up.  I know that the slowness comes from accidentally installing it outside the virtual.    So I ran the cflags command mentioned in another user's issue.  It installed the gpio thing.  BUT now this is the output from running callattendent --createfolder
"Traceback (most recent call last):
File "/home/pi/venv/bin/callattendant", line 8, in
sys.exit(main())
File "/home/pi/venv/lib/python3.9/site-packages/callattendant/main.py", line 19, in main
from app import main
File "/home/pi/venv/lib/python3.9/site-packages/callattendant/app.py", line 35, in
from config import Config
File "/home/pi/venv/lib/python3.9/site-packages/callattendant/config.py", line 15, in
from werkzeug.utils import import_string
File "/home/pi/venv/lib/python3.9/site-packages/werkzeug/init.py", line 2, in
from .test import Client as Client
File "", line 1007, in _find_and_load
File "", line 986, in _find_and_load_unlocked
File "", line 680, in _load_unlocked
File "", line 786, in exec_module
File "", line 918, in get_code
File "", line 587, in _compile_bytecode
ValueError: bad marshal data (invalid reference)
"

GOT IT.  I think I was panicking.  I just uninstalled the virtualenv and call attendant then restarted and reinstalled from beginning after purge.  It worked this time...but I made sure to run an update...so I think I was running an out of date or problematic version of python.
Got it.  Thanks.


DynamoDB unmarshalling slow

Describe the bug
Unmarshalling DynamoDB GetItem / BatchGetItem response is slow - ~700 msec for a 1.7 MB response
Regression Issue

[ ] Select this option if this issue appears to be a regression.

Expected Behavior
Unmarshalling time << of the HTTP request time
Current Behavior
Unmarshalling time >> of the HTTP request time
Reproduction Steps
Copy the following files in a S3 folder:
djk7enshnmzkphkldeszvgzole.json.gz
ikhj4i2zsi4ptfwkszjkizzvly.json.gz
jmknnpggim2u3fd3lknw5njlsq.json.gz
m5lnl37q7a7z7hvykktyqt2mn4.json.gz
Use the DynamoDB 'Import from S3' function on that folder to create a table

Table name dbperftest
Data format: DynamoDB JSON compressed
Partition key: @rid (string)
-No sort key
Capacity mode: on demand
No indexes, default encryption at rest

Download, compile and run
DBPerfTestConsole.zip

it expects AWS profile and region in the AWS_PROFILE and AWS_REGION environment variables (SSO is fine)
it reads data from the dbperftest table in various ways - main one being reading 100 items using a single BatchGetItemCall - whose statistics are:

CredentialsRequestTime = 00:00:00.0000269; RequestSigningTime = 00:00:00.0003347; HttpRequestTime = 00:00:00.2243586; ResponseUnmarshallTime = 00:00:00.7423187; ResponseProcessingTime = 00:00:00.7452110; ClientExecuteTime = 00:00:00.9727216;

with an unmarshall time that is more than three times the HTTP request time
Possible Solution
No response
Additional Information/Context
No response
AWS .NET SDK and/or Package version used
AWSSDK.DynamoDBv2 3.7.403.3
Targeted .NET Platform
.NET Core 8
Operating System and version
Windows 11, Amazon Linux

We are currently working on a V4 of the SDK. As part of that V4 we hoping to switch the SDK's JSON parsing to System.Text.Json from the its internal usage of a JSON library called LitJson. We aren't far enough yet with the change to measure the performance difference but we will use your sample code for measure the difference.

Needs review with the team as v4 backlog item.

We're not planning to change the serialization in V3 as that'd be too much of a breaking change. For V4, you can track the progress here: https://github.com/aws/aws-sdk-net/issues/3362
See also Norm's latest comment about V4's timeline: https://github.com/aws/aws-sdk-net/issues/3362#issuecomment-2474478445

I see . . .
I tried with the v4 preview and the unmarshalling time is better but still not great:
HttpRequestTime = 00:00:00.1873335; ResponseUnmarshallTime = 00:00:00.3164829; ResponseProcessingTime = 00:00:00.3181069; ClientExecuteTime = 00:00:00.5074811;

(it is 2 times slower than the raw DynamoDB call instead of 4+ . . . )

Keep in mind that HttpRequestTime is the time to first byte but the full response is read while doing the unmarshalling. So the numbers are a bit misleading what is exactly the "HTTP" part and the "Unmashalling" part.


DataPipe for GCS (Google Cloud Storage)

🚀 The feature
Build a DataPipe that allows users to connect to GCS (Google Cloud Storage). There is a chance that existing DataPipes may suffice, so we should examine the relevant APIs first.
Motivation, pitch
GCS (Google Cloud Storage) is one of the commonly used cloud storage for storing data.
Alternatives
Existing DataPipes are sufficient and we should provide an example of how that can be done instead.
Additional context
Feel free to react or leave a comment if this feature is important for you or for any other suggestion.

This can be closed as we have an example: https://pytorch.org/data/beta/dp_tutorial.html#accessing-google-cloud-storage-gcs-with-fsspec-datapipes


Server get/post/...etc handlers cannot be async and return promise according to current TS typings

Right now if I try to use async function as any kind of handlers (get/post/etc...) typescript will alarming me about non-correct type of handler function. It accepts only plain void function.

Right now if I try to use async function as any kind of handlers (get/post/etc...) typescript will alarming me about non-correct type of handler function. It accepts only plain void function.

I am doing a research about bugs in TypeScript, and I am trying to reproduce this bug. But I succeed to assign a async function to a property typed as returning void, just like WebSocketBehavior.message, without alarming.
May I ask what your case was and how the alarm showed?

I'm using ts-standard and it was pushing some error. I don't remember which one. You can try to reimplement it by yourself by installing ts-standard and desired version of uWS.js.

@JerryZhongJ I'm using ts-standard and it was pushing some error. I don't remember which one. You can try to reimplement it by yourself by installing ts-standard and desired version of uWS.js.

@JerryZhongJ @typescript-eslint/no-misused-promises
https://github.com/typescript-eslint/typescript-eslint/blob/main/packages/eslint-plugin/docs/rules/no-misused-promises.md#checksvoidreturn


Change cosine bell to be single layer

Checklist

[x] Testing comment in the PR documents testing used to verify the changes

@cbegeman, this is a placeholder until we figure out how to have shared yaml options

Testing
We ran cosine bell with this branch on anvil and it ran successfully

@lconlon, it seems like @cbegeman's right. I looks like the changes to cosine_bell.cfg didn't get committed and pushed to this branch yet.  We'll do that tomorrow.
@cbegeman, we're waiting on #57, regardless so no need to review yet.  These changes will be updated once that goes in.

 Here's the relevant comment: https://github.com/E3SM-Project/E3SM/pull/5590#issuecomment-1522526731.
I'm not quite sure why this case works with debug tracers but dam_break did not. I guess we should change MPAS_LOG_CRIT to MPAS_LOG_WARN.

@cbegeman, thanks for the heads up.  I guess the current submodule must be from before this change or we wouldn't have been able to run cosine bell.  Since there aren't any dynamics other than advection, it could be that this test just doesn't trigger whatever problem you saw in https://github.com/E3SM-Project/E3SM/pull/5590#issuecomment-1522526731.
It does seem like the change in https://github.com/E3SM-Project/E3SM/commit/73b90f7a392587840855cc6a05945a23e0209196 would make it impossible to run the cosine bell in single layer.  I don't know how much time we want to spend investigating debugTracers in RK4 but maybe we could allow debugTracers when config_disable_tr_all_tend == .false. but disallow them when config_disable_tr_all_tend == .true..  We aren't disabling tracer tendencies here (because tracer advection is the whole point of the test case).
Maybe this is a combination you've tried already and caused crashes.  Let's chat more about this tomorrow.

@xylar I've already tried that combination. I think the best path forward is just to change MPAS_LOG_CRIT to MPAS_LOG_WARN and continue disabling debug and active tracers for the wetting and drying tests.

Thanks @cbegeman.  I can make the PR to E3SM if you like.

@lconlon I think the documentation for this test case does refer to 3 layers in the vertical_grid section. If so, that should be updated.

@cbegeman, thanks for catching that. I believe I have it updated now, but let us know if I missed any multilayer references that you had seen.

That's the one I had in mind!

I'll update the E3SM submodule and re-test, then I hope we're good to go on this.

Testing
I ran both cosine_bell test cases and they passed with this branch:
Test Runtimes:
06:26 PASS ocean/global_convergence/qu/cosine_bell
04:54 PASS ocean/global_convergence/icos/cosine_bell


How to add auth to only some service actions?

Hi,
I have following requirements:
I have several services where each service has multiple actions.
Some actions will be accessible via an API gateway, some not (they are private).
Some of the actions accessible via the API getaway should only be accessible after auth, others are public.
My API should have this structure:
/api/<version>/public/<service>/<action>
/api/<version>/protected/<service>/<action>

What works:
The closest I'm getting is with this code:
// api.js
const HTTPServer = require("moleculer-web");

module.exports = {
	name: "api",

    mixins: [HTTPServer],

    settings: {
        port: process.env.PORT || 8080,

        routes: [
            {
                path: "/api/public",
                whitelist: [
                    "v1.public.**"
                ]
            }
            ,{
                path: "/api/protected",
                authentication: true,
                authorization: true,
                whitelist: [
                    "v1.protected.**"
                ]
            }
        ]
    }
};

// public/service.js
module.exports = {
    name: "public.service",
    version: 1,

    actions: {
        async login(ctx) {
            return "public action";
        }
    }
};

// protected/service.js
module.exports = {
    name: "protected.service",
    version: 1,

    actions: {
        async login(ctx) {
            return "protected action";
        }
    }
};

The problem:
This works, but it results in ugly paths for the api's:
/api/public/<version>/public/<service>/<action>
/api/protected/<version>/protected/<service>/<action>

So there are actually 2 problems with this approach, but I don't know how to fix this with moleculer(-web):

I have to split each service in 2 separate services in order to add auth to only some actions of a service at the gateway level
The API paths are ugly, they should be flattened in some way

Check this example how it controls which actions are protected
https://github.com/moleculerjs/moleculer-examples/blob/master/conduit/services/api.service.js#L97
https://github.com/moleculerjs/moleculer-examples/blob/master/conduit/services/articles.service.js#L83

Thanks for the pointers icebob!
So if I understand correctly, the suggestion is to enable authorization for the whole API (i.e. the /api route) but then override this behaviour in the authorize implementation based on the auth flag of each action?
This sounds good, but the only thing I'm worried about with this implementation is that each action is public by default, unless an explicit auth: true flag is set.
So whenever one forgets to set this flag, the action is exposed via the gateway.
But I suppose I can revert that behaviour by throwing an UnAuthorizedError when auth fails, unless the auth flag of the action is explicitly set to false (auth: false)?

In this case, change the logic, and rename the prop to noAuth: true and swap the condition in the authorization, as well.

Yes, noAuth: true is better than auth:false
Anyway, I tested this setup and it's working as expected.
So I'm closing the issue...
Thanks @icebob


Volume snapshot is always not ready to use

hello,I installed csi driver followed https://fuckcloudnative.io/posts/kubernetes-storage-using-ceph-rbd/
k8s version：v1.18.8
ceph version：14.2.22
snapshotter version ：2.1
When I create a volumesnapshots,my volumesnapshot is always showing READYTOUSE: false

If further info can be helpful let me know.

@byjos did u finish the problem


Update gRPC SHA

Signed-off-by: Jimmy Chen<EMAIL_ADDRESS>Description: Update gRPC SHA to pick a gRPC STS fix for gRPC 1.25 https://github.com/grpc/grpc/commit/d8f4928fa779f6005a7fe55a176bdb373b0f910f
Risk Level: Low
Testing: Existing tests
Docs Changes: n/a
Release Notes: n/a
[Optional Fixes #Issue] https://github.com/istio/istio/issues/20133
[Optional Deprecated:]

Any reason why you are not jumping to the latest release?
    com_github_grpc_grpc = dict(
        sha256 = "2df2804a89dc707b8402b4c946956203d2bc1814a4ef4d09a40fa2c4ae1729b8",
        strip_prefix = "grpc-1.27.1",
        urls = ["https://github.com/grpc/grpc/archive/v1.27.1.tar.gz"],
    ),

Any reason why you are not jumping to the latest release?
Ideally we can upgrade to 1.27, but I found some Envoy ALTS issues after upgrading to 1.27, and that requires some investigation. Besides, I am not sure if the latest gRPC release would cause any regression to Envoy.
This PR supports Enovy to use gRPC 1.25 plus a STS fix. Which would be low risk.


add qe_usage var env to track leakages

The new custom property - QE_USAGE, will help us to track after leakages by indicating the name of
the profile from which the cluster was created and did not teardown.
Depends on this PR

/approve

/override ci/prow/rosa-sts-advanced-optional-presubmit

/lgtm


Cancel moved to avoid crash

I maintain a couple of apps that uses your library to great success.
However there are an annoying crash that happens in both apps - even though the actual implementation of cancelling download tasks is very different in the apps.
A simple way it can be replicated would be to do this:
func collectionView(_ collectionView: UICollectionView, didEndDisplaying cell: UICollectionViewCell, forItemAt indexPath: IndexPath) {         if let cell = cell as? TestCell {             cell.imageView.kf.cancelDownloadTask()         }     }
In that case - if you have a long list - so you can get your scrolling velocity high and maintain that velocity it will eventually crash.
From my debugging the cause seems to be that since the underlying URLSessionDataTask is cancelled prior to the callback then it can actually have become nil when we are later using the task in the callback.
I have tested this solution in both my apps and the crash has disappeared and I have seen no side-effects from this change.
It seems that since I actually began the investigation of this, an issue (https://github.com/onevcat/Kingfisher/issues/1511) has been opened from a different user regarding the same problem I have tried to solve here. At least, when inspecting their crash logs it looks very similar to what I experience in my apps where it crashes in SessionDelegate.remove() by URLRequest.unconditionallyBridgeFromObjectiveC(:)
Let me know what you think.

@Statsminizzle Thanks a lot for this!
It looks promising at the first glance. I will soon check and verify it carefully and deeper to see if there is any side-effect (since all the tests are passing so I guess it is fine!).

Checked it.
In the ideal Swift world, that crash should not happen. But when things come to Objective-C bridging or some low layer memory management (as the #1511 indicates a EXC_BAD_ACCESS crash), I am afraid it is an implementation detail that we cannot know easily.
Let's merge it and see if it can fix that issue!
Thank you for your contribution and I will tag it soon.


undeclared identifier 'MENU_CUSTOM_COMMAND'

I'm using Ubuntu 20.04.5 LTS.
I followed the instruction from readme to build it from source (Version 3.1.0). But when I tried to do "make", it gave me an error.

So, as suggested in the error message, I opened the /src/plugin.c file and changed "MENU CUSTOM COMMAND" to "MENU CUSTOM ACTION" and everything worked perfectly.

Now I'm wondering if that was truly a mistake or if it was a problem with my system...!!

I don't get that compile error.
Which version of Rofi do you have?
$ rofi -version
Version: 1.7.5

$ grep -E "MENU_CUSTOM_(ACTION|COMMAND)" /usr/include/rofi/mode.h
  MENU_CUSTOM_COMMAND = 0x00800000,
  MENU_CUSTOM_ACTION = 0x10000000,

I'm truly sorry. I should have looked at the version first. The issue was with the version.
I'm running rofi 1.5.4, which doesn't support MENU CUSTOM COMMAND.
Actually, I'll be migrating to Arch very soon. So, I did not upgrade Ubuntu to the latest version.

I'm glad we found the problem! :smile:
Good luck with Arch, btw :wink:


make Dependabot a default plugin

As suggested in #393, I split the basic implementation of the Dependabot plugin from this PR setting it as a default plugin. My rationale for making it default is as follows.

Some default plugins such as CompatHelper and TagBot use GitHub actions
Updating dependencies seems to be considered important since CompatHelper is a default plugin
Thus, it seems reasonable to keep also GitHub actions dependencies up to date when using a default configuration

I'm unclear how crucial this is.
Like it seems to me to create a lot of noise, requesting to update things that haven't changed much like simple actions such as checkout.
Though perhaps that noise goes away after you have been using it for a while.
This seems less important than CompatHelper, since the big issue for Compat is that it is easy to end up in a situation where two packages can't be used together due to requiring different versions of downstream packages.
This can't occur for github actions as we are not in julia packages defining new actions other people can use.
Once you have a set of actions that works, it will keep working forever, AIUI.
modulo it depending on external resources tat get taken down and/or changed.
I can imaging that last occuring for some of our julia CI actions, so maybe  that does make sense to have this turned on by default.

Once you have a set of actions that works, it will keep working forever, AIUI.

That's not completely true as far as I know. For example, consider one of the latest CI runs in this repo:
https://github.com/JuliaCI/PkgTemplates.jl/actions/runs/4856935409
You can find lots of warnings

Node.js 12 actions are deprecated. Please update the following actions to use Node.js 16: actions/checkout@v2. For more information see: https://github.blog/changelog/2022-09-22-github-actions-all-actions-will-begin-running-on-node16-instead-of-node12/.

As far as I understand, the old actions will not continue to work forever and we must update the versions of these actions to get something usable in the future. That's why I became aware of this issue and submitted PRs such as https://github.com/JuliaCI/PkgTemplates.jl/pull/392

I would be in favor of this. @oxinabox if you have no objections I'd like to get this PR up to date and merge it?

I have no objections and if you are infavor of this then go ahead.


can unselect "Supports prompt caching" with Claude models ?

but can unselect "Supports prompt caching" with Claude models ?
Or add Custom name models with "Does not support prompt caching", just likes "GCP Vertex AI"

Originally posted by @edisonzf2020 in https://github.com/saoudrizwan/claude-dev/issues/243#issuecomment-2360051554

Oh are you using an API that doesn't support prompt caching? Interesting, I hadn't realized this was a problem. Do you want that removed bc it shows up as "Cache: 0 -> 0" the whole task?
I'm sorry but I don't think I'll add another checkbox just to uncheck prompt caching, it could be very confusing to most users.


Deprecate ubuntu 18.04

I’m thinking we should focus on the last two LTS - I wouldn’t recommend anyone to use 18.04 still at this point. Thoughts @davidbeckingsale ?

Sounds good to me!


Testing fixes for time scale

Simply injects moment.js into the testing context before chart.js get's hooked in.  Fixes a few typos (just beautification) in the testing, adds a new test to make sure that moment.js is present when testing, and now everything passes but two linear scale drawings.  Not sure why, but this is great.


fix(api): do not clone the value of node when mapping

Bug
const chart = new Chart({});
const date = new Date();
chart.grid().data([{ date }]);

// Expected
chart.data(); // [{ date }]

// Received
chart.data(); // [{ date: {} }]

Reason
To make the chart options immutable, it will use the clone of @antv/util every time the options change. But clone fail to clone Date object.
import { clone } from '@antv/util';

const date = new Date();
clone({date}); // { date: {} }

Solution
Remove the clone operation. It is unnecessary to mark the options immutable because it makes no sense to clone data every time.

建议直接使用 lodash 方法。


Integrated dida365 login

Hello, I am a user from China and I really like the plugin you made. But TickTick has an independent app in China called dida365. Here is the API document for dida365. It looks like same with TickTick. I would like to know if it is possible to add an option to log in using the dida365 service in the credentials.

Thanks for your kind words about the plugin - I am glad to hear that you find it useful! I appreciate your suggestion to integrate Dida365. I've never heard of it, is it really popular in China? At first I thought it was a clone, but it seems to be legit?
I've taken a look at the API documentation for Dida365, and it does indeed have some similarities to the TickTick API.
Before proceeding with the implementation, I would like to delve deeper into the specifics of the Dida365 API, particularly around authentication processes and any potential differences from the TickTick API.
At first glance, I think I would rather code another node than implement the credentials because of the different API URL endpoints. I will definitely look into this more next week if I can successfully register and try it out.

Yes, ticktick is actually a product from Chinese team. In China, it is called dida356, and ticktick is launched for overseas users. Chinese users will choose dida365. They are essentially the same product, with only some minor functional differences due to different user groups. I hope you can register dida365 and test it. It's logic is exactly the same as ticktick.

I released the package! It works locally, but I haven't tested it on my server yet. Let me know if there are any problems and I will try to help. ✌🏽 n8n-nodes-dida

It works well. Thank you for your contribution！


Internal Server Error when loaded

So I installed the Auto Organize plug-in. Every time I go to it's page, I get an Internal Server Error on the Activity Log. The other pages appear to be fine.
 [2019-02-22 01:03:31.547 -05:00] [ERR] Error processing request
System.NullReferenceException: Object reference not set to an instance of an object.
   at Emby.AutoOrganize.Core.FileOrganizationService.GetResults(FileOrganizationResultQuery query)
   at Emby.AutoOrganize.Api.FileOrganizationService.Get(GetFileOrganizationActivity request)
   at Emby.Server.Implementations.Services.ServiceExecGeneral.Execute(Type serviceType, IRequest request, Object instance, Object requestDto, String requestName) in /jellyfin/Emby.Server.Implementations/Services/ServiceExec.cs:line 88
   at Emby.Server.Implementations.Services.ServiceController.Execute(HttpListenerHost appHost, Object requestDto, IRequest req) in /jellyfin/Emby.Server.Implementations/Services/ServiceController.cs:line 177
   at Emby.Server.Implementations.Services.ServiceHandler.ProcessRequestAsync(HttpListenerHost appHost, IRequest httpReq, IResponse httpRes, ILogger logger, String operationName, CancellationToken cancellationToken) in /jellyfin/Emby.Server.Implementations/Services/ServiceHandler.cs:line 95
   at Emby.Server.Implementations.HttpServer.HttpListenerHost.RequestHandler(IHttpRequest httpReq, String urlString, String host, String localPath, CancellationToken cancellationToken) in /jellyfin/Emby.Server.Implementations/HttpServer/HttpListenerHost.cs:line 608

To be clear for anyone that sees this - you can click “Got It” on the message that pops up, and continue.
I haven’t tested the functions themselves, but the rest of the UI seems to work.

I confirm the same error and it should be treated as serious.

This is fixed throug #10


[Docs] Create Newcomer's meeting attendance folder for the week of 09/23/2024

Current State
As a project, we track attendance to the weekly Newcomers meeting under the _meetings directory. It’s important that each newcomer both feel at ease in the community, and also, comfortable with the process of contributing (in this particular case, using git).
Desired State
Each meeting attendee creates attendance record (a file with their name in the filename or their name in the content of the file) in the _meeting directory. The format of this file doesn't matter. What's important is that the attendee get into the groove of git-based contribution.
Implementation
Create a new directory under the _meetings directory, entitled "week-of-<mm/dd/yyyy>", replacing mm/dd/yyyy the date for the start of the week. This new, empty directory will serve as the landing spot for attendance records.
Acceptance Test
A new directory is present and is NOT listed as dd/mm/yyyy, but as mm/dd/yyyy.

Contributor Guides and Handbook

📚 Instructions for contributing to documentation

Meshery documentation site and source

🛠 Meshery Build & Release Strategy
🎨 Wireframes and designs for Meshery UI in Figma (open invite)
🙋🏾🙋🏼 Questions: Discussion Forum and Community Slack

can i work on this issue ?

@hargunkaur286 can i work on this issue . can you assign me this issue ?

@hargunkaur286 can i work on this issue ?

Please go ahead @Tharanishwaran

@Tharanishwaran I see you've been working on other items as well.
Let's reserve this for first-timers.

@vishalvivekm  I understand and fully respect reserving this issue for first-timers. I'll step aside to let them take it on.

@vishalvivekm  I understand and fully respect reserving this issue for first-timers. I'll step aside to let them take it on.

@vishalvivekm I understand and fully respect reserving this issue for first-timers. I'll step aside to let them take it on.

Thank you for your understanding @Tharanishwaran

@hargunkaur286 @vishalvivekm can i try this issue ?

@batmnnn May I know if you have the project setup locally?

@hargunkaur286 no but I can set it up by evening (maybe with a little help)

Have you referred the Meshery contribution guide? Specifically this page for instructions on setting up the repository?

Okay I'll do it asap, @hargunkaur286

can I work on this issue @hargunkaur286 ?

hi. i am first timer, can i work on this @hargunkaur286 ?

09-23-2024 folder was already present so i added for the upcoming week 09-30-2024


fix(engine): fixes known pairing request flow, use pairing.create() over pre-pairing API manual creation

Description

Fixes #60
Fixes #61

How Has This Been Tested?

Unit tests
Dogfooding (TBD)

Due Dilligence

[ ] Breaking change
[ ] Requires a documentation update
[ ] Requires a e2e/integration test update

Looking into why the canary flow fails. Seems to also fail on main due to pairing_ping events not resolving as expected, so not directly related to these changes.


Enable unathenticated docker pull/run registry.cncf.ci/repo/proj:tag

Neither docker run or docker login work against registery.cncf.ci:
docker pull:
$ docker run registry.cncf.ci/coredns/coredns:c737c741
Unable to find image 'registry.cncf.ci/coredns/coredns:c737c741' locally
docker: Error response from daemon: Get https://registry.cncf.ci/v2/coredns/coredns/manifests/c737c741: Get https://gitlab.cncf.ci/jwt/auth?scope=repository%3Acoredns%2Fcoredns%3Apull&service=container_registry: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers).
See 'docker run --help'.

We get the same error trying to docker login:
$ docker login registry.cncf.ci
Username: hh
Password:
Error response from daemon: Get https://registry.cncf.ci/v2/: Get https://gitlab.cncf.ci/jwt/auth?account=hh&client_id=docker&offline_token=true&service=container_registry: net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers) (Client.Timeout exceeded while awaiting headers)

It works against docker.ii.org.nz, which is running the same release.
We'll take a look into this next week.

Restarted gitlab, seems to have cleared the issue.
docker pull registry.cncf.ci/coredns/coredns:c737c741
c737c741: Pulling from coredns/coredns
cfc728c1c558: Already exists
1997f641ed13: Already exists
c1ea3238c35e: Already exists
Digest: sha256:2bece802070e78c7b13649cbebefb9a7f5df8669508143807fdba75fe10bc84e
Status: Downloaded newer image for registry.cncf.ci/coredns/coredns:c737c741


feat: FIFS-174 Wrap/Unwrap

Wrap / Unwrap NEAR feature

@SerDorosh we won't block this PR unless it introduces serious bugs but @gutsyphilip will leave a bunch of comments just for best practices

Thanks!
Done.


Debug Assertion Failure 'Expression: vector subscript out of range'"

Environment
Windows build number: Microsoft Windows [Version 10.0.18908.1000]
Windows Terminal version (if applicable): 71e19cd82528d66a0a7867cbed85990cfc1685f1

Steps to reproduce
launch Terminal
create cmd tab
close PowerShell tab via x on tab
type word^W into cmd
Expected behavior
Close the terminal (really, I would like readine completion)
Actual behavior
Invalid vector access.
Seems that the _GetFocusedTabIndex is returning the index unadjusted for the closing of the tab.  I think that _RemoveTabViewItem is not readjusting the index. The shared_ptr is constructed by indexing into _tabs by _GetFocusedTabIndex.  That calculates the index by _tabView.SelectedIndex  The _RemoveTabViewItem does not update the index.  I can not seem to track down where the implementation for the tab bar renderer is handled (I suspect due to the Xaml bits).  Some pointers as to where to start digging would be appreciated.

This might need some deep dive debugging to find out exactly what's happening here.
You're correct that the tab bar is out of our control - the code is from the Microsoft.UI.Xaml nuget package.
It's entirely possible that there's a bug in the tab bar implementation, because we're using a super early prerelease version. I think it's more likely we're moving the focus ourselves incorrectly.

The one other thing that I noticed that took some time was that the process is not immediately terminated but continues to execute in the background (I was attaching to the wrong conhost!).  I can try to see if I can trace where the focus is adjusted - although pointers would certainly be welcome :-)


Retry when topic leader not available

Description
Fixes #15,.
Quick checks:

[x] I have followed the Code Guidelines.
[x] There is no other pull request for the same update/change.
[x] I have written unit tests.
[x] I have made sure that the PR is of reasonable size and can be easily reviewed.

Love the retry logic! 🙌🏾 Thank you so much @hariso sparkles

You're welcome, Samir!


aws-migration

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


Fix Setting default parameters link

Closing this PR as the markdown gets build and transformed.
The content is not intended to be read on github or regular markdown.
The link is correct here:
https://console.ng.bluemix.net/docs/openwhisk/openwhisk_actions.html#openwhisk_binding_actions

The page on bluemix only shows a spinner. Perhaps the converter needs to convert .md to html links on bluemix. That way in case the bluemix site only shows a spinner as for this page you can fallback to github like  I did and click the links there.


[BEAM-8889]add experiment flag use_grpc_for_gcs

Previously, using grpc channel for GCS was controlled by an API change.
Changing that to an experiment, so that there is no need to introduce an API change.
That API change is not in use by anone yet because the underlying change in GCS library to use grpc is not yet public and hence there is no one yet using the new API.

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

[ ] Choose reviewer(s) and mention them in a comment (R: @username).
[ ] Format the pull request title like [BEAM-XXX] Fixes bug in ApproximateQuantiles, where you replace BEAM-XXX with the appropriate JIRA issue, if applicable. This will automatically link the pull request to the issue.
[ ] Update CHANGES.md with noteworthy changes.
[ ] If this contribution is large, please file an Apache Individual Contributor License Agreement.

See the Contributor Guide for more tips on how to make review process smoother.

Retest this please

LGTM. Thanks.

Run Java PreCommit

Run Java PreCommit

Run Java PreCommit

Run Java PreCommit

Run Java PreCommit

It looks like spotbugs is failing in the Java PreCommit with:
Dead store to gcsOptions in org.apache.beam.sdk.extensions.gcp.util.GcsUtil$GcsUtilFactory.create(PipelineOptions, Storage, HttpRequestInitializer, ExecutorService, Integer)
Bug type DLS_DEAD_LOCAL_STORE (click for details)
In class org.apache.beam.sdk.extensions.gcp.util.GcsUtil$GcsUtilFactory
In method org.apache.beam.sdk.extensions.gcp.util.GcsUtil$GcsUtilFactory.create(PipelineOptions, Storage, HttpRequestInitializer, ExecutorService, Integer)
Local variable named gcsOptions
At GcsUtil.java:[line 115]

That is a real problem.
unused variable "gcsOptions"
Thanks, Luke.
could you please issue "Run Java PreCommit" again.
I am trying to understand

why local build didn't show this error when spotbugs ran on it.
why didn't I see this error on github you saw. I should have. I wonder
if I didn't look in the right place. not happy  with myself

On Tue, Mar 31, 2020 at 4:50 PM Lukasz Cwik<EMAIL_ADDRESS>wrote:

It looks like spotbugs is failing in the Java PreCommit with:
Dead store to gcsOptions in org.apache.beam.sdk.extensions.gcp.util.GcsUtil$GcsUtilFactory.create(PipelineOptions, Storage, HttpRequestInitializer, ExecutorService, Integer)
Bug type DLS_DEAD_LOCAL_STORE (click for details)
In class org.apache.beam.sdk.extensions.gcp.util.GcsUtil$GcsUtilFactory
In method org.apache.beam.sdk.extensions.gcp.util.GcsUtil$GcsUtilFactory.create(PipelineOptions, Storage, HttpRequestInitializer, ExecutorService, Integer)
Local variable named gcsOptions
At GcsUtil.java:[line 115]
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/beam/pull/11183#issuecomment-606946300, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ALRAMQU6NKEJDI3ZY46PCHTRKJ6T3ANCNFSM4LQRRJQQ
.

retest this please

Did you run check task of the gradle project to cover spotbugs/checkstyle/unit tests/... since test only covers testing.
Also, I had to run the command locally after checking out your PR since the full error log in Jenkins points to a local file on the Jenkins host which isn't accessible.

On Tue, Mar 31, 2020 at 7:09 PM Lukasz Cwik<EMAIL_ADDRESS>wrote:

Did you run check task of the gradle project to cover
spotbugs/checkstyle/unit tests/... since test only covers testing.

I didn't.
that explains the step I am missing.
thanks

Also, I had to run the command locally after checking out your PR since
the full error log in Jenkins points to a local file on the Jenkins host
which isn't accessible.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/beam/pull/11183#issuecomment-606984664, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ALRAMQQEUEJMWXLAJ5U2JHTRKKO55ANCNFSM4LQRRJQQ
.

Run JavaPortabilityApi PreCommit

Run JavaPortabilityApi PreCommit

Run JavaPortabilityApi PreCommit

New failure seems to be unrelated.

Run JavaPortabilityApi PreCommit

Run JavaPortabilityApi PreCommit


feat: add SCRIPT SHOW, CLIENT CAPA, and CLUSTER SLOT-STATS commands

This PR shows how to generate new Valkey commands and new command options by adding them into the commands.json and running go generate.

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

Project coverage is 89.45%. Comparing base (f41a9e9) to head (020b06e).

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #13      +/-   ##
==========================================
- Coverage   89.62%   89.45%   -0.18%
==========================================
  Files          87       87
  Lines       36949    36307     -642
==========================================
- Hits        33117    32478     -639
+ Misses       3648     3643       -5
- Partials      184      186       +2

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

Merged in v1.0.46.


Switch from LightGraphs to Graphs

Codecov Report
Patch coverage has no change and project coverage change: -0.08 :warning:

Comparison is base (03e86ff) 93.61% compared to head (650a835) 93.54%.

Additional details and impacted files
@@            Coverage Diff             @@
##             main      #85      +/-   ##
==========================================
- Coverage   93.61%   93.54%   -0.08%
==========================================
  Files          23       22       -1
  Lines        1582     1564      -18
==========================================
- Hits         1481     1463      -18
  Misses        101      101

Impacted Files
Coverage Δ

src/graph.jl
95.34% <ø> (ø)

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

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Assurance case 4

Updated image, added evidence

Overall very well written and documented. After the comments are fixed feel free to merge to master.


enable_service_tags

check staus of service tags tests

Current coverage is 79.61% (diff: 100%)

Merging #166 into master will not change coverage

@@             master       #166   diff @@
==========================================
  Files            58         58
  Lines          2242       2242
  Methods           0          0
  Messages          0          0
  Branches        290        290
==========================================
  Hits           1785       1785
  Misses          326        326
  Partials        131        131

Powered by Codecov. Last update 69473de...51f70a0

@antonkharenko i posponed the work on this branch so you can see cluster test fails even before services tests started

It seems to me that this pull request is not relevant anymore so I am closing it.


On Hero Section cursor Image ,previous image some part showing

Hey @Alok5102R  I want make this correct.

Please proceed with this @VirendrKumarYadav

I had Raised PR @Alok5102R  please review it and merged it.


Exclude swarm when "all" dialog options is on

Is your feature request related to a problem?
no
Describe the solution you'd like
hi, do you think you guys could add an option to the "show all mythic dialog options" that the dialogs wouldn't show the swarm option? it is so off putting to see in almost every dialog that "do you wanna eat her?", i hate the swarm path and I actually stopped playing the game it became such an issue during the last act,
you have an option to eat your dialog partner in almost every dialog.... seriously? super sad
Describe alternatives you've considered
No response
Additional context
No response

Unlikely to be added. Simply ignore the dialog, or turn off the option.
However, if you are willing to do it yourself, we would gladly accept a PR on it.


Automated Rail Transportation gated behind Railways 2, should probably be Railways 1

Mod source
Github
Which mod are you having an issue with?

[ ] pyalienlife
[ ] pyalternativeenergy
[ ] pycoalprocessing
[ ] pyfusionenergy
[ ] pyhightech
[X] pyindustry
[ ] pypetroleumhandling
[ ] pypostprocessing
[ ] pyrawores

Operating system

=Windows 10

What kind of issue is this?

[ ] Compatibility
[ ] Locale (names, descriptions, unknown keys)
[ ] Graphical
[ ] Crash
[ ] Progression
[ ] Balance
[X] Pypostprocessing failure
[ ] Other

What is the problem?
Let me reopen the issue #20 and #76.
I reproduced this issue with pyindustry (GitHub latest version) and Automatic_Train_Painter_1.1.4, where I have checked that this issue is gone if I remove
table.insert(data.raw["technology"]["automated-rail-transportation"].effects, {type = "unlock-recipe",recipe = "manual-color-module"})

in Automatic_Train_Painter_1.1.4/prototypes/technology/module.lua.
This seems to be caused by the autotech procedure in pypostprocess. At AUTOTECH START, the technology is dumped as
{type="technology",
 name="automated-rail-transportation",
 effects={{type="unlock-recipe",recipe="train-stop"},
          {type="unlock-recipe",recipe="manual-color-module"},
          {type="unlock-recipe",recipe="fuel-train-stop"}},
 unit={count=75,ingredients={{"automation-science-pack",1},
                             {"py-science-pack-1",1}},time=30},
 prerequisites={"railway-mk01"}
}

but at AUTOTECH END it is
{type="technology",
 name="automated-rail-transportation",
 effects={{type="unlock-recipe",recipe="train-stop"},
          {type="unlock-recipe",recipe="manual-color-module"},
          {type="unlock-recipe",recipe="fuel-train-stop"}},
 unit={count=30000,ingredients={{type="item",name="automation-science-pack",amount=2},
                                {type="item",name="py-science-pack-1",amount=1}},time=45},
 prerequisites={"railway-mk02"}
}

I will dig it a bit, hoping to write you a patch.
Steps to reproduce
No response
Additional context
No response
Log file
factorio-current.log

Just check the train painter mod setting that adds a small grid to each train. Otherwise pypp wants a train with a grid in which to place the manual paint module that gets unlocked with the same tech

I got it. If a technology unlocks an item to be set in equipment-grid, pypp delays its availability after some technology that unlocks a vehicle/armor with equipment grid.
I am however not sure the purpose of this treatment, firstly because I cannot find the necessity of it while it results in this (repeated) bug-report from me, but also the solution can be non-unique, i.e., multiple technologies might unlock vehicles with grid, and then pypp may delay the technology after either of them.

That's actually a good point considering you'd expect pypp to place it behind railways 2 which also unlocks a loco with a grid

Fixed for v0.2.1


Surprising behavior on Windows with drive roots in the middle of a path

Consider the following (tested with v1.3.1 tag):
let fp = FilePath("Sources/E:\\source")
print(fp.isAbsolute) // false
print(fp.isRelative) // true
print(fp.root) // nil
print(Array(fp.components)) // ["Sources", "E:", "source"]

print(FilePath("Sources").appending(fp.components)) // SystemPackage/FilePathParsing.swift:351: Assertion failed
print(FilePath("Sources").pushing(fp)) // Sources\Sources\E:\source

print(FilePath("Sources").appending(FilePath.Component("C:"))) // SystemPackage/FilePathString.swift:299: Fatal error: FilePath.Component must be created from exactly one non-root component
print(FilePath("Sources").appending("C:")) // Sources

It's not clear to me that some of these assertions are expected, or even how a seemingly bogus path like Sources/E:\\source should be treated by the APIs. Should the FilePath constructor have asserted right away on this path if containing prohibited characters per https://learn.microsoft.com/en-us/windows/win32/fileio/naming-a-file#naming-conventions? Should there be an alternative validating constructor that returns nil or throws in this case?

Trapping in FilePath.appending does not seem right to me. Trapping in an assertion (as opposed to precondition) failure is definitely incorrect -- this operation either needs to succeed, or it must produce a guaranteed runtime error.
If Source/E:\\sources is not a valid path on Windows, then I think FilePath("Sources/E:\\source") should not successfully create a file path. FilePath.init(_: String) is a non-failable initializer, so the only way to report an error is to trap. If that isn't acceptable, then we have to make a choice between deprecating it, or coming up (and clearly documenting!) a mechanism to turn it into a valid path.
For what it's worth, Foo\0Bar is clearly an invalid path on UNIX-compatible systems, but FilePath("Foo\0Bar") appears to accept it, silently truncating the input string before the NUL character. If we take this (terrible) precedent as the intended behavior, then one potential solution on Windows would be to filter out inappropriate characters or to replace them with some bogus substitute.
The state of FilePath makes me deeply unhappy.


Add zsh-autopair module

Love this plugin, until #52 is done let's have it available in prezto.

@belak has started merging at the original! Feel free to reopen there if you'd like.


Question: Does GPU query performance counter method support WDDM 1.3

On win10 PC(version > WINDOWS_10_RS3), I paly a video first;

I set EnableGpuPerformanceCounters as 1, but GPU usage column is zero;
I find driver version is WDDM 1.3;
Besides, I check GPU Process Memory counter in performance monitor, but I fail to find result for my target exe (target exe pid is not find), do you know the possible reason?

Does GPU query performance counter method support WDDM 1.3

It supports all versions from 1.1

I fail to find result for my target exe (target exe pid is not find), do you know the possible reason?

The process is likely going to use raster operations via the CPU instead of the GPU when the version is 1.3... In that case the CPU utilization will instead include the GPU utilization.


Add variableHeight argument to CarouselProvider that disables the ratio

What:
Add a variableHeight attribute to CarouselProvider.
If set to true, the Slider will not adhere to the ratio being set with naturalSlideHeight and naturalSlideWidth.
The Slider will have the height of the biggest Slide.

Why:
So you can use non scaling context (like text on the slide).
Without these changes, the Slide would be either too small or too big (and just clip the Slide in half).
This somewhat addresses the issues in the following issues.  This does not however change the hide of the Slider depending on the current shown slide, which might be another cool addition.

https://github.com/express-labs/pure-react-carousel/issues/23
https://github.com/express-labs/pure-react-carousel/issues/225
https://github.com/express-labs/pure-react-carousel/issues/176
https://github.com/express-labs/pure-react-carousel/issues/154

How:
We store variableHeight in the store in CarouselProvider.
Each Slide then sets styles depending on that.
The styles Reset the position, height and padding-bottom css attributes, which allows the Slider to be as heigh as the biggest Slide, therefore dynamicaly scalling with the content.

Checklist:

[x] Documentation added/updated
[x] Typescript definitions updated
[x] Tests added and passing
[x] Ready to be merged

As this is my first change in the library, it might be wise to do a bit further testing, as I might have missed some egde cases.
But it feels very good, and all test pass.

Workaround
This can be archived "from the outside" by using these css rules:
.slider li {
    position: unset !important;
    height: unset !important;
    padding-bottom: unset !important;
}
.slider li .carousel__inner-slide {
    position: unset;
}

Generally, if it can be handled via CSS, then I'm against adding new props to the components.  But this seems to be a recurring theme with the height so I relent.
I have some requests though...
Can you add an example to our list of live demos?  I want to download the branch and see the demo so I can see how this affects a vertical carousel?
If one slide is 1000px in height, does that mean all slides are 1000px in height or are there "gaps" where the background will bleed through.  Have you looked at flex-box instead.  It will make all slides as tall as the tallest slide.
Is there an option for "variable width" on vertical carousels?
I might want to change the name to useIntrinsicDimension or intrinsicAxisSize or something more descriptive because "variable height" to me sounds like responsive height, and the carousel is currently responsive as is.  Might be confusing to others.  I'm getting the Axis concept from flex-box.

@mrbinky3000
I will add a Demo for sure.
Currently they do not flex to all become the same height.
Instead there is a gap beneath all smaller slides, that fills the missing height.
I am unsure what the right solution here would be regarding stretching all of the slides to be the same height, both (stretching and not-stretching) seem to make sense at first thought.
I haven't looked into the width case, so currently there is no such option, it shouldn't be too hard to add though.
Open for renaming, haven't put too much thought into that.
doNotEnforceRatio might be good candidate as well, as this is essentially what this does.

Looking at the vertical orientation:
The width of the whole slider currently scales to 100% of the container, in both vertical and horizontal arrangement. Based on that width, all the other sizes are calculated.
But to have the same behavior in vertical as in horizontal mode (with the new flag enabled), the height should be the size set from outside and all the rest depending on it, so the width then can become dependent on the widest slide.

Can you add the error for using this new flag in vertical mode?
Also can we change the name of the option to "isIntrinsicHeight".  We use "is[blank]" for booleans.  Also the word "use" implies a hook.
Make those changes and I will approve.

Let me know if the Error message is ok the way it is, or if you want to have something added :)

It's all good, thanks!

Thanks for this!
When is it going to be released?

when release ? :) thanks for this package

@allcontributors please add @reckter for code

:tada: This PR is included in version 1.26.0 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Change are really breakin.. for 0.8.0

I get
thread '::test_find_one' panicked at 'called `Result::unwrap()` on an `Err` value: Error(LIB_NULL_VALUE(CASS_ERROR_LIB_NULL_VALUE), State { next_error: None, backtrace: None })', ../src/libcore/result.rs:837

https://github.com/tupshin/cassandra-rs/commit/2c57a8216e26cb7e16d46c2a718b171d5b1d0286
This is related to to_result("").unwrap().into()

how about introducing tests and CI like Travis ?

Apologies. Pin to 0.7 for now. I'll look into this over the next day or two


Pydantic 1.6 does not validate nested models when using a default_factory

Bug
Output of python -c "import pydantic.utils; print(pydantic.utils.version_info())":
             pydantic version: 1.6
            pydantic compiled: True
                 install path: /usr/local/Caskroom/miniconda/base/envs/server/lib/python3.8/site-packages/pydantic
               python version: 3.8.3 (default, Jul  2 2020, 11:26:31)  [Clang 10.0.0 ]
                     platform: macOS-10.15.5-x86_64-i386-64bit
     optional deps. installed: ['typing-extensions']

I'm aware that validation does not apply to default values, but it appears that it is no longer applied to user-provided values that have a default factory value, either. If this is expected, I'm not sure if I saw it in the documentation or changelog.
from pydantic import BaseModel, Field
from typing import List

class Child(BaseModel):
    x: int

class Parent(BaseModel):
    children: List[Child] = Field(default_factory=list)

p = Parent(children=[{'x':1}, {'y':2}])

In Pydantic 1.5.1, an error is raised because the second child fails to validate (it is missing required value 'x')
In Pydantic 1.6, the Parent object is instantiated successfully and contains two dicts:
print(p)
# children=[{'x': 1}, {'y': 2}]

To avoid this and recover the expected behavior, validate_all must be set on the Parent class. However, since I'm providing the child value, I'm surprised that I had to ask for it to be validated.

This is definitely a bug, probably caused by the changes in #1691, specifically removing alwasy=True from list and set child fields.
That it turn was required to solve a problem that came up in #1627.
I see that this is urgent, but I'm flat out with work, will try to fix when I can. @PrettyWood do you have any bright ideas how to solve this without a different regeression?

Perhaps this is a consequence of the issue described in #1566 (and docs update #1592)? Does applying nested models implicitly set each_item=True with a default validator?

Ah sorry I see we just crossed messages. Ok, bittersweet glad to hear it :) I'll review the issues you linked and see what we can do in the meantime. Thank you!

Hmmm I see I'm sorry for that. I'll have a look as soon as I can (probably on monday in the train).

Edit: the bug was way easier than I thought as it was only due to #1504. If any other has the same issue, do not hesitate to try out the fix to make sure there is no further regression.

Hey everybody. I just picked up the same example from 1st comment, but without list:
from pydantic import BaseModel, Field
from typing import List

class Child(BaseModel):
    x: int

class Parent(BaseModel):
    child: Child

p = Parent(child={'y':2})

p.child
<class '__main__.Child'>

p.child.x
Traceback (most recent call last):
  File "<input>", line 1, in <module>
AttributeError: type object 'Child' has no attribute 'x'

p.child.y
Traceback (most recent call last):
  File "<input>", line 1, in <module>
AttributeError: type object 'Child' has no attribute 'y'

Is it expected behaviour or is it a bug?

This bug relates to pydantic 1.6, please upgrade to the newest version of pydantic.


Application to reproduce the experimental results of the industrial dataset

Hello, I am very interested in your work, can you provide the download link of industrial dataset？If possible, please send it to my email<EMAIL_ADDRESS>or reply to me directly.

Thank you for your interest in our paper! As the industrial dataset is real large-scale data from Alibaba's production environment, based on the company's data privacy policy, we are unable to make the industrial data public. The other public datasets involved in the paper are all accessible in Google Drive. I hope these can help your reproduction.

Okay, thank you for your reply.


Need better example and links for TargetApplicationPackageFamilyName on LauncherOptions

The JS example just sets the property to itself.  It should have an example package family name so that a developer knows they have something that looks right in their own app.  There should also be a link to info about what the Application Package Family Name is and how to get one for an app.

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

ID: 2ff12cee-d588-9e46-2d5e-844dbe6f711a
Version Independent ID: 2f14a1b3-c1f5-6dbd-4675-aceff296cfa0
Content: LauncherOptions.TargetApplicationPackageFamilyName Property (Windows.System) - UWP app developer
Content Source: https://cpubwin.visualstudio.com/DefaultCollection/windows-uwp/_git/winrt-api-build?path=%2fwinrt-api-build%2fwindows.system.launcheroptions.yml&version=GBlive&_a=contents
Service: unspecified
GitHub Login: @wdg-dev-content
Microsoft Alias: wdg-dev-content

I've made some changes to the article, they should show up shortly.


add e2e runner (go variant)

What this PR does / why we need it:
add e2e runner (go variant)
Release note:

add e2e runner (go variant)

WIP status closed, ready for review.

@OlegLoewen @dguendisch maybe we should move the e2e tests to a folder outside of <root>/test.
I think <root>/integration-tests/e2e could be a good directory as we currently mix the testmachinery tests and k8s e2e test.
This would be clearer and we are able to add more tests that are testing gardener/kubernetes not the testmachinery there.

@OlegLoewen @dguendisch maybe we should move the e2e tests to a folder outside of <root>/test.
I think <root>/integration-tests/e2e could be a good directory as we currently mix the testmachinery tests and k8s e2e test.
This would be clearer and we are able to add more tests that are testing gardener/kubernetes not the testmachinery there.

Good idea.


[Application] Training Resnet kotlin code for Android

This PR includes the kotlin android implemetation to train Resnet18 in
Applications.
Changes proposed in this PR:

Added TOC generator for README.md

Resolves:
Self evaluation:

Build test:	 [X]Passed [ ]Failed [ ]Skipped
Run test:	 [X]Passed [ ]Failed [ ]Skipped

Signed-off-by: jijoong.moon<EMAIL_ADDRESS>

:memo: TAOS-CI Version: 1.5.20200925. Thank you for submitting PR #2111. Please a submit 1commit/1PR (one commit per one PR) policy to get comments quickly from reviewers. Your PR must pass all verificiation processes of cibot before starting a review process from reviewers. If you are new member to join this project, please read manuals in documentation folder and wiki page. In order to monitor a progress status of your PR in more detail, visit http://ci.nnstreamer.ai/.

:octocat: cibot: @jijoongmoon, Applications/Android/kotlin/app/src/main/jni/lodepng.h does not include Doxygen tags such as @file @brief @author @bug. You must include the Doxygen tags in the source code. Please refer to a Doxygen manual at http://github.com/nnstreamer/TAOS-CI/blob/main/ci/doc/doxygen-documentation.md

:octocat: cibot: @jijoongmoon, Applications/Android/kotlin/app/src/main/jni/lodepng.cpp includes bug(s). Please fix incorrect coding constructs in your commit before entering a review process.

:octocat: cibot: @jijoongmoon, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2111-202302141119590.30047202110291-3b26f34fa3b0e6a705a89411950749347261f3cb/.

:octocat: cibot: @jijoongmoon, Applications/Android/kotlin/app/src/main/jni/lodepng.h does not include Doxygen tags such as @file @brief @author @bug. You must include the Doxygen tags in the source code. Please refer to a Doxygen manual at http://github.com/nnstreamer/TAOS-CI/blob/main/ci/doc/doxygen-documentation.md

:octocat: cibot: @jijoongmoon, Applications/Android/kotlin/app/src/main/jni/lodepng.cpp includes bug(s). Please fix incorrect coding constructs in your commit before entering a review process.

:octocat: cibot: @jijoongmoon, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2111-202302141348220.20315909385681-6d16f348eab65eba9d3b6e479b3c4f295b9d2beb/.

:octocat: cibot: @jijoongmoon, Applications/Android/kotlin/app/src/main/jni/lodepng.h does not include Doxygen tags such as @file @brief @author @bug. You must include the Doxygen tags in the source code. Please refer to a Doxygen manual at http://github.com/nnstreamer/TAOS-CI/blob/main/ci/doc/doxygen-documentation.md

:octocat: cibot: @jijoongmoon, Applications/Android/kotlin/app/src/main/jni/lodepng.cpp includes bug(s). Please fix incorrect coding constructs in your commit before entering a review process.

:octocat: cibot: @jijoongmoon, A builder checker could not be completed because one of the checkers is not completed. In order to find out a reason, please go to http://ci.nnstreamer.ai/nntrainer/ci/repo-workers/pr-checker/2111-202302211436510.42504405975342-6d16f348eab65eba9d3b6e479b3c4f295b9d2beb/.

:octocat: cibot: @jijoongmoon, Applications/Android/kotlin/app/src/main/jni/lodepng.h does not include Doxygen tags such as @file @brief @author @bug. You must include the Doxygen tags in the source code. Please refer to a Doxygen manual at http://github.com/nnstreamer/TAOS-CI/blob/main/ci/doc/doxygen-documentation.md

:octocat: cibot: @jijoongmoon, Applications/Android/kotlin/app/src/main/jni/lodepng.cpp includes bug(s). Please fix incorrect coding constructs in your commit before entering a review process.


Remove secondary files

Hi, here another pull request.
This one is just to remove secondary files from the repository.
Kind regards
Jan

Ok, removed .idea and .DS_Store.


Fix some docstrings and examples. No new release.

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

Project coverage is 86.16%. Comparing base (893bbb0) to head (8eb0db3).
Report is 9 commits behind head on master.

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##           master      #34   +/-   ##
=======================================
  Coverage   86.16%   86.16%
=======================================
  Files          21       21
  Lines         448      448
=======================================
  Hits          386      386
  Misses         62       62

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


Neka-Develop the listing creation form

This issue should be priority so that functionality can be added  to this  issue


Fail when dist doesn't exist

Given how manual glob expansion was implemented (https://github.com/gorilla-co/s3pypi/pull/90), the program stopped failing when specifying invalid dist paths. For example, when executing s3pypi -b my_bucket paht/with/a/typo, the program does nothing and returns exit code 0. This is not desirable since it's impossible to know whether everything went OK or not when using the tool in automated scripts.
This PR makes it work as follows:

If any of the specified dists is invalid, the program does nothing and it returns an exit code 1.
For globs, if they can expand to something valid, they're considered valid. E.g. if the glob *_package expands to both valid_package and invalid_package, then it's considered valid and only valid_package is added to the dists list (this is the same as the current behaviour). However, if it only expands to invalid packages or it doesn't expand to anything, then it's invalid.

Excellent! Thank you for fixing this.


mapbox: multilanguage support

We should also be able to get nav instructions in the correct language: https://docs.mapbox.com/api/navigation/directions/#instructions-languages

Seems to do something!

Nice!! I'll make sure our language codes match mapbox. We can also remove main,

@adeebshihadeh I've verified all of our language codes work and mapbox returns localized strings for directions/instructions, however I haven't been able to test the visual aspect of this PR, so I can't guarantee a lot of strings won't go off the screen. If we think that's fine, this is good to merge

Hmm, it should just wrap around, so I think this is fine.


Copy inputs from solpos to linke and vv

Don't do this automatically,  instead add copy button to webpage,  next to submit

closed in 7750734c4657ebeee1949738ad28b6ae8e0d0c97