Update 8tracks as hard

Were you able to gain contact with them?

No, I didn't contact them but the information I added is part of their privacy policy.

But were you able to delete an account with them @WebSnke ?

But were you able to delete an account with them @WebSnke ?

I have never had a account on 8tracks.
But this is what 8tracks privacy policy says:
"You may view, update, correct, or delete your user information and preferences by contacting us at<EMAIL_ADDRESS>

Hmm, that puts us in a weird position. We typically ask people to submit proven instructions. @SvicidalBug tried to delete and couldn't, hence the impossible, but if it proved to work now, then we can change. Sadly we cannot trust on privacy policies alone, because we have seen multiple times places where it failed.

Hmm, that puts us in a weird position. We typically ask people to submit proven instructions. @SvicidalBug tried to delete and couldn't, hence the impossible, but if it proved to work now, then we can change. Sadly we cannot trust on privacy policies alone, because we have seen multiple times places where it failed.

Ok, I will try to create an account and delete it soon. It would have to work as I am in the EU, fortunately.

Hmm, that puts us in a weird position. We typically ask people to submit proven instructions. @SvicidalBug tried to delete and couldn't, hence the impossible, but if it proved to work now, then we can change. Sadly we cannot trust on privacy policies alone, because we have seen multiple times places where it failed.

Ok, I will try to create an account and delete it soon. It would have to work as I am in the EU, fortunately.

There is now a delete button. I will try to use that one.


python310Packages.google-cloud-monitoring: 2.10.1 -> 2.11.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from passthru.updateScript.
meta.description for python310Packages.google-cloud-monitoring is: "Stackdriver Monitoring API client library"
meta.homepage for python310Packages.google-cloud-monitoring is: "https://github.com/googleapis/python-monitoring"
meta.changelog for python310Packages.google-cloud-monitoring is: ""
Updates performed

Ran passthru.UpdateScript

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 2.11.0 with grep in /nix/store/lgq7wfslxkc31lmkj6j5jylzl8y94y3f-python3.10-google-cloud-monitoring-2.11.0
found 2.11.0 in filename of file in /nix/store/lgq7wfslxkc31lmkj6j5jylzl8y94y3f-python3.10-google-cloud-monitoring-2.11.0

Rebuild report (if merged into master) (click to expand)

2 total rebuild path(s)

2 package rebuild(s)

First fifty rebuilds by attrpath
python310Packages.google-cloud-monitoring
python39Packages.google-cloud-monitoring

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/lgq7wfslxkc31lmkj6j5jylzl8y94y3f-python3.10-google-cloud-monitoring-2.11.0 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

