CollectionAction and CreateAction on related resource

Hello Pavel, per my example I have subscribers (one main resource) which can have many fields (secondary resource). The JSON-API is not very clear as to where to put routes:

For example the GET endpoint subscriber/{id}/fields should return a collection of fields from subsriber with id={id} is this supported in doctrine-rest? If so where to put the route under what controller Subscriber or Field? Do I need to setup special repository methods (for example find fields by subsriber)?

For example a POST on subscriber/{id}/fields should create new fields and assign these to subscriber. is this taken care of in CreateAction?.

I am a little lost here and the JSON-API is not well refined at these points. For your reference check the following issues from the json-api repository and discussion:

https://github.com/json-api/json-api/issues/1158
https://github.com/json-api/json-api/issues/962
https://github.com/json-api/json-api/issues/795

Thanks,
Nikos

@foo123 It is doctrine repository, take a look at https://symfony.com/doc/3.3/doctrine/repository.html.
I will work on this, to gave good test cases to implement. But it should work properly with any Doctrine entity, etc. So I will dig into it on Doctrine level and prepare something good.

My method works correctly only it makes two calls to database one to fetch the primary entity and one to fetch the related resource via get{Key} entity method (it should be implemented on entity having manytoone or onetoone association). The code follows (it correctly returns 404 Not Found if primary resource id is not found):
namespace App\Action;

use League\Fractal\Resource\Item;
use Pz\Doctrine\Rest\Action\ItemAction;
use Pz\Doctrine\Rest\Contracts\RestRequestContract;
use Pz\Doctrine\Rest\RestResponse;
use Pz\Doctrine\Rest\RestRepository;

class RelatedItemAction extends ItemAction
{
    /**
     * Field that contains the related resourse key
     *
     * @var string
     */
    protected $relatedKey;

    public function __construct(RestRepository $repository, $transformer, $relatedKey)
	{
		parent::__construct($repository, $transformer);
		$this->relatedKey = $relatedKey;
	}

    /**
     * @param RestRequestContract $request
     *
     * @return RestResponse
     */
    public function handle($request)
    {
        $entity = $this->repository()->findByIdentifier($request);
		$method = 'get' . ucfirst($this->relatedKey);
		$relatedEntity = $entity->{$method}();

        $this->authorize($request, $relatedEntity);

        $resource = new Item($relatedEntity, $this->transformer(), $this->relatedKey);

        return $this->response()->resource($request, $resource);
    }
}

I am making an alternative RelatedCollectionAction in similar terms to fetch related resource collection. It will also make two DB calls. One to fetch primary resource and one to fetch the related collection resource. But it will handle correctly the Not Found exception. I will post it here for future reference.

This is the new RelatedCollectionAction that I implemented. It makes two DB calls, one to primary resource and another one with pagination and filtering to fetch the related collection. It correctly handles 404 Not Found resource type and works for onetomany and manytomany associations. It accepts two repositiories one primary and one related and one related key (the key in the tomany association). The code follows:
namespace App\Action;

use Doctrine\ORM\QueryBuilder;
use Doctrine\ORM\Tools\Pagination\Paginator;
use League\Fractal\Pagination\DoctrinePaginatorAdapter;
use League\Fractal\Resource\Collection;
use Pz\Doctrine\Rest\Action\CollectionAction;
use Pz\Doctrine\Rest\Contracts\RestRequestContract;
use Pz\Doctrine\Rest\RestResponse;
use Pz\Doctrine\Rest\RestRepository;

/**
 * Action for providing collection (list or array) of data with API.
 */
class RelatedCollectionAction extends CollectionAction
{
    /**
     * Field that contains the related repository
     *
     * @var RestRepository
     */
    protected $relatedrepository;

	/**
     * Field that contains the related resourse key
     *
     * @var string
     */
    protected $relatedKey;

    public function __construct(RestRepository $repository, RestRepository $relatedRepository, $transformer, $relatedKey)
	{
		parent::__construct($repository, $transformer);
		$this->relatedRepository = $relatedRepository;
		$this->relatedKey = $relatedKey;
	}

    /**
     * @param RestRequestContract $request
     *
     * @return RestResponse
     */
    protected function handle($request)
    {
        $resourceKey = $this->relatedRepository()->getResourceKey();
        $this->authorize($request, $this->repository()->getClassName());

        $entity = $this->repository()->findByIdentifier($request);
		$qb = $this->relatedRepository()->sourceQueryBuilder();
		$qb->andWhere($this->relatedRepository()->alias() . '.' . $this->relatedKey . ' = ' . ((int)$request->getId()));
		$this->applyPagination($request, $qb);
        $this->applyFilter($request, $qb);

         $paginator = new Paginator($qb, false);
         $collection = new Collection($paginator, $this->transformer(), $resourceKey);

        if ($qb->getMaxResults()) {
            $collection->setPaginator(
                new DoctrinePaginatorAdapter(
                    $paginator,
                    $this->paginatorUrlGenerator($request, $resourceKey)
                )
            );
        }

        return $this->response()->resource($request, $collection);
    }

	/**
     * @return RestRepository
     */
    public function relatedRepository()
    {
        return $this->relatedRepository;
    }
}

And this is how it is called:
	/**
	* @Route("/api/subscriber/{id}/fields", name="subscriber_fields", requirements={"id"="\d+"}, methods={"GET"})
	*/
	public function collectionAction(Request $httpRequest, $id)
    {
		$restRequest = new ApiRequest($httpRequest);
		$transformer = new FieldTransformer();
		$entityManager = $this->getDoctrine()->getManager();

		$restRepository = new RestRepository(
		   $entityManager,
		   $entityManager->getClassMetadata(Subscriber::class)
		);
		$relatedRestRepository = new RestRepository(
		   $entityManager,
		   $entityManager->getClassMetadata(Field::class)
		);
		$action = new RelatedCollectionAction($restRepository, $relatedRestRepository, $transformer, 'subscriber');

		// dispatch action
		$restResponse = $action->dispatch($restRequest);
		return $restResponse;
    }

@foo123 Please create pull request add this file in commit please!

Do you want RelatedItemAction as well?

What about creating related resource? For example POST fields to api/subscriber/1/fields and create fields and assign to subscriber 1 automaticaly?

RelatedItemAction will be good.

What about creating related resource? For example POST fields to api/subscriber/1/fields and create fields and assign to subscriber 1 automaticaly?

It is should be RelatedCreateAction.

What line-endings do you have? My editor shows you have CRLF. Is this correct?
How amy I supposed to implement RelatedCreateAction any ideas to set related id automaticaly?

RelatedCreateAction works as expected. Sets the correct association and returns 404 Not Found is main resource does not exist. Makes 2 DB calss, one to fetch primary resource and one to create related resource Code follows:
namespace App\Action;

use League\Fractal\Resource\Item;
use Pz\Doctrine\Rest\Action\CreateAction;
use Pz\Doctrine\Rest\Contracts\RestRequestContract;
use Pz\Doctrine\Rest\RestResponse;
use Pz\Doctrine\Rest\RestRepository;

class RelatedCreateAction extends CreateAction
{
	/**
	* Field that contains the related repository
	*
	* @var RestRepository
	*/
	protected $relatedRepository;

	/**
	* Field that contains the related resourse key
	*
	* @var string
	*/
	protected $relatedKey;

    public function __construct(RestRepository $repository, RestRepository $relatedRepository, $transformer, $relatedKey)
	{
		parent::__construct($repository, $transformer);
		$this->relatedRepository = $relatedRepository;
		$this->relatedKey = $relatedKey;
	}

    /**
     * @param RestRequestContract $request
     *
     * @return RestResponse
     */
    public function handle($request)
    {
        $relatedEntity = $this->relatedRepository()->findByIdentifier($request);

        $headers = [];
        $class = $this->repository()->getClassName();

        $this->authorize($request, $class);
        $entity = $this->hydrateEntity($class, $request->getData());
		$setRelation = 'set' . ucfirst($this->relatedKey);
		$entity->{$setRelation}($relatedEntity);
        $this->validateEntity($entity);
        $this->repository()->getEntityManager()->persist($entity);
        $this->repository()->getEntityManager()->flush();

        if ($entity instanceof JsonApiResource) {
            $headers['Location'] = $this->repository()->linkJsonApiResource($request, $entity);
        }

        $resource = new Item($entity, $this->transformer(), $this->repository()->getResourceKey());
        return $this->response()->resource($request, $resource, RestResponse::HTTP_CREATED, $headers);
    }

	/**
	* @return RestRepository
	*/
	public function relatedRepository()
	{
		return $this->relatedRepository;
	}
}

This is how it is called:
	/**
	* @Route("/api/subscriber/{id}/fields", requirements={"id"="\d+"}, methods={"POST"})
	*/
	public function createWithSubscriberAction(Request $httpRequest, $id)
    {
		$restRequest = new ApiRequest($httpRequest);
		$transformer = new FieldTransformer();
		$entityManager = $this->getDoctrine()->getManager();

		$restRepository = new RestRepository(
		   $entityManager,
		   $entityManager->getClassMetadata(Field::class)
		);
		$relatedRestRepository = new RestRepository(
		   $entityManager,
		   $entityManager->getClassMetadata(Subscriber::class)
		);
		$action = new RelatedCreateAction($restRepository, $relatedRestRepository, $transformer, 'subscriber');

		// dispatch action
		$restResponse = $action->dispatch($restRequest);
		return $restResponse;
    }

if you want I can make another commit.

With the new actions that I have implemented this issue is resolved. Closing this.


[Bug] Permission package

Bug report
What I did
I've seeded permissions and role groups, all configurations is set proper, it hides menu elements.
What I expected to happen
it should hide all menu which is hidden by permission or the role (  backpack_user->hasPermissionTo('project_access') )
What happened
but when it comes to hide sidebar_content elements on dashboard page it hides them, but when it comes to get into a menu item, some hidden items are becoming visible on sidebar.
What I've already tried to fix it
I've checked auth.php, and also base.php, I ensure its not caused by a code override.
Backpack, Laravel, PHP, DB version
When I run php artisan backpack:version the output is:
LARAVEL VERSION:
v8.31.0@2aa5c2488d25178ebc097052c7897a0e463ddc35
BACKPACK VERSION:
4.1.38@90cf9d0613848144c1e5f3822892bf2a7afa860f

