Giuspen.Cherrytree 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?
[ ] 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.0 schema?

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

Microsoft Reviewers: Open in CodeFlow

/azp run

Duplicate of #17532
Fixed the Publisher name in that one 👍


Getting started lenet module loading operation raise an error

Bug Description
While activate the torch::jit::load operation on the TRTorch getting started lenet module which saved exactly according to the getting started instructions:
https://nvidia.github.io/TRTorch/tutorials/getting_started.html
The following error is reported:
ERROR: [TRTorch Conversion Context] - Parameter check failed at: ../builder/Layers.h::setStrideNd::321, condition: ((stride.nbDims == 2 || stride.nbDims == 3) && allDimsGt(stride, 0) && allDimsLtEq(stride, 100000))
It happens also for TRTorch Release and Debug
WithTRTorchDebugTraced.txt
WithTRTorchReleaseTraced.txt
To Reproduce
Steps to reproduce the behavior:
1.Perform all TRTorch getting started instructions described above
The code is exactly as provided in the Getting started guide
Expected behavior

Environment

Build information about the TRTorch compiler can be found by turning on debug messages

PyTorch Version (e.g., 1.0): 1.6
CPU Architecture: Jetson Xavier AGX
OS (e.g., Linux):JetPack 4.4
How you installed PyTorch (conda, pip, libtorch, source):pip3
Build command you used (if compiling from source):
Are you using local sources or building from archives: Local
Python version:3.6.9
CUDA version:10.2
GPU models and configuration: Jetson Xavier AGX
Any other relevant information: JetPack 4.4

Additional context

Thanks for catching this. Seems like PyTorch doesn't provide default stride explicitly. It shouldn't effect the operation of the compiler since TensorRT falls back to kernel size as the default but this patch adds it explicitly to suppress the error #233 .

Hello @narendasan,
Just want to say thanks.
When I made the update described in the error https://github.com/NVIDIA/TRTorch/pull/233 and rebuild again the TRTorch the Lenet module started to work properly for both Debug and Release.


feat: add datadog_trace 1.4.2 release

update datadog_trace with release 1.4.2

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


Size of the two video frames are different

Currently the two videos are inconsistent, generate project one is more recent, but build and run video is out-of-date.

@Matthew-Dong


Create Help, Help(.md for node file) added | Options button introduced

Hi @pradeeban
.md files need to be created for testing this. Moreover, the options button is added.
Any suggestions or questions are appreciated.
Thank You

Looks good to me. Merged. Thanks.
We can test more on Friday. Will comment later if I find something.


WARNINGS: React.createClass is deprecated, accessing PropTypes via the React main package is deprecated

I installed react-bootstrap-date-picker, and used it in a component, and I got some deprecated errors.
Expected Behavior

react-bootstrap-date-picker should work without warnings of deprecated parts.
Current Behavior

Getting these following error messages when using  component:
warning.js:36 Warning: Accessing PropTypes via the main React package is deprecated. Use the prop-types package from npm instead.
warning.js:36 Warning: DatePickerHeader: React.createClass is deprecated and will be removed in version 16. Use plain JavaScript classes instead. If you're not yet ready to migrate, create-react-class is available on npm as a drop-in replacement.
Possible Solution

The error messages give some steps to how to avoid getting them. Like using create-react-class and prop-types packages from npm.
Steps to Reproduce (for bugs)

Install  react-bootstrap-date-picker (npm install --save  react-bootstrap-date-picker).
Import DatePicker form 'react-bootstrap-date-picker'.
Use  component somewhere in your code.
See warning message in developer tools console.

Context

Your Environment

Version used: 5.0.1
Browser Name and version: Chrome: Version 58.0.3029.110 (64-bit)
Operating System and version (desktop or mobile): Ubuntu xenial 16.04.2 (virtual machine) on Windows 10 host machine

Same issue here.
It seems that the last version available on NPM, 5.0.1, doesn't have the latest changes that I can see on GitHub and still uses React.createClass.

when will this be available in npm?? is there anyway i can get the latest change?

src/index.jsx#L83 is using PropTypes from React.

@wehriam pls update npm to latest version

@wehriam pls update npm to latest version

Pushed 5.1.0 representing the current master. https://www.npmjs.com/package/react-bootstrap-date-picker

Thank you, but as mentioned by mervynrwtw, index.jsx is correctly importing PropTypes from 'prop-types', but still using React.PropTypes instead, which still triggers the warning. See here : https://github.com/pushtell/react-bootstrap-date-picker/blob/master/src/index.jsx#L82

@nathanvogel please consider resolving this issue and creating a pull request.

I considered doing so, but I'll need a bit of time since this would be my first time doing a pull request :) I'll try today or tomorrow.

It looks like #133 addresses the remaining issue with index.jsx, is there any way we can get that merged and released?

I'm keen to see the small fix in #133 go in as the warnings were fixed in #117, but unfortunately regressed in one area with #123

This issue, and #134 are now fixed in master - just need a new minor version pushed to npm. (package.json is ready at version 5.1.1 - current npm version is 5.1.0).
I'm not sure how releasing to npm is being handled at the moment - doesn't seem to be through CI.

Why this issue is closed?


Make README.rsts uploaded to PyPI render properly

Right now, in spite of GitHub's rendering of things nicely, PyPI displays our README.rsts as plain-text. While not 'plain old ugly', it's still 'plain old' looking.

Done in #7354.


Automate publishing grafana dashboard to grafana store

Description:
At the moment we do it manually.

We don't release this along with Ballerina releases anymore. Hence i am closing this issue


Design question...

Why would any software development manager ever allow their people to develop applications that are dependant on specific versions of an os when there is no guarantee that users of said software will be running that version? Am I the only one that sees this as problematic?

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

ID: 728fa4a8-ade5-b31a-c07f-de82f2402a5b
Version Independent ID: af5243e9-37a7-ed2f-a535-ce3ba3779b79
Content: Create and consume an app service - Windows UWP applications
Content Source: windows-apps-src/launch-resume/how-to-create-and-consume-an-app-service.md
Product: uwp
GitHub Login: @eliotcowley
Microsoft Alias: elcowle

Thanks for taking the time to let us know about this and we sincerely apologize for the delayed response. Due to the sheer volume of feedback in our repo, we are currently prioritizing new Issues. If you believe your feedback is still actionable, let us know either directly in this thread or by filing a new Issue and we’ll work to incorporate the suggestions into the documentation. Though the Issue will be marked as Closed, I will monitor any replies that come afterwards so feel free to treat this like an open Issue. Many thanks!


Refactor action invoke functions

This permits a called to set the handle the response as it wishes from invoking the action. This is toward removing the feed output when creating a trigger with a feed.
This is related to fixing https://github.com/apache/incubator-openwhisk-cli/issues/134.

this is semantic preserving - and permits some further refactoring down the line to fix the referenced bug, which is part of #315 but is turning out to be fairly substantial so I am breaking things up into smaller pieces.

@csantanapr @dubee @houshengbo @mdeuser @pritidesai may I get one of you to look at this?


Redis engine

Added a Redis engine as a storage mechanism. This does add a dependency on the redis gem which is questionable. I was unable to find a way to conditionally load it if a user wanted that engine. Perhaps the engines that depend on external gems should be external gems themselves.

I'd prefer to roll additional engines out as individual gems, similar to what fog does (see: https://rubygems.org/search?utf8=✓&query=fog-) trailing hyphen is intentional on the query.


Time-based gradual gossip

This reworks #4050 to use time-based gossip progression, rather than relying on the number of attempts, which is quite random.

This heavily conflicts with #4125

I'd like to get it in soon, but since a bug in the logic has the potential to halt finality, it's probably best to test a little first on @andresilva 's chaos setup, and roll out gradually. would nonetheless be nice to get it in soon after we bump polkadot-master for 0.6.18.

This heavily conflicts with #4125

Not that heavy.
Most changes are in  client/finality-grandpa/src/communication/gossip.rs, which is barely touched in #4125
Changes in client/network are mostly removing stuff introduced in #4050

For what it's worth I'm fine with that being merged. I don't know enough about how this part of the gossiping system works to review this, however.


[testing, bug] include sklearn fallback for normal non-invertible matrices in preview linearRegression

Description
Daal contains several methods for linear regression: https://github.com/oneapi-src/oneDAL/blob/master/cpp/daal/include/algorithms/linear_regression/linear_regression_training_types.h#L58 . oneDAL uses daal for CPU, but only has the norm_eq method available: https://github.com/oneapi-src/oneDAL/blob/master/cpp/oneapi/dal/algo/linear_regression/parameters/cpu/train_parameters.cpp#L42. Daal4py linear regression includes a fallback for non-invertible normal matrices: https://github.com/intel/scikit-learn-intelex/blob/master/daal4py/sklearn/linear_model/_linear.py#L61 using the other method before falling back to sklearn.
sklearnex.preview.linearRegression does not have either of these fallbacks, meaning it cannot handle norm_eq non-invertible matrices.
Ideally additional work should be done on the oneDAL side to include the QRdense method, and then expose it to sklearnex. This PR can be considered a stopgap bugfix as it falls directly back to sklearn.
This causes unit test failures for sklearn preview in public Nightly:
inspection/tests/test_partial_dependence.py::test_partial_dependence_easy_target[1-est0]
inspection/tests/test_partial_dependence.py::test_partial_dependence_easy_target[1-est1]
inspection/tests/test_partial_dependence.py::test_partial_dependence_easy_target[1-est2]
inspection/tests/test_partial_dependence.py::test_partial_dependence_easy_target[1-est3]
inspection/tests/test_partial_dependence.py::test_partial_dependence_easy_target[2-est0]
inspection/tests/test_partial_dependence.py::test_partial_dependence_easy_target[2-est1]
inspection/tests/test_partial_dependence.py::test_partial_dependence_easy_target[2-est2]
inspection/tests/test_partial_dependence.py::test_partial_dependence_easy_target[2-est3]
Changes proposed in this pull request:

Include a try catch for a Runtime error, fallback to sklearn due to non-invertibility.

/intelci: run

/azp run Nightly

/azp run Nightly

/intelci: run

/azp run Nightly

/intelci: run

/azp run Nightly

/intelci: run

/intelci: restart

manual rerun of private CI http://intel-ci.intel.com/ee644fea-91ee-f107-96d4-a4bf010d0e2e

Pre-commit failure is intermittent and unrelated to this PR, see manual rereun

/intelci: run

/azp run Nightly

The failed tests shown here are solved in #1507


Submitting Exercise 6

It took me about 5 hours just to figure out how to get the timestamp into ordinal haha. So the rest is pseudocode this time.

Thanks for taking on the pseudocode challenge, Jesse. It could be a little more detailed, but it gets your point across. The key step, I think, is finding unique ids within each hour.


Add test to describe the stop of application flow

You can use this feature to break the application flow prematurely
eg. Authentication listener change response statu code and stop
application flow

