Understand the breakdown of layouts in the PDF corpus

How does the corpus break down in terms of:

[x]  format (HTML and PDF)
and for PDFs:
[x] page count
[x] scanned vs not scanned.
[x] how many have chapters / bookmarks? (using doc.get_toc?)
[ ] layout
--
[ ] Write up results to a Notion page.

Clustering of VGG16 embeddings (a general-purpose model) hasn't been successful - the clusters produced by both kmeans and gaussian mixture models don't successfully separate layouts, even at a column level.
See notebook here.
I can't find a finetuned document image classification model anywhere, so my next step is to try clustering embeddings from LayoutLMV2, which are fine-tuned on documents and contain positional text embeddings, as follows:

visual embeddings only: the average-pooled initial visual embeddings concatenated with the average-pooled final visual embeddings
visual embeddings plus positional LM embeddings: If this proves slow, I'll try LayoutLMV2 with just the visual embeddings. the concatenation of the final hidden state of the [CLS] token, average-pooled initial visual embeddings and average-pooled final visual embeddings


Add mongodb-tools

It would be nice to have mongodump and mongorestore.

I don't think this is possible, there is no mongodb-tools package in alpine (AFAK)

in my case, my api image was based of golang,
git clone https://github.com/mongodb/mongo-tools
and ran go install
was easy for me since i was gona use it from the api side

Inside this image, you could just add mongo tools:
docker exec -ti mongo sh
then in the shell:
apk add --no-cache mongodb-tools

please add these https://docs.mongodb.com/manual/reference/program/ as mentioned by others.


_isOptional(type(of:)) Does Not Do What You Think It Does

In particular, if value is Any in a generic context, then type(of: value) is Any.Protocol which is never considered optional.  As a result, the first clause here (that provided special handling for printing optionals) was never actually being used for print() or other similar paths. (Curiously, it was used for string interpolation.)
Fortunately? print() was producing the right results for optionals because of a dynamic cast bug that failed to unwrap optionals in these same contexts.
Resolves rdar://58302667

@swift-ci Please test Linux

@swift-ci Please smoke test

Looks good for preserving the existing behavior. (As we discussed previously, this still isn't sufficient if the value is a multiply-wrapped Any, but that bug already existed.)

The best technical answer is probably to eliminate the special case for Optional entirely.  But that will require some additional discussion and socialization.

Yeah, ultimately it's only there in order to give Optional a fighting chance, because the dynamic casts that look for conformances below will look through Optionals. If we had separate "recursively unwrap and open an existential" and "test if this type conforms to a protocol" operations that didn't magically unwrap, we could do away with the special case.


[feat][workflow] add interactive features to bot

Features
Can we enforce the Bot to execute the following commands?

cherry-pick may not fit because it works between branches and we want to work between folders. Need to research more.

@maxsxu thanks for your great help on this! Feel free to add more ideas! 💡

Please do not automate cherry pick. Each cherry pick must be a deliberate action by the developer of the PR.

-1 for cherry picking in a bot

@Anonymitaet please add some motivation to the feature requests. Why do we need those features?

@dave2wave @lhotari thanks for your feedback! I should clarify more clearly.
We want to cherry-pick only documentation PRs (not code PRs) to reduce manual maintenance work.
Some doc changes are applicable to multiple doc versions. Currently, we need to copy them manually.

We could also reduce manual work by changing the workflow. Do we have documentation explaining why we still need this repo?

Some doc changes are applicable to multiple doc versions.

Can you explain this more? Doc version changes are not cherry picked, they are copied to the appropriate files.

We want to cherry-pick only documentation PRs (not code PRs) to reduce manual maintenance work.

That can be solved outside a docbot. There are security considerations so it's not just about convenience or preference using a bot. I'd suggest that there's a script that a committer can run to semi-automate your process.

We could also reduce manual work by changing the workflow. Do we have documentation explaining why we still need this repo?

Some doc changes are applicable to multiple doc versions.

Can you explain this more? Doc version changes are not cherry picked, they are copied to the appropriate files.

Yes, they are manually copied to files rather than cherry-pick to multiple branches (I use the inaccurate word cherry-pick, sorry, it results in confusion).

We want to cherry-pick only documentation PRs (not code PRs) to reduce manual maintenance work.

That can be solved outside a docbot. There are security considerations so it's not just about convenience or preference using a bot. I'd suggest that there's a script that a committer can run to semi-automate your process.

@lhotari

can you explain what the security concerns are?
any examples or resources for the script? Thanks!

@maxsxu thanks for your great help on this! Feel free to add more ideas! 💡

Thanks for bringing this out!

Closed as stale and no activities.


Crop the ROI along image boundarys

The current algorithm just moves points outside the image boundary along giving direction, but expect to crop by image boundary.

Suppose the size of the image is 1600900, and the coordinates of a vertex in the ROI are (1200, 1000). The existing method seems to change the vertex coordinates to (1200, 900) directly.
It might be possible to pad the bottom of the original image to make it 16001000, crop the ROI, and then crop out the padded part. But this may add a lot of computation

Suppose the size of the image is 1600_900, and the coordinates of a vertex in the ROI are (1200, 1000). The existing method seems to change the vertex coordinates to (1200, 900) directly. It might be possible to pad the bottom of the original image to make it 1600_1000, crop the ROI, and then crop out the padded part. But this may add a lot of computation

Plan to implement this function by the shapely API, which is implemented by C


Typo in the architecture image

In the architecture image, output names are not correctly written: YA -> ZB and YB -> ZA. They should be vice versa accourding to the paper:

The two batches of distorted views YA and YB are then fed to a function fθ, typically a deep network with trainable parameters θ,producing batches of representations ZA and ZB respectively.

The same image is also used in the paper and there are the same typos, too.

Good catch, will update, thanks!


Research on Power Estimation Formula

Amplitude sine control
Sine power estimation/control
Power Estimation
Signal power calculation
Signal energy estimation search / paper

https://dsp.stackexchange.com/questions/14474/energy-of-an-audio-signal


LDAP/AD Configuration: “save settings” button does not always become active.

Bug description
LDAP/AD Configuration: “save settings” button does not always become active when trying to modify config.
Expected behavior
Save Settings button should either be active or a red text / box outline shown on whatever field needs to be filled in.
Also, the password previously entered for ldap/ad service account should be remembered and not have to be re-typed each time a config change is made to ldap/ad.
Steps to reproduce the issue:

Once the password is entered

Technical details:

Portainer version: CE/BE
Docker version (managed by Portainer): 20.10.6
Kubernetes version (managed by Portainer): 1.21.0
Platform (windows/linux): ubuntu 18.04
Command used to start Portainer (docker run -p 9000:9000 portainer/portainer): helm chart
Browser: chrome

April 2022, this issue still happening. 😆


feat(@vtmn/css, @vtmn/react, @vtmn/svelte): progressbar, add a11y requirements

Changes description

Remove progressbar without progression label
The % is part of the HTML and is not added by the CSS anymore
Refactor the demo in consequence

Context

Some progressbar showcases didn't pass the a11y requirements. We need to enhance them to become accessible.

Checklist

[x] Make sure you are requesting to pull a topic/feature/bugfix branch. Please, don't request directly from your main!
[x] Check commits & PR names matches our requested structure. It must follow the https://www.conventionalcommits.org pattern.
[x] Check your code additions will fail neither code linting checks.
[x] I have reviewed the submitted code.
[x] I have tested on related showcases.
[x] If it includes design changes, please ask for a review with a core team designer.

Does this introduce a breaking change?

The :after selector is not used anymore.
Linear progressbar uses two spans to display the progression indicator.
Yes, you need to add the % in the progressbar bar explicitly.

Linear Progressbar BEFORE :
Loading

Linear Progressbar AFTER :

      Loading
      60%

Circular Progressbar BEFORE :

Circular Progressbar AFTER :
50%

Great job @GaspardMathon. But sorry, I have to convert to draft because:

you need to update in consequence all sources & showcases refered to the VtmnProgressbar components in community libraries (React, Svelte etc.)
we already have consumers of progressbar in CSS: https://cs.github.com/?q=vtmn-progressbar so breaking changes could cause problems (we will need to inform each of them)

Thanks for your attentiveness, I will make the changes

@GaspardMathon did you missed @vtmn/vue?


[1.x] Fix the issue for connecting if the SSL is not verified peer

See: https://github.com/laravel/reverb/issues/78

This fixed my problem during local development with Laravel Valet. Thanks :)

I want to sit on this one a little while as I'm not convinced it's needed.

I wouldn't sit on this. I've had nothing but trouble trying to get reverb working locally on MacOS with Herd secured sites. The most frustrating part is it will work one day and be broken the next.
The changes to the Factory.php with this config entry resolves my problems:
            'options' => [
                'tls' => [
                    'verify_peer' => false,
                ],
            ],

I would suggest adding verify_peer as it's own env variable.

Really, the problem has solved, please @joedixon merge this, If you want, I can make another more detailed PR.

Pushed some updates here which will resolve #93, #105 and possibly #106.
I opted not to include config by default for all of the SSL context options, but instead allow users to configure it manually.
Now, the check for Valet and Herd certificates will only be carried out if both local_cert and local_pk are not set. This means the other SSL options such as verify_peer, allow_self_signed, etc may still be used with Valet and Herd certificates.
Additionally, null values are removed from the TLS options array to allow environment variables to be used to control whether or not TLS is enabled.

Empurrei algumas atualizações aqui que resolverão #93 , #105 e possivelmente #106 .
Optei por não incluir a configuração por padrão para todas as opções de contexto SSL, mas em vez disso permitir que os usuários a configurem manualmente.
Agora, a verificação dos certificados de Valet e Rebanho só será realizada se ambos local_certe local_pknão estiverem configurados. Isso significa que as outras opções de SSL, como verify_peer, allow_self_signed, etc, ainda podem ser usadas com certificados Valet e Herd.
Além disso, nullos valores são removidos da matriz de opções TLS para permitir que variáveis de ambiente sejam usadas para controlar se o TLS está habilitado ou não.

This update broken forge applications running with ssl

Hi @lsdevelop, can you elaborate on what was broken? Are you running your Reverb server directly from the main branch?

Hi @lsdevelop, can you elaborate on what was broken? Are you running your Reverb server directly from the main branch?

Hi, yeah,
I have a chat app with deprecated websockets, after launching reverb,I'm up stating environment in forge for testing using @beta of reverb,
After merge this commit in next deployment the connection has return error for tls.
Solved after downgrade for bera4, I'm trying again now.

@lsdevelop you would have only seen this update if you explicitly used dev-main or @develop. This PR has not been released yet and beta4 is still currently the latest release.
Can you confirm the steps you took and verify the error you saw?


Update the Code documentation to include Flutter app demo example

Use the web version of the flutter app to display in the html documentation so that the user can see the live component in action

Done. Check this out! https://orange-opensource.github.io/ods-flutter/#/


Merging Smartcard CBA Feature into Dev

Smartcard CBA
This branch contains a feature that allows AAD account users to authenticate via USB using their YubiKey. This work is being done in order to help satisfy Executive Order 14028, "Improving the Nation's Cybersecurity" .
Summary

Certificate Based Authentication (CBA) will be expanded to allow logging in with certificates (PIV/CAC) provisioned onto YubiKeys.
Users can plug in the USB of their YubiKey into their Android device, and once they determine that they would like to authenticate via CBA (by clicking "Sign in with certificate"), they will be lead through a set of dialogs which guide the user through selecting a certificate for authentication.

