MvcTranslator being used without php5-intl (HeadTitle::__toString() must not throw an exception)

When using headTitle() view helper in ZF 2.2.1 without php5-intl extension installed, everything works fine. Upgrade to ZF 2.2.2 (still without php5-intl) and we are seeing Method Zend\View\Helper\HeadTitle::__toString() must not throw an exception.
Installing php5-intl solves this problem - but we do not have any sort of internationalisation in our app.
I believe it is change https://github.com/weierophinney/zf2/commit/36b20ff1d11ef898eab7b511a0fa6694a9fe181c#L0L148 that breaks our specific case.
I do not know what the difference in MvcTranslator to translator is, but we have not configured either of these services, but apparently MvcTranslator is a Zend\I18n\Translator\Translator instance. If we do not use translation in our application, we should not be forced to use either Zend\I18n or php5-intl as a dependency.

NOT FIXED.
This exact issue just bit me with versions much later than 2.3.0.  I'm using ZF3, so not sure what versions of what modules are useful to report.  But, exact same symptom, and solved by installing php*-intl.
Is anybody seeing this comment or do I need to open a new issue?

It is fixed, just not in the way you expect.
The issue referenced modified the MVC to define translator interfaces both in zend-i18n and zend-view. zend-mvc then provides an implementation that satisfies each. This allows using a dummy translator if the zend-i18n translator is not configured.
However, the zend-i18n translator requires the intl extension. The package only marks it as a suggestion, as there are other elements of the package that can be used without it. The point is: if you configure the zend-i18n translator, you will need to install the extension. Heed the suggestions when you install packages.

Heed the suggestions when you install packages.

Yes, learning that lesson!  I've read tonnes and have added features to an existing app, but this was my first "from scratch" bring up.
Used $this->form() and got a huge long stack trace.  My fault - I missed the suggestion that I needed zend-i18n.  Figured that out, installed it, missed the suggestion again, and was met with a cryptic and long stack trace which I couldn't make sense of.  Happened upon this thread which led me to install intl (called php-intl in Ubuntu), not ext-intl as suggested by composer.  Not sure if that's correct or an error.
I'm just a newbie and doing my best to read docs and suggestions, but still missing some things obviously.  Just telling my story in case it seems like a good idea for ZF to bark a little clearer about what it's unhappy about, if these two are common occurrences.  Maybe the answer is 'no, just read the suggestions more carefully'.
Love the project, thanks so much for all the time and effort.

which led me to install intl (called php-intl in Ubuntu), not ext-intl as suggested by composer

To hopefully help understand this, php-intl is the chosen package name, the extension is just called intl and Composer chose to express this requirement (or suggestion in this particular case) as ext-intl (the ext- part signifies this is a PHP extension rather than a PHP code library). Installation of PHP extensions varies depending on platform. Ubuntu provides the ability to install this particular extension by installing php-intl, this is probably to avoid naming conflicts with other i18n packages. Other methods could be YUM on RedHat based distros, and the name may or may not be different there, or using PECL (off my head, I'd imagine it'd be pecl install intl) for example (my point is not to recommend an installation method, but to highlight the distinction).


Update instructions to VS 2017

In Visual Studio 2017 the "Add Service Reference" option is gone. You now have to install the Microsoft extension "OData Connected Service" from the VS marketplace and use "Add Connected Service". Please update the instructions, so everyone trying to follow the example don't have to Google this and find this SO issue: https://stackoverflow.com/questions/43981604/how-to-update-odata-wcf-in-visual-studio-2017/48470007

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

ID: 45ab2d51-62c3-fa9a-7a3f-556097ef3c43
Version Independent ID: a93c5d06-2ca9-f8d5-7b49-b69429e7f613
Content: Walkthrough: Creating and Interacting with a Page Web Service (OData) - Dynamics NAV
Content Source: dynamics-nav/Walkthrough--Creating-and-Interacting-with-a-Page-Web-Service--OData-.md
Product: dynamics-nav-2018
GitHub Login: @jswymer

I agree with Soeren. Please update instructions. It will be very useful

Hello, the article has been updated with instructions about using the OData Connected Service. The updated article will be published soon. Thanks for the feedback!


Insert placeholder on failed image load.

Creates a small 100x100 image on load error to indicate failure.

Thanks for the pull request. I actually just completed the placeholder feature. Will be releasing within a few hours.


For a module command how to we pass arguments

protected $name = 'report {version?}';

How do we pass version as an argument here?
"nwidart/laravel-modules": "1.16.0",

Hello,
This isn't related to this package, please refer to the laravel documentation.


Indirect modification of properties causes no effect

As per today's testing, I found that GO-AOP-PHP proxies are quite weak on magic property access.
Specifically, consider following class:
<?php

class Foo
{
    private $bar = [];
}

$foo = new Foo;
$foo->bar['baz'] = 'tab';

Defining a property access interceptor for this property will likely cause an output like:
Notice: Indirect modification of overloaded property Foo::$bar has no effect in /in/lLa8o on line 14

This is because the generated code looks like:
<?php

class Foo
{
    private $bar = [];

    public function __get($name)
    {
        return $this->bar;
    }
}

$foo = new Foo;
$foo->bar['baz'] = 'tab';

The problem is that __get is not defined by reference.
I'm taking a ProxyManager generated proxy as a reference implementation (mainly because I tested a lot of aspects of it): https://gist.github.com/Ocramius/55cd7f709c91674add33
What does this mean for the API?

& $generated#__get
& Go\Aop\Framework\ClassFieldAccess#__invoke()
& Go\Aop\Framework\ClassFieldAccess#proceed()

In general, this needs quite extensive unit testing, specifically on the following operations:

getting a property
setting a property
isset-checking a property
unsetting a property
getting a property array key
setting a property array key
isset-checking a property array key
unsetting a property array key

Some tests to take as a reference implementation: https://github.com/Ocramius/ProxyManager/blob/7badedb5f8afaaccd496a096daadb19d7bf2b374/tests/ProxyManagerTest/Functional/LazyLoadingGhostFunctionalTest.php#L224-L285

Thanks, @Ocramius, this is known issue #54, actually it isn't fully baked now like in your ProxyManager. I have never seen before the real use-cases for intercepting property access, because it's very rare case ) Your check is real first one that requires an interceptions of properties.
My proxy is very limited indeed (no __isset, __unset, no reference passing), so a lot of thing to do and test.
So can I just your library to generate a proxy with my method body? This can be slower, but will more reliable and extendable.

As it currently stands, the problem is that ProxyManager uses runtime reflection, which is not compatible with how GO-AOP-PHP works (runtime code generation).
@asgrim is working on https://github.com/Roave/BetterReflection, which is a "cold" reflector (doesn't autoload classes, and would fit this particular use-case).
Another approach (for now) is using a separate process for the codegen.

Implemented in #281, property interceptors work by reference now.


[BUG]: CSI PowerStore unable to resize NVMe block PVC, even though volume on the array get's resized

Bug Description
Resizing a  NVMe block volume volume does not work. The volume on the array is actually increased to 2 GB but the PVC still at 1GB.
The driver node pods have below error:

{"level":"info","msg":"/csi.v1.Node/NodeExpandVolume: REP 0045: rpc error: code = NotFound desc = No raw block devices found","time":"2024-10-17T08:58:52.30687537Z"}

