conda install cupy installs wrong toolkit version with CUDA 11.0 on Windows

conda create --name cutest cupy installs toolkit version 11.2 when I have CUDA 11.0 installed. This raises the error below.
conda create --name cutest2 cupy cudatoolkit=11.0 works fine.
Ideally, conda would check which cudatoolkit version should be installed. Is this currently possible?
If not - would it be possible to check that the versions match on import cupy, and then raise a more useful error?
I check CUDA version by nvcc --version: version 11.0 is installed (using 11.0 for compatability reasons with other software)
Both cp.linspace(0, 10, 10) and cp.show_config() result in essentially the same error:
$ python -c 'import cupy; cupy.show_config()'
Traceback (most recent call last):
  File "<string>", line 1, in <module>
  File "C:\Users\thomasaar\Miniconda3\envs\cutest\lib\site-packages\cupy\__init__.py", line 860, in show_config
    _sys.stdout.write(str(_cupyx.get_runtime_info()))
  File "C:\Users\thomasaar\Miniconda3\envs\cutest\lib\site-packages\cupyx\_runtime.py", line 277, in get_runtime_info
    return _RuntimeInfo()
  File "C:\Users\thomasaar\Miniconda3\envs\cutest\lib\site-packages\cupyx\_runtime.py", line 156, in __init__
    self.cublas_version = _eval_or_error(
  File "C:\Users\thomasaar\Miniconda3\envs\cutest\lib\site-packages\cupyx\_runtime.py", line 64, in _eval_or_error
    return func()
  File "C:\Users\thomasaar\Miniconda3\envs\cutest\lib\site-packages\cupyx\_runtime.py", line 158, in <lambda>
    cupy.cuda.device.get_cublas_handle()),
  File "cupy\cuda\device.pyx", line 46, in cupy.cuda.device.get_cublas_handle
  File "cupy\cuda\device.pyx", line 47, in cupy.cuda.device.get_cublas_handle
  File "cupy\cuda\device.pyx", line 29, in cupy.cuda.device._get_device
  File "cupy_backends\cuda\api\runtime.pyx", line 289, in cupy_backends.cuda.api.runtime.getDevice
  File "cupy_backends\cuda\api\runtime.pyx", line 261, in cupy_backends.cuda.api.runtime.check_status
cupy_backends.cuda.api.runtime.CUDARuntimeError: cudaErrorInvalidValue: invalid argument

Conditions (you can just paste the output of python -c 'import cupy; cupy.show_config()')

The above call results in the same error.
CuPy version: 9.0.0
OS/Platform: Windows 10 v1909
CUDA version: 11.0

Alright! I've posted conda-forge/cupy-feedstock#128 :)


Parsec config can prevent ParsecConnectedCondition.cs's event listeners from triggering

Great application, exactly what I was looking for although initially it wouldn't work for me. Quickly found out it was due to my Parsec config.txt, which contains:
server_resolution_x=-1
server_resolution_y=-1
server_admin_mute=0

These settings prevent your speakers from being muted and preserve the host's resolution.
Which, of course, prevents both event listeners that point to this.CheckConditionMet(); from being triggered.
Was wondering if you have thought any extra events that the application could possibly be listening for. Maybe it'd be possible to listen for a new UDP connection directly.
For now I've just set server_admin_mute=1 as a workaround.

Thanks for submitting an issue! I could definitely add more event listeners. I figured those two would cover most people. Evidently I was wrong. 🙂
Here's what I'm thinking:

Listen for new UDP connections like you suggested. If there is some system event for this, that would be ideal. I'd like to avoid polling if possible.
Listen for the Parsec connected notification in windows. UWP has an API for this, but I think it requires admin rights. I'd like to avoid that as well. I've also turned those notification off on my system.
Listen for new active audio sessions. I'm doing something similar in ParsecConnectedCondition.HasAnyActiveAudioSessions. Maybe the NAudio.CoreAudioApi.AudioSessionManager.OnSessionCreated event could be useful. This is probably what I would try first.
Listen for new virtual input devices created by Parsec. Gamepads, mouse, keyboard, etc. Not sure how this would be done.

Unfortunately I won't have time to work on this until next weekend. If you come up with a solution before then, send me a pull request and I'll take a look. Otherwise I'll work on this then.
Thanks again!

I had a look this afternoon, NAudio.CoreAudioApi.AudioSessionManager.OnSessionCreated wasn't fired, at least not in the way I had implemented it. Next I had a look at the Parsec SDK: https://github.com/parsec-cloud/parsec-sdk
I was unable to add the Windows libraries, possibly because they're not compatible with .NET core.

I was however able to add the ParsecUnity46.dll, there's some interesting events:

However I believe it has a dependency to the UnityEngine, so sadly wasn't able to use it.

CS0012	The type 'MonoBehaviour' is defined in an assembly that is not referenced. You must add a reference to assembly 'UnityEngine, Version=<IP_ADDRESS>, Culture=neutral, PublicKeyToken=null'.
You'd think there'd be a solution to this use case somewhere in Parsec already. All we'd really need is the ability to have the host run a application / script when a remote connection gets established. Could be one line in the config file.
I was also thinking about how other gaming systems' UIs have been implemented. Usually you'd have a home button, to go back to a menu where you can quit your current game and go back to the main menu. Maybe this could be a solution, because then you'd have a way to regain control no matter what state the host system is in. I haven't tested it yet, but for an Xbox one controller it'd be the guide / xbox button at the top.

The Parsec SDK was one of the first things I looked into. I was never able to get it to work. I think it's meant for creating parsec connections outside of the official client. Pretty cool in general but not very helpful for me. I assume the Unity version does something similar.
Anyway, I spend some time this morning and I think I have a fix for this. I was able to use the OnSessionCreated event in tandem with the AudioSessionControl.RegisterEventClient() method to listen for state changes on the Parsec audio session. After debugging this, it looks like Parsec creates the audio session when it starts up, but leaves it in an inactive state. When a client connects, that session goes to active. Using both events together seems to pretty reliably detect connections even when the original display and mute events don't fire.
I went ahead and created a new release. Let me know if it works for you and I'll close this issue. 🙂

Just tested it, works well, thanks!


OOP view

Can I create views in OOP style? How in tornado or in Django CBV.

Sorry, I don't follow.
router registers any callable accepting the single request argument.
What forbid you to use class inheritance etc for organizing handlers in desirable way?
BTW The question should be asked in aiohttp itself not CORS.

I create new route as: (method, url, handler). If I create class:
class Handler():
    def get(self, request):
        ...
    def post(self, request):
        ...

I will have to add twice the class into routing for get and post method.

I still don't understand what is your question?
What do you want to achieve?

I want create class handler as shown below and it into router for application:
app.router.add_route(url, handler)

without method.

@WolkoDav, I don't really understand your question/bug report.
I think what you are asking is outside aiohttp_cors library scope, as @asvetlov mentioned.
(aiohttp_cors is a small library that adds Cross Origin Resource Sharing support to aiohttp.)
I suggest you to ask this question on aio-libs mailing list (also you can write there in Russian language).
If you want to use something similar to Class Based View you can implement it by yourself, e.g. as @asvetlov pointed here.
There is no standard CBV wrappers implementations for aiohttp AFAIK, but it's not hard to write one for yourself (and even contribute it to aiohttp if you manage to implement good generic and useful CBV).

Note about CBV: I see that @sloria implemented one in aiohttp_utils library: https://aiohttp-utils.readthedocs.org/en/latest/index.html
aiohttp_cors shouldn't work with aiohttp_utils, but I think support can be implemented pretty easily.


So many NPC fixes

Rewrites based on original japanese. May need to check for context.

Rewrites based on original japanese. May need to check for context.


Error 1055 on Cancel while adding dynamic user event

I experienced it with LabVIEW 2016.0f5 32 bit, JKI state machine editor v2<IP_ADDRESS>.
Steps to reproduce:

Right-click on the node inside the JKI state machine.
Select "Add Dynamic Events".
Then click "Cancel" in the appeared window.
The following error occurs:

Upd: if I select "Add Dynamic Events" from state machine helper window, and then cancel it - no error occurs.

Good catch! Thanks for reporting this.
Jim Sent from my mobile.

Thank you, @jimkring !
There is also similar behavior, when right-click on string constant, which is not connected (directly, or via other nodes) to "Add states to the queue" node. Then, the following menu is available:

And if I select some of those menu items ("Find Callers", etc.), then the same error occurs.
I guess, that this menu is also kind of a bug?

Yes, that’s another bug. Good catch! Glad your helping catch all these.
Thanks.
Jim Sent from my mobile.

Hi @kosist. I can't seem to reproduce this issue. Are you still able to reproduce it with the latest release?

Hello @jimkring. Yes, it still occurs...

Yes, I have it enabled.
But when I disable it, the error dialog window anyway appears.
I've checked the VI where it occurs, and it seems that now reason is clear - it checks, if selected constant is "Is state string?". If no, then it does not passes string reference further, and executes next case structure, but it has empty reference as input. And at the end of the VI there is Simple Error Handler dialog window...
Should there just be connected that missing wire, or in case when it is not state string, no action should be executed at all, please?

Thanks for posting that screenshot -- this makes sense and I see some other possible issues with that code that I will clean up. Thanks again!

This should be fixed in Release 2<IP_ADDRESS>.  Would you please test and let me know how it's working for you? Thanks!

Hello @jimkring! Thank you, seems that now it's working without any errors.
Thank you!

Great! 👍🏻
Jim Sent from my mobile.

Hi
When adding an empty JKI SM I can add dynamic events. I have a working program (a queued state machine with several loops) that is working fine. When I try to add Dynamc Events to the main JKI loop, after the animation, it throws Error 1055. LV 2017 and JKI 2018
Thanks for any clues


oeq-ts-rest-api: Add support for /userquery/search

Checklist

[x] the contributor license agreement is signed
[x] commit message follows commit guidelines
[x] tests are included

Description of change

Primarily the change here was to add support for the /userquery/search endpoint in the form of UserQuery.ts. But then when I noticed the formatting on my commits was not correct I added that support to the oeq-ts-rest-api module by applying the final tweaks tooeq-ts-rest-api/package.json and oeq-ts-rest-api/.eslintrc.js. On running that, suddenly I found many other files were also a bit out of wack.
So unfortunately this PR now contains a lot more noise than I'd like. Here is a run down to the help:
Feature (ccf789a):

UserQuery.ts
UserQuery.test.ts
Auxillary: Common.ts, index.ts, TestConfig.ts

Ran the tests:
Test Suites: 7 passed, 7 total
Tests:       23 passed, 23 total
Snapshots:   0 total
Time:        4.905 s
Ran all test suites.