I have found the reason, but it requires your help :)
when we create custom crud operations this bug occures.

Hello @siberfx
I am sorry but I could not reproduce your issue.
What I did:
Copied ShowOperation into CustomShowOperation and added use CustomShowOperation in the controller.
Added to sidebar: backpack_user()->hasPermissionTo('manage news') (User does not have permission for this).
Go into my CustomShowOperation, item still hidden in sidebar.
Might be a cache issue ? Try running php artisan cache:clear, and forcely clear permission cache when updating permissions via WebUI.
Let me know if I missed some step to reproduce it.
Thanks,
Pedro


Please implement Search Template

Which version of Elastic are you using?
[X] elastic.v7 (for Elasticsearch 7.x)
[ ] elastic.v6 (for Elasticsearch 6.x)
[ ] elastic.v5 (for Elasticsearch 5.x)
[ ] elastic.v3 (for Elasticsearch 2.x)
[ ] elastic.v2 (for Elasticsearch 1.x)
Please describe the expected behavior
Why description say that the Search template is supported but just partially?
Please is a powerful feature that must be implemented

When you say "implement search template" do you mean the creation, the validation, the updating process, or running a search with a template? That's quite some work.
I've personally never used search templates, but I'd be happy to see a PR to merge this into the code base. Meanwhile, you can build the feature yourself and use PerformRequest with a body and/or RawStringQuery to actually do what you want. Most services also have a BodyJson and a BodyString method that allows you to specify the request body yourself (overwrites anything the DSL does to the body)—find an example here. For creating a search template, this is probably the way to go anyway, as I don't see how a DSL would help in any way.


wasm: Add API to get buffered body data.

Description: Change the behavior of "proxy_on_request_body" and "proxy_on_response_body" to make it easy to get accessed to the buffered body.
When one of these callbacks returns "StopIterationAndBuffer," the next invocation of that callback will return the data that Envoy has been buffering. Specifically, the "length" parameter passed to the callback will reflect the buffered data, and the various "getBuffer" methods will return the data buffered so far.
A filter that wishes to gather the whole body in one buffer and act on it then can return StopIterationAndBuffer from each call until the "end_of_stream" flag is set, and then it can access the entire body at once.
A filter that wishes to only examine part of the body can return StopIterationAndBuffer until the buffer contains enough data, then return another status code to stop buffering.
Like in other Envoy plugins, Envoy will not allow the buffer to exceed the currently configured maximum. If this happens, Envoy will automatically stop filter processing and return either 413 (Payload Too Large) on the request path, or 500 (Internal Server Error) on the response path.
Testing: New test cases added to wasm_filter_test.cc, with a new WASM module to test it.
Signed-off-by: Gregory Brail<EMAIL_ADDRESS>

Definitely... let me make sure I can think of an interface that works,
though, because we might have to keep track of state in the "context"
object.
Maybe proxy_get_buffer_*(HttpRequestBody) works like this:

If the filter previously returned StopIterationAndBuffer, then return
the buffered data
Otherwise, return the current chunk.

That is not how regular callbacks work but IMO it is indeed simpler to use,
so I can try and test that out if you agree.
On Thu, Feb 27, 2020 at 12:08 PM Piotr Sikora<EMAIL_ADDRESS>wrote:

@PiotrSikora commented on this pull request.
In api/wasm/cpp/proxy_wasm_common.h
https://github.com/envoyproxy/envoy-wasm/pull/437#discussion_r385344341:

@@ -73,7 +73,8 @@ enum class BufferType : int32_t {
NetworkUpstreamData = 3,   // During the onLog callback these are immutable
HttpCallResponseBody = 4,  // Immutable
GrpcReceiveBuffer = 5,     // Immutable

MAX = 5,

BufferedBody = 6,          // After returning StopIterationAndBuffer

@gbrail https://github.com/gbrail sorry if my response wasn't clear, I
definitely want to have access to the buffered data for obvious reasons.
What I'm suggesting is that this data should be available via
getBuffer(HttpRequestBody) call (i.e. consumer shouldn't care whether
this is new or buffered data) and not via a separate call. Does it make
sense?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/envoyproxy/envoy-wasm/pull/437?email_source=notifications&email_token=AAD7I225GNPFXH5CGZCAAITRFAMTXA5CNFSM4K4UJTQ2YY3PNVWWK3TUL52HS4DFWFIHK3DMKJSXC5LFON2FEZLWNFSXPKTDN5WW2ZLOORPWSZGOCXICPJQ#discussion_r385344341,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAD7I2YYAOICZZ45VUS7GYTRFAMTXANCNFSM4K4UJTQQ
.

Actually, I'm just going to merge it now, since I have a follow-up that touches the same areas of the code, so I can cleanup style there.

Thank you and for directing me on the style!
On Tue, Mar 3, 2020 at 6:24 PM Piotr Sikora<EMAIL_ADDRESS>wrote:

Merged #437 https://github.com/envoyproxy/envoy-wasm/pull/437 into
master.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/envoyproxy/envoy-wasm/pull/437?email_source=notifications&email_token=AAD7I2YMK242QNS7CT62GWDRFVDN3A5CNFSM4K4UJTQ2YY3PNVWWK3TUL52HS4DFWZEXG43VMVCXMZLOORHG65DJMZUWGYLUNFXW5KTDN5WW2ZLOORPWSZGOXBQK4VA#event-3093343828,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAD7I2ZYY3WHOXARVCVB7G3RFVDN3ANCNFSM4K4UJTQQ
.


Add a simple example with how to use the mock server container

Thanks @worldtiki - that's a good idea.
We are trying to gradually move all code snippets into executable test code that gets included at docs build-time. This means that we can have more confidence that code snippets are correct and up to date.
Could you perhaps have a go at it? We have the process roughly documented here, and there are a few examples of documentation pages that have already been migrated to this approach (e.g. this.

Of course :)

Excellent, thank you :)


Add 1-moment microphysics

Purpose
Add 1-moment microphysics to ClimaAtmos
Closes #2103
To-do

Add precipitation flux to diagnostics
Add documentation on the source terms
Add the plot script output to artifacts
Test in a long run

Content

Adds RHS terms from 1-moment microphysics
Adds advection with terminal velocity
Adds a simple single column sanity test

[ ] I have read and checked the items on the review checklist.

This PR got too large. I'll split it into adding an empty precipitation tendency + test + diagnostics stuff as one PR. And in the follow up PR I'll add the actual RHS terms.


[fatal][tid:com.facebook.react.ExceptionsManagerQueue] Unhandled JS Exception: TypeError: undefined is not an object (evaluating 'o.PushNotificationIOS.FetchResult')

For anyone getting this when trying to get push notifications to work with react-native-firebase, this is the only thing that worked for me...

In Old Doc, I get this and work for me...
https://facebook.github.io/react-native/docs/pushnotificationios
At the top of your AppDelegate.m:
#import <UserNotifications/UserNotifications.h>

{
  ...
  // Define UNUserNotificationCenter
  UNUserNotificationCenter *center = [UNUserNotificationCenter currentNotificationCenter];
  center.delegate = self;

  return YES;
}

//Called when a notification is delivered to a foreground app.
-(void)userNotificationCenter:(UNUserNotificationCenter *)center willPresentNotification:(UNNotification *)notification withCompletionHandler:(void (^)(UNNotificationPresentationOptions options))completionHandler
{
  completionHandler(UNAuthorizationOptionSound | UNAuthorizationOptionAlert | UNAuthorizationOptionBadge);
}

Originally posted by @ruyjfs in https://github.com/react-native-community/react-native-push-notification-ios/issues/50#issuecomment-572650417

I don't have permission to push a branch, so if someone who can wants to here's an updated readme to reflect this. I also applied the markdownlint recommendations...
@react-native-community/push-notification-ios

React Native Push Notification API for iOS.
Getting started
Install
yarn add @react-native-community/push-notification-ios

Link
There are a couple of cases for linking. Choose the appropriate one.

react-native >= 0.60

The package is automatically linked when building the app. All you need to do is:
cd ios && pod install

react-native <= 0.59

react-native link @react-native-community/push-notification-ios

upgrading to react-native >= 0.60

First, unlink the library. Then follow the instructions above.
react-native unlink @react-native-community/push-notification-ios

manual linking

If you don't want to use the methods above, you can always link the library manually.
Update AppDelegate.m
Finally, to enable support for notification and register events you need to augment your AppDelegate.
At the top of the file:
#import <RNCPushNotificationIOS.h>

Then, add the following lines:
// Required to register for notifications
- (void)application:(UIApplication *)application didRegisterUserNotificationSettings:(UIUserNotificationSettings *)notificationSettings
{
  [RNCPushNotificationIOS didRegisterUserNotificationSettings:notificationSettings];
}
// Required for the register event.
- (void)application:(UIApplication *)application didRegisterForRemoteNotificationsWithDeviceToken:(NSData *)deviceToken
{
  [RNCPushNotificationIOS didRegisterForRemoteNotificationsWithDeviceToken:deviceToken];
}
// Required for the notification event. You must call the completion handler after handling the remote notification.
- (void)application:(UIApplication *)application didReceiveRemoteNotification:(NSDictionary *)userInfo
fetchCompletionHandler:(void (^)(UIBackgroundFetchResult))completionHandler
{
  [RNCPushNotificationIOS didReceiveRemoteNotification:userInfo fetchCompletionHandler:completionHandler];
}
// Required for the registrationError event.
- (void)application:(UIApplication *)application didFailToRegisterForRemoteNotificationsWithError:(NSError *)error
{
  [RNCPushNotificationIOS didFailToRegisterForRemoteNotificationsWithError:error];
}
// Required for the localNotification event.
- (void)application:(UIApplication *)application didReceiveLocalNotification:(UILocalNotification *)notification
{
  [RNCPushNotificationIOS didReceiveLocalNotification:notification];
}

