Add circuit breaker booster for Node.js RHOAR

https://github.com/bucharest-gold/nodejs-circuit-breaker
Initial implementation is complete. Additional issues should be tracked here: https://github.com/bucharest-gold/nodejs-circuit-breaker/issues


[RFC] Allow for restarting adb as root upon connection.

As per https://github.com/ARM-software/devlib/issues/406 currently in order to enable adbd as root, a connection to the target already needs to exist however there are use case that we want to perform initialising as root as well.

Add a utility function to restarted adbd in rooted and unrooted mode.
Add the adb_as_root connection parameter to AdbConnection.

Note: This will restart adbd as root before attempting to connect to the target and will also restart adbd unrooted upon the last disconnection from the target.

When working on #414 two things occurred to me:

AndroidTarget.adb_root() records the fact that the target has been rooted or not in _connected_as_root attribute. AFAICS that attribute would now "lie" since that is now up to the connection to decide what to do. That could be solved easily by making _connected_as_root a property that delegates the knowledge to the connection object.

The fact that the target is rooted is fundamentally a target property AFAIK. There is at most one adb server per device, and there is a 1-to-1 mapping between actual devices and devlib.Target instances. OTH, Target seems to somehow support multithreading by opening a separate connection in each thread using it, so we might end up with multiple connection objects. That means that once moved to the connection object, _connected_as_root would need to be kept in sync by Target, which indicates it should stay in Target, and that Target should be responsible for rooting the device.

AFAICS that attribute would now "lie" since that is now up to the connection to decide what to do.

That is a very good point. To prevent this and avoid need needing to implement the logic behind tracking the connected state across connections, it seems to make sense to just remove the caching behind the connected_as_root property and let the root status be queried as needed assuming this is property that would not be accessed too frequently to cause a performance impact.

That means that once moved to the connection object, _connected_as_root would need to be kept in sync by Target, which indicates it should stay in Target, and that Target should be responsible for rooting the device.

If we go with the approach stated above for determining connected_as_root as a target property then this would prevent the requirement to keep the status synchronised like you said, however as for the responsibility of rooting the device, a Target is independent of it's connection type and the method of rooting the device for that particular connection (e.g. adb vs ssh) would vary, so I think that the responsibility would make more sense to be part of the connection class itself.

it seems to make sense to just remove the caching behind the connected_as_root property

is_rooted is now used in a few places in LISA to change the behavior of client code when some optional-but-good-to-have operations are not possible.
Here is a suggestion: If all connection types support a kind of "rooting" concept, then all connections could gain an is_rooted property that is not cached (i.e. it will always poll the device, so it cannot go out of sync wrt other active connections). The Target class could just read that property after creating the connection, cache it and re-expose it as Target.is_rooted. AndroidTarget.adb_root() would update that cached attribute.

as for the responsibility of rooting the device, a Target is independent of it's connection type and the method of rooting the device for that particular connection (e.g. adb vs ssh) would vary

Good point.

The Target class could just read that property after creating the connection, cache it and re-expose it as Target.is_rooted. AndroidTarget.adb_root() would update that cached attribute.

I think there should be a distinction between connected_as_root and the is_rooted property. is_rooted is currently a property of a Target which indicates whether a target itself is able to provide root access in some way, (e.g. being connected directly as root or via su etc.) and that is independent of the connection and should not change over the lifetime of a Target, unlike connected_as_root so I think these two properties should stay unrelated in that sense?

Makes sense, so let me rephrase my previous suggestion as:

un-cache Target.connected_as_root, so it's always reflecting reality.
cache Target.is_rooted, and invalidate the cache from AndroidTarget.adb_root().

This means that the responsibility for connecting as root is entirely left to the connection, but the responsibility for exposing the connected_as_root status to the user is left to the target, using the current execute("id") method. Since is_rooted can actually change for AndroidTarget because of adb_root(), its caching is manually managed instead of using memoized().

When attempting to implement this a few potential issues were uncovered so as a result this update has un-memoized is_rooted and implemented its own caching which also relys on the connected_as_root property which is now left to the connection to track and cache as appropriate per connection.
The adb connection root status is cached manually and is updated / invalided either by calling  adb_root, which is now a method of the AdbConnection also used by AndroidTarget for compatibility, or from target methods that reset/reboot the device.
This allows for the state of multiple connections to the same android target to share the rooted state while not affecting connection to other devices.
I think this should allow for everything to reflect an up to date state of the connection while avoiding unnecessary calls to the target for each call.

Looks like it would solve the issue, thanks for looking into that @setrofim :)


Connecting to required app resource failed

