Restore missing FAQ tutorial from website migration

Description
According to Lin Yuan,  https://github.com/apache/incubator-mxnet/pull/15517 was deleted from mxnet website and faq during the website migration. Restored this file in this PR.
Checklist
Essentials

[x] The PR title starts with [MXNET-$JIRA_ID], where $JIRA_ID refers to the relevant JIRA issue created (except PRs with tiny changes)
[x] Changes are complete (i.e. I finished coding on this PR)
[x] To the best of my knowledge, examples are either not affected by this change, or have been fixed to be compatible with this change

Changes

[x] Restore missing tutorial Use TensorInspector to Help Debug Operators of FAQ
[x] First PR - add my name to CONTRIBUTORS.md

Comments

Preview: http://ec2-54-188-205-145.us-west-2.compute.amazonaws.com/

@mxnet-label-bot add [Website]

@mxnet-label-bot add [pr-awaiting-review]

@mxnet-bot run ci [sanity]

@mxnet-bot run ci [sanity]

@ys2843 sanity build broke due to an update to pylint and it's dependency astroid. I'm fixing it as part of https://github.com/apache/incubator-mxnet/pull/18177
Once it is merged, you can retrigger sanity build to pass

@mxnet-bot run ci [sanity]

Thank you guys for reviewing and fixing the check problem.

@mxnet-bot run ci [windows-gpu ]

@mxnet-bot run ci [windows-gpu ]

@mxnet-label-bot update [pr-awaiting-merge]


Bumping cluster app with necessary changes

What this PR does
This PR bumps Cluster Chart to version 0.33.1 which introduces the Giantswarm Cluster Suite app. The GCS app is disabled by default, hence must be enabled in this app.
Checklist

[x] Updated CHANGELOG.md.

Trigger E2E tests

/run cluster-test-suites

Regarding giantswarm-cluster-suite, for simple resources like a Namespace and a PriorityClass, wouldn't it be simpler to inline them and apply them as a CAPI ClusterResourceSet defined in the cluster chart? Do you think that approach would be more complicated? I think it's simpler. and easier to reason about.
There wouldn't be a reason to maintain yet another App and a Github repository for that. It wouldn't be necessary to take care of dependencies between apps while creating a cluster. And updating these resources (I mean the Namespace and PriorityClass) would be only one PR to the cluster chart, instead of two of them (one on the app repo and then a version bump in the cluster chart). Finally, creating an app as a all-in-one bag having a mixture of different resources with no connection between them feels wrong somehow.
This feels like a more CAPI native way of solving our requirements. A ClusterResourceSet is a CAPI object that applies to the WC some manifests defined in a ConfigMap (not just once, it will reconcile/re-apply the contents if the contents of the ConfigMap change). You can find more details in the design proposal.
In this case, the Namespace and the PriorityClass would be defined in the cluster chart, and whenever we need to update those (if ever) or new resources are needed, they would get re-applied by CAPI.
What do you think?

Thank you.

/run cluster-test-suites

@fiunchinho I discussed that within the team and to be honest, we are indifferent to how these two resources are provided to the cluster, this seems however a bit troublesome to change the approach now, for this app is already part of Cluster app and we initiated changes to Release CRs as well. On top of that, creation of this new app has been agreed a time ago, see this Slack thread, so we would prefer continuing this approach, just to get the changes we need live as soon as possible, but then at some point if you have better solution we could replace it with that.

Not sure though why test fails for China. The first run reported:
Summarizing 1 Failure:
  [FAIL] Common tests hello world [It] should have a ready Certificate generated
  /app/internal/common/hello.go:243

while the second:
Summarizing 3 Failures:
  [FAIL] Common tests basic [It] has all its Deployments Ready (means all replicas are running)
  /app/internal/common/basic.go:82
  [FAIL] Common tests hello world [It] cluster wildcard ingress DNS must be resolvable
  /app/internal/common/hello.go:121
  [FAIL] Common tests scale [It] scales node by creating anti-affinity pods
  /app/internal/common/scale.go:146

What seems like unrelated to my changes, maybe.

/run cluster-test-suites TARGET_SUITES=./providers/capa/china


Adds utility functions and unroll_reinject.

Adds a helper function (unroll_reinject) for unrolling RNNs while re-injecting their output as the input at the next timestep. For example, this function can be used as the decoder in encoder-decoder RNN architectures.
Also adds two utility functions that help deal with padded batches:

utils.select: for taking a tensor of shape [batch_size, sequence_length, param_dim] and an array of indices with shape [batch_size,] that indicate the length of each example, and returns a tensor of shape [batch_size, param_dim] that selects out the ith example of each sequence, where i is given by the indices array.
utils.build_mask: takes a sequence length (T) and returns a function that when given an array of indices of length N returns a binary mask of shape [N, T] where the first i elements of each of the N rows are one, and the rest are zero. This is useful for building binary masks that can be used to mask in only the valid (non-padded) elements of a sequence.

I added a test for utils.build_mask.  It would be nice to test utils.unroll_with_reinject, but I'm not sure how to make a clean test for this.

I added a test for utils.build_mask.  It would be nice to test utils.unroll_with_reinject, but I'm not sure how to make a clean test for this.

Otherwise, LGTM.  I can open an issue for adding a test for unroll-reinject.

Otherwise, LGTM.  I can open an issue for adding a test for unroll-reinject.


Resource control based on cgroup

See the doc for more details.

@scv119 want to shepherd this one?

@ericl @simon-mo We've refined the structure of the whole doc.

In the current runtime env plugin mechanism design, a plugin must implement a whole runtime env type (e.g., pip, conda, etc).  Cgroup is different here. Because it is more like a config of runtime env, rather than a new runtime env type. Because it can be used together with other types.  So in order to pluginize cgroup, we may need a new plugin mechanism that can extend the the current plugin mechanism. This seems weird. and I'm not sure if such a new plugin mechanism can be re-used for other features.  So I think maybe we can consider pluginizing it later if we have a second similar requirement.

I'm not sure I see this as weird. This was one of the original use cases we envisioned for runtime_env plugins when we designed it (arbitrary modifications to the environment, such as attaching debuggers, resource limits, etc.).

with the current plugin mechanism, it's hard to implement cgroup deletion. As I said here #7 (comment), the cgroups are one-off. It couldn't be shared and reused. So, the logic should be that: Create cgroup -> start worker -> worker dies -> delete cgroup. For example, if the cgroup dir is /sys/fs/cgroup/{worker_id}, we can't reuse the reference counting logic to delete this dir because we don't provide the worker_id when we decrease the reference by the PRC from raylet to agent.

This doesn't sound like a fundamental issue, but something we can add right? Here's my concern: we're adding a ton of stuff into core, which will not be used by most users. If we can do this with the existing plugin infra, with some minor improvements, then longer term that leads to a better architecture than handling it directly in core. I can understand it makes this project a little more involved, but from the overall Ray project perspective this is cleaner long term as we might have other types of plugins of this sort.

@ericl I agree that the pluggable architecture could make the core cleaner in long term. And I could try to make it to be a resource_control plugin. But I think the current abstraction of runtime env plugin is not clear and couldn't meet my requirements. We should redefine it first. Not sure if we need to create a separate REP for this. And we need to do more discussion about this with @edoakes and @architkulkarni.
btw, I don't think the resource control is a minor improvement. Maybe it will be a basic ability of Ray Core and widely used by users in large scale cluster in future. We already have a lot issues in Ant and we plan to put it into production in few month.

I'd like to see the discussion outcome then. If @edoakes and @architkulkarni think it's not a good fit for runtime env plugin, then I'm fine with that decision.

@ericl I agree that the pluggable architecture could make the core cleaner in long term. And I could try to make it to be a resource_control plugin. But I think the current abstraction of runtime env plugin is not clear and couldn't meet my requirements. We should redefine it first. Not sure if we need to create a separate REP for this. And we need to do more discussion about this with @edoakes and @architkulkarni.

The issue with deletion makes sense, I agree it seems tricky to support it with the current abstraction.  What would the ideal abstraction look like?  One naive idea is to have each runtime env plugin have a method OnWorkerDead(worker_id: int) which is called whenever the worker dies, but that might be too specific to this use case.

The issue with deletion makes sense, I agree it seems tricky to support it with the current abstraction. What would the ideal abstraction look like? One naive idea is to have each runtime env plugin have a method OnWorkerDead(worker_id: int) which is called whenever the worker dies, but that might be too specific to this use case.

Yep, we should add a method like what you said. And we should do more things to make it ideal. For example, we need to support configuration for each plugin, because I will add a lot cluster level config here https://github.com/ray-project/enhancements/pull/7/files#diff-98ccfc9582e95581aae234797bc273b2fb68cb9e4dcc3030c8e94ba447daef7dR24.
@architkulkarni btw, do we plan to make current runtime env modules, like pip and conda, to be plugins? Or we will keep it in long term?
Another thing is what @raulchen said here https://github.com/ray-project/enhancements/pull/7#discussion_r847047753. What do you think about this? In addition, do we need to support applying multiple plugins? If we do, how can we guarantee the sort and avoid the conflicts between plugins? We should consider any more for those issues in the abstraction of plugin, right?

I made some edits to https://docs.google.com/document/d/1x1JAHg7c0ewcOYwhhclbuW0B0UC7l92WFkF4Su0T-dk/edit# that I think will enable cgroups to be supported (namely, adding priority, create_for_worker, delete_for_worker). Cgroups might be implementable out of the box as a plugin after these hooks are added, wdyt?

I made some edits to https://docs.google.com/document/d/1x1JAHg7c0ewcOYwhhclbuW0B0UC7l92WFkF4Su0T-dk/edit# that I think will enable cgroups to be supported (namely, adding priority, create_for_worker, delete_for_worker). Cgroups might be implementable out of the box as a plugin after these hooks are added, wdyt?

I got your thought. But I think this doc is still not clear.

How these hooks cooperate with the Raylet and the Agent? How to refine the RPC ?
How the plugin affects the runtime env cache? Currently, if the runtime env json is same, we will return the cached runtime env context. But in the case of cgroup, maybe the context is different?
How to implement configuration of each plugin?

btw, @ericl @architkulkarni I think we should also make the google doc to be a REP, wdyt? Who can take this work? I'm also available for this if you don't have bandwidth.

I think we are on the same page that resource control is better implemented as a plugin. Also, it seems that the plugin system still needs an overhaul to meet different kinds of runtime env requirements.
So my suggestion is that we can do 2 things simultaneously:

summarize the minimal needed changes of the plugin system to support cgroup. And make these changes as part of the this REP.
discuss what other changes are needed to support other plugins, and potentially file another REP for the plugin system refinements.