Also, if not already present, at the top of the file:
#import <UserNotifications/UserNotifications.h>

Inside didFinishLaunchingWithOptions or equivalent:
  // Define UNUserNotificationCenter
  UNUserNotificationCenter *center = [UNUserNotificationCenter currentNotificationCenter];
  center.delegate = self;

And at the bottom (before @end):
  // Called when a notification is delivered to a foreground app.
  -(void)userNotificationCenter:(UNUserNotificationCenter *)center willPresentNotification:(UNNotification *)notification withCompletionHandler:(void (^)(UNNotificationPresentationOptions options))completionHandler
  {
    completionHandler(UNAuthorizationOptionSound | UNAuthorizationOptionAlert | UNAuthorizationOptionBadge);
  }

Migrating from the core react-native module
This module was created when the PushNotificationIOS was split out from the core of React Native. To migrate to this module you need to follow the installation instructions above and then change you imports from:
import { PushNotificationIOS } from "react-native";

to:
import PushNotificationIOS from "@react-native-community/push-notification-ios";

@plisitza thanks so much for clarifying the instructions!
I can make the change in the document, but if you make a fork of this repository, then make your changes there, and send a Pull Request towards this repository, then I can merge it and you will be credited! :+1:
You can make a fork by pressing the fork of this repository by pressing the fork button on top right


Compile error: Header 'ChattoAdditions-Swift.h' not found

I use Chatto and ChattoAdditions successfully in swift project, XCode 9.2. with Cocoa Pods.
I updated Xcode to version 9.4.1.
There was  an errors in automatic generated file "module.modulemap":
Header 'ChattoAdditions-Swift.h' not found.
There is not  'ChattoAdditions-Swift.h' file in repository.
How to fix this error?

@vasadulin I'm pretty sure there is an issue with Swift versions. Can you take a look into this comment? https://github.com/badoo/Chatto/issues/331#issuecomment-351670462 It should help

To fix this error:
Increase the version of Swift for the libraries: Chatto and ChattoAdditions.
The main project has swift 3.3 version. But I can use libraries with swift 4.
Steps to fix problem:

Choose Pods in Project navigator.
Choose target: ChattoAdditions (Chatto)
Change Swift Language Version to Swift 4.1
Rebuild project (Clean & Build)

@vasadulin If you do it manually then you need to do it every time you update pods. I suggest you to add a script from the comment above to the end of your podfile.


Almost all of the pages of preference dialog is not shown.

The setting items (like 'Editor', 'Preview', 'Workspace' and etc) is not shown at the left-side tree of the preference dialog.

It seems caused by the "early exit" functionality of lodash '_.each' function.


Package changelogs

Opening this for discussion for whether we should provide changelogs for when bugs/feautres have been fixed/added to the package, and if we should start adding changelogs then which format should we use.
Personally I think it would be helpful to add changelogs, and use a dates when these changes was implemented.
I.E.
# Package Changelog