NFC support will be implemented in the next quarter. See "Future Work" section farther down below.

For more details, please see the design documentation for this feature.

Steps
Note: This private preview testing document has detailed steps and screenshots for testing with Authenticator and Outlook.

User can plug in their YubiKey while the AuthorizationFragment is hosting, which will prompt an Android dialog for permission to connect to the YubiKey.
Upon permission granted, when the user clicks "Sign in with certificate", a dialog is displayed that allows the user to pick from eligible PIV certificates store on the YubiKey.

Note: the YubiKey must be plugged in prior to clicking "Sign in with certificate" if the user wants to use their YubiKey to authenticate. Otherwise, the fallback is for the feature to look for user certificates located on the mobile device.

The user should select a certificate and click "Continue". The next dialog shows a textbox in which the user should enter their YubiKey PIN.

If the user enters an incorrect PIN, they will see an error message asking them to try again. If a user has 3 incorrect attempts in a row, they won't be able to attempt again until their key gets unlocked (most likely, the group that originally provisioned the certificates will be able to assist in unlocking).

Once they enter their correct PIN, the WebView should close, and the user should be authenticated.

Some error handling has been implemented to address situations such as:

User enters an incorrect PIN.

An error message appears under the (cleared) text box informing the user that they entered an incorrect PIN.

User enters, or has entered, an incorrect PIN 3 times in a row.

Whenever the user attempts to interact with the YubiKey (in this context), a dialog pops up informing them that they have made too many incorrect PIN attempts. The user will not be able to proceed with smartcard CBA.

User unplugs YubiKey in the middle of the dialog flow (after the "Sign in with certificate" button is clicked).

The current authentication flow is cancelled and a dialog pops up to inform the user that they will need to replugin their YubiKey in order to try again.

User has no PIV certificates on their YubiKey.

The current authentication flow is cancelled and a dialog pops up to inform the user that no PIV certificates were found on the YubiKey.

An exception is thrown during dialog flow relating to the YubiKey connection.

The current authentication flow is cancelled and a dialog pops up with a generic error message. The exception is logged and emitted as an ErrorEvent.

Sub-Branches

Pull Request
Summary of Additions/Changes
Notes

Melissaahn/yubi kit override integration by melissaahn · Pull Request #1729 · AzureAD/microsoft-authentication-library-common-for-android (github.com)
- keyboard and keyboardHidden added to configChanges of applicable activities within manifest.  - Override  for yubico.yubikit.android in order to clear error messages regarding the min sdk of Yubikit (19) being higher than ours (16).  - Basic use of YubiKit that shows detection of a YubiKey being plugged in. - Method added to WebviewAuthorizationFragment that stops the detection of YubiKey devices when the fragment is about to be destroyed.
- These changes were originally merged into dev but were later taken out to keep smartcard CBA work in its own feature branch until ready for GA.

Implementing Cert Picker and PIN Dialogs for Smartcard CBA by melissaahn · Pull Request #1751 · AzureAD/microsoft-authentication-library-common-for-android (github.com)
- xml layout files for cert picker, PIN dialog, and max attempts dialog created.- smartcard cert picker now pops up when "sign in with certificate" is clicked and YubiKey is already plugged in.- smartcard cert picker shows PIV certs on YubiKey and prompts user to choose.- PIN dialog prompts user to enter PIN. If incorrect, an error message tells the user to try again.-  If YubiKey is unplugged in the middle of the smartcard CBA dialog flow, the request is cancelled and an error dialog is shown.
- In short, this PR started up the UI for smartcard CBA.

Smartcard CBA Completed Flow by melissaahn · Pull Request #1766 · AzureAD/microsoft-authentication-library-common-for-android (github.com)
- YubiKit bumped up to 2.1.0-alpha.1, which brings in some classes (PivProvider and PivPrivateKey are notable) that allow smartcard CBA to finish.- The complete smartcard CBA flow now works. This involves adding a PivProvider instance in the Java Security static list of security providers.- max attempts error dialog is altered to become a generic error dialog that takes in strings as parameters. - DialogHolder class is created to manage the current dialog showing.- Some more string resources added for error messages.- Very simple telemetry started.
- In short, this PR got smartcard CBA to actually work.

Improving Telemetry In CBA Flows by melissaahn · Pull Request #1805 · AzureAD/microsoft-authentication-library-common-for-android (github.com)
- Telemetry is set up to report the statuses of PivProvider being added/removed/present in the Security static list of security providers.- Telemetry is set up for when CBA in general either succeeds or fails after we call proceed on the cert request from our side.- ErrorEvents are emitted when an unexpected exception is thrown.
- I'm more than willing to refactor this code when needed.

Adding Localization to Common by melissaahn · Pull Request #1807 · AzureAD/microsoft-authentication-library-common-for-android (github.com)
- Localizes Common.- Small change made to PIN dialog layout to ensure EditText types from right to left for right-to-left languages.
- PR sent to Authenticator: Pull request 6298556: Auth Client: Temporarily Adding Strings for Localization - Repos (visualstudio.com)- A good amount of the files added in this PR are a result of localization.

Bump YubiKit version to public 2.1.0 release by melissaahn · Pull Request #1808 · AzureAD/microsoft-authentication-library-common-for-android (github.com)
- YubiKit versions bumped to 2.1.0, which is considered to be a stable release. No breaking changes were observed.
- Release YubiKit 2.1.0 · Yubico/yubikit-android (github.com)

Added more precautions when handling PIN by melissaahn · Pull Request #1815 · AzureAD/microsoft-authentication-library-common-for-android (github.com)
- Instances where PIN is saved as a string were removed. PIN is set right away to a char array.- The PIN char array is cleared as soon as it is no longer needed on the client side.
- This PR was created recently, so it is not approved and merged yet.

Breaking Changes
Since YubiKeys are recognized as external keyboards on Android, a configuration change is detected when they are plugged in and unplugged from the device. The default response to this change is to restart the activity, which is unnecessary, and even harmful, in many cases. A simple fix is to add the flags keyboard and keyboardHidden to the configChanges attribute for every relevant (could be hosting when YubiKey is active) activity within the manifest. This fix was done for our libraries, but other apps may need to implement this change as well.
I created PRs for Authenticator and Company Portal that address the breaking change. I'm engaging with engineers on both teams to help explain why these changes need to be made.

Authenticator: Pull request 6551394: Adding YubiKit Library and Keyboard ConfigChanges for Smartcard CBA - Repos (visualstudio.com)
Company Portal: Pull request 6584465: Updated AndroidManifest.xml configChanges for smartcard CBA - Repos (visualstudio.com)

The broker release engineer for next month must take a commit after these PRs get merged for the RC builds.
For other apps that use MSAL, this breaking change and fix should be noted in the monthly announcement and wherever else it may be relevant.
Known Issues

In internal testing during private preview, a bug was found where the user was unable to see the soft keyboard when the YubiKey was plugged in. The issue occurred while testing with a tablet, and this behavior hasn't been reported by other testers thus far.

It's possible that "Show on screen keyboard" isn't checked under "Physical Keyboard" within settings. I'm waiting for the tester to check their settings.

In my own testing, the connection between the YubiKey and mobile device seems to not occur at times despite the user giving permission to connect. This results in the "Sign in with certificate" link leading to on-device certificates. I wouldn't consider it an issue that should block GA, since it happens very infrequently (which makes it difficult to debug) and it could vary among hardware devices, but it's worth noting.

