DNS Zone tags limitation not added

Cannot Set tag value as colon [:] character for DNZ zone.  It would be great if we could add this as a limitation in tag limitation document.  I have raised this as an issue with the DNS team.

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

ID: 55b4c3f6-7ea3-9b94-cd8c-cbe37dc31656
Version Independent ID: 0310805b-ff71-85bf-3f74-ca4caa6a46ce
Content: Tag resources, resource groups, and subscriptions for logical organization - Azure Resource Manager
Content Source: articles/azure-resource-manager/management/tag-resources.md
Service: azure-resource-manager
Sub-service: management
GitHub Login: @tfitzmac
Microsoft Alias: tomfitz

@rajakumarbabu - Thanks for brining this to our attention. We will investigate it further and update you shortly.

@rajakumarbabu - Thanks again for bringing this to our attention. We have updated the Doc and it will be live once its merged.  We will now proceed to close this thread. If there are further questions regarding this matter, please tag me in your reply. We will gladly continue the discussion and we will reopen the issue.


Refactor ETL and publishing API stream so we store every edition of a content item

Summary
This changes both the nightly ETL process and the publishing API consumer so that multiple editions of a content item can be tracked per day. At the moment, we update Dimensions::Item records whenever we see multiple messages for the same content item in the same day, instead of inserting a new record.
This will have implications if we want to show historical quality metrics within publishing apps, because publishing apps show users a complete version history, rather than daily snapshots.
We're also storing fact-like data on the dimension itself, which is not following proper conventions and may make it harder to adopt 3rd party tools.
The solution we agreed upon was to create a new facts table with edition-level granularity, in addition to the current facts table that is a daily snapshot of every content item. This PR doesn't add that facts table - I'll do this in a future PR.
Trello: https://trello.com/c/SWlCL8xI/240-5-track-content-editions-metrics-through-time
How it works now

The publishing API consumer creates a new Dimensions::Item if there is no existing item for the same content_id with latest: true
Otherwise, it marks the existing item as outdated: true and updates its base path in place
Overnight, the OutdatedItemsProcessor processes every item that has outdated: true and latest: true

It creates a new version of the item with latest: true, outdated: false
It updates the previous version to be latest: false, updated: false
It triggers an async job to set the content details and quality metrics on the new version

Then, MetricsProcessor creates a Facts::Metric record for every item with latest: true

How it should work after this PR

The publishing API consumer creates Dimensions::Item records for every edition, and marks them as outdated.
The publishing API consumer marks the latest item per content id per day using latest=true
Overnight, the OutdatedItemsProcessor processes every item that has outdated: true

It triggers an async job to set the content details and quality metrics on the new version
That job sets outdated: false on the item

Then, MetricsProcessor creates a Facts::Metric record for every item with latest: true

How it should work when we're done with this story
We can remove the outdated flag and OutdatedItemsProcessor from the codebase.

The publishing API consumer creates Dimensions::Item records for every edition
The consumer creates a Facts::Version record for each edition

It populates it with content details from the message
It fetches the quality metrics and records those too

It marks the latest item per content id per day using latest=true
Overnight, MetricsProcessor creates a Facts::Metric record for every item with latest: true

(Optional) It takes a snapshot of the version facts to make it easier to query daily metrics

Things to fix

[x] At the moment the "latest" version is whatever version we happened to process last. However, RabbitMQ can send us messages out of order, or duplicate messages. We should read the publishing API version and/or message creation time so that we can reconcile our concept of latest with the publishing API's concept of latest, and avoid creating multiple records for the same edition.
See Rummager ADR 002 for a discussion of this problem in the context of search.

[x] I need to add in an integration test that makes sure Facts::Metric has the right granularity when there are multiple editions per day

I'd prefer to get the test in just because this is quite a big change, but I'll do this now. The other part can wait though.

@KyleMacPherson I think this can be merged now

I've just pushed another commit which changes the consumer to respect the order of the messages based on payload_version.
That should be the last thing for this PR.


Training error: change config.size to [256, 256] result in error