## 2015-05-01
### Bugs
- Fixed a problem that the wrong install directory was used (Issue \#457)

### Features
- Implemented ability to enable symlinks (Issue \#578)

Probably shouldn't require it though, not at first. But just recommend to add one.
Thoughts @gep13 @pascalberger @majkinetor

Another option could perhaps be to just use a generic ## Upcoming subheader and have it replaced with the version when it have been pushed from appveyor (using a script).

Changelog.md in package root might be good to have. Should probably be included in the package as it can be viewed from the gallery.

Yeah, it was in the package root I was thinking as well.
Not sure about including it in the package though, think it would be better to link to the changelog in the release notes element IMO.
Even though the changelog would be viewable on chocolatey.org, if using markdown it would just be displayed as ordinary text.

@majkinetor I've added a PR as an example to one way I think the changelogs could be implemented.
see PR #716

I think its hard to read with all that subheaders. Peraps just use Bugfix prefex ?

Not sure about including it in the package though, think it would be better to link to the changelog in the release notes element IMO.

Not sure either. One rationale to include it was that you don't have to depend on external sources in order to see it which may be important for some people, especially those that cache it.

Peraps just use Bugfix prefex and just version header ?

You mean something similiar to the changelog used in chocolatey-core.extension?
Personally I like to separate bugfixes and features/improvements to their own section (under the version), as well as having the date it was added, and I don't really find the 7zip.install changelog I added hard to read.
With that said though, formatting could definitely be improved.

You mean something similiar to the changelog used in chocolatey-core.extension?

Yeah, thats way more readable IMO

Personally I like to separate bugfixes and features/improvements

They can be separated without a header. The header formatting makes more sense where there are expected many changes across versions, packages will usually only have 1 thing per version, usually no more then 2 in any case, which makes headers just spam. So no, formatting can not be improved, its about ratio of header lines / changes which will here be most of the time > 1.

To resume, we are for changelog.
Closing this.


Generate new API Permission mappings

We should generate the newest permission mappings.
How was this done in the past?
Can we automate it?
Is there any new, better tool we can use?

I'm not entirely clear what "API Permission mappings" means.  Do you mean these from AndroidManifest.xml?

<uses-permission>
<uses-permission-sdk-23>
<permission>
<permission-group>
<permission-tree>

No, there is a reverse mapping of API Calls to Permissions. For example https://github.com/androguard/androguard/blob/master/androguard/core/api_specific_resources/api_permission_mappings/api_permission_mappings_api22.py
As google does not provide those information, there are some crawlers to just search in the documentation and create those files. Some tools are mentioned here: https://stackoverflow.com/a/24019120/446140
Maybe we can use the mappings from here? http://axplorer.org/
The Problem with PScout is, that it is not very precise...

related #266
maybe we should generate the android package resources as well.

We need also regenerate the SYSTEM ATTRIBUTES for the AXML parser.

@eighthave how would you implement this, especially when it comes to packaging: I have now used axplorer as a submodule and wrote a script to parse the files and convert them into the format that is used in androguard. those files are stored as JSON in the old folders and are loaded on demand.
should we generate the files and commit them or should this be done on install time? Of course we can also do both...

Either should be easy, so whatever is easier for you:

including them in git/source tarball
generating them as part of the build is easy

But keep in mind all the files needed to generate them need to be either in the source tarball or an existing Debian package.

Currently I commit the generated json files, see #417
Otherwise we can also use the submodule - are these included in the tarballs? then the generation is not that hard.

I'm thinking about adding platform_framework_base as a submodule as it contains all the necessary files to generate our stuff from... But this repo is huge! Any better ideas?

you can download the tarball, which is about 25MB, from their git web
view.  Look for the [tgz] link at the upper-ish right.
https://android.googlesource.com/platform/frameworks/base/+/android-8.1.0_r14
For example, you can download the "android-8.1.0_r14" release tag:
https://android.googlesource.com/platform/frameworks/base/+archive/android-8.1.0_r14.tar.gz


Rule "name" should be saved in Validation Error

Currently validation error is just a group of strings that are loosely tied to the rule name itself. We should save the rule name itself into the error.

I'll address this when I take care of #170


Ubuntu package local.ini changes cause conflict on upgrade

Expected Behavior

The comments at the top of the local.ini file state:
; Custom settings should be made in this file. They will override settings
; in default.ini, but unlike changes made to default.ini, this file won't be
; overwritten on server upgrade.
Current Behavior

Instead, during an upgrade from 2.1.1 to 2.2.0, the user is informed of a conflict in local.ini and asked to resolve.
Possible Solution

Move all setting defaults, descriptions, and boilerplate to default.ini and leave local.ini purely for local changes.
Steps to Reproduce (for bugs)

Install couchdb 2.1.1 via Apache repositories on Ubuntu 16.04
Make a change to local.ini
Use apt to upgrade to couchdb 2.2.0

Context

I have dozens of systems running couchdb that need to stay current and they all have at least one custom setting in local.ini. Automated updates run into this bug and require human intervention unless I explicitly ignore maintainer changes to local.ini.
Your Environment

Version used: 2.1.1, 2.2.0
Browser Name and version:
Operating System and version (desktop or mobile): Ubuntu server 16.04.5
Link to your project:

Hi @ahayes, thanks for this report.
You've made changes to a packaged config file. We very rarely, but occasionally, make changes to local.ini to change the commented-out defaults to their new values, or to add new values to it. This did happen with 2.2.0.
The Debian/Ubuntu warnings on the conffile are part of us adhering to Debian policy which dictates  that package upgrades MUST take care of preserving user changes to configuration files. We can't simultaneously do that while updating the contents of that file with new guidance or recommendations.
You have two options available to you the way things are today:

Pass the appropriate option to dpkg from apt when doing an upgrade, as documented here. In your case, I expect you'd prefer to have our new version installed as local.ini.dpkg-dist. This can be done with:

$ apt-get -o Dpkg::Options::"-force-confdef" -o Dpkg::Options::"--force-confold" install --only-upgrade couchdb

The first option tells dpkg to decide on its own whenever possible, prompting only when necessary, and overwriting any config files that have not been modified.
The second option says to not modify the current configuration file if changed, and install the new version from tha package with the .dpkg-dist suffix.
I've shown install --only-upgrade couchdb to limit this process to just the couchdb package. If you'd used dist-upgrade there, apt-get would proceed to apply the same approach across all packages, not just couchdb. You can use this if you want.

Another workaround is for you to simply not modify local.ini, and instead place new files inside of the local.d directory named with a .ini extension. These files are processed after all other files, including local.ini, per the order described in the documentation. In this case, there will never be a change to local.ini that will conflict with your changes.

I agree with your assessment that we should improve this going forward. Ideally, we wouldn't have default.ini or local.ini files at all, and would just use the contents of the local.d directory as provided by you, the end user. This would be part of a larger config subsystem rewrite that would address concerns like #777. I will open a new ticket on the roadmap for this (it's been under discussion for a while, but no roadmap ticket exists yet) and link back to this one so you can follow its progress in the future.
Thanks again for your interest in Apache CouchDB!

Thank you very much for the detailed response with options for me and for linking back so I can stay in the loop!


x/pkgsite: support viewing the standard library @master

It would be useful to view https://pkg.go.dev/std@master. This issue was originally opened in https://github.com/golang/go/issues/39973.
At the moment, when running the worker and visiting http://localhost:8000/fetch/std/@v/master, this error shows up in the version_map table:
fetchAndInsertModule("std", "master"): FetchModule("std", "master"): processZipFile("std", "v0.0.0-20210218181204-f3c2208e2cca"): extractPackagesFromZip(ctx, "std", "v0.0.0-20210218181204-f3c2208e2cca", r, d): expected file to have prefix<EMAIL_ADDRESS>got = "std@master/AUTHORS": module zip is malformed: bad module

Requests to https://pkg.go.dev/std@master are now supported.


[BUG] Incorrect signal being emitted in v2

Godot version
3.5.3
Plugin version
v2.1.0
Phone information
All iOS devices
Issue description
When the GAD delegate calls to https://developers.google.com/admob/ios/api/reference/Protocols/GADFullScreenContentDelegate#-ad:didfailtopresentfullscreencontentwitherror:, the plugin fires the interstitial_failed_to_load signal. However, because it's attempting to present it, it should be interstitial_failed_to_show. This is of course in an older version, but is a simple fix, and I'm happy to open a PR for it, just can't at the moment due to having to find a work-around for this in my app.
Steps to reproduce
The issue is right here: https://github.com/poingstudios/godot-admob-ios/blob/4ceb5f9944b9d6cad6ae76e54cd5451e1cc04b6a/plugin/admob/src/formats/Interstitial.mm#L87
Further, you can see that it's probably not intended to be load by looking at this line, which is firing the same signal, but correctly from the load call: https://github.com/poingstudios/godot-admob-ios/blob/4ceb5f9944b9d6cad6ae76e54cd5451e1cc04b6a/plugin/admob/src/formats/Interstitial.mm#L50
Additional context
If you're willing to make a new release and don't have time to fix this yourself, I'm happy to open a PR. Let me know!

Thank you for opening this issue, It would be awesome if you open a PR!


Add Travis CI

Travis now takes care of building the HTML version of the spec and
uploading it to AWS S3. This works for every branch that is hosted on
the p4lang/p4runtime repo, but not for PRs opened from forks (for
security reasons).

@wmohsin please review. This is related to your comment on my previous PR and https://github.com/p4lang/p4runtime/issues/8. With this you will be able to visualize the spec online for all branches of this repo (unfortunately not for fork branches but since you have write permissions for this repo, you can create branches directly on this repo).
For examples, for this branch: https://s3-us-west-2.amazonaws.com/p4runtime/travis/add-travis/P4Runtime-Spec.html

@chrispsommers Please leave an approving review, otherwise I can't merge...


Adding zoom to numeric CSS propery enum

Before when the css method appended "px" to the given value, although zoom is a numeric property and should not have any units

zoom is non-standard and shouldn't be used. Since cash is aimed towards modern browsers and aims to be absurdly small I don't think it makes sense to implement this.
@knee-cola why do you think it should be implemented?

Well I was using it in my project, which I'm switching over to from jQuery to cash. That's how I discovered it didn't work.
The logic I was following when creating this pull request is that cash is a perfect drop-in replacement for jQuery, which means it should implement the API exactly (only later did I discovered that .on and .one implemented a different API).
However if the official policy of cash is to implement standard features only, I see why this pull request should be rejected.
Thank you for you response!

@knee-cola we don't actually try to be a perfect drop-in replacement for jQuery. We have a migration guide in case you haven't seen it already, I'll make sure to mention that we don't add the px suffix to the zoom CSS property there 👍 Let me know if you discover more incompatibilities.


[🪢] Merge dev into master

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


[New Sample] - Tab Meeting Recording and Transcript - NodeJs

Executed build pipeline

URL: https://github.com/OfficeDev/Microsoft-Teams-Samples/actions/runs/6691260240

Executed build pipeline
https://github.com/OfficeDev/Microsoft-Teams-Samples/actions/runs/6731683390

@Jegadeesh-MSFT  Need to migrate into Teams Toolkit

Executed Build pipeline:
https://github.com/OfficeDev/Microsoft-Teams-Samples/actions/runs/6744647628


chore(main): release 1.22.0

:robot: I have created a release beep boop
1.22.0 (2024-12-17)
Features

APIM-608: gov notify - file upload/link support (#1083) (dddf3e6)
APIM-609: companies house - extend returned fields (#1089) (041124c)
APIM-610: markets - add country rating description field (#1090) (11ec0d4)

Bug Fixes

APIM-608: eslint downgraded (b0e349c)
APIM-608: make GovNotify properties optional (#1082) (9240907)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

v1.22.0
:sunflower:


Use class list opposed to using the classname string

This is caused because the add is adding a space that is not being trimmed.  Opposed to using classname (String), it is better to use classlist (List Object).
http://www.w3schools.com/jsref/prop_element_classlist.asp

.remove
Removes one or more class names from an element.Note: Removing a class that does not exist, does NOT throw an error

.add
Adds one or more class names to an element.If the specified class already exist, the class will not be added

Okay I get it I suck at coding


IE10 support

Tabs aren't clickable under IE10 and below
Would be looking for some help about this issue
Best

:+1: Same issue, href="#" was removed from the anchor link, which make the tab unclickable and clicking it results in page reload


Missing sensor in HomeKit app, but als not visible on accessoires overview page in Homebridge

I've got te script working, in the Homebridgelog I see data which comes from my solar installation. But I don't see any sensor-information in my Homekit app. What do I wrong?
Could you please advise, thank you.

Aere you ad the accessory to the home app?

Yes, and a lot of assessories were visible, except for the Enphase plugin assessories.

Please read this: https://github.com/grzegorz914/homebridge-enphase-envoy?tab=readme-ov-file#about-the-plugin

I did, but looks like I did everything as stated. Should I see the Accessoires (sensors) in Accessoires overview in Homebridge itself?

yes, the sensors are visible in homebridge and in home app, if you have some problems please post the debug log then I can look what is going wrong. To enable debug mode go to plugin settings advanced section>>>system>>debug

I found this issue in the logging:
[20-6-2024, 09:11:39] [homebridge-enphase-envoy] Device: xxx.xxx.xxx.xxx Envoy-S, Start error: Requesting power production mode error: AxiosError: Request failed with status code 401., trying again in 15s.
Replaced ip with xxx.xxx.xxx.xxx

I've turned of supportProductionPowerMode
If enabled, control Production Power Mode will be possible in Envoy section (EVE or Controler app), Fw. 7.x.x and newer required installer credentials data.
Now I see sensors coming up!

Yes, to read/write Production Power Mode and PLC level, Installer credentials data are required in other things wil return error 401 - wrong credentials data.
I think is solved now.


Setting CI running in PR trigger in any branch

Changed log

I think it should let CI running about PR trigger can run any of branches because it's easy for same contributor to create two or more PRs at same time.

Hi @peter279k, thank you for your contribution! Can you please fill out our Contributor's License Agreement form? https://docs.google.com/forms/d/e/1FAIpQLSeRVQ35-gq2vdSxD1kdh7CJwRdjmUA0EZ9gRXaWYoUeKPZEQQ/viewform?formkey=dDViT2xzUHAwRkI3X3k5Z0lQM091OGc6MQ&ndplr=1

Hi @peter279k, thank you for your contribution! Can you please fill out our Contributor's License Agreement form? https://docs.google.com/forms/d/e/1FAIpQLSeRVQ35-gq2vdSxD1kdh7CJwRdjmUA0EZ9gRXaWYoUeKPZEQQ/viewform?formkey=dDViT2xzUHAwRkI3X3k5Z0lQM091OGc6MQ&ndplr=1

@bezhermoso, done :).

Thanks!


Grammar update on articles/cosmos-db/concepts-limits.md

@seesharprun

Can you review this PR?
IMPORTANT: When this content is ready to merge, you must add #sign-off in a comment or the approval may get overlooked.

#label:"aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team

#sign-off

Due to the upcoming Ignite conference, all merging and publishing is on hold until the morning of 11/15.
This PR is ready for merge on 11/15.
#label: "event-triaged-to-10AM"
#label: "missed-content-complete"
#label: "aq-pr-triaged"
@MicrosoftDocs/public-repo-pr-review-team


Fix FOUC on Firefox

As mentioned in #1698 Firefox users experience a brief FOUC (flash of unstyled content) while loading various pages in Gitea, this commit should fix this by using Filament Groups loadCSS library to asynchronously load the CSS that makes the pages flash.
This commit will add ~1.5kB of JS to the <head> of the webpages. The scripts need to be in the head for the FOUC to not occur, if you do it with the scripts in the bottom of the page it will load the CSS too late and the FOUC will occur regardless. You could potentially also inline them but I went with linking to them.
You will notice in the before and after from the developer panel that the Font Awesome CSS is loaded last because it will not load until the DOM content is ready.

NOTE: In case users don't have JS enabled it will load the CSS as normal. However I'm not sure if this is required and that I could just remove the <noscript> line.
This is my first pull request to Gitea, so let me know if I need to change anything. 😃

I've tested this on MacOS as well.  Looks good in Firefox and Chrome.  Did not see any small flashes in Firefox at all, which occasionally show up without this patch applied.
I'll try to find some time to test on Windows 7 in the next few days.

Built and tested on Windows 7.  I tested Firefox 53, Chrome 58 and IE 11.  No FOUC on any of them, not even on initial (uncached) page load.  Better than github in that regard.
I did not notice any obvious problems with page load speeds on any of the browsers.  But I just browsed around the site and compared it to try.gitea.io.  No real timing tests.
Nice job with the fix.

So this will fix #1271?

Not sure about that one, but it does fix https://github.com/go-gitea/gitea/issues/1698

@lunny, this specifically fixes #1698 and if it fixes anything else that's purely coincidental 😃

@sondr3 I have tested that this will fix #1271, so LGTM

LGTM

Actually @sondr3  please add the license of the new .js files to https://github.com/go-gitea/gitea/blob/master/public/assets/librejs/librejs.html

@sondr3 see #1484 (there are also more librejs things missing, in case you want to deal with this in a separate PR)

@ethantkoenig please confirm your codereview

@strk I'll add them to this PR when I get to my computer in a few hours and push a new change 😃

Alright, added the JS files to the librejs.html file, I wasn't sure where to link to the license since there's not a canonical homepage for it but OSI seemed like a good fit.


Visualizations: Long variable values for categorical axes may also need ellipsis mouseover

PRISM2 bar plot

I just checked today and now x-axis labels are straight up & down instead of on an angle. Angle is better. Elipses are still needed

It looks good now. Closing ticket.

@aaronwlsong Thank you for your tests 👍


[FLINK-36742][cdc-base][oracle] Filter unacked  split for no capture tables when task restore from state

FLINK-36742

@leonardBang PTAL

@leonardBang Please help retry trigger CI. There are unrelated UT error.

I will rebase master after https://github.com/apache/flink-cdc/pull/3712 is merged.


⚠ Bofrost.lu has degraded performance

In a411b90, Bofrost.lu (https://www.bofrost.lu) experienced degraded performance:

HTTP code: 200
Response time: 1085 ms

Resolved: Bofrost.lu performance has improved in 4e8bfb5.


RowIndex Increase Across Pagination

Hello, is there a way to get rowindex cross pagination yet? Need the row index to be correct to do an onChange on that row. When I do onChange on rows on page 2, the onChange would affect rows on page 1.
I'm using the basic pagination, if I could somehow get the current page, then I would be able to use that to increment the row index, but I don't know how.

I was able to get the page number and set that to currentPage then use that in the column, but setting state inside onPageChange causes pagination to stop working. Clicking on the next page always return the first page.
const options = {
onPageChange: (page, sizePerPage) => {
this.setState({ currentPage: page });
console.log(page);
}
};
///
dataField: '#',
text: '#',
formatter: (cell, row, rowIndex) => {
let rowNumber = this.state.currentPage * (rowIndex + 1);
return {rowNumber};
},

Ok, I figured it out. I forgot to assigned page to the currentPage state.
const options = {
  onPageChange: page => {
    this.setState({ currentPage: page });
  },
  page: this.state.currentPage
};

// for the column
dataField: '#',
text: '#',
formatter: (cell, row, rowIndex) => {
let rowNumber = (this.state.currentPage - 1) * 10 + (rowIndex + 1);
return {rowNumber};
},


[Improvement] [AUTHZ] Spec json files should be auto generated, rather than edit manually

Code of Conduct

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

Search before asking

[X] I have searched in the issues and found no similar issues.

What would you like to be improved?
In #4658, this pr edit the table_command_spec.json, but this file should be generated by JsonSpecFileGenerator.scala, rather than edited this file manually.
The json automatically created using this PR is inconsistent with the manually modified json, which will cause trouble for developers on other branches
We should first fix this bug, and than every build use JsonSpecFileGenerator generated spec json, rather than those in resource dir.
How should we improve?
No response
Are you willing to submit PR?

[X] Yes. I would be willing to submit a PR with guidance from the Kyuubi community to improve.
[ ] No. I cannot submit a PR at this time.

Hi the spec json file should not be regenerated in each build. It's done by design.
The Authz plugin should only depends on the generated spec json file in runtime, so the committed spec json file should be static, packaged in plugin, checked in CI builds.
So it's good to enforce checks on generated spec json file, but not to regenerate them in builds.


Error for eval for KITTI-STEP Video Panoptic Segmentation

Follow the deeplab2/g3doc/projects/motion_deeplab.md, I try eval for kitti step dataset in panoptic deeplab. The order is a follows:'python train.py --config_file=../configs/kitti/panoptic_deeplab/resnet50_os32_trainval.textproto --mode=eval
--model_dir=/home/ubuntu/dev/sda1/model/model_yunjian/motion_deeplab/single_frame_ckpt --num_gpus=0'
while got the following error;
Traceback (most recent call last):
File "/home/ubuntu/yunjian/motion_deeplab/deeplab2/trainer/train.py", line 76, in
app.run(main)
File "/home/ubuntu/anaconda3/envs/motion_deeplab/lib/python3.6/site-packages/absl/app.py", line 312, in run
2021-07-07 21:58:00.839820: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
_run_main(main, args)
File "/home/ubuntu/anaconda3/envs/motion_deeplab/lib/python3.6/site-packages/absl/app.py", line 258, in _run_main
sys.exit(main(argv))
File "/home/ubuntu/yunjian/motion_deeplab/deeplab2/trainer/train.py", line 72, in main
FLAGS.num_gpus)
File "/home/ubuntu/yunjian/motion_deeplab/deeplab2/trainer/train_lib.py", line 200, in run_experiment
controller.evaluate(steps=config.evaluator_options.eval_steps)
File "/home/ubuntu/yunjian/motion_deeplab/models/orbit/controller.py", line 282, in evaluate
2021-07-07 21:58:00.840081: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
eval_output = self.evaluator.evaluate(steps_tensor)
File "/home/ubuntu/yunjian/motion_deeplab/models/orbit/standard_runner.py", line 344, in evaluate
eval_iter, num_steps, state=outputs, reduce_fn=self.eval_reduce)
File "/home/ubuntu/yunjian/motion_deeplab/models/orbit/utils/loop_fns.py", line 74, in loop_fn
outputs = step_fn(iterator)
File "/home/ubuntu/anaconda3/envs/motion_deeplab/lib/python3.6/site-packages/tensorflow/python/eager/def_function.py", line 780, in call
2021-07-07 21:58:00.840692: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
result = self._call(*args, **kwds)
File "/home/ubuntu/anaconda3/envs/motion_deeplab/lib/python3.6/site-packages/tensorflow/python/eager/def_function.py", line 840, in _call
return self._stateless_fn(*args, **kwds)
File "/home/ubuntu/anaconda3/envs/motion_deeplab/lib/python3.6/site-packages/tensorflow/python/eager/function.py", line 2829, in call
2021-07-07 21:58:00.841029: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.841384: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
return graph_function._filtered_call(args, kwargs)  # pylint: disable=protected-access
File "/home/ubuntu/anaconda3/envs/motion_deeplab/lib/python3.6/site-packages/tensorflow/python/eager/function.py", line 1848, in _filtered_call
2021-07-07 21:58:00.841919: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.842237: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
cancellation_manager=cancellation_manager)
File "/home/ubuntu/anaconda3/envs/motion_deeplab/lib/python3.6/site-packages/tensorflow/python/eager/function.py", line 1924, in _call_flat
2021-07-07 21:58:00.842551: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.842904: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
ctx, args, cancellation_manager=cancellation_manager))
File "/home/ubuntu/anaconda3/envs/motion_deeplab/lib/python3.6/site-packages/tensorflow/python/eager/function.py", line 550, in call
2021-07-07 21:58:00.843215: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
ctx=ctx)
File "/home/ubuntu/anaconda3/envs/motion_deeplab/lib/python3.6/site-packages/tensorflow/python/eager/execute.py", line 60, in quick_execute
inputs, attrs, num_outputs)
tensorflow.python.framework.errors_impl.InvalidArgumentError:  Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
[[{{node ParseSingleExample/ParseExample/ParseExampleV2}}]]
[[MultiDeviceIteratorGetNextFromShard]]
[[RemoteCall]]
[[IteratorGetNext]] [Op:__inference_eval_step_11410]
Function call stack:
eval_step
2021-07-07 21:58:00.843554: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.843883: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.844309: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.844679: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.844835: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.845372: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.845480: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.845700: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.846071: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.846429: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.846806: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.847188: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.847566: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.847957: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.848308: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.848663: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.849024: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.849314: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.849651: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.850048: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.850433: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.850796: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.851174: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.851542: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.851872: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.852309: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.852655: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.853005: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.853372: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.853777: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.854121: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.854466: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.854830: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.855111: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.855504: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.855864: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.856161: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.856533: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.856867: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.857240: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.857590: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.857939: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.858282: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.858656: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.859006: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.859322: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.859705: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.860125: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.860466: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.860779: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.861175: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.861490: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.861879: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.862221: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.862602: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.862925: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
2021-07-07 21:58:00.863304: W tensorflow/core/framework/op_kernel.cc:1767] OP_REQUIRES failed at example_parsing_ops.cc:94 : Invalid argument: Feature: image/segmentation/class/encoded (data type: string) is required but could not be found.
Process finished with exit code 1
The computer configuration is as follows：
cuda=10.0.130 cudnn=7.6.5
tensorflow=2.3.0
while I run 'deeplab2/compile.sh gpu'，It returns 'Done with configuration!'.

