Failed to load Better BibTex

Hi,
After I installed ZotLit, there is an error as follow figure

I am sure the better-bibtex-search.sqlite is in that directory.
Another issue is that when I use [@ to cite literature, it return back as [@undefined].
It there any way to solve these two problems?

The citation keys have moved. They live in better-bibtex.sqlite now, but that database must be mounted using
ATTACH DATABASE '<path to better-bibtex.sqlte>' AS betterbibtex;

after which the citation keys can be read from betterbibtex.citationkey.

Noted, will update shortly

@retorquere could you provide the version of the better bibtex?

6.7.132 or later.

I have a similar effect (noted here for clarifying):
It differs in Zotero items created before the update and Zotero items created now.
OLD Zotero Items:
On "Create Literature Note" all is fine: citekey is specified correctly.
NEW Zotero Items (added after update):
citekey first looks like it always does in Zotero, but On "Create Literature Note" citekey are "undefined".

Note:
If I change an old Citekey and "Create Literature Note", then the change take not into account and the old key is exported.
BibTeX: 6.7.132
Obsidian Note for Zotero: 1.0.1

That's because I have left the old database in place, it's an easy fallback scenario because database changes are the scariest of changes. But that backup is no longer being updated, so zotlit will have to be updated. This PR fixed it for another project, but I do not understand the composition of zotlit.

I have the same problem as @benpla with citation key of newly added references in Zotero! Thanks @retorquere and @aidenlx for your great work, I am really enjoying both your plugins and I hope this issue will be resolve soon!

I'll be glad to help when @PKM-er works on it, but I don't understand how this plugin hangs together.

I have to roll back to Better BibTeX 6.7.130 to make this plugin work.

Which will be undone by Zotero in the next 48 hours. This is not a sustainable workaround.

And if you roll back (with all the risk that entails - no support, and when you upgrade back to the regular release, and new citekeys and auto exports you make will be lost during the upgrade), please roll back to 124, not 130.

I use Better BibTeX 6.7.133 and Obsidian Note for Zotero: 1.0.1, and meet the same problems. Roll back is a useful way to temporary solve these problem.

Which will be undone by Zotero in the next 48 hours. This is not a sustainable workaround.

I just turned off automatic updates for Better BibTeX. Hope it works.

Still recommend 124 over 130

Just as a reminder then: when you go back to the regular release of BBT, some keys might be regenerated, and some auto exports may be lost.
Also please do install the latest BBT release before opening new issues.

I tried to prepare a PR but I don't understand the source code of this plugin.

Part of this plugin uses ophidian core which connects this.current to the SettingsPluginClass.
https://github.com/PKM-er/obsidian-zotlit/blob/dcd41794fd96f92c1866e870821aeb128507b339/app/obsidian/src/services/zotero-db/connector/settings.ts#L9
So here's where the zoterodatadir is being set, and once it is set, that data is being automatically cloned by ophidian core into this.current

That's fine, but I'm not diving into the details of obsidian plugin building, so I'm not going to prepare a PR. If someone who knows how this plugin is put together is willing to make the PR, I can say exactly what must be changed in the database access.

That's fine, but I'm not diving into the details of obsidian plugin building, so I'm not going to prepare a PR. If someone who knows how this plugin is put together is willing to make the PR, I can say exactly what must be changed in the database access.

https://github.com/PKM-er/obsidian-zotlit/blob/dcd41794fd96f92c1866e870821aeb128507b339/app/obsidian/src/settings/base.ts#L58C35-L58C35
i mean is it as simple as just changing this?

I only see stuff there about paths. I don't see where the connection is made, or where the database is queried.
But if you're willing to make the PR, the change is that instead of connecting directly to better-bibtex.sqlite, you must connect to any other database (:memory: would work) and then attach the bbt database using
ATTACH ? AS betterbibtex

where the parameter is the full path to better-bibtex.slqite. After this you can query betterbibtex.citekey.

Oh I see you're fighting with your data right now. That takes precedence of course. Did you sync with the zotero servers? That's easier to restore from.

I test zotero integration with selenium to set up the profile, then I drive zotero using a separate plugin called the debug bridge. Does that answer your question?

should be fixed in v1.1.3

restart obsidian can also solve the problem


DEC-777: Update beehive work with site_path

Why: Before I can work on beehive, we need to change site_objects to site_path in honeycomb.
How: Migrated site_objects to site_path and updated all references to site_path.

:+1:


test(e2e): always output manifest

This PR changes the logic in run-multiple to always output the manifest content, not only when it fails.
This will be helpful to troubleshoot errors where the infrastructure might be the root cause of the error (test is killed by CI because it was using too many resources).
Always showing the manifest content in the log will allow local testing to try to reproduce the problem.

Thanks @cason and @melekes


Tippy not playing well with styled component and redux

I have styled component wrapped with tippy in a component. the component is connected to the redux store to dispatch/receive props.
everything works fine until store state change and causing rerender. after that, the popover won't show.
I have created codesandbox to demonstrate the problem:
https://codesandbox.io/s/5w394qqzlk
Please look in 'Component.jsx' and follow instructions.
Thanks,

It's because you are creating a Button styled component in the render lifecycle method. Never a good idea. Most likely tippy creates event listeners to the "original" button component and it gets lost during the next re-render issued by store change.
Just move the Button component outside of your Component.

Thank you for the clarification, I tried your solution and it works fine.


ISSUE-259 Master Page null exception issue  Closes #259

Closes #259

Hi @TheJayMann - I'm not sure if @mason-chase is planning on finishing this pr, but feel free to open a new one that builds on this if you want to see it fixed quicker

Fixed in #315. Closing in favor of that issue


Fix 'Info.plist not found.' error

Got this error a while ago when trying to compile the 'HelloMaui' project, adding this into the HelloMaui.csproj file seemed to fix it

So I don't think we want this to be specified in the project file. We need the MSBuild targets in dotnet/maui to handle this.
Can you attach a .binlog of the error you're hitting? Add -bl to your dotnet build command and upload the msbuild.binlog file here. Thanks!

The issue seems to have fixed itself now without the change I made, I don't know how it occurred either, sorry if I caused any inconvenience


update logo,favicon and add clipboard copy button to code blocks

Thank you @DininduSenanayake for your contribution :).


conan: Fix build

conan has very strict requirements on the versions of its dependencies.
This patch adds downgraded versinos of node-semver and distro to
statisfy these requirements.
Motivation for this change
/cc ZHF #36453 (please backport)
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option build-use-sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[x] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Fits CONTRIBUTING.md.

@GrahamcOfBorg build conan

No attempt on x86_64-darwin
The following builds were skipped because they don't evaluate on x86_64-darwin: conan
No log is available.

Success on x86_64-linux (full log)
Attempted: conan
Partial log (click to expand)
/tmp/nix-build-conan-1.1.1.drv-0/conan-1.1.1
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/1186502jrg3n16zpp4mjzidgi2bf8hsl-conan-1.1.1
strip is /nix/store/b0zlxla7dmy1iwc3g459rjznx59797xy-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/1186502jrg3n16zpp4mjzidgi2bf8hsl-conan-1.1.1/lib  /nix/store/1186502jrg3n16zpp4mjzidgi2bf8hsl-conan-1.1.1/bin
patching script interpreter paths in /nix/store/1186502jrg3n16zpp4mjzidgi2bf8hsl-conan-1.1.1
checking for references to /tmp/nix-build-conan-1.1.1.drv-0 in /nix/store/1186502jrg3n16zpp4mjzidgi2bf8hsl-conan-1.1.1...
wrapping `/nix/store/1186502jrg3n16zpp4mjzidgi2bf8hsl-conan-1.1.1/bin/conan_server'...
wrapping `/nix/store/1186502jrg3n16zpp4mjzidgi2bf8hsl-conan-1.1.1/bin/conan_build_info'...
wrapping `/nix/store/1186502jrg3n16zpp4mjzidgi2bf8hsl-conan-1.1.1/bin/conan'...

Success on aarch64-linux (full log)
Attempted: conan
Partial log (click to expand)
post-installation fixup
shrinking RPATHs of ELF executables and libraries in /nix/store/qpbiad446d7lv9l07mxk523wb35j7px3-conan-1.1.1
strip is /nix/store/lvx1acn1ig1j2km8jds5x3ggh3f2wa8v-binutils-2.28.1/bin/strip
stripping (with command strip and flags -S) in /nix/store/qpbiad446d7lv9l07mxk523wb35j7px3-conan-1.1.1/lib  /nix/store/qpbiad446d7lv9l07mxk523wb35j7px3-conan-1.1.1/bin
patching script interpreter paths in /nix/store/qpbiad446d7lv9l07mxk523wb35j7px3-conan-1.1.1
checking for references to /build in /nix/store/qpbiad446d7lv9l07mxk523wb35j7px3-conan-1.1.1...
wrapping `/nix/store/qpbiad446d7lv9l07mxk523wb35j7px3-conan-1.1.1/bin/conan'...
wrapping `/nix/store/qpbiad446d7lv9l07mxk523wb35j7px3-conan-1.1.1/bin/conan_build_info'...
wrapping `/nix/store/qpbiad446d7lv9l07mxk523wb35j7px3-conan-1.1.1/bin/conan_server'...
/nix/store/qpbiad446d7lv9l07mxk523wb35j7px3-conan-1.1.1

@timokau The dependencies' versions should be pinned in another way. We do not want do have multiple version inside the pythonPackages prefix. Have a look at https://github.com/NixOS/nixpkgs/blob/staging/pkgs/servers/home-assistant/appdaemon.nix for how to do it correctly.
Please open another PR that removes the added pythonPackages and uses packageOverrides instead.
/cc @FRidh

@timokau Regarding the tests: nose-parameterized was removed from pythonPackages because it has been renamed to parameterized, see https://pypi.org/project/nose-parameterized/. I already opened an upstream PR (https://github.com/conan-io/conan/pull/2549) which you can use with fetchpatch.