Thank you for your work. I met the following errors when I changed the config size to [256, 256], could you help me?
Start evaluation.
Traceback (most recent call last):
  File "dreamer.py", line 445, in <module>
    main(parser.parse_args(remaining))
  File "dreamer.py", line 408, in main
    tools.simulate(eval_policy, eval_envs, episodes=config.eval_episode_num)
  File "/disk/users/jk639/Jing_ws/rl_rule_exceptions/dreamerv3-torch/tools.py", line 147, in simulate
    action, agent_state = agent(obs, done, agent_state, reward)
  File "dreamer.py", line 103, in __call__
    policy_output, state = self._policy(obs, state, training)
  File "dreamer.py", line 121, in _policy
    latent, _ = self._wm.dynamics.obs_step(
  File "/disk/users/jk639/Jing_ws/rl_rule_exceptions/dreamerv3-torch/networks.py", line 229, in obs_step
    x = self._obs_out_layers(x)
  File "/disk/no_backup/jk639/env_dreamer3/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/disk/no_backup/jk639/env_dreamer3/lib/python3.8/site-packages/torch/nn/modules/container.py", line 217, in forward
    input = module(input)
  File "/disk/no_backup/jk639/env_dreamer3/lib/python3.8/site-packages/torch/nn/modules/module.py", line 1501, in _call_impl
    return forward_call(*args, **kwargs)
  File "/disk/no_backup/jk639/env_dreamer3/lib/python3.8/site-packages/torch/nn/modules/linear.py", line 114, in forward
    return F.linear(input, self.weight, self.bias)
RuntimeError: mat1 and mat2 shapes cannot be multiplied (1x66048 and 4608x512)

I have made it possible to handle images with sizes that are powers of 2, so could you like to give it a try?

I made it possible to handle images of power-of-2 sizes (128, 256, ...), so why not give it a try?

I made it possible to handle images of power-of-2 sizes, so could you give it a try?

Now it works! Thank you!


ISIS-1678: replace with ClockService

Remove org.apache.isis.applib.clock.Clock, replace with org.apache.isis.applib.services.clock.ClockService

I think its save to assume, that https://issues.apache.org/jira/browse/ISIS-1678 can already be considered resolved. The VirtualClock was only introduced lately. And has a different use-case within the framework than the previous Clock had. I'd rather not move it.
Hope you don't mind if I close this PR without merging. Needless to say its much appreciated seeing PRs and people that want to help getting tasks done. Thumbs up!

Oh @ErnoViitanen-LUT - and by the way, if thats your first PR ever. Cool stuff, keep going!

Hi Erno,
and to echo what Andi says - join our Slack channel and have a chat first
about what you'd like to work on
Thanks
Dan
On Sun, 21 Feb 2021 at 06:51, Andi Huber<EMAIL_ADDRESS>wrote:

Oh @ErnoViitanen-LUT https://github.com/ErnoViitanen-LUT - and by the
way, if thats your first PR ever. Cool stuff, keep going!
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/apache/isis/pull/391#issuecomment-782810389, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH33SN2QQZ66CVD2RL7HY3TACUQJANCNFSM4X54OZ5Q
.


[QUESTION] Excel page orientation and other parameters

Prerequisites

[ x] Checked if your Laravel Excel version is still supported: https://docs.laravel-excel.com/3.1/getting-started/support.html#supported-versions
[ x] Able to reproduce the behaviour outside of your code, the problem is isolated to Laravel Excel.
[ x] Checked that your issue isn't already filed.
[ x] Checked if no PR was submitted that fixes this problem.
[ x] Filled in the entire issue template

Versions

PHP version: PHP Version 7.2.21-1+ubuntu16.04.1+deb.sury.org+1
Laravel version: Laravel 5.8
Package version: "maatwebsite/excel": "^3.1",

Description
Hello, I am using the Laravel Excel 3.1, but when I export in no matter what format I cant seem to find in documentation that would explain on how do I set orientation or other parameters.
Steps to Reproduce
Just regular:
return (new Exports)->download('gantt.xlsx', \Maatwebsite\Excel\Excel::XLSX);
Expected behavior:

Actual behavior:
What I woul like to achive is:

Put orientation in Landscape
Change the max widht to 1 page
Format the page to be A4 format.

Additional Information
Exports model:
`
class Exports implements FromView
{
use Exportable;
public function view(): View
{

    $_date = date('Y-m-d');
    $_chartStart = date('Y-m-d', strtotime("-2 weeks", strtotime($_date)));
    $_chartEnd = date('Y-m-d', strtotime("+2 months", strtotime($_date)));
    $_duration = ROUND((abs(strtotime($_chartEnd) - strtotime($_chartStart)) + 24 * 3600) / (24 * 3600));
    $_currentMonth = date("Y-m", strtotime($_chartStart));
    $_today = date("m-d", strtotime($_chartStart));

    return view('gantt.pdf', [
        'parent_task' => Task::where('parent', 0)->where('status', '1')->orderBy('priority', 'asc')->get(),
        'child_task' => Task::where('status', '1')->where('permission', '!=', -1)->get(),
        'duration' => $_duration,
        'month' => $_currentMonth,
        'start' => $_chartStart,
        'end' => $_chartEnd,
        'today' => $_today,
    ]);

}

}
My Controller:
return (new Exports)->download('gantt.xlsx', \Maatwebsite\Excel\Excel::XLSX);

Hello @dot431
As of Laravel Excel 3.0, a lot of convenience methods have been removed, as they were nothing more than wrappers around existing PHPSpreadsheet methods.
You can still use them, and @patrickbrouwers  has actually given an example for exactly your situation in his blogpost about the 3.0 release.
I'll copy paste the relevant code here, but make sure to read the blog for more information:
https://medium.com/maatwebsite/laravel-excel-lessons-learned-7fee2812551
You can create Macro's for any missing convenience methods:
Writer::macro('setCreator', function (Writer $writer, string $creator) {
    $writer->getProperties()->setCreator($creator);
});

Sheet::macro('setOrientation', function (Sheet $sheet, $orientation) {
    return $sheet->getPageSetup()->setOrientation($orientation);
});

Then in the Export class you can use it as follows:
class InvoicesExport implements WithEvents
{
    public function registerEvents(): array
    {
        return [
            BeforeExport::class  => function(BeforeExport $event) {
                // Macro
                $event->writer->setCreator('Patrick');

                // Or via magic __call
                $event->writer
                ->getProperties()
                ->setCreator('Patrick');
            },
            AfterSheet::class    => function(AfterSheet $event) {
                // Macro
                $event->sheet
                ->setOrientation(PageSetup::ORIENTATION_LANDSCAPE);

                // Or via magic __call
                $event->sheet
                ->getPageSetup()
                ->setOrientation(PageSetup::ORIENTATION_LANDSCAPE);
            },
        ];
    }
}

I hope this helps you solve your problem!

Hello @jochemfuchs , thank you for your help, I have actually seen this article, but I didn't know Laravel had Macros :D So when I read it - it was really confusing. At the end of the day I made it work, thanks for making me think. For other dummies like me here are some reference links:

Scotch.io article about Macros if you have your project skip to 'Bootstrap Service'
Documentation about Macros, basically the same as @jochemfuchs but if you need an extra read

In your Macro don't forget to add use \Maatwebsite\Excel\Sheet; & if you are printing a view your class in Export should be class Exports implements FromView, WithEvents {}
Hope this helps a bit :)

👍


TapTarget is placed behind RecyclerView items.

I'm trying to add a TapTarget in a RecyclerView item, but the TapTarget appears behind the item.
// Gets the first RecyclerView item
View view = UIUtils.getFirstVisibleItem(circlesView);
TapTarget tapTarget = TapTarget.forView(view, title, description);
new TapTargetSequence(activity).targets(tapTarget).start();

public class UIUtils {
  public static View getFirstVisibleItem(RecyclerView recyclerView) {
    View view = null;
    RecyclerView.LayoutManager layoutManager = recyclerView.getLayoutManager();
    if(layoutManager instanceof LinearLayoutManager) {
      int index = ((LinearLayoutManager) layoutManager).findFirstCompletelyVisibleItemPosition();
      view = layoutManager.findViewByPosition(index);
    }
    return view;
  }
}

If I increase the target radius, the appearance is a little better, but is not working as I expected. Look at the second screenshot.

[X] I have verified the issue exists on the latest version
[X] I am able to reproduce it

Version used:
com.getkeepsafe.taptargetview:taptargetview:1.7.0
Stack trace:
No stack trace
Android version:
6.0
Screenshots:

Interesting... are you setting the elevation for the view that appears on top?
A view hierarchy dump of that screen would be helpful in figuring out whats going on if youre not setting the elevation.

No, I'm not setting elevation.
This is a simplified version of my layout:
<?xml version="1.0" encoding="utf-8"?>
<android.support.v4.widget.DrawerLayout
    xmlns:android="http://schemas.android.com/apk/res/android"
    xmlns:app="http://schemas.android.com/apk/res-auto"
    android:id="@+id/drawer_layout"
    android:layout_width="match_parent"
    android:layout_height="match_parent">

    <RelativeLayout
        android:layout_width="match_parent"
        android:layout_height="match_parent">

        <include layout="@layout/progress_view"/>

        <LinearLayout
            android:orientation="vertical"
            android:layout_width="match_parent"
            android:layout_height="match_parent">

            <include layout="@layout/toolbar"/>

            <LinearLayout
                android:id="@+id/circles_layout"
                android:orientation="vertical"
                android:visibility="gone"
                android:layout_width="match_parent"
                android:layout_height="match_parent">

                <android.support.v4.widget.SwipeRefreshLayout
                    android:id="@+id/refresh_layout"
                    android:layout_width="match_parent"
                    android:layout_height="match_parent">

                    <android.support.v7.widget.RecyclerView
                        android:id="@+id/circles"
                        android:layout_width="match_parent"
                        android:layout_height="match_parent"
                        android:clipToPadding="false"/>

                </android.support.v4.widget.SwipeRefreshLayout>

            </LinearLayout>

        </LinearLayout>

        <android.support.design.widget.CoordinatorLayout
            android:id="@+id/coordinator_layout"
            android:layout_width="match_parent"
            android:layout_height="match_parent">

            <android.support.design.widget.FloatingActionButton
                android:id="@+id/new_circle"
                android:visibility="gone"
                android:layout_width="wrap_content"
                android:layout_height="wrap_content"
                android:layout_gravity="bottom|end"
                android:layout_margin="@dimen/fab_margin"
                android:src="@drawable/add_circle"
                app:backgroundTint="@color/accent"
                app:rippleColor="@color/accent_dark"
                app:borderWidth="0dp"
                app:elevation="6dp"/>

        </android.support.design.widget.CoordinatorLayout>

    </RelativeLayout>

    <android.support.design.widget.NavigationView
        android:id="@+id/navigation_view"
        android:layout_width="wrap_content"
        android:layout_height="match_parent"
        android:layout_gravity="start"
        app:itemTextAppearance="@style/NavigationViewItemTextAppearance"
        app:menu="@menu/menu_drawer"/>

</android.support.v4.widget.DrawerLayout>

This is happening in other two RecyclerViews of other two fragments (ViewPager).

Hi, the problem here is that youre targeting the entire item view, which is quite large. I suspect you want to target part of the item view, and so you will need to target the specific view instead of the entire item view. Another option is specifying bounds to target.
The reason why it appears that the TapTargetView is behind is because we re-draw your target view on top of the tap target (otherwise you wouldnt be able to see it). Since your view is extra large, it is extending beyond the bounds of the target circle.
Tap targets are meant for smaller type views, like FABs or icon buttons, not entire RecyclerView items.
I'm curious to know what you were expecting to have happen when targeting the item view, though. It might be worth adding a convenience function where you can specify the view and then some Rect that is within the view's bounds to target.

I was expecting the inner circle to appear above the view, in the middle of it. I'm using another library that works fine. I will try to create a Rect, but I think it will be nice if the library support. What do you think?

You can accomplish it by using forBounds and specifying a Rect that is within the view's bounds.

@xiphirx. Specifying a Rect is not working well.
Look at the follow screenshots. I draw a Rect in Canvas and I pass the same Rect to TapTarget. Any suggestion?
int centreX = (int) (view.getX() + view.getWidth() / 2);
int centreY = (int) (view.getY() + view.getHeight() / 2);
Rect bounds = new Rect(centreX - 100, centreY + 100, centreX + 100, centreY - 100);

Paint paint = new Paint();
paint.setColor(Color.rgb(255, 0, 0));
paint.setStyle(Paint.Style.FILL);
Bitmap bitmap = Bitmap.createBitmap(view.getWidth(), view.getHeight(), Bitmap.Config.ARGB_8888);
Canvas canvas = new Canvas(bitmap);
canvas.drawRect(bounds, paint);
view.setBackgroundDrawable(new BitmapDrawable(bitmap));

TapTarget tapTarget = TapTarget.forBounds(bounds, title, description);

You want to use something like
final int[] location = new int[2];
view.getLocationOnScreen(location);
new Rect(location[0], location[1], location[0] + view.getWidth(), location[1] + view.getHeight());

instead of getX and getY since those methods are relative to the parent, not the screen.


use one nixpkgs instance

Push the nix configuration into the CLI so we don't need the overlay,
and so we don't need to create another instance of nixpkgs.
This also means that the python CLI can be executed directly as long as
the user has a recent-enough version of nix and make iterations a bit
faster.
For more details, see
https://zimbatm.com/notes/1000-instances-of-nixpkgs
TODO: the PR needs testing

TODO: the PR needs testing

If nix run.#tests-impure succeeds, the CLI can be considered working.

Thanks!


Validate managedclusteravailable before relocating

Code drop for
Check and ensure managed cluster condition availability, before processing relocation #283

I am not sure if this PR is necessary. The MCV is automatically updated every 30 seconds by default, though this interval can be adjusted using the UpdateIntervalSeconds setting in the ViewScope. Similarly, I believe the ManagedCluster follows a similar algorithm for condition updates. If that's the case, this lightweight test should suffice. Have we seen any issues that prompted this PR?  The one issue we had and fixed recently is here.

I am not sure if this PR is necessary. The MCV is automatically updated every 30 seconds by default, though this interval can be adjusted using the UpdateIntervalSeconds setting in the ViewScope. Similarly, I believe the ManagedCluster follows a similar algorithm for condition updates. If that's the case, this lightweight test should suffice. Have we seen any issues that prompted this PR? The one issue we had and fixed recently is here.

Hi @ShyamsundarR ,
Could you please confirm if this PR should be squashed as the fix that is being added to resolve the issue seem to have already been resolved with an alternative solution as mentioned by @BenamarMk.
thanks,
Pruthvi

@pruthvitd let's close this one, it should be handled via the MCV freshness as pointed out by @BenamarMk

Closing the pull request as this fix is unnecessary as pointed out by Benamer


Card type could be a class rather than a struct

Cards are entirely immutable as is, and with like 13,000+ of them potentially in use, it doesn't really make sense to copy them around as much as they're currently forced to be. Consider making Card a class.

I dont think it should be a class. Swift best practice is to keep data as structs as long as you dont have a reason to use a reference type (like when you want to be able to modify a existing piece of data). And also, value types aren't always copied. The standard library tries to use copy-on-write for value types when able to, so chances are there are not actually any copies made if you just pass them around, specially for immutable data.
I dont think we should use classes unless we can see some weird performance issues related to using value types.

Totally agree


vue slot event passed on all components

i am facing a dilemma here :  i have a component which has a slot , the slot passes an event to the component which is the acted on by the component , however if i add 2 component and pass the custom event on an event lets say click event , 2 instances of the events are returned , which means the event is listened by the two components unlike by the component that its slot has passed , check code below :
the main script that handles has both component (it will pass two instances of the event)
<notie-js>
 <button class="margin btn btn-success" @click.prevent="$broadcast('show::notie-js')" type="button">Success</button>
</notie-js>

<notie-js>
 <button class="margin btn btn-success" @click.prevent="$broadcast('show::notie-js')" type="button">Success</button>
</notie-js>

the component notie-js
<template>

<slot></slot>

</template>

<script>

var notie = require('notie');

module.exports = {

    props:{

		alert: {
		  type: Object,
		  default: function () {
			  return {
				alertType: 1 ,
				message: 'Success' ,
				time: 2

			  }
		  }

		},

	},

    data: function () {
            return {

          }
        },
	created: function() {

	},
	ready: function(){

	},
	methods : {

	   doNotification : function(){

		  if(this.alert){
			  notie.alert(this.alert.alertType,this.alert.message,this.alert.time);
		   }

	   },

	},
  events: {

     'show::notie-js': function () {
      console.log('notie-js event received');
     // this.doNotification();
    }

  },
 computed: {

  }

}
</script>

Thanks for filing the issue. Please follow the Issue Reporting Guidelines and provide a minimal JSFiddle or JSBin containing a set of reproducible steps that can lead to the behavior you described.

Thsi is not a bug. a $broadcast event is sent to all children, so ig you have two instances of <notie> as child components, both will react on this. (One of the reasons that $broadcastwill be deprecated in 2.0 - these unintended behaviours make $broadcast rather useless.)


ISPN-5653 keySet().iterator() does not propagate flags to remove()

Made sure to support iterator remove and various flags
Added additional documentation describing this interaction
Added tests for keySet, values and entrySet versions

https://issues.jboss.org/browse/ISPN-5653

Some remote test failures I have to check out.

Tests should be fixed now.

@wburns some minor comments. I left the scala for the experts :)

Updated.

Integrated


fix for rails 6.1

fix regarding issue 45

any plans to merge it?

I'm working on a rails 6.1 project, and when I add panoramic without specifying a version, bundler resolves it to 0.0.6 since 0.0.7 has a dependency on rails ~> 4
However, even when I grab version 0.0.7 on its own to peek at resolver.rb, I don't see the fix from this commit. Could you possibly publish a new version of your gem with this fix included?


Add benchmarks for to_dataframe and to_dask_dataframe

Related to #7472.

Seems to work. :) I'll do a quick merge and continue in #7472.


Update package version

@label-u/components 1.0.0-alpha.10 (2023-02-08)
Bug Fixes

components: show the full list in rightsidebar (bc4fb84)

Dependencies

@label-u/annotation: upgraded to 1.0.0-alpha.8

:tada: This PR is included in version 1.0.0-alpha.11 :tada:
The release is available on npm package (@alpha dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-alpha.9 :tada:
The release is available on npm package (@alpha dist-tag)
Your semantic-release bot :package::rocket:

:tada: This PR is included in version 1.0.0-alpha.1 :tada:
The release is available on npm package (@alpha dist-tag)
Your semantic-release bot :package::rocket:


gulp-concat seems to sallow errors

Thank you for a very useful project!
I have an issue regarding errors not being propagated. Please consider the following snippet from my gulpfile:
    ...
    .on('error', function(err) {
        console.log("A!");
    })
    .pipe(concat('Sample.js'))
    .on('error', function (err) {
        console.log("B!");
    })
    ...

When there are any errors I see "A!" in the output. However, I do not see "B!" in the output (even if the first error handling section is omitted).
This means the exit code ends up being incorrect and this messes up my build integration.

Node version?


Added Dev mode/SSH details for Paper Pro

The final ref isn't rendering properly, probably due to an extra space and use of ' instead of `
Upon looking at this in context, it would probably make more sense to have a separate developer mode page under the tech folder that we link to in a warning at the top telling rM Paper Pro users they will need to enable it first.


In mid-2022 BT3 was discontinued.

why not simply remove it totally from list ?

The tooling still exists it’s just no longer supported and only runs in offline mode. So my thought with a strike through is that it references the tooling but sets expectations that it’s going away. I can agree with just removing it as well.

ok, plz remove it totally

Addressed with https://github.com/meirwah/awesome-incident-response/pull/223


Multiple Region Codes

Added functionality for multiple region codes. See server.js example for syntax. I left some debug stuff behind. I'll remove that and upload a new version

I appreciate the PR! But I can't merge it as is; the tests haven't been updated to account for the modified behavior, and are consequently failing. There are also no new tests to verify that the newly added behavior functions correctly.
I'm also curious what motivated the choice of semicolon-separated values on the region member. That seems like it'd be a headache to manage, compared to having region be (or be able to be) an array of objects, with each object representing a single region.

That's alright! I just came across your project while looking online, and
thought I'd add that functionality for myself, then realized I could upload
it. I'm new to GitHub and the system you were using to build/run the code.
I'm just a self taught java developer. I made the region member a separated
list of values because it was the easiest thing for me to write. I wasn't
sure how you were defining then accessing different elements, so I just
wrote something quick and dirty in my spare time. I appreciate the reply!
Sorry I didn't look into updating the tests.
Gabe
On Mon, Jun 18, 2018, 2:34 PM Aaron Miller<EMAIL_ADDRESS>wrote:

I appreciate the PR! But I can't merge it as is; the tests haven't been
updated to account for the modified behavior, and are consequently failing.
There are also no new tests to verify that the newly added behavior
functions correctly.
I'm also curious what motivated the choice of semicolon-separated values
on the region member. That seems like it'd be a headache to manage,
compared to having region be (or be able to be) an array of objects, with
each object representing a single region.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/aaron-em/same-encoder/pull/9#issuecomment-398152553,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ASy-ARS2CkMecUtkKwd_BOAUF61jumNKks5t9_KwgaJpZM4UhZF9
.


Integration with dataviewjs

Could timeline be integrated with dataviewjs to build a timeline based upon yaml headers?

+1

+1

I read your issues and wait for this university semester to end :) I'm really sorry