Wont let me generate a seed it keeps saying error
Click to see error details
{
"headers": {
"normalizedNames": {},
"lazyUpdate": null,
"headers": {}
},
"status": 0,
"statusText": "Unknown Error",
"url": "/minecraft_toolbox/resources/data/asset_definitions.json",
"ok": false,
"name": "HttpErrorResponse",
"message": "Http failure response for /minecraft_toolbox/resources/data/asset_definitions.json: 0 Unknown Error",
"error": {
"isTrusted": true

A browser addon most likely disallowed the connection to the file.
Please try using a different browser, or try disabling browser addons.


gh-1735: add vector to additional fields of reference

Fixes #1735

Thank you for the contribution, and welcome to the family!
Please add some test that make it impossible to allow a regression on this bug to happen. For example, here are some end2end tests that query references, you should be able to easily add another to this that queries a ref together with _additional{ vector }, etc.


Last.fm Not Authorized

OS: macOS 10.11.6
Issue Descriptions: After upgrading this morning to 3.6.0, the player stopped scrobbling. This has happened before and usually just requires unauthorizing and re-authorizing in the Preferences. So I did that and now I can't authorize. I will click "Log In to Last.fm", it will briefly flash "Authorization in Progress", and then go right back to "Not Authorized".
I also cleared out relevant files in ~/Library/Preferences and ~/Library/Application Support and restarted the application. This made no difference.
Steps to Reproduce: Unauthorized Last.fm, try to re-authorize it
No relevant logs were found in ~/Library/Application Support/Google Play Music Desktop Player/gpmdc.log and I could not find any other log files. If there is one, I can provide the contents if requested

I am experiencing the same issue. Mac OS X 10.11.6, and GPMDP v3.6.0.

Looks like Squirrel hit an update glitch and corrupted the LASTFM constants file.  Please download the latest version 3.6.0 from the website again.
www.googleplaymusicdesktopplayer.com
Sorry for the hassle, something strange happened in the latest mac update.

Seems like I'm having the same issue with GPMDP v4.0.1 (just installed the app for the first time) and macOS 10.12.1.
If I click the "Login to last.fm" button, the title changes to "Last.fm status: Authorization in progress" and just freezes there.

@jtiala The issue you are experiencing was fixed in master and will be out next release

Is it possible to get/compile the latest .app from the master branch?

I'm seeing this 4.0.2 after I logged out of last.fm, I'm unable to log back in (hangs and with the authorization in progress warning)

coincidental

👍 😆

I'm facing this same issue on Linux.


Add a warning when writing a Python file inside virtual environments

This is similar to https://github.com/microsoft/pylance-release/issues/3550 but when users save their Python files inside a virtual environment. Apparently there are tutorials out there that are directing users to save their Python files inside venvs and the Python extension does not behave well like that. It'd be nice if we could show an error when we when users are trying to change and save a file, so users can either move their files outside of a virtual environment, or just know they might be making edits to the wrong file.

How do you propose to determine when a user saves a file in a virtual environment? How does that look different from any other source file in a virtual environment?

For a virtual environment at this location: C:\GIT\project\.venv.
The python path for this would be:
Windows: C:\GIT\project\.venv\scripts\python.exe
Linux\mac: C:\GIT\project\.venv\bin\python
Following location are under the venv:
C:\GIT\project\.venv
C:\GIT\project\.venv\lib\site-packages

Adding files under C:\GIT\project\.venv should be treated as bad practice.
This is probably what we want to tell the users. From venv documentation: https://docs.python.org/3/library/venv.html
A virtual environment is (amongst other things):
- Used to contain a specific Python interpreter and software libraries and binaries which are needed to support a project (library or application). These are by default isolated from software in other virtual environments and Python interpreters and libraries installed in the operating system.
- Contained in a directory, conventionally either named venv or .venv in the project directory, or under a container directory for lots of virtual environments, such as ~/.virtualenvs.
- Not checked into source control systems such as Git.
- Considered as disposable – it should be simple to delete and recreate it from scratch. You don’t place any project code in the environment
- Not considered as movable or copyable – you just recreate the same environment in the target location.

How does that look different from any other source file in a virtual environment?

It does not. Editing the files inside the venv itself is the bad practice here. I think, if the user adds their project files, or edits a file that belongs to some third-party package, all should be treated the same way.

... if the user adds their project files

What operation are you suggesting would trigger such an error? A save operation? I don't think language servers are told when a file is saved to disk.

... or edits a file

Are you suggesting that files opened from within a venv should be marked as read-only so they cannot be edited? Some users might find that annoying, so it would probably need to be a configuration option. Also, I'm not aware of a way for a language server to tell VS Code that certain files must be treated as read-only, but perhaps there's some mechanism I don't know about.

We wouldn't mark the files as read-only, the idea is to just show a warning that could be dismissed and disabled if the action is intentional.
From what I understood when chatting with @rchiodo it sounded like it was possible to trigger such a warning on a file save request?

Yeah we would do this on the VS code client using its API. It wouldn't be in Pyright.


bug: IonScroll event are not triggered

Bug Report
Ionic version:
3.6.0
Current behavior:
The ionScroll events are not triggered on ion-content if there is ion-slides inside it
Expected behavior:
IonScroll event should be triggered
Related code:
<ion-content (ionScroll)="scrollHandler($event)">
  <ion-slides>
    <ion-slide>
      <div> Something </div>
    </ion-slide>
    <ion-slide>
      ...
    </ion-slide>
 </ion-slides>
</ion-content>

Method scrollHandler is never triggered
Is the same issue as here: https://github.com/ionic-team/ionic/issues/13188 but there is no solution for this and adding div below ion-slides as suggested is not working

Thanks for the issue. Please see the documentation: https://ionicframework.com/docs/api/content#properties. It states that scrollEvents must be set to true for scroll events to be emitted.
Additionally, scroll events do not fire on ion-slides because there is no scrolling. All transforms of ion-slides are done with translate3d in CSS.


Cleyton Antonio dos Santos - MongoDb - Exercicio 01 Resolvido

Formatação errada https://github.com/StunerX/be-mean-instagram-mongodb-exercises/blob/8595cb3a839b3072905f0df8d556c73540f9dda6/class-01/class-01-resolved-stunerx-cleyton-antonio-dos-santos.md

Errada tb https://github.com/StunerX/be-mean-instagram-mongodb-exercises/blob/5d755cb3b1f7eedbc4bd6f52a80bfccbafe40980/class-03/class-03-resolved-stunerx-cleyton-antonio-dos-santos.md

Corrija as formatações e reenvie por favor.


Question about subgraph forking

The log file reports: No fork base URL specified, subgraph forking is disabled. The help of graph-node says:
--fork-base <URL>                                            Base URL for forking subgraphs

What's subgraph forking? Should it be enabled or disabled by default? What should parameter fork-base be in a standalone envirment?

I get the answer from: https://thegraph.com/docs/en/cookbook/subgraph-debug-forking/.


Fold loadBalancerConfig into apiServerConfig since this load

balancer only applies to API servers.

retest this please

retest this please

retest this please


Scala 2.11 cross build

finagle-http now has a 2.11 published version so 2.11 cross build support is simple
fixes #109

project no longer maintained


Bug 2071491: Fix storage throughput value in Top Consumers card

📝 Description
The values for storage throughput in the top consumers card were being reported incorrectly when compared with the same metric in the top consumers dashboard in Observe > Dashboards. This PR fixes the issue by using the correct function to convert from the bytes returned from Prometheus to the unit to be displayed.
🎥 Screenshot
Before:

After:

/retest

/retest

Should the storage throughput be Bytes per second?

Shouldn't the storage throughput be bytes per second instead of bytes? I think the issue is that numbers were interpreted as MBs and not Bs

I originally thought that as well, which is why the bug existed in the first place. If you look at the y-axis of the graph in the left side of the screenshot, they're using the same units now. The queries used for the left and right sides are identical.
I believe the metric is supposed to indicate the total amount of data written and read at a given point in time.

/cherrypick release-4.11

@yaacov I'm in the kubevirt-ui org. Do you have any idea why the cherrypick command failed for me?

/cherrypick release-4.11


Fix path to sample: displaysceneintabletopar

Section titled Sample Code is missing in Display scene in tabletop AR sample:
https://master-stage.developers.arcgis.com/android/latest/java/sample-code/display-scene-in-tabletop-ar/.
I corrected code sample (aka snippet) path in  json metadata file so it matches the package path in MainActivity.java. Changed code from
"snippets": [
        "src/main/java/com/esri/arcgisruntime/displaytabletopmapinar/MainActivity.java"
    ],

to this
"snippets": [
        "src/main/java/com/esri/arcgisruntime/sample/displaysceneintabletopar/MainActivity.java"
    ],

At next publish to web, this should publish correctly from the sample repo to the Sample Code tab for Android on the live web site.

Per bug https://github.com/Esri/arcgis-runtime-samples-android/issues/657

Here it is with the Sample Code section fixed:
https://mjd-sample-fix-android-ar-preview-dev.developers.arcgis.com/android/latest/java/sample-code/display-scene-in-tabletop-ar/


add JS solution for array sum

For #57

Converting to string is a smart idea. There recently was another PR for adding a Javascript version here:
https://github.com/mre/the-coding-interview/commit/153017469aba0f0f5230f643219977b5e0e8c998
Not sure which version I prefer.

Closing this as we have a solution in master now. But thanks anyway for tackling this. Hope you look into other problems, too.


Why libpointmatcher works bad?

I download the indoor "Apartment" dataset of "Challenging data sets for point cloud registration algorithms". Then, I use libpointmatcher to align the point clouds taken by Hokuyo. We use the default parameters and set good initial guess based on the ground truth. However, for many pairs, the libpointmatcher performs very bad. The reference point clouds after alignment are just moved a litter compared with the reference point clouds before  alignment. Is the parameters not suitable? and the dataset of "NIFTi: multi-floor mapping:" or demo code is publicly available?

Interesting title for the issue.
The quick answer would be: because you didn't tuned the ICP solution to the application.
Long answer:
The default parameters are very light and were tuned to do the bare minimum with the basic unit test we have. They work also with the example code:
$ ./pmicp ../example/data//cloud.00000.vtk ../example/data//cloud.00001.vtk

The goal of the library is to provide flexibility in its configuration so it can fit to different applications, not to provide one solution that should fit all problems.

If you want to learn what the different modules are doing, you can start with our tutorials in the beginner section.
If you're looking for classical ICP solutions, you can find some parameter files here. Those were evaluated using the "Challenging data sets for point cloud registration algorithms" in this paper.

This library produces scan to scan alignment and is intended for developers who want to build there own solution on top of it. Building a large consistent map is a larger topic. The "NIFTi: multi-floor mapping" video, and most of the continuous mapping videos are from this code. The content of this repository is used for our research needs and is not supported for the greater public in general. The dataset was recorded under ROS format and was not aimed at public usage.
I hope it clarify the goals of the library and its intended use.

If there is no follow up on this, I'll close the issue.


TxHash Base58 Method

SubmitPayment should either return a tx hash object that has a base58 method or add a generic base58 method to utils.go. It was not obvious how to turn txHash into something that can be inspected on the blockchian.
SubmitPayment(ctx context.Context, payment Payment, opts ...SolanaOption) (txHash []byte, err error)

what would you recommend here?

what would you recommend here?


Add a Server Guide

Add a guide on how to do more and more complicated things with the Server/Handler in docs/guide/server.md.

So what sort of spec would you hold for this guide? like what points should it cover?

I could imagine the guide going in steps:

Introduce the Handler trait. Such as show how to make a simple "Hello World" handler, like from the examples/hello.rs.
Explain WouldBlock, and/or try_read/try_write, and repeating with Next until the IO is done.
Introduce some routing, using req.uri().
Add an additional blocking service, like a worker pool. This would show off how to use Next::wait() and Control.ready().

Somewhere in there, sometimes it makes sense to skip explaining all the pieces, and then eventually explain "So remember Handler<HttpStream>? That's actually a Transport, go read about the Transport docs." or something.

I'm currently fiddling with the docs script, to try to pull in any .md file in the doc directory, so that the guides will be part of the docs at http://hyper.rs/hyper, and can even be versioned.


Does IREE support native cuda buffer VM invocation or is there any chance to improve the performance of result torch tensors construction?

Hello, IREE developers, I've seen a similar question asked before: https://github.com/iree-org/iree/issues/11573#issuecomment-1371128261, but it seems lack of further discussion.
Suppose we have  a common resnet-50 inference script to be run using Pytorch/IREE, and the input torch tensors are both already in cuda device:
import time
from transformers import AutoImageProcessor, ResNetModel
import torch
from datasets import load_dataset

dataset = load_dataset("huggingface/cats-image")
image = dataset["test"]["image"][0]
image_processor = AutoImageProcessor.from_pretrained("microsoft/resnet-50")
model = ResNetModel.from_pretrained("microsoft/resnet-50")

device = "cuda"
model.to(device)

inputs = image_processor(image, return_tensors="pt")

# inputs are now device tensor list
inputs.to(device)

compiled_model = torch.compile(model, backend="turbine_cuda")
nwarm = 1
n = 10

# warm up
for i in range(nwarm):
    o1 = compiled_model(**inputs)

# n run for iree compiled model
t0 = time.time()
for i in range(n):
    o1 = compiled_model(**inputs)
t1 = time.time()
print(o1.last_hidden_state)
print(f"iree run: {t1 - t0} s")

For Vm context invocation, the current default method used by turbine is to construct DeviceArray  and wrap buffer into a iree_hal_buffer_t type variable, which might introduce redundant copy in AllocateBufferCopy (https://github.com/iree-org/iree/blob/05bbcf1385146d075829cd940a52bf06961614d0/runtime/bindings/python/hal.cc#L165), I did a little hack to used a lower level API like iree_hal_cuda_buffer_wrap  rather than iree_hal_device_transfer_h2d to wrap a cuda device buffer directly and avoid copy.
However, such process is still look very time consuming, I did a simple profile by nsight for such process in turbine (https://github.com/iree-org/iree-turbine/blob/1aa05e04d333bd2485337fbbe83c1c84a7c5e7f5/iree/turbine/dynamo/executor.py#L93), the profiler result shows that the process of iree_hal_buffer_t construction and unwraping iree_hal_buffer_t back to torch tensor takes about the same amount of time as vm context invoke:

I know that the design principle of HAL layer is mainly to compatible with buffers of different device platforms and convenient for buffer management, but is there any possible to hack into iree, to let it support a more native cuda buffer vm invocation for better performance? Or are there any better methods to improve the performance for result tensors construction?
Thanks.

You want the buffer import API, which let's you wrap a CUDA device pointer in an iree_hal_buffer_t: https://github.com/iree-org/iree/blob/05bbcf1385146d075829cd940a52bf06961614d0/runtime/src/iree/hal/allocator.h#L379

Yeah, I use an analogy buffer import API to wrap a cuda device buffer in a iree_hal_buffer_t  handle, but it's a cuda platform specific API:
https://github.com/iree-org/iree/blob/05bbcf1385146d075829cd940a52bf06961614d0/runtime/src/iree/hal/drivers/cuda/cuda_buffer.c#L37
However, through profiling result, I found that such purely buffer import/wrap procedure seems still very time cumsuming. For example, let's suppose we have a 400 length size input torch tensor list, which means that we have to do 400 times buffer import/wrap to create input variant list as vm invoation's input.
After vm invocation, we also have to use dlpack to unwrap iree_hal_buffer_view_t  and marshal output torch tensor. Let's also suppose output return list's length size is 450, we have to do this marshal procedure 450 times.  Overall, such buffer import and tensor marshal procedure takes about the same amount of time as vm context invoke.
Therefore, my curious is about are there any other more 'torch tensor native' hacking ways, to let IREE's VM support Pytorch tensor as input and output directly for better performance?
Or since that such torch.compile wrapper is an "outdated" way to invoke IREE, are there any other more Pytorch performance friendly usages to run above inference script?
Thanks.

First off, hundreds of tensors for something like that isn't great. I guess that's just because torch.compile functionalizes everything. Not a great design for performance even if all of the latencies are eliminated.
I think we'll end up just writing a C extension properly at some point and doing some manner of fast bulk import. The device pointer import case can be fast pathed but taking that much stuff through so many layers of python marshaling is never going to be particularly good. When I was writing all of the dlpack marshal code, I was just cringing looking at all of the tolls that get exacted just to exchange device pointers. For casual use or a small number of things, it is ok. For hundreds, there's no way to make that good. Need to drop down to an optimized c implementation for that level of marshaling, I expect.
There are also lower level APIs for allocating a result slab as one backing allocation and then having that be used by iree. It's not super straightforward to get everything to line up, but if doing it over again (which we are going to have to do), I would have just started there.
Probably not the answer you're looking for.

We could probably skip the dlpack stuff and just use data_ptr (https://pytorch.org/docs/stable/generated/torch.Tensor.data_ptr.html).
If doing that from python, it still wouldn't be as fast as it could be in c, but we could probably add some optimized API to the iree python API to take a bunch of torch tensors in bulk and get them into iree as fast as possible.
And then use the result buffer ABI to pass in one torch allocated result buffer and have IREE write into that vs returning individual tensors. For torch.compile, we'd need to do a little work to emit some kind of result size calculation so not just guessing. A lot of that information is in the metadata but needs to be found and used carefully.
Then basically get that down to one call into iree per invocation to handle all of it n+m calls to handle the inputs and results separately. It still wouldn't be free but could be made as fast as possible.

BTW, I would like to ask when the IREE upstream community would start or complete this part of  VM input/output data transfer optimization development? Can we expect it to be determined at an approximate time point? Hope this doesn't cause any disturbance:-)

This is raising in importance for some of the core contributors too and I am trying to see where it can slot in on a roadmap. The issue is that this is a relatively tricky thing and only a few people know all of the things involved.
Let me try to refresh some state on the output parameter thing. It requires generating the functions differently, which is something that I thought would always be needed to really serve the torch.compile case well but never had the time to actually flesh out the idea (the other reason for this is that it is needed for handling non contiguous input layouts without a copy).
These are all the reasons why I say that the current torch.compile thing is a demo and it was only ever written for CPU. Doing it right is a relatively advanced use of both the compiler and runtime: not hard per se but detailed.
Can't make a promise when, but I will at least try to write down a design for how this should work.

Thank you Stellar. I look forward to seeing the community's progress in this regard soon.
I will also continue to pay attention to the progress in this regard.


Bug: Weird crash when showing a Lottie animation : "Invalid Layer Save Flag"

Tested on Pixel 2 with Android P DP3.
I tried to disable hardware acceleration. Didn't help.
The same issue was reported on the lottie-android library:
https://github.com/airbnb/lottie-android/issues/802
I'm getting the next exception:
Java.Lang.IllegalArgumentException: Invalid Layer Save Flag - only ALL_SAVE_FLAGS is allowed
Steps to reproduce :scroll:

See isson on lottie-android, there is a animation / code file uploaded there to reproduce this exception
Test on a Android P device/emulator

Expected behavior :thinking:
The animation should work when targetting the new Android P firmware
Actual behavior :bug:
There is a crash right away
Configuration :wrench:
Version: 2.5.4
Platform:

[ ] :iphone: iOS
[x] :robot: Android
[ ] :checkered_flag: WPF
[ ] :earth_americas: UWP
[ ] :apple: MacOS
[ ] :tv: tvOS
[x] :monkey: Xamarin.Forms

Im testing this on a Xamarin Forms projects on an Android device or emulator

Seems like it would be fixed if you use the latest aar from android lottie:
https://mvnrepository.com/artifact/com.airbnb.android/lottie/2.5.6

@fabionuno could you make a PR to update the bindings to the latest version to fix this?

Update with 2.6.0 is available on Nuget


@see without description not working

If I use @see className, nothing shows up.. I need to type @see className className for it to be effective.

I believe this issue is resolved in version 2.6; I want to test this again to be sure

@mvriel: Just checked, it's still there in 2.8.5 (tested "clean" and "responsive" templates).

I'm investigating the issue using this test file and the phpDocumentor2 code base. The phpDocumentor2 version is the latest master but using version 2.0.5 of phpdocumentor/reflection-docblock
TestSeeTagIssue.php.zip

The results are as follows for templates responsive and clean:
namespace phpDocumentor\Descriptor;

use \phpDocumentor\Descriptor\Builder\AssemblerAbstract;

/**
 * Class to check if see tags are working correctly
 *
 * Inline relative class {@see AssemblerAbstract testClass relative} : responsive + clean ok
 * Inline relative class {@see AssemblerAbstract} : responsive + clean ok
 *
 * Inline absolute class {@see \phpDocumentor\Descriptor\Builder\AssemblerAbstract testClass absolute} : responsive + clean ok
 * Inline absolute class {@see \phpDocumentor\Descriptor\Builder\AssemblerAbstract} : responsive + clean ok
 *
 * Inline relative method {@see AssemblerAbstract::getBuilder() testMethod relative} : responsive + clean ok
 * Inline relative method {@see AssemblerAbstract::getBuilder()} : responsive + clean ok
 *
 * Inline absolute method {@see \phpDocumentor\Descriptor\Builder\AssemblerAbstract::getBuilder() testMethod absolute} : responsive + clean ok
 * Inline absolute method {@see \phpDocumentor\Descriptor\Builder\AssemblerAbstract::getBuilder()} : responsive + clean ok
 *
 * Inline relative property {@see AssemblerAbstract::$builder testProperty relative} : responsive + clean ok
 * Inline relative property {@see AssemblerAbstract::$builder} : responsive + clean ok
 *
 * Inline absolute property {@see \phpDocumentor\Descriptor\Builder\AssemblerAbstract::$builder testProperty absolute} : responsive + clean ok
 * Inline absolute property {@see \phpDocumentor\Descriptor\Builder\AssemblerAbstract::$builder} : responsive + clean ok
 *
 * Inline see to same class relative {@see TestSeeTagIssue} : responsive + clean ok
 * Inline see to same class absolute {@see \phpDocumentor\Descriptor\TestSeeTagIssue} : responsive + clean ok
 *
 * Inline see to same class relative {@see \phpDocumentor\Descriptor\TestSeeTagIssue class itself} : responsive + clean ok
 * Inline see to same class absolute {@see \phpDocumentor\Descriptor\TestSeeTagIssue class itself} : responsive + clean ok
 *
 * Inline see to property in same class relative {@see TestSeeTagIssue::$property} : responsive + clean ok
 * Inline see to property in same class absolute {@see \phpDocumentor\Descriptor\TestSeeTagIssue::$property} : responsive + clean ok
 *
 * Inline see to property in same class relative {@see TestSeeTagIssue::$property own property} : responsive + clean ok
 * Inline see to property in same class absolute {@see \phpDocumentor\Descriptor\TestSeeTagIssue::$property own property} : responsive + clean ok
 *
 * Inline see to method in same class relative {@see TestSeeTagIssue::method()} : responsive + clean ok
 * Inline see to method in same class absolute {@see \phpDocumentor\Descriptor\TestSeeTagIssue::method()} : responsive + clean ok
 *
 * Inline see to method in same class relative {@see TestSeeTagIssue::method() own method} : responsive + clean ok
 * Inline see to method in same class absolute {@see \phpDocumentor\Descriptor\TestSeeTagIssue::method() own method} : responsive + clean ok
 *
 * @see AssemblerAbstract : responsive wrong (no text, corrupt link), clean wrong (is linking to container class, text ok)
 * @see AssemblerAbstract with description : responsive wrong (corrupt link), clean wrong (is linking to container class, text ok)
 *
 * @see \phpDocumentor\Descriptor\Builder\AssemblerAbstract : responsive wrong (no text, corrupt link), clean ok
 * @see \phpDocumentor\Descriptor\Builder\AssemblerAbstract with description : responsive wrong (corrupt link), clean ok
 *
 * @see AssemblerAbstract::getBuilder() : responsive wrong (no text, corrupt link), clean ok
 * @see AssemblerAbstract::getBuilder() with description : responsive wrong (corrupt link), clean ok
 *
 * @see \phpDocumentor\Descriptor\Builder\AssemblerAbstract::getBuilder() : responsive wrong (no text, corrupt link), clean ok
 * @see \phpDocumentor\Descriptor\Builder\AssemblerAbstract::getBuilder() with description : responsive wrong (corrupt link), clean ok
 *
 * @see AssemblerAbstract::$builder : responsive wrong (no text, corrupt link), clean works but missing $ sign in text
 * @see AssemblerAbstract::$builder with description : responsive wrong (corrupt link), clean ok
 *
 * @see \phpDocumentor\Descriptor\Builder\AssemblerAbstract::$builder : responsive wrong (no text, corrupt link), clean works but missing $ sign in text
 * @see \phpDocumentor\Descriptor\Builder\AssemblerAbstract::$builder with description : responsive wrong (corrupt link), clean ok
 *
 * @see TestSeeTagIssue : responsive wrong (no text, corrupt link), clean ok
 * @see TestSeeTagIssue class itself : responsive wrong (corrupt link), clean ok
 *
 * @see \phpDocumentor\Descriptor\TestSeeTagIssue : responsive wrong (no text, corrupt link), clean ok
 * @see \phpDocumentor\Descriptor\TestSeeTagIssue class itself : responsive wrong (corrupt link), clean ok
 *
 * @see TestSeeTagIssue::$property : responsive wrong (no text, corrupt link), clean works but missing $ sign in text
 * @see TestSeeTagIssue::$property own property : responsive wrong (corrupt link), clean ok
 *
 * @see \phpDocumentor\Descriptor\TestSeeTagIssue::$property : responsive wrong (no text, corrupt link), clean works but missing $ sign in text
 * @see \phpDocumentor\Descriptor\TestSeeTagIssue::$property own property : responsive wrong (corrupt link), clean ok
 *
 * @see TestSeeTagIssue::method() : responsive wrong (no text, corrupt link), clean ok
 * @see TestSeeTagIssue::method() own method : responsive wrong (corrupt link), clean ok
 *
 * @see \phpDocumentor\Descriptor\TestSeeTagIssue::method() : responsive wrong (no text, corrupt link), clean ok
 * @see \phpDocumentor\Descriptor\TestSeeTagIssue::method() own method : responsive wrong (corrupt link), clean ok
 */
class TestSeeTagIssue
{
    /**
     * Test property to check if see tags are working correctly
     *
     * Inline relative class {@see AssemblerAbstract testClass relative} : responsive + clean ok
     * Inline relative class {@see AssemblerAbstract} : responsive + clean ok
     *
     * Inline absolute class {@see \phpDocumentor\Descriptor\Builder\AssemblerAbstract testClass absolute} : responsive + clean ok
     * Inline absolute class {@see \phpDocumentor\Descriptor\Builder\AssemblerAbstract} : responsive + clean ok
     *
     * Inline relative method {@see AssemblerAbstract::getBuilder() testMethod relative} : responsive + clean ok
     * Inline relative method {@see AssemblerAbstract::getBuilder()} : responsive + clean ok
     *
     * Inline absolute method {@see \phpDocumentor\Descriptor\Builder\AssemblerAbstract::getBuilder() testMethod absolute} : responsive + clean ok
     * Inline absolute method {@see \phpDocumentor\Descriptor\Builder\AssemblerAbstract::getBuilder()} : responsive + clean ok
     *
     * Inline relative property {@see AssemblerAbstract::$builder testProperty relative} : responsive + clean ok
     * Inline relative property {@see AssemblerAbstract::$builder} : responsive + clean ok
     *
     * Inline absolute property {@see \phpDocumentor\Descriptor\Builder\AssemblerAbstract::$builder testProperty absolute} : responsive + clean ok
     * Inline absolute property {@see \phpDocumentor\Descriptor\Builder\AssemblerAbstract::$builder} : responsive + clean ok
     *
     * Inline see to same class relative {@see TestSeeTagIssue} : responsive + clean wrong (doesn't make a link, text is ok)
     * Inline see to same class absolute {@see \phpDocumentor\Descriptor\TestSeeTagIssue} : responsive + clean ok
     *
     * Inline see to same class relative {@see \phpDocumentor\Descriptor\TestSeeTagIssue class itself} : responsive + clean ok
     * Inline see to same class absolute {@see \phpDocumentor\Descriptor\TestSeeTagIssue class itself} : responsive + clean ok
     *
     * Inline see to property in same class relative {@see TestSeeTagIssue::$property} : responsive + clean wrong (doesn't make a link, text is ok)
     * Inline see to property in same class absolute {@see \phpDocumentor\Descriptor\TestSeeTagIssue::$property} : responsive + clean ok
     *
     * Inline see to property in same class relative {@see TestSeeTagIssue::$property own property} : responsive + clean wrong (doesn't make a link, text is ok)
     * Inline see to property in same class absolute {@see \phpDocumentor\Descriptor\TestSeeTagIssue::$property own property} : responsive + clean ok
     *
     * Inline see to method in same class relative {@see TestSeeTagIssue::method()} : responsive + clean wrong (doesn't make a link, text is ok)
     * Inline see to method in same class absolute {@see \phpDocumentor\Descriptor\TestSeeTagIssue::method()} : responsive ok
     *
     * Inline see to method in same class relative {@see TestSeeTagIssue::method() own method} : responsive + clean wrong (doesn't make a link, text is ok)
     * Inline see to method in same class absolute {@see \phpDocumentor\Descriptor\TestSeeTagIssue::method() own method} : responsive + clean ok
     *
     * @see AssemblerAbstract : responsive wrong (no text, corrupt link), clean wrong (is linking to container class, text ok)
     * @see AssemblerAbstract with description : responsive wrong (corrupt link), clean wrong (is linking to container class, text ok)
     *
     * @see \phpDocumentor\Descriptor\Builder\AssemblerAbstract : responsive wrong (no text, corrupt link), clean ok
     * @see \phpDocumentor\Descriptor\Builder\AssemblerAbstract with description : responsive wrong (corrupt link), clean ok
     *
     * @see AssemblerAbstract::getBuilder() : responsive wrong (no text, corrupt link), clean ok
     * @see AssemblerAbstract::getBuilder() with description : responsive wrong (corrupt link), clean ok
     *
     * @see \phpDocumentor\Descriptor\Builder\AssemblerAbstract::getBuilder() : responsive wrong (no text, corrupt link), clean ok
     * @see \phpDocumentor\Descriptor\Builder\AssemblerAbstract::getBuilder() with description : responsive wrong (corrupt link), clean ok
     *
     * @see AssemblerAbstract::$builder : responsive wrong (no text, corrupt link), clean works but missing $ sign in text
     * @see AssemblerAbstract::$builder with description : responsive wrong (corrupt link), clean ok
     *
     * @see \phpDocumentor\Descriptor\Builder\AssemblerAbstract::$builder : responsive wrong (no text, corrupt link), clean works but missing $ sign in text
     * @see \phpDocumentor\Descriptor\Builder\AssemblerAbstract::$builder with description : responsive wrong (corrupt link), clean ok
     *
     * @see TestSeeTagIssue : responsive wrong (no text, corrupt link), clean ok
     * @see TestSeeTagIssue class itself : responsive wrong (corrupt link), clean ok
     *
     * @see \phpDocumentor\Descriptor\TestSeeTagIssue : responsive wrong (no text, corrupt link), clean ok
     * @see \phpDocumentor\Descriptor\TestSeeTagIssue class itself : responsive wrong (corrupt link), clean ok
     *
     * @see TestSeeTagIssue::$property : responsive wrong (no text, corrupt link), clean works but missing $ sign in text
     * @see TestSeeTagIssue::$property own property : responsive wrong (corrupt link), clean ok
     *
     * @see \phpDocumentor\Descriptor\TestSeeTagIssue::$property : responsive wrong (no text, corrupt link), clean works but missing $ sign in text
     * @see \phpDocumentor\Descriptor\TestSeeTagIssue::$property own property : responsive wrong (corrupt link), clean ok
     *
     * @see TestSeeTagIssue::method() : responsive wrong (no text, corrupt link), clean ok
     * @see TestSeeTagIssue::method() own method : responsive wrong (corrupt link), clean ok
     *
     * @see \phpDocumentor\Descriptor\TestSeeTagIssue::method() : responsive wrong (no text, corrupt link), clean ok
     * @see \phpDocumentor\Descriptor\TestSeeTagIssue::method() own method : responsive wrong (corrupt link), clean ok
     */
    protected $property;

    /**
     * Test method to check if see tags are working correctly
     *
     * Inline relative class {@see AssemblerAbstract testClass relative} : responsive + clean ok
     * Inline relative class {@see AssemblerAbstract} : responsive + clean ok
     *
     * Inline absolute class {@see \phpDocumentor\Descriptor\Builder\AssemblerAbstract testClass absolute} : responsive + clean ok
     * Inline absolute class {@see \phpDocumentor\Descriptor\Builder\AssemblerAbstract} : responsive + clean ok
     *
     * Inline relative method {@see AssemblerAbstract::getBuilder() testMethod relative} : responsive + clean ok
     * Inline relative method {@see AssemblerAbstract::getBuilder()} : responsive + clean ok
     *
     * Inline absolute method {@see \phpDocumentor\Descriptor\Builder\AssemblerAbstract::getBuilder() testMethod absolute} : responsive + clean ok
     * Inline absolute method {@see \phpDocumentor\Descriptor\Builder\AssemblerAbstract::getBuilder()} : responsive + clean ok
     *
     * Inline relative property {@see AssemblerAbstract::$builder testProperty relative} : responsive + clean ok
     * Inline relative property {@see AssemblerAbstract::$builder} : responsive + clean ok
     *
     * Inline absolute property {@see \phpDocumentor\Descriptor\Builder\AssemblerAbstract::$builder testProperty absolute} : responsive + clean ok
     * Inline absolute property {@see \phpDocumentor\Descriptor\Builder\AssemblerAbstract::$builder} : responsive + clean ok
     *
     * Inline see to same class relative {@see TestSeeTagIssue} : responsive + clean wrong (doesn't make a link, text is ok)
     * Inline see to same class absolute {@see \phpDocumentor\Descriptor\TestSeeTagIssue} : responsive + clean ok
     *
     * Inline see to same class relative {@see \phpDocumentor\Descriptor\TestSeeTagIssue class itself} : responsive + clean ok
     * Inline see to same class absolute {@see \phpDocumentor\Descriptor\TestSeeTagIssue class itself} : responsive + clean ok
     *
     * Inline see to property in same class relative {@see TestSeeTagIssue::$property} : responsive + clean wrong (doesn't make a link, text is ok)
     * Inline see to property in same class absolute {@see \phpDocumentor\Descriptor\TestSeeTagIssue::$property} : responsive + clean ok
     *
     * Inline see to property in same class relative {@see TestSeeTagIssue::$property own property} : responsive + clean wrong (doesn't make a link, text is ok)
     * Inline see to property in same class absolute {@see \phpDocumentor\Descriptor\TestSeeTagIssue::$property own property} : responsive + clean ok
     *
     * Inline see to method in same class relative {@see TestSeeTagIssue::method()} : responsive + clean wrong (doesn't make a link, text is ok)
     * Inline see to method in same class absolute {@see \phpDocumentor\Descriptor\TestSeeTagIssue::method()} : responsive + clean ok
     *
     * Inline see to method in same class relative {@see TestSeeTagIssue::method() own method} : responsive + clean wrong (doesn't make a link, text is ok)
     * Inline see to method in same class absolute {@see \phpDocumentor\Descriptor\TestSeeTagIssue::method() own method} : responsive + clean ok
     *
     * @see AssemblerAbstract : responsive wrong (no text, corrupt link), clean wrong (is linking to container class, text ok)
     * @see AssemblerAbstract with description : responsive wrong (corrupt link), clean wrong (is linking to container class, text ok)
     *
     * @see \phpDocumentor\Descriptor\Builder\AssemblerAbstract : responsive wrong (no text, corrupt link), clean ok
     * @see \phpDocumentor\Descriptor\Builder\AssemblerAbstract with description : responsive wrong (corrupt link), clean ok
     *
     * @see AssemblerAbstract::getBuilder() : responsive wrong (no text, corrupt link), clean ok
     * @see AssemblerAbstract::getBuilder() with description : responsive wrong (corrupt link), clean ok
     *
     * @see \phpDocumentor\Descriptor\Builder\AssemblerAbstract::getBuilder() : responsive wrong (no text, corrupt link), clean ok
     * @see \phpDocumentor\Descriptor\Builder\AssemblerAbstract::getBuilder() with description : responsive wrong (corrupt link), clean ok
     *
     * @see AssemblerAbstract::$builder : responsive wrong (no text, corrupt link), clean works but missing $ sign in text
     * @see AssemblerAbstract::$builder with description : responsive wrong (corrupt link), clean ok
     *
     * @see \phpDocumentor\Descriptor\Builder\AssemblerAbstract::$builder : responsive wrong (no text, corrupt link), clean works but missing $ sign in text
     * @see \phpDocumentor\Descriptor\Builder\AssemblerAbstract::$builder with description : responsive wrong (corrupt link), clean ok
     *
     * @see TestSeeTagIssue : responsive wrong (no text, corrupt link), clean ok
     * @see TestSeeTagIssue class itself : responsive wrong (corrupt link), clean ok
     *
     * @see \phpDocumentor\Descriptor\TestSeeTagIssue : responsive wrong (no text, corrupt link), clean ok
     * @see \phpDocumentor\Descriptor\TestSeeTagIssue class itself : responsive wrong (corrupt link), clean ok
     *
     * @see TestSeeTagIssue::$property : responsive wrong (no text, corrupt link), clean works but missing $ sign in text
     * @see TestSeeTagIssue::$property own property : responsive wrong (corrupt link), clean ok
     *
     * @see \phpDocumentor\Descriptor\TestSeeTagIssue::$property : responsive wrong (no text, corrupt link), clean works but missing $ sign in text
     * @see \phpDocumentor\Descriptor\TestSeeTagIssue::$property own property : responsive wrong (corrupt link), clean ok
     *
     * @see TestSeeTagIssue::method() : responsive wrong (no text, corrupt link), clean ok
     * @see TestSeeTagIssue::method() own method : responsive wrong (corrupt link), clean ok
     *
     * @see \phpDocumentor\Descriptor\TestSeeTagIssue::method() : responsive wrong (no text, corrupt link), clean ok
     * @see \phpDocumentor\Descriptor\TestSeeTagIssue::method() own method : responsive wrong (corrupt link), clean ok
     */
    public function method()
    {
        // body of method
    }
}

This issue has been fixed.


verify generator/reflector interface oper-state is TESTING

Fixes #2244

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 46.333%

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
1409

Relevant Lines:
3041

💛  - Coveralls


update RHOAI version and how to retrieve installplan name

Get the RHOAI's version as an argument or default to current version.
Get installplan's name from status.installplan.name

Closing this issue while creating another one with a different userid


Linking to the codelab

Hey @ditman,
I'm unsure how best to suggest mods to this codebase, given it's multi-branch organisation. Please feel free to give pointers...
brett

My bad @domesticmouse, please make changes against master, that's the branch that should have the whole shebang with all the changes in a normal git fashion. The other two branches should be always squashed to a few commits so users don't have to clone a ton of history.

(In this case, I broke "begin" by force-pushing without seeing your change, if you just copy the new README.md to master you should be fine)

I've merged this PR as:
https://github.com/FirebaseExtended/codelab-friendlyeats-flutter/commit/21da573491d0e20ba3042b890bc6a45b8257acd2
Thanks, and apologies for the breakage! I've also included a little section in the README pointing people who want to contribute to the master branch.


Dumping External Dlls to BizTalk resources.

I am currently working on a BizTalk  where i need to add external dll. to BizTalk resources.  Can any body please suggest me what all tags and settings i need to do in BTDFPROJ file.
Please suggest.
This work item was migrated from CodePlex
CodePlex work item ID: '8822'
Vote count: '1'

[tfabraham@10/13/2011]
This is a .NET DLL?  Why does it need to be a resource in BizTalk vs. just installed in the GAC like your other BizTalk assemblies?  If you have any external .NET DLL that needs to be installed on the server (in the GAC) along with your BizTalk artifacts, you can use an ExternalAssemblies ItemGroup.  The format is identical to the other common ItemGroup's like Orchestrations, Schemas, etc. (and you should see IntelliSense in the Visual Studio editor in the .btdfproj).  It's unusual to need it to be an actual BizTalk resource in the BizTalk app.

[Zizy@10/14/2011]
thanks for the help!!!
I am having an BizTalk Project which is consuming a webservice. This BizTalk project is only having web service in it. I am using the dll reference of this project in my main orchestration project. While deploying app using BTDF i m getting error  like :-
"Failed to deploy orchestration "Demo.ProcessAckNack".
Port "Port_SendACK" of orchestration "Demo.ProcessAckNack" refers to port type "Demo.WebServices.References.DemoWebService.WebService_Try" which has not been deployed."
I was wondering if i can use add resource command "AddResource Command: BizTalk Assembly" in BTDF !!!!
Thank and Regards,
Zizy

[tfabraham@10/14/2011]
Since there's a port type for the web service, I assume that the other DLL that you are asking about is also a BizTalk DLL that contains a web reference (and thus the port type Demo.WebServices.References.DemoWebService.WebService_Try)?  If that is the case, then you should treat that web services DLL as a Schemas artifact because a BizTalk web reference generally has schemas and an orchestration containing port types, and you'd add that file to your Schemas ItemGroup.

[UnknownUser@10/20/2011]

[UnknownUser@2/21/2013]

[UnknownUser@5/16/2013]

Issue closed by tfabraham with comment
Closing since this is not a product issue.  If you're still having trouble, please feel free to post a new topic in the Discussions area.


Include Vue instance when Build Target is Lib mode

What problem does this feature solve?
We are building multiple micro frontend applications that are then stitched together into singular spa experience at run-time. As such, building these applications in using a build target "--target app" is not a viable approach. We need a single file that contains the application source code to load up as we are stitching applications together. For this reason, using a build target "--target lib" seemed like a ideal solution for us. However, we've noticed the build tool contains logic when it is building the application that it excludes Vue instances automatically, which you folks have clearly indicated in your documentation. We weren't able to override this behavior using either the configureWebpack object nor the chainWebpack() callback function.
What does the proposed API look like?
As simple fix would be to move the process of externalizing Vue up prior to applying configureWebpack config object or executing chainWebpack() callback. That way, you are giving programmers the flexibility to include it if it suits their architectural scenario without it being a breaking change.

I've seen that config is defined based on user webpack chain:
https://github.com/vuejs/vue-cli/blob/500dc5020517f8d5780ce1ef85f9c74abc0c184c/packages/%40vue/cli-service/lib/commands/build/resolveLibConfig.js#L29
and then used to remove Vue instances:
https://github.com/vuejs/vue-cli/blob/500dc5020517f8d5780ce1ef85f9c74abc0c184c/packages/%40vue/cli-service/lib/commands/build/resolveLibConfig.js#L57
Is it possible to create the config another way, apply externals and then apply the chain?
If it's not, maybe a flag on vue.config can do that, so we add an "if" before applying externals

Personally, not having reviewed the source code in depth, @trickstival approach seems like a simple, backwards compatible solution to the problem. We would be happy with a change like that!

I'm still trying to understand the project structure as a whole, but I imagine something like that might work:
    if (!api.service.projectOptions.keepVueInstance) {
      // externalize Vue in case user imports it
      config
        .externals({
          ...config.get('externals'),
          vue: {
            commonjs: 'vue',
            commonjs2: 'vue',
            root: 'Vue'
          }
        })
    }

Here in the original file:
https://github.com/vuejs/vue-cli/blob/500dc5020517f8d5780ce1ef85f9c74abc0c184c/packages/%40vue/cli-service/lib/commands/build/resolveLibConfig.js#L57
But I'm not sure how to test it right now, still searching some examples in the project

Looking at the code snippet you provided, I might suggest a slightly different incarnation of it. That approach has a limitation in that if your "keepVueInstance" is false, then externals that the developer wanted to configure will not be applied either.
Maybe something like the following:
       // externalize Vue in case user imports it       config         .externals({           ...config.get('externals'),           ...(!api.service.projectOptions.keepVueInstance ? {                 vue: {                     commonjs: 'vue',                     commonjs2: 'vue',                     root: 'Vue'                }           } : {})         })

That's actually much better!

Apologies for the formatting, just fixed it. I am still learning my way around GitHub's formatting features.

[OFFTOPIC]
If you add js after your backticks you get some code highlighting. Like that:
` ``js
let a = 'hey'
`` `
Without spaces:
let a = 'hey'

i am trying to do something very similar (a core app with modules the user can install, but i don't want to update the app when new modules become available). I justed wanted to start looking into the lib or wc option when i tumbled upon this. If you want to load them at runtime, won't the webcomponent build be an option? or does the webcomponent solution not offer the following capabilities:
<component :is="moduleA">slot content</component>

I'm trying to do this exact thing. Is there any workaround? Also, I wonder if this issue is up for grabs, I would like to work on it.

I'm skeptical about the actual use case.
But if we have to support it, I think vue.config.js is not the best place to put this option, as it only applies the lib or web component target. This name also leads to confusion (Vue instance typically refers to the result of new Vue).
What about adding a flag to the build command? Like:
--inline-vue         include the Vue module in the final bundle of library or web component target

I got my plan to work by globally registering the components i wanted to share to the subcomponents. This way i don't have to call anything special. For data transfer between both i use either props or vuex. I build with target lib and include them using dynamic imports with the native require instead of webpack require.
So far no issues for me

@sodatea When will it be released？ i strongly need this feature

@mithom how do you resolve this question? is there some code to see ?

@sodatea, I really like flag for build command more than vue.config.js option.
Worth updating #4261 PR?

@romansp Yeah go ahead please.

@sodatea I updated #4261 PR. I think we can continue discussion over there.

@sodatea
Is it possible to merge and publish as soon as possible?

This feature is now shipped in both v3.11.0 & v4.0.0-rc.0

@sodatea  thanks. perfect!

When inline flag is true, is Vue attached to global variable?
What if two components bundle different versions of Vue?

@dika-pro no. Vue is module


Refactor emote matching implementation

Reimplementation of the matcher, instead of trying to break up message content into array of words and then iterating through that, it steps through each character instead.
We can easily skip matching the rest of the word and seek to the next word if it encounters a mismatch, this is currently only used when encountering extra colon on the emote (emote:override:modifier:unrelated) but this can be easily expanded.

Will rebase later once this is properly tested.

Going to close this since emotes are no longer part of the core


Password protect hidden item visibility

I think the "hide folder" functionality is pretty useful. The only downside is that just in case if someone finds a way into the settings one could easily unhide hidden folders. It would be nice to password protect removing hidden directories from the settings.
I don't think there's a need to implement a full fledged encryption method into the app since there are already other apps for encrypting files. A simple solution like provided by the app "simple gallery" (which password protects hidden item visibility) would be sufficient in my opinion.
Thx for a great gallery app!

Hiding folders (or other filters) is not meant for secrecy. It is useful to users who do not want to see in the gallery some media that should stay visible to the rest of the system (e.g. album covers in their music collection).
What you want is a vault / secure folder / locked folder. You can upvote #114 with a thumb-up reaction, or subscribe to it.
I'll close this as duplicate.


Features: add detailed annotations on diagrams where applicable

Where necessary, explain clearly:

the state before the command
where should reader be looking at
the result of the command
clarification of any UI element that is not straight-forward

e.g. this one should annotate the result of the command, and explain the meaning of 1-star priority

Agreed. For style, can refer to examples in other DG parts like below to maintain consistency.

highlight the new phone added

2. explain priority UI meaning and how has it changed

3. before/after command

4. highlight where is changed, before/after

5. highlight sort status with reference to items in contact list, adapt the highlight on filter status to be consistent with style

6. highlight filter status with reference to items in contact list

7. highlight 2nd link of the 2nd contact and connect to the link in browser

8. same as 7


Rescuing Pawns Dumps Them on Top of Bed Instead of in Bed

Developer To Do Notes:

[ ]
[ ]
[ ]

Vanilla Bug Report
Describe the bug
❗❗❗ bug description here ❗❗❗
Rescuing pawns dumps them on top of the bed instead of placing them actually in the bed to begin recovery.
This might be only for stranger pawns. The one in the screenshot/save was a stranger pawn.
Steps to reproduce the behavior (VERY IMPORTANT)

Rescue Pawn

Error Logs ?
!!! You can copy paste an error here !!!

ReservationManager.Reserve cannot reserve. This is likely because reservation is no longer valid after CanReserve was called due to time delay with multiple threads.
UnityEngine.StackTraceUtility:ExtractStackTrace ()
Verse.Log:Warning (string)
RimThreaded.ReservationManager_Patch:Reserve (Verse.AI.ReservationManager,bool&,Verse.Pawn,Verse.AI.Job,Verse.LocalTargetInfo,int,int,Verse.ReservationLayerDef,bool)
(wrapper dynamic-method) Verse.AI.ReservationManager:Verse.AI.ReservationManager.Reserve_Patch1 (Verse.AI.ReservationManager,Verse.Pawn,Verse.AI.Job,Verse.LocalTargetInfo,int,int,Verse.ReservationLayerDef,bool)
Verse.AI.ReservationUtility:Reserve (Verse.Pawn,Verse.LocalTargetInfo,Verse.AI.Job,int,int,Verse.ReservationLayerDef,bool)
RimWorld.JobDriver_LayDown:TryMakePreToilReservations (bool)
RimThreaded.Pawn_JobTracker_Patch:StartJob (Verse.AI.Pawn_JobTracker,Verse.AI.Job,Verse.AI.JobCondition,Verse.AI.ThinkNode,bool,bool,Verse.ThinkTreeDef,System.Nullable1<Verse.AI.JobTag>,bool,bool) (wrapper dynamic-method) Verse.AI.Pawn_JobTracker:Verse.AI.Pawn_JobTracker.StartJob_Patch1 (Verse.AI.Pawn_JobTracker,Verse.AI.Job,Verse.AI.JobCondition,Verse.AI.ThinkNode,bool,bool,Verse.ThinkTreeDef,System.Nullable1<Verse.AI.JobTag>,bool,bool)
Verse.AI.Pawn_JobTracker:Notify_TuckedIntoBed (RimWorld.Building_Bed)
RimWorld.Toils_Bed/<>c__DisplayClass4_0:b__0 ()
Verse.AI.JobDriver:TryActuallyStartNextToil ()
Verse.AI.JobDriver:ReadyForNextToil ()
Verse.AI.JobDriver:TryActuallyStartNextToil ()
Verse.AI.JobDriver:ReadyForNextToil ()
Verse.AI.JobDriver:TryActuallyStartNextToil ()
Verse.AI.JobDriver:ReadyForNextToil ()
Verse.AI.JobDriver:Notify_PatherArrived ()
Verse.AI.Pawn_PathFollower:PatherArrived ()
Verse.AI.Pawn_PathFollower:TryEnterNextPathCell ()
Verse.AI.Pawn_PathFollower:PatherTick ()
Verse.Pawn:Tick ()
RimThreaded.TickList_Patch:NormalThingTick ()
RimThreaded.RimThreaded:ExecuteTicks ()
RimThreaded.RimThreaded:ProcessTicks (RimThreaded.RimThreaded/ThreadInfo)
RimThreaded.RimThreaded:InitializeThread (object)
System.Threading.ThreadHelper:ThreadStart_Context (object)
System.Threading.ExecutionContext:RunInternal (System.Threading.ExecutionContext,System.Threading.ContextCallback,object,bool)
System.Threading.ExecutionContext:Run (System.Threading.ExecutionContext,System.Threading.ContextCallback,object,bool)
System.Threading.ExecutionContext:Run (System.Threading.ExecutionContext,System.Threading.ContextCallback,object)
System.Threading.ThreadHelper:ThreadStart (object)
TryMakePreToilReservations() returned false for a non-queued job right after StartJob(). This should have been checked before. curJob=LayDown (Job_92155) A=Thing_SleepingSpot37483
UnityEngine.StackTraceUtility:ExtractStackTrace ()
Verse.Log:Warning (string)
RimThreaded.Pawn_JobTracker_Patch:StartJob (Verse.AI.Pawn_JobTracker,Verse.AI.Job,Verse.AI.JobCondition,Verse.AI.ThinkNode,bool,bool,Verse.ThinkTreeDef,System.Nullable1<Verse.AI.JobTag>,bool,bool) (wrapper dynamic-method) Verse.AI.Pawn_JobTracker:Verse.AI.Pawn_JobTracker.StartJob_Patch1 (Verse.AI.Pawn_JobTracker,Verse.AI.Job,Verse.AI.JobCondition,Verse.AI.ThinkNode,bool,bool,Verse.ThinkTreeDef,System.Nullable1<Verse.AI.JobTag>,bool,bool)
Verse.AI.Pawn_JobTracker:Notify_TuckedIntoBed (RimWorld.Building_Bed)
RimWorld.Toils_Bed/<>c__DisplayClass4_0:b__0 ()
Verse.AI.JobDriver:TryActuallyStartNextToil ()
Verse.AI.JobDriver:ReadyForNextToil ()
Verse.AI.JobDriver:TryActuallyStartNextToil ()
Verse.AI.JobDriver:ReadyForNextToil ()
Verse.AI.JobDriver:TryActuallyStartNextToil ()
Verse.AI.JobDriver:ReadyForNextToil ()
Verse.AI.JobDriver:Notify_PatherArrived ()
Verse.AI.Pawn_PathFollower:PatherArrived ()
Verse.AI.Pawn_PathFollower:TryEnterNextPathCell ()
Verse.AI.Pawn_PathFollower:PatherTick ()
Verse.Pawn:Tick ()
RimThreaded.TickList_Patch:NormalThingTick ()
RimThreaded.RimThreaded:ExecuteTicks ()
RimThreaded.RimThreaded:ProcessTicks (RimThreaded.RimThreaded/ThreadInfo)
RimThreaded.RimThreaded:InitializeThread (object)
System.Threading.ThreadHelper:ThreadStart_Context (object)
System.Threading.ExecutionContext:RunInternal (System.Threading.ExecutionContext,System.Threading.ContextCallback,object,bool)
System.Threading.ExecutionContext:Run (System.Threading.ExecutionContext,System.Threading.ContextCallback,object,bool)
System.Threading.ExecutionContext:Run (System.Threading.ExecutionContext,System.Threading.ContextCallback,object)
System.Threading.ThreadHelper:ThreadStart (object)
HugsLib log
❗❗❗ Link to HugsLib log. (MUST BE LINK) ❗❗❗
Player.log (Optional)
❗❗❗ Link to contents of Player.log or Error.log (MUST BE LINK) ❗❗❗
Player.log
Save file ?
❗❗❗ Please add a save file where the issue occurs to speed up testing and fixing of the issue ❗❗❗
Quaunler.zip
Screenshots (Optional) ?
❗❗❗ Add screenshots to help explain your problem here ❗❗❗

Mod list (For vanilla report, it has to be same as below list.) ?
[Mod list length: 6]
Harmony [https://steamcommunity.com/sharedfiles/filedetails/?id=2009463077]
Core [https:// no link (local mod)]
Royalty [Official DLC] [https:// no link (local mod)]
Ideology [Official DLC] [https:// no link (local mod)]
RimThreaded [https://steamcommunity.com/sharedfiles/filedetails/?id=2222907981]

Harmony
Core
Royalty (Optional)
Ideology (Optional)
RimThreaded

As an aside, this save also has the job reservation idling bug if that helps diagnosing the other issue.

Thank you for the submission. I am loading the save, but the rescue seems to work now. I will dig in further. I have witnessed this bug myself as well, so I curious about this as well.

It's somewhat inconsistent. When bringing in the pawn from outside they would just dump them on top of the bed. If they are already on top of the bed the next time they are rescued there is a good chance that the downed pawn will actually be put inside the bed. However this is also not always the case. Sometimes I have to rescue them 2-3 times.


Confusing error message if list of file paths parameter provided to ImportRequest is of type

🔍 Before submitting the issue

[x] I have searched among the existing issues
[x] I am using a Python virtual environment

🐞 Description of the bug
Providing a file path in form of pure  to any ‘files’ (data_files, combined_files, attachment_files) parameter in import request, results in error: “ValueError: File paths in import are not unique.“
Request object is expecting a list of strings, but when just a single str is provided, it carries on iterating through the parameter treating each 'char' as a separate path.
Should we add a simple ‘if not list’ check and throw more meaningful error msg in such case?
📝 Steps to reproduce
prepare ExcelImportJobRequest where one of files parameter is a 'str' instead of ['str']`
and create a job with it
import_request = jobqueue.ExcelImportJobRequest(name = "name",
                                                description = "description",
                                                template_file = ".\\myTemplate.xls",
                                                data_files = ".\\myDataFIle.xls")

import_job = api_client.create_job_and_wait(job_request=import_request)

💻 Which operating system are you using?
Windows
📀 Which ANSYS version are you using?
ansys-grantami-jobqueue          1.1.0rc0
ansys-grantami-serverapi-openapi 4.0.0
ansys-openapi-common             2.2.0
GRANTA_MIScriptingToolkit        4.1.75
MI b. 25.1.1888
🐍 Which Python version are you using?
3.13
📦 Installed packages
ansys-grantami-jobqueue==1.1.0rc0
ansys-grantami-recordlists==1.3.0rc0
ansys-grantami-serverapi-openapi==4.0.0
ansys-openapi-common==2.2.0
certifi==2024.8.30
cffi==1.17.1
charset-normalizer==3.4.0
cryptography==43.0.3
filetype==1.2.0
GRANTA_MIScriptingToolkit @ file:///C:/Automation/STK/scripting-toolkit-4-1-75/pip/granta_miscriptingtoolkit-4.1.75-cp38-abi3-win_amd64.whl#sha256=7be8c6e46f63c29c0fde2a30911b2c3a607c5fb6443258b56e77339ca4db58b0
idna==3.10
jaraco.classes==3.4.0
jaraco.context==6.0.1
jaraco.functools==4.1.0
keyring==25.5.0
more-itertools==10.5.0
packaging==24.2
pycparser==2.22
pyparsing==3.2.0
pypiwin32==223
pyspnego==0.11.2
python-dateutil==2.9.0.post0
pywin32==308
pywin32-ctypes==0.2.3
requests==2.32.3
requests-negotiate-sspi==0.5.2
requests_ntlm==1.3.0
six==1.16.0
sspilib==0.2.0
urllib3==2.2.3

I'd normally say that we shouldn't add this. The package is type hinted, which means a modern IDE will warn that you've done something wrong, and mypy will also throw an error if you provide a string when it expects a list. Also, the argument name is plural, which gives another very strong hint that some kind of container is expected.
This is a bit of a weird case in Python though, since strings and lists are both sequences, which can cause unexpected errors in cases like this. And since we don't actually try to resolve the file before raising the error, the error message is not obvious what's going on.
Should be fine to add this in.


Filter/info pane doesn't persist across app closes

Issue:
If I tap on the filter or the info pane, it should persist across app loads

Repro Steps:

Set the filter on, or the info pane on
Close the app, reopen
App shows all versions again

This was working previously.

Okay this is weird, and feels like a bug with SceneStorage on macOS.
I have a minimal sample project to test this out, which matches what I see with Xcodes. If I stop the app with Xcode, or force quit or killall, the next launch will restore the SceneStorage state. If I quit the app normally (⌘-Q) and then re-run it with Xcode, it won't restore the state. This also happens when not running from Xcode, like with an archived build. Quit the app  and the next launch won't restore state.
What I'd expect to happen is for SceneStorage state to be restored in all of these situations.

If the Scene is explictly destroyed (e.g. the switcher snapshot is destroyed on iPadOS or the window is closed on macOS), the data is also destroyed.

https://developer.apple.com/documentation/swiftui/scenestorage#
I wonder if it's not distinguishing between "window closed because window was closed by user" and "window closed because app was terminated by user"?
The behaviour also seems similar to this quote, which is for UIKit state restoration:

When debugging the sample project, the system automatically deletes its preserved state when the user force quits the app. Deleting the preserved state information is a safety precaution. In addition, the system also deletes the preserved state if this app crashes at launch time. To test the sample app’s ability to restore the sample’s state, do not use the app switcher to force quit it during debugging. Instead, use Xcode to stop the app, or stop the app programmatically. One technique is to suspend the sample app using the Home button, and then stop the debugger in Xcode. Launch the sample app again using Xcode, and UIKit initiates the state restoration process.

https://developer.apple.com/documentation/uikit/uiviewcontroller/restoring_your_app_s_state

The easiest solution is probably to use AppStorage for now, with a comment explaining why. This should be scene-specific state, but having them all use the same state is not a big deal since multiple windows is not really a desired situation.

Okay this is weird, and feels like a bug with SceneStorage on macOS.
I have a minimal sample project to test this out, which matches what I see with Xcodes. If I stop the app with Xcode, or force quit or killall, the next launch will restore the SceneStorage state. If I quit the app normally (⌘-Q) and then re-run it with Xcode, it won't restore the state. This also happens when not running from Xcode, like with an archived build. Quit the app  and the next launch won't restore state.
What I'd expect to happen is for SceneStorage state to be restored in all of these situations.

If the Scene is explictly destroyed (e.g. the switcher snapshot is destroyed on iPadOS or the window is closed on macOS), the data is also destroyed.

https://developer.apple.com/documentation/swiftui/scenestorage#
I wonder if it's not distinguishing between "window closed because window was closed by user" and "window closed because app was terminated by user"?
The behaviour also seems similar to this quote, which is for UIKit state restoration:

When debugging the sample project, the system automatically deletes its preserved state when the user force quits the app. Deleting the preserved state information is a safety precaution. In addition, the system also deletes the preserved state if this app crashes at launch time. To test the sample app’s ability to restore the sample’s state, do not use the app switcher to force quit it during debugging. Instead, use Xcode to stop the app, or stop the app programmatically. One technique is to suspend the sample app using the Home button, and then stop the debugger in Xcode. Launch the sample app again using Xcode, and UIKit initiates the state restoration process.

https://developer.apple.com/documentation/uikit/uiviewcontroller/restoring_your_app_s_state

The easiest solution is probably to use AppStorage for now, with a comment explaining why. This should be scene-specific state, but having them all use the same state is not a big deal since multiple windows is not really a desired situation.

I've submitted feedback for this: FB8979533 "SceneStorage doesn't restore value after app is quit by user"

I've submitted feedback for this: FB8979533 "SceneStorage doesn't restore value after app is quit by user"


Stap to get wan

[Enter feedback here]

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

ID: 20faa6dc-59db-7b3e-d9ef-adc1f74718af
Version Independent ID: 99dcdfef-3ba7-5fb2-9f1f-4539345f8998
Content: Scenario: any-to-any - Azure Virtual WAN
Content Source: articles/virtual-wan/scenario-any-to-any.md
Service: virtual-wan
GitHub Login: @cherylmc
Microsoft Alias: cherylmc

#!/bin/bash
Place in /config/scripts/post-config.d/
GROUP=$1
IFACE=$2
STATE=$3
Call Ubiquiti's script to report to UniFi Controller
/config/scripts/wan-event-report.sh $1 $2 $3
Log execution
echo "$(date +'%h %e %T'): GROUP: $GROUP IFACE: $IFACE STATE: $STATE">>/tmp/wlb.log
if [[ "$STATE" == "failover" ]]
then
WRAPPER="/opt/vyatta/sbin/vyatta-cfg-cmd-wrapper"
$WRAPPER begin
$WRAPPER set interfaces ethernet $IFACE disable
$WRAPPER commit
$WRAPPER end
$WRAPPER begin
$WRAPPER delete interfaces ethernet $IFACE disable
$WRAPPER commit
$WRAPPER end
fi

#!/bin/bash
Place in /config/scripts/post-config.d/
GROUP=$1 IFACE=$2 STATE=$3
Call Ubiquiti's script to report to UniFi Controller
/config/scripts/wan-event-report.sh $1 $2 $3
Log execution
echo "$(date +'%h %e %T'): GROUP: $GROUP IFACE: $IFACE STATE: $STATE">>/tmp/wlb.log
if [[ "$STATE" == "failover" ]] then
WRAPPER="/opt/vyatta/sbin/vyatta-cfg-cmd-wrapper" $WRAPPER begin $WRAPPER set interfaces ethernet $IFACE disable $WRAPPER commit $WRAPPER end
$WRAPPER begin $WRAPPER delete interfaces ethernet $IFACE disable $WRAPPER commit $WRAPPER end
fi

Drop fix now ({})§£

@naz733
It looks like your issue is resolved since you closed this thread.
If there are further questions regarding this matter, please tag me in a comment. I will reopen it and we will gladly continue the discussion.


Previously watched video plays at 2x speed but displays 1x in UI

DESCRIPTION:
Previously watched video plays at 2x speed but displays 1x in UI.

REPRO STEPS:

Install and Launch LBRY 0.16.0 on Android 8.1.0
Begin watching a video
Change speed to 2x
Play video to the end
Tap the Back button
Click the same video you just watched
Click the play button

Results:  Video plays at 2x but UI says 1x
Expected: Playback speed is correctly listed in UI

ENVIRONMENT:

LG V20
Android 8.1.0
LBRY 0.16.0

MEDIA:

INTERNAL USE:

DEFINITION OF DONE:

[ ] Tested against acceptance criteria
[ ] Tested against the assumptions of the user story
[ ] The project builds without errors
[ ] Unit tests are written and passing
[ ] Tests on devices/browsers listed in the issue have passed
[ ] QA performed & issues resolved
[ ] Refactoring completed
[ ] Any configuration or build changes documented
[ ] Documentation updated
[ ] Peer Code Review performed

LBRY ADDRESS:
bZSqrVdpxt5KJdn2eGMUzT9Jn3gEiRet7b
<EMAIL_ADDRESS>

Thanks for filing the issues! Got your email and we'll get some appreciation over.

Fixed in https://github.com/lbryio/lbry-android/commit/c1106d71864f0c140417ae74607d7b80c00c5b18.


Further improvements to API handling in shell

This follows on from the brew --prefix API improvements to get rid of the shell out to Ruby and read a file that gets generated on the Ruby side during an API auto-update.
There's a few parts here:

The generated files are placed in HOMEBREW_CACHE_API/parsed.
They are only generated in Ruby, so we need brew update-report to try invoke that post-update.
brew update deletes the parsed files after an update to signal they should be regenerated. The Ruby auto-update signals back a boolean.
It regenerates only when necessary to avoid unnecessary file writes (which matters for sandboxed use).

I've also:

Updated brew casks to support the API (it previously only read local taps).
Added shell-side support for API aliases in brew --prefix (for #14663).
Added support for brew --cellar <formula>, using most of the existing brew --prefix <formula> implementation (also for #14663).

Copying across some benchmarks from #14622.
Worst case prior to #14622 (or prior to this PR for --cellar):
# Can be slower with poorer networks
$ hyperfine --warmup 3 "HOMEBREW_API_AUTO_UPDATE_SECS=0 brew --prefix hello"
Benchmark 1: HOMEBREW_API_AUTO_UPDATE_SECS=0 brew --prefix hello
  Time (mean ± σ):      2.416 s ±  0.162 s    [User: 1.542 s, System: 0.690 s]
  Range (min … max):    2.242 s …  2.844 s    10 runs

Best case before #14622 (or prior to this PR for --cellar):
$ hyperfine --warmup 3 "HOMEBREW_NO_AUTO_UPDATE=1 brew --prefix hello"
Benchmark 1: HOMEBREW_NO_AUTO_UPDATE=1 brew --prefix hello
  Time (mean ± σ):      1.831 s ±  0.083 s    [User: 1.259 s, System: 0.503 s]
  Range (min … max):    1.748 s …  2.011 s    10 runs

After #14622 but before this PR for --prefix:
$ hyperfine --warmup 3 "brew --prefix hello"
Benchmark 1: brew --prefix hello
  Time (mean ± σ):     787.8 ms ±  13.3 ms    [User: 665.9 ms, System: 106.0 ms]
  Range (min … max):   768.8 ms … 808.1 ms    10 runs

After this PR:
$ hyperfine --warmup 3 "brew --prefix hello"
Benchmark 1: brew --prefix hello
  Time (mean ± σ):      41.5 ms ±   7.9 ms    [User: 16.2 ms, System: 20.7 ms]
  Range (min … max):    28.5 ms …  58.0 ms    70 runs

Aliases:
$ hyperfine --warmup 3 "brew --prefix python"
Benchmark 1: brew --prefix python
  Time (mean ± σ):      64.7 ms ±   9.9 ms    [User: 26.8 ms, System: 32.3 ms]
  Range (min … max):    42.7 ms …  84.6 ms    50 runs

Review period will end on 2023-02-17 at 22:49:03 UTC.

Refactored the Ruby side a bit.

Review period ended.


Upgrade UBI version to 9.4-1181

Motivation
Jira :
https://issues.redhat.com/browse/RHOAIENG-10270
https://issues.redhat.com/browse/RHOAIENG-10001
IBM has requested for new build of text-generation-inference from RHOAI-2.8 branch to incorporate vulnerability fix came with latest UBI image. Current latest available release of UBI 9 image is 9.4-1181. I had raised this PR to upgrade UBI 9 image version from 9.3-1552 to 9.4-1181
[Describe why this change is needed]
Modifications
[Describe the code changes]
Result
[Describe how the changes affects existing behavior and how to test it]
Related Issues
[Resolves #123]

/test images

/retest


watching at a compacted revision doesn't gets canceled

Per etcd api document, watching at a compacted revision should get a response from etcd server that this watch has been canceled. However, this cpp api is not honoring that and will continue to watch for responses, and will get stuck in case of a synchronous call. The problem occur at two code places.

etcdv3::AsyncWatchAction::waitForResponse(), for the "watch" method of etcd::Client. When watching at a compacted revision, it will get a response with latest revision in header (which is greater than parameters.revision), empty events, and "canceled" field set to true. This will fall to the else case of line 86, and gets stuck there because etcd server will not send any further response.

Expected behavior: it should check for reply.canceled() before line 66 , and cancel the watch if it is set to true.
64     if(got_tag == (void*)this) // read tag
65     {
66       if ((reply.created() && reply.header().revision() < parameters.revision) ||
67           reply.events_size() > 0) {
68         // we stop watch under two conditions:
69         //
70         // 1. watch for a future revision, return immediately with empty events set
71         // 2. receive any effective events.
72         isCancelled = true;
73         stream->WritesDone((void*)"writes done");
74         grpc::Status status;
75         stream->Finish(&status, (void )this);
76         cq_.Shutdown();
77
78         // leave a warning if the response is too large and been fragmented
79         if (reply.fragment()) {
80           std::cerr << "WARN: The response hasn't been fully received and parsed" << std::endl;
81         }
82       }
83       else
84       {
85         // otherwise, start next round read-reply
86         stream->Read(&reply, (void)this);
87       }-
88     }

etcdv3::AsyncWatchAction::waitForResponse(std::function<void(etcd::Response)> callback), for the watcher class. Watching at a compacted revision will return a response with no events. Thus, similar to above case, it will not handle this response properly, and will keep trying to read from stream.

Expected behavior: it should check for reply.canceled() before line 128 , and cancel the watch if it is set to true. Additionally, the watcher class needs a way to know if it has been canceled by the server.  Consider adding following method to the watcher class:
bool etcd::Watcher::Canceled()
{
return call->Cancelled();
}
Also, the Cancelled() method needs to grab lock before accessing isCancelled:
bool etcdv3::AsyncWatchAction::Cancelled() const {

std::lock_guardstd::mutex scope_lock(this->protect_is_cancalled);
return isCancelled;
}

126     else if(got_tag == (void*)this) // read tag
127     {
128       if(reply.events_size())
129       {
130         // for the callback case, we don't stop immediately if watching for a future revison,
131         // we wait until there are some expected events.
132         auto resp = ParseResponse();
133         auto duration = std::chrono::duration_caststd::chrono::microseconds(
134             std::chrono::high_resolution_clock::now() - start_timepoint);
135         callback(etcd::Response(resp, duration));-
136         start_timepoint = std::chrono::high_resolution_clock::now();
137       }
138       stream->Read(&reply, (void*)this);
139     }

Thanks for letting me know such feature. I will invistage that tomorrow.

Fixed. Thanks for noticing such cases.


Finalize how to load byob extensions

Need to finalize how to load extensions into Runtime.
Currently, it's via an appsetting that points to a directory, and we can scan the dir for files with "extension" in the name.

This should include supporting direct nuget  references. ( https://github.com/Azure/azure-webjobs-sdk-script/issues/1398  ) , but may need additional means for direct dlls.
Ensure this works with our VS tooling.

Suggest using the folder name bindings or even bin\bindings. As a stopgap, we could simply have the VS tooling copy the binaries to that folder if they are a custom binding.

Would really recommend taking the NuGet package approach only. This would give us a lot of flexibility when dealing with the assembly resolution issues we currently have with the temporary implementation,  using the same mechanism as our NuGet resolution process, which allows for very controlled loading behavior based on the dependencies manifest (lock/deps). There are other benefits as well, mostly related to the load context used by the runtime.
This still enables file based deployment (without requiring publishing), but would just mean that what gets deployed is a package, as opposed to loose files. This also gives us consistent loading behavior between package referenced (e.g. from NuGet) and file based deployed binding extensions.

@fabiocav That makes a lot of sense. In my spec, I wrote that the CLI should do NuGet restore itself, but it sounds like you're recommending that we simply put all the functionality in Script Host. Is that accurate?

Yes. Need to flush out the actual details, the runtime doesn't have to be the one actually restoring things (it could) but it would use the restore artifacts to load the extensions.

Are there docs that describe how this works today, and any logging/debug hooks that might be useful?
I'm asking as I'm finding the current docs, such as the samples by @lindydonna, don't work for me on MacOS, with JS based Function apps running locally using func host start, so it would be great to double check against the docs and contribute any feedback once I've spotted the issue.


Anti Virus software picking Umami.js as Virus

Hello,
My antivirus just blocked my umami website because they found threat on umami,js file. See screenshot.
What could be the reason? I added the code for two websites of mine so far.

It sounds like Umami has been added to a deny list somewhere, presumably to disable analytics.
I'm not sure why Avast would pick that list up though.
It might be worth getting in touch with Avast directly and finding the source list.

I have asked them to remove from blacklist. Let's see their reply.

@surjithctly Just following up, did you get a response from them?

Hello,
yes. I received the message. Sorry! Forgot to update here.

Hello,
Thank you for reporting this false positive.
Our virus specialists have now cleared its reputation in our database.
With URLs this change should be instant, but it might take up to 24 hours with files.
For future reference you might also find the following article to be useful: Avast Clean Guidelines.
Best regards,
Avast Customer Care

Its started working again.


cocoMDS1 not started in docker-compose notebook environment

In the docker compose 'lab' notebook environment we create 3 egeria server platforms

egeriacore
egeriadl
egeriadev

In the notebooks

metadata-server-config uses egeria core to perform all configuration tasks (including of cocoMDS1)
managing-servers points to egeriadl to start cocoMDS1

This fails with a 404, and a debug exception reporting that the config file is not found.
This is because in the docker-compose / k8s case each platform has it's own private filesystem
If all three platforms are run locally they share the local filesystem, and so all platforms can see all the configuration files....
Suggested fixes
a) As a tactical issue update the docker-compose environment to utilize a shared filesystem for configuration
b) Investigate best approaches to share config in k8s case (filesystem, maps) & consider how updates to systems are managed across the lifecycle -- not just for a tutorial (++ devops)

Nigel and I talked about this today and we have a cunning plan.  The OMAG Server Platform supports a POST method called:
/open-metadata/admin-services/users/{userId}/servers/{serverName}/configuration

that takes a configuration document in the request body.  It stores the supplied configuration for the requested server.
I could add another REST API endpoint to the platform to POST a configuration document from one OMAG Server Platform to another.  Under the covers it would call the store configuration endpoint shown above on the destination platform.
This new REST API endpoint would be a POST with the following URL:
/open-metadata/admin-services/users/{userId}/servers/{serverName}/configuration/deploy

It would have a request body containing the destination OMAG Server Platform's root url.
This could be null in which case the serverURLRoot property from the server's configuration document is used.
When this new endpoint is called, the receiving OMAG Server Platform reads the configuration document for the requested server, determines the destination OMAG Server Platform and calls it to store the config document.  The same userId is used on the request to store the configuration.
This enhancement means an organization can manage configuration documents as a proper software artifact.  For example they could have an administration platform in their dev environment.  Configuration documents can be prepared and tested.  Once they are approved they can be checked into a document or config management repository, retrieved in a devOps pipeline and pushed to the production platform.   Maintenance changes the configuration document can also be pushed to the production platform in a single command.

Just seen the changes. The new section on distrubuting the config looks super. docker-compose loads the latest notebooks (it pulls from git on creation), but I need to rebuild the base image of egeria for the new services. I'll build my own images, but for others, In fact the build process will do this during the day. I'll then verify the compose images and raise any issues found.

This is now fixed thanks.


DROOLS-1236 JMX objectnaming separation for Stateful Vs Stateless

(and for alignment with RHQ/JON plug-in).

+1 to merge


Forking url for foundry

Hey guys,
Currently foundry uses the public mainnet RPC for forking, which can be problematic, see https://github.com/scaffold-eth/scaffold-eth-2/pull/955#discussion_r1794469370.
Hardhat already uses the FORKING_URL environment variable.
Note:
I might have had to send this PR to https://github.com/scaffold-eth/scaffold-eth-2/tree/foundry, but this branch seems to be older than this repo (still uses alchemy API key).
Cheers,
Tamas

I might have had to send this PR to https://github.com/scaffold-eth/scaffold-eth-2/tree/foundry, but this branch seems to be older than this repo (still uses alchemy API key).

Ohh yeah, @moltam89 do you want to update that branch with alchemy key changes and also add this changes to that PR? Ideally we are trying to keep that branch and this sync for now 🙌

Yeah, I'll look into this (probably next week) and try to apply the changes from here to the scaffold-eth-2/foundry branch.

Thanks Tam! I just updated the SE-2 foundry branch with (alchemy stuff) but can make this PR changes to SE-2 foundry

Thanks @technophile-04 !
Here is the SE2 version of this:https://github.com/scaffold-eth/scaffold-eth-2/pull/974

Closing this, ref https://github.com/scaffold-eth/scaffold-eth-2/pull/974#issuecomment-2490826429


Fix sort_target parameter off-by-one.

Fixes #18

Codecov Report

Merging #19 into master will not change coverage.
The diff coverage is 100%.

@@           Coverage Diff           @@
##           master      #19   +/-   ##
=======================================
  Coverage   89.03%   89.03%
=======================================
  Files           7        7
  Lines         310      310
  Branches       30       30
=======================================
  Hits          276      276
  Misses         22       22
  Partials       12       12

Impacted Files
Coverage Δ

etcd3gw/client.py
88.59% <100%> (ø)
:arrow_up:

Continue to review full report at Codecov.

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

Very cool. thanks @fasaxc


Detect last iteration of a loop

What version of Swift are you using (swift --version)?

Apple Swift version 3.0.2 (swiftlang-800.0.63 clang-8<IP_ADDRESS>)
Target: x86_64-apple-macosx10.9

What did you do?

    init(_ persisted: {{ type.name }}) {
        self.init(
{% for var in type.variables %}
            {{ var.name }}: persisted.{{ var.name }} {% if not last %},{% endif %}
{% endfor %}
        )
    }

What did you expect to see?

I expect to generate a call to the default initialiser of the struct with each parameter separated by a comma but without adding the comma to the last parameter, because Swift doesn't like to have that comma.
self.init(
            title: persisted.title,
            associatedUrl: persisted.associatedUrl
        )

What did you see instead?

self.init(
            title: persisted.title,
            associatedUrl: persisted.associatedUrl,
        )

The variable last, first, counter (from Stencil) doesn't seem to be present inside the for loops.
Maybe I'm doing something wrong with the template or maybe there is a different way of accomplishing the same?
Any help would be appreciated, thanks!

try if forloop.last

Nice!
I was looking for some namespace but didn't find it, sorry.
Thank you Krzysztof! 🙏


Bug: Refresh button on Home page doesn't work at all

Description
When you navigate to Home and try to refresh the page for the page to be up-to-date it just doesn't work at all.
Steps To Reproduce

Open Files
Go to Home
Click Refresh button

Requirements

Make the refresh button on Home page work

Files Version
3.7.0
Windows Version
10.22000.0
Log File
Doesn't help. Just missing this ability in Files.

I filed this issue so others can look into as this should be easy one.
Also basically works as a workaround for #15410 instead of turning off the option to run the app on the background.

Same as #6182?

I think that issue is for auto refresh when something was changed. Will we merge?

First part listed in it is to make the refresh button work

Ah I see, but we will have to update the different part for each.
I'll leave you to decide to close and merge this:)

Lets merge


Moving Target

Is it possible to assign a tag on moving object? For example - if a friend and I are in a large crowded park then I can see his accurate location at all times as long as he has the "FIND ME" type feature turned on?
Kinda like this:
https://mobile-ar.reality.news/news/apple-ar-quickly-find-your-friends-crowded-places-with-neon-app-0179493/
I have done this before in ARCore in Android but I am not sure if its possible with this repo in ARKit
Any feedback will be appreciated.
Thank you

Yes, of course you can build this type of experience.  It's not a built in feature of the library, but you could certainly use this library to build an app that does that.


Proposing adding MFA method of sign-in

related https://github.com/MicrosoftDocs/office-docs-powershell/issues/6997

@JohanFreelancer9 Copy editing is needed for this PR. Thanks.

@brandber PR has been copyedited and is ready for final review, could you please check and merge? Thanks!

Can this be merged?

Can this be merged?


Perf tests for new reference tracking cache

.NET5 has implemented a new reference tracking cache for use by WinUI. Need to test scenarios for Scrolling and page navigation

This is being tracked by the WinUI team.


Feature Request - Standardize AuthType

I think it would be beneficial to add the '-AuthType' option to all scripts in a standardized way.   The way it is done in the Account Onboarding scripts seems perfect.
It would be ideal if 'CyberArk' were the default for all scripts, but with the option to pass other -AuthType options.
Example:  I am doing some testing with the Safe Management scripts in a development environment and it doesn't allow Radius auth type, which is needed.

Hello @tarheeljeff ,
Thanks for proposing this enhancement request, I will shortly update it for the scripts that were missing it.
Specifically for the Safe Management script is using the 1st generation logon API I have updated the README file to include a tip on how to authenticate also using LDAP in addition to CyberArk without even changing the script :)
Let me know what you think
Regards,
Assaf


[GNMT] Changed reference model to use single input

This change allows the usage of a single input file for both accuracy and performance modes. @christ1ne , could you please take a look and see if you agree?
(This is a follow-up on https://github.com/mlperf/inference_policies/issues/64)
Before we selected a different input, depending on whether we run in
accuracy or perf mode. With this change we can use the same file,
as long as we limit the number of unique samples.

This change looks fine for me. However, I think we can leave this PR for people to pick up in case they want to use it for their GNMT submission. We already code freezed.

closing this as GNMT is no longer in the MLPerf inference suite


Fix modify throwing exception, when user enters empty input

Coverage increased (+0.007%) to 94.428% when pulling faff7c5ad6e88c698fef4fefcaeb1d2730f4bb22 on ajgon:fix-modify-for-empty-input into 314e1a1a79601a712f3afa46794c9daa72ede2f5 on piotrmurach:master.

This is a mega PR! Happy to see the extra tests. Thanks :heart:


Cosmos: Add API to configure the container…

…  that a hierarchy is mapped to, as well as the default container name
Enable materializing derived types polymorphically
Add exceptions for some unsupported cases

@divega to review the exception messages