[CP Stag] Fix User not redirected to IOU report when logging in after deeplink

Details
Because of changes introduced in https://github.com/Expensify/App/pull/49516, deeplinking logic was moved to onCompleted callback, I missed a case where the onboarding is either undefined or an empty array (PHP layer return an empty array for older accounts). For these cases we early returned and both onCompleted and onNotCompleted callbacks weren't triggered.
Fixed Issues
$ https://github.com/Expensify/App/issues/49798
PROPOSAL: N/A
Tests
Preconditions: Account with existing IOU report, IOU report URL copied and navigate to some other report

Log out of the app if logged in
Navigate to IOU report URL
Log in with the account from preconditions

Offline tests
N/A
QA Steps
N/A
PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

[x] Android: Native
[x] Android: mWeb Chrome
[x] iOS: Native
[x] iOS: mWeb Safari
[x] MacOS: Chrome / Safari
[x] MacOS: Desktop

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is approved by marketing by adding the Waiting for Copy label for a copy review on the original GH to get the correct copy.
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native
https://github.com/user-attachments/assets/c8397e4b-d00a-406b-a255-bb22996d9a1d

iOS: Native
https://github.com/user-attachments/assets/0f296951-c7f3-4b6a-8295-5b6a85f2090e

MacOS: Chrome / Safari
https://github.com/user-attachments/assets/d75c37e1-bdd4-4296-8243-91dc7eb20a7f

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.


can't get rid of untitled tabs

There are two problems with untitled tabs.  These untitled tabs are created with atom.workspace.open().

When there is an untitled tab with contents, and you close Atom and select Don't Save, when atom reopens the untitled tab reappears with no contents.  This happens even when there are multiple normal tabs.  If you do this over and over you get more and more untitled tabs.

When my code executes editor.delete() for an untitled tab the contents are deleted but the tab view doesn't go away.

These seem like the same bug to me.
windows 8.0   --  atom 0.138.0

@mark-hahn are you still experiencing the second issue?  The first one has been fixed in the 1.4.0 betas due to the new "autosave" feature for untitled tabs.

the contents are deleted but the tab view doesn't go away.
are you still experiencing the second issue?

I would have to put together a test to check this.  Let's assume it's also fixed until someone complains.


Combine dagger listen and dagger session

These two commands are quite similar to the point where they should probably be combined into one. This will require some thinking since dagger session has a json output consumed the SDKs that isn't ideal for humans using dagger listen among other little issues like that. These can most likely be addressed through flags that tweak the behavior (i.e. a flag to enable json output that the sdks use).
This is a non-essential spin off task from the previous overall effort to update the session interface: https://github.com/dagger/dagger/issues/3830

Is this issue still relevant @sipsma ? And is there any work I can do on that to help?

@TomChv we should probably do this someday, but I wouldn't consider it especially high priority at the moment. It's a small simplification to just internal code.


Fix incorrect implementation of logsumexp

Off by a_n.max() for the final value, needs to be added back in after the call to log
Use the scipy.special.logsumexp implementation (used elsewhere) rather than re-implement

Doesn't look like MultiTargetDesign is used, so feel free to close this PR. Just happened to see the bug when reading the code.
Description
Noticed that a custom implementation of logsumexp was incorrect, as it didn't add back in a_n.max().
Motivation and context
Incorrect implementation, will produce non-normalized log probabilities for the class MultiTargetDesign

No associated case
How has this been tested?
Tested by the following python script
import numpy as np
from numpy.typing import NDArray
from scipy.special import logsumexp

def old_log_sum_exp(vals: NDArray):
    return np.log(np.sum(np.exp(vals - vals.max())))

rng = np.random.default_rng(2023)

log_prob = rng.normal(size=1000, loc=1000)

assert not np.all(np.isclose(np.sum(np.exp(log_prob)), 1.0))

# Verify that the logsumexp from scipy produces a normalized log probability
norm_log = log_prob - logsumexp(log_prob)
print("Sum of probabilities (scipy.special.logsumexp)", np.sum(np.exp(norm_log)))
# Sum of probabilities (scipy.special.logsumexp) 0.9999999999999626
assert np.all(np.isclose(np.sum(np.exp(norm_log)), 1.0))

bad_norm_log = log_prob - old_log_sum_exp(log_prob)
print("Sum of probabilities (old logsumexp)", np.sum(np.exp(bad_norm_log)))
# Sum of probabilities (old logsumexp) inf
assert np.all(np.isclose(np.sum(np.exp(bad_norm_log)), 1.0)), np.sum(
    np.exp(bad_norm_log)
)  # Fails

Change log

Fix log probability normalization in `MultiTargetDesign`

@badisa Thank you for your contribution! Even if we don't end up really using this function, it would be good for it to be correct!

@badisa Thank you for your contribution! Even if we don't end up really using this function, it would be good for it to be correct!

Looks like the tests failed due to being unable to get the OE license, let me know if I need to do anything to resolve that.

Yah this is an issue with it being a fork, I will need to make this PR under a branch attached to the main repo, I can do that right now

This "tricks" github into running the tests here as well as https://github.com/choderalab/perses/pull/1239 since it is the same commit

@ijpulidos This PR has more context, do you mind reviewing this one?

The code is the same btw @ijpulidos


fixed typo error in infra proxy client components/automate-ui/src/app/entities/clients/client.effects.ts file

Signed-off-by: Vinay Sharma<EMAIL_ADDRESS>:nut_and_bolt: Description:
In client.effects.ts file have some typo error because I was copied this code part from environment.effect.ts file.

:chains: Related Resources
https://github.com/chef/automate/issues/4243
:+1: Definition of Done
I have made some minor changes in components/automate-ui/src/app/entities/clients/client.effects.ts
:athletic_shoe: How to Build and Test the Change
:white_check_mark: Checklist

[ ] I have read the CONTRIBUTING document.
[ ] Tests added/updated?
[ ] Docs added/updated?
[ ] All commits have been signed-off for the Developer Certification of Origin.

@vinay033 thanks. not a big deal, it just confused me for a minute before I realized it was an accident.


[Fix][Rest-API] fix submit job api

Purpose of this pull request
close #5699

Does this PR introduce any user-facing change?

How was this patch tested?

use postman
Check list

[ ] If any new Jar binary package adding in your PR, please add License Notice according
New License Guide
[ ] If necessary, please update the documentation to describe the new feature. https://github.com/apache/seatunnel/tree/dev/docs
[ ] If you are contributing the connector code, please check that the following files are updated:

Update change log that in connector document. For more details you can refer to connector-v2
Update plugin-mapping.properties and add new connector information in it
Update the pom file of seatunnel-dist

[ ] Update the release-note.

Could you add a test case for this? Seem like this is a very important feature we shouldn't missed. It's weird we don't have a test case to cover it. cc @liugddx

Could you add a test case for this? Seem like this is a very important feature we shouldn't missed. It's weird we don't have a test case to cover it. cc @liugddx

reuse the RestApiIT, but change something.

remove Common.setDeployMode before startup
when start the st cluster with ./bin/seatunnel-cluster.sh -d command, the deployMode will be null, so delete this setup to keep consistency

remove parameter as they are optional when submit job.
when submit job i think they all should be null. when re-store job they need have value.


docker dev env

I can't get get dtr to authenticate with pas locally or as part of this docker set up. There's no issues with the logic servers or with the PAS AEGIS tests so this is not a bug but user error on my part, I must be messing up the registration step or something. If anyone reviewing this is able to test authentication between pas and dtr and get it to work, please respond to this comment


Error compiling and running example runners/ash

Expected Behaviour
Example runners/ash compiles and runs.
Example & Steps To Reproduce

git clone https://github.com/Rust-GPU/rust-gpu
cd rust-gpu/yard-rs/example-xp/rust-gpu/examples/runners/ash
cargo run --release
error:

thread 'main' panicked at examples/runners/ash/src/main.rs:255:10:
called `Result::unwrap()` on an `Err` value: CratePathDoesntExist("examples/shaders/sky-shader")

Following the working example multibuilder, one can change the error line from
SpirvBuilder::new("examples/shaders/sky-shader", "spirv-unknown-vulkan1.1")

to
SpirvBuilder::new(concat!(env!("CARGO_MANIFEST_DIR"), "/../../shaders/sky-shader"), "spirv-unknown-vulkan1.1")

Now the example and the shader crate compiles, but running it gives an error
[mvk-error] VK_ERROR_EXTENSION_NOT_PRESENT: Vulkan extension VK_KHR_shader_non_semantic_info is not supported.
thread 'main' panicked at examples/runners/ash/src/main.rs:441:22:
called `Result::unwrap()` on an `Err` value: ERROR_EXTENSION_NOT_PRESENT

This might be fixable by updating ash, or might not be fixable at the moment. In the latter case, an explicit "support matrix"-ish table would be nice.
System Info

Rust: rustc 1.79.0-nightly (244da22fa 2024-04-23)
OS: MacBook Pro M1, 16-inch, 2021, macOS 14.4.1 (23E224)
GPU: Integrated
SPIR-V: SPIRV-Tools v2024.3 unknown hash, 2024-06-20T14:29:42+00:00

Backtrace
N/A

Backtrace

<backtrace>

CratePathDoesntExist("examples/shaders/sky-shader")

It can also be worked around by doing cargo run --bin example-runner-ash in the root of the repo, but ideally your way should also work

VK_ERROR_EXTENSION_NOT_PRESENT: Vulkan extension VK_KHR_shader_non_semantic_info is not supported

That is your device / driver not supporting the VK_KHR_shader_non_semantic_info extension, which should be available on literally all platforms. As you're on MacOS: The MoltenVK driver also lists this extension as supported, so could you try updating it?

Thanks for the reply!
For the path issue, it's better to make it robust despite the working directory.
For the Vulkan extension issue, the version of MoltenVK in use is determined by
[target.'cfg(target_os = "macos")'.dependencies]
ash-molten = { version = "0.13.1", features = ["pre-built"] }

so I try bumping this, unfortunately none worked, the result is:
v0.14.0+1.1.10:  VK_ERROR_EXTENSION_NOT_PRESENT: Vulkan extension VK_KHR_shader_non_semantic_info is not supported

v0.15.0+1.2.2:
[mvk-error] VK_ERROR_EXTENSION_NOT_PRESENT: Vulkan extension VK_KHR_shader_non_semantic_info is not supported.
[mvk-error] VK_ERROR_FEATURE_NOT_PRESENT: vkCreateDevice(): Requested feature is not available on this device.
[mvk-info] Created VkDevice to run on GPU Apple M1 Pro with the following 1 Vulkan extensions enabled:
                VK_KHR_swapchain v70
