MIC-328 WIP

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

Project coverage is 84.62%. Comparing base (b7d4b40) to head (f0094ce).

Additional details and impacted files
@@             Coverage Diff              @@
##               main      #73      +/-   ##
============================================
+ Coverage     84.17%   84.62%   +0.44%
- Complexity      489      491       +2
============================================
  Files           108      109       +1
  Lines          1795     1769      -26
  Branches         62       64       +2
============================================
- Hits           1511     1497      -14
+ Misses          259      247      -12
  Partials         25       25

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Return correct error code on create-producer/consumer is not complete yet

Motivation
When broker receives multiple create_producer request with same producer-id before it completes producer-creation, it returns UnknownError which misleads client while retrying the request.
Modifications
if client times out before broker successfully creates producer and if client retries to create producer then broker should return ServiceNotReady instead  UnknownError (if broker is still creating the producer)  so, client can again retry on this recoverable error.
Result
Broker returns ServiceNotReady error if it producer/consumer creation is not complete so, client can retry on this known error-code.

Looks good, nice catch! Can you also verify the return code in the mocked unit test for the producer/subscribe timeout? Also, probably this should go on 1.16 release, right?

@merlimat added the testcases for this error-code scenario.


Automated site quota management

If is mentioned that if we will use automated site quota management, then all sites will get 25TB of storage quota. What will happen in a scenario where there are thousands of sites and each site will have a quota limit of 25 TB but then total SP quota becomes less than as compared to no. of sites x 25TB and in actual all sites are using very less space (not full 25 TB). Could you please clarify this?

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

ID: d657793d-ad57-3801-6586-9c36b949386f
Version Independent ID: ce570a07-c861-b43c-67c3-088780ee8fec
Content: Manage site storage limits - SharePoint Online
Content Source: SharePoint/SharePointOnline/manage-site-collection-storage-limits.md
Service: sharepoint-online
GitHub Login: @kaarins
Microsoft Alias: kaarins

@prashant1380 Thank you for submitting feedback and contributing to the docs. We are currently investigating this.

Hi @prashant1380, thank you for your feedback.
In this case, you should monitor your storage and when you are running out of storage for your tenant/organization, you should buy more:
https://docs.microsoft.com/microsoft-365/commerce/add-storage-space

Thanks for your comment. But if we have not utilized the full quota then why we need to buy extra? Lets take this example:

Total quota available for SPO tenant = 10 TB (with automated quota management)
Due to automated quota management : 10 SPO sites x 25 TB = 250 TB
Actual space utilization of each site: 10 SPO sites x ~1 GB =  ~5 GB
So based on this given example, do you think we have to buy 240 TB extra space? Because in actual we are using only 5GB out of available 10 TB

@prashant1380 you need to buy extra storage if you reach your tenant limit. In your example, you didn't reach it yet. Just one correction: "Actual space utilization of each site: 10 SPO sites x ~1GB = ~10GB"
Similar example but in this case you reach the quota limit:

Total quota available for SPO tenant = 10TB (with automated quota management)
Due to automated quota management : 10 SPO sites x 25TB = 250TB
Actual space utilization of each site: 10 SPO sites x ~1TB = ~10TB

This information is in the paragraph:
"By default, your SharePoint storage is available in a central pool from which all sites can draw. You, as a global or SharePoint admin, don't need to divvy up storage space or reallocate space based on usage. That's all handled automatically: sites use what they need when they need it. If you previously set storage limits manually and switch to using pooled storage, SharePoint resets all the limits to 25 TB (25600 GB). (Note that the total storage for your organization might be less than 25 TB.)"

@prashant1380 Thank you for submitting feedback. We understand that this issue has been resolved.
Please feel free to re-open this issue if there is a specific area of the docs that we can improve or make better. Thank you.


Replace Selenium with Cypress in the testable-projects-fcc Repo

Currently the automated test suite in the testable-projects-fcc repo uses Selenium to run tests against each of the projects.
Because it can be difficult to keep Selenium and the web drivers for each browser in sync, we'd like to replace it with Cypress. Cypress now has support for Chrome and Firefox, and would allow us to pin browser versions so we don't have browser/web driver version issues running the tests locally with yarn test or with GitHub actions.
Right now there seems to be two main parts of the test runner: a Mocha test at /test/projects.js that goes through each project and feeds the local file path to Selenium, and Selenium logic at /test/automate/automate-utils.js .
Right now, Selenium is just used to open each local project in the browser, click the "Run Tests" button, wait for the tests to run, and click on the "Tests" button to see the results. If any of the tests fail, the error messages are taken from the dropdown that appears after the "Tests" button is clicked again and fed back to Mocha to show in the console.
If we use Cypress to test each project, we should be able to replace Selenium, and the Chrome and Gecko web drivers.

Let's say after you have written a test for this in Cypress how would you test if your written test works?

I would like to help. How can I help?