Take your time man, really appreciate your work.
Just to clarify this issue for the time when your schedule allows you to work on this plugin; I would like to create these timelines with using the dataview plugin like in the case of the other timeline plugin.


How to generalize the many new attributes/values for Bioscales samples?

@aclum has creating new slots to capture several values that have been "introduced" by Bioscales, from either spreadsheets or some JGI database. It seems like many or all of these identifiers or attributes could be useful for our own data integration efforts. They may also help visitors to the Data Portal find samples that interest them.
However, those sheets and databases frequently project an attribute of one thing onto another, such as reporting the "genotype" or "chemotype" of a Biosample, when those attributes are more likely attributes of the tree from which a Biosample was collected. We may need to add the new values to some other class, or even start instantiating some new classes. We have Site, which we are using to hold the tree identifiers.
Even when we do find more project-specific attributes, we should be conservative in increasing the already huge number of slots available for Biosamples. Could we add a general purpose slot that takes a list of key:value pairs?
Additionally, some of these values are labels for something that would need to be looked up elsewhere, like a genotype of "BESC-999". Wouldn't researchers wanting to re-use Bioscales data be more interested in knowing which genes had been knocked out or mutated, as opposed to knowing an opaque genotype label?

https://github.com/microbiomedata/nmdc-schema/issues/642

Per Montana the way this is handled now is there is a slot for experimental_factor_other where the value is an ontological term:value

I will provide a suggested format
@mslarae13 could provide some valid and invalid examples


Move nbdime requirement to extra

This is only needed by the ancillary method to diff changes, and pulls in a number of other unnecessary dependencies

done in v0.5


In scene network objects are not initialized correctly when calling NetworkObject.Flush

Issue created from a bug report in #forge-bugs on discord
Version Number and Operating System(s):
Forge Version 11.02.2019 master
Expected behavior:
When automatic scenes is disabled and switching scenes. On scene load calling flush should initialize all network objects that are already in the scene.
Actual behavior:
Automatic Scenes is disabled in Forge's NetworkManager. I start a server, load a scene upon server creation, then call NetworkObject.Flush. NetworkObjects already contained in the second scene will not Initialize.
Reproduction Steps:
Steps to reproduce:
Open my example project, open mainMenu.unity, hit play, click the "Server"  button, the next scene will load, a Debug.Log should be playing from inside ExistingObject.cs, but does not. If you enable Automatic Scenes, and comment out line 114 in SpherakillNetworkManager.cs, the Debug.Log will fire due to Forge's internal scene loaded callback being fired.
Example project:
https://www.dropbox.com/s/9wdlz4zr6zccr0i/forgeFlushBug.unitypackage?dl=0
[Optional] Discord Username:
@ambientocclusion#7740

Seems to be not a bug. For in scene network objects the custom setup code will need to find and initialize all in scene NetworkBehaviors before calling Flush.
Not sure if something similar will need to be done on the client side as the example code provided only has server code.

I would love for NetworkManager.OnLevelFinishedLoading or NetworkManager.SceneReady to be exposed as public so I can rely on Forge's built in commands to ensure the scene is initialized properly for now and every future Forge release.

I guess the changes made to the NetworkManager in #236 are enough to make this work on custom solutions as the SceneReady can now be called as access to it has been changed.


Bikeshed private endpoint UI

Per request from @ThorstenHans
I don't have a strong feeling one way or the other.

I'd probably vote for private = true over public = false; route = false was a sneaky way to reuse the key but if we're adding an alternative key I'd default to a positive predicate.


Fix Azure AI Search Sample Issue

Fixes #30926
@joheredi, @dgetu for notification.

API change check
API changes are not detected in this pull request.

@joheredi, @dgetu Could you help review this PR? Thanks a lot.

@joheredi, @dgetu Could you help review this PR? Thanks a lot.

/check-enforcer override


Support for scipy sparse arrays

Apparently scipy now has sparse arrays with array indexing?
Unfortunately they do seem to inherit from the matrix classes, which makes checking their types a bit fraught.

actually that would be awesome if anndata was providing new sparse arrays not matrices. I find it very hard and annoying to memorize how things are working in sparse matrices. As an idea that should be easy to implement and will not break downstream projects:
# setter that internally converts sparse array into a matrix
ad.X_sparr = some_sparse_array

# getter that converts X into sparse csc_array
ad.X_sparr

Eventually I believe you want to migrate internals of anndata to manipulate arrays not matrices.

I think we are going to hold off on this until there is better support in the broader ecosystem for these classes. E.g. until scikit-learn can use these, it's difficult to recommend them. At that point we can quickly move to automatically reading these at IO time.

unstale this. Still waiting for bright moment of sparse arrays


Fix creation of user in run-mongod-replication

In run-mongod-replication CREATE_USER was not exported, so it can't be used in init-replset.sh.
[test-openshift]
Fixes: https://github.com/openshift/origin/issues/13659#issuecomment-292263840

[test-openshift]


Cleanup ota reference manual

Grammar and style changes made.
Updates to content may be required.
QA: Ran linter in editor.
Checked rendered output in browser, no rendering issues spotted. Linkcheck encountering issues not believed to be associated with any changes made in this commit.
 What does it solve?
Checklist
Optional. Add a 'x' to steps taken.
You can fill this out after opening the PR. "Did I..."

[x] Run spelling and grammar check, preferably with linter.
[x] Avoid changing any header associated with a link/reference.
[ ] Step through instructions (or ask someone to do so).
[x] Review for wordiness
[x] Match tone and style of page/section.
[x] Run make linkcheck.
[x] View HTML in a browser to check rendering.
[x] Use semantic newlines.
[x] follow best practices for commits.

[x] Descriptive title written in the imperative.
[x] Include brief overview of QA steps taken.
[x] Mention any related issues numbers.
[x] End message with sign off/DCO line (-s, --signoff).
[x] Sign commit with your gpg key (-S, --gpg-sign).
[x] Squash commits if needed.

[x] Request PR review by a technical writer and at least one peer.

Comments
Any thing else that a maintainer/reviewer should know.
This could include potential issues, rational for approach, etc.

Docs for fc7fec134232d98f439fed39cdee0d39ed2f819d are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2506/docs/artifacts/html/index.html

Docs for 636e9d846de041d2a281b0ccc7a757b3ed454778 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2508/docs/artifacts/html/index.html

Docs for 5bf69289133f6f274e27d73e8ab8430e622c77dd are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2509/docs/artifacts/html/index.html

Docs for 70fbcb10fbf976e683ae1181146cb45a59a1421d are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2510/docs/artifacts/html/index.html

Docs for 17e7c1955d3356cc5768c1f0e0f5eebab1ef9daf are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2511/docs/artifacts/html/index.html

Docs for 9ad4fe85af4ee607ac48136500add6129f2997ce are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2512/docs/artifacts/html/index.html

Docs for 19e771a446193f5a4e02d64af5177bb995a7fde5 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2513/docs/artifacts/html/index.html

Docs for 1d44971656fe4c1eb0202f102b76c7bb8cfe21aa are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2514/docs/artifacts/html/index.html

Docs for 8bd489804ebf9b6fab81da05e451d72619413405 are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2519/docs/artifacts/html/index.html

Docs for 42c851934577d422a358bd9cdd103cf21e077aaf are browsable at: https://ci.foundries.io/projects/fio-docs/builds/2524/docs/artifacts/html/index.html


Automated cherry pick of #5173: fix: sync cloud provider should change its cloud account's sync_status

Cherry pick of #5173 on release/2.13.
#5173: fix: sync cloud provider should change its cloud account's sync_status

Codecov Report

:exclamation: No coverage uploaded for pull request base (release/2.13@bccefab). Click here to learn what that means.
The diff coverage is 0%.

@@              Coverage Diff               @@
##             release/2.13   #5175   +/-   ##
==============================================
  Coverage                ?   6.83%
==============================================
  Files                   ?     528
  Lines                   ?   89550
  Branches                ?       0
==============================================
  Hits                    ?    6117
  Misses                  ?   82924
  Partials                ?     509

Flag
Coverage Δ

#aFlag
6.83% <0%> (?)

Impacted Files
Coverage Δ

pkg/compute/models/cloudproviders.go
1.01% <0%> (ø)

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 bccefab...cb9ff42. Read the comment docs.

/lgtm
/approve

/lgtm
/approve


Passing -ErrorAction to Invoke-Jenkins Job Breaks it

This has taken me a while to nail down as its been a real pain for me over the last couple of weeks.
The following code snippet below :
    $Splat = @{
        URI        = 'http://jenkins:8080'
        Credential = $Credential
        Name       = 'Send New User Notification Email'
        Crumb      = $Crumb
        Folder     = 'Service desk/Joiner Process'
        Parameters = @{
            samaccountname = $Joiner.samaccountname
            template       = 'New Account Information Default'
            toaddress      = $toaddress
        }
    }
    Try{
        Write-host "Starting jenkins slave job to send user notification email."
        Invoke-JenkinsJob @Splat -ErrorAction Stop
    }
    Catch{
        Write-Error $_
        $LastExitCode = 1
        exit 1
    }

Throws the following error
Cannot bind parameter because parameter 'ErrorAction' is specified more than once. To provide multiple values to parameters that can accept multiple values, use the array syntax. For example,
"-parameter value1,value2,value3".
The minute i remove the -Erroraction Stop from the Invoke-jenkinsJob call it works as expected.
I am on module version <IP_ADDRESS> and psVersion 5.1

To be clear it also does the same thing if i include the ErrorAction value in the SPLAT as well.

Thanks for raising this @hematic - I'll take a look over the next couple of nights and get it sorted for you.


Auto Birthday/Anniversary/ special day wishes and notifications to admins, modarators and members

Auto Birthday/Anniversary/ special day wishes and notifications to admins, modarators and members. This is sort after feature which I think can be implemented immediately

https://github.com/unaio/una/issues/2956


fix: set the correct lastModifiedBy when application or it's resources are updated

Description

Set the correct lastModifiedBy when application or it's resources are updated.

PR fixes following issue(s)
Fixes https://github.com/appsmithorg/appsmith/issues/26120
Media

