Implement the "logs" endpoint for the journald log driver

This change set uses the journald libraries to read log entries from the journal, and hooks that up to the "logs" endpoint.  It moves handling of the --last option out of the endpoint logic and into the log drivers themselves, because doing so has the potential cut down on how much data the journald driver will have to dump to its pipe.
It's multiple patches to hopefully be easier to review, but I have no qualms about squashing things together if that's preferred.

Any comment from upstream?  This would be a really nice feature.  I already have logging people asking me about it.

Think they've been busy bug-hunting for the release.

I get Unrecognized input header with this driver. Also I have double output for json-file log-driver on first run of docker logs -f.

I can't reproduce the first symptom; can you give me more details about how you're getting it to happen?  The duplicate log data doesn't appear to be driver-specific (now that I know what to look for, I'm seeing it with the journald driver, too), but it goes away if I revert 153f98bad51e2f46cf3853d2da0173bcfb4b687d.

@nalind I run
docker run -d --log-driver=journald busybox ping google.com

and then just do docker logs -f on that container. Nothing in daemon logs also.

Ah, thanks!  It's still not giving me the Unrecognized input header error, though it does show me the first few lines of the output twice if I run docker logs -f quickly enough.
It looks as though, if the client and daemon disagreed about whether or not the container had a tty allocated to it, that the data stream coming back from the server wouldn't be muxed using an stdcopy.StdWriter, so it wouldn't be in the format that stdcopy.StdCopy expects to demux, and that should cause the Unrecognized input header message to appear, but I'm at a loss as to how to actually trigger it.

@nalind I'm using systemd-220.

I'm also running with version 220 (Fedora 23's systemd-220-3.fc23), but the like messages we retrieve from json-logs, data we read back from the journal should be wrapped up and chunked before it gets to the client, so if the driver was getting garbage back, I'd expect to get garbage in the output of the docker logs command rather than an error parsing the HTTP stream that's carrying it.  Is there anything else that might be making a difference?

@nalind I can't imagine. I'll try to put some logging to your code later.

Ah, found it.  When built without the journald tag, which the build scripts try to enable automatically when the libraries are detected, this is triggered when the daemon sends back an error message indicating that it couldn't read the logs, because it sends that message back without the framing that the client is expecting.
The Dockerfile installs libsystemd-journal-dev, and hack/make.sh tries to check for it, but that check fails because pkg-config isn't also available, so the journald build tag wasn't being enabled.  Adding it as a requirement to the top-level Dockerfile should handle most of the cases that the changes to contrib/builder/deb/generate.sh and hack/make/.build-rpm/docker-engine.spec didn't already cover.
As for the formatting of the error when it's sent back to the client, if ContainerLogs replaces the OutStream member of the ContainerLogsConfig that it gets with its wrapper, and getContainersLogs sends the error message through that, the client displays the error that the server sent.
I'm tweaking the patch set to fix both of these problems and rebasing against the current master.

Rebasing to resolve reported merge conflicts.

Catching up with the new fluentd driver.

ping @LK4D4 have you been able to successfully test this?

Hi, the log reader interface was refactored and should (I hope!) be much simpler to implement now, as all you need to do is implement a ReadLogs function on journald.

Yes, I waited for this refactoring. Now implementation of journald logs should be simpler and more robust.

The current refactor keeps knowledge of the number of lines to read when it's in "last" mode, and the cutoff time in "since" mode, in ContainerLogs.  The journald driver could definitely use that information to skip sending data that is only going to be ignored by ContainerLogs, and I suspect other log readers would, too.  (The current ContainerLogs also spends some time dealing with file numbers, which really seems to me like a jsonfilelog-specific notion, but a reader can ignore that.)

@nalind Not anymore. ContainerLogs does nothing except call the ReadLogs on the configured logger and Listens for logger.Messages on a channel.

@cpuguy83 Oh, you're right, that's new today, and it's much better.

Oh, you're right, that's new today, and it's much better.

glad you like it; kudos to @cpuguy83 :+1:

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "journald-logs" git@github.com:nalind/docker.git somewhere
$ cd somewhere
$ git rebase -i HEAD~4
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

Can we get some movement on this.  Would love to get this into docker-1.9.
@cpuguy83 @crosbymichael @jfrazelle @tianon @LK4D4

Please sign your commits following these rules:
https://github.com/docker/docker/blob/master/CONTRIBUTING.md#sign-your-work
The easiest way to do this is to amend the last commit:
$ git clone -b "journald-logs" git@github.com:nalind/docker.git somewhere
$ cd somewhere
$ git rebase -i HEAD~5
editor opens
change each 'pick' to 'edit'
save the file and quit
$ git commit --amend -s --no-edit
$ git rebase --continue # and repeat the amend for each commit
$ git push -f

Ammending updates the existing PR. You DO NOT need to open a new one.

@LK4D4 Do you think this is good to move to code-review?
I think this makes sense.

Rebasing to clear a merge conflict and drop the patch which is now PR#16022.

LGTM.
@nalind can you squash your commits into a single one so we can track all this feature together?

Will do.

small rebase problem, other than that feel free to ping me after to merge thanks

@nalind I don't see nor ID, neither name of container in journalctl -f(which is probably not your problem)`, but I also see:
Error running logs job: configured logging reader does not support reading

on docker logs

@LK4D4 They should show up if you use one of the verbose output formats (-o json, -o export, or -o verbose).
@jfrazelle Thanks for spotting that.  Dropped the file, rebased, and gave it another once over.

@nalind okay, see it now. What about docker logs? :)

@LK4D4 The logic's compiled in when we find the headers (make.sh sets a build tag if pkg-config finds them) and since I don't get static libraries with libsystemd-journal-dev or systemd-devel packages, it also limits itself to non-static builds.  Are you testing with a static binary?

@nalind no, I'm testing with dynamic binary. Just noticed that it requires buildtag, I'll try to build with it.

im testing the debs/rpm build now :)

Yup, it works with tag. And I can't find static systemd libs too.

so can we not compile a static binary with this? is there licensing problems?

Error running logs job: configured logging reader does not support reading

is confusing though, but I don't know what to do with it.
@jfrazelle Yes, there is no way to compile static binary with it as I see.

IMO, we're probably safe to disable this driver for static builds, especially since even if we can get libsystemd to link in statically, it likely won't work very well if we have host version mismatching (just like the libdevmapper issues we have with static binaries).

retesting building debs and rpms

ubuntu:wily is libsystemd-dev as well sorry

the rpms worked

@jfrazelle  No problem.  Your build box is clearly faster than mine.  :)

LGTM

@LK4D4 good for you?

LGTM

Just a question, but does this have any impact on or implications for the native GELF support that has been added with Docker 1.8?

We have an outstanding PR to the github.com/coreos/go-systemd package, which is used elsewhere in docker, to implement a journal API based on code Dan Mace tried to get working in 2014: https://github.com/coreos/go-systemd/pull/110

@LK4D4
I'm not getting Error running logs job: configured logging reader does not support reading with docker version 1.9.1 on Ubuntu Vivid when I run docker logs. journalctl works fine.
Should this be fixed now? I'm not sure why I'm getting the error.

@dmp1ce Are you getting error or not? I'm not sure how your docker is built, but with --log-driver=journalctl all should work fine.

@LK4D4  Sorry, I AM getting the error. I updated my comment with the removed "not".
I'm installing using the instructions here: https://docs.docker.com/engine/installation/ubuntulinux/
I'm using the journald driver using Docker Compose and docker run --log-driver=journald. I'm not using --log-driver=journalctl.

@dmp1ce it should be fine if binary built as dynamic with journald build-tag. I think @jfrazelle or @tianon know more than me about which binary we ship for ubuntu.

I am using official docker-engine package for jessie and getting this message too:
Error running logs job: configured logging reader does not support reading

ivan@36com10:~$ ldd `which docker`
	linux-vdso.so.1 (0x00007ffdec1b1000)
	libapparmor.so.1 => /usr/lib/x86_64-linux-gnu/libapparmor.so.1 (0x00007fe08b90a000)
	libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0 (0x00007fe08b6ed000)
	libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007fe08b4e8000)
	libdevmapper.so.1.02.1 => /lib/x86_64-linux-gnu/libdevmapper.so.1.02.1 (0x00007fe08b29f000)
	libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007fe08aef6000)
	/lib64/ld-linux-x86-64.so.2 (0x0000562f5b55f000)
	libselinux.so.1 => /lib/x86_64-linux-gnu/libselinux.so.1 (0x00007fe08acd0000)
	libudev.so.1 => /lib/x86_64-linux-gnu/libudev.so.1 (0x00007fe08aac1000)
	libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3 (0x00007fe08a853000)
	librt.so.1 => /lib/x86_64-linux-gnu/librt.so.1 (0x00007fe08a64a000)

Getting logs through journalctl works except for #15722.

@bobrik How do you start your container and what version do you use? Seems like works fine for me on master with
docker run -it --rm --log-driver=journald busybox ping google.com

Yeah, as far as I know, logging to journald should be enabled in our Ubuntu
and Debian packages, since they're dynamic for sure.
We have libsystemd-journal-dev in
https://github.com/docker/docker/blob/0b7e9ef910b91a0a8cb334db852ad143c4660155/contrib/builder/deb/debian-jessie/Dockerfile#L7
combined with
https://github.com/docker/docker/blob/c21eb2a4209f6339fe59e4a97c3e6479aeb39f94/hack/make.sh#L109-L111
should be sufficient for that code to be enabled (and I actually used it on
1.9.1 successfully myself on Tuesday).

$ docker run -it --rm --log-driver=journald --name nope busybox ping google.com

$ docker logs nope
Error running logs job: configured logging reader does not support reading

$ docker version
Client:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   a34a1d5
 Built:        Fri Nov 20 12:59:02 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   a34a1d5
 Built:        Fri Nov 20 12:59:02 UTC 2015
 OS/Arch:      linux/amd64

$ docker info
Containers: 263
Images: 1716
Server Version: 1.9.1
Storage Driver: overlay
 Backing Filesystem: xfs
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 4.1.3-wtf
Operating System: Debian GNU/Linux 8 (jessie)
CPUs: 32
Total Memory: 125.8 GiB
Name: 36com10
ID: CEGP:5ZLU:4ZGY:IQD7:RBMI:FB7A:JOB7:QP7Z:AXVM:N7Q5:Z5YH:YNLO
WARNING: No swap limit support

I think it's packaging problem. The binary must be linked with libsystemd.
Am I right, @tianon ?

Interesting, I can reproduce on both 1.9.1 and 1.10.0-rc1 using the official docker-engine Debian packages (for debian-jessie specifically); both give something like:
Error running logs job: configured logging reader does not support reading

@tianon check ldd. Also, maybe we don't set journald tag.

Hmm, I think the build containers (per contrib/builder/deb/generate.sh) might not have pkg-config in them.  I had erroneously assumed that they were pulled in by build-essential on Debian, and the various development tools groups.
If nm -CDu /usr/bin/docker | grep sd_journal_add_match turns up empty, then the logic's not getting compiled in.

Yeah, I don't see systemd or journal anywhere in ldd, so I'll be digging into the build containers next.

$ nm -CDu /usr/bin/docker | grep sd_journal_add_match
$

Into the build system I go! :smile:

Man, I could've sworn pkg-config was part of build-essential also, but it's not there!

I have Ubuntu 15.10 running with Docker version 1.10.0. I'm still getting Error running logs job: configured logging reader does not support reading. Should this have been fixed?