Cool. I'm going to merge even with that failed PackageAndNavigation test - as these changes have no impact on the core code at this point.


Date format with pre-hash string

Hi,
In rule 8 of the algorithm, you say:
All timestamps SHALL be expressed in UTC; the zero UTC offset SHALL be expressed with the capital letter 'Z'.

which means that timestamps can have a time offset, right?
This is indeed the case of the time field of a sensorMetadata. If you look at the example epcisDocWithSensorDataObjectEvent.jsonld, the pre-hash string is:
sensorMetadatatime=2019-04-02T14:05:00.000+01:00

(It keeps the offset so everything is working as expected)
However, when you look at the pre-hash string of the last event in SensorDataExamples.xml, we have this field:
<declarationTime>2020-09-29T15:00:00.000+02:00</declarationTime>

But in the pre-hash string, it converts the date like this:
declarationTime=2020-09-29T13:00:00.000

Is it the expected output? If it is the case, do I miss something in the algorithm?
Thanks a lot.

Dear @clementh59 ,
Good catch! You are correct. All timestamps should be converted to zero UTC.
I hope you do not need a fix urgently? ;-)
Kind regards and thanks again;
Ralph

Dear @RalphTro ,
I see, thanks!
No, that's ok, I just want to be sure I understand the algorithm correctly :)
Regards,
Clément


[TS migration] Remove 'OptionsSelector' component

Details

Fixed Issues

$ https://github.com/Expensify/App/issues/25125
PROPOSAL:
Tests

Go to small room.
Create split expense / submit expense.
Provide amount (e.g. 100).
Verify that values are displayed correctly.
There should be some space between the Show more and Submit buttons (depending on the room size).
Go to huge room (with at least 20 users) (crowded policy - #huge-room)
Do all previous steps.
Verify that the list is scrollable and clickable (values should update if someone is "unclicked").
Create split expanse / submit expense and add scan with wrong file type (there should be warning Password-protected PDF is not supported)

Offline tests

QA Steps

Go to small room.
Create split expense / submit expense.
Provide amount (e.g. 100).
Verify that values are displayed correctly.
There should be some space between the Show more and Submit buttons (depending on the room size).
Go to huge room (with at least 20 users) (crowded policy - #huge-room)
Do all previous steps.
Verify that the list is scrollable and clickable (values should update if someone is "unclicked").
Create split expanse / submit expense and add scan with wrong file type (there should be warning Password-protected PDF is not supported)

PR Author Checklist

[x] I linked the correct issue in the ### Fixed Issues section above
[x] I wrote clear testing steps that cover the changes made in this PR

[x] I added steps for local testing in the Tests section
[x] I added steps for the expected offline behavior in the Offline steps section
[x] I added steps for Staging and/or Production testing in the QA steps section
[x] I added steps to cover failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[x] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)
[x] I tested this PR with a High Traffic account against the staging or production API to ensure there are no regressions (e.g. long loading states that impact usability).

[x] I included screenshots or videos for tests on all platforms
[x] I ran the tests on all platforms & verified they passed on:

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

[x] I verified there are no console errors (if there's a console error not related to the PR, report it or open an issue for it to be fixed)
[x] I followed proper code patterns (see Reviewing the code)

[x] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick)
[x] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[x] I verified that comments were added to code that is not self explanatory
[x] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[x] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method

[x] If any non-english text was added/modified, I verified the translation was requested/reviewed in #expensify-open-source and it was approved by an internal Expensify engineer. Link to Slack message:

[x] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[x] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[x] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[x] I verified the JSDocs style guidelines (in STYLE.md) were followed

[x] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[x] I followed the guidelines as stated in the Review Guidelines
[x] I tested other components that can be impacted by my changes (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar are working as expected)
[x] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[x] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[x] I verified that if a function's arguments changed that all usages have also been updated correctly
[x] If any new file was added I verified that:

[x] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[x] If a new CSS style is added I verified that:

[x] A similar style doesn't already exist
[x] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG))

[x] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[x] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[x] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[x] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[x] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[x] I verified that all the inputs inside a form are aligned with each other.
[x] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[x] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[x] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.

Screenshots/Videos

Android: Native

https://github.com/Expensify/App/assets/61014013/1109851c-ae1d-4e90-b08d-d4c8b97d2da2

Android: mWeb Chrome

https://github.com/Expensify/App/assets/61014013/e986de25-9b24-40f9-abf0-76ad1641ee02

iOS: Native

https://github.com/Expensify/App/assets/61014013/3a9c4fa6-04ea-4c88-8567-14142839bf4a

iOS: mWeb Safari

https://github.com/Expensify/App/assets/61014013/72bd11c0-98a2-4301-b82f-72e113f74492

MacOS: Chrome / Safari

https://github.com/Expensify/App/assets/61014013/8d222309-d4bf-48cb-b938-9ea2314a4909

MacOS: Desktop

https://github.com/Expensify/App/assets/61014013/4f5c8b80-4683-455e-927b-0eac100357be

The main problem I've encountered here is that previously (in OptionsSelector) children and lists were displayed inside the ScrollView. Now they're not so after the migration MoneyRequestConfirmationList looks like that:

in small room

in huge room

Basically amount, description, ... are at the bottom and they are here all the time (aren't scrollable). Should we try doing it like it was before or maybe that solution is sufficient?

To do it like previously we would need to modify the BaseSelectionList by adding two ScrollViews like it was done before
<ScrollView style={{flexGrow: 1}}>
    <ScrollView
        horizontal
        bounces={false}
        contentContainerStyle={{flex: 1, flexDirection: 'column'}}
    >
    ...

In this case the performance is worse and we need to wait some for a click to happen (in huge room)
https://github.com/Expensify/App/assets/61014013/27a40e2a-5553-4665-a888-e6803d457f35

While working on this and recording videos I've encountered a bug (it is present on the main branch too)
The Password-protected PDF is not supported warning is not displayed on native app (iOS and android).
https://github.com/Expensify/App/assets/61014013/d69471fb-e812-4ce7-9ab2-811e9a12d1cd

The checkbox should only appear when starting a split from a report (not from global green button and not in a money request)
The rightElement style is not the same (the amount text)

@war-in Can you please tag me once this is ready for another review

Yup, will re-request review and tag you!

@s77rt It should be ready for review now :)

It turned out that there was another PR doing the same thing :/
I'll merge it and leave only necessary changes

Reviewer Checklist

[ ] I have verified the author checklist is complete (all boxes are checked off).
[ ] I verified the correct issue is linked in the ### Fixed Issues section above
[ ] I verified testing steps are clear and they cover the changes made in this PR

[ ] I verified the steps for local testing are in the Tests section
[ ] I verified the steps for Staging and/or Production testing are in the QA steps section
[ ] I verified the steps cover any possible failure scenarios (i.e. verify an input displays the correct error message if the entered data is not correct)
[ ] I turned off my network connection and tested it while offline to ensure it matches the expected behavior (i.e. verify the default avatar icon is displayed if app is offline)

[ ] I checked that screenshots or videos are included for tests on all platforms
[ ] I included screenshots or videos for tests on all platforms
[ ] I verified tests pass on all platforms & I tested again on:

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

[ ] If there are any errors in the console that are unrelated to this PR, I either fixed them (preferred) or linked to where I reported them in Slack
[ ] I verified proper code patterns were followed (see Reviewing the code)

[ ] I verified that any callback methods that were added or modified are named for what the method does and never what callback they handle (i.e. toggleReport and not onIconClick).
[ ] I verified that the left part of a conditional rendering a React component is a boolean and NOT a string, e.g. myBool && <MyComponent />.
[ ] I verified that comments were added to code that is not self explanatory
[ ] I verified that any new or modified comments were clear, correct English, and explained "why" the code was doing something instead of only explaining "what" the code was doing.
[ ] I verified any copy / text shown in the product is localized by adding it to src/languages/* files and using the translation method
[ ] I verified all numbers, amounts, dates and phone numbers shown in the product are using the localization methods
[ ] I verified any copy / text that was added to the app is grammatically correct in English. It adheres to proper capitalization guidelines (note: only the first word of header/labels should be capitalized), and is either coming verbatim from figma or has been approved by marketing (in order to get marketing approval, ask the Bug Zero team member to add the Waiting for copy label to the issue)
[ ] I verified proper file naming conventions were followed for any new files or renamed files. All non-platform specific files are named after what they export and are not named "index.js". All platform-specific files are named for the platform the code supports as outlined in the README.
[ ] I verified the JSDocs style guidelines (in STYLE.md) were followed

[ ] If a new code pattern is added I verified it was agreed to be used by multiple Expensify engineers
[ ] I verified that this PR follows the guidelines as stated in the Review Guidelines
[ ] I verified other components that can be impacted by these changes have been tested, and I retested again (i.e. if the PR modifies a shared library or component like Avatar, I verified the components using Avatar have been tested & I retested again)
[ ] I verified all code is DRY (the PR doesn't include any logic written more than once, with the exception of tests)
[ ] I verified any variables that can be defined as constants (ie. in CONST.js or at the top of the file that uses the constant) are defined as such
[ ] If a new component is created I verified that:

[ ] A similar component doesn't exist in the codebase
[ ] All props are defined accurately and each prop has a /** comment above it */
[ ] The file is named correctly
[ ] The component has a clear name that is non-ambiguous and the purpose of the component can be inferred from the name alone
[ ] The only data being stored in the state is data necessary for rendering and nothing else
[ ] For Class Components, any internal methods passed to components event handlers are bound to this properly so there are no scoping issues (i.e. for onClick={this.submit} the method this.submit should be bound to this in the constructor)
[ ] Any internal methods bound to this are necessary to be bound (i.e. avoid this.submit = this.submit.bind(this); if this.submit is never passed to a component event handler like onClick)
[ ] All JSX used for rendering exists in the render method
[ ] The component has the minimum amount of code necessary for its purpose, and it is broken down into smaller components in order to separate concerns and functions

[ ] If any new file was added I verified that:

[ ] The file has a description of what it does and/or why is needed at the top of the file if the code is not self explanatory

[ ] If a new CSS style is added I verified that:

[ ] A similar style doesn't already exist
[ ] The style can't be created with an existing StyleUtils function (i.e. StyleUtils.getBackgroundAndBorderStyle(theme.componentBG)

[ ] If the PR modifies code that runs when editing or sending messages, I tested and verified there is no unexpected behavior for all supported markdown - URLs, single line code, code blocks, quotes, headings, bold, strikethrough, and italic.
[ ] If the PR modifies a generic component, I tested and verified that those changes do not break usages of that component in the rest of the App (i.e. if a shared library or component like Avatar is modified, I verified that Avatar is working as expected in all cases)
[ ] If the PR modifies a component related to any of the existing Storybook stories, I tested and verified all stories for that component are still working as expected.
[ ] If the PR modifies a component or page that can be accessed by a direct deeplink, I verified that the code functions as expected when the deeplink is used - from a logged in and logged out account.
[ ] If the PR modifies the UI (e.g. new buttons, new UI components, changing the padding/spacing/sizing, moving components, etc) or modifies the form input styles:

