1.1.2 (x64) installer is broken

Describe the bug
Deploying package: Microsoft.WindowsAppRuntime.1.1_1002.543.1943.0_x64__8wekyb3d8bbwe
Package deployment result : 0x80073cfb
https://task.ms/40349590
Steps to reproduce the bug
Try installing 1.1.2 (x64)
Expected behavior
No response
Screenshots
No response
NuGet package version
1.1.2
Packaging type
No response
Windows version
Windows 10 version 21H2 (19044, November 2021 Update)
IDE
No response
Additional context
No response

Happens when 1.1.1 was installed through the previous installer.
You can try to remove all the previous installed Windows App SDK components with
get-appxpackage -AllUsers micro*win*appruntime* | remove-appxpackage -AllUsers
but even this might fail because of dependencies between the packages.
In the end i had a client machine where i had to remove the packages manually one by one until this was cleaned up. I hope that in the future there is a simple way to uninstall a previous version, because the current process is horrendous.

@DrusTheAxe @gabbybilka Was the wrong runtime installer uploaded? Can confirm it's trying to install 1.1.1.

What this error seems to indicate is that there's a difference between the package provided by the installer and the package provided by the store, and you already have the updated store version installed. You can check this in powershell. Run
Get-AppxPackage Microsoft.WindowsAppRuntime.1.1
You should see something like this:
Name              : Microsoft.WindowsAppRuntime.1.1
Publisher         : CN=Microsoft Corporation, O=Microsoft Corporation, L=Redmond, S=Washington, C=US
Architecture      : X64
ResourceId        :
Version           : 1002.543.1943.0

The version above is the correct version for 1.1.2 (The MSIX package is versioned with an encoded timestamp instead of patch number). If I then run the installer, I see the following error message:

ErrorMessage: Deployment of package Microsoft.WindowsAppRuntime.1.1_1002.543.1943.0_x64__8wekyb3d8bbwe was blocked because the provided package has the same identity as an already-installed package but the contents are different. Increment the version number of the package to be installed, or remove the old package for every user on the system before installing this package.One or more install operations failed. Result: 0x80073cfb

The store unpacks & repacks contents of the MSIX as part of submission, and we've had some challenges in the past with slight differences between the version we put in the installer and the version that ultimately shows up in the store causing the install stack in Windows to believe they're not quite the same (but they should be). We're investigating whether this is the case.
Ben

I can confirm that my previous comment is accurate. The phone package ID changed (the store helpfully updates this) but we didn't update it from the 1.0 package version. So the store-serviced package doesn't match the WinAppSDK installer's version. The phone identity is an anachronism at this point, but the Windows install stack still recognizes it as a meaningful difference.

I hope we agree showing 1.1 to the dev/user is a bug.

A visual studio project updated to 1.1.2 does not run with the store updated version! It keeps insisting on that the required version is missing.

I hope we agree showing 1.1 to the dev/user is also a bug.

@riverar, can you clarify what you mean here?
@Balkoth, We just approved the fix for this in shiproom today, so this will be in the next servicing update. I understand this is a significant nuisance. To work around it in the meantime, uninstall all App SDK 1.1 packages & dependencies, then run the 1.1.2 installer. Once you have the 1.1.2 version of the MSIX packages installed, the store updater won't swap it out for the store version, and the other deployment behaviors will work as expected (insatller, VS F5, etc.).

@riverar, can you clarify what you mean here?

Users are trying to install the 1.1.2 Windows App Runtime. It shouldn't say or try to deploy Microsoft.WindowsAppRuntime.1.1[...].

This issue was fixed and released in Windows App SDK 1.1.3 - check out the release notes and NuGet to try it out 🎉


What should be the sound path?

I have multiple voice recordings. I need to extract features from them and save them as a csv file. What should I do from the scratch? Do I need to select the path?