@timokau Please be quick with the follow-up PR as this is hindering me from updating Home Assistant! (Some issue where a script of mine finds two versions of distro and doesn't know which one to choose)

If you need it quick, its usually best you do it yourself.
That said: #37094


Bugs Found on version 1.0.0

[ ] Issue: Register User Form => Username length error is not alerted
Where:  Register User Form
[ ] Issue: Upload Picture => User Not Found Alert Error (sometime)
Where: top right menu -> account (if we go to left menu, we can upload image profile
[x] Missing profile photo for top right side

[x]  When Upload profile picture for user on /account => always reload
[x]  When Click Save Change to update profile on /account => user is logged out
[x] Forgot Password page not found

Q.Missing profile photo for top right side
I purposely avoided it to reduce resource usage.

When Upload profile picture for user on /account => always reload
When Click Save Change to update profile on /account => user is logged out
It has to be reloaded to update the token data. No other possible ways.

it won't be bothering as well. should be just fine


nvcc warnings are not caught in testing

Detected in #268. Warnings like
/var/jenkins/workspace/ArborX_PR-268/src/details/ArborX_Predicates.hpp(34): warning: __device__ annotation is ignored on a function("Nearest") that is explicitly defaulted on its first declaration

were not detected in Style. It seems that there is problematic interaction of nvcc_wrapper, nvcc, jenkins, etc.

We should be able to just record the compiler output manually and grep for "warning: ". That's certainly not perfect but should work as a workaround.

I think a better solution would be to make Style check pick it up. The following pattern works to transform nvcc style warnings to that of gcc:
sed "s/\(.*\)(\([[:digit:]]*\)):/\1:\2:/"'

Just need to make the output transform to that in .jenkins. Quick hack did not work for me, though.

We should introduced -Werror to CUDA builds.

Should do it after kokkos/kokkos#7021 is resolved.


Remove all deprecated elements from the public API

.. except for those that were deprecated in 0.99.8.

Closed via #2926


Rights management doesn't work well with vhosts

I am using this library with CloudAMQP https://www.cloudamqp.com/ which gives me access to a single vhost.
I do not have administrator tags, but I have management and policymaker. Since @needs_admin_privs only checks for admin, it forbids me from calling Client.is_alive on my vhost even though I am allowed to do so (the call succeed with curl).

I fork and update module. Welcome https://github.com/deslum/pyrabbit2


Remove the hex dependency

This removes the hex dependecy from the tests.
I had to leave the hex_hash! macro because here https://github.com/rust-bitcoin/rust-bitcoin/blob/master/src/util/bip143.rs#L143 I needed to use that instead of SigHash::from_hex because the latter requires the hex to be in reverse ordering.
FYI currently even non tests will build hex because of #[cfg(any(test, feature = "serde"))] extern crate hex;

This won't work until bitcoin_hashes#71 will get merged because the hash_newtype! currently require the hex crate


Refresh sequence control for shared configuration

For configurations shared among multiple services, sometimes we may need to control the configuration refresh sequence depending on the services. Do you plan to support refresh sequence control for shared configuration cases?

Duplicate post


iOS support

In google io 2018, firebase test lab for iOS was announced.
More info at: https://firebase.google.com/docs/test-lab/ios/firebase-console
I am more than happy to help with the implementation.
For maintainers: Do you think the iOS support can live inside this project?

Absolutely, I'm waiting on firebase test lab to white list my account.

@bootstraponline perfect! Same thing here.
Have you though on what to use to replace dex-test-parser?
I am not 100% we can parse all tests from .xctest package

I think we can parse them all: https://github.com/linkedin/bluepill/issues/258
Otherwise we could fall back to AST parsing.

I've been added to the beta. :) I'll check this out next week.

@bootstraponline I just recreated the client and there is no reference to "ios". Shouldn't we wait for May 16th for this?

It looks like https://www.googleapis.com/discovery/v1/apis/testing/v1/rest hasn't been updated yet. I think we're blocked until gcloud CLI releases.

@bootstraponline I guess we can start working on parsing the tests. What's on your mind? Should we depend on bluepill? Perhaps we should figure out how they do it and write the logic in kt.
wdyt?

yeah, we need a project like dex-test-parse for iOS. I think taking the bluepill code and printing the tests to stdout will be easy to start with. If the parsing logic is reasonable to implement in Kotlin then that may be a good next step.

Looks like the xctestrun file can be parsed directly.
https://github.com/linkedin/bluepill/pull/162

I updated the EarlGrey demo app to generate an xctestrun file:

https://github.com/bootstraponline/EarlGrey/commit/43174c90ea13d72c212a5c624efd48e806aaf6c3
Demo/EarlGreyExample/build.sh
Demo/EarlGreyExample/run.sh

The test names end up in a binary file

./EarlGrey/Demo/EarlGreyExample/xctestrun/Build/Products/Debug-iphonesimulator/EarlGreyExampleSwift.app/PlugIns/EarlGreyExampleSwiftTests.xctest/EarlGreyExampleSwiftTests

These magic commands parse the tests from the binary:

nm -gU 'EarlGreyExampleSwiftTests' | cut -d' ' -f3 | xargs -s 131072 xcrun swift-demangle | cut -d' ' -f3 | grep -e '[\.|_]'test

EarlGreyExampleTestsSwift.EarlGreyExampleSwiftTests.testWithGreyAssertions()
EarlGreyExampleTestsSwift.EarlGreyExampleSwiftTests.testLayout()
EarlGreyExampleTestsSwift.EarlGreyExampleSwiftTests.testWithInRoot()
EarlGreyExampleTestsSwift.EarlGreyExampleSwiftTests.testCustomAction()
EarlGreyExampleTestsSwift.EarlGreyExampleSwiftTests.testWithCondition()
EarlGreyExampleTestsSwift.EarlGreyExampleSwiftTests.testBasicSelection()
EarlGreyExampleTestsSwift.EarlGreyExampleSwiftTests.testWithCustomMatcher()
EarlGreyExampleTestsSwift.EarlGreyExampleSwiftTests.testCollectionMatchers()
EarlGreyExampleTestsSwift.EarlGreyExampleSwiftTests.testCatchErrorOnFailure()
EarlGreyExampleTestsSwift.EarlGreyExampleSwiftTests.testWithCustomAssertion()
...

NSString *swiftNmCmdline = @"nm -gU '%@' | cut -d' ' -f3 | xargs -s 131072 xcrun swift-demangle | cut -d' ' -f3 | grep -e '[\.|_]'test";
NSString *objcNmCmdline = @"nm -U '%@' | grep ' t ' | cut -d' ' -f3,4 | cut -d'-' -f2 | cut -d'[' -f2 | cut -d']' -f1 | grep ' test'";
https://github.com/linkedin/bluepill/blob/master/Source/Shared/BPXCTestFile.m#L17-18

The workflow is:

Find xctestrun, read TestBundlePath to locate xctest
Parse test list from xctest binary file

@bootstraponline amazing!
Plz add a couple of objective-c tests as well.
What about filtering? AFAIK, there is no concept of annotation.
Should we only filter by package?

@bootstraponline Thanks for the work!


CFP: Push Cilium images to GitHub container registry

Cilium Feature Proposal
Is your feature request related to a problem?
Yes
If so, please describe the problem
Work is being done to generate Software Bill of Materials (SBOM) from Cilium release images and attach the generated SBOM to the images in Quay in an effort to improve the security posture of the Cilium family’s open source projects . While testing SBOM generation in https://github.com/cilium/cilium/pull/21435, it was found that Quay doesn’t support 'text/spdx' manifest. So, the generated SBOM can’t be pushed to Quay. This is a known issue, ko generates and uploads an SBOM for every image it produces by default and face similar issue: https://github.com/ko-build/ko/issues/532.
Describe the feature you'd like
The generated images can be pushed to GitHub container registry in addition to Quay. Then the generated SBOM can be attached to images in GitHub container registry.

Makes sense, I think we can just look for places where we push tags to DockerHub today and also push to ghcr. From a quick glance, I don't think that any specific features need to be enabled on the repository.

Quay.io product manager here. What specific MIME types outside of text/spdx are expected by Cilium? Quay.io is configured to only accept a fixed set of OCI types and that's why this currently fails.

Perhaps @sandipanpanda could speak more to this, but I believe we are planning to use k8s bom and sigstore (related: https://docs.sigstore.dev/cosign/sign#signature-location-and-management) so I think it's mostly around what those tools push as OCI artifacts. I don't think we have any particular Cilium-specific constraints around this so it's mostly about what those projects are planning to generate.

Hi there, there has been some progress on this issue recently. Our initial approach was to attach the SBOM using
cosign attach sbom --sbom sbom.spdx quay.io/${{ env.QUAY_ORGANIZATION }}/${{ matrix.name }}:${{ steps.tag.outputs.tag }} and then signing the container image. But attaching SBOMs this way does not sign them. While trying to attach SBOM this way, we found that Quay doesn’t support 'text/spdx' manifest as seen in https://github.com/cilium/cilium/actions/runs/3100873683/jobs/5021632419.
I have noticed that in cosign docs that we can include the SBOM in an in-toto attestation; see https://docs.sigstore.dev/cosign/other_types#sboms-software-bill-of-materials. So I changed my approach to signing the SBOM attestation while attaching to the image using cosign attest --type spdx --predicate sbom.spdx quay.io/${{ env.QUAY_ORGANIZATION_DEV }}/${{ matrix.name }}:${{ steps.tag.outputs.tag }} and attaching the SBOM to Quay using this method worked as you can see in the Image CI Build - Test / build-and-push-prs workflows run in https://github.com/cilium/cilium/pull/21435. :tada: For example, https://github.com/cilium/cilium/actions/runs/3199021062/jobs/5224299458#step:20:1
The SBOM attestation can be verified using
cosign verify-attestation --type spdx quay.io/${{ env.QUAY_ORGANIZATION_DEV }}/${{ matrix.name }}:${{ steps.tag.outputs.tag }}
I think we should continue using this approach, as in this way the SBOM is signed while attaching it to the container image. So we are unaffected by whether Quay starts supporting 'text/spdx' manifest as of now. Moreover, other projects can start using this approach to attach SBOM to Quay images until Quay starts supporting them by default. Or, there is a workaround to support 'type/spdx' media types in Quay by Adding other OCI media types to Quay.

Closing this as the issue has been resolved and this feature is no longer needed.

FYI quay.io does support those OCI types now: https://twitter.com/quayio/status/1580121221080891392


gooseman implementation throws an Error: datetimepicker component should be placed within a relative positioned container

Hello,
gooseman fork throws an Error: datetimepicker component should be placed within a relative positioned container.
I am using quickform with following schema:
"date": {
type: Date,
autoform: {
type: "bootstrap-datetimepicker",
dateTimePickerOptions: {
format: "DD.MM.YYYY",
showTodayButton: true,
showClear: true,
showClose: true
}
}
}
Dynamically added div contains only script="display: block;".
Any advices?

Closing all issues. The plugin was a proof of concept which others have forked and made better alternatives.


File Path Warnings Needed

What version of WebTorrent Desktop? Version 0.7.2 (0.94.3)
What operating system and version? elementary OS 0.3.2 Freya (64-bit) Built on Ubuntu 14.04
What did you do? Start WebTorrent without mounted drive, where Download Path resides
What did you expect to happen? Error, Download Path does not exist, confirmation to create path or choose alternative.
What actually happened? Folder created in /media/user/, where files were downloaded off away from desired location
Details
Obviously I am saving all my torrents to a separate drive on my PC, where the drive has to be mounted before using. Silly me, I start WebTorrent before this happens. WebTorrent happily chugs along, downloads the files, returns no warnings. I realize after the download that my drive is not mounted, and the downloaded files are in /media/mark/External_Drive1/Torrent_Downloads/ when External_Drive is not mounted. (Please note that the incremented number may be from mounting the drive after Ubuntu sees the original path as not empty.)
I safely moved the files to the drive, however WebTorrent still thinks the torrents reside in _Drive1. Closing the application, modifying the .config file, and reopening did not resolve the issue.
Possible Solutions
Upon opening the application, the download path should be tested to see if it exists. If it does not exist, a warning should appear to remap, or create the directory. Verbosely, the warning should also detect if the /media path is being used, to suggest remounting & retrying.
Additionally, right clicking each torrent in the list should provide options to change the Download Path of each torrent, moving the files. This could save someone from having files dumped where they don't want, and modifying the .config as I did.

Error, Download Path does not exist, confirmation to create path or choose alternative.

Sounds good. I'll add that check

I believe that Transmission checks for this condition and warns the user. We should see what that UX looks like and ensure that we do just as good of a job, if not better.

Fixed by #776!


Message::verify() succeeds when gpg does not

I'm trying to verify a message has been signed by the given public key. To test this I tried modifying the contents of the ASCII message, expecting Message::verify() to produce an error, but it did not. I then used gpg --verify signed_message.sig, which produced
gpg: CRC error; 2E424B - 1BE5BF
gpg: no signature found
gpg: the signature could not be verified.

Code Snippet:
let message = Message::from_armor_single(data).unwrap().0;
let verify = &message.verify(&public_key);

When I dbg!(message) I can see it is Message::Compressed. As a test I produced a new signed message using gpg --output signed_message.sig --sign --compress-level 0 --armor message.toml. This produced a Message::Signed and after modifying the contents of the message, Message::verify() produced an Error as expected.

Any chance you could provide a version of the modified and unmodified messages where you are seeing this difference

Hi, it seems earlier I must have used some of the functions incorrectly which might have caused this error.
However, on trying again, the issue is not reproducible anymore. So it looks like signature verification works as
expected.


Packaging issue - Potential typo

[512]UATHelper: Packaging (Windows): ERROR: Expecting to find a type to be declared in a module rules named 'HttpServer' in UE5Rules, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null.  This type must derive from the 'ModuleRules' type defined by Unreal Build Tool.I ran into this issue packaging for windows in a test project, I managed to package by changing HttpServer in TwitchInteraction.Build.cs to HTTPServer however was unsure if this could create any issues since the unreal documentation seems to list the module as lowercase HttpServer. ❤

Hello,
Are you running this on the latest version of UE5 or still the early access version?
I haven't updated this for the latest version yet but will update it and fix the issue.

It was indeed a typo, fixed it. Thank you :)


vkinit::rendering_info is never mentioned, but first used in IMGUI setup

I'm following along starting with a blank project, and when I get to https://vkguide.dev/docs/new_chapter_2/vulkan_imgui_setup/#dynamic-rendering it says:
src/vulkan/vk_engine.cpp: In member function ‘void VulkanEngine::draw_imgui(VkCommandBuffer, VkImageView)’:
src/vulkan/vk_engine.cpp:472:46: error: ‘rendering_info’ is not a member of ‘vkinit’
  472 |         VkRenderingInfo renderInfo = vkinit::rendering_info(_swapchainExtent, &colorAttachment, nullptr);

At first I thought I'd simply missed something, but google says I haven't and github search concurs, it's just missing.
It's mentioned a couple more times in chapter 3, but again there's no definition or declaration, just usage.

Make sure you have included #include <vk_initializers.h>. It should be defined there.
Source is included as part of the Starting point project files

For the convenience of anyone else hitting this, its definition is this
VkRenderingInfo vkinit::rendering_info(VkExtent2D renderExtent, VkRenderingAttachmentInfo* colorAttachment,
    VkRenderingAttachmentInfo* depthAttachment)
{
    VkRenderingInfo renderInfo {};
    renderInfo.sType = VK_STRUCTURE_TYPE_RENDERING_INFO;
    renderInfo.pNext = nullptr;

    renderInfo.renderArea = VkRect2D { VkOffset2D { 0, 0 }, renderExtent };
    renderInfo.layerCount = 1;
    renderInfo.colorAttachmentCount = 1;
    renderInfo.pColorAttachments = colorAttachment;
    renderInfo.pDepthAttachment = depthAttachment;
    renderInfo.pStencilAttachment = nullptr;

    return renderInfo;
}


Relative mode title format

Now the timestamp is used as a title in the relative mode. Would you consider changing it to something easy parsable by non-programmers eyes? A title_format prop maybe with the Date.toLocaleString() by default?

Great idea – do you want to work on this?

I haven't done any Typescript, but I'll try

https://github.com/metonym/svelte-time/pull/16/

Released in v0.7.0. Thanks again!

Nice, thank you for the great lib :)


[8.x] Revert "fix LengthAwarePaginator translations issue (#34710)"

If someone is using LengthAwarePagination outside of Laravel app, will now get this error:
$pagination = new Illuminate\Pagination\LengthAwarePaginator(['a', 'b', 'c'], 3, 1);

// Fatal error: Uncaught Error: Call to undefined function Illuminate\Pagination\__() […]
var_dump($pagination->toArray());

Was afraid of that.


Dhalion health manager

PART-1 of #1952
A original PR related to Topology health manager, #1952, may be too big to review. This PR is "subset" of the original PR, and is created to review the following components of topology health manager:

HealthManager
Tracker metrics reader
Health policy config reader
Guice injector

Why DO NOT MERGE in the title? Is this ready for review to be merged?

@ashvina any update on this pr?

Hi @huijunw I will soon push updates to resolve some of the review comments.

Thank you @ashvina

@ashvina could you merge master that has ci fix
@billonahill could you review and give shipit

Yes, I should be able to review today.

@kramasamy what do you think on the above reply from @ashvina ? could you give a shipit

talked with @kramasamy on slack and we agreed:
we can give a ship it and later fix it


[Event Request] Codeunit 12 Gen. Jnl.-Post Line - OnPostReceivableDocsOnBeforeCreateGLEntryBalAcc

We need a new event in Codeunit 12 "Gen. Jnl.-Post Line" named OnPostReceivableDocsOnBeforeCreateGLEntryBalAcc:
[IntegrationEvent(false, false)]
local procedure OnPostReceivableDocsOnBeforeCreateGLEntryBalAcc(VAR GenJournalLine: Record "Gen. Journal Line"; VAR CustomerPostingGroup: Record "Customer Posting Group"; VAR AccountNo: Code[20])
begin
end;
called from (two calls):
local procedure PostReceivableDocs(GenJnlLine: Record "Gen. Journal Line"; CustPostingGr: Record "Customer Posting Group")
var
DocAmountAddCurr: Decimal;
GLAccNo: Code[20];
begin
if (DocAmountLCY <> 0) or (DiscDocAmountLCY <> 0) or (CollDocAmountLCY <> 0) or (RejDocAmountLCY <> 0) or
(DiscRiskFactAmountLCY <> 0) or (DiscUnriskFactAmountLCY <> 0) or (CollFactAmountLCY <> 0)
then
if NextEntryNo2 = NextEntryNo then
NextEntryNo := NextEntryNo - 1;
if DocAmountLCY <> 0 then begin
if GenJnlLine."Currency Code" = AddCurrency.Code then
DocAmountAddCurr := GenJnlLine.Amount
else
DocAmountAddCurr := DocAmtCalcAddCurrency(GenJnlLine, DocAmountLCY);
GLAccNo := GetGLAccountForReceivableDocs(GenJnlLine, CustPostingGr, DocAmountLCY, CollDocAmountLCY);
//INIT INSERT
OnPostReceivableDocsOnBeforeCreateGLEntryBalAcc(GenJnlLine, CustPostingGr, GLAccNo);
//END INSERT
CreateGLEntryBalAcc(
GenJnlLine, GLAccNo, DocAmountLCY, DocAmountAddCurr,
GenJnlLine."Bal. Account Type", GenJnlLine."Bal. Account No.");
end;
if DiscDocAmountLCY <> 0 then begin
CustPostingGr.TestField("Discted. Bills Acc.");
CreateGLEntryBalAcc(GenJnlLine,
CustPostingGr."Discted. Bills Acc.", DiscDocAmountLCY, DocAmtCalcAddCurrency(GenJnlLine, DiscDocAmountLCY),
GenJnlLine."Bal. Account Type", GenJnlLine."Bal. Account No.");
end;
if CollDocAmountLCY <> 0 then begin
GLAccNo := GetGLAccountForReceivableDocs(GenJnlLine, CustPostingGr, 0, CollDocAmountLCY);
//INIT INSERT
OnPostReceivableDocsOnBeforeCreateGLEntryBalAcc(GenJnlLine, CustPostingGr, GLAccNo);
//END INSERT
CreateGLEntryBalAcc(GenJnlLine,
GLAccNo, CollDocAmountLCY, DocAmtCalcAddCurrency(GenJnlLine, CollDocAmountLCY),
GenJnlLine."Bal. Account Type", GenJnlLine."Bal. Account No.");
end;
......
......
......

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.

Thanks for reporting this. We agree, and we’ll publish a fix asap, either in an update for the current version or in the next major release. We will update this issue with information about availability. Please do not reply to this, as we do not monitor closed issues. If you have follow-up questions or requests, please create a new issue where you reference this one.


To make the cards attractive

I want to contribute in this project as a GSSoC paricipant and  wanted to do the following changes:
1)To make the cards attractive
2)Add the animations to cards
3)Arrange the cards horizontally
4)Arrange the cards according to the genre of the blog