Yes, it should have.  When I poke at the packages in the apt repository, I'm finding the expected references to the right unresolved symbols in the 1.10.1 packages for jessie, precise, trusty, and wheezy, but not in the packages for stretch or wily.
On stretch and wily, the expected headers are included in libsystemd-dev, which the build scripts install, but there is no libsystemd-journal.pc for pkg-config to find when hack/make.sh calls it, so the logic doesn't get built at build-time.  Given that those are newer versions, we might be better off changing pkg-config references to just look for libsystemd, and have make.sh look for a version of it that's at least 209, when systemd's news file says those were all merged together.

Whoops, packages for precise and wheezy don't link with the right libraries - I was taking their packages apart wrong.  So only jessie and trusty are being built with the feature.

@nalind OK. Thanks. Is this already merged then for Wily? What about the future Xenial?

@dmp1ce I was mistaken in thinking that we could fix it by changing the pkg-config dependency (we'd stop pulling things in on older releases, and there's no single option that's present across all of the desired build targets), so that was closed without merging.  So for the moment at least, it's not working in stretch or wily.

@nalind Should I create an issue for Wily?

@dmp1ce Yeah, I think that's how we make sure it stays on the radar.


Add intentionally unwelcoming flag to make execution history read-only

This would be a big performance boost for certain CI environments,
but could cause problems if used in more generic use cases. See the
associated issue (#20005).
Fixes #20005
Contributor Checklist

[x] Review Contribution Guidelines
[x] Make sure that all commits are signed off to indicate that you agree to the terms of Developer Certificate of Origin.
[x] Make sure all contributed code can be distributed under the terms of the Apache License 2.0, e.g. the code was written by yourself or the original code is licensed under a license compatible to Apache License 2.0.
[x] Check "Allow edit from maintainers" option in pull request so that additional changes can be pushed by Gradle team
[ ] Provide integration tests (under <subproject>/src/integTest) to verify changes from a user perspective
[ ] Provide unit tests (under <subproject>/src/test) to verify logic
[x] Update User Guide, DSL Reference, and Javadoc for public-facing changes
[x] Ensure that tests pass sanity check: ./gradlew sanityCheck
[x] Ensure that tests pass locally: ./gradlew <changed-subproject>:quickTest

Gradle Core Team Checklist

[ ] Verify design and implementation
[ ] Verify test coverage and CI build status
[ ] Verify documentation
[ ] Recognize contributor in release notes

Closing per #20005


System tests are flaky

The change in https://github.com/googleapis/nodejs-logging/pull/701 shouldn't have any effect on the system tests.

Example output:
1) Logging
       "after all" hook in "Logging":
     Error: 8 RESOURCE_EXHAUSTED: Quota exceeded for quota metric 'Control requests' and limit 'Control requests per minute' of service 'logging.googleapis.com' for consumer 'project_number:1046198160504'.
      at Object.callErrorFromStatus (node_modules/@grpc/grpc-js/build/src/call.js:30:26)
      at Http2CallStream.call.on (node_modules/@grpc/grpc-js/build/src/client.js:96:33)
      at process.nextTick (node_modules/@grpc/grpc-js/build/src/call-stream.js:100:22)
      at process._tickCallback (internal/process/next_tick.js:61:11)

Deleting 64 test logs
Deleting nodejs-logging-system-test-1581247995403-5d0816ce2ebd failed: 8 RESOURCE_EXHAUSTED: Quota exceeded for quota metric 'Control requests' and limit 'Control requests per minute' of service 'logging.googleapis.com' for consumer 'project_number:1046198160504'.
Deleting nodejs-logging-system-test-1581248017048-2f98d67f08da failed: 8 RESOURCE_EXHAUSTED: Quota exceeded for quota metric 'Control requests' and limit 'Control requests per minute' of service 'logging.googleapis.com' for consumer 'project_number:1046198160504'.
Deleting nodejs-logging-system-test-1581248057995-0174f0064990 failed: 8 RESOURCE_EXHAUSTED: Quota exceeded for quota metric 'Control requests' and limit 'Control requests per minute' of service 'logging.googleapis.com' for consumer 'project_number:1046198160504'.
Deleting nodejs-logging-system-test-1581248079280-6f50d7b92899 failed: 8 RESOURCE_EXHAUSTED: Quota exceeded for quota metric 'Control requests' and limit 'Control requests per minute' of service 'logging.googleapis.com' for consumer 'project_number:1046198160504'.
Deleting nodejs-logging-system-test-1581248139973-4bb213f41468 failed: 8 RESOURCE_EXHAUSTED: Quota exceeded for quota metric 'Control requests' and limit 'Control requests per minute' of service 'logging.googleapis.com' for consumer 'project_number:1046198160504'.
Deleting nodejs-logging-system-test-1581248160258-6ecf672dad59 failed: 8 RESOURCE_EXHAUSTED: Quota exceeded for quota metric 'Control requests' and limit 'Control requests per minute' of service 'logging.googleapis.com' for consumer 'project_number:1046198160504'.
Deleting nodejs-logging-system-test-1581248160382-459cce82aa8c failed: 8 RESOURCE_EXHAUSTED: Quota exceeded for quota metric 'Control requests' and limit 'Control requests per minute' of service 'logging.googleapis.com' for consumer 'project_number:1046198160504'.
Deleting nodejs-logging-system-test-1581248161200-bf5b31705d61 failed: 8 RESOURCE_EXHAUSTED: Quota exceeded for quota metric 'Control requests' and limit 'Control requests per minute' of service 'logging.googleapis.com' for consumer 'project_number:1046198160504'.
Deleting nodejs-logging-system-test-1581248161990-13beab2b2021 failed: 8 RESOURCE_EXHAUSTED: Quota exceeded for quota metric 'Control requests' and limit 'Control requests per minute' of service 'logging.googleapis.com' for consumer 'project_number:1046198160504'.
Deleting nodejs-logging-system-test-1581327086493-029040be726c failed: 8 RESOURCE_EXHAUSTED: Quota exceeded for quota metric 'Control requests' and limit 'Control requests per minute' of service 'logging.googleapis.com' for consumer 'project_number:1046198160504'.
Deleting nodejs-logging-system-test-1581327127854-98235013e2f0 failed: 8 RESOURCE_EXHAUSTED: Quota exceeded for quota metric 'Control requests' and limit 'Control requests per minute' of service 'logging.googleapis.com' for consumer 'project_number:1046198160504'.
Deleting nodejs-logging-system-test-1581327168610-9db8a41fc038 failed: 8 RESOURCE_EXHAUSTED: Quota exceeded for quota metric 'Control requests' and limit 'Control requests per minute' of service 'logging.googleapis.com' for consumer 'project_number:1046198160504'.

@stephenplusplus if there's no quick fix, let's just revert to the old approach we were using for deleting logs.
It sounds like you had a relatively quick modification you could make however?

Yeah, I will have a PR soon and if it doesn't produce satisfactory results, we can just rollback to the old style in the meantime.

PR: #703


Inconsistent nuget.config boolean value casing

Of note:

Boolean values are a mix between value="true" and value="True" (compare #bindingredirects-section and #packagerestore-section),
Documentation references code without markup (see #bindingredirects-section),

incorrect: "The default is false."
correct: "The default is false."

Casing differs between value description and its associated example (see #packagerestore-section).

From memory, MSBuild handles Boolean comparisons in a case insensitive manner, though I could be wrong.
To reduce confusion for those new to the ecosystem and others referencing this page as the source of truth, it would be nice to see something along the lines of:

Consistent boolean values used across the page,
A note stating what boolean values are valid, or link to documentation that does this already.

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

ID: 0ea1390e-db36-6759-3095-ebab9d546fdb
Version Independent ID: ca88d8c6-0515-a267-aac3-a508c54157ab
Content: nuget.config File Reference
Content Source: docs/reference/nuget-config-file.md
Product: nuget
GitHub Login: @karann-msft
Microsoft Alias: karann

This seems useful and hopefully not too difficult to update.


[Core] delta_t other than 1 is failing

Please look at following test case -> https://github.com/lab-v2/pyreason-gym/tree/non-markov-exps/tests/non_markov_test and the rules.yaml file

Fixed, test-case is working


HELP \ AttributeError: 'NoneType' object has no attribute 'dtype' Error while converting in Model Inference

I'm very new to RVC and wanted to experiment with making AI music covers of my favorite artists. I recently trained my first model (which I believe went well) so I tried testing it using model inference but with no success. Here's what I got:
C:\Users\marci\Downloads\RVC0813AMD_Intel\RVC0813AMD_Intel>runtime\python.exe` infer-web.py --pycmd runtime\python.exe --port 7897 --dml
No supported Nvidia GPU found
use DirectML instead
Use Language: en_US
loading weights/britneyglory_2_e200_s200.pth
gin_channels: 256 self.spk_embed_dim: 109

Traceback (most recent call last):
File "C:\Users\marci\Downloads\RVC0813AMD_Intel\RVC0813AMD_Intel\infer-web.py", line 211, in vc_single
audio_opt = vc.pipeline(
File "C:\Users\marci\Downloads\RVC0813AMD_Intel\RVC0813AMD_Intel\vc_infer_pipeline.py", line 342, in pipeline
sid = torch.tensor(sid, device=self.device).unsqueeze(0).long()
RuntimeError
Traceback (most recent call last):
File "C:\Users\marci\Downloads\RVC0813AMD_Intel\RVC0813AMD_Intel\runtime\lib\site-packages\gradio\routes.py", line 321, in run_predict
output = await app.blocks.process_api(
File "C:\Users\marci\Downloads\RVC0813AMD_Intel\RVC0813AMD_Intel\runtime\lib\site-packages\gradio\blocks.py", line 1007, in process_api
data = self.postprocess_data(fn_index, result["prediction"], state)
File "C:\Users\marci\Downloads\RVC0813AMD_Intel\RVC0813AMD_Intel\runtime\lib\site-packages\gradio\blocks.py", line 953, in postprocess_data
prediction_value = block.postprocess(prediction_value)
File "C:\Users\marci\Downloads\RVC0813AMD_Intel\RVC0813AMD_Intel\runtime\lib\site-packages\gradio\components.py", line 2076, in postprocess
processing_utils.audio_to_file(sample_rate, data, file.name)
File "C:\Users\marci\Downloads\RVC0813AMD_Intel\RVC0813AMD_Intel\runtime\lib\site-packages\gradio\processing_utils.py", line 206, in audio_to_file
data = convert_to_16_bit_wav(data)
File "C:\Users\marci\Downloads\RVC0813AMD_Intel\RVC0813AMD_Intel\runtime\lib\site-packages\gradio\processing_utils.py", line 219, in convert_to_16_bit_wav
if data.dtype in [np.float64, np.float32, np.float16]:
AttributeError: 'NoneType' object has no attribute `'dtype'
The issue is probably not related to my model since I tested it using another model on the Internet and got the same issue. The path of the audio file to be processed was correct. (C:\Users\marci\OneDrive\Documentos\Audio\DontSpeak.wav if anybody is curious). I was very excited to see the results so I appreciate any help!

same


Memory leak when passing php array as parameter

We found that the memory used by passing an array into a C++ native function cannot be released after it returned to php. The situation is easily reproduced by using your bubblesort example:
http://www.php-cpp.com/documentation/bubblesort
I have used memory_get_usage() to capture the memory usage before and after both scripted_bubblesort() and native_bubblesort() functions:
<?php
function getMem() {
    return (memory_get_usage()/1024)."KB";
}

function scripted_bubblesort(array $input)
{
	// number of elements in the array
	$count = count($input);

	// loop through the array
	for ($i = 0; $i < $count; $i++)
	{
		// loop through the elements that were already processed
		for ($j = 1; $j < $count - $i; $j++)
		{
			// move on if smaller
			if ($input[$j-1] <= $input[$j]) continue;

			// swap elements
			$temp = $input[$j];
			$input[$j] = $input[$j-1];
			$input[$j-1] = $temp;
		}
	}

	// done
	return $input;
}

echo "init:".getMem()."
";

// fill an array with random numbers
$count = 10000;
$x = array();
for ($i=0; $i<$count; $i++) $x[] = rand(0, 1000000);

echo "Array generated:".getMem()."
";

// run the native and scripted bubblesort functions
$start = microtime(true);
$y = scripted_bubblesort($x);
$scripted = microtime(true);

echo("Scripted: ".($scripted - $start)." seconds, Mem:".getMem()."
");
unset($y);
echo("Unset y:".getMem()."
");

$y = native_bubblesort($x);
$native = microtime(true);

echo("Native:   ".($native - $scripted)." seconds, Mem:".getMem()."
");
unset($y);
echo("Unset y:".getMem()."
");

$y = scripted_bubblesort($x);
$scripted2 = microtime(true);

echo("Scripted: ".($scripted2 - $native)." seconds, Mem:".getMem()."
");
unset($y);
echo("Unset y:".getMem()."
");

$y = native_bubblesort($x);
$native2 = microtime(true);

echo("Native:   ".($native2 - $scripted2)." seconds, Mem:".getMem()."
");
unset($y);
echo("Unset y:".getMem()."
");

?>

The result is like this:
init:367.84375KB
Array generated:883.8984375KB
Scripted: 9.6133317947388 seconds, Mem:1400.015625KB
Unset y:883.8984375KB
Native: 0.10033297538757 seconds, Mem:1916.0859375KB
Unset y:1399.953125KB
Scripted: 9.5922122001648 seconds, Mem:1916.0703125KB
Unset y:1399.953125KB
Native: 0.100998878479 seconds, Mem:2432.125KB
Unset y:1916.0078125KB

You can see that both input x and result y are around 520KB. After unset y, the memory usage will back to before running scripted_bubblesort(). However, after running native_bubblesort(), the memory usage increased dubble as the scripted_bubblesort(), which increased around 1040KB. After unset result y, the memory usage only dropped 520KB only. There is 520KB leaked whenever the native_bubblesort() is called. It seems the memory used by input x cannot be released after the function return.
I have tried to change the native function to pass by reference. It seems the leak is gone. However, we experienced the native function may not able to get the value from the input array correctly if the array is big and multi-dimension. Hence, pass by reference is not a solution.
Please help. We choose to use native extension since we want to gain the performance of c++ in processing a large amount of data. However, memory leak is critical to this case, leak large amount of memory.
Thank you.

We have solved the problem after building a brand new environment to compile the code. We suspect there were some issues on the old environment after upgrading from php 5.5 to php 7.1 and also the php-cpp lib from 1.5.3 to 2.0.0.


[spi_device/dv] Fix regression timeout

mem size is increased recently, made these changes to avoid timeout

increase max timeout timer to 1.5s, 1s takes a bit over 1hr
reduce num_trans in spi_device_fifo_underflow_overflow_vseq
Signed-off-by: Weicai Yang<EMAIL_ADDRESS>

@sriyerg is this PR ready to land?


Add Simple Calculator program using Java GUI

Add a java program to implement calculator with addition, multiplication, subtraction and division operations.

As part of Hacktoberfest please assign this issue to me @keshavsingh4522

I request you to assign me this issue.


Till now I used Putty, but if I move to openSSH and mistakenly closing WSL CMD connection lost?

Till now I used Putty, and I consider moving to use openSSH with WSL. Now, as You know, when you run Putty's Pageant to load your private keys, it's just running as a background task, "well hidden" in the system tray so you can't quite elusively close it by mistake.
But what if I'll use SSH-agent of OpenSSH via the WSL on CMD or Powershell? These are part of task bar, not of the system tray, as you well know, so If I mistakenly close the window the connection lost and I'll need to load all keys each time a new... Even with a script it could be a bit annoying as entering both the Unix password and the passphrase each time can take some time especially if it happened twice or more in one day.
You might have any thought on how to better prepare for such problem or just how would you prevent it ahead?

This will help you: https://github.com/cerebrate/wabash

This one was obscured by the wording chosen in the OP. ssh-agent should run fine on WSL; if it does not please open a bug report following the template. Auto-startup of services (ssh-agent or otherwise) is covered in #709 (among others) and has improved quite a bit as of 17046.


When will the tutorials on Grisette be made available?

Hello @lsrcz , I am a Rosette user who would like to move to Grisette as soon as possible, but I think I will need tutorials on Grisette to get started initially. So I was wondering when will the tutorials on it will be made available? Thanks.

Hi @AkashIwnK, thank you for your interest in Grisette. We currently do not have a tutorial like Rosette Guide, but we do have some examples which you can have a look at.

https://github.com/lsrcz/grisette-g2q-benchmarks. Here we have some small examples from G2Q. There is an arithmetic language verifier, a de Bruijn encoded lambda expression synthesizer, a n-queens solver, and a solver-aided regex matcher. These are small examples, but not quite documented.
https://github.com/lsrcz/grisette-examples/tree/main/arith-synth Here we have an example for an arithmetic language synthesizer with extensive documentations.
https://hackage.haskell.org/package/grisette-<IP_ADDRESS>/docs/Grisette-Core.html The API doc for Grisette core is also available. There are some explanations for the data abstractions in Grisette.

Please take a look at the resources while I am working on a proper tutorial -- I will start doing it when I get some time. Please let me know if an example for some specific domain is useful for you, or if you would like me to document some of the examples. If they are too advanced, or you have any questions, please let me know and I can provide help.

Hi @AkashIwnK, there is also a library for synthesis in Grisette under development at https://github.com/lsrcz/grisette-synth-lib if your focus is synthesis or super-optimization. An example is available at https://github.com/lsrcz/grisette-synth-lib/tree/development/arith.


Dtr functionality

Adds all functionality from DTR.  When clicking on a link to open the smart app, it will now open in the same app.  You can click on the tabs at the top of the page to switch views between the questionnaire and the main page with the cards.

Looks like there is still a lining check failing.

This works really well, I especially like how it loads in a new tab within the smart app. Should we add a way to close the tabs that are open? Or do you believe that they should stay present for the entire session?

Starting the project opens the app in a web browser that complains about its and fhirServiceUrl parameters missing. Any way to suppress the launching of the web browser?

This looks and works great, after my other questions are addressed, we just need to merge the latest from dev. Differences to merge can be found here:
https://github.com/mcode/rems-smart-on-fhir/pull/23/files


Deleted <> at top of page

Pull Request Template

Please provide all of the details below. Pull requests missing any of the information below will be closed!
Providing the issue number/url helps us identify the problem being solved and keep the issues tab clean and tidy

Sumarise what this PR fixes
Just deleted the <> at top of page to look cleaner
What ISSUE NUMBER does this fix?
Fixes #
Checklist:
(Add an x between the brackets to check the items)

[ ] I have sumarised what this PR fixes above
[ ] I have provided the issue ID/URL above
[ ] This PR fixes only the issue mentioned above (create seperate PRs for seperate issues)
[x ] I was the first one to claim the issue or I created the issue

I"m a newbie trying to delete the <<<< head >>>> at top of page

@Jrrosario I would suggest you close this pr as it is neither a fix nor an improvement.

Nothing that was fixed


vcpkg install for qpid-proton crashing

Seems to be crashing while attempting to install a portable 7zip.

Dup to #23448


Preserve context while wrapping analyzer_driver errors [phab:D1694]

Created by schroederc at 2017-06-05 21:42:26:

fromberger commented inline (context lost during migration) at 2017-06-05 21:49:12:
Suggestion: berr → goerrors
Rationale:  I can't figure out what the "b" is supposed to stand for. :)
Or alternatively: Alias the non-standard one instead, perhaps werrors.

fromberger accepted this revision at 2017-06-05 21:49:12

schroederc wrote at 2017-06-05 21:50:54:
Rename import

schroederc commented inline (context lost during migration) at 2017-06-05 21:51:09:
I was going for "base".

schroederc closed via commit 453cbb993716b8f1fe9d826268d8ef6eb29ae426 at 2017-06-07 16:33:39


Workaround for slow slow shell startup in bash

Operating system and version:
Ubuntu 20.10
5.8.0-29-generic
x86_64
nvm debug output:

nvm --version: v0.37.0
$SHELL: /bin/bash
$SHLVL: 1
whoami: 'barabazs'
${HOME}: /home/barabazs
${NVM_DIR}: '${HOME}/.nvm'
${PATH}: ${HOME}/bin:${HOME}/.local/bin:${HOME}/.go:${HOME}/.bin:/opt/android-studio/bin:${HOME}/.cargo/bin:/opt/flutter/bin:${HOME}/.yarn/bin:${NVM_DIR}:${NVM_DIR}/versions/node/v14.14.0/bin:/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games:/usr/local/games:/snap/bin
$PREFIX: ''
${NPM_CONFIG_PREFIX}: ''
$NVM_NODEJS_ORG_MIRROR: ''
$NVM_IOJS_ORG_MIRROR: ''
shell version: 'GNU bash, version 5.0.17(1)-release (x86_64-pc-linux-gnu)'
uname -a: 'Linux 5.8.0-29-generic #31-Ubuntu SMP Fri Nov 6 12:37:59 UTC 2020 x86_64 x86_64 x86_64 GNU/Linux'
checksum binary: 'sha256sum'
OS version: Ubuntu 20.10
curl: /usr/bin/curl, curl 7.68.0 (x86_64-pc-linux-gnu) libcurl/7.68.0 OpenSSL/1.1.1f zlib/1.2.11 brotli/1.0.9 libidn2/2.3.0 libpsl/0.21.0 (+libidn2/2.3.0) libssh/0.9.3/openssl/zlib nghttp2/1.41.0 librtmp/2.3
wget: /usr/bin/wget, GNU Wget 1.20.3 built on linux-gnu.
git: /usr/bin/git, git version 2.27.0
grep: /bin/grep (grep --color=auto), grep (GNU grep) 3.4
awk: /usr/bin/awk, GNU Awk 5.0.1, API: 2.0 (GNU MPFR 4.1.0, GNU MP 6.2.0)
sed: /bin/sed, sed (GNU sed) 4.7
cut: /usr/bin/cut, cut (GNU coreutils) 8.32
basename: /usr/bin/basename, basename (GNU coreutils) 8.32
rm: /bin/rm, rm (GNU coreutils) 8.32
mkdir: /bin/mkdir (mkdir -pv), mkdir (GNU coreutils) 8.32
xargs: /usr/bin/xargs, xargs (GNU findutils) 4.7.0
nvm current:
which node: ${NVM_DIR}/versions/node/v14.14.0/bin/node
which iojs:
which npm: ${NVM_DIR}/versions/node/v14.14.0/bin/npm
npm config get prefix: ${NVM_DIR}/versions/node/v14.14.0
npm root -g: ${NVM_DIR}/versions/node/v14.14.0/lib/node_modules

nvm ls output:

       v13.11.0
       v14.14.0
         system
default -> node (-> v14.14.0)
node -> stable (-> v14.14.0) (default)
stable -> 14.14 (-> v14.14.0) (default)
iojs -> N/A (default)
unstable -> N/A (default)
lts/* -> lts/fermium (-> N/A)
lts/argon -> v4.9.1 (-> N/A)
lts/boron -> v6.17.1 (-> N/A)
lts/carbon -> v8.17.0 (-> N/A)
lts/dubnium -> v10.23.0 (-> N/A)
lts/erbium -> v12.19.0 (-> N/A)
lts/fermium -> v14.15.0 (-> N/A)

How did you install nvm?
script install.sh from readme.
What steps did you perform?

Executed this: curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.37.0/install.sh | bash
Pasted this in my .bashrc file: export NVM_DIR="$([ -z "${XDG_CONFIG_HOME-}" ] && printf %s "${HOME}/.nvm" || printf %s "${XDG_CONFIG_HOME}/nvm")" [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh" # This loads nvm

What happened?
Opening a new shell was suddenly really slow. I've ran some tests with hyperfine (a CLI benchmarking tool).
This is the result when nvm is installed as explained in the readme:
Benchmark #1: bash -i
  Time (mean ± σ):     267.5 ms ±  20.6 ms    [User: 203.1 ms, System: 76.9 ms]
  Range (min … max):   236.3 ms … 309.3 ms    11 runs

What did you expect to happen?
Without nvm installed, the startup time is:
Benchmark #1: bash -i
  Time (mean ± σ):      34.4 ms ±   4.9 ms    [User: 29.0 ms, System: 5.2 ms]
  Range (min … max):    27.6 ms …  60.3 ms    88 runs

As you can see there is a significant difference. The culprit is this line: [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"
Eventually I've managed to implement a basic workaround to only source $NVM_DIR/nvm.sh when nvm is invoked.
My .bashrc now contains the following lines:
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/bash_completion" ] && \. "$NVM_DIR/bash_completion"
nvm() {
    if ! [ -x "$(command -v nvm)" ]; then
        [ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"
        nvm
    fi
}

The function `nvm` basically checks if nvm is a command (which means nvm.sh is sourced). If it's not a command, it executes the original nvm.sh script to make it available as a command.
This means that nvm will only be activated when needed and does not impact the loading time of the shell.

And the benchmark returns:
Benchmark #1: bash -i
  Time (mean ± σ):      34.1 ms ±   2.9 ms    [User: 28.2 ms, System: 5.7 ms]
  Range (min … max):    28.3 ms …  43.6 ms    82 runs

nvm runs nvm use by default, which takes nonzero time. You can nvm unset default, or add --no-use to the line that sources nvm.sh, as a workaround.
See also #2334 which is tracking these 100-200ms (which, while not really “significant”, is something i strive to minimize).

I can't believe I've missed that issue...
Thank you for the feedback. I will try your suggestion.

Hi @ljharb With your suggestion, the loading time is now around 48.2 ms.
Benchmark #1: bash -i
  Time (mean ± σ):      48.2 ms ±   3.4 ms    [User: 42.4 ms, System: 6.0 ms]
  Range (min … max):    43.4 ms …  56.9 ms    52 runs

Unfortunately both workarounds break node for other programs depending on it. Which is expected, but not something I've thought of...

Indeed; the full load time is currently necessary to have node available.


New functionality: collection.count

I would love to see support for collection.count queries in rxdb-hooks. Do you think this would best work as a useRxCount hook or as part of the useRxData hook?
If you could offer your feedback and approve of a direction then I would be happy to try to implement this. I don't assume that the maintainers have time to implement every feature request.

Hi @DevinFrenze. Thanks for bringing this up.
colleciton.count() has been added from rxdb version 13.8, so before adding support for it somehow, I would like to ensure compatibility between rxdb-hooks and rxdb 13. At the moment the only issue I can detect is #61 which I would say is a blocker. Once #61 is resolved, I would probably go about introducing a dedicated useRxCount hook to avoid overloading useRxData.
If you are still interested in giving it a go, I can ping you again once #61 is out of the way.


Add 6 more cells in Ireland for Notify load test

What
This should be reverted when they are finished
How to review
Code review

There are 12 routers and they didn't seem troubled by the soak testing, just exercised a bit


Shaka Player goes blank on switching to landscape mode

Have you read the FAQ and checked for duplicate open issues?
Yes
What version of Shaka Player are you using?
We have tested with 3.3.2 using the demo app. We have also tested using these versions  of Shaka Player on a custom ReactJS demo app using NextJS framework:

3.2.1
3.2.0
3.0.1
2.5.22
2.5.23

Can you reproduce the issue with our latest release version?
Yes
Can you reproduce the issue with the latest code from main?
Yes
Are you using the demo app or your own custom app?
We were able to reproduce the issue both on the demo app and the custom app.
If custom app, can you reproduce the issue using our demo app?
Yes
What browser and OS are you using?
Browser: Chrome Browser
OS: Android
Mobile Device Used: OnePlus 7 Pro, Samsung M51(Android 11), One plus Nord 2
Note: We were able to reproduce this issue consistently on other Android devices too.
For embedded devices (smart TVs, etc.), what model and firmware version are you using?
NA
What are the manifest and license server URIs?

Manifest file URL: https://storage.googleapis.com/shaka-demo-assets/bbb-dark-truths-hls/hls.m3u8
What configuration are you using?  What is the output of player.getConfiguration()?

We have used the demo app and custom app with default configs. Attaching the configs in the file titled defaultConfig.txt
defaultConfig.txt
What did you do?

Enable autorotate on the mobile device.
Continue rotating the phone to switch back and forth from a fullscreen mode to portrait mode.
Attaching the video illustrating the steps mentioned for reference.

On the custom app, when user clicks on fullscreen icon, we force the player to render in landscape mode. So, there is another way to reproduce the issue on such an app:

Click on fullscreen icon multiple times. This forces the user to switch between portrait and landscape modes.
There would be an instance during these steps when the player skin disappears and the video does not render but the audio continues playing in the background.

What did you expect to happen?
We expected that the video would continue playing normally with audio and video. We expect the player skin controls and the video to render properly.
What actually happened?

The video player screen goes blank and the audio continues to play. The controls of the video player disappear as well. We can still click on where the controls were to play/pause and perform other actions on the video but the icons and the video do not render.
Rate of reproduction on Shaka Player demo app: ~30%(3 out of every 10 times)

https://user-images.githubusercontent.com/27827510/164386961-923fda3b-87e8-42cc-bbab-fe759e393ff2.mp4

Can you test if the main branch still has the problem? Thanks!


Drop chain! usages/references

Fixes #328
The only places where chain! is still listed/used are the Changelog, the nom-1.0 porting guide and chain! unit tests

Closing this one, will split it in 3


stat/distmv: Add KL divergence for two Dirichlet distributions

Please take a look.

Based on the discussion in #509 , I fixed all the spelling mistakes in KL and changed distance to divergence.

Can I get your approval here too @vladimir-ch ?


Vscode crashes every time after it mistakenly analyses grammar.

VSCode Version: 1.5.2
OS Version: Windows 10 x64

Steps to Reproduce:

When I write js or jsx code, vsCode will mistakenly analyses grammar some time, then it underlines the "mistaken" code which is no mistake in fact. And after not long, vsCode would crash.
This kind of  case happens so many times recently. Especially when I`m writing js, jsx & json code. I use eslint in my project, dose it make influence for this case ?

Following is one piece of code that attend to make this bug occurs:
(mistakenly analyses grammar is "name": "zyin")

{
  "name": "zyin",
  "version": "0.0.1",
  "main": "localhost:8005/webpack-dev-server/index.html",
  "node-remote": "http://localhost:8005/*",
  "description": "zyin atm v2",
  "nodejs": true,
  "scripts": {
    "start": "node server.js --env=dev"
  },
  "window": {
    "icon": "zyin-icon.png",
    "title": "zyin-atm-2",
    "width": 1200,
    "height": 720,
    "min_width": 1200,
    "min_height": 720,
    "show_in_taskbar": true,
    "kiosk": false
  },
  "webkit": {
    "page-cache": false
  },
  "devDependencies": {

  },
  "dependencies": {

  }
}

Assuming this is an issue with the TS/JS grammar moving to @waderyan . fyi @alexandrudima though

@bpasero Thanks. It seems like it. When this issue occur, my cup utilization increase obviously, sometime approximately 100%

To find out more about this issue, we need to get at the process that is causing the high load. VS Code creates multiple processes, each with different tasks. Depending on your OS you can get at the full command line of the process and paste it here. On Mac, the Activity Monitor allows to find the PID of the process and from a terminal ps aux | grep <pid> reveals its arguments. On Windows a tool like Process Explorer or Process Hacker helps.
Once you have the information please update this issue with it. Thanks!

I find a process that occupies the 20%+ of CPU all the time. What should I do next ?

@BirdLeeSCUT thanks I think this is good enough, it is the renderer process for the window.

I've also noticed eslint being triggered for JSON files (like this package.json), and showing random errors (like in the screenshot above, it has underlined name, seemingly for no reason (unless it's thinking this is a JS file).
This is the error it gives when it underlines "name" in the package.json file.
[eslint] Parsing error: Unexpected token
___________________________________________
The name of the package.

Also, this happens only intermittently, and the eslint server doesn't turn on sometimes when I open the package.json file.
This is my full eslint config:
{
  "parser": "babel-eslint",
  "env": {
    "browser": true,
    "mocha": true,
    "node": true
  },
  "rules": {
    "no-const-assign": 2,
    "react/no-multi-comp": 0,
    "react/prop-types": 2,
    "react/jsx-no-bind": 2,
    "comma-dangle": [1, "always-multiline"],
    "new-cap": [2, {"capIsNewExceptions": ["Radium", "DragDropContext", "DropTarget", "DragSource"]}],
    "key-spacing": [1, {"mode": "minimum"}],
    "indent": [2, 2, {"SwitchCase": 1}],
    "no-else-return": 0,

    // allow funtions
    "no-use-before-define": [2, "nofunc"]
  },
  "plugins": [
    "react"
  ]
}

@bpasero That is not the renderer process (notice the indent level being equal to CodeHelper.exe). I believe it is the extension host that somehow comes under incredible stress, most likely from the mentioned eslint

fyi @dbaeumer

@BirdLeeSCUT are you able to reproduce this consistently with one file that you could share maybe?

@dbaeumer The first screenshot in here shows Microsoft/vscode-eslint#138

@bpasero  I will try to catch a way to reproduce thisissue when it happen again, since this issue happen indeterminately

@kumarharsh @alexandrudima the eslint bug got addressed in the latest eslint extension update. I am pretty sure that this is not caused by eslint. I mistakenly validated package.json files with eslint and all that happened was one error I reported. Can not make the extension host go grazy :-).
@BirdLeeSCUT can you reproduce this if you start code with --disable-extensions.

@jrieken Freezing ... markers ... is this the same underlying issue you mentioned today?

unsure - only if someone generate 10s of thousands of markers and uses the problems view

Without extension host profiling, we're just guessing here ...

For what it's worth, I have the impression the package.json "unexpected token" error is always triggered after I mess around with files in the project (copy/create/rename...). I then need to restart to make it go away.

@hville which version of ESLint are you using. I fixed the problem in the eslint extension to not validate package.json files.

@dbaeumer was using ESLint 3.6.0. Just updated to 3.6.1

@hville I was meaning the VS Code eslint extension (https://marketplace.visualstudio.com/items?itemName=dbaeumer.vscode-eslint)

@dbaeumer thanks. More details: EsLint extension 1.06 still faced some issue, apparently with loading data from json.schemastore.org/package (ETIMEDOUT) error. I'm guessing you are already aware since a new  1.07 version just appeared while typing this.

@hville json.schemastore.org/package  (ETIMEDOUT error) is a problem of our JSON schema support and has nothing to do with the ESLint extension itself. Can you please open a separate issue with steps.

ESLint analyzing JSON file has been fixed a long time ago. Since no additional information has been provided I will close the issue. Please ping if you still see the issue.


update action name

the name is not accurate, it is not actually a toggle button, change its name to avoid confusion and wrong expectation

This PR fixes #11552

Coverage increased (+2.6%) to 40.184% when pulling 95b0ac1cfda72633a0d918ce1f54b6a624cbde80 on alanren/rename-action into d244a14468e58655146b813decab7584388f30b4 on main.


Sidenav fix in calendar

Still can't get the Sidenav to work properly on small screens

Are you calling any script twice? Like once in the template and the same in the base that it extends? It tends to mess things up


update ec2 eni limits

Please ensure your pull request adheres to the following guidelines:

[x] For first time contributors, read Submitting a pull request
[x] All code is covered by unit and/or runtime tests where feasible.
[x] All commits contain a well written commit description including a title,
description and a Fixes: #XXX line if the commit addresses a particular
GitHub issue.
[ ] If your commit description contains a Fixes: <commit-id> tag, then
please add the commit author[s] as reviewer[s] to this issue.
[x] All commits are signed off. See the section Developer’s Certificate of Origin
[x] Provide a title or release-note blurb suitable for the release notes.
[x] Are you a user of Cilium? Please add yourself to the Users doc

updates ENI limits per the script
ideally this can be backported to 1.13, or at the very least 1.14 - we have a desire for r7gd's on a certain project and this is blocking that at the moment
thanks!
Update ec2 eni limits - current as of Oct 30, 2023

/test

@christarazi any chance this can be backported into the next 1.14 patch release?

for some reason it is not in master just in main, therefore not in 12.2 and 13.0-rc0


GitDoc not staying enabled

I don't know if this is related to me using VS Code Insiders, but it seems like GitDoc is not staying enabled. I enabled it once, but it doesn't seem to stick.
I'm going to test saving this setting to my workspace settings which should fix I think.

This is actually related to #12 😄 Currently, the GitDoc: Enable command only enables auto-comitting/pushing for the VS Code session, whereas GitDoc: Enable (Branch) actually stores the enablement setting in your workspace. In hindsight, this is highly confusing, and so I'm going to remove the GitDoc: Enable (Branch) entirely, and update GitDoc: Enable to persist the setting to the workspace. Then, if you only want to enable GitDoc on a specific branch, you can simply checkout that branch, and run the enable command 👍

AH! That makes more sense now. Woohoo! Thanks!

This has now been fixed, and behaves like my previous comment 👍


Uncaught TypeError: Cannot read property '0' of undefined

got this error while change circle radius (no layers in map except circle)
steps to regenerate :
in your live demo example https://geoman.io/leaflet-geoman
1 . remove all layers using remove layers tool
2. now draw one circle using circle tool
3.  choose edit layers and edit circle radius
now you will get this error in console
leaflet-geoman.min.js:1 Uncaught TypeError: Cannot read property '0' of undefined
at i._checkPrioritiySnapping (leaflet-geoman.min.js:1)
at i._handleSnapping (leaflet-geoman.min.js:1)
at i.fire (leaflet.js:5)
at i._onDrag (leaflet.js:5)
at i.fire (leaflet.js:5)
at i._updatePosition (leaflet.js:5)

Thx for reporting. There is already a PR #627 and will be merged soon

Fixed in Release:  2.7.0


Create provider config migration job

Description
Due to planned changes in Provisioner's schema, some changes to the database will be necessary. This PR adds new component that will be run as an init container inside Provisioner pod.
Changes proposed in this pull request:

Migration job created
Db integration test added

Related issue(s)

Code moved to https://github.com/kyma-project/control-plane/pull/699


Regression in statuses handling

  ubuntu-vm:
    Container ID:
    Image:              virtlet/cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-disk1.img
    Image ID:
    Port:
    State:              Waiting
      Reason:           ContainerCreating
    Ready:              False
    Restart Count:      0

and in the same output of describe pod, later i have:
  FirstSeen     LastSeen        Count   From                    SubObjectPath                   Type            Reason          Message
  ---------     --------        -----   ----                    -------------                   --------        ------          -------
  12m           12m             1       default-scheduler                                       Normal          Scheduled       Successfully assigned ubuntu-vm-with-cm to kube-node-1
  12m           12m             1       kubelet, kube-node-1    spec.containers{ubuntu-vm}      Normal          Pulling         pulling image "virtlet/cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-disk1.img"
  17s           17s             1       kubelet, kube-node-1    spec.containers{ubuntu-vm}      Normal          Pulled          Successfully pulled image "virtlet/cloud-images.ubuntu.com/xenial/current/xenial-server-cloudimg-amd64-disk1.img"
  10s           10s             1       kubelet, kube-node-1    spec.containers{ubuntu-vm}      Normal          Created         Created container with id virtlet__a54c47ad-daec-5933-711a-95a99334f9ff
  9s            9s              1       kubelet, kube-node-1    spec.containers{ubuntu-vm}      Normal          Started         Started container with id virtlet__a54c47ad-daec-5933-711a-95a99334f9ff

VM is accessible but status is still the same: ContainerCreating.

Looks like this issue was on old dind, with 1.6.2.
After cleaning up dind - can not reproduce this, so I'm closing it.


[Bug]: Loss of retained QoS 1 messages across cluster nodes

Environment

VerneMQ Version: <IP_ADDRESS>
OS: Docker Container on Amazon Linux 2 EC2 instance (Kernel 4.14.198-152.320.amzn2.x86_64)
Erlang/OTP version: <IP_ADDRESS>
Cluster size/standalone: 2 Nodes on different ec2 instances

Current Behavior
If the publisher and subscriber are connected to different cluster nodes, the last retained message is lost if the message is published less than 1 second before the subscription is completed by another client. When the publish and subscribe actions are over 1 second apart, 100% of messages are delivered. However, if the time interval is less than 1 second, the percentage of lost messages increases, reaching up to 70% when publish and subscribe actions are concurrent. If the publisher and subscriber are connected to the same node, no message loss occurs, even with concurrent publish and subscribe actions.
Steps to Reproduce:

Client A publishes a QoS 1 retained message with the message "offline" to topic T and waits 5 seconds.
Client A then publishes a QoS 1 retained message with the message "online" to topic T.
Introduce a variable sleep duration between 0 and 1 second.
Client B subscribes to topic T and waits for the "online" message or a sequence of "offline" followed by "online" messages for 15 seconds.

Expected behaviour
A retained message published with QoS 1 should always be delivered to subscribers.
Configuration, logs, error output, etc.
listener.ssl.use_identity_as_username=on
max_inflight_messages=20
max_offline_messages=100000
vmq_bridge.ssl.sbr0.topic.2=device/+/foo/bar out 1
vmq_bridge.ssl.sbr0.topic.1=device/+/baz/foobar/barbaz out 1
vmq_bridge.ssl.sbr0.keepalive_interval=60
vmq_acl.acl_file=/etc/vernemq/acl/vmq.acl
vmq_bridge.ssl.sbr0.try_private=on
listener.max_connections=350000
vmq_bridge.ssl.sbr0.keyfile=/vernemq/ssl/key.pem
log.console.level=debug
accept_eula=yes
listener.tcp.pproxy=<IP_ADDRESS>:1884
listener.ssl.crlfile=/vernemq/ssl_crl/crl.pem
plugins.vmq_bridge=on
distributed_cookie=cluster1
listener.tcp.default=<IP_ADDRESS>:1883
listener.tcp.pproxy.proxy_protocol=on
vmq_bridge.ssl.sbr0.cleansession=on
listener.http.metrics=<IP_ADDRESS>:8990
listener.ssl.default=<IP_ADDRESS>:8883
listener.ssl.require_certificate=on
listener.vmq.clustering=<IP_ADDRESS>:44053
listener.ssl.keyfile=/vernemq/ssl/cloudkey.pem
listener.ssl.cafile=/vernemq/ssl/ca-chain.pem
vmq_bridge.ssl.sbr0.client_id=7snn1n0nos930oqrqrpq6ps0355n60n58q225s08ospr441496n52or37
erlang.distribution.port_range.minimum=6000
log.console=console
max_online_messages=10000
vmq_bridge.ssl.sbr0.cafile=/vernemq/ssl/RootCA.pem
listener.tcp.pproxy.proxy_protocol_use_cn_as_username=on
vmq_bridge.ssl.sbr0=foobarbaz.iot.somewhere-1.amazonaws.com:8883
allow_anonymous=on
listener.ssl.certfile=/vernemq/ssl/cloud.pem
<EMAIL_ADDRESS>listener.http.default=<IP_ADDRESS>:8888
erlang.distribution.port_range.maximum=7999
vmq_bridge.ssl.sbr0.certfile=/vernemq/ssl/certificate.pem
listener.ws.default = <IP_ADDRESS>:8080

Code of Conduct

[X] I agree to follow the VerneMQ's Code of Conduct

@dlanzafame Thanks for your report. The retain store is eventually consistent; it has often been noted.
You can try this PR to see whether it lowers the rate of missed Publish: https://github.com/vernemq/vernemq/pull/2219
But ultimately, the proper solution to this is to introduce consensus into the distribution of retained messages. This will lower performance of the retain store drastically, but make users more happy who observe wallclock time of events.
I'm working on a solution for this.


Readme: new troubleshootings section

@pilhuhn @tsegismont can you have a look? Any idea of other points to add?
You can see it there: https://github.com/jotak/hawkular-grafana-datasource/tree/troubleshooting#troubleshooting

Maybe @mwringe knows where you could point users to. If we don't know how
to upgrade Origin Metrics then we should not suggest to do it.
2016-12-09 11:03 GMT+01:00 Joel Takvorian<EMAIL_ADDRESS>
@jotak commented on this pull request.
In README.md
https://github.com/hawkular/hawkular-grafana-datasource/pull/44:

+### Grafana fails to establish a connection or get data from hawkular
+
+* Check the URL: [host]/hawkular/metrics. Make sure there's no ending slash. When you open up this URL in a browser you should see the Hawkular logo, the installed version and a mention that the service is started.
+
+* Make sure any credential / token matches your installation. In general, if you installed a standalone hawkular-metrics server without any specific configuration you probably don't have any authentication information to provide. If you installed hawkular-services using its installation guide you will probably have to fill-in the basic auth fields. If you are using Hawkular from OpenShift, you have to provide a Bearer token in the Token field. Tokens can be generated temporarily (got to [OpenShift host]/oauth/token/request) or from a Service account in OpenShift.
+
+* Check your browser's javascript debugging tool. If you see an error mentioning issues with CORS, switch to proxy mode in the datasource configuration.
+
+### I can't query by tag, the option is not displayed
+
+Querying by tag was introduced before the plugin was properly versioned, so if you have a version >= 1.0.2 you should have it. However it is only enabled when it talks to hawkular-metrics >=0.20.0. To check your version of hawkular-metrics just open its status page in a browser ([host]/hawkular/metrics or [host]/hawkular/metrics/status).
+
+### I'm running Hawkular in OpenShift, connection is OK but I can't query any metric
+
+Check your version of hawkular-metrics ([host]/hawkular/metrics or [host]/hawkular/metrics/status). Prior to 0.16.0, metric names containing slashes, like in OpenShift, were unfortunately not showing up in Grafana; you could consider upgrading hawkular-metrics.
Well, actually I'm not sure how to upgrade metrics in openshift...
especially if it's enterprise with already enabled metrics
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/hawkular/hawkular-grafana-datasource/pull/44, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ABblttlEYfRKr_7vLZRL-zG6Q5v4tcEfks5rGSd9gaJpZM4LIvhY
.

You also should mention that the tenant is case sensitive. Hawkular != hawkular

Updated with your remarks

Updating Hawkular Metrics is described in the OpenShift documentation (https://docs.openshift.org/latest/install_config/upgrading/manual_upgrades.html#manual-upgrading-cluster-metrics)

Thanks @mwringe , I'll update with that link


Is this project still supported ?

Hello,
When importing this package with Mirror 53, compilations errors appear (FizzyFacepunch not properly overriding ClientSend and ServerSend Methods)
Are you planning on keeping this module up-to-date with Mirror ? Or should I use Steamworks.NET instead ?
Many Thanks

@mickev36 Check out the latest pull request. You can fix the issue quite easily just by swapping parameters yourself, which is what I did.

Lol, there's just a need to swap arguments. Who thought of making such changes to the repository?

I wouldn't say it's no longer supported, but more like slower compared to https://github.com/Chykary/FizzySteamworks updates. I've lightly tested the latest master branch, and it seems to be working fine with the latest mirror version.

@barsovya
Can you tell me what to do?
I'm struggling for the same reason as the poster

@1iryu Have you tried the latest master branch?

@LukeSeers
I setted up with "FizzyFacepunch-4.3.unitypackage" for unity (https://github.com/Chykary/FizzyFacepunch/releases/tag/v4.3)
Is this not so good?

That's not the master branch, that is a release. The master branch is this https://github.com/Chykary/FizzyFacepunch

I followed this way
I got an error after installing the unity package according to this method, so I copied the master branch here to a specific location, but I still get the error (although the error has decreased a bit).
environment
mirror v57
unity NET4.0
facepunch (https://www.youtube.com/watch?v=72cRiBkUZbY       <-- I seted up with the wayy)
Error sentence
"Assets\Mirror\Runtime\Transport\FizzyFacepunch\LegacyCommon.cs(54,38): error CS0117: 'P2PSessionError' does not contain a definition for 'NotRunningApp'"
"Assets\Mirror\Runtime\Transport\FizzyFacepunch\LegacyCommon.cs(54,38): error CS0117: 'P2PSessionError' does not contain a definition for 'NotRunningApp'"

I'm sorry, but I don't want this turning into text support. If your stuck you should join the community mirror discord and ask their.
But, anyway it says "NotRunningApp" meaning that you haven't Initialized the steam client. To tell if you have Initialized the steam client, you'll see that you'll be playing a game on your steam account.

@LukeSeers  "But, anyway it says "NotRunningApp" meaning that you haven't Initialized the steam client. To tell if you have Initialized the steam client, you'll see that you'll be playing a game on your steam account or you might have given it the wrong steam AppID."
I need to run a script to set this, but I'm getting an error so I can't run it
also What are other people using instead of Mirror?

@LukeSeers

The "setting up" in this repository also says "and copy it to the Assets / Mirror / Runtime / Transports / FizzyFacepunch folder in your Unity project".
So I thought the mirror is the basic network solution

This issue should have now been fixed from: https://github.com/Chykary/FizzyFacepunch/pull/23 there has not been a release as of yet so, to get the latest fixes please just replaces the files with the latest master branch: https://github.com/Chykary/FizzySteamworks


Improve Conditions

This PR encompasses a major refactor of Conditions in ProcedureKit, improving performance, fixing bugs, and adding new features (while also expanding test coverage and documentation).
Highlights:

Conditions are no longer Procedure subclasses, and are lighter-weight.
Condition processing is faster, and supports short-circuit evaluation for considerable performance improvements.
MutualExclusivity is now evaluated post-dependencies and condition evaluation (i.e. immediately before execute), resolving numerous issues and edge cases.
Bugs have been fixed.
Internal implementation details are no longer exposed to user code unexpectedly.
Added a new CompoundCondition (and AndCondition / OrCondition) to support logical “&&” and “||” operations on Conditions.

Breaking Changes (from prior Procedure v4 betas):
TL/DR: Almost all code built using the prior beta of ProcedureKit v4 will work with these new improvements while requiring only minimal changes.
The few areas of change that may impact existing code are:
For Condition subclasses:

Condition.add(dependency:) now functions exactly the same as Procedure.add(dependency:). It does not result in the framework automatically enqueuing / running the dependency.

Solutions:

If you add the dependency to a queue yourself (or otherwise cause it to run), continue using add(dependency:).
If you want the framework to schedule the dependency for execution immediately prior to evaluating the Condition, use the new Condition.produce(dependency:) method.

var mutuallyExclusiveCategory: String? is no longer available.

Solutions:

Use Condition.addToAttachedProcedure(mutuallyExclusiveCategory:) instead to add a mutually-exclusive category to the Procedure to which your custom Condition is added.
Use var mutuallyExclusiveCategories to query the currently-set categories (rarely needed outside the framework).

You can no longer call add(condition:) on a Condition.

Since Condition is no longer a Procedure subclass, it makes no sense to add a Condition (which is evaluated on a Procedure) to a Condition. However, ComposedCondition and CompoundCondition provide supported alternative patterns.
Solution:

Investigate ComposedCondition and CompoundCondition. These support almost all common scenarios.
For cases in which you previously attached a NoFailedDependenciesCondition to a Condition, you can use the new Condition.dependencyRequirements to automate checking for dependency failures / cancellation.

How Conditions are Scheduled and Evaluated
Here’s the new order of operations / evaluation / scheduling:

All of a Procedure’s (direct) dependencies must finish.
Then, asynchronous processing of theConditions begins. For each Condition:

If it has dependencies or producedDependencies:

The Condition evaluation (call to evaluate(procedure:completion:)) is wrapped in a BlockOperation.
All dependencies and producedDependencies are added as dependencies to the BlockOperation.
The producedDependencies and BlockOperation are added to an internal queue.
(Thus, all Condition dependencies must finish before the wrapped Condition evaluation is executed.)

Otherwise, the Condition’s evaluate(procedure:completion:) is called directly.

Condition results are aggregated until the final result is known. This may be before all Conditions are processed (as short-circuit evaluation is now supported). If the final result is known before all Conditions have been evaluated, any remaining Conditions may be skipped (and any remaining Condition-produced dependencies may be cancelled / never scheduled for execution).
If the final result is a failure, the attached Procedure is cancelled (with / without errors depending on whether the final result is .failure(error) or .success(false)). Processing is complete.
Otherwise, if the final result is a success (.success(true)):

If no mutually exclusive categories exist on any of the Procedure’s Conditions, the Procedure is ready to execute.
If mutually exclusive categories exist on any of the Procedure’s Conditions:

A single asynchronous lock request is made for the union of all of the mutually-exclusive categories.
Once the lock request is granted, the internal EvaluateConditions operation finishes, and the Procedure is ready to execute.
(The locks are released once the Procedure has finished.)

Additional Details

Mutual Exclusivity is now evaluated when Procedures are ready to execute (as the final step of Condition evaluation), instead of when Procedures are added to the queue.

This resolves several deadlock and unexpected dependency scenarios, while still ensuring that only one Procedure with each mutual exclusivity category is running simultaneously.
It also improves performance by only acquiring locks in a single request, and only when the Procedure is otherwise ready to execute.

The internal EvaluateConditions operation - and any Condition-produced dependencies - are no longer added to a user-visible queue.

Improved encapsulation of internal implementation details.
Prevents unexpected user queue starvation as a result of many long-running, outstanding condition evaluations / produced dependencies.

Conditions and Condition dependencies no longer appear in the Procedure.dependencies.

Improved encapsulation of internal implementation details.
Fixes edge-case bugs with things like NoFailedDependenciesCondition (issue: #515).

Condition evaluation now supports short-circuit evaluation, dramatically speeding-up performance in many cases.

The result of Condition evaluation may be known before all Conditions are evaluated. (For example, if a Procedure has multiple Conditions, as soon as one of them fails, the ultimate result is guaranteed to be a failure.) Thus, we can avoid evaluating any remaining conditions as soon as the result is known.
Minor Backwards-Compatibility Note:

This means that Procedures will fail with the first failure error that is returned by a Condition.
Condition evaluation is asynchronous, and the order in which a Procedure’s conditions are evaluated is not guaranteed. Whichever Condition fails first will provide the failure error.
If you are relying on Procedures cancelling with information about every failing Condition (or a specific Condition error amongst many possible), you will need to modify your expectations to match the new behavior. (This will likely only affect exhaustive test-cases that verify the cancellation errors in-depth.)
OrCondition may fail with multiple errors, as its evaluation can only be short-circuited if at least one Condition succeeds.

New Features:

CompoundCondition is now supported, to provide support for logical “&&” and “||” operations on a sequence of Conditions. (As a short-cut, you can also use AndCondition and OrCondition.)
let condition1 = TrueCondition()
let condition2 = FalseCondition()

// The following are each equivalent to a Condition encompassing “condition1 || condition2”
// i.e. if either condition1 or condition2 succeeds, the “orCondition” succeeds
let orCondition1 = OrCondition(condition1, condition2)
let orCondition2 = CompoundCondition(orPredicateWith: [condition1, condition2])
let orCondition3 = condition1 || condition2

CompoundCondition supports short-circuit evaluation, for improved performance.

Codecov Report

:exclamation: No coverage uploaded for pull request base (development@e8f4aa9).

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 e8f4aa9...ecb66c5. Read the comment docs.

This PR also resolves several race conditions and TOCTOU (time-of-check time-of-use) issues.
One example:
Previously, Conditions only had an add(dependency:) method. ProcedureQueue attempted to handle scheduling Condition dependencies as-needed, by filtering Condition dependencies already scheduled on the current queue:
// Filter out the indirect dependencies which have already been added to the queue
let indirectDependenciesToProcess = indirectDependencies.filter { !self.operations.contains($0) }

This approach has several problems, including:

The dependency could be scheduled on another queue.
The dependency could be added to the queue post-check, but before the call to add.
The dependency could have already finished (if something else previously scheduled it).

It's not safe to decide whether to add an Operation to a queue based on whether it's already on the queue.
This PR resolves both these issues in part by splitting Condition dependency management into two functions:

add(dependency:) adds a dependency. You are responsible for scheduling it. (Just like Procedure.add(dependency:))
produce(dependency:) adds a dependency that will be produced and finished prior to Condition evaluation. This handles scheduling at the appropriate time for you.

Splitting these options absolves the framework from trying to do things that are necessarily race-condition-prone, and enables the programmer to specify their intent more clearly.

Not-Frequently-Asked-Questions:

What if I previously added a MutualExclusivity condition to a Condition, to ensure that the Condition itself wasn't executed concurrently with other things?

Mutual Exclusivity can only be applied to Procedures. Since Condition is no longer a Procedure subclass, you can no longer add a MutualExclusivity condition directly to a Condition.

SOLUTION:

Extract out the code / logic that requires mutual exclusivity, and put it in a Procedure. (SeeAlso: BlockProcedure)
Add the MutualExclusivity condition to the new Procedure.
Modify your Condition to produce(dependency:) the new Procedure.
Reduce your Condition's evaluate function to simply evaluating the output of your new Procedure (and any other logic that does not require mutual exclusivity).

Thus, your logic that requires mutual exclusivity now lives in a Procedure embedded in the Condition (that the Condition produces as a dependency), and the Condition's evaluate() function simply transforms the output of that Procedure to success / failure of the Condition.


Google Mobile Ads SDK Developers Privacy  •  Terms Flutter App crashes when "google_mobile_ads: ^2.3.0" is added into pubspec.yaml

Plugin Version
"google_mobile_ads: ^2.3.0"
So I want to put ads into my app. I followed the instructions from (https://developers.google.com/ad-manager/mobile-ads-sdk/flutter/banner/get-started) and added everything from the docs. When ever I run the app it stops at
Running Gradle task 'assembleDebug'... √ Built build\app\outputs\flutter-apk\app-debug.apk.
then the app crashes.
Here the pubspec, AndroidManifest and main.dart:
pubspec.yaml:

google_mobile_ads: ^2.3.0

AndroidManifest.xml:

<meta-data
android:name="com.google.android.gms.ads.APPLICATION_ID"
android:value="ca-app-pub-3940256099942544~3347511713"/>

and main.dart:

import 'package:flutter/material.dart';
import 'package:google_mobile_ads/google_mobile_ads.dart';

Future<void> main() async {
WidgetsFlutterBinding.ensureInitialized();
MobileAds.instance.initialize();
await Firebase.initializeApp();

runApp(const MyApp(
backgroundColor: Colors.black,
));
}

The app runs without the
google_mobile_ads: ^2.3.0
Others:

minSdkVersion 23
compileSdkVersion 33
implementation 'com.google.android.gms:play-services-ads:7.5.0'
implementation 'com.android.support:multidex:1.0.3'

I Tried removing each code from the docs starting from
MobileAds.instance.initialize();
and running it each time. Found out that the
google_mobile_ads: ^2.3.0
Was the one causing it.
Im new to this so any help is appreciated

Hi @XShrimpReal
Can you share the complete crash output?
I also see you are using Firebase, have you completely installed it via installation document? If so, can you provide a completed and minimal reproducible code sample so that we may verify this?

Same issue for me.
if i remove the code for google_mobile_ads and remove dependency in pubspec.yaml everything works fine.
google_mobile_ads: ^2.3.0

@TiMeJuMp As I see from your sample project, it's incompleted setup since there is missing APPLICATION_ID on AndroidManifest.xml file.
Please also check guideline from the error message:
E/AndroidRuntime(10157): FATAL EXCEPTION: main
E/AndroidRuntime(10157): Process: com.example.google_ads_sample, PID: 10157
E/AndroidRuntime(10157): java.lang.RuntimeException: Unable to get provider com.google.android.gms.ads.MobileAdsInitProvider: java.lang.IllegalStateException:
E/AndroidRuntime(10157):
E/AndroidRuntime(10157): ******************************************************************************
E/AndroidRuntime(10157): * The Google Mobile Ads SDK was initialized incorrectly. AdMob publishers    *
E/AndroidRuntime(10157): * should follow the instructions here:                                       *
E/AndroidRuntime(10157): * https://googlemobileadssdk.page.link/admob-android-update-manifest         *
E/AndroidRuntime(10157): * to add a valid App ID inside the AndroidManifest.                          *
E/AndroidRuntime(10157): * Google Ad Manager publishers should follow instructions here:              *
E/AndroidRuntime(10157): * https://googlemobileadssdk.page.link/ad-manager-android-update-manifest.   *
E/AndroidRuntime(10157): ******************************************************************************
E/AndroidRuntime(10157):
E/AndroidRuntime(10157):
E/AndroidRuntime(10157): 	at android.app.ActivityThread.installProvider(ActivityThread.java:7774)
E/AndroidRuntime(10157): 	at android.app.ActivityThread.installContentProviders(ActivityThread.java:7299)
E/AndroidRuntime(10157): 	at android.app.ActivityThread.handleBindApplication(ActivityThread.java:7207)
E/AndroidRuntime(10157): 	at android.app.ActivityThread.access$1700(ActivityThread.java:287)
E/AndroidRuntime(10157): 	at android.app.ActivityThread$H.handleMessage(ActivityThread.java:2166)
E/AndroidRuntime(10157): 	at android.os.Handler.dispatchMessage(Handler.java:106)
E/AndroidRuntime(10157): 	at android.os.Looper.loop(Looper.java:255)
E/AndroidRuntime(10157): 	at android.app.ActivityThread.main(ActivityThread.java:8212)
E/AndroidRuntime(10157): 	at java.lang.reflect.Method.invoke(Native Method)
E/AndroidRuntime(10157): 	at com.android.internal.os.RuntimeInit$MethodAndArgsCaller.run(RuntimeInit.java:632)
E/AndroidRuntime(10157): 	at com.android.internal.os.ZygoteInit.main(ZygoteInit.java:1049)
E/AndroidRuntime(10157): Caused by: java.lang.IllegalStateException:
E/AndroidRuntime(10157):
E/AndroidRuntime(10157): ******************************************************************************
E/AndroidRuntime(10157): * The Google Mobile Ads SDK was initialized incorrectly. AdMob publishers    *
E/AndroidRuntime(10157): * should follow the instructions here:                                       *
E/AndroidRuntime(10157): * https://googlemobileadssdk.page.link/admob-android-update-manifest         *
E/AndroidRuntime(10157): * to add a valid App ID inside the AndroidManifest.                          *
E/AndroidRuntime(10157): * Google Ad Manager publishers should follow instructions here:              *
E/AndroidRuntime(10157): * https://googlemobileadssdk.page.link/ad-manager-android-update-manifest.   *
E/AndroidRuntime(10157): ******************************************************************************
E/AndroidRuntime(10157):
E/AndroidRuntime(10157):
E/AndroidRuntime(10157): 	at com.google.android.gms.ads.internal.client.zzee.attachInfo(com.google.android.gms:play-services-ads-lite@@21.3.0:20)
E/AndroidRuntime(10157): 	at com.google.android.gms.ads.MobileAdsInitProvider.attachInfo(com.google.android.gms:play-services-ads-lite@@21.3.0:1)
E/AndroidRuntime(10157): 	at android.app.ActivityThread.installProvider(ActivityThread.java:7769)
E/AndroidRuntime(10157): 	... 10 more

great after adding the appid in the manifest, the app runs again correctly. thank you.
But the error message you show here, i didn't found in my output logs.

Hello, I kinda forgot about this since i gave up on ads but now im back with the github code:
https://github.com/XShrimpReal/BetterNotes.git

These are the changes i added to my code. When i try to launch the app, it crashes everytime. I even have my firebase connected to my admob acc. All same accs linked but i cant get it to run without crashing
Main.dart
Future<void> main() async {
  WidgetsFlutterBinding.ensureInitialized();
  MobileAds.instance.initialize();
  await Firebase.initializeApp();

  runApp(const MyApp(
    backgroundColor: Colors.black,
  ));
}

Manifest.xml
<meta-data
                android:name="com.google.android.gms.ads.APPLICATION_ID"
                android:value="ca-app-pub-3940256099942544~3347511713"/>

pubspec.yaml:
google_mobile_ads: ^2.3.0

@XShrimpReal I tested with below sample code but can not reproduce the issue:

Sample code (Dart)
import 'package:firebase_core/firebase_core.dart';
import 'package:flutter/material.dart';
import 'package:google_mobile_ads/google_mobile_ads.dart';

Future<void> main() async {
  WidgetsFlutterBinding.ensureInitialized();
  MobileAds.instance.initialize();
  await Firebase.initializeApp();

  runApp(const MyApp(
  ));
}

class MyApp extends StatefulWidget {
  const MyApp({Key? key}) : super(key: key);

  @override
  State<MyApp> createState() => _MyAppState();
}

class _MyAppState extends State<MyApp> {
  @override
  Widget build(BuildContext context) {
    return MaterialApp(
      home: Scaffold(
        body: Container(color: Colors.red,),
      ),
    );
  }
}

Hello, I kinda forgot about this since i gave up on ads but now im back with the github code: https://github.com/XShrimpReal/BetterNotes.git

It seems you set visibility as private so that I can not see the repository. Please set it as public.

@XShrimpReal I tested with below sample code but can not reproduce the issue:
Sample code (Dart)

Hello, I kinda forgot about this since i gave up on ads but now im back with the github code: https://github.com/XShrimpReal/BetterNotes.git

It seems you set visibility as private so that I can not see the repository. Please set it as public.

Hello, I just changed the visibility to public

its located in the master branch

Hi @XShrimpReal
Thanks, now I can see it. But for the issue to be workable, it needs to be reproducible with a completed and minimal reproducible code sample that doesn’t include 3rd party plugins or complex production code. Please provide such a sample.
You may use my above sample code (minimal) combined with other setups (Android side) to elaborate the sample code. Or using google_mobile_ads example could be an option.
Thank you!

Hi @XShrimpReal Thanks, now I can see it. But for the issue to be workable, it needs to be reproducible with a completed and minimal reproducible code sample that doesn’t include 3rd party plugins or complex production code. Please provide such a sample.
You may use my above sample code (minimal) combined with other setups (Android side) to elaborate the sample code. Or using google_mobile_ads example could be an option.
Thank you!

Alright. Ill try to make a sample and test the google ads plugin. Thanks for the response

Hi @XShrimpReal Thanks, now I can see it. But for the issue to be workable, it needs to be reproducible with a completed and minimal reproducible code sample that doesn’t include 3rd party plugins or complex production code. Please provide such a sample.
You may use my above sample code (minimal) combined with other setups (Android side) to elaborate the sample code. Or using google_mobile_ads example could be an option.
Thank you!

Hello again, I have run and test the sample ads and it worked perfectly. I will try and apply to my code to see if it works. Thanks again

Another update. I was able to get the test banner ads to work on my app. Thank you again. I wil now try the rewarded type.

yes , i have also face like crashing with 2.3.0 and flutter sdk is 3.7.0. when i remove just code of google addmob and remove library from yaml file it's works fin but with this library it's crash my app.

yes , i have also face like crashing with 2.3.0 and flutter sdk is 3.7.0. when i remove just code of google addmob and remove library from yaml file it's works fin but with this library it's crash my app.

https://github.com/TiMeJuMp/flutter_google_ads_error/tree/master/google_ads_sample
try this sample code if it works out.
You probably have to add the ApplicationId in the appmanifest in android folder

@TiMeJuMp Thank you for reply and solved my issue.


Not work

hi, I'm not sure if Sony updated the api method or not, anyway the workaround for now is to follow the docs to re-fetch PSN_NPSSO and update it in the repository's settings and remove the secrets PSN_ACCESS_TOKEN and PSN_REFRESH_TOKEN, I tested it and it works fine: https://github.com/Swilder-M/playstation-box/actions/runs/7623614063

hi, I'm not sure if Sony updated the api method or not, anyway the workaround for now is to follow the docs to re-fetch PSN_NPSSO and update it in the repository's settings and remove the secrets PSN_ACCESS_TOKEN and PSN_REFRESH_TOKEN, I tested it and it works fine: https://github.com/Swilder-M/playstation-box/actions/runs/7623614063

太感谢了老哥


Added some 8.58 peoplesoft fixes

Added the keystore password to the response file.  Also added error action silent for deleting the tmep fils because it errors on locked files.  Also added 8.57-8.58 support for the modules.

Sorry that took so long, but the fixes are now merged into master.


import tflib error!

Could you give more details about your error?

If you use pycharm, you can solve the problem by doing the following: Right click on the src file -> Mark Directory as->Sources Root.

If you use pycharm, you can solve the problem by doing the following: Right click on the src file -> Mark Directory as->Sources Root.

谢谢，后来解决了，之前是因为没有安装 tflib，pip install tflib 就好了 @seasonSH

If you use pycharm, you can solve the problem by doing the following: Right click on the src file -> Mark Directory as->Sources Root.

谢谢，后来解决了，之前是因为没有安装 tflib，pip install tflib 就好了 @seasonSH

tflib is  not a external library. It refers to the file "src/tflib.py". Make sure you are in the correct working directory when you run the code.

If you use pycharm, you can solve the problem by doing the following: Right click on the src file -> Mark Directory as->Sources Root.

谢谢，后来解决了，之前是因为没有安装 tflib，pip install tflib 就好了 @seasonSH

tflib is not an external library. It refers to the file "src/tflib.py". Make sure you are in the correct working directory when you run the code.

两者都能工作，你做过 tflib 的打包和发布

That's weird... I never did. Are you sure it works?

That's weird... I never did. Are you sure it works?

代码不报错，而且函数也都能跳转到正确的位置；整个工程并没有运行

So it's not working?

So it's not working?

It do not work. But I'm not exactly sure whether my setting is  error.
我分别实现了numpy 和 mxnet 版本，可以工作；思路没错

I am pretty sure there is something wrong with tflib. If you still want to use this tensorflow implementation, try to uninstall tflib library you have and fix the working path.


Update WebExtension notification doc to include some screenshots

Request type

[ ] New documentation
[x] Correction or update

Page to change
If this request relates to an existing article, please give its URL:
https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/notifications/TemplateType
Details
Please describe the change you are requesting. If you know of technical experts who can review the change, please mention them.
IMHO it would be good to include some screenshots for Firefox on all three platforms (Windows/MacOS/Linux), at least; so one get's an impression of what the notification looks like.
Especially for https://developer.mozilla.org/en-US/docs/Mozilla/Add-ons/WebExtensions/API/notifications/TemplateType to show the differences/differentiation between the notification types.
Maybe also mobile systems (Android, iOS).
Acceptance criteria

[ ] New images added to page

I did not add an image to the TemplateType page, I added it to the main page for the API: notifications


Highlight custom node - Shortcut key + more vibrant highlight color

What is the problem that needs solving?

Multiple clicks to get to the command.
Hard to identify highlighted nodes because of the default green color.

How would you like to see it solved?

Add a shortcut key.
Change highlight color to something more vibrant so it pops even when zoomed out. Thicker lines would also help.

👍

Going to have to investigate how involved this is with the Dynamo 2.13 UI. In short, I really wish that the team would just allow this.

This is a small preview of what I am thinking for that

This is a small preview of what I am thinking for that
The unfortunate result of this is it might wipe out your custom settings since it is a new version of the settings

Nice, this will definitely help! 👍 👍 :

@Lazarica-t  - are you willing and able to "beta" test a new release for me? It represents a pretty big change to the codebase, but includes new features like the one above.

Nice 👍
Font size for groups has been fixed.
Highlights are definitely much better now and the shortcut works like a charm.
So far everything worked as intended. 👍
The only thing that needs updating is the version numbers (they don't match):

Awesome. Thank you for testing and catching that version number. That should be updated when I got publish too. Excited to get this release out!


Content changes energy grants calculator

PT Story: https://govuk.zendesk.com/agent/tickets/103208406

Content changes energy grants calculator

Factcheck
https://smart-answers-pr-103208406.herokuapp.com/energy-grants-calculator
https://smart-answers-pr-103208406.herokuapp.com/energy-grants-calculator/y/all_help/benefits/1898-02-05/none/on-or-after-1995/flat/ground_floor/draught_proofing,electric_heating,loft_attic_conversion,mains_gas
Expected changes

URL on Gov.UK

Before

After

Stephen Gill has OKed this change..  @erikse @pmanrubia kindly review

Nice work @ikennaokpala - this looks good to me.


Remove unused debug-base image

What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #
Does this PR introduce a user-facing change?:

NONE

Nice catch!
/approve


Frontend Project "responsive navbar" Hamburger Visibility Correction

Describe the Feature you want to end
Correcting responsive bar hamburger which displays only on smaller screens.
Expected behavior
Making responsive navbar hamburger which displays only on smaller screens.
Screenshots (optional)
Current Design

Expected Updated Design
On large screen

On small screen

Additional context (optional )
N/A

@MohitGupta121 Kindly assign me this issue.


Client Allocation Request for: LeoCheung

Client Allocation Questions
Core Information

Name: LeoCheung
Website / Social Media: https://github.com/LeoZCH
Region: Greater China
DataCap Requested: 200TiB
Addresses to be Notarized: f3v7x4a2aapgx6o2r477tenoin3u5oadaeqyd7kjdsitykvf4ok7vq2utcyh34lmu5u7oybs25ff6s4dbudpma
Notary Requested: MegTei

@LeoZCH Please subscribe to notifications for this Issue to be aware of updates. Notaries may request additional information on the Issue.

@MegTei This application is for the Slingshot Restore Project

In which region(s) do you intend to use the DataCap?
China

How did you hear about the FIL+ program? Do you have a good understanding of the network and/or are involved in the web3.0 community?

I am a Filecoin researcher and one of community member from 2020. I pay attention to FIL+ from the start of notary govermance. I can offer my own github website: https://github.com/LeoZCH. I have ever worked in a storage provider company, and I am familiar to the filecoin's seal process and economy structures. Last year, I was selected to be as a member of official security Research Fellowship(https://security.filecoin.io/bug-bounty/ fortunately. Besides, I have taken part in the slingshot competition in phase2.2, 2.4, 2.5(the Project are FileZoo and FileWarehouse).

What is your registered business name & website?
I can offer my own github website: https://github.com/LeoZCH.

Provide a description of your business, the industry you work in and what you do.
I hope Filecoin can become storage foundation of web3.0.

What type/ category of data is being stored? (E.g Public data-back-up files, private encrypted files etc)
The dataset is data-back-up file.
I have submitted the application as a client, and I has been assigned the dataset "
common-crawl - april 2021(https://commoncrawl.org/2021/04/april-2021-crawl-archive-now-available/)"

Dataset Description：
The data was crawled April 10 – 23 and contains 3.1 billion web pages or 320 TiB of uncompressed content. It includes page captures of 1.35 billion new URLs, not visited in any of our prior crawls.

How much data will you onboard each week?
Around 50T

For how long do you intend to store your data with Filecoin?
500 days

Have you previously received DataCap? If so, please link to any previous requests/ github issues.
Yes @ has give me 10TiB,but it is not enough for me. I need 500TiB at least.
https://github.com/filecoin-project/filecoin-plus-client-onboarding/issues/1278

Are you aware of and do you intend to use any advanced features (e.g. Fast Retrieval) with your storage deals? If so, please specify the feature.
I will choose some providers who support the Fast-Retrieval to store my data.

How frequently do you intend to retrieve data stored on Filecoin e.g. monthly, a couple times a year, infrequently.
anytime

MINER DETAILS

How many miners do you plan on using to distribute the data, providing their ID's?
I need 3 miners at least in the official forms https://docs.google.com/spreadsheets/d/1Skga2Yn0BD7CDgT1WQmKtPJ3nxhQ4QWd45e78Y42Wjc/edit?usp=sharing

Are any of those miners controlled by yourself / your organization and if so, what is the percentage?
No

Do you agree on providing transparency of DataCap allocation decisions & execution details in public to prevent excessive/unfair self-dealing?
Totally Agree.

HI @LeoZCH I have attempted to approve this request, but it is failing, Ive asked for help to look into it.

These clients are requesting much larger allocations of DataCap, which are more appropriate through their large dataset applications. The notary here has 60TiB of total DataCap remaining, so these requests will fail.

@galen-mcandrew so what can I do?  should I ask large-dataset-datacap for DataCap?

HI @LeoZCH I have attempted to approve this request, but it is failing, Ive asked for help to look into it @fabriziogianni7 .

thanks @MegTei for your support


Unify local potential energy computation

The potentials are constructed complex (eg Hamiltonian:27), but they should all be real, right?

OK I see; they should be but it's annoying because of the way G_to_r works.


Problem with selecting and sorting

Hi,

When I click 'select all' nothing happens. No interfaces or bays are selected.
Created a few interfaces for testing A[1-4], then B[1-4]. Sorting order is:
A1
B1
B2
A2
B3
A3
A4
B4
When I added C[1-4] it was even worse. It was sorted but numbers first, letters just randomly. Is it possible to order them in alphabetical order?
Thank you.

Please see #284


Issue running a library that internally uses python -m pip ...

I understand the issue behind this, uv is replacing pip so there is no pip in the virtualenv, I am wondering if there is a way to ensure there is a pip in the venv using uv correctly.
MRE:
pyproject.toml
[project]
name = "uv-test"
version = "0.0.0"
requires-python = ">=3.10,<3.11"

dependencies = [
    "numpy == 1.26.3",
    "great_expectations == 0.18.1",
    "spacy[transformers] == 3.6.1",
]

lock/sync and then run:
>> uv run spacy download en_core_web_md-3.6.0 --direct
/home/edgy/code/nrwl/scripts/uv-test/.venv/bin/python: No module named pip

Under the hood spacy download is firing off python -m pip *args which understandably blows up. In our docker images and pipelines I can uv pip compile to get a requirements.txt and use the system pip to install things and spacy is happy.
But locally it picks up the .venv and triggers the error above.

Maybe use
uv add --dev pip

Or uv run --with pip spacy download  ... to add it temporarily.

You could also do something more controversial and alias pip to uv pip which would work fine if they're not depending on less common pip behaviors.

Was coming to the realisation pip isn't a special python tool, it's just a module I can use as a dependency. Thanks for the confirmation on the solution I should have realised yesterday. I'll confirm it works shortly.

Adding pip as a specified dependency did work.
Surprisingly --with pip didn't work, it did install pip before running.
>> uv run --with pip spacy download en_core_web_md-3.6.0 --direct
Installed 1 package in 8ms
/uv-test/.venv/bin/python: No module named pip

What did you end up doing to solve it? uv tool run --with pip spacy download en_core_web_md-3.6.0 --direct works for me, for what it's worth.

I think the uv run version fails due to how our environment layering works... They use [sys.executable, "-m", "pip", "install"], and I guess sys.executable refers to the base interpreter despite the fact that we layer the --with requirements on top as a separate environment.

I did not try uv tool run, i ended up adding pip to the projects requirements, as spacy does indeed require it :)
Ill keep uv tool run in mind next time i encounter an odd situation.
At this point we have successfully migrated all projects at work to uv, so happy with the current state of things. Thanks for all your work on this tool. Looking forward to if/when build tooling is in house.

Awesome, thank you @EdgyEdgemond. (We do have uv build but maybe you're referring to something different :))

I think I'd consider this a bug, though it's hard to say, arguably SpaCy should be importing / calling pip some other way than via subprocess... We can only fix this by redesigning the overlay system.

I think this is an edge case of a library performing under assumptions, that can be handled with existing functionality. It should have pip as a dependency in an ideal world etc. It would be nice to work around using --with but not a deal breaker.
@charliermarsh I was thinking of publish architecture not build, twine etc :)

I installed a spacy model using the given command and it worked.
uv tool run --with pip spacy download de_core_news_lg-3.7.0 --direct

But, when I tried to use it in the given code. It gives me an error.
Code:
import spacy
nlp = spacy.load("de_core_news_lg")

Error:
OSError: [E050] Can't find model 'de_core_news_lg'. It doesn't seem to be a Python package or a valid path to a data directory.

Why ?

I solved this by adding pip as a requirement of my project (as it is a requirement of spacy), and ran spacy in the venv directly.
Im not sure if uv tool puts pip somewhere else and as a result spacy download ends up in a different location. That would be my guess without understanding the internals like @charliermarsh

@EdgyEdgemond
Could you please explain how to add pip as a requirement ?

Simple as adding pip to your dependencies. pip is just another python package.
dependencies = [
    ...,
    "pip"
]


Automated Package Upgrade

:tada: This PR is included in version 7.7.96 :tada:
The release is available on:

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket: