Update to add yaml support

Initial pull request to add support for flags to get values from yaml files. Still some work to do to get this working on older versions of go. Open to review comments.

I attempted to add build constraints to the file that has yaml dependencies, but its not working yet. Hopefully this will be ok. Took a survey of yaml files and all of them use the encoding package which isn't in go version 1.0 and 1.1.

Thank you for putting this together @ChrisPRobinson! I'm still trying to find a solid block of time to give this the review it deserves, but I haven't forgotten it.
I think not supporting this feature in Go 1.0 and 1.1 is OK though.

@jszwedko: Sounds good. Can't wait for the review.
I think one area that likely has a bug is requesting for a GenericValue from a yaml source, this likely doesn't work. I'm not sure what the correct scenario is there, on how to decode the yaml value. So I kind of passed on figuring it out.
The other likely issue is with errors. How should I report them when there is a conversion error as an example? Just thought I'd point those out ahead of time.

@ChrisPRobinson I regret putting this review off for so long, I was intimidated by the SLOC, but this is really well written and easy to follow. I like that you implemented it in an extensible fashion (and provided two initial implementations), this should make it easy to add an INI loader for example.
I agree with you regarding errors -- it looks like conversion errors are only correctly handled in this library when parsed from a flag (via flagset.Parse). See https://github.com/codegangsta/cli/blob/master/flag.go#L299-L305 for example where if the value can't be parsed as a boolean it is just ignored. This pattern is repeated for the other types. It feels like cli.Flag.Apply should also be able to return an error, but this would break the current API -- I'll note for that`.
In your specific case, it seems like you should be able to have the ApplyInputSourceValue interface function have error in its return signature and bubble up the errors from https://github.com/codegangsta/cli/pull/306/files#diff-09e57851363e51591d63294f8e7ebd00R38. You'd also want to have all of the methods on InputSourceContext be able to return error. Unless I'm missing something.
For the generic flag it feels like you shouldn't do any type checking here: https://github.com/codegangsta/cli/pull/306/files#diff-e3d69d75afd9528121339b5ce88daa8dR99 and just return whatever the value is, letting https://github.com/codegangsta/cli/pull/306/files#diff-c614971d7e599304e5f08cbf7fcdff45R39 pass it along to .Set which should call the method they defined to unmarshal the value. Come to think of it, it feels like we could delegate all of the type marshalling to the flag library and just have the YAML file loader return everything as a string.
Thank you again for taking the time to put this together! I'll be much more active around this until we get it merged in.

@jszwedko - Sounds good, I'll work on getting those changes in and updated. Thanks for the review and comments.

@jszwedko - made the updates you pointed out, one more step to possible completion.

Awesome @ChrisPRobinson -- this looks great!
Let me know if there is any more touch-ups that you wanted to do, but otherwise I think the only remaining piece is an update to the README.

@jszwedko - Yes the README needs updating, updated it.
I think there is one thing that definitely needs to be fixed. I put all of the other packages in "inputfilesource". Looking at this now I don't like this name. Technically speaking the interface allows data to come from really anything not just a file. I think I should switch this to "altinputsource" or perhaps "altsrc"? Let me know what you think there.
The other thing I'm concerned about is the patterns for the InputSourceContext initialization patterns. Right now I implemented one func for the yaml one, but what about the case where the file name is always hardcoded and not pulled from a context variable. Also would we want each alternate directory/package for each alternate input source?

@jszwedko - I made a couple of updates, I change the package name to altsrc for alternate source context. I also tweaked the yaml source context and made two new functions that are used to create the source. One where a file is provided directly. Another that uses the cli.Context to get a file name and then  creates the source.
I then made two general functions that can be used for any input source context to load them for the Before method. The idea is that people implementing new sources can just create the required New funcs for their Input source. Then it integrates with the existing common code path that was used for the yaml one. Maybe I should have done this as a separate commit so you could see the difference rather than squashing them.
The readme is updated with samples

:+1: I agree that altsrc is a better package name and the rest of these changes seem sane. Thank you for updating the README too!
Looks like there is a build failure for Go 1.0 -- I'm also ok with just dropping 1.0 support.

@jszwedko - Good, glad you like the changes. I did attempt to optionally compile it for go 1.0 but it worked for go 1.1 but not go 1.2. Let me know if any other changes are required.

This looks great @ChrisPRobinson, thank you again! I'll merge and drop support for Go 1.0 as I don't see a compelling reason to continue that support.

@jszwedko Awesome, glad to help!


Add heroku topic

Thank you for contributing! Please confirm this pull request meets the following requirements:

[x] I followed the contributing guidelines: https://github.com/github/explore/blob/master/CONTRIBUTING.md
[x] I have no affiliation with the project I am suggesting (as a maintainer, creator, contractor, or employee).

Which change are you proposing?

[ ] Suggesting edits to an existing topic or collection
[x] Curating a new topic or collection
[ ] Something that does not neatly fit into the binary options above

Editing an existing topic or collection
I'm suggesting these edits to an existing topic or collection:

[ ] Image (and my file is *.png, square, dimensions 288x288)
[ ] Content (and my changes are in index.md)

Please replace this line with an explanation of why you think these changes should be made.

Curating a new topic or collection

[x] I've formatted my changes as a new folder directory, named for the topic or collection as it appears in the URL on GitHub (e.g. https://github.com/topics/[NAME] or https://github.com/collections/[NAME])
[x] My folder contains a *.png image (if applicable) and index.md
[x] All required fields in my index.md conform to the Style Guide and API docs: https://github.com/github/explore/tree/master/docs

All popular PaaS services are created as topics and GitHub contains lots of repositories containing this topic which would be available to more users if Heroku is made an official GitHub topic.

Something that does not neatly fit into the binary options above

[ ] My suggested edits are not about an existing topic or collection, or at least not a single one
[ ] My suggested edits are not about curating a new topic or collection, or at least not a single one
[ ] My suggested edits conform to the Style Guide and API docs: https://github.com/github/explore/tree/master/docs

Please replace this line with an explanation of your proposed changes.

Please note: we will close your PR without comment if you do not check the boxes above and provide ALL requested information.

Hello @MikeMcQuaid,
can you review my PR?

Thanks so much for your first contribution and sorry for the delay!  You rock, @parshnt!


Library versioning

https://github.com/cms-cat/cmsstyle/blob/master/pyproject.toml#L7 points to src/cmsstyle/_version.py but that file doesn't exist. Should it be created and then we need to run a script (bump version) whenever we want to update?

Assigning @andrzejnovak since he setup the full PyPi workflow

@clelange the file gets created in the release action automatically based on the release/tag name
Check https://pypi.org/project/cmsstyle/#history


ENH: stats.ansari: add axis / nan_policy / keepdims support

@tirthasheshpatel Shall I also submit a PRs that you can review, about one per week, or is that too much?
I'll wait for SciPy's CI to get fixed before opening this one on the main repo.
I think it's really as simple as this. The one thing I noticed is that currently, for Nd input, ansari returns a scalar result. However, the result seems to be garbage - it's different from axis=None / raveling the arrays before passing them to the function. So I think it's safe to let axis=0 be the default since there's no useful behavior to maintain.

Shall I also submit a PRs that you can review, about one per week, or is that too much?

Feel free to take some! Once per week sounds good.


PhotinoWindow does not show characters properly in Title

PhotinoWindow does not show characters properly in Title when use Chinese characters,
But it works well in previous version
      app.MainWindow
          .SetIconFile("favicon.ico")
          .SetTitle("测试");

@hejiajun107 Thanks for finding that. Apparently, it's only a problem on Windows. We found and fixed the issue and it will be in the next release.


Fixed #32114 -- Subtest pickle issue with ParallelTestRunner

Ticket: https://code.djangoproject.com/ticket/32114
Summary
When a subtest fails during a parallel test run, it gets pickled and
sent back to the main thread to be added to the RemoteTestResult.
The issue is that the entire TestCase needs to be pickleable. Often
it is not, in which case the original error message  is never displayed to
the user. Instead of trying to pickle the entire TestCase, which can contain
all sorts of weird and unexpected things, we can restrict  the pickled fields
to a subset of the original (basically just the stuff that unittest.TestCase
declares as part of the public API, plus _subDescription which is from
unittest._SubTest).
Further thoughts
This could be opt-in (or out) via a setting, as it's possible some users use customized
TestRunners that rely on accessing private fields of the TestCase. I've confirmed that
this works in PyCharm (which uses a modified TestRunner based on Django's
DiscoverRunner), but can't rule out the possibility that other tools might rely on
private/undocumented behavior.
We could also do something smarter in TestCaseDTO, like try to dynamically determine
which fields are pickelable and only copy those. This could potentially be more robust, but
also comes with extra cognitive overhead (and could have some negative performance
implications).

Out of curiosity have we considered adjusting SimpleTestCase.__setstate__ and .__getstate__ to drop unpickle objects instead?

have we considered adjusting SimpleTestCase.__setstate__ and .__getstate__ to drop unpickle able objects instead?

Maybe that is a better approach. The PR as it stands right now is more or less how I patched this in our codebase at work, but that was motivated somewhat by a desire to keep the diff small (overriding addSubTest vs adding a new base class for hundreds of TestCases).
Let me play around with __getstate__/__setstate__ on SimpleTestCase and I'll report back.

@JEphron Do you have time to keep working on this?

Closing due to lack of follow up.


Bringing Modals into alignment with UX rules

PR Checklist
Check these before submitting your pull request:

[ ] Visual and behavioral components are separated
[ ] Exported components are documented with examples
[ ] Props have JSDoc comments
[ ] All relevant visual sub-components can be overridden via props
[ ] Any extra props are spread into the outermost rendered element

Breaking Changes

Describe all breaking changes here

Changes to Existing Components

Describe meaningful changes to existing components here

removed title callout that would appear on hover on modal elements
removed padding on action content to extend seperation line to full length of modal.
Added 30px padding to button container to preserve correct spacing.
Added border rounding to title-top-left and title-top-right.

New Visual Components

List and describe any new visual components (styled-component primitives) here. Visual components which are sub-components of exported components must be contained in a /styles directory adjacent to their super-component

New Behavioral Components

List and describe behavioral components here. Behavioral components must have no associated styling. If styling is necessary, refactor styled elements into visual components and ensure they can be overridden via props.

@braxtonCoats Can you include a screenshot that shows what it looks like now?

added a screen of what it looks like. Note the title="" removes a callout that appears when a modal element (say button) is hovered.


Documentation Reference to .dylib files in MacOS for liboqs

After compiling liboqs on MacOS, i could not find a location for a liboqs.so, only a .dylib.
After changing the Environment to look for liboqs.dylib instead of liboqs.so, the tests ran fine.
Suggest change of documentation to reference dylib (if this is just a Mac thing) or generally to .dylib if this has been a change over last merge.
More than happy to provide a PR.

Hi Ryan! .dylib is a macOS thing, .so is Linux. So yes our documentation should reference both of them. A PR would be great!


 should extend HTMLButtonElement

As Eric Bidelman noted, "There's no better way to write a progressive web app than to progressively enhance existing HTML elements." [1]
Where possible, buttons and other custom elements should extend native HTML elements "to gain all of its features (DOM properties, methods, accessibility)". [1]
[1] https://developers.google.com/web/fundamentals/web-components/customelements#extendhtml