Please read the readme once before contributing and while raising the pr do mention the issue no. All the best!

@AKD-01  mam can u please assign me this issue i can make card more attractive

Please assign me this issue under GSSoC'23, thank you.

@Umesh7Dixit you may work on this.


sigmoid

which function can replace sigmoid in LSTM?

We don't customize the activation function of LSTM. It is preferable to use the default


QGIS: Remove checkboxes from dataset widget

What?
The checkboxes in the dataset widget in QGIS don't seem to have a function. When we look in code, there seems to be no connection to these checkboxes.
Why?
The interface is cluttered and the user may be confused on what these checkboxes might do. Especially in combination with the buttons underneath (Add to QGIS, Remove from Dataset). These buttons work with the selection instead.
How?
Make them simple list view items without a checkbox.

These checkboxes are a remnant from the Tim plugin where they do serve a function: you can use them to turn boundary conditions on or off. This concept doesn't exist in Ribasim since things are also represented in the network so the different input layers are not additive.
The checkboxds should be removed indeed.


fix: preadv2 only available on GNU libc

Technicially it is also available on musl libc 1.2.5,
yet the<EMAIL_ADDRESS>(lastet) doesn't export the symbol,
and that version of musl libc is too new (released in 2024-03)
Fixes #79. Tested against Rust docker image alpine3.18

@petrochenkov
Could you help do a 0.1.30 release, and after the release yank 0.1.29 then?

@weihanglo @NobodyXu
Could you check https://github.com/rust-lang/jobserver-rs/pull/82?
It seems fine, but I'm not well trained in noticing issues in CI scripts.
I'll make a release once that PR lands.

It looks great. It also failed without this PR and now passed, so r+.

#82 is just merged.

Published 0.1.30 and yanked 0.1.29.


Split tests into those requiring an atSign and those that don't

Is your feature request related to a problem? Please describe.
#23 was opened due to Dependabot PR (such as #22) test failing due to lack of access to secrets.
Describe the solution you'd like
Split tests into those that don't need an atSign (and the secrets to use an atSign), and those that do need an atSign.
Make tests that don't need an atSign mandatory, and skip tests that need secrets for Dependabot PRs.
Describe alternatives you've considered
Use the virtual environment (VE) for testing rather than live atSigns since VE has test data keys that don't need to be kept secret.
Additional context
See at_server and at_client_sdk for examples of using VE for functional tests.

