Multiple page Hitomi.la closes viewer

Using left or right to navigate in Hitomi.la for large enough galleries to have multiple pages would close the viewer on left/right. Opening the viewer again would show no pages if on page 2 or higher.

The script responsible is likely https://ltn.hitomi.la/gallery.js

fix: keyboard event propagation;

The issue returned ever since the rename to Comic Looms. The same script is responsible.
$(document).keydown(function(e) {
        var evtobj = window.event ? event : e;
        if (evtobj.altKey || evtobj.ctrlKey || evtobj.shiftKey || evtobj.metaKey) return;

        var current_page_el = $(".currentPage");

        switch (e.which) {
                case 37: //left
                        if (current_page_el.prev().children().length) {
                                window.location.hash = current_page_el.prev().children()[0].hash;
                        }
                        break;
                case 39: //right
                        if (current_page_el.next().children().length) {
                                window.location.hash = current_page_el.next().children()[0].hash;
                        }
                        break;
                default: return;
        }

        e.preventDefault();
});

@MapoMagpie Keydown event listener was replaced by a keyup event listener in the rewrite. Reverting back to keydown fixes this issue.


Provide binary installation for libsdl

Is your feature request related to a problem? Please describe.
SDL provide precompiled binary for multiple platforms, make use of these binary could reduce config time.
Describe the solution you'd like
Users of libsdl could set a config option to use binary package:
add_requires("libsdl", {binary=true})

Describe alternatives you've considered
Add another package and make this package a equivalent of existing package, thus we can specify which package to use at config stage:
xmake config --package-libsdl=libsdl-binary

Additional context
No response

If you use the windows libraries, precompiled binaries are provided by default.


numpy.version.version

It looks like cuPy doesn't have runtime version getter.
It would be great to have something like cupy.version.version

I may just be unfamiliar with the concept of a "runtime version getter", but I think what you want is cp.__version__.
Most packages have their version stored at package.__version__, to the degree that it's basically a standard.
>>> np.__version__
'1.19.4'
>>> cp.__version__
'8.2.0'


ci:[CNI] Windows cniv1 load test pipeline

Reason for Change:

The PR creates the windows cniv1 load test pipeline.( Added to the CNI load test pipeline)

Deploys windows pods multiple times
Validates the HNS state, azure vnet and azure vnet ipam state with cluster pods ips.

Issue Fixed:

Requirements:

[x] uses conventional commit messages

[ ] includes documentation
[ ] adds unit tests
[x] relevant PR labels added

Notes:

/azp run CNI Load test


Add option to stop waterline from posting multi-line log entries

Waterline provides some really helpful error messages when there are weird/incorrect database configurations.  However, these are sent as multi-line log entries, which doesn't really make sense in production systems.  (e.g. MIGHT_BE_YOUR_FAULT).
It would be great to have an option to change these multi-line messages to be sent as a single line.
Alternatively, if waterline were to log via the sails logger rather than using console.error, console.warn etc. then it would be easier to control these messages.

@alxndrsn I see where you're coming from, although I don't entirely agree with this:

which doesn't really make sense in production systems

We rely on these logs in our own production systems, and having extra information (especially when it comes to stack traces) can be really helpful to figure out which customers/orders/etc. were affected.
That said, it would make sense to me to have the option for fewer troubleshooting tips, etc in production for a lot of the errors  (and especially some of the warnings).
I'm not sure adding a new config setting is the right way to go, though (I've learned the hard way it's easy to add those and much much more annoying to maintain them).
Maybe what we should do is identify some specific examples of errors that are too long (i.e. drop a github link to the line of code where they come from -- easiest way to find that is to search github for a chunk of the error msg).  Then we'll be able to address improving them (or conditionally shortening them) on a case by case basis.
Re: conditional shortening, I'm thinking it would probably work the same way as how production stack traces work  (i.e. normally we improve stack traces by instantiating Error instances called omens -- but we skip doing that in prod because it has a (albeit small) negative impact on performance.  We do that based on env vars: we'd shorten only if either NODE_ENV==='production' and DEBUG is not truthy).

@mikermcneil thanks for the considered response.

We rely on these logs in our own production systems, and having extra information (especially when it comes to stack traces) can be really helpful to figure out which customers/orders/etc. were affected.

I've found the content of these errors very helpful including in production.  My issue is specifically with error messages which include linebreaks: in production these are written as multiple log entries which are very hard to filter out.
If we could just remove the linebreaks, this would immediately solve my problem.

@alxndrsn that makes sense!  OK, so then I think the next step is for us to identify some specific examples of production errors that are too long (i.e. drop a github link to the line of code where they come from -- easiest way to find that is to search github for a chunk of the error msg). Then we can address them one by one.
There are probably errors that you see during dev that should still probably span multiple lines (e.g. sails CLI related stuff), but for the other errors, I'm down to look at consolidating them onto a single line.  (We'll just have to deal with it on a case-by-case basis)

👍
My original example was https://github.com/balderdashy/waterline/blob/master/lib/waterline/utils/query/process-all-records.js#L19-L34, but it looks like many error messages in https://github.com/balderdashy/waterline/blob/master/lib/waterline/utils/query/process-all-records.js include line breaks.

👍
My original example was https://github.com/balderdashy/waterline/blob/master/lib/waterline/utils/query/process-all-records.js#L19-L34, but it looks like many error messages in https://github.com/balderdashy/waterline/blob/master/lib/waterline/utils/query/process-all-records.js include line breaks.

Sure enough - I'm cool with all of those living on a single line, because they are oftentimes seen in production logs  (although in my experience, if they're showing up in production logs, that's a bad sign, because it means there needed to be some migration that didn't happen.  Still, it'd be nice to actually be able to read what's going on in that situation!)

PR at https://github.com/balderdashy/waterline/pull/1606

@alxndrsn just took a look at your PR and added some feedback, let me know what you think: https://github.com/balderdashy/waterline/pull/1606#discussion_r286063262

Changing content of error messages will break tests that have expectations of a certain response/error.
The referenced PR will add a non-zero amount of work, for what I can only interpret as a cosmetic change. I would support an option, as stated in title, but oppose breaking existing behaviour. Just my 2c though.

@alxndrsn are you using winston or any other middleware to take care of your logs?
I believe these new lines are very handy for humans, are making these long texts easier to read.
Would not be better to sort this in a way that makes our servers deal with this instead of reducing readability for the operator?
We write high level code (and logs) for humans to read, I believe we can do better and teach our setups to deal with some extra new lines.
https://www.npmjs.com/package/winston


Added query optimizer, density calc/ML scripts and text (tex) for paper

Thanks for this @kevinjose! Is this now ready for a review? It's a bit hard to see whats going on with all the unnecessary checkpoint/aux files from Jupyter/LaTeX/DS_STORE, could you please go through and remove them? It would also be great if you could provide the environment this was run in (conda environment.yaml or just a requirements.txt) so that we can reproduce it in the future.

@kevinjose why was that closed abruptly?


[DP] /collections/index and /datasets/index are NOT gzipped

Problem:
/collections/index and /datasets/index endpoints are NOT gzipped
Solution:
gzip them at Cloudfront or in BE?
see thread:
https://czi-sci.slack.com/archives/C023Q1APASK/p1687449592226519

Assigning to @Bento007 for implementation during next on-call rotation. 🙏


Console UI allows admin users to set admin permissions for roles

Describe the issue:
When using the Console as an admin user, it is possible to set admin permissions to new/existing roles. This should not be possible. The current implementation of the SCIM2 API only allows the super (super) admin to carry out such functionalities.
How to reproduce:

Login as super admin
Create a user and give admin permissions (internal/admin) and application/console role.
Login to Console as the new user.
Create a role. In the role creation wizard, admin permission settings are offered.

Expected behavior:
Admin permission settings should not be offered to console users other than the super admin.
Environment information:

Product Version: IS-5.11.0-beta4

The backend improvement is tracked with this issue https://github.com/wso2/product-is/issues/10702


🐛 [Firebase Auth] Debug session paused with no details on every app rebuild (web)

Bug report
Describe the bug
I'm trying to develop a Flutter app and run it from Chrome instance. This app uses firebase emulator for the development purpose but somehow when I make changes to any code and when Flutter tries to reload the app, it paused the debug session and point me to the error.

However, it doesn't show any details about the error in the debug console other than this
Restarted application in 774ms.
[GETX] Instance "LoggerService" has been created
[GETX] Instance "LoggerService" has been initialized
[GETX] Instance "AuthService" has been created
[GETX] Instance "AuthService" has been initialized
[2022-04-14T16:06:38.386Z]  @firebase/firestore:
ChromeProxyService: Failed to evaluate expression 'FirebaseAuth.instance.useAuthEmulator': InternalError: No frame with index 46.
ChromeProxyService: Failed to evaluate expression 'async': InternalError: No frame with index 46.
ChromeProxyService: Failed to evaluate expression 'FirebaseFirestore.instance.useFirestoreEmulator': InternalError: No frame with index 46.

I tried several things including:

Restarting the emulator suite using <IP_ADDRESS> and set the app to point out to said host
Changing <IP_ADDRESS> to my computer's IP address (192.168.x.x)
Using localhost instead of <IP_ADDRESS> as pointed in the docs

But this still happening everytime I hit ctrl + S.
I did not modify anything in the emulator script, it was a fresh install.
Steps to reproduce
Steps to reproduce the behavior:

Create new flutter project
Configure firebase for the project
Follow instructions given in the documentation
Run the emulator suite
Run the app in Chrome instance
Hit ctrl + S
The debug session is paused and no details given

Expected behavior
The debug session should not be paused or if it does, at least provide details.
Flutter doctor
Click To Expand
[√] Flutter (Channel stable, 2.10.4, on Microsoft Windows [Version 10.0.19044.1586], locale en-US)
[√] Android toolchain - develop for Android devices (Android SDK version 32.1.0-rc1)
[√] Chrome - develop for the web
[√] Visual Studio - develop for Windows (Visual Studio Community 2022 17.1.3)
[√] Android Studio (version 2021.1)
[√] VS Code, 64-bit edition (version 1.66.2)
[√] Connected device (3 available)
[√] HTTP Host Availability

• No issues found!

Flutter dependencies
Click To Expand
Dart SDK 2.16.2
Flutter SDK 2.10.4
project_name 1.0.0+1