(The Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the trusted-users list or you can use sudo since root is effectively trusted.
Or, build yourself:
nix-build -A python310Packages.google-cloud-monitoring https://github.com/r-ryantm/nixpkgs/archive/d65060b9ad477c586447c5c21381c439f8c09055.tar.gz

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/lgq7wfslxkc31lmkj6j5jylzl8y94y3f-python3.10-google-cloud-monitoring-2.11.0
ls -la /nix/store/lgq7wfslxkc31lmkj6j5jylzl8y94y3f-python3.10-google-cloud-monitoring-2.11.0/bin

Pre-merge build results
We have automatically built all packages that will get rebuilt due to
this change.
This gives evidence on whether the upgrade will break dependent packages.
Note sometimes packages show up as failed to build independent of the
change, simply because they are already broken on the target branch.
Result of nixpkgs-review run on x86_64-linux 1

2 packages built:

python310Packages.google-cloud-monitoring
python39Packages.google-cloud-monitoring

Maintainer pings
cc @SuperSandro2000 for testing.

Result of nixpkgs-review pr 186190 run on x86_64-darwin 1

2 packages built:

python310Packages.google-cloud-monitoring
python39Packages.google-cloud-monitoring


Colons in hostname cause an error on Windows

What is the issue?
Including a colon in the hostname such as localhost:6000/my/model causes an error on windows:
$ ollama create -f ../models/Modelfile localhost:3000/library/tmp
transferring model data
reading model metadata
creating template layer
using already created layer sha256:4fed7364ee3e0c7cb4fe0880148bfdfcd1b630981efa0802a6b62ee52e7da97e
using already created layer sha256:fa8235e5b48faca34e3ca98cf4f694ef08bd216d28b58071a1f85b1d50cb814d
using already created layer sha256:d47ab88b61ba20ed39a1b205a7d5a8e201dcf09107e6b05f128778c32baa4a69
using already created layer sha256:e14c21df1d1c6baff291558d0da327e5aabe4d4e7dd97bc1bf173e535f2ab210
using already created layer sha256:cb4e88e025cabd86f873cd94972dc82cfd883336b2294882a5c28af996a4db92
writing manifest
Error: mkdir C:\Users\jmorg\.ollama\models\manifests\localhost:3000: The directory name is invalid.

OS
Windows
GPU
No response
CPU
No response
Ollama version
No response

What should this resolve to in a filepath? I propose host%port/..

That seems like a great choice


Update accessibility-statement.html.erb

with a terrible change

Hi Ben - not sure that the sentence reads well with the change as it would say 'We are sometimes always'. Could you revise?

@benvand would be good to know your thoughts around the change. Were you uncomfortable with us saying we're always looking to improve our accessibility? To me, I think the original statement is accurate, but we don't always prioritise the work if other high priority things come along (I don't think we should say that in the page though)


all: consider generalising the random source parameter type

We use a *rand.Rand as the source of randomness for routines we provide that need this. Recently, a new rand package was added to the golang/exp repo. For the most part this is a drop in replacement, but gonum clients can not use this. If we define a rand interface that matches the method set of *rand.Rand then that package will be usable. Is this something that we want to do? The alternative is to back up to the rand.Source-ish level and take that as the argument - this needs a shim to convert the signatures between the two.

@btracey Do you have a view on this?

I am ok with that even if we should also perhaps check going through an interface call doesn't impact too negatively a few meaningful (real life?) benchmarks.
note there are a few interesting differences between the two, and we should be careful not to paint ourself into a corner while creating our own Rander interface.

exp/rand.Rand and math/rand.Rand do have a few differences:

https://godoc.org/golang.org/x/exp/rand#Rand
https://godoc.org/math/rand#Rand

ie: exp/rand.Rand has:

func (r *Rand) Uint64n(n uint64) uint64
func (r *Rand) Seed(seed uint64)

while math/rand.Rand doesn't have Uint64n and has the following signature:

func (r *Rand) Seed(seed int64)

Yes, I think we should do this.

We should wait for the proposal document that @robpike has said is coming.

The proposal is #21835.

Thanks, Rob.

On the basis of the proposal, I'd like to suggest that we use the exp/rand.Source and change from math/rand to exp/rand, and then when the Go standard library makes the shift, change the import paths. This seems like the easiest path to follow.
@robpike The proposal is almost silent on the behaviour of the rand.Source that would by used in the Go2 math/rand package; if the implementation being used in exp/rand is used verbatim, there would be a change in the source stream method's signature from Int64() int64 to Uint64() uint64, but this is not explicitly discussed in the proposal. Would that change be part of the proposal (the comment above is contingent on this being true).

@kortschak That question is in fact unresolved, but perhaps it will end up that the new Source contains both.
I would be happy to work with you to figure out what exp/rand should look like for you. That is somewhat independent of the proposal.

The shape of exp/rand as it stands at the moment looks good to me. Retaining both looks like a reasonable way to retain backwards compatibility, though it's a little sad to expand the API surface.
I'll wait for others to comment here, but what you've said works for me.

I agree with @kortschak , the proposal sounds good and seems to be an improvement.
For your information @robpike , we essentially have the following use cases:

Numerical simulations like Monte Carlo rely on the statistical properties of the generator. Being a good random number is much more important that being fast.
We provide a lot of probability distributions that are outside the scope of math/rand (i.e. Gamma). We would like to support both the case where the user supplier their own random generator (currently we demand a *math/rand.Rand), or they do not and we use a default seed.
We have a fair number of tests that can fail with some small probability (especially ones testing the probability distributions). We'd like to have consistent tests to avoid the (small chance of flakiness).

It seems like your proposal is in line with all of these goals.

@robpike I just made a now experimental foray into switching to exp/rand and struck a minor problem that will hold this until go1.11 is released. We support 3 Go releases, but exp/rand depends in math/bits for a single call to bits.RotateLeft64. Since math/bits was only added in go1.9, we have two releases that would be broken by this change. What is the prospect of a change being accepted to exp/rand that backports the bits.RotateLeft64 as an unexported function to the rng.go file?

Instead, I would suggest we do a version of that code and build-tag it by version.

That sounds good to me: the code is question is only a couple of lines. How far back? Just to 1.7 would work for us - I don't recall the Go support policy.

This change, being performed before exp/rand went into the Go2 standard, has the net result in the meantime of making gonum uncompatible with math/rand sources of randomness a host program may have otherwise.
I am in the process of replacing old statistics code with calls to gonum and just realized that I cannot share randomness sources between both sides of my program. Of course I built an adapter in the meantime.
Is there any plan to integrate exp/rand this into Go2? Otherwise will this API decision to drift apart from the Go standard be reconsidered?

Gonum will stay as it is. The question relating to the exp/rand and Go is a question for golang-dev (or less likely at golang/go#21835).


Order-only dependencies trigger unneeded actions

Here is very artificial example:
rule CC
    command = gcc -c -o $out $in
build b.o: CC b.c
build c.o: CC c.c || b.o

Example of what's going wrong:
touch b.c c.c
ninja
touch b.c
ninja -v c.o

Second ninja invocation triggers completely unnecessary rebuild of c.o

If I understand it correctly this is indeed intentional to match Make's behavior.


Incorrect use of free() in ikev2_print_id() causes heap corruption/crash

During the authentication process, ikev2_print_id() hits the following switch case when the peer ID is the Subject/CN of a X509 certificate provided by the client:
    case IKEV2_ID_ASN1_DN:
        if ((str = ca_asn1_name(ptr, len)) == NULL)
            return (-1);
        if (strlcpy(idstr, str, idstrlen) >= idstrlen) {
            free(str);
            return (-1);
        }
        free(str);
        break;

The problem here is that ca_asn1_name() calls X509_NAME_oneline(), which in turn allocated the memory pointed to by str with OpenSSL’s allocator, not malloc(). Calling free() on str results in a heap corruption (at least on Linux with glibc) since the first 16 bytes are interpreted by free() to be heap metadata, when in fact they’re client-controlled data from the Subject of the X509 certificate. The fix for this is simply to call OPENSSL_free() instead.
This bug might actually be CVE-worthy since the attacker controls the heap data pre-auth, though exploitation is hard - the Subject/CN from the cert would have to result (after ASCII-encoding from X509_NAME_oneline()) in valid pointers to be used by a write-what-where primitive during the free() call. But I haven't proven it impossible, and could lead to code execution with some work (especially if iked was compiled in a non-standard way, e.g. no RELRO). See PR #91 for fix.

Thank you for your report, very nice catch! It doesn't help that the X509_NAME_oneline man page  only says "If buf is NULL then a buffer is dynamically allocated and returned" and does not specify how to free it.
Regarding the impact: Looking at the OpenSSL code I do understand that the malloc implementation can be changed via CRYPTO_set_mem_functions but isn't the default still using malloc()?

Right, after taking a deeper look this is probably because the system I caught the bug on was using BoringSSL vice OpenSSL. BoringSSL's implementation of OPENSSL_malloc is definitely different from OpenSSL, and the BoringSSL documentation/code comments seem to strongly hint at undefined behavior when mixing their allocation functions with free().

I found and fixed a few more hidden cases of OPENSSL_malloc() in 5eb36ff. Feel free to reach out if you find any that we missed. We have also added a notice to the libressl man page to make sure people are aware of this problem in the future


Lab 5 - Q5 - Why am I getting different answers?

@JasonSills I'm answering Q5 and I used code in 2 different ways. A short and long way. But they don't add up and I am not sure why. Can I please get some help pinpointing my mistake?
Here is my code:
5. Differences in Accidents
Question: Are there differences in the proportion of accidents that result in harm each day of the week?

RESULTS:

@swest235
In the "short version" you are analyzing both injuries and fatalities, but in the "long version" your analyzing only injuries.
In the short version:
mutate(harm_acc = Totalinjuries > 0 | Totalfatalities > 0) %>%
In the long version:
select(day, Totalinjuries) %>%
If we remove Totalfatalities from the short version you will have the same numbers.

@JasonSills ok, that makes more sense. Does counting total injuries and total fatalities double count fatalities? I was under the impression that total injuries included fatalities, is that not the case?

@swest235
The data dictionary states that total injuries are non-fatal injuries.


coredns: add support for plugins

Description of changes
Solves https://github.com/NixOS/nixpkgs/issues/146603
Usage:
coredns-fanout = pkgs.coredns.override {
  externalPlugins = [
    {name = "fanout"; repo = "github.com/networkservicemesh/fanout"; version = "v1.9.1";}
  ];
  vendorHash = "<SRI hash>";
};

This PR is based on https://github.com/NixOS/nixpkgs/pull/205649 . I've made 3 changes:

rebased it on master
added go mod vendor to the end of modBuildPhase
modified the externalPlugins argument to take the plugin name, repo and version

this allows plugins to be pinned, which was a request made on the original PR

dropped the list of official upstream plugins (external-plugins.nix)

this was convenient but not necessary. removing it means it doesn't need to be kept up to date.

Things done

Built on platform(s)

[x] x86_64-linux
[ ] aarch64-linux
[ ] x86_64-darwin
[ ] aarch64-darwin

[ ] For non-Linux: Is sandbox = true set in nix.conf? (See Nix manual)
[ ] Tested, as applicable:

NixOS test(s) (look inside nixos/tests)
and/or package tests
or, for functions and "core" functionality, tests in lib/tests or pkgs/test
made sure NixOS tests are linked to the relevant packages

[x] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
23.11 Release Notes

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[x] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module

[x] Fits CONTRIBUTING.md.

I made the suggested changes.

Thanks! I've squashed it into a single commit.

When coredns gets updated, and I use externalPlugins, does the build continue with stale vendored code, or does it fail?

My understanding (based on trying the 1.10.1 -> 1.11.0 upgrade and reading https://github.com/NixOS/nixpkgs/blob/master/pkgs/build-support/go/module.nix ):
The package version is part of the -go-modules derivation name. When the version changes goModules will be rebuilt. If the vendored dependencies have changed, then the vendorHash won't match and the build will fail.
I was worried that it might be possible for a new version to build successfully against old modules if you had a cached goModules, but I don't think this can happen since the version is part of the derivation name.

The package version is part of the -go-modules derivation name. When the version changes goModules will be rebuilt. If the vendored dependencies have changed, then the vendorHash won't match and the build will fail. If the vendored dependencies haven't changed then it will build successfully.

Perfect. Thanks!

Thanks!

sry to barge in like this but coredns is failing in staging-next with the following, mite be related.
Below is the build log of derivation /nix/store/fy12vfg6j6v86j997is0chhnypis75c9-coredns-1.11.0.drv. It was built on ssh://localhost.

unpacking sources
unpacking source archive /nix/store/9g5sy1favi7bawr3ynjdid2ssj0hnwv3-source
source root is source
patching sources
updateAutotoolsGnuConfigScriptsPhase
configuring
building
Building subPackage .
# github.com/quic-go/quic-go/internal/handshake
vendor/github.com/quic-go/quic-go/internal/handshake/crypto_setup.go:362:37: cannot use h.allow0RTT (variable of type bool) as tls.QUICSessionTicketOptions value in argument to h.conn.SendSessionTicket

This looks like the same issue: https://github.com/quic-go/quic-go/issues/4021
Possibly this is a result of https://github.com/NixOS/nixpkgs/pull/254878 ?

So, what mite be the correct approach here; we can just do buildGo119Module to build and it will succeed I guess. How about other options?

coredns 1.11.1 is supposed to have the fix (https://github.com/coredns/coredns/pull/6252). it builds successfully for me on staging-next:
diff --git a/pkgs/servers/dns/coredns/default.nix b/pkgs/servers/dns/coredns/default.nix
index 2dcfc538be45..8078018625a2 100644
--- a/pkgs/servers/dns/coredns/default.nix
+++ b/pkgs/servers/dns/coredns/default.nix
@@ -4,7 +4,7 @@
 , fetchFromGitHub
 , installShellFiles
 , externalPlugins ? []
-, vendorHash ? "sha256-TvIswNQ7DL/MtYmMSxXf+VqKHcmzZVZwohOCvRWxBkY="
+, vendorHash ? "sha256-tp22jj6DNnYFQhtAFW2uLo10ty//dyNqIDH2egDgbOw="
 }:

 let
@@ -14,13 +14,13 @@ let
     builtins.map ({name, repo, version}: "${repo}@${version}") attrs;
 in buildGoModule rec {
   pname = "coredns";
-  version = "1.11.0";
+  version = "1.11.1";

   src = fetchFromGitHub {
     owner = "coredns";
     repo = "coredns";
     rev = "v${version}";
-    sha256 = "sha256-Mn8hOsODTlnl6PJaevMcyIKkIx/1Lk2HGA7fSSizR20=";
+    sha256 = "sha256-XZoRN907PXNKV2iMn51H/lt8yPxhPupNfJ49Pymdm9Y=";
   };

   inherit vendorHash;

I can put up a PR for this tonight.

Oh that's great, thnx!

https://github.com/NixOS/nixpkgs/pull/258136


Dead library, avoid !! - Out of date package, frustrating setup, lib is broken

My experience went something like this:

Install dependencies, copy example code and run

-ImportError: cannot import name 'sign_cryptography'

Go through recent commit history, change syntax to match older crypto lib

-ModuleNotFoundError: No module named 'M2Crypto'

Attempt to install M2Crypto

-Fails, because I need the dependencies

~$ sudo apt install python3-dev libssl-dev build-essential swig
~$ pip3 install M2Crypto

Okay, at this point I thought I could finally use the library, but it seems to be completely broken:

First, attempting to connect by providing a serial

-Traceback (most recent call last):
-  File "main.py", line 29, in <module>
-    device.connect(serial)
-  File "main.py", line 15, in connect
-    self.device.ConnectDevice(rsa_keys=self.keys, serial=deviceSerial)
-  File "/home/chris/.local/lib/python3.6/site-packages/adb/adb_commands.py", line 130, in ConnectDevice
-    elif serial and b':' in serial:
-TypeError: argument of type 'UsbHandle' is not iterable

Remove the serial argument

-Traceback (most recent call last):
-  File "main.py", line 30, in <module>
-    device.connect(serial)
-  File "main.py", line 17, in connect
-    self.device.ConnectDevice(rsa_keys=self.keys)
-  File "/home/chris/.local/lib/python3.6/site-packages/adb/adb_commands.py", line 135, in ConnectDevice
-    timeout_ms=default_timeout_ms)
-  File "/home/chris/.local/lib/python3.6/site-packages/adb/common.py", line 221, in FindAndOpen
-    dev.Open()
-  File "/home/chris/.local/lib/python3.6/site-packages/adb/common.py", line 128, in Open
-    handle.claimInterface(iface_number)
-  File "/home/chris/.local/lib/python3.6/site-packages/usb1/__init__.py", line 1309, in claimInterface
-    libusb1.libusb_claim_interface(self.__handle, interface),
-  File "/home/chris/.local/lib/python3.6/site-packages/usb1/__init__.py", line 133, in mayRaiseUSBError
-    __raiseUSBError(value)
-  File "/home/chris/.local/lib/python3.6/site-packages/usb1/__init__.py", line 125, in raiseUSBError
-    raise __STATUS_TO_EXCEPTION_DICT.get(value, __USBError)(value)
- usb1.USBErrorBusy: LIBUSB_ERROR_BUSY [-6]

Although the 2nd issue might not be a problem with the library, it should be noted that the standard adb binary provided with android has no issues at all.
How is this such a mess? How is it that the biggest tech company in the world manages to provide an abysmal developer experience without fail? I understand that Google might not be able to keep every library up to date etc, but at least post a 'this is no longer being maintained' message (which takes max 30 seconds) so I don't waste my entire afternoon
Just curious, a breaking change (with the documentation) was merged which swapped out M2Crypto for py-cryptography. M2Crypto is still updated regularly, is there any reasoning behind this?

Hey :)
This isn't an official Google repo, I'm an ex-Google eng and I legitimately forgot about this repo, sorry.
I'll try to look through PRs and merge them in. I'd be happy to accept more PRs in the coming weeks to get this back off the ground and ready for a 1.3 PyPI release.


admin operation default deadline should be 60s

From @mdietz94 on December 12, 2017 21:44
Right now the deadline defaults to 30s as declared by gRPC. We should set this to 60s so it can more quickly be retried by clients if a server is unreachable or unavailable. This also mirrors the deadlines set by Java/C#.
Copied from original issue: GoogleCloudPlatform/google-cloud-node#2772

This is not an enhancement, we will soon consider operations made with deadlines shorter than 60s as out of SLO - this is a GA blocker and would cause users of the current client library to potentially suffer outages they would not with a higher deadline.

Thanks for providing that info.

@mdietz94 currently all deadlines are configured to be 60s in our client config. This leaves me wondering if this is an issue in our code or perhaps gax isn't honoring these configurations anymore.

I see, thanks, I was trying to follow this in the code and did not realize we had overrides - I did not actually see users' deadlines that were set shorter. Thanks for pointing out these configs.

Awesome, glad to hear!


RFC: Node Event API

Rendered

@obany the code will be changed to use index.

@obany the code will be changed to use index.

There is still parent1MessageId and parent2MessageId

Unable to access the spec via the link since last week: https://playground.asyncapi.io/?load=https://raw.githubusercontent.com/luca-moser/protocol-rfcs/rfc/node-event-api/text/0033-node-event-api/0033-node-event-api.yml
Hmm. We’re having trouble finding that site.

Unable to access the spec via the link since last week: https://playground.asyncapi.io/?load=https://raw.githubusercontent.com/luca-moser/protocol-rfcs/rfc/node-event-api/text/0033-node-event-api/0033-node-event-api.yml
Hmm. We’re having trouble finding that site.

Works fine for me.

Unable to access the spec via the link since last week: https://playground.asyncapi.io/?load=https://raw.githubusercontent.com/luca-moser/protocol-rfcs/rfc/node-event-api/text/0033-node-event-api/0033-node-event-api.yml
Hmm. We’re having trouble finding that site.

Works fine for me.

turn out, it's DNS_PROBE_FINISHED_NXDOMAIN on chrome, firefox doesn't give any hint on this error.

Same for me


Dispatch reorder table event

Description
This pull request adds the functionality for a "reorder-table" event to be dispatched when reordering a table.

[x] Changes have been tested.
[x] Documentation is up-to-date.

Using events for this sort of thing doesn't really fit the rest of the Filament API. If anything, it'd be a little closure method that gets executed instead.
For this, you can just override reorderTable() on the List page / Relation Manager, call parent::reorderTable(), and then execute your logic.

Also, registering a listener on a resource definitely wouldnt work


Run poco ~/tmp/foo generates output correctly in ~/tmp/WWW but reports it was output to current directory + WWW

Fixed


How to do the visualization of result?

Hello,author.Could you tell me how to visualize the result as video or gif? I am looking forward to your reply!

Thank you for your reply! I would like to know more about how to generate this animation result, and I wonder if you have a simple solution.

To be more specific, I save the 8 corners of a bbox in a specific order and draw lines between corresponding corner pairs to show the bbox. Actually, there are no technical difficulties to do visualization.  I am not going to release the visualization code because it is messy.

Thank you for your patient answer, I will try to do it.


Is there any way to load local image using Kitematic?

Is there any way to load local image using Kitematic?

as @alankent mentioned, the My Images tab is the way to do it


Check request id in logs

Check if the request id is being displayed in every log that needs to have it.

Will be fixed from 1.2.7.


Remove unnecessery dependency on DotNetZip library

According to the IANA http encoding parameters, zlib seems to me as invalid. So, it is good to move it away which will give you one more bonus - there is no need to depend on DotNetZip anymore, so your assembly become almost self-contained.
Doneness:

[v] Build is okay - I made sure that this change is building successfully.
[v] No Bugs - I made sure that this change is working properly as expected. It does'nt have any bugs that you are aware of.
[v] Branching - If this is not a hotfix, I am making this request against develop branch

Its good that with this change we don't need a 3rd party dependency.
But are we sure that this encoding is never used?

We cannot be 100% sure. But usage of non-standard values is very specific case, and we could provide some DI technics to inject custom encoders, and move non-standard encoders to another project/solution/repositories, if it is required, or provide documentation/samples about writing custom encoders.


Could you add more detailed example of how to use getDeployPlugin() feature?

Hi, in file acqdp/tensor_network/contractor.py there is a function to import "tensor_network" submodule.
I'm wondering if this is the way you utilized GPU devices in your paper.
If that GPU library is available on the internet, could you add some document about what it is and how to use it?

In our implementation, we used JAX for GPU acceleration, which should be automatically included during setup. To utilize GPU, one can modify the corresponding configuration file (for example, khp_params.json) to

'contractor_params': {'backend': 'jax'}
This enables the runtime JAX support on GPU acceleration of tensor network contraction.

In our implementation, we used JAX for GPU acceleration, which should be automatically included during setup. To utilize GPU, one can modify the corresponding configuration file (for example, khp_params.json) to

'contractor_params': {'backend': 'jax'}
This enables the runtime JAX support on GPU acceleration of tensor network contraction.

thanks for your help!

thanks for your help!


Upgrade to opentelemetry-rust v0.26.0

Thank you for authoring this crate! This PR upgrades opentelemetry-application-insights to use opentelemetry-rust v0.26.0.
The relevant changes in the new version are:

removal of AggregationSelector
a new KeyValue API to replace Key

In addition, I also included a couple of clippy fixes in this PR related to vec![] usage.

Oh, thank you. I meant to do that but it kinda dropped of my radar. I'll have a closer look at your PR tomorrow.


Can docker set the order of start up?

@nein09
So, if I follow, these lines
https://github.com/nein09/polder-federated-search/blob/e8a8ef9c06f338dc10272d4e0b4e0224853f1ccc/docker/docker-compose.yaml#L3-L14
This will start up Gleaner with the -setup call to ensure its requested top level bucket exists.
However, if Minio is not yet started, there may be no object store to talk to yet?   Assuming it is the one you are using.
Is there a way to sequence how containers start in Docker?

ha!  I didn't even see the depends on!   Thanks.  I didn't know about that one!

oh yeah! I just found out about that today. It looks handy.
There's a tradeoff there, where you can't use extends if you have 'depends on', which is why the docker-compose file repeats itself. But the 'depends on' looked worth it.


Intel 12900k Support

Architecture:                    x86_64
CPU op-mode(s):                  32-bit, 64-bit
Byte Order:                      Little Endian
Address sizes:                   46 bits physical, 48 bits virtual
CPU(s):                          24
On-line CPU(s) list:             0-23
Thread(s) per core:              1
Core(s) per socket:              16
Socket(s):                       1
NUMA node(s):                    1
Vendor ID:                       GenuineIntel
CPU family:                      6
Model:                           151
Model name:                      12th Gen Intel(R) Core(TM) i9-12900K
Stepping:                        2
CPU MHz:                         3200.000
CPU max MHz:                     6700.0000
CPU min MHz:                     800.0000
BogoMIPS:                        6374.40
Virtualization:                  VT-x
L1d cache:                       384 KiB
L1i cache:                       256 KiB
L2 cache:                        10 MiB
NUMA node0 CPU(s):               0-23
Vulnerability Itlb multihit:     Not affected
Vulnerability L1tf:              Not affected
Vulnerability Mds:               Not affected
Vulnerability Meltdown:          Not affected
Vulnerability Spec store bypass: Mitigation; Speculative Store Bypass disabled via prctl and seccomp
Vulnerability Spectre v1:        Mitigation; usercopy/swapgs barriers and __user pointer sanitization
Vulnerability Spectre v2:        Mitigation; Enhanced IBRS, IBPB conditional, RSB filling
Vulnerability Srbds:             Not affected
Vulnerability Tsx async abort:   Not affected
Flags:                           fpu vme de pse tsc msr pae mce cx8 apic sep mtrr pge mca cmov pat pse36 clflush dts acpi mmx fxsr sse sse2 ss
                                  ht tm pbe syscall nx pdpe1gb rdtscp lm constant_tsc art arch_perfmon pebs bts rep_good nopl xtopology nonsto
                                 p_tsc cpuid aperfmperf tsc_known_freq pni pclmulqdq dtes64 monitor ds_cpl vmx smx est tm2 ssse3 sdbg fma cx16
                                  xtpr pdcm pcid sse4_1 sse4_2 x2apic movbe popcnt tsc_deadline_timer aes xsave avx f16c rdrand lahf_lm abm 3d
                                 nowprefetch cpuid_fault epb cat_l2 invpcid_single cdp_l2 ssbd ibrs ibpb stibp ibrs_enhanced tpr_shadow vnmi f
                                 lexpriority ept vpid ept_ad fsgsbase tsc_adjust bmi1 avx2 smep bmi2 erms invpcid rdt_a rdseed adx smap clflus
                                 hopt clwb intel_pt sha_ni xsaveopt xsavec xgetbv1 xsaves split_lock_detect avx_vnni dtherm ida arat pln pts h
                                 wp hwp_notify hwp_act_window hwp_epp hwp_pkg_req umip pku ospke waitpkg gfni vaes vpclmulqdq tme rdpid movdir
                                 i movdir64b fsrm md_clear serialize pconfig arch_lbr flush_l1d arch_capabilities

Could you test whether the last commit in #308 makes it work?


Deprecate LoadAndSave asset processor

Technically LoadAndSave also works. All of cart's early asset processors worked in the AssetSaver, instead of a separate transform step. We might want to stop doing that and deprecate LoadAndSave.

Originally posted by @JMS55 in https://github.com/bevyengine/bevy/pull/15058#discussion_r1745895985

I agree with this: we should have one clear way to do this, and the three-step process is much clearer and more flexible.


SMS is not receiving in Android

Hi All
I am using  unity quick start master. I have dowloaded  latest firebase unity version. I have enabled phone verification method, and
i have added SHA1, SHA256 method in firebase and also i have enabled  safety check method also.
I have dowload the  googleservices.json also. I have download the unity quick start master and run the auth file in unity..
when i add phone number and  click the Authenticate Phone number.
SMS is not receiving... No Error message displayed...
Whats wrong ???

Hi @CLOUDFIRE91,
It appears that you're facing a backend issue that's preventing you from receiving an SMS. You may report this to Firebase Support where one of our agents can analyze this issue. That being said, I'll close this for now.


Is ssh-via-cloudflared still working now? [2021-04-06]

Hello,
I am using Colab-ssh before and it is working well.
Today I am trying to use the same notebook and it shows following error:
port 22: Connection timed out
I would like to confirm if there is a problem with Colab right now?

Hello @taicaile,
Yes it should be working. If you faced any issues, please share with us a snippet of your code so we can reproduce the bug :)

Hello @taicaile,
Yes it should be working. If you faced any issues, please share with us a snippet of your code so we can reproduce the bug :)

Hello,
I figured it out. I am using a new machine and I forgot to config ~/.ssh/config.
Thanks.


Standardize the gpu ID argument

Description
In our config files, generally there is a GPU argument which specifies the device ID to use:
"gpu": 0

However, in the config file for automate_training, the GPU argument is a list:
"gpu": [0,1,2]

For consistency, I think it makes sense to change the config files to all use the list method, as this will encompass both cases.
This pull request does the following:

Refactor terms such as gpu_number and gpu to either gpu_id or gpu_ids.
gpu_id (int): the GPU ID for one device
gpu_ids (list)(int): a list of GPU IDs
Refactor config files and the ivadomed.main, which accepts config files as an argument, to use a list of GPU ids.

Linked issues
https://github.com/ivadomed/ivadomed/issues/589

Pull Request Test Coverage Report for Build 494754131

16 of 35 (45.71%)  changed or added relevant lines in 13 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.03%) to 64.474%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

