New package: DigilentWaveForms v0.1.0

Registering package: DigilentWaveForms
Repository: https://github.com/ianshmean/DigilentWaveForms.jl
Created by: @ianshmean
Version: v0.1.0
Commit: 0c3c0d82d0d71a4b439ba67e88fec48bf249445b
Reviewed by: @ianshmean
Reference: https://github.com/ianshmean/DigilentWaveForms.jl/issues/1#issuecomment-544556132

Your new package pull request does not meet all of the guidelines for automatic merging.
Specifically, your pull request does not meet the following guidelines:

The following dependencies do not have a compat entry that has an upper bound: CEnum

It is important to note that if your pull request does not meet the guidelines for automatic merging, this does not mean that your pull request will never be merged. It just means that your pull request will require manual review by a human.

These guidelines are intended not as requirements for packages but as very conservative guidelines, which, if your new package or new version of a package meets them, it may be automatically merged.

On a separate note, I see that you are registering a release with a version number of the form v0.X.Y.
Does your package have a stable public API? If so, then it's time for you to register version v1.0.0 of your package. (This is not a requirement. It's just a recommendation.)
If your package does not yet have a stable public API, then of course you are not yet ready to release version v1.0.0.

[noblock]

Your new package pull request does not meet all of the guidelines for automatic merging.
Specifically, your pull request does not meet the following guidelines:

I was not able to install and import the package. See the Travis logs for details.

It is important to note that if your pull request does not meet the guidelines for automatic merging, this does not mean that your pull request will never be merged. It just means that your pull request will require manual review by a human.

These guidelines are intended not as requirements for packages but as very conservative guidelines, which, if your new package or new version of a package meets them, it may be automatically merged.

On a separate note, I see that you are registering a release with a version number of the form v0.X.Y.
Does your package have a stable public API? If so, then it's time for you to register version v1.0.0 of your package. (This is not a requirement. It's just a recommendation.)
If your package does not yet have a stable public API, then of course you are not yet ready to release version v1.0.0.

[noblock]

This package has the prerequisite of having the user install the (commercial) Digilent WaveForms SDK, and thus build fails on Travis (tests are guarded against CI too).
Can it be manually approved?

I just released a newer version, assuming it would queue up behind this one as a minor release but it's created a new PR as a new package https://github.com/JuliaRegistries/General/pull/4686


Math magicians: components

I did the following on Math magicians: components

Delete all the boilerplate from CRA (text, images, styles).
Create a directory called components.
Inside components, create a new Calculator.js file.
In Calculator.js, create a React component that matches the design provided.
Develop just the UI of the calculator; the math logic to make it work will be added in the next project.
Use class based components (All components should be class-based).
Once the Calculator is ready, import it and use it in your main component (App.js).
Test it in the browser; it should render without problems.

@Mihndim2020

Requested I remove Unused files from public Directory.

@omarsalem7

Checked changes made and approved.


google-authenticator two factor not working on xrdp login

google-authenticator two factor not working on xrdp login . Same google authenticator is working fine while I am trying to login using ssh .
For installing google-authenticator I am just following https://www.digitalocean.com/community/tutorials/how-to-set-up-multi-factor-authentication-for-ssh-on-ubuntu-16-04
step 1 , step 2 and step 3.
Is there any special configuration required for google-authenticator to made it working over xrdp session ?

We know that. That's why I do a survey #1047.  See also #736.

I am able to use google-authenticator with xrdp with some changes. It is working fine for password+token(from mobile app ) on xrdp session. Only thing is missing two different screens for providing password and OPT. For command mode it always asking for password on one screen and then OTP on second screen but same is not working on xrdp login screen. On xrdp login screen user has to provide password and OTP together without any scape or extra character and login will work fine. If we can have two separate screen working with xrdp it will really work as 2FA .
Here is the issue and configuration for xrdp to work with google-authenticator : https://github.com/google/google-authenticator-libpam/issues/110

Good work!

Please provide me step by step configuration for XRDP with Google authenticator

@Sas002 could you create an MD with instruction on how to set this up end-to-end? That would be great to include in the readmes on xRDP github 👍

Now I am working how to have HA for XRDP.

@Sas002 could you create an MD with instruction on how to set this up end-to-end? That would be great to include in the readmes on xRDP github 👍. Else I might give this is a go when I have some spare to time.

I will add it this week.

Please provide me step by step configuration for XRDP with Google authenticator

sorry for the delay. I will add the steps this week and update you.

Apologies for the vastly late response - I was stuck in between flying and deadlines. I have some time in the coming week to give this a shot for our linux VMs

Can someone confirm this is working? I've made a few attempts but seem to be getting no-where with the steps provided. I am working on a Centos 8 VM. SSHD is setup just fine to work with the google authenticator, but XRDP is not accepting the password+authenticator code with the /etc/pam.d/xrdp-sesman config described by @Sas002

Hi @Bruuldor
I'll have a look at this for you - this could really do with getting on the Wiki I think. Gimme a while to get a CentOS 8 VM set up and I'll see what I can do.
Couple of questions for you:-

Are you using GNOME or another desktop?
What does your /etc/pam.d/xrdp-sesman look like?
Depending on the section which is uncommented in /etc/pam.d/xrdp-sesman, can you post either /etc/pam.d/password-auth or /etc/pam.d/gdm-password?

Thanks

Hi @matt335672
I've gotten it to work after messing around with the xrdp-sesman file and also some SELinux restrictions that didn't allow google authenticator to update the file in the home directory of the user. See my config below:
Desktop: GNOME
`
/etc/pam.d/xrdp-sesman
#%PAM-1.0
#Generic Fedora config
#auth       include      password-auth
account    include	password-auth
#password   include      password-auth
session    include	password-auth
#auth required pam_google_authenticator.so secret=${HOME}/.ga/.google_authentic$
#auth required pam_google_authenticator.so forward_pass
auth required pam_google_authenticator.so secret=${HOME}/.ga/.google_authentica$
auth required pam_unix.so use_first_pass
#Gnome specific Fedora config
#auth       include      gdm-password
#account    include      gdm-password
#password   include      gdm-password
#session    include      gdm-password
/etc/pam.d/sshd
#pam_selinux.so open should only be followed by sessions to be executed in the user context
session    required     pam_selinux.so open env_params
session    required     pam_namespace.so
session    optional     pam_keyinit.so force revoke
session    optional     pam_motd.so
session    include	password-auth
session    include	postlogin
#add to end
auth required pam_google_authenticator.so secret=${HOME}/.ga/.google_authenticator
`
The GA code needs to be appended to the end of the password but it works!

Hi @Bruuldor
I've set the thing up just using a local user and I'm not seeing any problems with SELinux using the standard ~/.google-authenticator location for the file.
How did you install xrdp? Did you install it from EPEL, or from source? If you used EPEL, did you also install the xrdp-selinux RPM?
Thanks for any info.

I'm closing this issue now - I've added a Wiki page describing how to set this up with an example


Fast TaskRunScheduler

Task.Factory.StartNew is slow compared to QueueUserWorkItem or the newer QueueUserWorkItem(preferLocal: true) https://github.com/dotnet/corefx/issues/12442
Since the returned Task is just ignored; might as well use the faster versions (which Task.Factory.StartNew essentially ends up calling - more or less...)
/cc @davidfowl @pakrym

Can be improved post https://github.com/dotnet/corefxlab/pull/2001

Rebased on https://github.com/dotnet/corefxlab/pull/2001


backupccl: add IF NOT EXISTS as optional clause to CREATE SCHEDULE

https://github.com/cockroachdb/cockroach/pull/69152 --- Release Note (sql change): Added the optional IF NOT EXISTS clause to the CREATE SCHEDULE statement, making the statment idempotent.  Release justification: low risk, high benefit changes to existing functionality  Release note (<category, see below>):

Closing this in favor of #11461


Active user beacon

This implements the active user beacon (RFC 81), also in issue #324.
This needs to have a proper link to the blog before this should be merged?
This differs slightly from the RFC: all checks are performed on the main thread (steps 1 and 2 in the RFC) and only then does it create a thread to send the request (step 3).

This includes 2 new APIs in org.quiltmc.loader.api.QuiltLoader: getGlobalCacheDir and getGlobalConfigDir, which reference different places depending on the platform:

%LOCALAPPDATA%\QuiltMC\QuiltLoaderAndMods on windows
~/Library/Application Support/org.quiltmc.QuiltLoaderAndMods on mac os
$XDG_CONFIG_HOME/quilt_loader_and_mods on linux.

The exact paths are slightly more complex though, please see https://github.com/QuiltMC/quilt-loader/pull/326/files#diff-fad88a499d350f39f142ae7f01bb55a088e2d5112b9a645461bab17e4f7a099b for the actual implementation.

Moving back to draft until I actually test this on MacOS and windows.

This works fine on Mac OS.

And this works on windows! So this is nearly good to go, except for a blog post link. (Which can technically be added later, when the blog is posted.)

And this works on windows! So this is nearly good to go, except for a blog post link. (Which can technically be added later, when the blog is posted.)

@AlexIIL blog post is waiting on your review!

Sorry for the delay - I've left an approving review.


graphite-web not displaying anything when i use soft-link in carbon whisper files

I have installed graphite-web-0.9.15-1.el7rhgs.noarch, then i initialized graphite.db after that i updated to graphite-web-1.1.4-1, all migration commands are executed successfully.
But I am facing an issue like when I create an alias (soft link using some name) for whisper files then nothing is displayed in graphite-web.
All my data is stored in  /var/lib/carbon/whisper/{app_name}/{hostname}/cpu/abc.wsp
i created soft-link like
/var/lib/carbon/whisper/{app_name}/some_alias_name ->/var/lib/carbon/whisper/{app_name}/{hostname}
when I open graphite under alias name it should show hostname but I can see everything in terminal but not in graphite-web. Permission also 777 only.

I saw this issue lot of times, why I can't use the soft link there if I install web-1.1.4-1 in the fresh machine then I create soft-link then it works fine. but why it is not working in above case

This has been fixed in https://github.com/graphite-project/graphite-web/issues/2320

i am seeing this issue in  graphite-web-1.1.4-1

i can see fixed code in my setup but still i am faceing this issue, i removed all packages
yum remove graphite-web pythoon-carbon python-whisper python-django
and then installed again but still i am seeing this issue.

@GowthamShanmugam :
could you please elaborate which Graphite version do you use and how you trying to install it?
Thanks!