@samsonasik this is an idea :)

:+1:

Not bad


AugurWalletRegistry - Front running executeWalletTransaction

executeWalletTransaction is the entrypoint for interactions with the AugurWalletRegistry. If a AugurWallet is not associated with the user, it will create one before running the specified transaction.
The issue here is that the wallet being associated with the user might not have been created by the user. Consider the following order of transactions:
attacker makes their own AugurWallet via normal means
attacker approves this new AugurWallet, approving their personal EOA account access to all DAI held in this AugurWallet
attacker watches for pending "executeWalletTx", for users that do not yet have a wallet
When a transaction is seen, attacker front runs the tx to "gift" the pre-created, pre-dai-approved wallet to the user. AugurWallet transfer is done via the normal "transferOwnership" function
When the victim's transaction lands, AugurWalletRegistry sees they already have a wallet and uses it.
Victim's value is accrued to a wallet for which the attacker has approval

Similar to, but distinct from, #7454


[question] how many routes can fabio realistically handle?

I'm wondering whether to shift a large number of apache 301 redirects to the fabio instances at the edge of our network rather than them being proxied through and handled deeper within our architecture. There are about 3000 of them.
Realistically, does anyone know how Fabio performs with different numbers of routes?

It seems like a simple test case to setup and run.

We run a couple Fabio "clusters" with over 50k routes discovered from Consul Services (not K/V).
Each Fabio instance uses ~3.5GB RAM and ~3500MHz CPU, handling a couple thousand requests per second.

My fabio deployments with the largest number of routes have dozens to hundreds of routes and use ~10MB of RAM and <100 MHz.

Thanks for all your stats :) It's good to know what people are successfully doing with fabio :)


Installation fails with recent poetry due to fasttext issues

Hey!
As is explained in this issue: https://github.com/python-poetry/poetry/issues/6113 trying to install fasttext with a recent poetry version fails. This is because fasttext does some really funky things and tries to run a global pip during install. So this means that building luga or using any package that depends on it doesn't work. :/
This means that columbus doesn't build either, since it depends on luga. However, as is outlined in the issue there is a solution: using fasttext-wheel.
I pulled down luga and columbus and updated luga to use fasttext-wheel instead, and managed to get it to install, which also allowed me to build a new version of columbus using the new luga build.

fixed with #14


Unnecessary Escaping of '&' Character in sanitizeJSON Function

