Laravel 5.2

when running composer require barryvdh/laravel-cors 0.7.x I get this error?
./composer.json has been updated
> php artisan clear-compiled
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Conclusion: don't install barryvdh/laravel-cors v0.7.3
    - Installation request for symfony/http-foundation == <IP_ADDRESS> -> satisfiable by symfony/http-foundation[v3.0.0].
    - Conclusion: remove laravel/framework v5.2.0
    - Conclusion: don't install laravel/framework v5.2.0
    - barryvdh/laravel-cors v0.7.0 requires illuminate/support ~5.0.14|5.1.x -> satisfiable by illuminate/support[v5.0.22, v5.0.25, v5.0.26, v5.0.28, v5.0.33, v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.6, v5.1.8
].
    - barryvdh/laravel-cors v0.7.1 requires illuminate/support ~5.0.14|5.1.x -> satisfiable by illuminate/support[v5.0.22, v5.0.25, v5.0.26, v5.0.28, v5.0.33, v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.6, v5.1.8
].
    - barryvdh/laravel-cors v0.7.2 requires illuminate/support ~5.0.14|5.1.x -> satisfiable by illuminate/support[v5.0.22, v5.0.25, v5.0.26, v5.0.28, v5.0.33, v5.1.1, v5.1.13, v5.1.16, v5.1.2, v5.1.20, v5.1.22, v5.1.25, v5.1.6, v5.1.8
].
    - don't install illuminate/support v5.0.22|don't install laravel/framework v5.2.0
    - don't install illuminate/support v5.0.25|don't install laravel/framework v5.2.0
    - don't install illuminate/support v5.0.26|don't install laravel/framework v5.2.0
    - don't install illuminate/support v5.0.28|don't install laravel/framework v5.2.0
    - don't install illuminate/support v5.0.33|don't install laravel/framework v5.2.0
    - don't install illuminate/support v5.1.1|don't install laravel/framework v5.2.0
    - don't install illuminate/support v5.1.13|don't install laravel/framework v5.2.0
    - don't install illuminate/support v5.1.16|don't install laravel/framework v5.2.0
    - don't install illuminate/support v5.1.2|don't install laravel/framework v5.2.0
    - don't install illuminate/support v5.1.20|don't install laravel/framework v5.2.0
    - don't install illuminate/support v5.1.22|don't install laravel/framework v5.2.0
    - don't install illuminate/support v5.1.25|don't install laravel/framework v5.2.0
    - don't install illuminate/support v5.1.6|don't install laravel/framework v5.2.0
    - don't install illuminate/support v5.1.8|don't install laravel/framework v5.2.0
    - Installation request for laravel/framework 5.2.* -> satisfiable by laravel/framework[v5.2.0].
    - Installation request for barryvdh/laravel-cors 0.7.* -> satisfiable by barryvdh/laravel-cors[v0.7.0, v0.7.1, v0.7.2, v0.7.3].

Installation failed, reverting ./composer.json to its original content.

I realize laravel 5.2 is fairly new and you may be working on this currently..

can you try @dev version?

just tried the dev version got this
./composer.json has been updated
> php artisan clear-compiled
Loading composer repositories with package information
Updating dependencies (including require-dev)
Your requirements could not be resolved to an installable set of packages.

  Problem 1
    - Installation request for barryvdh/laravel-cors 0.7.x-dev -> satisfiable by barryvdh/laravel-cors[0.7.x-dev].
    - Conclusion: remove symfony/http-foundation v3.0.0
    - Conclusion: don't install symfony/http-foundation v3.0.0
    - barryvdh/laravel-cors 0.7.x-dev requires asm89/stack-cors 0.2.x -> satisfiable by asm89/stack-cors[0.2.0, 0.2.1].
    - asm89/stack-cors 0.2.0 requires symfony/http-foundation ~2.1 -> satisfiable by symfony/http-foundation[v2.1.0, v2.1.1, v2.1.10, v2.1.11, v2.1.12, v2.1.13, v2.1.2, v2.1.3, v2.1.4, v2.1.5, v2.1.6, v2.1.7, v2.1.8, v2.1.9, v2.2.0, v
2.2.1, v2.2.10, v2.2.11, v2.2.2, v2.2.3, v2.2.4, v2.2.5, v2.2.6, v2.2.7, v2.2.8, v2.2.9, v2.3.0, v2.3.1, v2.3.10, v2.3.11, v2.3.12, v2.3.13, v2.3.14, v2.3.15, v2.3.16, v2.3.17, v2.3.18, v2.3.19, v2.3.2, v2.3.20, v2.3.21, v2.3.22, v2.3
.23, v2.3.24, v2.3.25, v2.3.26, v2.3.27, v2.3.28, v2.3.29, v2.3.3, v2.3.30, v2.3.31, v2.3.32, v2.3.33, v2.3.34, v2.3.35, v2.3.4, v2.3.5, v2.3.6, v2.3.7, v2.3.8, v2.3.9, v2.4.0, v2.4.1, v2.4.10, v2.4.2, v2.4.3, v2.4.4, v2.4.5, v2.4.6,
v2.4.7, v2.4.8, v2.4.9, v2.5.0, v2.5.1, v2.5.10, v2.5.11, v2.5.12, v2.5.2, v2.5.3, v2.5.4, v2.5.5, v2.5.6, v2.5.7, v2.5.8, v2.5.9, v2.6.0, v2.6.1, v2.6.10, v2.6.11, v2.6.12, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6
.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.8.0].
    - asm89/stack-cors 0.2.1 requires symfony/http-foundation ~2.1 -> satisfiable by symfony/http-foundation[v2.1.0, v2.1.1, v2.1.10, v2.1.11, v2.1.12, v2.1.13, v2.1.2, v2.1.3, v2.1.4, v2.1.5, v2.1.6, v2.1.7, v2.1.8, v2.1.9, v2.2.0, v
2.2.1, v2.2.10, v2.2.11, v2.2.2, v2.2.3, v2.2.4, v2.2.5, v2.2.6, v2.2.7, v2.2.8, v2.2.9, v2.3.0, v2.3.1, v2.3.10, v2.3.11, v2.3.12, v2.3.13, v2.3.14, v2.3.15, v2.3.16, v2.3.17, v2.3.18, v2.3.19, v2.3.2, v2.3.20, v2.3.21, v2.3.22, v2.3
.23, v2.3.24, v2.3.25, v2.3.26, v2.3.27, v2.3.28, v2.3.29, v2.3.3, v2.3.30, v2.3.31, v2.3.32, v2.3.33, v2.3.34, v2.3.35, v2.3.4, v2.3.5, v2.3.6, v2.3.7, v2.3.8, v2.3.9, v2.4.0, v2.4.1, v2.4.10, v2.4.2, v2.4.3, v2.4.4, v2.4.5, v2.4.6,
v2.4.7, v2.4.8, v2.4.9, v2.5.0, v2.5.1, v2.5.10, v2.5.11, v2.5.12, v2.5.2, v2.5.3, v2.5.4, v2.5.5, v2.5.6, v2.5.7, v2.5.8, v2.5.9, v2.6.0, v2.6.1, v2.6.10, v2.6.11, v2.6.12, v2.6.2, v2.6.3, v2.6.4, v2.6.5, v2.6.6, v2.6.7, v2.6.8, v2.6
.9, v2.7.0, v2.7.1, v2.7.2, v2.7.3, v2.7.4, v2.7.5, v2.7.6, v2.7.7, v2.8.0].
    - Can only install one of: symfony/http-foundation[v2.8.0, v3.0.0].
    - Can only install one of: symfony/http-foundation[v2.1.0, v3.0.0].
    - Can only install one of: symfony/http-foundation[v2.1.1, v3.0.0].
    - Can only install one of: symfony/http-foundation[v2.1.10, v3.0.0].
    - Can only install one of: symfony/http-foundation[v2.1.11, v3.0.0].
    - Can only install one of: symfony/http-foundation[v2.1.12, v3.0.0].
    - Can only install one of: symfony/http-foundation[v2.1.13, v3.0.0].
    - Can only install one of: symfony/http-foundation[v2.1.2, v3.0.0].
    - Can only install one of: symfony/http-foundation[v2.1.3, v3.0.0].
    - Can only install one of: symfony/http-foundation[v2.1.4, v3.0.0].
    - Can only install one of: symfony/http-foundation[v2.1.5, v3.0.0].
    - Can only install one of: symfony/http-foundation[v2.1.6, v3.0.0].
    - Can only install one of: symfony/http-foundation[v2.1.7, v3.0.0].
    - Can only install one of: symfony/http-foundation[v2.1.8, v3.0.0].
    - Can only install one of: symfony/http-foundation[v2.1.9, v3.0.0].
// this repeats through all versions and ends with this:
    - Installation request for symfony/http-foundation == <IP_ADDRESS> -> satisfiable by symfony/http-foundation[v3.0.0].

Installation failed, reverting ./composer.json to its original content.

See https://github.com/asm89/stack-cors/pull/19

Still receiving the same error?

Yeah the underlying project uses Symfony 2 unfortunately.

any information about when it will be available? still getting the same error like op

The linked PR is merged, but it still needs to be tagged.

getting the same error

I got the same error. I had to explicitly set a laravel version, run composer update, and it worked.

I got the same error - installed via composer.json then composer update and worked.

See the linked issue upstream.

Right now I use @GrahamCampbell method add to composer.json
"asm89/stack-cors": "dev-master as 0.2.2",
"barryvdh/laravel-cors": "^0.7.3"
and do composer update, now it installing perfectly.

That said, you shouldn't actually need this change to use it on L5.2, since L5.2 support symfony 2.8 as well as 3.0.

use the
"asm89/stack-cors": "dev-master as 0.2.2",
"barryvdh/laravel-cors": "^0.7.3"
I can install the lib,but still have No 'Access-Control-Allow-Origin' header error!

Solved with the tip of @ssuhat

@ssuhat Your suggestion worked for me. Thanks

@ssuhat you're the man!

@ssuhat thanks!!

Thanks this seems to work :+1:

Can you guys try with 0.8.x@dev?

@barryvdh I've tested it and it installed perfectly. I do some request it works great!.

Ok, I've tagged it :)

Hello, I have the following problem when trying to install the package (composer require fruitcake / laravel-cors):
Problem 1
    - Conclusion: don't install fruitcake / laravel-cors v2.0.0
    - Conclusion: don't install fruitcake / laravel-cors v2.0.0-beta3
    - Conclusion: don't install fruitcake / laravel-cors v2.0.0-beta2
    - Conclusion: don't install fruitcake / laravel-cors v2.0.0-beta1
    - Conclusion: remove asm89 / stack-cors 1.3.0
    - Installation request for fruitcake / laravel-cors ^ 2.0 -> satisfiable by fruitcake / laravel-cors [2.0.x-dev, v2.0.0, v2.0.0-beta1, v2.0.0-beta2, v2.0.0-beta3].
    - Conclusion: don't install asm89 / stack-cors 1.3.0
    - fruitcake / laravel-cors 2.0.x-dev requires asm89 / stack-cors ^ 2 -> satisfiable by asm89 / stack-cors [2.0.0, 2.0.0-beta1, 2.0.0-beta2, 2.0.0-beta3 , 2.0.x-dev].
    - Can only install one of: asm89 / stack-cors [2.0.0, 1.3.0].
    - Can only install one of: asm89 / stack-cors [2.0.0-beta1, 1.3.0].
    - Can only install one of: asm89 / stack-cors [2.0.0-beta2, 1.3.0].
    - Can only install one of: asm89 / stack-cors [2.0.0-beta3, 1.3.0].
    - Can only install one of: asm89 / stack-cors [2.0.x-dev, 1.3.0].
    - Installation request for asm89 / stack-cors (locked at 1.3.0) -> satisfiable by asm89 / stack-cors [1.3.0].