2021-07-08 10:07:07.386663: E tensorflow/core/grappler/optimizers/meta_optimizer.cc:581] layout failed: Invalid argument: Size of values 3 does not match size of permutation 4 @ fanin shape inDeepLab/PostProcessor/StatefulPartitionedCall/while/body/_85/while/SelectV2_1-1-TransposeNHWCToNCHW-LayoutOptimizer

Hi yilin0223,
Please follow our install guide: https://github.com/google-research/deeplab2/blob/main/g3doc/setup/installation.md
You will need tensorflow >= 2.5 and CUDA >= 11.2. Then, please verify, that you can execute (some) tests. Next, please follow https://github.com/google-research/deeplab2/blob/main/g3doc/setup/kitti_step.md to setup KITTI.
Please update your issue once you tried it again after following the above steps.

Hi yilin0223,
Please follow our install guide: https://github.com/google-research/deeplab2/blob/main/g3doc/setup/installation.md
You will need tensorflow >= 2.5 and CUDA >= 11.2. Then, please verify, that you can execute (some) tests. Next, please follow https://github.com/google-research/deeplab2/blob/main/g3doc/setup/kitti_step.md to setup KITTI.
Please update your issue once you tried it again after following the above steps.

thanks, follow the kitti step guide，I find the error, I don't replace the corresponding panptic_maps folder correctly。