Thank you for great project!
I've encountered an issue with the sanitizeJSON function, where it unnecessarily escapes the & character. This behavior seems to be causing issues when parsing JSON strings.
export const sanitizeJSON = (unsanitized: string) => {
  return unsanitized
    .replace(/\\/g, "\\\\")
    .replace(/\n/g, "\\n")
    .replace(/\r/g, "\\r")
    .replace(/\t/g, "\\t")
    .replace(/\f/g, "\\f")
    .replace(/"/g, '\\"')
    .replace(/\&/g, "\\&"); // this line
};

If I've misunderstood something, I apologize 🙇

Thanks! You're right, as per json.org the ampersand shouldn't be escaped. I've published the new version on NPM based on this commit here:
https://github.com/kvnang/workers-og/commit/9866f9b2c1722252757cb464fa8f133c419b3a56


Cloudstack e2e tests

Issue #, if available:
Increase E2E test coverage for CloudStack
Description of changes:
This PR adds a bunch of E2E tests for features that were covered for other providers but were missing for Cloudstack. Vsphere tests were treated as baseline and all the Provider agnostic tests were included for coverage.
Testing (if applicable):
All the new tests that could be run locally were tested.
By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

/retest

/retest

/retest


[TW-114] timeout waiting for ACK

A programmable timeout in microseconds is given when a node is created. If a bidirectional connection does not hear an ACK before this time then it's killed with a Timeout exception. A test case is included.

I plan on doing some cleanup in here. The _nodeStateOutboundBidirectional type is unwieldly. I'll make it a record.


tests: Produce a coverage file with atomic mode

We're actually using the atomic counters when running our tests because
we run them with -race (2 lines later). We should set the mode of the
resulting coverage file to match this.
Signed-off-by: Damien Lespiau<EMAIL_ADDRESS>

Coverage remained the same at 72.705% when pulling 892578b7658568daf2cb07473d53151d414997c4 on dlespiau:20170530-atomic-coverage into 7a44618d5638f7ad325910b95e091d6b5d50b47e on clearcontainers:master.

lgtm

@amshinde just missing your review for this one.

lgtm


feat: Add the codespan-lsp crate

This contains functions to translate codepan's types into the ones used
n the language server protocol and is an almost straight translation of the pre-codespan implementation used in gluon's language server (which is why some parts may look a bit strange).

This also contains a generalization of FileMap which I failed to split up into a separate commit. While it currently is constrained to AsRef<str> I'd imagine this could be extended to let FileMap's contain ropes at a later stage.


prettyPrint is deprecated

Project throws an error after update to 9.0.0.
(node:8450) [PINODEP008] PinoWarning: prettyPrint is deprecated, look at https://github.com/pinojs/pino-pretty for alternatives.
/home/foxie/Dokumenty/Code/Artur/rutras-backend/node_modules/pino/lib/tools.js:221
    prettyFactory.asMetaWrapper = prettifierMetaWrapper

This is not an error but a warning. Follow the instructions at https://github.com/pinojs/pino-pretty to remove it.

Once you figure it out, would you like to send us a PR to update our docs?

This is not an error but a warning. Follow the instructions at https://github.com/pinojs/pino-pretty to remove it.

Well, actually localhost crashed. 😅
TypeError: Cannot set properties of undefined (setting 'asMetaWrapper')
    at getPrettyStream (node_modules/pino/lib/tools.js:221:33)
    at normalizeArgs (node_modules/pino/lib/tools.js:433:16)
    at pino (node_modules/pino/pino.js:83:28)
    at Object.register (node_modules/hapi-pino/index.js:55:14)
    at internals.Server.register (node_modules/@hapi/hapi/lib/server.js:495:35)
    at start (index.js:121:15)
[nodemon] app crashed - waiting for file changes before starting...

Once you figure it out, would you like to send us a PR to update our docs?
Sure, I just changed prettyPrint option to false. However, I'd like to have the pretty print available. How can I use/configure pino transport/stream globally?

This seems to work (taken from PR). Needs latest pino-pretty. This issue can be closed after the package is updated upstream and docs changed to reflect this usage.
	await server.register({
		plugin: HapiPino,
		options: {
			// Redact Authorization headers, see https://getpino.io/#/docs/redaction
			redact: ["req.headers.authorization"],
			transport: {
				target: "pino-pretty",
				options: {
					colorize: true,
					minimumLevel: "info",
					levelFirst: true,
					messageFormat: true,
					timestampKey: "time",
					translateTime: true,
					singleLine: false,
					mkdir: true,
					append: true,
				},
			},
		},
	});

Would you like to send a Pull Request to address this issue?


[BUG] Select blurs when it is used in other clickable element

Description
https://user-images.githubusercontent.com/50099653/181796105-856cd91e-29ae-40b5-8f84-e40ecf76cb86.mov
chakra-react-select Version
4.1.4
Link to Reproduction
No response
TypeScript?

[X] Yes I use TypeScript

Steps to reproduce

Go to '...'
Click on '...'
Scroll down to '...'
See error

Operating System

[X] macOS
[ ] Windows
[ ] Linux
[ ] iOS/iPadOS
[ ] Android

Additional Information
No response

Hmm, I'm not sure exactly what's causing this but using clickable elements inside other clickable elements tends to lead to complications.  If I had to guess it has something to do with the internal state of the select getting overridden during the render of the element above it.  Have you tried adding it inside another container which stops the click event from propagating to the element above it?
Something like this:
<Box onClick={(e) => e.stopPropagation()}>
  <Select />
</Box>

Either that or wrapping both the outside clickable element and the select as sibling children of the same relatively position container and using absolute positioning on the select itself.
If you could give me a minimal reproduction using one of the CodeSandbox templates I could probably give you more specific advice, otherwise there's not much I can do with just a video.

Overall, this is probably happening because the focusable element the Select is inside of is stealing the focus from the Select on click, and the dropdown only stays open while the Select is focused.  If you have any more updates on this feel free to leave a comment, but for now I'm closing this for inactivity.


feat(utility-types): add isNullable utility type

Overview
This is a minor suggestion! 🙏
How about managing types that have null as a union type with an isNullable utility type?
These types are meaningful and could be reused enough in the future.
However, this task may be subject to personal preferences. The opinion of the maintainer is important...!!💪
In the case of vitest, it also includes undefined as an isNullable type, but we don't seem to need it.
// vitest
type Nullable<T> = T | null | undefined;

PR Checklist

[x] I did below actions if need

I read the Contributing Guide
I added documents and tests.

Sorry for the late acknowledgement, your contribution is greatly appreciated!
Thanks for the awesome PR!!!

@manudeli @minsoo-web Thanks!! 🙏🎉


Wrong color for links

current color: #177ddc - should be #1da57a

That issue appears in multiple places, not only on the FAQ page:


inital call to acorn all or acorn volume errors out and returns non-zero

This is because the call get list volumes fails if the acorn namespace doesn't exist:
acorn-tmp $ ./acorn all

APPS:
NAME      IMAGE     HEALTHY   UPTODATE   CREATED   ENDPOINTS   MESSAGE

CONTAINERS:

VOLUMES:
Error: namespaces "acorn" not found, namespaces "acorn" not found
acorn-tmp $
acorn-tmp $
acorn-tmp $ echo $?
1

acorn-tmp $
acorn-tmp $ ./acorn volume
Error: namespaces "acorn" not found
acorn-tmp $ echo $?;
1

After getting acorn running, my first instinct was to just run acorn all as a sanity check. That shouldn't return an error

I tried to reproduce this but am not seeing this issue any more. Unsure if it got changed w/o closing the issue.
`jsilverio@joshuas-mbp ~ % kubectl get namespaces
NAME              STATUS   AGE
kube-system       Active   2d23h
default           Active   2d23h
kube-public       Active   2d23h
kube-node-lease   Active   2d23h
jsilverio@joshuas-mbp ~ % acorn all
APPS:
NAME      IMAGE     HEALTHY   UP-TO-DATE   CREATED   ENDPOINTS   MESSAGE
CONTAINERS:
NAME      APP       IMAGE     STATE     RESTARTCOUNT   CREATED   MESSAGE
VOLUMES:
NAME      APP-NAME   BOUND-VOLUME   CAPACITY   STATUS    ACCESS-MODES   CREATED
SECRETS:
ALIAS     NAME      TYPE      KEYS      CREATED
jsilverio@joshuas-mbp ~ %
`


Is this project dead?

@BryanJBryce Pretty much, yes. I don't think the approach is necessarily the best one. The problem doesn't seem to require a DSL, and I'm not personally using this library.

Sorry to drag up an old issue, but can you elaborate at all on what approach you prefer? I haven't spent a lot of time with Twilio, but this project felt exactly like what I needed.

I think you can achieve much the same results with simple HTTP controllers in a framework like Plug or Phoenix, rendering XML templates. Many developers would find it more intuitive to work with, and there'd be no DSLs to learn or maintain.


Add CMake variable for building with Address Sanitizer

Created a new variable "ASAN" in the top-level CMakeLists.txt. This variable is OFF by default. To enable building with Address Sanitizer, set the ASAN variable to ON by passing the argument to CMake "-DASAN=ON".
When ASAN is ON, the src/CMakeLists.txt file adds compile and link options for using Address Sanitizer to the directory properties and also to the target properties. These compile and link options will be applied to all tools in the src directory and to openroad itself.
Fixes #2738

I think something might be off with your history. It looks like something is a bit off with commit cbdc856d5062a3ecd98f7a03890459d8a7bcdc52. You might want to rebase and remove it.

My fork was 331 commits behind OpenROAD:master, so I tried pulling the more recent commits on to the master branch of my fork, and then I used merge and squash to move those changes to my feature branch.
Should I be pulling the latest commits from OpenROAD into my fork before opening a pull request? I can try using rebase instead.

@maliberty Generally dislikes rebases, but in this case I think it's warranted.
I say drop https://github.com/The-OpenROAD-Project/OpenROAD/commit/cbdc856d5062a3ecd98f7a03890459d8a7bcdc52
and then git fetch && git rebase origin/master or whatever you've called the upstream repo in your setup.

Does this look ok now?

Perfect!

LGTM!

@vvbandeira please setup a pipeline with this enabled to run with unit tests and a small design or two.  Nightly should be enough.

Strongly approved 😂

@rovinski Lol. My computer lagged, and I clicked the button way too many times.


Developing a Catchy and Bold Tagline for the Salon Website

Issue Description:
The purpose of this issue is to brainstorm and create a compelling tagline for the salon website that embodies the Hero archetype. The tagline should encapsulate the essence of the salon's brand identity, resonating with themes of empowerment, boldness, and trustworthiness. This tagline will play a crucial role in the salon's branding and marketing efforts, creating a memorable impression on potential clients.
Objectives:

Embodying the Hero Archetype:

The tagline should reflect qualities associated with the Hero archetype, such as courage, transformation, and empowerment.

Catchiness and Memorability:

It should be concise, easy to remember, and impactful, making a lasting impression on the audience.

Conveying Trustworthiness:

The tagline must build a sense of trust and reliability, assuring clients of the salon's commitment to quality and excellence.

Boldness and Appeal:

The tagline should be bold and engaging, capturing the essence of the salon’s mission and vision.

Brand Alignment:

It must align with the overall branding and messaging of the salon, complementing the name and visual identity.

Acceptance Criteria

Relevance to the Hero Archetype:

The tagline must clearly resonate with the themes of the Hero archetype.

Effectiveness in Branding:

It should effectively contribute to the salon’s brand identity and marketing strategy.

Clarity and Simplicity:

The tagline should be straightforward, avoiding ambiguity or complexity.

Cultural Sensitivity:

Ensure that the tagline is culturally appropriate and does not carry unintended negative connotations.

Feedback and Approval:

Gather feedback from team members.

Market Compatibility:

The tagline should be suitable for use across various marketing platforms, including social media, print, and digital advertising.

Legal Considerations:

Ensure that the tagline does not infringe on any existing trademarks or copyrights.

Came up with a bold and catchy tagline after a lot of branstorming with the team.


admin: update licensing

Since LG has re-licensed all his old code under Apache-2.0, we can change the license notice from BSD to Apache-2.0 for all files in which LG is the only extant author. Also change all files that LG co-authored with other people to specify "BSD-3-Clause and Apache-2.0".
Some files (mostly test scripts) had no license notice, so in those cases, we added one.

Amended: Also change all files that LG co-authored with other people to specify "BSD-3-Clause and Apache-2.0".

Does this look ok, @grdanny ?


Release on PyPI under a different name

As it is written in the documentation:
"Flit packages a single importable module or package at a time, using the import name as the name on PyPI. All subpackages and data files within a package are included automatically."
Could there be any way to specify a different release name for PyPI in the pyproject.toml than the module name?

Yup, it is possible - using the same name is now just the default behaviour. Here's how you do it with new-style [project] metadata:
https://flit.readthedocs.io/en/latest/pyproject_toml.html#module-section
It's a bit different in the older style metadata, but also possible.

Thanks, I misread that section and never tried it with the [project] name as the one to release on PyPI


python does not match the library

hi, this is a great job！
However, when I set up the environment, I found that python 3.6.12 version, can not download matplotlib==3.5.1

numpy==1.21.5 and scipy==1.7.3 also have this problem, what is the reason?
I then upgraded python to 3.7, downloaded the corresponding package, and encountered the following problem while running yelp datasets. Can you help me with this?

I solved it,thank you !


Contribute Parser to upstream

Hi Brian, just found this project and noticed you are using tree-sitting to re-write the parser. Since beancount v3 is now under development. Have you considered to contribute some code upstream, so this language server can be a thin wrapper around the upstream python/c++ functions?

have not had time to look at v3 of beancount. Are they using tree-sitter? I will definitely look at v3 to make improvements to this project


Fluentd config to Parse the log field correctly

With the default fluentd config,  the fields like logger, severity, tenant-id, trace-id and all other fields that are part of json log field are all crammed into one big json blob and hence not queriable.
To index these fields correctly so that all the keys which are part of log field which is a json are queriable, we need to modify the fluentd config like this and right now there isn't any mechanism through which we can pass this filter.
Can you guys please add an additional option through which this config is automatically injected at the time of Infra setup so that one additional manual step is avoided
step1:
kubectl -n logging edit configmap fluentdconf
    # Fixes json fields in Elasticsearch
    <filter kubernetes.**>
      @type parser
      format json
      key_name log
      reserve_time true
      reserve_data true
      remove_key_name_field true
      emit_invalid_record_to_error false
    </filter>
step2: change some param like requests or limits so that pods that are under daemonset gets restarted with updated configMap
kubectl -n logging edit ds/fluentd

It is possible to add a custom fluentdConfPath. This requires a full config be provided.
https://kurl.sh/docs/add-ons/fluentd

Hi @rajivml and @emosbaugh,
This one is open for a while. Have we here something that we would still needing to do to address this request? Is it something that still relevant or could we close this one?


@ashfurrow => Show Pages

Adds support for showing installation images on a show page, then you can scroll down into the artworks.

Looks great @orta! :cake:


Date Picker Off By 1 Day

When using this date picker anywhere between 12:00 AM to 12:59 AM (I suspect) the picked date is off by one day!
For example my code has mode selected to date:
<DateTimePickerModal
    isVisible={dp_visible}
    mode="date"
    onConfirm={handleConfirm}
    onCancel={hideDatePicker}
/>

And I am picking 21st of February 2023 and I would expect the results to come 21st of February but the picked date is shown for 20th of February like this:
A date has been picked:  2023-02-20
Original date  2023-02-20T17:52:01.000Z

My handleConfirm code:
const handleConfirm = (date) => {
    console.log("A date has been picked: ", date.toISOString().split('T')[0]);
    console.log("Original date ", date);
    hideDatePicker();
};

Note:
Date picker is usually working fine on my working hours (09:00 AM to 06:00PM)
Platforms
Both

👋 I'm sorry but I won't be able to help you unless you follow the issue template.

Use this

This may work
timeZoneOffsetInMinutes={0}


[Migration] Behaviour Change in getting OIDC claims retrival for client credential grant type

Describe the issue:
With https://github.com/wso2-extensions/identity-inbound-auth-oauth/pull/2132/files,
OIDC claims were skipped in JWT token issuer for client credential grant type.
This can be reversed with following config
[oauth.grant_type.client_credentials]
skip_oidc_claims = false

Note that this is not recommended way to request OIDC claims via CC grant type. This config should be suggested to anyone previously using this behaviour and want to use it after migration.

This issue is being closed due to extended inactivity. Please feel free to reopen it if further attention is needed. Thank you for helping us keep the issue list relevant and focused!


[CT-3042] Support meta attribute for SemanticModel nodes

It was recently noted by a user in a issue created on the MetricFlow project that the meta attribute isn't supported for SemanticModel nodes. As meta is a manifest node attribute (and not needed currently in MetricFlow or MetricFlowServer), I've moved the request here.
Acceptance Criteria

A meta field which is an arbitrary dictionary can be specified for SemanticModels and makes it to the corresponding SemanticModel node in the manifest
A test exists for ensuring this functionality

Is meta an attribute we require for all manifest nodes? If so perhaps we should consider creating a ManifestNode protocol that defines the fields which all nodes must support, and then use that protocol for some type checking.

It's worth noting that the original issue denoted a desire to have meta propagated to the semantic_manifest.json. This is not currently possible, this is because

dbt-semantic-interfaces de-serialization does not allow additional properties
dbt-semantic-interfaces protocols only contain attributes needed by both dbt-core and MetricFlow
the meta attribute is not needed in MetricFlow

Thus because of (3), meta is not part of the  DSI protocol spec (2).  Which in turn means we can't put it in the semantic_manifest.json because (1) means de-serialization would break. It is possible that long term we can change the de-serialization process in DSI to allow additional properties to exist in the serialization without causing de-serialization exceptions, but that is a separate conversation.

@QMalcolm There's a little bit of history here:

Originally, meta was a top-level attribute of (most/all) manifest nodes
We then allowed users to start defining it as a "config": in config: blocks in yaml files, and for all nodes in a subdirectory of the resource type in dbt_project.yml
For backwards compatibility, we continued to include meta both as a top-level node attribute and nested within the config dictionary, within the serialized node representation (in manifest.json)

I would expect users to define meta as a nested attribute within the config dict for semantic models. (We're adding support for this in https://github.com/dbt-labs/dbt-core/pull/8502.)
semantic_models:
  - name: my_sem_mod
    config:
      meta:
        whatever_key: whatever_value

If we can't then, during serialization, copy meta to be a top-level attribute of semantic_models, as we do with other node types — that would be a bit inconsistent for metadata consumers, but it's definitely not a show-stopper.

In conversation with @marcodamore @tlento @QMalcolm last week, we weren't sure whether:

meta can be a "bonus" attribute within dbt-core only, serialized out to manifest.json (current scope of this issue)
meta is needed for functionality within MetricFlow / needs to be included in semantic_manifest.json, in which case we would also need to add it to the DSI protocols

I'm not very familiar with how dbt-semantic-interfaces and dbt-core interact, so am not completely following. At the end of the day, the goal is to have meta available as an attribute in semantic interfaces. Rather than defining meta in the model/column YAML, I would define it in the semantic interfaces meta attribute on the entity/metric/dimension. Like many others, I am using meta for semantic layer purposes (synonyms, formatting, labels, etc.). With the new semantic layer and separate YAML definitions, these attributes should be in one place rather than defined partially in model YAML and partially in semantic YAML. Thus, the need for meta on semantic layer entity/metric/dimension. I do not want/need meta from dbt-core model YAML to be available in the semantic manifest.


Update astropy-helpers to v2.0.6

This is an automated update of the astropy-helpers submodule to v2.0.6. This includes both the update of the astropy-helpers sub-module, and the ah_bootstrap.py file, if needed.
A full list of changes can be found in the changelog.
This is intended to be helpful, but if you would prefer to manage these updates yourself, or if you notice any issues with this automated update, please let @bsipocz or @astrofrog know!
Along with with the astropy core release v3.0, we have also started to release astropy-helpers v3.0.x versions. Similarly to the core package, these require Python 3.5+. We will open automated update PRs with astropy-helpers v3.0.x only for packages that specifically opt in for it when they start supporting Python 3.5+ only. Please let @bsipocz or @astrofrog know or add your package to the list in https://github.com/astropy/astropy-procedures/blob/master/update-affiliated/helpers_3.py

Coverage remained the same at 74.82% when pulling 18d4a9421a50b24b842c56290ebe662f38ae6268 on bsipocz:update-helpers-v2.0.6 into 9818f02c126af5f7e94030ee93f73919807b8112 on radio-astro-tools:master.

Do we need to update the python2 numpy versions to 1.10?

Please try to restart those jobs instead, I suspect a recent update to ci-helpers fixed these, too.


Unsupervised: separate chunk for distances

material: slides which are commented out in pca and clustering slides

Is this outdated? Can it be closed?


Addition Of More Commands

Can i have the list of the commands you added?

Can i have the list of the commands you added?

ummm yes

Roleplay/blush
Roleplay/Hold_hands
Roleplay/sleep
Roleplay/smile
Roleplay/wave
Roleplay/wink

ummm yes

Roleplay/blush
Roleplay/Hold_hands
Roleplay/sleep
Roleplay/smile
Roleplay/wave
Roleplay/wink


[Feature]: Automatically set customerIpAddress

Tell us about your feature request
In Paddle Classic the customer IP would be read out automatically, but Billing requires to use an external service. See https://developer.paddle.com/build/checkout/build-pricing-page#pass-location
What problem are you looking to solve?
Why have additional calls if the IP is already available in the PricingPreview call? It would be much easier to not be required to have this additional step for integration.
Additional context
No response
How important is this suggestion to you?
Nice to have

Hi @holtwick,
Thank you for the feedback.
I agree with you. Expecting sellers to pass an IP address is not an ideal scenario.
We decided to skip IP address detection because the API could be called from a backend service and defaulting to the server's IP address will not be very helpful.
With that said, we are working on an opt-in solution that should allow us to detect the IP address if the sellers wants us to do so. Unfortunately, we do not have an ETA on the release date
I will close this issue as it is a duplicate of #34.
Please follow issue #34 to get notified when this issue is resolved.
Thank you.


Fine-grained control over notification behavior

Allow user to decide whether a specific notification type (stream vs @ message) makes a noise or a badge or both independently from each other.
Allow notifications only during specific time window of the day.

For having notifications only active during a specific part of the day, there's an OS-level "do not disturb" feature on both iOS and Android which you can use to disable notifications for all apps.

I don’t want to disable all apps though.  Some of these matter and need to
stay on.
On Wed, Mar 13, 2019 at 10:33 AM Tim Abbott<EMAIL_ADDRESS>wrote:

For having notifications only active during a specific part of the day,
there's an OS-level "do not disturb" feature on both iOS and Android which
you can use to disable notifications for all apps.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
https://github.com/zulip/zulip-mobile/issues/3401#issuecomment-472527593,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZQAtkOkGpAdibH5Rp6SxJfsNXudLfzEks5vWTaFgaJpZM4bt6LY
.

@0x4a50 do you need that for iOS or Android?
For Android, there is a thing called 'channels' that will allow more flexibility in changing notification's settings per stream or per message type.

IOS
On Wed, Mar 13, 2019 at 12:59 PM Boris Yankov<EMAIL_ADDRESS>wrote:

@0x4a50 https://github.com/0x4a50 do you need that for iOS or Android?
For Android, there is a thing called 'channels' that will allow more
flexibility in changing notification's settings per stream or per message
type.
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/zulip/zulip-mobile/issues/3401#issuecomment-472582178,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AZQAtuj01TC4PdtJvrGtzGJWsKWl5bFdks5vWVi0gaJpZM4bt6LY
.

(Thanks @0x4a50 for raising this!)
Some quick notes on implementing it:

The code that'd be involved in making this happen is largely in our platform-native code, for Android and iOS separately.
On Android, I think we'd want to align the fine-grained classification here with the "notification categories" exposed in system settings (called "channels" in the API) -- they exist to let the user specify exactly this kind of detailed choices, and as a user I much prefer using the standard interface over needing to find something idiosyncratic.

So e.g. we'd have a category for stream messages; one for PMs; one for @-mentions.
Currently we just lump everything into one category because we haven't dealt with this.

On iOS, I've spent less time to date looking into the API and I don't know if there's something equally helpful. But I certainly agree we should offer this feature even if we have to provide the settings more ad hoc.

Since this issue has the labels a-IOS and a-notifications, I'm marking it as blocked by https://github.com/zulip/zulip-mobile/issues/4115, so we only have to implement a solution once. The PR https://github.com/zulip/zulip-mobile/pull/4163 is currently open for that issue.

#4163 is merged!

We had another request for this feature today:

one single type of notification for Zulip messages seems too broad. I would like different notification settings for private messages and regular followed topic messages, for example.


Optimize the process of creating workflow tasks

Is your enhancement related to a problem? Please describe.

Describe the solution you'd like

Issue 1: After filling in the Deployment Environment fields, do not go to the next step automatically, because there are some fields that may still need to be configured.

Issue 2: When you create a task,  the form will be initialized if you go to the previous step and go back. Please don't clear the existing configuration.

Issue 3:  Let's set Retry Policy as Always by default and hide this option to simplify the selection.

Describe alternatives you've considered

Additional context

Environment

Walrus version: f94d57de903a925f2bd72d34b5aa1eaf8213f6ad
UI version: dev-c05317a

Test Steps:

New a workflow and add a workflow step.
In step 3, click Previous and then go back to step 3. The configuration in step 3 will be cleared.

Environment

Walrus version: v0.5.1

Test Result: pass


Export solid-permission's Authorization and PermissionSet classes

solid-client currently only exposes getPermissions() and clearPermissions() functions.
To create new ACL resources, a developer would need to use the PermissionSet class.
So, the top level client needs to expose/export the key classes from solid-permissions.

Currently also solid.acl ends up with undefined value, so this snipped will not work - https://github.com/solid/solid-client#editing-permissions

I recommend to make the whole solid-permissions module available via solid.acl and simply change solid-permissions so that it exports all the constants so one can do both

solid.acl.ALL
new solid.acl.PermissionSet

Fixed in latest release, v0.22.5. Closing.


Error when ng build --prod flag :  Uncaught TypeError: t is not a constructor

🐞 Bug report
Command (mark with an x)
- [ ] new
- [ X ] build
- [ ] serve
- [ ] test
- [ ] e2e
- [ ] generate
- [ ] add
- [ ] update
- [ ] lint
- [ ] xi18n
- [ ] run
- [ ] config
- [ ] help
- [ ] version
- [ ] doc

Is this a regression?
I cant tell, i can say was working in a previous deploy.
In this deploy i tested without updating using npm i and after with a npm i  , both same case so probably not.
Description
This project was working before with ng build --prod but seems to not be anymore.
Running without prod it works ng build.
When I run ng build --prod this complete the build successfully but when I try to run in the browser I receive an error:
    at main.js:1
    at Ti (main.js:1)
    at main.js:1
    at new e (main.js:1)
    at Object.nl [as createNgModuleRef] (main.js:1)
    at t.create (main.js:1)
    at main.js:1
    at t.invoke (polyfills.js:1)
    at Object.onInvoke (main.js:1)
    at t.invoke (polyfills.js:1)

🔬 Minimal Reproduction
These are the dependencies:
"dependencies": {
    "@angular/animations": "^7.0.0",
    "@angular/cdk": "^7.0.0",
    "@angular/cli": "^7.0.0",
    "@angular/common": "^7.0.0",
    "@angular/compiler": "^7.0.0",
    "@angular/compiler-cli": "^7.0.0",
    "@angular/core": "^7.0.0",
    "@angular/forms": "^7.0.0",
    "@angular/http": "^7.0.0",
    "@angular/material": "^7.0.0",
    "@angular/platform-browser": "^7.0.0",
    "@angular/platform-browser-dynamic": "^7.0.0",
    "@angular/router": "^7.0.0",
    "@ngx-translate/core": "^10.0.2",
    "ag-grid-angular": "^19.0.0",
    "ag-grid-community": "^19.0.0",
    "angular2-text-mask": "^9.0.0",
    "core-js": "^2.5.7",
    "hammerjs": "^2.0.8",
    "js-brasil": "^1.2.0",
    "ng-brazil": "^0.8.1",
    "ng-currency-format": "^0.1.6",
    "rxjs": "^6.3.3",
    "rxjs-compat": "^6.0.0-rc.0",
    "typescript": "3.1.3",
    "zone.js": "^0.8.26"
  },

🔥 Exception or Error

main.js:1 Uncaught TypeError: t is not a constructor
    at main.js:1
    at Ti (main.js:1)
    at main.js:1
    at new e (main.js:1)
    at Object.nl [as createNgModuleRef] (main.js:1)
    at t.create (main.js:1)
    at main.js:1
    at t.invoke (polyfills.js:1)
    at Object.onInvoke (main.js:1)
    at t.invoke (polyfills.js:1)

🌍 Your Environment

Angular CLI: 7.3.7
Node: 9.11.2
OS: linux x64
Angular: 7.2.11
... animations, common, compiler, compiler-cli, core, forms
... http, platform-browser, platform-browser-dynamic, router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.6.8
@angular-devkit/build-angular     0.6.8
@angular-devkit/build-optimizer   0.6.8
@angular-devkit/core              0.6.8
@angular-devkit/schematics        7.3.7
@angular/cdk                      7.3.6
@angular/cli                      7.3.7
@angular/language-service         6.0.9
@angular/material                 7.3.6
@ngtools/webpack                  6.0.8
@schematics/angular               7.3.7
@schematics/update                0.13.7
rxjs                              6.3.3
typescript                        3.1.3
webpack                           4.8.3

Anything else relevant?
This happens in different OS and browsers, so i dont think is a environment error

Seems to be related with #9929 because it works with --aot=false --build-optimizer=false ..
did update ng cli and worked!! thanks!

If someone ends up here, having this issue again even with newest ng-cli..
had to use without aot e optimizer to make it work again

I still have the same issue ... need to help !!


Accessing parameters inside custom predicates

Is there any ability to access parameters (that were passed to the schema) inside a custom predicate?
Dry::Validation.Form do
  configure do
    def my_predicate?
      params  # something like that
    end
  end

  required(:name).filled(:my_predicate?)
end

Or is there a way to pass them to the predicate?

Try the following documentation for the dry-validation library:
High-level Rules
Custom Validation Blocks
Dynamic Predicate Arguments

yep, it's on the docs


Chat - User searches "plant" , the first emoji is auto selected

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

Action Performed:

Go to https://staging.new.expensify.com/
Tap on a report
Tap emoji picker
Enter "plant" to search
Launch app
Repeat steps 2-4

Expected Result:
In mweb, when user search for " plant", the results alone must be displayed and first emoji must not be auto selected
Actual Result:
In android, when user searches " plant" , the results alone displayed and first emoji is not auto selected but in mweb, first emoji is auto selected
Workaround:
Unknown
Platforms:

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

[ ] Android / native
[x] Android / Chrome
[ ] iOS / native
[x] iOS / Safari
[x] MacOS / Chrome / Safari
[x] Windows / Chrome

Version Number: 1.3.63-0
Reproducible in staging?: Y
Reproducible in production?: Y
If this was caught during regression testing, add the test name, ID and link from TestRail:
Email or phone of affected tester (no customers):
Logs: https://stackoverflow.com/c/expensify/questions/4856
Notes/Photos/Videos: Any additional supporting documentation
https://github.com/Expensify/App/assets/78819774/f57fcb0b-8572-41c4-82a7-d761acdc2adc
Expensify/Expensify Issue URL:
Issue reported by: Applause - Internal team
Slack conversation:
View all open jobs on GitHub

This seems like a small polish and not necessarily consistent with other apps


My vs code appear blank after opening and gets stuck in a lag. I have tried various methods online and also deleted and downloaded it again for well over a year now but it just doesn't work. To make sure it works, I've also download all the extra packs on the official website for running it but it is just the same.

Does this issue occur when all extensions are disabled?: Yes/No (Yes)

VS Code Version:  Code 1.84.2
OS Version: 10.0.14393 N/A Build 14393

Steps to Reproduce:

I just downloaded it from the main site.
Opened it.
it got stuck in a blank like lag showing nothing.

My situation is something like this:

Can you try to reproduce with our nightly insider builds? You can give our preview releases a try from: https://code.visualstudio.com/insiders/

I searched a few way and stumbled upon deleted the 'Code' folder from the C:\Users\a(username)\AppData\Roaming and when I re-installed the app, it started working. Thanks for the suggestion anyway, @bpasero .


datafusion-cli should trap interrupt signal and abort execution

Is your feature request related to a problem or challenge? Please describe what you are trying to do.
datafusion-cli should trap interrupt signal and abort execution
Describe the solution you'd like
using rustyline signal handling and kill async operation instead of exiting
Describe alternatives you've considered
A clear and concise description of any alternative solutions or features you've considered.
Additional context
Add any other context or screenshots about the feature request here.

I tried to take an initial shot at this: https://github.com/Jefffrey/arrow-datafusion/commit/4761d169af2f08764af81f56aa1dab128a960167
But have run into a roadblock, where in the exec_and_print() function it can potentially block whilst printing, especially for a very large result set.
async fn exec_and_print(
    ctx: &mut SessionContext,
    print_options: &PrintOptions,
    sql: String,
) -> Result<()> {
    let now = Instant::now();
    let df = ctx.sql(&sql).await?;
    let results = df.collect().await?;
    print_options.print_batches(&results, now)?; // can block here!

    Ok(())
}

Since it is blocking, you can't abort the async function whilst it executes. Even spawning it in a separate task with spawn_blocking() doesn't look like it'll help, as though it would return control to let you enter more commands when you interrupt with CTRL-C, eventually that synchronous blocking print function will complete anyway and print onto the console (even though you interrupted it).
Perhaps could spawn it in a separate thread and kill it, rather than trying to relying on async cancellation?

That could be possible @qrilka, though I believe might require changes in arrow-rs as I think that's where the iterative print code is
Definitely something worth exploring

@Jefffrey my first thought was about having "cancellation points" after/before every batch i.e. in print_batches itself. But I guess that would be too coarse-grained and it looks like ideally we need AsyncWrite implemented for every printer...

Yeah that might be too coarse-grained and I think would vary depending on size of batches? So could still have cases where user hits CTRL-C and still has a batch print afterwards, messing with their prompt.
I'll see if I have time to look into this a bit more, though I haven't made any progress on this since my initial stab at it.

Closed by #8739


fix automatic entrypoint detector

This simply changes the template string to load correctly by replacing \ with \\ and adding file:// to the start
fixes #232

also holy thats alot of tests

Closing as it has been resolved in commit https://github.com/mandarineorg/mandarinets/commit/813d83b12b94467ff2c48be63479d5eaccd70181 using toFileUrl from STD.


[Feature Request] Show more details in logError

when I get an error in my SCSS file, I get an error message with little information.
In my opinion, this was more detailed in the past as well.
Maybe it is possible to add a more advanced option for the logError function.
This is my standard output:

I find this output more helpful:

this is my default gulpfile
const { sass } = require("@mr-hope/gulp-sass");
....

function css() {
  return src(paths.scss)
    .pipe(sass({style: 'compressed'}).on("error", sass.logError))
    .pipe(autoprefixer({
      cascade: false
    }))
    .pipe(dest(paths.destinationCss));
}
....

package.json:
...
    "@mr-hope/gulp-sass": "^3.0.2",
    "gulp": "^4.0.2",
...

Node 16 on Linux Mint 20.03

Sorry I totally fogot this, I will check this now

https://github.com/Mister-Hope/gulp-sass/commit/efa27908694df0f416845d4ab342a91a2417f33b


Fix logic for selecting recommended secure version

Only select version actually greater than the current
Reverse sort secure versions
Don't bump major version when picking secure Drupal core

I recommend looking at the commits one by one to understand the details.

See #14


Compile error when using the repo as reference

When referencing this repo (or a fork of it) directly in pubspec.yaml I get a compilation error:
Error (Xcode): ../../.pub-cache/git/flutter_scalable_ocr-7e74e46c3ecbacf791364f9be309e62a29c6b544/lib/flutter_scalable_ocr.dart:51:24: Error: Can't declare a member that conflicts with an inherited one.
Using version 2.0.0 from pub.dev does not produce this error.
Issue seemes to be introduced with this commit: https://github.com/vbalagovic/flutter_scalable_ocr/blame/7e74e46c3ecbacf791364f9be309e62a29c6b544/lib/flutter_scalable_ocr.dart#L51
Chaning to ScalableOCRState createState() => ScalableOCRState(); solves the issue


Works with new influxdb 0.9 line protocol

It seems the due to different indent config the change looks huge. Let me know your config, i'll send a pull request again. Till then please review the code.
Thanx.

Thanks for submitting a PR @kapilratnani. Not sure I follow you though. What's my config for formatting my code? That's probably best asked of @bernd who maintains the master I forked and then submitted my PR: https://github.com/bernd/statsd-influxdb-backend/pull/17. When I did that I made sure to keep the formatting in place and keep the diff as tight as can be.

Thanx Tima, I'll send a pull request again later today. Need to refactor a bit and will keep the formatting in  place.

I am actually just using the plain Javascript formatting that Vim does. ;)

Don't worry too much about the formatting. If this works for you both, I can just merge it to my master and fix the formatting.

Well, i am new to influxdb. Just figured out that this line protocol is quite new and it is not in the latest stable 0.9.0. It is supposed to come in >0.9.0. So, will just add another option in the config for version, refactor a bit and send a pull request again.


[request] ARM version

I was planning on self-hosting serpbear, but I am unable as there is no ARM version, only AMD64

Released the latest version in ARM64 version too. Give it a try.
From now on the app will be released for ARM64 too.


[spark] Use batch predict API

Description
Brief description of what this PR is about

If this change is a backward incompatible change, why must this change be made?
Interesting edge cases to note here

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

Project coverage is 72.42%. Comparing base (bd7f4ca) to head (b1f9f5b).

Additional details and impacted files
@@             Coverage Diff              @@
##             master    #3242      +/-   ##
============================================
+ Coverage     64.26%   72.42%   +8.15%
- Complexity     6455     7304     +849
============================================
  Files           676      676
  Lines         32443    32443
  Branches       3417     3417
============================================
+ Hits          20849    23496    +2647
+ Misses        10016     7335    -2681
- Partials       1578     1612      +34

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


http unsupported (self hosting)

Testing with self hosted instance and entered [IP ADDRESS]:8108 in the Extension configuration.
Firebase Functions logs show the port is updated to 443 and the connection is refused:

Ah yes, I didn't want to have one too many configuration options when setting up the extension. Would it be possible for you to use port 443?
Figured since API calls are made over public networks, it's a good idea to use https/443 when running your Typesense cluster.
You'd just need to get an SSL certificate and pass the location to the Typesense process when starting it up. See SSL params here: https://typesense.org/docs/0.19.0/guide/configure-typesense.html

Makes sense :) I can (and have now!) it was an unexpected speedbump switching from the docs to the extension but not too hard to get working. Thank you!