[ ] I verified that all the inputs inside a form are aligned with each other.
[ ] I added Design label and/or tagged @Expensify/design so the design team can review the changes.

[ ] If a new page is added, I verified it's using the ScrollView component to make it scrollable when more elements are added to the page.
[ ] If the main branch was merged into this PR after a review, I tested again and verified the outcome was still expected according to the Test steps.
[ ] I have checked off every checkbox in the PR reviewer checklist, including those that don't apply to this PR.

Screenshots/Videos

Android: Native

Android: mWeb Chrome

Networking issue

iOS: Native

iOS: mWeb Safari

MacOS: Chrome / Safari

MacOS: Desktop

Can you please fix this styling bug, comparing to staging the user email is right next to the amount

@s77rt Fixed :)

:hand: This PR was not deployed to staging yet because QA is ongoing. It will be automatically deployed to staging after the next production release.

🚀 Deployed to staging by https://github.com/danieldoglas in version: 1.4.75-0 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅

🚀 Deployed to production by https://github.com/puneetlath in version: 1.4.75-1 🚀

platform
result

🤖 android 🤖
success ✅

🖥 desktop 🖥
success ✅

🍎 iOS 🍎
success ✅

🕸 web 🕸
success ✅


[Feature #4032] Add Redis Connector modules

Fixes #4032.
Motivation
Explain the content here.
Explain why you want to make the changes and what problem you're trying to solve.
Modifications
Describe the modifications you've done.
Documentation

Does this pull request introduce a new feature? (yes / no)
If yes, how is the feature documented? (not applicable / docs / JavaDocs / not documented)
If a feature is not applicable for documentation, explain why?
If a feature is not documented yet in this PR, please create a followup issue for adding the documentation

The data encoding and decoding still in progress.

please check checkstyle.

 please check checkstyle.

Just fixed it.
BTW is there any way to check it automatically in my local IDEA. How to make it import the dependancy with the order we need as the rules said.

@fabian4 Please see https://eventmesh.apache.org/zh/community/contribute/contribute


Write page for Economic Botany Data Collection Standard

Page(s) where issue occurs
https://www.tdwg.org/standards/economic-botany/
Issue description
Apart from some metadata, the page for this standard is empty. On GitHub there is an abstract and reference, but no actual standard. Is there anyone knows more about this standard and could write some content for this page?
I will hide the page from the navigation (status: hidden) until this is resolved.

There is an online version at kew.org. I've updated the page (no longer hidden). 2a27b38


feat: upgrade the minimum go version

What are those test data? I saw you added it?

What are those test data? I saw you added it?

testdata? not able to follow

what was the need to force push?

That's fuzz seed data for reproducibility

@bxcodec
1599694a935139af681ea380560b405c360ebb4d is the first bad commit
commit 1599694a935139af681ea380560b405c360ebb4d
Author: Iman Tumorang<EMAIL_ADDRESS>Date:   Wed Feb 28 15:25:46 2024 +0700

    feat: upgrade the mimimum go version

 .golangci.yaml               |  2 ++
 Makefile                     |  3 ++-
 db.go                        |  2 +-
 go.mod                       |  6 +++---
 go.sum                       |  4 ++++
 loadbalancer.go              | 13 +++----------
 loadbalancer_test.go         |  2 +-
 misc/makefile/tools.Makefile | 18 +++++++++---------
 8 files changed, 25 insertions(+), 25 deletions(-)

@bxcodec Kindly revert 1599694a935139af681ea380560b405c360ebb4d and cherrypick to a new branch.

Lol, it's the first commit. So it's failed even on the first commit

What is this automated commit for the fuzz tests? @Nasfame


update translation

Add few word which was not translated.

Thank you @johnroyer for providing these updates. Will merge in now for the next release.


Api version update

Updated modules in go.mod to their latest versions and updated code to match the new updates
Updated github.com/Azure/azure-sdk-for-go/services/netapp/mgmt/2020-06-01/netapp to github.com/Azure/azure-sdk-for-go/services/netapp/mgmt/2021-04-01/netapp in sdkutils.go

I missed this, we didn't add the update to CHANGELOG.md file.


Does it support ActiveRecord mode?

seems the document only say how to use it for DataMapper mode

Hi,
Although I have never tested this mode, I believe it will work if you will patch the repository instances. See Patching typeorm repository with base repository

👍 it works, thanks a lot.


New version: SymFEL v0.1.3

Registering package: SymFEL
Repository: https://github.com/ncindea/SymFEL.jl
Created by: @ncindea
Version: v0.1.3
Commit: f8d02d2af7b5c77014e461df5c69419abc365a70
Git reference: master
Release notes:

Update some functions and add new ones

please block these from being auto-merged. I corrected the version issue.


Skipping IAM system tests when running in emulator.

/cc @hbchai

@tseaver I had to rebase after #1745. Does this LGTY to merge? (Notice I added a comment in my _maybe_emulator_skip method.)

LGTM


Builds failing - pep8 upgraded

pep8.py 1.6 has just been released. It has introduced new tests, which are causing all Travis builds to fail with error E402:  see https://github.com/jcrocholl/pep8/pull/304#issuecomment-66939162
I'm looking into it

Fixed up quite a lot of whitespace issues. I have also disabled the flake8 E402 check in Makefile. We can reenable it once pep8.py has issued a fixed release for some of the issues (e.g. imports within a try..except block, we we use a fair bit)

pep8 conformance can and probably should be a proper test in unittest.  See http://pep8.readthedocs.org/en/latest/advanced.html
Currently, you (me) can forget to run before commit and then have Travis fail on you - when this task could be automated and run as part of py.test.  Comments?

@dundeemt I think we have earlier not added linting to the test suite, because a test suite must be lightning fast to serve its purpose. pylint takes much too long to be executed as a unittest, but pep8 is about a second on my laptop, which may be ok. What does everyone else thinks?

I wouldn't be inclined to add a pep8 check as part of the unit tests (though I not that pytest has a pep8 plugin which might be useful)
If you forget to check the code before commit (which I do regularly) you can set up a git pre-commit hook to run make for you.  This will run flake8 over the changed files and disallow the committing of any non-pep8 code.

@lawrenceakka  pytest-pep8 is handy.
My argument is that, If the CI tests are going to include pep8 requirements then they should run by default in the local test suite to avoid surprises.  pytest-pep8 uses pytest-cache and only runs pep8 against those files that were modified or untested previously.  You can also configure it via pytest.ini to allow certain exceptions and skip certain files.
If my argument is not enough to sway the group, it is ok, but I thought I should bring up the subject.
Best,
Jeff

I tend to agree with @lawrenceakka then, that the pre-commit hook is probably the better option, from my point of view, to keep the unittest suite fast. (There are already a few tests that takes annoyingly long ;))

The build is no longer failing ... The pre-commit implemented and this discussion hasn't seen any activity in a while. I'll close this. Feel free to re-open if it turns out to still be relevant.

This has been here for some time...
Any reason why it's not closed?

@ghcs27 looks like I intended to close it, but forgot


toJson method in SignedTransaction seems to have problems.

In case setting prettyPrint to true, "ergoTree"  parameter of boxes in the transaction has a problem like the below example:
{       "ergoTree": "ErgoTree(0,WrappedArray(),Right(ConstantNode(SigmaProp(ProveDlog(ECPoint(4a186c,125e7c,...))),SSigmaProp)),80,[B@73d60e76)",     }

@mehranagh20 the ErgoTree here is printed using toString method. So it is not something that can be parsed back. Setting prettyPrint = false, will output Base16 string for "ergoTree", but the json will not be formatted.
The solution is to add formatJson option.

@aslesarenko Right, setting prettyPrint to false solves the problem; afterward, I used Gson with pretty printing to prettify it.
Maybe the same can be done in the toJson method.


c_macos_dbg.bins/dbg/h2_census_nosec_test shutdown_finishes_calls

https://grpc-testing.appspot.com/job/gRPC_pull_requests_macos/1260/testReport/junit/(root)/c_macos_dbg/bins_dbg_h2_census_nosec_test_shutdown_finishes_calls/

Hasn't happened in a while, closing


Call request end() in generators to initiate requests

Thanks for the demo. In order to get the tests to actually fire requests, I had to make sure that the request calls inside the generators ended with an end() call.

Thanks a lot - it was quite some time since I wrote this code. I learned a lot about supertest since then.
Thanks for correcting my old mistakes

Btw, I went through and updated the code to the latest version of koa and co (and friends, like supertest). This causes some more ... challenges.
I have blogged about that here should you be interested to read more.
Again - thanks for the PR. I'd never updated this otherwise :)


Add image alt texts

[x] Arrow corner logo (should be "home")
[ ] All cover images on browse/search pages (should be link destination)
[ ] All page images on browse/search pages (should be link destination)
[ ] "Has annotation" badge
[ ] "Not in collection" placeholder image
[ ] License image on library pages (get text from URI/json for the license)
[ ] Show/hide filters button

@rlskoeser For the cover/page images, the note says "should be link destination" as in the url or something more descriptive?

@bwhicks documenting what we just discussed: should be a description of where the link will take you, e.g. "view bibliographic details" or "view TITLE details" or something like that.

This is available for someone who is not me to take a look at. There should be alt text on any image I could lay my hands on.
The one exception was the "Not available" image on the Citation list view. It uses background image trickery to produce the desired effect, so I made the <span> tab navigable with an aria-label to say what it means.

Looks good to me. I'm going to tweak the wording in a few cases to make it a bit more consistent, and adding one more link title that I noticed, but calling this good.


Passing value with Close not working

Hi,
I am trying to pass a value from child window after it is closed. Here is what I have done:
// in child window.
Close("test");

// parent window.
string result = await ChildWindowManager.ShowChildWindowAsync<string>(
     m_mainWindow,
     childWindow);
return result != null;

But the result is always null in parent's code. What am I missing here?
Thanks.
Versions:

@realivanjx How is your ChildWindowManager.ShowChildWindowAsync implemented?

@punker76 I do not implement that function. I just called it. It is already there. Maybe i am using it wrong?

@realivanjx Sorry, my fault. Can you provide this sample?

@punker76 Sorry, I think now it is working. I was testing with the code i attached before but the result is always null. Sorry for interrupting.


Release 0.0.4

Checklist

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

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

@conda-forge-admin, please rerender

