[CELEBORN-1588] Use Platform.allocateDirectBuffer instead of ByteBuffer.allocateDirect

What changes were proposed in this pull request?
Use Platform.allocateDirectBuffer instead of ByteBuffer.allocateDirect.
Why are the changes needed?
The difference between ByteBuffer.allocateDirect and Platform.allocateDirectBuffer is that the latter bypasses / ignores the JVM's -XX:MaxDirectMemorySize limit. It's recommend to replace ByteBuffer.allocateDirect with Platform.allocateDirectBuffer, which way has already been mentitioned in https://github.com/apache/spark/pull/47733#pullrequestreview-2251276385.
Does this PR introduce any user-facing change?
No.
How was this patch tested?
CI.

Ping @cxzl25, @FMX.

Are there any benefits to this change?
Celeborn respects the config "-XX:MaxDirectMemorySize" and does not want to use memory above the limit. This PR is not suitable in some ways.


Merge Deep-Insights

Related to: https://github.com/CartoDB/cartodb/issues/13284
Team discussion

BOOM


DO NOT MERGE: Added TSGs to exception messages

Added TSGs to exception messages
Closes https://github.com/Azure/azure-sdk-for-java/issues/15959
Related PR : https://msdata.visualstudio.com/CosmosDB/_git/CosmosDB/pullrequest/384158

the links point to dot net troubleshooting guides. are we going to have different pages for dotnet and java? or add section for java in the tsg?

Yes, I plan to update the docs accordingly, will make sure customer's don't get confused by the docs title or content

@moderakh @j82w  - please check the updated code, I have created new links for java SDK troubleshooting, request timeout and not found guides.

looks great Kushagra. one small thing I noticed is the common TSGs all have links to DotNet perf guide and troubleshooting guide only and not to Java.
see the bottom of https://docs.microsoft.com/en-us/azure/cosmos-db/troubleshoot-not-found

Great catch @moderakh  - I will update all the common troubleshooting guides with both .Net and Java perf guides.
Good catch :)

@moderakh  - here you go :)
https://github.com/MicrosoftDocs/azure-docs-pr/pull/136054


error while loading shared libraries: libLLVM-14.so

Hi, I was building an example when I got this error. I don't know how to deal with this lib error, please help me, thanks.
I use kernel version 5.8.0-63-generic, llvm version 11.0

you should  update LLVM , from 11 to 14.
or try
cd  /usr/lib/x86_64-linux-gnu
sudo ln -s libLLVM-11.1.0.so libLLVM-14.so

this is a  guess， I  can't  sure it work.  just a try .

I have just had it.
Not even gcc and llvm installs helped. Only:
aptitude remove libc6 (or downgrade it).
Root problem: new apt sources messed up its glibc version.
Now, works:
root@localhost:~/downloads_Termux/CTranslate2# uname -a                                                   Linux localhost 6.2.1-PRoot-Distro #1 SMP PREEMPT Thu Mar 17 16:28:22 CST 2022 aarch64 GNU/Linux          root@localhost:~/downloads_Termux/CTranslate2# aptitude show libc6                                        Package: libc6                                       Version: 2.36-9+deb12u7                              State: installed                                     Automatically installed: yes                         Multi-Arch: same                                     Priority: optional                                   Section: libs                                        Maintainer: GNU Libc Maintainers<EMAIL_ADDRESS>                                        Architecture: arm64                                  Uncompressed Size: 23.7 M                            Depends: libgcc-s1                                   Recommends: libidn2-0 (>= 2.0.5~)                    Suggests: glibc-doc, debconf | debconf-2.0,                    libc-l10n, locales, libnss-nis,                      libnss-nisplus                             Breaks: aide (< 0.17.3-4+b3), busybox (< 1.30.1-6),          chrony (< 4.2-3~), fakechroot (< 2.19-3.5),          firefox (< 91~), firefox-esr (< 91~),                gnumach-image-1.8-486 (< 2:1.8+git20210923~),        gnumach-image-1.8-486-dbg (<                         2:1.8+git20210923~),                                 gnumach-image-1.8-xen-486 (<                         2:1.8+git20210923~),                                 gnumach-image-1.8-xen-486-dbg (<                     2:1.8+git20210923~), hurd (<                         1:0.9.git20220301-2), ioquake3 (<                    1.36+u20200211.f2c61c1~dfsg-2~),                     iraf-fitsutil (< 2018.07.06-4), libgegl-0.4-0        (< 0.4.18), libtirpc1 (< 0.2.3), locales (<          2.36), locales-all (< 2.36), macs (<                 <IP_ADDRESS>-3~), nocache (< 1.1-1~), nscd (<             2.36), openarena (< 0.8.8+dfsg-4~),                  openssh-server (< 1:8.1p1-5),                        python3-iptables (< 1.0.0-2), r-cran-later (<        0.7.5+dfsg-2), tinydns (< 1:1.05-14),                valgrind (< 1:3.19.0-1~), wcc (<                     0.0.2+dfsg-3)                                Description: GNU C Library: Shared libraries          Contains the standard libraries that are used by     nearly all programs on the system. This package      includes shared versions of the standard C library   and the standard math library, as well as many       others.                                             Homepage: https://www.gnu.org/software/libc/libc.htmlTags: role::shared-lib                                                                                root@localhost:~/downloads_Termux/CTranslate2#


Added imread, imsave and synchronize functionality

You can now just use imread(filename) and the library uses a local file on the cluster if it finds a matching one, or it downloads the file to a temporary location from the fileserver and accesses that one.
Similarly, imsave(filename, data), saves the file if the path is accessible. Otherwise, it saves to a temp file and then copies that to the final location (on the fileserver or project space) using the datamover tools.
The best way to test is to install the test singularity image for biapol-taurus:
git clone https://gitlab.mn.tu-dresden.de/bia-pol/singularity-devbio-napari.git
cd singularity-devbio-napari
./install.sh biapol_taurus

and then open a notebook with the devbio-napari_biapol_taurus kernel.
inside the notebook run:
from biapol_taurus import ProjectFileTransfer
from skimage.io import imshow

# Define the source directory. /grp/g_biapol/ is the mount point at the export node. HPCsupport can tell us this:
source_dir = "/grp/g_biapol/"

# Define the target directory. /projects/p_bioimage/ is the project space. HPCsupport told us that when we applied for the project:
target_dir = "/projects/p_bioimage/"

# We setup a connection:
pft = ProjectFileTransfer(source_dir, target_dir)

image = pft.imread('data/test/blobs19.tif')
# show image
imshow(image)

pft.imsave('/projects/p_bioimage/till/blobs_saved.tif', image)

thanks a lot for the code review. I will implement the changes you suggested when I am back from vacation (today I will focus on resubmitting a paper).
Cheers,
Till

@haesleinhuepf I now implemented the changes you suggested.
I left two comments open for you to check if the way I implemented the changes is o.k. with you.


add prettier and format all files

cc: @jvoros

Codecov Report