AttributeError: module 'wslPath' has no attribute 'is_windows_path'

Hi, I faced an error in execution.
I conducted a paired analysis of a control and a sample by following command:
DAJIN2 --control barcode01 --sample barcode02 --allele actc1L_cont_knockin.fa --name 02 --genome xenLae2
but this resulted:
2024-03-26 17:41:54, INFO, barcode01 is now processing...
2024-03-26 17:41:54, ERROR, Catch an Exception. Traceback:
Traceback (most recent call last):
  File "/home/user/miniconda3/envs/dajin2/bin/DAJIN2", line 10, in <module>
    sys.exit(execute())
  File "/home/user/miniconda3/envs/dajin2/lib/python3.10/site-packages/DAJIN2/main.py", line 236, in execute
    execute_single_mode(arguments)
  File "/home/user/miniconda3/envs/dajin2/lib/python3.10/site-packages/DAJIN2/main.py", line 47, in execute_single_mode
    core.execute_control(arguments)
  File "/home/user/miniconda3/envs/dajin2/lib/python3.10/site-packages/DAJIN2/core/core.py", line 26, in execute_control
    ARGS: FormattedInputs = preprocess.format_inputs(arguments)
  File "/home/user/miniconda3/envs/dajin2/lib/python3.10/site-packages/DAJIN2/core/preprocess/input_formatter.py", line 90, in format_inputs
    path_sample, path_control, path_allele = convert_input_paths_to_posix(path_sample, path_control, path_allele)
  File "/home/user/miniconda3/envs/dajin2/lib/python3.10/site-packages/DAJIN2/core/preprocess/input_formatter.py", line 33, in convert_input_paths_to_posix
    sample = io.convert_to_posix(sample)
  File "/home/user/miniconda3/envs/dajin2/lib/python3.10/site-packages/DAJIN2/utils/io.py", line 147, in convert_to_posix
    if wslPath.is_windows_path(path):