@shahumang19 do you have time to take this on?

@shahumang19 do you have time to take this on?

@cpswan
Sure I'll work on this


When calling service set_bucket, I think there should be a change in the state of a given zone, directly affecting the irrigation time.
How to reproduce
Call service set_bucket
Relevant log output
There was no bucket change recorded in the log.
Which version are you running?
v2024.4.3
Diagnostics file

[x] I have attached a diagnostics file

Additional information
I'm not sure if this is a bug, but I think there was this functionality in v1. When calling service set_bucket, there should be a change in the state of a given zone (seconds of watering), directly affecting the irrigation time.
I don't want to run the service update_zone because it will just recalculate the bucket and erase the existing weather data points.

Investigating.

so we split the update and calculate steps in v2, which were one and the same in v1.
that is causing this behavior.
the issue here is that if we implemented what you suggested and effectively calculated after a bucket is set, we would also be removing the weatherdata used to calculate (that is an effect of calculate) and I am quite certain that is something we don't want as once the weatherdata is gone it's gone for all the zones that use that weatherdata. So you set one bucket (and calculated), but all other zones can now not calculate anymore based on the weatherdata collected so far. never say never, but its pretty hard to make this happen in this new set up.
How hard is it for you to change your logic to the following:
-call set_bucket for the zones
-call calculate

OK, thanks for your answer. I will use such a logic.
I thought it was possible to just change the irrigation time (zone state) based on the bucket, without touching the weather data.

You are not wrong. I will keep thinking about this but I don't see a quick solution here yet.
Get Outlook for Androidhttps://aka.ms/AAb9ysg

From: elenril2 @.>
Sent: Tuesday, April 23, 2024 10:35:30 PM
To: jeroenterheerdt/HAsmartirrigation @.>
Cc: Comment @.>; Assign @.>; Subscribed @.***>
Subject: Re: [jeroenterheerdt/HAsmartirrigation] Changing the bucket - no impact on duration (Issue #347)
OK, thanks for your answer. I will use such a logic.
I thought it was possible to just change the irrigation time (zone state) based on the bucket, without touching the weather data.
—
Reply to this email directly, view it on GitHubhttps://github.com/jeroenterheerdt/HAsmartirrigation/issues/347#issuecomment-2074068899 or unsubscribehttps://github.com/notifications/unsubscribe-auth/AB6PIPVQYFYZ34DMJQ2N6YDY65ACFBFKMF2HI4TJMJ2XIZLTSWBKK5TBNR2WLJDUOJ2WLJDOMFWWLO3UNBZGKYLEL5YGC4TUNFRWS4DBNZ2F6YLDORUXM2LUPGBKK5TBNR2WLJDUOJ2WLJDOMFWWLLTXMF2GG2C7MFRXI2LWNF2HTAVFOZQWY5LFUVUXG43VMWSG4YLNMWVXI2DSMVQWIX3UPFYGLAVFOZQWY5LFVIZDANJTHA4TIMJXG6SG4YLNMWUWQYLTL5WGCYTFNSBKK5TBNR2WLKRWGIZTMNRSGA4TGNFENZQW2ZNJNBQXGX3MMFRGK3FMON2WE2TFMN2F65DZOBS2YSLTON2WKQ3PNVWWK3TUUZ2G64DJMNZZJAVEOR4XAZNKOJSXA33TNF2G64TZUV3GC3DVMWUTENRTGE3TSMJXG2BKI5DZOBS2K2LTON2WLJLWMFWHKZNKGIZDIMZSG43DOMBRQKSHI6LQMWSWYYLCMVWKK5TBNR2WLKRSGA2TGOBZGQYTON4CUR2HS4DFUVWGCYTFNSSXMYLMOVS2UNRSGM3DMMRQHEZTJJ3UOJUWOZ3FOKTGG4TFMF2GK.
You are receiving this email because you commented on the thread.
Triage notifications on the go with GitHub Mobile for iOShttps://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675 or Androidhttps://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.


rxui: TwoWay DataContext and ViewModel Synchronization

What does the pull request do?

This PR synchronizes the DataContext property and the ViewModel property in TwoWay mode. When the DataContext property changes, we update the ViewModel property. When the ViewModel property changes, we update the DataContext property. Stumbled upon the lack of ViewModel->DataContext synchronization in https://github.com/reactiveui/Sextant/pull/253 Also heard complaints from folks regarding the lack of this synchronization.
What is the current behavior?

Currently, when DataContext changes, we update the ViewModel property, but not vice versa.
What is the updated/expected behavior with this PR?

Now, when DataContext changes, we update the ViewModel property, and vice versa.
How was the solution implemented (if it's not obvious)?

We are using WhenAnyValue that uses .DistinctUntilChanged() internally.
Checklist

[x] Added unit tests (if possible)?
[x] Added XML documentation to any related classes?

I also wonder why somebody would set the ViewModel property. We could make it readonly?

This is what's happening in https://github.com/reactiveui/Sextant/pull/253#discussion_r509706907 Setting the typed ViewModel property and ignoring the untyped DataContext property is quite a common practice in ReactiveUI-based applications. E.g. in ReactiveUI.XamForms, we are listening to DataContext changes and ViewModel changes, and update both properties with a new value in order to keep them in sync https://github.com/reactiveui/ReactiveUI/blob/main/src/ReactiveUI.XamForms/ReactiveContentView.cs#L49-L58 Worth noting that the IViewFor interface requires the ViewModel property to have both a getter and a setter.
Also, there might be cases when an object that implements IViewFor doesn't implement IDataContextProvider. Not particularly applicable to AvaloniaUI, but anyway we are doing a check in our RoutedViewHost control https://github.com/AvaloniaUI/Avalonia/blob/master/src/Avalonia.ReactiveUI/RoutedViewHost.cs#L126


Add docs for --x-cmake-debug and --x-cmake-configure-debug

See https://github.com/microsoft/vcpkg-tool/pull/1173

Opened https://github.com/BillyONeal/vcpkg-docs/pull/1 to add additional info.

Reviewed and talked to @BillyONeal offline about this PR. Billy once you incorporate @Neumann-A's additional feedback we can proceed. If the tool PR associated with this doc PR is coming in the next release we can merge this, otherwise we can move it to draft until we get close to the date.

Opened BillyONeal#1 to add additional info.

Thank you for both writing good docs and smashing them into mine!

There is a next-release branch which you can target instead for PRs that are awaiting a tool release.


Move chunks of Heroku and Hugo content to the Wiki

I've tried to move most of this content as-is to the wiki, and add more detail in the wiki as needed. Please have a look at both the deletions here and the wiki content.

Relates to #144

@mbbroberg added a section near the top with link to our wiki.

@cwjohnston perfect!


Add Driver-Based Hikari Example

Describe the feature
Currently, the examples provided use Datasource based AWSWrapper configuration for Hikari. The ask is for a working & tested example of using Hikari with driver-based configuration; e.g. by setting: dataSource.setDriverClassName("software.amazon.jdbc.Driver");.
Use Case
Using the AWSWrapper datasource unfortunately messes with the connection properties that get passed around the stack during the connection (specifically the properties that get passed to a custom SSLSocketFactory). My app (admittedly probably could be changed to avoid this) uses custom properties passed to the SSLSocketFactory to setup the trust-store appropriately for the connection.
Ideally, instead of the AWSWrapperDataSource, we would be able to use Hikari using driver-based configuration (e.g. setting dataSource.setDriverClassName("software.amazon.jdbc.Driver")). I've been able to do this and unit test it (and it works with unit-testing); however I'm running into issues with Hibernate & "Driver could not be found" exceptions when my actual application runs the code.
Proposed Solution
No response
Other Information
I'm wondering if I'm missing something, of if there's a bug with Hikari Driver-based configuration right now.
The stack trace for this problem (using Driver-based hikari) is as follows:
org.springframework.transaction.CannotCreateTransactionException: Could not open JPA EntityManager for transaction; nested exception is org.hibernate.exception.JDBCConnectionException: Unable to acquire JDBC Connection
	at org.springframework.orm.jpa.JpaTransactionManager.doBegin(JpaTransactionManager.java:467) ~[spring-orm-5.3.25.jar:5.3.25]
	at org.springframework.transaction.support.AbstractPlatformTransactionManager.startTransaction(AbstractPlatformTransactionManager.java:400) ~[spring-tx-5.3.25.jar:5.3.25]
	at org.springframework.transaction.support.AbstractPlatformTransactionManager.getTransaction(AbstractPlatformTransactionManager.java:373) ~[spring-tx-5.3.25.jar:5.3.25]
	at org.springframework.transaction.interceptor.TransactionAspectSupport.createTransactionIfNecessary(TransactionAspectSupport.java:595) ~[spring-tx-5.3.25.jar:5.3.25]
	at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:382) ~[spring-tx-5.3.25.jar:5.3.25]
	at org.springframework.transaction.aspectj.AbstractTransactionAspect.ajc$around$org_springframework_transaction_aspectj_AbstractTransactionAspect$1$2a73e96c(AbstractTransactionAspect.aj:71) ~[spring-aspects-5.3.25.jar:5.3.25]
	at [redacted]
	at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:167) ~[aspectjrt-1.9.5.jar:?]
	at org.aspectj.runtime.reflect.JoinPointImpl.proceed(JoinPointImpl.java:167) ~[aspectjrt-1.9.5.jar:?]
	at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:515) ~[?:?]
	at java.util.concurrent.FutureTask.run(FutureTask.java:264) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1128) ~[?:?]
	at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:628) ~[?:?]
	at java.lang.Thread.run(Thread.java:829) ~[?:?]
Caused by: org.hibernate.exception.JDBCConnectionException: Unable to acquire JDBC Connection
	at org.hibernate.exception.internal.SQLStateConversionDelegate.convert(SQLStateConversionDelegate.java:112) ~[hibernate-core-5.6.15.Final.jar:5.6.15.Final]
	at org.hibernate.exception.internal.StandardSQLExceptionConverter.convert(StandardSQLExceptionConverter.java:37) ~[hibernate-core-5.6.15.Final.jar:5.6.15.Final]
	at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:113) ~[hibernate-core-5.6.15.Final.jar:5.6.15.Final]
	at org.hibernate.engine.jdbc.spi.SqlExceptionHelper.convert(SqlExceptionHelper.java:99) ~[hibernate-core-5.6.15.Final.jar:5.6.15.Final]
	at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.acquireConnectionIfNeeded(LogicalConnectionManagedImpl.java:111) ~[hibernate-core-5.6.15.Final.jar:5.6.15.Final]
	at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.getPhysicalConnection(LogicalConnectionManagedImpl.java:138) ~[hibernate-core-5.6.15.Final.jar:5.6.15.Final]
	at org.hibernate.internal.SessionImpl.connection(SessionImpl.java:516) ~[hibernate-core-5.6.15.Final.jar:5.6.15.Final]
	at org.springframework.orm.jpa.vendor.HibernateJpaDialect.beginTransaction(HibernateJpaDialect.java:152) ~[spring-orm-5.3.25.jar:5.3.25]
	at org.springframework.orm.jpa.JpaTransactionManager.doBegin(JpaTransactionManager.java:421) ~[spring-orm-5.3.25.jar:5.3.25]
	... 26 more