While I got another error when for evaluation for AP eval
I0710 10:58:20.160958<PHONE_NUMBER>86816 api.py:446] Creating COCO objects for AP eval...
creating index...
index created!
Loading and preparing results...
Traceback (most recent call last):
File "/home/ubuntu/anaconda3/envs/deeplab2/lib/python3.6/site-packages/absl/app.py", line 312, in run
_run_main(main, args)
File "/home/ubuntu/anaconda3/envs/deeplab2/lib/python3.6/site-packages/absl/app.py", line 258, in _run_main
sys.exit(main(argv))
File "/home/ubuntu/yunjian/motion_deeplab/deeplab2/trainer/train.py", line 72, in main
FLAGS.num_gpus)
File "/home/ubuntu/yunjian/motion_deeplab/deeplab2/trainer/train_lib.py", line 200, in run_experiment
controller.evaluate(steps=config.evaluator_options.eval_steps)
File "/home/ubuntu/yunjian/motion_deeplab/models/orbit/controller.py", line 282, in evaluate
eval_output = self.evaluator.evaluate(steps_tensor)
File "/home/ubuntu/yunjian/motion_deeplab/models/orbit/standard_runner.py", line 349, in evaluate
return self.eval_end()
File "/home/ubuntu/yunjian/motion_deeplab/deeplab2/trainer/evaluator.py", line 301, in eval_end
ap_results = self._eval_ap_metric.result()
File "/home/ubuntu/anaconda3/envs/deeplab2/lib/python3.6/site-packages/tensorflow/python/keras/utils/metrics_utils.py", line 118, in decorated
raw_result = result_fn(*args)
File "/home/ubuntu/anaconda3/envs/deeplab2/lib/python3.6/site-packages/tensorflow/python/keras/metrics.py", line 192, in result_fn
return ag_result(*args, **kwargs)
File "/home/ubuntu/anaconda3/envs/deeplab2/lib/python3.6/site-packages/tensorflow/python/autograph/impl/api.py", line 695, in wrapper
raise e.ag_error_metadata.to_exception(e)
tensorflow.python.autograph.impl.api.StagingError: in user code:
/home/ubuntu/yunjian/motion_deeplab/deeplab2/evaluation/coco_instance_ap.py:274 result  *
    return self.detection_metric.result()
/home/ubuntu/yunjian/motion_deeplab/deeplab2/evaluation/coco_instance_ap.py:161 result  *
    self.metric_values = self.evaluate()
/home/ubuntu/yunjian/motion_deeplab/deeplab2/evaluation/coco_instance_ap.py:120 evaluate  *
    coco_dt = coco_gt.loadRes(detections)
/home/ubuntu/anaconda3/envs/deeplab2/lib/python3.6/site-packages/pycocotools/coco.py:327 loadRes  *
    if 'caption' in anns[0]:

IndexError: list index out of range

python-BaseException
I try to make a breakpoint in coco_instance_ap.py，while it doesn't work and stop at the breakpoint.

While I got another error when for evaluation for AP eval
I0710 10:58:20.160958<PHONE_NUMBER>86816 api.py:446] Creating COCO objects for AP eval...
creating index...
index created!
Loading and preparing results...
Traceback (most recent call last):
File "/home/ubuntu/anaconda3/envs/deeplab2/lib/python3.6/site-packages/absl/app.py", line 312, in run
_run_main(main, args)
File "/home/ubuntu/anaconda3/envs/deeplab2/lib/python3.6/site-packages/absl/app.py", line 258, in _run_main
sys.exit(main(argv))
File "/home/ubuntu/yunjian/motion_deeplab/deeplab2/trainer/train.py", line 72, in main
FLAGS.num_gpus)
File "/home/ubuntu/yunjian/motion_deeplab/deeplab2/trainer/train_lib.py", line 200, in run_experiment
controller.evaluate(steps=config.evaluator_options.eval_steps)
File "/home/ubuntu/yunjian/motion_deeplab/models/orbit/controller.py", line 282, in evaluate
eval_output = self.evaluator.evaluate(steps_tensor)
File "/home/ubuntu/yunjian/motion_deeplab/models/orbit/standard_runner.py", line 349, in evaluate
return self.eval_end()
File "/home/ubuntu/yunjian/motion_deeplab/deeplab2/trainer/evaluator.py", line 301, in eval_end
ap_results = self._eval_ap_metric.result()
File "/home/ubuntu/anaconda3/envs/deeplab2/lib/python3.6/site-packages/tensorflow/python/keras/utils/metrics_utils.py", line 118, in decorated
raw_result = result_fn(*args)
File "/home/ubuntu/anaconda3/envs/deeplab2/lib/python3.6/site-packages/tensorflow/python/keras/metrics.py", line 192, in result_fn
return ag_result(*args, **kwargs)
File "/home/ubuntu/anaconda3/envs/deeplab2/lib/python3.6/site-packages/tensorflow/python/autograph/impl/api.py", line 695, in wrapper
raise e.ag_error_metadata.to_exception(e)
tensorflow.python.autograph.impl.api.StagingError: in user code:
/home/ubuntu/yunjian/motion_deeplab/deeplab2/evaluation/coco_instance_ap.py:274 result  *
    return self.detection_metric.result()
/home/ubuntu/yunjian/motion_deeplab/deeplab2/evaluation/coco_instance_ap.py:161 result  *
    self.metric_values = self.evaluate()
/home/ubuntu/yunjian/motion_deeplab/deeplab2/evaluation/coco_instance_ap.py:120 evaluate  *
    coco_dt = coco_gt.loadRes(detections)
/home/ubuntu/anaconda3/envs/deeplab2/lib/python3.6/site-packages/pycocotools/coco.py:327 loadRes  *
    if 'caption' in anns[0]:

IndexError: list index out of range

python-BaseException
I try to make a breakpoint in coco_instance_ap.py，while it doesn't work and don't stop at the breakpoint.

see this issue for the 'index out of range'error, #33

Did the new checkpoint specification get rid of the IndexError? The commit referenced above will make the error message more clear if a model produces no thing instances (producing no detections and then the exception in COCO).


Prepare for new release of Confluence

Workflow links: https://github.com/atlassian-labs/atlassian-slack-integration-server/actions/runs/685373176, https://github.com/atlassian-labs/atlassian-slack-integration-server/actions/runs/685373964.

Integration tests for Confluence 7.11.2 passed, so I marked current version of the Confluence plugin v.2.1.3 as compatible.


failed to select a version for the requirement sp-core = "^6.0.0"