Please check the wiki (https://github.com/tyiannak/pyAudioAnalysis/wiki/3.-Feature-Extraction). Audio data folder is an argument in most of the cases


travis!

https://travis-ci.org/mindw/mako/builds/77541154
The following image (svg or png) should be embedded into the readme:
https://img.shields.io/travis/zzzeek/mako.svg

thanks!


test('should be skipped when running') throws an error when running jest.

🐛 Bug Report
As of 23.0.0 and above, a test that contains a description without an assertion body test('should skip') throws an error when running Jest.
To Reproduce
Package Run Command
cross-env NODE_ENV=test jest --silent --config jest.config.js
Config for Jest
module.exports = {
  collectCoverage: true,
  collectCoverageFrom: [
    '**/lib/**.{js}',
    'index.js',
  ],
}

Create a  single test and run jest

// index.test.js

describe('index()', () => {
  test('should skip this test because it has no body')
})

Watch jest fail

Expected behavior
Before 23.0.0 a test that had no body would automatically be skipped and would not throw an error in the test report.
Link to repl or repo (highly encouraged)
no link as of yet, but happy to if further investigation is required
Issues without a reproduction link are likely to stall.
Run npx envinfo --preset jest
Paste the results here:
System:
    OS: macOS High Sierra 10.13.4
    CPU: x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz
  Binaries:
    Node: 9.11.1 - ~/.nvm/versions/node/v9.11.1/bin/node
    Yarn: 1.7.0 - /usr/local/bin/yarn
    npm: 6.1.0-next.0 - ~/.nvm/versions/node/v9.11.1/bin/npm
  npmPackages:
    jest: ^23.1.0 => 23.1.0

Just a note that I did try every version upwards of 23.0.0 and they all had the same effect. :+1:

This was one of the breaking changes in v23. Check out the CHANGELOG.md and preferably the [blog post](https://facebook.github.io/jest/blog/2018/05/29/jest-23-blazing-fast- delightful-testing.html) :)


fix(paeckchen-cli): respect context.config

the cli should use the context.config instead of the created own config,
because the core will extend the configuration with the config file
settings and defaults
ISSUES CLOSED: #117

Coverage remained the same at 100.0% when pulling 00d0379abec7db08977de27479e60240528212e1 on cli/out-file into 8bddd7e6d4b205d1c8aa2561a33fdedfa111d42e on master.


[FLINK-31551] Add support for CrateDB

Add support for CrateDB

retest this please

@eskabetxe When you have the time, please take another look.

@eskabetxe FYI, I've found a trick to choose the CrateDBDialect based on the jdbc:crate:// url provided by the user, but internally change it to jdbc:postgresql:// and therefore use the vanilla PostgreSQL JDBC driver. Therefore, no dedicated RowConverter is need, so I've reverted the corresponding refactoring.

Checking the test failure because of different Timezone (UTC vs Europe/Athens that I have locally)

Merged master and fixed timestamp related tests by using UTC timezone for the container and the tests.

@eskabetxe Could you take a look to finish up this PR please?

@MartijnVisser done!

apologies, I think you need to rerun the CI as I've pushed one more commit.

Asked because I see that jobs are cancelled

That's because the run for Flink 1.17.0 on Java 11 already failed, so then it cancels all others run too

do we need crate's dependency on jna or can we exclude it?

We can exclude it.

thx @snuyanzin, excluded the jna dependency from crate-jdbc.

@MartijnVisser @snuyanzin I've rebased again, can you please run ci again?
It would be great to merge it if everything passes, thx.

Thanks for addressing comments
it looks ok from my side
Thanks for review @eskabetxe @libenchao, please add anything if you have something not covered

@snuyanzin I don't have further comments. There is one thing we can do is to create a Jira about the translation for newly added docs about CrateDB.

thanks for the contribution @matriv
thanks for the review @libenchao , @eskabetxe
i'm about to merge it this weekend


GitHub Actions: Cache Maven dependencies

What does this PR (Pull Request) do?

This PR fixes building Traffic Router in GitHub Actions by caching Maven dependencies. It looks like GitHub Actions doesn't rate-limit downloads the same way if you use caching.
[x] This PR is not related to any Issue

This will speed up building TR as well, which always takes the longest of any component to build on GitHub Actions
Which Traffic Control components are affected by this PR?

CI tests

What is the best way to verify this PR?

Check the Traffic Router GitHub Actions result, since GHA is the only place experiencing rate limiting.
If this is a bug fix, what versions of Traffic Control are affected?

master (cd75524e6e)

The following criteria are ALL met by this PR

[x] Not reproducible outside of GitHub Actions since GitHub Actions is the thing rate-limiting our TR-building action's request
[x] Project components are unchanged, no documentation necessary
[x] An update to CHANGELOG.md is not necessary
[x] This PR includes any and all required license headers
[x] This PR does not include a database migration
[x] This PR DOES NOT FIX A SERIOUS SECURITY VULNERABILITY (see the Apache Software Foundation's security guidelines for details)

We should also be doing this for TP's node_modules dependencies, btw.

I got on this topic last night and threw a few more things in the mix that may aid this job:
https://github.com/MylesBock/trafficcontrol/runs/1129862202
Performs roughly the same caching of maven artifacts, adds a little finegrained control over settings.xml, but also tweaks how traffic_router is built by limiting the number of artifact download and build threads

Sorry, I didn't know anyone else was working on it (and should have made a GitHub issue before submitting a PR to fix). If you aren't there already, feel free to join #traffic_router on the Apache Traffic Control slack (there's an invite link in the docs). If think it can be improved further, though, feel free to open a PR.
I also opened #5042 to document that we don't cache NPM dependencies.


Added sudo indicator to the Powerline-Multiline Theme

If the user is currently in a valid sudo session (sudo currently does not require a password), then the last part of the left prompt will use a different color (orange). This gives an indication to the user that sudo commands will not require a password at the moment. One example for this might be that the user is reminded to run a sudo -k to terminate the current sudo session before stepping away from the screen.
This is what it looks like:

@tswicegood @edubxb @ifosch - would like to get your opinion on that. Let me know what you think.

Like the idea, but I prefer to put the indication in other place, some suggestions:

in the username section adding some descriptive icon/symbol/character/text to indicate it
another minor "disruptive" solution should be change the "prompt symbol" (❯) color.

What do you thing?

With regards to your other question - sure, another location would be perfectly fine. Do you have an icon in mind?
Changing the last prompt character would look like that:

One concern with that is that it might clash with the exit code display (last line in the screenshot).

We could change the background color of the user name section - how about that?

Could suit better, I'm thinking into remove the color change when logging via SSH, the hostname is added to the usename, indicating a remote connection, to avoid confusion.

I like the idea.  I think the full username is a better option.  Then there's one local, one privileged local, one remote.  Maybe one privileged remote too?

Thanks for the feedback, I'll give that a try and update the PR...

OK, made some changes - the color used for the username on the right side of the prompt is changed if the session is within the sudo timeout.
I haven't changed the way SSH is indicated, it's using the same colors as local access, and is still adding the lock icon and attaching the host name. Here's what it looks like...
Local access:

SSH access:

Let me know what you think...

@tswicegood @edubxb Any feedback - what do you think about the above?

+1

Cool - thanks for the feedback. I've merged this for now, we can keep adjusting it if we have more/better ideas.


[BUG] Error prompt message

Describe the bug

To Reproduce
Steps to reproduce the behavior:

Launch harvester, select Join an exiting Harvester cluster option
When entering token, the following prompt message is wrong

Expected behavior

Log

Environment:

Harvester ISO version:  master-388aa82c-head
Installation Mode: ISO
Underlying Infrastructure (e.g. Baremetal with Dell PowerEdge R630):

Additional context
Add any other context about the problem here.

Validated on v0.2.0-rc1
Verified fixed


beta docs don't display in Safari

None of the documentation pages are displaying in Safari (Version 8.0.6 (10600.6.3))
e.g. http://beta.semantic-ui.com/kitchen-sink.html displays the left black sidebar with navigation, but none of the linked pages display content, which is blank.
Displaying as expected in Firefox, Chrome.
Looking at the compatability for it says Safari 6. Does that mean only version 6 and not 6+?

@terraling Thanks, just realized some flexbox rules in docs are missing vendor prefixes. Will fix

Fixed with https://github.com/Semantic-Org/Semantic-UI-Docs/commit/07a5196fd72e64aa2c31479dd0179836a8863f95 and deployed


[improvement] Support @map and @@map

Thank you for this plugin.
Is there a chance that you could support the @map and @@map instructions, as defined here in the Prisma documentation? Where my Prisma file contains @map, the plugin reformats the file like this:
model users {
  id                        Int                         @id @default(autoincrement()) @map("ID")
  username                  String                      @unique(map: "username") @db.VarChar(25)
  password                  String                      @db.VarChar(40)
  allowSharing              Boolean                     @default(true) @map("AccepterPartage")
}

where I would expect something like:
model users {
  id                        Int                         @id @default(autoincrement())             @map("ID")
  username                  String                      @unique(map: "username") @db.VarChar(25)
  password                  String                      @db.VarChar(40)
  allowSharing              Boolean                     @default(true)                            @map("AccepterPartage")
}

Hey @bperel! This plugin is built on top of @prisma/prisma-fmt-wasm, which is built from the prisma-fmt lib from the prisma-engines.
I suggest you to forward your request there.


Feature/upgrade to api 25

Current coverage is 0.00% (diff: 100%)

Merging #137 into develop will not change coverage

@@           develop   #137   diff @@
=====================================
  Files            1      1
  Lines           36     36
  Methods          0      0
  Messages         0      0
  Branches         0      0
=====================================
  Hits             0      0
  Misses          36     36
  Partials         0      0

Powered by Codecov. Last update 229c2f3...90c067f


Feature: Shields made with Olvite

Problem (Optional)
that way shields can be make in the aether
Feature
Shields made with Zanite
Other Solutions
No response
Mod Version
any
Additional Information
No response

Shields are craftable with Olvite as of b2.2.0


Some entity prototypes have components added or modified during initialization.

This is a partial list of entity prototypes that need to be updated (though in some instances, the system/component itself may need to be fixed). There are several more not on this list, but those should get fixed by #10274. Currently the test added in #10274 just explicitly ignores the prototypes on this list.
A brute force way to figure out how to correct some of these prototypes is to just spawn them into an empty uninitialized map, saving the map, and then reading the map yaml.

[ ] Several weapons/staffs modify the BasicEntityAmmoProvider's  count field

[ ] WeaponProtoKineticAccelerator
[ ] various WeaponStaff..... prototypes
[ ] various WeaponWand..... prototypes

[ ] GlowstickBase modifies component on spawn: Item. Modified fields: heldPrefix
[ ] Thruster modifies component on spawn: AmbientSound. Modified fields: enabled
[ ] Gyroscope modifies component on spawn: AmbientSound. Modified fields: enabled
[ ] RemoteSignaller gains a component on spawn: SignalTransmitter
[ ] A bunch of entities gain ContainerContainer on spawn:

[ ] filingCabinet, filingCabinetTall, filingCabinetDrawer
[ ] WeaponLauncherChinaLake, WeaponLauncherRocket, WeaponLauncherMultipleRocket
[ ] WeaponImprovisedPneumaticCannon
[ ] MagazinePistolSubMachineGunTopMounted
[ ] ClusterBang
[ ] LauncherCreamPie
[ ] Crematorium
[ ] LightReplacer
[ ] PortableScrubber
[ ] DisposalHolder
[ ] AMEController
[ ] JanitorialTrolley
[ ] Vaccinator
[ ] ClothingHeadHatChef
[ ] CloningPod
[ ] MachineFrame
[ ] MedicalScanner
[ ] KitchenMicrowave

[ ] MultipleTools (JawsOfLife, SyndicateJawsOfLife, PowerDrill, Omnitool) modifies component on spawn: Tool. Modified fields: useSound
[ ] PortableScrubber modifies component on spawn: Physics. Modified fields: canCollide
[ ] ParticleAcceleratorControlBox modifies component on spawn: ApcPowerReceiver. Modified fields: powerLoad
[ ] Atmos devices enable themselves on init?

[ ] GasPressurePump modifies component on spawn: GasPressurePump. Modified fields: enabled
[ ] GasVolumePump modifies component on spawn: GasVolumePump. Modified fields: enabled
[ ] GasFilter modifies component on spawn: GasFilter. Modified fields: enabled
[ ] GasMixer modifies component on spawn: GasMixer. Modified fields: enabled

[ ] HospitalCurtainsOpen modifies component on spawn: Physics. Modified fields: canCollide
[ ] CargoPallet modifies component on spawn: Physics. Modified fields: canCollide
[ ] ParticlesProjectile modifies component on spawn: Fixtures. Modified fields: fixtures
[ ] FloorDrain gains a component on spawn: Fixtures
[ ] Organs modify solutions or add a solution container manager component:

[ ] OrganHumanLungs modifies component on spawn: SolutionContainerManager. Modified fields: solutions
[ ] OrganRatLungs modifies component on spawn: SolutionContainerManager. Modified fields: solutions
[ ] SentientSlimeCore gains a component on spawn: SolutionContainerManager
[ ] OrganSlimeLungs modifies component on spawn: SolutionContainerManager. Modified fields: solutions
[ ] OrganVoxLungs modifies component on spawn: SolutionContainerManager. Modified fields: solutions
[ ] OrganAnimalLungs gains a component on spawn: SolutionContainerManager

[ ] Floodlight modifies component on spawn: Physics. Modified fields: canCollide
[ ] HolosignWetFloor gains a component on spawn: Fixtures
[ ] HeadSkeleton modifies component on spawn: Vocal. Modified fields: action
[ ] DeployableBarrier modifies component on spawn: Physics. Modified fields: bodyType
[ ] CrateArtifactContainer modifies component on spawn: PlaceableSurface. Modified fields: isPlaceable
[ ] Machine Linking:

[ ] CloningPod gains a component on spawn: SignalReceiver
[ ] C4 modifies component on spawn: SignalReceiver. Modified fields: inputs
[ ] Poweredlight & inheritors gains a component on spawn: SignalReceiver
[ ] ComputerCloningConsole modifies component on spawn: SignalTransmitter. Modified fields: outputs
[ ] GasDualPortVentPump gains a component on spawn: SignalReceiver
[ ] Recycler gains a component on spawn: SignalReceiver
[ ] CargoTelepad gains a component on spawn: SignalReceiver
[ ] ConveyorBelt gains a component on spawn: SignalReceiver
[ ] MedicalScanner gains a component on spawn: SignalReceiver

[ ] A bunch of prototypes gain a tag component:

[ ] FoodBowlBig
[ ] FoodBowlFancy
[ ] FoodCondimentPacket
[ ] FoodCondimentBottle
[ ] FoodCondimentBottleSmall
[ ] Syringe

[ ] A bunch of prototypes modify the tag component (be careful not to override inherited tags)

[ ] EmergencyMedipen
[ ] AntiPoisonMedipen
[ ] SpaceMedipen
[ ] SprayBottle
[ ] DrinkColaCan
[ ] EpinephrineChemistryBottle
[ ] RobustHarvestChemistryBottle
[ ] NocturineChemistryBottle
[ ] EphedrineChemistryBottle
[ ] OmnizineChemistryBottle

[ ] MachineFrame modifies component on spawn: Construction. Modified fields: defaultTarget
[ ] GravityGenerator (Maybe this should actually just be an ignored prototype?)

[ ] modifies component on spawn: AmbientSound. Modified fields: enabled
[ ] modifies component on spawn: ApcPowerReceiver. Modified fields: powerLoad
[ ] modifies component on spawn: PointLight. Modified fields: radius
[ ] modifies component on spawn: AmbientSound. Modified fields: enabled
[ ] modifies component on spawn: ApcPowerReceiver. Modified fields: powerLoad
[ ] modifies component on spawn: PointLight. Modified fields: radius

[ ] the various lathe entities modify materialWhiteList on spawn
[ ] Recycler modifies component on spawn: Fixtures. Modified fields: fixtures
[ ] some ClothingHeadHatHardhat base entity adds item slots & containers on spawn
[ ] All the beakers, MopBucket, JanitorialTrolley, Bucket all modify the drink component solution on spawn
[ ] CargoTelepad modifies component on spawn: Physics. Modified fields: canCollide
[ ] Various doors & airlocks modify fixtures on spawn:

AirlockShuttle, AirlockGlassShuttle, AirlockExternalShuttleLocked, AirlockExternalGlassShuttleLocked, AirlockExternalGlassShuttleLocked, AirlockExternalGlassShuttleLocked, AirlockExternalGlassShuttleEmergencyLocked

[ ] ConveyorBelt modifies component on spawn: Fixtures. Modified fields: fixtures
[ ] flashlight related:

[ ] ClothingHeadHelmetFire modifies component on spawn: Clothing. Modified fields: equippedPrefix
[ ] ClothingHeadHelmetFire modifies component on spawn: Item. Modified fields: heldPrefix
[ ] ClothingHeadHelmetAtmosFire modifies component on spawn: Clothing. Modified fields: equippedPrefix
[ ] ClothingHeadHelmetAtmosFire modifies component on spawn: Item. Modified fields: heldPrefix
[ ] CableTerminal gains a component on spawn: CollideOnAnchor

kitchenmicrowave fixed by #10766

the lathes were fixed with lathe ECS

"All the beakers, MopBucket, JanitorialTrolley, Bucket all modify the drink component solution on spawn" was also fixed in #12390


Default workload identity bindings for deployments that need GCP permissions

I've found quite a few deployments don't work properly due to lack of GCP permissions, including:

profiles manager

2020-06-23T08:51:18.266Z        ERROR   controller-runtime.controller   Reconciler error        {"controller": "profile", "request": "/default-profile", "error": "googleapi: Error 403: Permission iam.serviceAccounts.getIamPolicy is required to perform this operation on service account<EMAIL_ADDRESS>forbidden"}
github.com/go-logr/zapr.(*zapLogger).Error
        /go/pkg/mod/github.com/go-logr/zapr@v0.1.0/zapr.go:128
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler
        /go/pkg/mod/sigs.k8s.io/controller-runtime@v0.2.0/pkg/internal/controller/controller.go:218
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem
        /go/pkg/mod/sigs.k8s.io/controller-runtime@v0.2.0/pkg/internal/controller/controller.go:192
sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).worker
        /go/pkg/mod/sigs.k8s.io/controller-runtime@v0.2.0/pkg/internal/controller/controller.go:171
k8s.io/apimachinery/pkg/util/wait.JitterUntil.func1
        /go/pkg/mod/k8s.io/apimachinery@v0.0.0-20190404173353-6a84e37a896d/pkg/util/wait/wait.go:152
k8s.io/apimachinery/pkg/util/wait.JitterUntil
        /go/pkg/mod/k8s.io/apimachinery@v0.0.0-20190404173353-6a84e37a896d/pkg/util/wait/wait.go:153
k8s.io/apimachinery/pkg/util/wait.Until
        /go/pkg/mod/k8s.io/apimachinery@v0.0.0-20190404173353-6a84e37a896d/pkg/util/wait/wait.go:88

pipelines ui, visualization server deployments
default-editor (and default-viewer, maybe later) KSA in user namespace (needed by pipeline runs, tensorboard instances)

/cc @jlewi
I think we should bind workload identity with these KSAs by default.
Proposal
Add workload identity binding for

profiles manager - admin GSA
pipelines ui, visualization server - user GSA

default-editor will be automatically bound to user GSA when profiles manager works properly.
@jlewi I can implement this, thoughts?

/assign @Bobgy

@Bobgy Isn't the profiles-manager already bound to a GSA?

I looked at one of the auto deployments
It looks like profiles manager is using KSA: serviceAccount: profiles-controller-service-account
Which doesn't have a GSA
kubectl -n kubeflow get serviceAccount -o yaml profiles-controller-service-account
apiVersion: v1
kind: ServiceAccount
metadata:
  annotations:
    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"v1","kind":"ServiceAccount","metadata":{"annotations":{},"labels":{"kustomize.component":"profiles"},"name":"profiles-controller-service-account","namespace":"kubeflow"}}
  creationTimestamp: "2020-06-23T11:45:21Z"
  labels:
    kustomize.component: profiles
  name: profiles-controller-service-account
  namespace: kubeflow
  resourceVersion: "3510"
  selfLink: /api/v1/namespaces/kubeflow/serviceaccounts/profiles-controller-service-account
  uid: 04de24e6-b547-11ea-8696-42010a800149
secrets:
- name: profiles-controller-service-account-token-bvcxp

I think this is a bug. If the profiles manager isn't bound to any GSA it won't be able to attach GSA's to KSAs in newly provisioned namespaces.
Looking at a v1 deployment it looks like it is bound to the admin account
kubectl --context=kf-v1-0210 -n kubeflow  get serviceaccount -o yaml profiles-controller-service-account
apiVersion: v1
kind: ServiceAccount
metadata:
  annotations:
    iam.gke.io/gcp-service-account<EMAIL_ADDRESS>    kubectl.kubernetes.io/last-applied-configuration: |
      {"apiVersion":"v1","kind":"ServiceAccount","metadata":{"annotations":{},"labels":{"app.kubernetes.io/component":"profiles","app.kubernetes.io/instance":"profiles-v1.0.0","app.kubernetes.io/managed-by":"kfctl","app.kubernetes.io/name":"profiles","app.kubernetes.io/part-of":"kubeflow","app.kubernetes.io/version":"v1.0.0","kustomize.component":"profiles"},"name":"profiles-controller-service-account","namespace":"kubeflow"}}
  creationTimestamp: "2020-02-10T19:12:36Z"
  labels:
    app.kubernetes.io/component: profiles
    app.kubernetes.io/instance: profiles-v1.0.0
    app.kubernetes.io/managed-by: kfctl
    app.kubernetes.io/name: profiles
    app.kubernetes.io/part-of: kubeflow
    app.kubernetes.io/version: v1.0.0
    kustomize.component: profiles
  name: profiles-controller-service-account
  namespace: kubeflow
  resourceVersion: "5691"
  selfLink: /api/v1/namespaces/kubeflow/serviceaccounts/profiles-controller-service-account
  uid: 4c172377-4c39-11ea-86b4-42010a8e01a3
secrets:
- name: profiles-controller-service-account-token-rxm4l

that's true, It was originaly bound by kfctl
We need to bind It by kcc now

Thanks @Bobgy that makes sense; thanks for reporting and fixing this

@Bobgy Lets not close this issue until

kubeflow/manifests#1317 has been cherry-picked onto the 1.1 branch
We have verified in the auto-deployments that the issue is fixed.

@Bobgy Are we going to have to apply the same change as #64 to the auto-deploy script.
https://github.com/kubeflow/testing/blob/637d1cd5fe33d03ee5646380d960fabe8a230d0a/py/kubeflow/testing/create_kf_from_gcp_blueprint.py#L130

The most recent deploy "kf-vbp-0629-571" runs pipelines successfully, but workload identity binding is still not properly setup.
$ k get sa pipeline-runner -o yaml
apiVersion: v1
kind: ServiceAccount
metadata:
  annotations:
    iam.gke.io/gcp-service-account<EMAIL_ADDRESS>  name: pipeline-runner
  namespace: kubeflow
  ...

I'm guessing the change https://github.com/kubeflow/testing/pull/705 didn't make it into the auto deploy. Is there a way we can trigger a manual deploy?

Looked at the tekton task https://kf-ci-v1.endpoints.kubeflow-ci.cloud.goog/tekton/#/namespaces/auto-deploy/pipelineruns/deploy-kf-master-p5sb2, it's using
params:
  - name: revision
    value: gcp_blueprints
  - name: url
    value: 'https://github.com/jlewi/testing.git'
type: git

@jlewi Can you fix this?

This is currently coming from here:
https://github.com/kubeflow/testing/blob/88c153fb7ab84ea08c5ea7cf21fbf0a30b7814d3/test-infra/auto-deploy/manifest/config/pipeline-run-deploy-blueprint-master.yaml#L35

The current auto-deployment was deployed before kubeflow/testing#707 was merged.
gcp-blueprint-master	kf-vbp-0629-3f5	8:28:38.534253	deploy-kf-master-rpgt4	7cfd7bc		gcloud --project=kubeflow-ci-deployment container clusters get-credentials --region=us-central1 kf-vbp-0629-3f5

The next auto-deployment will hopefully have the fix.

Thanks for the heads up! I'll wait for the next one then

This is working properly now. I verified in https://kf-vbp-0630-8f5.endpoints.kubeflow-ci-deployment.cloud.goog/_/pipeline/#/runs/details/c7af3e03-87ab-4a6b-b30c-20d8b9a5a8ea, the tfx taxi sample ran successfully.

I found a problem, I used IAMPolicy for workload identity bindings for kf-user GSA.
However, in multi user mode, profile controller also tries to add additional workload identity bindings to kf-user GSA.
Then, profile controller and KCC controller will periodically overwrite each other's IAM policies.
We should use IAMPolicyMember instead.

@Bobgy Thanks; we will need to cherry-pick this into the 1.0 branch of manifests.

We should verify permissions of notebooks whether this is good.


OPTIONS request being handled and returns 405

Whenever I issue an OPTIONS request to my controller route, 3 candidates are pre-selected but then none match, because they're PUT, DELETE, PATCH and not options, obviously.
Why is the versioning getting in the way of an OPTIONS request?
I get this in the output:
Microsoft.AspNetCore.Mvc.Routing.DefaultApiVersionRoutePolicy:Information: Multiple candidate actions were found, but none matched the requested service API version '1'
PS: I've debugged into the source and basically got into ApiVersionActionSelector.EvaluateActionConstraints and verified what I mentioned above.
Thanks in advance!

I've looked into this more. It's difficult to simulate your conditions without a repro. Thus far, I've been unable to recreate your scenario. I'm able to get CORS working just fine. Your registration of middleware seems correct, but you don't need to muck with the API versioning middleware. Currently, all it does is register the API versioning feature into the pipeline, which simply needs to occur any time before UseMvc(). This is automatically wired-up for you. For manually calling UseApiVersioning to have the intended effect, you must register the API versioning services with options.RegisterMiddleware = false; the default is true. You're not expected to ever have to mess with this except for the most advanced scenarios.
Using the Basic example for ASP.NET Core, I was able to get things working as expected with:
public void ConfigureServices( IServiceCollection services )
{
    services.AddMvc( options => options.EnableEndpointRouting = true )
            .SetCompatibilityVersion( Latest );
    services.AddCors();
    services.AddApiVersioning( options => options.ReportApiVersions = true );
}

public void Configure( IApplicationBuilder app, IHostingEnvironment env )
{
    app.UseCors(builder => builder.AllowAnyHeader().AllowAnyOrigin().WithMethods("GET", "POST"));
    app.UseMvc();
}

You didn't indicate which routing method you're using, but I confirmed that this works with both Endpoint Routing and Legacy Routing.
I tested the following preflight:
OPTIONS /api/values?api-version=2.0 HTTP/1.1
Host: localhost:5000
Origin: http://localhost
Access-Control-Request-Method: GET
Accept: application/json

HTTP/1.1 204 No Content
Access-Control-Allow-Methods: GET,POST
Access-Control-Allow-Origin: *

Clearly you are seeing a different behavior, but without more information, I'm unable to setup the same conditions.

I'm using .NET Core 2.1 so I don't think that option exists? Either way not specifying, so using the default routing mechanism.
Removed the UseApiVersioning and moved the AddCors right after AddMvc and then AddApiVersioning comes after that, but no change, I still get a 405 on OPTIONS

I don't have a complete picture of your environment and setup. A repro, even stripped down, is always best so I don't guess at your setup. The order in which you register services shouldn't matter, but I personally like to register them in logical order similar to middleware. In much older versions of API Versioning, it might have mattered.
I presume you meant ASP.NET Core 2.1. ASP.NET Core doesn't a specific affinity to .NET Core, but I can see how many people have been confused by the naming (thanks marketing team >_<). You'll want to make sure you at least using API Versioning 3.0. You might also consider moving to ASP.NET Core 2.2, but set the compatibility to 2.1 if that's what you really need. This will allow you to use the latest version of API Versioning (3.1.2). I don't really plan on patching 3.0.x unless there is a really strong demand for it. It's quite a bit of work to maintain multiple branches; especially, when the current branch is forward compatible.
You set the compatibility level like this:
services.AddMvc().SetCompatibilityVersion( CompatibilityVersion.Version_2_1 );

I tried making this change using the modifications to the Basic example that I listed above and it still works. I even tried dropping the versions back and that works too (though I did notice that CORS isn't reporting the Allow header correctly; maybe it's a bug in the old version).
The only other difference I can think of is hosting, which might make a difference. I'm attaching the 2.1 version that's working for me. Perhaps you can work it to repro your scenario or troubleshoot what's different in your setup.
Basic CORS Sample.zip

I did mean ASPNET Core 2.1 :)