What do you think? If we agree, @SongGuyang can add the first part to this REP first.

+1
On Thu, Apr 14, 2022, 9:27 PM Hao Chen @.***> wrote:

I think we are on the same page that resource control is better
implemented as a plugin. Also, it seems that the plugin system still needs
an overhaul to meet different kinds of runtime env requirements.
So my suggestion is that we can do 2 things simultaneously:

summarize the minimal needed changes of the plugin system to
support cgroup. And make these changes as part of the this REP.
discuss what other changes are needed to support other plugins, and
potentially file another REP for the plugin system refinements.

What do you think? If we agree, @SongGuyang
https://github.com/SongGuyang can add the first part to this REP first.
—
Reply to this email directly, view it on GitHub
https://github.com/ray-project/enhancements/pull/7#issuecomment-1099840101,
or unsubscribe
https://github.com/notifications/unsubscribe-auth/AAADUSWAKNJHTPLAV4G5WPLVFDV4JANCNFSM5S4EASIQ
.
You are receiving this because you were mentioned.Message ID:
@.***>

@raulchen +1. Please keep @architkulkarni in the loop on the plugin changes, he can also help scope out the design offline first.

I will continue to work on current REP this week and back to discuss with you about the left comments.

@ericl @architkulkarni @simon-mo @rkooo567 Take a look again?

We would prefer that the functionality does not live in the main Ray repo to begin with, but we can reevaluate this later as it matures and we get more user feedback.

Why it couldn't to be an experimental module in the main Ray repo? I didn't get a strong reason for this in your description.

We aren't quite sure what the gap between this and the container field in runtime_env is or how we should be thinking about them together. Should we support both? Can we support the cgroup functionality by extending container support? If we are providing cgroup, should we remove container support? Additionally, the existing container support has not been publicly documented/adopted nor maintained. Given these concerns, we think it would sense to evaluate both the container and cgroup options holistically as part of this REP -- a strawman proposal would be to move the existing container support out of the codebase and into a plugin as well if we think both are needed.

I think we need both.
Cgroup is only used to control the physics resources, e.g. cpus and memory, but the container is used for a lot of purposes, e.g. custom linux kernel, custom system packages(yum install ...), custom file system, and resource control certainly. We cannot use container instead of cgroup in some scenes because cgroup is more lightweight which doesn't rely on image and image center. When you create a directory in the file system, a cgroup is obtained.
Can we only add some description like what I say above? Container is another big issue. I ensure that it could also be a plugin. But, please don't let it block the pluggability enhancement and cgroup. We can discuss it in a separate issue or REP.

@edoakes here are my thoughts to your questions.

Why need both cgroup and container?

As @SongGuyang mentioned above, sometimes users only want resource control + pip requirements. In this case, containers are too heavy-weighted, as they would have to manage their docker files and images.

Where should the code live?

I'd prefer to putting it in the main repo (at least to begin with). For one, I think the resource control requirement is as common as other existing ones. Putting it in the main repo would benefit more users. For another, we need to keep refining the plugin system along with this feature. Putting everything in the same repo would facilitate testing.
I think we can put it in a new "runtime_env_plugins" directory, and later migrate existing runtime env to this directory as well. The core shouldn't depend on anything in this directory. Also, runtime envs can be shipped separately as well. E.g., "pip install ray[runtime_env_pip]" "pip install ray[runtime_env_container]".

@SongGuyang @raulchen
Re: cgroups + containers, I understand that you cannot use cgroup as a replacement for containers, but containers are essentially a superset of cgroup, so could we leverage the existing container support for this purpose as well without requiring users to specify an image or worry about other container details? For example, make the image and cgroup options both configurable in the container command and the image is optional.
Re: putting it in the repo vs. outside, the reasoning is we do not yet have evidence of user demand for this feature and adding it to the core repo increases maintenance burden. A relevant example is the container support in runtime_env: this is not something used by the community because it's not polished or well-documented, but it has increased maintenance burden for runtime_env and caused test failures without anyone taking clear ownership (the relevant test is now disabled). We want to ensure the same thing doesn't happen w/ cgroup support. Once the feature is fully-fledged and we see user demand, we can reconsider promoting it to put it in the repo.


[+orion] Bug 'do you like yourself'

The following answer was a given by sugaroid, and is considered as a bug. Please
manually review this issue, and close it if it looks unnecessary.

user: do you like yourself
sugaroid: Yes. I guess I like to like

@srevinsaju @TheDarkDrake,  do you have any suggestions on the reply sugaroid should give on "do you like yourself"

hmm

Hmmm indeed

yes,, indeed

@sreyasaju for insight, read this: https://www.quora.com/Do-you-like-yourself-1

Wait, wasn't the reply to "do you like yourself" different

Wait, wasn't the reply to "do you like yourself" different

different?

this was in the telegram group tho

like to like?

Wait, let me check

oh yes

Thats right, I am not sure how it came

At different times, sugaroid gives different answers. Sometimes it understands, sometimes it doesn't. Sometimes it gives one answer, sometimes different

For

Do you like to like: Give a list of answers and choose a random one
Do you like yourself: Read that previous Quora answer

Does it sound right?

wait, should sugaroid  like the user more than itself or
should it like itself more than the user

wait, should sugaroid like the user more than itself or
should it like itself more than the user

good question

A group of people have voted for "Sugaroid Itself", as sugaroid is not a bot, but a bot which is trying to act like real people. As it needs Human Traits, its important to like oneself, and we are not comparing it with other people. For the question, "Do you like yourself", the answer should be yes. You should not say, just yes. But a bunch of philosophical statements which seem to agree with the accepted idea.

hmm.. makes sense :)

Yep, perfect. Now, the response as a whole. A response should be made having those philosophical statements


Update contact section of CODE of CONDUCT

