javassist.NotFoundException: com.google.android.exoplayer.chunk.Format

Execution failed for task ':app:transformClassesWithBlockCanaryExForappDebug'.

javassist.NotFoundException: com.google.android.exoplayer.chunk.Format

@dadakkk can you tell me your BlockCanaryExPlugin version?

配了
block {
debugEnabled true //enable MethodSampler when debug mode, default true
releaseEnabled false //enable MethodSampler when release mode, default false
excludePackages = [] //exclude the package you don't want to inject MethodSampler, eg: ['com.android', 'android.support']
excludeClasses = [] //exclude the class you don't want to inject MethodSampler
includePackages = [] //only include the package you want to inject MethodSampler, packages which don't included will not be injected
  scope {
      project true //inject MethodSampler for app project, default true
      projectLocalDep false //inject MethodSampler for app libs(eg: .jar), default false
      subProject true //inject MethodSampler for subProject of app project, default true
      subProjectLocalDep false //inject MethodSampler for subProject libs, default false
      externalLibraries false //inject MethodSampler external libs, default false
  }

}
报
transformClassesWithBlockCanaryExForDebug'.

javassist.CannotCompileException: cannot find com.sun.msv.datatype.xsd.XSDatatype

没配之前可以编译通过
project gradle
classpath 'com.letv.sarrsdesktop:BlockCanaryExPlugin:<IP_ADDRESS>'
module gradle:
apply plugin: 'blockcanaryex'
compile 'com.letv.sarrsdesktop:BlockCanaryExJRT:<IP_ADDRESS>'

你可以点击Run with --stacktrace，然后把stacktrace信息给我么？

2017-06-27 15:30 GMT+08:00 Lu Meng<EMAIL_ADDRESS>
配了
block {
debugEnabled true //enable MethodSampler when debug mode, default true
releaseEnabled false //enable MethodSampler when release mode, default
false
excludePackages = [] //exclude the package you don't want to inject
MethodSampler, eg: ['com.android', 'android.support']
excludeClasses = [] //exclude the class you don't want to inject
MethodSampler
includePackages = [] //only include the package you want to inject
MethodSampler, packages which don't included will not be injected
scope {
project true //inject MethodSampler for app project, default true
projectLocalDep false //inject MethodSampler for app libs(eg: .jar), default false
subProject true //inject MethodSampler for subProject of app project, default true
subProjectLocalDep false //inject MethodSampler for subProject libs, default false
externalLibraries false //inject MethodSampler external libs, default false
}
}
报
transformClassesWithBlockCanaryExForDebug'.
javassist.CannotCompileException: cannot find com.sun.msv.datatype.xsd.
XSDatatype
没配之前可以编译通过
project gradle
classpath 'com.letv.sarrsdesktop:BlockCanaryExPlugin:<IP_ADDRESS>'
module gradle:
apply plugin: 'blockcanaryex'
compile 'com.letv.sarrsdesktop:BlockCanaryExJRT:<IP_ADDRESS>'
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/seiginonakama/BlockCanaryEx/issues/15#issuecomment-311276697,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ALOaMSMkUJxzW7MljX9DeIo8HaXXEaoJks5sIK98gaJpZM4NnaVH
.

Hi!
I have a similar problem:
`Error:Execution failed for task ':MyDemoApp:transformClassesWithBlockCanaryExForDebug'.

javassist.NotFoundException: retrofit.client.RequestUse project gradleclasspath 'com.letv.sarrsdesktop:BlockCanaryExPlugin:<IP_ADDRESS>'`
module gradle:

apply plugin: 'blockcanaryex'
compile 'com.letv.sarrsdesktop:BlockCanaryExJRT:<IP_ADDRESS>'

issue fixed at <IP_ADDRESS>
buildscript {
    repositories {
        jcenter()
    }
    dependencies {
        classpath 'com.android.tools.build:gradle:1.5.0' //version must >= 1.5.0
        classpath 'com.letv.sarrsdesktop:BlockCanaryExPlugin:<IP_ADDRESS>'
    }
}


Update version to 0.0.34.

#1234  👈
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @rohinb2 and the rest of your teammates on  Graphite

Merge activity

Sep 4, 1:58 PM EDT: @rohinb2 started a stack merge that includes this pull request via Graphite.


Breadcrumbs coming from wrong runtime

Environment
How do you use Sentry?
Sentry SaaS (sentry.io)
Which version of the SDK?
Unreal Upload Endpoint
Steps to Reproduce
Upload two log files, breadcrumbs seem to be coming from the latter rather than the former.
Expected Result
Breadcrumbs come from former file.
Actual Result
Breadcrumbs come from the wrong file.

More specific troubleshooting info available in https://getsentry.atlassian.net/browse/FEEDBACK-2112

Looks like this got dropped completely. The details on Jira might be helpful. It's useful to know which customer too.

This is related to unreal.crashreporter and not this plugin btw

Based on the additional context this is a processing issue in relay. Depending on which order the logfiles get processed (i.e. alphanumerical?), different logs make it into breadcrumbs.
https://github.com/getsentry/relay/blob/1a56dbc5a0b8e5d0ab8b892b0eee097f7165e072/relay-server/src/utils/unreal.rs#L125


How to release iOS package on Macbookpro without an iOS device?

Hi, I followed this ios guide https://flutter.io/docs/deployment/ios. but in my Xcode, it reports the error Failed to create provisioning profile. There are no devices registered in your account on the developer website. Plug in and select a device to have Xcode register it. in Review Xcode project settings section after choosing my team.
But I don’t have any apple devices. How to fix it? I did google it. I don’t really find any solutions that work or I can understand.. such as link1 or link2.
Are there any easy way to solve this error? Thanks a lot.

Have you selected Product > Destination > Generic iOS Device and then created an archive Product > Archive

@peterlazar1993 thank you very much for the reply. Sorry, I haven't tried that. The Xcode UI completely confuses me.
I can not test this anymore because I borrowed an iphone device from my friend and registered it in Xcode, and continued on next steps after searching for 2 hours without a clear help guide.
I think I simply close this issue and assume the step you provided should work. I hope this can be documented in https://flutter.io/docs/deployment/ios.
Thank you very much again for this help.


Explain how to use constraints in UCP

DDC has docs that explain how to apply labels to nodes . Now we need a user guide explaining how to leverage this and deploy a simple service that is scheduled on a node that meets certain criteria.

I will start working on it


Autocal relies on legacy (non-LMfit-based) fitters

Original report by Joseph Fowler (Bitbucket: joe_fowler, ).

Lots of test warnings are here to remind me that autocal uses a lot of legacy fitters. I never use autocal, because I never had much luck with it. If anyone else does, though, we should replace the deprecated legacy fitters with the new LMfit-based ones.

Original comment by Joseph Fowler (Bitbucket: joe_fowler, ).

Removing milestone: v0.7 (automated comment)

Original comment by Joseph Fowler (Bitbucket: joe_fowler, ).

Autocal uses modern line models + LMfit
Fixes #203


ERROR: Unable to download webpage: HTTP Error 403: Forbidden (caused by HTTPError());

Checklist

