tell @jovo how to make card container titles like the square container titles.

font-size: 1.2em;
    padding: 0.4rem 1rem;
    width: 90%;
    margin: auto;
    text-align: center;
    font-family: 'Roboto', Arial, Helvetica, sans-serif;
    box-shadow: 0 0 10px rgba(0, 0, 0, 0.5);
    border: 2px solid rgba(255, 255, 255, 0.5);
    transition: 0.5s;
    background: rgba(0, 0, 0, 0.5);
    border-radius: 0;
    text-transform: uppercase;
    letter-spacing: .5px;

This is the .title ruleset, essentially. But it'll only work on .square .square-mask .title, so we can just duplicate this into another global class to use it in the cards.

@j6k4m8 i tried and failed.  little help?

fixed!


Some custom items look like they are enchanted but they are not

Some custom items have the enchanted animation on the icon for apparently no reason.
Screenshoot:

Edit: found what caused it: the function to blame is Item.setHandEquipped()

I'm closing this since you opened a new issue - thanks.


[OpenAPI] OpenAPI spec

AS a developer
I WANT to see the OpenAPI doc
SO THAT I can implement relevant logics on both Playground and API apps, and send API requests to the API app

#20
#21
#22


Fix np.long for windows

Thanks for your contribution and we appreciate it a lot. The following instructions would make your pull request more healthy and more easily get feedback. If you do not understand some items, don't worry, just make the pull request and seek help from maintainers.
Motivation
np.long refer to int32 on Windows, which cause error when ground truth label is converted to torch tensor for loss computation.
Modification
use np.int64
BC-breaking (Optional)
No,
Use cases (Optional)
If this PR introduces a new feature, it is better to list some use cases here, and update the documentation.
Checklist

Pre-commit or other linting tools are used to fix the potential lint issues.
The modification is covered by complete unit tests. If not, please add more unit test to ensure the correctness.
If the modification has potential influence on downstream projects, this PR should be tested with downstream projects.
The documentation has been modified accordingly, like docstring or example tutorials.

Possibly we need more check because there seem to be multiple usages of 'np.long' but I am not very sure if all are related to this issue.


New package: Samsung.PhoneShare version <IP_ADDRESS>

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

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

The application doesn't seem to install anything.
Using the MSI or other exe in the folder shows a dependency on .NET 3.5

This appears to be a dependency

The application doesn't seem to install anything.
Using the MSI or other exe in the folder shows a dependency on .NET 3.5

This appears to be a dependency

You forgot to tag this.

[Policy] Dependencies

[Policy] Installer-Issue


Local compile server can't send large files to client

Trying to compile xlm-roberta-xl fails. This is probably because the model is either too large for the server to unpack or too large to send over
When the server sends the compiled model to the client to download, the server side gives the following error.
h11._util.LocalProtocolError: Too much data for declared Content-Length
On the client side:
requests.exceptions.ChunkedEncodingError: ('Connection broken: IncompleteRead([4957798400](tel:4957798400) bytes read, 10491 more expected)', IncompleteRead([4957798400](tel:4957798400) bytes read, 10491 more expected))

https://requests.readthedocs.io/en/latest/user/advanced/#streaming-uploads

GZip

I don't think I'm properly using the gzip middleware. This says I need a header


Failing test: Channel__history__should_return_a_PaginatedResult_page

When run locally with make test_macOS and make test_iOS:
✗ Channel__history__should_return_a_PaginatedResult_page, expected to have Array<ARTMessage> with count 1, got 0
✗ Channel__history__should_return_a_PaginatedResult_page, unexpected exception raised: *** -[__NSArray0 objectAtIndex:]: index 0 beyond bounds for empty NSArray

and
[19:05:43]: ▸     ✗ Channel__history__should_return_a_PaginatedResult_page, expected to have Array<ARTMessage> with count 1, got 0
[19:05:43]: ▸     ✗ Channel__history__should_return_a_PaginatedResult_page, unexpected exception raised: *** -[__NSArray0 objectAtIndex:]: index 0 beyond bounds for empty NSArray

┆Issue is synchronized with this Jira Bug by Unito

Closing outdated issue. The codebase changed drastically since then and all skipped tests were unskipped, see PRs for https://github.com/ably/ably-cocoa/issues/1406 and https://github.com/ably/ably-cocoa/issues/1848
If you encounter frequently failing test again, please create a new issue with a best guess why it might be happening.


trigger-integration-workflow: make cleanup-tags use tag parameter

Checklist

[x] All new jobs, commands, executors, parameters have descriptions
[x] Examples have been added for any significant new features
[x] README has been updated, if necessary

Motivation, issues
resolves #41

Description
Change trigger-integration-workflow to make its cleanup-tags option delete previous tags matching the tag parameter.