AttributeError: module 'wslPath' has no attribute 'is_windows_path'

I'm using Ubuntu20.04 and installed the latest version of DAJIN2 via conda in a new environment without any error.
Please let me know if anyone have idea to fix it.

@takeiga
Thank you for reaching out!
It seems that your environment might be running an older version of wslPath so we recommend updating to the latest version:
conda install -c conda-forge -n <your conda env> wslPath=0.4.1

Should you face any issues during the update, please don't hesitate to inform me.

@akikuno Thank you for your prompt reply!
I tried reconstruct environment by your command, but it showed following error and could not reconstruct environment:
  - nothing provides requested wslpath 0.4.1**
So I installed by pip and this fixed the issue:
pip install wslPath==0.4.1
However, I face the same error which I mentioned another thread #24.

@takeiga
Thank you for your effort. I truly appreciate it! I'm pleased to hear that the latest wslPath was installed using pip. If you don't have any further questions, please close the issue and proceed to #24.
The following is just an additional note.
I'm not sure why you couldn't find wslpath 0.4.1 via conda. It might be related to the version of conda. If you upgrade conda, I think the installation should work well.
conda update conda # or conda install -n base -c conda-forge conda=24.3.0
conda --version # check the version as 24.3.0
conda install -c conda-forge -n <your conda env> wslPath=0.4.1

