A repeatTableRow comment is ignored when the table is encapsulateb by a displayTableIf comment

Describe the bug
A  repeatTableRow comment is ignored when the table is encapsulateb by a displayTableIf
To Reproduce
Steps to reproduce the behavior:

Create a table with iterable data (repeatTableRow comment on a row of a Table)
Create a displayTableIf(true) comment on the Table

Expected behavior
The table should be visible but with the data, not with the variable inside the row and not with the comment that use the repeatTableRow processor
Desktop (please complete the following information):

OS: [Ubuntu 22.04]
Java version: [11, 17]
docx4j version: 11.4.8
docx-stamper version [1.4.7 - 1.5.0]

Additional context
If you know how to do it, or if you want help, I just need someone to explain me what to do or where to find my way :)
I know with Nested comment, something was done to allow that ... so if I can apply the same sort of patch, I will happy to help :)

Would you have a sample document that shows the problem.
I made a change to my own codebase to support more than one comment per paragraph...
Not sure whether this affects the code base here or not.
Here, (broadly is the change I made):
CommentProcessorRegistry.java
    List<Comments.Comment> commentList = CommentUtil.getCommentsFor(paragraph, document);

    for (Comments.Comment comment : commentList) {
      Optional<CommentWrapper> commentWrapper = runCommentProcessors(document, comments, proxyBuilder, comment, paragraph, null);
      if (commentWrapper.isPresent()) {
        commentWrapperList.add(commentWrapper.get());
      }
    }```

CommentUtil.java
```java
	public static List<Comments.Comment> getCommentsFor(ContentAccessor object,
												 WordprocessingMLPackage document) {

		List<Comments.Comment> commentList = new ArrayList<>();

		try {
			for (Object contentObject : object.getContent()) {
				if (contentObject instanceof CommentRangeStart) {
					try {
						BigInteger id = ((CommentRangeStart) contentObject).getId();
						CommentsPart commentsPart = (CommentsPart) document.getParts()
								.get(new PartName("/word/comments.xml"));
						Comments comments = commentsPart.getContents();
						for (Comments.Comment comment : comments.getComment()) {
							if (comment.getId().equals(id)) {
								commentList.add(comment);
							}
						}
					}
					catch (InvalidFormatException e) {
						logger.warn(String.format(
								"Error while searching comment. Skipping object %s.",
								object), e);
					}
				}
			}
			return commentList;
		}
		catch (Docx4JException e) {
			throw new DocxStamperException(
					"error accessing the comments of the document!", e);
		}
	}

Maybe if you can provide a test case we'd be able to fix it.
Keep in mind that there are actually 2 branches to maintain, one for pre jakarta migration (master-javax) and the other for jakarta ee (master).

We are moving out of the jakarta migration now, we are still interested in a sample document and code reproducing the error

Finally reproduced the issue in RegressionTest#test114, won't be covered in 2.7 in the end, as it require a too big refactoring to do properly. Moving this to 3.0.
This specific use case can be mitigated by making the displayIf comment on only a small part of the table, not covered by the other comments.


Duplicate "Go To Declaration"

Now there are two "Go to declaration" commands - one of Atom and one of ghd-mod sub-menu.
It will be more less confusing if it is only one common command integrated with Atom's one.
This of course is very small issue.

There's a reason for this. Atom's go-to-decl is overriden by ide-haskell-hasktags. Ghc-mod's one is there for the sake of completeness, and it can give better results than hasktags one in some cases, but it's slower and lacks history (i.e. you can't automatically go 'back' once you've gone to declaration). Long story short, I just do both.

Thanks for the full answer!


How do I recognize 8kHz audio for speech recognition sdk?

what is the exact option or parameter for handling input audio's sample rate?

You can use sox command which can help you see and modify the audio parameters.

Currently we do not support 8Khz audio for speech recognition. Please use goldwave or any other tool of your choice to convert the audio to 16Khz, 16 bit and mono wave file for recognition. Do let us know if you have more questions

I am closing this for the time being.

@chinmayembedded I am really sorry for the information. You can recognize 8khz wave file using speech sdk. the format should be 8Khz, 16 bits and mono.
Please use FromWavFileInput https://docs.microsoft.com/en-us/cpp/cognitive-services/speech/audio-audioconfig.
In our documentation it says that we only support 16Khz but we will go ahead and update the documentation. Do let us know if you still face any issue.
I am closing it for the time being.

Hi!,
Is the class WavStream.java updated for 8kHz WAV support? seems like it fails if it detects a sample rate not equal to 16kHz.
Thanks-

@carlossapnucivicom Thanks a lot for pointing this out to us. We should change this. Right now Speech sdk support all the wav formats.


Manage VisualStudioRazorParser lifetime.

Exposed VisualStudioRazorParser, DocumentStructureChangedEventArgs and ICanHasContextChangedListener as ways to consume the new parser for a Razor document.
Split the VisualStudioRazorParser into an abstract base and an implementation to avoid internal constructors.
Changed the parser and corresponding smart indenter to take in document trackers, template engine factories and parser context change listeners. Of these additions the parser context change listeners will be deprecated once we own the TagHelper discovery mechanisms.
Changed how the parser manages its internal parsing life cycle. It now creates template engines when the document tracker tells it to. So when project changes happen or new documents are opened the parser will re-instantiate its internal parsers to ensure that they're parsing against the correct configurations.
Split the VisualStudioDocumentTrackerFactory into a provider and a factory. The provider exposes the old GetTracker methods where the factory is the text view connection listener implementation.
Changed the code document provider to now use the parser provider in order to locate code documents associated with buffers. Prior to this that logic was hard coded.
Removed old template engine reconstruction logic in the document tracker now that the parser owns that piece.

#1630

🆙 📅, no longer in design


feat: Add knip

Description

https://github.com/webpro/knip#default-configuration
Not sure where to place it so I created a new category dependencyAnalysis based on https://bestofjs.org/projects/knip
Linked Issues
Additional context

Knip is more of a generic project linter, since it finds unused files, dependencies, exports, etc. :)


Removed unused bitstream_init_with_seed

Its ok if you want to keep this, just deny the PR. I found it a bit confusing to search where it is used.


Building the Data Migration Tool

A question. I downloaded this : https://github.com/azure/azure-documentdb-datamigrationtool
And thought clicking on "Build" in Visual Studio Version 15.4.4 would make the exe; but instead it returned 50 errors. Does someone have the exe that I can run? I'd love to get past this new roadblock! :-)

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

ID: 9edf1df2-588e-01ff-6d1c-234b8e51d550
Version Independent ID: 27873c08-b6cc-a52f-f277-ff9818a5e4d2
Content: Database migration tool for Azure Cosmos DB
Content Source: articles/cosmos-db/import-data.md
Service: cosmos-db
GitHub Login: @AndrewHoh
Microsoft Alias: anhoh

Resolved by Ben in https://github.com/Azure/azure-documentdb-datamigrationtool/issues/45. Download his "release" zip and run in visual studio 17.

@philipvago Glad to hear you found the .exe. We will now proceed to close this thread. If there are further questions regarding this matter, please reopen it and we will gladly continue the discussion.


fix dataset for pairwise task

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
6 unchanged lines in 5 files lost coverage.
Overall coverage remained the same at 96.314%

Files with Coverage Reduction
New Missed Lines
%

dooc/nets/init.py
1
88.57%

dooc/nets/mutations.py
1
95.78%

dooc/pipelines.py
1
96.2%

dooc/models.py
1
95.0%

dooc/datasets.py
2
96.43%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
392

Relevant Lines:
407

💛  - Coveralls

Pull Request Test Coverage Report for Build<PHONE_NUMBER>
Details

1 of 1 (100.0%)  changed or added relevant line in 1 file are covered.
6 unchanged lines in 5 files lost coverage.
Overall coverage remained the same at 96.314%

Files with Coverage Reduction
New Missed Lines
%

dooc/nets/init.py
1
88.57%

dooc/nets/mutations.py
1
95.78%

dooc/pipelines.py
1
96.2%

dooc/models.py
1
95.0%

dooc/datasets.py
2
96.43%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
392

Relevant Lines:
407

💛  - Coveralls


Expose form property in page store

Describe the problem
The new actions and forms api is very good, but I was very surprised (probably misread the docs and migration guide) to find out that the form prop is not exposed in the page store.
Since we can have both export let data and $page.data, I think it would make a lot of sense to have to same for form.
Moreover, if I want to access the form property outside of +page.svelte (like in a +layout.svelte or a component further down the tree), the current api requires me to do a lot of setup, like for example populating a store with the data, exposing the data through context or passing the data as a prop. For one page, this is not too bad, but having to do this for every route is very cumbersome.
I realize I can access the result prop in the enhance callback, but again, it requires more setup if I want to use this data to populate input values and errors, and it would not work without js.
Describe the proposed solution
Add the form prop to the page store.
Alternatives considered
Do this in userland, like using a store, context or passing the data as prop. In every page.
Importance
would make my life easier
Additional Information
This issue brought the issue count back to 300, sorry for this :)

I would like to give this a go.

Sure, go ahead :) Code to change will mostly be in write_root.js where the root Svelte component is generated that updates the page store; and typings.


Apple ID verfication not working

I migrated from Icloud3 2.4.7 to Icloud3 beta 15. All seemed to be working at least as far as the migration. Once I restarted HA if says that the integration has to be reconfigured. It needs the Apple ID Verification code. When I click on Reconfigure it says I should have received a code on one of my devices - yet nothing happen. No code appears on my Ipad, Iphone or Apple Watch. It seems that the code is not requested from Apple.
What can I do to get it to request one or reset it?

I cannot select anything else in the integration.

Managed to get the apple ID triggered. I had to delete the folder /config/.storage/icloud. After a restart of HA was the Apple ID triggered.

FYI - There ae 2 ways to get it to trigger:

Event Log > Actions > Reset iCloud Interface
Devices & Services > iCloud3 > Configure > iCloud Login Credentials > Reset and Reauthenticate

This does what you did, delete the .storage/icloud cookies and session files.


feat: Enable automatic updates from renovate

Goal
Automatically update Python packages to:

Install security updates in a timely manner.
Keep libraries up to date, and not get stuck on old versions with many breaking changes.

Deployment