version which i am using is:
python2-django-1.11.15-1
graphite-web-1.1.4-1
python-carbon-1.1.4-1
python-whisper-1.1.4-1

First i installed
graphite-web-0.9.15
python-carbon-0.9.15-2
python-whisper-0.9.15
after that i ran graphite command to intialize:
/usr/lib/python2.7/site-packages/graphite/manage.py syncdb --noinput
After intialized i just updated with new graphite-web package which i pasted in above command and then i intialized new version of graphite using a command:
PYTHONPATH=$GRAPHITE_ROOT/webapp/ django-admin migrate --settings=graphite.settings --run-syncdb
It executed successfully, then i start carbon-cache service:
service carbon-cache start
Then i created softlink inside /var/lib/carbon/whisper/{app_name}/{soft_link}
(e.g)
[root@tendrl-server graphite_dependency-]# ll /var/lib/carbon/whisper/tendrl/names/e43fcdf8-45b9-4146-909b-fb26b9078e26
lrwxrwxrwx. 1 root root 77 Dec  7 12:49 /var/lib/carbon/whisper/tendrl/names/e43fcdf8-45b9-4146-909b-fb26b9078e26 -> /var/lib/carbon/whisper/tendrl/clusters/e43fcdf8-45b9-4146-909b-fb26b9078e26
the softlink is not displayed in graphite-web, but i can see all directory using softlink in terminal.

If i install new version of graphite-web in a fresh machine  then it works fine, i am faceing issue when i try to update to new version from old version.

I am constantly reproducing this issue

Then you not really upgrading Graphite on old server and still using 0.9.15. Please note that you can't install graphite with RPMs and then upgrade it with installation from source - probably RPMs using different paths (probably /usr/something), source installation using /opt/graphite.
You can fing Graphite version if check /version url. If it's giving 404 - it's less then 1.0.0

version which i am using is:
python2-django-1.11.15-1
graphite-web-1.1.4-1
python-carbon-1.1.4-1
python-whisper-1.1.4-1

Where did you get those package from? Did you rebuilt my Fedora specfile or are you using some internal Red Had packages?

for RHEL we built it manually, during graphite-web build we figured out dependencies one by one and we build all, then issue which I am facing is once I removed graphite package and reinstalled higher version or same version then a soft link is not working.
I am working in redhat as SE, for our product we are using graphite as time series DB in RHEL

One thing is not clear, i removed all graphite related packages and then reinstalled same version then soft-link is not working.


Update uninstall script to remove mount point path after umount

Proposed Changes

This addresses #2435 by adding an rm call to the uninstall script after the given resource is unmounted.
Types of Changes

Verification

The directories listed below shouldn't exist.
ls '/run/k3s'
ls '/var/lib/rancher/k3s'
ls '/var/lib/kubelet/pods'
ls '/run/netns/cni-*'

Linked Issues

#2435
Further Comments

I think we will also need to ip netns delete each of the namespaces - as far as I can tell just umounting and removing things from the filesystem will not fix the linked issue.

I think we will also need to ip netns delete each of the CNI network namespaces - as far as I can tell just umounting and removing things from the filesystem will not fix the linked issue.

Yeah, I marked this as a WIP. I'll remove that when it's ready for review and add reviewers.

Sorry, didn't notice that in the title. We should probably decide if we are going to use WIP titles and/or the draft PR status. I know I'm not particularly consistent about it at the moment.

I don't know how it was asserted anywhere that it was better... Just an approach.
This was rendered correctly from the install script usage in my test environment.

Please outline with detail your preferred means of implementation for this and I'll update it to those lspecs.

It appears to work because we don't set -u, but $SUDO is an undefined variable in this script.
Also, we just unmounted and deleted all these directories, so this will always result in an error: ls: cannot access cni-*: No such file or directory. I had made a suggestion up above of:
ip netns show 2>/dev/null | grep cni- | xargs -r -t -n 1 ip netns delete

Right but $SUIDO isn't written to the script.
I'll make the other changes

It is though:
[root@centos01 ~]# curl -sfL https://raw.githubusercontent.com/briandowns/k3s/1453068f33e163d868c17c36d8a0f2c2fa6e1ee0/install.sh | INSTALL_K3S_SKIP_START=true INSTALL_K3S_EXEC=server bash -
[INFO]  Finding release for channel stable
[INFO]  Using v1.19.3+k3s3 as release
[INFO]  Downloading hash https://github.com/rancher/k3s/releases/download/v1.19.3+k3s3/sha256sum-amd64.txt
[INFO]  Skipping binary downloaded, installed k3s matches hash
Failed to set locale, defaulting to C
Loaded plugins: fastestmirror
Loading mirror speeds from cached hostfile
 * base: mirrors.cat.pdx.edu
 * elrepo: muug.ca
 * epel: mirror.siena.edu
 * extras: mirror.centos.lax1.serverforge.org
 * updates: mirrors.radwebhosting.com
Package yum-utils-1.1.31-54.el7_8.noarch already installed and latest version
Nothing to do
Failed to set locale, defaulting to C
Loaded plugins: fastestmirror
Failed to set locale, defaulting to C
Loaded plugins: fastestmirror
Repository rancher-k3s-common-stable is listed more than once in the configuration
Loading mirror speeds from cached hostfile
 * base: mirrors.cat.pdx.edu
 * elrepo: muug.ca
 * epel: mirror.siena.edu
 * extras: mirror.centos.lax1.serverforge.org
 * updates: mirrors.radwebhosting.com
rancher-k3s-common-stable                                                                                | 2.9 kB  00:00:00
Package k3s-selinux-0.2-1.el7_8.noarch already installed and latest version
Nothing to do
[INFO]  Skipping /usr/local/bin/kubectl symlink to k3s, already exists
[INFO]  Skipping /usr/local/bin/crictl symlink to k3s, already exists
[INFO]  Skipping /usr/local/bin/ctr symlink to k3s, command exists in PATH at /bin/ctr
[INFO]  Creating killall script /usr/local/bin/k3s-killall.sh
[INFO]  Creating uninstall script /usr/local/bin/k3s-uninstall.sh
[INFO]  env: Creating environment file /etc/systemd/system/k3s.service.env
[INFO]  systemd: Creating service file /etc/systemd/system/k3s.service
[INFO]  systemd: Enabling k3s unit
Created symlink from /etc/systemd/system/multi-user.target.wants/k3s.service to /etc/systemd/system/k3s.service.

[root@centos01 ~]# grep SUDO /usr/local/bin/k3s-killall.sh
    $SUDO ip netns del ${ns}
[root@centos01 ~]#

huh, my computer must have a works for me convenience class of bugs

Nice!


Avoid cloning results assembled from partial results

When a GraphQL query contains different block constraints, we run and cache the toplevel fields grouped by the block constraint separately, and assemble the response from those partials. We now see a lot of large GraphQL queries with different block constraints - on average we run 3-4 toplevel queries for each GraphQL request.
Assembling the response used to involve cloning all the partial responses. This PR changes that so that we will not clone at all, and rather pass the partial results around behind in an Arc; assembling the entire response is only done when we serialize the response to JSON (that's another clone-heavy part of request processing, but is not addressed by this PR)

I've addressed all the comments, but haven't rebased yet to avoid making the review harder.

@lutter Did you forget to push the changes?

Yes, I did. Pushed them now


Page Titles feature Dangling Hyphen

They're coming out as "Stan -" and "Documentation -" on Safari.

I'm confused.  Are we no longer using the old repo?  I filed exactly the same issue there:
https://github.com/stan-dev/webpages/issues/12

Can we merge so we just have one of these?

stan-dev/webpages is the old site, it has not been modified.
The new site lives in stan-dev/stan-dev.github.io — I moved
the issue to the new site, merged, and closed.
On Jul 30, 2015, at 9:35 PM, Bob Carpenter<EMAIL_ADDRESS>wrote:

I'm confused. Are we no longer using the old repo? I filed exactly the same issue there:
stan-dev/webpages#12
—
Reply to this email directly or view it on GitHub.

I think the titles should say "Stan: " or "Stan-" so it's clear
from browser tabs where you're at.

Bob

On Jul 30, 2015, at 5:12 PM, Michael Betancourt<EMAIL_ADDRESS>wrote:
stan-dev/webpages is the old site, it has not been modified.
The new site lives in stan-dev/stan-dev.github.io — I moved
the issue to the new site, merged, and closed.
On Jul 30, 2015, at 9:35 PM, Bob Carpenter<EMAIL_ADDRESS>wrote:

I'm confused. Are we no longer using the old repo? I filed exactly the same issue there:
stan-dev/webpages#12
—
Reply to this email directly or view it on GitHub.

—
Reply to this email directly or view it on GitHub.


Update attribute editor when clearing crop window #1258

Pretty much perfect, thanks!
I only have two minor suggestions regarding naming:

I would suggest signal_crop_window_cleared for the signal emitted by MainWindow because, as far as MainWindow is concerned, all it knows is that the crop window was cleared; it doesn't necessarily know that in consequence to that signal, a widget will be cleared...

I would suggest slot_clear_crop_window_widget for the slot, because that's the terminology we used: the user interface is made of widgets...

These are really details. The code is simple, clear and expressive. Excellent work!

Note that you can simply push a new commit, it will automatically get added to this PR.

@dictoon, thank you for the review,
Signal and slot are named now as requested.

Perfect, merging! Thank you


Add info about finding the runtime endpoint

Fixes #30974
Add a section to "Find out what container runtime is used on a node" to find the runtime endpoint, with a clarification that Docker users who use cri-dockerd already wouldn't be affected by the dockershim removal.
/sig docs
/language en
/cc @sftim @afbjorklund

@sftim I changed the commands to look for the kubelet process cmdline and analyse the --container-runtime-endpoint flag (or lack of it) to see what the runtime and socket are.

@kubernetes/sig-node-pr-reviews does this look technically correct?

@kubernetes/sig-node-pr-reviews this would be great to get an LGTM on asap :)

Should we mention the kubectl-detector-for-docker-socket tool here? https://github.com/aws-containers/kubectl-detector-for-docker-socket

It's third party software. On the other hand it's tool to accomplish this specific task. I'd suggest that we mention the tool, but link to it rather than document how to use it (which is what https://kubernetes.io/docs/contribute/style/content-guide/#what-s-allowed cares about).

this looks fine for sig-node.
/lgtm

/lgtm
thanks @shannonxtreme!


No default sort order in Grading tab table