Were you able to figure this out or otherwise resolve the issue? Did the example help?

It would appear that you've resolved your issue. If the issue isn't resolved, feel free to come back. We can reopen the issue and investigate further. Thanks.

@commonsensesoftware
With compatbilityversion 2.1 it works fine. with 2.2 it fails.
so please reopen and solve this problem.
here is a sample code.
eatklik.zip

@thezeeshanasghar I can't say exactly why your CORS configuration isn't working, but it's not related to API versioning. From what I can tell, you are not using API Versioning at all. Your question can more appropriately be answered on the ASP.NET repo(I'm not part of the ASP.NET team) or on Stack Overflow. Apologies for not being able to help  you troubleshoot your issue.

At some point something else changed and the issue went away


Jitpack not working as expected

What happened?
When running the example code of Jitpack (https://github.com/apache/camel-k-examples/tree/main/generic-examples/jitpack)
kamel run Jitpack.java -d github:squakez/samplejp:1.0.0-SNAPSHOT

It seemed the integration always goes into Error status without clear error message.
╰─ kamel get
NAME	PHASE	KIT
jitpack	Error	camel/kit-cm1cpb4qqlkcmha0bpv0

I looked up the status of several components, but couldn't figure out why it failed...
Steps to reproduce
Just follow the steps in the Jitpack example from camel-k examples github
Relevant log output
╰─ kubectl get it -o yaml
apiVersion: v1
items:
- apiVersion: camel.apache.org/v1
  kind: Integration
  metadata:
    annotations:
      camel.apache.org/operator.id: camel-k
    creationTimestamp: "2023-12-20T11:14:52Z"
    generation: 1
    name: jitpack
    namespace: camel
    resourceVersion: "4714827818"
    uid: ef70090e-fde1-48b4-95cc-94b05caf21fb
  spec:
    dependencies:
    - github:squakez/samplejp:1.0.0-SNAPSHOT
    sources:
    - content: |-
        /*
         * Licensed to the Apache Software Foundation (ASF) under one or more
         * contributor license agreements.  See the NOTICE file distributed with
         * this work for additional information regarding copyright ownership.
         * The ASF licenses this file to You under the Apache License, Version 2.0
         * (the "License"); you may not use this file except in compliance with
         * the License.  You may obtain a copy of the License at
         *
         *      http://www.apache.org/licenses/LICENSE-2.0
         *
         * Unless required by applicable law or agreed to in writing, software
         * distributed under the License is distributed on an "AS IS" BASIS,
         * WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
         * See the License for the specific language governing permissions and
         * limitations under the License.
         */

        // camel-k: language=java

        import org.apache.camel.builder.RouteBuilder;
        import acme.App;

        public class Jitpack extends RouteBuilder {
          @Override
          public void configure() throws Exception {
              from("timer:tick?period=2000")
                .setBody()
                  .simple(App.capitalize("hello"))
                .to("log:info");

          }
        }
      name: Jitpack.java
    traits: {}
  status:
    conditions:
    - firstTruthyTime: "2023-12-20T11:14:52Z"
      lastTransitionTime: "2023-12-20T11:14:52Z"
      lastUpdateTime: "2023-12-20T11:14:52Z"
      message: camel/camel-k
      reason: IntegrationPlatformAvailable
      status: "True"
      type: IntegrationPlatformAvailable
    - lastTransitionTime: "2023-12-20T11:14:52Z"
      lastUpdateTime: "2023-12-20T11:14:52Z"
      message: creating a new integration kit
      reason: IntegrationKitAvailable
      status: "False"
      type: IntegrationKitAvailable
    dependencies:
    - camel:log
    - camel:timer
    - github:squakez/samplejp:1.0.0-SNAPSHOT
    - mvn:org.apache.camel.k:camel-k-runtime
    - mvn:org.apache.camel.quarkus:camel-quarkus-java-joor-dsl
    digest: vRIQ0j9pvxlbEHd1kgTe57CxEGeCk7p3pJmPS2qW9sO0
    integrationKit:
      name: kit-cm1cpb4qqlkcmha0bpv0
      namespace: camel
    lastInitTimestamp: "2023-12-20T11:14:52Z"
    observedGeneration: 1
    phase: Building Kit
    platform: camel-k
    profile: Kubernetes
    runtimeProvider: quarkus
    runtimeVersion: 3.2.0
    version: 2.1.0
kind: List
metadata:
  resourceVersion: ""

klogs camel-k-operator-6bcfd5b9b6-cc9kt

{"level":"error","ts":"2023-12-20T11:17:26Z","msg":"Reconciler error","controller":"integration-controller","controllerGroup":"camel.apache.org","controllerKind":"Integration","Integration":{"name":"jitpack","namespace":"camel"},"namespace":"camel","name":"jitpack","reconcileID":"c29cf20a-2c70-45eb-b9cf-6da09bad8c74","error":"error during trait customization: mount trait execution failed: unable to find integration container: jitpack","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\tsigs.k8s.io/controller-runtime@v0.15.2/pkg/internal/controller/controller.go:324\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\tsigs.k8s.io/controller-runtime@v0.15.2/pkg/internal/controller/controller.go:265\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\tsigs.k8s.io/controller-runtime@v0.15.2/pkg/internal/controller/controller.go:226"}
{"level":"error","ts":"2023-12-20T11:17:36Z","msg":"Reconciler error","controller":"integration-controller","controllerGroup":"camel.apache.org","controllerKind":"Integration","Integration":{"name":"jitpack","namespace":"camel"},"namespace":"camel","name":"jitpack","reconcileID":"59f337aa-e25b-4918-9660-7010973b583f","error":"error during trait customization: mount trait execution failed: unable to find integration container: jitpack","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\tsigs.k8s.io/controller-runtime@v0.15.2/pkg/internal/controller/controller.go:324\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\tsigs.k8s.io/controller-runtime@v0.15.2/pkg/internal/controller/controller.go:265\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\tsigs.k8s.io/controller-runtime@v0.15.2/pkg/internal/controller/controller.go:226"}
{"level":"error","ts":"2023-12-20T11:17:56Z","msg":"Reconciler error","controller":"integration-controller","controllerGroup":"camel.apache.org","controllerKind":"Integration","Integration":{"name":"jitpack","namespace":"camel"},"namespace":"camel","name":"jitpack","reconcileID":"d7d29122-8cb3-4316-bcef-611dbeb08c9c","error":"error during trait customization: mount trait execution failed: unable to find integration container: jitpack","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\tsigs.k8s.io/controller-runtime@v0.15.2/pkg/internal/controller/controller.go:324\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\tsigs.k8s.io/controller-runtime@v0.15.2/pkg/internal/controller/controller.go:265\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\tsigs.k8s.io/controller-runtime@v0.15.2/pkg/internal/controller/controller.go:226"}
{"level":"error","ts":"2023-12-20T11:18:37Z","msg":"Reconciler error","controller":"integration-controller","controllerGroup":"camel.apache.org","controllerKind":"Integration","Integration":{"name":"jitpack","namespace":"camel"},"namespace":"camel","name":"jitpack","reconcileID":"09c0ff18-3320-44bc-93e9-c893e34940ba","error":"error during trait customization: mount trait execution failed: unable to find integration container: jitpack","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\tsigs.k8s.io/controller-runtime@v0.15.2/pkg/internal/controller/controller.go:324\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\tsigs.k8s.io/controller-runtime@v0.15.2/pkg/internal/controller/controller.go:265\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\tsigs.k8s.io/controller-runtime@v0.15.2/pkg/internal/controller/controller.go:226"}
{"level":"error","ts":"2023-12-20T11:19:59Z","msg":"Reconciler error","controller":"integration-controller","controllerGroup":"camel.apache.org","controllerKind":"Integration","Integration":{"name":"jitpack","namespace":"camel"},"namespace":"camel","name":"jitpack","reconcileID":"b8871452-998f-4a68-845d-26a8f1592cd4","error":"error during trait customization: mount trait execution failed: unable to find integration container: jitpack","stacktrace":"sigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).reconcileHandler\n\tsigs.k8s.io/controller-runtime@v0.15.2/pkg/internal/controller/controller.go:324\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).processNextWorkItem\n\tsigs.k8s.io/controller-runtime@v0.15.2/pkg/internal/controller/controller.go:265\nsigs.k8s.io/controller-runtime/pkg/internal/controller.(*Controller).Start.func2.2\n\tsigs.k8s.io/controller-runtime@v0.15.2/pkg/internal/controller/controller.go:226"}

╰─ kc describe ik kit-cm1cpb4qqlkcmha0bpv0
Name:         kit-cm1cpb4qqlkcmha0bpv0
Namespace:    camel
Labels:       camel.apache.org/created.by.kind=Integration
              camel.apache.org/created.by.name=jitpack
              camel.apache.org/created.by.namespace=camel
              camel.apache.org/created.by.version=4714827814
              camel.apache.org/kit.layout=fast-jar
              camel.apache.org/kit.priority=1000
              camel.apache.org/kit.type=platform
              camel.apache.org/runtime.provider=quarkus
              camel.apache.org/runtime.version=3.2.0
Annotations:  camel.apache.org/operator.id: camel-k
API Version:  camel.apache.org/v1
Kind:         IntegrationKit
Metadata:
  Creation Timestamp:  2023-12-20T11:14:52Z
  Generation:          1
  Resource Version:<PHONE_NUMBER>
  UID:                 32a3ef7c-4bea-4c9c-8d09-eb434ad3aa46
Spec:
  Dependencies:
    camel:log
    camel:timer
    github:squakez/samplejp:1.0.0-SNAPSHOT
    mvn:org.apache.camel.k:camel-k-runtime
    mvn:org.apache.camel.quarkus:camel-quarkus-java-joor-dsl
  Traits:
Status:
  Conditions:
    Last Transition Time:  2023-12-20T11:14:52Z
    Last Update Time:      2023-12-20T11:14:52Z
    Message:               IntegrationPlatform (camel-k)
    Reason:                IntegrationPlatformAvailable
    Status:                True
    Type:                  IntegrationPlatformAvailable
  Digest:                  v480vYI81ZKtdL9vqCv2yT5Z91tIQ8iCuEnjYmZPPubI
  Failure:
    Reason:  failure while building project: : exit status 1
    Recovery:
      Attempt:          5
      Attempt Max:      5
      Attempt Time:     2023-12-20T11:17:12Z
    Time:               2023-12-20T11:14:55Z
  Observed Generation:  1
  Phase:                Error
  Platform:             camel-k
  Runtime Provider:     quarkus
  Runtime Version:      3.2.0
  Version:              2.1.0
Events:
  Type    Reason                      Age    From                                Message
  ----    ------                      ----   ----                                -------
  Normal  IntegrationKitPhaseUpdated  6m39s  camel-k-integration-kit-controller  Integration Kit "kit-cm1cpb4qqlkcmha0bpv0" in phase "Build Submitted"
  Normal  IntegrationKitPhaseUpdated  6m39s  camel-k-integration-kit-controller  Integration Kit "kit-cm1cpb4qqlkcmha0bpv0" in phase "Build Running"
  Normal  IntegrationKitPhaseUpdated  4m16s  camel-k-integration-kit-controller  Integration Kit "kit-cm1cpb4qqlkcmha0bpv0" in phase "Error"

Camel K version
╰─ kamel version
Camel K Client 2.1.0

Strange. It works for me:
$ kamel run Jitpack.java -d github:squakez/samplejp:1.0.0-SNAPSHOT --dev
Integration "jitpack" created
Progress: integration "jitpack" in phase Initialization
...
[1] 2023-12-20 11:50:41,554 INFO  [org.apa.cam.k.Runtime] (main) Apache Camel K Runtime 3.2.0
[1] 2023-12-20 11:50:41,556 INFO  [org.apa.cam.qua.cor.CamelBootstrapRecorder] (main) Bootstrap runtime: org.apache.camel.quarkus.main.CamelMainRuntime
[1] 2023-12-20 11:50:41,559 INFO  [org.apa.cam.mai.MainSupport] (main) Apache Camel (Main) 4.0.0 is starting
[1] 2023-12-20 11:50:41,588 INFO  [org.apa.cam.k.sup.SourcesSupport] (main) Loading routes from: SourceDefinition{name='Jitpack', language='java', type='source', location='file:/etc/camel/sources/Jitpack.java', }
[1] 2023-12-20 11:50:42,484 INFO  [org.apa.cam.imp.eng.AbstractCamelContext] (main) Apache Camel 4.0.0 (camel-1) is starting
[1] 2023-12-20 11:50:42,494 INFO  [org.apa.cam.imp.eng.AbstractCamelContext] (main) Routes startup (started:1)
[1] 2023-12-20 11:50:42,494 INFO  [org.apa.cam.imp.eng.AbstractCamelContext] (main)     Started route1 (timer://tick)
[1] 2023-12-20 11:50:42,495 INFO  [org.apa.cam.imp.eng.AbstractCamelContext] (main) Apache Camel 4.0.0 (camel-1) started in 10ms (build:0ms init:0ms start:10ms)
[1] 2023-12-20 11:50:42,498 INFO  [io.quarkus] (main) camel-k-integration 2.1.0 on JVM (powered by Quarkus 3.2.6.Final) started in 2.244s.
[1] 2023-12-20 11:50:42,499 INFO  [io.quarkus] (main) Profile prod activated.
[1] 2023-12-20 11:50:42,499 INFO  [io.quarkus] (main) Installed features: [camel-bean, camel-core, camel-java-joor-dsl, camel-k-core, camel-k-runtime, camel-kubernetes, camel-log, camel-timer, cdi, kubernetes-client, smallrye-context-propagation, vertx]
[1] 2023-12-20 11:50:43,520 INFO  [info] (Camel (camel-1) thread #1 - timer://tick) Exchange[ExchangePattern: InOnly, BodyType: String, Body: v1.0.0-SNAPSHOT:HELLO]

Maybe your failure is related to the registry or any other cause. Have a look at the Camel Integration troubleshooting guide.

The guide I've provided above [1] should give you more details on how to troubleshoot an Integration. In your case what is clearly happening is a Maven build failure. I guess there could be some problem accessing the Jitpack repository by your cluster. You can have a more detailed trace checking the log of the Camel K operator Pod (kubectl logs camel-k-operator-xyz).
[1] https://camel.apache.org/camel-k/2.1.x/troubleshooting/troubleshooting.html

Thank you for the clue!
It seems my setting.xml uses company Nexus server as proxy.
To make it work, I had to add the following to Maven settings.xml
(in addition to other basic configs, like adding Jitpack repositories)
  <mirrors>
    <mirror>
      <id>repo-through-public</id>
      <mirrorOf>*,!jitpack.io</mirrorOf>
      <url>https://COMPANY-MAVEN-REPO/</url>
  </mirror>
  <mirror>
      <id>jitpack.io</id>
      <mirrorOf>jitpack.io</mirrorOf>
      <url>https://jitpack.io</url>
  </mirror>
  </mirrors>

It'll make Jitpack related dependencies go around company Nexus.
However, we can also do it the proper way -- that is make company Nexus server support Jitpack
See: https://github.com/jitpack/jitpack.io/issues/506#issuecomment-267338823
Thank you @squakez
I think we can close this issue?


Too Many Connections

I am having too many connections error and i dont see  any option to disable to ( disconnect ) the connection.

Could you please provide information about your new connection in your code, some  .getConnection() etc ?
and the maximum number of connections allowed on your database server?
Thank your.

its 151

Thanks for the information, but I'm not sure what's happening.
I'm testing benchmarks with multiple connections ( max_connection same you "151" connections )
but haven't encountered any "Too many connections" errors.
Could you please check if the connection is being established in a loop or another incorrect pattern?
This might be causing the issue.
// some method connection
.bind(connection) or .getConnection()
The information. It is important to me in finding and resolving the issues.
Thank you. your time

I will let you know if i get any error using these methods


WIP: Runner: Open Folders "in console" in Windows Terminal, if available

Open folders, which should be opened in a console, in windows terminal, if available.
There are ongoing discussions (see below) about how to properly do this feature, but this is a simple change, that enables windows terminal, if available, without changing anything of the code structure/architecture.
I personally love the launcher and found it inacceptable that it opened only cmd.

Tries to open Windows Terminal in selected path.
If not available, CMD will be opened.
(although I would prefer Powershell 😉, but which console a user wants, can be set in windows terminal)
Summary of the Pull Request
What is this about?
When searching for a folder, one can open the folder in a console. This console should be Windows Terminal (wt), if available.
Currently it is set to cmd.
PR Checklist

[ ] Applies to #xxx ?
[X] CLA signed. If not, go over here and sign the CLA
[ ] Tests added/passed  will try to find current tests and add to those
[ ] Requires documentation to be updated no
[ ] I've discussed this with core contributors already. If not checked, I'm ready to accept this work might be rejected in favor of a different grand plan. Issue number where discussion took place: #xxx

Info on Pull Request
What does this include?
Includes a simply check, if wt.exe exists. If yes, it will be launched (with -d PATH), otherwise, old behavior is performed, i. e. launcing ye olde cmd.exe
Validation Steps Performed
Tested the executed command on windows machines both with and without the Windows Terminal.
How does someone test & validate?
Run on a machine with and on one without Windows Terminal. With Windows Terminal, Windows Terminal should open. On a machine without WT, cmd (Command Prompt) should open.
Specs / References

Spec for Windows Terminal Process Model 2.0 #7240
Spec for Windows Terminal Window Management #8135
Default Terminal Spec #7414
Scenario: Windows Terminal 2.0 Process Model Improvements #5000

@MichaelWhi
thanks for working on this.
Can you please fix the links since they are not correct:

Spec for Windows Terminal Process Model 2.0 #7240
Spec for Windows Terminal Window Management #8135
Default Terminal Spec #7414
Scenario: Windows Terminal 2.0 Process Model Improvements #5000

Can we please add a setting for this?
Reason: I have wt installed but I don't use it really. So for me it should open in cmd as before and I don't want to uninstall wt to get this behaviour.

If we add a setting for this, can we implement Powershell and Powerschell 7 as two additional command processors too?

@MichaelWhi
Will you continue your work on this PR within the next time?

@MichaelWhi
Will you continue your work on this PR within the next time?

Will you continue your work on this PR within the next time?

I will, sorry for the delay! I will take a look again at your comments and suggestions during the next week.

Will you continue your work on this PR within the next time?

I will, sorry for the delay! I will take a look again at your comments and suggestions during the next week.

In agreement with @htcfreek questions, I'm closing this PR because we first need to open an issue to track this work and come up with a spec.
We cannot simply change a behavior that can effect users and cause problems for them.

In agreement with @htcfreek questions, I'm closing this PR because we first need to open an issue to track this work and come up with a spec.
We cannot simply change a behavior that can effect users and cause problems for them.


Update "submission started processing" email

Is your proposal related to a problem?
Currently the email is:
Dear NLP Sandbox Bots:

Your submission (submission ID 9712562) is in progress.  Log files produced while your workflow is running will be periodically uploaded here: https://www.synapse.org/#!Synapse:... Further notification will be provided when it is complete.

Sincerely,

Submission Queue Administration

I will add an extra email template step so we can use any template and text you want.  I will just disable the submission processing emailing step that the orchestrator does.

Proposed changes:

Don't mention the log (not useful)
Update the signature

Template:
Dear {name},

Your submission (submission ID 9712562) sent to the NLP Sandbox (NLP sandbox - Date Annotator) is in progress.

For further information, please visit the project website.

Sincerely,
The NLP Sandbox Team


get platform and architecture to download correct binary

Right now local-php-security-checker provides binaries for different platforms and architectures, see: https://github.com/fabpot/local-php-security-checker/releases/
Before this PR you did always download the linux_amd64 version, which doesn't run on other platforms like macOS (see https://github.com/fabpot/local-php-security-checker/issues/5 or https://github.com/fabpot/local-php-security-checker/issues/11 as an example).
To download the specific binary needed this PR tries to get the needed info from uname & uname -m and download the specific binary.
This pr was tested on Linux x86_64 and macOS.

this is exactly change I need as well and glad I came to check for any PR's on this before started down the path of figuring it out myself. Tested this change out just fine on macOS.

Thanks!


examples: integrate consumer example application

Add example OAuth consumer application and required documentation to
demonstrate how to interact with invenio-oauth2server.
(closes #147) (closes #137)

Signed-off-by: Harri Hirvonsalo<EMAIL_ADDRESS>

Rebased an integrated in #154. Once #154 is merged this PR should also show as merged.


How to process a missing trailing slash

If a visitor goes to this URL, with a missing trailing slash, it will fail
https://www.boost.io/doc/libs/1_83_0/libs/json
This works:
https://www.boost.io/doc/libs/1_83_0/libs/json/
However, that doesn't mean every URL should always get a trailing slash added.   There might be a URL displaying a file called a "Jamfile" in boost, which doesn't have an extension, or a trailing slash.

Something should be done in Django or Nginx..

@ashtum, many Algolia search results for beast go to https://www.boost.io/doc/libs/1_83_0/libs/beast which is missing a trailing slash.  Could that be adjusted in Algolia?

I think this is the same issue as #743.
I believe this should be resolved in the backend side.

Closing as duplicate


Outdated page

The steps described in the item 5 are not accurate with Atlassian's new UI. The flow should be https://admin.atlassian.com > select the org > directory > user provisioning.

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

ID: 04509836-867e-279f-c1d6-135a237d357e
Version Independent ID: e05a10ce-c46b-334e-78e2-30b416ed904a
Content: Tutorial: Configure Atlassian Cloud for automatic user provisioning with Azure Active Directory
Content Source: articles/active-directory/saas-apps/atlassian-cloud-provisioning-tutorial.md
Service: active-directory
Sub-service: saas-app-tutorial
GitHub Login: @zhchia
Microsoft Alias: jeedes

@joaopmartinezn Thanks for your feedback! We will investigate and update as appropriate.

@joaopmartinezn can you screenshot the part of the article you are referring to?

@v-viinde and @v-nagta Can you please update the doc? I agree that the flow is changed and we should update this in the doc.
@chetansriv for tracking.

Hey team.
First thing that should be changed is the order of the steps. Step 5 should be the step 6 since the Tenant URL and Secret Token are provided after the user creates the provisioning app at Atlassian. The correction is related to the following section:

Regarding the UI update. Atlassian has a different page to access the provisioning feature. The new steps are the following (https://admin.atlassian.com > select the org > directory > user provisioning):

Thanks for looking into this.

@joaopmartinezn We have updated the article as per your suggestion, please review
#please-close


[ISSUE] Possible duplicate class for WebHook

Description
The WebhookNotificationsOnDurationWarningThresholdExceededItem class is a possible duplicate of Webhook. Both takes a webhook destination id as input.
Removing the duplicate would make the options for WebhookNotifications consistent to be List[WebHook], just on_duration_warning_threshold_exceeded is different compared to the other options.
Other Information

OS: Linux Ubuntu 22.04.3 LTS (WSL)
Version: 0.12.0

Thanks for raising this! We will be doing a review of all dataclasses across all SDKs and try to remove these duplicate structures in the coming months.


Adding search, zoom, custom zoom and additional stylings to showplan

-Updating azdata to 0.0.13
-Updating prop views on node clicks

-Context menu on graphs

-Updating edge color on theme

-Scrolling graph control like ssms. Wheel scrolls through different graphs in tab and not an individual graph

-Zooming in, out and custom zoom on graph

-Node search widget

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

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

Totals

Change from base Build<PHONE_NUMBER>:
0.0%

Covered Lines:
14788

Relevant Lines:
29081

💛  - Coveralls


Import SSL certificates into Mono trust store

Import the default SSL root certificates into the Mono trust store, so that connecting to https services works out-of-the-box.
Fixes #7

I have slightly updated the PR and merged it: https://github.com/frol/docker-alpine-mono/commit/597c4952bc0f2de69bf8f39efc7c972e8b8b7e9d
@bvanreeven Thank you!


Visualize cannot load cube published on lindas int

I published Cube UBD003001 Red List on Lindas IINT with Cube creator, but Visualize cannot load the cube.
According to Cube Validator the cube is conformed to the basic profile.
The cube does not even appear in Visualize search.

Thank you for reporting the issue @ortnever. @bprusinowski could you take a look?

Hi @ortnever, could you share more information about the cube, such as its IRI? Or maybe a link to LINDAS query to show DESCRIBE the cube?
This would be very helpful if the cube doesn't even appear in the search. Thanks in advance!

Hi @bprusinowski
https://environment.ld.admin.ch/foen/ubd003001
https://int.visualize.admin.ch/en/browse?dataSource=Int&dataset=https%3A%2F%2Fenvironment.ld.admin.ch%2Ffoen%2Fubd003001
https://int.lindas.admin.ch/sparql#query=PREFIX+schema%3A+<http%3A%2F%2Fschema.org%2F>

DESCRIBE+%3Fcube

FROM+<https%3A%2F%2Flindas.admin.ch%2Ffoen%2Fcube>
WHERE+{

++++++<https%3A%2F%2Fenvironment.ld.admin.ch%2Ffoen%2Fubd003001>+schema%3AhasPart+%3Fcube+.
++++++%3Fcube+schema%3Aversion+14+.
++++
}

&endpoint=https%3A%2F%2Fint.lindas.admin.ch%2Fquery

Does it help?

Yes, thanks @ortnever! I am taking a look 👍

It looks like the cube with version 14 has a schema:expires predicate, which excludes the cube from being usable in Visualize. For "valid" cubes, we can't have this property, as it's used to filter out depreciated cubes.

@ortnever let me know if this makes sense and if removing the property fixes the error 👀

Thanks Bartosz for the explanation. I don't understand how this cube got the ‘expires’ property.
I created and published this cube via the Creator cube and did not use the ‘unlist cube’ function, which is intended to depreciate the cube.
Could you please delete the property "expires".
Thank you.

No problem! Unfortunately I cannot remove the "expires" property, I believe it requires some kind of "admin" rights to be able to remove triples from LINDAS – I'd suggest to reach out to Zazuko to support, as it also looks like a Cube Creator issue.
Let me know in case there's anything else I can support with 😊

Thank you Bartosz ! In this case you can close the issue. Have a nioce week-end !

Thanks @ortnever, you too!


1.5.16 release

We've got a couple bug fixes and a chance to deal with #379 via https://github.com/sgillies/frs-wheel-builds/issues/6.

[x] Close Shapely issues
[x] Update version, change log
[x] Tag
[x] Link only libgeos_c.dylib (geos-config --clibs) when making OS X wheels
[x] Publish dists

Share and enjoy!


Home Office specific templates in designer

Describe the bug
Currently there are Home Office specific templates in the designer for header, footer and logo.
To Reproduce
Run the designer.
Expected behavior
Generic header and footer are used by default.
Repository

designer

Additional context
It's certainly appropriate for specific running instances of these apps to be branded in different ways, so a mechanism for overriding templates and/or messaging needs to be provided.
Currently you can already override templates by copying over the top of the existing ones in your own internal build process. This doesn't need to be arduous, extending the base docker image and copying in additional files is very quick. Given this I'd suggest the current branded templates be replaced by something generic and organisation builds be updated with their own template overrides.

@superafroman #298 introduces feature flags. At the moment it's just used for turning on/off features but we will be able to pass down text. I reckon we could even pass down a path and do a dynamic import for components like the footer

P2


python3Packages.meilisearch: init at 0.18.0

Description of changes
Client for the Meilisearch API
https://github.com/meilisearch/meilisearch-python
Fixes #164010

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
[ ] Tested basic functionality of all binary files (usually in ./result/bin/)
22.05 Release Notes (or backporting 21.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
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[x] Fits CONTRIBUTING.md.

Result of nixpkgs-review pr 164080 run on x86_64-linux 1

2 packages built:

python310Packages.meilisearch
python39Packages.meilisearch


[Feature Request] The ability to see a parked/docked train's doors will be while parked/docked

Is your feature request related to a problem? Please describe.
A clear and concise description of what the problem is. Example: I'm always frustrated when...
I can't tell where a train car's door will be when parked at a station
Describe the solution you'd like
A clear and concise description of what you want to happen.
The ability to either

tell a train to park/dock stationary at a station without going through its route
or a tool that displays a "hologram" model of the train car on the station tracks in the position the actual train car would be in when parked/docked

Additional Information
Add any other context or screenshots about the feature request here.
I am wanting this so that I can (at least try to) place the automatic doors right up againgst the train.

机铁吗？怎么可能找不到车门？

I don't mean the door item you place.
I mean the doors of the trains in and of themselves.

I used Bing translator... translation of your second reply made no sense to me.

对了，一段文字用不同的翻译器，翻译出来的意思也是不同的！

JadianRadiator, send the trains along the routes before you build the screen doors. When the train stops at the stop, note where the doors are, and add the automatic doors. Eventually, some of this information(such as the fact that doors on the same car of a M train (or it's mini variant) are always 3 blocks apart) will passively enter your memory.

This can now be done with a temporary depot and siding rail. Thanks for your suggestion!


The set-output command is deprecated and will be disabled soon

https://github.com/github/codeql-action/blob/297ec80a468c234608046f51ee8c65da128a1e94/lib/analyze-action.js#L175-L179

Warning: The set-output command is deprecated and will be disabled soon. Please upgrade to using Environment Files. For more information see: https://github.blog/changelog/2022-10-11-github-actions-deprecating-save-state-and-set-output-commands/

This was fixed in https://github.com/github/codeql-action/pull/1301, and will be available in the next release of the action v2 action (or you can use main directly).


Extraction Error: invalid cross-device link

Hello,
I'm trying to use Unpackerr with sonarr and radarr.
It detects well the two *arr instances, detects when a .rar is present, but does not achieve to extract this archive, I have the error in wrote in the title.
I have a ubuntu server on version 20.04 LTS, all the app are in docker.
I'm also using mergerfs to merge two disks together. And my downloads folder is in the mergerfs array. I have no problem with it in any docker I have. But seeing the error I get using unpackerr, maybe its coming from there ?
If you need more info or anything please ask.

Please give me full log lines. invalid cross-device link is simply not showing me enough data to know what operation triggered the error.

2020/12/10 10:30:29 Extraction Started: B-Movie.Lust.and.Sound.In.West-Berlin.1979-1989.2015.1080p.BluRay.x264-BiQ, items in queue: 0 2020/12/10 10:30:29 [Unpackerr] Queue: [63 waiting] [0 queued] [1 extracting] [4 extracted] [0 imported] [0 failed] [0 deleted] 2020/12/10 10:30:29 [Unpackerr] Totals: [76 restarted] [1 finished] [164|164 webhooks] [0 stacks] 2020/12/10 10:30:29 Error: Renaming Temp File: /downloads/B-Movie.Lust.and.Sound.In.West-Berlin.1979-1989.2015.1080p.BluRay.x264-BiQ_unpackerred/_unpackerred.biq-b-movie.lust.and.sound.in.west-berlin.1979-1989.2015.1080p.bluray.x264-subs.rar.txt to /downloads/B-Movie.Lust.and.Sound.In.West-Berlin.1979-1989.2015.1080p.BluRay.x264-BiQ/Subs/_unpackerred.biq-b-movie.lust.and.sound.in.west-berlin.1979-1989.2015.1080p.bluray.x264-subs.rar.txt: rename /downloads/B-Movie.Lust.and.Sound.In.West-Berlin.1979-1989.2015.1080p.BluRay.x264-BiQ_unpackerred/_unpackerred.biq-b-movie.lust.and.sound.in.west-berlin.1979-1989.2015.1080p.bluray.x264-subs.rar.txt /downloads/B-Movie.Lust.and.Sound.In.West-Berlin.1979-1989.2015.1080p.BluRay.x264-BiQ/Subs/_unpackerred.biq-b-movie.lust.and.sound.in.west-berlin.1979-1989.2015.1080p.bluray.x264-subs.rar.txt: invalid cross-device link 2020/12/10 10:30:29 Error: Renaming Temp File: /downloads/B-Movie.Lust.and.Sound.In.West-Berlin.1979-1989.2015.1080p.BluRay.x264-BiQ_unpackerred/biq-b-movie.lust.and.sound.in.west-berlin.1979-1989.2015.1080p.bluray.x264.idx to /downloads/B-Movie.Lust.and.Sound.In.West-Berlin.1979-1989.2015.1080p.BluRay.x264-BiQ/Subs/biq-b-movie.lust.and.sound.in.west-berlin.1979-1989.2015.1080p.bluray.x264.idx: rename /downloads/B-Movie.Lust.and.Sound.In.West-Berlin.1979-1989.2015.1080p.BluRay.x264-BiQ_unpackerred/biq-b-movie.lust.and.sound.in.west-berlin.1979-1989.2015.1080p.bluray.x264.idx /downloads/B-Movie.Lust.and.Sound.In.West-Berlin.1979-1989.2015.1080p.BluRay.x264-BiQ/Subs/biq-b-movie.lust.and.sound.in.west-berlin.1979-1989.2015.1080p.bluray.x264.idx: invalid cross-device link 2020/12/10 10:30:29 Error: Renaming Temp File: /downloads/B-Movie.Lust.and.Sound.In.West-Berlin.1979-1989.2015.1080p.BluRay.x264-BiQ_unpackerred/biq-b-movie.lust.and.sound.in.west-berlin.1979-1989.2015.1080p.bluray.x264.rar to /downloads/B-Movie.Lust.and.Sound.In.West-Berlin.1979-1989.2015.1080p.BluRay.x264-BiQ/Subs/biq-b-movie.lust.and.sound.in.west-berlin.1979-1989.2015.1080p.bluray.x264.rar: rename /downloads/B-Movie.Lust.and.Sound.In.West-Berlin.1979-1989.2015.1080p.BluRay.x264-BiQ_unpackerred/biq-b-movie.lust.and.sound.in.west-berlin.1979-1989.2015.1080p.bluray.x264.rar /downloads/B-Movie.Lust.and.Sound.In.West-Berlin.1979-1989.2015.1080p.BluRay.x264-BiQ/Subs/biq-b-movie.lust.and.sound.in.west-berlin.1979-1989.2015.1080p.bluray.x264.rar: invalid cross-device link 2020/12/10 10:30:29 Error: Renaming Temp File: /downloads/B-Movie.Lust.and.Sound.In.West-Berlin.1979-1989.2015.1080p.BluRay.x264-BiQ_unpackerred/biq-b-movie.lust.and.sound.in.west-berlin.1979-1989.2015.1080p.bluray.x264.sub to /downloads/B-Movie.Lust.and.Sound.In.West-Berlin.1979-1989.2015.1080p.BluRay.x264-BiQ/Subs/biq-b-movie.lust.and.sound.in.west-berlin.1979-1989.2015.1080p.bluray.x264.sub: rename /downloads/B-Movie.Lust.and.Sound.In.West-Berlin.1979-1989.2015.1080p.BluRay.x264-BiQ_unpackerred/biq-b-movie.lust.and.sound.in.west-berlin.1979-1989.2015.1080p.bluray.x264.sub /downloads/B-Movie.Lust.and.Sound.In.West-Berlin.1979-1989.2015.1080p.BluRay.x264-BiQ/Subs/biq-b-movie.lust.and.sound.in.west-berlin.1979-1989.2015.1080p.bluray.x264.sub: invalid cross-device link 2020/12/10 10:30:29 Deleted (recursively): /downloads/B-Movie.Lust.and.Sound.In.West-Berlin.1979-1989.2015.1080p.BluRay.x264-BiQ_unpackerred 2020/12/10 10:30:29 Extraction Error: B-Movie.Lust.and.Sound.In.West-Berlin.1979-1989.2015.1080p.BluRay.x264-BiQ: rename /downloads/B-Movie.Lust.and.Sound.In.West-Berlin.1979-1989.2015.1080p.BluRay.x264-BiQ_unpackerred/biq-b-movie.lust.and.sound.in.west-berlin.1979-1989.2015.1080p.bluray.x264.sub /downloads/B-Movie.Lust.and.Sound.In.West-Berlin.1979-1989.2015.1080p.BluRay.x264-BiQ/Subs/biq-b-movie.lust.and.sound.in.west-berlin.1979-1989.2015.1080p.bluray.x264.sub: invalid cross-device link

Unpackerr made a new folder in /downloads/, unpacked things into it, and then tried to rename those things back to the original folder inside /downloads/. This is very much a problem being produced by the file system, that for most configurations, never happens.
If you need this fixed in unpackerr, it will take me some time to do, but it can be done.
The alternative is to figure out if you can tune mergerfs (I know nothing about it, sorry), to allow rename on the filesystem, or at least in the /downloads/ folder. It's basically treating every folder (at least in /downloads) as an independent file system. It may be that this fs just does not allow rename. I'm not sure.
Please let me/the Internet know what you figure out, and if you need me to build a workaround for this. The problem with the workaround is that it will use copy instead of rename and if your *arr app tries to import before the copy is finished, it may import an incomplete file. If you have your *arr apps set to use hard links you wont have this race condition. Just things to consider and make sure you set correctly if we go this route.

Thanks for your answer, it directed me to the right tracks.
I found the following indications on mergerfs github : https://github.com/trapexit/mergerfs#rename--link
I had to change a flag in my fstab, now its working.
It seems to be more of a workaround than the proper way to handle unpackerr's rename but its working for now.
Thanks :)

I'll make this work in the next release, but it may not be for a few weeks to a few months. I'm glad you found a workaround to get you unblocked! I'll leave this open and comment again when a fix is ready for you.

Hi there!
Which flag did you had to use exactly on that page?
I am encountering this message as well while using Mergerfs.
Sorry for the bad English, it is my third language.
Merci!

@maxi1134 Try the latest beta: https://github.com/davidnewhall/unpackerr/releases/tag/v0.8.0-beta3
This release includes a copy fallback when move does not work.

Seems to work!
Thanks a lot!

Sweet! Please let me know if you run into any problems so I can fix them before that beta goes not-beta.


Precommit after the original prettier formating

Hey there!
We are about to inject prettier to our project, so we looked for manual/automatic ways of its usage.
When I run Prettier manually on a .js file, and then commit it using precommit (thanks for the fix in #2 ), I get the same error as in that ticket:
 SyntaxError: Unexpected token (5:9)
  4 |         // code
> 5 |       } else {
    |         ^
  6 |         // code
  7 |       }

However, if I don't call prettier manually, there is no problem.

Hi @defusioner, we will definitely need more information here.
The output you have pasted does not contain any stack trace so it is impossible to tell what is happening. I don't think your issue is related to #2 from your description.
The best way to help us dig into the issue you are facing is by providing a minimal reproduction of the issue.

Seems that this is no longed reproducible in 1.10.1 @JamesHenry

Thanks for letting me know!


Not supported 19044.1586

After Windows Update on March 8, 2022—KB5011487. Thank you for your support in fixing this :-)

https://github.com/sebaxakerhtc/rdpwrap.ini/blob/master/rdpwrap.ini

Duplicate of https://github.com/stascorp/rdpwrap/issues/1725

Many thanks!

Many thanks, I confirm that the ini file works!


The number of 5mC sites obtained using the new(version 0.13.2) and old(version 0.11.0) versions of nanopolish is very different

Hello, I use different versions of nanopolish to call CpG sites according to the following commands, but the number of sites obtained varies greatly. Is there any filtering process in the new version ?
Thanks,
Xueyu.
Number of sites obtained using version 0.13.2      1575540
Number of sites obtained using version 0.11.0       1618763
nanopolish  call-methylation \
   -t 8 \
   -r my.fastq.gz \
   -b my.hg38.bam \
   -g hg38.fa \
   -w "chr1:0-248956422" > methylation_calls.tsv  &&  touch call_methylation_done

python calculate_methylation_frequency.py  -i  methylation_calls.tsv -s > methylation_calls.frequency.tsv

Hi,
In v0.12 we changed some of the criteria for methylation calling. You can read about it in the last paragraph here:
http://simpsonlab.github.io/2020/03/03/nanopolish-v0.12.0/
Jared


feat: add bloom_filter to data_structures

Description of Change
I have added a simple generic implementation for bloom filter

Checklist

[x] Added description of change
[x] Added file name matches File name guidelines
[x] Added tests and example, test must pass
[x] Added documentation so that the program is self-explanatory and educational - Doxygen guidelines
[x] Relevant documentation/comments is changed or added
[x] PR title follows semantic commit guidelines
[x] Search previous suggestions before making a new one, as yours may be a duplicate.
[x] I acknowledge that all my contributions will be made under the project's license.

Notes:
Good use case example for that data structure

Hello, thank you for a response. I ran the clang-tidy+clang-format, as it was descripted in contributing guide and made some fixes by hand. There are no any errors localy right now 👍🏻

@Panquesito7 please, check PR - all requested changes have been made


Microsoft ODBC driver needed in machine to connect Django to AzureSql

I had to install Microsoft ODBC driver in ubuntu to connect to azuresql from django. All other dependencies needed can be installed using pip (I have added them in requirements.txt file in backendapi branch) but this driver needs to be present in the ubuntu system.
Relevant links (second one received from Yugesh):
https://docs.microsoft.com/en-us/sql/connect/odbc/linux-mac/installing-the-microsoft-odbc-driver-for-sql-server?view=sql-server-ver15
https://medium.com/@__pamaron__/deploy-a-django-application-connected-to-azure-sql-using-docker-and-azure-app-service-a2c107773c11

Please give instructions for installing them on ubuntu we can add it to the Dockerfile

Need to add this to the Heroku docker as well.


Add services list

Add command to list all services

This looks to be the same as the `agent-services

ohhhhh you right :( sorry ... I didn't see this command. I'm looking for service* instead of agent.


[TACHYON-1582] Restructure POM: rename integration-tests to tests

https://tachyon.atlassian.net/browse/TACHYON-1582
This is the followup PR to achieve what proposed in https://tachyon.atlassian.net/secure/attachment/14000/POMstructurechangeproposal.pdf

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8198/
Test PASSed.

LGTM

@apc999 you may have missed some references to integration-tests (ie. inAbstractLocalTachyonCluster)

@calvinjia doc updated

LGTM

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/Tachyon-Pull-Request-Builder/8201/
Test PASSed.


Adding mwaa_environment resource

Description of your changes
Adding mwaa_environment resource #1093
I have:

[v] Read and followed Crossplane's [contribution process].
[v] Run make reviewable to ensure this PR is ready for review.
[ ] Added backport release-x.y labels to auto-backport this PR if necessary.

I tried to implement it v1.7.0. but I couldn't make a progress because of the error when I ran make submodules, make generate
10:03:14 [ OK ] go generate linux_arm64
10:03:14 [ .. ] go mod tidy
go: finding module for package github.com/upbound/provider-aws/apis/mwaa/v1beta1
go: github.com/upbound/provider-aws/internal/controller/mwaa/environment imports
github.com/upbound/provider-aws/apis/mwaa/v1beta1: no matching versions for query "latest"
10:03:20 [FAIL]
make[1]: *** [go.generate] Error 1
make: *** [generate] Error 2
How has this code been tested

Hey @sanhaKimVics,
We appreciate your contribution, thank you :) The problem you describe seems to be caused by the changes here. The approach in this comment may solve your problem, could you please take a look?

After this PR the problem should be solved, please ignore my comment above, reset your branch to main, and follow the steps of adding resources again.


docs: CLA Assistant Test Change

Testing a change to make sure that the CLA Assistant is working as needed.

The CLA Assistant test is complete, closing out this PR as it is no longer needed.


Auxiliary qubit tracking in HighLevelSynthesis

Summary
Enable tracking the state of auxiliary qubits in high-level synthesis. This allows synthesis plugins to leverage additional qubits in a decomposition, leading to a potential reduction of circuit depth and number of operations (which is why I tagged it for the performance demo 🙂). This PR unblocks work on the circuit library, in particular refactoring of the MCX and MCMT gates.
Details and comments
This first implementation follows a greedy approach, where each operation is given access to all currently available auxiliary qubits. It does so by using the newly added QubitTracker, which keeps track of which qubits in the circuit/dag are "clean" (in state $|0\rangle$) or "dirty" (an unknown state). Generally, if qubits start out as clean, and as soon as it is involved in an operation, it changes to dirty (special rules apply for operations like resets, barriers or delays).
Another important change is that synthesized blocks must be synthesized again. This recursion is necessary, since unrolling or decomposing an operation, could yield other operations that must be synthesized. This slows down the code compared to the current state, but only by another iteration over the DAG, so that should be a reasonably small overhead.
Follow-ups could involve:

speedup the code by having the synthesis plugins return DAG circuits (will be easier once we could construct a DAG from Rust's CircuitData or an iterator over circuit instructions)
avoid redundant recursion if plugins can report the basis gate set of their decomposition
do the whole thing in Rust 🙂

Pull Request Test Coverage Report for Build<PHONE_NUMBER>0
Details

179 of 190 (94.21%)  changed or added relevant lines in 7 files are covered.
9 unchanged lines in 2 files lost coverage.
Overall coverage increased (+0.004%) to 89.755%

Changes Missing Coverage
Covered Lines
Changed/Added Lines
%

qiskit/transpiler/passes/synthesis/high_level_synthesis.py
123
128
96.09%

qiskit/transpiler/passes/synthesis/qubit_tracker.py
51
57
89.47%

Files with Coverage Reduction
New Missed Lines
%

crates/qasm2/src/lex.rs
3
92.48%

crates/qasm2/src/parse.rs
6
97.61%

Totals

Change from base Build<PHONE_NUMBER>0:
0.004%

Covered Lines:
67442

Relevant Lines:
75140

💛  - Coveralls


[0-9]+/[0-9]+ renders as a fraction - difficult for DOI quoting

A string that matches [0-9]+/[0-9]+ renders as a superscript number, slash. subscript number. This is cute, but breaks the intention of slash separated numeric descriptors like seen for some DOIs (BioRxiv's DOI family is in 10.1101/nnnnnn and falls into the trap).
Is there a way to either hint this not to happen or preferably turn it off?

You could turn the DOI into a URL with the markdown link code. use the doi resolver service by prefixing with https://dx.doi.org/. For mine I have used it as https://doi.org/10.1017/S0025100309990296
Also what part of the text are you putting your DOI in? I am using like so:
[[url_custom]]
name = "Publisher Page"
url = "https://doi.org/10.1017/S0025100309990296"

This is for in-text bibs. An example is here at the bottom of the page..

Under [blackfriday] in your config.toml you can add fractions = false to disable smart fractions :)

Great. Thanks.


Skeleton offset

skeleton offset by offset the chest and neck horizontally to help with vrchat being weird.
https://github.com/SlimeVR/SlimeVR-Server/issues/22

This is not how #22 should be fixed. You are moving the whole skeleton forward, but you should be moving each tracker separately, without it affecting the whole skeleton hierarchy (this is also why leg offset is wrong). It sort of works, but it's not ideal. Skeleton needs refactoring to make this simpler...


Missing methods updates for MockResponse

Currently the docs say:

Body Method Renamed On MockResponse
Previously, Saloon had a method getBody() on a MockResponse class. This has now been renamed to body() to be more consistent with the rest of Saloon. Additionally, the old getBodyAsString() method has been removed.

I discovered that getHeaders() has been updated to headers() and getStatus() has been changed to status(). Not sure if there are other ones as well. Just thought you'd like to know!

Oh thank you very much for letting me know @brandonferens! I have updated the guide 🙌


Update to Login page

Fixes #
Converted "sign up" into a button in login page and removed unnecessary "sign up" link in forgot password page.
Note: Please check Allow edits from maintainers. if you would like us to assist in the PR.

The Signup link has been displayed as a hyperlink to signify secondary importance. Although not sure if we should keep the Signup link on Forgot Password page or not @nitin10s ?

The Signup link has been displayed as a hyperlink to signify secondary importance. Although not sure if we should keep the Signup link on Forgot Password page or not @nitin10s ?

Yes, please remove the sign up link in forgot password page. But keep the sign up as a hyperlink in the login page.

Yeah, signup link doesn't make sense on the Forgot Password page [ I don't think we had it in the prototype as well, I guess this got carried from the previous design. ]

Now, I made "sign up" as a hyperlink back @nitin10s @satu0king

I removed "new user" link in forgot password page @aayush-05

Oh sorry ,I haven't noticed my code is outdated. LOL


Added support for managing .P12 certificates

Ping @stack72

@ffrank This looks fine to me. Lets just merge it?

Eh, sure. What's the worst that can happen? :)
Thanks @Mharlin !

+1 from me. Also lost my commit bit here.

@ffrank and @liamjbennett: Sorry about that. We've been really bad at moving people back out of the modules/admin team once modules have been transferred and adding collaborators with write access to the module instead. I just fixed the latter so you're good to go again.

Awesome. Thanks!


Fix mismatched drawer transitions

Helps with #201.

Changes proposed in this Pull Request:

Update the DrawerLayout transition to match the timing of the Drawer transition

This seems to help with the transition, but if you get to clicking around on the drawer a bunch, you can still see the 'gap' occasionally. The transitions are the same, but I suspect there is a race condition when the variables get set to trigger them (drawer gets open/closed state set right away through the prop change, but the DrawerLayout has to wait until the Context is updated). We might need to explore moving some of the drawer logic into the context provider so that these get triggered at the exact same time.

Code looks good. Showcase spins good yet still with some transition animation delay — probably just a matter of my old machine at this point.
Do we want to use these transitions? I am happy with the way it is right now.

It's probably not a bad idea to use these...it's a little more involved though...we'd have to change the transition based on whether the drawer is open or closed to get the different timings. Right now we just set the transition once and use the same timing for entering and exiting. I'll log an enhancement for this.


Terms with backing content file is not handled correctly in 0.123

Example site. I try to list taxonomy terms, according to the docs (it is not changed for 0.123) I can do it like this:

  {{ range .Site.Taxonomies.tags }}

{{ .Page.Title }} {{ .Count }}

  {{ end }}

With the example site, when I run it in 0.122, I get this result in the console:
WARN  Listing tags:
WARN  --------------------
WARN  Tag "tag1" "Tag One"
WARN  Tag "tag2" "Tag Two"
WARN  Tag "tag3" "Tag Three"
WARN
WARN  Listing tags in alphabetical order:
WARN  -----------------------------------
WARN  Tag "Tag One"
WARN  Tag "Tag Three"
WARN  Tag "Tag Two"

But when I run it with 0.123, I get this:
WARN  Listing tags:
WARN  --------------------
WARN  Tag "tag1" "Tag One"
WARN
WARN  Listing tags in alphabetical order:
WARN  -----------------------------------
WARN  Tag "Tag One"

Thanks for this. I will fix this during the weekend.

Additional findings...

Ranging over an ordered taxonomy (e.g., site.Taxonomies.tags.ByCount) has the same problem
Ranging over .Page.GetTerms works as expected

Yea, I have spotted the obvious mistake.


Installation via chocolatey is missing

Linux installation guides use a package manager. Why Windows' installation experience can't be the same?

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

ID: 8246b90a-efb1-03ce-f642-d3eb2441fc30
Version Independent ID: 2fdd20ef-7bd3-57bc-7957-93f4bb5377ce
Content: Install the Azure CLI for Windows
Content Source: docs-ref-conceptual/install-azure-cli-windows.md
Product: azure
GitHub Login: @sptramer
Microsoft Alias: sttramer

The chocolatey package for Azure CLI is not officially maintained by Microsoft, and so is not a documented installation method.

Ok then why do you maintain macOS/Linux versions  of the packages installable via package managers but not the Windows one? Am I wrong in thinking that Microsoft supposed to back their own products? Using GUI to install a CLI doesn't make much sense.

If you'd like to see an official Chocolatey package, file a feature request with engineering: https://github.com/azure/azure-powershell/issues


Crash with Hamsters Plus Mod

Mod Name
Hamsters Plus
Mod Homepage
https://www.curseforge.com/minecraft/mc-mods/hamsters-plus
Minecraft version
1.20.1
Describe the bug
Crash on start up
Steps to reproduce

Use NeoForge modloader version 47.1.81 (has no problem with other fabric mods using connector, I'm for example using Better Nether/End and Useless Reptile)
Install Connector Beta 32, Extras 1.9.0 and Forgified Fabric Api 0.91.0+1.10.4
Install Hamsters Plus 1.0.2
Install Geckolib Neo version 4.3.1 (also, Neo version Gecko works fine with other dependencies like Useless Reptile)
Crash
...

Logs
https://gist.github.com/SuperStefan97/0c2411af330e398e688efed2c2393d35
Additional context
First of all Merry Christmas and Happy New Year. I also posted another issue about Recrafted Creatures around Christmas, I know you are busy, but could you give a check too when you got any time? Thanks for your time with this awesome mod

You will need to use Geckolib Fabric for Hamsters Plus

Thanks! Sadly, Fabric Gecko doesn't seems to work with Forge/Neo-gecko dependent mods. Oddly enough, Useless Reptile which is a Fabric mod that also needs Gecko, works nice with Neo gecko

I understand, so there is no way to use Forge/Neo Gecko dependent mods alongside Fabric dependent mods?

Most Geckolib Forge,Neo Gecko mods work with Geckolib Fabric. But at the moment we will have to wait till Geckolib inplants a mulitloader system. So for right now we cannot use Geckolib Forge, NeoForge alongside with Geckolib Fabric. There is a fork of Geckolib called "Azurelib" which has a mulitloader system.

I see, will mods need to replace it dependency to Gecko, or would it work only by replacing Gecko with Azure on my side?

No, Geckolib mods do not use Azurelib dependencies.

Same issue as #231, see that report for more information on the current state of geckolib on connector.


Automatic podspec versioning

Podspec Version is now being parsed directly from the SPEnvironment constant.
Props to @astralbodies for the idea (+ for helping me out!).

Post :shipit:  :grin:

Thanks again Aaron!


LightGBM support

It'd be nice to support explain_weights and explain_prediction for scikit-learn wrappers from https://github.com/Microsoft/LightGBM.

Fixed by https://github.com/TeamHG-Memex/eli5/pull/169.


Certain apps won't stay within zone

Environment
Windows build number: Microsoft Windows [Version 10.0.18362.476]
PowerToys version: <IP_ADDRESS>
PowerToy module for which you are reporting the bug (if applicable): FancyZones

Steps to reproduce

Create a small zone (I used the upper left quadrant of a 1080p screen)
Drag an app (Such as Spotify or Discord) into the zone

Expected behavior
The app should be confined within the zone

Actual behavior
The app extends out of the bottom out of the zone

I believe this might be because the app has a certain minimum size for the window.  I'm not entirely sure if this should be a bug report, or a feature request to force apps smaller than they allow
Thanks!

Hi @tgkenney
if the app has a minimum window size, and that can be verified pretty easily just resizing the window manually, there is nothing we can do about it, we can't force the window to be smaller.

I am having similar issues with at least 1 program. I think a second is doing the same thing but I cannot remember which one. As you can see in the first pic, the Window for Autodesk Design Review is not only not contained to the zone (layout in image 2) but it is not even contained to the Window. This was working properly in older versions (I believe 0.13.0).

HI @gregchamblin
I think in your case this is a different problem, try to move the zone a few pixel away from the edge of the screen, if the window get snapped it means you are experiencing the bug in issue https://github.com/microsoft/PowerToys/issues/762


Operation Queue collision on multiple RunTest calls and Tracing

On autorun of the IUTF we push at the end of RunTest a "Quit/N" to the operation queue.
If we call RunTest several times from a run() function this stacks up. While this is not an issue it gets a problem if we want to use tracing in a later call. Then we have already pushed
"Quit/N"
and later "RELOAD CHANGED PROCS " and "COMPILEPROCEDURES ".
Obviously the IUTF will quit Igor Pro when dropping to the command line instead of executing the reentry for tracing.
This bug only comes up if:

Autorun is enabled through DO_AUTORUN.TXT
multiple Runtest calls are issued in a e.g. run() function
a Runtest call with tracing is used as last call to RunTest in run().

As RunTest can not foresee future calls, we have to keep pushing "Quit/N" when RunTest ends.
However, if we later realize that we want to do tracing, we need to clear the OP Queue and put "RELOAD CHANGED PROCS " and "COMPILEPROCEDURES " in a fresh queue.
I made a feature request to WM to have a command for clearing the OP Queue.
Follow up issue based on that is that in the CI for testing the IUTF itself currently the tracing tests are not executed. The result shows "good" though, as the partial tests run through without errors. :-/

We probably should use one pxp per tracing test, and that's it or?

Maybe DO_AUTORUN_PLAIN.TXT from https://docs.byte-physics.de/igor-unit-testing-framework/advanced.html#automate-test-runs would help as well.

We already use one pxp per tracing test. We currently have no logic implemented for a reentry after run() dropped to the command line.
As workaround we could of course split off the RunTest call with tracing to another pxp such that we do not have other calls without tracing before.
If the proposed operation queue clear is available in IP9 we could at least allow normal RunTest calls before a RunTest call with tracing. Combined with a possible change that allows a reentry after a RunTest call with tracing, we could solve all of the above issues.

You write

If we call RunTest several times from a run() function this stacks up.

so can we have only one RunTest per pxp?

If autorun is enabled and we have multiple RunTest calls in one pxp that all do not use instrumentation then the Operation Queue stacks up: "SaveHistoryLog();Quit/N;SaveHistoryLog();Quit/N;SaveHistoryLog();Quit/N;...".
This is uncritical as the first Quit/N quits Igor Pro and the rest is forgotten.
Of course correct would actually be that the last "Quit/N" is the one that triggers the quit. Thus, the operation queue clear feature would also make this more correct.
If we have multiple RunTests and the last RunTest call is with Instrumentation we end up with:
"SaveHistoryLog();Quit/N;SaveHistoryLog();Quit/N;... ...RELOAD CHANGED PROCS COMPILEPROCEDURES ".
which fails. Thus, currently we can not have RunTest calls without instrumentation before a call with instrumentation.
(Except when INSTRUMENTONLY is used).
If we have multiple RunTests and after a RunTest call with Instrumentation a regular RunTest call follows, the IUTF aborts since it expects a Instrumentation reentry to RunTest. It has to Abort since the saved state from the regular RunTest call if it used Background Task reentry would have overwritten the state from instrumentation.

Current status: WM has taken the feature request as new ticket. The feature is not yet implemented. Until then we have to wait.


We now store and display the facebook "cover" for issue #378

This change adds columns to the models and REQUIRES a db migration.
The python code base had, and almost certainly still has, unhandled
exceptions that are being redirected to the http stream, instead of
going to the the "disk" where they can be discovered by Splunk.  I made
some improvements in this area, and the errors now are also printed to
the Python console, but we need to figure out how to log to the "disk"
in parallel with logging to the http stream.
In views_organization, pass the voter_device_id into organization_retrieve_for_api
so that we can determine logged in state.
In views_voter pass through facebook_background_image_url_https to the
sign in code.
In import_export_facebook/controllers cache the facebook_background_image_url_https
and then store it with facebook_manager.create_or_update_facebook_user
In import_export_facebook add facebook_background_image_url_https to the FacebookAuthResponse
and facebook_email columns to the FacebookUser.  ADDED EXCEPTION HANDLING
for every update_or_create() .. this caught real undiagnosed uncaught exceptions.
In organization/controllers added a facebook data heal section to
organization_retrieve_for_api that initializes the Facebook data in the
organization.  organization_retrieve_for_api now sends either Facebook
or Twitter images to the client based on logged in state. In organization_save_for_api
we now also try harder to get correct Facebook data into the organization
object on save.
In Organization/models added column for facebook_background_image_url_https
In wevote_functions/admin, added a handler for uncaught exceptions
In wevote_functions/functions restored a print(message_text) line that
got deleted -- these lines have great value when waiting for multi-hour
sync with master server runs.
In wevote_social/middleware, added a fallback print to console "logger" for
unhandled exceptions that currently are not otherwise detectable except by line
by line debugging of function calls.

👍