Infinite error loop

'Console Plus' logs are showing same error again and again. Not able to find any option to stop this without uninstalling the console plus. The pic below is showing that console has reported the same error
2149 times and yet doing the same thing again and again.

os version os x 10.9.1
bracket version Release 1.1 build 1.1.0-15558 (release ea908cae5)

Hii.. Can you provide some details : 1>  Is there any workflow that is causing this error ? If yes, please tell. 2> Open Developer Tool from Brackets (Debug -> Show Developer Tools ) and check whether these errors are also there. 3> Reload Brackets without Extensions (Debug -> Reload Without Extensions) and repeat the workflow and check whether these errors are in Developer Tools console.

The file causing exception belongs to extract which is a Deprecated feature See details .
Console plus extension works when tested.
Closing.


Add xtask to generate manpages

Codecov Report
All modified and coverable lines are covered by tests :white_check_mark:

Project coverage is 90.11%. Comparing base (e607f3a) to head (fb80c27).

Additional details and impacted files
@@            Coverage Diff             @@
##             main     #191      +/-   ##
==========================================
- Coverage   90.39%   90.11%   -0.29%
==========================================
  Files           9        9
  Lines         708      708
==========================================
- Hits          640      638       -2
- Misses         68       70       +2

:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Have feedback on the report? Share it here.


Update price of the test

The FAA and PSI are charging $175 now. That's what I paid yesterday.

I'm withdrawing this request to tidy up my GitHub task panels. No sweat about it at all.


Ryan M: Watch laravelsolutions.com

Ryan M requests the watch of the watch_keyword laravelsolutions\.com. See the MS search here and the Stack Exchange search in text, in URLs, and in code.

laravelsolutions\.com has been seen in 3 true positives, 0 false positives, and 0 NAAs.

Approved by tripleee in Charcoal HQ


figReal

i changed it to make it just 1 figure,
but i also screwed it up a bit.
can you add a title centered over A,B,C that says
"Brain vs. Mental Properties"
and make the heatmaps all the same size?

I made it a supertitle, since D is also about brain vs some properties.
The colorbar caused the size problem, which is fixed now.

you rock
On Fri, Aug 19, 2016 at 9:31 AM, cshen6<EMAIL_ADDRESS>wrote:

I made it a supertitle, since D is also about brain vs some properties.
The colorbar caused the size problem, which is fixed now.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/jovo/MGC/issues/89#issuecomment-241019041, or mute
the thread
https://github.com/notifications/unsubscribe-auth/AACjcmMEn9mXiuANdjQkzVLjpNoI5aS9ks5qhbBOgaJpZM4JoRGE
.

--
the glass is all full:  half water, half air.
neurodata.io, jovo calendar
https://calendar.google.com/calendar/embed?src=joshuav%40gmail.com&ctz=America/New_York

but the fonts were too small, so i made them bigger.
now