Merging #198 into master will increase coverage by 1.11%.
The diff coverage is 59.18%.

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

@jvoros Can we merge this one first before your spinner fix?

Definitely. Totally missed this PR.
Prettier will be great.
On Fri, Jul 7, 2017 at 11:25 Derek Sifford<EMAIL_ADDRESS>wrote:

@jvoros https://github.com/jvoros Can we merge this one first before
your spinner fix?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/aliemteam/aliemcards/pull/198#issuecomment-313743437,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ACVxJr8do-cU9tofGT4PR0DgVRMx4nA0ks5sLmn2gaJpZM4N9SmZ
.


Add an event for health check failures.

comments addressed.  ptal.

Please see my now-hidden comment: https://github.com/GoogleCloudPlatform/kubernetes/pull/4408#discussion_r24645257

oops, comments crossed paths on the wire.  addressed.

LGTM

@brendandburns Out of an abundance of caution I reverted this change because it caused v1.3 to fail on both Shippable and Travis. Rerunning, Travis is green, but [Shippable v1.3] (https://app.shippable.com/builds/54de25cbc44f060e00737a50) is still failing. The error seems transient. Could you squash the commits and resubmit.


Add weekends checker

add weekends checker for missing updates notifications: ignoring updates created on weekend

 [TARIFF17] build into the alert a checker that if it was a bank holiday yesterday/today then to add a day onto the checker

 [TARIFF17] build into the alert a checker that if it was a bank holiday yesterday/today then to add a day onto the checker

 [TARIFF17] build into the alert a checker that if it was a bank holiday yesterday/today then to add a day onto the checker

 [TARIFF17] build into the alert a checker that if it was a bank holiday yesterday/today then to add a day onto the checker


add more markdown extensions

Hi,
I'm using .mkd for all my markdown files because .md is historically for Modula-2. I prefer .mkd over other alternative extensions because it is shorter and clearer.
So each time I install vscode on a new machine I'm adding
    "files.associations": {
        "*.mkd": "markdown"
    },

to settings.json.
I think this extension (as some other) should be added and recognized by default: https://superuser.com/questions/249436/file-extension-for-markdown-files
I'm also asking myself if it is relevant to keep .workbook as it is not standard but used only by one app: Xamarin.
I don't know if it is the right file to push that change.

Thanks!


Add Andrew and Alessandro as curator

They're helping out with triaging, so just making this official :)
ping @aboch @andrewhsu @icecrime

LGTM :+1:

LGTM


Allow pinning network shares to favourites

What's the Problem?
At the moment, it's not possible to pin a network share (like \\<IP_ADDRESS>\ ) to the favourites list / cloud drives / network drives.
You can pin the subfolders, but not the root.
Solution/Idea
Add a command to add the current folder to the favourite list.
Alternatives
Add a specific function to add network shares to the favourite list
Priorities

Capability
Priority

This proposal will allow developers to access network shares with more ease
Must

This proposal will allow end users to accomplish access network shares with more ease
Must

This proposal will allow developers to pin the current folder with more ease
Should

This proposal will allow end users to pin the current folder
Should

Files Version
Versione <IP_ADDRESS> OS Version: 10.0.22000.556
Windows Version
Windows 11 21H2 22000.556
Comments

Atm you should be able to pin it under Network by right clicking on network and choosing "map network drive". From the dialog you'll be able to choose whether to actually map the share as a network drive or only add it as a link.

Is this still an issue in the preview version? https://files.community/download/preview


DEV | Property Access Controller

Overview
Added middleware unit test helper.
Removed try catch blocks.
Removed redundant if statements.
Fixed unit tests accordingly.
Azure board

Thank you @MathildaShongwe15  for pointing out the other controller instantiation which was unnecessary.👍


Corrected iOS/tvOS examples

There were a couple unimplemented protocols in the example targets.  Corrected these along with a couple warnings.

thanks for the request.
Unfortunately i'll have close it.
I'm actively making a bunch of changes on master Branch and on local, which is why the master branch was a mess before the push.
But thanks for alerting me to it.

No worries.
On Fri, Sep 8, 2017 at 12:24 PM JTAppleCalendar<EMAIL_ADDRESS>wrote:

thanks for the request.
Unfortunately i'll have close it.
I'm actively making a bunch of changes on master Branch and on local,
which is why the master branch was a mess before the push.
But thanks for alerting me to it.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/patchthecode/JTAppleCalendar/pull/550#issuecomment-328150235,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAr3mEH2vWYXhIcEEmuZuyIb3PVFZlziks5sgWoggaJpZM4PJu7V
.

--
-Evan


Upgrade Remote API Version for Docker

I have a docker version < 1.7.1 . which has the Client API version: 1.18.
I need Client API version: 1.19. Is there a way I can upgrade my APIs alone with newer features (ie upgrade to 1.19) without upgrading the docker itself.
If not can we have this as a feature?

Hi!
Please read this important information about creating issues.
If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
This is an automated, informational response.
Thank you.
For more information about reporting issues, see https://github.com/docker/docker/blob/master/CONTRIBUTING.md#reporting-other-issues

BUG REPORT INFORMATION
Use the commands below to provide key information from your environment:
docker version:
docker info:
uname -a:
Provide additional environment details (AWS, VirtualBox, physical, etc.):
List the steps to reproduce the issue:
1.
2.
3.
Describe the results you received:
Describe the results you expected:
Provide additional info you think is important:
----------END REPORT ---------
#ENEEDMOREINFO

Nope. Sorry, but client and server are incompatibles and they'd expect information going back and forward that might or might not be in the json payloads.


Research Performance and Usability Testing

Challenge
How do we effectively run Performance & Usability Testing? Based on the findings, recommend which of the two should be implemented in Release 2.
Time box
This experiment is limited to 2 days
Findings
With regards to PHP and Laravel, performance testing is done mainly through use of automatic tools such as AppOptics for PHP or Blackfire for Laravel. These tools perform stress-tests of the application to ensure that it can withstand heavy loads.
As for Usability testing, this is preferably done manually. Usability testing is giving early access to a limited number of users . By providing app access to as many user types as possible, their feedback can be used to find where the app's UI is lacking, where processes are too complicated, or if features are unintuitive/unnecessary/absent.
Recommendations
After presenting the solutions found and discussing them with the team, we believe that focusing on usability testing will have a larger benefit on our app for two reasons:

Our app will potentially be complex, especially since the prerequisites to book rooms are varied depending on both the room and the event being held. A focus on usability testing will help minimize the confusion users may have by pin-pointing where those confusions are.

The logistic challenges of setting up performance testing through Concordia's servers outweighed the benefits the app would receive, especially since this app would ideally not be used for extended periods at once.

Updated issue with my findings and the recommendation the team came to after discussion


Working with immutable value

Hey,
How do you do when you want to change a value that is immutable, and reuse use the changed value in other callback ?
I'm asking this because we work on ResponseInterface from PSR7 which are immutable, right now we use a Promise, but we would love to use async-interop in the near futur (once it's close to be stable).
But depending on Awaitable seems to be hard to do for immutable data as we would have to do the following:
$tempResponse = null;