Logs
{"level":"debug","msg":"mpath checkcommand values is lsblk --pairs --output NAME,MAJ:MIN,RM,SIZE,RO,TYPE,MOUNTPOINT | awk '/mpath.+csivol-af258affea/ {print $0}
'","time":"2024-10-17T08:58:52.290993379Z"}
{"level":"debug","msg":"multipath exec command output is : ","time":"2024-10-17T08:58:52.29788002Z"}
{"level":"debug","msg":"command value is lsblk --pairs --output NAME,MAJ:MIN,RM,SIZE,RO,TYPE,MOUNTPOINT | awk '/csivol-af258affea/ {print $0}
'","time":"2024-10-17T08:58:52.29790798Z"}
{"level":"debug","msg":"command output is : ","time":"2024-10-17T08:58:52.306792719Z"}
{"level":"info","msg":" Block volume expansion. Will try to perform a rescan...","time":"2024-10-17T08:58:52.306806959Z"} {"level":"info","msg":"getSysBlockDevicesForVolumeWWN 10 0.000029","time":"2024-10-17T08:58:52.306845979Z"} {"level":"error","msg":"No raw block devices found","time":"2024-10-17T08:58:52.3068505Z"} {"level":"info","msg":"/csi.v1.Node/NodeExpandVolume: REP 0045: rpc error: code = NotFound desc = No raw block devices found","time":"2024-10-17T08:58:52.30687537Z"}
Screenshots
No response
Additional Environment Information
No response
Steps to Reproduce

Create NVMe block PVC
Create POD that consumes the PVC
Resize the PVC

Expected Behavior
The PVC should be resized
CSM Driver(s)
CSM PowerStore
Installation Type
HELM
Container Storage Modules Enabled
CSM 1.11.1
Container Orchestrator
N/A
Operating System
N/A

link: 29249


Add subject to CreateStreamGroupRequest

This adds the additional field subjectto the CreateStreamGroupRequest.
This request is currently used internally to persist additional stream group (Jetstream Consumer) metadata through the ArunaServer. As the subject of a stream group shall also be stored in the database, it has to be provided with the request since e.g. an Object could exist in multiple collections. So it would have to be guessed with which Collection the subject would be generated.
This PR resolves #69.

PR won't update after subsequent push to dev. For safety reasons, this PR will be closed and a new one will be opened.


luaPackages.busted-htest: init at 1.0.0-1

Description of changes

Needed for luarocks development.
cc @teto
Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
24.11 Release Notes (or backporting 23.11 and 24.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

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

5 packages built:

lua51Packages.busted-htest
lua52Packages.busted-htest
lua53Packages.busted-htest
lua54Packages.busted-htest
luajitPackages.busted-htest

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

5 packages built:

lua51Packages.busted-htest
luaPackages.busted-htest (lua52Packages.busted-htest)
lua53Packages.busted-htest
lua54Packages.busted-htest
luajitPackages.busted-htest


Use the official cassandra driver

Hi,
I created a patch for cql-rb for running under ruby 2.0.0 and it was rejected saying that cql-rb is no longer supported, and that cequel should use the official datastax/ruby-driver driver.
https://github.com/iconara/cql-rb/pull/125
I don't have a minimal code to reproduce the issue, but basically starting from ruby 2.2.0 if you sort objects by Cql::TimeUuid class (key or foreign_key) and some of this objects are nil, it will raise some warnings:
../gems/cequel-1.5.0/lib/cequel/record/dirty.rb:59: warning: Comparable#== will no more rescue exceptions of #<=> in the next release.
../gems/cequel-1.5.0/lib/cequel/record/dirty.rb:59: warning: Return nil in #<=> if the comparison is inappropriate or avoid such comparison.

Starting from ruby 2.3 I believe this will transform automatically in errors.

An issue #153 is already created for the same. And a private branch with some progress is at @outoftime /cequel. Not sure of the ETA. May be this can be duped.

FYI all—the private branch is in pretty good shape, but a few specs in the data_set_spec that fail nondeterministically for reasons that aren't clear but might be a bug in the CQL driver. I'm hoping to put together a reduction fairly soon to confirm that it's a driver issue, but that's what's blocking it right now.
If anyone else who's highly motivated wants to take a look at that branch / the spec failures, that certainly wouldn't be unwelcome ; )


fix: Fixed failing to find headers when linked with Pods.

Summary:
Multiple people have reported that RNCAsyncStorage fails to build after #35. See https://github.com/react-native-community/react-native-async-storage/pull/35#issuecomment-482604705, #73, and #74.
After a little discussion, we agreed to rename the .podspec and the name of the Pod to be more in line with Apple's naming guidelines and the rest of the community. Unfortunately, this means that the next upgrade will break.
I got a little impatient knowing that I broke the latest release so I went ahead and implemented the fix. Sorry if you've already started looking at this.
Test Plan:
I used https://github.com/timmywil/react-native-async-storage-1.3.1, kindly provided by @timmywil, for testing.
Migration Plan:
Even though react-native link will be able to link the new .podspec, it won't clean up existing entries. Please find your Podfile, and make the following changes:
- pod 'react-native-async-storage', :path => '../node_modules/@react-native-community/async-storage'
+ pod 'RNCAsyncStorage', :path => '../node_modules/@react-native-community/async-storage'

cc @Krizzu @stigi @dblazeski

That was quick @tido64
Gave this a test try - it fixes the pods issue. Tried with:

Replace
pod 'react-native-async-storage', :path => '../node_modules/@react-native-community/async-storage
with
pod 'RNCAsyncStorage', :path => '../node_modules/@react-native-community/async-storage'
yarn add @react-native-community/async-storage@https://github.com/tido64/react-native-async-storage\#tido/fix-pods
cd ios && pod update

Build worked.

Good work! You should also update docs/Linking.md.

Thanks @tido64 and everybody, that was quick!

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[Cache: Suggestion] Partial/Segmented caching

Hi, I do not know if this is the best place to place feature suggestions and probably will be making a fool of myself but I just thought this could be a good feature to have. So I am slightly new to Laravel and I am currently doing a project (Laravel 4.2) that I wanted to cache the view for better performance on the site.
However I had this part of the view that had to be random stories which totally messed up the idea of caching.
Initially I though of creating a partial for the area that was not dynamic and the do something like:

public function show($storyId)
{
    $story = Api::get('stories/'.$storyId); // An API we built
    $storyContent = Cache::remember('story_content_'.$storyId, 60*24*7, function() use($storyId) {
        return View::make('stories.storyContent', [ 'story' => $story ])->render();
    });
    ...
    return View::make('stories.show', [ 'storyContent' => $storyContent, 'relatedStories' => $relatedStories]);
}

Now this was a bit convoluted and not as beautiful looking as the rest of Laravel. I would prefer something like this in a view:

@cache('story_content_'.$story->id, 60)
    // HTML here
@endcache

Also having the capability to work with tags too would be amazing. I was told that some other frameworks have similar things like in Django and Ruby on Rails, but I know that as of now this does not yet work out of the box in Laravel. It would be a nice to have. Thanks for the time and sorry once again if I posted this suggestion in the wrong place.

There are laravel packages out there that can do this for you. :)

@GrahamCampbell Hi I tried to have a look and the ones that I found are extremely old which I doubt that they are maintained anymore. Unless you know of any I did not manage then please do share as that would be helpful.
However on the other hand this is indeed something that could be considered to be made part of Laravel by default. Cmon I cannot be the only one thinking that this is very helpful for so many situations and projects instead of having to add yet another package when we could use something native. Like I said other frameworks which Laravel has some inspiration from have this kind of thing in them by default.


Implement BatchInsert

I think BatchInsert implementation is like BatchUpdate implementation but is little easy.
// Copy OrderItems from fromOrder to toOrder
var items = fromOrder.Items();
items.BatchInsert(i => new OrderItem { OrderId = toOrder.Id, ItemName == i.ItemName, ItemCount == i.ItemCount});

Hello @AlexRadch ,
Thank you for your suggestion.
BatchInsert is already in our todo list. Unfortunately, for the next few months, we will focus for our free support to improve some stuff on our side such as: Making .NET Fiddle compatible with Entity Framework to allow to create online examples and re-working our core to better handle all providers.
We will soon provide a roadmap.
Best Regards,
Jonathan

We would love the BatchInsert feature too!

Thank you for the reminder.
We will start to look at it to add it on https://entityframework-classic.net/
Once it's stable, we will try to import the feature in EF Plus as well.
Best Regards,
Jonathan


Feature Request : Lexer for Unity based c#, Javascript, boo scripts?

Hi,
I see some variants on lexer languages, so maybe there is a place for a Unity variant of c# javascripts and boo in snip Lexer?
https://unity3d.com/showcase
https://unity3d.com/learn/tutorials/modules/beginner/scripting/scripts-as-behaviour-components
https://unity3d.com/learn/tutorials/modules/beginner/scripting/c-sharp-vs-javascript-syntax
Basically, it's based on .NET20 with a very distinct api to work within Unity and create interactive 3d content, games obviously, but not just :)
I searched the snipts and found few examples, some of them in javascripts ( c# being the most used anyway)
https://snipt.net/search/?q=unity
https://snipt.net/fahied/using-accelerometer-in-unity-3d/
File extensions as .cs .js and .boo. I think mime types are regular.
Bye,
Jean

Hi Jean! We use Pygments, so if you write a new lexer for Pygments, it'll be added to Snipt in an update :)
Here's some info on writing new lexers: http://pygments.org/docs/lexerdevelopment/


Revise documentation on managing dependencies.

Minor update for guidelines on managing Python dependencies to better reflect when various options should be used.

R: @rszper

Thank you!


fixed a stream isClosed error on lobs Test.

Codecov Report

Merging #223 into dev will decrease coverage by 0.05%.
The diff coverage is n/a.

@@             Coverage Diff              @@
##                dev     #223      +/-   ##
============================================
- Coverage     32.91%   32.86%   -0.06%
- Complexity     1437     1439       +2
============================================
  Files            97       97
  Lines         23385    23385
  Branches       3889     3889
============================================
- Hits           7697     7685      -12
- Misses        14140    14158      +18
+ Partials       1548     1542       -6

Flag
Coverage Δ
Complexity Δ

#JDBC41
32.77% <ø> (+0.05%)
1436 <ø> (+7)
:arrow_up:

#JDBC42
32.74% <ø> (-0.09%)
1432 <ø> (-3)

Impacted Files
Coverage Δ
Complexity Δ

...om/microsoft/sqlserver/jdbc/SimpleInputStream.java
38.23% <0%> (-1.48%)
9% <0%> (-1%)

...in/java/com/microsoft/sqlserver/jdbc/IOBuffer.java
36.41% <0%> (-0.45%)
0% <0%> (ø)

...om/microsoft/sqlserver/jdbc/SQLServerBulkCopy.java
45.16% <0%> (+0.07%)
183% <0%> (+1%)
:arrow_up:

src/main/java/microsoft/sql/DateTimeOffset.java
40% <0%> (+2.85%)
10% <0%> (+2%)
:arrow_up:

Continue to review full report at Codecov.

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


HUM-666 preallocate temp files in hec

Call Preallocate() on shards.
Preallocating space for files reduces fragmentation and lets us
reject requests early when the drive is full.

LGTM 👍


Allow Carn/Herbivore to affect meals.

During play I trend towards less nutritious, singular objects since my bonuses don't apply to meals. Fix that. See if you can add tags to them on creation?

[23-06-23 00:12:34.262] LOG  : General     ,<PHONE_NUMBER>262> ERROR: Missing translation "Vegetable and Bacon Roast".
[23-06-23 00:12:40.729] LOG  : General     ,<PHONE_NUMBER>729> ERROR: Missing translation "Vegetable, Bacon and Chicken Roast".
[23-06-23 00:20:52.996] LOG  : General     ,<PHONE_NUMBER>996> Item| BaseHunger: -0.3199999928474426, ThirstChange: -0.012500000186264515, BoredomChange: 0, UnhappyChange: -15, Calories: 250.5.
[23-06-23 00:20:52.997] LOG  : General     ,<PHONE_NUMBER>997> After Eat, Before Mod| Hunger: 0.18554046750068665, Thirst: 0, Boredom: 36.791561126708984, Unhappiness: 0, Calories:730.8775024414062.
[23-06-23 00:20:52.997] LOG  : General     ,<PHONE_NUMBER>997> After Mod| Hunger: 0.025540471076965332, Thirst: -0.0062500000931322575, Boredom: 36.791561126708984, Unhappiness: -7.5, Calories:605.6275024414062.
[23-06-23 00:20:52.998] LOG  : General     ,<PHONE_NUMBER>998> Food Poisoning neutralized..


Do not reset license on Windows 2008R2

If product_key='default_kms_key', the license on Windows 2008 R2
should not be reset, otherwise the dowloads will fail to install
because Windows will not find a valid license.
Added better logs for Windows and PowerShell version.

:white_check_mark: Build windows-openstack-imaging-tools 1.0.225 completed (commit https://github.com/cloudbase/windows-openstack-imaging-tools/commit/5db7778a21 by @ader1990)

:white_check_mark: Build windows-openstack-imaging-tools 1.0.226 completed (commit https://github.com/cloudbase/windows-openstack-imaging-tools/commit/f34be4a92c by @ader1990)


Chore/DAEF-423 Removal of the Client API

NOTE: This PR is based on #448 so please review and merge that before!
This PR is the first step to the removal of the purescript daedalus-client-api and replacement with a flow-typed JS version. The notify websocket logic has been replaced by simple polling of /api/settings/sync/progress in the network store and the makePayment endpoint has been replaced by a POST request to /api/txs/payments/{from}/{to}/{amount}.
These are two important examples that highlight any interaction we need with the backend api (polling a GET endpoint and POSTing query/path params).

@darko-mijic @nikolaglumac @tomothespian the PR is ready for review! Please take a careful look at the new way to implement the api!

@darko-mijic @nikolaglumac PR is ready for review again.

This PR also fixes:
https://issues.serokell.io/issue/DAEF-460

Something is wrong with the reviewer list. I can not add myself there.
This is a beautiful simplification of the cumbersome logic we had with the Notify API.
Love the new Request API! Brilliant work as always @DominikGuzei :)

@darko-mijic you and @DominikGuzei can not be added as reviewers since you were assigned to this task ;)


Quickstart documentation

missing '#include ' which is required for members of Fish, Cat, Dog, etc.

Do you mean #include <string>? I can't say "first, let's include the library" and include <string> too, and it would feel like making the reader lose its time to specify "hey, don't forget to #include <string>".

When I went through the example in the docs it was just a bit awkward when I was trying to reproduce the code in my own file by copy-paste. I got a compilation error and then realized I needed some more includes. I imagine most people going through the quick start in that way will run into the issue.
Also, related to this is that "using namespace boost::hana::literals" isn't in the documentation but is required for compilation of part of the examples. I ran into that as well and actually didn't figure out how to fix it until I looked into quickstart.cpp directly.

Fixed. The tutorial will be updated when I push to master, after the review. Thanks for the report.


Commits.ListCommits() always returns Response.TotalItems = 0

Can you replicate the problem with cURL? Or can you use cURL to check the results when making the same API call directly?

It seems the header x-total is missing
x-next-page: 2
x-page: 1
x-per-page: 1
x-prev-page:

In the API response you mean? If so, this seems a but in the GitLab API. If not, can you replicate the problem with cURL and paste the output?

The HTTP-header from the API-response. I used httpie for testing, so it looks different from cURL
The entire output looks like this
http GET 'https://gitlab.com/api/v4/projects/<id>/repository/commits?per_page=1&page=2' PRIVATE_TOKEN:<your-token-here>
HTTP/1.1 200 OK
CF-Cache-Status: MISS
CF-RAY: 84d9972b183b453a-TXL
Connection: keep-alive
Content-Encoding: br
Content-Type: application/json
Date: Tue, 30 Jan 2024 12:06:43 GMT
NEL: {"success_fraction":0.01,"report_to":"cf-nel","max_age":604800}
Report-To: {"endpoints":[{"url":"https:\/\/a.nel.cloudflare.com\/report\/v3?s=%2FgXUyOtRmXvc%2BxZ3mygv0G%2BdEDc6WTX2HSm61VfU6QKo899GnVKTu%2F9PZzC%2BPSgUYuz8taaeN8tWlq%2FnhEiA3ZaOfHEh%2BE7amfFsiRpdKVNqb3AJQnkItG0ANE4%3D"}],"group":"cf-nel","max_age":604800}
Server: cloudflare
Set-Cookie: _cfuvid=sGSy2U7msmg.gnWm6GW7QS9BfnY3j24R.n_3Q6GFXCI-1706616403918-0-604800000; path=/; domain=.gitlab.com; HttpOnly; Secure; SameSite=None
Transfer-Encoding: chunked
cache-control: max-age=0, private, must-revalidate
content-security-policy: default-src 'none'
etag: W/"24d2924ba231f8e8a5d5e8ccf59e8adc"
gitlab-lb: haproxy-main-03-lb-gprd
gitlab-sv: localhost
link: <https://gitlab.com/api/v4/projects/42506673/repository/commits?id=<id>&order=default&page=1&per_page=1&trailers=false>; rel="prev", <https://gitlab.com/api/v4/projects/42506673/repository/commits?id=<id>&order=default&page=3&per_page=1&trailers=false>; rel="next", <https://gitlab.com/api/v4/projects/42506673/repository/commits?id=<id>&order=default&page=1&per_page=1&trailers=false>; rel="first", <https://gitlab.com/api/v4/projects/42506673/repository/commits?id=<id>&order=default&page=3&per_page=1&trailers=false>; rel="last"
ratelimit-limit: 2000
ratelimit-observed: 2
ratelimit-remaining: 1998
ratelimit-reset:<PHONE_NUMBER>
ratelimit-resettime: Tue, 30 Jan 2024 12:07:43 GMT
referrer-policy: strict-origin-when-cross-origin
strict-transport-security: max-age=31536000
vary: Origin, Accept-Encoding
x-content-type-options: nosniff
x-frame-options: SAMEORIGIN
x-gitlab-meta: {"correlation_id":"59dc496c6a113d9a528443e36980173a","version":"1"}
x-next-page: 3
x-page: 2
x-per-page: 1
x-prev-page: 1
x-request-id: 59dc496c6a113d9a528443e36980173a
x-runtime: 0.077426

[
    {
        ....
    }
]

Thanks! So it looks like an issue/bug with the GitLab API. In that case I will close this issue as I cannot fix it in this package. I suggest to open an issue with GitLab in order to get this one resolved.

@svanharmelen
I believe this is not a bug from the GitLab side however, it was intentional:
https://gitlab.com/gitlab-org/gitlab/-/merge_requests/43159
https://gitlab.com/gitlab-org/gitlab/-/issues/389582
It seems like the x-total is returned only if the repo has less than 100 commits, and therefore, it fits into a single page.


warehouse: Don't supply icon_url to WebAuthn

We were previously supplying this with the base domain,
which was neither an image nor (necessarily) a secure context.
Fixes #6343

cc @ewdurbin @di @dstufft


Explicit devirtualize of GetOverloadFactor

GetOverloadFactor() called from loop inside TCompactionLogic cause noticeable virtual call overhead.

before:

after:


In TLS1.3, the client provides the ”psk_dhe_ke“ mode. When the server selects the ”psk_ke“ mode, the alert description is not "illegal_parameter"

openssl version:3.0.9
according to rfc8446

Clients MUST verify that the server's selected_identity is within the
range supplied by the client, that the server selected a cipher suite
indicating a Hash associated with the PSK, and that a server
"key_share" extension is present if required by the ClientHello
"psk_key_exchange_modes" extension.  If these values are not
consistent, the client MUST abort the handshake with an
"illegal_parameter" alert.

The client sends the psk_dhe_ke mode. Then the server hello was received without the "key_share" extension, and the "missing_extension" alert was sent in extensions.c:final_key_share
    if (!s->server
            && !sent
            && (!s->hit
                || (s->ext.psk_kex_mode & TLSEXT_KEX_MODE_FLAG_KE) == 0)) {
        /* Nothing left we can do - just fail */
        SSLfatal(s, SSL_AD_MISSING_EXTENSION, SSL_R_NO_SUITABLE_KEY_SHARE);
        return 0;
    }

Fix in #25059


Lutece 2211

Add an option to DAOUtil to allow to not log some SQL queries (like queries containing passwords)

Your PR seems to contain an unrelated commit (3686c37)
For LUTECE-2211 : why would a query contain a password in the query text instead of it being passed as a parameter ? Since adopting your proposed change necessitate code change at the calling site, why not fix the calling site instead to pass the password as a parameter ?


bioimageio.core.test_model passes but GitHub CI fails

Expected behaviour: if local test passes, then GitHub Actions should encounter no error.
My test:

GitHub Actions: https://github.com/bioimage-io/collection/actions/runs/9515502505/job/26230316192

The issue is that the conda environment that you have locally and that the CI is running with are not the same.
As discussed offline you can try to specify a different (higher) PyTorch version to have CI run in a more up-to-date environment where torch can be imported successfully (which is the issue in the current default pytorch env the CI installs for the pytorch version you specified).
Or, for pytorch state dict weights anyways, add a custom dependencies file. (I'd prefer the first option as your usecase should not require a custom conda env.
The ideal solution is to improve the default conda environment used in CI for the pytorch version that you specified (which would fix all models specifying that pytorch version 🎉 ).
This environment is determined here


Refactor calendar day styles

Description
Make calendar and date-range picker calendar (partially) day styles rely on the attributes rather than additional class names. That reduces complexity as in some cases the styles can reuse the existing attributes (aria-current, aria-disabled, tab-index) and also allows for the easier reuse of styles between the two calendar implementation as it becomes possible to extract the calendar-day as a mixin w/o the need to support the additional classes.
The refactoring is done as a step towards reusing calendar and date-range picker calendar styles and updating the components to use the table layout.
How has this been tested?
Manual testing, visual regression tests.
Documentation changes
[Do the changes include any API documentation changes?]

[ ] Yes, this change contains documentation changes.
[x] No.

Related Links
[Attach any related links/pull request for this change]

Review checklist
The following items are to be evaluated by the author(s) and the reviewer(s).
Correctness

[ ] Changes are backward-compatible if not indicated, see CONTRIBUTING.md.
[ ] Changes do not include unsupported browser features, see CONTRIBUTING.md.
[ ] Changes were manually tested for accessibility, see accessibility guidelines.

Security

[ ] If the code handles URLs: all URLs are validated through the checkSafeUrl function.

Testing

[ ] Changes are covered with new/existing unit tests?
[ ] Changes are covered with new/existing integration tests?

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

These changes don't quite match our usual philosophy around styling and CSS. Using data- attributes for styles means that we are losing style encapsulation and protection against overrides. I think this warrants a bigger discussion before moving forward.

Thanks for the call out, I'll bring this topic to the team discussion then.


[Feature Request] Show Stat requirements for skill setup

Considering that it is possible to setup up your skill gems being able to see the stat requirements that those skill bring with them would be really helpful for planning the build, as you could see if you should get some more stat from the tree or how hard you have to invest into stats on gear

It's on the TODO list. The program doesn't yet have the data for skill gem stat requirements, and it doesn't seem to be in the game files, so I have to figure that out first.

It's been a long time coming, but the next update finally adds level and attribute requirement displays for gems and items.


Reduce Query Count from Settings

Calls to Settings options cause a query per each item requested.
On an average page, there are 10+ queries just to fetch data from the Settings table:
select * from `canvas_settings` where `setting_name` = 'blog_title' limit 1

As the Settings table is currently relative small (< 20 lines), it may be beneficial to grab all rows, and store them in an array in the Settings model as a form of caching.
Long term, this should possibly be stored in Redis (but that makes installation less simple due to more services), or another request-persistent in-memory cache mechanism, etc.

[x] Prevent repeat queries (calls to retrieve the Blog Title multiple times, should only use one query)
[x] Prevent superfluous queries by pulling in all of the Settings data

I'll work on the two points above, suggestions welcome.

Closed by #158.


feat(Frame): implement frame.content and frame.setContent methods

This refactors the page.content and page.setContent methods to be defined on the Frame class. This allows access from the Page still but also on all frames.
Fixes #754

I've updated the tests. Let me know if any other changes are needed.


fix: keys split into 2 strings, which allows # in fullName

What does this PR do?
allow # in fullNames for components
What issues does this PR fix or reference?
#, @@
@W-5185915@
Functionality Before
For a component with # in its name (see example on the WI), SDR would call string.split('#') and get confused.  When trying to pull, it wouldn't be able to find matching metadata
Functionality After
finds metadata (has to split into two strings on the first instance of the delimiter)

let's hope there's never a metadata type with # in it

Custom#Labels


Create a way to be able to link to the latest API docs

Just had a situation in the Lighthouse docs where I wanted to link to a specific section of the Puppeteer API reference docs.
The problem with the current setup is that it links me to a specific version of the API docs.
For example: https://github.com/GoogleChrome/puppeteer/blob/v1.6.0/docs/api.md#pagecoverage
Note the v1.6.0 part of the URL. Ideally, we'd have some kind of alias to the latest docs, so that my links are always up-to-date.

Oh right, just remembered about master. Replacing the version part with master links to tip-of-tree.
Ideally, we'd have a way to link the latest release, but this is probably good enough.

@kaycebasques https://pptr.dev is also quite handy for links.

That is nice. Forgot that you shipped that site. Thanks.


ThunderHub

@abhiShandy
Here's a first draft of a ThunderHub page. Too early to have any feel for if its too little, too much, or just right.
Critique and suggestions are welcome.

I'm closing this one, as some unrelated files seem to have found their way into my branch.
Re-do to follow.


Dynamic HTML form elements

I need to create an HTML form dynamically with Pebble.
The idea is that I have a generic entity that contains a list with parameters. Each parameter has a name and a type (integer, date, float, ...).
I want to generate a form for editing entity. For each parameter type I want to insert a different HTML input component.
Do anyone do that?

You could set up a separate template for each field type, and then dynamically include a template for each field.
Reference

You can also take a look at the spring petclinic example here

I wrote a from-lib that does exactly this.
Here are examples for pebble templates: (don't be fooled by the extension .twig. It's actually pebble!)
https://github.com/jochen777/jWebformExample/tree/master/src/main/resources/templates/jwebform/common
And here is the lib:
https://github.com/jochen777/jWebForm


Days of the previous month should be displayed

Maybe in gray

That's actually per the spec:
https://www.google.com/design/spec/components/pickers.html#pickers-date-pickers
It was in gray, and the spec doesn't mandate it...I can go either way.  You prefer gray?

Oh I see... it just looks weird to not have the days of the past/next month visible to fill the entire grid... Usualy the calendars look like that

agreed, but the visibility: none on this is actually causing #10.  I can implement either way.

So I checked two places:

google calendar web - it shows past/next month's days
google calendar android - it does not show past/next month's days

The Android mobile seems more material, so I'm inclined to keep these as not visible.  I did however adjust the stylesheet for those that want it.
In the case someone wants to show past/future, they can just override .old and .new and provide visibility: visible.


Image component does not load image from specific URI on iOS

Description
The Image component does not render an image on iOS when loaded from a specific URI
React Native version:
System:
OS: macOS 10.15.4
CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz
Memory: 234.47 MB / 16.00 GB
Shell: 5.7.1 - /bin/zsh
Binaries:
Node: 10.20.0 - ~/.nvm/versions/node/v10.20.0/bin/node
Yarn: 1.22.4 - /usr/local/bin/yarn
npm: 6.14.4 - ~/.nvm/versions/node/v10.20.0/bin/npm
Watchman: Not Found
SDKs:
iOS SDK:
Platforms: iOS 13.5, DriverKit 19.0, macOS 10.15, tvOS 13.4, watchOS 6.2
Android SDK: Not Found
IDEs:
Android Studio: Not Found
Xcode: 11.5/11E608c - /usr/bin/xcodebuild
Languages:
Java: 14.0.1 - /usr/bin/javac
Python: 2.7.16 - /usr/bin/python
npmPackages:
@react-native-community/cli: Not Found
react: 16.9.0 => 16.9.0
react-native: 0.62.2 => 0.62.2
npmGlobalPackages:
react-native: Not Found
Steps To Reproduce
See code snippet below
Expected Results
I would expect the code below to render an image on screen. It does do that on Android, but not on iOS. If i go to that link in a browser or curl it from the terminal it renders or downloads as expected. But React Native on iOS does not render it.
Snack, code example, screenshot, or link to a repository:
<Image style={{height: 100, width: 100}} source={{ uri: 'https://api.openpay.mx/barcode/185017437691737?width=1&height=100' }} />

See example here: https://snack.expo.io/QH4nUBfc6

I'm seeing this issue too. Are you running IOS 14 beta?

@ryanpag3 No, I'm running iOS 13.5

Can confirm. I have the same problem on iOS 14.

All images not loading for me on iOS 14 beta

Same, uri or local images not working. I have Xcode 12, iOS 14.

iOS 13.5.1 + XCode 11.5 works fine here.

Yep, same here. It only started occurring recently, so I think it must be from some dependency RN pulls in.

This is most likely coming from iOS SDK 14, which comes with XCode 12. Should probably stay away from XCode 12 for a few months for production builds.

I disagree. Even using the release SDK and toolchain still causes this on my end.

I disagree. Even using the release SDK and toolchain still causes this on my end.

Hey @SConaway, could you post the output you're getting from executing xcodebuild -showsdks in the terminal?

@rdperottoni The issue is reproducible on the snack emulator linked in the original post. I highly doubt that is using pre-release SDKs.

Sure thing.
With the production XCode selected (images don't work):
$ xcodebuild -showsdks
iOS SDKs:
	iOS 13.5                      	-sdk iphoneos13.5

iOS Simulator SDKs:
	Simulator - iOS 13.5          	-sdk iphonesimulator13.5

macOS SDKs:
	DriverKit 19.0                	-sdk driverkit.macosx19.0
	macOS 10.15                   	-sdk macosx10.15

tvOS SDKs:
	tvOS 13.4                     	-sdk appletvos13.4

tvOS Simulator SDKs:
	Simulator - tvOS 13.4         	-sdk appletvsimulator13.4

watchOS SDKs:
	watchOS 6.2                   	-sdk watchos6.2

watchOS Simulator SDKs:
	Simulator - watchOS 6.2       	-sdk watchsimulator6.2

With the beta XCode (images don't work):
$ xcodebuild -showsdks
iOS SDKs:
	iOS 14.0                      	-sdk iphoneos14.0

iOS Simulator SDKs:
	Simulator - iOS 14.0          	-sdk iphonesimulator14.0

macOS SDKs:
	DriverKit 20.0                	-sdk driverkit.macosx20.0
	macOS 10.16                   	-sdk macosx10.16

tvOS SDKs:
	tvOS 14.0                     	-sdk appletvos14.0

tvOS Simulator SDKs:
	Simulator - tvOS 14.0         	-sdk appletvsimulator14.0

watchOS SDKs:
	watchOS 7.0                   	-sdk watchos7.0

watchOS Simulator SDKs:
	Simulator - watchOS 7.0       	-sdk watchsimulator7.0

Again, as @rmacqueen, @ryanpag3 and @DennisdeWitNL said, it occurs with the production XCode and iOS 13.x.
In the example snack, however, my phone successfully loads the local and base64 images, but not the remote one. I'm able to access it in Chrome on my computer and iPhone Safari, so there's an issue there as well.
Clearing my DerivedData seems to have resolved this issue on both SDK versions. Give that a shot. Sorry for the slow response time @rdperottoni, I am a dual-core i5 MBP that builds slowly.

@SConaway What was your technique for clearing your DerivedData? I deleted my project folder @ ~/Library/Developer/Xcode/DerivedData/ and it did not fix the issue for me.

All images not loading for me on iOS 14 beta

See https://github.com/SDWebImage/SDWebImage/pull/3043/commits/bb7b1914e6091a04feae858ad2fb85aa37ecd87d

All images not loading for me on iOS 14 beta

See SDWebImage/SDWebImage@bb7b191

How do we integrate this fix with React Native? Where does React Native keep the SDWebImage library?

I'm also experiencing this issue, but only on iOS 14.
Images are working/loading just fine on iOS 13.x, but as soon as the same app is put on iOS 14 images are not displaying (neither local or remote).

That's odd. Building with the 13.5 SDK results in working images. Can anyone test building with the 14 SDK and using an iOS 13 (or before) iPhone?

That's odd. Building with the 13.5 SDK results in working images. Can anyone test building with the 14 SDK and using an iOS 13 (or before) iPhone?

@SConaway I just switched over to iOS 14 SDK and am running on a 13.5 iPhone 11 Simulator:

➜  ~ xcodebuild -showsdks
iOS SDKs:
	iOS 14.0                      	-sdk iphoneos14.0

iOS Simulator SDKs:
	Simulator - iOS 14.0          	-sdk iphonesimulator14.0

macOS SDKs:
	DriverKit 20.0                	-sdk driverkit.macosx20.0
	macOS 10.16                   	-sdk macosx10.16

tvOS SDKs:
	tvOS 14.0                     	-sdk appletvos14.0

tvOS Simulator SDKs:
	Simulator - tvOS 14.0         	-sdk appletvsimulator14.0

watchOS SDKs:
	watchOS 7.0                   	-sdk watchos7.0

watchOS Simulator SDKs:
	Simulator - watchOS 7.0       	-sdk watchsimulator7.0

When running in 13.5 simulator all images show as intended. You can see a video of it running in iOS 13.5 here.
when running in 14.0 simulator with iOS 14.0 SDK none of the images display. You can see a video of that here.

So, interesting discovery --
I rebuilt the application on another Mac that was using Catalina. Rebuilt with the most recent prod-ready Xcode version and the application built successfully and images are displaying (even in iOS 14.0).
So it looks like iOS 14 itself isn't the issue.

So, interesting discovery --
I rebuilt the application on another Mac that was using Catalina. Rebuilt with the most recent prod-ready Xcode version and the application built successfully and images are displaying (even in iOS 14.0).
So it looks like iOS 14 itself isn't the issue.

I built the app with iOS 13 SDK and even on iOS 14 the images show perfectly fine. I built the app on Big Sur. The problem either is Xcode 12 or iOS 14 SDK.

So, interesting discovery --
I rebuilt the application on another Mac that was using Catalina. Rebuilt with the most recent prod-ready Xcode version and the application built successfully and images are displaying (even in iOS 14.0).
So it looks like iOS 14 itself isn't the issue.

I built the app with iOS 13 SDK and even on iOS 14 the images show perfectly fine. I built the app on Big Sur. The problem either is Xcode 12 or iOS 14 SDK.

That's what I'm thinking as well. Initially, I thought it was an iOS 14 issue, but that wouldn't have made sense anyway since other apps were loading images just fine.

The snack linked in original post does not work on iOS device running iOS 13.4.1

RN 0.62.2, iOS 13.5.1 and xcode 11.5 here, working perfectly. But I'm facing issues on local images, only on Android.

@DennisdeWitNL use patch-package and my patch file (work with rn 0.63)
react-native+0.63.0.patch
diff --git a/node_modules/react-native/Libraries/Image/RCTUIImageViewAnimated.m b/node_modules/react-native/Libraries/Image/RCTUIImageViewAnimated.m
index 21f1a06..2444713 100644
--- a/node_modules/react-native/Libraries/Image/RCTUIImageViewAnimated.m
+++ b/node_modules/react-native/Libraries/Image/RCTUIImageViewAnimated.m
@@ -272,6 +272,9 @@ - (void)displayDidRefresh:(CADisplayLink *)displayLink

 - (void)displayLayer:(CALayer *)layer
 {
+  if (!_currentFrame) {
+    _currentFrame = self.image;
+  }
   if (_currentFrame) {
     layer.contentsScale = self.animatedImageScale;
     layer.contents = (__bridge id)_currentFrame.CGImage;
diff --git a/node_modules/react-native/scripts/.packager.env b/node_modules/react-native/scripts/.packager.env
new file mode 100644
index 0000000..361f5fb
--- /dev/null
+++ b/node_modules/react-native/scripts/.packager.env
@@ -0,0 +1 @@
+export RCT_METRO_PORT=8081

@DennisdeWitNL use patch-package and my patch file (work with rn 0.63)
react-native+0.63.0.patch
diff --git a/node_modules/react-native/Libraries/Image/RCTUIImageViewAnimated.m b/node_modules/react-native/Libraries/Image/RCTUIImageViewAnimated.m
index 21f1a06..2444713 100644
--- a/node_modules/react-native/Libraries/Image/RCTUIImageViewAnimated.m
+++ b/node_modules/react-native/Libraries/Image/RCTUIImageViewAnimated.m
@@ -272,6 +272,9 @@ - (void)displayDidRefresh:(CADisplayLink *)displayLink

 - (void)displayLayer:(CALayer *)layer
 {
+  if (!_currentFrame) {
+    _currentFrame = self.image;
+  }
   if (_currentFrame) {
     layer.contentsScale = self.animatedImageScale;
     layer.contents = (__bridge id)_currentFrame.CGImage;
diff --git a/node_modules/react-native/scripts/.packager.env b/node_modules/react-native/scripts/.packager.env
new file mode 100644
index 0000000..361f5fb
--- /dev/null
+++ b/node_modules/react-native/scripts/.packager.env
@@ -0,0 +1 @@
+export RCT_METRO_PORT=8081

I can confirm this worked! Thank you!
For those who don't know how this works:
npm i -g patch-package
Make a new folder called packaged
Make a new file called react-native+0.63.0.patch
Add the source code above.
patch-package
enter

npm i -g patch-package

where do you make the new folder?

I made a folder called patches at the root of the project and it worked.
However; with the patch, the images show up but they do  not update (size, etc) - They are just stuck.

@abiespinal04 You make a new folder called ‘patches’ right in your React Native project folder.
@joewired This is strange. I applied the patch too, and I have multiple images with a width and height of 50 pixels, just as I programmed. And I also have a screen width filling Image Background, which is working fine too. I don’t have this problem.

I can confirm that @DennisdeWitNL's fix https://github.com/facebook/react-native/issues/29215#issuecomment-657231577 also works for React Native 0.61.2, using Xcode 12 beta 3, iOS 14 simulator.

is it a good idea to use this patch? any possible negative side effects?
How long are we expected to need this patch? do I need to manually delete it later when the issue is fixed?

@DennisdeWitNL's solution worked for me, although I made a few small adjustments.

Install packages locally
yarn patch-package postinstall-postinstall
include new script in package.json that will run this after you invoke yarn install (or equivalent)

    "postinstall": "patch-package"

These steps were found in the patch-package README.

My problem was with both local and uri images.
I was able to fix the issue by applying the suggested patch. I confirm that works well with previous RN versions:

RN: 0.62.2
Xcode: 12.0
iOS simulator: 14

Same problem with local & remote not showing images.
The fix is the patch https://github.com/facebook/react-native/issues/29215#issuecomment-657231577
This patch does work on older RN versions.
Reach Native: 0.61.2
Xcode: 12.0
iOS Sim: 14

Worked for me with:
React Native: 0.61.5
Xcode: 12.0
I did the same as @ryanpag3 with one small tweak for step 1:
yarn add patch-package postinstall-postinstall

Error: Patch file found for package  react-native which is not present at node_modules/ react-native

I came across this same issue too yesterday after an OS update. Lost a few hours trying to figure out the problem. Updating to the latest version of react-native fixed it for me, it looks like it contains the fix.

@eowino you mean version 0.63.2?

@Dror-Bar Yes, 0.63.2.

#import "RCTUIImageViewAnimated+WLAdd.h"
#import <objc/runtime.h>
@implementation RCTUIImageViewAnimated (WLAdd)
+(void)load {
static dispatch_once_t onceToken;
dispatch_once(&onceToken, ^{
Method fromMethod = class_getInstanceMethod([self class], @selector(displayLayer:));
Method toMethod = class_getInstanceMethod([self class], @selector(wl_displayLayer:));
method_exchangeImplementations(fromMethod, toMethod);
});
}

(void)wl_displayLayer:(CALayer *)layer {
UIImage *currentFrame = [self valueForKey:@"currentFrame"];
CGFloat animatedImageScale = [[self valueForKey:@"animatedImageScale"] floatValue];
if (currentFrame) {
layer.contentsScale = animatedImageScale;
layer.contents = (__bridge id)currentFrame.CGImage;
} else {
[super displayLayer:layer];
}
}

@end

`#import "RCTUIImageViewAnimated+WLAdd.h"
#import <objc/runtime.h>
@implementation RCTUIImageViewAnimated (WLAdd)
+(void)load {
static dispatch_once_t onceToken;
dispatch_once(&onceToken, ^{
Method fromMethod = class_getInstanceMethod([self class], @selector(displayLayer:));
Method toMethod = class_getInstanceMethod([self class], @selector(wl_displayLayer:));
method_exchangeImplementations(fromMethod, toMethod);
});
}

(void)wl_displayLayer:(CALayer *)layer {
UIImage *currentFrame = [self valueForKey:@"currentFrame"];
CGFloat animatedImageScale = [[self valueForKey:@"animatedImageScale"] floatValue];
if (currentFrame) {
layer.contentsScale = animatedImageScale;
layer.contents = (__bridge id)currentFrame.CGImage;
} else {
[super displayLayer:layer];
}
}

@end`

`#import "RCTUIImageViewAnimated+WLAdd.h"
#import <objc/runtime.h>
@implementation RCTUIImageViewAnimated (WLAdd)
+(void)load {
static dispatch_once_t onceToken;
dispatch_once(&onceToken, ^{
Method fromMethod = class_getInstanceMethod([self class], @selector(displayLayer:));
Method toMethod = class_getInstanceMethod([self class], @selector(wl_displayLayer:));
method_exchangeImplementations(fromMethod, toMethod);
});
}

(void)wl_displayLayer:(CALayer *)layer {
UIImage *currentFrame = [self valueForKey:@"currentFrame"];
CGFloat animatedImageScale = [[self valueForKey:@"animatedImageScale"] floatValue];
if (currentFrame) {
layer.contentsScale = animatedImageScale;
layer.contents = (__bridge id)currentFrame.CGImage;
} else {
[super displayLayer:layer];
}
}

@end`

#import "RCTUIImageViewAnimated+WLAdd.h"
#import <objc/runtime.h>

@implementation RCTUIImageViewAnimated (WLAdd)

+(void)load {
  static dispatch_once_t onceToken;
  dispatch_once(&onceToken, ^{
    Method fromMethod = class_getInstanceMethod([self class], @selector(displayLayer:));
    Method toMethod = class_getInstanceMethod([self class], @selector(wl_displayLayer:));
    method_exchangeImplementations(fromMethod, toMethod);
  });
}

- (void)wl_displayLayer:(CALayer *)layer {
  UIImage *currentFrame = [self valueForKey:@"currentFrame"];
  CGFloat animatedImageScale = [[self valueForKey:@"animatedImageScale"] floatValue];
  if (currentFrame) {
      layer.contentsScale = animatedImageScale;
      layer.contents = (__bridge id)currentFrame.CGImage;
    } else {
      [super displayLayer:layer];
    }
}

@end

try and test...
🤷♀🤷♀🤷♀
Op vr 18 sep. 2020 02:44 schreef shoopi12<EMAIL_ADDRESS>
is it a good idea to use this patch? any possible negative side effects?
How long are we expected to need this patch? do I need to manually delete
it later when the issue is fixed?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/facebook/react-native/issues/29215#issuecomment-694578321,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQE6HXBIZRK5TYDBR763ULDSGKUQVANCNFSM4OHK6ZLA
.

For those running older versions of React Native (e.g., 0.60.6) the patch is not possible since the RCTUIImageViewAnimated.m file doesn't exist. I solved this problem by using React Native Fast Image v8.1.5 and upgrading SDWebImage pod with pod update SDWebImage. More specifically, I upgraded SDWebImage from v5.8.1 to v5.9.2.

If any one is still facing the problem here are stepwise solution which worked for me :-

Navigate to node_modules>>react-native>>Libraries>>image
Open RCTUIImageViewAnimated.m in your fav. editor
Replace the following code
if (_currentFrame) {  layer.contentsScale = self.animatedImageScale;  layer.contents = (__bridge id)_currentFrame.CGImage; }
with
if (_currentFrame) {  layer.contentsScale = self.animatedImageScale;  layer.contents = (__bridge id)_currentFrame.CGImage; }else {  [super displayLayer:layer]; }
Save the file
Close the packager if already running
ReLaunch the application (npx/ yarn ios)

@VisheshNucleusTeq the issue with editing a node_modules library directly is that after reinstalling with npm install for example, all of those edits are lost. This is a sure way to get very hard to find bugs later on.

@Dror-Bar
this is a temp solution this won't be need with the upcoming update
creating the post install script must be kept as first way  but if that doesn't work then this is sure shot solution

3. if (_currentFrame) { layer.contentsScale = self.animatedImageScale; layer.contents = (__bridge id)_currentFrame.CGImage;   }else { [super displayLayer:layer];   }

this patch worked

If any one is still facing the problem here are stepwise solution which worked for me :-

Navigate to node_modules>>react-native>>Libraries>>image
Open RCTUIImageViewAnimated.m in your fav. editor
Replace the following code
if (_currentFrame) { layer.contentsScale = self.animatedImageScale; layer.contents = (__bridge id)_currentFrame.CGImage;   }
with
if (_currentFrame) { layer.contentsScale = self.animatedImageScale; layer.contents = (__bridge id)_currentFrame.CGImage;   }else { [super displayLayer:layer];   }
Save the file
Close the packager if already running
ReLaunch the application (npx/ yarn ios)

this worked like butter

I am still not able to see any images with the iOs 14.2 update. I have implemented:

npm install --save react-native-fix-image
react-native+0.63.0.patch
manually within node_modules

Is anyone else seeing these solutions not working for them?
I am on:
react-native-cli: 2.0.1
react-native: 0.61.4
Managed Expo:
Expo CLI 3.28.2 environment info:
System:
OS: macOS 10.15.4
Shell: 3.2.57 - /bin/bash
Binaries:
Node: 15.0.1 - /usr/local/bin/node
Yarn: 1.22.10 - /usr/local/bin/yarn
npm: 7.0.3 - /usr/local/bin/npm
Watchman: 4.9.0 - /usr/local/bin/watchman
SDKs:
iOS SDK:
Platforms: iOS 13.1, DriverKit 19.0, macOS 10.15, tvOS 13.0, watchOS 6.0
IDEs:
Xcode: 11.1/11A1027 - /usr/bin/xcodebuild
npmPackages:
expo: ^37.0.12 => 37.0.12
react: 16.9.0 => 16.9.0
react-dom: 16.9.0 => 16.9.0
react-native: https://github.com/expo/react-native/archive/sdk-37.0.1.tar.gz => 0.61.4
react-native-web: ^0.11.7 => 0.11.7
react-navigation: ^3.13.0 => 3.13.0
npmGlobalPackages:
expo-cli: 3.28.2
Expo Workflow: managed

Finally fixed this by downgrading react-native from 0.63.3 to 0.63.0. Then applied the patch using the postinstall npm script.
Also, remember to set a width and height on the image style as it could be loading but just not displaying properly - this threw me off for a bit during testing.

If any one is still facing the problem here are stepwise solution which worked for me :-

Navigate to node_modules>>react-native>>Libraries>>image
Open RCTUIImageViewAnimated.m in your fav. editor
Replace the following code
if (_currentFrame) { layer.contentsScale = self.animatedImageScale; layer.contents = (__bridge id)_currentFrame.CGImage;   }
with
if (_currentFrame) { layer.contentsScale = self.animatedImageScale; layer.contents = (__bridge id)_currentFrame.CGImage;   }else { [super displayLayer:layer];   }
Save the file
Close the packager if already running
ReLaunch the application (npx/ yarn ios)

Worked like a charm!

@VisheshNucleusTeq  thank you. It is really help me

As mentioned above, this issue appears to be a duplicate of #29279. The issue is fixed in v0.63.2 (with https://github.com/facebook/react-native/commit/b6ded7261544c703e82e8dbfa442dad4b201d428) and the upcoming v0.64 (with https://github.com/facebook/react-native/commit/123423c2a9258c9af25ca9bffe1f10c42a176bf3).
It'd be good for someone who's able to do so to mark this issue as closed.

As mentioned above, this issue appears to be a duplicate of #29279. The issue is fixed in v0.63.2 (with https://github.com/facebook/react-native/commit/b6ded7261544c703e82e8dbfa442dad4b201d428) and the upcoming v0.64 (with https://github.com/facebook/react-native/commit/123423c2a9258c9af25ca9bffe1f10c42a176bf3).
It'd be good for someone who's able to do so to mark this issue as closed.

I using 0.63.4 and cli 2.0.1.
It's still continue this issue.
I'm using this link http://placehold.it/32x32
simulator 14.3

I using 0.63.4 and cli 2.0.1.
It's still continue this issue.
I'm using this link http://placehold.it/32x32
simulator 14.3

I am using RN 0.61.5 and Xcode 11.1, I am still getting this issue, but only when I try to make a Release build. Adding the else to node_modules/react-native/Libraries/Image/RCTUIImageViewAnimated.m only worked for Debug buids.
Could this also be an issue with a Pods library? I am getting [framework] CUICatalog: Invalid asset name supplied: '(null)' on Xcode's logs

I am using RN 0.61.5 and Xcode 11.1, I am still getting this issue, but only when I try to make a Release build. Adding the else to node_modules/react-native/Libraries/Image/RCTUIImageViewAnimated.m only worked for Debug buids.
Could this also be an issue with a Pods library? I am getting [framework] CUICatalog: Invalid asset name supplied: '(null)' on Xcode's logs

I solved this by using react-native-fast-image

I solved this by using react-native-fast-image

Any dev want to patch-package step by step doc to solve image issue checkout below link
https://infinitbility.com/image-not-showing-in-ios-14-react-native

Any dev want to patch-package step by step doc to solve image issue checkout below link
https://infinitbility.com/image-not-showing-in-ios-14-react-native

Any dev want to patch-package step by step doc to solve image issue checkout below link
https://infinitbility.com/image-not-showing-in-ios-14-react-native

I'm having this issue with my app on an actual device with the release build (images from URI only). However, on the simulator it works perfectly fine. Would this fix also work for this scenario?
Thanks

Any dev want to patch-package step by step doc to solve image issue checkout below link
https://infinitbility.com/image-not-showing-in-ios-14-react-native

I'm having this issue with my app on an actual device with the release build (images from URI only). However, on the simulator it works perfectly fine. Would this fix also work for this scenario?
Thanks

URI (from cache or web) image won't load either on physical device ios 14.4
using:

react-native: 4.14.0
expo: 4.1.6
node: 14.15.4

Any dev want to patch-package step by step doc to solve image issue checkout below link
https://infinitbility.com/image-not-showing-in-ios-14-react-native

I'm having this issue with my app on an actual device with the release build (images from URI only). However, on the simulator it works perfectly fine. Would this fix also work for this scenario?
Thanks

I'm having the same issue. Works fine on simulator. When I release it to TestFlight, it does not show remote images.

Hi everyone, face this issue today, Xcode 12, and iOS 14.3, tried the patch. without success,
So in the end of the url, that was using 'http', I replaced for 'https' and it worked:
.replace('http','https')
In my case my urls are http.

I might be in the wrong place, but I am using my android device and when I try to view the screen in my browser I can see the login screen with image file fine, but when I scan the qr code to my phone, the console is telling me that  the image file does not exist.  I am wondering if this is similar to this issues.


Compatibility Changes for React Native 0.69.2+ (SDK46)

This will likely address the issues in #18 and #19.
Context: In React Native 0.69.2, the way flipper was added to the build for iOS was changed in a backward incompatible way. Previously, flipper was invoked with a use_flipper invocation in the Podfile. The upgrade helper shows that the file changed significantly at the 0.69.2 release of react native

Flipper is now invoked as an argument to use_react_native and the old use_flipper is removed
The post_install step is no longer required

The result is inconsistent builds on iOS, where the iOS build will fail while Android succeeds. Forcing old versions of flipper has limited success, but isn't a good long term solution.
How to Test This Change

Check out this PR somewhere locally
Copy the /plugin/build folder into your expo app
Change the plugin to match the new syntax (no need to specify a Flipper version anymore)

{
  "expo": {
    "..."
    "plugins": [
      "./path/to/build/withFlipper.js"
    ]
  }
}

You can then run expo prebuild and verify the new Podfile changes.

A expo-community-flipper-isprod tag that tells use_react_native if the production ENV value was set
A expo-community-flipper-urn tag that tells use_react_native to enable/disable flipper based on the FLIPPER_DISABLE environment variable

It’s probably not required, but I would take chances after the breaking
patch change. I’ll update the readme in the pr to reflect this. I also need
to dive into the use_react_native podfile and see how the production arg is
used.
On Tue, Aug 23 2022 at 7:51 PM, rlam3 @.***> wrote:

@.**** commented on this pull request.
In plugin/src/withFlipper.ios.ts
https://github.com/jakobo/expo-community-flipper/pull/20#discussion_r953272488
:

IOS_URN_ARG_ANCHOR,
+} from "./constants";
+import { FlipperConfig } from "./types";
+import path from "path";
+import fs from "fs";

+/** Create a namepaced tag /
+const tag = (s: string) => ${EXPO_FLIPPER_TAG}-${s};
+
+/* Return the flipper enabling line for use inside of use_react_native */
+const createFlipperArgument = (version?: string) => {

const active = version
? FlipperConfiguration.enabled(["Debug"], { 'Flipper' => '${version}' }),
: FlipperConfiguration.enabled,;
const inactive = FlipperConfiguration.disabled;
return :flipper_configuration => ENV['FLIPPER_DISABLE'] ? ${inactive} : ${active};

So in addition to FLIPPER_DISABLE=1 I'd have to ensure that in our expo
build pipeline that PRODUCTION=1 is also set as an environment variable?
—
Reply to this email directly, view it on GitHub
https://github.com/jakobo/expo-community-flipper/pull/20#discussion_r953272488,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAAAOA2QLOAEBQBYTG5UC63V2WEZRANCNFSM57KRCS4Q
.
You are receiving this because you authored the thread.Message ID:
@.***>

@jakobo
From experimenting with eas builds via expo. It seems like if we set FLIPPER_DISABLE=1 as a secret in expo.dev, this environment variable will show up for your build environment in the Spin up build environment  section like the following:
Environment secrets:
  FLIPPER_DISABLE=****

I was able to verify that flipper was not installed via the "Install Pods" section of the expo build pipeline and I was able to download the successful build and install it via iOS simulator to verify that Flipper desktop app was not able to connect the app itself.
I think we can merge this PR!

The final piece I'd like to tackle now is how to separate FLIPPER_DISABLE=1 in prod and staging but FLIPPER_DISABLE=0 in local and development.

This should do it:
"production": {
      "extends": "base",
      "distribution": "store",
      "releaseChannel": "stable",
      "android": {
        "buildType": "app-bundle"
      },
      "env": {
        "FLIPPER_DISABLE": "true"
      }
   }

@Slapbox thank you! is it "true" or is it supposed to be "1" ?

I think either should work, just be sure to wrap the value in quotes.

I think either should work, just be sure to wrap the value in quotes.

Set it to "1" to disable it in your production profile. Leave it unset for development/testing profiles.
"production": {
  "extends": "base",
  "distribution": "store",
  "releaseChannel": "stable",
  "android": {
    "buildType": "app-bundle"
  },
  "env": {
    "FLIPPER_DISABLE": "1"
  }
}


Document tabIndex

and other like props :)

Is there a way to generate stubs for props like these on View in Windows so that we can go and add documentation?

The properties are defined in flow so I believe it is possible.


Can Apple reject the App Store upload for using rc version of Alamofire?

What did you do?
ℹ I am using Alamofire & AlamofireObjectMapper in a project with Swift version 5.0 & Deployment Target iOS 11.0. After 'pod install' AlamofireObjectMapper v6.2.0 got downloaded along with Alamofire v5.0.0-rc.2 and ObjectMapper v3.5.1. My question is can Apple reject the App Store upload for using rc version of Alamofire?
Alamofire Environment
**Alamofire version: 5.0.0-rc.2
**Xcode version: 11.3.1
**Swift version: 5.0
**Platform(s) running Alamofire: iOS 11 onwards (iPhone/iPad)
**macOS version running Xcode: 10.15.4

Apple can reject your uploads for any reason, but prerelease framework versions aren't usually one of them. Their only restriction on shipping apps built with prerelease versions is their own SDKs.


'onRewarded' and 'onRewardedVideoCompleted' events not fired on iOS

Describe the bug
when implement 'Rewarded Ad', its working fine on android. on iOS the ad itself appeared without problems but 'onRewarded' and 'onRewardedVideoCompleted' events are not fired after video is completed and 'Rewarded' word appear on the ad itself.
another thing, when I check 'definitions.d.ts' file I found 2 definitions of  'onRewarded'
   addListener(eventName: 'onRewarded', listenerFunc: (adMobRewardItem: AdMobRewardItem) => void): PluginListenerHandle;
   addListener(eventName: 'onRewarded', listenerFunc: (info: any) => void): PluginListenerHandle;

To Reproduce
Steps to reproduce the behavior:

call 'prepareRewardVideoAd'
call

AdMob.addListener('onRewarded', (info: { type: string, coin: number }) => {
    console.log('onRewarded YESSSSS');
});

call

AdMob.addListener('onRewardedVideoCompleted', (info: { type: string, coin: number }) => {
    console.log('onRewardedVideoCompleted YESSSSS');
});

call 'showRewardVideoAd.
the 'onRewarded' event will never fired

Expected behavior
'onRewarded' and 'onRewardedVideoCompleted' events should be fired after video is completed and rewarded on iOS
Smartphone:

Device: iPhone8 plus
OS: iOS 14.4

Any resolution for this issue?


after created a new admin user got Error 419 Page expired

Version information

Laravel: v6.2
Voyager: v1.14
PHP: 7.3.12
Database:  MySQL 8.0.18

Description

I installed in my project Voyager with dummy and it worked fine,
later i created a new admin user by commande php artisan voyager:admin<EMAIL_ADDRESS>--create
it worked the first day but the next day i've got Error 419 | Page expired.
How can I fix this error ?
thanx for help

419 means usually you have a problem with sessions, if refreshing doesn't work check that your session folder is writable.
Anyway it's not related to Voyager which BTW never had a v1.14, maybe v1.4.1?

thanks for your reply!
yes I was wrong with the version of Voyager, it's 1.4.2
I created another new admin and it still works, then the folder is working?..
but I noticed that the remember_token isn't generated in the database
maybe there is a reason?

have same issue, after update to 1.4.2 few days ago, can't login until now. Keep redirecting to 419. Still keep debugging but still have clue ???

Hi, Stark,
I've update my project on server and the error has disappeared.
I don't understand what its reasons are...
I hope this helps you!
Le sam. 5 sept. 2020 à 13:49, Stark Liew<EMAIL_ADDRESS>a
écrit :

have same issue, after update to 1.4.2 few days ago, can't login until
now. Keep redirecting to 419. Still keep debugging but still have clue ???
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/the-control-group/voyager/issues/5063#issuecomment-687598571,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/ACLJQBVQY4BZSYHU4I6KQR3SEIQWDANCNFSM4QR4OAAA
.


[Open source] Search optimization of Exchangis1.0 task library table.

Search before asking

[x] I had searched in the issues and found no similar feature requirement.

Problem Description
Search optimization of Exchangis1.0 task library table.
Description
When selecting a library table, you need to have a search box, otherwise there are too many library tables to find the desired library table; At the same time, it is necessary to add a covered loading box when loading library table information.
一选择库表的时候，需要有一个搜索框，不然库表太多很难找到想要的库表；同时，加载库表信息还是要加个遮盖的加载框

Use case
No response
solutions
No response
Anything else
No response

[x] Are you willing to submit a PR?

Yes I am willing to submit a PR!

#282 The bug has been resolved


RequestIdleCallback Scheduler

This was previously discussed @ https://github.com/ReactiveX/rxjs/issues/1870 -- It would be nice to have a scheduler that used RequestIdleCallback to process work.  While most browsers are supported, there's probably a remaining question of what to do if it's not supported by the browser (run immediately? fallback to RequestAnimationFrame? "setTimeout-based" polyfill?)
This would be super useful.

The concern on whether to polyfill should be up to the consumer IMO, if the consumer does not use this scheduler, it should be tree shaken out & not polyfilled.

I've put my thoughts on this into a blog post: https://ncjamieson.com/how-to-use-requestidlecallback/
Mostly because several other people have asked me about this recently.

Great article!
I was actually using something similar to an idle observable and had a passing thought a scheduler may have been better (admittedly, the ergonomics of using the RAF scheduler are quite nice).  The article actually explains it quite nicely and at least confirms my current path forward ;D Awesome.

@cartant thanks for the article. I use a home made operator to change the execution context today, instead of a scheduler. I still think having an official blurb in the docs would be great, to make sure these great thoughts from your blog get more visibility.
Regarding the "experimental" nature of it, couldn't it just be in a separate package, still living under this namespace, officially maintained, and referenced from the official docs?
Even if we don't provide the official implementation, I think it should be called out. Omitting it makes RxJs seem outdated for new users who may be approaching it. They may falsely conclude from it's omission that RxJs is not able to meet their needs.

Regarding the "experimental" nature of it, couldn't it just be in a separate package, still living under this namespace, officially maintained, and referenced from the official docs?

All of that takes time - which is limited - and doesn't include the time that would be spent explaining the situation in issues that would surely be opened on an ongoing basis. I see no point in 'officially' supporting an experimental API that has been discussed for something like 4 years - IIRC - and is still not in Safari and iOS Safari.

Right now the consumers of RxJs are paying the time each time to figure this out for themselves & re-implement it in every project over & over. I was hoping we could at least add a blurb in the docs that explains how to make the operator yourself & explains why it belongs as an operator instead of a scheduler. This blurb could contrast operators with schedulers like you've done in your excellent blog post.
My idea with providing an implementation in addition to docs would just require initial time commitment to create an official "extras"  repo. I'd bet there are volunteers willing to help maintain it & field any issues, including me, and I see you already have an "extras" repo, perhaps it could go there & be linked to from the official docs?
The tradeoff is fragmentation of the ecosystem, where users of RxJs have to write a bunch of third party libraries, which makes it harder to get going as a user. The other tradeoff is people will post issues like these if it is not added, or users will still be confused, they may just wrongly assume RxJs does not allow for using requestIdleCallback, I would personally rather help answer possible issues & clarify the docs vs potentially having a smaller community because of small barriers to entry like lack of support for some newer browser APIs. Ideally IMO if its not added here under this namespace, its added to a popular "extras" library like your awesome rx-etc package, to minimize the number of new packages a user of Rx must deal with to get basic tasks done.
I also quite frankly don't see why Safari matters, if people chose to pull in the optional package that houses this operator, the burden on them to polyfill or not would be on them.  My intent is to lower the barrier to entry so people don't have to independently discover the concepts themselves.
I think having a stand alone package that implements this operator, would be great, too. Ideally it lives under the official namespace, or is linked to from the official docs, so that users do not have to stop their task at hand & go search through a dozen slightly different community implementations.


mouse related macros are invalid

In version 1.0.0, mouse related macros are invalid，But the version published on the nexus website is normal

Please give an example. It did not support mouse macto from the very beginning actually...

I described several actual situations I encountered, let's take switching equipment as an example. When I tried to double wield a right handed weapon, my macro should be set to "interactive button+left mouse button (i.e. attack button)". However, the latest version 1.0.0 and the version on the Nexus website did not successfully complete this action. When I bound the attack button to a keyboard button, the 1.0.0 version still cannot complete this action, But the version on the nexus website can.

This project is so cool, I want to Chineseize this interface, but only datesheets.py has been completed so far.I found some amulets missing


[Feature Request] Uncss Google Font Imports

I'm making font utility library and was wondering if uncss supports, or would be interested in supporting, uncssing google font imports.  That way superfly-css-utilities-fonts can import all google fonts during compile time / prototyping relying on uncss to remove once that will not be used.
This is a code snippet containing utility construction:
@import url('https://fonts.googleapis.com/css?family=Open+Sans:100,400,900');
...
.u-font-open-sans {
  font-family: "Open Sans", var(--font-family-helvetica-neue) !important;
}

@oleersoy This has been somewhat covered in https://github.com/giakki/uncss/issues/258.
The conclusion was that uncss shouldn't mess with font-face declarations. Even if there are no CSS rules that use the font, the font is still usable, because it can be referenced from a style property directly. https://github.com/giakki/uncss/issues/258#issuecomment-250952792
For your use-case, you could probably run uncss as a postcss plugin, using https://github.com/ben-eb/postcss-discard-unused later in the plugin chain.
Hope this explains things clearly for you.

Hi @RyanZim
I created a separate superfly-css-task-deploy that can be run once prototyping with superfly-css-task-build is complete.
Ideally developers would be able perform their work like this in the prototyping stage:

Some condensed and italicized looking roboto text</

Some expanded looking opens sans text

400 weighted normal opens sans text

....

The above could be done without having to import fonts because the superfly-css-utilities-fonts module takes care of all the compile time imports.
So within the scope of the the superfly-css framework being able to remove all unused @font-face declarations that are not tied to a corresponding utility declaration would be really helpful, because the designer should never apply an imported font without using a utility.
I can see how it might not be desirable in the generic case though.  If there's any way I can "plug into" uncss to get this working I would definitely appreciate a heads up.

Not sure what would be the best approach here.
One way would be to use uncss as a postcss plugin https://github.com/giakki/uncss#as-a-postcss-plugin and then write a custom postcss plugin to strip unneeded google font imports.
Another approach would be to consider using something like https://github.com/jonathantneal/postcss-font-magician. Just something to consider.

Hmmm thanks for pointing that out!  https://github.com/jonathantneal/postcss-font-magician might be the perfect thing.  If it works the way that it looks like it works I could create all the font utilities and just leave the importing to the magician.
All the task I've written (build, deploy) use postcss BTW.
Just curious about one aspect of https://github.com/giakki/uncss/issues/258.  It says that uncss should not remove @font-face rules because an author could still inline the style.  I imagine that would be done sort of like this (import-css.css):
@font-face {
    font-family: myFirstFont;
    src: url(sansation_light.woff);
}

index.html

 My first font text

But what if index.html or any other html or javascript file does not reference myFirstFont.  It seems like it would be safe for uncss to remove the corresponding @font-face rule in this case or am I missing something?
In any case https://github.com/jonathantneal/postcss-font-magician might actually make a lot more sense since it uses an on-demand approach rather than a push one.  I'll have a more detailed look.  Thanks again.

But what if index.html or any other html or javascript file does not reference myFirstFont. It seems like it would be safe for uncss to remove the corresponding @font-face rule in this case or am I missing something?

In that case, it would be safe for uncss to remove the @font-face. However, uncss doesn't check style attributes. Also, it can't check what elements (potentially containing style attributes) the JS adds due to user interaction. In short, it just requires too much overhead for uncss to try and process this in a safe way.
If this clears things up for you, please close this issue.

uncss doesn't check style attributes.
Aha!  Gotcha.  I think I'm almost home free.

At compile and test time I'd like to make all the fonts available via utilities like these (The root variable is for baking in the font using the @apply(--u-font-open-sans) function):
:root {
  --u-font-open-sans {
    font-family: "Open Sans", var(--font-family-helvetica-neue) !important;
  }
}

.u-font-open-sans {
  font-family: "Open Sans", var(--font-family-helvetica-neue) !important;
}

.u-font-montserrat {
  font-family: Montserrat, var(--font-family-helvetica-neue) !important;
}

These would be imported at the top of the main stylesheet like this:
import 'superfly-css-utilities-fonts';
In this case every all the corresponding @font-face rules would be created by font-magician, which is hopefully not a big deal at design time.
I would then run the entire build again to produce the css to be deployed, but would run uncss before running font-magician and that would remove any of the unused u-font... utilities, and font-magician would then import only the ones that are used....Hopefully that does the trick!  Thanks again for all your input on this!

Also, it can't check what elements (potentially containing style attributes) the JS adds due to user interaction.

Ryan, this argument is true, but I believe it a strawman.
Uncss can't also check what elements (potentially containing class elements) the JS adds due to user interaction. But that doesn't stop us from doing so, and making something useful called "uncss". :)
Uncss could be amended to check style attributes, and I would have no issues with that, as it's all very similar conceptually/procedurally to what is done with class attributes.

Uncss could be amended to check style attributes, and I would have no issues with that, as it's all very similar conceptually/procedurally to what is done with class attributes.

Yeah, it could; but what's the point? In this user's case, they were actually asking about stripping Google font @import statements. To me, it seems like a lot of work for minimal benefit. If someone really needs style attributes checked, we can bikeshed that then IMHO.

I built this superfly-css-task-deploy task that does ended up  removing unused @font-face and @import statements.  It works like this.

At design time everything is compiled from the src directory to the target directory.
At deploy time css is compiled from the target directory to the deploy directory but uncss strips everything that is not used in HTML (And soon javascript after I update the task).

Full demo here superfly-css-component-button.
Run npm run update to install everything.  Run npm run build to build the test.  Finally run gulp deploy:css and gulp deploy html to deploy the minified and uncssed css and test html page correspondingly


x64 simd: Incorrect codegen leads to wrong result

Found with some fuzzing, this module:
(module
  (func (result i64)
      v128.const i64x2 -1 1
      global.get 0
      f64x2.replace_lane 0
      i64x2.extract_lane 1
  )

  (global f64 (f64.const 1))
  (export "" (func 0)))

leads to:
$ wasmtime run --enable-simd --invoke '' test.wat
0

but the result should be 1
cc @jlb6740, @abrown

I chose this to poke around with objdump and the new module serialization format (not that I couldn't do this before, I just wanted to make sure it all worked), and it looks like the assembly is:
0000000000000000 <_wasm_function_0>:
       0: 55                            pushq   %rbp
       1: 48 89 e5                      movq    %rsp, %rbp
       4: f3 0f 6f 05 14 00 00 00       movdqu  20(%rip), %xmm0  # 20 <_wasm_function_0+0x20>
       c: f2 0f 10 47 30                movsd   48(%rdi), %xmm0
      11: 66 48 0f 3a 16 c6 01          pextrq  $1, %xmm0, %rsi
      18: 48 89 f0                      movq    %rsi, %rax
      1b: 48 89 ec                      movq    %rbp, %rsp
      1e: 5d                            popq    %rbp
      1f: c3                            retq
      20: ff ff                         <unknown>
      22: ff ff                         <unknown>
      24: ff ff                         <unknown>
      26: ff ff                         <unknown>
      28: 01 00                         addl    %eax, (%rax)
      2a: 00 00                         addb    %al, (%rax)
      2c: 00 00                         addb    %al, (%rax)
      2e: 00 00                         addb    %al, (%rax)

It looks like xmm0 is reused for the global.get (or something about that) with some instructions possibly getting fused together. My guess is that there's a bug informing regalloc of used/defined registers somewhere which would fix this.


Simpler access to kitten data fields

Access fields from KittenData object through accessors instead of digging into internal hash object.

Coverage decreased (-0.13%) to 80.53% when pulling 4e6a39c8691d038c0899a10900c4766b0d65d1b3 on fix-access-to-kitten-data-fields into c1fe9c09d201a9d472f826ad918e12352104f9c9 on staging.

Coverage increased (+0.49%) to 81.15% when pulling c57429fb23d707f8b8ebd381296af93e266c892d on fix-access-to-kitten-data-fields into c1fe9c09d201a9d472f826ad918e12352104f9c9 on staging.


remove all flatpak stuff, because it will be hosted directly on flathub

[x] URL in the readme is updated

The license depends on the mode of distribution (as described in the "License" tab of pyfda:

The pyFDA source code is published under a permissive MIT license at the Github repository chipmuenk/pyfda and at PyPI, Icons (except the pyFDA icon itself) are taken from the "Open Iconic" collection (MIT license).
The self-contained pyFDA package (bundled e.g. with the help of pyInstaller or as a flatpak) is published under a GPLv3 license as it bundles some components with (L)GPL licenses, requiring an (L)GPL compliant license. See also wikipedia on license compatibility.

For this reason, I think pyfda needs to be distributed under the GPLv3 license at Flathub.

ok than I will change to it

@chipmuenk
I added a flatpak build manifest adapted from Gittyup, not sure if it will be executed when it is available the first time

Looks good! I'd just like to change "pyFDA" in favour of "pyfda" because the capitalized spelling has given me trouble several times in the past when exchanging files between Windows and Linux.

@Murmele If changing the case from "pyFDA" to "pyfda" creates extra work just tell me, then I'll merge your PR the way it is.

No thats not a problem I will do

@Murmele : CI still fails at the moment (should it be working already?) with the followig error
2022-04-08T14:34:45.0251564Z From https://github.com/chipmuenk/pyfda
2022-04-08T14:34:45.0253158Z  * [new ref]         a2be5eaabd182e223ba8e940390bebc4bf1b22f8 -> origin/master
2022-04-08T14:34:45.0279483Z ##[endgroup]
2022-04-08T14:34:45.0280224Z ##[group]Determining the checkout info
2022-04-08T14:34:45.0287412Z ##[endgroup]
2022-04-08T14:34:45.0299141Z ##[group]Checking out the ref
2022-04-08T14:34:45.0300307Z [command]/usr/bin/git checkout --progress --force -B master refs/remotes/origin/master
2022-04-08T14:34:45.1328532Z Reset branch 'master'
2022-04-08T14:34:45.1333172Z branch 'master' set up to track 'origin/master'.
2022-04-08T14:34:45.1369917Z ##[endgroup]
2022-04-08T14:34:45.1446617Z [command]/usr/bin/git log -1 --format='%H'
2022-04-08T14:34:45.1471324Z 'a2be5eaabd182e223ba8e940390bebc4bf1b22f8'
2022-04-08T14:34:45.1808165Z ##[group]Run GuillaumeFalourd/clone-github-repo-action@v1
2022-04-08T14:34:45.1808497Z with:
2022-04-08T14:34:45.1808722Z   owner: flathub
2022-04-08T14:34:45.1809285Z   repository: com.github.chipmuenk.pyfda
2022-04-08T14:34:45.1809567Z ##[endgroup]
2022-04-08T14:34:45.2029849Z ##[command]/usr/bin/docker run --name bcf09854093cf25d94ed1b05322187b56d20e_812943 --label 2bcf09 --workdir /github/workspace --rm -e INPUT_OWNER -e INPUT_REPOSITORY -e INPUT_ACCESS-TOKEN -e HOME -e GITHUB_JOB -e GITHUB_REF -e GITHUB_SHA -e GITHUB_REPOSITORY -e GITHUB_REPOSITORY_OWNER -e GITHUB_RUN_ID -e GITHUB_RUN_NUMBER -e GITHUB_RETENTION_DAYS -e GITHUB_RUN_ATTEMPT -e GITHUB_ACTOR -e GITHUB_WORKFLOW -e GITHUB_HEAD_REF -e GITHUB_BASE_REF -e GITHUB_EVENT_NAME -e GITHUB_SERVER_URL -e GITHUB_API_URL -e GITHUB_GRAPHQL_URL -e GITHUB_REF_NAME -e GITHUB_REF_PROTECTED -e GITHUB_REF_TYPE -e GITHUB_WORKSPACE -e GITHUB_ACTION -e GITHUB_EVENT_PATH -e GITHUB_ACTION_REPOSITORY -e GITHUB_ACTION_REF -e GITHUB_PATH -e GITHUB_ENV -e GITHUB_STEP_SUMMARY -e RUNNER_OS -e RUNNER_ARCH -e RUNNER_NAME -e RUNNER_TOOL_CACHE -e RUNNER_TEMP -e RUNNER_WORKSPACE -e ACTIONS_RUNTIME_URL -e ACTIONS_RUNTIME_TOKEN -e ACTIONS_CACHE_URL -e GITHUB_ACTIONS=true -e CI=true --network github_network_3c4cab989daa41768fc0556b2cf3f56c -v "/var/run/docker.sock":"/var/run/docker.sock" -v "/home/runner/work/_temp/_github_home":"/github/home" -v "/home/runner/work/_temp/_github_workflow":"/github/workflow" -v "/home/runner/work/_temp/_runner_file_commands":"/github/file_commands" -v "/home/runner/work/pyfda/pyfda":"/github/workspace" 2bcf09:854093cf25d94ed1b05322187b56d20e  "flathub" "com.github.chipmuenk.pyfda" ""
2022-04-08T14:34:45.6220138Z Cloning into 'com.github.chipmuenk.pyfda'...
2022-04-08T14:34:45.9234476Z fatal: could not read Username for 'https://github.com': No such device or address
2022-04-08T14:34:45.9276783Z Error: Couldn't clone com.github.chipmuenk.pyfda repository. Check the inputs or the PAT scope.

@chipmuenk No not yet, the problem is that flathub/com.github.chipmuenk.pyfda does not exist yet, it will be created as soon as the pullrequest on flathub will be processed. I will create a new pullrequest with the CI build after it is uploaded at flathub


How to open parquet files from local folder

Is there a way to create connection to a local folder and read parquet files stored in it as a table just like CSV connection?

I think we can do it by writing our own custom JDBC driver. Unfortunately, since we only ship our own JDBC drivers in commercial products, this feature won't be available in the DBeaver Community.

One workaround, for anyone wondering, is to use an in-memory DuckDB database, and then do:
SELECT * FROM read_parquet('path_to_parquet');

Now DBeaver supports it https://github.com/dbeaver/dbeaver/wiki/Database-driver-Parquet


Tabular/CSV result view in AQL Editor

As a developer/analyst, I would like to be able to transform JSON results to CSV so that I can send them as tables over email or dump them into Excel for quick ad-hoc reporting.
Right now, this can only be accomplished through the use of external tools or web sites (e.g., ttp://konklone.io/json/, http://csvkit.readthedocs.org/en/latest/scripts/sql2csv.html).  Obviously, this works better for flat result sets, so people wouldn't use it for hierarchical result sets.
This could be accomplished by adding a button or tab for displaying the results in a text field in CSV format.  The existing Download button could also then be modified to send the results in CSV, not JSON, format to the browser when the user wants CSV.  The transformation code be native or use the utility referenced above.  (This should be an offline capability, not something that requires internet access to work.)
Thanks

@minnownoir do you mean something like this https://youtu.be/l9IWLOO4cBE?

@baslr: Probably. How (and when) does it work though?

@Simran-B, it works with every resultset thats an array of objects. It collects all keys from every object.
https://github.com/DUOUNO/ArangoDB-view/blob/5521f2faf0c2f8c8ce0eb5a5321d7855ef11eca3/src/src/aql/aqlController.js#L217
You can try it out.

Looks like a good start.  The main functional requirements would be the
ability to copy and paste into email (formatting in Outlook is okay)  for
dissemination or into Excel for building charts.
Thanks!
On Mar 5, 2016 5:22 AM, "Manuel B."<EMAIL_ADDRESS>wrote:

@minnownoir https://github.com/minnownoir do you mean something like
this https://youtu.be/l9IWLOO4cBE?
—
Reply to this email directly or view it on GitHub
https://github.com/arangodb/arangodb/issues/1101#issuecomment-192616750.

Hi @minnownoir,
I have added a button to copy the result as CSV into the clipboard. https://www.youtube.com/watch?v=1Y-654DKlJo

Looks good. Thanks so much for doing this.
On Mar 11, 2016 2:52 AM, "Manuel B."<EMAIL_ADDRESS>wrote:

Hi @minnownoir https://github.com/minnownoir,
I have added a button to copy the result as CSV into the clipboard.
https://www.youtube.com/watch?v=1Y-654DKlJo
—
Reply to this email directly or view it on GitHub
https://github.com/arangodb/arangodb/issues/1101#issuecomment-195239770.

We will support tabular and graph output in the upcoming release.


Running cmd in container on remote docker host hangs

I have a problem with running a command in docker container on remote docker host. When I do that locally, all is fine. On remote docker host, the command is invoked, I see stdout, but it hangs then. Am I doing something wrong?
How to reproduce:
base_image = Docker::Image.create('fromImage' => 'alpine:3.2')
container = base_image.run(['/bin/echo', '123'])
container.attach(stream: true, stdout: true,
                 stderr: true, logs: true, tty: false) do |stream, chunk|
  puts("#{stream}: #{chunk}".strip())
end
container.delete()

This is similar to #251.

Update
This works fine (locally and remotely) when using docker client command line:
$ DOCKER_HOST=tcp://<remote_ip>:2375 docker run -ti alpine:3.2 /bin/echo 123
123
$

@xmik can you run the same code with the environment variable EXCON_DEBUG=true on? I'm curious if you're actually receiving anything from the daemon.  Since you're definitely connecting to the remote host, and running some commands we can assume this isn't an SSL problem.
Which versions of docker are you running?  I'm wondering if there was an API update that we're not using correctly now.  It does seem odd that an HTTP endpoint would behave differently remotely versus locally.
Lastly: If you run docker start CONTAINER_ID on that container on the remote host after the hang, does it complete successfully?

Thanks for fast response. Today I am on different workstation (different computer, different place) and the ruby snippet above works fine (!). Tommorrow I'll be on the first workstation and will give more feedback tommorrow.

@xmik oh boy! Ok, we can close this for now.  Feel free to open it back up if you've figured something out!

I gave it another try. This is clearly not a docker-api issue. Some kind of solution for me is to stream logs after the command is run, instead of seeing them live (like in dockly).
Sorry for bothering you @tlunter with the false issue.

@xmik one thing that I've seen the docker client do is:

Create the container (but not start)
Attach to the container (in a different thread)
Start the container

This works really well in Go with goroutines, but with a bit of thread management can work.  Maybe give that a try?


Report declaration/interface errors on start

When an interface file contains an error, it fails silently, resulting in unexpected errors:
declare module http {
  declare function createServer(callback?: (req: httpIncomingMessage, res: httpServerResponse) => void): httpServer
}

declare class httpServer {}
declare class httpIncomingMessage {}

// INVALID class method declaration syntax
declare class httpServerResponse {
  declare function end(chunk?: string): void
}

Results in:
http
Required module not found

@bhosmer took care of this in 729c2aff651b049e749875ab3d13de6041bd708b. Now, your example results in:
flow-test/lib/test.js:10:11,18: Library parse error:
flow-test/lib/test.js:10:11,18: Unexpected identifier

which is much nicer!

Fixed in 0.13


Update entry.csv

Added abapunit2junit, a project to trigger abap unit tests and present them as junit-results. The results can then be used in different tools, for example Jenkins or Azure Devops.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.You have signed the CLA already but the status is still pending? Let us recheck it.


Enforce dynamic attributes with explicit receiver

Fixes #687
factory_bot allows you to define attributes on an explicit receiver by
passing in the definition proxy as the first argument to the block.
This is not quite ready to be merged, but I wanted to get some feedback before going any further. Does this approach make sense to you?
The class is too big, so I will have to move some things around to get the build to pass. Any advice on the best way to break this up?

Before submitting the PR make sure the following are checked:

[x] Feature branch is up-to-date with master (if not - rebase it).
[X] Squashed related commits together.
[X] Added tests.
[x] Added an entry to the changelog if the new code introduces user-observable changes.
[x] The build (bundle exec rake) passes (be sure to run this locally, since it may produce updated documentation that you will need to commit).

Sorry it took so long for me to come back to this.
@jonatas thanks for the review - I took your suggestions.
I ended up moving the constants out of this specific cop and onto RuboCop::RSpec::FactoryBot, but then on rebasing realized that the module was removed in https://github.com/rubocop-hq/rubocop-rspec/commit/a5df6e2588401982b80ce8036614231d78aa4745#diff-3b3465ed7d5d185d4bfa9acc4d26546f. I am open to other suggestions on how to organize things.

The module was removed only because it was empty. You’re welcome to add the module back with some contents :-)


Add Black, Isort and Codecov to workflow

Functionalities to add to workflow:

[x] Black
[x] Isort
[x] Codecov
[x] Deploy docs

Adding some routines to the workflow to run after the tests.

It looks like secrets are only available if we create a PR from a branch within the repository (not from a fork).
I will merge this one and try to create a branch inside the repository to test it.

It looks like secrets are only available if we create a PR from a branch within the repository (not from a fork).
I will merge this one and try to create a branch inside the repository to test it.