Feature Request: API support for autocomplete "preselection"

The Visual Studio for Windows text editor's completion API has a feature that allows languages that implement completion to set the item that is selected when the completion list first comes up. The C# language service in VS has used this to build various experiences that they call "preselection": namely, the completion list comes up when the user types SPACE and a useful item is already selected. The canonical example of this is preselecting items after new in C#. List<string> is not normally present in the completion list, but gets specifically added preselected after the new keyword when the type of the expected expression is List<string> (or whatever).

It would be nice if VS Code could add a similar feature (perhaps by adding a "Preselect" bit to to the CompletionItem class). If this API were available, we would definitely consume it from omnisharp-vscode.

If this is something the team is interested in taking, I'm also happy to contribute this work--let me know.

cc @jrieken

It's not that simple with the VS Code model and that's because multiple extensions can provide extensions and the UI merges then. That model makes all "absolute" behaviour hard to get right because a provider only has a local view a global view is needed to pick the one preselected item.
Still, you can achieve this by utilising the 'sortText'-property. The VSCode UI always sorts the completion list by "rank" (in contrast to VS which selects the best match). These "ranks" are computed by looking at the text left of the cursor or, when there is no text, by using the 'sortText'-property

@jrieken: Doesn't using sortText just end up re-sorting the list?

@jrieken: Doesn't using sortText just end up re-sorting the list?

Only once when all completions are brought together. We will then show completions in that order but as soon as the user type (with the completion window open) we constantly resort item on "how well they match".

@jrieken If I use sortText, won't I be forcing the item I want to select to the top of the list (eg, not sorted alphabetically)?

a provider only has a local view of the world while a global view is needed to pick the one preselected item
We have code that handles this in Roslyn :). The main trick is making sure that preselection does not override matching based on what the user typed.

@jrieken If I use sortText, won't I be forcing the item I want to select to the top of the list (eg, not sorted alphabetically)?

Yes

@jrieken Roslyn has a model where there are multiple "providers" that can provide completions at a given location in a C#/VB file. Each provider can mark its own items for preselection if it wants, and the engine that aggregates all of the results chooses the best item across all providers.
I think this is basically what VSCode does, except "providers" in VSCode are extensions that have registered completion support for a given language.
I'm requesting that the VS Code API add a property onto completion items that says "I"m such a good item, that if the user hasn't typed anything, you should say that I'm the best match". This is a presentation mode that C# users depend on, so it would be nice we could provide it from Omnisharp-vscode.

I just want to mention that this is really important to people coming from VS like myself, that expect small but relevant time savers like the one described in the op, to be present and on feature parity before moving into VSCode.

For reference, Roslyn MatchPriority.
For us that could translate into something similar, e.g. CompletionItem#preselect: number with similar semantics.

The internal implementation for this is ready. It will select the first preselected item of the group of best ranked items unless there is MRU information. Next step is exposing this in the extension API
export class CompletionItem {
  preselect?: boolean
}

@jrieken Awesome! Any idea when the extension API will support this?

@rchande The last commit two commits linked above look like they're adding it to the extension API (vscode.d.ts) and TypeScript impl :-)

@rchande In tomorrows insiders and with the June release in 3 weeks

@jrieken Cool, thanks!
@DanTup Reading? What's that 😄