@akikuno I really applicate your kind support. Yes, I didn't updated conda via conda-forge, so that causing the issue.


⚠ Bofrost.at has degraded performance

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

HTTP code: 200
Response time: 1536 ms

Resolved: Bofrost.at performance has improved in ba0bd70.


Update schedule.yaml.

Updated with correct 1.27.1 patch and cherry pick dates.
/hold

/cc @mickeyboxell

Updated dates, thanks @reylejano

Thank you for replying to the suggestion
/approve

/lgtm

/unhold


compressor VSVs

update compressor to allow for VSVs.  This can be done by adding a method for entering a 3-D compressor map.

CompressorVG (variable geometries) has been created.  This new component makes use of an alpha vector to interpolate between alternate compressor maps. For this change a 3d table interp function was created and many new warning were developed. Required sizing for variable in the mask are documented accordingly.
7/14/2016
7fc485ce2fc747c5ea985695bbde6e28059dd80a
49aac72eea04b69be9b57f25b32783203486a90e
It has been determined this feature is also useful for the turbine, so this issue will continue and be used for that change as well.

updated per
897c200826172906bc6f22197482aa47a77c9bd3
to allow code generation for the new compressor modules.

It was decided not to add this to the turbines.  Closed...


dx-docker pull speed

I'm seeing some somewhat erratic docker image pull times for workflows executed by dxWDLrt. Typical pull time seems to be about 3-4mins which seems par for the course (I can achieve 2.5-3 minute pulls of my image on a GCE or AWS instance running CoreOS). But every once in a while, a DNAnexus job will take 20 or sometimes even 40 mins just to pull the docker image (example: job-F8G5KyQ09y3bJYjqB23XJgBQ).
Do you have /var/lib/docker pointing to a local ephemeral disk mount, or is it on an EBS/root volume? (Or maybe dx-docker doesn't use a daemon, but it must be saving / unpacking the ACI somewhere)
In my own attempts to time pull behavior outside of DNAnexus, it seems that docker pull speed has almost nothing to do with available network bandwidth, but is either bound by disk I/O speed (which might be at play here) or the inherent lameness of gzip (the latter of which is more predictable and doesn't explain this behavior).

We use the local ephemeral disk, not EBS. It sounds like a dx-docker vs. native docker issue,
@geetduggal, can you take a look at this please?

@geetduggal

I have seen this too with the >1GB viral-ngs image and my gut feeling is that it's a suboptimality of the docker2aci utility which dx-docker uses to pull the image layers. I doubt it's an issue with dxWDL specifically.
Speculation: while docker2aci fetches different image layers in parallel, each individual layer is downloaded on one sequential TCP connection. The viral-ngs image does have one layer which makes up a large majority of the total size. When docker2aci makes the TCP connection to S3 or whatever to retrieve it, it occasionally gets unlucky and hits a lousy remote host that can't push data at the expected speed (maybe it's overloaded or whatever).
dx download and other cloud transfer utilities smooth this over with multipart transfers, i.e. it uses many TCP connections to download small parts of the remote file in parallel, with individual part retries, so that a small % of lousy ones is well-tolerated. Maybe docker pull does that too.

If you think it is the network itself that is being unpredictable and slow, we can try a few things:

I can try an alternate registry just for kicks. Probably quay.io (which I think exposes raw S3 URLs in us-east)
If you're sure docker2aci pull operations are inherently not fast, and if this is a general issue beyond my project, then you could consider creating a fetch_aci dx applet that dxWDL invokes prior to every other applet in its workflows: takes a docker tag string in and emits a ACI file. It would be kind of annoying the first time you ran the workflow in a given project, but each subsequent time, DNAnexus will likely cache those jobs and use the ACI files already living in the project. This is if you believe that multi-part downloads are making all the difference here (and that dx download of an ACI would beat docker2aci consistently). I mean, dx download ought to be able to pull down a 1.5GB ACI in 12 seconds.

That being said, in my own playing around, rkt prepare viral-ngs.aci takes about 3 mins, so the bulk of the time here isn't the network-limited download speed--it's whatever else it's doing to unpack it. But I'm willing to settle for a 3-5 minute spin up time as long as it's consistently 3-5 minutes. Don't know how rkt compares to what dx-docker is doing though.

@dpark01 this is the key excerpt of dx watch job-F8G5KyQ09y3bJYjqB23XJgBQ consistent with my admitted speculation:
2017-11-24 10:09:10 scaffold STDERR sha256:f4e5dc28016: 947 MB/1.53 GB
2017-11-24 10:09:11 scaffold STDERR sha256:f4e5dc28016: 961 MB/1.53 GB
2017-11-24 10:09:11 scaffold STDERR sha256:f4e5dc28016: 975 MB/1.53 GB
2017-11-24 10:09:12 scaffold STDERR sha256:f4e5dc28016: 989 MB/1.53 GB
2017-11-24 10:09:12 scaffold STDERR sha256:f4e5dc28016: 1.01 GB/1.53 GB
2017-11-24 10:09:15 scaffold STDERR sha256:f4e5dc28016: 1.22 GB/1.53 GB
2017-11-24 10:18:26 scaffold INFO CPU: 0% (8 cores) * Memory: 850/15038MB * Storage: 152GB free * Net: 3↓/0↑MBps
2017-11-24 10:28:26 scaffold INFO CPU: 0% (8 cores) * Memory: 849/15038MB * Storage: 152GB free * Net: 0↓/0↑MBps
2017-11-24 10:38:26 scaffold INFO CPU: 0% (8 cores) * Memory: 850/15038MB * Storage: 152GB free * Net: 0↓/0↑MBps
2017-11-24 10:44:24 scaffold STDERR sha256:f4e5dc28016: 1.31 GB/1.53 GB
2017-11-24 10:44:29 scaffold STDERR sha256:f4e5dc28016: 1.47 GB/1.53 GB
2017-11-24 10:47:52 scaffold STDERR Image Repo	broadinstitute/viral-ngs-dev
2017-11-24 10:47:52 scaffold STDERR Image Tag	1.18.2-110-g4a530c5-dp-dx-pull_request
2017-11-24 10:47:52 scaffold STDERR Image Size	5.3G
2017-11-24 10:47:52 scaffold STDERR Image ID	sha256:3f1a535db9d99f467b2d888b0bdf75ae645f7c937a8f17ffddee09d50497791f

docker2aci is printing progress messages as it's downloading the big 1.53GB layer, which goes at a healthy clip up until 1.22GB. Then, not much seems to happen for like half an hour, and then then the last 200MB come in quickly. I think this is a sporadic delay occurring in the transfer, before any of the decompression/unpacking occurs. I'll need to discuss possible workarounds for this with @geetduggal when he gets back from re:Invent

Interesting.  Yes, let's dig more into it.  One nice thing about the dx-docker add-to-applet/create-asset subcommands is that they cache the image on the platform and avoid all these network issues -- particularly handy when we venture into non-US regions.  However, this involves an additional step to update the cache every time the public repo is updated -- something I can understand you may want to avoid if at all possible :)

@dpark01 BTW I do think it would be worthwhile to try quay at least as a one-off workaround until Geet and I can get our heads together on this

Yep, giving that a shot now!

@geetduggal, this is a pure dx-docker issue, I am closing it here.

(also, quay.io does seem to obviate this issue)


Can I add a feature to display some more elements  for user-specific brand image or text

In some videos, we may wanna display a personal brand with an image or text, can I make a pr to implement it ? OFC, it will be optional, rather than required

No thank you


[PL-46804] SMP patch 0.13.2 release notes

SMP patch 0.13.2 release notes
For reviewers, a preview is available:
--preview building--
What Type of PR is This?

[ ] Issue
[ ] Feature
[ ] Maintenance/Chore

If tied to an Issue, list the Issue(s) here:

Issue(s)

House Keeping
Some items to keep track of. Screen shots of changes are optional but would help the maintainers review quicker.

[ ] Tested Locally
[ ] Optional Screen Shoot.

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65bcf3ff5638ab8f1b22d0a1--harness-developer.netlify.app

Please check the Execution Link of the Pipeline for the Website Draft URL. This is located in the Preview Step behind the Harness VPN and also is available in #hdh_alerts. E.g Website Draft URL: https://unique-id--harness-developer.netlify.app. Current Draft URL is: https://65bd3308157bbe24c921954c--harness-developer.netlify.app


build error :COPY failed: file not found in build context or excluded by .dockerignore: stat .next/standalone: file does not exist

Environment
Docker
Version
0.13.3
Describe the problem
limbo@Limbo-NAS:/volume1/container/common/build/homarr-0.13.2$ sudo docker build -t limbo/homarr:0.32 .
Sending build context to Docker daemon  6.259MB
Step 1/13 : FROM node:20-alpine
 ---> ade38d68438a
Step 2/13 : WORKDIR /app
 ---> Using cache
 ---> cca197014578
Step 3/13 : ENV NEXT_TELEMETRY_DISABLED 1
 ---> Using cache
 ---> cad7ddc4a1f4
Step 4/13 : ENV NODE_ENV production
 ---> Using cache
 ---> 6f8f8bfa470e
Step 5/13 : ENV NODE_OPTIONS '--no-experimental-fetch'
 ---> Using cache
 ---> 423e5b149956
Step 6/13 : COPY next.config.js ./
 ---> d157436c64e7
Step 7/13 : COPY public ./public
 ---> 6e36b293e322
Step 8/13 : COPY package.json ./package.json
 ---> 083dfcacb693
Step 9/13 : COPY .next/standalone ./
COPY failed: file not found in build context or excluded by .dockerignore: stat .next/standalone: file does not exist

Logs
COPY failed: file not found in build context or excluded by .dockerignore: stat .next/standalone: file does not exist
Context
COPY failed: file not found in build context or excluded by .dockerignore: stat .next/standalone: file does not exist
Please tick the boxes

[X] I confirm that I attached the proper logs
[X] I've read the docs
[X] I've checked for duplicate issues
[X] I've tried to debug myself

Why are you trying to docker build yourself ?
anyways you need to do yarn build before. This is not a bug.

@nick-ling I'll close as completed now.


Support generating or redirecting rays for picking

What need does this fill?

Being able to pick an entity through a portal (that's my use case for bevy_basic_portals)
Idk maybe leveraging the picking system in a testing environment or as a intradiegetic game mechanic that doesn't involve the cameras/screen position directly? Like an ennemy that would be able to pick stuff like the player, but would do so with the picking logic?

More details about why this is complicated to do currently (tl;dr: RayMap cannot be mutated outside of Bevy's logic and the backends can't be called several times in a practical way so you can't rely on their result to call them again with new rays):
https://discord.com/channels/691052431525675048/1314258126832271381/1314258126832271381
Related issue: https://github.com/bevyengine/bevy/issues/16046
What solution would you like?
I see several options:

Make "ray-based" backends have a hook to allow to subscribe handles to generate new rays (RayId + Ray3d) in certain conditions on hit, those new rays are then reprocessed to send new PointerHits and generate other rays, etc until there's no ray left, this requires like Avian and Rapier to use this hook, and a logic to avoid infinite loops (I think this could be one of the more elegant solutions?). This solution allows to pass in the incoming ray to calculate the generated one, otherwise this information is lost or needs to be recreated with PointerHits/HitData.

Have a component in Bevy on some entities (like a portal) to allow to redirect picking rays with a closure or something, similar as the hook solution but the hook would be on the entities instead of subscribed in a list.

Make RayMap mutable (no private fields or setters) and being able to not be cleared at the beginning of the frame, that would allow to generate rays that are picked up next frame. This is not an elegant solution at all as there would be a delay in how the inputs are handled, and could generate a delayed infinite loop.

Make "ray-based" backends register their system in a subset of PickSet::Backend, like PickSet::RayBasedBackend, and make RayMap mutable, so that those systems could be recalled once after with a different RayMap, without having to recall them one by one. This doesn't allow recursion.

Rewrite update_hits so that it's a system calling a function using a RayMap not necessarily the ressource one, so that this function can then be called to handle the hit detection and do other stuff with it, and convinced Rapier and Avian to do the same (still backend-dependent)

What alternative(s) have you considered?
For my case, copying update_hits into bevy_basic_portals but modify its logic so that it operates on the RayMap ressource but also on potential portal-deviated rays.
This solution is not very satisfying as it not only duplicates code but also relies on Bevy's Mesh picking algorithm and doesn't leverage potential colliders / other backends.

It seems to me like you should write a custom back-end for this? We expect users to define new back-ends if they are doing custom stuff, and the ray-cast logic is fairly separate so it shouldn't be too hard to write a version of it that supports secondary rays. I'm iffy about adding a bunch of complexity to the stock one.

Well see the discord thread: I'm trying to, but it's hard because what I want is to use one backend (and not caring about which one), then generate rays based on its result, then reuse that backend with the new rays.
I could write a backend "from scratch" (modify Bevy's) like I said but it wouldn't leverage rapier or Avian if they're present for example.
I could use RayMap before any backend runs, detect which portals are on their path manually, then fill RayMap with new rays before the other backends run, but that would only work with rectangular portals, not be recursive, and I actually can't even add my own stuff to RayMap

Expending on the reasons I think this is necessary: https://discord.com/channels/691052431525675048/1317595264592384053/1323078573191594006


[Mac/Firefox] Texts on Buttons are not centred vertically

Description

We have included Spectrum Button component in our page, we observe that button text is not centered correctly in FireFox browser.
Steps to reproduce

Go to http://opensource.adobe.com/spectrum-css/
Click on ...
Observe ...

Expected behavior

Button text should align vertically across the browser.
Screenshots

This screenshot from our request page shows difference in their alignment:

Same when open the storybook https://react-spectrum.corp.adobe.com/storybook/?path=/story/button--variant-cta  in chrome and Firebox, I could see very little difference their alignment:

Environment

Spectrum CSS version:
Browser(s) and OS(s):  Firefox

Additional context

More information is available on react-spectrum issue:
https://git.corp.adobe.com/React/react-spectrum-v2/issues/618

@mopandit you're comparing Firefox to Chrome on MacOS?

@mopandit you're comparing Firefox to Chrome on MacOS?

@GarthDB  Yes. Both comparision is done btween chrome and fireFox on MacOS.


COPS-6139 don't make up job-groups

https://jira.d2iq.com/browse/COPS-6139
before we render jobs, we expect our graphql-server to only give us jobs that
are considered to be within the group we're currently looking at. we're grouping
by spliting job-ids by "." - everything except for the last segment is a group,
while the last segment is the jobs "name" (in the context of this code).
unfortunately our graphql-server (yes, we have a graphql-server bundled with our
application. i don't think it's making code more maintainable btw) filtered jobs
like so:
imagine there're the jobs foo.bar.baz.blorgh and foo.barbar.blorgh and we're
currently looking at the foo.bar group. we're now filtering out all jobs that
don't start with that path (["foo", "bar"]). we did that with a
startsWith, so foo.barbar.blorgh was be considered to be in that group. now
the rendering takes over and displays all the "third-level" groups and jobs. in
this case we'd see baz (being the third-level of foo.bar.baz.blorgh) AND
blorgh (being the third-level of foo.barbar.blorgh), while we actually don't
want that group to show up.
in code:
foo.bar
foo.bar.baz.blorgh <- starts with foo.bar
foo.barbar.blorgh  <- starts with foo.bar (the error)

this fix seeks to compare differently:
foo.bar.           <- notice the dot at the end
foo.bar.baz.blorgh <- starts with foo.bar.
foo.barbar.blorgh  <- does not start with foo.bar. :woohoo:

please let's follow up with removing that graphQL-server and -client at some point in time. they are mainly used in the context of jobs and are highly confusing as they add a lot of accidental complexity (that's very hard to debug).

@janisz sure. added one and made sure that it fails without the fix.
thanks!

:tada: This PR is included in version 5.0.57 :tada:
The release is available on:

v5.0.57
GitHub release

Your semantic-release bot :package::rocket:


Smart charging  add a new field amps per phase in edit charging station

I left the validation of the totalAmps, but I can also take it out if you want.

Good Job!


PHP authentification not working (Code 200 error on edge server)?

How can I create a basic authentification for the one that streams so that not everyone can stream with a simple URL?

I also tried with a JSON encode reply :
echo json_encode(http_response_code(200));
Still the same even if i return nothing...

For the future me I didn't founded a way to close the connection correctly but here is the basic code to reply yes to the server :
<?php
echo "0";
$code = 200;
    // clear the old headers
    header_remove();
    // set the actual code
    http_response_code($code);
    // set the header to make sure cache is forced
    header("Cache-Control: no-transform,public,max-age=300,s-maxage=900");
    // treat this as json
    header('Content-Type: application/json');
    $status = array(
        200 => '200 OK',
        400 => '400 Bad Request',
        422 => 'Unprocessable Entity',
        500 => '500 Internal Server Error'
        );
    // ok, validation error, or failure
    header('Status: '.$status[$code]);
    // return the encoded json
    return json_encode(array(
        'status' => $code < 300, // success or not?
        'message' => $message
        ));
?>


Packet parsing problem

Like he will put the Integer.MIN_VALUE to 0 (like ConfirmTransaction) one

Is this on Bedrock Edition?

nah Minecraft 1.8.9

Is this the packet with the problem? https://wiki.vg/index.php?title=Protocol&oldid=7368#Confirm_Transaction
So you mean a value that should be -2147483648 is changed to 0?

yes (windows id one)


feat(api + web): resorts

[x] Add resorts to API
[x] Add resorts to web

Resorts are pretty much implemented in the API, they just need to be finalized on web


Gigapixel Image Approximation Experiment in instant-ngp

Recently I tried to put this code into a video coding task ((x,y,t)->(r, g,b)), which is similar to SDF task, but the effect is not ideal, so I tried the  Gigapixel Image Approximation experiment  in the paper, and found that it cannot be reproduced under the same experimental setting. Has anyone ever encountered the same problem yet？

For Gigapixel Image exp, I would recommend using tiny-cuda-nn's example: https://github.com/NVlabs/tiny-cuda-nn/blob/master/samples/mlp_learning_an_image_pytorch.py

For Gigapixel Image exp, I would recommend using tiny-cuda-nn's example: https://github.com/NVlabs/tiny-cuda-nn/blob/master/samples/mlp_learning_an_image_pytorch.py

Ok, thanks a lot.


Entries for standard atmosphere calculations - stdatmus_z2tdp

We had a request for this over on https://github.com/NCAR/geocat-comp/issues/631.

Link in NCL for the NCAR's Data Support Section is dead
NOAA has a link to the U.S Standard Atmosphere, 1976 booklet which seems helpful

Here's the relevant Fortran code from NCL: https://github.com/NCAR/ncl/blob/develop/ni/src/lib/nfpfort/stndAtmUS76_dp.f
I think this is what came from NCAR's DSS (what's now RDA/DECS I believe).

Look to recreate with the Python package ambiance


Document tintColor option for ActionSheetIOS

also:

fixed the showActionSheetWithOptions example

This option was added in https://github.com/facebook/react-native/pull/4590
FYI, this is not even documented in the comments
https://github.com/facebook/react-native/blob/master/Libraries/ActionSheetIOS/ActionSheetIOS.js#L28
Are the docs generated from the code? Should I update that instead?

The docs were initially generated from code, but going forward they will not be synced. Feel free to add any necessary comments back into the JS file.
The idea here is to have the full API reference documented on the website, while only having minimal comments for each method in the source code. It will take a while to update every source file to match this style but you can see an example of what we're going for here:
https://github.com/facebook/react-native/blob/master/Libraries/AppState/AppState.js

Can you make this change to the file in docs/ as well? Normally we would only update the docs/ version whenever an api is added/changed, but fixes like these are worth adding both to docs/ as well as versioned_docs/.

Thanks for fixing the conflicts. I didn't have time and now I know how I should have done it as well :)
👍 to RN


Improve and extend urlize

Fixes #522
Fixes #827
Fixes #1172
The 'urlize' function does not as expected both in terms of some missing support. Among a few a few of the behaviors were a lack of support for 5/8 of the original TLDs, emails prefixed with mailto: would not be returned as links, and no support for ftp://.
This PR does not "fix" the latter point, but does add a policy that can be set so that the function will create the links.  This can also be used to add support for any arbitrary URI scheme.
Specifically:

Adds mailto: link support (issue #1172)
Adds an extra_uri_schemes policy and parameter to address lack of ftp: support and allow for other schemes (for example tel:) to be added as needed. (issue #522 and PR #587)
Parentheses at the end of a URL are now included if they match an opening parenthesis in the URL (issue #827)
Adds support for all of the original top-level domains when creating links such as example.org
Uses the same regex used to validate URLs to ensure that ipv4 and ipv6 https// and https:// links are well-formed.
Sets the default URI scheme for URLs to be https instead of http

updated docstrings
moved regexes from the top of the module to above the function
turned the http regex into a verbose one with comments since it's complex
renamed extra_uri_schemes to extra_schemes

updated docstrings
moved regexes from the top of the module to above the function
turned the http regex into a verbose one with comments since it's complex
renamed extra_uri_schemes to extra_schemes

After looking over the code more, I identified a number of optimizations, so I committed another refactor.

After looking over the code more, I identified a number of optimizations, so I committed another refactor.


Implement Configurable File Validation

Because there are so many ICL specifications, not to mention vendors who deviate from those specs, this project needs to be more flexible in the way it validates files. One potential approach would be to implement a ValidateOpts struct containing flags to tailor the validation behavior.
For examples of how this pattern has been implemented in our other OSS repos, see:

ACH: https://github.com/moov-io/ach/blob/719968e674cced90ace172b81e7ece9be8bca12c/file.go#L72
Wire: https://github.com/moov-io/wire/blob/3b5b8d23fea6e4dbff6dd901ae3dd87096b95a64/fedWireMessage.go#L10

This issue came up in the community Slack group, specifically regarding the ArchiveTypeIndicator field.

Is there a way to solve this or ignore the error and continue parsing? I know 1 is invalid as a ArchiveTypeIndicator, but I am still trying to read the rest of the file.

Proposed implementation:

Use the ACH implementation as a template for these changes
Avoid breaking changes
Define a ValidateOpts struct to include flags for customizing validation behaviors

SkipAll for skipping all validation checks (see ACH for example)
SkipArchiveTypeIndicator to skip validation of ArchiveTypeIndicator

Add a validateOpts field to the ICL File (here)

Example from ACH here

https://github.com/moov-io/imagecashletter/pull/295


Bump mq

Brief description
Bumps mq to use parallel request handling
Checklist

[X] I have built this pull request locally
[X] I have ran the unit tests locally
[X] I have manually tested this pull request
[X] I have reviewed my pull request
[ ] I have added any relevant tests

Demonstration

Erroring in CI with:
cmd/[secure]-jsonrpc/main.go:115:16: Error return value of `util.EnsureDir` is not checked (errcheck)
	util.EnsureDir(*descriptorsDir)


Drop provider() overload having 3 arguments

Due to #2200
Targets the future v22

needs migration, I presume


Tradestation has changed authentication from auth2 to auth0 Guardian

Tradestation has changed authentication from auth2 to auth0 Guardian. This library still uses auth2, Can you please update the authentication

Have you worked around this issue yet?

@Gabedave how is your fork coming along? Does it work?

As stated, this code has to be refactored so that authentication works with auth0, new links and guidelines can be found in the docs: https://api.tradestation.com/docs/fundamentals/authentication/auth-code/
A couple of additional comments once you got auth0 working:

once you've authenticated, make sure that you change your calls endpoints + args respecting new api version (v3). can be seen on the above docs + specs
add offline_access in scope so that you can have access to refresh_token and make the process algorithmic without having to login on each iteration. PLEASE NOTE THAT YOUR CONFIG FILE SHOULD BE ENCRYPTED/DECRYPTED on the fly, which isn't done here and is a security concern.
if you've done the above, simply login within the init function and the code will take care of understanding if it has to go through the lengthy authentication process or it has a refresh token to grab.
modify line 567:             if response_headers['Content-Type'] == 'application/json; charset=utf-8' to ['application/json', 'charset=utf-8']


Update results and /data

update results
replace /data with link to llicl-data repository

Looks good to me!
Please add a license (e.g., Apache 2.0) to this repository, and merge this PR.


Where did you get jaco v0.9.5?

Heya! I was just looking at your plugin because I wanted to add mp3 functionality to mine and I saw you were using jaco mp3 player but online all I can see is v0.9.3 and v0.9.4. Where did you get a v0.9.5?

Apparently I found it in the firebeats plugin https://github.com/RKGman/fire-beats/tree/master/libs

Ha, the rabbit trail continues. I just want to make sure I'm using official code and nothing jank. So weird! Thanks.


! Unable to create an HTML environment quickly

Housekeeping

[X] I'm sure this issue is not a duplicate

Information:

This is an english-only repo, please translate your title to English!

这是一个只有英文的repo，请把你的标题翻译成英文！

ok

This shouldn't be a vscode icons, it should just work again if you hit CTRL - Space / Command - Space

@tumeo, I'm closing this as this doesn't seem related to our repo as @sasial-dev was pointing out. Feel free to counterargument here if you feel that that's not the case. Thanks!


[build fail] build ports/nrf/board/makerdiary_nrf52840_mdk_usb_dongle fail

when I build makerdiary_nrf52840_mdk_usb_dongle
$ make BOARD=makerdiary_nrf52840_mdk_usb_dongle
Use make V=1, make V=2 or set BUILD_VERBOSE similarly in your environment to increase build verbosity.
Unable to check whether maximum number of endpoints is respected
QSTR updated
common-hal/_bleio/Adapter.c: In function 'bleio_adapter_gc_collect':
common-hal/_bleio/Adapter.c:826:74: error: expression does not compute the number of elements in this array; element type is 'bleio_connection_internal_t', not 'size_t' {aka 'unsigned int'} [-Werror=sizeof-array-div]
  826 | ct_root((void**)bleio_connections, sizeof(bleio_connections) / sizeof(size_t));
      |                                                              ^

common-hal/_bleio/Adapter.c:826:74: note: add parentheses around the second 'sizeof' to silence this warning
common-hal/_bleio/Adapter.c:91:29: note: array 'bleio_connections' declared here
   91 | bleio_connection_internal_t bleio_connections[BLEIO_TOTAL_CONNECTION_COUNT];
      |                             ^~~~~~~~~~~~~~~~~
cc1: all warnings being treated as errors
make: *** [../../py/mkrules.mk:55：build-makerdiary_nrf52840_mdk_usb_dongle/common-hal/_bleio/Adapter.o] 错误 1

Can anyone help me?

Having the same exact issue here with make BOARD=feather_nrf52840_express

you are right!
thanks!


Scrape without logging in/without account

Hey, thanks for the great tool. I want to simply scrape one account, and don't have an Instagram account. Any way to use the tool without an account? I tried running it and omitting the --login-user and --login-pass parameters but it gives me an error that they are required. Why is that?
Thanks.

I don't think it will work.  You can use fake email if you are afraid of giving your primary email id.

When you don't specify credentials it doesn't use them now.


Feature/add drop

This change is

Reviewed 4 of 7 files at r1, 1 of 3 files at r2, 2 of 4 files at r4, 4 of 4 files at r5, 16 of 16 files at r6.
Review status: all files reviewed at latest revision, all discussions resolved.

Comments from Reviewable


Show output for when it is not installed

I see your point. I feel this loses some concision for the documentation, but indeed, since we don't say what you should see it seems important to help the user here. Thanks.


Do not fingerprint outputs

@bot-gradle test QFL please.

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

@bot-gradle test QFL this.

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

@bot-gradle test QFL please.

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

@bot-gradle test QFL please.

OK, I've already cancelled the old build and triggered a new QuickFeedbackLinux build for you.

@bot-gradle test QFL please.

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

@bot-gradle test QFL please.

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

@bot-gradle test QFL please.

OK, I've already cancelled the old build and triggered a new QuickFeedbackLinux build for you.

@bot-gradle test this please.

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

@bot-gradle test this please.

OK, I've already cancelled the old build and triggered a new ReadyForMerge build for you.

@bot-gradle test QF please.

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

@bot-gradle test this please.

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

@bot-gradle test QFL please.

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

@bot-gradle test QFL please.

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

@bot-gradle test QFL please.

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

@bot-gradle test QFL please.

OK, I've already cancelled the old build and triggered a new QuickFeedbackLinux build for you.

@bot-gradle test QFL please.

OK, I've already cancelled the old build and triggered a new QuickFeedbackLinux build for you.

@bot-gradle test QF please.

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

@bot-gradle test this please.

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

Is it now possible that we have an empty output snapshot when we store in the build cache? I don't think so, so I think we can remove this code or make it an error:

I removed it.

@bot-gradle test QFL please.

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

@bot-gradle test QFL please.

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

@bot-gradle test this please.

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

@bot-gradle test this please.

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

I am ready to merge this PR now. We should do the following in a separate PR:

Add more tests for OutputChanges, since it is not tested any more as part of FingerprintCompareStrategyTest
Remove the absolute path creation from PathTracker
Update the Javadoc on OutputUtil.


more verbose logging

enable (console) logger for arbitrary number of params

Thanks for the pull request!
Is this compatible with IE10 (with closed and opened dev tools) and the loglevel library?

I only test under OSX, sorry


2x3 Header No Longer in Stock

It was noted that following part is no longer available https://www.sparkfun.com/products/retired/13010
We need to identify a replacement part.

they are available on Amazon but come in pack of 25 pieces or more
https://www.amazon.com/Connectors-Pro-2-54mm-PCB-Through-Board/dp/B08R8LGM4L/ref=sr_1_3?keywords=2x3+female+PTH+header&qid=1661296397&s=electronics&sr=1-3-catcorr

Looks like this part is suitable: https://www.pololu.com/product/1023

Fixed.


PHP 7.1.3 version needed

Info:

Docker version ($ docker --version): Docker version 18.09.0, build 4d60db4
Laradock commit ($ git rev-parse HEAD):
System info (Mac, PC, Linux): d8c36ab86007f04293d380bcf8325cb70c76fdd0
System info disto/version:

Issue:
I need PHP (PHP-FPM) version 7.1.3. But in container I see that my PHP version is 7.1.25.
.env
# Select a PHP version of the Workspace and PHP-FPM containers (Does not apply to HHVM). Accepted values: 7.2 - 7.1 - 7.0 - 5.6
PHP_VERSION=7.1

### PHP Interpreter #######################################

# Select the PHP Interpreter. Accepted values: hhvm - php-fpm
PHP_INTERPRETER=php-fpm

How I can upgrade my PHP version to 7.1.3?

Version 7.1.25 is a higher version than version 7.1.3