[X] I'm reporting a broken site support issue
[X] I've verified that I'm running youtube-dl version 2021.04.26
[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 bug reports including closed ones
[X] I've read bugs section in FAQ

Verbose log

C:\Users\Raulp\Downloads\Download SRT>youtube-dl --skip-download --write-sub --sub-lang ptBR --sub-format "ass" "https://www.crunchyroll.com/pt-br/food-wars-shokugeki-no-soma/episode-3-the-generation-of-prodigies-715213"
[crunchyroll] 715213: Downloading webpage
ERROR: Unable to download webpage: HTTP Error 403: Forbidden (caused by HTTPError()); please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.

Description

I am trying to download a subtitle from a episode but i cant.
Please help. Thank you

Exporte os cookies da sua sessão Crunchyroll, é necessário!
Para isso, use uma extensão apropriada. Recomendo o: Get cookies.txt

Adicione na sua linha de comando
--cookies cookies.txt

Obs: Caso tente utilizar os cookies numa máquina com IP diferente, irá falhar, continuará retornando 403!


add unit test for TableConfig constructor

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

Project coverage is 0.00%. Comparing base (59551e4) to head (185c157).
Report is 793 commits behind head on master.

:exclamation:  There is a different number of reports uploaded between BASE (59551e4) and HEAD (185c157). Click for more details.
HEAD has 53 uploads less than BASE

Flag
BASE (59551e4)
HEAD (185c157)

integration
7
1

integration2
3
1

temurin
12
1

java-21
7
1

skip-bytebuffers-true
3
1

skip-bytebuffers-false
7
0

unittests
5
0

unittests1
2
0

java-11
5
0

unittests2
3
0

integration1
2
0

custom-integration1
2
0

Additional details and impacted files
@@              Coverage Diff              @@
##             master   #13672       +/-   ##
=============================================
- Coverage     61.75%    0.00%   -61.76%
=============================================
  Files          2436     2479       +43
  Lines        133233   136816     +3583
  Branches      20636    21299      +663
=============================================
- Hits          82274        0    -82274
- Misses        44911   136816    +91905
+ Partials       6048        0     -6048

Flag
Coverage Δ

custom-integration1
?

integration
0.00% <ø> (-0.01%)
:arrow_down:

integration1
?

integration2
0.00% <ø> (ø)

java-11
?

java-21
0.00% <ø> (-61.63%)
:arrow_down:

skip-bytebuffers-false
?

skip-bytebuffers-true
0.00% <ø> (-27.73%)
:arrow_down:

temurin
0.00% <ø> (-61.76%)
:arrow_down:

unittests
?

unittests1
?

unittests2
?

Flags with carried forward coverage won't be shown. Click here to find out more.

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

Ready for review

rebased


Add additional checks when inferring dataType in "parseRawData"

What's this PR do?
When inferring the dataType, dataset, and schema for a
select_unique query response, keen-js breaks.
parseRawData can't find a "target property" because it's identifying
some select_unique queries as a "Funnel" dataType.
PR adds a few more checks in parseRawData to prevent that error from
happening. Originally I wanted to refactor parseRawData to take an
analysis type from the query and to make future testing easier, but
I'm still unfamiliar with a lot of the other types of queries we can
run on explorer, so I am saving that for a later date. The WIP branch
for those changes are in jc-parse-result-refactor.
Where should the reviewer start?

look at src/dataviz/lib/parseRawData.js

How should this be manually tested?

Go to explorer, start creating a select_unique query, and select a target
property that is a number type (ex: customer ids)

What are the relevant tickets?
https://github.com/keenlabs/data-tools/issues/283

:+1:


Find box is superimposed

VSCode Version: August 2019 (version 1.38)
OS Version: MAC OS High Sierra

Steps to Reproduce:

change tab file

/needsMoreInfo
Please paste a screenshot


Updating solution

Fixes #2
Run bundle install rake db:migrate and learn and this solution passes all tests. The other solution does not.
Because I built my solution off of master, it will not auto-merge with current solution branch. Best I can think to do is clone and git push origin solution -f.
@AnnJohn @pletcher @PeterBell @aturkewi

I'm not sure if we want to force push here. Could you merge your changes locally and resolve merge conflicts there?

A few comments, but most are very minor. Thanks for putting this together!

Also, just to document: @aturkewi suggested moving the old solution branch to something like old-solution, just so that we keep that history around; but then we'll force push these changes up.

@pletcher Updated per comments.

Hm, it looks like changes didn't come through. Could you push again?

@pletcher @PeterBell Sorry guys, got two remotes on this one. Pushed to my student one instead. All set now.

Looks good! Let's go ahead and move the current solution branch to old-solution (or something) and push this one up as the new solution.

@pletcher I'm on it


switch order of arguments of subroutine LDASsa_get_pert()

subroutine LDASsa_get_pert() expects the following arguments:
N_pert, N_ens,                                 &
pert_grid_f, pert_grid_l,                   &
...
Note that pert_grid_f comes first, then pert_grid_l.  This order was inherited from LDASsa and is different from that in subroutines GEOSldas_get_pert(), GEOSldas_propagate_pert(), and LDASsa_propagate_pert().  In the latter three subroutines, pert_grid_l comes first, then pert_grid_f.
To avoid confusion and errors in the future, switch the order of pert_grid_f and pert_grid_l in LDASsa_get_pert() to match that of the other 3 subroutines.
In a code review, @gmao-rreichle found only one single (relevant) call to LDASsa_get_pert() from clsm_ensupd_upd_routines.F90.   Need to double-check and test carefully for 0-diff.

addressed with #278


Remove support for macOS

As soon the initializer Image(systemName:) doesn't have support to macOS yet, in my point of view, doesn't make sense to support the platform yet.
Checking SwiftUI headers, specifically for the init method mentioned above, macOS/OSX is currently unavailable, for this reason I'm creating this pull request.
Here the snippet of code extracted from SwiftUI headers:
@available(iOS 13.0, tvOS 13.0, watchOS 6.0, *)
@available(OSX, unavailable)
extension Image {

    @available(OSX, unavailable)
    public init(systemName: String)
}

Thanks @unnamedd for noticing and fixing this! 👍


SimpleWebServer crashes on static initializer

Hi everyone!
I faced an issue while trying to use nanohttpd-webserver in my android app:
java.lang.NullPointerException: Attempt to invoke virtual method 'int java.io.InputStream.read(byte[])' on a null object reference
        at fi.iki.elonen.SimpleWebServer.<clinit>(SimpleWebServer.java:83)

This is actually happens because InputStream of LICENSE.txt is null and static initializer catches only IOException
    static {
        mimeTypes();
        InputStream stream = SimpleWebServer.class.getResourceAsStream("/LICENSE.txt");
        ByteArrayOutputStream bytes = new ByteArrayOutputStream();
        byte[] buffer = new byte[1024];
        int count;
        String text;
        try {
            while ((count = stream.read(buffer)) >= 0) {
                bytes.write(buffer, 0, count);
            }
            text = bytes.toString("UTF-8");
        } catch (IOException e) {
            text = "unknown";
        }
        LICENCE = text;
    }

Does anybody know what can be done about it? I simply can't start web server because of that.
Thanks in advance!

How about NOT deleting LICENSE.TXT, so that the stream isn't null? ;)
You're not supposed to edit or remove the license of something you don't own.

Who said that I'm deleting it? I can't modify dependency library included via gradle compile function. So the library is not modified in any ways.
(Included via compile 'org.nanohttpd:nanohttpd-webserver:2.2.0')

Then the file should be there. And if the file is there, it shouldn't have a null stream.
I shouldn't have assumed you deleted it though...

Ok, I kant imagine what the reason is that the license text is not found but I just extended the try a little to cover anything with the licence going wrong. Please try the SNAPSHOT and report back here.

Apparently, Android Studio excludes all unnecessary files when it packs .apk file and I don't know how to make it include this license. But I made a small pull request that solves this issue.

Thanks.


[nbc] unescape url before sending (close #17374)

Before submitting a pull request make sure you have:

[x] At least skimmed through adding new extractor tutorial and youtube-dl coding conventions sections
[x] Searched the bugtracker for similar pull requests
[x] Checked the code with flake8

In order to be accepted and merged into youtube-dl each piece of code must be in public domain or released under Unlicense. Check one of the following options:

[x] I am the original author of this code and I am willing to release it under Unlicense
[ ] I am not the original author of this code but it is in public domain or released under Unlicense (provide reliable evidence)

What is the purpose of your pull request?

[x] Bug fix
[ ] Improvement
[ ] New extractor
[ ] New feature

Description of your pull request and other information
The permalink of the video should be un-escaped before sending via JSON request.
Previous pull was #17442, I've closed it by mistake.

Hi,
changed to compat_urllib_parse_unquote, I missed that method.


[Bug]: Exported enums not working on tests

Version
27.1.4
Steps to reproduce

Clone the repo at https://github.com/ibesora/ts-jest-enum
Run npm install
Run npm run test

Expected behavior
Tests should pass
Actual behavior
Tests fail with TypeError: Cannot read property 'Above' of undefined
Debug log
See it here
It was too long to add it here
Additional context
It seems to be a regression of https://github.com/kulshekhar/ts-jest/issues/281
I can update the protomaps package if needed but it doesn't look like it's doing anything weird
Setting isolatedModules to false doesn't change anything
Environment
System:
    OS: Linux 5.13 Ubuntu 21.10 21.10 (Impish Indri)
    CPU: (16) x64 11th Gen Intel(R) Core(TM) i9-11980HK @ 2.60GHz
  Binaries:
    Node: 16.8.0 - ~/.asdf/installs/nodejs/16.8.0/bin/node
    Yarn: 1.22.15 - ~/.asdf/installs/nodejs/16.8.0/.npm/bin/yarn
    npm: 7.21.0 - ~/.asdf/plugins/nodejs/shims/npm
  npmPackages:
    jest: ^27.5.1 => 27.5.1

Hi, any update on this?

We just noticed this while working on Jest 28 support, will try to fix this issue.

Also facing the same issue, hope it will be fixed soon.

@ibesora @kudryashov13 In case you didn't see, a way to tackle the issue while it's being fixed has been found here https://github.com/kulshekhar/ts-jest/issues/281#issuecomment-500780488

Please fix this, it's affecting our core testing functionality

Hey, any update on this one? I can confirm tests still fail using ts-jest v28.0.8 with jest v28.0.3 and v28.1.3.
Thank you!

I am facing the same problem on version 28.0.1, @ahnpnl is there any update on this?

the protomaps does not do preserveContEnums in the tsconfig, so it is not preserved in the transpiled output
you can't import something that is not there

the protomaps does not do preserveContEnums in the tsconfig, so it is not preserved in the transpiled output
you can't import something that is not there

That doesn't seem to make a difference at all.

Hey, any update on this?

I'm having the same problem. It could be a Circular imports issue. However, I am still trying my test to find or come up with a solution.

https://github.com/kulshekhar/ts-jest/pull/308/files

I've had success mocking the enum and returning an object instead.

Hi guys, this is still problem...any news when it will be fixed?
"jest": "29.7.0",
"ts-jest": "29.1.2",

I've had success mocking the enum and returning an object instead.

Can you show your solution ?
I'm having this frustrating issue too.


Switch back to informalsystems hermes image

Summary
https://github.com/cosmos/ibc-go/pull/4535 switches the hermes image to use a custom image I built with ubuntu 22 as the operating system.
We can switch back once a new image has been built by informal systems following the closure of this issue https://github.com/informalsystems/hermes/issues/3580

For Admin Use

[ ] Not duplicate issue
[ ] Appropriate labels applied
[ ] Appropriate contributors tagged/assigned

We can switch back with hermes releases v1.7 (end of September).

We switched back here to tag from master. We can still update to v1.7 when it gets out.


All attempted blocks return errors.

The extension is completely non-functional, now.
I noticed it a few days ago.
EDIT: someone else has noticed this issue as well, see screen cap below

Still works for me. Additional info? Can you provide screenshots of web inspector? network tab? error'd out request responses?

Looks like Twitter may be blocking the extension, it returns a 403 error.

it's possible you are being throttled. have/had you been using the extension extensively before the errors started happening?
the web API calls our tool uses have relatively high API call limits since it's intended to be used by the twitter app and not our extension. that being said, those API call limits are undocumented, so i have no idea when that throttling starts to occur.
you may have luck trying the extension on another computer or waiting out out the throttling if that's what's happening. if its still broke after 24 hours, checking the request response in the network tab would be my next ask to try and figure out whats going on

Rotating the block chain will continue to produce an error that was not in the past.
You could just a few months ago, if you ran over a thousand people around a block chain, you could get a block.
Now, if I turn on the current program, I keep getting errors.
It looks like a program error. Please look at it and fix it.

This is how the error will occur. I think it's a program error.
Apparently, a few months ago, I turned around this program to spin blocks with more than 1,000 accounts.
And then I said, " Well, it's a mistake, but I just switched it today for the first time. I always don't want to create an account.
I used this program without any errors. Therefore, please check. There is no problem with the computer at all. because
I've been using this program on my own computer.I am very sad.
I would like to use this program without any errors.

@kmkm0408 can you please click one of the "block" entries in the list from your screenshot. Then, copy+paste the text from the "Preview" or "Response" tabs?

If you press it as you want, I will be Korean. Is it okay?
{"message":"해당 작업을 실행하실 수 없는 계정일 수 있습니다. 이 페이지 새로 고침 을 하신 후에 다시 시도해주세요."}
A brief description would suggest that the account is not capable of running the task. Then, I would like to refresh the page and try again. But if it's a simple error, every account I want to use a chain block has this error.

@kmkm0408 thank you! that's very strange. I am unsure if this is a problem with the program or with twitter. I'm trying to debug it...

You mean it could be an internal stream of Twitter?

@kmkm0408 yes, its possible that twitter's servers are preventing the addition of blocks either due to throttling (artificial limit of the number of blocks) or due to server overload...

But if you search, you'll also find some people who can run programs.

@kmkm0408 yes i am aware. i am included in that group. however, twitter is known to throttle certain IPs/browsers when too many requests are made. Additionally because twitter is a network of servers, some regional servers may be overloaded while others may not. it's hard for me to debug with twitter doesn't give me enough information.

If there is any error in the program, please correct it and let me know because I desperately need to write the program.

I would like to use this program for a long time. Please, it is just a program error.

@kmkm0408 have you tried signing out and signing in again, then trying to use twitter block chain again?

@cristynhoward @Phrobbert could you two both give me response bodies similar to how kmkm0408 did? thank you.

Yes, of course I've logged out and run the program, but it hasn't run. I think there is a kind of a reaction like this @Phrobbert

Please let me know exactly what I need to tell you. I'll give you my best answer.

@satsukitv Isn't this a program error?

I started seeing this issue as well earlier today. Running Twitter Block Chain on a list of followers results in 403 Forbidden errors for each follower it attempts to block, each with the response:
{"message":"Your account may not be allowed to perform this action. Please refresh the page and try again."}

Using block directly through the twitter.com web interface continues to work properly, so if it's a rate-limiting issue, the official web interface doesn't seem to be affected.
I also attempted signing out of Twitter and back in, which did not fix the issue.
I do notice a difference in the request form data for the web interface vs TBC. I'm not sure it's significant, but I'll provide it. Sensitive info such as auth tokens and user IDs redacted, but they remain identical between the two requests. Both requests seem to be hitting the same URL (https://twitter.com/i/user/block).
Block request via twitter.com web interface (works correctly):
authenticity_token: [REDACTED]
challenges_passed: false
handles_challenges: 1
impression_id:
user_id: [REDACTED]

Block request via TBC (403 error):
authenticity_token: [REDACTED]
block_user: true
impression_id:
report_type:
screen_name: [REDACTED]
user_id: [REDACTED]

Let me know if there's additional info that would be helpful tracking this down!

Hello! Then, do you think it is an internal problem on Twitter or an error on this program? @ystros

Hi.
I use this and "Twitter One Click Block" extension, and both could not be used at the same time from some day before. So I guessed that there was any change on Twitter.
"Twitter One Click Block" error is fixed yesterday. maybe they have some hint to fix.

Late returning to this thread but I get the same results as Ystros.

message:"Your account may not be allowed to perform this action. Please refresh the page and try again."

hi folks. if i get time this weekend i will try and release an update that may help. without experiencing this issue myself it's going to be difficult to provide a quick solution, though.

Haven't you experienced this error yet?

I'd like to know if I still haven't resolved my program errors.

I'd like to know if I still haven't resolved my program errors.

Late getting back to this thread, but more diagnostic info can't hurt. I'm getting exactly what the other users have reported.
Using Chrome 65.0.3325.181 on Mac OS X El Capitan 10.11.6.

Each failed block results in status 403 and a "Response" message reading

{"message":"Your account may not be allowed to perform this action. Please refresh the page and try again."}

And I also noticed a similar request format discrepancy to the one that user ystros mentioned.
Failed block attempts via the extension have the format:

authenticity_token: REDACTED
block_user: true
impression_id:
report_type:
screen_name: REDACTED
user_id: REDACTED

whereas successful ones made using the web interface have the format:

authenticity_token: REDACTED
challenges_passed: false
handles_challenges: 1
impression_id:
lang: en
user_id: REDACTED

I am seeing this issue as well today (though I haven't tried running this extension in a while).
I am using a Asus Laptop running Windows 10.
Request Headers:
Request URL: https://twitter.com/i/user/block
Request Method: POST
Status Code: 403
Remote Address: <IP_ADDRESS>:443
Referrer Policy: no-referrer-when-downgrade

Response:
{"message":"Your account may not be allowed to perform this action. Please refresh the page and try again."}

None of the blocking actions succeeded for the initial run, or the run I did a little later to make sure I wasn't being throttled. I hadn't used this plugin in at least a month previously.
Let me know if I can offer any more information or do anything to help debug. This is an excellent plugin!

I am getting the same errors. No one I block actually gets blocked. It used to work for me.

Have you found the cause of the error yet? Or are you in a situation where you can't solve the error because it's internal to Twitter? I want to know.

Currently Chrome has a bug where the content_scripts injected into a page, from an extension, are not considered to be on the same site as the page itself. So sites that utilize SameSite cookies will not be able to send requests with those cookies attached.
https://groups.google.com/a/chromium.org/forum/#!msg/extensions-reviews/SoLuNWUCvnA/d8aAhyxzAAAJ
Fortunately, Firefox doesn't have this problem. I have updated the Firefox plugin to the latest version (thanks @gaeulbyul for putting in the work on that code).
https://addons.mozilla.org/en-US/firefox/addon/twitter-block-chain/
For now I am going to leave this issue open while I weigh options for trying to get the Chrome version working again.

Update: Chrome Beta (67) has the code to fix the issue. When Chrome 67 hits stable the extension will be usable again on normal Chrome installations. Closing the issue since there two workarounds and a fix will eventually be delivered through standard Chrome updates.

6 more days :^)

chrome 67 is rolling out! please check for updates in chrome and report back if there are any issues on chrome 67! Thank you!


Fallback font support

When a glyph does not exist in the primary font, it should look in a list of other candidate fonts to find it (like in prawn, see https://github.com/prawnpdf/prawn/issues/103)

+1
Some notes.

Sometimes characters not found in the default or embedded font make all the text scrambled, even simple ASCII chains.

Someteimes if I embed big font (arialuni.ttf) I get completely blank document.

Is there any update on this feature? I need it.

Doesn't PDF allow to have text without any embedded fonts and then it's up to the rendering program or OS to select a default font?
It would be great if that was an option. Then instead of saying document.font('Helvetica') you could leave the default and for Chinese, Korean, Japanese, Greek, Russian, etc. you'd still get readable PDFs.

Has anyone managed to figure out a good strategy to allow fallback fonts?
Been having some trouble rendering such sentences which consists of a combination of various languages (Vietnamese, and Chinese):
doc
  .fontSize(12)
  .font('Semibold')
  .text('Hanoi Hotel, Trần Huy Liệu, Giang Vo,巴亭郡河内越南', 166, 468, {
    width: 370,
  })

Ok, just an update, I decide to use [arial unicode] for the pdf generation instead of the project's main font (which uses PingFang SC). It wasn't ideal, but arial unicode was a good compromise as it supports a variety of languages which is perfect for internationalisation.  (https://catalog.monotype.com/family/monotype/arial-unicode)

I found a workaround!
Follow these instructions
(You might have to use the 10 day trial | or use opensource FontForge but that did not work that good)
With these steps you can merge multiple fonts so there is no need for a fallback font.
Works pretty good! :)


Uni v3 mai usdc

Sync complete @ https://thegraph.com/hosted-service/subgraph/abtheo/otter-development

tried maiMarketValue and usdcMarketValue, both are zero 🤔

tried maiMarketValue and usdcMarketValue, both are zero 🤔

Fixed this issue, but now the Kyberswap revenue is broken 😅
Resyncing now. Need to double check the total daily revenue is correct before merging

tried maiMarketValue and usdcMarketValue, both are zero 🤔

Fixed this issue, but now the Kyberswap revenue is broken 😅
Resyncing now. Need to double check the total daily revenue is correct before merging

huh, why KNC/LDO affects by the fixes? 😅

@0xthk  Sync complete, ready for review & merge;


fix type for image_url

[x] I understand that this repository is auto-generated and my pull request may not be merged

Changes being requested
According to the official document, we can specify string url directory to the image_url for gpt-4-vision-preview.
So I made a PR to fix the type error

Additional context & links
https://platform.openai.com/docs/guides/vision

Because ImageURL is defined by the interface, we cannot use union type.

Oh, this is autogenerated.
So, I'll create a new PR on openAPI


BUG/1472 adapt order in which assets are deployed for inter-type dependencies

PR details
What changes did you make? (Give an overview)

closes #1472

Checklist

[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] test scripts updated
[ ] Wiki updated (if applicable)

needs a complete rewrite of the upsert method to process things sequentially like for folders


Add config() example to snowflake warehouse size

Description & motivation

Simple addition -- I noticed it only suggests the .yml file way, but doesn't explicitly show the .sql way using a config block. added it in!
To-do before merge

Prerelease docs
If this change is related to functionality in a prerelease version of dbt (delete if not applicable):

[ ] I've added versioning components, as described in "Versioning Docs"
[ ] I've added a note to the prerelease version's Migration Guide

Checklist
If you added new pages (delete if not applicable):

[ ] The page has been added to website/sidebars.js
[ ] The new page has a unique filename

If you removed existing pages (delete if not applicable):

[ ] The page has been removed from website/sidebars.js
[ ] An entry has been added to _redirects
[ ] Run link testing to update the links that point to the deleted page

thanks for opening this up and contributing @patkearns10 ! I've left some suggesting and let me know what you think! also waiting to see if i add tabs instead

Thank you for your help @mirnawong1 !

no worries at all :D!


[Bug]: Icon Button tag crosses the canvas boundary when placed in the left border

Is there an existing issue for this?

[X] I have searched the existing issues

Description
When we place the Icon button widget on the extreme left border of the canvas, its tag crosses the canvas boundary. This behaviour does not happen when we place the widget on the extreme boundary.
https://www.loom.com/share/d1e88857f22c4ce9b135774423862a27
Steps To Reproduce

D&D an Icon button widget on the extreme left border of the canvas.

Public Sample App
No response
Version
Cloud

Related to edge-cases in canvas, not controlled in appviewers


Update cvodes to 3.1.0

Submission Checklist

[x] Run unit tests: ./runTests.py test/unit
[x] Run cpplint: make cpplint
[x] Declare copyright holder and open-source license: see below

Summary:
This PR address issue #743 .
Use CVODES 3.1.0 for its new matrix & linsol API. This makes linear solver tuning more accessible, as well as provides CUDA API support.
Due to change of API, the initialization of the matrix solver in BDF is changed. The original workflow includes generating dense linsol using CVDense, which has been removed since SUNDIALS 3.0.0.
The updated approach is:

create Jacobian matrix skeleton using SUNDenseMatrix
create linsol object using SUNDenseLinearSolver
attach linsol object to CVODES pointers

The makefile changes accordingly by including sunmatrix and sunlinsol headers.
Intended Effect:
Using new CVODES API
How to Verify:
unit tests
Side Effects:
N/A
Copyright and Licensing
Please list the copyright holder for the work you are submitting (this will be you or your assignee, such as a university or company):
Metrum Research Group, LLC
By submitting this pull request, the copyright holder is agreeing to license the submitted work under the following licenses:

Code: BSD 3-clause (https://opensource.org/licenses/BSD-3-Clause)
Documentation: CC-BY 4.0 (https://creativecommons.org/licenses/by/4.0/)

quickly going over this I notice that you initialize the dense LA solver regardless of using the adams or bdf. Last time I looked into this, it was not needed to initialize the LA solver whenever the adams is being used. In fact, initializing the LA solver whenever adams was used even lead to memory issues.
Is it possible to not initialize the LA solver in case the adams is being used?
Oh... now I see. You are using CV_ADAMS and CV_NEWTON for the adams solver. This should probably have been asked in the adams pull which was to quick for me... but how come you use CV_ADAMS, CV_NEWTON for the adams case? The manual from  CVODE clearly recommends for non-stiff problems to use (CV ADAMS, CV FUNCTIONAL) which avoids the use of the costly Newton iterations.
What is the rationale to deviate from their recommendation?
Thanks.

The main reason is that Newton gives 2nd-order convergence and fixed-point
iteration is linear. The other reason is fixed-point is more likely to
spider away so less robust.
I know I should have done some profiling, I was being lazy....
Y
Regards,
Yi Zhang
metrumrg.com
On Thu, Feb 1, 2018 at 7:15 AM, wds15<EMAIL_ADDRESS>wrote:

quickly going over this I notice that you initialize the dense LA solver
regardless of using the adams or bdf. Last time I looked into this, it was
not needed to initialize the LA solver whenever the adams is being used. In
fact, initializing the LA solver whenever adams was used even lead to
memory issues.
Is it possible to not initialize the LA solver in case the adams is being
used?
Oh... now I see. You are using CV_ADAMS and CV_NEWTON for the adams
solver. This should probably have been asked in the adams pull which was to
quick for me... but how come you use CV_ADAMS, CV_NEWTON for the adams
case? The manual from CVODE clearly recommends for non-stiff problems to
use (CV ADAMS, CV FUNCTIONAL) which avoids the use of the costly Newton
iterations.
What is the rationale to deviate from their recommendation?
Thanks.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/math/pull/744#issuecomment-362248485, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AfkhsMfLKf1XWCscALp7rAAA7a3rj05Nks5tQarJgaJpZM4RzHBu
.

... profiling would be useful as the whole point of the Adams is to be faster for non-stiff problems.

I'd rather think the main point is to achieve higher order. After all we
still have Runge-Kutta.
Regards,
Yi Zhang
metrumrg.com
On Thu, Feb 1, 2018 at 9:49 AM, wds15<EMAIL_ADDRESS>wrote:

... profiling would be useful as the whole point of the Adams is to be
faster for non-stiff problems.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/math/pull/744#issuecomment-362288127, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AfkhsP1zEsElwhtF6mssZaWPhaPOB7iOks5tQc7xgaJpZM4RzHBu
.

also: Could we instead of passing "1" and "2" as argument to the LMM template argument instead use the symbols from CVODES? The CVODES symbols are easier to read and would update automatically should CVODES ever change things internally.

From reading a bit about what high order ode integration means, I understand that high order integration schemes allow for large steps to be made. However, if we can make large steps, then an implicit evaluation scheme appears not necessary to me. This would concur with the recommendation from the cvodes manual to combine adams with an explicit evaluation scheme.
That does not mean that there are problems where the Adams as you have proposed it gives advantages. Cleary, if the price for the implicit steps is not high, then they are more stable.
I have myself tried the Adams in PK/PD problems and I have not found them to be any better than RK45 for non-stiff problems (the set of ODEs I tried is by no means exhaustive!). For stiff problems the BDF approach is clearly best. The integrator which I would actually consider trying out and adding is the Bulirsch-Stör which is part of odeint. For one, the odeint solvers integrate much better with C++ and that integrator is supposed to output very high precision in a fast way. High precision is relevant for HMC to perform well from what I have seen.

@yizhang-cae, can you update the branch to the current state of develop?

Also, please add a license file under licenses/. We're missing one for CVODES. We should include it with this PR.

@syclik, rebased and added license.

Most of them are from previous implementation. I've made update according to the review comment. The only item left behind is the naming such as const size_t N = y0.size(). I'd like to leave it to the original developer.

On Feb 15, 2018, at 8:34 PM, Daniel Lee<EMAIL_ADDRESS>wrote:
...
domain_errors are caught and treated as recoverable exceptions. From NUTS, it's treated as a rejection. There's a chance that the next set of inputs to the log prob function may be computed fine.

I understand the difference in behavior.
What I don't understand is when one behavior or the other should be invoked.  My understanding is that we have:
reject:  an error that might be recoverable
error:  an unrecoverable error
I just don't know why the tolerances fell into the unrecoverable error category and it makes me wonder just how many things we have throwing recoverable errors that are non-recoverable.
A bigger issue is that I don't know of any user-facing doc for this distinction.
We also need an error() statement to allow users to invoke that same behavior where appropriate.

Here, if the relative tolerance is set to a negative value, it was configured improperly

Whenever a function throws a domain_error it was because it was given an illegel input.  So it's that definition of "configured improperly" that's key.  I think what you're getting at is that if it's data, then we can abort rather than waiting to see if the problem corrects itself in a future iteration.

and we do want everything to stop.

This is where I'm not sure where the line is.

We don't have to: if it was a domain_error Stan would run for 100 iterations, spit out rejection messages, then stop. I think that's not ideal.

Agreed.  Is there a way to detect non-recoverable errors? That is, is there a way to show that if a data argument is bad, it'll always be bad?   I just haven't thought it through well enough.

And yes, the check on time should also throw a non domain_error.

OK, that makes more sense, but I still don't know where the line is.
And if we all of a sudden let initial time be a parameter, do we then remove the error and replace with a rejection?

Sorry about the confusion. I like the "reject" vs "error" naming and we can use that going forward.

I just don't know why the tolerances fell into the unrecoverable error category and it makes me wonder just how many things we have throwing recoverable errors that are non-recoverable.

We currently have too many things that are rejections instead of errors -- we haven't done a full sweep of error / rejection handling since we made that distinction.
I think tolerances fell into errors due to at least a couple reasons:

if we pass that into CVODES and let it throw an error, I think it behaves poorly. (I forget if it crashes or passes a completely different type of error that isn't an std::except.)
the tolerances can only be data. I assumed this can't change iteration to iteration, but that's not guaranteed to be true, so perhaps it should be a recoverable error. (You'd really have to try to break it to do something like that, though.)

A bigger issue is that I don't know of any user-facing doc for this distinction.

We've got some conflicting doc now (stan reference 2.17.0). Appendix D says

An example warning message is an informational message about ill-formed input to an underlying function, which results in a Metropolis rejection during sampling or a reduction in step size for optimization, without causing a fatal error. An example error message is when either sampling or optimization cannot find a region of non- zero probability or when a program being parsed is ill formed. When an error arises, whatever program is running cannot continue and the entire execution must halt.

That's right, but could be made clearer. This conflicts with 26.2:

When an index is provided that is out of bounds, Stan throws a rejection error and computation on the current log density and gradient evaluation is halted and the algorithm is left to clean up the error.

Is there a way to detect non-recoverable errors? That is, is there a way to show that if a data argument is bad, it'll always be bad?   I just haven't thought it through well enough.

From the math library, it should just throw the appropriate C++ exception. It's up to the Stan library to decide what to do with these exceptions.
From Stan: we used to treat all exceptions that derived from std::except as a rejection. We switched that to treating all exceptions derived from domain_error as rejections and everything else as errors.
I've treated two things as errors: misconfiguration of things like the CVODES solver or things that stem from data-only arguments. I realize that we can construct functions that may recover, but I figured if it was driven by data-only arguments, then we don't want to reject, but rather error. I'm thinking about something like:
data {
  vector[3] y;
}
parameters {
  real theta;
  vector[1] mu;
}
model {
  if (theta < 0)
   y ~ normal(mu[1], 1);
  else if (theta > 3)
   y ~ normal(mu[3], 1);
  else
   y ~ normal(mu, 1);
}

I think the error stemming from accessing something out of bounds should error instead of reject because it's most certainly an error, but I can be convinced to reject instead.

And if we all of a sudden let initial time be a parameter, do we then remove the error and replace with a rejection?

Yes. Definitely.

Thanks!  Just what I was looking for.  A sweep through all these is a different issue.  I added a couple notes to the next manual issue to update the descriptions of how errors vs. rejections behave.  I don't quite like error vs. rejection as they're both kinds of errors, it's just that error is fatal.

@yizhang-cae, we're waiting on changes to this PR from you.

Oops, missed this thread. I’ll address it ASAP.
On Tue, Feb 20, 2018 at 10:17 PM Daniel Lee<EMAIL_ADDRESS>wrote:

@yizhang-cae https://github.com/yizhang-cae, we're waiting on changes
to this PR from you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/math/pull/744#issuecomment-367201033, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AfkhsBkTgrrFYZROBwl0iH2KM-zi9eTeks5tW4rXgaJpZM4RzHBu
.

--
Regards,
Yi Zhang
metrumrg.com

Thanks.
On Tue, Feb 20, 2018 at 10:45 PM, Yi Zhang<EMAIL_ADDRESS>wrote:

Oops, missed this thread. I’ll address it ASAP.
On Tue, Feb 20, 2018 at 10:17 PM Daniel Lee<EMAIL_ADDRESS>wrote:

@yizhang-cae https://github.com/yizhang-cae, we're waiting on changes
to this PR from you.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/math/pull/744#issuecomment-367201033, or
mute
the thread
<https://github.com/notifications/unsubscribe-auth/
AfkhsBkTgrrFYZROBwl0iH2KM-zi9eTeks5tW4rXgaJpZM4RzHBu>
.

--
Regards,
Yi Zhang
metrumrg.com
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/math/pull/744#issuecomment-367204570, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAZ_F5ahUtDSIbtcc_tl2cYjQTLjgZ9iks5tW5FfgaJpZM4RzHBu
.

@yizhang-cae, thanks! I removed the unnecessary comments on the includes, so it's going through tests again.
We're waiting on @bob-carpenter's approval. If he doesn't get to it by early next week, I'll review his comments and see if there's anything missing in the PR.

Thanks. I must have copied those lines from cvodes examples.
On Fri, Feb 23, 2018 at 9:44 AM Daniel Lee<EMAIL_ADDRESS>wrote:

@yizhang-cae https://github.com/yizhang-cae, thanks! I removed the
unnecessary comments on the includes, so it's going through tests again.
We're waiting on @bob-carpenter https://github.com/bob-carpenter's
approval. If he doesn't get to it by early next week, I'll review his
comments and see if there's anything missing in the PR.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/math/pull/744#issuecomment-368027097, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AfkhsIKTdYP96aZT0XTueNqIES6JVZqPks5tXs3ggaJpZM4RzHBu
.

--
Regards,
Yi Zhang
metrumrg.com

No problem! It was minor and I thought I included it in the original
review, but you did a lot of work and it might have gotten lost in the
shuffle.
For motivation as to why it's preferred to be removed:

we don't have those types of comments for any other include. When you
come across something that's unique when reading, you now have to dig into
why it's unique -- this makes it slower for the reader to understand what's
going on
includes are part of C++, so no need to call it out unless it's really
not standard

Anyway, thanks!
On Fri, Feb 23, 2018 at 9:46 AM, Yi Zhang<EMAIL_ADDRESS>wrote:

Thanks. I must have copied those lines from cvodes examples.
On Fri, Feb 23, 2018 at 9:44 AM Daniel Lee<EMAIL_ADDRESS>wrote:

@yizhang-cae https://github.com/yizhang-cae, thanks! I removed the
unnecessary comments on the includes, so it's going through tests again.
We're waiting on @bob-carpenter https://github.com/bob-carpenter's
approval. If he doesn't get to it by early next week, I'll review his
comments and see if there's anything missing in the PR.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/math/pull/744#issuecomment-368027097, or
mute
the thread
<https://github.com/notifications/unsubscribe-auth/
AfkhsIKTdYP96aZT0XTueNqIES6JVZqPks5tXs3ggaJpZM4RzHBu>
.

--
Regards,
Yi Zhang
metrumrg.com
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/math/pull/744#issuecomment-368028706, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AAZ_F8QNG8TFFAy0a2UD_TBSEt-4S5k9ks5tXs8zgaJpZM4RzHBu
.

Hmm... I just noticed that we have quite a bit of duplication of code which we import from sundials right now. So cvodes and idas both bring their sources for nvector and their linear algebra solvers. As it stands right now the cvodes and the idas bring themselves the nvector and linear algebra solvers with them which are identical copies.
Sundials also distributes a package which combines the different solvers into a single solver package. I would strongly suggest that we do the same for stan-math. The thing is that we had to patch the cvodes sources multiple times in order to make CRAN happy which is quite pedantic about not having code distributed which directly outputs to stdcout (I thing that was it). If we have multiple copies around then we would need to patch different places.
This should probably have been raised with the IDAS merge; sorry for being late with that. In short: I think we should switch to the sundials package which includes CVODES and IDAS (but we strip aways the bits from sundials which we do not use).

Yep. I plan to raise this when IDAS comes in. That’s why I did the upgrade
first.
On Sat, Feb 24, 2018 at 4:33 AM wds15<EMAIL_ADDRESS>wrote:

Hmm... I just noticed that we have quite a bit of duplication of code
which we import from sundials right now. So cvodes and idas both bring
their sources for nvector and their linear algebra solvers. As it stands
right now the cvodes and the idas bring themselves the nvector and linear
algebra solvers with them which are identical copies.
Sundials also distributes a package which combines the different solvers
into a single solver package. I would strongly suggest that we do the same
for stan-math. The thing is that we had to patch the cvodes sources
multiple times in order to make CRAN happy which is quite pedantic about
not having code distributed which directly outputs to stdcout (I thing that
was it). If we have multiple copies around then we would need to patch
different places.
This should probably have been raised with the IDAS merge; sorry for being
late with that. In short: I think we should switch to the sundials package
which includes CVODES and IDAS (but we strip aways the bits from sundials
which we do not use).
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/stan-dev/math/pull/744#issuecomment-368215157, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AfkhsKy_WOWbtNZpIYRD4MmfXd2Fax6yks5tX9dzgaJpZM4RzHBu
.

--
Regards,
Yi Zhang, Ph.D.
metrumrg.com

IDAS is already merged.

I mean #768.

Sounds like a good plan to me.  Anything to cut down on size and linking/compiling time.

My plan is a series of tasks:

include IDAS library (merged)
update CVODES (this PR)
implement DAE solver (#767)
combine IDAS & CVODES libraries to use SUNDIALS.

To me breaking tasks apart makes it easier to track & debug.

Thanks---much easier to review in small pieces, too.

Let me know if there are further changes needed for this PR to merge. Thanks.

I can look at it but don't know what all that config means, either in CVODES or in the makes.  It'd be great if @wds15 can look at it.

@bob-carpenter, @yizhang-cae, @wds15: this PR is good to go. @yizhang-cae, can you put in a new issue for combining IDAS and CVODES?


first pass remote hdt file querying

part of https://github.com/DeciSym/decisym-engine-rs/issues/44


Should available groups in gitte list

exampleservicename: [build, up, down] <dk, sv, uk>

Show groups in gitte list output #193


A way to use a pointer as key? without compiler warnings

/* Arbitrary key type */
struct key { ... };
struct value { ... }

HASHMAP(struct key, struct value) map;

/* Use the map, passing in `struct key *` as the key, and `struct value *` as the value */

/* Arbitrary key type */
struct key { ... };
struct value { ... }

HASHMAP(struct key, struct value) map;

/* Use the map, passing in `struct key *` as the key, and `struct value *` as the value */

wait so i dont pass it like struct key*
ah, that where my mistake is


read hatch fix

Description

Fix the reader for a polyline as boundary.

Confirm hatch fix - Thank you - nice work Albert


Add option to overwrite files in existing project

The book has the following to say about this:

cargo-generate will not allow any existing files to be overwritten and will fail to generate any files should there be any conflicts.

I actually think this would be a good feature to have, although the default choice of refusing to overwrite is good. Perhaps an --overwrite flag could be added to generate over the existing project anyway?
For an example use case, I have this template that receives relatively frequent updates since Nix Flakes are still evolving. I feel like an --overwrite option would make it easier to propagate these changes and new best practices to existing projects generated from this template. Then one could do cargo gen ... --overwrite && git restore -p . instead of having to figure out how to apply all of the changes manually.

maybe a -f | --force flag would be more reasonable for this sort of behaviour?

If anyone wants to work on this - I'm available to guide as needed.

yeah, that is unfortunate ☹


improve contacts, fix typedefs

improve contacts handling (convert old format into new one)
fix type defs

no stress with merging though, i will gradually add more things into this pr if needed.
this pr depends on https://github.com/minibits-cash/cashu-ts/pull/1 being merged.

for this pull request to be merged, whichever version of cashu-ts we end up using, will need to include the modifications to the type definitions i made in https://github.com/minibits-cash/cashu-ts/pull/1.

ah hej ja som tam dodal dalsie ltska lebo node 18 uz je out of date a ja pouzivam 22 (latest) - nemal som s tym ziadne problemy.


Optimized partial and smooth Bézier curve computations in bezier.py

Overview: What does this pull request change?

I made many changes to the functions defined in bezier.py to calculate Bézier curves faster. Here is a list of those changes, starting from the most important ones:

Optimized partial_bezier_points

~Also did something similar for partial_quadratic_bezier_points~ EDIT: now partial_quadratic_bezier_points is redirected to partial_bezier_points

Added split_bezier and subdivide_bezier, as analogs of split_quadratic_bezier and subdivide_quadratic_bezier

EDIT: also redirected those functions to their generalized counterparts

NEW: Added an optimized bezier_remap as the generalization of quadratic_bezier_remap, which now is redirected to it
Optimized get_smooth_cubic_bezier_handle_points

Redirected get_smooth_handle_points to get_smooth_cubic_bezier_handle_points
Added get_smooth_cubic_bezier_handle_points_for_open_curve and get_smooth_cubic_bezier_handle_points_for_closed_curve
Removed from scipy import linalg

Optimized is_close
Optimized interpolate
Slightly optimized bezier
Other very minor optimizations

Motivation and Explanation: Why and how do your changes improve the library?

partial_bezier_points
Funnily enough, this PR was originally going to be only about get_smooth_handle_points (more on that later), but then I figured out how to make this function faster, so I had to include it. I think it is more important because there are more instances of Mobjects being created, drawn or transformed into other Mobjects (or at least that's what I think), so I put it first.
The original algorithm was good and nifty, but it had its issues. It made a lot of calls to bezier, even for those cases in which there were only 1 or 2 points (defining Béziers of grade 0 and 1 respectively), and bezier did not handle those cases, falling back to the nth grade Bézier which was expensive. I modified bezier to handle those cases separately.
But in the end, the major problem was that, for every Bëzier curve it calculated, it made many intermediate calculations that could be reused for the other Béziers. Many of their calculations overlap because they have many control points in common.
So, instead of redoing those intermediate calculations (which ends up taking time O(n³) for calculating the final partial Bézier curve), I figured out a way to calculate all of the necessary points at once without wasting calculations, something that takes time O(n²). I reported around 4x - 5x speedup on this function after these changes.
EDIT: Because the resulting partial curve is a linear combination of the input points, the process can be encoded as a matrix, which is what I did for the simple cases (up to cubic curves). This is even more efficient: around 10x speedup.
I left a lot of comments regarding the algorithm in the code, because it might look really confusing at first glance. I did not include them in this message to avoid making it too long:
def partial_bezier_points(points: np.ndarray, a: float, b: float) -> np.ndarray:
    arr = np.array(points)  # It is convenient that np.array copies points
    N = arr.shape[0]
    # Border cases
    if a == 1:
        arr[:] = arr[-1]
        return arr
    if b == 0:
        arr[:] = arr[0]
        return arr

    if a != 0:
        for i in range(1, N):
            arr[: N - i] += a * (arr[1 : N - i + 1] - arr[: N - i])

    if b != 1:
        if a != 0:
            mu = (1 - b) / (1 - a)
        else:
            mu = 1 - b
        for i in range(1, N):
            arr[i:] += mu * (arr[i - 1 : -1] - arr[i:])

    return arr

partial_quadratic_bezier_points
I also tried to replicate the same thing on this function. EDIT: now it just redirects to partial_bezier_points, in an attempt to unify VMobject and OpenGLVMobject a little bit more.
Although, a word of caution: returning the result as an ndarray broke many test cases when I ran poetry run pytest, and the culprit was OpenGLVMobject.insert_n_curves_to_point_list, which expected a Python list instead of an ndarray because it used a list concatenation with +=.
So, for the moment, I transformed the final output to a Python list before returning it, which might result in a slight overhead.
split_bezier and subdivide_bezier
I made these functions that work similarly to split_quadratic_bezier and subdivide_quadratic_bezier, but for general Bézier curves (although they would be used mainly, if not only, for cubic Béziers):
EDIT: Again, the resulting subcurves are a linear combination of the input points, so the process can be encoded as matrices for extra efficiency. In the case of subdivide_bezier, these matrices can even be memoized as they're always the same given a Bezier degree and a number of divisions. Also, split_quadratic_bezier and subdivide_quadratic_bezier are again redirected to their generalized counterparts.
def split_bezier(points: Iterable[float], t: float) -> np.ndarray:
    points = np.asarray(points)
    N, dim = points.shape
    arr = np.empty((2, N, dim))
    arr[1] = points
    arr[0, 0] = points[0]

    for i in range(1, N):
        arr[1, : N - i] += t * (arr[1, 1 : N - i + 1] - arr[1, : N - i])
        arr[0, i] = arr[1, 0]

    return arr

def subdivide_bezier(points: Iterable[float], n_divisions: int) -> np.ndarray:
    points = np.asarray(points)
    if n_divisions == 1:
        return points

    N, dim = points.shape

    beziers = np.empty((n_divisions, N, dim))
    beziers[-1] = points
    for curve_num in range(n_divisions - 1, 0, -1):
        curr = beziers[curve_num]
        prev = beziers[curve_num - 1]
        prev[0] = curr[0]
        for i in range(1, N):
            a = (n_divisions - curve_num - 1) / (n_divisions - curve_num)
            curr[: N - i] += a * (curr[1 : N - i + 1] - curr[: N - i])
            prev[i] = curr[0]

    return beziers.reshape(n_divisions * N, dim)

I really want to highlight subdivide_bezier, because this function could perfectly replace the use of partial_bezier_points in the method VMobject.insert_n_curves_to_point_list, being around 1.5x - 2x more efficient (if we don't consider the removal of np.linspace, which is too slow to invoke repeatedly and actually takes a good portion of the runtime of this method). Of course, this is all in comparison to the NEW implementation of partial_bezier_points, because if we compare it to its old implementation it's actually like 8x more efficient.
# VMobject.insert_n_curves_to_point_list

# Original
for quad, sf in zip(bezier_quads, split_factors):
    alphas = np.linspace(0, 1, sf + 1)
    for a1, a2 in zip(alphas, alphas[1:]):
        new_points = np.append(
            new_points,
            partial_bezier_points(quad, a1, a2),
            axis=0,
        )

# My proposal
for quad, sf in zip(bezier_quads, split_factors):
    if sf == 0:
        new_points = np.append(new_points, quad, axis=0)
    else:
        new_points = np.append(new_points, subdivide_bezier(quad, sf), axis=0)

Of course, I plan to define the new points in a way that doesn't use np.append (new PR coming in the way!), because this method turns out to be slow if used repeatedly. NumPy arrays are not really designed to grow dynamically.
get_smooth_handle_points
Now we arrive to the first function in bezier.py I modified, and the main reason I made this PR.
I had a test scene with more than 100 ParametricFunctions in it, which were all being updated (I wanted to represent the effects of multiplying everything in a cartesian plane by e^(-st) to illustrate the Laplace transform). However, more than half of the time required to render the scene was spent on ParametricFunction.generate_points, and one of the 3 main culprits was VMobject.make_smooth. There were many issues in that function I plan to address in another PR, but the one I'm going to address in this specific PR is get_smooth_handle_points.
The main bottleneck for this function is the call to scipy.linalg.solve_banded. Apparently, it spends more time validating the arrays passed as a parameter, than actually solving the system of equations (at least that was what Snakeviz appeared to tell me).
That's the main reason I decided to manually implement the algorithm for solving these equations, but there was a second reason: the matrices all follow the same pattern and their coefficients are pretty much always the same, varying only in size, so the diagonals can be hardcoded in the algorithm rather than stored explicitly, as the original implementation had to do in order to use scipy.linalg.solve_banded.
Moreover, since the matrices all follow the same pattern, some computations are actually really similar, and they can be memoized. Thus, I decided to include memo arrays which grow depending on the user needs.
I did not include the code this time, because it is really, really long. You can see it in the diffs.
In the end, I got a speedup of around 3x. I can show a Snakeviz output of this, but that output includes a change to the is_closed function which really needed a rewrite, so lemme talk about it first.
is_closed
This function originally used np.allclose to compare if all the three components of two 3D points are all close to each other. Repeatedly using np.allclose to compare only two 3D points each time not only is overkill, it is actually very expensive and takes a painful part of the total time of get_smooth_handle_points.
As we just need to compare two 3D points, I rewrote it to a simple "compare 1st coords, then compare 2nd coords, then compare 3rd coords". Amazingly, this resulted in almost a 30x speedup!
def is_closed(points: tuple[np.ndarray, np.ndarray]) -> bool:
    start, end = points[0], points[-1]
    atol = 1e-8
    if abs(end[0] - start[0]) > atol:
        return False
    if abs(end[1] - start[1]) > atol:
        return False
    if abs(end[2] - start[2]) > atol:
        return False
    return True

(NOTE: in the end, I did not include the relative tolerance (rtol) that np.allclose does use. I do not know if this rtol is really that important, and including it only adds a small 50% overhead, which is not noticeable at all because it is still 20x faster than the original implementation with np.allclose, so I wanted to ask for your opinion regarding this matter.)
Now here come some graphics from VMobject.make_smooth before and after the changes to get_smooth_handle_points and is_closed:

Before
After

A closer look to get_smooth_handle_points:

Before
After

The red block at the right is the new is_closed. It now takes much less time to run! Combined with the get_smooth_handle_points optimization, this latter function now has an overall speedup of around 4x.
Now, VMobject._gen_subpaths_from_points is still a huge problem, and I'm addressing that in another PR.
interpolate
This is an interesting one:
# Original
def interpolate(start: np.ndarray, end: np.ndarray, alpha: float) -> np.ndarray:
    return (1 - alpha) * start + alpha * end

# New
def interpolate(start: np.ndarray, end: np.ndarray, alpha: float) -> np.ndarray:
    return start + alpha * (end - start)

This change looks so small and irrelevant, but actually makes a speedup of around 30% in this function. I guess this is because the original implementation has 2 products and 1 sum, while the new one has only 1 product and 2 sums (if you consider that subtraction as a sum).
Although this function is called pretty much everywhere, it is not that big of a change at all when compared to the overall render time of a scene, but it was kind of neat to include this one here.
bezier
First of all, I added the cases for Bézier curves of grade 0 and 1. This was originally intended for partial_bezier_curves, which repeatedly called bezier and was not prepared for these specific cases, falling back to the expensive general nth grade case:
def bezier(
    points: np.ndarray,
) -> typing.Callable[[float], int | typing.Iterable]:
    P = np.asarray(points)
    n = P.shape[0] - 1

    if n == 0:
        def zero_bezier(t):
            return P[0]
        return zero_bezier

    if n == 1:
        def linear_bezier(t):
            return P[0] + t * (P[1] - P[0])
        return linear_bezier

    # ...

Then, I made a very slight optimization for the cubic Bëzier case:
    if n == 3:
        def cubic_bezier(t):
            t2 = t * t
            t3 = t2 * t
            mt = 1 - t
            mt2 = mt * mt
            mt3 = mt2 * mt
            return mt3 * P[0] + 3 * t * mt2 * P[1] + 3 * t2 * mt * P[2] + t3 * P[3]
        return cubic_bezier

It reported a small speedup of around 10% - 15%. Not too bad! That was the fastest I managed to get it to be, my other options didn't go that well.
I did something similar with the quadratic Bëzier, although I didn't really test it to see if it was actually faster, because I didn't use OpenGL (my bad):
    if n == 2:
        def quadratic_bezier(t):
            t2 = t * t
            mt = 1 - t
            mt2 = mt * mt
            return mt2 * P[0] + 2 * t * mt * P[1] + t2 * P[2]
        return quadratic_bezier

Finally, the general nth grade Bézier case. I'm not really sure if this is ever gonna be used, but I avoided the extensive use of the choose function which can be a bit expensive, and instead used the recursive definition of Béziers I used for functions like partial_bezier_points and subdivide_bezier:
    def nth_grade_bezier(t):
        B = P.copy()
        for i in range(n):
            # After the i-th iteration (i in [0, ..., n-1]) there are (n-i)
            # Bezier curves of grade (i+1) stored in the first n-i slots of B
            B[: n - i] += t * (B[1 : n - i + 1] - B[: n - i])
        # In the end, there shall be a single Bezier curve of grade n
        # stored in the first slot of B
        return B[0]
    return nth_grade_bezier

Another good thing of this is that bezier no longer returns lambdas. Now it returns named functions, which is good for debugging and profiling: now you can know which function is taking what part of the time when profiling your code.
Some other very minor optimizations

~split_quadratic_bezier: Replaced np.zeros with np.empty.~ Outdated: now split_quadratic_bezier straight up redirects to split_bezier
get_quadratic_approximation_of_cubic: Replaced len(a0) with a0.shape[0], 0.5 * np.ones(len(a0)) with np.full(a0.shape[0], 0.5), and np.zeros with np.empty.

Links to added or changed documentation pages

Further Information and Comments

Reviewer Checklist

[ ] The PR title is descriptive enough for the changelog, and the PR is labeled correctly
[ ] If applicable: newly added non-private functions and classes have a docstring including a short summary and a PARAMETERS section
[ ] If applicable: newly added functions and classes are tested

Hello everyone! It's been a long time.
I made some updates and extra optimizations I discovered a long time ago while working on #3336 :)

Update:

Fixed subdivide_bezier() which had some typos causing wrong results for Béziers of degree 3 or higher
Added tests for partial_bezier_points(), split_bezier() and subdivide_bezier()


consistent label checking in client side

What do these changes do?

Related issue number

Related to #1179

Codecov Report

Merging #1242 (e4438ca) into main (a7d1472) will decrease coverage by 7.85%.
The diff coverage is 92.30%.

@@            Coverage Diff             @@
##             main    #1242      +/-   ##
==========================================
- Coverage   73.48%   65.62%   -7.86%
==========================================
  Files          88       88
  Lines        9399     9412      +13
==========================================
- Hits         6907     6177     -730
- Misses       2492     3235     +743

Impacted Files
Coverage Δ

python/graphscope/framework/context.py
67.05% <92.30%> (+1.92%)
:arrow_up:

...aphscope/tests/kubernetes/test_resource_builder.py
0.00% <0.00%> (-100.00%)
:arrow_down:

...on/graphscope/tests/kubernetes/test_demo_script.py
0.00% <0.00%> (-80.91%)
:arrow_down:

python/graphscope/deploy/kubernetes/utils.py
12.07% <0.00%> (-57.49%)
:arrow_down:

python/graphscope/deploy/kubernetes/cluster.py
23.73% <0.00%> (-52.53%)
:arrow_down:

python/graphscope/analytical/app/java_app.py
24.00% <0.00%> (-45.50%)
:arrow_down:

python/graphscope/tests/unittest/test_java_app.py
55.00% <0.00%> (-45.00%)
:arrow_down:

...thon/graphscope/tests/kubernetes/test_with_mars.py
0.00% <0.00%> (-44.83%)
:arrow_down:

python/graphscope/interactive/query.py
44.34% <0.00%> (-38.27%)
:arrow_down:

...n/graphscope/deploy/kubernetes/resource_builder.py
30.83% <0.00%> (-26.34%)
:arrow_down:

... and 9 more

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 a7d1472...e4438ca. Read the comment docs.


shelter: support to generate default rpm changelog

Signed-off-by: Zhou Liang<EMAIL_ADDRESS>

Please the fix line in commit header. Refer to https://github.com/alibaba/inclavare-containers/pull/1478


New version: bloznelis.typioca version 2.4.1

Pull request has been created with WinGet Releaser v2 :rocket:
Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/109989&drop=dogfoodAlpha

Closing in favor of https://github.com/microsoft/winget-pkgs/pull/109991


Ensure that Jinja2>=2.8 is installed

The FileSystemLoader class inside Jinja2 added the followlinks keyword argument in version 2.8. This keyword is being used in molecule/utilities.py and produces a runtime error when the system with Molecule installed has an older version of Jinja2 installed.
Resolves #149

@hectcastro, I think it would be nicer to squash those two commits into one.

@tjanez Commits squashed. Let me know if I should include anything else.

@hectcastro, thanks!
We'll us how Molecule maintainers proceed.

looks reasonable :+1:

👍 Thanks!


Wrap in `while-no-input'

This prevents selectrum from blocking while typing. I use a 10+ year old computer, and it was very laggy to type into the minibuffer as the full hook would run after every keypress. This change gave me a substantial speed-up.
I am not sure if there's a better way to do it, or any unexpected side-effects, but it works well for me.
(Note: The touched quite a few lines due to indentation changes, but really it's just a one line patch.)

Interesting, this is also what icomplete uses when computing icomplete-completions.

Huh, maybe the M-DEL regression has something to do with this enigmatic comment in the Icomplete code?
                 ;; Not sure why, but such requests seem to come
                 ;; every once in a while.  It's not fully
                 ;; deterministic but `C-x C-f M-DEL M-DEL ...'
                 ;; seems to trigger it fairly often!
                 (while-no-input-ignore-events '(selection-request))
                 (text (while-no-input
                         (icomplete-completions
                          field-string
                          (icomplete--completion-table)
                          (icomplete--completion-predicate)
                          (if (window-minibuffer-p)
                              (not minibuffer-completion-confirm)))))


Fix web camera not loading

Explanation of Change

Fixed Issues

$ https://github.com/Expensify/App/issues/51821
PROPOSAL: https://github.com/Expensify/App/issues/51821#issuecomment-2451859918
Tests

Click the FAB.
Choose Submit Expense.
If the Manual tab is not active by default, select it and navigate back, then repeat from step 1. Otherwise continue with step 4.
Switch to the Scan tab.
Verify that the spinner is not shown or disappears within a few seconds.

[x] Verify that no errors appear in the JS console

Offline tests

Click the FAB.
Choose Submit Expense.
If the Manual tab is not active by default, select it and navigate back, then repeat from step 1. Otherwise continue with step 4.
Switch to the Scan tab.
Verify that the spinner is not shown or disappears within a few seconds.

QA Steps

// TODO: These must be filled out, or the issue title must include "[No QA]."

Click the FAB.
Choose Submit Expense.
If the Manual tab is not active by default, select it and navigate back, then repeat from step 1. Otherwise continue with step 4.
Switch to the Scan tab.
Verify that the spinner is not shown or disappears within a few seconds.

[x] Verify that no errors appear in the JS console

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
https://github.com/user-attachments/assets/c974e6ba-bd37-4e70-8098-2f0ce9ad6340

Android: mWeb Chrome
https://github.com/user-attachments/assets/63de664e-f0ec-474c-aa2c-e57248907155

iOS: Native
https://github.com/user-attachments/assets/adaa9688-79f6-4b23-8f44-1732451fcf4e

iOS: mWeb Safari
https://github.com/user-attachments/assets/8687d46d-dbc0-4f4a-a3a2-35a906fbf6ca

MacOS: Chrome / Safari
https://github.com/user-attachments/assets/b95105b5-cf86-45c3-a915-1a7dfd78d8df

MacOS: Desktop
https://github.com/user-attachments/assets/ec7d2815-7d60-49e5-b8b3-7e1d8520a390

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.


[11.x] feat: introduce Number::divide()

Hi :wave:
I'm opening another PR here to introduce a nice handy Number::divide() method that takes in two values and returns the result. It takes into account the "Division by zero" error which can often be encountered in projects. It's inherited from a function I wrote in my own project that I've used in a number of places.
Starting super simple here, not overcomplicating it, we could in the future introduce a precision flag, but wanted to keep this as lightweight as possible!
I've used this over 70 times in my application

When the denominator is zero, then it defaults the division to zero?
What is behind this logic?

Thanks for your pull request to Laravel!
Unfortunately, I'm going to delay merging this code for now. To preserve our ability to adequately maintain the framework, we need to be very careful regarding the amount of code we include.
If applicable, please consider releasing your code as a package so that the community can still take advantage of your contributions!


Revert "python312Packages.zigpy: 0.65.2 -> 0.65.3"

Reverts NixOS/nixpkgs#333570

Sorry for this.

Thanks for providing the revert! I would have done it myself in any case.


Made some fixes to some checks, added a few checks and some comments in the checks I edited.

I basically just looked at this for about an hour and tried to make some changes for the better. I might add some more changes in the future. I hope these are useful.

// Decompiled with: CFR 0.152
// Class Version: 8

nice skid bro 😭


CLI, API for regenerating phonemic id from full length hash

Allow longer phonemic ID to be generated in case of collision.
Length override option?

Implemented in 47dd86df5424b017902ed80c866200528b680713


Installation failed

Dear Paul,
I have followed your instructions using the latest version from git, but I have run into some issues when adding a device. I get an error that the config flow is broken. In the log file I get:
2023-01-05 20:23:15.770 WARNING (SyncWorker_3) [homeassistant.loader] We found a custom integration stiebel_eltron_isg which has not been tested by Home Assistant. This component might cause stability problems, be sure to disable it if you experience issues with Home Assistant
2023-01-05 20:27:02.211 ERROR (MainThread) [homeassistant.config_entries] Error occurred loading configuration flow for integration stiebel_eltron_isg: No module named 'pymodbus.client3
Describe the bug
Whenever I try to add an device I get an error, that the config flow is interrupted.
I'm using
Home Assistant 2023.1.0
Supervisor 2022.12.1
Operating System 9.4
Frontend 20230104.0 - latest

thanks a lot,
Kai

This should be fixed with the new release 0.1.0. Could you please check if it is working now?

The fix did it! Thanks a lot for the quick response!


Minor tweaks to "About" page

Changes

Comments

#386  👈
master

This stack of pull requests is managed by Graphite. Learn more about stacking.

Join @forstmeier and the rest of your teammates on  Graphite


Remove CONFIG_ARCH_BOARD #ifdef dependencies from mtd

Since mtd already checks whether CONFIG_MTD_RAMTRON is set in
defconfig use this define to check whether to call ramtron_attach()
or at24xxx_attach() in the main function, instead of checking
CONFIG_ARCH_BOARD_PX4FMU-V1.
Also instead of using #ifdef CONFIG_ARCH_BOARD_AEROCORE to determine
whether to start mtd on spi 2 or 4, rather use a new board define
PX4_SPI_BUS_RAMTRON in the board_config.h file.
This is related to suggestion for improvement #2574 - improving the portability of the
firmware to new boards.

Nice! Cherry-picked.


Improve Search Results

The search feature on the registry doesn't work the way I would expect. I searched for "azure", but I would've expected the first result to be the Azure Native and Classic providers, but I got a bunch of lower-level Azure docs. Maybe this could work similar to how Searchlight reports categorized results, e.g. searching for "azure":

Providers:

Azure Native
Azure Classic

(other categories of content TBD - I don't know the registry well enough to suggest something)

@kimberleyamackenzie i think we may be able to tie this into the "improve docs user experience" initiative for this quarter. i believe @cnunciato has given you admin access to swifttype. let me know if you have interest in contributing to making this better.

@susanev yeah, for sure! definitely makes sense as part of that initiative + a great chance to get more familiar with swifttype generally for me

Thanks for the help on this! Hit me up if you have any questions as you get going.

I have weighted the tags as described above.  A couple speedbumps we're running into:

Using Azure as an example of something we have native and classic versions of:  with the weighted tags along, searching "azure" still didn't bring the package landing pages to the top.  This is because the package titles and overview language are actually "Azure Native" and "Azure Classic."  I solved this for our featured packages by customizing the search results and pinning the landing pages for classic + native to the top of the results.
But, this is related to a larger challenge when titles on the page don't necessarily match the search terms folks might be using.  A good example of this is https://www.pulumi.com/registry/packages/azuread/.  If I search "AzureAD", with the new weighting, the landing page is the first result.  However, if I search "Azure active directory," the overview doesn't make it into the first page of results, because we don't use that full name in the tags or title.  We can work around this for one-off instances by setting synonyms in swiftype - but we should consider doing a pass to make sure we have all of these set where we want them to be, or otherwise update the meta descriptions to use full names.

I'm going to call this issue complete, and I have created https://github.com/pulumi/registry/issues/762 to dive deeper into the full name search issue.


Setup TLS for copay.coloredcoins.org

QR code scanner no longer works in insecure environments

https://copay.coloredcoins.org/ up and running. Wallets need to be migrated from non-HTTPS version manually (via backup/export Copay feature)


dumpcerts.sh compatibility

The dumpcerts.sh script uses OpenSSL to verify that the private key is valid.
In doing so, the key is piped to the command openssl, without limiting the line lengths.
This appears not to work for all implementations of SSL.
To exemplify:
Within a Docker image based on alpine:3.8 the key line length need to be less than 80 characters.
# cat test.pem | fold -w 79 | openssl rsa -inform pem -out key.pem
writing RSA key

# cat test.pem | fold -w 80 | openssl rsa -inform pem -out key.pem
unable to load Private Key
140046610254796:error:09FFF064:PEM routines:CRYPTO_internal:bad base64 decode:pem/pem_lib.c:800:

This limitation does not appear on other systems. The reason for this compatibility issue might be that
Alpine Linux use an openssl implementation based on LibreSSL:
# openssl version
LibreSSL 2.7.4

Hello,
We want to remove this script from the Traefik repository.
You can find more explanation and alternatives here: #4783


libXNNPACK.so: internal symbol `xnn_f16_ibilinear_ukernel__neonfp16arith_c8' isn't defined

Please make sure that this is a build/installation issue. As per our GitHub Policy, we only address code/doc bugs, performance issues, feature requests and build/installation issues on GitHub. tag:build_template
System information

OS Platform and Distribution (e.g., Linux Ubuntu 16.04): Ubuntu 20.04.2 LTS
Mobile device (e.g. iPhone 8, Pixel 2, Samsung Galaxy) if the issue happens on mobile device: N/A
TensorFlow installed from (source or binary): source
TensorFlow version: 56e2e916929746cd6c415c2a402a46349bffa7e0 (commit id)
Python version: N/A
Installed using virtualenv? pip? conda?:  N/A
Bazel version (if compiling from source): N/A
GCC/Compiler version (if compiling from source): 9.3.0
CUDA/cuDNN version: N/A
GPU model and memory: N/A

Describe the problem
I was trying to build TFLite with XNNPACK delegate natively on an ARM-based board using CMake. Previously I successfully built TFLite as static library, but when I tried to link it to my program, many errors of undefined references related to ruy happened. So I turned to compile TFLite as shared library instead, but got the following error:
[ 21%] Linking CXX shared library libXNNPACK.so
/usr/bin/ld: CMakeFiles/XNNPACK.dir/src/init.c.o: in function `init':
init.c:(.text+0x139c): undefined reference to `xnn_f16_ibilinear_ukernel__neonfp16arith_c8'
/usr/bin/ld: init.c:(.text+0x13a0): undefined reference to `xnn_f16_ibilinear_ukernel__neonfp16arith_c8'
/usr/bin/ld: libXNNPACK.so: internal symbol `xnn_f16_ibilinear_ukernel__neonfp16arith_c8' isn't defined
/usr/bin/ld: final link failed: bad value
collect2: error: ld returned 1 exit status
make[2]: *** [_deps/xnnpack-build/CMakeFiles/XNNPACK.dir/build.make:6532: _deps/xnnpack-build/libXNNPACK.so] Error 1
make[1]: *** [CMakeFiles/Makefile2:5486: _deps/xnnpack-build/CMakeFiles/XNNPACK.dir/all] Error 2
make: *** [Makefile:152: all] Error 2

Provide the exact sequence of commands / steps that you executed before running into the problem
cmake -B tflite-build -DBUILD_SHARED_LIBS=ON tensorflow/tensorflow/lite
cmake --build tflite-build -j 4

Any other info / logs
Include any logs or source code that would be helpful to diagnose the problem. If including tracebacks, please include the full traceback. Large logs and files should be attached.

@mohantym Thanks for the reply, but TFLite is compiled natively on ARM in my case.

Hi @fengyuentau ! Can you check below command after declaring ARM 64 SDK tool chain in path and removing -DBUILD_SHARED_LIBS=ON flag ? Thanks!
cmake -DCMAKE_TOOLCHAIN_FILE=<CMakeToolchainFileLoc> ../tensorflow/lite/

I met the same problem and I can compile static library successfully, but failed with "-DBUILD_SHARED_LIBS=ON" on Android64.  "error: undefined reference to `xnn_f16_ibilinear_ukernel__neonfp16arith_c8'"

@mjp9527 Did you have undefined reference related to ruy when linking TFLite static library to your programe?

@mjp9527 Did you have undefined reference related to ruy when linking TFLite static library to your programe?

@fengyuentau ......I was wrong,  this error appeared again when linking TFLite static library.

This was fixed in XNNPACK in google/XNNPACK@ba7e4bf72936ad7dcb750707eb519cd9c56bc1c9, and the latest revision of TensorFlow shouldn't have this issue.

@Maratyszcza Let me check which version of XNNPACK is using when I compiled TLite.

@Maratyszcza The last compilation I tried was 3 days ago, but somehow CMake scripts downloaded XNNPACK at https://github.com/google/XNNPACK/commit/d605aa76904aa1c5ea98bb7a0a4bafc4886b8a0a, which was 6 days ago (The fix you mention was 5 days ago). Do you know how to force using latest of XNNPACK?

I wonder if pip install tflite-runtime comes with XNNPACK delegate for aarch64, which can be a workaround for now.

XNNPACK revision used in the build is specified here. You'd probably need to remove all configuration artifacts and reconfigure TFLite after updating this line.

@Maratyszcza Thanks for your information! I pulled the latest Tensorflow which has a newer XNNPACK with the patch you mentioned previously. It can finish compilation without errors.


docs: add registration step to creatingplugins

This step was not obvious to me until I stumbled on this comment: https://github.com/capacitor-community/electron/issues/245#issuecomment-1615681450

@IT-MikeS Thanks for merging this. I noticed that the docs site did not automagically update as a result of the merge. I'm hoping you could explain the workflow for this project and when I should expect to see this change published. Thanks again!


feat: Add 5xx error classes

Adds following error classes, together with tests:

[x] 501 Not Implemented
[x] 504 Gateway Timeout
[x] 505 HTTP Version Not Supported

@jmvrbanac @kgriffs Another PR with error classes.


dev: cleanup da_db

In crates/client/db/src/da_db.rs we use the DaDb to store information about proving jobs. One per block.
Once the blocks are proved on l1, we can remove those jobs from our DB.
TODO
Listen to l1.
When a new bunch of blocks is proven, read last_proven_block, find all the block hash for blocks since last_proven, remove their jobs from db, and call update_last_proven_block.
It has to be done before updating the last proven block. Ideally in the same function.

Can I take this one, please?
Need to be deep in the code before doing others' PR.
I think that's can help me to move to this PR:
https://github.com/keep-starknet-strange/madara/issues/1405

Sure. Contact us on telegram if you need help. Don't stay stuck on something you don't understand or don't know how to find in the codebase

Not ready yet

Hi, can I take this issue ?
@tdelabro

@dhirajs0 sorry it's still not ready to be done

It's fine, thank you for the update.

not relevant anymore as we are moving the proving flow out of madara repo


"gatsby-plugin-satorare" threw an error while running the onPostBootstrap lifecycle: Cannot read properties of undefined (reading 'map')

environment
node v18, gatsby 5.12.9, gatsby-plugin-sharp: "^5.12.3"
Reproduce step

Just following https://github.com/okaryo/gatsby-plugin-satorare#usage
Run gatsby develop
Got error ERROR #11321  API.NODE.EXECUTION
"gatsby-plugin-satorare" threw an error while running the onPostBootstrap lifecycle:
Cannot read properties of undefined (reading 'map')
File: file:/.../node_modules/gatsby-plugin-satorare/gatsby-node.js:106:12

TypeError: Cannot read properties of undefined (reading 'map')

  - bridge.js:485 VM2 Wrapper.apply
    [emewjin.github.io]/[vm2]/lib/bridge.js:485:11

  - gatsby-node.js:106 createOgImageReactElement
    [emewjin.github.io]/[gatsby-plugin-satorare]/gatsby-node.js:106:12

  - gatsby-node.js:79
	[emewjin.github.io]/[gatsby-plugin-satorare]/gatsby-node.js:79:39

  - gatsby-node.js:43 step
	[emewjin.github.io]/[gatsby-plugin-satorare]/gatsby-node.js:43:23

  - gatsby-node.js:24 Object.next
	[emewjin.github.io]/[gatsby-plugin-satorare]/gatsby-node.js:24:53

  - gatsby-node.js:18
	[emewjin.github.io]/[gatsby-plugin-satorare]/gatsby-node.js:18:71

  - new Promise

  - gatsby-node.js:14 __awaiter
	[emewjin.github.io]/[gatsby-plugin-satorare]/gatsby-node.js:14:12

  - gatsby-node.js:74 generateOGImage
	[emewjin.github.io]/[gatsby-plugin-satorare]/gatsby-node.js:74:63

In public/static directory, only first page's og image is created.

Thank you for bringing this issue, and I apologize for the delayed response. To better understand the problem, could you please share the contents of the JSX file used for generating the OG images? It seems like the error might be related to a map function being called on an undefined object within that file. Any additional information you can provide will be extremely helpful in resolving this issue.


Failed requests to <IP_ADDRESS>:8000

Hi,
Following the documentation, the app starts but clicking on the login button leads to
a connection refused error to <IP_ADDRESS>:8000
What I am missing to have a server running on that port ?
Thanks !

Hi tbultel, this project is currently an internal work in progress - we have a separate backend server that we are still putting together for this project.


Add css question

Checklist:

[x] I have read freeCodeCamp's contribution guidelines.
[x] My pull request has a descriptive title (not a vague title like Update index.md)

Closes #XXXXX

This is a standard message notifying you that we've reviewed your pull request and have decided not to merge it.
We do not accept submissions from external quiz sites like these
https://edurev.in/question/2737397/Which-of-the-following-is-the-correct-syntax-to-di
Please come up with your own quiz questions and answers 👍


Adds Portuguese pt-pt translations.

Tests are failing because of three words values.
@pekkaklarck In the cases we have an article there will be three words, and seems the parser is not linking it ;)
I tried the pt-pt variant and it was not accepted. Will the pt-br be accepted, for the class PtBr?
Example:
Test Cases --> Cases of Test --> Casos de Teste

I used Fedora 36 and Python 3.10.5.

Could you test does using "Casos De Teste" work?

The problem with Casos de Teste was that it wasn't in title case. I changed to code so that also this format works.
PT is added by #4377 along with other languages so I'll close this PR. Need to think should we add tests for translations like this PR did, though.

My fix above didn't actually fix the problem with headers, it fixed it only with setting names. Better fix coming soon. See #4411 for details.