It would be helpful if these were sorted by Submission ID, i.e. chronologically. Also a wishlist feature: remember the last sort order we used.

Sure. I'm actually thinking of a more intuitive sorting order (with some feedback from colleagues). Will update here.

Fixed by #321


Upgrade NodeJS

We'd like to start linting our Javascript using standard, see:
https://standardjs.com/
https://github.com/alphagov/govuk-lint/issues/63
https://github.com/alphagov/govuk_frontend_toolkit/pull/334
To run standard linting on our VMs and on Jenkins we need a modern version of NodeJS (> 4). We currently run version 0.10, which hasn't been updated since 2015: https://github.com/alphagov/govuk-puppet/blob/a6c51d887a6501f02766b7279127b60f02037a7f/hieradata/common.yaml#L1150
https://github.com/alphagov/govuk-puppet/commit/009e0b1f06b0c6495cb1420b42701533bce149aa
The PR that updated Node mentioned StatsD and Performance Platform as dependencies. Is that still the case?
cc @boffbowsh

This might be the time to include something like nvm too. https://github.com/creationix/nvm


Adding contributing guidelines to the repo

:white_check_mark: Checklist

[x] This pull request has a meaningful title.
[x] If your changes are not yet ready to merge, you have marked this pull request as a draft pull request.

:ballot_box_with_check: Maintainers' checklist

[ ] This pull request has had the appropriate labels assigned
[ ] This pull request has been added to the SATRE backlog project board
[ ] This pull request has been assigned to one or more maintainers

:arrow_heading_up: Summary
Adding the contributing guidelines to CONTRIBUTING.md on the repository, so people can find it immediately when they come. It also links out the the readthedocs version
:raising_hand: Acknowledging contributors

[x] All contributors to this pull request are already named in the table of contributors in the README file.

We could also just have a single link pointing to the readthedocs ones, but I think it's better to have them directly accessible here too for people familiar with reading CONTRIBUTING docs this way

Hey @harisood - I've created an earlier PR #44 that at @JimMadge suggestion uses a symlink. We can probably remove this PR?

Cardinal sin from me @arronlacey, 3 open PRs and I didn't read through them 😬 will close now


Redesign

Coverage decreased (-6.1%) to 84.513% when pulling ae3164fbf5c40e17227a792902906d31e819ed69 on refactoring-messenger into e7d3b1a53a917837e901015fbbdf6e6d0277ccff on master.


Typo in error code - HC00038 should be HC0038?

Product
Hot Chocolate
Version
main
Link to minimal reproduction
See below
Steps to reproduce
Just came across this:
https://github.com/ChilliCream/graphql-platform/blob/cdbc3e1148d104c3cf78726619423822e5160545/src/HotChocolate/Core/src/Abstractions/ErrorCodes.cs#L138
Based on the surrounding codes, I am guessing there's a 0 too many there.
What is expected?
See above
What is actually happening?
See above
Relevant log output
No response
Additional context
No response

Thanks @cmeeren – I've opened a PR.


v-if for item.text

Is your feature request related to a problem? Please describe.
i need margin between title and text, so i add style
but when i use only title, i have empty div for text with margin
Describe the solution you'd like
v-if will fix it
Additional context

Hello @horshechnyk
so you can probably achieve what you need with slot-scope(vue slot-scope docs).
Just add slot-scope="slotProps" in your slot line, and you shall have the access to parent data in slotProps.item.
<notifications width="600" group="notificationWithButtonGroup" position="bottom right">
    <template slot="body" slot-scope="slotProps">

{{ slotProps.item.title }}

    </template>
</notifications>


[Event Request] Codeunit 1254 "Match Bank Pmt. Appl." OnBeforeMatchNoOverwriteIfManualOrAccepted

Describe the request
Please can you add a new event OnBeforeMatchNoOverwriteOfManualOrAccepted to the procedure MatchNoOverwriteOfManualOrAccepted in Codeunit 1254 "Match Bank Pmt. Appl."
    procedure MatchNoOverwriteOfManualOrAccepted(BankAccReconciliation: Record "Bank Acc. Reconciliation")
    var
        MatchBankPayments: Codeunit "Match Bank Payments";
        IsHandled: Boolean;  //NEW CODE
    begin

        //NEW CODE -
        IsHandled := false;
        OnBeforeMatchNoOverwriteOfManualOrAccepted(BankAccReconciliation, IsHandled);
        if IsHandled then
            exit;
        //NEW CODE +

        BankAccReconciliationLine.FilterBankRecLines(BankAccReconciliation);

With the corresponding Event
    [IntegrationEvent(false, false)]
    local procedure OnBeforeMatchNoOverwriteOfManualOrAccepted(var BankAccReconciliation: Record "Bank Acc. Reconciliation"; var IsHandled: Boolean)
    begin
    end;

Additional context
This is similar to the OnBeforeRun event and is required to have the option to run custom bank payment matching code.
Internal work item: AB#498223

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. 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.
Build ID: 15815.


fix: Disable Change Tracking for Zipkin TraceID Header

Adds a check on config.http_response_header_for_traceid for the zipkin plugin. Change tracking is conditionally ignored when this field is set to the default value (nil).

Please add a test for this to ensure that track changes is not emitted when the default is set.


187: Build android in CI/CD

Short description

Build android in CI/CD and persist artifacts.
Proposed changes

Add build_android and bump_version CI jobs
Add fastlane for android
Add various scripts to manage CI and releases

Side effects

App signing is not configured yet

Testing

Check the pipeline.
Resolved issues

Partly fixes: #187

I mostly copied this from our digitalfabrik repos. Let me know if I should explain something or you think something does not make sense.


2RW RAM Vivado Benchmark

(Separating the benchmarks into separate issues for readability)
This issue presents various Vivado benchmarks for the file bsg_mem_2rw_sync_mask_write_byte.sv from BaseJump STL.
Each compressed zip file attached to a benchmark contains three things:

The original source file that was compiled by Vivado
The compiled Vivado code
The output log generated by Vivado

Results

Primitive
Used
Functional Category

LUT6
541696
LUT

FDRE
266112
Flop & Latch

MUXF7
104448
MuxFx

MUXF8
50176
MuxFx

LUT2
6152
LUT

LUT4
3840
LUT

LUT3
272
LUT

Compressed Zip File:
Uploading 2rw_ram_benchmark_els512.zip…

Number of elements is set to 256 (els_p=256).
Results:

Primitive
Used
Functional Category

LUT6
222528
LUT

FDRE
134016
Flop & Latch

LUT5
118144
LUT

MUXF7
52224
MuxFx

LUT3
36816
LUT

MUXF8
26112
MuxFx

LUT4
15808
LUT

LUT2
2112
LUT

Compressed Zip File:


Workaround: Prevent threads sitting in epoll forever

Fixes #1662 (I anticipate at least)

@jtattermusch - please patch this in and hammer on it, and respond here if it solves your problem (for now).

This is an alternative fix for #1731.

I tried several hundred iterations and haven't seen C# server hanging with this patch.

Merge it :)


LazyRow on ComposePanel is not scrollable

Helllo, I'm working on a UI for a player using Jetpack Compose for Desktop. My goal is to overlay Composables on top of a video player view, but I'm facing some issues.
Here is the core part of my code:
SwingPanel(
    modifier = Modifier.fillMaxSize(),
    factory = {
        ComposePanel().apply {
            setContent {
                Box (
                    modifier = Modifier.fillMaxSize()
                ) {
                    SwingPanel(
                        modifier = Modifier.fillMaxSize(),
                        factory = {
                            videoPlayerViewModel.player.getPlayerView()
                        }
                    )
                    Box (
                        modifier = Modifier.fillMaxWidth().height(200.dp),
                        contentAlignment = Alignment.BottomStart

                    ) {
                        SwingPanel(
                            modifier = Modifier,
                            factory = {

                                ComposePanel().apply {
                                    setContent {
                                        RandomLazyRow()
                                    }
                                }
                            }
                        )
                    }
                }
            }
        }
    }
)

Here are the problems I am facing with this setup:
Transparency problem: The ComposePanel doesn't seem to respect transparency settings on both Windows and Mac platforms. This prevents me from creating the desired UI effects. Related issues have been discussed in https://github.com/JetBrains/compose-multiplatform/issues/1061, https://github.com/JetBrains/compose-multiplatform/issues/2461 ,
Scrolling issue: I can't scroll through items in a LazyRow using the mouse. The scrolling works programmatically but does not respond to mouse scroll events.
ps: The reason I am using ComposePanel is due to limitations with SwingPanel, which does not properly handle overlaying Composables on top of it #2926, #1521,

Please check the following ticket on YouTrack for follow-ups to this issue. GitHub issues will be closed in the coming weeks.


Anydesk not Working if systemd is Enabled

Version
Microsoft Windows [Version 10.0.22621.963]
WSL Version

[X] WSL 2
[ ] WSL 1

Kernel Version
<IP_ADDRESS>-microsoft-standard-WSL2
Distro Version
Ubuntu 20.04
Other Software
Anydesk, version 6.2.1
Repro Steps

Install Anydesk
Edit wsl.confg and set systemd=true
Execute "anydesk" on the terminal

Expected Behavior

Actual Behavior

Diagnostic Logs
No response

I just discovered that running the following commands work:

sudo anydesk --get-id
sudo anydesk --version
sudo anydesk --get-alias
sudo anydesk --get-status
sudo anydesk --admin settings

However, trying to run "sudo anydesk" displays this error

Hmm, doesn't Anydesk also require a working X desktop to have something to connect to?


Bump animation above advanced

Yes, this is for next release, so we don't forget. We will have to update docs closer to the release than now.
I intend to merge and test in /beta and see first before changing the docs


add --project_id argument for create task

Motivation and context
The new project feature is helpful, but it is not yet compatible with the CLI create task script. This PR adds the --project_id option for the create task and sets the labels to an empty list, which defaults to the project's labels.
The main changes are:

add project_id paramater to the task_create_parser that defaults to None
add project_id param to tasks_create in core.py
sets labels to [] if using a project id, which defaults to the project's existing labels
project_id follows formatting of lowercase_param_name used in other (eg resource_type)

Main goal is to be able to batch import via CLI into existing projects with existing label sets.
How has this been tested?
Minimally tested using the following command:
docker exec -it cvat bash -ic \
  "python3 utils/cli/cli.py \
  --auth ${CVAT_USERNAME}:${CVAT_PASSWORD} \
  create --project_id 1 MyTaskName local /path/to/file.jpg"