A video or a GIF is preferred. when using Loom, don’t embed because it looks like it’s a GIF. instead, just link to the video

Type of change

Bug fix (non-breaking change which fixes an issue)

Testing

How Has This Been Tested?

[ ] Manual
[x] JUnit
[ ] Jest
[ ] Cypress

Test Plan

Add Testsmith test cases links that relate to this PR

Issues raised during DP testing

Link issues raised during DP testing for better visiblity and tracking (copy link from comments dropped on this PR)

Checklist:
Dev activity

[x] My code follows the style guidelines of this project
[x] I have performed a self-review of my own code
[x] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[x] My changes generate no new warnings
[x] I have added tests that prove my fix is effective or that my feature works
[x] New and existing unit tests pass locally with my changes
[ ] PR is being merged under a feature flag

QA activity:

[ ] Speedbreak features have been covered
[ ] Test plan covers all impacted features and areas of interest
[ ] Test plan has been peer reviewed by project stakeholders and other QA members
[ ] Manually tested functionality on DP
[ ] We had an implementation alignment call with stakeholders post QA Round 2
[ ] Cypress test cases have been added and approved by SDET/manual QA
[ ] Added Test Plan Approved label after Cypress tests were reviewed
[ ] Added Test Plan Approved label after JUnit tests were reviewed

/build-deploy-preview skip-tests=true

/ok-to-test


long_text attribute for retriever passages

Hi, I am creating a custom retriever, inheriting from dspy.Retrieve and overloading the __init__ and forward method.
Right now I am receiving an error on "long_text" not being present in the passages that my retriever is generating:
File ~/miniconda3/lib/python3.10/site-packages/dsp/primitives/search.py:10, in <listcomp>(.0)
      8     raise AssertionError("No RM is loaded.")
      9 passages = dsp.settings.rm(query, k=k, **kwargs)
---> 10 passages = [psg.long_text for psg in passages]
     12 if dsp.settings.reranker:
     13     passages_cs_scores = dsp.settings.reranker(query, passages)

AttributeError: 'str' object has no attribute 'long_text'

I am confused because I assumed that passages would be a list of strings, but it does not look like it's the case. However, when I look at the pinecone retriever, which is what I am using as a reference to implement mine, It does not look like it is using the "long_text"  field either.
https://github.com/stanfordnlp/dspy/blob/main/dspy/retrieve/pinecone_rm.py
What am I missing?

I am encountering the same.

Same here

@okhat Could you help answer this question? Thanks a lot!

Just had the same issue. This fixed it:
wiki_abstracts = dspy.ColBERTv2(url='http://<IP_ADDRESS>:2017/wiki17_abstracts')
dspy.settings.configure(lm=ollama_model, rm=wiki_abstracts)

Facing the same issue

I was able to resolve by adding
if hasattr(passages, 'passages'):
    passages = passages.passages

after this line https://github.com/stanfordnlp/dspy/blob/42a5943379d28d1673dc8fe332a3d596efdfc7a3/dsp/primitives/search.py#L12
It seems that we are getting a prediction object as the return of passages = dsp.settings.rm(query, k=k, **kwargs)

I think there are a few parts important for this to work:

dsp.search.retrieve: Calls the RetrieveModel and expects a list of objects with the key 'long_text'
dspy.retrieve.Retrieve.forward: The return type is Prediction, which contains a key 'passages'
Example RetrieveModels like Weaviate return the list of objects as expected by the retrieve function, but they should return Prediction.

A change is need to use the Prediction object in the retrieve function, and all Retrievers should return this object. Or we mist change the return type.
I did not check what other functions use this forward method. What I have seen sofar, we do not want to change the interface, so improving the Retrievers and the retrieve function feels more logical.

Is there a abstract class or object for this passage in the dspy framework? ;) it would be nice, becuase when we implement the custom retriver we can get the expected signature from the framework so...what I want to say if the framework (DSPy) works with this Passage API like this:
class Passage(ABC):
long_text: str
then this should be define herem and external tools, framwroks can interface with this over an adapter if neccesary ;) in my case I would just wire it :)
anyway, thanks for the info...I think i can fix this issue on my end

I just ran into this as well
The examples the docs give for a custom RM lead to this exact issue

I don't know why, but retrieve.py expects a list of dictionaries from the custom retriever. This works for me:
    def forward(self, query_or_queries: Union[str, List[str]], k: Optional[int] = None) -> dspy.Prediction:
        context = ['foo', 'bar']
        return [dotdict({"long_text": passage}) for passage in context]

I faced the same issue. This solved the problem for me.


Update Contributing.md doc

@Azure/azure-sdk-eng

@dsgouda @shahabhijeet can you guys please also review and provide feedback on the the documentation update on how to work in this repo.

There are over 90+ management plane SDK when compared to data plane SDKs, so naturally more any information we present should be geared first about management plane than data plane for now. So move management plane related stuff on the top.

Done


Graphical Glitches in virtual machines. UI unusable.

Expected Behavior
Consistent rendering
Actual Behavior
UI is not usable - see screen record
Reproduction Steps
Try to use insomnia client in a virtual machine (in my Case Guest and Host where Monterey on an intel Mac). Tried with parallels and vmware. Tried with and without hardware acceleration for graphics.
Is there an existing issue for this?

[X] I have searched the issue tracker for this problem.

Additional Information
perhaps related to : https://github.com/electron/electron/issues/33735
https://user-images.githubusercontent.com/1442798/195173013-fad61fe7-5c30-469c-b28d-8aaa47aea610.mp4
Insomnia Version
2022.6.0
What operating system are you using?
macOS
Operating System Version
Monterey in a Virtual machine on an intel Mac.
Installation method
Download from insomnia.rest
Last Known Working Insomnia version
2022.6.0

Hi @zuernBernhard, seems this is indeed related to the issue you mentioned, which is also related with https://github.com/electron/electron/issues/33685


[jvm-packages] Add BigDenseMatrix

ability to create DMatrix with bigger than Integer.MAX_VALUE size arrays
uses sun.misc.Unsafe

original author @michalkurka

thanks! I will review it shortly, really busy in a lot of stuffs recently

@CodingCat thanks for taking the time, please let me know if this is generally acceptable and I will then work on fixing the CI errors

hi @CodingCat, I have found some time and rebased this on top of master, please take a look

@CodingCat @trams Are you guys okay with the use of sun.misc.Unsafe, presumably to speed up serialization?

LGTM


Remove signup fields from campaign group

What's this PR do?
removes the signup fields config from the campaign group node form.
How should this be reviewed?

drush updb -y
drush fra -y
fields should be 💥

Any background context you want to provide?
This is the rest of the PR from #6514
Relevant tickets
refs #5914

👍 💥 ♻


[keyvault] Migrate remaining Key Vault packages to keyvault-common

Packages impacted by this PR

@azure/keyvault-keys
@azure/keyvault-secrets

Issues associated with this PR

Fix #22705

Describe the problem that is addressed by this PR
Noticed that I never actually finished the job for these two packages (oops!) so this PR brings Keys and Secrets up to speed with the latest keyvault-common goodness

API change check
API changes are not detected in this pull request.


Error 404 on shrinked URLs