ivadomed/object_detection/utils.py
1
2
50.0%

testing/unit_tests/test_adaptative.py
2
3
66.67%

testing/unit_tests/test_orientation.py
2
3
66.67%

ivadomed/main.py
0
2
0.0%

testing/unit_tests/test_HeMIS.py
1
3
33.33%

ivadomed/utils.py
0
3
0.0%

ivadomed/scripts/automate_training.py
0
4
0.0%

ivadomed/scripts/convert_to_onnx.py
0
5
0.0%

Files with Coverage Reduction
New Missed Lines
%

ivadomed/scripts/convert_to_onnx.py
1
0%

testing/unit_tests/test_HeMIS.py
1
94.78%

Totals

Change from base Build 491507272:
0.03%

Covered Lines:
4283

Relevant Lines:
6643

💛  - Coveralls

Pull Request Test Coverage Report for Build 494754131

16 of 35 (45.71%)  changed or added relevant lines in 13 files are covered.
2 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.03%) to 64.474%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

ivadomed/object_detection/utils.py
1
2
50.0%

testing/unit_tests/test_adaptative.py
2
3
66.67%

testing/unit_tests/test_orientation.py
2
3
66.67%

ivadomed/main.py
0
2
0.0%

testing/unit_tests/test_HeMIS.py
1
3
33.33%