[ ] renovate is allowed on your repository
[ ] renovate-approve is allowed on your repository
[x] All dependabot and auto-merge files are removed from your repository. While, not necessary, they will conflict with each other.
[ ] Allow auto-merge is enabled in your GitHub repository settings. While not necessary this will allow Renovate to use Github's default auto-merging strategy.

Reference
Tickets:

https://getpocket.atlassian.net/browse/DIS-576

Pocket's Renovate config:

https://github.com/Pocket/renovate-config

I understand the idea but python package ecosystem is very brittle and usually I prefer not to touch the dependencies when things work. Updating one package can cause ugly conflicts and since they are open source there are no guarantees of backward compatibility. What security risks do you use for RecAPI taking into account that it's behind the VPN and accessed only by internal services?

I think Evgeny makes some valid points, and for some repositories locking down dependencies would be the best strategy. Here is why I think it is better to update packages on recommendation-api more frequently:

For the last year or so, we've been relying on test coverage alone to add/update packages in this repo. I don't think we've had any incidents with breaking changes in package updates.
There is already a small risk today that our test coverage doesn't catch a breaking change when we add/update a package, because we don't pin all packages today. Automatic updates don't change that, but they do make it easier to find the cause. We will be notified when this happens by Sentry alerts and API monitoring for NewTab.
While a VPN limits the attack surface, it doesn't eliminate it. It's less effort to update packages than to investigate whether a security bug can be exploited.
Working through conflicts isn't avoidable in an actively used repo. The question is only whether we want to work through them gradually as part of continuous delivery, or only as needed. For recommendation-api I think the former is worth the investment.

We decided that weekly updates with human review would offer the best balance between avoiding an update backlog, and minimizing risk from breaking changes.
However, I don't see this as a priority now, so am closing this PR for now.


Updated examples of polling trigger behaviour

@swylezol,
Thanks for your contribution as a Microsoft full-time employee or intern. You do not need to sign a CLA.
Thanks,
Microsoft Pull Request Bot


[7.x] Implement mail factory on mailfake

Implement mail factory on mailfake, for some reason without this when calling Mail::fake() on a request where a notification email is sent the following error is thrown:
TypeError : Argument 1 passed to Illuminate\Notifications\Channels\MailChannel::__construct() must implement interface Illuminate\Contracts\Mail\Factory, instance of Illuminate\Support\Testing\Fakes\MailFake given
Notification email example:
$user->notify(new UserCreatedNotification($user));

<?php

namespace App\Notifications;

use App\EmailSettings;
use Illuminate\Auth\Passwords\DatabaseTokenRepository;
use Illuminate\Auth\Passwords\PasswordBroker;
use Illuminate\Bus\Queueable;
use Illuminate\Contracts\Queue\ShouldQueue;
use Illuminate\Database\ConnectionInterface;
use Illuminate\Notifications\Messages\MailMessage;
use Illuminate\Notifications\Notification;
use Illuminate\Support\Facades\DB;
use Illuminate\Support\Facades\Hash;
use Illuminate\Support\Str;

class UserCreatedNotification extends Notification
{
    use Queueable;

    public $user;

    public $token;

    /**
     * Create a new notification instance.
     *
     * @param $user
     */
    public function __construct($user)
    {
        $this->user = $user;

        /** @var PasswordBroker $broker */
        $broker = app('auth.password.broker');
        $this->token = $broker->createToken($user);
    }

    /**
     * Get the notification's delivery channels.
     *
     * @param  mixed  $notifiable
     * @return array
     */
    public function via($notifiable)
    {
        return ['mail'];
    }

    /**
     * Get the mail representation of the notification.
     *
     * @param  mixed  $notifiable
     * @return MailMessage
     */
    public function toMail($notifiable)
    {
        $greeting = EmailSettings::where('notification_type', get_class($this))->first()->greeting;
        return (new MailMessage())
            ->greeting($greeting)
            ->line(
                sprintf(
                    'Welcome %s, you have been added as a user to %s',
                    $this->user->first_name,
                    config('app.name')
                )
            )
            ->action('Login Here', route('password.reset', ['token' => $this->token]));
    }
}

But MailFake doesn't have a factory method?

@xHeinrich the mail fake cannot be used here because the notification doesn't sends a Mailable. It sends a SimpleMessage instance. You need to use the Notification fake.


[Website]fix the method params output in doc

if this.props.params.length is 0, then the result will be 0

@hramos

Is the current behavior that 0 will be rendered when a method has 0 params? Can you post an "after" screenshot of what the docs look like after the fix is applied?

@hramos  I tried to catch an "after" screenshop, but it took hours for me to clone this repo and npm install...so I cancelled.
But I can give you this:
the original code is
this.props.params && this.props.params.length && this.props.params.map(...)

Let's mimic the result:

@hramos ?

@janicduplessis ?

What does this change do? Would it render getString() in the docs, rather than getString(0)?

I can verify this fixes the bug. Here's an after screenshot:

Thanks for finding it! This was very clowny and we've had it in the docs for a long time.
I edited the code a bit to make it clearer we're checking for a non-empty array.
@facebook-github-bot shipit

@mkonicek The point here I guess is to check whether params is an Array (by checking whether length exists).
If params is 100% array, then this length check can be simplily removed. If length is 0, map function will return an empty array, which has no problem in JSX.
But if params can be types other than array, then this.props.params.length !== 0 is unsafe.

@mkonicek do you still want to import this? Looks like that was the intention, but the GitHub bot, I believe, will only handle the shipit command when it's a standalone comment.
Both tests aren't passing as of this writing, but I've restarted the builds to verify.

It looks like this is failing in Circle and the failure is legitimate.

Let's see if tests are still failing.


Script doesn't run - Validator closes straightaway

I've just tried to run the validator and it instantly opens and closes and doesn't run. Has this avenue of verifying been blocked off?

I believe it has, I attempted to update the URL's and still same issue.

I believe it has, I attempted to update the URL's and still same issue.

This version hasn't been supported since April  2023 when they made the switch to PTCGOLive and started using recaptcha V3 in their web API.
I have newer version that work but are no longer public as I got too many emails from folks begging for stuff / asking for tech support 👎


Revert "fix missing shop log blueprint"

Reverts hngx-org/spitfire-super-admin-one#106
Shop logs has been moved to logs blueprint

@Freeman-kuch @Dev-wonderful


tor: <IP_ADDRESS> -> <IP_ADDRESS>

Updates Tor to <IP_ADDRESS>.
There have been two security vulnerabilities, the Tor team advises to update asap.
See: https://gitlab.torproject.org/tpo/core/tor/-/raw/release-0.4.8/ReleaseNotes
Patch created by running passthru.UpdateScript.
GPG signature of release has been verified successfully.
Things done

Built on platform(s)

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

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

[ ] sandbox = relaxed
[ ] sandbox = true

[x] Tested, as applicable:

nixosTests.tor succeed
build has been tested on servers running tor as a relay.
NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

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

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

[ ] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 266934 run on aarch64-linux 1

8 packages built:

onionshare
onionshare-gui
onionshare-gui.dist
onionshare.dist
orjail
tor
tor.geoip
trezor-suite

I pushed one more commit 5aa01c8fe5e834c1a3f42509587001c6500d0619 which enables GPL build that brings in Proof of Work defense for onion services.
For more details see https://gitlab.torproject.org/tpo/onion-services/onion-support/-/wikis/Documentation/PoW-FAQ#compiling-c-tor-with-the-pow-defense

@GrahamcOfBorg build tor


Adding apartment_0000

Adding apartment_0000. This scene uses the UE5 latest features, lumen illumination and it has several assets and textures made from scratch for the development of a high quality apartment. In addition to that, I implemented physics constraints to the articulable parts of the furniture in order to be fully functional as a default scene.

Yes, I still have to do the clean up. I am working on it. Sorry for that.

Comment here when you'd like me to review again.

Comment here when this PR is ready for me to review again.
I am still checking the physic constraints but the scene has been improved and the clean up is done. You can check it again.

Here are some outstanding issues that I've already commented on but still are not fixed. Please carefully review all of my comments in this PR to make sure they're all addressed.

Revert all changes to [/Script/Engine.PhysicsSettings] since you probably did not intend to make any changes here.
Revert this change. I like having debug_0000 as the default startup map for internal development. We will make apartment_0000 the default map for external release builds, but that happens in a separate part of the code.
Don't make any changes to debug_0000.

Here are some new comments:

There are some MI_Kitchen_* files outside the dedicated kitchen folder. The kitchen folder should have all the kitchen materials. Honestly, I don't think the kitchen folder adds that much to the organization here, because it doesn't contain very many files, it isn't consistent (e.g., there is no dedicated folder for living room), and all the material instances begin with the name of the object anyway (e.g., MI_KitchenSink_*), so they are already sensibly grouped in the Material_Instances folder without this additional layer of folder hierarchy. I think we should remove the kitchen folder and use your existing naming convention to organize the material instances.
There are some M_ materials in the material instances folder.
Spelling error: SM_Exctractor_doors (also why is there a static mesh in the materials folder?)
Doesn't match your naming convention: MI_Oven_doorGlass, should be MI_Oven_DoorGlass
Doesn't match your naming convention: SM__SM_Extractor_*, should be SM_Extractor_*
Doesn't match your naming convention: SM_kitchen_base, should be SM_Kitchen_Base (pick a capitalization convention and stick to it 100% of the time)
Spelling error: Shelve
I don't think there should be a dedicated vases folder because there aren't that many vases, and you're you're not consistent about it. Cabinet_Vase is not in the Vases folder. And there are three tables, just like there are three vases. Why don't tables have a dedicated tables folder?

Clean up the World Outliner. Use our design doc and the latest debug_0000 as a reference:

There are several artificial rect lights on the windows. We have discussed this issue specifically, and you assured me that we are not using these lighting hacks. Why are these rect lights here?
Mimic the organizational structure for the World Outliner as it is described in our design doc, and as exemplified in debug_0000. This will require deciding on a semantic label for each actor. Use NYU40 semantic labels as described here (https://github.com/apple/ml-hypersim/blob/main/code/cpp/tools/scene_annotation_tool/semantic_label_descs.csv).
SM_wall_* aren't doing anything. Why are these actors here?
Move the spheres and the corresponding GroupActor into the Debug folder.
Mimic our approach for representing lights that have static meshes associated with them, as described in our design doc, and as exemplified in debug_0000. Represent all PointLight_CeilingLamp_* as PointLightComponents on the corresponding StaticMeshActor. Likewise for all the other lights that have static meshes associated with them. The reasoning for this approach is described in detail in our design doc.
Mimic the way we're doing outdoor illumination in debug_0000.
The PhysicsConstraintComponents are not configured correctly. For example, the spatial location of Chest2.PhysicsConstraint_01 is not the same as the spatial location of Chest2.Door_01, even though this is a requirement in our design doc. For now, it is fine if there are still simulation problems after the PhysicsConstraintComponents are configured to adhere to all of our requirements, but I want to make sure that we're adhering to all the existing requirements before investing additional human effort into debugging simulation problems.
Spelling error: SpotLight_CelingLamp_DinningRoom
Spelling error: SpotLight_KithecnLight_1

Minor nitpick: I think the drain in the sink is backwards. It should be directly under the tap, instead of being close to the edge of the counter.

I'll review the project structure in the World Outliner on Monday.

I get the following warnings when I build and cook via the command-line on Windows:
LogMaterial: Warning: [AssetLog] F:\code\github\spear\cpp\unreal_projects\SpearSim\Content\Scenes\apartment_0000\Materials\Materials\M_Master_Opacity.uasset: Failed to compile Material for platform PCD3D_SM6, Default Material will be used in game.
        (Node TextureSampleParameter2D) Sampler type is Color, should be Linear Color for /Game/Scenes/apartment_0000/Meshes/Clutter/Fireplace/T_Fireplace_orm.T_Fireplace_orm
        (Node TextureSampleParameter2D) Sampler type is Color, should be Linear Color for /Game/Scenes/apartment_0000/Meshes/Clutter/Fireplace/T_Fireplace_orm.T_Fireplace_orm

LogMaterial: Warning: [AssetLog] F:\code\github\spear\cpp\unreal_projects\SpearSim\Content\Scenes\apartment_0000\Materials\Materials\M_Master_Opacity.uasset: Failed to compile Material for platform PCD3D_SM5, Default Material will be used in game.
        (Node TextureSampleParameter2D) Sampler type is Color, should be Linear Color for /Game/Scenes/apartment_0000/Meshes/Clutter/Fireplace/T_Fireplace_orm.T_Fireplace_orm
        (Node TextureSampleParameter2D) Sampler type is Color, should be Linear Color for /Game/Scenes/apartment_0000/Meshes/Clutter/Fireplace/T_Fireplace_orm.T_Fireplace_orm

LogMaterial: Warning: Cooking a material resource (in M_Master_Opacity hierarchy) that doesn't have a valid ShaderMap! Shadermap pointer is null.
LogMaterial: Warning: Cooking a material resource (in M_Master_Opacity hierarchy) that doesn't have a valid ShaderMap! Shadermap pointer is null.

LogUObjectGlobals: Warning: [AssetLog] F:\code\github\spear\cpp\unreal_projects\SpearSim\Content\Scenes\apartment_0000\Materials\Material_Instances\MI_Curtains_01.uasset: Failed to load '/Game/Scenes/apartment_0000/Meshes/Clutter/Curtains/T_Curtain_Height': Can't find file.
LogLinker: Warning: [AssetLog] F:\code\github\spear\cpp\unreal_projects\SpearSim\Content\Scenes\apartment_0000\Materials\Material_Instances\MI_Curtains_01.uasset: VerifyImport: Failed to load package for import object 'Package /Game/Scenes/apartment_0000/Meshes/Clutter/Curtains/T_Curtain_Height'

Please make sure that the project builds and cooks without warnings on the command-line.

Lighting looks weird when I open the latest project in the editor:

Lighting still looks weird for me in the latest project.

In my last version of the scene (which I uploaded to sourcetree) I fixed up all the redirectors in apartment_0000 and the file "MI_Table_Living" has been changed to "MI_LivingRoom_Table".

De: Mike Roberts @.>
Enviado: martes, 27 de junio de 2023 23:39
Para: isl-org/spear @.>
Cc: Ahlam @.>; Author @.>
Asunto: Re: [isl-org/spear] Adding apartment_0000 (PR #205)
@mikeroberts3000 commented on this pull request.

On cpp/unreal_projects/SpearSim/Content/Scenes/apartment_0000/Materials/Material_Instances/MI_Table_Living.uassethttps://github.com/isl-org/spear/pull/205#discussion_r1244390992:
Please "fix up redirectors" in the editor for all redirectors if you haven't already. And please review your changes in the "Files changed" tab on GitHub as well as in the Unreal Editor so you can catch similar issues in future.
—
Reply to this email directly, view it on GitHubhttps://github.com/isl-org/spear/pull/205#discussion_r1244390992, or unsubscribehttps://github.com/notifications/unsubscribe-auth/A234SOYLBSFNF2QYP5GFDZTXNNHJTANCNFSM6AAAAAAY6JU7LQ.
You are receiving this because you authored the thread.Message ID: @.***>

Lighting still looks weird for me in the latest project.
![Screenshot (28)](https://user-images.githubusercontent.com/2341965/249287511-dd9592ed-96a8-4405-bd4e-acfa21084edb.p
This issue is related to the HDRI, I'm finding out what happen with this file.

After reading your latest comments in the COMMENTS.pdf file you sent me via Discord, I have the following follow-up comments:

Materials/Materials and Materials/Material_Instances are good.
Let's move the textures in Meshes/* directly into Materials/Textures with no additional subfolders. It is confusing that textures are currently stored in a folder called Meshes. And there are textures that apply to multiple meshes (e.g., T_Cabinet_Vase_Mirror), so it is confusing to store a shared texture with a particular mesh (e.g., storing a shared texture with Cabinet but not with Vase or Mirror).

The following comments apply to the Outliner view:

Move all the actors in the Composite folder into the Meshes folder (see below for details).
In the Meshes folder, create subfolders using the following semantic category names and IDs, and move all relevant actors into these subfolders:

https://github.com/apple/ml-hypersim/blob/main/code/cpp/tools/scene_annotation_tool/semantic_label_descs.csv
These semantic categories aren't perfect, but lots of people in the robotics community are already using them.
For example, create subfolders like 01_wall, 02_floor, 03_cabinet, etc.
Only create a subfolder if you intend to place at least one actor in it.

Move Rendering/Lights/Ceiling_Kitchen_Lights and Rendering/Lights/Ceiling_LivingRoom_Lights to the Meshes/35_lamp folder. We want these actors to be stored in Meshes because they each have a mesh attached to them, and we want them to be in the 35_lamp folder because lamp is the closest semantic category to an overhead light.
Move Rendering/Lights/HDRIBackdrop to Rendering/HDRI/HDRIBackdrop. I don't have a definitive justification for this, but I subjectively believe that HDRI actors deserve their own subfolder.
There are some lights that cause the word "Preview" to be projected onto the scene in the editor viewport. This happens because their mobility is set to Static. We should set the mobility of all lights to Movable so they interact correctly with Lumen.
Otherwise the structure in the Outliner is good.

The following comments apply to the World Settings view:

There are some non-default values in the World Settings view. We should avoid changing things in World Settings unless we have a good reason.

After reading your latest comments in the COMMENTS.pdf file you sent me via Discord, I have the following follow-up comments:

Materials/Materials and Materials/Material_Instances look good to me.
Let's move the textures in Meshes/* directly into Materials/Textures with no additional subfolders. It is confusing that textures are currently stored in a folder called Meshes. And there are textures that apply to multiple meshes (e.g., T_Cabinet_Vase_Mirror), so it is confusing to store a shared texture with a particular mesh (e.g., storing a shared texture with Cabinet but not with Vase or Mirror).

It has been changed.

The following comments apply to the Outliner view:

Move all the actors in the Composite folder into the Meshes folder (see below for details).

In the Meshes folder, create subfolders using the following semantic category names and IDs, and move all relevant actors into these subfolders:

https://github.com/apple/ml-hypersim/blob/main/code/cpp/tools/scene_annotation_tool/semantic_label_descs.csv
These semantic categories aren't perfect, but lots of people in the robotics community are already using them.
For example, create subfolders like 01_wall, 02_floor, 03_cabinet, etc.
Only create a subfolder if you intend to place at least one actor in it.

Move Rendering/Lights/Ceiling_Kitchen_Lights and Rendering/Lights/Ceiling_LivingRoom_Lights to the Meshes/35_lamp folder. We want these actors to be stored in Meshes because they each have a mesh attached to them, and we want them to be in the 35_lamp folder because lamp is the closest semantic category to an overhead light.

Move Rendering/Lights/HDRIBackdrop to Rendering/HDRI/HDRIBackdrop. I don't have a definitive justification for this, but I subjectively believe that HDRI actors deserve their own subfolder.

There are some lights that cause the word "Preview" to be projected onto the scene in the editor viewport. This happens because their mobility is set to Static. We should set the mobility of all lights to Movable so they interact correctly with Lumen.

Otherwise the structure in the Outliner is good.

The following comments apply to the World Settings view:

There are some non-default values in the World Settings view. We should avoid changing things in World Settings unless we have a good reason.

After following the semantic category names of each subfolder of "Meshes", should I change the naming structure of each SM from e.g. "Big_Carpet" to "bigcarpet" or "big_carpet" ?


Realm file gets randomly deleted when observing changeset

Goals
I'm a bit of panicking over this since it's a production-level issue we're dealing with at the moment.
We're using RxRealm that wraps Realm object notifications to perform some change observing for object. I noticed that after creating objects, they randomly "disappears", and then noticed that whenever this Observable is being used, not just an object or two are gone, but actually my entire Realm file is randomly being deleted (or is never there to begin with?), and not just the Realm file but also the auxiliary files.
Trying to create a new Realm object doesn't seem to create a fresh file, as well, at this point.
Discussing with @icanzilb (maintainer of RxRealm), it seems RxRealm is only a wrapper around the Realm notifications so this seems like a Realm issue and not a RxRealm issue.
Important: This seems to only happen the first time ever the app runs (when rebooting the app it will create a fresh realm file and continue)
I would truly appreciate your help as I'm not sure anymore what's going on and this is causing serious havoc.
The observable code in question:

Expected Results
The Realm file(s) should be consistently available but seems to get destroyed randomly by something more lower-level, or even not being created to begin with.
Actual Results
When using the following code to check for the existence of the files:
let urls = [
    realmURL,
    realmURL.appendingPathExtension("lock"),
    realmURL.appendingPathExtension("note"),
    realmURL.appendingPathExtension("management")
]

for url in urls {
    print("(pre) \(url.lastPathComponent): \(FileManager.default.fileExists(atPath: url.path))")
}

let _ = THRealms.main() // This is just doing a fresh Realm(configuration: _) all

for url in urls {
    print("(post) \(url.lastPathComponent): \(FileManager.default.fileExists(atPath: url.path))")
}

If the observing code is there, it outputs:
(pre) main.realm: false
(pre) main.realm.lock: false
(pre) main.realm.note: false
(pre) main.realm.management: false
(post) main.realm: false
(post) main.realm.lock: false
(post) main.realm.note: false
(post) main.realm.management: false

If the observing code is replaced with ongoingOrder = .empty() (e.g. not there), it outputs:
(pre) main.realm: true
(pre) main.realm.lock: true
(pre) main.realm.note: true
(pre) main.realm.management: true
(post) main.realm: true
(post) main.realm.lock: true
(post) main.realm.note: true
(post) main.realm.management: true

That is the only difference within the entire app for that situation.
Steps to Reproduce

Delete app completely from simulator
Open app that tries to create a realm / create some objects
Have the observing code in the app (for me its in a Singleton).
At some points look for the existence of the realm file or try to fetch objects from the realm, the file doesn't exist and the objects aren't returned

If 3 isn't at hand (no observing code), the Realm file exists as described in the "Actual Results" section.
Code Sample
Described above, also providing the code that creates the Realm.
As you can see it's just storing it in the Application Support folder, making sure it exists before setting it.

Version of Realm and Tooling
Xcode 8.2.1
RealmSwift 2.4.2
RxRealm 0.5.1 (which seems to depend on RealmSwift 2.2)
iOS Simulator latest
CocoaPods 1.2.0

Hi @freak4pc, that's very strange behavior you're seeing, and I can understand why you'd be worried about it. It sounds like it's reproducible though which should hopefully make it easy to track down and understand. If you can build an IPA of your app and share it with us at<EMAIL_ADDRESS>I'm happy to take a look.

Thanks @bdash for your prompt response
Highly appreciated
I'm gonna try creating a blank reproducible project to send to you and if that won't work I'll send an IPA or our app.
Thanks !

@bdash Was able to more accurately pinpoint the problem. This seems to be related to a situation where, if the Realm file was deleted after creation, consecutive try! Realm(configuration:_) won't create a new Realm file for some reason.
I made a reproduction project, here it is:
RealmNukeExample.zip
A good way I could "work around" this for now is only destroy the realm if it's not empty, but I would still love to understand what's causing this.
Flow of things:

AppDelegate initializes THOrderManager singleton that creates the first empty realm (file exists) - AppDelegate.swift:L16 , OrderManager.swift:L13
Quite immediately after (on viewWillAppear of first view controller), the realm file is deleted by a method that is supposed to make sure "everything in the app is clean" before initial onboarding - ViewController.swift:L24
Consecutive calls to create a fresh realm past that point don't help and the realm isn't actually being created. - Realms.swift - Lines 19-29

If past that point, the next call won't have the delete (which my app won't for the second time), the realm will be created successfully after a restart of the app.
Again, I highly appreciate your help!

Based on your description, and a quick look at the code, it looks like you're deleting the Realm file while it's open. When combined with the fact that open Realm instances are cached, this results in your attempt to create a "fresh Realm" actually returning the same Realm instance whose files on disk you've just deleted. The end result is that any data you store into that Realm instance will disappear as soon as the Realm instance is closed (file data remains on disk so long as there is at least one name for the inode the file system, or at least one open file descriptor to it).
To safely delete a Realm file you need to ensure that there are no open "accessors" to the Realm (Realm instances, and any live objects retrieved from it such as List, Results, and such). The easiest way to ensure this is to only delete the Realm file during app launch, before you've opened the Realm. If you need to delete it at any other point of your app's lifecycle you'll need to ensure that all of the accessors mentioned above have been invalidated or deallocated. For a log-in / log-out type workflow it may be easier to store the Realms for each log-in session at a different path, and to remove any inactive Realms during next app launch.

@bdash Thanks again. Is there anything problematic with just moving to an approach of just removing the objects of the realm instead of deleting the realm itself ?
Is there any way to actual understand which objects are "retained" in the Realm or perhaps a more verbose way to clear the cache in that situation? I assumed a try! Realm() always creates a new Realm file if one doesn't exist. Since realms can be created in many threads where the data needs to be accessed in, it might be tricky to actually make sure everything is closed in that specific moment.
Also, in the example I posted, There is no data inserted into the Realm, it is just created and then deleted so no references should be held from any of the objects, so just the empty Realm is cached? Perhaps it could be more verbose in creating a new realm and clearing the cache if the file doesn't exist at that path anymore? (clearly aware there is probably more to this I'm not considering)
I currently changed my destroy to a THRealms.reset method just clearing the objects. Is there anything problematic with this approach?
/// Reset realm (remove all objects)
public static func reset() {
    THLogger.Warning("Resetting Realm Database...")

    let realm = THRealms.main()
    do {
        try realm.write {
            realm.deleteAll()
        }
    } catch let err {
        THLogger.Failure("Can't delete all objects from Realm: \(err)")
    }
}

Many thanks,
Shai.

The only downside to deleting all objects rather than deleting the Realm files is that deleting all objects won't currently cause the Realm file to shrink. This is likely only a concern if the Realm file was large to begin with. The space that was occupied by the now-deleted objects will be used as new objects are inserted.
Instruments' memory allocation instrument can be used to determine whether there are any references to a given Realm file currently open. You're quite right that it can be difficult to ensure that all references are dropped, hence the suggestion to prefer deleting Realms only at app launch.

Also, in the example I posted, There is no data inserted into the Realm, it is just created and then deleted so no references should be held from any of the objects, so just the empty Realm is cached?

In the specific case of your example code, OrderManager.init() opens the Realm and captures a Results originating from that Realm. That is what keeps the Realm open.

Thanks again @bdash , I'll close it for now. My data set is relatively small so I'm fine with that cost for the added stability.
Maybe it'll be good to consider refreshing that cache if the underlying file doesn't exist anymore, not a huge deal but just a thought :)
Again thanks so much for the help in resolving this
Shai