dependencies:
- cloud_firestore 3.1.12 [cloud_firestore_platform_interface cloud_firestore_web collection firebase_core firebase_core_platform_interface flutter meta]
- cupertino_icons 1.0.4
- firebase_auth 3.3.14 [firebase_auth_platform_interface firebase_auth_web firebase_core firebase_core_platform_interface flutter meta]
- firebase_core 1.14.1 [firebase_core_platform_interface firebase_core_web flutter meta]
- flutter 0.0.0 [characters collection material_color_utilities meta typed_data vector_math sky_engine]
- get 4.6.1 [flutter]
- json_serializable 6.1.5 [analyzer async build build_config collection json_annotation meta path pub_semver pubspec_parse source_gen source_helper]
- logger 1.1.0

dev dependencies:
- build_runner 2.1.8 [args async analyzer build build_config build_daemon build_resolvers build_runner_core
code_builder collection crypto dart_style frontend_server_client glob graphs http_multi_server io js logging meta mime package_config path pool pub_semver pubspec_parse shelf shelf_web_socket stack_trace stream_transform timing watcher web_socket_channel yaml]
- flutter_lints 1.0.4 [lints]
- flutter_test 0.0.0 [flutter test_api path fake_async clock stack_trace vector_math async boolean_selector
characters charcode collection matcher material_color_utilities meta source_span stream_channel string_scanner term_glyph typed_data]
- lints 1.0.1

transitive dependencies:
- _fe_analyzer_shared 38.0.0 [meta]
- analyzer 3.4.1 [_fe_analyzer_shared collection convert crypto glob meta package_config path pub_semver source_span watcher yaml]
- args 2.3.0
- async 2.8.2 [collection meta]
- boolean_selector 2.1.0 [source_span string_scanner]
- build 2.2.1 [analyzer async convert crypto glob logging meta path]
- build_config 1.0.0 [checked_yaml json_annotation path pubspec_parse yaml]
- build_daemon 3.0.1 [built_collection built_value http_multi_server logging path pool shelf shelf_web_socket stream_transform watcher web_socket_channel]
- build_resolvers 2.0.6 [analyzer async build crypto graphs logging path package_config pool pub_semver stream_transform yaml]
- build_runner_core 7.2.3 [async build build_config build_resolvers collection convert crypto glob graphs json_annotation logging meta path package_config pool timing watcher yaml]
- built_collection 5.1.1
- built_value 8.1.4 [built_collection collection fixnum meta]
- characters 1.2.0
- charcode 1.3.1
- checked_yaml 2.0.1 [json_annotation source_span yaml]
- clock 1.1.0
- cloud_firestore_platform_interface 5.5.3 [collection firebase_core flutter meta plugin_platform_interface]- cloud_firestore_web 2.6.12 [cloud_firestore_platform_interface collection firebase_core firebase_core_web
flutter flutter_web_plugins js]
- code_builder 4.1.0 [built_collection built_value collection matcher meta]
- collection 1.15.0
- convert 3.0.1 [typed_data]
- crypto 3.0.1 [collection typed_data]
- dart_style 2.2.2 [analyzer args path pub_semver source_span]
- fake_async 1.2.0 [clock collection]
- file 6.1.2 [meta path]
- firebase_auth_platform_interface 6.2.3 [firebase_core flutter meta plugin_platform_interface]
- firebase_auth_web 3.3.12 [firebase_auth_platform_interface firebase_core firebase_core_web flutter flutter_web_plugins http_parser intl js meta]
- firebase_core_platform_interface 4.2.5 [collection flutter meta plugin_platform_interface]
- firebase_core_web 1.6.2 [firebase_core_platform_interface flutter flutter_web_plugins js meta]
- fixnum 1.0.0
- flutter_web_plugins 0.0.0 [flutter js characters collection material_color_utilities meta typed_data vector_math]
- frontend_server_client 2.1.2 [async path]
- glob 2.0.2 [async collection file path string_scanner]
- graphs 2.1.0 [collection]
- http_multi_server 3.2.0 [async]
- http_parser 4.0.0 [charcode collection source_span string_scanner typed_data]
- intl 0.17.0 [clock path]
- io 1.0.3 [meta path string_scanner]
- js 0.6.3
- json_annotation 4.4.0 [meta]
- logging 1.0.2
- matcher 0.12.11 [stack_trace]
- material_color_utilities 0.1.3
- meta 1.7.0
- mime 1.0.1
- package_config 2.0.2 [path]
- path 1.8.0
- plugin_platform_interface 2.1.2 [meta]
- pool 1.5.0 [async stack_trace]
- pub_semver 2.1.1 [collection meta]
- pubspec_parse 1.2.0 [checked_yaml collection json_annotation pub_semver yaml]
- shelf 1.3.0 [async collection http_parser path stack_trace stream_channel]
- shelf_web_socket 1.0.1 [shelf stream_channel web_socket_channel]
- sky_engine 0.0.99
- source_gen 1.2.1 [analyzer async build dart_style glob meta path source_span yaml]
- source_helper 1.3.1 [analyzer collection source_gen]
- source_span 1.8.1 [collection path term_glyph]
- stack_trace 1.10.0 [path]
- stream_channel 2.1.0 [async]
- stream_transform 2.0.0
- string_scanner 1.1.0 [charcode source_span]
- term_glyph 1.2.0
- test_api 0.4.8 [async boolean_selector collection meta source_span stack_trace stream_channel string_scanner term_glyph matcher]
- timing 1.0.0 [json_annotation]
- typed_data 1.3.0 [collection]
- vector_math 2.1.1
- watcher 1.0.1 [async path]
- web_socket_channel 2.1.0 [async crypto stream_channel]
- yaml 3.1.0 [collection source_span string_scanner]

Woops, it turns out that my auth service implementation is causing this error. This problem is gone when I commented it. I'm closing this issue. Thanks all for the attention, my bad!


Infinite recursion i table 8616 "Config. Package Field", procedure GetUniqueElementName

Infinite recursion occurs for the string 'ITI Full VAT Base Amount (LCY)' causing a memory overflow and crash.
Table 8616 "Config. Package Field", procedure GetUniqueElementName
This happens when the length of the parameter is equal to the maximum (here 30 characters), we add a suffix, and then we truncate the entire text to 30 characters - the starting position, to return this value again by calling the same function recursively.
Suggested solution
Shorten the text before incrementing by 1 if the string is maximally long (30 characters here)

That might just be a product defect! Unfortunately, this repository is only for extensibility requests for Dynamics 365 Business Central or pull requests towards the 1st party Business Central apps. We suggest that you open a support case or file a bug to ensure that all Business Central users benefit from your catch as soon as possible:
On premises - https://support.microsoft.com/en-us/supportforbusiness/productselection?sapId=93d37907-ad94-d591-22e9-593cfa09dd3f
Cloud – contact your partner, or if you are a partner open a support incident through Partner Center - https://partner.microsoft.com/en-us/pcv/dashboard/overview


reaper: address CVE-2024-4068

Merge Checklist