Agreed, where possible, native elements should be used. See Agreed :) See 7ca365291863f310c5006a01ec3029c62a485a6b

Unfortunately there's a lot of contention around extending built-in elements with some browsers stating that they will "never" support it. Even libraries like Polymer are dropping support (in the near term) to see if we can find consensus on a different solution. For these reasons we've chosen to not do customized built-ins on this project and we're going to be updating the docs wherever possible to indicate when using a native element would be preferable. This is a good issue because it reminds me we should add a similar warning to the toggle button.

Awesome! Thanks, Rob and Surma. I figured you had a good reason for not extending HTMLButtonElement. :-)
A warning would be helpful. Thanks for the explanation.

I changed the title of this issue and I'm reopening so we can go back and add this explanation to the docs.


Norwich 2 Slot updates

Description

Motivation and Context

Types of changes

[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[ ] Breaking change (fix or feature that would cause existing functionality to change)
[x] Prison details update (e.g. slot updates)

Checklist:

[ ] My commit message follows the GDS git style standards we have adopted.
[ ] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
[x] I have updated the deployment repo accordingly.
[ ] I have added tests to cover my changes.

The Pull Request relates to Norwich prisons wanting to block out days for the festive period.


We assume all the images have the same size!!!

Dear @prismformore
I am running inference file based on single image downloaded from the internet. Also, I successfully installed all libraries without downloading Cityscapes dataset because I do not want to train a model.
CUDA_VISIBLE_DEVICES=0 python3 inference.py --config_path=configs/pascal/pascal_vitLp16_taskprompter.yml --image_path=fff.jpeg --ckp_path=TaskPrompter_pascal_vitLp16.pth.tar --save_dir=output
Input

Traceback
/home/cvpr/anaconda3/envs/ICCV2023/lib/python3.7/site-packages/torch/nn/functional.py:3635: UserWarning: Default upsampling behavior when mode=bilinear is changed to align_corners=False since 0.4.0. Please specify align_corners=True if the old behavior is desired. See the documentation of nn.Upsample for details.
  "See the documentation of nn.Upsample for details.".format(mode)
/media/cvpr/CM_24/Multi-Task-Transformer/TaskPrompter/utils/visualization_utils.py:122: UserWarning: Warning: We assume all the images have the same size!!!
  warnings.warn('Warning: We assume all the images have the same size!!!')

@khawar-islam Hi, this is just a warning. Did you get any error?
Please also check the discussion here for visualization of 3D detection results on Internet images. Normally the model only works with those using camera parameters of Cityscapes stuttgart split here.


Duplicate regions

Add the possibility to import content from other regions when creating a new region.
The duplication process of the language tree and the pages was a bit tricky because they both have the tree structure and the parents have to be adjusted as well. I solved this with a recursive function which I tried to document a bit more detailed than usually.
Fixes #43
Other implicit changes of this PR:

Fixed a small bug of the page-status in the test data
Fixed the CSRF handler (we had still the old view in the settings)

Sorry, I fixed the pylint error now. The PR is ready for review :wink:


Websocket client does not send payload data to WEBSOCKET_EVENT_CLOSED event handler (IDFGH-4729)

Environment

Development Kit: ESP32-Wrover-Kit
Module or chip used: ESP32-WROOM-32
IDF version: ESP-IDF v4.4-dev-4-g73db14240-dirty
Build System: idf.py
Compiler version: 8.4.0
Operating System: Linux
Power Supply: USB

Problem Description
I'm using esp_websocket_client to communicate with websocket server. I have registered websocket event handler with esp_websocket_register_events and everything works awesome. In event handler I'm receiving instance of esp_websocket_event_data_t struct, and on WEBSOCKET_EVENT_DATA event I can read received websocket frame data. But, problem is when the server close connection (cleanly - op_code 8) with some data in websocket frame, event  WEBSOCKET_EVENT_CLOSED has been invoked, but I do not have access to the received data because data_len property of received esp_websocket_event_data_t is set to zero, and data_ptr is NULL.
As you can see in this line, websocket client dispatch the WEBSOCKET_EVENT_CLOSED event with data set to NULL and data_len set to zero:
https://github.com/espressif/esp-idf/blob/73db142403c6e5b763a0e1c07312200e9b622673/components/esp_websocket_client/esp_websocket_client.c#L701
Expected Behavior
It would be nice to have access to websocket frame data in WEBSOCKET_EVENT_CLOSED event, because my websocket server send more details about closing reason in frame data.
Code to reproduce this issue
static void gw_websocket_event_handler(void* handler_arg, esp_event_base_t base, int32_t event_id, void* event_data) {
    esp_websocket_event_data_t* data = (esp_websocket_event_data_t*) event_data;

    switch (event_id) {
        case WEBSOCKET_EVENT_CLOSED:
            ESP_LOGD(TAG, "WEBSOCKET_EVENT_CLOSED (WS_OP: %d, payload_len=%d, data_len=%d)", data->op_code, data->payload_len, data->data_len);
            break;
    }
}

Debug Logs
D (6811) application: WEBSOCKET_EVENT_CLOSED (WS_OP: 8, payload_len=24, data_len=0)

Hi @david-cermak @ESP-Marius  sorry for tag but I see that you are most active recently on ws_client. Just want to ask you what do you think will this be possible to implement, and will it at all? My ws client really need to have ability to read websocket data on clean connection close.  I've never contribute to esp-idf, but if you want I can try to implement this and open PR?

Hi @abobija
First of all, please, do not hesitate to post a PR (just note that we are a bit slow in getting back to you with feedback and reviews, but all contributions are more than welcome. we might amend the changes a little, though, to be in line with the internal pipeline of reviews and tests).
About the close message payload: I believe it should be already available in the application code, but as a separate event (WEBSOCKET_EVENT_DATA). In order to receive the close packet data, you could just modify the event handler here
https://github.com/espressif/esp-idf/blob/master/examples/protocols/websocket/main/websocket_example.c#L72-L73
to read not only the close message code, but also any applicable data after that.
if (data->op_code == 0x08 && data->data_len >= 2) {

Thank you @david-cermak
I was thinking all the time that I need to read closing data inside of WEBSOCKET_EVENT_CLOSED event, but now I see that on clean close first will be raised WEBSOCKET_EVENT_DATA with data, and then WEBSOCKET_EVENT_CLOSED, so I need to record data (and closing code) in first event and than use recorded data later in second event if I wish. That makes sense, so this issue can be closed.
p.s: Thanks for info about PRs
Best regards.

My websocket client code just freezes and does nothing after I got a close data from the server.
if (data->op_code == 0x08 && data->data_len == 2) {
    printf("[WebsocketClient] - Got Close data\n");
    return;
}

When my esp gets this data, the ws client does nothing after that. Can't receive or send frames. What should I do with this? Even a reinit does not help with these
void WebsocketClient::init() {
    client = esp_websocket_client_init(&config);
    esp_websocket_register_events(
        client,
        WEBSOCKET_EVENT_ANY,
        reinterpret_cast<esp_event_handler_t>(eventHandler),
        static_cast<void*>(this));
    esp_websocket_client_start(client);
}

bool WebsocketClient::reInit(){
    esp_err_t err = esp_websocket_client_destroy(client);
    if(err != ESP_OK){ return false; }
    init();
    return true;
}

It just stuck


AreExpectedScopesPresent method doesn't make sense

I can't understand in the code below:

Why it will always write an error in the log even though there can be no missing scopes
Why the missing scopes in the log line uses the variable supportedScopes? Shouldn't it be something like supportedScopes.Except(expectedScopes)?

protected virtual Task<bool> AreExpectedScopesPresent(IntrospectionRequestValidationResult validationResult)
{
    // check expected scopes
    var supportedScopes = validationResult.Api.Scopes.Select(x => x.Name);
    var expectedScopes = validationResult.Claims.Where(
       c => c.Type == JwtClaimTypes.Scope && supportedScopes.Contains(c.Value));

    Logger.LogError("Expected scope {scopes} is missing in token", supportedScopes);

    return Task.FromResult(expectedScopes.Any());
}

From IntrospectionResponseGenerator.cs
P.S.: I could have made a pull request but I'm not sure of the reasons why this method is right as it is. I do prefer to understand it first.

I've made a pull request "fixing" the second question.


feat: add moviepy, fontdict to allow.txt

Description
Thank you for opening a Pull Request!
Before submitting your PR, there are a few things you can do to make sure it goes smoothly:

[ ] Follow the CONTRIBUTING Guide.
[ ] You are listed as the author in your notebook or README file.

[ ] Your account is listed in CODEOWNERS for the file(s).

[ ] Make your Pull Request title in the https://www.conventionalcommits.org/ specification.
[ ] Ensure the tests and linter pass (Run nox -s format from the repository root to format).
[ ] Appropriate docs were updated (if necessary)

Fixes #<issue_number_goes_here> 🦕

For future reference, this could be added to the same PR as your notebook. Just push to the same branch.


BioModels backend changed?

Travis all of a sudden started to fail on Tellurium.  If the string

            # isn't utf-8, we fall back to iso-8859-1 for all other

            # encodings. (See PR #3538)

            try:

                reason = self.reason.decode('utf-8')

            except UnicodeDecodeError:

                reason = self.reason.decode('iso-8859-1')

        else:

            reason = self.reason

        if 400 <= self.status_code < 500:

            http_error_msg = u'%s Client Error: %s for url: %s' % (self.status_code, reason, self.url)

        elif 500 <= self.status_code < 600:

            http_error_msg = u'%s Server Error: %s for url: %s' % (self.status_code, reason, self.url)

        if http_error_msg:

>           raise HTTPError(http_error_msg, response=self)

E           requests.exceptions.HTTPError: 404 Client Error: Not Found for url: http://biomodels.caltech.edu//biomodels-main/download

../../../virtualenv/python3.6.3/lib/python3.6/site-packages/requests/models.py:935: HTTPError

------------------------------ Captured log call -------------------------------

connectionpool.py          824 DEBUG    Starting new HTTPS connection (1): www.ebi.ac.uk

connectionpool.py          396 DEBUG    https://www.ebi.ac.uk:443 "GET /biomodels-main/download?mid=BIOMD0000000139 HTTP/1.1" 307 0

connectionpool.py          208 DEBUG    Starting new HTTP connection (1): biomodels.caltech.edu

connectionpool.py          396 DEBUG    http://biomodels.caltech.edu:80 "GET //biomodels-main/download HTTP/1.1" 404 None

Is this a simple server issue or change in backend? I don't remember them announcing any changes.

Looking into the log, it seems like BioModel is redirecting the request to malformed url. Probably need to set allow_redirects = False for now.

Now Travis is choking 🤦♂


Add whistleblower to the post about contribution for Operação Serenata de Amor Project

What is the purpose of this Issue?
The purpose of this issue is include Whistleblower project on the post with all repositories of the project.
What could be done to achieve this purpose?
Write a extension to be included explaining about the Whistleblower should do the job.

cc @Irio


percents switched to 4 digits, use formatPercent for market preview

https://app.clubhouse.io/augur/story/14572/fee-should-be-shown-with-four-decimals

Pull Request Test Coverage Report for Build 1022

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 66.744%

Totals

Change from base Build 1021:
0.0%

Covered Lines:
3585

Relevant Lines:
4886

💛  - Coveralls

Pull Request Test Coverage Report for Build 1022

0 of 0   changed or added relevant lines in 0 files are covered.
No unchanged relevant lines lost coverage.
Overall coverage remained the same at 66.744%

Totals

Change from base Build 1021:
0.0%

Covered Lines:
3585

Relevant Lines:
4886

💛  - Coveralls


Add Light and Dark Mode Toggle for Katla Taiko  Swap

Describe the feature request
This issue proposes the implementation of a toggle switch to allow users to switch between light and dark mode for the Taiko Katla swap interface.
Benefits:
Improved user experience and preference customization.
Enhanced accessibility for users with visual impairments.
Implementation Details:
Use a toggle component from the existing UI library.
Implement state management to track the selected mode.
Update styles dynamically based on the chosen mode.
Optionally, persist the user's preference across sessions (using local storage or a database with appropriate security measures).
Testing:
Thoroughly test across browsers, devices, and screen sizes.
Ensure accessibility compliance and user-friendliness.
Spam policy

[X] I verify that this issue is NOT SPAM and understand SPAM issues will be closed and reported to GitHub, resulting in ACCOUNT TERMINATION.

Use a toggle component from the existing UI library.
Implement state management to track the selected mode.
Update styles dynamically based on the chosen mode.

There is a toggle in the settings:


Implement the backbone for future parametrization

Types of changes

[x] Docs change / refactoring / dependency upgrade
[ ] Bug fix (non-breaking change which fixes an issue)
[x] New feature (non-breaking change which adds functionality)
[x] Breaking change (fix or feature that would cause existing functionality to change)

Motivation and Context / Related issue
What
This provide the backbone for a brand new way to perform instrumentation (but leaves nevergrad unchanged for now, the new methods are not plugged in this PR). Currently the instrumentation is just a stateless bridge between the value space/candidates (the space of parameters feeded to the functions) and the optimization space (where the optimizers perform). The new Parameter  class in this PR now provides a stateful Instrumentation (i.e. an Instrumentation with a value), and therefore merges both Instrumentation  and Candidate together.
To simplify understanding of the code, be aware that they are 3 main types of parameters:

data: those are the actual base parameters leaf values. Everything is based on a generic Array parameters providing an interface for parametrizing np.ndarray. This is then subclassed into Scalar and Log (a shortcut for a log-distributed scalar).
containers: those are parameters that contain other parameters like Dict and Tuple. This also includes the former Instrumentation which is basically a tuple of a tuple (args) and a dict (kwargs).
choice: those are conditional parameters, which select one parameter among several choices. This includes Choice which is our former SoftmaxCategorical, and TransitionChoice which offers an equivalent to OrderedDiscrete, where mutations are defined as transitions between current element and the previous and next ones.

Why
This new way of doing things will hopefully make our lives simpler:

more explicit: the value serves as an initial value, and updating it is very easy, while it is currently tricky and not very intuitive (cf #314 for an example of how to provide an initial value in the current and the proposed method)
enables mutation and recombination: along the conversion to and from the standardized optimization space (get_std_data, set_std_data) the new API defines mutate and recombine methods. This will enable a whole new range of optimizers which would relie on these methods for their implementations (eg: currently crossovers in DE are predefined, now they could just call recombine which could be cleverly chosen/implemented by the user)
simpler to experiment: given that each Parameter has a value field, and mutate method, it is now easy to make sure that mutations behave as expected (correct standard deviation, logarithmic mutation etc). Eg. call param.value, then param.mutate() then recheck the value and check how it has been modified. When this new parametrization is plugged into the current framework, Optimizer.minimize function will preferably take only one argument which will be the output of the value attribute. A specific class of the new Parameter (called Instrumentation as before for compatibility) will however also allow to keep the current behavior with args and kwargs for those who prefer.
enables endogeneous parameters: evolution strategies sometimes define endogeneous parameters, i.e. internal parameters which can also mutate. This will also be possible with the new parametrization by having variable mutating using a standard deviation (for instance) which is itself a Parameter. This way, we will be able to define complex algorithms in a very straightforward way.
enables conditional variables: SoftmaxCategorical variable is now called Choice and allows arguments which are themselves Parameter, meaning they mutate/recombine as well. This way, it will for eg be possible to define choices between different deep neural network optimizers for instance, each taking parameters with different names and/or scales which can be tuned with nevergrad as well.

Advice
For reviewing, you may want to start by having a loop at the tests (test_parameters.py) with core.py alongside to check the docstrings (if a non-private method docstring is missing/not clear let me know). You can then check container.py, data.py and choice.py for implementation "details".
Next steps

Plug this new framework into the current framework, without breaking anything.
Let new and old frameworks live along for a couple of months with deprecation warnings.
Kill the old framework.

How Has This Been Tested (if it applies)

Checklist

[x] The documentation is up-to-date with the changes I made.
[x] I have read the CONTRIBUTING document and completed the CLA (see CONTRIBUTING).
[x] All tests passed, and additional code has been covered with new tests.

TODO list:

[ ] array bounds
[ ] array distribution
[ ] instrumentation
[ ] log parameter
[ ] sigma parameter?
[ ] ordered choice
[ ] unordered choice?

Possible future improvement (not to be included here):

stochastic int casting for Array (instead of rounding)

Now ready to review :)

always wrap the Constant in the class constructors?

I'll try

Merging this for now, dicussions can move on to #391
This second step will aim at plugging the new pipeline inside the old one, and have both compatibility


unban the work 'tiktok'

A description of the issue:
any message with the word 'tiktok' gets deleted. this is highly annoying and i feel like there is no actual reason to do that? like i think it was hahah funny back in the day but now its actually kinda annoying when you wanna talk ab tiktok or even mention it
Proposed Solution:
change the dyno perm
Additional Comments:
no

yeah fair enough gimme 2 secs

Reban tiktok


Group dont work for me

Kick members of legacy seat group and dont add members to that group (work with old groupe created with webseat beta 20)

After discussion with creator of this issue:
It was a configuration error by the user. For any SeAT-Group you need to assign valid corporations to the SeAT-Group. This is a feature to prevent users still carring roles that might have been purged from corporation. However this is not the first issue with this feature i leave this ticket open as an improvement request. I need to explain this better.
If any one got a suggestion

This issue has been adressed with the latest version:


MH-13106: Add Moodle groups to Moodle role provider

This extends the Moodle role provider to make it aware of Moodle groups. Additionally to the learner und instructor roles, group roles in the form of G{GROUP_ID}_Learner will be added. It is thus possible to restrict access to certain groups instead of a whole course.
This extension requires a recent version of the moodle-tool_opencast Moodle Plugin.

I fixed the typo.


Add prototypeSign property

With some fonts, for example, the zero is wider

Thank you for the input. A new feature to enable FontFeature.tabularFigures has been added in v0.3.1. Hopefully this can help resolve alignment issues for fonts that support tabular figures. Also, 0 is used to replace 8 as prototype for all cases.


[help]  on project seatunnel-connector-spark-hbase: wrap: org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1)

Java version: 1.8.0_271
Scala version: 2.11.12
When I execute ./mvnw install -Dmaven.test.skip
[ERROR] Failed to execute goal net.alchim31.maven:scala-maven-plugin:3.3.1:compile (scala-compile-first) on project seatunnel-connector-spark-hbase: wrap: org.apache.commons.exec.ExecuteException: Process exited with an error: 1 (Exit value: 1) -> [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions, please read the following articles:
[ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the command
[ERROR]   mvn <args> -rf :seatunnel-connector-spark-hbase

I have the same error, how did you solve it, thank you. @skyoct

I have the same error, how did you solve it, thank you. @skyoct

I didn't completely solve this problem, but directly blocked the module


resources: clarify acronyms

sometimes it's nice to get the full name out there, with all these xDS
Signed-off-by: Vincent Batts<EMAIL_ADDRESS>

Hi @vbatts. Thanks for your PR.
I'm waiting for a istio member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.
I understand the commands that are listed here.

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.

I could do this in other places like the RDS struct, etc.

/ok-to-test


Fix search box breaking when increasing font size

Bug report: #808
This fixes the search box breaking when someone increases the font size. When something has a height (especially of px) it doesn't grow with the text (not when zooming but increasing just the font size).
Removing the height completely would be the ideal solution but that caused issues in IE9, IE10 and WindowsPhone due to the alignment with the submit button.
The height got substituted with line-height but that alone caused issues in Safari in many iOS versions and Chrome on some Android phones, the text box somehow had a height of 36px and not 35px which caused a white line to appear below the submit button.
That's why the height of all the things got increased to 36px which fixed it. (Although it is not clear what caused it.)

Hmm, I don't have the right permissions to see details of the Jenkins errors. Who do I need to ask for that?

@selfthinker Seems there was some problem connecting to github before, I've rebuilt it for you.

This changes the default minimum size. Is that intentional?

It's half-intentional. As I wrote above, when I changed the original height: 35px to min-height: 35px, several browsers would make the input's height 36px. To make it more consistent across all browsers, I increased it everywhere to 36px. There might be a better way to fix that (e.g. reducing the padding?), so I'd be happy with other solutions.

@markhurrell thoughts?

looks better at 36px - think it was meant to be that anyway, it's not vertically centered at 35px
good spot fixing the issue


update dependency

upgrade dependency for pyjwt by following https://github.com/jpadilla/pyjwt/blob/master/CHANGELOG.rst#changed-3 so that we may fix CI error in Pypy3.9

API change check
API changes are not detected in this pull request.


Order of pointers array changed in between pinchmove and pinchend

It came to my attention that sometimes the value of e.rotation would be 180 degrees off at the end of a pinch.
Upon further inspecting the issue it came to my attention that the order of e.pointers had changed in between pinchmove and pinchend, resulting in the “wrong” value for e.rotation at pinchend.
Here's a (screenshot) dump of the last value of e during Hammer.INPUT_MOVE:

And here's a (screenshot) dump of the value of e at Hammer.INPUT_END (fired directly after the above):

Do note:

the order of pointers that has changed (the identifiers are correctly preserved)
the rotation that is 180 degrees off

A fix could be to sort the pointers array on their identifier before doing performing internal calculations (such as defining rotation) on them.

@bramus thank you for reporting this we had another bug from depending on pointer order previously looks like we missed this

@bramus can you confirm this is with latest Hammer.js and not an outdated build? The fix for pointer order was fairly recent.


Some chnages to test all-contributors

@all-contributors add @i-mighty for test and code and ideas and maintenance

@all-contributors add @i-mighty for test and code and ideas and maintenance

@all-contributors add @rowlandekemezie for ideas and reviews

@all-contributors add @iamNarcisse for test and code and platform and maintenance


Fixup multiple model DS tests

What does this PR do?
Fixes failures on DS tests wrt multiple models.
TL;DR:

Need to remember to call AcceleratorState.reset_state() when we want to do things in concurrent different configurations (such as the multiple ds model configuration tests that actually do things)
Still need patch_environment to properly setup everything, otherwise we end up with failures when running the entire DS suite at once.

Fixes our tests & deepspeeds PR's from failing
Before submitting

[ ] This PR fixes a typo or improves the docs (you can dismiss the other checks if that's the case).
[ ] Did you read the contributor guideline,
Pull Request section?
[ ] Was this discussed/approved via a Github issue or the forum? Please add a link
to it if that's the case.
[ ] Did you make sure to update the documentation with your changes? Here are the
documentation guidelines, and
here are tips on formatting docstrings.
[ ] Did you write any new necessary tests?

Who can review?
Anyone in the community is free to review the PR once the tests have passed. Feel free to tag
members/contributors who may be interested in your PR.
@SunMarc

Thank you very much for the example provided. Is there a way to integrate this with the transformers Trainer?


feat: manage accounts (resolves #1211)

Resolves #1211.

[x] Approve individuals, organizations, and regulated organizations
[x] Suspend and unsuspend individuals, organizations, and regulated organizations
[x] Add approval status to the publishable checks for their pages
[x] Notify individuals, organizations, and regulated organizations of approval, suspension, and unsuspension
[x] Restrict access to their pages based on suspension status
[x] Restrict their activity based on suspension status

Prerequisites
If this PR changes PHP code or dependencies:

[x] I've run composer format and fixed any code formatting issues.
[x] I've run composer analyze and addressed any static analysis issues.
[x] I've run php artisan test and ensured that all tests pass.
[x] I've run composer localize to update localization source files and committed any changes.

If this PR changes CSS or JavaScript code or dependencies:

[x] I've run npm run lint and fixed any linting issues.
[x] I've run npm run build and ensured that CSS and JavaScript assets can be compiled.

@cherylhjli, @greatislander and I were talking today about the need for a banner/message to be displayed to admins when they are viewing content that is for a suspended user. There may need to be copy and/or other design considerations for this.

@jobara @greatislander I think we can use this design here: https://www.figma.com/file/AXufBnFAVHvGdsxnQMVhNF/The-Accessibility-Exchange-Wireframes?node-id=5101%3A107877
Copy can be something like, "This account has been suspended." Thoughts?


Simplify guest I/O

"syscalls" are now how guest talks with host; no more distinction between "syscall" and "channel"
(Posix style file descriptors can be implemented on top of syscalls, since posix semantics are all byte-based)
Syscalls are now named to avoid numbering conflicts.
It's now just as easy (if not easier) for users to implement their own syscalls as it was for them to implement their own sendrecv channels.
Added "syscall!" macro to invoke a syscall from the guest side to reduce the number of separate asm! wrappers

Can these syscalls be used from other languages? One of the goals of the existing syscall interface is to make them callable by other languages that have the notion of a "C" FFI.


We should probably make the path for a fragment clearer

We give the example path as
C:\ProgramData\Microsoft\Windows Terminal\Fragments\{app-name}
But that's not totally clear if the .json goes there, or a folder does. We should make it clearer. Something like
C:\ProgramData\Microsoft\Windows Terminal\Fragments\{app-name}\{file-name}.json
and mention that {app-name} should be unique to your application, and that {file-name} can be anything - the terminal will read all .json files in that directory.
case in point: https://github.com/microsoft/terminal/pull/7632#issuecomment-793068481

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

ID: e7dd918e-788a-e3f5-379f-240d72b1e6ea
Version Independent ID: 341f8755-2701-601f-5b91-98527354b3e8
Content: Windows Terminal JSON Fragment Extensions
Content Source: TerminalDocs/json-fragment-extensions.md
Product: dev-environment
Technology: windows-terminal
GitHub Login: @cinnamon-msft
Microsoft Alias: cinnamon

Done. :)
https://github.com/MicrosoftDocs/terminal/commit/ba33faa70852cc93fcbe38495ad27f42b1df8acd


make issue on centos7

ii am trying to install the lustre_exporter on cetos 7 and below the steps i did
1-install go command
#wget https://dl.google.com/go/go1.10.3.linux-amd64.tar.gz
#tar -C /usr/local -xzf go1.10.3.linux-amd64.tar.gz
Adjust the Path Variable. ---> vi ~/.bash_profile ----> add the follwoing " export PATH=$PATH:/usr/local/go/bin" ---> source ~/.bash_profile
2-download luster_exporter
#cd /root/ ; go get github.com/HewlettPackard/lustre_exporter
3-Run make file
#cd /root/go/src/github.com/HewlettPackard/lustre_exporter
#make
the issue appears when i run make (check the attached file)
luster_error.txt
any thing i am missing ?

If you take a look at the build report, go tip is building but 1.8.x is not due to some of our linters...we need to fix this, but to get you started if you move to 1.9.x you should be able to make this work.

Thanks will use the 1.9.x
From: Joe Handzik<EMAIL_ADDRESS>Sent: Tuesday, June 18, 2019 5:15 PM
To: HewlettPackard/lustre_exporter<EMAIL_ADDRESS>Cc: Afify, Sherif S (IBS<EMAIL_ADDRESS>Author<EMAIL_ADDRESS>Subject: Re: [HewlettPackard/lustre_exporter] make issue on centos7 (#143)
If you take a look at the build report, go tip is building but 1.8.x is not due to some of our linters...we need to fix this, but to get you started if you move to 1.9.x you should be able to make this work.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHubhttps://github.com/HewlettPackard/lustre_exporter/issues/143?email_source=notifications&email_token=ADNLVEPTTFDN4CZEQDUFUETP3D3XDA5CNFSM4HYUUTZ2YY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODX67DKQ#issuecomment-503181738, or mute the threadhttps://github.com/notifications/unsubscribe-auth/ADNLVEOWKHCPDP6FUF5GUO3P3D3XDANCNFSM4HYUUTZQ.

i tried both 1.9.7  and 1.12.6 still have the same issue but in 1.12.6  i see a min. errors
1-version 1.9.7 error:
../../../../../../usr/local/go/src/net/cgo_unix.go:127:53:warning: invalid operation: r (variable of type *invalid type) has no field or method ai_addr (compile) (staticcheck)
../../../../../../usr/local/go/src/net/cgo_unix.go:175:22:warning: invalid operation: res (variable of type *invalid type) has no field or method ai_canonname (compile) (staticcheck)
../../../../../../usr/local/go/src/net/cgo_unix.go:183:30:warning: invalid operation: r (variable of type *invalid type) has no field or method ai_next (compile) (staticcheck)
../../../../../../usr/local/go/src/net/cgo_unix.go:185:6:warning: invalid operation: r (variable of type *invalid type) has no field or method ai_socktype (compile) (staticcheck)
../../../../../../usr/local/go/src/net/cgo_unix.go:188:10:warning: invalid operation: r (variable of type *invalid type) has no field or method ai_family (compile) (staticcheck)
../../../../../../usr/local/go/src/net/cgo_unix.go:190:53:warning: invalid operation: r (variable of type *invalid type) has no field or method ai_addr (compile) (staticcheck)
../../../../../../usr/local/go/src/net/cgo_unix.go:194:53:warning: invalid operation: r (variable of type *invalid type) has no field or method ai_addr (compile) (staticcheck)
make: *** [gometalinter] Error 1
[root@vm1 lustre_exporter]# go version
go version go1.9.7 linux/amd64
[root@vm1 lustre_exporter]#

2-version 1.12.6
[root@vm1 lustre_exporter]# make
>> formatting code
>> linting code
WARNING: Linters are now vendored by default, --update ignored. The original
behaviour can be re-enabled with --no-vendored-linters.

To request an update for a vendored linter file an issue at:
https://github.com/alecthomas/gometalinter/issues/new

../../../../../../usr/local/go/src/net/lookup_unix.go:324:23:warning: undeclared name: cgoLookupPTR (maligned)
../../../../../../usr/local/go/src/net/lookup_unix.go:124:24:warning: undeclared name: cgoLookupCNAME (maligned)
../../../../../../usr/local/go/src/net/lookup_unix.go:108:23:warning: undeclared name: cgoLookupPort (maligned)
../../../../../../usr/local/go/src/net/lookup_unix.go:96:24:warning: undeclared name: cgoLookupIP (maligned)
../../../../../../usr/local/go/src/net/lookup_unix.go:81:24:warning: undeclared name: cgoLookupHost (maligned)
../../../../../../usr/local/go/src/net/lookup_unix.go:324:23:warning: unused variable or constant undeclared name: cgoLookupPTR (varcheck)
../../../../../../usr/local/go/src/net/lookup_unix.go:124:24:warning: unused variable or constant undeclared name: cgoLookupCNAME (varcheck)
../../../../../../usr/local/go/src/net/lookup_unix.go:108:23:warning: unused variable or constant undeclared name: cgoLookupPort (varcheck)
../../../../../../usr/local/go/src/net/lookup_unix.go:96:24:warning: unused variable or constant undeclared name: cgoLookupIP (varcheck)
../../../../../../usr/local/go/src/net/lookup_unix.go:81:24:warning: unused variable or constant undeclared name: cgoLookupHost (varcheck)
../../../../../../usr/local/go/src/net/lookup_unix.go:324:23:warning: undeclared name: cgoLookupPTR (interfacer)
../../../../../../usr/local/go/src/net/lookup_unix.go:124:24:warning: undeclared name: cgoLookupCNAME (interfacer)
../../../../../../usr/local/go/src/net/lookup_unix.go:108:23:warning: undeclared name: cgoLookupPort (interfacer)
../../../../../../usr/local/go/src/net/lookup_unix.go:96:24:warning: undeclared name: cgoLookupIP (interfacer)
../../../../../../usr/local/go/src/net/lookup_unix.go:81:24:warning: undeclared name: cgoLookupHost (interfacer)
../../../../../../usr/local/go/src/net/lookup_unix.go:324:23:warning: undeclared name: cgoLookupPTR (unconvert)
../../../../../../usr/local/go/src/net/lookup_unix.go:124:24:warning: undeclared name: cgoLookupCNAME (unconvert)
../../../../../../usr/local/go/src/net/lookup_unix.go:108:23:warning: undeclared name: cgoLookupPort (unconvert)
../../../../../../usr/local/go/src/net/lookup_unix.go:96:24:warning: undeclared name: cgoLookupIP (unconvert)
../../../../../../usr/local/go/src/net/lookup_unix.go:81:24:warning: undeclared name: cgoLookupHost (unconvert)
../../../../../../usr/local/go/src/net/lookup_unix.go:324:23:warning: unused struct field undeclared name: cgoLookupPTR (structcheck)
../../../../../../usr/local/go/src/net/lookup_unix.go:124:24:warning: unused struct field undeclared name: cgoLookupCNAME (structcheck)
../../../../../../usr/local/go/src/net/lookup_unix.go:108:23:warning: unused struct field undeclared name: cgoLookupPort (structcheck)
../../../../../../usr/local/go/src/net/lookup_unix.go:96:24:warning: unused struct field undeclared name: cgoLookupIP (structcheck)
../../../../../../usr/local/go/src/net/lookup_unix.go:81:24:warning: unused struct field undeclared name: cgoLookupHost (structcheck)
make: *** [gometalinter] Error 1
[root@vm1 lustre_exporter]# go version
go version go1.12.6 linux/amd64
[root@vm1 lustre_exporter]#

I'm going to do what I can here, but some of this seems pretty specific to the linter that we're using. I can remove it, but I don't want to just do that without considering our options.
In the meantime, I just pulled this down and ran with version 1.12.6, and everything worked fine. I don't know what version tip is at, but I would be surprised if 1.12.x was super close to tip. So you'll need to upgrade a bit further to get this working in its current state.

Ok, on further inspection I made the decision to switch us to golangci-lint for linting. It seems to work well in my testing so far.
I was not able to get the Travis configuration working in its previous state (testing against 1.8.x and tip). On further investigation, these issues are to be expected. Only the last two releases of golang are supported (so 1.12 and 1.11). Anything older is not. In fact, I noticed that one of my primary issues with the new linter was a reference to the 'wasm' architecture which I assume is the WebAssembly support in golang as of 1.11. Testing passes now with the new linter and a couple fixes it requested.
Please reach out if you continue to have issues, but I suspect your environment needs to be cleaned up. It could be a result of binaries involved in the lustre_exporter build and run process being built with another version of golang. The 'easiest' fix is to delete everything located at $GO_PATH if you can. Please reach out if you continue to have issues, but I'm going to close for now as master builds in Travis and in my environment.


1603 | Design Parking System | C++

Design Parking System
What will change -
add new problem that is not present
Type of Issue -
Please add/delete options that are not relevant.

[x] Adding New Code

Programming Language
Please add/delete options that are not relevant.

[x] C++

Self Check

Ask for issue assignment and wait to get assigned to it before making Pull Request.
Add your file in the proper folder
Clean Code and Documentation for better readability
Add Title and Description of the program in the file

:star2: Star it :fork_and_knife:Fork it :handshake: Contribute to it!
Discord server ✉ - https://discord.gg/CXksGdn
Happy Coding,

assign to me


How can i set cookie on root domain?

Is there a way to set the cookie-consent cookie on the root domain? e.g. *.mydomain.com  I have a wildcard subdomain and right now the consent cookie includes the subdomain, making the consent banner popup appear for each subdomain i visit.

@VictorGerritsen
Just to be clear, you only want have the cookie consent banner show up on only the root domain and not the subdomains?
Example only show it on mydomain.com and do not show it on sub.mydomain.com ?

Some research:
https://stackoverflow.com/questions/3742675/sharing-django-sessions-on-specific-subdomains
https://stackoverflow.com/questions/556907/how-to-get-distinct-django-apps-on-same-subdomain-to-share-session-cookie
https://stackoverflow.com/questions/18492576/share-cookie-between-subdomain-and-domain
https://serverfault.com/questions/153409/can-subdomain-example-com-set-a-cookie-that-can-be-read-by-example-com
https://stackoverflow.com/questions/2116860/django-session-cookie-domain-with-multiple-domains
https://stackoverflow.com/questions/53349940/cookie-behavior-in-django
https://stackoverflow.com/questions/2043138/could-not-get-cookie-from-another-parent-domain-in-django
https://stackoverflow.com/questions/5258126/domain-set-cookie-for-subdomain
https://stackoverflow.com/questions/5671451/creating-a-javascript-cookie-on-a-domain-and-reading-it-across-sub-domains
https://stackoverflow.com/questions/4713019/setting-cross-subdomain-cookie-with-javascript


Scaling down

I wish I'd recognised earlier that it's not just the accommodation of the needs of busy/sophisticated teams
that's important here.
All the more frustrated with myself since it was a real client project where the need for maximum clarity and simplicity really struck home.
There is just as much need for teams whose needs are less demanding in terms of frequency and size of change. Here I am trying to define the simplest employment of the process with a new 'Starting simple' section which aims to justify that the simplest way to use this recommendation is actually the best simple scenario solution.

By Merging #416, I think it created conflicts. @ijmitch Can you have a look please?
I completely agree with what you added, since I had the feeling that a first explanation of the branching with mainwas missing and necessary (I just couldn't express it clearly).
@dennis-behm Are you OK to merge it into the main version? There are few things I'd like to fix in Ian's new section, but just minor things.

Looks like I was able to fix the conflict, it was a minor thing with the new sections names.

LGTM!

Thanks @ijmitch - this looks good to me!

Thanks @ijmitch - this looks good to me!

Good enough to merge? (I don't have write access.)

thanks @dennis-behm


Algebraic Lenses

This starts to develop algebraic lenses, as introduced in https://github.com/AlgebraicJulia/Blog/pull/81.

RIP coverage


Draft parallel console implementation

This allows Gradle to show multiple items in progress when attached
to an interactive terminal.
This is achieved by:
First, breaking apart ConsoleBackedProgressRenderer into 3 filters:

ThrottlingOutputEventListener buffers OutputEvents and flushes
them after a certain period of time or if the build has ended
BuildStatusRenderer maintains a Label that displays overall
build progress (formerly the "status bar")
WorkInProgressRenderer maintains a BuildProgressArea and
associates one branch of a ProgressOperations "tree" to a Label
representing work in progress for multiple workers.

Second, externalizing and enhancing concepts within AnsiConsole:

Cursor represents a position in the terminal, using a cartesian
coordinate system with origin (0, 0) at the bottom left
MultiLineProgressArea is a TextArea implementation with
addressible lines through Labels.
Style represents ANSI text colors and emphases.
Span is simply an association between a Style and String of
text.
AnsiExecutor is an ANSI-aware text writer. It accepts Actions
that may reposition the Cursor and write styled text

Finally, logging improvements. Project evaluation logging was
extracted from build progress logging. Build progress logs are
formatted with a ProgressBar formatter and submitted through
the same ProgressOperations mechanism. These ProgressOperations
are selected by the BuildStatusRenderer and rendered separately
from other ProgressOperations for now. In the future, we will
have must stronger semantics around this using BuildOperations.
Issue: gradle/gradle-private#649
Internal Review: https://code-review.gradle.org/cru/REVIEW-6444
Remaining tasks:

[ ] Address possible windows perf regression
[ ] Honor --max-workers option
[ ] De-duplicate ownership of "status bar"

This was merged with 34c3667, but we'll continue review at https://code-review.gradle.org/cru/REVIEW-6444


Fix infinite loop in C++

Issue
Infinite while (true) loops didn't yield when using C++ and would crash everything.
Fix
C++ uses some different tokens. Instead of a Literal token, it's a BooleanLiteral token that represents the concrete value true. By updating the aether yielding function, it's possible to add yielding to infinite C++ loops.
Risk
Although this touches a lot of code, it's additive. I believe the only risk is that this somehow causes more yielding to happen in the context of while (<Literal | BooleanLiteral>).
I cannot think of a situation where this happens.
China
If china needs this asap, merge this change behind a feature flag.
How to manually test

Check out this change locally.
Run against proxy
On the home page log into your admin/internal account.
Navigate to http://localhost:3000/play/level/village-rover?codeLanguage=cpp

Input the following code:
void main() {
    while (true) {
        auto enemy = hero.findNearestEnemy();
        if(enemy){
            hero.attack(enemy);
        }
    }
}

@nwinter do you think this is safe to merge. Can you think of any regression risks?

It looks good and I can't imagine anything. If you really want to spend more time verifying,  you could run the verifier on a bunch of levels using this change vs. current master; that should turn up most issues that this could cause (although that can take a while to interpret). But if it were me, I would just merge it in.

I'll merge it into china staging environment first, we have some partner testing C++ there

I ran this through the verified for python and javascript and everything turned out green. This gives me confidence to merge this, especially as we're testing in China.


bug: passphrase review screen crashes on passphrases exceeding 72 characters

The TextArea component is configured to not allow overflow. It crashes seed passphrase review on passphrases longer than 72 characters.
Steps to reproduce:

Input a long seed passphrase exceeding 72 characters in length
Accept the seed passphrase after entry

Expected Result:
User can review the passphrase, accept it, and continue with the transaction signing workflow
Actual Result
Get a System Error screen with a TextDoesNotFitException at components.py, line 361
User dies in poverty, because this is the only signing device they have access to
Suggested Remedies
Option 1: Allow Text Overflow
At the very least, allowing text overflow lets you get past this critical step
Option 2: Add multiple steps to the SeedReviewPassphraseView
If text overflow is detected (let's assume the rule is simple like len(self.seed.passphrase) > 72) button states will be [EDIT, SCROLL_DOWN]until the user has reached the last page of their passphrase, at which point, button states will be [EDIT, DONE]. SCROLL_DOWN button selection will set Destination to SeedReviewPassphraseView with a page_num view argument

issue fixed, will be put into next release (0.5.2)


How make the tests run faster?

I'm using Drone to run rspec and everything is okay so far. But, I think it's slow. On average, it took around 5 minutes, 20 seconds to finish.
My .drone.yml:
pipeline:
  build:
    image: zulhfreelancer/ruby_nodejs:latest
    commands:
      - gem update bundler
      - bundle install --path vendor/bundle
      - bundle exec rake db:create db:migrate
      - bundle exec rspec
    environment:
      - RAILS_ENV=test
      - SECRET_TOKEN=abc
      - DB_HOST=postgres
      - DB_USER=pg_user
      - DB_PASSWORD=pg_pass

services:
  postgres:
    image: postgres:9.4.5
    environment:
      POSTGRES_PASSWORD: pg_pass
      POSTGRES_USER: pg_user
      PGDATA: /var/lib/postgresql/data
      POSTGRES_DB: useradmin_test
  redis:
    image: redis:2.8.22

cache:
  - vendor/bundle
  - .git

Any idea or suggestion how to make the tests finish faster?
FYI, I'm running DroneCI on 1GB VPS. I only have Drone service inside that VPS. No other processes running except Drone.

per our issue template, we kindly ask that you use discourse for questions and support


[SPARK-15420] [SQL] Add repartition and sort to prepare output data

This is currently based on SPARK-14543 and includes its commits.
What changes were proposed in this pull request?

WriterContainer detects that the incoming logical plan has been sorted and does not sort a second time if the sort matches the table's partitioning, bucketing, and sorting.
Local sort is added by the optimizer for CatalogTables that have bucket or sort columns. This implements sortBy for Hive tables.
Repartition and sort operations are added when DataFrameWriter#writersPerPartition(Int) is set. This enables users to easily control how many files per partition are created.
Repartition and sort operations are added by the optimizer for columnar formats like Parquet if enabled by spark.sql.files.columnar.insertRepartition (and does not conflict with the query).

How was this patch tested?
WIP: adding tests.

Test build #58915 has started for PR 13206 at commit eed85ad.

Test build #58915 has finished for PR 13206 at commit eed85ad.

This patch fails Spark unit tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class DistributeAndSortOutputData(conf: CatalystConf) extends Rule[LogicalPlan]

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/58915/
Test FAILed.

Test build #58925 has started for PR 13206 at commit a64be8a.

Test build #58925 has finished for PR 13206 at commit a64be8a.

This patch passes all tests.
This patch merges cleanly.
This patch adds the following public classes (experimental):
case class DistributeAndSortOutputData(conf: CatalystConf) extends Rule[LogicalPlan]

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

Merged build finished. Test PASSed.

may be fixed in https://github.com/apache/spark/pull/16898

@rdblue do you know if Is it true ^ ?

@HyukjinKwon, that addresses part of what this patch does, but only for writes that go through FileFormatWriter. This patch works for Hive and adds an optimizer rule to add the sort instead of sorting in the writer, which I don't think is a great idea.

@rdblue What is the latest status of this PR?

We still maintain a version of this for our Spark builds to avoid an extra sort in Hive. If someone is willing to review it, I can probably find the time to rebase it on master. I think the year this sat initially was just because the 2.0 release was happening at the same time and there wasn't much bandwidth for reviews.

Test build #83583 has started for PR 13206 at commit a64be8a.

Test build #83583 has finished for PR 13206 at commit a64be8a.

This patch fails PySpark unit tests.
This patch does not merge cleanly.
This patch adds the following public classes (experimental):
case class DistributeAndSortOutputData(conf: CatalystConf) extends Rule[LogicalPlan]

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/83583/
Test FAILed.

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/testing-k8s-prb-make-spark-distribution-unified/2131/
Test PASSed.

Test build #95019 has started for PR 13206 at commit a64be8a.

Test build #95019 has finished for PR 13206 at commit a64be8a.

This patch fails Spark unit tests.
This patch does not merge cleanly.
This patch adds the following public classes (experimental):
case class DistributeAndSortOutputData(conf: CatalystConf) extends Rule[LogicalPlan]

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/95019/
Test FAILed.

Test build #95964 has started for PR 13206 at commit a64be8a.

Test build #95964 has finished for PR 13206 at commit a64be8a.

This patch fails Spark unit tests.
This patch does not merge cleanly.
This patch adds the following public classes (experimental):
case class DistributeAndSortOutputData(conf: CatalystConf) extends Rule[LogicalPlan]

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

Build finished. Test FAILed.

@rdblue can this be merged?

@tooptoop4, this will be done in the DataSourceV2 work. I don't think that it is going to be done for v1 plans.


Make App as NFC Card

Hello we are building smart doors that people can put their NFC cards on to unlock the door.
wondering if i can do the same thing but on mobile with this library? create an app that acs as a NFC Card (Not Reading or Writing)
The typical senario is i added some string on the mobile NFC when i put the app in front of the door. the door will scan the NFC data on the app and open the door.
How can i do something like that?

https://stackoverflow.com/questions/34607168/nfc-unavailable-when-camera-is-open

That would be really interesting. But, Apple doesn't give permission to do this. It's a closed API for their wallet app.

This can be done on Android using card emulation, but as @jackgisel mentioned, not possible on iOS.

Hi, as @svvitale mentioned, it is possible to do using the HCE feature in Android. I just wrote the react-native extension "react-native-hce", that supports the NFC tag emulation right away. Hope it will help.

@appidea so we can transmit from data from device A using react-native-hce and can receive data on B devices using react-native-nfc-manager , right ?

@Ov3rControl did you find any solution ?

@amitbravo no the project was cancelled so i didn't get the chance

can't simply
react-native-nfc-manager work as sending data on one device and read on another device , same app .

@amitbravo did you ever figure out a solution for this? Thanks

any updates on this one?


Browser tab unresponsive when typing >4 characters in a multiple select

Chrome's tab freezes with a select element with multiple="multiple". I initially thought this was caused by the fact that I was using Stimulus.js. However, I seem to have been able to replicate the issue in jsfiddle without using Stimulus.js.
Using 1.7.8
To Reproduce

Visit https://jsfiddle.net/apphancer/uoz6q8g5/4/ with Chrome
Type in a word with 1-2 characters and select it: all works well
Type in a word with more than 4-5 characters: no more characters can be typed and the tab freezes

It doesn't seem to be an issue with Firefox and Safari.

I confirm, update to version 2.0 fixed this issue. :+1:


Add task 'Use NuGet latest' to pipelines

Fixes #minor
Description
Using the latest NuGet fixes NuGet restore error "Project ... is not compatible with net60". The error results from using an old version.

Pull Request Test Coverage Report for Build 324196

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

Totals

Change from base Build 324169:
0.003%

Covered Lines:
25582

Relevant Lines:
32350

💛  - Coveralls


Added instructions to clone a new repo and "working directory" header in section

Will add localised string later if this is ok

What does FUZZ.txt mean?

Linting is broken. Forget it for now.

FUZZ.txt is the directory name. It is just a random repo i cloned from github

FUZZ.txt is the directory name. It is just a random repo i cloned from github

I see…. That’s a confusing name.

I think there should be instruction on on how to select another directory. Or even make it a button, popping up the folder selection menu.


Muzei keeps switching Sources

No matter how many times I switch the source to Backdrops, within a day it'll switch back to Featured Art.

Muzei switches back to the default source only if the source crashes when Muzei sends it an action (such as the 'Next Artwork') or the source disables itself. That is working as intended. I'd strongly suggest contacting Backdrops.
If you want to send a bug report to<EMAIL_ADDRESS>taken as soon as you can after it switches back to the Featured Art, we can confirm exactly what happened.


Added query dataset is displayed as reference

I add a dataset using the following command:
miga add -P ~/miga-data/TypeMat -i assembly --query pbivia.fasta
Then list all reference datasets and see this dataset in the list:
miga ls -P ~/miga-data/TypeMat --ref | grep bivia
Prevotella_bivia_DSM_20514_GCA_000262545
Prevotella_bivia_JCVIHMP010_GCA_000177315
pbivia

It is also displayed as a reference dataset in the dataset metadata.

Seems like it was caused by the metadata file that stayed in metadata folder nevertheless I executed "miga rm" for the dataset.


Broken d.ts generation for destructuring

Hello,
we moved recently from TS 1.4 to TS 1.5 with Visual Studio 2013.
When we have the following class definition:
export class ErrorClass {
    public foo({bar: number}) { }
}

With the Option "Generate declaration files" and "combine javascript output into file" to true, the resulting declaration for this file will be:
class ErrorClass {
    foo({bar: }: {
        bar: any;
    }): void;
}

Which is syntactically incorrect: The first "bar" is missing the type specifier (and is of type number instead of any).
This will cause that projects using this declaration file fails to compile.
Can anyone reproduce this? Is there a fix available?
Kind regards,
Timo

duplicate of #3912

Fix is in master now. please give it a try on the nightly build later tonight/tomorrow using npm install typescript@next


🚨 Surface warnings during toc file extension resolution

Old jupyterbook-style _toc.yml files allowed (required...?) filenames without extensions. We are hoping to encourage explicit filenames with extensions in the new myst.yml toc.
This PR raises warnings/errors during toc resolution; there are 4 distinct errors:

toc entry has an extension but does not exist
toc entry has no extension and cannot be resolved to a file that exists
toc entry has no extension and resolves to a single file (this is just a warning, but still surfaced to the user)
toc entry has no extension and resolves to multiple files

This PR addresses https://github.com/executablebooks/mystmd/issues/1248
Note - legacy jupyterbook toc behavior and warnings/errors are unchanged.

LGTM!


Log4netAppender depends on log4net 2.0.7 on targets that are not .netstandard1.3

During some code cleanup I entoutered an issue with an assemblybinding
After some looking into the code of Log4Net appender I encountered this curious piece of code in the csproj file.
  <ItemGroup Condition=" '$(TargetFramework)' == 'netstandard1.3' ">
    <PackageReference Include="log4net" Version="2.0.8" />
  </ItemGroup>

  <ItemGroup Condition=" '$(TargetFramework)' != 'netstandard1.3' ">
    <PackageReference Include="log4net" Version="2.0.7" />
  </ItemGroup>

What is special about netstandard1.3 that only this target deserves 2.0.8?
Repro Steps

Just add reference to Log4NetAppender

Actual Behavior
It depends on log4net 2.0.7
Expected Behavior
It depends on log4net 2.0.8

We regularly find things that aren't supported in netstandard1.x
That's the intent here, but i would have expected this to be the other way around. Usually it's the older version that supports the older framework.
Maybe this was a typo.
Thanks for calling attention to this. I'll take a look at it today


KafkaClient.sendRequest stuck in ensureBrokerReady loop preventing broker failover due to missing metadata refresh

Bug Report
We've been investigating why on some occasions our HighLevelProducer stops producing when one broker goes down and in some cases it doesn't. Discovered that the issue lies within KafkaClient.sendRequest getting stuck in ensureBrokerReady.
We have 3 brokers and are using keyed producer, with automatic retries on produce failure.
The "happy" (working) path on 1 broker going down with Debug logging:
message: 5413
  kafka-node:KafkaClient compressing messages if needed +1s
  kafka-node:KafkaClient checking payload topic/partitions has leaders +0ms
  kafka-node:KafkaClient found leaders for all +0ms
  kafka-node:KafkaClient grouped requests by 1 brokers ["1"] +0ms
  kafka-node:KafkaClient has apiSupport broker is ready +0ms
  kafka-node:KafkaClient found 1 connected broker(s) +1ms
Received error: BrokerNotAvailableError: Broker not available (sendRequest)
  kafka-node:KafkaClient updating metadatas +19ms
  kafka-node:KafkaClient compressing messages if needed +19ms
  kafka-node:KafkaClient checking payload topic/partitions has leaders +0ms
  kafka-node:KafkaClient found leaders for all +1ms
  kafka-node:KafkaClient grouped requests by 1 brokers ["0"] +0ms
  kafka-node:KafkaClient missing apiSupport waiting until broker is ready... +0ms
  kafka-node:KafkaClient Sending versions request to toniss-mbp-2.lan:9092 +1ms
  kafka-node:KafkaClient Received versions response from toniss-mbp-2.lan:9092 +2ms
  kafka-node:KafkaClient setting api support to {"21":{"min":0,"max":0,"usable":false},"22":{"min":0,"max":0,"usable":false},"23":{"min":0,"max":0,"usable":false},"24":{"min":0,"max":0,"usable":false},"25":{"min":0,"max":0,"usable":false},"26":{"min":0,"max":0,"usable":false},"27":{"min":0,"max":0,"usable":false},"28":{"min":0,"max":0,"usable":false},"29":{"min":0,"max":0,"usable":false},"30":{"min":0,"max":0,"usable":false},"31":{"min":0,"max":0,"usable":false},"32":{"min":0,"max":0,"usable":false},"33":{"min":0,"max":0,"usable":false},"34":{"min":0,"max":0,"usable":false},"35":{"min":0,"max":0,"usable":false},"36":{"min":0,"max":0,"usable":false},"37":{"min":0,"max":0,"usable":false},"produce":{"min":0,"max":5,"usable":2},"fetch":{"min":0,"max":6,"usable":2},"offset":{"min":0,"max":2,"usable":0},"metadata":{"min":0,"max":5,"usable":0},"leader":{"min":0,"max":1,"usable":false},"stopReplica":{"min":0,"max":0,"usable":false},"updateMetadata":{"min":0,"max":4,"usable":false},"controlledShutdown":{"min":0,"max":1,"usable":false},"offsetCommit":{"min":0,"max":3,"usable":2},"offsetFetch":{"min":0,"max":3,"usable":1},"groupCoordinator":{"min":0,"max":1,"usable":0},"joinGroup":{"min":0,"max":2,"usable":0},"heartbeat":{"min":0,"max":1,"usable":0},"leaveGroup":{"min":0,"max":1,"usable":0},"syncGroup":{"min":0,"max":1,"usable":0},"describeGroups":{"min":0,"max":1,"usable":0},"listGroups":{"min":0,"max":1,"usable":0},"saslHandshake":{"min":0,"max":1,"usable":false},"apiVersions":{"min":0,"max":1,"usable":0},"createTopics":{"min":0,"max":2,"usable":false},"deleteTopics":{"min":0,"max":1,"usable":false}} +0ms
  kafka-node:KafkaClient broker is now ready +16ms
  kafka-node:KafkaClient Using V2 of produce +0ms
  kafka-node:Client refresh metadata currentAttempt 1 +0ms
  kafka-node:Client refresh metadata currentAttempt 2 +204ms
  kafka-node:Client refresh metadata currentAttempt 3 +401ms
  kafka-node:KafkaClient kafka-node-client reconnecting to toniss-mbp-2.lan:9093 +119ms
message: 5414
  kafka-node:KafkaClient compressing messages if needed +407ms
  kafka-node:KafkaClient checking payload topic/partitions has leaders +0ms
  kafka-node:KafkaClient found leaders for all +0ms
  kafka-node:KafkaClient grouped requests by 1 brokers ["0"] +0ms
  kafka-node:KafkaClient has apiSupport broker is ready +0ms
  kafka-node:KafkaClient Using V2 of produce +0ms
  kafka-node:Client refresh metadata currentAttempt 4 +278ms
  kafka-node:KafkaClient kafka-node-client reconnecting to toniss-mbp-2.lan:9093 +323ms

All works as expected, producing message: 5413 fails with BrokerNotAvailableError at first as broker 1 went down. We catch the error and retry sending the message. BrokerNotAvailableError also triggers a metadata update from KafkaClient.sendRequest sendToBroker:
https://github.com/SOHU-Co/kafka-node/blob/b2e3593373dd6b2b1bfcb448982c461b4a414fe1/lib/kafkaClient.js#L774-L776
Kafka-node receives new partition assignments and the retry will succeed as another (up) broker is now the leader for the partition.
The broken path 1 broker going down with Debug logging:
message: 5127
  kafka-node:KafkaClient compressing messages if needed +1s
  kafka-node:KafkaClient checking payload topic/partitions has leaders +0ms
  kafka-node:KafkaClient found leaders for all +0ms
  kafka-node:KafkaClient grouped requests by 1 brokers ["2"] +0ms
  kafka-node:KafkaClient has apiSupport broker is ready +0ms
  kafka-node:KafkaClient Using V2 of produce +0ms
  kafka-node:KafkaClient kafka-node-client reconnecting to localhost:9092 +304ms
  kafka-node:KafkaClient kafka-node-client reconnecting to toniss-mbp-2.lan:9092 +2ms
  kafka-node:KafkaClient kafka-node-client reconnecting to localhost:9092 +1s
  kafka-node:KafkaClient kafka-node-client reconnecting to toniss-mbp-2.lan:9092 +1ms
message: 5128
  kafka-node:KafkaClient compressing messages if needed +207ms
  kafka-node:KafkaClient checking payload topic/partitions has leaders +1ms
  kafka-node:KafkaClient found leaders for all +0ms
  kafka-node:KafkaClient grouped requests by 1 brokers ["0"] +0ms
  kafka-node:KafkaClient missing apiSupport waiting until broker is ready... +0ms
  kafka-node:KafkaClient kafka-node-client reconnecting to localhost:9092 +800ms
  kafka-node:KafkaClient kafka-node-client reconnecting to toniss-mbp-2.lan:9092 +1ms
  kafka-node:KafkaClient kafka-node-client reconnecting to localhost:9092 +1s
  kafka-node:KafkaClient kafka-node-client reconnecting to toniss-mbp-2.lan:9092 +1ms
  kafka-node:KafkaClient kafka-node-client reconnecting to localhost:9092 +1s
  kafka-node:KafkaClient kafka-node-client reconnecting to toniss-mbp-2.lan:9092 +0ms
  kafka-node:KafkaClient kafka-node-client reconnecting to localhost:9092 +1s
  kafka-node:KafkaClient kafka-node-client reconnecting to toniss-mbp-2.lan:9092 +1ms
  kafka-node:KafkaClient kafka-node-client reconnecting to localhost:9092 +1s
  kafka-node:KafkaClient kafka-node-client reconnecting to toniss-mbp-2.lan:9092 +1ms
  kafka-node:KafkaClient kafka-node-client reconnecting to toniss-mbp-2.lan:9092 +1s
  kafka-node:KafkaClient kafka-node-client reconnecting to localhost:9092 +0ms
  kafka-node:KafkaClient kafka-node-client reconnecting to localhost:9092 +1s
  kafka-node:KafkaClient kafka-node-client reconnecting to toniss-mbp-2.lan:9092 +1ms
  kafka-node:KafkaClient kafka-node-client reconnecting to localhost:9092 +1s
  kafka-node:KafkaClient kafka-node-client reconnecting to toniss-mbp-2.lan:9092 +1ms
  kafka-node:KafkaClient kafka-node-client reconnecting to localhost:9092 +1s
  kafka-node:KafkaClient kafka-node-client reconnecting to toniss-mbp-2.lan:9092 +1ms
  kafka-node:KafkaClient kafka-node-client reconnecting to toniss-mbp-2.lan:9092 +1s
  kafka-node:KafkaClient kafka-node-client reconnecting to localhost:9092 +1ms
Received error: TimeoutError: Request timed out after 10000ms
  kafka-node:KafkaClient compressing messages if needed +184ms
  kafka-node:KafkaClient checking payload topic/partitions has leaders +0ms
  kafka-node:KafkaClient found leaders for all +0ms
  kafka-node:KafkaClient grouped requests by 1 brokers ["0"] +0ms
  kafka-node:KafkaClient missing apiSupport waiting until broker is ready... +0ms
  kafka-node:KafkaClient kafka-node-client reconnecting to toniss-mbp-2.lan:9092 +821ms
  kafka-node:KafkaClient kafka-node-client reconnecting to localhost:9092 +0ms
  kafka-node:KafkaClient kafka-node-client reconnecting to localhost:9092 +1s
  kafka-node:KafkaClient kafka-node-client reconnecting to toniss-mbp-2.lan:9092 +1ms
  kafka-node:KafkaClient kafka-node-client reconnecting to localhost:9092 +1s
  kafka-node:KafkaClient kafka-node-client reconnecting to toniss-mbp-2.lan:9092 +1ms
  kafka-node:KafkaClient kafka-node-client reconnecting to toniss-mbp-2.lan:9092 +1s
  kafka-node:KafkaClient kafka-node-client reconnecting to localhost:9092 +1ms
  kafka-node:KafkaClient kafka-node-client reconnecting to localhost:9092 +1s
  kafka-node:KafkaClient kafka-node-client reconnecting to toniss-mbp-2.lan:9092 +1ms
  kafka-node:KafkaClient kafka-node-client reconnecting to localhost:9092 +1s
  kafka-node:KafkaClient kafka-node-client reconnecting to toniss-mbp-2.lan:9092 +1ms
  kafka-node:KafkaClient kafka-node-client reconnecting to localhost:9092 +1s
  kafka-node:KafkaClient kafka-node-client reconnecting to toniss-mbp-2.lan:9092 +1ms
  kafka-node:KafkaClient kafka-node-client reconnecting to toniss-mbp-2.lan:9092 +1s
  kafka-node:KafkaClient kafka-node-client reconnecting to localhost:9092 +1ms
  kafka-node:KafkaClient kafka-node-client reconnecting to toniss-mbp-2.lan:9092 +1s
  kafka-node:KafkaClient kafka-node-client reconnecting to localhost:9092 +0ms
  kafka-node:KafkaClient kafka-node-client reconnecting to localhost:9092 +1s
  kafka-node:KafkaClient kafka-node-client reconnecting to toniss-mbp-2.lan:9092 +0ms
Received error: TimeoutError: Request timed out after 10000ms

Sending message: 5127 to broker 2 is successful, but before the next message is sent to broker 0 the retry function on broker 0 socket close is triggered, which creates a new BrokerWrapper that doesn't have apiSupport set:
https://github.com/SOHU-Co/kafka-node/blob/b2e3593373dd6b2b1bfcb448982c461b4a414fe1/lib/kafkaClient.js#L622-L633
So when it then tries to send a a message to broker 0 it triggers the waitUntilReady call in ensureBrokerReady in KafkaClient.sendRequest:
https://github.com/SOHU-Co/kafka-node/blob/b2e3593373dd6b2b1bfcb448982c461b4a414fe1/lib/kafkaClient.js#L814-L816
This sees that apiSupport is not set and waits for it to be set, but as broker 0 is down, this will never happen and then the timeout is triggered here:
https://github.com/SOHU-Co/kafka-node/blob/b2e3593373dd6b2b1bfcb448982c461b4a414fe1/lib/kafkaClient.js#L758-L761
We again catch the TimeoutError, retry to produce the message, but it gets stuck in the same place (in waitUntilReady) and we get another timeout etc. This will continue indefinitely or until broker 0 comes back up.
The root cause of the issue is that metadata is not updated in the broken path, which would make the message producing on retry go to the new leader of the partition. It keeps trying to send it to the broker that is down.
Potential fix
I could fix it locally by simply also triggering a this.refreshBrokerMetadata(); before the this.waitUntilReady(broker, callback); call, as that way after retry the message would go to the new leader. But I'm not sure it is the correct way to fix it, not that familiar with the code base yet.
It also looks a bit odd that sendToBroker in KafkaClient.sendRequest also does a broker.isReady() check and just returns:
https://github.com/SOHU-Co/kafka-node/blob/b2e3593373dd6b2b1bfcb448982c461b4a414fe1/lib/kafkaClient.js#L780-L783
Whereas ensureBrokerReady waits for it to be ready. Maybe these should be unified?
Alternative solution would be to maybe trigger metadata refresh from the retry function that runs on socket close / end?
Environment

Node version: 8.11.3
Kafka-node version: 2.6.1
Kafka version: 1.0.1

For specific cases also provide

Number of Brokers: 3
Number partitions for topic:

Include Sample Code to reproduce behavior
Not easy for me to add sample code as we've written our own small abstraction on top of HighLevelProducer, but the producer just sends a message every 1s keyed to an auto incrementing number (so that it would go to different partitions). The test topic had 13 partitions.
PS! This could explain some of the other issues reported about producer not doing a failover to another broker. For example the last comments at the bottom of this issue:
https://github.com/SOHU-Co/kafka-node/issues/948

@hyperlink Is the issue solved by https://github.com/SOHU-Co/kafka-node/pull/1345?

Yup, looks like it @HansonHH. 👍

@hyperlink when does this bug fix version release?

It’s already released as v5.0.0.

On Nov 18, 2019, at 11:06 PM, MaHao<EMAIL_ADDRESS>wrote:

@hyperlink when does this bug fix version release?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub, or unsubscribe.


BirdSeed integration

I found BirdSeed, which seems to be a promising one-does-it-all solution for customer engagement and analytics. Their pricing also is pretty fair, far from abusive.
Is anyone interested in having that integrated? Thumbs up, please!

I said get lost lootian, we are poor that's why we are programming i don't about others but for myself it's sure

Comment deleted and reported as spam.


GeoSwift Crashes

The following code snippet crashes in GeoSwift (tested in 2.1.0, 2.1.3, swift 3.2, swift 4.0):
let jsonString = "{\"type\":\"MultiPolygon\",\"coordinates\":[[[[-78.926467895507812,36.051319575025502],[-78.852289148724822,36.033005280682119],[-78.791885375976562,35.996896453738117],[-78.734207153320312,35.951329861522673],[-78.640823364257812,35.927980690382697],[-78.481521606445312,35.885712278670248],[-78.452682495117188,35.74316846139925],[-78.50833730594735,35.68130132015127],[-78.613357543945312,35.670685013302347],[-78.714981079101562,35.684071533140973],[-78.804244995117188,35.679609609368583],[-78.874276302296835,35.693002873745471],[-78.911361694335938,35.736480443001462],[-78.931961059570312,35.823380847706538],[-79.003372192382812,35.931316708569028],[-78.988265991210938,36.022446681758488],[-78.926467895507812,36.051319575025502]]]]}"
let jsonData = jsonString.data(using: .utf8)!
let json = try! JSONSerialization.jsonObject(with: jsonData, options: [])

guard let dictionary = json as? [String: AnyObject],
    let features = Geometry.fromGeoJSONDictionary(dictionary) else {
        fatalError()
}

let points = (features[0]
    .geometries![0]
    .boundary() as! GeometryCollection<LineString>)
    .geometries[0]
    .points

The crash doesn't always happen in the same place. Happy to provide more info as needed.

If it helps, the problem appears to be resolved if the boundary() call is not chained with anything else. I did receive this error at one point: "libc++abi.dylib: Pure virtual function called!" which leads me to believe some part of this chaining is calling a virtual function inside of a constructor or destructor. I just don't know how that's the cause or how to find it.
I did find this stackoverflow about it here: https://stackoverflow.com/questions/34051749/how-to-track-down-libcabi-dylib-pure-virtual-function-called-in-xcode
Will look into some of the suggestions to see if that leads to understanding what's happening.

Im getting a force unwrap crash on the line
let boundaryGEOM = GEOSBoundary_r(GEOS_HANDLE, self.geometry)!
Inside the func boundary() -> Geometry {

@jwilson85, while unrelated to the OP's issue, this is still a problem.
Unfortunately all those function use force unwrapping, and it will result in a crash whenever GEOS returns nil.
We could either change this functions to return nil, in case of failure, or to make them to throw an error. Both changes would be breaking changes tho.
Would you like to have a go at it?

@jwilson85 I believe the library does have some more force unwrapping happening on other files. But as a starting point, try to work on the file your pointed out, and if you find anywhere else, please feel free to change as you go.
Thanks!

I have never done a git hub PR before Do I need access from you? @vfn

@jwilson85 that's awesome! Please create a pull request https://github.com/GEOSwift/GEOSwift/pulls and we will review your changes. Thanks!

@jwilson85 if you haven't already done so, you may want to create a fork of this repo. You can push your changes there and then create the PR back to the main repo.

@vfn @jwilson85: I'm spending a few days working with @raugturi on a fix for this issue. We'll have a PR ready today or Monday with more info. The fix necessarily breaks the API, so we'll need to increment the major version number before releasing it. We've come up with a number of other ideas for this project as well, some of which would constitute fairly major changes to the API. Would anyone be interested in setting up a public Slack or other channel for having some discussion about what direction to go in?

@macdrevx I hope my merged PR helped

This was fixed by #100. It will be released with v3.0.0 since it's a breaking change.


Added Billing Product for image in EC2 compute driver

Added Billing Product for image in EC2 compute driver
Description
Added Billing Product param for register image method in EC2 compute driver
Status

done, ready for review

Checklist (tick everything that applies)

[x] Code linting (required, can be done after the PR checks)
[x] Documentation
[x] Tests
[ ] ICLA (required for bigger changes)

Hi @nirzari thanks for the contribution. this looks great. 👍


cmd/dlv: Revert 4e177b, use new flag name for debug logging options

cmd/dlv: Revert 4e177b, use new flag name for debug logging options

Previously to 4e177bb99acc511897f9cdbfc6cbc50d92ae4725 it was possible
to use --log without arguments to enable logging, this commit reenables
that use case.

The new functionality of the --log flag moved to a new flag name
--logx.

Fixes #1188

My only nit is the name logx. I'm fine with something more verbose like --log-output.

Done.

@aarzilli we should also note in the docs what the default log output is without this other flag specified.

Done.


Order page: Dose Unit doesn't show up in medication table

Should show as short name

Hey @mseaton
Here is an example of json:
{
  dose: 500,
  doseUnits: "Milligram per square meter",
  ...
}

Is there a way to get a short name or long name is ok?

@sabov there should be a way, yes.  Should I assume that this JSON is something that we created to represent the order set?  If so, then this is likely just the fully-specified name of a concept.  But Concepts have lots of different names associated with them, including a "Short Name", which is likely what we want here.  @mogoodrich may be able to provide more guidance this week, but I'd check with Mario on whether/how he has structured this.


[FLINK-1505] Separate reader API from result consumption

@gyfora, can you please rebase on this branch and verify that everything is still working as expected for you?
This PR separates the reader API (record and buffer readers) from result consumption (input gate). The buffer reader was a huge component with mixed responsibilities both as the runtime component to set up input channels for intermediate result consumption and as a lower-level user API to consume buffers/events.
The separation makes it easier for users of the API (e.g. flink-streaming) to extend the handling of low-level buffers and events. Gyula's initial feedback confirmed this.
In view of FLINK-1568, this PR makes it also easier to test the result consumption logic for failure scenarios.
I will rebase #356 on this branch.

Thank you!
I will try it over the weekend and give you feedback.

We have rebased and tried, it works fine for us, thank you. I will add several minor changes afterwards but thats just for our convenience.
So from my side
+1

+1 from me as well, works fine! Nice decoupling :)

Ok, thanks. I will merge this then.


HOTFIX: V/T Facility Spaces

Callum fixed the back end of this in CORE-186 (#1256) , however the actual value in the form was never changed accordingly

:tada: This PR is included in version 4.2.10 :tada:
The release is available on GitHub release
Your semantic-release bot :package::rocket:


Use milliseconds as the default unit for perf dashboard numbers

Nonseconds are too large and hard to immediately convert when reading graphs. If wanting more precision, one can opt to nonseconds manually.

Actually what I want is the UI's default display unit. @pzread pointed to me the proper place to fix.


Icon Issue in Konsole - recent update caused this

Konsole was updated on 8/19 and now this is an issue.
Who could resolve this im guessing KDE team but I am going to post here as well to see if you guys have some insight.
https://streamable.com/p52d1

This is not related to OMZ, I hope the people at Konsole can fix it.


Send transactions events to websocket channels

To let clients know in real-time about events, the eWallet should be able to forward the events it receives to websocket channels.

4 new websocket channels for transactions

all transactions
all transactions per account
all transactions per user
specific transaction by id

submit the events created and updated and send the  updated transaction


how to use functions feature within continuous conversation

Thank you for developing this powerful lib!
It always works well, but when I try to use functions feature, I' m in trouble.
I want to fulfill a continuous conversation with functions feature, for instance:

ask chatGPT what' s the time
chatGPT call my function to get current time
then chatGPT reply to me with the time that my function returns

Just like the example: https://openai.com/blog/function-calling-and-other-api-updates

Here is my test code:
  // build conversation and send to openAI
  conversation.add_function(get_current_time()).unwrap();
  let res = conversation
      .send_message_functions(ask)  // ask is "what' s the time now?"
      .await
      .unwrap()
      .message_choices;

about get_current_time:
/// get current time
///
/// * time - the time that user asks
#[gpt_function]
async fn get_current_time(time: String) -> Value {
    println!("AI uses param: {time}");
    return Ok(json!({
        "time":"10:30"
    }));
}

my function ( get_current_time ) was called successfully, but I could' t get a expected reply about current time.
message_functions' length is 1, content is empty str
called message().content also return empty str
history like this:

maybe need this?( I guess...)

and when I called send_message_functions again, error occur:

I tried again and again, but couldn't be able to solve it, hope to get help

and    src\api\chatgpt:95: 14 is here

Could you check if the issue still persists with version from the function-invocation-fix branch?

I write a testing code just now,  the issue still persists.
But I got a warning while running, do I use functions feature correctly?
Here are all about testing code:

main logic

  // some config code for client......

   let mut conversation = client.new_conversation();
    conversation.add_function(get_current_time()).unwrap();

    let res = conversation
        .send_message_functions("Please tell the current time.")
        .await
        .unwrap()
        .message_choices;

    println!("{}", res.len());
    for ele in res {
        println!("ele is: {}", ele.message.content);
    }
    println!("\nhistory is:{:#?}", conversation.history);

gpt_function

/// get current time
///
/// * time - the time that user asks
#[gpt_function]
async fn get_current_time(time: String) -> Result<Value> {
    println!("AI uses param: {time}");
    let result: serde_json::Value = serde_json::json!({
        "time":"10:30"
    });
    result
}

Cargo.toml

[package]
name = "test_gpt"
version = "0.1.0"
edition = "2021"

# See more keys and their definitions at https://doc.rust-lang.org/cargo/reference/manifest.html

[dependencies]
chatgpt_rs = { git = "https://github.com/Maxuss/chatgpt_rs", features = [
    "functions",
], branch = "function-invocation-fix" }
reqwest = { version = "0.11", features = ["json", "blocking"] }
tokio = { version = "1", features = ["full"] }
serde_json = { version = "1.0", features = ["raw_value"] }
serde = { version = "1.0", features = ["derive"] }

All output


SSH : Access denied

img: jessie-openmediavault-rock64-0.5.15-136-armhf
board: rock64 ram:1G
Problem: Can NOT login via ssh, but CAN login via a HDMI console
via ssh
try 1
login as: root
password: openmediavault
Access denied
try again, same.
using a monitor connected via HDMI to rock64
try 3
rock64 login: root
password: openmediavault
Access granted.
then I tpyed passwd and changed a new pass
and tried again via ssh
still denied.
Am I the only one facing this problem?

Ha, found the problem
"Permit root login" switch didn't on


Supervisor service not starting on boot...

This is not an issue with this playbook as such, however it seems the supervisor package for 16.04 currently does not correctly start the service on boot (some issue with move to systemd no doubt).
See answer 2 on the following page for more info:
https://unix.stackexchange.com/questions/281774/ubuntu-server-16-04-cannot-get-supervisor-to-start-automatically
The solution for now is to issue "systemctl enable supervisor.service" manually to get systemd to start the service on boot.  I am not sure if you'd rather wait for the issue to be resolved with supervisor on 16.04 or possibly include this step in your playbook as a workaround.
Thanks again,
Cathal.

Thanks for reporting this, I added a task to explicitly enable the supervisor service and after a reboot it looks good.