Testing
Manual tests for a success scenario and two common failure scenarios (incorrect PIN and unplugging mid-dialog) were added under the Cert Based Auth folder in the master monthly test plan. I'm curious if I should create tests for 1p apps as well (for example, installing Authenticator and testing with production Outlook).
There could be some opportunities for automation that I still need to investigate. While I do think it would be valuable to at least manually plug in a YubiKey as a part of testing, the dialog steps that come afterwards could potentially be automated with the help of Robolectric Shadows. This ShadowUsbManager class could be interesting.
Private preview is currently in progress (with an apk that consumes a non-production version of YubiKit), but other than some internal testing, it doesn't seem that we will get too much feedback before GA. Yubico also has a copy of this apk and had some smaller followup questions regarding if NFC was implemented (it wasn't), if the apk contained the production version of YubiKit (it contains 2.1.0-alpha, as the apk was generated before 2.1.0 was released), and why they were seeing a server error if they clicked on "Sign in with a certificate" without a plugged in YubiKey (defaults to on-device, so device probably didn't have any applicable user certs).
I've created a successful apk of Authenticator with the feature. I'm investigating a small issue with Company Portal (it can't find new classes written in common4j..... but I have been given a potential commandline statement that could fix this issue).
Future Work

YubiKit SDK also offers methods that help connect to a YubiKey via NFC. Smartcard CBA with NFC is work that I expect to pick up next quarter, and it will require an altered design of the current CBA flow. For example, a dialog asking if the user wants to use NFC will probably need to appear in the case where no YubiKey is plugged in.
In the future, smartcard CBA will need to be extended to browsers as well, but this will most likely require some confirmation of initial work from eSTS before the feature can be started on the client side.

Thanks @rpdome for the review and approval. I've made changes in the latest commit that address some of the smaller comments (final, NonNull, removing some unnecessary comments).
Below is a list of things that need to be considered for future PRs:

Can we bump the min sdk to 19? Brought this up in the latest scrum and it seemed like there wasn't currently any opposition to this (maybe we can even bump it to 24 to be able to use more Java 8 features)
Extract YubiKit method calls into a separate abstract class that ClientCertAuthChallengeHandler can call so that YubiKit and the handler can be decoupled. This will help with rollbacks, if YubiKit has breaking changes in the future, and testing. (I'm going to start working on this right away)
Spots to emit telemetry should continually be considered,


Add initial support for Markdown based on reviews

In HTMLFile.cpp :

I have updated setHtmlBody function to find the syntax # in .md files.

In pgprogram.cpp :

I made a change in if/else statement to process .md files.

Please take a look at my pull request again. Thank you.

Thank you for your contribution!


Update README with missing links, and bit of a restructure

I found a few links were missing, and given how many repos we've grown to I proposed a bit of organization too.

Codecov Report

Merging #835 (a48b574) into main (3b112a5) will not change coverage.
The diff coverage is n/a.

:exclamation: Current head a48b574 differs from pull request most recent head 78e304b. Consider uploading reports for the commit 78e304b to get more accurate results

@@            Coverage Diff            @@
##              main      #835   +/-   ##
=========================================
  Coverage   100.00%   100.00%
=========================================
  Files          299       299
  Lines        19457     19457
=========================================
  Hits         19457     19457

Continue to review full report at Codecov.

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


tests-ci : portability: posix: common.newlib test Failed

Describe the bug
common.newlib test is Failed on zephyr-v3.4.0-3926-g4ba97c22555e on mimxrt1060_evk
testcase path is portability/posix/common/newlib/nanosleep_execution
see logs for details
To Reproduce
1.
scripts/twister --device-testing --device-serial /dev/ttyACM0 -p mimxrt1060_evk  --sub-test portability.posix

or
# cd tests/portability/posix/common/newlib/nanosleep_execution
# west build -b mimxrt1060_evk
# west flash

See error

Expected behavior
test pass
Impact
Logs and console output
START - test_nanosleep_execution

Assertion failed at WEST_TOPDIR/zephyr/tests/posix/common/src/nanosleep.c:153: common_lower_bound_check: (actual_ns >= exp_ns is false)
actual: 93904 expected: 500000000
FAIL - test_nanosleep_execution in 0.016 seconds

Environment (please complete the following information):

OS: (e.g. Linux )
Toolchain (e.g Zephyr SDK)
Commit SHA or Version used: zephyr-v3.4.0-3926-g4ba97c22555e

related: #62889

@mmahadevan108 there is a set of issues that seem potentially related.

does not reproduce on latest main


Permission denied @ rb_sysopen - /srv/jekyll/_site/index.html

Tried to follow the directions for running with Docker.
This is with the demo Jupyter Book, no edits.
The build appeared to run correctly. But the following permission error occurs:
ceteri@juptyer:~/src/RSDRD_book/rsdrd$ sudo docker run --rm --security-opt label:disable     -v /home/ceteri/src/RSDRD_book/rsdrd:/srv/jekyll    -p 4000:4000    -it -u 1000:1000    emdupre/jupyter-book bundle exec jekyll serve --host <IP_ADDRESS>
Configuration file: /srv/jekyll/_config.yml
            Source: /srv/jekyll
       Destination: /srv/jekyll/_site
 Incremental build: disabled. Enable with --incremental
      Generating...
       Jekyll Feed: Generating feed for posts
jekyll 3.7.4 | Error:  Permission denied @ rb_sysopen - /srv/jekyll/_site/index.html

Thanks for reporting, I'll give it a shot with Docker as well and see if I run into the same issues.

Hey all - I'm gonna close this one as we've updated the docker image now, but please ping if there's still something wrong!


yarn buildpack dependency fix

There is an apparent dependency issue with yarn buildpack
On a simple repo with yarn.lock, it fails and yarn.lock is ignored. This leads to another buildpack group (with npm) to take over the build.
Result is that whether or not yarn.lock is present, application is always built using npm.
Some pack output demonstrating the issue:
✦ ❯❯❯ pack build -v small-yarn -b heroku/nodejs-engine -b heroku/nodejs-yarn
Builder cr.nrtn.dev/heroku/buildpacks:b8c5d04e is trusted
Pulling image cr.nrtn.dev/heroku/buildpacks:b8c5d04e
b8c5d04e: Pulling from heroku/buildpacks
Digest: sha256:79b3131b2f67bce8030fe1824574e4d37d24a7da365233681b65fbc904f2baf4
Status: Image is up to date for cr.nrtn.dev/heroku/buildpacks:b8c5d04e
Selected run image cr.nrtn.dev/infra/pack:20
Pulling image cr.nrtn.dev/infra/pack:20
20: Pulling from infra/pack
Digest: sha256:f774b9e6c779c6e7e168ae5b01eb8f78f393dcc8d02ba88eb22e2e5697f31a5e
Status: Image is up to date for cr.nrtn.dev/infra/pack:20
Setting custom order
Creating builder with the following buildpacks:
-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>-><EMAIL_ADDRESS>Using build cache volume pack-cache-library_small-yarn_latest-7623b5239096.build
Running the creator on OS linux with:
Container Settings:
  Args: /cnb/lifecycle/creator -daemon -launch-cache /launch-cache -log-level debug -cache-dir /cache -run-image cr.nrtn.dev/infra/pack:20 -process-type web small-yarn
  System Envs: CNB_PLATFORM_API=0.4
  Image: pack.local/builder/6e617364706f77646c74:latest
  User: root
  Labels: map[author:pack]
Host Settings:
  Binds: pack-cache-library_small-yarn_latest-7623b5239096.build:/cache /var/run/docker.sock:/var/run/docker.sock pack-cache-library_small-yarn_latest-7623b5239096.launch:/launch-cache pack-layers-fmxwuijyaj:/layers pack-app-qbkxereudo:/workspace
  Network Mode:
===> DETECTING
======== Results ========
pass<EMAIL_ADDRESS>pass<EMAIL_ADDRESS>Resolving plan... (try #1)
fail<EMAIL_ADDRESS>provides unused node
ERROR: No buildpack groups passed detection.
ERROR: Please check that you are running against the correct path.
ERROR: failed to detect: no buildpacks participating
ERROR: failed to build: executing lifecycle: failed with status code: 100

Without specific buildpacks and using full set, the group with npm takes over after this issue.
This pull request adds plan dependency on node similar to npm buildpack, that allows yarn to succeed in detection

switched to branch, amended commit message, closing this in favour of another one


Error when installing from script: unknown tool /usr/local/gcc-13.0.0-dev/bin/gcc-13.0.0-dev

Xmake Version
v2.7.5+202301221546
Operating System Version and Architecture
Fedora 38 (WSL2)
Describe Bug
I have in my PATH the following, from source-built GCC:
export PATH=/usr/local/gcc-13.0.0-dev/bin:$PATH
export LD_LIBRARY_PATH=/usr/local/gcc-13.0.0-dev/lib64:$LD_LIBRARY_PATH

# To let CMake know
export CC=/usr/local/gcc-13.0.0-dev/bin/gcc-13.0.0-dev
export CXX=/usr/local/gcc-13.0.0-dev/bin/g++-13.0.0-dev

If I run the install script:
bash <(curl -fsSL https://xmake.io/shget.text)

I get:
downloading<EMAIL_ADDRESS>..
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 1800k  100 1800k    0     0  4763k      0 --:--:-- --:--:-- --:--:-- 4775k
Creating directory /tmp/.xmake_getter30512
Verifying archive integrity...  100%    100%   All good.
Uncompressing xmake-v2.7.5-runfile  100%
checking for platform ... linux
checking for architecture ... x86_64
checking for make ... ok
unknown tool /usr/local/gcc-13.0.0-dev/bin/gcc-13.0.0-dev
configure failed!

It's not a big deal, removing source-built GCC fixes it, but just wanted to let you know =)
Expected Behavior
It works
Project Configuration
No response
Additional Information and Error Logs
No response

I have fixed it on dev.
bash <(curl -fsSL https://xmake.io/shget.text) dev


Default location for configs

2 parts here: client configs and server configs.
We should just default to default application data directory on each platform (e.g. $XDG_CONFIG_HOME on linux).
Client directory might want to have multiple sub-directories for each federation it's a member of.

Old and stale. I think what we're doing now is OK, and I don't recall complains. I'm not sure if default location is really all that useful for a tool like this.


ReactNative - Analytics changes

Description
We need to make sure all analytics libraries are properly working for react native. In doing so we might need to test some of the current implementation and in other cases we need to migrate to the corresponding npm packages.
Plan of attack (by priorities)

Amplitude -> move to npm package, should work cross-platform
Sentry -> test and make sure works cross-platform using sentry/react-native
FullStory, Mautic & GoogleAnalytics -> all imported from window, should be moved out for react-native

Tasks done

[x] Amplitude
[ ] Sentry
[ ] FullStory
[ ] Mautic
[ ] Google Analytics

@MathiasMoralesDixtra Here's the updated ticket for analytics, feel free to let me know if more details need to be added.
Lets have individual PRs for each one of the points of the plan of attack and as we've been speaking points 1 & 2 are top priorities, 3 medium, 4 super low.

https://help.fullstory.com/hc/en-us/articles/360052419133-Getting-Started-with-FullStory-React-Native-Recording
no need for mautic
google analytics is required used just once in claim queue
I suggest a separate issue for fullstory

https://help.fullstory.com/hc/en-us/articles/360052419133-Getting-Started-with-FullStory-React-Native-Recording
no need for mautic
google analytics is required used just once in claim queue
I suggest a separate issue for fullstory

Thank you for the suggestions, I have the same opinion about FullStory. We came to the same library to implement on Native.

@MathiasMoralesDixtra Updated issue - removed mautic and fullstory moved to separate issue #2309


Cannot build go flyway

hello sir i have this error when i try github.com/coyove/tcpmux
goworkspace/src/github.com/coyove/tcpmux/dial.go:24:4: undefined: rand.Rand
Sir is it possible to give binary release for 32 bit linux please

goflyway: git checkout gdev

Sir is it possible to give me Binary release of 32 bit linux kindly

Please goto releases and find what you want.


Annotations should be available for Enum.Case.

Hi everyone!
As of version 0.4.3, annotations are available for types and variables, but not for cases of enum's.
I think it would be very nice to have access to annotations for enum cases.
For example, I'm trying to wrap localized strings in some custom MyLocalizable structs and starting from
enum Localizable {
    enum Category {
        /// sourcery comment = "Some comment"
        case someKey = "Default value"
    }
}

I would like to generate
struct Localizable {
    struct Category {
        static let someKey = MyLocalizable(key: "Localizable.Category.someKey", default: "Default value", comment: "Some comment")
    }
}

Please note that the enum is not part of the project. It is used only by Sourcery to generate code.
MyLocalizable has a string var that returns the localized string and I can then simply use Localizable.Category.someKey.string. where I need to. The Localizable.strings files can easily be generated from Sourcery too.
With the current version, the best I can do is to use a struct instead of an enum:
struct Localizable {
    struct Category {
        /// sourcery comment = "Some comment"
        /// sourcery default = "Default value"
        let someKey: String
    }
}

Here, I need to use another comment for the default since one doesn't have the rawValue anymore. Furthermore, I need to specify the type of key, even if I'm not using it after. This is not as optimal as the enum case.
An alternative solution would be to give access to literal values of variables when they have some. For example, for the variable let foo = "bar" could maybe have a literalValue property returning "bar".

Makes total sense to me, I'll enable annotation for cases today, should be very straighforward 👍

@RabugenTom available in 0.4.4


Train on cpu

Does mmdetection support train models on CPU (my computer does not have GPU and cuda)? How shouild I config if it support, thx a lot!!!

I think this is what you want:
https://mmdetection.readthedocs.io/en/latest/install.html#install-with-cpu-only

Training with CPU is currently not supported. Inference with CPU is okay.

Are there any updates on this? When I try to do training on the CPU, I get the error batch_size should be a positive integeral value, but got batch_size=0. Is it still not supported?


ASP NET Core and EntityFramework6 after upgrade to VS 2017 faling with exception

Hello
I know that is probably not directly related but maybe you can point me how to solve the issue.
On one computer all is working on the other not. Reverting application to VS 2015 solves the issue.
Other methods with EF working. Only one not.
The exception we have is:
 System.NullReferenceException: Object reference not set to an instance of an object.    at System.Data.Entity.Internal.Linq.InternalSet1.get_Expression()
at System.Data.Entity.Infrastructure.DbQuery1.System.Linq.IQueryable.get_Expression()    at System.Data.Entity.QueryableExtensions.FirstOrDefaultAsync[TSource](IQueryable1 source, Expression1 predicate, CancellationToken cancellationToken)    at System.Data.Entity.QueryableExtensions.FirstOrDefaultAsync[TSource](IQueryable1 source, Expression1 predicate)    at SyncService.<Sync>d__1.MoveNext()

EF Team Triage: This issue is lacking enough information for us to be able to effectively triage it. In particular, it is missing the following information requested in the new issue template. Can you please provide this information?

Steps to reproduce

Ideally include a complete code listing that we can run to reproduce the issue.
Alternatively, you can provide a project/solution that we can run.
BTW we're not just doing this to be mean :smile:... we get a lot traffic on this project and it takes time to attempt to reproduce an issue based on fragments of information. In addition, our attempt is often unsuccessful as the exact conditions required to hit the issue are often not explicitly included in the code provided. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we ask that folks give us a self-contained way to reproduce an issue.
For a guide on submitting good bug reports, read Painless Bug Tracking.
BTW this is a canned response and may have info or details that do not directly apply to this particular issue. While we'd like to spend the time to uniquely address every incoming issue, we get a lot traffic on the EF projects and that is not practical. To ensure we maximize the time we have to work on fixing bugs, implementing new features, etc. we use canned responses for common triage decisions.

That is a problem, this issue is strange. It occurs on one computer, and not on other. Also it is not occurring every time, only on one method, other application using ef 6 and connecting to the same db is working. Just wondered if you can point me were to look for problem.

@msmolka From just the information provided I don't have any ideas on what the problem is or where to look for it. I would start by looking at what is different between the code/machines where it works and where it doesn't.

The funny thing is all is working in asp core vs2015 but not after migrate to vs2017

It is stranger and stranger. I've downgraded version EF all worked properly then upgraded again and now all is working.


Release version 3.0.0

Questions
Answers

Description?
Release version 3.0.0

Type?

BC breaks?

Deprecations?

Fixed ticket?

How to test?

@florine2623 Just a quick test, we just tested it. ;-)


⚠ Secret Website 2 has degraded performance

In be8176b, Secret Website 2 ($SECRET_WEBSITE_2) experienced degraded performance:

HTTP code: 200
Response time: 7977 ms

Resolved: Secret Website 2 performance has improved in e216438.


Config, Documentation: Correctly format "rocksdb.info-log-roll-time" default config value

Signed-off-by: abbccdda<EMAIL_ADDRESS>Problem Summary:
The default config written on the RocksDB configuration intro page https://github.com/tikv/tikv/blob/master/docs/reference/configuration/rocksdb-option-config.md would fail to build as:
thread  'main' panicked at 'invalid auto generated configuration file mac_tikv.conf, err valid duration, only d, h, m, s, ms are supported. for key `rocksdb.info-log-roll-time`', /Users/boyang.chen/.rustup/toolchains/nightly-2020-07-01-x86_64-apple-darwin/lib/rustlib/src/rust/src/libstd/macros.rs:16:9

The reason is that for a time config info-log-roll-time, its value must end with a unit. Adding s to all the recommended config values and verified the build work.
What's Changed:
Ensure the configuration value for info-log-roll-time always ends with seconds unit.
Tests

Not applicable

Side effects

No

@youjiali1995 @nrc  Could you take a look?

/merge

@abbccdda Thanks.


fixed typos in backup.rst file

Summary
fixed typos in backup.rst file

Thanks, @fakela, this is a great catch! I have added one suggestion - let me know what you think and then I think this is good to merge.

@justinegeffen thanks it's looks good I have committed the suggestions

I picked up two minor edits which I've committed and this looks good to go. Thanks, @fakela! :)


Searching value of XCOM is broken

Go to Admin > XComs and search for a value, also filtering by task ID, such as:

Click Search and you get an Airlfow "Oops something went wrong" page. Here is the stacktrace from the log:
[2024-11-05T17:05:29.460+0000] {app.py:1744} ERROR - Exception on /xcom/list/ [GET]
Traceback (most recent call last):
  File "/home/airflow/.local/lib/python3.11/site-packages/flask/app.py", line 2529, in wsgi_app
    response = self.full_dispatch_request()
               ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/airflow/.local/lib/python3.11/site-packages/flask/app.py", line 1825, in full_dispatch_request
    rv = self.handle_user_exception(e)
         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/airflow/.local/lib/python3.11/site-packages/flask/app.py", line 1823, in full_dispatch_request
    rv = self.dispatch_request()
         ^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/airflow/.local/lib/python3.11/site-packages/flask/app.py", line 1799, in dispatch_request
    return self.ensure_sync(self.view_functions[rule.endpoint])(**view_args)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/airflow/.local/lib/python3.11/site-packages/flask_appbuilder/security/decorators.py", line 137, in wraps
    return f(self, *args, **kwargs)
           ^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/airflow/.local/lib/python3.11/site-packages/flask_appbuilder/views.py", line 550, in list
    widgets = self._list()
              ^^^^^^^^^^^^
  File "/home/airflow/.local/lib/python3.11/site-packages/flask_appbuilder/baseviews.py", line 1179, in _list
    widgets = self._get_list_widget(
              ^^^^^^^^^^^^^^^^^^^^^^
  File "/home/airflow/.local/lib/python3.11/site-packages/flask_appbuilder/baseviews.py", line 1078, in _get_list_widget
    count, lst = self.datamodel.query(
                 ^^^^^^^^^^^^^^^^^^^^^
  File "/home/airflow/.local/lib/python3.11/site-packages/flask_appbuilder/models/sqla/interface.py", line 489, in query
    count = self.query_count(query, filters, select_columns)
            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/airflow/.local/lib/python3.11/site-packages/flask_appbuilder/models/sqla/interface.py", line 398, in query_count
    ).count()
      ^^^^^^^
  File "/home/airflow/.local/lib/python3.11/site-packages/sqlalchemy/orm/query.py", line 3176, in count
    return self._from_self(col).enable_eagerloads(False).scalar()
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/airflow/.local/lib/python3.11/site-packages/sqlalchemy/orm/query.py", line 2893, in scalar
    ret = self.one()
          ^^^^^^^^^^
  File "/home/airflow/.local/lib/python3.11/site-packages/sqlalchemy/orm/query.py", line 2870, in one
    return self._iter().one()
           ^^^^^^^^^^^^
  File "/home/airflow/.local/lib/python3.11/site-packages/sqlalchemy/orm/query.py", line 2916, in _iter
    result = self.session.execute(
             ^^^^^^^^^^^^^^^^^^^^^
  File "/home/airflow/.local/lib/python3.11/site-packages/sqlalchemy/orm/session.py", line 1717, in execute
    result = conn._execute_20(statement, params or {}, execution_options)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/airflow/.local/lib/python3.11/site-packages/sqlalchemy/engine/base.py", line 1710, in _execute_20
    return meth(self, args_10style, kwargs_10style, execution_options)
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/airflow/.local/lib/python3.11/site-packages/sqlalchemy/sql/elements.py", line 334, in _execute_on_connection
    return connection._execute_clauseelement(
           ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/home/airflow/.local/lib/python3.11/site-packages/sqlalchemy/engine/base.py", line 1577, in _execute_clauseelement
    ret = self._execute_context(
          ^^^^^^^^^^^^^^^^^^^^^^
  File "/home/airflow/.local/lib/python3.11/site-packages/sqlalchemy/engine/base.py", line 1953, in _execute_context
    self._handle_dbapi_exception(
  File "/home/airflow/.local/lib/python3.11/site-packages/sqlalchemy/engine/base.py", line 2138, in _handle_dbapi_exception
    util.raise_(exc_info[1], with_traceback=exc_info[2])
  File "/home/airflow/.local/lib/python3.11/site-packages/sqlalchemy/util/compat.py", line 211, in raise_
    raise exception
  File "/home/airflow/.local/lib/python3.11/site-packages/sqlalchemy/engine/base.py", line 1910, in _execute_context
    self.dialect.do_execute(
  File "/home/airflow/.local/lib/python3.11/site-packages/sqlalchemy/engine/default.py", line 736, in do_execute
    cursor.execute(statement, parameters)
TypeError: can't escape str to binary
<IP_ADDRESS> - - [05/Nov/2024:17:05:29 +0000] "GET /xcom/list/?_flt_0_task_id=add_marc_tags_to_record&_flt_3_value=False HTTP/1.1" 500 1585 "https://sul-libsys-airflow-prod.stanford.edu/xcom/list/?_flt_0_task_id=add_marc_tags_to_record&_oc_XComModelView=value&_od_XComModelView=asc" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.1 Safari/605.1.15"
<IP_ADDRESS> - - [05/Nov/2024:17:05:29 +0000] "GET /favicon.ico HTTP/1.1" 404 462 "https://sul-libsys-airflow-prod.stanford.edu/xcom/list/?_flt_0_task_id=add_marc_tags_to_record&_flt_3_value=False" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_15_7) AppleWebKit/605.1.15 (KHTML, like Gecko) Version/18.1 Safari/605.1.15"

What environment is this error occurring? I think it may fixed in the latest main branch as I can't replicate the error either locally or on airflow-dev.

This was in prod. I've also seen it in stage and dev last week but maybe now it's fixed.

Also a problem in 2.9.3 and 2.10.1 (Jeremy replicated in ILS-MiddleWare)

Waiting for fix in upstream.


RuntimeError: Given input size: (512x2x3). Calculated output size: (512x0x0). Output size is too small

I get an Error when executing your Testexample:
python main_joint.py --mode test --clm_model ./model/joint/clm_final.pth  --fsm_model ./model/joint/fsm_final.pth --test_fold ./testRes --sal_mode t
I am running Windows 10 with Cuda 10.1 and Torch 1.7.1
Traceback (most recent call last):
  File "main_joint.py", line 282, in <module>
    main(config)
  File "main_joint.py", line 229, in main
    test.test()
  File "C:\Users\Seppi\Desktop\MobulaOP\Locate-Globally-Segment-locally-A-Progressive-Architecture-With-Knowledge-Review-Network-for-SOD\Solver_joint.py", line 84, in test
    feasum_out, merge_solid, out_merge_solid1, out_merge_solid2, out_merge_solid3, out_merge_solid4 = self.net(images)
  File "C:\Users\Seppi\AppData\Local\Programs\Python\Python38\lib\site-packages\torch\nn\modules\module.py", line 727, in _call_impl
    result = self.forward(*input, **kwargs)
  File "C:\Users\Seppi\Desktop\MobulaOP\Locate-Globally-Segment-locally-A-Progressive-Architecture-With-Knowledge-Review-Network-for-SOD\KRN.py", line 155, in forward
    merge_solid1 = self.DeepPool_solid1(conv2merge[0], conv2merge[1])
  File "C:\Users\Seppi\AppData\Local\Programs\Python\Python38\lib\site-packages\torch\nn\modules\module.py", line 727, in _call_impl
    result = self.forward(*input, **kwargs)
  File "C:\Users\Seppi\Desktop\MobulaOP\Locate-Globally-Segment-locally-A-Progressive-Architecture-With-Knowledge-Review-Network-for-SOD\KRN.py", line 54, in forward
    y = self.convs[i](self.pools[i](y))
  File "C:\Users\Seppi\AppData\Local\Programs\Python\Python38\lib\site-packages\torch\nn\modules\module.py", line 727, in _call_impl
    result = self.forward(*input, **kwargs)
  File "C:\Users\Seppi\AppData\Local\Programs\Python\Python38\lib\site-packages\torch\nn\modules\pooling.py", line 594, in forward
    return F.avg_pool2d(input, self.kernel_size, self.stride,
RuntimeError: Given input size: (512x2x3). Calculated output size: (512x0x0). Output size is too small

I am using the DUTS-TE Dataset for testing like in your example, shouldn't that work? Looking at the sizes they all seems to be around 300x400 Pixel

Switching the Images with higher resolution one seems to solve the issue, sadly my GPU seems to be to low on Memory.
I get the following Error
RuntimeError: CUDA out of memory. Tried to allocate 264.00 MiB (GPU 0; 6.00 GiB total capacity; 4.18 GiB already allocated; 0 bytes free; 4.57 GiB reserved in total by PyTorch)
Is there a minimum requirement?

I get an Error when executing your Testexample:
python main_joint.py --mode test --clm_model ./model/joint/clm_final.pth --fsm_model ./model/joint/fsm_final.pth --test_fold ./testRes --sal_mode t
I am running Windows 10 with Cuda 10.1 and Torch 1.7.1
Traceback (most recent call last):
  File "main_joint.py", line 282, in <module>
    main(config)
  File "main_joint.py", line 229, in main
    test.test()
  File "C:\Users\Seppi\Desktop\MobulaOP\Locate-Globally-Segment-locally-A-Progressive-Architecture-With-Knowledge-Review-Network-for-SOD\Solver_joint.py", line 84, in test
    feasum_out, merge_solid, out_merge_solid1, out_merge_solid2, out_merge_solid3, out_merge_solid4 = self.net(images)
  File "C:\Users\Seppi\AppData\Local\Programs\Python\Python38\lib\site-packages\torch\nn\modules\module.py", line 727, in _call_impl
    result = self.forward(*input, **kwargs)
  File "C:\Users\Seppi\Desktop\MobulaOP\Locate-Globally-Segment-locally-A-Progressive-Architecture-With-Knowledge-Review-Network-for-SOD\KRN.py", line 155, in forward
    merge_solid1 = self.DeepPool_solid1(conv2merge[0], conv2merge[1])
  File "C:\Users\Seppi\AppData\Local\Programs\Python\Python38\lib\site-packages\torch\nn\modules\module.py", line 727, in _call_impl
    result = self.forward(*input, **kwargs)
  File "C:\Users\Seppi\Desktop\MobulaOP\Locate-Globally-Segment-locally-A-Progressive-Architecture-With-Knowledge-Review-Network-for-SOD\KRN.py", line 54, in forward
    y = self.convs[i](self.pools[i](y))
  File "C:\Users\Seppi\AppData\Local\Programs\Python\Python38\lib\site-packages\torch\nn\modules\module.py", line 727, in _call_impl
    result = self.forward(*input, **kwargs)
  File "C:\Users\Seppi\AppData\Local\Programs\Python\Python38\lib\site-packages\torch\nn\modules\pooling.py", line 594, in forward
    return F.avg_pool2d(input, self.kernel_size, self.stride,
RuntimeError: Given input size: (512x2x3). Calculated output size: (512x0x0). Output size is too small

I encountered the same problem, have you solved it?

Switching the Images with higher resolution one seems to solve the issue, sadly my GPU seems to be to low on Memory.
I get the following Error
RuntimeError: CUDA out of memory. Tried to allocate 264.00 MiB (GPU 0; 6.00 GiB total capacity; 4.18 GiB already allocated; 0 bytes free; 4.57 GiB reserved in total by PyTorch)
Is there a minimum requirement?

NVIDIA 2080Ti with 11G can work.

I get an Error when executing your Testexample:
python main_joint.py --mode test --clm_model ./model/joint/clm_final.pth --fsm_model ./model/joint/fsm_final.pth --test_fold ./testRes --sal_mode t
I am running Windows 10 with Cuda 10.1 and Torch 1.7.1
Traceback (most recent call last):
  File "main_joint.py", line 282, in <module>
    main(config)
  File "main_joint.py", line 229, in main
    test.test()
  File "C:\Users\Seppi\Desktop\MobulaOP\Locate-Globally-Segment-locally-A-Progressive-Architecture-With-Knowledge-Review-Network-for-SOD\Solver_joint.py", line 84, in test
    feasum_out, merge_solid, out_merge_solid1, out_merge_solid2, out_merge_solid3, out_merge_solid4 = self.net(images)
  File "C:\Users\Seppi\AppData\Local\Programs\Python\Python38\lib\site-packages\torch\nn\modules\module.py", line 727, in _call_impl
    result = self.forward(*input, **kwargs)
  File "C:\Users\Seppi\Desktop\MobulaOP\Locate-Globally-Segment-locally-A-Progressive-Architecture-With-Knowledge-Review-Network-for-SOD\KRN.py", line 155, in forward
    merge_solid1 = self.DeepPool_solid1(conv2merge[0], conv2merge[1])
  File "C:\Users\Seppi\AppData\Local\Programs\Python\Python38\lib\site-packages\torch\nn\modules\module.py", line 727, in _call_impl
    result = self.forward(*input, **kwargs)
  File "C:\Users\Seppi\Desktop\MobulaOP\Locate-Globally-Segment-locally-A-Progressive-Architecture-With-Knowledge-Review-Network-for-SOD\KRN.py", line 54, in forward
    y = self.convs[i](self.pools[i](y))
  File "C:\Users\Seppi\AppData\Local\Programs\Python\Python38\lib\site-packages\torch\nn\modules\module.py", line 727, in _call_impl
    result = self.forward(*input, **kwargs)
  File "C:\Users\Seppi\AppData\Local\Programs\Python\Python38\lib\site-packages\torch\nn\modules\pooling.py", line 594, in forward
    return F.avg_pool2d(input, self.kernel_size, self.stride,
RuntimeError: Given input size: (512x2x3). Calculated output size: (512x0x0). Output size is too small

I encountered the same problem, have you solved it?

Could you print the shape and path of your input image? Make sure they are right.

I change datasets, and train these code, also have this problem!

I re-tested the code and I think I may have found the problem. I encountered the same problem "RuntimeError: Given input size: (512x2x3). Calculated output size: (512x0x0). Output size is too small" with Pytorch 1.6.0, but it can work with Pytorch 1.0.0.
Using a high version of Pytorch may cause this problem, so try a lower version.

It seems the DeepPoolLayer_first is similar to the fam in poolnet. In the forward process of the DeepPoolLayer_first, a feature map is subsampled by a factor of 2, 4, and 8, successively. However, in the original poolnet repo., the three subsampling operations are conducted separatedly, i.e. y=self.convsi. Is it a typo?

After rechecking the code and paper, I believe that the error is caused by a typo. The   self.pools_sizes = [2, 4, 8] should be  changed into        self.pools_sizes = [2, 2, 2].

Thanks a lot, I will try your method!
------------------ 原始邮件 ------------------
发件人:                                                                                "bradleybin/Locate-Globally-Segment-locally-A-Progressive-Architecture-With-Knowledge-Review-Network-for-SOD"                                                                                @.>;
发送时间: 2021年7月2日(星期五) 晚上10:02
@.>;
<EMAIL_ADDRESS>主题: Re: [bradleybin/Locate-Globally-Segment-locally-A-Progressive-Architecture-With-Knowledge-Review-Network-for-SOD] RuntimeError: Given input size: (512x2x3). Calculated output size: (512x0x0). Output size is too small (#1)
After rechecking the code and paper, I believe that the error is caused by a typo. The   self.pools_sizes = [2, 4, 8] should be  changed into        self.pools_sizes = [2, 2, 2].
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

After rechecking the code and paper, I guess that the error is caused by a typo. The  self.pools_sizes = [2, 4, 8] should be changed into self.pools_sizes = [2, 2, 2]. However, after modifing the code, the genearetd results are still different from the provided saliency maps.
For example, these two results are slightly different.

(provided saliency map)

(generated saliency map)

非常感谢你关注我们的工作并发现了我们代码中关键的错误。确实由于我们的粗心，这个地方出现了你说的问题，我们将会马上纠正这个错误。
我们提供的saliency maps和我们提供的训练好的模型出来的结果的确不一样。我们提供的预测saliency maps是我们论文中使用的那个版本（论文里的实验结果都是基于我们提供的这个显著性图），我们提供它也是为了方便接下来的工作和我们的工作比较。但是这个结果是我们比较早期训练出来的，所用的代码比较粗糙。为了方便大家更好理解我们的工作，我们就写了这个当前所公开的代码。不过，我们提供的训练好的模型测试结果出来的结果是近似甚至略好于我们提供的saliency maps。
另外，我们近期会基于纠正后的代码重新训练一遍，然后放上来的。
<EMAIL_ADDRESS>

您客气了，我也从您的论文和代码中受到了一些启发，感谢您能够公布自己的代码~


Fixed crash when removing some shortcuts from Editor Settings

Refactor of #51813
Fixes: #51794

@jmb462
I fixed the crash issue when opening the project

I did it! (first time using interactive rebase)

Issue issue is no longer reproducible, it appears issue has been fixed inadvertently in a another change.


Improve monomorphization implementation

Is this intended to supersede #820? It looks like the code changes are similar.


Makes chai-iterator compatible with chai 4; closes #12

This is a breaking change.
Applying either 18246bb or cc0cab6 by itself causes tests to fail.
Mergin this pr would require bumping npm to version 2.

@TimothyGu I have done :)

@harrysarson Thanks!

hi, guys! @harrysarson thnk you for package https://www.npmjs.com/package/@harrysarson/chai-iterator
but does anybody know will be this package updated here(https://www.npmjs.com/package/chai-iterator)?

Hi @iamsimakov, I have reached out to @mcmath by email as described in https://docs.npmjs.com/misc/disputes about three weeks ago.
I haven't yet heard anything back so I am hoping that folk at npm might be able to transfer ownership. Once that happens I will release version 2 of chai-iterator with these updates.

@iamsimakov I have released version 3.0.0 of chai-iterator.

@harrysarson thanks

Does it work ok for you?

@harrysarson I'm sorry but I can not check this version now, I will try it few days later, thanks


fix(gif): revert GIF

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

npm package (@latest dist-tag)
GitHub release

Your semantic-release bot :package::rocket:


[BUG]  Custom Roblox Sound Effects are way too low in volume, or the music is too loud.

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.
[ ] My answer given in the checkbox above is a lie.

What problem did you encounter?
What i encountered is that the sound effects arent playing anymore on my side, but work for others, and they barely work and barely have any volume. I cannot fix this and someone said they fixed it, BUT THEY NEVER SAID HOW THEY FIXED IT, which is why I want to know HOW to FIX it. I have done everything to try and fix it, it doesnt fix.

NVM I FIXED IT BY ENABLING SPATIAL SOUND LOL


Oncotree mappings at the tissue level

I have been looking at the Oncotree resource and noticed that MONDO provides xrefs to it. Oncotree is organized in a way that at the top level, it lists tissues (e.g., LUNG, PANCREAS, etc.) and all descendent terms are types of cancer (e.g., LUAD, PAAD). These tissue-level entries create a bit of a confusing situation in terms of mappings to MONDO, for instance (line numbers included):
468005 [Term]
468006 id: MONDO:0021117
468007 name: lung neoplasm
468008 def: "A benign or malignant, primary or metastatic neoplasm involving the lungs. Representative examples of benign                 neoplasms include adenoma, papilloma, chondroma, and endobronchial lipoma. Representative examples of malignant neoplasms          include carcinoma, carcinoid tumor, sarcoma, and lymphoma."  But the fact that ONCOTREE:LUNG is a tissue, not a cancer type results in a conflict in terms of NCIT mappings:
xref: NCIT:C12468 {source="ONCOTREE:LUNG"}
xref: NCIT:C3200 {source="MONDO:equivalentTo"}

where NCIT:C12468 is just "lung" and NCIT:C3200 is "lung neoplasm".
My question is, is this way of representing ONCOTREE tissue-level entries intentional or should e.g. ONCOTREE:LUNG {source="MONDO:equivalentTo"} be changed to a different type of relationship? If it is intentional, I will figure out how to resolve the xref issues, just want to make sure!

TL;DR - it looks like you are using the mondo-edit file. In all release artefacts this should not be there
xref: NCIT:C12468 {source="ONCOTREE:LUNG"}
but either way we should make the edit file less confusing and clarify if and how MONDO:0021117   should be mapped to oncotree
AFAICR the oncotree tissue terms could be interpreted in 2 ways

as tissues with equivalents in UBERON
as neoplasm terms that are labeled as tissue terms

The paper leaves in IMO open:
"its root node represents a tissue and the branches and leaves include different histological and genomic subclassifications"
However, if Oncotree is already mapped to NCIT tissues then this points to 1.
1 is a little less practical as it divides the mapping task across two ontologies, OR forces us to use an odd way of representing the non-equivalent cognate term.
If we want to stick with 2, we want to eliminate the erroneous propagated xrefs to NCIT (they are already blocked from the release but their presence in the edit files does no good and could confuse us internally)

Hi @cmungall! Thanks, that all makes sense.

Yes, I've been looking at mondo-edit.obo, and didn't realize that the release would be different in this regard, that's good to know.
I agree that an interpretation of Oncotree where top level terms represent "cancer originating in [TISSUE]" would make sense, but given their mappings to NCIT tissue terms, it seems like the intended interpretation is "[TISSUE] of origin".


Fix deps for 0.4.0, add tests, pip check, maintainer collective

Checklist

[x] Used a personal fork of the feedstock to propose changes
[x] Bumped the build number (if the version is unchanged)
[ ] Reset the build number to 0 (if the version changed)
[x] Re-rendered with the latest conda-smithy (Use the phrase @conda-forge-admin, please rerender in a comment in this PR for automated rerendering)
[x] Ensured the license file is being packaged.

References:

blocks https://github.com/conda-forge/jupyterlab-feedstock/pull/350/

Notes:

add jupyter_server_fileid
adds the @conda-forge/jupyter_server group as maintainers
runs the test suite and pip check

Hi! This is the friendly automated conda-forge-linting service.
I just wanted to let you know that I linted all conda-recipes in your PR (recipe) and found it was in an excellent condition.

@conda-forge-admin please rerender

@conda-forge/jupyter_server_ydoc ready for review


Fast fail on impossible year scenarios

With all other fields other than year, it makes sense to continue iterating in either direction, since the values of everything other than year eventually repeat. With year, however, we can easily end up iterating @max_runs in many common scenarios, such as:
 ~e[1 2 3 4 5 * 2010]e |> Crontab.Scheduler.get_next_run_date

If done inside a hot loop, this can become a very expensive operation. While we can't totally eliminate these cases, we can detect them in the case of simple single-year lookups and fail quickly without having to run out the @max_runs clock. If we're iterating (say) forward and we're being asked to match against a (single) year which is strictly before the candidate year, there's no possible way it will ever match. In this case we can return quickly and avoid having to loop @max_runs times to come to the same conclusion. A similar logic applies for decrementing searches.
Note that this only applies to single-year targets. Year targets such as */5 will continue to be matched (or not) by previous logic.

Coverage decreased (-8.5%) to 89.623% when pulling f4f1e2af2f308f69937a6a30a1c9f71384c98116 on mtrudel:master into 078efc03e585a7abba4d369262b9792203eb17fd on jshmrtn:master.

@mtrudel Sorry fir the long wait. I somehow overlooked the PR.
I’ll create a patch release soon.


[2.5] istio sidecar

https://github.com/rancher/system-charts/pull/397

https://github.com/rancher/rancher/issues/30604

https://github.com/rancher/rancher/issues/30604


Add a configuration variable for the bot's name

It's already implemented but not everytime used.

Modification done in the say command (519afbd5c545efd1aa3d94342858a6eeab4ff4da)

In the command say, even if the bot as han other name, it is still changed to "Biomane" (made for the french pronounciation TTS).


Add gzip to nginx

Moves our lighthouse rating from 12 => 53.

Still way under the 80 we get on the current page.

I take it back, we only get a 69 - so really need to get this out so we can start working on that properly.


Update Logos for shipped connectors

Bug Description
Update Logos for shipped connectors, currently we show a default Ethyca logo.

Friendbuy
Friendbuy NextGen
Recharge

Please find the logos here
Steps to Reproduce
Click on create connection in the new release.
Expected behavior
All connectors have the right logos assigned.

https://github.com/ethyca/fides/pull/2002/commits/7eeeb2b1e5712a22581e4cb2e9245be1a76333aa


Add my project to the README

My personal project uses tinygltf so i want to add it to the "Projects using TinyGLTF" section of the README

Awesome! Merged!


Update text in AutoRelease

Currently the text comes as:
The libraries in each release are compiled for all recent major versions of CircuitPython. Please download the one that matches the major version of your CircuitPython. For example, if you are running 3.0.0 you should download the 3.x bundle.

To install, simply download the matching zip file, unzip it, and copy the lib folder onto your CIRCUITPY drive. Non-express boards such as the Trinket M0, Gemma M0 and Feather M0 Basic will need to selectively copy files over.

However, with the bundle getting larger, copying over the entire lib folder to the CIRCUITPY drive isn't so feasible anymore.
Also, maybe update the example to be 4.0.0 and 4.x bundle since that is current.

agreed - @makermelissa @sommersoft  either of you want to update the text as a PR? i can review it

Sure, I can take a stab at it.


Could not find a production build in the '.next' directory. when starting in production

To Reproduce

Create a new app npm create fumadocs-app

Move to the directory cd test-app

Execute build command npm run build

Execute start command npm run start

$ npm run start

><EMAIL_ADDRESS>start
> next start

   ▲ Next.js 15.0.2
   - Local:        http://localhost:3000

 ✓ Starting...
Error: Could not find a production build in the '.next' directory. Try building your app with 'next build' before starting the production server. https://nextjs.org/docs/messages/production-start-no-build-id
    at setupFsCheck (D:\asdsadsa\GitHub\poc\test-app\node_modules\next\dist\server\lib\router-utils\filesystem.js:149:19)
    at async initialize (D:\asdsadsa\GitHub\poc\test-app\node_modules\next\dist\server\lib\router-server.js:65:23)
    at async Server.<anonymous> (D:\asdsadsa\GitHub\poc\test-app\node_modules\next\dist\server\lib\start-server.js:266:36)

Current vs. Expected behavior
Following the previous steps it should start the project and host it on port :3000, but it fails stating that next is unable to find the build directory. You dont encounter this issue when running in development mode.
Provide environment information
Operating System:
  Platform: win32
  Arch: x64
  Version: Windows 11 Pro
  Available memory (MB): 16252
  Available CPU cores: 16
Binaries:
  Node: 23.0.0
  npm: N/A
  Yarn: N/A
  pnpm: 9.11.0
Relevant Packages:
  next: 15.0.2 // Latest available version is detected (15.0.2).
  eslint-config-next: N/A
  react: 18.3.1
  react-dom: 18.3.1
  typescript: 5.6.3
Next.js Config:
  output: N/A

Which area(s) are affected? (Select all that apply)
Core, CLI (create-fumadocs-app)
Additional context
This issue has been encountered in these OS: Windows 11 23H2 / 10, Linux (Ubuntu 22.04.4 LTS), it happened when migrating from the older "fumadocs-core": "13.4.10",,     "next": "^14.2.8", version to the latest one.

Cannot reproduce the error on code sandbox, please provide a minimal reproduction to your issue

I have the same issue here, just create a new project, start dev, start prod and it will error.

Please submit a reproduction if you have similar problems

Please submit a reproduction if you have similar problems

My steps to reproduce are the exact same ones he sent in his submit

You need to produce the problem in a repo or code sandbox

You need to produce the problem in a repo or code sandbox

I dont know of any code sandbox that i can share with you, so i have created a repo https://github.com/IMXNOOBX/fumadocs-issue-1021

Have you tried on a linux machine? (CodeSandbox whenever possible, click the "Open Demo" button on Fumadocs will open a codesandbox).
It works for me (ignore the port already in use one, it's because of other running dev servers)

Cant reproduce either in the codesandbox, but on a linux server you get the same issue, im sorry i cannot be of more help, but i suggest you try on any other machine you dont use for dev and try it, ive tried in 3 diferent windows machines and in a ubuntu server 22
redacted@redacted:~/github/fumadocs-issue-1021$ node -v
v23.0.0

redacted@redacted:~/github$ git clone https://github.com/IMXNOOBX/fumadocs-issue-1021
Cloning into 'fumadocs-issue-1021'...
remote: Enumerating objects: 31, done.
remote: Counting objects: 100% (31/31), done.
remote: Compressing objects: 100% (26/26), done.
remote: Total 31 (delta 0), reused 31 (delta 0), pack-reused 0 (from 0)
Receiving objects: 100% (31/31), 53.98 KiB | 26.99 MiB/s, done.
redacted@redacted:~/github$ cd fumadocs-issue-1021/
redacted@redacted:~/github/fumadocs-issue-1021$ npm i
(node:3256662) ExperimentalWarning: Support for loading ES Module in require() is an experimental feature and might change at any time
(Use `node --trace-warnings ...` to show where the warning was created)

><EMAIL_ADDRESS>postinstall
> fumadocs-mdx

[MDX] types generated

added 390 packages, and audited 391 packages in 9s

160 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
redacted@redacted:~/github/fumadocs-issue-1021$ npm run build

><EMAIL_ADDRESS>build
> next build

   ▲ Next.js 15.0.2
   - Experiments (use with caution):
     · turbo

   Creating an optimized production build ...
[MDX] initialized map file
(node:3256858) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
<w> [webpack.cache.PackFileCacheStrategy] Caching failed for pack: Error: Unable to snapshot resolve dependencies
<w> [webpack.cache.PackFileCacheStrategy] Caching failed for pack: Error: Unable to snapshot resolve dependencies
redacted@redacted:~/github/fumadocs-issue-1021$ npm run start

><EMAIL_ADDRESS>start
> next start

   ▲ Next.js 15.0.2
   - Local:        http://localhost:3000

 ✓ Starting...
Error: Could not find a production build in the '.next' directory. Try building your app with 'next build' before starting the production server. https://nextjs.org/docs/messages/production-start-no-build-id
    at setupFsCheck (/home/redacted/github/fumadocs-issue-1021/node_modules/next/dist/server/lib/router-utils/filesystem.js:149:19)
    at async initialize (/home/redacted/github/fumadocs-issue-1021/node_modules/next/dist/server/lib/router-server.js:65:23)
    at async Server.<anonymous> (/home/redacted/github/fumadocs-issue-1021/node_modules/next/dist/server/lib/start-server.js:266:36)
redacted@redacted:~/github/fumadocs-issue-1021$ node -v
v23.0.0

could you degrade node.js to v22 and use pnpm, and see if the problem exists?

Seems to work with node v22, no pnpm used in this test
redacted@redacted:~/github/fumadocs-issue-1021$ nvm install v22
Downloading and installing node v22.11.0...
Downloading https://nodejs.org/dist/v22.11.0/node-v22.11.0-linux-arm64.tar.xz...
################################################################################################################################################################################################ 100.0%
Computing checksum with sha256sum
Checksums matched!
Now using node v22.11.0 (npm v10.9.0)
redacted@redacted:~/github/fumadocs-issue-1021$ node -v
v22.11.0
redacted@redacted:~/github/fumadocs-issue-1021$ npm ci

><EMAIL_ADDRESS>postinstall
> fumadocs-mdx

[MDX] types generated

added 390 packages, and audited 391 packages in 9s

160 packages are looking for funding
  run `npm fund` for details

found 0 vulnerabilities
redacted@redacted:~/github/fumadocs-issue-1021$ rm .next -R
redacted@redacted:~/github/fumadocs-issue-1021$ npm run build

><EMAIL_ADDRESS>build
> next build

   ▲ Next.js 15.0.2
   - Experiments (use with caution):
     · turbo

   Creating an optimized production build ...
[MDX] initialized map file
(node:3262628) [DEP0040] DeprecationWarning: The `punycode` module is deprecated. Please use a userland alternative instead.
(Use `node --trace-deprecation ...` to show where the warning was created)
 ✓ Compiled successfully
 ✓ Linting and checking validity of types
 ✓ Collecting page data
 ✓ Generating static pages (7/7)
 ✓ Collecting build traces
 ✓ Finalizing page optimization

Route (app)                              Size     First Load JS
┌ ○ /                                    171 B           109 kB
├ ○ /_not-found                          897 B           101 kB
├ ƒ /api/search                          137 B           100 kB
└ ● /docs/[[...slug]]                    11.3 kB         158 kB
    ├ /docs
    └ /docs/test
+ First Load JS shared by all            99.9 kB
  ├ chunks/215-429da4f3e8265a89.js       45.2 kB
  ├ chunks/4bd1b696-89a6990571457db2.js  52.6 kB
  └ other shared chunks (total)          2.07 kB

○  (Static)   prerendered as static content
●  (SSG)      prerendered as static HTML (uses generateStaticParams)
ƒ  (Dynamic)  server-rendered on demand

redacted@redacted:~/github/fumadocs-issue-1021$ npm run start

><EMAIL_ADDRESS>start
> next start

   ▲ Next.js 15.0.2
   - Local:        http://localhost:3000

 ✓ Starting...
 ✓ Ready in 499ms

My thought is there's some compatibility issues with Next.js and Node.js 23. Fumadocs is only a library on top of Next.js so we cannot fix this unless the upstream problem get fixed. For now, I recommend to use Node.js 22 as a solution.

Alright, thanks for your time!


Add JobPosting to the provider

Comparing https://docs.zyte.com/zyte-api/usage/extract.html#zyte-api-extract-fields to https://scrapy-zyte-api.readthedocs.io/en/latest/reference/inputs.html#inputs I see JobPosting is missing, I think it should be trivial to add it or are there any problems?

Hi folks, can this be prioritized? We have some spiders in DO using the old AutoExtract and we'd like to migrate them to ZyteAPI extraction.


[wip] Second test of render hooks for links

Testing Hugo Render Hooks to update links.
Testing changes to feature state (raw html not rendered).

/remove-language fr

/remove-language de ja zh

/cc @tengqm

Note: There is debugging info inserted before links.

/close


Update naming rules for network

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

Close in favor of https://github.com/Azure/azure-sdk-for-net/pull/27139


Overflows/underflow with streaming on the PiZero (choppy audio)

So I have installed the pushtotalk.py sample, yet everytime I try to run it I am met with many underflows for buffer writes and overflows for reads. here is a log of a sample conversation:
INFO:root:Connecting to embeddedassistant.googleapis.com
INFO:root:Using device model #### and device id ####
Press Enter to send a new request...
INFO:root:Recording audio request.
WARNING:root:SoundDeviceStream read overflow (3200, 6400)
INFO:root:Transcript of user request: "hello".
INFO:root:Transcript of user request: "hello".
INFO:root:End of audio request detected.
INFO:root:Stopping recording.
INFO:root:Transcript of user request: "hello".
INFO:root:Expecting follow-on query from user.
INFO:root:Playing assistant response.
WARNING:root:SoundDeviceStream write underflow (size: 1600)
WARNING:root:SoundDeviceStream write underflow (size: 1600)
WARNING:root:SoundDeviceStream write underflow (size: 1600)
INFO:root:Finished playing assistant response.
INFO:root:Recording audio request.
INFO:root:Transcript of user request: "what".
INFO:root:Transcript of user request: "what's".
INFO:root:Transcript of user request: "what's the".
INFO:root:Transcript of user request: "what's the weather".
INFO:root:Transcript of user request: "what's the weather like".
INFO:root:Transcript of user request: "what's  the weather like".
INFO:root:Transcript of user request: "what's the  weather like".
INFO:root:Transcript of user request: "what's the  weather like out".
INFO:root:Transcript of user request: "what's the weather  like outside".
INFO:root:Transcript of user request: "what's the weather like  outside".
INFO:root:Transcript of user request: "what's the weather like outside".
INFO:root:End of audio request detected.
INFO:root:Stopping recording.
INFO:root:Transcript of user request: "what's the weather like outside".
INFO:root:Playing assistant response.

Every time one of these warnings appears, it produces a stutter in the output audio (playback is audible, just very choppy and not smooth). Unsure if the read ones create stutter in my voice being recorded. I have trying messing with block size, flush size, iter size etc. and it does have effects but I cannot seem to find a sweet spot. There isn't much documentation regarding these options on the docs pages anyhow (if there is, it's very minimal). Any advice on how to solve?

Fixed it by setting the audio block size to 80000

Here is a more complete train of thought:
I'd try keeping the others at defaults and then doing like 0, 1024, 2048, 4096 on the block size to see if it's a speed issue
I'll see about getting it set up myself to do some verbose debugging, but it looks like the error is from relatively close to the metal given the whole root: thing
My guess from the top of my head is a performance issue, the program isn't able to feed samples to play at the speed that it needs so some samples end up getting skipped which causes the stuttering
In which case you might want a larger block size so you need fewer block writes going to the audio device to play the samples?
Anyways, according to the sounddevice library that is actually returning the underflow indicator, the underflow bool is set to true when a gap is inserted into output data, possibly because the stream callback is using too much CPU time
https://github.com/spatialaudio/python-sounddevice/blob/master/sounddevice.py#L1783-L1793
That file holds too many layers of abstraction for audio I/O for it's own good, but that's okay. In the snippet I linked, they say that the underflow might happen during "play()". Turns out, play() calls upon an OutputStream object which again is an abstraction of the RawOutputStream object which is ultimately what is interfacing with the audiosetting the underflow flag. The Google Assistant example is skipping a bunch of the abstractions and writes the buffer straight to RawOutputStream.write() where the underflow error is being tripped due to what seems to be skipped samples due to performance issues. I'm not sure how much deeper I can dig, the next layer of abstraction is a CFFI and that's a whole other can of beans, but it points to a bunch of different audio backends depending on the platform it's running on
That was a bit of a mess but basically the Google sample skips some abstraction in the sounddevice library and writes a buffer straight to a RawOutputStream, which works via a C Foreign Function Interface down to your Pi's audio framework which is ALSA with what I think is a JACK server on top. At this point we're at the Linux kernel so I don't think changing things here is the way to go to say the least.
I would try to change the settings in the Google example to be more performance oriented, like lowering the sample rate/width. I'm not sure if the block size should be bigger or smaller, but play around with each of the settings individually until you find something you think is an acceptable compromise between sound quality and performance
According to the troubleshooting part in the readme.md of the google assistant sdk repo, stuttering audio may be fixed by setting the block size to a value larger than the size of the "ConverseResponse" audio payload. I'm not clear on how to find the payload size, so I guess either make sure there isn't too much else running on your Pi to avoid running out of CPU time or try arbitrarily raising the block size without touching the other settings until things work?

@maroonsp1rit Realise this is a closed issue but I'm having exactly this issue. Can you confirm which file you changed when you said:

Fixed it by setting the audio block size to 80000

and also in which directory that file is located. Many Thanks.

OK so having looked at #269 I realised I was looking for the audio_helpers.py file located at /home/pi/env/lib/python3.5/site-packages/googlesamples/assistant/grpc
Amended the file and changed the audio block size to 80000
*DEFAULT_AUDIO_SAMPLE_RATE = 16000

DEFAULT_AUDIO_SAMPLE_WIDTH = 2
DEFAULT_AUDIO_ITER_SIZE = 3200
DEFAULT_AUDIO_DEVICE_BLOCK_SIZE = 80000
DEFAULT_AUDIO_DEVICE_FLUSH_SIZE = 25600`

No improvement. symptoms as before. Did I do something wrong?


Feature/event models

Please check my Event() class and the test code in test_basic.py
https://github.com/pknn1/radii/blob/d566451a53c8ce135ede125978b63f6c44516e5a/app/models.py#L4-L33

Alright will change that right away


feat: rewrite to pure js

as mentioned in #80, this is a PR for rewriting to js
PS. I can't pass the default lint config, so I choose to use the GitHub action template eslint.yml
I tested Service Accounts and 1Password Connect locally using npm run local-action. If any reviewer is interested, you can test it locally by copying .env.example to .env.

NOTE to other reviewers: This PR is large due to the generated dist files; however, the significant changes are quite minimal.

@Xuanwo Thank you for the review. I have learned a lot from your comments about the CI check. I have added a new workflow, check-dist.yml, to ensure the generated dist is reliable.

@Xuanwo Thank you for the review. I have learned a lot from your comments about the CI check. I have added a new workflow, check-dist.yml, to ensure the generated dist is reliable.

Thank you, mostly LGTM now!

Inviting @edif2008 and @SimonBarendse for a review.

Hi folks, really appreciate your efforts on this! ❤ 🙌  Definitely aligned with the direction we'd like to move in for this and other integrations. We've build SDKs exactly because we saw such large desire from all of you to build integrations, and friction from doing so with CLI (e.g. performance, support for self-hosted runners, Windows support and it removes complexity from the implementation, making it easier to maintain and less error-prone). Excited to see you already help us move in that direction! 🚀
A couple things we'll want to look at to get this merged and deployed:

Backwards compatibility: Continuity is quite important to us. We realize many depend on this and other integrations in critical workflows, and want to avoid disruptions as much as possible. With that in mind, we'll want to have a look at whether we can find a path to keep this action backwards compatible and at v2.  So far, desktop app integration is the only missing feature in SDK we've identified to make a fully backwards compatible migration possible. While we work on closing that gap in SDKs, to not block this work from moving forward and make those aforementioned improvements available when not running locally (probably most uses), shall we support both side-by-side for now? We can check for Service Account token and/or Connect token envvars to use the new SDKs, and fall back to requiring CLI when those are not present (and thus probably running local). Once SDKs support Auth Prompts (aka desktop app integration) we can fully move over to SDK-only solution. That'd be a fully backwards compatible migration and we could stick to v2 throughout.
Dist: Not sure why this action is using dist. @edif2008 is currently out, but when he returns next week, would love to learn from him what our reasoning was for introducing and if we could move away from that now. This could remove the complexity of required checks and prevent this repo from bloating by checking in a new binary for the WASM build on every new SDK release. Binary is already 5MB right now, and will likely grow further when expanding SDKs with additional functionality. With frequent SDK releases can add up quite quickly.
Atomic Commits / PRs: To make the changes easier to review and move through faster, could you separate out unrelated changes in separate commits and PRs? For example I believe the changes to CONTRIBUTING.md, linting, .gitignore, TS Config and .env.example could each go in separate PRs, unless there's a relation that I'm not understanding yet. In that case, could you explain these changes and how they relate to this rewrite to help us understand and review? Shout-out to @AleksandrHovhannisyan for writing a great blog on this topic: https://www.aleksandrhovhannisyan.com/blog/atomic-git-commits/ 🙌

Thank you @SimonBarendse for the bravo comments!
@bxb100 led the entire effort, so I will leave the final decision to him on how to implement changes. I'm here to explain why we need dist/.
For every uses: actions/checkout@v4, the GitHub Actions runner will clone the specified action actions/checkout and directly execute its entrypoint. There is no build or compile setup involved, so each action must include a bundled index.js file for the action to function properly.
The entry point is defined here: https://github.com/1Password/load-secrets-action/blob/0a309926fa2e1d3844db604b984ea6214baa028b/action.yml#L14-L16
Additional documentation can be found here: https://docs.github.com/en/actions/sharing-automations/creating-actions/creating-a-javascript-action

I am not sure if there are some dependencies in 1Password SDK that require ncc and wasm specifically, but I've had a great experience bundling JS GitHub Actions with esbuild. It's fast, supports tree shaking and the final bundle is smaller than NCC one.

I am not sure if there are some dependencies in 1Password SDK that require ncc and wasm specifically

I'm guessing 1Password has written their logic in Rust, with the JS SDK being just a wrapper.

I'm guessing 1Password has written their logic in Rust, with the JS SDK being just a wrapper.

Yes, this is exactly it. We're using WASM to share a single implementation (in Rust) between all languages we support SDKs in. Right now that's Go, Python and JS, and we've built it with the intention to grow to more languages (in a scalable & sustainable way).

Thanks for the explanation on why dist is required @Xuanwo ! ❤  That makes sense.

Thank you @Xuanwo, @SimonBarendse, and @yafanasiev for your reviews and discussions. I would like to provide some explanations and background information regarding the submitted content in this PR:

.env.example is an example config used for local-action, which facilitates local testing directly.
.eslintignore, .github/linters/.eslintrc.yml, package.json (deleting eslintConfig) are changes made because I couldn't use the original @1password/front-end-style/eslintrc.yml when submitting the code. Therefore, I switched to the configuration recommended by https://github.com/actions/typescript-action.
__tests__, config/jest.config.js are to expand the original test set.
.github/workflows/check-dist.yml is used to check the consistency of the generated dist for every PR and PUSH as mentioned before. It requires executing npm run bundle, which includes format:write.
CONTRIBUTING.md results from the pre-push hook from husky executing npm run validate(contain format). I apologize for its appearance in this submission.
The changes to .github/linters/tsconfig.json and tsconfig.json will be reverted.
Regarding the fallback to CLI when there are no environment variables, perhaps we can follow @Xuanwo 's suggestion and bump into v3, then iterate gradually. I understand this occurs mainly during local testing, but it can also be bypassed by setting the environment variables.
About compatibility, the inputs in action.yml remain consistent with version v2. The environment variables OP_SERVICE_ACCOUNT_TOKEN, OP_CONNECT_HOST, and OP_CONNECT_TOKEN also remain unchanged.
Based on my understanding of action uses ^1, I believe frequently changing the dist output will only affect users who do not use the major version and need to update manually (although, to be honest, I haven't seen this usage scenario).
For the bundled submission of this PR, since it was converted from one of my projects ^2, I did not consider atomic submissions. I sincerely apologize for any inconvenience this may have caused.

Backwards compatibility

Hi @SimonBarendse, I suggest we avoid taking this direction since switching from CLI-based to JS-based does introduce a breaking change. I can foresee multiple ways this action could fail. It's common and expected for GitHub Actions users to upgrade actions between major versions (every Node version bump will trigger one).
Adopting load-secrets-action@v3 would provide a much smoother transition for the community. Releasing v3 doesn't mean users will adopt it by default; they will continue using v2 unless they manually update their workflows.

For the bundled submission of this PR, since it was converted from one of my projects 2, I did not consider atomic submissions. I sincerely apologize for any inconvenience this may have caused.

Hi @bxb100, I understand the concern from @SimonBarendse's side. To make the PR review smoother, do you think it would be a good idea to simply remove all files except for package.json, src/, and dist/? We can gradually add other staffs back later (which makes it much easier to review without involving real logic).

I would like to provide some explanations and background information regarding the submitted content in this PR

Thank you @bxb100! 🙌  This is very helpful.
Followed up in separate issues

ES Lint Config: I've opened https://github.com/1Password/load-secrets-action/issues/83 for us to follow up on this.

Linting:

CONTRIBUTING.md results from the pre-push hook from husky executing npm run validate(contain format). I apologize for its appearance in this submission.

Thank you! This uncovered a gap in our linting in CI. We're following up in https://github.com/1Password/load-secrets-action/issues/84

Rewrite specific changes - Discussing in this PR
Backwards Compatibility

I suggest we avoid taking this direction since switching from CLI-based to JS-based does introduce a breaking change. I can foresee multiple ways this action could fail.

@Xuanwo could you help me see these too? I'm currently under the impression that SDKs will be fully compatible with CLI after addition of Auth Prompts. As @bxb100 mentioned as well:

the inputs in action.yml remain consistent with version v2. The environment variables OP_SERVICE_ACCOUNT_TOKEN, OP_CONNECT_HOST, and OP_CONNECT_TOKEN also remain unchanged.

Could you please help me see and understand what I'm missing?
Dist
Yes, I'm less concerned about this now and okay with proceeding with checking in the WASM binary into the code here after @Xuanwo's explanation why this is necessary. Apologies that I not explicitly mentioned that before.
I assume and hope when using the action that GitHub only fetches the referenced commit and not the full Git history, similar to the checkout action, by using --depth=1. That prevents historic binaries slowing down the action and increasing required bandwidth.
So the larger repo size from historic binaries checked in would only affect new contributors checking out the full repo, including all historic WASM binaries. But it won't affect using the action.
With that in mind, I believe we can pull back in the changes to dist and your introduction of .github/workflows/check-dist.yml.
Code Review
I've requested a review from @Marton6 and @edif2008 for the specific code changes made in this PR.

Thank you, @SimonBarendse, for the detailed explanation.

With that in mind, I believe we can pull back in the changes to dist and your introduction of .github/workflows/check-dist.yml.

I believe we can proceed after #83 #84 .

I assume and hope when using the action that GitHub only fetches the referenced commit and not the full Git history, similar to the checkout action, by using --depth=1. That prevents historic binaries slowing down the action and increasing required bandwidth.

base on https://github.com/actions/runner/blob/078eb3b381939ee6665f545234e1dca5ed07da84/src/Runner.Worker/ActionManager.cs#L784C1-L792C1 I think it direct download like https://api.github.com/repos/{action.NameWithOwner}/tarball/{action.Ref}

Hey @bxb100,
The contribution you’ve made so far has been amazing. While functionally testing this, I've come across a few feature gaps in the SDK's handling of secret references, differing from the CLI, such as:

File support
SSH key item support
Query parameters - only attribute=otp/totp is supported at the moment in the SDKs.

These features are actively being scoped and prioritized for future updates to the SDK.
Because of that, however, we can’t guarantee at this point the full backwards-compatibility of this rewritten version of the action until those features are available in the SDK as well. Therefore, I propose to move forward with this and make this a v2-alpha until the SDKs have the same support on secret references as the CLI.
Let me know how you feel about this.

Therefore, I propose to move forward with this and make this a v2-alpha until the SDKs have the same support on secret references as the CLI.

Hi, @edif2008, thank you so much for your review! This idea aligns with my initial thoughts, so here’s my +1 support. I fully support moving quickly rather than causing delays here.

I have no objections, agree with @Xuanwo

Hey @bxb100!
Just wanted to let you know that I've merged a couple of improvements related to the pipelines, as well as the ES Lint tooling. If you could merge the latest version of main into your branch, that would be much appreciated. That will also solve any merge conflicts that currently need to be resolved. 😄

Done, PTAL @edif2008


support jemalloc

Feature Request
make pegasus to support jemalloc
Related pull requests
https://github.com/XiaoMi/rdsn/pull/910

Support to set/get dirty_decay_ms and muzzy_decay_ms dynamically
Since we've supported building rDSN with jemalloc in https://github.com/XiaoMi/rdsn/pull/910, it's necessary for us to  supporting setting/getting dirty_decay_ms and muzzy_decay_ms dynamically.
For details please see https://github.com/XiaoMi/rdsn/pull/928


AssertionError: An object named 'MaskDINOEncoder' was already registered in 'SEM_SEG_HEADS' registry!

code:
from detectron2.projects.hipie.demo_lib.part_segm_demo import PartSegmDemo
found:
AssertionError: An object named 'MaskDINOEncoder' was already registered in 'SEM_SEG_HEADS' registry!

Hi testing on a new environment I am not able to reproduce the error. This is likely a problem with the detectron2 installation folder. Please ensure you are using a clean environment as multiple detectron2 versions from different projects can cause such an error. You can try pip3 install -e . without the --user flag.
I would be happy to try to reproduce the error if you have the installation steps you used.


USER STORY: Add-Product-Page

As a developer, I will want to make it so that:

[ ] When new products are submitted, unrelated fields should not be submitted into database
[ ] In the products page, the details for the shirt should not show a shoe size or pant size

I'm dropping this issue and unassigning myself because this may be a bit too difficult for me @SeattleColleges/leadership


jsx elements in yield statement

I found that write jsx elements directly after yield statement would cause a syntax error (Unexpected token). But according to jsx spec (https://facebook.github.io/jsx/) and ECMAScript spec. JSXElement is a PrimaryExpression which can be used after yield statement.
Currently Error but should be OK:
yield ;
Currently OK:
yield ();
Because I am writing a program heavily depends on generator functions. I want my code be more clear. So I forked this project and fix this problem in commit de56e12c6867e947cefc7e1b37676460b0365cb7. There is just one line difference where I add { startsExpr: true } to jsxTagStart token.
Because I am not familiar with the internal representation in this project. I don't know if it is proper to do such a change. But at least there is no test failed after change.

Fixed via #31.


Assets cached on production despite having file changes.

Is there a way to make it so browsers force reloading of asset files such as Javascript and CSS files upon there being changes?
Particularly referring to production.css/js

How did you actually make use of cache initially? For me nothing is cached in browser, even though server returns 304 code - there still is a round-trip request.

@sochka a 304 will always make a round-trip request as it is validating that the content hasn't been modified.
In our app instance, we also have middleware that adds cache headers to various requests (depending on what is being requested, cache headers are different), something along the lines of:
var limit = 60 * 60 * 24 * 1000; /* one day */
res.header('Cache-Control', 'public, max-age='+ (limit / 1000));
res.header('Expires', new Date(Date.now() + limit).toUTCString());

@gavinbunney thanks, I've made it work using express.static and maxAge option.