Misleading Quantity units with pi

Is your feature request related to a problem? Please describe.
Inputing a number in radian values needs the unit specifier "Hz"
But inputing a unit in Hz values needs the unit specifier "Hz 2pi"
This is rather counter intuitive and should be changed.
However if you currently use the unit Hz 2pi the input value will be multiplied by 2pi converting from Hz to rad. But it would be more intuitive the other way around to insert a value in Hz with the unit Hz and then transform this value to a radian value, if necessary, e.g. creating the Hamiltonian.
Describe the solution you'd like
Do not transform input value of quantity if 2pi is in the quantity name.
Objects which need a value in radians (e.g. creation of the hamiltonian) should be able to request a value that is in radians and includes a scaling factor dependend on the given unit
Describe alternatives you've considered
Transform an initalized Hz unit to a Hz 2Pi while changing the unit specifier, as well as the value.
Additional context

An additional problem with the current implementation is that a modification by get_value and set_value is not straightvorward:
v = Qty(3, unit="Hz 2pi") v.set_value(v.get_value())
leads to an out of bounds error

An additional problem with the current implementation is that a modification by get_value and set_value is not straightvorward:
v = Qty(3, unit="Hz 2pi") v.set_value(v.get_value())
leads to an out of bounds error

Maybe "Hz" and "rad/s" ?
Cumbersome, but clear.
On Thu, 28 Jan 2021, 18:37 Niklas Glaser<EMAIL_ADDRESS>wrote:

An additional problem with the current implementation is that a
modification by get_value and set_value is not straightvorward:
v = Qty(3, unit="Hz 2pi") v.set_value(v.get_value())
leads to an out of bounds error
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/q-optimize/c3/issues/26#issuecomment-769211454, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH3Q4K3KXUJQ7IDCDFJLY3S4GHD3ANCNFSM4WXLG4QQ
.

Maybe "Hz" and "rad/s" ?
Cumbersome, but clear.
On Thu, 28 Jan 2021, 18:37 Niklas Glaser<EMAIL_ADDRESS>wrote:

An additional problem with the current implementation is that a
modification by get_value and set_value is not straightvorward:
v = Qty(3, unit="Hz 2pi") v.set_value(v.get_value())
leads to an out of bounds error
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/q-optimize/c3/issues/26#issuecomment-769211454, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAH3Q4K3KXUJQ7IDCDFJLY3S4GHD3ANCNFSM4WXLG4QQ
.

The main point is what should be the unit that invokes the following transformation:
https://github.com/q-optimize/c3/blob/ef9533008dccbcb23810e1e7396f85b5f200da15/c3/c3objs.py#L74-L79

The main point is what should be the unit that invokes the following transformation:
https://github.com/q-optimize/c3/blob/ef9533008dccbcb23810e1e7396f85b5f200da15/c3/c3objs.py#L74-L79


All null JSON fields get masked

If some field is null, it gets replaced by XXX by default. I couldn't find any way to change it other than copy-pasting and tweaking JsonBodyFilters.
public static void main(String[] args) {
    val result = BodyFilters.defaultValue().filter(MediaType.APPLICATION_JSON_UTF8_VALUE, "{\n" +
            "  \"myRandomField\": null\n" +
            "}");
    System.out.println(result);
}

Prints this:
{"myRandomField":"XXX"}