Checklist

[x] I submit my changes into the develop branch
[ ] I have added description of my changes into CHANGELOG file
[ ] I have updated the documentation accordingly
[ ] I have added tests to cover my changes
[ ] I have linked related issues (read github docs)
[ ] I have increased versions of npm packages if it is necessary (cvat-canvas,
cvat-core, cvat-data and cvat-ui)

License

[x] I submit my code changes under the same MIT License that covers the project.
Feel free to contact the maintainers if that's a concern.
[ ] I have updated the license header for each file (see an example below)

This overrides previous PR https://github.com/openvinotoolkit/cvat/pull/2877

Coverage decreased (-0.002%) to 74.053% when pulling b3ba137f876eace9dfa54c997a6892cbf06412d0 on vframeio:develop into 6988e2b98f9cfc7e0f98142a7c2829640d4fffcf on openvinotoolkit:develop.


fix(core): use TextDecoderStream for stream response

Closes #1492
Description
This PR changes the implementation of streamResponse function to use TextDecoderStream rather than to use TextDecoder for each chunk from streaming response.
The current implementation sometimes break the response non-ASCII characters and this PR will fix it. see #1492 for more detail.
Checklist

[x] The base branch of this PR is preview, rather than main

Note:
const stream = (ReadableStream as any).from(response.body);

yield* stream.pipeThrough(new TextDecoderStream("utf-8"));

response is not an instance of globalThis.Response and response.body is not ReadableStream. So we need to convert response.body into ReadableStream to use TextDecoderStream.
TypeScript doesn't recognize that ReadableStream has from static method so as any is required.

Thanks for the contribution! This is quite important : )

I believe this causes the following error:
ReadableStream.from is not a function

I believe this causes the following error:
ReadableStream.from is not a function

I found that ReadableStream.from() seems to be only supported in the latest VSCode.
MDN says ReadableStream.from() is supported Node.js v20.6.0+ and the VSCode built-in Node.js version seems to be like the bellow.

VSCode version
Electron version
Node.js version

May 2024 (version 1.90)
29
20.9.0

April 2024 (version 1.89)
28
18.18.2 (ReadableStream.from() is NOT available)

March 2024 (version 1.88)
28
18.18.2 (ReadableStream.from() is NOT available)

The bellow code can be a remedy of the error if you want to support older VSCode versions.
// This triple slash directive doesn't seem to be recognized by TypeScript on compile time so we can't use this instead of `as any`.
// /// <reference lib="DOM.AsyncIterable" />

export async function* streamResponse(
  response: Response,
): AsyncGenerator<string, void, undefined> {
  if (response.status !== 200) {
    throw new Error(await response.text());
  }

  if (!response.body) {
    throw new Error("No response body returned.");
  }

  // Use ReadableSteam constructor instead of Readable.from() function
  const body = response.body;
  const stream = new ReadableStream<Uint8Array>({
    async start(controller) {
      for await (const chunk of body as any) {
        controller.enqueue(chunk);
      }
      controller.close();
    },
  }) as any;

  yield* stream.pipeThrough(new TextDecoderStream("utf-8"));
}


Make @cncf-ci bot comment with link to PR preview upon successful build.

/assign @devaii
I'd also like to ensure that:

[ ] https://apisnoop.cncf.io is the primary url (currently that url redirects to https://apisnoop.cncf.ci)
[ ] If possible use the *.apisnoop.io as the suburls for previews, though a quick looks makes me feel this will only work for branches... ie BRANCHNAME.apisnoop.io

While this is somewhat working, we'll need a loop in the ./hack/ci/netlify-pr.sh to wait for the latest-build.txt to appear. It might also be useful to ensure that the job output we are pulling in is actually from the commit that generated this PR preview.
You may need to look at some of the ENV vars related to the commit sha hash or similar to wait for the correct job output to be available.

ENV work now merged.


docker-compose for nodejs and postgres connection

Hello
I hope you guys are well
So I would like to suggest a sample for nodejs with postgres connection, it could have:

a simple NodeJS app using Express
Postgres
And docker-compose file for setting the environment.
The connection between the nodejs app and postgres could be made through networks in compose.

In my profile there's some examples using docker-compose with nodejs.
It would be great contributing to this repository.

Hello @sisouza
There is some examples for compose in the dedicated docker/awesome-compose repository.
And there is a existing example with React Express and Mysql, maybe you can propose some improvements to this sample
I'll close this issue because all samples for compose are managed in this 2nd repository

Ho sorry, I was thinking we were in the comopse repository 🤦
I reopen the issue, my bad

okay, no problem, so can i contribute to this issue? it would be such a great experience! how should i start besides reading contributor guide? i am open to tips.
Thanks for answering! 😃

I am working on this task, then soon there will be a PR 😀

please see https://github.com/docker/awesome-compose/issues/247
I've got something ready if it helps.


Environment variable not resolve in arguments

Hello, @eskatos . I using your action in my build. I want use environment variable in arguments:
 - name: Publish with Gradle
        env:
          RELEASE_VERSION: ${GITHUB_REF:11}
        uses: eskatos/gradle-command-action@v1
        with:
          gradle-version: current
          arguments: test publish -Pversion=$RELEASE_VERSION

But, it not work for me. I get this result of this step:
/home/runner/gradle-provision-tmpdir/installs/gradle-6.1.1/bin/gradle test publish -Pversion=$RELEASE_VERSION

My env variable not resolve, and set as is. How can I set this variable for gradle param? Thx,

Solved in this topic https://github.community/t5/GitHub-Actions/Environment-variable-not-resolve-in-my-script/m-p/45969#M6399


Evaluate package manager alternatives to Hunter

Evaluate:

Conan
vcpkg
and more

Should work fine on Windows, Linux, and macOS. Also, we should still be able to compile core into WebAssembly.
TODO: what are other criteria, what do we want to optimize?
Might be related to Issue #358.
If we do move away from Hunter, one prerequisite is to include intx and ethash as submodules rather than Hunter packages.
Two points in favour of vcpkg:

We already use it for MPIR on Windows (by the way, GMP is now available as well)
It integrates nicely with Visual Studio

CRoaring is available in vcpkg (what about Conan?), so we probably should use its packaged version rather than have it as a git submodule.

PR #866 adds experimental support of the Conan package manager.


Do not use node-specific APIs

I understand that browserify and webpack exist, but I would like to use Tape in the browser without having to depend on a specific bundler. My own build process automatically compiles CommonJS to ES Modules, and so I can run those libraries directly in the browser without any bundling. The only issue with this library is that there are a few node-specific APIs at play here. I'm wondering if they could be replaced with browser-compatible versions so that everything works seamlessly across all platforms. Stream, path, and events all seem easy to replace. fs would probably be the most difficult, but it looks like it's only used in default_stream.js, could be replaced with an in-memory version potentially. I would be happy to do a PR with the changes.

The nature of modern web dev is that everything comes from npm, and everything requires a build process (a bundler).
The defacto standard for bundlers is that they do what browserify does, which includes reading the "browser" field and also stubbing out node core modules with either polyfills or empty implementations.
I'm not sure what your own build process is using, but if it doesn't have the feature set that the entire ecosystem has come to expect - nay, demand - then I'm not sure what tape could or should do to accomodate it.

I suppose we disagree here, which is okay. I'll just state it as my opinion that everything can come from npm without requiring node-specific APIs, and not everything requires a build process nor a bundler process, nor should everything require a build process or bundler process.
Thanks for making an awesome library nonetheless

There's virtually nothing that can be consumed from npm that does not require a build process or bundler process; and if something uses node-specific APIs, then it's incompatible with browsers, and it's not reasonable to expect a bundler will allow you to use it there (altho it's possible, as shown by browserify/webpack/etc)

There's virtually nothing that can be consumed from npm that does not require a build process or bundler process

I really do not believe that statement is correct. There are many modules that are just plain JavaScript that can be used right away. As I've been looking through the issues, I'm not the only one confused by this library's lack of compatibility with the browser. There is no reason in my opinion that this library should be written using any node-specific APIs. It is supposed to be simple and just run your tests and provide output. Why does fs need to be included? Why rely on node-specific streams?
Not everyone uses Browserify or Webpack, that may be what many people use and what you use, but if this library is only usable in the browser with those build systems, perhaps the library documentation should reflect that and not lead the user to believe this library is browser-ready without those extra steps.
Also, Webpack and Browserify are stop-gap solutions in my opinion. What we should be working toward is a world without complicated build-processes. All of this tooling should be built to melt away when the platform can support it, so that the barrier to entry is as low as possible, without sacrificing performance as far as is possible.


Modules not being publically exported (Pyright)

Describe the bug
Pyright will throw an error about imports not being publically exported.
To Reproduce
Steps to reproduce the behavior:

Generate an client
Import a module from the client
from test_client.models import test
Pyright will throw an error "test" is not exported from module "test_client.models"

Expected behavior
All public exports should be exported with a redudant alias.
from .feature import Feature should be from .feature import Feature as Feature
Additional context
Pyright will check imports in specific ways, which can be found here https://github.com/microsoft/pyright/blob/main/docs/typed-libraries.md#library-interface.
Can also be fixed in the way issue https://github.com/openapi-generators/openapi-python-client/issues/540 suggested.

#676 fixes this 🥳


Change emptyStateTitle in runtime? #question

Is there a way to set a different message title when it load, but then, when user do something (i.e push button) change the title?

Yes, you can change the title using the methods described in the docs.
This is just a matter of hooking up an action and performing on user tap.
I'm closing this issue as it is not a bug. Please feel free to ask this question for more help on StackOverflow


Implementation of map-reduce functionality

As per the request in #146, I've implemented functionality for the map-reduce command in the driver. It functions similarly to the other commands, except for the funkiness with the "out" option. Basically, the command can take either a string or a document; in the former case, it dumps the output into the collection specified in the string, and in the latter, the document can specify more options, like dumping to a different database or specifying how to merge/overwrite the existing documents in the collection. I'm not completely convinced there isn't a better design for the signatures of the collection methods and the options struct implemented here, so feedback on that would be appreciated.
Pinging @kyeah as usual

lgtm from my end :+1:

@saghm I've a rough sketch for implementation that try to differentiate some arguments that we have when dealing with mongodb map reduce. You might want to check it :D
https://github.com/mongodb-labs/mongo-rust-driver-prototype/compare/1.0...zerosign:feature/map-reduce?expand=1