hmmmmm, actually, with this PR, the second line (git tag -d $(git tag -l "master-skip-master-*") isn't even necessary, as it will already be hit by the first wildcard..... maybe this isn't such an ideal fix. because sometimes folks don't want to delete those master tags at all....
let me try to take a look at refactoring some of this logic in a more holistic way, unless you have any other ideas @jrnail23
if there are specific tags you want to delete in the interim, i'd recommend doing so as a post-step—should be easy, since all the giit config commands will already have been run for you.

@iynere, the only way "master-skip-master-*" would get hit is if you specified tag: master, right?

what i'm saying is that, git tag -d $(git tag -l "<<parameters.tag>>-*" will already delete any tags that git tag -d $(git tag -l "master-skip-master-*" would delete @jrnail23 so the second command is redundant......
and the purpose of structuring it the original way, was specifically to avoid deleting tags like master-minor-etc or master-major-etc, which, with this PR, would be deleted

If you set up your job like this:
- orb-tools/trigger-integration-workflow:
    cleanup-tags: true
    tag: testing

that git command would end up looking like this:
# delete local tags
git tag -d $(git tag -l "testing-*")
git tag -d $(git tag -l "master-skip-master-*")
# fetch remote tags
git fetch
# delete remote tags
git push origin --delete $(git tag -l "testing-*") || true
git push origin --delete $(git tag -l "master-skip-master-*") || true

That would only delete tags named testing-* or master-skip-master-*

i'm talking about the edge case where tag = `master @jrnail23
which is the important one to look out for, since those tags have the possibility of being linked to a production orb release, in which case we wouldn't want to delete them

@iynere, I understand your concern about deleting master- tags unintentionally, but the other side of the coin here is that since I'm using tag: rc for this job on my master branch, I've got five tags named rc-patch-master-MY_SHA7 after only a day of development.
Your suggestion to run a post-step is very helpful, but I don't really want to put that in all five of the orbs I'm maintaining.
I'll experiment a bit here, and let you know what I learn from it.

@iynere: so it looks like post-steps aren't an effective substitute here. The actual cleanup-tags happens before the new integration tag is applied.  Running it in post-steps actually deletes the newly created INTEGRATION_TAG immediately upon creation.
Running it in pre-steps would seem preferable, but in that case, it's happening before the checkout, or any of the git config stuff is run by the job, so makes it a lot less workable.
I keep circling back to the idea of cleanup-tags already being an opt-in thing, but I understand that you wouldn't want to surprise anyone with breaking behavior, even if it fixes an existing bug.
Myself, I'm generally using your prescribed workflow (modified to use manual approvals to release patch/minor/major instead of the SemVer inference behavior), and using the default publish-version-tag behavior on dev-promote-prod, so I don't really care too much about keeping tags for integration test versions, particularly since the orbs are getting saved as artifacts in the lint-pack_validate_publish-dev workflow.
Anyway, I hope that helps you come up with an acceptable solution to cleaning up the cruft from test runs.

hmmm, let's just merge it—since orb-tools now creates different production release tags anyway @jrnail23
& this will all change / improve very soon anyway—once this is done https://github.com/CircleCI-Public/api-preview-docs/blob/master/designs-for-feedback/trigger-workflows-in-pipeline.md git tags will mostly go away here completely 🎉

@iynere Excellent.  And I'm looking forward to seeing what you come up with for the workflow triggering feature.


DNS Response Recorder?

Love this stuff: https://godoc.org/net/http/httptest#ResponseRecorder, makes doing (for instance) metrics a breeze. We should add something to dns to mimic this.

CoreDNS has this: https://github.com/miekg/coredns/blob/master/middleware/recorder.go

Also this should then sit in a dnstest/ sub dir

Any plans to add this?

Seems easy enough to write yourself: https://github.com/miekg/coredns/tree/master/middleware/pkg/dnsrecorder
Not sure if we should pull this into this lib.

I actually wrote something like coredns dnsrecorder, but I think it should be in lib because every person who want to test his handlers will write own implementation. I think this is why httptest exists in stdlib.

Ok. Let move it to here in dnstest sub package.

I can live without this - less code to maintain


[flutter_tools] allow applications to specify additional license files to be bundled into the application NOTICES automatically

Description
Currently the flutter tool will automatically bundle all software licenses for the dart dependencies into the aggregate NOTICES file. This PR adds the capability to specify additional licenses (perhaps for included assets) that should be included in this aggregate file, without manually incorporating these into the the package LICENSE/NOTICES file.
While developing a small game for myself, I noticed that the number of LICENSE files I needed to include if I intended to ship it was growing quite large, since almost every set of assets/audio have their own LICENSE. While some of these don't need to be included, I generally prefer crediting the authors where possible.
Originally I wasn't sure if it was feasible to combine these license files into the aggregate licenses. I was informed this is possilbe in https://github.com/flutter/flutter/issues/73363. Nevertheless, with such a large and changing asset set I would prefer to delegate this work to tooling instead of relying on manual copy paste.
Related Issues
https://github.com/flutter/flutter/issues/73363

Friendly ping @christopherfujino

Friendly ping @christopherfujino

@christopherfujino I updated the validation to check each list item for the correct type.

@christopherfujino I updated the validation to check each list item for the correct type.

@christopherfujino I updated the validation to check each list item for the correct type.

thanks, LGTM!

@christopherfujino I updated the validation to check each list item for the correct type.

thanks, LGTM!

Did we end up documenting this anywhere? The API docs have some mention of this under the licensing API but it would be good to have something more canonical (and which includes the pubspec.yaml features too).

Did we end up documenting this anywhere? The API docs have some mention of this under the licensing API but it would be good to have something more canonical (and which includes the pubspec.yaml features too).

Not yet! We also need to add it to the autocomplete APIs in the analyzer. I'll file two more follow up bugs
https://github.com/flutter/flutter/issues/74001
They might need to wait until this ends up in a release branch.

Not yet! We also need to add it to the autocomplete APIs in the analyzer. I'll file two more follow up bugs
https://github.com/flutter/flutter/issues/74001
They might need to wait until this ends up in a release branch.

@Hixie @jonahwilliams I'm a new Flutter developer and had the same issue with my web project.  Show License works at debug time, but not at runtime.
It Will be nice when this makes its way into the released tools, thank you!


Add link to OData repositories

Add link to OData repositories

Docs Build status updates of commit 784bf0a:
:warning: Validation status: warnings

File
Status
Preview URL
Details

Odata-docs/resources/support.md
:warning:Warning
View
Details

Odata-docs/resources/support.md

Line 2, Column 1: [Warning-author-missing] Missing required attribute: 'author'. Add the current author's GitHub ID.
Line 2, Column 1: [Suggestion-description-missing] Missing required attribute: 'description'.

For more details, please refer to the build report.
If you see build warnings/errors with permission issues, it might be due to single sign-on (SSO) enabled on Microsoft's GitHub organizations. Please follow instructions here to re-authorize your GitHub account to Docs Build.
Note: Broken links written as relative paths are included in the above build report. For broken links written as absolute paths or external URLs, see the broken link report.
Note: Your PR may contain errors or warnings unrelated to the files you changed. This happens when external dependencies like GitHub alias, Microsoft alias, cross repo links are updated. Please use these instructions to resolve them.
For any questions, please:Try searching in the Docs contributor and Admin GuideSee the frequently asked questionsPost your question in the Docs support channel


WIP: Feature: Parse and utilize tags to add more meta-data existing models and define new models

Hello @sedruk! Thanks for updating this PR. We checked the lines you've touched for PEP 8 issues, and found:

In the file twitch/parser.py:

Line 220:57: E251 unexpected spaces around keyword / parameter equals
Line 248:80: E501 line too long (80 > 79 characters)


Remove error kind?

For future reference: the design of combining Error, ErrorKind and BoxError into a single catch-all type might not be the right way to go about it.
An alternative would be to only have a single catch-all error type that stores a message + StatusCode, so that it can wrap any other error type. That way we don't have to worry about all the error kind stuff and can simplify error construction throughout.
@dignifiedquire mentioned yesterday that error construction takes a lot of parameters, and I agree. This could be a way to improve that.

Done!


Option to store http responses to file

This PR adds changes in order to add these two options (Context: #177):
   -sr, -store-response              store http response to output directory
   -srd, -store-response-dir string  store http response to custom directory

For now the PR creates the output directory (katana_responses by default, but can be changed with -srd option), then it creates correctly the specific subfolders for each domain (e.g. katana_responses/www.edoardoottavianelli.it) and it also creates the file named as the hash of the URL.
E.g.:
For the URL https://www.edoardoottavianelli.it/post/post6/post6.html, this is the file created: katana_responses/www.edoardoottavianelli.it/3270ccbc882c5239fcaa7c801503df606e8979be (sha1 hash of URL)
The problem is that the output is built upon the struct Result:
// Result is a result structure for the crawler
type Result struct {
	// Timestamp is the current timestamp
	Timestamp time.Time `json:"timestamp,omitempty"`
	// Method is the method for the result
	Method string `json:"method,omitempty"`
	// Body contains the body for the request
	Body string `json:"body,omitempty"`
	// URL is the URL of the result
	URL string `json:"endpoint,omitempty"`
	// Source is the source for the result
	Source string `json:"source,omitempty"`
	// Tag is the tag for the result
	Tag string `json:"tag,omitempty"`
	// Attribute is the attribute for the result
	Attribute string `json:"attribute,omitempty"`
}

and this struct is not suitable for this type of output. I would like to write something similar to meg output:
▶ head -n 20 ./out/example.com/45ed6f717d44385c5e9c539b0ad8dc71771780e0
http://example.com/robots.txt

> GET /robots.txt HTTP/1.1
> Host: example.com

< HTTP/1.1 404 Not Found
< Expires: Sat, 06 Jan 2018 01:05:38 GMT
< Server: ECS (lga/13A2)
< Accept-Ranges: bytes
< Cache-Control: max-age=604800
< Content-Type: text/*
< Content-Length: 1270
< Date: Sat, 30 Dec 2017 01:05:38 GMT
< Last-Modified: Sun, 24 Dec 2017 06:53:36 GMT
< X-Cache: 404-HIT

<!doctype html>
<html>
<head>

Do you have any suggestions? @ehsandeep @Mzack9999
This PR closes #177.

@edoardottt the above example was for response format, for the filenames, we are adopting httpx to follow meg format in https://github.com/projectdiscovery/httpx/pull/848 and something to adopt here as well.

Hi @ehsandeep, just a lil bit of context.
I'm trying to add the feature with as few changes as possible, however there are some constraints.

In Headless mode for now it's not possible to store the responses because the responses provided in headless mode lack some important information (such as the status, the protocol used) and I don't know how to store them. It might be possible to do this, but of course the format of the responses won't be the same. Let me know how you want to handle that.

katana prints the results on the command line, but it doesn't perform an HTTP request for all of them. I don't know if I'm wrong on this but using a proxy I see 12 results on the CLI and 6 requests made by katana (I guess due to DOM parsing). Because of this, the results in the responses folder and the results printed on the cli don't match.
For this I've used https://www.edoardoottavianelli.it/ as test case.

Test command
echo "https://www.edoardoottavianelli.it/" | ./katana -sr -proxy http://<IP_ADDRESS>:8888

Katana CLI output:
...
[WRN] Developers assume no liability and are not responsible for any misuse or damage.
https://www.edoardoottavianelli.it/blog.html
https://www.edoardoottavianelli.it/cve.html
https://www.edoardoottavianelli.it/aboutme.html
https://www.edoardoottavianelli.it/cv.html
https://www.edoardoottavianelli.it/
https://www.edoardoottavianelli.it/index.html
https://www.edoardoottavianelli.it/CVE-2022-44019/index.html
https://www.edoardoottavianelli.it/CVE-2022-41392/index.html
https://www.edoardoottavianelli.it/post/post7/post7.html
https://www.edoardoottavianelli.it/post/post6/post6.html
https://www.edoardoottavianelli.it/post/post5/post5.html
https://www.edoardoottavianelli.it/post/post1/post1.html

Proxify logs
/tmp/logs> head -n 1 www.edoardoottavianelli.it:443-*
==> www.edoardoottavianelli.it:443-cdsvqfe2g8ihqu0g3pdg.txt <==
GET / HTTP/1.1

==> www.edoardoottavianelli.it:443-cdsvqfm2g8ihqu0g3pe0.txt <==
GET /cve.html HTTP/1.1

==> www.edoardoottavianelli.it:443-cdsvqfu2g8ihqu0g3peg.txt <==
GET /blog.html HTTP/1.1

==> www.edoardoottavianelli.it:443-cdsvqg62g8ihqu0g3pf0.txt <==
GET /aboutme.html HTTP/1.1

==> www.edoardoottavianelli.it:443-cdsvqge2g8ihqu0g3pfg.txt <==
GET /cv.html HTTP/1.1

==> www.edoardoottavianelli.it:443-cdsvqgm2g8ihqu0g3pg0.txt <==
GET / HTTP/1.1

Awesome, lack of this feature was the reason I didn't use katana yet. Merge please?


Azure Cloud Shell after remove will auto add back to the list

Windows Terminal version (or Windows build number)
1.9.1942.0
Other Software
No response
Steps to reproduce

open settings.json
comment / remove Azure cloud shell block from the list

Expected Behavior
Azure Cloud Shell should remove without problem
Actual Behavior
Azure Cloud Shell automatic add back to the list

    "disabledProfileSources":
    [
        "Windows.Terminal.Azure"
    ],

can fix it

hi @peach-lasagna , will test it later
thanks for advices

Yep, the azure shell is a Dynamic Profile. You'll need to either disable the profile source, or add
"hidden": true

to the profile to remove it from the dropdown.


Why test fails?

Problem description
$ npm test

><EMAIL_ADDRESS>test /Users/name/Projects/material-ui
> cross-env NODE_ENV=test babel-node test/index.js

  ․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․
  ․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․Warning: Failed context type: Required context `muiTheme` was not specified in `Paper`.
    in Paper
․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․
  ․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․․
  ․․․․․․․․․․․․․․Warning: Exception thrown by hook while handling onSetChildren: Invariant Violation: Expected onBeforeMountComponent() parent and onSetChildren() to be consistent (15 has parents 0 and 13).
Invariant Violation: Expected onBeforeMountComponent() parent and onSetChildren() to be consistent (15 has parents 0 and 13).
    at invariant (/Users/name/Projects/material-ui/node_modules/fbjs/lib/invariant.js:38:15)
    at Object.ReactComponentTreeHook.onSetChildren (/Users/name/Projects/material-ui/node_modules/react/lib/ReactComponentTreeHook.js:202:78)
    at callHook (/Users/name/Projects/material-ui/node_modules/react/lib/ReactDebugTool.js:28:8)
    at emitEvent (/Users/name/Projects/material-ui/node_modules/react/lib/ReactDebugTool.js:40:7)
    at Object.ReactDebugTool.onSetChildren (/Users/name/Projects/material-ui/node_modules/react/lib/ReactDebugTool.js:263:5)
    at ReactDOMComponent.setChildrenForInstrumentation (/Users/name/Projects/material-ui/node_modules/react/lib/ReactMultiChild.js:159:38)
    at ReactDOMComponent.ReactMultiChild.Mixin._updateChildren (/Users/name/Projects/material-ui/node_modules/react/lib/ReactMultiChild.js:362:39)
    at ReactDOMComponent.ReactMultiChild.Mixin.updateChildren (/Users/name/Projects/material-ui/node_modules/react/lib/ReactMultiChild.js:301:12)
    at ReactDOMComponent.Mixin._updateDOMChildren (/Users/name/Projects/material-ui/node_modules/react/lib/ReactDOMComponent.js:941:12)
    at ReactDOMComponent.Mixin.updateComponent (/Users/name/Projects/material-ui/node_modules/react/lib/ReactDOMComponent.js:759:10)
․․․․․․․․․

  334 passing (4s)
  1 failing

  1) <RaisedButton /> renders an enhanced button inside paper:
     TypeError: Cannot read property 'prepareStyles' of undefined
      at Paper.render (src/Paper/Paper.js:72:12)
      at [object Object].ReactCompositeComponentMixin._renderValidatedComponentWithoutOwnerOrContext (node_modules/react/lib/ReactCompositeComponent.js:808:34)
      at [object Object].ReactCompositeComponentMixin._renderValidatedComponent (node_modules/react/lib/ReactCompositeComponent.js:835:34)
      at [object Object].ReactCompositeComponentMixin.performInitialMount (node_modules/react/lib/ReactCompositeComponent.js:372:30)
      at [object Object].ReactCompositeComponentMixin.mountComponent (node_modules/react/lib/ReactCompositeComponent.js:260:21)
      at Object.ReactReconciler.mountComponent (node_modules/react/lib/ReactReconciler.js:47:35)
      at node_modules/react/lib/ReactServerRendering.js:46:36
      at ReactServerRenderingTransaction.Mixin.perform (node_modules/react/lib/Transaction.js:138:20)
      at renderToStringImpl (node_modules/react/lib/ReactServerRendering.js:44:24)
      at renderToStaticMarkup (node_modules/react/lib/ReactServerRendering.js:84:10)

npm ERR! Test failed.  See above for more details.

Steps to reproduce
diff --git a/src/RaisedButton/RaisedButton.spec.js b/src/RaisedButton/RaisedButton.spec.js
index 1fec3e5..807b2ab 100644
--- a/src/RaisedButton/RaisedButton.spec.js
+++ b/src/RaisedButton/RaisedButton.spec.js
@@ -19,6 +19,7 @@ describe('<RaisedButton />', () => {
     const wrapper = shallowWithContext(
       <RaisedButton>Button</RaisedButton>
     );
+    console.log(wrapper.html());
     assert.ok(wrapper.is('Paper'));
     assert.ok(wrapper.childAt(0).is('EnhancedButton'));
   });

Versions

Material-UI: master
React: master
Browser: -

.html() is valid method
https://github.com/airbnb/enzyme/blob/master/docs/api/ShallowWrapper/html.md

I think that .html() is making enzyme render some level deeper of the react tree.
That's breaking the encapsulation of the Paper element, he tries to render it.
The best option here seems to use the mount API.

@oliviertassinari thx!
import React from 'react';
import { expect } from 'chai';
import { mount } from 'enzyme';
import getMuiTheme from 'material-ui/styles/getMuiTheme';

  const mountWithContext = (node) => mount(node, {
    context: { muiTheme },
    childContextTypes: { muiTheme: React.PropTypes.object },
  });


wrong contour lines with Curvilinear data when units of X coord not Longitude

Reported by ansley b manke on 18 Sep 2009 17:22 UTC
Reported by Patrick McGuire
let xb = x[yb = y[y=0:290:10](x=0:290:10]
let)
let xb2 = xb + 0*yb
let zb = I[* J[y=0:290:10](x=0:290:10])

contour/hlimits=-100:400:50 xb2+zb,xb2,zb
The plot draws some of the contours over to the left past 0.
Migrated-From: http://dunkel.pmel.noaa.gov/trac/ferret/ticket/1688

Comment by ansley.b.manke on 22 Sep 2009 16:18 UTC
Another example with FILL

let xb = x[yb = y[y=0:290:10](x=0:290:10]
let)
let xb2 = xb + 0*yb
let zb = I[* J[y=0:290:10](x=0:290:10])
fill/hlimits=-100:400:50 0.0000001*(xb2+zb)^3,xb2,zb

This is fixed in routines fer/plt/load_curvilienar.F, fer/plt/curv_coord_sub.F, fer/plt/curv_coord_add_sub.F, taking care to separate the cases of curvilinear coordinates in units of longitude and modulo operations on longitudes, from the case where the curvilienar X coordinate is not modulo longitude.

Attachment from ansley.b.manke on 18 Sep 2009 17:22 UTC
the plot from the example script
REPLACE THIS TEXT WITH UPLOADED FILE ./attachments/TRAC_1688_GIT_960/contourbug.gif


Add command to apply a label to an issue

Closes #48

@sgnn7 I decided to work "issue-not-found" error handling into this story since it was relevant. Any changes to files other than cmd/label.go are related to the addition of error handling.


Resize video (OpenGlView) on the fly

Hello again.
I am trying to implement a function to resize the video based on the resolutions that the camera is capable of supporting.
I have implemented a small function:
public void changeVideoResolution (int width, int height) {
    prepareVideoEncoder (width, height, fps, bitRate, rotation, hardwareRotation,
            iFrameInterval, formatVideoEncoder, -1, -1);
  }
And to apply it I do the following:
rtspServerCam !!. changeVideoResolution (176, 144)
rtspServerCam !!. replaceGlInterface (rtspServerCam !!. glInterface)
Although it works, I have detected that sometimes (I don't know which ones yet), the application goes black and the application crashes.
Is there any other way to make this image resize?
Thanks again!!!

First of all.
Resize video on fly is not possible for stream because RTMP and RTSP need inform to server resolution used in stream before you start it (this is specified in protocol). The reason is because a player need know it to reproduce the video.
This feature should be developed in server side where you have multiple endpoint and player can change endpoint on fly to reproduce other resolution.
For example, you can do it with wowza server. Also, others stream platforms like youtube or twitch can do it.
If you want change resolution in client side you only can stop stream totally and re start with other resolution.

Ok, but it does work. The problem is that sometimes the screen is blocked
and I have not been able to determine under what circumstances it occurs.
El sáb., 16 may. 2020 a las 13:14, Pedro Sánchez<EMAIL_ADDRESS>escribió:

First of all.
Resize video on fly is not possible for stream because RTMP and RTSP need
inform to server resolution used in stream before you start it (this is
specified in protocol). The reason is because a player need know it to
reproduce the video.
This feature should be developed in server side where you have multiple
endpoint and player can change endpoint on fly to reproduce other
resolution.
For example, you can do it with wowza server. Also, others stream
platforms like youtube or twitch can do it.
If you want change resolution in client side you only can stop stream
totally and re start with other resolution.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/pedroSG94/rtmp-rtsp-stream-client-java/issues/569#issuecomment-629629520,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AA44XQJB4CO557KTVYSZ25TRRZYQXANCNFSM4NC2NE6A
.

Can you share a logcat of your crash?

@Racker79  -- did you ever make any progress here? I'm interested in the code that you were using.


Templates should rename to themes

Templates should rename to themes , becuse it might confuse with page templates. let's make it theme

You can assign the task to me

@dazunE agreed. 👍
Send me a PR.


markdown URLs no longer highlighted

It seems like in Markdown URLs are no longer highlighted?

Hold on - seems to be a conflict between different color schemes... will investigate further.

I'm not opposed to supporting this if someone wants to do a pr.

Closing, as I wasn't able to find anything on CommonMark about this syntax for links. Please feel free to re-open if I missed something.


pre-launch regression testing results

[x] examples/simple
[x] change-wallet-provider
[x] change-account
[x] change-network
[x] transaction
[x] configuration/auto-connect-to-nami
[x] configuration/auto-connect-to-eternl
[x] configuration/auto-connect-to-gero
[x] configuration/auto-connect-to-flint
[x] configuration/no-auto-reconnect
[x] configuration/auto-connect-and-reconnect
[x] configuration/only-mainnet
[x] configuration/only-testnet
[x] configuration/mainnet-and-testnet
[x] theming/custom-styles
[x] manual/toaster-operations
[x] manual/your-own-wallet-provider-selector
[ ] lucid/always-succeed
[ ] lucid/matching-keyhash
[ ] lucid/matching-numbers
[x] lucid/simple-mint
[ ] lucid/parameterized-script
[x] lucid/sign-message

There are some tests that are failing
Lucid / Alway Succeed
Can lock, but not redeem UTxO

Cannot read properties of undefined (reading 'lenght')

Lucid / Matching Keyhash
Can lcok, but not redeem UTxO

UTxO not found

Lucid / Matching Numbers
Can lcok, but not redeem UTxO

Cannot read properties of undefined (reading 'lenght')

Lucid / Parameterized Script
Cannot mint

InsufficientCollateralBalance

Always Succeed. Preview network
transaction submit error ShelleyTxValidationError ShelleyBasedEraBabbage (
    ApplyTxError [
        UtxowFailure (
            FromAlonzoUtxowFail (
                NonOutputSupplimentaryDatums (
                    fromList [
                        SafeHash "923918e403bf43c34b4ef6b48eb2ee04babed17320d8d1b9ff9ad086e86f44ec"
                    ]
                ) (
                    fromList []
                )
            )
        ),
        UtxowFailure (
            FromAlonzoUtxowFail (
                ExtraRedeemers [
                    RdmrPtr Spend 0
                ]
            )
        ),
        UtxowFailure (
            FromAlonzoUtxowFail (
                PPViewHashesDontMatch (
                    SJust (
                        SafeHash "1b27d417046665a2ee5ee1d9158ecbb095aa446aecffacf572cfd2c682ab7bd4"
                    )
                ) (
                    SJust (
                        SafeHash "36afc2c20903edc903f0f6267cd59f9c0a1725249bb62921dd5233671694ea86"
                    )
                )
            )
        ),
        UtxowFailure (
            UtxoFailure (
                FromAlonzoUtxoFail (
                    ValueNotConservedUTxO (
                        Value 151882251 (
                            fromList []
                        )
                    ) (
                        Value 451882251 (
                            fromList []
                        )
                    )
                )
            )
        ),
        UtxowFailure (
            UtxoFailure (
                FromAlonzoUtxoFail (
                    BadInputsUTxO (
                        fromList [
                            TxIn (
                                TxId {
                                    _unTxId = SafeHash "198def3b549a55ef3e004de73f82fe41eb87c51e160598d945bbe86e0ba7f8e1"
                                }
                            ) (
                                TxIx 2
                            ),
                            TxIn (
                                TxId {
                                    _unTxId = SafeHash "e08cd43dc6108a53c17577b0d8c942cabc66cba7bc05bc0802c57315e180b3dc"
                                }
                            ) (
                                TxIx 0
                            )
                        ]
                    )
                )
            )
        ),
        UtxowFailure (
            UtxoFailure (
                FromAlonzoUtxoFail NoCollateralInputs
            )
        ),
        UtxowFailure (
            UtxoFailure (
                FromAlonzoUtxoFail (
                    InsufficientCollateral (
                        Coin 0
                    ) (
                        Coin 256557
                    )
                )
            )
        )
    ]
)

Matching Keyhash
transaction submit error ShelleyTxValidationError ShelleyBasedEraBabbage (
    ApplyTxError [
        UtxowFailure (
            UtxoFailure (
                FromAlonzoUtxoFail NoCollateralInputs
            )
        ),
        UtxowFailure (
            UtxoFailure (
                FromAlonzoUtxoFail (
                    InsufficientCollateral (
                        Coin 0
                    ) (
                        Coin 262791
                    )
                )
            )
        )
    ]
)

All of the examples that aren't working are interacting with a smart contract. When downgrading to version 0.7.8, they work again. I opened an issue on this in the Lucid repo: https://github.com/spacebudz/lucid/issues/134.

seems to be working up to version 0.8.0, but not after.

Updated to 0.8.2, everything is working now!


lib: standardize use of lib and self

Things done:

Drop helpers in internal useage
Access nixvim's lib via self
Access the (un-extended) lib via lib

While I like the idea of having lib.nixvim access internally within our lib, keeping our lib (self) separate from the extended lib will be better in the long-term.
This is intended to simplify accessing a lib overlay without needing to first evaluate parts of our custom lib (#2328).
lib/types.nix is a bit of a special case, it isn't really part of our (lib.nixvim scoped) custom lib. Instead it is part of the lib extension overlay. Therefore we can use either strategy of passing it { lib = final; } or { lib = prev; inherit self; }. Feedback is welcome on which approach is preferred.

CI failures have highlighted some cases where we use our custom types within our nixvim scoped lib.
I wonder if types should once again be built within lib.nixvim, and then this final value can be merged later in the overlay... :thinking:


Applies new checkstyle to OVM3 module

The old checkstyle has already been removed and the module is now compliant with the new checkstyle.

Ping @remibergsma @borisroman
Tests

Build source including tests

[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 09:34 min
[INFO] Finished at: 2016-01-28T00:44:11+01:00
[INFO] Final Memory: 95M/570M
[INFO] ------------------------------------------------------------------------

Will do some more before before asking for a merge.

Please, hold on this. It built locally, but failed in the bubble because a file for some reason was not pushed correctly:
[INFO] ------------------------------------------------------------------------
[INFO] BUILD FAILURE
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 7:23.872s
[INFO] Finished at: Thu Jan 28 00:02:27 GMT 2016
[INFO] Final Memory: 59M/292M
[INFO] ------------------------------------------------------------------------
[ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.2:compile (default-compile) on project cloud-plugin-hypervisor-ovm3: Compilation failure
[ERROR] /data/git/cs2/cosmic/cosmic-plugin-hypervisor-ovm3/src/main/java/com/cloud/hypervisor/ovm3/objects/PoolOCFS2.java:[26,7] error: class PoolOcfS2 is public, should be declared in
a file named PoolOcfS2.java

The file on my mac:
sbpltk1zffh04:cosmic-plugin-hypervisor-ovm3 wrodrigues$ ls -lart ./src/main/java/com/cloud/hypervisor/ovm3/objects/PoolOcfS2.java
-rw-r--r--  1 wrodrigues  SBP\Domain Users  4727 Jan 27 23:37 ./src/main/java/com/cloud/hypervisor/ovm3/objects/PoolOcfS2.java

But the file on github:

Ping @borisroman @remibergsma @miguelaferreira
Fixed the file name issue.
INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 8:27.752s
[INFO] Finished at: Thu Jan 28 06:55:20 GMT 2016
[INFO] Final Memory: 80M/417M
[INFO] ------------------------------------------------------------------------
[root@cs2 cosmic]#

Will deploy DC; Networks; and VMs

Built RPMs from source
Deployed DC
Deployed isolated network and VM

Will run some integration tests.

Some tests executed:
[root@cs2 integration]# less /tmp//MarvinLogs/test_vm_life_cycle_SX1HJV/results.txt
Test router internal advanced zone ... === TestName: test_02_router_internal_adv | Status : SUCCESS ===
ok
Test restart network ... === TestName: test_03_restart_network_cleanup | Status : SUCCESS ===
ok
Test router basic setup ... === TestName: test_05_router_basic | Status : SUCCESS ===
ok
Test router advanced setup ... === TestName: test_06_router_advanced | Status : SUCCESS ===
ok
Test stop router ... === TestName: test_07_stop_router | Status : SUCCESS ===
ok
Test start router ... === TestName: test_08_start_router | Status : SUCCESS ===
ok
Test reboot router ... === TestName: test_09_reboot_router | Status : SUCCESS ===
ok
Test reset virtual machine on reboot ... === TestName: test_01_reset_vm_on_reboot | Status : SUCCESS ===
ok
Test advanced zone virtual router ... === TestName: test_advZoneVirtualRouter | Status : SUCCESS ===
ok
Test Deploy Virtual Machine ... === TestName: test_deploy_vm | Status : SUCCESS ===
ok
Test Multiple Deploy Virtual Machine ... === TestName: test_deploy_vm_multiple | Status : SUCCESS ===
ok
Test Stop Virtual Machine ... === TestName: test_01_stop_vm | Status : SUCCESS ===
ok
Test Start Virtual Machine ... === TestName: test_02_start_vm | Status : SUCCESS ===
ok
Test Reboot Virtual Machine ... === TestName: test_03_reboot_vm | Status : SUCCESS ===
ok
Test destroy Virtual Machine ... === TestName: test_06_destroy_vm | Status : SUCCESS ===
ok
Test recover Virtual Machine ... === TestName: test_07_restore_vm | Status : SUCCESS ===
ok
Test migrate VM ... SKIP: At least two hosts should be present in the zone for migration
Test destroy(expunge) Virtual Machine ... === TestName: test_09_expunge_vm | Status : SUCCESS ===
ok

----------------------------------------------------------------------
Ran 18 tests in 2772.219s

OK (SKIP=1)
/tmp//MarvinLogs/test_vm_life_cycle_SX1HJV/results.txt (END)

Ping @borisroman @remibergsma
Can we get this one merged? :)

LGTM :+1:


Allow user to toggle between noise-free and noisy observations

At present, the code assumes the inputs/targets are noise-free, and attempts to exactly interpolate between them. If this cannot be done due to a nearly singular covariance matrix, the method adds an increasing noise term to the diagonal successively until the matrix can be inverted. One improvement to this would be to allow the user to choose between several options: (1) noise-free, do not add noise if matrix is singular and raise an exception, (2) noise-free, add noise only as needed to stabilize the matrix inversion [this is the current behavior], (3) noise-free but let noise be a hyperparameter to be optimized [likely to be similar to the current behavior but included as an option to give user more control], (4) noisy observations with a single noise level specified by the user and not changed during hyperparameter optimization, and (5) noisy observations with the noise value potentially different for each target value but still not changed during hyperparameter optimization.

Additionally, a nice feature along these lines would be to implement (6) pivoting to stabilize Cholesky decomposition and automatically omit data points that are too close to each other. I have a simple Python implementation that does this, and it works very nicely. There is a LAPACK version of the Cholesky algorithm with pivoting (dpstrf), but it is more recent and thus is not supported in Scipy at the moment. So this will involve writing the glue code that is needed to use the LAPACK routine and ensuring that we have an appropriate LAPACK version.

Better handling of the noise term has been added on a feature branch and will be merged into devel -- the code exposes an option to set the jitter parameter to either zero (fit the data exactly), a fixed noise level (the case where the observations have a known uncertainty level), or the adaptive approach implemented previously. This feature is needed to do the MICE procedure for experimental design, as the procedure adds a fixed noise level to smooth the observations to stabilize the MICE criterion.

This has been mostly addressed in PR #81. Still need to work on the pivoted Cholesky factorization.


feat(atmo): AppSource returns a list of applications

Closes #117
This is a work in progress PR

This PR is now ready for a review


Add Postgres Autoscalar Icon

Notes for Reviewers
This PR fixes #8750
Signed commits

[x] Yes, I signed my commits.

Thanks, @Akshun-01!


created set matrix zero

I have just added the optimised and working java code for the same question..please merge my pull request..and thanx for assigning this to me

@tanus786  I have just added the optimised and working java code for the same question..please merge my pull request..and thanx for assigning this to me

Great work @Sarumathi02 please give this repo a star if it really helped you to complete your PR.
Also follow me for follow back if you want to get connected with me for any such open source contribution program. Thank you 😊


adding a line break in a string template adds unnecessary quotes

Adding a line break before
        throw 'Number of passed arguments (${
            query.argumentValues == null ? 0 : query.argumentValues.length}) doesn\'t match the number of used named arguments (${query.namedArguments.length}).';
//                                                                        ^

results in
        throw 'Number of passed arguments (${
            query.argumentValues == null ? 0 : query.argumentValues.length'
        '}) doesn\'t match the number of used named arguments (${query.namedArguments.length}).';

with two redundant ' before and after the added line break.

@zoechi What made you think this is a bug in SDK? ;)
SDK doesn't include any editor where you could type Enter.

@alexander-doroshko Hard to tell where the work of the analyzer ends and the IDE begins for me. Do you think this is an IDE bug?

Yes, typing is handled by the IDE.
Server used for code highlighting, errors and quick fixes, code completion, go to declaration, find usages, intention actions, line markers and refactorings. But some part of each feature is anyway implemented at IDE level and in some cases it is difficult for users to guess who is responsible for the bug.


Test against the http2jp/hpack-test-case

Now that this project contributes to http2jp/hpack-test-case as per #71, it would be great if you could also run tests against one or more other implementations results to validate the implementation.

We already do: see the test fixtures.


Layout In which this group is used does not show a preview

I have implemented this library in my project no doubt it is awesome.
But the issue I am facing is the preview of the layout does not show up on android studio.
Below is the preview while segmented group Code is commented.

And below is preview while not commented:

It does not cause any error but really slows down the designing process.
Kindly solve the issue Cheers.

I understand your frustrations with it not showing in designer.
Do you have an example project I can test this out on?
Are there any sort of errors within designer that says the component can't be instantiated?
I've messed around with issues like this before and it can be extremely difficult to fix in designer because there is no "knobs" or adjustable parameters to fix it.

But, also try to clear cache in Android Studio, restart your machine and Android studio.
It may do nothing and all, but I just want to make sure that there's not some relic that is causing issues.

I really appreciate your quick response.
I ha e tried makin different projects but no use even the sample provided
by you do not show up on designer preview.
On Sat, Jul 13, 2019, 4:56 PM Addison Elliott<EMAIL_ADDRESS>wrote:

But, also try to clear cache in Android Studio, restart your machine and
Android studio.
It may do nothing and all, but I just want to make sure that there's not
some relic that is causing issues.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/addisonElliott/SegmentedButton/issues/15?email_source=notifications&email_token=AIZ7YUF6VEUCWJGFGWZ3LUTP7G7GVA5CNFSM4IC2T7WKYY3PNVWWK3TUL52HS4DFVREXG43VMVBW63LNMVXHJKTDN5WW2ZLOORPWSZGODZ3QI2A#issuecomment-511116392,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AIZ7YUEVI5YEYJ6QIVSA2BDP7G7GVANCNFSM4IC2T7WA
.

As many people suggest on StackOverflow changing SDK version or changing Theme.App.......... to Base.Theme.App.... may work...
no use...

Hmm, very odd. The sample project shows up on designer for me (I think). Let me do a bit of experimentation and get back to you. Maybe the latest Android SDK is causing issues or something?

I've discovered that the sample project is not displaying correctly for me either. I'm assuming some sort of change occurred in Android Studio to cause this because it did work at one point.
The exception I receive is: java.lang.ClassNotFoundException: codetail.graphics.drawables.LollipopDrawable. I've been debugging it but haven't had much success. Will keep my progress posted here.

Thank You  Mr.Addison I Really appreciate.

No problem. I'll start with I can't really get you an ETA for when this will be completed. It's a very odd and specific bug since it's a problem with Android Studio itself.
Here's the line of code that "offends" Android Studio: https://github.com/addisonElliott/SegmentedButton/blob/master/library/src/main/java/com/addisonelliott/segmentedbutton/SegmentedButton.java#L1308
Disabling that will make it work. I have no idea why it has a problem with this. I might even go the route of creating a brand new RippleDrawable class with a new package name to see if that's causing the issue.

I've debugged this for quite awhile and I have not the slightest idea what is going on. I submitted a bug report to Google and we'll see what happens.
https://issuetracker.google.com/issues/138310608

Was able to resolve this with a workaround, should be fixed in 3.1.5

Really Appreciate it as it works like a charm.
Admire your work Thank you


Problem with Github public registry

Hi!
I know this is basically not a specific problem of this project, BUT...
Github public image registry currently does not support non-authenticated pull access. This makes it hard to reference images in Dockerfiles. Since you already seem to maintain some images also on Docker Hub, I would like to ask, if you could update this project on Docker Hub
Thank you in advance!

Hi @gstolz , you should be able to docker pull ghcr.io/ironpeakservices/iron-scratch:1.0.1 now!


Add attribute iso3_codes to the country list

This PR adds the newly-added attribute iso3_codes of the nomenclature package to the list of (European) countries.
fyi @phackstock @GretchenSchowalter

Ah, tests are failing because the tests are run against nomenclature v0.9.1. Let's keep this PR on hold, bring in the other open PRs in nomenclature, then merge this PR.

Should I create a new release now, or wait until iamconsortium/nomenclature#237 is merged?


Move playbook.yml into app repo

This will allow users to write custom roles files in the local roles directory.
It will also allow us to VC the roles that we want to use inside of tape.

This is good 2 be merged.

What about fe_deploy?


How password hash sync works diagram or text below it is incorrect

In the "Detailed description of how password hash synchronization works" section, Step 4 in the diagram says that the MD4 password hash is an 8-byte binary hash but Step 4 in the text below the diagram says it's a 16-byte binary hash.  One of them needs to be corrected.

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

ID: f4c06608-fe23-4097-f78a-123667ac763f
Version Independent ID: e334ab72-d55e-87dd-3cdb-cd9d88d6a844
Content: Implement password hash synchronization with Azure AD Connect sync
Content Source: articles/active-directory/connect/active-directory-aadconnectsync-implement-password-hash-synchronization.md
Service: active-directory
GitHub Login: @billmath
Microsoft Alias: billmath

@VShrubowich Thanks for the feedback !  I have assigned this issue to content author to investigate and update the document as appropriate.


Deployed using new script but app does not populate reflect

I have tried deploying using the new script to our teams app. Everything seems to go through successfully but attempts at creating reflect after deployment results in the following:

Sorry.... didn't add it to the team. It now works


adding dual channel support

What does this Pull Request accomplish?
TODO: Include high-level description of the changes in this pull request.
Why should this Pull Request be merged?
TODO: Justify why this contribution should be part of the project.
What testing has been done?
TODO: Detail what testing has been done to ensure this submission meets requirements.

Measurement UI:
Created measurement UI with two different tabs one for protocol settings and other for measurement configuration.
The UI similar to the POC.
Plot legends enabled for the graphs.
Measurement Configuration:
Added the controls with same names as in measurement UI.
Measurement Results:
Added indicators for the graphs and crosstalk results.
Measurement Logic:
Implemented the logic in the linear method
Updated the Get UI details.vi and measurement details.vi
Testing:
Tested the measurement service in with CS and TI DUT with different protocols and got validated results.


Rebaseline incremental Java compilation tests after Guava upgrade

Rebaseline and re-enable performance tests disabled in https://github.com/gradle/gradle/pull/17480.

Thanks. I hate this process being so error-prone.

@bot-gradle test and merge please.

OK, I've already triggered a build for you.


Add support for field2d widget to simulate a field

Field2d doesn't simulate a field, it just is a shuffleboard component that shows a field. It is added in the big_refactor branch.


Video is not uploaded to S3 in Microsoft Azure

In AWS it works.

Fixed in https://github.com/aerokube/moon2/pull/147.


Unattend-lab vmvalidate-lab failed  for powershelllab-0.9.4

The script is keep failing when running the VMvalidate.test.ps1.
I run the unattend-lab -ignorePendingReboot.  The script created one vm already but it stopped at vmvalidation step.
I am running it on win 10 ent <IP_ADDRESS>2 build 18362

This project is now under new ownership. The 3.x version line is obsolete. Version 4.0.0 has been published to the PowerShell Gallery with new updates, configuration, and documentation. It is expected that this version will resolve most if not all of the problems you were experiencing. Read Updating for more information.
No further action will be taken on this issue and it will most likely be closed at some point. If you still have the same issue with the new version, then go ahead and open a new issue.

for future reference, you must have an execution policy that allows running scripts. This configuration has also been updated beginning with v4.0.0.


Support exporting non-fullchain cert file

Support the option to export the cert file as a standalone item, even if its content is already included in the fullchain file.

Thank you for reviewing. Could you please release a new version of this action?


Stable cognito user pool

Hi!
We create a Cogito UserPool before running integration tests, and random IDs complicate the process of finding a pool.
I added an environment variable MOTO_COGNITO_IDP_USER_POOL_ID_STRATEGY=HASH, setting which makes the ID of Cognito Userpool reproducible. I think this change will be useful to other moto users as well.

@bblommers, I will correct all comments and suggestions. I will try to do it within the next couple of weeks.

@bblommers , i fix all comments and add tests.

Codecov Report

Merging #5194 (6693570) into master (7c00654) will increase coverage by 0.06%.
The diff coverage is 100.00%.

@@            Coverage Diff             @@
##           master    #5194      +/-   ##
==========================================
+ Coverage   95.81%   95.87%   +0.06%
==========================================
  Files         688      688
  Lines       67829    67847      +18
==========================================
+ Hits        64993    65051      +58
+ Misses       2836     2796      -40

Flag
Coverage Δ

servertests
36.50% <73.68%> (?)

unittests
95.82% <100.00%> (+<0.01%)
:arrow_up:

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

moto/cognitoidp/models.py
95.36% <100.00%> (+0.01%)
:arrow_up:

moto/cognitoidp/utils.py
100.00% <100.00%> (ø)

moto/settings.py
74.19% <100.00%> (+0.86%)
:arrow_up:

moto/core/responses.py
94.40% <0.00%> (+0.49%)
:arrow_up:

moto/core/models.py
96.44% <0.00%> (+16.44%)
:arrow_up:

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 7c00654...6693570. Read the comment docs.


Fixed spelling and grammatical errors in the README.md

Closes #
📑 Description

✅ Checks

[x] My pull request adheres to the code style of this project
[x] My code requires changes to the documentation
[x] I have updated the documentation as required
[x] All the tests have passed

ℹ Additional Information

Hey @Wjozey, thanks for contributing to this project! Really sorry I couldn't see this earlier 🤕
Can you please pull the Github repo again and sync it with the current version?
Thanks!

@anuran-roy will do so.


ignore logfd/outfd streams in makeEnv()

Streams are allowed as logfd and outfd and work in most places, but not for npm.install which gets us to makeEnv() in lifecycle.js where outfd and/or logfd are passed to JSON.stringify() which fails on circular references (and is nonsense for Streams).
I believe that the appropriate thing to do is just ignore them in makeEnv() when they are Streams.

I thought perhaps I should explain the use-case here. This is for Ender which uses the NPM API.
Initially, Ender passed nulls for both logfd and outfd so as to prevent any stdout/stderr output from NPM. As of Node 0.6 that no longer worked properly and the process was left hanging so we switched to passing 1 for logfd and just put up with having the output, somewhere around Node 0.6.8 we had to do the same for outfd for the same reason.
Anyway, what I'm trying to do now is capture the output properly, so along with a call to npm.load() I'm creating a temporary log file for the session and passing the stream reference to logfd and outfd. Then when we're finished, if there were no errors the file is deleted. If there are any errors along the way the log file is left. This works fine except for npm.install() which goes through makeEnv() and tries to make a copy of the logfd and outfd references, which is OK if they are integers but not if they are stream references.
I hope that helps, please let me know if you need anything else.

I thought that I'd put together a (rather elaborate) demo program to show this problem, in the process I decided to also demonstrate other issues that we've encountered with logfd and outfd.
https://gist.github.com/1923131
The /* */ comments contain the relevant notes, other comments are to try and explain what it's doing.
I've expanded further than my original issue with using a net.Stream for logfd and outfd to show how using an actual fd is a problem and that using null is now broken (it worked on Node 0.4, didn't seem to matter the NPM version).
This is in lieu of actual test cases because as far as I can tell the programatic NPM API isn't tested directly.

Merged into master.

brilliant! thanks


Control app ingress

How can I control the ingress traffic for the function app running in the Container App Environment?  For example, I'd like to set ingress to be internal only for a few apps, while allowing external traffic for other apps.
I didn't see a way in the current Bicep template to control ingress options.

Currently ingress is managed by Functions and is enabled by default. This is not exposed to user as of today. Can you explain more about this ? why do you need ingress for function apps? Is this common customer scenario?

I see a few common scenarios:

the need to keep functions private to an enterprise.  With the current Azure Functions plans, this is typically done with either applying private endpoints to a Premium (EP) plan or hosting in an ASE.  The ASE allows for more control from a virtual network perspective, but imposes limits on event driven scaling.  Customers will opt for Premium (EP) to support inbound private endpoints and event driven scaling.
the need to compose several services in relation to an overall solution.  For example, a publicly/internet accessible HTTP-triggered function app that sends events/messages to a private Event Hub or Service Bus.  There is another private, non-internet accessible function which consumes from the Event Hub or Service Bus.  Only the HTTP-triggered function should be accessible via the internet or intranet.  The "backend" event/message consuming function should only be accessible from within the app environment.

The scenarios make sense! Let us evaluate them!

Feature Request - Enable Ingress


feat: Enable Hermes to work on iOS

Summary
This PR makes it possible to build iOS applications with Hermes. Note that it doesn't work with use_frameworks! just yet.
Fixes #27845 (by downgrading iOS deployment target for RCT-Folly to 9.0)
Fixes #28810 (as above)
Checklist:

[x] Adjust release scripts to create Hermes bytecode bundle
[x] Release new Hermes npm package that includes iOS files (unreleased right now, if you want to try locally, you have to clone Hermes and yarn link its master to this project)
[x] Test on a new React Native application in both Debug and Release (Device)
[x] Test on an RNTester application in both Debug and Release (Device)
[x] Add missing i386 to Hermes framework and enable Bitcode
[x] Inspect CI failures for possible regressions
[x] Resolve Folly issue as reported #27845 and #28810
[x] Release new Hermes and test against it that everything works

Changelog
[IOS] [FEATURE] - Enable Hermes on iOS
[INTERNAL] - Upgrade to CocoaPods 1.10.0 to resolve Xcode 12.0 issues
[INTERNAL] - Upgrade to Xcode 12.0 on the CircleCI
[INTERNAL] - Fix building RNTester in Release mode
[INTERNAL] - Fix build-time errors of libevent with use_frameworks!
[INTERNAL] - Introduce USE_HERMES variable and test all RNTester configurations on the CI
[INTERNAL] - Do not fetch CocoaPods repository since we're using CDN anyway
Test Plan
Turn on hermes_enabled to true in your Podfile, install pods, and run the iOS application. Your app should be running Hermes now.
Preview: (note "Engine: Hermes")

Thank you @alloy for your swift review, appreciate it! Now time to move it out of WIP stage

This looks pretty good to me, except for the line endings (I think that's the problem) for gradlew.bat?

I'm sorry, did I miss something? I though Apple didn't allow other JS engines than their own WebKit JS Engine to be used in iOS apps?

There will be bytecode instead of js code so i think it complies with apple policy
---Original---
From: "Marc<EMAIL_ADDRESS>Date: Mon, Sep 14, 2020 19:41 PM
To<EMAIL_ADDRESS>Cc: "Manual"<manual@noreply.github.com>;"Sunny<EMAIL_ADDRESS>Subject: Re: [facebook/react-native] feat: Enable Hermes to work on iOS (#29914)
I'm sorry, did I miss something? I though Apple didn't allow other JS engines than their own WebKit JS Engine to be used in iOS apps?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.

Code-wise it's ready. Will perform some testing tomorrow to ensure everything works as expected from the UX perspective and will update this PR with minor tweaks.
After that, this one is ready to be reviewed / merged.

Meanwhile, we're waiting for a new Hermes release that will make these tests pass. It should be up really soon.

@grabbou Heeey Mike, here is a fresh hermes-engine-darwin-v0.7.0.tgz. Would you mind testing if it works correctly with this PR?

Running RNTester in debug mode works. The react-native-xcode.sh script works as well and produces correct files.
Note: Currently, RNTester fails to build in release mode due to a link-time error. I am not sure whether this is a result of this PR, or whether RNTester is failing on master as well. I will double-check and let you know.
I think it likely that RNTester is failing on master too, because the react-native-xcode.sh script was broken for RNTester and didn't output any main.jsbundle. Fixed in this PR as well.

@grabbou Heeey Mike, here is a fresh built hermes-engine-darwin-v0.7.0.tgz. Would you mind testing if it works correctly with this PR? If it does then we will publish to npm.

@Huxpro thank you for releasing this - confirmed that it worked just fine.

I have updated the main PR description with two remaining todo items to do before this one is ready to go.

Hermes 0.7.0 has been published https://www.npmjs.com/package/hermes-engine/v/0.7.0

Cherry-picking https://github.com/facebook/react-native/pull/29477 to fix building in release mode.

Two TODOs resolved today. Pending TODO work to happen tomorrow.

If #29477 is cherry-picked to fix stuff, maybe it's time to merge it to give attribution to the OP?

@thymikee yes, that PR will be merged separately. I am going to remove it from this PR when I am done testing.

Two PRs shipped to Hermes today:
https://github.com/facebook/hermes/pull/363 and https://github.com/facebook/hermes/pull/364.
That should be everything needed to get this up and running.

Are there any benchmarks/performance comparisons between JSC and Hermes available?

@mrousavy too early, I will do that as soon as this lands.

Xcode 12 is a wider issue and will need to be addressed on a framework level. For now, my workaround works here in RNTester but will have to be removed before merging to master.
https://github.com/facebook/react-native/issues/29984

Waiting for a new release of Hermes with https://github.com/facebook/hermes/pull/354, https://github.com/facebook/hermes/pull/363, https://github.com/facebook/hermes/pull/364 and https://github.com/facebook/hermes/pull/365 released.

While everything works with all the Hermes PRs I have submitted, we need to address https://github.com/facebook/hermes/issues/368 before moving forward.
Hope we can make a conclusion real quick and optimise the size of the Hermes artifact so that it doesn't affect installation times. Discussions will happen in that issue and PRs for now, as there's not much left as a part of this PR.

Note: The CI will be failing as long as the Hermes package is not available online for broader use. Right now, it loads my package locally.

I was able to resolve RCT-Folly issue and I think this may resolve some other issues that were reported in the past, mainly:

https://github.com/facebook/react-native/issues/28810
https://github.com/facebook/react-native/issues/27845

TL;DR RCT-Folly has to be build targeting iOS 9.0 release, otherwise, it will result in an error of duplicated type definitions and macros caused by Time.h file.
This fix has been inspired by:

https://github.com/facebook/flipper/blob/master/FlipperKit.podspec#L20 (what Flipper uses as a deployment target)
https://github.com/facebook/flipper/issues/834

This PR is ready to go. We're waiting for Hermes to be released to CocoaPods so that we can use it here (instead of my local, symlinked version).

Unfortunately, there turned out to be a problem with how we release Hermes. The CocoaPods package didn't include all platforms and architectures - in other words, I was unable to run this PR with such package in all testing scenarios.
I have spent some time reworking CircleCI pipeline of Hermes (especially when it comes to releasing a new package). The PR is already and it's here: https://github.com/facebook/hermes/pull/393.
I have tested it works just fine with a Hermes package released after these changes, so I am hoping this one is really the last PR we need 🙏

Since https://github.com/facebook/hermes/pull/393 has been merged, this PR is ready for final review and shipping.

Note: Upgrading to CocoaPods 1.10.0 in this PR to resolve https://github.com/facebook/react-native/issues/29984

@grabbou Looking at the CI output, it doesn't look like the pod install step is using the Gemfile that locks the CP version, it should be bundle exec pod install. So perhaps it’s still using an older version of CP?

@grabbou Looking at the CI output, it doesn't look like the pod install step is using the Gemfile that locks the CP version, it should be bundle exec pod install. So perhaps it’s still using an older version of CP?

Correct, we should be using bundle exec there. I have an internal diff (external PR copy here: https://github.com/facebook/react-native/pull/30250) which makes this change, but it's currently blocked on Xcode 12.1.0 becoming available on our internal CI. Feel free to make the bundle exec change as part of this PR if necessary.

@hramos I'll do that - thank you @alloy for spotting it.

FYI @hramos, I bumped Xcode to 12 and it fixed the build time errors I was getting on the CI. I will rebase once your PR is merged and remove my commits.

The good news for anyone who is following this PR is - the build failures on CircleCI are finally gone! This week I spent on trying to understand why everything works and is green on my laptop and breaks on the CI.
My plan for tomorrow is to make both test_ios_unit and test_ios_unit_frameworks green and #shipit.

@grabbou no need to wait for my PR to land first, don't let that block you, I can rebase after your changes land. As for the failing Android tests, we landed some fixes to master recently.

Current status is:

This branch builds when building static libraries. When building dynamic frameworks it fails building the libevent framework, for this issue I have a PR up here: https://github.com/callstack/react-native/pull/26
After fixing that, I stumbled on the issue of RN master’s copy of JSI being out of sync with JSI that comes with hermes v0.7.1. Specifically this recent RN commit.
To at least try to get this PR into a mergeable state, I wanted to then switch to consumer Hermes from master, but ran into the issue of Hermes master failing to build for iOS. I’ve tracked the issue down to this Hermes commit which makes the hermesc binary a dependency, which we don’t build for iOS.

Reverting that commit does fix the iOS build again, but I’m unsure of the ramifications. The proper fix would be to first build the macOS artefacts and then re-use its hermesc artefact during the iOS build, but that might make this PR drag on again.

@Huxpro @TheSavior Do you have any thoughts on the best recourse/prioritization?
Possible options I see are the following:
Fastest turnaround time
This could technically be released in a stable RN release.

Revert the commit mentioned above in #2 in RN master.
Revert the commit mentioned above in #3 in hermes master.
Finish this PR by using the existing Hermes v0.7.1 release.

Medium turnaround time
This can not be released in a stable RN release.

Revert the commit mentioned above in #3 in hermes master.
Finish this PR by temporarily pointing the hermes dependency to hermes master.
Potentially make the proper fix to first build macOS artefacts and use the resulting hermesc binary.
[Soon-ish] release Hermes v0.7.2 with a JSI version matching RN master’s.
Update RN’s hermes dependency to the prebuilt version of v0.7.2.

Longest turnaround time
This can definitely be released in a stable RN release.

Revert the commit mentioned above in #3 in hermes master or make the proper fix to first build macOS artefacts and use the resulting hermesc binary.
Release Hermes v0.7.2 with a JSI version matching RN master’s.
Finish this PR by pointing RN’s hermes dependency to the prebuilt version of v0.7.2.

@alloy thanks for the detailed summary! It seems like the real road blocking issue was just the JSI getting out of sync by https://github.com/facebook/react-native/commit/d8b0e9d9ab401fb3a0b2486ef64c97420cd45051 and we only need to do 2 and 3 of the "longest turnaround time" option to get this PR rolling again.
We are trying to patch https://github.com/facebook/hermes/commit/73594b5f568567c7469c88316ca698ef6df21685 and its dependencies to Hermes release-v0.7 branch to hopefully have a v0.7.2 that is JSI compatible with RN master's. By this way we don't need to revert from either RN or Hermes master.

After fixing that, I stumbled on the issue of RN master’s copy of JSI being out of sync with JSI that comes with hermes v0.7.1.

It would be helpful to know what are the steps to repro so we can verify if the patch resolve the issue. I can still build RN Tester app on Android on RN master with the hermes-engine v0.7.1 npm package. Starting heap profiler does not crash the app but disabling it does. I'm not sure if that is the crash you encountered or another.

To at least try to get this PR into a mergeable state, I wanted to then switch to consumer Hermes from master, but ran into the issue of Hermes master failing to build for iOS. I’ve tracked the issue down to this Hermes commit which makes the hermesc binary a dependency, which we don’t build for iOS.
The proper fix would be to first build the macOS artefacts and then re-use its hermesc artefact during the iOS build, but that might make this PR drag on again.

Yeah, that would be the proper fix. At some point we'll need a hermes 0.8.0 with the fix for RN 0.65, but that could be months. For now, we should probably not fix it and consider using Hermes from master for RN 0.64 an option.

Here's the idea/question as this PR is getting older and older and starts to have a lot of changes inside it:

This branch builds when building static libraries. When building dynamic frameworks it fails.

Shall we merge it and release a release candidate with a note that use_hermes on iOS only works with static libraries (use_frameworks! not enabled) and that will be fixed in the next release candidate?
CC: @TheSavior

I'm not sure what the all implications of that would be, but in general it seems totally reasonable to land parts of this PR to make things easier on you instead of batching them altogether. I'll let you and @alloy decide what the right call is here.

@alloy thanks for the detailed summary! It seems like the real road blocking issue was just the JSI getting out of sync by d8b0e9d and we only need to do 2 and 3 of the "longest turnaround time" option to get this PR rolling again.

Agreed.

We are working on a patch that include facebook/hermes@73594b5 and its dependencies onto the Hermes release-v0.7 branch to hopefully have a v0.7.2 that is JSI compatible with RN master's. By this way we don't need to revert from either RN or Hermes master. I'll keep everyone posted once it's merged.

Perfect 🙏

After fixing that, I stumbled on the issue of RN master’s copy of JSI being out of sync with JSI that comes with hermes v0.7.1.

It would be helpful to know what are the steps to repro so we can verify if the patch resolve the issue. I can still build RN Tester app on Android on RN master with the hermes-engine-v0.7.1 npm package.

The failure is a build time failure. Try building this PR with dynamic frameworks enabled and then build:
cd packages/rn-tester
env USE_FRAMEWORKS=1 pod install

The proper fix would be to first build the macOS artefacts and then re-use its hermesc artefact during the iOS build, but that might make this PR drag on again.

Yeah, that would be the proper fix. At some point we'll need a hermes v0.8.0 with the fix for RN 0.65, but that could be months. For now, we should probably not consider using Hermes from master for RN 0.64 a very feasible option.

Gotcha 👍

Here's additional option […] Merge it and release a release candidate with a note that use_hermes on iOS only works with static libraries (which is the default setup, use_frameworks! not enabled) and that support for dynamic frameworks will be fixed in the next release candidate.

I’m in favour. I’d perhaps even go farther and not promise it to be fixed in a RC, just at a later time.

I’m in favour. I’d perhaps even go farther and not promise it to be fixed in a RC, just at a later time.

Interestingly, Flipper doesn't work with use_frameworks! either right now.
https://github.com/facebook/react-native/blob/master/template/ios/Podfile#L20-L23
Could that be related?

Opening #30300 restarted CircleCI. Yay!

All tests are passing except test_ios_unit_frameworks_hermes, which is expected. This is the variation that doesn't work right now, as per previous discussion.
This PR is ready to land. We may want to disable the failing job so that the CI remains green. Hope this can be done while landing to avoid re-running all tests. If not, I will submit another commit.

@facebook-github-bot import

Just out of curiosity - has anyone done any benchmarks on hermes for iOS?
E.g what is the impact on bundle size and startup performance.


allow for extra args on helm push?

for pushing to private nexus registries one has to specify the flag --context-path=/repo/chart with the helm cm-push command.
It would be awesome if we could specify additional parameters for helm cm-push via the options :)

Should be quite simple to implement at this point, similar to

https://github.com/nflaig/semantic-release-helm/pull/12

Feel free to open a PR if you need this quickly


Separate yargs with the core code

The intent is to make the code easier to test.

Closed with PR https://github.com/IBM/audit-ci/pull/15


Importing JSON data to selected Tab.

Hi Team,
I was trying to import json data to newly created tab (with 29 columns and 20 rows). Imported json has 14 columns and 4 rows data. Here, after importing data the tab is not rendering properly.
Thanks,
Kamesh.

Screenshots

Hi,
Do you import on load or after loading spreadsheet ?


Update vibration.json

Vibration API is a W3C Recommendation: http://www.w3.org/blog/news/archives/4370

Thanks!


Should include null provider

Added

Provider:

null

Only after merging #153 I realized that this should've been generated.


Check for both nil and zero length

Signed-off-by: Jhon Honce<EMAIL_ADDRESS>

@TomSweeneyRedHat FYI

@giuseppe and @rhatdan PTAL

LGTM

Do we actually ship this package anywhere?

To answer @rhatdan, yes we still ship this with Docker.

So we package this up as docker-runc?

From what @control-d showed me, yes, we basically package it up as docker-runc.  He or @jnovy could explain it far better than I, but there's packaging code that makes it happen.


[DevX] Move web-based app to celotools org and update docs

use-contractkit has been moved 🚀
Pull request for updating the documentation is here


bootstrap 4

will this framework work with bootstrap 4?

Hello,
Existing version of Propeller does not work with Bootstrap 4. But building bootstrap 4 compatible version is on our roadmap.

Any update on when a bootstrap 4 version would be available?

Hey Adam,
Bootstrap 4 based version will be launched in couple of months around April.
Regards,
Supriya
On 10-Feb-2018 12:56 PM, "Adam Youngers"<EMAIL_ADDRESS>wrote:
Any update on when a bootstrap 4 version would be available?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub
https://github.com/digicorp/propeller/issues/51#issuecomment-364632623,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AFiGdDwQPQapgV9TvUYYKAZInRqZZlnUks5tTUSsgaJpZM4PkXoJ
.

Hey Adam,
We have launched the Bootstrap 4 version of Propeller - Propeller Pro. You can find it out at https://pro.propeller.in/.
Regards,
Monika


chore(governance): fix errors when creating Gitpod environment

Issue number: #4530
Summary
Changes
This PR resolves the issue of Gitpod environment configuration by removing the poetry-bumpversion plugin from the initial setup. This plugin is not necessary in a development environment, as the only way we perform library versioning is through our CI/CD pipeline.
Additionally, I have taken the opportunity to update the environment to use Python 3.11.
User experience

Checklist
If your change doesn't seem to apply, please leave them unchecked.

[x] Meet tenets criteria
[x] I have performed a self-review of this change
[x] Changes have been tested
[x] Changes are documented
[x] PR title follows conventional commit semantics

Is this a breaking change?
RFC issue number:
Checklist:

[ ] Migration process documented
[ ] Implement warnings (if it can live side by side)

Acknowledgment
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.
Disclaimer: We value your time and bandwidth. As such, any pull requests created on non-triaged issues might not be successful.

should we perhaps use 3.12 (latest) instead of 3.11 given the opportunity?

Yeah, I tried that but for some reason the gitpod workspace for python3.12 is breaking some dependencies. I need to investigate more, but I think it's ok to use 3.11 for now. WDTY?


Starting client in QueueService constructor

Isn't that a bit early and uncontrollable? If server is unavailable, the whole app might be blocking, even before logging is set up, so app could just crash without any information. Which may be a wanted effect, but I'd prefer keeping this more under control by moving StartClient() to a later stage, e.g. before StartConsuming(), or maybe even a separate method, exposed through IQueueService?

We are experiencing this specific issue and getting a InitialConnectionException.
If the connection to RabbitMQ cannot be establish the entire Application fails because the Depedency cannot be injected.

We are experiencing this specific issue and getting a InitialConnectionException.
If the connection to RabbitMQ cannot be establish the entire Application fails because the Depedency cannot be injected.

I was able to solve this by injecting a Lazy loaded dependency
StartUp
var rabbitMqSection = configuration.GetSection("rabbitMq");
var exchangeOptions = new RabbitMqExchangeOptions
{
    Type = "fanout",
    Durable = true
};

services.AddRabbitMqProducingClientSingleton(rabbitMqSection)
    .AddProductionExchange("exchange", exchangeOptions);

// Allow to inject Lazy loaded instance for IProducingService
services.AddScoped(x => new Lazy<IProducingService>(() => x.GetRequiredService<IProducingService>()));

Implementation
public class EventPublisher
{
    private readonly Lazy<IProducingService> _producingService;

    public EventPublisher(Lazy<IProducingService> producingService)
    {
        _producingService = producingService;
    }

    public async Task PublishEvent()
    {
        await _producingService.Value.SendAsync(
            @object: new { Message = "something",
            exchangeName: "exchange",
            routingKey: "my.key");
    }
}

I was able to solve this by injecting a Lazy loaded dependency
StartUp
var rabbitMqSection = configuration.GetSection("rabbitMq");
var exchangeOptions = new RabbitMqExchangeOptions
{
    Type = "fanout",
    Durable = true
};

services.AddRabbitMqProducingClientSingleton(rabbitMqSection)
    .AddProductionExchange("exchange", exchangeOptions);

// Allow to inject Lazy loaded instance for IProducingService
services.AddScoped(x => new Lazy<IProducingService>(() => x.GetRequiredService<IProducingService>()));

Implementation
public class EventPublisher
{
    private readonly Lazy<IProducingService> _producingService;

    public EventPublisher(Lazy<IProducingService> producingService)
    {
        _producingService = producingService;
    }

    public async Task PublishEvent()
    {
        await _producingService.Value.SendAsync(
            @object: new { Message = "something",
            exchangeName: "exchange",
            routingKey: "my.key");
    }
}

@andrejt I am so late to answer that issue, but better later than never, right?
I'll start with a small story how this library even appeared. Some time ago I'd had to deal with rabbitMQ in one of my projects at work and I decided to create a small library that would help me with queue declarations and other stuff. I came up with simple idea to make a single QueueService that would be responsible for all the work: both consumption and production of messages. That was a huge mistake. Simplicity took over common programming principles as single responsibility.
Same thing for declarations in constructor - simplicity is the key.
Then I posted this library at GitHub and NuGet without a hope that it will be useful to someone, but after people began to use it I started trying to avoid making breaking changes. And yeah, it is a mistake as well, coz I have to do it anyway.
There is an issue where I share my thoughts about reworking current paradigm of QueueService, and here is a pull request where you can track upcoming changes.
I hope a new library version will come up in a week or so.
I think that it answers initial question, so I intend to close this issue. Feel free to re-open it if something is not clear and if the pull-request and connected issue do not satisfy your desires.

@fbridger I am happy you solved that problem by yourself!
Please take a look at this issue and the pull request too.
After an update that can change the way you use the library.
And if you have a suggestion (or a couple of them) feel free to leave them in the "Upcoming changes issue"


Fix Sonarqube scan failure "Set the SONAR_TOKEN env variable."

The Sonarqube job appears to be failing consistently in most PRs. I don't have access to check the secret settings but I do think this only occurs when a PR is raised from a forked repo.
Example:
https://github.com/rog-golang-buddies/golang-template-repository/runs/7134639006?check_suite_focus=true

An explanation and possible fix:
https://github.blog/2020-08-03-github-actions-improvements-for-fork-and-pull-request-workflows/#improvements-for-public-repository-forks

Alternative manual run on inspection by maintainers:
https://docs.github.com/en/actions/managing-workflow-runs/approving-workflow-runs-from-public-forks

@shukra-in-spirit can we also rename the file to something where we can infer the workflow? build is very generic and is not representative of a code scan.


[GHSA-8g4q-xg66-9fp4] Microsoft Security Advisory CVE-2024-43485 | .NET Denial of Service Vulnerability

Updates

CVSS v3
Description

Comments
The attribute name is JsonExtensionData(Attribute), not ExtensionData(Attribute). Stating the Attribute wrongly lead to false negative in a coworker assessment whether one of our projects could be affected by this issue, as she searched for the wrong attribute.
See: https://docs.microsoft.com/en-us/dotnet/api/System.Text.Json.Serialization.JsonExtensionDataAttribute?view=net-8.0

Hi there @rbhanda! A community member has suggested an improvement to your security advisory. If approved, this change will affect the global advisory listed at github.com/advisories. It will not affect the version listed in your project repository.
This change will be reviewed by our Security Curation Team. If you have thoughts or feedback, please share them in a comment here! If this PR has already been closed, you can start a new community contribution for this advisory


StringUtils.stripAccents(String) doesn't handle "\u0111" and "\u0110" (Vietnamese)

In Vietnamese, we have the characters "đ" and "Đ" (For reference, here is the Wikipedia page about this character: https://en.wikipedia.org/wiki/D_with_stroke.) When using your function, we need to manually replace these characters to remove their diacritical marks. It would be wonderful if you could add support for removing the diacritical marks from these two characters in your library. Thank you!

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

Project coverage is 92.51%. Comparing base (f962e7b) to head (1cfca36).
Report is 153 commits behind head on master.

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #1216      +/-   ##
============================================
+ Coverage     92.07%   92.51%   +0.43%
- Complexity     7587     7742     +155
============================================
  Files           200      200
  Lines         15844    15892      +48
  Branches       2890     2822      -68
============================================
+ Hits          14589    14702     +113
+ Misses          682      653      -29
+ Partials        573      537      -36

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

@hunghhdev
Thank you for your PR! Merged.


feat: add colors flag to infrastructureLogging

Fixes #12899
Since it's my first try of contribution to webpack, even if I looked carefully for impacted default values etc, there can exists some missed parts. Please review carefully for me to fix things. Thanks!

What kind of change does this PR introduce?

feature
Did you add tests for your changes?

Yes
Does this PR introduce a breaking change?

No
What needs to be documented once your changes are merged?

Maybe some page describing infrastructureLogging flags, but I cannot find that.

Omg I'm fixing lints

Thanks


Allowing user to manually input date

This allows the date to be set from the user manually inputing the date
into the input box. This had been discussed previously in an issue and was somewhat answered on a side note. The change is actually from another fork, but had never been actually a pull request. Recently we had used this feature and it worked wonderfully for the purpose we had in mind.
Here is the previous issue that was involved with this.
Issue #165

Any update?

2013 - 2021

related to #2629

I've just discovered this as well!


Axis3 is not working with heatmaps

The following works if one uses an `LScene, including a warning regarding [0.0] ticks size.
fig = Figure(resolution = (400, 400), fontsize = 10)
ax = LScene(fig, scenekw = (camera = cam3d!, show_axis = true))
heatmap!(ax,0:0.1:1, 0:0.1:1, rand(10,10), transformation=(:xz, 1), limits= Rect(Vec3f0(-1), Vec3f0(2)))
fig[1,1]= ax
fig

and if one tries to do the same with the new axis,
fig = Figure(resolution = (1000, 1000), fontsize = 10)
ax = Axis3(fig, aspect = :data)
heatmap!(ax, 0:0.1:1, 0:0.1:1, rand(10,10), transformation=(:xz, 1), limits= Rect(Vec3f0(-1), Vec3f0(2)))
fig[1,1]= ax
fig

I get the error:
InexactError: check_top_bit(UInt64, -9223372036854775481)

I ran into the same thing in https://github.com/JuliaPlots/AbstractPlotting.jl/pull/680. There the error was related to finding ticks with 0 width along the z-axis. I don't know if Axis3 uses the same function though. If that is the reason maybe the error goes away if you pass limits to Axis3?

in the example above I also pass limits to the Axis3 script.

You're passing it to heatmap, not Axis3. It doesn't seem like that matters though. I get
ax.limits
Observable{GeometryBasics.HyperRectangle{3, Float32}} with 22 listeners. Value:
GeometryBasics.HyperRectangle{3, Float32}(Float32[-0.05, -0.05, 0.0], Float32[1.1, 1.1, 0.0])

in either case. So the issue here is (1) limits don't get passed/get recalculated and (2) 0-width limits along some axis throws an error.

 That'll stop the error and you can adjust limits with ax.limits[] = Rect(Vec3f0(-1), Vec3f0(2)) afterwards.

ah yeah I probably just forgot to include the more robust limit mechanism from Axis where 0 width limits are expanded a bit

Indeed, the trick above works fine. A related question, how do we go back to the previous projection given in a LScene. There are some distortions that I don't like with the new Axis3.  :fit, :fitzoom, :stretch don't take me back.

The only thing that distorts is the :stretch viewmode, and perspectiveness just controls from how far away (with zoom to counter) you are

This should be fixed with https://github.com/JuliaPlots/AbstractPlotting.jl/pull/686
There is still some more work left to assimilate how limits work in 3d


Update balena-cli and balena-sdk

Change-type: minor
Signed-off-by: Kyle Harding<EMAIL_ADDRESS>Resolves: https://github.com/balena-os/leviathan/issues/576

lgtm

@balena-ci I self-certify!


ENH: Drop n_procs tag from BSplineApprox

BSplineApprox does not make use of multiple processors by default or accept them as an option.

Codecov Report
Base: 83.80% // Head: 87.71% // Increases project coverage by +3.90% :tada:

Coverage data is based on head (69c9310) compared to base (404fe3e).
Patch coverage: 100.00% of modified lines in pull request are covered.

Additional details and impacted files
@@            Coverage Diff             @@
##           master     #315      +/-   ##
==========================================
+ Coverage   83.80%   87.71%   +3.90%
==========================================
  Files          24       24
  Lines        1995     1995
  Branches      235      307      +72
==========================================
+ Hits         1672     1750      +78
+ Misses        281      205      -76
+ Partials       42       40       -2

Flag
Coverage Δ

travis
83.80% <100.00%> (ø)

unittests
87.61% <100.00%> (?)

Flags with carried forward coverage won't be shown. Click here to find out more.

Impacted Files
Coverage Δ

sdcflows/workflows/fit/fieldmap.py
98.43% <100.00%> (ø)

sdcflows/workflows/fit/syn.py
69.82% <100.00%> (+21.30%)
:arrow_up:

sdcflows/workflows/outputs.py
93.84% <0.00%> (+1.53%)
:arrow_up:

sdcflows/interfaces/reportlets.py
89.83% <0.00%> (+1.69%)
:arrow_up:

sdcflows/interfaces/bspline.py
80.00% <0.00%> (+3.33%)
:arrow_up:

sdcflows/interfaces/fmap.py
87.35% <0.00%> (+14.94%)
:arrow_up:

sdcflows/utils/phasemanip.py
94.02% <0.00%> (+28.35%)
:arrow_up:

Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here.

:umbrella: View full report at Codecov.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.

Going to merge, but please let me know if you object before a release, @oesteban. It may be that it can go multithread in cases I don't understand.


Add module-level merge function

Add merge function to the module-level functions like route function and mount function. This PR will be easy to merge the routes into the default application.

Merging usually only happens if an application grows big enough to justify splitting it up in multiple parts. In that case I'd rather have people move away from the module-level shortcuts and be more explicit about application context. This change would send the wrong message, I think. The module-level stuff is targeted at really really simple one-module applications.

@defnull   Thank you for the feedback.


Set default value for type parameter in SelectProps

Closes #6960
✅ Pull Request Checklist:

[x] Included link to corresponding React Spectrum GitHub Issue.
[ ] Added/updated unit tests and storybook for this change (for new code or code which already has tests).
[ ] Filled out test instructions.
[ ] Updated documentation (if it already exists for this component).
[ ] Looked at the Accessibility Practices for this feature - Aria Practices

📝 Test Instructions:

🧢 Your Project:

@snowystinger
I tried using overload syntax to deprecate only the function signatures where a type parameter is provided, but I couldn’t get it to work. Here’s my attempt: TypeScript Playground.
Could you check if my approach is correct, and let me know if there’s a better way to achieve this?
Thanks!

@snowystinger
Is there anything I should do?

Might need to run git rebase origin/main after updating your main branch, looks like the git history went wonky due to an accidental change we had on main


Installation scheme does not work

The installation scheme does not work even after making the repo public and omitting release tag!

(base) [tb571@rc-predict ~]$ pip install git+https://github.com/AMP-SCZ/dpanonymize.git

Collecting git+https://github.com/AMP-SCZ/dpanonymize.git
  Cloning https://github.com/AMP-SCZ/dpanonymize.git to /tmp/pip-req-build-2eblivfy
    ERROR: Command errored out with exit status 1:
     command: /home/tb571/min3-dpdash/bin/python -c 'import sys, setuptools, tokenize; sys.argv[0] = '"'"'/tmp/pip-req-build-2eblivfy/setup.py'"'"'; __file__='"'"'/tmp/pip-req-build-2eblivfy/setup.py'"'"';f=getattr(tokenize, '"'"'open'"'"', open)(__file__);code=f.read().replace('"'"'\r\n'"'"', '"'"'\n'"'"');f.close();exec(compile(code, __file__, '"'"'exec'"'"'))' egg_info --egg-base /tmp/pip-pip-egg-info-pxejd1xv
         cwd: /tmp/pip-req-build-2eblivfy/
    Complete output (4 lines):
    running egg_info
    /home/tb571/min3-dpdash/lib/python3.8/site-packages/setuptools/dist.py:452: UserWarning: Normalizing 'v0.1' to '0.1'
      warnings.warn(tmpl.format(**locals()))
    error: Invalid distribution name or version syntax: dpanonymize--0.1
    ----------------------------------------
ERROR: Command errored out with exit status 1: python setup.py egg_info Check the logs for full command output.

Thanks, now dpanonymize up in the pypi. Installation works now - Tested.
pip install git+https://github.com/PREDICT-DPACC/lochness.git@kcho/link_bpanonymize

scripts/anonymize_phoenix.py

Has it been renamed to dpanon.py? (No action necessary for you)

scripts/anonymize_phoenix.py

Has it been renamed to dpanon.py? (No action necessary for you)

Yes.  I wanted to give it a different name from the dpanonymize library folder name.

So I figured the dependency is the other way--for dpanon.py --help to work, lochness needs to be installed. But I think you made dpanonymize a dependency of lochness here.

Thanks for spotting this. pii removal of the survey uses atomic_write function from lochness. I'll make a hard copy of this function to dpanonymize to remove this dependency.

Will that hard copy make dpanonymize an independent package?

Without lochness, this is the error I got by the way:
(dpanonymize) [tb571@rc-predict-lochness dpanonymize]$ dpanon.py -h
Traceback (most recent call last):
  File "/home/tb571/miniconda3/envs/dpanonymize/bin/dpanon.py", line 7, in <module>
    from dpanonymize import dtype_module_dict
  File "/home/tb571/miniconda3/envs/dpanonymize/lib/python3.8/site-packages/dpanonymize/__init__.py", line 6, in <module>
    import dpanonymize.survey as SURVEY
  File "/home/tb571/miniconda3/envs/dpanonymize/lib/python3.8/site-packages/dpanonymize/survey/__init__.py", line 1, in <module>
    import lochness
ModuleNotFoundError: No module named 'lochness'

Will that hard copy make dpanonymize an independent package?

independent from lochness, yes.

Without lochness, this is the error I got by the way:
(dpanonymize) [tb571@rc-predict-lochness dpanonymize]$ dpanon.py -h
Traceback (most recent call last):
  File "/home/tb571/miniconda3/envs/dpanonymize/bin/dpanon.py", line 7, in <module>
    from dpanonymize import dtype_module_dict
  File "/home/tb571/miniconda3/envs/dpanonymize/lib/python3.8/site-packages/dpanonymize/__init__.py", line 6, in <module>
    import dpanonymize.survey as SURVEY
  File "/home/tb571/miniconda3/envs/dpanonymize/lib/python3.8/site-packages/dpanonymize/survey/__init__.py", line 1, in <module>
    import lochness
ModuleNotFoundError: No module named 'lochness'

Yes, this dependency is coming from this one.
https://github.com/AMP-SCZ/dpanonymize/issues/3#issuecomment-875050255

Problem with hard link/copy is that if you need to modify that module, you will have to modify it in two places ... :(

Will that hard copy make dpanonymize an independent package?

but lochness will depend on dpanonymize

Problem with hard link/copy is that if you need to modify that module, you will have to modify it in two places ... :(

We can keep it as it is for now, since for our projects, we will have both of them installed anyway. What's your thought on this?

We can keep it as it is for now

Yeah probably this is the better idea. This thread will serve as the documentation that if someone needs to install just dpanonymize, they should also install lochness.