as described here i did all the fixes but no results, except this cURL error but i think is not related to this problem
DB driver: pdo
SELECT `option_name`, `option_value` FROM `yourls_options` WHERE 1=1
SELECT `option_value` FROM `yourls_options` WHERE `option_name` = 'active_plugins' LIMIT 1
cURL error 28: Resolving timed out after 3514 milliseconds (POST on https://api.yourls.org/core/version/1.0/)
UPDATE `yourls_options` SET `option_value` = 'O:8:\"stdClass\":4:{s:15:\"failed_attempts\";i:45;s:12:\"last_attempt\";i:1453496502;s:11:\"last_result\";s:0:\"\";s:15:\"version_checked\";s:5:\"1.7.1\";}' WHERE `option_name` = 'core_version_checks'
SELECT COUNT(keyword) as count, SUM(clicks) as sum FROM `yourls_url` WHERE 1=1
SELECT * FROM `yourls_url` WHERE 1=1  ORDER BY `timestamp` desc LIMIT 0, 15;

Duplicate of #2022 (and even references it). Please do not create duplicate discussions just because nobody has answered in 16 hours.


App has crashed : java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so

Description
I did the same steps which is mentioned in this link (link is : https://medium.com/@jyubinpatel/make-reactnative-module-as-a-library-and-how-its-used-into-android-native-application-35b13f65ac7c) to make index.android.bundle file from react native project then putting it into a fresh native app to create a .aar file of it then we can use this in another needed native application where we exactly want to integrate this as library. Please let me know if any solution is available for this below error or related to this task which i have explained above.
I am getting this error while calling the react native application library (.aar file) in native android application, so when I run it I am calling the below code on which i am getting this error is as follows :
MainActivity class
import android.content.Intent
import androidx.appcompat.app.AppCompatActivity
import android.os.Bundle
import android.widget.TextView
class MainActivity : AppCompatActivity() {
override fun onCreate(savedInstanceState: Bundle?) {
super.onCreate(savedInstanceState)
setContentView(R.layout.activity_main)
var textView: TextView = findViewById(R.id.txt_hello)
textView.setOnClickListener {
startActivity(Intent(this@MainActivity, ReactNativeActivity::class.java))
}
}
}
ReactNativeActivity class
import android.app.Application;
import com.facebook.react.ReactNativeHost;
import com.facebook.react.ReactPackage;
import com.facebook.react.shell.MainReactPackage;
import java.util.Arrays;
import java.util.List;
public class ReactNativeActivity extends BaseActivity {
@Override
protected String getMainComponentName() {
    return "react_native_app_name";
}

@Override
protected ReactNativeHost createReactNativeHost(Application app) {
    return new ReactNativeHost(app) {
        @Override
        public boolean getUseDeveloperSupport() {
            return false;
        }

        @Override
        protected List<ReactPackage> getPackages() {
            return Arrays.asList(new MainReactPackage());
        }

        @Override
        protected String getBundleAssetName() {
            return "index.android.bundle";
        }
    };
}

}
BaseActivity class
import android.app.Application;
import android.os.Bundle;
import com.facebook.react.ReactActivity;
import com.facebook.react.ReactActivityDelegate;
import com.facebook.react.ReactNativeHost;
public abstract class BaseActivity extends ReactActivity {
private ReactNativeHost reactNativeHost;

/**
 * Returns the name of the main component registered from JavaScript. This is used to schedule
 * rendering of the component.
 */
@Override
protected abstract String getMainComponentName();

protected abstract ReactNativeHost createReactNativeHost(Application app);

protected ReactActivityDelegate createReactActivityDelegate(){
    return new ReactActivityDelegate(this, getMainComponentName()){
        @Override
        protected ReactNativeHost getReactNativeHost(){
            if(reactNativeHost==null){
                reactNativeHost = createReactNativeHost(getApplication());
            }
            return reactNativeHost;
        }
    };
}

}
Error :
App has crashed
java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
SoSource 0: com.facebook.soloader.ApkSoSource[root = /data/data/#####.##.###/lib-main flags = 1]
SoSource 1: com.facebook.soloader.DirectorySoSource[root = /data/app/~~vccykcNnSseE2lbdU59CjA==/#####.##.###-tIZ_hFLpxg-OPnnpZ2yerg==/lib/arm64 flags = 0]
SoSource 2: com.facebook.soloader.DirectorySoSource[root = /system/lib64 flags = 2]
SoSource 3: com.facebook.soloader.DirectorySoSource[root = /vendor/lib64 flags = 2]
Native lib dir: /data/app/~~vccykcNnSseE2lbdU59CjA==/###-tIZ_hFLpxg-OPnnpZ2yerg==/lib/arm64
result: 0
Version
0.70.1
Output of npx react-native info
abhi@abhi-Latitude-3480:~/workspace/react-native/###-mobile-app/android$ npx react-native --version
6.1.0
abhi@abhi-Latitude-3480:~/workspace/react-native/###-mobile-app/android$ npx react-native info
info Fetching system and libraries information...
System:
OS: Linux 5.15 Ubuntu 20.04.5 LTS (Focal Fossa)
CPU: (4) x64 Intel(R) Core(TM) i5-7200U CPU @ 2.50GHz
Memory: 1.36 GB / 11.40 GB
Shell: 5.0.17 - /bin/bash
Binaries:
Node: 16.17.1 - ~/.nvm/versions/node/v16.17.1/bin/node
Yarn: 1.22.19 - ~/workspace/react-native/###-mobile-app/node_modules/.bin/yarn
npm: 8.15.0 - ~/.nvm/versions/node/v16.17.1/bin/npm
Watchman: Not Found
SDKs:
Android SDK: Not Found
IDEs:
Android Studio: Not Found
Languages:
Java: 11.0.16 - /usr/bin/javac
npmPackages:
@react-native-community/cli: Not Found
react: Not Found
react-native: Not Found
npmGlobalPackages:
react-native: Not Found
Steps to reproduce
Actually doing this below link steps to run the React Native Library in Native Android Application
link is : https://medium.com/@jyubinpatel/make-reactnative-module-as-a-library-and-how-its-used-into-android-native-application-35b13f65ac7c
Snack, code example, screenshot, or link to a repository
Error :   E  App has crashed
java.lang.UnsatisfiedLinkError: couldn't find DSO to load: libhermes.so
SoSource 0: com.facebook.soloader.ApkSoSource[root = /data/data/###/lib-main flags = 1]
SoSource 1: com.facebook.soloader.DirectorySoSource[root = /data/app/~~vccykcNnSseE2lbdU59CjA==/###-tIZ_hFLpxg-OPnnpZ2yerg==/lib/arm64 flags = 0]
SoSource 2: com.facebook.soloader.DirectorySoSource[root = /system/lib64 flags = 2]
SoSource 3: com.facebook.soloader.DirectorySoSource[root = /vendor/lib64 flags = 2]
Native lib dir: /data/app/~~vccykcNnSseE2lbdU59CjA==/###-tIZ_hFLpxg-OPnnpZ2yerg==/lib/arm64
result: 0

Can anyone share the source code of the completed framework and sample application. It would help me greatly.

Can you share your build.gradle file? Also are you using variants?

Can you share your build.gradle file?

I had the same experience when I upgraded from 0.67.5 to 0.70.6 and was able to solve it after struggling for some time.
In my case, the app crashes only when hermes is enabled.
And in fact, turned out libhermes.so is actually missing from my APK.
You can open the APK using Android Studio and look under lib directory
(Or you can also check under android/app/build/intermediates/merged_native_libs/debug/out/arm64-v8a/ and look for libhermes.so. Faster than opening the APK everytime using Android Studio).
After some digging, I found out that the following script ./node_modules/react-native/react.gradle is receiving enableHermes value as false, even though it's set to true in my app/build.gradle, and there's also a new cleanup task in that script which removes unneeded libraries from the final package, and thus, removing libhermes.so
Check here
Turned out the problem was that I'm applying react.gradle script in my app/build.gradle BEFORE setting react config!
So I moved the react.gradle statement after project.ext.react, cleaned the project, ran a new build and problem solved.
Like this:
project.ext.react = [
    enableHermes: true, // Clean and Rebuild if Changed
    bundleInDebug: false,
    bundleInRelease: true,
    extraPackagerArgs: []
]

/**
 * The script "react.gradle" is using properties defined in the exported "project.react" object.
 * So please always make sure it's applied after "project.react" is defined.
*/
apply from: "../../node_modules/react-native/react.gradle"

Don't forget to run ./gradlew clean before building again.

I had the same experience when I upgraded from 0.67.5 to 0.70.6 and was able to solve it after struggling for some time.

We resolved this and all the "couldn't find DSO to load" crashes in version 0.71 of React Native. The issues were caused by a too aggressive cleanup logic which was attempting to remove too many libraries.
I'm closing this issue as the resolution is available for public usage in 0.71

@cortinico, we seeing this on all our customers with devices running Android 10, we can't move to 0.71 yet due to depending on a few modules from Expo, any chance of a patch to 0.70?

any chance there's a way to patch this for 0.70

Sadly not as this required a significant rework of the internals. If the issue persists on 0.71, we can keep a look at it and fix it furhter


Could not load type 'Microsoft.AspNetCore.Http.Internal.BufferingHelper

I have installed this package, and it works well thanks!
I have this issue though where a lot of unit tests are failing with this error:
System.TypeLoadException : Could not load type 'Microsoft.AspNetCore.Http.Internal.BufferingHelper' from assembly 'Microsoft.AspNetCore.Http, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=adb9793829ddae60'.
I am using netcoreapp3.1 framework, and don't really understand how your package causes this issue since there are no dependencies, however when I remove your package its fine again.
Any help appreciated.

That's strange. I've never seen such an error with the library. I'm not aware of referencing those libraries. The library does depend on HttpClient https://github.com/TimothyMeadows/reCAPTCHA.AspNetCore/blob/master/reCAPTCHA.AspNetCore/RecaptchaService.cs#L12 but that's the only requirement for http that exists that i am aware of.
There may be a specific configuration in your environment that has internal buffering disabled for httpclient?

Its really weird, I can't figure it out, and don't know enough about the new Microsoft.AspNetCore.Http library to know.
I have tried adding Framework reference in both main and test project with no luck:
  <ItemGroup>
    <FrameworkReference Include="Microsoft.AspNetCore.App" />
  </ItemGroup>

Why do you need to use Microsoft.AspNetCore.Http though? the code you showed me uses HttpClient from System.Net.Http.  Just wondered if you needed it at all?

The project doesn't reference it directly. Quick google search show it's part of HttpRequest maybe? It seems like you have unique environment / requirements which falls on you to satisfy. This is not a general problem or error or it would be felt by the many projects that depend on this library. Though i will leave this issue up for anyone else that might have more information that might help.

@TimothyMeadows thanks for the feedback.
Looks like issue was in one of the packages I was referencing.  It used ReadAsStringAsync() an extension for HttpRequest, that I guess is not compatible with 3.1 or some issue.
This helped:
https://stackoverflow.com/questions/59466227/could-not-load-type-microsoft-aspnetcore-http-internal-bufferinghelper-from-as
Basically changing that method from using request.EnableRewind to request.EnableBuffering() sorted it.
I am still not sure why your package caused the issue (perhaps it forced 3.1 AspNetCore, where as it was falling back to previous version before.  Nuget/DLL hell!
Anyway hope this helps someone..

Interesting indeed. Closing this now, will point others to it if they run into the same issue.


CLOUD-544 Use version service

Test name
Status

Test name
Status

Test name
Status

init-deploy
failed

recreate
failed

scaling
failed

big-data
failed

storage
failed

scaling-proxysql
failed

restore-to-encrypted-cluster
failed

limits
failed

upgrade
failed

self-healing
failed

monitoring
failed

upgrade-consistency
failed

self-healing-advanced
failed

demand-backup
failed

security-context
failed

monitoring-2-0
failed

affinity
failed

scheduled-backup
failed

demand-backup-encrypted-with-tls
failed

one-pod
failed

auto-tuning
failed

operator-self-healing
failed

proxysql-sidecar-res-limits
failed

Test name
Status

Test name
Status

scaling
failed

big-data
failed

init-deploy
failed

storage
failed

recreate
failed

limits
failed

restore-to-encrypted-cluster
failed

self-healing
failed

scaling-proxysql
failed

self-healing-advanced
failed

upgrade
passed

demand-backup
failed

monitoring
failed

operator-self-healing
failed

scheduled-backup
failed

monitoring-2-0
failed

demand-backup-encrypted-with-tls
failed

affinity
failed

one-pod
failed

upgrade-consistency
passed

security-context
failed

auto-tuning
failed

proxysql-sidecar-res-limits
failed

Test name
Status

init-deploy
failed

scaling
failed

storage
failed

recreate
failed

big-data
failed

self-healing
failed

limits
failed

scaling-proxysql
failed

self-healing-advanced
failed

restore-to-encrypted-cluster
failed

monitoring
failed

operator-self-healing
failed

demand-backup
failed

upgrade
failed

monitoring-2-0
failed

scheduled-backup
failed

demand-backup-encrypted-with-tls
failed

affinity
passed

one-pod
failed

auto-tuning
failed

proxysql-sidecar-res-limits
failed

upgrade-consistency
failed

Test name
Status

init-deploy
failed

recreate
failed

big-data
failed

storage
failed

scaling
failed

self-healing
failed

scaling-proxysql
failed

restore-to-encrypted-cluster
failed

upgrade
passed

self-healing-advanced
failed

demand-backup
failed

limits
passed

operator-self-healing
failed

scheduled-backup
failed

demand-backup-encrypted-with-tls
failed

monitoring
failed

upgrade-consistency
passed

security-context
failed

monitoring-2-0
failed

affinity
passed

one-pod
failed

auto-tuning
failed

proxysql-sidecar-res-limits
failed

Test name
Status

big-data
failed

storage
passed

init-deploy
failed

scaling
failed

recreate
passed

self-healing
failed

scaling-proxysql
passed

limits
passed

self-healing-advanced
failed

upgrade
failed

operator-self-healing
failed

monitoring
passed

upgrade-consistency
passed

restore-to-encrypted-cluster
failed

security-context
failed

demand-backup
failed

monitoring-2-0
passed

affinity
passed

one-pod
failed

scheduled-backup
failed

auto-tuning
passed

demand-backup-encrypted-with-tls
failed

proxysql-sidecar-res-limits
passed

Test name
Status

storage
passed

big-data
failed

init-deploy
failed

recreate
passed

scaling
failed

limits
passed

self-healing
failed

monitoring
passed

scaling-proxysql
failed

restore-to-encrypted-cluster
failed

upgrade
passed

self-healing-advanced
passed

demand-backup
failed

monitoring-2-0
passed

operator-self-healing
failed

upgrade-consistency
passed

security-context
failed

affinity
passed

one-pod
failed

scheduled-backup
failed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

demand-backup-encrypted-with-tls
failed

Test name
Status

scaling
failed

init-deploy
failed

recreate
failed

big-data
failed

storage
passed

limits
failed

scaling-proxysql
passed

self-healing
failed

monitoring
failed

upgrade
failed

restore-to-encrypted-cluster
failed

self-healing-advanced
passed

demand-backup
failed

upgrade-consistency
passed

monitoring-2-0
failed

security-context
failed

scheduled-backup
failed

operator-self-healing
passed

affinity
passed

one-pod
failed

auto-tuning
failed

proxysql-sidecar-res-limits
failed

demand-backup-encrypted-with-tls
failed

Test name
Status

init-deploy
failed

big-data
failed

scaling
failed

storage
passed

recreate
passed

limits
passed

scaling-proxysql
failed

monitoring
passed

self-healing
failed

monitoring-2-0
passed

restore-to-encrypted-cluster
failed

upgrade
failed

self-healing-advanced
passed

demand-backup
failed

affinity
passed

operator-self-healing
passed

upgrade-consistency
passed

security-context
failed

one-pod
failed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

scheduled-backup
failed

demand-backup-encrypted-with-tls
failed

Test name
Status

init-deploy
failed

scaling
passed

recreate
passed

big-data
failed

storage
failed

self-healing
failed

scaling-proxysql
passed

limits
passed

upgrade
passed

restore-to-encrypted-cluster
failed

self-healing-advanced
passed

upgrade-consistency
passed

monitoring
passed

security-context
failed

demand-backup
failed

monitoring-2-0
passed

operator-self-healing
passed

affinity
passed

one-pod
failed

auto-tuning
failed

scheduled-backup
failed

proxysql-sidecar-res-limits
failed

demand-backup-encrypted-with-tls
failed

Test name
Status

init-deploy
passed

big-data
failed

limits
passed

monitoring
passed

monitoring-2-0
passed

affinity
passed

one-pod
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

Test name
Status

init-deploy
passed

recreate
passed

scaling
passed

storage
passed

big-data
failed

scaling-proxysql
passed

self-healing
passed

limits
passed

monitoring
passed

upgrade
failed

restore-to-encrypted-cluster
failed

self-healing-advanced
passed

monitoring-2-0
failed

affinity
passed

operator-self-healing
passed

one-pod
passed

demand-backup
passed

auto-tuning
passed

proxysql-sidecar-res-limits
passed

scheduled-backup
passed

demand-backup-encrypted-with-tls
failed

upgrade-consistency
failed

Test name
Status

scaling
failed

recreate
failed

big-data
failed

init-deploy
failed

storage
failed

scaling-proxysql
failed

limits
passed

upgrade
failed

restore-to-encrypted-cluster
failed

monitoring
failed

demand-backup
failed

self-healing
failed

monitoring-2-0
failed

scheduled-backup
failed

self-healing-advanced
failed

affinity
passed

operator-self-healing
failed

demand-backup-encrypted-with-tls
failed

one-pod
passed

auto-tuning
failed

proxysql-sidecar-res-limits
failed

upgrade-consistency
failed

Test name
Status

init-deploy
failed

recreate
failed

storage
failed

big-data
failed

scaling
failed

restore-to-encrypted-cluster
failed

self-healing
failed

limits
passed

demand-backup
failed

scaling-proxysql
failed

self-healing-advanced
failed

operator-self-healing
failed

upgrade
failed

monitoring
failed

monitoring-2-0
failed

scheduled-backup
failed

affinity
passed

demand-backup-encrypted-with-tls
failed

one-pod
passed

auto-tuning
failed

proxysql-sidecar-res-limits
failed

upgrade-consistency
failed

Test name
Status

storage
failed

recreate
passed

init-deploy
passed

scaling
failed

big-data
passed

self-healing
passed

limits
passed

restore-to-encrypted-cluster
passed

scaling-proxysql
passed

monitoring
passed

upgrade
passed

demand-backup
passed

monitoring-2-0
passed

self-healing-advanced
failed

upgrade-consistency
passed

security-context
passed

affinity
passed

operator-self-healing
passed

one-pod
passed

scheduled-backup
failed

auto-tuning
passed

demand-backup-encrypted-with-tls
passed

proxysql-sidecar-res-limits
passed

Test name
Status

init-deploy
passed

scaling
failed

recreate
passed

storage
passed

big-data
passed

scaling-proxysql
passed

self-healing
passed

limits
passed

monitoring
passed

restore-to-encrypted-cluster
passed

upgrade
passed

self-healing-advanced
passed

upgrade-consistency
passed

security-context
passed

monitoring-2-0
passed

operator-self-healing
passed

demand-backup
passed

affinity
passed

one-pod
passed

auto-tuning
failed

scheduled-backup
passed

proxysql-sidecar-res-limits
failed

demand-backup-encrypted-with-tls
passed

Test name
Status

init-deploy
failed

scaling
passed

big-data
passed

storage
passed

recreate
failed

limits
failed

self-healing
failed

restore-to-encrypted-cluster
passed

scaling-proxysql
passed

self-healing-advanced
failed

operator-self-healing
passed

upgrade
passed

monitoring
passed

upgrade-consistency
passed

security-context
passed

monitoring-2-0
passed

demand-backup
failed

scheduled-backup
failed

affinity
passed

one-pod
failed

demand-backup-encrypted-with-tls
failed

auto-tuning
passed

proxysql-sidecar-res-limits
passed


archive failed

New Issue Checklist

[x] Updated fastlane to the latest version
[x] I read the Contribution Guidelines
[x] I read docs.fastlane.tools
[x] I searched for existing GitHub issues

Issue Description
My project uses the dlib library, using Xcode package can be successful, but the use of fastlane archive failed, suggesting Invalid bitcode signature error. I dlib removed can be packaged with fastlane success. dlib static library is a real machine release version.
Complete output when running fastlane, including the stack trace and command used

[INSERT OUTPUT HERE]
Environment

[INSERT OUTPUT HERE]
cd /Users/home_taonix/Desktop/v1.2
export IPHONEOS_DEPLOYMENT_TARGET=9.1
export PATH="/Applications/Xcode.app/Contents/Developer/Platforms/iPhoneOS.platform/Developer/usr/bin:/Applications/Xcode.app/Contents/Developer/usr/bin:/usr/local/bin:/usr/bin:/bin:/usr/sbin:/sbin"

@codergelly Heyyy 👋 Sorry about the late reply! I know you tried setting include_bitcode with build app but have you tried setting Bitcode to ‘NO’ in the Build Settings? Don't know if this would help since I've never tried to include dlib in a project but just curious if that would work 🤔


🐛 Why Camera preview is a black screen?

What's happening?
Hi 👋,
first of all, I want to thank you @mrousavy in advance for your incredible work! 👏
Now my question: why I'm getting a black screen when app starts?
package.json
{
  "name": "visioncamera",
  "version": "1.0.0",
  "main": "node_modules/expo/AppEntry.js",
  "scripts": {
    "start": "expo start",
    "android": "expo start --android",
    "ios": "expo start --ios",
    "web": "expo start --web"
  },
  "dependencies": {
    "@types/react": "~18.2.14",
    "expo": "~49.0.12",
    "expo-dev-client": "~2.4.11",
    "expo-status-bar": "~1.6.0",
    "react": "18.2.0",
    "react-native": "0.72.5",
    "react-native-vision-camera": "^3.1.0",
    "react-native-worklets-core": "^0.2.0",
    "typescript": "^5.1.3"
  },
  "devDependencies": {
    "@babel/core": "^7.20.0"
  },
  "private": true
}

Reproduceable Code
import { Camera, getCameraFormat, useCameraDevice, useFrameProcessor } from 'react-native-vision-camera';
import { useEffect } from 'react';
import { StyleSheet, Text, View } from 'react-native';
import { StatusBar } from 'expo-status-bar';

export default function App() {
	const device = useCameraDevice('back');

	useEffect(() => {
		const cameraPermissions = async () => {
			const cameraPermission = await Camera.getCameraPermissionStatus();
			console.log("cameraPermission", cameraPermission);
			await Camera.requestCameraPermission();
		};

		cameraPermissions();
	}, []);

	if (device == null) return <View style={{ flex: 1, justifyContent: 'center', alignItems: 'center' }}><Text>Loading...</Text></View>

	return (
		<>
			<StatusBar style='light' />
			<Camera
				style={StyleSheet.absoluteFill}
				device={device}
				isActive={true}
			/>
		</>
	);
}

Relevant log output
09-26 13:35:18.077 26277 26277 D ApkSoSource: not allowing consideration of lib/arm64-v8a/libVisionCamera.so: deferring to libdir
09-26 13:35:40.324 26277 26643 I VisionCameraProxy: Initializing VisionCameraProxy...
09-26 13:35:40.324 26277 26643 I VisionCameraProxy: Creating Worklet Context...
09-26 13:35:40.330 26277 26643 I VisionCameraProxy: Worklet Context created!

Camera Device
{
  "sensorOrientation": "landscape-right",
  "hardwareLevel": "full",
  "maxZoom": 8,
  "minZoom": 1,
  "supportsLowLightBoost": false,
  "neutralZoom": 1,
  "physicalDevices": [
    "wide-angle-camera"
  ],
  "supportsFocus": true,
  "supportsRawCapture": true,
  "isMultiCam": false,
  "name": "BACK (0)",
  "hasFlash": true,
  "hasTorch": true,
  "position": "back",
  "id": "0"
}

Device
RedMi Note 7 - MIUI Global 12.5.1
Android 10 QKQ1.190910.002
VisionCamera Version
3.1.0
Can you reproduce this issue in the VisionCamera Example app?
No, I cannot reproduce the issue in the Example app
Additional information

[X] I am using Expo
[X] I have enabled Frame Processors (react-native-worklets-core)
[X] I have read the Troubleshooting Guide
[X] I agree to follow this project's Code of Conduct
[X] I searched for similar issues in this repository and found none.

Hey! Thanks man.
This sounds like a classic android issue. Can you try commenting out line by line here and see what makes it fail? https://github.com/mrousavy/react-native-vision-camera/blob/fb6ebd9ee1b831ce1c2e0b42d123257f5f9c5459/package/android/src/main/java/com/mrousavy/camera/core/CameraSession.kt#L461-L492

Ehi! Thanks for the kind reply.
I'm pretty new here so can you guide me a little bit more? I am in an Expo project, so, if I've understood well, I have to do:

Find CameraSession.kt file into node_modules/react-native-vision-camera package
Starting to comment first couple of lines (eg: 462 and 463 for FPS)
Launch a new build using EAS CLI in order to generate a new expo dev client .APK
Run it and test
Iterate for all lines

Is it right?
Thank you 👋

Hey - yep!
I don't know how it'd work in Expo, but I guess that's how you do it yea.
Runnjng yarn android won't rebuild, does it? cc @EvanBacon

Unfortunately my proposal does not work! 😭 The command eas build command triggers a pipeline in the cloud witch download fresh node_modules remotely, ignoring my local edits with commented lines (of course! 😓).
I've tried to build locally as well but I got strange errors such as:

I'm stuck! Any suggestions ?

Hey!
If the issue is still there after commenting all lines in there then I haven't seen it before.
I need the full adb logcat output, and a way to reproduce (but I don't have that phone)

@mrousavy i took the time to debug this issue, it's only happening on android 10 and less so in the code we need to adapt in two places => preview (CameraSession) & photoCapture (CameraDevice+createPhotoCaptureRequest) and the issue is related to the Zoom utility you have created, it's changing the coordinates of the Rect even if zoom == 1.0f so i have tested with a small if to resolve it, and now it's working, but the zoom is broken here's what i have done
@pepperav FYI
      val cameraCharacteristics = cameraManager.getCameraCharacteristics(cameraId!!)       val size = cameraCharacteristics.get(CameraCharacteristics.SENSOR_INFO_ACTIVE_ARRAY_SIZE)!!       if (zoom != 1.0f) {         captureRequest.set(CaptureRequest.SCALER_CROP_REGION, size.zoomed(zoom))       } else {         captureRequest.set(CaptureRequest.SCALER_CROP_REGION, size)       }

ehi! tnx @idrissakhi for your insight! 🏆
I have updated CameraSession.kt file with your tip:
    // Zoom
    if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.R) {
      captureRequest.set(CaptureRequest.CONTROL_ZOOM_RATIO, zoom)
    } else {
      val cameraCharacteristics = cameraManager.getCameraCharacteristics(cameraId!!)
      val size = cameraCharacteristics.get(CameraCharacteristics.SENSOR_INFO_ACTIVE_ARRAY_SIZE)!!

      //captureRequest.set(CaptureRequest.SCALER_CROP_REGION, size.zoomed(zoom))

      if (zoom != 1.0f) {
        captureRequest.set(CaptureRequest.SCALER_CROP_REGION, size.zoomed(zoom))
      } else {
        captureRequest.set(CaptureRequest.SCALER_CROP_REGION, size)
      }
    }

But the black screen on preview is still there 😓.
Am I miss something else?
@mrousavy I'm going to save the full adb logcat

@pepperav you have a black screen after taking a picture ? if it's the case you need to do the same thing on CameraDevice+createPhotoCaptureRequest line 93
captureRequest.set(CaptureRequest.SCALER_CROP_REGION, size.zoomed(zoom))

@pepperav you have a black screen after taking a picture ? if it's the case you need to do the same thing on CameraDevice+createPhotoCaptureRequest line 93
captureRequest.set(CaptureRequest.SCALER_CROP_REGION, size.zoomed(zoom))

nop, always! Since the app is started (all permissions granted), in the preview of camera...check my App.tsx file

Here the full log. Hope it should be enough to understand the issue
black_screen_log.txt

It worked for me by commenting line 487. How can it be resolved? Do I need to use patch-package?
    // Zoom
    if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.R) {
      captureRequest.set(CaptureRequest.CONTROL_ZOOM_RATIO, zoom)
    } else {
      val cameraCharacteristics = cameraManager.getCameraCharacteristics(cameraId!!)
      val size = cameraCharacteristics.get(CameraCharacteristics.SENSOR_INFO_ACTIVE_ARRAY_SIZE)!!
      // --> captureRequest.set(CaptureRequest.SCALER_CROP_REGION, size.zoomed(zoom))
    }

I'm coming from version 2.15.4 to 3.1.0 hoping to resolve the error java.lang.IllegalStateException - Surface was requested when the Recorder had encountered error c.c.a.l1.l: c.c.a.l1.o.a1: Encoder cannot created :null which was a crash happening on some devices, but I still don't know if it's stable enough to make the change.
Device
Motorola G8 Plus - Android 10
VisionCamera Version
3.1.0
Can you reproduce this issue in the VisionCamera Example app?
No, I cannot reproduce the issue in the Example app
Additional information

[ ] I am using Expo
[ ] I have enabled Frame Processors (react-native-worklets-core)
[x] I have read the Troubleshooting Guide
[x] I agree to follow this project's Code of Conduct
[x] I searched for similar issues in this repository and found none.

It worked for me by commenting line 487. How can it be resolved? Do I need to use patch-package?
    // Zoom
    if (Build.VERSION.SDK_INT >= Build.VERSION_CODES.R) {
      captureRequest.set(CaptureRequest.CONTROL_ZOOM_RATIO, zoom)
    } else {
      val cameraCharacteristics = cameraManager.getCameraCharacteristics(cameraId!!)
      val size = cameraCharacteristics.get(CameraCharacteristics.SENSOR_INFO_ACTIVE_ARRAY_SIZE)!!
      // --> captureRequest.set(CaptureRequest.SCALER_CROP_REGION, size.zoomed(zoom))
    }

I'm coming from version 2.15.4 to 3.1.0 hoping to resolve the error java.lang.IllegalStateException - Surface was requested when the Recorder had encountered error c.c.a.l1.l: c.c.a.l1.o.a1: Encoder cannot created :null which was a crash happening on some devices, but I still don't know if it's stable enough to make the change.
Device
Motorola G8 Plus - Android 10
VisionCamera Version
3.1.0
Can you reproduce this issue in the VisionCamera Example app?
No, I cannot reproduce the issue in the Example app
Additional information

[ ]  I am using Expo
[ ]  I have enabled Frame Processors (react-native-worklets-core)
[x]  I have read the Troubleshooting Guide
[x]  I agree to follow this project's Code of Conduct
[x]  I searched for similar issues in this repository and found none.

I've tried commenting line 487 but I get always black screen 😓

@pepperav you need to add formats for android =>
<AnimatedCamera
testID={${testID}}
ref={cameraRef}
style={styles.cameraView}
device={device}
isActive={isActive}
photo
animatedProps={animatedProps}
orientation="portrait"
{...(isAndroid && { format: format })}
/>

Ehi @idrisssakhi , thanks but nothing happens.
Check my code below:
import { Camera, useCameraDevice, useCameraFormat, useFrameProcessor } from 'react-native-vision-camera';
import { useEffect, useRef } from 'react';
import { Platform, StyleSheet, Text, TouchableOpacity, View } from 'react-native';
import { StatusBar } from 'expo-status-bar';

export default function App() {
	const device = useCameraDevice('back');

	const camera = useRef<Camera>(null);

	const format = useCameraFormat(device, [
		{ videoResolution: 'max' },
  		{ photoResolution: 'max' },
  		{ fps: 30 }
	]);

	useEffect(() => {
		const cameraPermissions = async () => {
			const cameraPermission = await Camera.getCameraPermissionStatus();
			console.log("cameraPermission", cameraPermission);
			await Camera.requestCameraPermission();

			const microphonePermission = await Camera.getMicrophonePermissionStatus();
			console.log("microphonePermission", microphonePermission);
			await Camera.requestMicrophonePermission();
		};

		cameraPermissions();
	}, []);

	if (device == null)
		return
			<View style={styles.flexCenter}>
				<Text style={{ fontSize: 16 }}>⌛ Loading...</Text>
			</View>

	return (
		<>
			<StatusBar style='light' />

			<Camera
				ref={camera}
				style={StyleSheet.absoluteFill}
				device={device}
				isActive={true}
				photo
				{ ...(Platform.OS === 'android' && { format }) }
			/>
		</>
	);
};

const styles = StyleSheet.create({
	flexCenter: {
		flex: 1,
		justifyContent: 'center',
		alignItems: 'center'
	}
});

Hey!
Quick update: I think there could be four problems here:

You are using a limited/legacy device, and use Preview (always on), photo and video/frameProcessor outputs (3 outputs) which are by default at maximum resolution. LIMITED/LEGACY devices might not support full-resolution streaming, see the Android capture session documentation on supported configuration maps.
We need PRIV PREVIEW + YUV/PRIV RECORD + JPEG MAXIMUM. anything lower, needs to be explicitly handled by me, but I can easily add that no problemo. I just need the device to test it on.

What you can do: Try disabling photo, video and frameProcessor and check if that works. If only PREVIEW is attached, everything should work.
We are using some setting in the Capture Request that is not supported (e.g. FPS, HDR, Zoom, ...) but we don't previously check if those settings are supported on the device. I can easily add some checks here, so that the Camera doesn't just swallow any errors and fails silently, but instead throws and says something like "60 FPS is not supported on this device". https://github.com/mrousavy/react-native-vision-camera/blob/fb6ebd9ee1b831ce1c2e0b42d123257f5f9c5459/package/android/src/main/java/com/mrousavy/camera/core/CameraSession.kt#L461-L492
What you can do: Try disabling each line in getPreviewCaptureRequest and see what happens. I've heard zoom is often the cause.
Some manufacturers (cough* cough Samsung) explicitly say they support something (e.g. 60 FPS), but then don't support it and just swallow errors and show blackscreens when trying to use it.
What you can do: Also try other steps here and remove code by code to see what it is. Maybe also browse similar issues in the CameraX issue tracker or StackOverflow to see if someone had similar issues, explicitly by searching for your device.
There could be some synchronization issue. I can try to make everything fully atomic so nothing ever goes out of sync with mutexes. This is pretty tricky, but I'll do it

Tnx @mrousavy  for your full detailed response 🙏. I will do some tries but, as you said, this device is too old! I will move to another one (a Samsung Galaxy J7 - Android 9) which seems more promising.

I'm going to paste the camera2-probe report for both my Android devices. Do you see some helpful info?
Model:Redmi Note 7
Manufacturer:Xiaomi
Build:10
SDK:29
------------------------------------------
Camera ID: 0
Camera Facing: BACK
Hardware Support Level:LEVEL_3
Manual exposure:1
Auto exposure:1
Auto exposure, always flash:1
Auto exposure, auto flash:1
Auto exposure, auto flash, red eye reduction:1
AE Lock:1
Compensation Range: [-24, 24]
Compensation Step: 1/6
Target FPS  Range: [15, 15]
Target FPS  Range: [20, 20]
Target FPS  Range: [24, 24]
Target FPS  Range: [7, 30]
Target FPS  Range: [30, 30]
Manual focus:1
Auto focus:1
Auto focus macro:1
Auto focus continuous picture:1
Auto focus continuous video:1
Auto focus EDOF:0
White balance off:1
Automatic white balance:1
WB: cloudy day:1
WB: daylight:1
WB: fluorescent:1
WB: incandescent:1
WB: shade:1
WB: twilight:1
WB: warm fluorescent:1
AWB Lock:1
RawCapture:1
BurstCapture:1
availableCapability: BACKWARD_COMPATIBLE
availableCapability: MANUAL_SENSOR
availableCapability: MANUAL_POST_PROCESSING
availableCapability: READ_SENSOR_SETTINGS
availableCapability: BURST_CAPTURE
availableCapability: PRIVATE_REPROCESSING
availableCapability: YUV_REPROCESSING
availableCapability: CONSTRAINED_HIGH_SPEED_VIDEO
availableCapability: RAW
Stabilization Mode: Video
previewSize: 4000 * 3000 (4:3)
previewSize: 4000 * 2250 (16:9)
previewSize: 4000 * 1844 (1000:461)
previewSize: 3840 * 2160 (16:9)
previewSize: 2592 * 1944 (4:3)
previewSize: 2340 * 1080 (13:6)
previewSize: 2048 * 1536 (4:3)
previewSize: 1920 * 1080 (16:9)
previewSize: 1600 * 1200 (4:3)
previewSize: 1440 * 1080 (4:3)
previewSize: 1440 * 720 (2:1)
previewSize: 1280 * 960 (4:3)
previewSize: 1280 * 768 (5:3)
previewSize: 1280 * 720 (16:9)
previewSize: 1280 * 480 (8:3)
previewSize: 1280 * 400 (16:5)
previewSize: 800 * 480 (5:3)
previewSize: 720 * 480 (3:2)
previewSize: 640 * 480 (4:3)
previewSize: 480 * 640 (4:3)
previewSize: 480 * 360 (4:3)
previewSize: 480 * 320 (3:2)
previewSize: 352 * 288 (11:9)
previewSize: 320 * 240 (4:3)
previewSize: 240 * 320 (4:3)
previewSize: 176 * 144 (11:9)
previewSize: 144 * 176 (11:9)
photoSize: 4000 * 3000 (4:3)
photoSize: 4000 * 2250 (16:9)
photoSize: 4000 * 1844 (1000:461)
photoSize: 3840 * 2160 (16:9)
photoSize: 2592 * 1944 (4:3)
photoSize: 2340 * 1080 (13:6)
photoSize: 2048 * 1536 (4:3)
photoSize: 1920 * 1080 (16:9)
photoSize: 1600 * 1200 (4:3)
photoSize: 1440 * 1080 (4:3)
photoSize: 1440 * 720 (2:1)
photoSize: 1280 * 960 (4:3)
photoSize: 1280 * 768 (5:3)
photoSize: 1280 * 720 (16:9)
photoSize: 1280 * 480 (8:3)
photoSize: 1280 * 400 (16:5)
photoSize: 800 * 480 (5:3)
photoSize: 720 * 480 (3:2)
photoSize: 640 * 480 (4:3)
photoSize: 480 * 640 (4:3)
photoSize: 480 * 360 (4:3)
photoSize: 480 * 320 (3:2)
photoSize: 352 * 288 (11:9)
photoSize: 320 * 240 (4:3)
photoSize: 240 * 320 (4:3)
photoSize: 176 * 144 (11:9)
photoSize: 144 * 176 (11:9)
videoSize: 4000 * 3000 (4:3)
videoSize: 4000 * 2250 (16:9)
videoSize: 4000 * 1844 (1000:461)
videoSize: 3840 * 2160 (16:9)
videoSize: 2592 * 1944 (4:3)
videoSize: 2340 * 1080 (13:6)
videoSize: 2048 * 1536 (4:3)
videoSize: 1920 * 1080 (16:9)
videoSize: 1600 * 1200 (4:3)
videoSize: 1440 * 1080 (4:3)
videoSize: 1440 * 720 (2:1)
videoSize: 1280 * 960 (4:3)
videoSize: 1280 * 768 (5:3)
videoSize: 1280 * 720 (16:9)
videoSize: 1280 * 480 (8:3)
videoSize: 1280 * 400 (16:5)
videoSize: 800 * 480 (5:3)
videoSize: 720 * 480 (3:2)
videoSize: 640 * 480 (4:3)
videoSize: 480 * 640 (4:3)
videoSize: 480 * 360 (4:3)
videoSize: 480 * 320 (3:2)
videoSize: 352 * 288 (11:9)
videoSize: 320 * 240 (4:3)
videoSize: 240 * 320 (4:3)
videoSize: 176 * 144 (11:9)
videoSize: 144 * 176 (11:9)

Model:SM-J730F
Manufacturer:samsung
Build:9
SDK:28
------------------------------------------
Camera ID: 0
Camera Facing: BACK
Hardware Support Level:LIMITED
Manual exposure:1
Auto exposure:1
Auto exposure, always flash:1
Auto exposure, auto flash:1
Auto exposure, auto flash, red eye reduction:0
AE Lock:1
Compensation Range: [-20, 20]
Compensation Step: 1/10
Target FPS  Range: [7, 7]
Target FPS  Range: [15, 15]
Target FPS  Range: [24, 24]
Target FPS  Range: [8, 30]
Target FPS  Range: [10, 30]
Target FPS  Range: [15, 30]
Target FPS  Range: [30, 30]
Manual focus:1
Auto focus:1
Auto focus macro:1
Auto focus continuous picture:1
Auto focus continuous video:1
Auto focus EDOF:0
White balance off:1
Automatic white balance:1
WB: cloudy day:1
WB: daylight:1
WB: fluorescent:1
WB: incandescent:1
WB: shade:0
WB: twilight:0
WB: warm fluorescent:0
AWB Lock:1
RawCapture:1
BurstCapture:1
availableCapability: BACKWARD_COMPATIBLE
previewSize: 4128 * 3096 (4:3)
previewSize: 4128 * 2322 (16:9)
previewSize: 3264 * 2448 (4:3)
previewSize: 3264 * 1836 (16:9)
previewSize: 3088 * 3088 (1:1)
previewSize: 2048 * 1536 (4:3)
previewSize: 2048 * 1152 (16:9)
previewSize: 1920 * 1080 (16:9)
previewSize: 1280 * 720 (16:9)
previewSize: 960 * 720 (4:3)
previewSize: 720 * 480 (3:2)
previewSize: 640 * 480 (4:3)
previewSize: 352 * 288 (11:9)
previewSize: 320 * 240 (4:3)
previewSize: 256 * 144 (16:9)
previewSize: 176 * 144 (11:9)
photoSize: 4128 * 3096 (4:3)
photoSize: 4128 * 2322 (16:9)
photoSize: 3264 * 2448 (4:3)
photoSize: 3264 * 1836 (16:9)
photoSize: 3088 * 3088 (1:1)
photoSize: 2048 * 1536 (4:3)
photoSize: 2048 * 1152 (16:9)
photoSize: 1920 * 1080 (16:9)
photoSize: 1280 * 720 (16:9)
photoSize: 960 * 720 (4:3)
photoSize: 720 * 480 (3:2)
photoSize: 640 * 480 (4:3)
photoSize: 352 * 288 (11:9)
photoSize: 320 * 240 (4:3)
photoSize: 256 * 144 (16:9)
photoSize: 176 * 144 (11:9)
videoSize: 4128 * 3096 (4:3)
videoSize: 4128 * 2322 (16:9)
videoSize: 3264 * 2448 (4:3)
videoSize: 3264 * 1836 (16:9)
videoSize: 3088 * 3088 (1:1)
videoSize: 2048 * 1536 (4:3)
videoSize: 2048 * 1152 (16:9)
videoSize: 1920 * 1080 (16:9)
videoSize: 1280 * 720 (16:9)
videoSize: 960 * 720 (4:3)
videoSize: 720 * 480 (3:2)
videoSize: 640 * 480 (4:3)
videoSize: 352 * 288 (11:9)
videoSize: 320 * 240 (4:3)
videoSize: 256 * 144 (16:9)
videoSize: 176 * 144 (11:9)

Hey! Can anyone try with VisionCamera 3.4.1. and see if the issue still persists? Thanks!

Sure!  Thanks

Awesome! If you appreciate my work please consider sponsoring me on GitHub to say thanks.


ExternalLibrary.dispatch E.O2.default performance problem

From @umuro, earlier:
Much of the slowness comes from the function:
The major problem is @ src/rescript/ReducerInterface/ReducerInterface_ExternalLibrary.res
line 19
E.A.O.firstSomeFn([
    () => ReducerInterface_GenericDistribution.dispatch(call, environment),
    () => ReducerInterface_Date.dispatch(call, environment),
    () => ReducerInterface_Duration.dispatch(call, environment),
    () => ReducerInterface_Number.dispatch(call, environment),
    () => FunctionRegistry_Library.dispatch(call, environment, reducer),
  ])->E.O2.default(chain(call, environment, reducer))
chain call is always made even if there is an answer. This leads to MathJs always being called.


build(catalog): use firebase for hosting and remove url prefixes

creates a firebase action that deploys on main and creates a github actions bot that deploys previews on PR.

Nice! I assume this is working because the preview URL looks great!


Fix order sensitivity of sensor computation

Proposed change

Updated tests to process resource list out of order
From PR #327

Co-Authored-By: Justin Paupore<EMAIL_ADDRESS>Type of change

[ ] Dependency upgrade
[x] Bugfix (non-breaking change which fixes an issue)
[ ] New feature (which adds functionality)
[ ] Breaking change (fix/feature causing existing functionality to break)
[ ] Code quality improvements to existing code or addition of tests

Additional information

This PR is related to issue: n/a

Codecov Report

Merging #329 (881b5dd) into 0.3.0 (ec58eda) will increase coverage by 0.48%.
The diff coverage is 98.38%.

@@            Coverage Diff             @@
##            0.3.0     #329      +/-   ##
==========================================
+ Coverage   96.68%   97.16%   +0.48%
==========================================
  Files           5        3       -2
  Lines        1025      742     -283
==========================================
- Hits          991      721     -270
+ Misses         34       21      -13

Impacted Files
Coverage Δ

custom_components/mail_and_packages/sensor.py
98.21% <96.29%> (-0.34%)
:arrow_down:

custom_components/mail_and_packages/helpers.py
96.43% <98.26%> (+1.32%)
:arrow_up:

custom_components/mail_and_packages/config_flow.py
100.00% <100.00%> (ø)

Codecov Report

Merging #329 (881b5dd) into 0.3.0 (ec58eda) will increase coverage by 0.48%.
The diff coverage is 98.38%.

@@            Coverage Diff             @@
##            0.3.0     #329      +/-   ##
==========================================
+ Coverage   96.68%   97.16%   +0.48%
==========================================
  Files           5        3       -2
  Lines        1025      742     -283
==========================================
- Hits          991      721     -270
+ Misses         34       21      -13

Impacted Files
Coverage Δ

custom_components/mail_and_packages/sensor.py
98.21% <96.29%> (-0.34%)
:arrow_down:

custom_components/mail_and_packages/helpers.py
96.43% <98.26%> (+1.32%)
:arrow_up:

custom_components/mail_and_packages/config_flow.py
100.00% <100.00%> (ø)


Subsequent interview attempts shouldn't start from scratch if the first didn't

22:08:23.655 CNTRLR   [Node 009] Beginning interview - last completed stage: RestartFromCache
22:08:23.655 CNTRLR » [Node 009] pinging the node...
... some messages ...
22:10:27.306 CNTRLR   [Node 009] Interview attempt 1/5 failed, retrying in 5000 ms...
22:10:28.498 CNTRLR   [Node 009] Beginning interview - last completed stage: None
22:10:28.498 CNTRLR   [Node 009] new node, doing a full interview...

The driver tries to query the device endpoints with security encapsulation. I'm not sure what's going on here. Might have to do with the replaceFailedNode attempts.

Cannot reproduce, neither with a battery-powered, nor with a mains-powered device. I'm assuming this is some kind of iterference between two devices sharing the same node id due to replacing a non-failed device.


Matched Colors

changed the background colors of the sign in and sign up pages to match with the rest of the pages

Nice work


Untar fork/exec /usr/bin/docker: argument list too long

Hi,
Thanks for doing this project1  I am generating an intermediate image due to huge build who's artifacts I remove but leaves my image bloated.
I'm using docker 1.3.2. and a pull of your repo from today.  I was excited to see that docker-squash has shrunken my image from 9.9G to 2.6 but docker is gacking on loading it back in.  I can save/load other images with docker but I think something must happening with the generated json or something.
Can you point me at a way to troubleshoot this?  Here is my pipeline:
sudo docker save 3e8458581665 | sudo docker-squash -verbose -t hhvm_builder_squashed | sudo docker load
                  -snip-
  -  Replacing 3e8458581665 w/ new layer 5eb58410aab4 (/bin/sh -c #(nop) CMD [/bin/bash])
Tarring up squashed layer 327e680e08d5
Removing extracted layers
Tagging 5eb58410aab4 as hhvm_builder_squashed:latest
Tarring new image to STDOUT
Done. New image created.
                  -snip-
  -  c8ce5a628d02 9 seconds /bin/sh -c #(nop) ENV LD_RUN_PATH=/opt/hhvm-dev/rtf/lib:/... 1.024 kB
  -  5eb58410aab4 8 seconds /bin/sh -c #(nop) CMD [/bin/bash] 1.024 kB
Removing tempdir /tmp/docker-squash547210872
2014/12/15 15:44:35 Error: Untar fork/exec /usr/bin/docker: argument list too long

FWIW, there is a seemingly unrelated docker issue -- though it is does involve a forthcoming docker squash command --  that matches the error I'm getting here.
Thanks
Chris

I was just able to reproduce this with an image. The same error happens when I just save and re-load the image without squashing.

docker/docker#10426

@ddollar My current workaround is to remove old images on the host.

Wish I could do that but I build 100s of images...
On Feb 26, 2015, at 6:45 PM, Jason Wilder<EMAIL_ADDRESS>wrote:

@ddollar My current workaround is to remove old images on the host.
—
Reply to this email directly or view it on GitHub.


Missing user permissions for docker on AWS ec2 ubuntu

I just tried to deploy a Ruby on Rails app using the new Kamal 2, I learned that the .env changed to use credentials defined in secrets or a command so thats cool and I had my deploy working correctly until it finished installing docker on AWS and I got a permission denied error. The user account didn't have permissions to access the docker daemon socket. I looked up the error online and quickly found an article which showed a fix.
SSH into the server and then run this command
sudo usermod -a -G docker $USER
Then you have to log out and it should work
I did this and verified it worked by running docker ps which previously threw an error
I'm guessing the permission error is because I specified a user other than root, I set my user to "ubuntu" which the aws server was using for a default username.
Anyways the command that fixed it for me could be added into Kamal to reduce the struggle of deploying, I might look into the code and see If it makes sense to add in to the kamal setup script

It seems like this was mentioned in the ssh.yml docs
If you are using a non-root user, you may need to bootstrap your servers manually before using them with Kamal
and it lists some helpful commands for setting up the server for non root users so I guess thats all it is.

what ssh.yml docs?   This is not at all clear.

what ssh.yml docs? This is not at all clear.
I meant that it was mentioned on the website at the very top it says if you aren't using a root account you need to give docker permissions to the user
I do it by sshing in as the user and running
sudo usermod -a -G docker $USER
https://kamal-deploy.org/docs/configuration/ssh/


Support change of loglevel per Runtime without restarting KIM

Description
For debugging purposes it is helpful to enable the debug-log for a particular runtime. KIM should be able to change the log-level (e.g. to DEBUG or TRACE) for all log-messages generated during the reconciliation of a paritcular RuntimeCR.
AC:

[ ] An annotation is added to the RuntimeCR which indicates that KIm should use a particular log-level for this runtime
[ ] KIM is at the beginning of the reconciliation of a RuntimeCR checking the loglevel-label defined the RuntimeCR. If not loglevel-label is set, its using the configured default-loglevel. Otherwise, the logger is using the defined loglevel.

Reasons
Changing loglevels for a paritcular runtime can simplify the debugging process.
Attachments

Relates to #402

Could be covered by https://github.com/stakater/Reloader


Can't display ™

Using the latest version (currently 1.4.1) I couldn't display the trade mark symbol.
var doc = new jsPDF();
doc.fromHTML('
Hello ™
');

Facing same issue. Did you get to resolve this issue

nope