I like a lot of the stuff in there! Taking the query as an argument probably makes sense, since I'd imagine it's pretty commonly used. I also like the changes with MapReduceOutput. Making a separate Inline variant definitely makes things a bit more usable.
As for the MapReduceFn struct, I'm still learning toward having map and reduce be separate arguments; it's structured that way in the Mongo shell, and it's also more consistent with how the other Collection methods are implemented. As for the finalize function, I'm not sure if that should be an argument or an option. How common is passing a finalize function in making map reduce queries in Mongo (I haven't really used them much). If they're fairly uncommon, I'd lean towards making them an option rather than an argument, but I don't really have a good enough sense of the common forms of the map reduce queries to know which way this would go.
I think the best way to go forward might be for me to merge my changes into a separate branch in this repo and then for you to make a PR to it so we can iron out the differences between the two implementations. Do you think you'll have some spare time any time soon to work on this a bit more?

Agreed with Sam -- we should be sticking close to the mapReduce implementations of other drivers, namely, taking in separate map and reduce arguments. We should also try to make the API as uniform as possible, and I think making the query and lesser-used options separate structs moves away from that. Perhaps keeping sort and limit in the options, and taking in the query explicitly as an argument may make more sense in keeping it close to the find implementation?

@saghm I'll try :-)
@kyeah ok

hey @saghm @zerosign ! It's been a while :) Just wondering if there's any potential or interest in picking this back up. If not, I'm happy to play around with different implementations and see what gels.

(@kyeah Honestly, I completely forgot this was still pending. My bad)
@zerosign, wayyyyy back, I had suggested that you make a PR merging my changes and yours. I think I was a little unclear about it though; I meant for the PR to be made to this repo, not my fork. If you're still interested in helping us out with that, feel free to submit the PR here instead! Otherwise, I can take care of it

@kyeah @saghm sorry for not following this a bit, sorry to not be able to contribute to this project at this time :'(. I think I'm okay with anyone to take whether to merge this PR or merge my implementation with this PR.


Allow users to do copy paste in the integrated terminal using ctrl+c, ctrl+v

VSCode Version:
All versions
OS Version:
Ubuntu

Within terminal if you need to copy text, currently we need to use ctrl+insert & for pasting shift+insert
However, this is a strange way to do this especially in an editor.
Intellij allows you to copy & paste text within terminal using ctrl+c & ctrl+v
If text is selected within terminal using mouse, ctrl+c would trigger copy. If no text is selected & ctrl+c is pressed, this would lead to usual cancellation of the running program, i.e exactly the way it is behaving now.
ctrl+v should paste the text bindly from clipboard
So, ctrl+c should selection sensitive copy/cancel & ctrl+v is blind paste

Hey @thekalinga, thanks for reaching out! It looks like we already have something like what you're looking for: https://code.visualstudio.com/docs/editor/integrated-terminal#_copy-paste
Note that on Linux, it should be Ctrl+Shift+C and Ctrl+Shift+V - perhaps @Tyriar could share a little more insight on that design decision.

Yes ctrl+shift+c/v are the defaults on Linux to align with gnome-terminal's defaults. You can configure your settings to do a bunch of cool stuff with copy and paste though. Just add this to your keybindings.json file to get the behavior you're after:
{ "key": "ctrl+c", "command": "workbench.action.terminal.copySelection", "when": "terminalFocus && terminalTextSelected" },
{ "key": "ctrl+v", "command": "workbench.action.terminal.paste", "when": "terminalFocus" }

You may also be interested in the terminal.integrated.rightClickCopyPaste setting which adopts the new cmd.exe's behavior to copy on right click with a selection and paste when there is no selection.

Looks like I am consistently missing on doing my home work w.r.t existing actions that are already available.
Will make sure I've done my background work before posting next issue :)
Sorry for the trouble.
Thanks in anycase


JDateTime cannot parse 20170808_100808

When parse time like "20170808_100808", I got error
java.lang.NumberFormatException: For input string: "20170808_100808",
JDateTime a = new JDateTime("20170808_100808", "YYYYMMDD_hhmmss");

Thanx @yeetrack !!! 👍
It happened that parsing code was a bit weird :)


Successfully updated the Google forms links to open on separate Tabs

🛠 Fixes Issue #632

👨💻 Changes proposed

✔ Check List (Check all the applicable boxes)

[x] My code follows the code style of this project.
[x] This PR does not contain plagiarized content.
[x] The title of my pull request is a short description of the requested changes.

📄 Note to reviewers
@SauravMukherjee44 @IAmTamal Please review and merge this PR. I have successfully completed the task.

📷 Screenshots

@SauravMukherjee44 please merge this pull request


Report duration analytics(Issue 112)

Please check as let me know if this is satisfactory.

thanks @abhishek71994


PasswordExpiredController: Accept block for update action

Currently if password is failed to update, nothing is displayed, and there is no way to change it easily (ie. without completely overriding update action in app's controller)
Devise though, allows user to add additional logic by passing a block to the update, like here: https://github.com/heartcombo/devise/blob/8593801130f2df94a50863b5db535c272b00efe1/app/controllers/devise/passwords_controller.rb#L34-L37
In this PR we're using same pattern.
So now user can do something like this:
class Users::PasswordExpiredController < Devise::PasswordExpiredController
  def update
    super do |resource|
      flash[:error] = resource.errors.full_messages.first if resource.errors.any?
    end
  end
end

As far as I'm aware, errors should be appearing on the page if the password fails to update. You can see a test that demonstrates this here. If you are still experiencing this issue, can you reproduce it in a brand new project? If so, can you create a dummy project and share it in example project here?
If you look at the commit that added the equivalent code to the devise project, you can see they added it for doing additional behavior such as enqueueing a job, not because errors didn't display.
I'm still happy to accept this PR for that reason, but I will need you to add a test for the behavior.

Coverage decreased (-1.8%) to 96.63% when pulling 045b7d8a717173d3845f9015257fcc564b1c8d37 on vlad-psh:accept-block-at-password-expired-controller-update into 42aa0f4b05ef4407efeb0fa61ebdb9c5cedf95e2 on devise-security:master.

@dillonwelch Thanks for your comment!
Yeah, you're right, default device's view template renders list of resource.errors.
However, if rails app, for example, configured to display errors from flash messages right in the application layout, and we want to put our errors there, yielding block at PasswordExpiredController would be perfect solution for this case :)
PS: I've added new test similar to how it is implemented in devise


Fixed the parameters passed to the AppendBreak method.

No text attribute should be passed, only break time and strength.

Looks good.


The sick driver disconnected with sick picscan150 while robot is running and can't reconnect again except power recycle

Hi
We are using the ros2 humble sick_scan_xd driver for sick picoscan150, and current we encountered an timeout issue during robot running: there is no topic published. After that, we launch the picoscan150 launch file sepratedly, but it still doesn't work.  (see the log attached below). After we power cycle the lidar, this issue resolved, could you tell us why this issue happens and how can we fix it? Thanks.
sicklaunchfaied.txt

Thanks for your feedback and logfile. The lidar responds with error code 3 (unknown sopas index) to the IMU activation command "sWN ImuDataEnable 1". It means that your lidar does not support an Inertial Measurement Unit (IMU).
Your lidar is most likely a picoScan model w/o addons, which do not have an IMU. Please disable the IMU in the launchfile sick_picoscan.launch:
<param name="imu_enable" type="bool" value="False"/> <!-- Enable or disable inertial measurement unit IMU -->
Alternatively, use launch file sick_picoscan_single_echo.launch, which does not activate the IMU.


NewTubeSet not called

In your readme file, the code sample is wrong.

The type Conn uses a feature of Go called embedding, where it contains a field of another type, but the field has no name. It uses this with both Tube and TubeSet. The methods on those types, like Peek, Reserve, etc, can all be called on a Conn as well. This is what the beanstalk package documentation is referring to when it says "the embedded types carry methods with them"—it means you can use those methods as if they had been defined on Conn itself.


this.BufferIndices is not a function

When trying to run the Image-transition example, I get this error
from bas.min.js.
Anyone knows the cause??

I dont know if this is usefull, but it occurs when its a SlideGeometry?

Can you share some of the source code where this is occuring? Also, what's a slide geometry?