Hi @ManasMahanand, thanks for your patience. We'd certainly welcome the help. Feel free to explore the testable-projects-fcc repo and let us know if you have any questions.
@Sembauke, thanks for the additional info. While it would be nice to test the projects on CodePen for extra assurance, we don't currently do that with Selenium.
All of the code that's in the example CodePen projects are in the testable-projects-fcc repo and can be run locally. The goal here would just be to replace the Selenium test runner with Cypress instead.
Just to give a bit of context, the testable-projects-fcc repo is used for two things: to develop the CDN loaded test suite for the Responsive Web Design, Front End Libraries, and the D3 projects, and to track the code for all of those example projects.
If there's a bug in one of those example projects like the Tribute Page, we should update the project in the testable-projects-fcc repo, then once those changes are merged, copy them over to the example CodePen project.
Or if we need to make a change to the CDN loaded test suite, we can run those changes against the example projects in the repo (which should mirror what's on CodePen), and ensure those changes work against valid projects.
Hope that helps, and sorry if it's a bit confusing. It all gets a bit messy because we're discussing testing tests haha.

Oh! I misunderstood your original comment. I had thought you wanted to use Cypress to test Camper's code on codepen, or locally. I think @Sembauke thought the same.
What you would like to do is replace the tests that tests the tests that run on the Campers code... Got it.

I've been looking through the repo, and playing around with stuff to understand how it all works right now. One thing I'm confused about:
Under package.json, "scripts" you have "test" which is what is run when I run yarn test. And that runs "mocha".
But when I run yarn test, it also runs eslint, and some prettier stuff before it runs mocha. I don't get why it's doing that, and also how does mocha know to run projects.js under test?

@ManasMahanand, sorry for the initial confusion.
But right, what we want to do is use Cypress to test the example projects in the testable-projects-fcc repo against the CDN loaded test suite, which is in the same repo.
About the eslint and prettier stuff that runs before the test, those are being triggered by pretest in package.json. I believe that's just an npm pre hook that runs before whatever script name comes after it.
So if instead of pretest it was predevelop, when you run yarn develop, npm would run all that linting and prettier stuff before the develop script.
As for how Mocha knows to run project.js, I think the default behavior is for Mocha to look through everything in the /tests directory and try to run those.


Feature: Implement .transform(X) in the lasagne wrapper to extract hidden representations

This allows you to call .transform(X) on a trained model (lasagne wrapper) to retrieve a transformed feature representation at an intermediate layer of your choice. Particularly useful to inspect your learned features or to stack your model with a different classifier. The functional MNIST test has been extended with an example of the latter, with a SVM on top of the neural network, using its last hidden representation as transformation layer. (This increases accuracy here from 0.877 to 0.903.)

I like the idea a lot, but was wondering if the implementation could maybe be done in a way that all necessary changes are local to the transform method (apart from the parameter to __init__).
Another point is that if we're going to store transform_iter_ on self, we'll have to remove it in __getstate__.

The current implementation closely follows how predict(X) is implemented with self.predict_iter_, so I think it makes sense to thread transform(X) equally and precompute and store the iterator. Especially since a major use case for using the neural net as a feature extractor is chaining it to another classifier, so that the same reasoning that applies to predict(X) (e.g. performance) should also apply to transform(X).
The proposed implementation has one downside, the transformation layer has to be chosen when the NeuralNet is created. But this similar to a RandomForestClassifier in Sklearn, which can transform features to keep the n best features and n is chosen at initialisation. We could have a update_transform_layer(name) if that is a problem.
Yep, I missed getstate, should be included there. And while we're at it, self.transform_layer should probably be renamed to self.transform_layer.

Apparently Travis encountered a time-out (?). What is the maximum execution length and was that ever a problem? Scaling down form 5 epochs to 4 epochs in the NN or limiting the number of samples could help to scale down on testing time. I could also chain something else than a SVM, but the NN+SVM combo is what you can find in literature, so its a good example.

Is this slated to be merged in soon?  If not, is there a different way to get the output of an intermediate layer in the interim?  Thanks!

@edz504: Look for "Theano layer functions and Feature Extraction" in this tutorial.

Thanks for the quick and informative response as always!
On Wed, Oct 7, 2015 at 7:21 AM Daniel Nouri<EMAIL_ADDRESS>wrote:

@edz504 https://github.com/edz504: Look for "Theano layer functions and
Feature Extraction" in this tutorial
http://blog.christianperone.com/2015/08/convolutional-neural-networks-and-feature-extraction-with-python/
.
—
Reply to this email directly or view it on GitHub
https://github.com/dnouri/nolearn/pull/89#issuecomment-146159638.

Sorry for leaving this stale for such a long time.
The equivalent is now implemented by #196, though it's using the method name get_output and you have to pass in the name of the layer explicitly, rather than having that a parameter of NeuralNet.  The speed concerns were also addressed.


Is there a maxWidth set on the search bar?

I'm building a landscape iPad app and am using the searchbar at full width, it appears to max-out at 1000px

Yes, see here https://github.com/umhan35/react-native-search-bar/blob/master/RNSearchBar.m#L18
Probably you can find a workaround solution there.

Okay, thanks for the that.
Is there any reason you settled on 1000, why not 1024?

Because I was only developing a portrait iPhone app. I think we can programmingly get the width of the device, something like this: http://stackoverflow.com/a/3655117/390014. I don't have an iPad or a bigger device to test on. But you are welcome to try and contribute :)


Tensors outer product is not easy

I want to get the outer product between tensors with different shapes.
I give here a representative example of what I want, with Numpy.
import numpy as np
a= np.linspace(1,2,12).reshape((2,3,2))
b= np.linspace(3,4,4).reshape((2,2))
b=b.reshape(2,1,2)
result=a*b
print(result)

I get
[[[ 3.          3.63636364]
  [ 3.54545455  4.24242424]
  [ 4.09090909  4.84848485]]

 [[ 5.66666667  6.54545455]
  [ 6.33333333  7.27272727]
  [ 7.          8.        ]]]

If I "translate" this code into java with ND4j
INDArray a= Nd4j.linspace(1,2,12).reshape(2,3,2);
INDArray b= Nd4j.linspace(3,4,4).reshape(2,2);
b=b.reshape(2,1,2);
a.muli(b);
System.out.println(a);

I get
Exception in thread "main" java.lang.IllegalStateException: Mis matched lengths: [4] != [12]

Fine, I need to call the broadcast by myself.
INDArray a= Nd4j.linspace(1,2,12).reshape(2,3,2);
INDArray b= Nd4j.linspace(3,4,4).reshape(2,2);
b=b.reshape(2,1,2).broadcast(2,3,2);
a.muli(b);
System.out.println(a);

I get
[[[3.00, 3.27],
  [3.55, 4.24],
  [4.55, 4.85]],

 [[5.67, 6.00],
  [6.33, 7.27],
  [7.64, 8.00]]]

Not ok. I check the code, the broadcast func is not the solution. #994 #1101
So I do the broadcast by myself :
INDArray a= Nd4j.linspace(1,2,12).reshape(2,3,2);
INDArray b= Nd4j.linspace(3,4,4).reshape(2,2);
b=Nd4j.concat(0,b,b,b);
a.permutei(1,0,2).muli(b).permutei(1,0,2);
System.out.println(a);

I get
[[[3.00, 3.64],
  [3.55, 4.24],
  [4.09, 4.85]],

 [[5.67, 6.55],
  [6.33, 7.27],
  [7.00, 8.00]]]

Works fine, but what about the perfs ?
Numpy : ~ 1.239776611328125e-05 s
ND4J: ~ 0.028957072 s

NB: I tried with bigger tensors, perfs are bad :/
An other way :
INDArray a= Nd4j.linspace(1,2,12).reshape(2,3,2);
INDArray b= Nd4j.linspace(3,4,4).reshape(2,2);
for(int i=0;i<a.tensorssAlongDimension(0,2);i++){
    a.tensorAlongDimension(i,0,2).muli(b);
}
System.out.println(a);

Works !... but perfs are worse, even with parallelisation.
So, what about the BroadcastMulOp. Since the first and third dims of a are matching the dims of b,
INDArray a= Nd4j.linspace(1,2,12).reshape(2,3,2);
INDArray b= Nd4j.linspace(3,4,4).reshape(2,2);
Nd4j.getExecutioner().exec(new BroadcastMulOp(a, b, a, new int[]{0,2}));
System.out.println(a);

I get
[[[ 3.00,  3.64],
  [13.00, 16.97],
  [15.00, 19.39]],

 [[ 5.67,  6.55],
  [ 1.73,  1.82],
  [ 1.91,  2.00]]]

Wrong !
Let's do it work :
INDArray a= Nd4j.linspace(1,2,12).reshape(2,3,2);
INDArray b= Nd4j.linspace(3,4,4).reshape(2,2);
a=a.permute(0,2,1).reshape(4,3);
Nd4j.getExecutioner().exec(new BroadcastMulOp(a, b, a, new int[]{0}));
a=a.reshape(2,2,3).permute(0,2,1);
System.out.println(a);

yes ! but the perfs... #1132
I have done several benchmarks with these 3 last working implementations. Depending on size of tensors, common dims etc... That is never the same implementation that performs the better !
Cuda is a little faster than native
Numpy is at less 10 time faster than my ND4j implementations.
So any ideas ? Is BroadcastMulOp supposed to work with tensors of order greater than 2 ?

We have Nd4j.tensorMmul FYI.
Either way you really shouldn't be using for loops. We do everything in c++ like they do. On a lot of things we're faster.

I'll take a look on tensorMmul, don't know how it works and already find a bug :/
Yes I know about the loop, it's just for demo purpose.

Itd similar to np.tensordot. Could you be less vague about finding a bug
though? That doesnt help either of us.
On Aug 24, 2016 00:03, "Jajawah"<EMAIL_ADDRESS>wrote:

I'll take a look on tensorMmul, don't know how it works and already find a
bug :/
Yes I know about the loop, it's just for demo purpose.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/deeplearning4j/nd4j/issues/1229#issuecomment-241761320,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABF18mKyLFv3mjFRcqA2YHFvnrk08mWAks5qiwurgaJpZM4Jq_J-
.

sure, I was writing #1230

Thanks!
On Aug 24, 2016 00:08, "Jajawah"<EMAIL_ADDRESS>wrote:

sure, I was writing #1230
https://github.com/deeplearning4j/nd4j/issues/1230
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/deeplearning4j/nd4j/issues/1229#issuecomment-241763085,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABF18nljJvRhLJSi6-F07yclA9daZXIxks5qiwzrgaJpZM4Jq_J-
.

btw, tensordot is inner product, I want an outer, without summation

Yeah just saw that sorry about that misread :(.

@Jajawah
Yeah - this is something we are thinking about. Maybe add a couple more ops that will make life easier regarding slice operations with rank >2.
So this gives better timing. I am seeing a really big jump and it would be kind what would happen under the hood anyway minus the call to the native code and bundled together.
    a= Nd4j.linspace(1,2,j*m*k).reshape(j,m,k);
    b= Nd4j.linspace(3,4,j*k).reshape(j,k);
    myb = b.repeat(0,new int[] {m}).reshape(a.shape());
    a.muli(myb);

I repeat values along the dimension and so no more broadcast. It ends up as the same thing as the concat in your post but takes the number of repeats as an argument.
Since we have another issue open on performance and another one for broadcast I am closing this.
Thanks!

@eraly
I test repeat() on big tensors, and the perfs are slow. I guess repeat() is doing an hard copy, while I need only to simulate the shape to do the product.
Otherwise, I think that BroadcastMulOp is the answer to my issue, but when I run Nd4j.getExecutioner().exec(new BroadcastMulOp(a, b, a, new int[]{0,2})); I get odd results, as if the b tensor was multiplied by himself...

I agree. The BroadcastMulOp would be great here...


Following the closed issue #1824, apparently not resolved : [Microsoft.EdgeWebView2Runtime]Unable to install, error code<PHONE_NUMBER>

Brief description of your issue
Hello,
i have the same issue right now
winget upgrade Microsoft.EdgeWebView2Runtime
Found Microsoft Edge WebView2 Runtime [Microsoft.EdgeWebView2Runtime] Version 97.0.1072.76
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Successfully verified installer hash
Starting package install...
Installer failed with exit code:<PHONE_NUMBER>
winget --info
Windows Package Manager (Preview) v1.2.3411-preview
Copyright (c) Microsoft Corporation. All rights reserved.
Windows: Windows.Desktop v10.0.19044.1469
Package: Microsoft.DesktopAppInstaller v1.17.3411.0
Cheers
Steve
Steps to reproduce
winget upgrade Microsoft.EdgeWebView2Runtime
Expected behavior
anything else than a : Installer failed with exit code:<PHONE_NUMBER> ...
Actual behavior
Installer failed with exit code:<PHONE_NUMBER>
Environment
winget --info

Windows Package Manager (Preview) v1.2.3411-preview
Copyright (c) Microsoft Corporation. All rights reserved.

Windows: Windows.Desktop v10.0.19044.1469
Package: Microsoft.DesktopAppInstaller v1.17.3411.0

The Edge team was confused why I had to put that key into the manifest, so I removed it in the latest update to Edge WebView2. Turns out that was a bad idea :(
Anyway, it will be hopefully resolved once https://github.com/microsoft/winget-pkgs/pull/43955 is merged. After that manifest is merged, can you try again?

Well, @jedieaston, I was thinking of removing previous versions of browsers since most of them auto-update themself in the background. (atleast we can think about beta/dev channels of brave)

If the download links stay around there’s no reason to remove them IMO, if someone wants to download an old browser winget should be able to do it. Maybe something to open a discussion about.

Hello jedieaston,
I appologize ! i have just noticed your modification is not include in the v1.2.3411-preview of winget-cli i have installed and in which i have this current problem.
Sorry guys, I should have done it better !
i close this issue
Steve

So how do we (the users) fix this issue? I keep getting it

The issue wasn't resolved by that PR so I rolled it back. Sorry.
We're waiting on either the Edge team to fix their installer or for https://github.com/microsoft/winget-cli/issues/1885 to be resolved (that will take a long time, so hopefully the first one)

Ok since there are a few issues around this, Microsoft.EdgeWebView2Runtime requires to be installed with terminal ran as Administrator because it does not self elevate.
This will be resolved once winget-cli supports the field ElevationRequirement: elevationRequired.
as user:
PS M:\> winget install Microsoft.EdgeWebView2Runtime
Found Microsoft Edge WebView2 Runtime [Microsoft.EdgeWebView2Runtime] Version 98.0.1108.43
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://msedge.sf.dl.delivery.mp.microsoft.com/filestreamingservice/files/257e16c7-6b27-41bc-b212-64d0a9418970/MicrosoftEdgeWebView2RuntimeInstallerX64.exe
  ██████████████████████████████   116 MB /  116 MB
Successfully verified installer hash
Starting package install...
Installer failed with exit code:<PHONE_NUMBER>

Upgrade with administrator and without the uninstallPrevious switch
PS M:\> winget upgrade Microsoft.EdgeWebView2Runtime
Found Microsoft Edge WebView2 Runtime [Microsoft.EdgeWebView2Runtime] Version 98.0.1108.43
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Successfully verified installer hash
Starting package install...
Successfully installed

Additional answer to the ones who still see Microsoft.EdgeWebView2Runtime as a available upgrade; check if you have 2 different Microsoft Edge WebView2 Runtime's installed (could be another architecture)
Related issues: https://github.com/microsoft/winget-cli/issues/1883, https://github.com/microsoft/winget-cli/issues/1824, https://github.com/microsoft/winget-cli/issues/1904, https://github.com/microsoft/winget-cli/issues/1873, https://github.com/microsoft/winget-pkgs/discussions/44812

PS C:\Users\user> winget upgrade --all
Found Microsoft Edge WebView2 Runtime [Microsoft.EdgeWebView2Runtime] Version 98.0.1108.55
Found  [Microsoft.EdgeWebView2Runtime] Version 98.0.1108.55
This application is licensed to you by its owner.
Microsoft is not responsible for, nor does it grant any licenses to, third-party packages.
Downloading https://msedge.sf.dl.delivery.mp.microsoft.com/filestreamingservice/files/cae1821c-be52-4d6b-8409-83fa73fc5a73/MicrosoftEdgeWebView2RuntimeInstallerX64.exe
██████████████████████████████   116 MB /  116 MB
Successfully verified installer hash
Starting package install...
Installer failed with exit code:<PHONE_NUMBER>

Again, run Powershell or Windows Terminal as Administrator.


fix(clients): support the rest of the languages

🧭 What and Why
Do the rest of the languages for #2561 , and add a new variable to make the templates more readable.

I have indeed, I'll do it later 😁
[DI-1787]


broken name of attribute (starts with a digit)

I see this in the .phi file that JEO generates:
α2 ↦ ξ.2dedb735-e2aa-4514-a7ac-eb20dc70361a,

Here, the name of the attribute is invalid, since it starts with a digit (must be a letter).

@volodya-lombrozo please, pay attention to this one, it's a blocker

@yegor256 Thank you for the bug report. I will attend to it shortly.

@rultor release, tag is 0.6.1, title is 0.6.1.

@rultor release, tag is 0.6.1, title is 0.6.1.

@volodya-lombrozo OK, I will release it now. Please check the progress here.

@rultor release, tag is 0.6.1, title is 0.6.1.

@volodya-lombrozo Done! FYI, the full log is here (took me 10min).


fix: Correctly log MAX_RETRY

Fixed a typo, so now the max retry attempts gets logged correctly in the docker script.

Thanks for the PR!


Text file busy (os error 26)

Component
Forge
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
nightly
What command(s) is the bug in?
forge build
Operating System
Linux
Describe the bug
Our monorepo has a bunch of packages, each using foundry nightly in CI (via foundry-rs/foundry-toolchain@v1). Each of these use forge build in their build step and we recently tried to turn on parallel builds (via pnpm), but it failed with
Text file busy (os error 26)

The logs weren't specific about where this was coming from, but I later saw a log line that mentioned solc-0.8.13:

Unclear if this is a foundry issue or solc issue, but it originates from forge build, so I'm starting here.
Ultimately would like to be able to run forge build for multiple foundry projects in parallel. Is this an issue with some sort of global cache? Or strictly just a ulimit thing?

this is likely just a flake
this usually happens when a binary is in use and another process wants to write to the binary's location (e.g. race condition of two separate forge build processes that both try to install/run it)
can you try:
deleting the installed 0.8.13
install it once: run forge build once, after which it should be installed

To clarify, we only see this in CI (Github actions). Foundry is installed once at the start of the action via the official action (https://github.com/foundry-rs/foundry-toolchain) and our version is configured to nightly.
And then the action's build step runs forge build multiple times in parallel (via pnpm but soon nx, once per project/package in the monorepo).

I see, then this is indeed the above-mentioned case.
looks like the svm file lock is not working properly, will try to investigate.
are all of these build tasks targeting the same profile?
can you perhaps add a single step to the CI that runs forge build once (this should install missing solc)

I'm not following. Are you saying that forge build lazily installs solc (and isn't part of the foundryup step) and because I am running this in parallel, it's trying to install solc in parallel, which is causing conflicts? And the potential resolution is to foundryup then forge build once, then running all the forge build steps in parallel should work?

And the potential resolution is to foundryup then forge build once, then running all the forge build steps in parallel should work

yes, missing solc bins are lazily installed during forge build, looks like the file lock in svm that should prevent these cases where two processes potentially write to and execute the same binary isn't working as expected
This is should be bypassed if you trigger forge b once before starting the parallel job

Text file busy (os error 26)

https://stackoverflow.com/a/16764967/6242846

Will give that a try, thank you!
Aside from forge build, are there other ways to trigger getting the solc bin?

forge build internally uses
https://github.com/roynalnaruto/svm-rs/tree/master
it doesn't have a static binary, please consider opening an issue there, should be possible to release it as such

ahh, so an alternative would be something like cargo install svm-rs && svm install 0.8.13 ahead of the parallel forge build usages? that seems a little easier to wire up in the way we have our CI actions configured

yes, that works. and is essentially would forge b would do first run
cargo install svm-rs adds a bit to CI time though, but not too much, I'd assume ~1:30min

since we already have is in forge, seems like there is actually a use case for an install solc subcommand

since we already have is in forge, seems like there is actually a use case for an install solc subcommand

that would be great!

cargo install svm-rs adds a bit to CI time though, but not too much, I'd assume ~1:30min

I assume we could cache this so hopefully won't need this every CI run

I think a nice temporary fix would be if the foundry action took care of installing solc non lazily
https://github.com/ethereum-optimism/optimism/pull/6210/files#diff-9fb8259afcb532c9556e2d41ae1ee97cf6de54b486cef93a7ef1bf39433fa530R36

at LUKSO with the lsp-smart-contracts, we fixed it by running forge build first as well in the CI and setting forge test as dependant on the build command in the turbo.json first.
See this commit for details: https://github.com/lukso-network/lsp-smart-contracts/pull/894/commits/25ba13438c0336cc99222f0e74222403e837f23f

Thanks for a good thread and explanation.
We are running into this issue at Trading Strategy Github CI builds, as we are parallelising unit tests. We do not have proper fix now (lock file before running forge?) so we are probably marking the tests flaky.

FWIW we fixed this by running one forge build before starting the parallel tasks that run forge build within the same worker (e.g. with turbo): https://github.com/latticexyz/mud/blob/57bf8c361999c7210622466dadcba037d4fe1238/.github/actions/setup/action.yml#L20-L25


Added icons to the UI tools/commands

@garys-esri

@jmccausland: do you want me to review and merge?

if you could, thanks


Day7

add contributors challenge 7

From all of us on the Cloud Advocacy team at Microsoft, thank you for creating this pull request!
Have a Happy Holiday season!


Using live & sandbox modes simultaniously and getting ApiException{statusCode: 404}

Hey,
Firstly thanks for this plugin! I'm running in to an issue when I try to use both the live and sandbox simultaneously to verify payment receipts. I'm doing this as my app was just rejected due to the fact that I was only checking production purchases, here is Apple's feedback:

Next Steps
When validating receipts on your server, your server needs to be able to handle a production-signed app getting its receipts from Apple’s test environment. The recommended approach is for your production server to always validate receipts against the production App Store first. If validation fails with the error code "Sandbox receipt used in production," you should validate against the test environment instead.

To implement this I'm doing something this:
        var order =
            await appstoreLive.lookUpOrderId(receipt.providerTransactionRef);

        // Check sanbox...
        if (order.status != 0) {
          log.info('APPSTORE: invalid live purchase, trying sandbox');
          var sandboxOrder = await appstoreSandbox
              .lookUpOrderId(receipt.providerTransactionRef);
          if (sandboxOrder.status == 0) {
            log.info('APPSTORE: Sandbox order valid');
            order = sandboxOrder;
          }
        }

However the sanbox client is failing with a 404 error:
ApiException{statusCode: 404, error: null}

#0      AppStoreServerHttpClient._makeRequest (package:app_store_server_sdk/src/io/app_store_server_http_client.dart:176)
<asynchronous suspension>
#1      AppStoreServerAPI.lookUpOrderId (package:app_store_server_sdk/src/app_store_server_api.dart:67)
<asynchronous suspension>
#2      AppleAppStorePaymentProvider._processPurchase (package:cloud_functions_core/src/payments/providers/apple_app_store_provider.dart:47)
<asynchronous suspension>
#3      AppleAppStorePaymentProvider.updateReceipt (package:cloud_functions_core/src/payments/providers/apple_app_store_provider.dart:29)
<asynchronous suspension>
#4      PaymentProcessor.processPurchaseReceipt (package:cloud_functions_core/src/payments/payment_processor.dart:90)
<asynchronous suspension>
#5      corsFunction (package:payment_processor/functions.dart:68)
<asynchronous suspension>
#6      cloudLoggingMiddleware.hostedLoggingMiddleware.<anonymous closure>.<anonymous closure> (package:functions_framework/src/logging.dart:171)
<asynchronous suspension>

I'm not sure if it's the JWT token that's causing an issue, I'm maintaining two JWT tokens, one for live and one for sandbox.
Do you have any idea why I'm getting a 404 for sandbox lookups?
This is running in a Cloud Run instance & my version is:
  app_store_server_sdk:
    dependency: transitive
    description:
      name: app_store_server_sdk
      url: "https://pub.dartlang.org"
    source: hosted
    version: "1.2.5"

FYI: The github issues URL is broken on the readme.md

Doing some more testing and lookUpOrderId() on sandbox always returns a 404.
Also I'm not convinced that lookUpOrderId (orderId) is working on live? It always returns status: 1. Here is the response when I lookup my order:<PHONE_NUMBER>72903
Order: OrderLookupResponse{status: 1, signedTransactions: null}

Yet I POST the receipt data to  the 'https://buy.itunes.apple.com/verifyReceipt' it returns it as valid and lists<PHONE_NUMBER>72903 as a valid transaction_id in in_app.
{
    "receipt": {
        "receipt_type": "Production",
        "adam_id":<PHONE_NUMBER>,
        "app_item_id":<PHONE_NUMBER>,
        "bundle_id": "com.myapp.app",
        "application_version": "57",
        "download_id":<PHONE_NUMBER>39396258,
        "version_external_identifier": 853018761,
        "receipt_creation_date": "2022-11-24 18:05:02 Etc/GMT",
        "receipt_creation_date_ms": "1669313102000",
        "receipt_creation_date_pst": "2022-11-24 10:05:02 America/Los_Angeles",
        "request_date": "2022-11-24 18:35:53 Etc/GMT",
        "request_date_ms": "1669314953638",
        "request_date_pst": "2022-11-24 10:35:53 America/Los_Angeles",
        "original_purchase_date": "2022-10-25 17:51:24 Etc/GMT",
        "original_purchase_date_ms": "1666720284000",
        "original_purchase_date_pst": "2022-10-25 10:51:24 America/Los_Angeles",
        "original_application_version": "20",
        "in_app": [
            {
                "quantity": "1",
                "product_id": "like_1",
                "transaction_id": "240001281972903",
                "original_transaction_id": "240001281972903",
                "purchase_date": "2022-11-24 18:05:01 Etc/GMT",
                "purchase_date_ms": "1669313101000",
                "purchase_date_pst": "2022-11-24 10:05:01 America/Los_Angeles",
                "original_purchase_date": "2022-11-24 18:05:01 Etc/GMT",
                "original_purchase_date_ms": "1669313101000",
                "original_purchase_date_pst": "2022-11-24 10:05:01 America/Los_Angeles",
                "is_trial_period": "false",
                "in_app_ownership_type": "PURCHASED"
            },
            {
                "quantity": "1",
                "product_id": "undo_3",
                "transaction_id": "240001281101159",
                "original_transaction_id": "240001281101159",
                "purchase_date": "2022-11-23 10:34:12 Etc/GMT",
                "purchase_date_ms": "1669199652000",
                "purchase_date_pst": "2022-11-23 02:34:12 America/Los_Angeles",
                "original_purchase_date": "2022-11-23 10:34:12 Etc/GMT",
                "original_purchase_date_ms": "1669199652000",
                "original_purchase_date_pst": "2022-11-23 02:34:12 America/Los_Angeles",
                "is_trial_period": "false",
                "in_app_ownership_type": "PURCHASED"
            }
        ]
    },
    "environment": "Production",
    "status": 0
}

Any advice would be appreciated, hopefully I'm just doing something wrong?


Cannot reproduce performance on forn_2v

Hi~ Thank you very much for the open source code and paper
I tried to train a model with default config，but I got poor performance on forn_2v.I strictly followed the instructions to start the reproduction experiment，However, my experimental results are quite different from the released results；
result of mine：

log of last iter：

Am i missing something ?  Really appreciate for your help.

Hi,
A test PSNR of ~19 is expected on the horns data. I would suggest several things to check:

Are the latest code and data being used?
Are some parameters being changed? (e.g., number of sampled rays to fit into memory)
Check the released pre-trained model and see whether the results are similar.

Thanks for your interest!


Automated cherry pick of #3257: optimized: 优化安全组规则，支持逗号分隔的规则

Cherry pick of #3257 on release/2.12.
#3257: optimized: 优化安全组规则，支持逗号分隔的规则

Codecov Report

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

@@              Coverage Diff               @@
##             release/2.12   #3258   +/-   ##
==============================================
  Coverage                ?   7.12%
==============================================
  Files                   ?     480
  Lines                   ?   77695
  Branches                ?       0
==============================================
  Hits                    ?    5534
  Misses                  ?   71697
  Partials                ?     464

Flag
Coverage Δ

#aFlag
7.12% <0%> (?)

Impacted Files
Coverage Δ

pkg/compute/models/secgrouprules.go
5.05% <0%> (ø)

Continue to review full report at Codecov.

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

/approve
/lgtm


When either data_profiler_filter or superuser_filter aren't defined,…

… don't crash, and set user to have data_profiler or superuser access.
At present, if data_profiler_filter or superuser_filter aren't defined, dataprofiler and superuser aren't set in LDAPUser's init, resulting an an AttributeError when accessors are called.

@bolkedebruin

@bolkedebruin btw, without this patch, LDAP on master won't work unless dataprofiler/superuser filters are set (i.e. master is broken for default use case right now).

Ok. Will have a look at it towards the end of this week

Gentle nudge here. :)

@criccomini In general the patch looks solid! I would like to see the tests also cover the use of data_profiler and superuser. This would require to add it to the ldap provisioning for a specific user.
After that please squash your commits in some meaningful ones.

@bolkedebruin can you elaborate a bit on what you mean by "tests covering the use of data_profiler and superuser"?

@mtagle I think he means that he wants a test that adds several users to the LDAP test. One would be a user with just basic access (no data profiler/super user), one with just data profiler, and one with just super user (and potentially one with both). Then verify that the data_profiler() and superuser() methods return True/False as expected.

Correct. The provisioning can be done by the files no need to encapsulate it in the test itself.

@bolkedebruin could I get a further review/merge?

ping @mistercrunch

@mistercrunch I think this is ready to be committed.

:+1:


livecheck: crates.io strategy

[x] Have you followed the guidelines in our Contributing document?
[x] Have you checked to ensure there aren't other open Pull Requests for the same change?
[x] Have you added an explanation of what your changes do and why you'd like us to include them?
[x] Have you written new tests for your changes? Here's an example.

[x] Have you successfully run brew tests with your changes locally?
[x] Have you successfully run brew man locally and committed any changes?

This adds a new livecheck strategy for software obtained from crates.io. Note that crates.io doesn't let bots access their data (https://crates.io/policies#crawlers) so docs.rs is used instead.

From what I'm seeing, we don't currently have any formulae in homebrew/core that use a crate as the stable archive, homepage, etc. We prefer to check for a new version in the same place as the stable URL, whenever possible, so that usually ends up being GitHub for Rust-related formulae.
Could you explain a bit about what category of formulae would benefit from this strategy (with examples, if possible)? We usually add a strategy in response to a demonstrated need (i.e., multiple formulae doing something similar in their livecheck block, multiple formulae using the same stable source, etc.).

we don't currently have any formulae in homebrew/core that use a crate as the stable archive, homepage, etc.

Emphasis on the currently https://github.com/Homebrew/homebrew-core/pull/66697 😁
I'm guessing that asking upstream to retroactively tag commits is no go (https://github.com/Homebrew/brew/pull/9505#issuecomment-743216664). And something tells me this isn't an isolated case and we might bump into it again so I decided to take care of it.
I already addressed it with a formula-specific livecheck block but then I saw PyPI, npm & Hackage specific strategies and one thing led to another...

Could you explain a bit about what category of formulae would benefit from this strategy (with examples, if possible)?

So to answer your question, the only category of formulae that would benefit from this strategy are weird ones without tagged releases on Github 🤷
I guess this falls into:

Your scientists were so preoccupied with whether or not they could, they didn’t stop to think if they should.

 I figured out that all livecheck strategies lack (fake) user agent making them susceptible to data access restrictions like in crates.io case (https://crates.io/policies#crawlers).
This brings me to the next question. @samford how do you feel about me doing some actually useful PR ensuring Homebrew's fake Safari user agent is used for all livecheck requests?

Emphasis on the currently Homebrew/homebrew-core#66697 😁

There was one problematic formula in the past where I floated the idea of switching stable to a crate file (as there weren't any other good options at the time) but there was pushback against the idea. If that idea got anywhere, I was going to either add .crate to unpack_strategy/tar.rb or create a new strategy (like #9505), so it's interesting to see this.
Let's see how Homebrew/homebrew-core#66697 and #9505 play out before we move forward with this livecheck strategy. If the oakc formula ends up being merged while using the crate, I'll come back and review this and move it toward merging. I'm going to label this do not merge for now.

how do you feel about me doing some actually useful PR ensuring Homebrew's fake Safari user agent is used for all livecheck requests?

I'm glad you asked, as I have some local changes hanging around that address this as part of something larger. I've encountered issues with a small number of other websites in the past, which is why I made sure to add support for user agents as part of working on something else. I haven't created a PR for this yet because I promised not to work on notable livecheck PRs until my open documentation PR is pretty much done (or at least closer to merging).
I've been working on the docs PR a lot this week and I'm getting close to pushing a revision, so I should be working on livecheck's internals again very soon. At that time, I'll be creating a bunch of PRs for changes I've been sitting on, so it would be best to hold off for now. Thanks for the offer, though!

There was one problematic formula in the past where I floated the idea of switching stable to a crate file (as there weren't any other good options at the time)

It is kinda comforting to know I'm not the only one that hit that bummer. And you can definitely expect me to fix exotic and things not worth touching 😄

I've been working on the docs PR a lot this week and I'm getting close to pushing a revision, so I should be working on livecheck's internals again very soon. At that time, I'll be creating a bunch of PRs for changes I've been sitting on, so it would be best to hold off for now. Thanks for the offer, though!

It is equally satisfying to fix things myself or just see them being fixed by others so go ahead and make it better 🚀

Let's see how Homebrew/homebrew-core#66697 and #9505 play out before we move forward with this livecheck strategy.

In light of #9505  being closed without merging, I think we should follow suit here. oakc is the only formula that uses a crate as the stable archive at the moment and I don't see that number notably increasing anytime soon. It seems likely that oakc will remain the only formula using a crate for some time, as it's not something that we do under normal circumstances. Even then, the long-term goal with oakc is to migrate its stable URL away from the crate if upstream ever starts tagging release versions on GitHub.
As mentioned before, we create new strategies based on a demonstrated need in enough formulae/casks and that's not the case here yet. With that in mind, I'm going to close this but feel free to save a patch or stash these changes in case the situation changes in the future.
Thanks for your understanding, @vladimyr!

It was the logical thing to do 👍
If we ever see an increase in cases where crate URL is used as stable this could be used as the basis for a new livecheck strategy.


Exported macros appear twice in left sidebar (rustc 1.60.0 nightly, docsrs 0.6.0)

Hey! Ran into what appears to be a bug - crate's exported macros each appear twice in the left sidebar:

Build log here
Current doc page here
Toolchain versions (per log): rustc 1.60.0-nightly (e7aca8959 2022-02-09), docsrs 0.6.0 (5c3b689 2022-02-01)

Please let me know if I can provide additional info.

Thank you for the report!
This is definitely not an issue with docs.rs itself, but with rustdoc.
@GuillaumeGomez @jsha is this known? Should a rustdoc issue be created?

Not known afaik. Please do file an issue (or transfer this one)!


Topology restrictions

The phrase "topology restrictions" is very unclear and should be reworded to make it easier to understand.

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

ID: 5a808705-dc30-b57f-7e2e-2ec0a9360124
Version Independent ID: 2d766a55-b579-0991-5d79-78ca2a82ef4a
Content: Model relationships in Power BI Desktop - Power BI
Content Source: powerbi-docs/transform-model/desktop-relationships-understand.md
Service: powerbi
Sub-service: powerbi-desktop
GitHub Login: @peter-myers
Microsoft Alias: v-pemyer

Hi, @DaniilMaslyuk -- thanks for the suggestion! Assigned to the author to address.

Hi @DaniilMaslyuk - thanks for your feedback. We agree with your comments, and we're actively working with engineering to gain a deeper understanding. Stay tuned for an update to this article when we learn more. #please-close


Broken pkg-config Libs.private OpenGL libraries with MinGW cross compilation.

Prerequisite Checklist

[X] I searched for existing issues to prevent duplicates
[X] I searched for existing discussions on the forum to prevent duplicates
[X] I am here to report an issue and not to just ask a question or look for help (use the forum or Discord instead)

Describe your issue here
The sfml-window.pc and sfml-graphics.pc scripts have incorrect expansions for the OpenGL libraries in the Libs.private variable.
When invoking pkg-config --libs --static sfml-window on a MinGW cross-compilation, the OpenGL libraries are reported as opengl32 glu32. Same thing happens with sfml-graphics.
These are not valid libraries for linking, it should either be the full path (e.g. /usr/i686-w64-mingw32/sys-root/mingw/lib/libglu32.a /usr/i686-w64-mingw32/sys-root/mingw/lib/libopengl32.a) or specified with the -l option (e.g. -lglu32 -lopengl32).
This problem does not occur with native Linux compilation; the reported libraries are /usr/lib64/libGL.so /usr/lib64/libGLU.so (although the order should be GLU then GL.)
This problem also does not occur in sfml-audio.pc, where OpenAL is used in Libs.private; it correctly expands to the full path (e.g. /usr/i686-w64-mingw32/sys-root/mingw/lib/libOpenAL32.dll.a).
Your Environment

OS / distro / window manager: Fedora 39, Mageia 9
SFML version: 2.6.1
Compiler / toolchain: MinGW gcc 13.2.1
Special compiler / CMake flags:
-DCMAKE_TOOLCHAIN_FILE=/usr/share/mingw/toolchain-mingw32.cmake
-DBUILD_SHARED_LIBS=TRUE
-DSFML_USE_SYSTEM_DEPS=TRUE
-DSFML_INSTALL_PKGCONFIG_FILES=TRUE

Steps to reproduce

cross-compiling SFML with MinGW:

export MINGW_ROOT=/usr/i686-w64-mingw32/sys-root/mingw
cmake \
    -DCMAKE_TOOLCHAIN_FILE=/usr/share/mingw/toolchain-mingw32.cmake \
    -DBUILD_SHARED_LIBS=TRUE \
    -DCMAKE_INSTALL_PREFIX=${MINGW_ROOT} \
    -DCMAKE_VERBOSE_MAKEFILE=TRUE \
    -DSFML_USE_SYSTEM_DEPS=TRUE \
    -DSFML_INSTALL_PKGCONFIG_FILES=TRUE \
    ..
make
sudo make install

Run i686-w64-mingw32-pkg-config --libs --static sfml-window

Expected behavior
It should print -lsfml-window -lglu32 -lopengl32 -lsfml-system, which is what can be used by the linker.
Actual behavior
It prints -lsfml-window opengl32 glu32 -lsfml-system, and any attempt to use that for linking causes errors:
/usr/lib/gcc/i686-w64-mingw32/12.2.1/../../../../i686-w64-mingw32/bin/ld: cannot find opengl32: No such file or directory
/usr/lib/gcc/i686-w64-mingw32/12.2.1/../../../../i686-w64-mingw32/bin/ld: cannot find glu32: No such file or directory

Is it valid to add a -l before @OPENGL_gl_LIBRARY@ and @OPENGL_glu_LIBRARY@? That would seemingly fix the crosscompilation case but I'm not sure what happens when you add -l before an absolute path.

No, it would also be wrong to have -l in front of absolute paths.
I just checked the MSYS2 SFML package (https://packages.msys2.org/base/mingw-w64-sfml), it's also broken, for both MinGW and Clang builds. Cross compilation is not a factor.
It seems the combination of Windows host and non-MSVC causes the problem, perhaps something funny inside FindOpenGL.
Perhaps you could check for Windows, then hardcode the OpenGL libs used in the pkg-config scripts to -lglu32 -lopengl32.
Note that pkg-config has a --msvc-syntax, that automatically rewrites GCC-style arguments into MSVC-style arguments. This would come out as glu32.lib opengl32.lib, which is correct for MSVC. Even if SFML is being built with MSVC, you can write the pkg-config variables as if they were for GCC.

Looks like we'll need some very specific solution where we check the value of those two cache variables produced by FindOpenGL.cmake and prepend -l if they're not absolute paths. Can you look into whether CMake (as of version 3.7) has a way of detecting whether a given path is absolute or not?
You might have found something worth reporting to Kitware as a CMake bug. You should consider reaching out. https://gitlab.kitware.com/cmake/cmake/-/issues

OpenGL detection is already working for building SFML, right? So all you need is a dedicated variable for the pkg-config scripts, where you hardcode the result for Windows builds, instead of using the detected OpenGL.


error getting download url

PS D:\Desktop\instaget-master> cargo run https://www.instagram.com/p/CYjktDFqxIm/?utm_source=ig_web_copy_link
    Finished dev [unoptimized + debuginfo] target(s) in 0.91s
     Running `target\debug\instaget.exe https://www.instagram.com/p/CYjktDFqxIm/?utm_source=ig_web_copy_link`
downloading . error decoding response body: expected value at line 1 column 1
error getting download url
error getting file type
error: process didn't exit successfully: `target\debug\instaget.exe https://www.instagram.com/p/CYjktDFqxIm/?utm_source=ig_web_copy_link` (exit code: 1)

hey @89z , can you help me to debug it? To be honest, this tool has not been tested on the Windows operating system yet


Can't drag a Window out of the screen bounds when using WindowDraggableArea

Describe the bug
Hi! Using a Window ~with undecorated and transparent parameters set to true~, and a WindowDraggableArea to provide a custom header for users to drag the window, we can't seem to move the window outside of the screen bounds, to the right, left, or bottom like we can do with a normal, decorated window, which can be dragged out of the screen in all directions except the top of the window.
This is not about multiple monitors and dragging the window between them. The issue is about the whole "screen", the virtual space spanning all monitors. I only have one monitor and haven't tested the multi-monitor case.
Update: it doesn't matter if the Window is undecorated, dragging using a WindowDraggableArea always exhibits the same behavior. The native top bar doesn't have this issue.
Affected platforms

Desktop (Linux, not tested on Windows/macOS)

Versions

Kotlin version: 1.9.10
Compose Multiplatform version: 1.5.2
OS version: Fedora 38 / GNOME 44.5 (Wayland)
OS architecture: x86
JDK: Azul Zulu 17

To Reproduce
Create an ~undecorated, transparent~ Window with a WindowDraggableArea in it. Dragging the window works, but only when the entire window is inside the screen. Trying to move it such that only part of it is outside the screen doesn't work.
Expected behavior
Window should move outside the screen at least through the right, left, and bottom edges.
Additional context
I think it might be great if this behavior is customizable, allowing us to set the edges we want to allow the window to go through, with the default value being set to the right, left, and bottom, just like how it works with the native decorations.
This might be related to #3771.

I tested this sample on Mac (for another issue with WindowDraggableArea): https://github.com/dima-avdeev-jb/issue-3709
and I am not sure what you mean. I noticed that moving window between screens using  WindowDraggableArea definitely has an issue (there is no "preview" of the window on another monitor until it is really moved to another monitor).
However I have not noticed differences when moving the window out of the screen bounds when using WindowDraggableArea and usual title bar. Maybe it is a Linux specific -- can you record a video on what you mean? Do you have several virtual screens on Linux (so you are trying to move the window to another virtual screen)?

Thanks for the response! No, I'm not trying to move between virtual screens (workspaces).
Here's a video:
https://github.com/JetBrains/compose-multiplatform/assets/35589610/375f275d-1ffe-4d71-91d4-b2b1d3512744
You can see how the window can go through the edges of the screen when using the native title bar, but can't do that when using the WindowDraggableArea.
Apparently this video also shows another bug: trying to move the WindowDraggableArea when there's also the native title bar, the window immediately moves down by the height of the native title bar (sometimes). I normally have the native title bar disabled, but enabled it here for the sake of demonstration, that's why I never noticed that before. But that's for another issue, I guess.

It's probably this issue: https://bugs.openjdk.org/browse/JDK-8205204

That sure looks related, but it's not specific to undecorated windows, but for any "manual" handling of window position, just like Compose's WindowDraggableArea.

What happens in that ticket is exactly what happens here: attempting to set the location of the window such that it's (partially) outside the screen fails. Most likely Window.setLocation simply prevents it, or coerces the bounds to be fully inside the screen.

Java issues like these make me believe much more in Kotlin/Native support for Compose Desktop, since we can wire it up directly to a low-level windowing library without these limitations.
We can also take the path that Jetbrains took with their IDEs and have thin native wrappers over some system APIs that allows us to break out of Java's limitations and have more when needed.
For example, IntelliJ IDEs merge their top bar with native window controls on Windows and macOS and control them as they like.

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Add Queen Elizabeth School

Queen Elizabeth School: https://qes.edu.hk
Our email domain is cloud.qes.edu.hk instead of qes.edu.hk.

@sdip15fa Thank you for your patience while waiting for a review and processing your request. Pull request merged. Thank you!


[issue-69] Redis instrumentation

Fixes #69
Please feed back on this approach

@pavolloffay I couldn't find an easy way to make use of java-redis-client in the Spring classes. I'll wait for @malafeev 's advice on this

java-redis-client is more low level api for jedis and lettuce clients.
I don't think it can be used here because here is abstraction over any client. And that's good.
But maybe we can move this instrumentation into java-redis-client as module?
And use it here? It would be useful for spring projects, but not cloud.

Indeed these could be useful for a regular spring project. I'll refactor the code and open a PR against the other project

Raised https://github.com/opentracing-contrib/java-redis-client/pull/10

java-redis-client version 0.0.7 with spring support is released.
It will be available in maven central during 24 hours.

thanks @malafeev

hi @pavolloffay any thoughts on this PR?

Sorry, I'm snowed under ATM... I'll try to take a look at this tonight

@pavolloffay  with regards adding more testing under the alldeps profile, this will require setting up an embedded Redis to be able to fetch a connection. I'm not sure whether is worth doing all this in this test but let me know and I can add it

Merged in #172. Thanks @ddcprg. I wanted to rush and do release with this feature. Thanks again.

cool, thanks @pavolloffay


Unify make commands for deployment

Description
Currently multiply options / make commands to install the operator exist.
This PR aligns them by:

removing all commands for deployment but make [un]deploy
use helm upgrade to get it as close to customer experience as possible

Jira

How can this be tested?

run make [un]deploy

:warning: Please install the  to ensure uploads and comments are reliably processed by Codecov.
Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 64.24%. Comparing base (a57f910) to head (76ec343).

:exclamation: Your organization needs to install the Codecov GitHub app to enable full functionality.
Additional details and impacted files
@@           Coverage Diff           @@
##             main    #4214   +/-   ##
=======================================
  Coverage   64.24%   64.24%
=======================================
  Files         398      398
  Lines       26909    26909
=======================================
  Hits        17287    17287
  Misses       8255     8255
  Partials     1367     1367

Flag
Coverage Δ

unittests
64.24% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.

Checked with asperitas, they use the helm command directly to install the operator


snippet for def classmethod

https://github.com/Microsoft/vscode-python/blob/b741e1af6d53cdf94765a6708964d489bd558ff8/snippets/python.json#L146-L153
should be
"body": [
    "@classmethod",
    "def ${1:funcname}(cls, ${2:parameter_list}):",
    "\t${3:pass}"
]

Please provide more info,

Reasons for changing
Current behavior
Expected behavior

@karrtikr
Here are the current json file, they are the same content.
    "def": {
        "prefix": "def",
        "body": [
            "def ${1:funcname}(${2:parameter_list}):",
            "\t${3:pass}"
        ],
        "description": "Code snippet for a function definition"
    },
    "def(class method)": {
        "prefix": "def(class method)",
        "body": [
            "def ${1:funcname}(self, ${2:parameter_list}):",
            "\t${3:pass}"
        ],
        "description": "Code snippet for a class method"
    },

Can you please elaborate? With an example perhaps. I don't understand the issue here.

Current behavior:
When user typing def(class method):
def ${1:funcname}(self, ${2:parameter_list}):
    ${3:pass}

Expected behavior:
When user typing def(class method):
@classmethod
def ${1:funcname}(cls, ${2:parameter_list}):
    ${3:pass}

Thanks a lot for elaborating. I see what you're saying.
Prescribed solution
Replacing
"def(class method)": {
    "prefix": "def(class method)",
    "body": [
        "def ${1:funcname}(self, ${2:parameter_list}):",
        "\t${3:pass}"
    ],
    "description": "Code snippet for a class method"
},,

with
"def(class method)": {
    "prefix": "def(class method)",
    "body": [
        "@classmethod",
        "def ${1:funcname}(cls, ${2:parameter_list}):",
        "\t${3:pass}"
    ],
    "description": "Code snippet for a class method"
},
"def(instance method)": {
    "prefix": "def(instance method)",
    "body": [
        "def ${1:funcname}(self, ${2:parameter_list}):",
        "\t${3:pass}"
    ],
    "description": "Code snippet for a instance method"
},

should do the job here.

I would actually just name it "method" as that's what everyone is going to look for as the name.

This looks like an easy fix that fell under the table. Shall I submit the PR?

@janosh I would hold off as we are considering dropping all of our snippets.

Interesting. Where is that being tracked?

#14781

@janosh correct, we have no control over user-defined snippets, so you can totally have your own copy (or even create your own extension of Python snippets!).

Snippets have been removed by #15006, so closing this as out of date.


[Packaging tasks] Update dependencies on "azure-pipelines-tasks-packaging-common" package to fix high vulnerability issues

Required Information
Entering this information will route you directly to the right team and expedite traction.
Question, Bug, or Feature?
Type: Bug
Enter Task Name:

DownloadPackageV0
DownloadPackageV1
NpmV0
NpmV1

Issue Description
These tasks have dependency on "azure-pipelines-tasks-packaging-common" that has critical vulnerability in "azure-devops-node-api > typed-rest-client > underscore", " typed-rest-client >underscore", "azure-devops-node-api > underscore".

Please update this dependency to latest version.
This vulnerability was fixed in PR.
Error logs
To get error log for each task run npm audit

Hi, @phil-hodgson could you please take a look?


Update Booking Page

🖥 Frontend Issue
Description
Change existing UI/UX of the booking the elements are not aligned
Steps to Reproduce

Check Booking Page

Expected behavior

Actual behavior

Screenshots or Video

Are you participating in GSSoC?

[X] Yes
[ ] No

hey @dhairyagothi he seems to be inactive at the issue, can u assign me so that I can work, I will make the PR by tommorow


require is not defined

[x] Review the documentation: https://facebook.github.io/react-native
[x] Search for existing issues: https://github.com/facebook/react-native/issues
[x] Use the latest React Native release: https://github.com/facebook/react-native/releases

Environment
React Native Environment Info:
    System:
      OS: macOS 10.14.1
      CPU: (8) x64 Intel(R) Core(TM) i7-4771 CPU @ 3.50GHz
      Memory: 2.01 GB / 16.00 GB
      Shell: 3.2.57 - /bin/bash
    Binaries:
      Node: 11.3.0 - /usr/local/bin/node
      Yarn: 1.12.3 - /usr/local/bin/yarn
      npm: 6.4.1 - /usr/local/bin/npm
      Watchman: 4.9.0 - /usr/local/bin/watchman
    SDKs:
      iOS SDK:
        Platforms: iOS 12.0, macOS 10.14, tvOS 12.0, watchOS 5.0
      Android SDK:
        API Levels: 23, 26, 27, 28
        Build Tools: 23.0.1, 26.0.1, 26.0.3, 27.0.3, 28.0.3
        System Images: android-26 | Google APIs Intel x86 Atom_64, android-27 | Intel x86 Atom_64, android-27 | Google APIs Intel x86 Atom
    IDEs:
      Android Studio: 3.2 AI-181.55<IP_ADDRESS>56338
      Xcode: 10.0/10A254a - /usr/bin/xcodebuild
    npmPackages:
      react: 16.6.1 => 16.6.1
      react-native: 0.57.7 => 0.57.7
    npmGlobalPackages:
      react-native-cli: 2.0.1
      react-native-git-upgrade: 0.2.7

Description
First time I faced this error last week after upgrading to 0.57, then I tried some commands like react-native start --reset-cache and it was ok.
Today again I faced it and nothing works to me! Simulator also went slow and laggy!
The things that I tried :

the command above and pkill node
changing Xcode build system
trying node version: 8 & 11

These screenshots are from a new initialized react-native by init command :

Reproducible Demo
The app is the react-native init starter and here the errors :
Unhandled JS Exception: Can't find variable: require (http://localhost:8081/index.bundle?platform=ios&dev=true&minify=false:410) ( as the attached image )
after choosing Debug JS Remotely :
require is not defined!
I'm not sure if it's a bug or my environment problem! I need to upgrade our app and will be happy with any idea to solve it.
Regards

no it was both in env. I found the problem.
{
  "presets": ["module:metro-react-native-babel-preset"],
  "plugins": [
    ["@babel/plugin-proposal-decorators", { "legacy": true }]
  ],
  "env": {
    "development": {
      "plugins": [
        "@babel/plugin-transform-typeof-symbol"
      ]
    },
    "production": {
      "plugins": ["transform-remove-console"]
    }
  }
}

I removed these lines and now it's ok. I just need a way find out how to include it.
"env": {
    "development": {
      "plugins": [
        "@babel/plugin-transform-typeof-symbol"
      ]
    },

same here


Untracked files in git repository after running "flutter create ."

Immediately after creating an new Flutter project, there are untracked files in the Git repository.
 This is not desirable, because now there are differences between a fresh checkout and a freshly created project.
Fix

Fix the output of all flutter create template types (app, module, package, plugin, plugin_ffi and skeleton) to only generate files that are committed to git or adjust the gitignore to include them.
Guard this by a github action that fails if the output of git clean -xdn or git ls-files . --ignored --exclude-standard --others lists untracked files.

Related issues
#9460
Logs

flutter create .
Creating project ....
Resolving dependencies... (1.1s)
Got dependencies.
Wrote 108 files.

All done!
You can find general documentation for Flutter at: https://docs.flutter.dev/
Detailed API documentation is available at: https://api.flutter.dev/
If you prefer video documentation, consider: https://www.youtube.com/c/flutterdev

In order to run your application, type:

  $ cd .
  $ flutter run

Your application code is in ./lib/main.dart.

git init
Initialized empty Git repository in /Users/johannesroest/repos/flutter_git_test/.git/

git add .

git commit -m "initial commit"
[master (root-commit) 6189338] initial commit
 101 files changed, 3379 insertions(+)
 create mode 100644 .gitignore
 create mode 100644 .metadata
 create mode 100644 README.md
 create mode 100644 analysis_options.yaml
 create mode 100644 android/.gitignore
 create mode 100644 android/app/build.gradle
 create mode 100644 android/app/src/debug/AndroidManifest.xml
 create mode 100644 android/app/src/main/AndroidManifest.xml
 create mode 100644 android/app/src/main/kotlin/com/example/flutter_git_test/MainActivity.kt
 create mode 100644 android/app/src/main/res/drawable-v21/launch_background.xml
 create mode 100644 android/app/src/main/res/drawable/launch_background.xml
 create mode 100644 android/app/src/main/res/mipmap-hdpi/ic_launcher.png
 create mode 100644 android/app/src/main/res/mipmap-mdpi/ic_launcher.png
 create mode 100644 android/app/src/main/res/mipmap-xhdpi/ic_launcher.png
 create mode 100644 android/app/src/main/res/mipmap-xxhdpi/ic_launcher.png
 create mode 100644 android/app/src/main/res/mipmap-xxxhdpi/ic_launcher.png
 create mode 100644 android/app/src/main/res/values-night/styles.xml
 create mode 100644 android/app/src/main/res/values/styles.xml
 create mode 100644 android/app/src/profile/AndroidManifest.xml
 create mode 100644 android/build.gradle
 create mode 100644 android/gradle.properties
 create mode 100644 android/gradle/wrapper/gradle-wrapper.properties
 create mode 100644 android/settings.gradle
 create mode 100644 ios/.gitignore
 create mode 100644 ios/Flutter/AppFrameworkInfo.plist
 create mode 100644 ios/Flutter/Debug.xcconfig
 create mode 100644 ios/Flutter/Release.xcconfig
 create mode 100644 ios/Runner.xcodeproj/project.pbxproj
 create mode 100644 ios/Runner.xcodeproj/project.xcworkspace/contents.xcworkspacedata
 create mode 100644 ios/Runner.xcodeproj/project.xcworkspace/xcshareddata/IDEWorkspaceChecks.plist
 create mode 100644 ios/Runner.xcodeproj/project.xcworkspace/xcshareddata/WorkspaceSettings.xcsettings
 create mode 100644 ios/Runner.xcodeproj/xcshareddata/xcschemes/Runner.xcscheme
 create mode 100644 ios/Runner.xcworkspace/contents.xcworkspacedata
 create mode 100644 ios/Runner.xcworkspace/xcshareddata/IDEWorkspaceChecks.plist
 create mode 100644 ios/Runner.xcworkspace/xcshareddata/WorkspaceSettings.xcsettings
 create mode 100644 ios/Runner/AppDelegate.swift
 create mode 100644 ios/Runner/Assets.xcassets/AppIcon.appiconset/Contents.json
 create mode 100644<EMAIL_ADDRESS> create mode 100644<EMAIL_ADDRESS> create mode 100644<EMAIL_ADDRESS> create mode 100644<EMAIL_ADDRESS> create mode 100644<EMAIL_ADDRESS> create mode 100644<EMAIL_ADDRESS> create mode 100644<EMAIL_ADDRESS> create mode 100644<EMAIL_ADDRESS> create mode 100644<EMAIL_ADDRESS> create mode 100644<EMAIL_ADDRESS> create mode 100644<EMAIL_ADDRESS> create mode 100644<EMAIL_ADDRESS> create mode 100644<EMAIL_ADDRESS> create mode 100644<EMAIL_ADDRESS> create mode 100644<EMAIL_ADDRESS> create mode 100644 ios/Runner/Assets.xcassets/LaunchImage.imageset/Contents.json
 create mode 100644 ios/Runner/Assets.xcassets/LaunchImage.imageset/LaunchImage.png
 create mode 100644<EMAIL_ADDRESS> create mode 100644<EMAIL_ADDRESS> create mode 100644 ios/Runner/Assets.xcassets/LaunchImage.imageset/README.md
 create mode 100644 ios/Runner/Base.lproj/LaunchScreen.storyboard
 create mode 100644 ios/Runner/Base.lproj/Main.storyboard
 create mode 100644 ios/Runner/Info.plist
 create mode 100644 ios/Runner/Runner-Bridging-Header.h
 create mode 100644 ios/RunnerTests/RunnerTests.swift
 create mode 100644 lib/main.dart
 create mode 100644 macos/.gitignore
 create mode 100644 macos/Flutter/Flutter-Debug.xcconfig
 create mode 100644 macos/Flutter/Flutter-Release.xcconfig
 create mode 100644 macos/Flutter/GeneratedPluginRegistrant.swift
 create mode 100644 macos/Runner.xcodeproj/project.pbxproj
 create mode 100644 macos/Runner.xcodeproj/project.xcworkspace/xcshareddata/IDEWorkspaceChecks.plist
 create mode 100644 macos/Runner.xcodeproj/xcshareddata/xcschemes/Runner.xcscheme
 create mode 100644 macos/Runner.xcworkspace/contents.xcworkspacedata
 create mode 100644 macos/Runner.xcworkspace/xcshareddata/IDEWorkspaceChecks.plist
 create mode 100644 macos/Runner/AppDelegate.swift
 create mode 100644 macos/Runner/Assets.xcassets/AppIcon.appiconset/Contents.json
 create mode 100644 macos/Runner/Assets.xcassets/AppIcon.appiconset/app_icon_1024.png
 create mode 100644 macos/Runner/Assets.xcassets/AppIcon.appiconset/app_icon_128.png
 create mode 100644 macos/Runner/Assets.xcassets/AppIcon.appiconset/app_icon_16.png
 create mode 100644 macos/Runner/Assets.xcassets/AppIcon.appiconset/app_icon_256.png
 create mode 100644 macos/Runner/Assets.xcassets/AppIcon.appiconset/app_icon_32.png
 create mode 100644 macos/Runner/Assets.xcassets/AppIcon.appiconset/app_icon_512.png
 create mode 100644 macos/Runner/Assets.xcassets/AppIcon.appiconset/app_icon_64.png
 create mode 100644 macos/Runner/Base.lproj/MainMenu.xib
 create mode 100644 macos/Runner/Configs/AppInfo.xcconfig
 create mode 100644 macos/Runner/Configs/Debug.xcconfig
 create mode 100644 macos/Runner/Configs/Release.xcconfig
 create mode 100644 macos/Runner/Configs/Warnings.xcconfig
 create mode 100644 macos/Runner/DebugProfile.entitlements
 create mode 100644 macos/Runner/Info.plist
 create mode 100644 macos/Runner/MainFlutterWindow.swift
 create mode 100644 macos/Runner/Release.entitlements
 create mode 100644 macos/RunnerTests/RunnerTests.swift
 create mode 100644 pubspec.lock
 create mode 100644 pubspec.yaml
 create mode 100644 test/widget_test.dart
 create mode 100644 web/favicon.png
 create mode 100644 web/icons/Icon-192.png
 create mode 100644 web/icons/Icon-512.png
 create mode 100644 web/icons/Icon-maskable-192.png
 create mode 100644 web/icons/Icon-maskable-512.png
 create mode 100644 web/index.html
 create mode 100644 web/manifest.json

git clean -xdn
Would remove .dart_tool/
Would remove .idea/
Would remove android/app/src/main/java/
Would remove android/flutter_git_test_android.iml
Would remove android/gradle/wrapper/gradle-wrapper.jar
Would remove android/gradlew
Would remove android/gradlew.bat
Would remove android/local.properties
Would remove flutter_git_test.iml
Would remove ios/Flutter/Generated.xcconfig
Would remove ios/Flutter/flutter_export_environment.sh
Would remove ios/Runner/GeneratedPluginRegistrant.h
Would remove ios/Runner/GeneratedPluginRegistrant.m
Would remove macos/Flutter/ephemeral/

git ls-files . --ignored --exclude-standard --others
.dart_tool/dartpad/web_plugin_registrant.dart
.dart_tool/package_config.json
.dart_tool/package_config_subset
.dart_tool/version
.idea/libraries/Dart_SDK.xml
.idea/libraries/KotlinJavaRuntime.xml
.idea/modules.xml
.idea/runConfigurations/main_dart.xml
.idea/workspace.xml
android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java
android/flutter_git_test_android.iml
android/gradle/wrapper/gradle-wrapper.jar
android/gradlew
android/gradlew.bat
android/local.properties
flutter_git_test.iml
ios/Flutter/Generated.xcconfig
ios/Flutter/flutter_export_environment.sh
ios/Runner/GeneratedPluginRegistrant.h
ios/Runner/GeneratedPluginRegistrant.m
macos/Flutter/ephemeral/Flutter-Generated.xcconfig
macos/Flutter/ephemeral/flutter_export_environment.sh

Flutter doctor
[✓] Flutter (Channel stable, 3.13.1, on macOS 13.5 22G74 darwin-x64, locale en-NL)
    • Flutter version 3.13.1 on channel stable at /Users/johannesroest/fvm/versions/3.13.1
    • Upstream repository https://github.com/flutter/flutter.git
    • Framework revision e1e47221e8 (2 days ago), 2023-08-22 21:43:18 -0700
    • Engine revision b20183e040
    • Dart version 3.1.0
    • DevTools version 2.25.0

[✓] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
    • Android SDK at /Users/johannesroest/Library/Android/sdk
    • Platform android-34, build-tools 32.1.0-rc1
    • Java binary at: /Applications/Android Studio.app/Contents/jbr/Contents/Home/bin/java
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)
    • All Android licenses accepted.

[✓] Xcode - develop for iOS and macOS (Xcode 14.3.1)
    • Xcode at /Applications/Xcode.app/Contents/Developer
    • Build 14E300c
    • CocoaPods version 1.11.3

[✓] Chrome - develop for the web
    • Chrome at /Applications/Google Chrome.app/Contents/MacOS/Google Chrome

[✓] Android Studio (version 2022.3)
    • Android Studio at /Applications/Android Studio.app/Contents
    • Flutter plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/9212-flutter
    • Dart plugin can be installed from:
      🔨 https://plugins.jetbrains.com/plugin/6351-dart
    • Java version OpenJDK Runtime Environment (build 17.0.6+0-17.0.6b829.9-10027231)

[✓] VS Code (version 1.79.2)
    • VS Code at /Applications/Visual Studio Code.app/Contents
    • Flutter extension can be installed from:
      🔨 https://marketplace.visualstudio.com/items?itemName=Dart-Code.flutter

[✓] Connected device (3 available)
    • MC3300x (mobile) •<PHONE_NUMBER>7000 • android-arm64  • Android 11 (API 30)
    • macOS (desktop)  • macos          • darwin-x64     • macOS 13.5 22G74 darwin-x64
    • Chrome (web)     • chrome         • web-javascript • Google Chrome 116.0.5845.110

[✓] Network resources
    • All expected network resources are available.

• No issues found!

This is not desirable, because now there are differences between a fresh checkout and a freshly created project

Hi @jsroest. Thanks for filing this issue. Can you explain more about the differences? I can't seem to see a difference between these.

Some files are not checked in, so they will not be there if you do a fresh checkout of the repository.
For example, if you work on a project with a coworker, your coworker will miss these files if he checks out the repository.

.dart_tool/dartpad/web_plugin_registrant.dart
.dart_tool/package_config.json
.dart_tool/package_config_subset
.dart_tool/version
.idea/libraries/Dart_SDK.xml
.idea/libraries/KotlinJavaRuntime.xml
.idea/modules.xml
.idea/runConfigurations/main_dart.xml
.idea/workspace.xml
android/app/src/main/java/io/flutter/plugins/GeneratedPluginRegistrant.java
android/flutter_git_test_android.iml
android/gradle/wrapper/gradle-wrapper.jar
android/gradlew
android/gradlew.bat
android/local.properties
flutter_git_test.iml
ios/Flutter/Generated.xcconfig
ios/Flutter/flutter_export_environment.sh
ios/Runner/GeneratedPluginRegistrant.h
ios/Runner/GeneratedPluginRegistrant.m
macos/Flutter/ephemeral/Flutter-Generated.xcconfig
macos/Flutter/ephemeral/flutter_export_environment.sh

Thanks for your response. These seem to be files specified in .gitignore, can you check them out?

Thanks for your response. These seem to be files specified in .gitignore, can you check them out?

I think @jsroest would like the .gitignore generated by default to include those files.

android/gradlew
android/gradlew.bat

I agree with those files. The gradle documentation says to commit the wrapper.
But, all the .dart_tool/* & .idea/* shouldn't be committed IMO, since it's mostly caching and user-specific configuration.

Most of those ignored files are created by the second step in the output log (Resolving dependencies...), which prepares the project for things like using an IDE, or using native tooling. This is intentional, because it makes the fresh project more immediately usable by the developer. If you want to skip that step, you can pass --no-pub.

now there are differences between a fresh checkout and a freshly created project.

That is correct; flutter creates various untracked files on the fly as a normal part of its operation.

For example, if you work on a project with a coworker, your coworker will miss these files if he checks out the repository.

Your co-worker will get their own versions of these files as soon as they interact with the repository (e.g., flutter get or flutter run).
Closing as these files are intentionally ignored, and also intentionally created post-template-instantiation as a convenience.

Thanks @stuartmorgan for the clear explanation. It makes total sense to me know. I was under the assumption that "flutter create" would only create files, and that "flutter pub get" would only download dependencies mentioned in the pubspec.yaml. Thanks for the insight!

Thanks for your response. These seem to be files specified in .gitignore, can you check them out?

I think @jsroest would like the .gitignore generated by default to include those files.

android/gradlew
android/gradlew.bat

I agree with those files. The gradle documentation says to commit the wrapper. But, all the .dart_tool/* & .idea/* shouldn't be committed IMO, since it's mostly caching and user-specific configuration.

Hi @BLKKKBVSIK,
I made some tooling to create a new flutter app containing our business template app, but with the flutter version of your choice. Just to be sure that all support files are created with the right flutter version. This works fine for a few years now, but for some time I noticed that some changes I made to ‘.idea’ and ‘iml’ files got automatically reverted. In the process of debugging that I noticed that flutter made some untracked files. I was not aware that these files are also created by a ‘flutter pub get’ command and assumed that to be a bug. I always thought that Android Studio or IntelliJ created the ‘.idea’ and ‘iml’ files on the fly. But I was wrong and learned something new 😎.


Kafka figures

Make an example that subscribes to a kafka topic and generates figures.

I'm not sure about the right way to hook up the RunRouter yet. I need to investigate.

All the RunRouter details should be handled by stream_documents_to_run. Something like this should do:
from bluesky_widgets.models.utils import run_is_live_and_not_completed
...

def export_thumbnails_when_complete(run):
    "Give a BlueskyRun, export thumbnail(s) to a directory when it completes."
    model =...
    model.add_run(run)
    view = HeadlessFigures(model)
    directory = "the uid or something"
    # If the Run is already done by the time we got it, export now.
    # Otherwise, schedule it to export whenever it finishes.
    if run_is_live_and_not_completed(run):
        run.events.completed.connect(view.export_all(directory))
    else:
        view.export_all(directory)

# stream_documents_into_runs organizes the flat stream of (name, doc) pairs
# from the dispatcher into BlueskyRun objects. When the dispatcher emits a 'start'
# document, a BlueskyRun will be created and immediately passed to
# export_thumbnails_when_complete.
# Future documents belonging to that run will be added to that BlueskyRun's internal DocumentCache.
# Signals on the run like `run.events.new_data` and `run.events.completed` can be
# used to detect updates. At any point, the (partial) data can be accessed
# as documents or as xarrays.
dispathcher.subscribe(stream_documents_into_runs(export_thumbnails_when_complete))

Updated all of the suggestions, no more warnings!

Added some commits to clean up after the renaming of bluesky_widgets.examples.utils.stream_data and other minor stuff. Merging.


Broken internet connection detection

VSCode Version: v1.28.2
OS Version: 10.13.5

Steps to Reproduce:

Load VSC

I'm using a VPN, I've never seen this before when I wasn't using a VPN.

Does this reproduce with all extensions disabled? (code --disable-extensions)

Probably, I can't reproduce it anymore.
I haven't changed my extensions in a while, what changed was: crappy WiFi and a VPN. You can't see this in the gif but I actually tried multiple times and VSCode would always detect that I had no internet connection, even though I was actually able to browse the internet.
Also the detection seemed too fast, maybe the isOffline value or whatever was cached for some reason? I don't know.

Let me know if you can repro.


How we can use yup.when() ?

I am trying something like this
`[
['yup.object'],
[
'yup.shape',
{
email: [
['yup.string'],
['yup.nullable'],
[
'yup.required',
'Bitte geben Sie eine gültige E-Mail-Adresse ein (maximal 320 Zeichen).',
],
],
      roleRespresentative: [['yup.boolean'], ['yup.default', 'false']],

      email2: [
        ['yup.string'],
        ['yup.nullable'],
        [
          'yup.when',
          'roleRespresentative',
          {
            is: true,
            then: [
              [
                'yup.required',
                'Bitte geben Sie eine gültige E-Mail-Adresse ein (maximal 320 Zeichen).',
              ],
            ],
          },
        ],
      ],
    },
  ],
]`

Hi, so I'm also not that deep into the code as I only maintain it now, but I played a little with your example it seems yup.shape makes problems, since I can't get the schema to transform when it's defined.
But the main problem is that it seems the new nested schema parts from yup.when won't get appended to the schema correctly.
So for now my guess is yup.when doesn't work correctly at this time.
Unfortunately we do not use the lib that much anymore so I can't say when I get around to investigate this problem.
Feel free to solve it yourself and make a PR if you have the time.


Refresh READMEs

What does this PR do?
Update documentation to fix inconsistencies and improve layout.
Motivation
Fix #126

@irabinovitch could you have a look please?


implement multassign for strings

import "console";

test := "test";
test = 2 * test;
console.println(test);
test *= 2;

returns an error
Can't assign int to string

it doesn't work for div, diveq or mod neither


Refactoring genericpilot implementation

What this PR does / why we need it:
Improvements to genericpilot package to encompass full process lifecycle
Special notes for your reviewer:
Still WIP
Release note:
NONE

/assign

/test e2e

/test e2e 1.8

/test e2e 1.7

/retest

/retest

/retest

/test e2e 1.7

/test e2e

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest

/retest


SPARQL over entailed graph

Hi,
thank you for your library.
We currently use it to enhance our SemWeb exercises with it.
It works out quite well.
One demand which I have for some exercises is to query the entailed graph with SPARQL.
From what I read,  the entailed graph can be only used inside the same cell:
For now you can only entail graphs in-place
In the example notebooks it shows that
%rdf graph entail-rdfs -l pets
%rdf graph draw -l pets

works, but the SPARQL query would need the cell magic (%%)  and not the line magic.
So is it possible to also create queries over entailed graph?
If not, would it be possible to also store the entailed graph in the store with a new label such that we can use this label for SPARQL queries in other cells.
What was the reason behind not storing the entailed graph?
Thank you
Best regards
Sven

Sorry for the late answer. With in-place, this definition is meant: https://en.wikipedia.org/wiki/In-place_algorithm
So when entailing a graph, it overwrites the non-entailed graph, this does not mean that you have to query it in the same cell.
This means that you can entail the graph with %rdf graph entail-rdfs -l pets in one cell and then query it in the next with %%rdf sparql -l pets.
I hope this helps.
Best regards
Lars

Hi Lars,
thank you for your answer.
Want I want to do is to query the entailed graph with a SPARQL query.
Here is a very small example notebook ( I need to zip it because github dosn't support jupyter notebooks directly) together with my current workaround (which I described above).
Maybe you know if there is a better way instead of writing a code cell with some python code and run the queries inside it.
Thanks
Best regards
Sven

As far as I know, RDFLib does not provide copy functionality for its graphs. And as RDFLib/OWL-RL does only operate in-place on graphs, RDFify does so as well.
It is indeed not possible to entail and query the graph in a single cell (without using python). I have deliberately not added the entailment functionality to the SPARQL submodule, as I think this would result in too much of a side effect as even SELECT queries would make changes to the graph. But it is possible, as said above, by first entailing the graph in one cell and then querying the entailed graph in the next one.
I have changed your notebook to use this approach.
Best regards
Lars

Hi Lars,
thanks for your reply.
This is exactly what I was searching for.
I thought I also tried this out but maybe not in the exact same way as you did.
Best regards
Sven


Troubleshooting Kaggle Integration in Olama Collab Integration Repository

Hello,
I am currently facing challenges with integrating the Olama Collab Integration repository with Kaggle. Although the repository mentions compatibility with Kaggle.com, it lacks detailed instructions or notebooks for seamless integration.
Despite my efforts to adapt the code and directory structure to Kaggle's environment, I have encountered persistent issues in achieving the desired functionality. As a result, I am seeking the assistance of the repository creator to collaborate on resolving these issues and ensuring successful integration with Kaggle.
I am eager to work together with the creator to overcome these obstacles and optimize the repository's performance on Kaggle. If possible, I would appreciate direct contact through my GitHub account or any linked social media platforms to facilitate communication and collaboration.
Furthermore, I have established a separate GitHub repository titled "Ollama Colab Integration for Kaggle," housing the modified versions of the files. You can access it here.
Thank you for considering my request for assistance
Warm regards,
Md.Fatin Ishraq
facebook

Hey,
Cool to hear there are more Kagglers out there!
We never really dropped Kaggle support but the scope and usecase shifted when working on the companion part.
Kaggle doesnt allow proxy-passing/having public endpoints via Cloud-Flare, and blocks alot of connections, and whenever you launch certain parts of gradio or streamllit they kill the notebook instance.
I myself use Kaggle with Ollama alot but in my experience running the UI also within that ENV made it reach a couple bottlenecks.
So we kept with the old way of running Ollama within a notebook defined in this Kaggle-Notebook:
https://github.com/Luxadevi/Ollama-Colab-Integration/blob/main/Old Version/ollama-publicV2kaggle.ipynb
Here we use R0lfs Nat python tunneling script that won't false flag for a remote connection and stays generally on.
Then you have the Ollama endpoint available and what i personally do is just run somewhere on a linux install since we can just kick off companion with a one liner:
curl https://raw.githubusercontent.com/Luxadevi/Ollama-Companion/main/install.sh | sh

There are some old parts about this notebook that can be optimized like

Removing-Cuda installer - not needed anymore
Changing some parts of the httpx and asyncio back (Jupyter is not well equipped for this out of the box)
Removing Ipython model-maker (yes this is how it all started :)

I myself removed these things but are filled with other testing things and my variables like IP and Ports for the backend, so i  dont need to do that again and again.
If you would like to try this with another way feel free, always open for a PR if  works well generally.
as said i did run streamlit over on kaggle but all around performance was too low with loading in big models, checking hash and the like while running inference and so on.
You can also use Ngrok as so many but Ngrok kicked me out or closed connections too many times to even consider :)
I hope i informed you well enough with this and will change the mentioned optimizations when im available.
Kind regards,
Luxa,

Additional info - Installer,
Within the installer there are some options to make your install add or disregards some features, these can be passed with a flag but are not documented, i moved on about making the UI part and am focusing on different projects right now so not everything is as updated as it could be.
Also in some parts because Streamlit was not as wel featured a while back compared to right now.
Last thing i want to mention is, there will be a update soon probably since my friend is building upon Companion and adding fine tuning and more quanting options.


Set Helsinki time zone when creating Talpa order

Context
PV-669
How Has This Been Tested?
Unit tests

Codecov Report

Merging #403 (c587ba3) into develop (4a6584b) will increase coverage by 0.01%.
The diff coverage is 100.00%.

@@             Coverage Diff             @@
##           develop     #403      +/-   ##
===========================================
+ Coverage    80.95%   80.97%   +0.01%
===========================================
  Files          149      149
  Lines         8783     8792       +9
===========================================
+ Hits          7110     7119       +9
  Misses        1673     1673

Files
Coverage Δ

parking_permits/talpa/order.py
35.65% <ø> (ø)

parking_permits/tests/test_utils.py
100.00% <100.00%> (ø)

parking_permits/utils.py
71.95% <100.00%> (+0.45%)
:arrow_up:

:mega: We’re building smart automated test selection to slash your CI/CD build times. Learn more


Add options in the config to control how the character encoding will work.

Addresses concerns of #143 (backport of #151)

LGTM


broken link in documentation

The link to mark series in
http://uber.github.io/react-vis/#/documentation/xy-plot/series
is broken.
It should be
http://uber.github.io/react-vis/#/documentation/xy-plot-series/mark-series
instead of
http://uber.github.io/react-vis/mark-series.md.

Should be resolved, marking as closed

Super impressed: Super quick !


test: synchronize bidi expectations changes for Bug 1756595

This PR can only be merged once Bug 1756595 is included in the Nightly build used by Puppeteer's CI.
There are some mandatory expectation changes that will need to happen anyway once that patch is available, but also ~10 currently skipped tests which should now pass.

@OrKoN should I investigate the failures or are they known intermittent issues?

@juliandescottes failures are probably outdated because there is a conflict in expectations now. I have not looked into conflicts, is it easy to solve?

Tried to rebase, let's see if it helps

Still some chrome failures, I guess intermittents since my update only changed Firefox expectations, I can try to re-push to see if this goes away.


v1.16.7 is available

https://github.com/go-gitea/gitea/releases/tag/v1.15.7

runs on debian bullseye without trouble btw.


Add a 'status' field to our state struct

When thinking about kill() vs delete(), a client needs to know (gracefully - w/o errors) when to call each. Which means it needs to be able to query the container to know what its current state is (running vs stopped).  This defines a property in our 'state' struct to convey that info.
Signed-off-by: Doug Davis<EMAIL_ADDRESS>

LGTM

I commented via email last night, but GitHub seems to have eaten my
comment.  Here it is again:
On Thu, May 26, 2016 at 05:32:14PM -0700, Doug Davis wrote:

When thinking about kill() vs delete(), a client needs to know
(gracefully - w/o errors) when to call each.

-1.
There is no race-free way to do this gracefully without errors, since
“‘state’, process changes, take action based on stale state” is always
possible.  If a client wants to start a container, just run ‘start’
and catch errors.  The same approach works for the other commands,
with the additional complication of a wait-before-delete dance like
@julz outlined in 1.

@wking the intent isn't to remove any chance of an error, the intent is to make it so that an error isn't part of the normal workflow just to figure out the state of a container.

On Fri, May 27, 2016 at 02:08:03PM -0700, Doug Davis wrote:

@wking the intent isn't to remove any chance of an error, the intent
is to make it so that an error isn't part of the normal workflow
just to figure out the state of a container.

So “decrease the likelyhood of generating errors” (and I agree that
this change would do that).  Why is that useful?  Is there a problem
with errors?
I think that the runtime needs to be careful in this case (e.g. I
don't like this risk of sending the ‘start’ signal to user-specified
code 1), but at the level of abstraction exposed by the spec
operations I see no such risks.  That doesn't mean that the risk isn't
there, but I think we should identify it (or some other use-case) more
clearly before landing a new field in the state.

I would prefer a status operation over a field in the state file.

@mrunalp we already have one:  https://github.com/duglin/runtime-spec/blob/master/runtime.md#query-state
The problem is that it doesn't return enough info and I doubt we want 2 ops that return almost the same info.

I meant status as a separate op that just returns the current run status of the container.
Sent from my iPhone

On May 31, 2016, at 9:49 AM, Doug Davis<EMAIL_ADDRESS>wrote:
@mrunalp we already have one: https://github.com/duglin/runtime-spec/blob/master/runtime.md#query-state
The problem is that it doesn't return enough info and I doubt we want 2 ops that return almost the same info.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or mute the thread.

LGTM.
@duglin @wking AFAIK this is most useful when use for things like inspect, not really for When thinking about kill() vs delete(), a client needs to know (gracefully - w/o errors) when to call each. though,  as runtime should try to make those operations idempotent.

@mrunalp why would another op that just returned the status be better than the state op that returns status along with the other info?

On Tue, May 31, 2016 at 10:02:56AM -0700, Daniel, Dao Quang Minh wrote:

@duglin @wking AFAIK this is most useful when use for things like
inspect…

This is getting into very fuzzy territory to me.  “I want to know
$PROPERTY because I want to know $PROPERTY” is hard to argue
for/against ;).  I'd rather keep the spec restricted to “I want to
know $PROPERTY because I neet it to take $ACTION” is much easier to
reason about (do we want to support $ACTION?  Do you really need
$PROPERTY to do it?).  So, what sort of actions does this information
let you take?

… not really for When thinking about kill() vs delete()… though,
as runtime should try to make those operations idempotent.

At least with the current spec, delete is not idempotent 1:
Attempting to delete a container that does not exist MUST generate
an error.

@crosbymichael state is static whereas the running status of a process is more dynamic. The information in the state file could get stale.

I think it will be hard to keep the status field in the state file correct and queries race free.

@mrunalp we are not talking about cat'ing a file.  The state response is dynamic as well and the status is correct it is returned.  Nothing static about it in the spec or in the runc implementation.

the spec doesn't mention state files any more - we put it all behind an op.

@crosbymichael Agree if the state isn't persisted in a file in a implementation (but anyway that is up to the implementation).

@duglin Needs rebase.

I think git is acting up again - there were not conflicts at all so the rebase shouldn't have been necessary.  Very odd.

oh man - had to rebase again.  Git is really acting up.

LGTM

LGTM


--slot : command not found in az webapp deployment source config-zip

az feedback auto-generates most of the information requested below, as of CLI version 2.0.62

Describe the bug
I am trying to run az webapp deployment source config-zip with --slot param but it's giving me --slot: command not found error
To Reproduce
Install latest az cli. I also have webapp extension installed. Run webapp deployment command with config-zip and provide slot param.
Expected behavior
It should deploy the app in defined slot.
Environment summary
{
"azure-cli": "2.5.1",
"azure-cli-command-modules-nspkg": "2.0.3",
"azure-cli-core": "2.5.1",
"azure-cli-nspkg": "3.0.4",
"azure-cli-telemetry": "1.0.4",
"extensions": {
"webapp": "0.2.24"
}
}

webapp

cc @fengzhou-msft for awareness