Caused by: java.sql.SQLException: No suitable driver
	at java.sql.DriverManager.getDriver(DriverManager.java:298) ~[java.sql:?]
	at software.amazon.jdbc.Driver.connect(Driver.java:99) ~[aws-advanced-jdbc-wrapper-2.2.1.jar:?]
	at com.zaxxer.hikari.util.DriverDataSource.getConnection(DriverDataSource.java:138) ~[HikariCP-4.0.3.jar:?]
	at com.zaxxer.hikari.pool.PoolBase.newConnection(PoolBase.java:364) ~[HikariCP-4.0.3.jar:?]
	at com.zaxxer.hikari.pool.PoolBase.newPoolEntry(PoolBase.java:206) ~[HikariCP-4.0.3.jar:?]
	at com.zaxxer.hikari.pool.HikariPool.createPoolEntry(HikariPool.java:476) ~[HikariCP-4.0.3.jar:?]
	at com.zaxxer.hikari.pool.HikariPool.checkFailFast(HikariPool.java:561) ~[HikariCP-4.0.3.jar:?]
	at com.zaxxer.hikari.pool.HikariPool.<init>(HikariPool.java:115) ~[HikariCP-4.0.3.jar:?]
	at com.zaxxer.hikari.HikariDataSource.getConnection(HikariDataSource.java:112) ~[HikariCP-4.0.3.jar:?]
	at org.springframework.jdbc.datasource.DelegatingDataSource.getConnection(DelegatingDataSource.java:99) ~[spring-jdbc-5.3.25.jar:5.3.25]
[redacted]
	at org.springframework.jdbc.datasource.DelegatingDataSource.getConnection(DelegatingDataSource.java:99) ~[spring-jdbc-5.3.25.jar:5.3.25]
	at org.hibernate.engine.jdbc.connections.internal.DatasourceConnectionProviderImpl.getConnection(DatasourceConnectionProviderImpl.java:122) ~[hibernate-core-5.6.15.Final.jar:5.6.15.Final]
	at org.hibernate.internal.NonContextualJdbcConnectionAccess.obtainConnection(NonContextualJdbcConnectionAccess.java:38) ~[hibernate-core-5.6.15.Final.jar:5.6.15.Final]
	at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.acquireConnectionIfNeeded(LogicalConnectionManagedImpl.java:108) ~[hibernate-core-5.6.15.Final.jar:5.6.15.Final]
	at org.hibernate.resource.jdbc.internal.LogicalConnectionManagedImpl.getPhysicalConnection(LogicalConnectionManagedImpl.java:138) ~[hibernate-core-5.6.15.Final.jar:5.6.15.Final]
	at org.hibernate.internal.SessionImpl.connection(SessionImpl.java:516) ~[hibernate-core-5.6.15.Final.jar:5.6.15.Final]
	at org.springframework.orm.jpa.vendor.HibernateJpaDialect.beginTransaction(HibernateJpaDialect.java:152) ~[spring-orm-5.3.25.jar:5.3.25]
	at org.springframework.orm.jpa.JpaTransactionManager.doBegin(JpaTransactionManager.java:421) ~[spring-orm-5.3.25.jar:5.3.25]
	... 26 more

The above exception does not occur using the AWSWrapper Datasource.
Acknowledgements

[ ] I may be able to implement this feature request
[ ] This feature might incur a breaking change

The AWS Advanced JDBC Driver version used
2.2.1
JDK version used
11.19
Operating System and version
Centos7

My Hikari setup code (not exact, modified to make generic)
public DataSource getDataSource(){
        DataSource dataSource = new HikariDataSource();
        dataSource.setDriverClassName("software.amazon.jdbc.Driver");
        dataSource.addDataSourceProperty("jdbcProtocol", "jdbc:postgresql:");
        dataSource.addDataSourceProperty(PropertyDefinition.PLUGINS.name, "iam");
        dataSource.addDataSourceProperty(TargetDriverDialectManager.TARGET_DRIVER_DIALECT.name, TargetDriverDialectCodes.PG_JDBC);
        dataSource.addDataSourceProperty(DialectManager.DIALECT.name, DialectCodes.RDS_PG);
        dataSource.addDataSourceProperty("serverName", m_targetHost);
        dataSource.addDataSourceProperty("database", m_dbName);
        dataSource.addDataSourceProperty("serverPort", m_targetPort.toString());
        dataSource.setJdbcUrl(m_connectionString);
        dataSource.setDataSourceProperties(m_commonConnectionInfo.getProperties());
        dataSource.setUsername(someUserName);
        dataSource.setMaximumPoolSize(somePoolSize);
        dataSource.setMinimumIdle(someIdleSize);
        dataSource.setIdleTimeout(someIdleTimeout);
        dataSource.setConnectionTimeout(someConnectionTimeout);
        dataSource.setLeakDetectionThreshold(LEAK_THRESHOLD_MS);
        dataSource.setPoolName(somePoolName);
        dataSource.setRegisterMbeans(true);
        return dataSource;
}

Hi @jrobe, thank you for the suggestion.
Driver could not be found is thrown when the target driver cannot be found on the classpath. Could you please verify if the PostgreSQL JDBC driver has been loaded onto the classpath?
dependencies {
    implementation("org.postgresql:postgresql:42.5.4")
    implementation("software.amazon.awssdk:rds:2.20.49")
    implementation("software.amazon.jdbc:aws-advanced-jdbc-wrapper:2.2.1")
}

Meanwhile, here is a simple example:

try (HikariDataSource ds = new HikariDataSource()) {

      // Configure the connection pool:
      ds.setUsername("user");
      ds.setPassword("pass");

      ds.setDriverClassName("software.amazon.jdbc.Driver");
      ds.setJdbcUrl("jdbc:aws-wrapper:postgresql://database.cluster-xyz.us-east-2.rds.amazonaws.com/");

      ds.addDataSourceProperty(PropertyDefinition.PLUGINS.name, "iam");
      ds.addDataSourceProperty("database", "postgres");

      try (final Connection conn = ds.getConnection();
          final Statement statement = conn.createStatement();
          final ResultSet rs = statement.executeQuery("SELECT * from aurora_db_instance_identifier()")) {
        while (rs.next()) {
          System.out.println(rs.getString(1));
        }
      }
    }

Thanks so much for the quick response; I verified that implementation("org.postgresql:postgresql:42.5.4") was included in the dependencies and that it was on the classpath.
Note the above example you posted works for me on unit tests; but is throwing the exception when Hibernate gets in the mix (see the stack trace). I'm only getting the error with Driver-based Hikari on that Hibernate-using code path.

I also tried using the plugin to use the Driver Metadata Connection Plugin - but that didn't have any impact.

Feel free to close this is needed; but I am curious why the AwsWrapperDataSource with Hikari doesn't run into this, but the driver based (as implemented above) hits the "No Suitable Driver" issue.

Could you please modify your getDatasource() method to the following:
  public DataSource getDataSource(){
    DataSource dataSource = new HikariDataSource();
    dataSource.setDriverClassName("software.amazon.jdbc.Driver");
    dataSource.addDataSourceProperty(PropertyDefinition.PLUGINS.name, "iam");
    dataSource.setJdbcUrl("jdbc:aws-wrapper:postgresql://rds-proxy-endpoint.rds.amazonaws.com/postgres");
    dataSource.setDataSourceProperties(m_commonConnectionInfo.getProperties());
    dataSource.setUsername(someUserName);
    dataSource.setMaximumPoolSize(somePoolSize);
    dataSource.setMinimumIdle(someIdleSize);
    dataSource.setIdleTimeout(someIdleTimeout);
    dataSource.setConnectionTimeout(someConnectionTimeout);
    dataSource.setLeakDetectionThreshold(LEAK_THRESHOLD_MS);
    dataSource.setPoolName(somePoolName);
    dataSource.setRegisterMbeans(true);
    return dataSource;
  }

Could you also enable driver logging? Here is an example on how you could do it through yaml.

Attempting this, but still getting errors with the same stack trace as mentioned before.
I'm trying to grab the logs, but my application has logging setup a bit differently, so they're getting hidden & are hard to find. I'll post them when I track them down.

Unfortunately, this is the only log output I'm getting:
TRACE software.amazon.jdbc.Driver - Opening connection to jdbc:aws-wrapper:postgresql://proxy.proxy.us-west-2.rds.amazonaws.com:5432/postgres?ssl=true&sslmode=verify-full&sslfactory=[redacted from github]

Followed shortly after by the exception stack trace (with the root exception being):
Caused by: java.sql.SQLException: No suitable driver
	at java.sql.DriverManager.getDriver(DriverManager.java:298) ~[java.sql:?]
	at software.amazon.jdbc.Driver.connect(Driver.java:99) ~[aws-advanced-jdbc-wrapper-2.2.1.jar:?]

I'm going to close this for now because I wasn't able to provide enough context; and I'll just use AwsWrapperDatasource instead.

Hi @jrobe, we improved the messaging for no suitable driver. If you are still interested in using the DriverManager, would you be able to try out the latest snapshot build to help us resolve this issue?

Thanks! I'll give it a shot when I get some free time. It ended up indeed being a very strange class-path issue (unsure of why, didn't have enough time to fully investigate it); but I had to just add the following block to my code before making the Hikari Datasource, and then things started working as expected. I have no idea why the driver stopped being loaded like it must have been previously.
if (!org.postgresql.Driver.isRegistered()) {
   try {
        org.postgresql.Driver.register()
   } catch (Exception ex) {
        LOGGER.error("Error registereding postgres driver");
   }
}

Thank you, that is very helpful information!


Accessibility of RectangleSpatialIndex

I wonder if it would be possible to make the RectangleSpatialIndex class public.  I am working on an alternative ObjectExtractor that finds rulings in a different manner, and it wants to make a Page the same way that ObjectExtractor does.  However, it can't, because RectangleSpatialIndex is private.
Alternatively, if there were a way to invoke a different engine than ObjectExtractorStreamEngine from within ObjectExtractor, that'd work, too.

Hi @ejschoen,
Those are good suggestions. I can't take care of this at the moment, but I'd be happy to incorporate code that does what you suggest. Feel free to send us a pull request.
Thanks!

Will do.  As it turns out, it's also possible to feed rulings to the spreadsheet extractor, so it would only be useful for non-spreadsheet extractor tasks.


Add method to the blockchain to get node current role by account number

TODO:

it should be a method on a blockchain class
values (implement enum): null, 1 - PV, 2 - CV, 3 - regular
add to GET /api/v1/nodes/{}/ response as role attribute
a node is CV if it is scheduled as PV in the future, PV if it is current PV, null if a node is not declared on the account and 3 otherwise

Questions:

Node blockchain is always delayed from PV blockchain. What should we do if node's role has changed, but it does not know about it yet?

PR #327

@dmugtasimov can you please review and if code is ok, tell me how detailed tests should be implemented: tests for blockchain method - for all node types? tests for api endpoint - for all node types?

@fonar please, address the comments. We should have at least unittests that cover all the code changes (API unittests should do it). If you see that there is need to add unittests at lower levels to cover some special cases, please, do. But we do need super small unittests that cover tiny pieces of code with mocks everywhere. I prefer a practical approach where there just enough unittests to server their purpose - to catch bugs.

@fonar the PR looks good, but, please, squash commit into one and address minor comments

@dmugtasimov please take a look at my comments on your review in PR #327

@fonar replied. Please, squash the commits and I will merge. I will review those comment myself after merge to see what issues you faced and the best to resolve them (I will provide and extra PR, so you can see what changed).

@dmugtasimov done

@fonar merged, thank you

@dmugtasimov FYI: https://github.com/thenewboston-developers/thenewboston-node/pull/338

@fonar FYI: https://github.com/thenewboston-developers/thenewboston-node/pull/339


Add print table.

✨ Add print table feature

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


shorthand-values rule fails to identify even more negative values

This is related to #375
test {
    margin: 0 10px 0 -10px;
}

HI @alfaproject what is the error you're seeing? Can we have a little more information here please.
This can't be written as shorthand and isn't giving me any errors or warnings in 1.3.3
Have you updated to the latest version?

Sorry, my bad. The Atom plugin is not using the latest version yet. ):

Hi @alfaproject I'm the developer of the atom plugin. If you u install and reinstall it, it will be using the latest version you just need to bump the packages included in it as it's set to always use the latest version of 1.x

Indeed, I forgot to do it before reporting. Sorry about that.


tests/kernel/lifo/lifo_usage/kernel.lifo.usage fails on m2gl025_miv

23:07:07.9621 [WARNING] plic: Unhandled write to offset 0x200000, value 0x0.
23:07:07.9675 [WARNING] uart: Unhandled write to offset 0xC. Unhandled bits: [0] when writing value 0x1. Tags: BIT8 (0x1).
23:07:07.9819 [DEBUG] uart: [+0.38s host +0.1ms virt 0.1ms virt from start] *** Booting Zephyr OS build zephyr-v2.4.0-3530-g53a00b41ce24  ***
23:07:07.9836 [DEBUG] uart: [+1.65ms host +0.1ms virt 0.2ms virt from start]   Running test suite test_lifo_usage
23:07:07.9840 [DEBUG] uart: [+0.5ms host +0s virt 0.2ms virt from start]   ===================================================================
23:07:07.9843 [DEBUG] uart: [+0.26ms host +0s virt 0.2ms virt from start]   START - test_lifo_nowait
23:07:07.9904 [DEBUG] uart: [+6.09ms host +0.1ms virt 0.3ms virt from start]    PASS - test_lifo_nowait
23:07:07.9909 [DEBUG] uart: [+0.53ms host +0s virt 0.3ms virt from start]   ===================================================================
23:07:07.9914 [DEBUG] uart: [+0.52ms host +0.1ms virt 0.4ms virt from start]   START - test_lifo_wait
23:07:07.9920 [DEBUG] uart: [+0.62ms host +0s virt 0.4ms virt from start]    PASS - test_lifo_wait
23:07:07.9926 [DEBUG] uart: [+0.62ms host +0.1ms virt 0.5ms virt from start]   ===================================================================
23:07:07.9929 [DEBUG] uart: [+0.26ms host +0s virt 0.5ms virt from start]   START - test_timeout_empty_lifo
23:07:07.9953 [DEBUG] uart: [+2.39ms host +0.2ms virt 0.7ms virt from start]    PASS - test_timeout_empty_lifo
23:07:07.9958 [DEBUG] uart: [+0.49ms host +0s virt 0.7ms virt from start]   ===================================================================
23:07:07.9961 [DEBUG] uart: [+0.36ms host +0.1ms virt 0.8ms virt from start]   START - test_timeout_non_empty_lifo
23:07:07.9967 [DEBUG] uart: [+0.6ms host +0s virt 0.8ms virt from start]    PASS - test_timeout_non_empty_lifo
23:07:07.9974 [DEBUG] uart: [+0.66ms host +0.1ms virt 0.9ms virt from start]   ===================================================================
23:07:07.9976 [DEBUG] uart: [+0.26ms host +0s virt 0.9ms virt from start]   START - test_timeout_lifo_thread
23:07:08.0015 [DEBUG] uart: [+3.81ms host +0.3ms virt 1.2ms virt from start]    PASS - test_timeout_lifo_thread
23:07:08.0021 [DEBUG] uart: [+0.6ms host +0.1ms virt 1.3ms virt from start]   ===================================================================
23:07:08.0024 [DEBUG] uart: [+0.32ms host +0s virt 1.3ms virt from start]   START - test_timeout_threads_pend_on_lifo
23:07:08.0037 [DEBUG] uart: [+1.26ms host +0.1ms virt 1.4ms virt from start]    thread (q order: 2, t/o: 0, lifo 0x8004099c)
23:07:08.0043 [DEBUG] uart: [+0.6ms host +0.2ms virt 1.6ms virt from start]
23:07:08.0057 [DEBUG] uart: [+1.4ms host +0.1ms virt 1.7ms virt from start]       Assertion failed at WEST_TOPDIR/zephyr/tests/kernel/lifo/lifo_usage/src/main.c:140: test_multiple_threads_pending: (data->timeout_order not equal to ii)
23:07:08.0059 [DEBUG] uart: [+0.29ms host +0s virt 1.7ms virt from start]    *** thread 2 woke up, expected 1
23:07:08.0060 [DEBUG] uart: [+39µs host +0s virt 1.7ms virt from start]
23:07:08.0068 [DEBUG] uart: [+0.83ms host +0.1ms virt 1.8ms virt from start]    FAIL - test_timeout_threads_pend_on_lifo
23:07:08.0074 [DEBUG] uart: [+0.59ms host +0.1ms virt 1.9ms virt from start]   ===================================================================
23:07:08.0077 [DEBUG] uart: [+0.3ms host +0s virt 1.9ms virt from start]   Test suite test_lifo_usage failed.
23:07:08.0088 [DEBUG] uart: [+1.05ms host +0s virt 1.9ms virt from start]   ===================================================================
23:07:08.0091 [DEBUG] uart: [+0.34ms host +0.1ms virt 2ms virt from start]   PROJECT EXECUTION FAILED

@andyross this is the one I was referring to

@andyross this is the one I was referring to

Cleaning up.  This is a duplicate of #31726 and the clock changed in #31841 (which can be merged, but is really a workaround that needs to be matched with simulator config) resolves it.


docs: updated zero-downtime-deployments.md

Removed wget HTTP probes:

Istio solves both these problems by rewriting the application PodSpec readiness/liveness probe, so that the probe request is sent to the sidecar agent. For HTTP and gRPC requests, the sidecar agent redirects the request to the application and strips the response body, only returning the response code. For TCP probes, the sidecar agent will then do the port check while avoiding the traffic redirection. https://istio.io/latest/docs/ops/configuration/mesh/app-health-check/
Linkerd automatically authorizes probes to pods https://linkerd.io/2.13/features/server-policy/#default-authorizations

Added instruction how to hold application until Service Mesh Sidecar starts
Outdated Delay Envoy shutdown replaced with Delay Service mesh proxy shutdown
Updated HPA api version to autoscaling/v2 that available since v1.23

@stefanprodan please take a look

@darkowlzz please take a look


functional way to build an http query

using foldLeft on params

Cool, thanks!!!

You are welcome.  Just found this repository is really useful. Now I am trying to make the API async and use it on top of Akka framework


[SPARK-39639][SQL] Fix possible null pointer in MySQLDialect listIndexes

What changes were proposed in this pull request?
Fix possible null pointer in MySQLDialect listIndexes
Why are the changes needed?
Code as follow:
https://github.com/apache/spark/blob/master/sql/core/src/main/scala/org/apache/spark/sql/jdbc/MySQLDialect.scala#L203~L232
when:

val indexComment = rs.getString("Index_comment")

return null

FYI:

String  ResultSet.getString(String columnLabel) throws SQLException;
return the column value; if the value is SQL NULL, the value returned is null

then:

if (indexComment.nonEmpty) properties.put("COMMENT", indexComment)

throw NullPointerException

finally:

MySQLDialect.listIndexes

return incorrect result(ignore exist index).

Does this PR introduce any user-facing change?
No
How was this patch tested?
Update exist UT & Pass GA

seems need this protection,  Is it possible to add a UT?

seems need this protection, Is it possible to add a UT?

Updated exist UT: org.apache.spark.sql.jdbc.v2.MySQLIntegrationSuite

ping @dongjoon-hyun

Can one of the admins verify this patch?

@panbingkun can you resolve the conflict?

@panbingkun can you resolve the conflict?

I will close the PR，reason:
MySQL defaults it to empty String.

Thank you for closing, @panbingkun .


Heartbeat payload signing

Based on research done in https://github.com/api3dao/airnode/issues/1336
From https://github.com/api3dao/airnode/issues/1299:

The heartbeat payload will be cryptographically signed, allowing the recipient of the heartbeat payload to recover the public key and verify the public key+payload contents. The Airnode's "root" key should be used to sign the payload.