thread 'main' panicked at examples/runners/ash/src/main.rs:441:22:

v0.16.0+1.2.6:

[mvk-error] VK_ERROR_FEATURE_NOT_PRESENT: vkCreateDevice(): Requested physical device feature specified by the 1st flag in VkPhysicalDeviceVulkanMemoryModelFeatures is not available on this device.
[mvk-info] Created VkDevice to run on GPU Apple M1 Pro with the following 2 Vulkan extensions enabled:
                VK_KHR_shader_non_semantic_info v1
                VK_KHR_swapchain v70
[mvk-info] Destroyed VkDevice on GPU Apple M1 Pro with 2 Vulkan extensions enabled.

v0.17.0+1.2.7:
[mvk-error] VK_ERROR_FEATURE_NOT_PRESENT: vkCreateDevice(): Requested physical device feature specified by the 1st flag in VkPhysicalDeviceVulkanMemoryModelFeatures is not available on this device.

v0.18.0+1.2.8:
[mvk-error] VK_ERROR_FEATURE_NOT_PRESENT: vkCreateDevice(): Requested physical device feature specified by the 1st flag in VkPhysicalDeviceVulkanMemoryModelFeatures is not available on this device.
[mvk-info] Created VkDevice to run on GPU Apple M1 Pro with the following 2 Vulkan extensions enabled:
                VK_KHR_shader_non_semantic_info v1
                VK_KHR_swapchain v70

v0.19.0+1.2.8:

compilation error:
error[E0308]: mismatched types
   --> examples/runners/ash/src/main.rs:338:38
    |
338 |                     .create_instance(&instance_create_info, None)
    |                      --------------- ^^^^^^^^^^^^^^^^^^^^^ expected `&InstanceCreateInfo<'_>`, found `&InstanceCreateInfoBuilder<'_>`
    |                      |
    |                      arguments to this method are incorrect
    |
    = note: expected reference `&ash::vk::definitions::InstanceCreateInfo<'_>`
               found reference `&InstanceCreateInfoBuilder<'_>`

...omitted...

Per MoltenVK's changelog, the support for VK_KHR_shader_non_semantic_info is added in MoltenVK 1.2.5, so at least not present in the version v0.13.1+1.1.10 of ash-molten in use.
For the error log above, one can see that indeed after v0.16.0+1.2.6, it starts to complain about another extension: "Requested physical device feature specified by the 1st flag in VkPhysicalDeviceVulkanMemoryModelFeatures is not available on this device" and the VK_KHR_shader_non_semantic_info v1 is successfully enabled.

rust-gpu always writes it's shaders as requiring the VulkanMemoryModel to make sure it's atomic intrinsics work correctly (as before the vulkan memory model atomics were very vague about how they should actually work), even if the shaders themselves don't use atomics. And again it was assumed every major vendor has implemented it, given how critical it is. So I'm very surprised to be unable to even find a mention of that extension in MoltenVK's docs.
And I would guess most devs using apple have been using it via wgpu, so noone noticed the regression.
I'll be forwarding this issue.


Option to export textures as they are.

Is your feature request related to a problem? Please describe.
I import some nice optimized .webp textures into blender, but when I export I can only choose "jpg" or "automatic".  Both options lead to less optimized textures and a much larger file size.
Describe the solution you'd like
There should be an option to export the textures exactly as they are currently on disk.