This is the 'composer.json' setting:
"require": {
        "php": "^ 7.2.5",
        "fideloper / proxy": "^ 4.2",
        "fruitcake / laravel-cors": "^ 1.0",
        "guzzlehttp / guzzle": "^ 6.5",
        "laravel / framework": "^ 7.0",
        "laravel / homestead": "^ 10.8",
        "laravel / passport": "^ 9.1",
        "laravel / tinker": "^ 2.0",
        "laravel / ui": "^ 2.0",
        "spatie / laravel-fractal": "^ 5.7"
    }
How could I fix it?

Remove the old version first.

Remove the old version first.
The old version of what?

I removed this line and it follows the same problem:
        "fruitcake / laravel-cors": "^ 1.0",

Apparently for the version of Laravel that I have installed, it already has a package installed by default, it is for this reason that it generates the error when trying to install from the composer.

Yeah I don't really understand why Composer doesn't just updated it to the v2 version in this case.

Also this is an issue that is 5 years old and unrelated, so please open a new issue of the problem persists.

This first solution :)
composer require fruitcake/laravel-cors:~1.0


[Miniflare 3] Enforce subrequest limit

Hi 👋
This is likely a feature request for workerd but I'm opening the issue here because we are only using Miniflare directly. Let me know if I should transfer it to the workerd repo.
In Miniflare 2 we had process.env.MINIFLARE_SUBREQUEST_LIMIT to set a subrequest limit but afaik there's nothing like that in Miniflare 3.
From what I was able to find, workerd could support limit enforcements but it sets them to "null" on purpose (source). There seem to be concern around limits due to how they will behave in different platforms. However, I don't think that concern applies to subrequest limit so it would be great if we can enforce it.
Thanks!