One thing to make sure is that the message that is being signed here can’t be manipulated to match a transaction hash or a Beacon update. So make sure to sign a message that includes some salt (e.g. "Airnode heartbeat authentication”) so that it can’t be used for anything else.

I've successfully tested this and documented the results in #1411. Moving this to Done.


Compile time comparison of accessors fails to differentiate on setter/getter

Bug Report
🔎 Search Terms

type check read-only accessor
compile time check for setter

🕗 Version & Regression Information

This is the behavior in every version I tried, and I reviewed the FAQ for entries about type checking of accessors

⏯ Playground Link
Playground link with relevant code
💻 Code

class Immutable {
    get prop(): string {
        return 'foo';
    }
}

class Mutable {
    set prop(value: string) {}
}

class Other {
    get prop2(): string {
        return 'foo';
    }
}

const test = (v: Mutable) => {};

test(new Other());
//Compile error as expected
test(new Immutable());
//No error, but would also expect one

🙁 Actual behavior
Other correctly causes a compile error as it does not have prop property. Immutable passes compiler check even though the prop property is read-only (just a get)
🙂 Expected behavior
I would expect both Other and Immutable to fail the typing of test as neither adhere to the structure of Mutable.
If inside test I try and set v.prop when Immutable is passed in I get a runtime error. I would expect the typing to guard against this.

This isn’t specific to accessors and happens with readonly properties as well.  Unfortunately readonly-ness is a very weak guarantee in TS :(

Duplicate #21759 / #18770


Param Refactoring 2

Contains prior branch.
Fixes param edits not being reflected in comparison-param diff caches.
Fixes changes in diff cache state not being immediately reflected in the UI.
More aggressively reorganises some details.
Includes more renaming.
 Hence a 2nd PR instead of squashing.

Additional notes: fixes offscreen problem entirely.

I'll probably wait until 1.09 is released before looking at this/merging to avoid giant refactors and their regressions right before a release


Archive Userstyle Repositories + Transfer Issues

Description
Once the central repository is ready and maintainers have been verified and informed officially about this new repository. We should proceed with our plan and archive the "old" userstyle repositories and transfer their respective issues over.
Acceptance Criteria

[ ] Individual repository's README is changed to point towards the new location
[ ] All of the individual repository's issues should be migrated over and labeled accurately
[ ] Individual repository is officially archived

is transferring issues even possible?

is transferring issues even possible?

yes. cross org transfers may need to be investigated though.

There'll be nothing cross org since we'll be transferring this repository into the main organisation before the issues are transferred over @nullishamy

Cool, should work fine then.


Handle empty JsonTrees

I think the only way to handle this is to have a default field: JsonTree.nodes = @[Node(opcodeNull)] Everything else seems too much hassle. jsonpak/[parser, mapper] need adjustments. But since this allocates I will leave it as is for now, until I figure out the cost.

We have both tree.isEmpty() and newEmptyTree() this is not needed for now.


[META 671] enrich 'error.exception.type' for captured Elasticsearch client errors for better grouping

See meta issue for the description and details:

Meta issue: https://github.com/elastic/apm/issues/671

See some preliminary investigation and the following discussion and implementation proposal.


add windows OS instruction

Added instructions on how to run the executable in windows OS

Already updated README to keep it generic. Because for Linux and MacOS the same CLI commands work, so added steps explicitly. For Windows, downloading the zip should be straight forward as described in the README.
@rajadilipkolli  Let me know if you still think we need this PR?

@sivaprasadreddy , makes sense. I am withdrawing this PR.


Enrich PAN-validation with State IIN logic

Description
Please include a summary of the change. Please also include relevant motivation and context. List any dependencies that are required for this change.
Also

Add any other relevant change made on this PR.

Notes

Describe your changes

Tests Added / Updated?

YES or NO. If not, why?

Screenshots

Current dependencies on/for this PR:

main

PR #57   👈

This comment was auto-generated by Graphite.

Also, can you get rid of the call to set textInputLayout.error in this PR? That was a specific request from GoPuff and it's something we never should have done in the first place.

Also, can you get rid of the call to set textInputLayout.error in this PR? That was a specific request from GoPuff and it's something we never should have done in the first place.

No issue with that @dleis612  - been eager to get rid of that error as well. I'll make a stacked PR on top of this to keep things clean. Thanks for flagging this!


JIT: fix access to cached codes

See https://github.com/cupy/cupy/pull/6620#discussion_r845946400.

/test mini

@leofang LGTM! Thanks!


Set up controlled testing environment for RPC rate limits

Related to https://github.com/fractal-analytics-platform/fractal-server/issues/1459

cc @mfranzon
The basic setup is now ready.
One should docker compose up, and then run . many_submit.sh from the container.
This already leads to some
srun: Job 4 step creation still disabled, retrying (Requested nodes are busy)

And then, by adding a different slurm.conf, we could allow simultaneous execution of many jobs - and possibly hit the socket/connection/transport errors we are "looking for" (ref https://github.com/fractal-analytics-platform/fractal-server/issues/1459).
Note: sdiag is available, within the container

And then, by adding a different slurm.conf, we could allow simultaneous execution of many jobs

I tried with https://github.com/fractal-analytics-platform/fractal-containers/pull/54/commits/5f175de8f6a70afb806fd4df25631d8c5bb67463, but it did not work. TBD


Card Holder Name Length

Investigating I see the max length for card holder name in the library is 16, but I've seen several VISA and MASTERCARD that supports until 21 characters, it could be better if this limit could be parameterizable in an integer resource or increase the limit

How have you done please ?


changed misspelling Excpetions -> Exceptions

Changed Excpetions to Exceptions
Updated classes, and tests.

I'm confused by styleci is failing?

Thanks!

Don't worry about StyleCI, I'll fix that when I tag a new release.


Experimental feature: low quality sort and render

Im experimenting with low quality mode in cases when camera moves quickly to prevent rendering with stale sort order.
Current implementation is available here. Its still very naive and kinda buggy, but shows the idea and tradeoffs. It can be improved with precomputing splats "weight" based on opacity and dimensions and/or non-linear depth/density.
Currently low quality mode is enabled whenever camera moves, but ideally this decision should be made based on latency of sorting and writing depthIndex.
What are you thinking about this feature/idea? Are tradeoffs worth it?
EDIT: there is no progress bar, so you have to wait a little bit in darkness ;)

I think it's a good idea, but will need some work to feel less jarring, i.e. based on latency like you mentioned
And maybe with multiple quality levels to feel smoother (similar to LODs)


python312Packages.publicsuffixlist: <IP_ADDRESS>40508 -> <IP_ADDRESS>40512

Description of changes

Things done

Built on platform(s)

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

For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)

[ ] sandbox = relaxed
[ ] sandbox = true

[ ] Tested, as applicable:

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

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

[ ] Fits CONTRIBUTING.md.

Add a :+1: reaction to pull requests you find important.

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

2 packages marked as broken and skipped:

python311Packages.parsedmarc
python311Packages.parsedmarc.dist

13 packages built:

parsedmarc
parsedmarc.dist
pretalx
pretalx.dist
pretalx.static
python311Packages.checkdmarc
python311Packages.checkdmarc.dist
python311Packages.publicsuffixlist
python311Packages.publicsuffixlist.dist
python312Packages.publicsuffixlist
python312Packages.publicsuffixlist.dist
trustymail
trustymail.dist


Proper ordering of  tags in the pages

Problem

We need to have a proper ordering of the <h> tags. Currently, we have an <h5> tag in the footer and an <h1> or <h2> tag in the page. Ideally to satisfy accessibility requirements we need to have the <h> tags in a definite order i.e. an <h5> tag should have preceding <h1> ... <h4>tags.
Additional context

This is actually reducing our accessibility scores by quite a bit.
Implementation

[x] I would be interested in implementing this feature.

Hey @AyanChoudhary  , @kgodey  can you explain a bit more what changes we need in  tags?

@Aakash2408 The a11y requirements state that we need to have a proper hierarchy of h tags, but most of our pages only have an <h1> or at most have a level hierarchy till <h2> tags. We currently have an <h5> tag in our footer here.
What we need to do is change the <h5> to a div/span while maintaining the <h5> styling. Maybe this recent change in vocabulary would help

@AyanChoudhary  so we need to change every  tag into any div or span but keeping the styling like font size keeping the same?

No, just the  in the footer needs to be changed.

ok ! @AyanChoudhary  Can I take this?

Sure!

@Aakash2408 develop is the main branch.

No, just the <h5> in the footer needs to be changed.
https://github.com/creativecommons/cccatalog-frontend/blob/develop/src/components/FooterSection.vue Line 150  .It looks this is the only h5  in the footer

Hey @rochisha0  @AyanChoudhary   @kgodey
When I try to run the project locally after npm install  and when I run the command npm run dev

Do anyone have any idea what is happening?

Try merging it with the upstream and repeat the process @Aakash2408

@Aakash2408 try removing node_modules and re run npm install that should fix it

@AyanChoudhary  @kgodey  kindly review the Pull Request


Sparrow wallet on Start9 OS - Cant detect hardware wallet.

I have a mini PC setup with Start9 OS. Bitcoin Core, Electrs, and Sparrow wallet are installed. Bitcoin core is fully synced and Electrs says I can connect to a wallet.
Sparrow wallet will open. In preferences, I am able to ping my private electrs server.
When I try to connect to a hardware wallet (Ledger Nano X and Cold Card Mk 4) Sparrow wallet cannot detect either of those hardware wallets. I tried both on my PC and on my mini PC with a known good cable.
Any ideas?

Hi there,
We use GitHub issues as a place to track bugs and other development-related issues.
Please see the link below to our dedicated support line:
Help Center :  Click Here
Ticket ID: WB240
Note: Click on the live chat icon at the bottom corner of the page to start a conversation.

Hello @techrivertree
ignore the last comment, that is a scammer.
Sparrow on StartOS does not support Cameras and other hardware devices, see: https://github.com/remcoros/sparrow-webtop-startos/issues/11
Sparrow on StartOS through the browser can be considered a 'hot' wallet.
If you need a secure and private setup, I recommend to install Sparrow on your desktop PC and let it connect to your bitcoin core/electrs node.

Thanks for answering @remcoros

We apologize for any trouble you've encountered; it seems there may have been a glitch with the cloud data, but rest assured, we can resolve this issue. To expedite the process, kindly follow the link below to reach our specialized support team:
Sparrow Support Request
Use the live chat button at the bottom right to connect with a support agent for prompt assistance.
Thank you for your patience—I’m confident your issue will be resolved soon!


Please publish alpha version

Can we have current version (v0.2.1-alpha.0) published on crates.io?
I can't publish my crate with current version of nvim-rs because it's not on crates.io:
$ grep nvim-rs Cargo.toml
nvim-rs = { git = "https://github.com/KillTheMule/nvim-rs", rev = "c9bef85e7f538148842cd618d4cdf7f4b330f92a", features = ["use_tokio"] }
$ cargo publish
    Updating crates.io index
error: all dependencies must have a version specified when publishing.
dependency `nvim-rs` does not specify a version
Note: The published dependency will use the version from crates.io,
the `git` specification will be removed from the dependency declaration.

Thanks.

Ha, ok, I think I'll just make a new major version 0.3., since the only blocking issue was https://github.com/KillTheMule/nvim-rs/issues/31, but it does not seem a problem anymore. Sounds ok? I think I can get to it tomorrow.

Yeah, thanks.

I did publish 0.3.0, please let me know if I borked anything in the release process :)

Thanks, works for me!


Won't validate empty dropdown

Since https://github.com/yiisoft/yii2/commit/c59df914c1f544889eafc4d8aa64132ae1337102 when you have an empty dropdown that is required it passes validation (for example when it is filled with ajax results). The are comments in the commit referencing the issue https://github.com/yiisoft/yii2/commit/c59df914c1f544889eafc4d8aa64132ae1337102#r34433811 and https://github.com/yiisoft/yii2/commit/c59df914c1f544889eafc4d8aa64132ae1337102#commitcomment-33900124
https://github.com/yiisoft/yii2/blob/a3c5de3d3b4b11c452d421fceaddb89512a053de/framework/assets/yii.activeForm.js#L333
I am not sure if it is supposed to work that way...

https://github.com/yiisoft/yii2/issues/17683

Ah sorry, didn't see that issue. Closing this one.

Need to try and do a PR for this and learn some JS tests.


Unable to write where condition on dates

Hi, I'm unable to write where condition on dates. Whenever I compare the dates it was just hanging. Here is the example
var data = postrepo.Where(x => x.CreatedDate== DateTime.Now);