Seems like this did what I want
$ wget -qO - https://dev.azure.com/conda-forge/84710dde-1620-425b-80d0-4cf5baca359d/_apis/build/builds/635301/logs/7 | grep py.typed
2023-01-02T16:41:57.9882198Z   copying openff/models/py.typed -> build/lib/openff/models
2023-01-02T16:41:58.0066578Z   copying build/lib/openff/models/py.typed -> build/bdist.linux-x86_64/wheel/openff/models
2023-01-02T16:41:58.0276676Z   adding 'openff/models/py.typed'


Miss 'description' section in 'extra' section (composer.json)

Description
Miss 'description' section in 'extra' section (composer.json)
https://docs.shopware.com/en/shopware-platform-dev-en/how-to/indepth-guide-bundle/setup
Possible Solution
Add in example composer.json:
"extra": {         "shopware-plugin-class": "Swag\\BundleExample\\BundleExample",         "copyright": "(c) by shopware AG",         "description": {             "de-DE": "Beispiel für Shopware",             "en-GB": "Example description for Shopware"         }         "label": {             "de-DE": "Beispiel für Shopware",             "en-GB": "Example for Shopware"         }     }
Additional context

sounds like a good issue for a PR to the docs :blush:

I have created a PR for the new docs

I have created a PR for the new docs


[BUG] Crashes when you try to generate a sandwich.

Is there an existing issue for this?

[X] I have searched the existing issues

Current Behavior
Crashes when you try to generate a sandwich and creates a blank file if you tell it to create one.
Expected Behavior
I would've expected it to work.
Steps To Reproduce

Run the file.
Try to generate a sandwich in any way.

Environment
- OS: Windows 10 21H2
- Python: 3.9.6
- pip3: 21.1.3

Anything else?
No response
Code of Conduct

[X] I agree to follow this project's Code of Conduct

Sorta fixed

im gonna try re merging diets soon

output to file works but generating in cmd doesnt

Any updates?


⚠ Samsung has degraded performance