ivadomed/utils.py
0
3
0.0%

ivadomed/scripts/automate_training.py
0
4
0.0%

ivadomed/scripts/convert_to_onnx.py
0
5
0.0%

Files with Coverage Reduction
New Missed Lines
%

ivadomed/scripts/convert_to_onnx.py
1
0%

testing/unit_tests/test_HeMIS.py
1
94.78%

Totals

Change from base Build 491507272:
0.03%

Covered Lines:
4283

Relevant Lines:
6643

💛  - Coveralls

This looks good! Thanks @ahill187 - one thing of note, #589 was intended more to point out that the stock train code doesn't support multi-GPU usage; could we explicitly point that out somewhere in the documentation, until we implement it? Maybe here on the configuration file documentation, as that's what people are most likely to read while setting up models.

Oh good call! I'll add some docs for that :)

This looks good! Thanks @ahill187 - one thing of note, #589 was intended more to point out that the stock train code doesn't support multi-GPU usage; could we explicitly point that out somewhere in the documentation, until we implement it? Maybe here on the configuration file documentation, as that's what people are most likely to read while setting up models.

Oh good call! I'll add some docs for that :)

@leandervaneekelen Was this what you had in mind? https://github.com/ivadomed/ivadomed/pull/644/commits/5c261d4b74230392a7a367199755320a2935258b

@leandervaneekelen Was this what you had in mind? https://github.com/ivadomed/ivadomed/pull/644/commits/5c261d4b74230392a7a367199755320a2935258b

Yep, nothing more than that is needed :)

Yep, nothing more than that is needed :)


Problems with Phases and SubPhases

After SubPhases rework, filtering of user input is not polished:

Some vital moments can be skipped by "Next" button (example: dice rolling in combat phase)
Sometimes activation can be called few times (exampe: "Perform move" command)

Fixed after subphases architecture rework


Sc3004

Description
https://apps.nrs.gov.bc.ca/int/jira/browse/SHOWCASE-3004

Added aria-label attributes to links/buttons that open in new tab or popup
Restructure Heading tags in template
Included alt text for images

Types of changes

Bug fix (non-breaking change which fixes an issue)

Checklist

[x] I have read the CONTRIBUTING doc
[x] I have checked that unit tests pass locally with my changes
[ ] I have added tests that prove my fix is effective or that my feature works
[ ] I have added necessary documentation (if appropriate)

Further comments

There's a whole bunch of linting warnings about aria-label and line length. I think it would be a good idea to resolve those. They show up in the "files changed" tab on this page. Otherwise it looks good.


Replace oleksandr/bonjour with grandcat/zeroconf

Replace oleksandr/bonjour with grandcat/zeroconf.
Fortunately for me, there was only a single API difference between the two versions, this being zeroconf.RegisterProxy now accepting a list of IP's. I have inlined the creation of this structure, however happy to change to whatever style is suited best to this project.
TODO:

[x] Test in the real world to determine if this solves #31

After replacing the library, the consistency of the bridge being accessible appears to be much more reliable. There are occasionally dropouts, but I think i'm going to pass the blame for this onto poor wifi reception.

Regardless of whether this resolves the issue or not, I still think this library should be used in favour of the one from oleksandr, since it is actively maintained (and is a fork):

Great thanks to hashicorp and to oleksandr and all contributing authors for the code this projects bases upon. Large parts of the code are still the same.
However, there are several reasons why I decided to create a fork of the original project: The previous project seems to be unmaintained. There are several useful pull requests waiting. I merged most of them in this project. Still, the implementation has some bugs and lacks some other features that make it quite unreliable in real LAN environments when running continously. Last but not least, the aim for this project is to build a solution that targets standard conformance in the long term with the support of the community. Though, resiliency should remain a top goal.

Highly suggest merging this, it worked well for me.

Likewise, haven't had a connection issue since I last posted

Thanks for your effort.
In the meantime, I've made a dnssd library which is used in HomeControl in the dnssd branch.


extend MonologServiceProvider

add some processors, show integration with symfony/monolog-bridge, extend config
monolog:
   processors:
       some:
           class: ...

fixed in https://github.com/kamilsk/CilexServiceProviders/issues/51


Gradle deprecation warning: Antlr plugin

Plugin version
1.4.0
Gradle version
7.4.2
Describe the bug
Running buildHealth on my project leads to the following deprecation warning in the explodeCodeSourceMain and explodeCodeSourceTest tasks:
> Task :subproj:explodeCodeSourceMain
Execution optimizations have been disabled for task ':subproj:explodeCodeSourceMain' to ensure correctness due to the following reasons:
  - Gradle detected a problem with the following location: '/home/project/subproj/build/generated-src/antlr/main'. Reason: Task ':subproj:explodeCodeSourceMain' uses this output of task ':subproj:generateGrammarSource' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.4.2/userguide/validation_problems.html#implicit_dependency for more details about this problem.
Gradle detected a problem with the following location: '/home/project/subproj/build/generated-src/antlr/main'. Reason: Task ':subproj:explodeCodeSourceMain' uses this output of task ':subproj:generateGrammarSource' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed. Please refer to https://docs.gradle.org/7.4.2/userguide/validation_problems.html#implicit_dependency for more details about this problem. This behaviour has been deprecated and is scheduled to be removed in Gradle 8.0. Execution optimizations are disabled to ensure correctness. See https://docs.gradle.org/7.4.2/userguide/more_about_tasks.html#sec:up_to_date_checks for more details.

To Reproduce
I guess the issue is because I'm using the antlr built-in Gradle plugin:
plugins {
	id 'antlr'
}