OAK-9713 sas uri support in oak-upgrade

sas uri support in oak-upgrade

Please document the possibility to use SAS URIs in upgrade_usage.txt. The new skip-create-azure-container option should be documented there as well.

@smiroslav What should happen with this PR now? It was approved more than three months ago but never merged. Also I see no comment in here or the connected JIRA explaining why it is still lingering.


Fixes FirstNameNode suggestions bringing it closer to CallNode.

Fixes https://github.com/microsoft/Power-Fx/issues/1851

✅ No public API change.

Do we still need this function here? Or this can be cleaned up?

Refers to: src/libraries/Microsoft.PowerFx.Core/Texl/Intellisense/SuggestionHandlers/FunctionRecordNameSuggestionHandler.cs:204 in 8b5328d. [](commit_id = 8b5328d741b8c106cd4c9a9a1f08b4495887192d, deletion_comment = False)

✅ No public API change.

✅ No public API change.


Identifiers validation failed for dataset Inventario de la biota marina (cnidarios, poliquetos, moluscos, crustáceos, equinodermos y peces) del Santuario Islas e Islotes de Bahía Chamela, Jalisco, México

Identifier validation failed for the dataset Inventario de la biota marina (cnidarios, poliquetos, moluscos, crustáceos, equinodermos y peces) del Santuario Islas e Islotes de Bahía Chamela, Jalisco, México:

Crawler attempt: 270
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 3319
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 3318 total records; 3318 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3740155/step

New IDs sample:

Old IDs sample:

63dc3cefc3d31ec290a51d20ea477e5a
8cec76d53591a6aa80c4852de62d4832
a29906b30eec0b671846b4c41f3e7879
feb06cf097b5d7684951a09aa3bef9f1
d9b4709a85667fe0e5395c80bf371eb2
081c0fd2842e48c879459586e8a0fede
1de12634a89acbd2172b9fa90f34e4b9
3adf1313d06765acc55b6e0cf88bf0a3
55a7a9c5c2fff499d840752bb9b3a1b2
7c4f57d2f77fab27f3b3e2a1a67466c6

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Inventario de la biota marina (cnidarios, poliquetos, moluscos, crustáceos, equinodermos y peces) del Santuario Islas e Islotes de Bahía Chamela, Jalisco, México : https://doi.org/10.15468/egionz.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Inventario de la biota marina (cnidarios, poliquetos, moluscos, crustáceos, equinodermos y peces) del Santuario Islas e Islotes de Bahía Chamela, Jalisco, México:

Crawler attempt: 271
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 3319
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 3318 total records; 3318 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3741096/step

New IDs sample:

Old IDs sample:

63dc3cefc3d31ec290a51d20ea477e5a
8cec76d53591a6aa80c4852de62d4832
a29906b30eec0b671846b4c41f3e7879
feb06cf097b5d7684951a09aa3bef9f1
d9b4709a85667fe0e5395c80bf371eb2
081c0fd2842e48c879459586e8a0fede
1de12634a89acbd2172b9fa90f34e4b9
3adf1313d06765acc55b6e0cf88bf0a3
55a7a9c5c2fff499d840752bb9b3a1b2
7c4f57d2f77fab27f3b3e2a1a67466c6

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Inventario de la biota marina (cnidarios, poliquetos, moluscos, crustáceos, equinodermos y peces) del Santuario Islas e Islotes de Bahía Chamela, Jalisco, México : https://doi.org/10.15468/egionz.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.

Identifier validation still  failing for the dataset Inventario de la biota marina (cnidarios, poliquetos, moluscos, crustáceos, equinodermos y peces) del Santuario Islas e Islotes de Bahía Chamela, Jalisco, México:

Crawler attempt: 273
Publishing organization: Comisión nacional para el conocimiento y uso de la biodiversidad
Publishing country: MEXICO
Installation: IPTCONABIO
Number of occurrences indexed for this dataset at the time of the issue: 3319
Cause: GBIF ID problems exceed 50% threshold: 100% duplicates; 3318 total records; 3318 absent records
Pipelines execution steps: http://api.gbif.org/v1/pipelines/history/execution/3741705/step

New IDs sample:

Old IDs sample:

63dc3cefc3d31ec290a51d20ea477e5a
8cec76d53591a6aa80c4852de62d4832
a29906b30eec0b671846b4c41f3e7879
feb06cf097b5d7684951a09aa3bef9f1
d9b4709a85667fe0e5395c80bf371eb2
081c0fd2842e48c879459586e8a0fede
1de12634a89acbd2172b9fa90f34e4b9
3adf1313d06765acc55b6e0cf88bf0a3
55a7a9c5c2fff499d840752bb9b3a1b2
7c4f57d2f77fab27f3b3e2a1a67466c6

Publisher email
Hello,
I am contacting you from the GBIF Secretariat about a dataset published by the Inventario de la biota marina (cnidarios, poliquetos, moluscos, crustáceos, equinodermos y peces) del Santuario Islas e Islotes de Bahía Chamela, Jalisco, México : https://doi.org/10.15468/egionz.
We noticed that the occurrenceIDs were changed. We have temporarily paused the ingestions of this dataset.
As you might already know, when an occurrence record has a new occurrenceID for a given dataset, our system considers it to be a new occurrence.
This means that it will be given a new gbifid and a new occurrence URL (like this one: https://www.gbif.org/occurrence/1252968762) and the old gbifid and URL will be deprecated.
In this case, this means that the occurrence URLs would be deprecated when ingesting the newest versions of these datasets.
We would like to check with you if those changes were intentional. Do you know if this is the case?
Please let us know, thanks! We are happy to resume the dataset ingestion.
Note that some users rely on those occurrence URLs and gbifids (like https://bionomia.net for example). In an attempt to improve
the stability of the occurrence URLs and gbifids, we have implemented a warning system to detect these type of changes in datasets (see this news item).
If the data publisher can provide us with a list of old and new occurrenceIDs per record, we can avoid the identifier and URL changes. Could that be an option?
Please let us know if you have any question. Thanks!
All the best,

You can skip/fix identifier validation using the registry UI.


EDC - Revise Multi-Tenancy PR  (ext: CXAR-1033)

+Benefit Hypothesis+
< What´s the purpose, what´s the expected result. You can use User Story Format and Gherkin or following simple approach: If (proposition), then (benefit)>

+Beneficiaries+
< Who will benefit for that feature>

Components: EDC
Sprints: N/A
Fix Versions: N/A
StoryPoints: N/A
Attachments: N/A

Review based on old PR: https://github.com/catenax-ng/product-edc/pull/477

Tasks

[ ] Revise and update the PR for TractusX-EDC.
[ ] Document the MT approach.

sample: https://github.com/eclipse-tractusx/tractusx-edc/tree/main/samples/multi-tenancy


Web frontend?

Hi Magnus,
I'm not sure if this is of interest to you, but in case you have plans for a web frontend, this repo could be helpful:
https://github.com/miguelgrinberg/microdot
Maybe a web frontend could help the users to set some parameters if you plan such a feature in the future.
BTW, thinking beyond iNetBox, e.g. the spirit-level and Duo Control that you already included, why not try to plan for a customized modular board that could offer even more "gimmicks", e.g. sensors for water leakage, gas alarm, air humidity, air pressure in tires, etc.? ("Baukastensystem"?) Is it affordable for private customers to ask a company to develop and produce such boards?

Hi ....., whats your name?
I'll try to bring you up to date. I have been trying to develop a web frontend for the last 2 weeks. With Miguel's help, I first did this in microdot, then transferred everything to the nanoweb framework. The frontend is now running after crash courses in CSS and Jquery. But there is no real use-case and unfortunately the upython resources are finite. So microdot does not run together with the inetbox2mqtt modules in memory.
So I'm not sure how many addons we can still get executable in memory, because the code is pulled into RAM during import.
What actually works for me, however, is the OTA update from the GITHUB. This makes the installation process much easier and possible without having to work with an IDE (e.g. Thonny). And you can also repeat this upload later if you have internet in the camper - which is what most people interested in these solutions have.
The installation process with a terminal connection on a fresh microPython installation would take place like this. At the terminal, one enters the few lines of code at the >> prompt.
>>>import network
>>>s = network.WLAN(network.STA_IF)
>>>s.active(True)
>>>s.connect("<yourSSID>","<YourWifiPW>")
>>>print('network config:', s.ifconfig())
>>>mip.install("github:mc0110/inetbox2mqtt/source/bootloader/main.py","/")
>>>import main

This gives you an internet connection and the bootloader script loads all modules onto the chip. After that, the module starts with the input of the credentials and, more recently, with the queries as to which add-ons are desired.
What do you think, is this a right way to go?

The point is, you actually always need a terminal / galvanic connection first. Even webrepl does not run without entering the credentials. The way I am following at the moment is as follows:

Install Micropython on the port
Wifi connection via terminal
Loading the web application via terminal
After starting the application all further adjustments via web frontend

What do you think?
From my point of view it is relevant to realise the installation of the code without IDE installation, otherwise you can also do everything with Thonny.

I would like that process a lot. And after this you'd have to enter a web frontend for config, updates, etc. ?

Hi Stan, and to anyone else who is interested!
I published the library wifimanager today. It hasn't become as compact as I wanted it to be at the moment. But this version is executable and tested on two different ports (ESP32 and RPI pico W).
Features: You can log in via the Wifi AP (without Internet) and then use the web frontend to enter the credentials. You can create 2 credential-files and then swap them. This is especially useful if you want to install at home, but want to start it in the rv afterwards. You also have the OTA function via the frontend.
@skrebber wanted json-support for the credentials. This is also realised.
What is not possible because of the size is to leave the web-fontend on during normal operation. So one of my questions is: Do you need a file manager feature, for example? I'm not sure. The advantage is, you can download py-files, modify and upload without terminal or thonny-connection, e.g.
I am interested in your opinion. Does it make sense to go down that route? Do we want to implement this at inetbox2mqtt. Please give feedback.

Hello
That's great progress for the project and makes installation easier. Of course, a file manager would be a massive improvement, so that files can be replaced or edited without connecting the ESP32 via USB. If the function has room in memory, I would be excited about this possibility.
Thanks and regards

Thanks for your feedback - at the moment this functionality is included!

Hi Stan,
first of all, thank you for the effort you have made and your feedback.
Your questions indicate that there are still some uncertainties. But I will answer them all together in your other post.

The web frontend is now implemented, so the issue should be solved.


[0.9.1] Logging config doesn't make a difference (reopen of #3254)

Changes to the [logging] parameters in the influxdb.conf file don't seem to make any difference.
I have set write-trace to true and http-access to false, restarted and yet I still see http and no write traces.
Although this time around I may be seeing "[shard] ... flush xx points" messages at the start.
Version 0.9.1.

I believe our logging is now OK. Please let us know if not.


Snapshot mini dumps data retention

For how long the snapshot dumps are kept in AI? Is it configurable?

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

ID: af126ce9-b961-fd20-e4f2-0c17e43e8423
Version Independent ID: 7b5d06b9-67bc-4861-2f76-5e62cfa5cf11
Content: Azure Application Insights Snapshot Debugger for .NET apps
Content Source: articles/application-insights/app-insights-snapshot-debugger.md
Service: application-insights
GitHub Login: @mrbullwinkle
Microsoft Alias: mbullwin

@lukzog In general, Application Insights data is kept for 90 days.  To keep the data longer, you'll need to export and save the data.  I'll confirm that this is true for snapshot dumps.
https://docs.microsoft.com/en-us/azure/application-insights/app-insights-data-retention-privacy#how-long-is-the-data-kept


I crashed after dumping torchilight.

I crashed after dumping torchilight.
msg is :
"Sorry! You ran into a unrecoverable errorthat forces the Dumper to close.
Failed to allocate memory forUBigObjectArray!"

hey there, please look at the log in the log window. I'm very sure that it's due to a faulty GObject offset.

0 [13:11:17 - MAIN]: Loading program...
1 [13:11:17 - MAIN]: Loaded imgui helper library...
2 [13:11:17 - MEMORY]: Initializing memory class...
3 [13:11:17 - MEMORY]: Initialized Memory class!
4 [13:11:22 - MEMORY]: Error getting base address!
5 [13:11:55 - MEMORY]: Loaded Memory class!
6 [13:11:57 - DUMPPROGRESS]: Starting dump...
7 [13:11:57 - ENGINECORE]: Loading core...
8 [13:11:57 - OBJECTSMANAGER]: TUObject -> 0x058B48F1F7480000
9 [13:11:57 - OBJECTSMANAGER]: TUObject elements:<PHONE_NUMBER>
10 [13:11:57 - OBJECTSMANAGER]: TUObject -> 0x058B48F1F7480000
11 [13:11:57 - OBJECTSMANAGER]: Allocated 802C800 bytes for FFields cache
12 [13:11:57 - OBJECTSMANAGER]: Allocated 61A800 bytes for FFieldClass cache
13 [13:11:58 - OBJECTSMANAGER]: Allocating 0x00000000641EC2E8 bytes of memory for GObjectPtrArray at 0x0000028769FF3070
14 [13:11:58 - OBJECTSMANAGER]: Loaded GObjectPtrArray successfully!
15 [13:11:58 - ENGINECORE]: Allocating 0x12FC3344D8 bytes of memory for UBigObjectArray at 0x0000000000000000
16 [13:11:58 - ENGINECORE]: Failed to allocate memory for UBigObjectArray!
17 [13:11:58 - DUMPPROGRESS]: No success at copyUBigObjects!

object count<PHONE_NUMBER>? Doesn't look right to me. Looks like invalid GObjects pointer.

can you help me?

how am i supposed to help you lol? You need the right offsets. You can find them by reversing the game.


Lazy RUM raw event creation in event generator methods

What does this PR do?
This PR does a bit of the optimization for the methods in RumEventExt: when random RUM raw event needs to be created, we are avoiding creating all of them and then selecting only one, but instead selecting the type and then creating only the selected one.
This gives a benefit for the tests where a lot of events are created. For example, for the RumViewScopeTest#M produce event safe for serialization W handleEvent() where there is a 1000 iterations loop to call RumMonitor#handleEvent this change is reducing execution time from 15s to 2s (and it will be much less redundant objects created, less work for GC).
Review checklist (to be filled by reviewers)

[ ] Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
[ ] Make sure you discussed the feature or bugfix with the maintaining team in an Issue
[ ] Make sure each commit and the PR mention the Issue number (cf the CONTRIBUTING doc)

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

Project coverage is 70.36%. Comparing base (a1b97be) to head (0b9e2ac).

Additional details and impacted files
@@             Coverage Diff             @@
##           develop    #2363      +/-   ##
===========================================
+ Coverage    70.26%   70.36%   +0.10%
===========================================
  Files          743      743
  Lines        27681    27676       -5
  Branches      4629     4630       +1
===========================================
+ Hits         19449    19474      +25
+ Misses        6937     6921      -16
+ Partials      1295     1281      -14

see 29 files with indirect coverage changes


feat: support mediamtx rtsp server

This supports splitting out the mediamtx rtsp-server from the device-usb-camera service such that it can be made optional, as well as allows the end user to control the rtsp-server configuration in a more streamlined manner.

If your build fails due to your commit message not passing the build checks, please review the guidelines here: https://github.com/edgexfoundry/edgex-compose/blob/main/.github/Contributing.md
PR Checklist
Please check if your PR fulfills the following requirements:

[ ] I am not introducing a breaking change (if you are, flag in conventional commit message with BREAKING CHANGE: describing the break)
[X] I have fully tested (add details below) this the new feature or bug fix (if not, why?)
[ ] I have opened a PR for the related docs change (if not, why?)

Testing Instructions

make run rtsp-server ds-usb-camera

execute StartStreaming apis of device usb and verify streaming works

@ajcasagrande , are you still wanting to take this approach. I am good with it as long we don't introduce backward breaking changes.

Yes, this would be my preferred approach in a docker environment as it gives full control of the rtsp-server.

Yes, this would be my preferred approach in a docker environment as it gives full control of the rtsp-server.

OK, please update the PR and take out of draft and we can get it in.

@ajcasagrande This request is stale.

closing due to inaction. PLease reopen if needed.


Private repository?

I can’t see the repo in desktop version but I can in mobile version whattttt

@RDIL if your issue is solved, please close this issue
Thanku

But on both my phone and laptop it still says “GitHub.com/tbhaxor/morphine
is not allowed at this time”

Can you show me the screen shot?
On Mon, 22 Oct 2018, 02:42 RDIL<EMAIL_ADDRESS>wrote:

But on both my phone and laptop it still says “GitHub.com/tbhaxor/morphine
is not allowed at this time”
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/tbhaxor/morphine/issues/1#issuecomment-431704385, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AbEloW5DY4AkOtSeSY5VTc1RAVm1dP-Hks5unONHgaJpZM4XwOAH
.

Sure one moment

hey @RDIL  i am closing this issue since i didnt  hear from your side for so long. Anytime you encounter same issue you can reopen it
Thnx


APCEMM interface

I'm leaving this PR as a draft for now because I'm anticipating that I'll make changes as I get this interface ready for the pycontrails workshop. Some likely changes include

Exposing additional YAML parameters in the low-level interface (pycontrails.models.apcemm.interface) to give more control to "expert" users
Adding options to the high-level interface as needed to support case studies for the pycontrails workshop
Documenting known limitations, if any come up in conversations with @sdeastham

But, I think the interface is at a point where it's ready for review. @mlshapiro: go to town. @nickmasson: would you mind looking specifically at the run function in interface.py and the run_apcemm method in adapter.py to make sure I'm not doing anything dumb setting up child processes to run APCEMM?
@sdeastham: feel free to chime in here as much or a little as you'd like!
Changes
Features

Add interfaces for running APCEMM from within pycontrails. The interface includes:

a low-level wrapper around the native APCEMM interface (pycontrails.models.apcemm.interface) than allows users to generate APCEMM input files and run a compiled APCEMM binary manually.
a high-level adapter (pycontrails.models.apcemm.APCEMM) that allows users to run APCEMM through the pycontrails Model interface.

Add APCEMM tutorial notebook.

Internals

Create unit tests for the APCEMM interface that run if an APCEMM executable is found on the PATH inside a clean APCEMM git repository with a pinned git hash. These tests will be skipped unless users carefully configure their local test environment and will not run in CI.
Exclude APCEMM tutorial notebook from notebook tests.

Tests

[x] QC test passes locally (make test)
[x] CI tests pass

Reviewer

@mlshapiro
@nickmasson

I've finished making changes--@mlshapiro, you're free to test drive again!
I will note that the output in the notebook looks different than what you saw initially. I think this is because I found and fixed an issue in the azimuth initialization in DryAdvection, and the contrail is being spread less by normal shear as a result.


fixed bug that occurs when using a 2 in 1 model

some models have more than one model in them like jarvis.umdl in which case this gives the error of unmatched sensitivities. This fixes the issue.

thank you!


Add some styling

This PR makes listings look like this:

It does pull in an icon set from here for the download icon.

Looking much better already!
A few ideas:

What do you think about reducing the size of each row? There's a lot of padding, which makes fewer items visible in a given amount of space. (A good way to get a listing with a lot of items is to do cargo run -- --directory . to just list the project directory. Then you can browse src and .git for dirs with lots of files.)

The rows with a download icon are slightly larger than rows without a download icon. For visual consistency, they should probably be the same size.

What do you think about making the download icon a bit smaller? More like the height of the text itself. This would also allow the rows to be smaller.

Now the rows have a smaller height, the download icon is smaller, and all the rows have the same height:

What do you think?

Nice, looks good to me, aside from the hr thing.
The only thing I don't particularly like is how the download links are far away on the right, and that there's lots of whitespace, but I can't think of an obvious way to fix that, so I think we should merge this and worry about that later.

The only thing I don't particularly like is how the download links are far away on the right, and that there's lots of whitespace, but I can't think of an obvious way to fix that, so I think we should merge this and worry about that later.

Agreed. Both on that the icons are too far away and that there's no obvious way to fix it. :|


Blocked: SequenceValueGenerator may fail with LocalDb due to LocalDb concurrency issue with sequences

Stack trace from CI failure:
The statement has been terminated.
   at System.Data.SqlClient.SqlCommand.<ExecuteDbDataReaderAsync>b__24(Task`1 result)
   at System.Threading.Tasks.ContinuationResultTaskFromResultTask`2.InnerInvoke()
   at System.Threading.Tasks.Task.Execute()
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
   at Microsoft.Data.Entity.Relational.Update.BatchExecutor.<ExecuteBatchAsync>d__1.MoveNext() in C:\BuildAgent\work\9114aaddeefdc8e8\src\Microsoft.Data.Entity.Relational\Update\BatchExecutor.cs:line 68
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.ConfiguredTaskAwaitable.ConfiguredTaskAwaiter.GetResult()
   at Microsoft.Data.Entity.Relational.Update.BatchExecutor.<ExecuteAsync>d__1.MoveNext() in C:\BuildAgent\work\9114aaddeefdc8e8\src\Microsoft.Data.Entity.Relational\Update\BatchExecutor.cs:line 50
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.Data.Entity.Relational.RelationalDataStore.<SaveChangesAsync>d__1.MoveNext() in C:\BuildAgent\work\9114aaddeefdc8e8\src\Microsoft.Data.Entity.Relational\RelationalDataStore.cs:line 67
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.ConfiguredTaskAwaitable`1.ConfiguredTaskAwaiter.GetResult()
   at Microsoft.Data.Entity.ChangeTracking.StateManager.<SaveChangesAsync>d__1.MoveNext() in C:\BuildAgent\work\9114aaddeefdc8e8\src\Microsoft.Data.Entity\ChangeTracking\StateManager.cs:line 266
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter`1.GetResult()
   at Microsoft.Data.Entity.SqlServer.FunctionalTests.SequenceEndToEndTest.<AddEntitiesAsync>d__1.MoveNext() in C:\BuildAgent\work\9114aaddeefdc8e8\test\Microsoft.Data.Entity.SqlServer.FunctionalTests\SequenceEndToEndTest.cs:line 128
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.GetResult()
   at Microsoft.Data.Entity.SqlServer.FunctionalTests.SequenceEndToEndTest.<Can_use_sequence_end_to_end_from_multiple_contexts_concurrently_async>d__1.MoveNext() in C:\BuildAgent\work\9114aaddeefdc8e8\test\Microsoft.Data.Entity.SqlServer.FunctionalTests\SequenceEndToEndTest.cs:line 163
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)
--- End of stack trace from previous location where exception was thrown ---
   at System.Runtime.CompilerServices.TaskAwaiter.ThrowForNonSuccess(Task task)
   at System.Runtime.CompilerServices.TaskAwaiter.HandleNonSuccessAndDebuggerNotification(Task task)```

<!---
@huboard:{"custom_state":"blocked"}
-->

Internal bug on SQL Server indicates that this is now fixed and released in latest versions and service packs. Re-enabling test and closing out.


Add PIP switcher

ability to use PIP mode extending flicker controller. for both ios and andriod

You can use PIP package on top of this Player. Here you go: https://pub.dev/packages/pip_flutter


[FEATURE REQ] EventHub consumer group / EventProcessorClient metrics

Is your feature request related to a problem? Please describe.
I maintain applications consuming data from Event Hubs managed by external legal entities and had like to monitor my consumer groups health. AFAIK azure-sdk-for-java provides no consumer group or EventProcessorClient related metrics, nor tools which could observe consumer group health (ex. https://github.com/lightbend/kafka-lag-exporter).
I must compute such technical metrics by myself and EventProcessClient API is kind of burdensome for a such task.
Describe the solution you'd like
I had like an EventProcessorClient to produce metrics enabling consumer group supervision. SDK metrics should be easy to merge to other application metrics and not be tied to Azure Monitor. Kafka's consumer metrics and KIP 489: Kafka Consumer Record Latency Metric could serve as a base of inspiration.
Metrics exported by kafka-lag-exporter are also good reference of useful metrics. At the very least I want to be able to monitor consumer group consumption rate, max lag & latency and production rate.
Describe alternatives you've considered
Additional context
We started a prototype based on EventContext and  wrapping an event processor but that proved to be more difficult that expected:

it is unclear how to handle metrics for partitions without consumed  message during window (ex. lag and latency might have increased if the issue is on the consumer side)
using processPartitionInitialization and processPartionClose is likely required too.

@conniey could you please take a look?

Hey, thanks for suggesting this.. at the moment, we have incorporated client-side tracing around processing each message using tracing. https://github.com/Azure/azure-sdk-for-java/wiki/Tracing
however, these metrics seem like they would have be surfaced by the service?
@JamesBirdsall do you know if this is something that Event Hubs publishes?

at the moment, we have incorporated client-side tracing around processing each message using tracing

Tracing is great, but I doubt it can address this issue as comparing consumption (ie. state of the consumer group) with production (ie. state of the hub) seems required.

however, these metrics seem like they would have be surfaced by the service?

Disclaimer: I'm not an eventHub power-user, I only maintain a couple of consumer groups and might say odd things.
I can image four options:
Event Hubs service publishes consumer group metrics. Users can view them using an Azure service or to retrieve them programmatically.  From my user perspective, that would be ideal the solution. However, I don't see how Event Hubs service could compute such metrics as consumer group offsets are persisted in a blob checkpoint store. I doubt that Event hubs know where consumer group checkpoints are stored nor can read to them.
Monitor one or a set of consumer group using a provided tool or library. Combining information from a CheckpointStore and an EventHubConsumerClient should be enough (ie. checkpoint.getSequenceNumber(), partitionProperties.getLastEnqueuedSequenceNumber(), partitionProperties.getLastEnqueuedTime() and maybe client.receiveFromPartition( "", 1, EventPosition.fromSequenceNumber( offset )) to compute latency). This would be similar to what kafka-lag-exporter does. The main challenge is likely how to monitor multiple consumer groups without cumbersome configuration. Because Kafka brokers persist consumer group state and expose an API, one can easily deploy a single kafka-lag-export to monitor all cluster's customer groups. It don't a such pleasant deployment option for Event hubs.
Consumer application monitor its consumer groups like in previous option. Application already knows consumer group name, checkpoint location, credentials etc. However, it would mean that each application replica monitors the consumer group or that an election mechanism is required.
Consumer application monitors event flowing through an EventProcessorClient rather that a consumer group state. This seems doable by combining DataEvent, InitializationContext and CloseContext. However, metrics semantic & alerting might be harder to get right as application might stop, some partition be unassigned etc.

Trying to produce good metrics for Event Hubs is a complex issue. Event Hubs itself is a distributed system, and frequently the consumer application is as well, and neither side has a complete picture. Kafka can do a bit better because checkpoints are stored in the service, giving the service side more insight. That may eventually become an option for Event Hubs accessed via AMQP as well, but adding that functionality is not currently on any plan or schedule.
One thing we do have internally is a metric for "backlog" on a receiver, which is the difference between the highest sequence number flowed to the receiver and the highest sequence number in the partition. This doesn't map directly to lag at the application level because AMQP is a streaming protocol and messages flow down the wire into a buffer within the client while the application is doing other things, and it common that the messages flowed are well ahead of what the application has actually processed, but it is a useful proxy -- if the backlog is increasing, we can infer that the application is processing slowly (or stopped); if the backlog is decreasing, the application is catching up; and if the backlog remains 0, then the application is keeping up with message flow and presumably healthy. However, it is possible to have more than one receiver on the same partition and consumer group, and that's something which is more likely to happen when there are troubles -- for example, the application is in a bad state and not processing messages for a partition but the receiver is still connected while the application creates another receiver to get message processing started again. What then is the backlog for the partition on that consumer group? A human engineer can look at these metrics and interpret them usefully, but trying to devise rules for an automated monitoring system would be difficult.
Our best existing solution to this problem is a feature which adds information about the current state of the partition to each message, which gives the application side the most complete view of the overall situation. This may be what you were talking about with EventContext, although it looks like what I'm thinking of is exposed in the new client as PartitionProperties. It suffers from certain drawbacks, in that the information is already at least a little old when your application sees it, and of course if communications with the service pause or stop then the application can't update the metrics at all. However, as things stand, the consuming application is the only part of the combined system that knows what messages have actually been processed, so it is uniquely positioned to measure the actual lag.

Have some progress been made in the past months?
Event hubs consumers are a major pain point of our information system because consumers sporadically stop processing some partition until application is restarted and consumer group state being not observable we cannot detect it.
It seems inconceivable that a service such as event hubs does not enable users to easily and robustly monitor whether a consumer group is lagging or not. This is a non existent issue for any other messaging system that I'm aware of.
@JamesBirdsall While I understand your explanation (and with no better alternative we developed some monitoring based on message consumption and EventContext), this cannot be an acceptable answer from the Event Hubs team.

We have several github issues that fill the gaps in our observability experience.  Closed in favour of:

#38351
#25605


[BUG] - Age is NaN from some valid personnummer

Can't get age from some otherwise valid personnummer.
Steps to reproduce:

Go to the Personnummer website
Try<PHONE_NUMBER>32
Returned age is NaN

Can't reproduce, how do you get the NaN on age?

Wow, that was fast! Upon further testing it seems to be browser specific.
Does not work in Safari 14.0.3 on macOS or iOS 14. Does work in Chrome and Firefox though.

Woops, accidentall

Thanks for report, will be fixed and new version is out soon.

Thanks for the fix and quick response. Just noticed this on our prod this evening! Huge thanks


Fixes #205

fixes #205

@Clinale Great work, thank you! Let's hope this solves the problem, at least for most people. Thanks!


Quick diff should not run in diff editor

I think we had it disabled there:

This is not a regression, I can also reproduce in older VS Code builds (e.g. stable with useVersion2: false).
It happens when at some point in time the modified file is open in an editor. This creates a DirtyDiffModel that stays around until the text model is closed.
Repro steps:

Open a git repo
Modify a file in a normal editor, notice there are dirty diff decorations in the horizontal scroll bar
Now open the file from the SCM view in the diff editor
Notice these dirty diff decorations also show in the editor

When you reload VS Code after step 2 or 3, the dirty diff decorations disappear.

fyi @joaomoreno @lszomoru

I'm looking into this.


Limit the branches that build on travis

@danroth27  We have a similar setup in all of our repos to reduce the amount of churn on travis and I'm wondering if we should do the same for the Docs repo. The idea is to restrict building branches to PRs, main branches (master, release and dev) and branches specifically tagged with /ci-.

Hi @JunTaoLuo, I'm your friendly neighborhood .NET Foundation Pull Request Bot (You can call me DNFBOT). Thanks for your contribution!
You've already signed the contribution license agreement. Thanks!
The agreement was validated by .NET Foundation and real humans are currently evaluating your PR.
TTYL, DNFBOT;

:shipit:


[Bug]: Test Project Build Paths Too Long - Windows

What Operating System(s) are you seeing this problem on?
Windows
dlib version
19.24.2
Python version
3.9.10
Compiler
MSVC 19.37.32822.0
Expected Behavior
I am running Windows 11 Enterprise 22H2. After completing the pre-requisite steps of installing NVIDIA CUDA and CUDNN, along with CMAKE, and VS Build Tools I expected that installing dlib via pip would build with CUDA support.
Current Behavior
Currently the install fails to build the test project. Errors appear to be around creating log files in the temp directories. The paths that fail exceed Microsoft's 260 character limit. Attempting to force long paths in Windows 11 via policy is broken and a known issue. Is it possible to reduce path lengths for the test builds?

FileTracker : error FTK1011: could not create the new file tracking log file:
log.txt

Steps to Reproduce
pip install dlib --verbose --no-cache-dir
Anything else?
No response

It's not super clear to me how to get pip and/or cmake to locate files in different folders.  If you figure something out send us a PR though :)

Your comment gave me some much needed hints. It appears that cmake/pip use the Windows environment variables for TEMP and TMP which default as shown below.

I was able to successfully build by changing my TEMP/TMP paths to a location closer to the root. While this may be considered a workaround, it is acceptable for my purposes.

I believe this is likely directly related to cmake and not pip.
Another possible solution for anyone looking for alternatives if they do not have permissions to modify environment variables may be to force this in the CMakeLists.txt file, however I have not tested this, and it would not be a global solution that is platform independent.
set(ENV{TEMP} "C:/Temp")
set(ENV{TMP} "C:/Temp")

To note, any alternate location will need to be a path that the user has full RW access to.
As I do not posses the necessary skills to dive further into this for a more permanent fix, I am submitting this work around as the solution and closing the bug.

Thanks for the follow up :)


A build operation failed.     Could not create task ':tangem-sdk-react-native:compileDebugKotlin'. Could not create task ':tangem-sdk-react-native:compileDebugKotlin'.

DUPLICATED


ImportApi operation for apigatewayv2

Issue #128 , if available:
Description of changes:

Fixing the classic e2e test run. Temporarily commenting docker test run.

Update ack-generate/release to drop ".tpl" from files generated for helm charts.
I spent one day trying to fix docker-file and scripts for successfully running docker-test-run but in the end I hit the blocker where daws was unable to run inside docker.
Then I fall back to old e2e runs and temporarily commented docker-test-runs from kind-build-test
I made some minor fixes in script for successfully running e2e tests.

Adding required override for fields in FieldConfig.

Introduced a new boolean field 'required' in FieldConfig to override the required behavior present in aws-sdk-go.
This was required for ImportApi operation to succeed without taking required-fields from CreateApi operation.

Implementing ImportApi & ReimportApi for apigatewayv2.

Created custom methods for Import and Reimport Api operations.
Updated e2e tests for apigatewayv2 to include ImportApi and ReimportApi.

e2e test run was successful.
vijat@186590cff3cf aws-controllers-k8s % ./scripts/kind-build-test.sh apigatewayv2
checking AWS credentials ... ok.
creating kind cluster ack-test-2b2ebd8b-d02fcaf7 ... ok.
[+] Building 93.8s (17/17) FINISHED
 => [internal] load build definition from Dockerfile                                                                                0.0s
 => => transferring dockerfile: 39B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load metadata for docker.io/library/amazonlinux:2                                                                        1.5s
 => [internal] load metadata for docker.io/library/golang:1.14.1                                                                        1.5s
 => [auth] library/amazonlinux:pull token for registry-1.docker.io                                                                      0.0s
 => [auth] library/golang:pull token for registry-1.docker.io                                                                           0.0s
 => [internal] load build context                                                                                1.5s
 => => transferring context: 809.40kB                                                                                1.5s
 => [builder 1/7] FROM docker.io/library/golang:1.14.1@sha256:38a520b05b971181a5a30d72b74d1b70c63688eb267a4fb376c7476a5c6f885b          0.0s
 => => resolve docker.io/library/golang:1.14.1@sha256:38a520b05b971181a5a30d72b74d1b70c63688eb267a4fb376c7476a5c6f885b                  0.0s
 => CACHED [stage-1 1/3] FROM docker.io/library/amazonlinux:2@sha256:e87ffde799fd6e9c70c6ffb190726c146aeb1ae4d7667848850d9a609e7a7ab0   0.0s
 => CACHED [builder 2/7] WORKDIR /github.com/aws/aws-controllers-k8s                                                                    0.0s
 => CACHED [builder 3/7] COPY go.mod go.mod                                                                                0.0s
 => CACHED [builder 4/7] COPY go.sum go.sum                                                                                0.0s
 => CACHED [builder 5/7] RUN  go mod download                                                                                0.0s
 => [builder 6/7] COPY . /github.com/aws/aws-controllers-k8s/                                                                           8.9s
 => [builder 7/7] RUN GIT_VERSION=$(git describe --tags --dirty --always) &&     GIT_COMMIT=$(git rev-parse HEAD) &&     BUILD_DATE=$  79.9s
 => [stage-1 2/3] COPY --from=builder /github.com/aws/aws-controllers-k8s/bin/controller /github.com/aws/aws-controllers-k8s/LICENSE /  0.4s
 => exporting to image                                                                                0.4s
 => => exporting layers                                                                                0.4s
 => => writing image sha256:841c676bcbe3a3ddad6393b7bc65d8b8dc47dcd1fd81a188e44526b892386f33                                            0.0s
 => => naming to docker.io/library/aws-controllers-k8s:apigatewayv2-v0.0.1-119-g735f9da-dirty                                           0.0s
ok.
loading the images into the cluster ... ok.
loading CRD manifests for apigatewayv2 into the cluster ... ok.
loading RBAC manifests for apigatewayv2 into the cluster ... ok.
loading service controller Deployment for apigatewayv2 into the cluster ...ok.
generating AWS temporary credentials and adding to env vars map ... ok.
======================================================================================================
To poke around your test cluster manually:
export KUBECONFIG=/Users/vijat/Documents/gocode/src/github.com/vijtrip2/aws-controllers-k8s/scripts/lib/../../build/tmp-ack-test-2b2ebd8b-d02fcaf7/kubeconfig
kubectl get pods -A
======================================================================================================
testing Helm release for apigatewayv2 for release version v0.0.1-119-g735f9da-dirty.
Building release artifacts for apigatewayv2-v0.0.1-119-g735f9da-dirty
Generating custom resource definitions for apigatewayv2
Generating RBAC manifests for apigatewayv2
namespace/ack-system-test-helm created
installing the helm chart for ack-apigatewayv2-controller in namespace ack-system-test-helm ... ok.
uninstalling the helm chart for ack-apigatewayv2-controller in namespace ack-system-test-helm ... ok.
e2e took 192 second(s)
🥑 Deleting k8s cluster using "kind"
Deleting cluster "ack-test-2b2ebd8b-d02fcaf7" ...

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

Few small requests inline, please see my comments, @vijtrip2. Overall this looks very solid, though.
One thing you will need to do in a followup PR is create e2e tests for the failure scenarios (in particular, the Bad Input scenarios). You have created unit tests that adequately test the Go custom update and create methods themselves, but you will want to add TerminalConditions the CR's Status.Conditions collection and mark the CR as being unable to be synced.
See here for an example of where Elasticache is doing this:
https://github.com/aws/aws-controllers-k8s/blob/main/services/elasticache/generator.yaml#L7-L11
which generates this code:
https://github.com/aws/aws-controllers-k8s/blob/main/services/elasticache/pkg/resource/cache_subnet_group/sdk.go#L387-L399
And here is an example of the Elasticache Snapshot resource throwing a terminal condition in its custom create code paths:
https://github.com/aws/aws-controllers-k8s/blob/main/services/elasticache/pkg/resource/snapshot/custom_create_api.go#L31-L32
and that exception code is listed in the generator here:
https://github.com/aws/aws-controllers-k8s/blob/main/services/elasticache/generator.yaml#L59
Ping @nmvk for details on how the TerminalCondition stuff works :)

Thank you very much. I will incorporate this into upcoming PR. Pasting these very good instructions into issue #128

Recent successful e2e run.
vijat@186590cff3cf aws-controllers-k8s % ./scripts/kind-build-test.sh apigatewayv2
checking AWS credentials ... ok.
creating kind cluster ack-test-06a6e1e9-89c2341e ... ok.
[+] Building 159.9s (17/17) FINISHED
 => [internal] load build definition from Dockerfile                                                                                0.1s
 => => transferring dockerfile: 39B                                                                                0.0s
 => [internal] load .dockerignore                                                                                0.0s
 => => transferring context: 2B                                                                                0.0s
 => [internal] load metadata for docker.io/library/amazonlinux:2                                                                        2.4s
 => [internal] load metadata for docker.io/library/golang:1.14.1                                                                        1.6s
 => [auth] library/golang:pull token for registry-1.docker.io                                                                           0.0s
 => [auth] library/amazonlinux:pull token for registry-1.docker.io                                                                      0.0s
 => [builder 1/7] FROM docker.io/library/golang:1.14.1@sha256:38a520b05b971181a5a30d72b74d1b70c63688eb267a4fb376c7476a5c6f885b          0.0s
 => => resolve docker.io/library/golang:1.14.1@sha256:38a520b05b971181a5a30d72b74d1b70c63688eb267a4fb376c7476a5c6f885b                  0.0s
 => [stage-1 1/3] FROM docker.io/library/amazonlinux:2@sha256:420a6503505c73ea05e1254acd4d1a5e73305dab8ec3fa70833e112cc6980624         20.4s
 => => resolve docker.io/library/amazonlinux:2@sha256:420a6503505c73ea05e1254acd4d1a5e73305dab8ec3fa70833e112cc6980624                  0.0s
 => => sha256:420a6503505c73ea05e1254acd4d1a5e73305dab8ec3fa70833e112cc6980624 547B / 547B                                              0.0s
 => => sha256:1c5213077930ebbd35b51bece063ffb31f47df9c6fb71b7248944785c77ba772 529B / 529B                                              0.0s
 => => sha256:9917dfe117ca1e8affbea6d819c0d94918524ae1882fe69746a8217aec4c4053 1.48kB / 1.48kB                                          0.0s
 => => sha256:4232b9ee675bb1f9a32337ec3f266a570b75c54c3c3f173b1abb998e9984ad8c 62.01MB / 62.01MB                                        5.7s
 => => extracting sha256:4232b9ee675bb1f9a32337ec3f266a570b75c54c3c3f173b1abb998e9984ad8c                                              13.8s
 => [internal] load build context                                                                                7.7s
 => => transferring context: 20.10MB                                                                                7.5s
 => CACHED [builder 2/7] WORKDIR /github.com/aws/aws-controllers-k8s                                                                    0.0s
 => CACHED [builder 3/7] COPY go.mod go.mod                                                                                0.0s
 => CACHED [builder 4/7] COPY go.sum go.sum                                                                                0.0s
 => CACHED [builder 5/7] RUN  go mod download                                                                                0.0s
 => [builder 6/7] COPY . /github.com/aws/aws-controllers-k8s/                                                                          17.9s
 => [builder 7/7] RUN GIT_VERSION=$(git describe --tags --dirty --always) &&     GIT_COMMIT=$(git rev-parse HEAD) &&     BUILD_DATE=  127.6s
 => [stage-1 2/3] COPY --from=builder /github.com/aws/aws-controllers-k8s/bin/controller /github.com/aws/aws-controllers-k8s/LICENSE /  1.1s
 => exporting to image                                                                                1.4s
 => => exporting layers                                                                                1.4s
 => => writing image sha256:b1fd2407d2d1abbf74d16f932c165a0bcb42665101c054203249d1620a06e1d9                                            0.0s
 => => naming to docker.io/library/aws-controllers-k8s:apigatewayv2-v0.0.1-127-gc15e700-dirty                                           0.0s
ok.
loading the images into the cluster ... ok.
loading CRD manifests for apigatewayv2 into the cluster ... ok.
loading RBAC manifests for apigatewayv2 into the cluster ... ok.
loading service controller Deployment for apigatewayv2 into the cluster ...ok.
generating AWS temporary credentials and adding to env vars map ... ok.
======================================================================================================
To poke around your test cluster manually:
export KUBECONFIG=/Users/vijat/Documents/gocode/src/github.com/vijtrip2/aws-controllers-k8s/scripts/lib/../../build/tmp-ack-test-06a6e1e9-89c2341e/kubeconfig
kubectl get pods -A
======================================================================================================
testing Helm release for apigatewayv2 for release version v0.0.1-127-gc15e700-dirty.
Building release artifacts for apigatewayv2-v0.0.1-127-gc15e700-dirty
Generating custom resource definitions for apigatewayv2
Generating RBAC manifests for apigatewayv2
namespace/ack-system-test-helm created
installing the helm chart for ack-apigatewayv2-controller in namespace ack-system-test-helm ... ok.
uninstalling the helm chart for ack-apigatewayv2-controller in namespace ack-system-test-helm ... ok.
e2e took 220 second(s)
🥑 Deleting k8s cluster using "kind"
Deleting cluster "ack-test-06a6e1e9-89c2341e" ...

closing in favor of PR #609


Include babel-preset-env documentation

Fixes #1081.

We'll need to make some change to the babel-preset-env README (avoid inline code blocks for example).

@xtuc I tweaked the GitHub/Edit this Link logic to allow us to point to a non monorepo

We should wait for https://github.com/babel/babel-preset-env/pull/96 to get merged, as it removes a $ and converts some relative links.

merged

@existentialism Nice job, thanks. Links are working correctly.
The logic is becoming quite complex but isn't visible by contributors.
LGTM