Also @jrieken, when should we update the vscode npm package (https://www.npmjs.com/package/vscode/v/1.1.18) to get updated with the latest vscode.d.ts?

It will need the stable release to work. Then simply set the engine version in your package.json file and run npm install. To test against insiders, you can simply copy the vscode.d.ts from our repo or temporary set the engine property to *

Language server protocol needs to be updated as well. Currently it does not seem to copy the field over from external LS to the TS side of things.


Units have the same dialog as a settler in the orders menu

build a city, build irrigation, change to forest, ...

as #89

Indeed, duplicate of #89


When using OnInstallPerCompany you might also want add code to CompanyInitialize subcription (info)

Title
When using OnInstallPerCompany you might also want add code to CompanyInitialize subcription (info).
Description
When using OnInstallPerCompany you might also want add code to CompanyInitialize subcription (info).
Reason for the rule
OnInstallPerCompany do only get called for existing companies at the point of installing the extension. If you have general extension setup code you should place it in CompanyInitialize event.
Bad code sample
codeunit 50000 "MyEXT - Initialize"
{
    Subtype = Install;

    trigger OnInstallAppPerCompany()
    var
        AppInfo: ModuleInfo;
    begin
        NavApp.GetCurrentModuleInfo(AppInfo);
        if AppInfo.DataVersion() = Version.Create('<IP_ADDRESS>') then
            CODEUNIT.Run(CODEUNIT::"MyEXT-Upgrade");

        SetupCompany();
    end;

    local procedure SetupCompany()
    begin
        CreateElectronicProfiles();
        CreateDocumentSendingProfile();
        CreateProfileCode();
    end;
    ...

Good code sample
codeunit 50000 "MyEXT - Initialize"
{
    Subtype = Install;

    trigger OnInstallAppPerCompany()
    var
        AppInfo: ModuleInfo;
    begin
        NavApp.GetCurrentModuleInfo(AppInfo);
        if AppInfo.DataVersion() = Version.Create('<IP_ADDRESS>') then
            CODEUNIT.Run(CODEUNIT::"MyEXT-UpgradeCompany");

        SetupCompany();
    end;

    local procedure SetupCompany()
    begin
        CreateElectronicProfiles();
        CreateDocumentSendingProfile();
        CreateProfileCode();
    end;

    [EventSubscriber(ObjectType::Codeunit, Codeunit::"Company-Initialize", 'OnCompanyInitialize', '', false, false)]
    local procedure CompanyInitialize()
    begin
        SetupCompany();
    end;
    ...

Good and bad practices for fixing the rule
Make sure to call the extensions company setup code from OnInstallPerCompany and CompanyInitialize.
Remarks

Thank you for reporting this issue. Unfortunately, we do not find it important enough to address at this point.
We’re planning to give the CodeCop engine and its rules an overhaul in a future major release.


Skip expired cookies

Changes

skip expired cookies when sending requests

Comments
Closes #68, by skipping expired cookies when sending requests instead of removing them from the jar, so that they can be asserted.

Hey @lasantosr , thank you very much for raising the issue and making a PR so quickly.
The issue was that the server is that when a request responds with an expired cookie, it will then be sent in a following request. If I understand your PR correctly, your fix is to check the cookie expiration on send. I think it would be better to instead check on save, or when the cookie is added to the TestServer.
My reasoning is that I think having the state store cookies, that we need to be aware should be ignored, is not healthy. It would be better to only store cookies that we are sending IMO.
How would that sound as an alternative solution?

Hey @JosephLenton, that was my first approach indeed. Not only not saving it but also removing it.
For example if I make a "login" request to the server, it responds with the valid cookie, then I make a "logout" request to the server and it responds with the expired cookie, so the cookie must be removed and the next request must not send it.
But then I thought that I want to assert after a request is made to the server, with maybe_cookie(), that the server did respond a cookie with an expired value in order to unset it. I could still use the headers I guess, but it's easier to check the already-parsed cookie.
Let me know if this approach fits for you, and if not I could change the PR to avoid storing expired cookies and remove them if present.

Thank you very much for the PR btw!


Get dwarf from Numba assembly

This works for cpu (@njit),
For kernels, you need to use a different method, in this information does not get into the dwarf
We need to set numba environment variable and run script and get info
NUMBA_DUMP_ASSEMBLY=1 python njit-basic.py > njit-basic-asm.txt

Clear file from prints and unrecognized characters (-, =, !, )
Get compiled from asm
as -o o njit-basic-asm.txt

Get dwarf with objdump
objdump -W o > o_dwarf

@1e-to
Is it in documentation already?

@PokhodenkoSA yes. It is in documentation. PR 458 added it.
Docs link


Release 0.1.0

Once the automated release process PR is in, we can update the CHANGELOG to say "- Initial release" under "Added" and then do a 0.1.0 release

Released!


Markdown is not recognized in the html type fields

I copied and pasted the attached document in the about/body field and I got a text rendering only.
I also tried to drag and drop a *.md file in the editor and the title of the file got input, not its content nor its fully qualified pathway.
NodeBB+Docker.md.zip

@asitemade4u Just to clarify, is the issue:

You enabled Markdown in your about field (e.g. {{about type=html editor=markdown}}), and it didn't work.
You used the standard HTML tag (e.g. {{about type=html}}), and expected Markdown to render when inputted into the WYSIWYG.

Re: drag n' drop, it's not enabled for the editors currently, but that sounds like a useful feature.

@asitemade4u I wanted to check in, and see if you were able to sort this out. If not, let me know the answer to the question above, and/or share your template HTML.


modal disappear completely after the first show

Hi
I have problem with the modal
everything is fine but the problem is when i click on the button to open the modal its work 100%
if i close it
my model will gone completely and i will not be able to open it again
I have opened the inspect element but there was nothing related to modal ( removed )
any idea ? ?
I'm calling the show method from my angular file
 $scope.StdModel = function () {
         $(".std>.ui.modal").modal("show");
    };

there is no error

Ihave found the problem but i dont know the resone of it
when i'm using
.std>.ui.modal
its work for the first time but then it's not ( I dont know why)
i change it to .ui.modal.std and everything fine now

Hi @badrsh,
Thank you for posting, but although it’s a valid usage question, we’ve limited GitHub Issues to bug reports and feature requests, keeping the board more manageable for maintainers; see the contributing guidelines for more information on what kind of posts should find themselves into the GitHub Issues board.
To get answers or feedback that might allow you to repost this issue, please use one of our other support resources:

Gitter chatroom
Official forums
StackOverflow


Inventory cursor sometimes doesn't reappear after a dialogue is finished

This started happening after adding a new feature: dialogues. Right-click shows the cursor.

It seems to be fixed together with #327 .


The Subscribe method may only be called when a RenderlessSink device is attached

Describe the issue
Some times we get an exception like this:
$>2020-11-10T11:57:09.4653242Z Error: BotMediaStream.cs:297 Unsubscribe ScenarioId: d6491720-0d49-417c-b858-e2e237e0bea5 CallId: 891f0200-0c20-4e33-b876-e3b970228c7f TenantId: fe380fea-xxxx AppId: 8c8bd361-xxxx AppName: Sample.PolicyRecordingBot.FrontEnd Unsubscribing to video failed for the socket: 2 with exception exception: Subscription failure. The Subscribe method may only be called when a RenderlessSink device is attached. StackTrace:    at Microsoft.Rtc.MPService.Stream.Subscribe(MPSubscriptionMode subscriptionMode, VideoSubscriptionSize videoSize, UInt32 sourceID, Boolean subscriptionCompletedEventRequested, MPStreamDirection direction)    at Microsoft.Rtc.MPService.Context.Microsoft.Rtc.MPService.IInternalContext.Subscribe(MediaType mediaType, VideoSubscriptionSize videoSubscriptionSize, Int32 videoIndex, UInt32 msi)    at Microsoft.Rtc.MPService.MPMediaSession.Subscribe(MediaType mediaType, VideoSubscriptionSize videoSubscriptionSize, Int32 videoIndex, UInt32 msi)    at Microsoft.Skype.Bots.Media.Wrappers.MPMediaSessionWrapper.Subscribe(MediaType mediaType, VideoSize videoSize, UInt32 videoIndex, UInt32 msi)
Expected behavior
We are not sure why this error occurs and whether it can be ignored.
Call ID
see above
Logs
see above

The error can be ignored.
But if you are not on the most recent Microsoft.Skype.Bots.Media nuget package, please update - https://www.nuget.org/packages/Microsoft.Skype.Bots.Media/<IP_ADDRESS>-alpha. Thanks.

Thanks. I am on the version you mentioned.


Update GPU Operator

Thank you for making MicroK8s better
Please reference the issue this PR is fixing, or provide a description of the problem addressed.
Also verify you have:

[x] Read the contributions page.
[x] Submitted the CLA form, if you are a first time contributor.

fixes #303


Support running dashboards.sh from inside teslamate container

Describe the issue
I use the teslamate docker container along with watchtower in order to keep the container updated.  However, I do not use the teslamate grafana container (because I have other grafana dashboards as well).  So when watchtower fetches a new telsamate container, I would like to be able to use its update hook to run dashboards.sh.  However, watchtower can only run hooks within the context of the container it updates, so I need to be able to run dashbaords.sh from the teslamate container.  I'd rather not extend the teslamate container myself, since that will break watchtower's ability to detect updates.
The current issues:

dashboards.sh requires curl and jq which are not available in the image
the grafana subdir is not included in the teslamate container

Ideally I would like both of the above addressed, but even just adding curl and jq could make things much easier.
Today, to work around this, I mount a volume on /grafana/update with curl and jq and the following script as the watchtower update hook:
#!/bin/bash
URL=<grafana url>
LOGIN=<grafana login>
set -e
SCRIPT_DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" &> /dev/null && pwd )"
# add jq and curl to the path
export PATH=${PATH}:${SCRIPT_DIR}

release=$(/bin/ls -1 /opt/app/releases | grep -e '^\([0-9]*\.\)*[0-9]*[0-9]$')
rm -rf /tmp/teslamate-* /tmp/${release}
curl https://github.com/adriankumpf/teslamate/archive/refs/tags/v${release}.tar.gz | tar -C /tmp -xzf -
cd /tmp/teslamate-${release}
./grafana/dashboards.sh restore

For reference (although not relevant to the request) I use the following for a static curl/jq:

curl: https://github.com/moparisthebest/static-curl
jq: https://stedolan.github.io/jq/download/

As the above solution is working for me, feel free to close this request if you don't think it has enough broad appeal.  If you are interested and would prefer a pull-request, I'll be happy to file one.

I'm afraid this is a rather niche use case. Since you already have a working solution, I would not like to install dependencies just for this purpose.  On the one hand because of the image size, on the other hand so that people don't start to expect that those dependencies are present and thus preventing us to make changes to the image in the future.


Bug 501006: [Bug] Page "Word Template Creation Wizard" (9995) - missing variable update leads to an error #23867

Summary
The issue was reported here: https://github.com/microsoft/ALAppExtensions/issues/23867
In essence, if you ever got the error message that more than 250 fields were selected, you cannot get past it, as the number of fields never is recalculated. Now it is.
Work Item(s)
Fixes AB#501006

I actually don't fully understand why the current code isn't working, as the dictionary is supposed to be updated in the trigger. The new code works, but as should the old. I'll debug...


CI build, distribution, and badges

There is no Travis config, I assume the unit tests are not run automatically on pull requests. Can the Travis build be set up?
I don't know how PHP modules are usually distributed, is there some repository (like npm, pypi, Maven) where the module is packaged and distributed? Or do people always import it directly from GitHub?  If there is a repository, please document it in the README.
Please include badges in the README for the Travis build, latest release version of the module, and the repository (if available).

Done v2.0.9-beta


fixed openssl hash for uwp builds

This PR updates the source hash for uwp builds

Hi @stammen, I'm your friendly neighborhood Microsoft Pull Request Bot (You can call me MSBOT). Thanks for your contribution!

It looks like you're a Microsoft contributor (Dale Stammen). If you're full-time, we DON'T require a Contribution License Agreement. If you are a vendor, please DO sign the electronic Contribution License Agreement. It will take 2 minutes and there's no faxing! https://cla.microsoft.com.

TTYL, MSBOT;

Thanks!


Tag the released images in this repository

Its quite hard to go from a image, say, image2disk:v1.0.0 to its source code, as there are no tags in this repository nor a git revision in the artifacthub page.
Can these be included in the release process?

Discussed at triage:

We could add Github tags for each image released, say image2disk-v1.0.0
We could also add a commit label for each image released, say 0eaf0ebc

Thoughts?

Both sound good! :-)

It seems like if commits land and the README.md hasn't been updated, a new container reusing the same version string and thus the same tag will be pushed to quay. So there's no enforcement preventing us from pushing new containers with the same version string. (Also, per #69, other stuff may not be quite right with the release process.)
I'm not sure if we want to enforce updates to action README files or update the CD process to push an image tag corresponding to the commit ID, or what...

Obsolete


Serialize ignores flatten in a tuple struct or newtype struct

Both of the following appear to ignore the flatten attribute. I don't think we need to support these cases but they should be an error at compile time.
#[derive(Serialize)]
struct Mitsuhiko(#[serde(flatten)] HashMap<String, String>);

#[derive(Serialize)]
struct Mitsuhiko(usize, #[serde(flatten)] HashMap<String, String>);

Fixed by #1205


Fold all from last line

If editor has many lines of code and many items that can be folded,
then if you scroll down to the bottom of editor and try to execute "fold all" you will see blank page, until you do something that refresh it, like scroll up.

I can't repeat this in the EditBone but I will test this later.

I can't repeat this with the latest source. Send me a file that will fail, if this is still an issue.

Sorry for late I was busy.
Here is sample file, and video with last compiled bonecode.
frmMainUnit.zip

Thanks, I got it.

Fixed.


rename everything from joinrun to chymyst core

preparing for publishing the package under io.chymyst organization name rather than code.chymyst

Current coverage is 100% (diff: 100%)

Merging #96 into master will not change coverage

@@           master   #96   diff @@
===================================
  Files          13    13
  Lines         957   957
  Methods       854   854
  Messages        0     0
  Branches      103   103
===================================
  Hits          957   957
  Misses          0     0
  Partials        0     0

Powered by Codecov. Last update c3b2915...31311c6


Missing documentation for iron-icons

There's no information about iron-icons in the element catalog for polymer 1.0. In contrast, 0.5 documentation has a great page with examples of all the different icons.

This issue tracker is for the core Polymer library, not elements created with it.  We'll move this issue to the correct tracker.

This issue was moved to Polymer/polymer-element-catalog#151


Order of URL paths is significant

From the blog post describing the scheme, it sounded like the order in which packages are specified shouldn't matter as they're sorted via popularity contest. But I went ahead and tested by pulling both nixery.dev/shell/git/htop and nixery.dev/shell/htop/git and I got slightly different images. In particular, the layer lists contained 2 differing images. Here's the full diff:
--- /var/folders/cs/l6c6g06x0974_0w5pdg8dps80000gn/T//.psub.wcskj82kr7	2019-08-16 21:55:37.000000000 -0700
+++ /var/folders/cs/l6c6g06x0974_0w5pdg8dps80000gn/T//.psub.1eJdVVLLlj	2019-08-16 21:55:38.000000000 -0700
@@ -1,11 +1,11 @@
 [
     {
-        "Id": "sha256:53bc82b06d1d69b2269c7fbc3731b5562171edd5b017ab96ec53643da63fa1ea",
+        "Id": "sha256:7b17fd401c9bc238c5d3a0ffb950bb0970bf61505f7e29931072f58b7f99e8d4",
         "RepoTags": [
-            "nixery.dev/shell/git/htop:latest"
+            "nixery.dev/shell/htop/git:latest"
         ],
         "RepoDigests": [
-            "nixery.dev/shell/git/htop@sha256:3855a8e5cda85d1ae4c59572ef58b750118302a4c5ef2670d6904145cc708e69"
+            "nixery.dev/shell/htop/git@sha256:bfa000aeb58b39c4a31f45338d0d3120855685237a1257297033c31f3963eec6"
         ],
         "Parent": "",
         "Comment": "",
@@ -57,10 +57,10 @@
         "VirtualSize": 408528799,
         "GraphDriver": {
             "Data": {
-                "LowerDir": "/var/lib/docker/overlay2/0173427d85a846ea5f1297370978c82c03df8fc8772fc744a9fb34bfc5087035/diff:/var/lib/docker/overlay2/9e0c12530fc830ffdc09499c7935dac6bf431c452fafecd50420453da56912c2/diff:/var/lib/docker/overlay2/dde77970d035e06661e0e09d53f8dc1a300cd95acf952780762cf74046788ebd/diff:/var/lib/docker/overlay2/c3e31b7f14fa52bddee4c0608afbfb766a0f2c88520e52c958a19110b0932ff3/diff:/var/lib/docker/overlay2/a109334aa52bfa2db8c24a24a79f49d2501d9c533e59a3ee4c17568d15a6a7f8/diff:/var/lib/docker/overlay2/23464966c5047712a745a1a2673472399778d840f19d97631edb58cf53ea968c/diff:/var/lib/docker/overlay2/990b7892444eef37380e1873544b4509d3490bd18c7653787a25ef9ec0cf46c3/diff:/var/lib/docker/overlay2/70df7b589d5af8e06528f38fac08b455ddd71314140c137f84834363aeefe347/diff:/var/lib/docker/overlay2/5da78554e9c85d3e08745aefed2f759d4dd0d5eceab009a7966d90b207ccd639/diff:/var/lib/docker/overlay2/ec19c3f60d637182f12f13f961c444d4ddcef9df52836d4486279a512cda372a/diff:/var/lib/docker/overlay2/3669cf73da01bd50989eaa5fa7a553029afdc96d0b7b49f3ce021787c92f0d4f/diff:/var/lib/docker/overlay2/d23886ce103b580a6c259fd6629bfb627f55a4bfe3ba9f28bfc12b0149ad8d55/diff:/var/lib/docker/overlay2/36cf0eab6487ab1500e2b4aff19a11c33665edf68d5e1dbfd28770032056a00a/diff:/var/lib/docker/overlay2/f488d326274a0fca791eeaf36e831dce52fc3eef5a40962b16f31d51c52de0ff/diff:/var/lib/docker/overlay2/feaf5c02de8657b4377580c8e4ca8bc85ecf1916a880b026183ad1ba96fa4354/diff:/var/lib/docker/overlay2/69477bc47d3166e7865787fd26d5d2bcfc53eff6a1507e1d93bce17d25736a56/diff:/var/lib/docker/overlay2/c8baf1475e6727f76104fca23035bd5e044df5f040609a5d6368ae3e42c33974/diff:/var/lib/docker/overlay2/d23e31c50432e8742ab7cc8c843e7f54412fbc4198ff858df4a8ea5871107dbd/diff:/var/lib/docker/overlay2/26ccce43019489f715b366d745dec7bb2550577bb36b8082979ab649254b3527/diff:/var/lib/docker/overlay2/0471903f29c4c9b58d98d5d0f97c378a382b86228b38a9f6bc4109d8e221e1d3/diff:/var/lib/docker/overlay2/5642c9aa56a27b3db86147ce6de8c9f2be794d1f9953f2f5ca059d1dfbbfec09/diff:/var/lib/docker/overlay2/704b751c8877c6b898e860184ffe344e83173bba45b5635c9d27d6285ca74586/diff:/var/lib/docker/overlay2/e147e321e364b262cd83c9a147d0780b64fd600e6b016b825b25b0cc01887563/diff:/var/lib/docker/overlay2/c563d06fdb7e6932296169bf8f0c87d3e4ba04e68c2a858563de15781bc68eeb/diff:/var/lib/docker/overlay2/c14aa23daca50c008136f677edb0eeec9da75469c3b1b9e84689f75f36a3d472/diff:/var/lib/docker/overlay2/8cf4731d72882d448b1d7b0eb558f62b2ff2721ccd16cd9bb659bcf63e66f2dc/diff:/var/lib/docker/overlay2/6647bfa0e50c01238a24e531f9e42e373cb202845fe2240f08597a817dbe520c/diff:/var/lib/docker/overlay2/375afe318fb884ba994199d9efcb55ab08fada830dd0afe2b51a86c6be67c79e/diff:/var/lib/docker/overlay2/cf6737fe8f2c698e0bcbf984c4e83ff4a92a26d414ecf8c85cbfd9803d58dc67/diff:/var/lib/docker/overlay2/b437938fef8a668780c5f99b8c093f80106ca3a57bfbfe72d5cdb3d9bae4c17f/diff:/var/lib/docker/overlay2/ae78224e3cdbecf3c11866deacaa72161f34f5d2915665df932e9375523fb43d/diff:/var/lib/docker/overlay2/b01135f3d9eda3516f563beb7fe8498619d7e82b3ce837c85922e47cb87a2b57/diff:/var/lib/docker/overlay2/591f5127c0434e13251ffb7924702e8bb66ab0471c3636c8a7c7b4d320890ca2/diff:/var/lib/docker/overlay2/51c6b0170e7c4b0da8818a2ef1bc6a2c8f13276b2f927f5cac69af543a4026f8/diff:/var/lib/docker/overlay2/3d1ae9e5ef9f1697024ad8ce242ddcd975664eb108aece0260df6a5a183d9a05/diff:/var/lib/docker/overlay2/1a7d1f17d4a0f3fa100e284ea7fd95ed3af2f02c762d0a3db6658e337df61a92/diff:/var/lib/docker/overlay2/1acb4c623eea0f67d485edadb6957c231928eb35620ac22db072323e2259a0c0/diff:/var/lib/docker/overlay2/b11639100a2e2376430dfb633d09df3401423af0acc41916a98f9660dc5229a2/diff:/var/lib/docker/overlay2/64404bf6f20eab9060da0b69465ddb23b4c71f1fb1d1b08e595e559e2592fb57/diff:/var/lib/docker/overlay2/623fc39c0e766e39c30f39d5525972ea19e37b5deaca226526c0ed22207bd0be/diff:/var/lib/docker/overlay2/1da1f135bd886236f34af3c4a24dbe2dc8580c85c99389a543b4896717c88d2b/diff:/var/lib/docker/overlay2/266ee61abbeb47359c5a50fc7e07adfc1b03f50b1a3abcbf5d4a0c7a14f2fe4e/diff:/var/lib/docker/overlay2/7b56bf02a6691c46ed34d8983f5555078d5ab72c55f26708607873570b38d8f4/diff:/var/lib/docker/overlay2/7104ab400f45f8f079860dcf00a7a0382843b8ac36db3c4abb364a9c6512ceb5/diff:/var/lib/docker/overlay2/e0d100b33769dd8ace3baed0f866acc360f152757b9a61b8ec056695ad95af7b/diff",
-                "MergedDir": "/var/lib/docker/overlay2/b033a3d3a9c5f3b9a08fc4cde71d91f658aa4aa76d85ed643d66189e187252ee/merged",
-                "UpperDir": "/var/lib/docker/overlay2/b033a3d3a9c5f3b9a08fc4cde71d91f658aa4aa76d85ed643d66189e187252ee/diff",
-                "WorkDir": "/var/lib/docker/overlay2/b033a3d3a9c5f3b9a08fc4cde71d91f658aa4aa76d85ed643d66189e187252ee/work"
+                "LowerDir": "/var/lib/docker/overlay2/14792abcf705c37fdb9ac6f4267293b98907bdfedae6ecff3e48b596850acbae/diff:/var/lib/docker/overlay2/2d2ab3293bd81b743055052ed78e7dbecaf9975bbae8968fee13bdb9379353d1/diff:/var/lib/docker/overlay2/09dde8cd11a2ca944fff9637eff7050cef2cf06cde5ac7e9a2403b21366ff33b/diff:/var/lib/docker/overlay2/3cbe56c3289ca915b8ef74755efcc6fd10d52afcf5a35033bd6d75646f147e9d/diff:/var/lib/docker/overlay2/6cd985e95c6c12116c38fe47e59748d283edc2d856a185638480083daca094b8/diff:/var/lib/docker/overlay2/0cb276a10a505dee21b4e45e19e67ba10c7ffde59bcf3757dfafe8a141aebc0f/diff:/var/lib/docker/overlay2/20a388730805e67d0774714e77ab65e095bef321d419434a3d1526efd0dae8af/diff:/var/lib/docker/overlay2/fa82b2c6bd97068f9e09fb469e34d226fcc889e4df10f26dec864eaec1cefa2c/diff:/var/lib/docker/overlay2/154823073d424cf0f47c207a17031f87a2aea3d3dc820ce23ee3aecf2d76d767/diff:/var/lib/docker/overlay2/17637c1c503ed9feb9ca381fe42da834d86a0bd3525512b318a5a5e9f0bc3bcb/diff:/var/lib/docker/overlay2/d7dc82b156eb6f7eba8a7c95b8b5bb7434cd73ebcba3abc3855c7d292581a889/diff:/var/lib/docker/overlay2/6a21f3f712d74b2ccf358d3c7e31fe37ed1c291d793e6f2ad111e1933ac2cceb/diff:/var/lib/docker/overlay2/f5b9c1851f37c9ee761fb14e51c4307e8fb60e6abd0f0ca2c538567c4425515d/diff:/var/lib/docker/overlay2/797ea8a649006321f87220c4b197d2fdc8fe809b884acf1d4cbdeae45e808f93/diff:/var/lib/docker/overlay2/50f91994ccb3f068a3ba4f20cdabf4f382029cf5c71cc887360324148b598aa9/diff:/var/lib/docker/overlay2/69e3c0b79a8d39340f3ed48d6188bb69b66692b0e53f0cd9c012018d8a50fb93/diff:/var/lib/docker/overlay2/0a1753dbd450ee66008df9689a088707d4e882e374b1cdcd3daf1127053d7db6/diff:/var/lib/docker/overlay2/62c6667c1a4a49f31a38c54d1fa015bf916cd882d32f89dbafa58b6f9ccd0a7c/diff:/var/lib/docker/overlay2/861cd74355b40af4c2d685fddbe7a022f6183a33240f1383d2ab32deccd49310/diff:/var/lib/docker/overlay2/f3d75a6190e42ed22bba0c58a9da530183494004c7b24fb08af3c53f5e467a2a/diff:/var/lib/docker/overlay2/76282c15172d2988732f76628a0f87abcfe430af4f6db622627d17321e445c46/diff:/var/lib/docker/overlay2/f9c1c035e2795d5a1fb3674f93c7c8ca6225710e3047dc514509434e8c408bbe/diff:/var/lib/docker/overlay2/7468caa33034fbf51821fc9bf92b7bfcedd5ce8201141da0f60d36542d5157f1/diff:/var/lib/docker/overlay2/0641004c456502e294f98a79c9a0441a2474edb74fb6357bad1e32bbf25645d3/diff:/var/lib/docker/overlay2/ae405a83479c996b731a98d782dca709339ac6eb1550ecb20e1da345fd833414/diff:/var/lib/docker/overlay2/2ae9c037a29731d8cb8f0a8b1de74d8cec6deff2a2bae3a9345244712d76951d/diff:/var/lib/docker/overlay2/cf1b36939a0805bc8ff097bf953845b67e6bbd762cc9dd9301e637aefd99e557/diff:/var/lib/docker/overlay2/467e910616641965e05577737aae7f121a566c82a3a7fec8ef6097730622c1ff/diff:/var/lib/docker/overlay2/fde6f959bbe09348450ecacf9b2b615bf15b9e94b470aa2efb106a5517f07291/diff:/var/lib/docker/overlay2/03be3883b2ff67f6e46899a123bb499fc4f24ce7568082d6a22ec7662291c449/diff:/var/lib/docker/overlay2/7b00ee3f271f3d17006a1c237b5579dc4d87be14da9f2267bbcb1689fd8ba205/diff:/var/lib/docker/overlay2/e18c5b408bfac03f6b1375f33cf1d5f3d13c8478877e912ba2e50b5fc66c5a41/diff:/var/lib/docker/overlay2/fb57ec9c16caf44d446c846fc44098f62d94028d8b5831e4472f575c279e1040/diff:/var/lib/docker/overlay2/1fbb6a28d4d1f245d5fbe5078d3639debe6db8af82c71de62a5124c42fe5fd5b/diff:/var/lib/docker/overlay2/eace056934b863204eef85854d5b81d44b45935418f4af4f6bce9912bedcc396/diff:/var/lib/docker/overlay2/16354c0a2b73f9213f75df131d7e06c81b2a27e5ee3bb9577266791e854c00f6/diff:/var/lib/docker/overlay2/9966da64c3e64e2146b3e10e3cf6183b9c14019421c7ed68da607769864dcbbe/diff:/var/lib/docker/overlay2/3be492a2c42b9bfb37dbb76e21538520d7cc1a3e9aae8b7bb5dc3ada4c7a7c87/diff:/var/lib/docker/overlay2/947a85ad184790812be3a7fe1930180618bd8ecd52600563e5b688d44d89e71c/diff:/var/lib/docker/overlay2/623fc39c0e766e39c30f39d5525972ea19e37b5deaca226526c0ed22207bd0be/diff:/var/lib/docker/overlay2/1da1f135bd886236f34af3c4a24dbe2dc8580c85c99389a543b4896717c88d2b/diff:/var/lib/docker/overlay2/266ee61abbeb47359c5a50fc7e07adfc1b03f50b1a3abcbf5d4a0c7a14f2fe4e/diff:/var/lib/docker/overlay2/7b56bf02a6691c46ed34d8983f5555078d5ab72c55f26708607873570b38d8f4/diff:/var/lib/docker/overlay2/7104ab400f45f8f079860dcf00a7a0382843b8ac36db3c4abb364a9c6512ceb5/diff:/var/lib/docker/overlay2/e0d100b33769dd8ace3baed0f866acc360f152757b9a61b8ec056695ad95af7b/diff",
+                "MergedDir": "/var/lib/docker/overlay2/b51dfce287846321b63fd4adc9b31cf77abcacfd6846eb50f9c1f7dee7377080/merged",
+                "UpperDir": "/var/lib/docker/overlay2/b51dfce287846321b63fd4adc9b31cf77abcacfd6846eb50f9c1f7dee7377080/diff",
+                "WorkDir": "/var/lib/docker/overlay2/b51dfce287846321b63fd4adc9b31cf77abcacfd6846eb50f9c1f7dee7377080/work"
             },
             "Name": "overlay2"
         },
@@ -73,18 +73,19 @@
                 "sha256:965ae3c47f2287813c574e1c6950f684e5a387b12eb38025bb885660d05a2bfb",
                 "sha256:9359cddeb36f01d6e4b13fe9d72826739277b5a330925b998ee7d2b2526ffc9f",
                 "sha256:30e81ceec044c2fca5f95e39a144acafd71b2a9409e5df7c61fc8888470878ca",
-                "sha256:3c82b95881ccfb56f7b9345cfe0f32e951c1fa08c8c0c2619e536baf436b44de",
                 "sha256:2e9f080e2b60c694a01fe00b507232e6269834f40653878cee9958838357eea3",
                 "sha256:f7c07daf6fb408e266b01c024ff7a55467963e0e191862e0143cfaa1adc405f9",
                 "sha256:1f5d95f5b4189585125a4b8dfd6be77732535d3c196d7b08902b2515e954ea79",
                 "sha256:e6d65fe539f9f6458ee4b8bf80d81650190a78921bbecdee33a4078936900fc4",
                 "sha256:c8796d3861127d80efa6011559b0a900a92134e13b51ba320affae877ddd7c8b",
+                "sha256:fe49c2421c9f0b77b82bf1ec399a01a9d90565504fd59052f01f8f464ba46792",
                 "sha256:f57e2949a73e1490b02c00423cc7f9e55ae5c2673d37235b76e252d9cda73c6e",
                 "sha256:6aac2ada745c369ab4a600189bb8dca5967910f436c2d34df0b514a8866627ef",
                 "sha256:536d9863dbbe6a6890fe6e2f6bfee027279dda11f5a327be494f5bad36ae61e9",
                 "sha256:ad9c996a76ae965421152f2e8f28c74b208523f21841a44117a2e94707324464",
                 "sha256:fb243fa1fb24bfcc9d47a438a39ed98e1e6644aaad4bbab98024e707cf8af72d",
                 "sha256:575a2971905010731a67babf8f1d20c4e05c84e5159ee246c08cf969c27767a2",
+                "sha256:6a9f9c115e3b0646f11f20333fef51231c62fe1bf11a2b43d844c544e0968152",
                 "sha256:153e701ec17a1c58f0b3d0d2f579c00a6c6f6ae13971f9a7496e3ef576ced6f4",
                 "sha256:36b9305f1391adf7e08203524629c65fcc4dd74e34eb08edfe61c76e8cb641cd",
                 "sha256:6420057074310204895a90707c878896ab0beb65225c8023bd1cce926122a2ef",
@@ -103,7 +104,6 @@
                 "sha256:587045e8ec0564d717693c5e8a0d85deff936c0a77571e03482707d107187a85",
                 "sha256:1fd6e1d73b5ca24f9c911486c8b01a7d9ea9ce67f2ed9b9eb30f32878d9a827a",
                 "sha256:fc9ba6680afff052f093449c0bb7e949e424b17103a61310a84106c5167c8790",
-                "sha256:f1456e4b73154401ed88593d90163d3cf8df85deaa4a85f7f31b700384ff8c4d",
                 "sha256:8e079aea2d57922972c7304e76a6e890e6f616db96a7ce5d24753048990cf20a",
                 "sha256:20dd260d105a505ebc7f59648c6cb4e2fde888128a4db65059dd943170ec8676",
                 "sha256:41741c3dd0f6d50a54de266714e85a21cd3797429b5bb3f922bdd2c501699b02",

Thanks for reporting! Presumably the differing layers are metadata layers because there's nothing ensuring a stable order at the moment. I'll verify that - the fix should be easy if that's the issue.

Fix is in the PR above, it was simply to sort the package list so that identical metadata would be generated.
I'll be rolling this out on the public instance soon.


RESOURCE_EXHAUSTED: XLA:TPU compile permanent error

To Reproduce
Use a TPU v2_8 with vm architecture
Time For configure functions and sharding them (ms) : 2012.7429962158203
Action : Sharding Passed Parameters
Model Contain  1.100048384  Billion Parameters
  0%|                                                                                | 0/12000 [00:00<?, ?it/s]jax.errors.SimplifiedTraceback: For simplicity, JAX has removed its internal frames from the traceback of the following exception. Set JAX_TRACEBACK_FILTERING=off to include these.

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/home/***/research/EasyDeL/1.py", line 101, in <module>
    output = trainer.train(flax.core.FrozenDict({"params": params}))
  File "/home/***/research/EasyDeL/.venv/lib/python3.10/site-packages/EasyDel/trainer/causal_language_model_trainer.py", line 708, in train
    sharded_state, loss, accuracy = self.sharded_train_step_fn(
jaxlib.xla_extension.XlaRuntimeError: RESOURCE_EXHAUSTED: XLA:TPU compile permanent error. Ran out of memory in memory space hbm. Used 21.90G of 7.48G hbm. Exceeded hbm capacity by 14.42G.

Where you are running these codes?
They provide you with tpuv2 and you are getting out of memory errors
You can use kaggle for free TPUv3 and that's much more powerful


hello

Batch Export To Foreign Formats
I couldn't download this macro, where to download it

https://github.com/codestackdev/solidworks-api-examples/tree/master/edrawings-api/Export

https://github.com/codestackdev/solidworks-api-examples/tree/master/edrawings-api/Export

only macro execution required


localhost refused to connect.

Hi,
I tried to build mediocre on my Windows 11 like
~> yarn
~> yarn tauri dev

When the tauri application starts, I get following error message:
localhost refused to connect.
ERR_CONNECTION_REFUSED

Please, could you tell what I am doing wrong?
I also tried to build a release ala:
yarn build:fe

I totally forgot the debug message
[2022-12-28T16:10:04Z INFO] Starting Tauri backend...
[2022-12-28T16:10:05Z INFO] db does not exist, creating new db...

I think the application has not the correct permissions.

Hey @harryherold
Thanks for checking out mediocre.
The issue seems to be because Tauri can't find the front-end dev server on localhost.
If you want to run in dev you should try:

yarn start which concurrently runs:

yarn devfe
yarn devbe

Essentially the devfe (front-end dev server) needs to start before the devbe (Tauri backend). So that it can find it running on http://localhost:3000/.  Also make sure you give the Windows firewall permission for the same.
I think in your case you do not want to develop it but rather just build it. In that case you should just run yarn build.
Also note that the project might still fail to build because its using a pre-release version of Tauri. I'm considering a rewrite of this in the future, therefore all developments on this have been on a hold.


Unable to find attachment on GetAttachmentRequestModel when running on Linux and attachment is windows-based path

Agent Version and Platform
2.150.3
OS of the machine running the agent? OSX/Windows/Linux/...
Linux (Ubuntu)
Azure DevOps Type and Version
dev.azure.com
What is your organization name?
https://dev.azure.com/henryscheinone
What's not working?
Unable to publish artefacts from a .trx because the job ran on Windows Machine and my agent runs on a Linux machine.
Logs:
2019-06-26T02:07:33.0806483Z ##[debug]  /azp/agent/_work/r2/a (directory)
2019-06-26T02:07:33.0812577Z ##[debug]  /azp/agent/_work/r2/a/ExactBuildResults (directory)
2019-06-26T02:07:33.0816703Z ##[debug]  /azp/agent/_work/r2/a/ExactBuildResults/hydration (directory)
2019-06-26T02:07:33.0821352Z ##[debug]  /azp/agent/_work/r2/a/ExactBuildResults/hydration/meta-build.json (file)
2019-06-26T02:07:33.0821853Z ##[debug]  /azp/agent/_work/r2/a/ExactBuildResults/hydration/meta-gitversion.json (file)
2019-06-26T02:07:33.0822232Z ##[debug]  /azp/agent/_work/r2/a/ExactBuildResults/hydration/meta-version.json (file)
2019-06-26T02:07:33.0823356Z ##[debug]  /azp/agent/_work/r2/a/TestResults (directory)
2019-06-26T02:07:33.0823806Z ##[debug]  /azp/agent/_work/r2/a/TestResults/Deploy_vagrant 2019-06-26 14_15_22 (directory)
2019-06-26T02:07:33.0828404Z ##[debug]  /azp/agent/_work/r2/a/TestResults/Deploy_vagrant 2019-06-26 14_15_22/In (directory)
2019-06-26T02:07:33.0830693Z ##[debug]  /azp/agent/_work/r2/a/TestResults/Deploy_vagrant 2019-06-26 14_15_22/In/TAU-8368-NZ-1 (directory)
2019-06-26T02:07:33.0833823Z ##[debug]  /azp/agent/_work/r2/a/TestResults/Deploy_vagrant 2019-06-26 14_15_22/Out (directory)
2019-06-26T02:07:33.0836152Z ##[debug]  /azp/agent/_work/r2/a/TestResults/vagrant_TAU-8368-NZ-1_2019-06-26_14_16_18 (directory)
2019-06-26T02:07:33.0838409Z ##[debug]  /azp/agent/_work/r2/a/TestResults/vagrant_TAU-8368-NZ-1_2019-06-26_14_16_18/In (directory)
2019-06-26T02:07:33.0845915Z ##[debug]  /azp/agent/_work/r2/a/TestResults/vagrant_TAU-8368-NZ-1_2019-06-26_14_16_18/In/4bf1fae2-8c27-45a9-b4b6-bd3703ffcaec (directory)
2019-06-26T02:07:33.0848721Z ##[debug]  /azp/agent/_work/r2/a/TestResults/vagrant_TAU-8368-NZ-1_2019-06-26_14_16_18/In/4bf1fae2-8c27-45a9-b4b6-bd3703ffcaec/TAU-8368-NZ-1 (directory)
2019-06-26T02:07:33.0857195Z ##[debug]  /azp/agent/_work/r2/a/TestResults/vagrant_TAU-8368-NZ-1_2019-06-26_14_16_18/In/4bf1fae2-8c27-45a9-b4b6-bd3703ffcaec/TAU-8368-NZ-1/error_NZPayorsInsuranceTestSuite_NZAddPayor_14-16-07.jpeg (file)
2019-06-26T02:07:33.0857790Z ##[debug]  /azp/agent/_work/r2/a/TestResults/vagrant_TAU-8368-NZ-1_2019-06-26_14_16_18.trx (file)
2019-06-26T02:07:33.0858044Z ##[debug]  /azp/agent/_work/r2/a/hydration (directory)
2019-06-26T02:07:33.0915861Z ##[debug]  /azp/agent/_work/r2/a/hydration/meta-build.json (file)
2019-06-26T02:07:33.0916842Z ##[debug]  /azp/agent/_work/r2/a/hydration/meta-gitversion.json (file)
2019-06-26T02:07:33.0918130Z ##[debug]  /azp/agent/_work/r2/a/hydration/meta-version.json (file)
2019-06-26T02:07:33.0918463Z ##[debug]  /azp/agent/_work/r2/a/screenshots (directory)
2019-06-26T02:07:33.0920114Z ##[debug]  /azp/agent/_work/r2/a/screenshots/26-06-2019_0 (directory)
2019-06-26T02:07:33.0922051Z ##[debug]  /azp/agent/_work/r2/a/screenshots/26-06-2019_0/error_NZPayorsInsuranceTestSuite_NZAddPayor_14-16-07.jpeg (file)
2019-06-26T02:07:33.0924510Z ##[debug]24 results
2019-06-26T02:07:33.0925114Z ##[debug]found 24 paths
2019-06-26T02:07:33.0925710Z ##[debug]applying include pattern
2019-06-26T02:07:33.0927110Z ##[debug]adjustedPattern: '/azp/agent/_work/r2/a/**/*.trx'
2019-06-26T02:07:33.0943528Z ##[debug]1 matches
2019-06-26T02:07:33.0951129Z ##[debug]1 final results
2019-06-26T02:07:33.0951648Z ##[debug]Detected 1 test result files
2019-06-26T02:07:33.0953737Z ##[debug]PublishTestResults.OverrideExeFlow=undefined
2019-06-26T02:07:33.0954358Z ##[debug]OS type: Linux
2019-06-26T02:07:34.5800316Z ##[debug]Reading test results from file '/azp/agent/_work/r2/a/TestResults/vagrant_TAU-8368-NZ-1_2019-06-26_14_16_18.trx'
2019-06-26T02:07:34.7307242Z ##[debug]Setting run start and finish times.
2019-06-26T02:07:34.7350708Z ##[debug]Attachment location: /azp/agent/_work/r2/a/TestResults/vagrant_TAU-8368-NZ-1_2019-06-26_14_16_18/In
2019-06-26T02:07:34.9770144Z ##[debug]Total test results: 3
2019-06-26T02:07:35.2510902Z ##[error]There are one or more test failures detected in result files. Detailed summary of published test results can be viewed in the Tests tab.
2019-06-26T02:07:35.2889660Z ##[debug]Processed: ##vso[results.publish type=VSTest;mergeResults=true;runTitle=Exact Tests NZ;publishRunAttachments=true;resultFiles=/azp/agent/_work/r2/a/TestResults/vagrant_TAU-8368-NZ-1_2019-06-26_14_16_18.trx;failTaskOnFailedTests=true;testRunSystem=VSTS - PTR;]
2019-06-26T02:07:35.2890985Z ##[debug]task result: Succeeded
2019-06-26T02:07:35.2892395Z ##[debug]Processed: ##vso[task.complete result=Succeeded;]
2019-06-26T02:07:35.2893067Z ##[debug]Release.ReleaseUri=vstfs:///ReleaseManagement/Release/8368
2019-06-26T02:07:35.2893485Z ##[debug]Release.ReleaseId=8368
2019-06-26T02:07:35.2893823Z ##[debug]Build.BuildUri=vstfs:///Build/Build/31448
2019-06-26T02:07:35.2894150Z ##[debug]Build.Buildid=31448
2019-06-26T02:07:35.3026133Z ##[debug]Processed: ##vso[telemetry.publish area=TestExecution;feature=PublishTestResultsTask]{"releaseuri":"vstfs:///ReleaseManagement/Release/8368","releaseid":"8368","builduri":"vstfs:///Build/Build/31448","buildid":"31448","osType":"Linux","testRunner":"VSTest","failTaskOnFailedTests":"true","mergeResultsUserPreference":"true","config":null,"platform":null,"testResultsFilesCount":1,"subFeature":"publishTestResultsTaskConsolidatedCiEvent"}
2019-06-26T02:07:35.3175669Z ##[section]Async Command Start: Publish test results
2019-06-26T02:07:35.4390232Z Publishing test results to test run '1043868'
2019-06-26T02:07:35.4390493Z Test results remaining: 3. Test run id: 1043868
2019-06-26T02:07:35.9486052Z ##[warning]Skipping attachment as it is not available on disk: /azp/agent/_work/r2/a/TestResults/vagrant_TAU-8368-NZ-1_2019-06-26_14_16_18/In/4bf1fae2-8c27-45a9-b4b6-bd3703ffcaec/TAU-8368-NZ-1\error_NZPayorsInsuranceTestSuite_NZAddPayor_14-16-07.jpeg

It should try to convert the path first, then check if it exists:
On GetAttachmentRequestModel (link here):
        private TestAttachmentRequestModel GetAttachmentRequestModel(string attachment)
        {
            Trace.Entering();
            if (!File.Exists(attachment))
            ...

It could be:
        private TestAttachmentRequestModel GetAttachmentRequestModel(string attachment)
        {
            // Convert attachment to localpath.  Ref: https://docs.microsoft.com/en-us/dotnet/api/system.uri.localpath?view=netframework-4.8#remarks
            attachment = new Uri(attachment).LocalPath;
            Trace.Entering();
            if (!File.Exists(attachment))
            ...

i think the root issue should be which code generate the full path that contains the wrong slash
/azp/agent/_work/r2/a/TestResults/vagrant_TAU-8368-NZ-1_2019-06-26_14_16_18/In/4bf1fae2-8c27-45a9-b4b6-bd3703ffcaec/TAU-8368-NZ-1\error_NZPayorsInsuranceTestSuite_NZAddPayor_14-16-07.jpeg
@nigurr

That's part of my .trx file:
      <ResultFiles>
        <ResultFile path="TAU-8368-NZ-1\error_NZPayorsInsuranceTestSuite_NZAddPayor_14-16-07.jpeg" />
      </ResultFiles>

As you can see, it uses the windows path, because the test was executed on a windows machine.

sorry, I am a little bit confused, if you test is run on a windows machine, why the test result is upload by a Linux agent? I would expect you have a windows agent that runs the test and upload the test result file.

So I have a Linux machine to be only the agent, the one that communicates to the Azure and send the commands.  My windows machine is a VM with a bare minimum configuration to run some UI tests.
I can't execute an agent on that windows VM because it gets reverted to a snapshot very often.


Rename idcollege.txt to ict-idcollege.txt

ict afdeling ID College zoetermeer

The main college domain is idcollege.nl - please provide some proof of the fact, that ict-college.nl also belongs to the school. Thanks!

obsolete, please reply to reopen


makeKernelHeaders: expose at top-level, support kernel 5.3 and newer

Motivation for this change
I want to provide newer kernel headers to a package that requires them.
Things done

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

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

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

Notify maintainers
cc @lostman

I agree it would be good to make this function public, however, we should avoid adding more functions to the top-level; it's really intended only for packages and package sets.

Is there a recommended place to put functions like these?

Not really. You could add the function to its own passthru. You would then get linuxHeaders.makeLinuxHeaders.

I think there may still be a reason to expose makeKernelHeaders when working with non-mainline features. However the features I wanted were merged around 5.0, so updating to 5.5 is sufficient. Going to close in favor of the update.


Callout Dialog Fixes + WYSIWYG Improvements for Insert Link

https://user-images.githubusercontent.com/40371649/109606492-9b7cb580-7adb-11eb-94d8-b44bf6dbe5c4.mp4
I apologize for fixing a few different things in this PR, but they were all related.
Fixes #12859.
Fixes #14406.

Added Insert Link Callout functionality to WYSIWYG
Link text in callout is set by default in both WYSIWYG + non-WYSIWYG editor modes if text is selected
Keyboard navigation now works as expected in Link callout
Fixed markdown generated in callout to be consistent with previous md link generation in non-WYSIWYG modes

Pull Request Test Coverage Report for Build 613048033

13 of 78 (16.67%)  changed or added relevant lines in 4 files are covered.
3 unchanged lines in 1 file lost coverage.
Overall coverage increased (+0.009%) to 43.145%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

src/sql/workbench/contrib/notebook/browser/cellViews/textCell.component.ts
0
1
0.0%

src/sql/workbench/contrib/notebook/browser/markdownToolbarActions.ts
12
15
80.0%

src/sql/workbench/contrib/notebook/browser/calloutDialog/linkCalloutDialog.ts
0
17
0.0%

src/sql/workbench/contrib/notebook/browser/cellViews/markdownToolbar.component.ts
1
45
2.22%

Files with Coverage Reduction
New Missed Lines
%

src/sql/workbench/contrib/notebook/browser/calloutDialog/linkCalloutDialog.ts
3
1.69%

Totals

Change from base Build 612384165:
0.009%

Covered Lines:
25080

Relevant Lines:
53113

💛  - Coveralls

Tested linking and looks good! Theres still that issue of ESC key closing the dialog and exiting edit mode though.

@lucyzhang929 Yeah that'll be tackled separately in a different PR. Tracked by #14434


Add test spec ARN input

Closes https://github.com/peartherapeutics/bitrise-aws-device-farm-runner/issues/46

Please someone can approve this PR @fadookie

Sorry I have not had time to test it yet. I am planning on moving these repos over to the bitrise community organization soon so others can help maintain them as I don't even use them anymore

Hi @fadookie, Can we help you with testing this ? Adding test spec to the list would help us in the work we are doing straight away. Please let me know if there is anything we can do to help ?

@vj-raghavan to simplify testing I can merge this to a non-master branch so you can point directly at it from your bitrise.yml and test to see if it works.

@vj-raghavan I've merged these changes to the ginmon-master branch. You can point your bitrise.yml to use this branch directly to verify that these changes do what's needed - I was not sure how to create a test case for this functionality.
We no longer use this step at my work so I am going to try to get it moved to the bitrise community org so it can be maintained there. If you're interested in being a new maintainer we could use one or more, I don't have time to do it anymore.

Created a new PR to track movement of this code to master branch after testing is complete:
https://github.com/peartherapeutics/bitrise-aws-device-farm-runner/pull/52

@elashpear I have been using the code in our pipeline and can confirm that this works as intended. I was thinking there might be something else that we need to be doing. But if its getting it run locally and verify that the changes work as intended it does.
Please merge it in.


Adding game object from container to scene renders the game object twice.

Version
3.20.1

Phaser Version:
All
Operating system:
All
Browser:

Description
I am not sure if it is intended to behave like this but when a game object is added to scene through add.existing method which was already added to a container, then the game object is being rendered twice, even if the game object is a single instance unless we remove it from the container explicitly.
Example Test Code
var config = {
    type: Phaser.AUTO,
    parent: 'phaser-example',
    width: 800,
    height: 600,
    scene: {
        preload: preload,
        create: create,
        extend: {
            createCards: createCards
        }
    }
};

var game = new Phaser.Game(config);

function preload ()
{
    this.load.atlas('cards', 'assets/atlas/cards.png', 'assets/atlas/cards.json');
}

function create ()
{

this.container = this.add.container();
    this.container.x = 100;

    this.createCards();

    this.input.on('gameobjectdown', function (pointer, gameObject) {
        console.log(this)
        if(gameObject.addedToContainer){
            this.add.existing(gameObject);
            //should explicitly remove from the container to fix it.
            //this.container.remove(gameObject);
            gameObject.addedToContainer =false;
        }
        else{
            this.container.add(gameObject);
            gameObject.addedToContainer = true;
        }
        //gameObject.destroy();

    }.bind(this));
}

//  Creates 64 random card sprites on the screen and sets them all to be interactive
function createCards ()
{
    var frames = this.textures.get('cards').getFrameNames();

    for (var i = 0; i < 1; i++)
    {
        var x = Phaser.Math.Between(0, 800);
        var y = Phaser.Math.Between(0, 600);
        var s = Phaser.Math.FloatBetween(0.5, 1);

        var image = this.add.image(x, y, 'cards', Phaser.Math.RND.pick(frames)).setScale(s).setInteractive();
        this.container.add(image);
        image.addedToContainer = true;

    }
}

I think that's intended.

This is correct, the Scene is not a parent container, so there is no removal of the Game Object from the Container. Containers aren't even exclusive, a single Game Object can exist in multiple Containers (if they're created to be non-exclusive)


Cannot find the parameter CBRK_IO_SAFETY

I have successfully uploaded the px4_fmu-v5_default.px4 to QGC. However, in the Parameters interface I cannot find the parameter CBRK_IO_SAFETY, which has been defined in src/lib/circuit_breaker/circuit_breaker_params.c (other parameters in this file can be seen otherwise). There is another question about motors. Having chosen the airframe 'Hexarotor x with tilted arms', there's only 4 motors in total. More details can be seen in screenshots below. Looking forward to your advice！

I also encountered this problem. Have you solved it?Thank you.


update: egui dependencies to 0.27

Any chance that this one gets merged?

In the mean-time, you can use this patch in your Cargo.toml:
[patch.crates-io]
egui-plotter = { git = "https://github.com/Gip-Gip/egui-plotter.git", rev = "refs/pull/16/head" }

(or refs/pull/15/head for egui 0.26)


Tracking Issue For migrate integration from dotnet/aspire repo

We're looking to migrate some of the integrations from the .NET Aspire repo.
There is some open PRs like #5786 , #5721 in aspire repo that should move to this repo.
@aaronpowell @davidfowl, Could you please list other integrations that should move to this repo and update the issue description?

I've move ActiveMQ to the community toolkit as proposed in other "issues": https://github.com/CommunityToolkit/Aspire/pull/273.
When should something be part of the CommunityToolkit?

When should something be part of the CommunityToolkit?

We should get something more clearly written up on when something would be a candidate for the Community Toolkit and when it's not.
Simply put, new integrations should be proposed in the Community Toolkit and not the dotnet/aspire repo. But that doesn't mean that everything would be a candidate for the toolkit, after all, we have finite amount of capacity to support everything, so some general thoughts I have are:

Is it broadly useful to people building with Aspire? If it's super niche and only going to be used by you, it's not likely a good candidate.
Does it fit with the problem space that Aspire operates in? Aspire is designed to improve the developer inner loop, especially for distributed applications, so the integration should fit in that.
Does the company/OSS project the integration is for want to create/manage it themselves? For example, RavenDB was proposed early on, but they would prefer to ship it in their tool stack, so having an integration here doesn't make sense.

I am the author of the KrakenD integration (component) mentioned above. I am curious if it’s relevant to migrate or not given some of the criteria mentioned. That said, I have not seen many options for API Gateway integrations in Aspire which is a common design pattern for microservice based architectures.
I also completely understand the maintenance burden too. So with that said, what is the process here? Should a proposal issue be written to discuss community interest etc?

I hear what you are saying, however there are cases where you might want this locally to reproduce things like token exchange or header augmentation etc. If you use this for rate limiting, api keys, caching, etc. I think there is a compelling use case to supplement the local development experience. It’s kind of a necessary evil for specific microservice designs.

I can see how it would be valuable in a dev workflow, otherwise you're never truly testing/developing the app under the conditions that users are using it, and as such, run the risk of "works on my machine" but nowhere else.
Rather than overloading this issue, if you think KrakenD is something you'd want to contribute to the toolkit, let's spin up a new issue on it (as I have some thoughts on design/features/etc.). But at the same time, I want others to not feel any pressure to have their integrations in the toolkit or that we're trying to be a gatekeeper to integrations.

Apache Pulsar - feat: support Aspire.Hosting.Apache.Pulsar dotnet/aspire#4146

Should I move pulsar integration?

Apache Pulsar - feat: support Aspire.Hosting.Apache.Pulsar dotnet/aspire#4146

Should I move pulsar integration? @aaronpowell

Happy to review it as a contribution. Make sure you check out the contributor guide on how to set it up in the repo.

Apache Pulsar: Easy adopt, very well implemented. Also uses VolumeNameGenerator though

I'd have to update on guidance about VolumeNameGenerator, care to elaborate or we can take it in the follow-up PR?

We have a copy of that file in the repo in a shared location that you can add into projects. Check out https://github.com/CommunityToolkit/Aspire/blob/main/src/CommunityToolkit.Aspire.Hosting.ActiveMQ/CommunityToolkit.Aspire.Hosting.ActiveMQ.csproj#L8-L10

I can see how it would be valuable in a dev workflow, otherwise you're never truly testing/developing the app under the conditions that users are using it, and as such, run the risk of "works on my machine" but nowhere else.
Rather than overloading this issue, if you think KrakenD is something you'd want to contribute to the toolkit, let's spin up a new issue on it (as I have some thoughts on design/features/etc.). But at the same time, I want others to not feel any pressure to have their integrations in the toolkit or that we're trying to be a gatekeeper to integrations.

Submitted https://github.com/CommunityToolkit/Aspire/issues/328


Race Mode: Invuln fix (Issue #115)

This one was a fun one - StartInvul call without explicitly setting Player.m_spawn_invul_active field to false essentially made invuln granted by L2 Upgrade Points behave like spawn invuln, which we know disappears rapidly based on your ship's velocity

The best part is I noticed that difference and didn't even think it was necessary.


Invalid message: "connect" and "host"/"port" are mutually exclusive when debugging (Insiders)

Environment data

VS Code version: 1.44.0-insider Commit: b7bfce30
Extension version (available under the Extensions sidebar): 2020.4.68094-dev
OS and version: MacOS Mojave 10.15.3
Python version (& distribution if applicable, e.g. Anaconda): 3.8.0
Type of virtual environment used (N/A | venv | virtualenv | conda | ...): N/A
Relevant/affected Python packages and their versions: jedi 0.16.0
Relevant/affected Python-related VS Code extensions and their versions: N/A
Jedi or Language Server? (i.e. what is "python.jediEnabled" set to; more info #3977): false
Value of the python.languageServer setting: Microsoft

Expected behaviour
Debugging a Python file should work.
Actual behaviour
Debugging doesn't work all the time.
Steps to reproduce:

Create a new project with the following file:

import jedi

with open("empty_file.py") as file:
    source = file.read()

script = jedi.Script(source=source, line=1, column=0)

Create a launch.json file with the basic Python: Current file configuration
Start debugging

Notes:

Commenting out the last line (script = jedi....) allows debugging to start without issues.
Debugging this script works in the stable release of the extension (2020.2.64397)

Logs
Output for Python in the Output panel (View→Output, change the drop-down the upper-right of the Output panel to Python)
User belongs to experiment group 'ShowPlayIcon - start'
User belongs to experiment group 'DebugAdapterFactory - experiment'
User belongs to experiment group 'PtvsdWheels37 - experiment'
User belongs to experiment group 'UseTerminalToGetActivatedEnvVars - control'
User belongs to experiment group 'WebHostNotebook - control'
User belongs to experiment group 'CollectLSRequestTiming - experiment'
User belongs to experiment group 'CollectNodeLSRequestTiming - experiment'
> conda --version
> ~/opt/anaconda3/bin/conda info --json
> pyenv root
> python3.7 -c "import sys;print(sys.executable)"
> python3.6 -c "import sys;print(sys.executable)"
> python3 -c "import sys;print(sys.executable)"
> python2 -c "import sys;print(sys.executable)"
> python -c "import sys;print(sys.executable)"
> ~/.pyenv/versions/3.8.0/bin/python3.8 -c "import sys;print(sys.executable)"
> ~/opt/anaconda3/bin/conda env list
> ~/.pyenv/versions/3.8.0/bin/python3.8 -c "import jupyter"
> ~/.pyenv/versions/3.8.0/bin/python3.8 -c "import jupyter"
> ~/.pyenv/versions/3.8.0/bin/python3.8 -c "import notebook"
> ~/.pyenv/versions/3.8.0/bin/python3.8 -c "import notebook"
> ~/opt/anaconda3/bin/conda env list
Starting Microsoft Python language server.
> ~/.pyenv/versions/3.8.0/bin/python3.8 -m autopep8 --diff ~/Documents/Sandbox/foo/one_file.py.8468da13c1572aa4ef40a54aad7ae461.py
cwd: ~/Documents/Sandbox/foo
> ~/.pyenv/versions/3.8.0/bin/python3.8 -m autopep8 --diff ~/Documents/Sandbox/foo/one_file.py.8468da13c1572aa4ef40a54aad7ae461.py
cwd: ~/Documents/Sandbox/foo
> ~/.pyenv/versions/3.8.0/bin/python3.8 -m autopep8 --diff ~/Documents/Sandbox/foo/one_file.py.8468da13c1572aa4ef40a54aad7ae461.py
cwd: ~/Documents/Sandbox/foo
> ~/.pyenv/versions/3.8.0/bin/python3.8 -m autopep8 --diff ~/Documents/Sandbox/foo/one_file.py.8468da13c1572aa4ef40a54aad7ae461.py
cwd: ~/Documents/Sandbox/foo
> ~/.pyenv/versions/3.8.0/bin/python3.8 -m autopep8 --diff ~/Documents/Sandbox/foo/one_file.py.8468da13c1572aa4ef40a54aad7ae461.py
cwd: ~/Documents/Sandbox/foo
> ~/.pyenv/versions/3.8.0/bin/python3.8 -m autopep8 --diff ~/Documents/Sandbox/foo/one_file.py.8468da13c1572aa4ef40a54aad7ae461.py
cwd: ~/Documents/Sandbox/foo

Fixed in 2020.4.68499-dev.


[AutoMM] Add document classification pipeline

Description of changes:
This pull request adds a document classification pipeline which can classify scanned document images into appropriate categories. Specifically,
(1) documents are represented as images;
(3) an OCR pipeline is used to obtain their texts and layout information;
(3) document foundation models (or document transformer) such as LayoutLM, LayoutLmv*, are used as the backbone which can be fine-tuned with document classification datasets.
We added

DocumentProcessor: for document processing, e.g., OCR, text, layout, and image feature generation.
DocumentTransformer: a classification wrapper for document foundation models. Text-focused models are also supported.
Tutorial and unit test on document classification.

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

@cheungdaven Feel free to merge when you think it's ready.


Modify openstack provider configuration for CCEE

To expose the APIServer over the public internet, We have to modify Exposure Class in the shoot spec
FloatingIP Network for CCEE is FloatingIP-external-cp-kyma

Based on this PR #898
Issue: #1775
TODO:

[x] implementation
[ ] tests

/retest

/retest


[improvement] Fix Indexed for type checkers

MyPy (rightfully) complains that Indexed(type) should be Indexed[].
This leaves two questions:

Can we come up with a nice syntax for the other arguments for Indexed
How do we do this under the hood. class_getitem is designed for this, and might work if we only cared about mypy, but pydantic also needs to understand what is going on. Maybe a custom Pydantic type?

Yes, good point.
Seems like this guy is relevant for the problem: https://pydantic-docs.helpmanual.io/usage/types/#generic-classes-as-types

Yes, and maybe the implementation of Generic. I think it should be doable for the easiest use but I do not see an easy solution for the parameters to Indexed. Something like Indexed(ASCENDING)[int] might work but seems rather ugly. Including them  in the [] would break typing again.

Hi, this is still happening. I guess the current workaround is to use indexes in the Settings class.
One question, wouldn't it be possible to use the assign syntax instead of typing? Just like Pydantic does with the Field function. So it could look like:
class MyModel(Document, BaseModel):
    indexed: str = Indexed(...)

Is there any static advantage to having the Indexed type? For example, the Optional type is useful because it gives a static semantic for variables that can be None.
Of course, in the case of Pydantic, types also give important runtime information about serialization, on top of the static typing. But if you need something more advanced then you need to use Field.
There are however also the constrained types like conlist etc, which I'm not sure how they actually pass mypy checking.

Apologies for the drive-by comment, as I'm not a beanie user, but this looks like a use-case for Annotated.
class MyModel(Document, BaseModel):
    indexed: Annotated[str, Indexed(...)]

A benefit of this is that other libraries that inspect types don't need to know anything about Indexed to know that the indexed field on this model is a str type.


Usage with GitHub URL dependencies

I am currently using rollup and node resolve to package up a library which uses a GitHub URL for a dependency. Something like:
{
  "name": "foo",
  "version": "0.0.0",
  "dependencies": {
    "module": "user/repo#feature_branch"
  }
}

Running rollup for the first time seemed to work fine. I then pushed an update to the GitHub repo, and ran npm i. The module in node_modules updated to the latest version, but whenever I run rollup the compiled code uses the previous version. Does the plugin cache the source? and if so, how can I invalidate it? I have tried referencing the commit directly (e.g. "module": "user/repo#commit_hash”), but I still get the same outcome.
Is this a bug, or is there a better approach?

My mistake—this was a file renaming issue. Apologies.


Crashes when recording video to the provided location

Describe the bug
Recording video using the Open Camera app to the selected location on a CIFS share provided by this app works fine when taking pictures but crashes instantly when tapping the record button.
To Reproduce
Steps to reproduce the behavior:

Add a CIFS storage location provided by this app
Install and open the Open Camera app
Under the "More camera controls..." settings, turn on "Storage Access Framework" and select  the CIFS location from step 1.
Back out of settings, change to video mode and tap the record button.

Expected behavior
Video is recorded successfully and written to the CIFS share.
CIFS Documents Provider

App Versin: 2.0.2
Connection Settings

Storage Type: SMB2,3(JCIFS-NG)
Authantication: Anonymous
Safe Data Taransfer: no

App Settings

Show notification when opening files: no
Use as local storage: no

App installed device (please complete the following information):

OS: Android 14
Device: Pixel 7a
Client App: Open Camera

Server (please complete the following information):

OS: The ghcr.io/servercontainers/samba Docker image
Device: Ubuntu 22.04 under WSL 2
Server Software: 4.18.9

Additional context
Recording video works using the "Storage Access Framework" to locations from other providers, including Termux.

Also crashes with "Use as local storage: yes" and with "Safe Data Taransfer: yes", tested individually.

I can reproduce the issue too. I see the file name that is being created in the notification in the status bar. Files are created successfully but has 0 bytes. I didn't see the logs yet.
But slightly unrelated, even if this was working, I don't think it is a good idea to directly save a live capture (recording) to SMB share directly, if there are connection drops, or recording in 4k while bandwidth is limited for example, that could render the whole file corrupted.
What I do personally, I have FolderSync app, that syncs all DCIM contents and upload changes to TrueNAS server on scheduled interval, in bulk transfer at once. There is an option to delete a file after it was transferred successfully, but I personally like to keep both and do mirror.

@rpatterson
I was able to reproduce this issue.
I think this problem occurs with dynamic data output streams. Wen I tried using the voice recorder app Record You, it crashed as well.
I don't know any implementation that solves this problem. I'll look into it too.
I'll leave this issue as is.
Let me know if you can solve this problem.


Bias parameter not used in Linear.predictValues()

I am using a logistic regression model with 2 features and a bias.
I would expect the score to be calculated as
w1*x1 + w2*x2 + bias

but looking at https://github.com/bwaldvogel/liblinear-java/blob/99518885860ad5f88f7582c3fb491607352b6dc7/src/main/java/de/bwaldvogel/liblinear/Linear.java#L503 it seems like the bias parameter is never added to dec_values.
Am I right to think the bias parameter should contribute to the score or is my understanding incorrect?

Hello,
Have a look at this line here:
if (model.bias >= 0)
            n = model.nr_feature + 1;

This leads to the bias term being included in the weight vector.
You can double check for your case by writing out your weight vector and see whether it has 2 or 3 entries. I would guess it will have 3.
The code is a bit confusing to Java developers because it is ported from C++, and kept very similar to the original source for maintainability reasons.

Hello,
thanks for your quick reply.
Maybe I should describe my use case a little more.
I'm using liblinear-java only for inference, doing training separately (not using liblinear for training).
My trained model uses 2 features and has e.g. coefficients w1=1 w2=-2 and bias=3.
I'm loading the model from a file that I construct manually and using Linear.predictProbability() directly for inference directly (not using the CLI).
I'd like my prediction score to be calculated as w1*x1 + w2*x2 + bias. For that, I'd expect the right way to write the model file to be
solver_type L2R_LR
nr_class 2
label 1 0
nr_feature 2
bias 3.0000000000000000
w
1.0000000000000000
-2.0000000000000000

and to run the inference with an array of 2 FeatureNodes.
But that doesn't seem to add the bias to the sum. Yes, due to
if (model.bias >= 0)
            n = model.nr_feature + 1;

, n is increased, but bias does not seem to be added to the w vector.
I managed to get expected results by modifying to model from above to
solver_type L2R_LR
nr_class 2
label 1 0
nr_feature 3
bias -1
w
1.0000000000000000
-2.0000000000000000
3.0000000000000000

and then calling Linear.predictProbability() with an array of 3 FeatureNodes (the last one with value of 1). I basically replaced the bias constant with a 3rd feature with a constant value of 1 and w3=<original bias>.
Am I misunderstanding something about how the bias parameter is supposed to work?

@tomas-milata: Could you do me a favor and check if the Java implementation¹ does exactly the same thing as the C++ version?
If yes, please file this issue in https://github.com/cjlin1/liblinear.
¹ the part of the code that is relevant for this issue

Hi! Sorry, I've found a workaround for this, my project is finished and don't have capacity to check this.


Minor changes in docs

Coverage remained the same at 75.244% when pulling fdafcbdbc845d68d950810b7ad6d6e6a35e37bb4 on migueldvb:docs into 110bd3c23baa2841d5af83dac88f437d652fe98c on radio-astro-tools:master.

Neat, thanks for this fix!  I suppose we didn't know how to do this concisely when we wrote the docs.

There are two failures in python2, which I suspect may be because python2 is tied to an older astropy version that doesn't handle WCS as well.... but I'm not really sure.

If https://github.com/radio-astro-tools/spectral-cube/pull/490 passes, I recommend merging that into this one; I hope it will resolve the problem.  My local tests on py2.7 w/np1.13 passed using your modifications.

I have merged #490 and got one error. It seemed to be a change in the indentation of the output from the print(cube) command in http://spectral-cube.readthedocs.io/en/latest/index.html#quick-start.  I hope this build job will pass now.


Incorrect subresources value for Application Configration

I believe the subresources value for Application Configuration should be "configurationStores" instead of "configurationStore".
"configurationStore" doesn't work when creating a private service connection via Terraform.

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

ID: b006a616-2f2f-8ecf-8b80-fd0a3cc62090
Version Independent ID: 92c54dc6-8ddf-b1f7-4a58-d61b8cd7fe25
Content: What is an Azure Private Endpoint?
Content Source: articles/private-link/private-endpoint-overview.md
Service: private-link
GitHub Login: @malopMSFT
Microsoft Alias: allensu

Thanks for the feedback! I have assigned the issue to the doc author to update appropriately.

Information corrected in article on DNS setup.
#please-close


Update emoji list to emoji v15.0.

Context
Update emoji list to emoji version.
Add option to customize emoji list.
Summary
Update emoji list to emoji v15.0.
Change emoji grouping to official grouping.
Add option to customize emoji list.
Change default group icon to lucide icon.
Modify Header Padding to accommodate new grouping size.
Modify Header flex option to fix off-center icons.
Updating npm dependencies.
Fix some bugs.
And more...
To-do

[ ] Due to the change in emoji grouping, users may need to be reminded of the change in the documentation in the future.

User-facing changes
Too much changes. Comment it if you need.
Checklist

[x] I have tested this code to the best of my abilities
[x] I have added documentation where necessary

Hi @lushangkan Thank you for the PR; I will review the changes and merge it as soon as possible.

Seems like I didn't handle skin tones well, I'll fix that later

Fixed unsupported skin color issue, zwj_emoji not supported for now (except Other group)

Hi @lushangkan, thanks again for your incredible effort on this.
PR looks good, just two minor changes needed:

You may want to update the emoji cdn URL as well in constant.ts#L3, the new src should be<EMAIL_ADDRESS>
https://github.com/delowardev/vue3-emoji-picker/blob/c430646adea6727f0b31349ec33629b72a7715f2/src/constant.ts#L3-L4

In emojis.json#10461, could you please update 2642-fe0f to 2641-fe0f? I noticed the male sign emoji doesn't show with the previous code for some reason.

https://github.com/delowardev/vue3-emoji-picker/blob/c430646adea6727f0b31349ec33629b72a7715f2/src/data/emojis.json#L10461

Thank you for checking it out!
I've noticed some new issues in the meantime, I'll get back to you when I'm done fixing them.
Also, emoji added a lot of zwj emoji to switch the gender of the character within the emoji, etc., do you have plans to adapt it?

I think zwj emoji will be a good feature, I will need to check the possibilities.

2. 2641-fe0f

Is the 2641 the ♁ symbol you are referring to? The symbol is [earth symbol] (1)，deprecated in Unicode 1.1, I switched 2642 to 2641 in my device (Windows 11) and it shows up as , and I didn't find this icon in the official list of Unicode either
1
2

2641-fe0f

Is the 2641 the ♁ symbol you are referring to? The symbol is earth symbol，deprecated in Unicode 1.1, I switched 2642 to 2641 in my device (Windows 11) and it shows up as , and I didn't find this icon in the official list of Unicode either
1 2

Hi @lushangkan, thanks again for your incredible effort on this.
PR looks good, just two minor changes needed:

You may want to update the emoji cdn URL as well in constant.ts#L3, the new src should be<EMAIL_ADDRESS>
https://github.com/delowardev/vue3-emoji-picker/blob/c430646adea6727f0b31349ec33629b72a7715f2/src/constant.ts#L3-L4

In emojis.json#10461, could you please update 2642-fe0f to 2641-fe0f? I noticed the male sign emoji doesn't show with the previous code for some reason.

https://github.com/delowardev/vue3-emoji-picker/blob/c430646adea6727f0b31349ec33629b72a7715f2/src/data/emojis.json#L10461

Is the 2641 the ♁ symbol you are referring to? The symbol is earth symbol, deprecated in Unicode 1.1, I switched 2642 to 2641 in my device (Windows 11) and it shows up as , and I didn't find this icon in the official list of Unicode either

Hi @lushangkan, thanks again for your incredible effort on this.
PR looks good, just two minor changes needed:

You may want to update the emoji cdn URL as well in constant.ts#L3, the new src should be<EMAIL_ADDRESS>
https://github.com/delowardev/vue3-emoji-picker/blob/c430646adea6727f0b31349ec33629b72a7715f2/src/constant.ts#L3-L4

In emojis.json#10461, could you please update 2642-fe0f to 2641-fe0f? I noticed the male sign emoji doesn't show with the previous code for some reason.

https://github.com/delowardev/vue3-emoji-picker/blob/c430646adea6727f0b31349ec33629b72a7715f2/src/data/emojis.json#L10461

I see the request<EMAIL_ADDRESS>failed message in the console, which could be a problem with the emoji-datasource-apple repository


Unify union types in the same error

Improves on #5
I started to work on the reporting of union types errors. It's not yet finished, but I'd like some feedback on the code (I think my editor applied automatic formatting btw 🤦♂) and also on how the errors look.
Here are some examples one the errors, and what's still missing.
t.keyof
io-ts suggests to use t.keyof for union types of only string literals.
const OneOf = t.interface({
    oneOf: t.keyof({ a: null, b: null, c: null }),
});

report(OneOf.decode({ oneOf: '' }));

That still reports as before:
Expecting "a" | "b" | "c" at oneOf but instead got: "A".

Literals unions (using t.union):
const StringUnion = t.interface({
    stringUnion: t.union([t.literal('a'), t.literal('b'), t.literal('c')]),
});
report(StringUnion.decode({ stringUnion: 'A' }));

Reports with the new format (instead of showing 3 different errors):
Expecting one of:
    "a"
    "b"
    "c"
at stringUnion but instead got: "A".

Things to improve:
There are some things that should still be improved. For unions of other types, I need to do some improvements on the usage of the context to get proper errors.
const Unions = t.interface({
    interfaceUnion: t.union([
        t.interface({ key: t.string }),
        t.interface({ code: t.number }),
    ]),
});

For such union, the following input would give the error one expects:
report(Unions.decode({ interfaceUnion: 'name' }));

Expecting one of:
    { key: string }
    { code: number }
at interfaceUnion but instead got: "name".

But for the case when there's more context of the value:
report(Unions.decode({ interfaceUnion: {} }));

The error is wrong 😕
Expecting one of:
    string
    number
at interfaceUnion but instead got: undefined.

As a side note, I think it would be beneficial to add assertions to the tests, since changes such as this PR would require several cases being checked.
Also I could add prettier (to prevent what happened with my changes).
Didn't want to go ahead and add such stuff since it's not my call 😅 But I'm open to make such additions if you think it's beneficial.

Happy @gillchristian, really sorry for taking so long to get back to you on this.
I'm not using io-ts at the moment and I'm finding it really hard to remember how everything fits together. It might be better if I just added you add a contributor to this repo, or you could maintain a fork (I'd be happy to link from my repo to yours)?

No worries. I parked the work on this PR from my side anyways 😴
If you are fine with having a contributor I'd prefer that since a fork would be misleading. I'm also happy to maintain the project in general, since it's already the one listed in fp-ts / io-ts websites better to keep this one alive, wdyt?

@gillchristian I've sent you an invite :-)

Finally put some time into this. The errors look decent now.
There could be some more work into making the formatting smart: eg. if the provided value is "closer" to the type of one of the branches of the union, then only report to that one. But for now is good enough I guess.

I made a PR on your repo that merges in the current master and converts your tests to the new test format FYI!

FYI: I'm not sure why, but I tried this branch decoding a codec of mine with some garbage data, and got a lot of duplicate values for the union:
// codec looks roughly like this
export const orgData = t.intersection([
  t.type({
    // ... a bunch of other entries including several union types
    revenueAmt: t.union([NumberFromString.pipe(Int), t.null])
  }),
    t.type({ id: t.string }),
    t.partial({
      customerInfo: customerInfoCodec // also a fairly complex type
    })
])

Result
Expecting one of:
    pipe(NumberFromString, BoundedInt)
    null
    pipe(NumberFromString, BoundedInt)
    null
    pipe(NumberFromString, BoundedInt)
    null
    pipe(NumberFromString, BoundedInt)
    null
    pipe(NumberFromString, BoundedInt)
    null
    pipe(NumberFromString, BoundedInt)
    null
    pipe(NumberFromString, BoundedInt)
    null
at revenueAmt but instead got: "5.24".

@osdiab I think that is because it adds errors for every branch or something like that.
I need to get this PR in better shape, I'll take a look at your changes on the tests and pick up the work I was doing.

any way I can help move this along? I'd love to get this into my prod codebase :) I can take a look in a couple days and make some changes if you're too busy to sink time into it.

I'll do some progress on Sunday & Monday (holiday here) and push my progress in case I do not finish. Wdyt?

it would make error logs at my company so much more readable haha

Same reason why I started this PR :)

@osdiab I guess it should be good to go know.
We certainly can iterate on improvements (eg. only show the error from the type of the union that is closer). But for now I think it's fine like this.
Please check the tests to see how errors are formatted in different cases


Can't enter data on form fillable pdf

I've created a FF pdf using PDF Escape, uploaded it into the Forge Asset Library and linked it to PDF Pager in Foundry. The pdf is assigned as the CS and shows up when a character is created but it won't allow me to enter any data. I click on the fillable area, its background turns white but no cursor is shown in the editable area and it doesn't see any key strokes I make for the data. A friend of mine says PDF Pager is working for him with no issues. BTW, the pdf works fine outside of Foundry. What am I missing here?? I feel like I'm not installing something correctly...

If you open the PDF in a normal journal page (with PDF Pager module disabled) can you edit it there? On 4 Mar 2023 13:20, Meliath1742 @.***> wrote:
I've created a FF pdf using PDF Escape, uploaded it into the Forge Asset Library and linked it to PDF Pager in Foundry. The pdf is assigned as the CS and shows up when a character is created but it won't allow me to enter any data. I click on the fillable area, its background turns white but no cursor is shown in the editable area and it doesn't see any key strokes I make for the data. A friend of mine says PDF Pager is working for him with no issues. BTW, the pdf works fine outside of Foundry. What am I missing here?? I feel like I'm not installing something correctly...
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you are subscribed to this thread.Message ID: @.***>

Its odd. As a Journal entry PDF and PDF Pager disabled, a few of the fillable areas work, but most do not. I can see the flashing cursor in the fillable areas, but only a few allow me to actually enter data.

What browser are you using?
Also, what happens if you open a browser (not containing Foundry) and drag the PDF into it?  (This should use your browser's built-in PDF support)?

I'm using Chrome. I'll have to try the pdf-browser and get back with you.
On Sat, Mar 4, 2023 at 5:44 PM Farling @.***> wrote:

What browser are you using?
Also, what happens if you open a browser (not containing Foundry) and drag
the PDF into it? (This should use your browser's built-in PDF support)?
—
Reply to this email directly, view it on GitHub
https://github.com/farling42/fvtt-pdf-pager/issues/53#issuecomment-1454910776,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4NHPIZX6I6GUABQNN55RALW2PAT3ANCNFSM6AAAAAAVPROYBQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

It might be worth checking what extensions you have enabled in Chrome - if the PDF is editable on another player's computer.

Thanks, I'll check it out.
On Sat, Mar 4, 2023 at 6:25 PM Farling @.***> wrote:

It might be worth checking what extensions you have enabled in Chrome - if
the PDF is editable on another player's computer.
—
Reply to this email directly, view it on GitHub
https://github.com/farling42/fvtt-pdf-pager/issues/53#issuecomment-1454920380,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/A4NHPI27VRELOSYQRAT4TETW2PFN3ANCNFSM6AAAAAAVPROYBQ
.
You are receiving this because you authored the thread.Message ID:
@.***>

It is also worth checking version 0.39.1 to see if that makes any difference.

Yeah, I've tried using Form Fillable pdfs as well. I can edit all the fields, no problem, but I cannot find a way to save the changes, so it always just reverts to the base pdf with none of the information that I added.

If you are using PDF Pager and are using a PDF as an Actor sheet, then when you change a field in the fillable PDF the new value is immediately stored on the Actor.

I am using PDF Pager and as an Actor sheet. Then I took the time to fill in every field, then closed the actor sheet. I reproduced this bug with several different PDFs in multiple actors. All changes were erased. Tried on both Forge and my local Foundry program, same thing occured. I am going to try removing all other modules, in case there's a conflict.

I now tried with a different system from before; Simple World Builder instead of Sandbox and it's now working. interesting.

If you open your browser console and switch the logging level to All, then you should see messages appear whenever you modify a value in the PDF. It might be generating an error for the fields which don't appear to be getting saved.

Which game system are you using?

Closing due to lack of response


finer control over treesitter integration (italicization, etc)

First off, this colorscheme is really awesome! =) I'd just like to have the option to configure how the treesitter integration behaves. not sure if this is already doable since it's not documented in the readme. Examples below are written in typescript.
setup with integrations.treesitter = true

setup with integrations.treesitter = false

I much prefer the syntax highlighting with treesitter enabled, but I'm not really a fan of the italicization for object properties & function calls. It can be a bit jarring for me if an object has a lot of props, especially deeply nested ones.
I understand that the italicization is hardcoded here but am not sure how this can be configured without manually overriding file in the cloned repo. Having a way to control this would be really good imo, especially considering how popular treesitter is. Thanks!

Every highlight group can be customized: https://github.com/catppuccin/nvim#overwriting-highlight-groups
Let me know if you need help using the API :)

Thank you for pointing this out! Some help would be great :)
For example, if i want to remove italicization for this highlight group but keep the color the same:

How should i go about this with the API you provided?

AH nevermind, after some messing around i got it to work. Big thanks!! Love this colorscheme! ;)


[Task] : Instrument server heap monitoring and create baseline for tracking memory consumption

Reopening to track updates on changes unrelated to code.

Implemented in both release and production. Documented notes for this here.


Perform the entire CircleCI workflow on tags.

This should make it such that CircleCI runs on tag builds (and thus can push to npm).

Nixing in favor of not being on a fork.


The review app stops compiling Sass after encountering an error

Description of the issue
If you make a change that causes an error in Sass compliation whilst using the review app, the build process for the review app crashes and is not restarted.
This means that even if you fix the change, you need to stop the process and restart it (Ctrl + C then re-run npm start).
Steps to reproduce the issue

Run npm start
Edit *.scss file to cause a Sass or PostCSS error

Actual vs expected behaviour
Expected behaviour:
The error is outputted on the console and the watch task for the review app build continues to retry compilation when further changes are made
Actual behaviour:
The error is outputted on the console but the watch task for the review app build crashes.
Environment (where applicable)

Operating system: macOS 13.5.1
Browser: N/A
Browser version: N/A
GOV.UK Frontend Version: N/A (happening on main branch)

Will be fixed by https://github.com/alphagov/govuk-frontend/pull/4239 and tested in https://github.com/alphagov/govuk-frontend/pull/4240


Installed app crashes & doesn't open

I tried merging Lightroom (9.5.0) and everything went well with the merging & signing. The app even gets installed but as soon as I open the app, a black screen pops up for split second & then nothing.
I've tried multiple methods, the default merging behaviour, selecting all the right things according to my device, letting antisplit M itself automatically select things for my device.
PS: the said app gets installed successfully if I use SAI & it even works fine. I'm using Antisplit M just so I can use the ReVanced patches
PPS: Yes, I tried the app even before patching with ReVanced.

The problem is that Adobe added Pairip/Google加固 Integrity to Lightroom since v9.4.2, which checks signature verification among other things to check if the APK was modified. There are ways to bypass it, but it's not the job of AntiSplit app. If you want a version newer than 9.4.1 you should look for alternative patched sources.

The problem is that Adobe added Pairip/Google加固 Integrity to Lightroom since v9.4.2, which checks signature verification among other things to check if the APK was modified. There are ways to bypass it, but it's not the job of AntiSplit app. If you want a version newer than 9.4.1 you should look for alternative patched sources.

Hypocrite Google, taking privacy & security seriously when it benefits them 🥲


CacheUnmanagedCertificatePEMFile rejects duplicate certs, without accounting for tags

What version of the package are you using?
v0.17.2
What are you trying to do?
I originally ran into this issue when porting an existing nginx setup to Caddy:
I have a pre-existing LE certificate, with multiple SANs names. This certificate is matched based on tags. When CacheUnmanagedCertificatePEMFile encounters a certificate it has already loaded, it rejects it ("certificate already cached"), which ignores any "additional" tags assigned to the certificate.
What steps did you take?

In Caddy, I create a config similar to:
sub1.domain {
    tls /var/lib/acme/live/sub1.domain/fullchain /var/lib/acme/live/sub1.domain/privkey
}
sub2.domain {
    tls /var/lib/acme/live/sub2.domain/fullchain /var/lib/acme/live/sub2.domain/privkey
}

Note that the filepaths aren't the same, even though the certificates actually are identical. (The subdomain directories actually point to the same on-disk directory, since both subdomains are included in the certificate.)
From this, Caddy generates something like:
"tls": {
    "certificates": {
        "load_files": [
            {"certificate": "/var/lib/acme/live/sub1.domain/fullchain", "key": "/var/lib/acme/live/sub1.domain/privkey", "tags": ["cert1"]},
            { "certificate": "/var/lib/acme/live/sub2.domain/fullchain", "key": "/var/lib/acme/live/sub2.domain/privkey","tags": ["cert0"]}
        ]
    }
}

Alternatively, as (rough) code:
package main

import (
        "context"
        "crypto/tls"
        "errors"
        "fmt"
        "net"

        "github.com/caddyserver/certmagic"
)

func main() {
        cfg := certmagic.NewDefault()

        if err := cfg.CacheUnmanagedCertificatePEMFile(context.TODO(), "/var/lib/acme/live/sub1.domain/fullchain", "/var/lib/acme/live/sub1.domain/privkey", []string{"cert0"}); err != nil {
                fmt.Println("cert0:", err)
        }
        if err := cfg.CacheUnmanagedCertificatePEMFile(context.TODO(), "/var/lib/acme/live/sub2.domain/fullchain", "/var/lib/acme/live/sub2.domain/privkey", []string{"cert1"}); err != nil {
                fmt.Println("cert1:", err)
        }

        result := func(t *tls.Certificate, err error) {
                if err != nil {
                        fmt.Println("failed:", err)
                } else {
                        fmt.Println("cert:", t.Leaf.Subject)
                }
        }

        fakeConn, _ := net.Dial("udp", "[::1]:1") // XXX: just so the log statement in GetCertificate doesn't crash

        cfg.CertSelection = certFromTag("cert0")
        result(cfg.GetCertificate(&tls.ClientHelloInfo{
                ServerName: "sub1.domain",
                Conn:       fakeConn,
        }))

        cfg.CertSelection = certFromTag("cert1")
        result(cfg.GetCertificate(&tls.ClientHelloInfo{
                ServerName: "sub2.domain",
                Conn:       fakeConn,
        }))
}

type certFromTag string

func (tag certFromTag) SelectCertificate(hello *tls.ClientHelloInfo, certs []certmagic.Certificate) (certmagic.Certificate, error) {
        for _, c := range certs {
                for _, t := range c.Tags {
                        if string(tag) == t {
                                return c, nil
                        }
                }
        }
        return certmagic.Certificate{}, errors.New("No matching certificate")
}

The above config and/or code example results in the certificate for the second domain not being found, without any error being returned by CacheUnmanagedCertificatePEMFile.
What did you expect to happen, and what actually happened instead?

The certificate should be found; this scenario works fine in other webservers.
How do you think this should be fixed?

Potentially, tags should be added to the existing certificate.
Or deduplication should not be just on certificate hash, but also account for tags.
Please link to any related issues, pull requests, and/or discussion

Bonus: What do you use CertMagic for, and do you find it useful?

That's a good point. I'll look into this!

I think this should be fixed now, in a46420b. Can you test and verify?


Add note about escaping characters with backslash

Originally filed by Andrewery https://github.com/MicrosoftDocs/terminal/pull/134/files

Docs Build status updates of commit ddd6ba2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

TerminalDocs/customize-settings/interaction.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

Docs Build status updates of commit ddd6ba2:
:white_check_mark: Validation status: passed

File
Status
Preview URL
Details

TerminalDocs/customize-settings/interaction.md
:white_check_mark:Succeeded
View

For more details, please refer to the build report.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel

@mattwojo
This commit doesn't fix the main problem of my commit in #134 : The actual "Default value" line has again a syntax problem. The actual default value string of the wordDelimiters setting cannot be "as-is" cut-pasted in the JSON configuration file. Some characters must be escaped with the backslash.
If you don't write the exact "JSON-compatible" line, maybe the "default value" title should be replaced by "default delimiters".

@mattwojo
This commit doesn't fix the main problem of my commit in #134 : The actual "Default value" line has again a syntax problem. The actual default value string of the wordDelimiters setting cannot be "as-is" cut-pasted in the JSON configuration file. Some characters must be escaped with the backslash.
If you don't write the exact "JSON-compatible" line, maybe the "default value" title should be replaced by "default delimiters".

Ahh. My bad @anderewrey -- I see what you were doing now. Filed another PR: https://github.com/MicrosoftDocs/terminal/pull/232

Ahh. My bad @anderewrey -- I see what you were doing now. Filed another PR: https://github.com/MicrosoftDocs/terminal/pull/232

Thanks for pointing this out. I've got Friday brain. That fix look ok?

Thanks for pointing this out. I've got Friday brain. That fix look ok?

Thanks for pointing this out. I've got Friday brain. That fix look ok?

No problem @mattwojo.
Have a good day.

Thanks for pointing this out. I've got Friday brain. That fix look ok?

No problem @mattwojo.
Have a good day.


FIX-#5985: BUG: ArrowPeriodType and ArrowIntervalType are not supported by HDK

…ed by HDK

What do these changes do?

[x] first commit message and PR title follow format outlined here

NOTE:  If you edit the PR title to match this format, you need to add another commit (even if it's empty) or amend your last commit for the CI job that checks the PR title to pick up the new PR title.

[x] passes flake8 modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] passes black --check modin/ asv_bench/benchmarks scripts/doc_checker.py
[x] signed commit with git commit -s
[x] Resolves #5985
[x] tests added and passing
[ ] module layout described at docs/development/architecture.rst is up-to-date

@AndreyPavlenko, please title PRs with a description what has been done in future. It is not clear what has been done when you title FIX-#Issue: "The issue title".