[ ] not everything fits on the page :(
[ ] the colorbar is too close to A
[ ] colorbar should have a title "p-value", right?

no  problem,  let me fix them
On Fri, Aug 19, 2016 at 10:59 AM, joshua vogelstein <
<EMAIL_ADDRESS>wrote:

but the fonts were too small, so i made them bigger.
now

not everything fits on the page :(
the colorbar is too close to A
colorbar should have a title "p-value", right?

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/jovo/MGC/issues/89#issuecomment-241042256, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ALX0yylgFr30zSt_cCDuXE0Ni-2V-huJks5qhcTtgaJpZM4JoRGE
.

all  fixed!
On Fri, Aug 19, 2016 at 11:04 AM, Cencheng Shen<EMAIL_ADDRESS>wrote:

no  problem,  let me fix them
On Fri, Aug 19, 2016 at 10:59 AM, joshua vogelstein <
<EMAIL_ADDRESS>wrote:

but the fonts were too small, so i made them bigger.
now

not everything fits on the page :(
the colorbar is too close to A
colorbar should have a title "p-value", right?

—
You are receiving this because you were assigned.
Reply to this email directly, view it on GitHub
https://github.com/jovo/MGC/issues/89#issuecomment-241042256, or mute
the thread
https://github.com/notifications/unsubscribe-auth/ALX0yylgFr30zSt_cCDuXE0Ni-2V-huJks5qhcTtgaJpZM4JoRGE
.


How add custom style properties to to search bar

How to add custom style properties to to search bar

I want to modify custom serach like below. Can anyone guide me how to achive this using react-native-searchbar

@iiitmahesh you're probably better off writing your own one from scratch or using https://github.com/umhan35/react-native-search-bar.


Make pulling images on M1 silicon more user friendly

Currently users who try to pull images on their M1 silicon (eg. using the local runner) will run into the following issue:
no matching manifest for linux/arm64/v8 in the manifest list entries

They can solve this by setting the DOCKER_DEFAULT_PLATFORM environment variable.
export DOCKER_DEFAULT_PLATFORM=linux/amd64

This will instruct docker to pull images built for the linux/amd64 platform instead. From the docker docs:

Some images do not support the ARM64 architecture. You can add --platform linux/amd64 to run (or build) an Intel image using emulation.
However, attempts to run Intel-based containers on Apple silicon machines under emulation can crash as qemu sometimes fails to run the container. In addition, filesystem change notification APIs (inotify) do not work under qemu emulation. Even when the containers do run correctly under emulation, they will be slower and use more memory than the native equivalent.
In summary, running Intel-based containers on Arm-based machines should be regarded as “best effort” only. We recommend running arm64 containers on Apple silicon machines whenever possible, and encouraging container authors to produce arm64, or multi-arch, versions of their containers. This issue should become less common over time, as more and more images are rebuilt supporting multiple architectures.

I see different actions we can take with different levels of investment and return:

Document the current workaround clearly
Add the platform flag / environment variable in the docker compose file when compiling the pipeline
Build arm64 or multi-arch images. We should investigate what is needed for this and how it will affect our build times, which are already quite long building for a single architecture.

Building multi-arch images has nice benefits:

easiest to use (no setting of env vars)
best performance (no emulation)
can be expanded for specialized architecture (TPU, AWS Graviton)

Downsides:

extra build time (cache seems to be unique per architecture) -> does this fit in github actions
extra problems that arise because of differences between architectures

If it is only for local development (local runner on  Mac's M1 chips) then I would just alter the docker-compose file to include the platform.
https://github.com/compose-spec/compose-spec/blob/master/spec.md#platform

The major clouds also offer ARM machines, especially Amazon it seems. Not sure how popular those are, but those would benefit from multi-arch images as well.

Since this might have an impact on image size as well, let's take https://github.com/ml6team/fondant/issues/573 into account and maybe tackle them together.


In dev: Test exhaustiveness of symbolic evaluator

We need a test that the symbolic evaluator really does check all the possible values of a type up to a certain amount of constructors; something like checking that symbolic evaluating with stopping condition sestConstructors st < 20 the term \(x : Pair (List Int) (List Int)) -> product (fst x) + product (snd x) will explore branches for x `elem` [ (as, bs) | length as + length bs == 19 ] (the pair has one constructor)

Note that the actual statistic right now is how unifications are done during matches are found during symbolic execution.

Is this why we're doing #98 ? If so, does it make sense to make add another dial to pirouette or does it make sense to refine how statistics are computed and remove a dial?

I had a discussion with @lucaspena, and the problem seems more complex that it appears at first, since there are a lot of traps which would make f e1 e2 just recurse forever on e1 if we don't have a cut-off. To prevent that, the code before #98 was:

Evaluating one step of all arguments in parallel, and only moving to the function body if none of those steps resulted in further evaluation;
Evaluating the body, the "assume" and the "to prove" functions in parallel. This is really important, as you want to prune the search as early as possible using the "assume" function.

Since the counter is only checked once after taking those parallel steps, it could be the case that you've seen several matches and thus the counter of known constructors is reached.
#98 was a simple attempt at being more precise by using a depth-first approach to the evaluation of arguments. We only look at argument 2 if argument 1 didn't take any further steps. This risks going into an infinite loop (imagine we symbolically evaluation something on a list, we get larger and larger symbolic lists at each step); but it's safe if you have a cut-off, since at some point you'll run out of fuel/constructors/... and the stopping condition for that branch would be true.
Thinking about it this weekend I've come to another possible strategy to be at the same time (1) more precise and (2) not risk into unfairness. Here's the strategy applied to a list of expressions:

Traverse the list looking for a match, and if found, take a step on that one (which introduces constructors);
If none of them is a match, then take a step in parallel on every expression.

I'm going to work on that on a separate branch.

@lucaspena, do you have some work on this that should become a PR? Please coordinate with @facundominguez so we don't duplicate work. He will be picking this up as part of his pirouette onboarding

Hello! While the discussion here seems to focus around how to make the symbolic evaluator be exhaustive, I'm wondering now about how to test what the evaluator has actually checked (whether exhaustive or not).
One obvious way forward would be to augment the output of the symbolic evaluator with tracing information. So every time we ask to check a property, we keep a record of the information we have at that point about the meta variables.
I wanted to grab the opportunity to float another idea though. What if the symbolic evaluator were split in three phases?

The first phase would produce an infinite tree, holding in the nodes the assumptions and the properties that the SMT solver needs to check.
The second phase would just traverse the infinite tree in bread first order, or whatever strategy you think is best, and construct an infinite list of nodes.
The third phase would just traverse the list sequentially until the SMT solver finds an interesting node.

If working with this design, it would be easier to inspect which work is asked of the SMT solver and in which order. It would also help separating the concerns of producing the paths of symbolic execution and evaluating them.

Hello @facundominguez!
I like your second idea very much! In fact, one would even argue that this would be the Haskell way of building a symbolic engine! I think that such work might severely simplify the backend of pirouette and even help with a future problem: how to define different evaluation semantics. Because pirouette is language-agnostic, we should be able to plug in call-by-name and call-by-value languages: it seems to me that the evaluation semantics could be define as a traversal of the infinite tree that the evaluator generates.


aws-sdk regresion https://github.com/aws/aws-sdk-java/issues/1657 introduced on gradle 4.8.1

A regresion in aws-sdk causes output noise in builds using it (https://github.com/aws/aws-sdk-java/issues/1657). Builds using S3 repos work but the connection objects are not reused (builds take more time) and a log statement is included in the output
This was not happening with gradle 4.4.1 which ships aws-sdk 1.11.6 but happens with aws-sdk 1.11.267. It is suposed to be fixed on 1.11.374
Not all bytes were read from the S3ObjectInputStream, aborting HTTP
The builds don't fail but the generated logs grow in size.
Expected Behavior
Do not generate output noise.
Current Behavior
The output contains repeated log statements from aws-sdk when objects are pulled from aws s3 buckets (on private repos), specially if the header indicates the resource has not been altered and the connection is aborted.
Context
N/A
Steps to Reproduce (for bugs)
N/A
Your Environment
Gradle 4.8.1

Build scan URL:
N/A

@marcphilipp not in gradle 5.0; our production builds have dependencies on incompatible tasks. We might need to redo the tasks but it's not in short term pipeline.

We're having the same issue and after some digging I found this:
https://github.com/aws/aws-sdk-java/issues/1111
Don't know if it applies to here or not, but the explanation and workaround suggested for the issue above is:
ZIP archives have a (redundant) central directory structure at the end, so you can list the contents of the archive without scanning through the whole thing. Java's ZipInputStream never actually consumes this from the underlying stream; getNextEntry() returns null as soon as it finds the start of the central directory.
You might try adding while (in.read() >= 0); in your overridden close method to read through to the end of the underlying stream?

Probably related to #4162

This was not happening on Gradle 4.4.1; aws-sdk 2.0 is still not production ready.
@marcphilipp I think I will be able to get some time to test it on my next sprint, during the next couple of weeks. LMK if a nightly build is ready and I'll do my best

@TarodBOFH I've updated the AWS SDK to 1.11.407. Please try the latest nightly and let me know whether it helped. Thanks!


Cast interface generates non-compiling code for struct return type.

Component
Cast
Have you ensured that all of these are up to date?

[X] Foundry
[X] Foundryup

What version of Foundry are you on?
0.2.0 (56dc746 2022-08-26T00:07:43.474069Z)
What command(s) is the bug in?
cast interface
Operating System
macOS (Intel)
Describe the bug
Summary
When encountering functions with an array of structs as a return type, cast --interface generates solidity code that does not compile.
Example
For the following input code
// SPDX-License-Identifier: MIT
pragma solidity ^0.8.15;

contract ExampleContract
{
    struct NFT {
        address tokenContract;
        uint256 tokenId;
    }

    NFT[] nfts;

    function getNfts() public view returns (NFT[] memory) {
        return nfts;
    }
}

cast generates the following interface (when run against the json abi obtained from above source code via forge build):
pragma solidity ^0.8.15;

interface Interface {
    function getNfts() external view returns ((address, uint256)[] memory);
}

which triggers the following error when trying to compile with forge build:
Compiler run failed
error[3546]: ParserError: Expected type name
 --> src/ExampleGeneratedInterface.sol:4:47:
  |
4 |     function getNfts() external view returns ((address, uint256)[] memory);
  |                                               ^

right, tuples are not proper types, we should support structs here as well

Seems to be fixed (according to manual tests on commit 8fd5930c74d352bb8e8c7dffc3e7fd7839ecb535
)

This still seems to be an issue if you provide an ABI to cast interface because ABIs don't specify structs.


Added delete button for comments and functionality such that only authenticated user can comment.

What is the change?
Added Delete button for comments which is visible to all to delete comments.
Added functionality such that only authenticated user can comment
Removed the user name input box in the comments and fetched the username from the database.
How was it tested?
Tested it on my pc and it works fine.
Checklist:
Before you create this PR, confirm all the requirements listed below by checking the checkboxes [x]:

[x] Have you followed the Contribution Guidelines while contributing.
[x] Have you checked there aren't other open Pull Requests for the same update/change?
[] Have you made corresponding changes to the documentation?
[x] Your submission doesn't break any existing feature.
[x] Have you tested the code before submission?

Screenshots or Video:
https://user-images.githubusercontent.com/55927827/108386842-0b18b800-7233-11eb-9e33-33a873895178.mp4

This code is giving some error on my local machine, could be my environment. So I wasn't able to test this code locally. Can you tell whether the delete option appears for all the people visiting the website or only the user whose post the comment is on or only to the person who has made the comment.
Ideal would be the delete button should be visible to the owner of the post and the person who has made the comment.

Yes, the delete comment button appears to all as of now ( as instructed in the issue) so that vulgar comments can be deleted.

Yes, the delete comment button appears to all as of now ( as instructed in the issue) so that vulgar comments can be deleted.

Ok, sounds good. Let's make one change though, to delete a comment, the person needs to be logged in or a registered user.

Actually, I have made a new pull request to the develop branch so if it is fine then merge the pull request and raise an issue regarding the change. I'll work on that

Actually, I have made a new pull request to the develop branch so if it is fine then merge the pull request and raise an issue regarding the change. I'll work on that

No it is the part of this issue only, regarding deleting a comment. Even if you have created a pull request, you can still make changes to that adding commits to that branch. It's a very small and easy updation. Let me know when you're done.

Hi,
I have made the changes and also made a PR on the develop branch.


Digest the CI workflow and document how it's done

As a follow-up to #1, this change-set digests all actions used in that workflow and documents how to use actions-digest with various examples.

As one can observe, the workflow was executed using all the digested action steps on this pull-request.


Add skip-transaction-signatures option to eosd

A skip-transaction-signatures cli option is needed for eosd so that it can be run in test mode such that transactions do not have to be signed.

Merged by Dan. https://github.com/EOSIO/eos/pull/177


Determine route direction based on querystring/header/path

NOTE: Please read the Contributing.md guidelines before submitting your patch:
https://github.com/apache/incubator-apisix/blob/master/Contributing.md#how-to-add-a-new-feature-or-change-an-existing-one
Summary
Determine route direction based on querystring/header/path
Full changelog

change upstream based on querystring/header/path
support priority with rules
support  combination rules

Issues resolved
Fix #922

+make lint
luacheck -q lua
Checking lua/apisix/plugins/routex.lua            1 warning
    lua/apisix/plugins/routex.lua:182:33: empty if branch
Total: 1 warning / 0 errors in 71 files
Makefile:71: recipe for target 'lint' failed
make: *** [lint] Error 1
+exit 1


Proper Documentation?

When will we be able to read proper documentation, the one that already exists is very incomplete and it's timeconsuming to find all the methods and parameters of a function and class, I have tried some unofficial documentation but they are incomplete so are all tutorials? In the first place as a developer, I would look for the documentation for a code or library but I am extremely unpleased to find such crappy documentation for such a good code.
Sorry for the anger,
Dex Devlon.

Sorry for the anger

It's fine, your reaction is much better than many other people's.
It's important to keep the proper perspective on this project. It's primarily developed by a single person, for a single purpose, for use in a single development environment. And it just happens to be in a public location.
Manim doesn't have anywhere near the community support of matplotlib or numpy for example. All of the documentation, tutorials, support threads, etc. that you've come across are there because someone else was once in your position, took the time to read through the code, and wanted to make it a little easier for the next person.
The unfortunate reality is that despite producing a nice result, manim isn't designed very well. It's buggy, difficult to set up, and renders far too slowly for the average developer to use it comfortably. As a result, people tend to consider it a better use of time to try to improve the library rather than document it while it's still so unwieldy.

The unfortunate reality is that despite producing a nice result, manim isn't designed very well. It's buggy, difficult to set up, and renders far too slowly for the average developer to use it comfortably. As a result, people tend to consider it a better use of time to try to improve the library rather than document it while it's still so unwieldy.

if I am right and not to be mean, bugs are found in any programs and fixing them is a good thing, but it doesn't even matter if no one is going to use as no one is going to understand how to do X or what does Y mean, yes I get it that there is technically only one person doing it but their cant be more people doing it as no one understands it, you may have heard that reading the documentation for 15 mins will save you googling of 2 hours.

Manim doesn't have anywhere near the community support of matplotlib or numpy for example.

My suggestion is to make better documentation so that people don't get scared of the first look at the documentation and run away, I am sure many people world have at least looked at the repo in expectation to make some animation of there own but got scared or tired for looking for the answer. And the fact that 3b1b has over 2m subscribers also adds on to the fact.
I am again sorry to be in anger,
Dex Devlon

This was resolved offline.

The conclusion of the issue for people who may have stumbled over this issue is that manim dev community is not prioritizing better documentation because of changes happening all the time and the size of the manim. Manim is not (yet) a community tool.
Correct me if I am wrong @eulertour,
Thanks,
Dex Devlon

Are there any other open-source python tools similar to Manim with better documentation?

@Shubodh, Well its complicated, you could do it the hard way using pycairo and making animation in it, or could use other libraries made on it, e.g. mplcairo which uses matplotlib on pycairo, its pretty cool but limited to mostly making graphs, other than that, I don't really know another library as complicated and well developed as pycairo, maybe processing.py might help? And just forgot to mention that manim is build on pycairo.
Thanks,
Dex Devlon

mplcairo looks interesting, will check it out. Thanks @bin0x00!


Derive SmallPrime and LargePrime constants from hex string, rather than base64 string.

The productionGroup().constants.smallPrime and largePrime have leading 0's in their byte arrays when they are formed from the base64 string. (this is for JVM, havent tested on native).
Theres no problem with the mathematics, but the serialization (both proto and JSON) retain the leading 0's, which can make the verifier fail when testing that the constants are correct.
There are a number of ways to fix this, but I think a simple one is to use the base16 string instead of the base64. This has the added advantage of matching the spec, which specifies them in base16.
See electionguard/core/ConstantsTest.kt testConstants(). Output is:
smallPrime size= 33
smallPrime     = 00FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF43
qnormal        = FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF43
q64 size= 33
q64     = 00FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF43
q16 size= 32
q16     = FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF43

====================

largePrime size= 513
largePrime     = 00FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF93C467E37DB0C7A4D1BE3F810152CB56A1CECC3AF65CC0190C03DF34709AFFBD8E4B59FA03A9F0EED0649CCB621057D11056AE9132135A08E43B4673D74BAFEA58DEB878CC86D733DBE7BF38154B36CF8A96D1567899AAAE0C09D4C8B6B7B86FD2A1EA1DE62FF8643EC7C271827977225E6AC2F0BD61C746961542A3CE3BEA5DB54FE70E63E6D09F8FC28658E80567A47CFDE60EE741E5D85A7BD46931CED8220365594964B839896FCAABCCC9B31959C083F22AD3EE591C32FAB2C7448F2A057DB2DB49EE52E0182741E53865F004CC8E704B7C5C40BF304C4D8C4F13EDF6047C555302D2238D8CE11DF2424F1B66C2C5D238D0744DB679AF2890487031F9C0AEA1C4BB6FE9554EE528FDF1B05E5B256223B2F09215F3719F9C7CCC69DDF172D0D6234217FCC0037F18B93EF5389130B7A661E5C26E54214068BBCAFEA32A67818BD3075AD1F5C7E9CC3D1737FB28171BAF84DBB6612B7881C1A48E439CD03A92BF52225A2B38E6542E9F722BCE15A381B5753EA842763381CCAE83512B30511B32E5E8D80362149AD030AABA5F3A5798BB22AA7EC1B6D0F17903F4E22D840734AA85973F79A93FFB82A75C47C03D43D2F9CA02D03199BACEDDD4533A52566AFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
pnormal        = FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF93C467E37DB0C7A4D1BE3F810152CB56A1CECC3AF65CC0190C03DF34709AFFBD8E4B59FA03A9F0EED0649CCB621057D11056AE9132135A08E43B4673D74BAFEA58DEB878CC86D733DBE7BF38154B36CF8A96D1567899AAAE0C09D4C8B6B7B86FD2A1EA1DE62FF8643EC7C271827977225E6AC2F0BD61C746961542A3CE3BEA5DB54FE70E63E6D09F8FC28658E80567A47CFDE60EE741E5D85A7BD46931CED8220365594964B839896FCAABCCC9B31959C083F22AD3EE591C32FAB2C7448F2A057DB2DB49EE52E0182741E53865F004CC8E704B7C5C40BF304C4D8C4F13EDF6047C555302D2238D8CE11DF2424F1B66C2C5D238D0744DB679AF2890487031F9C0AEA1C4BB6FE9554EE528FDF1B05E5B256223B2F09215F3719F9C7CCC69DDF172D0D6234217FCC0037F18B93EF5389130B7A661E5C26E54214068BBCAFEA32A67818BD3075AD1F5C7E9CC3D1737FB28171BAF84DBB6612B7881C1A48E439CD03A92BF52225A2B38E6542E9F722BCE15A381B5753EA842763381CCAE83512B30511B32E5E8D80362149AD030AABA5F3A5798BB22AA7EC1B6D0F17903F4E22D840734AA85973F79A93FFB82A75C47C03D43D2F9CA02D03199BACEDDD4533A52566AFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
q64 size= 513
q64     = 00FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF93C467E37DB0C7A4D1BE3F810152CB56A1CECC3AF65CC0190C03DF34709AFFBD8E4B59FA03A9F0EED0649CCB621057D11056AE9132135A08E43B4673D74BAFEA58DEB878CC86D733DBE7BF38154B36CF8A96D1567899AAAE0C09D4C8B6B7B86FD2A1EA1DE62FF8643EC7C271827977225E6AC2F0BD61C746961542A3CE3BEA5DB54FE70E63E6D09F8FC28658E80567A47CFDE60EE741E5D85A7BD46931CED8220365594964B839896FCAABCCC9B31959C083F22AD3EE591C32FAB2C7448F2A057DB2DB49EE52E0182741E53865F004CC8E704B7C5C40BF304C4D8C4F13EDF6047C555302D2238D8CE11DF2424F1B66C2C5D238D0744DB679AF2890487031F9C0AEA1C4BB6FE9554EE528FDF1B05E5B256223B2F09215F3719F9C7CCC69DDF172D0D6234217FCC0037F18B93EF5389130B7A661E5C26E54214068BBCAFEA32A67818BD3075AD1F5C7E9CC3D1737FB28171BAF84DBB6612B7881C1A48E439CD03A92BF52225A2B38E6542E9F722BCE15A381B5753EA842763381CCAE83512B30511B32E5E8D80362149AD030AABA5F3A5798BB22AA7EC1B6D0F17903F4E22D840734AA85973F79A93FFB82A75C47C03D43D2F9CA02D03199BACEDDD4533A52566AFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF
p16 size= 512
p16     = FFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF93C467E37DB0C7A4D1BE3F810152CB56A1CECC3AF65CC0190C03DF34709AFFBD8E4B59FA03A9F0EED0649CCB621057D11056AE9132135A08E43B4673D74BAFEA58DEB878CC86D733DBE7BF38154B36CF8A96D1567899AAAE0C09D4C8B6B7B86FD2A1EA1DE62FF8643EC7C271827977225E6AC2F0BD61C746961542A3CE3BEA5DB54FE70E63E6D09F8FC28658E80567A47CFDE60EE741E5D85A7BD46931CED8220365594964B839896FCAABCCC9B31959C083F22AD3EE591C32FAB2C7448F2A057DB2DB49EE52E0182741E53865F004CC8E704B7C5C40BF304C4D8C4F13EDF6047C555302D2238D8CE11DF2424F1B66C2C5D238D0744DB679AF2890487031F9C0AEA1C4BB6FE9554EE528FDF1B05E5B256223B2F09215F3719F9C7CCC69DDF172D0D6234217FCC0037F18B93EF5389130B7A661E5C26E54214068BBCAFEA32A67818BD3075AD1F5C7E9CC3D1737FB28171BAF84DBB6612B7881C1A48E439CD03A92BF52225A2B38E6542E9F722BCE15A381B5753EA842763381CCAE83512B30511B32E5E8D80362149AD030AABA5F3A5798BB22AA7EC1B6D0F17903F4E22D840734AA85973F79A93FFB82A75C47C03D43D2F9CA02D03199BACEDDD4533A52566AFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFFF

What do you think, @danwallach ?

Not sure if I know what all the values in
egklib/src/commonMain/kotlin/electionguard/core/GroupCommon.kt
should be.
What do you think, @danwallach  ?

I suppose we could change from base64 to base16 for the constants. The reason I decided to go with base64 was that I thought base16 was wasteful particularly when you're doing JSON and you've got a million ballots. Getting to 6 bits per byte rather than 4 bits per byte is a significant savings.
For purposes of making it easier to cut-and-paste from the standard docs into GroupCommon.kt, it makes sense to go with base16.
BTW, there's something else going on here worth noting: We've got a bunch of pre-computed constants. Things like b64Production4096P256MinusQ is just $$2^{256} - Q$$ (i.e., the additive inverse of Q), which comes in handy for some equations. Similar things are going on for the Montgomery transformation, where I'm hanging on to $$i-1$$ so I can avoid having to recompute it. I know this smacks of premature optimization, but I was aiming to make as few HACL calls as possible, and these things helped with that.

Also worth noting here, we've got our own Base16.kt and Base64.kt classes which define extension functions on ByteArray. At least hypothetically, this gives us identical behavior between native and JVM. If you wanted to change leading-zero behavior for a base-16 conversion, you'd do it in Base16.kt.
Honestly, though, I thought one of the outcomes of the hashing discussion was that we'd want to hash the raw bytes without any conversion prior to hashing. That suggests that the only thing to do is to have a ByteArray method that strips leading zeros.

I have the failing test in  ConstantsTest commented out for now.
Waiting for 2.0 spec, and hopefullly some sample election records to test against.

this has been fixed in 2.0, see Primes4096 and Primes3072.


Remove redundant ip_forward check

Signed-off-by: Lei Jitang<EMAIL_ADDRESS>Carry from #14665 , closes #15286

LGTM if janky's happy

LGTM

cherry picked into #15091


[Stepper] Add TypographyProps to StepLabel

[x] I have searched the issues of this repository and believe that this is not a duplicate.

Summary 💡
I want to add a TypographyProps argument to StepLabelProps in the same vein as StepIconProps.
Examples 🌈
How I currently code
<StepLabel>
  Label
</StepLabel>

How I wish to code
<StepLabel TypographyProps={{ 'aria-current': 'step' }}>Label</StepLabel>

Motivation 🔦
I want to add an ARIA property to the span that wraps the label, but I currently can't. My current solution is to place a span inside the StepLabel, but it just adds an unnecessary DOM element.

Another possible solution to my direct problem is to have already that aria-current="step" when active is true in the StepLabel component on the Typography component. Both solutions are improvements to the component, and I'm willing to create a PR if y'all OK with these ideas.

I just tried using Apple's screen reader, VoiceOver, for the first time. I just realized that it reads the current step only if I place aria-current="step" on the StepButton component. Making my use case for this feature request obsolete.
I still believe that we should add TypographyProps to the StepLabel component. Do y'all think it's still a good idea?
I suggested adding aria-current="step" to the StepLabel component in the previous comment. Given what I just learned, should we add that property to the StepButton component instead?

This looks close to https://github.com/mui-org/material-ui/issues/19696#issuecomment-841746100

Yeah, I do see the similarities, @oliviertassinari. I'll write up a PR similar to #25883 but for the StepLabel component. What about the other question I have about aria-current="step"? Should I create a PR to add that to the StepButton component when it is active?

A couple of thoughts:

I'm not sure that the accessibility dimension of the Stepper has been seriously considered in the past. I could find different approaches. But I'm not sure we need to change it:

ol > li: https://www.w3.org/WAI/tutorials/forms/multi-page/
tabs: https://material.angular.io/components/stepper/overview, http://www.jquery-steps.com/Examples

The TypographyProps goes in opposition to the direction we took in #21453. Better follow #25883.
Developers can't really customize the componentsProps prop in theme.components.MuiStepLabel.defaultProps, as the structure is nested. Maybe we don't need to worry about it.
We could reduce the number of rendered components with:

diff --git a/packages/material-ui/src/StepLabel/StepLabel.js b/packages/material-ui/src/StepLabel/StepLabel.js
index b2749f1671..414ba72ebe 100644
--- a/packages/material-ui/src/StepLabel/StepLabel.js
+++ b/packages/material-ui/src/StepLabel/StepLabel.js
@@ -4,7 +4,6 @@ import clsx from 'clsx';
 import { unstable_composeClasses as composeClasses } from '@material-ui/unstyled';
 import experimentalStyled from '../styles/experimentalStyled';
 import useThemeProps from '../styles/useThemeProps';
-import Typography from '../Typography';
 import StepIcon from '../StepIcon';
 import StepperContext from '../Stepper/StepperContext';
 import StepContext from '../Step/StepContext';
@@ -64,11 +63,13 @@ const StepLabelRoot = experimentalStyled('span', {
   }),
 }));

-const StepLabelLabel = experimentalStyled(Typography, {
+const StepLabelLabel = experimentalStyled('span', {
   name: 'MuiStepLabel',
   slot: 'Label',
   overridesResolver: (props, styles) => styles.label,
 })(({ theme }) => ({
+  ...theme.typography.body2,
+  display: 'block',
   /* Styles applied to the Typography component that wraps `children`. */
   transition: theme.transitions.create('color', {
     duration: theme.transitions.duration.shortest,
@@ -170,9 +171,6 @@ const StepLabel = React.forwardRef(function StepLabel(inProps, ref) {
       <StepLabelLabelContainer className={classes.labelContainer} styleProps={styleProps}>
         {children ? (
           <StepLabelLabel
-            variant="body2"
-            component="span"
-            display="block"
             className={classes.label}
             styleProps={styleProps}
           >


Choose correct component for user creation and organization creation

Actually the current component for the creation of user and organization are not good (may be the CreationUser and the CreateOrganization component)
We can also clean all console.log :)

we must change this bloc in route.tsx:
	{
		path: '/realm/:realm/users/create',
		exact: true,
		breadcrumb: 'Création',
		component: DetailsOrganization,
		secure: true,
	},

to :
	{
   	path: '/realm/:realm/users/create',
   	exact: true,
   	breadcrumb: 'Création',
   	component: CreateUsers,
   	secure: true,
   },

and the same for create organization :)

we must change this bloc in route.tsx:
	{
		path: '/realm/:realm/users/create',
		exact: true,
		breadcrumb: 'Création',
		component: DetailsOrganization,
		secure: true,
	},

to :
	{
   	path: '/realm/:realm/users/create',
   	exact: true,
   	breadcrumb: 'Création',
   	component: CreateUsers,
   	secure: true,
   },

and the same for create organization :)

And all the occurence of console.log can be clean :)

And all the occurence of console.log can be clean :)


Remove message_list.narrowed from codebase.

Discussion: https://chat.zulip.org/#narrow/stream/6-frontend/topic/message_lists.2Ecurrent.20vs.20message_list.2Enarrowed
Right now, it only has some of prep commits.

I don't think the abstraction of a new exported current_different_than_home function is directly helpful. I think we want to be these blocks into something like this:
for (const msg_list of messages_lists.all_rendered_message_lists()) {
    msg_list.view.rerender_messages([message]);
}

And then we can just define a couple functions:
export function all_rendered_message_lists {
    const rendered_message_lists = [home_msg_list];
    if (current_msg_list !== home_msg_list) {
        rendered_message_lists.append(current_msg_list);
    }
    return rendered_message_lists;
}

export function all_message_lists(...)

This way, we only have to do one sweep through all these places, and we contain the logical detail that there are up to 2 message lists that might be rendered at any given time just in this one file.
(And I think we can do this sweep that way today, with just a single prep commit defining functions like all_rendered_message_lists)

@timabbott I updated this PR based on your feedback, ready for another round of review!

Cool, I like the interface we've developed here! There's one bundle of coupled problems, which is that I don't think the message_lists => message_list refactor is desirable, for a few reasons:

It introduces an import cycle that will be annoying when we move to typescript
The this === message_lists.current checks inside message_list.js are awkward.

I'll post an inline comment on how I think we can fix that, basically by making the message list itself now whether it's the current one.

@timabbott fixed the tests.

This is kinda getting bogged down, and it's starting to feel painful to rereview the whole thing every time. Perhaps you can split this into smaller commits? Some parts are very much working, like introducing all_rendered_message_lists and migrating a bunch of the loops, and I'd like to integrate them.

@timabbott separated the all_rendered_message_lists change as a separate commit and seems to be working fine on its own.

I added a new second-to-last commit, which introduce some test failures likely related to mocking that I haven't investigated.

@timabbott fixed the tests and pushed.

Great, I merged the first 4 commits as the series ending with 303bbee2a2ae00c37f142b642902bbd0595a1fbf; see the comment above on the last one's migration.

One of the prep commits here was likely responsible for the subtle interaction causing https://chat.zulip.org/#narrow/stream/9-issues/topic/Lost.20unreads.20in.20recent.20topics/near/1422941. I'm trying to figure out whether there's an easy way to address it via pushing on #22618.

See 22784. I think what we probably need to do is set current_message_list to null when you're viewing recent topics, and figure out how to make doing so not break anything.

I think what we probably need to do is set current_message_list to null when you're viewing recent topics, and figure out how to make doing so not break anything.

It would break a lot of things, so not worth it.

I think what we probably need to do is set current_message_list to null when you're viewing recent topics, and figure out how to make doing so not break anything.

I gave a good shot at this but there are 200+ occurrences of message_lists.current some of which are inside are functions which are used inside multiple functions which are in areas that are hard to verify if things are working as intended. Also, since we are planning to use a message_list for recent_topics, we can just fix the ones that are not relevant operations for recent topics, and it would likely be a much simpler change.

OK. One reason why I'm thinking about that is that it's the correct conceptual model and when we add the "inbox" view, we're going to double all the places where we currently need to check whether "Recent topics" is in view ... but perhaps we need to prioritize that work later.

I pushed back after some small local changes. posted a few comments but I think we should be able to merge this once you resolve those.

@timabbott updated based on your reviews!

Merged, with a few nonfunctional changes to just better document some of the conditionals (or order them in a more readable way). Thanks @amanagr!


Please update the guide with at least one complete example of how to use Stream=True for gpt-3.5-turbo

would be greatly appreciated. it's kind of wild to take the time to make an entire cookbook with no complete recipes in it that someone could just copy paste and run on their own.
I struggled for 3 hours today trying to get gpt-4 to implement any working example, and it failed over and over even after including the entire cookbook as context.
in the meantime, if anybody has any working examples of streaming the response to a chat completion prompt with the gpt-3.5-turbo model, you would be my hero. i'm also interested in what context i could have given gpt 4 such that it would be able to figure this out. Google's Bard also failed miserably, so it's not just a gpt thing.
thank you!

What would make this guide better or more discoverable?
https://github.com/openai/openai-cookbook/blob/main/examples/How_to_stream_completions.ipynb

this is the cookbook i'm talking about that i'd like to see improved.
1/ if there's anywhere in that guide that includes a code snippet i can copy paste, swap in my api key, and run, then please point me to it -- i would greatly appreciate it. so one way to improve the guide would be to add in an example program that the reader can run. that would be 10X more valuable than all of the space spent on timing differences.
2/ after failing to figure it out myself, when i copy pasted the the entire guide as context for gpt-4 and asked to help create an app that includes a streaming response with gpt-3.5-turbo, it was unable to do even after multiple hours of back and forth. i then tried Bard, which is able to access the internet itself, and it also failed to figure it out. so a second way to improve the guide would be to keep refining it until at least gpt 4 can understand it in one shot.
3/ this isn't an improvement to the guide, but if you personally have example code i can use to successfully figure out how to get this working, that would be greatly appreciated. i'm developing an app that lets users learn foreign languages via song lyrics line by line, but without the streaming responses it feels too slow.
thank you very much for your time and for listening!

in case anyone comes across this curious, managed to finally get this code working:
`import openai
import time
import tkinter as tk
openai.api_key = "YOUR_API_KEY_HERE"
conversation_history = [
{"role": "system", "content": "You are a helpful assistant that counts numbers."},
{"role": "user", "content": "Start counting from 1 to 100."},
]
def get_response():
user_input = input_entry.get()
input_entry.delete(0, tk.END)  # Clear the input entry widget
conversation_history.append({"role": "user", "content": user_input})
output.insert(tk.END, f"You: {user_input}\n")  # Display the user's message
output.see(tk.END)  # Scroll to the bottom of the output text widget
# Record the time before the request is sent
start_time = time.time()

# Send a ChatCompletion request with the conversation history
response = openai.ChatCompletion.create(
    model='gpt-3.5-turbo',
    messages=conversation_history,
    stream=True,
)

content_accumulator = ""
# Iterate through the stream of events
for event in response:
    event_time = time.time() - start_time  # Calculate the time delay of the event

    # Check if the keys 'choices', 'delta', and 'content' are present in the event
    if 'choices' in event and 'delta' in event['choices'][0] and 'content' in event['choices'][0]['delta']:
        content = event['choices'][0]['delta']['content']
        conversation_history.append({"role": "assistant", "content": content})
        content_accumulator += content
        output.insert(tk.END, content)  # Insert the content without a newline
        output.update_idletasks()  # Update the output text widget immediately

        if content in {".", "?", "!"}:
            output.insert(tk.END, "\n")  # Add a newline after the specified punctuation
            output.see(tk.END)  # Scroll to the bottom of the output text widget

Create the main window
root = tk.Tk()
root.title("GPT-3.5 Turbo Response")
Create an input entry widget to receive user input
input_entry = tk.Entry(root, width=40)
input_entry.pack()
Create a button to fetch the response
button = tk.Button(root, text="Send", command=get_response)
button.pack()
Create a text widget to display the response and conversation history
output = tk.Text(root, wrap=tk.WORD, width=250, height=100)
output.pack()
Run the main loop
root.mainloop()
`

Here you go:
# imports
import openai  # for OpenAI API calls

# a ChatCompletion request
response = openai.ChatCompletion.create(
    model='gpt-3.5-turbo',
    messages=[
        {'role': 'user', 'content': "What's 1+1? Answer in one word."}
    ],
    temperature=0,
    stream=True  # this time, we set stream=True
)

for chunk in response:
    print(chunk)

How do I know that a stream is over? is there a "stream.on('end')" or something? Im using Node with the 'stream' package.


Photoshop script needs to be rewritten a little to actually work

Photoshop version
eg : CC2021
Wine latest version
Describe the bug
wine fails to launch wineboot and load kernel32.dll
To Reproduce
Steps to reproduce the behavior:
1.install photoshop by installer.sh
2.launch photoshop
3.get nothing
4.after a short period of time softlocks the pc (in my case virtualmachine)
Screenshots
If applicable, add screenshots to help explain your problem.

Expected behavior
for photoshop to launch
System informations

Distro : Arch_Linux
GPU : (NVIDIA)

Additional context
This is a fresh install from arch titus script i just installed wine and winetricks.
i use GTX 1060 8 GB
and i have a intel CPU
found out i was using wine staging will try the aur wine-stable package soon.

ok update on the issue i used the wine stable and still got the same issue
also seems like there is a bug in your script seems like
you forgot to export the WINEPREFIX= and from that issues arise
well this photoshop script will not work untill you fix the script
if i export it manually it does not give me the wineboot issue but still softlocks the virt machine
sagde i really wanna see this script to succeed.

This is what happens when you try to open it up

this install script works perfectly fine for me. https://github.com/Gictorbit/photoshopCClinux
so i guess i have to wait and see.

Please use the installer in the release section.

well thanks will try that later.

You should also know that if your device don't support vulkan it won't work.
I don't know if VMware supports vulkan.

(going a little off topic)
if i ever would learn bash scripting i would write a script that would install EVERYTHING that a 3d artist needs/uses on windows
things that are native
(Maya) (Short Explanation: this is where 3d artists rig and do animation) ( im just having libcrypt issues that i need to fix),
pureref (Short Explanation: this a massive refrence board where artists can yeet their refrences to)(would like to use beeref(FOSS on python(The Project is Abandoned)) but the pkg is broken),
Blender (Short Explanation:the most powerful 3d software to exist/can be used not just for 3d) (its native and its going to be way faster since its built for linux)
Adobe Substance Painter(Short Explanation: this is where artists make their textures) (you can download it Through AUR)
windows only apps that run almost natively (sometimes faster on linux)
(Zbrush) (Short Explanation: this is where 3d artists sculpt things) needs one dll override in order for your viewport to not go batshit insane, and emulate desktop to make wintab(aka pen pressure to work)
(Marmoset toolbag) (short explanation: this is where 3d artists bake normals and render their final work) installs natively you just need to make sure that you enable DXVK/VKD3D and after that its just native performance
(RizomUV) (Short Explanaiton: this is where 3d artists unwrap their meshes) literally windows experience in terms of installation click install and it just works.
i would make a script that install all of the above and include your script as an option if you like REALLY need photoshop instead i would just install krita,gimp is kinda not my taste for me.

(going a little off topic) if i ever would learn bash scripting i would write a script that would install EVERYTHING that a 3d artist needs/uses on windows
things that are native (Maya) (Short Explanation: this is where 3d artists rig and do animation) ( im just having libcrypt issues that i need to fix), it exists on AUR but the build of adsklicensing fails so you have to do it the scuffed way.
pureref (Short Explanation: this a massive refrence board where artists can yeet their refrences to)(would like to use beeref(FOSS on python(The Project is Abandoned)) but the pkg is broken),
Blender (Short Explanation:the most powerful 3d software to exist/can be used not just for 3d) (its native and its going to be way faster since its built for linux)
Adobe Substance Painter(Short Explanation: this is where artists make their textures) (you can download it Through AUR)
windows only apps that run almost natively (sometimes faster on linux)
(Zbrush) (Short Explanation: this is where 3d artists sculpt things) needs one dll override in order for your viewport to not go batshit insane, and emulate desktop to make wintab(aka pen pressure to work)
(Marmoset toolbag) (short explanation: this is where 3d artists bake normals and render their final work) installs natively you just need to make sure that you enable DXVK/VKD3D and after that its just native performance
(RizomUV) (Short Explanaiton: this is where 3d artists unwrap their meshes) literally windows experience in terms of installation click install and it just works.
i would make a script that install all of the above and include your script as an option if you like REALLY need photoshop instead i would just install krita,
gimp is meh.

As long as I'm credited for photoshop, I'm ok with it.

hey noob question, i booted into my hard drive installation of arch and uhh how do i give read and write permissions the entire home drive?
i genuinely want to know that.

hey noob question, i booted into my hard drive installation of arch and uhh how do i give read and write permissions the entire home drive?
i genuinely want to know that.

With the chown command... but it isn't recommended to give you permission in the home folder... but in your personal folder
Ex : don't give permission to /home/
But to /home/username/

hey seems like you did a big mistake writing a script since $1 variable leads to a filename not a path to user and it tries to write to root.
you should use $HOME variable instead since it will actually use the /home/user/ path to make the script somewhat work for some reason wget winetricks stops working for no reason
i also added 2 lines to specify script path variable
at the begginning of the script
so you can invoke it at any time you want.
i will upload my modified sh script here
hopefully you are much more skilled at bash scripting and fix the issue

The simple answer at why it isn't working it's because you havent read the documentation.
as you say, $1 is nothing and that's right until you read the documentation. $1 is used to define where to install the software.
if you say nothing it's nothing.

you have to say where to install it. if you don't it will install to /adobe-photoshop and yes that's the root folder.

oh then i just have to define $1 then and that would work?

oh then i just have to define $1 then and that would work?
like this sh photoshop2022install.sh /path/to/your/install/folder? (taken from the github page)

Yeahy that's the thing. $1 is the first argument. so if you set it like in the example you mentioned it will work.

ye just thanks. sorry for attracting unneeded attention


Containerd block snapshotter support

Kata does not support block based containerd snapshotters
Kata does not support block based containerd snapshotters. This is due to an incorrect assumption in Kata that there will be a directory called "rootfs" within the block device that holds the snapshot.
However with containerd block based snapshotters this no longer true.
e..g In the past the built in devicemapper would report the rootfs at
/var/lib/docker/devicemapper/mnt/999042f4b5dea95ed2b91e58ca5dbd865fe064f8a17cca5415489930f1a34df5/rootfs

The backing device is at
/var/lib/docker/devicemapper/mnt/999042f4b5dea95ed2b91e58ca5dbd865fe064f8a17cca5415489930f1a34df5/

and the rootfs is a directory under the backing device.
The Kata logic always assumed that this was the case.
However with the current container snapshotter implementation the rootfs is reported as follows
/dev/mapper/vgthin-47 on /run/containerd/io.containerd.runtime.v2.task/default/hello-kata-lvm/rootfs type xfs

the rootfs is a directory is the backing device.
i.e. the volume/block device is mounted directly at rootfs which breaks Kata logic
Kata Logic
Kata today has four different paths in handling the rootfs

Hypervisor does not support block device hotplug
Kata bind mounts the rootfs location to the shared directory at location c.id/rootfs
a. For overlay based snapshotters
b. For block based snapshotters

Hypervisor supports block device hotplug
a. overlay based snapshotters
Kata bind mounts the rootfs location to the shared directory at location c.id/rootfs
b. block based graph drivers (e.g devicemapper) where the rootfs is a directory within the device
c. block based snapshotters  (e.g firecracker devicemapper, kata lvm) where the rootfs is the device

We need to handle all of these cases
Fix
diff --git a/virtcontainers/container.go b/virtcontainers/container.go
index 5408d85..f11fe99 100644
--- a/virtcontainers/container.go
+++ b/virtcontainers/container.go
@@ -276,6 +276,7 @@ type Container struct {
        runPath       string
        configPath    string
        containerPath string
+       rootfsSuffix  string

        state types.State

@@ -640,6 +641,7 @@ func newContainer(sandbox *Sandbox, contConfig ContainerConfig) (*Container, err
                runPath:       store.ContainerRuntimeRootPath(sandbox.id, contConfig.ID),
                configPath:    store.ContainerConfigurationRootPath(sandbox.id, contConfig.ID),
                containerPath: filepath.Join(sandbox.id, contConfig.ID),
+               rootfsSuffix:  "rootfs",
                state:         types.State{},
                process:       Process{},
                mounts:        contConfig.Mounts,
@@ -1131,6 +1133,10 @@ func (c *Container) hotplugDrive() error {
                return nil
        }

+       if dev.mountPoint == c.rootFs {
+               c.rootfsSuffix = ""
+       }
+
        // If device mapper device, then fetch the full path of the device
        devicePath, fsType, err := getDevicePathAndFsType(dev.mountPoint)
        if err != nil {

Test Matrix

Kata with OCI interface with overlay (crio and containerd)
Kata with OCI interface with block based graphdriver with containerd
Kata with OCI interface with snapshotter with containerd
Kata with containerd-shim-v2 interface with overlay (crio and containerd)
Kata with containerd-shim-v2 interface with snapshotter with containerd

with
Kata configured to
A. Disable block device hotplug
B. Enable block device hotplug
# Disable block device from being used for a container's rootfs.
# In case of a storage driver like devicemapper where a container's
# root file system is backed by a block device, the block device is passed
# directly to the hypervisor for performance reasons.
# This flag prevents the block device from being passed to the hypervisor,
# 9pfs is used instead to pass the rootfs.
# disable_block_device_use = true
disable_block_device_use = false

We need this fix to support https://github.com/kata-containers/runtime/issues/1303

This should also fix https://github.com/kata-containers/runtime/issues/1248

@mcastelino we definitely need to solve this. Is the fix you're showing here the solution to both problems (with and without rootfs extension)? Or do we need to find a generic fix?

/cc @ganeshmaharaj @egernst @amshinde @sboeuf @bergwolf
With this change we can support all variants of graph drivers and snapshotters.
We should also make one more change longer term
https://github.com/kata-containers/runtime/blob/master/containerd-shim-v2/service.go#L327
This always mounts the block device on the host even though in the case of Kata this is no longer desired. In the case of block based snapshotters we should skip mounting on the hostside. This will be safer even though we may break some docker functionality.

@mcastelino yes we should check the type of device that needs to be mounted, and if it's a block device, we should ignore this.
/cc @lifupan

@mcastelino we definitely need to solve this. Is the fix you're showing here the solution to both problems (with and without rootfs extension)? Or do we need to find a generic fix?

@sboeuf this is a completely generic fix and should work for all use cases.

@mcastelino

@sboeuf this is a completely generic fix and should work for all use cases.

Why don't we have a PR submitted yet then? :smile:

@mcastelino yes we should check the type of device that needs to be mounted, and if it's a block device, we should ignore this.
/cc @lifupan

Hi @sboeuf @mcastelino , Yes, I agree it. But before we do that, we need to figure out how to pass this block device as a container root to virtcontainer pkg, by container spec of any other method?

@lifupan

But before we do that, we need to figure out how to pass this block device as a container root to virtcontainer pkg, by container spec of any other method?

Could you elaborate on the reasons for this need?

@lifupan

But before we do that, we need to figure out how to pass this block device as a container root to virtcontainer pkg, by container spec of any other method?

Could you elaborate on the reasons for this need?

@lifupan we already pass the rootfs as a block device today. The only optimization we need to do is not the mount it on the host in the case of shim-v2


test reachability: make protocol on outer loop

I think this may effectively work around
https://github.com/istio/istio/issues/38982 by ensuring we don't send to
multiple ports in parallel anymore. Runtime and coverage should be the
same, only order changed.
Please provide a description of this PR:

/test all

/test all

@howardjohn: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name
Commit
Details
Required
Rerun command

integ-pilot-istiodremote-mc_istio
bff687401c0af6a394feae098cdb152efe90d695
link
unknown
/test integ-pilot-istiodremote-mc_istio

Instructions for interacting with me using PR comments are available here.  If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

/retest


Inheritance in simple usertypes doesn't work

There's problem with inheritance( or lack information about it in documentation) in simple_usertypes.
When using usertypes everything works fine, but when i'm using simple_usertypes, the program throws exception. If inheritance doesn't work with simple usertypes, then we need to add some warning/notice about it in inheritance section, because I couldn't find anything about it in documentation.
Reproduction code:
class A
{
public:
    virtual void a() = 0;
};

class B : public A
{
public:
    virtual void a() override { }
};

int main()
{
    sol::state state;
    state.new_simple_usertype<A>("A", "a", &A::a);
    state.new_simple_usertype<B>("B", sol::base_classes, sol::bases<A>());
    B* b = new B();
    state.set("b", b);
    state.script("b:a()");
}

From the docs, at the bottom of the inheritance portion of the usertype documentation:

Sol currently attempts to link base class methods and variables with their derived classes with an undocumented, unsupported feature

Emphasis mine, but maybe I should have an explicit separate note saying how unsupported and undocumented it really is. As it stands, the 'feature' is there because people continually expect it to be: I don't endorse it because the current way of using it has performance implications and the implementation itself is somewhat messy.
Also from the docs, in the same yellow exclamation [ ! ] warning bubble:

please specify all the base methods on the derived class in the method listing you write

I will also add a warning note to simple_usertype to make it more apparent how unsupported it is.

It is now explicit here, about inheritance (in the warning) and here, for simple_usertype.

So this bothered me a lot. In the end, I actually ended up working hard on the implementation and enabling inheritance, as well as actual properties / variables. The usual caveats no longer apply: http://sol2.readthedocs.io/en/latest/api/simple_usertype.html
Give it a try with the latest (v2.14.0), and let me know if it's satisfactory.

Everything works perfectly, thanks for the new update. Keep up the good work!

@ThePhD Hi, first of all thanks a lot for this great library, so useful. Second, regarding to your message:

So this bothered me a lot. In the end, I actually ended up working hard on the implementation and enabling inheritance, as well as actual properties / variables. The usual caveats no longer apply: http://sol2.readthedocs.io/en/latest/api/simple_usertype.html
Give it a try with the latest (v2.14.0), and let me know if it's satisfactory.

does it mean, we no longer need to specify base class member methods when registering derived class via new_usertype? I have tried the following, which works as I expected, but I just worried if there would be a runtime overhead issue?
my code:
new_usertype<widget>(
    "widget",
    "draw", &widget::draw,
    );

new_usertype<button>(
    "button",
    "draw", &button::draw,
    sol::base_classes, sol::bases<widget>()
    );

where "button" derived from "widget" with "draw" being the overloaded member function.
In summary, I wonder if my code is the best way of doing inheritance with sol?
Thank you in advance.


Updates after deploy 2022.11

This is messier than what I expected because by mistake we have been merging PRs to dev and master; sorry for the confusion.

Coverage decreased (-0.02%) to 92.902% when pulling 8a42cf75146f91de84194671d4d30af6e0269467 on antgonza:updates-after-deploy-2022.11 into c169c6bf919ca56cdbd073a14c66757a0a34488d on qiita-spots:dev.


Rollback queue refactoring

the defer is inside a loop that avoids the call to Done()

This change is

Coverage decreased (-0.02%) to 47.096% when pulling 7eee34f4737ad5f3108b54990e1ba3f4d5a171a9 on aledbf:update-client-go into b01dc68e30d935bc7845e40e85bc6b99ddb320a0 on kubernetes:master.


fix: ack timeout in  pulsar cpp client when subscribing to regex topic

Motivation
When subscribing to a regex in cpp/python client and using a message listener, ack timeout does work and unacked messages are not delivered.
This is because the unack message tracker is not call in one place

@merlimat i have added a test

rerun java8 tests

rerun java8 tests
rerun integration tests

rerun java8 tests

rerun java8 tests


⚠ Jenkins Plugins Artifactory has degraded performance

In 1360158, Jenkins Plugins Artifactory (https://get.jenkins.io/plugins/artifactory/) experienced degraded performance:

HTTP code: 200
Response time: 1328 ms

Resolved: Jenkins Plugins Artifactory performance has improved in 735e38f after 13 minutes.


lite: init at 1.03

Motivation for this change
Ultrafast editor written in Lua
Things done

[ ] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS linux)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[ ] Determined the impact on package closure size (by running nix path-info -S before and after)
[ ] Ensured that relevant documentation is up to date
[x] Fits CONTRIBUTING.md.

I'd just like to confirm that I've built this PR on my laptop and, as far as I can tell, lite works as intended.

Problem on darwin:
/nix/store/0np9zfyh5rq4kymr2ldqj5w2n82v1n30-stdenv-darwin/setup: line 1315: gcc: command not found

@GrahamcOfBorg build lite

darwin fixed in d90df25

Added @filalex77 as a maintainer as per https://github.com/NixOS/nixpkgs/pull/87589#issuecomment-626948757

@GrahamcOfBorg build lite

Successfully built and executed the package on NixOS and MacOS Catalina.
Note that the 1.03 version does not have correct scaling on MacOS. This comment thread in the lite repo indicates that supporting MacOS is probably not within the scope of the rxi/lite repo. Maybe setting platforms = platforms.linux; until MacOS support is confirmed would be advisable.

@GrahamcOfBorg build lite

@GrahamcOfBorg build lite


v2.0: Change global working directory on opening/saving files

From<EMAIL_ADDRESS>on 2010-10-26T02:35:31Z
Hi,
could you please add an option to the preference, to enable/disable the following two rules:

when opening a file, set its path as the global working directory
(e.g. open c:\temp\test\main.py => automatically switch to c:\temp\test\ as working directory)
when saving a file, set its path as the global working directory
There could an extra rule to automate the "set as current console's working directory"

when changing the global working directory, the working directory of the consoles are changed, too.
but don't delete the button from the GUI

I'm really missing at least feature 1/2 maybe feature 3 is not that important.
Original issue: http://code.google.com/p/spyderlib/issues/detail?id=428

From<EMAIL_ADDRESS>on 2010-10-26T00:35:53Z
By the way, really great work! :)

From pierre.raybaut on 2010-10-26T04:26:39Z
Summary: v2.0: Change global working directory on opening/saving files
Status: Accepted
Labels: -Type-Defect Type-Enhancement Milestone-Release2.0

From pierre.raybaut on 2011-04-24T07:36:26Z
This issue was closed by revision 001efddfe13f .

From pierre.raybaut on 2010-10-26T09:58:58Z
This issue was closed by revision 001efddfe1 .
Status: Fixed


⚠ Bofrost.at has degraded performance

In f7112cd, Bofrost.at (https://www.bofrost.at) experienced degraded performance:

HTTP code: 200
Response time: 1289 ms

Resolved: Bofrost.at performance has improved in a907ddf.


Feature: Enable PMTile protocol support

@mapcomponents/react-maplibre version:
Feature description
PMTile vector sources can be rendered
Example
<MlPMTileLayer or MlVectorTileLayer
Summary
For react devs using maplibre your library is a clear win, however some of us are using pmtile files and its not super intuitive to add a new protocol just yet

In my opinion the useAddProtocol hook provides the required functionality to work well with the pmtiles package.
We are using pmtiles too in our MapComponents application.
iirc there have been some issues with Github pages (where all the examples are hosted) and byte range requests, which are required for pmtiles to work.
The example from pmtiles can be easily adapted to work with MapComponents though.
https://github.com/protomaps/PMTiles/blob/main/js/examples/maplibre.html
`
// This line should be outside of your react component
let protocol = new pmtiles.Protocol();
// This line inside your react component
useAddProtocol({
protocol: 'pmtiles',
handler: protocol.tile
});
// In the JSX
<MlVectorTileLayer url={'pmtiles://https://URL_TO_YOUR_PMTILES'} />
`
If you provide an example that is not working now, we can take a look at it.

Thanks very much for the help!  Your example is very straight forward, but I don't see to be able to get it to work.  If you checkout https://github.com/bcgov/WetpaddlersV2/tree/issue_example that branch, and cd && app && nvm use 20 && npm install && npm run dev you can run the app and you should see some blue circles on the west coast of North America (BC to be more specific).  The commented out 'old way' of adding the PMTile layer is in a hook near the top of the file.

I have created a pull request for your repo that fixes the implementation.
PMTiles URL was missing ZXY placeholders. I have now also added them in the example above.

Thank you again for the help and insight!


exiftool: 10.80 -> 11.01

https://sno.phy.queensu.ca/~phil/exiftool/history.html
Things done

[x] Tested using sandboxing (nix.useSandbox on NixOS, or option sandbox in nix.conf on non-NixOS)
Built on platform(s)

[x] NixOS
[ ] macOS
[ ] other Linux distributions

[ ] Tested via one or more NixOS test(s) if existing and applicable for the change (look inside nixos/tests)
[ ] Tested compilation of all pkgs that depend on this change using nix-shell -p nox --run "nox-review wip"
[x] Tested execution of all binary files (usually in ./result/bin/)
[x] Determined the impact on package closure size (by running nix path-info -S before and after)
[x] Fits CONTRIBUTING.md.

Let's check the darwin build:
@GrahamcOfBorg build exiftool

Success on aarch64-linux (full log)
Attempted: exiftool
Partial log (click to expand)
/nix/store/qvx2kck8scnw2j3z52n8l7mqfy5yxpab-perl-Image-ExifTool-11.01

Success on x86_64-linux (full log)
Attempted: exiftool
Partial log (click to expand)
/nix/store/sggf1hydlhnwvr0n1kqm539k4g9bxv3n-perl-Image-ExifTool-11.01

Success on x86_64-darwin (full log)
Attempted: exiftool
Partial log (click to expand)
Moving /nix/store/3hpqz7ikqzdqr5hklnmdmbcvniyhyg8x-perl-Image-ExifTool-11.01/share/man/man3 to /nix/store/4iza3pqi0gbs0z8sr3h5z14lxf82n0nq-perl-Image-ExifTool-11.01-devdoc/share/man/man3
rmdir: failed to remove '/nix/store/3hpqz7ikqzdqr5hklnmdmbcvniyhyg8x-perl-Image-ExifTool-11.01/share/man': Directory not empty
gzipping man pages under /nix/store/3hpqz7ikqzdqr5hklnmdmbcvniyhyg8x-perl-Image-ExifTool-11.01/share/man/
strip is /nix/store/7ddbq63v97nk8gkbf7gcsfmby37h6gbl-cctools-binutils-darwin/bin/strip
stripping (with command strip and flags -S) in /nix/store/3hpqz7ikqzdqr5hklnmdmbcvniyhyg8x-perl-Image-ExifTool-11.01/lib  /nix/store/3hpqz7ikqzdqr5hklnmdmbcvniyhyg8x-perl-Image-ExifTool-11.01/bin
patching script interpreter paths in /nix/store/3hpqz7ikqzdqr5hklnmdmbcvniyhyg8x-perl-Image-ExifTool-11.01
gzipping man pages under /nix/store/4iza3pqi0gbs0z8sr3h5z14lxf82n0nq-perl-Image-ExifTool-11.01-devdoc/share/man/
strip is /nix/store/7ddbq63v97nk8gkbf7gcsfmby37h6gbl-cctools-binutils-darwin/bin/strip
patching script interpreter paths in /nix/store/4iza3pqi0gbs0z8sr3h5z14lxf82n0nq-perl-Image-ExifTool-11.01-devdoc
/nix/store/3hpqz7ikqzdqr5hklnmdmbcvniyhyg8x-perl-Image-ExifTool-11.01


[ZAP]: Allow specify the the length constraint of a list

Problem
Now we can specify 'list' type using "ARRAY" in a Attribute or Command definition:
groups
But the length here is the maximum allowed bytes of each entryType. We need to have a way to specify the maximum element of the list defined by the CHIP spec
Proposed Solution
Allow specify the the length constraint of a list

https://github.com/project-chip/zap/issues/151

I've moved all the "chip_zap_support" labeled bugs into the zap repo itself under https://github.com/project-chip/zap/issues
I propose that we delete the chip_zap_support label, and all the bugs in this repo, and in the future simply open the issues in the zap repo itself, since it's much easier to keep track.
But given that I'm not sure how this repo is tracking "dependent issues" it's not my call.


Add isNotch()

Description
Fixed issue #427

Added isNotch() that returns a boolean if the device has a notch.
Compatibility

OS
Implemented

iOS
✅❌

Android
✅❌

Windows
✅❌

Checklist

[x] I have tested this on a device/simulator for each compatible OS
[x] I added the documentation in README.md.
[ ] I mentionned this change in CHANGELOG.md.

@ddobby94 is it possible on these devices to disable/enable the notch? If so, do you think it's something we can detect at runtime?

@diegolmello Thank you for this PR. Maybe we could name this hasNotch() instead? 🤔

please merge 😄

@diegolmello could you add those Android devices before I merge?  :pray:

@machour Done! 👍

Just published 0.23.0 with hasNotch()
Thank you @diegolmello & @ddobby94


Add grad_scale parameter for RegressionOutput

Add grad_scale parameter for RegressionOutput
Fix grad_scale in SoftmaxOutput. Currently, when grad_scale is > 1.0, it will be igonored.

Thanks for the contribution. Will merge after test finishes

Thanks for the contribution, have add you to https://github.com/dmlc/mxnet/blob/master/CONTRIBUTORS.md
Please feel free to send updates on your information


Update and rename 0000-template.md to 0067-MCC_Reconstruction.md

Hi, closing as a duplicate of #439 since these look functionally identical? please re-open if not


is there a change to what the create_project method returns -- I'm getting None back for the project dictionary.

I'm running my test code again after a month or so and I find that this code:
try:
print ("try to make a project")
proj_dict = dd_client.create_project(files=query_files, query=thequery, idle_timeout=259201)
print ("project creation succeeded",query_files,thequery)
except:
print ("project creation failed")

if debug: print("project dictionary",proj_dict)
succeeds but prints out:
create_project with 10  files
try to make a project
project creation succeeded 10 files from schellma:rawPhysics_5141_5143 ordered skip 10 limit 10
project dictionary None
so valid list of files and query, no exception but no response.
THanks, Heidi

I think I fixed it.
Please try and let me know

Works now…
On Sep 22, 2023, at 5:21 AM, Igor Mandrichenko @.***> wrote:
[This email originated from outside of OSU. Use caution with links and attachments.]
I think I fixed it.
Please try and let me know
—
Reply to this email directly, view it on GitHubhttps://github.com/ivmfnal/data_dispatcher/issues/22#issuecomment-1731323438, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIA37DIBIEK7NL4BACXHMSTX3V7C3ANCNFSM6AAAAAA5CIBDG4.
You are receiving this because you authored the thread.Message ID: @.***>

I did get a strange error at the end of a project which I think was trying to read files frmo tape but that did fix the original issue.  More checks for me to do.
On Sep 22, 2023, at 7:09 AM, Igor Mandrichenko @.***> wrote:
[This email originated from outside of OSU. Use caution with links and attachments.]
Closed #22https://github.com/ivmfnal/data_dispatcher/issues/22 as completed.
—
Reply to this email directly, view it on GitHubhttps://github.com/ivmfnal/data_dispatcher/issues/22#event-10447916221, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIA37DIT3NI7CONWZJAL4W3X3WL25ANCNFSM6AAAAAA5CIBDG4.
You are receiving this because you authored the thread.Message ID: @.***>

What was the error ?

Replica availability information is not updated in real time. So initially replicas are always not found until DD polls Rucio next time

Any way to get it to behave better, like wait?  having the job check, fail to find anything and then fail to do anything seems non-optimal.
On Sep 22, 2023, at 8:26 AM, Igor Mandrichenko @.***> wrote:
[This email originated from outside of OSU. Use caution with links and attachments.]
Replica availability information is not updated in real time. So initially replicas are always not found until DD polls Rucio next time
—
Reply to this email directly, view it on GitHubhttps://github.com/ivmfnal/data_dispatcher/issues/22#issuecomment-1731611651, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIA37DPW55HRYS757743LX3X3WU3BANCNFSM6AAAAAA5CIBDG4.
You are receiving this because you authored the thread.Message ID: @.***>

I am not sure what you mean.
The worker is supposed to issue "next file" and wait for a replica to become available.
Are you doing something else ?

May be missing that step.  this is based on Jake’s work almost a year ago.  right now it is asking for list of replicas and due to the design of larsoft was passing the list of locations to the executable.
On Sep 22, 2023, at 8:53 AM, Igor Mandrichenko @.***> wrote:
[This email originated from outside of OSU. Use caution with links and attachments.]
I am not sure what you mean.
The worker is supposed to issue "next file" and wait for a replica to become available.
Are you doing something else ?
—
Reply to this email directly, view it on GitHubhttps://github.com/ivmfnal/data_dispatcher/issues/22#issuecomment-1731653790, or unsubscribehttps://github.com/notifications/unsubscribe-auth/AIA37DJCJSAJITEHYNSBLL3X3WYAFANCNFSM6AAAAAA5CIBDG4.
You are receiving this because you authored the thread.Message ID: @.***>

This is absolutely not right


add batch presigned api

Our project need batch PresignedGetObject and PresignedPutObject api, but minio-go has not provide those apis, so I change the api-presigned.go file.

Because we need to put a few objects sometimes.
And mobile or web gets object through urls.

Yes but you should do this outside. This API is not meaningful IMO - APIs need to be primitives. The API proposed is not a primitive.
We shouldn't move application logic into minio-go.

OK,I know that. But can minio-go provide batch PresignedPutObject and PresignedGetObject api ?

That is exactly what I meant batch API is not an expected behavior. It should be done outside in the application.
PreSign is a Primitive which requires a bucket and an object. Look at how mc an application generates presigned URLs using the same API for many objects. By simply iterating over ListObjects response.

Closing this as not required


Add integration tests for user-registrants retrieval endpoint

This PR adds integration tests for the user-registrants retrieval endpoint in the application management API.
The API layer changes were introduced with https://github.com/wso2/identity-api-server/pull/417
The BE improvements were introduced with https://github.com/wso2-extensions/identity-governance/pull/663

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/4312704010

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/4312704010
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/4351180638

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/4351180638
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/4353702342

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/4353702342
Status: failure

PR builder started
Link: https://github.com/wso2/product-is/actions/runs/4362219772

PR builder completed
Link: https://github.com/wso2/product-is/actions/runs/4362219772
Status: success


feat(publisher): remove application when is stopped

The reason of /deis/publisher/containers/<id container> -> <app name>/<app type instance> is required because in the docker stop event only the id of the stopped container is available.
closes #3176

Personally I'd rather keep the IDs in an in-memory map as it's a lot faster and more reliable to access than etcd. We fall back with TTLs so it's not a huge concern if the process is restarted, losing the map's data.

Personally I'd rather keep the IDs in an in-memory map

that was my first approach but I thought use etcd like in the rest of the services :)
I will change this

code LGTM!

That's great cleanup code, thanks @aledbf. Code LGTM, but this needs a manual test after CI.

Jenkins, test this please.

Jenkins, test this please.

Jenkins, test this please.

Jenkins, test this please.

Note that this passed testing, although the way that GitHub test statuses stack now doesn't reflect that on the summary page with a green :white_check_mark:

I tested this interactively on vagrant. LGTM.


I have installed SDK, I have cloned the project from github still I'm getting error.

/Users/{Home}/Library/Developer/Xcode/DerivedData/arcgis-ios-sdk-samples-evftpkeyioizojaenycmfrtwgnln/Build/Products/Debug-iphonesimulator/arcgis-ios-sdk-samples.app/ArcGIS.bundle/Directions/NA Campus/pl.json: No such file or directory

@harshchitrla What version of the SDK are you using?

I'm using ArcGIS_Runtime_SDK_iOS_100_0_0 .
On Tue, Dec 20, 2016 at 4:01 AM, Gagandeep Singh<EMAIL_ADDRESS>wrote:

@harshchitrla https://github.com/harshchitrla What version of the SDK
are you using?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/Esri/arcgis-runtime-samples-ios/issues/237#issuecomment-268098001,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFPv-uAin8apwVlxzLFLs8fExJgSukAmks5rJwXHgaJpZM4LO3tR
.

Did you try clearing your derived data folder? If not follow the instructions on this post. Please close Xcode before deleting the folders inside derived data folder.

Closing. If this is still a problem, please open a new issue.


[SPARK-14812][ML][MLLIB][PYTHON] Experimental, DeveloperApi annotation audit for ML

What changes were proposed in this pull request?
General decisions to follow, except where noted:

spark.mllib, pyspark.mllib: Remove all Experimental annotations.  Leave DeveloperApi annotations alone.
spark.ml, pyspark.ml
** Annotate Estimator-Model pairs of classes and companion objects the same way.
** For all algorithms marked Experimental with Since tag <= 1.6, remove Experimental annotation.
** For all algorithms marked Experimental with Since tag = 2.0, leave Experimental annotation.
DeveloperApi annotations are left alone, except where noted.
No changes to which types are sealed.

Exceptions where I am leaving items Experimental in spark.ml, pyspark.ml, mainly because the items are new:

Model Summary classes
MLWriter, MLReader, MLWritable, MLReadable
Evaluator and subclasses: There is discussion of changes around evaluating multiple metrics at once for efficiency.
RFormula: Its behavior may need to change slightly to match R in edge cases.
AFTSurvivalRegression
MultilayerPerceptronClassifier

DeveloperApi changes:

ml.tree.Node, ml.tree.Split, and subclasses should no longer be DeveloperApi

How was this patch tested?
N/A
Note to reviewers:

spark.ml.clustering.LDA underwent significant changes (additional methods), so let me know if you want me to leave it Experimental.
Be careful to check for cases where a class should no longer be Experimental but has an Experimental method, val, or other feature.  I did not find such cases, but please verify.

Test build #62132 has started for PR 14147 at commit f86ea5a.

Test build #62132 has finished for PR 14147 at commit f86ea5a.

This patch fails Scala style tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62132/
Test FAILed.

CC: @MLnick @yanboliang If you have a chance

Test build #62184 has started for PR 14147 at commit 5bd0d38.

Test build #62184 has finished for PR 14147 at commit 5bd0d38.

This patch fails to build.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test FAILed.

Test FAILed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62184/
Test FAILed.

Test build #62193 has started for PR 14147 at commit 8f5fb63.

Test build #62193 has finished for PR 14147 at commit 8f5fb63.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62193/
Test PASSed.

@jkbradley I'd like to leave ml.clustering.LDA Experimental, since we did significant changes in this release cycle. Other than that, this looks great. Thanks!

@yanboliang Thanks for taking a look!  I reverted the LDA changes for spark.ml.

Test build #62266 has started for PR 14147 at commit b57f398.

Test build #62266 has finished for PR 14147 at commit b57f398.

This patch passes all tests.
This patch merges cleanly.
This patch adds no public classes.

Merged build finished. Test PASSed.

Test PASSed.
Refer to this link for build results (access rights to CI server needed):
https://amplab.cs.berkeley.edu/jenkins//job/SparkPullRequestBuilder/62266/
Test PASSed.

Merging with master and branch-2.0


Liberty Installl AIO one NIc

I install  an AIO build in one step on server one Nic with IP 217.79.181.xx
but VM do not access internet. How do i setup it working?
thank

Thank you for contributing to openstack/openstack-ansible!
openstack/openstack-ansible uses Gerrit for code review.
If you have never contributed to OpenStack before make sure you have read the
getting started documentation:
http://docs.openstack.org/infra/manual/developers.html#getting-started
Otherwise please visit
http://docs.openstack.org/infra/manual/developers.html#development-workflow
and follow the instructions there to upload your change to Gerrit.

Thank you for contributing to openstack/openstack-ansible!
openstack/openstack-ansible uses Gerrit for code review.
If you have never contributed to OpenStack before make sure you have read the
getting started documentation:
http://docs.openstack.org/infra/manual/developers.html#getting-started
Otherwise please visit
http://docs.openstack.org/infra/manual/developers.html#development-workflow
and follow the instructions there to upload your change to Gerrit.


add mod file

go modules will be enabled in 1.13
go mod tidy was also run to include required dependencies

if you would like to only consume valid releases, this can block on:

[ ] bradfitz/gomemcache#94
[ ] peterbourgon/diskv#52 or peterbourgon/diskv#53

this will remove all // indirect dependencies
this could also be done later

after merge it would be nice if you would tag this repo: e.g. v1.0.0

this will allow consumers something more consistent and readable than v0.0.0-20181229203832-0af3f3b09a0a

@gregjones, sorry to pester, but I would rather close out this pr if you are not yet interested in merging module support at this time.


N26: good-web-game

Part of #783

Cool logo, btw!

Cool logo, btw!

Thanks! :D

Could you please remove some non-essential information?

Will do.

I didn't count the words, but I think it's short enough now, right?
I'm content with it now.

Merged, thanks for the PR!


feat: add region proxying to actor client

Fixes RVT-4326
Fixes RVT-4327
Changes

[!WARNING]
This pull request is not mergeable via GitHub because a downstack PR is open. Once all requirements are satisfied, merge this PR as a stack on Graphite.
Learn more

#1540  👈 (View in Graphite)
#1538
#1535 : 1 other dependent PR (#1539 )
main

This stack of pull requests is managed by Graphite. Learn more about stacking.

@NathanFlurry still have to publish the npm package


Replace deprecated RabbitMQ SSL environment variables with configuration file (#5599)

This PR enables configuring RabbitMQ SSL for RabbitMQ 3.9+ versions. Until 3.9, SSL could be configured by environment variables. These variables were deprecated in RabbitMQ 3.9 version. If defined, the broker is generating an error on startup.
We solved this issue by adding an additional advanced configuration file that is merged with the default configuration file included in the Docker image. We chose this solution because the advanced configuration is not configured using Testcontainers DSL and it doesn't interfere with the optional configuration added with withRabbitMQConfig method.
Co-authored-by: Joan Fisbein<EMAIL_ADDRESS>Co-authored-by: Marcin Gryszko<EMAIL_ADDRESS>On-behalf-of: @clarityai-eng<EMAIL_ADDRESS>Fixes #5599

@mgryszko any update on this?

@jgiovaresco feel free to make a proposal. If you'd like to discuss it then openning a GH Discussion would be ok then we can turn it into an issue. If you have the PR ready then we can discuss it there too.
I'm closing this one looking after the new PR.


Use YAML.safe_load to avoid possible code execution

It's better to use safe_load to avoid a situation where a crafted yaml could execute code when parsing.

OS X comes with ruby 2.0 and psych 2.0. Installing newer version of the gem builds native extension:
$ sudo gem install psych
Password:
Fetching: psych-2.2.2.gem (100%)
Building native extensions.  This could take a while...
Successfully installed psych-2.2.2
Parsing documentation for psych-2.2.2
unable to convert "\xCA" from ASCII-8BIT to UTF-8 for lib/psych.bundle, skipping
Installing ri documentation for psych-2.2.2
1 gem installed

I think we should also search for alternative solutions.

There's also this: https://github.com/dtao/safe_yaml

#1573 is better.