Sure, and SlideGeometry is what $this refers to after BufferGeometry.call(this)
SlideGeometry of type BufferGeometry (im just starting with your library, so im not sure on specifics).
The following is from ModelBufferGeometry.js:
`function ModelBufferGeometry(model, options) {
BufferGeometry.call(this);
/**

A reference to the geometry used to create this instance.
@type {THREE.Geometry}
*/
this.modelGeometry = model;

/**

Number of faces of the model.
@type {Number}
*/
this.faceCount = this.modelGeometry.faces.length;

/**

Number of vertices of the model.
@type {Number}
*/
this.vertexCount = this.modelGeometry.vertices.length;

options = options || {};
options.computeCentroids && this.computeCentroids();
this.bufferIndices();
this.bufferPositions(options.localizeFaces);
}
ModelBufferGeometry.prototype = Object.create(BufferGeometry.prototype);
ModelBufferGeometry.prototype.constructor = ModelBufferGeometry;
/**

Computes a centroid for each face and stores it in THREE.BAS.ModelBufferGeometry.centroids.
/
ModelBufferGeometry.prototype.computeCentroids = function() {
/*

An array of centroids corresponding to the faces of the model.

@type {Array}
*/
this.centroids = [];

for (let i = 0; i < this.faceCount; i++) {
this.centroids[i] = Utils.computeCentroid(this.modelGeometry, this.modelGeometry.faces[i]);
}
};
ModelBufferGeometry.prototype.bufferIndices = function() {
const indexBuffer = new Uint32Array(this.faceCount * 3);
this.setIndex(new BufferAttribute(indexBuffer, 1));
for (let i = 0, offset = 0; i < this.faceCount; i++, offset += 3) {
const face = this.modelGeometry.faces[i];
indexBuffer[offset    ] = face.a;
indexBuffer[offset + 1] = face.b;
indexBuffer[offset + 2] = face.c;

}
};

Did you ever resolve this issue @L03TJ3 ? If I run the examples locally, everything works.

I hadn't been able to look at it yet. I just tried a few things out, and still couldn't resolve the issue.
Then I found out I have a different version of /examples/image-transition/main.js.
But what the cause is in that other version, is a real mystery.
But no issue for here, thus this can be closed I guess!


health link relation

It would be interesting to also propose a health link relation (or similar). I imagine a scenario where service responses include a Link header with it
Link: <https://example.com/monitoring/health>; rel="health"

This link relation could also be used on application/json-home representations
{
  "api": {

  },

  "resources": {
    "health": {
      "href": "/monitoring/health"
    }
  }

}

This would be a nice way to improve discoverability.

@TODO: reference status link rel from the spec.

Have you considered using well-known URIs (with associated registry) and include a registration for a well known URI /.well-known/health ?

Since the RFC defines content format and not the address (e.g. in Kubernetes the format would be used by two endpoints for liveness checks and readiness checks), these kind of things may only be defined in an FAQ section of the RFC as the additional suggestions.
That said, speaking of well-known URIs specifically, the spec has been standard for over 8 years but I personally haven't seen it in common usage. Is it just me? What are some prominent usages of well-known URIs that you know?

Off the top of my head ACME Challenges stands out as the one big success story. The well-known registry itself has numerous entries, so presumably it's being used, but like with ACME challenges, in places where we don't notice.
Registering a .well-known name is just a nice way of "getting out of the way" of the primary namespace of the host, and might ease discoverability by way of a management server simply ask GET /.well-known/health without having to discover the resource URI; an origin is enough.  Either it gets an application/health+json document, or it doesn't.

On 2018-12-06 03:17, Irakli Nadareishvili wrote:

That said, speaking of well-known URIs specifically, the spec has been
standard for over 8 years but I personally haven't seen it in common
usage. Is it just me? What are some prominent usages of well-known URIs
that you know?

this may be intentional. the idea of well-known is not so much to
standardize a naming pattern, because that would cause a flood of
registrations. the idea is to solve discoverability in cases where it is
not possible or reasonable to discover resources through other means
such as links. my guess is that a well-known "health" registration would
be met with some skepticism, as for APIs, it seems easily possible and
even advisable to make health endpoints discoverable via links.
the "status" link relation just made it through its last-call reviews
and will become RFC early next year. my recommendation would be to
strongly encourage healthcheck resource discoverability through "status"
links in key API resources, such as an API's home document.

I am not arguing against using links to discover the health of a system, because I do recognise that an API might want to link to a health resource to allow clients of that API to react accordingly. (For example, api.example.com might have a link to health.example.com/api to report on the API's health.)
However, I also see situations where you have a large set of heterogeneous components (e.g. APIs, web pages, caches) that might have little in common when it comes to media types (home documents), but that might all (because of an internal service policy) expose some notion of health using application/health+json.  Having to go through some home document to look for the health resource seems wasteful, since these various services might have different "home documents", some might not even have room for a home document that supports a link with this relation.
If this spec registered health in the well-known registry, it could make it a lot easier to deploy health checks to a lot of components where linking does not make sense.

On 2018-12-06 12:00, Erik Mogensen wrote:

If this spec registered |health| in the well-known registry, it could
make it a lot easier to deploy health checks to a lot of components
where linking does not make sense.

again, my understanding is that well-known was specifically defined to
make site-wide information available (with the canonical example being
the robots.txt scenario). while not all APIs will use links, i think it
is practical for pretty much any API style and technology to define how
to discover their status info.
in many cases, i would even expect that the well-known assumption of one
resource per site might not be a great fit for APIs. but it may actually
be a good fit for actual web sites, but these can of course just link to
their status page as well.


Refactor initialization API to conform to shared design with iOS SDK.

@optimizely/fullstack-devs
Refactored the initialization API to match the API design we agreed upon for both iOS and Android SDKs.

i'd differ to @jophde for the final ok though.

LGTM


Integrate UDapp (universal-dapp.js) better

Historically I think UDapp was a fork of some of the initial browser-solidity UI, greatly improved, then it made it back into browser-solidity.
Since it doesn't seem to be used elsewhere, wouldn't it make sense splitting it up and integrating it more closely into the codebase? Even more so given the efforts of @redsquirrel we have a much more manageable app source code.

@axic One of my next tasks (been waiting on #51 to be merged) was going to be to start refactoring the UDapp code. My intention is to eventually remove the distinction between app and udapp, in favor of modules with clearer responsibilities. Is that what you have in mind?

Yes, there's little point having it separate.
I would like to keep a small wrapper managing the execution context, which is effectively a wrapper over VM and web3, but doesn't have the rendering responsibilities.


add new page for Crystal Clemmys

This is a place holder in which we can fill out migration notes as they come up.

It's currently hard to discover any page unless there's a link path to it from the entry point

That's a good idea, but I'd like to try it out locally before pushing a change that uses links and stuff. So I'll probably wait on some basic instructions in the README or CONTRIBUTING files as to how to generate the pages locally. We were discussing that in https://github.com/ros2/ros2_documentation/issues/10#issuecomment-434732867.


Fix for edge case when gif data is invalid

Sometimes GIF data may be invalid due to incorrect encoding, corrupted transmission etc. This causes problems when attempting to call drawImage() to the canvas context. In most cases, the frame data will be undefined so we must check for this before attempting drawImage() just in case. There’s probably a more elegant way to handle this, but it seems to work for my use-case.

@UXVirtual i am so sorry for the late reply.
thank you so much for your PR 🙏
i need to close this as the branch got conflicted.
but i added your code here and added you as a contributor.


focal loss

Thanks for releasing the code .Firstly,I want to ask if you have tried the focal loss and if it works. Then i want to ask if you achieve the same map with the refineDet paper. By your table , I see the map is 0.4% higher and i want to ask the reason. And if the inference time is the same as the paper. Thanks again.

It seems to no improvement using the focal loss, 0.4%map is just fluctuation in experiment results. And I did't test the speed very strictly. @Sun-Fan

@yqyao sigmoid focal loss implement seems not right.
origin code:
loss_neg = -1. * torch.pow(1 - P, self.gamma) * torch.log(1 - P) * (
1 - targets) * (1 - alpha_mask)
but according to paper, I think it should be:
loss_neg = -1. * torch.pow(P, self.gamma) * torch.log(1 - P) * (
1 - targets) * (1 - alpha_mask)
@yqyao Please help to confirm it.
Thanks a lot!


Database is locked

Sorry, here again.
I am testing the system done with dblite and after a two days of testing I got this error:
````Error: Error: near line 44372: database is locked```
It caused the next query to fail.
Is there any workaround? Or maybe I'm handling the errors in the wrong way?

had no answer in ages, will close this

yes, sorry, it is resolved. thanks!


Refactoring of the adapter template

Enhancement Description
To benefit from the practices of microservices kits like gokit.
// @kumarabd

@leecalcote I assume this is the repo that we are using currently for templates? https://github.com/layer5io/meshery-adapter-template
We need to create a repository for the gokit and meanwhile ill push in the docs for the new template design.

@kumarabd is there an update on this?


