Support purge from queues and subscriptions that require a session

Fixes #96 where purging failed from a subscription that requires a session. The bug also mentions queues, and this PR also fixes the issue with queues.

:white_check_mark: Build ServiceBusExplorer 4.0.105-PullRequest0159.9.build.317 completed (commit https://github.com/paolosalvatori/ServiceBusExplorer/commit/33f6cad8c6 by @lenardg)

A note concerning curly brackets style, sorry about the formatting - we usually use different formatting in our projects than what ServiceBusExplorer does, and I forgot to check that.
Have you considered adding an .editorconfig to the source? That is our "standard" way to ensure that the same settings are picked up by everyone in the project. Visual Studio 2017 supports editorconfig files out of the box with no need to install a separate extension.
If you are interested I can contribute a base .editorconfig via a PR?

I've raised an issue for .editorconfig
https://github.com/paolosalvatori/ServiceBusExplorer/issues/160
Kind regards,
Sean Feldman
On Wed, Oct 25, 2017 at 11:24 PM, Lenard Gunda<EMAIL_ADDRESS>wrote:

A note concerning curly brackets style, sorry about the formatting - we
usually use different formatting in our projects than what
ServiceBusExplorer does, and I forgot to check that.
Have you considered adding an .editorconfig to the source? That is our
"standard" way to ensure that the same settings are picked up by everyone
in the project. Visual Studio 2017 supports editorconfig files out of the
box with no need to install a separate extension.
If you are interested I can contribute a base .editorconfig via a PR?
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/paolosalvatori/ServiceBusExplorer/pull/159#issuecomment-339554939,
or mute the thread
https://github.com/notifications/unsubscribe-auth/ABP7tjtdTFNDPldXMLLOK2Vvbx2fcDcTks5swBefgaJpZM4QGpUm
.

I added three more commits with corrections to the issues you suggested @SeanFeldman

:white_check_mark: Build ServiceBusExplorer 4.0.105-PullRequest0159.12.build.318 completed (commit https://github.com/paolosalvatori/ServiceBusExplorer/commit/e38446540c by @lenardg)

I added one final commit to address the latest suggestion of the Count() usage in the new code.

:white_check_mark: Build ServiceBusExplorer 4.0.105-PullRequest0159.13.build.319 completed (commit https://github.com/paolosalvatori/ServiceBusExplorer/commit/6f7b2350b9 by @lenardg)


Added Nextflow programming lang extension.

See https://github.com/search?p=1&q=extension%3Anf+process&ref=searchresults&type=Code&utf8=✓

Hi @pditommaso, thanks for opening this Pull Request. It looks like there are only ~180 Nextflow files on GitHub right now and this doesn't meet our contributing guidelines for adding a new language.
Is there a more expansive/inclusive search that could be constructed here to find additional files?

I don't think so.
p
On Fri, Apr 15, 2016 at 5:05 PM, Arfon Smith<EMAIL_ADDRESS>wrote:

Hi @pditommaso https://github.com/pditommaso, thanks for opening this
Pull Request. It looks like there are only ~180 Nextflow files on GitHub
right now and this doesn't meet our contributing guidelines
https://github.com/github/linguist/blob/master/CONTRIBUTING.md#adding-a-language
for adding a new language.
Is there a more expansive/inclusive search that could be constructed here
to find additional files?
—
You are receiving this because you were mentioned.
Reply to this email directly or view it on GitHub
https://github.com/github/linguist/pull/2946#issuecomment-210497045

OK, then I think we should close this for now and revisit periodically to assess usage.

Hello, adoption of nextflow growth considerable in the last year. There are more than 1k hits on Github, see for example:
https://github.com/search?q=extension%3Anf+input&type=Code
https://github.com/search?q=extension%3Anf+output&type=Code
May you revise this PR ?


Activate CodeCov

For the CodeCov badge to work, you need to give it access to your GitHub repository

Idk what it is but there is a 50 Mb file called codecov in your repository, you better ignore it


Whenever im using pop3 always return 'connection setup failed'

Good afternoon,
Please forgive if this quite simple explanation,
As you can see in the title Whenever im using pop3 always return 'connection setup failed'. im trying using imap and other with dummy value in it like
IMAP_HOST=dummi.com
IMAP_PORT=993
IMAP_ENCRYPTION=ssl
IMAP_VALIDATE_CERT=true
IMAP_USERNAME=user
IMAP_PASSWORD=root
IMAP_PROTOCOL=imap
it simply say 'connection failed' instead 'connection setup failed'.
I Hope i can get a little bit explanation about it
Thanks you & Best Regard

Hi @takuminaoya ,
port 993 is usually used by imap. If you are indeed trying to connect through pop3, please use port 995 for an ssl encrypted connection (unless your server setup differs from the default).
Best regards,

Thanks for the reply, im really sorry to bother you.
Im already fix it. the reason is


test-branch/execute-job/quoted-authorization/6b248af8-628b-44ea-97d6-45abde70f754

PR for testing e6bd87bdfa9048a8edc02ac929601d4d9f61e672

/canonical/self-hosted-runners/run-workflows e6bd87bdfa9048a8edc02ac929601d4d9f61e672


Split CI workflows up for the OS badges

Allows the reader to see that the project's CI supports their platform
at a glance.
Badge links format looks to have changed. Tested by pointing temporarily
at my own repo to see the badges in the rendered README.md.

Hm, maybe I was mistaken, and the repository gets unlimited minutes since it's not private!

Sweet.  In that case I'll send a PR to schedule the macOS everyday so its still out of the way but gets a better signal in case something regresses.


Implement window rules

We should research how other wm's (like awesome) implement rules and consider how complicated and how featureful we should be

No longer relevant, since the awesome libs will deal with that


langchain: Allow passsing run_id from config when invoking the chain

Description: When passing run_id to a chain invoke, it has no effects. I want to use the pre-defined run_id when invoking the agent executor.
Issue: none
Dependencies: none
Twitter handle: none

If no one reviews your PR within a few days, please @-mention one of baskaryan, efriis, eyurtsev, hwchase17.

@hinthornw cc: @baskaryan
Thanks for your comments.
Regarding the async function, I added the code to it.
I want to discuss the unit tests.
This pull request doesn't implement the new things.
The single llm.invoke still works well because it is already defined here:

https://github.com/langchain-ai/langchain/blob/b8db73233c0e01e283115b0f5b069aec25bf1384/libs/core/langchain_core/tools.py#L265

I pass the run_id from config to the callback manager in the chain, so I believe that the unit test about the run_id in the callback manager is already covered, and all I need is to pass the test cases.
The test cases are written here:

https://github.com/langchain-ai/langchain/blob/8c71f92cb2f3cca21f2ca02657c8f2906d6a91d7/libs/core/tests/unit_tests/tracers/test_base_tracer.py#L160

Correct me if I am wrong. Thank you.

@hinthornw
Sorry for mentioning you multiple times.
I fixed the lint error. Could you approve the CI workflow?

@hinthornw cc: @baskaryan
Please let me know if you ignore this PR or plan to support setting up the specific run_id for agent invoking in another PR.
I want to set the run_id to set up feedback for Langsmith manually. Without it, the process can not go forward.

Sorry about it!


DRILL-6919: Fix compilation error in TestGracefulShutdown class for mapr profile

In the fix for DRILL-6912 was used a class from hadoop 2.7.4, but for mapr profile hadoop 2.7.1 is used, where this class is absent.
In this PR removed usage of ServerSocketUtil class.
For details please see DRILL-6919.

LGTM, +1


[HOLD for payment 2024-08-01] [$250] Click back button, the category picker opens again.

If you haven’t already, check out our contributing guidelines for onboarding and email<EMAIL_ADDRESS>to request to join our Slack channel!

Version Number: 9.0.6-6
Reproducible in staging?: y
Reproducible in production?: y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Expensify/Expensify Issue URL:
Issue reported by: @dukenv0307
Slack conversation: https://expensify.slack.com/archives/C049HHMV9SM/p1721020681660959
Action Performed:
Prerequisite: There is at least one workspace.

Go to self dm.
Create any track expense if there is no.
Choose "Categorize it" in actionable whisper.
Select any workspace. Then the category page opens.
Select any category option. Then the confirmation page opens.
Click "back" button.

Expected Result:
The participant page opens.
Actual Result:
The category page opens.
Workaround:
unknown
Platforms:

Which of our officially supported platforms is this issue occurring on?

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

Screenshots/Videos
https://github.com/user-attachments/assets/a24a1e91-c95b-478f-8fb2-e8a7e6b27b10
https://github.com/user-attachments/assets/6a465196-18a8-4aec-bd71-8b592cf5b817

View all open jobs on GitHub
Upwork Automation - Do Not Edit

Upwork Job URL: https://www.upwork.com/jobs/~01e2d95899400aa8ef
Upwork Job ID:<PHONE_NUMBER>158052404
Last Price Increase: 2024-07-16
Automatic offers:

dukenv0307 | Reviewer | 103143642
dominictb | Contributor | 103143643

Issue OwnerCurrent Issue Owner: @
Issue OwnerCurrent Issue Owner: @sakluger

@dukenv0307 Could you please explain why we should we back to the participant page.
is that because we have an option to change the category in the submit page so no need to use the back button to return to the category page.
Is there another reason?

I think the bug report is correct. Clicking the back button should go to the previous step, not necessarily the preview screen.
On the summary screen (the screen before clicking back), you can click into the category and change it, but the "To workspace" selection is not clickable, and I can't change it any other way. Because of that, I'd consider the Workspace selection as the previous step, and clicking back should take me to that page.

MacOS: Chrome / Safari

Does it have to be tested on metal, or is a virtual machine acceptable?

The Please re-state the problem that we are trying to solve in this issue. section is wrong though, right?
Also, quick question, won't the proposed solution cause any weird looking animations?

Looks good, thanks!

Summarizing payment on this issue:
Contributor: @dukenv0307 $250, paid via Upwork
Contributor+: @dominictb $250, please request on Newdot

Hey @dukenv0307, could you please complete the BZ checklist?

@dukenv0307 thanks for catching that! I updated the payment summary and it should be correct now.
Thanks also for posting the checklist and regression steps. We're all done here!


Test connection during OCP provider validation.

Test connection during OCP provider validation and support the same conditions/events as for vSphere providers.
Validated
ConnectionTested

Fixed.


[Device IMEI Request] Lenovo K15 Plus

TAC,Model
35379576,Lenovo K15 Plus
I Want Firmware file

How to repair IMEI of Lenovo k 1t plus

This project is for Samsung devices.


Add dependency into app.js when you create new module

Write a function into util.js to add dependency in app.js when you create new module
angular.module(
        'appname',
        [
            'templates-common',
            'ui.router',
            'ngCookies',
            'cr-session',
            //Add dependencies
            'cr-auth',
            'templates-app'
        ]
)

Sorry, I don't know what you want to achieve. But I think you should use something like require js or dojo's require functionilty to lazy load dependencies. In your app config you should only specify common deps and the deps required to run app.init() or something like that.

Hi @prolic! :)
yo ng:module name-module

This command create a new module

src/app/name-module/name-module.js
...
But to load it in my app I can add your name into the list.. I would automate it


Set up initial render deployment

Done! https://gost-grants-tools.onrender.com/#/users
Will get a deployment review from someone on the team in case I missed any essential config


Update document for lidar apollo instance segmentation

Description
Update README.md for lidar apollo instance segmentation.
Review Procedure

Remarks

Pre-Review Checklist for the PR Author
PR Author should check the checkboxes below when creating the PR.

[x] Read pull request guidelines
[x] Code follows coding guidelines
[x] Assign PR to reviewer

Checklist for the PR Reviewer
Reviewers should check the checkboxes below before approval.

[ ] Commits are properly organized and messages are according to the guideline
[ ] Code follows coding guidelines
[ ] (Optional) Unit tests have been written for new behavior
[ ] PR title describes the changes

Post-Review Checklist for the PR Author
PR Author should check the checkboxes below before merging.

[ ] All open points are addressed and tracked via issues or tickets
[ ] Write release notes

CI Checks

Build and test for PR / build-and-test-pr: Required to pass before the merge.
Build and test for PR / clang-tidy-pr: NOT required to pass before the merge. It is up to the reviewer(s). Found false positives? See the guidelines.
Check spelling: NOT required to pass before the merge. It is up to the reviewer(s). See here if you want to add some words to the spell check dictionary.

@wep21 pre-commitで失敗していそうです


Batch Uploader for Revit

Revirew of current MVP and planning next steps.
https://github.com/specklesystems/batch-uploader
Spec in Notion:
https://www.notion.so/speckle/Batch-Uploader-for-Revit-fcc99c374eed45b1ae9e5cbf8040bc89

Closing this ticket as we are moving to Jira to reduce noise. You can access it there.


new errors with deconz 2.07

deconz.0
2020-12-04 18:11:33.753
error
(28100) Error: Request failed with status code 400

deconz.0
2020-12-04 18:11:33.715
error
(28100) TypeError: Cannot read property 'success' of undefined

Hello,
have errors too.

deconz.0
2020-12-05 22:50:14.565
info
(8049) Terminated (NO_ERROR): Without reason

deconz.0
2020-12-05 22:50:14.561
info
(8049) terminating

deconz.0
2020-12-05 22:50:14.432
error
(8049) TypeError: Cannot read property 'id' of undefined at handleWSmessage (/opt/iobroker/node_modules/iobroker.deconz/main.js:2325:54) at runMicrotasks () at processTicksAndRe

deconz.0
2020-12-05 22:50:14.430
error
(8049) unhandled promise rejection: Cannot read property 'id' of undefined

deconz.0
2020-12-05 22:50:14.429
error
Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

deconz.0
2020-12-05 22:50:14.372
info
(8049) cleaned everything up...

deconz.0
2020-12-05 22:50:14.369
error
(8049) TypeError: Cannot read property 'id' of undefined at handleWSmessage (/opt/iobroker/node_modules/iobroker.deconz/main.js:2325:54) at runMicrotasks () at processTicksAndRe

deconz.0
2020-12-05 22:50:14.358
error
(8049) unhandled promise rejection: Cannot read property 'id' of undefined

deconz.0
2020-12-05 22:50:14.357
error
Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch().

deconz.0
2020-12-05 22:49:52.670
info
(8049) deConz Version: 2.7.0; API version: 1.16.0

deconz.0
2020-12-05 22:49:52.480
info
(8049) Please wait while adapter is starting

deconz.0
2020-12-05 22:49:52.429
info
(8049) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.deconz, node: v14.15.1, js-controller: 3.1.6

deconz.0
2020-12-05 22:49:18.938
info
(7452) Terminated (NO_ERROR): Without reason

deconz.0
2020-12-05 22:49:18.935
info
(7452) terminating

deconz.0
2020-12-05 22:49:18.798
info
(7452) cleaned everything up...

deconz.0
2020-12-05 22:49:18.795
error
at WebSocket.ws.onmessage (/opt/iobroker/node_modules/iobroker.deconz/main.js:614:13)

deconz.0
2020-12-05 22:49:18.795
error
at processTicksAndRejections (internal/process/task_queues.js:93:5)

deconz.0
2020-12-05 22:49:18.795
error
at runMicrotasks ()

deconz.0
2020-12-05 22:49:18.795
error
at handleWSmessage (/opt/iobroker/node_modules/iobroker.deconz/main.js:2325:54)

deconz.0
2020-12-05 22:49:18.795
error
(7452) TypeError: Cannot read property 'id' of undefined

deconz.0
2020-12-05 22:49:18.791
error
(7452) unhandled promise rejection: Cannot read property 'id' of undefined

deconz.0
2020-12-05 22:48:58.593
info
(7452) deConz Version: 2.7.0; API version: 1.16.0

deconz.0
2020-12-05 22:48:58.437
info
(7452) Please wait while adapter is starting

deconz.0
2020-12-05 22:48:58.392
info
(7452) starting. Version 2.0.5 in /opt/iobroker/node_modules/iobroker.deconz, node: v14.15.1, js-controller: 3.1.6

Is there a way to fix this issues?

deconz.0	2020-12-04 18:11:33.753	error	(28100) Error: Request failed with status code 400
deconz.0	2020-12-04 18:11:33.715	error	(28100) TypeError: Cannot read property 'success' of undefined

I need more information. Can you provide a log in debug mode?
@jannnfe you can install version 2.0.6 from Github, the issue should be solved with it. But be aware it sends data about your used Zigbee devices to my server. If this is not ok for you do not install it and wait for the next version or go back to 1.3.11.
Actual there is no schedule when the next version will come.

I installed 2.0.6 but im struggling since 4 hours to figure out what's the problem. My devices connected to deCONZ are working fine (Control over Phoscon) but she devices are not updated in ioBroker and i can't really figure out what's the problem. No error log, nothing. They are not getting updated? I repaired some devices that are not reporting states to iobroker but this did not help. Do you have an idea what's wrong?

Seems to be a problem with deconz version >=2.05.88, it does not send updates.
The only solution that is known downgrade to lower version.

Is there a way to validate this on my own system, so i can open a issue on deCONZ?
How to test the updates send from deCONZ?
Btw i installed homebridge and the home bridge hue plugin and all updates are reported in this setup.

You can change the log level of the adapter instance to debug and see whats coming in. Go to instances, activate expert mode and change the log level.
Could be that homebridge is polling data and does not use pushnotifications.

@jannnfe @Jey-Cee The fact that Phoscon still works, means the issue is not with deCONZ.
I'd say some stuff going into iobroker is not working properly. Having logs would be amazing here.

I had similar problems after updating deconz. I installed the client in a docker. So I can keep my usb devices apart I gave the appliances names like ttyUSB_conbee. However, the latest version of Deconz only supports ttyACM0 and ttyACM1. I have mapped the device to ttyACM0 and everything works again.

I had similar problems after updating deconz. I installed the client in a docker. So I can keep my usb devices apart I gave the appliances names like ttyUSB_conbee. However, the latest version of Deconz only supports ttyACM0 and ttyACM1. I have mapped the device to ttyACM0 and everything works again.

@PLCHome Unfortunately, this issue didn't had to do with your fix. Turns out there was some stuff with iobroker on later versions.

@PLCHome Unfortunately, this issue didn't had to do with your fix. Turns out there was some stuff with iobroker on later versions.


Fix getExperimentState query

Query caused error: "table Experiments_Platform_Status.platform_status does not exist in field list".

it wasn't merged yet, was there a problem?

I failed to notice the changes at the bottom of the file and wanted to revert them.


Azure OAUTH failing due to bad request 400

Azure OAUTH failing due to bad request 400
uvicorn[756]: INFO:     <IP_ADDRESS>:0 - "GET /auth/oauth/azure-ad/callback?code=PLACEHOLDER HTTP/1.0" 500 Internal Server Error
uvicorn[756]: ERROR:    Exception in ASGI application
uvicorn[756]: Traceback (most recent call last):
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/uvicorn/protocols/http/h11_impl.py", line 408, in run_asgi
uvicorn[756]:     result = await app(  # type: ignore[func-returns-value]
uvicorn[756]:              ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/uvicorn/middleware/proxy_headers.py", line 84, in call
uvicorn[756]:     return await self.app(scope, receive, send)
uvicorn[756]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/fastapi/applications.py", line 1054, in call
uvicorn[756]:     await super().call(scope, receive, send)
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/starlette/applications.py", line 113, in call
uvicorn[756]:     await self.middleware_stack(scope, receive, send)
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/starlette/middleware/errors.py", line 187, in call
uvicorn[756]:     raise exc
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in call
uvicorn[756]:     await self.app(scope, receive, _send)
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in call
uvicorn[756]:     await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send)
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app
uvicorn[756]:     raise exc
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app
uvicorn[756]:     await app(scope, receive, sender)
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/starlette/routing.py", line 715, in call
uvicorn[756]:     await self.middleware_stack(scope, receive, send)
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/starlette/routing.py", line 735, in app
uvicorn[756]:     await route.handle(scope, receive, send)
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/starlette/routing.py", line 460, in handle
uvicorn[756]:     await self.app(scope, receive, send)
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/fastapi/applications.py", line 1054, in call
uvicorn[756]:     await super().call(scope, receive, send)
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/starlette/applications.py", line 113, in call
uvicorn[756]:     await self.middleware_stack(scope, receive, send)
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/starlette/middleware/errors.py", line 187, in call
uvicorn[756]:     raise exc
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/starlette/middleware/errors.py", line 165, in call
uvicorn[756]:     await self.app(scope, receive, _send)
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/starlette/middleware/cors.py", line 85, in call
uvicorn[756]:     await self.app(scope, receive, send)
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/starlette/middleware/exceptions.py", line 62, in call
uvicorn[756]:     await wrap_app_handling_exceptions(self.app, conn)(scope, receive, send)
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app
uvicorn[756]:     raise exc
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app
uvicorn[756]:     await app(scope, receive, sender)
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/starlette/routing.py", line 715, in call
uvicorn[756]:     await self.middleware_stack(scope, receive, send)
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/starlette/routing.py", line 735, in app
uvicorn[756]:     await route.handle(scope, receive, send)
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/starlette/routing.py", line 288, in handle
uvicorn[756]:     await self.app(scope, receive, send)
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/starlette/routing.py", line 76, in app
uvicorn[756]:     await wrap_app_handling_exceptions(app, request)(scope, receive, send)
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/starlette/_exception_handler.py", line 53, in wrapped_app
uvicorn[756]:     raise exc
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/starlette/_exception_handler.py", line 42, in wrapped_app
uvicorn[756]:     await app(scope, receive, sender)
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/starlette/routing.py", line 73, in app
uvicorn[756]:     response = await f(request)
uvicorn[756]:                ^^^^^^^^^^^^^^^^
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/fastapi/routing.py", line 301, in app
uvicorn[756]:     raw_response = await run_endpoint_function(
uvicorn[756]:                    ^^^^^^^^^^^^^^^^^^^^^^^^^^^^
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/fastapi/routing.py", line 212, in run_endpoint_function
uvicorn[756]:     return await dependant.call(**values)
uvicorn[756]:            ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/chainlit/server.py", line 526, in oauth_callback
uvicorn[756]:     token = await provider.get_token(code, url)
uvicorn[756]:             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/chainlit/oauth_providers.py", line 205, in get_token
uvicorn[756]:     response.raise_for_status()
uvicorn[756]:   File "/home/user/miniconda3/envs/chainlit/lib/python3.11/site-packages/httpx/_models.py", line 763, in raise_for_status
uvicorn[756]:     raise HTTPStatusError(message, request=request, response=self)
uvicorn[756]: httpx.HTTPStatusError: Client error '400 Bad Request' for url 'https://login.microsoftonline.com/TENANT_PLACEHOLDER/oauth2/v2.0/token'
uvicorn[756]: For more information check: https://developer.mozilla.org/en-US/docs/Web/HTTP/Status/400
Chainlit 1.3.2
Python 3.11.10

async def get_token(self, code: str, url: str):
    payload = {
        "client_id": self.client_id,
        "client_secret": self.client_secret,
        "code": code,
        "grant_type": "authorization_code",
        "redirect_uri": url,
    }
    async with httpx.AsyncClient() as client:
        response = await client.post(
            self.token_url,
            data=payload,
        )
        response.raise_for_status()
        json = response.json()

        token = json["access_token"]
        if not token:
            raise HTTPException(
                status_code=400, detail="Failed to get the access token"
            )
        return token

Fails in this function in chainlit\oauth_providers.py; looks like payload is not being built properly, Because the token_url is ok. To me it looks like the "code" variable is wrong. I have been debugging and all other parts seems okay, but it fails on some users due to that error.
I have doubts on what that parameter is:
url = get_user_facing_url(request.url)
token = await provider.get_token(code, url)

in chainlit/server.py line 526

async def get_token(self, code: str, url: str):
    payload = {
        "client_id": self.client_id,
        "client_secret": self.client_secret,
        "code": code,
        "grant_type": "authorization_code",
        "redirect_uri": url,
    }
    async with httpx.AsyncClient() as client:
        response = await client.post(
            self.token_url,
            data=payload,
        )
        response.raise_for_status()
        json = response.json()

        token = json["access_token"]
        if not token:
            raise HTTPException(
                status_code=400, detail="Failed to get the access token"
            )
        return token

Fails in this function in chainlit\oauth_providers.py; looks like payload is not being built properly, Because the token_url is ok. To me it looks like the "code" variable is wrong. I have been debugging and all other parts seems okay, but it fails on some users due to that error.
I have doubts on what that parameter is:
url = get_user_facing_url(request.url)
token = await provider.get_token(code, url)

in chainlit/server.py line 526


bug in genome browser

I was interested in  fig|1313.9910.peg.257, on the far right.  Note the pegs above it, 254,55 and 56.  If you click on them, they are all at least 900bases long, so something is wrong in the way they are being rendered.
Same is true of peg.239 and peg.240

This was due to lack of implemented stats function to determine when to turn off labels. This has been fixed.

@aswarren, has this been deployed? I am still seeing the same problem on alpha. The features close to the vertical grid lines seem to be truncated in display, specially when you zoom out to see ~50kb region.
https://www.alpha.patricbrc.org/view/Feature/PATRIC.1313.9910.1313.9910.con.0004.CDS.50079.51998.fwd#view_tab=genomeBrowser


Add Fiber integration

Fiber integration

@rhcarvalho

@arsmn thanks for the contribution. Sorry we haven't had the bandwidth to review this yet.
On a high level I expect this is pretty much the same as the fasthttp integration with types adapted to match fiber's.
I'll have a look at this and Buffalo (https://github.com/getsentry/sentry-go/pull/196) in the coming weeks, perhaps start moving integrations off into their own modules to avoid an ever increasing list of deps in the main go.mod file.

@rhcarvalho gentle ping

@rhcarvalho gentle ping

@rhcarvalho Can we please merge this ?

Any updates on this? 💐

any news?

@rhcarvalho any update ?

Any update?

any update?
plz

Ping generally

any update?
plz

Ping and Pong, please.

not yet?

not yet2?
@rhcarvalho @kamilogorek @benvinegar

@arsmn thanks for the contribution. Sorry we haven't had the bandwidth to review this yet. On a high level I expect this is pretty much the same as the fasthttp integration with types adapted to match fiber's.
I'll have a look at this and Buffalo (#196) in the coming weeks, perhaps start moving integrations off into their own modules to avoid an ever increasing list of deps in the main go.mod file.

This is open for 1.5 years now. Is this still on the road map?

I think @arsmn should create PR under the https://github.com/gofiber/contrib.

Fiber integration is now available https://github.com/gofiber/contrib/tree/main/fibersentry
Thank you all

Hey @arsmn
Are you still interested in getting this merged?

@robd003 Adding a Fiber integration is definitely on our road map, but I can't provide you with an ETA when this may land.

@cleptric Kind reminder 🙏🏻

Updated to work with the latest main branch in #795

Thanks @arsmn for the contribution and sorry it took so long to get merged.


phf_shared: make uncased feature compatible with no_std

@JohnTitor would you be able to take a look at this?

No no, no problem at all! Thanks for being such a responsive maintainer! :)
On Mon, Sep 6, 2021 at 12:27 PM Yuki Okushi @.***>
wrote:

Merged #232 https://github.com/rust-phf/rust-phf/pull/232 into master.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/rust-phf/rust-phf/pull/232#event-5261973160, or
unsubscribe
https://github.com/notifications/unsubscribe-auth/AAGXSIEXKPVY2OKZUYUF7Y3UATTYHANCNFSM5CODUMKQ
.
Triage notifications on the go with GitHub Mobile for iOS
https://apps.apple.com/app/apple-store/id1477376905?ct=notification-email&mt=8&pt=524675
or Android
https://play.google.com/store/apps/details?id=com.github.android&referrer=utm_campaign%3Dnotification-email%26utm_medium%3Demail%26utm_source%3Dgithub.

thank you!

Hi Petros,
I just found this line, and was imagining that you'd like a ping on this.
@petrosagg:  // FIXME(petrosagg): remove this once rust-phf/rust-phf#232 is released
From https://github.com/chronotope/chrono-tz/blob/0dc2741ca8966818eea641004366d2aad2a7c686/chrono-tz-build/src/lib.rs#L113
Best wishes and thanks for chrono-tz!


Ensure extracted files are written to the path, not the filename

Looks like the extract function was always writing to the current working directory and using the file's name, not the requested output path.

Hi @GrumpyMetalGuy thanks for the PR. There are 2 issues I think should be addressed.

If the destination directory does not exist, it won't create it and panics. From a usability perspective, I think it should.
If a Windows path is supplied with backslashes on a Unix system, the filename will include the path. ex. 'data\local\test.txt'. And vise versa with Unix path on Windows. It's probably best to have it create the directory structure regardless which type of supplied path and OS.

Yep, sounds good. I'll do an update a bit later tonight and get that into the PR...

Actually, thinking about this - PathBuf, etc, allow users to construct paths suitable for the OS in question, so we don't need to worry about the clash between Windows and other OSes in that case, they should be fine.
The other option is something like a command line tool, where someone supplies a string of some sort, which would then be used directly as a path. In this case, if someone passes \ as a separator on a *nix OS, they (presumably) know what they're doing (and if they don't, then they just get some odd-named files, they'll facepalm, and try again).
I'd be inclined to create the directory using Path's parent() as the directory name, and let the buyer beware... thoughts?

Yeah, I'm leaning towards the second option as well. I'm okay with creating directory using the Path's parent() as the directory name. And assuming the user supplied a valid path for their OS platform.


Reading data from s3

Hi,
Is there a way to provide input from s3 for create "API"
Thanks!

I may not prefer to include an AWS S3 client library here, but maybe we can read from an InputStream for user to pipe the content from S3?

Thanks!


How can I change the month names? or make it Numerical.

Make sure to add all the information needed to understand the bug so that someone can help. If the info is missing we'll add the 'Needs more information' label and close the issue until there is enough information.

[ ] Provide a minimal code snippet, please make sure it is well formatted.
[ ] Provide a stackblitz demo / stackblitz example that reproduces the bug.
[ ] Provide screenshots where appropriate
[ ] What's the version of Angular you're using?
[ ] Does this occur on specific browser?

@azad47808  you can set Month Button Format (monthBtnFormat) to MM or M

@azad47808  You can set Month Format (monthFormat) to MM YYYY or M YY
datePickerConfig = {
monthFormat: 'MM YYYY'
}


Ability to have different colours for sub folders with coloured folder.

Currently if i set a path to a folder (e.g folder/includes) and tell it to be cyan for example. All files/folders within that path turn cyan.
Can we have it so that if i add another path (e.g folder/includes/somefolder) that i can make 'somefolder' a different colour?
So all files/folders in the overall folder are cyan, but the specific one outlined above a totally different colour?

You could try coloring folder/include/, with an additional '/' at the end.
It works for me.


Is this written with the Phaser framework?

Phaser seems to think your source was written with their framework https://phaser.io/news/2016/04/solitaire however it looks like this is written in Scala.

It is indeed based on Phaser, a tremendous engine! However, the client code is written in Scala, and compiled to JavaScript by Scala.js. It's a great community built around a strong language.
https://www.scala-js.org


chore: rename bullseye docker image to cloud-sql-proxy

This has been omitted during the gce-proxy -> cloud-sql-proxy version rename for v2. Adjusted the build config so that future releases are released under the documented docker image name already used for the other tags.
Already published versions would need to be adjusted manually by someone with the respective permissions if desired.

@ngergs Great catch! Thanks for this PR updating the bullseye build to the proper naming convention, much appreciated!
I will go back and look at re-tagging previous builds to the proper tags 😄


Guest isn't online after 7 s

Is what I get when I run the Android Studio emulator (Nexus 5X with API 28). Below in the console I have Waiting for target device to come online.
Other than that I have build completed successfully with one warning, which I think is: 12:23	Emulator: qemu-system-x86_64: warning: TSC frequency mismatch between VM (2195012 kHz) and host (2195013 kHz), and TSC scaling unavailable.

Hm got a physical device working Xperia LT25i - 4.3. Put it in dev mode. Build successful. Error: error: device unauthorized. Please check the confirmation dialog on your device.
Don't know what that means, could it be that it's not authorized somewhere on AWS?

Just tried to run it again: npm run android. Now I get a red screen on the mobile which disapered when the screen lock kicked in. But I get some messages in the terminal window:
BUILD SUCCESSFUL in 13s
27 actionable tasks: 1 executed, 26 up-to-date
Running adb -s BX903JNBC2 reverse tcp:8081 tcp:8081
error: closed
error: closed
Could not run adb reverse: Command failed: adb -s BX903JNBC2 reverse tcp:8081 tcp:8081
Starting the app on BX903JNBC2 (adb -s BX903JNBC2 shell am start -n com.awsappsyncevents/com.awsappsyncevents.MainActivity)...
Starting: Intent { cmp=com.awsappsyncevents/.MainActivity }
(running it on Ubuntu Mate 16.04)

Do my phone need to have a Internet connection?

Checked adb devices:
adb devices
adb server is out of date.  killing...
cannot bind 'tcp:5037'
ADB server didn't ACK

failed to start daemon *
error:

Checked adb devices:
adb devices
adb server is out of date.  killing...
cannot bind 'tcp:5037'
ADB server didn't ACK

failed to start daemon *
error:

Found this thread: https://github.com/facebook/react-native/issues/15388
Then I started the packager server: npm start. And solved! There is a couple of hidden steps to get it working apparently.


ARROW-13700: [Docs][C++] Clarify DayOfWeekOptions args

This is to resolve ARROW-13700.

@ianmcook

@lidavidm - could I ask you for a quick doc check?


Add support for configurable api endpoint

To enable using eu endpoint for API this needs to be configurable. I've added so the full URL is possible to configure.
To test this add this to initializers/sparkpost_rails.rb
c.api_endpoint = "https://api.eu.sparkpost.com/api/"

for a Sparkpost account in EU.
This is similar to https://github.com/the-refinery/sparkpost_rails/pull/58/files but have some pros

It does not include the version in the configuration option so in case of bump in API version it's not needed to reconfigure
Tests are actually testing using the configuration variable
If additional API paths were to be added it can be reused.

This would be a very welcome change!


fix: add version to bu.sublime-syntax

version needs to be the same as in YAML.sublime-syntax, cf this StackOverflow question and answer.
I have tested this in Sublime Text 4143.

Thanks for the fix! Now I just gotta remember how to update it on Package Control 😅


Add SearXNG

I added SearXNG. It works, but you should review it in ase I made decisions that aren't wise.

LGTM


Makes title and related works into text areas.

closes #1032
Why was this change made?
Better data entry.
How was this change tested?
Local
Which documentation and/or configurations were updated?
NA
Note that default citation was already a text area.


Custom webhook feedback URL

As requested by a few people - a way to deliver feedback to an endpoint owned by a plugin dev in a variety of formats, so that they don't have to look at #feedback to get their plugin's feedback specifically and so that they can send feedback to their own bug reporting system.
Requirements:

Be able to disable feedback entirely, deliver feedback to #feedback, deliver feedback to the specified custom endpoint, or deliver feedback to both. (i.e. all four variations)
Must not leak the endpoint URL to anyone. This will likely be done by encrypting it, as we do with the secrets: https://goatcorp.github.io/plogon-secrets/
Must be able to handle standard payload formats. Probably just Discord for now?

Given that, the solution will probably:

Store the custom endpoint in the manifest, as well as instructions on how to deliver it. I'd say start with just a basic JSON payload ({author: string, message: string}) and a Discord payload. We can add more if people suggest them.
Bugbait decrypts the payload with its private key, and then delivers the payload to the endpoint, in addition to Discord if specified

Another option that would be nice to have: getting pinged by your Discord username. We could let people specify their username in the manifest, and then have an option to be pinged.


[BUG] Tried to open roblox but an error came up and it said something closed it

Acknowledgement of preliminary instructions

[X] I have read the preliminary instructions, and I am certain that my problem has not already been addressed.

What problem did you encounter?
Bloxstrap_20231026T022922Z.log
it jus says something forebly closed it

Does this happen every time you try to use it?

@kazidus I've seen similar issues on Roblox (not Bloxstrap) and it was because of a Firewall. Check that your computer allows it past the firewall (see https://www.digitalcitizen.life/how-change-windows-firewalls-list-allowed-blocked-apps/ for help on how to do it), or check your router for Parental Controls that disallow it.

@kazidus I've seen similar issues on Roblox (not Bloxstrap) and it was because of a Firewall. Check that your computer allows it past the firewall (see https://www.digitalcitizen.life/how-change-windows-firewalls-list-allowed-blocked-apps/ for help on how to do it), or check your router for Parental Controls that disallow it.

i dont see the bloxstrap app on my firewall

i dont see the bloxstrap app on my firewall

...Are you having the same issue?

Issue has been awaiting clarification for over a month, closing as stale. If you have anything further to add, just respond and I'll reopen.


Specify the semantics of mini-protocol programs

We shall specify the semantics of mini-protocol programs as a function from mini-protocol programs to Þ-calculus processes. This approach will allow us to leverage the Þ-calculus for stating and proving properties about mini-protocol behavior.

This issue has been superseded by #95 and #96.


Prevent spam of emails if server is down.

Fix for issue #1. Added threshold variable (in seconds) to config file. When delta > threshold, emails are not sent.

run['lastrun'] might be a poor choice. That's the last time we checked the repo and should be past the threshold in almost every case I've deployed this in. Currently the crontab I use is set for every hour.


Request: Using colors or html-classes for decorating

Thanks for putting in the effort into this project, much appreciated.
In my use case, I wanted to try to go for even more readability by changing the icon-colors. To my surprise "ICON" works (but can't find it in the TOML docs) but I can't add other tags - they get printed out to the workspace tray even when I try to escape everything.
Couldn't find anything to work with when inspecting with GDK_DEBUG either.

Not sure what you're trying to achieve, but an Icon is just a piece of text/string. It depends on the bar you use how it gets rendered. Found out that waybar supports A also  blocks.

Sorry if I was a bit unclear.
Having a few icons next to each other quickly gets hard to discern. Instead of increasing font-size (not sure if I can increase inject icon margins) I wanted to be able to recolor the icons to distinguish them more from each other.  New to Sway!
I'm attaching an example of how I did it manually Waybar with fixed icons and conf(no working sworkstyle):
Visual result

Waybar config
        "format": "{value} {icon}",
        "format-icons": {
            "1": "  ",
            "2": "  ",
            "3": " "

Yeah, so I get what you want but Sworkstyle can only simply rename workspaces based on Applications being run in the workspace. It depends on the bar how it interprets the workspace title. Not really a Sworkstyle issue. There is no way for me to add colored support since I don't handle the rendering of workspace titles... :\


Updated download function

Added progress bar, notification and simple failure handling for the download functionality.
Tickets #12, #15

Its moved and resolved in this commit


Fixed unwanted trailing tab in chrome 53

Closes https://github.com/minkphp/MinkSelenium2Driver/issues/243

Also don't send PR from master branch, because you'll be unable to send 2 PR in parallel to same project.

One test still fails. However I'm unsure if this is related to made changes or just to Firefox version updated on Travis CI, that doesn't play nice with Selenium Driver version that is used.

For me latest stable Selenium Driver (2.53.0) + latest stable Firefox (48.0.1) doesn't work at all. When running test suite on Chrome I'm getting same " error.

I've created #245 issue for that failing test because it's not related.

Otherwise change looks good if it solves problem you're having in both Chrome and Firefox.

Faced with the same problem on my current project. This solution works for me in Chrome 53.0.2785.116 (64-bit).

The build failure is due different problem described in #245.
Otherwise tests are passing and I think this one is ready to be merged.

Thanks @adorin , merging.


RuboCop config being ignored?

My RuboCop is configured to ignore schema changes:
require: 'rubocop-rails'
inherit_from: .rubocop_todo.yml

AllCops:
  TargetRubyVersion: 2.6
  Exclude:
    - 'db/schema.rb' # auto-generated

When I run RuboCop directly, there are no issues.
I have Lefthook configured with:
run: bundle exec rubocop {staged_files} --parallel
When it's triggered through Lefthook, it seems to ignore the config.
I tried changing it to explicitly specify the config file, but it made no difference:
run: bundle exec rubocop --config .rubocop.yml {staged_files} --parallel

This is strange :thinking:  I will check it.

What about to use --force-exclusion option for RuboCop?
RuboCop does not ignore Exclude config when the command given file except to use --force-exclusion.

@AquiTCD thanks, that works.
I think others will also run into this, so I'll open a PR to document it.


Proposal: Replace exitCode, stdout and stderr with new pattern

Context
We have an outstanding bug when using exitCode, stdout and stderr:

https://github.com/dagger/dagger/issues/3192

These fields trigger the configured command to execute. Problem is that if the command fails, the common code that they all share returns an error. That isn’t the proper behavior. A proper GraphQL error would be for example that no exec was actually configured, or the network connection was suddenly killed.
This happened initially because we had a technical limitation, but it seems we can fix it now with the shim:

[…] this should be easier to fix now that we have the plumbing for collecting the stdout/stderr/exit status that we added for better error messages.

- Originally posted by @vito in https://github.com/dagger/dagger/issues/3192#issuecomment-1459212866
Problem
There’s a lot of confusion around using exitCode as a way to trigger command execution in a lazy pipeline:

https://github.com/dagger/dagger/issues/4668#issuecomment-1490289888

Some users are doing things like if exitCode != 0, which doesn’t work now but would if the bug was fixed. In the meantime, they’re probably not aware that branch of their pipeline code never gets executed.
On another hand, users that are aware of the issue, find themselves in the need of parsing the error message to extract these fields (e.g., using a regex pattern), which is the only workaround they can use, but one I’d love to make obsolete.
Adding to that, you need to be aware that a GraphQL error here could be something that’s not related to the command that was executed (e.g., command not configured or network error):
func exec(ctr *dagger.Container, ctx context.Context) (bool, error) {
    exitCode, err := ctr.ExitCode(ctx)
    if err != nil {
        msg := err.Error()
        // This could be a network error,
        // or command not configured,
        // for example.
        if strings.Contains(msg, "exit code:") {
            return false, nil
        }
        return false, err
    }
    // FIXME: will never be != 0 so need to
    // extract the actual code from error message
    return exitCode == 0, nil
}

And in case of success, you have to make multiple network requests to get the other fields:
exitCode, err := ctr.ExitCode(ctx)
if err != nil {
    return err
}
stdout, err = ctr.Stdout(ctx)
if err != nil {
    return err
}
stderr, err = ctr.Stderr(ctx)
if err != nil {
    return err
}

There’s also the very common pattern of using .ExitCode(ctx) to just force command execution in a lazy pipeline, not caring about the actual exit code value and maybe relying on the side effect of a bug (GraphQL error) to abort the pipeline (exceptions in Python and NodeJS).
This pattern has become so common that users reach for .ExitCode(ctx) even when they don’t actually want the configured command to execute, they just want to synchronize lazyness (e.g., see if a Dockerfile build succeeds).
More on this confusion:

https://github.com/dagger/dagger/issues/4668

Because of all of this, fixing these fields has been flagged as a priority, but it’s currently stuck because so many users rely on it now.
Solution
I think the best way to move past this problem is to:

Create new API call to get the exit code, stdout and stderr as values, even on command failure;
Deprecate current exitCode, stdout and stderr (i.e., print warning when these are used);
Encourage users to migrate to new pattern to run commands (e.g., update docs);

This deprecation path into a new pattern solves the backwards compatibility problem, while also seizing the opportunity of improving it.
Option 1: Returning a new simple object
This is my preferred solution. It’s explained in more detail in:

https://github.com/dagger/dagger/issues/4920

In summary, I think it would be great to get all of these fields in a single API request at once:
query {
    withExec(...) {
        execResult {
            exitCode
            stdout
            stderr
            error
        }
    }
}

And without relying on a GraphQL error:
res, err := alpine.WithExec(...).ExecResult(ctx)
if err != nil {
    // example: command not configured, or network error
    return err
}
// no need for `res.exitCode != 0`
if res.Error {
    // can do anything: abort pipeline, just log, switch behavior...
    // depends on what user wants, as it's not always the same
    fmt.Printf("Failed with exit code %d\n", res.ExitCode)
}
// all fields are always received as values, even on non-zero exit code
fmt.Println(res.stdout)
fmt.Fprint(os.Stderr, res.stderr)

That’s the best DX in my opinion.
Option 2: Returning a new object, but without codegen
Without codegen returning the multiple fields in the same request, you can still use the same API change to encapsulate these fields and allow migrating to a new pattern while deprecating the old.
You’d still need to make multiple network requests to get the multiple fields which isn’t fun though.
Option 3: SDK helper
If we can’t make an API change that every SDK benefits from, but there’s still a pattern where everyone is reinventing the same wheel, we should at least provide helpers in the SDKs that can be imported an reused by everyone.
The downside is that it has to be re-implemented in every SDK, but at least it would allow hiding the error parsing and getting all values concurrently in case of success, from users.
(pseudo) Python POC
@dataclass
class ExecResult:
    stdout: str
    stderr: str
    exit_code: int
    error: str | None = None

async def exec(ctr: dagger.Container) -> ExecResult:
    try:
        return ExecResult(
            await ctr.stdout(),
            await ctr.stderr(),
            await ctr.exit_code(),
        )
    except dagger.QueryError as e:
        msg = str(e)
        if "exit code:" not in msg:
            # This could be a network error,
            # or command not configured,
            # for example.
            raise
        # basically extract the various components from the error message
        # this is the format:
        #     process “<command>” did not complete successfully: exit code: <exit code>">
        #     Stdout:
        #     <stdout>
        #     Stderr:
        #     <stderr>
        return ExecResult(
            stdout_from_error(msg),
            stderr_from_error(msg),
            exit_code_from_error(msg),
            error_message(msg),
        )

async def lint():
    ctr = dagger.container(...)
    result = await exec(ctr)

    # you can choose what to do with the error
    # (e.g., abort, log, ignore...)
    if result.error:
        raise MyCustomError(result.error)

Alternative proposals
@vito proposed the following:

https://github.com/dagger/dagger/pull/4723

It depends on keeping the same GraphQL error, while ignoring the return value for exit code. However, as I said in Context, using the GraphQL error is not an appropriate use for this. It would be better to return a new Error type as a value instead, but then I think the above solution is a better implementation of that.

@samalba @gerhard can you confirm who needs to approve this proposal, so we can move forward with implementation?

Thanks for putting this together! Glad to see progress around this thorny area.
Some scattered feedback from a couple different perspectives, but all just my $.02c:

I don't think users should feel compelled to write code like if res.failed { print("failed:", res.code) }, or even write code to print stdout/stderr in the happy path. It seems like a lot of overhead for something you're doing with Dagger 99% of the time. I think this pattern is mostly a result of having poor visibility when running Dagger, but we have dagger run now which should help a lot.

As an end user scripting pipelines in Dagger, in most cases I don't really care about the different types of errors that might happen. I just want to write optimistic code with minimal error handling noise, similar to Bash with set -e. I want to be able to identify the root cause for any errors that might come out, but I don't want to have to code against those all the time. Personally, I don't think I would ever handle a GraphQL, network error, or "command not found" error any differently from a command failing, but again I'm talking about the typical case here, not saying it never happens.

On the other hand, as someone hypothetically writing an orchestration layer on top of Dagger (say a CI control plane, or Bass's Dagger runtime), I can see value in programmatically identifying the root cause for errors. For example, Concourse made a distinction between "errored" and "failed" CI build states, which let the user know if there was an internal infra failure (=> rerun build) or if their build legitimately failed (=> investigate). It's worth noting that "command not found" was classified as a failure, not an error, since that's not likely to recover on its own.

There will be cases where the API caller wants to fetch exitCode but specifically avoid fetching stdout and stderr. For example, a CI control plane that's already equipped to collect stdout/stderr via the progress stream won't need to collect them again, and in fact would probably not want to fetch them just in case someone printed 1GB of logs. (It can easily happen with a runaway loop and a long enough timeout.)

If we're adding the ability to distinguish error cases for Container.WithExec, wouldn't we need to make the same consideration for other APIs? For example, Container.DockerBuild might fail when running the Dockerfile, but it also might fail to even locate the Dockerfile, which is analogous to "command failed" vs "command not found."

Thanks for the feedback @vito 🙂
What to do with field error?

I don't think users should feel compelled to write code like if res.failed { print("failed:", res.code) }, or even write code to print stdout/stderr in the happy path. It seems like a lot of overhead for something you're doing with Dagger 99% of the time. I think this pattern is mostly a result of having poor visibility when running Dagger, but we have dagger run now which should help a lot.
As an end user scripting pipelines in Dagger, in most cases I don't really care about the different types of errors that might happen.

You shouldn’t feel compelled to do anything with stdout/stderr/exitCode. At a minimum, just an if res.Error allows a distinction between error types. I still think it’s useful to make that distinction:

https://github.com/dagger/dagger/issues/4700

res, err := ctr.WithExec(...).ExecResult(ctx)
if err != nil {
    // example: command not configured, or network error
    return err
}
if res.Error {
    // can do anything: abort pipeline, just log, switch behavior...
    // hard to generalize, it depends on needs
}

// continue with pipeline

If you’re executing a go test, having a failed network connection would make you believe the tests failed, which isn’t the case.
I’ve seen multiple different needs for what to do when a command fails (abort, log, switch behavior…). Even on the same project. You’re focusing on just printing the error but that’s not on my mind when I think of it.
The “happy path”: Run() convenience?

I just want to write optimistic code with minimal error handling noise, similar to Bash with set -e. I want to be able to identify the root cause for any errors that might come out, but I don't want to have to code against those all the time.

I get what you’re saying, I also want that as much as possible. But it feels like we need a convenience on top, as I still think we need to replace exitCode.
Initially I also wanted to write another proposal to add a convenience like .Run(ctx) for that happy path and when you don’t care about any result, just success or failure. The reason I didn’t submit it is that now we’d have two ways to execute a container command, while this attempts to simplify things.
Maybe the usefulness of this added convenience trumps the disadvantage of having multiple ways to do the same thing. If so, this is how I was going to suggest it.
Still attached to the idea of not depending on the GraphQL error for command as a normal condition, seemed better to return a Error type in data on command failure, while keeping errors for “failing to resolve a field”.
interface Error {
    message: String!
}
type ExecError implements Error {
    exitCode: Int!
    stdout: String!
    stderr: String!
}
type Container {
    run(): ExecError
}

So this means returning null on success, and ExecError on failure. Notice that I’m avoiding using a Union for success and error conditions because of Go.
In Python I just want two different exception types (e.g., QueryError vs ExecError), so the happy path is still await ctr.run(), nothing to return, but if I choose to capture that exception, I can capture either one, or both if I want to.
In codegen, you can check if a value implements the Error interface and raise an exception, instead of returning a value:
# don't care, just abort!
await ctr.run()

# abort only on server errors,
# but catch command failure
try:
    await ctr.run()
except dagger.ExecError as e:
    log.error(e)
    return False
return True

NodeJS is similar and the same can be done in Go:
// don't care, just abort!
err := ctr.Run(ctx)
if err != nil {
    panic(err)
}

// abort only on server errors,
// but catch command failure
err := ctr.Run(ctx)
if err != nil {
    if execErr, ok := err.(dagger.ExecError); ok {
        log.Error(execErr)
        return false
    }
    panic(err)
}
return true

Although that second case looks simpler with ExecResult in Go:
res, err := ctr.ExecResult(ctx)
if err != nil {
    panic(err)
}
if res.Error {
    log.Error(res.Error)
    return false
}
return true

Different error types don’t matter?

Personally, I don't think I would ever handle a GraphQL, network error, or "command not found" error any differently from a command failing, but again I'm talking about the typical case here, not saying it never happens.

We lack hard data on what’s the most common use cases, so we can only rely on our impressions. 😇
Don’t agree with this part though. Of course it depends on personal needs, but I’ve seen enough cases where users simply aren’t aware of this difference and always treat the error as if the command failed. Whenever I’ve pointed out that you need to look in the error message for “exit code:” (especially on bigger pipelines), no one has told me they don’t care that, but it always feels like a big, non-intuitive caveat to teach/learn. A stop gap, really.
Based on what I’ve seen, I don’t think I can generalize not caring about this difference as the most typical case (after considering awareness that there’s a difference in the first place). I’d rather have the distinction be clearer and provide a convenience for that “happy path” or when it doesn’t matter.
Errored vs failed

On the other hand, as someone hypothetically writing an orchestration layer on top of Dagger (say a CI control plane, or Bass's Dagger runtime), I can see value in programmatically identifying the root cause for errors. For example, Concourse made a distinction between "errored" and "failed" CI build states, which let the user know if there was an internal infra failure (=> rerun build) or if their build legitimately failed (=> investigate). It's worth noting that "command not found" was classified as a failure, not an error, since that's not likely to recover on its own.

Just to be clear, there’s a difference between a “no command has been executed” error and a “command not found” error that we actually never return. What gets returned instead is process "wat" did not complete successfully: exit code: 1 (with empty stdout and stderr).
The latter one is handled the same as any existing command’s non-zero exit. Perhaps it should be a GraphQL error there. How can a command that doesn’t exist return any exit code? Unless you run it in a shell sh -c "wat". Even then, it’s a 127 exit code, not 1.
But yes, some users are making a report for the result status of multiple sub-pipelines (even concurrent), and they need to differentiate between a “pipeline authoring” error and a “code under test” error, for example.
When stdout is unwanted?

There will be cases where the API caller wants to fetch exitCode but specifically avoid fetching stdout and stderr. For example, a CI control plane that's already equipped to collect stdout/stderr via the progress stream won't need to collect them again, and in fact would probably not want to fetch them just in case someone printed 1GB of logs. (It can easily happen with a runaway loop and a long enough timeout.)

I actually didn’t think about that. Fetching the other 2 values when you only care about 1 seemed harmless enough, but I didn’t consider a huge stdout/stderr.
However, in case of an error, we’re already sending all 3! In the case of success, I suggest maybe using the .Run() convenience from above.
When you only need exit code, in the success path, it’s always zero. On error it can be returned on  ExecError. The only problem is if you only need stdout and really don’t want stderr, or vice versa.
To be clear, I’m assuming option 1 for ExecResult here. Not an issue otherwise.
Different error types in the API

If we're adding the ability to distinguish error cases for Container.WithExec, wouldn't we need to make the same consideration for other APIs? For example, Container.Build might fail when running the Dockerfile, but it also might fail to even locate the Dockerfile, which is analogous to "command failed" vs "command not found."

Yes, you’re totally right. That’s part of why I reported this:

https://github.com/dagger/dagger/issues/4700

That was my priority a little over a month ago, but put in on pause to deal with other things. It’s high on my list to return to next.

Thanks for the breakdown! :smile:
I don't want to dominate the airwaves with just my perspective, but my main concern is that this addresses the problem of "the user doesn't know what failed" by forcing them to handle those different cases in their code. That extra 3 lines of error checking seems like it will become pretty tiring because it applies to Dagger's "bread and butter" (running commands). My concern with if res.error { print } wasn't necessarily about printing, it was about having to do anything at all - including just propagating the "inner" error. I'd almost immediately write a helper to hide it away.
If the goal is just to elucidate failure modes, I think there are other approaches we could consider:

Returning structured errors from the API + SDK (Go error types, Python exception classes etc)

As you pointed out, this is #4700

Improving error messages in general (inspiration)

This is probably challenging with all our SDKs, but seems worth considering

Better UIs for seeing the whole system and pinpointing where failures happen (dagger run)

I think dagger run addresses a lot of these issues, and it only just came out, so I'm hesitant to put a lot of weight on patterns and failure modes that emerged from a world where it didn't exist.
Also: still totally in support of being able to distinguish errors in code somehow, as I mentioned it would be useful for Dagger based CI systems/etc. Really just worried about getting grumpy with all the error checking I already have to write in Go. :sweat_smile:

[...] Really just worried about getting grumpy with all the error checking I already have to write in Go. 😅

I think I've addressed this, but I'll re-organize things to make your concerns clearer.

Also pt. 2: if we have this API but also ship a helper that lets you write less code, I have no qualms, though I suspect #4700 might still be a more fruitful investment for the rest of the API.

I always take #4700 into consideration because that's something that should be done regardless. I just haven't had time yet to formalize the design change.

I’ve thought about this some more and I’m withdrawing this proposal.
Considering the following issues:

https://github.com/dagger/dagger/issues/4700
https://github.com/dagger/dagger/issues/5124
https://github.com/dagger/dagger/issues/3496

We’re left with just stdout and stderr.
All that remains then is to be able to get the full output (not truncated) in case of a failure:

https://github.com/dagger/dagger/issues/4979

I’ve been thinking on a few solutions for that as well, so I’ll discuss it in that issue.


Add build-script -a/-A to control assertions

This PR adds two short equivalents of current long flags: -a is short for --assertions, while -A is short for --no-assertions. The assertion setting is critical for testing performance, so it really ought to be easy to specify.
With this change, common configurations like "release-debug, no assertions" can be specified with build-script -rA.

@swift-ci please smoke test


support ansible-core 2.12; scan for plugins

Add support for ansible-core 2.12.  This is currently pre-release so
have to use pip_pre to install it.
Add a check for non-core plugins - ansible-plugin-scan - so we can
catch in CI when a role uses a non-core plugin.

We'll have to "move" some tests to use python 3.8 or later in order to use ansible 2.12 - for example - https://github.com/linux-system-roles/storage/pull/234


Update README.md to point url to v1.1

Issue
Sprites that are in the list weren't available on the v1.0.
E.g. pwa.
Fix
Pointing to v1.1 in the documentation now.

Thank you!


should we be on pythonxy?

https://code.google.com/p/pythonxy/
(cvxopt is)
Would greatly simplify windows installation for some users

That would be amazing. Will test on my Win laptop.

I think we should use this instead of Anaconda on Windows.

Could also use pythonxy to install cvxopt on Windows, even if gpkit is not on it.

This remains open to determine whether we should get in touch with pythonxy and ask them to include us in their package.

Closed since we no longer use pythonxy on windows.


Ref: organising walkSchema

A minor thing

coverage: 100.0%. remained the same
when pulling 9c73a3393d7c90c1f2ae3f09e27c372e74d40151 on org-schema-walker
into 819f224c5c226d0b680c6c0213f82dab8a2f4d91 on master.


Option to select hour, minute and am/pm in select box?

Is there any way to select hour, minute and am/pm in three different select box? For example say, hour from 1 to 12, minute from 1 to 59 and am/pm in another select box.
Thanks.

Hi I am trying to do exactly the same thing.  I use controlType: input and timeFormat: 'hh:mm TT'
I have my custom control. It works but when I switch between AM and PM, it is giving me 24h format instead of 12h format.
Any snippet for that or example?

Any idea?

I would also like to see this feature implemented.

This already exists in the library. Just use controlType: 'select'. Have a
look at the docs for more info. You can also define custom control types.
On May 17, 2016 9:42 PM, "Grant Kiely"<EMAIL_ADDRESS>wrote:

I would also like to see this feature implemented.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/trentrichardson/jQuery-Timepicker-Addon/issues/542#issuecomment-219903162

Hi Trent, does setting it to controlType: 'select' generate a separate am/pm select box?
If I get time I might do a custom control type but it would be awesome if this was an option.

It doesnt, it will be included within the hour select box
On May 17, 2016 9:58 PM, "Grant Kiely"<EMAIL_ADDRESS>wrote:

Hi Trent, does setting it to controlType: 'select' generate a separate
am/pm select box?
If I get time I might do a custom control type but it would be awesome if
this was an option.
—
You are receiving this because you commented.
Reply to this email directly or view it on GitHub
https://github.com/trentrichardson/jQuery-Timepicker-Addon/issues/542#issuecomment-219905154


Update paypal-rest-sdk to version 1.8.1

Coverage remained the same at 67.667% when pulling 7a2eaf671ff0707273f1656f3dd726547b8b91a9 on packages/paypal-rest-sdk-update into de10da9428b4844082172fbbd639fad56a77d0d4 on master.


Valid zips

Hello,
Sorry for bombarding you with PRs. But I found issue with zipping XCFrameworks with Catalyst. Turns out zip by default expands symlink. MacOSX and Catalyst frameworks use symlinks inside, so the have doubled everything inside and the worst part - Xcode can't sign them.
So I added --symlinks flag to zip. I tested everything and now they are really good Catalyst frameworks.
Will make PR for network_ios too

Hi,
No problems with the PR. They solved a major issue with the building system. There is a strong chance that Apple will introduce something similar at WWDC 2021.
I can't test on Catalyst, so I'll trust you with this PR.

Thank you, can you also retag? I wanna make PR for network_ios today

The new version is now retagged.


iOS/Android support?

I'm curious if BLUI/Chromium can be ran on ARM/mobile.

unfortunately it is not possible for this software to run on Android of iOS at the moment.
CEF3 (the chromium framework that the plugin relies on) has not been ported to theses systems, and doing so would require effort far beyond what I could muster right now!


TypeScript: Consider extending model class from model interfaces

Current design:
interface User
{
name: string
}

class User implements IUser{
name: string
}

New design:
class User {
 name:string;
}

interface IUser extends Partial<User>{}

This helps in deduplicating some code and optimizing size.

closing as duplicate of #1730

@baywet this is not a duplicate. Do you mind if I reopen this?
#1730 focuses on just the serialization part.

@nikithauc, sure, sorry for jumping the guns here. Would you mind providing more context/details on the original post to help understand things please?

As we're moving to a model of interfaces only, this is no longer required. Closing


NameError: uninitialized constant Rule :: how is this suppose to work?

Where does Rule come from?
irb(main):023:0> schedule = IceCube::Schedule.new(Time.now) do |s|
irb(main):024:1*  s.add_recurrence_rule(Rule.daily.count(3))
irb(main):025:1>   s.add_exception_time(now + 1.day)
irb(main):026:1> end
NameError: uninitialized constant Rule
from (irb):24:in block in irb_binding' 	from /Users/btaylor/.rbenv/versions/2.1.4/lib/ruby/gems/2.1.0/gems/ice_cube-0.12.1/lib/ice_cube/schedule.rb:24:in initialize'
from (irb):23:in new' 	from (irb):23 	from /Users/btaylor/.rbenv/versions/2.1.4/bin/irb:11:in '
irb(main):027:0> Rule
NameError: uninitialized constant Rule
from (irb):27
from /Users/btaylor/.rbenv/versions/2.1.4/bin/irb:11:in `'

you need IceCube::Rule

seems the ReadMe document need to be modify

https://github.com/seejohnrun/ice_cube/pull/290


1.12 Pagination with user configurable rows in each page

The  is an infinitely scrolling list by nature.
Pagination component will be implemented for the purpose of changing the grid's items array on page change.
Component name TBD.
Reference implementation: https://cdn.vaadin.com/vaadin-grid/4.1.0-alpha1/demo/#grid-pagination-demos
UI specs:

Done in https://github.com/vaadin/px-data-grid/pull/117


Rest end point for run rules on list events and find aggregated object

Rest end point for run rules on list events and find aggregated object
Implemented code for multiple users access EI functionality.

Yes its good to have test report, But in this pull request we cont continue, We can implement those reports in separate pull request.


are here some runtime dependencies needed to be installed before running llama-box rebuild windows amd64 release binary file(llama-box.exe) on a clean windows env?

System: Win10-amd64-21H1 AVX2 is enabled
vc runtime env Installed: Microsoft Visual C++ 2015-2019 Redistributable(x64)-14.29.30139
download & unzip & run  llama-box rebuild windows amd64 release binary llama-box-windows-amd64-avx2.zip -> llama-box.exe
shell just get a empty line output and exit:
C:\llama-box>llama-box.exe -h

C:\llama-box>

Window log viewer has an application error message

<Event xmlns="http://schemas.microsoft.com/win/2004/08/events/event">
  <System>
    <Provider Name="Application Error" />
    <EventID Qualifiers="0">1000</EventID>
    <Version>0</Version>
    <Level>2</Level>
    <Task>100</Task>
    <Opcode>0</Opcode>
    <Keywords>0x80000000000000</Keywords>
    <TimeCreated SystemTime="2024-12-14T01:14:30.9476968Z" />
    <EventRecordID>782</EventRecordID>
    <Correlation />
    <Execution ProcessID="0" ThreadID="0" />
    <Channel>Application</Channel>
    <Computer>ADMIN9922</Computer>
    <Security />
  </System>
  <EventData>
    <Data>llama-box.exe</Data>
    <Data><IP_ADDRESS></Data>
    <Data>674fb3c7</Data>
    <Data>MSVCP140.dll</Data>
    <Data>14.29.30139.0</Data>
    <Data>61b17c25</Data>
    <Data>c0000005</Data>
    <Data>0000000000013020</Data>
    <Data>1758</Data>
    <Data>01db4dc58728aeef</Data>
    <Data>C:\llama-box\llama-box.exe</Data>
    <Data>C:\Windows\SYSTEM32\MSVCP140.dll</Data>
    <Data>1d667bcf-52a3-4ddc-b757-6f1d10250424</Data>
    <Data>
    </Data>
    <Data>
    </Data>
  </EventData>
</Event>

are here some runtime dependencies needed to be installed before running llama-box rebuild windows amd64 release binary file(llama-box.exe) on a clean windows env?

have you try ./llama-box.exe -h?

yes, i retried, it is .\llama-box.exe -h on windows and it needn't in windows command shell normally. only output a empty line in command shell.

@shenliqing so it works for you?

not works yet.
my error is https://github.com/gpustack/llama-box/releases/download/v0.0.93/llama-box-linux-amd64-avx2.zip can not run alone on a clean win 10 (versions: 21h1 and 22h2) / win11 systems which is not installed  whole gpustack app.

Hi, i have finded the runtime dependency for running llama-box rebuild windows amd64 release binary( llama-box-windows-amd64-avx2.zip / llama-box.exe) alone :
it need the "Visual C++ Redistributable for Visual Studio 2015-2022" be installed.
my env is Microsoft Visual C++ 2015-2019 Redistributable(x64) and .\llama-box.exe -h cant not work.
when i installed "Visual C++ Redistributable for Visual Studio 2015-2022", .\llama-box.exe -h can work correctly.

Thank you for the reply and concern, maybe pre-build llama-box.exe with vc++ runtime static compile option is a good way to use llama-box.exe in any win10 env as a portable exe.

Thank you for the reply and concern, maybe pre-build llama-box.exe with vc++ runtime static compile option is a good way to use llama-box.exe in any win10 env as a portable exe.


select all references to a local variable

find all references to a local variable. ctrl+d is not very nice as it's file-scoped

And "find all reference"? It's helpful while read some code.

Found this tools: https://godoc.org/golang.org/x/tools/oracle


Two dimensional array access in go vs C

I have the following code in C where I attempt to access elements of a two D int array
#include <stdio.h>
#include <time.h>
void main ()
{
int tr_nextstate[8][2] = {{0, 4}, {4, 0}, {5, 1}, {1, 5}, {2, 6}, {6, 2}, {7, 3}, {3, 7}};
int i, j,next_state=0;
clock_t start, end;
double cpu_time_used;
start = clock();
for (i = 0; i < 100000000; i++)
{
j = i % 2;
next_state = tr_nextstate[next_state][j];
}
end = clock();

cpu_time_used = ((double) (end - start)) / CLOCKS_PER_SEC*1000;
printf("fun() took %f milliseconds to execute \n", cpu_time_used);
}
I have the same code in go :
package main
import (
"fmt"
"time"
)
func main() {
tr_nextstate := [][]int{{0, 4}, {4, 0}, {5, 1}, {1, 5}, {2, 6}, {6, 2}, {7, 3}, {3, 7}}
next_state := 0
var j int
startTime := time.Now()
for i := 0; i < 100000000; i++ {
	j:= i % 2
	next_state = tr_nextstate[next_state][j]

}
fmt.Printf("\nTime Elapsed : %v", time.Since(startTime))

}
When I run both the codes in my machine.
C - code gives a runtime of roughly 400 milliseconds
Go-code gives a runtime of roughtly 550 milliseconds
Can anyone throw light on why so?
My machine runs kubuntu 15.04 with i5 @2.4GHz with 16GB RAM

Can anyone throw light on why so?

Go programs always bounds check array access, where C programs do not.

Please raise this question on the mailing list, golang-nuts. The issue tracker is only for bugs.


Adding support for logstash http input

Hi guys, hereby my modded version for adding Logstash support (http input filter).
I was not able to test the direct input to ES, but it should still work. Hopefully one of you can easily test this?

Thank you very much @jeffrey-e . Sorry for the late response. I will give this a try . Hey @thomaspatzke , do you think you can test this too just in case so that it doesnt break your import to ES? Thank you in advance man!

Thank you again @jeffrey-e !


error animation in certain webs

Hi!
If enter in some urls like below you see that some elements are randomly rotating:

https://watracz.com/ (web itself)
https://gocdkeys.com/en/search?product=red (the load more bar below)

Searching in the code the .loader class had the fault.

Hey @Nisgrak !
The issue has been reproduced and we have started working on it. We will be releasing a fix soon.
Thank You for the feedback and if you find SpanTree useful, do spread the word!

Hey @Nisgrak !
The issue has been fixed. Thanks for the bug report. The update will be released on the Chrome Web Store and Mozilla Addons within a day.


adding bitrig support to installer

this fixes an error in the installer when run on Bitrig.

Thanks for the pull request, and welcome! The Rust team is excited to review your changes, and you should hear from @brson (or someone else) soon.
If any changes to this PR are deemed necessary, please add them as extra commits. This ensures that the reviewer can see what has changed since they last reviewed the code. The way Github handles out-of-date commits, this should also make it reasonably obvious what issues have or haven't been addressed. Large or tricky changes may require several passes of review and changes.
Please see the contribution instructions for more information.

Thanks! For this to take effect the rust-installer submodule will need to be updated in rust, cargo, and rust-packaging.


Link every heading automatically

Fixes #434
How it looks:

With :hover

URL:

Tested on Safari.

Note: this still needs some loving. Navigating to an URL with hash covers the header of section, because it's rendered below the heading. We might need to hack CSS to solve it.

I think showing a "#" before the heading is nicer than underline. Underline feels like it's link that'll take me somewhere.

Not really sure.  It's the same. Adding # requires additional work that I believe can be carried in next PR.

React Native docs show a pound sign https://facebook.github.io/react-native/docs/getting-started.html#content

Okay, fixed :) Used a different approach to avoid un-semantic use of a and absolute positions.


Removes 'WorldOfP2P'

Dead site.

https://github.com/Igglybuff/awesome-piracy/pull/524#issuecomment-848969254


SENRAN KAGURA Peach Ball: Backwards characters

For some reason during cutscenes, character models are backwards, this issue goes away as soon as i set proton to use wined3d.

How it should look.

Software information
SENRAN KAGURA Peach Ball
System information

GPU: AMD Van Gogh
Driver: Mesa 23.1.3
Wine version: Experimental
DXVK version: Unsure

Apitrace file(s)

Put a link here

For instructions on how to use apitrace, see: https://github.com/doitsujin/dxvk/wiki/Using-Apitrace
Log files
Please attach Proton or Wine logs as a text file:

When using Proton, set the Steam launch options for your game to PROTON_LOG=1 %command% and attach the corresponding steam-xxxxx.log file in your home directory.
When using regular Wine, use wine game.exe > game.log 2>&1 and attach the resulting game.log file.

steam-1074080.log.txt

Please make an apitrace.

Can confirm that fixes it on my windows laptop, thank you. Presuming it will also fix on deck whenever proton pulls in DXVK again.


Provide an option to backup world data when server version changes

Hard requirements:

[ ] handle TYPE=VANILLA
[ ] use level in server.properties and/or LEVEL var to account for both config styles
[ ] create backup as tar.gz in the /data directory named with a prefix the same as the level name

Open questions

[ ] keep only one backup and overwrite or increment a backup index?

Could implement variable for user to decide one backup or incremental.


How to share VeeValidator from Vuex store to all children

VueJs: "^2.5.16"
Vee-Validate: "^2.0.9"

How do I share the VeeValidator vuex store to all the children component ?

import Vuex from 'vuex';
Vue.use(Vuex);

import VeeValidate from 'vee-validate';

// Rename the error Bag to avoid the collision with other similar namespace in global
Vue.use(VeeValidate, {
    errorBagName: 'vFormErrors',
    events: 'change'
});

import { Validator } from 'vee-validate';

export default new Vuex.store({
  state: {
     // ... Add Error Bag
   },

   getters: {
      // Add getters for VeeValidator error bag
   }
});

Sorry I am going to check for documentation.

You can check here if are still stuck:
https://baianat.github.io/vee-validate/advanced/

@logaretm Thank you very much and I was able to figure it out. I think I started with wrong architecture. I was trying to store the ErrorBag itself in the vuex store state. This should not be necessary as VeeValidate is a global component that should be registered on the parent component and then we can share that instance to children. And once the same VeeValidate instance is shared with parent and children, it  solves the purpose so need to go extra mile to add ErrorBag to Vuex store.


Save icon snapshot is not attached to brush

After clicking "Save Sketch", the snap shot frame(yellow box in below image) stays floating in the air.

I found out in SaveIconTool.cs, LateUpdateTool function is not called.
Not sure if this is the root cause.

Hi! Is this in the XR beta?

I am using feature/xr_v2 branch.

Thanks, I have a feeling I know where this is coming from, it's on my fix list for today/tomorrow. Thanks for submitting!
I believe this is from the Mobile Bloom script attached to the mono camera used to take the snapshots. Something changed between 2019 and 2021 that breaks how this functions for mono cameras compared to the stereo camera used for the HMD.

Fixed on xr_v2 #237 in 7f3e6a4c98c2e8985d5a55cdc429219a32615d59


file upload feature

Description
feature to upload file to AWS S3 from SDK
Changes

added boto3 to requirements.txt
created API.upload_file() method

Tests

Known Issues

not sure if the url_expire_time is too long or too short

Notes

big thanks to @fatjon95 for helping me with the creation of this method! 🎉

Checklist

[ ] My name is on the list of contributors (CONTRIBUTORS.md) in the pull request source branch.

@InnocentBug from what I understand I believe there would need to be a different token for file uploads, but this might also be just us in development stage and it might change going forward, not sure.
I think if we end up with 2 tokens we could possibly do something like
api = cript.API(host="https://criptapp,org", api_token="my api token", file_upload_token="my Globus/S3 token")

@InnocentBug from what I understand I believe there would need to be a different token for file uploads, but this might also be just us in development stage and it might change going forward, not sure.
I think if we end up with 2 tokens we could possibly do something like
api = cript.API(host="https://criptapp,org", api_token="my api token", file_upload_token="my Globus/S3 token")

I see that makes sense.
Ideally we get the second token from CRIPT during the handshake.
I.e. the back end stores the the file_upload_token.
And when we create the API object we get that token from the back end (authenticated with the CRIPT TOKEN).
But temporary for development this might be fine.

for file upload my first idea is this, but not sure about the flow of it honestly. Let me know what you think
import cript

with cript.API(host=None, token=None) as api:
    # upload and get back an S3 file link
    uploaded_file_source: str = api.upload_file(absolute_file_path="C:\\users\\username\\onedrive\\desktop\\my_file.txt")

    # use S3 file link
    my_file = cript.File(source=uploaded_file_source, type="my file type")

    # continue with the rest as usual
    my_data_node = cript.Data(name="my data node", file=[my_file], type="my data type")

in the JSON it will have the file source written as
{
    "node": ["file"],
    "name": "my file name",
    "type": "my file type",
    "source": "https://aws.123456.s3.link.come",
    "extension": ".csv"
}

Note: I think in the future we can also add relative file paths as well but I did not add it here because I've noticed in the past that ../../my_file.txt is not from where the file is, but from where the program has been ran which introduces another complication, but I think eventually I think we can make it work.

for file upload my first idea is this, but not sure about the flow of it honestly. Let me know what you think
import cript

with cript.API(host=None, token=None) as api:
    # upload and get back an S3 file link
    uploaded_file_source: str = api.upload_file(absolute_file_path="C:\\users\\username\\onedrive\\desktop\\my_file.txt")

    # use S3 file link
    my_file = cript.File(source=uploaded_file_source, type="my file type")

    # continue with the rest as usual
    my_data_node = cript.Data(name="my data node", file=[my_file], type="my data type")

in the JSON it will have the file source written as
{
    "node": ["file"],
    "name": "my file name",
    "type": "my file type",
    "source": "https://aws.123456.s3.link.come",
    "extension": ".csv"
}

Note: I think in the future we can also add relative file paths as well but I did not add it here because I've noticed in the past that ../../my_file.txt is not from where the file is, but from where the program has been ran which introduces another complication, but I think eventually I think we can make it work.

I think we should capsulate that a little better for the user.
The user should write something like this:
import cript

with cript.API(host=None, token=None) as api:
    my_file = cript.File(absolute_file_path="C:\\users\\username\\onedrive\\desktop\\my_file.txt", type="my file type")

    # continue with the rest as usual
    my_data_node = cript.Data(name="my data node", file=[my_file], type="my data type")

And upon the first time the node is converted into json, we trigger a function within the file node.
So we overload the get_json function of file like this.
class File:
   def get_json(self):
       if self.absolute_file_path is not None: # File hasn't been uploaded
               # upload and get back an S3 file link
               api = _get_cached_global_api()
               uploaded_file_source: str = api._upload_file(self.absolute_file_path)
               # Error checking
               self._json_attrs = replace(self._json_attrs, source = uploaded_file_source) # store the source for json serialization
               self.absolute_file_path = None # Signal that file has been successfully uploaded
       # Call parent `get_json` for actual serialization
       return super().get_json(self)

and set the source in json_attr.
Should be pretty simple to do. And hides all the complications from the user.
And this automatically keeps track to only do this once.

for file upload my first idea is this, but not sure about the flow of it honestly. Let me know what you think
import cript

with cript.API(host=None, token=None) as api:
    # upload and get back an S3 file link
    uploaded_file_source: str = api.upload_file(absolute_file_path="C:\\users\\username\\onedrive\\desktop\\my_file.txt")

    # use S3 file link
    my_file = cript.File(source=uploaded_file_source, type="my file type")

    # continue with the rest as usual
    my_data_node = cript.Data(name="my data node", file=[my_file], type="my data type")

in the JSON it will have the file source written as
{
    "node": ["file"],
    "name": "my file name",
    "type": "my file type",
    "source": "https://aws.123456.s3.link.come",
    "extension": ".csv"
}

Note: I think in the future we can also add relative file paths as well but I did not add it here because I've noticed in the past that ../../my_file.txt is not from where the file is, but from where the program has been ran which introduces another complication, but I think eventually I think we can make it work.

I think we should capsulate that a little better for the user. The user should write something like this:
import cript

with cript.API(host=None, token=None) as api:
    my_file = cript.File(absolute_file_path="C:\\users\\username\\onedrive\\desktop\\my_file.txt", type="my file type")

    # continue with the rest as usual
    my_data_node = cript.Data(name="my data node", file=[my_file], type="my data type")

And upon the first time the node is converted into json, we trigger a function within the file node. So we overload the get_json function of file like this.
class File:
   def get_json(self):
       if self.absolute_file_path is not None: # File hasn't been uploaded
               # upload and get back an S3 file link
               api = _get_cached_global_api()
               uploaded_file_source: str = api._upload_file(self.absolute_file_path)
               # Error checking
               self._json_attrs = replace(self._json_attrs, source = uploaded_file_source) # store the source for json serialization
               self.absolute_file_path = None # Signal that file has been successfully uploaded
       # Call parent `get_json` for actual serialization
       return super().get_json(self)

and set the source in json_attr. Should be pretty simple to do. And hides all the complications from the user. And this automatically keeps track to only do this once.

I think this can work and it could make the user's workflow a bit easier. I don't know too much about the get_json function though, so that I would refer to you

should this PR go into the validate branch or into develop branch directly?

should this PR go into the validate branch or into develop branch directly?

probably either is fine.
The tricky bit is testing this branch.

should this PR go into the validate branch or into develop branch directly?

probably either is fine. The tricky bit is testing this branch.

I fully agree, and there are a few complications with testing upload and download regardless.
upload writing tests will be tricky because we don't want to use infinite cloud storage
download functionality in general might be tricky because we have to allow users to explore the available files that they have access to

putting this PR into the file upload and download pr

putting this PR into the file upload and download pr


Resources.Deployments API should return the ExpressionEvaluationOptions property in response

After tested, seems Resources.Deployments API wouldn't return the ExpressionEvaluationOptions property in response. I assume it should be returned in the response since this property could be set in the request body.

@Azure/arm-template-deployments @rajshah11 @vivsriaus , could you have a look at this ARM resource template issue? If you're not the owner, please add appropriate contact. Thanks.

@Azure/arm-template-deployments @rajshah11 @vivsriaus , could you have a look at this ARM resource template issue? If you're not the owner, please add appropriate contact. Thanks.


Release/v0.5.2

First public release

Glad to see this project back on trail! Keep up the good work 💪

Thanks! I've put a lot of effort in this, kind of a promise to myself 😅
Will be ready soon enough!


add check for exclamation mark in absolute path

What kind of change does this PR introduce?
Bug fix.
Did you add tests for your changes?
No.
If relevant, link to documentation update:
N/A
Summary
If users use ! in their directory names, webpack will generate a bunch of unhelpful errors. This commit introduce a check in validation period, which makes webpack more user-friendly. See issue #6742 and #5320 for more information.
Does this PR introduce a breaking change?
No.
Other information
N/A

Closing because there is already a PR (#6754) for this. Please contribute there instead of opening new competing PRs. That's not nice.


NativeBase on NPM comments out Spinner & ProgressBar

Seems to be commented out in the current master branch as well, but is pretty annoying if you are sharing a code base with multiple people and node_modules are not committed to git (which they shouldn't be).

We couldn't get the ProgressBarAndroid path to work. So had to comment it out. You can have a go at it  by uncommenting it but it'll error out in Android.

is it the same issue with the spinner?

Yes, Spinner component too. More details here https://facebook.github.io/react-native/docs/progressbarandroid.html

Spinner added in v0.5.0

I just pulled 0.5.0 into my repo to test out and I'm seeing the following for the spinnner

I'll investigate further and post most to see if I can fix it.

So i think the issue has to do with the ActivityIndicator. I'm currently on RN 0.27 but ActivityIndicator isn't introduced until 0.28. Probably need to make 0.28 a dependency/requirement for Nativebase 0.5

Works once upgraded to 0.30 React Native. Going to close this out


Because every version of flutter_test from sdk depends on quiver 2.0.5 and flutter_whirlpool depends on quiver 2.1.3, flutter_test from sdk is forbidden.

[flutter_whirlpool] flutter pub get
Running "flutter pub get" in flutter_whirlpool...
Because every version of flutter_test from sdk depends on quiver 2.0.5 and flutter_whirlpool depends on quiver 2.1.3, flutter_test from sdk is forbidden.
So, because flutter_whirlpool depends on flutter_test any from sdk, version solving failed.
pub get failed (1; So, because flutter_whirlpool depends on flutter_test any from sdk, version solving failed.)
exit code 1

What version of flutter do you have?
This app needs Flutter 1.17+. And your error sounds like you have something below.

Why is the particle scrolling effect stuck on the ios simulator? Works fine on Android devices, but there are still noticeable dropped frames

Physics simulation needs more power than a regular application. It's hard for me to answer your question. If you have run applications on an for example iPhone 12 max emulator, and on Android with a much lower resolution, I'm not surprised that there are drops on iPhone emu.  You didn't give enough details. The emulator needs good hardware to make it behave like a real device.
Please, describe one problem per issue and always provide more details.
If you can run Flutter project then I will close this issue.


Unable to Click Theme Switch

While using mouse it's impossible to click on the dark/light mode switch button

Hi @VishalTheHuman
Thank you for pointing out the bug.
I will look into it.
Much appreciated.