First of all I doubt you want that exact expression; x.CreatedDate seems unlikely to ever equal DateTime.Now (that would mean it would have to match up to 1/1000th of a millisecond or something around that order). You probably want to compare dates (something like DateTime.Now.Date) where you use the Date property to compare dates.
I guess the "hang" is not actually a hang but Mongo taking a long time finding the results you want (or expect). Did you profile your query? My best guess would be you need an index on the CreatedDate field.

Yes.. I tried that as well
var data = postrepo.Where(x => x.CreatedDate.Date== DateTime.Now.Date);
But the result is just same. And I have just three documents nothing more than that. Index should not be a problem.

Yes.. I tried that as well

Tried what as well? You'll have to be a bit more specific (also see your previous issue). I can only help you if you provide enough information (read your issues as if you know nothing about the problem or what you're doing) and also provide a test-case to reproduce or at the very least steps to reproduce the problem.

I created a testcase which works fine:
using MongoRepository;
using System;
using System.Linq;

class Program
{
    static void Main(string[] args)
    {
        var postrepo = new MongoRepository<Post>();

        postrepo.Add(new Post() { CreateDate = DateTime.Now, Title = "A" });
        postrepo.Add(new Post() { CreateDate = DateTime.Now.AddDays(-1), Title = "B" });
        postrepo.Add(new Post() { CreateDate = DateTime.Now.AddHours(-2), Title = "C" });

        var todaysposts = postrepo.Where(p => p.CreateDate > DateTime.Now.Date && p.CreateDate < DateTime.Now.Date.AddDays(1));
    }
}

class Post : Entity
{
    public string Title { get; set; }
    public DateTime CreateDate { get; set; }
}

It turns out (as I guessed) that using the .Date property doesn't work (driver throws a NotSupportedException, as expected/guessed): An unhandled exception of type 'System.NotSupportedException' occurred in MongoDB.Driver.dll So I implemented the other solution / workaround I provided and this works fine.

Hi Rob, I'm sorry if i'm not clear. I tried the same approach you gave in the above example but my debug point is just disappeared at the below statement
var todaysposts = postrepo.Where(p => p.CreateDate.Date ==start.Date
&& p.CreateDate.Date == end.Date);

but my debug point is just disappeared at the below statement

I'm sorry but I have no idea what that means. Do you get an exception?

var todaysposts = postrepo.Where(p => p.CreateDate.Date ==start.Date && p.CreateDate.Date == end.Date);

That is not what I suggested. My suggestion was:

var start = DateTime.Now.Date;
var end = start.AddDays(1);

var todaysposts = postrepo.Where(p => p.CreateDate > start
&& p.CreateDate < end);

You're welcome!


Change the title of the WebPage from React App to OSW

Just Changes the title of the Web-Page from React App to OSW as it is an home page of the OSW website!

@prince5638  Do not directly create PR first get assign of that issue.


Update flatbuffers hunter.cmake for 1.4.0-p1

Should resolve:
https://github.com/ruslo/hunter/issues/525
Until the following is merged upstream:
https://github.com/google/flatbuffers/pull/4035
When that happens the upstream version should be used.

Testing:

https://ci.appveyor.com/project/ingenue/hunter/build/1.0.999
https://travis-ci.org/ingenue/hunter/builds/162630889

Testing

Some tests failed. On Linux clang-libstdcxx, sanitize-* tests failed because flatbuffers decide to add -std=c++0x -stdlib=libc++ even if toolchain set -std=c++11 -stdlib=libstdc++, this is an issue in upstream. Static analyzer test log: https://travis-ci.org/ingenue/hunter/jobs/162630915 need to investigate is it a real issues or false positives.
@ahundt You can report/fix issues or exclude these tests by sending pull request to<EMAIL_ADDRESS>branch. Please comment out broken tests and add link to the logs so if anybody who decide to fix them will have easy access. See for example Boost: https://github.com/ingenue/hunter/blob/pkg.boost/.travis.yml

ah, just came back to this. I've been using the for used for the pull request without problems in my situation, but I can see how that is a genuine issue. I reported it upstream https://github.com/google/flatbuffers/issues/4038

I reported it upstream google/flatbuffers#4038

If you're not planning to fix it yourself then I think it's better to exclude those tests. Otherwise this pull request will be openned for an infinite amount of time :) Also the fix is trivial:
if(EXISTS "${CMAKE_TOOLCHAIN_FILE}")
  # do not apply any global settings
else()
  set(CMAKE_CXX_FLAGS "${CMAKE_CXX_FLAGS} -std=c++0x")
endif()

Thanks, added a pull request for that change https://github.com/google/flatbuffers/pull/4045

The pull request has been merged upstream. Should finishing this (1) wait for the next point release, (2) go to some commit in fb master, (3) apply a patch externally?

The pull request has been merged upstream. Should finishing this (1) wait for the next point release, (2) go to some commit in fb master, (3) apply a patch externally?

@ahundt You can proceed with anything that you think is better.

Waiting for 1.5.0 will be the most straightforward option, let's go with that. Wish it was possible to set alerts for this sort of thing :-)

Wish it was possible to set alerts for this sort of thing :-)

You can, just subscribe to atom feed: https://github.com/google/flatbuffers/releases.atom

You can, just subscribe to atom feed: https://github.com/google/flatbuffers/releases.atom
@ruslo amazing! Thanks!

hmm seems 1.5 still is not out yet...

ruslo closed this 10 days ago

I've removed branch develop (now we can just use master) and it was closed automatically. Reopenning.

hmm seems 1.5 still is not out yet...

We can always return to the fork if you want.

https://github.com/google/flatbuffers/releases/tag/v1.6.0

Closing inactive pull request.


Circle code shape can not be recognized

Change codeShape property from default to QrShape.circle(), will cause qr code can not be recognized.

Try decrease logo size and set errorCorrectionLevel to High

From 1.5.51 error correction level of vector codes is set to Auto by default and works better with custom code shapes.


c3 stickers

two versions, one with just logo, one with QR code that goes to the GitHub (or to cogent3.org ?)
@fredjaya to sort stickers
@KatherineCaley to provide links to the svg files

png and svg file for full logo are here

c3-qr-code.zip

Quotes sent to radstickers

QR 40x40mm
150 - $145+gst
250 - $220+gst
Logo 100x40mm
250 - $220+gst
500 - $400+gst
For die cut, a 5mm border is required (which is thicker than usual)
Postage
$20+gst

@Vini2 how does this compare to the stickers you got made?

@KatherineCaley I had 50 50x50mm printed for $69.99 (including GST and postage), but if was not the thick vinyl stickers I was expecting. They started fading after a few months.

@Vini2 thank you!! good to get a comparison 😇

This Brisbane service [ https://shop.eprintonline.com.au/vinyl-sticker-printing-australia/ ] will do 100 vinyl low tack stickers for $44 in 5 days.
Low tack is good if you are sticking them on the backs of laptop displays as they won't leave a residue when you remove them.

Stickers ordered!


Suggestion: Allow for linking to security.txt (or other external resources) specifying a checksum

For sites which already maintain a security.txt file (see A File Format to Aid in Security Vulnerability Disclosure) which also allows specifying preferred languages and encryption keys, it might not make sense to maintain DNS TXT records unless they simply link to https://example.org/.well-known/security.txt.
As pointed out, the obvious challenge [on the other hand] is that it inserts the owner of the web host between the user and the contact channel and policy details. This is true for all external references by means of a URL, of course.
DNS entries can be secured with cryptographic signatures (see DNS Security Introduction and Requirements), but a simple URL specified above—regardless of what it refers to—only specifies the location, but does not provide a means to validate the contents without the aid of additional roots of trust. While the latter should be used if available, an additional checksum provided as part of the DNS entries could at least be used as "last resort" (or rather, to utilize DNSSEC to its full extent w.r.t. this use case).

Hey! Thanks, That's an interesting idea, I think this will be something that can be cited in the _security. record set, while the main principle is to provide a point of contact, we've had conversations about the freedom of _security. personally, I like the minimal approach of having a point of contact, a privacy method if desired (PGP etc...) , and a link to the security page, but there is no reason why someone couldn't add their security.txt file(s) if they wanted to maintain managing them on a host by host / site by site orchestration, it may be easier to stick to DNS as an authoritative route to security contacts but, _security. is a good place to demonstrate what you want people to know, it might be nice to see how people format those and hope that it follows suite with the general schema

OK Closing this, but to reiterate...
the principle here is to provide means for contact, in the APEX TXT record, and an optional _security. space for similar and relative security information, there is list in the APEX, it just delivers in it's simplest terms: security contact information.
but with the _security. record there is freedom to define what you want, if you wanted to inherit some of security.txt's very granular options, have at it, I think we (@yesnet0 citation needed) would prefer that entries follow a machine parsable and human readable schema such as:
purpose_title= information1; information2;more if needed;etc; (max 255 chars)
We want people to use DNSSEC and where possible we will nudge people to using it, it's not for us to enforce, I agree, it's certainly better than not having it. what we dont want to do is set a huge architectural requirement for some contact information, if they dont have it, i'm sure they hear about it in every security report, and hopefully that will chip away to the point where action is taken, but it's out of our hands, if they do have it, great, get signing!  maybe we'll put some examples up too for good measure.
With reguards to content validation we agree, but think about what we are offering here, it's first and formost, contact information to allow access to the security department, by email and an optional link to a URL, the argument for content valudation is fair, and more reason why not to use security.txt if you care that much as that too is content. but if we focus on fighting the mean and not the edge, providing a URL to a security page moves into the risk acceptance criteria of - if someone is in a position to modify the DNS record or secuirty page , why dont they just (xyz).
sure we could wax lyrical about how to monitor for DNS changes, or how to use DNSSEC but those are out of scope, we will assume that you're doing things the way you want to do things less good or more good. it's a fight worth having but not from us.
We are in early days with this project, but it's good to know that the potential challenge being presented are not show stoppers and that the simplicity of the idea wont get burried in technicalities or nuanced situations. we would hope that everyone operates their DNS admin to a highly competent security focused manner but often that isnt the case, and as a least case, having contact information available is our job done, if someone wants to validate that poor DNS quality may effect the records integrity, i'd agree with them and equally defer them to the organisation as the records themselves are not the posture or configuration, we can only desire best practices often there are various reasons why that cannot be the case, either way, I think we agree good security practice is good security practice, but we simply offer an idea with a proposed way to organise the idea to make it more useful. - Thanks again !


SUBMARINE-326. Hook submarine REST server and JobManager to accept K8s Tensorflow Job

What is this PR for?
Implements submit the TF job to K8s cluster by REST
What type of PR is it?
Feature
Todos
Implements the job RUD operates when 0.4.0 released
What is the Jira issue?
https://issues.apache.org/jira/browse/SUBMARINE-326
How should this be tested?
unit test
Screenshots (if appropriate)
Questions:

Does the licenses files need update? No
Is there breaking changes for older versions? No
Does this needs documentation? No

@jiwq The PR title is too long. Can you shorten it?

@jiwq The PR title is too long. Can you shorten it?

Done. Thanks @liuxunorg for review.
I found one discussion thread named 'Git Commit Messages : 50/72 Formatting'. Maybe we can follow this.

Thanks @jiwq for the contributions and @liuxunorg @tangzhankun for the reviews.