Just ran into this as a bit of a surprise myself -- local dev was just fine, but after deploying (on the free tier), I'm hitting the subrequest limit. Would've been nice to know about this ahead of time (though it's my fault for not skimming the usage limits).

It is also an issue doing D1 dev as queries count towards the limits. Would be great if local env enforced this

Right, definitely seems like request limits should be enforced locally.. otherwise that's a pretty major difference in behaviour when running in production.


improved the description of LogMaster4Net

improved the description of LogMaster4Net

Thanks!
"like in the application self before" seems a bit awkward. Is there another way to word that?

Ok, I'll review my words and then send another PR again.


Create 0000-01-02-VitaliiFedotkin.md

created a branch, created a file and made a commit, and opened a pull request

cbxvvzxvxzvxzvxz


Add button on search bar to clear input?

Hi Allen,
Is it possible to clear the search bar like sending a callback when pressing a button? See image below:

You see, I have a global search on top, on my page view I actually have plenty of tables with local search on each table acting as filter. Is it possible to add a button on the searchbar (same with my global search on top), then pass a callback on the button to clear the search string? How do I do it?
Thanks.

@flipjs, I thinks I can support this feature or some solutions for you, but just a little question,
if clear the text in search bar, do you want the table search again(means clear the search condition)

Yes Allen, thats correct. When I click clear, it will reset the search and show all data again. Thanks for the quick reply.

Thanks, I'll find a best solution for you or add a feature in these day

Cool! Probably an option like searchClear={true} on the BootstrapTable, which will add a bootstrap button group on the search input.
Looking forward to this. Many thanks!

it's idea for this case, but just another question, if I add this clear button with search input field, which means your user need click that button by themself, am I right?

Hi Allen. That's correct. User has to click on the clear button. When the clear button was click, it will empty/clear the search input, and shows all data again on the table.

Great, I'll support this feature. Thanks

Great! Thank you Allen!

check example 6eb548e
Supported on v1.4.6

Excellent! Thank you @AllenFang !

Should have clearSearchText option to support languages/i18n, or use of "X" instead of the word "Clear"


tables.moor file can't use the table defined in database.dart file?

I'd like to define folders table in database.dart file. Is it possible for me to use it from tables.moor file?

Yes, this is possible. Just like how it works in Dart, you need to import files into a .moor file to use the tables defined in there.
So you can just do:
import 'database.dart'; -- If the two files are next to each other, but you can also use package: imports or other relative paths

CREATE TRIGGER IF NOT EXISTS folders_after_update
  -- ...


Master data

Master Data is a very well established term that describes non transactional business data that provide context for the transactions. It comes with its own set of theories and methodologies under the term Master Data Management.
In this sense, the term is used in the many UIs to mark such data. (e.g. list of persons, part is labeled "Master Data")
Proposal:
replace with defining data

Defining data is already in use. Master data could be replaced by:

Main data
Key data

Or we keep the term as master in this context is not discriminatory. There is no ‚slave‘. We should not ban ‚master‘ in general.
What’s your opinion?
Btw. ABS and Airwave are terms not known to nor used by this OSS project.

Thanks for the hint, I'll change to a less specific description.

I like key data.
personally I think that removing master in this case is a bit problematic due to the them more dificult identification as master data in the sense of Master Data Management.
I am ready to be convinced otherwise.

Cambridge english disctionary:
master
noun [ C ]
uk /ˈmɑː.stər/
us /ˈmæs.tɚ/

the person who owns, cares for, and controls an animal:
With careful training, a dog will obey its master completely.
a person who employs a servant or owns a slave:
Servants have to obey their masters.
a person who has control over a particular situation:
She was the master of her fate.
the captain of a ship that carries goods :
Ship's masters are in charge of a ship, its crew and any cargo it is carrying, at sea and in port.


⚠ Bofrost.de has degraded performance

In a7305d0, Bofrost.de (https://www.bofrost.de) experienced degraded performance:

HTTP code: 200
Response time: 1190 ms

Resolved: Bofrost.de performance has improved in 884fc8c.


Add build task to example

This hopefully makes it clearer how to use the cf resource with the new explicit outputs.

LGTM now, thanks!


Error building  using Carthage

Looks like there's an issue with building this repo using Carthage on master.
Here's what my Cartfile looks like:
github "moozzyk/SignalR-Client-Swift"
$carthage update --platform iOS
*** Building scheme "iOS SignalRClient" in SignalRClient.xcworkspace
Build Failed
	Task failed with exit code 65:
	/usr/bin/xcrun xcodebuild -workspace /Users/anuj/projects/ios/Eva/ios/Eva/Carthage/Checkouts/SignalR-Client-Swift/SignalRClient.xcworkspace -scheme iOS\ SignalRClient -configuration Release -derivedDataPath /Users/anuj/Library/Caches/org.carthage.CarthageKit/DerivedData/10.2.1_10E1001/SignalR-Client-Swift/0.4.2 -sdk iphoneos ONLY_ACTIVE_ARCH=NO CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES archive -archivePath /var/folders/dj/1hvxkr256vlcd2qft9ww4jq00000gn/T/SignalR-Client-Swift SKIP_INSTALL=YES GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=NO CLANG_ENABLE_CODE_COVERAGE=NO STRIP_INSTALLED_PRODUCT=NO (launched in /Users/anuj/projects/ios/Eva/ios/Eva/Carthage/Checkouts/SignalR-Client-Swift)

This usually indicates that project itself failed to compile. Please check the xcodebuild log for more details: /var/folders/dj/1hvxkr256vlcd2qft9ww4jq00000gn/T/carthage-xcodebuild.RFYYqd.log

Then I inspect the log file for build errors:
$cat /var/folders/dj/1hvxkr256vlcd2qft9ww4jq00000gn/T/carthage-xcodebuild.RFYYqd.log | grep error:

error: /Users/anuj/projects/ios/Eva/ios/Eva/Carthage/Checkouts/SignalR-Client-Swift/Pods/Target Support Files/Pods-iOS SignalRClient/Pods-iOS SignalRClient.release.xcconfig: unable to open file (in target "iOS SignalRClient" in project "SignalRClient") (in target 'iOS SignalRClient')
error: /Users/anuj/projects/ios/Eva/ios/Eva/Carthage/Checkouts/SignalR-Client-Swift/Pods/Target Support Files/Pods-iOS SignalRClient/Pods-iOS SignalRClient.release.xcconfig: unable to open file (in target "iOS SignalRClient" in project "SignalRClient") (in target 'iOS SignalRClient')
error: /Users/anuj/projects/ios/Eva/ios/Eva/Carthage/Checkouts/SignalR-Client-Swift/Pods/Target Support Files/Pods-iOS SignalRClient/Pods-iOS SignalRClient.release.xcconfig: unable to open file (in target "iOS SignalRClient" in project "SignalRClient") (in target 'iOS SignalRClient')

Did this start happening after spm update?
On Mon, Apr 29, 2019, 9:44 AM Anuj<EMAIL_ADDRESS>wrote:

Looks like there's an issue with building this repo using Carthage on
master.
Here's what my Cartfile looks like:
github "moozzyk/SignalR-Client-Swift"
$carthage update --platform iOS
*** Building scheme "iOS SignalRClient" in SignalRClient.xcworkspace
Build Failed
Task failed with exit code 65:
/usr/bin/xcrun xcodebuild -workspace /Users/anuj/projects/ios/Eva/ios/Eva/Carthage/Checkouts/SignalR-Client-Swift/SignalRClient.xcworkspace -scheme iOS\ SignalRClient -configuration Release -derivedDataPath /Users/anuj/Library/Caches/org.carthage.CarthageKit/DerivedData/10.2.1_10E1001/SignalR-Client-Swift/0.4.2 -sdk iphoneos ONLY_ACTIVE_ARCH=NO CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES archive -archivePath /var/folders/dj/1hvxkr256vlcd2qft9ww4jq00000gn/T/SignalR-Client-Swift SKIP_INSTALL=YES GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=NO CLANG_ENABLE_CODE_COVERAGE=NO STRIP_INSTALLED_PRODUCT=NO (launched in /Users/anuj/projects/ios/Eva/ios/Eva/Carthage/Checkouts/SignalR-Client-Swift)
This usually indicates that project itself failed to compile. Please check the xcodebuild log for more details: /var/folders/dj/1hvxkr256vlcd2qft9ww4jq00000gn/T/carthage-xcodebuild.RFYYqd.log
Then I inspect the log file for build errors:
$cat /var/folders/dj/1hvxkr256vlcd2qft9ww4jq00000gn/T/carthage-xcodebuild.RFYYqd.log | grep error:
error: /Users/anuj/projects/ios/Eva/ios/Eva/Carthage/Checkouts/SignalR-Client-Swift/Pods/Target Support Files/Pods-iOS SignalRClient/Pods-iOS SignalRClient.release.xcconfig: unable to open file (in target "iOS SignalRClient" in project "SignalRClient") (in target 'iOS SignalRClient')
error: /Users/anuj/projects/ios/Eva/ios/Eva/Carthage/Checkouts/SignalR-Client-Swift/Pods/Target Support Files/Pods-iOS SignalRClient/Pods-iOS SignalRClient.release.xcconfig: unable to open file (in target "iOS SignalRClient" in project "SignalRClient") (in target 'iOS SignalRClient')
error: /Users/anuj/projects/ios/Eva/ios/Eva/Carthage/Checkouts/SignalR-Client-Swift/Pods/Target Support Files/Pods-iOS SignalRClient/Pods-iOS SignalRClient.release.xcconfig: unable to open file (in target "iOS SignalRClient" in project "SignalRClient") (in target 'iOS SignalRClient')
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/moozzyk/SignalR-Client-Swift/issues/50, or mute the
thread
https://github.com/notifications/unsubscribe-auth/AAK7JJEMNAM32A7LAMD4E7DPS4QVDANCNFSM4HJE54TA
.

I just tried this to test out that theory using the .4.2 commit hash (see below). I believe this error due to the way the Xcode project integrates Cocoapods. If I remove the *.xcconfig files then it successfully builds.
$carthage update --platform iOS
*** Checking out SignalR-Client-Swift at "98609fc1bd59c965eb949f052c281681154b2ee1"
*** Building scheme "iOS SignalRClient" in SignalRClient.xcworkspace

Build Failed
	Task failed with exit code 65:
	/usr/bin/xcrun xcodebuild -workspace /Users/anuj/projects/ios/Eva/ios/Eva/Carthage/Checkouts/SignalR-Client-Swift/SignalRClient.xcworkspace -scheme iOS\ SignalRClient -configuration Release -derivedDataPath /Users/anuj/Library/Caches/org.carthage.CarthageKit/DerivedData/10.2.1_10E1001/SignalR-Client-Swift/98609fc1bd59c965eb949f052c281681154b2ee1 -sdk iphoneos ONLY_ACTIVE_ARCH=NO CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES archive -archivePath /var/folders/dj/1hvxkr256vlcd2qft9ww4jq00000gn/T/SignalR-Client-Swift SKIP_INSTALL=YES GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=NO CLANG_ENABLE_CODE_COVERAGE=NO STRIP_INSTALLED_PRODUCT=NO (launched in /Users/anuj/projects/ios/Eva/ios/Eva/Carthage/Checkouts/SignalR-Client-Swift)

This usually indicates that project itself failed to compile. Please check the xcodebuild log for more details: /var/folders/dj/1hvxkr256vlcd2qft9ww4jq00000gn/T/carthage-xcodebuild.m7qDUk.log

And I get the same result with the error log:
$cat /var/folders/dj/1hvxkr256vlcd2qft9ww4jq00000gn/T/carthage-xcodebuild.m7qDUk.log | grep error:

error: /Users/anuj/projects/ios/Eva/ios/Eva/Carthage/Checkouts/SignalR-Client-Swift/Pods/Target Support Files/Pods-iOS SignalRClient/Pods-iOS SignalRClient.release.xcconfig: unable to open file (in target "iOS SignalRClient" in project "SignalRClient") (in target 'iOS SignalRClient')
error: /Users/anuj/projects/ios/Eva/ios/Eva/Carthage/Checkouts/SignalR-Client-Swift/Pods/Target Support Files/Pods-iOS SignalRClient/Pods-iOS SignalRClient.release.xcconfig: unable to open file (in target "iOS SignalRClient" in project "SignalRClient") (in target 'iOS SignalRClient')
error: /Users/anuj/projects/ios/Eva/ios/Eva/Carthage/Checkouts/SignalR-Client-Swift/Pods/Target Support Files/Pods-iOS SignalRClient/Pods-iOS SignalRClient.release.xcconfig: unable to open file (in target "iOS SignalRClient" in project "SignalRClient") (in target 'iOS SignalRClient')

Any progress on this?

I haven't had a chance to look at this yet.
On Thu, Aug 1, 2019 at 2:44 AM Guido Hendriks<EMAIL_ADDRESS>wrote:

Any progress on this?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/moozzyk/SignalR-Client-Swift/issues/50?email_source=notifications&email_token=AAK7JJCKN5I745IRSEMDW3LQCLLCFA5CNFSM4HJE54TKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGOD3KO2YQ#issuecomment-517270882,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAK7JJHGBJPZ62NCUXKZ5NDQCLLCFANCNFSM4HJE54TA
.

I think the issue here is that Carthage is trying to build Examples but building Examples requires running pod install. Just to test this hypothesis I ran:
moozzyk:~/tmp/carthage-test$ ls
Cartfile
moozzyk:~/tmp/carthage-test$ carthage update --platform macOS
*** Checking out SignalR-Client-Swift at "3c72557a6ccdf2c19556d512e7259c517bad2d85"
*** xcodebuild output can be found in /var/folders/6v/x42kfppx18s4pgcnsw04fklc0000gn/T/carthage-xcodebuild.Ei2Ipy.log
*** Building scheme "SignalRClient-Package" in SignalRClient.xcodeproj
*** Building scheme "macOS SignalRClient" in SignalRClient.xcworkspace
Build Failed
	Task failed with exit code 65:
	/usr/bin/xcrun xcodebuild -workspace /Users/moozzyk/tmp/carthage-test/Carthage/Checkouts/SignalR-Client-Swift/Examples/SignalRClient.xcworkspace -scheme macOS\ SignalRClient -configuration Release -derivedDataPath /Users/moozzyk/Library/Caches/org.carthage.CarthageKit/DerivedData/10.3_10G8/SignalR-Client-Swift/3c72557a6ccdf2c19556d512e7259c517bad2d85 ONLY_ACTIVE_ARCH=NO CODE_SIGNING_REQUIRED=NO CODE_SIGN_IDENTITY= CARTHAGE=YES archive -archivePath /var/folders/6v/x42kfppx18s4pgcnsw04fklc0000gn/T/SignalR-Client-Swift SKIP_INSTALL=YES GCC_INSTRUMENT_PROGRAM_FLOW_ARCS=NO CLANG_ENABLE_CODE_COVERAGE=NO STRIP_INSTALLED_PRODUCT=NO (launched in /Users/moozzyk/tmp/carthage-test/Carthage/Checkouts/SignalR-Client-Swift)

This usually indicates that project itself failed to compile. Please check the xcodebuild log for more details: /var/folders/6v/x42kfppx18s4pgcnsw04fklc0000gn/T/carthage-xcodebuild.Ei2Ipy.log
moozzyk:~/tmp/carthage-test$ cd /Users/moozzyk/tmp/carthage-test/Carthage/Checkouts/SignalR-Client-Swift/Examples/Pods
-bash: cd: /Users/moozzyk/tmp/carthage-test/Carthage/Checkouts/SignalR-Client-Swift/Examples/Pods: No such file or directory
moozzyk:~/tmp/carthage-test$ cd /Users/moozzyk/tmp/carthage-test/Carthage/Checkouts/SignalR-Client-Swift/Examples
moozzyk:~/tmp/carthage-test/Carthage/Checkouts/SignalR-Client-Swift/Examples$ pod update
Update all pods
Updating local specs repositories
Analyzing dependencies
Downloading dependencies
Generating Pods project
Integrating client project
Sending stats
Pod installation complete! There are 0 dependencies from the Podfile and 0 total pods installed.

[!] The Podfile does not contain any dependencies.
moozzyk:~/tmp/carthage-test/Carthage/Checkouts/SignalR-Client-Swift/Examples$ cd -
/Users/moozzyk/tmp/carthage-test
moozzyk:~/tmp/carthage-test$ carthage update --platform macOS
*** Checking out SignalR-Client-Swift at "3c72557a6ccdf2c19556d512e7259c517bad2d85"
*** xcodebuild output can be found in /var/folders/6v/x42kfppx18s4pgcnsw04fklc0000gn/T/carthage-xcodebuild.pP6Cuh.log
*** Building scheme "SignalRClient-Package" in SignalRClient.xcodeproj
*** Building scheme "macOS SignalRClient" in SignalRClient.xcworkspace

(after the initial failure of carthage update I went to the Carthage/Checkouts/SignalR-Client-Swift/Examples folder and ran pod update and then re-run carthage update).
I think that ideally the Examples folder should not be built. I wonder if it can be excluded with a Cartfile.ignore file

Just noticed that the PR to add Cartfile.ignore file was never merged. For reference here is an issues in Carthage that seems related https://github.com/Carthage/Carthage/issues/1227. Looks like a workaround for now can be:
carthage update --no-build
cd Carthage/Checkouts/SignalR-Client-Swift/Examples
pod update
cd -
carthage build --platform macOS

Fixed via 0a201951e559a821740d252df843efba365cd12e


docs(barchart): add documentation to BarChart

Add documentation to the BarChart widgets and its sub-modules.
Relates to #386.
Screenshots

Most of it should be fixed. Here's an updated screenshot of the BarChart type documentation:


enhancement Log out end version before truncating new tablet data (#39924)

Proposed changes
As title.

run buildall

run buildall

run buildall


[reggen] Ordering required between regwen and reg

This is pretty low priority, but I did encounter the issue, so I figure I may as well flag it.
Right now if a regwen register is defined as hwext=true, the dv ral_gen flow bombs out. Since it's an external register, the base class isn't generated, however, registers it locks still attempt to reference it, causing a null pointer issue.
It's not a big issue because it's trivial to convert this to a register inside the regfile and appropriately set de/d.  Still I figure I would point it out in case other people do this.  Maybe we can just explicitly error out on hwext when it comes to regwen.

so my previous description of the issue was completely wrong.
Turns out the actual issue it seems is that the in hjson, the regwen needs to be declared ahead of the register it protects.
Maybe this is known already, if so, let me know, and i'll close the issue.

Thanks for pointing out.
So just need to move the regwen declaration in the Hjson to the top?

yeah basically. This came up because Scott pointed out CTRL registers should be the first. I just so happened to have a hw managed lock register that managed the CTRL, so I mistakenly thought the issue was the hwext.

interesting, that seems fixable and should be fixed. but not the end of the
world if the order gets a little funny as a workaround until then.
On Mon, Apr 13, 2020 at 11:32 PM tjaychen<EMAIL_ADDRESS>wrote:

yeah basically. This came up because Scott pointed out CTRL registers
should be the first. I just so happened to have a hw managed lock register
that managed the CTRL, so I mistakenly thought the issue was the hwext.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/lowRISC/opentitan/issues/1953#issuecomment-613252221,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AJZQKVLKURL4FLMI32Z5ANTRMP7O7ANCNFSM4MHOUV6A
.

should i just document this in the regtool spec and close this issue? There's no real reason we have to fix this right?

In the interest of making decisions and moving on, I agree let's spec it and close. I'll suggest a quick change for this one, thanks @tjaychen


Show gas estimation errors, refactor popup/tab id, show loading tranactions

instead of figuring out if a given window/tab id is window or tab, refactor them to be always separate

Show gas estimation errors:

show pending queued transactions that are simulating:

@coderabbitai review

@coderabbitai review


LoadError: cannot load such file -- ./_sass/bourbon/lib/bourbon.rb

Idears?
$ rake watch
Starting to watch source with Jekyll and Sass...
LoadError: cannot load such file -- ./_sass/bourbon/lib/bourbon.rb
  Use --trace for backtrace.
LoadError: cannot load such file -- ./_sass/bourbon/lib/bourbon.rb
  Use --trace for backtrace.
       Deprecation: Jekyll now uses subcommands instead of just switches. Run `jekyll help' to find out more.
       Deprecation: The --server command has been replaced by the 'serve' subcommand.
       Deprecation: The switch '--auto' has been replaced with '--watch'.
invalid option: --auto

Hi, cd into _sass and bourbon install does not fix this:
** Invoke default (first_time)
** Invoke watch (first_time)
** Execute watch
Starting to watch source with Jekyll and Sass...
LoadError: cannot load such file -- ./_sass/bourbon/lib/bourbon.rb
Use --trace for backtrace.
/usr/local/var/rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/liquid-2.4.1/lib/liquid/htmltags.rb:43: warning: key "index0" is duplicated and overwritten on line 46
LoadError: cannot load such file -- ./_sass/bourbon/lib/bourbon.rb
Use --trace for backtrace.
/usr/local/var/rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/maruku-0.6.1/lib/maruku/output/to_latex_entities.rb:58: warning: constant ::Fixnum is deprecated
Configuration from /Users/soniajoseph/GitHub/tirtha/_config.yml
Auto-regenerating enabled: /Users/soniajoseph/GitHub/tirtha -> /Users/soniajoseph/GitHub/tirtha/_site
[2019-11-17 06:20:29] regeneration: 613 files changed
[2019-11-17 06:20:29] INFO  WEBrick 1.4.2
[2019-11-17 06:20:29] INFO  ruby 2.6.2 (2019-03-13) [x86_64-darwin15]
[2019-11-17 06:20:29] INFO  WEBrick::HTTPServer#start: pid=50947 port=4000
/usr/local/var/rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/posix-spawn-0.3.6/lib/posix/spawn.rb:455: warning: constant ::Fixnum is deprecated
/usr/local/var/rbenv/versions/2.6.2/lib/ruby/gems/2.6.0/gems/maruku-0.6.1/lib/maruku/output/to_html.rb:940: warning: constant ::Fixnum is deprecated


Reason for Y021 (docstring in stubs)

Hi,
what lead you to the decision to introduce the Y021 warning? I can't find it in PEP 561.
In my use case I am creating *.pyi files for a cythonized module. While that gives me type hints, I would also love to have docstrings. It seems like I have nowhere to put them - the cythonization removes everything and flake protests if I leave them in the pyi files.
It also generates Y010, although there's nothing but "..."
Example.pyi:
def nothing() -> None:
    """
    does nothing
    """
    ...

def something(a: int) -> str:
    """
    does something
    """
    ...

class Klass:
    """
    oh hi I'm a docstring
    """

    def __init__(self) -> None: ...

    def ret(self, nuthin: bool) -> None: ...

Docstrings in stubs have undefined behavior. But you can always disable Y021 using flake8's configuration.

It also generates Y010, although there's nothing but "..."

Oh, that seems slightly buggy, if it's triggering two error codes instead of one.

As an addendum: I don't think that using docstrings in stubs is actively harmful, but docstring might have special semantics in a future typing spec that could in theory be incompatible with your stubs. I think the danger is fairly low, though.

It also generates Y010, although there's nothing but "..."

Oh, that seems slightly buggy, if it's triggering two error codes instead of one.

Actually, is that a bug? This is legal syntax:
def nothing() -> None:
    """
    does nothing
    """

So the ellipses in your nothing() and something() functions are arguably redundant.
Our error message could maybe be improved, though.

OK, thanks, I'll use them in suppress the warning.
Removing ellipsis and leaving empty body looks like a good solution, thanks.
def nothing() -> None:
    """
    does nothing
    """

Y009 also suggests that ellipsis should be there, but I understand this is a somewhat special case.

Y009 also suggests that ellipsis should be there, but I understand this is a somewhat special case.

No, the checks should be independent of each other, so it's good to know if they're stomping on each other :) This is useful feedback!


docs: add authentication to user settings

Fixes https://github.com/daytonaio/enterprise-docs/issues/184

@fabjanvucina @ivan-burazin


"Auth completed." screen doesn't auto-close on Expo-Web-Browser

Hello!
Is there any issue regarding the automatic closure of the browser after OAuth2 (using Expo-RN)? I recall someone mentioning this, but I couldn't locate it, and I haven't been able to resolve it either.
My login function:
const googleLogin = async () => {
    try {
      const result = await backendClient?.collection("users").authWithOAuth2({
        provider: "google",
        urlCallback: (url) => {
          WebBrowser.openBrowserAsync(url).catch((err) => {
            console.log("failed to open url", err);
          });
        },
      });
      console.log(result?.token);
      setAuthState({
        token: backendClient!.authStore.token,
        authenticated: true,
      });
    } catch (error) {
      console.log("erro authcontext lin 71", error);
    }
  };

The browser window will be automatically closed if it is allowed but that's not always the case (see window.close docs).
Or in other words, it may not be actually possible and it will depend on the platform, browser, how it was opened, etc.
This is also why the message implies that users can manually go back to the app "if this window is not automatically closed".
Alternatively you can try calling WebBrowser.dismissBrowser() somewhere after the console.log (note that the documentation mentions that it works only for iOS) or some other methods from the expo package but in any case I don't think there is anything we can do on the PocketBase side.


Update MongoDBHandler.php

Convert the date to a native MongoDate to make it easier to sort

@josephspurrier You might want to revisit this PR as MongoDBHandler has changed quite a bit, and 2.0 is now >= PHP 7.0. MongoDate is now MongoDB\BSON\UTCDateTime with a millisecond integer as the input.

I think it can probably be closed actually as I merged (https://github.com/Seldaek/monolog/pull/724) for 2.0 yesterday that was done by the mongodb people. And it includes UTCDateTime support.

Great, thanks.


Remove Obsolete RunSCUBA.ps1 script.

🐛 Summary
When running .\RunSCUBA.ps1 getting the following error....
PS C:\tmp\ScubaGear-1.0.0\utils> .\RunSCuBA.ps1
Invoke-SCuBA : Cannot validate argument on parameter 'ProductNames'. The argument "onedrive" does not belong to the set
"teams,exo,defender,aad,powerplatform,sharepoint,*" specified by the ValidateSet attribute. Supply an argument that is in the set and then try the command again.
At C:\tmp\ScubaGear-1.0.0\utils\RunSCuBA.ps1:33 char:18

Invoke-SCuBA @SCuBAParams

             ~~~~~~~~~~~~

CategoryInfo          : InvalidData: (:) [Invoke-SCuBA], ParameterBindingValidationException
FullyQualifiedErrorId : ParameterArgumentValidationError,Invoke-SCuBA

Add any screenshots of the problem here.

Thanks for the report.  The RunScuba script is a relic at this point and we should just remove it.  Please follow the instructions on the README page on how to run ScubaGear.

Piggybacking off of this issue, there a couple of other relics we should remove as well:

[ ] utils/RunSCuBA.ps1
[ ] utils/RegoCachedProviderTesting.ps1
[ ] Testing/Functional/RegoCachedProviderTesting.ps1


Exploratory Refactoring

increase readability in a few places

Closing this PR for this one: https://github.com/openscd/open-scd/pull/1562


How to increase the height of the spike.

AudioWaveform library uses normalize() function to make waveform height "balanced" for all audio files.
I don't understand what exactly you need. Please, provide more details or screenshots


fix:applications sort by provider

fixed: https://github.com/hexa-org/policy-orchestrator/issues/288

@jingchu000 - Thank you again for doing this. I have approved the PR, you can merge.

@saurabh-io ，I appreciate your guidance, what other actions do I need to take? I don't have the merge option.

@saurabh-io ，Thank you very much. Who's going to help me with the merge?

@jingchu000 - I went ahead and merged it.


fix clipPath not works on android N 7.0

@YorkShen
here is my polyfill. just judge the scaleX、scaleY and so on to fix。
the one with is broken at release-0.16。 see first yellow box. click it will do the animation.

fixed with the polyfill. clip child view works on the first yellow box.

First of all, thank you for your contribution!
Please makes sure that these checkboxes are checked before submitting your PR, thank you!

CheckList:
if isBugFix :

[ ] Make sure that you add at least one unit test for the bug which you had fixed.

elif isNewFeature :

[ ] Update API docs for the component.
[ ] Update/Add demo to demonstrate new feature.
[ ] Update test scripts for the feature.
[ ] Add unit tests for the feature.

https://issues.apache.org/jira/browse/WEEX-84
Demo:
http://rax.alibaba-inc.com/playground/1094b05a-0b0e-4ec3-a962-c91c8d22f21f
APK:
http://mtl.alibaba-inc.com/oss/mupp/55218/2785369/2785369/f46de55f54a9b9a251d8240640f2d840/taobao-android-debug.apk

The APK link can't be opened.

@wispy316 thanks a lot for your pull request.
There are somethings wrong for all weex developers and users.

please not use alibaba local links that other people can't open,such as 'mtl.alibaba-inc.com','rax.alibaba-inc.com'.
2.By the way,  if PR title is of the form [WEEX-xxxx], xxxx is the relevant JIRA number,  it will be referenced to the JIRA issue automaticly.

have a better way to join weex.~

update url, @gurisxie  @cxfeng1 @cxfeng1

has merge rebase ,but bot seems broken.


Rocket.Chat lacks of sharing-feature

Description
It is not possible to share something from another app to the rocket.chat-app, e.g. an interesting link from a webbrowser to a channel in RC
Devices and Versions
Your Rocket.Chat.Android version: 2.6
Your Rocket.Chat Server version: 0.67
Galaxy Note 8, Android 8.0
Steps to reproduce
Open any app on the smartphone with the ability to share to another app: rocket.chat-app is missing as a possible target.
IMHO a very important feature RC should support. Thanks!

I agree, we really need this feature. It's already on our roadmap to include it soon!
Closing this since it's duplicate of #98


change build so it builds the extension as well

/skip-changelog

/skip-changelog

/skip-changelog

/skip-changelog

/kick

/skip-changelog


List of things to consider cleaning up in the light curve notebook

Collecting a list of things we may consider doing as we finish up the notebook light_curve_generator.md.
Formatting

[ ] Apply a max line length.
[ ] Run autopep8 on .py files.
[ ] Any other auto formatting tool we should run for either .py or .md (myst) files?

Function docstrings

[ ] Review for accuracy.

Notebook text

[ ] Review for accuracy (e.g., since we switched coords_list --> sample_table, instructions in section 1.1 should be updated).
[ ] Review sections for completeness:

[ ] Non-standard Imports
[ ] References

[ ] Some of the serial cells have text explaining the catalog data or query method (e.g., WISE) but some don't (e.g., ZTF). Consider standardizing this.

Code
Note that several MAST functions still iterate over individual sample objects rather than loading in bulk. This is a known issue being handled separately (see #165, #166, #179).
General

[ ] #174
[ ] #159
[x] #155
[ ] #182
[ ] #184
[ ] Since it's hard to attach units, etc. to DataFrame columns/values, consider renaming columns to be explicit (e.g., "flux" --> "flux_mjy" and "time" --> "mjd"). OTOH, we may run into issues that mean this is just more confusing (to the point of deceiving), like ZTF actually uses "hmjd" rather than "mjd".

fluxconversions.py

[ ] See if we can use Astropy methods in place of any functions in this file (prompted by https://github.com/fornax-navo/fornax-demo-notebooks/pull/181#discussion_r1411663452).

heasarc_functions.py

[ ] The two lists heasarc_cat and max_error_radius have an implicit, one-to-one relationship. Replace the two lists with a dict that ties the correct values together. Then iterate over the dict instead of a list index.

mast_functions.py

[ ] Remove this file. It's not being used anywhere.

panstarrs.py

[ ] Remove try/except if possible. Otherwise, move as much code as possible outside the try block as possible.

plot_functions.py (create_figures function)

[ ] Remove sample_table as an argument to create_figures. Iterate over df_lc (grouped by objectid) instead of sample_table rows.
[ ] The function is very long function; breaking it up into smaller ones would improve readability. Consider making separate functions each band (or group of bands) and for the formatting.
[ ] Remove the manual counter cc. If this counter is really needed, get it by adding enumerate to the for loop.

sample_lc.py

[ ] Update it to, e.g., use sample_table. (This is a script version of the parallel section of the notebook, meant to be called from command line, but has not been kept up to date.)
[ ] Alternately, consider making the modules directly callable from the command line and write a .sh script to execute them. This should speed up bulk runs because ZTF could use multiple workers.

sample_selection.py

[ ] nonunique_sample function: either remove it or update it to return a Table like clean_sample does.

tde_functions.py

[ ] Remove this file. It doesn't appear to be in use.

TESS_Kepler_functions.py

[ ] Remove the try/except if possible. Otherwise, move as much code as possible outside the try block and catch a specific error in the except statement.
[ ] Iterate over the search results directly instead of over the index numlc.

ztf_functions.py

[ ] Use either variable name ztf_radius or radius, but not both.
[ ] Replace manual flux unit conversion with Astropy methods.

@bsipocz what's your input on the Formatting section? What standards should we apply for .py and .md files?

re: sample_lc.py and nonunique_sample inside of sample_selection.py
Both of these are not part of light_curve_generator.md instead ML_AGNzoo.md
What to do with them depends on our goal for the ML notebooks.  I think they should start with a pre-made sample of light curves, and not need to run light_curve_generator.  My reasoning is twofold.  1) speed of running the ML notebooks will be faster without first having to generate the light curves.  2) for anyone wanting to use the ML notebooks they wouldn't have to understand the extra pieces of code that generate the light curves, they could just focus on the code in the ML notebooks themselves.
If that is ok with everyone, then we should remove sample_lc.py (but make sure @xoubish  has a copy somewhere since she needs it to generate the initial sample), and also remove nonunique_sample

I would say we could add a CI job to check on the .py formatting

I'm in favor of that, but I'd like to keep the scope of this Issue more narrowly focused on cleaning up just the light curve notebook.
I have specific formatting preferences, especially for python code. While I know that your preferences are different than mine, I don't know exactly what your preferences are. So I'd like our group to come to a consensus before I make any broad changes there. Do you want to discuss specifics to be applied to this notebook? Or do you think we should leave the formatting alone for now?

I have specific formatting preferences, especially for python code

Something that is PEP8 compatible. I don't like to be as strict and whitespace heavy as black and would rather just make flake8 or similar pass on the codebase, but I agree, getting a consensus would be nice and I suppose can be done quickly. Shall we put it on the agenda for this afternoon?

@jkrick That's all fine with me. We'll just need to figure out where to store the pre-made sample of light curves. (I know we're using Google Drive for this right now, but want to figure out a more general solution.)

I have added formatting preferences to the agenda for this afternoon, but I would be super happy to just adopt whatever you two think is best.  This is definitely your domain.

And I am pretty sure I have a gitlab issue in with the Navteca people about where we should be storing data as a long term solution instead of google drive.

After looking over everything in the directory, I fully agree that MAST_functions.py can be removed.  I don't see it used anywhere.


[$500] LHN - Red dot does not appear in LHN conversation when IOU deletion error occurs

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

Version Number: 1.4.16-3
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal Team
Slack conversation:
Action Performed:

Open New Expensify app
Log in with any account
Navigate to any conversation with an user you have access to and Request $10
Disable the internet connection on the main testing device.
As the secondary user/device navigate to the conversation with the main user where the 10$ were just requested
As the Secondary user/device Pay the IOU via "Pay elsewhere"
On the main testing device while offline - cancel the 10$ IOU
Enable the internet connection on the main testing device
Navigate to a paid IOU

Expected Result:
The red dot should appear in the LHN conversation when the error is caused by an offline deletion of a paid IOU
Actual Result:
A red dot does not appear in the LHN conversation when the error is caused by a paid IOU being removed offline
Workaround:
Unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Screenshots/Videos
Add any screenshot/video evidence

https://github.com/Expensify/App/assets/78819774/2c3b5833-437e-4e9b-bc06-98238b40b510
View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01c5cf5023e3aab261
Upwork Job ID:<PHONE_NUMBER>951575552
Last Price Increase: 2023-12-23

@tienifr Your proposal doesn't seem right in this case. Your RCA is correct but solution seems wrong

Proposal
Problem Statement
The red dot isn't appearing in the Expensify LHN conversation when a paid IOU is removed offline.
Root Cause
During the deletion of a money request, the IOU.deleteMoneyRequest.failureData doesn't set the error message to the reportPreviewAction in Onyx.
Solution
To resolve this, we propose enhancing the code responsible for updating ONYXKEYS.COLLECTION.REPORT_ACTIONS for chatReport. Instead of a simple merge, explicitly set the errors field for the reportPreviewAction. Also, modify ReportActions.clearReportActionErrors to clear errors in both the IOU report and its parent chat.
Alternative Solutions Explored
Alternatively, making the IOU report 'unread' when an error emerge, could push it to the top of the list upon reconnection, eliminating the need to send the error message in two places.

@tienifr Your proposal doesn't seem right in this case. Your RCA is correct but solution seems wrong

@shubham1206agra just curious what do you think seems wrong about it?
Since we're doing the same thing when creating money request here. That's why creating money request doesn't have the same problem.

Oh shoot, I actually got confused with something else. Your solution is correct. Sorry for the confusion.

Currently even for other money request-related errors (like when creating money request fails), if we want to clear error by clicking "X", we have to clear errors individually in the report preview action and the IOU report. This will be the same for the delete money request error here.

Lets keep this as it is right now as it is out of scope for this PR.

@tienifr's proposal looks good to me
🎀👀🎀 C+ reviewed

Agreed, let's go with @tienifr 's proposal!

Awaiting completion of BZ checklist 🙏

BugZero Checklist: The PR fixing this issue has been merged! The following checklist (instructions) will need to be completed before the issue can be closed:

[x]  [@shubham1206agra] The PR that introduced the bug has been identified. Link to the PR: https://github.com/Expensify/App/pull/17583
[x]  [@shubham1206agra] The offending PR has been commented on, pointing out the bug it caused and why, so the author and reviewers can learn from the mistake. Link to comment: https://github.com/Expensify/App/pull/17583/files#r1463432049
[x]  [@shubham1206agra] A discussion in #expensify-bugs has been started about whether any other steps should be taken (e.g. updating the PR review checklist) in order to catch this type of bug sooner. Link to discussion: Not required
[x]  [@shubham1206agra] Determine if we should create a regression test for this bug. No
[x]  [@shubham1206agra] If we decide to create a regression test for the bug, please propose the regression test steps to ensure the same bug will not reach production again.
[ ]  [@Christinadobrzyn] Link the GH issue for creating/updating the regression test once above steps have been agreed upon:

Sorry for the delay- paying this out.
Payouts due:
Issue Reporter: NA
Contributor: $500 @tienifr (paid in Upwork)
Contributor+: $500 @shubham1206agra (in Upwork)
Eligible for 50% #urgency bonus? NA
Upwork job is here.
@shubham1206agra can you accept our offer in Upwork and I'll pay you? Thanks!

Accepted

Awesome! paid in Upwork based on this payment summary - https://github.com/Expensify/App/issues/33535#issuecomment-1906852954
Closing this out as complete! Thanks everyone!


chore: remove access token

Changes

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1312
#1311  👈
#1310
#1309
#1308
#1307
#1306
#1305
main

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

Join @NathanFlurry and the rest of your teammates on  Graphite


Easting labels not displayed on mobile unless toolbar is hidden

Shouldn't be fixed as part of the library, implement the fix client-side with CSS:
https://css-tricks.com/css-fix-for-100vh-in-mobile-webkit/


Got 500 internal error

Hello, everytime I try to get /message, I have an internal 500 error:
500 Internal Server Error
ERROR:    Exception in ASGI application
Traceback (most recent call last):
File "/usr/local/lib/python3.8/dist-packages/uvicorn/protocols/http/httptools_impl.py", line 390, in run_asgi
result = await app(self.scope, self.receive, self.send)
File "/usr/local/lib/python3.8/dist-packages/uvicorn/middleware/proxy_headers.py", line 45, in call
return await self.app(scope, receive, send)
File "/usr/local/lib/python3.8/dist-packages/fastapi/applications.py", line 171, in call
await super().call(scope, receive, send)
File "/usr/local/lib/python3.8/dist-packages/starlette/applications.py", line 102, in call
await self.middleware_stack(scope, receive, send)
File "/usr/local/lib/python3.8/dist-packages/starlette/middleware/errors.py", line 181, in call
raise exc from None
File "/usr/local/lib/python3.8/dist-packages/starlette/middleware/errors.py", line 159, in call
await self.app(scope, receive, _send)
File "/usr/local/lib/python3.8/dist-packages/starlette/exceptions.py", line 82, in call
raise exc from None
File "/usr/local/lib/python3.8/dist-packages/starlette/exceptions.py", line 71, in call
await self.app(scope, receive, sender)
File "/usr/local/lib/python3.8/dist-packages/starlette/routing.py", line 550, in call
await route.handle(scope, receive, send)
File "/usr/local/lib/python3.8/dist-packages/starlette/routing.py", line 227, in handle
await self.app(scope, receive, send)
File "/usr/local/lib/python3.8/dist-packages/starlette/routing.py", line 41, in app
response = await func(request)
File "/usr/local/lib/python3.8/dist-packages/fastapi/routing.py", line 196, in app
raw_response = await run_endpoint_function(
File "/usr/local/lib/python3.8/dist-packages/fastapi/routing.py", line 149, in run_endpoint_function
return await run_in_threadpool(dependant.call, **values)
File "/usr/local/lib/python3.8/dist-packages/starlette/concurrency.py", line 34, in run_in_threadpool
return await loop.run_in_executor(None, func, *args)
File "/usr/lib/python3.8/concurrent/futures/thread.py", line 57, in run
result = self.fn(*self.args, **self.kwargs)
File "/usr/local/lib/python3.8/dist-packages/signal_cli_rest_api/app/api/api_v1/endpoints/messages.py", line 24, in get_messages
return [json.loads(m) for m in response.split("\n") if m != ""]
AttributeError: 'coroutine' object has no attribute 'split'
/usr/local/lib/python3.8/dist-packages/uvicorn/main.py:390: RuntimeWarning: coroutine 'run_signal_cli_command' was never awaited
loop.run_until_complete(self.serve(sockets=sockets))
RuntimeWarning: Enable tracemalloc to get the object allocation traceback

Same here, the docker image was ok though, Although I didn't want to go for the docker version. In addition, it is impossible to send / receive messages containing anything else than alphanum. It would be a fantastic piece of software otherwise ...

Same here, the docker image was ok though, Although I didn't want to go for the docker version. In addition, it is impossible to send / receive messages containing anything else than alphanum. It would be a fantastic piece of software otherwise ...

I had a similar issue and was able to resolve it by changing the return statement in utils.py, line 86 from: return await process.stdout.readline() to return (await process.stdout.read()).decode()
My understanding is that this allows multiple envelopes to be received by the signal-cli task instead of reading just the first one.

I had a similar issue and was able to resolve it by changing the return statement in utils.py, line 86 from: return await process.stdout.readline() to return (await process.stdout.read()).decode()
My understanding is that this allows multiple envelopes to be received by the signal-cli task instead of reading just the first one.


ConcatDataset

Description
Concatenate multiple datasets; datasets can be of different classes.
Checklist
Essentials

[x] Changes are complete (i.e. I finished coding on this PR)
[x] All changes have test coverage
[x] Code is well-documented

Changes

[x] ConcatDataset

Yes, it is not required, however we may still support it as long as there is no downside

#381


E-commerce-Website

an ecommerce web project is very tough for beginners, it is for intermediate peoples. This repository is dedicated for beginner level react concepts & projects.


No saving alert when renaming an unsaved file

VSCode Version: 1.27.2
OS Version: macOS 10.14

Steps to Reproduce:

Edit a file and rename the file.
The edited content is missing.

Does this issue occur when all extensions are disabled?: No

Not covered.

I restart my vscode, and the issue is gone.


Supply - wait for "Update is live in the store" response from Google Play

Issue Description
Is there an option for supply to add a flag for waiting until the app hits the Play Store (same like in pilot you can wait for processing to be done).
Usually it can take couple of hours and we would like to send an automated email from jenkins to our testers when the app is live in the store.
Fastlane 1.105.3

@tomachi thanks for the feature request. We use the Google Api Client for interacting with Google Play. If there is a api for knowing when a version is live, this is something that we'd accept a PR for. 👍


With artist information fixed

Description (required)
Fixes #3147
What changes did you make and why?
Tests performed (required)
have tested the artist extraction logic externally as my username and display name is the same. https://ideone.com/iCURPU

Codecov Report

Merging #3232 into master will decrease coverage by <.01%.
The diff coverage is 0%.

@@            Coverage Diff            @@
##           master   #3232      +/-   ##
=========================================
- Coverage    6.01%   6.01%   -0.01%
=========================================
  Files         270     270
  Lines       11600   11605       +5
  Branches      905     905
=========================================
  Hits          698     698
- Misses      10845   10850       +5
  Partials       57      57

Impacted Files
Coverage Δ

app/src/main/java/fr/free/nrw/commons/Media.java
17.9% <0%> (-0.58%)
:arrow_down:

Continue to review full report at Codecov.

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

Thanks for updating the PR title @neslihanturan. :)
I will try to follow this structure in the future.


Changing the pullSecret Secret name

py-mtcli
Description
The Secret needs a deterministic name, but not need to make it related to the addon itself, as we creat it in the namespace of the addon anyway.
This will make it easier to find the secret, regardless the operator looking for it.
Checklist
For any modification to managedtenants/bundles/

[x] $ managedtenants --addons-dir=../managed-tenants-bundles/addons --dry-run bundles (successfuly built all addons)
[x] $ managedtenants -addons-dir=../managed-tenants-bundles/addons --addon-name=<addon> bundles --quay-org <personal_org> (successfuly built and push a single addon)

LGTM


Unable to debug with  SAM local invoke in Node.js example

Hi all,
in nodejs-example-extension example for Node.js platform something during registration phase brokes the debugger when runs locally on VS Code using sam local invoke --port 6767 ... on a Lambda that includes this layer.
The following is a snap of the debug logs when launched from VS Code:
START RequestId: 05da599b-f76d-494e-905b-bead9860f186 Version: $LATEST
nodejs-example-extension  launching extension
Debugger listening on ws://<IP_ADDRESS>:6767/95282789-af6d-4c40-b544-b1d70e0650c2
For help, see: https://nodejs.org/en/docs/inspector
Debugger attached.
hello from extension
register
extensionId 0e16eae5-5e84-4b22-a204-c54424793f69
next
Starting inspector on <IP_ADDRESS>:6767 failed: address already in use
invoke
next
...

notice the Starting inspector on <IP_ADDRESS>:6767 failed: address already in use error line in logs, after that all set breakpoints are ignored and it's impossible to debug every Lambdas.
this is the VS Code debug task setup:
{
        "name": "lambda_with_example_layer",
        "type": "pwa-node",
        "request": "attach",
        "address": "localhost",
        "port": 6767,
        "localRoot": "${workspaceFolder}/lambda_with_example_layer",
        "sourceMaps": true,
        "remoteRoot": "/var/task",
        "protocol": "inspector",
        "stopOnEntry": false,
        "skipFiles": [
          "<node_internals>/**"
        ]
}

Is there any debugger/SAM/Docker configuration that i missed? Or is something else deeper in the layer execution flows that broke debugging in a container with SAM local?

+1

+1

+1

+1

+1

+1

+1


Remove executable bit from text files

Text files definitely don't need it.
Fixes #2181.

This is likly also in stable, can you do it there. We will merge stable afterwards to develop.
Also please add an issue.  The issues are listed in a new revision.

I think I don't understand yet when something should go to develop and when it should go to stable. This issue is definitely not urgent or critical in any sense and doesn't require to hit a release any time soon, it is just something I stumbled across and quickly threw in a PR. Shouldn't stuff like that go to develop, and reach stable at some point through a release?
Anyway, I can re-target this to stable as well, if you want.

stable would be good.
so in principle when something is in stable which was the past from develop and we can solve it there we do it there. Then we get it with a merge (less conflicts) into develop.
When something is further developed already so it is different to what we have in stable, we do it in develop. Currently develop is quite different from stable but this is also there an issiue.

OK. I don't think I like this approach as there are effectively two branches that are actively being worked on and there is a lot of potential for merge issues between them, but it is what it is I guess.

Also please add an issue. The issues are listed in a new revision.

I've added an issue, but it is also possible to add milestones to PRs (PRs and issues are treated very similar by GitHub, they even share the same auto-increment counter. A PR is basically just an issue with code attached.). If the PR has a milestone attached it would be listed in the issues closed by a milestone, which is then referenced by a release. For some things (e.g. a small code change without a bigger issue attached, like here) I just think that creating both an issue and a PR adds unnecessary overhead.

We can maybe use also the Milestone in the PR for such things. An issue has a different position. First agree that it is an issue and discuss a scope how to fix it.
Issues have also the option to declare them as "good first issue".

We can maybe use also the Milestone in the PR for such things.

If we added milestones to both a PR and an issue for the same topic then this would become redundant. So either an issue with a milestone attached and then a PR for that issue or a PR with a milestone but without an issue. Having everything show up twice in the changelog would be bad.

An issue has a different position. First agree that it is an issue and discuss a scope how to fix it.

I agree, but only if the change even necessitates a discussion. I think there is no discussion necessary for removing the executable bit from e.g. the changelog, so I didn't open an issue. Also, if I first opened an issue and waited long enough for anyone who wants to to chime in then a 5 minute task suddenly gets stretched over days, if I don't immediately open the PR as well. If I open then PR immediately then first creating an issue is just overhead, discussion can happen in PRs as well and if the change is unwanted those can just be closed.
TL;DR if the change is rather uncontroversial and a ~5 minute task to code up then I think an issue is just unnecessary. But that is just my opinion, if you want I can also start opening issues for those things.

A newcomer to open source, github and MSS needs very simple issues. A 5 minute task for us is an ideally good first issue for someone learning all the tools and workflows. We only have to take care that we have a few of these.
So simply consider whether you should do it yourself now or make a good first issue out of it and wait a while. You did this already. We tend to have hardly any good first issues, because we also do everything that is easy immediately. So this is just a suggestion or a reminder of very simple task for others.

I didn't think about it that way. I'll keep it in mind.


Speed up examples

The examples may need some speed up to help with the CI load.
From discussions with @jchodera:

I think the issue is (1) the size of the system, and (2) the LocalEnergyMinimizer.minimize call
If the example system could be smaller---or perhaps if we can just run it by capping the amount of explicit solvent that is added (or preventing solvent from being added)---it will be much faster
We might need to add in some additional arguments to skip the solvent addition or limit the number of waters that can be added

I'm making this issue to explore these and other possibilities to speed up the examples.

Closing, cleaned examples should be running now in a reasonable amount of time. Re-open if needed.


Allow an immediate break when a server responds with HTTP Error 429

Checklist

[X] I'm requesting a feature unrelated to a specific site
[X] I've looked through the README
[X] I've verified that I'm running yt-dlp version 2022.07.18 (update instructions) or later (specify commit)
[X] I've searched the bugtracker for similar issues including closed ones. DO NOT post duplicates
[X] I've read the guidelines for opening an issue

Provide a description that is worded well enough to be understood
It seems that yt-dlp will continue to cycle through fragment retries even when a server responds with a rate-limiting rejection such as 'HTTP Error 429'. This seems time-wasting and counterproductive to potentially having to wait for that rate-limiting block to expire.
My request is for a feature or option to not allow retries to continue to cycle when the server is responding (or perhaps repeatedly responding?) with status error 429.
Thank you for your time and consideration. My apologies if I could not find a duplicate of this request.
Provide verbose output that clearly demonstrates the problem

[X] Run your yt-dlp command with -vU flag added (yt-dlp -vU <your command line>)
[ ] Copy the WHOLE output (starting with [debug] Command-line config) and insert it below

Complete Verbose Output
Not a complete verbose, but an example snippet of the unnecessary retries:

[hlsnative] Downloading m3u8 manifest
[hlsnative] Total fragments: 182
[download] Destination: C:\yt-dl\WebSite\VIDEO_NAME [1920x1080] [videoID] [formatCode].mp4
[debug] File locking is not supported. Proceeding without locking
WARNING: The download speed shown is only of one thread. This is a known issue and patches are welcome
[download] C:\yt-dl\WebSite\VIDEO_NAME [1920x1080] [videoID] [formatCode].mp4.part-Frag179 has already been downloaded
[download] C:\yt-dl\WebSite\VIDEO_NAME [1920x1080] [videoID] [formatCode].mp4.part-Frag180 has already been downloaded
[download]  97.8% of ~774.51MiB at   91.97MiB/s ETA  Unknown (frag 178/182)[download] C:\yt-dl\WebSite\VIDEO_NAME [1920x1080] [videoID] [formatCode].mp4.part-Frag181 has already been downloaded
[download] Got server HTTP error: HTTP Error 429: Too Many Requests. Retrying fragment 178 (attempt 1 of 999) ...
[download] Got server HTTP error: HTTP Error 429: Too Many Requests. Retrying fragment 182 (attempt 1 of 999) ...
[download] Got server HTTP error: HTTP Error 429: Too Many Requests. Retrying fragment 178 (attempt 2 of 999) ...
[download] Got server HTTP error: HTTP Error 429: Too Many Requests. Retrying fragment 182 (attempt 2 of 999) ...
[download] Got server HTTP error: HTTP Error 429: Too Many Requests. Retrying fragment 178 (attempt 3 of 999) ...

--fragment-retries 0?

Hi pukkandan,
That's certainly an immediate solution - and it isn't often a problem (for me), but imo it doesn't seem like a good idea to allow. The retries are usually beneficial in my experiences, and this is the first case that I'm aware of that I have encountered 429's associated with them.
Blindly retrying against recurring 429's only has the potential to incur more time to be blocked for. I see the issue as being only negative to the user, and only bring frustration and help requests.
This may not directly apply, but I just recently discovered a similar issue the hard-way with a script I wrote to grab codec updates for a media app I use. The first penalization for banging on their server is 30 min, but it would incur additional blocks of 30 min cool downs if I blindly kept retrying. So I added a check to break the retry loop if status code 429 was the response. And granted, if the script and the server are working properly, it's not an issue at all. But, this would be for when things go awry - and you don't want to make it worse than it has to be.
It's just a thought to hopefully help make yt-dlp a more resilient tool.

hm.. I get your point - and this is technically easy to implement. But many sites are known to send inappropriate HTTP codes. I haven't seen any sites sending wrong 429s, but I have seen other codes being misused and am concerned about it. Not retrying on a misused 429 is far more problematic than retrying on a correct 429.
Actually, original implementation of the retry code only did so on specific codes. But it was generalized to retry on all errors because of this issue.


Ionic icons are not showing up in the screen

Ionic version:  (check one with "x")
[ ] 1.x
[X ] 2.x
I'm submitting a ...  (check one with "x")
[X ] bug report
[ ] feature request
[ ] support request => Please do not submit support requests here, use one of these channels: https://forum.ionicframework.com/ or http://ionicworldwide.herokuapp.com/
Current behavior:
I am facing difficulties in showing ion-icon in the screen. The following is the HTML code which I use;
<ion-item>
<button ion-button icon-only clear small color="twitter">
      <ion-icon name="logo-twitter"></ion-icon>
    </button>
            <ion-label color="primary">Title</ion-label>
            <ion-input type="text"></ion-input>
        </ion-item>

For some reasons, ion-icon does not show up in the screen.
Expected behavior:
Use the above snippet in your app to observe the behaviour.

Hello, thanks for using ionic! Unfortunately I cannot seem to reproduce this issue. I made this plunker http://plnkr.co/edit/z0DzVL?p=preview  that demonstrates it working. Could you make a plunker that I can use to reproduce this issue? Thanks!

I have the same problem..i tried this..  https://github.com/driftyco/ionic-preview-app/tree/master/src/pages/cards/image
dont know if I missed something. I am on ionic 2.

Hey @forethoughtde and @nextbigtech , unfortunately i cannot reproduce this issue with either the preview app, the conf app or in that plunker i posted above. Could you guys post a repo i can use to reproduce this issue? Thanks!

Hello all! As it seems it has been a while since there was any activity on this issue i will be closing it for now. Feel free to comment if you are still running into this issue. Thanks for using Ionic!

Still having this issue with ionic v. 3.7.0
This code:
    <ion-col>
      <button ion-button icon-left clear small>
        <ion-icon name="thumbs-up"></ion-icon>
        <div>{{story.numofvotes}} Likes</div>
      </button>
    </ion-col>

generates this (right click->inspect):

Adding class="ion-md-thumbs-up" to the ion-icon tag fixes the issue but I don't think that is the correct way to do it

I am getting the same issue

I found my problem, I was overriding ionicons with this:
* {
  font-family: "my-cool-font" !important;
}

I guess the same issue is in Ionic Creator app viewer too!!!

@suvsah I have the same problem too! The icons are showing fine when I do "ionic serve", but when I build an apk, the icons (everywhere... like tabs and buttons with images) are showing with a small X in a box... Can't get it to work!! :(
If anyone knows which references are missing, please guide us here?

Dears
I have found a solution for this problem when we are adding user defined css class in ionic tag where we are going to show icons at that time the inner class will differ and icons are not show as usual.


Get core client is not typed

if you follow the doc example:
core_client = connection.clients.get_core_client()

the resulting core_client variable gets an Any type from the get_core_client function. This means that you don't get autocomplete on functions available to the core_client
My current work-around:
from typing import Type
from azure.devops.released.core.core_client import CoreClient

core_client: Type[CoreClient] = connection.clients.get_core_client()

Can you fix the return type on the get_core_client function?

This feature should simplify usage of library for new developers.
Pls ;)


Tracker: Accept YAML file as CLI argument

sointu-track could load a yaml file when you specify one as command line argument.

Hey, finally something easy to do :D Yeah, this one's straightforward and makes sense.


mistakes in proofnet.png?

Hi, I just browsed to the front of this repo, and I'm very confused by the example image proofnet.png . Is it meant to be an example of a mistaken proof generated by a bad model? It seems to me that the statement is about a group of size 312 but the proof is about a group of size 351? But also, that proof seems to think that 351/13 is 9 when it's actually 27?
If these errors are intentional, maybe it would be good to frame the image with a bit more context, to avoid bewildering future casual browsers of the repo.

This was indeed a mistake. Thanks for catching it.


IllegalArgumentException thrown when generate CscaMasterList from a ml file.

Dear support,
When the following code used to generate CscaMasterList from a ml file, IllegalArgumentException was thrown
FileInputStream in = new FileInputStream(mlFile);
byte[] byteArr = Streams.readAll(in);
ASN1Primitive asn1 =  ASN1ObjectIdentifier.fromByteArray(byteArr);
CscaMasterList parsedList = CscaMasterList.getInstance(asn1);
The ML file was download from
https://www.bsi.bund.de/SharedDocs/Downloads/DE/BSI/ElekAusweise/CSCA/GermanMasterList.html
Exception stack
java.lang.IllegalArgumentException: illegal object in getInstance: org.bouncycastle.asn1.ASN1ObjectIdentifier
at org.bouncycastle.asn1.ASN1Integer.getInstance(Unknown Source)
at org.bouncycastle.asn1.icao.CscaMasterList.(Unknown Source)
at org.bouncycastle.asn1.icao.CscaMasterList.getInstance(Unknown Source)
Please help check what is wrong.
If something wrong with the masterlist file, would you like share a CscaMasterListcan be used?
Thanks a lot.
Shoutao

It's actually a PKCS#7 signed data file. Try:
    FileInputStream in = new FileInputStream(mlFile);
    byte[] byteArr = Streams.readAll(in);
    ContentInfo contInfo = ContentInfo.getInstance(byteArr);
    SignedData signedData = SignedData.getInstance(contInfo.getContent());
    CscaMasterList parsedList = CscaMasterList.getInstance(
        ASN1OctetString.getInstance(signedData.getContentInfo().getContent()).getOctets());

It works like magic.
Thanks a lot.
Shoutao


Add Control Plane API call to change username and password for basic HTTP authentication

Changed ticket title, please update commit


[style]: The scroll to the top button's index is positioned under the footer.

What's the style idea?
The scroll to the top button's index should be positioned above the footer.
Add screenshots
Add screenshots

Code of Conduct

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

yeah, we need to fix it.
assigned to you

thanks sir

Completed. Thanks for your contributions 🎉 ❤


Use the new mangadex json api to fetch chapters and series.

Adjusted the tests:

the latest releases list moved from the frontpage to /updates
Title of decimal point test changed
1v2 version numbers seem to omit the v2 part everywhere on the site.

Tests pass on my machine:
python3 -m unittest discover -s ./tests/ -p 'test_scraper_mangadex.py'
love-rush 12
  [>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>]  19/19  100%
love-rush 11
  [>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>]  19/19  100%
love-rush 10
  [>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>]  19/19  100%
love-rush 9
  [>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>]  19/19  100%
hedgehog-harry 85
  [>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>]  1/1  100%
...hidamari-sketch 001-013
  [>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>]  150/150  100%
.ramen-daisuki-koizumi-san 18
  [>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>]  8/8  100%
.tomo-chan-wa-onna-no-ko 1
  [>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>]  1/1  100%
....
----------------------------------------------------------------------
Ran 9 tests in 39.328s

fixes https://github.com/Hamuko/cum/issues/63

Wait a second I found an error on one of my follows. I'll figure out what it is and add a test case.

<link rel="icon" type="image/png" sizes="96x96" href="/favicon-96x96.png">
<title>Error 503 - MangaDex</title>

Error 503

Please stop spamming the server!

Maybe we should add a sleep between requests to the mangadex api.
Is there some good spot in the base code for it should I just put a sleep after every request.get?

I don't think there's really any good placement for throttling in the current code, since I don't think we do any kind of throttling at the moment. In the beginning cum wasn't threaded and there wasn't a huge of a need for it. I have thought about making queues per scraper for updating in v1, so you might not be hitting one site with four threads at once.
Having sleep after every request is at least not the most elegant way. However, I don't think there's any good way to track global state in cum at the moment. The best way would be to track globally when a site was last hit by request.get and make sure to sleep appropriately if not enough time has passed. Perhaps some kind of a wrapper for request.get that keeps track of scrapers and last download times.
Any ideas, @CounterPillow?

I tested out adding a random sleep to the request for Series and it's always passing fine for me now.
I have ~30 mangadex follows and ran update 10 times consecutively without running into it. Previously it would almost always occure between updating the 20th and 30th follow.
I only got those spam errors when making many api calls during cum update and not when downloading chapters. The spam block only lasts a very short time, maybe just a few seconds when I rerun update and it gets past my 15 follow on other sites it has always expired.
I added some additional error handling and retry code that didn't trigger yet, but should make it fail more graceful.
The current state of the mangadex scraper is that due to their rewrite of the reader, chapters can't be downloaded at all. So at least the MangadexChapter update should be merged. The MangadexSeries could keep the old slow html pagination scraper, if you are uncomfortable with this shitty workaround.
In the long run @CounterPillow 's suggested design should be implemented, but besides this project I don't have any python experience, so I can't say either what technique should be used to implement it.

I've been using the workaround until now and didn't run into any failures.
A lot of pages link to /title/ instead of /manga/, but the old /manga/ links still work. The api remains unchanged.
Mangadex.com is now no longer redirecting to manga, and used for wordpress blog hosting instead.
I'll be looking into how to make a db-repair update for it.

Alright the db-repair worked with my cum.db. I'll be looking into how to make a test case for it.
I've had a bunch of chapters that had the .org domain already and it caused an unique constraint.
So, I made it so that old chapters/series get deleted instead of updated if there is already a chapter/series with the new url.

Thanks.


Comments in src/Simulation/Simulators/QCTraceSimulator/Circuits/*.qs in XML format

These files have comments in XML-doc format. They should be moved to use Q# doc comments format (Markdown).

Hey there,
I am interested in working on this. Do you have any requirements in terms of all of the inputs being documented, even if they're not in the old docs?
I have started here:
https://github.com/microsoft/qsharp-runtime/compare/master...codingupastorm:master


Crash when a program uses openCL with AMD

Describe the bug
All programs that try to use openCL crash
Steps To Reproduce
Steps to reproduce the behavior:

use this config

  systemd.tmpfiles.rules = [
    "L+ /opt/rocm/hip - - - - ${pkgs.rocmPackages.clr}"
  ];
  # Enable ROCM on my RX 580
  environment = {
    variables = {
      ROC_ENABLE_PRE_VEGA = "1";
    };
    systemPackages = with pkgs; [
      clinfo
    ];
  };
  # Additional hardware configurations
  services.xserver.videoDrivers = ["amdgpu"];
  boot.initrd.kernelModules = ["amdgpu"];
  hardware.opengl = {
    enable = true;
    driSupport = true;
    driSupport32Bit = true;
    extraPackages = with pkgs; [
      rocm-opencl-icd
      rocm-opencl-runtime
    ];
  };

Try to run hashcat

Expected behavior
It works
Screenshots

Additional context
My whole config is here
output from clinfo
❯ clinfo
free(): invalid pointer

Metadata
Please run nix-shell -p nix-info --run "nix-info -m" and paste the result.
 - system: `"x86_64-linux"`
 - host os: `Linux 6.8.5, NixOS, 24.05 (Uakari), 24.05.20240412.cfd6b5f`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.2`
 - nixpkgs: `/etc/nix/path/nixpkgs`

Add a :+1: reaction to issues you find important.

It seems like there is an issue with the ROCM driver for Polaris cards. The problem can be reproduced with version 6.0.2, but not with 5.7.1.
You can test it as follows:
export OCL_ICD_VENDORS=$(nix-build '<nixpkgs>' --no-out-link -A rocmPackages_5.clr.icd)/etc/OpenCL/vendors/

nix-shell -p clinfo

clinfo

So workaround is to use ROCM v5 in your config:
hardware.opengl.extraPackages = with pkgs; [ rocmPackages_5.clr.icd ];

i dont know if it's related but rocmPackages causes GPU hangs and crashes like on the pictures below  every time any application tries to use HIP or OpenCL
rocmPackages_5 works around this

Similar issue here, version 6 resulted in segfault.
Version 5 "works" but anytime I run clinfo or hashcat -I I get screen flickering.
Gpu AMD Radeon RX 570 Series
$ nix-shell -p nix-info --run "nix-info -m"
 - system: `"x86_64-linux"`
 - host os: `Linux 6.6.56, NixOS, 24.05 (Uakari), 24.05.5709.c0b1da36f7c3`
 - multi-user?: `yes`
 - sandbox: `yes`
 - version: `nix-env (Nix) 2.18.8`
 - channels(root): `"nixos-24.05"`
 - nixpkgs: `/nix/var/nix/profiles/per-user/root/channels/nixos`

{ config, lib, pkgs, ... }:

{
  services.xserver.enable = true;
  services.xserver.videoDrivers = ["amdgpu"];
#  boot.initrd.kernelModules = ["amdgpu"];
  hardware.opengl = {

  enable = true;
  driSupport = true;
  driSupport32Bit = true;
  extraPackages = with pkgs; [
    amdvlk
    rocmPackages_5.clr.icd
    rocmPackages_5.clr
    rocmPackages_5.rocm-runtime
  ];
};
  systemd.tmpfiles.rules = [
    "L+    /opt/rocm/hip   -    -    -     -    ${pkgs.rocmPackages_5.clr}"
  ];

  environment.variables = {
  ROC_ENABLE_PRE_VEGA = "1";
};
environment.systemPackages = with pkgs; [
  lact
  amdgpu_top
  rocmPackages_5.rocminfo
  vulkan-tools

];
systemd.packages = with pkgs; [ lact ];
systemd.services.lactd.wantedBy = ["multi-user.target"];

}


Feature/auth

Thanks for accepting my pull request 😒
On Sun, 19 Jun, 2022, 4:55 PM Murari Sabavath, @.***>
wrote:

Merged #1 https://github.com/MurariSabavath/askit/pull/1 into master.
—
Reply to this email directly, view it on GitHub
https://github.com/MurariSabavath/askit/pull/1#event-6834603691, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/ARF3X4WKAHFA3M4I337XAJDVP37R3ANCNFSM5ZGHGWOQ
.
You are receiving this because you authored the thread.Message ID:
@.***>


Deploy website

Deployment check

Highly technical Webhint Error on the part of Github that is beyond owner jurisdiction to repair. It is a general problem students are dealing with please ignore.

Website officially deployed on Github pages.


feat: add logrocket to dependency whitelist

related:
https://github.com/DefinitelyTyped/DefinitelyTyped/pull/36387

This is now in production.


Reset REPL takes very long time

~20 seconds. Are we performing full reconnect?

We restart R process on the broker side.

It is 2 seconds on local so times goes elsewhere

I will make the change recommended by Pavel below. There might be additional changes needed.
@int19h:

Now, one bug that I see here is that it assumes that once QuitAsync completes, hostRunTask is also immediately complete (i.e. that host process exiting will immediately propagate to VS and terminate the main host loop, which is what hostRunTask is). That’s incorrect, and is likely contribute to us moving onto TerminateSessionAsync in many cases where we don’t actually need to do it. The fix would be to issue QuitAsync, but not wait on it – wait only on the hostRunTask, with a timeout. If q() is handled within that timeout, the wait will return early, and we bail out early. If not, we move onto termination.

Another place to improve is to avoid calling testconnection while doing reset. We need a way to let the disconnect handler know that the disconnect was intentional.

I have a fix for that

Closing this task. @AlexanderSher 's fix will address this. Specific tasks should be opened as we discover performance problem.


Build image in dockerized tests with BUILD_ARG

Q
A

Is bugfix?
no

New feature?
yes

Breaks BC?
no

Tests pass?
yes

Will be helpful to pick a PHP version for tests, along with the existing option to pick MySQL and Postgres

Merged. Thanks!


There was an issue while attempting to enable Xbox Live

Hi
I can't enable the app with the Association Wizard.

App Info:

Package/Identity/Name
9023AatlantisStudios.Koteekoo

Package/Identity/Publisher
CN=3EB4758E-A8A4-4A65-B26A-8D1B61D4AD7A

Thanks

Hey @naaturaz,
We've found the issue that's preventing you from enabling using the Association Wizard and we'll work to get it fixed pretty soon.  In the meantime, you should be able to enable your product by heading over to DevCenter and going through the enable flow there.
After that's completed you should be able to re-run the Association Wizard and it will pull down and setup the required configuration that you need.

I am having the same issue. Where and how do I enable the product outside of the association wizard? I've been looking all over my dashboard at developer.windows.com and I am not sure where I do this.

We have resolved an issue that was blocking the enable flow. Please try enabling and then associating again now

The original bug should be fixed now as well.  Be sure to update to https://github.com/Microsoft/xbox-live-unity-plugin/releases/tag/v1707qfe2 or later for the fix.


Something about the GlShader::fromCache();

I'm sorry, I wondering how did the GlShaderCache initialize and where did the sources_ filled with the GLSL have provide？

Please see my answer at https://github.com/jbehley/glow/issues/9#issuecomment-658401197
Just for convenience:

That's a good question and I'm still happy about the solution, even if it is a little bit of magic involved.
First, the cmake command COMPILE_SHADER takes the code in the text file and copies it into a class CacheInitializer (see visualization_shader.cpp or computation_shaders.cpp in the build folder). There the constructor gets an instance of the GlShaderCache and adds the corresponding shader sources from the COMPILE_SHADER macro.
Now comes the magic: the CacheInitializer is used as a static variable: static CacheInitalizer __init__; inside the same cpp file. :tada:
The static variable will be initialized as you define it using the constructor. Thus it will add the shader sources to the cache, et voila. The shaders are added without explicitly calling ever some initialization code!
You just have to now link the cpp into the binary and that's it. Real magic! :tophat: :sparkle:

Please see my answer at jbehley/glow#9 (comment)
Just for convenience:

That's a good question and I'm still happy about the solution, even if it is a little bit of magic involved.
First, the cmake command COMPILE_SHADER takes the code in the text file and copies it into a class CacheInitializer (see visualization_shader.cpp or computation_shaders.cpp in the build folder). There the constructor gets an instance of the GlShaderCache and adds the corresponding shader sources from the COMPILE_SHADER macro.
Now comes the magic: the CacheInitializer is used as a static variable: static CacheInitalizer __init__; inside the same cpp file. 🎉
The static variable will be initialized as you define it using the constructor. Thus it will add the shader sources to the cache, et voila. The shaders are added without explicitly calling ever some initialization code!
You just have to now link the cpp into the binary and that's it. Real magic! 🎩 ❇

Yes! I already find it, thank you very much! SuMa is a really great program!


Replace with header component

What?
Switch out headings to use component gem to improve a11y and adjust visual layouts to match, or closely match, the existing design
Why?
Paying back debt to for heading elements to use component gem - more consistency, improved a11y (changes to the gem will be cascaded across apps)
Trello ticket
Visuals
Before (left)      |      After (right)

Live link #11

Visual change: results numbers are now bold as it's a header
This element is also hidden on mobile intentional PR)

Live link #10

Live link #9

Live link #8

Live link #7

Live link #6

Live link #5

Live link #4

Live link #3

Live link #2
(Mobile only > Filter modal)

Live link #1

Anything else?

There was also a fix to resolve a visual issue found on this page

Before (element outside grid) After (element on right)

⚠ This repo is Continuously Deployed: make sure you follow the guidance ⚠

@injms thank you! Could you do the honours and merge (as an auth user)?


Telescope preview border color same as bg color in dark mode

the border for Telescope previewer  is the same as bg color when let g:gruvbox_flat_style = "dark"
In lua/gruvbox/colors.lua
both colors.bg and colors.border are #282828
with let g:gruvbox_flat_style = "dark"

without let g:gruvbox_flat_style = "dark"

II personally prefer it that way. Maybe I will set it as my personal config and revert it. Thanks for the heads up

This also occurs on LspSagaHoverBorder/AutoPreview border etc. That one feels a lot more clunky when the hover/preview blends into the background.


Malformed HTML when indenting attributes using the tab character

Describe the bug
Sprig renders malformed HTML attributes if you use tab-based indentation on input fields.
To reproduce
Steps to reproduce the behaviour:

Create an empty Sprig component
Add an <input> element, but use linebreaks and tab-based indentation for each property. (This doesn't appear to be an issue if you use space-based indentation).

<input
	class="p-4 text-lg w-full"
	type="search"
	sprig
>

The rendered HTML is malformed:

Expected behaviour
Tab indentation on an element should not cause the rendered HTML to have malformed attributes
Versions

Plugin version: 1.10.4
Craft version: <IP_ADDRESS>

Thanks, fixed in https://github.com/putyourlightson/craft-sprig-core/commit/97983cf4920d4d483be8c54d00c6018d8f42e4b6 for the next release.

Released in Sprig Core version 1.1.6. Running a composer update should install the latest version for you.

Thanks, @bencroker!


Added the Panaromic Camera Angle. Fixes #140

Description
This PR fixes the issue #140 raised by me - Ritankar Saha thereby successfully integrating a new camera angle - Panaromic Camera Angle to the Project.
Fixes:  #140
Type of change

[ x] New feature (non-breaking change which adds functionality)

Checklist:

[ x] I have made this from my own
[x ] I have taken help from some online resourses
[x ] My code follows the style guidelines of this project
[x ] I have performed a self-review of my own code
[ x] I have commented my code, particularly in hard-to-understand areas
[ x] I have made corresponding changes to the documentation
[x ] My changes generate no new warnings

I have fixed the issue #140 opened by me thereby adding a new camera angle - Panaromic Camera Angle to the project and also raised a PR for the same #170

@Dev-tanay  I am sorry but i have rebased the codebase on my desktop with the main branch, rendering it's changes as the PR was 2 weeks old and i thought the repo went dead.
I don't have the codebase on my desktop now owing to it getting rebased with the main branch. I ensure you all the changes are rendered correctly, I have previously worked on this codebase as well fixing 2 issues handling authentication measures. Please review the code, the changes are quite clear and have been commented as well for better understanding.
Thank You.


Migrating away from swig.

Possibly using: https://github.com/Firwood-Software/AdvanceDLSupport
If not, manual PInvoke.

This is coming along good. I much prefer to hand-craft PInvoke. I'm also using shared pointers now as well.
I hope to be done this week.

Alright, everything is back in and working, except for INotifyPropertyChanged.
I'm looking into adding events/signals support, then it will be added on top of it.


Title: Creation of an editing software using Numpy

Is your proposal related to a problem? Please describe.
Yes with normal webcam or camera we can detect different kind of images  like Hsv , negative , gray scale ,detect face and rest all blurred, adding filters etc.

Most of people dont know that we can take thermal images using webcam or camera of laptop with numpy which gives same level of input as a thermal image-capturing device

We can capture live video in thermal, negative, grey etc

The highlight of this project is teaching usage of Python in image creation, manipulation etc

This project will teach how Python can be used to manipulate images and take different forms of images which have quality equivalent to devices used for detecting specific types of images

Add any other context or screenshots about the proposal request here.
No response

Sir in this issue i will create algorithm and core functionalities can u please label3 or 2 sir as it will be helpful for me ,I will be making it from scratch

@Kushal997-das Sir because of some exam issues I was not active project is ready if you open it I will push the code sir

@litesh1123 Submit it ASAP

Ok sir Thank you sir

@Kushal997-das Sir projects is done shall I add this folder to desktop application ?


Protect ourselves from wrong origin repo

When origin is set to the upstream repo we end up pointing to a non
existing repo:
--set main.git.repoURL="https///github.com/hybrid-cloud-patterns/multicloud-gitops.git"
Let's add some code to protect us from this mistake. So when origin
points to the upstream repo and not our own copy:
$ git remote -v
michele git@github.com:mbaldessari/multicloud-gitops.git (fetch)
michele git@github.com:mbaldessari/multicloud-gitops.git (push)
origin  https://github.com/hybrid-cloud-patterns/multicloud-gitops.git (fetch)
origin  https://github.com/hybrid-cloud-patterns/multicloud-gitops.git (push)
We error out sufficiently early:
$ make install
make -f common/Makefile deploy
make[1]: Entering directory '/home/michele/Engineering/cloud-patterns/multicloud-gitops'
ERROR origin points to wrong repo https///github.com/hybrid-cloud-patterns/multicloud-gitops.git
exit 1
make[1]: *** [common/Makefile:43: deploy] Error 1
make[1]: Leaving directory '/home/michele/Engineering/cloud-patterns/multicloud-gitops'
make: *** [Makefile:7: deploy] Error 2

I definitely agree we don't want to proceed if we have the wrong repo.  But maybe there's a git command or something we could run that could test repo accessibility with the current config?  The 3 /'s seems like a very specific kind of error, and if we're looking for typos that code might not catch all of them.
There's an article I found after this PR encouraged me to consider the problem: https://stackoverflow.com/questions/9610131/how-to-check-the-validity-of-a-remote-git-repository-url.  Maybe if we ran git ls-remote on the target repo URL, we could error out if we get a non-zero result.  What do you think?

Agreed on /// being too specific. Sounds like a plan, I'll explore a more simpler approach. Let's hold off on this one for a bit

I still think we're better off running git ls-remote as a validation step.  could it be as straightforward as (untested):
 # Test the charts as the pattern would drive them
        @for t in $(CHARTS); do common/scripts/test.sh $$t normal "$(TEST_OPTS) $(PATTERN_OPTS)"; if [ $$? != 0 ]; then exit 1; fi; done

+validate-origin:
+       git ls-remote $(TARGET_REPO)
+
 init:
        git submodule update --init --recursive

-deploy:
+deploy: validate-origin
        helm install $(NAME) common/install/ $(HELM_OPTS)

-upgrade:
+upgrade: validate-origin
        helm upgrade $(NAME) common/install/ $(HELM_OPTS)

 uninstall:

?

Ack, I'll close this one out for the time being


Add robot type to failed import popup

When importing a program from a different robot type, the following message will occur.

Now it has been changed to show the robot type of the program wanting to be imported.

Note that the robot type is initially the group robot type (ev3, calliope, arduino), and is assumed to be (ev3lejosv1, calliope2017, Nepo4Arduino Uno).

Adapted and merged in 973e9f9.