Announcement: Cake.Orchard will move to the Cake Contrib organization ( https://github.com/cake-contrib )

Hey @davidangel @DanielOliver @phillipsj I'm writing on behalf of the Cake team, after trying to reach out to you via email and Twitter over the past several weeks without getting a response.
I understand that some of you are no longer involved with @RadioSystems, but if you can connect me to anyone that have admin access to this repo, please do, otherwise feel free to ignore this message.
We are keen ensure the longevity of this addin in the Cake ecosystem and ensure that it remains compatible with future versions of Cake.
It would be great if we could get this repository moved into the Cake Contrib organization for a clean transition.
The easiest way to get the repository into the organization would be for you to transfer the repository to my GitHub account ( augustoproiete ), and then I can move it into the cake-contrib org.
If we don't hear from you until March 25th, we'll assume this addin has been abandoned, and we'll fork it into the cake-contrib org, and continue maintaining this addin in the fork.

The code of the Cake.Orchard addin is now maintained at
https://github.com/cake-contrib/Cake.Orchard


docs: Fix unclosed docstring

What

This PR fixes an unclosed docstring in CameraProps type.

Changes

This PR adds ``` at the end of the codeScanner docstring

Tested on

I think there is no need to test :)

Related issues
No related issues.

dope thank you!


in operator shouldn't narrow {} originating in unknown

Fixes #50531.
This is a targeted fix for the exact issue in #50531. It doesn't address other known issues with the in operator.

@typescript-bot test this
@typescript-bot user test this inline
@typescript-bot run dt
@typescript-bot perf test faster
@typescript-bot test top100

@typescript-bot cherry-pick this to release-4.8

What was the cause of #50531?  It’s weird that unknown -> {} got narrowed by in but a directly-typed {} didn’t.

It’s that weird declaredType !== type condition—we discussed rewriting that whole set of conditions for 4.9 such that in only filters object types out of unions by property when there’s more than one object-like type in the declared type. There was also some discussion about whether to do anything if the property tested by in doesn’t exist in any of the object-like types in the union. (@ahejlsberg can probably better explain where we landed.)


Help inside Algernon

As a user new to Algernon I want to have keyword that displays all commands available to me I order to interactively discover Algernon.
Acceptance Criteria

Client
Team
Text

:heavy_check_mark:
entering help gives a list of hotwords

:heavy_check_mark:
entering help [keyword]will display an explanation of a keyword

:heavy_check_mark:
the keyword is documented in the Wiki

It might be a good idea to transfer the keyword ? to also display the help.

Todos

[ ] Find out what printout does
[ ] Write Help texts

We have investigated the overflow issue a bit and would bounce it back to the team that tried to fix it since a fix only pertaining to help texts would be hacky and bad for the architecture and fixing it for all resultitems would be out of scope and infringe on the autonomy of that team.

I have written the remaining help texts. In light of issue #57, I have only documented one way of searching for class comments in order to not clutter up the help menu.

I have also implemented the action. I think the pr should be ready for review.
@sinnaj-r would you please take a look and add tests or refactor if need be? Feel free to un-draft the pr and request reviews once you are done.

It seems like SortedCollection>>take: is only available on Squeak 5.3 and not on the earlier versions. What is our strategy for dealing with that?

I think the build targets are for the client to decide.
@MrModder, what version of Squeak should we support?

Regarding version support: At least one version before 5.3 would be good.
But if it is very hard to replace

We have replaced it, it's not that hard. It was just a general question that came up due to this small issue. We continue to support 5.1, 5.2, 5.3 and trunk. (I'm acutally using trunk, so we have manual testing there in addition to the provided swt-squeak).

@MrModder, is there a reason you reopened the issue?

Closing the issue was a mis-click on my part, so I reopened it. The issue shouldn't be closed until it has been accepted in the customer meeting.


IGNITE-12508: Fix GridCacheProcessor#cacheDescriptor's Time Complexity

This commit adds a new mapping from cache ID to cache name, thus allowing
cacheDescriptor method to get the needed cache descriptor in two map
lookups.

@alamar Thank you for the review! Updated the PR

@alex-plekhanov @alamar Updated, please see. Also, how do I trigger a MTCG build?

LGTM! Thank you for your contribution.
Also, @atris you should ask for ASF JIRA permissions on dev-list, so you can assign this ticket to yourself and change it's status to Patch Available.
P.S. to run build via MTCGA you must register at Apache Ignite TeamCity and login with your TeamCity credentials at mtcga. See details here

@alex-plekhanov @sk0x50 @alamar @SammyVimes Thank you for looking. Updated the same, please see.

LGTM! Thank you for your contribution.
Also, @atris you should ask for ASF JIRA permissions on dev-list, so you can assign this ticket to yourself and change it's status to Patch Available.
P.S. to run build via MTCGA you must register at Apache Ignite TeamCity and login with your TeamCity credentials at mtcga. See details here

Thank you! Let me do that

@alex-plekhanov Updated, please see

Updated with latest master

@alex-plekhanov Please let me know if any further comments


Typescript nk.multiUpdate() function does not update user account details

Description

From Typescript environment, nk.multiUpdate() with UserUpdateAccount[] does not work.
Steps to Reproduce

const user = nk.authenticateCustom(nk.uuidv4());
nk.multiUpdate([{
    userId: user.userId,
    displayName: 'test',
    metadata: { test: 'test' }
}], null, null);

const acct = nk.accountGetId(user.userId);

The user's account details are not updated.
Expected Result
acct = {
   user: {
    displayName: 'test',
    metadata: { test: 'test' }
  }
}

Actual Result

acct = {
   user: {
    displayName: '',
    metadata: {  }
  }
}

Your Environment

Nakama: 3.10.0
Typescript environment

@gpiumatti This has already been fixed in commit eb5270fdd5a8ab79f0bed86d51d38a2b6d689a45 and will be part of the next release. 👍


why not provided as npm package?

how do i add this to a project that I need to the cloud if i have it only as a local folder?

You could use is as a CDN package


Drill 1950 : Parquet row group filter pushdown.

@amansinha100 , @parthchandra , I pushed three commits, to address the review comments, and add one option.  Please kindly take another look at the commits. Thanks!

LGTM.  +1


Add BMP support

Adds in BMP support that would resolve #171
Tested by loading a BMP, resizing it and then saving it back as a BMP.
Obviously requires PHP 7+

Awesome, thanks!
Curious on the mime types. I figured it would be image/bmp but noticed you used a couple proprietary ones in addition. I got to googling and found this. 😮
image/bmp, image/x-bmp, image/x-bitmap, image/x-xbitmap, image/x-win-bitmap, image/x-windows-bmp, image/ms-bmp, image/x-ms-bmp, application/bmp, application/x-bmp, application/x-win-bitmap

Are any/all of these applicable? Just wondering why you chose those two, or if you found something in the GD docs that explains why those should be used.

Yeah, the image_type_to_mime_type() function has a returned value of image/bmp and the BMP wikipedia page lists both image/bmp and image/x-bmp while both ietf.org and iana.org indicates the only subtype is image/bmp.

This probably depends on the OS. I quickly found at least one instance where getimagesize() returned image/x-ms-bmp. Not sure which ones are actually in use, though, or which ones should be included.

This probably depends on the OS. I quickly found at least one instance where getimagesize() returned image/x-ms-bmp. Not sure which ones are actually in use, though, or which ones should be included.

I created a BMP in mspaint and then tried to load that through imagecreatefrombmp and x-ms-bmp and that was the type returned, so that's why I added x-ms-bmp. I then googled "BMP MIME type" and saw image/x-windows-bmp so I added that too.
No harm in adding the other types if PHP supports them, right? That is, if they're all different MIME types for the same base format..

No harm in adding the other types if PHP supports them, right?

Agreed.
Just out of curiosity, what Imagetype Constant do you get if you process the mspaint image that you made through exif_imagetype() ??
Hopefully it returns type 6 (IMAGETYPE_BMP) but just thought I would ask to see / make sure.
Hmm, might be a good idea to test it on both the original image and the one made by imagecreatefrombmp(), to see if it returns different results.

Both the Windows BMP and the one converted using imagecreatefrombmp() return int(6), which is IMAGETYPE_BMP
These were both tested on Windows 10 (Version 1709) with PHP 7.2.0
I just had a look at that fileext site, and they list a whole bunch of different MIME types for jpeg, including image/x-xbitmap (??), so rather than going down a rabbit's hole of MIME types for BMP and other types, I'd personally be inclined to leave the BMP MIME types as they are in my PR (given that they're the most common), and any new ones can be added via a PR

I'd personally be inclined to leave the BMP MIME types as they are in my PR (given that they're the most common), and any new ones can be added via a PR

Agreed. Thanks for the solid PR!


MB: QoL: Seed the batch recording comments script

I ran a test on a release. Just wanted to let you know the script doesn't work if there is more than one date on recordings.
https://musicbrainz.org/edit/80062461

Fixed in 2021.6.2.
The script will now refuse to update comments if there are conflicting dates, places, or areas in the ARs, or if the new comment differs significantly from the existing comment. It may be a bit overzealous in some cases, but it's better to be safe than sorry. It will also keep the credited name of a venue, if present.


Added BIOS version aliases

The code has been modified to allow using the same settings for multiple BIOS version strings.
This is required for example for the SCPH-102, where there were two different and incompatible versions (4.4 and 4.5) BIOSes shipped on them, so "102" doesn't fully identify the settings required to build a working image.

Thanks for the contribution, funnily enough I implemented a similar model/bios name deduplication in parallel... But the support of the 10x models is welcome. Could you update the pull request? I can also just pick and apply the new BIOS support if that's easier.

There's a slight problem with the current approach, and it's that the SCPH-102 has a single model number but two different BIOSes (v4.4 and v4.5). How can you map that to your structure?

I see, I will update the options to allow selection by model and/or BIOS.

Latest commit adds support for selection by model or BIOS version. For the SCPH-102, it should simply not appear in the model list, but only in the BIOS list.

Updated to use the new structure

Thanks!


How was the fluency model trained?

As I understand, this is just a BERT with a binary classification head.
If that is the case, then what was the training data for this model?

This is not an issue, please use this forum for creating issues ONLY


added current voting power to UserInfo

In the left sidebar, when viewing a user's profile, the current voting power is now shown.

In a future PR this should be implemented:
function calculateVotingPower(votingPower, lastVoteTime, precision) {
    let secondsPassedSinceLastVote = (new Date - new Date(lastVoteTime + "Z")) / 1000;
    votingPower += (10000 * secondsPassedSinceLastVote / 432000);

    return Math.min(votingPower / 100, 100).toFixed(precision);
}

I took this code from another project. It takes into account the replenishment of the voting power since the last vote.

I don't know if I use it correctly and I also don't know why I have to divide by 10000 but... it works.


Publish a new version

The library has changed a lot and the crates.io version hasn't been updated in a while. If possible, please release a new version of the library so that other libraries can depend on it (crates.io requires no links to github projects as dependencies). Thanks.

I wouldn’t call “changed a lot” three commits since 2015, but regardless I’m not planning to maintain this code. I’ve added a section to the README to explain this. If you’d like to use this code, consider copying it into your repo.

Yes, but you yanked the crate from crates.io for some reason. Why? I'd just leave it up.

I yanked it so that people wouldn’t depend on it. I don’t want people to depend on it because I don’t want to deal with reviewing PRs and publishing new versions. If you want to do that, feel free to do it in another repository. The code’s still open-source.


Better command handling

The command handler should be able to do the following things:

Check for member permissions
Generate help documentation automatically
Handle debugging commands gracefully
Use objects for commands (or alternatively a builder pattern, DSLs aren't really a good solution here, why didn't I make this with Kotlin :c)

A DSL could be a solution here. Although, that would introduce a lot of this keywords across commands, which harms readability.
More research is needed for DSLs.
As for builder patterns, given how I want type-safe arguments and permissions to work, they might be the best fit.
Typing objects is hellish, even more so if you want other parts of the object to "react" to argument types.


Styles being set on body instead of #root will affect dashboard styles

Discord username
No response
What type of issue is this?
Permanent – Ocurring repeatably
Is this issue blocking you from using Enso?

[ ] Yes, I can't use Enso because of this issue.

Is this a regression?

[ ] Yes, previous version of Enso did not have this issue.

What issue are you facing?
cursor: none is being set on body. This will hide the cursor for the dashboard as well, which is not good because the dashboard doesn't have a replacement cursor, unlike the editor which has the translucent circle.
https://github.com/enso-org/enso/blob/7ad09f4e406dfad999ec47c772157eadf3761279/lib/rust/ensogl/core/src/application.rs#L81
Expected behaviour
cursor: none should be set on #root instead; this way the cursor will always be visible on the dashboard and top bar.
How we can reproduce it?
No response
Screenshots or screencasts
No response
Enso Version
latest
Browser or standalone distribution
Standalone distribution
Browser Version or standalone distribution
standalone
Operating System
Linux
Operating System Version
No response
Hardware you are using
No response

@somebody1234 is this issue blocking some work on dashboard?

not really, since you can manually remove the cursor: none

note: i cannot consistently reproduce the underlying issue, usually (but not always) it sets cursor back to auto when out of view. (regardless, this will not be an issue anyway, if this change is made)

hasn't been an issue lately, so closing this


Danish Update

GitHub has somehow made me lose the permissions to edit #2070 #2071 and #2072. So here is a new pull-request with the changes and all-in-one request (my old pc couldn't run GitHub sorry for that).
Phone
Accepts:
+45 21-77-21-77
+45 21 77 21 77
+45 21772177
+4521772177
21 77 21 77
21-77-21-77
2177 2177
2177-2177
21772177
Have changed the regex to use the non-capturing group as requested.
Postal codes
Have also changed the postal codes to accept from the Danish Kingdom instead of Danish and Greenland only. This means that the Faroe Islands is now included.

Have no idea about why its keep failing the test

Hi @BenjaminHoegh
Thanks for your contribution! and sorry for taking so long to repond to this PR.
I'll triage and take a look at it as soon as possible!


Boost 1.80.0 Bind Placeholder warnings

We recently upgraded to boost 1.80.0 in combination with the latest turtle library.
In the compilation of our project we are getting te following warnings with turtle
/opt/boost_1_80_0/include/boost/bind.hpp:41:1: note: #pragma message: The practice of declaring the Bind placeholders (_1, _2, ...) in the global namespace is deprecated. Please use <boost/bind/bind.hpp> + using namespace boost::placeholders, or define BOOST_BIND_GLOBAL_PLACEHOLDERS to retain the current behavior.
relating to
turtle/detail/action.hpp:19:0,
turtle/detail/function.hpp:18,
turtle/detail/functor.hpp:13,
turtle/reset.hpp:15,
turtle/mock.hpp:17,

Will turtle be made compliant with boost 1.80.0 ?
For the moment we define BOOST_BIND_GLOBAL_PLACEHOLDERS to retain the current behavior

There likely just needs to be another release of turtle. Try the recent master which has lot's of changes improving compiletimes and more. Note that it also requires C++14

This is fixed with Turtle 2.0


Added .sln files

Summary

Remove *.sln from the .gitignore
Add local solution files, that were otherwise ignored

You can include a .sln file with --force -- what's the motivation for making it included by default?

I'd rather not allow .sln files by default. I think more people are going to add one by default when it's not needed (i.e. there's only one project), and hopefully Snippets 5000 will catch when a .sln file is missing but needed.
Also, are all the .sln files here necessary (i.e. there's more than one project)?

I have updated the PR based on everyone's feedback thus far.


Sign Language to text or speech

A system to assist physically impaired individuals by translating Indian Sign Language (ISL) into text or speech, enabling better communication. The proposed solution is to build a real-time detection system using computer vision and machine learning. This system would employ CNNs to recognize ISL gestures and sequence models to interpret them, converting gestures into audio or textual output. Alternatives considered include wearable devices with sensors for gesture detection or manual input-based translation apps.
@Niketkumardheeryan kindly assign this issue to me under GSSoC'24 extended and hactoberfest ' 24

Explore existing publicly available ISL datasets that you can incorporate into your training data. Some resources to explore include:
RWTH ISL Dataset: https://www.statlearning.com/resources-second-edition
The ASLLVD 1.0 Indian Sign Language Video Dataset:
https://www.bu.edu/asllrp/av/dai-asllvd.html


feat: support sticky, unicode and dotAll

Close #3.
Especially dotAll (s flag) to provide mongodb $regex support for mongoose
If this PR is accepted, please release a new version in order to use it in mongoose.

Thanks! Released in 1.0.0


404 after upgrading from 3.2.1 to 3.3.0

INSERT SHORT DESCRIPTION EXPLAINING THE HIGH-LEVEL REASON FOR THE NEW ISSUE HERE.
Current behavior
After upgrading (removing old plugin and installing new one) when navigating to the /wp-content/plugins/bullhorn-oscp page I get a 404.
Expected behavior
Page should render as expected
Steps to replicate behavior

navigate to https://spotontalent.com/wp-content/plugins/bullhorn-oscp/

Screenshots
Current
Expected

Hello, to ensure everything is installed correctly, can you view the plugin under the Wordpress admin page?

Yes, and I've verified the app.json is being generated as well

Yeah I guess I can confirm I do see the json file under https://spotontalent.com/wp-content/plugins/bullhorn-oscp/app.json
What happens if you use the shortcode on a page so [oscp] on a random WordPress page? Also, can you confirm that you see an index.html file in that directory?

yes, the index.html file is present and the shortcode returns the 404 as well, you can click the search jobs button on the original page to see how it also returns a 404

I am able to see every other file resolve (minus some security rejections).   I am wondering why the index.html file would not.  My initial instinct is server config in some form.   Was there a .htaccess in this directory previously that helped resolve requests?

not to my knowledge

it should have been a fresh install based on the fact that I removed the plugin and then installed it fresh, I didn't see any other configuration steps in the documentation.

Did you update WordPress Versions as well by chance?  I do not see any reason this should be happening.  I am unable to reproduce this specific issue on my demo site (error intentional).
The only change that can cause this to my knowledge is a change to your .htaccess's URL rewrite rules or the file permissions for that specific file being off (looks good to me in that screenshot).
Is getting your web host looped in an option? Because from everything you have shown, it should be working

We did not upgrade the wordpress version, I was just brought in as a consultant today on this issue so I'm unfamiliar with the host situation yet.

I tweaked the .htaccess file to get the page to render but every job posting now links to undefined https://spotontalent.com/wp-content/plugins/bullhorn-oscp/#/jobs/undefined

This is causing invalid job id

Heya! id needs to be added to the fields property in the app.json file.  That controls the fields pulled down in the API requests,

Thanks @charlesabarnes We're up and running again!


chore: release  code.pianist 1.4.0

:robot: I have created a release
1.4.0 (2024-08-16)
Features

111 (6fd2d55)

This PR was generated with Release Please. See documentation.

:robot: Created releases:

code.pianist-v1.4.0
:sunflower:


moarvm: 2024.01 -> 2024.05

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/moarvm/moarvm/releases.
meta.description for moarvm is: VM with adaptive optimization and JIT compilation, built for Rakudo
meta.homepage for moarvm is: https://moarvm.org
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2024.02 with grep in /nix/store/wcn2j4pwqcc5q9clqszg7cfdkpycdzws-moarvm-2024.02
found 2024.02 in filename of file in /nix/store/wcn2j4pwqcc5q9clqszg7cfdkpycdzws-moarvm-2024.02

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

4 total rebuild path(s)

4 package rebuild(s)

First fifty rebuilds by attrpath
moarvm
nqp
rakudo
zef

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/wcn2j4pwqcc5q9clqszg7cfdkpycdzws-moarvm-2024.02 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/92f99f2cd94b388a7bdb535f927b9c7f79f7ef21#moarvm

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

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

4 packages built:

moarvm
nqp
rakudo
zef

Maintainer pings
cc @thoughtpolice @vrthra @stigtsp for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/moarvm/moarvm/releases.
meta.description for moarvm is: VM with adaptive optimization and JIT compilation, built for Rakudo
meta.homepage for moarvm is: https://moarvm.org
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2024.04 with grep in /nix/store/j5y6szs33c1gx5mc47pa2ad129yss9xz-moarvm-2024.04
found 2024.04 in filename of file in /nix/store/j5y6szs33c1gx5mc47pa2ad129yss9xz-moarvm-2024.04

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

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath

moarvm
nqp
rakudo
zef

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/j5y6szs33c1gx5mc47pa2ad129yss9xz-moarvm-2024.04 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/2be3baaebffc5832fc7b25bf06026f4a864fceb0#moarvm

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

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

4 packages built:

moarvm
nqp
rakudo
zef

Maintainer pings
cc @thoughtpolice @vrthra @stigtsp for testing.

Automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/moarvm/moarvm/releases.
meta.description for moarvm is: VM with adaptive optimization and JIT compilation, built for Rakudo
meta.homepage for moarvm is: https://moarvm.org
Updates performed

Version update

To inspect upstream changes
Impact
Checks done

built on NixOS
The tests defined in passthru.tests, if any, passed
found 2024.05 with grep in /nix/store/vmiab6k05bkk5pqs0jrya4m7989wvznb-moarvm-2024.05
found 2024.05 in filename of file in /nix/store/vmiab6k05bkk5pqs0jrya4m7989wvznb-moarvm-2024.05

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

5 total rebuild path(s)

5 package rebuild(s)

First fifty rebuilds by attrpath

moarvm
nqp
rakudo
zef

Instructions to test this update (click to expand)

Either download from Cachix:
nix-store -r /nix/store/vmiab6k05bkk5pqs0jrya4m7989wvznb-moarvm-2024.05 \
  --option binary-caches 'https://cache.nixos.org/ https://nix-community.cachix.org/' \
  --option trusted-public-keys '
  nix-community.cachix.org-1:mB9FSh9qf2dCimDSUo8Zy7bkq5CX+/rkCWyvRCYg3Fs=
  cache.nixos.org-1:6NCHdD59X431o0gWypbMrAURkbJ16ZPMQFGspcDShjY=
  '

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

Or:
nix build github:r-ryantm/nixpkgs/18ea06a77e58ab2a6d4649ce7499f967d9c27b20#moarvm

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

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

1 package failed to build:

zef

3 packages built:

moarvm
nqp
rakudo

Maintainer pings
cc @thoughtpolice @vrthra @stigtsp for testing.

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

1 package failed to build:

zef

3 packages built:

moarvm
nqp
rakudo

The zef failure was maybe caused by moarvm being independently bumped from rakudo and nqp. I'm thinking we should disable the auto updater here


fix #472 throw exception if given class name is invalid

This PR is attempting to fix #472. While Mockery gets a parse error with Mockery::mock('this-is-invalid') this fix throws a Mockery\Exception error with friendlier message. It uses the regex on the official document and I'm assuming that namespaces follow the same rule.
It might be a little too strict since it currently allows a parameter like mock('\\\\Foo'). Please let me know if there's any better way.

Looks great, thank you!


Update template

hey
did they change the vortex icon?
did you test it out?
i can pull it and then run a makefile so if someone happens on it they can use it.

@Dyuko

Hello, there's no need to update the template. They just changed the color of the vortex icon, which doesn't affect image detection.
I downloaded a modpack with 700+ mods, and sometimes image detection would fail, which wasn't fixed by updating the image. I think sometimes the aspect ratio of the download button changes.


[Bug]: chromadb-client should not require sqlite3?

What happened?
Running chromadb-client on lambda produces the following error:
"Error: Your system has an unsupported version of sqlite3. Chroma requires sqlite3"
Having looked at https://github.com/chroma-core/chroma/blob/main/clients/python/pyproject.toml it seems to me that the sqlite3 client is not a dependency?
I have had to install pysqlite3-binary, however if the client is connecting to a chromadb server, wouldn't only the server need sqlite3?
Thanks for your consideration
Versions
chromadb-client 0.4.14.dev0
Relevant log output
"Error: Your system has an unsupported version of sqlite3. Chroma requires sqlite3"

Thanks this is a bug in the client code it seems. Will fix!


quiche-client panics if the server returns initial_max_data=0

thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: Done', apps/src/common.rs:881:14

https://github.com/cloudflare/quiche/blob/a7ab6dd0363b83b09039e166a5dae18fc75bec52/apps/src/common.rs#L877-L881
I don't think this is recoverable, but it would at least be nice to print a more helpful error here.

This is a bad UX, apologies. Let's fix it up.