Hello,
Webp is not allowed in core glTF specification, but is available via an extension. (  https://github.com/KhronosGroup/glTF/blob/main/extensions/2.0/Vendor/EXT_texture_webp/README.md )
This extension is not implemented in Blender glTF I/O yet.
Mark as duplicated, as this request is already in various tickets ( #1308 )

This is different than #1308.

#1308 asks for a new mode that converts images to WebP.
This asks for "Automatic" to export WebP images as they are, the same way it exports PNG/JPEG as they are.


feat(): KubeSlice Events CRD + Events Refactor

Description
Features:

Changes to sliceConfig CRD to add kubesliceEvents in status
Refactor the events as per the library change
Addition of events for worker CRs.

How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration

[x] Manual testing
[x] Unit tests

Checklist:

[ ] The title of the PR states what changed and the related issues number (used for the release note).
[ ] Does this PR requires documentation updates?
[ ] I've updated documentation as required by this PR.
[ ] I have performed a self-review of my own code.
[ ] I have commented my code, particularly in hard-to-understand areas.
[ ] I have tested it for all user roles.
[ ] I have added all the required unit test cases.

Does this PR introduce a breaking change for other components like worker-operator?

report link  'https://kubeslice.github.io/e2e-allure-reports/Kind-kubeslice-controller-2023-03-30T15:01:21-master-126/index.html'


some error i found when generate doc

Environment：python3

Have you ever tested the document py3.5 docstring? If the error comes from the docstring syntax, we can adjust the comments to ensure the document generation.


Snap version of hugo throws relocation error

I am using the snap version of hugo for sometime. But now I can't run hugo. Every time when I try to run hugo, this error shows up:
/snap/hugo/1455/bin/hugo: relocation error: /snap/hugo/1455/lib/x86_64-linux-gnu/libpthread.so.0: symbol __mmap, version GLIBC_PRIVATE not defined in file libc.so.6 with link time reference

I have removed and installed hugo snap again, but the error persists.
$ snap list
Name   Version    Rev   Developer     Notes
core   16-2.31.2  4206  canonical     core
hugo   0.37.1     1455  hugo-authors  -
rg     0.8.1      15    tasdomas      -

I am using Ubuntu 17.10
Thank you for building such a useful project!

See this thread: https://discourse.gohugo.io/t/hugos-snap-stopped-working/11184/27
I will track this in another issue.


blog

blog/announcements thing

Cool idea! Would a new post be made every update(e.g. bug fixes), or would it be when something big happens(e.g. new ui)?

Most likely every non-minor update


fix(deps): update dependency vue-i18n to v9

This PR contains the following updates:

Package
Type
Update
Change

vue-i18n
dependencies
major
^8.4.0 -> ^9.0.0

Release Notes

intlify/vue-i18n-next
v9.1.4
Compare Source
:zap: Improvement Features

core-base, devtools-if, vue-i18n

#450 experimental: fix devtools-if (@kazupon)

:pencil: Documentation

#449 Japanese translation (~essential) (@noy4)

Committers: 2

@noy4
kazuya kawaguchi (@kazupon)

v9.1.3
Compare Source
:zap: Improvement Features

core-base, vue-i18n

#446 experimental: improve meta for intlify devtools (@kazupon)

Committers: 1

kazuya kawaguchi (@kazupon)

v9.1.2
Compare Source
:bug: Bug Fixes

vue-i18n

#441 fix: typing errors (@kazupon)

Committers: 1

kazuya kawaguchi (@kazupon)

v9.1.1
Compare Source
:bug: Bug Fixes

vue-i18n

#436 fix: cannot defined feature flags accessing (@kazupon)

Committers: 1

kazuya kawaguchi (@kazupon)

v9.1.0
Compare Source
:star: Features

core-base, devtools-if, vue-i18n

#433 experimental: Hooking for @intlify/devtools (@kazupon)

core-base, vue-i18n

#411 feat: resolve locale message translation new API rt (@kazupon)

message-resolver, shared, vue-i18n

#402 Add support for flat json separated with dot('.') (@PeterAlfredLee)

vue-i18n

#386 feat: Vue I18n Data Editing at DevTools (@kazupon)

:bug: Bug Fixes

vue-i18n

#404 fix: suppress console for devtools flag (@kazupon)
#403 fix: cannot fallback at tm / $tm (@kazupon)
#374 fix: cannot warn fallback root (@kazupon)

message-compiler

#372 fix: cannot use underscore as indentifier (@kazupon)

:zap: Improvement Features

core-base, vue-i18n

#422 fix: Intl type definition for TS 4.2 (@kazupon)

core-base

#417 Coherent update from 'best-fit' to 'best fit' (@ValdoGhafoor)

message-compiler, shared, vue-i18n

#397 fix: Support for browsers that don't support object spread literals (@kazupon)

vue-i18n

#387 improvement: Vue I18n Devtools plugin info (@kazupon)
#384 support suppress esm-bundler feature flags warning (@kazupon)
#368 improvement: upgrade vue devtools (@kazupon)

:boom: Breaking Change

core-base, size-check-vue-i18n, vue-i18n

#434 breaking: split devtools production feature flags (@kazupon)

To provide experimental features for @intlify/devtools, feature flags have been separated as follows.

__VUE_I18N_PROD_DEVTOOLS__: enable/disable vue-devtools support in production, default: false
__INTLIFY_PROD_DEVTOOLS__: enable/disable @intlify/devtools support in production, default: false

Previously, __INTLIFY_PROD_DEVTOOLS__ setting flagged the use of both vue-devtools and @intlify/devtools in production.
In later v9.1, The feature flags for vue-devtools are now enabled/disabled by setting __VUE_I18N_PROD_DEVTOOLS__.
:pencil: Documentation

Other

#420 Fix typos in Composition API page (@FlandreDaisuki)
#406 Add easy-i18n as third-party tool (@marhali)

vue-i18n

#370 Fix typo in docstring (@kuanyen)

Committers: 6

Chun-Hao Lien (@FlandreDaisuki)
Lee (@PeterAlfredLee)
Marcel (@marhali)
Valdo Ghafoor (@ValdoGhafoor)
Yen Kuan (@kuanyen)
kazuya kawaguchi (@kazupon)

v9.0.0
Compare Source
See the below link:
https://blog.intlify.dev/posts/vue-i18n-9.html

Configuration
📅 Schedule: At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR is behind base branch, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box.

This PR has been generated by Renovate Bot.

⚠ Artifact update problem
Renovate failed to update an artifact related to this branch. You probably do not want to merge this PR as-is.
♻ Renovate will retry this branch, including artifacts, only when one of the following happens:

any of the package files in this branch needs updating, or
the branch becomes conflicted, or
you check the rebase/retry checkbox if found above, or
you rename this PR's title to start with "rebase!" to trigger it manually

The artifact failure details are included below:
File name: @uportal/eyebrow-user-info/package-lock.json
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
npm notice
npm notice New minor version of npm available! 7.7.6 -> 7.9.0
npm notice Changelog: <https://github.com/npm/cli/releases/tag/v7.9.0>
npm notice Run `npm install -g<EMAIL_ADDRESS>to update!
npm notice
npm ERR! code ERESOLVE
npm ERR! ERESOLVE unable to resolve dependency tree
npm ERR!
npm ERR! While resolving<EMAIL_ADDRESS>npm ERR! Found<EMAIL_ADDRESS>npm ERR! node_modules/eslint
npm ERR!   dev<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   @uportal/api-template-vue
npm ERR!
npm ERR! Could not resolve dependency:
npm ERR! peer eslint@">= 1.6.0 < 7.0.0" from<EMAIL_ADDRESS>npm ERR! node_modules/@vue/cli-plugin-eslint
npm ERR!   dev<EMAIL_ADDRESS>from<EMAIL_ADDRESS>npm ERR!   @uportal/api-template-vue
npm ERR!
npm ERR! Fix the upstream dependency conflict, or retry
npm ERR! this command with --force, or --legacy-peer-deps
npm ERR! to accept an incorrect (and potentially broken) dependency resolution.
npm ERR!
npm ERR! See /tmp/renovate/cache/others/npm/eresolve-report.txt for a full report.

npm ERR!


Pretrained model?

Are you planning to release a trained model? I'm interested to see how this model compares in terms of image quality and inference speed.

It would be most appreciated!
On a related note, that dataset link you provided for the LSRW dataset needs a Baidu account, which I cannot easily create as someone who doesn't live in China. The LOL-real and LOL-sys links provided only contain a few results, not training or validation data. If you can also upload those datasets to website that doesn't require an account to download like Google Drive, Wetransfer or Dropbox, that would be very helpful!

You can provide an email address and I directly send to you.
--------------原始邮件--------------
发件人："Fred-Erik @.>;
发送时间：2023年8月15日(星期二) 晚上7:49
收件人："wangchx67/FourLLIE" @.>;
抄送："王晨曦 @.>;"Comment @.>;
主题：Re: [wangchx67/FourLLIE] Pretrained model? (Issue #1)
It would be most appreciated!
On a related note, that dataset link you provided for the LSRW dataset needs a Baidu account, which I cannot easily create as someone who doesn't live in China. The LOL-real and LOL-sys links provided only contain a few results, not training or validation data. If you can also upload those datasets to website that doesn't require an account to download like Google Drive, Wetransfer or Dropbox, that would be very helpful!
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

Thank you for the pretrained models you sent! I've tried a few of them on my dataset but I think I might have a denoising problem instead of a low-light image enhancement problem.
Inputs:

Simple auto leveling results:

Result with your model:

It doesn't improve much compared to simply using auto levels. And the result still looks bad, but it seems to mainly be due to the very present noise.

Actually, the noise distribution of real scence
is very different with that of existing LLIE datasets (e.g., LSRW and LOL). Maybe you can try to train the model in SID, or you can calibirate the noise distribution of your own dataset with the camera settings and re-train the model.
--------------原始邮件--------------
发件人："Fred-Erik @.>;
发送时间：2023年8月15日(星期二) 晚上10:43
收件人："wangchx67/FourLLIE" @.>;
抄送："王晨曦 @.>;"Comment @.>;
主题：Re: [wangchx67/FourLLIE] Pretrained model? (Issue #1)
Thank you for the pretrained models you sent! I've tried a few of them on my dataset but I think I might have a denoising problem instead of a low-light image enhancement problem.
Inputs:
Simple auto leveling results:
Result with your model:
It doesn't improve much compared to simply using auto levels. And the result still looks bad, but it seems to mainly be due to the very present noise.
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you commented.Message ID: @.***>

<EMAIL_ADDRESS>


Audio effects killswitch / reset

When changing a scene etc. we generally don't want trailing audio effects (such as reverb) to carry over to the new environment.
I am able to fade effects down using mixer buses with volume attenuation, but I can't find a good way to clear the audio buffers whilst faded down. Turning the effect off-and-on-again doesn't work.
Currently in my game, long reverb tails can be heard during the following scene's fade-up.
Apologies if there is already a solution for this, I have been developing frameworks with both Godot and Unity for a while and never managed to crack this problem! Where necessary, I've ended up baking reverb into sounds, as they can be cleared and reset... obviously this is not a memory-optimal solution.

Perhaps a workaround would be to remove the reverb from the effect chain?

Perhaps a workaround would be to remove the reverb from the effect chain using a script?

That's a good suggestion for many cases, but as the Audio Mixer's arrangement is effectively global state I wouldn't want to be manipulating it in that way.

@matwhill I mean, if you still want that reverb after, you could add/remove it immediately at the same index? That would effectively reset the states.

That's a good point! In my case I would be 'resetting' from a global manager anyway so it makes sense to create a DSP killswitch that way. I'll test this tonight!
I'm interested to see if anyone wants to implement this anyway. I don't really know what Godot's DSP code-base looks like but if this is trivial, having a mixer.clearBuffers() etc. might be worthwhile!

Sorry the massive delay... can confirm that:
# could be replaced in future, work-around suggested by: github.com/Zylann func _kill_reverb(): 	for bus in buses: 		var reverb = AudioServer.get_bus_effect(bus, 0) 		AudioServer.remove_bus_effect(bus, 0) 		AudioServer.add_bus_effect(bus, reverb, 0)
...works fine :)
Gonna leave this open for now as some others seemed into the idea of clearing buffers manually? Feel free to close though!

Feature and improvement proposals for the Godot Engine are now being discussed and reviewed in a dedicated Godot Improvement Proposals (GIP) (godotengine/godot-proposals) issue tracker. The GIP tracker has a detailed issue template designed so that proposals include all the relevant information to start a productive discussion and help the community assess the validity of the proposal for the engine.
The main (godotengine/godot) tracker is now solely dedicated to bug reports and Pull Requests, enabling contributors to have a better focus on bug fixing work. Therefore, we are now closing all older feature proposals on the main issue tracker.
If you are interested in this feature proposal, please open a new proposal on the GIP tracker following the given issue template (after checking that it doesn't exist already). Be sure to reference this closed issue if it includes any relevant discussion (which you are also encouraged to summarize in the new proposal). Thanks in advance!


[NVIDIA Container] Fix PATH to include NVIDIA binaries

This branch addresses and fix a PATH issue in the NVIDIA containers.
docker run -it \
    --gpus=all \
    gcr.io/iree-oss/nvidia-bleeding-edge bash

# %%%% Container is starting  %%%%

# As you can see `nvcc` is not in the PATH
root@12c0c715d753:/ nvcc --version
bash: nvcc: command not found

# Now let's fix the issue "by hand" and try again
root@12c0c715d753:/ PATH=${PATH}:/usr/local/cuda/bin/
root@12c0c715d753:/ nvcc --version

nvcc: NVIDIA (R) Cuda compiler driver
Copyright (c) 2005-2022 NVIDIA Corporation
Built on Wed_Sep_21_10:33:58_PDT_2022
Cuda compilation tools, release 11.8, V11.8.89
Build cuda_11.8.r11.8/compiler.31833905_0

This simple PR fixes the problem.
@ScottTodd & @GMNGeoffrey  for review

@ScottTodd how does it work to merge to PR once approved ?

@ScottTodd how does it work to merge to PR once approved ?

https://github.com/openxla/iree/blob/main/CONTRIBUTING.md#merging

It is assumed that the PR author will merge their change unless they ask someone else to merge it for them (e.g. because they don't have write access).

(I thought Geoffrey might click merge, but I can do it)


gRPC-web support

Original code from @gertvdijk, thanks! This branch has merge conflicts resolved, etc.

Also thanks to @gsagula for actually fixing the merge conflicts. :smile:

Good job guys!
How soon we will see this feature in release?


Dependencies of local dependency are not packaged.

Hello,
I'm having an issue with a HelmChart which is targeting a folder in a GitRepository.
The chart root located in this folder has a dependency on another local chart, component, specified as such :
dependencies:
- name: component
  version: 0.1.0
  repository: file://../component
  alias: mycomponent

This works fine and if I download the package tgz from the source-controller, it contains the component chart in the charts subfolder.
But, this component chart also has a dependency on postgresql, specified as such :
dependencies:
- name: postgresql
  condition: postgresql.deploy
  version: "9.8.3"
  repository: https://charts.bitnami.com/bitnami

And this is not included in the tgz, which cause my deployment to fail.
For what it's worth, calling helm package on root does package recursively : root/charts/component/charts/postgresql/Chart.yaml, which means a traditional helm install works.
I looked at the code, it seems it is because the dependency resolution is not recursive and https://github.com/fluxcd/source-controller/blob/aed11a171f527f16d121597b3c40cd4eae84332c/internal/helm/dependency_manager.go#L80 does not resolve dependency before loading the subchart.
Is there something I am missing ?
Thank you.

Hello @clement-buchart, thanks for reporting this issue.
I've looked into this and it doesn't look like the helm cli handles dependencies recursively either. For my test case, I created three charts with recursive dependencies as follows:
# recursive-one/Chart.yaml
dependencies:
  - name: recursive-two
    version: "0.1.0"
    repository: "file://../recursive-two"

# recursive-two/Chart.yaml
dependencies:
  - name: recursive-three
    version: "0.1.0"
    repository: "file://../recursive-three"

# recursive-three/Chart.yaml
dependencies:
  - name: grafana
    version: ">=5.7.0"
    repository: "https://grafana.github.io/helm-charts"

The only way to get all the dependencies packaged together recursively via helm package is to priorly run helm dep build . in each of the chart directories.
For reference, this is the helm specific implementation. As you can also probably tell, there is no recursion build and rather dependencies are only resolved at the first level.
I think the use case you presented here makes sense and would be tempted to investigate further for a potential solution.
If you're looking for a temporary workaround, you need to ensure that local dependency charts (e.g. the component chart in your case) have their charts/ directories populated (helm dep build .) and committed to git.

Hello,
Yes, sorry for the misunderstanding : Indeed it works via the helm CLI only if helm dep update is run prior.
And I can also confirm that committing the dependency to git does work, that is the workaround I went with.
I'm glad you'll consider investigating further anyway and will follow this issue.
If I can help with the implementation or testing of a solution, I'll be glad to.

I also run into this issue. I use three local helm charts where the first depend transitively on the last chart. Only the first two are deploy in the cluster, the manifests of chart which is only transitively referenced is not deployed to the cluster.
Are there any plans to fix or workaround the helm limitation, which does not require me to commit packaged charts into my git repository?
An alternative would be to use a dedicated helm repository instead of a git repository for helm charts. But this would add additional complexity and CI pipeline effort to implement the release process.

(Subscribing to this issue).
I am interested conceptually in solutions which can help test packaged dependencies together without requiring a release first. I am not sure whether this is possible now, historically I have just used a beta chart repo where prerelease charts can go, since helm dep update is in the build, but this is feeling quite extra and seems cumbersome.
An effective pipeline for streamlining helm chart releases and easy validation/testing of prereleases is something I would consider as highly desirable as a use case example for Flux.


Deprecate bindPhase and skipPhase

Recommend Dep.Phase.>>= and pure () Dep.Phase.>> instead (with or without -XQualifiedDo).

Better only deprecate skipPhase for now 45306a26250c3e8331336b0814dbbd2dd12b5928.


Be able to template (non-interrupting) start events inside event sub processes

Problem you would like to solve
I have a hard time to model non-interrupting start events along with connectors without editing the XML.
Proposed solution
Non-interrupting start event connectors embed intuitively within the existing modeling UX: Whatever can be modeled as an interrupting start event can also be modeled as a non-interrupting start event. This is because both are the same internally, with non-interrupting simply triggering other external effects (done by the BPMN engine):

[ ] I can create start event connectors either as interrupting or non interrupting from the create menu
[ ] In can replace from interrupting to non-interrupting (connectors) without loosing the connector details
[x] If I apply a connector template on a non-interrupting start event, then the non-interrupting nature is kept (https://github.com/bpmn-io/bpmn-js-element-templates/issues/20).
[ ] I can create a start event (or any element) within a specific context, binding additional properties (https://github.com/bpmn-io/bpmn-js-element-templates/issues/19)

Alternatives considered

Be able to define specific element templates for interrupting and non-interrupting usage
Be able to define "conditional, based on applied location" element templates (https://github.com/bpmn-io/bpmn-js-element-templates/issues/19)

Additional context
The following shows the standard interaction that core modeling provides to support interrupting vs. non-interrupting events:

With the proposal we simply want to ensure that templated start events plug into this intuitively.

Raised via https://github.com/camunda/product-gaps/issues/109.

Sounds reasonable, see my comment related to this ticket: https://github.com/camunda/product-gaps/issues/109#issuecomment-1752805359

Initial Investigation
Within event sub-processes a message start event must bind the correlationKey to something used-defined to signify how the message is being correlated:

This implies that we need a mechanism for contextual application of a property (https://github.com/bpmn-io/bpmn-js-element-templates/issues/19) or users would need to create two different element templates, for nearly similar templates.

You are right, this is not yet fixed upstream. Only part of it is implemented. Moving back to Ready

@marstamm Could you share an update regarding this issue? To me it seems like it is fixed upstream, with all components including https://github.com/bpmn-io/bpmn-js-element-templates/issues/19 taken care of.

We were missing correlation key conditions in the previous release.
Implementation for the conditional correlation keys in element-templates are done and docs are merged. This will be integrated and released with the Web-modeler alpha/Desktop modeler minor release.

Included via https://github.com/camunda/camunda-modeler/pull/4009


[hi] Localize service tutorial in hindi

Description
This PR will add -

Localization of service tutorial in Hindi
Add kubernetes manifests files

Closes: #47354

Related Page -> https://kubernetes.io/docs/tutorials/services/

/remove-lifecycle rotten


Added Binary Search Algorithm

Added a program that searches for an element from an array using binary search and displays the index at which it found.
This is for hacktoberfest-2022 .Kindly merge this request.

@jayaS1008  Kindly raise an issue and get the issue assigned first and then place the PR

@jayaS1008 Kindly raise an issue and get the issue assigned first and then place the PR

Kindly follow the above steps and then open a fresh PR


Add an option to filter on CIS specific controls so that LW added controls are not included

Compliance with CIS recommendations is often a minimum requirement that must be satisfied. LW adds a number of additional best practice recommendations that may not be applicable in all cases. This would allow the ability to only report on CIS (or LW) controls as needed.

JIRA: ALLY-495


Add further reading links

Yeah wow, I went through and checked them all and you're absolutely spot on. Thanks for the contribution!


fix: IAM as service-group-id

Description
When using pseudo service IAM, only service-group-id should be specified.
Git Issue
Release required?

[ ] No release
[x] Patch release (x.x.X)
[ ] Minor release (x.X.x)
[ ] Major release (X.x.x)

Release notes content

Run the pipeline
If the CI pipeline doesn't run when you create the PR, the PR requires a user with GitHub collaborators access to run the pipeline.
Run the CI pipeline when the PR is ready for review and you expect tests to pass. Add a comment to the PR with the following text:
/run pipeline

Checklist for reviewers

[ ] If relevant, a test for the change is included or updated with this PR.
[ ] If relevant, documentation for the change is included or updated with this PR.

For mergers

Use a conventional commit message to set the release level. Follow the guidelines.
Include information that users need to know about the PR in the commit message. The commit message becomes part of the GitHub release notes.
Use the Squash and merge option.

/run pipeline

/run pipeline

/run pipeline

/run pipeline

:tada: This issue has been resolved in version 1.23.2 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


[Bug]: instance.rds.aws.upbound.io/v1beta2 Created with a default name

Is there an existing issue for this?

[X] I have searched the existing issues

Affected Resource(s)

rds.aws.upbound.io/v1beta2 - Instance

Resource MRs required to reproduce the bug
apiVersion: rds.aws.upbound.io/v1beta2
kind: Instance
metadata:
  name: name-issue
spec:
  deletionPolicy: Delete
  forProvider:
    allocatedStorage: 100
    allowMajorVersionUpgrade: true
    applyImmediately: true
    autoMinorVersionUpgrade: false
    backupRetentionPeriod: 1
    copyTagsToSnapshot: true
    dbName: mydb
    dbSubnetGroupNameRef:
      name: REPLACEME
    engine: mysql
    engineVersion: 8.0.35
    instanceClass: db.t3.micro
    passwordSecretRef:
      key: password
      name: name-issue
      namespace: default
    region: us-east-1
    skipFinalSnapshot: true
    storageEncrypted: true
    username: root
    vpcSecurityGroupIdRefs:
    - name: REPLACEME
  managementPolicies:
  - '*'
  providerConfigRef:
    name: providerconfig-family-aws
  publishConnectionDetailsTo:
    configRef:
      name: default
    name: name-issue

Steps to Reproduce

Apply the provided manifest
Check AWS console

What happened?

Name in the AWS console is not what we should expect

Relevant Error Output Snippet
Output trimmed for clarity

apiVersion: rds.aws.upbound.io/v1beta2
kind: Instance
metadata:
  name: testalex-rdsinstance-r74cm
spec:
  deletionPolicy: Delete
  forProvider:
    allocatedStorage: 100
    applyImmediately: true
    autoMinorVersionUpgrade: true
    availabilityZone: us-east-1d
    backupRetentionPeriod: 1
    backupWindow: 06:16-06:46
    caCertIdentifier: rds-ca-rsa2048-g1
    dbName: mydb
    dbSubnetGroupName: default-rds-eks77-tst-us-east-1
    dbSubnetGroupNameRef:
      name: default-rds-eks77-tst-us-east-1
    deleteAutomatedBackups: true
    engine: mysql
    engineVersion: 8.0.35
    instanceClass: db.t3.micro
    licenseModel: general-public-license
    maintenanceWindow: thu:08:20-thu:08:50
    networkType: IPV4
    optionGroupName: default:mysql-8-0
    parameterGroupName: default.mysql8.0
    passwordSecretRef:
      key: password
      name: testalex-rdsinstance
      namespace: testalex
    port: 3306
    region: us-east-1
    skipFinalSnapshot: true
    storageType: gp2
    username: root
    vpcSecurityGroupIdRefs:
    - name: default-rds-eks77-tst-us-east-1
    vpcSecurityGroupIds:
    - sg-01caf7e64553aef3d
  initProvider: {}
  managementPolicies:
  - '*'
  providerConfigRef:
    name: providerconfig-family-aws
  publishConnectionDetailsTo:
    configRef:
      name: default
    name: testalex-rdsinstance-r74cm
status:
  atProvider:
    address: terraform-20240207150854356000000001.cmcypbsqbicb.us-east-1.rds.amazonaws.com
    allocatedStorage: 100
    applyImmediately: true
    arn: arn:aws:rds:us-east-1:134842860454:db:terraform-20240207150854356000000001
    autoMinorVersionUpgrade: true
    availabilityZone: us-east-1d
    backupRetentionPeriod: 1
    backupWindow: 06:16-06:46
    caCertIdentifier: rds-ca-rsa2048-g1
    characterSetName: ""
    copyTagsToSnapshot: false
    customIamInstanceProfile: ""
    customerOwnedIpEnabled: false
    dbName: mydb
    dbSubnetGroupName: default-rds-eks77-tst-us-east-1
    deleteAutomatedBackups: true
    deletionProtection: false
    domain: ""
    domainIamRoleName: ""
    endpoint: terraform-20240207150854356000000001.cmcypbsqbicb.us-east-1.rds.amazonaws.com:3306
    engine: mysql
    engineVersion: 8.0.35
    engineVersionActual: 8.0.35
    hostedZoneId: Z2R2ITUGPM61AM
    iamDatabaseAuthenticationEnabled: false
    id: db-GKFPAKWSRGYQYCFOG4KXPJQJRU
    instanceClass: db.t3.micro
    iops: 0
    kmsKeyId: ""
    latestRestorableTime: "2024-02-07T15:13:49Z"
    licenseModel: general-public-license
    maintenanceWindow: thu:08:20-thu:08:50
    maxAllocatedStorage: 0
    monitoringInterval: 0
    monitoringRoleArn: ""
    multiAz: false
    ncharCharacterSetName: ""
    networkType: IPV4
    optionGroupName: default:mysql-8-0
    parameterGroupName: default.mysql8.0
    performanceInsightsEnabled: false
    performanceInsightsKmsKeyId: ""
    performanceInsightsRetentionPeriod: 0
    port: 3306
    publiclyAccessible: false
    replicaMode: ""
    replicateSourceDb: ""
    resourceId: db-GKFPAKWSRGYQYCFOG4KXPJQJRU
    skipFinalSnapshot: true
    status: available
    storageEncrypted: false
    storageThroughput: 0
    storageType: gp2
    timezone: ""
    username: root
    vpcSecurityGroupIds:
    - sg-01caf7e64553aef3d
  conditions:
  - lastTransitionTime: "2024-02-07T15:17:55Z"
    reason: Available
    status: "True"
    type: Ready
  - lastTransitionTime: "2024-02-07T15:08:54Z"
    reason: ReconcileSuccess
    status: "True"
    type: Synced
  - lastTransitionTime: "2024-02-07T15:17:54Z"
    reason: Success
    status: "True"
    type: LastAsyncOperation

Crossplane Version
1.14.2-up.1
Provider Version
1.0.0
Kubernetes Version
1.26
Kubernetes Distribution
EKS
Additional Info
No response

With the introduction of the v1beta2 API version, there's a configuration change for this resource in the v1.0.0 version of the provider. You now need to specify the database identifier as follows:
piVersion: rds.aws.upbound.io/v1beta2
kind: Instance
metadata:
  name: name-issue
spec:
  deletionPolicy: Delete
  forProvider:
    dbName: mydb
    identifier: testidentifier
...

, which results in the given identifier being assigned to the provisioned database:

Could you please add the spec.forProvider.identifier parameter to your manifest?

@ulucinar is it possible to override the default terraform-xyz default string with upjet ?


Remove makefile and use npm scripts

Nothing to fancy here, just removed the makefile and used xo directly in the npm script.

Could you also add this to package.json:
{
  "xo": {
    "extends": "vdemedes",
    "env": "node"
  }
}

oh and "eslint-config-vdemedes": "*" in package.json devDependencies

Voila :).

Ok, great, thanks! Now only squash your commits and it's ready to merge ;)

Done!


FEATURE: Select which links should be used in web scraper nodes (cheerio, puppeteer, and playwright)

Adds a Manage Links button to Web Scraper nodes like Cheerio, Puppeteer, and Playwright. Until now, users can't choose which links to scrap. The node just picks the first n links (configurable in Additional Parameters) and scraps their content. Now users can pick which links they want to scrap.
Clicking on the Manage Links button will open a dialog where you can fetch all the links from the given URL, and remove the ones you don't need. During upsert, only the selected links will be scraped. Selecting links is optional. The nodes will fallback to the old behavior when no links are selected.
If Relative Links Method is set in Additional Parameters before selecting links, the manage links dialog will use the selected method to fetch the links.
If Relative Links Limit is set and is smaller than the number of selected links, the limit will apply to the selected links and the first n links are chosen. If it's larger, then all the selected links are scraped.

Bug:
1.) Enter https:flowiseai.com into the Cheerio node:

2.) Open Manage Links and modified to https://docs.flowiseai.com:

3.) Fetch links
4.) Click save
5.) On the canvas, the Cheerio Node URL is still https:flowiseai.com, same as when you click manage links:

@HenryHengZJ Fixed the bug. The URL field in the node will be updated if we change it in the manage links dialog.

@HenryHengZJ Sure! I'll update it :+1:

@HenryHengZJ There's already an isUpsert flag in the buildLangchain() in server/src/index.ts. It's set to true only during upsert operations. When calling the prediction endpoints, it's not set so it won't do upsert. This means the scraping will also only happen during upsert and not during prediction.

@HenryHengZJ There's already an isUpsert flag in the buildLangchain() in server/src/index.ts. It's set to true only during upsert operations. When calling the prediction endpoints, it's not set so it won't do upsert. This means the scraping will also only happen during upsert and not during prediction.

it wont upsert, but it will still go through the init of Cheerio node, scraping all the links, which might take significant portion of the time

@HenryHengZJ Added a condition to skip initializing web scraper nodes during prediction.


Null Exception on BaseGetAllKeys

Hello,
We had a problem occuring several times randomly.
Our server is unable to come back on its own afterwards. We had to recycle on the few times it occured.
Do you have any clue for the cause ? See below for stacktrace
Thanks for your help
Exception message
Object reference not set to an instance of an object.
Stacktrace
at System.Collections.Specialized.NameObjectCollectionBase.BaseGetAllKeys()
at System.Collections.Specialized.NameValueCollection.get_AllKeys()
at DotNetCasClient.Utils.UrlUtil.ConstructValidateUrl(String serviceTicket, Boolean gateway, Boolean renew, NameValueCollection customParameters)
at DotNetCasClient.Validation.TicketValidator.AbstractUrlTicketValidator.Validate(String ticket)
at DotNetCasClient.CasAuthentication.ProcessTicketValidation()
at DotNetCasClient.CasAuthenticationModule.OnAuthenticateRequest(Object sender, EventArgs e)
at System.Web.HttpApplication.SyncEventExecutionStep.System.Web.HttpApplication.IExecutionStep.Execute()
at System.Web.HttpApplication.ExecuteStepImpl(IExecutionStep step)
at System.Web.HttpApplication.ExecuteStep(IExecutionStep step, Boolean& completedSynchronously)
End exception

Uh.... not that it's your fault, but that stack trace is pretty useless, lol.
I'm going to need more context and also reproduction scenarios (full details on what you did to reproduce the problem forcefully.)  E.g. do you have more environments than just production?  Is this problem exhibited in all environments or just one?  In a non-production environment where this problem occurs can you make it so that you are the only person using it, then freshly spin up the app, and does this happen on the first attempt at log on for the sole user of the system OR does it happen seemingly randomly or randomly after a certain amount of time?
What operating system are you running this on (and flavor.)  What version of the .NET framework does your project target?  Is it compiled for x86, x64 or AnyCPU?  What project type is it: e.g. ASP.NET WebForms, Web Pages, MVC (which specific version of the one are you using?)  What version of our NuGet package are you using and are you using the most recent one?  If you are not using the NuGet package and are instead directly referencing DLL's you should probably not be doing that.  Does this error occur at what seems like random?  Does it only occur for a specific user?  Which version of CAS server are you targeting?  Which type and version of authentication ticket are you using (e.g. Cas, Saml, etc?)  What versions of TLS are you using on both your Windows/IIS server and also the server that CAS is running on?
I'm assuming you did your sleuthing as a developer and went over all of this already and have completely exhausted all efforts, but I wasn't there with you so I'll need the infos ;)
Can you also share your casClientConfig section in your web.config file?  For the 3 entries that contain your server names in the URL's, can you just replace just the hostnames with "example.com"?

If you are using the latest version of our NuGet package... have you tried rolling back to each previous version till you reached one that does work?  If so, what was the last working version?

Alright, lot's of question, I'll try to answer each of them precisely :)
By the way, thanks for the help !
I don't have any clue what is creating this problem actually. It went down during this night. This particular app we're talking is an internal web application with around 150 users at least.
Keep in mind that the system is working flawlessly in production 24/6 with ~150 concurrent users logged through SSO so we are not talking of some trivial bug of misconfiguration.
We have production environment and preproduction environment on the same server (about to be changed in coming months to separate both, you may have a clue here because the preproduction stood started last night where we shut it down most of the time when not needed). It is on another AppPool and another database
It happened on production environment. I have no clue how to reproduce it on preproduction. I don't even know if the CAS server we're using can be a cause or not for this problem (the CAS server might have been down and causing some null exception on our side (??)) ; we are a small team in a big corporation so contacting people managing the CAS server status could be tricky ... but I could try.
It seems that once the problem occurs once, it occurs for everybody. Only way to solve it is to recycle (and clean this dictionary from RAM I guess)
We are using Windows Server 2012 ; x64
Project is targetting .Net 4.5.2 ; Any CPU ; it is a .net MVC project v<IP_ADDRESS>
dotnetcasclient DLL is taken from NUGET : v<IP_ADDRESS> ; I forgot to check if we were on latest release ; My bad, we will use latest on Monday (Because problem seems randomly happening, do you have any clue of something like that being solved in latest releases ?)
We are using CAS20 ; CAS Server through https ; our server in http at the moment
Here are the interesting part of our webconfig

Hello,
In the meantime, we had a discussion with the CAS server team. They updated their system and we discovered some problem concerning the proxy, it broke the entire system once they corrected it.
The first problem might have been caused by this proxy mode not working as intended by CAS standard on the CAS server.

If I understand you correctly you are saying you think the proxy mode on the CAS server was configured wrong?  FWIW, if you specify the proxyTicketManager attribute and the proxy stuff isn't configured (at all or correctly) on the CAS server then things will probably go wrong in the ASP.NET application.  There is the chance they may never had it configured on the CAS server.

Yes that's right. We don't know exactly the inner problems but from information we have :

Proxy was not working correctly on the CAS Server
The effect of this is the system worked well with this misconfiguration when it should have not (but might have some weird problems like the one described in my previous messages, redirection loops etc.)
They updated it to correct the problem on the proxy
Our system was not working anymore forcing us to correct our configuration.

I guess we can close this issue, and hope not to reopen it :)

Well if you run into further problems just reopen or make a new issue.  If the other team has CAS related errors there is a Gitter channel that may be of help to them where they can ask questions: https://gitter.im/apereo/cas


Update Pull Button: ignore status

as title
fix #10637
ToDo: fix css

look:
As admin:

As write access user:

@silverwind you may have a look at the CSS part? ;)

That's not something I can review easily. One suggestion is to stick to quarters (.25, .5, .75, 1, ...) of rem units unless pixel-perfect positioning is needed.


Update variables.css

The scroll bar was not visible in gameish theme. Changed colours to make it more visible.

the gameish theme is being removed and replaced by a similar "playful purple" theme for v0.11.0


Incorrect markdown generated for fenced code blocks containing doctest tests

Describe the bug:

When a fenced code block includes a doctest test (specifically >>> prompts), the generated markdown is incorrect.
Expected behaviour:

Fenced code blocks containing >>> should render just like any other fenced code block.
For example, this docstring:
"""Compute the sum of 2 numbers.

Examples:

```plain
>>> add(1, 2)
3
>>> add(2, 2)
4
```
"""

should generate the following markdown:
Compute the sum of two numbers.

**Examples:**

```plain
>>> add(1, 2)
3
>>> add(2, 2)
4
```

Unfortunately, it produces the following instead:
Compute the sum of two numbers.

**Examples:**

```plain
``` add(1, 2)``` 3 ``` add(2, 2)```
4
```

And the resulting HTML does not render as expected.
Steps to reproduce the issue:

See example docstring above.
Technical details:

Host Machine OS (Windows/Linux/Mac): Mac
Browser (Chrome/Firefox/Safari): Any

Possible Fix:

I have not looked at the lazydocs code, so I don't know, but happy to dig in, if it would help.
Additional context:

None

Hmmm, I just discovered this: https://github.com/ml-tooling/lazydocs/blob/v0.4.8/src/lazydocs/generation.py#L366-L368
At first glance, this appears to be incorrect, but I'll investigate further.


Fix management plane track 2 pull request assignment

Contributing to the Azure SDK
Please see our CONTRIBUTING.md if you are not familiar with contributing to this repository or have questions.
For specific information about pull request etiquette and best practices, see this section.

/check-enforcer override


proposals: don't download activeset for old epochs

merge before that change https://github.com/spacemeshos/go-spacemesh/pull/5169
we use active sets only to verify eligibilities for ballots in the current epoch. as there is an incentive to create as little ballots as possible. for older ballots we use eligibility counter provided in the reference ballots

bors merge

bors merge

bors merge


Saltern: Security substation made more secure, solars, tweaks

About the PR
See changelog & screenshots.
Plating was used on solars because cables cannot be placed on lattice - this is intended to be usable right now.
Screenshots
North-west, part A:

North-west, part B:

South-east:

Changelog
:cl:

tweak: Saltern's security substation's protective APC is now inside the security substation chamber, which has been made a little bigger accordingly.
add: Saltern now has solars - north set in north-west maintenance, south set a bit east of library.

comparison details anyway

LGTM, nice work.


Fixing InstallerSha265 of GeoGebra Classic

[x] Have you signed the Contributor License Agreement?
[x] Have you checked that there aren't other open pull requests for the same manifest update/change?
[x] This PR only modifies one (1) manifest
[x] Have you validated your manifest locally with winget validate --manifest <path>?

[x] Does your manifest conform to the 1.4 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: codeflow:open?pullrequest=https://github.com/microsoft/winget-pkgs/pull/111351&drop=dogfoodAlpha

What did I do wrong now?


Python client allows authentication via ENV's the CLI does not

Would be nice if the CLI would check for ENV just like the Python client seems to provide. Easy fix?
Tried setting up the dev-env to have a go but could not pull the docker image (I guess not on Docker hub).
$ env | grep HPECP
HPECP_PASSWORD=******
HPECP_API_PORT=8080
HPECP_VERIFY_SSL=False
HPECP_USE_SSL=False
HPECP_WARN_SSL=False
HPECP_USERNAME=admin
HPECP_API_HOST=ezmeral-cluster.*****.***

$ unset HPECP_CONFIG_FILE

$ hpecp k8sworker list
Could not find configuration file '/home/ansible/.hpecp.conf'

Would like to run this via Ansible and was thinking I'd skip creating modules that uses the Python client and rather go for a more blunt usage via shell/command module.

This would simplify calling from Ansible using Vault for secrets like:
- name: Create K8S Worker
  shell: |
    hpecp k8sworker create-with-ssh-key --ip {{ ansible_host }} --ssh-key {{ ezmeral_admin_privkey }}
  environment: "{{ hpecp }}"
  delegate_to: localhost


Is this another abandoned Hugo theme?

Is this theme still maintained? Issues and PR's seem to indicate not. I'm looking to add a documentation theme but I'm not interested in adding one that's been abandoned.
Anybody?

Hi @pauby, @vjeantet
I am using this at my workplace for internal docs as this was the best-suited/working when I looked around for Hugo documentation themes and don't see any reason to migrate away anytime soon.
Though for our production I am building from my fork, which usually lags behind a little. Just to keep things stable and no worry, every few months I update my fork in sync with this repro.
Also, I've committed to this theme before with serious improvements and am interested in keeping it in good shape.
I cannot promise to be active every week here but could make it more often to keep out the clutter.
So, maybe @vjeantet is willing to elevate my permissions so that I can help to review PR's?

Hello @Pilskalns
I’m ok with this, I’ll do it tonight.
This theme is still maintained, I need to find more time to allocate.

ping @vjeantet -t

64 bytes from @vjeantet: icmp_seq=2 ttl=54 time=8h
@Pilskalns push rights OK

That is good news !!! Thanks @Pilskalns & @vjeantet .
We also are using this theme internally for all our documentation and improving it internally.
If you take over and keep it alive I will propose some (small) updates / correct bugs
Long live docdock :-)


docs: fix regression in install instructions

Seems like there was a regression in the installation instructions from #7
This PR corrects the plugin name.
Fixes #10

@tyler36 I can confirm the doc change works, thank you!

@btmash Thank you for the confirmation.
Just got back to the office so will merge and release.


Reduce Makefile Complexity

This patch further reduces the Makefile complexity. The schema generation is now handled via ./api/utils/schema/Makefile, the version generation is in ./api/Makefile, and the dependency management has been placed in glide.mk.

Codecov Report

:exclamation: No coverage uploaded for pull request base (master@45890bb). Click here to learn what that means.
The diff coverage is n/a.

@@           Coverage Diff            @@
##             master    #590   +/-   ##
========================================
  Coverage          ?   39.4%
========================================
  Files             ?      37
  Lines             ?    2906
  Branches          ?       0
========================================
  Hits              ?    1145
  Misses            ?    1650
  Partials          ?     111

Continue to review full report at Codecov.

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


The title in the app bar should be controlled by the strings option.

Using the project-name as the app bar title on the scanner window is limiting. Would really like the option to customize it.
Thanks for a great plugin - had it up and working in no time.

Feel free to create a PR.
I'm closing this issue and reference it in https://github.com/mintware-de/flutter_barcode_reader/issues/265

Feel free to create a PR.
I'm closing this issue and reference it in #265

You mean #187, right?

Hello! We already have a solution to change hide the title?


port buffer example from QCSTM

This PR ports the Buffer example from QCSTM to STM (issue #40)
allowing to check that Buffer is not Domain safe.
The QCSTM Buffer example can be found here

next_state has been slightly changed
a type res has been added
run_cmd has changed into run and postcondition has been added

There are two tests that are run:

sequential test that is expected to succeed
parallel test that is expected to fail

Looks good - thanks!


CMake Error at cmake_install.cmake:48 (FILE):   file INSTALL cannot find   "/home/rootme/Downloads/Polycode-master/Standalone/../Release/Linux/Framework/Player/PolycodePlayer".   make: *** [install] Error 1

I am trying to install polycode on ubutnu 14.04 LTS but I get the above title.How should I do ?

How fix it?

At the best by installing py_ply using your packet manager.


Longest Substring Without Repeating Characters

hey @vidhichadha2507, I want to contribute to this issue. can you please assign this to me?

hey @vidhichadha2507, I want to contribute to this issue. can you please assign this to me?

Done


Enable namespace_id for GKE

cc: @a-robinson

LGTM, but can we have a unit test? I thought that there used to be a test that covered all the fields we expected to be present?

There is a test that checks whether the exported metrics have the labels mentioned in the schema. But if a label is not mentioned in the schema (as it was in this case) then the test won't indicate any troubles.
If you have a separate list of labels that have to be in the dump we can use it to double-check that everything is exported as expected.

That test sounds a little self-fulfilling :)
We always want:
namespace_id
pod_id
host_id
container_name
And for disk metrics, we expect a resource_id field.

Yeah, kind of :).
I will add the explicit checks in couple minutes in the next PR. Merging this one.

@mwielgus we should cherry-pick this, make patch release and bump Heapster version in Kubernetes.

This change is


nginx mime types

Issue description
The nginx config generated by the nginx module does not set a default mime type, resulting in many binary files (.opus, .mkv, .pkg) being displayed as text (text/plain).
I suggest using the mime types list from mailcap, like ArchLinux does, and adding "default_type: application/octet-stream".
I fixed this for my setup temporarily like this: https://git.pbb.lc/petabyteboy/nixfiles/commit/21ee8ed7f87571353df5b86c4cd1bc7478fddcc0
Steps to reproduce
Set up a basic nginx server on NixOS. Put a .mkv or .opus file in the served directory. Try to download it. Its content will be shown as text in the browser.
Technical details

system: "x86_64-linux"
host os: Linux 5.0.10, NixOS, 19.09pre177651.aeb464dfd37 (Loris)
multi-user?: yes
sandbox: yes
version: nix-env (Nix) 2.2.2
nixpkgs: /nix/var/nix/profiles/per-user/root/channels/nixos

Let's make a PR with your patch? :slightly_smiling_face:

Yeah, but I think the mime types should be customizable in the nginx module. I will take a look and make a draft PR at some point.


ghdorker: init at 0.3.2

Motivation for this change
Extensible GitHub dorking too
https://github.com/dtaivpp/ghdorker
Related to #81418
Things done

Built on platform(s)

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

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

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[x] Tested basic functionality of all binary files (usually in ./result/bin/)
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 150277 run on x86_64-linux 1

5 packages built:

ghdorker
python38Packages.fastcore
python38Packages.ghapi
python39Packages.fastcore
python39Packages.ghapi


Fix #9056: Default variable value missing in /forms/_text.scss

Please take a look @colin-marshall.

Looks good to me!


Perform browsertesting on commit and adopt collaborative code quality tools.

Given the hight usage of the library it would be important to perform browsertesting on commit and adopt collaborative code quality tools.
This would allow to detect defects happening on some specific browser/version, track code coverage and work in a collaborative way on improving the code quality of the library
Given the fact that the project is already using karma performing tests with PhantomJS, i would suggest to adopt karma-coverage to perform testing on Saucelabs.
It would be great than if during the testing we could integrate Codeclimate in order to keep track of the code maturity and the code coverage of the tests.
I've no interest in suggesting this specific software/services, but this all the softwares i'm suggesting are opensource and the cloud services involved are offering a complete free support for opensource projects so that it would be great if start adopting them.
Here you find the exact integration you need given the libraries involved in the project.
I did it few days ago in order to improve a library we use in GlobaLeaks: https://github.com/ghostbar/angular-zxcvbn/pull/15
The result of that integration could be something like:

Here is the current output of codeclimate for https://codeclimate.com/github/mgonto/restangular: codeclimate results for mgonto/restangular

I agree! Can you submit a PR with changes and I'll merge that in?

Good idea @evilaliv3. Any change for a PR?


Added config parameters for dump over network - v4

Have used these parameters in dump over ssh and nfs in PowerNVDump.py.
Changed --server-ip to --dump-server-ip and --server-pw to --dump-server-pw as suggested in previous PR.
Signed-off-by: Pavithra<EMAIL_ADDRESS>

LGTM,


Remove get_filters() from controller

(This is a part of #213)

Coverage decreased (-0.1%) to 39.457% when pulling 28fc662c3487c5e4a04903941b8b890d40a5605e on kmws:get-filters into 879b14a17a579d4901cb6df0c82db7407ce36866 on newsboat:master.

Thank you for the reviews, @Minoru. After #301 is done and merged, I will rebase both my PRs (#302 and #304) and fix the initialization thing in this one.

#301 is merged, you can rebase now.

A lot of files were renamed, and you probably have old object files still lying around. If so, you can do one of the following:

check out some older commit (from before #301 got merged) and run make distclean;
or just run find -name '*.o' -delete. That always worked for me so far, but is a bit hacky IMHO.

or just run find -name '*.o' -delete

That did the rick... thank you!

Hmm. I've tried to git pull --rebase, but the result is pretty bad. Should I just open new PR with cleanly applied changes?

Not sure if it's the best way, but you can try the following: branch off of current master and then cherry-pick your last two commits of this branch with the actual work and than force-push to this branch here.
Alternatively just do git rebase master on this branch, however I'm not sure whether this will work in this case or not. Good luck! ;-)
(In order to combine both of the commits into a single one, I'd do an interactive rebase (git rebase -i HEAD~2) and then squash or just fixup the second into the first one.)

Eh, hang on, I just took a look at the two "main" commits and they don't seem to do what the commit message states they do. So I'm not sure whether redoing it is easier or cherry-picking the original commits and fixing the resulting merge conflicts.

branch off of current master and then cherry-pick your last two commits of this branch with the actual work and than force-push to this branch here.

Well I tried this, but if I try to force-push it says Everything up to date. :-(

I'm not sure what went wrong, but it looks like you rebased onto zaowen's branch rather than master, because I don't see my merge commit in your branch. If you're getting "Everything up to date" despite retrying, your master must be old. Check it out once more, do a pull, and make sure it's now on commit 8069b1fb. After that, retry Lyse's suggestion about cherry-picking.
If none of this helps, I can go in and fix this myself (GitHub lets me change your branch), so you don't have to create a new PR. But I'd rather help you figure this out if you're in the mood ;)

it looks like you rebased onto zaowen's branch rather than master

No, I pulled from Newsboat's master (as always) before branching out (in an effort to force-push later). My local master branch is indeed at 8069b1f. Then I did all of my changes (as one commit) and tried to force-push here, but it says it's up to date...
First I tried to git pull --rebase from Newsboat's master, resolved some conflicts, did rebase --continue and my changed were looking like they are on top of your merge, which seemed OK. Huh. :-(

No, I pulled from Newsboat's master (as always) before branching out

Yeah; it'd be hard to rebase onto someone else's PR without noticing :) But I just don't have any other explanation for the current state of history in this PR.

My local master branch is indeed at 8069b1f.

That's reassuring, I think we can fix this still (not the xkcd way, but for real)!

Then I did all of my changes (as one commit) and tried to force-push here, but it says it's up to date...

Can you re-try that now, and post what commands you ran and what output you got? There's probably some small detail that we're missing, maybe the output will hint at it.

$ git checkout get-filters-2
Switched to branch 'get-filters-2'
$ git log --oneline -n 2
c6abaaf1 (HEAD -> get-filters-2) Remove get_filters() from controller
8069b1fb (gh/master, master) Merge pull request #301 from zaowen/ClassRename
$ git pull gh master
From https://github.com/newsboat/newsboat
 * branch              master     -> FETCH_HEAD
 Already up to date.
$ git push origin get-filters
Everything up-to-date

c6abaaf1 contains all of the changes as one commit.

Ah, here's the detail I was suspecting:
$ git push origin get-filters

This command pushes branch get-filters to its remote branch in origin, which is get-filters by default. It does so even though you're on branch get-filters-2 right now. Run this instead:
$ git push origin --force-push get-filters-2:get-filters

The last argument means "push local branch get-filters-2 to remote branch get-filters".

Wows. Thank you, that was it!
It seems that some of the clang-format changes sneaked in. If they are not OK, I can undo them and force again (to train ;).

That's Git for you: it's flawless when it works, and it's a total puzzle when it doesn't :)
The clang-format changes seem fine, but please put them into a separate commit. A good opportunity to try out git reset --soft "HEAD~" and git add --patch if you haven't already ;)

Coveralls went mad from all that rebasing :)
Thank you for the contribution, @kmws! Don't forget to rebase your other PRs ;)

Once again, thank you for taking the time to help me, @Minoru. And thank you too, @der-lyse, we were close. ;)


Generalize Mixers

The reason for this PR is to allow the controlled bond expansion to be implemented as a Mixer.
Main changes

Implement mixers in tenpy.algorithms.mps_common
-> Offer backwards-compatible wrappers in tenpy.algorithms.dmrg
Change methods of the Mixer interface: two different methods (mixed_svd_2site and mix_and_decompose_1site) for decomposing single-site or two-site theta to replace peturb_svd.
Since the current perturb_svd has different signatures for those cases, any users would need
to distinguish these cases anyway.
Removed the update_sites class attribute.
Move the implementation of using a "1-site mixer" to decompose a 2-site wavefunction from the
TwoSiteDMRGEngine to the Mixer base class, as the mix_and_decompose_2site method.
Change docstring summary to cover a broader view that is not specialized on application in DMRG
Change docstrings to emphasize that the physical state, the wavefunction and the singular values
are unchanged.
E.g. reformulate "amplitude; Singular values are perturbed on that order of magnitude.".
Put longer explanations of how the mixers work in the Notes section of the docstring
Anticipate mixers where (i) "amplitude" makes no sense (always same strength) or
(ii) that do not decay / are never turned off
-> class variables for defaults of amplitude, decay and disable_after
-> allow None for those attrs

Follow-up TODO list

[ ] Discuss differences between SubspaceExpansion and DensityMatrixMixer in docs. Advantages? Costs?
-> Make SubspaceExpansion the default and sell it as such?
[ ] Do we need an interface that maps e.g. --A--Th-- to --A==Th-- or similar?
I.e. do mixing without doing an SVD?
[ ] Adjust usage in the notebooks, e.g. in 12_dmrg_mixer.ipynb
[ ] Mixer seems to handle qtotal differently than the pure SVD alternatives in XxxSiteDMRGEngine.mixed_svd
[ ] Warn on single-site DMRG with a "two-site" mixer?
[ ] Make qtotal_LR work the same as with svd_theta, i.e. auto-detect on a single None entry.
[ ] Investigate effects of qtotal typo in SubspaceExpansion
[ ] Should S_inv_cutoff be decreased for all mixers? Not needed if we only do mix_and_decompose_1site right, e.g. in single-site DMRG (or future single-site TDVP)?

I made a design choice in the commit that I am about to push that is up for debate.
We now have the 'mixer' option in the Sweep class.
We need to encode two different defaults for every Sweep subclass;

The default for the option itself, i.e. what happens if the key is not set at all
The meaning of mixer=True, i.e. which mixer to use if the user says "Use a mixer, I dont care which"

So far, this is done by an instancecheck in DMRGEngine.mixer_activate, which does not generalize well.
I have added a second class attribute use_mixer_by_default in addition to DefaultMixer, such that we can control them both separately. In particular, to recover the default behavior of the live main branch we need
class TwoSiteDMRGEngine:
    DefaultMixer = mps_common.DensityMatrixMixer
    use_mixer_by_default = False

class SingleSiteDMRGEngine:
    DefaultMixer = mps_common.SubspaceExpansion
    use_mixer_by_default = True

We currently set S_inv_cutoff to a much higher threshold (1.e-8 instead of 1.e-15) when the mixer is activated. I dont think this is needed for the mixers that use true (i.e. 1D) singular values, such as SubspaceExpansion or the soon-to-come controlled bond expansion, if used via mix_and_decompose_1site. correct?
Ideas how we best implement this distinction in Sweep.mixer_activate? It depends both on the type of mixer and how the engine calls it.

What about something like this;
class Sweep:
  ...
  @property
  def S_inv_cutoff(self):
    return 1.e-8 if any(isinstance(S, npc.Array) for S in self._S) else 1.e-15

It does the same as the current intention (higher cutoff if there are 2D arrays Ss due to the mixer)  and subclasses may still override.

Regarding the computation costs i get the following, assuming d < w < chi:
SubspaceExpansion (single-site theta)

contraction d^2 w chi^3
SVD of (d chi, w chi) costs d w^2 chi^3 [dominant]
total d w^2 chi^3

SubspaceExpansion (two-site theta)

contraction d^3 w chi^3
SVD of (d chi, d w chi) costs d^3 w^2 chi^3 [dominant]
total d^3 w^2 chi^3

DensityMatrixMixer

contraction d^3 w chi^3 [dominant]
EIG of (d chi, d chi) costs d^3 chi^3
total d^3 w chi^3

So it seems that for two-site wavefunctions, the DensityMatrixMixer should be cheaper by a factor of the MPO bond dimension.

Everything we discussed, I have now either committed here or opened separate issues for (keep branches short-lived).
See the mentions above.


Aggregrate properties for composite allOf types

Don't anonymously embed composite types, promote their properties
into the containing type.  This avoids unnecessary levels of nesting
and represents what's sent over the wire.  It also simplifies the
handling of custom marshallers and unmarshallers.

Fixes https://github.com/Azure/autorest.go/issues/732

Also fixes https://github.com/Azure/autorest.go/issues/709

It will be.  However, we think the change is worth it as it simplifies the usage and is the same that we generate in track 1 which will ease migration.

It will be. However, we think the change is worth it as it simplifies the usage and is the same that we generate in track 1 which will ease migration.

I would agree with you, in that case LGTM


http2 cleartext upgrade, server not support first POST request to upgrade protocol

send a initial upgrade request with POST method and header content-length > 0, the server will not upgrade to HTTP/2.
Expected behavior
upgrade the HTTP/1.1 to HTTP/2 and response the request rather than 413.
as the rfc http://httpwg.org/specs/rfc7540.html, it is not mandatory that frist upgarde request must be GET or OPTIONS method. just need to modify the header "Connection", "Upgrade", "HTTP2-Settings"
GET / HTTP/1.1
Host: server.example.com
Connection: Upgrade, HTTP2-Settings
Upgrade: h2c
HTTP2-Settings: <base64url encoding of HTTP/2 SETTINGS payload>

Requests that contain a payload body MUST be sent in their entirety before the client can send HTTP/2 frames. This means that a large request can block the use of the connection until it is completely sent.
If concurrency of an initial request with subsequent requests is important, an OPTIONS request can be used to perform the upgrade to HTTP/2, at the cost of an additional round trip.
It means the first request could be any method request. If the server support HTTP2, then response 101 code and the real response for this request with http frame format. If not, it still can response with HTTP/1.1 protocol.
Actual behavior
The http2 server example will reponse 413 not 101.
Steps to reproduce
send a request with POST method for upgrade request.
POST / HTTP/1.1
Host: server.example.com
Connection: Upgrade, HTTP2-Settings
Upgrade: h2c
HTTP2-Settings: <base64url encoding of HTTP/2 SETTINGS payload>
Content-length: 5

<http1.1 body data>

Netty version
lastest, 4.1

@zjupure seems legit... want to contribute a PR to fix it ?

@zjupure can you tell me which exact example code you are talking about ? We have multiple :)

@normanmaurer  the http2 examples under netty/example/src/main/java/io/netty/example/http2/helloworld, the server examples in package server, multiplex.server, frame.server would response 413 code and not upgrade to HTTP/2.
I digest the source and find the default consturct function with two params of class 'io.netty.handler.codec.http.HttpServerUpgradeHandler with set super class HttpObjectAggregator's filed maxContentLength to be zero. When Http2ServerInitializer configure clear text pipeline handlers, it use the default consturct method,  so then the call isContentLengthInvalid() in HttpObjectAggregator's will return true, so POST upgrade to HTTP/2 failed.
io.netty.handler.codec.http.HttpServerUpgradeHandler
public HttpServerUpgradeHandler(HttpServerUpgradeHandler.SourceCodec sourceCodec, HttpServerUpgradeHandler.UpgradeCodecFactory upgradeCodecFactory) {
        this(sourceCodec, upgradeCodecFactory, 0);
    }

and I modify the example code in Http2ServerInitializer to set a large maxContentLength to HttpServerUpgradeHandler, then it can pass my POST upgrade test. Thanks.
io.netty.example.http2.helloworld.server.Http2ServerInitializer
    private void configureClearText(SocketChannel ch) {
        final ChannelPipeline p = ch.pipeline();
        final HttpServerCodec sourceCodec = new HttpServerCodec();
         // change this line to use the three params construct function
        final HttpServerUpgradeHandler upgradeHandler = new HttpServerUpgradeHandler(sourceCodec, upgradeCodecFactory, maxHttpContentLength);
        final CleartextHttp2ServerUpgradeHandler cleartextHttp2ServerUpgradeHandler =
                new CleartextHttp2ServerUpgradeHandler(sourceCodec, upgradeHandler,
                                                       new HelloWorldHttp2HandlerBuilder().build());

        p.addLast(cleartextHttp2ServerUpgradeHandler);
        p.addLast(new SimpleChannelInboundHandler<HttpMessage>() {
            @Override
            protected void channelRead0(ChannelHandlerContext ctx, HttpMessage msg) throws Exception {
                // If this handler is hit then no upgrade has been attempted and the client is just talking HTTP.
                System.err.println("Directly talking: " + msg.protocolVersion() + " (no upgrade was attempted)");
                ChannelPipeline pipeline = ctx.pipeline();
                ChannelHandlerContext thisCtx = pipeline.context(this);
                pipeline.addAfter(thisCtx.name(), null, new HelloWorldHttp1Handler("Direct. No Upgrade Attempted."));
                pipeline.replace(this, null, new HttpObjectAggregator(maxHttpContentLength));
                ctx.fireChannelRead(ReferenceCountUtil.retain(msg));
            }
        });

        p.addLast(new UserEventLogger());
    }

@zjupure ah makes sense... Then its not a bug. Let me close this


I don't undestand how get user username and avatar from social

Hello. Very good modul, thank you very match. But i not undestand how get data user from VK.
Please talk me how can i do

At the moment, there isn't any guide, which describes the way you can retrieve social network data. However I'll try to add documentation on this point in a few days.

Thank you

I've added basic exaple in docs. I'll try to add more complex example a little bit later.

Спасибо большое.


Composer tree visualization new

Added visualization of directed acyclic graph

Hello @Sash0check! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file fedot/core/composer/composing_history.py:

Line 47:28: E128 continuation line under-indented for visual indent

In the file fedot/core/composer/optimisers/gp_optimiser.py:

Line 279:49: W292 no newline at end of file

In the file test/visualization/test_visualisation_utils.py:

Line 61:12: E127 continuation line over-indented for visual indent

Hello @Sash0check! Thanks for opening this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file fedot/core/composer/composing_history.py:

Line 47:28: E128 continuation line under-indented for visual indent

In the file fedot/core/composer/optimisers/gp_optimiser.py:

Line 279:49: W292 no newline at end of file

In the file test/visualization/test_visualisation_utils.py:

Line 61:12: E127 continuation line over-indented for visual indent


Make group selector database-efficient

Fixes #109 by building an array of lightweight objects from a single query.

:+1:


De-novo binder generation

The supplement of the original Nature paper suggests that De-novo binders could be generated by "Combine (i) substructure conditioning on antigen, (ii) optional scaffold constraint on binder, and (iii) contact constraints on epitope/paratope."
From my current understanding of Chroma, I am unsure on how to use an existing antigen as the template for a de novo binder. I've been able to successfully generate re-designs on existing binders using code similar to #9 but de novo is proving more of a challenge. In practice, what API(s) should one use to ask Chroma to design a brand new chain in complex with an existing antigen?
As a second question, the "(iii) contact constraints" should ostensibly be implemented via the "Substructure distances conditioner" (pg 80, Supp Table 6). My understanding of this module is that it would allow the user to provide Chroma with a pre-specified binding location, akin to hotspots in RFDiffusion. I recognize all the other conditioners from the source code, but I can't find the substructure distances module. Has that one already been implemented/open-sourced, or does it exist as a mathematical template for now until its implemented in Python?

Hi,
For me the opposite in fact. De novo binder design can be done directly by substructure conditioner. You just need to modify the pdb file a bit, by adding new chain (pseudo-chain) with dummy coordinate.
Here's the colab example.

Hi, thank you so much for the code example. Would you be able to share how you added a psuedo chain to the PDB, or maybe share an example? I am a little new to the PDB format.

And, have you found a way to identify particular "hotspots" for the receptor? Essentially, how to specify which receptor residues Chroma should try to diffuse the binder near?
Thank you so much!

o share how you added a psuedo chain to the PDB, or maybe share an example? I am a little new to the PDB format.

The code is included in the colab example.
`protein = Protein(f"{input_dir}/6wrw_A.pdb", device=device) # input pdb should be clean before, in this case only the chain A of pdb 6WRW
X, C, S = protein.to_XCS()
define length of your binder
len_binder = 100
prepare new pseudo-chain of the binder for your pdb
X_new = torch.cat(
[X,
torch.zeros(1, len_binder, 4, 3).cuda()
],
dim=1
)
C_new = torch.cat(
[C,
torch.full((1, len_binder), 2).cuda()
],
dim=1
)
S_new = torch.cat(
[S,
torch.full((1, len_binder), 0).cuda()
],
dim=1
)
del X,C,S
protein = Protein(X_new, C_new, S_new, device=device)
X, C, S = protein.to_XCS()`

Hi, For me the opposite in fact. De novo binder design can be done directly by substructure conditioner. You just need to modify the pdb file a bit, by adding new chain (pseudo-chain) with dummy coordinate. Here's the colab example.

Thanks for sharing of the binder-designing code.
I met one problem when using it, that the receptor sequence was changed in the final result.
Any idea ?
Thanks !

Problem solved. Modification of the code to:
#################################
for i in range(L_complex):
if i < L_receptor:
mask_aa[i] = torch.Tensor([0] * 20)
mask_aa[i][S[0][i].item()] = 1
else:
mask_aa[i] = torch.Tensor([1] * 20)
#################################
Also ask:  how to set hot spot residues in the receptor for binder design?

Thanks for all the discussions and feedbacks! I will close this issue for now, feel free to reopen or post new issues if you feel the need.


calibre: 4.15.0 -> 4.17.0

Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from https://repology.org/metapackage/calibre/versions.
meta.description for calibre is: "Comprehensive e-book software"
meta.homepage for calibre is: "https://calibre-ebook.com"
Updates performed

Version update

To inspect upstream changes
Impact

Checks done (click to expand)

built on NixOS

The tests defined in passthru.tests, if any, passed

0 of 0 passed binary check by having a zero exit code.

0 of 0 passed binary check by having the new version present in output.

found 4.17.0 with grep in /nix/store/qx16vrx587srqi3p2i7bna7ib3qdkx3x-calibre-4.17.0

directory tree listing: https://gist.github.com/bde23c06d1f55e3e4d4547ab5a2d2fde

du listing: https://gist.github.com/895242cc866ac28bc83e0ebf55e50f20

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

3 total rebuild path(s)

1 package rebuild(s)

1 x86_64-linux rebuild(s)
1 i686-linux rebuild(s)
0 x86_64-darwin rebuild(s)
1 aarch64-linux rebuild(s)

First fifty rebuilds by attrpath
calibre

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/qx16vrx587srqi3p2i7bna7ib3qdkx3x-calibre-4.17.0 \
  --option binary-caches 'https://cache.nixos.org/ https://r-ryantm.cachix.org/' \
  --option trusted-public-keys '
  r-ryantm.cachix.org-1:gkUbLkouDAyvBdpBX0JOdIiD2/DP1ldF3Z3Y6Gqcc4c=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

After you've downloaded or built it, look at the files and if there are any, run the binaries:
ls -la /nix/store/qx16vrx587srqi3p2i7bna7ib3qdkx3x-calibre-4.17.0
ls -la /nix/store/qx16vrx587srqi3p2i7bna7ib3qdkx3x-calibre-4.17.0/bin

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

1 package marked as broken and skipped:
- calligra

1 package built:
- calibre

Maintainer pings
cc @domenkozar @pSub @AndersonTorres for testing.

Changelog looks good and the bot has built all packages that depend on this.

[x] Tested on NixOS

Great, thanks!


Delete call to #output?

Test PR in https://github.com/logstash-plugins/logstash-filter-zeromq/pull/8

minor comment but otherwise LGTM


System sounds for notifications

Add an setting to use System/Platform sounds.
Eg: Notifications - Use the System Notification sound instead the sound of the current Skin

This feature is already implemented upon release on some platforms

This feature is already implemented upon release on some platforms