It should be simple enough to reproduce the issue by just adding the plugin to the build-script. If you have troubles reproducing, I'll try creating a repo.
Expected behavior
No deprecation warning

Thanks for the issue.

I just saw a new one (using Gradle 7.5.1):
> Task :subproj:explodeJarMain
Build service 'inMemoryCache' is being used by task ':subproj:explodeJarMain' without the corresponding declaration via 'Task#usesService'. This will fail with an error in Gradle 8.0. Declare the association between the task and the build service using 'Task#usesService'. Consult the upgrading guide for further information: https://docs.gradle.org/7.5.1/userguide/upgrading_version_7.html#undeclared_build_service_usage

I see a similar one for findInlineMembers and findDeclaredProcs.

Could you file this as a separate issue, please?

Sure, here you go. :)

A workaround for this:
// Workaround for https://github.com/gradle/gradle/issues/25885
// Technically it should be `explodeCodeSourceMain dependsOn generateGrammarSource` and
// `explodeCodeSourceTest dependsOn generateTestGrammarSource`, but this module is so
// small it isn't worth fine-tuning it.
tasks.withType(com.autonomousapps.tasks.CodeSourceExploderTask) {
  dependsOn('generateGrammarSource', 'generateTestGrammarSource')
}

I have a similar issue with https://github.com/jsonschema2dataclass/js2d-gradle plugin instead of Antlr.

Instead of the manual dependsOn, it is better to fix the broken Antlr setup, so that all tasks that consume sources are worked-around properly at once. Please find the proper work-around at https://github.com/gradle/gradle/issues/19555#issuecomment-1593252653 :-)

Hi, I think I have a similar issue with the org.jsonschema2pojo plugin:
A problem was found with the configuration of task ':myproject:sarif-parser:explodeCodeSourceMain' (type 'CodeSourceExploderTask').
  - Gradle detected a problem with the following location: '/home/julien.henry/Projects/myproject/sarif-parser/build/generated-sources/js2p'.

    Reason: Task ':myproject:sarif-parser:explodeCodeSourceMain' uses this output of task ':myproject:sarif-parser:generateJsonSchema2Pojo' without declaring an explicit or implicit dependency. This can lead to incorrect results being produced, depending on what order the tasks are executed.

    Possible solutions:
      1. Declare task ':myproject:sarif-parser:generateJsonSchema2Pojo' as an input of ':myproject:sarif-parser:explodeCodeSourceMain'.
      2. Declare an explicit dependency on ':myproject:sarif-parser:generateJsonSchema2Pojo' from ':myproject:sarif-parser:explodeCodeSourceMain' using Task#dependsOn.
      3. Declare an explicit dependency on ':myproject:sarif-parser:generateJsonSchema2Pojo' from ':myproject:sarif-parser:explodeCodeSourceMain' using Task#mustRunAfter.

    For more information, please refer to https://docs.gradle.org/8.10.2/userguide/validation_problems.html#implicit_dependency in the Gradle documentation.

I tried different workarounds, including something similar to the one suggested by @Vampire :+1:
val generateJsonSchema2Pojo by tasks.existing
sourceSets {
  main {
    java.srcDir(generateJsonSchema2Pojo.map { files() })
  }
}

but I still have the same issue when running ./gradlew buildHealth

The previous workaround from @autonomousapps worked:
tasks.withType<CodeSourceExploderTask> {
    dependsOn("generateJsonSchema2Pojo")
}

Any explicit dependsOn where the left-hand side is not a lifecycle task is a code smell and usually just a duct-tape solution masking the actual problem for some specific cases.
The .map { files() } trick I have so far seen only necessary to fix up the greatly broken setup of the built-in ANTLR plugin.
Usually if the generateJsonSchema2Pojo properly defines its output and you just do
val generateJsonSchema2Pojo by tasks.existing
sourceSets {
  main {
    java {
      srcDir(generateJsonSchema2Pojo)
    }
  }
}

Then the outputs of the task are treated as sources with all tasks consuming sources having the necessary task dependencies automatically.
If you get that error by Gradle it usually means that you registered the output path of the task manually as sources instead of declaring the task itself as source dir.

@Vampire That's not the case here. org.jsonschema2dataclass plugin output is compiled by Gradle and added to a jar without any explicit configuration. It's enough to add the plugin.

I tried:
val generateJsonSchema2Pojo by tasks.existing
sourceSets {
  main {
    java {
      srcDir(generateJsonSchema2Pojo)
    }
  }
}

jsonSchema2Pojo {
  sourceFiles = files("${sourceSets.main.get().output.resourcesDir}/sarif/sarif-schema-2.1.0.json")
  targetPackage = "org.sarif.pojo"
}

and I still get the same error.

Hm, sounds that plugin is doing really bad things then :-D


Fixing IsSensical() in hanoi example [Models->Constants]

The implementation of IsSensical() assumption given in "Models->Constants" section won't catch the problem with TSPACES <- 3, TSIZE <- 3, SOLUTION <- <<<<1,2>>, <<>>, <<3,4>>>> which is the example you are discussing in this section.
So, instead of:
IsSensical(state) == /\ Len(state) = TSPACES \* Correct spaces
                     /\ \A n \in 1..TSIZE : \* All numbers appear
                        \E tower \in DOMAIN state:
                            \E disc \in DOMAIN state[tower]:
                                n = state[tower][disc]

it's better to use the following:
  IsSensical(state) ==  /\ Len(state) = TSPACES \* Correct spaces
                        /\ \A tower \in DOMAIN state: \* Numbers do not exceed TSIZE
                            \A disc \in DOMAIN state[tower]:
                                state[tower][disc] \in 1..TSIZE
                        /\ \A n \in 1..TSIZE : \* All numbers appear
                            \E tower \in DOMAIN state:
                                \E disc \in DOMAIN state[tower]:
                                    n = state[tower][disc]

Haven't tried but ACKing the issue

Yup, you're correct, fixing the issue now

Fixed in https://github.com/hwayne/learntla/commit/31b6232925e28054d1dbd9607fd5614a112a1d65.


gatt_security_client can't connect mouse (IDFGH-11780)

Answers checklist.

[X] I have read the documentation ESP-IDF Programming Guide and the issue is not addressed there.
[X] I have updated my IDF branch (master or release) to the latest version and checked that the issue is present there.
[X] I have searched the issue tracker for a similar issue and not found a similar issue.

General issue report
When the gatt_security_client connects to a Bluetooth mouse, it will not trigger the secure pairing process, and it will automatically disconnect after about 110 seconds of connection.
the configure:
#define GATTC_TAG             "RAPOO 5.0MS"
#define REMOTE_SERVICE_UUID   ESP_GATT_UUID_HID_SVC
#define REMOTE_NOTIFY_UUID    ESP_GATT_UUID_HID_REPORT

the client log with esp32s3：
I (59427) RAPOO 5.0MS: EVT 46, gattc if 3
I (59497) RAPOO 5.0MS: EVT 18, gattc if 3
I (59497) RAPOO 5.0MS: ESP_GATTC_CFG_MTU_EVT, Status 0, MTU 23, conn_id 0
I (59497) RAPOO 5.0MS: EVT 7, gattc if 3
I (59497) RAPOO 5.0MS: SEARCH RES: conn_id = 0 is primary service 1
I (59507) RAPOO 5.0MS: start handle 25 end handle 44 current handle value 25
I (59517) RAPOO 5.0MS: UUID16: 1812
I (59517) RAPOO 5.0MS: EVT 6, gattc if 3
I (59517) RAPOO 5.0MS: Get service information from remote device
I (59527) RAPOO 5.0MS: EVT 38, gattc if 3
I (59567) RAPOO 5.0MS: EVT 9, gattc if 3
I (59567) RAPOO 5.0MS: write descr success
I (59597) RAPOO 5.0MS: EVT 4, gattc if 3
I (59597) RAPOO 5.0MS: Write char success
W (174227) BT_APPL: gattc_conn_cb: if=3 st=0 id=3 rsn=0x8
W (174227) BT_HCI: hcif disc complete: hdl 0x1, rsn 0x8
I (174227) RAPOO 5.0MS: EVT 41, gattc if 3
I (174227) RAPOO 5.0MS: ESP_GATTC_DISCONNECT_EVT, reason = 0x8
I (174237) RAPOO 5.0MS: EVT 5, gattc if 3

the client log with esp32:
I (18425) RAPOO 5.0MS: EVT 46, gattc if 3
I (18425) RAPOO 5.0MS: EVT 18, gattc if 3
I (18425) RAPOO 5.0MS: ESP_GATTC_CFG_MTU_EVT, Status 0, MTU 23, conn_id 0
I (18435) RAPOO 5.0MS: EVT 7, gattc if 3
I (18435) RAPOO 5.0MS: SEARCH RES: conn_id = 0 is primary service 1
I (18445) RAPOO 5.0MS: start handle 21 end handle 24 current handle value 21
I (18455) RAPOO 5.0MS: UUID16: 180f
I (18455) RAPOO 5.0MS: EVT 6, gattc if 3
I (18465) RAPOO 5.0MS: Get service information from remote device
I (18475) RAPOO 5.0MS: EVT 38, gattc if 3
I (18745) RAPOO 5.0MS: EVT 9, gattc if 3
I (18745) RAPOO 5.0MS: write descr success
lld_pdu_get_tx_flush_nb HCI packet count mismatch (0, 1)
I (168524) RAPOO 5.0MS: EVT 41, gattc if 3
I (168524) RAPOO 5.0MS: ESP_GATTC_DISCONNECT_EVT, reason = 0x8
I (168524) RAPOO 5.0MS: EVT 5, gattc if 3

Uploading esp32-mouse.zip…
This is the Bluetooth packet I caught.I hope it will be helpful to you.

@jjj19950710
thanks for report the issu,I will check.