This looks intentional.
I can "fix" it by removing the last concatenation here (org.zalando.logbook.json.JsonBodyFilters#replacePrimitiveJsonProperty):
final Pattern pattern = compile("(" + property + "\\s*:\\s*)" + value + "|null");
final Pattern pattern = compile("(" + property + "\\s*:\\s*)" + value);

For that "fix" I had to copy-paste JsonBodyFilters and JsonMediaType

Thanks for the issue! That's indeed an undesired effect. I prepared a fix in #654.
My guess why we haven't noticed this earlier is primarily https://opensource.zalando.com/restful-api-guidelines/#123 which advocates to not include properties with null values at all in any JSON document.


shiori: 1.5.3 -> 1.5.4

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/go-shiori/shiori/releases.
meta.description for shiori is: Simple bookmark manager built with Go
meta.homepage for shiori is: https://github.com/go-shiori/shiori
Updates performed

Golang update

To inspect upstream changes

Release on GitHub

Compare changes on GitHub

Impact

Checks done (click to expand)

built on NixOS
The tests defined in passthru.tests, if any, passed
found 1.5.4 with grep in /nix/store/qqkn11pjkx8c7nn9w46v2m5pw6n3bv9n-shiori-1.5.4
found 1.5.4 in filename of file in /nix/store/qqkn11pjkx8c7nn9w46v2m5pw6n3bv9n-shiori-1.5.4

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
shiori

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qqkn11pjkx8c7nn9w46v2m5pw6n3bv9n-shiori-1.5.4 \
  --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 shiori https://github.com/r-ryantm/nixpkgs/archive/73b810b140a31c3014002b806b6da9e877ec674e.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/qqkn11pjkx8c7nn9w46v2m5pw6n3bv9n-shiori-1.5.4
ls -la /nix/store/qqkn11pjkx8c7nn9w46v2m5pw6n3bv9n-shiori-1.5.4/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

1 package built:

shiori

Maintainer pings
cc @minijackson for testing.

Result of nixpkgs-review pr 213332 run on aarch64-darwin 1

1 package built:

shiori

Backporting to fix migration story, that was introduced in 1.5.3 without support in our module, and then reverted in 1.5.4.
via @fleaz


neo4j: 4.4.11 -> 5.16.0

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/neo4j/versions.
meta.description for neo4j is: A highly scalable, robust (fully ACID) native graph database
meta.homepage for neo4j is: https://neo4j.com/
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 5.15.0 with grep in /nix/store/1556i2isx85y28g2y5kscwlmg94ccmj2-neo4j-5.15.0
found 5.15.0 in filename of file in /nix/store/1556i2isx85y28g2y5kscwlmg94ccmj2-neo4j-5.15.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
neo4j

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/1556i2isx85y28g2y5kscwlmg94ccmj2-neo4j-5.15.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 neo4j https://github.com/r-ryantm/nixpkgs/archive/83b384b36c28bf480e836225a34403495c25dc2a.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/83b384b36c28bf480e836225a34403495c25dc2a#neo4j

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/1556i2isx85y28g2y5kscwlmg94ccmj2-neo4j-5.15.0
ls -la /nix/store/1556i2isx85y28g2y5kscwlmg94ccmj2-neo4j-5.15.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

1 package built:

neo4j

Maintainer pings
cc @jonringer @offlinehacker for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/project/neo4j/versions.
meta.description for neo4j is: A highly scalable, robust (fully ACID) native graph database
meta.homepage for neo4j is: https://neo4j.com/
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
Warning: a test defined in passthru.tests did not pass
found 5.16.0 with grep in /nix/store/z39aav1ci89la8qg6f45y7nk2d0l1yc6-neo4j-5.16.0
found 5.16.0 in filename of file in /nix/store/z39aav1ci89la8qg6f45y7nk2d0l1yc6-neo4j-5.16.0

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

1 total rebuild path(s)

1 package rebuild(s)

First fifty rebuilds by attrpath
neo4j

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/z39aav1ci89la8qg6f45y7nk2d0l1yc6-neo4j-5.16.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 neo4j https://github.com/r-ryantm/nixpkgs/archive/d766b098ed40539c4adbe8fcf515d47a0a4b22ff.tar.gz

Or:
nix build github:r-ryantm/nixpkgs/d766b098ed40539c4adbe8fcf515d47a0a4b22ff#neo4j

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/z39aav1ci89la8qg6f45y7nk2d0l1yc6-neo4j-5.16.0
ls -la /nix/store/z39aav1ci89la8qg6f45y7nk2d0l1yc6-neo4j-5.16.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

1 package built:

neo4j

Maintainer pings
cc @jonringer @offlinehacker for testing.

@ofborg build neo4j neo4j.passthru.tests


Unable to control absolute state path

When using S3 as my state backend, the location in the S3 bucket is prepended with env:/<Kubernetes Workspace Name>/<Desired State Path>
I'm unable to find any information on this - the cached local tfstate indicates the key I want, but scanning Dynamo shows the prepended paths.
Is there any information around this feature?
Using v0.14.1

That is the default prefix as defined in the terraform s3 backend code:
https://github.com/hashicorp/terraform/blob/main/internal/backend/remote-state/s3/backend_state.go#L29
and can be overridden in the backend configuration:
https://developer.hashicorp.com/terraform/language/settings/backends/s3#workspace_key_prefix
Also:
https://stackoverflow.com/questions/61875412/can-i-configure-terraform-to-not-use-env-in-the-path-for-a-workspaces-state


test: Use Go 1.17 to build e2e-tests

To unblock https://github.com/redhat-appstudio/e2e-tests/pull/63 and https://github.com/redhat-appstudio/e2e-tests/pull/65 which both depend on Go 1.17

/retest


(gitlab-ci) add release jobs for goreleaser and docs gen

note: for docs to work on gitlab themselves we will need to get a jeckyll/markdown renderer rigged up, but this much will keep the files up to date

merging this as it mostly fixes the goreleaser file. the docs commit will be wrong when I run the release, but I'm not gonna worry about that.

merging this as it mostly fixes the goreleaser file. the docs commit will be wrong when I run the release, but I'm not gonna worry about that.


Cannot get tenant subscription list if tenant has an expired subsctiption.

Steps to reproduce
Run 'Get-PartnerCustomerSubscription' against a tenant with an expired subscription
Expected behavior
List of subscriptions on the tenant is returned
Actual behavior
Get-PartnerCustomerSubscription : Requested value 'Expired' was not found.
At line:1 char:2

Get-PartnerCustomerSubscription -CustomerId ________---____- ...

 + CategoryInfo          : CloseError: (:) [Get-PartnerCustomerSubscription], ArgumentException
 + FullyQualifiedErrorId : Microsoft.Store.PartnerCenter.PowerShell.Commands.GetPartnerCustomerSubscription

Diagnostic logs
Running with -debug shows data being returned from Microsoft as expected.
Logs not included as it is a live customer tenant.
Environment
PSVersion                      5.1.18362.1801
PSEdition                      Desktop
ModuleType Version    Name

Script     3.0.10     PartnerCenter

On a similar note, the BillingCycle 'Triennial' isn't supported by the powershell module so anything that involves getting details of a product that supports that billing type will fail.

Having the same issue. The Expired subscription is showing in the Debug output, but the module does not know how to handle the expired status it seems.
I will try your workaround David.

Any chance this is going to get fixed soon?

I sure hope so - I have this issue as well

Any chance this is going to get fixed soon?

I sure hope so - I have this issue as well

Also encountered this. David's workaround works well though. Thanks.
If anyone needs a token for unattended access:
$token = (New-PartnerAccessToken `
  -ApplicationId $pcClientId `
  -Credential $pcCreds `
  -Scopes "https://graph.windows.net/.default" `
  -ServicePrincipal `
  -Tenant $pcTenantId).AccessToken
[securestring]$ssToken = ConvertTo-SecureString $token -AsPlainText -Force

I can't believe this is still an open issue almost two years on. We are also seeing this same issue if any subscriptions are in the "Disabled" state, or if the BillingCycle is "Triennial". This is causnig us to not be able to do a full subscription export via PowerShell.

@ngailloux-softlanding Last release was 3 and a half years ago, I think it's pretty clear that this module has been abandoned now. Unfortuantely Microsoft's documentation still directs people to it in quite a few places.
I've ended up building a module with all the functionality we need myself, once you've set up the necessary stuff for authentication the majority of the calls are very straightforward to implement.

As @DavidMoore-intY said, the PartnerCenter module is abandoned. It would be best to switch to using the APIs and modernizing your scripts. You will find more fields available to you and also not encounter the broken functionality described here and elsewhere. The New-PartnerAccessToken cmdlet was the last one I held onto from the old module but now have a replacement for that using APIs.
This is unfair of me to say: I would share with you what I have created but for now I'm too buried with projects to spend time cleaning up my code so I'm comfortable sharing it. Over a year ago I started with getting authentication working, then I've built my own module of customer functions to replace the old module. As necessary I add a new function and keep moving on. As @DavidMoore-intY  said, most are straightforward to implement.


Did you do any progress with pairing

Hi,
Very interesting project!. Thanks for sharing. I'm going to add TBS rf proto support to my hobby cheap QLRS project, based on asr 6601 device..
https://qczek.beyondrc.com/qczek-lrs-433mhz-1w-lora-rc-link/qczek-lrs-32-for-asr-6601-modules/
I wonder if you know abut the TBS protocol anything more then presented on your blog.
Thank you in advance
Krzysiek

Hi Krzysiek,
I did not check further if I can replay or decode some information needed for pairing.
Great project, very interesting. Thanks for sharing :)
Regards,
g3gg0


user16217248: Blacklist sajidali59848

user16217248 requests the blacklist of the username sajidali59848. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

Rejected by Jeff Schaller in Charcoal HQ. Reason: 'at 8 tp, 2 fp, 3 naa == ~62% TP, this isn't a candidate for blacklisting; will add a watch for the username'


Safe region

Codecov Report

Merging #12 (b15f1e5) into master (c2cf7a5) will increase coverage by 0.10%.
The diff coverage is 72.91%.

@@            Coverage Diff             @@
##           master      #12      +/-   ##
==========================================
+ Coverage   68.32%   68.43%   +0.10%
==========================================
  Files          12       12
  Lines         963      960       -3
==========================================
- Hits          658      657       -1
+ Misses        305      303       -2

Impacted Files
Coverage Δ

src/time_domain.rs
71.42% <70.00%> (+0.46%)
:arrow_up:

src/day_selector.rs
74.10% <75.00%> (+0.45%)
:arrow_up:

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 c2cf7a5...b15f1e5. Read the comment docs.


eliminate need to shift-refresh javascript upon new release

@joefutrelle The two options we have are:

Always include a ? at the end of the include for the js file. However, this will prevent ANY caching of the file, not just per release
Same as above, but use a version number instead of a timestamp. E.g., abc.js?v=2.1

#1 has the benefit of not being "forgotten" in a new release. #2 is less thrashing, since it will still allow the browser to cache, but we have to update the version number, on each "release". Right now, I don't believe we actually have true releases, and its just when a new version is deployed to the server, correct? If that's the case, maybe we should work on formalizing the release process first, and then tackle this one right after (which would then be super quick to change)

Option 1 for now. Will we need to do this for dependencies as well or just our JS? I think the former.

Updated Files
https://github.com/WHOIGit/photic/pull/223


Deployment issues on Azure

Continuous deployment  is failing on Azure. .NET core version should be upgraded.

Related
http://stackoverflow.com/questions/37296198/deploy-to-azure-from-github-error


Program received signal SIGSEGV: Segmentation fault - invalid memory reference.

Version pyCATHYv0.0.1 with CATHY 1.0
The simulation runs until TIME:   1.8026E+04, then stops with an "invalid memory reference.".  I checked the cathyH file but i don't see apparent inconsistency with the simulation inputs.
Note that time 1.8026E+04, is the first value in the atmbc file with a negative net Precipitation/ET (i.e. -2.212e-08).  Changing the value to 0 makes the simulation run until next time...
Attached (https://we.tl/t-sLFlTAlHI2) are the files to reproduce.

In the file soil, the parameter VGNCELL cannot be negative!
Also, in the file parm, you indicate a number of NUMVP nodes = 1 but then the corresponding node NODVP is 0. You should indicate a node number NODVP <= NNOD.


Cluster : Version 0.5.0 failed to collect cluster info on old kafka versions

Describe the bug (Actual behavior)
We have a 2.0.0 kafka cluster (i know, old), using version 0.4.0 works correctly but when i upgraded to 0.5.0 i saw the following error message
java.lang.IllegalStateException: Error while creating AdminClient for Cluster stg
	at com.provectus.kafka.ui.service.AdminClientServiceImpl.lambda$createAdminClient$3(AdminClientServiceImpl.java:45)
	at reactor.core.publisher.Mono.lambda$onErrorMap$31(Mono.java:3776)
	at reactor.core.publisher.FluxOnErrorResume$ResumeSubscriber.onError(FluxOnErrorResume.java:94)
	at reactor.core.publisher.FluxHide$SuppressFuseableSubscriber.onError(FluxHide.java:142)
	at reactor.core.publisher.FluxMap$MapSubscriber.onError(FluxMap.java:134)
	at reactor.core.publisher.Operators$MultiSubscriptionSubscriber.onError(Operators.java:2063)
	at reactor.core.publisher.MonoFlatMap$FlatMapMain.onError(MonoFlatMap.java:172)
	at reactor.core.publisher.MonoFlatMap$FlatMapMain.onError(MonoFlatMap.java:172)
	at reactor.core.publisher.MonoFlatMap$FlatMapMain.onError(MonoFlatMap.java:172)
	at reactor.core.publisher.MonoIgnoreThen$ThenIgnoreMain.onError(MonoIgnoreThen.java:278)
	at reactor.core.publisher.MonoPublishOn$PublishOnSubscriber.run(MonoPublishOn.java:187)
	at reactor.core.scheduler.SchedulerTask.call(SchedulerTask.java:68)
	at reactor.core.scheduler.SchedulerTask.call(SchedulerTask.java:28)
	at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
	at java.base/java.util.concurrent.ScheduledThreadPoolExecutor$ScheduledFutureTask.run(ScheduledThreadPoolExecutor.java:304)
	at java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1136)
	at java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:635)
	at java.base/java.lang.Thread.run(Thread.java:833)
Caused by: org.apache.kafka.common.errors.UnsupportedVersionException: Attempted to write a non-default includeClusterAuthorizedOperations at version 6

The UI has multiple issues
Brokers - page is compeltly blank
Topics - Loads forever
Consumers - A red error popup shows with
500 Internal Server Error
Error while creating AdminClient for Cluster stg

I can see the 0.5.0 version is using kafka 3.3.1 but 0.4.0 is using 2.8.0
i couldn't find any kafka version compatibility but i assume this is the cause of this issue
Expected behavior
Using a different version of kafka client according to remote version or listing supported versions in the README
Set up
1.Running docker image 0.5.0/0.4.0 in kubernetes cluster
2.Running 2.0.0 kafka cluster running on EC2
3.No other settings are changed
Steps to Reproduce

run the docker image with environment variables KAFKA_CLUSTERS_0_ZOOKEEPER and KAFKA_CLUSTERS_0_BOOTSTRAPSERVERS

Screenshots
None
Additional context
None

Hi, please try pulling master-labeled docker image. It's been fixed within #3141, we might do a minor release soon.
Cheers.


Fix broken URL for application dev

the actual URL is https://docs.substrate.io/build/application-dev/

If you found somewhere that the old name was used, please feel free to re-open.


Some known vulnerabilities

I'm working with Snyk to scan our code.
So far we've discovered some issues related to react-scripts 5.0.1 (Which is the latest version).
The specific vulnerable packages are:

nth-check < 2.0.1 (2.1.1 available, manual override is possible - https://github.com/facebook/create-react-app/issues/13364).
css-what < 5.0.1 (6.1.0 available).
postcss < 8.4.31 (latest).

Fixing these will dismiss the warnings and will allow working without any known risks until new ones are discovered.
Thanks :)

I moved the project to vite instead of react-scripts, the related vulnerabilities are now patched


You need to stop hijacking "localhost" while WPN-XM is not running

For some reasons, I switched WPN-XM to WAMPserver due to usage of Apache, I hadn't time to configure nginx for many reasons like php api url gives me download file which is wrong.
I disabled all daemons in WPN-XM, and started running wampserver, i tried to enter "localhost" and it shows WPN-XM redirection page, I was like WTF! I checked all daemons from WPN-XM are not running.
Should I uninstall WPN-XM to fix this issue?

Related to https://github.com/WPN-XM/WPN-XM/issues/177

I didn't install portable mode, It seems this #177 explains that I should manually remove server folder, correct?

Stop the daemons.
Check that they are down by using wpnxm-status.bat or status.bat depending on your version.
And don't forget to clear your browser cache... :)

Woah, clearing my browser cache fixed my issue, I was worried so much!
Thanks!


Issue with GPU code

Hello,
I'm having an issue with the GPU code, when I run even with the graph provided I always get zero for the number of triangles or other patterns. The OpenMP code seems to work fine with me. I provided the output of both GPU and OpenMP.
GPU:
./tc_gpu_base /home/ghadeer/cit-Patents/graph
Triangle Counting (for undirected graphs only)
Using DAG (static orientation)
Orientation enabled, using DAG
Time on generating the DAG: 0.216688 sec
|V| 3774769 |E| 16518947
Found 4 devices
Device[0]: NVIDIA TITAN V
Compute capability: 7.0
Warp size: 32
Total # SM: 80
Total # CUDA cores: 5120
Total amount of shared memory per block: 49152 bytes
Total # registers per block: 65536
Total amount of constant memory: 65536 bytes
Total global memory: 11.8 GB
Memory Clock Rate: 0.81 GHz
Memory Bus Width: 3072 bits
Peak Memory Bandwidth: 652.80 GB/s
Device[1]: NVIDIA GeForce RTX 2070 SUPER
Device[2]: NVIDIA TITAN Xp
Device[3]: Tesla K40c
GPU_total_mem =<PHONE_NUMBER>2 graph_mem = 162349736
Time on generating the edgelist: 0.070154 sec
Edge parallel: edgelist size = 16518947
max_blocks_per_SM = 0
CUDA triangle counting (65536 CTAs, 256 threads/CTA)
runtime [gpu_base] = 2e-06 sec
throughput = 8259.47 billion Traversed Edges Per Second (TEPS)
total_num_triangles = 0
OpenMP (which seems to work fine)
./tc_gpu_base 0 /home/ghadeer/cit-Patents/graph
Triangle Counting (for undirected graphs only)
Using DAG (static orientation)
tc_gpu_base: ../common/graph.cc:8: Graph::Graph(std::string, bool, bool): Assertion `f_meta' failed.
Aborted (core dumped)
[gaa54@ithaca bin]$ ./tc_gpu_base
Usage: ./tc_gpu_base  [num_gpu(1)] [chunk_size(1024)]
Example: ./tc_gpu_base /graph_inputs/mico/graph
[gaa54@ithaca bin]$ ./tc_omp_base /home/ghadeer/cit-Patents/graph 0
Triangle Counting (for undirected graphs only)
Using DAG (static orientation)
Orientation enabled, using DAG
Time on generating the DAG: 0.215716 sec
|V| 3774769 |E| 16518947
Launching OpenMP TC solver (32 threads) ...
runtime [omp_base] = 0.241254 sec
total_num_triangles = 7515023
Thank you

Have you set this flag for your GPU?
CUDA_ARCH := -gencode arch=compute_70,code=sm_70

Yes, I set this flag for my GPU but I still have the same problem.

Yes, I set this flag for my GPU but I still have the same problem.

which GPU do you use? I don't see this problem with a V100.


fix: updated deps

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


root matrix is not considered

Hello there.
Transform matrix in root element has no effect.
Thank for the coming fix.
root_matrix.svg.zip

@Papirosnik what would be your expected result? I found that root transformations in SVG is an unclear question (see https://github.com/w3c/csswg-drafts/issues/894). And Firefox, Chromium and Inkscape all treat it in a different way. So, I'm a bit confused now how it actually should work. Of course it should be implemented in accordanse to some specs, if some mention about that is found in any specs.

Also, I tried InternetExplorer, it seems to ignore the root transformation as well...
In some draft spec of SVG 2 I found that transformations should be applied before viewBox, but then transformations will affect the final size of the image, and it's not very clear how it should affect the raster image dimensions in case the transformation is rotation.
@Papirosnik what is your actual use case? As I understand you have this attached SVG generated by some editor program and it is rendered smaller than you'd expect by svgren right?

Ok, the other thing is that looks like the svg element cannot have transform attribute at all, see https://www.w3.org/TR/SVG/struct.html#SVGElement. So, the request for this looks invalid.
But still, I would like to hear about your use case, @Papirosnik .

Yeah, it appears smaller than expected.
But having your info in mind I have to rethink our expectation.

I have to agree with you and withdraw my request.
Thanks a lot for the clarification.

Thanks. It looks like in SVG v2 there will be transform attribute for svg element, but we're not there yet. So, closing the issue.


Adds a check for strict types

This adds a requirement for files to declare strict types. I opted to do this through PHPStan rather than a sniff so that we can easily generate a baseline for existing files.

@olivernybroe nice work on the conversion to Pest 😎


New version: Peppy.Osu! version 2022.127.0

ARP entries are correct.
Auto-updated by vedantmgoyal2009/winget-pkgs-automation in workflow run 2114
Microsoft Reviewers: Open in CodeFlow

#42616


SciPy Datasets Test CI python3.11-dev & python3.8-dbg

Reference issue

What does this implement/fix?

Additional information

Ah, it looks like Pooch doesn't support Python 3.11-dev yet (without deprecation warnings that is), and i don't see an open issue at https://github.com/fatiando/pooch/issues for it yet.
The SciPy test suite converts warnings into errors, which is quite useful but leads to strange tracebacks when that happens during import of another package.

Yes, that probably is the case for 3.11 but what I don't quite understand is why are we facing similar errors in python 3.8 dbg build? I remember earlier this job was passing (no idea what's changed in between).


Remove deprecated #load_wav functions from io backend classes

Testing Steps:
Run entire test suite.
I am getting one failure locally, but it doesn't look related to these changes.

Seems to have to do with imprecision of floating point arithemetic. Let me know if you want me to relax the threshold slightly -- it may be that the tests do not fail on CI build. (edit: I actually don't see the tests running on checks).
Let me know what you think. Thanks!

@mthrok hmm... I did use the locally built sox as opposed to the package.

@iseessel Can you push something so that web hook is delivered? I cannot find a way to trigger CI.

Strange... other PRs are triggering CI properly but not this one.
let me see if closing and reopening helps.

here it goes.

@iseessel flake8 is failing. Can you remove the no longer used import statement?
torchaudio/backend/no_backend.py:2:1: F401 'typing.Any' imported but unused

Yep, I see a few failures, I'll work through them. @mthrok

@iseessel other PRs landed on master is causing conflict. Could you resolve it?

I've rebased and resolved conflicts. @mthrok
Errors I've fixed:

Sphinx Doc creation was failing -- I've updated relevant rst's to remove deleted methods from the docs.
"torchaudio/backend/no_backend.py:2:1: F401 'typing.Any' imported but unused" style guide was failing. I've removed the import.

Tests Still failing (Look unrelated to PR):

https://github.com/pytorch/audio/pull/1362/checks?check_run_id=204296817.  Looks like a dependency issue.

Thanks!


Add total time to STAR chart tooltips

Notes
One critical piece of context for understanding STAR data results is the time the student spent taking the test. If the student spent less than a minute, that means they quit early and the data point is essentially junk data. This is a first pass at visualizing total time along with STAR results, by adding it to the additional information displayed in the tooltip.
Screenshot (Internet Explorer, fake data)
TK
Checklist

[ ] Checked latest commit in Internet Explorer
[ ] Added specs for additional JS

Realizing that moment.humanize() doesn't supply a super accurate or precise result. It's rounds 23 minutes and 40 seconds up to say "24 minutes", which is less precise than we want. Looking at https://github.com/moment/moment/issues/348.

selfie 🚢


App crashes

Device: iPhone SE Gen 1
App: 0.25.5(20)
iOS: 15.8
The crash report might have been sent by TestFlight already but in any case, I have also shared what exactly happened in the additional info of the crash report.
Current Behavior:
as soon as the app homepage opens, the app crashes.

Hi
I know it.
Patch is already in review @ Apple.
Also I've made a new release, that is already can be downloaded via GitHub
release

I've had the same issue for the quite some time, actually. Today I was finally able to get it recorded.
iPhone 14 Pro Max
iOS: 17.1.1
App: 0.25.6
https://github.com/oolxg/Hanami/assets/1661112/0cc6b269-0198-416e-8274-a6177b413c06

@mazulo
Thanks
Will investigate later

I don't have experience with swift but today I'm going to fork the project and run it locally to see if I can find anything. I also have a few ideas for features that would be awesome to have. Let's see if I can get something

@mazulo
Can you also explain what you did before the app crashed. Like tapped on chapter or what? From recording it's hard to understand the trigger of the crash

@mazulo
Can you also explain what you did before the app crashed. Like tapped on chapter or what? From recording it's hard to understand the trigger of the crash
I tried to download it as on record and i got no crash :/

@oolxg i was just scrolling the chapters and tapping the download icon. After each time I tapped the download, I was just scrolling up so that I could expand/collapse another chapter


Peer to Peer code Review

Hey @Nicolaswg  & @Reem-lab
Awesome job on the code, the UI looks absolutely amazing 🔥
I personally really liked how you styled your card backgrounds. They're mesmerizing
Some Suggestions

You can add CSS property cursor: pointer to your button because it will look like it's pressable on hover :)
And maybe add an overflow: scroll property to your comment popup. I personally believe it will make it look been better

Hello @Reem-lab and @Nicolaswg
First of all, congratulations on your amazing job!!!.

Your website looks awesome.

I do not have other suggestions.
Happy coding!!!

Thanks @gabyse1  and @zhadier  For the review ♥

I would like to do the updates to be better ♻


[BUG] [Windows] Rancher cli prints file permission warning on Windows

Rancher Server Setup

Rancher version: CLI version 2.8.0 and higher
Installation option (Docker install/Helm Chart): n/a

If Helm Chart, Kubernetes Cluster and version (RKE1, RKE2, k3s, EKS, etc): n/a

Proxy/Cert Details: n/a

Information about the Cluster

Kubernetes version: n/a
Cluster Type (Local/Downstream): n/a

If downstream, what type of cluster? (Custom/Imported or specify provider for Hosted/Infrastructure Provider):

User Information

What is the role of the user logged in? (Admin/Cluster Owner/Cluster Member/Project Owner/Project Member/Custom)

If custom, define the set of permissions: n/a

Describe the bug
When running rancher-cli commands on Windows the following warning are printed
time="2024-08-12T05:56:20Z" level=warning msg="Rancher configuration file C:\\Users\\Administrator\\.rancher\\cli2.json is group-readable. This is insecure."
time="2024-08-12T05:56:20Z" level=warning msg="Rancher configuration file C:\\Users\\Administrator\\.rancher\\cli2.json is world-readable. This is insecure."

These warnings were introduced in https://github.com/rancher/cli/pull/341, which aimed to reduce the scope of permission set on the rancher-cli config file. Unfortunately, golang on Windows does not handle file permissions in the same way as it does on Linux. Go will only use the owner bit for all fields, resulting in 600 creating a 666 file. This fails the check added in 341 and results in warning messages. However, the ACLs for this file are limited and only the user who created the file, the Administrators group, and the system itself will have read write access to the config file. This ACL configuration is in line with how other Rancher components and non-rancher open source projects create files on Windows nodes.
To Reproduce
run rancher-cli login <SERVER> --token <TOKEN>, select a context, and then run rancher-cli ps
Result
The above mentioned warning logs are printed in the console
Expected Result
No warning logs
Screenshots

Additional context

Closed in favor of https://github.com/rancher/rancher/issues/46769


Support reducing a model considering non-zero positions of removed joints

WIP

📚 Documentation preview 📚: https://jaxsim--137.org.readthedocs.build//137/

Tests are temporarily failing since they need a released version of iDynTree that includes https://github.com/robotology/idyntree/pull/1180.


Initial testing framework to master

Signed-off-by: Theodor Gherzan<EMAIL_ADDRESS>

Nitty gritty, but why are you signing off as @telphan :P ?


Device code flow not working with /common

https://github.com/Azure-Samples/ms-identity-python-devicecodeflow/blob/bb57d559d27f6ed2543846f25412349a1072f764/parameters.json#L2
For some reason, I'm unable to do device code flow with /common.
"AADSTS50059: No tenant-identifying information found in either the request or implied by any provided credentials.\r\nTrace ID: 0429e904-7771-4175-a8c6-366cb0b30400\r\nCorrelation ID: 54a1a1ab-cb1f-4b26-a7cb-34315391d301\r\nTimestamp: 2020-10-10 22:29:22Z",
I made sure that Default to Public Client on the app registration is set.  If I change /common to /microsoft.com in parameters.json, then this sample works perfectly.
I am using a multi-tenant app.
Who can use this application or access this API?
Accounts in any organizational directory (Any Azure AD directory - Multitenant) and personal Microsoft accounts (e.g. Skype, Xbox)
Is this expected?  Does the app need to be audience AAD-only?  If so, we better update the documentation and samples.

@rayluo did you see this issue?

No. Somehow this repo is not on my subscription list.
Regarding to the topic in this issue, it is supposed to work. We even explicitly switched to use ".../common" in our main repo's sample here. I guess we would need a repro for this issue for further investigation.

I got same error when using out-of-the-box version of repo:
"AADSTS50059: No tenant-identifying information found in either the request or implied by any provided credentials..."
I solved it by replacing "/common" with "/tenantid":
"authority": "https://login.microsoftonline.com/common"


Making the Footer Responsive

Presently, the footer is not responsive. I would like to work on it. Please assign me this issue. @vinitshahdeo

Assigning you. @goyalmuskan

Is this done. If not I would liek to work on it @goyalmuskan

@Ruchika30 Hey, this is merged.


How to play in background?

How can I make sure that music continues to play when minimizing the application.

Hey @Datastore24Kirill
Make sure that the background mode is checked for Audio, Airplay and PiP in the capabilities section of your app:


RHMAP-15272 - sync does not allow overwriting sync options per dataset

What
sync was resetting dataset.config to global sync config
How

added config per dataset
changed order of parameters in sync.manage

JIRA
https://issues.jboss.org/browse/RHMAP-15272
Related PRs
https://github.com/feedhenry/fh-js-sdk/pull/206
@nialldonnellyfh
@wtrocki

@witmicko I think its worth doing performance as part of this work.
@grdryn can you point us to infrastructure where we can test this (using PM)?

@wtrocki now it wont affect it, times we were trying to set were the same as the default ones


Remove multiservice regions

@Jann-Skotdal : Thanks for your contribution! The author(s) have been notified to review your proposed change.

#sign-off


iOS: No way to retrieve user-friendly filename from Medium.

I was hoping that I could get the IMG_XXX.JPG filename back from a Medium object but it doesn't look like it is exposed.
I'm building a synchronization engine and while I can use medium.id to generate unique filenames, I'd like to use the friendly names so that I match the behavior that the user sees when they share a photo with others via the iPhone.

Sorry for the late reply! I have added filename property of Medium in version 1.1.1.


Not a prime number in the hashencoder

https://github.com/ashawkey/torch-ngp/blob/56bae6037e68041d7b36024a684177a566f66301/hashencoder/src/hashencoder.cu#L42
One of these numbers is not a prime. This was already fixed in the tiny-cuda-nn repository. And if I remember well the original paper about this hash encoding technique says that the prime numbers used should be big numbers (do not ask me to define big number :D).
BTW: great job you've done here!

Thanks a lot! I have fixed it in https://github.com/ashawkey/torch-ngp/commit/cfcaed4e3e6db81fa2b08a76b3e9479b24fb5984.


Controller ERROR InvalidParameter: Security group X and subnet Y belong to different networks.

Version

Karpenter Version: v0.24.0

Kubernetes Version: v1.24
Expected Behavior
I followed the guide: https://karpenter.sh/v0.24.0/getting-started/getting-started-with-eksctl/
I created the cluster using ekscli:
eksctl create cluster -f - << EOF
---
apiVersion: eksctl.io/v1alpha5
kind: ClusterConfig

metadata:
  name: ${CLUSTER_NAME}
  region: ${AWS_DEFAULT_REGION}
  version: "1.24"
  tags:
    karpenter.sh/discovery: ${CLUSTER_NAME}
    kubernetes.io/cluster/${CLUSTER_NAME}=owned

managedNodeGroups:
  - name: main
    instanceTypes: ["t3a.medium", "t3.medium", "t3a.large", "t3.large", "m5a.large", "m6a.large"]
    minSize: 1
    maxSize: 5
    desiredCapacity: 2
    labels:
      nodegroup-type: main-nodes

iam:
  withOIDC: true
  serviceAccounts:
  - metadata:
      name: karpenter
      namespace: karpenter
    roleName: ${CLUSTER_NAME}-karpenter
    attachPolicyARNs:
    - arn:aws:iam::${AWS_ACCOUNT_ID}:policy/KarpenterControllerPolicy-${CLUSTER_NAME}
    roleOnly: true

iamIdentityMappings:
- arn: "arn:aws:iam::${AWS_ACCOUNT_ID}:role/KarpenterNodeRole-${CLUSTER_NAME}"
  username: system:node:{{EC2PrivateDNSName}}
  groups:
  - system:bootstrappers
  - system:nodes

# cluster AZs must be set explicitly for single AZ nodegroup example to work
availabilityZones: [${AWS_ZONES}]
EOF

Added Provisoner:
cat <<EOF | kubectl apply -f -
apiVersion: karpenter.sh/v1alpha5
kind: Provisioner
metadata:
  name: spot
spec:
  requirements:
    - key: "node.kubernetes.io/instance-type"
      operator: In
      values: ["m6a.xlarge", "m5a.xlarge","m6i.xlarge", "r6a.xlarge", "r5a.xlarge"]
    - key: "kubernetes.io/arch"
      operator: In
      values: ["amd64"]
    - key: "karpenter.sh/capacity-type"
      operator: In
      values: ["spot"]
  ttlSecondsAfterEmpty: 30
  providerRef:
    name: spot
  taints:
    - key: spot
      value: "true"
      effect: NoSchedule
---
apiVersion: karpenter.k8s.aws/v1alpha1
kind: AWSNodeTemplate
metadata:
  name: spot
spec:
  subnetSelector:
    karpenter.sh/discovery: "${CLUSTER_NAME}"
  securityGroupSelector:
    karpenter.sh/discovery: "${CLUSTER_NAME}"
EOF

Expected behavior is: New node Created
Actual Behavior
ERROR:
ERROR   controller.provisioner  launching machine, creating cloud provider instance, creating instance, with fleet error(s), InvalidParameter: Security group sg-089171ea7e37b8bf7 and subnet subnet-0a4915fa517269a14 belong to different networks.; InvalidParameter: Security group sg-089171ea7e37b8bf7 and subnet subnet-061692cad8fdd4e2e belong to different networks.

Steps to Reproduce the Problem
I followed the guide: https://karpenter.sh/v0.24.0/getting-started/getting-started-with-eksctl/
I created the cluster using ekscli:
eksctl create cluster -f - << EOF
---
apiVersion: eksctl.io/v1alpha5
kind: ClusterConfig

metadata:
  name: ${CLUSTER_NAME}
  region: ${AWS_DEFAULT_REGION}
  version: "1.24"
  tags:
    karpenter.sh/discovery: ${CLUSTER_NAME}
    kubernetes.io/cluster/${CLUSTER_NAME}=owned

managedNodeGroups:
  - name: main
    instanceTypes: ["t3a.medium", "t3.medium", "t3a.large", "t3.large", "m5a.large", "m6a.large"]
    minSize: 1
    maxSize: 5
    desiredCapacity: 2
    labels:
      nodegroup-type: main-nodes

iam:
  withOIDC: true
  serviceAccounts:
  - metadata:
      name: karpenter
      namespace: karpenter
    roleName: ${CLUSTER_NAME}-karpenter
    attachPolicyARNs:
    - arn:aws:iam::${AWS_ACCOUNT_ID}:policy/KarpenterControllerPolicy-${CLUSTER_NAME}
    roleOnly: true

iamIdentityMappings:
- arn: "arn:aws:iam::${AWS_ACCOUNT_ID}:role/KarpenterNodeRole-${CLUSTER_NAME}"
  username: system:node:{{EC2PrivateDNSName}}
  groups:
  - system:bootstrappers
  - system:nodes

# cluster AZs must be set explicitly for single AZ nodegroup example to work
availabilityZones: [${AWS_ZONES}]
EOF

Added Provisoner:
cat <<EOF | kubectl apply -f -
apiVersion: karpenter.sh/v1alpha5
kind: Provisioner
metadata:
  name: spot
spec:
  requirements:
    - key: "node.kubernetes.io/instance-type"
      operator: In
      values: ["m6a.xlarge", "m5a.xlarge","m6i.xlarge", "r6a.xlarge", "r5a.xlarge"]
    - key: "kubernetes.io/arch"
      operator: In
      values: ["amd64"]
    - key: "karpenter.sh/capacity-type"
      operator: In
      values: ["spot"]
  ttlSecondsAfterEmpty: 30
  providerRef:
    name: spot
  taints:
    - key: spot
      value: "true"
      effect: NoSchedule
---
apiVersion: karpenter.k8s.aws/v1alpha1
kind: AWSNodeTemplate
metadata:
  name: spot
spec:
  subnetSelector:
    karpenter.sh/discovery: "${CLUSTER_NAME}"
  securityGroupSelector:
    karpenter.sh/discovery: "${CLUSTER_NAME}"
EOF

Related to https://github.com/aws/karpenter/issues/404  but I'm using the 0.24.0 version and it should be fixed.
Old Bug: https://github.com/aws/karpenter/issues/3007
Resource Specs and Logs
cat <<EOF | kubectl apply -f -
apiVersion: karpenter.sh/v1alpha5
kind: Provisioner
metadata:
  name: spot
spec:
  requirements:
    - key: "node.kubernetes.io/instance-type"
      operator: In
      values: ["m6a.xlarge", "m5a.xlarge","m6i.xlarge", "r6a.xlarge", "r5a.xlarge"]
    - key: "kubernetes.io/arch"
      operator: In
      values: ["amd64"]
    - key: "karpenter.sh/capacity-type"
      operator: In
      values: ["spot"]
  ttlSecondsAfterEmpty: 30
  providerRef:
    name: spot
  taints:
    - key: spot
      value: "true"
      effect: NoSchedule
---
apiVersion: karpenter.k8s.aws/v1alpha1
kind: AWSNodeTemplate
metadata:
  name: spot
spec:
  subnetSelector:
    karpenter.sh/discovery: "${CLUSTER_NAME}"
  securityGroupSelector:
    karpenter.sh/discovery: "${CLUSTER_NAME}"
EOF

LOGS:
2023/02/13 10:07:48 Registering 2 clients
2023/02/13 10:07:48 Registering 2 informer factories
2023/02/13 10:07:48 Registering 3 informers
2023/02/13 10:07:48 Registering 6 controllers
2023-02-13T10:07:48.141Z        DEBUG   controller.aws  discovered kube dns     {"commit": "8c27519-dirty", "kube-dns-ip": "<IP_ADDRESS>"}
2023-02-13T10:07:48.145Z        DEBUG   controller.aws  discovered version      {"commit": "8c27519-dirty", "version": "v0.24.0"}
2023-02-13T10:07:48.152Z        INFO    controller      Starting server {"commit": "8c27519-dirty", "path": "/metrics", "kind": "metrics", "addr": "[::]:8080"}
2023-02-13T10:07:48.153Z        INFO    controller      Starting server {"commit": "8c27519-dirty", "kind": "health probe", "addr": "[::]:8081"}
I0213 10:07:48.255554       1 leaderelection.go:248] attempting to acquire leader lease karpenter/karpenter-leader-election...
2023-02-13T10:07:48.313Z        INFO    controller      Starting informers...   {"commit": "8c27519-dirty"}
2023-02-13T10:07:49.076Z        INFO    controller.aws.pricing  updated spot pricing with instance types and offerings  {"commit": "8c27519-dirty", "instance-type-count": 612, "offering-count": 2832}
2023-02-13T10:07:50.260Z        INFO    controller.aws.pricing  updated on-demand pricing       {"commit": "8c27519-dirty", "instance-type-count": 613}
I0213 10:21:20.306421       1 leaderelection.go:258] successfully acquired lease karpenter/karpenter-leader-election
2023-02-13T10:21:20.307Z        INFO    controller.provisioner  starting controller     {"commit": "8c27519-dirty"}
2023-02-13T10:21:20.307Z        INFO    controller.deprovisioning       starting controller     {"commit": "8c27519-dirty"}
2023-02-13T10:21:20.307Z        INFO    controller.metricscraper        starting controller     {"commit": "8c27519-dirty"}
2023-02-13T10:21:20.307Z        INFO    controller      Starting EventSource    {"commit": "8c27519-dirty", "controller": "node-state", "controllerGroup": "", "controllerKind": "Node", "source": "kind source: *v1.Node"}
2023-02-13T10:21:20.307Z        INFO    controller      Starting Controller     {"commit": "8c27519-dirty", "controller": "node-state", "controllerGroup": "", "controllerKind": "Node"}
2023-02-13T10:21:20.308Z        INFO    controller      Starting EventSource    {"commit": "8c27519-dirty", "controller": "provisioning", "controllerGroup": "", "controllerKind": "Pod", "source": "kind source: *v1.Pod"}
2023-02-13T10:21:20.308Z        INFO    controller      Starting Controller     {"commit": "8c27519-dirty", "controller": "provisioning", "controllerGroup": "", "controllerKind": "Pod"}
2023-02-13T10:21:20.308Z        INFO    controller      Starting EventSource    {"commit": "8c27519-dirty", "controller": "provisionerstate", "controllerGroup": "karpenter.sh", "controllerKind": "Provisioner", "source": "kind source: *v1alpha5.Provisioner"}
2023-02-13T10:21:20.308Z        INFO    controller      Starting Controller     {"commit": "8c27519-dirty", "controller": "provisionerstate", "controllerGroup": "karpenter.sh", "controllerKind": "Provisioner"}
2023-02-13T10:21:20.309Z        INFO    controller      Starting EventSource    {"commit": "8c27519-dirty", "controller": "pod-state", "controllerGroup": "", "controllerKind": "Pod", "source": "kind source: *v1.Pod"}
2023-02-13T10:21:20.309Z        INFO    controller      Starting Controller     {"commit": "8c27519-dirty", "controller": "pod-state", "controllerGroup": "", "controllerKind": "Pod"}
2023-02-13T10:21:20.309Z        INFO    controller      Starting EventSource    {"commit": "8c27519-dirty", "controller": "termination", "controllerGroup": "", "controllerKind": "Node", "source": "kind source: *v1.Node"}
2023-02-13T10:21:20.309Z        INFO    controller      Starting Controller     {"commit": "8c27519-dirty", "controller": "termination", "controllerGroup": "", "controllerKind": "Node"}
2023-02-13T10:21:20.309Z        INFO    controller      Starting EventSource    {"commit": "8c27519-dirty", "controller": "node", "controllerGroup": "", "controllerKind": "Node", "source": "kind source: *v1.Node"}
2023-02-13T10:21:20.310Z        INFO    controller      Starting EventSource    {"commit": "8c27519-dirty", "controller": "node", "controllerGroup": "", "controllerKind": "Node", "source": "kind source: *v1alpha5.Provisioner"}
2023-02-13T10:21:20.310Z        INFO    controller      Starting EventSource    {"commit": "8c27519-dirty", "controller": "node", "controllerGroup": "", "controllerKind": "Node", "source": "kind source: *v1.Pod"}
2023-02-13T10:21:20.310Z        INFO    controller      Starting Controller     {"commit": "8c27519-dirty", "controller": "node", "controllerGroup": "", "controllerKind": "Node"}
2023-02-13T10:21:20.310Z        INFO    controller      Starting EventSource    {"commit": "8c27519-dirty", "controller": "provisionermetrics", "controllerGroup": "karpenter.sh", "controllerKind": "Provisioner", "source": "kind source: *v1alpha5.Provisioner"}
2023-02-13T10:21:20.310Z        INFO    controller      Starting Controller     {"commit": "8c27519-dirty", "controller": "provisionermetrics", "controllerGroup": "karpenter.sh", "controllerKind": "Provisioner"}
2023-02-13T10:21:20.310Z        INFO    controller      Starting EventSource    {"commit": "8c27519-dirty", "controller": "podmetrics", "controllerGroup": "", "controllerKind": "Pod", "source": "kind source: *v1.Pod"}
2023-02-13T10:21:20.310Z        INFO    controller      Starting Controller     {"commit": "8c27519-dirty", "controller": "podmetrics", "controllerGroup": "", "controllerKind": "Pod"}
2023-02-13T10:21:20.310Z        INFO    controller      Starting EventSource    {"commit": "8c27519-dirty", "controller": "inflightchecks", "controllerGroup": "", "controllerKind": "Node", "source": "kind source: *v1.Node"}
2023-02-13T10:21:20.310Z        INFO    controller      Starting Controller     {"commit": "8c27519-dirty", "controller": "inflightchecks", "controllerGroup": "", "controllerKind": "Node"}
2023-02-13T10:21:20.310Z        INFO    controller      Starting EventSource    {"commit": "8c27519-dirty", "controller": "counter", "controllerGroup": "karpenter.sh", "controllerKind": "Provisioner", "source": "kind source: *v1alpha5.Provisioner"}
2023-02-13T10:21:20.311Z        INFO    controller      Starting EventSource    {"commit": "8c27519-dirty", "controller": "counter", "controllerGroup": "karpenter.sh", "controllerKind": "Provisioner", "source": "kind source: *v1.Node"}
2023-02-13T10:21:20.311Z        INFO    controller      Starting Controller     {"commit": "8c27519-dirty", "controller": "counter", "controllerGroup": "karpenter.sh", "controllerKind": "Provisioner"}
2023-02-13T10:21:20.311Z        INFO    controller      Starting EventSource    {"commit": "8c27519-dirty", "controller": "awsnodetemplate", "controllerGroup": "karpenter.k8s.aws", "controllerKind": "AWSNodeTemplate", "source": "kind source: *v1alpha1.AWSNodeTemplate"}
2023-02-13T10:21:20.311Z        INFO    controller      Starting Controller     {"commit": "8c27519-dirty", "controller": "awsnodetemplate", "controllerGroup": "karpenter.k8s.aws", "controllerKind": "AWSNodeTemplate"}
2023-02-13T10:21:20.311Z        INFO    controller.interruption starting controller     {"commit": "8c27519-dirty"}
2023-02-13T10:21:20.311Z        DEBUG   controller.interruption watching interruption queue     {"commit": "8c27519-dirty", "queue": "tokenflow-k8s-poc"}
2023-02-13T10:21:20.312Z        DEBUG   controller.aws  hydrating the launch template cache     {"commit": "8c27519-dirty", "tag-key": "karpenter.k8s.aws/cluster", "tag-value": "tokenflow-k8s-poc"}
2023-02-13T10:21:20.400Z        DEBUG   controller.aws  finished hydrating the launch template cache    {"commit": "8c27519-dirty", "tag-key": "karpenter.k8s.aws/cluster", "tag-value": "tokenflow-k8s-poc", "item-count": 0}
2023-02-13T10:21:20.408Z        INFO    controller      Starting workers        {"commit": "8c27519-dirty", "controller": "provisioning", "controllerGroup": "", "controllerKind": "Pod", "worker count": 10}
2023-02-13T10:21:20.408Z        INFO    controller      Starting workers        {"commit": "8c27519-dirty", "controller": "provisionerstate", "controllerGroup": "karpenter.sh", "controllerKind": "Provisioner", "worker count": 10}
2023-02-13T10:21:20.409Z        INFO    controller      Starting workers        {"commit": "8c27519-dirty", "controller": "node-state", "controllerGroup": "", "controllerKind": "Node", "worker count": 10}
2023-02-13T10:21:20.411Z        INFO    controller      Starting workers        {"commit": "8c27519-dirty", "controller": "pod-state", "controllerGroup": "", "controllerKind": "Pod", "worker count": 10}
2023-02-13T10:21:20.412Z        INFO    controller      Starting workers        {"commit": "8c27519-dirty", "controller": "podmetrics", "controllerGroup": "", "controllerKind": "Pod", "worker count": 1}
2023-02-13T10:21:20.511Z        INFO    controller      Starting workers        {"commit": "8c27519-dirty", "controller": "inflightchecks", "controllerGroup": "", "controllerKind": "Node", "worker count": 10}
2023-02-13T10:21:20.512Z        INFO    controller      Starting workers        {"commit": "8c27519-dirty", "controller": "node", "controllerGroup": "", "controllerKind": "Node", "worker count": 10}
2023-02-13T10:21:20.515Z        INFO    controller      Starting workers        {"commit": "8c27519-dirty", "controller": "provisionermetrics", "controllerGroup": "karpenter.sh", "controllerKind": "Provisioner", "worker count": 1}
2023-02-13T10:21:20.515Z        INFO    controller      Starting workers        {"commit": "8c27519-dirty", "controller": "awsnodetemplate", "controllerGroup": "karpenter.k8s.aws", "controllerKind": "AWSNodeTemplate", "worker count": 10}
2023-02-13T10:21:20.516Z        INFO    controller      Starting workers        {"commit": "8c27519-dirty", "controller": "counter", "controllerGroup": "karpenter.sh", "controllerKind": "Provisioner", "worker count": 10}
2023-02-13T10:21:20.516Z        INFO    controller      Starting workers        {"commit": "8c27519-dirty", "controller": "termination", "controllerGroup": "", "controllerKind": "Node", "worker count": 10}
2023-02-13T10:21:20.602Z        DEBUG   controller.awsnodetemplate      discovered subnets      {"commit": "8c27519-dirty", "awsnodetemplate": "spot", "subnets": ["subnet-09b275305b2fb716d (us-east-1f)", "subnet-03d6465fce8eccc6b (us-east-1c)", "subnet-0d3e45bbfeaee6895 (us-east-1c)", "subnet-061692cad8fdd4e2e (us-east-1f)", "subnet-0a4915fa517269a14 (us-east-1c)"]}
2023-02-13T10:21:20.660Z        DEBUG   controller.awsnodetemplate      discovered security groups      {"commit": "8c27519-dirty", "awsnodetemplate": "spot", "security-groups": ["sg-02669632d322aecad", "sg-06d16ef06368c9c43", "sg-0a8889f078e610089", "sg-089171ea7e37b8bf7"]}
2023-02-13T10:21:21.957Z        DEBUG   controller.deprovisioning       discovered EC2 instance types   {"commit": "8c27519-dirty", "instance-type-count": 605}
2023-02-13T10:21:22.268Z        DEBUG   controller.deprovisioning       discovered EC2 instance types zonal offerings for subnets       {"commit": "8c27519-dirty", "subnet-selector": "{\"karpenter.sh/discovery\":\"tokenflow-k8s-poc\"}"}
2023-02-13T10:21:45.282Z        INFO    controller.provisioner  found provisionable pod(s)      {"commit": "8c27519-dirty", "pods": 1}
2023-02-13T10:21:45.282Z        INFO    controller.provisioner  computed new node(s) to fit pod(s)      {"commit": "8c27519-dirty", "nodes": 1, "pods": 1}
2023-02-13T10:21:45.282Z        INFO    controller.provisioner  launching machine with 1 pods requesting {"cpu":"3125m","memory":"3Gi","pods":"3"} from types r5a.xlarge, m6a.xlarge, r6a.xlarge, m6i.xlarge, m5a.xlarge    {"commit": "8c27519-dirty", "provisioner": "spot"}
2023-02-13T10:21:45.316Z        DEBUG   controller.provisioner.cloudprovider    discovered kubernetes version   {"commit": "8c27519-dirty", "provisioner": "spot", "kubernetes-version": "1.24"}
2023-02-13T10:21:45.363Z        DEBUG   controller.provisioner.cloudprovider    discovered new ami      {"commit": "8c27519-dirty", "provisioner": "spot", "ami": "ami-06bf8e441ff8de6c6", "query": "/aws/service/eks/optimized-ami/1.24/amazon-linux-2/recommended/image_id"}
2023-02-13T10:21:45.508Z        DEBUG   controller.provisioner.cloudprovider    created launch template {"commit": "8c27519-dirty", "provisioner": "spot", "launch-template-name": "Karpenter-tokenflow-k8s-poc-8203095505758827270", "launch-template-id": "lt-001a856bedb159636"}

2023-02-13T10:21:51.415Z        ERROR   controller.provisioner  launching machine, creating cloud provider instance, creating instance, with fleet error(s), InvalidParameter: Security group sg-089171ea7e37b8bf7 and subnet subnet-0a4915fa517269a14 belong to different networks.; InvalidParameter: Security group sg-089171ea7e37b8bf7 and subnet subnet-061692cad8fdd4e2e belong to different networks.       {"commit": "8c27519-dirty"}

2023-02-13T10:21:55.209Z        INFO    controller.provisioner  found provisionable pod(s)      {"commit": "8c27519-dirty", "pods": 1}
2023-02-13T10:21:55.209Z        INFO    controller.provisioner  computed new node(s) to fit pod(s)      {"commit": "8c27519-dirty", "nodes": 1, "pods": 1}
2023-02-13T10:21:55.210Z        INFO    controller.provisioner  launching machine with 1 pods requesting {"cpu":"3125m","memory":"3Gi","pods":"3"} from types r5a.xlarge, m6a.xlarge, r6a.xlarge, m6i.xlarge, m5a.xlarge    {"commit": "8c27519-dirty", "provisioner": "spot"}
2023-02-13T10:22:00.972Z        ERROR   controller.provisioner  launching machine, creating cloud provider instance, creating instance, with fleet error(s), InvalidParameter: Security group sg-089171ea7e37b8bf7 and subnet subnet-0a4915fa517269a14 belong to different networks.; InvalidParameter: Security group sg-089171ea7e37b8bf7 and subnet subnet-061692cad8fdd4e2e belong to different networks.       {"commit": "8c27519-dirty"}

Community Note

Please vote on this issue by adding a 👍 reaction to the original issue to help the community and maintainers prioritize this request
Please do not leave "+1" or "me too" comments, they generate extra noise for issue followers and do not help prioritize the request
If you are interested in working on this issue or have submitted a pull request, please leave a comment

I followed the guide: https://karpenter.sh/v0.24.0/getting-started/getting-started-with-eksctl/
I use eksctl and it creates the SCs and Subnets for me so I did not tag anything, I run:
eksctl create cluster -f - << EOF
---
apiVersion: eksctl.io/v1alpha5
kind: ClusterConfig

metadata:
  name: ${CLUSTER_NAME}
  region: ${AWS_DEFAULT_REGION}
  version: "1.24"
  tags:
    karpenter.sh/discovery: ${CLUSTER_NAME}
    kubernetes.io/cluster/${CLUSTER_NAME}=owned

managedNodeGroups:
  - name: main
    instanceTypes: ["t3a.medium", "t3.medium", "t3a.large", "t3.large", "m5a.large", "m6a.large"]
    minSize: 1
    maxSize: 5
    desiredCapacity: 2
    labels:
      nodegroup-type: main-nodes

iam:
  withOIDC: true
  serviceAccounts:
  - metadata:
      name: karpenter
      namespace: karpenter
    roleName: ${CLUSTER_NAME}-karpenter
    attachPolicyARNs:
    - arn:aws:iam::${AWS_ACCOUNT_ID}:policy/KarpenterControllerPolicy-${CLUSTER_NAME}
    roleOnly: true

iamIdentityMappings:
- arn: "arn:aws:iam::${AWS_ACCOUNT_ID}:role/KarpenterNodeRole-${CLUSTER_NAME}"
  username: system:node:{{EC2PrivateDNSName}}
  groups:
  - system:bootstrappers
  - system:nodes

# cluster AZs must be set explicitly for single AZ nodegroup example to work
availabilityZones: [${AWS_ZONES}]
EOF

to create the whole cluster.

eksctl will not create SGs or subnets.
so something else is creating those.
can you describe those resources? the ones with the tag.
and see if they are in the same VPC

eksctl will not create SGs or subnets. so something else is creating those. can you describe those resources? the ones with the tag. and see if they are in the same VPC

eksctl is creating SG and subnets, I can see it in the cloud formation template. It also adds the tags to the SGs:
karpenter.sh/discovery
alpha.eksctl.io/cluster-name

alpha.eksctl.io/cluster-oidc-enabled | true
alpha.eksctl.io/eksctl-version | 0.129.0

and the ones created by cloudformation are the only ones with those tags?
or does your account have other SG and subnets with that tag too?

No, there i just the default VPC which has SGs without tags.

Hi, I found the issue, it seems a ekscli delete command did not complete successfully and there were extra SGs and subnets that were not cleared. After manually deleting them it works fine. Thanks!


Debug C functions in application with vscode client.

I have embedded LUA in my C++ program, how can I bind the vscode client to my program?
Making my program the debug server?
I have custom C functions that are in my script. 🥲

I think you are looking for a lua debugger, try https://marketplace.visualstudio.com/items?itemName=actboy168.lua-debug

@Anderson0xFF has your issue been resolved?


Implement: auth init

Add a "auth init" command to tapis-cli

Completed 15d63e414e612ab32efe19dde10e63e0ae313c38

Specifying all the options generates some warnings and requires a redundant keyboard interaction:
# tapis auth init --tenant-id tacc.prod --username urrutia --password xxxx
Tenant changed. Username and password must be specified.
Username changed. Password must be specified.
Username [urrutia]:

Which then goes through fine if you hit the return key, but I wouldn't expect that to be necessary.


Error formatting filter: progid:

Operating System (+Version):  Windows 10 Enterprise 1703
VS Code Version: 1.12.2
beautify Version: 1.1.1

.scss
filter: progid:DXImageTransform.Microsoft.gradient( startColorstr='#00b7eb', endColorstr='#ffffff', GradientType=0);

turns to:
filter: progid: DXImageTransform.Microsoft.gradient( startColorstr='#00b7eb', endColorstr='#ffffff', GradientType=0);
               ^ this space

I have the basic settings. And the beautifier adds a space after progid and when the scss is formated it crashes.

There was another plugin installed by the system. Uninstalled it. Works perfectly.


inotify-tools: add fanotifySupport option

This option allows to build additional utils, fsnotifywait and fsnotifywatch, which use the fanotify kernel API.
The fanotify support is disabled by default so the previous behaviour of the package is not affected.
Description of changes

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

[ ] 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.05 Release Notes (or backporting 22.11 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (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.

@SCOTT-HAMILTON @MarcWeber @pSub Did you have any chance to review the changes?

This pull request has been mentioned on NixOS Discourse. There might be relevant details there:
https://discourse.nixos.org/t/prs-already-reviewed/2617/977

@SuperSandro2000 Are you fine with this new version?


[Bug]: Translation of the liturgical rank for All Souls

What happened?
Alls Souls falls on a Sunday in 2025 and takes precedence over the Thirty First Sunday of Ordinary Time. But the liturgical rank is not translated. It states Commemoration, while it should be Gedachtenis.
(feedback from Steven van Roode)
Version
dev (Edge)
Which browser or browsers are you seeing the problem on? (can select more than one, or N/A if not applicable)
N/A
Relevant error messages
No response

I believe I understand the situation better now, see #252:

All Souls has a logical rank of 7 = Solemnity.
However, it is never displayed as a Solemnity.
It is called a Commemoration: Commemoration of the Faithful Departed*.
Should commemoration be a display_grade value? Or should it display as nothing?
Commemoration is the same word that is used to refer to Memorials that are reduced to optional memorials in partial form during days of Advent between Dec. 17 and Dec. 24, and during Lent.
But perhaps in the case of All Souls day, usage of the term Commemoration is just a case of homonymity?
English, Italian and Latin all work pretty much the same way in all these cases. However, I have learned that in the Netherlands, Dutch does not have a specific term for Commemoration and they just use optional memorial in the case of Memorials that are reduced in rank during Advent and Lent. However, All Souls should NOT be displayed as an optional memorial. Therefore I am led to think that in the case of All Souls, display_grade should indicate that it should not show anything at all.
But in order to indicate that nothing should be displayed we would probably use an empty value for display_grade.
And yet, we are currently using an empty value for display_grade on all liturgical events to indicate that the property is not needed / used.
In order to indicate that an empty value should actually show as an empty value, we should change all other empty display_grade values to a value of null.

Closing as fixed for now.


Use Multi JSON gem instead of requiring explicit 'json' gem dependency

https://github.com/intridea/multi_json
I use YAJL as my json encoder and the multi json gem allows for you to swap any compatible encoder transparently.

Since MultiJson with :pretty => true is now available; Jsonify now uses it. There are no longer dependencies on a specific JSON library.


Add image compressor

added on branch https://github.com/garasijogi/mamoto-website/tree/feature/image-compressor in this commit https://github.com/garasijogi/mamoto-website/commit/c4efe9dcc0e72d487abe0acd1937dc761918fab4


Use ES single redundancy by default

Related to https://github.com/jaegertracing/jaeger-operator/pull/501#discussion_r304001869
Signed-off-by: Pavol Loffay<EMAIL_ADDRESS>

I want to test it first.


Bug reports

Hi there,
Actually there are 2 issues I found in the QAT1.6 driver and the nginx-1.10.0 async patch, I don't know where else to post the issues,  so I have to post them here in QAT Engine project. If this is not a correct place, pls help me moving them into the correct one.

QAT1.6 driver built with OpenSSL 1.1.0 or later will not be loaded due to a 'undefined reference to SHA_Init' problem. After I dig into OpenSSL 1.1.0, I have not found 'SHA_Init', the API is not there anymore. The QAT1.6 driver I used is downloaded from 01org website, the latest one.

For nginx-patch of async use of QAT, the problem is the patch does not support the following style of nginx configuration file: listen 443 ssl;, it only supports the ssl on; directive. And no document mentions this situation, and this really caused me lots of time to resolve the problem.

Hi @InfoHunter
Thanks a lot for reporting these issues.
I have created two separate issues to track them separately: #12  - #13


add bbs montabaur

Hello,
this is the Pull Request for the BBS Montabaur you can find it here: https://www.bbs-montabaur.de

@Sequess12 Pull request merged. Thank you!


Adding new flag for Apply Changes

To reduce the amount of time it takes to apply changes for things that have not changed. This pull request adds a flag to apply changes to skip unchanged products.
This will get the list of pending changes and populate them into deployProducts variable.
If there are no pending changes, we default to not deploying any apps.

@hjaffan Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.

Are you able to proive an example workflow how how (and why) to use these commands? We'd like to verify they are working as expected not just from the CLI level, but how they affect Ops Manager.

@hjaffan Thank you for signing the Contributor License Agreement!

@jtarchie So the main reason behind this additional flag is to only deploy actual changes.
The workflow we are working with is for the PCF Deployment pipeline where we have all tiles being configured prior to applying changes, and then say we add a new tile that did not alter the configurations of the other existing tiles, rather than applying changes to everything all the time, this additional flag will just run the apply changes for that specific product.

@hjaffan, I understand the usage of want. I'm looking for steps to verify.
Can you provide accurate instructions for us to verify that the features works as specified?

manually merged in this commit: https://github.com/pivotal-cf/om/commit/f87449add8c0abaf9537b3fc7ab397d6435958bb


Add Information about Non-Text Contrast

This is a small change that adds information about WCAG 2.1 Non-Text Contrast criteria. Non-text contrast is a new requirement in WCAG 2.1.
Because WCAG 2.1 requires a contrast ratio of 3:1 for this content, it matches the existing AA criteria for large text, so the only changes required was an update to the language.
I also updated the text of the WCAG link from 2.0 to 2.1 as that is where the link points and is the current recommendation.

Merged, thanks!


Update build.gradle

update version to 1.3.1

@Light2288 remember to create the release tag :) thanks!


Fix param error in ByteUtils#equals in java9 #1551

Summary
Fix for issue https://github.com/ClickHouse/clickhouse-java/issues/1551

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.周海水 seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.

@haishui126 thank you for the contribution!
I see some steps have failed. We fixed the issue. Would you please pull latest changes to the branch to verify the fix in CI?
Thank you in advance!

@haishui126 thank you for the contribution! I see some steps have failed. We fixed the issue. Would you please pull latest changes to the branch to verify the fix in CI?
Thank you in advance!

Hi @chernser,
I have merged main into my branch. How can I verify my fix in CI? Workflow requires approval from a maintainer.

@haishui126 Thank you!
I see @mshustov triggered the CI (thank you) and it is passed.


Windows Desktop under ASP.NET apps?

It's not clear why Windows Desktop technologies are under the ASP.NET app node, in the same way, there is no option in the Azure portal to create AppInsights resources for Desktop. Why do we need to select ASP.Net?
AppCenter does not support Desktop apps, and HockeyApp is being deprecated. How should I configure telemetry for my client app?

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

ID: 516c83d5-29e4-4594-8431-18e90ada27ea
Version Independent ID: 92179854-8188-dd7f-ae7b-0bf738badbcb
Content: Monitoring usage and performance for Windows desktop apps
Content Source: articles/application-insights/app-insights-windows-desktop.md
Service: application-insights
GitHub Login: @mrbullwinkle
Microsoft Alias: mbullwin

The portal selection options were previously used to light up different experiences in the UI based on what features were supported in the different SDKs. For example, if your SDK didn't support Live Metrics we wouldn't show you a Live Metrics icon on the classic (now retired) overview pane. As the SDKs have gotten much closer to feature parity the product group has moved away from this and your selection at least as of today doesn't really have any impact on your experience in the portal. Even if you selected Java it wouldn't prevent you from instrumenting your .NET application.
I believe in your case it would be fine to select ASP.NET or General depending on which you prefer. Adding @nikmd23 to weigh in on if there is a preferred PG selection for instrumenting desktop/console apps.


Pychromecast is dropping suppport for Python 2

Howdy.
Pychromecast will no longer support python 2, as of next release (because python-zeroconf will drop python 2 support).
I have a slew of minor PR's coming up after the controllers refactor PR (which is ready, by the way :smiley: ) has been merged. After that I humbly suggest that we make python 3.5 the min. requirement for catt, as this is now available for all major OS'es (the new min. requirement for Pychromecast will be 3.4, I'm just more keen on 3.5).

Hello!
I'm generally loath to remove support for things. If Pychromecast removes support for 2, there's not much we can do, but I generally like erring on the site of being compatible. If there's a version of 3 we need, then by all means, we should use it, but we shouldn't go around turning everything into f-strings or whatever just because.
Other than that, I generally agree with you (I'm reviewing #55 now, by the way), although I would like to keep support for 3.4 as my Raspbian doesn't have 3.5 yet and I can imagine many people using catt on a Raspberry Pi.

Min. 3.4 is cool, although raspbian stretch has 3.5, so I'm not sure I understand that argument. But as long as we commit to no longer care about what might not work for <3.4 then I'm happy (no more try except clauses around import statements etc.).

(It may have been a while since I last upgraded my raspi)

@skorokithakis Please consider making a final python2 compatible release, so we can move on. As for #73, I'm honestly reluctant to invest time in fixing this myself, as I plan to completely rework the server script (I want catt to spawn an independent process that automatically dies when the cc has stopped/finished playing). If this pans out, I also intend to extend this further, by implementing #46.

@theychx Certainly, I can release now. We're sorted for all the py2 compatible things we wanted to release, right?
About #73, I've been meaning to retest, but I'm kind of blocked because catt can't locate my Chromecast. I'll debug that when I have some time and try to fix it.

Released 0.5.5 and added README information.

We're sorted for all the py2 compatible things we wanted to release, right?

Yep. I'll make a PR that removes py2 compat code after you've made the release.


adding an event on interpreted procs inbound network activity

What type of PR is this?

Uncomment one (or more) /kind <> lines:

/kind bug

/kind cleanup

/kind documentation

/kind tests

/kind feature

Any specific area of the project related to this PR?

Uncomment one (or more) /area <> lines:

/area commands

/area pkg

/area events

What this PR does / why we need it:
this PR triggers rule interpreted procs inbound network activity
Which issue(s) this PR fixes:

Fixes #151
Special notes for your reviewer:

[APPROVALNOTIFIER] This PR is NOT APPROVED
This pull-request has been approved by: h4l0gen
Once this PR has been reviewed and has the lgtm label, please assign leogr for approval. For more information see the Kubernetes Code Review Process.
The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@leogr please give your thoughts on InboundConnection helper.

Hey @leogr, thanks for your valuable review, I will look into it.

Hey @leogr, I made all proposed changes. Please take a look again, whenever you find time.
Thank you!

LGTM label has been added.  Git tree hash: 92bbfadacc65253f52074aa7f06ae3beb2796859

[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: h4l0gen, leogr
The full list of commands accepted by this bot can be found here.
The pull request process is described here

Needs approval from an approver in each of these files:

OWNERS [leogr]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment


error: Microsoft Visual C++ 14.0

Hi, I have this problem when I use python setup.py develop command. Is this error shows that I don't install visual studio or someting?

Same problem and I've confirmed several times that I have Microsoft Visual C++ 14.0

So I guess that's not the problem. Does this have to run on Linux?

Same problem and I've confirmed several times that I have Microsoft Visual C++ 14.0

So I guess that's not the problem. Does this have to run on Linux?

Same problem and I've confirmed several times that I have Microsoft Visual C++ 14.0

So I guess that's not the problem. Does this have to run on Linux?

Hi, I have not solve the problem until now. And I think it is not running on Linux because there are some examples which run on windows. However, I don't know how they do. Good luck


[init] Reference flink-shade, initialize the project.

Ah... I used merge...

https://github.com/apache/incubator-paimon-shade/blob/1522477a1c910a4212bdc0aa0540542089b6a689/.asf.yaml#L23-L26
It is because this is the first submission, so there is no limit?


Implement Pool Allocator for StateNodes and Rename arena.c/h To allocation.c/h

When pruning branches, it would be nice to reuse the memory we allocated for the nodes on the branch.
We can do a pool allocator to do just this, and it will be a billion times faster than free(void *block) because free isn't free.
If anybody else wants to implement it, here is a resource I still need to read.
https://www.gingerbill.org/article/2019/02/16/memory-allocation-strategies-004/
It's not hard to implement at all. I want to make sure that it is done in my preferred API

Did this just now


Throw a handleable native Javascript error when RecordNotFound is thrown by query engine

Problem
For CRUD actions in Prisma client, such as .update() or .delete(), if the record does not exist an error is thrown by the query engine, but it is not easily handleable. ex)
Error for binding '0': RecordNotFound("Record to delete does not exist.")

One must check error.detail or error.code to determine if this was a simple record not found issue or something else.
Suggested solution
It would be helpful for Prisma client to catch this scenario and throw a native JS error to is more easily handleable, like RecordNotFoundError extends Error.
Alternatives
Return null instead of throwing
Additional context
Related issues:

https://github.com/prisma/prisma/discussions/4552
https://github.com/prisma/prisma/issues/4072

Something that came to mind for me earlier is for update/delete, if the record does not exist an error is thrown. But for get, the default behavior is to return null instead of throwing an error. You must enable rejectOnNotFound() when instantiating the prisma client to change the behavior for get().
Perhaps update/delete should follow / be added to this setting group to stay consistent.

Closing as duplicate of #5040 and this specific one is also opened as #4072 as you have mentioned.
rejectOnNotFound doesn't make sense for update/delete because we will always throw an error here when record is not found as opposed to null.
The problem here is really bad error we throw and we plan to rework errors.


Explicitly state bazel version support

Is your feature request related to a problem? Please describe.
I had a hard time trying to build grpc from sources. A lot of error messages that seemed to lead nowhere. In the end, it turned out that it was just that the bazel configuration for the most recent bazel version 2.1.4 was missing.
Describe the solution you'd like
It would be nice to explicitly state the required bazel version range in the docs. Yes, there is a debug message in the build saying that no configuration for bazel 2.1.4 could be loaded, but I underestimated how bad that is. All my problems disappeared after installing bazel 1.0.0 (and Wheel in the Python 2.7 that came with it -- I only had Python 3.7).

We've already addressed this using bazel itself: if you rely on a normal distribution of bazel, we have a hijack of its invocation done automatically using our own settings: https://github.com/grpc/grpc/blob/master/tools/bazel
Obviously, we don't want to override things on a global scope if you include gRPC into your own project, but when building the repository only, this override should happen automatically:
~/sources/grpc (master)$ bazel
INFO: Running bazel wrapper (see //tools/bazel for details), bazel version 1.0.0 will be used instead of system-wide bazel installation.
Starting local Bazel server and connecting to it...
                                                           [bazel release 1.0.0]


Generate docs with go generator

It is now possible to generate provider docs using the https://www.terraform.io/docs/registry/providers/docs.html#generating-documentation generator and fields embedded in the provider.
Can we generate all of our documentation identically in this way?
The generator is noted to have some weakness handling deep structures.
Some example repositories using this method:

https://registry.terraform.io/providers/hashicorp/boundary/latest/docs
https://registry.terraform.io/providers/paultyng/unifi/latest/docs
https://registry.terraform.io/providers/paultyng/sql/latest/docs

The draft pull request https://github.com/equinix/terraform-provider-metal/pull/15 created at equinix/terraform-provider-metal has been closed without resolution due to the complexity of migrating that work to this repository. Any related work must be recreated. Relevant information from the conversation is linked below:
_https://github.com/equinix/terraform-provider-metal/pull/15#issuecomment-750300896_

Have a look at this thread, https://github.com/tinkerbell/terraform-provider-tinkerbell/pull/20#discussion_r542100422 and this commit https://github.com/tinkerbell/terraform-provider-tinkerbell/commit/1d2377da4208ffc773fe6738b3ff2d08c3c9a317.
I think this provides a cleaner approach to introducing this bit of tooling without adding dozens of new requirements.

The provider will likely need to adopt documentation generation in a major version release, because we cannot generate docs in the current structure where files are prefix with equinix_: (https://github.com/hashicorp/terraform-plugin-docs/issues/347).  Our current file naming convention does not align with the standards proposed by Hashicorp and implemented in the generator.
Rather than fork the generator or do extra workarounds to rename files after generation, we should align with the standards that are implemented by the generator and that are used by other providers; that means breaking existing docs pages because there's no way to redirect those old URLs.


fix:#277 Add message while deleting item

Please check if the PR fulfills these requirements

[x] The commit message follows our guidelines
[ ] Tests for the changes have been added (for bug fixes/features)
[ ] Docs have been added / updated (for bug fixes / features)

What kind of change does this PR introduce?
Adds toast message when CRUD item is deleted.

@bielsky0 It would be good to also adjust generator


Resolving deltas: 100% (54/54), done.
Checking connectivity... done.
Tapped 1 formula (3,470 files, 13.4M)
==> Caveats
google-cloud-sdk is installed at /opt/homebrew-cask/Caskroom/google-cloud-sdk/latest/google-cloud-sdk. Add your profile:

      for bash users
        source '/opt/homebrew-cask/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/path.bash.inc'
        source '/opt/homebrew-cask/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/completion.bash.inc'

      for zsh users
        source '/opt/homebrew-cask/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/path.zsh.inc'
        source '/opt/homebrew-cask/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/completion.zsh.inc'

      for fish users
        set fish_user_paths /opt/homebrew-cask/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/bin
        set -x MANPATH /opt/homebrew-cask/Caskroom/google-cloud-sdk/latest/google-cloud-sdk/help/man /usr/local/share/man /usr/share/man /opt/x11/share/man

        Run fish_update_completions to generate completions for fish based on the man pages

==> Downloading https://dl.google.com/dl/cloudsdk/release/google-cloud-sdk.tar.gz
/usr/bin/curl -fLA Homebrew-cask v0.51+ (Ruby 2.0.0-645) https://dl.google.com/dl/cloudsdk/release/google-cloud-sdk.tar.gz -C 0 -o /Library/Caches/Homebrew/google-cloud-sdk-latest.tar.gz.incomplete
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 3990k  100 3990k    0     0  1645k      0  0:00:02  0:00:02 --:--:-- 1645k
==> No checksum defined for Cask google-cloud-sdk, skipping verification
==> Running installer script google-cloud-sdk/install.sh
==> Welcome to the Google Cloud SDK!

I suspected it might be asking a question about collecting usage metrics or not but the appropriate flags are passed to the installer script. I added --quit to ensure it would pick up any other defaults but no dice either. It just sits there.

Please always follow the reporting bugs guide. To do so, edit the top post and then comment after this one so I can check back.
Closing in the meantime, because a number of people never report back and it’s useless to keep the issue open in that case and without all the required information.

Updated

Thank you. Currently updating my VM so I can try this.

Fixed in https://github.com/caskroom/homebrew-cask/commit/81604d911c0d77e256d68abb317888b1bb6f5d00.

I'm still having the same issue.

Did you brew update?

Yes :smile:


Fix attribute lookup of standard library names

The attributes were accidently being converted to NameNode instead. The tests weren't picking this up because the names were available so were being looked up successfully.
Fixes #5536

I've confirmed this fix resolves my local reproduction.

This fixes my similar reproducer in some aspects (I have a bunch of cases where typing.* are used in class definition subscripts), but then I hit:
[ 8/10] Cythonizing mesonbuild/interpreterbase/decorators.py

Error compiling Cython file:
------------------------------------------------------------
...
        if disabler and not ret.found():
            return Disabler()
        return ret
    return T.cast('TV_func', wrapped)

@dataclass(repr=False, eq=False)
 ^
------------------------------------------------------------

mesonbuild/interpreterbase/decorators.py:114:1: Compiler crash in AnalyseExpressionsTransform

File 'Nodes.py', line 397, in analyse_expressions: StatListNode(decorators.py:14:0)
File 'Nodes.py', line 397, in analyse_expressions: StatListNode(decorators.py:115:0)
File 'Nodes.py', line 5147, in analyse_expressions: PyClassDefNode(decorators.py:115:0,
    name = 'permittedKwargs')
File 'ExprNodes.py', line 636, in analyse_expressions: SimpleCallNode(decorators.py:114:0,
    analysed = True,
    result_is_used = True,
    use_managed_ref = True)
File 'ExprNodes.py', line 6041, in analyse_types: SimpleCallNode(decorators.py:114:0,
    analysed = True,
    result_is_used = True,
    use_managed_ref = True)
File 'ExprNodes.py', line 6799, in analyse_types: GeneralCallNode(decorators.py:114:10,
    is_called = 1,
    result_is_used = True,
    use_managed_ref = True)
File 'ExprNodes.py', line 5933, in analyse_as_type_constructor: GeneralCallNode(decorators.py:114:10,
    is_called = 1,
    result_is_used = True,
    use_managed_ref = True)
File 'ExprNodes.py', line 2125, in analyse_as_type: NameNode(decorators.py:114:1,
    cf_maybe_null = True,
    is_name = True,
    name = 'dataclass',
    result_is_used = True,
    use_managed_ref = True)

Compiler crash traceback from this point on:
  File "/home/eschwartz/.local/lib/python3.10/site-packages/Cython/Compiler/ExprNodes.py", line 2125, in analyse_as_type
    entry = Builtin.get_known_standard_library_entry(entry.known_standard_library_import)
  File "/home/eschwartz/.local/lib/python3.10/site-packages/Cython/Compiler/Builtin.py", line 618, in get_known_standard_library_entry
    mod = get_known_standard_library_module_scope(module_name)
  File "/home/eschwartz/.local/lib/python3.10/site-packages/Cython/Compiler/Builtin.py", line 597, in get_known_standard_library_module_scope
    entry.known_standard_library_import = "%s.%s" % (module_name, name)
UnboundLocalError: local variable 'name' referenced before assignment

Source file: https://github.com/mesonbuild/meson/blob/7824ff80dcaa457706a4f762e976383e6bd03daf/mesonbuild/interpreterbase/decorators.py#L115


Ordinal Index Snapshot Link

We need Ordinal Index File Snapshot to reduce the indexing process.
We can download the snapshot file.
There may be several snapshot files as along the index flag.
It is very similar to the several blockchain node sync mode.

Doubt if you'll see an official team-provided snapshot but there is a community-provided index file for download.
http://ordstuff.info

But I think it should be verify officially such as official github or any other social.

We've thought about this and unfortunately the database is not built deterministically. So there is no way to provide a checksum/hash that will be the same across systems. There have been proposals to create a consensus hash https://github.com/ordinals/ord/issues/2574 and https://github.com/hirosystems/ordhook/issues/223, I've commented on both but the proposer has never answered. If you would like to champion this proposal and formalize it more, I'm happy to help and review PRs though!