In bd5ad18, Samsung (https://samsung.com) experienced degraded performance:

HTTP code: 200
Response time: 2755 ms

Resolved: Samsung performance has improved in 74fead1.


Feature request: Sub list and sub headers

Hello,
Our company is using your action and it's great! But would it be possible to add more options to the dod.yaml?
We would love to be able to make a list like this:
Header

check 1
checkl 2

sub check of 2
sub check of 2

Another header

check 3
check 4

Thank you for your time

The sub-list part should be easy. I need to take a look for the multiple header part. Feel free to submit any pull requests in the meanwhile. :+1:

I am currently looking into sub-lists. Unfortunately a YAML with the following syntax is not valid, so I will have to see if there's a way to easily implement this:
dod:
  - 'Action manually tested and link to successful run provided'
  - 'Python best practices followed'
    - 'Documentation updated'

:point_up: The last (indented) point is not valid.

OK, so the current master contains the possibility to add sub-lists by adding the appropriate number of "➡" characters, as shown below:
dod:
  - 'Checklist item 1'
  - '➡Checklist item 2'
  - '➡➡Checklist item 3'
  - 'Checklist item 4'

The end result, will look like this:

@platisd @Thijs-van-Drongelen is on holiday, so i'll respond for him.
Thank you for implementing the feature! Will update our actions accordingly.
Would it also be possible to have optional checkboxes? Do all checkboxes found get checked? If not i could simply add them to the message myself.
It would be neat to have them all in one dod.yml though.

@RFreij the following now is satisfied as of #43:

Would it also be possible to have optional checkboxes? Do all checkboxes found get checked? If not i could simply add them to the message myself.

Should this issue be closed?


New version: Meltytech.Shotcut version 23.09.29

[ ] Have you signed the Contributor License Agreement?
[ ] Have you checked that there aren't other open pull requests for the same manifest update/change?
[ ] This PR only modifies one (1) manifest
[ ] Have you validated your manifest locally with winget validate --manifest <path>?
[ ] Have you tested your manifest locally with winget install --manifest <path>?
[ ] Does your manifest conform to the 1.5 schema?

Note: <path> is the name of the directory containing the manifest you're submitting.

Microsoft Reviewers: Open in CodeFlow

Automatic Validation ended with:

Exception during executable launch operation System.InvalidOperationException: No process is associated with this object.

This is likely an insignificant error.

@wingetbot waivers Add Validation-Executable-Error


Add options for disabling link and DNS prefetching

See What about folks who pay-per-byte for network bandwidth? and Privacy implications in the link prefetching FAQ.


fix(protocol-kit): Fix memoization issue across different chains in the predict Safe address util

What it solves
Resolves #598 & #634
Added the Sepolia chain to the protocol-kit tests.
How this PR fixes it
Added the chainId to the memoization cache to prevent issues across different chains.

Pull Request Test Coverage Report for Build<PHONE_NUMBER>

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage increased (+23.0%) to 100.0%

Totals

Change from base Build<PHONE_NUMBER>:
23.0%

Covered Lines:
25

Relevant Lines:
25

💛  - Coveralls


Creating Custom FormControl Component

FormControl
Props:

onChange: func
value?: string
componentClass?: string
placeholder?: string
name?: string
required?: string
rows?: 4
type?: 'text' | 'email | 'url'

Variations:

FormControl
FormControl.static
FormControl.Feedback

Form control for chapter:
Need to alter the props to account for chapter need here is the link of the chakira component
https://github.com/chakra-ui/chakra-ui/tree/main/packages/form-control

Which prop is being used in the chapter that we are not passing in the component library?
Since chapter views are limited, it might be easier to create the components with learn specifications and use those props to control the component. does that make senes?

Instead of checking the chaikra library and comparing it with the current component, I am better off checking chapter itself for prop it's using.
for example, in this file https://github.com/freeCodeCamp/chapter/blob/main/client/src/components/Form/Fields.tsx
we are using key and isRequired, so I note these down and check if these 2 props are different from the props we are using.
depend on how different they are, I may do from the follow:

Add new value to existing prop.
Add new prop to the component.

Here is what I propose we do. We could continue building the components with the learn spec and ship them. For the second sprint, we collect the Chapter requirements and update the components accordingly.


/usr/lib/tmpfiles.d/docker.conf is missing the directory path

On my systems the file /usr/lib/tmpfiles.d/docker.conf contains:
d  0755 root root -

Looking at the template, it seems that <%= @run_dir %> isn't being substituted correctly.
And indeed, it looks like there is no variable @run_dir set.
This generates system log entries like:
[/usr/lib/tmpfiles.d/docker.conf:1] Path '0755' not absolute.

Fixed in 1.0.29


dumper stopped working after upgrading to Rails 6.1

We recently checked on our dumper.io information and realized that few of the apps were not backed up. It seems like the back up stopped after we raise the rails version to 6.1. It would be great if the team can take a look at it.

@kenn It would be great if you can take a look into this 🙇


irl model missing in configured path

pretraining create_dataset.sh script points to a model location that does not exist, yielding
raise FileNotFoundError(f"file {url_or_filename} not found")
FileNotFoundError: file ../models/irl_model/irl-model-sgd-08-16-2022.tar.gz not found
Directory models in the root dir does not exist.

我也遇到了请问解决了吗

预训练 create_dataset.sh 脚本指向不存在的模型位置，产生
引发 FileNotFoundError(f"文件 {url_or_filename} 未找到") FileNotFoundError: 文件**../models/irl_model/irl-model-sgd-08-16-2022.tar.gz**未找到
根目录中的目录模型不存在。

我也遇到了这个问题，请问解决了吗

Hi @DiazBejaranoD and @chen989898, thank you for your interest in this project and for raising this issue.
Unfortunately, we're unable to release the original model at this time. However, I've updated the repo in #6, providing instructions and scripts for training the IRL model using the provided dataset here. Let us know if you have any further questions!


v4. Animations do not work properly (they work until the first refresh)

Describe the bug
As in the description. Animations work - but don't work in fast refresh. When I refresh, they stop working. Latest version v4.0.13

Related: https://github.com/software-mansion/react-native-reanimated/issues/5296 https://github.com/software-mansion/react-native-reanimated/pull/5268
I'm currently trying to gauge how much effort a hack fix will be vs waiting for the fix.

Actually this can occur though normal usage as well. I'll publish a fix soon

We are closing all pre-v4.1 issues now that v4.1 is released. If the problem is still happening with the latest v4.1, please open a new issue and reference this one in the description.


Setup centralisation of branch protection rules for all repos

Problem

All repositories are currently managing their own branch protection rules. Based on needs such as pushing to GH pages or allowing force-push to one's one branches but not master can cause these rules to diverge from each other as well as from the ideal configuration.
Description

These rules should be defined in this repository and synced to all downstream repositories so that we have a consistent set of rules everywhere.
Additional context

This sort of work has been done earlier. Refer to this implementation by CC for example.
Implementation

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

We should close this as a duplicate of https://github.com/WordPress/openverse-infrastructure/issues/173. The monorepo will eventually merge everything but for now it excludes the infra and catalog repos so this feature will still be useful.


A problem with PushScaler

Report
The scaler's close method has already been called once by ScalersCache. PushScaler will call the scaler's close method again.
Expected Behavior
The scaler's close method is expected to be called once.
Actual Behavior
The scaler's close method is actually called twice.
Steps to Reproduce the Problem

Delete the PushScaler resource.

Logs from KEDA operator
No response
KEDA Version
2.8.0
Kubernetes Version
1.24
Platform
Other
Scaler Details
No response
Anything else?
No response

Thanks for reporting! Are you willing to propose a fix for this?

This is already fixed


Typo "Azure Blob storage"→"Azure Blob Storage"

https://docs.microsoft.com/en-us/windows/uwp/gaming/cloud-for-games

@hyoshioka0128 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@hyoshioka0128 : Thanks for your contribution! The author(s) have been notified to review your proposed change.

The update matches the current Microsoft-internal cloud style guide; thanks @hyoshioka0128.

The update matches the current Microsoft-internal cloud style guide; thanks @hyoshioka0128.


dx12 is not supported on your system

Hello,
I am trying to run CarlaUE4.exe on my GPU but I am encountering an error message: dx12 is not supported on your system try running without the dx12 or d3d12 command line argument.
I tried to solve the problem using the solution described here: https://www.reddit.com/r/TheCycleFrontier/comments/vmpdzx/comment/ie3k54s/?utm_source=share&utm_medium=web3x&utm_name=web3xcss&utm_term=1&utm_content=share_button
Unfortunately, it did not work for me. I could not find the string m_enableDX12=True to modify it or delete it. Also, my NVIDIA driver is up-to-date.
CARLA version: 0.9.15
Platform/OS: Windows 19 Datacenter
Any help would be appreciated.

Hi, i have single GPU so my command is as follows: CarlaUE4.exe -carla-rpc-port=3000 -carla-primary-host=<IP_ADDRESS> -ini:[/Script/Engine.RendererSettings]:r.GraphicsAdapter=0
if i try to change the GraphicsAdapter number to 1 i am getting the error which you have posted. so make sure how may graphic cards do you have in your system and proceed as follows.
open task manager there you can see the GPU and change the number accordingly.

Thank you for responding. Unfortunately, the problem still persists


Improve Record formatting

Addresses #6 and #8. @andrewdavey
Uses the same logic Immutable does in toString to display record names.

Thanks for this! I've released it to npm in v0.0.5.

Glad to help!


How can you turn off ssl verification?

I need to make parallel requests to a site that cannot have SSL certs as the DNS endpoint changes periodically.
I found I can use the blocking call Clue\React\Block\awaitAll() to achieve this within our synchronous framework.
It works with the React\Http\Browser::post() function but I cannot turn off SSL verification in the post function.
React\HttpClient\Client allows you to define a Connector which lets you set the TLS context options verify_peer and verify_peer_name to false. I can make the request to the endpoint successfully with this method but I cannot use the client and connector in the blocking call as they return a React\HttpClient\Request object not a promise so I can't use the awaitAll() function.
Can the TLS functionality be added to the Browser::post() function as an option or is there a way to use the Clue awaitAll() function with the HtpClient function?

Here is a working example of a simple HttpClient request that successfully returns a result with HTTP 200:
$dns = 'https://ec2-*-*-*-*.eu-west-1.compute.amazonaws.com:8000';
$post_data = 'test=12345';
$loop = React\EventLoop\Factory::create();
$connector = new \React\Socket\Connector($loop, array(
    'tls' => array(
        'verify_peer' => false,
        'verify_peer_name' => false
    )
));
$client = new React\HttpClient\Client($loop, $connector);

$request = $client->request(
    'POST',
    $dns,
    [
        'Content-Length' => strlen($post_data),
        'Content-Type' => 'text/plain'
    ]
);
$request->end($post_data);

$request->on('response', function ($response) {
    $response->on('data', function ($chunk) {
        echo $chunk;
    });
});
$loop->run();

When I try the same using Http\Browser it doesn't work and I get a HTTP 500 error:
$dns = 'https://ec2-*-*-*-*.eu-west-1.compute.amazonaws.com:8000';
$loop = React\EventLoop\Factory::create();
$connector = new \React\Socket\Connector($loop, array(
    'tls' => array(
        'verify_peer' => false,
        'verify_peer_name' => false
    )
));
$client = new React\Http\Browser($loop, $connector);
$post_data = 'test=12345';

$client->post(
    $dns,
    [
        'Content-Length' => strlen($post_data),
        'Content-Type' => 'text/plain'
    ],
    json_encode($data)
)
    ->then(
        function (Psr\Http\Message\ResponseInterface $response) {
            var_dump((string)$response->getBody());
        }, 'printf');

$loop->run();

Can anyone explain why they get different results?

@crwh05 Thanks for posting! It looks like you've got this right, you can configure the Connector to change TLS settings which will then be used by the Browser.
The Client is internal only, so I'll focus on the second example. I'm not sure if your second example is complete, but it looks like it's referencing an unknown $data variable (vs $post_data)? Additionally, the Content-Length header can be omitted as it will be set automatically.
The "HTTP 500 error" you're seeing means that TLS/HTTPS does work as expected, but the server returned an error for the request. Might be the above variable, but hard to tell without being able to access the same server.
The below example works just fine:
<?php

require __DIR__ . '/../vendor/autoload.php';

$loop = React\EventLoop\Factory::create();
$connector = new React\Socket\Connector($loop, [
    'tls' => [
        'verify_peer' => false
    ]
]);
$client = new React\Http\Browser($loop, $connector);

$data = [
    'name' => 'Alice'
];

$client->request(
    'GET', // change to POST, but badssl.com only accepts GET
    'https://self-signed.badssl.com/',
    [
        'Content-Type' => 'application/json'
    ],
    json_encode($data)
)->then(function (Psr\Http\Message\ResponseInterface $response) {
    var_dump($response->getHeaders(), (string)$response->getBody());
}, 'printf');

$loop->run();

I hope this helps :+1:

Hi @clue,
Thanks for your detailed response, especially for clarifying TLS/HTTPS does work as expected as I received an HTTP 500. That allowed me to focus on other points.
Regarding the use of $post and not $post_data there was a simple mistake while copying the sample code where I forgot to update the name of the post data being passed. (I had to change a few things as some info was sensitive)
That was not the issue but what was the issue was that while testing various endpoints (ones with SSL certs and ones without) I forgot to remove the json_encode() from the data passed in the post request when I was only sending text/plain instead of application/json.
The server was receiving the body as "test=12345" instead of test=12345
This was causing the issue.

@crwh05 Thanks for the feedback!
Yeah, JSON-encoding a string is a nasty oversight, happy to hear my response has helped and you've got this working now! 💪


Indicate to Global Caches how long a resource should be cached for

As discussed at ET-W2AT meeting, 16-Oct-2023.
WIS2 Manual (Tech Regs) states:
"""
4.5.4 Based on received notifications, a Global Cache shall download core data from WIS nodes or other Global Caches and store for a duration compatible with the real-time or near real-time schedule of the data and not less than 24-hours.
"""
The default period for caching resources is 24-hours. But some (near) real time might need to be kept for longer based on the "real-time or near real-time schedule". Its a WMO Programme decision about how long data should be cached for, agreed with the WIS2 operators - in a process that's yet to be defined.
A mechanism is required to inform Global Caches to cache content for a duration other than 24-hours - usually longer, but perhaps shorter too.
It seems likely that this would be a per-object policy, i.e., each object that is cached should indicate the length of time it should be cached. The simplest way to do this would be to add a cache-duration attribute to the notification message.
A Global Cache may ignore the cache-duration statement, for example, if the duration was set to an excessively long period that compromised the ability of the Global Cache to perform. In "tech regs speak": the Global Cache should respect the cache-duration value.

note: current guide differs from text above content. https://wmo-im.github.io/wis2-guide/guide/wis2-guide-DRAFT.html#_2_4_3_global_cache


The optimization effects vary significantly between different models

Here is my deployenv
PyTorch version: 2.4.0+cu121
CMake version: Could not collect
Libc version: glibc-2.38
Python version: 3.11.6
CUDA_MODULE_LOADING set to: LAZY
GPU: NVIDIA L20
Nvidia driver version: 535.161.07
cuDNN version: Could not collect
Here is my testing data
Input data: Musique 50 rounds
Model: Llama-3-8B, Mistral-7B
And this is my testing script:
import time
import lmcache_vllm
import torch
from lmcache_vllm.blend_adapter import (append_separator,
                                        combine_input_prompt_chunks)
from lmcache_vllm.vllm import LLM, SamplingParams
import json
import numpy as np
from transformers import AutoTokenizer
# cache blend utils and dataset
from utils import load_dataset, normalize_question, build_qa_prompt, compute_f1
from pathlib import Path
eval_dataset = load_dataset("inputs/musique_s.json")
model_path = "xxxxx"
llm = LLM(model=model_path , gpu_memory_utilization=0.85)
tokenizer = AutoTokenizer.from_pretrained(model_path)
llm.set_tokenizer(tokenizer)

prefix_prompt = "You will be asked a question after reading several passages. Please directly answer the question based on the given passages. Do NOT repeat the question. The answer should be within 5 words..\nPassages:\n"
query_prompt = "\n\nAnswer the question directly based on the given passages. Do NOT repeat the question. The answer should be within 5 words. \nQuestion:"

ttft_blend = []
ttft_full = []
f1_blend = []
f1_full = []
# change round number here
k = 50
def precompute_kv(text_chunk, llm):
    sampling_params_prefix = SamplingParams(temperature=0.0,
                                            max_tokens=1)
    text_chunk = append_separator(text_chunk)
    llm.generate([text_chunk], sampling_params_prefix)

i = 0
for ex in eval_dataset:
    if i == k:
        break
    answers = ex["answers"]
    doc_prompts, q_prompt = build_qa_prompt(ex, query_prompt)

    print("-------------- Pre-computing KV cache for the chunks -------------------")
    # Concatenate old KVs
    for chunk in doc_prompts:
        precompute_kv(chunk, llm)

    print("Running the real query here!")
    sampling_params = SamplingParams(temperature=0, max_tokens=128)
    user_prompt = [prefix_prompt]
    user_prompt.extend(doc_prompts)
    user_prompt.append(q_prompt)
    user_prompt = combine_input_prompt_chunks(user_prompt)
    output = llm.generate(user_prompt, sampling_params)
    ttft = output[0].metrics.first_token_time-output[0].metrics.first_scheduled_time
    res = output[0].outputs[0].text
    print(f"Cached generation: {res}")
    print(f"TTFT with cache: {ttft}")
    ttft_blend.append(ttft)
    f1 = max([compute_f1(res, answer, tokenizer) for answer in answers])
    f1_blend.append(f1)
    i += 1

print("---------------Result Summary---------------------")
print(f"k = {k}")
print(f"TTFT with cache: {np.mean(ttft_blend)}")
print(f"F1 with cache: {np.mean(f1_blend)}")

# Graceful exit
lmcache_vllm.close_lmcache_engine()

And this is my LMCACHE yaml:
chunk_size: 256
local_device: "cpu"

# Enables KV blending
enable_blending: True

# Whether retrieve() is pipelined or not
pipelined_backend: False

Results and questions

Models
Input tokens number
LMCache TTFT latency(s)
vLLM Baseline TTFT latency(s)

llama-3-8B-Instruct
musique 50 rounds
0.92
0.84

Mistral-7B-Instruct-v0.2
musique 50 rounds
0.3
0.97

I tested the performance of Mistral-7B and Llama-3-8B with enable_blending=True, but only the former model successfully reproduced the results from the CacheBlend paper like table I listed above. What could be the reason for this?

@jokmingwong I believe the possible reason is that the encoding of the special token ("#") might differ between models. You could modify the code at this link:
https://github.com/LMCache/lmcache-vllm/blob/f5b015bfa2f5dd1aa27c4bb0bd28085e3407ca11/lmcache_vllm/blend_adapter.py#L33

I believe the possible reason is that the encoding of the special token (" # #<s>") might differ between models. You could modify the code at this link:
[https://github.com/LMCache/lmcache-vllm/blob/f5b015bfa2f5dd1aa27c4bb0bd28085e3407ca11/lmcache_vllm/blend_adapter.py#L33]

I believe the possible reason is that the encoding of the special token (" # #") might differ between models. You could modify the code at this link

The issue has been resolved, thank you very much!
I changed code like below:
TEMP_SPT = [422, 422] to TEMP_SPT = [674, 674]
separator = " # # " to " # #<|begin_of_text|>" (no space at last) in function combine_input_prompt_chunks
After changing the encoding format, the results align with those presented in the paper.

close the issue

I still have a question when using lmcache with other models. How should this be modified to support cache blending for models without bos_token, like Qwen? @xhx1022

The issue has been resolved, thanks very much! I changed code like below: TEMP_SPT = [422, 422] to TEMP_SPT = [674, 674] separator = " # #<s> " to " # #<|begin_of_text|>" (no space at last) in function combine_input_prompt_chunks
After changing the encoding format, the results align with those presented in the paper.
Models	Input tokens number	LMCache TTFT latency(s)	vLLM Baseline TTFT latency(s)
llama-3-8B-Instruct	musique 50 rounds	0.28	0.84


Electron Builder and Travis Failures

Right now, there are quite a few issues with our build process, CI and Electron Builder:
Fetching Web UI
Currently, the latest Web UI version is not pinned to the gateway. On normal circumstances, it should not be a problem because it's still pinned to the cluster. Although, the gateway is having issues connecting to cluster.
This makes build fails due to timeouts.
Solutions:

Make webui.ipfs.io the latest released version and dev.webui.ipfs.io the latest commit. That way, both domains shall be pinned to gateway.
Add a git submodule to IPFS Desktop with IPFS Web UI and build IPFS Web UI on the fly.

More burden when updating IPFS Web UI.

Electron Builder failing on Linux releases...
Electron builder has a bug on the latest version that makes releases fail on Travis (don't know if it happens on other CIs). Issue opened on their repo 20 days ago. No replies yet, no activity on the repo. See electron-builder#4134.
Downgrading also implicates downgrading electron which implicates changes on the code.
There's also the issue #1044, which I believe is caused by the beta binaries been built manually on a virtual machine I created because of this issue.
What to do?
Other points...

Travis is slow.
Windows builds can be built on either Linux or macOS. Perhaps we can remove AppVeyor/Win Executor.
Circle CI macOS is quite expensive, worth it? https://circleci.com/pricing/#build-os-x

Performance plan from the 'New plans' is required for having Windows & macOS: https://circleci.com/pricing/usage/

See an example that builds for Windows, macOS and Linux:

https://dev.to/kontrollanten/super-fast-electron-builds-with-circleci--5ghn
https://github.com/protonmail-desktop/application/blob/7289770d44f8f8acdda69f878643d354928e406e/.circleci/config.yml

Working on https://github.com/ipfs-shipyard/ipfs-desktop/tree/chore/circleci

Also, just found out we can build Windows binaries on Linux through Wine!

A few updates on this issue:

I've created a PR to test GitHub Actions.
I've found another error in Travis logs which may be the actual cause of the error: there was a breaking change on Electron Builder which was not published as a major release. Snap packages now deploy to the snap store by default and since we didn't have the credentials to the snap store, build failed.

Note: I believe this is why it failed, but I'm not sure.

If 2 is true, we can keep using Travis+AppVeyor.
Anyways, I've contacted the AppVeyor support to delete the project: https://ci.appveyor.com/project/wubalubadubdub/ipfs-desktop-difec because it was created by an user called 'wubalubadubdub' which doesn't seem to have any relation to IPFS Shipyard, nor IPFS organisations.
If we decide to keep AppVeyor after that, I'll create a project for IPFS Desktop here.

After running Travis+AppVeyor, I could successfully publish a 0.9.0-beta.3 prerelease which seems to indicate that our build process is fixed.
The problem with Electron Builder was, in fact, something else much easier but was buried deeper in the logs: see #1069.

Will close this for now since the issues on IPFS Desktop side seem to be solved!


Split project into separate files

(will add a more detailed description later)

This is good stuff, thank you @makupi!
Something to consider: while we only cover New Horizons right now, we'll eventually have endpoints for other games. As-is we could add endpoints for the other games to the existing files (furniture.py, fish.py, etc.), while the other option might be to create separate directories for each game (for now, an ACNH folder, and in the future ACNL, etc.).
The other thought I have is moving the static directory back to the root, since it's its own thing separate from the Python app.

@KevinPayravi I can move the existing endpoints to a separate ACNH folder, probably easier to do right now than later and I can try to move the static back but flask was being somewhat weird about that 😅


Update best-practices-serverless-sql-pool.md

it is important to understand the impact of the UTF8 Collation (More clarity and/or technical accuracy may be need to explain this better). I wanted to add a link to provide more context based on this: https://docs.microsoft.com/en-us/sql/relational-databases/collations/collation-and-unicode-support?view=sql-server-ver15#converting but wasn't sure how

@jasonhorner : Thanks for your contribution! The author(s) have been notified to review your proposed change.

@jasonhorner thank you very much for pointing this out and for PR!
Think it is valid for any UTF8 collation, not just the one specified in PR?
It would be good to have that comment in both places -> where you added it and where we explicitly mention perf  benefits from specific collation.
adding @JocaPC for awareness

@jasonhorner i can make proposed changes to your PR, if i have permissions.

@jasonhorner i can make proposed changes to your PR if you like, if i have permissions.

please do, is there something i need to do on my end?

@jasonhorner after giving this another thought and discussing it with the team, this requires more details that are not belonging to the best practices page.

I still think it would be useful to add the link.

Thank you for contributing to the documentation. We'll close the pull request per the author's comment.


Fix #1022: Document CI is Broken

#1022 It is broken in commit https://github.com/Azure/azure-cli/commit/90c7b7de3159e41160c96dbaffd13f94e20c3874 because get_group_priority has changed in _help.py but not in azhelpgen.py

@tjprescott and @derekbekoe to look
Looks good from my side.


Ashok Manghat First Pull Request

First pull request from the repository

Hi  @ashokmanghat, I'm quite elated about your pull request. I wanna evolve this project to addresses various problems faced by first-time contributors. I'd love to learn about your journey in open source community, the problems, pain points you had etc.
Could you explain how you felt when you went through the tutorial, made a pull request and learned that I merged it?
We’ve recently added social share  to our web app. Could you please go to https://roshanjossey.github.io/first-contributions/#social-share and share your first contribution to open source?
Also, check out projects with easy issues while you’re there.


Homework w4

Got a little bit stuck on this assignment, but hopefully after tonight it will get clear.

I updated it with a 3th commit. Could you check it out please. :)


Support for other Cloudflare-like services

Cloudflare is not the only service offering similar technical features (other notable encountered often is Incapsula).
This is something that would prove useful to a lot of testers. I'm currently evaluating if I can programmatically determine Incapsula's ranges effectively (since they have an AS it should be possible). However, I'm not aware of a similar database as crimeflare. Yet, it could still be useful to incorporate with thanks to the DNSDumpser API and the common subdomain checks.
Cheers,
~H

This is definitely something I have been thinking about. obviously with CloudFail it checks to see if the IP is part of the cloudflare network and if not then it fails, there should be a way to do it with similar companies as well. Now I dont know whether to update cloudfail to support general domain dns enumeration / bruteforce or have a separate tool for each service...
Cheers for the research anyhow, this will definitely be thought about.

I was thinking we should start with CloudFront and Fastly.

Isn't CloudFront integrated into AWS, so you'd end up with an AWS address anyway?

Man I really let myself go on some F/OSS contributions. I opened this back in 2017?

Isn't CloudFront integrated into AWS, so you'd end up with an AWS address anyway?

Yes, but you could potentially end up with the Origin IP of the direct EC2 instance or backing service. This would allow evasion of IDS/IPS functionality when routing through the expected path as some tenants do not configure their VPC security properly.


Does the wait_time argument need a wait_until to work correctly?

In the following parser I want the spider to SeleniumRequest all links on a page according to the rules I have specified in the Srapy LinkExtractor 'le'. It seems to me that no matter what wait_time I pass it does that same thing. Am I doing something wrong? Does the wait_time argument need a wait_until to work correctly? Or something else?
def parse(self, response):
        for link in self.le.extract_links(response):
            yield SeleniumRequest(url=link.url,
                                  callback=self.parse,
                                  wait_time=40
                                    )

Not sure if this is still relevant, but I encountered the same issue.
From looking through the code, it looks like wait_time defined a timeout for the wait_until event.
Based on the code below:
    def process_request(self, request, spider):
        """Process a request using the selenium driver if applicable"""
        [...]

        if request.wait_until:
            WebDriverWait(self.driver, request.wait_time).until(request.wait_until)

I don't see another reference to wait_time in the code.
It looks like that wait_time is indeed ignored when no wait_until is specified. Otherwise the WebDriver will wait for the specified event, but only for a maximum of wait_time seconds.


AppService websocket vs ip limits

How does the websocket limits in AppServices relate to the IP limits? Eg, on a S1 there are unlimited websockets possible, but only 1920 (outbound) IP's. Is the actual websocket limit for a S1 1920?

Document Details
⚠ Do not edit this section. It is required for docs.microsoft.com ➟ GitHub issue linking.

ID: 36f49a06-90b1-cbe1-3853-2c38277b79f8
Version Independent ID: 02ff6f6c-3ef6-b48f-060d-b290419e0aba
Content: Azure subscription limits and quotas - Azure Resource Manager
Content Source: articles/azure-resource-manager/management/azure-subscription-service-limits.md
Service: azure-resource-manager
Sub-service: management
GitHub Login: @davidsmatlak
Microsoft Alias: v-dasmat

#assign:davidsmatlak

@tomkuijsten thank you for the feedback. I'll research the issue and post an update when more information is available.

Any progress?

Research is in progress.

Requested clarification from the App Service documentation owners about the relationship between the limits for Web sockets and IPs.

#assign:msangapu-msft

#unassign:davidsmatlak

Hi @tomkuijsten can you provide some details on your particular scenario - what are you trying to do here? Generally speaking, websockets and outbound calls/IPs are independent of each other.

I want to use an app service to host websockets for +/- 20k unique clients (unique ip addresses) on a S1. Load tests prove that from 1 IP 20k websockets is possible, but I'm not sure if it works from 20k unique ipaddresses.

Okay, the connection limit is for outbound connections from the app, not client IPs. I believe your scenario with 20k users using web sockets should work. Let me confirm this and get back to you.

Did you get the confirmation?

Hi @tomkuijsten  - the web sockets limit applies to the inbound connections to the application established using web sockets.  The other number (in this case 1920) applies to the outbound network traffic generated by an app running on a worker (in this case an S1 instance).
Hope that helps! If you have additional questions based on your app, I'd recommend you open a support ticket so someone can take a closer look at your situation.

Thanks for chasing the confirmation! Would be a good idea to clarify this in the docs. I'll close the issue as you answered my initial question.


Add Apache 2.0 LICENSE file

Signed-off-by: Ry Jones<EMAIL_ADDRESS>

The goal is to get projects using the same license file.

What is the plan for Rights-Managed assets?
https://www.w3.org/TR/odrl-model/


🐛 BUG: Pages middleware context.data not persisted if overwritten

Which Cloudflare product(s) does this pertain to?
Pages
What version of Wrangler are you using?
2.11.1
What operating system are you using?
Windows 10
Describe the Bug
Originally reported on the Community: https://community.cloudflare.com/t/what-is-context-data-in-pages-functions/476559?u=cherryjimbo
If I have a project structure like this:
functions
   _middleware.js
  auth.js
public
  index.html

Where my _middleware.js looks like:
export async function onRequest(context){
	context.data = {
		authed: true,
		username: 'jimbo'
	}
	context.data.test = true;
	console.log('set data')
	return context.next();
}

And my auth.js looks like this:
export async function onRequest(context) {
	console.log('getInfo');
	console.log(context.data);

	return new Response(`getInfo: ${JSON.stringify(context.data)}`);
}

I ran npx wrangler@latest pages dev public, and npx wrangler@latest pages publish public to reproduce this.
When I hit /auth, I see getInfo: {}. Looking at tail logs (also reproducible in dev), I see it was fired:
GET https://601914ff.middleware-test.pages.dev/auth - Ok @ 25/02/2023, 00:06:15
  (log) set data
  (log) getInfo
  (log) {}

But nothing about data was persisted.

This seems to happen when you override context.data via context.data = {...}. If you only interact with context.data by doing context.data.<key> = {...}, things work as expected. You can reproduce this by commenting out the following in my example _middleware:
context.data = {
	authed: true,
	username: 'jimbo'
}

so you're only left with context.data.test = true;.
With this change, you'll now see getInfo: {"test":true} on /auth.

Another user ran into this today in the Discord.
I can also confirm this is still a bug in wrangler 3.1.0.

Created a PR at https://github.com/cloudflare/workers-sdk/pull/3431 to fix this. It's pretty gnarly, but due to how context is passed in with data as a reference, I don't really see any other way to catch this outside of a Proxy.


How to modify db.json from server side?

For example, when I do
GET /posts/1

I would like its views +1.
{ "id": 1, "title": "json-server", "views": "1" } => { "id": 1, "title": "json-server", "views": "2" }

Is it possible with json-server?
I tried lowdb commands, db.json was changed accordingly but this change was not reflected in api.

you would do a POST /posts/1 , { "id": 1, "title": "json-server", "views": "2" } If I understand you correctly

Try to pass the lowdb instance to the jsonServer.router. Then both should share the same lowdb instance and the change you make in using the lowdb API will also be reflected in the json server.
const low = require('lowdb');
const FileSync = require('lowdb/adapters/FileSync');
const db = low(new FileSync('./db.json'));

// ...
const router = jsonServer.router(db); // here instead of a file you pass the lowdb instance

Note: HTTP GET requests by convention should not change any resource on server.


Inconsistent quotation marks in elasticsearch.yml

Module version: 0.13.2
Puppet version: 3.8.7
OS and version: CentOS 7.2

Bug description
Hello,
This is probably a nitpicky issue, but here it goes: with the current version of the module the generated elasticsearch.yml uses quotation marks around numbers inconsistently. I think it's due to the to_yaml call in the template, and how Puppet interprets the types of its own variables. We previously used version 0.10.1 of the module, where this was not an issue.
Here's an example:
class{ 'elasticsearch':
    [..]
    config           => {
      'cluster' => {
        'routing.allocation' => {
          'node_concurrent_recoveries'        => 20,
          'node_initial_primaries_recoveries' => floor(30),
          'awareness.attributes'              => 'landb_parent'
        }
    }
}

This will result in the following entries in the yaml file:
cluster.routing.allocation.awareness.attributes: landb_parent
cluster.routing.allocation.node_concurrent_recoveries: "20"
cluster.routing.allocation.node_initial_primaries_recoveries: 30

As you can see the string landb_parent has not quotes around it, while the value 20 has. Number 30 has been put through Puppet's floor function, and it has no quotes around.
In our config we have many more numerical values, some are calculated using arithmetic operators, or put through numerical functions like floor. These values have no quotes around them. However the "static" numerical values (like the 20 in the example) get quoted in the config file.
It does not look pretty. :) Apart from that, does ElasticSearch makes a difference between quoted and unquoted values when parsing the settings file?
Thanks,
Akos

As far as I understand, Elasticsearch should parse either form of those numerics the same way. You're correct in assuming it's the way puppet handles hashes internally that is causing the inconsistency here, I've had to work around it a few times to ensure numbers are represented correctly in a few places (it may have something to do with pson, not sure).
For example, when passing a Puppet hash to create a new index template, I have to explicitly call a custom function called deep_to_i in order to ensure all numbers are actually numbers before comparing what puppet wants the template to be to what the Elasticsearch API reports. deep_to_i is here. It's definitely not ideal, but it solves the problem.
In this case I agree that it's probably more cosmetic than a bug, but it good to note it here at least. There's more pressing items on the agenda (like compatability with 5.x) but I'd wholeheartedly accept PRs if someone wanted to tackle it.
In addition to some tests that reproduce the quoted numerics, the solution is pretty straightforward and probably just needs to be a call to deep_to_i in the template (nearby the to_yaml call).

Fixed in #715


Add contribution guidance to the readme

This may seem pretty obvious to most but at first I wasn't I wasn't sure if proposals were being accepted via  GitHub Issues or pull requests.
I think the readme needs a section on how to submit a proposal with a brief explanation on the acceptance/rejection process.

Good call. I may have an even better solution shortly. Going to talk about it on the board meeting tomorrow.

@daveajones Great, I'm glad it's being brought up.  It might be worth having a PR or issue template for proposals so a common submission format can be followed.


Azure Powershell - Set workingFolder

Similar to the Powershell VSO Build Agent, can we set the workingFolder when instantiating Azure Powershell?
Use Case:
I am trying to download assets from Azure Blob storage to the build machines. From my build logs, the working directory is set to wherever Azure Powershell lives.
2016-01-27T20:16:32.1304033Z Found 5 blob(s)
2016-01-27T20:16:32.1414028Z Downloading to C:\LR\MMS\Services\Mms\TaskAgentProvisioner\Tools\agents\default\tasks\AzurePowerShell\1.0.8\

Workaround:
Use $PSScriptRoot to figure out where my script is and go from there.

currently no.

@ericsciple - let's add this.

I just uploaded the entire task directory up to blob storage accidentally because of this.  $PSScriptRoot is a good work-around, but please add support.  Thanks!

Added it to backlog Feature: 649929

@RoopeshNair What is backlog feature 649929? I presume this has been moved to a private VSTS. If that is the case, how can we (the public) be aware of what's going on with this issue?

Just stumbled upon the same issue, extremely irritating. This should be fixed asap, and if not then there has to be a big fat warning about this behaviour.

Any updates?

Not at this point in time, we haven't been able to get to this.
We do encourage contributions, if you are willing to help.


Automatically format and add license header to generated code

The aim of this issue is to improve automation & to reduce the amount of noise present in the diffs when regenerating the data model code.
A maven plugin can be used to format the generated code. If we can use a consistent format, then it should make diffing generated code changes easier.
The license needs to be manually added by running the license plugin, ideally we would like this to be done automatically.

#458 has applied a change that will automatically add the license header to files when the mvn build is run.

Formatting will be done manually for now, using the ForgeRock style configuration for IntelliJ: https://wikis.forgerock.org/confluence/display/devcom/Java#Java-IDEintegration
The existing code has been reformatted, going forwards we need to format the code using IntelliJ post generation.
The plugins I investigated tend to use Google style which doesn't match with the FR style.


CVE-2024-24791 in v6.42.0

Describe what happened
Our scanning jobs have identified a new CVE "CVE-2024-24791" in the pulumi-std v1.7.2. This is an issue with the Go standard library net/http.
Sample program
N/A
Log output
Scan result
{
      "Target": "home/appian/.pulumi/plugins/resource-aws-v6.42.0/pulumi-resource-aws",
      "Class": "lang-pkgs",
      "Type": "gobinary",
      "Vulnerabilities": [
        {
          "VulnerabilityID": "CVE-2024-24791",
          "PkgName": "stdlib",
          "PkgIdentifier": {
            "PURL"<EMAIL_ADDRESS>            "UID": "f2328c2729d2b74b"
          },
          "InstalledVersion": "1.22.4",
          "FixedVersion": "1.21.12, 1.22.5",
          "Status": "fixed",
          "Layer": {
            "Digest": "sha256:12b42ef700cd619bf6b070c29488e45d2706debd29cc072b6c70cfc476aba9bb",
            "DiffID": "sha256:c01c35830eba6aa5d25006afdecebf6a3ed84701acf2ab573180bd5dc488c3c0"
          },
          "PrimaryURL": "https://avd.aquasec.com/nvd/cve-2024-24791",
          "DataSource": {
            "ID": "govulndb",
            "Name": "The Go Vulnerability Database",
            "URL": "https://pkg.go.dev/vuln/"
          },
          "Description": "The net/http HTTP/1.1 client mishandled the case where a server responds to a request with an \"Expect: 100-continue\" header with a non-informational (200 or higher) status. This mishandling could leave a client connection in an invalid state, where the next request sent on the connection will fail. An attacker sending a request to a net/http/httputil.ReverseProxy proxy can exploit this mishandling to cause a denial of service by sending \"Expect: 100-continue\" requests which elicit a non-informational response from the backend. Each such request leaves the proxy with an invalid connection, and causes one subsequent request using that connection to fail.",
          "Severity": "UNKNOWN",
          "References": [
            "https://go.dev/cl/591255",
            "https://go.dev/issue/67555",
            "https://groups.google.com/g/golang-dev/c/t0rK-qHBqzY/m/6MMoAZkMAgAJ",
            "https://pkg.go.dev/vuln/GO-2024-2963"
          ],
          "PublishedDate": "2024-07-02T22:15:04.833Z",
          "LastModifiedDate": "2024-07-02T22:15:04.833Z"
        }
      ]
    }

Affected Resource(s)
No response
Output of pulumi about
Using pulumi v3.122.0 and pulumi-aws v6.42.0
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).

Thank you for the report! My team is looking into getting this fixed.


Finite HMM api

HMM api.
@davidbenjamin  please review.

@vruano Back to you.  It's a nice design, very clear API.  My main suggestion is to supplement the R testing with a few analytic results.  Also, I wasn't fully comfortable with the performance hit  representing states by objects instead of integer indices, but then I saw your testing code's use of ordinal()  I can't say I love this solution, but I don't know of any better way and I do like the flexibility of using either an Integer or an Enum.

@davidbenjamin you can always use Integer typed hidden-states if that is what you need.

@davidbenjamin  back to you.
I have addressed all the comments in three commits
196acc5 : simple comments
271b82f : HMM enhanced unit testing.
7413b6a : FW tables from 1D to 2D arrays.

Very small comments.  I love the HMM tests.  Feel free to merge when you're done.


Bug of Pow Operator!

Hi
Please Check this.
example/test.ank (input file) : print(5**5)
vm/vm.go file:

case "**":
	if lhsV.Kind() == reflect.Float64 {
		return reflect.ValueOf(math.Pow(toFloat64(lhsV), toFloat64(rhsV))), nil
	}
	print(toFloat64(lhsV))//added by me to test
	print(" ** ")//added by me to test
	print(toFloat64(rhsV))//added by me to test
	print("\n")//added by me to test
	print(math.Pow(toFloat64(lhsV),toFloat64(rhsV)))//added by me to test
	print("\n")//added by me to test
	return reflect.ValueOf(int64(math.Pow(toFloat64(lhsV), toFloat64(rhsV)))), nil

=========
output :

$ ./anko example/test.ank
+5.000000e+000 ** +5.000000e+000
+3.125000e+003
3125

why output of pow is 3125 ?!!!

It is not issue report. Please explain what is problem. PLEASE DO NOT ask me.

5**2 in your interpreter is 3125
but just output = 25
so why output of **(pow) is wrong?

you check bug?

Do you understand what is pow? This behavior is same as your favorite python.

Don't judge what is a bug just by your knowledge, please. And you should more study programming languages.


Adding websocket upgrade support

Taking inspiration from https://github.com/http-party/http-server/pull/637 and attempting to address the changes requested from the PR review
Adding a handler for an "upgrade" request so that the proxy properly manages the connection to the downstream.
Relevant issues
Fixes #142.
Contributor checklist

[ ] Provide tests for the changes (unless documentation-only)
[x] Documented any new features, CLI switches, etc. (if applicable)

[x] Server --help output
[x] README.md
[x] doc/http-server.1 (use the same format as other entries)

[x] The pull request is being made against the master branch

Maintainer checklist

[ ] Assign a version triage tag
[ ] Approve tests if applicable

@thornjad please take a look. This one should finally be merged.


Associated type position impl trait

Metadata

Owner(s)
@oli-obk

Team(s)
lang, types

Goal document
2024h2/ATPIT

Summary
Stable support for impl Trait in the values of associated types (aka "associated type position impl trait" or ATPIT)
Tasks and status

[ ] Implementation (@oli-obk)
[ ] FCP decisions (types )
[ ] Stabilization decision (types, lang )

The remaining blockers for this feature are

make a lang decision on whether methods with the ATPIT in their signature need to actually define the ATPIT (https://github.com/rust-lang/rust/pull/123046)
Switch remaining DefineOpaqueTypes::No to Yes

horrible unreviewable PR: https://github.com/rust-lang/rust/pull/127034 instead try one of the following

try revealing opaque type in candidate assembly and bail as ambiguous while no concrete hidden type available https://github.com/oli-obk/rust/tree/infer instead (see https://rust-lang.zulipchat.com/#narrow/stream/144729-t-types/topic/opaque.20types.20and.20ATPIT.20oh.20my/near/451059084 for details)
or try normalizing opaques to infer vars eagerly https://github.com/rust-lang/rust/compare/master...oli-obk:infer2?expand=1 (may need AliasRelate predicate support in the old solver? not sure) Read https://hackmd.io/lXnLt7nsSS2NUFGHKW4B3Q to see what we can do to make old solver's opaques more similar to the new solver

unreviewed PR: https://github.com/rust-lang/rust/pull/126316
unopened PR: https://github.com/oli-obk/rust/pull/new/define_opaque_types22

Not necessary for stabilization, but would be cool if #[defines()] would make a method not define the opaque type, even if it is in the signature (see https://github.com/rust-lang/rust/pull/128440 for an impl of the #[defines] attribute)

No progress (that I know of) since last update

No progress

I'm going to close this goal -- consensus is that we will not reach stabilization in this goal period. We'll try again next time!


Caused by: java.lang.ClassNotFoundException: com.yahoo.ycsb.Client

Hi, mighty confused.
After using YCSB successfully for a while on this host, it's now giving me an error. Started after I tried to write a script to automate some work.  Seems that I've lost track of some Java components, but I've changed nothing about Java. Thought it might be something I changed in my environment but logging out and back in did not clear the problem.  Don't know much about Java...  Thanks for any ideas.
[root@r2601-d5-us03 YCSB]# python2.7 ./bin/ycsb load mongodb-async -s -P workloads/workloadb
[WARN]  Running against a source checkout. In order to get our runtime dependencies we'll have to invoke Maven. Depending on the state of your system, this may take ~30-45 seconds
[DEBUG]  Running 'mvn -pl com.yahoo.ycsb:mongodb-binding -am package -DskipTests dependency:build-classpath -DincludeScope=compile -Dmdep.outputFilterFile=true'
java -cp /usr/local/YCSB/mongodb/conf:/usr/local/YCSB/mongodb/target/mongodb-binding-0.3.0-SNAPSHOT.jar:/root/.m2/repository/com/allanbank/mongodb-async-driver/2.0.1/mongodb-async-driver-2.0.1.jar:/usr/local/YCSB/core/target/core-0.3.0-SNAPSHOT.jar:/root/.m2/repository/org/codehaus/jackson/jackson-core-asl/1.9.4/jackson-core-asl-1.9.4.jar:/root/.m2/repository/org/hdrhistogram/HdrHistogram/2.1.4/HdrHistogram-2.1.4.jar:/root/.m2/repository/org/mongodb/mongo-java-driver/3.0.2/mongo-java-driver-3.0.2.jar:/root/.m2/repository/org/codehaus/jackson/jackson-mapper-asl/1.9.4/jackson-mapper-asl-1.9.4.jar com.yahoo.ycsb.Client -db com.yahoo.ycsb.db.AsyncMongoDbClient -s -P workloads/workloadb -load
Exception in thread "main" java.lang.NoClassDefFoundError: com/yahoo/ycsb/Client
Caused by: java.lang.ClassNotFoundException: com.yahoo.ycsb.Client
at java.net.URLClassLoader$1.run(URLClassLoader.java:217)
at java.security.AccessController.doPrivileged(Native Method)
at java.net.URLClassLoader.findClass(URLClassLoader.java:205)
at java.lang.ClassLoader.loadClass(ClassLoader.java:323)
at sun.misc.Launcher$AppClassLoader.loadClass(Launcher.java:294)
at java.lang.ClassLoader.loadClass(ClassLoader.java:268)
Could not find the main class: com.yahoo.ycsb.Client. Program will exit.

Does this file exist: /usr/local/YCSB/core/target/core-0.3.0-SNAPSHOT.jar?
If not make sure you do a mvn clean package before running ycsb.
If you are running automated scripts I recommend using the distribution that is generated by the package.  It is located in the distribution/target/ directory as a ycsb-<version>.tar.gz file. If you unpack that file somewhere it will then have a directory with the bin/ycsb script and all of the dependencies for each binding in well know locations.

Hi,
Yes the file exists: -rw-r--r--. 1 root root 1103269 Jul 16 11:56 /usr/local/YCSB/core/target/core-0.3.0-SNAPSHOT.jar
I used this method to install YCSB:
git clone git://github.com/brianfrankcooper/YCSB.git
cd YCSB
mvn -pl com.yahoo.ycsb:mongodb-binding -am clean package
I then do my work in /usr/local/YCSB.
It’s very odd that one script works fine, but if I run my new script it not only doesn’t work but also causes the first script to stop working...
—Peter

On Jul 16, 2015, at 9:23 PM, allanbank<EMAIL_ADDRESS>wrote:
Does this file exist: /usr/local/YCSB/core/target/core-0.3.0-SNAPSHOT.jar?
If not make sure you do a mvn clean package before running ycsb.
If you are running automated scripts I recommend using the distribution that is generated by the package. It is located in the distribution/target/ directory as a ycsb-.tar.gz file. If you unpack that file somewhere it will then have a directory with the bin/ycsb script and all of the dependencies for each binding in well know locations.
—
Reply to this email directly or view it on GitHub https://github.com/brianfrankcooper/YCSB/issues/361#issuecomment-122143315.

Just tried reinstalling with
git clone git://github.com/brianfrankcooper/YCSB.git git://github.com/brianfrankcooper/YCSB.git
cd YCSB
mvn -pl com.yahoo.ycsb:mongodb-binding -am clean package
That seemed to fix the problem (probably until I run my new script again)…
—Peter

On Jul 16, 2015, at 11:01 PM, Peter Baer Galvin<EMAIL_ADDRESS>wrote:
Hi,
Yes the file exists: -rw-r--r--. 1 root root 1103269 Jul 16 11:56 /usr/local/YCSB/core/target/core-0.3.0-SNAPSHOT.jar
I used this method to install YCSB:
git clone git://github.com/brianfrankcooper/YCSB.git git://github.com/brianfrankcooper/YCSB.git
cd YCSB
mvn -pl com.yahoo.ycsb:mongodb-binding -am clean package
I then do my work in /usr/local/YCSB.
It’s very odd that one script works fine, but if I run my new script it not only doesn’t work but also causes the first script to stop working...
—Peter

On Jul 16, 2015, at 9:23 PM, allanbank<EMAIL_ADDRESS><EMAIL_ADDRESS>wrote:
Does this file exist: /usr/local/YCSB/core/target/core-0.3.0-SNAPSHOT.jar?
If not make sure you do a mvn clean package before running ycsb.
If you are running automated scripts I recommend using the distribution that is generated by the package. It is located in the distribution/target/ directory as a ycsb-.tar.gz file. If you unpack that file somewhere it will then have a directory with the bin/ycsb script and all of the dependencies for each binding in well know locations.
—
Reply to this email directly or view it on GitHub https://github.com/brianfrankcooper/YCSB/issues/361#issuecomment-122143315.

Any chance you can post the new script in a gist?

Peter could you try using the 0.2.0 binary release instead of the working repo?
With the binary release you can run your tests without having to build.

That seems to have fixed the problem. Thanks!
—Peter

On Jul 17, 2015, at 8:54 AM, Sean Busbey<EMAIL_ADDRESS>wrote:
Peter could you try using the 0.2.0 binary release instead of the working repo?
With the binary release you can run your tests without having to build.
—
Reply to this email directly or view it on GitHub https://github.com/brianfrankcooper/YCSB/issues/361#issuecomment-122265857.