The API for initiating pairing is 'esp_ble_set_encryption,' which is not actively called in the 'gatt_security_client' example. You can modify the example to initiate pairing when ESP_GATTC_CONNECT_EVT occurs.

Now the client can initiate pairing requests proactively.Thanks very much！


Support for OpenStack ConfigDrive datasource

I've started a discussion with @Itxaka on this already (thank you so much for all the insights 🙏 ) but essentially we are looking for a way to configure edge-nodes (deployed as OpenStack VMs) via the ConfigDrive capability of OpenStack. Effectively the ideal outcome would be to use the ConfigDrive just like what we do today with a 2nd ISO that can be mounted as a 2nd media. In this case, mounting a a 2nd ISO is not an option and Config Drive has to be used - this will be mostly used to setup Static IP for the nodes
Some context:

Kairos version being used is v2.1.3
The OpenStack version being used is Newton
The meta-data service is available in the fixed IP: <IP_ADDRESS>
The label of the config-drive in the booted system is config-2 or CONFIG-2, as per cloud-init OpenStack datasource documentation

The preliminary investigation that @Itxaka (🙏 ) did:
Currently there's no support for the config drive in kairos datasources unfortunately - https://github.com/rancher-sandbox/linuxkit/
The idea is generic cloud config that opens the config-drive and copies the data into /oem so the real cloud-config comes from the config-drive
 - name: "Get cloud config from config-drive"
      commands:
        - mkdir -p /tmp/cc
        - DRIVE=$(blkid -t LABEL="config-2" -odevice) mount $DRIVE /tmp/cc
        - cp /tmp/cc/openstack/latest/user-data /oem/userdata
        - umount /tmp/cc

Also, adding to this, there's no DHCP available at any point, so that should also be taken into account

Thsi needs to expand the cdrom provider upstream in linuxkit to also read the metadata from the cdrom with this label. Should be simply enough.

https://github.com/rancher-sandbox/linuxkit/pull/4

This is now supported in kairos 2.4.1 but its not added to the default metadata services


Subgraph is down

index-3f0a3c7f.js:233 ApolloError: indexing_error
    at new a (index-3f0a3c7f.js:200:184)
    at g.toQueryResult (index-3f0a3c7f.js:206:11615)
    at g.useQuery (index-3f0a3c7f.js:206:7413)
    at useLazyQuery (index-3f0a3c7f.js:206:12360)
    at useCollectiveData (index-3f0a3c7f.js:233:70)
    at HomePage (index-3f0a3c7f.js:237:9757)
    at Xh (index-3f0a3c7f.js:38:20960)
    at dj (index-3f0a3c7f.js:40:3318)
    at Wk (index-3f0a3c7f.js:40:47416)
    at Vk (index-3f0a3c7f.js:40:42128)
(anonymous) @ index-3f0a3c7f.js:233
index-3f0a3c7f.js:237 undefined
index-3f0a3c7f.js:233 ApolloError: indexing_error
    at new a (index-3f0a3c7f.js:200:184)
    at index-3f0a3c7f.js:204:99107
    at b0 (index-3f0a3c7f.js:199:10095)
    at index-3f0a3c7f.js:199:10002
    at new Promise (<anonymous>)
    at Object.then (index-3f0a3c7f.js:199:9967)
    at Object.next (index-3f0a3c7f.js:199:10109)
    at notifySubscription (index-3f0a3c7f.js:199:2415)
    at onNotify (index-3f0a3c7f.js:199:2926)
    at a.next (index-3f0a3c7f.js:199:3560)

This is blocking additional development and @Joshua-Jack is working on resolving it.

Fix did not resolve the issue. It might be worth getting the subgraph working locally to start pushing some of the features forward.

@benefacto @sirpy
is this just a local issue? is this a specific subgraph issue which should be reported to them?

@benefacto @sirpy is this just a local issue? is this a specific subgraph issue which should be reported to them?

@L03TJ3 This was an issue with the hosted subgraph currently used in the latest preview environment. I just rechecked and it looks like it's back up again, though, but I'm not aware of what change @Joshua-Jack may have made to bring it up again.

I spoke too soon. It looks like the indexing errors are now not occurring on the main page but on the subpages.
Main collective page loads:

But click on any collective and you'll note that indexing_error is still occurring. Further debugging within the subgraph is needed (this is not an Apollo side issue):

indexing errors are now not occurring on the main page
Indexing errors are back on the main page again:

Deployment steps:

prepare script
prepare:celo (includes an auth key secret that should probably be removed)
build:copyabi or yarn codegen to pull updated ABIs

Next steps:

@sirpy may publish the subgraph publicly so that the errors are accessible to more than the account who owns it
@benefacto to debug the subgraph errors as needed or otherwise proceed on other work (which a working subgraph should unblock)

This issue should now be resolved with the new, indexed subgraph. Feel free to verify at the latest preview deployment: https://good-collective-7ssf2sna9-gooddollarteam.vercel.app/

@benefacto it still reproduces for me. You can see the link above in the picture

@vldkhh The image you attached does not bear relevance to this ticket.

This image signifies different errors which may or may not be affecting the app and might warrant further investigation.
Since you can navigate to the donation page, this signifies that the subgraph is back up as expected.

What is the status of this?

@krisbitney fixed

Awesome. Is it okay to close the issue?


ValueError: unable to deduce auto rule

When using the latest bf from pip (to this date) and modifying my config file line 14:
build out/objects/lib/**_*.obj: auto lib/src/**/*.cpp

and line 23:
build out/libs/shlib(tw) | out/libs/lib(tw): auto out/objects/lib/**_*.obj

I get the following error:
$ bf
Traceback (most recent call last):
  File "/usr/local/bin/bf", line 9, in <module>
    load_entry_point('buildfox==0.1.2', 'console_scripts', 'bf')()
  File "/Library/Python/2.7/site-packages/buildfox/__init__.py", line 1775, in main
    engine.load(args.get("in"))
  File "/Library/Python/2.7/site-packages/buildfox/__init__.py", line 820, in load
    parse(self, filename)
  File "/Library/Python/2.7/site-packages/buildfox/__init__.py", line 459, in parse
    parser.parse()
  File "/Library/Python/2.7/site-packages/buildfox/__init__.py", line 73, in parse
    self.parse_line()
  File "/Library/Python/2.7/site-packages/buildfox/__init__.py", line 98, in parse_line
    self.engine.on_build(obj, assigns)
  File "/Library/Python/2.7/site-packages/buildfox/__init__.py", line 1061, in on_build
    name, vars = self.eval_auto(inputs_explicit, targets_explicit)
  File "/Library/Python/2.7/site-packages/buildfox/__init__.py", line 936, in eval_auto
    self.current_line_i,
ValueError: unable to deduce auto rule in 'build out/objects/lib/**_*.obj: auto lib/src/**/*.cpp', please check if your file extensions are supported by current toolchain (build.fox:14)

You need to use build obj(out/objects/lib/**_*): auto lib/src/**/*.cpp instead, because it's .o on OS X, and not .obj. Though I will try to improve logging there.

Or maybe we can just allow .obj on *nix, and .o on Windows, @den-mentiei ?

I think we shouldn't allow it - it will simplify the switch to other toolchains and make everything look consistent.
We just need to clarify it in the docs and have a better error messages.

Improved error message in #101


⚠ Cioos National CKAN Sitemap has degraded performance

In 57c2aa5, Cioos National CKAN Sitemap (https://catalogue.cioos.ca/sitemap/sitemap-1.xml) experienced degraded performance:

HTTP code: 200
Response time: 13953 ms

Resolved: Cioos National CKAN Sitemap performance has improved in 3aa0536 after 5 minutes.


FL-TPCA Review TPCA HL7 messages from PRIME for compliance with FLDOH HL7

Review TPCA existing HL7 messages from PRIME for compliance with FLDOH HL7
Acceptance criteria:
Identify and document any gaps between the TPCA HL7 messages vs FLDOH HL7 messages.

https://docs.google.com/document/d/1U70cNZL3Ff9-vSZVQmRYEF9jrOsloBRXcsW1jmaWB2k/edit?usp=sharing


touch on xiwi

I have a chromebook pixel 2015 and I was hoping to use the touch target.  I am trying to get it to work in the atom editor with no luck.  The Atom package to add touch support is new and may be the culprit.
I'd like to figure out whether the touch events get to the x-window.  Is there an app that is known to work with touch in a xiwi window?
What is the touch target supposed to do?  I couldn't find anything in the wiki or this forum.

Also see https://github.com/russlescai/atom-touch-events/issues/10#issuecomment-102736550

Currently, touch events aren't passed through xiwi.  The touch target is only effective with xorg, and even then, it just adds standard gestures like 1-finger scrolling.
I'll keep this open as an enhancement request to support passing through touch events with xiwi.

Thanks.
I found out from the author that he uses the native browser touchstart and touchmove events.  So these would be my personal enhancement request.


clear up dependencies

still need version info but it'll help more newbs like me lol.

https://github.com/mitevpi/revit-wpf-template/issues/1

Hi there - thanks for digging into this! I am traveling this week and next, and will have limited connectivity, but I'll review as soon as I can.

Sounds good! Your template really helped me get started. You’re the best.

Closing this for now due to inactivity.


unexpected resizing and changing possition of fbx object

Hello,
I have made simple demo scene of my project, using enable3d as extension for Phaser.
The problem is the fbx object 'ignore' a real canvas size.
When it tries to change the distance between chrome dev tools and canvas - the fbx object, after refreshing the page, changes its position as well as its scale (although the canvas has rigidly declared dimensions).
Screenshots:
https://imgur.com/a/NjhcQDV

I do not know what causes this. But I guess phaser and enable3d are out of sync in some way.
Can you please upload a simple demo scene or can you give me private access to your repo? I guess I will be able to track down the issue if I see the code.

I made the same mistake using your example, and your template:
https://github.com/Trusiak/enable3d-test
or this class, if you don't want to clone whole repo: https://addpaste.com/c70cbc1679b9c3ffc5f97139f7477398
remember, that i did not use any scaling mode of canvas element (only const dimensions).
and here again the screenshoots for you:
https://imgur.com/a/q0LuvOV
btw. you make awesome thing with this libs and Server Side Physics system.
I'm a fan of yours! :D

I see. You actually have to keep these lines,
// adjust width and height
this.third.renderer.setSize(1280, 720)
// @ts-ignore
this.third.camera.aspect = 1280 / 720
this.third.camera.updateProjectionMatrix()

when you set a fixed width and height to the Phaser.Game config.
const config: Phaser.Types.Core.GameConfig = {
  type: Phaser.WEBGL,
  backgroundColor: '#ffffff',
  scale: {
    width: 1280,
    height: 720
  },
  scene: [PreloadScene, MainScene],
  ...Canvas()
}

This way three.js and phaser.js have the same rendering size.

Thank you for your answer.
I have a few more questions because you are in the process of writing the documentation. :)

How can I give texture to the custom ground?
I know I can refer to it with scene.third.ground - but unfortunately I can't load the texture into it.

How can I enable shadows on new ground? Using this example: https://enable3d.io/examples/load-and-use-textures.html unfortunately, I'm not able to get shadows and I can't find anywhere to turn them on.

Is there / will there be a possibility to attach the 3d model with FBX extension to the dice, other models? I mean, situations where I have a 3d warrior and wants to attach a sword under his hand bone.
Three.js doesn't offer this solution with FBX (or I haven't found it).