In an effort to help enforce the code of conduct I did things the wrong way. According to this I should have opened an issue (instead I opened a discussion which I think is pretty much the same, both are public)
This remove the line about opening an issue and instead says to contact privately.
I think for this to be effective there needs to be some kind of email (like<EMAIL_ADDRESS>or some way of contacting. Right now I was expected to contact people privately, but did not know who to contact or how.

I also wonder if it'd be a good idea for the core team to get togther and read through the CoC and make sure it is all up-to-date and covers the things the community cares about. I think it is pretty good, but may be worth a second look. Thanks for considering this PR


Sagfault at createExecutionContext on Jetson

So I've tried this code (both regular detect and detect for Jetson) with a custom ONNX model (YOLOv8s with 42 classes). Both versions work on Windows PC (CUDA 11.4/TRT <IP_ADDRESS>) with GTX 1070. However when I'm trying to run it on Jetson (CUDA 10.2/TRT <IP_ADDRESS>) I'm getting segfault on createExecutionContext call, and gdb can't even backtrace it on a debug version. Tried on 2 Jetsons (thought might be an issue with one of them) to no luck.
Any ideas what could it be?

I am sorry to hear that.
But do you try csrc/jetson/detect code on jetson.

I've tried both:
csrc/jetson/detect
and
csrc/detect/normal
Same result.
I don't think it's a problem in your code, but maybe you have any ideas?

I've tried both: csrc/jetson/detect and csrc/detect/normal Same result. I don't think it's a problem in your code, but maybe you have any ideas?

But I run it well on my TX2.
What's your jetpack version?
Please update it to jetpack4.6.3+

I have 4.6.3-b17 version already

Your error message is too sparse for me to help pinpoint the location. Please send screenshots or other information

7. createExecutionContext

There are so few error messages that I can't help locating them.

I cannot too. This is why I think it is library problem. I will try newer Jetpack now.

I cannot too. This is why I think it is library problem. I will try newer Jetpack now.

Okay. Hope you get the correct result soon!

Hello, it appears that I'm encountering the same issue. Have you found a solution to this problem?

Unfortunately no. I've spend many time rewriting a new code from several repositories including this one until eventually I've managed to get it to work. However it's a piece of larger product under NDA so I can't share it unfortunately.

Okay, thanks for your reply.

closed, feel free to reopen it if you have further questions. Thanks!


Proposal for Linux Seccomp addition to Marathon

Summary:
We need to add seccomp to Marathon.  This requires a Mesos bump to version 1.8.
JIRA issues: DCOS-50606

thanks for the feedback.   I didn't care for the "Info" of linuxInfo... Info is such a vague term as to not add value IMO.     I think "runtime" is closer.. but it makes sense to be consistent... and it is easy to claim traceability to the mesos defined "Info" of LinuxInfo.   Seems like we are there... thanks!


ci(release): make Dependabot dependency updates trigger patch releases

By default, only fix/feat/BREAKING triggers a new semantic release. I think Go dependency updates also deserve a new release. This PR slightly modifies the Dependabot configuration so that Go dependency update PR should be prefixed with build(deps):. Then configures the semantic-release release configuration to trigger releases for those commits, and includes dependency updates in a separate section of the release notes.
Inspired by https://mattbun.io/posts/semantic-release-dependabot/, and tested in https://github.com/erikgb/test-ci-release.

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


DHCP Relay send/listen on same interface. Issue #10381

[x] Redmine Issue: https://redmine.pfsense.org/issues/10381
[x] Ready for review

Required to OpenVPN clients to get DHCP address from internal DHCP server across the bridge.

https://redmine.pfsense.org/issues/10381?next_issue_id=10380&prev_issue_id=10382#note-11:

However, after reading that DHCP is a special case on pfSense, it is allowed with hidden rules that are activated when DHCP is used on an interface. (https://forum.netgate.com/topic/90384/help-clarify-my-understanding-of-the-net-link-bridge-pfil-tunables-please/3) I added firewall rule on LAN interface, allowing UDP on port 67 and 68 to pass and now DHCP is working.
MacOS OpenVPN clients are receiving DHCP offer from servers and get IP address without dhcrelay running. So I have found "a workaround" or finally have a proper configuration, whatever.


Provide full JSON key path in labelRenderer (in reverse order)

Before:
labelRenderer(key) => {key}

After:
labelRenderer(key, parentKey, ..., rootKey) => {key}

This can be used to determine exact position in data object (to navigate in onClick handler, for example).

I would love to see this merged. It enables a great use case in https://github.com/alexkuz/redux-devtools-inspector.

@alexkuz @gaearon merged in 0.5.6!

👏

@alexkuz This whole workflow breaks immutable support in redux-devtools-inspector. I'm hoping to submit a pull request soon, but you know your code better than I do so if you come up with a way to easily fix that it might be simpler than whatever I might come up with?

Okay so I might have been a bit eager with why immutable does not work in Inspector. One issue is actually with react-json-tree which I've reported here: https://github.com/chibicode/react-json-tree/issues/34 and the other is that your JSONDiff module doesn't support Iterables at all. I imagine this is probably something you realised in the latter case, but if you haven't even considered making progress on this I'd be happy to help out, as I love the look of this monitor and really would like to start integrating it into my workflow. For now I'm running a forked version with 'state' as the default tab and hideRoot set to false, but I'd love to take advantage of some of the more advanced features, and if contributing would help speed that up let me know.

@leonaves can you file an issue to redux-devtools-monitor? I haven't check Immutables yet as I'm not really using them (though I should).

Do you mean redux-devtools-inspector?

@leonaves yeah, sorry :)

Looks like this broke https://github.com/gaearon/redux-devtools-log-monitor:
https://github.com/gaearon/redux-devtools-log-monitor/issues/39
This is a public API change and should have been a minor bump rather than a patch bump.

For now I locked redux-devtools-log-monitor to use 0.5.5. The solution here would be:

Release 0.5.7 that undoes the change in 0.5.6
Release 0.6.0 that introduces it again


Remove feature flag section from Mx9 Git how-to

As --enable-git-support feature flag is not available for Mx9 anymore we have to remove the section 4.2 from the Git how-to document.

 Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.Maksym Vyhovskyi seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.You have signed the CLA already but the status is still pending? Let us recheck it.


Kubelet Stats Receiver is a new feature and kubelet can use an upper case K in this instance

https://github.com/openshift/openshift-docs/pull/73626/files#r1535802857 - example false positive. I don't understand why the error message doesn't suggest replacing with "kubelet" - I can't replicate this locally - but at least this rule won't fire on this product name

Is this something to do with it being in a heading.


Grid typesetting support

Description
A professional typesetting system should have extensive support for grid typesetting. InDesign supports (as well as a lot of other professional DTP applications) baseline grid and document grid for typesetting and "snapping" of objects to it. See: https://helpx.adobe.com/indesign/using/grids.html
General information on baseline grid layout and why it is needed:

https://www.haydnsymons.com/blog/the-ultimate-beginners-guide-to-the-baseline-grid/
https://www.onlineprinters.de/magazin/registerhaltigkeit/ (German)

Alternatives to Typst have none or only basic support for this functionality so far:

LaTeX: With LaTeX it's nearly impossible to achieve it, because of diversity of packages and some limitations of TeX engine itself. Although there is a grid package (https://ctan.org/pkg/grid) it's impossible to guarantee grid layout in complex documents.
ConTeXt: With ConTeXt you get good support for grid typesetting. They could implement it, because packages are more uniform than in LaTeX and ConTeXt is based on LuaTeX, which allows to implement more complex handling with Lua code: https://wiki.contextgarden.net/Grid_typesetting and http://context.aanhet.net/svn/contextman/context-reference/en/co-pagedesign.pdf (esp. p. 9-10). But it's still limited (difficult to place first line of heading, which is larger or smaller than grid, on baseline grid - or - adjusting non-paragraph objects like floating objects vertically centered between nearest baselines). Overall it's quite complicated to use and documentation is hard to find.
troff: With troff grid typesetting is possible, but the only macro package which supports it out of the box is mom (https://www.schaffter.ca/mom/momdoc/docprocessing.html#vertical-whitespace-management). Mom is based on GNU troff, which is unfortunately not as good as TeX/pdftex regarding microtypography. There is only one troff implementation, which has similar typographic qualities: neatroff. But neatroff is not compatible with mom.
SILE: SILE typesetter does a lot of things right and it has support for grid typesetting (https://sile-typesetter.org/what-is-sile/). But the actual implementation (https://github.com/sile-typesetter/sile/blob/master/packages/grid/init.lua) is quite basic and can't compete with ConTeXt at this point. It also looks like the current SILE development team is focusing on other features than grid typesetting in the near future.

Use Case
By implementing extensive support for grid typesetting, Typst would have a unique feature among other open source text-based typesetting systems. Apart from that, it's state of the art to have gridline typesetting in professional documents, especially in multi-column documents.

Hopefully this will be accepted.

I want to support this, but don't have concrete plans yet.

+1
This is the basis for all my layout work in any DTP app I used in the last 30 years.

Maybe a snap() function, similar to align() that can reference grids defined somewhere else in the document?


Rainbow fringes on certain scales of glasses

For example:

The happens on the middle of the glasses as well.
Example:

I'll see I can I get this in an offline environment with controlled vars for scale and background.
This will require trouble shooting. Isn't alpha blending in OpenCV really weird with blending?

I think the issue is that we're not using a real filtering algorithm, and so for the rainbow: that's the random memory you sometime get in transparent areas bleeding in because of different filtering on the alpha and the color. This could potentially be fixed by editing the original png depending on the implementation of the png loader.


Building for production with custom server

Hey there, quick on the question. I am running next build in the project directory and then starting my custom server in production mode NODE_ENV=production node server but I am getting tis error

Error: Cannot find module '/Users/andreiungureanu/WebstormProjects/internal-issuuinfo/.next/build-stats.json'

Any ideas on what to do ? Or is there any other way to set the production mode ?

@Andrei997 did you run npm run build before?

As @impronunciable mentioned, you need to build your app first.


fix: Update helm CRD

What this PR does / why we need it:
Which issue(s) this PR fixes:

Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?:

Update CRD in helm charts

/assign @gaocegege @FogDong

/lgtn

Need lgtm, need update it again @FogDong

/lgtm

/approve

We are not in the OWNER group...😅   /cc @gaocegege


docs(state): Use different terms for block verification and state queues

Motivation
Close https://github.com/ZcashFoundation/zebra/issues/6681
Solution
Do suggested renames.
Review

Reviewer Checklist

[ ] Will the PR name make sense to users?

[ ] Does it need extra CHANGELOG info? (new features, breaking changes, large changes)

[ ] Are the PR labels correct?
[ ] Does the code do what the ticket and PR says?

[ ] Does it change concurrent code, unsafe code, or consensus rules?

[ ] How do you know it works? Does it have tests?

Follow Up Work

This PR should be rebased to main after https://github.com/ZcashFoundation/zebra/pull/7035 is merged.
I forgot how to set up an automatic rebase. I will add that when i find the feature.


Touchswipe false doesn't work in breakpoint

I using this code to disable touchSwipe disable in smaller screens:
$( '#Carousel' ).sliderPro({
width: 200,
height: 150,
autoHeight: false,
autoplay:false,
fade: false,
arrows: true,
buttons: false,
visibleSize: '100%',
breakpoints: {
500: {
touchSwipe: false,
fadeArrows: false,
},
},
})
It doesn't work. What do I wrong?

The touch-swipe feature can't be disabled if it's initially enabled. I didn't consider this as a necessity, as I think in most cases you want the touch-swipe to be active on smaller screens, which are usually touch-enabled screens.
Cheers

But, when I want to make a carousel with links, I can't open them. Is there a solution?

If you're referring to text links, try to add the 'sp-selectable' class to them.

It helps. Thanks.


squid:S2097, squid:S1488 - "equals(Object obj)" should test argument …

This pull request is focused on resolving occurrences of Sonar rule squid:S2097, squid:S1488 - "equals(Object obj)" should test argument type, Local Variables should not be declared and then immediately returned or thrown
You can find more information about the issue here:
https://dev.eclipse.org/sonar/coding_rules#q=squid:S2097
https://dev.eclipse.org/sonar/coding_rules#q=squid:S1488
Please let me know if you have any questions.
M-Ezzat

Just started reviewing :):rocket:


fix(sandpack-client): fixing package exports

What kind of change does this pull request introduce?
Fixes package exports again and enable code-splitting and dynamic imports in esbuild
docs: https://esbuild.github.io/api/#splitting
fix #724

Split this PR on bundler changes: https://github.com/codesandbox/sandpack/pull/741


App crash after open immediately?

Description:

There is no error alert or anything the app just stopped after opened but I debug from Android studio and found this error.
 E/AndroidRuntime: FATAL EXCEPTION: main
  Process: app.udrinkidive.feed2us.com.udrinkidrivebeta, PID: 30554
java.lang.NoClassDefFoundError: Failed resolution of: Lcom/google/android/gms/common/internal/zzbq;
 at com.google.firebase.provider.FirebaseInitProvider.attachInfo(Unknown Source)

Environment

"react-native": "0.50.3"
using npm "react-native-onesignal": "^3.0.9",
'com.android.tools.build:gradle:3.0.0'
compileSdkVersion 26,     buildToolsVersion "27.0.3"
Is this have something to do with one-signal? because it is my only library that involve firebase. How to solve this?

same issue here.. any solution found?

@nilaybrahmbhatt Not yet. Not really. Stuck here for two weeks now.

@pacozaa Unfortunately this is a common issue with Android & gradle in general.
But it's also very well documented on Google
Here's some links you might find helpful.
https://stackoverflow.com/questions/41322864/java-lang-noclassdeffounderror-failed-resolution-failed-resolution-of-lcom-goo
https://github.com/OneSignal/OneSignal-Android-SDK/issues/298
I'll be closing this issue since I do not see how it is related to our SDK. However I will reopen the issue if you can investigate further and provide some more details. Please try removing our SDK from your project and then re-run your app and let me know if the issue still occurs. If not, then please post some more information and I will be happy to reopen the issue and investigate
app/build.gradle
android/build.gradle
gradle-wrapper.properties

@pacozaa Is this have something to do with one-signal? because it is my only library that involve firebase. How to solve this?
Double check you're implementing Firebase in your project, I get this issue when I forget to include Firebase Core. Check android/app/build.gradle includes the following.
dependencies {
    ...

    implementation 'com.google.firebase:firebase-core:17.0.0'
}

https://firebase.google.com/docs/android/setup#add-sdks
If you haven't already you'll need a google-services.json configuration file for your project. You can follow this documentation on how to create one: https://firebase.google.com/docs/android/setup#add-config-file
This is a bit of a shot in the dark, nonetheless I hope it was helpful.


Update munit-cats-effect-3 to 1.0.2

Updates org.typelevel:munit-cats-effect-3 from 1.0.1 to 1.0.2.
GitHub Release Notes - Version Diff
I'll automatically update this PR to resolve conflicts as long as you don't change it yourself.
If you'd like to skip this version, you can just close this PR. If you have any feedback, just mention me in the comments below.
Configure Scala Steward for your repository with a .scala-steward.conf file.
Have a fantastic day writing Scala!

Ignore future updates
Add this to your .scala-steward.conf file to ignore future updates of this dependency:
updates.ignore = [ { groupId = "org.typelevel", artifactId = "munit-cats-effect-3" } ]

labels: test-library-update, semver-patch

Superseded by #196.


fix compilation for target wasm32-wasi

This PR partially reverts https://github.com/rusqlite/rusqlite/pull/961 that has introduced a bug in detection of wasm32-wasi target. That PR replaced the check of TARGET with a check of CARGO_CFG_TARGET_ENV. That however is incorrect because wasm32-wasi is a CPU architecture target (similar to x86 and armv8) and not an operating system.
This PR only affects wasm32-wasi compilation and is a no-op for other targets.

See #1116 and #1289

@gwenn, thanks for the reply and linking the existing attempts to fix the bug. I apologize for sending a PR with an empty description. I fixed it now.
The bug was introduced in https://github.com/rusqlite/rusqlite/commit/5511a12e57af7bead3d32bdc0618cf754e56a97e?diff=split#diff-c1c013e096409a5aea1f123c04254379057791785963eba5ef253fdd686570b8L120
My PR reverts the change that introduced the bug. I verified locally that wasm32-wasi works locally after this partial revert.
My fix looks very similar to PR #1116, but it doesn't have the || is_compiler(..) part which is superfluous. If you would like to proceed with PR #1116, I am happy to close my PR and continue the work in #1116.
The PR #1289 is incorrect because it is changing the definition of is_compiler().

Thanks for the explanation.


Sending emails does not seem to work anymore

Even though sending emails wasn't working in the first place, it now breaks development if you try to send an email due to an error with attachments.

PR merged. Closing issue


[ADN] ERROR: Unable to extract config URL

C:\Windows\system32>youtube-dl --verbose https://animedigitalnetwork.fr/video/clannad/12828-episode-1-sur-la-pente-aux-cerisiers
[debug] System config: []
[debug] User config: []
[debug] Custom config: []
[debug] Command-line args: ['--verbose', 'https://animedigitalnetwork.fr/video/clannad/12828-episode-1-sur-la-pente-aux-cerisiers']
[debug] Encodings: locale cp1252, fs mbcs, out cp850, pref cp1252
[debug] youtube-dl version 2020.05.08
[debug] Python version 3.4.4 (CPython) - Windows-10-10.0.19041
[debug] exe versions: ffmpeg 4.3.1-2020-10-01-full_build-www.gyan.dev, ffprobe 4.3.1-2020-10-01-full_build-www.gyan.dev
[debug] Proxy map: {}
[ADN] 12828: Downloading webpage
ERROR: Unable to extract config url; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
Traceback (most recent call last):
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmp4z7swgz7\build\youtube_dl\YoutubeDL.py", line 797, in extract_info
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmp4z7swgz7\build\youtube_dl\extractor\common.py", line 530, in extract
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmp4z7swgz7\build\youtube_dl\extractor\adn.py", line 129, in _real_extract
File "C:\Users\dst\AppData\Roaming\Build archive\youtube-dl\ytdl-org\tmp4z7swgz7\build\youtube_dl\extractor\common.py", line 1005, in _search_regex
youtube_dl.utils.RegexNotFoundError: Unable to extract config url; please report this issue on https://yt-dl.org/bug . Make sure you are using the latest version; type  youtube-dl -U  to update. Be sure to call youtube-dl with the --verbose flag and include its complete output.
I think they updated their player

Issou

up.
Any date or any plan to face this code rewriting please ?!?
The key method for subtitles downloading seems to be also outdated :(
Thanks a lot for your consideration.
Take care !


How do I share a draw target with a console::Term?

I'm confused because ProgressDrawTarget::to_term takes Term by-value.

In new versions of console terminals can now be cheaply cloned.


Add linting for gulpfile.js

Now that folks are adding to it, it should be linted.

Actually, eslint isn't necessary - tslint can do it.


when code release?

Sorry, I was too busy this month, I will update the codes during the weekend. Sorry for the inconvenient.

@forkbabu you need the code for multi modal translation or creating a smooth transition between two images? Thx

@forkbabu  I just upload the Cross-domain Image Morphing codes.


ImportError: bad magic number in 'geo_map_cython_lib': b'\x03\xf3\r\n'

the detail about the error is :Traceback (most recent call last):
File "/home/user/east/EAST-pytorch/main.py", line 11, in
from data_utils import custom_dset, collate_fn
File "/home/user/east/EAST-pytorch/data_utils.py", line 18, in
from geo_map_cython_lib import gen_geo_map
i search a lot , but not solved this error,so how to solve the error to run the code correctly?thanks..

Just delete all the *.pyc files in geo_map_cython_lib folder.

Just delete all the *.pyc files in geo_map_cython_lib folder.

In this case it starts to give the error "libpython2.7.so.1.0: cannot open shared object file: No such file or directory"
Does it mean this repo works only for Python2 ?

You can try to run it on Python3, I used python3 and this problem was solved.

You can try to run it on Python3, I used python3 and this problem was solved.

i find this method before,but when i delete the init_.pyc, new problem occur:
ImportError: dynamic module does not define module export function (PyInit_gen_geo_map);
the init_.pyc ｉｓ downloaded from git repository.do you meet the same problem?

You can try to run it on Python3, I used python3 and this problem was solved.

i find this method before,but when i delete the init_.pyc, new problem occur:
ImportError: dynamic module does not define module export function (PyInit_gen_geo_map);
the init_.pyc ｉｓ downloaded from git repository.do you meet the same problem?

Have you solved this problem

ImportError: dynamic module does not define module export function (PyInit_gen_geo_map);
the init_.pyc
I did not meet this problem. But I guess it related to the OS you used. I used Win10.

Just delete all the *.pyc files in geo_map_cython_lib folder.

In this case it starts to give the error "libpython2.7.so.1.0: cannot open shared object file: No such file or directory"
Does it mean this repo works only for Python2 ?

I meet the same problem. Have you solved it now?

Just delete all the *.pyc files in geo_map_cython_lib folder.

In this case it starts to give the error "libpython2.7.so.1.0: cannot open shared object file: No such file or directory"
Does it mean this repo works only for Python2 ?

I met the same problem. Have anyone solved it yet?

只需删除geo_map_cython_lib文件夹中的所有* .pyc文件即可。

You can try to run it on Python3, I used python3 and this problem was solved.

python3.0？I used python3.7 and that can not

有关该错误的详细信息是：跟踪（最近一次通话最近）：
文件“ /home/user/east/EAST-pytorch/main.py”，第11行，
从data_utils导入custom_dset，collate_fn
文件“ / home / user / east / EAST-pytorch / data_utils.py“，第18行，
来自geo_map_cython_lib import gen_geo_map
我搜索了很多，但没有解决此错误，那么如何解决错误才能正确运行代码？

that is python3.0? I use python3.7,but the problem is not solved

Use the ls -a command in geo_map_cython_lib to find all the .pyc files deleted.

when i trained main.py,i met this problem.how to do with?

when i trained main.py,i met this problem.how to do with?

I have also met this problem, and I solve it by run build_ext.sh, or directly input command
python setup.py build_ext --inplace
Hope it works for you.

thank you
---Original---
From: "Zhu<EMAIL_ADDRESS>Date: Sat, Dec 14, 2019 22:14 PM
To<EMAIL_ADDRESS>Cc: "Comment"<comment<EMAIL_ADDRESS>Subject: Re: [songdejia/EAST] ImportError: bad magic number in 'geo_map_cython_lib': b'\x03\xf3\r\n' (#17)
when i trained main.py,i met this problem.how to do with?
I have also met this problem, and I solve it by run build_ext.sh, or directly input command
python setup.py build_ext --inplace
Hope it works for you.
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub, or unsubscribe.

ImportError: dynamic module does not define module export function (PyInit_gen_geo_map);
the init_.pyc
I did not meet this problem. But I guess it related to the OS you used. I used Win10.

I have the same problem and I use Win10 too. Have anyone solved this problem?  THANKS

删除__init__.pyc, 重新运行build_text.sh，python3.6, centos,docker有效

when i trained main.py,i met this problem.how to do with?

I have also met this problem, and I solve it by run build_ext.sh, or directly input command
python setup.py build_ext --inplace
Hope it works for you.

I used this way, not solve this problem... Unresolved reference 'gen_geo_map'

删除__init__.pyc, 重新运行build_text.sh，python3.6, centos,docker有效

亲测有效，重命名也不行

Just delete all the *.pyc files in geo_map_cython_lib folder.

In this case it starts to give the error "libpython2.7.so.1.0: cannot open shared object file: No such file or directory"
Does it mean this repo works only for Python2 ?

I met the same problem. Have anyone solved it yet?

如果你删除了init_py遇到了上面的问题，可能是由于你没有在运行main.py前运行geo_map_cython_lib下的build_ext.sh脚本，你可能还需要安装cython。


How to use the heartbeat mechanism to determine whether to disconnect?

How to use the heartbeat mechanism to determine whether to disconnect?

Here is the relevant wiki page. In short, when your other endpoint doesn't respond in time, the connection will automatically be closed. You can change the timeout (or disable it) using setConnectionLostTimeout();. Default timeout is 60 seconds.

No additional feedback and reference to the wiki
Closing issue!
Best regards,
marci4


Use ProjectReactor in Axon's messaging APIs

ProjectReactor provides a very nice API towards reactive streams. Axon could benefit form using these API's.
Potential usage is in:

reading events from the event store
performing queries on the query bus

Hello.
I think providing a reactive API for EventStore, EventStorageEngine and so on... will be awesome !
It's the only thing that discouraged me choosing Axon for a stack on a new project with Spring Boot 2 relying only on non blocking IO .
Reactor is a good choice as Axon is already well integrated with Spring eco system.
I don't know if it is possible but relying only the spec (http://www.reactive-streams.org/ or JDK 9 Flow.Publisher) for new interfaces and providing some implementation using Reactor types could be an alternative . It would allow users to switch to an other reactive-stream implementation if they prefer (RxJava) and only add Reactor as an optional dependency.
I have not contribute on open source projects yet but I fond of event sourcing and reactive programming concepts. I would be very happy to help for this enhancement if needed.
Cheers,
For more

Hi @neoXfire,
thanks for you feedback. Relying on Reactive-Streams only would perhaps be a cleaner solution. However, the API it offers is rather "crude". Many of our users have asked us to be slightly more "opinionated" to make it easier to use the framework. It's a fine balance of opinion versus flexibility.
Thinking of it, one thing we could do is have the Event Bus use the spec in the API, while the QueryGateway offers a Reactor API (and perhaps another QueryGateway supports the RxJava API).
Why would the lack of a Reactive Streams based API stop you from looking at Axon. The APIs are already non-blocking in nature, where that makes sense. I admit there's room for improvement (hence this story), but I don't believe it should be a blocker in any way.
If you use Spring Boot and their reactive approach, it should be fairly easy to connect that to Axon's APIs, at the moment.
Thanks for your offer to help us. The best would be to fork the repository and make your suggested changes on your fork. You can then open a pull request, which we can then discuss. Usually, when it comes to API design (which can only be done between major releases, generally), there is a "risk" of discussion and many changes to be made along the way. We therefore recommend to open the PR early, while it's still work in progress. Early feedback prevents a lot of (re)work.
Cheers,
Allard


chore: Improve description of optional arguments in ExpectAPI.md

Summary
Fixes #8059
We fix the doc now, and then at next major version will make breaking change to throw new errors when toMatchSnapshot has unexpected combinations of arguments.
For example, if first argument is object, but second argument is not object. /cc @morungos

Append ? to optional arguments in headings.
Rewrite corresponding prose so optional always occurs.

For local test of website to make sure ? didn’t break links, I had to make corresponding changes to the versioned doc, but I forget if I needed to commit that change, or is it is automatic?

matcher
optional arguments

toBeCloseTo
numDigits

toHaveProperty
value

toMatchSnapshot
propertyMatchers and snapshotName

toMatchInlineSnapshot
propertyMatchers

toThrow
error

toThrowErrorMatchingSnapshot
snapshotName

Two existing link anchors changed where arguments were missing:

#tothrowerrormatchingsnapshot
#tothrowerrormatchinginlinesnapshot

Here are proposed sentences to help you review for clear meaning and consistent grammar:

The optional numDigits argument has default value 2 which means the criterion is Math.abs(expected - received) < 0.005 (that is, 10 ** -2 / 2).
You can provide an optional value argument to compare the received property value (recursively for all properties of object instances, also known as deep equality, like the toEqual matcher).
You can provide an optional propertyMatchers object argument, which has asymmetric matchers as values of a subset of expected properties, if the received value will be an object instance. It is like toMatchObject with flexible criteria for a subset of properties, followed by a snapshot test as exact criteria for the rest of the properties.
You can provide an optional snapshotName string argument for the snapshot key, in addition to the concatenated name arguments of containing blocks. Jest also appends 1, 2, 3, and so on to snapshot keys, in case an it or test block contains multiple snapshot assertions.
You can provide an optional argument to test that a specific error is thrown:

Residue: It’s hard to say if inlineSnapshot argument is optional or required. The tester (usually) doesn’t write it, but Jest does provide it when assertion passes the first time.
Test plan
yarn lint:md passed

Yes, thank you. What do you think of this rewrite?
You can provide an optional snapshotName string argument for the snapshot key. It follows the concatenated name arguments of containing blocks and precedes the final number (that Jest appends in case an it or test block contains multiple snapshot assertions).

Codecov Report

Merging #8126 into master will decrease coverage by <.01%.
The diff coverage is n/a.

@@            Coverage Diff             @@
##           master    #8126      +/-   ##
==========================================
- Coverage   62.43%   62.42%   -0.01%
==========================================
  Files         264      264
  Lines       10368    10368
  Branches     2515     2515
==========================================
- Hits         6473     6472       -1
  Misses       3318     3318
- Partials      577      578       +1

Impacted Files
Coverage Δ

packages/jest-core/src/SearchSource.ts
56.84% <0%> (-1.06%)
:arrow_down:

Continue to review full report at Codecov.

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

It’s hard to say if inlineSnapshot argument is optional or required.

IMO it's optional. The matcher won't throw an error if it's not there (just like toMatchSnapshot() won't throw if a snapshot file is not there), so it was a valid call, one that causes Jest to write the snapshot by modifying that call in the test file.


Fix drawing boxselection on GraphEdit

Box selection is drawn with previous area at mouse press when one or more GraphNode is connected.

By looking at this PR,I noticed a typo in line 1316."previus_selected" instead of "previous_selected".

@AnilBK nice catch. I made another commit for it.

I can't reproduce the issue.

here is my full reproduction step.

tested official rc6 from https://downloads.tuxfamily.org/godotengine/3.3/rc6/

@KoBeWi Can't you reproduce it? I have this issue with master and 3.x both.

Yeah I can reproduce. I was a bit busy and forgot to reply, sorry.

Thanks for the confirmation.

Thanks!

Cherry-picked for 3.3.


Support optional 2nd Argument

Fixed #6

Coverage remained the same at 100.0% when pulling 5fd34d793e4c02f5361832ca73b04ce608630f7e on undefined-2nd into 5600babc5f35cae56c4d7d28f428ad4334a0886b on master.


Using DirectML from C#

I know I could PInvoke the nuget package but how will I create a console app which uses DirectML and also will I be able to use a ML.NET with DirectML. Samples for this would be appreciated (or a gist).
P.S: I am a beginner in ML.NET

This isn't something we support at the moment. It's possible, but you'd have to write your own bindings or wrapper/abstraction around DirectML. Additionally, DirectML in total isolation isn't particularly useful since you need Direct3D 12 for allocating resources and submitting work.
DirectML & D3D12 are both low-level "nano-COM" style APIs that don't have out-of-the-box language projections like WinRT APIs. There are other higher-level APIs like Windows ML & ONNX Runtime that layer on top of DML & D3D, but if you want to program directly against DML/D3D you need to drop down to C++.
The most viable approach is to probably to write a higher-level library in C++ that handles allocation and submission, then create bindings to use that library in the language of your choice; this is how the PyDirectML  bindings work.

hmm...... any idea when it will be supported ? or is it possible to just convert PyDirectML to into C#

Have you looked at https://github.com/Microsoft/xlang?
We would love to know how DirectML API can be projected in other language through xlang. We're open to contribution if you want to have a run with it.
PyDirectML is done manually and is specific to Python only today.

I've implemented DirectML bindings through https://github.com/amerkoleci/Vortice.Windows/tree/main/src/Vortice.DirectML with the HelloDirectML example as well. The example works and everything is technically implemented, but I'll be refining the API. Expect it to stabilize over the next few weeks. Give it a try, LMK if there are any issues.
The nuget package is here: https://www.nuget.org/packages/Vortice.DirectML/2.1.10-beta
You can see sample code here: https://github.com/amerkoleci/Vortice.Windows/blob/main/src/samples/HelloDirectML/DmlDevice.cs

DirectML & D3D12 are both low-level "nano-COM" style APIs that don't have out-of-the-box language projections like WinRT APIs. There are other higher-level APIs like Windows ML & ONNX Runtime that layer on top of DML & D3D, but if you want to program directly against DML/D3D you need to drop down to C++.

@jstoecker -- is Windows ML a different Runtime / API than Direct ML? -- Boy that's confusing.  Does it have a .NET API?
At the end of the day, as a Windows App developer who abandoned C++ nearly 20 years ago, in favor of Microsoft's C#, I need guidance on how best to continue to do that with officially supported libraries and runtimes.
If Direct ML isn't Windows ML, it would be nice if the main page called that out, and gave us links of where Windows App developers should go to find this stuff, because it's not easily searchable or discoverable.  And the MS Learn pages for the Windows Machine Learning Runtime sent me here. -- And even searching for Windows.AI.MachineLearning (as opposed to Microsoft.AI.MachineLearning) just links back to this page.  So... any guidance on resources for this stuff would be really helpful.

DirectML is distinctly DirectML and not anything that is not named DirectML. You can learn about it in Microsoft documentation at https://learn.microsoft.com/en-us/windows/ai/directml/dml. It's a low level API that works with the DirectX 12 environment. Other Microsoft frameworks may use DirectML underneath but this project is not related to those higher level libraries. High level Microsoft libraries likely utilize the C++ api to leverage DirectML and DirectX and not this library.
Can you share what pages link to this project? Are they official documentation or search queries?


Is there a plan to add dotnet interactive into kaggle notebook

Hi Kaggle
Jupyter notebook has already support C# through dotnet interactive, here's a sample

https://mybinder.org/v2/gh/dotnet/interactive/main?urlpath=lab

Just wondering if kaggle notebook supports that too

Hi,
We don't support C# and have no plans currently to expand to languages beyond Python and R.
Julia is also not supported anymore on Kaggle notebooks.
Thank you


BugFix to dev branch

In terms of workflow, let's merge master into dev after we have merged bugfix PRs.

Some internal bug in the deploy docs. Should be fine from my perspective.


x/tools v0.27.0 breaks gomock

What version of rules_go are you using?
0.50.1
What version of gazelle are you using?
0.38.0
What version of Bazel are you using?
7.4.0
Does this issue reproduce with the latest releases of all the above?
Yes.
What operating system and processor architecture are you using?
Linux amd64
What did you do?
Upgrade x/tools to v0.27.0 in my own repository, and tried to run go tests that rely on gomock from rules_go.
What did you expect to see?
It should have worked as it did in previous versions of x/tools.
What did you see instead?
It fails with 2024/11/12 21:28:26 Failed to format generated source code: err: go command required, not found: exec: "go": executable file not found in $PATH.
I narrowed it down to this commit https://github.com/golang/tools/commit/cceaf96b2526ff522217c68731a2bd9ef176ab80

@linzhp


Document how staging environment is used

Summary
Data processing software will need to be fully tested in the staging environment prior to being integrated into the SDC production processing environment. The staging environment replicates that of production, but operates independently in order to not interfere with daily production. This process for how the staging environment will be used should be documented.
Parent Requirement

SOC-SDC-L4-27
SDC Staging Environment
The SDC shall provide a staging environment for developer testing of L1, L2, L3, and i-ALiRT software prior to release to production.
Requirement
Data processing software will need to be fully tested in the staging environment prior to being integrated into the SDC production processing environment. The staging environment replicates that of production, but operates independently in order to not interfere with daily production.
SOC-L3-57
Demonstration

Documentation for setting up and deploying the staging environment was done here: https://sds-data-manager.readthedocs.io/en/latest/cdk/index.html


Is there any way to retrieve historical data from each dashboard?

⚠ Please verify that this bug has NOT been raised before.

[X] I checked and didn't find similar issue

🛡 Security Policy

[X] I agree to have read this project Security Policy

📝 Describe your problem
I need to retrieve historical data from each dashboard in text plane or json format. Can you tell me how to do it?

📝 Error Message(s) or Log
No response
🐻 Uptime-Kuma Version
1.23.1
💻 Operating System and Arch
Kubernetes
🌐 Browser
Google Chrome
🐋 Docker Version
louislam/uptime-kuma:1.23.1
🟩 NodeJS Version
No response

Currently, such a functionality does not exist.
For the moment, you can use external (unofficial) tools like https://uptime-kuma-api.readthedocs.io/en/latest/ to export data or directly access the database.
If you'd like to add address this feature, here is our contributing guide: https://github.com/louislam/uptime-kuma/blob/master/CONTRIBUTING.md
I think this is a duplicate of https://github.com/louislam/uptime-kuma/issues/1093 (and its duplicates like https://github.com/louislam/uptime-kuma/issues/1101)
If you agree, could you please close this Issue, as duplicates only create immortal zombies and are really hard to issue-manage?
If not, what makes this issue unique enough to require an additional issue? (Could this be integrated into the issue linked above?) ^^


Clean up and abstract github pipelines

Issue description / feature objectives
The current setup of compliance trestle's github pipelines are robust, however, have been aging:
Brittleness and risk of errors

Python versions are defined in multiple places
Elements of the pipelines are (probably) necessarily replicated.
Some areas particularly release management (see #1571) are tightly coupled making the pipeline brittle.

General updates

The pipeline versions have not been updated recently (note the dependabot configuration should be updated to ensure that prompt alerts are configured)

Efficiency

Caching is now inconsistently applied. This leads to long build times particularly for windows where the runners are slower.
The pipelines are a bit bulky. There are two recommendations:

Currently three versions of python are testedL A lower bound, a mid version and an upper bound. Recommend that it's slimmed down to a minimum and maximum.
Remove or slim actions run on push to develop (which is unnecessary as the pipeline insists the code is up to date before merging so exactly the same)

Caveats / Assumptions

Fundamental tech in the supply chain don't change

Completion Criteria

This would include #1559

Hi @butler54 While issue triage today we were just wondering if this close is done or is there more pending work to do? I've seen the abstract python version in pipelines PR to be closed but not sure if that covers all the items in here. Assuming no, but just wanted to confirm. Thanks.

@AleJo2995 sorry I think there is still something to do. i'll do a little work on it.


Add warning about using CLI tool with APC(u) cache

Because this happens and the APC(u) documentation does not help matters.
This PR really isn't enough to sufficiently document the "gotchas" when using APC(u) cache but hopefully it gets the conversation started.

You link to a tweet saying:

Today I learned that you cannot flush the #Doctrine metadata cache from the CLI when using #APCu cache. Totally not obvious anywhere in the APCu or Doctrine documentation. #FML

So "you cannot"… can you please describe a bit more what happens exactly?

@greg0ire the APC(u) cache exists in memory shared owned by a single PHP process. In my case, that process is owned by Apache. Running vendor/bin/doctrine orm:clear-cache:metadata does not error but it will not clear the cache that Apache uses.

Thanks for the explanation, do you get an exception, or some CLI warning?

@greg0ire no, there is no warning because the APC(u) cache is initialized, assuming that apcu.enable-cli is active, but it contains no data. Doctrine CLI tool doesn't give any warning about this because it assumes there are no cache entries.

Makes sense, technically people could be willing to use a separate APCu cache just for the CLI, and should not get any error when trying to clear it. Note that the doc you linked says that having it enabled is not very likely though:

Mostly for testing and debugging. Setting this enables APC for the CLI version of PHP. Under normal circumstances, it is not ideal to create, populate and destroy the APC cache on every CLI request, but for various test scenarios it is useful to be able to enable APC for the CLI version of PHP easily.

@greg0ire right, my PR does not really reflect the complicated nature of what is happening. The APC(u) cache works just fine for CLI and for Apache/PHP-FPM, but the cache is not shared. This is the point that I want to see reflected in the documentation.
The language in this PR definitely needs to be updated, I am just not sure what the best way to explain this is.

It could be nice to produce a warning to users that are trying to clear an APCu cache from the cli and have apcu.enable_cli set to "0"?
Regarding your message how about:

It is not possible to clear the APCu cache of the webserver from the CLI context. The following commands will not work as intended and will clear a separate, empty cache that is owned by the PHP CLI process, provided apcu.enable_cli is set to 1, which it probably shouldn't

with a nice link to the php docs.

Perhaps the documentation should be updated to use PhpFileCache instead of APCu for metadata? At least then vendor/bin/doctrine orm:clear-cache:metadata would work correctly.
That doesn't solve the overall problem of clearly documenting that APC(u) cache is not shared between CLI and webserver.

There have been similar attempts on the sf docs, and they were reverted so that the docs stay compatible with read-only filesystems, which are getting traction.

The problem is exacerbated by the fact that http://php.net/apcu says absolutely nothing about how APCu works with regard to visibility of cache between different PHP processes. Obviously that cannot be solved by Doctrine, but I think it is worth mentioning because linking to the PHP docs won't help people understand the root of the issue.

There have been similar attempts on the sf docs, and they were reverted so that the docs stay compatible with read-only filesystems, which are getting traction.

I understand that point, but the current documentation defaults imply that using the command line tools to manage cache will work as expected with APCu and that simply isn't true.

This is (somewhat) related to symfony/symfony#24545

linking to the PHP docs won't help people understand the root of the issue.

Ok so let's insist even more then:

Because APCu caches are stored in a memory segment owned by a php process and not shared with other php processes, it is not possible to clear the APCu cache of the webserver from the CLI context. The following commands will not work as intended and will clear a separate APCu cache that is owned by the PHP CLI process, provided apcu.enable_cli is set to 1, which it probably shouldn't.

@greg0ire that makes sense. Do I need to make separate PRs to target older versions of documentation?

Sorry, I'm a bit new to reviewing on that repository. From my understanding, you should create one PR, and (I'm less sure here), target the stable branch (so 2.6 ?), see https://github.com/doctrine/doctrine2/blob/master/CONTRIBUTING.md#choosing-the-branch

@greg0ire updated target and applied your wording.

@Ocramius

this should be a warning on the CLI command itself

Do you mean that doctrine orm:cache* commands should have a warning when using the APCu driver?

We shouldn't explain users how their caching backend works, since they installed it and should (hopefully) have read how it works.

As I mentioned above, there is zero mention of how memory sharing works in http://php.net/apcu. I understand your position but surely there is a duty to make it obvious to users that doctrine tool won't work as expected with APCu cache?

I would rather warn users about their use of the APCu backend, and steer them to the more efficient PhpFileCache.

Does this mean that it would be better for the documentation to suggest PhpFileCache as the default cache implementation, as I suggested above?

this should be a warning on the CLI command itself

Do you mean that doctrine orm:cache* commands should have a warning when using the APCu driver?

Yes

We shouldn't explain users how their caching backend works, since they installed it and should (hopefully) have read how it works.

As I mentioned above, there is zero mention of how memory sharing works in the http://php.net/apcu documentation. I understand your position but surely there is a duty to make it obvious to users that doctrine tool won't work as expected with APCu cache?

This is a SEP (Someone Else's Problem). The fact that upstream docs are lacking in content doesn't mean that anything downstream should fill the gap. The analogy would be to find a MySQL documentation issue, and reporting it here: not OK.

I would rather warn users about their use of the APCu backend, and steer them to the more efficient PhpFileCache.

Does this mean that it would be better for the documentation to suggest PhpFileCache as the default cache implementation, as I suggested above?

Yup 👌

@Ocramius thank you for the clarification. I will work on two separate pull requests:

Add a warning to doctrine tool when using the APC(u) driver.
Update ORM cache documentation to use PhpFileCache in examples.

Should both of these PRs should target 2.6 branch?

Yeah, you can target 2.6 👍
On Thu, 29 Nov 2018, 22:16 Woody Gilk<EMAIL_ADDRESS>wrote:

@Ocramius https://github.com/Ocramius thank you for the clarification.
I will work on two separate pull requests:

Add a warning to doctrine tool when using the APC(u) driver.
Update ORM cache documentation to use PhpFileCache in examples.

Should both of these PRs should target 2.6 branch?
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
https://github.com/doctrine/doctrine2/pull/7493#issuecomment-442995966,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAJakCnO52o05mCxiAiAJe6AJC4qhLsSks5u0E6ggaJpZM4Y6MBS
.

Could really not care less about the symfony defaults: whole different project again, and we can't let scopes leak constantly.

I was just giving out reasons (namely ro filesystems getting traction) why APCu might still be the default, but yeah, we don't have to be consistent with Symfony at all, of course.

@greg0ire your point is valid. When working with RO filesystems, it would be possible to generate the metadata cache as part of the build process and upload the cached metadata to the RO filesystem. For most use cases, I think that @Ocramius is right about using PhpFileCache as the default. Opcode caching is so fast in PHP 7+ that it probably outperforms APCu.

Replaced by #7494 and #7500.


Still working on Big Sur as of May 2021

Feel free to close this but actually the description or readme should atleast be updated to state that it still works as of late, with the age of the last commit I thought this might be out of commission.
Thankfully looking into the issues someone did say it was still working for them in 2019/2020

That's a good idea, I will update it now. Also, I use this tool essentially everyday (not yet on Big Sur though), so if Apple changes/removes the API someday I will try to get it back working.


[WIP] Track element instances in running application

Description
Allows invalidation of a subset of the widget tree, when provided with file/line/column information. Currently registered in the WidgetInspector extensions due to the visibility constraints on _Location. Probably doesn't quite work yet
cc @jacob314

Took another pass on this based on the double linked list approach. If we use expandos that are kept in the widget inspector class, then we don't need to add any fields to Element

I'm going to leave this as a draft (or close it) for the short/medium term and pursue the approach of walking the entire element tree. Then I'll be able to say more easily whether this is a performance improvement, once we account for the edge cases

I'm going to close this one for now (for above reasons) to remove from PR queue


Drop-down menu added for date format selection

Drop-down menu added for date format selection in app.py and support for the drop-down menu added in func_use_extract_data.py

Awesome 😃 . Soon I will deploy it.


fix: Repos with long names get cut off

Description
Truncating repo names using css instead of javascript.

fixes #1750
What type of PR is this? (check all applicable)

[ ] 🍕 Feature
[x] 🐛 Bug Fix
[ ] 📝 Documentation Update
[ ] 🎨 Style
[ ] 🧑💻 Code Refactor
[ ] 🔥 Performance Improvements
[ ] ✅ Test
[ ] 🤖 Build
[ ] 🔁 CI
[ ] 📦 Chore (Release)
[ ] ⏩ Revert

Related Tickets & Documents

Mobile & Desktop Screenshots/Recordings

Added tests?

[ ] 👍 yes
[x] 🙅 no, because they aren't needed
[ ] 🙋 no, because I need help

Added to documentation?

[ ] 📜 README.md
[ ] 📓 docs.opensauced.pizza
[ ] 🍕 dev.to/opensauced
[ ] 📕 storybook
[x] 🙅 no documentation needed

[optional] Are there any post-deployment tasks we need to perform?
[optional] What gif best describes this PR or how it makes you feel?

Thanks for the PR @aryanas159. Can you add a before and after screenshot of with a repository with a long name? You can always change the text manually in the component to a long name to demonstrate the fix if you don't have a repository with a long name.
Thanks!

Thanks for the PR @aryanas159. Can you add a before and after screenshot of with a repository with a long name? You can always change the text manually in the component to a long name to demonstrate the fix if you don't have a repository with a long name.
Thanks!

@nickytonline  I have added the before and after screenshots.


[WIP] debug CI random issue : StandardPartitionGlobalSortTestCase

Added more logs to debug StandardPartitionGlobalSortTestCase.concurrent global sort partition table load test.
Be sure to do all of the following checklist to help us incorporate
your contribution quickly and easily:

[ ] Any interfaces changed?

[ ] Any backward compatibility impacted?

[ ] Document update required?

[ ] Testing done
Please provide details on
- Whether new unit test cases have been added or why no new tests are required?
- How it is tested? Please attach test report.
- Is it a performance related change? Please attach the performance test report.
- Any additional information to help reviewers in testing this change.

[ ] For large changes, please consider breaking it into sub-tasks under an umbrella JIRA.

SDV Build Success , Please check CI http://<IP_ADDRESS>:8080/job/ApacheSDVTests/6248/

retest this please

Build Success with Spark 2.1.0, Please check CI http://<IP_ADDRESS>:8080/job/ApacheCarbonPRBuilder1/7889/


Fails to install on npm 5

The engines field in package.json is currently specifying "npm": "^3.0.0", which causes installation to fail on npm 4 and 5.

This isn't a great solution, but while trying to install @storybook/react which depends on podda, I set engine-strict=false in my .npmrc. https://docs.npmjs.com/misc/config#engine-strict


fix PVC path in storage doc

Found a small error with the PVC path and ended up fixing a few nits.

Thanks!


Some codes are written twice in brew and brew.sh

Mostly codes for checking enviroment.
One of them is "Homebrew must need current working directory exist"
may be one of the reasons why eveytime I run brew it wait few seconds and then run.

Please note we will close your issue without comment if you do not correctly fill out the issue checklist below and provide ALL the requested information. If you repeatedly fail to use the issue template, we will block you from ever submitting issues to Homebrew again.


AnimationFactory being deprecated

Hey, I'm currently working on my own mod. I'm making a monster entity but for some reason every time I've tried to write this line of code:
private final AnimationFactory factory = new AnimationFactory(this);
I have had an error message come up,
'AnimationFactory(software.bernie.geckolib3.core.IAnimatable)' is deprecated and marked for removal
There is a red strike through the second AnimationFactory, I have absolutely no idea what to do or what I'm doing wrong.
I am still learning java and have a basic understanding so if my issue is partly to do with that then I apologize.
VERSION: 1.19:3.1.38
Link to my Git Repository: https://github.com/OllyHolcombe/MageCraft

Look at the example entities or wiki.


Add course info on click

When you click on a course, the info for the course is displayed. For now it just displays the raw json cuz y not 🤷♂ .
I also did some refactoring.
Test: http://<IP_ADDRESS>/courseplannerd/

Related to #45


fix(@nestia/fetcher): incorrect overloading of fetcher functions

fix #246

Will study about this issue at this Sunday. Sorry for waiting for a long time.


ActorContext in CommandContext

This PR brings ActorContext into CommandContext.
ActorContext now belongs to the base package.
Other changes:

CommandEnvelope was extended for obtaining TenantId.
The short link for FieldMask specs are used in Javadocs.

@armiol, PTAL.


[#3149] feat(catalog-lakehouse-iceberg): Support Iceberg RestCatalog in Gravitino

What changes were proposed in this pull request?
Add Iceberg RestCatalog backend in Gravitino
Why are the changes needed?
As discussed in https://github.com/datastrato/gravitino/issues/2716, we should support Iceberg RESTCatalog in Gravitino, and after supporting this, we can use RESTCatalog in spark-connector.
Fix: https://github.com/datastrato/gravitino/issues/3149
Does this PR introduce any user-facing change?
No
How was this patch tested?
New UTs and ITs.
And tested locally.

Hi @FANNG1 could you help review this PR? Thank you.

LGTM except few comments

LGTM except few comments

all comments have been addressed.

@FANNG1 all comments have been addressed.

LGTM, @caican00 could you add the document in docs/iceberg-rest-service.md?

LGTM, @caican00 could you add the document in docs/iceberg-rest-service.md?

seems to be no related to IcebergRestService? because we do not support a rest service as backend storage yet.
this simply adds RestCatalog backend to the Gravitino Server.

LGTM, @caican00 could you add the document in docs/iceberg-rest-service.md?

@FANNG1 seems no related to IcebergRestService? because we do not support a rest service as backend storage yet. this pr only adds RestCatalog backend to the Gravitino Server.

sorry for mistake, it should be docs/lakehouse-iceberg-catalog.md

LGTM, @caican00 could you add the document in docs/iceberg-rest-service.md?

@FANNG1 seems no related to IcebergRestService? because we do not support a rest service as backend storage yet. this pr only adds RestCatalog backend to the Gravitino Server.

sorry for mistake, it should be docs/lakehouse-iceberg-catalog.md

@FANNG1 Sorry for the late reply, i have updated the document.

@FANNG1 could you help review this again? Thank you.

LGTM

@caican00 could you propose a new PR based on branch-0.5?

@caican00 could you propose a new PR based on branch-0.5?

Sorry for the late reply, and i have created a new pr for this commit to branch-0.5


Add new design and text to hotels 'see more'

Updates per design input. Also addresses mobile and tablet view positioning


Update Please!

Can you please update the Falcon Badge and add more information and codes?
Its a little hard to understand as it is.
So please elaborate and add all information and uses. Also add the writeups.

Check the b31fe42 commit and the OTA branch for more info. Feel free to ask questions, if still confused.


Roi msgs

Use sensor_msgs/RegionOfInterest for ROI (fixes #5)
Solves this issue related to pyhri apparently being the only package in the ROS4HRI framework using hri_msgs/NormalizedRegionOfInterest2D instead of sensor_msgs/RegionOfInterest.
With respect to simply undoing commit https://github.com/ros4hri/pyhri/commit/be95f6a9ed7caf397f532a3d713496451047266e, in face.py it also switches from hri_msgs/NormalizedPointOfInterest2D to sensor_msgs/RegionOfInterest to represent face ROI.
Solve AttributeError on first detection
Due to _hrilistener = None in __init__ of person.py, at the first call to one of the on_<x>_id callbacks, the following error was thrown:
[ERROR] [1679581959.014495]: bad callback: <bound method Person.on_face_id of <hri.person.Person object at 0x7f1f2f63b520>>
Traceback (most recent call last):
  File "/opt/ros/noetic/lib/python3/dist-packages/rospy/topics.py", line 750, in _invoke_callback
    cb(msg)
  File "/home/luca/hri_ws/src/pyhri/src/hri/person.py", line 138, in on_face_id
    if msg.data and msg.data in self._hrilistener._faces:
AttributeError: 'NoneType' object has no attribute '_faces'

due to the _hrilistener attribute being not set by hri.py yet. The error do not cause any major issues, as everything work just smoothly from the second detection on.
It has been fixed by adding a and self._hrilistener is not None check in each on_<x>_id callbacks.

Thanks! can you squash commits 16ccf9c3816d0c895b94f534fb71def4c562f965 and be03f62dd5c139d29e457aad0198e3cbf5cc2278 before I merge, please?

Hi @severin-lemaignan!
Sorry for bothering, I squashed the commits (correctly, I hope) last week. Is there anything else I should do?

thanks! merged!

I've released pyhri-0.4.0 with those changes, that should be soon merged in noetic: https://github.com/ros/rosdistro/pull/36812


OAuth2 authentication expires and causes app to crash

Need to track this down

Fixed the crash, but still need to fix the issue. Caught the exception


Querying the same value against multiple fields

I may be missing it in the docs, but is there an easy way to use escape to query the same value against multiple fields without having to repeat it multiple times in the array?
For instance
var myDate = new Date();
connection.query('SELECT * FROM users WHERE date_1 >= ? AND date_2 <= ?', [myDate, myDate], function(err, results) {
  // ...
});

(I have a query where I am using the same date against 8 date fields)

Because ? is a positional replacement, there is no other way to do it using that replacement style.


TypeScript compiler stucks with --incremental flag

TypeScript Version:  3.4.5

Search Terms:
stuck, slow, incremental
Code
https://github.com/ms-qinyang/typescript-stuck-incremental
run npm run buildIncremental
PS D:\stuck-with-incremental> Measure-Command { npm run build | Out-Host }

><EMAIL_ADDRESS>build D:\stuck-with-incremental
> tsc -p .

Days              : 0
Hours             : 0
Minutes           : 0
Seconds           : 1
Milliseconds      : 890
Ticks             : 18903973
TotalDays         : 2.18795983796296E-05
TotalHours        : 0.000525110361111111
TotalMinutes      : 0.0315066216666667
TotalSeconds      : 1.8903973
TotalMilliseconds : 1890.3973

PS D:\stuck-with-incremental> Measure-Command { npm run buildIncremental | Out-Host }

><EMAIL_ADDRESS>buildIncremental D:\stuck-with-incremental
> tsc -p ./tsconfig-incremental.json

Days              : 0
Hours             : 0
Minutes           : 1
Seconds           : 3
Milliseconds      : 989
Ticks             : 639891999
TotalDays         : 0.000740615739583333
TotalHours        : 0.01777477775
TotalMinutes      : 1.066486665
TotalSeconds      : 63.9891999
TotalMilliseconds : 63989.1999

Expected behavior:
Compiler should be finished in a short time
Actual behavior:
Compiler takes more than 1 minute to finish. Since the real project has many files, the compiler won't be finished in an acceptable time. This breaks typecheck in create-react-app after 2.1.8
Related Issues:

This seems to be stuck in declaration emit.

One of the declaration files we produce is 209163 lines long. (specifically the output for createModel2) 150,000 of those lines are spent repeating the anonymous type
type repeated = {
    type: TConfigs[number]["type"];
    str1: string;
    str2: string;
}

and the rest are spent nesting a bunch of redux-advanced types, specifically, specifying the type arguments for SelectorContext. I would say that normally what we'd like to do here is preserve aliases better (mapped types, especially), but with all the fluent mapping and building going on in redux-advanced, I'd be surprised if there's anything approaching a short way to refer to any of this - all throughout the createModel2 definition, there's truncation in the quickinfo, just because all of the types for everything are so complex - the very first chained method call returns a ModelBuilder<TDependencies, TProps, TState extends object ? TState & T : T, TSelectors, TReducers, TEffects, TEpics>; which has it's infered argument type inserted, and those result is truncated in quickinfo because it's just too much. Then that's flowed into every subsequent call which layers on more and more stuff. There is simply not a short name for this stuff - it's a grand amalgam, a great composition, of no fewer than 10 inferred types which are combined and composed in numerous ways.
Our canonical response in cases like these, thus far, is to recommend adding a type annotation to the offending declaration, so we can avoid the generation process entirely.
Now, while I said that I don't think all of the complexity in the printback can be avoided, I think #30979 or something like it (specifically the let ... in style variant) could help quite a bit - then we'd be able to hoist all these common anonymous types to the outermost area wherein they were valid and avoid repeating them so much.

TL;DR: There's no simple "fix" here because nothing is going "wrong" - our declaration emit just just less expressive than the input code, and it shows in the complexity of the output. At least the work around is pretty easy to do: add a type annotation on your function returns (which, given that a builder pattern is in use, probably isn't what anyone wants to hear, as it kills an advantage to the strongly typed builder, but it's what we have right now).

Our canonical response in cases like these, thus far, is to recommend adding a type annotation to the offending declaration, so we can avoid the generation process entirely.

This. I've been burned by it too many times that I've basically requested a lint rule be written for it,
https://github.com/typescript-eslint/typescript-eslint/issues/730
When it comes to generic functions/methods, always err on the side of caution and explicitly annotate the return type.
If you're composing them, this rule goes triple.
You'll save yourself a lot of declaration emit headaches

Thanks for the investigation. However, the reason we use this library is that we don't want to write unnecessary type definitions explicitly. Since it works well without incremental flag, we will override CRA configuration to avoid this issue.

It's probably also worth noting that your config had both incremental an noEmit on, which just... Does extra work for no gain. That it's not an error is an oversight on or part right now. You at least need to emit declaration files and the incremental bundle info.


Add placeholder selectors to utility classes

[ ] Dimension
[ ] Layout
[ ] Spacing
[ ] Text
[x] Visibility

@avelinet @jeffkamo I thought this was done… is that true?

Yep, all utilities have been given placeholder selectors.


Install failed on windows 10

I got this issue while installing.
Installing<EMAIL_ADDRESS>failed.Hide output…
npm ERR! Windows_NT 10.0.14393
npm ERR! argv "C:\Users\Yaswanth\AppData\Local\atom\app-1.13.1\resources\app\apm\bin\node.exe" "C:\Users\Yaswanth\AppData\Local\atom\app-1.13.1\resources\app\apm\node_modules\npm\bin\npm-cli.js" "--globalconfig" "C:\Users\Yaswanth\.atom\.apm\.apmrc" "--userconfig" "C:\Users\Yaswanth\.atom\.apmrc" "install" "C:\Users\Yaswanth\AppData\Local\Temp\d-117031-14892-jk0r\package.tgz" "--runtime=electron" "--target=1.3.13" "--arch=ia32" "--global-style"
npm ERR! node v4.4.5
npm ERR! npm  v3.10.5
npm ERR! code EAI_AGAIN
npm ERR! errno EAI_AGAIN
npm ERR! syscall getaddrinfo
npm ERR! getaddrinfo EAI_AGAIN registry.npmjs.org:443
npm ERR!
npm ERR! If you need help, you may report this error at:
npm ERR!     https://github.com/npm/npm/issues
npm ERR! Please include the following file with any support request:
npm ERR!     C:\Users\Yaswanth\AppData\Local\Temp\apm-install-dir-117031-14892-1afavj8\npm-debug.log
operation_log.txt

This is a DNS error from the npm registry: "EAI_AGAIN actually means a temporary failure in name resolution or simply the name server returned a temporary failure indication. It will ask you to try again later."
Try to re-install.


Add OASA Telematics greek public transport sensor component

Description:
Pull request in home-assistant.io with documentation (if applicable): https://github.com/home-assistant/home-assistant.io/pull/8836
Example entry for configuration.yaml (if applicable):
sensor:
  - platform: oasa_telematics
    route_id: '090006'
    stop_id: '1965'

Checklist:

[X] The code change is tested and works locally.
[X] Local tests pass with tox. Your PR cannot be merged unless tests pass
[X] There is no commented out code in this PR.

If user exposed functionality or configuration variables are added/changed:

[X] Documentation added/updated in home-assistant.io

If the code communicates with devices, web services, or third-party tools:

[X] New dependencies have been added to the REQUIREMENTS variable ([example][ex-requir]).
[X] New dependencies are only imported inside functions that use them ([example][ex-import]).
[X] New or updated dependencies have been added to requirements_all.txt by running script/gen_requirements_all.py.
[X] New files were added to .coveragerc.

If the code does not interact with devices:

[ ] Tests have been added to verify that the new code works.

Hello @panosmz,
When attempting to inspect the commits of your pull request for CLA signature status among all authors we encountered commit(s) which were not linked to a GitHub account, thus not allowing us to determine their status(es).
The commits that are missing a linked GitHub account are the following:

8d28bb94827ca1bf9127cf632b5206f7ac51ce88 - This commit has something that looks like an email address (panosmz@outlook.com). Maybe try linking that to GitHub?.

Unfortunately, we are unable to accept this pull request until this situation is corrected.
Here are your options:

If you had an email address set for the commit that simply wasn't linked to your GitHub account you can link that email now and it will retroactively apply to your commits. The simplest way to do this is to click the link to one of the above commits and look for a blue question mark in a blue circle in the top left. Hovering over that bubble will show you what email address you used. Clicking on that button will take you to your email address settings on GitHub. Just add the email address on that page and you're all set. GitHub has more information about this option in their help center.

If you didn't use an email address at all, it was an invalid email, or it's one you can't link to your GitHub, you will need to change the authorship information of the commit and your global Git settings so this doesn't happen again going forward. GitHub provides some great instructions on how to change your authorship information in their help center.

If you only made a single commit you should be able to rungit commit --amend --author="Author Name<EMAIL_ADDRESS>
(substituting Author Name and<EMAIL_ADDRESS>for your actual information) to set the authorship information.
If you made more than one commit and the commit with the missing authorship information is not the most recent one you have two options:

You can re-create all commits missing authorship information. This is going to be the easiest solution for developers that aren't extremely confident in their Git and command line skills.
You can use this script that GitHub provides to rewrite history. Please note: this should be used only if you are very confident in your abilities and understand its impacts.

Whichever method you choose, I will come by to re-check the pull request once you push the fixes to this branch.

We apologize for this inconvenience, especially since it usually bites new contributors to Home Assistant. We hope you understand the need for us to protect ourselves and the great community we all have built legally. The best thing to come out of this is that you only need to fix this once and it benefits the entire Home Assistant and GitHub community.
Thanks, I look forward to checking this PR again soon! :heart:

I added the missing email address. Cla-error should be fixed.

@homeassistant cla-error should be resolved

This is a PR gone wrong, locking it as such.

Oh yeah @panosmz feel free to submit a new clean PR obviously.


Add explanation and use cases to readme

Language server
No response
Requested feature
I have no idea what the thing does or why I should use it.
Other clients which have this feature
No response

First line of the readme says:

Configs for the Nvim LSP client (:help lsp).

We can expand on it:

nvim-lspconfig is a collection of configurations for use with the Nvim builtin LSP client, to save you the trouble of manually creating such configurations. For example to use Nvim LSP with a typescript project, you would need to

install the typescript language server
in your init.lua (or init.vim) configure it like this: https://github.com/neovim/nvim-lspconfig/blob/80fddd28de5fe0642da7adee955f5762b933e730/lua/lspconfig/server_configurations/tsserver.lua#L3-L26

With nvim-lspconfig, you only need to:

install the typescript language server
in your init.lua (or init.vim) call require'lspconfig'.tsserver.setup{}

Is that clear?

Need to add the above changes to the readme before closing this.

closed because Readme has been updated.


Multiple generation of UnitOfAttribute.cs

I use UnitOf in a class library L.
This class library is referenced in another project A.
Project A contains other source generators (not sure if it is relevant or not).
When building the solution, the UnitOfAttributes is added in the class library L AND in Project A (while the UnitGenerator is only referenced in the class library L).
This yields an exception:
xxx\UnitGenerator\UnitGenerator.SourceGenerator\UnitOfAttribute.cs(11,20,11,35): error CS0101: The namespace 'UnitGenerator' already contains a definition for 'UnitOfAttribute'
xxx\UnitGenerator\UnitGenerator.SourceGenerator\UnitOfAttribute.cs(26,19,26,38): error CS0101: The namespace 'UnitGenerator' already contains a definition for 'UnitGenerateOptions'
xxx\UnitGenerator\UnitGenerator.SourceGenerator\UnitOfAttribute.cs(10,6,10,20): error CS0579: Duplicate 'AttributeUsage' attribute
xxx\UnitGenerator\UnitGenerator.SourceGenerator\UnitOfAttribute.cs(17,16,17,31): error CS0111: Type 'UnitOfAttribute' already defines a member called 'UnitOfAttribute' with the same parameter types

A possible fix would be to skip the generation if the class is already found:
var isAlreadyGenerated = context.Compilation.GetTypeByMetadataName($"UnitGenerator.UnitOfAttribute");

I'm not really sure why this class attribute (UnitOfAttribute) is generated and not directly included within the UnitGenerator lib.
Regards,
Adrien.

GeneratorPostInitializationContext has no Compilation so can not check it.
All generated UnitOfAttribute is internal type so will not conflict I think.

The namespace used in the generated file is namespace UnitGenerator. So even if this is internal it would conflict as each class is generated in the same namespace and not in the namespace of the containing project.
// <auto-generated>
// THIS (.cs) FILE IS GENERATED BY UnitGenerator. DO NOT CHANGE IT.
// </auto-generated>
#pragma warning disable CS8669
#pragma warning disable CS8625
using System;

namespace UnitGenerator
{
    [AttributeUsage(AttributeTargets.Struct, AllowMultiple = false)]
    internal class UnitOfAttribute : Attribute
    {

I don't really understand the situation.
Could you provide reproducible project?


Add running "go fmt" to "make test" in makefile and run it

go fmt is required to be run for all PRs. To enforce this we are adding running go fmt to the test target in all makefiles. As part of doing this effort make test should be run to ensure all go files are formatted so that subsequent PRs don't have changes to unrelated files just for formatting.

Addressed by PR #14


Test upgrading of NBT data properties of items within shulker boxes in an item stack from 1.20.1 > 1.21

One report that this wasn't quite working?

User updated game version w/o updating HuskSync


Add numberToString

added a function to convert a number to its string representation.
Please, if accpeted add the label "hacktoberfest-accepted" 🙏

thnx anyway for your review, can you please just add "hacktoberfest-accepted", I spent the day on it