error: failed to select a version for the requirement sp-core = "^6.0.0"
candidate versions found which didn't match: 7.0.0
location searched: Git repository https://github.com/paritytech/substrate.git?branch=master
required by package substrate-api-client v0.7.0 (https://github.com/scs/substrate-api-client.git#b7f07a4e)

I have also encountered this problem, does anyone have a solution?

master needs to be updated to fix that. Alternatively, you can use one of the release branches here, like https://github.com/scs/substrate-api-client/tree/polkadot-v0.9.29.

I think that should be fixable by removing the version number completely. AFAIK that was only introduced because of the -dev version from substrate which required the explicit version tagging.

Yes, this is true, we can remove that.


How many bits?

There should be a link somewhere on this page
https://docs.microsoft.com/en-us/cpp/standard-library/complex-long-double?view=vs-2017
to long double type.

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

ID: b9b8e63a-155d-7dd9-2c05-6310a9a86d23
Version Independent ID: 862bb5c5-b9c0-7f80-85c2-b9af90e1eb27
Content: complex<long double>
Content Source: docs/standard-library/complex-long-double.md
Product: visual-cpp
GitHub Login: @corob-msft
Microsoft Alias: corob

@mrmsbarnes Do you have a target article in mind?

To Colin Robertson,
I thought pages referenced themselves when we submit feedback or click ‘No’ on ‘Is this page helpful’
·         I can’t find the article ( https://docs.microsoft.com/en-us/?view=vs-2017 Docs >  https://docs.microsoft.com/en-us/cpp?view=vs-2017 Visual C++ >  https://docs.microsoft.com/en-us/cpp/visual-cpp-in-visual-studio?view=vs-2017 Documentation) page now, but wherever it was it should reference this page:
https://docs.microsoft.com/en-us/cpp/c-language/type-long-double
From: Colin Robertson<EMAIL_ADDRESS>Sent: Wednesday, October 24, 2018 3:49 AM
To: MicrosoftDocs/cpp-docs
Cc: mrmsbarnes; Mention
Subject: Re: [MicrosoftDocs/cpp-docs] How many bits? (#495)
@mrmsbarnes https://github.com/mrmsbarnes  Do you have a target article in mind?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub https://github.com/MicrosoftDocs/cpp-docs/issues/495#issuecomment-432608282 , or mute the thread https://github.com/notifications/unsubscribe-auth/AH4vpIemw4dtMc8aog6riUqHbA8tIdq3ks5uoEWigaJpZM4X3OW9 .  https://github.com/notifications/beacon/AH4vpFslAUReib8tIAn87bWk9HDyriqiks5uoEWigaJpZM4X3OW9.gif

I remember now.  See original post.

@mrmsbarnes The closest equivalent in the C++ language reference is Fundamental Types (C++), but you have to search for the long double type on the page. I've got a fix with that link in progress that clarifies that Microsoft considers long double and double to be distinct types, but uses the same representation for both.

The fixed content is live.


use xarray's version of DataTree

At some point in the next few months, xarray will ship with a (slightly improved) version of DataTree, after which the xarray-datatree package will be deprecated / archived (and thus, abandoned).
To migrate, I believe the only thing to do is change the imports / package metadata / CI (but let's see).

xarray=2024.10.0 has been released, which publicly exposes DataTree


Error When Attempting to Post

Got another one for you Nathan. A new requirement in my project is to find the appropriate account manager ID and insert it when creating an account. My code:
    class SDataHelper
    {
        [SDataPath("accounts")]
        public class Account
        {
            [SDataProtocolProperty(SDataProtocolProperty.Key)]
            public string Id { get; set; }

            public string AccountName { get; set; }
            public string AccountManagerId { get; set; }
            public string Region { get; set; }

            public string Type = "End Users";
            public string Status = "Active";
        }....

        public Account InsertAccount(string company, string RSM, string region)
        {
            var account = new Account
                              {
                                AccountName = company,
                                AccountManagerId = RSM,
                                Region = region
                              };

            account = _client.Post(account);

            return account;
        }

However, upon the attempted post, I get the following error:

Invalid index 14 for this OleDbParameterCollection with Count=14.

After some Googling, it appears that it might be that Account Manager ID is being mapped twice? I know that earlier, before this new requirement, the business logic was creating the accounts with "ADMIN" in the Account Manager ID field. Any insight?

I wasn't able to reproduce your error but in general you should use a resource property for relationships like this. In your particular case, rename the property to AccountManager and pass it an instance with just the Key property populated. You can use either a typed User object if you have one or an untyped SDataResource.
var account = new Account
    {
        AccountName = company,
        AccountManager = new SDataResource {Key = RSM},
        Region = region
    };
account = client.Post(account);

Thanks Nathan, will try that!

That did the trick! Now why did that work as opposed to the way I was doing it?

I can't say off the top of my head but that would be a server-side issue.

Got it, thanks again!


Enable selective fields in nested association

Why
In current implementation, fields option is ignored in nested association.
What
Support fields option in nested association.
Diff
test_fields_with_nested_associations_include_option_with_sub_fields fails in the current 0-10-stable branch.
fields option in commets.author is ignored, which causes this error.
[2020/03/23 16:13:36] ~/.go/src/github.com/wantedly/active_model_serializers (0-10-stable)
$ BUNDLER_VERSION=1.17.3 bundle exec rake test
.
.
.
  1) Failure:
ActiveModelSerializers::Adapter::Json::Collection#test_fields_with_nested_associations_include_option_with_sub_fields [/Users/minami/.go/src/github.com/wantedly/active_model_serializers/test/adapter/json/collection_test.rb:175]:
--- expected
+++ actual
@@ -1 +1 @@
-{:posts=>[{:id=>1, :comments=>[{:id=>3, :author=>{:id=>4}}], :author=>{:name=>"Steve K."}}, {:id=>2, :comments=>[], :author=>{:name=>"Steve K."}}]}
+{:posts=>[{:id=>1, :comments=>[{:id=>3, :author=>{:name=>"John L."}}], :author=>{:name=>"Steve K."}}, {:id=>2, :comments=>[], :author=>{:name=>"Steve K."}}]}

CI fails when Ruby version is 2.3.8. But this is not caused by the change of this PR. I confirmed that same failure occurs in current 0-10-stable branch (cf. https://github.com/wantedly/active_model_serializers/pull/6)

cf. https://github.com/wantedly/active_model_serializers/pull/5/checks?check_run_id=526734646

Thanks a lot! 😄


Adding files in rdk-gstreamer-utils-platform repo

Merged when asked by Arun, to fix up a license scan oddity


electrode

May I ask what electrode you use？

We used OpenBCI's gold cup electrodes!

We used OpenBCI's gold cup electrodes!

Thank you！The project is very nice！Is there any relevant explanation for the filter circuit? I'm a novice. I'm afraid that there will be large deviation in different environments.


[Snyk] Upgrade @types/lodash from 4.14.182 to 4.14.184

This PR was automatically created by Snyk using the credentials of a real user.Snyk has created this PR to upgrade @types/lodash from 4.14.182 to 4.14.184.

:information_source: Keep your dependencies up-to-date. This makes it easier to fix existing vulnerabilities and to more quickly identify and fix newly disclosed vulnerabilities when they affect your project.

The recommended version is 2 versions ahead of your current version.
The recommended version was released a month ago, on 2022-08-19.

Release notes

Package name: @types/lodash

4.14.184 - 2022-08-19

4.14.183 - 2022-08-16

4.14.182 - 2022-04-18

    from @types/lodash GitHub release notes

Note: You are seeing this because you or someone else with access to this repository has authorized Snyk to open upgrade PRs.
For more information:
🧐 View latest project report
🛠 Adjust upgrade PR settings
🔕 Ignore this dependency or unsubscribe from future upgrade PRs

This is an issue with types, will need to fix the build and test.


Timeout option

Some of websites are very slow. Is there an option to set timeout? link-check has it.

There's a theme of issues that follow the pattern "link-check supports x, MLC should support x." It seems to me a reasonable expectation of function, but current architecture demands that upstream additions features require downstream implementation.
I'm not a JavaScript dev by any means, but casual read of the code suggests MLC is a consumer of link-check's API rather than an extension. It seems natural that MLC should enhance link-check with markdown-specific methods rather than wrapping them in another layer of abstraction.
How much effort would be required to extend link-check in the class-sense instead of consuming it? I don't know the answer but it may be a good roadmap question.


Nuxt 3.7 - "Starting nuxt..." takes 20 seconds and after that devtools don't open with many errors

Environment
Nuxt project info:                                                                                10:41:32 AM

Operating System: Linux
Node Version:     v18.14.2
Nuxt Version:     3.7.0
CLI Version:      3.7.0
Nitro Version:    2.6.1
Package Manager<EMAIL_ADDRESS>Builder:          -
User Config:      ssr, runtimeConfig, modules, alias, serverDir, dir, components, imports, typescript, experimental, css, build, devtools, vite, tailwindcss, postcss, apollo
Runtime Modules<EMAIL_ADDRESS><EMAIL_ADDRESS><EMAIL_ADDRESS>Build Modules:    -

Reproduction
https://github.com/martinszeltins/nuxt-errors
Describe the bug
When I run pnpm run dev and then open my app in the browser it says "Starting nuxt...." which takes 20 seconds before my app is shown. This also happens every time nuxt.config.ts file is changed and Nuxt is restarting... (also takes so long). On Docker it takes even longer - 70 seconds!!! And I have no clue why this is happening because my app is very very small, I just created a new nuxt project, added graphql, fontawesome, primevue and nothing more.
And then when the app finally opens and I want to open the devtools it shows many errors in the console and the devtools never open. Again, I have no idea why this is happening.
Errors in console:
client.ts:77 WebSocket connection to 'ws://localhost:35547/_nuxt/' failed:
setupWebSocket @ client.ts:77
(anonymous) @ client.ts:67

client.ts:105 [vite] server connection lost. polling for restart...
client.ts:339     GET http://localhost:35547/_nuxt/ net::ERR_SOCKET_NOT_CONNECTED
ping @ client.ts:339
waitForSuccessfulPing @ client.ts:352
(anonymous) @ client.ts:106

client:1 Failed to load module script: Expected a JavaScript module script but the server responded with a MIME type of "text/html". Strict MIME type checking is enforced for module scripts per HTML spec.

client:1 Failed to load module script: Expected a JavaScript module script but the server responded with a MIME type of "text/html". Strict MIME type checking is enforced for module scripts per HTML spec.

client.ts:77 WebSocket connection to 'ws://localhost:35547/_nuxt/' failed:
setupWebSocket @ client.ts:77
(anonymous) @ client.ts:67

client.ts:105 [vite] server connection lost. polling for restart...
client.ts:339     GET http://localhost:35547/_nuxt/ net::ERR_SOCKET_NOT_CONNECTED
ping @ client.ts:339
waitForSuccessfulPing @ client.ts:352
(anonymous) @ client.ts:106

client.mjs:104 Uncaught (in promise) Nuxt DevTools client injection failed
iframe.onload @ client.mjs:104
load (async)
getIframe @ client.mjs:101
(anonymous) @ FrameBox.vue:20
callWithErrorHandling @ chunk-4OF65L5M.js:1565
callWithAsyncErrorHandling @ chunk-4OF65L5M.js:1573
getter @ chunk-4OF65L5M.js:3108
run @ chunk-4OF65L5M.js:423
job @ chunk-4OF65L5M.js:3171

Screenshot:

Additional context
No response
Logs
No response

Exactly the same issue on my side too. I have an even simpler config:
`// https://nuxt.com/docs/api/configuration/nuxt-config
import { URL, fileURLToPath } from 'url'
import { dirname, join } from 'path'
import { devCMSUrl } from '../../devoptions'
const baseDir = join(dirname(fileURLToPath(import.meta.url)), '.')
const configDir = fileURLToPath(new URL('./config', import.meta.url))
export default defineNuxtConfig({
imports: {
dirs: ['stores', 'types', 'composables/**', 'enums', 'utils']
},
components: {
dirs: [
// base
{
path: './components/base'
},
// only base
{
path: '~/components/dev',
prefix: 'Dev'
},
// widgets
{
path: './components/widgets',
global: true,
isAsync: true
}
]
},
alias: {
config: configDir,
// just in case we need something from the base nuxt project
base: baseDir
},
modules: [
'@nuxtjs/tailwindcss',
'@pinia/nuxt',
'@nuxtjs/apollo',
'@nuxtjs/i18n',
'@nuxtjs/google-fonts',
'@vueuse/nuxt',
'@nuxt/devtools',
'nuxt-headlessui',
'nuxt-swiper'
],
pinia: {
autoImports: [['defineStore', 'definePiniaStore']]
},
apollo: {
clients: {
default: {
httpEndpoint: ${devCMSUrl}/graphql
}
}
},
headlessui: {
prefix: 'UI'
},
runtimeConfig: {
public: {
cmsUrl: devCMSUrl,
deployEnv: 'dev',
ims: {
scriptUrl: 'https://some-script',
gwApiUrl: '/_auth'
}
}
},
i18n: {
strategy: 'no_prefix',
locales: ['en-GB', 'en-US'], // make configurable
detectBrowserLanguage: {
useCookie: true,
cookieKey: 'userLocal',
redirectOn: 'root'
}
},
googleFonts: {
families: {
Roboto: {
wght: [100, 300, 500, 700, 900],
italic: [100, 300, 500, 700, 900]
}
}
},
typescript: {
// needed to include global declaration overrides in typecheck
includeWorkspace: true
},
build: {
transpile: [
'tslib' // version 2.5.3 introduced module export issues with apollo package
]
},
devtools: {
enabled: true
},
tailwindcss: {
// aims at project local tailwind config
configPath: '~/tailwind.config.js'
},
nitro: {
devProxy: {
'/_auth': {
target: 'https://some-api-we-needed-for-cors',
changeOrigin: true,
secure: false
}
}
}
})
`

If I enable power saving mode on my computer, it takes more than 10 minutes for Nuxt to start, my computer goes to sleep in such a long time. 😅
Look at these numbers...
ℹ Using default Tailwind CSS file                                                                                nuxt:tailwindcss 10:04:03 AM
✔ Nuxt DevTools is enabled v0.8.0 (experimental)                                                                                10:04:07 AM
ℹ Tailwind Viewer: //_tailwind/                                                                                nuxt:tailwindcss 10:04:08 AM
ℹ [nuxt] compiled routes.mjs in 1334.67ms                                                                                10:04:28 AM
ℹ [nuxt] compiled types/imports.d.ts in 8447.46ms                                                                                10:04:35 AM
ℹ [nuxt] compiled plugins/server.mjs in 16063.79ms                                                                                10:04:43 AM
ℹ [nuxt] compiled plugins/client.mjs in 39523.6ms                                                                                10:05:06 AM

 ERROR                                                                                10:05:59 AM
[vue-tsc] Found 0 errors. Watching for file changes.

ℹ ✨ optimized dependencies changed. reloading                                                                                10:07:34 AM
ℹ Vite client warmed up in 101684ms                                                                                10:07:42 AM
✔ Nitro built in 132464 ms                                                                                nitro 10:09:02 AM

After adding ~10 css files, now I have to wait 3 minutes until Nuxt starts 🤯 This feel very wrong...

Does it work faster again when removing some modules, e.g. tailwind? 🤔

Nuxt is extremely slow at startup for me as well.  I don't have the quickest computer on the block, but this feels extraordinary.  I didn't have an issue until I upgraded to 3.7.  Even after the following screenshot, I'm still stuck on the start screen.

Actually, you can scratch my last post.  I had a couple of experimental settings in my nuxt config which seem to have been the problem.  I had the experimental.watcher: 'chokidar' set from a previous version issue.  I removed it and now it seems to be working properly.

cc: @antfu
possibly same issue as https://github.com/nuxt/nuxt/issues/22797

It's because of these lines changing the Vite HMR port and causing DevTools to fail to connect.
https://github.com/martinszeltins/nuxt-errors/blob/1b2f4dbf4d01fc26dec34bfd7d7221741ecbdec7/common/config/nuxt/vite.config.ts#L3-L7
I will see how we can fix it on DevTools, while meanwhile you can workaround by commenting out them.
There are many moving parts in the reproduction. If possible, next time it would be better if could provide reproductions that are minimal by removing modules/configs one by one. So that maybe you could identify the root cause more easily, maybe even before creating the issue. Thank you

For everyone else who encountered similar issues, please also share your minimal reproductions. We are happy to help :)

There are many moving parts in the reproduction. If possible, next time it would be better if you could provide reproductions that are minimal by narrowing down modules/configs one by one. So that maybe you could identify the root cause more easily, maybe even before creating the issue. Thank you

The extremely slow Nuxt starting time can be achieved only if multiple modules, CSS files, composables are added. The more files I add the slower the startup time gets. I have no clue what is causing it exactly.

I think the slowness here should be resolved in the next nuxi release via https://github.com/nuxt/cli/pull/122. Until then, you can check https://github.com/nuxt/cli/issues/109 for some workarounds.


Adding the support for the configurable token sources.

This includes the actual list of checks and customisations such as cookie or query param names. Fixes #38.

@BTBurke Is there anything I can improve in the pull request? :)

Oh, I see. No problem. Have a great time!


stdenv: prune libtool files by default

Motivation for this change
Spotted in the wild:
# Generated by ltmain.sh - GNU libtool 1.5.22-OpenLDAP (1.1220.2.365 2005/12/18 22:14:06)

which pruneLibtoolFiles fails to prune as is.
/cc @orivej
EDIT: now extended to pruning libtool files by default
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[ ] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Assured whether relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

:+1: on enabling by default. This seems like a pretty common issue, just recently upgrading hunspell, cyrus_sasl and iptables caused downstream failures due to new -ls in the .la files. So there's definitely a risk with plain upgrades too.

This pull request has been mentioned on Nix community. There might be relevant details there:
https://discourse.nixos.org/t/prs-ready-for-review-december/1711/4

@matthewbauer I wonder if this would break staticPkgs?

It only prunes .la files where old_library='' which is meant to avoid breaking static builds, as I understand it.

There were some regressions, but not too many and almost all trivial to fix: 64edccb46.


Depth estimation in evaluate

hi~ i want to know why the different in the utils.py evaluate function with origin Densedepth code
your code in line  131 in utils.py:
`
Compute errors per image in batch
   for j in range(len(true_y)):

        errors = compute_errors(true_y[j], (0.5 * pred_y[j]) + (0.5 * np.fliplr(pred_y_flip[j])))

        for k in range(len(errors)):
            depth_scores[k][(i*bs)+j] = errors[k]

e = depth_scores.mean(axis=1)

#==============
`
origin Densedepth code line 131 in utils.py:
`
Compute errors per image in batch
    for j in range(len(true_y)):
        predictions.append(   (0.5 * pred_y[j]) + (0.5 * np.fliplr(pred_y_flip[j]))   )
        testSetDepths.append(   true_y[j]   )

predictions = np.stack(predictions, axis=0)
testSetDepths = np.stack(testSetDepths, axis=0)

e = compute_errors(predictions, testSetDepths)

`
The part of code make the rmse value change very much
Thanks

I made changes to the utils to have different types of visualizations.


Add support for PreAuthKey tags/automatic tagging

[X] read the CONTRIBUTING guidelines
[x] raised a GitHub issue or discussed it on the projects chat beforehand
[X] added unit tests
[X] added integration tests
[ ] updated documentation if needed
[ ] updated CHANGELOG.md

These changes add the ability to automatically tag nodes when activated with a preauthkey as is available in SaaS
CreatePreAuthKey and like APIs were expanded to optionally accept a list of tags and the CLI arguments were updated. The database schema was also updated with a new table to store tags associated with preauth keys.
Keys associated to a preauthkey are applied to a new or existing Machine's ForcedKeys when registered/refreshed

just to note that there's a small test break I'll need to push a change to depending on which order this and #763 get merged (if either is accepted

fixed broken test from merge

np will have a crack tomorrow - just noticed my local linting is broken too so will address both

np will have a crack tomorrow - just noticed my local linting is broken too so will address both

Thanks ! Maybe you'll want to wait for an owner review first :smile:

np will have a crack tomorrow - just noticed my local linting is broken too so will address both

Thanks ! Maybe you'll want to wait for an owner review first smile

Sorry this comment was for another PR. No need for approval to add tests they are always welcome :smile:

haha all good, fwiw just about to push a fix for the linting issues but not the unit test as the point where tags is applied is in protocol_common.go as part of machine registration/refresh as this most closely follows SaaS behaviour.
Let me know if an equivalent integration test is desired - just a bit of extra effort to stand up a new test case in there 🥲

@kradalby thanks for the review - have merged in your recommendations

Seems like there is a lint error, and could you add changelog entry for this one as well?


First draft of a community-contributed blog post on multi-tenant backup

Minor edits made for clarity and to pass the linter
Added image

Does this PR need a docs update or release note?

[x] :no_entry: No

@meuchels Can you please review this too?

works for me


Don't try to clone

hi, have tested on real device ios 15.3.1 and on launch camera xcode bug and
console.
2022-03-25 09:03:39.654284+0400 Fidy[31740:7440464] [native] VisionCamera.didSetProps(:): Updating 13 prop(s)...
2022-03-25 09:03:39.654894+0400 Fidy[31740:7441026] [native] VisionCamera.configureCaptureSession(): Configuring Session...
2022-03-25 09:03:39.654932+0400 Fidy[31740:7441026] [native] VisionCamera.configureCaptureSession(): Initializing Camera with device com.apple.avfoundation.avcapturedevice.built-in_video:0...
2022-03-25 09:03:39.655000+0400 Fidy[31740:7441026] [native] VisionCamera.configureCaptureSession(): Adding Video input...
2022-03-25 09:03:39.659604+0400 Fidy[31740:7440676] FrameProcessorBindings: Setting new frame processor...
2022-03-25 09:03:39.659643+0400 Fidy[31740:7440676] FrameProcessorBindings: Adapting Shareable value from function (conversion to worklet)...
2022-03-25 09:03:39.659872+0400 Fidy[31740:7440676] FrameProcessorBindings: Successfully created worklet!
2022-03-25 09:03:39.659944+0400 Fidy[31740:7440696] FrameProcessorBindings: Converting worklet to Objective-C callback...
Assertion failed: (object->ctx == ctx_ && "Don't try to clone an object backed by a different Runtime"), function cloneObject, file JSCRuntime.cpp, line 618.
dyld4 config: DYLD_LIBRARY_PATH=/usr/lib/system/introspection DYLD_INSERT_LIBRARIES=/Developer/usr/lib/libBacktraceRecording.dylib:/Developer/usr/lib/libMainThreadChecker.dylib:/Developer/Library/PrivateFrameworks/DTDDISupport.framework/libViewDebuggerSupport.dylib

I had the same issue.
iOS: 15.4
react-native-vision-camera: 2.13.0
react-native-reanimated: 2.2.4
vision-camera-code-scanner: 0.16

@khasbilegt i solved for update react-native-reanimated for 2.3.1