All boxes should be checked before merging the PR (just tick any boxes which don't apply to this PR)

[x] The toolchain has been rebuilt successfully (or no changes were made to it)
[x] The toolchain/worker package manifests are up-to-date
[x] Any updated packages successfully build (or no packages were changed)
[x] Packages depending on static components modified in this PR (Golang, *-static subpackages, etc.) have had their Release tag incremented.
[x] Package tests (%check section) have been verified with RUN_CHECK=y for existing SPEC files, or added to new SPEC files
[x] All package sources are available
[x] cgmanifest files are up-to-date and sorted (./cgmanifest.json, ./toolkit/scripts/toolchain/cgmanifest.json, .github/workflows/cgmanifest.json)
[x] LICENSE-MAP files are up-to-date (./SPECS/LICENSES-AND-NOTICES/data/licenses.json, ./SPECS/LICENSES-AND-NOTICES/LICENSES-MAP.md, ./SPECS/LICENSES-AND-NOTICES/LICENSE-EXCEPTIONS.PHOTON)
[x] All source files have up-to-date hashes in the *.signatures.json files
[x] sudo make go-tidy-all and sudo make go-test-coverage pass
[x] Documentation has been updated to match any changes to the build system
[x] If you are adding/removing a .spec file that has multiple-versions supported, please add @microsoft/cbl-mariner-multi-package-reviewers team as reviewer (Eg. golang has 2 versions 1.18, 1.21+)
[x] Ready to merge

Summary

What does the PR accomplish, why was it needed?
This patch updates the src/ui node modules dependency to address the following CVEs:

Address CVE-2024-4068 by upgrading the version of the npm module "braces" to 3.0.3
Remove patch for CVE-2023-28155 as request npm module upgraded to 2.88.2
Remove patch for CVE-2018-11694 as node-sass npm module upgraded to 4.14.1
Remove patch for CVE-2022-37601 as loader-utils npm module upgraded to 1.4.2
Remove patch for CVE-2023-26159 as follow-redirects npm module upgraded to 1.15.6

Does this affect the toolchain?

NO
Test Methodology

Pipeline build id: https://dev.azure.com/mariner-org/mariner/_build/results?buildId=576557&view=results

Auto cherry-pick results:

main :white_check_mark: -> https://github.com/microsoft/azurelinux/pull/9298

Auto cherry-pick pipeline run -> https://dev.azure.com/mariner-org/mariner/_build/results?buildId=581073&view=results


Design and buildout of Agortization proejct

see #39
Create design
Create issues for each piece of work.

This is a duplicate of #39 since individual issues will be create in that milestone.


Add JSON for Japanese locale

Japanese locale added.
but, some parts are not applied.

Yeah thanks for noticing, fixed with next update.
I am pushing new changes which change some translations and updates some, so update them when you can. Thanks!


Visual Studio Code insiders is now sending textDocument/didOpen messages for notebooks.

Does this issue occur when all extensions are disabled?: Yes

VS Code Version: Version: 1.87.0-insider (user setup)
Commit: 019f4d1419fbc8219a181fab7892ebccf7ee29a2
OS Version: Windows 10 WSL

Steps to Reproduce:

Install Pylance and Jupyter extensions
Open VS code in WSL
Set "python.trace.server": "verbose" in your settings.json
Create a notebook and save it to disk
Edit a cell

If you look at the trace log output for the Python Language Server you'll see that we're getting textDocument/didOpen notifications  in Pylance.
According to this capability:
https://microsoft.github.io/language-server-protocol/specifications/lsp/3.17/specification/#notebookDocument_synchronization
And this setting here:
https://github.com/microsoft/pyrx/blob/4c00dacee634e2c1b29524f41f02065624a8534a/packages/pylance-internal/src/server/asyncServer.ts#L659
We should only be getting notebookDocument/didOpen and notebookDocument/didChange events.
On Windows and in the stable version of VS code, this is true. On the insiders versions we seem to sometimes also get textDocument/didOpen and textDocument/didChange events for notebook cells as well.

This breaks notebooks for pylance as we don't find any of the notebook cells.

it looks like with the same selector, vscode.languages.match such as this https://github.com/microsoft/vscode-languageserver-node/blob/main/client/src/common/notebook.ts#L493 fails in insider but pass in stable in WSL
2 inputs for the match, selector and document (uri) seems identical.
and it only happens with WSL, even insider, match works as expected with windows.

for this particular case, we are using this notebook selector

{
        notebookSelector: [
            {
                notebook: undefined,
                cells: [{ language: 'python' }],
            },
        ],
    }

might be related to this? https://github.com/microsoft/vscode/pull/205351

shouldn't this issue's priority bump up since now it got into stable?

bump this issue again. It is really bothering now with the new version. Looking forward to some fix soon

Bumping this again. I reported this problem at https://github.com/microsoft/vscode-jupyter/issues/15276. It's been driving me crazy for 3 days. I thought I did something wrong while modifying Ruff.

@dbaeumer This is likely related to my change but I also wonder about the inner workings here. For the VS Code API it is expected that the didOpen event fires for all documents - no matter if they are a notebook cell or a standalone document.

The underlying problem is a URI comparison with an un-transformed remote URI:

This is an interesting issue and something that might strike us in other places. The gist is that CellUri.parse(...).notebook cannot be safely be used in the EH. This is because uris of notebooks get transformed (when entering the EH) but cell-uris are not. This means uri-equality checks fail. However, text document identity checks will work correctly.
I have fixed this issue with a document identity check but IMO there is some debt

we either transform cell uris
we stop using the property notebook the CellUri.parse util

@rebornix Have you encountered this issue before? Are workarounds in place already or is this the first case this happens on the EH?

@rchiodo can you verify if this has been fixed in the latest insiders!

are you guys hot fix stable as well? once fix is verified in insider?

@heejaechang yes, if this fix is verified in insiders, recovery 1 for stable is currently planned for Thursday morning.

Yes it has been fixed for me in insiders. /verified

@rchiodo fantastic, tysm!


Reconfigure yeager for summer development

Need to clone yeager from production data to test rolling in new features before pushing to the prod server in the fall

Server has been redeployed in development mode but can be spun up to prod as well by activating a service or two.


How do you trigger the smoke sensor status

The problem
Real-time updates smoke sensor is Nest Protect (Kitchen) Smoke Status "Not Detected"
I hope that can be solved first then we can show the status on the dashboard
that would be really cool

What version of this integration (ha-nest-protect) has the issue?
0.1.0
What version of Home Assistant Core has the issue?
core-2022.2.9
Device / Model
nest protect Topaz-2.7 smoke alarm
Home Assistant log
Logs
```
Copy/paste any log here, between the starting and ending backticks (`)
```

..
Additional information
..

@benotje thanks for reporting. Just checking; are you aware that real-time updates are not possible yet? (for none of the entities). This is currently stated in the README.
In order to see if your smoke status works, you could try to trigger the smoke alarm and than reload the integration in Home Assistant. (press the dots next to the integration and pick 'reload'). This will show the last available status.


"No matching distribution found for mlc-chat-nightly"

pipx install llm
llm install llm-mlc
llm mlc pip install --pre --force-reinstall \
  mlc-ai-nightly \
  mlc-chat-nightly \
  -f https://mlc.ai/wheels
Looking in links: https://mlc.ai/wheels
Collecting mlc-ai-nightly
  Downloading https://github.com/mlc-ai/package/releases/download/v0.9.dev0/mlc_ai_nightly-0.15.dev138-cp312-cp312-macosx_10_15_x86_64.whl (84.0 MB)
     ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━ 84.0/84.0 MB 16.0 MB/s eta 0:00:00
ERROR: Could not find a version that satisfies the requirement mlc-chat-nightly (from versions: none)
ERROR: No matching distribution found for mlc-chat-nightly

Mac mini M1
macOS 14.3
python 3.12.2
llm 0.13.1

Same here -- in MLC's instructions it appears maybe they renamed mlc-chat-nightly to mlc-llm-nightly?

Will llm mlc setup be able to complete with this name change? I'm doing a first-time setup.

See the open PR here: https://github.com/simonw/llm-mlc/pull/24


add helm labels and nodeSelector for flux-cli job

Signed-off-by: Daniel Werdermann<EMAIL_ADDRESS>
What this PR does / why we need it:

add labels as recommended by https://helm.sh/docs/chart_best_practices/labels/
add nodeSelector, affinity and tolerations for the pre-install check
remove helm-changelog step from CONTRIBUTING.md

Special notes for your reviewer:
Everything in the __snapshot__ directories can be ignored, I just updated the expected test result, because of changed labels.
Checklist

[x] DCO signed
[x] Chart Version bumped
[x] helm-docs are updated
[x] Helm chart is tested

LGTM - thanks for this enhancement


Puppeteer in headless mode takes empty screenshot of Canvas element, working fine in headfull mode

A clear and concise description of what the bug is.
Puppeteer in headless mode is not able to take the screenshot of a canvas element in my test app. Though while using puppeteer in non-headless mode, it's working perfectly fine.
This is my test scenario,
Press some button, it will invoke WebGL rendering on the canvas element.
(As soon as the rendering is finished source code update a div element value on the web page.)
Test code wait for the div element value to get changed
Take the screenshot of canvas element.
Repeat step 1-3 for some 'n' number of times (each time code will render something on the canvas)
On taking the screenshot, I see that sometimes the first screenshot if blank other times second. It's showing intermittent behavior. It's working fine with headful mode though.
To Reproduce
// My function to take a screenshot
async function captureScreenshotAndCompare(element: ElementHandle, fileName: string, shouldCompare: boolean = true) {
const testFile = Path.resolve(testFolder, ${fileName}.png);
// capture screenshot
const image = await element.screenshot({ path: testFile });
// compare with baseline
if(!shouldCompare) return;
expect(image).toMatchImageSnapshot({
failureThreshold: 0.1,
failureThresholdType: 'percent',
customSnapshotsDir: baselineFolder,
customDiffConfig: { threshold: 0.1 },
customSnapshotIdentifier: () => {
return fileName;
},
});
}
const canvas = await page.$('canvas[id="webgl-canvas"]');
expect(canvas).not.toBeNull();
if(!canvas) return;
await captureScreenshotAndCompare(canvas, 'Image_1', true);
let index: number = 2;
while (index <= maxCount) {
// move to next step
await nextBtn.click();
await page.waitFor(() => document.querySelector('#eventName')!.innerHTML === "rendered" );
await captureScreenshotAndCompare(canvas, Image_${index});
index += 1;
}
Steps to reproduce the behavior:
Expected behavior
The screenshot should be correct both in headless and headful mode.
A clear and concise description of what you expected to happen.
These are all the versions exist in my package.json file.
"puppeteer": "^2.0.0",
"jest-puppeteer": "4.3.0",
"jest-image-snapshot": "2.11.0"
"@types/puppeteer": "^1.19.1",
"@types/jest-environment-puppeteer": "4.3.1",
"@types/expect-puppeteer": "3.3.1",

I tried this workaround and didn't work for me.
First of all I got some simple js errors from node:
`function canvasToImage(element: HTMLCanvasElement) {`
                                                         ^

SyntaxError: Unexpected token ':'
 `const properties = ['width', 'height', 'position', 'left', 'top'] as const;`
                                                                                ^^

SyntaxError: Unexpected identifier
I'm not familiar with js nor node, maybe just some version issue. I commented out the problematic parts, run it and still it did not capture image from site https://www.kathabineider.de/.

@yxiong20  I'm using typescript, you can try this instead.
  await page.evaluate(() => {
    function canvasToImage(element) {
      const dataUrl = element.toDataURL();
      const image = document.createElement('img');
      image.src = dataUrl;

      const properties = ['width', 'height', 'position', 'left', 'top'];
      properties.forEach(key => image.style[key] = element.style[key])
      image.className = element.className;

      element.parentNode && element.parentNode.insertBefore(image, element);
      element.parentNode && element.parentNode.removeChild(element);
    }

    [].forEach.call(document.getElementsByTagName('canvas'), canvasToImage)
  })
  await page.screenshot({
    path: path.resolve(__dirname, './temp/dashboardPage.png'),
    type: 'png',
  });

Thanks @demonly.
In my case I solved the problem by adding "--use-gl=egl" to the args pass to Chrome which seems to work in headless mode.


Prevent replacing .md links on external URL's

Adjustment for logic when checking if link is external (has a hostname) in order to skip .md replacements.
Relates to issue raised on W3C website: https://github.com/w3c/w3c-website/issues/475
Previously it was continuing out if there was no path, but I don't think this is intended. Have changed this to check if a host is defined instead.

Changes for v1.0.1:

Improve legibility of code snippets, by specifying the tab size and how to handle white space for more consistent handling of indentation.
Fix issue where external links which end .md are incorrectly parsed to .html (only local links should convert .md to .html)


Grammars for articulating effects, for state machines with strongly typed transitions

Hi, I'm not familiar with the literature, and my naive searches lead to nothing so far. This may not be a new idea, if it's been experimented with I'd love get pointers. This may also be off base...
A natural extension of typed effects would be to let users articulate grammars. E.G. for file operations, with a RegExp-like syntax, Open(Read|Write)*Close would prevent one from writing to a file that hasn't been opened yet (I know there are better ways to enforce this, this is for the sake of the example).
This would enable one to ensure at compile time that a piece of code respects a given protocol (e.g. that you can't write HTTP headers while the body is being sent).

This sounds to me like session types, though those are mostly used for describing protocols between communicating clients. For a connection with effect systems, you could start with D. Orchard & N. Yoshida: Effects as sessions, sessions as effects.

Thanks @matijapretnar this is exactly what I was after (and then some).


知识库支持execl格式文件上传解析

Description
Please include a summary of the change and which issue is fixed. Please also include relevant motivation and context. List any dependencies that are required for this change.
How Has This Been Tested?
Please describe the tests that you ran to verify your changes. Provide instructions so we can reproduce. Please also list any relevant details for your test configuration
Snapshots:
Include snapshots for easier review.
Checklist:

[ ] My code follows the style guidelines of this project
[ ] I have already rebased the commits and make the commit message conform to the project standard.
[ ] I have performed a self-review of my own code
[ ] I have commented my code, particularly in hard-to-understand areas
[ ] I have made corresponding changes to the documentation
[ ] Any dependent changes have been merged and published in downstream modules

@zhenchaozhu Thanks for your PR, we have a release today, this will test  and merge at next version.


Adding bootstrap tabs

Hi,
I'm using bootstrap 4 beta in this boilerplate and updated .bootstraprc file accordingly.
Under scripts updated tab to true
"tab": true,

And in webpack dev.config.js i've added below code in plugins array
new webpack.ProvidePlugin({
      $: "jquery", // Used for Bootstrap JavaScript components
      jQuery: "jquery", // Used for Bootstrap JavaScript components
      Util: "exports-loader?Util!bootstrap/js/dist/util",
    }),

And now tabs are working.
Just want to make sure if  this is the right way to do or there is another workaround without changing the webpack config file?
Thanks

I advise you to use react-bootstrap for this: https://react-bootstrap.github.io/components/tabs/


Support asset change when updating transaction

When changing the fee in a transaction (presumably with bumpfee / RBF — are there any other cases?), we currently only support a change in fee amount, not in fee asset. We want to support changing the fee asset. [We also only currently support bumping fees on unblinded transactions, but that's for another issue, this issue is only for the change in asset.]
Note that Bitcoin, and after it Elements and Sequentia, mandates a minimum bump in fee. In Sequentia, this minimum bump should be accounted in RFU / RFA (Reference Fee Unit / Reference Fee Atom, 1 RFU = 1e8 RFA), not in the fee asset used by the transaction (unclear if already done). Test cases should include cases where the amount changes up or down or stays the same, and the value is indeed bumped enough or isn't. Test cases should also include cases where the asset (and amount?) stay the same, but the value is bumped (or isn't) because the exchange rate changed. Also note that among those cases, if the asset is unchanged and the amount doesn't increase, the value cannot increase past the positive bump and so the new transaction should be rejected.

Already impelmented in bumpfee in #30


Fix BrowserStack CI or find a replace

Prerequisites

[X] I have searched for duplicate or closed issues
[X] I have validated any HTML to avoid common problems
[X] I have read the contributing guidelines

Describe the issue
As browserstack ci fails at 98% of the runs, we must find a way to fix it or to replace it, as now we are used to ignoring it by default.
Reduced test cases
Almost all the PR CI runs
What operating system(s) are you seeing the problem on?
Linux
What browser(s) are you seeing the problem on?
Firefox, Opera
What version of Bootstrap are you using?
all

i looked into this issue. what you suggest @GeoSot ,with my local test its good to know on which browser functionality is breaking
but I think a good idea would be to add priority on browser? that show if it is good enough to merge


Fix bootrap command generating duplicate namespace entries in kustomization.yaml

What type of PR is this?
/kind bug
What does this PR do / why we need it:
This PR fixes https://issues.redhat.com/browse/GITOPS-674
Have you updated the necessary documentation?

[ ] Documentation update is required by this PR.
[ ] Documentation has been updated.

Which issue(s) this PR fixes:
Fixes #?
https://issues.redhat.com/browse/GITOPS-674
How to test changes / Special notes to the reviewer:

Follow https://github.com/redhat-developer/kam/tree/master/docs/journey/day1 to install GitOps Operator and Sealed Secret.
kam bootstrap to generate GitOps configuration using Smart Defaults.  The key is to use the default internal image registry with namespace cicd.
Verify that the generated /config/cicd/base/kustomization.yanl has NO duplicate entries in particular no duplicate entries for 01-namespaces/cicd-environment.yaml
Proceed to the steps in Day 1 operator to push configuration to GitOps repository and execute oc apply -f <gitops>/config/argocd
Login to Argo CD UI and verify that all argod apps (in particular cicd-app) are successfully sync'ed.

// copied from How to test changes / Special notes to the reviewer:
2. kam bootstrap to generate GitOps configuration using Smart Defaults. The key is to use the default internal image registry with namespace cicd.

My question is not related to this pr validation. @wtam2018 you can address it in a separate issue
Question -
Setting up prerequisite for Day 1 operation is a valid usecase when the default internal OpenShift registry is used, but i could not find a doc reference. As part of external registry quay is concerned, its properly documented - https://github.com/redhat-developer/kam/blob/master/docs/journey/day1/prerequisites/quay.md. Can we have similar document for internal registry too ?

// copied from How to test changes / Special notes to the reviewer:
2. kam bootstrap to generate GitOps configuration using Smart Defaults. The key is to use the default internal image registry with namespace cicd.

My question is not related to this pr validation. @wtam2018 you can address it in a separate issue
Question -
Setting up prerequisite for Day 1 operation is a valid usecase when the default internal OpenShift registry is used, but i could not find a doc reference. As part of external registry quay is concerned, its properly documented - https://github.com/redhat-developer/kam/blob/master/docs/journey/day1/prerequisites/quay.md. Can we have similar document for internal registry too ? cc_ @dewan-ahmed

Here is a doc on OpenShift Internal Registry.
https://docs.openshift.com/container-platform/4.6/registry/accessing-the-registry.html

My question is not related to this pr validation. @wtam2018 you can address it in a separate issue

@amitkrout What would you like me to address?

My question is not related to this pr validation. @wtam2018 you can address it in a separate issue

@amitkrout What would you like me to address?

@wtam2018 Steps similar to https://github.com/redhat-developer/kam/blob/master/docs/journey/day1/prerequisites/quay.md for internal registry

My question is not related to this pr validation. @wtam2018 you can address it in a separate issue

@amitkrout What would you like me to address?

@wtam2018 Steps similar to https://github.com/redhat-developer/kam/blob/master/docs/journey/day1/prerequisites/quay.md for internal registry

@wtam2018 Do we need such steps for OpenShift internal registry ?

My question is not related to this pr validation. @wtam2018 you can address it in a separate issue

@amitkrout What would you like me to address?

@wtam2018 Steps similar to https://github.com/redhat-developer/kam/blob/master/docs/journey/day1/prerequisites/quay.md for internal registry

@wtam2018 Do we need such steps for OpenShift internal registry ?
@amitkrout OS internal registry is built-in.   No setup of tokens or user accounts is needed.   It uses role/role bindngs to do access control which is set up by kam.

See https://github.com/redhat-developer/kam/pull/174


fix libm not getting used when building

this is needed for AIX/PASE

The failures from Travis are unrelated. Merging.


Common response/payload object but different data defined per API?

What is the best way to represent a generic response/payload object that has basic fields such as message, total elements, data, and status?  Where the variability between each API is the data element.  For instance, one API could be for permissions, so the data element would hold an array of permissions.  But for another API, it would hold a different array of object types.  My main goal is to have reuse with a payload object and to define the next "layer" of actual data.
Here are some JSON samples of what's been attempted but isn't rendering the way we would expect it to in Swagger UI (i.e. a flat structure of 4 elements with data defined per the API).
Example 1 - composition:
{
    "swagger": "2.0",
    "host": "localhost:8888",
    "info": {
        "version": "0.0.1",
        "title": "API"
    },
    "paths": {
        "/permissions": {
            "get": {
                "description": "Returns all permissions",
                "operationId": "getPermissions",
                "produces": [
                    "application/json"
                ],
                "responses": {
                    "200": {
                        "description": "success",
                        "schema": {
                            "$ref": "#/definitions/permissionResponse"
                    }
                }
            }
        }
        }
    },
    "definitions": {
       "response": {
           "type": "object",
           "properties": {
              "message": {
                "type": "string",
                "description": "A string indicating the response from the server."
              },
              "totalElements": {
                "type": "integer",
                "format": "int64",
                "description": "The number of items retrieved."
              },
              "status": {
                "type": "string",
                "description": "A string indicating the response from the server."
              }
            }
        },
       "permissionResponse": {
         "allOf": [
                   {
          "$ref": "#/definitions/response"
        },{
           "type": "object",
           "properties": {
              "data": {
                "type": "array",
                "description": "The collection of items returned from the API request.",
                "items": {
                  "$ref": "#/definitions/permission"
                }
              }
            }
        }
            ]
        },
       "permission": {
            "type": "object",
            "properties": {
                "id": {
                    "type": "integer",
                    "format": "int64",
                    "description": "Unique identifier representing a specific permission."
                },
                "label": {
                    "type": "string",
                    "description": "The label of a permission."
                },
                "description": {
                    "type": "string",
                    "description": "A description of the permission."
                },
                "active": {
                    "type": "boolean",
                    "description": "A flag indicating whether a permission is active."
                }
            },
        "required": [
          "id",
          "label",
          "description",
          "active"
        ]
        }
    }
}

Example 2 - composition variation:
{
    "swagger": "2.0",
    "host": "localhost:8888",
    "info": {
        "version": "0.0.1",
        "title": "API"
    },
    "paths": {
        "/permissions": {
            "get": {
                "description": "Returns all permissions",
                "operationId": "getPermissions",
                "produces": [
                    "application/json"
                ],
                "responses": {
                    "200": {
                        "description": "success",
                        "schema": {
                            "$ref": "#/definitions/permissionResponse"
                    }
                }
            }
        }
        }
    },
    "definitions": {
       "response": {
           "type": "object",
           "properties": {
              "message": {
                "type": "string",
                "description": "A string indicating the response from the server."
              },
              "totalElements": {
                "type": "integer",
                "format": "int64",
                "description": "The number of items retrieved."
              },
              "status": {
                "type": "string",
                "description": "A string indicating the response from the server."
              }
            }
        },
       "permissionResponse": {
          "allOf":[
            {
              "$ref": "#/definitions/response" }        ],
           "type": "object",
           "properties": {
              "data": {
                "type": "array",
                "description": "The collection of items returned from the API request.",
                "items": {
                  "$ref": "#/definitions/permission"
                }
              }
            }
        },
       "permission": {
            "type": "object",
            "properties": {
                "id": {
                    "type": "integer",
                    "format": "int64",
                    "description": "Unique identifier representing a specific permission."
                },
                "label": {
                    "type": "string",
                    "description": "The label of a permission."
                },
                "description": {
                    "type": "string",
                    "description": "A description of the permission."
                },
                "active": {
                    "type": "boolean",
                    "description": "A flag indicating whether a permission is active."
                }
            },
        "required": [
          "id",
          "label",
          "description",
          "active"
        ]
        }
    }
}

Example 3 - additional properties:
{
    "swagger": "2.0",
    "host": "localhost:8888",
    "info": {
        "version": "0.0.1",
        "title": "API"
    },
    "paths": {
        "/permissions": {
            "get": {
                "description": "Returns all permissions",
                "operationId": "getPermissions",
                "produces": [
                    "application/json"
                ],
                "responses": {
                    "200": {
                        "description": "success",
                        "schema": {
                            "$ref": "#/definitions/permissionResponse"
                    }
                }
            }
        }
        }
    },
    "definitions": {
       "response": {
           "type": "object",
           "properties": {
              "message": {
                "type": "string",
                "description": "A string indicating the response from the server."
              },
              "totalElements": {
                "type": "integer",
                "format": "int64",
                "description": "The number of items retrieved."
              },
              "status": {
                "type": "string",
                "description": "A string indicating the response from the server."
              }
            }
        },
       "permissionResponse": {
           "type": "object",
           "properties": {
              "data": {
                "type": "array",
                "description": "The collection of items returned from the API request.",
                "items": {
                  "$ref": "#/definitions/permission"
                }
              }
            },
            "additionalProperties": {
              "$ref": "#/definitions/response"
            }
        },
       "permission": {
            "type": "object",
            "properties": {
                "id": {
                    "type": "integer",
                    "format": "int64",
                    "description": "Unique identifier representing a specific permission."
                },
                "label": {
                    "type": "string",
                    "description": "The label of a permission."
                },
                "description": {
                    "type": "string",
                    "description": "A description of the permission."
                },
                "active": {
                    "type": "boolean",
                    "description": "A flag indicating whether a permission is active."
                }
            },
        "required": [
          "id",
          "label",
          "description",
          "active"
        ]
        }
    }
}

If I understand right, you want support for generic data types.
Apart from simple maps (with string keys, being represented as JSON objects) or lists (being represented as JSON arrays), OpenAPI doesn't support that yet.
A related issue I found is #519.

@ePaul , yes sort of.  I want to be able to define a data type that's generic - like a "response" that has basic fields but I want to be able to further define that content for each API (data containing permissions or roles or whatever).
The composition concept in Swagger (example 1 above) works great when I run it through swagger2markup and renders the content as I would hope/expect.  SwaggerUI represents it as multiple objects and some nesting as a part of it too, so it's rather odd and confusing.  This leaves me questioning if it's an issue with SwaggerUI, my Swagger structure, or something else.  So trying to figure out the best way to represent the scenario in Swagger.
Markup rendered:

Swagger UI rendered:

Swagger UI rendered - expanded:

will this to be supported in future?

I am evaluating this as a possible use case for overlays, https://github.com/OAI/Overlay-Specification/discussions/9.
I don't think overlays are needed here. I believe this can be represented in openapi3 as example (I did not test this)
{
  "openapi": "3.0.1",
  "info": {
    "title": "API",
    "version": "1.0"
  },
  "paths": {
    "/permissions": {
      "get": {
        "description": "Returns all permissions",
        "operationId": "getPermissions",
        "responses": {
          "200": {
            "description": "success",
            "content": {
              "application/json": {
                "schema": {
                  "$ref": "#/components/schemas/permissionResponse"
                }
              }
            }
          }
        }
      }
    }
  },
  "components": {
    "schemas": {
      "permissionResponse": {
        "type": "object",
        "properties": {
          "message": {
            "type": "string",
            "description": "A string indicating the response from the server."
          },
          "totalElements": {
            "type": "integer",
            "description": "The number of items retrieved.",
            "format": "int64"
          },
          "status": {
            "type": "string",
            "description": "A string indicating the response from the server."
          },
          "data": {
            "type": "array",
            "description": "The collection of items returned from the API request.",
            "items": {
              "oneOf": [
                {
                  "$ref": "#/components/schemas/permission",
                },
                {
                  "$ref": "#/components/schemas/role"
                }
              ]

            }
          }
        }
      },
      "role": {
        "type": "object",
        "properties": {
          "roleName": {
            "type": "string"
          },
          "description": {
            "type": "string"
          }
        }
      },
      "permission": {
        "required": [
          "active",
          "description",
          "id",
          "label"
        ],
        "type": "object",
        "properties": {
          "id": {
            "type": "integer",
            "description": "Unique identifier representing a specific permission.",
            "format": "int64"
          },
          "label": {
            "type": "string",
            "description": "The label of a permission."
          },
          "description": {
            "type": "string",
            "description": "A description of the permission."
          },
          "active": {
            "type": "boolean",
            "description": "A flag indicating whether a permission is active."
          }
        }
      }
    }
  }
}

which looks like this at editor.swagger.io

This has been supported in OAS 3.1 by using dynamic references to implement generic types.


Add a wiki: Conker Wiki

An anonymous user has submitted a new wiki via our submission form.
Link to origin wiki: https://conker.fandom.com/wiki/Conker_Wiki
Link to destination (independent) wiki: https://conkerwiki.com/wiki/Main_Page

438 vs. 243 articles, will need to take a closer look on coverage.


[Good First Issue]: Replicate Existing Cookbooks and Create New Examples - Batch 4

For context, see: CONTRIBUTING.md and cookbooks/README.md

Overview
We're looking for contributors to help expand our collection of Jupyter notebooks (cookbooks) that demonstrate various AI and automation tasks using Julep's features. This is a great opportunity for newcomers to get familiar with Julep and contribute to the project!
Objectives

Replicate existing cookbooks to ensure they're up-to-date and functioning correctly.
Create new cookbooks based on the ideas listed in the cookbooks/README.md file.

Tasks
1. Replicating Existing Cookbooks

Choose one or more of the existing cookbooks from the list in cookbooks/README.md.
Follow the instructions in the notebook to run it in Google Colab.
Verify that all cells execute without errors and produce the expected outputs.
If you encounter any issues or outdated information, document them for updating.

2. Creating New Cookbooks

Select an idea from the "Potential Cookbooks for Contributors" section in cookbooks/README.md.
Create a new Jupyter notebook following the structure of existing cookbooks.
Implement the chosen use case using Julep's features.
Ensure your notebook includes:

A clear introduction and overview of the task
Step-by-step implementation with explanations
Proper error handling and user guidance
A conclusion summarizing the key learnings

Guidelines for Creating New Cookbooks

Naming Convention: Name your notebook following the pattern XX-Descriptive_Name.ipynb, where XX is the next available number in the sequence.

Structure:

Start with an introduction explaining the purpose of the cookbook.
Include a cell for installing the Julep client.
Create sections for each major step (e.g., Creating an Agent, Defining a Task, Creating an Execution).
Add markdown cells to explain concepts and code.

Code Quality:

Ensure your code is well-commented and follows PEP 8 style guidelines.
Use meaningful variable names.
Handle potential errors gracefully.

Documentation:

Explain each step clearly, assuming the reader is new to Julep.
Include links to relevant Julep documentation where appropriate.

Testing:

Test your notebook thoroughly in Google Colab to ensure it runs without errors.
Include sample outputs where relevant.

Update README.md:

Add your new cookbook to the table in cookbooks/README.md.
Include a brief description and mark it as implemented.

How to Contribute

Fork the repository.
Create a new branch for your cookbook (e.g., cookbook/weather-notification-service).
Develop your cookbook following the guidelines above.
Test your notebook thoroughly.
Commit your changes and push to your fork.
Open a pull request with a clear description of your contribution.

Resources

Julep Documentation
Existing Cookbooks
CONTRIBUTING.md

Need Help?
If you have any questions or need assistance, please don't hesitate to ask in the comments of this issue or reach out on our Discord channel.
We're excited to see your contributions and help grow the Julep cookbook collection!

Long-ass list of ideas

Personal Finance Tracker and Advisor
Description: Tracks user expenses, analyzes spending patterns, and provides financial advice based on data.
Features:
Tools: finance, sendgrid
Step Types: Tool Call, Evaluate, Conditional Logic, Set Budgets (Set), Send Advice (Prompt), Log
Automated Content Publishing Workflow
Description: Creates, schedules, and publishes content to various platforms, ensuring consistency and timely updates.
Features:
Tools: twitter, google_calendar, sendgrid
Step Types: Tool Call, Evaluate, Conditional Logic, Schedule Posts (Set), Publish Content (Tool Call), Log
AI-Powered Personal Assistant
Description: Manages personal tasks, schedules appointments, sends reminders, and interacts through chat.
Features:
Tools: google_calendar, slack, sendgrid, weather
Step Types: Chat, Tool Call, Evaluate, Conditional Logic,
Set Reminders (Set), Schedule (Sleep), Log
Automated Bug Tracking and Reporting System
Description: Monitors repositories for new issues, categorizes them, assigns them to developers, and sends notifications.
Features:
Tools: slack, api_call, sendgrid
Step Types: Tool Call, Evaluate, Conditional Logic, Assign Issues (Set), Send Notifications, Log
Multi-Stage Data Validation Pipeline
Description: Validates incoming data through multiple stages, applying different validation rules and cleaning steps before final acceptance.
Features:
Tools: huggingface, wikipedia
Step Types: Tool Call, Evaluate, Conditional Logic, Transform Data (Set), Log, Return
Intelligent Document Summarization and Archiving
Description: Summarizes lengthy documents, categorizes them, and archives the summaries for easy retrieval.
Features:
Tools: wikipedia, dalle
Step Types: Tool Call, Evaluate, Conditional Logic, Set, Log, Return
Real-Time Stock Market Analysis and Alerting
Description: Analyzes real-time stock market data, identifies trends, and alerts users about significant changes.
Features:
Tools: finance, slack
Step Types: Tool Call, Evaluate, Conditional Logic, Send Alert, Loop, Log
Automated Webinar Scheduling and Management
Description: Schedules webinars based on participant availability, sends reminders, and manages follow-up communications.
Features:
Tools: google_calendar, sendgrid, slack
Step Types: Tool Call, Evaluate, Conditional Logic, Create Event (Set), Send Reminders, Log

i can work on this

@ijindal1  can you assign this issue to me

Hey @prathamesh424 @PRIYANKjakharia - it hink you guys have already shown interest in a lot of demos. Please pick one and work on that first. :)

May I please have this issue assigned to me


Please Update Logparser to v.2.1.1

Also changed the url in latest repo to the new community repo

thank you!


Rename commands from deploy/undeploy to create/delete

Changes the commands to create/delete rather than deploy/undeploy.
Similar to the concepts of kubectl.

Hey @pradeepto I've gone ahead and added the documentation changes to this PR.


chore(ci): use non-root user

What's changed and what's your intention?
PLEASE DO NOT LEAVE THIS EMPTY !!!
Please explain IN DETAIL what the changes are in this PR and why they are needed:

Summarize your change (mandatory)
How does this PR work? Need a brief introduction for the changed logic (optional)
Describe clearly one logical change and avoid lazy messages (optional)
Describe any limitations of the current code (optional)
Add the 'user-facing changes' label if your PR contains changes that are visible to users (optional)

Checklist

[ ] I have written necessary docs and comments
[ ] I have added necessary unit tests and integration tests
[ ] All checks passed in ./risedev check (or alias, ./risedev c)

Refer to a related PR or issue link (optional)

need rebuild CI image with a user :(

Any updates? Shall we close this?

I think we should move forward to use non-root user for CI. But as now we have so many conflicts, I'd like to open a new issue.


Rich Text Implementation?

Thinking about switching from JavaFX to compose for desktop. One of the most frustrating things I encountered was having to implement a rich text implementation in JavaFX with RichTextFX (fonts/bold/itallic/underline/bullet point lists/paragraph alignment etc).
Does compose for desktop have a rich text implementation and if not is the library mature enough that it would be possible to implement it?

@SKeeneCode there is no RT component in Compose at the moment. However it should be possible to implement it using current API.

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


No contribute section

Expected Behavior
There should be a how to contribute section to help newcomers to the project get onboard easily
Current Behavior

Possible Solution
I would like to add a how to contribute section.
Context
It has been kind of hard knowing how to contribute since there is no contribute section compared to other open source projects.

That would be great! Thanks, @mikey2020 :smiley:

That's a great idea @mikey2020
One caveat, we are just now in the process of rewriting Captain completely.
Please hold off on creating this document as it will become obsolete within days if you make it now.

ok @TalAter I will hold off until the changes are completed

Now in #120

Fixed in #123


Migrate to Tigris' alpha.26

Tigris released alpha.26 with some crucial bug fixes (e.g. for the bugs we experienced in #900) - https://github.com/tigrisdata/tigris/releases/tag/v1.0.0-alpha.26.
Let's migrate to the newer Docker image when it's ready.

@AlekSi I guess we only update the Docker image tag, not the client version. Right?


4/1/22 Auto Fixes

Various auto fixes made while testing each mode.

This isn't the most important, but would using src/main/deploy and Filesystem (specifically getDeployDirectory()) be better?
A potential benefit would be that it would be impossible to forget to copy the images to the device, but putting ~8 MB of images into the deploy directory could affect deploy times.

I'd love to do that. It actually wouldn't affect deploy times too much because I believe the deploy task checks if files it's trying to deploy are already on the bot, meaning it would only be slow once, during the first deploy.
However, since the shuffleboard plugin executes through shuffleboard and not on the robot, it doesn't really have easy access to any files on the actual bot :(

I'd love to do that. It actually wouldn't affect deploy times too much because I believe the deploy task checks if files it's trying to deploy are already on the bot, meaning it would only be slow once, during the first deploy. However, since the shuffleboard plugin executes through shuffleboard and not on the robot, it doesn't really have easy access to any files on the actual bot :(

Ah, okay, that makes sense.


how can i build a release configuration in Windows?

I've tried editing the do-cmake.bat to pass in -DCMAKE_BUILD_TYPE=Release when creating the build or --target Release in conjunction with the --build parameter but in either scenarios, it's creating a debug build which requires VCRUNTIME140D.dll. From what I've gathered, this DLL cannot be redistributed. Where can I find a release build so I only need to install the publicly available vcredist to run lagscope.exe for Windows?

I'm not immediately sure how to do cmake release build.  Can you meanwhile ignore this cmake build and remove src/CMakeLists.txt do normal visual studio release build?
Visual studio -> File -> New -> Project from existing sources.

Actually, that didn't work. What did work was opening Visual Studio -> Open -> Folder and selecting the the src folder. By default it creates a debug build in folder in c:\users<username>\CMakeBuilds<guid>\build\x64-Debug (default). You could then change configuration from x64-Debug to x64-Release. This will create another build subfolder called x64-Release. Right click on CMakeLists.txt after switching configuration and select Build lagscope.exe.
My folder structure looks like this.


Tab bar "scrolling"

Is your feature request related to a problem? Please describe.
The problem arises when there are too many tabs to fit in the horizontal space. At the moment, if I keep opening tabs at some point the status line "overflows" or scrolls to the left and shows only the part that has overflowed.
Describe the solution you'd like
I know one solution is to set the precedence of some parts to hide when they overlap, but this would be another solution to this problem:
It would be nice if instead of having to hide parts, there would be a "virtual" tab created on the left or the right signifying how many more tabs there are that cannot be shown at the moment. In fact, this is how vanilla Zellij handles it, there is a small tab with "+x tabs" created when there are too many to show.
Additional context
Please excuse me if that is already possible, I tried to find documentation to do that but couldn't find it.

Just to add an option, shrinking the tabs (trimming the rightmost characters from {name}) is another option which would be nice.  I have a prompt that sets the tab name to a shortened path which runs me up against this issue fairly often.

Hi and thanks for your feature request and ideas. Unfortunately it will be not that easy, since everything is rendered in order, such that we cannot really say, how much space a widget can/should occupy. Therefore it's not really easy to implement a logic based on the size. It would also mean, that other widgets should also gain this functionality, which will impose the problem of priorities.
As this gets complex quite quickly, we could implement the scrolling behavior based on the tab count. Basically everything above a configurable amount of tabs will be hidden. This simplifies the logic and will introduce the missing feature. However, this would not adapt to different screen sizes.

I've implemented it now with the option to limit the tab count, as it's not really possible to limit it by size due to the flexibility and dynamic rendering of zjstatus. It will be released with the next version. Here's a sneak peak. It's also possible to navigate between the tabs with the indicators.
https://github.com/dj95/zjstatus/assets/4348959/b7698dbf-e4ac-4728-92e7-4088889022cd
Hopefully it suffices your feature request.

Forgot to mention, that you can of course specify the count in the indicator :)
https://github.com/dj95/zjstatus/assets/4348959/7cbf3407-eaa1-4ce6-99e7-b63921d28e91

Thank you!


Redirects to example.com when doing NODE_ENV=production node app.js

Sails version: "sails": "^1.0.2",
Node version: v10.1.0
NPM version: 5.6.0
DB adapter name: "sails-postgresql":
DB adapter version: "^1.0.1"
Operating system: mac OS HighSierra 10.13.4 (17E202)

Hi everyone!
In dev mode everything works great, but when on production mode, somehow sails redirects me to https://example.com
Not sure, why. Any ideas?

@mikermcneil?

Hi, I'm sorry to insist, but I need to pass to prod and I have this problem 😢.

Commenting this line did the trick.
baseUrl: 'https://example.com',


Feature Request: Daily Note Improvements

Is your feature request related to a problem? Please describe.
Currently the daily note requires absolute referencing but the advanced URI functionality allows for daily note based querying. I have a macro that sets up a daily note folder. This means that the daily note path changes per day: /path-to-daily-note-folder/YYYY-MM-DD/YYYY-MM-DD.md
Describe the solution you'd like
I've manually changed the od command to handle this but i think that it should be the default functionality

This URI will open the daily note regardless of the path.
obsidian://advanced-uri?&daily=true

Advanced URI also allows specification of the vault incase there is a more flexibility that is required. Currently, the above command will default to the currently open vallt

Ah, I have the same issue with a different folder structure (/path-to-daily-note-folder/YYYY/MM/YYYY-MM-DD.md), and I didn't know about the Advanced URI solution -- that's great. Making this the default model, or more easily configured, would be great. Thanks!

Particularly trick to solve the append to daily note workflow, as well.

Shouldn't be too hard, I'll look into it when I continue working on this workflow!

As daily notes are by far the Number 1 request, I'll tackle a comprehensive daily note implementation for version 3.0. I am pinning this to avoid duplicate issues. :)

I am sorry to say that I feel a bit uneasy to work on and maintain the daily note feature – since I personally do not use daily notes myself, I would have to rely on someone else to maintain this, which probably isn't worth the effort. However, the Alfred workflow by hauselin does focus a lot more on daily note features, and can be used alongside this workflow without any issue.
Therefore, I think it makes more sense to make a feature request for that hauselin's workflow.

well, as I said, I don't use daily notes, and therefore have neither interest nor competence to implement such a feature (considering all special cases there are, with date formats, weekly notes etc.)
I'd be open if anyone wants to contribute and maintain a daily note feature for this plugin, though.


Draft of the Amazon RDS quick info card

Description
Amazon RDS quick info card for limitations and known issues when using RDS as a provider account and RDS database instances.  From the import provider account page when Amazon RDS is selected as the provider account, you could add a link to this quick info card (tile) to warn users about potential pitfalls.
Type of change

[ ] New doc (non-breaking change which adds functionality)

Checklist (Definition of Done)

[ ] All acceptance criteria specified in JIRA or in issue number have been completed
[ ] Unit tests added that prove the fix is effective or the feature works
[ ] Documentation added for the feature
[ ] all relevant tests are passing
[ ] Code Review completed
[ ] Verified independently by reviewer

Checklist (Definition of Done)

[ ] All acceptance criteria specified in JIRA or in issue number have been completed
[ ] Unit tests added that prove the fix is effective or the feature works
[ ] Documentation added for the feature
[ ] all relevant tests are passing
[ ] Code Review completed
[ ] Verified independently by reviewer

Design has gone in a different direction given the technical limitations of quick start console implementation, so not sure we'll utilize this PR soon. Going to close for now, but we can always recreate once console has the changes we need for implementation - that way, we won't have to work out rebase, etc. to catch the PR when it's time.


Add a version command

It would be helpful if there was a command which printed out the version of the tool. Then when you update, you can easily check you're running the new version.
eg something like this:
$ dbt version
dbt version dbt0.0.2

Added in v0.1.11


Stuck on Model Building Cell

Hello!
I'm using lightning pose for my project, but it got stuck on the cell for model building and won't run through. I downloaded Lightning Pose using the conda from source installation method. I've tried running the command from the terminal and also breaking it down step by step in Jupyter (like the one used in demo on Colab).
Here's what I got when I ran this cell in Jupyter:

Thank you in advance!
Happy holidays!
Alan

Alan, happy holidays and thanks for reporting this.
It seems like there it is stuck for two hours (instead of a few seconds) without showing any errors 🙃
What machine are you running this on? do you mind running pytest -vvv and copy/pasting the outputs here?
Dan

Thanks for your reply! I'm using centos9 with cuda11.
Here's what I got from running pytest -vvv :

we haven't explicitly tested before on centos9. do you mind breaking down the commands in the jupyter notebook and reporting which one is the one that is stuck?

@wddwxq just wanted to check in and see if you still need help with this. Two of your pytest errors are known (https://github.com/mrdbourke/pytorch-deep-learning/issues/696#issuecomment-1776124098), the third is something I've seen related to ffmpeg - but shouldn't affect model training at least. Are you still having issues with training a model?

closing due to inactivity


Smoke Tests Codegen Working

Issue #, if available:
Description of changes:
Check all that applies:

[x] Did a review by yourself.
[ ] Added proper tests to cover this PR. (If tests are not applicable, explain.)
[ ] Checked if this PR is a breaking (APIs have been changed) change.
[ ] Checked if this PR will not introduce cross-platform inconsistent behavior.
[ ] Checked if this PR would require a ReadMe/Wiki update.

Check which platforms you have built SDK on to verify the correctness of this PR.

[x] Linux
[x] Windows
[ ] Android
[ ] MacOS
[ ] IOS
[ ] Other Platforms

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

resending

Left some comments, have some concerns around exception handling and the structure of some of the operations. but overall the execution pattern looks good, just need to refactor some things.
also in the future make sure to remove commented code, system outs, and white space changes before marking the PR as ready to review

Addressed all the comments that were brought up. If there are some things missed, I will address


Make removeOnComplete configurable

It'd be nice for the removeOnComplete option to be a configuration option. I might submit a PR shortly.

closed by https://github.com/nrempel/adonis-kue/pull/12


NOISSUE - Add health check for MQTT broker

Signed-off-by: Ivan Milosevic<EMAIL_ADDRESS>What does this do?
If health-check path is set, mqtt adapter will wait that path is up and returning 200 status code. For VerneMQ health-check path is /health so it's default in docker composition where VerneMQ is used.
Which issue(s) does this PR fix/relate to?
Related to  issue in mProxy repo

Codecov Report

Merging #1305 (fc99848) into master (9864b27) will increase coverage by 0.02%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #1305      +/-   ##
==========================================
+ Coverage   64.65%   64.67%   +0.02%
==========================================
  Files         117      117
  Lines        8029     8029
==========================================
+ Hits         5191     5193       +2
+ Misses       2383     2381       -2
  Partials      455      455

Impacted Files
Coverage Δ

things/service.go
54.28% <0.00%> (+1.14%)
:arrow_up:

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 9864b27...fc99848. Read the comment docs.

bunch of files are removed from vendor directory after
go mod vendor

bunch of files are removed from vendor directory after
go mod vendor


Sampling Rate differences

I am training on the pre-trained model with my own dataset which is about 7 hours of audio with sampling rate = 16000 with a batch size of 32. Will model give some good results if I train on sampling rate = 16000 or do I need to resample my data at 22050 for getting good results?

After training for nearly 100 iterations, the results are noises only. Do I need to change anything in Inference notebook other than sampling rate =16000?

I think if you are using a pretrained model (ljspeech?) you should resample
to 22050. I have also had similar issues with Arctic which is at 16 khz.
pravn.wordpress.com
On Thu, May 30, 2019, 10:55 PM akshit-mittal-1<EMAIL_ADDRESS>wrote:

After training for nearly 100 iterations, the results are noises only. Do
I need to change anything in Inference notebook other than sampling rate
=16000?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/NVIDIA/tacotron2/issues/210?email_source=notifications&email_token=AAEGOVM72K333O4LWL4OVP3PYC4W5A5CNFSM4HQ46FKKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODWUI33Y#issuecomment-497585647,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAEGOVOHHUU72OEH44ZOUFTPYC4W5ANCNFSM4HQ46FKA
.

Hi, I first trained my model with 16khz with my data. After nearly 100 epochs, results were very good, I could hear the text which I was giving as input but the problem coming was that output audio was very fast, I mean words were spoken very fast.


armcord: init at 3.0.7

Description of changes
ArmCord is a custom client designed to enhance your Discord experience while keeping everything lightweight.
Things done

Built on platform(s)

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

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

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

[ ] Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
[X] Tested basic functionality of all binary files (usually in ./result/bin/)
22.11 Release Notes (or backporting 22.05 Release notes)

[ ] (Package updates) Added a release notes entry if the change is major or breaking
[ ] (Module updates) Added a release notes entry if the change is significant
[ ] (Module addition) Added a release notes entry if adding a new NixOS module
[ ] (Release notes changes) Ran nixos/doc/manual/md-to-db.sh to update generated release notes

[X] Fits CONTRIBUTING.md.

Built and tested (superficially) on x86_64-linux (NixOS).
Application builds and starts fine, and selecting a client mod works.

Hmm, not a fan of the giant let-block. Could this be structured more like most derivations, rather than putting the whole thing in a let-block?

Hmm, not a fan of the giant let-block. Could this be structured more like most derivations, rather than putting the whole thing in a let-block?

I modeled it after the slack client with the assumption that I would add darwin support in the future (just don't currently have an environment to test it, so I was not comfortable submitting it).
If that is not a good enough reason to keep it the way it is now, I am happy to modify it and add whatever paradigm is needed to support darwin in the future.

Also, welcome!

Thanks!

Oh, one more thing: the addition to maintainers should be a separate commit (I'd say it,'s also documented like that). And I guess the rest of the commits can then be squashed in one init commit


Dynamically setting log level does not update DDOSLogger (or other library-provided loggers)

Checklist

[x] I have read and understood the CONTRIBUTING guide
[x] I have read the Documentation
[x] I have searched for a similar issue in the project and found none

Describe the bug
We are trying to use dynamic log levels in order to set level for all registered Lumberjack loggers. However, when trying to utilize the DDLog methods for retrieving (registeredClassNames, registeredClasses) and configuring log levels (setLevel), we are not observing the built-in DDOSLogger as supporting this feature. We have a feature in our app to change log levels dynamically and want to extend this to the built-in loggers.
To Reproduce

In AppDelegate, register the library-provided DDOSLogger (as well as any other desired loggers):[DDLog addLogger:[DDOSLogger sharedInstance]];
[DDLog addLogger:[CustomLogger alloc]];

Try and retrieve all registered classes:NSArray *registeredClassNames = [DDLog registeredClassNames];
NSLog(@"registeredClassNames: %@", registeredClassNames); // <----- does not include DDOSLogger!

NSArray *registeredClasses = [DDLog registeredClasses];
for (Class class in registeredClasses) { } // <-----registeredClasses does not include DDOSLogger!

Expected behavior
Our expectation is that DDOSLogger would support dynamic logging out of the box, so that its log level can be dynamically configured in the same way as any other custom logger.
There are scenarios where sensitive data may be logged and it would be undesirable to log these to the built-in loggers.
Environment info

Info
Value

Platform Name
ios

Platform Version
15.0

CocoaLumberjack Version
3.8.1

Integration Method
cocoapods

Xcode Version
Xcode 15.0

Repro rate
all the time (100%)

Repro project link
n/a

Additional context
It appears the built-in/provided loggers do not support this feature (we believe this same problem applies to other library loggers besides DDOSLogger).

Registered dynamic logging is a very advanced feature, that is not intended for loggers themselves (or at least not most of them). Thus none of the built-in loggers have the required methods. As described in the documentation you linked, it's basically based on two class methods: +ddLogLevel and + ddSetLogLevel:.
Furthermore, it's only used to give users of CocoaLumberjack the option to easily list all classes that use registered dynamic logging. CocoaLumberjack itself does not do much with it - except for collecting the classes when you ask for them, as well as calling the two methods when you use setLevel:forClass: or levelForClass:.


Find a better way to display game tabs.

Tabs are overflowing in default mode. Looks fine in dark mode.
Default mode has a lot of padding next the text which I don't know how to adjust.

Would something like this work ? https://doc.qt.io/qt-6/qtwidgets-mainwindows-menus-example.html

You want a menu dropdown? Or a QComboBox?

https://github.com/PokemonAutomation/Arduino-Source/commit/d225e6e7453c3c6d38bbc18fd0e7c08b11c44030


Error in workflow zmin.calendar

I just tried the workflow this morning and I got this error:
Starting debug for 'Calendar'
 [ERROR: alfred.workflow.input.scriptfilter] Code 1: 09:14:33 workflow.py:1945 DEBUG    Workflow version : 1.2.0
09:14:33 workflow.py:1951 ERROR    No JSON object could be decoded
Traceback (most recent call last):
  File "workflow/workflow.py", line 1946, in run
    func(self)
  File "main.py", line 37, in main
    self.init_settings()
  File "main.py", line 27, in init_settings
    self.minus = self.wf.settings.setdefault('minus', self.minus_default)
  File "workflow/workflow.py", line 1378, in settings
    self._default_settings)
  File "workflow/workflow.py", line 802, in __init__
    self._load()
  File "workflow/workflow.py", line 813, in _load
    for key, value in json.load(file_obj, encoding='utf-8').items():
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/__init__.py", line 290, in load
    **kw)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/__init__.py", line 351, in loads
    return cls(encoding=encoding, **kw).decode(s)
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/decoder.py", line 365, in decode
    obj, end = self.raw_decode(s, idx=_w(s, 0).end())
  File "/System/Library/Frameworks/Python.framework/Versions/2.7/lib/python2.7/json/decoder.py", line 383, in raw_decode
    raise ValueError("No JSON object could be decoded")
ValueError: No JSON object could be decoded
09:14:33 workflow.py:1969 DEBUG    Workflow finished in 0.429 seconds.

Hi @politicus,
Looks like it caused by a broken JSON file. Can you paste the content of the file "~/Library/Application Support/Alfred 2/Workflow Data/zmin.calendar/settings.json"? Thanks a lot.
Also, a quick workaround is delete that file and back to the default settings. Please backup the file first if you have some important settings.
Owen

The .json file is empty.

Yes, an empty file will cause the issue. Deleting it shall solve the problem. I'll improve the code to solve this issue automatically in the future.
BTW, have you changed any configuration of the workflow recently? I'm so curious about what kind of thing can destroy the setting file.

Ok. Thank you.
No change at the configuration file. Had the workflow in my "buggy Alfred workflow you should try to make work".
Running calconfig -> error in workflow 'zmin.calendar'.

hmm, still can't figure out how that happened.
Anyway, thanks a lot for the ticket and please let me know if delete the file can't solve the issue.

Deleting the file can't solve the issue.

Interesting. What command have you typed after deleting?  cal or calconfig? Or both of them failed?

And is a new setting file be generated after the command? is it still empty?

1°) cal then calconfig
2°)Yes a file is generated
3°) Yes it is empty

Can you try cal?

Hi @politicus
Sorry for the inconvenience. Can you paste the exception track again for the first time you run the command after deleting? Is it exactly same as before?
Owen

Hi @politicus
I need more time to figure out the reason as it's so weird. Since the deleting didn't work, can you try to type {} in the empty file instead?
Owen

Same error.
On 13 Jun 2015 at 18:25:17, Owen Min<EMAIL_ADDRESS>wrote:
Can you try cal?
—
Reply to this email directly or view it on GitHub.

Hi @politicus
Sorry, didn't see you already tried cal already in your previous post.
Now I need more information for who creates the empty file because I can't find it by code. Can you paste the log file for:

deleting the settings.json -> type cal
deleting the settings.json -> type calconfig

Is there any other error message after the deleting?
Also, not sure if it's related, do you use default Alfred Workflow data directory or the custom one? For the data directory/setting.json file, do you got the read/write permission?
Owen

cal after deleting  settings.json:
Starting debug for 'Calendar'

[STDERR: alfred.workflow.input.scriptfilter] 08:29:48 workflow.py:1945 DEBUG    Workflow version : 1.2.0
08:29:59 workflow.py:2124 DEBUG    Set last run version : 1.2.0
08:29:59 workflow.py:1969 DEBUG    Workflow finished in 11.726 seconds.
[INFO: alfred.workflow.input.scriptfilter] <?xml version="1.0" encoding="utf-8"?>
<items><item valid="no"><title>                              June  2015                              </title><subtitle /></item><item valid="no"><title>    Su        Mo        Tu        We        Th        Fr        Sa    </title><subtitle /><icon>image/blank.png</icon></item><item valid="yes"><title>                01         02        03         04        05        06</title><subtitle /><arg>2015 6 01</arg><icon>image/biank.png</icon></item><item valid="yes"><title>    07        08         09        10         11        12        13</title><subtitle /><arg>2015 6 07</arg><icon>image/biank.png</icon></item><item valid="yes"><title>    ★        15         16         17         18        19       20</title><subtitle /><arg>2015 6 ★</arg><icon>image/biank.png</icon></item><item valid="yes"><title>    21        22         23        24         25        26        27</title><subtitle /><arg>2015 6 21</arg><icon>image/biank.png</icon></item><item valid="yes"><title>    28        29         30                                             </title><subtitle /><arg>2015 6 28</arg><icon>image/biank.png</icon></item></items>

calconfig after deleting  settings.json:
[STDERR: alfred.workflow.input.scriptfilter] 08:33:46 workflow.py:1945 DEBUG    Workflow version : 1.2.0
08:33:47 workflow.py:2124 DEBUG    Set last run version : 1.2.0
08:33:47 workflow.py:1969 DEBUG    Workflow finished in 0.857 seconds.
[INFO: alfred.workflow.input.scriptfilter] <?xml version="1.0" encoding="utf-8"?>
<items><item autocomplete="width " valid="no"><title>Set width of the calendar</title><subtitle>Current: 10</subtitle></item><item autocomplete="minus " valid="no"><title>Set hotkey: showing previous month</title><subtitle>Current: <</subtitle></item><item autocomplete="plus " valid="no"><title>Set hotkey: showing next month</title><subtitle>Current: ></subtitle></item><item autocomplete="week " valid="no"><title>Set first day of a week</title><subtitle>Current: Sunday</subtitle></item><item autocomplete="config " valid="no"><title>Open config file</title><subtitle /></item></items>

I  think the problem was a file permissions problem. By default, the .json file was a 644. When set to 755 the cal command works fine.
It seems like the .json file is generated as a 644. While the zmin.calendar folder is a 755 by default. I didn't need to change its permissions.

Interesting. Is there any IOError: [Errno 13] Permission denied in the early log file?
I don't think the workflow needs an execute permission of a JSON file. What's more, 022 shall be default umask value for most of  Linux/Mac system. So it doesn't make too much sense to me logically. However, so glad it solves your problem.

No error like these one in the early log file.

I'm having the same issue. I don't have an Alfred 2 folder in Application support at all. Any suggestions on how to get that back?

No Alfred 2 folder in Users/[Your Username]/Library/Application support? Weird. As it is where your Alfred settings are set.
Just go the Alfred forums for an answer to your question.

Okay found it. My mistake. I was going to the library folder found on the root of the hdd.
Deleting the json file did the trick for me. It's working now. Thanks!

Hi @politicus and @shateredsoul ,
The problem is caused by alfred-workflow package. It has been resolved by the latest release. I will update the package soon.

Hi @politicus and @shateredsoul
The new version is able to download now, feel free to leave a message again if anything goes wrong.
Regards,
Owen


Update the ROSA Scheduled workflow to include Health Checks

Fixes #980
Individual workflow works as expected - https://github.com/keycloak/keycloak-benchmark/actions/runs/10907745335/job/30272134584
Adding the health checks to the ROSA Scheduled workflow.

Thanks @kami619


Get server information from Toolbox if possible

Done in https://github.com/Foglio1024/external-interface/commit/8a3eb278eb0d87eedf0b065a2fe0ce4e08d7bd4e and https://github.com/Foglio1024/Tera-custom-cooldowns/commit/9631351408621f75d71f7d1592c7e79e64f22951


Flaky tsup build

It seems #158 has introduces some flakiness to the tsup step of the build, about 1 in 5 runs it fails with this error:
Error parsing: /Users/samwillis/Code/pglite-next/node_modules/.pnpm/pg-protocol@1.6.1_patch_hash=25fzkl5vysjg7s6f5cjgks6z4i/node_modules/pg-protocol/src/messages.ts:4:7
Error: error occured in dts build
    at Worker.<anonymous> (/Users/samwillis/Code/pglite-next/node_modules/.pnpm/tsup@8.2.4_tsx@4.17.0_typescript@5.5.4/node_modules/tsup/dist/index.js:1539:26)
    at Worker.emit (node:events:520:28)
    at MessagePort.<anonymous> (node:internal/worker:262:53)
    at [nodejs.internal.kHybridDispatch] (node:internal/event_target:816:20)
    at MessagePort.<anonymous> (node:internal/per_context/messageport:23:28)
DTS Build error
 ELIFECYCLE  Command failed with exit code 1.

I'm tempted to suggest the solution here would be to vendor pg-protocol into the pglite package. We may want to fork pg-protocol anyway and convert it to use ArrayBuffers, rather than the Node Buffer and a polyfill for the browser.

Fixed by vendoring pg-protocol as an internal package, see https://github.com/electric-sql/pglite/pull/247
No more tsup glitches


Reactivate HoundCI at a later point

Disabled HoundCI for the time being as it is does not seem to parse the Sass according the to defined linter settings in .scss-lint.yml.
Checked with Hound support, and they are not sure what the problem is. Said to be looking into it, but that was ~2 months ago.
Maybe we can try again later??

Going to enable Hound for a bit and see how it works out.  Updated hound.yml also with the latest config settings.

Well,  Hound is still not  working right,  Disabling yet again...


Verb Construction Fails

I have a working recipe like so:
recipe ProductList &showShopList
  copy #shoplist as newlist
  List
    items = newlist
  ItemMultiplexer
    list = newlist
    hostedParticle = ShowProduct
  description `show ${List.items}`

I tried to rewrite this in terms of verbs:
recipe MuxedProductItem &muxProduct
  use #shoplist as items
  List
    list = items
    hostedParticle = ShowProduct

recipe ProductListVerbs &showShopListVerbs
  copy #shoplist as newlist
  List
    items = newlist
  &muxProduct
description `show ${List.items}`

which fails with this output in Strategy Explorer:
recipe ProductListVerbs
  use #shoplist as handle0 // [Product Thing {Text category, Text seller, Text price, Number shipDays, Text name, Text description, URL image, URL url, Text identifier}]  // unresolved handle: unresolved typemissing id
  copy 'manifest:./../../artifacts/Products/../Demo/ClairesWishlist.manifest:store0:f9969af3b19f72fce2f7d1923ff98c9b612d2966' #shoplist as handle1 // [Product Thing {Text category, Text seller, Text price, Number shipDays, Text name, Text description, URL image, URL url, Text identifier}]
  copy 'manifest:./../../artifacts/Products/ShowProducts.recipes::1:af46b67a2f5f65fba23b4c0aa39afca57fe17a3c:ShowProduct' as handle2 // HostedParticleShape
  slot 'rootslotid-root' #root as slot0
  ItemMultiplexer as particle0 // unresolved particle: unfullfilled slot connections
    hostedParticle = handle2
    list <- handle0
    consume item
  List as particle1
    items <- handle1
    consume root as slot0 // unresolved slot-connection: missing consuming slot
      provide action as slot1
      provide annotation as slot2
      provide item as slot3
      provide postamble as slot4
      provide preamble as slot5
  description `show ${List.items}`
        c0425700438aeeafd55537e7d4d5366200cc929a

I also tried simplifying MuxedProductItem:
recipe MuxedProductItem &muxProduct
  ItemMultiplexer
    hostedParticle = ShowProduct

recipe ProductListVerbs &showShopListVerbs
  copy #shoplist as newlist
  List
    items = newlist
  &muxProduct
description `show ${List.items}`

But then Strategizer creates suggestions that map [ArcMetadata] and [Person] collections into ProductListVerbs ... but those types are incompatible with ShowProduct.

When &muxProduct is substituted we're just appending a use handle to the list of recipe handles, without considering whether it should be connected to some existing handle.
I won't have bandwidth for this before my leave, which starts this Friday. If @shans doesn't take a look at it in the meantime I'm happy for it to land on my plate later on. Sorry Scott...
With require/construct we probably should express this as below, indicating that a use handle should be found in the recipe already:
recipe MuxedProductItem &muxProduct
  require
    handle #shoplist as items // not sure about 'handle'
  construct
    List
      list = items
      hostedParticle = ShowProduct

recipe ProductListVerbs &showShopListVerbs
  construct
    copy #shoplist as newlist
    List
      items = newlist
    &muxProduct

@piotrswigon Could we just not append the use handle? If it is the right way to do, it'll be added by the add-use-handle strategy, but also leaves an opportunity for other handle strategies to find a match?

verb substitution doesn't do handle mapping (at least at the moment). It isn't clear to me that it should.
Try something like:
recipe MuxedProductItem &muxProduct
  ItemMultiplexer
    hostedParticle = ShowProduct

recipe ProductListVerbs &showShopListVerbs
  copy #shoplist as newlist
  List
    items = newlist
  &muxProduct
    * = newlist
description `show ${List.items}`

Let's revisit once @AliceLetitia is done with require/construct - it will make handle connecting handles between recipes more explicit.


AppD Monitoring init

Is your feature request related to a problem? Please describe.
We should use AppD as a new monitoring solution.
For this we should configure AppD agent for all Java services in DigiWF-Ops.
Describe the solution you'd like

Configure AppD Init-Container in Java-Base
As AppD needs more Time to Start and more resources, we need to increase

readiness probe, e.g.
max RAM to 1500MB

Dashboard and other Configs in AppD are not Part of this story

Describe alternatives you've considered
Grafana - #493
acceptance criteria

Every Java-Service is available in AppD

Needs to be partly rolled back because the amount of agents exceeds the available AppD licenses.