Forgive me if I asked trivial questions - but I really looked for a good hour and found nothing. :)

Do not initialize the default ground this.third.warpSpeed('-ground') and add your own ground this.third.ground = this.third.physics.add.ground({ }, { phong: { map: TEXTURE } })

There is a small bug. But I have updated the example.

In three.js you can add child objects. If you have a arm or hand mesh/bone, you can simply do hand.add(weapon). Take a look at the updated fbx-loader-and-animations example.

Ok, but the next problem is, when i try to load another FBX object as child of player, the object (weapon) spawn in cooridates 0,0,0.  This problem doesn't exist on "add.box" method (everything is fine like in your example).
Should I give some position to the attached object so that it can appear in the bone or something?
My code:
//this piece of code were from the player class

this.traverse(child => {
                if (child.name === 'Bip01_Spine') {
                  child.add(new Weapon(scene))
                }
              })

//this is a weapon class

export class Weapon extends ExtendedObject3D {
    constructor(scene){
        super()
         scene.third.load.fbx('/assets/sword_anim.fbx', object => {
            this.add(object)
            this.traverse(child => {
                if (child.isMesh) child.castShadow = child.receiveShadow = true
              })
             this.scale.set(0.005, 0.005, 0.005)
             scene.third.add.existing(this);
        })
    }
}

PS.
you should also make the paypall available as a form of grant for you :P

I do not know. Sometimes it can get tricky.
Yes, try to add position and rotation. Maybe you have to multiply the coordinates with your scale?
// get position and rotation
this.traverse(child => {
  if (child.name === 'Bip01_Spine') {
    const { position, rotation } = child
    child.add(new Weapon(scene, position, rotation))
  }
})

You could also always ask in the three.js forum, since this is a very three.js specific question.

I do already have patreon :)


Fix broken wikipedia link

Link to Swing on the bottom was broken

[ x] I have read freeCodeCamp's contribution guidelines.
[ x] My pull request has a descriptive title (not a vague title like Update index.md)
[ x] My pull request targets the master branch of freeCodeCamp.
[ x] None of my changes are plagiarized from another source without proper attribution.
[ x] My article does not contain shortened URLs or affiliate links.

If your pull request closes a GitHub issue, replace the XXXXX below with the issue number.
Closes #XXXXX

Looks good. Congrats on your first contribution @ChristianWilkie 🔥.


Remove nonexistent actions from database when upgrading/downgrading a pack

SUMMARY
Actions are not removed when upgrading/downgrading packs.
ISSUE TYPE

Bug Report

STACKSTORM VERSION
Paste the output of st2 --version:
st2 3.0dev (7524cc8), on Python 2.7.12
(on st2cicd037)
OS / ENVIRONMENT / INSTALL METHOD

Ubuntu 16.04.5 LTS
Installed via st2cicd.build-controller
STEPS TO REPRODUCE

Install most recent version of AWS pack.
Note all of the actions, specifically the aws.ec2_describe_instances action exists and is runnable from the Actions tab in the web UI and from a workflow task.
Install AWS pack from the v0.10.0 or v0.10.1 tags using st2 pack install ... WITHOUT running st2 pack remove aws.
Note all of the actions, specifically the aws.ec2_describe_instances action still exists, and is even runnable from the Actions tab in the web UI.
Create a workflow that calls aws.ec2_describe_instances from a task. Note the incomprehensible error.

Action metadata:
---
name: remote_windows
runner_type: orquesta
description: ...
enabled: true
entry_point: workflows/remote_windows.yaml
parameters:
  instance_id:
    type: string
    description: EC2 instance ID

Workflow:
---
version: '1.0'
description: Remote into a Windows EC2 instance
input:
  - instance_id
tasks:
  get_instance:
    action: aws.ec2_describe_instances
    input:
      InstanceIds: <% ctx().instance_id %>

EXPECTED RESULTS

A better error message is desirable, but it is probably easier to simply remove all actions that exist in the database but not in an action metadata file when running st2 pack install ....
ACTUAL RESULTS

An incomprehensible error:
{
  "output": null,
  "errors": [
    {
      "message": "SyntaxError: unexpected EOF while parsing (<unknown>, line 0)",
      "type": "error",
      "task_id": "get_instance"
    }
  ]
}

I had this same error when a workflow parameter was incorrectly defined as array type when it should have been string.  This leads to St2 processing the string as an object literal.  The Python exception is logged:
  File "/opt/stackstorm/st2/lib/python3.6/site-packages/st2common/services/workflows.py", line 680, in request_task_execution
    raise e
  File "/opt/stackstorm/st2/lib/python3.6/site-packages/st2common/services/workflows.py", line 663, in request_task_execution
    wf_ex_db, task_ex_db, st2_ctx, ac_ex_req, delay=ac_ex_delay
  File "/opt/stackstorm/st2/lib/python3.6/site-packages/retrying.py", line 49, in wrapped_f
    return Retrying(*dargs, **dkw).call(f, *args, **kw)
  File "/opt/stackstorm/st2/lib/python3.6/site-packages/retrying.py", line 206, in call
    return attempt.get(self._wrap_exception)
  File "/opt/stackstorm/st2/lib/python3.6/site-packages/retrying.py", line 247, in get
    six.reraise(self.value[0], self.value[1], self.value[2])
  File "/opt/stackstorm/st2/lib/python3.6/site-packages/six.py", line 696, in reraise
    raise value
  File "/opt/stackstorm/st2/lib/python3.6/site-packages/retrying.py", line 200, in call
    attempt = Attempt(fn(*args, **kwargs), attempt_number, False)
  File "/opt/stackstorm/st2/lib/python3.6/site-packages/retrying.py", line 49, in wrapped_f
    return Retrying(*dargs, **dkw).call(f, *args, **kw)
  File "/opt/stackstorm/st2/lib/python3.6/site-packages/retrying.py", line 206, in call
    return attempt.get(self._wrap_exception)
  File "/opt/stackstorm/st2/lib/python3.6/site-packages/retrying.py", line 247, in get
    six.reraise(self.value[0], self.value[1], self.value[2])
  File "/opt/stackstorm/st2/lib/python3.6/site-packages/six.py", line 696, in reraise
    raise value
  File "/opt/stackstorm/st2/lib/python3.6/site-packages/retrying.py", line 200, in call
    attempt = Attempt(fn(*args, **kwargs), attempt_number, False)
  File "/opt/stackstorm/st2/lib/python3.6/site-packages/st2common/services/workflows.py", line 767, in request_action_execution
    ac_ex_ctx,
  File "/opt/stackstorm/st2/lib/python3.6/site-packages/st2common/util/param.py", line 343, in render_live_params
    params, context, [action_parameters, runner_parameters]
  File "/opt/stackstorm/st2/lib/python3.6/site-packages/st2common/util/param.py", line 266, in _cast_params_from
    result[name] = _cast(context[name], param_schema)
  File "/opt/stackstorm/st2/lib/python3.6/site-packages/st2common/util/param.py", line 87, in _cast
    return cast(v)
  File "/opt/stackstorm/st2/lib/python3.6/site-packages/st2common/util/casts.py", line 40, in _cast_object
    return ast.literal_eval(x)
  File "/usr/lib/python3.6/ast.py", line 48, in literal_eval
    node_or_string = parse(node_or_string, mode='eval')
  File "/usr/lib/python3.6/ast.py", line 35, in parse
    return compile(source, filename, mode, PyCF_ONLY_AST)
  File "<unknown>", line 1
    host.example.com.
                    ^
SyntaxError: unexpected EOF while parsing

However the workflow execution produces the below output which is misleading/unhelpful to diagnose the cause of the error because it doesn't indicate the parameter name or value as the source of the error:
result:
  errors:
  - message: Execution failed. See result for details.
    result:
      errors:
      - message: 'SyntaxError: unexpected EOF while parsing (<unknown>, line 1)'
        route: 1
        task_id: process_records
        type: error
      output: null
    task_id: process_zones
    type: error


Error gpg: no valid OpenPGP data found is faced when we try to gpg --verify operator-sdk-0.8.2-x86_64-apple-darwin.asc