$awaitable->when(function($error, $response) use (&$tempResponse ) {
    $tempResponse = $response->withHeader();
});

$awaitable->when(function($error, $response) use (&$tempResponse) {
    $tempResponse = $tempResponse->withBody();
});

And this get even weird when the when method is called somewhere else as we would have to transfer the reference to $tempResponse.
Or is there a better way ?

Okay nevermind we should just do the following:
$awaitable->when(function($error, &$response) {
    $response = $response->withHeader();
});

But is it valid for the spec ?

The spec doesn't specify what happens then. It's undefined brhavior. The spec mandates the passed callback to not include refs. If they do, that's the callers fault.

Don't do that. Resolved values MUST NOT change, that's what the spec says.
You better just use coroutines and it will work like in a synchronious world.

So the following ?:
$awaitable->when(function($error, &$response) {
    yield $response->withHeader();
});

Nah.
You need to create a new Awaitable. Check the library you use for Awaitable creation.
A library like Amp has a function pipe() which transforms the Awaitable and returns a new one:
$awaitable = \Amp\pipe($awaitable, function($response) { return $response->withHeader(); });
$awaitable->when(function($error, $response) { ... });

This pipe function then looks like (pseudo-code):
function pipe($awaitable, $callback) {
    // the Future can be resolved or failed and may be asked for the related Awaitable
    $future = new Future;
    $awaitable->when(function($error, $result) use ($callback, $future) {
         if (!$error) {
             $future->resolve($callback($result));
         } else {
             $future->fail($error);
         }
    });
    return $future->getAwaitable();
}

You definitely ought to not change the value of an Awaitable directly. The Awaitable should always call the callbacks passed to when() with the same $error, $result pair.

Check the library you use for Awaitable creation.

That's the point we don't want to be link to any library implementing "Awaitable" as we want the user using our lib to choose his own implementation.
So i will have to implement this in a generic way :/
For reference i'm speaking about this interface : https://github.com/php-http/httplug/blob/master/src/HttpAsyncClient.php and we are using a huge number of decorator to handle various thing.

The standard is really just ensuring pure interoperability. It does - intentionally - not provide functions for Awaitable manipulation. That's the task of the libraries.
The user of your lib will still be able to choose his own implementation. You can use some library and at the boundaries of your library, all you are communicating is Awaitables. Awaitables from one library can absolutely just used by every other library  the user wishes to use. Just because your library is based on e.g. Amp, that doesn't mean that an user cannot use it in a React context - after all, that's the whole point of interop.

Thanks for the answer, the pipe thing should be documented IMO (or referenced like you did), as many people rely on this (as they have often the chainable promise in their mind when working with async)


Lerna with workflow icons

Description
Switch from private @spectrum/spectrum-icons package to open sourced @adobe/spectrum-css-workflow-icons package.
Related Issue

Motivation and Context

How Has This Been Tested?

Screenshots (if appropriate):
Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)

Checklist:

[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[ ] I have read the CONTRIBUTING document.

@jianliao will wait on this PR until color icons are in. Thanks!

@lazd Color icons were in.

Closed as lerna branch was merged to master branch. Will create another PR against master branch.


Rust syntax highlighting breaks with raw strings in attributes

VSCode Version: 1.44.2

When raw string literals that use ##s appear in attributes in a Rust file, syntax highlighting breaks.
Steps to Reproduce:

Copy the following code into a Rust source file:

#[cfg(feature = r#"""#)]
const _: () = ();

You will get something similar to the following:

Does this issue occur when all extensions are disabled?: Yes

Looks like that's not a permitted raw string literal because double quotes are not permitted in raw string literals: https://rahul-thakoor.github.io/rust-raw-string-literals/
https://doc.rust-lang.org/reference/tokens.html#raw-string-literals

Raw string literals can contain double quotes by surrounding the opening and closing quotes with an equal number of pound signs, as in r#""Hello""#, r##""Hello""##, etc.

All Unicode characters contained in the raw string body represent themselves, the characters U+0022 (double-quote) (except when followed by at least as many U+0023 (#) characters as were used to start the raw string literal) or U+005C () do not have any special meaning.
Examples for string literals:
"foo"; r"foo";                     // foo
"\"foo\""; r#""foo""#;             // "foo"

"foo #\"# bar";
r##"foo #"# bar"##;                // foo #"# bar

"\x52"; "R"; r"R";                 // R
"\\x52"; r"\x52";                  // \x52

Such literals are already highlighted correctly in VSCode when used outside of attributes, which can be demonstrated by pasting the following snippet into a Rust source file:
fn main() {
    println!(r#""Hello, world!""#);
}

Thanks for the additional info! Moved to the owning repo: https://github.com/zargony/atom-language-rust/issues/151


readme barcode only

this says "barcode only" when I think you mean "assembly / genes only"
readme barcode only

Done :)


Add Continuations to help prevent memory leaks

This PR adds a Continuation abstraction to Suspension to help avoid accidental memory leaks. If all Continuation objects associated with a Suspension are destroyed, the associated fiber is destroyed.

Related to #42 and #52.

Closing in favor of #52.


Reduce docker base image size

clean up unneeded files in binder postBuild
only copy notebook files
add script for local docker runs

only saves a couple hundred mb compared to the released images:
chris@xanadu:~/code/nessie-demos$ docker images
REPOSITORY                                  TAG                                        IMAGE ID       CREATED         SIZE
r2d-2e1646306922                            latest                                     f6d44866c11c   4 hours ago     5.77GB
r2d-2e1646306500                            latest                                     f6d44866c11c   4 hours ago     5.77GB
projectnessie/nessie-binder-demos           e12478cfb3447af4bc26e535a9daffe374233aa1   c17f6a22dd49   4 hours ago     5.77GB
(...)
ghcr.io/projectnessie/nessie-binder-demos   7fb962b09182c5f60ac2f80bbabb693290f3f741   0f701f74995f   2 months ago    6.49GB

but better than nothing.
also the demos are now easier to use because the notebooks folder in the image does not contain unneeded files anymore, just the notebooks.
Instead of just documenting the local docker image build process for testing purposes i wrote a script that automates it.

@omarsmak i've addressed all your comments
also found another way to reduce the image size, so we reduce it by ~1GB in total now:
REPOSITORY                                  TAG                                        IMAGE ID       CREATED             SIZE
r2d-2e1646392563                            latest                                     daa146619274   15 minutes ago      5.46GB
projectnessie/nessie-binder-demos           294ec5908c3b7aa970d99a2f5c7a669773cb591d   c95d9ca26b8a   16 minutes ago      5.46GB
(..)
projectnessie/nessie-binder-demos           e12478cfb3447af4bc26e535a9daffe374233aa1   14bf09fb62ef   2 hours ago         5.76GB
(..)
ghcr.io/projectnessie/nessie-binder-demos   7fb962b09182c5f60ac2f80bbabb693290f3f741   0f701f74995f   2 months ago        6.49GB

A question, does that linking working with pyflink? I presume all notebooks are working from the docker image?

yes to both answers, i was rerunning all the notebooks locally with all cells executing without errors

workflow on main pushed the new image successfully:
Successfully pushed ghcr.io/projectnessie/nessie-binder-demos:294ec5908c3b7aa970d99a2f5c7a669773cb591d

https://github.com/orgs/projectnessie/packages/container/nessie-binder-demos/16188982?tag=294ec5908c3b7aa970d99a2f5c7a669773cb591d


Discord Server

The discord server doesn't exist anymore.

https://discord.gg/2mCKgev5w9
On Sunday, December 12, 2021, Alpha_Video bot @.***>
wrote:

Hey thanks for creating an issue. Andrew will normally respond within 24
hours.
—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/unofficial-skills/alpha-video/issues/104#issuecomment-991950863,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AKZ55XY3CUFQTBPCSAKKL3LUQTVMBANCNFSM5J4RXZTA
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

I can't write in the chats though


No such file or directory @ rb_sysopen - tmp/rspec_guard_result

I'm getting the following failure, intermittently but very regularly:
Guard::RSpec failed to achieve its <run_on_modifications>, exception was:
Errno::ENOENT: No such file or directory @ rb_sysopen - tmp/rspec_guard_result

Here's the command I'm running with guard:
guard :rspec, cmd: "zeus rspec --tag ~js", all_after_pass: true, failed_mode: :none do

The error might be only when running acceptance specs with capybara, but it looks like it's failing before actually running any specs and I haven't been able to narrow it down because it's happening maybe once in every 15 runs.
Sounds similar to #316 and maybe #314, but @e2 said to report crashes as new issues (https://github.com/guard/guard-rspec/issues/316#issuecomment-108604997)
I'm using:

guard-rspec-4.5.2
rspec 3.2.0
ruby 2.2.0
rails 4.2.2

Project: https://github.com/dgmstuart/swingoutlondon2/tree/ad42c55c2b6dbd79be3487fc155e3d967a673448
Stack trace:
Guard::RSpec failed to achieve its <run_on_modifications>, exception was:
> [#] Errno::ENOENT: No such file or directory @ rb_sysopen - tmp/rspec_guard_result
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-rspec-4.5.2/lib/guard/rspec/results.rb:11:in `readlines'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-rspec-4.5.2/lib/guard/rspec/results.rb:11:in `initialize'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-rspec-4.5.2/lib/guard/rspec/runner.rb:76:in `new'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-rspec-4.5.2/lib/guard/rspec/runner.rb:76:in `_command_output'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-rspec-4.5.2/lib/guard/rspec/runner.rb:94:in `_process_run_result'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-rspec-4.5.2/lib/guard/rspec/runner.rb:47:in `block in _run'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-rspec-4.5.2/lib/guard/rspec/runner.rb:45:in `tap'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-rspec-4.5.2/lib/guard/rspec/runner.rb:45:in `_run'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-rspec-4.5.2/lib/guard/rspec/runner.rb:32:in `run'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-rspec-4.5.2/lib/guard/rspec.rb:42:in `block in run_on_modifications'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-rspec-4.5.2/lib/guard/rspec.rb:48:in `_throw_if_failed'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-rspec-4.5.2/lib/guard/rspec.rb:42:in `run_on_modifications'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-2.12.6/lib/guard/runner.rb:82:in `block in _supervise'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-2.12.6/lib/guard/runner.rb:79:in `catch'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-2.12.6/lib/guard/runner.rb:79:in `_supervise'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-2.12.6/lib/guard/runner.rb:61:in `block (3 levels) in run_on_changes'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-2.12.6/lib/guard/runner.rb:56:in `each'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-2.12.6/lib/guard/runner.rb:56:in `block (2 levels) in run_on_changes'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-2.12.6/lib/guard/runner.rb:119:in `block (2 levels) in _run_group_plugins'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-2.12.6/lib/guard/runner.rb:117:in `each'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-2.12.6/lib/guard/runner.rb:117:in `block in _run_group_plugins'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-2.12.6/lib/guard/runner.rb:116:in `catch'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-2.12.6/lib/guard/runner.rb:116:in `_run_group_plugins'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-2.12.6/lib/guard/runner.rb:54:in `block in run_on_changes'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-2.12.6/lib/guard/runner.rb:53:in `each'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-2.12.6/lib/guard/runner.rb:53:in `run_on_changes'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-2.12.6/lib/guard/internals/queue.rb:23:in `process'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-2.12.6/lib/guard/commander.rb:43:in `start'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-2.12.6/lib/guard/cli/environments/valid.rb:16:in `start_guard'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-2.12.6/lib/guard/cli.rb:122:in `start'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/thor-0.19.1/lib/thor/command.rb:27:in `run'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/thor-0.19.1/lib/thor/invocation.rb:126:in `invoke_command'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/thor-0.19.1/lib/thor.rb:359:in `dispatch'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/thor-0.19.1/lib/thor/base.rb:440:in `start'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-2.12.6/lib/guard/aruba_adapter.rb:32:in `execute'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-2.12.6/lib/guard/aruba_adapter.rb:19:in `execute!'
> [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-2.12.6/bin/_guard-core:11:in `<main>'

Actually it comes out with odd staggering in my terminal, so it's more like this:
Guard::RSpec failed to achieve its <run_on_modifications>, exception was:
                                                                                > [#] Errno::ENOENT: No such file or directory @ rb_sysopen - tmp/rspec_guard_result
                       > [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-rspec-4.5.2/lib/guard/rspec/results.rb:11:in `readlines'
                                                                                > [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-rspec-4.5.2/lib/guard/rspec/results.rb:11:in `initialize'
                                                                                > [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-rspec-4.5.2/lib/guard/rspec/runner.rb:76:in `new'
                                                                                > [#] /usr/local/var/rbenv/versions/2.2.0/lib/ruby/gems/2.2.0/gems/guard-rspec-4.5.2/lib/g
# etc...

Thanks for the report. It's failing in a completely different area: either the test output file is not being created, or it's deleted before it's being processed (or something just as strange).
Guard::RSpec uses a custom formatter (lib/guard/rspec_formatter.rb), which is supposed to create a file with the test results. RSpec is supposed to call the formatter's :dump_summary method, which writes the RSpec failures into a file tmp/rspec_guard_result (relative to the current directory).
You might try the Guard::RSpec cmd_additional_args options to redirect any output, e.g.
guard :rspec, cmd: "zeus rspec --tag ~js", all_after_pass: true, failed_mode: :none, cmd_additional_args: ' | tee -a rspec_errors.log' do
RSpec could be crashing for some reason - and zeus may be hiding the output when that happens.
If this is still relevant and you have time, let me know and I'll add some debugging/diagnostics for you to check - to find out what happens in the formatter before you're getting this error.

Thanks for the reply. Debugging/diagnostics would be great - I'm happy to spend some time getting to the bottom of this :)

Also, now that you say that about the formatter I'm wondering if the issue could be that I'm using the Fuubar formatter, which probably behaves a bit differently to other formatters. I'll try it without that.

I've create a branch which logs calls and errors related to the formatter:
In your Gemfile:
gem 'guard-rspec', github: 'guard/guard-rspec', branch: 'debug_logging_for_formatter'

and run: bundle update guard-rspec
If you get the error again, there should be some hints in the guard_rspec_debug.log file.
I'll work out some proper diagnostic mode (and release it) once we get to the bottom of this.
Thanks!

Awesome! Thanks - I'll enable this when I'm in that code next.
On 23 June 2015 at 14:56, Cezary Baginski<EMAIL_ADDRESS>wrote:

I've create a branch which logs calls and errors related to the formatter:
In your Gemfile:
gem 'guard-rspec', github: 'guard/guard-rspec', branch: 'debug_logging_for_formatter'
and run: bundle update guard-rspec
If you get the error again, there should be some hints in the
guard_rspec_debug.log file.
I'll work out some proper diagnostic mode (and release it) once we get to
the bottom of this.
Thanks!
—
Reply to this email directly or view it on GitHub
https://github.com/guard/guard-rspec/issues/326#issuecomment-114514714.

Hmm - I've got another crash, but the debug log doesn't show anything unusual:
D, [2015-07-10T17:10:33.806805 #44628] DEBUG -- : dump_summary writing summary
D, [2015-07-10T17:10:33.807023 #44628] DEBUG -- : write_summary: 108 examples
D, [2015-07-10T17:13:50.837635 #44686] DEBUG -- : dump_summary writing summary
D, [2015-07-10T17:13:50.838233 #44686] DEBUG -- : write_summary: 1 examples
D, [2015-07-10T17:13:59.471677 #44702] DEBUG -- : dump_summary writing summary
D, [2015-07-10T17:13:59.471944 #44702] DEBUG -- : write_summary: 1 examples
D, [2015-07-10T17:14:04.312027 #44717] DEBUG -- : dump_summary writing summary
D, [2015-07-10T17:14:04.312240 #44717] DEBUG -- : write_summary: 1 examples
D, [2015-07-10T17:14:15.913445 #44733] DEBUG -- : dump_summary writing summary
D, [2015-07-10T17:14:15.913666 #44733] DEBUG -- : write_summary: 1 examples
D, [2015-07-10T17:15:16.871907 #44762] DEBUG -- : dump_summary writing summary
D, [2015-07-10T17:15:16.872476 #44762] DEBUG -- : write_summary: 23 examples
D, [2015-07-10T17:15:21.101407 #44772] DEBUG -- : dump_summary writing summary
D, [2015-07-10T17:15:21.101632 #44772] DEBUG -- : write_summary: 23 examples
D, [2015-07-10T17:15:25.763609 #44788] DEBUG -- : dump_summary writing summary
D, [2015-07-10T17:15:25.763826 #44788] DEBUG -- : write_summary: 23 examples

I sent a PR to fix the issues with Guard::RSpec - since you're using Zeus, there's a special workaround (mentioned in the Readme). Maybe I should detect the issue better.
The results of running zeus test on your project:
Pending: (Failures listed here are expected and do not affect your suite's status)
  1) EventGenerator Validations validates that date is a date
     # Not yet implemented
     # ./spec/models/event_generator_spec.rb:13
  2) EventInstance Validations validates that date is a date
     # Not yet implemented
     # ./spec/models/event_instance_spec.rb:12
  3) Admin adds an event with invalid venue postcode
     # Not yet implemented
     # ./spec/acceptance/create_event/create_event_with_venue_spec.rb:27
Finished in 12.9 seconds (files took 8.1 seconds to load)
110 examples, 0 failures, 3 pending
Randomized with seed 57825

If you have a different issue, just open a new issue and link to the repo so I can reproduce this.
Thanks very much for the reports and the repo to test - it helped a lot!

Sorry - there's still an issue when running from Guard - I'll check it out...

@e2 the error complained about
tmp/rspec_guard_result

While the zeus config sets
tmp/guard_rspec_results.txt

Is that intended?

I'll need to rework the error handling completely, because it's too complex to work out what's the problem and how to fix it.

OK - many thanks for looking into it!

Release as 4.6.1. Open new issues if you have any.
In 4.6.1, if you don't have a custom Zeus play, there should be a warning linking to this wiki entry: https://github.com/guard/guard-rspec/wiki/Warning:-no-environment
I should create a PR for Zeus for this though ...

Great - thanks so much for your work :heart:

Glad to help! I wish this all could be a lot simpler. Web development is hard work these days...

I've got the same error :(

I'm getting this with monotonous regularity now.

@vyorkin @suranyami Are you on guard-rspec 4.6.1 or later? If not, please upgrade, and if so then please follow the advice above and raise new issues.
You'll want to include the following:

Gem versions
The exact guard command you're running
The full console output that you're getting

Also try passing the -b flag in your guard command to see if that gives you a more detailed backtrace.
Good luck :)

See comments in #359

@suranyami :+1:


Release notes for next release

[x] Telemetry collection in https://github.com/pybamm-team/PyBaMM/pull/4441
[ ]

I believe it would be good to have the telemetry info elsewhere, in addition to the release notes (I suggest under "About us"). Let me know what you think and I will open a PR @valentinsulzer @agriyakhetarpal. This way we can release that as soon as the release comes out, and then we can edit the release notes without rushing.

I believe it would be good to have the telemetry info elsewhere, in addition to the release notes (I suggest under "About us"). Let me know what you think and I will open a PR

Sounds good to me, thanks, @brosaplanella!

I want to make a LinkedIn post about the release so merging this now and we can always edit them afterwards.


Notebook dependency Issues urlib

With default Watson Studio 3.6 Python Environment I had to downgrade urlib in the example Notebooks
from time import time from random import random import logging import sys try:     **!python -m pip install "urllib3<1.25"**     import pywren_ibm_cloud as pywren except:     !{sys.executable} -m pip install pywren-ibm-cloud     import pywren_ibm_cloud as pywren

What was the error/exception?

Similar like this: https://github.com/urllib3/urllib3/issues/1571

Currently urlib is not pinned anymore in requirements. So there is no need to use specific urllib version


chore: bump arabica-6 id

Overview
Forgot in the #180 😓

Checklist

[ ] New and updated code has appropriate documentation
[ ] New and updated code has new and/or updated testing
[ ] Required CI checks are passing
[ ] Visual proof for any user facing features like CLI or documentation updates
[ ] Linked issues closed with keywords

@Bidon15  already merged ✌


GIMP 2.99.2 Released

GIMP 2.99.2 Released
https://www.gimp.org/news/2020/11/06/gimp-2-99-2-released/

2.99.4 was released back in december: https://www.gimp.org/downloads/devel/
Any chance we could get this as an option?

This issue was fixed by #255. @jnsgruk this can be closed.

Nice, thanks!


Invalid URI error when passing the URL of a running Jupyter notebook

I am trying to send message using websocket client (Python-based) to the Jupyter notebook (the websocket server is running in the cell of notebook). The code i am using is below:
Websocket Client Code:
import websockets
import asyncio
async def listen():
url = "ws://<IP_ADDRESS>:8888/?token=14bf261ecb24d32d4c3d63270fc27f75e32699b7a51f22aa"
async with websockets.connect(url) as ws:
await ws.send("Hello Server!")
while True:
msg = await ws.recv()
print(msg)
asyncio.get_event_loop().run_until_complete(listen())
The websocket server Code (running in the cell of Jupyter notebook shown below):

But when I run client i get following error:

However when I use the given URL separately in new browser window it actually works. Why I am getting this error?
The details of running Jupyter address is:

Is there any specific syntax i need to follow for URL. I need this to run urgently for my project submission. Please help in this issue.

Actually this is a bug -- websockets doesn't support redirects when the Location header contains a relative URL.
Try url = "ws://<IP_ADDRESS>:8888/tree?token=14bf261ecb24d32d4c3d63270fc27f75e32699b7a51f22aa" so you bypass the redirect?

@aaugustin Thanks for the suggestion! But this is again giving error with following line of codes.
import websockets
import asyncio
async def listen():
url = "ws://<IP_ADDRESS>:8888/tree?token=14bf261ecb24d32d4c3d63270fc27f75e32699b7a51f22aa"
async with websockets.connect(url) as ws:
await ws.send("Hello Server!")
while True:
msg = await ws.recv()
print(msg)
asyncio.get_event_loop().run_until_complete(listen())
Error is:

And the weird part is I can able to communicate easily if I simply use below one and not passing URL:
import websockets
import asyncio
async def listen():
url = "ws://<IP_ADDRESS>:8080"
async with websockets.connect(url) as ws:
await ws.send("Hello Server!")
while True:
msg = await ws.recv()
print(msg)
asyncio.get_event_loop().run_until_complete(listen())
I can okay with that for communication on local host but my full project is running in Jupyter notebook (accessible via local browser) at remote server for that i need to pass URL for websocket connection. Or is there any other method by which i can establish the connection?

Related to above issue: The other help that i can expect is: I made a websocket server on glitch.com using jsnode with below code:

When i try to establish the connection from my remote Jupyter notebook (which is websocket client by passing URL of server i.e. glitch.com) I can able to connect with following code:

Is there any method by which  i can access the client URL at server end which is used by websockets (i mean reverse method). And after getting the client URL I can use that in my code.


Build 138680 - 13/12/22 - Failed To Inject Hook 6

Latest patch for today broke it again, getting hook 6 failing to inject again.

Fix in release candidate.


Uninstallation of Istio

Description
Changes proposed in this pull request:

Add handling for uninstalling Istio when Istio CR is deleted

Related issue(s)

https://github.com/kyma-project/istio/issues/81

/restest

/retest

/retest

/retest


Research authorization between the frontend and the backend

I have seen some kind of OAuth authorization with a bearer token.
Are there any other options we should look into?
What do we need to make it work? An account?

My strong recommendation is to use Json Web Tokens for persistent authentication and authorization. We also need to secure ssl certificate and enable https protocol for our services but for now it has to stay. We can get a free ssl cert from cloudflare: https://www.cloudflare.com/en-gb/plans/#overview


battery: Add AC icon and low_battery_threshold config

When fully charged on AC, show plug character (U+1F50C).
Add config option to show percentage even if fully charged on AC.
Add config option to set low battery threshold.

Oops, I guess I won’t create a separate pull request for the svn update. :-P

if @b-ryan can look at this one, I have a change adding mac support, but I'm after this guy's change. My pull request in not yet pending so I can merge my code with this guys code. I do however disagree with the name of the configuration, I think the word "battery" should be dropped as it is redundent. If not done in this pull request, I will do in mine.

I'm going to go ahead and split this out into two separate PRs.

@kc9jud, that sounds great, I'm still holding my code back since I made a few changes as I reworked the code a bit to make it more clear, since there is now 2 ways to get the battery info


Make the dist script crawl all features by default

The "**" path pattern in package.json doesn't work on at least macOS,
and contributed to an orphaned dist file:
https://github.com/web-platform-dx/web-features/pull/1205.
To avoid such issues, let the command expand directory names to any dist
files within, and make the dist script crawl all features by default.
This also allows simplifiying instructions in a README.

This leaves in the check from https://github.com/web-platform-dx/web-features/pull/1209 since that also provides a clear error message.


fix: replace @proload/plugin-typescript with @proload/plugin-tsm

Codecov Report
Base: 100.00% // Head: 100.00% // No change to project coverage :thumbsup:

Coverage data is based on head (5d5aa53) compared to base (2807989).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff            @@
##              beta       #34   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files            3         3
  Lines          191       191
  Branches        58        58
=========================================
  Hits           191       191

Impacted Files
Coverage Δ

src/utils.ts
100.00% <100.00%> (ø)

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.


Fueled pack

Some people just want to watch the Spire burn.

I believe this is now ready once I know what to do with the dice PR for Packmaster repo.

I think this is ready.  Sorry if I missed something.

I think this is ready. Sorry if I missed something.

Looks like Burning Strike is still missing the strike tag, but I'll just merge this and ad that in myself. I'm looking forward to playing with the release version of this pack!


Create A Prototypical Animation Of ROB being Ripped Apart Revealing A Gun Sprite Inside Him

@vitormaduro haven't tested the rob branch in a while, but was there any animation of rob being ripped apart revealing a gun. I believe there was, but just double checking before closing the issue.

There's this one


[AzureMonitorDistro] add unit tests to verify QueryString Redaction

API change check
API changes are not detected in this pull request.


New VNet integration does not work with multiple app service plans in multiple subnets

Currently we have multiple app service plans in the same region. we started removing P2S integration and using the new VNet integration.
I created a separate subnet for each app service plan:
ASP1 --> Subnet1
ASP2 --> Subnet2
ASP3 --> Subnet3
the 1st VNet integration works.
Any other VNet integration does not work and gives below error when trying tcpping to a VM within the same VNet:
A non-recoverable error occurred during a database lookup
is it a known issue?

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

ID: a7a98803-1438-b1b5-f543-7dd88bc4294e
Version Independent ID: 37ff1d0f-ed8e-5e4d-1f4c-1b9f6cffb938
Content: Integrate app with Azure Virtual Network - Azure App Service
Content Source: articles/app-service/web-sites-integrate-with-vnet.md
Service: app-service
GitHub Login: @ccompy
Microsoft Alias: ccompy

@mohamed-shehata Thanks for the feedback! We are currently investigating and will update you shortly.

@mohamed-shehata-m Thanks again for asking question! As its mentioned in doc that this feature is in preview but, it is supported for Windows app production workloads with some limitations.
“The integration subnet can only be used by only one App Service plan”

Hello SnehaAgrawal,
Thank you, but I'm already using different subnet for each app service plan.
You can reproduce the same behavior by creating 2 app service plans and integrate them into two different subnets.
Only the the 1st app service to be integrated, will have connectivity to the VNet. The other app service plan will throw the error i mentioned earlier.

I've asked this type of question a few times and still waiting for a definite answer. Seems like a massive limitation if not.

@mohamed-shehata-m Thanks for the clarification. Could you please send an email to AzCommunity[at]Microsoft[dot]com referencing this GitHub issue, we would like to work closer with you on this matter.
Since we will work with you offline, we will now proceed to close this thread.

@SnehaAgrawal-MSFT could I please be updated with the outcome?

I have same issue multiple subnets but still not working ..

Same issue as the other posters here. Have had a support case open for a month with dozens of phone calls and emails and virtually no progress on diagnosis or resolution.
One temporary resolution is to create an entirely new VNET, although after time this too breaks.
Once a VNET encounters this issue I've not been able to get it to ever reconnect using the Regional VNET integration as all new subnets fail with the same error.
One interesting thing observed is that if you create a VNET with a dozen subnets and simply attach and detach your app service from them then at least you have a dozen to swap between, although once this error shows up, it is not possible to add any new subnets to the VNET for use with Regional integration as these too will suffer the same issue from the start.

Please provide some update. This is important, because many people will have the same issue as I have, where you need two subnets. The first is accessible to the internet, while the second is attached to a security group that denies internet access. Apps on this second, private subnet are private and should not be exposed.

"You can have only one regional VNet Integration per App Service plan. Multiple apps in the same App Service plan can use the same VNet."

@azuregurus I tried this Today and it worked .. is there an update roled up to azure that fixed this issue .. I have two plans in the same region and the VM works

@psallis Apologize to delay response. This issue has been resolved. If any other concerns on this request to open fresh issue for better visibility. Thanks again!

@mohamed-shehata-m @SnehaAgrawal-MSFT , I am currently facing the same issue
2 App service plans. 1st App serice plan net Integration is working and 2nd App service Plan is throwing the error saying Non recoverable error from data base lookup. Could you please advise of the resolution?

It has to be 1 app service plan per subnet (multiple web apps on the same app service plan).
You cannot integrate multiple app service plans in the same subnet.

Hi yes, I am creating one subnet per app service plans but it is still not
working.
I am not using multiple app service plans under one subnet.
Regards,
Divya
On Sat, 18 Jul 2020, 02:36 Mohamed Shehata<EMAIL_ADDRESS>wrote:

It has to be 1 app service plan per subnet (multiple web apps on the same
app service plan).
You cannot integrate multiple app service plans in the same subnet.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/MicrosoftDocs/azure-docs/issues/35478#issuecomment-660337886,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AQKBFZQ4SX6MVABMWGZ4APTR4C4MTANCNFSM4IFEZPFQ
.

Hi
Was this solved?

Yes, you have to use 1 subnet per app service plan.

So.. I'll possibly be running out of /28 subnets.. might just have a separated vnet just for this, right?

De: Mohamed Shehata<EMAIL_ADDRESS>Enviado: viernes, 13 de noviembre de 2020 11:59
Para: MicrosoftDocs/azure-docs<EMAIL_ADDRESS>Cc: matibs<EMAIL_ADDRESS>Comment<EMAIL_ADDRESS>Asunto: Re: [MicrosoftDocs/azure-docs] New VNet integration does not work with multiple app service plans in multiple subnets (#35478)
Yes, you have to use 1 subnet per app service plan.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHubhttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2FMicrosoftDocs%2Fazure-docs%2Fissues%2F35478%23issuecomment-726811828&data=04|01||9cbe3688f6374bd31a0608d887e4c20d|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637408763857443633|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=XbuCOMtFvZUPOnfyXW%2BNhOM%2F%2F0EQMukal%2FoVsR5suAg%3D&reserved=0, or unsubscribehttps://nam12.safelinks.protection.outlook.com/?url=https%3A%2F%2Fgithub.com%2Fnotifications%2Funsubscribe-auth%2FAPGI7EAF52GQEYFNSUHGWIDSPVCWBANCNFSM4IFEZPFQ&data=04|01||9cbe3688f6374bd31a0608d887e4c20d|84df9e7fe9f640afb435aaaaaaaaaaaa|1|0|637408763857443633|Unknown|TWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D|1000&sdata=FSNxeF%2BP1bsZZJZs1%2BE7gBPmuD7vz50f0yITj8Z0Z2o%3D&reserved=0.

This still happening for me with a slight twist
I have the app service and 3 subnets. I can attach 2 of the app services to their respective subnets, but I get a failure when I try to do the third. There is no further information in the failure message.
After the failure, the subnet does show that it is delegated to Microsoft.Web/serverfarms

I think that I have figured this out. It is failing because the 2 app services are on the same app service plan.

Still not possible from what I've observed using Linux Containers on App Services. A Service Plan can only have one attached Subnet. It's a One:2:One relationship.
However, the Portal, ARM Templates and docs all make out that you can have multiple :(
If you're unable to join and app to a subnet, it may be due to the hosting Service Plan having apps that connect to a different subnet, breaking the 1:1 rule.
This can be found using Azure Resource Graph Query
resources
| where type =~ 'Microsoft.Web/Sites'
| extend properties = parse_json(properties)
| extend virtualNetwork = properties.virtualNetworkSubnetId
| extend vnetData = split(virtualNetwork, "/")
| extend vnet = vnetData[8]
| extend subnet = vnetData[10]
| extend serverFarmData = split(properties.serverFarmId, '/')
| extend serviceplan = serverFarmData[8]
| project resourceGroup, name, vnet, subnet, serviceplan
//| where resourceGroup == "development"
| order by name asc

If anyone has managed to get a Single Service Plan to connect to multiple subnets, please let me know how :)


Prototype -  auto close

prototype close and generates this code in wine
terminate called after throwing an instance of 'std::out_of_range'
what():  array::at: __n (which is 1188) >= _Nm (which is 17)
0030:fixme:msvcrt:__clean_type_info_names_internal (0x1131fe54) stub
Software information
Prototype,800x600, all low, no Antialiasing
System information

GPU:nvidia 1050 oc
Driver:430.09
Wine version: 4.7
DXVK version: git

Apitrace file(s)
Was unable to obtain a trace (copied lib/wrappers/d3d9.dll from current apitrace release into game directory, but no trace was generated)
Log files

d3d9.log:prototypef_d3d9.log

Does it work without D9VK though? Apparently the game doesn't work at all for modern CPUs. It didn't work for me either under windows, or under vanilla wine.

Can you please provide a trace? It may be on your desktop.
I can't fix an issue like this without either owning the game or having a trace.

@Joshua-Ashton  upload apitrace

Same issue for me.

Does it work without D9VK though?

Prototype work without d9vk, but is limited to 20fps.
Disabling csmt patch is 30min-90max fps, but graphics glitch.

Prototype works for me as of latest d9vk with latest nvidia vulkan drivers. Didn't play enough to thoroughly check for any bugs (expect for like 10ms green-color background at the game menu loading after the copyright)
I'm also using a full-hd patch

I played for around 30 mins (with low/mid/max settings at FullHD), riding tanks, helicopters, doing explosions, etc, didn't notice a single bug :D

Thank-you. Solved for me too.
Min 45, max 60 fps at max settings.

Can this be closed then?

fix problem :3rd_place_medal:


[Unix ThreadPool] Worker Thread Allocation and Management

Adds logic for worker threads for the CLR thread pool. Also adds logic for thread allocation and management using hill climbing.

@jkoritzinsky,
Thanks for having already signed the Contribution License Agreement. Your agreement was validated by .NET Foundation. We will now review your pull request.
Thanks,
.NET Foundation Pull Request Bot

@kouvel

@AntonLapounov @sergiy-k

LGTM, thanks!


[Question] Batch on SDXL?

Well, this is awkward. I am trying animatediff with SDXL for the very first time. I want to do batch prompting. Usually with SD1.5, there is a nice box where I can have my batch prompts

but on the sdxl version of the node I don't see it. Is the text_g and text_l the same thing as the one I am seeing in the sd1.5 version?

The text_g is for the Clip G encoder and the text_l is for the Clip L encoder. the encode from the regular batch prompt would be the two inputs with the same prompt. this node was made so you can schedule them separately.

sorry but could you give me an example?


Should non-OK status entries be listed for non-matching component groups?

Example:
$ go run ./cmd/check_statuspage_components/ --url 'https://status.zoom.us/api/v2/components.json' --group 6zvc1tw9rpfm
OK: 0 evaluated "Zoom" components have a non-operational status (6 evaluated, 135 total)
**THRESHOLDS**

* CRITICAL: major_outage
* WARNING: under_maintenance, partial_outage, degraded_performance

**DETAILED INFO**

Specified filter: {Group: "6zvc1tw9rpfm", Components: ""}
NOTE: Component count (135) is higher than display limit (50); overriding default display of OK components.

Page: Zoom (https://status.zoom.us)
Time Zone: America/Los_Angeles
Last Updated: 2022-11-28T07:33:01-08:00

NOTE: Omitting OK/operational components as requested.

GROUP NAME                    COMPONENT NAME                STATUS
----------                    --------------                ------
LATIN AMERICA - Zoom Phone    Zoom Phone                    DEGRADED PERFORMANCE
LATIN AMERICA - Zoom Phone    Calling (Inbound/Outbound)    DEGRADED PERFORMANCE

Summary:

* Filtering applied to components set: true
* Evaluating all components in the set: false
* Omitting OK/operational components (if requested): true
* Number of total top-level components: 6
* Number of total component groups: 20
* Number of total subcomponents: 109
* Number of total problem components: 2
* Number of ignored problem components: 2
* Number of remaining problem components: 0

 | 'all_problem_components'=2;;;; 'remaining_components_critical'=0;;;; 'remaining_components_warning'=0;;;; 'all_component_groups'=20;;;; 'all_components_warning'=3;;;; 'remaining_components_unknown'=0;;;; 'time'=222ms;;;; 'all_components'=135;;;; 'all_components_critical'=0;;;; 'remaining_components_ok'=6;;;; 'excluded_problem_components'=2;;;; 'remaining_problem_components'=0;;;; 'all_components_unknown'=0;;;; 'all_components_ok'=132;;;;

These non-OK status components have nothing to do with the specified component group:
GROUP NAME                    COMPONENT NAME                STATUS
----------                    --------------                ------
LATIN AMERICA - Zoom Phone    Zoom Phone                    DEGRADED PERFORMANCE
LATIN AMERICA - Zoom Phone    Calling (Inbound/Outbound)    DEGRADED PERFORMANCE

I suspect that this was intentional on my part, but it's been so long since I worked with the codebase that I don't recall for sure and will need to review docs/code to be sure.

Stumbled across this again today, came back here to file a GH issue for it so I could research further.
I think a compromise is to detect this scenario (other problems exist, but not problems for the specified component group) and provide some lead-in text noting as much right before the table in the output.


Introduce a JAVA_API_JARS usage

Context
This commit introduces a new JAVA_API_JARS usage, mirror
to the JAVA_RUNTIME_JARS usage. This is both for consistency,
and to make sure that the JAVA_API and JAVA_RUNTIME usages
are limited to cases where the consumer doesn't care, or when
a producer doesn't have a more specific usage to provide.
This is, for example, the case for Java platforms. It's worth
noting than in case a producer mixes both "generic" usages
and "specific" usages, selection is likely to produce unexpected
results, because of disambiguation rules.
The Java disambiguation rule has been simplified and now
supports more cases.

Running a quick feedback only since the PR passed all stages but needed a rebase.


Prostopleer can be removed (service offline)

Prostopleer (http://pleer.net) is no longer active and can be removed from this extension.

Done in https://github.com/borismus/keysocket/pull/290


Build using logstash >=8.10

Is your feature request related to a problem? Please describe.
Yes. As described in https://github.com/elastic/logstash/issues/15908, JRuby 9.3 does not include the necessary Zlib function for processing gzipped S3 log files. The necessary function (Zlib::GzipReader.zcat()) exists only in JRuby 9.4. Logstash 8.10 is the first Logstash release to ship with JRuby 9.4.
Describe the solution you'd like
Upgrade upstream Logstash to >=8.10
Describe alternatives you've considered
Currently I have worked around this problem by modifying the logstash-input-s3 plugin to shell out to the system zcat but that is not ideal for (hopefully) obvious reasons.
Additional context
To briefly describe the problem: CloudFront and AWS LBs (and probably other services) concatenate multiple GZipped chunks together into a single GZipped log file. When Zlib::GZipReader.new encounters such a file, it reads only the first chunk and then stops, ignoring the rest of the file. The problem is described in this bug report. As a solution the zcat function was added in Ruby 3.

Is logstash 8.10 apache v2 license-compatible?

Does the presence of an 8.12 logstash-oss container imply that it is? https://www.docker.elastic.co/r/logstash/logstash-oss:8.12.1

I believe so, I think as long as we use the -oss version we're A-OK. But IANAL. Do you want to attempt an upgrade @eherot?

I don't know if I have cycles for it this week but if no one else can handle it in the next couple of days I may be able to tackle it...

Hi! I'd love to see updated logstash for the opensearch project, i am also hoping for an updated docker container :+1:


⚠ Bofrost.lu has degraded performance

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

HTTP code: 200
Response time: 2613 ms

Resolved: Bofrost.lu performance has improved in f9263d1 after 1 hour, 8 minutes.