yfinance should not write to the filesystem unless explicitly instructed by the user

Describe bug
I think yfinance should not write to the filesystem unles instructed by the user. When I use yfinance, I don't expect it to craete databases for caching purposes without being told, it seems to me that that's what everyone using the library would expect.
Caching is a great feature but it should be turned off by default.
if the code is executed in a read-only filesystem that an error will be thrown by the python interpreter. Whether the error is handled internally (thus seamlessly preventing the creation of the caching dir) or by the user, this event should not happen to begin with
import yfiance as yf

symbol= "MSFT"

# tell yf to cache these (tz, ticker, etc...)
df = yf.download(symbol, cache=True)
ticker = yf.download(symbol, cache=True)

Related issues
#1700
Simple code that reproduces your problem
# On a readonly filesystem
import yfinance as yf

symbol = "MSFT"

df =yf.Download(symbol)
ticker = yf.Ticker(symbol)

Debug log
Traceback (most recent call last):
File "/app/main.py", line 1, in
import yfinance as yf
File "/usr/local/lib/python3.11/site-packages/yfinance/init.py", line 23, in
from .ticker import Ticker
File "/usr/local/lib/python3.11/site-packages/yfinance/ticker.py", line 29, in
from .base import TickerBase
File "/usr/local/lib/python3.11/site-packages/yfinance/base.py", line 38, in
from . import utils
File "/usr/local/lib/python3.11/site-packages/yfinance/utils.py", line 991, in
class _KV(_peewee.Model):
File "/usr/local/lib/python3.11/site-packages/yfinance/utils.py", line 995, in _KV
class Meta:
File "/usr/local/lib/python3.11/site-packages/yfinance/utils.py", line 996, in Meta
database = _DBManager.get_database()
^^^^^^^^^^^^^^^^^^^^^^^^^
File "/usr/local/lib/python3.11/site-packages/yfinance/utils.py", line 953, in get_database
cls._initialise()
File "/usr/local/lib/python3.11/site-packages/yfinance/utils.py", line 972, in _initialise
_os.mkdir(cls._cache_dir)
OSError: [Errno 30] Read-only file system: '/root/.cache/py-yfinance'
Bad data proof
No response
yfinance version
0.2.30
Python version
3.11
Operating system
Linux

As a general principle I 100% agree. But here we have to consider load on Yahoo and risk of them blocking/gatekeeping access to everyone. If we assume less load = less risk, then yfinance should try to reduce total load. That timezone cache reduces #requests per history()/download() call by half.

A solution is don't fetch timezone if user provides timestamps or timezone-aware datetimes.

we have to consider load on Yahoo and risk of them blocking/gatekeeping access

This is a great point that I failed to consider.
I suppose a solution for a related issue would be to help users deploying on lambda functions or read-only filesystems (as discussed on issue #1700 and #1702) would be to allow them to pass a dns string to connect to, say a Postgres database and then generate the shema.
since the OSError is thrown as we import yfinance, we should at least handle that differently (maybe generate the tables with the first db statement exectuion).
# db cache is not instantiated
import yfinance as yf

# db cache is instantiated
ticker =  yf.Ticker("MSFT")

#...

# db cache is already instntiated
ticker = yf.Ticker("GOOGL")

As per the DNS string, I could see something like this happening
import yfinance as yf

yf.CacheConfig(my_provider, my_dns_string)

since the OSError is thrown as we import yfinance, we should at least handle that differently

Or fully implement lazy-loading database #1709


feat(system_error_monitor): aggregate control validator diagnostics

Description

add missing control.param.ymal update for https://github.com/autowarefoundation/autoware_launch/pull/509
Tests performed

psim
https://github.com/autowarefoundation/autoware.universe/assets/39142679/726fa0ed-ad44-4fed-aeb6-652394a1f6c2
system_error_monitor.param.yaml
        /autoware/control/autonomous_driving/performance_monitoring/control_validator: { sf_at: "none", lf_at: "warn", spf_at: "error"}

vehicle cmd gate
    use_emergency_handling: true

Effects on system behavior

Not applicable.
Pre-review checklist for the PR author
The PR author must check the checkboxes below when creating the PR.

[x] I've confirmed the contribution guidelines.
[x] The PR follows the pull request guidelines.

In-review checklist for the PR reviewers
The PR reviewers must check the checkboxes below before approval.

[ ] The PR follows the pull request guidelines.

Post-review checklist for the PR author
The PR author must check the checkboxes below before merging.

[ ] There are no open discussions or they are tracked via tickets.

After all checkboxes are checked, anyone who has write access can merge the PR.

@ito-san could you please approve this? :pray:


Improve mask tool

Change behaviour of aspect ratio and y-axis origin icons
Display mask shape using the mask color
Display shape for the pencil tool before drawing anything
Update mask icon

Ready to be merged.
The preview of the mask is part of another PR: https://github.com/silx-kit/silx/pull/332

It seems that following this, the aspect ratio and y-axis origin icons are always present in the PlotWindow toolbar regardless of the value set by the user at instantiation.

Intresting. It would be good to fix it before the release.

Opened issue #344 for this


Redirects from your root domain to www does not work

Before opening, please confirm:

[X] I have checked the custom domains troubleshooting guide.
[X] I have read the guide for submitting bug reports.
[X] I have done my best to include a minimal, self-contained set of instructions for consistently reproducing the issue.

App Id
Let me know if it matters
Region
us-east-1
Step
Domain Redirects
Status
Partial failure
Issue or question
My SEO is getting wrecked because we don't have a functioning domain for https://domain.com.
The https://www version works fine, as well as the http:// and http://www. version, but https:// on its own gets either ERR_CONNECTION_TIMED_OUT or ERR_CONNECTION_REFUSED depending on what configuration of redirect rules I have.
Right now we have the following configuration. I've tried multiple other approaches like removing the root domain from domain management and trying to rely just on redirects, I've also tried using alternative redirect types like 200 (rewrite) and 301 (permanent).
Nothing's working.
Error message
ERR_CONNECTION_TIMED_OUT / ERR_CONNECTION_REFUSED
Additional information

+1 I've got a custom domain and have already migrated DNS to Route53, had the redirect rules set
The problem I face however is DNS_PROBE_FINISHED_NXDOMAIN not timeout
dig +trace shows
......
abcdomain.com.	10800	IN	NS	ns-670.awsdns-19.net.
abcdomain.com.	10800	IN	NS	ns-1927.awsdns-48.co.uk.
abcdomain.com.	10800	IN	NS	ns-1238.awsdns-26.org.
abcdomain.com.	10800	IN	NS	ns-64.awsdns-08.com.
abcdomain.com.	900	IN	SOA	ns-1238.awsdns-26.org. awsdns-hostmaster.amazon.com. 1 7200<PHONE_NUMBER> 86400
any pointers will be appreciated! Thank you! :)

Never mind found a way around and got it working 🤣

Manually create an A record, tick Alias, Route traffic to "Alias to CloudFront distribution"
When clicking the drop down, it didn't show any options so I just manually entered the xxxxxxxxx.cloudfront.net from AWS Amplify Console, Domain management, Actions, View DNS record

Never mind found a way around and got it working 🤣

In Route53, manually create an A record, for the root domain, tick Alias, Route traffic to "Alias to CloudFront distribution"
When clicking the drop down, it didn't show any options so I just manually entered the xxxxxxxxx.cloudfront.net from AWS Amplify Console, Domain management, Actions, View DNS record

I have the domain and DNS set up in GoDaddy - I'm not sure I have access to those features. Have you got any ideas?

Never mind found a way around and got it working 🤣

In Route53, manually create an A record, for the root domain, tick Alias, Route traffic to "Alias to CloudFront distribution"
When clicking the drop down, it didn't show any options so I just manually entered the xxxxxxxxx.cloudfront.net from AWS Amplify Console, Domain management, Actions, View DNS record

I have the domain and DNS set up in GoDaddy - I'm not sure I have access to those features. Have you got any ideas?

I had a domain on GoDaddy too and unfortunately gave up trying to get it working there, so instead migrated the DNS to Route53
In your case, the question is how does your GoDadddy record know what's the IP of your AWS cloudfront is if it's not static, assuming that you don't currently have your IP dynamically mapped?
As far as I know GoDaddy doesn't currently support ANAME record
If you're going to migrate your DNS, just a heads up that your website could be offline for a while, so remember to lower the TTL

Hi @jacobsapps  👋🏽 apologies for the delay. It's suggested in the documentation that you migrate your DNS to Route53 in order to configure your root domain since GoDaddy doesn't support ANAME/ALIAS records. The workaround would be to setup a domain forward in GoDaddy. Please see step 6 of Add a custom domain managed by GoDaddy.

Hi @jacobsapps 👋🏽 apologies for the delay. It's suggested in the documentation that you migrate your DNS to Route53 in order to configure your root domain since GoDaddy doesn't support ANAME/ALIAS records. The workaround would be to setup a domain forward in GoDaddy. Please see step 6 of Add a custom domain managed by GoDaddy.

Even after setting the domain forward in GoDaddy, still facing the same issue. Any workaround would be much appreciated

I am facing the same issue with my DNS.  The domain forwarding section is allowing only HTTP or HTTPS, not both.

Still facing this issue. I have tried all possible options to resolve this including adding a permanent redirect, rewrite etc. Still no luck with getting non-www working on the root domain.

Facing the same issues aswell, domain.com is not being redirected to www.domain.com

Same as everyone else.

Same here

Same problem. Please, send any instructions

I fixed it! My problem was I was using AWS Amplify and didn't add the non-www url to the custom domain list in the amplify console under "Domain Management" like so:

Then it will have problems adding an extra / at the end of the non-www url, which will break paths to any external images/scripts, so to fix that, you add this under "Rewrites and Redirects"

I was facing same issue but found a cure with the help of @lijameshao who has already replied above.Just add @.example.com and choose alias and problem will be solved

This is from the godaddy forum:
@KinaHus   That's correct, the forwarding service is not currently compatible with HTTPS.  As the forwarding service uses a server to do the redirect it would need to be covered by an SSL certificate for your domain name, which isn't possible at this time.
Does anyone know where the idea to use godaddy even came from?

I've noticed this issue recently when the UI and location of functions has changed on the recent AWS Amplify update.
Didn't have this issue before when im setting up my domain in amplify, then recently i got this issue where root domain didnt get automatically redirected to www.
My solution is like this which might help someone so im posting it here.

The 1st record on this image is URL1 which is working fine, URL2 on the other hand is having the issue. after moving URL2 above the 2 records with Target Address: /index.thml then save it will now automatically redirect root domain to www.
Hope this helps someone.

@michaeldino27 This worked for me! thanks!

@michaeldino27 This worked for me! thanks!

Happy to help!

In my case, I had an AAAA record in Route53 that I had to remove.

@michaeldino27 Thanks very much, this works!

@michaeldino27 I tried this and couldn't get it to work.  Clearly it's working for others so I must have something wrong.
May I ask what your "Custom Domains" tab looks like?  And what your relevant entries in Route 53 look like?
I keep getting DNS errors where it can't resolve the host for the root name.
For Amplify devs, maybe you guys could write some sort of trouble shooting tool for this?  Right now we edit this page, hit Save and it says "Updating app: success" then proceeds to not work.

@jpangburn
Have a look here.

Can you also show your Rewrites & Redirects so i can have a look as well?

@michaeldino27  Hmm, that's different!  I don't have that first one.  I wonder if that's the problem.  As it stands, I have the following settings:
Custom domains:

Rewrites and redirects:

Route 53:

I made the change like you showed on your custom domain so it looks like:

In route 53, that added a record:

After this was complete, I can now go to the root URL and under the hood it works like going to www.rooturl.com as there's a 302 redirect, so all the referrers in the HTTP headers show www.  The funny thing was, I tried adding that DNS record manually yesterday because I thought it just needed an A record aliased to cloudfront, but it didn't work despite looking exactly like what Amplify generated.  I think you really need that redirect in Amplify rather than manually putting the A record alias in Route 53, maybe it tells Cloudfront something else we don't see here.
Thank you so much for your help!  Hope my notes here help someone else who screwed their configuration up similar to me haha

@jpangburn yeah i have also tried playing around Route 53 prior discovering the solution.
Glad the solution worked on you!
Just hoping that amplify team would be able to fix this soon, it used to be automatic but now have to extra step to make it work. XD

I've tried it again on a new branch and it did it automatically already! thanks amplify team!


Local dev mode /third_party/*.js NOT FOUND

Hi @aleventhal
Very new to this extension, please forgive me if I missed something obvious.
Followed the "Running from the local file system" section from
https://github.com/google/automation-inspector/blob/master/README.md

Using developer mode from the Chrome extensions page at chrome://extensions, use the load unpacked extension feature, pointing it at the build/extension folder.

Unfortuently getting 404 for /third_party/*.js
(e.g., chrome-extension://enlmgkkaebjkhjbeajabgddgmggdeadf/third_party/jquery.fancytree.table.js)

A quick guess is something wrong with the Gruntfile.js, not sure right now though.
Happy to dig into it sometime late this week(maybe it's just a mistake I made 😅).
And ideas? Thanks!

Closing, not sure why, but did a fresh re-install everything, it worked.
Maybe re-open when someone found the same issue.


feat: Close button added, which can be shown with new prop closable

fixes #79

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


Ensure that the APIs Allowlist is extend to include distributed lock, configuration and workflows APIs

These APIs have been introduced as alpha-APIs and also need to be include in the APIs allow list. See
https://docs.dapr.io/operations/configuration/api-allowlist/ for the current supported APIs that can be restricted for an application.

This is already included in the code.
Nothing special needs to be done for HTTP APIs, and for gRPC the code is already done:
https://github.com/dapr/dapr/blob/77a3f1669c83253c203b9e30b9c8d7f59284c66d/pkg/grpc/endpoints.go#L68-L84


Character library is not showing

Hi, I am new to this community, so if I asked some dumb questions, I am truly sorry! But I really need help.
At first, I am following this guide to start, but it turns out there's nothing when I opened Character library (picture below).
https://home.gamer.com.tw/artwork.php?sn=5698780

Then I've tried following the guide to fix this problem, but it didn't work.
https://github.com/TavernAI/TavernAI/wiki/How-to-install
What should I do to fix this problem QQ

Hi yujiechiu, charaCloud (cloud server for the character library) is down so all users are also affected(I think), the only solution now is go to characterhub and download the character you want (or you have your own character already created) and chat.
Just wait until characloud is back 😅

There were technical works on the server. Now it's online again.


zh.po documents by the mdbook-i18n-helpers

Following #2385,
Construct the new documents by mdbook-i18n-helpers;
Complete the Chaptor 3.
updating the remaining.
following ISO-639-1 code standard of languages:
zh = Chinese Version of Language

@DrJingLee I added some scaffolding and a language picker. you can see the page by installing just
and doing
just serve-docs

or if you do not want to install just it would be:
  mdbook build docs -d build
  MDBOOK_BOOK__LANGUAGE=zh mdbook build docs -d build/zh
  mv docs/build/zh/html docs/build/html/zh
  python3 -m http.server --directory docs/build/html --bind <IP_ADDRESS> 8080

And .pot files are autogenerated so they do not have to be checked into git :)

It also seems that it's only partially translated:

I've delete the changes I made and opened a new PR https://github.com/ordinals/ord/pull/2403 for just the language picker things. Once that is merged you can merge those changes in here

I just merged https://github.com/ordinals/ord/pull/2403, so have a look at the updated README for instructions.
For this PR I will integrate into our build system tomorrow :)

I just merged https://github.com/ordinals/ord/pull/2403, so have a look at the updated README for instructions.
For this PR I will integrate into our build system tomorrow :)

Great job @raphjaph 👍👍


[Bug]: Background Text Visibility Issue on ChromeGaming!

Give a brief about the bug ✍
The background text on the ChromeGaming site is not visible, which creates readability issues and makes it difficult to interact with the site.
The text blends into the background, making it hard to read and navigate the site properly.

What is the expected behavior? 🤔
The background text should be clearly visible against the site background to ensure good readability.
Provide step by step information reproduce the bug 📄

Inspect the Element: Right-click on the problematic text and select "Inspect" to find the CSS class or ID.

Edit the CSS: Locate the CSS file and change the text color to ensure better contrast.

Test Locally: Save the changes and refresh the browser to verify the fix.

Commit and Deploy: Commit the changes to your version control and deploy to the production server.

Verify the Fix: Check the live site to ensure the issue is resolved and the text is readable.

Select program in which you are contributing
GSSoC24
Code of Conduct

[X] I follow CONTRIBUTING GUIDELINE of this project.

someone is already working on the same


Run nginx controller on a non-minion node

Add a --running-in-cluster=false mode. This is useful for running the controller on any non-minion node (eg: edge router, kubernetes master, local desktop for development etc).
Also adds an all-in-one rc example.
@aledbf

LGTM

I'll send a follow-up pr for the netlink ip address fix, merging this as is.


Create opt-in system for recent-messages

Is your feature request related to a problem? Please describe.
I'm trying to make my recent_messages service more compliant with the law, and i'd like more users to know about the optout options they have if they need them
Describe the solution you'd like
A section in the installer where the user is shown

that Chatterino2 can fetch messages from the recent_messages service
it will send each channel name you visit to a third-party service for that,
and that channels you visit will have their messages stored
that you can opt out of having the bot collect messages in your own channel by visiting https://recent-messages.robotty.de/ (Could be dynamic based on the recent messages url environment variable that was introduced), and that you can read the privacy policy by visiting that page
Two buttons at the bottom "Accept terms and use service", "Decline terms and don't use service" (or something like that)

Describe alternatives you've considered
Don't do it i guess, but it would be nice, also to keep the users more informed
Additional context

Sorry, due to the rewrite of recent-messages this is now no longer quite accurate. I'll work on updating this issue if somebody says they would be willing to even implement it.

I can implement it :-)

@Mm2PL the privacy page has been reinstated. https://recent-messages.robotty.de/privacy You can go ahead with implementing the feature now.

Maybe this could be done by inserting a system message with the question and two links: Accept and load history and Decline and don't ask again. I imagine this would look similar to automod allow/deny mod messages. Would require #1308. :thinking:

Oh yeah, that‘s a neat idea for a solution that‘s low-friction for the user.


Update NuGet Package fails with invalid project

I'm running the tool on a solution that contains an MVC 5 project and several class libraries. The libraries are in the SDK format with NuGet package references. The MVC5 project is the old project format. I have gotten to the step where it wants to upgrade my first class library project and then it wants to upgrade the NuGet packages. When that step runs it fails with the error "Invalid project: *.csproj". There is no indication as to what is wrong or why it is failing. That project is already in the SDK format, it targets .NET 4.7.2 and it already uses package references. Here's the project file it is trying to upgrade.
<Project Sdk="Microsoft.NET.Sdk">
  <PropertyGroup>
    <TargetFramework>net472</TargetFramework>
  </PropertyGroup>

  <ItemGroup>
    <PackageReference Include="Fsmb.Apollo" Version="8.1.0" />
    <PackageReference Include="Fsmb.Augusta" Version="4.1.2" />
    <PackageReference Include="Fsmb.EnterpriseServices.Logging" Version="4.1.1" />
    <PackageReference Include="Microsoft.CodeAnalysis.NetAnalyzers" Version="5.0.3">
      <PrivateAssets>all</PrivateAssets>
      <IncludeAssets>runtime; build; native; contentfiles; analyzers; buildtransitive</IncludeAssets>
    </PackageReference>
  </ItemGroup>
  <ItemGroup>
    <Reference Include="System.ComponentModel.DataAnnotations" />
  </ItemGroup>
</Project>

The FSMB packages are company packages hosted in our Nuget repo that is authenticated. Given the earlier issue with authenticated feeds I don't know if that is what is causing the problem here. Just to check I commented out the non-Nuget.org packages and it failed with the same error. Not sure if this information is cached or something such that I would need to rerun the tool after the project file change.
Attaching the log file.
log.txt

@mtaylorfsmb Could you provide a verbose log for this issue?
upgrade-assistant <solution/project> -v
Also we made a lot of bug fixes in this area, could you confirm you see this issue in the latest release of upgrade-assistant too? https://www.nuget.org/packages/upgrade-assistant/0.2.220602

@sunandabalu I can confirm that the latest 0.2.220602 resolves this particular error for my projects.

@mtaylorfsmb Closing this issue based on above comment, feel free to re-open if you are still seeing this issue.

@sunandabalu at this time I am unable to verify whether it works because I'm impacted by the authenticated Nuget feed issue that was already reported. Until the tool can pull from authenticated Nuget packages like Azure DevOps there is no way for me to validate.

@sunandabalu at this time I am unable to verify whether it works because I'm impacted by the authenticated Nuget feed issue that was already reported. Until the tool can pull from authenticated Nuget packages like Azure DevOps there is no way for me to validate.

#359 is tracking the work for auth Nuget feeds, its in progress currently.


Update java ckzg header to new interface

This file is pretty out-of-date:

https://github.com/ethereum/c-kzg-4844/blob/main/bindings/java/c_kzg_4844_jni.h

It says that it's a machine generated file though, not quite sure how to generate it.
https://github.com/ethereum/c-kzg-4844/blob/edb1274b705f9a44b4da0e726a16e462b76ee4b2/bindings/java/c_kzg_4844_jni.h#L1-L3
I'm surprised there are no complaints anywhere. Where is this used?

@StefanBratanov how do we regenerate this file? Or should we update it manually?

@StefanBratanov how do we regenerate this file? Or should we update it manually?

You can do javac -h . CKZG4844JNI.java and copy the contents of it to the current header file.


fetch() will send cookies even if told not to

Please provide all the information requested. Issues that do not follow this format are likely to stall.
Description
This issue Tries to resurface issue #12956
https://github.com/facebook/react-native/issues/12956#issuecomment-392775218
That seems to be happening even today.
You have to explicitly clear the cookies every time to avoid them being sent (even on the first request)
Even with credential: 'omit' header
React Native version:
System:
OS: macOS 10.15.6
CPU: (8) x64 Intel(R) Core(TM) i7-4870HQ CPU @ 2.50GHz
Memory: 1.55 GB / 16.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 12.19.0 - /usr/local/bin/node
Yarn: 1.22.10 - /usr/local/bin/yarn
npm: 6.14.8 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
Managers:
CocoaPods: 1.10.1 - /usr/local/bin/pod
SDKs:
iOS SDK:
Platforms: iOS 13.7, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
Android SDK:
API Levels: 23, 27, 28, 29, 30
Build Tools: 28.0.2, 28.0.3, 29.0.2, 29.0.3, 30.0.0, 30.0.2
System Images: android-25 | Google APIs ARM 64 v8a, android-28 | Intel x86 Atom, android-28 | Intel x86 Atom_64, android-28 | Google APIs Intel x86 Atom, android-28 | Google Play Intel x86 Atom
Android NDK: 22.0.7026061
IDEs:
Android Studio: 4.1 AI-201.87<IP_ADDRESS>53283
Xcode: 11.7/11E801a - /usr/bin/xcodebuild
Languages:
Java: 1.8.0_275 - /usr/bin/javac
Python: 2.7.16 - /usr/bin/python
npmPackages:
@react-native-community/cli: Not Found
react: 17.0.0 => 17.0.0
react-native: 0.63.4 => 0.63.4
react-native-macos: Not Found
npmGlobalPackages:
react-native: Not Found
Steps To Reproduce
Provide a detailed list of steps that reproduce the issue.

send a fetch request, include credentials: 'omit' in the headers.
sit back and watch getting different results from what you tested before with postman....

Expected Results
There should be away of making sure we a fetch request does not send any cookies.
(REST, stateless=no cookies)
Snack, code example, screenshot, or link to a repository:
                     let response = await fetch(ROUTES.serverURL + ROUTES.token.login, {                         headers: {                             "Authorization": "Basic " + base64.encode(username + ":" + password)                         },                         credentials: 'omit',                         method: 'POST',                     })
I feel that having to resort to:
CookieManager.clearAll()
is proof enough to make it an issue worth fixing.
Thanks!!

Hi @iairsalem thanks for the issue. I agree, cookie support in core RN is missing a bunch of features. I help maintain react-native-cookies, let me know how the package can be improved.

Closing as stale


Plural for data-suggestion-word

Hi, is there a way to set the plural of data-suggestion-word?
There are some languages (eg: Italian) that use "Suggerimento" for the singular, and "Suggerimenti" for the plural.
Can I set the plural suggestion word via data-*?
Actually the plugin adds the "s" word at the end of the suggestion word, this works for English language but not for other languages.
Thanks

Hi @acespace90 ,
good idea, I've implemented it in https://github.com/nico3333fr/jquery-accessible-autocomplete-list-aria/commit/7ee199e560775d02f40657c571cdf7597190f5bb ;)
Thanks a lot ;)

Great, you rock man! :-)

One thing: I can not update to the latest version via npm?
I'm trying with npm update jquery-accessible-autocomplete-list-aria
Where am I wrong?

No, you're not wrong, I forgot to publish. I've updated it right now.


Fix bug when both provider and consumer use async way.

Judge if statement to avoid bug when both provider and consumer use async way.

Codecov Report

Merging #3686 into master will decrease coverage by 0.01%.
The diff coverage is 0%.

@@             Coverage Diff              @@
##             master    #3686      +/-   ##
============================================
- Coverage     63.44%   63.43%   -0.02%
  Complexity       71       71
============================================
  Files           703      703
  Lines         31000    31000
  Branches       5024     5024
============================================
- Hits          19669    19664       -5
+ Misses         9066     9065       -1
- Partials       2265     2271       +6

Impacted Files
Coverage Δ
Complexity Δ

...g/apache/dubbo/rpc/proxy/AbstractProxyInvoker.java
50% <0%> (ø)
0 <0> (ø)
:arrow_down:

.../apache/dubbo/remoting/transport/AbstractPeer.java
58.69% <0%> (-13.05%)
0% <0%> (ø)

...mmon/threadpool/support/AbortPolicyWithReport.java
83.33% <0%> (-5.56%)
0% <0%> (ø)

...ng/exchange/support/header/HeartbeatTimerTask.java
73.68% <0%> (-5.27%)
0% <0%> (ø)

...onfig/spring/extension/SpringExtensionFactory.java
80.48% <0%> (-4.88%)
0% <0%> (ø)

...dubbo/remoting/exchange/support/DefaultFuture.java
74.32% <0%> (-1.36%)
0% <0%> (ø)

...apache/dubbo/rpc/protocol/dubbo/DubboProtocol.java
66.91% <0%> (+1.12%)
0% <0%> (ø)
:arrow_down:

...dubbo/rpc/protocol/dubbo/CallbackServiceCodec.java
78.67% <0%> (+2.2%)
0% <0%> (ø)
:arrow_down:

...apache/dubbo/common/config/ConfigurationUtils.java
72% <0%> (+8%)
0% <0%> (ø)
:arrow_down:

Continue to review full report at Codecov.

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


Releasing training data

Do you have any plan to release the 50 collected demo used for training in each task?
Thanks!

hi @enyen
I apologize that I can not find the original demonstrations collected. Now the data collection tool is here in this repo, I believe that you do not need much effort to collect just 50 demonstrations for each task, and also create your new environment for data collection.

No problem!


Marked as unsafe and removed from the Chrome webstore

This extension is marked as unsafe and removed from the chrome webstore.
The link no longer works.
https://chrome.google.com/webstore/detail/octohint/hbkpjkfdheainjkkebeoofkpgddnnbpk

I'm not sure about whether it really is unsafe, but I know that when I browsed the code for the version of Octohint that I still had, I found a lot of packing and obfuscation (most of it related to the module loader and the compilation of TypeScript); maybe I'll upload an archive if and when I'm satisfied that Google made a false positive, but for now, https://github.com/stefanbuck/awesome-browser-extensions-for-github recommends an alternative, albeit one with more features than just code-hinting: https://github.com/sourcegraph/sourcegraph

Resubmitted, waiting for the review. Thanks for your report!
It was removed by Chrome Web Store because some new fields need to be filled in, while I didn't respond in time. Actually, nothing to do with 'unsafe'.

Published as v2.0.9


Prevent deleted tracks from being zapped

Issue is that even if we delete track events, they could still exist on other relays we don't manage. We should create a check in zap requests to see if a track has been deleted before generating the invoice.

Included in: https://github.com/wavlake/wavlake.com/pull/523


on error handling

I realize opinions might run a bit strong here, but I'd like to make a case against the use of error-chain (or failure) for error handling in the cookbook examples. I think the error handling mechanisms provided by the standard library should be used instead.
Some background: I've been using Rust for a long time (since before 1.0), so the cookbook isn't actually something I've ever read in close detail before. I've also never used error-chain before (which I think probably reveals some bias in my argument here, FWIW).
I have an experience report from a colleague of mine that is in the process of learning Rust. They were using this cookbook as a way of reading example code. One of the things they did in their own code was copy the use of Result<()>. But their code wouldn't compile and they couldn't figure out why. When they asked me, I said, "oh, you're probably missing a type Result<T> = ...; somewhere in your code." But then they pointed me to the example in which they saw Result<()>, which does not have any such type alias.
It took me at least a few minutes of perplexed digging before I was actually able to figure out how that code was compiling. It turns out that the error_chain! macro is defining a Result type alias for you. Personally, I think this makes learning from these examples much harder than necessary. Some might even argue that the Result type alias itself is problematic, but even aside from that argument, I think having it implicitly defined and brought into scope is really quite surprising, especially for beginners that might be trying to learn Rust through this cookbook.
Of course, this is just one experience report. In any case, what are the alternatives? Here are some that I can think of:

Keep error-chain, but don't use the Result type alias. (What does one use instead that doesn't suffer from the same implicitness fault?)
Switch to using failure.
Switch to using only the facilities provided by the standard library.
Remove proper error handling altogether and use unwrap/panic.

I don't think we should remove proper error handling. I think a cookbook that shows how to do error propagation is much more valuable than a cookbook that doesn't. And I think such examples are incredibly useful for beginners.
I don't think we should use failure because its development is a bit in flux, despite it being used in a fair number of crates. In particular, there is a merged RFC to fix the standard library's Error trait, and this will likely have an impact on failure's API. So I think there is a collective "let's wait and see" on that front. However, if and when failure's future becomes solidified, it might be a good idea to transition to using it.
I also don't think we should use error-chain either, even if we were able to fix the implicitness problem in the examples today. Of course, fixing the implicitness would be something that I'd see as an improvement! For the most part, I perceive error-chain as something that the ecosystem is probably not going to adopt. I think the direction is likely headed more towards failure, or perhaps, even std itself.
Ultimately, my argument concludes here that we should just use what the standard library provides. In particular, if I were to write the aforementioned example:
#[macro_use]
extern crate error_chain;

use std::fs::File;
use std::io::{Write, BufReader, BufRead};

error_chain! {
    foreign_links {
        Io(std::io::Error);
    }
}

fn run() -> Result<()> {
    let path = "lines.txt";

    let mut output = File::create(path)?;
    write!(output, "Rust\n💖\nFun")?;

    let input = File::open(path)?;
    let buffered = BufReader::new(input);

    for line in buffered.lines() {
        println!("{}", line?);
    }

    Ok(())
}

quick_main!(run);

then I would write it like this:
use std::fs::File;
use std::io::{self, Write, BufReader, BufRead};
use std::process;

fn run() -> io::Result<()> {
    let path = "lines.txt";

    let mut output = File::create(path)?;
    write!(output, "Rust\n💖\nFun")?;

    let input = File::open(path)?;
    let buffered = BufReader::new(input);

    for line in buffered.lines() {
        println!("{}", line?);
    }

    Ok(())
}

fn main() {
    if let Err(err) = run() {
        eprintln!("{}", err);
        process::exit(1);
    }
}

If an example requires dealing with multiple errors, then I'd either write out a new error type, possibly with appropriate From impls, or just use Box<Error>. Namely, Box<Error> is used in command line tools effectively as a means of bubbling an error up to main. The downside to using Box<Error> is that it's probably not something one wants to use in a library.
I also believe that the examples should not return Result directly from main, as suggested in #433. I explained my position on that front in more detail here. With that said, I personally feel less strongly on this point than I do about using error_chain or failure.
Finally, I certainly don't intend to say that error-chain (or failure) should be expunged from the cookbook entirely. I just think they shouldn't be the go-to error handling mechanism for every single example.
Thanks for your consideration! And thanks so much for all your hard work on this wonderful resource. I'd like to end on a positive note: my colleague reports that the cookbook has been a wonderful resource for learning Rust. In particular, he found that the cookbook---above other docs---made it much easier to learn how to actually start writing a full program. That's an awesome compliment!

Let me start that I love your feedback and hope to make it into something actionable!
I agree that the current error handling situation is less than ideal, mostly due to error-chain being both too "magical" and heavyweight. Also I second that if the whole error handling can be performed with builtin / imported Result / Error types the error-chain usage should ideally be removed.
I can't say that I love the idea of writing explicit error handling in main
fn main() {
    if let Err(err) = run() {
        eprintln!("{}", err);
        process::exit(1);
    }
}

and presenting it on nearly every example along with hand crafted error types. This would get rather verbose and would lead the examples to be quite noisy (error boilerplate vs actual example code ratio would suffer). The error boilerplate and main is typically hidden in order not to obscure the actual learning material which sadly leaves the Result<()> in sight which is counter productive to the learning process.
The main goals in regard to error handling in cookbook were:

be correct and as close to real use cases
be painless to implement (both for learners and cookbook contributors)
require minimal boilerplate not to obscure the actual example / learning material

Once the error-chain seamed to provide the best trade-off for these particular requirements and I still hope that failure will reach maturity giving us minimal boilerplate.
At this point I'm not sure what would be the best way to proceed with the error handling, every approach that you have mentioned is perfectly valid with its own set of drawbacks and each strategy has its usage in given domains If possible I'd like to avoid advertising any particular error handling strategy and hid as much of it as possible, the reader will know that the hidden parts are not part of the example, just the implementation detail for the curious.
I'd love to get more feedback on this matter!

Wow, there's a lot of thought in there that I can appreciate.
I personally have seen more and more movement towards a specified Enum of Error variants.  I personally like that approach because it defines in the code the error types expected and doesn't require learning a library's macro to use.  Here is Hyper's error enum.  Here's a stackoverflow answer demonstrating how to implement an Enum.
The first book also gives this advice: defining your own error type.  I think including something similar in the Error Handling section would help learners understand error-chain under the hood. If at the least we make it difficult for readers of the cookbook to miss doing this once to learn about managing their own errors, a novice would be prepared to use whichever library.
I also like the idea of taking error_chain out of every example that doesn't require it.  Your example is one of them that slipped by review.  error_chain is only supposed to be used when there are multiple error types returned.
What I want to see done is:

Identify the examples that are incorrectly using error_chain
Continue to consider failure and the possibility of including it in the future.  It seems to be rapidly become de facto rust library for error management.
Look for a resource to manage multiple error types without magic, whether it be Box or Enum.  Seeing how a library accomplishes this is important for knowing how to use a library.

I can't say that I love the idea of writing explicit error handling in main [...snip...] and presenting it on nearly every example along with hand crafted error types. This would get rather verbose and would lead the examples to be quite noisy (error boilerplate vs actual example code ratio would suffer).

I think this might come down to folks weighting the negativity of boiler plate differently. To me, adding a 4 line main function to each example in exchange for making the example explicit and easy to understand, is a trade well worth making. Note that the main function probably never grows, or at least, doesn't grow much.
I also think that putting the main function in the "hidden" section of the code would be acceptable, or at least better than today. It's true that the Result is still implicit, but it would become explicit after looking at the hidden code. I think the existence of hidden code in the first place acknowledges that it's OK to make this trade in some cases. For example, examples are putting this in the hidden code:
error_chain! {
    foreign_links {
        Io(std::io::Error);
    }
}

My method allows you to remove that and the extern crate error_chain; at the top. So I think you actually wind up with fewer lines of code.
Separate from that is building out error enums. I do agree that this can become quite noisy. With that said, that pattern is in widespread use in the ecosystem. However, it isn't always necessary. Box<Error> is a fine substitute in plenty of cases that should be suitable for very terse examples. io::Result<()> is probably also suitable in a large class of examples. For example, the csv crate's Error type has a From<csv::Error> for std::io::Error impl to make it seamless to use with io::Error. I expect other libraries might do the same.

I also like the idea of taking error_chain out of every example that doesn't require it. Your example is one of them that slipped by review. error_chain is only supposed to be used when there are multiple error types returned.
What I want to see done is:
...
Big :+1:

I think this might come down to folks weighting the negativity of boiler plate differently.

It's admittedly my very subjective take on how we ought to present the teaching material. We established it without any prior teaching experience mostly based on "gut feeling" so nothing is set in stone and any ideas are welcome  :)

My method allows you to remove that and the extern crate error_chain; at the top. So I think you actually wind up with fewer lines of code.

Yep we are totally on board with this idea as @AndyGauge mentioned its already on the agenda.

Box<Error> is a fine substitute in plenty of cases that should be suitable for very terse examples.

That is true but I'm worried a out two things:

What level of consistency between examples should we strive for?
Box<Error> is a very convenient pattern but I worry that mere fact of presenting it in the examples will act as blessing it as the "silver bullet" solution. Error handling is almost always dependent on additional factors and constraints which will not be present in the artificial environment of the cookbook. How do we prevent our readers from conflating boilerplate with idiomatic approach endorsement?

Box<Error> is a very convenient pattern but I worry that mere fact of presenting it in the examples will act as blessing it as the "silver bullet" solution. Error handling is almost always dependent on additional factors and constraints which will not be present in the artificial environment of the cookbook. How do we prevent our readers from conflating boilerplate with idiomatic approach endorsement?

I don't think you can really solve this completely. Even if failure evolves a year from now with something that's based on the fixes to the standard library Error trait into something that gains near universal adoption, you will still always have cases where libraries want to create their own structured errors.  Some examples might call for defining those errors, or perhaps, you might consider specifically constructing examples in which defining your own custom error type is the right way forward. But other examples devolving to the use of trait objects (which ultimately is what failure is encouraging) seems fine to me, especially in examples that are command line programs.
Proper error handling in libraries can be difficult. While I think some examples devoted to it would be great, I do not think using trait objects in the majority of examples is a significant negative. If people wind up using Box<Error> in command line applications, then I don't think that's a big negative. If people wind up returning Box<Error> in their libraries (and possibly failure::Error in the future) in place of more structured errors, then that's more of a negative, but at that point, you're well into API design.
One additional note: Box<Error> is much less useful today than it will be once the Error trait is fixed with the aforementioned RFC. In particular, it will at that point be possible to downcast effectively and extract backtraces from it.

Box<Error> is a very convenient pattern but I worry that mere fact of presenting it in the examples will act as blessing it as the "silver bullet" solution. Error handling is almost always dependent on additional factors and constraints which will not be present in the artificial environment of the cookbook. How do we prevent our readers from conflating boilerplate with idiomatic approach endorsement?

I don't think you can really solve this completely. Even if failure evolves a year from now with something that's based on the fixes to the standard library Error trait into something that gains near universal adoption, you will still always have cases where libraries want to create their own structured errors.  Some examples might call for defining those errors, or perhaps, you might consider specifically constructing examples in which defining your own custom error type is the right way forward. But other examples devolving to the use of trait objects (which ultimately is what failure is encouraging) seems fine to me, especially in examples that are command line programs.
Proper error handling in libraries can be difficult. While I think some examples devoted to it would be great, I do not think using trait objects in the majority of examples is a significant negative. If people wind up using Box<Error> in command line applications, then I don't think that's a big negative. If people wind up returning Box<Error> in their libraries (and possibly failure::Error in the future) in place of more structured errors, then that's more of a negative, but at that point, you're well into API design.
One additional note: Box<Error> is much less useful today than it will be once the Error trait is fixed with the aforementioned RFC. In particular, it will at that point be possible to downcast effectively and extract backtraces from it.

Hi, I love this cookbook, and I feel fun with typing it on my vim screen :)Thank you.By the way, although the example shows a code which uses 'flate2' and 'tar' library, the code can't be compiled without "error_chain" crate. I found the problem by clicking the "expand" icon and could access the full source codes.It would be better if "error_chain" crate is specified explicitly(and also #[macro_use] is important one), and add some comment about it to avoid confusion to the beginner, or some description which informs reader to click the "expand" icon to get a whole working code.Thanks!
@gkm2164

In the mean time, error-chain is unmaintained, and failure has been deprecated. Yet this cookbook still shows error-chain all while the introduction says:

Error handling in Rust is robust when done correctly, but in today's Rust it requires a fair bit of boilerplate. Because of this one often sees Rust examples filled with unwrap calls instead of proper error handling.
Since these recipes are intended to be reused as-is and encourage best practices, they set up error handling correctly when there are Result types involved.
The basic pattern we use is to have a fn main() -> Result.

I think this cookbook should have dedicated recipes about error handling right at the beginning. One for apps and one for libs. I would suggest that they show how to make a custom error type with thiserror for libs and how to use anyhow in application code. Explaining extras like why this is currently the recommended way. Maybe refer to crates like user-error and human-panic for apps as well.
I would follow the proposition of @BurntSushi of using an explicit main that handles the errors. There's nothing more hampering for learning than some invisible magic happening. Returning Result from main is an anti-pattern. It is functionally equivalent to unwrapping, that is to say worse than expect and only exists to hide the unwrapping from users in documentation so they wouldn't copy paste unwrap. It's no good in an actual application, so I don't think teaching materials should have it.
For aggregating errors, Box<dyn Error> is pretty good if you want to avoid boilerplate, but I would put a link just above every example that says, "for proper error handling techniques, see Chapter 1: Error Handling".
I know it's easy to have an opinion, but if there was consensus about this, I could put some time towards writing an error handling chapter.

I would suggest that they show how to make a custom error type with thiserror for libs

I wouldn't recommend thiserror for libraries without qualification. It adds a fairly hefty dependency. It might be good to have an example using thiserror (and perhaps snafu), but the dominant method for defining errors in library should be without a derive helper (unless one becomes available in std).

There's nothing more hampering for learning than some invisible magic happening. Returning Result from main is an anti-pattern. It is functionally equivalent to unwrapping, that is to say worse than expect and only exists to hide the unwrapping from users in documentation so they wouldn't copy paste unwrap. It's no good in an actual application, so I don't think teaching materials should have it.

main -> Result works okay when you use anyhow::Result, but only because anyhow emits a human readable error message for its Debug format. (Precisely because main -> Result prints the debug representation.)

I wouldn't recommend thiserror for libraries without qualification. It adds a fairly hefty dependency.

Are you referring to compile times?

I think the cookbooks use of error-chain gives the false impression that error-chain is the current, favoured error-handling library.
We could update to use the latest error handling libraries thiserror and/or anyhow, but it's hard to know there won't be a new error handling library in a year or two.
For that reason, using only std for error handling becomes desirable.
On the other hand, since the rust cookbook is about demonstrating use of the favoured crates in the eco system, perhaps there should be a set of recipes for error handling to show off anyhow and thiserror. Which could mention how you would swap out the std error handling in other reviews for anyhow or thiserror.

I think the cookbooks use of error-chain gives the false impression that error-chain is the current, favoured error-handling library.

In case it's a useful data-point. I am (comparatively) new to rust, and this is the exact initial impression the use of error_chain here gave me. I did work out that anyhow was more suitable for my needs, but not after losing a little time trying to figure out how to use error_chain, and then realizing that it wasn't state-of-the-art anymore.
Definitely something showing off anyhow and thiserror (including why anyhow is often preferred for apps, and thiserror for apis) would have been a lot more instructive for me.

due to deprecations, anyhow and thiserror are being recommended for 2024.  I truly appreciate all the work @BurntSushi put into failure and @brson put into error-chain but looking to close this chapture.

To clarify, I did not author or work on failure.

Well I use ripgrep all the time, so thank you for that.  Also bringing up the rust error situation in the cookbook was important too.


duplicate subtitle while converting vtt subtitle to srt which the vtt subtitle is auto-translated

Checklist

[X] I'm reporting a bug unrelated to a specific site
[X] I've verified that I'm running yt-dlp version 2022.04.08 (update instructions) or later (specify commit)
[X] I've checked that all provided URLs are alive and playable in a browser
[X] I've checked that all URLs and arguments with special characters are properly quoted or escaped
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Description
after downloaded the youtube video with only auto-generated subtitles, the post-processor converted the vtt subtitle into srt subtitle succesfully but with improper content.  the srt subtitle have duplicated sentences which is very confusing when watching video with the srt subtitle.  please see the screenshot below and find more as the Archive.zip

[Archive.zip](https://github.com/yt-dlp/yt-dlp/files/8587839/Archive.zip)
Verbose log
appledeMacBook-Pro:t apple$ yt-dlp https://www.youtube.com/watch?v=MfGNLVS5-RE -vU -k
[debug] Command-line config: ['https://www.youtube.com/watch?v=MfGNLVS5-RE', '-vU', '-k']
[debug] Home config "yt-dlp.conf": ['--output', '//Users/apple/t/%(uploader)s/%(title)s-%(resolution)s.%(ext)s', '--console-title', '--progress-template', 'download-title:%(info.id)s-%(progress.eta)s', '--merge-output-format', 'mp4', '--sub-langs', 'zh-Hans', '--write-auto-subs', '--convert-subs', 'srt', '--embed-thumbnail', '--embed-metadata']
[debug] Encodings: locale UTF-8, fs utf-8, out utf-8, err utf-8, pref UTF-8
[debug] yt-dlp version 2022.04.08 [7884ade65]
[debug] Python version 3.9.10 (CPython 64bit) - macOS-12.3-x86_64-i386-64bit
[debug] Checking exe version: ffmpeg -bsfs
[debug] Checking exe version: ffprobe -bsfs
[debug] exe versions: ffmpeg 5.0 (setts), ffprobe 5.0
[debug] Optional libraries: brotli, certifi, Cryptodome, mutagen, sqlite, websockets
[debug] Proxy map: {'http': 'http://<IP_ADDRESS>:7890', 'https': 'http://<IP_ADDRESS>:7890'}
Latest version: 2022.04.08, Current version: 2022.04.08
yt-dlp is up to date (2022.04.08)
[debug] [youtube] Extracting URL: https://www.youtube.com/watch?v=MfGNLVS5-RE
[youtube] MfGNLVS5-RE: Downloading webpage
[youtube] MfGNLVS5-RE: Downloading android player API JSON
[debug] Loading youtube-nsig.fe8185e7 from cache
[debug] [youtube] Decrypted nsig jsvJWDITcvfIZU5o8 => eVUJDR5ldPDe7Q
[debug] Sort order given by extractor: quality, res, fps, hdr:12, source, codec:vp9.2, lang, proto
[debug] Formats sorted by: hasvid, ie_pref, quality, res, fps, hdr:12(7), source, vcodec:vp9.2(10), acodec, lang, proto, filesize, fs_approx, tbr, vbr, abr, asr, vext, aext, hasaud, id
[debug] Downloading subtitles: zh-Hans
[debug] Default format spec: bestvideo*+bestaudio/best
[info] MfGNLVS5-RE: Downloading 1 format(s): 303+251
[info] Writing video subtitles to: //Users/apple/t/Megs Braap/I Am Weird - Solo Practice Session-1920x1080.zh-Hans.vtt
[debug] Invoking downloader on "https://www.youtube.com/api/timedtext?v=MfGNLVS5-RE&caps=asr&xoaf=5&hl=en&ip=<IP_ADDRESS>&ipbits=0&expire=1651226072&sparams=ip%2Cipbits%2Cexpire%2Cv%2Ccaps%2Cxoaf&signature=5CCDB8E4A5DBA39718CEBBF106082CFD39A8E058.C4293B498F8739F55519E2EE0C04333C315CD3E9&key=yt8&kind=asr&lang=en&tlang=zh-Hans&fmt=vtt"
[download] Destination: //Users/apple/t/Megs Braap/I Am Weird - Solo Practice Session-1920x1080.zh-Hans.vtt
[download] 100% of 22.30KiB in 00:00
[info] Downloading video thumbnail 41 ...
WARNING: Unable to download video thumbnail 41: HTTP Error 404: Not Found
[info] Downloading video thumbnail 40 ...
WARNING: Unable to download video thumbnail 40: HTTP Error 404: Not Found
[info] Downloading video thumbnail 39 ...
WARNING: Unable to download video thumbnail 39: HTTP Error 404: Not Found
[info] Downloading video thumbnail 38 ...
WARNING: Unable to download video thumbnail 38: HTTP Error 404: Not Found
[info] Downloading video thumbnail 37 ...
[info] Writing video thumbnail 37 to: //Users/apple/t/Megs Braap/I Am Weird - Solo Practice Session-1920x1080.webp
[SubtitlesConvertor] Converting subtitles
[debug] ffmpeg command line: ffmpeg -y -loglevel repeat+info -i 'file://Users/apple/t/Megs Braap/I Am Weird - Solo Practice Session-1920x1080.zh-Hans.vtt' -f srt -movflags +faststart 'file://Users/apple/t/Megs Braap/I Am Weird - Solo Practice Session-1920x1080.zh-Hans.srt'
[debug] Invoking downloader on "https://rr5---sn-npoldn7e.googlevideo.com/videoplayback?expire=1651222473&ei=aVNrYs_nE8ynwgObh57IDQ&ip=<IP_ADDRESS>&id=o-AAJwxP8T1cFvEPrHXpzTyD2buQMUhCD_0VUKnusf5Wvc&itag=303&source=youtube&requiressl=yes&mh=Ce&mm=31%2C26&mn=sn-npoldn7e%2Csn-oguelney&ms=au%2Conr&mv=m&mvi=5&pl=21&initcwndbps=613750&vprv=1&mime=video%2Fwebm&gir=yes&clen=260164413&dur=364.113&lmt=1651178632488776&mt=1651200564&fvip=3&keepalive=yes&fexp=24001373%2C24007246&c=ANDROID&txp=6319224&sparams=expire%2Cei%2Cip%2Cid%2Citag%2Csource%2Crequiressl%2Cvprv%2Cmime%2Cgir%2Cclen%2Cdur%2Clmt&sig=AOq0QJ8wRQIgUMVsr0fYQdEZh-pGeM1xdL13MLMPF3KVkzmFt9-7QO0CIQC-d18j_IXbdOwnZYLZtnaZWJijC9ASm65Zeg-I8kaLxw%3D%3D&lsparams=mh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpl%2Cinitcwndbps&lsig=AG3C_xAwRQIgYK2IC0RZUcNrqETn2LXkgccpdf6ver7p87c5z2XsKkoCIQCiTP0VcBbpaCPIzpF0XTqlXCtBpe8oBNMBA_N-Py87gw%3D%3D"
[download] Destination: //Users/apple/t/Megs Braap/I Am Weird - Solo Practice Session-1920x1080.f303.webm
[download] 100% of 248.11MiB in 01:11
[debug] Invoking downloader on "https://rr5---sn-npoldn7e.googlevideo.com/videoplayback?expire=1651222473&ei=aVNrYs_nE8ynwgObh57IDQ&ip=<IP_ADDRESS>&id=o-AAJwxP8T1cFvEPrHXpzTyD2buQMUhCD_0VUKnusf5Wvc&itag=251&source=youtube&requiressl=yes&mh=Ce&mm=31%2C26&mn=sn-npoldn7e%2Csn-oguelney&ms=au%2Conr&mv=m&mvi=5&pl=21&initcwndbps=613750&vprv=1&mime=audio%2Fwebm&gir=yes&clen=6070590&dur=364.141&lmt=1651178690673095&mt=1651200564&fvip=3&keepalive=yes&fexp=24001373%2C24007246&c=ANDROID&txp=6318224&sparams=expire%2Cei%2Cip%2Cid%2Citag%2Csource%2Crequiressl%2Cvprv%2Cmime%2Cgir%2Cclen%2Cdur%2Clmt&sig=AOq0QJ8wRgIhALTNc5UW1J2puxv9D5JK0KMSoEhaNe8l_biLR7Nw3kJdAiEA2R6g1wwwH7-DpEnnM2tHzs-doUV6Wv7ectPMmA5KJoY%3D&lsparams=mh%2Cmm%2Cmn%2Cms%2Cmv%2Cmvi%2Cpl%2Cinitcwndbps&lsig=AG3C_xAwRQIgYK2IC0RZUcNrqETn2LXkgccpdf6ver7p87c5z2XsKkoCIQCiTP0VcBbpaCPIzpF0XTqlXCtBpe8oBNMBA_N-Py87gw%3D%3D"
[download] Destination: //Users/apple/t/Megs Braap/I Am Weird - Solo Practice Session-1920x1080.f251.webm
[download] 100% of 5.79MiB in 00:02
[Merger] Merging formats into "//Users/apple/t/Megs Braap/I Am Weird - Solo Practice Session-1920x1080.mp4"
[debug] ffmpeg command line: ffmpeg -y -loglevel repeat+info -i 'file://Users/apple/t/Megs Braap/I Am Weird - Solo Practice Session-1920x1080.f303.webm' -i 'file://Users/apple/t/Megs Braap/I Am Weird - Solo Practice Session-1920x1080.f251.webm' -c copy -map 0:v:0 -map 1:a:0 -movflags +faststart 'file://Users/apple/t/Megs Braap/I Am Weird - Solo Practice Session-1920x1080.temp.mp4'
[Metadata] Adding metadata to "//Users/apple/t/Megs Braap/I Am Weird - Solo Practice Session-1920x1080.mp4"
[debug] ffmpeg command line: ffmpeg -y -loglevel repeat+info -i 'file://Users/apple/t/Megs Braap/I Am Weird - Solo Practice Session-1920x1080.mp4' -map 0 -dn -ignore_unknown -c copy -write_id3v1 1 -metadata 'title=I Am Weird - Solo Practice Session' -metadata date=20220428 -metadata 'description=If you'"'"'d like to support my channel, you can purchase your parts, gear, and supplies through my Rocky Mountain ATV/MC link! Anything at all that you purchase through this link (doesn'"'"'t have to be my favourites), helps support me. Thank you!

https://www.rockymountainatvmc.com/Sales/3329/Megs-Top-Picks?ref=1048&utm_source=youtube&utm_medium=megsbraap&utm_campaign=influencer

When I go for a solo ride that isn'"'"'t focused around stamina training, this is often what I get up to.  Just practicing my technical skills by focusing on obstacles or sections of trail that are difficult.' -metadata 'synopsis=If you'"'"'d like to support my channel, you can purchase your parts, gear, and supplies through my Rocky Mountain ATV/MC link! Anything at all that you purchase through this link (doesn'"'"'t have to be my favourites), helps support me. Thank you!

https://www.rockymountainatvmc.com/Sales/3329/Megs-Top-Picks?ref=1048&utm_source=youtube&utm_medium=megsbraap&utm_campaign=influencer

When I go for a solo ride that isn'"'"'t focused around stamina training, this is often what I get up to.  Just practicing my technical skills by focusing on obstacles or sections of trail that are difficult.' -metadata 'purl=https://www.youtube.com/watch?v=MfGNLVS5-RE' -metadata 'comment=https://www.youtube.com/watch?v=MfGNLVS5-RE' -metadata 'artist=Megs Braap' -movflags +faststart 'file://Users/apple/t/Megs Braap/I Am Weird - Solo Practice Session-1920x1080.temp.mp4'
[ThumbnailsConvertor] Converting thumbnail "//Users/apple/t/Megs Braap/I Am Weird - Solo Practice Session-1920x1080.webp" to png
[debug] ffmpeg command line: ffmpeg -y -loglevel repeat+info -f image2 -pattern_type none -i 'file://Users/apple/t/Megs Braap/I Am Weird - Solo Practice Session-1920x1080.webp' -movflags +faststart 'file://Users/apple/t/Megs Braap/I Am Weird - Solo Practice Session-1920x1080.png'
[EmbedThumbnail] mutagen: Adding thumbnail to "//Users/apple/t/Megs Braap/I Am Weird - Solo Practice Session-1920x1080.mp4"

Duplicate of https://github.com/yt-dlp/yt-dlp/issues/1734


PureIDELight: Fix name in buildRepositories

What type of PR is this?
Bugfix
What does this PR do / why is it needed ?
Fix name of module in buildRepositories in PureIDELight. Allows IDELight to launch without throwing missing repository exception

isn't this duplicated of https://github.com/finos/legend-engine/pull/1698 ?

Duplicate of #1698


Feature request: Exif metadata

I think it's a great feature that tools like automatic1111 write all the parameters from inference into the images' metadata. That way you can re-discover old pictures on your harddrive and see what model hash, seed and prompt you used.
The Readme of the stb library mentiones this small lib:

https://github.com/mayanklahiri/easyexif

(Edit: I think that library is just to read metadata, not write it :disappointed: )

In fact, I'm considering adding parameter information to the generated images. However, I haven't found a good method for doing so yet.

I think we should be able to "write" the image to memory (using stb_image_write) and modify the memory afterwards to insert a tEXt chunk (automatic's ui inserts them at the front after IHDR)
wikipedia excerpt:

tEXt can store text that can be represented in ISO/IEC 8859-1, with one key-value pair for each chunk. The "key" must be between one and 79 characters long. Separator is a null character. The "value" can be any length, including zero up to the maximum permissible chunk size minus the length of the keyword and separator. Neither "key" nor "value" can contain null character. Leading or trailing spaces are also disallowed.

example hex screencap from file generated with automatic's ui:


Enable link opening

I've found that installing xdg-utils is the missing piece to get vscode to be able to open links in devcontainers.
One of the things it installs is open. Tested that it triggers the browser to open:
open https://nasa.gov

I've used that for other cli tools in the past that try to open the browser nicely, but I haven't tried it with sfdx personally. I assume it's using the same method to open things.
And I'm using that apt-packages feature instead of apt install xdg-utils just because it's pre-built and a little easier to consume.

Ah looks like I'll need someone else to merge:


Update links to k8s.io/docs/user-guide/... in autogenerated docs

This is a...

[ ] Feature Request
[X] Bug Report

Problem:
There are still links in the kubernetes/kubernetes autogenerated docs to the deprecated /docs/user-guide/ directory in k8s.io. This issue is the same as kubernetes/kubernetes#48105 in that repo.
Proposed Solution:
Submit a PR in kubernetes/kubernetes to fix all of the links containing kubernetes.io/docs/user-guide/. See https://github.com/kubernetes/kubernetes/search?utf8=✓&q=%2Fuser-guide%2F&type=
Page to Update:
types.go files in kubernetes/kubernetes repo

Isn't this the same as #4192?

Sigh. Yes. :(


1.1.3 version

@cerdiogenes - Turns compatible with sprockets 4
@shekhar-patil - Application Controller inheritance
@taki - Switch to sassc-rails gem

@zuzannast Could you please release 1.1.3 :question:

Thank you 🎉


tank → Taunts, avoidance, and one-on-one duels notifications do not work.

tank → Taunts, avoidance, and one-on-one duels notifications do not work.

Highly likely this is related to #328, so will close this for now pending a fix to #328 (as these features do seem to work fine in current int'l versions).  Please do re-open though if the eventual fix for the other PR doesn't address these issues.


Add support for text slot metadata

This is part of a larger Home Assistant PR, but essentially it allows passing additional data through on text slots which can be accessed on the returned entities.

Thanks! I'm adding a similar thing for sentences too :+1:

Please don't forget to add docs, too. https://github.com/home-assistant/developers.home-assistant


Sync multiple vuejs-paginate components

What might be the best option to sync multiple vuejs-paginate components?
I want to add the pagination at the top and bottom of a table.
Thank you in advance,

Hello @johnmerced . You can check this issue. Hope it will solve your problem. Thanks.
https://github.com/lokyoung/vuejs-paginate/issues/36


[ERROR] "not found" message when specifying ja_ginza_electra

Hi there,
When I executed the code below:
import spacy
nlp = spacy.load('ja_ginza_electra')

I got the following error and could not specify it.
Cannot find the requested files in the cached path and outgoing traffic has been disabled. To enable model look-ups and downloads online, set 'local_files_only' to False.
trying to download model from huggingface hub: /tmp/tmpnvmt9ddh/config.json ...
Traceback (most recent call last):
  File "/usr/local/lib/python3.8/dist-packages/transformers/configuration_utils.py", line 568, in get_config_dict
    resolved_config_file = cached_path(
  File "/usr/local/lib/python3.8/dist-packages/transformers/file_utils.py", line 1776, in cached_path
    output_path = get_from_cache(
  File "/usr/local/lib/python3.8/dist-packages/transformers/file_utils.py", line 1994, in get_from_cache
    raise FileNotFoundError(
FileNotFoundError: Cannot find the requested files in the cached path and outgoing traffic has been disabled. To enable model look-ups and downloads online, set 'local_files_only' to False.

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/local/lib/python3.8/dist-packages/ginza_transformers/layers/hf_shim_custom.py", line 127, in from_bytes
    transformer = AutoModel.from_pretrained(config._name_or_path, local_files_only=True)
  File "/usr/local/lib/python3.8/dist-packages/transformers/models/auto/auto_factory.py", line 418, in from_pretrained
    config, kwargs = AutoConfig.from_pretrained(
  File "/usr/local/lib/python3.8/dist-packages/transformers/models/auto/configuration_auto.py", line 582, in from_pretrained
    config_dict, _ = PretrainedConfig.get_config_dict(pretrained_model_name_or_path, **kwargs)
  File "/usr/local/lib/python3.8/dist-packages/transformers/configuration_utils.py", line 593, in get_config_dict
    raise EnvironmentError(msg)
OSError: Can't load config for '/tmp/tmpnvmt9ddh/config.json'. Make sure that:

- '/tmp/tmpnvmt9ddh/config.json' is a correct model identifier listed on 'https://huggingface.co/models'
  (make sure '/tmp/tmpnvmt9ddh/config.json' is not a path to a local directory with something else, in that case)

- or '/tmp/tmpnvmt9ddh/config.json' is the correct path to a directory containing a config.json file

Can you please tell me how to solve this problem?

@cidrugHug8
I got the same error as you reported above.
These are library versions I used:
ginza==5.1.0
ja-ginza-electra==5.1.0
spacy-transformers==1.1.4
transformers==4.15.0

I suspect that this error is due to specification change of transformers.
When I downgraded transformers==4.12.5 and executed spacy.load('ja_ginza_electra'), there was no error.
I think 4.12.5 is boundary condition because transformers==4.13.0 generated the same error.

Hi @cidrugHug8 and @tnakae,
Thank you for reporting this issue.
We've deployed revised version of ginza-transformers (0.4.1) which restricts transformers <= 4.13.0.
Could you please test it via pip install -U ?
$ pip install -U ja-ginza-electra ginza-transformers transformers

@hiroshi-matsuda-rit
Nice job!
When I updated packages, no error occurred. Thanks!


groupBy fails to aggregate Options

Version: 2.3.2
Module: quill-async-postgres
Expected behavior
Aggregate Options as normal if they have value otherwise provide default value, Something like (COALESCE) in postgresql. Query could be like:
case class Person(name: String, age: Option[Int])

val m = ctx.run(
   query[Person].groupBy(p =>p.name).map {
    case ( name,people) =>

      ( name,people.map(_.age).sumOrElse(0) )

Actual behavior
could not find implicit value for parameter n: Numeric[Option[Int]]
Steps to reproduce the behavior
https://scastie.scala-lang.org/o5DhxlFgRJyC5O2q1xpeVA
Workaround
@getquill/maintainers

Same problem here. with all aggregation functions not only on group by.


Add resource size info to transfer type OCM share

At WP4.4 it is discussed that it would be useful for a receiver of a transfer type OCM share to know the size of the transfer before accepting it. Although the size cannot be guaranteed, a sender could still add more files to a transfer folder which would also be transferred after acceptance in case of a transfer retry, the receiving end could limit the transfer to the expected size (data cap). Or, from the end user viewpoint, have an idea of what to expect.
For the receiver it is not possible to stat the resource to be transferred before accepting it because the webdav reference to it is only created after accepting the share. Thus, the size info must be send by the creator of the resource as a specific size parameter.
The initiator of the datatx type OCM share adds the current size to the opaque field of the request:
https://github.com/cs3org/reva/blob/44c9fa189af323a877168a63d77a078caaabda20/cmd/reva/transfer-create.go#L112
		createShareReq := &ocm.CreateOCMShareRequest{
			Opaque: &types.Opaque{
				Map: map[string]*types.OpaqueEntry{
					"permissions": {
						Decoder: "plain",
						Value:   []byte(strconv.Itoa(pint)),
					},
					"name": {
						Decoder: "plain",
						Value:   []byte(statRes.Info.Path),
					},
					"protocol": {
						Decoder: "plain",
						Value:   []byte("datatx"),
					},
					"size": {
						Decoder: "plain",
						Value:   []byte("60000000"),
					},
				},
			},

Next we add the size as an option of the protocol section of the OCM share request:
https://github.com/cs3org/reva/blob/44c9fa189af323a877168a63d77a078caaabda20/pkg/ocm/share/manager/json/json.go#L257
		protocol := map[string]interface{}{
			"name": "webdav",
			"options": map[string]string{
				"permissions": pm,
				"token":       ctxpkg.ContextMustGetToken(ctx),
				"size": size,
			},
		}

And the datatx driver will be called specifying the size in a new options parameter:
https://github.com/cs3org/reva/blob/44c9fa189af323a877168a63d77a078caaabda20/pkg/datatx/datatx.go#L30
type Manager interface {
	// StartTransfer initiates a transfer job and returns a TxInfo object including a unique transfer id, and error if any.
	StartTransfer(
		ctx context.Context,
		srcRemote string,
		srcPath string,
		srcToken string,
		destRemote string,
		destPath string,
		destToken string,
		options map[string]interface{}) (*datatx.TxInfo, error)
	...

In the driver implementation the decision to cap on size is based on the value of 2 new datatx config flags:
# if true and size option (set in bytes) is specified in the received datatx type share, the transfer will stop if that size has been reached
limit_transfer = true/false
# will stop the transfer if max_transfer_size (set in bytes) has been reached and limit_transfer is set to true
max_transfer_size = 60000000

@glpatcern @michielbdejong @gmgigi96 do we regard discovering the size of the transfer a task of reva or the efss ? (ps. I know its a required field, but are we aiming to keep reva as light as possible in that regard or spare the efss ?)

@redblom well someone would have to traverse the tree to be sent out and execute du on it: if it is the Reva gateway implementing the loop, the Reva storage providers (and the underlying EFSSs) have no extra requirement as it will just be a bunch of stat calls. Otherwise, each storage provider (or ultimately the EFSS? but there's no such functionality via WebDAV AFAIK) would have to implement such a discovery.
I'd implement it in the Reva gateway, factored out for everyone.

Implemented with https://github.com/cs3org/reva/pull/3891


Support for Qwen models

Any plans to support quantitative reasoning for qwen models?

We have apply AWQ on Qwen models, as same as other LLMs

Qwen

same as other LLMs, we fail to  apply awq in deepseek-v2 caused on unsupported module like mla(multi-latent attention)

We have apply AWQ on Qwen models, as same as other LLMs

Hi, how about the ppl of wikitext 2 ?


Disable check_freq in testing util.

We'd disable check_freq for checking the freq in DatetimeIndex because so far we don't provide freq in DatetimeIndex.

Let merge this now.

Thanks, the change is super helpful!


Possible docstring error for DataFrame.quantile

Out of curiosity I decided to see how approximate quantiles are calculated in Dask. I've followed the past bug reports and the move to tdigest so I can see that there's some flux. I think that the DataFrame.quantile docstring might be in error, but I can't easily follow the code to check.
Specifically for DataFrame.quantile the docstring states Approximate row-wise and precise column-wise quantiles of DataFrame which feels back to front - aren't the column-wise quantiles calculated over partitions and so are approximate, whilst the row-wise quantiles will be complete in a partition so will be precise? If that's the case then the fix is to swap "approximate" and "precise".
This is referenced here on the current version of Dask:

https://github.com/dask/dask/blob/main/dask/dataframe/core.py#L2392
https://docs.dask.org/en/latest/generated/dask.dataframe.DataFrame.quantile.html#dask.dataframe.DataFrame.quantile

The equivalent Series method notes Approximate quantiles of Series.
Apologies if I'm missing something and causing noise!
This worked example shows that a Pandas DataFrame and a Dask DataFrame with npartitions=1 for column-wise quantile give the same result, but for npartitions=2 (and higher) we get a slightly different, approximate, result. The final part shows the same for row-wise quantiles and at least in this case the result is identical.
import pandas as pd
import dask.dataframe as dd
import numpy as np

ser = pd.Series(np.arange(0, 100))
df = pd.concat([ser]*10, axis=1)
df.shape # (100, 10), 10 columns of numbers
df.quantile(0.5) # 10 rows of identical results
0    49.5
...
9    49.5
ddf_p1 = dd.from_pandas(df, npartitions=1)
ddf_p1.quantile(0.5).compute() # same result as for Pandas
0    49.5
...
9    49.5

ddf_p2 = dd.from_pandas(df, npartitions=2)
ddf_p2.quantile(0.5).compute() # approximate result with >1 partition column-wise
0    49.0
...
9    49.0

If we calculate row-wise then I see the same result with 1 or 2 partitions:
(df.quantile(0.5, axis=1) == ddf_p1.quantile(0.5, axis=1).compute()).all() # True
(df.quantile(0.5, axis=1) == ddf_p2.quantile(0.5, axis=1).compute()).all() # True

I think you have the notions of row-wise and column-wise flipped. I was not at all confident of this so I looked up the pandas docs where it says:

ref

@jsignell thanks for checking the Pandas docs (and yes, if I was smarter I should have started there!). I've googled through the numpy docs and the only place I see references to column- and row-wise are in relation to stacking of arrays, everywhere else the axis discussion doesn't mention whether you should interpret that as columns or rows.
Being in agreement with the Pandas docs is definitely the right choice.
20 years in and I still don't know my columns from my rows :-) Apologies for the noise!


2FA user is not able to login

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Action Performed:

Open app
Try to login with 2FA account

Expected Result:
user should be able to login
Actual Result:
user is unable to login with 2FA
Workaround:
unknown
Platform:

Where is this issue occurring?

Web
iOS
Android
Desktop App
Mobile Web

Version Number: 1.2.7-0
Reproducible in staging?: Y
Reproducible in production?: N
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
Expensify/Expensify Issue URL:
Issue reported by: @marcaaron
Slack conversation: https://expensify.slack.com/archives/C01GTK53T8Q/p1664223333258679
View all open jobs on GitHub

Closing. dup  https://github.com/Expensify/App/issues/11305

:wave: Friendly reminder that deploy blockers are time-sensitive ⏱ issues! Check out the open StagingDeployCash deploy checklist to see the list of PRs included in this release, then work quickly to do one of the following:

Identify the pull request that introduced this issue and revert it.
Find someone who can quickly fix the issue.
Fix the issue yourself.


Skip relationship query when we know there are none

# when parent_rel_ids = []

def parent_rels
  Relationships.where(:id => parent_rel_ids)
end

# => SELECT * from "relationships" WHERE 1=0

When parent_rel_ids is an empty array, we perform a no-op query. This PR removes this extra query.
numbers

ms
bytes
objects
queries
query (ms)
rows
comments

3,418.4
77,412,641*
4,659,232
81
363.0
2,941
before

3,305.5
76,674,581*
4,375,785
67
409.2
2,941
after

3%
n/a
6%
17%
n/a
0
diff

* Memory usage does not reflect 1,550,176 freed objects.
* Memory usage does not reflect 1,274,302 freed objects.
analysis
Typically, the widget report "Host Summary for VMs", shows a number of skipped queries. But results are data dependent, and some data sets show the same query count for the before and after cases.
Since only non-result queries are skipped, row counts will be identical and timings will only show modest savings. (runtime variances actually showed this query time as higher)

fixed cop.


Review new simplified docs and align with README

With the exception of individial command help, all the docs have been integrated into a single document. The README has been updated to include this document too.

[ ] Revise and proof-read man/man1/fisher.md
[ ] Update README accordingly.
[ ] Add animated Gifs to the README.

Proof-read help wanted.
/cc @pickfire @jethrokuan

proof-read?

Read and mark errors or inconsistencies.

I think it is better to put the code as another color (type):

For the README right? Yes, I agree.
Also, I think the README should be a simplified version of fisher.1.

No, I mean for the man page.

You can't change the color in the man page.

You can use something like:
.RS
.B spt -e 'aplay alarm.wav' -n 'notify-send'
.RE

Ha! Nice trick. I am using ronn to generate the .1 files so those would be overwritten.

@bucaran, I know about that but I think there might be some method to do that in ronn, not sure about ronn, haven't used it.
And the VARIABLES like $fisher_home should be underlined or emphasized.
Idea: A bug section.
BUGS
       Bugs? You must be kidding; there is no bugs in this software. But if we happened to be wrong, please report the bugs!

Noted.

Issues:

fisher help --all is not a legitimate command. Documentation should read fisher help for showing help.
Update all plugins in cache should be fisher update -a
Steps to manually submitting plugins are incorrect (need to fork, push, then send PR)

Closing as mostly resolved.


Add the option of choosing the solarized theme when selecting the theme

This PR adds the possibility to select the solarized theme when choosing the theme to install as part of the generated .vimrc file.

Thank you @hamza-tam !


Help! transform-origin: 50% 50% 0px;

I am doing a course on d3 and I have:
var myChart = d3.select('#chart').append('svg')
.attr('width', width)
.attr('height', height)...
When I add: .append('g') to the svg, I am getting the above error. I am getting this from the "user agent stylesheet".
I have tried to override the transform-origin but...no luck. What am I doing wrong?
I am using Codekit which compiles the js with no errors but warnings that d3 is not defined...but it seems to work until the ('g') is added!
Thanks!

Oh...svg:not(:root). Is it because I have buried the page I am working on?

I got it, I think. I moved the ('g') down past the svg definition and appended it to the enter(). It appears to be working.


Bug bounty test - PLEASE DO NOT APPROVE. qwbhjk

Bug bounty test - PLEASE DO NOT APPROVE. qwbhjk

Closing this PR as it seems malicious. Please comment if you think otherwise.


[Reshaped] Provide visual feedback for prepared spells

Would it be possible to highlight prepared spells if the filter is selected instead of hiding un-prepared?
Or gray-out the not-prepared (opacity 70% or something).
I think this would be more usability-friendly, because spells remain in their positions and you dont loose oversight of your learned spells (especially useful for wizards).

The goal of filtering is to hide everything that isn't currently being filtered for.
The only issue is the way it's laid out (2 columns) means that the item is just hidden, not removed from the DOM so you get some blank lines, but that shouldn't be an issue especially now that you'll only see the gray bar for spells when in presentation mode (when you'd be filtering).

The use-case I'm looking at is switchting prepared and not-prepared spells after a long rest.
Would it be ok / possible to include a checkbox when in edit-mode to quickly change prepared-state of spells without opening the settings?

Switching which spells are prepared is something a user will do uncommonly. They'll do it more than most other adjustments under the spell details, but not really enough to assume that all users would want it to be prevalent.
If a user leaves all spells toggled to show details and then turns off edit mode they can then adjust prepared state fairly quickly if they turn on edit more.

But the spells-list can get pretty clusted if you are a higher level.
Consider the cleric who knows every spell which he has slots for; granted you dont need to add them all, but after some time the list gets pretty long.
A wizard can potentially know even more spells.
But you are probably right in that this is not a common task. I will wait for further feedback from my cleric and wizard players ;)

I will close this issue, as it seems not to be a common use-case.


Update zio, zio-test, zio-test-magnolia, ... to 1.0.13

Updates

dev.zio:zio
dev.zio:zio-test
dev.zio:zio-test-magnolia
dev.zio:zio-test-sbt

from 1.0.12 to 1.0.13.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "dev.zio" } ]

labels: library-update, early-semver-patch, semver-spec-patch, commit-count:1

Codecov Report

Merging #202 (b64a35a) into master (f8261e7) will not change coverage.
The diff coverage is n/a.

@@           Coverage Diff           @@
##           master     #202   +/-   ##
=======================================
  Coverage   87.30%   87.30%
=======================================
  Files          28       28
  Lines         843      843
  Branches       39       39
=======================================
  Hits          736      736
  Misses        107      107

Continue to review full report at Codecov.

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


access zip folder

How to access optional assets.zip folder?

Hi, sorry for the delay.
You can find a complete example here:
https://pub.dev/packages/download_assets/example
Through the assetsDir property, you will get access to downloaded files.


Update to SenzingAPI 3.8.0

See https://github.com/Senzing/g2-sdk-go/issues/95

Pull requests:

https://github.com/Senzing/senzing-tools/pull/121
https://github.com/Senzing/senzing-tools/pull/127


VIM Command Line ctrl+p only returns last command and ctrl+n doesn't work at all

What could be causing this?

Humm, I am also experiencing this with the latest neovim. I feel like the problem is relatively recent?

Yes, I tried with empty neovim config and still get the same, also with most VSCode plugins disabled. I am thinking recent VSCode updates have broken something about cmdline. Anyone else experience this?

i've had it for a while (even before NVIM 5), but i didn't have a go with an empty config, also i'm on Windows.

Yeah, I am also on windows.

+1

Fixed by #908


The player should be able to enter text into the fields provided for each line of the meme.

closed by pull request

https://github.com/sopra-fs23-group-13/meme-it-client/pull/55


I'd like to join this project's community

Your public repo
https://github.com/wesc/gov4git-identity-public.git
Your public branch
main

Approved.

 Follow up
On Sunday, 10-Mar-24 04:13:01 UTC by Gov4Git dev
@wesc was added to the community.


(3.1.0) hung Jadeite process

I believe that I clicked the close button on the inspector and now the whole process is hung:

I'm going to have to kill the process to move forward ... thank god for auto commit

This is a case similar to #746, in that I was probably prompted (or should have been prompted) to keep changes and I would have answered no ... only this didn't happen during image shutdown  ... It's also worth noting then I was in a phase where I did the same operation (close a dirty inspector) several times in a row, before the the image hung

hung again ... got invalid session, clicked okay the project browser closed and perhaps another and then froze. The window on top appears to be the workspace tab of the console and it would not have been saved, so Jadiete froze before/while bringing up the save dialog:

This bug is old enough and there are enough changes to 3.2.12, dolphin, and 3.7 that I'm closing it.  File new bugs if there are still similar hanging cases.


Log which user enabled expert mode

Probably best to implement this using ContextVar.

Probably best to implement this using ContextVar.

The JWT tokens created by the Inmanta server currently don't include any information regarding the user where the token belongs to. It would be good to include the user in the same way in the token as Keycloak does it. The integration with Keycloak is currently broken when SSL is enabled on the Inmanta server (See: inmanta/web-console#4594). It was decided together with Bart to postpone the implementation of this ticket until the integration with Keycloak is fully working and we have a better view regarding the structure of the payload of the tokens created by Keycloak.


Add logout button to navbar

Added logout link to navbar
Created _signout function to hit devise signout route
Update devise config to allow for get request signout instead of delete default

Thank you so much for this!


Update requirements.txt

openfermionpyscf now requires openfermion>1.0, where some interfaces have changed from the previous versions.

Thanks!


Setup minimum ruff lint

Related to #8481 .

Have we already tried setting up pre-commit.ci?
That might help with testing for lint (as well as having a bot to help fix up changes in PRs 😉)


Change pocket-debug log to log to console

Since logging no longer diverts to S3 buckets, we need to see the pocket-debug logs in the normal log output.

Fixed with branch new-altruists


CSI-1896 add seamless upgrade support

difference from https://github.com/IBM/ibm-block-csi-operator/pull/58:

default images from CR yaml, not from consts
avoid changing a CR that has any image in non-official registry username
minor bug fixes and improvements

It looks good


No response from Adv3

Hello,
I tried to use this tool.
Everything fine with install and run.
Connecting to the printer works also - there is no Error Message.
Send a Command, like M501 or M105 or M104 there is absolutely no response in the Output:.

Can you help me with that?
Regards,
Jochen

Hi Jochen,
is there any output in the command prompt?
if you did not run it with command prompt can you run it with that and tell me the output?
you can do that by going to the folder that the python script is located in in explorer, then pressing the location bar at the top (the bar that has the file path in), then typing in cmd, then pressing enter and typing in python3 (Adv3GUI.py)

Just commenting again because you havent replied


chore: clean up from electra review

Motivation
Address some of the open remarks on https://github.com/ChainSafe/lodestar/pull/6986
Description
Just a bit of clean up

:tada: This PR is included in v1.23.0 :tada:


do not log API keys

API keys are currently being logged along with each request.
They should be hidden as a security measure.

Coverage remained the same at 100.0% when pulling 2ad8404503d584c4c3618851ff7c8eddd778fecc on hide-api-key-logging into 7da4ad14c7054cca4444b8893e73c24d8f7721f5 on master.


Fix windows build

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind design

/kind documentation

/kind failing-test

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area build

/area driver-kmod

/area driver-bpf

/area driver-modern-bpf

/area libscap-engine-bpf

/area libscap-engine-gvisor

/area libscap-engine-kmod

/area libscap-engine-modern-bpf

/area libscap-engine-nodriver

/area libscap-engine-noop

/area libscap-engine-source-plugin

/area libscap-engine-udig

/area libscap
/area libsinsp

/area tests

/area proposals

What this PR does / why we need it:
Fixes the build under Visual C++ and allows for a CMake presets file.
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

NONE

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: geraldcombs
To complete the pull request process, please assign leogr after the PR has been reviewed.
You can assign the PR to them by writing /assign @leogr in a comment when ready.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

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

Hi @geraldcombs. Thanks for your PR.
I'm waiting for a falcosecurity member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
Once the patch is verified, the new status will be reflected by the ok-to-test label.
I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Hi Gerald! Thank you very much for this!
/ok-to-test

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: FedeDP, geraldcombs
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [FedeDP]

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

LGTM label has been added.  Git tree hash: f503810d6cf0385d57aa91f14236b80a276d24f2

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: Andreagit97, FedeDP, geraldcombs
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [Andreagit97,FedeDP]

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


Deprecate this package for 0.12?

I was reviewing https://github.com/paulyoung/purescript-prettier-printer/pull/12 and it looks like this package may be redundant for 0.12 https://github.com/paulyoung/purescript-prettier-printer/pull/12#discussion_r193926849
Thanks for providing this up until now, and apologies in advance if I'm mistaken 🙇

I was thinking something along the lines of what purescript-maps and other packages have done might be helpful.
Something like a migration guide in the README would be good.

Not sure I follow - what has 0.12 introduced? (Genuinely curious as I use this library in a few places)
I think the point could be made that this library is essentially liftEff (and later liftEffect) over a few quickCheck functions - is this a Fairbairn threshold thing?

0.12 made Effect the default for effects, so in https://github.com/paulyoung/purescript-prettier-printer/pull/12, we can just do this:
-import Test.QuickCheck (class Arbitrary, arbitrary, (===))
+import Test.QuickCheck (class Arbitrary, arbitrary, (===), quickCheck)
-import Test.Spec.QuickCheck (QCRunnerEffects, quickCheck)

...and also this:
-spec :: Spec (QCRunnerEffects ()) Unit
+spec :: Spec Unit

Note the use of liftEffect as well.
-it "is a homomorphism from addition to composition" do
+it "is a homomorphism from addition to composition" $ liftEffect do

Oh, I see - spec-quickcheck was useful for hiding away some ugly liftEff and its effects declaration, but now it's only useful for the former?

I think so, but that's what I'm trying to determine with this issue.

This makes sense to me - I think ultimately it'll be @owickstrom's decision, but I agree that there's maybe not a lot of utility here anymore. I'll leave this around for when Oskar has time to review it, but I'm definitely inclined to agree!


Mod Dead?

Anyone know if this mod is still supported by its mod author?

Up until July 17th of this year it was. It may still be, but in order to get more updated info you'll need to go to the social media twitter. At least that is what it says on the curseforge mod page. I hope this answered the question in some form.


Fix for aliases in older IE

for #71, it should work now when in I.E. 9 and somebody has aliased clearTimeout, also comments to help the next poor soul that finds this code and some fixes to make it easier to browser test.

Works for me on:
Chrome_47.0.2526_(Linux_0.0.0)
Chrome_48.0.2564_(Linux_0.0.0)
Edge_13.10586.0_(Windows_10_0.0.0)
Firefox_44.0.0_(Linux_0.0.0)
Firefox_45.0.0_(Linux_0.0.0)
IE_7.0.0_(Windows_XP_0.0.0)
IE_8.0.0_(Windows_7_0.0.0)
IE_9.0.0_(Windows_7_0.0.0)
IE_10.0.0_(Windows_7_0.0.0)
IE_11.0.0_(Windows_7_0.0.0)
PhantomJS_2.1.1_(Mac_OS_X_0.0.0)
Safari_9.0.0_(Mac_OS_X_10.11.0)


"go get -u" couldn't been getting new version(1.0.11) source code and run with android.

Because gdev branch not yet merge to master branch so dependent library not match that had couldn't working.

git clone
cd
git checkout
go build
Also: go to termux home/go/src/github.com/coyove/goflyway maybe can change branch that use "git checkout gdev"

cd $GOPATH/src/github.com/coyove
git clone https://github.com/coyove/goflyway && cd goflyway && git checkout gdev
go build ./cmd/goflyway/main.go

1.0.11a 没在android上测过，还不清楚能不能工作

I had tried it was working!

Thanks so much !!!


Feat/support static cdn deploy

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


Split test module into two modules

To avoid circular dependencies between lib-common code, lib-common test code, and service operator api modules the existing modules/test module split into two:

modules/test contains helpers for handling k8s generic resource
like ConfigMaps
modules/test-operators contains helpers for handling
openstack-k8s-operators specific resources like KeystoneAPI

This way test code in lib-common that covering generic k8s resource handling does not need to depend on openstack-k8s-operators related api structures.
The TestHelper struct is also split into two and the TestHelper in modules/test-operators wraps the generic TestHelper from modules/test. The current users of modules/test needs to be switched over to use module/test-operators as a dependency but otherwise the interface TestHelper interface is kept intact.

Nova-operator adaptation patch https://github.com/openstack-k8s-operators/nova-operator/pull/353

@karelyatin FYI, this lib-common change will need adaptation in neutron- and ovn-operator. But only the import of lib-common/modules/test needs to be changed to lib-common/modules/test-operators. No other issue is expected based on my trial of this in nova-operator.


Add the Telegram bot dependencies and script output to the setup.cfg

The Telegram bot is still part of this package and therefore should be properly functional when installed.
Currently you have to just know that it depends on python-telegram-bot and you cannot invoke the script as an executable. Arguably the Telegram bot should be added to the README as well, however I can see not doing this if it's not expected to be supported. It should at least be functional however.
These are the minimum changes required for the Telegram bot to work out of the box on install of the package.

Closing in favor of merging these changes as part of #7.