Bug Report
Usage/Bug/Doc
What did you do?
Follow the steps in : https://github.com/operator-framework/operator-sdk/blob/master/doc/user/install-operator-sdk.md#install-from-github-release to install the version 0.8.2 in a mac.
What did you expect to see?
The installation is finished with success.
What did you see instead? Under which circumstances?
Error gpg: no valid OpenPGP data found is faced when we try to gpg --verify operator-sdk-0.8.2-x86_64-apple-darwin.asc
$ curl -OJL https://github.com/operator-framework/operator-sdk/releases/download/0.8.2/operator-sdk-0.8.2-x86_64-apple-darwin
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100     9    0     9    0     0     18      0 --:--:-- --:--:-- --:--:--    18
$ curl -OJL https://github.com/operator-framework/operator-sdk/releases/download/0.8.2/operator-sdk-0.8.2-x86_64-apple-darwin.asc
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100     9    0     9    0     0     23      0 --:--:-- --:--:-- --:--:--    23
$ gpg --verify operator-sdk-0.8.2-x86_64-apple-darwin.asc
gpg: no valid OpenPGP data found.
gpg: the signature could not be verified.
Please remember that the signature file (.sig or .asc)
should be the first file given on the command line.
$ chmod +x operator-sdk-0.8.2-x86_64-apple-darwin && sudo mkdir -p /usr/local/bin/ && sudo cp operator-sdk-0.8.2-x86_64-apple-darwin /usr/local/bin/operator-sdk && rm operator-sdk-0.8.2-x86_64-apple-darwin
camilamacedo@Camilas-MacBook-Pro /usr/local/bin $ operator-sdk
/usr/local/bin/operator-sdk: line 1: Not: command not found

Important:
The same issue is faced with other versions.
camilamacedo@Camilas-MacBook-Pro /usr/local/bin $ curl -OJL https://github.com/operator-framework/operator-sdk/releases/download/0.8.2/operator-sdk-0.8.1-x86_64-apple-darwin
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100     9    0     9    0     0     20      0 --:--:-- --:--:-- --:--:--    20
camilamacedo@Camilas-MacBook-Pro /usr/local/bin $ curl -OJL https://github.com/operator-framework/operator-sdk/releases/download/0.8.2/operator-sdk-0.8.1-x86_64-apple-darwin.asc
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100     9    0     9    0     0     23      0 --:--:-- --:--:-- --:--:--    23
camilamacedo@Camilas-MacBook-Pro /usr/local/bin $ gpg --verify operator-sdk-0.8.1-x86_64-apple-darwin.asc
gpg: no valid OpenPGP data found.
gpg: the signature could not be verified.
Please remember that the signature file (.sig or .asc)
should be the first file given on the command line.
camilamacedo@Camilas-MacBook-Pro /usr/local/bin $

It was missing the v of the version. Closing it.


README example code are buggy

Hi! Today i seen next bug.
When i call draw function in next code:
var data = [
    ["Plants",     5000],
    ["Flowers",    2500],
    ["Perennials", 200],
    ["Roses",      50]
];

var chart = new D3Funnel("#funnel");
chart.draw(data);

I have next js error:

Uncaught TypeError: undefined is not a function d3-funnel.js?body=1:308
D3Funnel._makePaths d3-funnel.js?body=1:308
D3Funnel.draw d3-funnel.js?body=1:95

Error occurs in this line:
count = this.data[i][1].replace(/\,/g, "")

Then i use string instead int type it works.
i.e.
var data = [
    ["Plants",     "5000"],
    ["Flowers",    "2500"],
    ["Perennials", "200"],
    ["Roses",      "50"]
];

Versions:

jquery - 1.11.1
d3 - 3.5.2

That's embarrassing.
I honestly don't know why I was trying to parse the counts to begin with. I made it to where numeric values are now required and that the numbers are formatted to the browser's locale when the funnel is rendered.


TRT-1118: Remove DisableStrictZoneCheck from AWS CCM config

This option was removed from the CCM and now causes the CCM to crash loop when specified.
Since we were disabling the check anyway, the removal of the check has no effect on the outcome for HyperShift.

/test e2e-aws

/approve

For ref https://github.com/kubernetes/cloud-provider-aws/pull/573

/lgtm


added doc to RegExp.firstMatch for getting first match from offset

Added documentation of how to combine get first RegExp match starting from an offset.
As discussed here:
https://github.com/dart-lang/sdk/issues/26815

[x] I’ve reviewed the contributor guide and applied the relevant portions to this PR.

Contribution guidelines:

See our contributor guide for general expectations for PRs.
Larger or significant changes should be discussed in an issue before creating a PR.
Contributions to our repos should follow the Dart style guide and use dart format.

Note that this repository uses Gerrit for code reviews. Your pull request will be automatically converted into a Gerrit CL and a link to the CL written into this PR. The review will happen on Gerrit but you can also push additional commits to this PR to update the code review.

@jonpittock please take a look at https://github.com/dart-lang/sdk/pull/55609#issuecomment-2088377783 if you would like us to land this PR. Thanks.

Closing as inactionable as CLA wasn't signed


Incorrect definition of Conflicting Meeting Hours

Current definition: Number of meeting hours where the person had overlapping meetings in their calendar. The count includes the entire duration of all overlapping meetings, not just the amount of time that overlaps. (This number includes all accepted meeting times.).
I believe the "all accepted meeting times" should be changed to "all non-declined meeting times" unless the definition has changed recently.

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

ID: e59345bb-9abb-9e5d-8613-01c0226dfc2e
Version Independent ID: 493ac915-2a6a-a271-825a-43f40d1863e8
Content: Workplace Analytics metric definitions - Workplace Analytics Office 365
Content Source: WorkplaceAnalytics/Use/Metric-definitions.md
Product: wpa
GitHub Login: @paul9955
Microsoft Alias: v-pascha

You're correct. The number of conflicting meeting hours does include all "non-declined" meetings. I’ve updated this topic accordingly. Thank you so much for your feedback!


Add license badge in README

Display license as auto-updating badge instead of hardcoded value in README

Pull Request Test Coverage Report for Build 2752

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

Totals

Change from base Build 2747:
0.0%

Covered Lines:
1037

Relevant Lines:
1130

💛  - Coveralls


rdebug doesn't stay attached

On an M1 mac I am running a rails application within docker:
fdns@e4272744ebc9:~/src$ RUBY_DEBUG_OPEN=true RUBY_DEBUG_PORT=9092 rails s -b <IP_ADDRESS>
DEBUGGER: Debugger can attach via TCP/IP (<IP_ADDRESS>:9092)
=> Booting Puma
=> Rails <IP_ADDRESS> application starting in development
=> Run `bin/rails server --help` for more startup options
Puma starting in single mode...
* Puma version: 5.6.5 (ruby 3.1.2-p20) ("Birdie's Version")
*  Min threads: 5
*  Max threads: 5
*  Environment: development
*          PID: 21
* Listening on http://<IP_ADDRESS>:3000
Use Ctrl-C to stop

Using the following launch:
        {
            "type": "rdbg",
            "name": "Attach with rdbg",
            "request": "attach",
           // "rdbgPath": "docker exec fdns /usr/local/bundle/bin/rdbg",
            "debugPort": "localhost:9092",
            //"debugPort": "localhost:1000",
            "localfsMap": "/srv/fdns/src:${workspaceFolder}",
            "useTerminal": true,
            "showProtocolLog": true
          }

The IDE seems to attach but within five seconds it just terminates.  No errors.  If I use the incorrect port I get a warning telling me, so I believe it is connecting.
I have no idea where those protocol logs are being written so I haven't seen them.

If you go to the Output panel and choose rdgb from the dropdown, it may give some additional information.

output panel is empty :-(

This seems to be the magic incantation for making the debug port listen to requests outside of docker:
RUBY_DEBUG_OPEN=true RUBY_DEBUG_PORT=9092 RUBY_DEBUG_HOST=<IP_ADDRESS> rails s -b <IP_ADDRESS>

Note RUBY_DEBUG_HOST


WIP: Implement Metro Window Control

Implements control very similar to Mahapps Metro Window.
very basic at moment, so WIP for now.

aiming for a design very close to this...

@danwalmsley haha, nice 👍

Hey @danwalmsley I'm going to close this out for now, please re-open a new PR if/when you complete this!

Do we have something like this already available?

@nitanmarcel that style of window is not available out of box, but it isn't too hard to implement similar.
Check sample repository, which has fluent window with acrylic background:
https://github.com/AvaloniaUI/XamlControlsGallery

@nitanmarcel that style of window is not available out of box, but it isn't too hard to implement similar.
Check sample repository, which has fluent window with acrylic background:
https://github.com/AvaloniaUI/XamlControlsGallery

Thanks. But 5 minutes ago I've found about Avalonia.Shell which does exactly what I'm looking for.


TypeScript Sources changes not registering in dev server

Discussed in https://github.com/patternfly/patternfly-elements/discussions/2061

Originally posted by codyburleson July 20, 2022
I created a new element, but I can't seem to get my changes to be watched. As described in the Develop/Setup page, under the section, Development Workflow, I run the command, npm start. Once started, I navigate to my new element's demo page at: http://localhost:8000/demo/pfe-wizard/. It renders as expected. If I change the file demo/pfe-wizard.html, the change registers with the listener and then change is rendered in my web browser. If I change the component code in elements/pfe-wizard/pfe-wizard.ts, however, the change is not registered. All I can do to see the change is stop the dev server and restart it. Does anyone have an idea why I'm unable to work on my actual component code in the watch mode? What am I missing?
Note that it's the same story if I use npm run dev instead of npm run start. I'm working directly in a fork of the patternfly-elements repo.

@codyburelson I've identified the problem. pfe-tools' dev server configuration adds typescript files to web-dev-server's watchfiles config by default. As it happens, if the files are so watched, they wds somehow caches their content forever (at least, until you restart the server). I might look into the root causes in wds, but for now the fix will be to simply remove the ts extension from that list in the default config.

In the mean time, you can override this in your web-dev-server.config.js
watchFiles: '{elements,core}/**/*.{css,scss,html}',